Ok so I'm currently running Insert Coin and whoppers enhanced kernel. So I'm running 4.4.2 obviously. Is it possible to flash the jelly bean hboot and then run the RUU to return to full stock?
Good question. I dont think u can
Any other method to return to stock
U flash a stock recovery and a stock kernel via fastboot and u flash a stock rom via recovery http://forum.xda-developers.com/showthread.php?t=2804427
Which file is the Rom?
System backup
How do i flash the backup in stock recovery?
U cant. Flash a cwm or twrp again then flash a rom
---------- Post added at 12:45 PM ---------- Previous post was at 12:43 PM ----------
Actually we dont have a cwm recovery for kk so flash twrp
It failed to install the backup
Try this https://drive.google.com/folderview?id=0B-kSF8g8H7KuME12ai1OVHVqd3M&usp=sharing#list
Do I get the kk stock system dump zip?
Yes
Still no luck
Thats weird. Cant figure it out
It's not that big of a deal for me. But still something we need to solve
Same problem
I am currently having a similar problem. I have a Desire 601 CL running 4.2.2 with the Clockwork Senseless ROM. I wanted to return to stock to upgrade to KK so that I could try out the Insert Coin ROM but no luck yet. I've tried going S-Off with rumrunner and firewater,that failed. I tried running stock JB system dump, and that failed. My goal was to run the stock JB Rom and recovery so that I could relock my bootloader at HTCDev but i'm stuck as I seem to have lost my stock backup and none posed are working for me.
Which custom recovery do u use? If ur carrier is sprint, u can run the ruu to return to stock. Rumrunner works. what error msg do u get when u try to run rumrunner?
TWRP 2.7.1.0 going to re-run rumrunner this evening and get message.
Message says something about downloading updated package from the rumrunner website. I think all my problems stem from not having stock ROM.
Its a server-side issue. U should report the issue to beaups in irc so he can fix it and u run rumrunner again
Related
OK so i am rooted, S-Off, and hboot 1.49.1107
i just flashed the firmware update and then immediately after flashed a new rom. i didn't know you had to flash the firmware and go into the OS after, then flash the rom. so it just gets stuck at the HTC screen now. how do i flash a rom with the new firmware already installed? so i have to go back to a GB rom and old firmware and try again?
If your s-off just grab a Rom and reflash I would think. I don't know why u fooled with firmware to begin with if ur s-off already.
Sent from my PG86100 using xda app-developers app
just take the OTA when it comes out. all better. LOL! BUT DON'T FORGET! look at what you flash. sometimes what you flash can cause you to loose your root.
Chillaxed said:
OK so i am rooted, S-Off, and hboot 1.49.1107
i just flashed the firmware update and then immediately after flashed a new rom. i didn't know you had to flash the firmware and go into the OS after, then flash the rom. so it just gets stuck at the HTC screen now. how do i flash a rom with the new firmware already installed? so i have to go back to a GB rom and old firmware and try again?
Click to expand...
Click to collapse
If you don't have supercid
can't go back GB RUU
Could someone please help??
tryed updating through System Update (OTA)
failed to install... said my device may have custom rom
I wasn't using a custom rom, only changed cid to use a custom rom but ended up using stock. Just forgot to change cid back.
Changed cid back to original (HTC__044) and tryed to download OTA again...
It succeeded to download and asked me to install... Accepted.
it rebooted to Recovery and failed to install.
Followed 1st post instructions (status 7)
and installed the OTA through recovery.
Instalation successful!
BUT
When I rebooted the device, it just doesn't boot.
I downloaded anryl files, but it failed to load PG86IMG.zip when I boot to bootloader. Says wrong image.
tried booting into recovery but it won't boot into recovery either.
then tried flashing recovery again and booting into recovery again. No success.
any ideas?
Thanks in advance
Ok so I've been struggling with this for MONTHS. I flashed Hatka 2.x (Android 4.2) a while back, and ever since then I have not been able to install any other rom besides Hatka 2.x.:crying:
Android: 4.2
Rom: Hatka 2.x
Kernel: 3.4.10-g4d47dce [email protected] #1 SMP PREEMPT
HTC Sense: 4+
I have tried flashing several roms from just about anything 4.2.2 - 4.3 and now 4.4.x. I'm not sure If maybe I need a new kernel, boot image or what but I feel like I have tried everything. When I flash a rom I wipe data/cache/dalvik cache (of course), Flash the rom, flash gApps, flash cache/dalvik and more times than not my phone will never get past the HTC logo. Sometimes more lately with 4.4 roms my phone will boot loop only showing the HTC logo for a minute or two then restart. I root and flash several different types of phones for my friends all the time, and never have any of these issues that I've faced with my own phone.
I recently thought about trying to un-root, re-lock, and flash back to stock, then re-root and un-lock again but I'm not sure if that will even help.
Things I've tried:
Several roms
Moded kernel
Stock kernel
Multiple CWM versions
Multiple TWRP versions
Fastboot flash
Adb flash
Adb Sideload
Roms I am currently trying to flash:
AOKP unofficial (4.4.2)
BeanStalk (4.4.2)
CM-11 Nightly (4.4.2)
OSE Official (4.4.2)
My secondary HDD with all of the kernels, roms, and anything else I have tried recently failed so I don't have the specific version numbers for any of the attempts listed above.
If someone could give me any advice on this I would be eternally greatful. The Android/xda community has always been so helpful with many others in times of need, so now after spending months of research and trial & error I am reaching out to anyone here at xda that may be able to give me some advice/assistance.
Links to other threads/tools are greatly appreciated also! :good:
Thank you in advance.
-EDIT-
SOLVED
I took thay10's advice and flashed RUU. Since I got an error flashing RUU 3.04 I found RUU 1.15 here and flashed that successfully.
After that I verified my cid using this method.
When that turned out ok I continued to the HTCDev page to unlock my bootloader.
Once the bootloader was unlocked I used Facepalm S-Off method to achieve S-Off. (Using only the modified boot.img and DNA-rescue.img [links in thread]).
After all that was finished and I now had my bootloader unlocked and S-Off, I chose the recovery of my choice and flashed it using fastboot.
FINALLY, I was able to load the recovery and wipe everything (system,data,cache,sdcard) and flash a 4.4.2 rom of my choice!
Everything works perfectly now, I'm so relieved! Thank you again thay10 for your help. Hopefully this can help someone else out as well.
anyone?
Okay first thing. Looks like your doing a dirty flash and going from rom to rom may cause problems and clutter.
What I would advise is you to do a clean flash which involves you wiping. cache,data,system,sdcard.
But ONLY do this after you backup files you need, and make sure you have fastboot and adb installed and is working properly on your computer.
Edit: Are you still soff and bootloader unlocked?
thayl0 said:
Okay first thing. Looks like your doing a dirty flash and going from rom to rom may cause problems and clutter.
What I would advise is you to do a clean flash which involves you wiping. cache,data,system,sdcard.
But ONLY do this after you backup files you need, and make sure you have fastboot and adb installed and is working properly on your computer.
Edit: Are you still soff and bootloader unlocked?
Click to expand...
Click to collapse
Thank you for the advice. Yes I am S-off and my bootloader is unlocked. I noticed that the version of cwm I had installed was not wiping the system folder so I flashed 'Philz Touch 6' cwm and used that to do a full wipe including system,data,cache,sdcard and then used adb sideload to flash a couple roms. Each rom I flashed after a full wipe still won't boot. I continue to loop through the htc logo.
ADB and fastboot are both working properly, and htc drivers are fully up to date.
Roms I am currently trying to flash are:
AOKP unofficial (4.4.2)
BeanStalk (4.4.2)
CM-11 Nightly (4.4.2)
OSE Official (4.4.2)
stevenschemers said:
Thank you for the advice. Yes I am S-off and my bootloader is unlocked. I noticed that the version of cwm I had installed was not wiping the system folder so I flashed 'Philz Touch 6' cwm and used that to do a full wipe including system,data,cache,sdcard and then used adb sideload to flash a couple roms. Each rom I flashed after a full wipe still won't boot. I continue to loop through the htc logo.
ADB and fastboot are both working properly, and htc drivers are fully up to date.
Click to expand...
Click to collapse
I've never used CWM so I'll half to pass it on to someone else to help you.
Maybe you can try and flash a 3.04 RUU and or try flash TWRP which I know works because I use it everyday,
thayl0 said:
I've never used CWM so I'll half to pass it on to someone else to help you.
Maybe you can try and flash a 3.04 RUU and or try flash TWRP which I know works because I use it everyday,
Click to expand...
Click to collapse
No problem. I was using TWRP for the longest time but I read a few different places that people were having issues flashing cm-11 on some versions of TWRP and to explorer versions of CWM that worked.
I have RUU downloaded but I have not ran it yet. What exactly will RUU do?
-EDIT- Also when would I run RUU? Would I have to restore my nandroid backup first or can it read my phone while in recovery through adb?
-EDIT- I went ahead and flashed RUU 3.04 while in the bootloader. It says it's sending to my phone right now so I will update shortly with a result.
thayl0 said:
I've never used CWM so I'll half to pass it on to someone else to help you.
Maybe you can try and flash a 3.04 RUU and or try flash TWRP which I know works because I use it everyday,
Click to expand...
Click to collapse
I flashed the latest TWRP and when I sideload the rom I get the error saying "Error executing updater binary in zip '/data/'
This is the issue I was reading about when people were saying they couldn't flash cm-11 with TWRP. I've even tried installing cm-10.2 roms and had the same issue.
thayl0 said:
I've never used CWM so I'll half to pass it on to someone else to help you.
Maybe you can try and flash a 3.04 RUU and or try flash TWRP which I know works because I use it everyday,
Click to expand...
Click to collapse
The RUU 3.04 flash finished and I got "ERROR 158; Image error. The rom update utility cannot update your android phone. Please get the correct rom update utility and try again."
Any idea what would cause that?
RUU was downloaded from HERE.
stevenschemers said:
No problem. I was using TWRP for the longest time but I read a few different places that people were having issues flashing cm-11 on some versions of TWRP and to explorer versions of CWM that worked.
I have RUU downloaded but I have not ran it yet. What exactly will RUU do?
-EDIT- Also when would I run RUU? Would I have to restore my nandroid backup first or can it read my phone while in recovery through adb?
-EDIT- I went ahead and flashed RUU 3.04 while in the bootloader. It says it's sending to my phone right now so I will update shortly with a result.
Click to expand...
Click to collapse
TWRP last time I checked didn't support CM thats why people switched to CWM
What are you trying to do to your phone? Most people only run RUU to get to stock.
---------- Post added at 02:42 AM ---------- Previous post was at 02:40 AM ----------
stevenschemers said:
The RUU 3.04 flash finished and I got "ERROR 158; Image error. The rom update utility cannot update your android phone. Please get the correct rom update utility and try again."
Any idea what would cause that?
RUU was downloaded from HERE.
Click to expand...
Click to collapse
I'm guessing you ran the exe. I was refering to the one thats a zip file and you flash it
Hello ,
since two days i am trying to install a custom rom on my htc desire x. I repeated every single step several times to make sure everything still is fine.
(unlook, flash boot, flash recovery / tried twmp and cwm, etc..)
The only rom which works for me ist the cM10-2-20138004-unofficial. But with restrictions. WLAN doesn't work, media manager isn't starting. Cant hear the partner when calls are incoming.
I tried mySense, Half_Sense, myOnedx, but after finishing installation the device hangs on startup. I waited hours and minutes but nothing happened.
I tried several RUU´s but can't find the right ones for me, or i got the 155 error message.
There is no OS installed on the device. How can i get the device up an running? I would be really happy if somebody can give me a hint whats going wrong.
Thx in advance
Dont worry all ****s can be fixed.Wha is ur hboot ? Or simply before to try to install custom rom U was with ICS rom or JB ?.You have to use the right recovery.Look what rom you want to flash, if you on ics hboot u cant just flash jb room (Some roms already have this funcion)
Ps:
After flasing the rom go in boothloader and flash boot.img And away do full wipe
What you need to make sure when installing a ROM: Install a suitable kernel. When installing a Sense ROM, install a Sense custom kernel or the stock kernel. Installing CM isn't advisable, because it's not ready for daily use yet. Also, make sure you use the right recovery for right hboot.
Good Morning,
thx for reply. I want to install the myOnedx_RC4.0 FX. I extracted the boot.img from zip. Installed the rom, wiped, reboot and installed the boot.img.
But that failed. Again, the cyanogen start up occurs for hours and hours. The device doesnt start.
Also tried the same wir the mySENSEdx5_RC4
I evem tried to install the nexuskernelv3.img
I am on hboot 1.25.002
Anyone an idea what wrong with my installation?
Thx
Again: Which custom recovery are you using? Please post a link to the thread here, so we can see what you've installed. Also, as first time user, you should check this and this.
Sorry i forgot. I am using TWRP 2.6.3.0 as custom recovery
Ok, strange, as this one works for me without problems. However, try the 2.5.0.0 version for JB and see if it goes without problems then. Also be sure to wipe system, dalvik cache, cache and data partition before installing a new ROM.
Same with version 2.5.0.0. I tried clockworkmod recovery, but as soon as i try to wip i got the error messages:
cant mount cache/recovery
cant open cache/revocery
So how can i get back to a stock rom? I tried the way described in here: http://forum.xda-developers.com/showthread.php?p=41327224
, but restore failed.
Any other ideas?
If you want to get back to stock, you need to know your CID first. After that, check this thread: http://forum.xda-developers.com/showthread.php?t=2324815
As you have JB hboot, you need to restore a JB backup. In the thread I linked you to are backups of several CIDs. If yours isn't there, you won't be able to return to stock.
Ok thanks. So it is not in there. I got the cid VODAP102.
Does that mean my device is gone? Or can i even try other workarounds?
Thanks
So i installed odexed rom and this one works fine. Do not know why all the other roms not working to me.
Maybe anyone an idea.
Otherwise thanks for your support.
Lastmenstanding said:
Does that mean my device is gone? Or can i even try other workarounds?
Thanks
Click to expand...
Click to collapse
Your hboot : 1.25.0002
Recovery to flash - JB recovery download from here : http://d-h.st/VjM
fastboot flash recovery command : fastboot flash recovery recovery.img
For a test ROM to flash, flash this stock ROM : http://forum.xda-developers.com/showthread.php?t=2239511
also make sure to fastboot flash boot boot.img
(boot.img is attached on OP)
Once everything run, it is up to you to try any other ROM and any other boot.img
Lastmenstanding said:
So i installed odexed rom and this one works fine. Do not know why all the other roms not working to me.
Maybe anyone an idea.
Otherwise thanks for your support.
Click to expand...
Click to collapse
It's either you flash ROM with wrong recovery type or wrong boot.img type or ROM which is not supported on your hboot.
Simple rules:
1) Recovery must be a recovery for JB.
2) Correct boot.img for correct ROM
ICS ROM that support hboot 1.25.0002
Recovery : JB recovery is a must
Boot.img : ICS boot.img is a must
JB ROM which should run fine on hboot 1.25.0002
Recovery : JB recovery is a must
Boot.img : JB boot.img is a must
ICS ROM that does not support hboot 1.25.002 - you need to manually change the mountpoint in updater-script, then
Recovery : JB recovery is a must
Boot.img : ICS boot.img is a must
Yeah, that was the problem, I see now... Have been blind a bit... The ROMs OP has installed on his phone are all ICS ROMs which need changing of updater-script mountpoints. That's why they won't work. @Lastmenstanding: Try any JB ROM available in Android Development section, should work without problems. The ROMs you tried were ICS ROMs especially written for ICS hboot, that's why they didn't work on your phone.
dansou901 said:
Yeah, that was the problem, I see now... Have been blind a bit... The ROMs OP has installed on his phone are all ICS ROMs which need changing of updater-script mountpoints. That's why they won't work. @Lastmenstanding: Try any JB ROM available in Android Development section, should work without problems. The ROMs you tried were ICS ROMs especially written for ICS hboot, that's why they didn't work on your phone.
Click to expand...
Click to collapse
OP mentioned about installing my ICS ROMs. Both ICS ROMs work on JB hboot without a need to edit the updater-script. My guess is he either use wrong recovery (ICS recovery is wrong) or wrong boot.img (JB boot.img is wrong) as it should be JB Recovery and ICS boot.img
..do not know how to use the thank meter, but..
Thank you guys for your excellent support.
Lastmenstanding said:
..do not know how to use the thank meter, but..
Thank you guys for your excellent support.
Click to expand...
Click to collapse
Just thank them at the bottom of their posts...
There is a thanks button at the bottom of every post.
hey everyone.i have a att m8.s-off unlocked rooted.i was running twrp 2.8.01 i think.dirty unicorns for the rom.i was getting ready to flash viper.so i went to recovery to flash just started wiping stuff did the fist wipe cant remember the name of what it was.it wasnt something i wasnt suppost to just one of the normal wipes it did it then the phone rebooted.i think because i started the wioe process the rom wouldnt boot.so i tried to go back and finish everthing.about 30 seconds into recovery the phone tries to reboot.i tried flashin g recovery though fastboot it said it worked but recovery is unusable any help is appreciated.thanks.
Did you try to flash recovery again?
If it dosent work try flashing the RUU and then flash the viperone rom
Ya I flashed recovery it took but recovery just keeps rebooting phone.which ruu should I try.im a little confused with those.thanks for the help.
jhzzer said:
Ya I flashed recovery it took but recovery just keeps rebooting phone.which ruu should I try.im a little confused with those.thanks for the help.
Click to expand...
Click to collapse
4.4.3 is the RUU you'd want to use. Not causing the problem, but are you trying to use 3.2.1 or 2.5.0 viper?
Viper 3.2.1 is there a problem with that version.the problem was my sd card when I pluggedit into computer to load up firmware the computer ask me to format it.when I plugged it back into phone I went to recovery and it worked.thanks for all your help.
jhzzer said:
Viper 3.2.1 is there a problem with that version.the problem was my sd card when I pluggedit into computer to load up firmware the computer ask me to format it.when I plugged it back into phone I went to recovery and it worked.thanks for all your help.
Click to expand...
Click to collapse
You can only run 3.2.1 if you're on build 3.28.401.9 which hasn't been released for AT&T yet. Latest AT&T build is 2.23.502.3 which can only be used with Viper 2.5.0. Flashing Viper 3.2.1 while not on the correct build will cause your WiFi to stop working and probably a few other bugs. You can either flash Viper 2.5.0 or you can flash the 3.28.401.9 International build and run 3.2.1 and Viper will update you to 4.4.4. So you can use the RUU to get back to 4.4.3 (build 2.23.502.3) and run Viper 2.5.0 and wait for the officials AT&T update for 4.4.4 (build 3.28.401.9) or you can flash the International build (3.28.401.9) and run Viper 3.2.1. If you decided to update and want to flash International here is a guide to do it http://venomroms.com/viperonem8_3-0-0-requirements/
I wasn't aware 3.28.401.9 was international that's the one I flashed when it came out.but for whatever reason my sd card was causing recovery not to work right.I'm running viper 3.2.1 now.everything seems to be working good.I only changed Roms because du isn't supporting lollipop when it comes out so I'm trying different ones.
fastboot erase cache and install recovery with fastboot again.
Than restore nandroid. Didn't make one, why the heck not?
If that is the case, flash a known good ROM. adb push the ROM to the phone, or put it on SD with a USB card reader connected to your computer.
The above steps will get you out of a no boot situation from bad recovery or bad flash 99% of the time.
---------- Post added at 11:52 AM ---------- Previous post was at 11:48 AM ----------
jhzzer said:
so i went to recovery to flash just started wiping stuff did the fist wipe cant remember the name of what it was.it wasnt something i wasnt suppost to just one of the normal wipes
Click to expand...
Click to collapse
There is only one default wipe in TWRP (data, Dalvik and Cache). It says "most the time this is the only wipe that you need" and it means what it says. If you picked to go into Advanced (again, its labelled that way for a reason) you better know what you are doing and make sure before you confirm the wipes.
I download the system update for OnePlus x oxygen os 2.2.1. But when I reboot it for installation, there's a message "installation failed". What's wrong with the file? It seems to download everything properly. But error occurs during installation.
Is it rooted? Which recovery r u using? Twrp or stock?
Not rooted
itsmelutfor said:
Is it rooted? Which recovery r u using? Twrp or stock?
Click to expand...
Click to collapse
What have you already modded in the original installation? If your system was stock the update wouldn't fail. Please be more specific so people can help you. If you've kingrooted or flashed twrp, the update will fail...
I don't know about the OP, but I had the same issue when I tried to OTA to OOS 2.2.1. I applied all my hacks through TWRP but always booting TWRP by ADB and never flashing TWRP to the phone. So, I have unlocked bootloader, Developer settings, stock recovery, Boeffla, CameraHAL. With this, OOS 2.2.1 OTA gave me "installation failed". Shouldn't it have worked since I was still in stock recovery?
Thinking it could be the kernel I then tried to restore the original kernel by going to a TWRP backup I made immediately before flashing Boeffla, and restoring boot.img. To my surprise, I then lost all Wi-Fi functionality.
In the end, I downloaded the full OOS 2.2.1 ROM from OnePlus and dirty-flashed it, stacking it before the newest versions of Boeffla and CameraHAL. Phone is working OK, no bugs noticed so far.
I still haven't flashed TWRP nor rooted the phone. In my configuration, what's stopping OTA from working? It would be nice to have OOS3 OTA, since I still don't trust the backups I'm making.
Sent from my ONE E1003 using XDA Labs
TiagoJSilva said:
I don't know about the OP, but I had the same issue when I tried to OTA to OOS 2.2.1. I applied all my hacks through TWRP but always booting TWRP by ADB and never flashing TWRP to the phone. So, I have unlocked bootloader, Developer settings, stock recovery, Boeffla, CameraHAL. With this, OOS 2.2.1 OTA gave me "installation failed". Shouldn't it have worked since I was still in stock recovery?
Thinking it could be the kernel I then tried to restore the original kernel by going to a TWRP backup I made immediately before flashing Boeffla, and restoring boot.img. To my surprise, I then lost all Wi-Fi functionality.
In the end, I downloaded the full OOS 2.2.1 ROM from OnePlus and dirty-flashed it, stacking it before the newest versions of Boeffla and CameraHAL. Phone is working OK, no bugs noticed so far.
I still haven't flashed TWRP nor rooted the phone. In my configuration, what's stopping OTA from working? It would be nice to have OOS3 OTA, since I still don't trust the backups I'm making.
Sent from my ONE E1003 using XDA Labs
Click to expand...
Click to collapse
If you modify even a single bit in stock rom and revert back, updates are definitely going to fail.
The only solution to receive OTAs is flashing stock recovery with stock rom with locked bootloader.
Or you can manually flash OTAs using TWRP.
I made several backups of my stock rom before testing mods, but when I restored and tried to perform OTAs, it always failed while installing.
prabhat.singh.836 said:
If you modify even a single bit in stock rom and revert back, updates are definitely going to fail.
The only solution to receive OTAs is flashing stock recovery with stock rom with locked bootloader.
Or you can manually flash OTAs using TWRP.
I made several backups of my stock rom before testing mods, but when I restored and tried to perform OTAs, it always failed while installing.
Click to expand...
Click to collapse
You just need to wipe cache from the stock recovery in order to install the ota updates , customer care babe told me
---------- Post added at 03:44 AM ---------- Previous post was at 03:43 AM ----------
Hello guys, I unlocked my bootloader...now would I get the ota updates? It's not rooted and on stock ROM.
If no then please tell me how to revert back to locked bootloader.
TiagoJSilva said:
I don't know about the OP, but I had the same issue when I tried to OTA to OOS 2.2.1. I applied all my hacks through TWRP but always booting TWRP by ADB and never flashing TWRP to the phone. So, I have unlocked bootloader, Developer settings, stock recovery, Boeffla, CameraHAL. With this, OOS 2.2.1 OTA gave me "installation failed". Shouldn't it have worked since I was still in stock recovery?
Thinking it could be the kernel I then tried to restore the original kernel by going to a TWRP backup I made immediately before flashing Boeffla, and restoring boot.img. To my surprise, I then lost all Wi-Fi functionality.
In the end, I downloaded the full OOS 2.2.1 ROM from OnePlus and dirty-flashed it, stacking it before the newest versions of Boeffla and CameraHAL. Phone is working OK, no bugs noticed so far.
I still haven't flashed TWRP nor rooted the phone. In my configuration, what's stopping OTA from working? It would be nice to have OOS3 OTA, since I still don't trust the backups I'm making.
Sent from my ONE E1003 using XDA Labs
Click to expand...
Click to collapse
swatidixit710 said:
I download the system update for OnePlus x oxygen os 2.2.1. But when I reboot it for installation, there's a message "installation failed". What's wrong with the file? It seems to download everything properly. But error occurs during installation.
Click to expand...
Click to collapse
deathaddder said:
You just need to wipe cache from the stock recovery in order to install the ota updates , customer care babe told me
---------- Post added at 03:44 AM ---------- Previous post was at 03:43 AM ----------
Hello guys, I unlocked my bootloader...now would I get the ota updates? It's not rooted and on stock ROM.
If no then please tell me how to revert back to locked bootloader.
Click to expand...
Click to collapse
I have tried wipe cache method and doesn't works at all if you have rooted your phone and unrooted back.
And the OTA should work even with unlocked bootloader, if you have not rooted your phone before.
If you want to lock your bootloader again, just follow these steps,
1. Goto Settings -> Developer options
2. OEM unlocking -> turn it off
Error in installation of OxygenOS2.2.1
Having same issue, I doubt why it is not getting installed. Not rooted and not even touchted the kernel. Is it a bug or it requires a flash ?
Ankit_Lal said:
Having same issue, I doubt why it is not getting installed. Not rooted and not even touchted the kernel. Is it a bug or it requires a flash ?
Click to expand...
Click to collapse
Did you try to flash the full rom zip here?
http://downloads.oneplus.net/2016-04-20/opx/OnePlus_X_OxygenOS_2.2.1-X/
Cannot update to Oxygen OS 2.2.1
Yup ! I tried the same but it fails repetedly
Is there anyone who is facing the same issue ?
Ankit_Lal said:
Yup ! I tried the same but it fails repetedly
Is there anyone who is facing the same issue ?
Click to expand...
Click to collapse
I have the same problem. Brand new phone, out of box, Oxygen version 2.1.0.