Related
Hi,
I have an lg c800 -- mytouch q by lg
I rooted it yesterday and removed all the bloat. I also installed several root only apps to optimize the phone.
It ran smoother than even right out of the box.
So, I figured it be a good idea to backup the rom, and maybe later try cyanogenmod... So I installed Rom Manager by clockworkmod
It said i needed to install clockwork recovery rom. I went in there but it said my device was unsupported (only like 12 were) so I backed out,
and stupidly hit TWRP listed under "Recovery Already Installed". (thinking that meant what options I had to SETUP a recovery/backup)
I hit backup rom. almost instantly the phone restarted. After the bios, but before android it went to a screen with a box, and an arrow pointing from the inside of the box to the little android man. Then went to the regular android boot screen.
It does this every reboot now. The SuperSU is still there, whenever Rom Manager (which I have to reinstall each reboot) asks for root access I get that dialog box, so it hasn't actually hard reset the phone I don't think. But all the user data, contacts, apps, wifi passwords, google id "(to access Play) get wiped out.
I understand what I did wrong. I think I understand what its doing (booting to the factory rom as it was, and I can't set it to stop doing it each reboot)
What I need help with is getting back, if possible, to what I had previously, among other things, I had a bunch of tasker profiles and notes that will be time consuming to replace.
Thank you for your help.
EDIT: SuperSU is now listed among the factory installed apps. This is unchanged each reboot.
Question: If I unroot the phone what that invalidate Rom Managers ability to run before android boots?
where the people at?
dosmastr said:
where the people at?
Click to expand...
Click to collapse
going off of this page:
http://forum.xda-developers.com/showthread.php?t=1752704
for cwm recovery
drivers are all installed (I was able to root phone)
but the adb devices command comes up empty.
what gives?
dosmastr said:
going off of this page:
http://forum.xda-developers.com/showthread.php?t=1752704
for cwm recovery
drivers are all installed (I was able to root phone)
but the adb devices command comes up empty.
what gives?
Click to expand...
Click to collapse
OK so its not in the guide, but one is to exit the shell BEFORE keying adb devices. it does show.
but sadly I don't think this gets me closer to fixing what is broken.
Can anybody at least tell me if my stuff is still there or gone?
I have the impression that the boot loader is grabbing the stock rom and just expanding it and running it each boot, but that the old functional rom is still there but being unused --- like a dual boot type thing.
Am I off in left field here or?
dosmastr said:
Can anybody at least tell me if my stuff is still there or gone?
I have the impression that the boot loader is grabbing the stock rom and just expanding it and running it each boot, but that the old functional rom is still there but being unused --- like a dual boot type thing.
Am I off in left field here or?
Click to expand...
Click to collapse
more info: the bloat from the original rom is still gone, and SuperSU is intact and functional
Chui says its some flag in CWM that isn't getting cleared when the device boots.
I'm just trying to get the data my apps help at this point.
cmon phone nerds i still need some help!
no help.
The original ROM of your phone got modified after you rooted, hence no bloat and SuperSU intact even after many wipes.
I suggest re installing the factory ROM again, including the bootloader, radio and other stuff. That ought to fix the issue.
What phone do you have ?
So when it was modifying the rom that was running at the time, also the recovery rom was modified?
how do you reinstall factory rom if the phone never enters fastboot?
I'm all about wiping the bootloader (so it STOPS running recovery) but I have only made a little progress in finding how to do that without fastboot.
What I can do is run a root viewing file manager. I even found the log for the recovery it keeps running. But not what to kill so that it STOPS recovering.
Phone is LG C800DG
The LG rom update software has a recovery option but that didn't work.
One youtube video
http://www.youtube.com/watch?v=nDFO6H1XObI
Says I can get around this by using a flash utility the installs as an apk. I doubt I'll find one compatible with this phone though as support is very limited.
looks like everything out there says I need a 3rd party recovery already flashed...so that I can flash a stock rom.
sounds like the damn chicken and egg to me, to get stock fixed you need 3rd party but since you have stock you cant get 3rd party
It seems to be a general problem with your set as many others too have posted the same issue.
For stock ROM this should work.
http://forum.xda-developers.com/showthread.php?t=1825818
And a flashing guide
http://blog.androidia.net/8/how-to-flash-stock-lg-rom/
You can also see these for CM9
http://wiki.cyanogenmod.org/w/C800_Info
and
http://forum.xda-developers.com/showthread.php?t=1801622
Dumb e3 recovery. There been any updates on the cwm recovery? Thing takes forever to backup and restore rom
OK. So. I've been encountering nothing but problems since I received my Huawei Ascend P2 phone.
To begin with -
I bought the phone for the sole purpose of it being 4G/LTE. When I got it, I couldn't figure out how to get it, so I contacted Three and was told that my phone had to be 4.3 - it was running 4.1.2.
When I tried to get 4.3 through whatever means, it stopped working.
I tried to do a complete factory reset and now I'm getting many more problems -
I keep getting errors that anything Google related has stopped working (especially Google keyboard).
My contacts won't auto-sync, despite me having my Google account synced up with it.
The icons at the bottom of the screen (back, home, settings/whatever else) won't light up and the home button isn't working.
It's a different loading screen than normal - before it was a Huawei Ascend splash screen, now it just says "Android".
It is not being detected by my laptop whatsoever.
When I try and download anything using a browser, it says "starting download" but nothing works.
So, anyone have a solution? It is driving me demented. And all because I wanted bloody 4G.
boneyarsebogman said:
OK. So. I've been encountering nothing but problems since I received my Huawei Ascend P2 phone.
To begin with -
I bought the phone for the sole purpose of it being 4G/LTE. When I got it, I couldn't figure out how to get it, so I contacted Three and was told that my phone had to be 4.3 - it was running 4.1.2.
When I tried to get 4.3 through whatever means, it stopped working.
I tried to do a complete factory reset and now I'm getting many more problems -
I keep getting errors that anything Google related has stopped working (especially Google keyboard).
My contacts won't auto-sync, despite me having my Google account synced up with it.
The icons at the bottom of the screen (back, home, settings/whatever else) won't light up and the home button isn't working.
It's a different loading screen than normal - before it was a Huawei Ascend splash screen, now it just says "Android".
It is not being detected by my laptop whatsoever.
When I try and download anything using a browser, it says "starting download" but nothing works.
So, anyone have a solution? It is driving me demented. And all because I wanted bloody 4G.
Click to expand...
Click to collapse
I think we need some more info on the attempt to upgrade via whatever means. What steps / guide were you following? Did you install a custom rom? If so, what rom and what recovery are you using? From a few minutes of searching around, it seems that there is no official 4.3 update for the phone, and just being ON 4.3 itself will not automagically enable LTE service as this has much to do with the radio/baseband used as much as the actual operating system and that will not get updated via a custom rom (99.999% of the time unless SPECIFICALLY stated). Seems like they are working on an LTE capable update/patch for 4.1.2 soon according to this: http://forum.xda-developers.com/showpost.php?p=50495570&postcount=162 (that post is part of a thread about your phone on a UK carrier so should be pertinent).
es0tericcha0s said:
I think we need some more info on the attempt to upgrade via whatever means. What steps / guide were you following? Did you install a custom rom? If so, what rom and what recovery are you using? From a few minutes of searching around, it seems that there is no official 4.3 update for the phone, and just being ON 4.3 itself will not automagically enable LTE service as this has much to do with the radio/baseband used as much as the actual operating system and that will not get updated via a custom rom (99.999% of the time unless SPECIFICALLY stated). Seems like they are working on an LTE capable update/patch for 4.1.2 soon according to this: http://forum.xda-developers.com/showpost.php?p=50495570&postcount=162 (that post is part of a thread about your phone on a UK carrier so should be pertinent).
Click to expand...
Click to collapse
Thank you for your reply.
I'll talk you through the steps I took as much as I can.
Firstly I rooted the phone using eRoot, which did work and allowed root access.
I then downloaded P2Tools, which was obtained from this thread and it allowed me to put CWM on it.
Once this was done, I attempted to put CM 10.2 on it, but kept getting a Status 7 error. Some quick Googling later, I discovered this video, which showed how to solve it.
When I followed the steps on there, I kept getting a Status 0 error.
That was when I started to encounter those problems, so I wiped everything I could, even system, but that part failed.
And that's about it.
boneyarsebogman said:
Thank you for your reply.
I'll talk you through the steps I took as much as I can.
Firstly I rooted the phone using eRoot, which did work and allowed root access.
I then downloaded P2Tools, which was obtained from this thread and it allowed me to put CWM on it.
Once this was done, I attempted to put CM 10.2 on it, but kept getting a Status 7 error. Some quick Googling later, I discovered this video, which showed how to solve it.
When I followed the steps on there, I kept getting a Status 0 error.
That was when I started to encounter those problems, so I wiped everything I could, even system, but that part failed.
And that's about it.
Click to expand...
Click to collapse
K. So you are still on the stock rom, rooted, with CWM recovery (which version?), and after you attempted to wipe /system, it failed to wipe (what was the error message there?), and now it boots and has all kinds of weird glitches? First thing to try would be to go back to CWM and wipe Cache and Dalvik Cache and then Fix Permissions. This MIGHT help. If it doesn't then you will just probably want to throw a stock rom back on there to get back to running right again.
es0tericcha0s said:
K. So you are still on the stock rom, rooted, with CWM recovery (which version?), and after you attempted to wipe /system, it failed to wipe (what was the error message there?), and now it boots and has all kinds of weird glitches? First thing to try would be to go back to CWM and wipe Cache and Dalvik Cache and then Fix Permissions. This MIGHT help. If it doesn't then you will just probably want to throw a stock rom back on there to get back to running right again.
Click to expand...
Click to collapse
I've wiped the Caches and Dalvik Cache and can't seem to find "Fix Permissions". I did some searching and it seems this feature was removed from CWM? I'm running v6.0.3.7 of CMW.
When I try to format the system, it says
E:format_volume failed to unmount "/system"
Error formatting /system!
Weird, they did take it out. Koush said it was a placebo. Which normally I would take as law, if it weren't for many times I have ran fix permissions and it caused apps that were force closing to not force close anymore. But whatever, if you wanna try, flash this: http://db.tt/9aWdF8Rp. It'll either help fix something, or do nothing. Won't make it any worse. If it can't mount to format though, it's either or a bug with CWM for your device, or after factory reset, reboot recovery and try again. But you really don't want to wipe /system unless you have a nandroid or another rom on your storage that is accessible.
Thanks so much for your help so far. Took me ages to figure out how to get that file on my phone, but I managed to do it. I then installed zip from recovery mode and chose the fix_permissions. Then reboot and it asked me to root the phone again. It's now upgrading and hopefully it will work now.
It is still saying "Unfortunately, Android keyboard has stopped" and other things. What do you reckon I can do now? You're right, it seems like I can't make it any worse.
boneyarsebogman said:
Thanks so much for your help so far. Took me ages to figure out how to get that file on my phone, but I managed to do it. I then installed zip from recovery mode and chose the fix_permissions. Then reboot and it asked me to root the phone again. It's now upgrading and hopefully it will work now.
It is still saying "Unfortunately, Android keyboard has stopped" and other things. What do you reckon I can do now? You're right, it seems like I can't make it any worse.
Click to expand...
Click to collapse
Ok. So looks like first thing to check is to see WHICH version of the P2 you have because it seems like there are at least 2 different sub versions of it. The P2-6070 and the P2-6011. Please go to Settings / About Phone/Device and let me know all the software info there.
Also, have you unlocked the bootloader (I'm guessing so since you have recovery, but just checking)?
I found some more info on how to get you back up and running, but want to confirm the system version so everything goes as smoothly as possible. There's a new update that just came out not too long ago that people are saying LTE works on, so hopefully we can get you to that point.
es0tericcha0s said:
Ok. So looks like first thing to check is to see WHICH version of the P2 you have because it seems like there are at least 2 different sub versions of it. The P2-6070 and the P2-6011. Please go to Settings / About Phone/Device and let me know all the software info there.
Also, have you unlocked the bootloader (I'm guessing so since you have recovery, but just checking)?
I found some more info on how to get you back up and running, but want to confirm the system version so everything goes as smoothly as possible. There's a new update that just came out not too long ago that people are saying LTE works on, so hopefully we can get you to that point.
Click to expand...
Click to collapse
Mine is the P2-6011.
Swear if we get this working, never changing anything ever.
Yes, the bootloader is unlocked.
Alright, so here is a link for the newest firmware for your phone :
http://huaweidevices.ru/ROM4221/P2/...R001C00B038CUSTC19D001_United_Kingdom_H3G.rar
Need to be on stock recovery. Unpack the rar file and put the whole folder /dload on the root of the SD card. This has the update.app that should take care of everything for you. Turn off the phone and turn it on by holding Vol + and - and Power together. This is supposed to boot it into the mode to take care of the update for you.
If you don't wanna go back to complete stock, I have another way that involves switching to TWRP recovery and restoring a rom via nandroid restore. If you'd prefer that, lemme know and I'll shoot you the links.
es0tericcha0s said:
Alright, so here is a link for the newest firmware for your phone :
http://huaweidevices.ru/ROM4221/P2/...R001C00B038CUSTC19D001_United_Kingdom_H3G.rar
Need to be on stock recovery. Unpack the rar file and put the whole folder /dload on the root of the SD card. This has the update.app that should take care of everything for you. Turn off the phone and turn it on by holding Vol + and - and Power together. This is supposed to boot it into the mode to take care of the update for you.
If you don't wanna go back to complete stock, I have another way that involves switching to TWRP recovery and restoring a rom via nandroid restore. If you'd prefer that, lemme know and I'll shoot you the links.
Click to expand...
Click to collapse
If I ever meet you I definitely owe you a drink. Did exactly as you said and everything (from what I can tell) is working.
It's one of the things I love about Android phones - unless you do some serious damage to it physically, for the most part it is fixable.
So, thanks button isn't enough - you saved me giving up and buying a new phone
*Hi Five* Glad all is well!
But yea, I do this for a living. Seriously. Helping people on here is how I stay sharp. lol
getting a gateway 504 error from link to firmware, would love to get this update working as i keep getting a notification on phone saying update available but it wont work
boneyarsebogman said:
Thank you for your reply.
I'll talk you through the steps I took as much as I can.
Firstly I rooted the phone using eRoot, which did work and allowed root access.
I then downloaded P2Tools, which was obtained from this thread and it allowed me to put CWM on it.
Once this was done, I attempted to put CM 10.2 on it, but kept getting a Status 7 error. Some quick Googling later, I discovered this video, which showed how to solve it.
When I followed the steps on there, I kept getting a Status 0 error.
That was when I started to encounter those problems, so I wiped everything I could, even system, but that part failed.
And that's about it.
Click to expand...
Click to collapse
Can you post the link of the CM 10.2 rom For huawei P2.
I search for a long long time. but still dosnt found a rom.
Thx
Sorry for digging this up but does someone have the stock ROM of the P2? Im stuck like the fella who started this thread and havent found the stock ROM anywhere.
Thanks for the attention.
Forgive my novice status with both my first Android phone and this site. Galaxy S6 which I rooted using Odin and I believe a kernel it was, from here.
If I run the os upgrade from Smartswitch, what effect will that have one the phone as far as being rooted and all the stuff I've done since being rooted. Thank you very much.
If you update, you will lose root. I would not update via Smart Switch, being that you are rooted with a custom kernel. Your best bet would be to update via Odin. Check the subforum here @ xda for your variant of the S6 for further info. You should find what you need in the General forum of that subforum.
es0tericcha0s said:
If you update, you will lose root. I would not update via Smart Switch, being that you are rooted with a custom kernel. Your best bet would be to update via Odin. Check the subforum here @ xda for your variant of the S6 for further info. You should find what you need in the General forum of that subforum.
Click to expand...
Click to collapse
Thank you sir. Is it simply a matter rerooting the device? Or will every other change I made from root be gone too?
It will wipe your phone, so you will have to redo any mods or settings.
es0tericcha0s said:
It will wipe your phone, so you will have to redo any mods or settings.
Click to expand...
Click to collapse
It wipes the phone every time you do an operating system update? Why would anybody ever do it unless something wasn't working? Unless it's only when rooted? I have good pc skills and some understanding of Linux even, but man I have a lot to learn about these phones.. What about Smart Switch backups? It wipes the phone, how close to before the update will that get somebody? I don't have time to research all this. I may just leave it. This update I'm talking about is a gigabyte btw. That seems pretty huge for a phone.
It wipes the phone when you update via Odin (unless modded by a dev to not wipe for some versions). The reason that this needs to be done is that when you are rooted and have changed system files, OTA updates usually cause issues like bootloops / soft brick. Typically when you have a Samsung with a modded kernel and system, the regular Samsung tools like Kies and Smart Switch fail. Your results may vary, but I would have the firmware downloaded to reload via Odin in case that does not work. I am not familar with Smart Switch as it just came out for the S6 and newer stuff and I have never had use for Samsung's tools like that because I prefer to use Google and Titanium Backup to backup and restore my apps, contacts, texts, call logs, etc. As far as the updates go, 1 GB is actually kind of small for newer versions. It's probably bigger once unzipped. Some newer phones have systems that are well over 2 GBs. Most people here usually update via custom rom as it's easy to do on the phone once you have a working custom recovery and doing a factory reset there will not wipe the internal storage @ /data/media. If you prefer to be stock rooted, there most likely is a version already posted in the subforum for your phone. If you are updating whole Android versions and not minor updates, it might be required to install additional firmware files with Odin or Chainfire's Flashfire tool. If so, the developer will mention that in the OP of the thread.
es0tericcha0s said:
It wipes the phone when you update via Odin (unless modded by a dev to not wipe for some versions). The reason that this needs to be done is that when you are rooted and have changed system files, OTA updates usually cause issues like bootloops / soft brick. Typically when you have a Samsung with a modded kernel and system, the regular Samsung tools like Kies and Smart Switch fail. Your results may vary, but I would have the firmware downloaded to reload via Odin in case that does not work. I am not familar with Smart Switch as it just came out for the S6 and newer stuff and I have never had use for Samsung's tools like that because I prefer to use Google and Titanium Backup to backup and restore my apps, contacts, texts, call logs, etc. As far as the updates go, 1 GB is actually kind of small for newer versions. It's probably bigger once unzipped. Some newer phones have systems that are well over 2 GBs. Most people here usually update via custom rom as it's easy to do on the phone once you have a working custom recovery and doing a factory reset there will not wipe the internal storage @ /data/media. If you prefer to be stock rooted, there most likely is a version already posted in the subforum for your phone. If you are updating whole Android versions and not minor updates, it might be required to install additional firmware files with Odin or Chainfire's Flashfire tool. If so, the developer will mention that in the OP of the thread.
Click to expand...
Click to collapse
It just occurred to me. Firmware IS the Android OS on these phones. That's not the same as a kernel though? With the regular Linux os it isn't. Forgive my ignorance. Like I say this is my first one.
Unfortunalely, firmware is one of those terms that can mean a few different things depending on the situation (like flashing). Firmware in this instance refers to the bootloader and modem files as well for Samsungs. If you don't have the bootloader and modem files (which roms do not install) correctly matched to the OS then you might have issues like not being able to boot or cell service issues.
es0tericcha0s said:
It wipes the phone when you update via Odin (unless modded by a dev to not wipe for some versions). The reason that this needs to be done is that when you are rooted and have changed system files, OTA updates usually cause issues like bootloops / soft brick. Typically when you have a Samsung with a modded kernel and system, the regular Samsung tools like Kies and Smart Switch fail. Your results may vary, but I would have the firmware downloaded to reload via Odin in case that does not work. I am not familar with Smart Switch as it just came out for the S6 and newer stuff and I have never had use for Samsung's tools like that because I prefer to use Google and Titanium Backup to backup and restore my apps, contacts, texts, call logs, etc. As far as the updates go, 1 GB is actually kind of small for newer versions. It's probably bigger once unzipped. Some newer phones have systems that are well over 2 GBs. Most people here usually update via custom rom as it's easy to do on the phone once you have a working custom recovery and doing a factory reset there will not wipe the internal storage @ /data/media. If you prefer to be stock rooted, there most likely is a version already posted in the subforum for your phone. If you are updating whole Android versions and not minor updates, it might be required to install additional firmware files with Odin or Chainfire's Flashfire tool. If so, the developer will mention that in the OP of the thread.
Click to expand...
Click to collapse
What I'm wondering is if there's any to have this galaxy s6 just like it is now after many hours of tweaking after one of these updates. I couldn't make heads or tails out of Titanium update.
You are being very helpful sir. Thank you.
Depends on what tweaks you've done and which update that it is. If it is a minor security update, then usually someone will post a flashable via custom recovery version and often you can get away with installing that over your current system while just wiping cache and dalvik cache. If it is a major update, like when Marshmallow comes out, it would benefit you to do a factory reset before updating. Yea, it sucks having to set up your phone again, though with all the tools available, it's really not that bad, but better to start fresh instead of wondering if the phone is slow or buggy because you didn't.
es0tericcha0s said:
Depends on what tweaks you've done and which update that it is. If it is a minor security update, then usually someone will post a flashable via custom recovery version and often you can get away with installing that over your current system while just wiping cache and dalvik cache. If it is a major update, like when Marshmallow comes out, it would benefit you to do a factory reset before updating. Yea, it sucks having to set up your phone again, though with all the tools available, it's really not that bad, but better to start fresh instead of wondering if the phone is slow or buggy because you didn't.
Click to expand...
Click to collapse
You're making sense. I totally get it. (about starting from scratch) Can I then re-root it with the same UniKernel-v5-920P-072715.tar as before or will I need a new one of those too.? Thanks again.
This is the update SmartSwitch is telling me is available. I don't even know which of this stuff we've been discussing this is. Firmware, ROM or OS update.
Current version: PDA:0H1 / CSC:0H1/ PHONE:0H1 (SPR)
Latest version: PDA:011 / CSC:011 / PHONE:011 (SPR)
Size: 1612 MB
That's just a minor security update. I would not use that kernel to reroot. I believe the only option available for the update you are on and the update that is available is via TWRP + SuperSU zip.
es0tericcha0s said:
That's just a minor security update. I would not use that kernel to reroot. I believe the only option available for the update you are on and the update that is available is via TWRP + SuperSU zip.
Click to expand...
Click to collapse
Whatsa TWRP + SuperSU zip Is that a tool and file for getting this update?
Sorry man. I've had this phone for less than 2 months and it's my very first one.
I do appreciate your patience. I've been a PC support guy for 16 years. I know what it's like.
TWRP = Team Win Recovery Project. It replaces the stock recovery that the phone uses to perform factory resets and updates signed by Samsung. This allows you multiple benefits such as complete system/data/kernel backups, being able to wipe any combo of system/data/caches/internal storage, factory data reset without wiping internal storage, terminal commands, and installing custom files, roms, mods, etc not signed by Samsung to name a few. SuperSU is the popular root binary and root permissions app made by the developer Chainfire. If you needs links, I can provide, but assuming you're familiar with Googling things being a support guy. ☺
es0tericcha0s said:
TWRP = Team Win Recovery Project. It replaces the stock recovery that the phone uses to perform factory resets and updates signed by Samsung. This allows you multiple benefits such as complete system/data/kernel backups, being able to wipe any combo of system/data/caches/internal storage, factory data reset without wiping internal storage, terminal commands, and installing custom files, roms, mods, etc not signed by Samsung to name a few. SuperSU is the popular root binary and root permissions app made by the developer Chainfire. If you needs links, I can provide, but assuming you're familiar with Googling things being a support guy.
Click to expand...
Click to collapse
I have SuperSU already.
These are some truly terrible directions unless you already know enough to not need them.
https://twrp.me/devices/samsunggalaxys6sprint.html
Will installing TWRP effect the root method I've already used?
Will installing recovery effect any of the multitude of configurations I've already done?
Does this then allow manual installs of OTA updates without losing root or any of your configuration customizations?
Is it JUST the recovery partition were dealing which stands alone from the os?
Does Nandroid backup then encompass the recovery and os and rom etc? Meaning are they all backed up and custom recovery via TWRP was what made that possible? Or do you have to make your current config the recovery itself in order to do a ghost style backup and restore if you jack yourself up later? OR is not even this a ghost style restore?
Maybe it's just me, but the terminology is very confusing and I can't make heads or tails of what I'm even talking about with all this.
Tried to make backup with TWRP...
I guess whatever I flashed it with last time won't let it boot into recovery or the bootloader or whatever it's called. If I tell TWRP manager to reboot and do backup it just goes to the menu for rebooting and wiping cache etc. If I specifically go to "reboot to bootloader" it just reboots into android. I went to install a custom recovery and it said that if the location for the recovery is wrong it could brick the phone. I have no idea if it's right or wrong or if the root method I've already used is effecting this or not.
Installing a custom recovery will not affect your OS or any settings (as long as the recovery version is compatible with your phone and update). It is installed in a different partition than where the OS resides. It will not let you install official OTA zips. It is only for installing files not directly signed with Samsung's special key. When you do a nandroid backup, it will give you options on which parts of the phone you would like to backup. The important ones are boot, system, data, and EFS (though this is not typically needed when you restore, just as a precaution because it holds important data and settings of your IMEI and such - only restore if needed). Boot is the kernel, which controls many drivers for stuff like wifi, BT, CPU and GPU processes as well as others. System contains preloaded software, as in if you just restored boot and system, it would be like you factory reset the device and would need to setup your accounts and settings. Data is the apps, data, settings you have changed or added. A factory reset in the stock recovery would also wipe your /data/media storage which your phone sees as your internal storage. TWRP allows a factory reset that skips this so you will not lose the stuff you have accumulated on the phone such as pictures, music, downloads, etc.
The reason that when you are using TWRP Manager to install the recovery and reboot to it and it is still stock is probably due to the system has a script built in that notices if you change the recovery and will rewrite the stock recovery back to it upon rebooting. You can avoid this by renaming the script with a root enabled file browser. You will find this script in /system/etc/install-recovery.sh (or something similar). Just rename it to something like install-recovery.sh.bak.
es0tericcha0s said:
Installing a custom recovery will not affect your OS or any settings (as long as the recovery version is compatible with your phone and update). It is installed in a different partition than where the OS resides. It will not let you install official OTA zips. It is only for installing files not directly signed with Samsung's special key. When you do a nandroid backup, it will give you options on which parts of the phone you would like to backup. The important ones are boot, system, data, and EFS (though this is not typically needed when you restore, just as a precaution because it holds important data and settings of your IMEI and such - only restore if needed). Boot is the kernel, which controls many drivers for stuff like wifi, BT, CPU and GPU processes as well as others. System contains preloaded software, as in if you just restored boot and system, it would be like you factory reset the device and would need to setup your accounts and settings. Data is the apps, data, settings you have changed or added. A factory reset in the stock recovery would also wipe your /data/media storage which your phone sees as your internal storage. TWRP allows a factory reset that skips this so you will not lose the stuff you have accumulated on the phone such as pictures, music, downloads, etc.
The reason that when you are using TWRP Manager to install the recovery and reboot to it and it is still stock is probably due to the system has a script built in that notices if you change the recovery and will rewrite the stock recovery back to it upon rebooting. You can avoid this by renaming the script with a root enabled file browser. You will find this script in /system/etc/install-recovery.sh (or something similar). Just rename it to something like install-recovery.sh.bak.
Click to expand...
Click to collapse
You sir, are one patient and helpful man I very much appreciate your suffering through my whining. Interestingly, the boot loop just stopped in it's own and now I have the TWRP interface in place of the stock menu where the option was to wipe the cache partition.
Does this THIS mean I have a custom recovery now? Meaning, a different restore image than the one that came with the phone? Or does this now let me install that?
About this....
You were saying up HERE that if I run this update with smart switch I would lose root, but if I use TWRP to do it, I won't? Is that right? Thanks again.
Tiribulus said:
You sir, are one patient and helpful man I very much appreciate your suffering through my whining. Interestingly, the boot loop just stopped in it's own and now I have the TWRP interface in place of the stock menu where the option was to wipe the cache partition.
Does this THIS mean I have a custom recovery now? Meaning, a different restore image than the one that came with the phone? Or does this now let me install that?
Click to expand...
Click to collapse
This should mean that the recovery is installed. You can verify by using the app to boot to recovery or via powering the phone on by holding the Power, Volume Up, and Home buttons together as you restart. You should notice a recovery booting message in the top left and then you can let go of the buttons. Once there, you should perform a backup of the boot, system, and data partitions. If you have an EFS option, I would back that up too for safe keeping. It's rare that it would get corrupted, but best to have a backup just in cause.
If you update via Smart Switch, you will definitely lose root, as well as TWRP. Most likely, a developer has posted a rooted version of the update that you can use TWRP to install.
So I was looking into this a little closer for you and realized that the preferred method of updating and rooting the update you are trying to get involves using Odin to install the full update package, then reflashing TWRP, and using a newer version of the kernel to root. However, from some of the user comments about it, it seems like it might be better to wait till Samsung has released the source code of the kernel for the OI1 update. The kernels based on the slightly older 5.1.1 builds will work, but some people were experiencing random issues such as reboots or other oddities. I don't think OI1 has anything in it that would be worth losing root over or possibly having things run oddly. The alternative would be to update via a rom like this http://forum.xda-developers.com/spr...ment/ram9200-ofe-rom-thread-v3-5-1-1-t3173417
Hey guys, I was running stock ZVC (with stock recovery and bootloader) until just a few minutes ago, when I finally gave in and told the phone to apply the OTA update that was pushed out last week (the "ZVE" one). It started doing its thing, but next time I looked back at the device it was in recovery mode, just sitting there at the menu prompt...
I've since tried rebooting and powering off about half a dozen times, but it just keeps looping back to recovery mode. I also tried wiping the cache and rebooting, with no luck... It still loops back to recovery mode. I don't know what went wrong, but I'm assuming it could be related to one of two things that I didn't think about until afterwards:
1) The phone was rooted via Kingoroot, and root was still active when I tried to apply the update.
2) Just a FEW programs were frozen via TitaniumBackup (as well as Android's own app management system, using the "disable" feature), but these weren't system- or kernel-critical apps. They were things like LG Health, Sprint Money, etc...
Can anyone suggest a fix? Right now it just keeps rebooting into stock recovery and I've never had to deal with an issue like this, so I'm not sure what to do. I was obviously running the stock ROM, so I'm not set up to flash stuff. Although if it can be done with the default recovery, I suppose I could obviously do that... Once again, everything was stock on the phone except for Kingoroot, which was still enabled during the update.
I'm in a pickle here, guys. It's not like I'm any different than everyone who "needs their phone for work," but yeah, I need my phone for work... If I have to wipe data/factory reset, there's probably no way to pull some data off of the phone via PC first, is there? I suppose it's not that big of a deal, but I have some data and some program data that I hadn't gotten around to backing up yet, because I didn't think I'd need to until before I attempted to flash a new ROM or custom recovery.
Any help would be HUGE. Thanks...
EDIT: I took it into the Sprint store today a couple hours after I posted this, and they said I'd have to send it in to LG for warranty service. I don't know if the Sprint tech person knew what she was doing or not (because she had to use Google to figure out how to put the phone into download mode, even though she owns the same model), but she said that she couldn't establish a connection between the PC and the phone...
Now I'm not sure if that's the case, or if she just didn't have the right drivers installed, or if she was even in the right mode (I think she was using some Sprint-made flashing tool, but she did get it into download mode). She also seemed bored and like she just didn't wanna deal with it, so I don't know...
Assuming I can flash back to an earlier build like ZVB (and assuming I can even find it online), is that done from download mode or from recovery? By the way, we also tried just doing a factory reset and that didn't work either; just keeps rebooting to recovery...
Thanks...
EDIT 2: Fixed by flashing to stock via these instructions. Had to select Board DL and use a different key sequence as described here.
tl;dr - Can't seem to find my way out of a software brick. Have sideloaded the stock OS from 1+ but still forever getting the spinning dots or fastboot screen, depending on which mode i boot into.
Hi all. Signed up to make this thread, but i've been lurking for years.
I have a OnePlus X that is about the least modded smartphone i've ever owned. I've never been pleased enough with a retail product that i didn't feel compelled to strip out the bloat and start over, until this phone. Other than stock, i've just got a gallery app, some apps for manipulating text files or compiling code, couple games, and social media apps.
Anyway, a few days ago i got a notification about a software update. Downloaded. Installed. Updated. No problem.
Maybe yesterday or the day before, it showed up again. This morning i downloaded, installed, and suddenly i have apps closing. It's been over 12 hours so i'm hazy on how it all started, but i was getting something like "package installer" errors when attempting to open some apps. Same deal when i went to adjust permissions of those affected apps. Every time i unfocused a box that had pulled up swype, i would get an error message saying swype crashed or closed or something.
So i started uninstalling third party apps (i don't keep many, and most i've had for years so i think they're probably trustworthy). Same deal. Started uninstalling updates to google apps. Same deal. Went to uninstall and reinstall some non stock apps that i'd kept previously. Nothing.
I went to cook breakfast while an app was reinstalling, and i came back to a red dot on my screen with two white dots chasing each other around it. From what i'm reading that's a sign of a bootloop or software brick. I've taken all steps i could find, including wiping cache and sideloading a fresh stock OS, but to no avail.
Is it that i've ruined my google apps somehow and need to restore them? How would i even go about figuring out what the problem is? Any advice or guidance is appreciated
Hi,
As your device is in bootloop state, try flashing the stock rom. Make sure you wipe data and cache. As far as after update problems, i faced it few times. After updating many app crashed and phone hangs. So i prefer clean flash over dirty flashing, to make sure everything is hazel free. For the time being i upgraded from 3.1.2 to 3.1.3 without wiping data or cache and facing no problem( of course since it was an OTA). But sometimes situation comes when after update phone act weird, so tbe option which i prefer then is clean flashing the stock rom. Hope this helps.
"A09" said:
Hi,
As your device is in bootloop state, try flashing the stock rom. Make sure you wipe data and cache. As far as after update problems, i faced it few times. After updating many app crashed and phone hangs. So i prefer clean flash over dirty flashing, to make sure everything is hazel free. For the time being i upgraded from 3.1.2 to 3.1.3 without wiping data or cache and facing no problem( of course since it was an OTA). But sometimes situation comes when after update phone act weird, so tbe option which i prefer then is clean flashing the stock rom. Hope this helps.
Click to expand...
Click to collapse
I have wiped cache, deleted data, tried a factory reset in the stock bootloader, and i have used ADB to sideload a full stock rom (not upgrade package) that i downloaded from OnePlus.
Flash old stock recovery then 2.2.3. From there you can flash any MM stock firmware.
Exodusche said:
Flash old stock recovery then 2.2.3. From there you can flash any MM stock firmware.
Click to expand...
Click to collapse
Pardon me for being nooby, but how do i do this? Do i just sideload in ADB like i did the ROM? Most instructions i'm finding assume access to the OS either normally or through fastboot. I'm just stuck in the default recovery.
Thanks for the tip, though. Looking for a copy of the old stock recovery now. Did OnePlus alter their stock recovery recently? In some threads i've seen people say that a recent update made them unable to load a non-stock ROM. Is that the new recovery blocking access to non-1+ operating systems?
jtg1984 said:
Pardon me for being nooby, but how do i do this? Do i just sideload in ADB like i did the ROM? Most instructions i'm finding assume access to the OS either normally or through fastboot. I'm just stuck in the default recovery.
Thanks for the tip, though. Looking for a copy of the old stock recovery now. Did OnePlus alter their stock recovery recently? In some threads i've seen people say that a recent update made them unable to load a non-stock ROM. Is that the new recovery blocking access to non-1+ operating systems?
Click to expand...
Click to collapse
Fastboot flash easiest way. Make sure it's the old recovery from 2.2.2. Not the new mm stock recovery.
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
jtg1984 said:
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
Click to expand...
Click to collapse
I m not a dev, i m a newbie like you. i hv done a lot of experiments with my oneplus-x, as for u the first update u got few days back should be oos 3.1.2 and the one u got 2 days before should be 3.1.3. When u upgrade from lollipop to marshmellow, even your stock recovery got upgraded to latest version, which is something different from old lollipop recovery.
You said you have access to recovery mode. thts pretty much gud, what u can do is that wipe data and cache through stock recovery and do a clean install of oos 3.1.3. I ll be providing all the necessary links down below. If you need assistance with fastboot cmds and anything feel free to ask.
Thanks to original link provider @Sachin7843
Useful Links: -
1. Stock Lollipop Recovery - https://s3.amazonaws.com/oxygenos.oneplus.net/OPX_recovery.img
2. Official TWRP Recovery - https://dl.twrp.me/onyx/
3. Blu Spark Recovery - http://forum.xda-developers.com/devdb/project/dl/?id=20236
4. SuperSU for OOS 3.x.x - https://drive.google.com/file/d/0B4K5cvm1zdldcmZpc3RuVnRjUUE/view
5. Unbrick Guide - http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
6. Official Oxygen OS 3.1.3 link - https://s3.amazonaws.com/oxygenos.o...OTA_018_all_201609291837_741146bcf28e4587.zip
7. SD Card Writable fix in MM - http://forum.xda-developers.com/android/software/fix-extsd-fix-v1-0b-2016-01-18-t3296266
8. For Stock MM Recovery - http://forum.xda-developers.com/oneplus-x/general/oxygenos-3-1-0-marshmallow-community-t3445043
Sorry for my bad english
jtg1984 said:
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
Click to expand...
Click to collapse
Don't sideload it, use fastboot to flash it. "Fastboot flash recovery name.img" - without he quotes and the image name.
Sorry for vanishing. Had a busy week.
Not sure what happened the first time i tried to put the 2.2.3 image on the SD card, because the file didn't show up in my recovery, but i tried again later (after giving up on flashing the old recovery, since i couldn't figure out how to do that in recovery) and managed to do a clean install of the older OOS version.
That did the trick, and after booting up, my phone proceeded to update again - this time without any crashes or errors with my apps afterward. The phone still does the red dot with the white dots chasing around it when it boots up, which must be the new boot screen. It also seems to stay on that screen for much longer than it stayed on the old morphing shape boot screen, but it still boots up reliably now after 30-60 seconds rather than freezing in boot forever.
I've since enabled dev mode on my phone. Is that going to be enough to enable ADB commands from recovery? I kind of like that i've kept my phone stock, so i'll leave it that way if i can, but it would have been much easier to fix this problem if i'd had access to most of my debug commands. As it was, without dev mode and in the standard recovery, it seemed that sideload was the only command i was able to use, and only when the phone was requesting a sideload over usb