gyroscope/ autorotation not working after 5.1 roms flashed. - ONE Q&A, Help & Troubleshooting

No matter what cm 12.1/5.1 roms I flashed, the gyroscope sensor isn't working. If I flashed back to cm 12.0 roms or lower, it works again. What could be the issue?

sseng587 said:
No matter what cm 12.1/5.1 roms I flashed, the gyroscope sensor isn't working. If I flashed back to cm 12.0 roms or lower, it works again. What could be the issue?
Click to expand...
Click to collapse
Revert to some other cm12.1 build nightly instead or flash latest nightly build
May be it's a problem associated with that build

I tried other 12.1 rom, same results. Cm 12.0 is fine though.

Fixed. I fastboot flashed the firmware partition.
take the files out the firmware.zip
and use the steps (8. How To Flash The Cyanogen OS Fastboot Images) from this link
edit: I found the steps! http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
*Only flash the files you extracted from the firmware zip

I have this issue too ... Brand new OnePlus One, put TWRP on it, flashed the latest CyanogenMod 12.1 nightly. Looks like rotation is not working and when I look at apps that show pitch and roll values they are seemingly not getting output from the sensors.
I see that you fixed yours ... But what is this problem from? Did the 12.1 ROM come bundled with bad firmware or something?
When I flash a ROM, maybe I'm ignorant, but I presume that the right and proper firmware and radios are bundled in.
Any advise OP?
Cheers!
cg6ry79m

[email protected] said:
I have this issue too ... Brand new OnePlus One, put TWRP on it, flashed the latest CyanogenMod 12.1 nightly. Looks like rotation is not working and when I look at apps that show pitch and roll values they are seemingly not getting output from the sensors.
I see that you fixed yours ... But what is this problem from? Did the 12.1 ROM come bundled with bad firmware or something?
When I flash a ROM, maybe I'm ignorant, but I presume that the right and proper firmware and radios are bundled in.
Any advise OP?
Cheers!
cg6ry79m
Click to expand...
Click to collapse
Depends on the ROM you flashed. I usually flash the firmware separately and never had issues.
https://www.androidfilehost.com/?fid=23991606952604019
Flash this for CM12.1

Flashed that firmware ROM ... Seemed to go in just fine ... But no joy. Still no rotation/gyro function. Any ideas? Sure would like to fix that.
cg6ry79m

[email protected] said:
Flashed that firmware ROM ... Seemed to go in just fine ... But no joy. Still no rotation/gyro function. Any ideas? Sure would like to fix that.
cg6ry79m
Click to expand...
Click to collapse
Same problem here, I think the problem is located in the firmware. So it is something that CM will have to modify. Because the latest firmware (like the one in the zip) is also included in the latest nightly builds.
If rotation is something you need badly you can try the following 2 options:
- use an app to do the rotation like: playstore:rotation manager
- flash the stock CM11 and the accompaning firmware back, reflash the firmware in attachement and then reflash the CM12.1 nightly. (untested)

[email protected] said:
Flashed that firmware ROM ... Seemed to go in just fine ... But no joy. Still no rotation/gyro function. Any ideas? Sure would like to fix that.
cg6ry79m
Click to expand...
Click to collapse
Little update ... Rotation seemed to work for a minute but has since stopped. Frustrating.

Same issue here, all sensors are shown to be off by Sensor Kinetics from Play Store.
Flashing everything from the factory restore image via fastboot did not help...

I have been troubleshooting the issue of rotation/orientation sensors seemingly not working. What I have found on my new OnePlus One, running the latest CyanogenMod 12.1 nightly builds is this:
Once I root the device using SuperSu I cannot regain use of the sensors/auto-rotate. I use the app named Phone Tester and after the phone is rooted the comps/orientation sensors show no output.
If I unroot the phone and reboot several times, the orientation subsystem functionality returns.
No matter what firmware/Cyanogen ROM combination I use the result is the same.
I wonder if anyone else can confirm that their screen rotation ceases to function when the phone is rooted.
Cg6ry79m

davebugyi said:
Depends on the ROM you flashed. I usually flash the firmware separately and never had issues.
https://www.androidfilehost.com/?fid=23991606952604019
Flash this for CM12.1
Click to expand...
Click to collapse
Nooby question ... Doesn't the Cyanogen Nightly that I flash contain the device's firmware also? So if I flash the firmware file above separately, will it not be replaced by the next nightly that I flash? Should I tell TWRP to flash both items every time?
Before, I flashed that firmware that is mentioned above. ... But I feel like maybe it was superseded when I flashed a nightly.
Educate me.
cg6ry79m

