Develop Bugs

Reboot cycle

Can someone please help me? I'm worried my phone may be really screwed up.
I recently rooted my phone using the instructions from this forum and everything went great. I had no problems for a couple days.
Then I installed Titanium Backup and backed up all my apps.
Then I deleted some apps, like Allshare, Dropbox and other bloatware. I still had no problems.
Then I saw that an OTA update was available. I read somewhere that the update can cause problems if stock apps are removed, so I went into Titanium Backup to restore the apps I had deleted. This is where things started to go wrong. When I tried to restore apps, Titanium Backup was hanging and I had to restart the phone. After Dropbox wouldn't restore, I restarted the phone and I'm stuck in a reboot cycle. The phone restarts, I see the usual boot up screens, I see my lock screen, there's a circled i with a cross through it in the notification bar and I can't unlock the phone. How can I get access to my phone back? I'm really upset that this has happened. I thought I was being very careful and this is exactly the kind of thing I was trying to prevent from happening.
Please help.

BraveRobot said:
Can someone please help me? I'm worried my phone may be really screwed up.
I recently rooted my phone using the instructions from this forum and everything went great. I had no problems for a couple days.
Then I installed Titanium Backup and backed up all my apps.
Then I deleted some apps, like Allshare, Dropbox and other bloatware. I still had no problems.
Then I saw that an OTA update was available. I read somewhere that the update can cause problems if stock apps are removed, so I went into Titanium Backup to restore the apps I had deleted. This is where things started to go wrong. When I tried to restore apps, Titanium Backup was hanging and I had to restart the phone. After Dropbox wouldn't restore, I restarted the phone and I'm stuck in a reboot cycle. The phone restarts, I see the usual boot up screens, I see my lock screen, there's a circled i with a cross through it in the notification bar and I can't unlock the phone. How can I get access to my phone back? I'm really upset that this has happened. I thought I was being very careful and this is exactly the kind of thing I was trying to prevent from happening.
Please help.
Click to expand...
Click to collapse
Be Brave, little Robot.
From what you've described, you're not out of luck here. I seriously doubt you've hard-bricked your phone. In order for me to help you, I need you to verify the following:
You can get into your Recovery (either CWM or TWRP).
You can get into download mode.
If these two are true, you're in luck. Below, I've copied a post I made yesterday helping someone else through a similar situation. Some things may be a bit different, but for the most part, it'll help you through you stuff.
Ok, first I'll describe what you did and how that (most likely) messed up your phone. Then I'll describe what you can do to fix it.
Problem
It seems like your original flash of CM10.1 went smoothly. It must have been something to do with your Titanium Backup (TiBu) restores. More than likely, you tried to restore too much. In TiBu, the different apps have different colors: Red, Yellow, Green, and White. In the menu, you can see the following Legend:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
White: User Application. These are apps that you installed from the Play Store or sideloaded by directly installing an apk. These are safe to restore.
Red: System Application. These are system files that heavily rely on which Android version (4.1.x vs. 4.2.x) and whether you're on TW or AOSP. I always try to avoid restoring these backups (even when just upgrading to a newer version of the same Rom). Some people will say that you can restore the Data only for these, but my motto is: caution will help prevent mistakes (ground-shaking, I know).
Green: System Service with Useful Data: These are system apps that have useful information (such as User Accounts, etc.). I treat these the same as Red Backups, but am a bit more likely to restore the data of them (green means go, right?).
Yellow: These backups are system data that can be restored as an xml file. These are inherently safer than the red and green ones, and I say restore away (I always restore my Call Log, Messages, and Wi-Fi Access Points).
The reason you were getting FCs was restoring a red or green backup. This can sometimes work, but has a lot of potential for issues when switching between TW and AOSP Roms. Most likely something in your /system folder is messed up due to restoring an app. Even when you flash a new Rom, it just overwrites items in your System folder, it doesn't wipe /System. So whatever is wrong in your /System folder is still there, regardless of what you flash.
Ok, now that we've identified what's wrong with your phone, we can now help solve it!
Solution/Fixes
Are you able to get into a custom Recovery? If not, you need to use Odin and follow The Rooting Guide to get back to a custom recovery (I recommend TWRP, but CWM is just as good).
Next, you want to download a Rom and put it on your device. I'd recommend (just for now), to get Freeza's stock TW Rom.
Now, before you try to flash this Rom, you'll have to wipe. In order to get rid of the FCs, you'll have to at least wipe System. I'd recommend a full wipe of your Internal SD Card (after backing up anything you want to save), but it's not technically necessary. Afterwards, you can wipe data and cache/dalvik cache.
Then you can flash your Rom. It seems like you know how to do this, but in case you don't, I have previously posted directions over here.
Hope this helps!
Click to expand...
Click to collapse

Be Brave, little Robot.
Click to expand...
Click to collapse
Haha, you're awesome. Thanks for the quick reply. I'm in CWM recovery now. But I don't understand it well enough to use it without instructions. What should I do?

BraveRobot said:
Haha, you're awesome. Thanks for the quick reply. I'm in CWM recovery now. But I don't understand it well enough to use it without instructions. What should I do?
Click to expand...
Click to collapse
I've always given my instructions in TWRP, but the options/settings should be very similar in CWM. In the quoted post below, there are instructions on how to flash a new Rom.
For your situation, I'd recommend wiping system in step 4 below:
Ok, let's start at the very beginning (it's a very good place to start).
Before we get started, I'm going to make the following assumptions:
You successfully rooted your phone through Odin.
You currently have a custom recovery (either TWRP or CWM).
You have a Rom you'd like to flash on either your internal storage or your SDcard (I'd recommend the SDcard, but that's your prerogative).
If either of the first two is not true, I'd recommend going back to qbking77's thread and check out the videos on how to use Odin to gain root and a custom recovery.
If number 3 above is not true, download a ROM (nor someone new to flashing/custom Roms, I'd recommend Freeza's stock rooted Rom, as it's identical to stock TW, but just with Root). Once you download a Rom, check it's md5sum to verify that it's a good download. Copy the file to your SD card and get ready to flash (make sure you have decent battery life left, I try to keep at least 50% or more when flashing Roms, although it shouldn't take too long.
I'll give directions on how to flash a Rom below. The instructions will be for TWRP, but CWM has similar options/settings
Turn your phone completely off (hold down power for 3-5 seconds)
Boot your phone into recovery. Hold Up, Menu, and Power for a few seconds (until SAMSUNG appears on your screen and the phone vibrates)
Make a Nandroid backup. I can't emphasize this enough. In flashing, it's almost a certainty that one time, something will mess up. When that happens, you want to be able to restore a backup. In TWRP, just go into Backup Menu and choose where you want it (internal vs. External storage). It takes my phone a few (5-10) minutes to completely backup my data.
In TWRP, click the wipe button, then system. This will completely wipe the Rom from your phone. Doing this will allow you to get a "clean" install, without any settings or leftover files from your old Rom getting in the way. Instead, you could only wipe data (factory reset), which is good enough for most Roms. I'd still recommend a system wipe, though.
Also while in the Wipe menu, wipe Cache and Dalvik Cache.
Go back to the TWRP main menu.
Click Install, then find your Rom zip file (may have to switch from internal to external storage).
Let TWRP do it's thing.
If you're installing a TW-based Rom, chances are it had gapps already installed. If not, you should now flash the correct gapps package from goo.im. Make sure you're flashing the correct one, as if you don't, your google apps will force close upon use.
Reboot into system and give it time to boot (first boot sometimes takes a couple of minutes).
Set up your phone the way you like.
These should be the directions to follow whenever you flash a new Rom. Some Roms have the Aroma installer, so you'll have more options once you choose to flash the Rom zip, but those are typically easy to follow (and vary from Rom to Rom, so I won't be able to give you a good guide on that).
Hope this helps!
Click to expand...
Click to collapse
I'm going home from work for the night. I'll try to keep up with the thread, but if you have any questions, look over at this thread, I think Miguelcoo1 asked just about every question that can be asked, haha (he's a good guy, I'm just giving him a hard time).

In CWM recovery it says wipe data/factory reset. Is that what I want?

BraveRobot said:
In CWM recovery it says wipe data/factory reset. Is that what I want?
Click to expand...
Click to collapse
Is there an advanced option? Factory rest only wipes Data and Cache, if I recall correctly.

Here are my options:
- reboot system now
- install zip from sdcard
- wipe data/factory reset
- wipe cache partition
- backup and restore
- mounts and storage
- advanced
In advanced, here are my options:
- reboot recovery
- wipe dalvik cache
- wipe battery stats
- report error
- key test
- show log
- fix permissions
- go back
By the way, I have to wait 5 minutes between posts because my account is new. (How do I get rid of that?)

BraveRobot said:
Haha, you're awesome. Thanks for the quick reply. I'm in CWM recovery now. But I don't understand it well enough to use it without instructions. What should I do?
Click to expand...
Click to collapse
Here's the guide for CWM

Ok, it sounds like you're on an old version of cwm. In my Sig, click on flashable and you can flash the newest version of cwm. Then you should have the option to wipe system.
Sent from my SPH-L710 using xda app-developers app

topherk said:
Ok, it sounds like you're on an old version of cwm. In my Sig, click on flashable and you can flash the newest version of cwm. Then you should have the option to wipe system.
Sent from my SPH-L710 using xda app-developers app
Click to expand...
Click to collapse
Alright. I don't mean to sound ungrateful, but this is all very new to me. How do I flash the new CWM onto my phone?

g_money said:
Here's the guide for CWM
Click to expand...
Click to collapse
Oh! from g_money's guide, under "Mounts and Storage" there should be an option to wipe system. Now be aware, wiping system is wiping your Rom, so you won't be able to boot your phone back up to anything besides recovery and download modes (which is no different than you can do right now anyways).

topherk said:
Oh! from g_money's guide, under "Mounts and Storage" there should be an option to wipe system. Now be aware, wiping system is wiping your Rom, so you won't be able to boot your phone back up to anything besides recovery and download modes (which is no different than you can do right now anyways).
Click to expand...
Click to collapse
I am so freaking lost.
What is the end-game here? Am I trying to wipe system and then reflash a new rom? And if so, where does that rom come from? Am I basically starting over like in the root guide using Odin?

BraveRobot said:
I am so freaking lost.
What is the end-game here? Am I trying to wipe system and then reflash a new rom? And if so, where does that rom come from? Am I basically starting over like in the root guide using Odin?
Click to expand...
Click to collapse
If you go into recovery/backup and restore/restore, do you have any backups listed?

g_money said:
If you go into recovery/backup and restore/restore, do you have any backups listed?
Click to expand...
Click to collapse
It says "No files found."
So I guess I didn't back anything up?

Could someone clue me into what I'm trying to do?
Am I trying to flash a new rom or do I need to do something else?
Sorry for being a noob. I'm trying to learn about this stuff, but it's a little difficult. I really appreciate you guys helping me.

BraveRobot said:
Could someone clue me into what I'm trying to do?
Am I trying to flash a new rom or do I need to do something else?
Sorry for being a noob. I'm trying to learn about this stuff, but it's a little difficult. I really appreciate you guys helping me.
Click to expand...
Click to collapse
Yes the instructions topherk gave you where to wipe and flash freezas stock rom. He gave you the links. Make sure you have the rom on your sd card ready to flash.
Transmitted with a portable device using Xparent Blue Tapatalk 2

Ok, that worked. Thanks guys! Everything seems to be back working again.
Does anyone have any idea went wrong with my Titanium Backup? It's kind of useless if it's going to crash my phone when I use it for the main thing it was designed for.
Edit: Actually, I may try to return my phone to stock. Can anyone recommend a guide to un-doing root access and putting everything back completely stock? I think that's probably better for someone with my level of knowledge.

No I think your ok. At some point you restored one bad data or something. The only thing you should ever restore are apps you downloaded from the play store. Never restore any system apps. And samsung apps (bloat) you don't want to delete you just want to freeze.
Transmitted with a portable device using Xparent Blue Tapatalk 2

BraveRobot said:
Ok, that worked. Thanks guys! Everything seems to be back working again.
Click to expand...
Click to collapse
Good to hear
BraveRobot said:
Does anyone have any idea went wrong with my Titanium Backup? It's kind of useless if it's going to crash my phone when I use it for the main thing it was designed for.
Click to expand...
Click to collapse
Reread topherk's previous posts. It's a great guide for understanding Titanium. And Titanium is an awesome program.
BraveRobot said:
Edit: Actually, I may try to return my phone to stock. Can anyone recommend a guide to un-doing root access and putting everything back completely stock? I think that's probably better for someone with my level of knowledge.
Click to expand...
Click to collapse
LOL. I hear ya. But if your phone's working, it's all good right? QBking77 has a video on unrooting here. After what you've been through, you may want to stick around and learn even more?

g_money said:
Good to hear
Reread topherk's previous posts. It's a great guide for understanding Titanium. And Titanium is an awesome program.
LOL. I hear ya. But if your phone's working, it's all good right? QBking77 has a video on unrooting here. After what you've been through, you may want to stick around and learn even more?
Click to expand...
Click to collapse
Yeah, I guess I'll keep it rooted, but I'm going to give things a few days rest after that scare. I need my phone! Maybe I'll come back and mess with it more later.

[PLEASE] Save my life, i messed up everything

I recently have buyed a GNex with a lot of effort, and playing with it i really messed up everything, i'm really a dumbass but need help please.
I just wiped radio and factory partitions without knowing the EFS function, i never had a samsung before and wiped everything in the recovery to install CyanogenMod, and after hours and hours of not getting signal and dont know for what, i get the surprise that my IMEI is a generic one and that don't have factory backup.
Please i'm really crying, desperate for this s****y thing.
Thing I don't do:
* Backup
Things I do
* Wiped /Factory
* Flashed a rom
Every thread that ive read says that if i don't backup the EFS i'm fvcked up, please, i buy my phone 2 days ago
my IMEI number is in the back

santi1993 said:
I recently have buyed a GNex with a lot of effort, and playing with it i really messed up everything, i'm really a dumbass but need help please.
I just wiped radio and factory partitions without knowing the EFS function, i never had a samsung before and wiped everything in the recovery to install CyanogenMod, and after hours and hours of not getting signal and dont know for what, i get the surprise that my IMEI is a generic one and that don't have factory backup.
Please i'm really crying, desperate for this s****y thing.
Thing I don't do:
* Backup
Things I do
* Wiped /Factory
* Flashed a rom
Every thread that ive read says that if i don't backup the EFS i'm fvcked up, please, i buy my phone 2 days ago
my IMEI number is in the back
Click to expand...
Click to collapse
I did the same, without backup. I made it work again.
This will only work if you haven't tried anything on the partitions formatted yet.
Install Hexamob Recovery PRO Undelete from Play. Use the Total Recovery function. This will attempt recovery on an entire partition. I'd suggest first recovering it to another partition as backup. But basically, I did the recovery procedure from /factory straight into /factory.
Reboot e voila. It worked again. Probably will work for you too if all you've done is format /factory in CWM and haven't attempted any fixes on it.

B9anders said:
I did the same, without backup. I made it work again.
This will only work if you haven't tried anything on the partitions formatted yet.
Install Hexamob Recovery PRO Undelete from Play. Use the Total Recovery function. This will attempt recovery on an entire partition. I'd suggest first recovering it to another partition as backup. But basically, I did the recovery procedure from /factory straight into /factory.
Reboot e voila. It worked again. Probably will work for you too if all you've done is format /factory in CWM and haven't attempted any fixes on it.
Click to expand...
Click to collapse
thx for reply, i cant select only /factory to recover, the program itself dont let me make selective recovery, i've to do a full recovery and nothing found with .bin or .md5 files.
sh**ty happens
i cant change the routes, there's no button to make this, is there much disturb if i question u how can do u select this?

Try using Wugfresh's Nexus Root Toolkit.
Then if you want to install Cyanogenmod, go to their site and click get started and follow the instructions.
That's how I installed Cyanogenmod on my Gnex.

I know I probably sound like an arse but in life do only what is necessary and not more.
Also applies to Android, one only needs to wipe /system and /data (without wiping /data/media) on this phone. Why even bother wiping more? Or even better if you use TWRP, its only a single menu to wipe all that is necessary for a ROM change.
When flashing kernels on Nexus devices, tons of people wipe cache and dalvik cache. For what? So far I never ever wiped cache and dalvik for a kernel flash and all is fine for me.
Hope you take it slowly, read, learn and make sure you don't further screw up. All the best fixing!
Oh and never be cocky and be lazy to backup. Nandroid is your best friend as it also would have helped you to restore your efs.
Sent from my Galaxy Nexus using Tapatalk

santi1993 said:
thx for reply, i cant select only /factory to recover, the program itself dont let me make selective recovery, i've to do a full recovery and nothing found with .bin or .md5 files.
sh**ty happens
i cant change the routes, there's no button to make this, is there much disturb if i question u how can do u select this?
Click to expand...
Click to collapse
When you choose total recovery, it should allow you to choose which partition to recover. It can be set to look like this
Click next, confirm, reboot and it should work.

B9anders said:
When you choose total recovery, it should allow you to choose which partition to recover. It can be set to look like this
Click next, confirm, reboot and it should work.
Click to expand...
Click to collapse
hi thanks for support; it wont, it only let me choose: /storage/emulated/legacy and only store it on /storage/emulated/legacy
I try such apps like docomo or EFS trying to recovery the EFS Partition, but none of them workz
Did u set up anything before?
ive tryied it on 4.4 ART gcc 4.8 and i believed that maybe a custom rom affects, so i've installed google factory 4.3, rooted, etc and the same, it cannot let me choose any other thing that /storage/emulated/legacy or i don't know how can i done dat, which version did u have? i'm using 5.0 PRO
akash3656 said:
I know I probably sound like an arse but in life do only what is necessary and not more.
Also applies to Android, one only needs to wipe /system and /data (without wiping /data/media) on this phone. Why even bother wiping more? Or even better if you use TWRP, its only a single menu to wipe all that is necessary for a ROM change.
When flashing kernels on Nexus devices, tons of people wipe cache and dalvik cache. For what? So far I never ever wiped cache and dalvik for a kernel flash and all is fine for me.
Hope you take it slowly, read, learn and make sure you don't further screw up. All the best fixing!
Oh and never be cocky and be lazy to backup. Nandroid is your best friend as it also would have helped you to restore your efs.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
too much thanks to this, i'm applying it in my life right now.
i've learnd it in the worst way, but well, i don't know about samsung EFS, or don't recorded that when installing roms, yes i was lazy to make a backup and now im paying consequences.
right to learn.

