PRIMARY QUESTION: I cannot seem to install any "ghost" KitKat or Lollipop ROM on my XT1058. Can anyone please help shed some light on this? I've spent around a combined 12+ hours searching, researching, and tinkering trying to figure this out, but no success. I typically receive a "com.android.systemui" error message or "Unfortunately, System UI has stopped" message. After I acknowledge the message, it pops up again in a second or two. I have to force a shutdown of the phone and recover via TWRP. I've detailed my history and attempts below.
On the CM website, it says something about how "ghost" is a unified OS for every Moto X, except AT&T, since it's not unlockable. With Sunshine, shouldn't I be able to install the "ghost" ROM? Or does it not matter? I hope this isn't a case of, "even though you have an unlocked bootloader, the 'ghost' ROM isn't intended for your version of the phone." If that's true, it looks like all development on the XT1058 has pretty much stopped.
Many thanks, XDA Community, for helping me understand all this!
Secondary Questions:
I recently tried using the feature, "fixing permission" in TWRP thinking it might help with the "ghost" installations. I started getting bootloops when trying to restore to previous ROMs. The only restore that worked was my true original stock backup; the other restore attempts on SlimKat and other stock instances failed. That worries me. While I have successfully restored my phone, does anyone know if I may have screwed up my phone for the long-term?
(Answered by KidJoe; thank you!) Since I unlocked my bootloader at 4.2.2, can I freely upgrade and downgrade stock OSs? i.e., Can I install AT&T's stock 4.4.4 and then downgrade to 4.4.2?
(Answered by KidJoe; thank you!) Why do so many people seem to care to downgrade their stock OS? While I'm sure some may not be happy with some changes that come with upgrades, what could possibly be so "upsetting" that people need to downgrade?
HISTORY
Phone: AT&T Moto X XT1058, non-developer edition
Android: 4.2.2 | No attempt has been made to upgrade the OS beyond 4.2.2
Used Sunshine to unlock the bootloader while still on 4.2.2
Recovery: Installed TWRP v2.8.1.0, and I use TWRP to backup and install old and new ROMs (I think it's version 2.8.3... I never downloaded a version 2.8.1, but that's what the screen says. I'm wondering if the authors just forgot to update the version number in the program.)
Successful ROM installs:
SlimKat build 7 Official, msm8960dt
Cyanogenmod 11 Snapshot M5 msm8960dt (2014-04-05)
Failed ROM installs:
Cyanogenmod 11 Snapshot M12 ghost (2014-11-15)
Cyanogenmod 11 Nightly ghost (2014-12-19)
LiquidSmooth KitKat v3.2 Nightly ghost (2014-10-31)
LiquidSmooth Lollipop v4.0 Nightly ghost (2014-12-20)
Other Notes:
GApps were always installed when available. I also tried not installing them.
cxwong1 said:
Many thanks, XDA Community, for helping me understand all this!
Secondary Questions:
Since I unlocked my bootloader at 4.2.2, can I freely upgrade and downgrade stock OSs? i.e., Can I install AT&T's stock 4.4.4 and then downgrade to 4.4.2?
Why do so many people seem to care to downgrade their stock OS? While I'm sure some may not be happy with some changes that come with upgrades, what could possibly be so "upsetting" that people need to downgrade?
Click to expand...
Click to collapse
I will answer these two....
1. NO you can not. Once you have 4.4.2, 4.4.3 or 4.4.4 on your phone, do NOT attempt to downgrade, even if you have an unlocked bootloader... For more details see what I typed here -> http://forum.xda-developers.com/moto-x/general/4-4-4-downgrade-possibility-t2971847/post57563419 along with the other discussions in that SHORT thread.
2. The older root and write protection disable processes for a Moto X with a locked bootloader (like ATT and Verizon) rely on taking advantage of vulnerabilities in the 4.2.2 w/Camera update rom version, or the 4.4 rom. These processes walk you through downgrading your ROM to 4.2.2 w/Camera update and following a set of steps to upgrade which will keep root and disable write protection. NOTE: It was safe to downgrade from 4.4. to 4.2.2 w/Camera update when following the SlapMyMoto/MotoWpNoMo processes. But that was the only time it was safe!!!!
KidJoe, thank you much!
Does anyone else have any idea about my "systemui" issue?
cxwong1 said:
KidJoe, thank you much!
Does anyone else have any idea about my "systemui" issue?
Click to expand...
Click to collapse
Just got a Moto X 1st gen replacement from Motorola and getting same problem after unlocking/rooting. Have you found a fix for this? Or does anyone know how to fix? Spent all day working on this and its driving me nuts.
syckman said:
Just got a Moto X 1st gen replacement from Motorola and getting same problem after unlocking/rooting. Have you found a fix for this? Or does anyone know how to fix? Spent all day working on this and its driving me nuts.
Click to expand...
Click to collapse
Hey! Nope, I haven't found the answer, unfortunately. I haven't really tried to upgrade my OS since.
cxwong1 said:
PRIMARY QUESTION: I cannot seem to install any "ghost" KitKat or Lollipop ROM on my XT1058. Can anyone please help shed some light on this?
Click to expand...
Click to collapse
I bit the bullet yesterday and paid for the Sunshine bootloader unlock. After replacing the stock bootloader with TWRP and making a backup, I started looking into putting CyanogenMod onto it, as I had just updated a Galaxy Tab 2 7.0 to KitKat (via CyanogenMod 11) last week and it wasn't right that my phone had an older Android build than my tablet. I ran into conflicting information here and elsewhere, but the bottom line:
I have CyanogenMod 11 running on my AT&T Moto X.
More specifically, it's this zipball (remove spaces in next line to bypass the forum's lame link blocking):
https :// download.cyanogenmod.org / get / jenkins / 90775 / cm-11-20141115-SNAPSHOT-M12-ghost.zip
I also tried the latest 12.1 nightly, but while it appears to boot up, it reboots almost as soon as you try to set it up.
One thing that seems to help: before loading any ROM (whether stock, CyanogenMod, or whatever), wipe the flash. I have the ROM and Google Apps files on a flashstick that gets connected through an OTG cable, so I just tell TWRP to wipe everything but OTG storage, restore the ROM, let it boot up, then go back to TWRP to install the Google apps.
(Good thing I had the stock ROM backed up...had to revert to it this morning to back up aCar and Stocard data so I could bring them into CM.)
Starting configuration for my phone: AT&T XT1058, stock 4.4 firmware, rooted with the usual means for doing so, bootloader locked until Sunshine worked its magic.
Related
hi all, I'm a little lost on what to do. I'm trying to update my phone because I'm not receiving texts out of town (need to reset my phone to get them all every time).
My phone has the following:
android 4.2.2 vs98012b (verizon)
rooted w twrp installed (and I'm guessing some sort of ota block since it hasn't updated)
What I want to do is update my phone so it can get texts out of town so I'm thinking OTA? I've searched and found
VS98024A - OTA manual install + Patched Stock Kernels (http://forum.xda-developers.com/showthread.php?t=2699123), is this the way to go?
Is there a flash I can just use? I don't need the latest OTA or Android OS since I'm fine with what I'm using now (although that would be nice too).
anyways, a point in the right direction would be much appreciated. thanks!
ponso said:
hi all, I'm a little lost on what to do. I'm trying to update my phone because I'm not receiving texts out of town (need to reset my phone to get them all every time).
My phone has the following:
android 4.2.2 vs98012b (verizon)
rooted w twrp installed (and I'm guessing some sort of ota block since it hasn't updated)
What I want to do is update my phone so it can get texts out of town so I'm thinking OTA? I've searched and found
VS98024A - OTA manual install + Patched Stock Kernels (http://forum.xda-developers.com/showthread.php?t=2699123), is this the way to go?
Is there a flash I can just use? I don't need the latest OTA or Android OS since I'm fine with what I'm using now (although that would be nice too).
anyways, a point in the right direction would be much appreciated. thanks!
Click to expand...
Click to collapse
You need to wipe your phone to out of the box stock to use that method, if you're gonna wipe clean, you might as well take the OTA's to the current version of android on our phones.
Another option is this - http://forum.xda-developers.com/showthread.php?t=2715408
You would just need to update your baseband following the instructions in the post then install the rom via TWRP.
Either way you're gonna be wiping your phone clean.
Thank you. I went with the 2nd option and my phone is running great with the update.
Although it took awhile to reconfigure everything back.
mjones73 said:
You need to wipe your phone to out of the box stock to use that method, if you're gonna wipe clean, you might as well take the OTA's to the current version of android on our phones.
Another option is this - http://forum.xda-developers.com/showthread.php?t=2715408
You would just need to update your baseband following the instructions in the post then install the rom via TWRP.
Either way you're gonna be wiping your phone clean.
Click to expand...
Click to collapse
guys, can anyone knows how to revert to android 4.4.2 android 5.0.1 with? updated firmware bass headphones disappeared, this problem occurs not only at me. who are important sound in the headphones do not advise upgraded. ASUS disappointed by this update.
ME572C Lollipop 5.0.1? Where? Please share it with us. You can downgrade with MOFD_SDUPDATE.zip and recovery.
BerndHhn said:
ME572C Lollipop 5.0.1? Where? Please share it with us. You can downgrade with MOFD_SDUPDATE.zip and recovery.
Click to expand...
Click to collapse
I tried to downgrade the firmware. but in the new android 5.0.1 bootloader and recovery, and this does not take recovery firmware based on Android 4.4.2. And here is the update on the official website for ME572C, but only TW version, WW firmware not yet available. http://www.asus.com/ru/supportonly/ASUS MeMO Pad (ME572C)/HelpDesk_Download/
Yeah
I installed this night.
Sound is fine.
Tested on Audio Out and Bluetooth, but unfortunately no root possibility yet.
It broke my auto screen rotation. Although this isn't Asus fault it's a bug in lollipop. Also been reported on nexus and moto.
However I don't like the new look and don't like the new notification system or the way quick settings now require two swipes. Quick should mean quick.
Also noticed more lag in starting apps.
Want to revert back to 4.4.2 too
Frisian said:
It broke my auto screen rotation. Although this isn't Asus fault it's a bug in lollipop. Also been reported on nexus and moto.
However I don't like the new look and don't like the new notification system or the way quick settings now require two swipes. Quick should mean quick.
Also noticed more lag in starting apps.
Want to revert back to 4.4.2 too
Click to expand...
Click to collapse
downgrade do not advise to do, I wanted to do this service firmware (which use service centers to flash, free access to this firmware is not), but killed the tablet, it will not turn on and hung on the splash screen Intel Inside. I repeat: who is not updated to 5.0.1 do not advise to do it, a lot of bugs in the new firmware.
Armada17 said:
downgrade do not advise to do, I wanted to do this service firmware (which use service centers to flash, free access to this firmware is not), but killed the tablet, it will not turn on and hung on the splash screen Intel Inside. I repeat: who is not updated to 5.0.1 do not advise to do it, a lot of bugs in the new firmware.
Click to expand...
Click to collapse
Thats awful for you. Can't you get into any recovery anymore? Perhaps flash the 5.0.1. again?
I'm not going to try to downgrade but I wish I hadn't installed lollipop. I really like this tablet and everything worked perfectly. Now I have to rotate the screen manually. I cheked the sensors with a diagnostic tool and they are working fine. It's the software. It isn't known what triggers the bug so it could happen at any time or never. Nice work google.
Hopefully we'll have root and custom mods in the near future.
Armada17 said:
downgrade do not advise to do, I wanted to do this service firmware (which use service centers to flash, free access to this firmware is not), but killed the tablet, it will not turn on and hung on the splash screen Intel Inside. I repeat: who is not updated to 5.0.1 do not advise to do it, a lot of bugs in the new firmware.
Click to expand...
Click to collapse
If you can boot back into the download screen, you can probably reflash the newest firmware.
pWEN said:
If you can boot back into the download screen, you can probably reflash the newest firmware.
Click to expand...
Click to collapse
does not work, bootloader killed, dependent on Intel Inside logo.
Hi, i try at the moment downgrade from the me581cl. It looks good. You can look at my thread Root with downgrade for the intel developer tool.
The highest importent file is the ifwi.bin.
You can it flash with fastboot flash dnx .....
Has anyone found a way to do this? I foolishly manually upgraded my ME572CL (JP SKU) with the WW 5.0.1 firmware. Seemed OK at first but now noticing a lot of bugs which are making it quite unpleasant to use. Lollipop firmware didn't seem to add anything much to the experience anyway, so I would really like to downgrade back to 4.4.2 but MOFD_SDUPDATE fails.
kanagawaben said:
Has anyone found a way to do this? I foolishly manually upgraded my ME572CL (JP SKU) to the WW 5.0.1 firmware. Seemed OK at first but now noticing a lot of bugs which are making it quite unpleasant to use. Lollipop firmware didn't seem to add anything much to the experience anyway, so I would really like to downgrade back to 4.4.2 but MOFD_SDUPDATE fails.
Click to expand...
Click to collapse
I got ME572C(JP sku) and tried almost same things. Android 5.0.1(WW) seems stable on my environment but root is required for my usage. Downgrading with MOFD_SDUPDATE method also failed and now watching TWRP/CWM forums in order to get revised intel atom platform supports for 5.01....
gmaxjp said:
I got ME572C(JP sku) and tried almost same things. Android 5.0.1(WW) seems stable on my environment but root is required for my usage. Downgrading with MOFD_SDUPDATE method also failed and now watching TWRP/CWM forums in order to get revised intel atom platform supports for 5.01....
Click to expand...
Click to collapse
I did a factory reset and the WW 5.0.1 seems stable again now. Would still like to return to a rooted 4.4.2 if possible though.
Any progress on downgrading or rooting ME572C on lollipop? I do have droidboot.img available took out from 4.4 if that might help.
Myuboku said:
Any progress on downgrading or rooting ME572C on lollipop? I do have droidboot.img available took out from 4.4 if that might help.
Click to expand...
Click to collapse
Thanks for interest that. But it seems that we have no ways to revert 5.0x upgrade to 4.4x with method such as reflash partition or something like that because of fastboot oem stuffs to unlock bootloader are completely changed.
The only thing I succeed was reflashing the same version of OTA image WW_V12.14.1.12 downloaded from ASUS site (stupidly I cleared partitions before I confirmed if oem unlock is still valid or not....so I tried this to unblrick my one..). I tried flash partitions with images extracted from older ROM and fastboot server said "Not able to downgrade to KK" or something like that.
Perhaps fastboot server checks version of current vs to be flashed and reject if the version of the software is OLDER THAN CURRENT. This perhaps shows we can inject some hacks into current image, but I have still no progress regarding this idea because I was newbie to IA architecture hacking....I'm guessing that reversing fastboot.img contents shows the way to next milestone....
gmaxjp said:
Thanks for interest that. But it seems that we have no ways to revert 5.0x upgrade to 4.4x with method such as reflash partition or something like that because of fastboot oem stuffs to unlock bootloader are completely changed.
The only thing I succeed was reflashing the same version of OTA image WW_V12.14.1.12 downloaded from ASUS site (stupidly I cleared partitions before I confirmed if oem unlock is still valid or not....so I tried this to unblrick my one..). I tried flash partitions with images extracted from older ROM and fastboot server said "Not able to downgrade to KK" or something like that.
Perhaps fastboot server checks version of current vs to be flashed and reject if the version of the software is OLDER THAN CURRENT. This perhaps shows we can inject some hacks into current image, but I have still no progress regarding this idea because I was newbie to IA architecture hacking....I'm guessing that reversing fastboot.img contents shows the way to next milestone....
Click to expand...
Click to collapse
On one russian forum there is already a person who was able to downgrade to 4.4. Although, he flashed something from "CL" version, instead of "C" so the tablet was unusable, thats why he brought it to Asus service, they did a normal downgrade for him, but it took almost a month.
Myuboku said:
On one russian forum there is already a person who was able to downgrade to 4.4. Although, he flashed something from "CL" version, instead of "C" so the tablet was unusable, thats why he brought it to Asus service, they did a normal downgrade for him, but it took almost a month.
Click to expand...
Click to collapse
Beside the changed bootloader & recovery i believe it is not possible because of the changed partition assignment on LP5.0.1. KK isnt compatible with that anymore i guess and as far as i can see the partition assignment is not renewed and rewritten within any of the prelollipop firmwares again.
tycoo said:
Beside the changed bootloader & recovery i believe it is not possible because of the changed partition assignment on LP5.0.1. KK isnt compatible with that anymore i guess and as far as i can see the partition assignment is not renewed and rewritten within any of the prelollipop firmwares again.
Click to expand...
Click to collapse
Thus, Asus service has .raw service firmware, and they can downgrade to kitkat
Myuboku said:
Thus, Asus service has .raw service firmware, and they can downgrade to kitkat
Click to expand...
Click to collapse
Ya, that might be true.
tycoo said:
Ya, that might be true.
Click to expand...
Click to collapse
Also as i know, there is a person who has service firmwares. As he explained, when flashing service lollipop firmware, it somehow unlocks bootloader(i can be mistaken at this part), and makes it possible to install any android firmware.
I am rooted, unlocked, and S-offed and running a custom GPE+ 5.0.1 ROM. I have an unpinnable notification that says "System Update Downloaded: Android L Upgrade for User/Release-Keys". It is an OTA update obviously, but doesn't even say what version it is. I believe I cannot install it because I am running a custom ROM, is that correct? If not, is there any way to install it? Otherwise, how can I get this notification to stop appearing? The update is ~300MB downloaded and I would love to have that space back. Also I think it is keeping my device awake because I use the Xposed mod "Notification Count" and it says the darn thing has sent out a notification a whopping 463 times since my last reboot - within 3-4 hours!. That is insane.
Any help will be appreciated.
EDIT: Woke up the next morning, and now the notification count for this stupid thing is "999+". WTF. Why does it have to be so insistent? Anybody have a solution to this?
A week passed and no response. Bump. Nobody has any idea how to get rid of this thing??
Koolstr said:
I am rooted, unlocked, and S-offed and running a custom GPE+ 5.0.1 ROM. I have an unpinnable notification that says "System Update Downloaded: Android L Upgrade for User/Release-Keys". It is an OTA update obviously, but doesn't even say what version it is. I believe I cannot install it because I am running a custom ROM, is that correct? If not, is there any way to install it? Otherwise, how can I get this notification to stop appearing? The update is ~300MB downloaded and I would love to have that space back. Also I think it is keeping my device awake because I use the Xposed mod "Notification Count" and it says the darn thing has sent out a notification a whopping 463 times since my last reboot - within 3-4 hours!. That is insane.
Any help will be appreciated.
EDIT: Woke up the next morning, and now the notification count for this stupid thing is "999+". WTF. Why does it have to be so insistent? Anybody have a solution to this?
Click to expand...
Click to collapse
Is updating your custom rom to 5.1+ an option? Already many custom roms were updated to 5.1 even 5.1.1.
Interesting. Last time I checked there wasn't a 5.1 version. But it seems the dev recently implemented an initial version: http://forum.xda-developers.com/ver...m-google-play-edition-lollipop-v1-00-t2963841
The current version of 5.1 of this ROM has some known bugs and I would like to hold off until they are fixed - I like having ambient display. Is it worth waiting until they are fixed, or should I just update now?
Is it safe for me to flash the 5.1 ROM over the 5.0.1 without doing even a cache wipe?
Koolstr said:
Interesting. Last time I checked there wasn't a 5.1 version. But it seems the dev recently implemented an initial version: http://forum.xda-developers.com/ver...m-google-play-edition-lollipop-v1-00-t2963841
The current version of 5.1 of this ROM has some known bugs and I would like to hold off until they are fixed - I like having ambient display. Is it worth waiting until they are fixed, or should I just update now?
Click to expand...
Click to collapse
Don't even know what rom it is so its hard to answer. If you prefer a stable rom they yes, you should wait a little more.
Is it safe for me to flash the 5.1 ROM over the 5.0.1 without doing even a cache wipe?
Click to expand...
Click to collapse
You should ask this one in your rom thread, sometime when the update is considered a major update, its recommend to do a full wipe, in some cases you are fine just updating without wiping. You could do a nandroid backup using your custom recovery (save it on your computer, not just on the phone) try to update without wiping. If its working fine, there is no problem, if not you can wipe your phone and restore your backup.
To disable the notification, I would try to go in settings --> apps --> all, search for the updater service, clear cache of that service and then disable it. Then find where the ota file is stored on your phone and delete it. Not sure if it will work, never tried myselef
Is there a way to do a nandroid backup directly to pc? Because I don't have room on my phone, and TWRP Manager only lets internal backups take place.
For some reason I can't search the apps in my ROM. The notification says it is from Google Play Services but I suspect that is simply routed requests from the actual updater service. Do you know what the name of the service is, so I can find it? I have a crazy number of apps and can't find it.
Hi Koolstr,
I know this thread is old, but wanted to let you know I am on an unlocked and rooted HTC One (m7) S-On. I am using TWRP and can backup to external storage using a Micro USB Powered Micro USB Host OTG cable, which I purchased from Amazon.
I am running:
Android version: 5.1
Rom: Google-Plus-Edition-LP_m7_v3.2_072915
Kernel: 3.4.10-NuK3rn3l-Lollipop_v8.00
I am getting a similar Android System Update: Android L upgrade for user/release-keys. I cannot get it to go away. I made a complete nandroid backup and then proceeded applying the update. It will reboot the phone into TWRP recovery and do nothing. The update goes away for a few days and then it comes back. I have tried to look for a way to disable the update, but I am at a stand still. If anyone knows that would be great.
Best,
manderson706
It's something that santod did. I believe there's a post in his topic with the fix. Or just flash the updated GPE from santod
Hello All,
I've just flashed the AOSP ROM for THEA XT1072 and I'm very happy with the results, it's exactly the return to stock I was looking for. However, I have a few questions I hope somebody can kindly answer:
1) Is it possible to re-lock the bootloader once an unofficial ROM has been installed? My device is telling me I need an officially signed ROM and refusing to relock when I do "mfastboot oem lock".
2) What's the update process for installing later builds of the AOSP ROM? Is it just a case of checking back here and re-flashing the whole new image as and when it is released? Or is there an OTA update alternative?
3) Is the current AOSP build 20150828 inclusive of the various security fixes that Google rolled out recently (Stagefright etc.)? I know they were released to AOSP source code but that presumably doesn't guarantee they are in the current THEA 20150828 AOSP build yet.
Thanks
sharkyblunt
sharkyblunt said:
Hello All,
I've just flashed the AOSP ROM for THEA XT1072 and I'm very happy with the results, it's exactly the return to stock I was looking for. However, I have a few questions I hope somebody can kindly answer:
1) Is it possible to re-lock the bootloader once an unofficial ROM has been installed? My device is telling me I need an officially signed ROM and refusing to relock when I do "mfastboot oem lock".
2) What's the update process for installing later builds of the AOSP ROM? Is it just a case of checking back here and re-flashing the whole new image as and when it is released? Or is there an OTA update alternative?
3) Is the current AOSP build 20150828 inclusive of the various security fixes that Google rolled out recently (Stagefright etc.)? I know they were released to AOSP source code but that presumably doesn't guarantee they are in the current THEA 20150828 AOSP build yet.
Thanks
sharkyblunt
Click to expand...
Click to collapse
1. No.
2. Just flash rom without any wipes as there's no OTA functionality.
3. Yes.
Thanks Luk. Great work on this ROM. It flies compared to the stock 5.0.2 and no issues yet.
Only one issue so far, after 24 hours of using it. I'm getting a battery drain whereby Miscellaneous is by far the biggest culprit (currently at 22% since taking it off charge this morning). It was the same yesterday too, and I rebooted it last night just in case it was a hangover from the original flashing, but it's still draining faster than stock 5.0.2 did.
The AOSP-5.1.1-20150905 build is perfect (once I'd erased the modemst1 & modemst2 to get GPS working). No issues whatsoever from me. Great work.
By the way, I'm commenting here as I've not done enough posts to participate in the developers sub-forum.
Hi all,
I am having issues with my Bluetooth and GSM. I am considering trying to downgrade from OOS 4.1.3 to 4.1.1. I am completely stock, not rooted and don't even have TWRP.
Would appreciate some clarification to the following questions:
1) Can I downgrade by just flashing the official full 4.1.1 zip found in OP website?
2) Should I only flash the modem zip? And if so, can I use 4.1.1 modem while having 4.1.3 installed?
3) Since 4.1.1 already has nougat 7.1.1, is 1) also safe for further downgrades, for example, directly to 4.0.4?
Thanks.
Best regards,
Oldiamond
If your bootloader is locked, you can't downgrade (unless you exploit the security vulnerability from a few weeks back).
If your bootloader is unlocked, use TWRP or fastboot to clean flash whatever version of OOS you want.
You should consider flashing the latest open beta release, I think it's already fixed over there plus there are some Extra goodies and its stable as ****
Anova's Origin said:
If your bootloader is locked, you can't downgrade (unless you exploit the security vulnerability from a few weeks back).
If your bootloader is unlocked, use TWRP or fastboot to clean flash whatever version of OOS you want.
Click to expand...
Click to collapse
Pharrax said:
You should consider flashing the latest open beta release, I think it's already fixed over there plus there are some Extra goodies and its stable as ****
Click to expand...
Click to collapse
Thanks to both. I am this close to send it back to RMA, as I did not install anything other than 4.1.3, and didn't even unroot it. I don't know... perhaps by sending it back without ever installing TWRP or unlocking anything would provide more feedback to the manufacturer, other than saying "damn guy, started fiddling with the phone and ROMs, and here's the result".
Regarding the beta, I initially considered avoiding it because i read in the forums about issues such as sometimes alarms not ringing. I figure that my boss wouldn't like that
Going back from BETA to regular version also requires TWRP?
Best regards,
Old
oldiamond said:
Thanks to both. I am this close to send it back to RMA, as I did not install anything other than 4.1.3, and didn't even unroot it. I don't know... perhaps by sending it back without ever installing TWRP or unlocking anything would provide more feedback to the manufacturer, other than saying "damn guy, started fiddling with the phone and ROMs, and here's the result".
Regarding the beta, I initially considered avoiding it because i read in the forums about issues such as sometimes alarms not ringing. I figure that my boss wouldn't like that
Going back from BETA to regular version also requires TWRP?
Best regards,
Old
Click to expand...
Click to collapse
Alarm issues were fixed, also it never happened to me I and I've been on beta a long time i think on the official page there are the steps to switch between stable and beta. I don't think it requires twrp but don't take my word for it.