[email protected] said:
Nooby question ... Doesn't the Cyanogen Nightly that I flash contain the device's firmware also? So if I flash the firmware file above separately, will it not be replaced by the next nightly that I flash? Should I tell TWRP to flash both items every time?
Before, I flashed that firmware that is mentioned above. ... But I feel like maybe it was superseded when I flashed a nightly.
Educate me.
cg6ry79m
Click to expand...
Click to collapse
Yes, the nightly contains and will overwrite your firmware. When going from CM to a different ROM, you don't have to flash the firmware again. As long as the android version is the same ofcourse.
Abiut your problem, do you use Superuser or SuperSU? Make sure you flash the latest SuperSU zip. More people had problems with the built in one from TWRP
Sent from my A0001 using XDA Free mobile app

cantthinkofagoodname said:
Yes, the nightly contains and will overwrite your firmware. When going from CM to a different ROM, you don't have to flash the firmware again. As long as the android version is the same ofcourse.
Abiut your problem, do you use Superuser or SuperSU? Make sure you flash the latest SuperSU zip. More people had problems with the built in one from TWRP
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Yeah I had used the latest SuperSU. The problem persists even when I don't use SuperSU though. I feel like it is some sort of race condition as processes kick off during boot or something.
I wish I wasn't relying on voodoo to get the accelerometer/auto-rotate to work.
cg6ry79m

sseng587 said:
Fixed. I fastboot flashed the firmware partition.
take the files out the firmware.zip
and use the steps (8. How To Flash The Cyanogen OS Fastboot Images) from this link
edit: I found the steps! http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
*Only flash the files you extracted from the firmware zip
Click to expand...
Click to collapse
Yes! Thank you this worked. Was getting really annoyed by this issue, thought I was gonna be stuck on 5.02 forever. Tried flashing different nightlies, different modems...
Flashed everything from the 20150505 Firmware, the first 8 steps in the guide quoted above. For some reason flashing each file manually works as opposed to flashing the zip with all of them- odd, but hey whatever works...

Great thanks that worked!!
Sent from my A0001 using Tapatalk

I wanted to close out this issue as I believe it has been resolved. This problem was also a case of TWRP not correctly flashing the firmware. I "downgraded" from the X.X.0.7 TWRP to that X.X.0.6 version that others have posted links to in other threads. Frankly the GUI on this version is better.
So I downgraded TWRP, reflashed the 9 July Cyanogen nightly build. Accelerometer, compass, and proximity sensor working fine. Survived reboots. Survived new nightly.
Thanks to you folks who posted the issue about TWRP not flashing firmware correctly.
cg6ry79m

sseng587 said:
Fixed. I fastboot flashed the firmware partition.
take the files out the firmware.zip
and use the steps (8. How To Flash The Cyanogen OS Fastboot Images) from this link
edit: I found the steps! http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
*Only flash the files you extracted from the firmware zip
Click to expand...
Click to collapse
i have issue with gyroscope like this video:
https://www.youtube.com/watch?v=cXsB2LG1ftM
Thanks for this method but not working for me!
could you give me more detail working firmware
i try 8 step in fastboot mode with 20150515 and 20150518 firmware but the issue still here!

Which version of twrp do you use? And did you flash the latest su?
Sent from my A0001 using Tapatalk

davebugyi said:
Depends on the ROM you flashed. I usually flash the firmware separately and never had issues.
https://www.androidfilehost.com/?fid=23991606952604019
Flash this for CM12.1
Click to expand...
Click to collapse
sseng587 said:
Fixed. I fastboot flashed the firmware partition.
take the files out the firmware.zip
and use the steps (8. How To Flash The Cyanogen OS Fastboot Images) from this link
edit: I found the steps! http://forum.xda-developers.com/oneplus-one/general/guides-bacon-timmaaas-how-to-guides-t2839471
*Only flash the files you extracted from the firmware zip
Click to expand...
Click to collapse
Thaks guys it worked for me
Cheers!

Related

CM10 Stable Version OTA

Just got an OTA from CM that says a stable build (CM10.0.0) is ready to be installed. My phone is currently running the 1109 nightly.
Has anyone gotten this and successfully installed? I'm about to try it, but wonder if we still need to flash the boot.img first, or if the actual OTA takes care of that. Would be completely awesome if it does.
If you have the old hboot then you can just ota. If you have the new one, fastboot flash boot.img
Sent from my HOX running Cyanogenmod 10
I'm currently running the CM10 nightly from 10/11 and tried the OTA upgrade to the stable version. Well, once I flashed the new version my wifi wouldn't turn on.
It's the same problem I've had previously. My wifi works fine on the 10/11 nightly, but anything after that and my wifi just won't turn on. It shows that it's off in my settings and when I try to turn it on it just hangs and never turns on.
No one else seems to be having this problem so I'm not sure what's going on. I would love to upgrade to the stable build but I need wifi to work. I ended up having to reflash the older ROM and Gapps, so my wifi is working fine now.
Anyone else have problems turning wifi on with the new version??
Thanks. Installed with TWRP and everything is working great.
Just didn't realize that CM even pushed OTAs. A coworker also got an OTA on his GS3 today and installed that way with no problem. They don't have the extra boot.img step to deal with.
danny39 said:
If you have the old hboot then you can just ota. If you have the new one, fastboot flash boot.img
Sent from my HOX running Cyanogenmod 10
Click to expand...
Click to collapse
danny39 said:
If you have the old hboot then you can just ota. If you have the new one, fastboot flash boot.img
Sent from my HOX running Cyanogenmod 10
Click to expand...
Click to collapse
Does this mean I need to wipe like I did the first time I installed CM10 or is there a way to do this as an update without losing apps and settings?
Also, is there a way to do this directly on the phone or does it need to be done over USB like I did with the initial ROM install? Sorry, this is my first update since rooting recently. I'd like to make sure I do this correctly.
ctennenh said:
Does this mean I need to wipe like I did the first time I installed CM10 or is there a way to do this as an update without losing apps and settings?
Also, is there a way to do this directly on the phone or does it need to be done over USB like I did with the initial ROM install? Sorry, this is my first update since rooting recently. I'd like to make sure I do this correctly.
Click to expand...
Click to collapse
You shouldn't lose apps or settings, but never hurts to do a backup anyway.
If you rooted from the 2.20 firmware: download the rom from CM and extract the boot.img file on the computer. Then put the two on the phone's sd card. From there, you do the same thing you did the first time. Flash the boot.img and then the rom and GApps. Everything should work fine.
If you came from 1.85, apparently you can install directly from the OTA on the phone.
Thanks for the help. Do I need to do fastboot on boot img from the computer as well, or is there a way to manage it on the phone?
I wish I could just do OTA updates like people on the older hboot.
ctennenh said:
Thanks for the help. Do I need to do fastboot on boot img from the computer as well, or is there a way to manage it on the phone?
I wish I could just do OTA updates like people on the older hboot.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1982442
ctennenh said:
Thanks for the help. Do I need to do fastboot on boot img from the computer as well, or is there a way to manage it on the phone?
I wish I could just do OTA updates like people on the older hboot.
Click to expand...
Click to collapse
I use FlashImageGUI to flash the boot.img on the phone. Only thing I do on the computer is extract the actual boot.img file from the ROM.
joe23521 said:
I use FlashImageGUI to flash the boot.img on the phone. Only thing I do on the computer is extract the actual boot.img file from the ROM.
Click to expand...
Click to collapse
Ok, just so I have it straight and because Flash Image GUI is warning me over and over: after I extract the correct boot.img I flash it using the Flash Image GUI, then use TWRP to install the boot.img, then the rom zip, then my gapps.zip? Thanks.
I was able to install it without flashing the boot.img. I was coming from the the latest nightly.
Sent from my One X using xda app-developers app
ctennenh said:
Ok, just so I have it straight and because Flash Image GUI is warning me over and over: after I extract the correct boot.img I flash it using the Flash Image GUI, then use TWRP to install the boot.img, then the rom zip, then my gapps.zip? Thanks.
Click to expand...
Click to collapse
Flash the boot.img with Flash Image GUI, ignore all the warnings. Then, it'll ask you if you want to boot into recovery. Say yes. Then in TWRP, just flash the rom and gapps zips. Don't touch the boot.img again.
h1m said:
I was able to install it without flashing the boot.img. I was coming from the the latest nightly.
Sent from my One X using xda app-developers app
Click to expand...
Click to collapse
Interesting. Did you root from the 2.20 firmware?
No Stable for me
The CM10 Stable release for HTC One X is not on get.cm and it does not come up on my ota check on the CM10 nightly (i have the latest nightly)
Any ideas
Hello everyone,
This is the issue i had, when going from 1109 to stable the system will not do a clean OTA, the system will not load, attempted cleaning everything but nothing worked, at one point i even corrupted my memory so i had to do a factory reset, lastly what i did was flash the boot.img again and reinstall the system this got everything back to work. so from experience it seems the stable will need to do a full reinstall.
I hope that will help other people.
EDIT: updated to 1114 but it seems that broke the search feature so going back to 10.0.0 :S
ozozdil said:
The CM10 Stable release for HTC One X is not on get.cm and it does not come up on my ota check on the CM10 nightly (i have the latest nightly)
Any ideas
Click to expand...
Click to collapse
Definitely there. http://get.cm/get/4LO
Excellent. Thanks so much. I managed to get it done. Here are my steps, FYI:
Coming from the 2.20 root with the latest hboot.
I downloaded but did not install the 10.0 stable update.
I went through my file browser to sdcard/cmupdater and copied the 10.0 evita zip to my Downloads folder.
After extracting the zip I copied the boot.img to the root directory of my sdcard. I don't think it has to be there, though.
I ran Flash Image GUI on the boot.img file, even with all the warning.
I then chose to reboot into recovery, where I installed the 10.0 evita zip, then installed the gapps zip.
Everything seems to work, including WiFi. I really appreciate all the help here at XDA. Hopefully my process above will help someone else.
deleted
That link is for the One XL Evita lte dual core version, I'm talking about the One X international hspa quad core version.
Thaks for thehelp anyway
Sent from my HTC One X using xda premium
Hey Guys
I'm struggling to locate an OTA for my HOX, is it only the XL that was updated with a stable release? as im unable to locate an endeavoru stable release for CM10?
I've taken a look through get.cm but cannot locate a copy anywhere? did we miss out? ?

