Related
Hi everyone, I have a big problem. Recently I got the phone and decided to root it. I used this guide: http://forum.xda-developers.com/showthread.php?t=2788632
I successfully rooted 4.4.2. using TWRP method, no problem but I when I decide it to update to OTA XNPH30O - 4.4.4. after clicking install, it sends me back to TWRP recovery page and I never able to install the update. What I did next was probably what got me in this situation. I went to recovery page, I did both format data and advance wipe but turns out it didn't clean everything on the SD DIR. So now when I restart the system, it just hangs on the OPO page.
Please how do I restore to the original factory ROM so I can re-root it again. Currently I have only access to fastboot and TWRP recovery page. I'm very noob at this and the last thing I want is to messed up the bootloader so I need someone to guide me through it step by step.
Thank You
Check the index thread in my signature. In the stock images section there's a thread that has TWRP flashable versions of the CM11S ROMs, just flash one of those.
Transmitted via Bacon
timmaaa said:
Check the index thread in my signature. In the stock images section there's a thread that has TWRP flashable versions of the CM11S ROMs, just flash one of those.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks, I recover to the original XNPH22R stock ROM that I was on when I got the phone but after I update through system to
XNPH25R I can't update anymore? - 0 updates available. I like to go to at least XNPH30O so I can be on 4.4.4 before I want to root it. What do you suggest I should do?
You could follow the guide in my signature to get back to 100% stock 33R build but make sure you backup your data first
Majestic_12 said:
Thanks, I recover to the original XNPH22R stock ROM that I was on when I got the phone but after I update through system to
XNPH25R I can't update anymore? - 0 updates available. I like to go to at least XNPH30O so I can be on 4.4.4 before I want to root it. What do you suggest I should do?
Click to expand...
Click to collapse
The OTA updates are bugged.
You might want to consider using a custom ROM.
Majestic_12 said:
Thanks, I recover to the original XNPH22R stock ROM that I was on when I got the phone but after I update through system to
XNPH25R I can't update anymore? - 0 updates available. I like to go to at least XNPH30O so I can be on 4.4.4 before I want to root it. What do you suggest I should do?
Click to expand...
Click to collapse
Like I said just go to my index thread, there are full versions of every release of CM11S in the Stock Images thread. Just flash whichever version you wavy to be on.
Transmitted via Bacon
EddyOS said:
You could follow the guide in my signature to get back to 100% stock 33R build but make sure you backup your data first
Click to expand...
Click to collapse
33R are suppose to be a stock ROM? i thought 22R was hmm.. either way I did fastboot recovery to 22R but now I seem to encounter new issue: can't download anything from google play store due to an "error retrieving info from server". I'm getting frustrated now, I have no idea what to do...
I guess I should root it all over again to gain access to TWRP and SuperSU but what's after that?
Gamm86 said:
The OTA updates are bugged.
You might want to consider using a custom ROM.
Click to expand...
Click to collapse
Please enlighten me about this, I just wish to be on 4.4.4 rooted that fixes the current battery drain issue. I just want to install a ROM that's the most stable currently and most people would recommend at the moment.
Majestic_12 said:
33R are suppose to be a stock ROM? i thought 22R was hmm.. either way I did fastboot recovery to 22R but now I seem to encounter new issue: can't download anything from google play store due to an "error retrieving info from server". I'm getting frustrated now, I have no idea what to do...
I guess I should root it all over again to gain access to TWRP and SuperSU but what's after that?
Please enlighten me about this, I just wish to be on 4.4.4 rooted that fixes the current battery drain issue. I just want to install a ROM that's the most stable currently and most people would recommend at the moment.
Click to expand...
Click to collapse
22R was an earlier build based on Android 4.4.2, 33R is the latest CM11S build based on Android 4.4.4. Following my guide will get your phone back to how it would be if brand new out-the-box (but it will wipe all data in the process)
Which is probably overkill. All he needs to do is flash a ROM.
Transmitted via Bacon
timmaaa said:
Which is probably overkill. All he needs to do is flash a ROM.
Transmitted via Bacon
Click to expand...
Click to collapse
True, but if the OP doesn't really know what they're doing going back to the start might be a good thing. Otherwise, this ZIP flashed in TWRP would do the job...
http://dist01.slc.cyngn.com/factory/bacon/cm-11.0-XNPH33R-bacon-signed.zip (taken from the images thread)
Thank you all for helping me with this, I know all this noob asking is lame but I need to ask in order for me to learn.
EddyOS said:
True, but if the OP doesn't really know what they're doing going back to the start might be a good thing. Otherwise, this ZIP flashed in TWRP would do the job...
link (taken from the images thread)
Click to expand...
Click to collapse
I did just that using fastboot, I flashed ROM XNPH33R which is supposedly 4.4.4 and I again rooted it afterward with TWRP/SuperSU method. But now I think I need to go through a checklist on why my battery still isn't doing good as many would say. I wouldn't consider it draining but it does go down quite fast when I put it to use. Evening idling for 8 hours the phone still drains about 20% when I woke up.
timmaaa said:
Which is probably overkill. All he needs to do is flash a ROM.
Transmitted via Bacon
Click to expand...
Click to collapse
I did just that on using the XNPH33R fastboot img but now that I think about it, should I use the zip method instead but that's putting the files onto DIR and flash it from TWRP right?
EddyOS said:
22R was an earlier build based on Android 4.4.2, 33R is the latest CM11S build based on Android 4.4.4. Following my guide will get your phone back to how it would be if brand new out-the-box (but it will wipe all data in the process)
Click to expand...
Click to collapse
Well I did all that, now I'm on 33R and is rooted, is there anything I can do to help improve the battery life? I';m still experiencing a drain.
OK I might have found something to do with battery drain now since I have root access, sorry I'm too new to rooting at this moment but I learned that I suppose to get rid of bloatware from CM11 to increase battery duration. Now the question is, is there a thread in XDA going over a list of what I should uninstall/freeze?
Majestic_12 said:
OK I might have found something to do with battery drain now since I have root access, sorry I'm too new to rooting at this moment but I learned that I suppose to get rid of bloatware from CM11 to increase battery duration. Now the question is, is there a thread in XDA going over a list of what I should uninstall/freeze?
Click to expand...
Click to collapse
Getting rid of bloat isn't really going to increase the duration of your battery. Finding which apps are driving your battery the most or causing wakelocks and then dealing with them by using something like Greenify will have a positive effect though.
Transmitted via Bacon
Hi there,
A while ago I got a OnePlus One which came with ColorOS loaded. I of course googled my way to get the Cyanogenmod and followed these instructions.
http://www.youtube.com/watch?v=QDKOEtN9pbo
I'm currently on the 25R firmware and I know there are some updates after that but the phone doesnt detect any update release. I would like to know why the OTA updates are not being picked up from the phone. Was it simply the easy method mentioned above?
I also thought of reflashing it properly and found some instructions on the web.
Code:
Install Android tools (and drivers if you use Windows-crap). You need the fastboot and adb tools
Get http://dist01.slc.cy...ed-fastboot.zip and unpack it
Enable USB debugging on the phone
Run adb reboot-bootloader
Once bootloader started run: fastboot oem unlock
After automatic reboot, do steps 3 & 4 again
In the directory where you unpacked it, run in a console
fastboot flash modem NON-HLOS.bin
fastboot flash sbl1 sbl1.mbn
fastboot flash dbi sdi.mbn
fastboot flash aboot emmc_appsboot.mbn
fastboot flash rpm rpm.mbn
fastboot flash tz tz.mbn
fastboot flash LOGO logo.bin
fastboot flash boot boot.img
fastboot flash cache cache.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash userdata userdata_64g.img (or userdata.img for 16G version)
fastboot oem lock
fastboot reboot
These instructions will somehow get the OTA updates working, am I right to assume that this method would rewrite everything and I would lose the recovery software of the ColorOS? Also are the Android tools these?
http://developer.android.com/sdk/index.html
Fastboot and ADB, I can use this one right?
http://forum.xda-developers.com/showthread.php?t=2588979
I appreciate the help and a few explanations.
Cheers.
Just download this
http://builds.cyngn.com/fota/incremental/bacon/cm-bacon-ac1ccf7921-to-5fa8c79c0b-signed.zip
Sent from my A0001 using XDA Premium 4 mobile app
scabbie1980 said:
Just download this
http://builds.cyngn.com/fota/incremental/bacon/cm-bacon-ac1ccf7921-to-5fa8c79c0b-signed.zip
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Hi scabbie, from the looks of the file its an incremental update. Do I just run it from the OPO with Cyanogenmod? If this is a long tedious method, I would rather do a fresh install and get the OTA updates to work. Also part of the reason I want a clean install is because the phone is acting up and my screen goes black when I call someone and then when I want to hang up the screen is still black and I cant hang up. and physical buttons dont respond either.
I dont know if this incremental update will fix this kind of problem, so hence my option to do some clean install.
Cheers
dude777 said:
Hi scabbie, from the looks of the file its an incremental update. Do I just run it from the OPO with Cyanogenmod? If this is a long tedious method, I would rather do a fresh install and get the OTA updates to work. Also part of the reason I want a clean install is because the phone is acting up and my screen goes black when I call someone and then when I want to hang up the screen is still black and I cant hang up. and physical buttons dont respond either.
I dont know if this incremental update will fix this kind of problem, so hence my option to do some clean install.
Cheers
Click to expand...
Click to collapse
If you're looking for a completely fresh install, just go to my guide thread (link in signature) and follow section 8.
Transmitted via Bacon
OK, for a clean download you need to download this in fastboot mood
https://www.copy.com/s/hMXtmkJAbDhjxQyC
Sent from my A0001 using XDA Premium 4 mobile app
---------- Post added at 02:01 PM ---------- Previous post was at 01:56 PM ----------
scabbie1980 said:
OK, for a clean download you need to download this in fastboot mood.
https://www.copy.com/s/hMXtmkJAbDhjxQyC
Look on YouTube on how to use this toolbox and it will completely wipe your phone then flash clean.
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my A0001 using XDA Premium 4 mobile app
scabbie1980 said:
OK, for a clean download you need to download this in fastboot mood
https://www.copy.com/s/hMXtmkJAbDhjxQyC
Sent from my A0001 using XDA Premium 4 mobile app
---------- Post added at 02:01 PM ---------- Previous post was at 01:56 PM ----------
Sent from my A0001 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
A toolbox is completely unnecessary, and they're more trouble than they're worth. Plus, nobody learns anything even using a toolbox, and that knowledge is crucial for when things go wrong.
Transmitted via Bacon
DON'T use a toolbox please
Learn as you go by doing things properly, I speak from my own experience. These skills and knowledge that you gain will help if you ever run into any issues
Go here to install the adb drivers computer wide so you can flash from any folder on your computer, it makes your life so much easier
http://forum.xda-developers.com/showthread.php?t=2588979
Then follow timmaaa guide on how to start fresh with a complete 44s ROM
Sent from my A0001 using XDA Free mobile app
Thanks guys for the effort here, really like your guides timmaaa very clear and non confusing. Yes I would like to avoid shortcuts as I took the easy route and now the phone goes in hiatus moment when calling. I'll get around this in the weekend and see how that goes.
Cheers.
@ timmaaa
Love the guide you put up, I was having a read through this and I'm slightly confused on your comments. http://forum.xda-developers.com/one...-to-guides-t2839471/post56731494#post56731494
You mentioned just go straight to Section 8, but in the link above you mentioned go through 1-4 then go to 8. I dont think I need to root on section 4 but for 1, 2 and 3, I would like to know, particularly in section 2 and 3 if you can explain to a novice like me. As I'm understanding this, I think the ColorOS phone has some recovery software, thats how I did the easy flashing method thing, so for section 2 your instructions will overwrite the ColorOS one?
For Section 3 the nandroid backup seems like a snapshot of the phone (which includes recovery, phone OS and other things) before installing custom rom?
Please let me know if my interpretation is correct and correct me along the way, I am here to learn what I can, so that I can successfully flash the OPO phone.
Cheers.
dude777 said:
@ timmaaa
Love the guide you put up, I was having a read through this and I'm slightly confused on your comments. http://forum.xda-developers.com/one...-to-guides-t2839471/post56731494#post56731494
You mentioned just go straight to Section 8, but in the link above you mentioned go through 1-4 then go to 8. I dont think I need to root on section 4 but for 1, 2 and 3, I would like to know, particularly in section 2 and 3 if you can explain to a novice like me. As I'm understanding this, I think the ColorOS phone has some recovery software, thats how I did the easy flashing method thing, so for section 2 your instructions will overwrite the ColorOS one?
For Section 3 the nandroid backup seems like a snapshot of the phone (which includes recovery, phone OS and other things) before installing custom rom?
Please let me know if my interpretation is correct and correct me along the way, I am here to learn what I can, so that I can successfully flash the OPO phone.
Cheers.
Click to expand...
Click to collapse
I was assuming that because you're on the 25R build of CM11S that you've already unlocked your bootloader and installed TWRP recovery, if this isn't the case then you will need to follow sections 1, 2, and 3 before moving on to section 8.
The phone definitely already has some kind of recovery on it (every phone does), but you do need to install a custom recovery in order to make a backup of your current ROM. It will overwrite the existing recovery when you install it, and then later on when you flash the fastboot images (in section 8) the stock recovery will overwrite the custom recovery. So why bother flashing the custom recovery if it'll just be overwritten? Because insurance. It'll allow you to make a nandroid backup of your current setup to fall back on just in case something goes wrong.
A nandroid is like a snapshot of the phone, but it doesn't include your recovery partition, it includes the /system partition (where the os resides), the /data partition (where your apps and settings reside), and the /boot partition (the kernel). You should always have at least one nandroid on your phone at all times. Personally, I make one before I flash anything, that way if I don't like whatever I'm flashing or if something goes wrong, I can just restore my backup and boot the phone up, and it's exactly how I left it.
After you've made your backup make sure you transfer it to your PC (and anything else important on the phone), because flashing the fastboot images is going to wipe your whole phone, including all of your user data.
If you have any other questions please don't hesitate to ask.
Transmitted via Bacon
timmaaa said:
I was assuming that because you're on the 25R build of CM11S that you've already unlocked your bootloader and installed TWRP recovery, if this isn't the case then you will need to follow sections 1, 2, and 3 before moving on to section 8.
The phone definitely already has some kind of recovery on it (every phone does), but you do need to install a custom recovery in order to make a backup of your current ROM. It will overwrite the existing recovery when you install it, and then later on when you flash the fastboot images (in section 8) the stock recovery will overwrite the custom recovery. So why bother flashing the custom recovery if it'll just be overwritten? Because insurance. It'll allow you to make a nandroid backup of your current setup to fall back on just in case something goes wrong.
A nandroid is like a snapshot of the phone, but it doesn't include your recovery partition, it includes the /system partition (where the os resides), the /data partition (where your apps and settings reside), and the /boot partition (the kernel). You should always have at least one nandroid on your phone at all times. Personally, I make one before I flash anything, that way if I don't like whatever I'm flashing or if something goes wrong, I can just restore my backup and boot the phone up, and it's exactly how I left it.
After you've made your backup make sure you transfer it to your PC (and anything else important on the phone), because flashing the fastboot images is going to wipe your whole phone, including all of your user data.
If you have any other questions please don't hesitate to ask.
Transmitted via Bacon
Click to expand...
Click to collapse
I see, so even if my phone doesnt have much inside it should still be recommended, because of the listed above are operational and if something were to happen on the newly flashed phone, I have no way of retracing my steps.
So in a hypothetical situation I unlocked the bootloader and proceed to section 2. The recovery software provided when I first got the phone will be overwritten by the TWRP recovery and I will have lost the old one. I will then perform a nandroid backup where I can preserve a last known working configuration as an insurance, if future flashes fail. I assume you restore nandroid backup through the TWRP recovery? Also the nandroid backup is made on the phone? so I will need to transfer that to my PC before flashing?
At this stage all I changed is the bootloader and recovery partition with custom recovery. When I jump to section 8 it should be smooth sailing, provided I follow them clearly and the drivers work on the PC.
I apologise for being a pain in the butt! I just like to clarify before I do something horrible and have no idea what to do next.
Cheers
dude777 said:
I see, so even if my phone doesnt have much inside it should still be recommended, because of the listed above are operational and if something were to happen on the newly flashed phone, I have no way of retracing my steps.
So in a hypothetical situation I unlocked the bootloader and proceed to section 2. The recovery software provided when I first got the phone will be overwritten by the TWRP recovery and I will have lost the old one. I will then perform a nandroid backup where I can preserve a last known working configuration as an insurance, if future flashes fail. I assume you restore nandroid backup through the TWRP recovery? Also the nandroid backup is made on the phone? so I will need to transfer that to my PC before flashing?
At this stage all I changed is the bootloader and recovery partition with custom recovery. When I jump to section 8 it should be smooth sailing, provided I follow them clearly and the drivers work on the PC.
I apologise for being a pain in the butt! I just like to clarify before I do something horrible and have no idea what to do next.
Cheers
Click to expand...
Click to collapse
You do indeed restore a nandroid backup with the recovery that you made the backup with. And yes it is saved on the phone so you will need to transfer it to your PC. You're not being a pain in the butt, you're doing the right thing and researching before attempting something.
Transmitted via Bacon
Yeah I agree users like you that research crap before attempting something are much preferred over users that blindly use a toolbox then come complaining cuz they messed something up but dunno how to fix it. I always do my research before flashing just like you are doing. Just make sure you install the drivers I linked to computer wide on your windows computer and you should have no problems, no need to install separate SDK for android and copy the files you're flashing into a special folder, etc
info update
Hey guys, noob here. I wanted to update to the most recent version and I am running version: XNPH25R atm.
Anyone could be so kind to tell me what's the easiest way to to this? I have a 64gb chinese version.
If you follow timmaaa's guide you should be good to go. I'm a noob myself and just did it over the weekend and its a blast. Good luck
Cheers
maeishoj said:
Hey guys, noob here. I wanted to update to the most recent version and I am running version: XNPH25R atm.
Anyone could be so kind to tell me what's the easiest way to to this? I have a 64gb chinese version.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
maeishoj said:
Hey guys, noob here. I wanted to update to the most recent version and I am running version: XNPH25R atm.
Anyone could be so kind to tell me what's the easiest way to to this? I have a 64gb chinese version.
Click to expand...
Click to collapse
Lol really? Did u completely ignore reading the thread that you just posted in??
[emoji15] [emoji58]
Hi,
My mobile data no longer works. I've done a lot of research, tried every fix, to no avail. My WiFi works, it's only my mobile data.
Things I've tried:
Following this guide: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
Completely reverting to stock
Flashing a stock, rooted 44S + radio files
Flashing ColorOS, and then flashing CM11S using this guide: http://forum.xda-developers.com/oneplus-one/general/fix-people-corrupt-efs-mobile-data-t2836389
Sticking the SIM card in my Galaxy S3 to see if it works (spoiler: it does)
Restoring previous nandroid while data was working fine
Under ColorOS, I have a notification that says "The NV partition is invalid!". Just thought I'd mention that.
Stupid me didn't backup my EFS. No APNs, unknown IMEI, unknown baseband, etc.
I'm at a loss guys. I'd greatly appreciate your help.
Thanks,
Niko
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2970390
Transmitted via Bacon
timmaaa said:
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2970390
Transmitted via Bacon
Click to expand...
Click to collapse
Yup. Sadly didn't work.
You might be outta luck then, the methods you've mentioned above are the only ones that I know of that work. Let this be a lesson to anyone reading, backup your EFS. DO IT.
Transmitted via Bacon
timmaaa said:
You might be outta luck then, the methods you've mentioned above are the only ones that I know of that work. Let this be a lesson to anyone reading, backup your EFS. DO IT.
Transmitted via Bacon
Click to expand...
Click to collapse
You think it would be worth trying to get a new sim card from my carrier?
It isn't the SIM that's the problem, your EFS partition is corrupt.
Transmitted via Bacon
If my EFS partition was corrupt, why does my Wifi work?
That's normal.
Transmitted via Bacon
I FIXED IT! This is exactly what I did.
* Flash ColorOS from this post: https://forums.oneplus.net/threads/rom-official-4-3-coloros-v-2-0-0_beta.79203/
* Download and install OTA updates for ColorOS
* Flash back TWRP
* Flash 44S (Pre-Rooted)
* Boot up phone without SIM in (at this point I checked the settings and to my joy saw that baseband wasn't unknown
* Power down, insert SIM in, reboot
NikoZBK said:
I FIXED IT! This is exactly what I did.
* Flash ColorOS from this post: https://forums.oneplus.net/threads/rom-official-4-3-coloros-v-2-0-0_beta.79203/
* Download and install OTA updates for ColorOS
* Flash back TWRP
* Flash 44S (Pre-Rooted)
* Boot up phone without SIM in (at this point I checked the settings and to my joy saw that baseband wasn't unknown
* Power down, insert SIM in, reboot
Click to expand...
Click to collapse
Hi, have the same issue. Did you flash the ColorOS thru a recovery or thru SDK Tools? and what recovery did you use to flash if you flashed with a recovery?
grneyez said:
Hi, have the same issue. Did you flash the ColorOS thru a recovery or thru SDK Tools? and what recovery did you use to flash if you flashed with a recovery?
Click to expand...
Click to collapse
I flashed ColorOS in fastboot mode, so through SDK tools. I manually flashed every .img. In other words, I just followed the guide in the link I gave.
NikoZBK said:
I flashed ColorOS in fastboot mode, so through SDK tools. I manually flashed every .img. In other words, I just followed the guide in the link I gave.
Click to expand...
Click to collapse
I gonna give it a shot, see what happens. I'm not so good in with SDK tools.
grneyez said:
I gonna give it a shot, see what happens. I'm not so good in with SDK tools.
Click to expand...
Click to collapse
Please post back how it goes.
NikoZBK said:
Please post back how it goes.
Click to expand...
Click to collapse
I will thanks.
NikoZBK said:
Please post back how it goes.
Click to expand...
Click to collapse
Worked like a charm, thanks so much for your help.
timmaaa said:
You might be outta luck then, the methods you've mentioned above are the only ones that I know of that work. Let this be a lesson to anyone reading, backup your EFS. DO IT.
Transmitted via Bacon
Click to expand...
Click to collapse
Sorry, bit of a noob here!
What is the EFS and how would I go about backing it up? I don't see any option for that in TWRP?
Rkr87 said:
Sorry, bit of a noob here!
What is the EFS and how would I go about backing it up? I don't see any option for that in TWRP?
Click to expand...
Click to collapse
Go to my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
Transmitted via Bacon
NikoZBK said:
I FIXED IT! This is exactly what I did.
* Flash 44S (Pre-Rooted)
Click to expand...
Click to collapse
Could I ask you what 44S is? I get the feeling my issue with my phone might be the same as yours. You also did this for a Chinese OPO?
DGX_Goggles said:
Could I ask you what 44S is? I get the feeling my issue with my phone might be the same as yours. You also did this for a Chinese OPO?
Click to expand...
Click to collapse
44S is short for XNPH44S, which is the latest build of CM11S (the stock firmware) for this phone.
Transmitted via Bacon
DGX_Goggles said:
Could I ask you what 44S is? I get the feeling my issue with my phone might be the same as yours. You also did this for a Chinese OPO?
Click to expand...
Click to collapse
No, I did this for the global version, but the steps should work for you as well.
Ok so i'm running lollipop 5.0 with twrp 2.8.3.0 rooted with cf auto root and i want to update to 5.0.1. First what i did i tryed to install ota but it did not start to install when the device resets. So i downloaded factory images for 5.0 and flashed factory recovery via fastboot, now when i download ota and device starts to install it on 1/4 % of progress bar it says error. So what else i need to do to install ota? Or there is not any other way exepct to flash factory image for 5.0.1.
Best option is to download factory image 5.0.1 and flash it with no wipe.
zagorteney said:
Best option is to download factory image 5.0.1 and flash it with no wipe.
Click to expand...
Click to collapse
Ok, so i do it with no wipe by editing the bat file right? i need to delete w?
Yeah, why download 5.0 instead of 5.0.1 factory image?
Easiest thing to do would have been flashing the 5.0.1 twrp flashable version of the rom from XDA...
rootSU said:
Yeah, why download 5.0 instead of 5.0.1 factory image?
Easiest thing to do would have been flashing the 5.0.1 twrp flashable version of the rom from XDA...
Click to expand...
Click to collapse
Sorry i did not know that there is a flashable version :/ can you give me the link to it? i will flash back twrp now and flash it like you said.
Its in the resources section of general > sticky roll-up, by vomer
rootSU said:
Its in the resources section of general > sticky roll-up, by vomer
Click to expand...
Click to collapse
I did all as u said and it went without a problem. So thanks a lot
Alexandar92zr said:
I did all as u said and it went without a problem. So thanks a lot
Click to expand...
Click to collapse
Can u give me more information ?
chessjoe said:
Can u give me more information ?
Click to expand...
Click to collapse
What more do you need? If you read my post, all the information is there
rootSU said:
What more do you need? If you read my post, all the information is there
Click to expand...
Click to collapse
someone else asked for more information, but it all went well im on 5.0.1 now rooted with twrp so thanks again
Alexandar92zr said:
someone else asked for more information, but it all went well im on 5.0.1 now rooted with twrp so thanks again
Click to expand...
Click to collapse
I was talking to the guy who asked for more information.
rootSU said:
I was talking to the guy who asked for more information.
Click to expand...
Click to collapse
That's great to hear. By the time, Is there any handy guide just to sideload the 5.0.1 update without actually wiping the data.
A lot of people will be looking the same just like me!
CODENEX said:
That's great to hear. By the time, Is there any handy guide just to sideload the 5.0.1 update without actually wiping the data.
A lot of people will be looking the same just like me!
Click to expand...
Click to collapse
You can only sideload OTA and OTA doesn't wipe data.
rootSU said:
You can only sideload OTA and OTA doesn't wipe data.
Click to expand...
Click to collapse
So it's the same way like we flash the factory image/custom ROM. Since the manual wiping doesn't even require, no need for apps backup?! #n008
CODENEX said:
So it's the same way like we flash the factory image/custom ROM. Since the manual wiping doesn't even require, no need for apps backup?! #n008
Click to expand...
Click to collapse
If you are 100% stock, you can:
- sideload OTA. No wipe
If you have a custom recovery you can
- flash a ROM.zip, without wipe
No matter what state you are:
- flash a factory image, with some modification to not wipe. This can be done by moving the -w from the flash script or individually flashing via fastboot, the system, boot, radio images. Though if you want ota in the future, you'll need to flash bootloader and recovery the same way.
Everything you need is in general > sticky roll-up
rootSU said:
If you are 100% stock, you can:
- sideload OTA. No wipe
If you have a custom recovery you can
- flash a ROM.zip, without wipe
No matter what state you are:
- flash a factory image, with some modification to not wipe. This can be done by moving the -w from the flash script or individually flashing via fastboot, the system, boot, radio images. Though if you want ota in the future, you'll need to flash bootloader and recovery the same way.
Everything you need is in general > sticky roll-up
Click to expand...
Click to collapse
I think the Section - B of the guide complies what you said.
Why is there three links, with warning (Original, may not flash for most people and full radio)?
rootSU said:
If you are 100% stock, you can:
- sideload OTA. No wipe
If you have a custom recovery you can
- flash a ROM.zip, without wipe
No matter what state you are:
- flash a factory image, with some modification to not wipe. This can be done by moving the -w from the flash script or individually flashing via fastboot, the system, boot, radio images. Though if you want ota in the future, you'll need to flash bootloader and recovery the same way.
Everything you need is in general > sticky roll-up
Click to expand...
Click to collapse
This is best explanation as you can get. But for newbies like me, there is also tool, named Wugfresh Root Toolkit. It does exactly what rootSU said above, but for ordinary users in more friendly way.
Regards, Zagor
zagorteney said:
This is best explanation as you can get. But for newbies like me, there is also tool, named Wugfresh Root Toolkit. It does exactly what rootSU said above, but for ordinary users in more friendly way.
Regards, Zagor
Click to expand...
Click to collapse
True but the problem there is that toolkits take away the learning curve for noobs. This means if something goes wrong using the toolkit of even later on, when we try to help, the noob doesnt understand the basic things we're saying.
Sure, it saves noobs time, but it wastes our time later when the noob needs our help (which is unfair and a bit selfish) So we strongly urge noobs to NOT use toolkits.
rootSU said:
True but the problem there is that toolkits take away the learning curve for noobs. This means if something goes wrong using the toolkit of even later on, when we try to help, the noob doesnt understand the basic things we're saying.
Sure, it saves noobs time, but it wastes our time later when the noob needs our help (which is unfair and a bit selfish) So we strongly urge noobs to NOT use toolkits.
Click to expand...
Click to collapse
It makes sense. But there is another truth, too. There aren't so many professionals like you with understanding android enviroment.
For example. I'm steel worker. I know how to weld. But also I know just few basic things about how welding machines works. I do not need exactly know how it works I just need to know how to adjust some of parameters to get better results. Because I have a good welding machine, it is almost impossible to go anything wrong. So for me good Toolkit is like good welding machine.
When I try to install SDK from Google and start with it I just give up after only 10 min. Toolkits works for me since X10. Of course there were many mistakes I've made (and probably will do), but I never bother people for such a situations like "I flash HTC Xspeed kernel on Samsung device - my gosh, please help". There are also unpredictable situations. I hate that with Titanium Backup and its /storage folder most. But the beauty of android system is that you can't do anything wrong. If you have somekind of backups you can allways start fresh. And that is the best school for everybody.
Regards, Zagor
You don't need the SDK. Its worth reading the stickies. The problem is when someone uses a toolkit and doesn't know how to use fastboot and we have to explain everything to them whilst panicking. Its easier to learn fastboot first.
Of course you must feel free to use toolkits yourself but many of us will say what I have said today if you recommend it.
Fastboot is not knowing how it works. Fastboot is the same knowledge you have as your welding machine. Developing would be more than you know than your welding machine.
Hi XDA Forum Members,
I had rooted my OPO a while back using TWRP.
I got the CM 12 official update this morning but when I said Install, I saw the TeamWin Menu when the phone rebooted. Since I don't really know the technical details, I didn't know how to install CM 12 (and if I will lose data if I do so). So I just rebooted to system.
Could you please help me out here? If I want to update to CM 12, how do I do it? And if I do so, will I lose data and have to root my phone all over again?
Thanks in advance!
-Apoorva
Just grab the update from here And flash it manually with TWRP.
Transmitted via Bacon
Thanks but which option do I select among the 4 there? (I wasn't kidding when I said I don't know technical stuff )
timmaaa said:
Just grab the update from here And flash it manually with TWRP.
Transmitted via Bacon
Click to expand...
Click to collapse
apoorva_ said:
Thanks but which option do I select among the 4 there? (I wasn't kidding when I said I don't know technical stuff [emoji14])
Click to expand...
Click to collapse
The first option.
Transmitted via Bacon
I downloaded it but does not install as a secondary in MultiRom. ANyway I can do this?