Guys please help.
Currently using OPO unlocked. updated the phone maually to Q. but now facing issues like continuous screen non responsive, heavy battery draining, GPS not working properly.
PLease help to go back to 44s from 05Q using TWRP.
Download the 44S stock images here:
http://builds.cyngn.com/factory/bacon/cm-11.0-XNPH44S-bacon-signed-fastboot.zip
Follow the instructions in section 8 of my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
(Without downloading the 05Q images of course)
Don't flash the userdata image or it'll wipe your internal storage.
Transmitted via Bacon
Related
Hello guys,
I installed CM11 a while ago on my Nexus 5. I had no trouble installing it through Cyanogenmods own installer, but now i want to install
the official rom again, so android 4.4.4 Kitkat. But when I want to flash it through TWRP i get the error that there is no MD5 file found.
I got the rom from the official site from Google.
I want to install the clean version of android again because i have some trouble with my battery and want to try if its still a problem with original software
installed.
So can you help me with this?
Thanks in advance.
Eelke91
When you after trouble shooting a battery issue you should wipe your phone and flash the stock image. Do not trouble shoot a battery issue with a custom ROM. Period. There are too many factors involved. And bugs can arise that won't be in a stock image.
I do want to flash to my stock image, but sadly i didnt backup so i want to manually install stock android kitkat.
Eelke91 said:
I do want to flash to my stock image, but sadly i didnt backup so i want to manually install stock android kitkat.
Click to expand...
Click to collapse
You don't have to wipe internal. Just Data and Cache. Go fastboot a stock image. If you aren't backing up Your Apps and you aren't clean flashing ROMs, that's why you are having so many issues. Never dirty flash a ROM unless your ROM Dev says otherwise.
Okay, but im pretty sure I wiped everything trying to install stock android. Atleast i got the message when i wanted to reboot that there was no OS installed..
So if its still possible to fastboot to my stock image can you tell me how to? I've now restored my phone to CM11, which was the last ROM i had installed, so i still can use my phone but its not the stock
image.
Eelke91 said:
Okay, but im pretty sure I wiped everything trying to install stock android. Atleast i got the message when i wanted to reboot that there was no OS installed..
So if its still possible to fastboot to my stock image can you tell me how to? I've now restored my phone to CM11, which was the last ROM i had installed, so i still can use my phone but its not the stock
image.
Click to expand...
Click to collapse
Google nexus factory image. Use that with fastboot.
Sent from my Nexus 5 using XDA Free mobile app
Eelke91 said:
Okay, but im pretty sure I wiped everything trying to install stock android. Atleast i got the message when i wanted to reboot that there was no OS installed..
So if its still possible to fastboot to my stock image can you tell me how to? I've now restored my phone to CM11, which was the last ROM i had installed, so i still can use my phone but its not the stock
image.
Click to expand...
Click to collapse
The instructions to flash a factory image are on the same page you download the image from. You need to flash it with fastboot, not recovery.
Okay i flashed it back to the stock os but still problems with my battery so i think its broken..
Eelke91 said:
Okay i flashed it back to the stock os but still problems with my battery so i think its broken..
Click to expand...
Click to collapse
Not likely. Probably just wakelocks. Go visit the battery help thread in my signature
With Nexus devices you can download a factory image that wipes EVERYTHING (even your custom recovery) and flashes stock EVERYTHING from scratch, all with one batch file, no "extras" or anything else needed. You simply run the batch file, wait a few minutes, and voila you're doneāno need to worry about whether you're using the proper modem/radio/whatever.
But my head is spinning after spending two minutes reading different threads about how to flash the latest OPO release. Now, I don't mind learning how to do things with this phone, this isn't my first rodeo and I realize sometimes you have to dig deeper. I'm just wondering if OP provides an official factory image that does everything all at once without having to worry about flashing extras and making sure you're on the proper radio/modem/whatever.
(Note, I'm not asking about someone's zip that they've compiled and rooted.) Thanks!
You might benefit from reading some important threads for our device:
OnePlus One How-To:
http://forum.xda-developers.com/showthread.php?t=2839471
OnePlus One FAQ:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
OnePlus One Compilation Index:
http://forum.xda-developers.com/showthread.php?t=2843675
Look at section 8 of my guide for instructions on how to flash the stock images.
Pretty much everything you could want to ask about this device has already been asked and answered before, so checking out the stickies and using the search feature should be your first port of call before creating new threads.
Transmitted via Bacon
Thanks!
OK so I read A LOT in all of those threads, and even followed some links to further threads. There's a lot to take in, so I'm sorry if it wasn't ever perfectly clear whether "signed fastboot zip" is the same as "fastboot image", and whether either of those is the equivalent of Nexus factory images (in other words, whether they wipe literally everything, including recovery/modem/radio/etc, and re-install it all from scratch).
Also, am I understanding properly that "XNPH44S" (aka "44s") is the latest CM11s factory image version? So I can use fastboot to flash that and I'll be on the most proper modem/radio (obviously it flashes the data, cache and so forth, I'm concerned about whether it will update my modem/radio to the proper versions) then I can use the stock update feature to obtain the latest incremental update?
.psd said:
Thanks!
OK so I read A LOT in all of those threads, and even followed some links to further threads. There's a lot to take in, so I'm sorry if it wasn't ever perfectly clear whether "signed fastboot zip" is the same as "fastboot image", and whether either of those is the equivalent of Nexus factory images (in other words, whether they wipe literally everything, including recovery/modem/radio/etc, and re-install it all from scratch).
Also, am I understanding properly that "XNPH44S" (aka "44s") is the latest CM11s factory image version? So I can use fastboot to flash that and I'll be on the most proper modem/radio (obviously it flashes the data, cache and so forth, I'm concerned about whether it will update my modem/radio to the proper versions) then I can use the stock update feature to obtain the latest incremental update?
Click to expand...
Click to collapse
Signed fastboot zip = fastboot image = stock image = the equivalent of Nexus stock images. It wipes every partition and flashes new. 44S is the latest version that's available in that format. 05Q is the actual latest version (released yesterday) but it hasn't been made available in that format by CM yet. So, flash the 44S stock images and then you'll receive the 05Q update.
Transmitted via Bacon
timmaaa said:
Signed fastboot zip = fastboot image = stock image = the equivalent of Nexus stock images. It wipes every partition and flashes new. 44S is the latest version that's available in that format. 05Q is the actual latest version (released yesterday) but it hasn't been made available in that format by CM yet. So, flash the 44S stock images and then you'll receive the 05Q update.
Transmitted via Bacon
Click to expand...
Click to collapse
Thanks for the clarification! Makes a lot more sense to my puny brain when put straightforward like that.
When returning my phone, do I need to swap it back to 44S or is it okay to leave CM12?
It's probably best to return it to stock, follow the instructions in section 8 of my guide thread here:
http://forum.xda-developers.com/showthread.php?t=2839471
That'll put CM11S (05Q build) back onto it.
Transmitted via Bacon
Yesterday I decided to flash the new 6.0 Marshmallow everything went smooth and fine I just wanted to check how does the new CM handles and after couple of hours decided to recover my old ROM but once I did it and my phone booted up the radio was not working(wi-fi, 3g, cellular networks) the phone was constantly rebooting. I thought myself that this is a problem caused from a new radio which was included in the new Marshmallow so I decided to clean flash Temasek's Rom installed everything correctly followed all of the instructions but still I got the same problem.After that I tried to go back to Marshmallow but I was having exact the same problem so I started worrying how to get my phone work properly. Then I decided to restore my phone to stock CM11s I have downloaded it and booted into recovery. After flashing it phone wont boot at all I mean just black screen nothing works I had about 40% battery once I did it. After that I pluged my phone into the charge for about 5-6 hours and now still wont boot up or show anything.
So my questions is why my phone is not booting at all and why I was having this radio problem what caused it?
Well I managed to bring it back to life with this useful thread but still the radio is not working.
You can just flash 44S Modem via Fastboot or full CM12.1 Firmware. I will leave out a link for 44S Modem down. CM12.1 Firmware can be flashed via TWRP anyways Check your Baseband and IMEI anyway... If any one is missing then get ready for the big challenge
44S Modem: https://www.androidfilehost.com/?fid=95784891001607675
PS: Flash it through FASTBOOT only!!! Else won't work
Sanjiv Kumar said:
You can just flash 44S Modem via Fastboot or full CM12.1 Firmware. I will leave out a link for 44S Modem down. CM12.1 Firmware can be flashed via TWRP anyways Check your Baseband and IMEI anyway... If any one is missing then get ready for the big challenge
44S Modem: https://www.androidfilehost.com/?fid=95784891001607675
PS: Flash it through FASTBOOT only!!! Else won't work
Click to expand...
Click to collapse
I think that I'm ready for a the big challenge both of them are missing . What can I do now
You're gonna face a lot of difficulties now!!
weriwd said:
I think that I'm ready for a the big challenge both of them are missing . What can I do now
Click to expand...
Click to collapse
I hope that your Wi-Fi is working... If it's not, then you have to flash ColorOS to get it back (I will drop a link to it at last. Just do what it says and don't be mislead by the title. It works and is the only way)
Try this first: http://forum.xda-developers.com/oneplus-one/help/fix-brickloop-audio-fx-fc-efs-corrupt-t2879061
If that doesn't work, try flashing Stock 44S via Fastboot (I will drop the link for it too.)
If both of these don't work, then you're gonna spend a lot of time brother...
If you're quite experienced in flashing and stuff, this is gonna be a cake for you. But if you're a first timer... Get READY!!
You have to follow this guide carefully... You would have to translate it anyway (I reckon its German):
http://www.htcmania.com/showthread.php?t=969255.
For any doubts (after reading the WHOLE CONTENT on the links that I provided) contact me directly on Mail or PM.
Downloads:
ColorOS: https://forums.oneplus.net/threads/solution-recover-from-hard-bricked-oneplus-one.104943/
44S Fastboot: https://www.androidfilehost.com/?fid=95784891001613103
I hope you will fix it soon and report to me Don't forget to leave a :good:
Followed this guide didn't solve the problem after that I erased the modemset:
fastboot erase modemst1
fastboot erase modemst2
fastboot erase persist
Then I flashed OxygenOS 1.0.0. and it's running normal without any problems!! :victory:
Thanks a lot for the help mate :highfive:
Hey weriwd, jus to inform u dat always keep the backup of ur stock rom. Coz I too found myself in a great trouble after flashing miui 7 rom on my opo. The rom installed correctly but wen I thought of flashing blisspop back, it won't allow me to flash any other custom rom. Den using opo toolbox I flashed cm11s. So bro jus keep stock rom backed up. It will save ur life?
....................
Did you try reflashing your stock boot.img Or jsut dirty flash your Stock Rom. just get the full OTA and flash it. If that doesn't work you can always use the Fastboot Rom of the firmware you're on. If you're on 9.5.8 then you must use the Fastboot Rom for 9.5.8. This however will wipe all your internal storage as well and you'll loose any and all files on the phone. If you can still see the phone with your PC I'd backup your files first if that matters to you. If all that fails you should use the MSM Tool.
Eric214 said:
Did you try reflashing your stock boot.img Or jsut dirty flash your Stock Rom. just get the full OTA and flash it. If that doesn't work you can always use the Fastboot Rom of the firmware you're on. If you're on 9.5.8 then you must use the Fastboot Rom for 9.5.8. This however will wipe all your internal storage as well and you'll loose any and all files on the phone. If you can still see the phone with your PC I'd backup your files first if that matters to you. If all that fails you should use the MSM Tool.
Click to expand...
Click to collapse
thanks, a guy on the the Havoc Thread (where i posted the question first) wrote while I was posting this thread.. It seems my Problem wasn't that bad after all .. One just has to press Volume up AND Volume DOWN at same time .. i was just pressing and holding volume UP (maybe in combination with power button like on the galaxy s9)... Now I see that these OP phones are not so easy to brick.. even after bootloader unlock, root twrp and custom rom (and rom installed wrong way) it still kept the FACTORY ONEPLUS RECOVERY MENU ! Fastboot also works so I can push twrp etc. (same steps I did 1 hour ago after first unlocking it)
Why did you delete the text in your top post (that described the issue) as well as change the thread title to only say "resolved"?
This content should be kept, as it may be useful to other xda members with a similar issue. Simply adding [SOLVED] to the thread title (but keeping the original thread title as a description of the problem) is the best practice.