I used 5.0.
Don't know why you only get emulated folders. maybe someone else can help with this?

santi1993 said:
hi thanks for support; it wont, it only let me choose: /storage/emulated/legacy and only store it on /storage/emulated/legacy
I try such apps like docomo or EFS trying to recovery the EFS Partition, but none of them workz
Did u set up anything before?
ive tryied it on 4.4 ART gcc 4.8 and i believed that maybe a custom rom affects, so i've installed google factory 4.3, rooted, etc and the same, it cannot let me choose any other thing that /storage/emulated/legacy or i don't know how can i done dat, which version did u have? i'm using 5.0 PRO
too much thanks to this, i'm applying it in my life right now.
i've learnd it in the worst way, but well, i don't know about samsung EFS, or don't recorded that when installing roms, yes i was lazy to make a backup and now im paying consequences.
right to learn.
Click to expand...
Click to collapse
Hey are you rooted? Stock 4.3 isn't rooted. If the ROM you flashed is based on Omni, it isn't rooted either. The app seems like it needs your phone to be rooted. Just flash SuperSU from recovery and then try again.
http://download.chainfire.eu/supersu
And also you may need to buy the PRO version to scan /factory (using Total Recovery option)
Don't worry we all make mistakes, but try to make mistakes that don't cause your entire phone to go crap next time.

B9anders said:
I used 5.0.
Don't know why you only get emulated folders. maybe someone else can help with this?
Click to expand...
Click to collapse
u got the options in the first try? i changed android version and only get the 'sdcard' folders, like photos, movies, etc.
akash3656 said:
Hey are you rooted? Stock 4.3 isn't rooted. If the ROM you flashed is based on Omni, it isn't rooted either. The app seems like it needs your phone to be rooted. Just flash SuperSU from recovery and then try again.
http://download.chainfire.eu/supersu
And also you may need to buy the PRO version to scan /factory (using Total Recovery option)
Don't worry we all make mistakes, but try to make mistakes that don't cause your entire phone to go crap next time.
Click to expand...
Click to collapse
ye, rooted and installed twrp, already done this.
i'm in the pro version, but cant access /factory, there are only 2 checkboxes to switch and only can check emulated sdcard, the buttons below, recovery, back, next, etc... no other options, no options section or anything :S
it seems i'll need to pay a boxer to get my proper IMEI and never touch the phone in this manner way again.
damn me.

If it's a matter of ROM setup, I am using liquidsmooth 4.3. May want to try that and see if you get a differrent result.

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
now installed cm11, same results... dont know which setting im needing to set

santi1993 said:
u got the options in the first try? i changed android version and only get the 'sdcard' folders, like photos, movies, etc.
ye, rooted and installed twrp, already done this.
i'm in the pro version, but cant access /factory, there are only 2 checkboxes to switch and only can check emulated sdcard, the buttons below, recovery, back, next, etc... no other options, no options section or anything :S
it seems i'll need to pay a boxer to get my proper IMEI and never touch the phone in this manner way again.
damn me.
Click to expand...
Click to collapse
I know I sound like I'm nagging but root doesn't persist on every ROM. Each time you flash a ROM you probably need to reflash SuperSU too. And the built in Superuser (koush) that comes with some ROMs plain suck, so avoid that by flashing SuperSU.

akash3656 said:
I know I sound like I'm nagging but root doesn't persist on every ROM. Each time you flash a ROM you probably need to reflash SuperSU too. And the built in Superuser (koush) that comes with some ROMs plain suck, so avoid that by flashing SuperSU.
Click to expand...
Click to collapse
i think the program doesn't have permission to access system files, i'll try flashing supersu right now.
it's there another option to give hexamob full system access?

akash3656 said:
I know I sound like I'm nagging but root doesn't persist on every ROM. Each time you flash a ROM you probably need to reflash SuperSU too. And the built in Superuser (koush) that comes with some ROMs plain suck, so avoid that by flashing SuperSU.
Click to expand...
Click to collapse
still doesnt work :s
i don't know what more could i do
hexamob doesn't show anything except the image, and the other methods doesn't work...
fvck me hard, then, kill me fasst

Umh, I tried hexamob and it shows me /factory so I think that you are doing something wrong or your partitions are really messed.
Try this, wipe system, data and cache, flash last cm11 and askp kernel (just because I tried with this kernel) and try again.
Let me know, good luck
Sent from my Galaxy Nexus using xda app-developers app

Suxsem said:
Umh, I tried hexamob and it shows me /factory so I think that you are doing something wrong or your partitions are really messed.
Try this, wipe system, data and cache, flash last cm11 and askp kernel (just because I tried with this kernel) and try again.
Let me know, good luck
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
i've tried with this cfg, with stock 4.3 +supersu and with aosp 4.4 gcc 4.8, with same results :S
tried to boot with insecure boot image, tried a lot of things, hexamob don't let me choose any other partition
i can access them with ES btw or root explorer
there is a photo with my /factory partition, i'm seeing that i don't have nv_data.bin, only md5.

You could try to send a mail to the app developer, I think that recovering that file is your only option
Sent from my Galaxy Nexus using xda app-developers app

Why not just Odin flash this thing I lost messed my radio and deleted it and used Odin and fixed it right up that's the easiest way I think.
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
---------- Post added at 02:27 PM ---------- Previous post was at 02:20 PM ----------
This is for Verizon http://rootzwiki.com/topic/27050-vzwodin-files-needed-for-odin-winstructions/
Sent from my Galaxy Nexus using XDA Premium 4 mobile app
---------- Post added at 02:27 PM ---------- Previous post was at 02:27 PM ----------
This is smooth guide http://forum.xda-developers.com/showthread.php?t=2065470
Sent from my Galaxy Nexus using XDA Premium 4 mobile app

[Q] Question concirning my filesystem?

