• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [International] No network connection after failed flash - damaged my phone?

davoid

Android Expert
Aug 3, 2011
1,801
712
London
I was on AOKP mr1 with googy max kernel and all was working fine.

I wanted to try Illusion rom so did a nandroid backup, flashed the zip, wiped the phone and rebooted the phone.

I suspected there was something wrong when I was confronted by the googy max splash screen, and the boot never progressed beyond this splash screen.

So...

I booted back into recovery, wiped the phone again (using philz "wipe before installing new rom" feature, then a manual data wipe, dalvik, and cache. Reflashed Illusion.

Rebooted. Stuck on googy splash screen.

entered recovery, restored my AOKP install and rebooted.

I now have my previous setup apart from one significant difference.

I now have no network connection.

My phone signal is a blank triangle, and when I go into mobile network settings and tap on Network operators (Choose a network operator) a toast pops up saying "Error while searching for networks"

I can no longer use my phone as a phone. I have tried restoring earlier nandroids of other roms and they all show a network error. Neatrom told me to insert a sim card.

I have tried removing and reinserting my sim, but I get the same error.

Is it possible that I have permanently damaged my phone through the failed flash? Or is there a way I can recover from this problem?

I hope someone can help me. I am very stressed about losing my telephony.
 
Nandroids backup and restore everything but the modem. So there's a chance that the original flash messed your modem up but when you restored the nandroid it sorted everything but that. With any luck your efs folder will be fine and all you need to do is flash a compatible modem.

shotgun I didn't see this post. doh!

I tried restoring my efs - first from the img file (nothing happened, even after reboot) and then the tar file. My phone instantly restarted and got stuck during boot.

I have tried restoring nandroids but now it won't boot into anything. I have tried a new flash of AOKP and it is stuck on the samsung splash screen.

EDIT: I assume a new flash would install the modem with it. That makes me think it is too late for that.

I feel like my options are diminishing
 
Upvote 0
shotgun I didn't see this post. doh!

I tried restoring my efs - first from the img file (nothing happened, even after reboot) and then the tar file. My phone instantly restarted and got stuck during boot.

I have tried restoring nandroids but now it won't boot into anything. I have tried a new flash of AOKP and it is stuck on the samsung splash screen.

EDIT: I assume a new flash would install the modem with it. That makes me think it is too late for that.

I feel like my options are diminishing

Oh no I'm so sorry :( I feel really bad because I might not have given you the right info :( Really hope there's a fix for this.
 
  • Like
Reactions: davoid
Upvote 0
I've just read that kTool doesn't work with 4.2.1

AOKP is 4.2.2 so that could be why the efs restore crapped out.

I'm currently downloading the latest stock rom to try shotgun's suggestion.

It will be strange running a stock rom lol.

It's been so long I can't even remember how to root it. :eek:

CDPlant don't worry, you were trying to help.
 
Upvote 0
I flashed a stock rom using Odin, however it wouldn't boot but kept repeating the swirling samsung splash animation.

I flashed Chainfire's CM recovery, then rebooted into philZ (in order to recover my fix for Sudden Death Syndrome) and restored my neatrom nandroid.

Upon booting I noticed a small vertical red line in the top left hand corner of the Galaxy SIII splash screen and when it successfully booted into Android (Yay! :D) there was a brief toast popped up informing me of Factory Mode meaning some things might not work; and on my home screen there was a semi-transparent overlay with technical phone info.

Research turned up that this is caused by a corrupted EFS Folder (not necessarily only, I suppose) and I guess this could have been the original cause for the loss of network, as CDPlant suggested, ;) or it might have been because I attempted to restore my efs folder using kTool with an incompatible version of Android (4.2.1 and above).

Anyway I restored my efs folder using kTool, rebooted as requested, and I now have my network back!

I got my phone back! :D

Thank you so much for any advice and suggestions, guys. CDPlant please don't feel bad about giving advice that might have been wrong. I didn't blame you even when I didn't know if my phone was recoverable. You offered me the kindness of your time and advice when I was worried about my phone and I really appreciate that. And it looks like it might well have been the esf corruption after all.

As an aside, I've remembered that the small red line is there because I flashed a Jelly Bean bootloader with the latest stock rom, and this line indicates I have flashed a custom rom. If I want to get rid of it Ill probably have to flash an ICS rom and then restore again with that bootloader.
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones