FORUMS

Xposed 3.0 Alpha 3 Released

A new alpha for the Xposed framework is out and brings several bug fixes. You’ll only need to flash … more

XDA Recap: This Week In Android (Apr 18 – 25)

Here in the digital XDA newsroom, we spend our days pouring over an average of … more

Sunday Debate: Custom ROMs vs. Modular Tweaks

Join us in a fun Sunday Debate on Mods and ROMs. Come with your opinions and feel free to … more

AOSP 5.1 Lollipop for Nexus Q

Google Nexus Q is an intriguing device released with Android 4.0 Ice Cream Sandwich. It was abandoned by … more
Post Reply Subscribe to Thread Email Thread

N9005 Soft brick ... please help

3rd September 2014, 03:11 AM |#1  
OP Junior Member
Thanks Meter: 0
 
More
hi all
i will try to tell my story in short

i have installed CM11 in my phone and it was just fine then i didnt like the rom for some reason so I've installed the stock rom back
then i dicovered that my phone acting wired

following Symptoms which my phone has :
IEMI : unknown
baseband : unknown
No service
phone crashes


i will be thankful for any help.
 
 
3rd September 2014, 03:29 AM |#2  
Junior Member
Flag Jakarta
Thanks Meter: 0
 
More
err....

have you backup your EFS folder before ??
3rd September 2014, 03:48 AM |#3  
W@r10ck's Avatar
Senior Member
Thanks Meter: 88
 
More
Quote:
Originally Posted by memo880

hi all
i will try to tell my story in short

i have installed CM11 in my phone and it was just fine then i didnt like the rom for some reason so I've installed the stock rom back
then i dicovered that my phone acting wired

following Symptoms which my phone has :
IEMI : unknown
baseband : unknown
No service
phone crashes


i will be thankful for any help.

Check what ver do you have now. You can download the latest firmware from your country on Sammobile then flash again via odin. after flashing try to clear data and cache on recovery. Hope it fixes your problem.
3rd September 2014, 03:55 AM |#4  
OP Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by w1ndfly3r

err....

have you backup your EFS folder before ??

unfortunately No.
3rd September 2014, 03:59 AM |#5  
OP Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by W@r10ck

Check what ver do you have now. You can download the latest firmware from your country on Sammobile then flash again via odin. after flashing try to clear data and cache on recovery. Hope it fixes your problem.

Doesn't Work.
3rd September 2014, 04:19 AM |#6  
Junior Member
Flag Jakarta
Thanks Meter: 0
 
More
Quote:
Originally Posted by memo880

unfortunately No.

hmmm... im afraid your phone are useless now..


btw, i have read somewhere that there is a way to recover your IMEI but i cant remember where it is.
3rd September 2014, 05:51 AM |#7  
Member
Flag Barcelona
Thanks Meter: 9
 
More
Try to connect your phone from the KIES program in a mode of emergency restoration of firmware by Model phone type and Serial Number of the phone. This may take several hours. To do this, you need a good internet.
3rd September 2014, 02:36 PM |#8  
OP Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by porcelana

Try to connect your phone from the KIES program in a mode of emergency restoration of firmware by Model phone type and Serial Number of the phone. This may take several hours. To do this, you need a good internet.

No Luck, Thank though.
3rd September 2014, 06:05 PM |#9  
rayman95's Avatar
Senior Member
Flag monaco
Thanks Meter: 1,460
 
More
Quote:
Originally Posted by memo880

No Luck, Thank though.

That s modem problem. Flash back old modem and you get back IMEI
3rd September 2014, 06:23 PM |#10  
OP Junior Member
Thanks Meter: 0
 
More
Quote:
Originally Posted by rayman95

That s modem problem. Flash back old modem and you get back IMEI

Is modem file called CSC ?
if so i tried many times i think it has to do wiht EFS file maybe.

anyway appreciate your reply
Post Reply Subscribe to Thread
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes


Top Threads in Galaxy Note 3 Q&A, Help & Troubleshooting by ThreadRank