I've just updated my G1 to ADP 1.1 with help from the post "How-to- Root, Hack, and Flashing your G1/Dream Read first!!".
Everything worked perfectly, auto-rotate, multitouch and everything. But suddenly a pop-up asked me to update 1/2 updates. I agreed, and no problems afterwords. But after a while update 2/2 came, and after that I lost root access and the extra functions.
What did I do wrong? Shouldn't I agree to these updates? And do I have to go through the procedure "How-to- Root, Hack, and Flashing your G1/Dream Read first!!" all over again?
ampliz said:
What did I do wrong?
Click to expand...
Click to collapse
You accepted an OTA update.
hmmm.... new update???? what one? whats new? firmware #?
I don't know whats new, just that I lost all the good stuff..
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Is this the information you were looking for?
Strange.... it appears you have the JF build and a new kernal??? I'm on RC33 but my kernal is 2.6.25-01843-gfea26b0
EDIT: After looking into your kernal, it appears you simply have the ADP1 official build. Time to start over with flashing the NBH
U didnt lost root, have same firmware, just JF stuff is gone, just download ADP1.1h again rename it as update.zip und flash ist again...
McLin said:
U didnt lost root
Click to expand...
Click to collapse
He's right. HTC/Google are now sending out OTAs for ADP1 signed with the test keys. These updates will not take your root away, but you will occasionally have your /system normalized to the "canonical" ADP1 build (meaning a loss of the JF components, among things). Two easy solutions:
1. Install JF RCxx build.
-or-
2. Create your own crypto keys and replace the test keys with em.
Thanks for all the help!
I'm not so into making stuff myself to this device jet, making my own crypto keys, so the easiest solution for me is to repeat the last step in the procedure and flash ADP 1.1?
And not agree to any auto-updates in the future?
ADP Image from JF will still have enabled OTA cos you dont loose your root, by rc RF firmware its disabled, cos tmob will kill you root...
So ignore the update message, or build own keys...
I did install the original holiday update, and customie it to my stuff what I need... is another possibility
ampliz said:
Thanks for all the help!
I'm not so into making stuff myself to this device jet, making my own crypto keys, so the easiest solution for me is to repeat the last step in the procedure and flash ADP 1.1?
And not agree to any auto-updates in the future?
Click to expand...
Click to collapse
I can almost assure you that one day you will accidentally click Accept on an update dialog. I can't be sure if its the same as with the G1, but on the G1 update dialogs will keep popping up occasionally until you accept. At some point also, the update manager can be instructed to perform the update silently without your permission (no anecdotal cases of this occurring but the code is there to do it).
If you don't care about branding, the easiest way is simply to flash a JF RCxx build. The only thing that kind of irritates me about that solution is that every time the update manager pings the OTA server, it sends your imei in addition to the fingerprint.
So if I flash the phone to RC33 instead of ADP1.1 I wont have the problem with the update dialog? And still have root with possibility to auto-rotate, multitouch and use the phone as a wireless router for Internet access?
ampliz said:
So if I flash the phone to RC33 instead of ADP1.1 I wont have the problem with the update dialog? And still have root with possibility to auto-rotate, multitouch and use the phone as a wireless router for Internet access?
Click to expand...
Click to collapse
I have RC33 and have all of the above
HI, I'm posting in this thread because I see my problem is related to the one solved here, in fact I did update the phone from the version this user had:
I received yesterday a G1 I bought on eBay. When I received it I saw it was a Dev Phone 1 just like the one described in htc.com under the adp entry (sorry no external links):
In the terminal application I downloaded, the "su" command answered "#"
"about phone" said:
Model number: Android Dev Phone 1
firmware 1.1
Kernel 2.6.25-01845-g85d4f0d [email protected]#27
Baseband version: 62.33.20.08U_1.22.14.11
Build number: holiday_devphone-userdebug 1.1 UNLOCKED 130444 test-keys
I configured the internet access (spanish operator Movistar - phone is unlocked), a couple of minutes later a message tells me there is a new version of the system
Today checking "System Updates" I see a 40 something mb file with an update. I run it (I know - noob )
I'm no loger root, "su" command gives "su: permission denied" message
The new "about phone" says
Model number: Android Dev Phone 1
Firmware version 1.6
Baseband 62.505.20.17U_2.22.19.26I
Kernel: 2.6.29-00479-g3c7df37 [email protected] #19
Build number DRC83
If I turn the phone on using power + back or power + camera I get a rainbow-like screen saying:
DREA110 PVT 32B
HBOOT-0.95.0000
CPLD-4
RADIO-2.22.19.26I
Sep 2 2008
Serial 0
There's not much info about this version, maybe somebody could tell me what tutorial to follow in order to get root privileges again
Regards!
Do you have recovery tools like Amon RA,or cyanogen recovery ?
If you do, Can you go to console in recovery mod ?
If everything ok than the problem is only several file on your linux has false permission setting,
In your recovery console try:
chmod 6755 /system/bin/su
Or using adb
adb remount
adb shell
chmod 6755 /system/bin/su
Sent from my HTC Dream using XDA App
I had nothing installed as far as I know, can these recovery tools be installed now (without root privileges)?
Search the cyanogenmod wiki on the rooting process, which you need to do from the beginning.
cloverdale said:
Search the cyanogenmod wiki on the rooting process, which you need to do from the beginning.
Click to expand...
Click to collapse
As I am not root I have to use the G1 Dream tutorial, so I need to downgrade to RC29 (US) or RC7 (Europe).
I bought my phone on eBay from a Spanish guy but it is an Android dev phone 1. Should I use RC29 or RC7?
Moved to the Q&A section
Related
Firstly, I'm a G1 owner on tmobile in the UK. Love my G1, much prefer it to my Hermes although do miss the lack of decent sat nav...anyway...
I bought the phone new in the UK and over the last couple of days managed to root the phone and install various recovery images and various roms.
Now, I'm not sure how or why but I ended up downloading the following from http://developer.htc.com/adp.html#s3
I think I was following some instruction to upgrade from cupcake to donut. I make it sound like I know what I'm talking about!! yeah right!
signed-dream_devphone_userdebug-img-14721.zip (system image)
and
signed-dream_devphone_userdebug-ota-14721.zip (recovery image)
My phone is now telling me I have the following:
Model Number
Android Dev Phone 1
Firmware Version
1.6
Baseband version
62.50s.20.17H_2.22.19.26I
Kernel version
2.6.29-00479-g3c7df37
[email protected] #19
Build number
dream_devphone_userdebug 1.6 DRC83
14721 test-keys
If I boot in the the recovery menu it tells me:
Android system recovery <2e>
Use trackball to highlight;
click to select
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
My problem is, I no longer seem to have root on the phone and cant find a way to get root / lower the rc level to one where I can, or flash a new recovery image.
Can anyone help this newb?
Cheers..
Adrian.
u lost root. so ur now on the adp rom. all u need 2 do is follow the guide called stock to cyanogen. google it. n follow those step. theres already a thread for cyanogen 4.1.999 for ppl
here to make it more easier go here http://forum.xda-developers.com/showthread.php?t=563679
many thanks
I could manage the google search you know!
Thanks for your help guys, back up and running now on rooted CyanogenMod 4.1.99, phew!
yay
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
The answer is this: You DO have root, you just don't know how to use it.
adb shell.
There. You have root.
Want a "community"-type su command? Install it with adb.
[email protected] said:
Firstly, I'm a G1 owner on tmobile in the UK. Love my G1, much prefer it to my Hermes although do miss the lack of decent sat nav...anyway...
I bought the phone new in the UK and over the last couple of days managed to root the phone and install various recovery images and various roms.
Now, I'm not sure how or why but I ended up downloading the following from http://developer.htc.com/adp.html#s3
I think I was following some instruction to upgrade from cupcake to donut. I make it sound like I know what I'm talking about!! yeah right!
signed-dream_devphone_userdebug-img-14721.zip (system image)
and
signed-dream_devphone_userdebug-ota-14721.zip (recovery image)
My phone is now telling me I have the following:
Model Number
Android Dev Phone 1
Firmware Version
1.6
Baseband version
62.50s.20.17H_2.22.19.26I
Kernel version
2.6.29-00479-g3c7df37
[email protected] #19
Build number
dream_devphone_userdebug 1.6 DRC83
14721 test-keys
If I boot in the the recovery menu it tells me:
Android system recovery <2e>
Use trackball to highlight;
click to select
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe cache partition
My problem is, I no longer seem to have root on the phone and cant find a way to get root / lower the rc level to one where I can, or flash a new recovery image.
Can anyone help this newb?
Cheers..
Adrian.
Click to expand...
Click to collapse
HTC implemented security on their newer generation phones. This flag, called @secuflag, controls whether your phone has
it's NAND or flash unlocked. Most noticeably, S-ON (security on) will read-lock your /system and /recovery partition, to name a few. Also, secuflag controls whether zip files being flashed through recovery or fastboot, are signed by HTC.
The now notorious S-OFF (security off) will disable this NAND security.
Since we are unable to access the Radio NVRAM itself (where secuflag is stored), we turned our attention to HBOOT.
AlphaRev has patched HBOOT images for several phones, whereas the HTC Desire (GSM) was our first victim.
Soon to be supported devices:
HTC Legend GSM
HTC Aria GSM (Liberty)
HTC Wildfire GSM (Buzz)
The following patches were made:
First and foremost, the security flag is ignored. HBOOT now always thinks the phone is S-OFF.
Second, Fastboot extended commands are enabled. This is similar to engineering HBOOTS, these allow you to use commands like 'fastboot flash system system.img' (flashing a system image), or 'fastboot boot boot.img' (downloading and directly booting a kernel image and ramdisk).
Is there any risk involved?
Yes, there is. Flashing HBOOT will flash a critical part of your phone, if that gets corrupted, your phone WILL be bricked.
We do not accept any responsibility for bricked phones, even though we've attempted to make the actual flashing method as safe as possible.
If your phone no longer turns on anymore, please return to HTC for warranty purposes.
Should you still run this hack/program, you then hereby accept full responsibility.
So how does this work?
The image provided is an ISO image. You can either burn that on CD, and boot it. Instructions will be provided when you run the CD.
The actual tool is packaged in a Linux livecd, to ensure maximum compatibility.
On a sidenote: yes, you should be able to run this in VMWare or Virtualbox, as long as you enable the USB device to be routed to the livecd running.
Will my phone stay S-OFF forever?
Yes and no. As soon as you decide to flash a stock RUU that has a HBOOT update in it, this hacked HBOOT will be overwritten.
You do have the option to remove the HBOOT update from the rom.zip inside the RUU. Since your phone no longer checks signatures, you could easily do that.
Also, you then still have the option to flash custom recovery, or different kernels using the fastboot functions described above (fastboot flash, et al).
http://alpharev.shadowchild.nl/
http://forum.xda-developers.com/showthread.php?t=794314&page=5 (Desire thread)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NIIIICE *cheer*
I cant wait for this to arrive.
That are awesome news
Sent from my HTC Wildfire using XDA App
That means we can flash new roms (or single images) via `adb fastboot [...]`?
Great news tho.
Sent from my HTC Wildfire using XDA App
nice, keepup good work.
p.s. i hate word "soon", hope its soon not later
Just tryd this on my HTC Desire.. (so dont try it on wildfire yet)
Im soooooooo happy right now
Agghh, I loaded up the RUU with the .25 image, and now im locked in s-on. Can't wait for this to come out =) no more HTC stock images for me =)
Wow
Thanx to IEF @ alpharev my wildfire is now s-off!!!!!! damn so nice... thanx man!
Is it out for the wildfire then?
Nice one.
what version of hboot is suported? lots of peopel flashed froyo ruu as i see in treads
updated first post
Very nice, were do i get it from?
you lucky sob
whats the issues with having nand security off?
and what real benefits will we see from this?
Sorry for asking maybe quite numb questions
Nice leaf!
Is it out officially for the wildfire yet Danne?
Phinxy said:
Nice leaf!
Click to expand...
Click to collapse
You know now when autumn have came alot of leaf is flying around in the air
tigger69 said:
Is it out officially for the wildfire yet Danne?
Click to expand...
Click to collapse
Not yet but now when its proven it wont be long
Good news to see it working
Thank You. Thank You. Thank You =)
I have a smile on my dial, was kickin meself last week when i put on the RUU_Buzz_HTC_WWE_1.25.405.1_Radio_13.45.55.24_3.35.15.31_release_142189_signed rom and found I could no longer flash stuff.
Gonna make sure I never flash a boot image again once this is done.
Isn't this what Unrevoked Forever does?
This method is from XDA智能手机网(xda.cn)
(updated 20th, september, finally can put all the instruction picture in this post)
Non-offical receovery, for flashing only.
version: 4.0.1.4
language: English
Editor: Qiu Long (from xda.cn)
Preparation:
1. Salsa
2. must s-off
3. download PH11IMG.zip and root.zip, save in root of your sd card
Start recovery:
1. Shut off the phone, then push volume low and power enter into Hboot
2. Get into Hboot, will show a message if need update or not. choose yes or no.
3. Push volume up start flash
4. According to instruction reboot then finish recovery.
Start root (for this step please make sure your phone is already flashed receovery):
1. Shut off the phone, then push volume low and power enter into Hboot
2. By using volume control choose recovery and enter into recovery
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3. By using volume control choose install zip from sdcard
4. Then choose zip from sdcard then find the location you savied root.zip file.
5. Find root.zip in your sdcard
6. Confirm one more time yes, install root.zip
7. Flashing start
8. Finished flash will show the screen as below
9. Choose Go Back, then reboot. Root is done.
Note:
When confirm a selection, it's better use camera button then power.
-----------------------------------
Update information (9.28)
---Can not receovery, shows:
SD CHECKING..
Loading…[PH11DIAG.zip]
NO image!
Loading…[PH1DIAG.nbh]
No image or wrong image
Loading…[PH11IMG.zip]
Parsing…[PH11IMG.zip]
--- Can not recovery, stoped on HTC screen
★ Open recovery zip file, find txt file. Find HTC_xxx, change into HTC_11111111 in this txt file, save and replace the original one.
Take this method have a try. If still have problem with the recovery, please let me know.
tested out and installed both, this has allowed me to root an o2 stock rom
im stuck on Hboot
no image or wrong image!
anyone can help me?
gdavies08 said:
tested out and installed both, this has allowed me to root an o2 stock rom
Click to expand...
Click to collapse
you use your stock rom or the attached image?
Sent from my SK17i using XDA Premium App
is this a confimed rooting? need to get s-off now lol
i am using a stock 02 rom with the custom recovery, after i installed the root via the install zip from sd card it had managed to root my phone, Since then i have been able to install busybox and a few other root only tools
Woohoo. Ok u want more space? Links2sd will work now lol.
Maybe a bit off a chose, but I think using tYour guide, the xtc click guide and this guys guide in one. Break it down to simple terms. I just need to figure out the xtc clip part and I'm off!
I take it u know how to do links 2 ad and the ext2 partitions?
sent from my HTC Salsa via Tapatalk
yeah am looking at installing linux on this bad boy at the mo
to be fair id be happy with full root access, allowing me to rip out the **** bits, install a partition and start using my sd for space.
i will start playing more with roms once more become avalible lol, still playing with my xperia x8 on gdx lol.
if i can get the clip to do its job and root via the guide given i will start experimenting with other options.
if i can get this rooted i will start on making a guide on the lot!
think i will put a complete guide to the clip at some point when i do another phone as then i can full on photo each step etc
gdavies08 said:
think i will put a complete guide to the clip at some point when i do another phone as then i can full on photo each step etc
Click to expand...
Click to collapse
ok cool, need any help just ask away
gdavies08 said:
tested out and installed both, this has allowed me to root an o2 stock rom
Click to expand...
Click to collapse
hey,
am a newbie here , what exactly do you mean by an o2 stock rom?
I have a HTC Salsa which i bought at a store in india... could i use this root???
and how is this different from the tools like revolutionary.io
Thanks a ton for the help
ok getting stuck now!
xtc setup, gold card created and inserted, sim thingy inserted.
hboot with auto diag ph11diag comes up
recives zip info screen open file fail!
reflash or DIAG
select diag
waiting for gsm
clean s58 data
hit fb button then power
10 secs later phone boots up again.
go back to hboot and still s-on
tried no ends of times now!
roopak.v said:
hey,
am a newbie here , what exactly do you mean by an o2 stock rom?
I have a HTC Salsa which i bought at a store in india... could i use this root???
and how is this different from the tools like revolutionary.io
Thanks a ton for the help
Click to expand...
Click to collapse
An o2 stock rom is the rom that comes delivered on the phone from an o2 store, o2 been the network the phone was purchased from, My phone is the uk version but the tools throughout this section can be used on any htc salsa. Hope that helps out
BigBearEvo said:
ok getting stuck now!
xtc setup, gold card created and inserted, sim thingy inserted.
hboot with auto diag ph11diag comes up
recives zip info screen open file fail!
reflash or DIAG
select diag
waiting for gsm
clean s58 data
hit fb button then power
10 secs later phone boots up again.
go back to hboot and still s-on
tried no ends of times now!
Click to expand...
Click to collapse
try the reflash option instead of going straight to dev option, also do you have the sim card cable the right way round with it coming up open file fail
Tried relashing, got secruity still on and had to take battery out to reboot it. In the pic shown my finger points to the cable sim I used.
Tried all the options available in the screens and every time file open error. I assume that's the key part of it. That needs to be read in order to access the s-off.
I've even tried the other cable which fits..the non angled one, same thing again.
Cheers
Scotty
Sent from my HTC Salsa C510e using Tapatalk
I used the middle one due to the fact you could still close the battery door too
I tried that one first lol, found the angled one made the battery flap close alot easier lol
Sent from my HTC Salsa C510e using Tapatalk
Iucken said:
im stuck on Hboot
no image or wrong image!
anyone can help me?
Click to expand...
Click to collapse
Just updated the install instruction, added more detials. Don't know if there could be any help.
33poison said:
Just updated the install instruction, added more detials. Don't know if there could be any help.
Click to expand...
Click to collapse
Its a great help! But u need s-off first if u want root. I have to get the xtc clip to s-off first lol
Sent from my HTC Salsa C510e using Tapatalk
33poison said:
This method is from XDA智能手机网(xda.cn)
(updated 20th, september, finally can put all the instruction picture in this post)
Non-offical receovery, for flashing only.
version: 4.0.1.4
language: English
Editor: Qiu Long (from xda.cn)
Preparation:
1. Salsa
2. must s-off
3. download PH11IMG.zip and root.zip, save in root of your sd card
Start recovery:
1. Shut off the phone, then push volume low and power enter into Hboot
2. Get into Hboot, will show a message if need update or not. choose yes or no. 3. Push volume up start flash
4. According to instruction reboot then finish recovery.
------ deleted
Click to expand...
Click to collapse
So the PH11IMG.zip file is actually a CWM Recovery? I will try this once I S-OFF my Salsa.
And, have you try any a2sd script after got root?
Hi all! I registerd now on forum but i'm an old noob reader of the forum. I
I bought Captivate(AT&T) on ebay and had Froyo 2.2 installed. I tryed to flash and root it to CYNOGENMOD with this GUIDE: wiki.cyanogenmod.com/wiki/Samsung_Captivate:_Full_Update_Guide
I did everything as written on thad guide but the phone continued to reboot and reboot and reboot. Now I don't even know what have I done but the phone starts with AT&T LOGO and than blocks with Samsung SGH i897 LOGO.
When i push volume buttons and start button it goes on CLOCKWORKMODRECOVERY.
Anyone can help me? I think i'm in big problem isn'it? PLEASE SOMEONE HELP!
(sorry for bad english)
alexmr89 said:
Hi all! I registerd now on forum but i'm an old noob reader of the forum. I
I bought Captivate(AT&T) on ebay and had Froyo 2.2 installed. I tryed to flash and root it to CYNOGENMOD with this GUIDE: wiki.cyanogenmod.com/wiki/Samsung_Captivate:_Full_Update_Guide
I did everything as written on thad guide but the phone continued to reboot and reboot and reboot. Now I don't even know what have I done but the phone starts with AT&T LOGO and than blocks with Samsung SGH i897 LOGO.
When i push volume buttons and start button it goes on CLOCKWORKMODRECOVERY.
Anyone can help me? I think i'm in big problem isn'it? PLEASE SOMEONE HELP!
(sorry for bad english)
Click to expand...
Click to collapse
Boot loop often happens and means you can't boot into the rom....it's called soft bricked. If you have recovery and download mode still active your safe.
1-Did you check you got the right files ?
2-Did you check the md5sum of the files (if available) to make sure your download is not corrupted.
3-Did you download and flash the proper cwm and/or kernel
4-You missed something in the process. (Recheck #[email protected])
silvertag said:
Boot loop often happens and means you can't boot into the rom....it's called soft bricked. If you have recovery and download mode still active your safe.
1-Did you check you got the right files ?
2-Did you check the md5sum of the files (if available) to make sure your download is not corrupted.
3-Did you download and flash the proper cwm and/or kernel
4-You missed something in the process. (Recheck #[email protected])
Click to expand...
Click to collapse
Hi thank you very much for answering. I managed to restart it by flashing a new rom downloaded online, a Froyo 2.2. As I am a little idiot if I write down infos about my firmware would you gently link me to a guide or tell me what should I do to upgrade in order do not do any mistake again? Anyway phone is from At&T but I'd like to unlock operator in order tu use my Italian sim.(before i screwed it up it was unlocked, as i bought it USED from ebay.)
Anyway these are the infos:
Firmware version 2.2
Baseband version I897UCJI6
Kernel version [email protected] #1
Build number:Froyo.UCJI6.
THANK YOU VERY MUCH. Hope to hear from you
PS: I used this to restore it I897UCJI6-OCD-REV02-Low-designgears.exe and ODIN, if this has any importance!
It should be posted in the OP or there should be a link to sufficient installation instructions in the OP of whatever Rom you would like to flash.
And no need to start a thread in the General and same exact thread in Q & A.
NO need to double post.
Help will be given even with one thread started.
Ok i won't crosspost, I did it because I really need help. Anyway my question.is: now that i have installed this 2.2froyo rom,as i don't know if phone is rooted or not CAN I install a superoneclick 2.3 gingerbread or should i do something first. Will this also remove sim operator lock? Please someone answer
Thanks everybody for help!
If u have root then u should have the "Superuser app"
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
or View attachment 854464, but Not this in ur app drawer. Or download a free app that requires root and test and see that way.
To go to a Gingerbread Rom from the Froyo 2.2 that u currently are running, u can use one of the One Clicks GB with Bootloaders in the Stickied One Click Thread in the Development Forum.
You have to have the GB Bootloaders in order to run a Gingerbread Rom, but once u have the Bootloaders there is not any need in flashing any bootloaders in the future, because the GB Bootloaders are backwards compatible.
There is risk in flashing bootloaders, so be sure u have a good micro usb to usb cable connection, preferably use a laptop so u don't loose power mid flash, remove all babies, animals, etc. from the room, so the cable does not get "accidentally" yanked during the flash.
Be sure u know what u r doing and then proceed.
Hello, i'm not an expert, i just wanted to unlock my new s10, like i did on my old devices i just used Unlock.io for that.
i followed the instructions here
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and now it looks like i am not able to receive OTA Updates.
It says "Your current software version isn't supported. Visit a service centre"
I dont want to loose my warranty or Knox functionality, i just wanted to get my phone unlocked.
Can anyone help me out here what i should do now? The Phone is from the Provider "A1" (Austria)
Here a Picture of the Device with the Error Message and Software Version
What version of phone do you have 973U? What carrier do you have?
highaltitude said:
What version of phone do you have 973U? What carrier do you have?
Click to expand...
Click to collapse
G973F
A1 Austria
Proxolin said:
Hello, i'm not an expert, i just wanted to unlock my new s10, like i did on my old devices i just used Unlock.io for that.
i followed the instructions here
and now it looks like i am not able to receive OTA Updates.
It says "Your current software version isn't supported. Visit a service centre"
I dont want to loose my warranty or Knox functionality, i just wanted to get my phone unlocked.
Can anyone help me out here what i should do now? The Phone is from the Provider "A1" (Austria)
Click to expand...
Click to collapse
There's another similar post that you may find helpful.also might be try asking unlock io and see what they say. Let us know.
https://www.reddit.com/r/galaxys10/...date/?utm_medium=android_app&utm_source=share
Sent from my SM-G975U using Tapatalk
Proxolin said:
Hello, i'm not an expert, i just wanted to unlock my new s10, like i did on my old devices i just used Unlock.io for that.
i followed the instructions here
and now it looks like i am not able to receive OTA Updates.
It says "Your current software version isn't supported. Visit a service centre"
I dont want to loose my warranty or Knox functionality, i just wanted to get my phone unlocked.
Can anyone help me out here what i should do now? The Phone is from the Provider "A1" (Austria)
Click to expand...
Click to collapse
Once unlocked its permanent. Back up phone and do hard reset. Use the key combo not the option from Setting menu. If that doesn't solve it then use Emergency software repair ( Samsung Switch) on PC .
i already tried a hard reset, did not solve the problem.
i will try smart switch and let you know
Rexton270 said:
Once unlocked its permanent. Back up phone and do hard reset. Use the key combo not the option from Setting menu. If that doesn't solve it then use Emergency software repair ( Samsung Switch) on PC .
Click to expand...
Click to collapse
ok i tried to use samsung switch, first of all the tab "Device Initialization" is missing in the latest version of this software, i tried to use an older version, here the tab Device Initialization still was here but when i type in my Model Number and SrNumber it Says:
"SM-G973F" does not support Initializing. Please contact a Service Centre
do i have to use ODIN now??
i guess i just will wait until a new update will come out and try to update with Smart Switch
Proxolin said:
ok i tried to use samsung switch, first of all the tab "Device Initialization" is missing in the latest version of this software, i tried to use an older version, here the tab Device Initialization still was here but when i type in my Model Number and SrNumber it Says:
"SM-G973F" does not support Initializing. Please contact a Service Centre
do i have to use ODIN now??
i guess i just will wait until a new update will come out and try to update with Smart Switch
Click to expand...
Click to collapse
You can reflash the fw with Odin. Flash the version you had before the "unlock ". I think they are messing with some version of firmware...
Rexton270 said:
You can reflash the fw with Odin. Flash the version you had before the "unlock ". I think they are messing with some version of firmware...
Click to expand...
Click to collapse
Very close.
Bare with me as it's been a moment since I've worked with these tools:
Most 'instant' unlocks, done via USB over TCP/IP, tend to alter one of the device's primary certificates to allow for an 'instant unlock'.
If, and when, one of these certificates is replaced, it alters the chain of trust required by the device.
So when the device goes looking for an update, the update server acknowledges the request but sends back a query. In this query, and depending on the model, the update server looking for several variables and these must ALL match. Seeing as one of the primary certificates has changed, the result expected by the server isn't matched and, as such, it doesn't allow for an update.
@Rexton270 is correct in that you should replace the firmware with the same (and failing that, a newer version if possible). AFTER you flashed the new update, follow these steps:
https://www.verizonwireless.com/support/knowledge-base-222931/
(I know you don't have a Verizon device but the steps are the same)
Please keep us posted.
AHE_XDA said:
Very close.
Bare with me as it's been a moment since I've worked with these tools:
Most 'instant' unlocks, done via USB over TCP/IP, tend to alter one of the device's primary certificates to allow for an 'instant unlock'.
If, and when, one of these certificates is replaced, it alters the chain of trust required by the device.
So when the device goes looking for an update, the update server acknowledges the request but sends back a query. In this query, and depending on the model, the update server looking for several variables and these must ALL match. Seeing as one of the primary certificates has changed, the result expected by the server isn't matched and, as such, it doesn't allow for an update.
@Rexton270 is correct in that you should replace the firmware with the same (and failing that, a newer version if possible). AFTER you flashed the new update, follow these steps:
https://www.verizonwireless.com/support/knowledge-base-222931/
(I know you don't have a Verizon device but the steps are the same)
Please keep us posted.
Click to expand...
Click to collapse
thank you for that explanation.
i will first try to update the phone with smart switch as soon as there is a newer version for my phone, atm it says im up to date (i hope that is true) maybe it solves itself when i start an update with smart switch, if not i will follow your steps
thank you very much.
because there was still no update in samsung smart switch i flashed it with odin.
problem solved.
thank you.
for other users: if you want to unlock your phone, use the samsung database instead of the cheaper version.....
Excellent news. Glad to hear it all worked out.