Related
I rooted my phone and used firewater to get S-OFF (a lifesaver), then unfortunately installed a TWRP recovery that has completely messed up the device. It wouldn't respond at all and I was lucky enough to flash CWM when I got it back to bootloader. Now, at least I do have a recovery to work from.
I can't do a factory reset (just goes back to recovery), can't sideload a new ROM, and tried to flash a new boot.img and system.img from here:http://forum.xda-developers.com/showthread.php?t=2706233
None of these have worked and I'm at a loss in terms of what else I can do to get the phone working again. Any ideas????
Alex
Bump
Sent from my HTC One M8!
U WOT M8?
AP26322 said:
I rooted my phone and used firewater to get S-OFF (a lifesaver), then unfortunately installed a TWRP recovery that has completely messed up the device. It wouldn't respond at all and I was lucky enough to flash CWM when I got it back to bootloader. Now, at least I do have a recovery to work from.
I can't do a factory reset (just goes back to recovery), can't sideload a new ROM, and tried to flash a new boot.img and system.img from here:http://forum.xda-developers.com/showthread.php?t=2706233
None of these have worked and I'm at a loss in terms of what else I can do to get the phone working again. Any ideas????
Alex
Click to expand...
Click to collapse
Have you tried pushing back the stock recovery and then doing a factory reset?
droidkevlar said:
Have you tried pushing back the stock recovery and then doing a factory reset?
Click to expand...
Click to collapse
I have not. Where can I find the stock recovery?
AP26322 said:
I have not. Where can I find the stock recovery?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2708291
Stock recovery, boot and hboot are in there. I would start with the boot, then recovery, and then factory reset.
droidkevlar said:
http://forum.xda-developers.com/showthread.php?t=2708291
Stock recovery, boot and hboot are in there. I would start with the boot, then recovery, and then factory reset.
Click to expand...
Click to collapse
Thanks so much. Installed the boot, then recovery and it's back to working like a charm. Great to know all of these .imgs are in one place, too. You're a lifesaver!
http://forum.xda-developers.com/showthread.php?t=2708291
Try it.
AP26322 said:
Thanks so much. Installed the boot, then recovery and it's back to working like a charm. Great to know all of these .imgs are in one place, too. You're a lifesaver!
Click to expand...
Click to collapse
NP
It's possible this is also somewhere else, but I am having trouble finding it....so I gave up and figured I'd ask.
Okei. I started with TWRP 2.8.6.1. So from my understanding flashing a modem does not work in versions of TWRP newer than 2.8.6.0. I get that, and so I decided to downgrade. However, that seems to be the version that I am unable to get working. I've attempted to flash the 2.8.6.0 recovery via fastboot. Everything says it's good in my terminal. So I go ahead and boot into recovery, but my phone goes to a black screen for a moment and then reboots into OS. I tried a different method, via the app from the google play store. It tells me that there is an error of some sort, or that I already have it installed. So I used the google play app to install 2.8.6.1, which worked flawlessly. So now I am back where I started.
Is there some trick to getting specifically TWRP 2.8.6.0 working so that I am able to use it to flash a different modem? Will using an even earlier version yield the same results? Or am I better off doing it via fastboot?
Thank you for your time <3
Use philz recovery
Myrskyta said:
It's possible this is also somewhere else, but I am having trouble finding it....so I gave up and figured I'd ask.
Okei. I started with TWRP 2.8.6.1. So from my understanding flashing a modem does not work in versions of TWRP newer than 2.8.6.0. I get that, and so I decided to downgrade. However, that seems to be the version that I am unable to get working. I've attempted to flash the 2.8.6.0 recovery via fastboot. Everything says it's good in my terminal. So I go ahead and boot into recovery, but my phone goes to a black screen for a moment and then reboots into OS. I tried a different method, via the app from the google play store. It tells me that there is an error of some sort, or that I already have it installed. So I used the google play app to install 2.8.6.1, which worked flawlessly. So now I am back where I started.
Is there some trick to getting specifically TWRP 2.8.6.0 working so that I am able to use it to flash a different modem? Will using an even earlier version yield the same results? Or am I better off doing it via fastboot?
Thank you for your time <3
Click to expand...
Click to collapse
I too have experienced exactly what you describe and have yet to find a solution. I own 2 OPO's, plus I administer one for a friend who purchased one based on my recommendation. The oldest one I own which was purchased 4 months prior to the others has worked perfectly with any recovery or ROM I've installed on it. It has TWRP-2.8.6.0 installed and has no problems flashing any partition from recovery. My newer handset and my friend's both refuse to boot into recovery with that version installed. It doesn't matter if I flash from fastboot or from TWRP itself. I have no idea why this phenomena occurs on some of these devices, but it makes administering them a more time consuming pain in the ass. I'm going to try Phil's recovery, as was suggested, as a workaround, but I'm dumbfounded as to why the inconsistencies exhibit themselves on particular devices.
Odysseus1962 said:
I too have experienced exactly what you describe and have yet to find a solution. I own 2 OPO's, plus I administer one for a friend who purchased one based on my recommendation. The oldest one I own which was purchased 4 months prior to the others has worked perfectly with any recovery or ROM I've installed on it. It has TWRP-2.8.6.0 installed and has no problems flashing any partition from recovery. My newer handset and my friend's both refuse to boot into recovery with that version installed. It doesn't matter if I flash from fastboot or from TWRP itself. I have no idea why this phenomena occurs on some of these devices, but it makes administering them a more time consuming pain in the ass. I'm going to try Phil's recovery, as was suggested, as a workaround, but I'm dumbfounded as to why the inconsistencies exhibit themselves on particular devices.
Click to expand...
Click to collapse
Well....at least now I know I'm not totally crazy. Thank you~
=)
Ejvyas said:
Use philz recovery
Click to expand...
Click to collapse
Is there any particular reason for Philz recovery over standard CWM?
Also, while this might be a viable option my understanding is that, that would render my old backups useless since I was previously using TWRP? That's kind of unfortunate. =(
Myrskyta said:
Is there any particular reason for Philz recovery over standard CWM?
Also, while this might be a viable option my understanding is that, that would render my old backups useless since I was previously using TWRP? That's kind of unfortunate. =(
Click to expand...
Click to collapse
uploaded the file for you (Take out .apk extension), hope you know how to flash thru fastboot. Else google.
KSKHH said:
uploaded the file for you (Take out .apk extension), hope you know how to flash thru fastboot. Else google.
Click to expand...
Click to collapse
Unfortunately, if that is the same one from twrp's website it isn't going to do me any good. I already attempted that through fastboot. 2.8.6.1 works flawlessly. 2.8.6.0 seems to bootloop once and then toss me back into the OS. Thank you though, I appreciate it.
Had the same problem tried to flash back to 2.8.6.0 via TWRP and didn't work and seemed like recovery had disapeared so used TWRP App to install 2.8.6.1 booted into recovery then rebooted and tried to downgrade to 2.8.6.0 but got a message about same recovery, rebooted phone tried again and it installed no problem.
stylez said:
Had the same problem tried to flash back to 2.8.6.0 via TWRP and didn't work and seemed like recovery had disapeared so used TWRP App to install 2.8.6.1 booted into recovery then rebooted and tried to downgrade to 2.8.6.0 but got a message about same recovery, rebooted phone tried again and it installed no problem.
Click to expand...
Click to collapse
Hmm...maybe I'll give it another shot then. I had opted to just flash them via fastboot because I couldn't get it to work. It's not the worst thing ever. Thank you =)
Myrskyta said:
Is there any particular reason for Philz recovery over standard CWM?
Also, while this might be a viable option my understanding is that, that would render my old backups useless since I was previously using TWRP? That's kind of unfortunate. =(
Click to expand...
Click to collapse
just FYI, philz recovery does support TWRP backups. you just have to enable that feature in the settings
Oh! Thank you for letting me know. I'll keep that in mind. =)
Save yourself all that trouble, just flash modems with fastboot....fastboot flash modem modem.bin
Okay, many of us don't do this everyday but I flashed TWRP 3.0.2.0 on my OPO and needed to go back to 2.8.6.0 to use jgcaap's MM build.
So i tried flashing 2.8.6.0 img file from 3.0.2 and guess what happened? No. It didn't downgrade it self, instead I lost my recovery. My phone rebooted straight to system after being stuck on Bootlogo for a while. So I flash the recovery AGAIN via fastboot, flashify, RashR, Flashfire, Mobile Terminal whatever I could think of. But nope, same result whatsoever. Flashing other recoveries doesn't work either. Same errors return.
Then I thought of flashing 3.0.0.0 instead of 2.8.6.0 and yes, flashing 3.0.0.0 from 3.0.2.0 worked indeed. Then I started to download all the recovery files till 2.8.6.0 and started flashing them one after another, step by step climbing down the number and it kept downgrading but ONE version down at a time, if I try to skip it returns the same bs as before. Then flashing down until I reached 2.8.6.0 and then flashed that too via RashR. And surprise! Surorise! The recovery version I needed was not working. It would be flashed then the recovery would disappear and it would go into a no recovery state like before again. Then I'd flash 2.8.6.1 and get recovery back. And now finally after all the endeavor I'm on 2.8.6.1.
Anybody might know the reason of this stupid anomaly? And why it doesn't work?
And also why I can't flash ANY OTHER recovery?
Unnecessary screenshot attached :good: enjoy~
Tiash420 said:
Okay, many of us don't do this everyday but I flashed TWRP 3.0.2.0 on my OPO and needed to go back to 2.8.6.0 to use jgcaap's MM build.
So i tried flashing 2.8.6.0 img file from 3.0.2 and guess what happened? No. It didn't downgrade it self, instead I lost my recovery. My phone rebooted straight to system after being stuck on Bootlogo for a while. So I flash the recovery AGAIN via fastboot, flashify, RashR, Flashfire, Mobile Terminal whatever I could think of. But nope, same result whatsoever. Flashing other recoveries doesn't work either. Same errors return.
Then I thought of flashing 3.0.0.0 instead of 2.8.6.0 and yes, flashing 3.0.0.0 from 3.0.2.0 worked indeed. Then I started to download all the recovery files till 2.8.6.0 and started flashing them one after another, step by step climbing down the number and it kept downgrading but ONE version down at a time, if I try to skip it returns the same bs as before. Then flashing down until I reached 2.8.6.0 and then flashed that too via RashR. And surprise! Surorise! The recovery version I needed was not working. It would be flashed then the recovery would disappear and it would go into a no recovery state like before again. Then I'd flash 2.8.6.1 and get recovery back. And now finally after all the endeavor I'm on 2.8.6.1.
Anybody might know the reason of this stupid anomaly? And why it doesn't work?
And also why I can't flash ANY OTHER recovery?
Click to expand...
Click to collapse
Did you try flashing the recovery img via TWRP itself? And are you using any theme on TWRP 3.x.x.x?
Nope no themes and I tried flashing through every method I could think of but nope, doesn't work.
Tiash420 said:
Nope no themes and I tried flashing through every method I could think of but nope, doesn't work.
Click to expand...
Click to collapse
You don't need to be on TWRP 2.8.6.0 to flash jgcaap MM build. Just use 3.0.2.0 it flashes modem and does everything the older one you're trying to get to can do.
Sent from my A0001 using Tapatalk
Renosh said:
You don't need to be on TWRP 2.8.6.0 to flash jgcaap MM build. Just use 3.0.2.0 it flashes modem and does everything the older one you're trying to get to can do.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I get the notification quick settings bug, I mean, I can't get quick setting toggles directly from notification nor can I have a regular basic swipe lock screen. And the bugs persist no matter which ever recovery I'm flashing through and with or without Gapps. How do I get pass that? Meanwhile my friend on the other hand downloaded the same version from the same place and he doesn't face those bugs. :'| Why is this happening to me?
Tiash420 said:
I get the notification quick settings bug, I mean, I can't get quick settings directly from notification nor can I have a regular basic swipe lock screen. And the bugs persist no matter which ever recovery I'm flashing through and with or without Gapps. How do I get pass that?
Click to expand...
Click to collapse
I've been seeing mentions of flashing 21/4 build first set it up then dirty flash latest update. I also got the same issue when I last flashed jgcaap MM ROM. It would have been best to just ask for advise there than assume it's a recovery issue
Sent from my A0001 using Tapatalk
Renosh said:
I've been seeing mentions of flashing 21/4 build first set it up then dirty flash latest update. I also got the same issue when I last flashed jgcaap MM ROM. It would have been best to just ask for advise there than assume it's a recovery issue
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I'll thank my friends who owned the OPO before I did for the recovery 'assumptions' :|
Tiash420 said:
I'll thank my friends who owned the OPO before I did for the recovery 'assumptions' :|
Click to expand...
Click to collapse
I'm guessing they insisted because of the previous problems with flashing modems for TWRP. Flash the latest 3.0.2.0 and I guarantee it'll work for every ROM only issue that still exists is if you want encryption on CM13 and that's present on all current TWRP versions
Sent from my A0001 using Tapatalk
Renosh said:
I'm guessing they insisted because of the previous problems with flashing modems for TWRP. Flash the latest 3.0.2.0 and I guarantee it'll work for every ROM only issue that still exists is if you want encryption on CM13 and that's present on all current TWRP versions
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Well doesn't matter, I flashed Sultan's unofficial CM13 build via Kumajaya's TWRP 3.0.0.0 and it works fabulously! jgcaap can wait, I'm sure it's not much different in features and stuff! :3
Last night i decided it was finally time to root and put recovery onto my shield tablet. everything went smoothly that is untill i tried to boot into recovery (TWRP) everytime i try to enter recovery there's a picture of a dead android with a triangle on him with the words "no command" ...the only way i've been able to get back into recovery is to flash the image again. but once i leave twrp it's gone again. does anyone have any suggestions please. if you need more information, let me know
Thanks
Habbz said:
Last night i decided it was finally time to root and put recovery onto my shield tablet. everything went smoothly that is untill i tried to boot into recovery (TWRP) everytime i try to enter recovery there's a picture of a dead android with a triangle on him with the words "no command" ...the only way i've been able to get back into recovery is to flash the image again. but once i leave twrp it's gone again. does anyone have any suggestions please. if you need more information, let me know
Thanks
Click to expand...
Click to collapse
You unlocked your bootloader before, right?
seems the original recovery is working, and not twrp.
after boot loader unlock you flashed TWRP via fastboot?
Yeah first thing i did was unlock the bootloader , then proceeded to root. i've installed a custom rom too ( Lineage os)...but i just can't seem to get into TWRP when rebooting , even with the button combo. the files for TWRP are on my tablet but i just can't access it. i followed this guide
http://nvidiashieldzone.com/shield-...shmallow/root-shield-tablet-v1-marshmallow-2/
Habbz said:
Yeah first thing i did was unlock the bootloader , then proceeded to root. i've installed a custom rom too ( Lineage os)...but i just can't seem to get into TWRP when rebooting , even with the button combo. the files for TWRP are on my tablet but i just can't access it. i followed this guide
http://nvidiashieldzone.com/shield-...shmallow/root-shield-tablet-v1-marshmallow-2/
Click to expand...
Click to collapse
Don t know how old the twrp is? Can t try it now, cause our web protection blocked the site.
I use always the last recovery from official twrp site
https://twrp.me/devices/nvidiahshieldtablet.html
Steps.
-bootloader unlock.
-'fastboot flash recovery /place/of/your/recovery'
after that you can flash custom roms and/or root with supersu or magisk..
If you did not start TWRP, how could you flash linageos?
wiQbold said:
Don t know how old the twrp is? Can t try it now, cause our web protection blocked the site.
I use always the last recovery from official twrp site
https://twrp.me/devices/nvidiahshieldtablet.html
Steps.
-bootloader unlock.
-'fastboot flash recovery /place/of/your/recovery'
after that you can flash custom roms and/or root with supersu or magisk..
If you did not start TWRP, how could you flash linageos?
Click to expand...
Click to collapse
Once i flashed TWRP it automatically put me into it after a few seconds, but then when i rebooted or asked to be put into recovery it gave me the no command line, the version of TWRP was old and i just installed the latest one like you mentioned and now it's working again. thanks for replying though, it might help someone else out in the same position.
Just one last question, do i need Xposed for Magisk ? i'm on nougat and haven't seen much about it apart from an unnoficial release.
Habbz said:
Once i flashed TWRP it automatically put me into it after a few seconds, but then when i rebooted or asked to be put into recovery it gave me the no command line, the version of TWRP was old and i just installed the latest one like you mentioned and now it's working again. thanks for replying though, it might help someone else out in the same position.
Just one last question, do i need Xposed for Magisk ? i'm on nougat and haven't seen much about it apart from an unnoficial release.
Click to expand...
Click to collapse
maybe you wait for official xposed. what modules are you looking for?
there are many alternatives and/or magisk modules that can do some work ..
I only missed gravitybox cause of customisation of the statusbar and xprivacy..
don t tried the early xposed, cause there is no need for me.
but your problem was solved? good
wiQbold said:
maybe you wait for official xposed. what modules are you looking for?
there are many alternatives and/or magisk modules that can do some work ..
I only missed gravitybox cause of customisation of the statusbar and xprivacy..
don t tried the early xposed, cause there is no need for me.
but your problem was solved? good
Click to expand...
Click to collapse
I'm looking for one that can play remote play, heard it uses Magisk , i'm not too sure though, yeah it's been solved thanks.
Hi,
I have a VZW Quark that's been unlocked with Sunshine and rooted and running fine on custom ROM's for a year. Today I did a factory reset and complete wipe and reinstalled RR Rom and GApps etc. However, on reboot, it only goes back to recovery (TWRP 3.1.1-0). I faced this the last time as well and managed to find the fix by googling it but can't seem to get to it now. It was a quick fix and then it booted to system fine and I cannot remember it. Can anyone help! Thanks.
Rikhit said:
Hi,
I have a VZW Quark that's been unlocked with Sunshine and rooted and running fine on custom ROM's for a year. Today I did a factory reset and complete wipe and reinstalled RR Rom and GApps etc. However, on reboot, it only goes back to recovery (TWRP 3.1.1-0). I faced this the last time as well and managed to find the fix by googling it but can't seem to get to it now. It was a quick fix and then it booted to system fine and I cannot remember it. Can anyone help! Thanks.
Click to expand...
Click to collapse
Someone else had this issue and they solved it by flashing the latest @bhb27 modded TWRP. You say you have TWRP 3.1.1, but is it from the TWRP website or from @bhb27? Flash this one below to make sure.
twrp-3.1.1-mod_2-quark.img
https://androidfilehost.com/?w=files&flid=39562
Once they flashed it, they were able to boot to system, then they booted back to TWRP (on purpose) -- and then upon subsequent reboots everything was fine.
See here:
mpro420 said:
@bhb27 Im face a problem, since I do a clean install build 08/23, when my phone restart, it always boot into TWRP, and I need to boot to bootloader and press START to start system normally.
Maybe Im doing something worng due the install process, (full wipe include internal storage, flash Crdroid, flash Gapps, reboot), I try to flash boot.img and new TWRP 3.1.1 recovery.img, but got a same results.
Please help, thanks a lot.
我從使用 Tapatalk 的 DROID Turbo 發送
Click to expand...
Click to collapse
bhb27 said:
You may not be using the TWRP made by me, check TWRP thread and use the twrp-3.1.1-mod_2-quark.img version that is in the afh mirror folder if you are not using that... also try to update the ROM as 8/23 is one month old on updates...
Click to expand...
Click to collapse
mpro420 said:
Thank you!!
After flash the TWRP 3.1.1-mod 2, my phone booting is back to normal. :good
ps: I want to donate to your hard work, but I dont had a Paypal account, its there other way I can buy you a beer?
我從使用 Tapatalk 的 DROID Turbo 發送
Click to expand...
Click to collapse
bhb27 said:
Mod TWRP can cleanup the "android to recovery commands" the process was changed in nougat and official or old version don't have the new support...
From outside of Brazil that is the only option that I can received and use what I have received...
:good:
Click to expand...
Click to collapse