Related
Hi all,
I am interested in the CM11 ROM. Last night I spent 6hrs trying and failed, epically.
Here is what I did already:
1. Downgraded from 4.4.2 back to factory
2. Successfully rooted
3. Installed ROM Manager
4. Successfully downloaded CM11 and latest GApps
Then when I tried to boot into recovery it kept going to a screen with a little android guy lying on his back with a red triangle!!! I tried six times.
I got frustrated and just updated back to 4.4.2 and have been dealing with it. I am still rooted and have been able to remove my bloatware and other things you need root access for.
Any thoughts or help as to how I can install the CM11 rom?? I am happy running NovaLauncher and using DynamicNotifications to approximate it but really want to try out CM11.
Cheers and thanks!
Lucky there is no way to root on 4.4.2 yet or atleast no Recovery's yet it could be worse you're atleast rooted and it didn't brick your phone
Sent from my VS980 4G using Tapatalk
Did you actually try flashing a recovery first? Just installing ROM manager won't install the custom recovery needed to flash ROMs. You have to do that step as well.
JRJ442 said:
Did you actually try flashing a recovery first? Just installing ROM manager won't install the custom recovery needed to flash ROMs. You have to do that step as well.
Click to expand...
Click to collapse
No, I didn't. I am super new with android. Had an iphone for a long time. How do I flash a recover? Can I still do it now on 4.4.2 b/c its rooted?
Sorry about the noob questions, everyone is being very helpful!
follow this step..
http://forum.xda-developers.com/showthread.php?t=2681205
android_nashville said:
No, I didn't. I am super new with android. Had an iphone for a long time. How do I flash a recover? Can I still do it now on 4.4.2 b/c its rooted?
Sorry about the noob questions, everyone is being very helpful!
Click to expand...
Click to collapse
LG blocked the Loki exploit with 4.4.2 so you can't flash recoveries currently. You'd have to flash back to 4.2.2 to do that. Which if you want custom ROMs now its going to have to be done sooner or later. Which carrier and model number do you have? If you have an international D802 the above post by @zekurosu will work for you, otherwise don't use that one. You're gonna have to find the method for your model number.
My first guess was that you missed the flashing the custom recovery step, which people above me have already helped ya out on. For being new to Android you did fairly well, you just missed that one step.
Good luck!
JRJ442 said:
LG blocked the Loki exploit with 4.4.2 so you can't flash recoveries currently. You'd have to flash back to 4.2.2 to do that. Which if you want custom ROMs now its going to have to be done sooner or later. Which carrier and model number do you have? If you have an international D802 the above post by @zekurosu will work for you, otherwise don't use that one. You're gonna have to find the method for your model number.
Click to expand...
Click to collapse
thanks, forgot to mention it was only for D802 :good:
zekurosu said:
thanks, forgot to mention it was only for D802 :good:
Click to expand...
Click to collapse
I have an ATT D800 running 4.4.2. I can't decide whether its worth it to flash back to 4.2.2 to try again. Pretty happy with NovaLauncher + widgetlocke and fairly closely approximates what I am looking for.
For what its worth, I was in 4.2.2 when I tried the first time and failed. I think mackster is right, I didn't flash the custom recovery. I basically flashed back to 4.2.2->rooted->tried to boot into recovery (OVER and OVER) then gave up and upgraded back to 4.4.2.
Thanks for all the help. At least I now have a rooted phone and have been able to do some cool stuff with that. My goal is to get nexus 5 software in an LG G2 body (battery, camera, etc)
@android_nashville There's a way to have the best of both worlds. You can flash back to 4.2.2 (10d preferably) root, flash a custom recovery with Flashify or FreeGee. Both available on the play store. Then actually update to 4.4.2 following this thread http://forum.xda-developers.com/showthread.php?t=2483043. Eventually, if you want to flash custom ROMs you're going to have flash back to 4.2.2 and do this process regardless. The 4.4 aboot image (bootloader) can't be bypassed with Loki. Its been blocked. But some brilliant devs basically found out they can make a hybrid setup, with the 4.2.2 aboot, and everything else 4.4.2. This way you can have the ability to flash custom recovery, kernels and ROMs.
Android 5.0 (Lollipop) Bootloader and KitKat Compatibility
Everyone wants Lollipop, however it is worth considering some of the possible consequences of upgrading via OTA update.
Flashable zip of Android 5.0.2 'Soak Test' now available and boots with KitKat Bootloader: http://forum.xda-developers.com/moto-g/development/rom-retail-brazil-lollipop-soak-test-t2998793
Downgrading to KitKat also possible even with Lollipop Bootloader.
Bootloader:
A new Bootloader (BL) will almost certainly be is included in the OTA update. It is also very likely no KitKat Kernel, stock or custom will be able to boot properly with the 5.0 BL. Perhaps the Kernel DEVs can find a workaround.
Root: (DONE)
It may take some time to gain root access on Lollipop as on other devices this has required a custom Kernel. A custom kernel itself may require kernel sources to be released - something that has taken weeks / months in the past.
Chainfire releases Android 5.0 Root for Moto G (2013) (All Models)
In addition; apps that use root access in KitKat, require further development to have functional root access in Lollipop.
Xposed Framework:
Developer has said he will wait for CyanogenMod based on Lollipop before properly starting development of an ART version of Xposed. CM12 may take a few weeks to release. Expect to do without Xposed for at least a month, probably longer since root is also required (see above.) Related: Alternatives to popular Xposed Modules
Custom Recovery:
This has not been an issue before, but it is always possible a new Bootloader could break compatibility with existing Custom Recoveries. Obviously, you would not be able to restore a CWM / TWRP backup without a functional custom recovery; but even then, it is unlikely you will [not] be able to boot your KitKat backup. CWM unaffected, TWRP not fully supported yet.
Custom ROMs:
This is another area that could be affected by a new Bootloader. It is unknown if existing custom ROMs will require new Kernels / system changes in order to work with the new BL - something that could take days, weeks or months. CyanogenMod 12 (Lollipop) for Moto G (Falcon) now available and does not appear to require a new BL.
Performance:
Currently the performance difference between KitKat and Lollipop is unknown. If the first release of Lollipop for Moto G has performance issues, you may be unable to revert back to stock KitKat.Possible solution:
Wait for a flashable zip [NOT OTA Update zip] of Stock Moto G Lollipop ROM - this would mean your Bootloader remains at it's current version and potentially allowing you to change 'back and forth' between Stock KitKat and Stock Lollipop. However, it is currently unknown if the newer BL is a requirement for Android 5.0 Kernels. Flashable zip of Android 5.0.2 'Soak Test' now available and boots with KitKat Bootloader.
That is what I thought, since something like that happened because of the upgrade from JB to KK. Taking all of this into account, I'm not sure to upgrade immediately when the OTA comes out, maybe I'll try to still alive waiting for reviews from someone who dares to OTA right then.
You can be pretty sure it'll bring a bootloader update too because of all the fundamental changes lollipop brings in almost all areas of the OS. Major relase, as was gingerbread -> ICS.
It's pretty safe to say that once you upgrade, it won't be easy to downgrade, if at all possible... Many changes are in the security area and everything is getting tightened up a lot... Loads of tempting things we'll get in this upgrade, yes, but we'll have to give up much of what we're used to (in terms of rooting/etc), at least for a little while. I'll also wait until the dust settles a bit and it's clearer on where we stand with the upgrade once it gets released.
nice info
lost101 said:
Android 5.0 Bootloader and KitKat Compatibility
Everyone wants Lollipop, however it is worth considering some of the possible consequences of upgrading via OTA update.
Bootloader:
A new Bootloader (BL) will almost certainly be included in the OTA update. It is also very likely no KitKat Kernel, stock or custom will be able to boot properly with the 5.0 BL. Perhaps the kernel DEVs can find a workaround.
Root:
It may take some time to gain root access on Lolipop as on other devices this has required a custom Kernel. A custom kernel itself may require kernel sources to be released - something that has taken weeks / months in the past.
Custom Recovery:
This has not been an issue before, but it is always possible a new Bootloader could break compatibility with existing Custom Recoveries.
Performance:
Currently the performance difference between KitKat and Lollipop is unknown. If the first release of Lollipop has performance issues on Moto G, you may be unable to revert back to stock KitKat.
Alternative solution:
Wait for a flashable zip of Stock Moto G Lollipop ROM - this would mean your Bootloader remains at it's current version and potentially allowing you to change between Stock KitKat and Stock Lollipop. However, it is currently unknown if the newer BL is a requirement for Android 5.0 Kernels.
Click to expand...
Click to collapse
UUUUUUHHHHHHHH iam afraight. a little. who needs bootloaders. i dont.
juanchotazo99 said:
You can be pretty sure it'll bring a bootloader update too because of all the fundamental changes lollipop brings in almost all areas of the OS. Major relase, as was gingerbread -> ICS.
It's pretty safe to say that once you upgrade, it won't be easy to downgrade, if at all possible... Many changes are in the security area and everything is getting tightened up a lot... Loads of tempting things we'll get in this upgrade, yes, but we'll have to give up much of what we're used to (in terms of rooting/etc), at least for a little while. I'll also wait until the dust settles a bit and it's clearer on where we stand with the upgrade once it gets released.
Click to expand...
Click to collapse
Will you be able to wait when you see that little notification saying there's a new system update awaiting you?? I'll eat my nails until then!
Can i still get the OTA update even though my bootloader is unlocked and rooted? (Kitkat 4.4.4.)
Drift0r said:
Can i still get the OTA update even though my bootloader is unlocked and rooted? (Kitkat 4.4.4.)
Click to expand...
Click to collapse
I don't think so....
Drift0r said:
Can i still get the OTA update even though my bootloader is unlocked and rooted? (Kitkat 4.4.4.)
Click to expand...
Click to collapse
Bootloader doesn't matter. Root doesn't matter. What does matter is the software on your phone that checks for OTA updates. As long as that is functioning; you will get the notification.
You can ignore the update notification and will not be forced to install it.
Drift0r said:
Can i still get the OTA update even though my bootloader is unlocked and rooted? (Kitkat 4.4.4.)
Click to expand...
Click to collapse
The only real thing you need to install the OTA is stock recovery, doesnt matter bootloader or root, only stock recovery to install the OTA! :good:
As always, very informative thread @lost101.
lost101 said:
Bootloader doesn't matter. Root doesn't matter. What does matter is the software on your phone that checks for OTA updates. As long as that is functioning; you will get the notification.
You can ignore the update notification and will not be forced to install it.
Click to expand...
Click to collapse
MarckozZ said:
The only real thing you need to install the OTA is stock recovery, doesnt matter bootloader or root, only stock recovery to install the OTA! :good:
Click to expand...
Click to collapse
How do I know what recovery I am on? I entered recovery and it is like this http://i.gyazo.com/1c3fa4923e85db7042ad6e36b97a31cc.png then when I click recovery on that screen I am on CWM, does that mean I can't or can do it?
Also I am not using any roms or anything, just rooted it for Xposed.
Drift0r said:
How do I know what recovery I am on? I entered recovery and it is like this http://i.gyazo.com/1c3fa4923e85db7042ad6e36b97a31cc.png then when I click recovery on that screen I am on CWM, does that mean I can't or can do it?
Also I am not using any roms or anything, just rooted it for Xposed.
Click to expand...
Click to collapse
You need stock recovery and rid of xposedand any modules
MarckozZ said:
The only real thing you need to install the OTA is stock recovery, doesnt matter bootloader or root, only stock recovery to install the OTA! :good:
Click to expand...
Click to collapse
And another real thing is pure/stock system. Which means no system apps were deleted or frizzed no mods were installed through custom recovery no custom kernels no luckyputcher stuff. And I think you have to delete xposed framework (manually via xposed installer).
And a lot of users think that it's enough just to flash back stock recovery and install ota. But then they are just wondering why is it can not install. So, untouched system block is mandatory for applying ota as well as stock recovery.
Root, unlocked bootloader and custom boot logo are things you could keep.
Is stock recovery and stock firmware same? If not how do i get stock recovery back?
S0bes said:
And another real thing is pure/stock system. Which means no system apps were deleted or frizzed no mods were installed through custom recovery no custom kernels no luckyputcher stuff. And I think you have to delete xposed framework (manually via xposed installer).
And a lot of users think that it's enough just to flash back stock recovery and install ota. But then they are just wondering why is it can not install. So, untouched system block is mandatory for applying ota as well as stock recovery.
Root, unlocked bootloader and custom boot logo are things you could keep.
Click to expand...
Click to collapse
How about if you are using Adaway?
I know this will change something to the file hosts.
Do you need to get this original hosts file as well?
Drift0r said:
How do I know what recovery I am on? I entered recovery and it is like this http://i.gyazo.com/1c3fa4923e85db7042ad6e36b97a31cc.png then when I click recovery on that screen I am on CWM, does that mean I can't or can do it?
Also I am not using any roms or anything, just rooted it for Xposed.
Click to expand...
Click to collapse
I'd reccomend to you this: when the OTA comes up, restore stock 4.4.2 firmware, then OTA to 4.4.4 and then to 5.0... Or if you find a 4.4.4 firmware just flash it and then OTA to 5.0... But the best you could do is to install the Lollipop OTA in a fresh new installed system.
S0bes said:
And another real thing is pure/stock system. Which means no system apps were deleted or frizzed no mods were installed through custom recovery no custom kernels no luckyputcher stuff. And I think you have to delete xposed framework (manually via xposed installer).
And a lot of users think that it's enough just to flash back stock recovery and install ota. But then they are just wondering why is it can not install. So, untouched system block is mandatory for applying ota as well as stock recovery.
Root, unlocked bootloader and custom boot logo are things you could keep.
Click to expand...
Click to collapse
Yes, maybe the best thing is to backup everything and restore all things to stock... then OTA to Lollipop... :good:
MarckozZ said:
I'd reccomend to you this: when the OTA comes up, restore stock 4.4.2 firmware, then OTA to 4.4.4 and then to 5.0... Or if you find a 4.4.4 firmware just flash it and then OTA to 5.0... But the best you could do is to install the Lollipop OTA in a fresh new installed system.
Yes, maybe the best thing is to backup everything and restore all things to stock... then OTA to Lollipop... :good:
Click to expand...
Click to collapse
Almost always it is enough to flash only system img files without erasing userdara. It should rewrite system block so it becames stock
MarckozZ said:
I'd reccomend to you this: when the OTA comes up, restore stock 4.4.2 firmware, then OTA to 4.4.4 and then to 5.0... Or if you find a 4.4.4 firmware just flash it and then OTA to 5.0... But the best you could do is to install the Lollipop OTA in a fresh new installed system.
Yes, maybe the best thing is to backup everything and restore all things to stock... then OTA to Lollipop... :good:
Click to expand...
Click to collapse
How do I restore it to 4.4.3? Im currently downloading this file to flash via mfastboot RET-EU-SS_4.4.3_KXB21.14-L1.31_cid7_CFC_1FF.xml.zip from this guide. http://forum.xda-developers.com/showthread.php?t=2542219 would this work?
my phone moto g 4g lte - xt1039
Drift0r said:
How do I restore it to 4.4.3? Im currently downloading this file to flash via mfastboot RET-EU-SS_4.4.3_KXB21.14-L1.31_cid7_CFC_1FF.xml.zip from this guide. http://forum.xda-developers.com/showthread.php?t=2542219 would this work?
my phone moto g 4g lte - xt1039
Click to expand...
Click to collapse
You can try the guide I've done with some help from other users here at XDA...
http://forum.xda-developers.com/moto-g/general/guide-restore-moto-firmware-gpe-t2914884
here we go
https://dl.dropboxusercontent.com/u/40676435/Blur_Version.210.12.32.falcon_umts.Retail.en.US.zip
4.4.4
Moto G (gen 1) (Consumer Cellular) just updated 4.4.4
Thanks pal, changelog?
I just got the update. I think Motorola is getting ready to update their Moto devices to Lollipop.
Im on CWM
Is it weird that I got the notification for the 4.4.4 update even though I use CWM instead of the stock recovery?
When I got the 4.4.3 update, I installed it via the OTA and didn't change from CWM to stock recovery. Nothing seemed wrong. But from what I understood you shouldn't be able to get OTA updates if you have a custom recovery?
I'm on Philz recovery. Unfortunately can't install the OTA. While installing error appears saying that there is a problem with verification Exchange2.apk...
Does this work with cwm? I tried with twrp but no luck and for some reason I can't fastboot stock recovery
Only stock recovery and untouched /system partition
So not for me
tony_evl said:
Only stock recovery and untouched /system partition
Click to expand...
Click to collapse
I've got Philz Recovery and I can update with the update zip.
My system partition was unmodified (The Exchange error like it happens to Legomina was caused by a system modification).
Have a rooted device with xposed. OTA does not apply either with stock recovery or philz. Does anyone have a full SBF instead (I hate OTAs anyway, they never quite work for me)?
When the full firmware image is available, it will be announced here:
http://forum.xda-developers.com/showthread.php?t=2546251
tony_evl said:
here we go
https://dl.dropboxusercontent.com/u/40676435/Blur_Version.210.12.32.falcon_umts.Retail.en.US.zip
Click to expand...
Click to collapse
Thanks for this! Updated using this. My falcon was rooted using Superboot. So the recovery was stock. I was using xposed modules. I followed these steps:
1. Downloaded the file in OP
2. Copied it to sdcard
3. Booted to recovery
4. Selected install update from sdcard and then selected the update zip
5. Done! :good:
It took around 5 minutes for all this process. Thanks a lot @tony_evl :highfive:
---------- Post added at 08:26 PM ---------- Previous post was at 08:25 PM ----------
nupi said:
Have a rooted device with xposed. OTA does not apply either with stock recovery or philz. Does anyone have a full SBF instead (I hate OTAs anyway, they never quite work for me)?
Click to expand...
Click to collapse
Check my post. I have just installed it with stock recovery. Let me know if you need any help...
x1032, Amazon, Global version
I just bought my x1032 Moto G from Amazon. The global GSM (international) version. I learned how to and I unlocked bootloader, flahsed TWRP 2.8.1.0 as my recovery and rooted yesterday!
Currently running 4.4.3. What do I need to do to install 4.4.4?
Total noob here. Moto G is my first andrioid device
cubk said:
I just bought my x1032 Moto G from Amazon. The global GSM (international) version. I learned how to and I unlocked bootloader, flahsed TWRP 2.8.1.0 as my recovery and rooted yesterday!
Currently running 4.4.3. What do I need to do to install 4.4.4?
Total noob here. Moto G is my first andrioid device
Click to expand...
Click to collapse
Go back to stock, you'll get system update notification, flash it and again follow the procedure to root it...
Sent from my Nexus 4 using XDA Free mobile app
nitin.chobhe said:
Go back to stock, you'll get system update notification, flash it and again follow the procedure to root it...
Sent from my Nexus 4 using XDA Free mobile app
Click to expand...
Click to collapse
I'm on CWM and got the update notification? Is that weird? I flashed the 4.4.3 update through CWM and the update notification.
reeved said:
I'm on CWM and got the update notification? Is that weird? I flashed the 4.4.3 update through CWM and the update notification.
Click to expand...
Click to collapse
No, that's not weird. You get that notification, you can even download it. But it won't get installed :silly:
Does anyone have a flashable .zip ROM or a system dump for the 4.4.4 update?
But my 4.4.3 update installed seemingly correctly through CWM. I didnt witness anything out of the ordinary like any bugs.
alireza_simkesh said:
Does anyone have a flashable .zip ROM or a system dump for the 4.4.4 update?
Click to expand...
Click to collapse
If anyone else is also looking for a flashable zip ROM, there is a collection (including 4.4.4 version) in here:
http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688
hi all , sorry but my english is so bad
i just bought a galaxy s4 att secondhand , this had bassband UCUAMDL . and i checked the lastest version of it is 4.2.2
can i upgrade my phone up to 4.4 ?
and i dont know terminology about "MF3 - MK2 ............."
could you tell me ?
thanks so much :victory::victory::victory:
Root. Install TWRP recovery. Flash a rom 4.4.4 or try some lollipop love!! You are lucky enough to have an unlocked bootloader..
HORiZUN said:
Root. Install TWRP recovery. Flash a rom 4.4.4 or try some lollipop love!! You are lucky enough to have an unlocked bootloader..
Click to expand...
Click to collapse
thanks so much ,
can you get me links :crying:
but MF3 - MK2 ............. what is it ?
when i flash rom , what i have to notice ?
I hope you don't have MF3. If that's the case, I'm pretty sure that SafeStrap is your only recovery option.
HORiZUN said:
I hope you don't have MF3. If that's the case, I'm pretty sure that SafeStrap is your only recovery option.
Click to expand...
Click to collapse
but i dont know MF3 >"<
what is it ?
how check it on my phone ?
HORiZUN said:
I hope you don't have MF3. If that's the case, I'm pretty sure that SafeStrap is your only recovery option.
Click to expand...
Click to collapse
i am in 4.2.2
sonluyen94 said:
but i dont know MF3 >"<
what is it ?
how check it on my phone ?
Click to expand...
Click to collapse
I have the same question. hopefully someone will be able to explain it to us.
MF3 would be the last three digits of your system software version
HORiZUN said:
MF3 would be the last three digits of your system software version
Click to expand...
Click to collapse
my baseband : I337UCUAMDL
kernel version : 3.4.0-453947 - [email protected] #1
android version : 4.2.2
build number : JDQ39.I337UCUAMDL
it is my phone >"<
You don't have MF3, and that's a good thing. You can install a custom recovery. You need to root, install a custom recovery, and then you can start flashing roms.
sonluyen94 said:
my baseband : I337UCUAMDL
kernel version : 3.4.0-453947 - [email protected] #1
android version : 4.2.2
build number : JDQ39.I337UCUAMDL
it is my phone >"<
Click to expand...
Click to collapse
nogods said:
I have the same question. hopefully someone will be able to explain it to us.
Click to expand...
Click to collapse
Ok, use TowelRoot.com to root the phone, and use TWRP manager to install TWRP on your device. After that check out the development section of this very forum and flash any ROM you wish. 4.2.2 or 4.4.4 or 5.0 or anywhere in between (Just read the thread and instructions first!!!). Whatever you do, never update using the OTA updater on the stock ROM! Also, dotn ever flash an image in Odin that isn't MDL, because if you go higher than MDL, you lose the ability to have a custom recovery. You are one of the lucky ones, cherish the ability, and read through threads before flashing, stuff. Good Luck!
Also, you don't have to worry if the ROM says safestrap compatible, because you don't have to use Safestrap, you can have TWRP instead (which is better), because all Safestrap ROMS are TWRP compatible, but not vice-versa.
npjohnson said:
Ok, use TowelRoot.com to root the phone, and use TWRP manager to install TWRP on your device. After that check out the development section of this very forum and flash any ROM you wish. 4.2.2 or 4.4.4 or 5.0 or anywhere in between (Just read the thread and instructions first!!!). Whatever you do, never update using the OTA updater on the stock ROM! Also, dotn ever flash an image in Odin that isn't MDL, because if you go higher than MDL, you lose the ability to have a custom recovery. You are one of the lucky ones, cherish the ability, and read through threads before flashing, stuff. Good Luck!
Also, you don't have to worry if the ROM says safestrap compatible, because you don't have to use Safestrap, you can have TWRP instead (which is better), because all Safestrap ROMS are TWRP compatible, but not vice-versa.
Click to expand...
Click to collapse
thanks so much :fingers-crossed:
but can you talk to me what rom is good about battery ?
sonluyen94 said:
thanks so much :fingers-crossed:
but can you talk to me what rom is good about battery ?
Click to expand...
Click to collapse
Most if not all. They're all built from either GPE or CM.
All good advice. Plus when you root and get Twrp recovery installed do a backup thru Twrp (Nandroid) and keep on phone and put a copy on pc. That way you have something to restore if you get in trouble. Also, your bootloader is not unlocked. No Att i337s are. Instead devs use an exploit called Loki-Doki to bypass Sammy's security checks to allow custom roms/kernels etc to flash. You can google Loki Doki and read up on it. If the rom or kernel is not loki'd you will have to flash the zip thru recovery to allow the rom or kernel to flash. You will come across this when flashing International roms and kernels. I don't have link any more so maybe someone else can link it. Keep it on SD card. Like noted read OP carefully and last 20 pages of rom thread. Builds newer than MDL are blocked by Att from using Loki and require SafeStrap. Which you don't need to worry about. Although you can read up on it. Good Luck. [emoji1]
Sent from my iPhone 6 Plus using Tapatalk
I hope you won't mind me jumping in your thread.,
I've recently had to odin my mdl phone back to stock. I haven't done that in a long time. I have root, and supersu, and busybox. The TWRP Manager app is malfunctioning and I cannot use it to install recovery. They list the crash I am experiencing in the play store as a known problem, and they say it will take time to fix. I have a good loki'd copy of twrp but the stock recovery doesn't want to install it. I even changed the name to "update.zip" and it fails. So my problem is I need a recovery. I am considering installing Clockworkmod's ROM Manager to install their recovery, and then using their recovery to install the good loki'd twrp that I want. Does this sound like a good plan? I have been away from this hobby for a while.
plasticglock said:
I hope you won't mind me jumping in your thread.,
I've recently had to odin my mdl phone back to stock. I haven't done that in a long time. I have root, and supersu, and busybox. The TWRP Manager app is malfunctioning and I cannot use it to install recovery. They list the crash I am experiencing in the play store as a known problem, and they say it will take time to fix. I have a good loki'd copy of twrp but the stock recovery doesn't want to install it. I even changed the name to "update.zip" and it fails. So my problem is I need a recovery. I am considering installing Clockworkmod's ROM Manager to install their recovery, and then using their recovery to install the good loki'd twrp that I want. Does this sound like a good plan? I have been away from this hobby for a while.
Click to expand...
Click to collapse
You can flash a recovery zip in a custom recovery. So if you have the loki'd twrp in a zip file, flashing cwm first will work
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
You can flash a recovery zip in a custom recovery. So if you have the loki'd twrp in a zip file, flashing cwm first will work
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks man, that's exactly what I was planning. I remember avoiding CWM last year due to some issue on this device so I just wanted to make sure it wasn't going to do more harm than good. :good:
plasticglock said:
Thanks man, that's exactly what I was planning. I remember avoiding CWM last year due to some issue on this device so I just wanted to make sure it wasn't going to do more harm than good. :good:
Click to expand...
Click to collapse
ROM manager didn't work. It said it installed cwm recovery but it didn't. I was able to install the latest TWRP with this ROM Installer and it worked like a charm! I then installed my custom TWRP from there, rebooted recovery, and installed Danvh's Google edition. I'm setting it up right now. I'm so happy to get my phone back. I just hope the odin flash fixed my problems.
To the OP try ROM installer to get your custom recovery going. Also if you like simple and fast AOSP check out Danvh's google edition rom, but stick to 4.4.4 for now. 5.0 is out but its buggy. Here's a link to the custom version of twrp that I use. https://www.dropbox.com/l/iDQQqlzNbyiFbQrMF4XcRc It's already loki'd so you can flash it if you have any problems with the latest build.
I've spent a week trying to upgrade to lollipop. Finally got it done today and hated it. Tried to downgrade back to 4.4.2 but didn't work.
I'm currently sitting on the samsung colored screen that bootloops. I get beyond the white boot screen. I have twrp 2.8.5.0 installed and working fine. I tried to nandroid restore a 4.4.2 but thats what put me in this bootloop. Any suggestions?
Yes
Update your Bootloader, So you can go to Recovery and Wipe Everything except the External Storage, and try flashing the rom.
DBlackFireD said:
Yes
Update your Bootloader, So you can go to Recovery and Wipe Everything except the External Storage, and try flashing the rom.
Click to expand...
Click to collapse
update bootloader, you mean with a 4.4.2 bootloader? Wouldnt the nandroid already have the correct bootloader?
Isriam said:
update bootloader, you mean with a 4.4.2 bootloader? Wouldnt the nandroid already have the correct bootloader?
Click to expand...
Click to collapse
NO, a nandroid backup does NOT contain bootloader or modem. They must be flashed separately, see the thread below for download links, flash in odin
http://forum.xda-developers.com/showpost.php?p=52210611
wow thank you, didnt know that.
ok so it appears g900az bootloader can't be found on the internet that i see. can i extract it from a stock rom and flash it on its own? i'm thinking that i cannot go down to 4.4.2 from 5.0 on the stock rom.
G900AZTUU3BOG3_G900AZAIO3BOG3_G900AZTUU3BOG3_HOME.tar
COfatboy said:
NO, a nandroid backup does NOT contain bootloader or modem. They must be flashed separately, see the thread below for download links, flash in odin
http://forum.xda-developers.com/showpost.php?p=52210611
Click to expand...
Click to collapse
wait, in TWRP you can include bootloader and modem. I always do this. After using this nandroid to restore, it does not seem to restore the bootloader as I still have the 5.0 bootloader.
Isriam said:
wait, in TWRP you can include bootloader and modem. I always do this. After using this nandroid to restore, it does not seem to restore the bootloader as I still have the 5.0 bootloader.
Click to expand...
Click to collapse
Modem yes bootloader no. When you see the option to backup "boot" in TWRP that is the boot.img which is NOT the bootloader.
COfatboy said:
Modem yes bootloader no. When you see the option to backup "boot" in TWRP that is the boot.img which is NOT the bootloader.
Click to expand...
Click to collapse
interesting, thank you! i went ahead and installed a decent 5.1.1 rom since i needed xposed. so far so good, but i do miss my 4.4.2. i could not get any bootloader to flash for my g900az even the 4.4.2 odin rom.
Gs5
Are you sure I can just flash overy the stock lollipop romantic because I have to try downgrade back to kitkat and it's been trial and error
I have successfully downgraded from 5.1.1 to 5.0
I seem to remember reading once you go to 5.0 you can not downgrade to 4.4.2. Not 100% sure though.
COfatboy said:
I have successfully downgraded from 5.1.1 to 5.0
I seem to remember reading once you go to 5.0 you can not downgrade to 4.4.2. Not 100% sure though.
Click to expand...
Click to collapse
Yes, you can downgrade to 4.4.2, you only have to downgrade your bootloader to use an 4.4.2 android version.
If you are already using an 5.0 Bootloader version, when you try to flash an 4.4.2 android version you get into a LOOP - BOOTLOOP.
Even i didn't know about that thread. Thank you for posting it.
DBlackFireD said:
Yes, you can downgrade to 4.4.2, you only have to downgrade your bootloader to use an 4.4.2 android version.
If you are already using an 5.0 Bootloader version, when you try to flash an 4.4.2 android version you get into a LOOP - BOOTLOOP.
Even i didn't know about that thread. Thank you for posting it.
Click to expand...
Click to collapse
I'm confused by your reply so please clarify. You say you can downgrade your bootloader to 4.4.2 but then your next sentence says if you are using 5.0 bootloader and flash 4.4.2 you get a boot loop. That is my experience also, are we having a translation issue here?
Isriam said:
I'm confused by your reply so please clarify. You say you can downgrade your bootloader to 4.4.2 but then your next sentence says if you are using 5.0 bootloader and flash 4.4.2 you get a boot loop. That is my experience also, are we having a translation issue here?
Click to expand...
Click to collapse
Because from what i researched, the G900AZ came already with an 5.0 Bootloader. Dunno if i got that wrong, but i understood that.
DBlackFireD said:
Because from what i researched, the G900AZ came already with an 5.0 Bootloader. Dunno if i got that wrong, but i understood that.
Click to expand...
Click to collapse
ok that makes sense. my g900az shipped with 4.4.2 a long time ago. i just now started to upgrade it, but didnt realize xposed only worked on 5.1 not 5.0, so it took me awhile to find a 5.1 rom that was good enough. i like stock odex'd roms with xposed. thats hard to find, and custom roms are just too custom for me.