Does the x820 rooting procedure works in x821? Thanks
Yes, I have a X821 and its working fine
Flash twrp from TeamSpain 15s version:
fastboot flash recovery twrp.img
and then flash the latest SuperSu from chainfire
https://chainfire.eu/
Yep.. done!.. thanks for the reply..
i too have x821 version but nothings working... can u all telme which recovery and adb drivers you ll used, or give me links here please, rooting is failing so long for me....
---------- Post added at 01:35 PM ---------- Previous post was at 01:22 PM ----------
please give me links of adb driver that works for x821 version, an appropriate twrp and supersu file please somebody.....
nikeshcfri said:
i too have x821 version but nothings working... can u all telme which recovery and adb drivers you ll used, or give me links here please, rooting is failing so long for me....
---------- Post added at 01:35 PM ---------- Previous post was at 01:22 PM ----------
please give me links of adb driver that works for x821 version, an appropriate twrp and supersu file please somebody.....
Click to expand...
Click to collapse
which step is going wrong? I trouble had trouble getting drivers working for my old xp machine too, I tried so many i can't even remember what ones got it working for me in the end. For some reason I always have nightmares with adb divers on all android phones, lord knows why.
problem loading recovery
meangreenie said:
which step is going wrong? I trouble had trouble getting drivers working for my old xp machine too, I tried so many i can't even remember what ones got it working for me in the end. For some reason I always have nightmares with adb divers on all android phones, lord knows why.
Click to expand...
Click to collapse
recovery is getting flashed and showing done, but booting to recovery is showing the leecos stock recovery...
can u please help on this...
nikeshcfri said:
recovery is getting flashed and showing done, but booting to recovery is showing the leecos stock recovery...
can u please help on this...
Click to expand...
Click to collapse
yep, i done the same thing. eventually I worked out that i had to hold up volume and power buttons to exit fastboot after flashing twrp, and keep holding until you see recovery booting.
twrp then boots up and offers to make system changes so it won't get overwritten on normal boot, just swipe at the bottom of the screen to let twrp make the changes
meangreenie said:
yep, i done the same thing. eventually I worked out that i had to hold up volume and power buttons to exit fastboot after flashing twrp, and keep holding until you see recovery booting.
twrp then boots up and offers to make system changes so it won't get overwritten on normal boot, just swipe at the bottom of the screen to let twrp make the changes
Click to expand...
Click to collapse
i tried holding the vol up and power key after flashing twrp but the phone booted into system and not recovery
i tried adb reboot recovery didnt worked, then i tried fastboot reboot n then adb reboot recovery it booted into stock recovery..
nikeshcfri said:
i tried holding the vol up and power key after flashing twrp but the phone booted into system and not recovery
i tried adb reboot recovery didnt worked, then i tried fastboot reboot n then adb reboot recovery it booted into stock recovery..
Click to expand...
Click to collapse
try again with volume up and power after flashing twrp, try to press volume up first and then power and hold both and don't let go even as the phone restarts out of fastboot, keep holding
still no
meangreenie said:
try again with volume up and power after flashing twrp, try to press volume up first and then power and hold both and don't let go even as the phone restarts out of fastboot, keep holding
ok i got twrp but its not mounting any data from internal storage, i tried installing supersu from sideload but that too didnt worked,..
Click to expand...
Click to collapse
strange
nikeshcfri said:
i think my drivers on win 7 are improper or something, its still not working...
tried that also
Click to expand...
Click to collapse
Is it booting straight to stock recovery holding the buttons? if it's just going straight the normal system boot, it would suggest the button combo isn't working. Maybe it's a different combo for x821 software. Drivers won't have an affect on a button combo reboot afaik.
button sets are ok
meangreenie said:
Is it booting straight to stock recovery holding the buttons? if it's just going straight the normal system boot, it would suggest the button combo isn't working. Maybe it's a different combo for x821 software. Drivers won't have an affect on a button combo reboot afaik.
Click to expand...
Click to collapse
holding vol up and power goes into recovery but stock recovery, twrp is nowhere in picture..
another problem
meangreenie said:
Is it booting straight to stock recovery holding the buttons? if it's just going straight the normal system boot, it would suggest the button combo isn't working. Maybe it's a different combo for x821 software. Drivers won't have an affect on a button combo reboot afaik.
Click to expand...
Click to collapse
my twrp is loading but twrp cannot mount internal storage data..
i want to flash cyanogenmod 13 on the phone wht to do now..
i really appreciate your help, plz just few steps further..
at this point i think it might be better to flash official china s17 or s19 with reset option, reboot fully then flash the twrp 3.0.2.0 from the rom kernel section here [RECOVERY][OFFICIAL]TWRP 3.0.2-0 [LeEco Le Max 2]
Related
So I did everything I could. None of the instructions on this forum help me, I am almost a complete newb in this.
I used this instruction: wiki.cyanogenmod.org/w/Install_CM_for_p3
To the part where you need to boot into recovery by holding power and volume up. Well, guess what, nothing happens when you hold power + volume up.
Please, could someone write a good step-by-step newb-friendly manual on how to get the Jelly Bean on this tab? I am seriously considering throwing this thing out of the window right now as I spent the whole evening trying to get this working with no results.
By the way, after doing all the manipulations with odin, now when the tab is loading and it shows the logo "samsung galaxy tab 10.1v", there is an image of an open lock in the bottom of the screen.
oh_delay said:
By the way, after doing all the manipulations with odin, now when the tab is loading and it shows the logo "samsung galaxy tab 10.1v", there is an image of an open lock in the bottom of the screen.
Click to expand...
Click to collapse
That means the bootloader is unlocked, the first step to install custom ROMs and recovery images.
---------- Post added at 01:18 PM ---------- Previous post was at 01:00 PM ----------
oh_delay said:
So I did everything I could. None of the instructions on this forum help me, I am almost a complete newb in this.
I used this instruction: wiki.cyanogenmod.org/w/Install_CM_for_p3
To the part where you need to boot into recovery by holding power and volume up. Well, guess what, nothing happens when you hold power + volume up.
Click to expand...
Click to collapse
Yes, with the P3, never could use POWER+VOL UP to boot into recovery (that combination can get out of stock recovery and into normal boot, which IS useful, since sometimes, one makes a mistake and stays stranded on a recovery bootloop.
Unfortunately, contrary to P4, there is no menu in the bootloader to boot into recovery.
You can however substitute that step 3 with this:
"From a terminal run adb reboot recovery"
[NOTE: its skipped in the tutorial, but for adb to function while in normal mode, you need to activate it, by going to Settings->Programmer Tools (or something like that, activate it, since its off by default and set the DEBUG USB connection on , or something - sorry, they changed the place in 4.1 and cannot give you the correct path)]
The device will then reboot into the Clockworkmod Recovery (assuming it has been correctly flashed); if not, repeat step 9 from section above.
Afterwards, you can either use adb or the Boot into Recovery menu option from the Shutdown dialog of ClockworkMod to boot into recovery.
AW: Recovery doesn't boot! Help!allready
Slow down
Bootloader unlocked ??
Custom revovery allreadY flashed??
You started With a stock Rom ??
3.1? 4.0.3?
A bit more info pls
Boot in bootloader by Holding power and volume -
Than
Fastboot flash recovery recovery.img
fastboot reboot recovery
You are still able to boot in Rom ??
Gesendet von meinem HTC One X mit Tapatalk 2
feraay said:
Slow down
Bootloader unlocked ??
Custom revovery allreadY flashed??
You started With a stock Rom ??
3.1? 4.0.3?
A bit more info pls
Click to expand...
Click to collapse
Well, yeah, apparently. I have stock 4.0.4 installed.
feraay said:
Boot in bootloader by Holding power and volume -
Than
Fastboot flash recovery recovery.img
fastboot reboot recovery
You are still able to boot in Rom ??
Gesendet von meinem HTC One X mit Tapatalk 2
Click to expand...
Click to collapse
What exactly should I do? IDK what that means, "Fastboot flash recovery recovery.img
fastboot reboot recovery".
As I said, I am almost a complete newb in this.
pruano said:
That means the bootloader is unlocked, the first step to install custom ROMs and recovery images.
---------- Post added at 01:18 PM ---------- Previous post was at 01:00 PM ----------
Yes, with the P3, never could use POWER+VOL UP to boot into recovery (that combination can get out of stock recovery and into normal boot, which IS useful, since sometimes, one makes a mistake and stays stranded on a recovery bootloop.
Unfortunately, contrary to P4, there is no menu in the bootloader to boot into recovery.
You can however substitute that step 3 with this:
"From a terminal run adb reboot recovery"
[NOTE: its skipped in the tutorial, but for adb to function while in normal mode, you need to activate it, by going to Settings->Programmer Tools (or something like that, activate it, since its off by default and set the DEBUG USB connection on , or something - sorry, they changed the place in 4.1 and cannot give you the correct path)]
The device will then reboot into the Clockworkmod Recovery (assuming it has been correctly flashed); if not, repeat step 9 from section above.
Afterwards, you can either use adb or the Boot into Recovery menu option from the Shutdown dialog of ClockworkMod to boot into recovery.
Click to expand...
Click to collapse
I did adb reboot recovery, and it booted the stock recovery. Maybe I should use another recovery image? I used the one linked in the CM's instructions.
Ok, so basically what happens now is I flash recovery.tar.md5 through Odin, then it reboots in OS and I reboot it to recovery through terminal. The recovery says 'Android system recovery <3e>', so I assume it's the stock one?
feraay said:
Boot in bootloader by Holding power and volume -
Than
Fastboot flash recovery recovery.img
fastboot reboot recovery
Click to expand...
Click to collapse
Ok i figured out how to use fastboot command. Still I don't understand, which recovery.img should I flash? I don't have this file, at least not in an .img format, it's format is .tar.md5
So I guess my next question is, where can I get recovery in .img format?
OK, so I figured this out.
I downloaded the recovery.img for the Galaxy Tab 10.1 from the official CWM site (NOT 10.1v, cause they don't have it for this version. It worked fine).
then I loaded in bootloader, used ./fastboot boot <path to downloaded recovery.img>, I just dragged the img to terminal window.
Through this booted recovery, I flashed the CM rom and gapps (I did this without actually flashing the recovery, mind you).
After that, I used odin in windows again to flash their recovery.tar.md5, and now finally, when I use ./adb reboot recovery it starts up with CWM.
So yeah, thank you for your posts and thoughts, you helped me figure this out.
oh_delay said:
Through this booted recovery, I flashed the CM rom and gapps (I did this without actually flashing the recovery, mind you).
Click to expand...
Click to collapse
Yes, if you use "fastboot boot [recovery image]" instead of "fastboot flash recovery [recovery image]", you can boot to a custom recovery like CWM without flashing.
oh_delay said:
After that, I used odin in windows again to flash their recovery.tar.md5, and now finally, when I use ./adb reboot recovery it starts up with CWM.
Click to expand...
Click to collapse
Fastboot only accepts .img files, Odin only accepts tar.md5 files; however, tar.md5 files are just archive files, if you rename the file to remove the .md5 extension and use a program like 7-zip which can read .tar files, you will find one or more .img files inside, which you can extract for use with fastboot.
oh_delay said:
So yeah, thank you for your posts and thoughts, you helped me figure this out.
Click to expand...
Click to collapse
Great that you managed on your own (even with some tips), best way to learn.
---------- Post added at 12:12 PM ---------- Previous post was at 12:07 PM ----------
oh_delay said:
Well, yeah, apparently. I have stock 4.0.4 installed.
Click to expand...
Click to collapse
Its the last stock release for this tablet.
---------- Post added at 12:45 PM ---------- Previous post was at 12:12 PM ----------
oh_delay said:
I used this instruction: wiki.cyanogenmod.org/w/Install_CM_for_p3
Click to expand...
Click to collapse
One last thing: those instructions do not include adding root, as indeed you can use most of the functionality of Cyanogen without root (and possibly exposing your device to malware).
However many useful functions and apps DO require root; to check if you have root, either install this app, or do "adb shell" + "adb su", which should change the prompt from a $ to a #
For root the best way is probably to flash both zip files (ARM version) with CWM at this point (so you get the latest version); dont forget to hit the "Fix Permissions" CWM option afterwards to prevent any potential problems.
AW: Recovery doesn't boot! Help!
Noo dont take 10.1 recovery take the recovery from droidbasement.com
P3 7100 only this
And do this
Adb reboot bootloader
If not work press power and volume +
Or may
power and volume -
Should Boot into bootloader click not in download modus for Odin just take the other icon and Connect to PC
Fastboot flash recovery recovery.img
Thats all
Gesendet von meinem HTC One X mit Tapatalk 2
So I was on my TWRP recovery and I wiped Dalvik cache and all the other things that I was able to wipe while I was on the TWRP recovery and now my phone won't boot up. It is stuck on the white screen that says, "htc powered by android"
I assume that I probably wiped the os and everything. I can't get access to the TWRP recovery now what do I do?
Hold power, vol up, and vol down. Try that, if that does not work try holding the power button down till the phone shuts off, they hold power button and vol down this should get you into recovery.
grneyez said:
Hold power, vol up, and vol down. Try that, if that does not work try holding the power button down till the phone shuts off, they hold power button and vol down this should get you into recovery.
Click to expand...
Click to collapse
Power button + vol down is the button combo for bootloader, not recovery. Bootloader and recovery completely different things, so its important not the confuse them.
Power + vol up will restart the phone (similar to a battery pull on phones with a use accessible battery).
Power+ vol up and vol down is not any button combination for this phone I am familiar with.
Its not clear whether the OP is having trouble accessing bootloader; or if he can access bootloader but not recovery. Again, these are 2 very different issues. You are right, in that failure to access bootloader is almost always a matter of user error in not performing the button combo correctly. If the phone is stuck on the boot splash (which is what it sounds like) the correct sequence would be:
1) Hold power + vol up until the phone reboots.
2) The moment the screen goes black, but before the boot splash screen, let go of the vol up, and press vol down
3) Do not let go of vol down until the bootloader screen appears
Failure to get into bootloader is usually because either the user started pressing vol down to late; or let go of it too early. As long as the screen comes on, bootloader is virtually always accessible.
---------- Post added at 12:20 PM ---------- Previous post was at 12:08 PM ----------
jae2014 said:
So I was on my TWRP recovery and I wiped Dalvik cache and all the other things that I was able to wipe while I was on the TWRP recovery and now my phone won't boot up. It is stuck on the white screen that says, "htc powered by android"
I assume that I probably wiped the os and everything.
Click to expand...
Click to collapse
Of course the phone won't boot. If you wiped /system, the OS is wiped.
If you don't know what it is, you shouldn't be wiping it.
Some folks like to wipe /system before they flash a new ROM for the sake of being thorough, but technically this is not necessary. Flashing a ROM always wipes /system.
But it doesn't sound like you were flashing a ROM. What were you trying to do, and why were you wiping things?
My advice would be to access bootloader as described above, then select recovery. Alternately, use adb to reboot into recovery:
adb reboot recovery
If you still can't get into recovery with either the adb command or from bootloader, its likely that recovery was somehow damaged or otherwise not accessible. Use fastboot to flash it again (boot into bootloader, select fastboot mode):
fastboot erase cache
fastboot flash recovery "filename.img"
(where "filename.img" is the actual name of the desired the recovery file with no quotes, placed in your fastboot folder on your computer)
Once recovery is working again, either restore your nandroid or flash the stock rooted or custom ROM of your choice.
redpoint73 said:
Power button + vol down is the button combo for bootloader, not recovery. Bootloader and recovery completely different things, so its important not the confuse them.
Power + vol up will restart the phone (similar to a battery pull on phones with a use accessible battery).
Power+ vol up and vol down is not any button combination for this phone I am familiar with.
Its not clear whether the OP is having trouble accessing bootloader; or if he can access bootloader but not recovery. Again, these are 2 very different issues. You are right, in that failure to access bootloader is almost always a matter of user error in not performing the button combo correctly. If the phone is stuck on the boot splash (which is what it sounds like) the correct sequence would be:
1) Hold power + vol up until the phone reboots.
2) The moment the screen goes black, but before the boot splash screen, let go of the vol up, and press vol down
3) Do not let go of vol down until the bootloader screen appears
Failure to get into bootloader is usually because either the user started pressing vol down to late; or let go of it too early. As long as the screen comes on, bootloader is virtually always accessible.
---------- Post added at 12:20 PM ---------- Previous post was at 12:08 PM ----------
Of course the phone won't boot. If you wiped /system, the OS is wiped.
If you don't know what it is, you shouldn't be wiping it.
Some folks like to wipe /system before they flash a new ROM for the sake of being thorough, but technically this is not necessary. Flashing a ROM always wipes /system.
But it doesn't sound like you were flashing a ROM. What were you trying to do, and why were you wiping things?
My advice would be to access bootloader as described above, then select recovery. Alternately, use adb to reboot into recovery:
adb reboot recovery
If you still can't get into recovery with either the adb command or from bootloader, its likely that recovery was somehow damaged or otherwise not accessible. Use fastboot to flash it again (boot into bootloader, select fastboot mode):
fastboot erase cache
fastboot flash recovery "filename.img"
(where "filename.img" is the actual name of the desired the recovery file with no quotes, placed in your fastboot folder on your computer)
Once recovery is working again, either restore your nandroid or flash the stock rooted or custom ROM of your choice.
Click to expand...
Click to collapse
I appreciate your response I'm not even sure what it is that I did wrong. I was just kind of messing around and clicking things. I've learned my lesson the hard way. lol Anyways, I managed to flash the viper one rom somehow lol and now everything is ok.
I am having the same issues. but wiping the recovery cache and all that is mentioned does not work. I flash newest and or oldest twrp via fastboot commands and nothing works. It gets stuck on the white screen with the pink letters for rebooting to recovery, then after a while it just reboots the phone into the OS.
SonneKonig said:
I am having the same issues. but wiping the recovery cache and all that is mentioned does not work. I flash newest and or oldest twrp via fastboot commands and nothing works. It gets stuck on the white screen with the pink letters for rebooting to recovery, then after a while it just reboots the phone into the OS.
Click to expand...
Click to collapse
What hboot?
Hboot-3.19.0.000
os-4.28.502.1
att
s-off
supercid
twrp
root
---------- Post added at 08:47 AM ---------- Previous post was at 08:44 AM ----------
I got TWRP working but the real issue is no cell service or data. Benn going on for a while now. I RUU to stock flashed 3.16 and then back to 4.28. Then root etc again. Nothing fixes it. Got a new sim card as well.
SonneKonig said:
Hboot-3.19.0.000
os-4.28.502.1
att
s-off
supercid
twrp
root
---------- Post added at 08:47 AM ---------- Previous post was at 08:44 AM ----------
I got TWRP working but the real issue is no cell service or data. Benn going on for a while now. I RUU to stock flashed 3.16 and then back to 4.28. Then root etc again. Nothing fixes it. Got a new sim card as well.
Click to expand...
Click to collapse
You're talking about a completely different issue now, and not enough details and specifics.
Are you on AT&T?
How long is "a while", is it a year, a month, a week?
Did you change anything (new ROM, etc.) that may have stopped cell service from working; or did it just start happening spontaneously?
Does the SIM work properly on another phone (if available)? Did you try a different SIM (your provider's store might be able to help with that).
No service at all, not even emergency calls possible?
Hello Guys,
I have an issue with TWRP recovery. I can't enter in TWRP from bootloader. I have installed ViperOneM8 5.0.1. and used now for more then one year. I also notice that my battery last just for 8 hours and I think it should help to clean my phone. When I decide to clean my phone I try to enter in recovery and when I chose an option recovery in bootloader it is trying to enter but then it goes back to bootloader. I also try to install new TWRP recovery via usb cable (ADB) and issue stay the same. In the past I enter in TWRP recovery with out any problems. Can somebody help regarding this issue?
Thank you and BR...
Basinc said:
I try to enter in recovery and when I chose an option recovery in bootloader it is trying to enter but then it goes back to bootloader. I also try to install new TWRP recovery via usb cable (ADB) and issue stay the same.
Click to expand...
Click to collapse
What are the specific results when you flash TWRP? Any error messages? Or does it say successful?
What version TWRP did you try? Saying "new" is not enough. I've often seen folks say they used "new" or "latest" and when prompted for a version number, it turns out the version is 2 years old.
What firmware (OS number on bootloader screen)?
Also, try fastboot erase cache, and try to flash TWRP again.
redpoint73 said:
What are the specific results when you flash TWRP? Any error messages? Or does it say successful?
What version TWRP did you try? Saying "new" is not enough. I've often seen folks say they used "new" or "latest" and when prompted for a version number, it turns out the version is 2 years old.
What firmware (OS number on bootloader screen)?
Also, try fastboot erase cache, and try to flash TWRP again.
Click to expand...
Click to collapse
When I flash TWRP it say successful. I also try to flash it with TWRP manager.
I try to flash version 2.8.7.0. When I saw I couldn't enter in TWRP, then I also try with TWRP manager and try to flash version 3.0.2.0. But again no luck.
OS number is 4.16.401.13
I try to fastboot erase cache, but when I select fastboot I have no option erase cache in bootloader. Only Hboot, Ramdump, reboot, reboot fastboot & power down.
Do you have any new hints for me and thank you for your time...
BR,
Basinc.
Basinc said:
When I flash TWRP it say successful. I also try to flash it with TWRP manager.
I try to flash version 2.8.7.0. When I saw I couldn't enter in TWRP, then I also try with TWRP manager and try to flash version 3.0.2.0. But again no luck.
OS number is 4.16.401.13
Click to expand...
Click to collapse
I'd stick with flashing by fastboot command. Apps like TWRP Manager just add a layer of needless complication. Something more to go wrong.
Both those TWRP versions should be okay, I think. But for your OS number, I'd be inclined to stick with 2.8.7.0
Basinc said:
I try to fastboot erase cache, but when I select fastboot I have no option erase cache in bootloader. Only Hboot, Ramdump, reboot, reboot fastboot & power down.
Click to expand...
Click to collapse
Its not a bootloader option on the phone, its a fastboot command you issue on your computer, like the one you used to flash TWRP. Connect the phone to PC, boot phone to bootloader-fastboot mode. Then in command prompt:
fastboot erase cache
Then try to flash TWRP 2.8.7 again, and see if you can them boot into TWRP.
Hi Redpoint,
I try to erase cache via usb cable like I would flash recovery. In cmd cache was erased successfully. I also flash recovery successfully in cmd, but then I can't enter in recovery from bootloader. When I chose option recovery I go back to bootloader. The same as before. Do you have any other hint for this problem?
Basinc said:
Do you have any other hint for this problem?
Click to expand...
Click to collapse
Hmm, not sure what the problem might be. All I can think of is relock the bootloader (not needed if s-off) and RUU back to full stock image (basically, "start from scratch"), then try to unlock the bootloader and install TWRP again.
For that matter, you can RUU up to Marshmallow (MM) firmware, to get everything up to date. Although you will need to flash the MM firmware first, then MM RUU as described in the red text under RUUs section of my Index thread: https://forum.xda-developers.com/showthread.php?t=2751432
Also, keep in mind that RUU will wipe all data on the phone.
Hi Guys,
I want to root my LG G5 with TWRP & SuperSU
So first i unlocked the bootloader for my phone.
2. Dwonloaded TWRP & SuperSU
3. Installed TWRP with CMD
works everything fine, but i cant enter in the TWRP recovery it just loads the normal recovery where i can swipe my data.
I also tried to "fastboot boot" into TWRP recovery and also install TWRP and remove battery so android cannt boot.
Unfortunately nothing worked
I really dont know what to do ?
thx 4 help
trash195 said:
Hi Guys,
I want to root my LG G5 with TWRP & SuperSU
So first i unlocked the bootloader for my phone.
2. Dwonloaded TWRP & SuperSU
3. Installed TWRP with CMD
works everything fine, but i cant enter in the TWRP recovery it just loads the normal recovery where i can swipe my data.
I also tried to "fastboot boot" into TWRP recovery and also install TWRP and remove battery so android cannt boot.
Unfortunately nothing worked
I really dont know what to do ?
thx 4 help
Click to expand...
Click to collapse
Start your phone in fastboot mode, flash TWRP, disconnect and reconnect the battery.
Now hold volume down + power until you see the LG logo, keep holding volume down and let go of the power button for a moment and then hold the power button again while still holding the volume down button.
You will now see a prompt asking if you'd like to factory reset, press yes to both prompts.
You will now be inside TWRP.
Which variant you are using.
mass/cls/ said:
Start your phone in fastboot mode, flash TWRP, disconnect and reconnect the battery.
Now hold volume down + power until you see the LG logo, keep holding volume down and let go of the power button for a moment and then hold the power button again while still holding the volume down button.
You will now see a prompt asking if you'd like to factory reset, press yes to both prompts.
You will now be inside TWRP.
Click to expand...
Click to collapse
I've tried this process myself and I get the same result. Reply Yes, Yes to factory reset and it *should* then start TWRP but it doesn't. You end up with a wiped phone and have to start all over again. Tried process a few times and never works.
lywyn said:
I've tried this process myself and I get the same result. Reply Yes, Yes to factory reset and it *should* then start TWRP but it doesn't. You end up with a wiped phone and have to start all over again. Tried process a few times and never works.
Click to expand...
Click to collapse
The only reason it wouldn't work is if you did not flash TWRP correctly, make sure flashing TWRP with fastboot was successful before disconnecting the battery and entering the factory reset prompt.
mass/cls/ said:
The only reason it wouldn't work is if you did not flash TWRP correctly, make sure flashing TWRP with fastboot was successful before disconnecting the battery and entering the factory reset prompt.
Click to expand...
Click to collapse
It is successful, and I pull the battery and go straight into recovery as recommended. Used latest version.
lywyn said:
It is successful, and I pull the battery and go straight into recovery as recommended. Used latest version.
Click to expand...
Click to collapse
This is not something I've ever had a problem with, every time I've wiped my phone and installed a new version this has worked.
Flash the latest version of android with LGUP and try again.
mass/cls/ said:
This is not something I've ever had a problem with, every time I've wiped my phone and installed a new version this has worked.
Flash the latest version of android with LGUP and try again.
Click to expand...
Click to collapse
On V20a-234-30. I have flashed TWRP successfully in the past. Might try LGUP to V20D and then try, but if it factory resets I waste hours while phone goes through setup to try again
lywyn said:
On V20a-234-30. I have flashed TWRP successfully in the past. Might try LGUP to V20D and then try, but if it factory resets I waste hours while phone goes through setup to try again
Click to expand...
Click to collapse
Yes I know it is very annoying when that happens, you should definitely flash the latest version regardless, I'm sure you won't have the problem after flashing :good:.
trash195 said:
Hi Guys,
I want to root my LG G5 with TWRP & SuperSU
So first i unlocked the bootloader for my phone.
2. Dwonloaded TWRP & SuperSU
3. Installed TWRP with CMD
works everything fine, but i cant enter in the TWRP recovery it just loads the normal recovery where i can swipe my data.
I also tried to "fastboot boot" into TWRP recovery and also install TWRP and remove battery so android cannt boot.
Unfortunately nothing worked
I really dont know what to do ?
thx 4 help
Click to expand...
Click to collapse
Found it! After you install twrp, you just execute 2 more commands:
fastboot format userdata
fastboot format cache
Don't reboot, just turn it off.
Works like a charm!
Hi All,
I have an Redmi 3 pro with unlocked BL and the latest "official" weekly 7.3.9 from xiaomi.eu and latest TWRP 3.0.2.0 from official twrp site.
I am unable to flash twrp.
I flash it with fastboot flash recovery recovery.img then boot into it using fastboot boot recovery.img with no issue at all.
Then,
if i reboot into recovery from twrp itself it still works.
if i let it boot the phone in its bootloader (POW+VOL_UP the one where you can choose "download" "fasboot" or "recovery") and i select recovery, it does not boot. The phone boots instead.
if i choose from the updater to reboot in recovery, same.
if i choose from flashify (which shows me "stock recovery" is installed), same.
if i use adb reboot recovery same.
i can only boot it using command fastboot boot recovery.img.
It just looks like the twrp flash says OKAY but it's not being flashed.
I've also tried cofface recovery with no success.
i've also tried official twrp app with no success.
everytime flash goes fine and successfully, but i'm unable to boot the phone in recovery itself.
i must always use fastboot boot recovery.img
Hints?
Hi @lalontra,
Use combination of Power+Vol(+)+Vol(-) button. It should boots you to recovery.
Regards.
Sent from my Redmi 3 using XDA Labs
It is error in this release ROM
You are not alone, its problem of this concrete ROM from 9.3.2017 ido.! You must flash different ROM, previous release.
krasCGQ said:
Hi @lalontra,
Use combination of Power+Vol(+)+Vol(-) button. It should boots you to recovery.
Regards.
Click to expand...
Click to collapse
Hi,
Did not work.
I have now reverted to 7.2.24 and TWRP from the TWRP from the phone is back. I think something is broken in 7.3.9 global weekly miui build.
krasCGQ said:
Hi @lalontra,
Use combination of Power+Vol(+)+Vol(-) button. It should boots you to recovery.
Regards.
Sent from my Redmi 3 using XDA Labs
Click to expand...
Click to collapse
For me works
Sent from my Redmi 3 using XDA-Developers Legacy app
The Volume+ and Volume- and Power worked for me even with the rom error. Hold all buttons til you see the Mi logo, then release Power but keep holding both of the Volume buttons. I also reflashed TWRP Recovery via Fastboot, so maybe that was it.
I'm also facing a problem around TWRP 3.0.2.
But different situation
I always failed/unable to boot into recovery or bootloader everytime I click reboot recovery or bootloader button in TWRP recovery mode.
I still try to find a way how to fix it. Because all the articles that I found always explain about "cannot enter to recovery mode from the system", not from the recovery mode itself.
Do you got anything from all the steps above? Please let me know if there something u can share. Thanks in advance
Here's what happened in my xiaomi redmi 3 pro. Always failed to boot into recovery again or into bootloader mode when I'm still in TWRP mode.
lalontra said:
Hi,
Did not work.
I have now reverted to 7.2.24 and TWRP from the TWRP from the phone is back. I think something is broken in 7.3.9 global weekly miui build.
Click to expand...
Click to collapse
Update, once installed 7.3.23 all three buttons combination works!
What still does not work is adb reboot recovery nor reboot in recovery from update page, but this is fine to me.
Thanks a lot!
brittown said:
I'm also facing a problem around TWRP 3.0.2.
But different situation
I always failed/unable to boot into recovery or bootloader everytime I click reboot recovery or bootloader button in TWRP recovery mode.
I still try to find a way how to fix it. Because all the articles that I found always explain about "cannot enter to recovery mode from the system", not from the recovery mode itself.
Do you got anything from all the steps above? Please let me know if there something u can share. Thanks in advance
Click to expand...
Click to collapse
Hello there, Im also facing the same.
I can enter both recovery / bootloader from key combo but not from the system nor TWRP itself. I cannot really find a way to fix issue wich is kinda annoying for us flashaolics...
hope someone can find a way to fix it!
lalontra said:
Hi All,
I have an Redmi 3 pro with unlocked BL and the latest "official" weekly 7.3.9 from xiaomi.eu and latest TWRP 3.0.2.0 from official twrp site.
I am unable to flash twrp.
I flash it with fastboot flash recovery recovery.img then boot into it using fastboot boot recovery.img with no issue at all.
Then,
if i reboot into recovery from twrp itself it still works.
if i let it boot the phone in its bootloader (POW+VOL_UP the one where you can choose "download" "fasboot" or "recovery") and i select recovery, it does not boot. The phone boots instead.
if i choose from the updater to reboot in recovery, same.
if i choose from flashify (which shows me "stock recovery" is installed), same.
if i use adb reboot recovery same.
i can only boot it using command fastboot boot recovery.img.
It just looks like the twrp flash says OKAY but it's not being flashed.
I've also tried cofface recovery with no success.
i've also tried official twrp app with no success.
everytime flash goes fine and successfully, but i'm unable to boot the phone in recovery itself.
i must always use fastboot boot recovery.img
Hints?
Click to expand...
Click to collapse
I'm facing same problem with you since updated to 7.3.9 Global Beta ROM.
I can only boot into TWRP by holding down Power + Vol Up + Vol Down buttons simultaneously.
---------- Post added at 11:59 AM ---------- Previous post was at 11:55 AM ----------
rubenix said:
Hello there, Im also facing the same.
I can enter both recovery / bootloader from key combo but not from the system nor TWRP itself. I cannot really find a way to fix issue wich is kinda annoying for us flashaolics...
hope someone can find a way to fix it!
Click to expand...
Click to collapse
I'm still on 7.3.30, does it fixed in the latest update?
hi I'm using redmi 3s too. This problem happened when I flash new kernel to enable double tap to screen on I flashed twrp using both method: official twrp app and fastboot devices method...did not work but then power off the phone and use power + vol- + vol+ (works))) thanks for this post (note: for those who encouter this problem, when power + vol+ + vol- keep holding the 3 button until twrp logo on ))
phenomejohn said:
The Volume+ and Volume- and Power worked for me even with the rom error. Hold all buttons til you see the Mi logo, then release Power but keep holding both of the Volume buttons. I also reflashed TWRP Recovery via Fastboot, so maybe that was it.
Click to expand...
Click to collapse
Thanks, it worked for me.
I unlocked bootloader, went to fastboot and tried to flash TWRP - https://eu.dl.twrp.me/mido/ (I have SN version of RN4). Flash went without error, but then I pressed volume-up and power-on and phone didn't go on. Notification LED for battery doesn't light when connected and I can't turn the phone on or access the fastboot. It seems bad to me. Is there anything I can do? I spent my only money for this device and fact I might kill it makes me cry.
gr4nis said:
I unlocked bootloader, went to fastboot and tried to flash TWRP - https://eu.dl.twrp.me/mido/ (I have SN version of RN4). Flash went without error, but then I pressed volume-up and power-on and phone didn't go on. Notification LED for battery doesn't light when connected and I can't turn the phone on or access the fastboot. It seems bad to me. Is there anything I can do? I spent my only money for this device and fact I might kill it makes me cry.
Click to expand...
Click to collapse
Did you flash twrp successfully right?
If yeah, then try enter into fastboot mode [volume down + power key] use fastboot commands to boot to TWRP -
Fastboot boot <whatever the recovery name.img> hit enter, then wait sometime it'll eventually boot to trwp, from twrp flash lazyflasher zip, reboot your phone, that's the way.
If you can't go on fastboot mode, then try this - http://en.miui.com/thread-565784-1-1.html
deleted
sachin n said:
Did you flash twrp successfully right?
If yeah, then try enter into fastboot mode [volume down + power key] use fastboot commands to boot to TWRP -
Fastboot boot <whatever the recovery name.img> hit enter, then wait sometime it'll eventually boot to trwp, from twrp flash lazyflasher zip, reboot your phone, that's the way.
If you can't go on fastboot mode, then try this - http://en.miui.com/thread-565784-1-1.html
Click to expand...
Click to collapse
Well, I managed to do what you said, I was in TWRP and flashed lazyflasher. I clicked reboot but phone don't go on. If I hold power on phone long enough (7 sec or so) it just shows Xiaomi logo for a split of second and then go off. Before I did that, I held button long enough and was able to boot into system. Now I can't.
gr4nis said:
Well, I managed to do what you said, I was in TWRP and flashed lazyflasher. I clicked reboot but phone don't go on. If I hold power on phone long enough (7 sec or so) it just shows Xiaomi logo for a split of second and then go off.
Click to expand...
Click to collapse
Ohhh! Yeah! I too faced this issue bruh! [look here - https://forum.xda-developers.com/redmi-note-4/help/redmi-note-4-isnt-booting-flashing-twrp-t3587781] same issue, it's just pops mi logo for a sec when I long press power key.
How I recovered my device -
Went to fastboot mode - volume down + power key.
Then fastboot boot <recovery.img>
Wait let it boot to TWRP, once you get into twrp, just wipe everything except internal /SD card, then choose install zip, flash los14.1. Firmware, then flash any custom rom + Gapps, hit reboot!
This fixed my issue.
Try this»^
---------- Post added at 11:46 ---------- Previous post was at 11:41 ----------
Links - firmware.zip
DL this rom
Choose gapps - opengapps.org [choose Pico variant, or whatever the package you want] (7.1/arm64)
RESOLVED
sachin n said:
Ohhh! Yeah! I too faced this issue bruh! [look here - https://forum.xda-developers.com/redmi-note-4/help/redmi-note-4-isnt-booting-flashing-twrp-t3587781] same issue, it's just pops mi logo for a sec when I long press power key.
How I recovered my device -
Went to fastboot mode - volume down + power key.
Then fastboot boot <recovery.img>
Wait let it boot to TWRP, once you get into twrp, just wipe everything except internal /SD card, then choose install zip, flash los14.1. Firmware, then flash any custom rom + Gapps, hit reboot!
This fixed my issue.
Click to expand...
Click to collapse
Oh, dude! You really saved my ass. It worked! Thank you very much. You are the hero of the day. Long be your life!
gr4nis said:
Oh, dude! You really saved my ass. It worked! Thank you very much. You are the hero of the day. Long be your life!
Click to expand...
Click to collapse
Hahaha! :silly:
I'm glad you fixed it! now, play with custom ROMs, Miui sux.
sachin n said:
Hahaha! :silly:
I'm glad you fixed it! now, play with custom ROMs, Miui sux.
Click to expand...
Click to collapse
Yeah, it does But actually one more question. I tried to get to TWRP once again but there is no TWRP after holding Vol+ and Power on. There is still stock recovery something which looks like this. Everything else is fine but I don't feel like going through fastboot when recovery is needed.
gr4nis said:
Oh, dude! You really saved my ass. It worked! Thank you very much. You are the hero of the day. Long be your life!
Click to expand...
Click to collapse
gr4nis said:
Yeah, it does But actually one more question. I tried to get to TWRP once again but there is no TWRP after holding Vol+ and Power on. There is still stock recovery likeTHIS. Everything else is fine but I don't feel like going through fastboot when recovery is needed.
Click to expand...
Click to collapse
Dude nah!!
Follow this to boot recovery mode -
Power off your device
Press volume up + power key until you see MI logo, when you see it, just leave power key but keep hold the volume up.
BTW, which rom did you flashed?
sachin n said:
Dude nah!!
Follow this to boot recovery mode -
Power off your device
Press volume up + power key until you see MI logo, when you see it, just leave power key but keep hold the volume up.
BTW, which rom did you flashed?
Click to expand...
Click to collapse
Yeah, I did just like that. Even when I enable advanced reboot in dev options and choose to reboot directly to recovery from system, I get that black screen instead of TWRP.
I flashed LOS 14 for now. Maybe I'll go with RR later.
gr4nis said:
Yeah, I did just like that. Even when I enable advanced reboot in dev options and choose to reboot directly to recovery from system, I get that black screen instead of TWRP.
Click to expand...
Click to collapse
Damn!
Get terminal Emulator from play store -
su hit enter -
Then -
reboot recovery - - hit enter
@gr4nis, Sup now? Still the same Mi pc suite screen?
sachin n said:
Damn!
Get terminal Emulator from play store -
su hit enter -
Then -
reboot recovery - - hit enter
@gr4nis, Sup now? Still the same Mi pc suite screen?
Click to expand...
Click to collapse
It said "su: not found" but I entered "reboot recovery" anyway and got the same black screen as before.
gr4nis said:
It said "su: not found" but I entered "reboot recovery" anyway and got the same black screen as before.
Click to expand...
Click to collapse
Eh, it looks like twrp is gone. Ehh
Nothing to worry, tell me what rom are you on at the moment?
sachin n said:
Eh, it looks like twrp is gone. Ehh
Nothing to worry, tell me what rom are you on at the moment?
Click to expand...
Click to collapse
This one: https://forum.xda-developers.com/re...other-development/rom-lineageos-14-0-t3566095
I believe the same you recommended.
Should I maybe try to "fastboot boot recovery.img" ?
gr4nis said:
This one: https://forum.xda-developers.com/re...other-development/rom-lineageos-14-0-t3566095
I believe the same you recommended.
Should I maybe try to "fastboot boot recovery.img" ?
Click to expand...
Click to collapse
Yeah, just fastboot boot recovery.img, once you are in recovery, just flash lineageOS addon.zip [look here - addonsu-arm64-signed.zip] ,reboot. Then tell me..
Link for the addon.zip - https://download.lineageos.org/extras [Download '' addonsu-arm64-signed.zip''.
sachin n said:
Yeah, just fastboot boot recovery.img, once you are in recovery, just flash lineageOS addon.zip [look here - addonsu-arm64-signed.zip] ,reboot. Then tell me..
Link for the addon.zip - https://download.lineageos.org/extras [Download '' addonsu-arm64-signed.zip''.
Click to expand...
Click to collapse
Oh, root was missing, sure. That's why "su" didn't work. Okay, rooted now. What's next?
BTW: I'm starting to think I never flashed TWRP. I guess I was too hasty after it said it's done. Maybe I should gave it some more time. I immediately pushed Vol+ and Power button. Maybe it wasn't flashed at all or wasn't flashed properly. Should I try to flash it again?
@sachin n
gr4nis said:
Oh, root was missing, sure. That's why "su" didn't work. Okay, rooted now. What's next?
BTW: I'm starting to think I never flashed TWRP. I guess I was too hasty after it said it's done. Maybe I should gave it some more time. I immediately pushed Vol+ and Power button. Maybe it wasn't flashed at all or wasn't flashed properly. Should I try to flash it again?
@sachin n
Click to expand...
Click to collapse
Wait, you got su access? Then wait, u don't need a pc now!
You can flash recovery.img from flashify app [DL it from PS]
Download flashify app from PS, open it, give su access.
Then choose flash recovery.img from the list, locate twrp.img, once its done just hit the reboot now, when it prompts.
sachin n said:
Wait, you got su acces? Then wait, u don't need a pc now!
You can flash recovery.img from flashify app [DL it from PS]
Click to expand...
Click to collapse
Yeah, I thought it was the reason why you asked me to flash that addonsu-arm64-signed.zip. But I installed Flashify and it said I don't have a root. So I flashed SuperSU and then flashed recovery through Flashify. Now it works! So, again, thank you! You helped me a lot today. :good:
gr4nis said:
Yeah, I thought it was the reason why you asked me to flash that addonsu-arm64-signed.zip. But I installed Flashify and it said I don't have a root. So I flashed SuperSU and then flashed recovery through Flashify. Now it works! So, again, thank you! You helped me a lot today. :good:
Click to expand...
Click to collapse
Ah yep, that's the reason I told you to flash su.
Anyway, you're good with TWRP now?
It's easy to enter into recovery mode using physical buttons?
sachin n said:
Ah yep, that's the reason I told you to flash su.
Anyway, you're good with TWRP now?
It's easy to enter into recovery mode using physical buttons?
Click to expand...
Click to collapse
Yeah, it totally works now. Vol+ and Power button takes me to TWRP. Much better, I was already sick of Fastboot