Even after 2I3 update touch screen issue near center of phone still exists. Any Suggestions?
indiangamer007 said:
Even after 2I3 update touch screen issue near center of phone still exists. Any Suggestions?
Click to expand...
Click to collapse
Please flash fastboot images of CMOS12 2l3 if you updated from last version of CMOS12 via OTA
Reference link http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Most of the issue are always solved by flashing fastboot images.
Mr hOaX said:
Please flash fastboot images of CMOS12 2l3 if you updated from last version of CMOS12 via OTA
Reference link http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
Most of the issue are always solved by flashing fastboot images.
Click to expand...
Click to collapse
To be able to flash fastboot images, we need unlocked bootloader, right?
Related
As Title asking,How do I do it?
I am trying to do that in recovery mode but facing the dialog which said you have installed 1.0.2 already.
Do I need to do full flash again or can omit this step?
The reason of why I downgrade the kernal due to performance slower than 1.0.1
I encountered system response lag(hang over about 2 mins) so many times
alan_lin said:
As Title asking,How do I do it?
I am trying to do that in recovery mode but facing the dialog which said you have installed 1.0.2 already.
Do I need to do full flash again or can omit this step?
The reason of why I downgrade the kernal due to performance slower than 1.0.1
I encountered system response lag(hang over about 2 mins) so many times
Click to expand...
Click to collapse
You can flash the older kernel over your current one in recovery (or via fastboot), shouldn't give you any problems.
astar26 said:
You can flash the older kernel over your current one in recovery (or via fastboot), shouldn't give you any problems.
Click to expand...
Click to collapse
Thanks,
I tried and got the dialog as previous my mention,
This dialog prevents me to go next step.
alan_lin said:
Thanks,
I tried and got the dialog as previous my mention,
This dialog prevents me to go next step.
Click to expand...
Click to collapse
did you try with fastboot command?
rzr86 said:
did you try with fastboot command?
Click to expand...
Click to collapse
Yes,I tried to flash the old kernal(boot.img) via fastboot command.
But caused the WiFi can not be detected.
alan_lin said:
Yes,I tried to flash the old kernal(boot.img) via fastboot command.
But caused the WiFi can not be detected.
Click to expand...
Click to collapse
if the wifi shows error then flash again the boot.img from 1.0.2
i can't think something else for going back to 1.0.1 just only reflashing full rom and then 1.0.1 update
rzr86 said:
if the wifi shows error then flash again the boot.img from 1.0.2
i can't think something else for going back to 1.0.1 just only reflashing full rom and then 1.0.1 update
Click to expand...
Click to collapse
Sorry for late reply,I have fixed it by manually modify the script in 1.0.1 zip file due to script has error protection.
It is come back right now,Thanks everyone.
Hi,
I downloaded and attempted to install OTA update 63, on my Shield running stock system updated to 59, unlocked, rooted and having flashed CWM recovery.
CWM failed to flash the 63 OTA because of the blob flashing issue, as I read on the CWM thread, so I flashed back the stock recovery. However now the system updater always finds that my OS is up-to-date even though I am still on OTA 59. I tried to wipe data for a couple of Nvidia apps (Nvidia services and system updater) to no avail. Any ideas on what to do to force OTA update? I'd rather avoid factory resetting just for that...
Cheers!
Nikojiro said:
Hi,
I downloaded and attempted to install OTA update 63, on my Shield running stock system updated to 59, unlocked, rooted and having flashed CWM recovery.
CWM failed to flash the 63 OTA because of the blob flashing issue, as I read on the CWM thread, so I flashed back the stock recovery. However now the system updater always finds that my OS is up-to-date even though I am still on OTA 59. I tried to wipe data for a couple of Nvidia apps (Nvidia services and system updater) to no avail. Any ideas on what to do to force OTA update? I'd rather avoid factory resetting just for that...
Cheers!
Click to expand...
Click to collapse
I'm having the same issue. No idea, we might just have to wait a while.
Delete Data from Google Framework Apk and then start the Update Checker.
UNCUT88RAW said:
Delete Data from Google Framework Apk and then start the Update Checker.
Click to expand...
Click to collapse
Aah didn't think of that trick, it works, <thank you> pressed :laugh:
Could someone please give me a link to the Stock Recovery and maybe a description what the best way is to flash it instead of the Custom Recovery? Thanks ...
I have had no problems flashing updates with ClockWorkMOD revocery.
However if you have the 1.0 version from http://forum.xda-developers.com/showthread.php?t=2390389 the update will fail with an error.
1.0 had a name wrong that makes it think the update are for a different device.
the command to flash the stock recovery (if every thing is in the correct place) is "fastboot flash recovery recovery.img"
chevyowner said:
1.0 had a name wrong that makes it think the update are for a different device.
Click to expand...
Click to collapse
Ah, maybe this is causing the error! Okay, I will try to flash 1.1 before going back to stock recovery.
Unfortunately the link for v1.1 is down. Would you be able to mirror it for me please?
Thanks!
fquadrat said:
Ah, maybe this is causing the error! Okay, I will try to flash 1.1 before going back to stock recovery.
Unfortunately the link for v1.1 is down. Would you be able to mirror it for me please?
Thanks!
Click to expand...
Click to collapse
When I was checking to see if I had 1.1 I found the naming error is still there.
This brings me to my next point. I had edited the ramdisk on 1.0 to correct the naming error, and not updated to 1.1
Here is a link to 1.1 with the edited ramdisk.
Update
I messed up the link in Google drive i think i fixed it now.
chevyowner said:
Here is a link to 1.1 with the edited ramdisk.
Click to expand...
Click to collapse
Unfortunately I think there is something broken with your attached file. After flashing it, I can't access the recovery anymore. The background light of the screen is constantly turning on and off but nothing appears on the screen. Fortunately I can still access Fastboot and Android.
fquadrat said:
Unfortunately I think there is something broken with your attached file. After flashing it, I can't access the recovery anymore. The background light of the screen is constantly turning on and off but nothing appears on the screen. Fortunately I can still access Fastboot and Android.
Click to expand...
Click to collapse
Try this it "should" be the recovery I currently have flashed
EDIT
It instead of flashing the recovery to test it, use "fastboot boot recovery.img"
chevyowner said:
It instead of flashing the recovery to test it, use "fastboot boot recovery.img"
Click to expand...
Click to collapse
Sorry, I just flashed stock recovery and my Shield is installing Android 4.3 right this second ...
chevyowner said:
Try this it "should" be the recovery I currently have flashed
EDIT
It instead of flashing the recovery to test it, use "fastboot boot recovery.img"
Click to expand...
Click to collapse
I really need that img. Going to test now. Thanks!
This is the one that can install zips without the error right?
desertflame said:
I really need that img. Going to test now. Thanks!
This is the one that can install zips without the error right?
Click to expand...
Click to collapse
should be
I cannot seem to be able to update my bootloader to flash new nightlys for Vanir. I have extracted the radio and bootloader from the factory image, but I cannot flash them. I keep getting an access denied from adb, while I'm in fastboot.
you cannot use adb in fastboot. You can only use fastboot in fastboot. adb only works in recovery or android
Sent from my Nexus 5 using Tapatalk
TheAfroGuy said:
I cannot seem to be able to update my bootloader to flash new nightlys for Vanir. I have extracted the radio and bootloader from the factory image, but I cannot flash them. I keep getting an access denied from adb, while I'm in fastboot.
Click to expand...
Click to collapse
Correct me if wrong but what you want to update is your recovery.
GUGUITOMTG4 said:
Correct me if wrong but what you want to update is your recovery.
Click to expand...
Click to collapse
No.idea about this rom.but latest cm11 requires users to be on.latest bootloader and have get.prop checks in updater-script too
Sent from my Nexus 5 using Tapatalk
TheAfroGuy said:
I cannot seem to be able to update my bootloader to flash new nightlys for Vanir. I have extracted the radio and bootloader from the factory image, but I cannot flash them. I keep getting an access denied from adb, while I'm in fastboot.
Click to expand...
Click to collapse
Hi,
Easier, see in attachment for a flashable zip (it's the last one)...
Hammer_Of_The_Gods said:
Hi,
Easier, see in attachment for a flashable zip (it's the last one)...
Click to expand...
Click to collapse
So I managed to flash the bootloader and radio, but I still cannot flash any CM based ROM. I keep getting a Status 7 error.
TheAfroGuy said:
So I managed to flash the bootloader and radio, but I still cannot flash any CM based ROM. I keep getting a Status 7 error.
Click to expand...
Click to collapse
Did you reboot after the flash?
Sent from my Nexus 5 using Tapatalk
Please help...I recieved my OPO today. It was a chinese version that was supposed ot ship with CM 11s but instead had just regular cm11. I was trying to flash it with twrp recovery first...but could not see a zip file that would flash correctly on the CM OPO page. I ended up trying to use ADB but ended up bricking my phone. I can get into Fastboot mode but that's all. What can I do now to get it workign again...can't even seem to get into recovery anymore. Please help.
acheney1990 said:
Please help...I recieved my OPO today. It was a chinese version that was supposed ot ship with CM 11s but instead had just regular cm11. I was trying to flash it with twrp recovery first...but could not see a zip file that would flash correctly on the CM OPO page. I ended up trying to use ADB but ended up bricking my phone. I can get into Fastboot mode but that's all. What can I do now to get it workign again...can't even seem to get into recovery anymore. Please help.
Click to expand...
Click to collapse
Try flashing a stock image.. follow the instructions on this page: http://forum.xda-developers.com/oneplus-one/general/guide-return-opo-to-100-stock-t2826541
extract the image into your adb/fastboot folder and then Run flash-all.bat (if your bootloader is unlocked, if not make sure you unlock it using one of the toolkits available then run flash-all.bat)
Hope this helps.
acheney1990 said:
Please help...I recieved my OPO today. It was a chinese version that was supposed ot ship with CM 11s but instead had just regular cm11. I was trying to flash it with twrp recovery first...but could not see a zip file that would flash correctly on the CM OPO page. I ended up trying to use ADB but ended up bricking my phone. I can get into Fastboot mode but that's all. What can I do now to get it workign again...can't even seem to get into recovery anymore. Please help.
Click to expand...
Click to collapse
I'm assuming your bootloader is unlocked? All you need to do is flash TWRP recovery from here.
Code:
fastboot flash recovery <filename>.img
And then grab one of the recovery flashable versions of CM11S from this thread and flash it. That's your easiest solution.
Transmitted via Bacon
I got it everyone. Thanks though.
Can a moderator please delete those thread.
acheney1990 said:
Can a moderator please delete those thread.
Click to expand...
Click to collapse
No they won't delete it, plus it's good that it remains because the information is now readily available for anyone else who gets into the same situation.
Transmitted via Bacon
I spent all day trying to make this work. I had root but took an OTA by accident. I'm on 8.1 stock and can't check for updates or update locally. I also cannot fastboot twrp. It reboots to a fastboot mode screen. I've tried many versions of twrp new and old. I haven't found an answer yet. Anyone seen this before? Thanks
Bubba Fett said:
I spent all day trying to make this work. I had root but took an OTA by accident. I'm on 8.1 stock and can't check for updates or update locally. I also cannot fastboot twrp. It reboots to a fastboot mode screen. I've tried many versions of twrp new and old. I haven't found an answer yet. Anyone seen this before? Thanks
Click to expand...
Click to collapse
What fastboot commands have you tried?
mikex8593 said:
What fastboot commands have you tried?
Click to expand...
Click to collapse
Fastboot devices
Fastboot boot twrp. Img
It used to work. It shows through adb that it was successful but op6 reboots to fastboot mode in the center of the screen. I can get the phone recognized by adb when the screen has a green start sign on top.
Bubba Fett said:
I spent all day trying to make this work. I had root but took an OTA by accident. I'm on 8.1 stock and can't check for updates or update locally. I also cannot fastboot twrp. It reboots to a fastboot mode screen. I've tried many versions of twrp new and old. I haven't found an answer yet. Anyone seen this before? Thanks
Click to expand...
Click to collapse
Unbrick tool
Bubba Fett said:
I spent all day trying to make this work. I had root but took an OTA by accident. I'm on 8.1 stock and can't check for updates or update locally. I also cannot fastboot twrp. It reboots to a fastboot mode screen. I've tried many versions of twrp new and old. I haven't found an answer yet. Anyone seen this before? Thanks
Click to expand...
Click to collapse
use this method
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
siddhrsh said:
use this method
https://forum.xda-developers.com/oneplus-6/how-to/rom-stock-fastboot-roms-oneplus-6-t3796665
Click to expand...
Click to collapse
I have that downloaded and ready as my last resort. I was trying to avoid wiping the whole device again but if that's what I have to do I will. Thanks.
Bubba Fett said:
I have that downloaded and ready as my last resort. I was trying to avoid wiping the whole device again but if that's what I have to do I will. Thanks.
Click to expand...
Click to collapse
Remove -w from command
siddhrsh said:
Remove -w from command
Click to expand...
Click to collapse
Ooohh yeah! Thanks man! Have a good New Years!