im having very weird boot loops, which i think is because of full wipes, i couldnt install carhd rom, with full wipe and without..but with crisscross it only works without full wipe. if i fullwiped and installed crisscross, i get stuck in a boot loop...
does anyone have any idea? these are my first roms btw.
Have you updated your bootloader and modem to MM?
Also have you installed TWRP v3.x.x.x (arter has custom recovery for F and I variants).
I'd suggest you do the MM update through odin
Valkiry said:
Have you updated your bootloader and modem to MM?
Also have you installed TWRP v3.x.x.x (arter has custom recovery for F and I variants).
I'd suggest you do the MM update through odin
Click to expand...
Click to collapse
i flashed by being on stock MM, do i still need to flash the bootloaded and modem to MM? im already using the arter TWRP
Related
When I restore a backup of rls 19 hyperdrive that i made on an older (2.6.x.x) version of TWRP the completion percentage goes OVER 100% then i get bootlooped at the samsung screen, any help? Had to upgrade my TWRP version so I can run lollipop.
Drake9897 said:
When I restore a backup of rls 19 hyperdrive that i made on an older (2.6.x.x) version of TWRP the completion percentage goes OVER 100% then i get bootlooped at the samsung screen, any help? Had to upgrade my TWRP version so I can run lollipop.
Click to expand...
Click to collapse
Bump, would really like some help :/
Back to stock
Drake9897 said:
Bump, would really like some help :/
Click to expand...
Click to collapse
You can follow this guide to Odin back to stock MDK: http://forum.xda-developers.com/showthread.php?t=2301259. Should fix your issue. Once you're there, flash TWRP. Once you've flashed TWRP, flash the ROM that you want. I'm running danvdh's GPE lollipop ROM and TWRP 2.8.4.0 with no issues. The latest version is 2.8.5.0, but I can't get that version to boot for some reason.
I'll try that! Thanks! (sorry for late reply)
just flashed stock and got twrp back, tried to flash my RLS 19 backup and it completes at 3gb out of 1.2gb and 170% out of 100%. ugh :/ also twrp won't install via goo manager, have to use twrp manager .
TheSt33v said:
You can follow this guide to Odin back to stock MDK: http://forum.xda-developers.com/showthread.php?t=2301259. Should fix your issue. Once you're there, flash TWRP. Once you've flashed TWRP, flash the ROM that you want. I'm running danvdh's GPE lollipop ROM and TWRP 2.8.4.0 with no issues. The latest version is 2.8.5.0, but I can't get that version to boot for some reason.
Click to expand...
Click to collapse
z
Also I'm running danvdh's lollipop GPE as well. It's actually the reason i updated twrp and started to get this issue. i'm running the same version of twrp as you and still no hyperdrive backup can restore. ):
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.
1) cm-14.0-20160914-UNOFFICIAL-onyx.zip, 2) cm-14.0-20160917-UNOFFICIAL-onyx.zip
These are the 2 cm14 zips that I tried to flash multiple times (using twrp 3.0.2.0). The flash was successful everytime. But no matter how hard I try, it just won't boot. Just stays stuck on the OnePlus logo for eternity. I just recovered my phone from a soft-brick (no OS, no Recovery) and still continuously trying since days to use cm14.
Please, if anyone can then PLEASE HELP!
amritanshu.sikdar said:
1) cm-14.0-20160914-UNOFFICIAL-onyx.zip, 2) cm-14.0-20160917-UNOFFICIAL-onyx.zip
These are the 2 cm14 zips that I tried to flash multiple times (using twrp 3.0.2.0). The flash was successful everytime. But no matter how hard I try, it just won't boot. Just stays stuck on the OnePlus logo for eternity. I just recovered my phone from a soft-brick (no OS, no Recovery) and still continuously trying since days to use cm14.
Please, if anyone can then PLEASE HELP!
Click to expand...
Click to collapse
Check the bootloader compatibilty of these roms, if they r for the mm bootloader it ll not boot untill u upgrade ur bootloader, check the threads from wer u hv downloaded this...
amritanshu.sikdar said:
1) cm-14.0-20160914-UNOFFICIAL-onyx.zip, 2) cm-14.0-20160917-UNOFFICIAL-onyx.zip
These are the 2 cm14 zips that I tried to flash multiple times (using twrp 3.0.2.0). The flash was successful everytime. But no matter how hard I try, it just won't boot. Just stays stuck on the OnePlus logo for eternity. I just recovered my phone from a soft-brick (no OS, no Recovery) and still continuously trying since days to use cm14.
Please, if anyone can then PLEASE HELP!
Click to expand...
Click to collapse
Most Roms now require you too flash OOS 3.1.3 first. Like mentioned above bootloader issue.
Exodusche said:
Most Roms now require you too flash OOS 3.1.3 first. Like mentioned above bootloader issue.
Click to expand...
Click to collapse
I already flash the OOS 3, but still this problem continues.
File name: OnePlusXOxygen_14_OTA_015_all_201608181615_e03d2112e8ad4bff
Is there any other way how I can manually upgrade my bootloader? That would really help.
amritanshu.sikdar said:
I already flash the OOS 3, but still this problem continues.
File name: OnePlusXOxygen_14_OTA_015_all_201608181615_e03d2112e8ad4bff
Is there any other way how I can manually upgrade my bootloader? That would really help.
Click to expand...
Click to collapse
check out this thread http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
amritanshu.sikdar said:
I already flash the OOS 3, but still this problem continues.
File name: OnePlusXOxygen_14_OTA_015_all_201608181615_e03d2112e8ad4bff
Is there any other way how I can manually upgrade my bootloader? That would really help.
Click to expand...
Click to collapse
I use Oxygen_14_OTA_18_all but there's a couple files posted on the bootloader upgrade threads that allow you not too flash the whole firmware just the partions you need to upgrade.
i am having same issue i was on oxygenos 3.1.3 firmware when i started to flash nogut roms every nogut rom works except cm. i flashed official cynogenmod 14.1 thinking that problem must have been solved but it wont boot it just shows oneplus logo. i have waited for 30 minutes but nothing happened if something worked out for you please tell me.
Well I've looked around XDA for soultion and this is it.
CM 14 has some Kernel problems, so only what you have to do is just install new kernel as Arsenic or Black Reactor kernel
I was running the new bootloader on cm13 nightlies and couldn't get it to boot either.
Even after a full wipe and reflash with v7 gapps
Gave up in the end and went back to the last cm13 Nightly
flash arsenic kernel after flashing rom and gapps it will boot. Read the posts in ashwin's official cm 14.1 thread.
Flash Black Reactor (recommended) or Arsenic Kernel.
The zip files that you have for CM are the unofficial ones. So I guess they're from Sarthak Narang. Or at least one of them. Those ROMs require the older bootloader to function. So if you have the newer bootloader, it won't work.
When I flash only N ROM + Gapps, everything's going normal. But when I flash custom kernel (radon, agni, assassinx), my phone always ended bootloop. Is there something wrong? I'm using Psy_Man's firmware & Official TWRP 3.0.2-2 anyway.
Anyone? Please?
Hi, i found my old gt 9100 galaxy s2 and i want to flash some roms on it or the original one back and working again, but twrp 2.3.2.3 is not letting me flash anything, it says unable to mount '/system, , if anyone could help me i ll appreciate it thanks?
KonC13 said:
Hi, i found my old gt 9100 galaxy s2 and i want to flash some roms on it or the original one back and working again, but twrp 2.3.2.3 is not letting me flash anything, it says unable to mount '/system, , if anyone could help me i ll appreciate it thanks[emoji16]
Click to expand...
Click to collapse
To flash roms like android 4.4.4 you need newer (kitkat compatible) twrp. Yours is outdated.
To flash latest roms you need also an isorec kernel and isorec twrp and you need to increase size of system- and data-partition (there are many threads how to do).
For stockrom you need odin to flash.
Sent from my [device_name] using XDA-Developers Legacy app
TriboDoP said:
To flash roms like android 4.4.4 you need newer (kitkat compatible) twrp. Yours is outdated.
To flash latest roms you need also an isorec kernel and isorec twrp and you need to increase size of system- and data-partition (there are many threads how to do).
For stockrom you need odin to flash.
Click to expand...
Click to collapse
I tried to flash isorec kernel from odin but it fails, and also whatever im trying to flash from twrp is says unable to mount system, and in the mount tab the system is unchecked and i cant check it!
KonC13 said:
I tried to flash isorec kernel from odin but it fails, and also whatever im trying to flash from twrp is says unable to mount system, and in the mount tab the system is unchecked and i cant check it!
Click to expand...
Click to collapse
No idea on which rom you are and what exactly you tried to flash.
So what i would do: using your twrp i would flash a kitkat-compatible custom recovery (cwm or twrp). Then boot straight this kk recovery (do not boot system) and make a clean flash of latest unofficial lineage 11 android 4.4.4 by grzwolf together with isorec twrp 3.1.xxx.zip by the.gangster (this rom has already isorec-kernel).
After that you could carry on with repartioning system and data and flashing nougat roms etc. (Having made a backup before doing all sorts of thing is of course adviced)
Sent from my [device_name] using XDA-Developers Legacy app
TriboDoP said:
No idea on which rom you are and what exactly you tried to flash.
So what i would do: using your twrp i would flash a kitkat-compatible custom recovery (cwm or twrp). Then boot straight this kk recovery (do not boot system) and make a clean flash of latest unofficial lineage 11 android 4.4.4 by grzwolf together with isorec twrp 3.1.xxx.zip by the.gangster (this rom has already isorec-kernel).
After that you could carry on with repartioning system and data and flashing nougat roms etc. (Having made a backup before doing all sorts of thing is of course adviced)
Click to expand...
Click to collapse
Thanks man you saved me!!!!!