I recently had my Orange Galaxy S2 i9100P unlocked by the local phone shop.
The unlocking worked fine, but I have now noticed that it has been rooted too.
It has a superuser app installed, which he said he didn't realise it had installed.
Not sure that I want it to be rooted when I sell it as it might put off potential buyers.
So I called the shop and asked if it has to be rooted to unlock it and he said that it does.
He said that the other way to unlocked it is to use a code but that system is currently down (the website that gives out codes) and it would cost £26 instead of the £10 that I paid to have it unlocked using root. I asked him if I could unroot it by flashing with the standard Orange firmware (using Keis) and he said yes I could and that would unroot it. When asked that if this would then lock it again he said that no it shouldn't, but he didn't seem too sure about what he was saying.
So some specific questions:-
1) Did he have to root it to unlock it?
2) Did it have to be left in root once unlocked?
3) Can I unroot it and return to standard firmware (using Keis) and it still remain unlocked?
4) If the answer to 3) is no, then can I delete / uninstall the superuser app?
5) When I run the superuser app, there is a temp unroot option. What does that do? Can I use that to unroot it?
MrModbus said:
1) Did he have to root it to unlock it?
2) Did it have to be left in root once unlocked?
3) Can I unroot it and return to standard firmware (using Keis) and it still remain unlocked?
4) If the answer to 3) is no, then can I delete / uninstall the superuser app?
5) When I run the superuser app, there is a temp unroot option. What does that do? Can I use that to unroot it?
Click to expand...
Click to collapse
1. Yes root was required to unlock from the carrier. Or else you had to pay full price to get the unlock.
2. Not exactly! If he made a permanent change then no need, But if he's using something dependent to unlock it then it needs to be rooted.
3. Not sure, cause if the stock Orange firmware finds the phone as locked it might re-lock it again. So there's a risk. If you can find a fresh carrier free firmware for your model why not flash that?
4. I used SuperSU there's an unroot button there but nothing that says 'Temporary'. But if the root binaries are once flashed I'm not sure that gets rid of it.
Just trying to be helpful.
Tiash420 said:
1. Yes root was required to unlock from the carrier. Or else you had to pay full price to get the unlock.
Click to expand...
Click to collapse
Ah OK.
Tiash420 said:
2. Not exactly! If he made a permanent change then no need, But if he's using something dependent to unlock it then it needs to be rooted.
Click to expand...
Click to collapse
How do you mean? Are you saying that there is another appliocation that is running that is performing the unlock and that needs root to do its stuff?
Tiash420 said:
3. Not sure, cause if the stock Orange firmware finds the phone as locked it might re-lock it again. So there's a risk. If you can find a fresh carrier free firmware for your model why not flash that?
Click to expand...
Click to collapse
That is an option. But Last time I looked (a few years back) I couldn't find any i9100P specific unbranded firmware. There was i9100 firmware, but that didn't support the i9100P NFC chip.
Tiash420 said:
4. I used SuperSU there's an unroot button there but nothing that says 'Temporary'. But if the root binaries are once flashed I'm not sure that gets rid of it.
Click to expand...
Click to collapse
My app is just called "superuser" and is at v3.1.3. I suppse that I could try the temp unroot and see what happens.
Yes, I'm saying there might be some app keeping the unlock alive. Cause that's how I unlocked my iPhone 4, quite a lot of times. :3
And you should search again for unofficial rom.
And also try the temporary unroot button.
Rightho, I have now moved over to the S5 and I would like to get my S2 ready for sale.
Someone mentioned earlier that Keis might not recognise the device. Well you are correct it doesn't and will not let my flash. I does not recognise it as a Samsung device.
So I would like some generic I9100P firmware that supports NFC.
I would also like to unroot the device.
Current firmware is V4.1.2
Baseband version is I9100PBVLS2
Kernel is 3.0.31 - 1246097
[email protected] - 109 #3
SMP PREEMPT Tue Jun 4 15:49:20 KST 2013
Build number is JZO54K.I9100PXXLSS
I do not get a yellow warning triangle so I assume that it is a secure kernel.
So can anyone help me to:-
1) Unroot the device.
2) Get it so that Keis will talk to it again.
3) Keep it unlocked
4) Get a secure kernel if mine is insecure.
MrModbus said:
Rightho, I have now moved over to the S5 and I would like to get my S2 ready for sale.
Someone mentioned earlier that Keis might not recognise the device. Well you are correct it doesn't and will not let my flash. I does not recognise it as a Samsung device.
So I would like some generic I9100P firmware that supports NFC.
I would also like to unroot the device.
Current firmware is V4.1.2
Baseband version is I9100PBVLS2
Kernel is 3.0.31 - 1246097
[email protected] - 109 #3
SMP PREEMPT Tue Jun 4 15:49:20 KST 2013
Build number is JZO54K.I9100PXXLSS
I do not get a yellow warning triangle so I assume that it is a secure kernel.
So can anyone help me to:-
1) Unroot the device.
2) Get it so that Keis will talk to it again.
3) Keep it unlocked
4) Get a secure kernel if mine is insecure.
Click to expand...
Click to collapse
Flash a custom recovery through Odin and then backup your current Rom. And then find flashable-zip official firmwares and then flash and see results. If anything goes wrong revert back to the old firmware.
The solution seems to be to download and install firmware XXLSU Android 4.1.2 Jelly Bean.
This will install a generic unlocked stock ROM and generic firmware, which is just what I need.
See here.
w w w.ibtimes.co.uk/galaxys2-i9100p-xxlsu-android412-jellybean-update-install-501998
However, I am not able to find the update ROM / Firmware files as all the links in all the websites that I have found are all dead.
I have founf some working links but this is for Spanish / French versions. Will these be OK?
MrModbus said:
The solution seems to be to download and install firmware XXLSU Android 4.1.2 Jelly Bean.
This will install a generic unlocked stock ROM and generic firmware, which is just what I need.
See here.
w w w.ibtimes.co.uk/galaxys2-i9100p-xxlsu-android412-jellybean-update-install-501998
However, I am not able to find the update ROM / Firmware files as all the links in all the websites that I have found are all dead.
I have founf some working links but this is for Spanish / French versions. Will these be OK?
Click to expand...
Click to collapse
Keep in mind to use the firmware with the right "MODEM" version. SamMobile offers the firmware version(s) you are looking for. BUT don't risk flashing another firmware, if its much more easy. Install "SuperSU" from the play store. Open it an switch ROOT to "SuperSU", you will be prompted to uninstall the current superuser (root). Accept it. Reboot your phone. Open SuperSU and perform "Complete Unroot". Thats it
Ok that will unroot it but stay with orange firmware and be re-locked to orange?
I was wanting a generic ROM and firmware that supports NFC.
SamMobile has the I9100PXXLSU firmware which I believe I need. However, it has 2 versions:-
Date Country/Carrier Version PDA CSC MODEM
2013 August France 4.1.2 I9100PXXLSU I9100PXEFLS3 I9100PXXLS8
2013 August Spain (Vodafone) 4.1.2 I9100PXXLSU I9100PATLLS6 I9100PBULS3
Should I be concerned about the carrier / country?
You say get the correct MODEM version but how do I know what the correct one is?
My current details are:-
PDA: I9100PXXLSS
PHONE: I9100PBVLS2
CSC: I9100PPORALS6
Please can someone just tell me where I can get a generic ROM / firmware and tell me which one I should be using.
It all seems to be riddles and cryptic clues.
I am confident of downloading the ROM / firmware using ODIN, but I just want to know what to download.
MrModbus said:
Ok that will unroot it but stay with orange firmware and be re-locked to orange?
I was wanting a generic ROM and firmware that supports NFC.
SamMobile has the I9100PXXLSU firmware which I believe I need. However, it has 2 versions:-
Date Country/Carrier Version PDA CSC MODEM
2013 August France 4.1.2 I9100PXXLSU I9100PXEFLS3 I9100PXXLS8
2013 August Spain (Vodafone) 4.1.2 I9100PXXLSU I9100PATLLS6 I9100PBULS3
Should I be concerned about the carrier / country?
You say get the correct MODEM version but how do I know what the correct one is?
Please can someone just tell me where I can get a generic ROM / firmware and tell me which one I should be using.
It all seems to be riddles and cryptic clues.
I am confident of downloading the ROM / firmware using ODIN, but I just want to know what to download.
Click to expand...
Click to collapse
Vodafone firmware is Vodafone branded, so i won't use it as its probably highly customized by vodafone. The France version should not have a branding. You can check your modem version in Android: "Settings-->about Phone". If you get you right, you want to sell a branded phone as unbranded and potentially next owner may not know. sounds not very good
I was just trying to get rid of all the ornage bloatware. If someone wants to use a different network operator, they might not want all the orange stuff on there. I was certainly not wanting to trick anyone. I suppose I could just unroot it and leave it as it is (it is obviously an orange branded phone as it has orange logos on it). Or I could just download the standard orange ROM / Firmware and return it to stock. My worry is that this will lock it again. I keep asking this question but no one seems to give me a straight answer if it will or not. Maybe it is an unknown. As I am a newby I have no idea.
MrModbus said:
I was just trying to get rid of all the ornage bloatware. If someone wants to use a different network operator, they might not want all the orange stuff on there. I was certainly not wanting to trick anyone. I suppose I could just unroot it and leave it as it is (it is obviously an orange branded phone as it has orange logos on it). Or I could just download the standard orange ROM / Firmware and return it to stock. My worry is that this will lock it again. I keep asking this question but no one seems to give me a straight answer if it will or not. Maybe it is an unknown. As I am a newby I have no idea.
Click to expand...
Click to collapse
I suppose its hard to say, because no one but the shop owner exactly knows what method was used to unlock the phone. Thats the reason why there is no guarantee that the unlock survives a firmware flash. If you just want to get rid of unwanted apps, you can use "Titanium Backup" to uninstall whatever you want. I would never use a non rooted phone again, so may be the new owner is happy that its already rooted
LS.xD said:
Keep in mind to use the firmware with the right "MODEM" version. SamMobile offers the firmware version(s) you are looking for. BUT don't risk flashing another firmware, if its much more easy. Install "SuperSU" from the play store. Open it an switch ROOT to "SuperSU", you will be prompted to uninstall the current superuser (root). Accept it. Reboot your phone. Open SuperSU and perform "Complete Unroot". Thats it
Click to expand...
Click to collapse
Yeah this works, if you really wanna get rid off the orange BS. Just uninstall all the BS with Titanium Backup and then simply unroot. :3 And the device fresh and unlocked and not rooted without the BS. :3 And everybody's happy, right?
Related
Hi all
A week ago a rooted my Samsung Galaxy S6 device following this post: http://forum.xda-developers.com/galaxy-s6/general/root-pingpongroot-s6-root-tool-t3103016
All was OK. At that point my device is using the Android Version: 5.0.2
The question I have is that now the version 5.1.1 (Lillipop) has been released, I would like to know if my rooted device can still be upgrading when the new version is released in my region (Mexico) by the phone provider. (Telcel). In case it cannot be updated automatically, I guess I will need to do it manually or unroot my device. In that scenario, Does someone know a good tutorial how to do that?
Regards!
@LesthadMK, sure you can update rooted devices. But it may not be possible via OTA update. You will have to download the full firmware and install it manually.
Because root makes changes to system partition, OTA fails when you have rooted. If you unroot and flash stock recovery and kernel back, then OTA may work. Otherwise, simply flash the full firmware, in .tar format using Odin software, and you're good.
It's good to have full firmware saved on PC anyway, as if in case you brick your device, you can fix it by installing your device's firmware manually.
If you need help with 5.1.1 firmware installation on your s6, let me know the build no. of your device.. I will guide you to page you need to look at.
Thanks for the help. I have download Odin in case I need to do it manually.
Also, mentioned that yesterday I read an article saying that using the Samsung software "Smart Switch" in an rooted device will upgrade the device to the newest version (which I don't know if it it's true or not) Any way this is the link I found:.... Well seems since I'm newby I cannot post some external links. So just google it as: How to Use Smart Switch to Update Your Galaxy S6—Even It's Rooted.
By other hand, this is the build number for my device: G920IDVU1AOE3, so if you can help me to know how to upgrade that version that would be very helpful
Regards!
(From later on in this thread)
Jaxas said:
Hello again, sorry to bother you guys but I'm seeing a surprising amount of conflicting information about this...
So I'm trying to upgrade to Nougat, but I'm having some troubles figuring out what I need to do for that.
I know I need to get my phone back to stock so I can accept the OTA update, but I'm not sure how to go about that.
My phone currently:
- Phone Model: HTC One A9 (Sprint - 2PQ93)
- Android Version: 6.0.1
- Software Version: 1.60.651.4
- Root: Yes
- Recovery: TWRP v2.8.8.2_CPTB-TEST2
- S: ON
- Bootloader: Unlocked
- Software Status: Modified
So as far as I'm aware, I need to restore the Stock recovery (how?), re-flash the RUU for my current software version, and then... relock the bootloader? Maybe?
So my questions are...
- How do I actually restore the stock recovery?
- Are there any steps I'm missing?
- Do I need to re-lock the bootloader, or does that not matter?
(- Is there anything I need to do once I get Nougat to root besides flash TWRP 3.0.3 & SuperSU through that?)
Thanks!
Click to expand...
Click to collapse
=============== ORIGINAL POST ===============
Hello,
I'm basically at my wit's end and I'd just like to see if anyone knows whether it's actually possible to get Android 7.0 Nougat on my phone?
I currently have a rooted, RUU-updated 6.0.1 build of Android (Version Number: 1.60.651.4) running on a Sprint (so CDMA) HTC One A9 (Model Number: 2PQ9300). My phone is still S-On (I'm willing to pay for Sunshine if it'll actually work for me, but I'd like to confirm that first), and due to the updating process I do not currently have TWRP - that's easily fixed, however.
Mostly, I'd just like to know if there's a way to get Android 7.0 on my phone, as it is not the International version, while also retaining things like mobile data and calling.
So far, I've looked into simply flashing the RUU (seems to be both not compatible with my phone version, and also has the signing issue mentioned Here), however with the signing issue I'd have to OTA update first so that's not relevant.
I've looked into Sunshine for S-OFF as well as This thread to convert to the "Unlocked" version that has the update, however I'm seeing comments about it not being compatible with the Sprint edition.
I've most recently tried to follow This guide, however I've had no luck and I'm still seeing talk of random reboots, dropped calls, and the like.
Basically, if there's any way I can get Android 7.0 Nougat on my phone, I would love to know how - if I can't (reasonably), then I'd also like to know that so I can stop beating my head into the wall, so to speak
Thanks!
Jaxas said:
Basically, if there's any way I can get Android 7.0 Nougat on my phone, I would love to know how - if I can't (reasonably), then I'd also like to know that so I can stop beating my head into the wall, so to speak
Thanks!
Click to expand...
Click to collapse
So far, the CDMA versions of the A9 can't run Nougat. As you know, HTC hasn't updated it for Nougat, and our phones run different enough firmware from the GSM-Locked and Dev versions that we can't use theirs. And so far, HTC's Dev Nougat requires Nougat firmware. So... we're boned.
Hopefully this won't be forever; HTC should eventually update American phones, so we'll just have to factory reset from system image (and maybe RUU) and OTA. For now, we can only hope guys like Captain_Throwback figure out how to backport Nougat to the 1.60.651.4 firmware.
Jaxas said:
Hello,
I'm basically at my wit's end and I'd just like to see if anyone knows whether it's actually possible to get Android 7.0 Nougat on my phone?
I currently have a rooted, RUU-updated 6.0.1 build of Android (Version Number: 1.60.651.4) running on a Sprint (so CDMA) HTC One A9 (Model Number: 2PQ9300). My phone is still S-On (I'm willing to pay for Sunshine if it'll actually work for me, but I'd like to confirm that first), and due to the updating process I do not currently have TWRP - that's easily fixed, however.
Mostly, I'd just like to know if there's a way to get Android 7.0 on my phone, as it is not the International version, while also retaining things like mobile data and calling.
So far, I've looked into simply flashing the RUU (seems to be both not compatible with my phone version, and also has the signing issue mentioned Here), however with the signing issue I'd have to OTA update first so that's not relevant.
I've looked into Sunshine for S-OFF as well as This thread to convert to the "Unlocked" version that has the update, however I'm seeing comments about it not being compatible with the Sprint edition.
I've most recently tried to follow This guide, however I've had no luck and I'm still seeing talk of random reboots, dropped calls, and the like.
Basically, if there's any way I can get Android 7.0 Nougat on my phone, I would love to know how - if I can't (reasonably), then I'd also like to know that so I can stop beating my head into the wall, so to speak
Thanks!
Click to expand...
Click to collapse
hey,
can you try this ...
https://forum.xda-developers.com/one-a9/general/htc-one-a9-android-7-nougat-t3546557
New info: Nougat is now available via OTA. Now we just need to... get back to full stock.
Woo! Just saw the notification. So now the question is if TWRP will work with 7.0 on our phones.. I think I'd rather keep root than upgrade and lose it if there's a choice.
JohnRogers23 said:
Woo! Just saw the notification. So now the question is if TWRP will work with 7.0 on our phones.. I think I'd rather keep root than upgrade and lose it if there's a choice.
Click to expand...
Click to collapse
TWRP 3.0.3 beta is available for nougat
MGfusion said:
TWRP 3.0.3 beta is available for nougat
Click to expand...
Click to collapse
I saw, but I'm not sure what's going on in the thread right now. It seems it sometimes bootloops? I'm hesitant to upgrade until there's either an RUU for 2.whatever out or I'm sure TWRP is reliable. I'm resigning myself to living without Xposed, but I at least need root and Magisk.
JohnRogers23 said:
Woo! Just saw the notification. So now the question is if TWRP will work with 7.0 on our phones.. I think I'd rather keep root than upgrade and lose it if there's a choice.
Click to expand...
Click to collapse
Whelp.
I'm upset, lol.
Time to re-reset my phone (finally got it set back up the way I wanted it yesterday on 6.0.1)
Oh well, thanks for the heads up!
I have the Sprint a9. I flashed the ruu and flashed TWRP 3.0.3-1 I believe, with no issues
Okay, so before I go re-wipe my phone and upgrade, I have a few quick questions...
1) Can this update be flashed with S-ON? (I'm assuming so, but always good to check) and
2) Can the Sprint A9 be rooted on Nougat yet?
Thanks!
I used TWRP 3.0.3.-4 and root with Magisk. Still miss Xposed, but the N features are pretty nice too. All seems to be working well.
Hello again, sorry to bother you guys but I'm seeing a surprising amount of conflicting information about this...
So I'm trying to upgrade to Nougat, but I'm having some troubles figuring out what I need to do for that.
I know I need to get my phone back to stock so I can accept the OTA update, but I'm not sure how to go about that.
My phone currently:
- Phone Model: HTC One A9 (Sprint - 2PQ93)
- Android Version: 6.0.1
- Software Version: 1.60.651.4
- Root: Yes
- Recovery: TWRP v2.8.8.2_CPTB-TEST2
- S: ON
- Bootloader: Unlocked
- Software Status: Modified
So as far as I'm aware, I need to restore the Stock recovery (how?), re-flash the RUU for my current software version, and then... relock the bootloader? Maybe?
So my questions are...
- How do I actually restore the stock recovery?
- Are there any steps I'm missing?
- Do I need to re-lock the bootloader, or does that not matter?
(- Is there anything I need to do once I get Nougat to root besides flash TWRP 3.0.3 & SuperSU through that?)
Thanks!
Jaxas said:
So as far as I'm aware, I need to restore the Stock recovery (how?), re-flash the RUU for my current software version, and then... relock the bootloader? Maybe?
So my questions are...
- How do I actually restore the stock recovery?
- Are there any steps I'm missing?
- Do I need to re-lock the bootloader, or does that not matter?
(- Is there anything I need to do once I get Nougat to root besides flash TWRP 3.0.3 & SuperSU through that?)
Thanks!
Click to expand...
Click to collapse
If you don't have an unmodified system image from before you mounted the system partition then yes, you do have to use an RUU, which will also give you stock recovery. No, you don't need to do anything with the bootloader.
Flash the RUU for the version you're on now, start up normally and take the OTA. No, I didn't have to do anything special besides making double checking /system is mounted read-only in TWRP. Personally I like using Magisk for root, etc, but I've heard SuperSU works fine. too. I'm S-on as well and it was all very easy.
I have a modified htc one a9 sprint, i want to get back to fully stock so i can update my device by using RUU side load. Please help
samweli benjamin said:
I have a modified htc one a9 sprint, i want to get back to fully stock so i can update my device by using RUU side load. Please help
Click to expand...
Click to collapse
What is your CID, MID and version-main? Is your bootloader locked or unlocked? S-ON or S-OFF?
I have attached a screenshot of getvar all for my device, when i was attemping to update it by using RUU its status was LOCKED and S-OFF but currently its status is **RE-LOCKED** and S-OFF
samweli benjamin said:
I have attached a screenshot of getvar all for my device, when i was attemping to update it by using RUU its status was LOCKED and S-OFF but currently its status is **RE-LOCKED** and S-OFF
Click to expand...
Click to collapse
What ruu version were you trying to flash and what was the error?
It was RUU_HIA_AERO_WHL_N70_SENSE80GP_SPCS_MR_Sprint_WWE_2.18.651.2 and the ERROR that I received was SIGNARURE ERROR: 132
samweli benjamin said:
It was RUU_HIA_AERO_WHL_N70_SENSE80GP_SPCS_MR_Sprint_WWE_2.18.651.2 and the ERROR that I received was SIGNARURE ERROR: 132
Click to expand...
Click to collapse
You can't flash a nougat ruu (2.xx.xxx.x) on a phone running the marshmallow firmware (1.xx.xxx.x). You need to manually update your firmware to 2.xx.651.x before being able to flash the 2.18.651.2 RUU. This is because the new signature key implemented in all 2.xx.xxx.x ruu, explained here at faq #4
Or you can flash the older 1.60.651.4 ruu and after, update your phone using OTA updates. Probably the easiest way for you :good:
http://dl3.htc.com/application/RUU_HIA_AERO_WHL_M60_SENSE7GP_SPCS_MR_Sprint_WWE_1.60.651.4.exe
This seems to be of great help to me, but am afraid i can't install the OTA in my device, b'se I received it and i did downloaded it but when i click to install it finish unzipping file and then fail and the phone boots in TWRP recovery so i thought i can update it by running a RUU side load
According to the Verizon Galaxy S5 Update Page:
Android® Security Patch Level: 2017–08-01
August 2017 Android security patches.
Fixed an issue where device was unable to connect and pair with some Bluetooth® Low Energy (BLE) devices.
Click to expand...
Click to collapse
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME_No_Aboot.tar.md5.zip
This update prevent downgrading for older builds?
enmanuel255 said:
This update prevent downgrading for older builds?
Click to expand...
Click to collapse
I doubt it since the only time that really happens is when the number in the bootloader is increased.
For example, the first time the VZW S5 was updated to prevent downgrading was when the firmware version went from G900VVRU1BOD5 to G900VVRU2BOE1.
The VRU1 and VRU2 are the bootloader versions. Once updated to VRU2/VRS2, you can't go back to VRU1. For some reason they keep changing back and forth from VRU2 to VRS2 at random times. The past few updates have either been VRU2 or VRS2 but you can still go all the way back to the first firmware with VRU2.
TLDR; Since this firmware is using the VRU2 bootloader, it is very unlikely that it will prevent downgrading.
On a side note, this is the longest that it has taken for the complete Odin firmware to be uploaded to Samsung's servers. The update was out the 13th. Normally it takes 3 days for it to be available on their servers and it still isn't. I even tried using the Verizon Software Upgrade Assistant and both of my S5's say they are up to date on QF2.
It's rolled out:
Checking firmware for SM-G900V/VZW/G900VVRU2DQF2/G900VVZW2DQF2/G900VVRU2DQF2/G900VVRU2DQF2
Model: SM-G900V
Version: G900VVRU2DQH2/G900VVZW2DQH2/G900VVRU2DQH2/G900VVRU2DQH2
OS: Marshmallow(Android 6.0.1)
Filename: SM-G900V_1_20170824083446_06zw9gofua_fac.zip.enc4
Size: 2292181872 bytes
LogicValue: 0zmklm1qb9k6sfxe
Click to expand...
Click to collapse
P.S. I would not hurry with this upgrade. As for now I experience sound stuttering in my Samsung Level Active earbuds.
Trying to found out the cause but it definitely happened after bootloader/kernel/modems upgrade to DQH2.
bbsc said:
It's rolled out:
P.S. I would not hurry with this upgrade. As for now I experience sound stuttering in my Samsung Level Active earbuds.
Trying to found out the cause but it definitely happened after bootloader/kernel/modems upgrade to DQH2.
Click to expand...
Click to collapse
Yep I literally just saw that it was. I checked at 12:30am EST and it wasn't.
It's odd that you'd be having problems with bluetooth headphones since this update is supposed to fix bluetooth problems, other than the security related bluetooth problems.
Dudash said:
It's odd that you'd be having problems with bluetooth headphones since this update is supposed to fix bluetooth problems
Click to expand...
Click to collapse
See below.
Lost Hotspot Functionality
Once I flashed this update I lost the ability to bypass Verizon's check to use the hotspot functionality. Now it keeps checking my account and wanting me to pay for the service. Is there anyway I can get around this again, as I was able to with basic root?
I did flash the Developer Bootloader Friendly version using FlashFire.
In addition to my previous post.
Ok, I've been experimenting for a few days with two units of SM-G900V and two pairs of Samsung Level Active wireless earbuds.
I was walking in the same places and listening the same music in the same conditions with different earbuds and different phones, having different (DQF2 and DQH2) firmware (kernel, modem, recovery). In all cases the phones were loaded with the same /system ROM - stock-near ALEXNDR.G900FXXS1CQH1
My conclusion is: DQH2 keeps bluetooth connection much worse than DQF2.
I cannot say that we have a crystal-clear sound in one case and a crappy stuttering in the other.
But the difference is noticeable and obvious.
That's why I personally am reverting back to DQF2 firmware.
wbr.
Updated to this build from QA1, flashed in odin, then booted up, reflashed TWRP and SU, froze system updater all good. No problems here with BT streaming music 2hrs a day in my car for 3 days.
After Flashear everything is fine except autorotation, it does not work for me
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME.tar.md5.zip
Is there a full stock non rooted retail download available? I would like to revert completely to stock.
MrTrumpz said:
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME.tar.md5.zip
Is there a full stock retail download available? I would like to revert completely to stock.
Click to expand...
Click to collapse
That will return you to stock, it just won't delete all of your data.
If you want stock firmware that will completely wipe your device, you can go to my thread here.
Keep in mind that if you are on a firmware that has VRU2 or VRS2 in the name, you cannot downgrade to a firmware that has VRU1 in the name.
Dudash said:
That will return you to stock, it just won't delete all of your data.
If you want stock firmware that will completely wipe your device, you can go to my thread here.
Keep in mind that if you are on a firmware that has VRU2 or VRS2 in the name, you cannot downgrade to a firmware that has VRU1 in the name.
Click to expand...
Click to collapse
Thanks so much. I appreciate the response.
If i unlocked my bootloader on PB1 firmware, will I have issues flashing this firmware? For some reason I've always thought updating my firmware without updating the bootloader like I originally had to would cause some serious problems. Or did I misinterpret the necessity of updating the bootloader to match the firmware? Is that even an actual problem if they don't match?
Maphack said:
Is that even an actual problem if they don't match?
Click to expand...
Click to collapse
Nobody knows the exact answer except Samsung itself.
In most cases it works.
But this bootloader can be unlocked in the same way as the others if you have CID15.
bbsc said:
Nobody knows the exact answer except Samsung itself.
In most cases it works.
But this bootloader can be unlocked in the same way as the others if you have CID15.
Click to expand...
Click to collapse
Sorry, I was unclear. I unlocked my bootloader and chose PB1 as the firmware to be... Unlocked on, I guess? Not sure the proper phrasing for it.
So I have an unlocked bootloader, but am afraid of updating my firmware in case that messes up something.
If you already answered my question and my response to your question is just due to my lack of knowledge, I apologize.
@Maphack
Ok, let's clarify the things a little.
1. Locked bootloader is called "locked" because it doesn't boot custom unsigned kernels, i.e. rooted 6.0.1 kernels, TWRP kernels, kernels from kernel modders, etc.
2. Virtually all bootloaders in SM-G900V are locked by default.
3. Some of them can be unlocked if the phone has CID15.
4. People unlock bootloaders to install a custom recovery, to have root on 6.0.1, etc.
5. BPB1 is Android 5.0 and it does not require unlocked bootloader for to be rooted because root on 5.0 does not require kernel modification. So you may not know if it's locked or unlocked if you're on BPB1 currently.
But you can see it in download mode.
So if you want to update to QH2 or another 6.0.1 ROM, you need first:
1. Decide if you need root on 6.0.1.
2. Check the CID of your phone with EMMC Brickbug Check app from Market.
P.S. Probably I misunderstood you and your current firmware is not BPB1 but some 6.0.1 firmware and you are talking about BPB1 as about that firmware you've used to unlock bootloader on.
That's another story.
You can find directions how to update unlocked bootloader here.
bbsc said:
@Maphack
Ok, let's clarify the things a little.
1. Locked bootloader is called "locked" because it doesn't boot custom unsigned kernels, i.e. rooted 6.0.1 kernels, TWRP kernels, kernels from kernel modders, etc.
2. Virtually all bootloaders in SM-G900V are locked by default.
3. Some of them can be unlocked if the phone has CID15.
4. People unlock bootloaders to install a custom recovery, to have root on 6.0.1, etc.
5. BPB1 is Android 5.0 and it does not require unlocked bootloader for to be rooted because root on 5.0 does not require kernel modification. So you may not know if it's locked or unlocked if you're on BPB1 currently.
But you can see it in download mode.
So if you want to update to QH2 or another 6.0.1 ROM, you need first:
1. Decide if you need root on 6.0.1.
2. Check the CID of your phone with EMMC Brickbug Check app from Market.
P.S. Probably I misunderstood you and your current firmware is not BPB1 but some 6.0.1 firmware and you are talking about BPB1 as about that firmware you've used to unlock bootloader on.
That's another story.
You can find directions how to update unlocked bootloader here.
Click to expand...
Click to collapse
Thanks. Yeah, I'm already on an unlocked bootloader running 7.1.4. I'll look into updating an unlocked bootloader. I appreciate the help.
Or is there even a point for me to tweak my phone at this point?
Maphack said:
Or is there even a point for me to tweak my phone at this point?
Click to expand...
Click to collapse
None.
Modem upgrade, maybe...
But if you're satisfied, don't repair a working thing.
Help
Dudash said:
According to the Verizon Galaxy S5 Update Page:
Stock No-Wipe Firmware:
*This will remove Developer Status/Lock your Bootloader*
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME.tar.md5.zip
Developer Bootloader Friendly/No Aboot No-Wipe Firmware:
G900VVRU2DQH2_G900VVZW2DQH2_G900VVRU2DQH2_HOME_No_Aboot.tar.md5.zip
Click to expand...
Click to collapse
Currently this is my System info.
Model - SM G900V
Baseband - G900VVRU2DPD1
Kernel - 3.4.0 [email protected] #1
Build Number - MMB29M.G900VVRU2DPF4
I flashed NI2 using Odin and have Safestrap. I have been away from this phone for long so lost touch of the updates. I have not flashed the Dev bootloader or unlocked it as far as I remember because when I installed this rom, there was no method to unlock bootloader. Can I still flash the QH2 update on this in Safestrap, the Developer Friendly version or the official.
the samsung device maintenance system app worked alright in the past, but I've been seeing a few people not liking the new update since it apparently targets more than what it should; I aimed to not update it at all, but while I was updating apps before I went to sleep yesterday, that app updated as well. I didn't know it did so I've been trying to downgrade it to an earlier version. I downloaded an apk file from apkmirror, made sure to uninstall the updates to it and set it to factory version, but it won't let me install, saying it conflicts with the same app already present. I then used the adb command-line tool to "uninstall" it (pm uninstall -k --user 0 com.samsung.android.lool ), hoping it would work then, but it says "nope, this app doesn't exist on this phone, plus this apk file is corrupted". I can "re-install" it by installing it from the google play store
I'm at a loss on how I can get this done without root (I don't plan on rooting my phone unless the situation is perfect for it), using the adb tool or any tool that won't kill my phone. Any help
LodeUnknown said:
the samsung device maintenance system app worked alright in the past, but I've been seeing a few people not liking the new update since it apparently targets more than what it should; I aimed to not update it at all, but while I was updating apps before I went to sleep yesterday, that app updated as well. I didn't know it did so I've been trying to downgrade it to an earlier version. I downloaded an apk file from apkmirror, made sure to uninstall the updates to it and set it to factory version, but it won't let me install, saying it conflicts with the same app already present. I then used the adb command-line tool to "uninstall" it (pm uninstall -k --user 0 com.samsung.android.lool ), hoping it would work then, but it says "nope, this app doesn't exist on this phone, plus this apk file is corrupted". I can "re-install" it by installing it from the google play store
I'm at a loss on how I can get this done without root (I don't plan on rooting my phone unless the situation is perfect for it), using the adb tool or any tool that won't kill my phone. Any help
Click to expand...
Click to collapse
Uninstalling updates and reverting it back to the factory version is downgrading it as far as it will downgrade, and if it worked before you let it update, then you are running the version (factory) that was working previously, therefore something else is wrong if it still doesn't work
*Detection* said:
Uninstalling updates and reverting it back to the factory version is downgrading it as far as it will downgrade, and if it worked before you let it update, then you are running the version (factory) that was working previously, therefore something else is wrong if it still doesn't work
Click to expand...
Click to collapse
what would I have to do to diagnose this if possible, and if it can't be, am I pretty much at a dead end?
LodeUnknown said:
what would I have to do to diagnose this if possible, and if it can't be, am I pretty much at a dead end?
Click to expand...
Click to collapse
Flash the same ROM over the top using HOME_CSC instead of CSC so not to lose data
If that fails, bite the bullet and factory reset
*Detection* said:
Flash the same ROM over the top using HOME_CSC instead of CSC so not to lose data
If that fails, bite the bullet and factory reset
Click to expand...
Click to collapse
im using the default Android OS (7.1 nougat), no custom ROMs, and this android phone was bought at an AT&T retailer; if the right chance comes, I would be willing to flash a custom rom (probably LineageOS) after I get it unlocked (doubt ill be updating to a newer phone unless there's an actual difference) and the money situation is good, but until then, sticking with what I got
I did remember about an application called odin that can (maybe?) flash stock rom of android without tripping the knox counter, that true? and if I do, will I lose all my installed stuff, apps, contact info, etc...
LodeUnknown said:
im using the default Android OS (7.1 nougat), no custom ROMs, and this android phone was bought at an AT&T retailer; if the right chance comes, I would be willing to flash a custom rom (probably LineageOS) after I get it unlocked (doubt ill be updating to a newer phone unless there's an actual difference) and the money situation is good, but until then, sticking with what I got
I did remember about an application called odin that can (maybe?) flash stock rom of android without tripping the knox counter, that true? and if I do, will I lose all my installed stuff, apps, contact info, etc...
Click to expand...
Click to collapse
If your phone is a US model S7 (snapdragon) you cannot flash custom ROMs
My instructions are for ODIN (version 3.12.7 for Nougat)
So at this point, my only option is to switch to a new phone that can be used by Odin, or just standard root my phone and flash a custom rom of a different type, right?
LodeUnknown said:
So at this point, my only option is to switch to a new phone that can be used by Odin, or just standard root my phone and flash a custom rom of a different type, right?
Click to expand...
Click to collapse
You cannot flash a custom ROM to a snapdragon phone using any method, it has a locked bootloader
ODIN is for stock ROMs only (and TWRP recovery which you cannot use on snapdragon either)
You can use ODIN on any S7 for stock ROMs
To sum it all up, you're saying that I have to get an exynos/international version of any Android phone if I want to root and or flash a custom ROM, correct? And if I do, could I still use it with a US phone carrier, like AT&T or MetroPCS afterwards?
And even if I could use it with a US phone carrier, would I still be eligible for any technical support / repair service they would offer, or would I have to use a non-affiliated repair service?
LodeUnknown said:
To sum it all up, you're saying that I have to get an exynos/international version of any Android phone if I want to root and or flash a custom ROM, correct? And if I do, could I still use it with a US phone carrier, like AT&T or MetroPCS afterwards?
And even if I could use it with a US phone carrier, would I still be eligible for any technical support / repair service they would offer, or would I have to use a non-affiliated repair service?
Click to expand...
Click to collapse
Yes, only Exynos has an unlocked bootloader (See the snapdragon vs exynos custom ROM dev forums)
Yes you could still use a US carrier as long as the phone is SIM unlocked (carphone warehouse phones are all unlocked), I have no idea of the limitations / implications, but some people here already do that, and the G930W8 (Canada) is Exynos
No idea about warranty, but if you bought it from say the UK and had it shipped, you'd have to discuss with Samsung if they would accept it into a US service centre or if you'd have to ship it back to the UK, no idea about that, no doubt there are places in the US that you could buy a Exynos from
Hit Samsung up on twitter and ask them
Hi guys,
I bought S8 and I'm looking for best way how to root and unroot device. I want to have updates of my device but I need root too . I dont want custom roms. I want stock rom.
Is there any way?
Thanks for answer
vlakiks said:
Hi guys,
I bought S8 and I'm looking for best way how to root and unroot device. I want to have updates of my device but I need root too . I dont want custom roms. I want stock rom.
Is there any way?
Thanks for answer
Click to expand...
Click to collapse
If you modify your phone ( root ) you will loose the option to update ( OTA update ).
If you want to update you phone you will have to download firmware and flash with Odin. Everytime that you update firmware you will have to re-root you phone again.
spawnlives said:
If you modify your phone ( root ) you will loose the option to update (TA update ).
If you want to update you phone you will have to download firmware and flash with Odin. Everytime that you update firmware you will have to re-root you phone again.
Click to expand...
Click to collapse
Thank you for answer.
Data will be lost after reflash?
vlakiks said:
Thank you for answer.
Data will be lost after reflash?
Click to expand...
Click to collapse
Generally yes ( mainly with rooting )
You can backup your app/data by using something like Google backup service or smart switch ( PC app ).
Hey guys,
Hopefully I'm not requesteing a completely useless thing cause I haven't found a fix so far. Since it's somehow related to firmware flashing via Odin, I chose to ask in this thread.
I bought my Galaxy S8+ a while ago and carrier unlocked it (It was on Vodafone Romania). Ever since unlocking the carrier, I can't seem to receive any firmware updates for some reason.
Smart switch says I'm at the latest firmware version but according to Sammobile, I'm far from being at the last version. (Still Android 8 on it)
My phone is not rooted (I haven't felt the need to root it so far because it's been doing great). Any ideas how can I fix this and install the latest firmware?
If I download the latest Romania firmware from sammobile (carrier-free version) and flash it through Odin, would it work or I'd encounter a difference because the CSC is Vodafone Romania?
Thanks!
Hey is there a way to root the SM-G975U with security update on july 1, android pie, and a way to unroot? (like the stock rom files)
Thanks