Today I was looking into my filesystem, thinking my phone was WAY more full than it should be, and I noticed something that looked odd to me.
It looks like I have multiple entire Android SubSystems?
If that sounds completely strange, please don't laugh at me, let me explain a bit.
I am running Android 4.1.2 M.O.A.R ROM and have done some ROM hopping, but nothing too extensive.
Please look at my attachments, they should explain what I'm saying.
I only posted pictures of 3, but you get the point, I have a total of 6 of these stacked up.
Is this normal?
If this is just a bad case of a dirty filesystem, can someone give me a bit of advice as to how to clean it up?
Whenever I flash a new rom, I'm always sure to wipe all caches and data.
Thank you for your time.

Lordmavick said:
Today I was looking into my filesystem, thinking my phone was WAY more full than it should be, and I noticed something that looked odd to me.
It looks like I have multiple entire Android SubSystems?
If that sounds completely strange, please don't laugh at me, let me explain a bit.
I am running Android 4.1.2 M.O.A.R ROM and have done some ROM hopping, but nothing too extensive.
Please look at my attachments, they should explain what I'm saying.
I only posted pictures of 3, but you get the point, I have a total of 6 of these stacked up.
Is this normal?
If this is just a bad case of a dirty filesystem, can someone give me a bit of advice as to how to clean it up?
Whenever I flash a new rom, I'm always sure to wipe all caches and data.
Thank you for your time.
Click to expand...
Click to collapse
what recovery are you using?

ClockworkMod 6.0.4.5
When I flash a new rom, is it pulling a Windows on me and throwing everything into a dump folder of sorts?

Lordmavick said:
ClockworkMod 6.0.4.5
When I flash a new rom, is it pulling a Windows on me and throwing everything into a dump folder of sorts?
Click to expand...
Click to collapse
Maybe....see i use PhilZ Recovery that has 2 factory reset/wipe options the first one being regular user data and cache wipe which will leave the current rom like if you barely flashed it (i believe TWRP and CWM use this method) the second one is called "full wipe flash new rom" it literally takes the rom away and i use this method before i flash a new rom and i haven't seen these added/old sub android files at all....so i would recommend using Philz from now on or you can just delete those extra files from your internal SD card and your phone will make the ones it needs again also for space check how many backups you have...

6th_Hokage said:
Maybe....see i use PhilZ Recovery that has 2 factory reset/wipe options the first one being regular user data and cache wipe which will leave the current rom like if you barely flashed it (i believe TWRP and CWM use this method) the second one is called "full wipe flash new rom" it literally takes the rom away and i use this method before i flash a new rom and i haven't seen these added/old sub android files at all....so i would recommend using Philz from now on or you can just delete those extra files from your internal SD card and your phone will make the ones it needs again also for space check how many backups you have...
Click to expand...
Click to collapse
I checked my backups first, I only have 1 Nandroid backup placed on my external SD card, so I can't see where I'm using almost 10Gigs of space on my internal storage.
I think I like the Philz Method, but could you first confirm whether or not it has a Nandroid backup equivalent?

6th_Hokage said:
Maybe....see i use PhilZ Recovery that has 2 factory reset/wipe options the first one being regular user data and cache wipe which will leave the current rom like if you barely flashed it (i believe TWRP and CWM use this method) the second one is called "full wipe flash new rom" it literally takes the rom away and i use this method before i flash a new rom and i haven't seen these added/old sub android files at all....so i would recommend using Philz from now on or you can just delete those extra files from your internal SD card and your phone will make the ones it needs again also for space check how many backups you have...
Click to expand...
Click to collapse
Wait, I see, it's simply an advanced version of CWM. I can figure this out myself man, thanks so much for your help!

[Q] What Happened To My Phone

I was running rooted stock version of kit kat. Yesterday afternoon I had Google Music running while doing housework when suddenly the music stopped. I checked the phone and the screen was black and would not turn on. Pulled the battery and then it stuck at the AT&T logo for 30+ minutes. I booted into CWM to perform a factory reset and potentially reinstall the ROM from the external sd card. The factory reset produced the following error.
Code:
--Wiping Data ...
Formatting /data...
Error mounting /data!
Skipping format...
Formatting /cache
Formatting /sdcard/.android_secure...
Error mounting /sdcard/.android_secure!
Skipping format...
Data wipe complete
Fiddled around more with CWM to reset and try to fix. Now, upon reboot, it hands at the Samsung Galaxy Note II screen.
Any help on fixing this so it can at least limp along until my Nexus 6 gets here would be greatly appreciated.

Use Phil touch recovery, and use wipe\clean to install new ROM. Should fix your problem. Also if you are going to a Nexus 6 you should try CM11 when u flash a new ROM.
If you want to use CWM then just format the system and flash a new ROM.
Sent from my GT-N7105 using XDA Free mobile app

I'm unfamilair with Phil Touch recovery.
Can I flash it using JOding on OSX?
ShrekOpher said:
Use Phil touch recovery, and use wipe\clean to install new ROM. Should fix your problem. Also if you are going to a Nexus 6 you should try CM11 when u flash a new ROM.
If you want to use CWM then just format the system and flash a new ROM.
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse

John.T.Erskine said:
I'm unfamilair with Phil Touch recovery.
Can I flash it using JOding on OSX?
Click to expand...
Click to collapse
You can check here
http://forum.xda-developers.com/showthread.php?t=2201860
Sent from my SHIELD Tablet using XDA Free mobile app

Odin doesn't recognize the device. It could be the browser version running on an old macbook pro, but I believe it is the fact that the phone's internal sd card is corrupted somehow.

John.T.Erskine said:
Odin doesn't recognize the device. It could be the browser version running on an old macbook pro, but I believe it is the fact that the phone's internal sd card is corrupted somehow.
Click to expand...
Click to collapse
Have you tried formating the data and system from cwm?
Go into recovery and go to "advanced" and select format system and/or format data.
Sent from my GT-N7105 using XDA Free mobile app

Tried that and received the same error as the OP. Can not mount SD card.
ShrekOpher said:
Have you tried formating the data and system from cwm?
Go into recovery and go to "advanced" and select format system and/or format data.
Sent from my GT-N7105 using XDA Free mobile app
Click to expand...
Click to collapse

