Related
ok about to root and rom. will verizon know if i call them for service questions? what i mean is, i suppose for a tech support call they can do over-the-phone diagnostics. right? if i call for tech support are they able to determine i am rooted and rommed through their diagnostics?
would i need to return to stock prior to making a tech support call to verizon?
thanks
there are honestly very few reps that know anything about the phones they sell
I'm not sure why you'd call Verizon for diagnostics on a device that's not running their software anymore. I'd think talking to the dev would make more sense. I suppose the could tell, but care? Probably not. I told the manager where I got mine that I intended to root it as soon as I got home shd that my old Incredible was already rooted. His only question was how much better the battery life gets.
They will try to help you for sure but they may no be able to since you do not have stock. They can not look up your phone info on their end but they may ask you for info like software or info about the phone from about phone that could give it away. Honestly you're probably better off posting your issue on this forum and having XDA help.
They wouldn't be too helpful not because you rooted but because you have a different piece of software on your phone.
It'd be like calling Microsoft because your copy of Ubuntu is acting up.
>_> big red is all knowing >_> they will find you.. they will GET YOU! >_>
I don't think they can see what software you are using, but I do believe they may be able to see your radio version.
So what about if i pay my bill with the My Verizon app and the thunderbolt ( which they know i have) is not yet supported by them? Not that i care but id think that be a huge red flag lol
Sent from my ADR6400L using XDA App
littleguevara said:
So what about if i pay my bill with the My Verizon app and the thunderbolt ( which they know i have) is not yet supported by them? Not that i care but id think that be a huge red flag lol
Sent from my ADR6400L using XDA App
Click to expand...
Click to collapse
Anyone can google "My Verizon.apk Thunderbolt", download it, and put it on their phones. Even non rooted fellas. So no, this should not throw up any red flags other than you are using a modded application.
U r legally allowed to root so dont worry about it
Sent from my ADR6400L using Tapatalk
I did this a week ago, my TB lost 3G completely at the house and 4G only works in PHX. It just happens the wife's D1 had no 3G so I called and we went through some settings on the phone and they checked the IMEI number etc. Found out the following day after talking to several Verizon people that the issue was the SIM card on the phone so I took it in and they replaced it and that fixed it.
I was rooted when I called, I went back to stock before taking it in and replacing the SIM card. They knew nothing at all.
It would be wise to just find help elsewhere. I find that online support is better than verizons anyways
I am an AT&T tech rep, so I can only speak for here. Bu universally most of us, despite carrier, that know what they are doing will answer the same from what I've found.
When someone walks into the device support center with an obviously rooted I won't exchange it for them. I will help them, find answers, and tell them how to fix it. I will also explain any known problems, or past problems, I know about with various roms. But I won't exchange the phone. And it's not to be mean. But often times when a person does come in with a rooted phone the issue they are experiencing is with the radio they flashed or the rom they are using. I see this a lot with the Inspire as is.
If I deem it to be an actual hardware issue and I can very the rom is not the issue then I will tell them how to take the phone back to stock so I can exchange it. For the Inspire I keep a handy sd card with the stock image there that I can flash it back right away.
If I know a phone has been rooted and the person brings it back to me with it flashed back to stock, I will exchange it without a problem. The phone is still under warranty and the warranty does explain in most products that not current software alterations exist (Ie: rooting, clockwork mod, unlock boot loader). If it's back to stock then warranty guidelines are meet.
Now with that being said, I have physical access to the device. Over the phone, the only way they would really be able to know is if they asked the software version, baseband version, kernel version, etc... and knew what they were off hand. Things like that. They can't magically peer into your phone over the air to see what's going on with it. That's the reason for their little script techs over the phone have to run through.
Ultimately, the advice mentioned above about asking the dev or the rom thread is the best you'll get. Most times this is your best place to look after a custom rom has been flashed. If a problem is deemed hardware and not software and you have to have it exchanged, flash back to stock and take it in. No tech rep will care if it was flashed back to stock (unless they are having a really miserable day and can prove it's rooted. but that's few and far between and not specific to any company).
I was with 3 and I legitimately unlocked my phone to move over to vodaphone.
The it wouldn't work. Wouldn't recognise the sim.
I sent it back to Vodaphone and they wouldn't touch it because there was a crack in the screen.
I got it home and did a bit of a google search and figured out it had something to do with the EFS file.
I rooted the phone and figured out that its completely empty.
I've tried a 1000's things. Looked at 1000's threads and I'm at a loss.
Is there ANY way to fix this at all?
I'm completely at a loss now.
Can I create a new nv_data.bin file and anything else that needs to be in the efs folder?
Happened to me before.
Well of course the way out will be send to service centre.
However, try a full flash to stock rom.
If it doesn't, try factory reset the phone, flash stock rom.
Since you have no backup, pretty tough here.
Sent from my Samsung Galaxy S II using XDA App
Maybe try GS_II Repair from the Market. No idea if/how it works (It's touted on here/on Market as your last best chance before sending it back to Samsung) as I've never used it & always backup my EFS.
If worst comes to worse, pm Odia, and apparently will repair it (edit: remotely) with a "donation". Instal app "team viewer" first;
https://market.android.com/details?id=com.teamviewer.teamviewer.market.mobile
http://forum.xda-developers.com/showthread.php?t=1103357
Apparently been quite successful, nearly but not 100%
Sent from my GT-I9100 using xda premium
nicregi said:
Happened to me before.
Well of course the way out will be send to service centre.
Click to expand...
Click to collapse
Is that how yours was fixed? I've already done that. They won't fix it.
MistahBungle said:
Maybe try from the Market. No idea if/how it works (It's touted on here/on Market as your last best chance before sending it back to Samsung) as I've never used it & always backup my EFS.
Click to expand...
Click to collapse
Yep tried that. Didn't work.
So follow Up In The Air's suggestion & get in touch with Odia & see if he can help, or send it back to Samsung. I'm betting Odia will be cheaper if he can indeed fix it.
Please Help!
Did your issue got resolved?
I am facing the same problem now. Although i didn't root my s2. Been using it stock since i bought it. Only today i got this no network error (baseband and imei unknown) when i was changing between some sim cards.. Anyone any ideas?? My warranty is still applicable since its just been 5 months. So will samsung cover it under their warranty?
I read in a thread that a user got their imei back by switching off, removing sim, switching back on.
Then they were able to backup efs with correct imei.
Then they switched off, put sim back in, switched on. Can't remember if it was a sim issue but you could try that.
Sent from my GT-I9100 using XDA App
aceofclubs said:
I read in a thread that a user got their imei back by switching off, removing sim, switching back on.
Then they were able to backup efs with correct imei.
Then they switched off, put sim back in, switched on. Can't remember if it was a sim issue but you could try that.
Click to expand...
Click to collapse
Tried that like a dozen times already.. Heres some more details regarding my problem:
1. My S2 wont detect any sim card (tried like 3-4 sims)
2. When i checked under settings>about i found imei and baseband version are missing and has been changed to "unknown" (*#06# returns a blank number)
3. Its just 5 months old and is in stock condition. (Not rooted and still running 2.3.3)
4. Cant turn off the flight mode (constantly shows in the upper right corner)
5. Cant connect my phone to kies (version 2.0.2.11071_128) on pc either
What do i do now guys? I dont have a proper service centre in my town. I was wondering if i can fix it on my own without making my warranty void..
Try GS_II Repair from Market, and failing that, contact Odia on here who might be able to recover your IMEI for a small 'donation'. Or you could send the phone in for warranty repair given you haven't been messing around with it like most of us here
You'd probably want to use the third option (send it in for warranty service). If you try and fix it yourself & stuff it up, you'll void your warranty & then you'll end up paying to have it fixed.
kreygor said:
Tried that like a dozen times already.. Heres some more details regarding my problem:
1. My S2 wont detect any sim card (tried like 3-4 sims)
2. When i checked under settings>about i found imei and baseband version are missing and has been changed to "unknown" (*#06# returns a blank number)
3. Its just 5 months old and is in stock condition. (Not rooted and still running 2.3.3)
4. Cant turn off the flight mode (constantly shows in the upper right corner)
5. Cant connect my phone to kies (version 2.0.2.11071_128) on pc either
What do i do now guys? I dont have a proper service centre in my town. I was wondering if i can fix it on my own without making my warranty void..
Click to expand...
Click to collapse
Any fix will probably void warranty .Try factory reset first.
jje
Sent from my GT-I9100 using xda premium
MistahBungle said:
Try GS_II Repair from Market, and failing that, contact Odia on here who might be able to recover your IMEI for a small 'donation'. Or you could send the phone in for warranty repair given you haven't been messing around with it like most of us here
You'd probably want to use the third option (send it in for warranty service). If you try and fix it yourself & stuff it up, you'll void your warranty & then you'll end up paying to have it fixed.
Click to expand...
Click to collapse
Thanks dude. Duly noted your point. Here are some more inputs from me:
1. So i tried GS_II repair from market but it requires for the phone to be rooted which mine isn't.
2. And first thing i tried after i faced this problem was doing a factory reset. Have done it over a dozen times by now and it does not solve it.
3. I faced this problem when i was changing between some sims cards within a couple of minutes. (Hope this doesn't void my warranty since i wasn't actually messing with it!)
4. As i mentioned in my earlier post, my town doesn't actually have a proper authorised service centre. So sending it for service would mean missing my baby S2 for over a month or two (which i find hard since i am so used to it by now)!
So my question is, can i flash an official stock firmware which matches with mine (i found one already here on xda, thanks you guys!) without having to root my phone or making my warranty void, and more importantly, will it solve my problem?
No reflashing a rom won't help, your best bet is to send it off to Samsung before you do anything that might void your warranty.
Sent from my GT-I9100 using Tapatalk
^ Precisely. As long as you have warranty you should use that to your advantage and keep from doing rash decisions that void your warranty. Good luck!
Seriously dude, don't try and fix it yourself. Regardless of how long you'll be without it, at least you'll get it back working and it won't cost you anything other than postage (I presume ?).
If you stuff up whatever you try to do to fix it, you might brick it, which means you'll be without your phone while Samsung fixes it anyway, only you'll be paying for it to be fixed. And given you've already spent however much you paid for the phone, do you really want to spend another couple of hundred bucks to have it repaired when you can get it fixed for nothing ?
As the very wise two posters above me have said, just don't risk it.
Thanks guys.. i have decided to send it for warranty repair then. I will make the visit tomorrow. Will be missing it lots! One hell of a great phone, it was like my mini computer
If i ever knew changing sim cards would screw it up so bad, i would never have done it!
Hopefully will post here later with the good news..
Gave my cell to the service center guys, told me to return later today so that they can examine it. Last i saw it they were fiddeling with it by some IMEI writer on a pc. Hope i get it back up and running soon.
While i was briefing them about my missing IMEI no. they told me that the reason behind it could be me using screen-lock-pattern on my phone. Is it true? Any one experienced it before?
Cool. Hopefully they sort it for you soon
That's interesting. I use a pattern lock mostly & have never seen a relationship between it and the IMEI going missing. What I have noticed tho (and I've seen other people report on here) is the IMEI/baseband go missing occasionally if you reboot the phone whilst connected to a charger.
This rights itself if you do a reboot (occasionally two) with the phone off charger. The first time it happened it scared the crap out of me I had an EFS backup so it would have been recoverable, but it happened out of the blue & I had no idea what caused it. I re-flashed my modem as a first step as the baseband was missing, and that seemed to fix it tho I suspect simply rebooting did the job.
kreygor said:
Gave my cell to the service center guys, told me to return later today so that they can examine it. Last i saw it they were fiddeling with it by some IMEI writer on a pc. Hope i get it back up and running soon.
While i was briefing them about my missing IMEI no. they told me that the reason behind it could be me using screen-lock-pattern on my phone. Is it true? Any one experienced it before?
Click to expand...
Click to collapse
The screen unlock codes are stored in the efs, both patern and pin so maybe that's correct, but efs and thus imei corruption seem to be random, I got it once updating my rom, I keep about 5 backups so I was ok, scary thought.
If you are going to root, first thing you should do after rooting is make an efs backup, hellcats ktool from the market is a good choice, easy and works well.
Sent from my GT-I9100 using Tapatalk
My Galaxy Note (Bell) has a loose micro USB port. It can charge from the wall and is recognized by my pc however I need to prop it up on a slant in order for it to maintain pressure on the cable input, otherwise it will disconnect. It was caused by my dog knocking it off an end table while charging. It's a pain and Samsung has sent me a UPS slip to send it away.
The phone is rooted and this is my first experience with an Android. I've had a good time loading Da_G's kernel, figuring out adb, cwm, dagr8's Saurom and all the rest. However its time to send it back and I really don't know what Samsungs procedures are for a rooted phone. I've loaded the Bell kernel back to the phone but it's not the 100% solution I was looking for so I got frustrated and just went back to where I was already at with Saurom rc4 loaded up and titanium backup now doing it's thing.
Anyone with previous experiences send back a rooted phone for a hardware issue and know their policies?
Is there a step after flashing the bell kernel tar I'm missing?
Thanks
Jesso2k said:
My Galaxy Note (Bell) has a loose micro USB port. It can charge from the wall and is recognized by my pc however I need to prop it up on a slant in order for it to maintain pressure on the cable input, otherwise it will disconnect. It was caused by my dog knocking it off an end table while charging. It's a pain and Samsung has sent me a UPS slip to send it away.
The phone is rooted and this is my first experience with an Android. I've had a good time loading Da_G's kernel, figuring out adb, cwm, dagr8's Saurom and all the rest. However its time to send it back and I really don't know what Samsungs procedures are for a rooted phone. I've loaded the Bell kernel back to the phone but it's not the 100% solution I was looking for so I got frustrated and just went back to where I was already at with Saurom rc4 loaded up and titanium backup now doing it's thing.
Anyone with previous experiences send back a rooted phone for a hardware issue and know their policies?
Is there a step after flashing the bell kernel tar I'm missing?
Thanks
Click to expand...
Click to collapse
I had to send my Captivate to Samsung for repair. it was rooted and they fixed it without any issues.
Most manufacturers will fix hardware issues clearly not caused by rooting. Of course, no promises.
That's the reassurance I needed. I'll get on with it and send it away tomorrow. I'll report back in a very long 2 weeks...
Sent from my SGH-I717R using XDA
Jesso2k said:
My Galaxy Note (Bell) has a loose micro USB port. It can charge from the wall and is recognized by my pc however I need to prop it up on a slant in order for it to maintain pressure on the cable input, otherwise it will disconnect. It was caused by my dog knocking it off an end table while charging. It's a pain and Samsung has sent me a UPS slip to send it away.
The phone is rooted and this is my first experience with an Android. I've had a good time loading Da_G's kernel, figuring out adb, cwm, dagr8's Saurom and all the rest. However its time to send it back and I really don't know what Samsungs procedures are for a rooted phone. I've loaded the Bell kernel back to the phone but it's not the 100% solution I was looking for so I got frustrated and just went back to where I was already at with Saurom rc4 loaded up and titanium backup now doing it's thing.
Anyone with previous experiences send back a rooted phone for a hardware issue and know their policies?
Is there a step after flashing the bell kernel tar I'm missing?
Thanks
Click to expand...
Click to collapse
Best luck.... if you were in America you could just take it to an att store. Just be on a stockish rom and turn it in and they would not notice lol, get another device that day. Idk how things go up in Canada though.
Dont Do It!!!!
I dont know WHY there are people here sending the OP off....EVERYONE KNOWS that if you root it voids your warranty...it doesnt say "It voids your warranty except for hardware issues"
Why set yourself up to be disappointed when you can just revert it back to stock and not worry at all.....people always trying to catch a fool slipping....question is who will be the fool in this scenario????
BigBrotherMotown said:
I dont know WHY there are people here sending the OP off....EVERYONE KNOWS that if you root it voids your warranty...it doesnt say "It voids your warranty except for hardware issues"
Why set yourself up to be disappointed when you can just revert it back to stock and not worry at all.....people always trying to catch a fool slipping....question is who will be the fool in this scenario????
Click to expand...
Click to collapse
Well he should revert back to stock for sure but you can't roll back the counter. But as long as your stock they may not look at the counter and just fix the phone. It's been said before, there's no known case of Samsung voiding a warranty because of it.
Dont know how they do it up there but down here on AT&T we have a 30 day return/exchange policy I exercised yesterday in fact, plus a year warranty giving us refurbished phones if anything happens. I know you guys got it a little before us but I would check into this. Go back to stock there's a thread on how to do this in our development section and take it into your local providers store see what happens maybe you'll get lucky and they'll replace it on the spot. Say it was a hardware defect though.
BigBrotherMotown said:
I dont know WHY there are people here sending the OP off....EVERYONE KNOWS that if you root it voids your warranty...it doesnt say "It voids your warranty except for hardware issues"
Why set yourself up to be disappointed when you can just revert it back to stock and not worry at all.....people always trying to catch a fool slipping....question is who will be the fool in this scenario????
Click to expand...
Click to collapse
Because in everyone's experience they'll generally fix hardware problems even if you're rooted. Of course they have to, but they tend to. We all said there were no guarantees.
BigBrotherMotown said:
I dont know WHY there are people here sending the OP off....EVERYONE KNOWS that if you root it voids your warranty...it doesnt say "It voids your warranty except for hardware issues"
Why set yourself up to be disappointed when you can just revert it back to stock and not worry at all.....people always trying to catch a fool slipping....question is who will be the fool in this scenario????
Click to expand...
Click to collapse
It seems like one does not simply revert back to stock. Admittedly I'm new to this but all I can find in the development forum is the Bell kernel. The full bell system doesn't seem to be up, just the At&T. After a factory reset and old kernal I still have super user loaded and all of the bell bloatware gone. I'm sure with some due diligence I could have made a back up right after my original root but I didn't. Frustrated with the mess I created I just set the phone back up with Saurom the way I liked it.
alexige said:
Dont know how they do it up there but down here on AT&T we have a 30 day return/exchange policy I exercised yesterday in fact, plus a year warranty giving us refurbished phones if anything happens. I know you guys got it a little before us but I would check into this. Go back to stock there's a thread on how to do this in our development section and take it into your local providers store see what happens maybe you'll get lucky and they'll replace it on the spot. Say it was a hardware defect though.
Click to expand...
Click to collapse
It's only 14 days here. I've had it since launch on Feb 14th. Bell is synonymous for passing the buck off, contact them online and they tell you to call in, call them and they tell you go into a store, go to a store and they'll tell you to go to the original store of purchase or another another store with a repair tech on duty. Going directly through Samsung has been smooth thus far, I just hope if they have an issue they'll contact me before blowing whistles and charging my bill some erroneous fees.
Ok, as im sure this question has been asked a 1000 times over, my search turned up no results...so lets ask.
I got this phone from good ol' craigslist with the explicit request that it not be rooted. SURPRISE its rooted and the orig. owner decided to do a fac. data reset, so im none the wiser until I start messing with the phone (lesson learned, no lectures in trading phones needed).
Not only can I not find a comprehensive guide on rooting this thing, I really want a comprehensive guide on UN rooting it.. honestly I'll turn around and root it again, but Id like to know the process going both ways.
The build number is 4.5.141 Firmware Version 2.3.6
If anyone would be so kind as to point me in the right direction I'd greatly appreciate it!
also, My purchased apps are no longer registering as purchased on the Atrix, I can put my SIM back into my inspire and its all good, but the atrix says I need to pay, is this a side effect of rooting this specific phone?
gorealmighty said:
Ok, as im sure this question has been asked a 1000 times over, my search turned up no results...so lets ask.
I got this phone from good ol' craigslist with the explicit request that it not be rooted. SURPRISE its rooted and the orig. owner decided to do a fac. data reset, so im none the wiser until I start messing with the phone (lesson learned, no lectures in trading phones needed).
Not only can I not find a comprehensive guide on rooting this thing, I really want a comprehensive guide on UN rooting it.. honestly I'll turn around and root it again, but Id like to know the process going both ways.
The build number is 4.5.141 Firmware Version 2.3.6
If anyone would be so kind as to point me in the right direction I'd greatly appreciate it!
also, My purchased apps are no longer registering as purchased on the Atrix, I can put my SIM back into my inspire and its all good, but the atrix says I need to pay, is this a side effect of rooting this specific phone?
Click to expand...
Click to collapse
1. To unroot, I guess you can flash your phone back to stock.
2. Your purchases are linked to your Google account.
I had my headphone jack go bad, so I needed to make it look as stock as I could. Simply flashed the stock rom found at http://forum.xda-developers.com/showthread.php?t=1125944 for my model and was done.
To root I used the download from http://www.psouza4.com/Bionic/ and it worked perfectly.
Hope this helps.
Well, I tried one of the unroot processes or it may even been the CWM install process and I'm now the proud owner of a soft bricked Motorola
I found out that the previous owner used super one click, and as convenient as that is I hate that its all based on generic code. SO my problem has gone from unroot to unbrick. Any new suggestions? I'm getting a failed to reboot 3 message and the phone is entering rsd mode and not doing anything from that point on.
Also I know the market is linked to my Gmail, causing my confusion as to why the market on that phone is asking me to repurchase apps.
Sent from my Desire HD using XDA
Dear All,
today I ran into a massive problem with my brand new i9300, which i bought 2 days ago and literally bricked the phone in very unusual way - no network available so I can not make/receive calls, texts or data.
I bought the phone in Bangkok(Thailand), as is(without warranty as it is not from original thai distribution therefore I saved bit over 100 bucks). When I got home and start exploring the phone a little I noticed weird thing - when booting up the logo is GT-I9300T and when I checked on firmware, it was showing GT-I9300T as well but the paper boxe(written in french) showed GT-I9300 as well as the sticker under the battery(GT-I9300). The phone was unlocked and rooted, can not remember the firmware it was equipped with but it was TELSTRA branded(boot on/off animation plus lots of crap appz TELSTRA related). Plus there were few bugs like phone was not able to lock itself(pin, face unlock etc. etc. - nothing was working, no unlocking needed because it never locked anyway) no matter what I did. That really annoyed me so I decided to flash DarkyROM III v3(have been playing with DarkyROMs for last 2 years on my SGS) as I learned that i9300 and i9300T firmwares are interchangable anyway so it should not matter. So I flashed according the guide, no problems encountered at all, it went very smooth. But after the phone booted up, despite everything else was working nicely, there was no signal/network available. Only the "crossed-circle" in the top-right corner where usually the signal bars are.
So I went to the service mode, tried to force different bands in both - GSM and WCDMA but no luck. Still no networkd available. So I decided to give a go to few another modems - both versions i9300 and i9300T - flashed in CWM and Odin too - no luck, still the same. So I reflashed few SAMSUNG stock firmwares plus tried the various modems again, still the same result - crossed circle instead of signal bars, no network. So I went to SAMSUNG SERVICE CENTER, they were very helpful, played with my phone for almost an hour, flashed latest official thai firmware but the result is still the same. No network. They even reflashed the initial bootup animation so now it is showing correctly GT-I9300. They checked the imei+s/n and confirmed the phone is I9300 coming from France originaly(french distribution) and apologized, because it is french phone they do not have the required firmware/software on hand so that they can help me and fix my phone. So what can I do? I guess if SAMSUNG Service Center can not help me, does it mean I should throw away my phone into the nearest thrashbin? I spent almost 600USD on it - its a lots of money for me. Well lesson for me is - never buy anything from unofficial distribution!
But please let me ask you guys - any idea what can I do to make it work again? Anyone else have similar experience as me?
The phone shows same IMEI as on the paper sticker below the battery, but the serial number shows ony zeros(0000000) instead the letters/numbers which are mentioned on the sticker.
Any more info, please let me know. I will appreciate any suggestion/help/assistance to make my SGS3 work again, please please please help me!
Thanks a lot, kind regards
Tomas
Are you absolutly sure that this phone wasnt stolen? It can be locked by IMEI If it was.
By Tapatalk 2
SirKunon said:
Are you absolutly sure that this phone wasnt stolen? It can be locked by IMEI If it was.
By Tapatalk 2
Click to expand...
Click to collapse
I have no idea, how can I find out? I guess SAMSUNG Service Center would tell me, no? And the phone was working perfectly until the flash.
Its not brand new if its been rooted .
See the recent posts regarding the T Model and network .
jje
Maybe this phone was simunlocked in some kind of temporary way. After flashing original firmware efs was rebuilded with simlock to original carrier, Telstra in this case? I dont think you have got their sim to check this. Maybe try few ways to simunlock now, just after flashing a tripplefile stock firmware with mx.pit and repartition checked in Odin.
Take out your current simcard and external sd card while flashing.
By Tapatalk 2
@JJEgan: thanks but as per SAMSUNG SC the unit is i9300, not i9300t as was flashed originally.
@SirKunon: how complicated is it to simunlock? Do I need some specialized equipment/sw? So what you suggest is to find stock firmware with three separate files - pda, phone, csc - and flash them together with mx.pit repartition ticked? Can't that mx.pit do some more harm? And how about bootloader, what is it really good for?
Indopilot said:
@SirKunon: how complicated is it to simunlock? Do I need some specialized equipment/sw? So what you suggest is to find stock firmware with three separate files - pda, phone, csc - and flash them together with mx.pit repartition ticked? Can't that mx.pit do some more harm? And how about bootloader, what is it really good for?
Click to expand...
Click to collapse
Bootloader is usualy included in all firmwares and flashed, no matter is it one or three files. But generaly only roms with separete csc, pda and modem include script commands for wiping data (dalvik also) and cache just after flashing a firmware. Some carriers are using diffrent than stock recommended partition layout and that why i suggest repartition - to wipe all junks from Telstra branding.
About simunlock You should search this forum, I didnt do that with my s3 becouse its stock unlocked. I only debranded my phone from T-mobile to stock. On sgs and sgs2 i have to use some soft, I dont remember how its names. From efs folder (root needed) extract nvdata.bin in this file are informations about IMEI and simlock encoded. You need to find that software which will remove simlock bytes and after that push nvdata.bin back to efs partition and set right owner (radio or root) and permissions. Maybe three is also easiest way to do that. But root always will be necesary.
This is only things that may help if sammys SC itself failed.
By Tapatalk 2
Easy solution for you :-
http://forum.xda-developers.com/showthread.php?t=1838480
Can people stop using the term "bricked" when it's clearly not please.
Sent from my GT-I9300 using xda app-developers app
riso123 said:
Can people stop using the term "bricked" when it's clearly not please.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
I'm sure people like me can stop using the term "bricked" if you know a better term for a cell you can not use for calling, texting and using data anymore(sorry but phone u can not use for its main purpose is a brick to me). But honestly I would expect more from a senior member like u than an "advice" like that just to add an 1 extra count on your posts count. If you don't know how to or don't want to help, just say that straight away or don't reply at all. Your comment like this is not gonna help anyone and certainly no-one is gonna learn anything new from it.
Indopilot said:
I'm sure people like me can stop using the term "bricked" if you know a better term for a cell you can not use for calling, texting and using data anymore(sorry but phone u can not use for its main purpose is a brick to me). But honestly I would expect more from a senior member like u than an "advice" like that just to add an 1 extra count on your posts count. If you don't know how to or don't want to help, just say that straight away or don't reply at all. Your comment like this is not gonna help anyone and certainly no-one is gonna learn anything new from it.
Click to expand...
Click to collapse
What does me being "senior" have to do with it? It doesn't make me any more of a role model, doesn't earn me extra money and doesn't make my poopie smell nice...
Your phone is not bricked, it's just lacking in functionality at the moment. It's likely something that can be fixed... if it was bricked, you would have no functionality and no way to fix the device, thus making it a useless brick...
So yeah, my original post stands... your using the term, along with a lot of other people, incorrectly and it's annoying.
Sent from my GT-I9300 using xda app-developers app
try flashing it with stock rom for australia.
riso123 said:
What does me being "senior" have to do with it? It doesn't make me any more of a role model, doesn't earn me extra money and doesn't make my poopie smell nice...
Your phone is not bricked, it's just lacking in functionality at the moment. It's likely something that can be fixed... if it was bricked, you would have no functionality and no way to fix the device, thus making it a useless brick...
So yeah, my original post stands... your using the term, along with a lot of other people, incorrectly and it's annoying.
Sent from my GT-I9300 using xda app-developers app
Click to expand...
Click to collapse
Well what else can I add, maybe just "thank you very much for your very useful advice, it's very much appreciated and it helped me a lot". But on a serious note now, obviously you have absolutely no idea how to help as the SAMSUNG SC does, but at least they don't try to be a smart ass and admit that straight away. Anyways my apologies to everyone who got offended by my term "brick", I should use more proper term "useless". I hope this will make you happy now so you can get a good night sleep Mr. Smart###!
Indopilot said:
Well what else can I add, maybe just "thank you very much for your very useful advice, it's very much appreciated and it helped me a lot". But on a serious note now, obviously you have absolutely no idea how to help as the SAMSUNG SC does, but at least they don't try to be a smart ass and admit that straight away. Anyways my apologies to everyone who got offended by my term "brick", I should use more proper term "useless". I hope this will make you happy now so you can get a good night sleep Mr. Smart###!
Click to expand...
Click to collapse
You have been given the needed advise to fix the problem. The only reason that flashing your carrier and country brand firmware would be that your IMEI has been blocked. If your IMEI is blocked then the phone is likely a stolen unit.
What more advise do you want/need, Mr Arrogant?
Edit: oh, and of course your EFS could be screwed. But again, flashing to stock would fix that too...
Sent from my GT-I9300 using xda app-developers app
First if all, not all country implemented the IMEI blocking.
It requires huge resource to maintain the database.
Which country and network you are trying to use it at?
Secondly I haven't seen one method of flashing to change the boot logo like SAMSUNG SC did.
Can the Thai have done the same originally?
What is the model number under the battery.
Sent from my GT-P1000 using xda app-developers app
priyana said:
First if all, not all country implemented the IMEI blocking.
It requires huge resource to maintain the database.
Which country and network you are trying to use it at?
Secondly I haven't seen one method of flashing to change the boot logo like SAMSUNG SC did.
Can the Thai have done the same originally?
What is the model number under the battery.
Sent from my GT-P1000 using xda app-developers app
Click to expand...
Click to collapse
Sorry I have no idea about IMEI blocking - maybe it is not that common here due to huge amount of mobiles in use around here? I am in northern Thailand, trying to use it on DTAC and yesterday got 2 more SIMs to try another operators - AIS and TRUEMOVE. Even tried my czech and indonesian SIMs, without luck.
I do not know the way SAMMY SC used to change my boot logo but they did it somehow. And this morning I dropped my S3 to one of those street shops specialised in unlocking and repairing phones - they said should be no problem to fix it, left it there for an hour but they returned it to me with apologies that they reflashed what they could and tried different firmwares but no luck. And BTW they reflashed the boot logo too - now it is back to GT-I9300T(which is annoying, will go to SC again on Monday to reflash it back to I9300).
The model number under the battery states: GT-I9300 and SAMMY SC confirmed I9300.
And yes I am sure despite the fact the phone has been sold to me as brand new, someone must have tampered with it - I guess to unlock it or something - it was rooted and CWM was installed. As I mentioned according SAMMY SC the phone comes from french distribution, is GT-I9300 but it was TELSTRA(I think australian) branded and flashed with GT-I9300T.
And to top it up - KIES can not identify what was the original FW for this unit - after inserting the model and S/N into KIES, it just says to check the S/N again and insert the correct one. Real mistery!!!:crying:
But anyway thanks a lot for help and suggestion priyana,
Tomas
Indopilot said:
Sorry I have no idea about IMEI blocking - maybe it is not that common here due to huge amount of mobiles in use around here? I am in northern Thailand, trying to use it on DTAC and yesterday got 2 more SIMs to try another operators - AIS and TRUEMOVE. Even tried my czech and indonesian SIMs, without luck.
I do not know the way SAMMY SC used to change my boot logo but they did it somehow. And this morning I dropped my S3 to one of those street shops specialised in unlocking and repairing phones - they said should be no problem to fix it, left it there for an hour but they returned it to me with apologies that they reflashed what they could and tried different firmwares but no luck. And BTW they reflashed the boot logo too - now it is back to GT-I9300T(which is annoying, will go to SC again on Monday to reflash it back to I9300).
The model number under the battery states: GT-I9300 and SAMMY SC confirmed I9300.
And yes I am sure despite the fact the phone has been sold to me as brand new, someone must have tampered with it - I guess to unlock it or something - it was rooted and CWM was installed. As I mentioned according SAMMY SC the phone comes from french distribution, is GT-I9300 but it was TELSTRA(I think australian) branded and flashed with GT-I9300T.
And to top it up - KIES can not identify what was the original FW for this unit - after inserting the model and S/N into KIES, it just says to check the S/N again and insert the correct one. Real mistery!!!:crying:
But anyway thanks a lot for help and suggestion priyana,
Tomas
Click to expand...
Click to collapse
Hi Tomas,
I am experiencing the same problem have u been able to fix your phone? If so how did you do it? I hv tried flashing so many firmwares and took it to like 10 stores without success. Imei is shown also, but sn differs from the one on the sticker. Thanks!
Yes, the issue has been solved easily and free of charge although Sammy SC in Czech Republic and Thailand told me it is a hardware issue and motherboard has to be replaced(costs 225UDS in Thailand and 250EUR in Czech Republic). I repeat it is a lie and trick how to rip you off of some cash - it is SW issue only and I found a place where it has been fixed in less than half an hour and free of charge. Sorry, I m travelling now, will give u more details later Keep hope alive!
Sent from my GT-I9300 using xda app-developers app
manormachine said:
Hi Tomas,
I am experiencing the same problem have u been able to fix your phone? If so how did you do it? I hv tried flashing so many firmwares and took it to like 10 stores without success. Imei is shown also, but sn differs from the one on the sticker. Thanks!
Click to expand...
Click to collapse
You need to visit some service centre wih SPT box.
It will make your phone functional.
But you need to remove modem before flashing roms
If you flash modem after repair you will loose signals.
muhammad.ali123 said:
You need to visit some service centre wih SPT box.
It will make your phone functional.
But you need to remove modem before flashing roms
If you flash modem after repair you will loose signals.
Click to expand...
Click to collapse
So this issue can not be solved and I will have to stay on the same modem forever? So how can we ever update our firmware if modem can not be tampered with? It sounds like this issue bans us completely from updating our firmware I wanted to try other stock/modded firmwares or at least kernels but now I m afraid to touch the firmware in order not to lose signal again:'(
Sent from my GT-I9300 using xda app-developers app