Flashing problems

OK guys let me tell you about my issue's
I'm using TWRP 2.7.1.0 (Tried 2.7.0.2 no difference) S-off, Unlocked, latest firmware from Santods files. The phone works fine with Sense ROMS but for the life of me I can't flash a GPE ROM. They fail every time. Santod tried to help me out the best he could by having me replace the Boot.img from the ROM I was flashing thinking that I was on a secure Boot image (And I may be but I replaced it and they still won't flash). Mr. Jaydee82 also modified a ROM for me to try out (although I'm not sure exactly what he did to it) and it wouldn't Flash properly either. When I try to flash these ROMs it will appear to flash properly and then they will go to the bootscreen and just sit there and churn. Depending on the ROM some will time out and power down the device and some will just sit there forever until I do a virtual battery pull. I'm freaking desperate to find out what is going on with this device and I don't feel right bugging Santod so I decided to post this in hope of more ideas about what could possibly be going on with my device. Any and all help greatly appreciated!!!
Thanks!
Duckman_UF said:
OK guys let me tell you about my issue's
I'm using TWRP 2.7.1.0 (Tried 2.7.0.2 no difference) S-off, Unlocked, latest firmware from Santods files. The phone works fine with Sense ROMS but for the life of me I can't flash a GPE ROM. They fail every time. Santod tried to help me out the best he could by having me replace the Boot.img from the ROM I was flashing thinking that I was on a secure Boot image (And I may be but I replaced it and they still won't flash). Mr. Jaydee82 also modified a ROM for me to try out (although I'm not sure exactly what he did to it) and it wouldn't Flash properly either. When I try to flash these ROMs it will appear to flash properly and then they will go to the bootscreen and just sit there and churn. Depending on the ROM some will time out and power down the device and some will just sit there forever until I do a virtual battery pull. I'm freaking desperate to find out what is going on with this device and I don't feel right bugging Santod so I decided to post this in hope of more ideas about what could possibly be going on with my device. Any and all help greatly appreciated!!!
Thanks!
Click to expand...
Click to collapse
What did you use to s-off; firewater or sunshine? Are you able to flash/boot AOSP roms? Did you take the 1.55.605.2 OTA before?
krazie1 said:
What did you use to s-off; firewater or sunshine? Are you able to flash/boot AOSP roms? Did you take the 1.55.605.2 OTA before?
Click to expand...
Click to collapse
I used Firewater I'm able to Flash all of the Sense ROM's not sure if they are considered AOSP. Give me an example of one and I'll try it. I'm not 100% sure if I took the OTA update before I Rooted and S-offed/unlocked the device but I think I did. I Flashed Santods Nobootimg firmware via ADB to be sure I was on the latest firmware. I know my radios were up to date before doing this but I wasn't sure about the FW so I flashed it. Flashed fine, didn't need to flush again, flashed fine first time.
Duckman_UF said:
I used Firewater I'm able to Flash all of the Sense ROM's not sure if they are considered AOSP. Give me an example of one and I'll try it. I'm not 100% sure if I took the OTA update before I Rooted and S-offed/unlocked the device but I think I did. I Flashed Santods Nobootimg firmware via ADB to be sure I was on the latest firmware. I know my radios were up to date before doing this but I wasn't sure about the FW so I flashed it. Flashed fine, didn't need to flush again, flashed fine first time.
Click to expand...
Click to collapse
I'll post a link to a aosp ROM but first can you link me to the firmware file you flashed?
krazie1 said:
I'll post a link to a aosp ROM but first can you link me to the firmware file you flashed?
Click to expand...
Click to collapse
4th one down and this was per Santod's instuction so I'm sure it's good.
http://www.androidfilehost.com/?w=files&flid=13966
Duckman_UF said:
4th one down and this was per Santod's instuction so I'm sure it's good.
http://www.androidfilehost.com/?w=files&flid=13966
Click to expand...
Click to collapse
Alright so you flashed it in bootloader right like this video?
http://youtu.be/e21qb7iZAOo
Here is a aosp ROM cm11 download the 20140801 build wipe and flash.
https://download.cyanogenmod.org/?device=m8
krazie1 said:
Alright so you flashed it in bootloader right like this video?
http://youtu.be/e21qb7iZAOo
Here is a aosp ROM cm11 download the 20140801 build wipe and flash.
https://download.cyanogenmod.org/?device=m8
Click to expand...
Click to collapse
Yes, ADB Fastboot Hboot...exactly as video instructed. No problems at all.
I'll give it a shot!
krazie1 said:
Alright so you flashed it in bootloader right like this video?
http://youtu.be/e21qb7iZAOo
Here is a aosp ROM cm11 download the 20140801 build wipe and flash.
https://download.cyanogenmod.org/?device=m8
Click to expand...
Click to collapse
Is a Gapps package needed for this ROM. Ive used Cyanogen ROM's before just not on this Phone.
Duckman_UF said:
Yes, ADB Fastboot Hboot...exactly as video instructed. No problems at all.
I'll give it a shot!
Click to expand...
Click to collapse
Forgot to link the GAPPs you need these for all AOSP roms, download and flash right after CM11
https://goo.im/gapps/gapps-kk-20140606-signed.zip/
krazie1 said:
Forgot to link the GAPPs you need these for all AOSP roms, download and flash right after CM11
https://goo.im/gapps/gapps-kk-20140606-signed.zip/
Click to expand...
Click to collapse
Thats what I thought..Thanks! About to dl Gapps and give it a shot.
krazie1 said:
Forgot to link the GAPPs you need these for all AOSP roms, download and flash right after CM11
https://goo.im/gapps/gapps-kk-20140606-signed.zip/
Click to expand...
Click to collapse
Yep flashed fine...no problems.
Duckman_UF said:
Yep flashed fine...no problems.
Click to expand...
Click to collapse
OK then, did you try both GPE ROMs for the vzw variant? Download the newest version of sinlessrom and wipe advanced (cache, dalvik cache, data & system) in TWRP.
http://www.androidfilehost.com/?fid=23578570567721616
krazie1 said:
OK then, did you try both GPE ROMs for the vzw variant? Download the newest version of sinlessrom and wipe advanced (cache, dalvik cache, data & system) in TWRP.
http://www.androidfilehost.com/?fid=23578570567721616
Click to expand...
Click to collapse
Already tried...Various Roms, various versions, 2 versions of TWRP (As stated) Aroma, non Aroma...They all just sit there and churn away on the boot screen or power down the device. I always wipe in that fashion
Man I'm out of ideas, I really want to help but can't think of anything. I'll still look and see if I can find anything.
krazie1 said:
Man I'm out of ideas, I really want to help bit can't think of anything. I'll still look and see if I can find anything.
Click to expand...
Click to collapse
I really appreciate your help. Santod and me went back and forth via PM a few times and JayDee modified his Rom for me and now you. IDK....I'm dumbfounded. If you think of anything let me know. I'll just stay on AOSP for now. Always liked Cyanogen's stuff anyway, just never even thought about them since their ROMS are not in the forums. They used to be for my various other phones. Never really though about them not being on XDA until we did this just now. Thanks again for you time and help!!!
Duckman_UF said:
I really appreciate your help. Santod and me went back and forth via PM a few times and JayDee modified his Rom for me and now you. IDK....I'm dumbfounded. If you think of anything let me know. I'll just stay on AOSP for now. Always liked Cyanogen's stuff anyway, just never even thought about them since their ROMS are not in the forums. They used to be for my various other phones. Never really though about them not being on XDA until we did this just now. Thanks again for you time and help!!!
Click to expand...
Click to collapse
Yeah cm11 is what I'm currently using, it recently had a speakerphone issue but its been fixed since 7/30. The only AOSP ROMs that have incorporated the fix are cm11, liquidsmooth & aokp. Here is the section for all the aosp ROMs they are universal so means 1 zip for all HTC One M8 variants.
http://forum.xda-developers.com/htc-one-m8/orig-development
Have you tried a RUU?
young0ne said:
Have you tried a RUU?
Click to expand...
Click to collapse
What do you mean? I put the phone in RUU when when flashing the firmware with ADB??
Duckman_UF said:
What do you mean? I put the phone in RUU when when flashing the firmware with ADB??
Click to expand...
Click to collapse
it put stock back on the phone just like it was new out of box. it re installs everything from factory.
Thanks!
GNU con Linux