Same issue
I'm having the same issue as OP. The phone won't get back to recovery. Won't even go into download mode.......Please help!
Edit: I was so used to working on my wife's phone (Note 1) that I was using the wrong button combination for download mode. I still can't get back to recovery, but I'll be ok once I get home.

Try to flash stock rom in Odin. That should fix any errors but if you're still getting errors there's other stuff to try

absinthesummer said:
Try to flash stock rom in Odin. That should fix any errors but if you're still getting errors there's other stuff to try
Click to expand...
Click to collapse
Not the OP but I just tried this with KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user_low_ship.tar and it did not help.
Here's what I have done thus far:
1. Reflash the stock ROM from sammobile via ODIN
2. Ends in a FAIL on sboot.img
3. Phone says unsupported version (I believe this is due to the Knox locking. I can't downgrade)
4. Reflash recovery-clockwork-touch-6.0.4.3-t0lteatt.img using Heimdall
5. Wipe data, cache, and Dalvik cache (noting the errors regarding the /data partition still occur)
5. Sideload cm-11-20141008-SNAPSHOT-M11-t0lte.zip
6. Sideload gapps-kk-20140606-signed.zip
7. Reboot the phone
8. Stuck in a boot loop on the cyanogenmod logo
Thoughts on where to go from here? Tearing my hair out.

ProjektTHOR said:
Not the OP but I just tried this with KIES_HOME_I317UCAMA4_I317ATTAMA4_578342_REV04_user_low_ship.tar and it did not help.
Here's what I have done thus far:
1. Reflash the stock ROM from sammobile via ODIN
2. Ends in a FAIL on sboot.img
3. Phone says unsupported version (I believe this is due to the Knox locking. I can't downgrade)
4. Reflash recovery-clockwork-touch-6.0.4.3-t0lteatt.img using Heimdall
5. Wipe data, cache, and Dalvik cache (noting the errors regarding the /data partition still occur)
5. Sideload cm-11-20141008-SNAPSHOT-M11-t0lte.zip
6. Sideload gapps-kk-20140606-signed.zip
7. Reboot the phone
8. Stuck in a boot loop on the cyanogenmod logo
Thoughts on where to go from here? Tearing my hair out.
Click to expand...
Click to collapse
Yes that's definitely KNOX bootloader kicking back your flash attempts in odin. MA4 is pretty old firmware. You need MK6 or NE5. Here's where you can get the latest 4.3-4.4.2 firmwares: http://forum.xda-developers.com/galaxy-note-2-att/development/rom-att-i317-ucucne5-mj4-stock-odex-t2802189
This should correct the data issue, if not, you may need to grab a pit file, but usually flashing the latest stock fixes it without requiring all that.
Flash that, re-root, flash new recovery (note: use a newer recovery, cwm sometimes has issues with our device, but twrp has been updated to work with 4.3+ same with philz, if you prefer that UI. Once 4.4.4 comes out, it doesn't play well with cwm, philz, OR older versions of twrp- I had a fight with a note 3 and recoveries yesterday, finally got it going with the latest twrp).
Boot up the device, flash/update your supersu. If you want to install a different rom now, go ahead. Once you have a new recovery installed, format (manually) /system /data /internal storage /cache /dalvik. The internal storage is important b/c it's usually what causes the /data corruption. Always wipe internal storage when switching between roms (or even between an update, I do). I don't usually wipe everything 3 times like some people do, but it is important to wipe the essentials. In twrp, internal storage is an option when wiping. In cwm & philz, you have to go under mounts & storage & it's second up from the bottom (format /data including /data/media> sdcard). Then back out to the main recovery menu and flash your rom, if you have any issues reboot recovery (not system) and re-flash it.
One more thing, make sure you have enough system storage for the gapps. I've run into issues where the rom flashed fine but gapps was too big for the system and didn't flash correctly. Try a slim gapps
Hope this helps, if you have any other questions I'm happy to try to help. We'll get it fixed for ya

Not able to flash other ROMS besides Stock now.......
In my previous post, I was able to get to download mode and flashed back to stock. I thought I was flashing At&t Stock 4.3, but was really flashing At&t 4.1.2 Stock.
I guess it would help to state what happened and the order of things. I'm at work so I don't have the exact versions for each file used, but I'll try my best. I was running DN3 v3.1.1. Something was happening where there was very little space left on my internal storage and I felt like it was time to try a different Rom since I had been on this for a few months as a daily.
1. I flashed BlissStalk with no issues, just didn't care much for the Rom (no hate, just not my cup of tea!)
2. Next I flashed CyanideMod and didn't care for that either. No issues, just wasn't my cup of tea.
3. I then attempted to flash the DS NE5 Rom, using CWM, and it would come on and show the Samsung Galaxy Note II screen and then go black. I had to do a battery pull to get anywhere and then it would come back on and get back to the Galaxy Note II screen and freeze there, or cut off completely again. This is what brought me here to this thread.
I was able to go back to stock 4.1.2, then stock 4.3, and even now on stock 4.4.2. But now I can't flash any Rom at all without getting stuck. I tried to flash DN3's latest and keep getting stuck at the second Samung Screen. I have tried to reboot and tried to reflash as the help says. I am reading through various topics and FAQ pages, but I figured this may be more than any particular Rom issue (I've tried flashing other Roms and I'm getting stuck on those too-either stuck at logos or turning off completely). I have to keep flashing back to stock.
I am researching this, even while at work, but does anyone have any idea what could be wrong?
PS Even though I don't state it above, I followed all flashing directions to a T!

dirtyalphaman said:
In my previous post, I was able to get to download mode and flashed back to stock. I thought I was flashing At&t Stock 4.3, but was really flashing At&t 4.1.2 Stock.
I guess it would help to state what happened and the order of things. I'm at work so I don't have the exact versions for each file used, but I'll try my best. I was running DN3 v3.1.1. Something was happening where there was very little space left on my internal storage and I felt like it was time to try a different Rom since I had been on this for a few months as a daily.
1. I flashed BlissStalk with no issues, just didn't care much for the Rom (no hate, just not my cup of tea!)
2. Next I flashed CyanideMod and didn't care for that either. No issues, just wasn't my cup of tea.
3. I then attempted to flash the DS NE5 Rom, using CWM, and it would come on and show the Samsung Galaxy Note II screen and then go black. I had to do a battery pull to get anywhere and then it would come back on and get back to the Galaxy Note II screen and freeze there, or cut off completely again. This is what brought me here to this thread.
I was able to go back to stock 4.1.2, then stock 4.3, and even now on stock 4.4.2. But now I can't flash any Rom at all without getting stuck. I tried to flash DN3's latest and keep getting stuck at the second Samung Screen. I have tried to reboot and tried to reflash as the help says. I am reading through various topics and FAQ pages, but I figured this may be more than any particular Rom issue (I've tried flashing other Roms and I'm getting stuck on those too-either stuck at logos or turning off completely). I have to keep flashing back to stock.
I am researching this, even while at work, but does anyone have any idea what could be wrong?
PS Even though I don't state it above, I followed all flashing directions to a T!
Click to expand...
Click to collapse
Ok so you've got the ne5 bootloader, so any time you flash stock you'll have to flash that version or above. Stock rom works, but custom ones don't, correct?
What's weird is that the latest dn3 is a modified stock rom so that shouldn't be an issue.
When you flashed stock, you re-rooted and did you update super su? I'm sure you already know but you should update super su's binaries & let it disable Knox, which will set your seLinux from enforcing to permissive. That could potentially be a reason why you can't flash new roms, Knox & selinux interfering with the kernel flash part of the rom(s) you're trying. If you haven't done this you may want to try and then try flashing a custom rom again. If you still encounter issues I'll try to help.
---------- Post added at 12:32 PM ---------- Previous post was at 12:21 PM ----------
John.T.Erskine said:
I'm unfamilair with Phil Touch recovery.
Can I flash it using JOding on OSX?
Click to expand...
Click to collapse
Also, cwm is pretty old and prone to bugs on our devices. However philz is based on cwm and very similar in terms of user interface. It's not as different as twrp is. It has the same style and setup just a few additional tools that cwm doesn't have. It's also more compatible with our devices. If I had to choose one I wouldn't choose cwm, I'd go with philz or twrp for the sake of compatibility.

Thanks. I'll try this when I get home. Yea, once I flashed stock I kept getting Security Notices. I saw this was due to Knox and disabled it but that was a few flash attempts ago. I will follow you steps and let you know how it goes. Once again, thanks.

absinthesummer said:
Yes that's definitely KNOX bootloader kicking back your flash attempts in odin. MA4 is pretty old firmware. You need MK6 or NE5. Here's where you can get the latest 4.3-4.4.2 firmwares: http://forum.xda-developers.com/galaxy-note-2-att/development/rom-att-i317-ucucne5-mj4-stock-odex-t2802189
This should correct the data issue, if not, you may need to grab a pit file, but usually flashing the latest stock fixes it without requiring all that.
Click to expand...
Click to collapse
You are a saint. I'm not sure why I was struggling to find stock 4.4-series firmwares that could be flashed. I was so focused on getting them from sammobile or samware-firmware that I didn't even think to look here. I am going to try this process today and let you know if it works out!

absinthesummer said:
When you flashed stock, you re-rooted and did you update super su? I'm sure you already know but you should update super su's binaries & let it disable Knox, which will set your seLinux from enforcing to permissive. That could potentially be a reason why you can't flash new roms, Knox & selinux interfering with the kernel flash part of the rom(s) you're trying. If you haven't done this you may want to try and then try flashing a custom rom again. If you still encounter issues I'll try to help.
Click to expand...
Click to collapse
I really think this is my issue. I tried updating Super SU by flashing 1.75, but I think that's old. It doesn't show up and when I download it from the PLAY store, it says there is no SU Binary. It's too late to fiddle with this now, but I will mess around with it tomorrow. I think I lost my root and it's not trying to let me get it back. But I don't give up that easy. I was looking through the sticky thread to get the most up to date SU flash, but because it's late and I had a lot going on, this project will have to wait until tomorrow. Thanks for your help and I will let you know what happens tomorrow.

dirtyalphaman said:
I really think this is my issue. I tried updating Super SU by flashing 1.75, but I think that's old. It doesn't show up and when I download it from the PLAY store, it says there is no SU Binary. It's too late to fiddle with this now, but I will mess around with it tomorrow. I think I lost my root and it's not trying to let me get it back. But I don't give up that easy. I was looking through the sticky thread to get the most up to date SU flash, but because it's late and I had a lot going on, this project will have to wait until tomorrow. Thanks for your help and I will let you know what happens tomorrow.
Click to expand...
Click to collapse
Sounds like you've figured it out. 1.75 is very old. Latest (stable) is 2.16. There are also beta versions out. I can link you to the latest flashable in the morning.
You may want to re-root via cf auto root if you can't get it to flash, but if you've got access to recovery a flash to the latest supersu should take... it's just not with 1.75 because those binaries are so outdated, it likely can't overpower enforcing selinux. That has been resolved in newer versions. I'm almost positive you'll be fine with a newer supersu/root.
Edit:
here's the link to 2.16 zip download: http://download.chainfire.eu/589/SuperSU/UPDATE-SuperSU-v2.16.zip
And here's a link to chainfire's thread so you can bookmark it & always have access to the latest:
http://forum.xda-developers.com/showthread.php?t=1538053

absinthesummer said:
Sounds like you've figured it out. 1.75 is very old. Latest (stable) is 2.16. There are also beta versions out. I can link you to the latest flashable in the morning.
You may want to re-root via cf auto root if you can't get it to flash, but if you've got access to recovery a flash to the latest supersu should take... it's just not with 1.75 because those binaries are so outdated, it likely can't overpower enforcing selinux. That has been resolved in newer versions. I'm almost positive you'll be fine with a newer supersu/root.
Edit:
here's the link to 2.16 zip download: http://download.chainfire.eu/589/SuperSU/UPDATE-SuperSU-v2.16.zip
And here's a link to chainfire's thread so you can bookmark it & always have access to the latest:
http://forum.xda-developers.com/showthread.php?t=1538053
Click to expand...
Click to collapse
Hey, this worked for my root. I installed and updated the SU Binary. It got stuck trying to disable Knox, but I rebooted and went right back to it--Knox was disabled in a few seconds! Thanks again. I will wait until I get home to try to flash again because I would hate to end up stuck at work without my phone working and also because..........my name.......my name is Ken. And I.......I'm a flashaholic...........
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

dirtyalphaman said:
Hey, this worked for my root. I installed and updated the SU Binary. It got stuck trying to disable Knox, but I rebooted and went right back to it--Knox was disabled in a few seconds! Thanks again. I will wait until I get home to try to flash again because I would hate to end up stuck at work without my phone working and also because..........my name.......my name is Ken. And I.......I'm a flashaholic...........
Click to expand...
Click to collapse
Awesome! Good luck (and I think we're all flash-aholics)

Thank you for all of your help!!! Flashed the latest DN5 rom and it's working great. I found an issue that might have been preventing me from flashing earlier besides the botched root. My external sd card is having a few issues. A week or so ago it changed to read only and wouldn't let me move any files to or from it. Tonight it wouldn't let me flash the rom, but it worked when moved the rom to the internal storage. So I'm good to go! Can't thank you enough!
Sent from my SAMSUNG-SGH-I317 using XDA Free mobile app

TWRP - Unable to mount storage (Moto Z Play on Nougat)

​I've been using the forums for a while but this is the first time I post on here, so I'm not so sure if I'm posting this in the right place. But I need any help I can get at this point.
​So a while ago I unlocked and rooted my Moto Z Play by flashing TWRP recovery with the fastboot ADB tools. Things were fine, but then I accidentally let the phone do an automatic OTA update. When the phone was going to boot, it went straight to TWRP recovery and after I input my unlock pattern, it gave me a couple lines of text. In these lines was a red line of text saying "Unable to mount storage" and then it would go to the recovery menu. It won't boot past the recovery anymore.
​I looked it up but I can't seem to find clear answers anywhere, as many that I have found have their storage indicating that they have "0mb" when they go to backup. I don't have that problem as all my storage is present and even MTP is enabled. Hopefully someone can help me out here anyway possible.

You can not install OTA updates on ROOTED phone with TWRP recovery.
For working OTA you must have stock recovery and NO ROOT.
If you have XT 1635-02 version, you can reflash your phone using this RSD LITE unbrick tool https://forum.xda-developers.com/ge...orola-usb-drivers-rsd-lite-firmware-t3042687- and you can try to use this firmware for Moto Z Play : https://androidfilehost.com/?fid=673791459329058517
Your phone data will be deteled.

Ax1qwer said:
Your phone data will be deteled.
Click to expand...
Click to collapse
This sounds a bit too hard for me. Usually it is sufficient to flash a firmware with a similar version like you currently have installed, omitting "erase userdata", meaning you do a dirty flash keeping the data.
Alternative, if you want to keep data but erase the phone installing a firmware, you may do backup in twrp and restore data after the phone runs. But keep in mind that a) there were some problems restoring Nandroid backups on Z Play and b) /data/media must be treated separately, which usually is the data you want to keep (mainly: photos and videos you made). You need to enter your phone pin to decrypt data to mount it, maybe that is the missing step.

If you cannot receive OTA updates on a phone with custom recovery, even after (say) restoring a full TWRP System Image backup. . . doesn't that imply, in practice, that you cannot ever return to a stock experience?
I have a stock Z Play with the latest 7.1.1 updates. If I decide to unlock and install LineageOS, there is no way to get back to stock? ever? I mean, I knew about the warranty, that safetynet won't pass, and that I can't re-lock the bootloader. I'm fine with all that. But I thought I could at least get back to the stock ROM, and continue to receive OTA updates. Instead, it sounds like running my backup would be hell: the phone would constantly nag me to install OTA updates, yet if I ever slipped up and said "yes" it would be bricked.
Is there no way to back up the original recovery partition too, so that you can make the OTA updater happy?

mark04 said:
Is there no way to back up the original recovery partition too, so that you can make the OTA updater happy?
Click to expand...
Click to collapse
The are several easy possibilities.
You can get some firmware which you install using fastboot flash. You may decide to only flash stock recovery. For a successful update you need to have system, boot, recovery, logo, oem (from memory, hope I got this right) in exactly the same version.
You can use fastboot boot to start recovery. Then you should be able to restore your recovery backup.
My usual way: if you have stock, never install twrp. Always boot it when needed using fastboot boot. Then you don't need to care about recovery when updating.
If an update does not work, your always can decide to install a full stock ROM, if you omit the command "erase userdata", your data usually survives fine. No guarantee of course, always do a backup. Don't forget data/media where personal things are stored and never covered by Nandroid backup of twrp.

tag68 said:
My usual way: if you have stock, never install twrp. Always boot it when needed using fastboot boot. Then you don't need to care about recovery when updating.
Click to expand...
Click to collapse
Aha---great suggestion, thanks! I would never have thought of that, even though I had to do it on another device once where the bootloader kept overwriting the recovery.
tag68 said:
If an update does not work, your always can decide to install a full stock ROM, if you omit the command "erase userdata", your data usually survives fine. No guarantee of course, always do a backup. Don't forget data/media where personal things are stored and never covered by Nandroid backup of twrp.
Click to expand...
Click to collapse
I was just reading up on how to wipe and install a full stock ROM (factory image). It seems reasonably straightforward, IF you can find the correct image. This worries me a little, because my device is RETUS and there aren't many of those images floating around. None on lolinet.com for example. Some people say to use a RETAIL image but does anyone actually understand how they are different, and what the repercussions might be?

mark04 said:
... and there aren't many of those images floating around. None on lolinet.com for example.
Click to expand...
Click to collapse
You may have a look at firmware.center. They have a lot, but I'm not sure if all are working fine. You may need to do a backup and try. But you nowhere get the safety it's right, because Lenorola does not release signed versions (which would also allow relocking).
Note: For me all the firmwares from there worked by now.
mark04 said:
Some people say to use a RETAIL image but does anyone actually understand how they are different, and what the repercussions might be?
Click to expand...
Click to collapse
Changing update channel is said to be possible, but I never tried it. If you really want it you may try searching a bit in xda forums of similar but older phones how experiences with this are.