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.
Related
A little background info:
ATT GS4, rooted and on stock firmware
Had TWRP 2.6.0.0 on my phone
Tried to flash Illusion 7|15 or 7|16?
---------------------------------------------------
In the past, I've tried to flash illusion, with some success. I was able to get to the homescreen, but when I flashed my data backup. The phone wouldn't boot, so I reverted to stock. A few weeks later, I decide to take another spin at the rom and get it working. I wiped the data/cache/dalvik, and flashed the rom with gapps, rebooted the phone, and nothing happens. The phone keeps vibrating, but there is nothing happening past that.
After a significant amount of research, I've found a few tools/advice. I've downloaded ODIN and the (disgustingly large) tar file, but it doesn't have any use if the phone cannot be recognized by the computer since I am unable to enter download mode or recovery mode.
I found another tool that is supposed to "resurrect" the phone provided by legija. The only unfortunate part is there are no instructions provided, and once again, my computer isn't recognizing the phone as a device, as if it wasn't plugged in to the usb port at all. The application asks for a port number, but I have no clue what relevance a port number has, or at least that a usb port has a numerical value.
Anyway, is there anything left for me to do or is this a fancy new paperweight?
Excuse me for any poor grammar, I'm a little antsy about this
Gfrt94yn said:
A little background info:
ATT GS4, rooted and on stock firmware
Had TWRP 2.6.0.0 on my phone
Tried to flash Illusion 7|15 or 7|16?
---------------------------------------------------
In the past, I've tried to flash illusion, with some success. I was able to get to the homescreen, but when I flashed my data backup. The phone wouldn't boot, so I reverted to stock. A few weeks later, I decide to take another spin at the rom and get it working. I wiped the data/cache/dalvik, and flashed the rom with gapps, rebooted the phone, and nothing happens. The phone keeps vibrating, but there is nothing happening past that.
After a significant amount of research, I've found a few tools/advice. I've downloaded ODIN and the (disgustingly large) tar file, but it doesn't have any use if the phone cannot be recognized by the computer since I am unable to enter download mode or recovery mode.
I found another tool that is supposed to "resurrect" the phone provided by legija. The only unfortunate part is there are no instructions provided, and once again, my computer isn't recognizing the phone as a device, as if it wasn't plugged in to the usb port at all. The application asks for a port number, but I have no clue what relevance a port number has, or at least that a usb port has a numerical value.
Anyway, is there anything left for me to do or is this a fancy new paperweight?
Excuse me for any poor grammar, I'm a little antsy about this
Click to expand...
Click to collapse
Do you have AT&T insurance? Maybe the phone can have an accident? I would know of no other way to fix it if Odin isn't recognizing it. ):
Gfrt94yn said:
A little background info:
ATT GS4, rooted and on stock firmware
Had TWRP 2.6.0.0 on my phone
Tried to flash Illusion 7|15 or 7|16?
---------------------------------------------------
In the past, I've tried to flash illusion, with some success. I was able to get to the homescreen, but when I flashed my data backup. The phone wouldn't boot, so I reverted to stock. A few weeks later, I decide to take another spin at the rom and get it working. I wiped the data/cache/dalvik, and flashed the rom with gapps, rebooted the phone, and nothing happens. The phone keeps vibrating, but there is nothing happening past that.
After a significant amount of research, I've found a few tools/advice. I've downloaded ODIN and the (disgustingly large) tar file, but it doesn't have any use if the phone cannot be recognized by the computer since I am unable to enter download mode or recovery mode.
I found another tool that is supposed to "resurrect" the phone provided by legija. The only unfortunate part is there are no instructions provided, and once again, my computer isn't recognizing the phone as a device, as if it wasn't plugged in to the usb port at all. The application asks for a port number, but I have no clue what relevance a port number has, or at least that a usb port has a numerical value.
Anyway, is there anything left for me to do or is this a fancy new paperweight?
Excuse me for any poor grammar, I'm a little antsy about this
Click to expand...
Click to collapse
I've seen the repeated vibrating issue before from flashing the wrong file. Download mode was still accessible. Try again by hooking up the phone to the USB slot without the battery in it. Hold Vol Down + Home while inserting the battery. See if download mode will come up. If it does, Odin may not fix it, and you may end up using KIES, and that's if it does go into Download mode.
Phone is toast, fortunately the phone is still under warranty and they couldn't even get it to turn on so they replaced it
Still lost data, but it's not the end of the world. Thanks for the help though!
Gfrt94yn said:
Phone is toast, fortunately the phone is still under warranty and they couldn't even get it to turn on so they replaced it
Still lost data, but it's not the end of the world. Thanks for the help though!
Click to expand...
Click to collapse
Good deal man, glad you got a new one.
I have another question for somebody knowledgeable in rooting/rom flashing:
I think this was because the s4 bootloader is locked (through an update), would this cause the phone to hard brick? I've had nasty experiences in the past with locked bootloaders!
If it is locked, is there a way to unlock it? Or does it even need to be unlocked to flash a rom?
Thanks!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Gfrt94yn said:
I have another question for somebody knowledgeable in rooting/rom flashing:
I think this was because the s4 bootloader is locked (through an update), would this cause the phone to hard brick? I've had nasty experiences in the past with locked bootloaders!
If it is locked, is there a way to unlock it? Or does it even need to be unlocked to flash a rom?
Thanks!
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
The bootloader is locked yes, but Loki is there to workaround that. What is the build version on your replacement?
JDQ39.I337UCUAMDL
Is Loki on xda? I haven't found anything like that yet, although I've heard many references to that
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Update:
Maybe I should open my eyes lol, found it in about 30 seconds
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
One more update:
I ran the casual root and now have my root and recovery. A couple of questions:
Does this also unlock the bootloader?
Somebody said that twrp flashes roms as if the bootloader is unlocked, so it wouldn't matter if it was or not. Is this true?
I guess really my question is, once I run casual root, is my phone ready to flash?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Gfrt94yn said:
One more update:
I ran the casual root and now have my root and recovery. A couple of questions:
Does this also unlock the bootloader?
Somebody said that twrp flashes roms as if the bootloader is unlocked, so it wouldn't matter if it was or not. Is this true?
I guess really my question is, once I run casual root, is my phone ready to flash?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
Your phone is ready to flash, just make sure the ROM you flash has been Lokied or you'd have to flash a Loki kernel/LokiDoki after flashing the ROM (but before rebooting).
Gfrt94yn said:
One more update:
I ran the casual root and now have my root and recovery. A couple of questions:
Does this also unlock the bootloader?
Somebody said that twrp flashes roms as if the bootloader is unlocked, so it wouldn't matter if it was or not. Is this true?
I guess really my question is, once I run casual root, is my phone ready to flash?
Sent from my SAMSUNG-SGH-I337 using xda app-developers app
Click to expand...
Click to collapse
If you are going to use TWRP, make sure the ROM has LOKI applied, and if it doesn't, flash the Loki_Doki patch last before rebooting.
If you use OUDHS recovery, it will Auto-Loki whatever you flash.
Ladies and Gentlemen, I am proud to announce that I've successfully flashed a rom without bricking my phone! *applause*
I thank(ed) you all for the help!
GS4 running slimbean and kanged key lime pie theme.
GiantBallSack said:
If you are going to use TWRP, make sure the ROM has LOKI applied, and if it doesn't, flash the Loki_Doki patch last before rebooting.
If you use OUDHS recovery, it will Auto-Loki whatever you flash.
Click to expand...
Click to collapse
What happens if one accidentally reboots before flashing Loki? Just need to reboot back into recovery and flash it?
godefroi said:
What happens if one accidentally reboots before flashing Loki? Just need to reboot back into recovery and flash it?
Click to expand...
Click to collapse
Yes
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
You know what to do. If you have any questions or problems come here. Me or someone else will do our best to help you resolve any issues.
Fauert said:
@bigfau, any fix for camera issue ?
Sent from my unknown using XDA Premium 4 mobile app
Click to expand...
Click to collapse
farhanito said:
D802?
Try "App Settings" module in Xposed. Change camera DPI to 479 or 481.
ÆONFLEX - 3.0.1
Click to expand...
Click to collapse
ÆONFLEX-3.0.3 Why Flash Anything Else.
droidiac13 said:
No problem and I wish I had better news for you. I don't think LGFlash is going to help. Again, I hope I'm wrong. I've seen too many of my friends go through it though. I would check to see if you can have it replaced.
Sent from my LG-D800 using Tapatalk
Click to expand...
Click to collapse
How do u back up your EFS files
Sent from my LG-D801 using XDA Premium 4 mobile app
**This is "my" way of doing things on my D800. I cannot take any responsibility for your device getting effed up no matter who's directions you follow!"
So you think you've got issues with this ROM? Won't boot, flash or start-up. Well, maybe you haven't followed the proper flashing sequence or you have a bad download. Did you know that 99.999% of the issues people are having is user related? Well, maybe I don't know the exact percentage, but you get my drift.
Seriously though, before posting a question, make sure you have done all the personal troubleshooting possible. To help make this a little easier, I am posting the exact method I use for flashing this ROM and I haven't had a single issue.
Before flashing any ROM, you should always be sure to do a proper back-up of your EFS files. This could very well save you from a bricked G2 and save you from having headaches if you do something wrong during the flash, wipe, etc...
The method I use is to download FreeGee from HERE. Once you have downloaded and installed FreeGee, you will have an option for backing up your EFS files and also will provided the different versions of TWRP (TWRP is all I use). Once your EFS files are backed-up, immediately upload them to the "cloud". If you need a good cloud app, HERE is one.
Now that you have this done, you are ready to attempt installing a custom ROM. Here are the steps that I take:
1. Boot into recovery
2. Make a back-up of your current ROM
3. Go back to the recovery home screen
4. Hit the Wipe button
5. Hit the Advanced Wipe button
6. Check the boxes for Dalvik Cache, System, Data and Cache. DO NOT CHECK THE INTERNAL STORAGE BOX!!!
7. Once the wipe is complete, go back to the recovery home screen
8. Hit the Install box
9. Choose the ROM you want to install
10. Swipe to confirm the flash
Once the flash is done, it should say successful if all went correctly. From that screen hit Reboot System. You should see the sweet boot screen and then be brought to the setup screen.
If you have done all this and you are still having trouble, please re-download the ROM and follow the steps again. You may have gotten a bad download.
If after you have followed these steps twice and you still have a ROM specific question, post away.
If anyone has something to add to this, let me know and I will add it. I hope this helps at least one person. bigfau, if you want me to remove this, please let me know.
Other Notes:
~ If you are on the software version that ends with "o", you will likely have to LGFlash back to the "d" version. @AyDee Thank you!
~ The newer version of TWRP and Philz Recovery may cause issues with flashing. I am using TWRP v2.6.3.3 and have no issues with it.
You could add that ATT users coming from the 'o' firmware need to roll back to 'd' and that a lot of users are having issues with the newest TWRP and Philz.
Not rom-specific but worth mentioning.
Anyone use Facebook Messenger on D800 with 3.0 and have it open two apps when you run it? Tried uninstalling and installing it again and still does it. Only app that does. Any idea how to fix it?
Sent from my LG-D800 using Tapatalk
Hello, I have the lgsetupwizard force close... What I do? Thanks!
Enviado desde mi LG-D802 mediante Tapatalk
When i want make a phone call from contacts app i got force closed, any idea ? Thx a lot
Click to expand...
Click to collapse
Up
Envoyé de mon unknown en utilisant Tapatalk
CotoZ said:
Hello, I have the lgsetupwizard force close... What I do? Thanks!
Enviado desde mi LG-D802 mediante Tapatalk
Click to expand...
Click to collapse
Just flash back to your stock kdz and then flash the rom, the issue can be solved.
Is there a 3.0.3 version out?
freakyd9984 said:
How do u back up your EFS files
Sent from my LG-D801 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
See #3 , You can use Freegee app from playstore .
muhyidin said:
Up
Envoyé de mon unknown en utilisant Tapatalk
Click to expand...
Click to collapse
I had same issue from clean install. I wiped cache and contacts. I replaced apks from 3.0.2 and also 3.0.1 but got fc. I solved by another fresh install. Now all works.
good morning last dorimanx rom comes with 1.4? correct?
jaco1975 said:
good morning last dorimanx rom comes with 1.4? correct?
Click to expand...
Click to collapse
Huh? Dorimanx makes a kernel, not a rom. I don't think this rom includes dorimanx kernel. However, you can flash it after installing the ROM.
Sent from my LG-D800 using Tapatalk
hey guys just want to share my experience when updatin 3.0.1 to 3.0.2.. here it goes . after i flash 3.0.2 i wipe also dalvic cache and after that i reboot my phone and got stucked at fastboot mode .. i just did search a little on the web . didnt find any answers . but then again as my experience of my phone being bricked i suddenly realize that i think i have a wrong kernel in my phone.. so what i did was to download stock based kernel . access my phone to twrp recovery . flash the stock kernel then reboot . :crossfingered: then it works like a charm . it booted . and now i am happy w/ my phone . ) i hope this one help someone thankss
Sent from my unknown using XDA Premium 4 mobile app
josh012 said:
hey guys just want to share my experience when updatin 3.0.1 to 3.0.2.. here it goes . after i flash 3.0.2 i wipe also dalvic cache and after that i reboot my phone and got stucked at fastboot mode .. i just did search a little on the web . didnt find any answers . but then again as my experience of my phone being bricked i suddenly realize that i think i have a wrong kernel in my phone.. so what i did was to download stock based kernel . access my phone to twrp recovery . flash the stock kernel then reboot . :crossfingered: then it works like a charm . it booted . and now i am happy w/ my phone . ) i hope this one help someone thankss
Sent from my unknown using XDA Premium 4 mobile app
Click to expand...
Click to collapse
You DL and flash stock based kernel , from where and what ? access your phone by sideload or ??
Fauert said:
You DL and flash stock based kernel , from where and what ? access your phone by sideload or ??
Click to expand...
Click to collapse
i tried dorimanx kernel its a stock based kernel . i flashed it tru twrp . i have accessed using hardware keys combination . power down your phone. then hold power + volume - then when you see the lg screen . release your fingers then push it can using the same keys . you will be headed in factory reset mode . if yiu have installed twrp earlier before you bricked your phone . just follow tje step on the screen dont be afraid because that will only lead you to the recovery mode ..
Sent from my unknown using XDA Premium 4 mobile app
WIFI issue
I installed this rom on my D801 and seemed to go well. I booted up phone and could not connect to WIFI so I bypassed that part and when on. Everything seemed to be working so I went into WIFI settings again and tried to connect again but still wouldn't connect just kept searching. Can anyone help me resolve this issue because this really is a great looking rom and would like to use it?
jimmydee62 said:
I installed this rom on my D801 and seemed to go well. I booted up phone and could not connect to WIFI so I bypassed that part and when on. Everything seemed to be working so I went into WIFI settings again and tried to connect again but still wouldn't connect just kept searching. Can anyone help me resolve this issue because this really is a great looking rom and would like to use it?
Click to expand...
Click to collapse
I had similar problem on D800 and solved it by flashing TWRP 2.6.3.3 and then re-flashing this ROM. Hope it helps.
What are the changes in the last version
josh012 said:
i tried dorimanx kernel its a stock based kernel . i flashed it tru twrp . i have accessed using hardware keys combination . power down your phone. then hold power + volume - then when you see the lg screen . release your fingers then push it can using the same keys . you will be headed in factory reset mode . if yiu have installed twrp earlier before you bricked your phone . just follow tje step on the screen dont be afraid because that will only lead you to the recovery mode ..
Sent from my unknown using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I "mis"understood you lol .... flash the stock kernel ... habla .... habla... :laugh:
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
Friends i am on stock 4.4 kitkat and i want to install pardus hd rom can anyone help me with proper guide about rooting and installing custom recovery on 4.4 kitkat
Sent from my LG-D802 using XDA Premium 4 mobile app
First you root using ioroot 25. It's extremely easy and there are instructions in the thread. Then I suggest using AutoRec to install TWRP 2.7. Again, very easy and instructions in the thread.
Then when you are ready to install the rom, you reboot into recovery. If you don't have an app or mod to do it for you, then you can do it manually. Turn off your phone, then hold volume down and power button till the lg logo appears. When that happens, you release the buttons and immediately hold them again. You will see a window asking if you want to factory reset your phone (as long as your recovery is properly installed, then there's no need to worry). Press power 3 times and it'll boot into recovery.
Now you can install your rom. The rom thread probably have instructions as well. It's probably something like wiping dalvik, system, data and cache. Then install the zip(s).
I hope this helps. I didn't go into too much details because there's already instructions in the respective threads and it's usually fairly straight forward and most screw ups can easily be fixed. Just remember to double check anything you install matches and is compatible with your specific model so you don't brick your phone. That's all. You should be fine.
Sent from my LG-D802 using XDA Free mobile app
If you have Titanium Backup like so many others, there is a reboot to recovery in options. I use it all the time.
Sindroid said:
If you have Titanium Backup like so many others, there is a reboot to recovery in options. I use it all the time.
Click to expand...
Click to collapse
Nice. I didn't know that. I use G2 tweak box to add it as a reboot option. But it's nice to know for other devices without that xposed module.
Sent from my LG-D802 using XDA Free mobile app
Trixanity said:
First you root using ioroot 25. It's extremely easy and there are instructions in the thread. Then I suggest using AutoRec to install TWRP 2.7. Again, very easy and instructions in the thread.
Then when you are ready to install the rom, you reboot into recovery. If you don't have an app or mod to do it for you, then you can do it manually. Turn off your phone, then hold volume down and power button till the lg logo appears. When that happens, you release the buttons and immediately hold them again. You will see a window asking if you want to factory reset your phone (as long as your recovery is properly installed, then there's no need to worry). Press power 3 times and it'll boot into recovery.
Now you can install your rom. The rom thread probably have instructions as well. It's probably something like wiping dalvik, system, data and cache. Then install the zip(s).
I hope this helps. I didn't go into too much details because there's already instructions in the respective threads and it's usually fairly straight forward and most screw ups can easily be fixed. Just remember to double check anything you install matches and is compatible with your specific model so you don't brick your phone. That's all. You should be fine.
Sent from my LG-D802 using XDA Free mobile app
Click to expand...
Click to collapse
Thanx bro everything worked perfectly
KaranBhoir said:
Thanx bro everything worked perfectly
Click to expand...
Click to collapse
I'm glad to hear that.
Edit: I actually forgot something in the "guide". A bit of an oversight from me. Always make nandroid backups. They can be a huge life saver. It can be done within the recovery... Or the easier way: install online nandroid backup. You can also schedule backups with that.
Sent from my LG-D802 using XDA Free mobile app
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.