Related
Am I just missing it, or is there no root or recovery ability for the 915A?
Marshmallow 6.0.1 ****ed mine up when it got pushed down, and Samsung's backup software (all 3 of them) failed to capture my apps and settings properly. Really wish I could've had a better backup ability.
Does or has anyone checked to see if the update to MM 6.0.1 has unlocked the bootloader on the SM-N915A like the Verizon variant?
How does one check?
Att have not released any M updates.
Mine updated to 6.0.1 the same day I bought it . Several small updates happened first. 5.0.1 to 5.1.1 then a small one, and finally 6.0.1. Since I had just bought it, resetting was a simple thought. But so far, no problems, I bought a PowerBear to make it last longer. :fingers-crossed:
Mine had a lot of issues after being updated. MMS didn't work at all. SMS worked sporadically, but would sometimes delete whole threads. Couldn't get a signal in many spots. Google Play Services wouldn't run and couldn't be fixed. Tried a cache-wipe and every other non-destructive method, but nothing worked. Ended up having to factory-reset, and since then the phone works as it should, but none of the backup methods captured key settings. Basically all it did was save contacts and APK's. Lost my 2-factor keys and everything.
I am with you! Since the update to MM, phone has been very laggy/unresponsive. Lock screen lights up for no reason sporadically and I have LOTS of dropped calls/deadspots. VERY irritating! I wish this release would have been tested a bit more before it was OTA pushed out
Hey all! Good news! A 9-year-old bug called the "Dirty Cow" exploit still exists in the Linux/Android kernel can easily grant root on any Android phone!!! See the video below.
http://www.xda-developers.com/9-yea...-dirty-cow-can-root-every-version-of-android/
So there's another bug to exploit for root and even possibly unlocking the bootloader! The bug has been fixed recently in Linux but hasn't been rolled into Android yet.
Could someone make this Windows compatible? http://androiding.how/dirty-cow-root-android/
JEANRIVERA said:
Hey all! Good news! A 9-year-old bug called the "Dirty Cow" exploit still exists in the Linux/Android kernel can easily grant root on any Android phone!!! See the video below.
http://www.xda-developers.com/9-yea...-dirty-cow-can-root-every-version-of-android/
So there's another bug to exploit for root and even possibly unlocking the bootloader! The bug has been fixed recently in Linux but hasn't been rolled into Android yet.
Click to expand...
Click to collapse
Have you tried or someone. I'm already installing Linux into my computer.
juanfe1a said:
Have you tried or someone. I'm already installing Linux into my computer.
Click to expand...
Click to collapse
did you end up doing it?
Who else could get the root on sm-n915a ??? I also have problems with the transition from 5.1.1 to 4.4.4. (Kitkat). If anyone can help write please how to do this ??
I would also like to know if I am from russia and I need a Russian language that is not available on samsung galaxy note edge n915a. Is it possible to add it like that ?? Sorry for my bad english (googl translate)). Thank you. I am hope for your help
pleasseee i need debrick image for at&t not egde (SM-N915A)
winstonakime said:
pleasseee i need debrick image for at&t not egde (SM-N915A)
Click to expand...
Click to collapse
https://forum.xda-developers.com/note-edge/general/stock-att-note-edge-5-1-1-t3241314
You may need to know your build number tho
Just to keep this alive it is now November 2017 any news?
Dr.Lost said:
Just to keep this alive it is now November 2017 any news?
Click to expand...
Click to collapse
I wish...
Anything new?
Need to rollback, or be advised of any custom ROMS that work..
Try Elite ROM from ROM section. it should work fine.
I personally would not recommend installing Elite ROM as it is more hassle than it is worth when you try to switch ROMs. It re/debrands your device and even after restoring a nandroid your audio will not work nor will your camera function properly. What files have bad keys? I put a lot of those up and the keys should work fine....
@shashank1320 check the links in the BLN-L24 section....something got messed up when you copied my links as mine work.
@ghostair is your device bricked? IMO none of the ROMs for this phone are worth installing on a main phone because there is too much functionality lost, no disrespect to the devs. Elite ROM does have the least amount of bugs but it is a hassle as I mentioned earlier. My main gripe about it is when installing and uninstalling apps you must restart the device in order for the apps to be added or removed from the app drawer....its a major annoyance.
BLN-L24C567B110 Thanks to @Dazed No More
boot - https://mega.nz/#!ceRkHQoA!L8MECn8Ul...8JwO7ZuVEEr8mk
recovery - https://mega.nz/#!sOZAUJTZ!QKKROoWkI...UPNDwL79ZI1yQI
BLN-L24C567B360 Thanks to @Dazed No More
boot - https://mega.nz/#!hDQB3RCT!YTH2j1IhJ...y_prJHEgHdSrxg
recovery - https://mega.nz/#!Fa4DBbxS!XDIczpXcr...TApUtNvcOMEDnc
TWRP 3.1.1 didn't work for me, nor did EliteROM or his version of TWRP.
ghostair said:
TWRP 3.1.1 didn't work for me, nor did EliteROM or his version of TWRP.
Click to expand...
Click to collapse
Is your device bricked? You say you want to rollback, but have you started the process....what firmware are you on?
Dazed No More said:
....
@shashank1320 check the links in the BLN-L24 section....something got messed up when you copied my links as mine work.
.
Click to expand...
Click to collapse
Let me check mate. Thanks for pointing that out.
No it's not bricked, actually I am on TWRP 3.1.1-0, it was only EliteROM's version that didn't work. I haven't even been able to use the phone at all, for a week, and am currently on LineageOS 13 as it was only release that works for my model it seems.
ghostair said:
No it's not bricked, actually I am on TWRP 3.1.1-0, it was only EliteROM's version that didn't work. I haven't even been able to use the phone at all, for a week, and am currently on LineageOS 13 as it was only release that works for my model it seems.
Click to expand...
Click to collapse
Im confused....your original post says you need to rollback but you say you are currently on LOS 13?? Rolling back refers to downgrading from Android 7.0 (Nougat) to 6.0.1 (MM) but you are already on MM if you are running LOS 13. You also say your device is not bricked but then in the next sentence say you havent been able to use it at all for a week.....and lastly you say LOS 13 was the only release to work for your model yet every single ROM in the development forum can be flashed to the BLN-L24, I know because I have done it.
What exactly are you trying to accomplish here? Your posts are contradictory and make no sense. Id be glad to help but you gotta give me something to work with here.
Im assuming you did not make a full backup in TWRP before flashing any ROMs, in which case you have learned a valuable lesson....always have a backup. But since you dont we will get you back to EMUI which I assume is what you mean when you say roll back.
Dazed No More said:
Im confused....your original post says you need to rollback but you say you are currently on LOS 13?? Rolling back refers to downgrading from Android 7.0 (Nougat) to 6.0.1 (MM) but you are already on MM if you are running LOS 13. You also say your device is not bricked but then in the next sentence say you havent been able to use it at all for a week.....and lastly you say LOS 13 was the only release to work for your model yet every single ROM in the development forum can be flashed to the BLN-L24, I know because I have done it.
What exactly are you trying to accomplish here? Your posts are contradictory and make no sense. Id be glad to help but you gotta give me something to work with here.
Click to expand...
Click to collapse
I understand, I probably should have just used, "go back," to EMUI. Since LOS 13 isn't usable in the least, as I can't make calls, and it drops LTE.
If they work then how? I followed everything, flashing vendor.img with fastboot, then flashing the respective zip?
I'd rather not go back to EMUI, it's why I haven't been able to actually "use it as a phone," since purchase.
Why would you not want to go back to EMUI? Its smooth and everything works. EMUI is the reason you havent been able to use it as a phone?? There is not one single ROM for this device that works entirely and has full functionality. You're always going to be missing something whether its the camera, LTE, calls, etc.
You're going to have to go back to EMUI so you can update to Anrdoid 7.0 (be sure to make a full backup) and then flash away all the ROMS you like and you will see they are all broken in some way. This is most definitely not the phone to use if you are looking for polished ROMs.
My last tip before departing......download the flashable vendor zip if you still want to mess around with the ROMs, it makes life much easier. Its in one of the threads in that forum I think AOKP
Hello everybody, I just received the OTA of Android 11 on my Note 10+ Snapdragon US version. Does anybody knows if its safe to install it? Cause I have a lot of information and is not an option to do a wipe data or hard reset after the installation. I have hex and other optimization apps but I can live without them if I find any issue.
Hope somebody already have installed this official update and share your opinions.
Thanks in advance.
juliospinoza said:
Hello everybody, I just received the OTA of Android 11 on my Note 10+ Snapdragon US version. Does anybody knows if its safe to install it? Cause I have a lot of information and is not an option to do a wipe data or hard reset after the installation. I have hex and other optimization apps but I can live without them if I find any issue.
Hope somebody already have installed this official update and share your opinions.
Thanks in advance.
Click to expand...
Click to collapse
Hey, I don't think it's safe to install at this time. I just updated my phone about an hour ago and am now stuck in a bootloop because of this update.
Unfortunately it's looking like I'll probably loose 6 months of data because of this unless there's a work around anyone knows about.
Looking for the safest ... least invasive way to either disable the **** ton of bloatware on this crappy N975U1, or advice on the best rooting routes that are available right now... Samsung was bad before... but I cannot deal with this crap that they loaded in with the android11 update! I'd read that Magisk hadn't even been effective on this last attack by these heathens...
Has anyone managed to get Android Auto to connect to their vehicle on their whyred?
I bought a new car last week and have been unable to get it to connect. Meanwhile my friends Blackberry KeyOne and iPhone both activated AA/Carplay immediately like they were supposed to.
I'm running Lineage 17.1 latest build, but I did see folks were having trouble with it a couple years ago. I was just hoping the situation had improved since then. I just updated the fw files from the Xiaomi firmware project and will try it again, but sadly I'm not hopeful.
If it does work for some of you, what rom are you using?
Thanks!
mik101 said:
Has anyone managed to get Android Auto to connect to their vehicle on their whyred?
I bought a new car last week and have been unable to get it to connect. Meanwhile my friends Blackberry KeyOne and iPhone both activated AA/Carplay immediately like they were supposed to.
I'm running Lineage 17.1 latest build, but I did see folks were having trouble with it a couple years ago. I was just hoping the situation had improved since then. I just updated the fw files from the Xiaomi firmware project and will try it again, but sadly I'm not hopeful.
If it does work for some of you, what rom are you using?
Thanks!
Click to expand...
Click to collapse
Problems with GAPPS I guess. Update both, car HUR and phone (gapps, Androidauto, play store,etc).
It's suppose to work normaly.. you can test it with MIUI ROM. You will need to delete LOS anyway if you wanna update FW the correct way (latest Fastboot MIUI ROM using PC).
Good luck and stay safe.
P.S.: I don't use gapps, to much troubles, and not privacy friendly and battery/data eater.
drnightshadow said:
Problems with GAPPS I guess. Update both, car HUR and phone (gapps, Androidauto, play store,etc).
It's suppose to work normaly.. you can test it with MIUI ROM. You will need to delete LOS anyway if you wanna update FW the correct way (latest Fastboot MIUI ROM using PC).
Good luck and stay safe.
P.S.: I don't use gapps, to much troubles, and not privacy friendly and battery/data eater.
Click to expand...
Click to collapse
What is the vendor security date of your device? (Unless its newer than Nov 1 2018 I'm already running the newest available vendor update and firmware.) The xiaomi firmware project updates the exact same files that the MIUI builds would.
Latest open gapps, android auto, etc are all installed. Headunit is updated to the latest version of Entune 3.0. The problem isn't the head unit. It's the phone. Old reports on here suggest it never worked with MIUI either. I was just curious if anyone has tried recently to see if the situation changed. I have zero desire to run that mess that is MIUI. It was bad enough using it long enough to get my bootloader unlock key. When you plug in the device you're presented with a menu on LOS that doesn't exist on other devices. (File Transfer, PTP, MIDI, Do Nothing). None of them do anything, so it appears that the MTP built into lineage doesn't know what to do with the connection.
mik101 said:
What is the vendor security date of your device? (Unless its newer than Nov 1 2018 I'm already running the newest available vendor update and firmware.) The xiaomi firmware project updates the exact same files that the MIUI builds would.
Latest open gapps, android auto, etc are all installed. Headunit is updated to the latest version of Entune 3.0. The problem isn't the head unit. It's the phone. Old reports on here suggest it never worked with MIUI either. I was just curious if anyone has tried recently to see if the situation changed. I have zero desire to run that mess that is MIUI. It was bad enough using it long enough to get my bootloader unlock key. When you plug in the device you're presented with a menu on LOS that doesn't exist on other devices. (File Transfer, PTP, MIDI, Do Nothing). None of them do anything, so it appears that the MTP built into lineage doesn't know what to do with the connection.
Click to expand...
Click to collapse
It's not LOS fault, it's car HUR or GAPPS(androidauto,..) fault.
Something is wrong in communication. I have 2nd device with LOS + GAPPS and all is working in my car HUR.
God luck and stay safe!
drnightshadow said:
It's not LOS fault, it's car HUR or GAPPS(androidauto,..) fault.
Something is wrong in communication. I have 2nd device with LOS + GAPPS and all is working in my car HUR.
God luck and stay safe!
Click to expand...
Click to collapse
You're leaving out a lot of necessary information, like your build of gapps and what your second device actually is. I have no doubt LOS works fine with Android auto on other devices, but I have yet to see any proof of it working on any whyred anywhere. You're just making assumptions and jumping to defend LOS without any proof whatsoever. You're ignoring the part where every post regarding AA on whyred posted on this forum in the past refers to it not working. It may not be LOS' fault in particular but it very well could be the device firmware never working with AA at all.
mik101 said:
You're leaving out a lot of necessary information, like your build of gapps and what your second device actually is. I have no doubt LOS works fine with Android auto on other devices, but I have yet to see any proof of it working on any whyred anywhere. You're just making assumptions and jumping to defend LOS without any proof whatsoever. You're ignoring the part where every post regarding AA on whyred posted on this forum in the past refers to it not working. It may not be LOS' fault in particular but it very well could be the device firmware never working with AA at all.
Click to expand...
Click to collapse
Ok ok I have 2 whyred devices(2nd has smashed screen, i leave it connected in car)...hope that makes sense now
Let me simplified this... whyred and android auto is working! Yeah you need to hasel a bit but its working, at least in my Nissan OEM HUR from 2019. You just need to find right GAPPS version. I think its from feb. 2020, anythig newer breaks androidauto. Than just freeze all google stuff or it will update and breaks again. I cant remember all details couse it's too long ago I did it. Sorry, but you'll need to experiment by yourself.
Ahh almost forget...my FW is 10.0.3 I think. Not the latest.
Good luck and stay safe.
It's a big gapps problem and not about the devices. I am on redmi note 4x and have the same problem. My whyred have too. All original devices work. And my mido work before too. Its all about gapps.
I am very much thankful for all developers here but please don't talk its fixed. Its not especially on android 11 builds. There is non fully working gapps out just betas talk work but not. I have many devices. I flash and hundreds of others cellphones.
For all people search. Help to develop or wait for a right gapps build and report to all.
Does anyone here recieved android 12 for oneplus 9 pro 5G LE2120?
Sheikhoo007 said:
Does anyone here recieved android 12 for oneplus 9 pro 5G LE2120?
Click to expand...
Click to collapse
Believe me, you won't want to. The update has been pulled. It still has so many bugs. Biggest problem for me, I was curious that it, and updated, A12 currently has no local update option. Means roll back is not possible, only with the MSM tool. Then it starts all over with rooting again.
Flying Fox said:
Believe me, you won't want to. The update has been pulled. It still has so many bugs. Biggest problem for me, I was curious that it, and updated, A12 currently has no local update option. Means roll back is not possible, only with the MSM tool. Then it starts all over with rooting again.
Click to expand...
Click to collapse
you can download and install this system update apk from oneplus and it gives you the options to rollback. But be aware rolling back will wipe your device.
https://www.getdroidtips.com/downgrade-oxygenos-12-to-11/
You can you the apk on ColorOS to rollback also.
Flying Fox said:
Believe me, you won't want to. The update has been pulled. It still has so many bugs. Biggest problem for me, I was curious that it, and updated, A12 currently has no local update option. Means roll back is not possible, only with the MSM tool. Then it starts all over with rooting again.
Click to expand...
Click to collapse
Which bugs are you facing?
Yup, and i've been using it for a month now.
I updated to A12 in Dec when the first OTA was pushed. I had too many issues even after the first 2 patches, downgraded back to OOS11 and never been happier.
I'm waiting for 10pro to launch so I can update to OOS12 then
Time of Awakening said:
Which bugs are you facing?
Click to expand...
Click to collapse
I played around so much, that I don´t remember everything now. Some apps didn´t work. I think, but I´m not sure, I had problems with Viper4Android. Or it was Youtube vanced. Sorry, I really forgot.
Certain setting options had been missing for me or were no longer where you would have expected them to be. I also missed the local upgrade, but that problem has been solved in the meantime (I was not well informed). I was also not happy with the UI, but that is not a bug but a matter of taste.
In sum, not so dramatic, but my evaluation has coincided with those of other forum members. Does not mean that I am right. I'm happy to be corrected.
How is the general satisfaction with A12 here?
A few months back when they started pushing Android 12 I was eager to try it and so I used "Oxygen Updater" from the play store to download a full stable version of android 12 but i accidentally downloaded the Indian version. I had so many bugs on it, but then I used the same app (oxygen updater) to switch to the EU version and my phone worked perfectly with no bugs or anything. I have now switched to Pixel Experience rom and wifi is not working so I may go back to Oxygen 12. But yeah if you have bugs on Oxygen 12 then use Oxygen Updater and download a new version to flash and your bugs may vanish.
Enjoy
I was curious about A12 and gave it a second try after cleaning up everything.
Does Viper4Android work? Just trying with a fix but not sure if it will work.
The next thing is that file manger doesn´t appear in Magisk, when u want to install a module from internal storage.
At least Youtube Vanced is working now.
BTW, post above is ColorOS 12
mrcrazy11 said:
you can download and install this system update apk from oneplus and it gives you the options to rollback. But be aware rolling back will wipe your device.
https://www.getdroidtips.com/downgrade-oxygenos-12-to-11/
You can you the apk on ColorOS to rollback also.
Click to expand...
Click to collapse
Another question: how to us the "OnePlus 9/9Pro Rollback APK". It´s a zip file. Unpacking shows now apk file. Flashing through kernel manager of course not possible. Sorry, don´t find a way to install.
Second try of A12 was not satisfying. When I use the MSM Tool I´ve to re-root again....
Edit: renamed the file to apk at the end. Did it once without success, don´t know why. Now it works
Hope you figured it out. If you haven't.
- download appropriate downgrade package and move it to the root folder of your phone.
- download and install https://oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk
on your devices... this allows you to access local upgrade... if your phone doesn't install a shortcut you can keep reinstalling it every time you need it
- open OPLocalUpdate_For_Android_12.apk click gear in top left corner and install the downgrade package you put in the root directory
You can also use the local update to install other OxygenOS12/ColorOS12 packages. I just went from C.36(Global) -> C.38(EU) -> C.46(ColorOS12) then rolled back because MMS is broken at C.44 all variants of both OSs and above... at least for me.
mrcrazy11 said:
Hope you figured it out. If you haven't.
- download appropriate downgrade package and move it to the root folder of your phone.
- download and install https://oxygenos.oneplus.net/OPLocalUpdate_For_Android12.apk
on your devices... this allows you to access local upgrade... if your phone doesn't install a shortcut you can keep reinstalling it every time you need it
- open OPLocalUpdate_For_Android_12.apk click gear in top left corner and install the downgrade package you put in the root directory
You can also use the local update to install other OxygenOS12/ColorOS12 packages. I just went from C.36(Global) -> C.38(EU) -> C.46(ColorOS12) then rolled back because MMS is broken at C.44 all variants of both OSs and above... at least for me.
Click to expand...
Click to collapse
Thanks, my problem was that I didn´t know that I have to rename the files. Many thanks!
Personally, I'm pretty satisfied with the C44 update for OxygenOS 12, stable and smooth, as intended. But yes, the first updates were messy.
For having given a try to ColorOS 12 too, OxygenOS 12 gave me a better experience on the OnePlus 9 Pro: less throttling in games and less bloated.
If we get a ColorsOS C44 EU (which should be far more debloated than its Chinese counterpart) that isn't making games throttle, then I'll surely jump into the wagon, but for now, OxygenOS 12 remains the better option if you want an Android 12 official experience for your phone.