Impossible to install TWRP 2.8.6.0

First of all sorry if there are some solution in other thread but i was searching a lot and found nothing. Also i cannot ask this on the twrp thread because of the xda system that don't allow me to write there or on some other development thread because my account have few than 10 messages (very frustrating this).
I tried to install the twrp 2.8.6.0 and it's impossible to have it working, when i install it always i have a bootloop that don't allow the phone to enter to the recovery.
I tried all the ways to install it (app flashify, app twrp manager, app kernel adiutor, cmd, toolkit, through twrp 2.8.7.0, 2.8.4.0, 2.8.7 multirom) and still without luck. It's very strange because is THAT specific version (2.8.6.0) that don't work, when i flash other version like 2.8.7 works perfectly.
Anyone knows what's the problem?
mustang_ssc said:
First of all sorry if there are some solution in other thread but i was searching a lot and found nothing. Also i cannot ask this on the twrp thread because of the xda system that don't allow me to write there or on some other development thread because my account have few than 10 messages (very frustrating this).
I tried to install the twrp 2.8.6.0 and it's impossible to have it working, when i install it always i have a bootloop that don't allow the phone to enter to the recovery.
I tried all the ways to install it (app flashify, app twrp manager, app kernel adiutor, cmd, toolkit, through twrp 2.8.7.0, 2.8.4.0, 2.8.7 multirom) and still without luck. It's very strange because is THAT specific version (2.8.6.0) that don't work, when i flash other version like 2.8.7 works perfectly.
Anyone knows what's the problem?
Click to expand...
Click to collapse
Install either TWRP 2.8.6.0.6 materialised (personally tested works perfect) or the latest 2.8.7.0.5 materialised other users say it works with flashing firmware and works with encrypted systems
https://www.androidfilehost.com/?w=files&flid=30332
Sent from my A0001 using Tapatalk
Renosh said:
Install either TWRP 2.8.6.0.6 materialised (personally tested works perfect) or the latest 2.8.7.0.5 materialised other users say it works with flashing firmware and works with encrypted systems
https://www.androidfilehost.com/?w=files&flid=30332
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
And do you know if works well with the new Sultan CM13 versions? That's the problem i have, the other TWRP versions cannot flash correctly that rom and also i heard that the TWRP 2.8.6.0.6 don't flash the rom correctly, maybe I'm wrong.
Me and many people have this strange problem that don't allow us to flash the 2.8.6.0. Hope someone can help us.
Thanks anyway.
mustang_ssc said:
And do you know if works well with the new Sultan CM13 versions? That's the problem i have, the other TWRP versions cannot flash correctly that rom and also i heard that the TWRP 2.8.6.0.6 don't flash the rom correctly, maybe I'm wrong.
Me and many people have this strange problem that don't allow us to flash the 2.8.6.0. Hope someone can help us.
Thanks anyway.
Click to expand...
Click to collapse
The problem isn't flashing the ROM correctly its that you don't have the correct firmware so it gives an error and refuses to flash the latest Sultan builds. TWRP 2.8.6.0.6 or 2.8.7.0.5 both in that directory I posted earlier can flash the correct firmware. You'll need to download the latest CM13 flash that wipe again and then flash Sultan to have the latest baseband version
Renosh said:
The problem isn't flashing the ROM correctly its that you don't have the correct firmware so it gives an error and refuses to flash the latest Sultan builds. TWRP 2.8.6.0.6 or 2.8.7.0.5 both in that directory I posted earlier can flash the correct firmware. You'll need to download the latest CM13 flash that wipe again and then flash Sultan to have the latest baseband version
Click to expand...
Click to collapse
I did that you told me and now i have the Sultan cm13 working perfectly.
I didn't know that, thanks.

