Related
Can someone help me with me problem?
I have a Nexus 4, its currently running 4.3 & want to update to 4.4 without loosing my data.
Its a stock 4.3 ROM, but my device has the bootloader unlocked, rooted & has Franco kernel installed along with TWRP recovery.
Recently, I've been getting the notification that 4.4 update is ready to install. I click ok & the phone re-boots into TWRP, after a few seconds the screen goes back to the main TWRP menu without installing the update.
So, I downloaded the latest factory image from here: https://developers.google.com/android/nexus/images (Android 4.4 (KRT16S)) & extracted the 'image-occam-krt16s.zip' file from the 'occam-krt16s-factory-2006f418.tgz' download. I then booted into TWRP > Advanced > ADB Sideload.
and ran the following command from adt sdk tools: 'adb sideload image-occam-krt16s.zip'. This sent the zip file to the phone (took about ~1 minute) & the update started but failed almost straight away.
This is the error message I got:
Can anyone point me in the right direction why 4.4 wont install?
Thanks.
Thats not how it works. The factory image zip is not flashable...it contains the imgs for flashing via fastboot, not a recovery.
You can get the flashable ota zips from here: http://forum.xda-developers.com/showthread.php?t=2145848
The ones found on that thread can be adb sideloaded.
Thanks for the update.
So, according to the link you provided I need to wipe everything & revert back to stock.
So, there's no way to install 4.4 if I have TWRP & custom kernel installed?
cmberry20 said:
Thanks for the update.
So, according to the link you provided I need to wipe everything & revert back to stock.
So, there's no way to install 4.4 if I have TWRP & custom kernel installed?
Click to expand...
Click to collapse
No there is a way. Download the ota zip from that page and flash via TWRP. It should work, assuming that you are currently on 4.3 JWR66Y.
Chromium_ said:
Thats not how it works. The factory image zip is not flashable...it contains the imgs for flashing via fastboot, not a recovery..
Click to expand...
Click to collapse
Not saying your wrong but theres a ton of links showing you how to install the factory image via adb sideloading.
http://phandroid.com/2013/11/21/dow...d-4-4-kitkat-krt16s-ota-directly-from-google/
http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
http://www.androidpolice.com/2013/1...16s-ota-manually-root-or-unlock-not-required/
What gives??
Chromium_ said:
No there is a way. Download the ota zip from that page and flash via TWRP. It should work, assuming that you are currently on 4.3 JWR66Y.
Click to expand...
Click to collapse
Thanks, I'll give that a go.
cmberry20 said:
Not saying your wrong but theres a ton of links showing you how to install the factory image via adb sideloading.
http://phandroid.com/2013/11/21/dow...d-4-4-kitkat-krt16s-ota-directly-from-google/
http://www.androidpolice.com/2013/1...riants-of-nexus-7-2012-and-2013-and-nexus-10/
http://www.androidpolice.com/2013/1...16s-ota-manually-root-or-unlock-not-required/
What gives??
Click to expand...
Click to collapse
The links are not installing the factory image image by adb sideloading. They are using an ota zip (what i have provided you with above) and sideloading that.
Thanks.
Someone lead me down the wrong path with the OTA image. They told me to use the factory image one. Sorry about the dumbness!!
I've tried updating via TWRP install & adb sideload with the image from the link & it fails each time.
Seems that theres something not quite right with my phone. My phone is definitely running 4.3 JWR66Y with 3.4.0 Franco Kernel.
Is my version of TWRP ok - I have 2.6.3.0. I didn't know if this had any issues with flashing 4.4? I've tried updating it through Goomanager but i doesn't seem to want to download the latest version.
edit, just manually install 2.6.3.3 & update is still failing.
cmberry20 said:
I've tried updating via TWRP install & adb sideload with the image from the link & it fails each time.
Seems that theres something not quite right with my phone. My phone is definitely running 4.3 JWR66Y with 3.4.0 Franco Kernel.
Is my version of TWRP ok - I have 2.6.3.0. I didn't know if this had any issues with flashing 4.4? I've tried updating it through Goomanager but i doesnt seem to want to download the latest version.
Click to expand...
Click to collapse
You are definetly using this right?: http://android.clients.google.com/p....signed-occam-KRT16S-from-JWR66Y.d1b99704.zip
Instead of sideloading try pushing it to the phone manually then flashing it.
Nope, not working. It just doesnt want to know.
I wonder if its the custom kernel? I'll try flashing the OEM one see if it makes a difference.
it will not work, otas check for fils remember?.
hes using custom kernel so no work.
to upgrade to 4.4 download factory images of 4.4. extract and then u open image-occamikrt16s.zip(or whatever the name is), delete userdata.img and recovery.img, then u restart your n4 into fastboot mode, connect to pc, and run flash-all.boom, but u will need to re flash the kernel with a krt16s compatible one.
So I've searched and read for about the last 4 hours, and I'm only more confused than before.
Using a Verizon VS980:
1.Took the OTA (to VS96012B) when I first got the phone
2. Rooted using ioroot script
3. installed latest twrp (2.6.3.3) using Freegee
4. Downloaded CM10.2 stable directly from Get.cm as well as appropriate GAPPS
5. Rebooted into TWRP
6. Wiped (but did not backup since I didn't care about keeping user data...did this wipe the factory OS too then?)
7. Attempted to flash CM10.2 and got the following error:
"Skipping MD5 check: no MD5 file found.
assert failed: run_program("/system/bin/loki.sh
E:Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/download/cm-10.2.0
8. Attempted to reboot into stock since CM flash had failed and got "secure booting unsuccessful" error message
Why would the CM10.2 install be failing under the above messages? And did I blow away my factory ROM? I just used the generic TWRP 2.6.3.3 "factory reset option"??
Dear lord help me. I've read so many threads, but I've ended up much more confused.
In theory, the stock ROM should still be installed since the CM10.2 flash failed, what do I need to do to A.)Be able to successfully flash the CM10.2 without getting the "error executing updater binary in zip" problem, or B.) Be able to at least boost back into stock LG image?
Thanks,
-A
Planning on using this to go back to how it shipped stock, and then re-rooting, and re-installing TWRP and taking another shot at a ROM. Can someone please tell me if this is the right direction?
http://forum.xda-developers.com/showthread.php?t=2449670
After going back to stock I would go this route if u take 12b OTA.
http://forum.xda-developers.com/showthread.php?t=2587296
Sent from Verizon logo plastered G2 bastard
Thanks for the reply! I've edited the OP for a little additional detail/clarity. I'm trying to figure out at this stage why my CM10.2 install failed first and foremost. I'd like to be able to avoid going all the way back to stock if possible?
Any suggestions on why I was getting the below message during attempting to install?
"
Attempted to flash CM10.2 and got the following error:
"Skipping MD5 check: no MD5 file found.
assert failed: run_program("/system/bin/loki.sh
E:Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/download/cm-10.2.0
"
amazonparrot said:
Thanks for the reply! I've edited the OP for a little additional detail/clarity. I'm trying to figure out at this stage why my CM10.2 install failed first and foremost. I'd like to be able to avoid going all the way back to stock if possible?
Any suggestions on why I was getting the below message during attempting to install?
"
Attempted to flash CM10.2 and got the following error:
"Skipping MD5 check: no MD5 file found.
assert failed: run_program("/system/bin/loki.sh
E:Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/download/cm-10.2.0
"
Click to expand...
Click to collapse
It seems like the recovery u flashed from freegee was not properly loki'd for the 12b firmware. It allowed u to overwrite the stock recovery but not flash any ROMs. U could try pushing the patched Loki img and recovery in the thread I posted earlier using adb. U can follow the same instructions in the thread u linked just use the updated patched files.
When u wiped prior to flashing cm10.2, if u wiped system then u have no ROM on ur device to boot into. Always make a backup just in case. That way if u have a bad download or the ROM just won't boot, u gotta plan B.
Sent from Verizon logo plastered G2 bastard
truckroot said:
It seems like the recovery u flashed from freegee was not properly loki'd for the 12b firmware. It allowed u to overwrite the stock recovery but not flash any ROMs. U could try pushing the patched Loki img and recovery in the thread I posted earlier using adb. U can follow the same instructions in the thread u linked just use the updated patched files.
When u wiped prior to flashing cm10.2, if u wiped system then u have no ROM on ur device to boot into. Always make a backup just in case. That way if u have a bad download or the ROM just won't boot, u gotta plan B.
Sent from Verizon logo plastered G2 bastard
Click to expand...
Click to collapse
If I just used the standard TWRP Wipe/factory reset, (which I did) my factory system ROM should be still there, but for whatever reason I'm unable to boot it.
I'm assuming the threads and methods you referenced will work with ADB sideload?
Thanks again
amazonparrot said:
If I just used the standard TWRP Wipe/factory reset, (which I did) my factory system ROM should be still there, but for whatever reason I'm unable to boot it.
I'm assuming the threads and methods you referenced will work with ADB sideload?
Thanks again
Click to expand...
Click to collapse
Yeah. I would try pushing the patched Loki img via adb, then try flashing the cm10.2 ROM. Otherwise u can sideload a stock ROM and flash that.
Sent from Verizon logo plastered G2 bastard
Managed to get back to stock!
Re-rooted, and used Freegee to install latest CWM ths time. Attempted to install CM10.2 again (fresh download) and it STILL gives the error:
Attempted to flash CM10.2 and got the following error:
"Skipping MD5 check: no MD5 file found.
assert failed: run_program("/system/bin/loki.sh
E:Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/download/cm-10.2.0
Why am I still unable to flash a ROM?
amazonparrot said:
Managed to get back to stock!
Re-rooted, and used Freegee to install latest CWM ths time. Attempted to install CM10.2 again (fresh download) and it STILL gives the error:
Attempted to flash CM10.2 and got the following error:
"Skipping MD5 check: no MD5 file found.
assert failed: run_program("/system/bin/loki.sh
E:Error executing updater binary in zip '/sdcard
Error flashing zip '/sdcard/download/cm-10.2.0
Why am I still unable to flash a ROM?
Click to expand...
Click to collapse
Read that some are having issues using Freegee/Flashify to install a working loki'd recovery with 12b OTA. ADB seems to work best. Glad to hear u were able to get back to stock though.
Sent from Verizon logo plastered G2 bastard
I'm actually on 11A :-/
I was planning on using CM10.2 since I just want a 4.3 or 4.4 ROM thats actually stable, but maybe its just the particular ROM I'm trying? I'll try doing ADB to push a different recovery just in case.
Any recommendations on a good stable ROM?
amazonparrot said:
I'm actually on 11A :-/
I was planning on using CM10.2 since I just want a 4.3 or 4.4 ROM thats actually stable, but maybe its just the particular ROM I'm trying? I'll try doing ADB to push a different recovery just in case.
Any recommendations on a good stable ROM?
Click to expand...
Click to collapse
The unofficial cm 4.4.2 is a good one. OP has good directions on getting ROM to run perfectly with kernel settings.
If ur on 11a u should have zero issues flashing, def try a different ROM.
Sent from Verizon logo plastered G2 bastard
Same error... kinda freaking out now #FML
I am so lost and confused. Definately in over my head right now. I usually depend on the one click methods to flash, and this time I'm bricked. Same problem as post #1 on the thread. Not very familiar with adb. Is anyone with experience in this area able/willing to remote into my mac or even over the phone to help a brother out? I'm willing to compensate you for your time.
Thanks,
Vinnie
Ok so currently running a rooted VS980 on 12B with CWM 6.0.x.x non touch. I have attempted to flash both CM10.2 and a 4.4 kitkat absed rom (pa_g2-4.0-ALPHA-20131205-vs980). In both cases I get the same error,
asset failed: run_program("/system/bin/loki.sh") == 0
E: Error in /data/media/o/ (filename of rom in zip format)
(status 7)
installation aborted
My current steps are a backup of rooted 12B,
wipe/factory reset
wipe cache partition
wipe dalvik
format system.
I also attempted to install a GAPPS .zip to see if it was happening with all zip files, the GAPPS installed with no issues.
phone also will take a restore from CWM so at least im not bricked in the meantime
Now that that is all out of the way can anyone tell me what is happening here? Only my second rooted phone first being a droid 4 and by the time I rooted it there was a lot out in the form of auto runs and apps to take care of all the steps to root/flash roms. So my knowledge level is pretty novice on this.
UPDATE: so after my reading im coming across random issues with CWM on the LG G2. going to attempt to push ASOPA 4.4 with GAPPS after I switch to TWRP.
Get same thing on trwp
Sent from my VS980 4G using XDA Premium 4 mobile app
Make sure you are on the latest versions. Darker ones will not install kitkat. Roms
Sent from my LG-D800 using Tapatalk
UPDATE 2:
Ok, so after following the guide below and face palming myself about a thousand times through the process, I've come to another snag..... I get all the way to the end in both options 1 and 2, then get the error below. Option 3 (GooManager) states that there is no recovery for my phone.
http://forum.xda-developers.com/showthread.php?t=2449670
[+] loki_flash 2.1
[-] loki aboot version does not match device
looked around through the thread and cannot find a definitive answer on what im doing wrong or what I may have done wrong in rooting or with already running CWM.
I want to attempt to go back to stock. Completely unrooted and start from scratch but not sure the path to take on this. I've factory reset via CWM but the phone is still rooted and the apps i removed via titanium backup are missing as well.
Is there a way to pull a stock firmware and somehow push it to the phone so that everything i have done thus far is erased? ( excuse the terminology here) like erasing and reformatting a computer's hdd and re installing windows.
update:
http://forum.xda-developers.com/showthread.php?t=2432476
Hopefully this stock firmware guide works...
Goo doesn't work either lol. Use freegee to install recovery. Will take you about 2 minutes to complete and you will be rooted and have a custom recovery installed
Sent from my LG-D800 using Tapatalk
Thats how I got CWM onto the phone after I rooted. After all my reading though, I want to go back to stock and start all over again. I still haven't got a chance to start the proccess yet, been pouring through the thread about reverting back to stock firmware to see what issues have come up. From mwhat I can tell the issues were all related to people not fully reading the directions provided by the OP. Will update once I have attempted. FreeGee worked like a charm for getting CWM on though
Ok, so using the thread listed above i was able to revert back to 11a!!!!!!! now, onto IORoot and see if i can loki twrp 2.6.3.2 and then flash 2.6.3.3.
Status 7 error means the rom developer is still using the old update binary script.
If you flash the latest philz recovery before you install a zip untick the setting that says" don't allow old update binary" Your zips should then flash without issue.
A better solution is to use the new update binary script yourself or ask the rom developer to update it.
Sent from my LG-D802 using Tapatalk
corrsea said:
Status 7 error means the rom developer is still using the old update binary script.
If you flash the latest philz recovery before you install a zip untick the setting that says" don't allow old update binary" Your zips should then flash without issue.
A better solution is to use the new update binary script yourself or ask the rom developer to update it.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
Thanks for clarifying that!!!!!
So as of now I have re flash stock 11A per the guide (showed unrooted once done), Rerooted via IORoot 22 and then adb flashed twrp 2.6.3.2, Now I am going to flash the 2.6.3.3 .zip via TWRP and then try to flash A ROM and Kernel.
Back up and running!!!!
IORoot22
TWRP 2.6.3.3
ASOPA 4.4 BETA (updating as daily releases come out)
Slim GAPPS (might switch to regular due to the speech to text function being missing from keyboard but need to do some reading to figure out if running the full GAPPS will fix that or if it is something with the ROM ) EDIT: as i typed this i got a text and as i replied I noticed the icon is there now on the keyboard.... FACEPALM....
Thanks for all the information that was provided guys. Probably could have cleared this all up without the thread and just reading, Thanks for not flaming me and turning me away with a statement to use the search function.
To anyone reading this to find a fix for an issue they are having here are the links in order of what I did to get back up and functioning.
1. Went back to stock
http://forum.xda-developers.com/showthread.php?t=2448960 ( how to go back to stock )
http://forum.xda-developers.com/showthread.php?t=2141817 ( how to set up SDK )
2. ReRooted
http://forum.xda-developers.com/showthread.php?t=2448887 ( IOROOT how to )
3. TWRP
http://forum.xda-developers.com/showthread.php?t=2449670 ( TWRP how to )
All these guides worked the first time through for me, make sure you take the time and read all the directions in them.
Today I received the OTA update from Android 4.4.2 to 4.4.4 for my Moto G.
Filename:
Blur_Version.176.44.1.falcon_umts.EURetail.en.EU.zip
Md5:
fbe58f70c4922c785d55fd5a998e9628
Download links:
http://www.filedropper.com/blurversion176441falconumtseuretaileneu
http://www13.zippyshare.com/v/24209763/file.html
https://www.sendspace.com/file/ighq3s
Extra info:
- Received the OTA while being rooted & using custom recovery.
- Can be flashed using PhilZ recovery.
- SuperSU Pro survived the OTA.
Petrovski80 said:
Today I received the OTA update from Android 4.4.2 to 4.4.4 for my Moto G.
Filename:
Blur_Version.176.44.1.falcon_umts.EURetail.en.EU.zip
Md5:
fbe58f70c4922c785d55fd5a998e9628
Download links:
http://www.filedropper.com/blurversion176441falconumtseuretaileneu
http://www13.zippyshare.com/v/24209763/file.html
https://www.sendspace.com/file/ighq3s
Click to expand...
Click to collapse
Is it possible to just flash this in twrp recovery?
Ive been having this pop up every 5 mins and its driving me mad, I download it but it wont flash in custom recovery, I flash stock recovery still wont flash, ive downloaded it several times just incase it was a bad download.
feartheanonymity said:
Is it possible to just flash this in twrp recovery?
Ive been having this pop up every 5 mins and its driving me mad, I download it but it wont flash in custom recovery, I flash stock recovery still wont flash, ive downloaded it several times just incase it was a bad download.
Click to expand...
Click to collapse
It should be. I flashed it using Philz recovery.
feartheanonymity said:
Is it possible to just flash this in twrp recovery?
Ive been having this pop up every 5 mins and its driving me mad, I download it but it wont flash in custom recovery, I flash stock recovery still wont flash, ive downloaded it several times just incase it was a bad download.
Click to expand...
Click to collapse
I had the same problem, TWRP did not take the OTA file properly. Every time it wanted to boot after the install started, it started TWRP and if I restarded the device it went into a bootloop.
So I installed Philz and everything went fine!
It has been said many times already. Phliz is the way to go when flashing OTAs.
Sent from my XT1032 using XDA Premium 4 mobile app
drfr said:
It has been said many times already. Phliz is the way to go when flashing OTAs.
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I copied the zip from /cache and am attempting to install it with the latest Philz.
I get this error in Philz when flashing the zip:
Verifying current system...
"EMMC:boot:10485....................... a0" has unexpected contents.
I restored my stock kernel (was running Faux before). My bootloader is unlocked and I am rooted.
Is it possible to flash directly? Or must I restore stock recovery, flash and reroot?
Is it OK to flash this if I'm already on 4.4.4?
Quark^2 said:
I copied the zip from /cache and am attempting to install it with the latest Philz.
I get this error in Philz when flashing the zip:
Verifying current system...
"EMMC:boot:10485....................... a0" has unexpected contents.
I restored my stock kernel (was running Faux before). My bootloader is unlocked and I am rooted.
Is it possible to flash directly? Or must I restore stock recovery, flash and reroot?
Click to expand...
Click to collapse
You´ve restored wrong kernel. It may be working for you, but it is different from stock. The error says that there is something that is not supposed to be there in the kernel partition.
Nicolae-Daniel said:
Is it OK to flash this if I'm already on 4.4.4?
Click to expand...
Click to collapse
You´re kidding, right?
No.my system is tesco GB.i live in Romania.by flashing this i believe will improve connectivity.
@knizmi what do you think?
Nicolae-Daniel said:
No.my system is tesco GB.i live in Romania.by flashing this i believe will improve connectivity.
@knizmi what do you think?
Click to expand...
Click to collapse
1. You can´t flash this if you are on anything other than en.EU 4.4.2. This is not a complete ROM, but rather an update for a specific ROM version.
2. It is possible reflash your XT1032 with en.EU 4.4.2 firmware and then update it to 4.4.4, but if you don´t know what you are doing, you could brick your device (several people have when they tried to downgrade the bootloader).
3. What improvement in conectivity do you mean? Is the tesco firmware limited in any way? AFAIK it isn´t, so leave it as it is and be happy about a great phone with the latest Android version.
knizmi said:
1. You can´t flash this if you are on anything other than en.EU 4.4.2. This is not a complete ROM, but rather an update for a specific ROM version.
2. It is possible reflash your XT1032 with en.EU 4.4.2 firmware and then update it to 4.4.4, but if you don´t know what you are doing, you could brick your device (several people have when they tried to downgrade the bootloader).
3. What improvement in conectivity do you mean? Is the tesco firmware limited in any way? AFAIK it isn´t, so leave it as it is and be happy about a great phone with the latest Android version.
Click to expand...
Click to collapse
By connectivity I meant signal strength.
My US-Global XT1032 still waiting...
tonyleeloveyou said:
My US-Global XT1032 still waiting...
Click to expand...
Click to collapse
US Global already has 4.4.3. The new kernel and dialer are already there, so don´t expect any improvements besides security patches when we get 4.4.4.
I received the OTA today. Updated without problems. Stock XT1032 8GB Moto G.
drfr said:
It has been said many times already. Phliz is the way to go when flashing OTAs.
Sent from my XT1032 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
If you're still on Stock Recovery and don't want to use Philz, you can try to update the OTA by following the steps in the OP of this Post. I tried a lot of flashing, but in the end only this worked:
http://forum.xda-developers.com/moto-g/general/ota-file-indian-dual-sim-4-4-4-t2810166
Just follow the steps below the text:
REVERT TO STOCK WITHOUT LOSING DATA OR ANYTHING ELSE
Phone is unlocked, rooted and had xposed modules on it
Petrovski80 said:
Today I received the OTA update from Android 4.4.2 to 4.4.4 for my Moto G.
Filename:
Blur_Version.176.44.1.falcon_umts.EURetail.en.EU.zip
Md5:
fbe58f70c4922c785d55fd5a998e9628
Download links:
http://www.filedropper.com/blurversion176441falconumtseuretaileneu
http://www13.zippyshare.com/v/24209763/file.html
https://www.sendspace.com/file/ighq3s
Extra info:
- Received the OTA while being rooted & using custom recovery.
- Can be flashed using PhilZ recovery.
- SuperSU Pro survived the OTA.
Click to expand...
Click to collapse
i have a xt1032 too, and thought this would be the easiest way to update!
unlocked, rooted, cwm philz (6.19.2)
but i get a status 7 error during flashing.
verifying current system...
"/system/build.prop"has unexpected contents.
E: Error in in /data/media/0/clockworkmod.Blur_Version.176.44.1.flacon_umts.EURetail.en.EU.zip
dreezz said:
i have a xt1032 too, and thought this would be the easiest way to update!
unlocked, rooted, cwm philz (6.19.2)
but i get a status 7 error during flashing.
verifying current system...
"/system/build.prop"has unexpected contents.
E: Error in in /data/media/0/clockworkmod.Blur_Version.176.44.1.flacon_umts.EURetail.en.EU.zip
Click to expand...
Click to collapse
So why don´t you revert your build.prop to stock?
dreezz said:
i have a xt1032 too, and thought this would be the easiest way to update!
unlocked, rooted, cwm philz (6.19.2)
but i get a status 7 error during flashing.
verifying current system...
"/system/build.prop"has unexpected contents.
E: Error in in /data/media/0/clockworkmod.Blur_Version.176.44.1.flacon_umts.EURetail.en.EU.zip
Click to expand...
Click to collapse
Knizmi is right. You modified your build.prop file, and an OTA update requires unmodified system files. You can add files to /system without problems however, so the su binary for example isn't an issue.
Sent from my Moto G using Tapatalk
OK, and where do i find a stock build.prop?
i don't know what modifications i have, but can i replace the stock one with my current after flashing? (and do i need to?)
HI! Firstly thanks for share the zip.
I´m using cwm recovery, superSU and xposed. Can I flash the zip directly from the recovery without any change? Will I lose the recovery (coming back to stock recovery) if I succed?
I tried to install the OTA after uninstall xposed and checking the ota survival mode on superSU, but it didn´t work (bootloop).
Thanks in advance.
Hi
I am hoping someone can help me please?
My phone was already rooted and not really had any issue up until yesterday.
I have been trying to get a lollipop ROM onto my phone. In the process i decided that it would be wise to update my TWRP recovery to the latest using the play store TWRP app. Having done that, when i now try to get to recovery, the phone hangs on the 'Reovery Booting...' message.
How can I move forward from here? Am i able to flash the original version of the TWRP using odin again?
Thanks in advance
Manny
mannysroot said:
Hi
I am hoping someone can help me please?
My phone was already rooted and not really had any issue up until yesterday.
I have been trying to get a lollipop ROM onto my phone. In the process i decided that it would be wise to update my TWRP recovery to the latest using the play store TWRP app. Having done that, when i now try to get to recovery, the phone hangs on the 'Reovery Booting...' message.
How can I move forward from here? Am i able to flash the original version of the TWRP using odin again?
Thanks in advance
Manny
Click to expand...
Click to collapse
Yes, maybe the TWRP Manager detected one update (TWRP 2.8.5.0) and installed it but this version have bugs. It was deleted of the official page of TWRP too. Flash via ODIN the older version (TWRP 2.8.4.0) and all will be solved. Good luck :highfive:.
I used Nandroid manager to flash the img of twrp when I rooted my phone. Because Odin failed to flash it.