Something I just noticed was my SGS2 shows an unknown serial number when looking at the phone info. The IMEI is correct, but not the s/n field.
Is this the usual thing to see when running custom ROMs? Does that affect anything with the Android market, etc?
No it says the same thing on mine shouldnt effect anything
Sent from my SAMSUNG-SGH-I777 using XDA
Same here. Not an issue in my opinion.
Sent from my SGH-I777 using xda premium
I'm with the OP.
This shows the same even on my leak.
Sent from my SAMSUNG-SGH-I777 using Tapatalk 2
Thanks everyone!
Sengfeng said:
Something I just noticed was my SGS2 shows an unknown serial number when looking at the phone info. The IMEI is correct, but not the s/n field.
Is this the usual thing to see when running custom ROMs? Does that affect anything with the Android market, etc?
Click to expand...
Click to collapse
If you are running ICS then you must install ICS bootloader and it will appear back.
andreivibefm said:
If you are running ICS then you must install ICS bootloader and it will appear back.
Click to expand...
Click to collapse
How do I do this?
Because I want to ship my phone back to AT&T for a warranty replacement and my serial # is unknown which I think would be a problem.
slatestud said:
How do I do this?
Because I want to ship my phone back to AT&T for a warranty replacement and my serial # is unknown which I think would be a problem.
Click to expand...
Click to collapse
Shouldn't you revert it back to stock first before sending it back to AT&T?
Wing2468 said:
Shouldn't you revert it back to stock first before sending it back to AT&T?
Click to expand...
Click to collapse
Yeah I already did. I I just flashed stock ICS ucle5 and also reset the flash counter. I was about to wrap it up for shipping when I saw the unknown serial #.
slatestud said:
Yeah I already did. I I just flashed stock ICS ucle5 and also reset the flash counter. I was about to wrap it up for shipping when I saw the unknown serial #.
Click to expand...
Click to collapse
Have you tried to revert it back to GB instead of ICS? If your phone originally came with GB, you should give it a try.
Wing2468 said:
Have you tried to revert it back to GB instead of ICS? If your phone originally came with GB, you should give it a try.
Click to expand...
Click to collapse
I will give it a try and report back. I'm just gonna flash uckh7 stock root with Odin right?
Didn't work. Couldn't get past the setup wizard because it kept glitching
I am out of ideas now or you may try what andreivibefm suggested to install an ICS bootloader. But as far as I have read so far from the net, it isn't recommended. You have to be extra careful for flashing a bootloader. Sorry can't help you here and good luck!
I actually finally got GB uckh7 on my phone working and I don't think the serial number is even available in the settings. The only way to read the serial number is to look at the sticker behind the battery.
All in all this works and I will ship tomorrow! Thanks!
I'm also with the OP. My phone also shows an unknown serial number. No big deal, but it would be interesting to know what causes this... Could this somehow have been caused by a previous ROM or kernel we've had on our phones, or must it be somehow caused by the current ROM or kernel?
Sent from my SGH-I777 using xda app-developers app
slatestud said:
I actually finally got GB uckh7 on my phone working and I don't think the serial number is even available in the settings. The only way to read the serial number is to look at the sticker behind the battery.
All in all this works and I will ship tomorrow! Thanks!
Click to expand...
Click to collapse
I started with uk6 then rooted and flashed a few roms, went back to stock uk7 and went for the ics kies update and just check for my serial number and saw this
{
"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"
}
Sent from my SAMSUNG-SGH-I777 using xda app-developers app
bdpyo said:
I started with uk6 then rooted and flashed a few roms, went back to stock uk7 and went for the ics kies update and just check for my serial number and saw this
Sent from my SAMSUNG-SGH-I777 using xda app-developers app
Click to expand...
Click to collapse
Yeah the general consensus is that on ICS the the S/N is unknown
Sent from my HTC One X using xda app-developers app
The kies UCLE5 release that can be downloaded from SamMobile Firmware or Samsung Updates contains boot.bin (but not sbl.bin). I wondered why that was included in the distribution. I left the boot.bin out when I packaged up the UCLE5 Stock plus Root package. I could make boot.bin into a standalone tar if anyone wants to try flashing it to see if it corrects the serial number issue. At your own risk, of course.
creepyncrawly said:
The kies UCLE5 release that can be downloaded from SamMobile Firmware or Samsung Updates contains boot.bin (but not sbl.bin). I wondered why that was included in the distribution. I left the boot.bin out when I packaged up the UCLE5 Stock plus Root package. I could make boot.bin into a standalone tar if anyone wants to try flashing it to see if it corrects the serial number issue. At your own risk, of course.
Click to expand...
Click to collapse
I maybe interested in trying it, you just have to agree to buy my bricked device at a fair price.
Sent from my SAMSUNG-SGH-I777 using xda app-developers app
Related
Now that rooting is possible, although not a one-click experience - how many of you have rooted, what were the reasons, and what root access apps have you installed?
rooted, mainly for Titanium Backup but at least it's prepped and ready if anything else crops up!
I dont really understand what rooting does.. some one care to explain?
Thanks
RedBlueGreen said:
I dont really understand what rooting does.. some one care to explain?
Thanks
Click to expand...
Click to collapse
It gives you full access to all the information on your phone. It lets you back up apps and data to the SD card, which isn't possible with default security settings.
In essence, it's like getting administrator access to your computer, or "root" in linux, hence the name
Hoping to get mine tomorrow. I won't be rooting yet since there isnt anything released yet worth rooting for. And... I don't suppose I'll need TB just yet since I won't be messing with the phone SINCE nothing worth messing around with is available yet. Also I'll probably wait for a 1 click root or till something worth rooting comes along, whichever happens first.
shabs52 said:
Hoping to get mine tomorrow. I won't be rooting yet since there isnt anything released yet worth rooting for. And... I don't suppose I'll need TB just yet since I won't be messing with the phone SINCE nothing worth messing around with is available yet. Also I'll probably wait for a 1 click root or till something worth rooting comes along, whichever happens first.
Click to expand...
Click to collapse
The root method is virtually one click now CF wrote a guide for it...
Also, consider mine rooted, even though it's not here yet
I did it to get rid of all of the Samsung crapware that the phone came with.
I'd do the same with any Android device, regardless of manufacturer.
Do you loose warranty if you perform rooting?
Sent from my Milestone using XDA App
Raymond77 said:
I did it to get rid of all of the Samsung crapware that the phone came with.
Click to expand...
Click to collapse
+1
Sent from my GT-I9100 using XDA App
sakazulu said:
Do you loose warranty if you perform rooting?
Click to expand...
Click to collapse
Usually you can revert to stock firmware but the answer is yes
Sent from my GT-I9100 using XDA App
pulser_g2 said:
The root method is virtually one click now CF wrote a guide for it...
Click to expand...
Click to collapse
Where is this easy guide?
AaronUK said:
Where is this easy guide?
Click to expand...
Click to collapse
Development section .
Works only flaw is the yellow triangle at boot .
jje
Raymond77 said:
I did it to get rid of all of the Samsung crapware that the phone came with.
I'd do the same with any Android device, regardless of manufacturer.
Click to expand...
Click to collapse
What version did you use? And can it be used on a O2 PAYG and will there be a big yellow /!\ ?
Thanks.
JJEgan said:
Development section .
Works only flaw is the yellow triangle at boot .
jje
Click to expand...
Click to collapse
after you've confirmed you have root, you can flash back just the official kernel and the yellow triangle will disappear and root will still work....
nah don't plan to if i need to will use my htc hd2 dual boot with 2.3.3 on it
Don't have a reason to root yet.
Rooted this morning so I could start using Root file explorer, Titanium Backup, and get rid of ads.
beggin said:
Don't have a reason to root yet.
Click to expand...
Click to collapse
You couldn't have this
{
"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"
}
Sent from my GT-I9100 using XDA App
nightranger73 said:
You couldn't have this
Sent from my GT-I9100 using XDA App
Click to expand...
Click to collapse
How did you do that?
Sent from my GT-I9100 using Tapatalk
AaronUK said:
What version did you use? And can it be used on a O2 PAYG and will there be a big yellow /!\ ?
Thanks.
Click to expand...
Click to collapse
You can remove the big yellow thing and the download mode counter using a USB jig
http://www.androidpolice.com/2012/0...ndwich-builds-for-its-phones-purpose-unknown/
According to P3droid, a number of Motorola devices running Android 4.0+ have been imbued with a new feature you might not have noticed: a visual root checker. It's present on the RAZR, RAZR MAXX, DROID 4, and test builds of the Bionic. It operates rather simply. Once a phone is rooted, somewhere in permanent memory, a status change is written that displays in the phone's recovery menu. It works as follows: "1/1" means currently rooted, "0/0" means never rooted, and "0/1" means not presently rooted, but rooted at some point in the past. There is no way to reset this check, at present.
Click to expand...
Click to collapse
{
"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"
}
You can also get it to display "2/1" - though we're not sure what this means (possibly running non-stock code?).
Click to expand...
Click to collapse
The more nefarious theory is that Motorola's warranty service employees will use this to deny repair or replacement service to defective but previously-tinkered-with phones. It could also result in the buck stopping at the carrier store, where a representative could quickly and easily verify if a subscriber has voided their warranty. Will it be used this way? At carrier stores, I'd say it's pretty likely. But if you send your phone to Moto for service on something that clearly isn't a result of tampering with the phone, I'm not so sure they'd care. Especially under the new Google regime.
Click to expand...
Click to collapse
oh motorola how good you treat us...this is a great alternative to actually unlocking our bootloader! thanks! /sarcasm
i actually have 2/1 maybe because im using bootmenu and have rooted my device twice
just reboot into stock recovery and see for yourself!
omg.... could anyone please tell me why do I even keep this phone??? why do I let motorola to treat me like an idiot for the money I paid them??\
btw, I am proud for my 2/1 !
lol. I am sure flashing the official sbf will fix this.
haha here is a comment from androidpolice
I have qe 1/1, and I'm NOT rooted. So, FAIL?
Click to expand...
Click to collapse
poor fellow
romdroid. said:
lol. I am sure flashing the official sbf will fix this.
Click to expand...
Click to collapse
would be interesting to see someone try this out!
let's hope the root counter is not an e-fuse :S
pseudoheld said:
would be interesting to see someone try this out!
Click to expand...
Click to collapse
I don't believe it will work as in case you can wipe its data by simple sbf the checker will be pointless....
pseudoheld said:
would be interesting to see someone try this out!
let's hope the root counter is not an e-fuse :S
Click to expand...
Click to collapse
yes I cant because I have just flashed it, maybe someone else can check it. But I think it restore the phone to 100% stock. And if that guy in the comments never rooted his phone and still get 1/1, is motorola going to say he tampered with the software when he didnt? They need to check up their ****ing security routines stupid dumb****s
The 2/1 image on AP was my device - no idea why though. I've definitely rooted my device more than twice (probably along the lines of a dozen times!) and i'm running the stock .41 en.eu ROM.
Any other thoughts on the 2/1 statement?
adaimespechip said:
The 2/1 image on AP was my device - no idea why though. I've definitely rooted my device more than twice (probably along the lines of a dozen times!) and i'm running the stock .41 en.eu ROM.
Any other thoughts on the 2/1 statement?
Click to expand...
Click to collapse
maybe if you flashed a custom rom it goes from 1/1 (being stock rom rooted) to 2/1 (custom rom rooted)?
just guessing though.
from first reports however it seems like the indicator is pretty wonky.
a guy in a german forum i frequent has 1/1 even though he now is unrooted again.
pseudoheld said:
maybe if you flashed a custom rom it goes from 1/1 (being stock rom rooted) to 2/1 (custom rom rooted)?
just guessing though.
from first reports however it seems like the indicator is pretty wonky.
a guy in a german forum i frequent has 1/1 even though he now is unrooted again.
Click to expand...
Click to collapse
I don't use custom ROMs really, I stick to stock roms and just root it. I flashed the STOCK .41 rom via RSD and then rooted, I didn't check to see what the status was prior to rooting, however.
adaimespechip said:
I don't use custom ROMs really, I stick to stock roms and just root it. I flashed the STOCK .41 rom via RSD and then rooted, I didn't check to see what the status was prior to rooting, however.
Click to expand...
Click to collapse
i think thats one of the problems we will have.
what we need is someone with a brand new device who can go through some steps and check how the root checker reacts.
just root a stock rom.
flash a custom rom
reflash stock
etc.
I think this whole story is a made-up paranoid uneducated guess.
I've just totally un-rooted and 2/1 is still showing, rerooted and again, showing 2/1
I'll reflash via RSD this evening and I assume, it will still show 2/1 even though the flashed build is un-rooted.
Hey Moto, if you would just unlock the bootloaders like you said you would we wouldn't being playing these games!
I think you can use fastboot flash recovery.img to reset counter if they really recorded root counts. I'm not sure though. I've got 2/1 on my RAZR. Anyway, my RAZR is almost out of warranty. So I wouldn't care about that count.
Sent from my XT910 using xda app-developers app
blisslove said:
I think you can use fastboot flash recovery.img to reset counter if they really recorded root counts. I'm not sure though. I've got 2/1 on my RAZR. Anyway, my RAZR is almost out of warranty. So I wouldn't care about that count.
Sent from my XT910 using xda app-developers app
Click to expand...
Click to collapse
That's a really good point! Could anyone try this out please?
Edit: surely flashing the entire sbf via RSD will have the same effect though?
I don't think RSD would fix it...i heard it was independent of anything to do with flashing. That's just an idea though.
Sent from my DROID RAZR using xda premium
Well according to OP, Motorola started to implement it on ICS. If we can refresh from GB boot, system, CDROM and recover images manually and flash ICS OTA again, it would reset the counter i think. I might be wrong.
Sent from my XT910 using xda app-developers app
i never ever rooted my new rarz maxx ....neither i flashed official or unofficial rom via rsd lite nd still it showing qe 2/1 but i do want to mention when i bought razr maxx it was on gingerbread rom 2.3.6 and when i checked for update it showed its up to date but on all websites official ics has come ....so i checked through motorola update checker still showing phone UTD ....so i called service center and asked them about ICS & they said ics is available bring phone to service center and v will update ur phone nd i think they flash ICS through rsd lite thats y its showing qe 2/1??
I've got 2.3.5 stock rooted and still got qe 1/1 on recovery what's the fuss with ICS only?
coniliakis said:
I've got 2.3.5 stock rooted and still got qe 1/1 on recovery what's the fuss with ICS only?
Click to expand...
Click to collapse
so maybe this is all wrong after all....
i just copied the news thought someone actually checked up on it already but by the looks of it it seems either totally random or to have nothing to do with being rooted or not....
I am running stock asia retail ICS and rooted (and once only), but it shows 2/1 instead of 1/1
so..i believe it is not really a root checker
I have previously rooted my 3uk branded phone then flashed the latest (at the time) UK unbranded official software.
Now my phone keeps telling me they are no updates available, but as we all know, jelly bean is now available here in the UK for unbranded handsets.
Is something wrong? Please look at my screen shots for software version, csc, baseband etc and let me know if they is some reason why I am not getting the OTA update.
Thanks for your time,
{
"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"
}
bigOliver
Sent from my GT-I9300 using Tapatalk 2
No replies yet
This morning I tried installing jelly bean via kies but my phone is not connecting to it. I guess this relates to the same issue? Any ideas anyone? Please, I really want the upgrade
Thanks,
BigOliver
Sent from a forum app on my phone
Read the ten thousand odd identical posts or use CHECKFUS to download firmware for 3UK and flash via Odin .
JJEgan said:
Read the ten thousand odd identical posts or use CHECKFUS to download firmware for 3UK and flash via Odin .
Click to expand...
Click to collapse
Sorry if this is a duplicate post, please if you have seen another post with the answer to my question I'd really appreciate it. I still don't know why my phone won't connect to kies or why my phone says they is no update available.
Thanks in advance,
Oliver
Ps I want to stay unbranded, so, do I really need to upgrade from unbranded ics to jb 3uk?
Cheers again.
Sent from a forum app on my phone
I'm pretty much still a noob so don't take me too seriously.
I read some unrooting and stock re flashing is required for ota or Kies upgrade. Your screen shots look pretty much like mine before upgrade and I got it upgraded even with root. But I never flashed a custom rom so I could not tell if there is anything special.
I would suggest to look for the stock rom your device came with and wipe it clean following the procedures you can find on this Web.
I cannot recall where exactly was the post from chainfire providing details on rooting and unrooting. But it shouldn't be too hard to find for looking for cf-root related threads with "chainfire" on them.
Good luck.
Sent from my GT-I9300 using xda app-developers app
jamartinezdlv said:
I'm pretty much still a noob so don't take me too seriously.
I read some unrooting and stock re flashing is required for ota or Kies upgrade. Your screen shots look pretty much like mine before upgrade and I got it upgraded even with root. But I never flashed a custom rom so I could not tell if there is anything special.
I would suggest to look for the stock rom your device came with and wipe it clean following the procedures you can find on this Web.
I cannot recall where exactly was the post from chainfire providing details on rooting and unrooting. But it shouldn't be too hard to find for looking for cf-root related threads with "chainfire" on them.
Good luck.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Hi and big thanks for your kind response, much appreciated.
I have solved my problem now, I had managed to wipe, unroot, re lock and reset the counter to make my phone "stock unbranded" but, the problem for me, I had not changed my csc code. My code was for another country which is why ota update and kies would not work. I did not know about csc codes until now.
All I did to solve the ota update and kies was...
1. I search Google play for app to change the csc (can't remember the name of it)
2. Installed the app.
3. Changed the csc code to BTU which is the csc code for UK unbranded handsets, unfortunately this process also reset the phone.
As soon as I did this I had an update waiting, the one before 4.1.1 so I installed it. After I checked software and it said I had another update waiting but, basically I had to join the que, so I connected my phone to kies (worked 1st time) and the 4.1.1 update installed without any issues.
Just wanted to keep you updated and I hope this post helps others
Cheers again
Sent from my GT-I9300 using Tapatalk 2
Dos anybody know what this is at the picture? Its only there at the Boot and only as long as the Samsung Galaxy S3 icon like in the picture is there.thx
{
"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"
}
Same here
Sent from my GT-I9300 using xda app-developers app
Probably just means your phone is restarting
Sent from my GT-I9300 using xda premium
It's some kind of custom firmware counter, I think this happens on some of the latest SIII.
Sent from my GT-I9300 using Tapatalk 2
Thats possible because i get a New one due to a crack in the frame. On My old s3 i dont get this sign. I hope this sign disappear when i flash a original Firmware.
Gesendet von meinem GT-I9300 mit Tapatalk 2
I also have a red mark like that after rooting LK1
Must be something of an answer by Samsung for Triangle Away!
Go through this link http://forum.xda-developers.com/showthread.php?t=1918667
This will solve the issue
Sent from my GT-I9300 with a BIG
Mine just came back from repair ("sudden death syndrome") with a new mainboard and totally stock firmware, showing this red thingy, so it's got nothing to do with being rooted. I'd say it's a 'feature' of newer boards.
UncleBeer said:
Mine just came back from repair ("sudden death syndrome") with a new mainboard and totally stock firmware, showing this red thingy, so it's got nothing to do with being rooted. I'd say it's a 'feature' of newer boards.
Click to expand...
Click to collapse
This could be great info in order to make everybody calm (I mean if I have this then I will never experience the sudden death syndrome, because of newer motherboard).
But, on the other hand, the above mentioned thread has ways to remove it and mentioning that this is due to rooting (flash counter >=1 creates this sign)
Was your phone completely stock when it died ?
(btw I have the same mark on my boot screen)
STELIOSFAN said:
Was your phone completely stock when it died ?
Click to expand...
Click to collapse
Nope; rooted and running Wanam's J5. But since the entire motherboard was replaced, what could possibly remain in the phone to indicate that it had been rooted? The phone's essentially just a mainboard, battery and screen.
UncleBeer said:
Nope; rooted and running Wanam's J5. But since the entire motherboard was replaced, what could possibly remain in the phone to indicate that it had been rooted? The phone's essentially just a mainboard, battery and screen.
Click to expand...
Click to collapse
Maybe something in the motherboard drivers (bootlaoder, perhaps)?
Just guessing...
msri3here said:
Maybe something in the motherboard drivers (bootlaoder, perhaps)?
Click to expand...
Click to collapse
But . . . they're on the motherboard, right? Which was entirely replaced.
UncleBeer said:
But . . . they're on the motherboard, right? Which was entirely replaced.
Click to expand...
Click to collapse
I was reading this other thread and people faced this issue after the bootloader got updated (through OTA updates).
It seems that they flashe the old bootloader and the red line is gone!!
So, it looks pretty much like an OTA update issue (JB mostly)
jaidev.s said:
Go through this link http://forum.xda-developers.com/showthread.php?t=1918667
This will solve the issue
Sent from my GT-I9300 with a BIG
Click to expand...
Click to collapse
____________________
thanks fir this! now i know why there is a red mark on the top left of my screen
during boot up. i got it after rooting and flashing custom ROM on my I9300.
Also getting this after flashing a custom rom on an SGS3 that suddenly died and was replaced.. I'd say it's just another form of 'flash counter'
Anyone know how to remove it? Triangle away doesn't work
Sent from my GT-I9305 using xda app-developers app
prot- said:
Anyone know how to remove it? Triangle away doesn't work
Sent from my GT-I9305 using xda app-developers app
Click to expand...
Click to collapse
For i9300, you need to flash back and old bootloader.. On i9305 dont know..
erto90 said:
For i9300, you need to flash back and old bootloader.. On i9305 dont know..
Click to expand...
Click to collapse
not true. TA works if you follow the instructions
Yep is because of the new Bootloader. I updated it on purpose a few weeks ago, flashed a stock firmware and recovery, rerooted the phone and installed a new recovery...this exclamation mark came up...nothing to worry about..
There is one way to solve that issue
It works for me every time
The red ! appeared if you used custom rom or kernel or recovery
So what you have to do is that flash only stock firmware, kernel and recovery
Then use triangle away to reset counter
After resetting flash counters with TA, the red ! will never appear as long as you use stock firmware, kernel and recovery
Sent from my GT-I9300 using xda premium
I think I am screwed. What is this?
{
"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"
}
Sent from my SCH-I605 using Tapatalk
No idea on every you possibly did but was bored at work and nowhere does it recognize your version. Sorry man.
Sent from my SCH-I605 using Tapatalk
Dang. Im screwed
Sent from my SCH-I605 using Tapatalk
Hey just seen this and remembered about you but in case you haven't figured it out here you go. http://www.droid-life.com/2014/05/0...-gets-minor-update-includes-roaming-on-telus/
Sent from my SCH-I605 using Tapatalk
Thanks. Saw that too.
Sent from my SCH-I605 using Tapatalk
Download link???
Quick note to anyone coming from MJ9, this update can remove your root, and the MJ9 saferoot method will not work on it.
Happy updating to those out there!
I've lost root too..does anyone know of a root process for the build? I haven't tried the process listed in the Development section as it doesn't say anything about the VRUAND3 build...
Thanks!!
Saferoot is not working with the new update VRUAND3 so don't waste your time.
Sent from my SCH-I605 using Tapatalk
Latindude001 said:
Saferoot is not working with the new update VRUAND3 so don't waste your time.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
Forever or is there plans to include it soon in the next safeboot build?
gee1000 said:
Forever or is there plans to include it soon in the next safeboot build?
Click to expand...
Click to collapse
At the moment we don't know yet. But I was told today that you can go back to 4.1.1 with a great risk of bricking your device.
Sent from my SCH-I605 using Tapatalk
how?
Latindude001 said:
At the moment we don't know yet. But I was told today that you can go back to 4.1.1 with a great risk of bricking your device.
Sent from my SCH-I605 using Tapatalk
Click to expand...
Click to collapse
If you updated to 4.3 you cannot go back to 4.1.1
Also going to 4.1.1 is touchy. If you were to go back you need to go to 4.1.2
Basically if you have the official 4.3 update and beyond you cannot unlock the bootloader or in some instances root.
I am using the Skynote Rc2.5 ROM but I am technically coming from 4.1.2. There is no official 4.2.x update for this version of the Note 2.
bvzxa3 said:
If you updated to 4.3 you cannot go back to 4.1.1
Also going to 4.1.1 is touchy. If you were to go back you need to go to 4.1.2
Basically if you have the official 4.3 update and beyond you cannot unlock the bootloader or in some instances root.
I am using the Skynote Rc2.5 ROM but I am technically coming from 4.1.2. There is no official 4.2.x update for this version of the Note 2.
Click to expand...
Click to collapse
Right, I was asking because the ND3 update doesn't appear to be any different than MJ9 firmware wise except for what I assume are mostly changes in the baseband to accomodate the Telus bands. I would think that safeboot will be updated easily for this minor build but I am not any expert by any means.
I also saw people talking about for the same Telus update for the S3 to just Odin backflash VRUCNC1 4.3 to VRUCML1 4.3 with success (http://forum.xda-developers.com/showthread.php?t=2575661&page=153). Anyone tried that? I might actually try it myself to get root back. I don't this new "update". I think VZ did this more to take away root than add some really necessary Canadian roaming anyway.
gee1000 said:
Right, I was asking because the ND3 update doesn't appear to be any different than MJ9 firmware wise except for what I assume are mostly changes in the baseband to accomodate the Telus bands. I would think that safeboot will be updated easily for this minor build but I am not any expert by any means.
I also saw people talking about for the same Telus update for the S3 to just Odin backflash VRUCNC1 4.3 to VRUCML1 4.3 with success (http://forum.xda-developers.com/showthread.php?t=2575661&page=153). Anyone tried that? I might actually try it myself to get root back. I don't this new "update". I think VZ did this more to take away root than add some really necessary Canadian roaming anyway.
Click to expand...
Click to collapse
Curious to see what your results are if you do try this. I also feel that VZW did this update more to take root away, especially considering that the base band could have been incorporated into the (hopefully) upcoming 4.4 update.
Yup, this annoyed me enough that I finally got an account!
this update was just to steal root. they had already tried using the my verizon app to take it. telus uses gsm and the same lte frequency verizon uses. all vzw note 2's could already "roam" on telus. this was just vzw being f**ktards trying to control us.
Has anyone been able to revert or re root their phone after this?
mwinschel said:
Has anyone been able to revert or re root their phone after this?
Click to expand...
Click to collapse
Other users are reporting that you can Odin back to MJ9 and then root with saferoot. See this thread for details... http://forum.xda-developers.com/showthread.php?p=52792973
Sent from my SCH-I605 using XDA Premium 4 mobile app
I was forced the vruand3 update at about 4 am while I was sleeping. I woke up to no root and some issues tied to the freedom app not being uninstalled. I flashed back to mj9 with odin. I rerooted with saferoot. I was still having the connection issues with everything google related. I took the ota update again to try to fix the issue. The google issue fixed itself after the ota, but my root wasn't taken away this time. So now I'm on build vruand3 and have full root access. Maybe someone can shed some light on this , or it will help someone