Wilson3q CM12 to MIUI 7

Hello all,
I want to move from CM12 (Wilsons3q) to the latest MIUI 7 Global Stable. Im having a problem getting my phone recognized through the MiFlash program I originally used to get to CM12. I go into fastboot mode on the phone but the program does not recognize the phone. Ive tried this on 2 different computers. I installed the universal ADB drivers and still nothing. Does anyone know why the phone isnt recognized anymore?
I searched through the previous topics and found no answer to my question. Thanks guys
Solved.
Turns out all I had to do was flash the .zip from MIUI with TWRP recovery
It failed the first time so I did it a second time and it worked great.
Leaving this here for anyone else who may run into the same question/ problem
gotmicah said:
Solved.
Turns out all I had to do was flash the .zip from MIUI with TWRP recovery
It failed the first time so I did it a second time and it worked great.
Leaving this here for anyone else who may run into the same question/ problem
Click to expand...
Click to collapse
you flash the update zip through twrp recovery?
NO! Dont flash the update.zip
Download the global version from miui.
the name of what I flashed was "miui_MI4iGlobal_V7.1.1.0.LXIMICK_15c5da242c_5.0.zip"
gotmicah said:
NO! Dont flash the update.zip
Download the global version from miui.
the name of what I flashed was "miui_MI4iGlobal_V7.1.1.0.LXIMICK_15c5da242c_5.0.zip"
Click to expand...
Click to collapse
i download the miui latest version just rename it into update zip. because want to install in stock recovery. so, mean i can directly flash that zip?
fidows said:
i download the miui latest version just rename it into update zip. because want to install in stock recovery. so, mean i can directly flash that zip?
Click to expand...
Click to collapse
Oh I see. I didn't know you were using stock recovery. Im not sure completely, but im assuming that would be safe.
Edit: on second thought, maybe not. I dont have enough information about your situation, what ROM are you running now? im not sure how the stock recovery interacts with different ROMS
gotmicah said:
Oh I see. I didn't know you were using stock recovery. Im not sure completely, but im assuming that would be safe.
Edit: on second thought, maybe not. I dont have enough information about your situation, what ROM are you running now? im not sure how the stock recovery interacts with different ROMS
Click to expand...
Click to collapse
i mean this. im now in miui7. just to make sure if i flash cm13 then. can i flash the miui7 zip directly from twrp?

