Related
I have done flashing and rooting in the past on both a Samsung Charge, Nexus and S3, but it's been a while. Ive used Odin, and the TOOLKIT, and am somewhat familiar with both.
I have had my S3 for several years, STOCK, STOCK, STOCK, and liked it just the way it was. I had a WIFI tethering app, SVTP that worked, and didnt take updates for fear it would quit working, well I accidentally took an update, and now it doesnt work.
Id like to reflash the phone back to a previous stock software, I forget which one I had, but currently here is my phone info
SCH-I535
4.3
I535VRUCML1
KERNEL 3.0.31
build JSS15J.I535VRUCML1
hardware I535.10
I believe I had Jellybean, or a 4.0 firmware.
How should I flash this back, and where can I download the files and the correct version of ODIN?
So i attempted to flash an older OS 4.0 i think, with odin, and It said ABOOT FAIL! and I kind of bricked it. Was I supposed to unlock the boot loader or wipe the device before doing this?
Now I got it connected to kies and am in the process of downloading latest Samsung OS to phone, so i can try again.
What did I do wrong?
Nitro169 said:
So i attempted to flash an older OS 4.0 i think, with odin, and It said ABOOT FAIL! and I kind of bricked it. Was I supposed to unlock the boot loader or wipe the device before doing this?
Now I got it connected to kies and am in the process of downloading latest Samsung OS to phone, so i can try again.
What did I do wrong?
Click to expand...
Click to collapse
As long as your not on the NC1 or NE1 baseband/firmware you can indeed revert back to an older version. And you do indeed have to unlock the bootloader to revert to a previous version of Android
In my personal opinion your best bet is the casual root/unlock method which will do both for you
Sent from my Nexus 5
so i have NE1 now. Why cant i downgrade anymore?
Tonight im going to reattempt to flash 4.1 with odin, unlocking bootloader first.
my only othed issue is i can find very few versions of Stock OS on web. There should be like 5 or 6 for this phone, ive only found 2 or 3. Please point me in direction of any stock OS files.
Nitro169 said:
so i have NE1 now. Why cant i downgrade anymore?
Tonight im going to reattempt to flash 4.1 with odin, unlocking bootloader first.
my only othed issue is i can find very few versions of Stock OS on web. There should be like 5 or 6 for this phone, ive only found 2 or 3. Please point me in direction of any stock OS files.
Click to expand...
Click to collapse
Because your on a locked bootloader and downgrading now would brick your device
Sent from my Nexus 5
Is there no method to unlock these firmwares currently?
if so does anyone have an S3 for sale that has older firmware?
Nitro169 said:
Is there no method to unlock these firmwares currently?
if so does anyone have an S3 for sale that has older firmware?
Click to expand...
Click to collapse
Check swappa for that. I know brand new ones have the newest firmware, your better bet is swappa
And no they are locked down tightly, unlocking is nearly impossible
Sent from my Nexus 5
what if i soft brick it on purpose, can i somehow download an older version via kies once soft bricked?
Nitro169 said:
what if i soft brick it on purpose, can i somehow download an older version via kies once soft bricked?
Click to expand...
Click to collapse
No, you can't get around the locked bootloader. Your stuck on it
Sent from my Nexus 5
I believe even the 4.3 ML1 update will lock your bootloader. The 4.4.2 NE1 definitely will. There's no known way to revert back to an unlocked bootloader.
MrBrady said:
I believe even the 4.3 ML1 update will lock your bootloader. The 4.4.2 NE1 definitely will. There's no known way to revert back to an unlocked bootloader.
Click to expand...
Click to collapse
You are correct. I did a quick search and those who took the 4.3 ML1 OTA are indeed on a locked bootloader
Sent from my Nexus 5
(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
Hi guys,
yesterday I made update of Renovate ROM like other days. First of all I updated new firmware (G950FXXU1AQG5) and restarted to recovery (via TRWP) again to make rom update. BUT...after firmware update my loved S8+ didnt reboot to recovery but freeze on Samsung LOGO. And now I can only start DOWNLOAD mode. There is no way to go to RECOVERY. No reaction on hotkeys, ADB command line doesnt work too...there is no way how to start RECOVERY mode.
I tried DOWNLOAD mode and ODIN to make firmware uploads again but ALWAYS Odin say <ID:0/007> FAIL! (DeviceInfo). So doesnt matter if I had try to upload firmware or complet stock rom or only BL and CL always ODIN give me error.
Please is there somebody who can help me with this terrible situation. I need my phone for everyday work....
Thanks 2 All
dc98 said:
Hi guys,
yesterday I made update of Renovate ROM like other days. First of all I updated new firmware (G950FXXU1AQG5) and restarted to recovery (via TRWP) again to make rom update. BUT...after firmware update my loved S8+ didnt reboot to recovery but freeze on Samsung LOGO. And now I can only start DOWNLOAD mode. There is no way to go to RECOVERY. No reaction on hotkeys, ADB command line doesnt work too...there is no way how to start RECOVERY mode.
I tried DOWNLOAD mode and ODIN to make firmware uploads again but ALWAYS Odin say <ID:0/007> FAIL! (DeviceInfo). So doesnt matter if I had try to upload firmware or complet stock rom or only BL and CL always ODIN give me error.
Please is there somebody who can help me with this terrible situation. I need my phone for everyday work....
Thanks 2 All
Click to expand...
Click to collapse
Read this thread it might help ?
Read OP Post #1
Good luck
https://forum.xda-developers.com/galaxy-s8/help/stuck-bootloop-flashing-aqg5-fix-t3636857
I'm no expert so take this as tip/question.
Are you using the latest Odin 3.12.3? http://odindownload.com/SamsungOdin/
You can download the bootloader AQF7 from here : https://www.androidfilehost.com/?fid=889764386195911671
Possible your tar/md5 is corrupt?
TWRP will be updated to work as soon as Samsung release the kernel source so that it can be updated to work. No ETA unfortunately
Flash a custom "Kernel"!
dc98 said:
Hi guys,
yesterday I made update of Renovate ROM like other days. First of all I updated new firmware (G950FXXU1AQG5)
Click to expand...
Click to collapse
AQG5 isnt support yet, so phone dont start again like bootloop
download the old Bootloader : BL_G950FXXU1AQF7
https://www.androidfilehost.com/?fid=889764386195911673
maybe CL : modem CP_G950FXXU1AQF7
https://www.androidfilehost.com/?fid=889764386195911675
flash it over Odin , than restart the phone.
good luck
The new update locks the Exynos bootloader! Don't flash the new Bootloader!
B3501 said:
The new update locks the Exynos bootloader! Don't flash the new Bootloader!
Click to expand...
Click to collapse
Same question as the other thread....where did you this information from?
sent from my Note FE, S8 plus, S7 edge or S6
force70 said:
Same question as the other thread....where did you this information from?
sent from my Note FE, S8 plus, S7 edge or S6
Click to expand...
Click to collapse
https://forum.xda-developers.com/showthread.php?p=73084829
The best we can hope for is that its just enhanced security that can be overcome with the new sources when released. The worst outcome is they've locked the BL and its unlockable like the Snapdragon version which means we'll be stuck on the current BL and will be unable to install new updates that need a new BL.
B3501 said:
https://forum.xda-developers.com/showthread.php?p=73084829
The best we can hope for is that its just enhanced security that can be overcome with the new sources when released. The worst outcome is they've locked the BL and its unlockable like the Snapdragon version which means we'll be stuck on the current BL and will be unable to install new updates that need a new BL.
Click to expand...
Click to collapse
Well considering that we can downgrade back to the previous BL....we know its not locked. Common sense really.
no need to start posting all over the board the BL is locked unless you have proof of it 100%.
force70 said:
Well considering that we can downgrade back to the previous BL....we know its not locked. Common sense really.
no need to start posting all over the board the BL is locked unless you have proof of it 100%.
Click to expand...
Click to collapse
You can't downgrade unless you button mash which is most likely a bug. It's pretty obvious Samsung are trying to stop bootloader unlocking on the Exynos.
Batfink33 said:
You can't downgrade unless you button mash which is most likely a bug. It's pretty obvious Samsung are trying to stop bootloader unlocking on the Exynos.
Click to expand...
Click to collapse
Im not sure what you mean exactly...i was talking about simply flashing the previous BL in Odin which people are doing.
And the exynos bootloaders do not and have never required unlocking because they are not locked to begin with.
Further to that this isnt the first time samsung pushed an update that broke twrp and root...its happened lots of times on sammy devices over the years... they will get it fixed no doubt.
Now that's not to say that they arent trying to prevent us from modding our devices...and it may happen at some point that the exynos does get locked...time will tell
force70 said:
Im not sure what you mean exactly...i was talking about simply flashing the previous BL in Odin which people are doing.
And the exynos bootloaders do not and have never required unlocking because they are not locked to begin with.
Further to that this isnt the first time samsung pushed an update that broke twrp and root...its happened lots of times on sammy devices over the years... they will get it fixed no doubt.
Now that's not to say that they arent trying to prevent us from modding our devices...and it may happen at some point that the exynos does get locked...time will tell
Click to expand...
Click to collapse
It would ruin a lot of peoples phones if they did lock the Exynos versions and would be a very shady move.
Batfink33 said:
It would ruin a lot of peoples phones if they did lock the Exynos versions and would be a very shady move.
Click to expand...
Click to collapse
Damn straight it would...No one loves sammy phones more than me but if they do that i wont buy another sammy device.
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.
Hey everyone hope you're all well. I have an s8 plus that's not booting. Here's the events that transpired....
My nephew wanted it wiped so I went into recovery and it immediately started to install an update for some reason and wouldn't boot, so I told his brother to flash a stock ROM which he did and booted fine, but with one issue, it showed as 16gb instead of 64gb. At this point I downloaded a pit file and flashed it. I then flashed the stock ROM and it won't get past the Samsung logo.
This is the stock ROM I flashed, AP_G955FXXSADTI1_CL18920278_QB34109287_REV00_user_low_ship_meta_OS9
I'm guessing I need to flash the correct pit file and then the stock ROM?
Any advice would be appreciated
Thanks!
thedan55 said:
Hey everyone hope you're all well. I have an s8 plus that's not booting. Here's the events that transpired....
My nephew wanted it wiped so I went into recovery and it immediately started to install an update for some reason and wouldn't boot, so I told his brother to flash a stock ROM which he did and booted fine, but with one issue, it showed as 16gb instead of 64gb. At this point I downloaded a pit file and flashed it. I then flashed the stock ROM and it won't get past the Samsung logo.
This is the stock ROM I flashed, AP_G955FXXSADTI1_CL18920278_QB34109287_REV00_user_low_ship_meta_OS9
I'm guessing I need to flash the correct pit file and then the stock ROM?
Any advice would be appreciated
Thanks!
Click to expand...
Click to collapse
Flash full firmware not just AP file. Flashing AP file only is more than likely the reason for difference in storage size.
No need for pit file. If it is needed it can be exacted from the firmware that you have downloaded.
I did flash all 4 files not just the ap. I only wanted to show the version etc
Now when I try to flash Odin says failed
What Odin version are you using
What errors in Odin
Can you post a copy of download mode and error in Odin
spawnlives said:
What Odin version are you using
What errors in Odin
Can you post a copy of download mode and error in Odin
Click to expand...
Click to collapse
Absolutely. Odin3 3.13
I've also attached a picture of the rom files. For some reason there's 2 CSC files. I tried using both but same issue.
thedan55 said:
Absolutely. Odin3 3.13
I've also attached a picture of the rom files. For some reason there's 2 CSC files. I tried using both but same issue.
Click to expand...
Click to collapse
1. CSC files
CSC file will wipe all apps and data ( same as out of the box )
HOME_CSC file will keep apps and data
2. The reason Odin is failing is you are trying to downgrade your firmware.
You are on bootloader version 11 the firmware you are flashing is on version 10. You can check in download mode to check bootloader version. There will be a line saying AP SWREV. The number after the letter B is your bootloader number.
Also in download mode down the bottom ( in red ) will tell the reason why it is failing.
You will have to find what firmware was flash before or wait for samsung to upgrade it's bootloader version.
spawnlives said:
1. CSC files
CSC file will wipe all apps and data ( same as out of the box )
HOME_CSC file will keep apps and data
2. The reason Odin is failing is you are trying to downgrade your firmware.
You are on bootloader version 11 the firmware you are flashing is on version 10. You can check in download mode to check bootloader version. There will be a line saying AP SWREV. The number after the letter B is your bootloader number.
Also in download mode down the bottom ( in red ) will tell the reason why it is failing.
You will have to find what firmware was flash before or wait for samsung to upgrade it's bootloader version.
Click to expand...
Click to collapse
I see. The strange thing is that this is the firmware that my nephew flashed after it initially failed and it flashed with no errors. The errors only occurred after I tried to flash the pit file, which I'm guessing was a big mistake.
Right so I need to find a stock ROM with bootloader 11. Is there an indicator in the filename that will tell me the bootloader version?
Why do I get this message every day? Throw the darn thing out already.
thedan55 said:
I see. The strange thing is that this is the firmware that my nephew flashed after it initially failed and it flashed with no errors. The errors only occurred after I tried to flash the pit file, which I'm guessing was a big mistake.
Right so I need to find a stock ROM with bootloader 11. Is there an indicator in the filename that will tell me the bootloader version?
Click to expand...
Click to collapse
Flashing the pit file should only fix the partition size and is generally not needed. Flashing the wrong pit file will cause issues. Doesn't effect the issue of trying to downgrading firmware.
As far I'm aware official samsung firmware is up to bootloader 10. Firmware should be downloaded from official site like sammobile or updato or pc apps like samfirm or frija
In regards to bootloader version ( official firmware ) it can be found in the firmware being downloaded.
Bootloader version will be the fifth number/letter from the right of firmware name.
eg:
G955FXXSADTI1 - A - bootloader version 10. I'm assuming the next bootloader version number will start with B
G955FXXU9DTF1 - 9 - bootloader version 9
The higher the number the higher the bootloader version.
Due to samsung anti róll back bootloader version cannot be downgraded.
Buy your nephew a damn phone
thedan55 said:
I see. The strange thing is that this is the firmware that my nephew flashed after it initially failed and it flashed with no errors. The errors only occurred after I tried to flash the pit file, which I'm guessing was a big mistake.
Right so I need to find a stock ROM with bootloader 11. Is there an indicator in the filename that will tell me the bootloader version?
Click to expand...
Click to collapse
pego99 said:
Buy your nephew a damn phone
Click to expand...
Click to collapse
I did buy him this phone. Just because it's a little messed up right now doesn't mean I should just thrown it out. This entire forum is dedicated to invigorating devices and keeping them going. XDA didn't accept the philosophy of throwing out devices when they can be repaired. I've been here long enough to know that.
Ffs people are still developing for the hp touchpad and m7 Windows devices!
Unsubscribe from this thread mate. Delete your replies so you don't notifications.
There's no need for your unhelpful comments when others are trying to be of assistance.
spawnlives said:
Flashing the pit file should only fix the partition size and is generally not needed. Flashing the wrong pit file will cause issues. Doesn't effect the issue of trying to downgrading firmware.
As far I'm aware official samsung firmware is up to bootloader 10. Firmware should be downloaded from official site like sammobile or updato or pc apps like samfirm or frija
In regards to bootloader version ( official firmware ) it can be found in the firmware being downloaded.
Bootloader version will be the fifth number/letter from the right of firmware name.
eg:
G955FXXSADTI1 - A - bootloader version 10. I'm assuming the next bootloader version number will start with B
G955FXXU9DTF1 - 9 - bootloader version 9
The higher the number the higher the bootloader version.
Due to samsung anti róll back bootloader version cannot be downgraded.
Click to expand...
Click to collapse
Thank you very much for your replies. It's very much appreciated mate.
I did flash the pit file and subsequently got errors in odin. I want aware that I was trying to downgrade. I've download from official site and will try flashing today.
Again thanks for the help. Been a while since I've had to do this lol I think the last device I was rooting and roming was my note 3! The support for it is still going strong though!
Cheers
I guess at some point its best to move on. My grandsons S8 had the digitizer go bad tried to fix unsuccessfully bought him a used on on fleabay for $150.
@spawnlives thank you very much. Phone is back up running perfectly. Appreciate it mate
@pego99 that's a judgment call. Fair enough buying an s8 screen is 100 and new is 150 it would be reasonable to buy a new device. However this was a software issue which costs nothing to fix. Your posts in this thread are redundant and useless.
thedan55 said:
@spawnlives thank you very much. Phone is back up running perfectly. Appreciate it mate
@pego99 that's a judgment call. Fair enough buying an s8 screen is 100 and new is 150 it would be reasonable to buy a new device. However this was a software issue which costs nothing to fix. Your posts in this thread are redundant and useless.
Click to expand...
Click to collapse
OK it costs nothing money wise but time but time is valuable. i.e. If you spend the next 6 months on this has it cost anything? Nope no out of pocket but a lot of time and nephew has no phone to use. BTW If you bought the phone in working condition how did it get screwed up anyway?
pego99 said:
OK it costs nothing money wise but time but time is valuable. i.e. If you spend the next 6 months on this has it cost anything? Nope no out of pocket but a lot of time and nephew has no phone to use. BTW If you bought the phone in working condition how did it get screwed up anyway?
Click to expand...
Click to collapse
It took less than an hour to fix this phone, that's a cost I can stomach.
if you had actually READ the post instead of commenting asinine remarks them you would know how the phone for corrupted in the first place.
Please stop replying to this now.