Related
[Q]
Hi,
I have nexus s GRJ22 Android 2.3.4 I904. I tried rooting it using clockwork and super user but after doing that when i reboot It stays in the google logo. I could find that i was not able to mount system in the clockwork recovery with means that its not having sufficient permissions .
1. Factory reset - not working
2. Tried fixing permissions - not working
3. tried remounting - not working
what i'm possible to do is get into fastboot mode and clockwork recovery mode and in the normal booting it stays at the google logo.
with this i can say i messed up something when i was rooting. and the phone is useless now.
The last option i know now is fastboot flashing of all the images (boot, system, recovery). How to flash everything finally and bring it back to the state which I got from the factory?
I'm looking for if any one has theses images so that I can fastboot flash it and bring it back in an operating condition.
I'm new to android development, android devices and a noob.
Please do ask If you guys need any more info.
I appreciate any answers and thanks for reading my question.
First, make sure that ClockWorkMod recovery that you installed is the right version for your NS model (sorry but I don't know what the "I904" means)
After you flashed the correct recovery then I'd suggest you go to this thread and see if there is a full OTA package for your NS model. If there is one then you can download it, connect your phone to a PC, mount SD card from the recovery, copy the package over then flash it. That should bring your NS back to life.
If there is no OTA package for your model then you can search/ask for a stock nandroid backup of your phone model. It's most likely that someone has already posted it here in xda.
suksit said:
First, make sure that ClockWorkMod recovery that you installed is the right version for your NS model (sorry but I don't know what the "I904" means)
After you flashed the correct recovery then I'd suggest you go to this thread and see if there is a full OTA package for your NS model. If there is one then you can download it, connect your phone to a PC, mount SD card from the recovery, copy the package over then flash it. That should bring your NS back to life.
If there is no OTA package for your model then you can search/ask for a stock nandroid backup of your phone model. It's most likely that someone has already posted it here in xda.
Click to expand...
Click to collapse
Thanks for the reply.
its not I904 I'm sorry its I9020 which is the model number of the phone.
I tried the link that you had posted already but it stops at getprop function in the script when i do the update and says status 7 error and the update fails because the /system is not mounting.
Kindly suggest me to bring this phone back.
Hmm, I still have the impression that you have the incorrect version of CWM. What is your service provider? As far as I remember, the I9020T and I9020A require a different version of CWM. And also what is the version of CWM installed?
If you've got the I9020T, try installing this one (from kouch's site)
But if you've got the I9020A, you should try the recovery from this guide (Part 3 - Recovery)
Sorry for the delayed response ,
I have the Tmobile carrier and its I9020T. The version of CWR is 3.0.2.4 which is running. As i said before its not monting the /system.
any other options that I have. ?
Please suggest
Thanks for your time..
I got the nandroid for GRJ22 I9020T.
I'm unable to fastboot flash boot boot.img from this ROM.
it says FAILWrite..
also tried to do the same way for system.img it says Invalid Magic Code !
thankyou suksit I recovered the ROM link that u had posted. I pushed using the adb on to the sdcard and installed from the CWR. I had tried that initially but had not worked.. but now it worked perfectly..
thanks KUDOS..
rakeshpatil1983 said:
thankyou suksit I recovered the ROM link that u had posted. I pushed using the adb on to the sdcard and installed from the CWR. I had tried that initially but had not worked.. but now it worked perfectly..
thanks KUDOS..
Click to expand...
Click to collapse
Glad you made it!
Well.. Its been 2 days it got bricked..
I still dont understand why it did not get it rooted even after i used the right CWR and superuser .. ?
Now i wont try for a while as i'l be on a vacation to India and I will need my phone..
rakeshpatil1983 said:
Well.. Its been 2 days it got bricked..
I still dont understand why it did not get it rooted even after i used the right CWR and superuser .. ?
Now i wont try for a while as i'l be on a vacation to India and I will need my phone..
Click to expand...
Click to collapse
your phone was never bricked. bricked means itll never ever work again. if your planning on using it later and using it now, then bricked is definitely not the right word to use ;-)
well then its appropriate to say
"It was broken for two days"
nexus S was in locked state...can't able to unlock thorugh "fastboot oem unlock" (FAILED <remote:ERASE FAIL>.. even all drivers were installed properly...if i try to get in to recovery mode there is an exclamtion mark...what it that..??? plzzzz help me with this
Ive been trying to fix this for two days. This post is a last resort. Ive searched the forum and tried what little I found.
Ive trashed phones and had to fix them but never seen this.
I finally got root on this thing and was flashing CM10 but kept seeing "failed" using TWRP so decided id flash
CWM and give it a try. Once,still TWRP Twice,still TWRP. Third, Black recovery screen then skip to normal boot.
Fourth try it read "error: cannot load 'openrecovery-twrp-2.3.1.0-evita'" and has since with both recoveries.
No access with volume/power method. No access from command prompt. No access through Quick Boot , Rom Toolbox,
etc.
If I posted this wrong Im sorry. I can usually fix these things myself but Im waving the white flag on this one.
I tried adb help but everything I tried said failed. Any help would be greatly appreciated.
ksflat43 said:
Ive been trying to fix this for two days. This post is a last resort. Ive searched the forum and tried what little I found.
Ive trashed phones and had to fix them but never seen this.
I finally got root on this thing and was flashing CM10 but kept seeing "failed" using TWRP so decided id flash
CWM and give it a try. Once,still TWRP Twice,still TWRP. Third, Black recovery screen then skip to normal boot.
Fourth try it read "error: cannot load 'openrecovery-twrp-2.3.1.0-evita'" and has since with both recoveries.
No access with volume/power method. No access from command prompt. No access through Quick Boot , Rom Toolbox,
etc.
If I posted this wrong Im sorry. I can usually fix these things myself but Im waving the white flag on this one.
I tried adb help but everything I tried said failed. Any help would be greatly appreciated.
Click to expand...
Click to collapse
First off stick with twrp cwm is not officially supported on our device and can blank your SD card...can you link me to the cm ROM you were trying to flash it was for our phone not the international one x right?
tactical kitten said:
First off stick with twrp cwm is not officially supported on our device and can blank your SD card...can you link me to the cm ROM you were trying to flash it was for our phone not the international one x right?
Click to expand...
Click to collapse
Thanks for the reply. Ive got the link. first thing I see wrong is it says endeavoru and mine says evita I believe. The CM10 wouldnt install so I
tried flashing CWM recovery and here we are. Heres the link.
Thanks again.
Well, I cant send you the link. It says new users cant post outside links. Sorry. Its from the CM website. Dated 2012-01-07
ksflat43 said:
Thanks for the reply. Ive got the link. first thing I see wrong is it says endeavoru and mine says evita I believe. The CM10 wouldnt install so I
tried flashing CWM recovery and here we are. Heres the link.
Thanks again.
Well, I cant send you the link. It says new users cant post outside links. Sorry. Its from the CM website. Dated 2012-01-07
Click to expand...
Click to collapse
Ok so corrct me if im wrong the cm10 you're trying to install says endeavoru? That's the intl one x not ours....we have the evita like you stated so you're lucky the build prop check is there or if it successfully flashed you'd be bricked...stay in our forum and you'll be fine...now here are your stepsinstall twrp through fastboot
Move the Rom of you're choice onto your phone(mount in twrp)
If you're on hboot 1.14 you have to flash boot.omg seperately
Wipe data system and cache install Rom enjoy...
You may have to format your sd if cwm corrupted it
tactical kitten said:
Ok so corrct me if im wrong the cm10 you're trying to install says endeavoru? That's the intl one x not ours....we have the evita like you stated so you're lucky the build prop check is there or if it successfully flashed you'd be bricked...stay in our forum and you'll be fine...now here are your stepsinstall twrp through fastboot
Move the Rom of you're choice onto your phone(mount in twrp)
If you're on hboot 1.14 you have to flash boot.omg seperately
Wipe data system and cache install Rom enjoy...
You may have to format your sd if cwm corrupted it
Click to expand...
Click to collapse
I cant install through fastboot. I get the "error cant load" message i talked about in the first post. It wont let me near recovery
if u can get in to fastboot but not in to twrp youll probly have to relock your bootloader and ruu back to stock
Reflash twrp 2.3.3.1 for evita in fastboot, also run fastboot erase cache. If your nandroid was made with cwm it wont work with twrp.
Anybody figure out how to fix this? I can find people having this problem flashing 4.4 but I can't flash anything. I've tried to flash mf1 firmware, a 4.3 carbon nightly, and a 4.3 pac nightly. All with the same results. Here is exactly what I did -
I flashed PhilZ recovery earlier on a earlier version of TWRP.
kept getting a "failed" in PhilZ
Flashed latest TWRP via Odin
Tried flashing the above mentioned zips all with the error message.
Restored my hyper drive rls16 backup (4.1.2)
Installed latest TWRP via goomanager app
Edit : my phone is flashed to PagePlus so I kinda have to be careful I'm afraid of using Odin to go back to stock/rooted but my luck that's what it'll take. When I get home I'm going to try it with a older version of TWRP that's the only other thing I can think to try.
Any suggestions or info is appreciated.
delete
anyone ? please ?
Supposedly the update binary here is generic, you could try replacing the one in the rom zip with it
http://forum.xda-developers.com/showthread.php?t=2492496
Sent from my SCH-I535 using XDA Premium 4 mobile app
I've tried CWM PhilZ and TWRP all latest versions, and still can't get rid of this.
I Cannot install any rom, whatsoever. I did manage to install a MF1 radio zip, but that's it. I can't install 4.3 or even 4.2 ..
I've replaced the update-binary inside the zips, and edited the update-script and removed the stuff used for recognizing the device, still no dice ..
I ended up flashing a full mf1 img via Odin and then used casual to root/unlock/recovery install - and I STILL get the error. Not sure where to go from here. Seems like nobody else is having this problem unless they're not on the latest recovery and trying to flash KitKat.
Thought I'd share the rest of my story ..
edit: I was able to restore a old backup of 1.7 carbon ...lol. better than nothing or a TW rom, that's for sure.
When you replaced the update binary did you get the same error or a different one? Also, have you tried flashing from internal and external SD?
Sent from my SCH-I535 using XDA Premium 4 mobile app
dpeeps74 said:
When you replaced the update binary did you get the same error or a different one? Also, have you tried flashing from internal and external SD?
Sent from my SCH-I535 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sorry I didn't get a notification for this.
I did get the same error. I did get a error 6 once or twice but it was because I edited the update-script file and used word or word pad I downloaded note++ and it stopped and went back to error 7 :banghead:
Sent from my SCH-I535 using Tapatalk
cjmcsw87 said:
Sorry I didn't get a notification for this.
I did get the same error. I did get a error 6 once or twice but it was because I edited the update-script file and used word or word pad I downloaded note++ and it stopped and went back to error 7 :banghead:
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
OK, I have one for you to try, use the original rom zip (don't edit the update-script), when you flash in recovery and it failed, select boot and boot back into recovery, then reflash again. Try it with the latest TWRP 2.6.3.2.
SOLVED ! only took a week ...
I had been using an update-binary file that was posted in a thread.
I took the file from PhilZ recovery ( which I had been able to flash, just nothing else ) and used that one. Imagine that, it worked.
**DUH** :silly:
cjmcsw87 said:
SOLVED ! only took a week ...
I had been using an update-binary file that was posted in a thread.
I took the file from PhilZ recovery ( which I had been able to flash, just nothing else ) and used that one. Imagine that, it worked.
**DUH** :silly:
Click to expand...
Click to collapse
Nice, glad you have a happy ending!!
buhohitr said:
Nice, glad you have a happy ending!!
Click to expand...
Click to collapse
Me too buddy, let me tell ya ..
I appreciate the advice along the way. Thank you.
now I just have to decide if I want carbon or pac as my daily driver for awhile.. Carbon is what i've almost always used after I figured out how bloated and laggy TW is.. Best of all my PagePlus flash is perfectly fine, didn't have to add APN's or mess with anything else to get data to work.
I hope this thread helps somebody else.
I am having the same issue with HTC One.
Could you please let me know how you solved this. Maybe it can help with my device as well. had no luck in our threds..
Thank you
umka83 said:
I am having the same issue with HTC One.
Could you please let me know how you solved this. Maybe it can help with my device as well. had no luck in our threds..
Thank you
Click to expand...
Click to collapse
If you're getting a status 7 error you have to replace the update binary with the latest nightly from cm11 in anything you want to flash. The update binary is universal and will work on anything you want to flash. If it is throwing another error then this won't work.
This will probably only work with cwm or philz.
BadUsername said:
If you're getting a status 7 error you have to replace the update binary with the latest nightly from cm11 in anything you want to flash. The update binary is universal and will work on anything you want to flash. If it is throwing another error then this won't work.
This will probably only work with cwm or philz.
Click to expand...
Click to collapse
Hello, thanks for reply,
1) I am not getting a STATUS 7 error, only this one:
Code:
E: eror eexecuting updater binary in zip /sdcard/zipfilename.zip Error flashing zip /sdcard/zipfilename Updating partition details Failed
Could you please let me know how can I replace the update binary with the latest nightly from cm11? Do you need to open zip from latest Nities and put it into my ZIP?
2) I have tried both cwm or philz and I am getting this error
Code:
this package is for m7wlj devices this is dlx
My device is m7wlj for sure. But somehow recovery thinks it is DLX
THANK YOU
umka83 said:
Hello, thanks for reply,
1) I am not getting a STATUS 7 error, only this one:
Code:
E: eror eexecuting updater binary in zip /sdcard/zipfilename.zip Error flashing zip /sdcard/zipfilename Updating partition details Failed
Could you please let me know how can I replace the update binary with the latest nightly from cm11? Do you need to open zip from latest Nities and put it into my ZIP?
2) I have tried both cwm or philz and I am getting this error
Code:
this package is for m7wlj devices this is dlx
My device is m7wlj for sure. But somehow recovery thinks it is DLX
THANK YOU
Click to expand...
Click to collapse
It's a recovery version problem, so either update your recovery or use an older one until you find something that works.
Problem Solved
umka83 said:
Hello, thanks for reply,
1) I am not getting a STATUS 7 error, only this one:
Code:
E: eror eexecuting updater binary in zip /sdcard/zipfilename.zip Error flashing zip /sdcard/zipfilename Updating partition details Failed
Could you please let me know how can I replace the update binary with the latest nightly from cm11? Do you need to open zip from latest Nities and put it into my ZIP?
2) I have tried both cwm or philz and I am getting this error
Code:
this package is for m7wlj devices this is dlx
My device is m7wlj for sure. But somehow recovery thinks it is DLX
THANK YOU
Click to expand...
Click to collapse
After conducting my own research with this same problem I discovered a much simpler method of correcting the issue. When flashing KK roms with older versions of custom recoveries, the recoveries did not have sufficient instructions to to handle some of the file system changes in KK. I tried replacing the updater binaries from multiple ROMs to no avail. After about 24 hours of trial and error I managed to successfully flash Cyanogenmod cm-11-20140709-NIGHTLY-d801 and GAPPs aokp_gapps-kk-20140517 to my LG G2 D801. All that had to be done is to update TWRP from 2.6.3.2 to version 2.7.1. This version of TWRP had the necessary instructions to support a KK version custom ROM.
Good Job
Sent from my SM-G900F using XDA Free mobile app
Fixed
buhohitr said:
Nice, glad you have a happy ending!!
Click to expand...
Click to collapse
I had same issue, installed newest TWRP. Fixed! Used Odin to install.
I had the same issue as the OP. I was trying to flash a rom from the external SD card. I moved it to the Internal SD and it worked.
J
can someone send the stock recovery image for the 16gb wifi version please? cwm is not letting me flash at all for some reason. got my tablet working (not on loop anymore), but wifi stops working every 3 minutes or so (even though it says its still connected). anybody run into this problem ? at any rate hoping to flash via original recovery to the latest update... any help appreciated.
johnnobts said:
can someone send the stock recovery image for the 16gb wifi version please? cwm is not letting me flash at all for some reason. got my tablet working (not on loop anymore), but wifi stops working every 3 minutes or so (even though it says its still connected). anybody run into this problem ? at any rate hoping to flash via original recovery to the latest update... any help appreciated.
Click to expand...
Click to collapse
I have not seen the stock recovery.img posted anywhere. But you can flash the OTAs via CWM. Go to post #20 here > http://forum.xda-developers.com/shi...ery-cwm-recovery-nvidia-shield-t2848064/page2
johnnobts said:
can someone send the stock recovery image for the 16gb wifi version please? cwm is not letting me flash at all for some reason. got my tablet working (not on loop anymore), but wifi stops working every 3 minutes or so (even though it says its still connected). anybody run into this problem ? at any rate hoping to flash via original recovery to the latest update... any help appreciated.
Click to expand...
Click to collapse
Here is the stock recovery, extracted from link in this thread >http://forum.xda-developers.com/nvidia-shield/general/shield-tablet-source-factory-t2840406
Note that I haven't tested it. Try it at your own risk. Fastboot flash....
Edit: tested and found not working. Removed.
I make a back up of the stock recovery in flashify but I don't now how to share in a mesege , some one explain me how please thanks
Sent from my SHIELD Tablet using XDA Free mobile app
rene130313 said:
I make a back up of the stock recovery in flashify but I don't now how to share in a mesege , some one explain me how please thanks
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Use a web browser instead of the XDA app. When you create or reply to a message, you will see several "buttons" at the top. One of them is a paperclip icon. Click on that one to attach a file.
rene130313 said:
I make a back up of the stock recovery in flashify but I don't now how to share in a mesege , some one explain me how please thanks
Sent from my SHIELD Tablet using XDA Free mobile app
Click to expand...
Click to collapse
Would you mind attaching a copy of your recovery.img?
Looks like they have the stock images up now @ nvidia.
https://developer.nvidia.com/develop4shield#tablet-osr
phobic99 said:
Looks like they have the stock images up now @ nvidia.
https://developer.nvidia.com/develop4shield#tablet-osr
Click to expand...
Click to collapse
Unfortunately, you need to be a registered developer to download.
Stock recovery attached. Confirmed working on my device.
cam30era said:
Stock recovery attached. Confirmed working on my device.
Click to expand...
Click to collapse
Is this recovery compatible with the LTE version?
dgjenkins said:
Is this recovery compatible with the LTE version?
Click to expand...
Click to collapse
I don't know. I wouldn't use it without assurance from someone who knows for sure. Sorry I can't help more.
just register as a developer, no strings attached, just create an account and you can download all os recovery images
i moved up all the way to 2.2.1, then reinstalled 1.2.1 because i wasn't liking lollipop
also unlocked the bootloader, flashed CWM and rooted
now i want to try the BitO kernel, which is only available to 2.2.1, so installed the 2.1 update (through CWM, as i forgot to flash the stock recovery for 1.2.1)
now i try to install 2.2, but recovery gives me an error
flashed CWM again, doesn't want to flash the OTA
flashed the 2.1 stock recovery, it starts the update but almost immediately gives me an error
yes i could flash the 2.2.1 OS recovery image, but then i would lose all my data....
EDIT: never mind, fixed it, flash boot.img, recovery.img, erased system, flashed system img, all from 2.1 update zip file, reboot, now 2.2 is installing through OTA
JarlSX said:
just register as a developer, no strings attached, just create an account and you can download all os recovery images
i moved up all the way to 2.2.1, then reinstalled 1.2.1 because i wasn't liking lollipop
also unlocked the bootloader, flashed CWM and rooted
now i want to try the BitO kernel, which is only available to 2.2.1, so installed the 2.1 update (through CWM, as i forgot to flash the stock recovery for 1.2.1)
now i try to install 2.2, but recovery gives me an error
flashed CWM again, doesn't want to flash the OTA
flashed the 2.1 stock recovery, it starts the update but almost immediately gives me an error
yes i could flash the 2.2.1 OS recovery image, but then i would lose all my data....
EDIT: never mind, fixed it, flash boot.img, recovery.img, erased system, flashed system img, all from 2.1 update zip file, reboot, now 2.2 is installing through OTA
Click to expand...
Click to collapse
Just curious, what was it about 2.2.1 that you didn't like? What was wrong with lolipop?
i prefered the way the notification pulldown worked in KK, some settings were quicker to reach
not too fond of the navigation buttons either
it's weird i know, they're in the same location, have the same function, but they just look wrong
look too much like the symbols on a Playstation controller
and GameGuardian doesn't work on Lollipop (yet), but by going back to KK i managed to fix what i wanted to fix
i hope nvidia gets it right this time with the 5.1 update, disabling swap would be nice
hmm, seems lag isn't gone at all...
was playing a bit of Sky Force 2014 yesterday, holy crap the lag
also noticed other apps were lagging
sure hope 5.1 will fix this
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