TWRP downgrade works but strangely.

Okay, many of us don't do this everyday but I flashed TWRP 3.0.2.0 on my OPO and needed to go back to 2.8.6.0 to use jgcaap's MM build.
So i tried flashing 2.8.6.0 img file from 3.0.2 and guess what happened? No. It didn't downgrade it self, instead I lost my recovery. My phone rebooted straight to system after being stuck on Bootlogo for a while. So I flash the recovery AGAIN via fastboot, flashify, RashR, Flashfire, Mobile Terminal whatever I could think of. But nope, same result whatsoever. Flashing other recoveries doesn't work either. Same errors return.
Then I thought of flashing 3.0.0.0 instead of 2.8.6.0 and yes, flashing 3.0.0.0 from 3.0.2.0 worked indeed. Then I started to download all the recovery files till 2.8.6.0 and started flashing them one after another, step by step climbing down the number and it kept downgrading but ONE version down at a time, if I try to skip it returns the same bs as before. Then flashing down until I reached 2.8.6.0 and then flashed that too via RashR. And surprise! Surorise! The recovery version I needed was not working. It would be flashed then the recovery would disappear and it would go into a no recovery state like before again. Then I'd flash 2.8.6.1 and get recovery back. And now finally after all the endeavor I'm on 2.8.6.1.
Anybody might know the reason of this stupid anomaly? And why it doesn't work?
And also why I can't flash ANY OTHER recovery?
Unnecessary screenshot attached :good: enjoy~
Tiash420 said:
Okay, many of us don't do this everyday but I flashed TWRP 3.0.2.0 on my OPO and needed to go back to 2.8.6.0 to use jgcaap's MM build.
So i tried flashing 2.8.6.0 img file from 3.0.2 and guess what happened? No. It didn't downgrade it self, instead I lost my recovery. My phone rebooted straight to system after being stuck on Bootlogo for a while. So I flash the recovery AGAIN via fastboot, flashify, RashR, Flashfire, Mobile Terminal whatever I could think of. But nope, same result whatsoever. Flashing other recoveries doesn't work either. Same errors return.
Then I thought of flashing 3.0.0.0 instead of 2.8.6.0 and yes, flashing 3.0.0.0 from 3.0.2.0 worked indeed. Then I started to download all the recovery files till 2.8.6.0 and started flashing them one after another, step by step climbing down the number and it kept downgrading but ONE version down at a time, if I try to skip it returns the same bs as before. Then flashing down until I reached 2.8.6.0 and then flashed that too via RashR. And surprise! Surorise! The recovery version I needed was not working. It would be flashed then the recovery would disappear and it would go into a no recovery state like before again. Then I'd flash 2.8.6.1 and get recovery back. And now finally after all the endeavor I'm on 2.8.6.1.
Anybody might know the reason of this stupid anomaly? And why it doesn't work?
And also why I can't flash ANY OTHER recovery?
Click to expand...
Click to collapse
Did you try flashing the recovery img via TWRP itself? And are you using any theme on TWRP 3.x.x.x?
Nope no themes and I tried flashing through every method I could think of but nope, doesn't work.
Tiash420 said:
Nope no themes and I tried flashing through every method I could think of but nope, doesn't work.
Click to expand...
Click to collapse
You don't need to be on TWRP 2.8.6.0 to flash jgcaap MM build. Just use 3.0.2.0 it flashes modem and does everything the older one you're trying to get to can do.
Sent from my A0001 using Tapatalk
Renosh said:
You don't need to be on TWRP 2.8.6.0 to flash jgcaap MM build. Just use 3.0.2.0 it flashes modem and does everything the older one you're trying to get to can do.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I get the notification quick settings bug, I mean, I can't get quick setting toggles directly from notification nor can I have a regular basic swipe lock screen. And the bugs persist no matter which ever recovery I'm flashing through and with or without Gapps. How do I get pass that? Meanwhile my friend on the other hand downloaded the same version from the same place and he doesn't face those bugs. :'| Why is this happening to me?
Tiash420 said:
I get the notification quick settings bug, I mean, I can't get quick settings directly from notification nor can I have a regular basic swipe lock screen. And the bugs persist no matter which ever recovery I'm flashing through and with or without Gapps. How do I get pass that?
Click to expand...
Click to collapse
I've been seeing mentions of flashing 21/4 build first set it up then dirty flash latest update. I also got the same issue when I last flashed jgcaap MM ROM. It would have been best to just ask for advise there than assume it's a recovery issue
Sent from my A0001 using Tapatalk
Renosh said:
I've been seeing mentions of flashing 21/4 build first set it up then dirty flash latest update. I also got the same issue when I last flashed jgcaap MM ROM. It would have been best to just ask for advise there than assume it's a recovery issue
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I'll thank my friends who owned the OPO before I did for the recovery 'assumptions' :|
Tiash420 said:
I'll thank my friends who owned the OPO before I did for the recovery 'assumptions' :|
Click to expand...
Click to collapse
I'm guessing they insisted because of the previous problems with flashing modems for TWRP. Flash the latest 3.0.2.0 and I guarantee it'll work for every ROM only issue that still exists is if you want encryption on CM13 and that's present on all current TWRP versions
Sent from my A0001 using Tapatalk
Renosh said:
I'm guessing they insisted because of the previous problems with flashing modems for TWRP. Flash the latest 3.0.2.0 and I guarantee it'll work for every ROM only issue that still exists is if you want encryption on CM13 and that's present on all current TWRP versions
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Well doesn't matter, I flashed Sultan's unofficial CM13 build via Kumajaya's TWRP 3.0.0.0 and it works fabulously! jgcaap can wait, I'm sure it's not much different in features and stuff! :3

Categories

Resources