Related
Full story: Sold my phone, tried unrooting, soft brick, went back to stock, flashed Cameleon ROM 3.0.2, starts acting weird (more frequent freezes and reboots, vibrates for about 5-10 seconds when it's been off for a while), charge and boot up this morning, and now phone refuses to connect to any network. IMEI's not blocked or anything. TriangleAway formatted my internal SD, so no backups. Also said the battery was at 100% every time I rebooted, even though it was ~85%. Clean flashing CM10.1 didn't help. I've searched everywhere and nothing seems to help. Warranty's out long ago. I'm incredibly frustrated and desperate for a solution
Who knew running low on battery could cause this?
Running on low battery didn't cause it, tho it could be a simple case of needing a new battery. Might want to try that first, tho it does sounds like the USB board is on the way out. This gets discussed here all the time, search for these threads & read them very carefully. There's 4 different revisions of the board; you need to order the same one that's currently in the phone or your phone may not work properly. Other than that, it's quick/cheap to replace yourself.
So if a new battery doesn't do it, replace the USB board.
Edit - Re: the phone not connecting to networks, how do you know for certain the IMEI isn't blocked ?
MistahBungle said:
Running on low battery didn't cause it, tho it could be a simple case of needing a new battery. Might want to try that first, tho it does sounds like the USB board is on the way out. This gets discussed here all the time, search for these threads & read them very carefully. There's 4 different revisions of the board; you need to order the same one that's currently in the phone or your phone may not work properly. Other than that, it's quick/cheap to replace yourself.
So if a new battery doesn't do it, replace the USB board.
Edit - Re: the phone not connecting to networks, how do you know for certain the IMEI isn't blocked ?
Click to expand...
Click to collapse
Of course, I don't know for certain. I used AMTA's checker, and apparently it's not blocked.
I'll try repairing the board. In the meantime, I'll contact the police to find out about the IMEI. Thanks!
Something similar happened to me, try to flash your device with an official ROM, preferable Android 2.3 root your device, then search the GB's Modem or baseband, find the one compatible for your network or country and then you need to flash it via CWM recovery of course you need to be rooted, do a full wipe before you flash anything. Doing this you device should be fully functional and then you can install any Custom Rom. Hope that helps..!
Hi All,
I thought I’d share this as I’ve been pulling my hair out with trying to find answers to this, and sending it to old Sammy was the next option.
After trying everything on every forum, trying the QPST method, trying to use someone else's efs folder (which changed the serial as well) and every other complicated as hell method everyone had suggested, nothing worked expect his which I’ve not found mentioned anywhere as a solution to this (or any other) problem
In the Samsung Kies application under "Tools" there is "Firmware Upgrade and Initialisation,"
With your device unplugged (it will say not available for this model if its plugged in, don't plug it in until it tells you to when in download mode) select this and run the what it tells you to do,
After this is finished you will have a completely fresh install of the latest officially released firmware (for your original build eg. carrier branded) with original serial number and imei number :laugh:
It’s really silly how simple this is yet has not been mentioned or attempted by anyone else, or if it has, not mentioned by anyone else.
I crap you not…
Thanks,
[edit:] just as a note, I got into this problem by not backing up the efs, the world would be a much nicer place if everyone just backed up their efs :laugh:
This has been posted before and does not work in many cases .
Although the method can be useful to restore to original firmware .
jje
Yes, flashing a stock rom will sometimes fix the problem of the efs folder not being mounted or read. It won't fix a corrupt partition or damaged files.
The stock rom you flashed didn't contain any efs data so it isn't any substitute for a backup, you were very lucky it worked.
To my tests this work only when efs is completely empty while upgrade if not it doesn't work
sent from the state where Marijuana is NOT illegal !
Same problem
hello guys,
Well I'm to tell the story of how my aunt damaged apparently her phone
At first the phone is a samsung galaxy S3 from movistar (locked), and she bought a freaking iphone 5 to give the S3 to his husband and there it starts the problem he's in another company so she goes to a store to unlock the phone, the guys on the store supposedly unlocked the phone. So when she arrives home, she puts the sim into the phone and SORPRISE it says emergency calls only and not registered in network. After a week she calls me and hands me over the phone.
My surprise was when I put it in recovery mode, it says flash count 3, and then i did all these terrible things with thephone.
1) Flash it to a stock movistar rom 4.1.2.
2) Sorprise the IMEI sayd null.
3) Searching in the web, found the ariza patch, and I patched it without saving the efs (big mistake).
4) The phone imei's became 0049.
5) So I flash it back to the rom they put in the store and the imei went back I make sure it was the one on the back of the phone.
6) I still stuck in the emergency call not registered in the network thing.
7) Now I rooted the phone erased the whole content of the efs directory (this time with a back up).
8) Did the tutorial thing with samsung kies and I'm back with the movistar rom with the 0049 IMEI.
I don't what to do at this point besides going to samsung and send it to repair I really hope they can fix it at a low price.
Sorry for my english, I'm trying to improve it.
Best Regards
Andy Serrato... the spaniard
Start by reading the stickied faqs and guides EFS/IMEI sticky for one or just pay for a repair .
Galaxy S3(GT-I9300) having the same problem! HELP HELP HEEEELP PLEASE!!
Very unfortunately. this didn't solve my problem, the phone's Serial number is still that auto generated junk, and the EMEI is 00499901640000 as before. I had 4.1.2 on my S3 and Kies has updated it to 4.3 without resolving the issue!
can anyone give an idea on how to surely resolve this issue please. its about 3 months now ever since my phone got screwed up!
Pay for a repair
Perfect
I cannot believe this worked, but it did.
I messed up somehow by trying to flash the wrong cwm.tar file (for i9305) I needed i9300 of course and odin stopped halfway and got stuck, i then pulled the cable out and everything got very messy,.. i kept getting lots of errors etc. i somehow managed to install an old cm11 rom which worked lovely. BUT I had no baseband, no imei, no network, no number, nothing, #*06# or whatever it is, wouldn't work. nothing.
I then started to figure out how the efs filesystem worked, then foundout kies has an emergency thing where i guess they look into there database what your imei was when the phone was built. this would not work because I was using a custom rom (i think) but then I stumbled upon this post. thank goodness!!!!!
It's just restarted and internet, signal, imei is back, baseband version is back. all in order.
however, i think i was also very lucky, but for those of you who are in the position i was in, but this doesn't work, I do think there are ways to get an old efs going again and modify it to your "should be" imei,
if anyone needs an IMEI, I can give you one from a phone i had stolen in vietnam, (not sure its even legal to give it out but whatever)
thank you
Nev
EFS recovery
DonkeyDuck said:
Hi All,
I thought I’d share this as I’ve been pulling my hair out with trying to find answers to this, and sending it to old Sammy was the next option.
After trying everything on every forum, trying the QPST method, trying to use someone else's efs folder (which changed the serial as well) and every other complicated as hell method everyone had suggested, nothing worked expect his which I’ve not found mentioned anywhere as a solution to this (or any other) problem
In the Samsung Kies application under "Tools" there is "Firmware Upgrade and Initialisation,"
With your device unplugged (it will say not available for this model if its plugged in, don't plug it in until it tells you to when in download mode) select this and run the what it tells you to do,
After this is finished you will have a completely fresh install of the latest officially released firmware (for your original build eg. carrier branded) with original serial number and imei number :laugh:
It’s really silly how simple this is yet has not been mentioned or attempted by anyone else, or if it has, not mentioned by anyone else.
I crap you not…
Thanks,
[edit:] just as a note, I got into this problem by not backing up the efs, the world would be a much nicer place if everyone just backed up their efs :laugh:
Click to expand...
Click to collapse
WOW! This worked! I had been struggling for 3 months with my Note 2. Been flashing rom after rom and got stuck in boot cycle. Actually broke down and brought phone to a cell repair shop. She said it just needed a new battery. $50 later got my phone back. She had put stock AT&T rom on it but lo and behold, my sim card didn't work and my IMEI was null. I brought it back and she had it for a week and then said there was a hardware problem AND my USB port wasn't working and it would cost more to fix than it was worth, so she gave it back to me no charge. So I spent next months trying other roms. reading up on EFS folder, even learned some ADB stuff. To no avail. And BTW, my usb port seems to work fine. Finally this afternoon after Turkey Dinner, I stumbled across your forum message. And 15 minutes later I was downloading a repair and the son of a gun fixed everything. I verified it with a Sim card - perfect ! Apparently Samsung has a database of phone serial numbers and what IMEI code goes with them. Fanatastic! Thank you. I will be writing a serious neg review of that cell phone repair place soon.
kangerX said:
To my tests this work only when efs is completely empty while upgrade if not it doesn't work
sent from the state where Marijuana is NOT illegal !
Click to expand...
Click to collapse
I have tried the method posted in the thread ..... but EFS didn't recovered ........ so i decided to follow your procedure
like making empty EFS folder.... so how can i do that ...and if so will it work .....as someone here mentioned that Download firmware package doesn't contains any EFS contains .... help me out :good:
DonkeyDuck said:
Hi All,
I thought I’d share this as I’ve been pulling my hair out with trying to find answers to this, and sending it to old Sammy was the next option.
After trying everything on every forum, trying the QPST method, trying to use someone else's efs folder (which changed the serial as well) and every other complicated as hell method everyone had suggested, nothing worked expect his which I’ve not found mentioned anywhere as a solution to this (or any other) problem
In the Samsung Kies application under "Tools" there is "Firmware Upgrade and Initialisation,"
With your device unplugged (it will say not available for this model if its plugged in, don't plug it in until it tells you to when in download mode) select this and run the what it tells you to do,
After this is finished you will have a completely fresh install of the latest officially released firmware (for your original build eg. carrier branded) with original serial number and imei number :laugh:
It’s really silly how simple this is yet has not been mentioned or attempted by anyone else, or if it has, not mentioned by anyone else.
I crap you not…
Thanks,
[edit:] just as a note, I got into this problem by not backing up the efs, the world would be a much nicer place if everyone just backed up their efs :laugh:
Click to expand...
Click to collapse
i love u so much right now,.. worked like a charm,.. and after thjat i was able to unlock my phone,... thanks so much i would love to give u 10000 thanks
I cant get past entering my model number,, I read it right from under the battery and it still keeps telling me to enter the model number. G550T1 doesnt change from G550T1 no matter how many times you type it... I give up.. If I could just get a twrp backup for mine I may be able to fix it. It's metropcs! flashing to the T-Mobile twrp backup by mistake thinking it was the metropcs one is what got me in this situation... Should have paid better attention...
UPDATE: It took my numbers and I'm trying it now, wish me luck
Well I got it to take my model number and did the whole software thing. Everything is all back to stock but it didnt fix the problem.. Still no net work and says theres no sim card.
Which shop samsung
Which shop samsung or repair shop bro.
Please tell.?????? me I am facing too problem.
stwischu said:
WOW! This worked! I had been struggling for 3 months with my Note 2. Been flashing rom after rom and got stuck in boot cycle. Actually broke down and brought phone to a cell repair shop. She said it just needed a new battery. $50 later got my phone back. She had put stock AT&T rom on it but lo and behold, my sim card didn't work and my IMEI was null. I brought it back and she had it for a week and then said there was a hardware problem AND my USB port wasn't working and it would cost more to fix than it was worth, so she gave it back to me no charge. So I spent next months trying other roms. reading up on EFS folder, even learned some ADB stuff. To no avail. And BTW, my usb port seems to work fine. Finally this afternoon after Turkey Dinner, I stumbled across your forum message. And 15 minutes later I was downloading a repair and the son of a gun fixed everything. I verified it with a Sim card - perfect ! Apparently Samsung has a database of phone serial numbers and what IMEI code goes with them. Fanatastic! Thank you. I will be writing a serious neg review of that cell phone repair place soon.
Click to expand...
Click to collapse
I've resorted to exploring options in Odin3.
All options I've tried didn't work:
1. Flash 1 tar file at a time
2. Re-flash the incompatible TWRP and kernel
3. Boot into recovery
4. Flash PIT
5. Tried different ODIN versions
6. Tried 6 USB cables
7. Tried 2 other computers
Nothing was working, until I saw a Family Guy episode where Peter said "Life is like a Sunday night with your girlfriend, you want to bang her to get to sleep and wake up to a good Monday morning".
That's when I got the idea - I ticked Phone EFS Update (try it first without checking this option) and Phone Bootloader Update and by good heavens, it worked! (had to do 6 or 7 retries as I was getting FAIL! (DeviceInfo)).
So anyone out there with a bricked N930FD, there might be light at the end of the tunnel.
Giggety
Sent from my SAMSUNG-SM-N930A using XDA-Developers mobile app
Lol. You're quite a daredevil to try something like that on a new phone that doesn't have much support options yet.
But I'm glad you got your phone back to normal.:victory:
i23u8 said:
I've resorted to exploring options in Odin3.
All options I've tried didn't work:
1. Flash 1 tar file at a time
2. Re-flash the incompatible TWRP and kernel
3. Boot into recovery
4. Flash PIT
5. Tried different ODIN versions
6. Tried 6 USB cables
7. Tried 2 other computers
Nothing was working, until I saw a Family Guy episode where Peter said "Life is like a Sunday night with your girlfriend, you want to bang her to get to sleep and wake up to a good Monday morning".
That's when I got the idea - I ticked Phone EFS Update and Phone Bootloader Update and by good heavens, it worked!
So anyone out there with a bricked N930FD, there might be light at the end of the tunnel.
Click to expand...
Click to collapse
Maybe lost IMEI if ticked "Phone EFS Update" or "Phone EFS Clear" !!!
Didn't lose IMEI, baseband/radio works like first time I turned on the phone
I didn't lose IMEI, and I haven't encountered any issue.
I tried setting it to GSM only, 3G only, and LTE only, and everything works like as it should.
For LTE, I still get the 4G+ signal which I think is a lot faster than the older 4G.
Both SIM's IMEI are also recognizable.
I thought you only lose the IMEI if you flash the wrong bootloader and/or baseband?
Why, just whyyyyyyyyyyyyyyyyyy??
Bricking as a result of customizing
because I wanted to customize parts of my phone. Dont get me wrong, I think Samsung did a great job allowing us to change a plethora parts of the phone but there are still unreachable parts I wish to change with root hence bricking my phone in the process. Kudos to Samsung still for making it easy to recover the phone.
As Peter would have said, I'm a free-thinking-hypnotized-by-by-the-media member of the society.
.
I admire your enthusiasm and yes it's what being on XDA is all about I guess. But I agree with others that it's way too early to be tinkering about with flashing or modding the Note 7. It's such an expensive phone and (as you learned) so much can go horribly wrong.
.
I only want my Wogiz WX40 to work properly again. It somehow got into a booting loop and I spent many hours figuring out how to flash it due to drivers acting unexpectedly, incorrect instructions for my device and so on.
I finally got it to flash with stock software I got from needrom using SP Flash Tool. However 1) none of the bottom keys work now and 2) it looks as if the resolution is set too high for the device and I think there is also some slowness when using the phone. I have tried clicking upgrade firmware and formatting the entire flash and using different versions of the software and the result is always the same - the bottom keys not working in particular makes it unusable. I tried downloading the stock rom from another location but after downloading it said I needed a password.
So what is the next thing I can try? I'm at my wit's end here and just want it to work again. Thanks for all help.
Anyone know what I should try? For example what custom RAM + firmware might I want to try? At this point I don't care what it is as long as it works. It's a MT6580 device if that helps.
God, I FINALLY got it working.
In case there's anyone else that runs into this: My mistake was getting the stockrom from needrom, every one of those roms for this phone is bad. Get the rom from shareas.us and use SP Flash Tool to flash it, and even then you have to try to get the one that isn't password protected with no password. Leave the battery in, turn the phone off, use option "format + download" in the software and click download BEFORE you connect the phone, NOW connect the phone and after a little while it will start downloading. Disconnect the phone when it's done and switch it on, it will take a REALLY long time to boot up the first time but it should then work.
That's what came from hours of trying to get it to work. The tutorials etc. online are so confusing, even some incorrect instructions like saying I should take out the battery that are completely false and I would never have gotten it to work if I paid more attention to them. I don't ever want to go through something like that again. I finally have my phone back.
I've tried so many times here to get at least a response... Perhaps devs at xda have finally realised, goole are defo creating problems.
I know my stuff, I've flashed hundreds of android phones and tablets, but never have I seen solving a problem, and providing solutions disappear so fast.. Android 10 sux. Random macs destroy firewall security... but hey..
Tried so many times to flash the Armour x5, and know how to use all flash tools. Restored to origional provided rom, but imei was wrong, and got the GoogleKeyState: Fail, used sn write tool to do imei, worked.
So in testing, Imei went back to incorrect one, reflash origional firmware again, only this time, TEE PL error -3, now, I cant use serial writer to do anything, it wont write, yet all in testing is 'normal'
At no point have I messed with anything other than trying to put twrp on this phone, and always extracted a fresh firmware to flash when not happy with tests. To date I have yet to place a sim in this brand new phone.
seems we can do what we want until they get a wiff of our hacks, then they block them.
So yup I'm asking help to root my android 10 Armour x5, I'm testing, but no-one else seems to wanna input anymore, anyone wanna help me help them?
Well, finally managed to get rid of the GoogleKeyState: Fail, as well as correcting the imei's, a rather long drawn out process when no-one knows what they're doing anymore, I guess ya just got to love the old time hackers huh?
To be rid of big red GoogleKeySTate: Fail
Load up SNWrier_1828-4.0.0-vturkey select attestation file, found in extracted firmware, the google folder, select google attest key, make sure all else is unchecked then write, succesfull, gets rid of the big red ****.
Changing imei:
Tried with bootloader locked, then bootloader unlocked...
Using SNWrier_1828-4.0.0-vturkey: Looked like it wrote, got the green tick, upon rebooting phone, wrong imei's were still there, it did not write succesfully. Same with serial numbers.
Used Maui Meta build 9.1724.0.00, on left, select imei download, read from device, (1st box on left) only input the first 14 digits of your 15 digit imei, the last digit of each imei is the checksum, and loads automatically (if you dont increment macs) hit write, shut down the app gracefully, it turns fone off, upon restart, imei was fixed.
Thanks for the lack of help all you experienced folks waiting on us less qualified to wreck our fones so you can profit by reading how we did what..
I got more help from lesser site's..
Not bumping old threads, just keeping at least one up to date with my ever so slow progress..
Still no joy finding any twrp for this fone, but I did find out how to remove all the forced bloatware on the fone, by doing:
pm uninstall --user 0 com.google.android.apps.wellbeing
...and on and on till i got rid of it all, showing you dont need root to remove the apps that are locked to all apk's... surely this 'PM' can be used to grant access to su somehow? I know it can grant, but I know nothing of this layout in 10_Q, even after reading so much crap from others who clearly have as much a clue as I do... and they write apps lol...
I also managed to change the firmware, I swapped Android_10_Q and managed to load the firmware for the x5 PRO, a different fone, different firmware, yet it loaded, and worked 100%, but I went back to the 10_q in order to figure out more, as the pro had way more partitions, and there was NO system viewable compared to the 10_q, which at least can be grep'd.
As for the big red googlekeystate:fail, dont flash preloader when flashing anything! When I flashed the pro android over 10_q, I flashed the preloader of pro and it bricked the fone... I had to wait until fone was out of power before I could load up the writer to reflash 10_q, had to redo the macs and serial, which incidently, for those not knowing, BARCODE is the serial number if you need to revert to stock mac n serial using attestation key. Flashed Pro again and then back to 10_q without causing big red crap by not flashing preloader!!
Now as for those numpties that cant decide if we are using A/B or A only partitions, dont write apps if you cant get it right, your sacked?! One look at the preloader when loaded in SP Flash Tool clearly shows 2 boot sections!!!!!!! Treble checker does what? Lie and cause so many headaches...
Now if i had a twrp for either 10_Q or Pro variant of the ulefone armour x5....