Related
I have root, the first time it froze and didn't sent a test correctly. So I tried it again using Super one. Now I have superuser. Tried both apps on the market and neither one seem to have worked thus yet.
When I try Herolz Galaxy s unlock It is unable to copy EFS, All it says is Done, Error, Not saved. And yes there is an SD card present.
The GS2 unlocker also available on the market will fart around for over 5 minutes and say unlock code not found.
What gives am I doing something wrong? I have tried it with the sim in and with it out. Using Family mobile from Walmart, so I am guessing Tmobile sim card.
Please give me some other root around this.
android 2.3.4
I777UCKH7
kernel version 2.6.35.7
Just go to stock and reroot
Sent from my SGH-I777 using XDA
I didn't know ti wasn't stock. LOL . I just bought it used from a shop here yesterday as am upgrade from gs1. Could you possibly direct me in the right direction as I am unsure what part you are talking about mot being stock.
Than ks in advance
you know you'll only get Edge on Tmo bands.
KH7 is stock, but you stated you have root. Did you do it? if not then check the android Development forums on how to get back to stock. and start the root proccess again.
I got the root through superoneclick. It seemed it did ok as the secong time I went through it said it was already rooted. as for the crappy internet it won't really matter here as we don't even have 3g here in this town for t-mobile anyhow.
if I un-root and re flash back to stock just using the button press combo work? Any why does it only get edge on tmobile?
-Steve
stevewasthere said:
if I un-root and re flash back to stock just using the button press combo work? Any why does it only get edge on tmobile?
-Steve
Click to expand...
Click to collapse
Unroot and back to stock would require Odin/Heimdall.
Only gets Edge on Tmo because its an at&t phone. different bands for 3g.
I have used Super One Click in the past, but its just easier to flash a rooted kernal in Odin/Heimdall, then flash a custom ROM via CWM.
Back to stock is mainly because SuperOneClick is an old tool. and then starting fresh with the latest.
But I had no need to unlock my phone, but from what I've heard its very simple, and most dont have any issues. using the app from the market
I am not afraid of ODIN. I have done that in the past but I did have a huge problem with the GS1 installing an older kernel. I just about bricked the phone. I had to use the HEimdall or what ever it was to get back in it.
On these phone with a custom kernal and rom will it automatically unlock the phone? I am just afraid of using the wrong one and in this particualr section I am sure as to where to go. It doesn't give a whole lot of detail and with the cryogen mod thing it is getting places where I am not sure if I want to really try that. I would but the information is spaced out so much I am afraid of missing something and buggering everything up. What should I have to worry about when doing this?
Also it is the software unlocking I am having problems with.
stevewasthere said:
I am not afraid of ODIN. I have done that in the past but I did have a huge problem with the GS1 installing an older kernel. I just about bricked the phone. I had to use the HEimdall or what ever it was to get back in it.
On these phone with a custom kernal and rom will it automatically unlock the phone? I am just afraid of using the wrong one and in this particualr section I am sure as to where to go. It doesn't give a whole lot of detail and with the cryogen mod thing it is getting places where I am not sure if I want to really try that. I would but the information is spaced out so much I am afraid of missing something and buggering everything up. What should I have to worry about when doing this?
Also it is the software unlocking I am having problems with.
Click to expand...
Click to collapse
Custom kernal will not unlock the phone to be used on a network other than at&t.
Software unlock? assuming you mean using s/w to unlock the device, yes thats the way i understood this thread. I cant really tell ya much about that, but i have heard that its easy and works fine, which is why you should go back to stock first, to get rid of anything messy leftover from using an old rooting method.
stevewasthere said:
I have root, the first time it froze and didn't sent a test correctly. So I tried it again using Super one. Now I have superuser. Tried both apps on the market and neither one seem to have worked thus yet.
When I try Herolz Galaxy s unlock It is unable to copy EFS, All it says is Done, Error, Not saved. And yes there is an SD card present.
The GS2 unlocker also available on the market will fart around for over 5 minutes and say unlock code not found.
What gives am I doing something wrong? I have tried it with the sim in and with it out. Using Family mobile from Walmart, so I am guessing Tmobile sim card.
Please give me some other root around this.
android 2.3.4
I777UCKH7
kernel version 2.6.35.7
Click to expand...
Click to collapse
You get this error when you dont reboot the phone after installing busybox and Herolz Galaxy s phone. Just reboot and try. Same happened for me
stevewasthere said:
I got the root through superoneclick. It seemed it did ok as the secong time I went through it said it was already rooted.
Click to expand...
Click to collapse
You're probably fine as is. Look in Settings | About Phone. If you are stock UCKH7 it should read something like -
Android version 3.2.4
Baseband version UCKH7
Kernel version 2.6.35.7
And why does it only get edge on tmobile?
Click to expand...
Click to collapse
AT&T hardware handles different frequencies than T-Mobile hardware. It's a limitation of the phone's capability to receive the signal.
Try this thread for unlocking the phone.
FIXED!!
Stupid busy box was causing errors. re-downloaded it from the market and installed. Whoalla, unlocked. WTF.... Stupid phone. HAHAHA Thanks...
Trouble Unlocking After Odin Root of
I rooted my phone using Odin and the Siyah-v3.4.2-nomswap-I777.tar file in the PDA. The phone passed, and it reloads with the triangle on the start up as expected. However, it then says "enter network lock control key". It has nothing to do with the sim, as the sim works in another phone. I have done the process several times, running odin back to the original factory settings with I777UCLE5_I777ATTLE5_I777UCLE5_HOME.tar.md5
Could someone please tell me how to get the phone unlocked?
I have done this process before with another i777 phone, and it worked fine.
KEITH000000 said:
I rooted my phone using Odin and the Siyah-v3.4.2-nomswap-I777.tar file in the PDA. The phone passed, and it reloads with the triangle on the start up as expected. However, it then says "enter network lock control key". It has nothing to do with the sim, as the sim works in another phone. I have done the process several times, running odin back to the original factory settings with I777UCLE5_I777ATTLE5_I777UCLE5_HOME.tar.md5
Could someone please tell me how to get the phone unlocked?
I have done this process before with another i777 phone, and it worked fine.
Click to expand...
Click to collapse
Just go back to stock 2.3.4 and go from there.
Sent from Team Pirate Headquarters. AKA yer moms basement.
Also, why expect the triangle? Only time I've seen a triangle is in other people's screenshots...
Clay
Team Pirate
Sent from my Buttery Smooth PINK SGH-i777
aviseqdas said:
You get this error when you dont reboot the phone after installing busybox and Herolz Galaxy s phone. Just reboot and try. Same happened for me
Click to expand...
Click to collapse
I have tried re-installing both software and then reboot. still no luck.:crying:
Xposed module to enable SMS, USSD and native SIP dialing on Nexus 4, 5, 6, 7 2012 and 2013, 9, and 10
I've created an Xposed module to give you a very simple and secure way to enable SMS, USSD and the native SIP dialing function on your Nexus 4, 5, 6, 7 2012 and 2013, 9, and 10. With this module you are now OTA-ready, as you don't have to revert to stock before applying an OTA, because you will not get the popular checksum error, because you don't have to flash anything (except Xposed) and thus don't modify any important file(s).
After this long time I should maybe give an update about the current status.
I red every single reply to this thread now and see there are some Nexus users having problems mainly with MMS. Well first of all I never talked about enabling MMS, but I enabled it anyway, because there isn't a difference to SMS in terms of how Google+OEMs+Providers blocked them.
That means the only reason why some of you are still not able to send and receive MMS messages is, because the provider blocks them at network level. So even though your tablet is able to send them, the providers tower doesn't even think about accepting such a message from your device, because you have a special contract.
The second problem I noticed is something I encountered myself. You will always get two pop-ups when you receive an SMS when you receive an SMS if your ROM already has an SMS receiver module like the SimpleMessageReceiver.apk that is installed by default in Googles Stock Android.
To solve that you have two options: Freeze the app in the app storage list or remove it completely. I recommend to freeze it, because a nonexistent file (after you removed it) would break incremental OTA updates.
I dropped the support for the flashable ZIP files, because they are just so uncomfortable, not cross ROM compatible, break updates, can lead to very ugly boot-loops on SOME devices without any reason. In fact, even if you copy an original framework apk from one stock Nexus 7 to another, you might even get problems there. Even though those files should be exactly the same, because the built number and md5 is the same. Very very strange and I don't have the time to investigate this.
In case you really - for whatever reason possible - don't want to install Xposed and this module, and still use the flashable ZIPs, @GuyAdams still continues to support them here. But it seems like this is for the SMS function only. You decide.
The Xposed module SHOULD work on ANY Android version, with ANY installed ROM on ANY device that is missing one of the above mentioned features. If it does not re-activate those functions on a device, you can still post it here, but Nexus devices will have priority.
If there is an important question for me you can mention me "@makuser". I currently don't have that much time, but I see @teddy0209 is already helping out a lot. Thank you very much for that! I would look out for a direct mention of my name in case anything else is unclear.
If you have any other questions, feel free to ask them
How to get it
If you don't know the Xposed Framework click here to read about it in the Xposed Module XDA-thread.
You will find the Xposed module in the Google Play Store and in the Xposed repo.
Watch it in action
Waiting for upload finished. Thanks
Any one getting boot loop after this install?
Sent from my Nexus 7 using xda app-developers app
msn0005 said:
Any one getting boot loop after this install?
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Are you using TWRP or CWM to flash it? Any other modifications?
bootloop
Bootloop for me, although it did briefly make it to the lock screen the first boot.
I'm on rooted stock 4.4.1 using TWRP 2.6.3.1.
**EDIT: Got it to work by fixing permissions in TWRP immediately after installing.
blackbaa said:
Bootloop for me, although it did briefly make it to the lock screen the first boot.
I'm on rooted stock 4.4.1 using TWRP 2.6.3.1.
Click to expand...
Click to collapse
stacked bootroop too.
Me too 4.4.1 KOT49E TWRP 2.6.3.1
Edit.
Revert bionic patch and now work.
I've a Nexus 2013 LTE with CM 11 based on KOT49E and flash zip with CMW but on reboot system hangs on the cyanogen logo .. I had to reinstall the rom ... Help!!!
After installing SMS Mod the Nexus remained in Bootloop, I installed 2013_KOT49E_Revert and nexus started normally. Reinstalling the SMS Mod brought renewed Bootloop.
Then I installed 2013_KOT49E_Revert and directly behind the SMS Mod Now the MOD works
What i have done:
Scenario:
KOT49E rooted
ElementalX kernel 2.3
4.4 qc-optimized_bionic patch http://forum.xda-developers.com/showthread.php?t=2546120
4.4 qc-optimized_dalvik patch http://forum.xda-developers.com/showthread.php?t=2546120
Working without problems.
Flash KOT49E SMS (OP). Reboot and bootloop.
Solution (almost for me)
Flash KOT49E Revert to Stock in the OP. Reboot and verify.
Flash KOT49E_stock_revert.zip http://forum.xda-developers.com/showthread.php?t=2546120
Reboot an verify.
Flash KOT49E SMS (OP) again, reboot and working.
As i want test qc optimized i re-flash both patchs in http://forum.xda-developers.com/showthread.php?t=2546120.
Working !!!
Good luck
Hung on me too... Stock KOT49E+ElementalX 2.3. Installed and cashe+dalvic wipe.
*But I was able to get it working by:
1) Boot TWRP (power+vol up) and ran the uninstall zip.
2) Restart -- everything looks normal.
3) Restart into TWRP and ran the install zip again.
...now it's working!
Isn't this basically trying to do what the other "SMS enable" mod does, except you know, not actually working???
The one that actually works and wasn't started by the guy with the post count of 4 is here:
http://forum.xda-developers.com/showthread.php?t=2539407
Does it work on 4.4.2 (KOT49H)?
This has bricked my Nexus = Wont turn on, just 5 white LED flashes and nothing.
jarrodstrachan said:
This has bricked my Nexus = Wont turn on, just 5 white LED flashes and nothing.
Click to expand...
Click to collapse
See?
Kind of a bummer cause I need my nexus to direct me to a new job I start today
walterc said:
Does it work on 4.4.2 (KOT49H)?
Click to expand...
Click to collapse
Was someone able to test this?
peter_betos said:
Was someone able to test this?
Click to expand...
Click to collapse
It doesn't even work on 4.4.1 - I wouldn't risk this. It bricked my device
it is working
Trimis de pe al meu Nexus 7 folosind Tapatalk
walterc said:
Does it work on 4.4.2 (KOT49H)?
Click to expand...
Click to collapse
Flashed on KOT45H and bootlooped. Confirmed there is no SMS selection on KOT45H as well.
@makuser
Is it possible to upgrade it for KOT45H?
Many thanks
Sent from my Nexus 7 using xda app-developers app
I've been asked by lots of folks on how to convert the HTC 10 unlocked US version into a full-featured Verizon version so I figured i'd write an all encompassing guide on how to complete the process.
After following this guide, your phone will effectively be a fully-functioning Verizon variant. IMS, advanced calling, wifi calling and all other Verizon features will work flawlessly!
Note: I am purely compiling this information. I had no part in discovering this process, I simply followed multiple guides and other random posts on XDA to accomplish this! Credits go to @jcase, @beaups, @dottat, and any others that were involved with testing this process. Please make sure to thank these guys for the work they've done.
Step 1: Unlock bootloader and acquire s-off
In order to modify the CID/MID and change the radio, we must first acquire s-off. The easiest way to do this is to follow jcase's well-written guide.
[FONT=Hind, sans-serif][Guide] Root (Optionally s-off) and Keep your radio working[/FONT]
Move on to step 2 after finishing the above guide to completion.
Step 2: Change CID and MID
2a) Download this link, and extract into your directory of choice
https://www.androidfilehost.com/?fid=24545065934258327
2b) Boot your phone into download mode via the button combo (down + power) or by using adb reboot-bootloader with USB debugging turned on and then selecting download mode
2c) Issue the following command while in download mode:
Code:
htc_fastboot oem writecid VZW__001
2d) Issue the following command while in download mode:
Code:
htc_fastboot oem writemid 2PS650000
2e) Reboot phone back into download mode and verify the CID and MID have changed and are correct.
Step 3: Flash Verizon RUU to phone
Now that we have s-off, unlocked bootloader and the proper CID/MID on our device, now we just need the Verizon stock ROM and radio on our device. The Verizon RUU will handle both of these for us in a relatively hassle-free manner.
3a) Download the following .exe file to your local machine (big thanks to @dottat!)
Verizon Stock RUU exe (dottat)
3b) Boot phone into download mode (or Android OS w/ USB debugging enabled) and run the executable file
3c) Follow onscreen instructions and wait for process to finish
3d) Reboot phone (it may take a while to boot so BE PATIENT! mine took about 4-5 minutes if I recall)
After your phone boots, it will be a fully functioning Verizon phone. At this point, you can go activate your phone and it will work. You will be able to take Verizon official OTAs and it will behave identically to the true Verizon variant due to the RUU re-flashing stock recovery and an unmodified system.
OPTIONAL -- Step 4: Re-root phone
The RUU that you deployed on your phone was an unrooted system image with stock recovery. In order to get root back, you will need to re-do steps 1-10 in jcases's Root/s-off guide from step 1.
Here's the link again in case you're too lazy to scroll back up
[FONT=Hind, sans-serif][Guide] Root (Optionally s-off) and Keep your radio working[/FONT]
Reminder: your phone already has s-off so you ONLY NEED TO DO STEPS 1-10! Running Sunshine again will likely just report that your phone already has s-off so no worries if you accidentally do the entire guide again.
Step 5: Activate your phone
This step can be very straightforward or a moderate pain the ass depending on what you have available to you.
There are two ways to activate the HTC 10 now that it's running stock Verizon firmware/software:
1) Pop an existing, activated nano-SIM with your current phone number on it in the device and reboot. Voila!
2) Take your device to a Verizon store and convince the employee that your phone is in fact, a true Verizon phone.
I would highly suggest using an already active nano-SIM if you have that available. I, unfortunately, did not as I was coming from the Verizon LG G4. I had to go three different Verizon stores to convince them to finally activate the device. Your IMEI on your unlocked 10 will not show up in Verizon's IMEI database. The store clerk actually had to pull an IMEI from a display model HTC 10 so that she could get the nano-SIM activated for my 10.
noahjk said:
Good post! I think you're looking for this link: http://forum.xda-developers.com/htc-10/how-to/guide-root-optionally-s-off-radio-t3373025
Click to expand...
Click to collapse
Good catch, thanks. I updated the links.
Tried this twice, both times my phone gets stuck on 'Preparing your phone...' after flashing and rebooting on the setup wizard.
edit: worked fine after removing SIM. Run through the setup without SIM for anybody having issues. I know this isn't explicitly stated in OP but if you're having issues, make sure you try this.
If anyone is having connection issues after putting in your SIM, you have to change your Preferred Network mode from Global to LTE/CDMA.
Other than that, everything's working great! Even comes with free VZW bloatware
anyone receiving "Htcdm has stopped" on their phone all of a sudden .... i just downloaded a few things, changed the bootanimation, setup my hotspot, and then bam - popups randomly.
codelinx said:
anyone receiving "Htcdm has stopped" on their phone all of a sudden .... i just downloaded a few things, changed the bootanimation, setup my hotspot, and then bam - popups randomly.
Click to expand...
Click to collapse
Haven't seen that before. What did you do to setup your Hotspot?
DoctorB0NG said:
Haven't seen that before. What did you do to setup your Hotspot?
Click to expand...
Click to collapse
That error would be the ota downloader.. what anything frozen I would ask the person who posted
Sent from my HTC6545LVW using Tapatalk
How would I revert back to the stock values and a stock unlocked RUU? Can you put that in the guide with a link to a stock RUU?
Zooks97 said:
How would I revert back to the stock values and a stock unlocked RUU? Can you put that in the guide with a link to a stock RUU?
Click to expand...
Click to collapse
I'd *think* that you just do the opposite of this guide.
Write MID/CID back to UL (UnLocked) Variant version along with then flashing the UL Variant RUU.
I agree it would be a good idea to add the return to stock either in the OP, or possibly a link to another thread explaining how.
andybones said:
I'd *think* that you just do the opposite of this guide.
Write MID/CID back to UL (UnLocked) Variant version along with then flashing the UL Variant RUU.
I agree it would be a good idea to add the return to stock either in the OP, or possibly a link to another thread explaining how.
Click to expand...
Click to collapse
Looks like all the stock information, RUUs, roms, and recoveries are here.
Has the MID/CID for stock there as well. Hope this makes it into the OP.
When I have access to a desktop/laptop I'll update the guide. Thanks for the suggestions.
After following all the instructions, I got to the end where the phone reboots and is supposed to be Verizon. When mine reboots, however, it comes up with the decryption screen asking for my password. Any ideas?
I think I might have figured it out. I did a factory reset/wipe and it looks like it's coming up now.
hunteditor said:
After following all the instructions, I got to the end where the phone reboots and is supposed to be Verizon. When mine reboots, however, it comes up with the decryption screen asking for my password. Any ideas?
I think I might have figured it out. I did a factory reset/wipe and it looks like it's coming up now.
Click to expand...
Click to collapse
Yep that's the fix. The vzw ruu does not wipe.
Sent from my HTC6545LVW using Tapatalk
andybones said:
I'd *think* that you just do the opposite of this guide.
Write MID/CID back to UL (UnLocked) Variant version along with then flashing the UL Variant RUU.
I agree it would be a good idea to add the return to stock either in the OP, or possibly a link to another thread explaining how.
Click to expand...
Click to collapse
Did you pick up a 10 yet?
aer0zer0 said:
Did you pick up a 10 yet?
Click to expand...
Click to collapse
I did.
It's prepared to be sent to Mr. @beaups when they are back doing devices again on May 22nd.
(In my signature below, in green are the devices I currently own, and the ones striked out are previous devices I had but are sold).
Just an FYI, I followed instructions on this guide, did everything without SIM card in and I do not have any advanced calling features. Signal drops to 1x when on a call and there is no Wi-Fi calling option in the advanced calling menu within Android. My guess on the cause is that I flashed TWRP and side loaded SuperSU before I put my SIM in the phone. I will try again from scratch and activate the phone prior to root and recovery and report back. Is anyone else having similar issues?
Light1984 said:
Just an FYI, I followed instructions on this guide, did everything without SIM card in and I do not have any advanced calling features. Signal drops to 1x when on a call and there is no Wi-Fi calling option in the advanced calling menu within Android. My guess on the cause is that I flashed TWRP and side loaded SuperSU before I put my SIM in the phone. I will try again from scratch and activate the phone prior to root and recovery and report back. Is anyone else having similar issues?
Click to expand...
Click to collapse
Did you activate those features on your account using the menu on the phone?
Sent from my HTC6545LVW using Tapatalk
dottat said:
Did you activate those features on your account using the menu on the phone?
Click to expand...
Click to collapse
What menu are you talking about? I went to take a screen shot of my advanced calling menu in settings and now Wi-Fi calling is showing up.. I didn't change a thing, very odd. However, my signal still drops to 1x when placing a call. And my device says non-VZW device when I login to my account online. I'm guessing that is part of the problem.
Light1984 said:
What menu are you talking about? I went to take a screen shot of my advanced calling menu in settings and now Wi-Fi calling is showing up.. I didn't change a thing, very odd. However, my signal still drops to 1x when placing a call. And my device says non-VZW device when I login to my account online. I'm guessing that is part of the problem.
Click to expand...
Click to collapse
Take some screen shots.
Sent from my HTC6545LVW using Tapatalk
Here is my advanced calling menu with Wi-Fi calling now showing up. Haven't tested, but it seemed to let me set it up. I have Wi-Fi tether enabled via default.xml edits. The one feature I'd really like is LTE on call. Had this without problem on my M7 but I think thats because it had multiple radios and didn't have to share a radio while on call. My noob guess anyways.
Maybe it's a setting in the hidden dialer menu *#*#4636#*#*? However, when I enter that into the dialer, nothing happens, the entered numbers just disappear and nothing happens. Thoughts?
You may need to use Odin3_v3.12_PrinceComsy
- G930UUEU4BQD2_G930UOYM4BQD2_ATT.zip
Thanks a bunch! I've been trying to download it with no success
Thank you. Time to tinker again...haha
Yeah I'm gonna get this rooted and hopefully get some performance back after UPDATE: i rooted successfully but after i tried to fix the fingerprint sensor issue my phone would only boot to recovery and download mode so i flashed to stock
It turns out that when I flashed those files it kept trying to activate my phone on the sprint network instead of att and also it made my settings go wonky so I'm downloading the u firmware with the att product code again because it messed it all up
Just a heads up, I was unable to get the EngBoot Kernel working on this ROM. It would reboot on its own every 2-3 minutes. I spent about 6 hours on this until I gave up and flashed the ATT ROM and then EngBoot. That worked just fine (except for the performance issues).
fatbas202 said:
Just a heads up, I was unable to get the EngBoot Kernel working on this ROM. It would reboot on its own every 2-3 minutes. I spent about 6 hours on this until I gave up and flashed the ATT ROM and then EngBoot. That worked just fine (except for the performance issues).
Click to expand...
Click to collapse
Can you link to ATT Nougat EngBoot rom? I wanted to upgrade to Nougat, wipe, and then get Nougat EngBoot rom on their, but I don't want to use Sprint or whatever that other carrier was. (Prefer to use ATT on ATT devices, ya know?)
Hey I finally was able to get my phone working right I forgot to flash the csc
loganbeck14 said:
Hey I finally was able to get my phone working right I forgot to flash the csc
Click to expand...
Click to collapse
Glad to hear it.
muniz_ri said:
Glad to hear it.
Click to expand...
Click to collapse
Hey can you get the usc product code version for me I have tried to download that specific version but it always corrupts itself and i could only use this version but I had my phone unlocked which means I need a different version so that I can detect my sim card and hopefully set the apn settings acordingly
loganbeck14 said:
Hey can you get the usc product code version for me I have tried to download that specific version but it always corrupts itself and i could only use this version but I had my phone unlocked which means I need a different version so that I can detect my sim card and hopefully set the apn settings acordingly
Click to expand...
Click to collapse
I will try to download it from Sammobile at some point but they seem to be doing maitenance on the site this weekend.
Ok I just want to make sure I'm not going crazy over this so thanks
If I'm using a G930T but using Cricket at my carrier should I flash this or.the TMO variant that you posted in the T-Mobile S7 forum?
A0425A said:
If I'm using a G930T but using Cricket at my carrier should I flash this or.the TMO variant that you posted in the T-Mobile S7 forum?
Click to expand...
Click to collapse
I don't know if it will make any difference but I would try the t-mo version to match your device.
Help!!! I went ahead and flashed the TMO version of the 930u code. I downloaded the ZIP. Placed all the right files in the correct place in Odin (comsey odin) and finished the process. The phone didn't reboot even though reboot was checked. Now I'm in a boot loop. Help!!
Update:. For it to work after flashing a second time. Not sure what happened the first time.
Sent from my Nexus 7 using Tapatalk
It's been a while my S3 has been dead now, virtually rendering it into a WiFi tablet. Let me give a backstory.i had originally bought the phone and it was running 4.0.4, rooted. I wanted to go onto a different software so I came across Cyanogenmod. I flashed it with the automatic tool on pc. It had been quite some time I was running it, until I decided that I wanted to go back to stock. I was a complete noob back then, and where I may now a lot more stuff about phones now, there is still alot to learn. Anyway, I decided to flash a rom called "Back to noot", using twrp. The flash had gone successfully however I booted up to find that I had the infamous circle with the line through it, where the signal should be. I did some more digging and had concluded that my efs had been corrupted. As I was a complete noob, I didn't know what the efs partition was and I hadn't made a backup of it. So I was without a phone basically. Recently though I flashed the latest stock 4.3 rom onto it. My IMEI and baseband are back. However my IMEI isn't correct, the last couple of digits are incorrect, resulting in me having to face the "not registered on network". This is where I am now. I'm without my correct IMEI. Can anyone please help me restore my original IMEI? I have seen on some forums where some people have flashed down to 4.0.4 to successfully recover their phone. However sammobile now requires a premium account to download a 4.0.4 rom for the i9300, weirdly. Can anyone help me to restore the IMEI? Thanks.
You can download firmware for the i9300 on fw.updato.com . Search for the i9300 and filter by version to find the one you want. I am not sure if it is possible to restore your imei without an efs backup though. Good luck
Are you referring to the digits after the "/"?
I've never heard that dowgrading the stock ROM would change the imei.
audit13 said:
Are you referring to the digits after the "/"?
I've never heard that dowgrading the stock ROM would change the imei.
Click to expand...
Click to collapse
The entire IMEI is correct until I reach a certain point.
After the 3rd dash on the back of the phone, the digits follow "182/9". However when dialing *#06# on the phone itself the digits "4344/15". This is what I feel is causing the "not registered on network" error. I never knew downgrading can restore the phone. Ive seen on a forum that someone had recovered their phone by rolling from a higher firmware down to 4.0.4
Sent from my S6 Edge+ using XDA Labs
Was the phone purchased brand new, used, or refurbished?
If the phone is running a stock 4.3 ROM, you can't flash an older ROM as the phone will not allow flashing an older bootloader.
audit13 said:
Was the phone purchased brand new, used, or refurbished?
If the phone is running a stock 4.3 ROM, you can't flash an older ROM as the phone will not allow flashing an older bootloader.
Click to expand...
Click to collapse
The phone was purchased used. If I cannot flash an older version of Android does this mean it's no hope?
Sent from my S6 Edge+ using XDA Labs
It's very unusual that the imei would change on its own. It would be even more unusual for the imei to change when flashing one stock ROM over another. I suppose it is possible but I have never come across a situation where such a thing has happened.
Since the imei on the label does not match the imei in the phone and it was a used purchase, I tend to believe the phone is a "frankenphone" in that it was put together with parts from different phones.
Did you check to see if the imei from dialling *#06# belongs to an s3?
audit13 said:
It's very unusual that the imei would change on its own. It would be even more unusual for the imei to change when flashing one stock ROM over another. I suppose it is possible but I have never come across a situation where such a thing has happened.
Since the imei on the label does not match the imei in the phone and it was a used purchase, I tend to believe the phone is a "frankenphone" in that it was put together with parts from different phones.
Did you check to see if the imei from dialling *#06# belongs to an s3?
Click to expand...
Click to collapse
Actually I haven't checked to see if it does. Do you know how I can?
Sent from my S6 Edge+ using XDA Labs
Type the imei #s in here: https://swappa.com/esn?ref=mobilenations&data1=UUwpUvbUpU2855846YYw
Sent from my S6 Edge+ using XDA Labs
ABADAZZPLAYER said:
Not sure if it's been done properly but that's what came up
Sent from my S6 Edge+ using XDA Labs
Click to expand...
Click to collapse
Please remove your imei from the post. Enter the first 15 numbers.
audit13 said:
It's very unusual that the imei would change on its own. It would be even more unusual for the imei to change when flashing one stock ROM over another. I suppose it is possible but I have never come across a situation where such a thing has happened.
Since the imei on the label does not match the imei in the phone and it was a used purchase, I tend to believe the phone is a "frankenphone" in that it was put together with parts from different phones.
Did you check to see if the imei from dialling *#06# belongs to an s3?
Click to expand...
Click to collapse
Not if he flashed a firmware or rom based earlier than 4.3 and the phone has been 4.3. Efs changed at 4.3 and going backwards kills the efs partition because 4.2 or earlier can't read the new encryption.
There is a possibility that flashing earlier firmwares can write the imei back in, I've read something about this before. If all else fails then why not try it.. Its borked anyway.
Kies emergency recovery is another method but won't work if the phone was rooted.
I think have an efs of a now dead phone. It was a btu i9300 https://drive.google.com/file/d/1MiFFyCCeh1PFuQVZa-M4woreaofcDmrb/view?usp=drivesdk
shivadow said:
Not if he flashed a firmware or rom based earlier than 4.3 and the phone has been 4.3. Efs changed at 4.3 and going backwards kills the efs partition because 4.2 or earlier can't read the new encryption.
There is a possibility that flashing earlier firmwares can write the imei back in, I've read something about this before. If all else fails then why not try it.. Its borked anyway.
Kies emergency recovery is another method but won't work if the phone was rooted.
I think have an efs of a now dead phone. It was a btu i9300 https://drive.google.com/file/d/1MiFFyCCeh1PFuQVZa-M4woreaofcDmrb/view?usp=drivesdk
Click to expand...
Click to collapse
Is this efs dead or working?
Sent from my S6 Edge+ using XDA Labs
How you use it, no clue. I've never had to. It's from a phone that was eventually killed in an accident.
The files are as they were extracted. I zipped them up myself. It is not in anyway suitable to be flashed as is but if you can get the os working and root it you can copy the files to the correct folder, set the permissions and see what happens..
I thought seeing as I have no use for it someone else can, if they can.
shivadow said:
How you use it, no clue. I've never had to. It's from a phone that was eventually killed in an accident.
The files are as they were extracted. I zipped them up myself. It is not in anyway suitable to be flashed as is but if you can get the os working and root it you can copy the files to the correct folder, set the permissions and see what happens..
I thought seeing as I have no use for it someone else can, if they can.
Click to expand...
Click to collapse
I'll give this a try. Who knows maybe this could work. If it does , lots of thanks to you lol
Sent from my S6 Edge+ using XDA Labs
The phone was successfully recovered by flashing the XXUGMK6 ROM, then flashing the Patched UGMK6 Kernal and Baseband that zuluman had given. However the phone only accepted one SIM card from a couple that I had tried, and the phone thought I was in a roaming state, meaning I couldn't use mobile data. Other than that the text message and phone calling functionality, which was the main focus of the repair, has been successful.
Sent from my S6 Edge+ using XDA Labs