Facebook 3.4 - Security Discussion

Hi everybody,
I've just heard of the problems affecting the new Facebook release (3.4, released e today July 4th) in relation to how it could spread our cantacts' info.
I am a Facebook beta tester, so today I was on facebook 3.4 beta, then I updated it to the release version 3.4.
Something strange happened: after finishing installing, phone automatically rebooted into recovery (I'm on the latest 4ext recovery), something occurred (I had no time to see nor to realise what was hapoening)... I guess something was flashed.. Then phone rebooted once more. Now Facebook works fine, even if most users are facing problems with this release: it doesn't start at all.
I wonder why it rebooted into recovery and why facebook it's working fine on my phone...
I just wanted to share this with you...
Here's my configuration:
Phone: HTC Desire S (s-on)
Rom: pure Cyano10.1 unofficial by blindndumb
Recovery: 4ext recovery touch 1.0.0.5 RC9
Thanks everybody guys
Sent from my Desire S using Tapatalk 4 Beta

Hmm I don't think it is possible for Facebook to do this.
To boot into recovery, this needs root access. As Facebook doesn't have root access, it should not be able to initiate the restart, or set it to flash anything automatically (also needs root)
You could check /cache/recovery/last_log and see what was flashed though.

pulser_g2 said:
Hmm I don't think it is possible for Facebook to do this.
To boot into recovery, this needs root access. As Facebook doesn't have root access, it should not be able to initiate the restart, or set it to flash anything automatically (also needs root)
You could check /cache/recovery/last_log and see what was flashed though.
Click to expand...
Click to collapse
And the plot thickens... DUN DUN DUNNNN!
(I tried inserting a YouTube video of a mouse in a dramatic situation, but alas, not enough posts yet.
But on a serious note. Yea, there's no way that Facebook would ask for root access. Then most of the general population wouldn't be using it! But just in case, since this is a beta version after all, check the app permissions?

electricbam said:
And the plot thickens... DUN DUN DUNNNN!
(I tried inserting a YouTube video of a mouse in a dramatic situation, but alas, not enough posts yet.
But on a serious note. Yea, there's no way that Facebook would ask for root access. Then most of the general population wouldn't be using it! But just in case, since this is a beta version after all, check the app permissions?
Click to expand...
Click to collapse
nice information

I am using Facebook 3.4 in a Samsung Galaxy 3 phone. When I received the new update my phone automatically rebooted itself and when it rebooted I now have a SD card error. And the Facebook app very randomly updates or connects. Looking into the permissions on the app they have changed... I am probably going to uninstall it till a new stable update has come out

Don't know if it helps, but I was on 3.4 (now 3.5) and saw no such issue.

I'm having some weird issues where facebook keeps changing who can/can't see my posts, randomly. Now my grandma has seen the last week of all my bull**** :silly:

HundenBuller said:
I'm having some weird issues where facebook keeps changing who can/can't see my posts, randomly. Now my grandma has seen the last week of all my bull**** :silly:
Click to expand...
Click to collapse
If you can reproduce this, give me a shout if you need a hand. You might be able to get a bug bounty from Facebook if you go through responsible disclosure, I am not sure if it covers the apps and issues like this.

Facebook has access to all of your contacts, browsing data, and now root access of your phone?
lol maybe time for me to go back to myspace...

MatthewJoe said:
Hi everybody,
I've just heard of the problems affecting the new Facebook release (3.4, released e today July 4th) in relation to how it could spread our cantacts' info.
I am a Facebook beta tester, so today I was on facebook 3.4 beta, then I updated it to the release version 3.4.
Something strange happened: after finishing installing, phone automatically rebooted into recovery (I'm on the latest 4ext recovery), something occurred (I had no time to see nor to realise what was hapoening)... I guess something was flashed.. Then phone rebooted once more. Now Facebook works fine, even if most users are facing problems with this release: it doesn't start at all.
I wonder why it rebooted into recovery and why facebook it's working fine on my phone...
I just wanted to share this with you...
Here's my configuration:
Phone: HTC Desire S (s-on)
Rom: pure Cyano10.1 unofficial by blindndumb
Recovery: 4ext recovery touch 1.0.0.5 RC9
Thanks everybody guys
Sent from my Desire S using Tapatalk 4 Beta
Click to expand...
Click to collapse
Unless you rooted your phone without any sort of control over which apps get superuser access, Facebook simply cannot not and would not boot into recovery.
Happy to help.

Have you guys ever heard of XPrivacy?

i didnt notice any issue updating it too. Not on my Rooted device, nor on my non-rooted tablet

nidpancho said:
Facebook has access to all of your contacts, browsing data, and now root access of your phone?
lol maybe time for me to go back to myspace...
Click to expand...
Click to collapse
Uh...Justin Timberlake bought MySpace.

Related

Htc One S Root SuperSU0.99 issue

Hi
Many people complained last days that they have problem with SuperSU 0.99 app.
They cant update the binary and phone reboots its self after "update failed" message
I got an HTC One S with S4 cpu last week and i got the new Jelly Bean Update 4.1.1
Then i unlocked my bootloader and installed TWRP custom recovery with One_S_All-In-One_Kit_v3.0 tool kit
After that i tryed to Root the phone with SuperSU 0.99.
Seems worked fine until i tryed to update my binary.
I get message "update failed" and my phone restarts.
I tryed to wipe and reflash the root but still same.
I even tryed to remove SUPERSU from System/App but with no luck. It keeps coming back even if i
removing it and revert everything to stock its still in SYSTEM.
Now i found this new Superuser version and flashed it and now my phone works fine and updating binary.
No more phone restart.
Even my SuperSU 0.99 is gone from system.
How TO:
Download superuser from this page http://androidsu.com/superuser/
Superuser-3.2-RC3-arm-signed.zip
Then boot into recovery
Flash Superuser-3.2-RC3-arm-signed.zip
Restart and voila the root works...
Hope i helped you guys.. Good Luck
Version 3.1.3 is reported to work better.
And doubt it really needed a new thread starting its discussed in most rom treads.
I started this thread just because of the issue SUPERSU 0.99 brings to HTC One S with Jelly Bean update.
I hope i can help someone because i didnt find any solution to my problem until i flashed superuser and it solved my problem.
shadowch31 said:
Version 3.1.3 is reported to work better.
And doubt it really needed a new thread starting its discussed in most rom treads.
Click to expand...
Click to collapse
I agree that this adds clutter, but I have been lightly following the threads for the JB ROMs and tried using superuser (though not the rc) without it working (still unable to update system). It's good to have this kind of solution in its own thread but general would probably be a better section.
Sent from my HTC One S Special Edition using xda app-developers app
This doesn't belong in the dev section for multiple reasons
Sent from my HTC VLE_U using xda app-developers app
Im sorry i didnt see that it was Development section. If someone can move it pls do so.
everyone uses SU...... this is very important for everyone using JB... leave it in here...
I feel it belongs here... this is where SU apps are in the development section... SO, this is where it should stay... (that is just my opinion)
I never want to start this thread like an development because im not a developer.
Reason is that i want to share my issue with anyone who is facing the same problem as i did.
Just like i said if someone think this thread doesn´t belong here then admins can move it to right section.
Updated to JB with OTA yesterday night.
Short version:
-Initially rooted with CWM recovery-> flashed MoDaCo stock recovery
-Apply OTA
-Flash CWM recovery
-Used CWM recovery to flash SuperSU 0.99 zip
-Uninstall/reinstall SuperSu from the Market
When starting SuperSU, it asks for update, if agree -> reboot.
BUT
When using root needing apps, like Titanium backup or FX file manager, they ask for root permission through SU and everything runs normally.
So SuperSU seems to work, only the front end app has some bug. I'm staying with that config waiting for an update.
Hi, same problem here on S3 cpu. Is this method works on S3 cpu as well? Thx for replying.
Hi. I think I have a problem with SuperSU (or something else??). I first started SuperSU last thursday (31.1.2013.). It ask me to update binary, I hit OK, and then it took about half hour to restart. System then recovered, and everything seem to be OK, but it's not!
When I connect my HTC One S to PC I only see files created (photos, videos) until 31.01.2013. Also, when I run Settings -> Memory com.android.settings crashes.
What to do?
I'm new to android. Plese help!
bihslk said:
Hi
Many people complained last days that they have problem with SuperSU 0.99 app.
They cant update the binary and phone reboots its self after "update failed" message
I got an HTC One S with S4 cpu last week and i got the new Jelly Bean Update 4.1.1
Then i unlocked my bootloader and installed TWRP custom recovery with One_S_All-In-One_Kit_v3.0 tool kit
After that i tryed to Root the phone with SuperSU 0.99.
Seems worked fine until i tryed to update my binary.
I get message "update failed" and my phone restarts.
I tryed to wipe and reflash the root but still same.
I even tryed to remove SUPERSU from System/App but with no luck. It keeps coming back even if i
removing it and revert everything to stock its still in SYSTEM.
Now i found this new Superuser version and flashed it and now my phone works fine and updating binary.
No more phone restart.
Even my SuperSU 0.99 is gone from system.
How TO:
Download superuser from this page http://androidsu.com/superuser/
Superuser-3.2-RC3-arm-signed.zip
Then boot into recovery
Flash Superuser-3.2-RC3-arm-signed.zip
Restart and voila the root works...
Hope i helped you guys.. Good Luck
Click to expand...
Click to collapse
I'm glad I ran across your thread. It helped me tremendously...
Da Baron
Any idea on how to get SuperSU work instead of SuperUser? I purchased SuperSU in the play store and I think it just looks better...

[Q] about CM11.0 [20140316]

Hello,
I've been reading this forum for quite some years and using some of the tutorials and ROMs from here but never actually posted anything and now that I have a few questions about on of the ROMs I'm using now I'm not quite sure where to post it since as a newly registered member I can't post anything in the correct ROM Thread [ http://forum.xda-developers.com/showthread.php?t=2467013 ], so please be patient with me.
I thought it would make more sense to post my actually questions than trying to reach those 10 posts to be able to post it directly there.
So now to my questions:
I have a HTC Desire S (obviously) and had for about 1 1/2 years now an old CoreDroid Version from here (can't remember which one) which I was quite happy with till it started to crash more and more often, battery kept draining and then there came a point a few weeks ago where it would just randomly go out and wouldn't restart till you charged it again.
That got me so annoyed I thought I either buy a new HTC Desire 310 soon or give another ROM a try, so I chose the cm-11-20140324-UNOFFICIAL-saga.zip from the first page and installed it after remembering how to do so.
Then the Gapps and started configuring it.
So far so good, ROM looks good, stable, battery is working much longer now, so thanks a lot.
But I had and still have some issues.
Whatsapp wouldn't instal, so through the search function I would a way around it (in the end downloading it from whatsapp directly and installing it through the .apk worked) and got that sorted.
The next thing is still a worry to me, I used to sync my contacts from my outlook through android-sync [ http://www.android-sync.com/ ] which I bought after non of the other syncing methods worked to my satisfaction. Everything worked fine with the old ROM (after I set it up) but with the new ROM the program on my computer can't find the mobile phone anymore, I tried to reinstall the ADB drivers, but it didn't work (I sent the error log from the program to the developer a few days ago but still haven't heard back), so maybe someone around here knows a way around it?
Last night I experienced another issue, the clock works fine and after I installed the ROM I set up a few different alarm clocks and they worked. But yesterday I wanted to change the alarms and now every time I try to access the alarm clock the clock app stops working "Clock stopped working" and it closes.
I can delete the alarms and set up a new one, but only the time, then it saves and when I try to change the days or the sound same error appears. I searched the forum and internet for a bit and found ideas like deleting the clock data and cache, rebooting the device, but none worked.
And last but not least it seems I can't find the right settings for it but every time I swype or type on the keyboard it vibrates. I turned off all the other noises that the phone made while typing but this one I can't find. I would like my phone to be silent and don't vibrate when I type. Where can I find the settings for it?
If anybody could help me with this I would appreciate it a lot.
Kind Regards
Marvin
For vibrating on keyboard press setting are at SETTINGS/Presonal/Languager and Input/Keyboard settings (for me it's ASOP keyboard settings).
Did you do dirty flash or clean one? Clean ROM flash is recommended.
Other problems I got with previous devil-kin CM11.Couldn't get usb mass storage and adb working.Now I keep Flinny CM11 build and it works.I didn't try devil-kin last build.
Maybe you can try install Flinny alpha 5 CM11 and try if that work.
SKENER said:
For vibrating on keyboard press setting are at SETTINGS/Presonal/Languager and Input/Keyboard settings (for me it's ASOP keyboard settings).
Did you do dirty flash or clean one? Clean ROM flash is recommended.
Other problems I got with previous devil-kin CM11.Couldn't get usb mass storage and adb working.Now I keep Flinny CM11 build and it works.I didn't try devil-kin last build.
Maybe you can try install Flinny alpha 5 CM11 and try if that work.
Click to expand...
Click to collapse
I installed Flinny alpha 5 CM11 now and tried it out. I had a few crashes with the devil-kin version too and bought a new battery, so hard to tell what solved what, but so far so good.
But for the syncing problem, now I have an even worse error:
ht*p :// i.gyazo.com/798a67697deb9f91904e7cac9b62bf76.png
with the devil-kin version it still found something and just had problems with the adb drivers, now there seems to be something else going on.
m4rvin88 said:
Hello,
That got me so annoyed I thought I either buy a new HTC Desire 310 soon or give another ROM a try, so I chose the cm-11-20140324-UNOFFICIAL-saga.zip from the first page and installed it after remembering how to do so.
Then the Gapps and started configuring it.
So far so good, ROM looks good, stable, battery is working much longer now, so thanks a lot.
But I had and still have some issues.
Whatsapp wouldn't instal, so through the search function I would a way around it (in the end downloading it from whatsapp directly and installing it through the .apk worked) and got that sorted.
Click to expand...
Click to collapse
Regarding that issue I also got problems with many other apps i.e. Redphone, Textsecure, Chiffry and so on there always comes the message that these apps are incompatible to my device - strange I also use cm11_saga_flinny_alpha5 Kernel 4.4.2.
These messages of incompatibility are generated by Google play store, when comparing AndroidManifest.XML permissions and requirements with the phone...
Further more Issues at Finny/Devilkin CM11.0
Hello guys,
I am also new at this Forum although using it "passiv" since years. Now I flashed the CM 11.0 from Devilkin and ones from Flinny.
- Unofficial CM10.2 / CM11.0 build for Saga / Desire S
All works (both ROMs) great up to the wired headphone Controles.
I think this might be the right thread to Post that until I reached the Number of Posts to put the in the right developerthread. Hope anyone can help.
The exactly problem:
I use orginal HTC-Headset with three controller Buttoms. The headphone itself is working though I can hear music and sound but the Controls and the Mic are not working. I tried to register an input with the jayzheadphone app but it shows no input. Headphone and controls worked fine with stock ROM.
Thank you for help.
@Terodax
Sorry but I cant't evaluate your issue cause of the missing HTC-Headset, but I got some other weird thing with the "mute" button on calling someboy it fails in doing it .-/
So I worked around the little problem in "holding" the call -> that works and it's like muting
htc wihc room to use
Hello
I bought this item.
http://www.ebay.com/itm/121361166744...84.m1423.l2649
Wich rom to android 4 or last?
How can I install those rom?
I need to using zip flashable file on recovery mod or addoin way?
will I need to flash the modem (phone) after?
has the recovery a nandroid backup option? I wanna backup the current rom like it is.
which is the best recovery for that item?
Thanks
---------- Post added at 10:45 PM ---------- Previous post was at 10:44 PM ----------
Hello
I need to use whatsapp and facebook mensseger on it.
thanks

[Android 5.1] Random reboots.

Good afternoon gents!
This is the first time I post on this forum so I apologize in advance if I am not going to provide all the details regarding my problem. I'll try to be as explicit I can with my issue.
A couple of weeks ago I bought a LG Nexus 5, second hand. After one day of use the device started to randomly reboot. The odd thing is that the reboots seem to be "soft". After the device restarts there is no data loss, even the recent apps are still there. The reboots are as random as I can get, when browsing with Chrome, checking emails, or playing a game.
I tried several fixes, including costum kernels, costum ROMs and so. The problem persisted with the official KitKat 4.4.4 and Lollipop 5.0, 5.0.1 and 5.1.
Currently I am running stock Lollipop 5.1 with stock kernel and TWRP 2.8.5.2 recovery and the device is rooted.
Below I attached a screenshot with the device's current configuration and a text file with the kmsg log from the last reboot.
Faulty power button.
Reboot phone into bootloader/fastboot.
If it random reboots in the bootloader too, it's likely the power button.
Nope, I already tested this. The device reboots during use, either heavy or simply browsing the menu.
Sent from my Nexus 5 using XDA Free mobile app
I noticed this in your Log
"<6>[ 0.514020] [email protected]: Power-off reason: Triggered from UVLO (Under Voltage Lock Out)"
Just curious, Are you undervolting?
I don't know exactly what undevolting implies. Could you give me more details please?
vektor1993 said:
I don't know exactly what undevolting implies. Could you give me more details please?
Click to expand...
Click to collapse
Lowering the voltage the CPU runs at, at certain frequencies.
I understand. No, I did no change any of the voltages. In that log that I posted up there the device is rooted and has TWRP 2.8.5.2 with stock lollipop 5.1 and stock kernel. Later yesterday evening i installed xtrasmooth rom with franco kernel and the phone only restarted in Here Maps from Nokia. I'll run more tests, but from this I draw the conclusion that it is a software problem, not a hardware one. Unfortunately I can't RMA the phone. Do you lads have any other opinions?
vektor1993 said:
I understand. No, I did no change any of the voltages. In that log that I posted up there the device is rooted and has TWRP 2.8.5.2 with stock lollipop 5.1 and stock kernel. Later yesterday evening i installed xtrasmooth rom with franco kernel and the phone only restarted in Here Maps from Nokia. I'll run more tests, but from this I draw the conclusion that it is a software problem, not a hardware one. Unfortunately I can't RMA the phone. Do you lads have any other opinions?
Click to expand...
Click to collapse
Try posting another log if it happens again.
I'm back with the latest ksmg log here. I searched for fixes all over the internet and nothing seemed to fix the problem. Restarts also occur in safe mode. Below is the latest last_kmsg.
vektor1993 said:
I'm back with the latest ksmg log here. I searched for fixes all over the internet and nothing seemed to fix the problem. Restarts also occur in safe mode. Below is the latest last_kmsg.
Click to expand...
Click to collapse
This log shows a kernel panic.
My n5 reboot today without any reason
That was the only thing I understood from the log too. Do you have any idea what's the reason for these kernel panics and a possible way to fix them?
I experienced today three more random reboots. I attached down the logs. As an unexperienced users point of view all of them are produced by a "Unable to handle kernel paging request at virtual address" . Could anyone throw a look on them and give me a possible reason for these reboots and a possible fix? Thank you in advance
vektor1993 said:
I experienced today three more random reboots. I attached down the logs. As an unexperienced users point of view all of them are produced by a "Unable to handle kernel paging request at virtual address" . Could anyone throw a look on them and give me a possible reason for these reboots and a possible fix? Thank you in advance
Click to expand...
Click to collapse
Same problem as this guy
http://forum.xda-developers.com/showpost.php?p=59551481&postcount=8615
having the same problem. i'm running 5.1, but dont know if it's caused by that, cause i just got this phone as a refurbished one from google.
Good day lads!
I tried since the last post more possible fixes, and the only thing that showed some resuslt was downgrading to 4.4 bu the device still resarts exactly once a day. I am going to switch to another phone.
having the same problem. i'm running 5.1, but dont know if it's caused by that, cause i just got this phone as a refurbished one from google.
Click to expand...
Click to collapse
If you just recieved a new device and you have the possibility to RMA it, I suggest doing it. I went as far as page 30 on google searching possbile fixes and came up with no valid result.

FreedomPop Motorola Photon Q 4G LTE xt897c, want help with Cyanogenmod

Hi xdadevelopers,
I ordered a Motorola Photon Q 4G LTE (xt897c) phone from FreedomPop for $25 and 28 days later it has arrived. My experience with FreedomPop has been decidedly mixed. Lots of hassle from customer service combined with a product that is sometimes very useful and always cheap. (Unless you use over 2GB of data per month) The phone itself seems very adequate for an excellent price. I would like your assistance in putting Cyanogenmod or another appropriate ROM on it.
Here's where I am,
The phone appears to have been rooted out of the box according to "Root Checker Basic" from Google Play
I installed "Superuser" from Google Play and that seems to work correctly
Busybox seems to be present already according to "Online Nandroid" from Google Play
I have created a TWRP Backup using Online Nandroid without modifying the recovery
The phone currently has Android 4.1.2
Where I want to be
I want to install a custom recovery, preferably one I can make backups from
I want to update to a more recent version of Android such as the stable one found here DUCK RULES cyanogenmod bot org /?device=xt897c or another version where everything just works
Notes. I have ADB and Fastboot installed from "Android Studio". I have an appropriate USB cable. I do not have a microsdhc card right now. It appears "Sandisk 64GB Extreme Micro SD (SDXC) Card + Adapter 60MB/s Class 10 U3 UHS-1" at DUCK RULES amazon bot com /gp/product/B00N98QLRQ is a good choice for a good price. I have this on order and should have it within the week.
I understand this phone has a locked bootloader. The "Messaging" app from FreedomPop available in Google Play seems to control messaging and the phone dialer. I went to the official Motorola Bootloader unlock page DUCK RULES motorola-global-portal bot custhelp bot com /cc/cas/sso/redirect/standalone%2Fbootloader%2Funlock-your-device-b I booted into recover with Power and volume up and volume down held, selected fastboot, connected to the computer , ran fastboot, as described, got the code, put the code in the webpage as described, and got a blank page. This happened 2x, with no emails form Motorola. I tried a third time 6 hours later, and it loaded a page with more instructions and I had the bootloader unlock code in my email instantly (There were no preceding messages, they didn't go to spam or somewhere else). I have installed TWRP Manager by Jmz software from Google Play. The standard reboot method doesn't work I changed the settings to "Reboot using an alternate method". I attempted to the TWRP recovery with the "Install TWRP". One must select their device and the closest thing to mine was "Motorola Photon 4G" codename "sunfire". This didn't appear to be it exactly but there wasn't a better choice. The next line down says "custom recovery not installed or detected". Then I selected the recovery version to install "2.6.3.0" "openrecovery-twrp-2.6.3.0-sunfire.img appeared the most recent, then I attempted to "Install Recovery" The phone downloaded the image, and said "Ensure the partition listed below is the correct one for your device..." "/dev/block/mmcblk0p10" how do I know if that's correct or not? I said yes to the question and went ahead, the phone rebooted to an Android on it's side with a yellow triangular sign with an exclamation point above it. Thirty seconds later the phone rebooted normally and everything worked no custom recovery was flashed.
Also thanks to the xdadevelopers community for your past and future efforts. I threw in my lot with Android when the neXus One launched after watching the keynote, buying it full price and paying extra for next day air shipping. I stayed stock despite the cool stuff being done by the development community until Google fell behind in updates. Then I started with CM6 and later went to CM7. That was wonderful software, thanks everyone who was involved in that. Unfortunately way late in the life of my phone I was homeless and got robbed for it. I got a used HTC HD7 Windows Phone for free from a friend. It was great for movies and music with a great screen and touch sensor but it was very early in the life of the new Windows Phone and there wasn't a lot of quality software being developed. That, and it just wasn't Android, and I longed for freedom. The integrated Web browser IE 9 variant sucked, and T-mobile denied me the final Windows Phone 7 update. The phone has gotten less and less useful as time went by though it always sucked for web browsing. This fall I got a One Plus One, it made a wonderful Wifi phablet, but when I tried to use it as a phone I found the radio was severely deficient in range, possibly due to defective manufacture as it got better range in colder weather. I had to initiate a chargeback with my credit card company to get support to talk to me and then ultimately get a refund. That's how I got where I am now and this is the first time I've needed to register for an account here. Thanks again xdadevelopers.
What is the best way to proceed? Semi detailed logical instructions please, as while I am intelligent and not a noob, I have been out of the game since CM7
Code:
.. ("`-''-/").___..--''"`-._
.. `6_ 6 ) `-. ( ).`-.__.`)
.. (_Y_.)' ._ ) `._ `. ``-..-'
.. _..`--'_..-_/ /--'_.' ,'
.. (il),-'' (li),' ((!.-'
Holy wall of text. This seems to be the crux:
Aslan_ said:
I have installed TWRP Manager by Jmz software from Google Play. The standard reboot method doesn't work I changed the settings to "Reboot using an alternate method". I attempted to the TWRP recovery with the "Install TWRP". One must select their device and the closest thing to mine was "Motorola Photon 4G" codename "sunfire". This didn't appear to be it exactly but there wasn't a better choice. The next line down says "custom recovery not installed or detected". Then I selected the recovery version to install "2.6.3.0" "openrecovery-twrp-2.6.3.0-sunfire.img appeared the most recent, then I attempted to "Install Recovery" The phone downloaded the image, and said "Ensure the partition listed below is the correct one for your device..." "/dev/block/mmcblk0p10" how do I know if that's correct or not? I said yes to the question and went ahead, the phone rebooted to an Android on it's side with a yellow triangular sign with an exclamation point above it. Thirty seconds later the phone rebooted normally and everything worked no custom recovery was flashed.
Click to expand...
Click to collapse
Why would you flash something that is OBVIOUSLY not for your device!? I sincerely hope it did nothing because you could do some permanent damage to your device by flashing stuff that's not made for it.
Did you bother looking for any recovery threads? Say my TWRP thread?
I recommend 2.7.1.2 in that thread, which is fine for CM11. If you want CM12, grab 2.8.5.0 in that thread.
Flash it per my directions using fastboot in my TWRP thread.
Got it thanks, now which rom?
Thank you very much arrrghhh. First off I sucessfully flashed TWRP 2.7.1.2. I did see the "[recovery] TWRP 2.7.1.2" thread, but it was from 2012 and it's 2015 now, plus it was 25 pages. Now I do see that the initial post was last edited 23rd July 2014, so that's better, but that's still over six months ago, so I'd have asked the question anyway having seen that. Several things to note, GooManager has been retired since the new cdn for goo.im was implemented, so that should be removed from the post. I like apps, they make me feel like there's less risk in my actions, though after some poking around I see it's probably the opposite. People are doing so much more low level stuff in apps compared to CM7 it's amazing.
arrrghhh said:
I recommend 2.7.1.2 in that thread, which is fine for CM11. If you want CM12, grab 2.8.5.0 in that thread.
Click to expand...
Click to collapse
It would be nice to see that info in the 2.7.1.2 thread. that the newer version is recommended for CM12 and where to get it, that would show you're on top of the latest changes not to mention make the thread even more useful. Perhaps include the reason for stopping at 2.7.1.2, the SELinux split. Seeing a new version that works always makes me want to get the newer version, but in this case there's a good reason not too.
I'm always hated vague it's broken posts that don't adequately describe the problem, the hardware used and the environment, so I head in the opposite direction with mine.
Next question is which rom should I choose? I want something stable and secure with everything or just about everything working. I like Cyanogen Mod, but I'm open to other things. As new as I can get, but stable. I thought I needed something from download bod cyanogenmod bot org /?device=xt897c , but now looking around it looks like I might be able to use other sources like download bot cyanogenmod bot org /?device=xt897 I'm not sure though. Again I have the Motorola Photon Q 4G LTE which is CDMA, from FreedomPop running on the Sprint Network.
Code:
.. ("`-''-/").___..--''"`-._
.. `6_ 6 ) `-. ( ).`-.__.`)
.. (_Y_.)' ._ ) `._ `. ``-..-'
.. _..`--'_..-_/ /--'_.' ,'
.. (il),-'' (li),' ((!.-'
Aslan_ said:
Thank you very much arrrghhh. First off I sucessfully flashed TWRP 2.7.1.2. I did see the "[recovery] TWRP 2.7.1.2" thread, but it was from 2012 and it's 2015 now, plus it was 25 pages. Now I do see that the initial post was last edited 23rd July 2014, so that's better, but that's still over six months ago, so I'd have asked the question anyway having seen that. Several things to note, GooManager has been retired since the new cdn for goo.im was implemented, so that should be removed from the post.
Click to expand...
Click to collapse
I no longer use this as my primary device, so my threads are basically stagnant. fastboot always works, where apps come and go... I'll try to find some time to adjust the post.
Aslan_ said:
It would be nice to see that info in the 2.7.1.2 thread. that the newer version is recommended for CM12 and where to get it, that would show you're on top of the latest changes not to mention make the thread even more useful. Perhaps include the reason for stopping at 2.7.1.2, the SELinux split. Seeing a new version that works always makes me want to get the newer version, but in this case there's a good reason not too.
Click to expand...
Click to collapse
Reason for stopping at 2.7.1.2 was they implemented MTP in 2.8.x, and I could never get it working right for both Win & Lin. I spose my bar was too high and I should've just released it, but I hate releasing half working stuff. It was a new feature that didn't work right.
Again, this is no longer my primary device so I'm not working on it very much at all. I have to pry the thing from my roommate's hands to even play with it, I haven't flashed CM12 yet (because it's no longer my device really).
I'd like to update the official TWRP, but in the meantime the CM maintainer has taken care of updating it so F2FS can be utilized.
Aslan_ said:
Next question is which rom should I choose? I want something stable and secure with everything or just about everything working. I like Cyanogen Mod, but I'm open to other things. As new as I can get, but stable. I thought I needed something from download bod cyanogenmod bot org /?device=xt897c , but now looking around it looks like I might be able to use other sources like download bot cyanogenmod bot org /?device=xt897 I'm not sure though. Again I have the Motorola Photon Q 4G LTE which is CDMA, from FreedomPop running on the Sprint Network.
Click to expand...
Click to collapse
Well obviously some of that does go down to choice - if you want CM, it is a little confusing. The device started out in CM10 as its own device, xt897 for GSM xt897c for CDMA. Then in CM11 they merged the devices into moto_msm8960. Of course they had to split again when the new bootloaders were released for the other moto_msm8960's (Razr HD, Atrix HD, etc) and moto_msm8960_jbbl was kind of a stopgap device at the end of CM11. Again, reading is your friend here although I realize all of that history is hard to glean. At least read the OP of the CM thread:
kabaldan said:
Please note:
In CM12, the Motorola 2012 msm8960 device line has been de-unified again, so moto_msm8960/moto_msm8960_jbbl builds are dead from now on.
Please check the xt897 device link for new Photon Q builds.
Click to expand...
Click to collapse
Good luck. The device is now semi-unified (GSM & CDMA), as xt897.
Aslan_ said:
[*]I have created a TWRP Backup using Online Nandroid without modifying the recovery
Click to expand...
Click to collapse
Would you mind terribly to share this? My device shipped with a Sprint branded ROM and I'd like a proper backup.
I flashed CM 12.1 and lost data (3g/LTE) connection
I tried to flash FreedomPOP APN fix but it did not help
Anyone knows how to fix this?
How do I update PRL/Profile on CM 12.1?
turbozapekanka said:
I flashed CM 12.1 and lost data (3g/LTE) connection
I tried to flash FreedomPOP APN fix but it did not help
Anyone knows how to fix this?
How do I update PRL/Profile on CM 12.1?
Click to expand...
Click to collapse
You don't update PRL/Profile in CM, you do that on the stock ROM. Make sure EVERYTHING works on stock before flashing CM.
I found another APN fix and it worked.
So the result of the update PRL/Profile is stored somewhere in the phone and does not get lost when I flash a new ROM, is that correct?
The only way to update PRL/Profile is to flash back to stock, do update, reflash back to custom, right?
turbozapekanka said:
I found another APN fix and it worked.
So the result of the update PRL/Profile is stored somewhere in the phone and does not get lost when I flash a new ROM, is that correct?
The only way to update PRL/Profile is to flash back to stock, do update, reflash back to custom, right?
Click to expand...
Click to collapse
Correct.
turbozapekanka said:
I found another APN fix and it worked.
So the result of the update PRL/Profile is stored somewhere in the phone and does not get lost when I flash a new ROM, is that correct?
The only way to update PRL/Profile is to flash back to stock, do update, reflash back to custom, right?
Click to expand...
Click to collapse
Can you share this "another APN fix"?
already shared here http://forum.xda-developers.com/showpost.php?p=60153295&postcount=18
Anyone still have issues? I was running a June Nightly and it was working somewhat. It would randomly lose connection and I would have to flash the APN.zip. It happened again a few days ago and I decided to go up to 722 Nightly and now I haven't been able to connect. When I go to APNs the list is empty and even if I manually add one it does not seem to stick. The APN zip doesn't help either. The phone is connected but shows an exclamation mark next to the signal and I have no data.
Sort of solved my own problem
Flashed back to stock Spring using RSD lite and a modified XML that didn't flash the system.img since it kept giving me errors. Found a stock TWRP dump on the forums and flashed that. Updated PRL and Profile, reflahsed back to CM11 Snapshot and flashed the 2015 FreedomPOP APN fix. Working for 1 day now.

stable android 11 released for op7p

why is no one discussing stable android 11 for op7p ? got my update round 3 a.m. this morning. been searching all day for a working twrp since the stable android 11 been released. no luck though......
Hi,
Today I installed the update manually and my phone keeps flashing the TWRP load-screen at boot. It's stuck now. Is that because there is no compatible TWRP version yet? How do I fix this?? Any idea?
There is no working TWRP yet for Android 11. You'll need to flash the stock boot.img or rooted boot.img from one of the threads in the news, guides section.
Edit: TWRP screen flashing is because it's incompatible. I had the same issue on the open betas.
Have the exact same issue as above, Twrp screen flashing, cannot boot back to normal even with adb... anybody has a rooted boot.img link that knows works with Android 11?
Should have checked on xda first *slaps his face*
Always check xda first *slaps his face again*
EDIT: For other poor saps with this issue use this -> https://www.androidfilehost.com/?fid=2188818919693770594 I didnt managed to get booted with rooted img but the original boot img file worked well ... at least I got a phone now...
im on 10.3.8 and rooted..
can i just do the same old process.. twrp isnt an issue as long as may apps are safe and root..
santiagoruel13 said:
im on 10.3.8 and rooted..
can i just do the same old process.. twrp isnt an issue as long as may apps are safe and root..
Click to expand...
Click to collapse
No, its not the same process.... For me for example I couldnt get wifi to actually work on rooted image AND you lose the ability to do backups via TWRP..... Refer here for the latest on this: https://forum.xda-developers.com/t/...p-recovery-for-oneplus-7-pro.3931322/page-153
dejjem said:
No, its not the same process.... For me for example I couldnt get wifi to actually work on rooted image AND you lose the ability to do backups via TWRP..... Refer here for the latest on this: https://forum.xda-developers.com/t/...p-recovery-for-oneplus-7-pro.3931322/page-153
Click to expand...
Click to collapse
I mean.. same steps.. that ive used so far amd retain its root.
1. Download rom via o2 updater
2. Flash it via local update
3. Install magisk to inactive slot
4. Reboot.
So if i do this.. wifi wont work??? Is that it???
Finished updating my phone..after downloading it for about 2 hours.
And im quite satisfied with the results. No problems whatsoever..
Glad for you... You probably had already removed the encryption on your mobile... from what I'm reading that is the main incompatibility issue with TWRP...
FWIW after playing around for a day, I had to revert everything Phone wifi was weird (weirder with root and all mods disabled) and system was a little unstable in some 3p apps and there seems to be some bugs with the phone screen 60/90 refresh... Gonna wait a bit to update again.
dejjem said:
Glad for you... You probably had already removed the encryption on your mobile... from what I'm reading that is the main incompatibility issue with TWRP...
FWIW after playing around for a day, I had to revert everything Phone wifi was weird (weirder with root and all mods disabled) and system was a little unstable in some 3p apps and there seems to be some bugs with the phone screen 60/90 refresh... Gonna wait a bit to update again.
Click to expand...
Click to collapse
i dont mind not having TWRP for the meantime,, i just used TWRP previously for flashing CUSTOM kernels.. hehehehe.
anyways, what problem have you encountered regarding wifi?? i dont seem to experience those,, maybe because i came from stable oos 10.3.8..
what app crashed and problems have you encountered???

Categories

Resources