Sorry if this has been answered elswhere I can't find it.
Is it possible to change a standard uk tmobile g1 to an adp?
Or is it as simple as flashing an adp rom onto it? Ie does the hardware get locked down or is it just software?
download the update, wipe the phone, flash the update
Cool I will flash that later
Hey,
I just rooted my RC8 UK G1 using the guide here and then I came here and saw that JF1.43 is out, where the guide I was using used JF1.41.
Should I upgrade? What are the benefits and how do I upgrade?
Also, if a new OTA update comes out can I just update and keep root? If not, can I just update without doing anything special and loose root?
Thank you
JFv1.42 and 1.43 are US only so I believe you need to reflash to use, though I'm not sure. The number structure of US numbers is different (it has dashes in it like xxx-xxxx-xxxx) and they have some extra programs like MyFaves by the sound of it. For now if you want to stick with UK releases, you have the most recent. I contacted TMo about it and all they had to say was that they didn't know when our RC33 equivalent would be out.
Hi,
now I have the Official Holiday Firmwae 1.1 with Holiday Bootloader on my G1.
But I dont know if I should switch to ADP1.1 from HTC with Engeneer Bootloader.
Did anybody know if Holiday Phones has OTA Updates? Did you think Latitude comes for ADP1.1?
I develop for G1 but I can test the Software on my Holiday too. But I dont know if Google check the Imei sometime an I didnt get any update anymore...
Any big diffrents between the both versions?
Thx.
No Need
I had 1.1 Holiday installed, and it does NOT change your bootloader. The bootloader is not effected by firmware updates, if you have an ADP, you'll always have your Eng Bootloader (Unless you flash the HardSPL.)
As far as differences, it was my understanding that the updates were the same, the reason the Holiday version is called "Holiday" is because it was given out early to the Google Dev's as a Holiday bonus. The HTC version is just the official version as the Holiday versions were leaked.
In short, don't update, its the same firmware.
Where he Holiday Update comes they told me that the bootloader not mismatch so I downgraded my Bootloader...
I thank ADP dont get OTA Update?
The holiday OTA update came with a bootloader. You would have received this if you initially installed (manually) the original holiday image. If you installed the holiday update manually, you kept the original bootloader.
Both holiday and adp have latitude, it is just not activated -- same as with UK RC9. There is a thread about that somewhere around here that describes how to enable latitude.
Regarding choice between holiday and adp... choose adp and either engineering or hard spl. You never know what the future holiday updates are going to look like since the holiday phone is being treated somewhat differently than adp.
Mhmm in Holiday Version Latitude is enabled...
The ADP Firmware just published by HTC direct right?
What you mean with:
You never know what the future holiday updates are going to look like since the holiday phone is being treated somewhat differently than adp.
Click to expand...
Click to collapse
I have a dev phone and received the Holiday update OTA
rantrav said:
I have a dev phone and received the Holiday update OTA
Click to expand...
Click to collapse
That is because you manually installed the holiday firmware at some point before the OTA update came in.
Enquiry
Hi guys, is it possible to root my G1? My phone memory getting low with all the apps i installed
Model number: Android Dev Phone 1
Firmware version: 1.1
Baseband version: 62.33.20.08H_1.22.14.11
Kernel version: 2.6.25-01845-g85d4f0d [email protected] #27
Build number: holiday_devphone-userdebug 1.1 UNLOCKED 130444 test-keys
your phone is rooted...
Forgive me if this has already been answered somewhere. I've read literally hundreds of posts here, and I think I might be suffering from temporary information overload.
Last week I successfully rooted my G1 by following one of the several sets of instructions here. I now want to use JFUpdater to upgrade my G1 to a rooted version of Cupcake, but I am unable to do so. JFUpdater just tells me that there are no updates for me.
This is my current configuration:
Model Number: T-Mobile G1
Firmware version: 1.1
Baseband version: 62.33.20.08H_1.22.14.11
Kernel version: 2.6.25-01843-gfea26b0 [email protected] #1
Build number: kila-user 1.1 PLAT-RC33 126986 ota-rel-keys, release-keys
When I start JFUpdater, I get this message:
No updates found.
Press 'Check now' to manually
check for new updates.
When I select 'Check now' I get a "Checking for updates" message followed by "No JF OS updates found" 5-10 seconds later.
I thought that I would be able use JFUpdater to upgrade my rooted RC33 system to a rooted Cupcake build, but is that an incorrect assumption?
Or perhaps is it the case that I can only use JFUpdater to get 1.5 if I am currently running a rooted ADP build?
Thanks in advance for any clarification you could offer me.
.
The issue is that there's no JF1.5 build based on T-Mobile's US Cupcake image yet (as they've just barely started rolling it out to "regular" users).
You can upgrade to the JF1.5 Cupcake build for ADP (your G1 acts like an ADP) if you tell the JFUpdate tool to show a different "System Mod Version." You're on "T-Mobile G1 (US)" and the current 1.5 build is for "ADP 1." If you pick that and tell it to update again, it'll find the new 1.5 build.
Note that it's a "generic" Google build for the ADP w/JF's well-known and well-regarded mods; you will not have MyFaves or other T-Mobile specific stuff. The phone *will* work, though. If you go that route, make sure you update the radio image too for best results.
I'm figuring on waiting, myself; I'm eager to get a rooted T-Mobile US Cupcake image with JF's mods. It's handy being able to muck around with MyFaves settings on the phone.
I can't speak for JF, of course, but it shouldn't be too much longer before T-Mobile's US Cupcake image is unleashed on the public, snagged by somebody here on XDA, and modded for release via the JFUpdate tool.
OK. I get it now. I'll just wait until there's a JF-based US Cupcake image that's ready to download.
Thank you for explaining.
.
What i have: a brand new carrier unlocked samsung galaxy s7 sm-g930w8 - came with 7.0
What Id love to do: downgrade to 6.0.1 official touchwiz rom but rooted
What im reading: that the security patch is from february of 2018, which means the bootloader is too new, which means downgrading using odin wont work ( https://www.sammobile.com/forum/threads/36282-Does-Region-Matter )
... so what can i do? i bought this phone with the sole intention of downgrading, as ive seen that it is possible for that phone model (s7) in general
i hate the look of the newer OS. They took the touchwiz out of touchwiz which i loved, although mine is a rare opinion. I want the operation and exact feel of 6.0. the menus are simpler, the notifications area isnt completely stripped of features differing from total stock android. i hate having to pull down twice to see everything. I just really want that older look and feel, but all around, not just a theme.
is there anything i can do to either downgrade or fool the bootloader into letting me carry this out? is this a true limitation, or si that info i found false/old? and if I can downgrade, which build version should I use?
ive been looking here for versions
https://samsung-firmware.org/model/SM-G930W8/ but im not sure which region to go with, or if i can technically use any region
sammobile doesnt list that version anymore at all ( https://www.sammobile.com/firmwares/galaxy-s7/SM-G930W8/ )
https://mobiletech360.co/samsung-galaxy-s7-sm-g930w8-stock-firmware-rom-android-6-0-1-marshmallow/ there are a number of options here but unsure of the different numbers/builds. or if since its carrier unlocked, i could pick any?
I know most will think im silly for wanting to downgrade or caring that much about appearance, but silliness aside... is this even possible??
a while ago, i purchased an s5 mini, and downgraded that with no issues at all.... but its honestly been so long and i cant for the life of me remember the steps i took or if i needed to care about region codes or other numbers. but it did sucessfully work.... it was really built unwell/cheap, but it did work.... its also slower than my captivate glide which is still my current phone, until/if i can get this s7 working the way i desire.
any help and guidance is appreciated. If it is needed, ill be using it with a Koodo mobile sim.
well it is too new if its from DRAG or so onwards (those with U2/S2 in the file name) so no dice, you're stuck with 7.0 unless you want to upgrade to oreo. (and 7.0 firmwares prior to DRAG cant be downgraded to either, not that theres much point doing that)
btw this is the wrong forum to post this in
teddytsen said:
well it is too new if its from DRAG or so onwards (those with U2/S2 in the file name) so no dice, you're stuck with 7.0 unless you want to upgrade to oreo. (and 7.0 firmwares prior to DRAG cant be downgraded to either, not that theres much point doing that)
btw this is the wrong forum to post this in
Click to expand...
Click to collapse
But this is the forum about s7? I'm wanting to modify an s7?
Which part of the file name are you referring to? Which file?
I would have thought all s7's are made at the same time, and so released with the same overall software, but it all seems so complex now. I've seen s7's running 6.0.1 stock so in my mind it seems they should all be able to...
Not sure what you're referring to with drag either? Does that stand for something?
I'm really hoping this can work somehow, its the last flagship before the edge models which was why I got it, and I love Samsung software up until 7 and 8.
My mom has an s7 as well, not rooted or anything that's too complex for her, but she did the upgrade to 8 and it's still got all the same gross appearance factors that I don't like about version 7. I got excited when her phone wanted to upgrade, maybe they had fixed some of the grossness. But, nope. Wish they had included an option even for stock based or touchwiz based appearance and menus.
Sent from my [device_name] using XDA-Developers Legacy app
Pawprints1986 said:
But this is the forum about s7? I'm wanting to modify an s7?
Which part of the file name are you referring to? Which file?
I would have thought all s7's are made at the same time, and so released with the same overall software, but it all seems so complex now. I've seen s7's running 6.0.1 stock so in my mind it seems they should all be able to...
Not sure what you're referring to with drag either? Does that stand for something?
I'm really hoping this can work somehow, its the last flagship before the edge models which was why I got it, and I love Samsung software up until 7 and 8.
My mom has an s7 as well, not rooted or anything that's too complex for her, but she did the upgrade to 8 and it's still got all the same gross appearance factors that I don't like about version 7. I got excited when her phone wanted to upgrade, maybe they had fixed some of the grossness. But, nope. Wish they had included an option even for stock based or touchwiz based appearance and menus.
Click to expand...
Click to collapse
go into about phone and tell me the last 6 characters of your build number
(i was referring to the PDA file in a stock firmware zip)
(Also i meant this should be in Q&A section)
Hello,
I can understand you and also understand what you want but Samsung installed a downgrade lock in their bootloader in early 2018,
if you installed this version you can't go back to an older version, I think that was in February.
You can go back from a 6.2018 version to a 4.2018 version for example but not to a 1.2018 version!
If you have a version of for example 12.2017, you can also go back to a version of 2016, so you can also go back to Android 6.01,
if not you only have the last versions of Android 7 or update to Oreo.
I hope I could help.
teddytsen said:
go into about phone and tell me the last 6 characters of your build number
(i was referring to the PDA file in a stock firmware zip)
(Also i meant this should be in Q&A section)
Click to expand...
Click to collapse
the last of the build number and the last of the baseband version are the same. But i did take a screenshot of it when i was thinking rooting and changing would be no big thing. figured that would be easier. i purposely havent even hooked it up to wifi yet or anything, said no to anything non essential when i was setting it up... on the chance it was starting up in version 6, and i didnt want it upgrading on its own.
also why would they block downgrading? It seems if anything blocking upgrading would be the way to go, to stop people from updating their devices before official software is ready, not just samsung but any manufacturer. in my head it seems silly to even need to root anymore... someone always figures it out, and cell phone manufacturers must know it. it would be nice if it were included, sort of like developer options, where its hidden, but if you know what to look for its there, and if youre not that advanced youll never find it.
if the bootloader is in fact locked and that is the main prevention, has anyone ever successfully unlocked it before?
ETA: Ive done a bit more looking around and there is alot around about frp and making you sign in to a google account in order to reset.... i have *not* needed and havent signed into a google account on that device at all... does that mean a downgrade is still possible though odin? Or, are these 2 things in fact unrelated...
eta #2: Did a bit more searching around, and it seems to be that in order to root your device, in the process it must unlock the bootloader? If that is still the case, would i be able to then flash the marshmallow stock ROM? Thats what i was looking to do all along, sorry maybe i should have been more clear about my planned method initially. Its a bit more nerve wracking as it seems rooting itself has gotten a little more difficult with that dm verity thing... but I definitely want root no matter which version im running. Ive had root on all my devices and theres no way im going back to a locked down OS (cant remove microsoft stuff for example), i need to be able to declutter beyond what factory allows lol.
Pawprints1986 said:
the last of the build number and the last of the baseband version are the same. But i did take a screenshot of it when i was thinking rooting and changing would be no big thing. figured that would be easier. i purposely havent even hooked it up to wifi yet or anything, said no to anything non essential when i was setting it up... on the chance it was starting up in version 6, and i didnt want it upgrading on its own.
also why would they block downgrading? It seems if anything blocking upgrading would be the way to go, to stop people from updating their devices before official software is ready, not just samsung but any manufacturer. in my head it seems silly to even need to root anymore... someone always figures it out, and cell phone manufacturers must know it. it would be nice if it were included, sort of like developer options, where its hidden, but if you know what to look for its there, and if youre not that advanced youll never find it.
if the bootloader is in fact locked and that is the main prevention, has anyone ever successfully unlocked it before?
ETA: Ive done a bit more looking around and there is alot around about frp and making you sign in to a google account in order to reset.... i have *not* needed and havent signed into a google account on that device at all... does that mean a downgrade is still possible though odin? Or, are these 2 things in fact unrelated...
eta #2: Did a bit more searching around, and it seems to be that in order to root your device, in the process it must unlock the bootloader? If that is still the case, would i be able to then flash the marshmallow stock ROM? Thats what i was looking to do all along, sorry maybe i should have been more clear about my planned method initially. Its a bit more nerve wracking as it seems rooting itself has gotten a little more difficult with that dm verity thing... but I definitely want root no matter which version im running. Ive had root on all my devices and theres no way im going back to a locked down OS (cant remove microsoft stuff for example), i need to be able to declutter beyond what factory allows lol.
Click to expand...
Click to collapse
TL;DR
your bootloader is currently on version 3, and you cant downgrade to marshmallow
see that "U3BRB2"? that "U3" means your bootloader is on version 3. i assume the marshmallow firmwares use bootloaders pre-version 3 so you cant downgrade to firmwares using bootloaders with version 1 or 2. (this is how it works for F/FD models and im pretty sure samsung made it like that too for the W8 models)
eta 1) unrelated
eta 2) F/FD/W8/S/K/L variants (basically all the exynos models) have unlocked bootloaders. only SD variants have locked bootloaders so it's just your misconception
So, it's literally impossible? Has nobody ever figured out a way to downgrade or mod the bootloader itself? It seems to me the rom makers wouldn't stand for this at all and would figure out a way around it...
I can see an old bootloader can't run new software, but it seems much easier for newer bootloader to run older software, isn't it? You can buy a windows 7 pc and install Windows xp on it much easier than you could buy a windows XP PC and install Windows 7 on it... It's just boggling my mind a little
Sent from my [device_name] using XDA-Developers Legacy app
Pawprints1986 said:
So, it's literally impossible? Has nobody ever figured out a way to downgrade or mod the bootloader itself? It seems to me the rom makers wouldn't stand for this at all and would figure out a way around it...
I can see an old bootloader can't run new software, but it seems much easier for newer bootloader to run older software, isn't it? You can buy a windows 7 pc and install Windows xp on it much easier than you could buy a windows XP PC and install Windows 7 on it... It's just boggling my mind a little
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Off course you can downgrade to Marshmallow. To unlock the bootloader, enable OEM unlocking in devlopper options. After flash TWRP 3.1.0 for Herolte and wipe everything from the recovery. Install any 6.0 roms on XDA for G930F then flash Magisk 17.1 to root and you're done. You can't FRP if OEM unlocking in devlopper is enabled.
AoEKiller said:
Off course you can downgrade to Marshmallow. To unlock the bootloader, enable OEM unlocking in devlopper options. After flash TWRP 3.1.0 for Herolte and wipe everything from the recovery. Install any 6.0 roms on XDA for G930F then flash Magisk 17.1 to root and you're done. You can't FRP if OEM unlocking in devlopper is enabled.
Click to expand...
Click to collapse
You'll trip knox (which breaks features like secure folder, private mode, shealth and Sbrowser private mode) and lose the comfort of OTA updates if you do this tho. Not to mention that you can encounter signal reception problems because your flashed ROM is on marshmallow and your bl/cp is on Oreo or nougat. So I wouldn't advise this method as it may break so many things.