Related
Hi.
Has any one been able to flash custom recovery after installing OTA and upgrading to 23.72-47?
I upgraded to stock version 23.72-47 via the OTA update way. And after that I tried using the fastboot method to flash twrp in bootloader mode. The command is execuded successfully but rebootin to recovery opens the stock recovery and not twrp. Any one was successful in flashing twrp after OTA update?
arunhebbare said:
Hi.
Has any one been able to flash custom recovery after installing OTA and upgrading to 23.72-47?
I upgraded to stock version 23.72-47 via the OTA update way. And after that I tried using the fastboot method to flash twrp in bootloader mode. The command is execuded successfully but rebootin to recovery opens the stock recovery and not twrp. Any one was successful in flashing twrp after OTA update?
Click to expand...
Click to collapse
Just for the heck of it, have you tried just booting into TWRP instead of permanently installing, to see if TWRP will even load ok?
No. Will try.....
Aaaaah, yes. Now I recall why I was wondering the first time I tried to root the fastboot command was 'fastboot boot recovery recovery.img'.
I still wonder why the flash command does not work.. There is a clear 'OKAY' indicating successful flashing of the recovery. It surprises me as to where the recovery was flashed or written (if I have understood flashing correctly).
arunhebbare said:
No. Will try.....
Aaaaah, yes. Now I recall why I was wondering the first time I tried to root the fastboot command was 'fastboot boot recovery recovery.img'.
I still wonder why the flash command does not work.. There is a clear 'OKAY' indicating successful flashing of the recovery. It surprises me as to where the recovery was flashed or written (if I have understood flashing correctly).
Click to expand...
Click to collapse
I had no problems flashing TWRP with "flash" command afterwards. My notes... http://forum.xda-developers.com/2015-moto-g/general/manual-ota-update-process-step-step-t3206049
Boot command worked
As an update I tried the fastboot boot recovery.img command and I could reboot and adb reboot onto twrp recovery mode. But when resorting to the volume button mode to recovery I again was presented with stock recovery.
I tried using the fastboot flash recovery command and it seems to have done the job. Now I am able to reboot to twrp recovery using both software and hardware ways.
What still bugs me is that why did not the flash commands work?
Any insight into this will help me understand the nuances of differences between booton and flashing o I have misunderstood them.
fastboot boot recovery.img=boot into recovery once
fastboot flash recovery=flash it permanently
Sent from my Nexus 6 using Tapatalk
Thank you, so what I too understood is correct then.
Bear with me but my question is, why the command of flashing the recovery did not work first time despite of the fact that the fastboot command terminal showed "OKAY"?
It worked when I used the boot command to flash and I could root it after that. But after booting and rooting, I was presented with the stock rom subsequently.
So, I used the flash recovery command this time around and it worked to lodge the recovery in place.
Not able to understand why the flash command did not work first time.
Appreciate any clarification or explanation
arunhebbare said:
Thank you, so what I too understood is correct then.
Bear with me but my question is, why the command of flashing the recovery did not work first time despite of the fact that the fastboot command terminal showed "OKAY"?
It worked when I used the boot command to flash and I could root it after that. But after booting and rooting, I was presented with the stock rom subsequently.
So, I used the flash recovery command this time around and it worked to lodge the recovery in place.
Not able to understand why the flash command did not work first time.
Appreciate any clarification or explanation
Click to expand...
Click to collapse
I don't know if it's same in Moto devices too or not but in Samsung there's a file named installrecovery.sh which replaces custom recoveries with stock on boot.
But once the device has been rooted it can be stopped from doing so.
Maybe this same thing happend with you.
Again this is just mere assumption keeping a samsung device in mind and may be completely wrong logic.
Sent from my SM-A800F using XDA Free mobile app
arunhebbare said:
Thank you, so what I too understood is correct then.
Bear with me but my question is, why the command of flashing the recovery did not work first time despite of the fact that the fastboot command terminal showed "OKAY"?
It worked when I used the boot command to flash and I could root it after that. But after booting and rooting, I was presented with the stock rom subsequently.
So, I used the flash recovery command this time around and it worked to lodge the recovery in place.
Not able to understand why the flash command did not work first time.
Appreciate any clarification or explanation
Click to expand...
Click to collapse
Try using a new usb cable. I have no idea WTF motorola was thinking, including that god-awful charger without a detachable usb. I've seen this problem happen several times, though. When the cable goes bad but still has the actual connection it may not transfer data properly...but since it's connected fastboot doesn't know the file never actually transferred so it reports that it's done.
I bought a 6-pack of Tronsmart USB cables from amazon for $10, and they're absolutely amazing!!! They're made with 20-gauge wires, which are far thicker than those that will come with the phone, no matter what OEM it's from. Fat cable means fast transfer speeds and a longer life, since it will take longer to fray due to its heft.
*** the deal I got is actually back. Last time it only lasted a day, so if you want it, I'd recommend hurrying!!
http://www.amazon.com/Tronsmart-Cha...YYK0/ref=sr_1_7?ie=UTF8&qid=1442849948&sr=8-7
hey guys, I need help rooting my Nexus 5 running the latest version of Android, 6.0.1
I can't seem to find a method which sounds safe enough ..
I'm no newcomer to rooting as I have done it with many other devices but this is my first time trying it on a device running marshmallow
You could try what I did successfully with SuperSU 2.62 - I'm on MM 6.0.1 and was completely stock. I believe newer SuperSU versions are amendments/improvements to the install method rather than to the SuperSU binary functions.
Copy SuperSU 2.65 (brand new today) to your device, boot temporarily into TWRP ("fastboot boot twrp.img" rather than "fastboot flash recovery twrp.img" which will permanently overwrite the stock recovery - make sure to get the right version for your N5), then in TWRP install SuperSU and reboot. You retain stock recovery (because TWRP lasts just for that session) and you can use SuperSU's full unroot function when the next OTA rolls out, install it, and then reroot.
https://dl.twrp.me/hammerhead/
http://forum.xda-developers.com/showpost.php?p=64161125
Although Chainfire does stress that this is experimental, I've had no problems with it at all, like most other people. Still, I'll repeat his warning that everybody roots at his/her own risk. You'd have to be really unlucky, careless or stupendously incompetent to do unrecoverable damage...
dahawthorne said:
You could try what I did successfully with SuperSU 2.62 - I'm on MM 6.0.1 and was completely stock. I believe newer SuperSU versions are amendments/improvements to the install method rather than to the SuperSU binary functions.
Copy SuperSU 2.65 (brand new today) to your device, boot temporarily into TWRP ("fastboot boot twrp.img" rather than "fastboot flash recovery twrp.img" which will permanently overwrite the stock recovery - make sure to get the right version for your N5), then in TWRP install SuperSU and reboot. You retain stock recovery (because TWRP lasts just for that session) and you can use SuperSU's full unroot function when the next OTA rolls out, install it, and then reroot.
https://dl.twrp.me/hammerhead/
http://forum.xda-developers.com/showpost.php?p=64161125
Although Chainfire does stress that this is experimental, I've had no problems with it at all, like most other people. Still, I'll repeat his warning that everybody roots at his/her own risk. You'd have to be really unlucky, careless or stupendously incompetent to do unrecoverable damage...
Click to expand...
Click to collapse
i am not currently running twrp.. how do i flash it from recovery ?
Download into fastboot mode and you can use fastboot commands to flash TWRP on a permanent or temporary basis to the phone, boot into twrp, flash supersu, and reboot.
I provided the link to TWRP (rename it to twrp.img after downloading) and the command you need ("fastboot boot twrp.img" without inverted commas). Which piece isn't clear?
Edit: you aren't flashing TWRP from recovery. TWRP is the recovery. All you're doing is temporarily installing TWRP to allow you to install SuperSU. I obviously have to work on my communications skills...
Edit #2: To be sure that my message is clear, the temporary TWRP installation is done via Fastboot on the PC, not within TWRP. When you've temporarily installed TWRP, which will cause your N5 to display the TWRP screen, install the SuperSU on your device (put it somewhere where you can easily find it, like Downloads), then reboot. Job done.
Questions...?
i just tried flashing and i run into an error
FAILED(remote:image is not a boot image)
i have run into this error before but i cant recall how i fixed it . any suggestions?
I have to ask - sorry...
"I'm no newcomer to rooting as I have done it with many other devices but this is my first time trying it on a device running marshmallow"
Marshmallow is admittedly slightly different from previous versions, but not show-stoppingly. I've given you the best root instructions as clearly as I can with pointers to a Marshmallow-specific root.
What exactly have you done to invoke the "FAILED" message? Did you follow my instructions to the letter?
(Edit: I do feel your pain. Sorry for appearing frustrated, since I was a total noob not long ago and am still very far short of the many people here who know the technicalities of Android infinitely better than I do, but you really have to follow the advice and provide better information if you want people to have the patience to help you.)
dahawthorne said:
I have to ask - sorry...
"I'm no newcomer to rooting as I have done it with many other devices but this is my first time trying it on a device running marshmallow"
Marshmallow is admittedly slightly different from previous versions, but not show-stoppingly. I've given you the best root instructions as clearly as I can with pointers to a Marshmallow-specific root.
What exactly have you done to invoke the "FAILED" message? Did you follow my instructions to the letter?
(Edit: I do feel your pain. Sorry for appearing frustrated, since I was a total noob not long ago and am still very far short of the many people here who know the technicalities of Android infinitely better than I do, but you really have to follow the advice and provide better information if you want people to have the patience to help you.)
Click to expand...
Click to collapse
yhup I followed exactly and I'm positive I ddnt mess up
I have to disagree. I did what I wrote and got no FAILED message...
Bootloader is unlocked?
audit13 said:
Bootloader is unlocked?
Click to expand...
Click to collapse
yes it is
Are you running a Windows PC? Is the phone detected properly in fastboot mode? What command are you typing in?
yes I am running a windows pc, device is detected and I have used both :fastboot flash recovery twrp.img and fastboot boot recovery twrp.img
Now I see two mistakes in your commands, maybe mistypes.
:fastboot flash recovery twrp.img - this would install TWRP permanently in the recovery partition - if you lose the colon at the beginning.
fastboot boot recovery twrp.img - no "recovery" - just fastboot boot twrp.img - this will boot TWRP temporarily.
And have you downloaded TWRP, renamed it for ease of typing to "twrp.img" and put it in the fastboot directory? If Fastboot doesn't find twrp.img in its directory this would cause an error.
oh kk .my bad .. thanks
So you've had 15 minutes. It must be done by now, right?
dahawthorne said:
So you've had 15 minutes. It must be done by now, right?
Click to expand...
Click to collapse
yup all done. thanks
What is the best version of TWRP ro install on nexus 5 cata 6.0.1?
I suggest 2.8.7.0.
Just out of curiosity, why not 2.8.7.1? I think I read recently that someone had had some sort of problem with it, but I've been using it with no problems at all.
Hi,
Can anybody help me how to unlock the bootloader and root Leagoo t10.
Thanks.
I solved it myself...
I finaly found a way how to unlock the bootloader...
1. I had to turn off the phone
2. hold the volume up button and insert the usb cable to connect to the pc
3. the phone starts at that point to recovery mode and after it I had to reboot to bootloader (from recovery)
4. then I could use the basic fastboot program (it finaly detected the phone via the commant "fastboot devices") and use the command "fastboot oem unlock" to unlock the bootloader
5. I finaly also had to folow the promt on the phone (the phone asked if I realy want to unlock it) to allow the bootloader to be unlocked
6. The bootloader is unlocked (when starting, the phone shows that its been unlocked)
I think that rooting after this wont be a problem...
PS
I forgot to mention that I also installed PdaNet drivers meanwhile which might be the cause fastboot was able to detect my device...
Hi
Finaly did you manage to root it successfully ?
I am just discovering this phone and I am very interested. But I need it to be rooted
Thanks
No not yet.... The trouble is not the root itself but the backing up before doing it... There are no rooting apps witch can do it automatized yet but that should be solved in the future... The problem is creating the scatter file for backup because the software doing that for Mediathek procesors was not updated for a while and can't handle the 67xx series...
There is presently a flash sale on gearbest, I just ordered it. I hope too that the necessary tools will be available some day. Thanks for the explanation. And wait...
You might be interested that a few days ago there is a downloadable version of the official Leagoo t10 software with all backups and the scatter file included... You can Google it but I believe it was page called something like " need ROMs"...
Now I could try now to Port a custom recovery but after 20 hours of trying I gave up for some time again.... I ported at least 6 recoveries from TWRP and CWM but non worked and the f*cking system of the Leagoo t10 has a failsafe witch automaticky recovers the factory recovery on any standard boot... You should look some time on that need ROMs website because if someone ports a functioning recovery on the t10 that is most probably the first place to be available... If you would have a custom recovery installed rooting would be no problem... Good luck with your new phone... I at least take it the way that I learned more about Android and the ways around it in three months than I have in that last three years thanks to Mediathek...
So I got a version of TWRP working only when you use fastboot to boot to it, the screen is frozen if you try to flash it.
Link here
command is fastboot boot <imgname>
You can root from there, not done much else but playing with it just now.
How did you managed to Port it? I tried at least 3 TWRPs from other mt6797 devices (and modified them trough image kitchen) but none worked... I also tried once to boot to one trough fastboot but that also didn't work... And you said you rooted it with that TWRP but woul it be possible to do MAGISK root this way? Because T10 has only Android 6.0 now and basic root would do the update (when it comes out) harder...
Thanks.
It took me a few hours but I got the LG K10 TWRP to work with it, not sure about MAGISK as I said I only just got it working. I see this device is discontinued now too so unlikely to see much more than this I think.
Thanks... If you got something else working please write about it because it's really hard to find anything useful about this device... And thank you again for the root advice, I will do it as soon as I have some time.
The root worked... With the TWRP from alpha232 I was able to install supersu 2.82 (trough "fastboot boot <image name>" to TWRP and install the zip from there) and my Leagoo T10 is now rooted... (Thanks Alpha232). If someone finds out a way to port TWRP for T10 I woul welcome it if he would share the way how to do it... I woul be also glad if someone could tell me how to go around the failsafe which restores the factory recovery on normal boot for this device.
Info: I'm on OOS, Android P, on a OnePlus 6. I've never rooted my phone before.
I've tried flashing TWRP onto my phone like a hundred times. I was able to unlock the bootloader, but when I enter "fastboot boot twrp-3.2.3-0-enchilada.img" in Powershell, it says that it found my phone and whatnot, but when I try to boot to TWRP, it just takes me to the Qualcomm Crash Dump Mode. I can just turn off my phone from that point, then boot normally. I heard that there might be issues with flashing TWRP onto an Android P, and that I might have luck flashing blu_spark TWRP onto it instead, but I don't know how to do that. I know next to nothing about this stuff, so an ELI5 would be super helpful here. Thanks!
The command should be: fastboot flash recovery recoveryname.img
SoyHowlett said:
Info: I'm on OOS, Android P, on a OnePlus 6. I've never rooted my phone before.
I've tried flashing TWRP onto my phone like a hundred times. I was able to unlock the bootloader, but when I enter "fastboot boot twrp-3.2.3-0-enchilada.img" in Powershell, it says that it found my phone and whatnot, but when I try to boot to TWRP, it just takes me to the Qualcomm Crash Dump Mode. I can just turn off my phone from that point, then boot normally. I heard that there might be issues with flashing TWRP onto an Android P, and that I might have luck flashing blu_spark TWRP onto it instead, but I don't know how to do that. I know next to nothing about this stuff, so an ELI5 would be super helpful here. Thanks!
Click to expand...
Click to collapse
Ignore the last comment, it only works on non treble phones. You need to download the twrp blu spark edition as it is the only one that doesn't crash on boot. Visit the blu spark thread on roms kernels and other development and download blu spark img and zip. Then follow the rooting and twrp manual on xda.
Gionikva said:
Ignore the last comment, it only works on non treble phones. You need to download the twrp blu spark edition as it is the only one that doesn't crash on boot. Visit the blu spark thread on roms kernels and other development and download blu spark img and zip. Then follow the rooting and twrp manual on xda.
Click to expand...
Click to collapse
Thanks! This should fix it!
SoyHowlett said:
Info: I'm on OOS, Android P, on a OnePlus 6. I've never rooted my phone before.
I've tried flashing TWRP onto my phone like a hundred times. I was able to unlock the bootloader, but when I enter "fastboot boot twrp-3.2.3-0-enchilada.img" in Powershell, it says that it found my phone and whatnot, but when I try to boot to TWRP, it just takes me to the Qualcomm Crash Dump Mode. I can just turn off my phone from that point, then boot normally. I heard that there might be issues with flashing TWRP onto an Android P, and that I might have luck flashing blu_spark TWRP onto it instead, but I don't know how to do that. I know next to nothing about this stuff, so an ELI5 would be super helpful here. Thanks!
Click to expand...
Click to collapse
I had also the same problem... There is only one way.. install twrp blu spark. Oy this img can be installed as recovery on android pie.. after installing blu spark
Open twrp recovery and install the twrp installer zip file
Okay so yesterday I decided to finally try to install TWRP to flash a custom rom on the system, but never thought it would give so much headache. My drivers were bad, the system locked and android 11 updating making the phone all sorts of bugs, I was anxious to get rid of it, and I did somehow. I was unable to flash TWRP into the recovery as the system partition type is different than usual for it seems, but the recovery partition was all weird, "no command" was stuck in the screen even after a hard reset through there. So I got Magisk and got Root and used Smart Flash to install TWRP through the running system and it landed successful. But when going to the recovery the TWRP screen was flickering, but I could send ADB commands yet and boot normally, I just couldn't access the recovery functions yet. So I flashed a different version of the TWRP with the IMG and the zip folder and nothing worked then I realized that maybe I should erase the partition before flashing it and then the murder. I found a tutorial on erasing stuff, but the whole process cost me more than twelve hours as I messed with so many things and was kinda learning the hows and dos.
But then I saw the command "fastboot erase system -w" that was a shortcut for all cleanup processes and I was wanting to wipe it again even to recover my google backup and be able to use my messenger apps. But it did erase, of course, the whole system and everything, simply destroying everything, but yet stuck in the fastboot screen. What I did? Well, I downloaded the TGRZ of an older version of xiaomi mi a3 firmware, the android 10, as I was tired and thought that maybe if I downgraded it I would get my phone to get rid of android 11 bugs and sleep for good till tomorrow, that is today. I ran the script to wipe anything and install the system over it and it did successfully, then the message "successfully installed, press any key to finish" but then the prompt closed and the phone tried to reboot but fell into a hard brick. The computer recognizes the device as the name "QUSB_BULK_CID:0411_SN:EFCF04FD" and the hardware ID "USB\VID_05C6&PID_9008" matches the original.
So is there anything I could do yet? Phone warranty ended in january and that's why I tried that process, it is any worth?
BillyWroth said:
Okay so yesterday I decided to finally try to install TWRP to flash a custom rom on the system, but never thought it would give so much headache. My drivers were bad, the system locked and android 11 updating making the phone all sorts of bugs, I was anxious to get rid of it, and I did somehow. I was unable to flash TWRP into the recovery as the system partition type is different than usual for it seems, but the recovery partition was all weird, "no command" was stuck in the screen even after a hard reset through there. So I got Magisk and got Root and used Smart Flash to install TWRP through the running system and it landed successful. But when going to the recovery the TWRP screen was flickering, but I could send ADB commands yet and boot normally, I just couldn't access the recovery functions yet. So I flashed a different version of the TWRP with the IMG and the zip folder and nothing worked then I realized that maybe I should erase the partition before flashing it and then the murder. I found a tutorial on erasing stuff, but the whole process cost me more than twelve hours as I messed with so many things and was kinda learning the hows and dos.
But then I saw the command "fastboot erase system -w" that was a shortcut for all cleanup processes and I was wanting to wipe it again even to recover my google backup and be able to use my messenger apps. But it did erase, of course, the whole system and everything, simply destroying everything, but yet stuck in the fastboot screen. What I did? Well, I downloaded the TGRZ of an older version of xiaomi mi a3 firmware, the android 10, as I was tired and thought that maybe if I downgraded it I would get my phone to get rid of android 11 bugs and sleep for good till tomorrow, that is today. I ran the script to wipe anything and install the system over it and it did successfully, then the message "successfully installed, press any key to finish" but then the prompt closed and the phone tried to reboot but fell into a hard brick. The computer recognizes the device as the name "QUSB_BULK_CID:0411_SN:EFCF04FD" and the hardware ID "USB\VID_05C6&PID_9008" matches the original.
So is there anything I could do yet? Phone warranty ended in january and that's why I tried that process, it is any worth?
Click to expand...
Click to collapse
You should never try to install software for another board (mi mix 3 global is codenamed "perseus")...
If you are unable to reach fastboot and recovery, you may refer to this, since it sounds like your phone is in EDL mode:
Reboot to EDL mode from FASTBOOT!
Reboot to EDL mode from FASTBOOT! No more Test Point Method needed Technical Details: Redmi Note 3 support rebooting to EDL in Android Bootloader aboot module (the "reboot-edl" command) but fastboot utility doesn't recognize "reboot-edl" in the...
forum.xda-developers.com
I never encountered this issue so only do this if you're absolutely sure you have no other means of flashing anything on it (i.e. through fastboot), and use the appropriate firmware at all times for your specific model
CriGiu said:
You should never try to install software for another board (mi mix 3 global is codenamed "perseus")...
If you are unable to reach fastboot and recovery, you may refer to this, since it sounds like your phone is in EDL mode:
Reboot to EDL mode from FASTBOOT!
Reboot to EDL mode from FASTBOOT! No more Test Point Method needed Technical Details: Redmi Note 3 support rebooting to EDL in Android Bootloader aboot module (the "reboot-edl" command) but fastboot utility doesn't recognize "reboot-edl" in the...
forum.xda-developers.com
I never encountered this issue so only do this if you're absolutely sure you have no other means of flashing anything on it (i.e. through fastboot), and use the appropriate firmware at all times for your specific model
Click to expand...
Click to collapse
well it seems I recovered it back, I bricked it and somehow it just got into EDL mode without cable or opening it up. So I found a tutorial back on reddit showing how use GFIL to install the stock rom back. I used android 10 stock rom before bricking it, but as I just flashed everything on empty partitions it didn't work, it seems that the Qualcomm setup needs some kind of previous work to set everything up. Anyways I managed to boot it, but now I'm aware that I should use Lineage recovery instead of TWRP as Mi A3 support is lacking, that's why after installing it I got it flickering (no compatible version with the latest Android 11 firmware).
BillyWroth said:
well it seems I recovered it back, I bricked it and somehow it just got into EDL mode without cable or opening it up. So I found a tutorial back on reddit showing how use GFIL to install the stock rom back. I used android 10 stock rom before bricking it, but as I just flashed everything on empty partitions it didn't work, it seems that the Qualcomm setup needs some kind of previous work to set everything up. Anyways I managed to boot it, but now I'm aware that I should use Lineage recovery instead of TWRP as Mi A3 support is lacking, that's why after installing it I got it flickering (no compatible version with the latest Android 11 firmware).
Click to expand...
Click to collapse
hello, im having maybe a similiar case with my phone (in this case its a MI A3) i installed "succefully" evolution x 6.3 on my phone and everthing was ok with a few bugs, the only problem was that mi cannot connect to internet, so i decided to restart the phone and now my phone just don't turn on, the power button don't respond and i cannot start up my phone and its just a black screen, if u remeber ¿can u pass the tutorial that u saw on reddit? maybe it can help me