Related
Hey guys, im new to the scene, and while fiddling around with my Galaxy S3, i have managed to brick it! Here is what happened.
I rooted the phone using a tutorial from here:
http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/
Everything worked fine and the phone successfully rooted. But than i came across roms ... and i found a tutorial that told me how to install CyanogenMod 9:
http://forum.xda-developers.com/showthread.php?t=1778165
I tried to follow the instructions, but i would get (Error 7), and i realized that this tutorial instructed me to install the ClockworkMod Recovery version 5.8.4.7. So i downloaded the file from ClockworkMod's website, and it was in a .img format. When i had rooted my phone and installed ClockworkMod i used a .tar version via Odin, and this time i had a .img. After going through many tutorials, i found someone that showed how to install the .img varient via Android Terminal Emulator. So i followed the instructions:
http://forum.xda-developers.com/showthread.php?t=1363132
After i was finished following the instructions i rebooted the phone. And boom, it would not turn on. I tried all variants of holding the external buttons etc. Than i plugged the phone into a Windows PC. and the phone shows up in device manager as "QHSUSB DLOAD". So after tirelessly researching, i finally found the drivers for this and installed them. And know the phone shows up in Odin as COM10 in yellow. So i tried to flash the stock Image. I fire up Odin, select PDA, than the stock image, and click start. This is all that happens in the "Message Log":
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
(I have attached a screenshot of the above)
Please guys, i just got the phone and now it is bricked, any help would be greatly appreciated. Thanks!!
First download the correct version of Odin and drivers for s3's here ;
http://forum.xda-developers.com/showthread.php?t=1722686
Then download and flash the full stock rom from here;
http://forum.xda-developers.com/showthread.php?t=1752729
Hopefully that will get your phone to boot.
Then once you have reapplied the rooted system image download "rom manager" from the market and flash the updated recovery from there to avoid the error you encountered when attempting to flash cm9.
Good luck!
Hi, Thanks for your reply. I tried using a "Jig" and it did not put the S3 into download mode. LIke i said previously. When the S3 is connected to my PC it shows up as "QHSUSB DLOAD". And no Samsung drivers would work with it. I had to research and find the drivers that finally worked and allowed Odin v1.85 to see the phone as "COM10", and i select the ROM under the PDA and click the "Start" button. But than it does not go past SetupConnection. I thought maybe the "Jig" was faulty and didnt work, but i tested it with another working Samsung Galaxy S2, and it worked exactly as it was supposed to. Should i still try your suggestion or is it pointless?
neubauej said:
First download the correct version of Odin and drivers for s3's here ;
http://forum.xda-developers.com/showthread.php?t=1722686
Then download and flash the full stock rom from here;
http://forum.xda-developers.com/showthread.php?t=1752729
Hopefully that will get your phone to boot.
Then once you have reapplied the rooted system image download "rom manager" from the market and flash the updated recovery from there to avoid the error you encountered when attempting to flash cm9.
Good luck!
Click to expand...
Click to collapse
Ouch.
It sounds like your bootloaders might be borked, so kinda pointless.
I would get ahold of Josh at www.mobiletechvideos.com as it sounds like jtag might be required.
Hey, Thanks for the info. But the image i flashed via the Android mobile terminal app on the phone, i was flashing a ClockworkMod v5.4.8.1, that was made for the AT&T i747 (I have the Bell i747M, which i am told is the same thing?) , is that the bootloader? I know someone here that is local that does the jTag repair. But im not sure if the problem i have is in relation to the bootloader. Please let me know. As the phone still does show up when connected to the PC.
neubauej said:
Ouch.
It sounds like your bootloaders might be borked, so kinda pointless.
Get ahold of Josh at as it sounds like jtag might be required.
Click to expand...
Click to collapse
I tried your solution. The phone when connected to the PC with does not show up in Odin 3.07 (Correct version for my phone, from your link), But if i turn on Odin 1.85, the phone shows up fine in that as COM10 in yellow. So does my phone need a jTag? Samsung Canada told me to send the phone in for service and they will reset it and send it back. At the moment the phone does not turn on or go into download mode, and when connected to the computer it shows up as HS-USB QDLoader. So my question is: If i send it to Samsung, will they discover that i have Rooted it and void my warranty and not fix the phone?
neubauej said:
First download the correct version of Odin and drivers for s3's here ;
http://forum.xda-developers.com/showthread.php?t=1722686
Then download and flash the full stock rom from here;
http://forum.xda-developers.com/showthread.php?t=1752729
Hopefully that will get your phone to boot.
Then once you have reapplied the rooted system image download "rom manager" from the market and flash the updated recovery from there to avoid the error you encountered when attempting to flash cm9.
Good luck!
Click to expand...
Click to collapse
If you send it to Samsung its unlikely they will notice or care that its rooted.
I have sent them 2 devices that I wanted them to reflash after I did stupid things and hardbricked, fully expecting to pay for it, and it was returned to me flashed and at no charge. This was after I told the customer service rep that I was flashing custom firmware and i screwed it up.
YMMV.
The worst case scenario there is they void your warranty and charge you a minimal fee to reflash it.
As for your bootloaders, you pushed a custom recovery that failed, corrupted, or was an incorrect application. The recovery lies in the bootloader..
If it doesn't power up, won't go into download mode, and Odin won't flash it I'd say its jtag or send it to sammy time.
I see, well i do not care if they charge me anything. Money is not an issue, Ok well i just got the email from Samsung with the shipping label. Thanks for your information.
neubauej said:
If you send it to Samsung its unlikely they will notice or care that its rooted.
I have sent them 2 devices that I wanted them to reflash after I did stupid things and hardbricked, fully expecting to pay for it, and it was returned to me flashed and at no charge. This was after I told the customer service rep that I was flashing custom firmware and i screwed it up.
YMMV.
The worst case scenario there is they void your warranty and charge you a minimal fee to reflash it.
Click to expand...
Click to collapse
Goodluck!
Fyi 5.4.8.7 is the clockwork version I'm running.
After doing some more research, i found that another person with a different Samsung phone. Followed the same instructions to flash ClockworkMod via Android Mobile Terminal using the same instructions i did and got the same problem. On his post somebody told him that the flash was made to the wrong partition or something like that. So ... Lesson for next time. READ EVERYTHING BEFORE TRYING IT!
neubauej said:
Goodluck!
Fyi 5.4.8.7 is the clockwork version I'm running.
Click to expand...
Click to collapse
Yeah just go to Samsung. Its too bad u never read that the newer versions of CWM recovery don't work on the 747m. The 747 and our m variants are close but still a bit different in a few ways although when coming here for rooms and stuff we have to use this at&t 747. Section. There is a great rooting post under the development stickies and it mentions the UNICERSAL VERSION OF CWM RECOVERY FOR 747m phones and that is the one I used and all of us 747m users should install. 5.4.0.4 or something like that. Definitely not 5.8.x.x. I could have told u that would brick your phone and most proper posts would too. And unfortunately yes the recovery resides in the boot loader area so it can cause a brick.. so keep that in mind when u get your phone fixed. Either use the earlier cwm rec version or just change to TWRP RECOVERY which I just did and many recommend now anyways.
Good luck and I'll come back to post the link with the best root and cwm rec install forOUR 747M phones and remember there are some differences and not all 747 mods will work for us so please read up first
Sent from my SGH-I747M using xda premium
pchemerys said:
Yeah just go to Samsung. Its too bad u never read that the newer versions of CWM recovery don't work on the 747m. The 747 and our m variants are close but still a bit different in a few ways although when coming here for rooms and stuff we have to use this at&t 747. Section. There is a great rooting post under the development stickies and it mentions the UNICERSAL VERSION OF CWM RECOVERY FOR 747m phones and that is the one I used and all of us 747m users should install. 5.4.0.4 or something like that. Definitely not 5.8.x.x. I could have told u that would brick your phone and most proper posts would too. And unfortunately yes the recovery resides in the boot loader area so it can cause a brick.. so keep that in mind when u get your phone fixed. Either use the earlier cwm rec version or just change to TWRP RECOVERY which I just did and many recommend now anyways.
Good luck and I'll come back to post the link with the best root and cwm rec install forOUR 747M phones and remember there are some differences and not all 747 mods will work for us so please read up first
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
I don't think the version he used was the issue as other Canadian users report that 5.8.x.x works fine.
http://forum.xda-developers.com/showthread.php?p=29664739
Edit: the link with instructions for terminal emulator on the op is for the lg thrill which writes the recovery onto block 6. On this phone it needs to be written to block 18.
Sent from my HTC One S using xda app-developers app
Frowben said:
I don't think the version he used was the issue as other Canadian users report that 5.8.x.x works fine.
http://forum.xda-developers.com/showthread.php?p=29664739
Edit: the link with instructions for terminal emulator on the op is for the lg thrill which writes the recovery onto block 6. On this phone it needs to be written to block 18.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Ah yes..that makes sense. That would pooch the phone. As for cwm it appears I was mislead as I read on few posts that newest versions don't work or not recommended for Canadian variant but it appears u might be right and I'm now seeing more and more report that it is installable. I'll have to check it out. Thanks
You flashed a recovery for the LG Thrill 4G. At what point in time did you assume it was the same phone as the I747M? You have bricked your phone. It needs JTAG service. Samsung will probably cover it under warranty, or you can pay someone that has the equipment to do it. You have no other options at this point. When you get it back from repairs, make sure you only flash AT&T/Bell/Telus/Rogers I747(M) software to the phone....
Ya i got the phone back from Samsung after waiting 3 weeks. They had to change the motherboard on the phone. Yes, it was the wrong instructions i followed which screwed me over! Since than i re-rooted how i did the first time i got the phone. Just a few days ago i saw the new CyanogenMod 10 M1 Rom, which i wanted to install. And again like last time in order to install it i had to upgrade my CWM to the newest version. This time i did not rush into it like last time and consulted with my buddy who is an expert in Android. The problem i had last time was i downloaded the new CWM in an .img file, and this time i ended up finding the newest CWM in a .tar and used Odin to flash it successfully. Than i just installed the rom and was good to go. My main reason for wanting to install a custom rom was i was getting absolutely HORRIBLE battery life from my S3. I ended up buying a juice pack which greatly helped me out. But now that i have CM10 my battery life is phenomenal, + the juice pack i now go maybe 2 days without having to charge. Now my sister who has the Wind Mobile S3 T999V wants me to upgrade her rom to the same as mine. I have found the T-Mobile CWM for her phone, and all the relevant software, but i am still hesitant to install the CWM on her phone. The T-Mobile CWM 6.0.1.2 is compatible with the Wind Mobile S3 T999V right? Or do i have to use a different version?
just to be clear about where you went wrong (im sure its been said already)
the guide you followed to install cwm is from the lg thrill forum. so the command dd if=... of=... had the wrong device id which is the most common cause of a brick
its actually pretty difficult to mess up your phone as long as you don't use mods designed for other devices
jefferson9 said:
just to be clear about where you went wrong (im sure its been said already)
the guide you followed to install cwm is from the lg thrill forum. so the command dd if=... of=... had the wrong device id which is the most common cause of a brick
its actually pretty difficult to mess up your phone as long as you don't use mods designed for other devices
Click to expand...
Click to collapse
Yes, i know that. I realized after i had done everything that the instructions where for another phone. Now im trying to find the CWM 6.0.1.2 for my sister phone T-Mobile S3 T999V that is in a .tar file already. Any suggestions on where i can get it?
I use cwm 5.8 .0.4 i think and it works fine go to the dev stickies and its there
Sent from my SAMSUNG-SGH-I747 using xda premium
JB calhoun said:
I use cwm 5.8 .0.4 i think and it works fine go to the dev stickies and its there
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Ya for my sisters phone i have that version as a flashable tar, however to install CM 10 M1 i need to install CWM 6.0.1.2.
Did u try rom manager
Sent from my SAMSUNG-SGH-I747 using xda premium
First, I'm an idiot,,,got new to android,,had no idea about flashing,, so I just randomly picked a Rom, and turned out its a GT-N7100 ROM, now my phone has no signal at all,,, anyone know how to flash back ? or I have to wait a att ROM come out?
BTW, Im with Rogers.
Thanks:laugh:
your gonna have to wait till either someone makes a odin back with a stock rom or makes a stock rom you can flash via recovery.
EDIT: did you make a backup?
this reminds me of the following youtube video:
http://www.youtube.com/watch?v=wwleOote5M0
Can you give a link to the firmware you flashed? It'd be useful to know if it contained a modem and/or kernel (or not.)
If it contained a modem, you'll need another modem. If it contained a kernel, you'll need another kernel. We have those. Regardless, you'll need to talk someone into getting you a system image (someone that has the same phone as you and has already rooted.)
Also, do you have CWM recovery installed? Is the existing firmware (as trashed as it might be) rooted? Can you use adb?
im an idiot
garyd9 said:
this reminds me of the following youtube video:
http://www.youtube.com/watch?v=wwleOote5M0
Can you give a link to the firmware you flashed? It'd be useful to know if it contained a modem and/or kernel (or not.)
If it contained a modem, you'll need another modem. If it contained a kernel, you'll need another kernel. We have those. Regardless, you'll need to talk someone into getting you a system image (someone that has the same phone as you and has already rooted.)
Also, do you have CWM recovery installed? Is the existing firmware (as trashed as it might be) rooted? Can you use adb?
Click to expand...
Click to collapse
nope,, I didnt back up anything,,
heres the ROM link I used.
http://forum.xda-developers.com/showthread.php?t=1925402
...
I just opened the file you linked to.. it includes a modem, kernel, etc.
I know you won't be happy with this, but until an ODIN image shows up, you're kind of out of luck. If someone you know has the same phone, you could ask them to do a backup to an external memory card, and then you restore that backup to your device. Assuming the modem wasn't flashed when you installed, that would get you back into business. If a modem was flashed, you'll need to get someone to extract a modem (and I'm not sure how to go about doing that.)
garyd9 said:
Please answer ALL of these questions. I can't help you if you don't answer them all...
Does your phone work now, with the exception of connecting to the mobile network?
Are you familiar with adb? If so, are you able to get a shell via adb?
When you plug your phone into your computer, are you able to copy files to/from the phone?
Which custom recovery do you have installed? CWM recovery or TWRP?
Is your phone rooted? (it probably is with a custom firmware - assuming the phone works at all.)
Click to expand...
Click to collapse
sorry buddy,,,
right now, the phone has no signal, asking for a sim card, which Ive already inserted it.
noepe, I donno what adb is, I tried google it, but I think its too complicate for me.
I'm able to copy files into or from my phone( SD card)
i rooted my phone through this:
http://forum.xda-developers.com/showthread.php?t=1923956
donno if i successed,,, but it has a superSU on my screen after I done it,(guess it count as rooted?) and I may used the TWRP
thank you for your help....
now Im back to my old Iphone 4
I updated that post. Basically, I can't think of anything you can do right now.. until an ODIN dump is available - or if someone gets you a backup you can restore. However, a backup won't flash the proper modem (and it appears you also overwrote the modem.)
garyd9 said:
I updated that post. Basically, I can't think of anything you can do right now.. until an ODIN dump is available - or if someone gets you a backup you can restore. However, a backup won't flash the proper modem (and it appears you also overwrote the modem.)
Click to expand...
Click to collapse
so, if theres a ATT ROM avaiable in the future,,,I can use my phone again by flashing the ATT ROM?
callmejoe1 said:
so, if theres a ATT ROM avaiable in the future,,,I can use my phone again by flashing the ATT ROM?
Click to expand...
Click to collapse
Was the phone originally from AT&T or Rogers?
callmejoe1 said:
First, I'm an idiot,,,got new to android,,had no idea about flashing,, so I just randomly picked a Rom, and turned out its a GT-N7100 ROM, now my phone has no signal at all,,, anyone know how to flash back ? or I have to wait a att ROM come out?
BTW, Im with Rogers.
Thanks:laugh:
Click to expand...
Click to collapse
Welcome to club i've been here for 6 days... it's a crappy feeling especially when its your work phone :[
garyd9 said:
Was the phone originally from AT&T or Rogers?
Click to expand...
Click to collapse
with rogers,but I heard ppl say ATT AND ROGERS‘s ROM can be equivalent , are they ?
callmejoe1 said:
with rogers,but I heard ppl say ATT AND ROGERS‘s ROM can be equivalent , are they ?
Click to expand...
Click to collapse
Perhaps - perhaps not. Until one actually flashes from the other, we don't know. (Many will tell you that they've done it with a different phone model - my answer to that is simply that it was a different phone model. Until its tried with THIS one, we can only guess.)
I think the biggest stumbling block for you right now is the modem. We have a stock kernel and recovery. A "near" stock system partition image can also be made from another device with a simple command. I have to be honest, though, that I have no clue how to extract the modem from these LTE phones.
A recovery (and kernel) can easily be flashed with ODIN (or with dd from a rooted shell.) Same for the system partition (which is, basically, the OS.) Getting a system image might be annoying, as you'd need to find someone with a roger's phone to make it for you, upload it, etc.
The modem, however... I'm not sure how to go about getting that for you. I've never had to create a modem image...
If/when a ODIN package appears, you can use a program that will, basically, reflash your entire phone to stock. Modem, kernel, recovery, bootloader, etc. Everything. Normally, users wouldn't see those ODIN packages, but there are a couple of websites that have access to some samsung servers where they a put. Once they are put there, we can get it...
Take care
Gary
Mobiletechvideos. Have them Jtag it for you.
Sent from my SAMSUNG-SGH-I317 using Tapatalk 2
Just me happy you don't have the note 1 if you would have made that same mistake you could have bricked your phone
envision said:
Just me happy you don't have the note 1 if you would have made that same mistake you could have bricked your phone
Click to expand...
Click to collapse
Yup your very lucky
I firmly believe you cna just flash your modem and kernel on top and it will be fine ,.
im hella busy this weekend but im sure we can get you fix withou a single $$ injected on your part
DAGr8 said:
I firmly believe you cna just flash your modem and kernel on top and it will be fine ,.
im hella busy this weekend but im sure we can get you fix withou a single $$ injected on your part
Click to expand...
Click to collapse
Looking forward to this remedy as this is the reason I am jumping from att Galaxy S 3 to the note2. Want my international dev community back!
Unfortunately so far down here in Southern Florida Miami beach there is no white Note 2 anywhere.
For those that have the ATT version of the Note 2, if you've mistakenly flashed the ROM, I highly suggest visiting your nearest AT&T Device Support Center. Since I've previously worked in those centers, they have a propietary Samsung flashing tool that allows them to flash to the stock ROM, even if it's rooted. Granted they'll be able to tell if you've rooted it or not (which may or may not void the warranty, depending on who you talk to), as long as the phone can turn on and go to firmware recovery mode, the flashing works almost 100% of the time and it's a free service.
However, as I got my Note 2 yesterday, I've contacted my nearest DSC and they said that they don't have the ability to flash the Note 2 yet and they may have that ability to do so in the next few weeks or possibly by the end of the year (if you can wait that long). Being that the associates are just corporate drones, if they can't fix it, they'll more than likely replace your phone under warranty (which I don't suggest since the replacements are refurbished, and besides you should be within the 14 day return period for a new phone).
Sorry if it doesn't help the ones who have the Rogers versions.
DAGr8 said:
I firmly believe you cna just flash your modem and kernel on top and it will be fine ,.
im hella busy this weekend but im sure we can get you fix withou a single $$ injected on your part
Click to expand...
Click to collapse
would you mind if you can post the link for the modem and kernel please?
thank you
DAGr8 said:
I firmly believe you cna just flash your modem and kernel on top and it will be fine ,.
im hella busy this weekend but im sure we can get you fix withou a single $$ injected on your part
Click to expand...
Click to collapse
Im having the same problem. I hope you can roll out a fix!
hi everyone.. i just bought Samsung Galaxy Note II 4G on first december, from Optus Australia..
and last night i try to root, and flashing Omega v7.3 Rom from N7100, it is work well but the IMEI and Signal is gone, and also the S-pen is not working..
and i try use N7105 custom rom http://forum.xda-developers.com/showthread.php?t=1985200
and also my signal is still not detected, but my S-Pen is working back..
somebody please help me...
how to fix my signal problem
benatis said:
and flashing Omega v7.3 Rom from N7100
Click to expand...
Click to collapse
Why in first case did you flash a ROm which isn't intended to be for your device?
Well you killed your EFS partition (bricked)
I hope you mad a EFS backup BEFORE you flashed. So you can restore it and all will be fine.
You could try the Stock Firmware via Mobile Odin if it fixes your EFS problem. No Guarantee here, sometimes it dsoes work and sometimes not.
Good luck to you
Higgins12 said:
Why in first case did you flash a ROm which isn't intended to be for your device?
Well you killed your EFS partition (bricked)
I hope you mad a EFS backup BEFORE you flashed. So you can restore it and all will be fine.
You could try the Stock Firmware via Mobile Odin if it fixes your EFS problem. No Guarantee here, sometimes it dsoes work and sometimes not.
Good luck to you
Click to expand...
Click to collapse
hmm.. i never used Samsung device before.. this is my first Samsung device i have ever..
different with my old HTC devices..
i will try ODIN now... use Stock ROM....
-----
and also, i have tried to wipe data from CWM, why my Note2 device still can boot?
i mean, like not wiped the data completely
benatis said:
hmm.. i never used Samsung deviced before.. this is my first Samsung device i have ever..
different with my HTC devices
Click to expand...
Click to collapse
I believe the reason you are experiencing this issue is because this new firmware you flashed doesn't contain a custom radio and the n7100 firmware did. You will need to find a n7105 radio, flash that through CWM or TWRP and you should be back in business mate.
chrisaw said:
I believe the reason you are experiencing this issue is because this new firmware you flashed doesn't contain a custom radio and the n7100 firmware did. You will need to find a n7105 radio, flash that through CWM or TWRP and you should be back in business mate.
Click to expand...
Click to collapse
where i can download n7105 radio ???
and how to flash the radio?
where i can download the stock Radio, Firmware, and rom of N7105 ???
i Have tried Odin, and flash Stock rom... but i dont know how to wipe data and chache from odin..
i just flash it..
and now, my Signal is appear... lol...
thanks for everyone...
Would be glad to help you but you seem to have skipped the first rule : read, read, read before you do anything else. You even admitted that this is your first Samsung device, so why did u assume that everything should have been htc like ?
Anyhow, you can try to flash the newest 4.1.2 update for the 7105, even though I fear that your problem is your efs folder, and since this is unique for each device, no flashing any rom will put it back in place.
http://forum.xda-developers.com/showthread.php?t=2027586
Good luck,
P_
pakalrtb said:
Would be glad to help you but you seem to have skipped the first rule : read, read, read before you do anything else. You even admitted that this is your first Samsung device, so why did u assume that everything should have been htc like ?
Anyhow, you can try to flash the newest 4.1.2 update for the 7105, even though I fear that your problem is your efs folder, and since this is unique for each device, no flashing any rom will put it back in place.
http://forum.xda-developers.com/showthread.php?t=2027586
Good luck,
P_
Click to expand...
Click to collapse
yah.. i have flash that ROM just now..
but, why my signal is verry in poor level? only showing 2 bar?
im sorry, im not experienced with samsung devices
Since you said that the phone is from Australia and Optus you may want to flash its original firmware back in place :
http://www.sammobile.com/firmware/?page=3&model=GT-N7105&pcode=OPS&os=1&type=1#firmware
If you do not use the phone in Australia you may want to find a firmware (if available) for your device/geographical region.
P_
benatis said:
i Have tried Odin, and flash Stock rom... but i dont know how to wipe data and chache from odin..
i just flash it..
and now, my Signal is appear... lol...
thanks for everyone...
Click to expand...
Click to collapse
I am facing the same problem you had before, however when i try to Odin the stock 4.1.1 firmware back to the phone, it stops at the Samsung logo when restarting. I have to force back to recovery mode to flash the omega back to have it start again. Can you please tell me the steps you did on putting back to stock firmware? thanks
If you haven't yet reflashed the EFS partition (don't do that, ever ! unless you have a good reundant set of backups), you actually don't need to reflash to stock firmware at all (and I doubt that it'd do any good anyways. It just puts back a generic EFS with the files set at default values, but certainly can't put back the data you had in your own device's EFS, this is unique to each phone).
Just head on over to the Galaxy S2 forums and look for a thread called "Restore your IMEI in 9 steps" (something like that. There's actually quite a number of threads describing the same procedure, you can find them by searching "samsung restore imei" in all forums, works just as well).
I had the same problem the other day (and no backup of course, silly and impatient me... ), it worked like a charm..
It's topics like this that i know that People Will get Hurt on. Come on, read and study before doing anything on a smartphone. There's a reason why android doesn't come with administrator rights from factory.
Sent from my GT-N7100 using Tapatalk 2
Hey guys, I think I screwed up. I think that I lost my IMEI through flashing it and I didn't make a back up. It says 0 and only very few of the *# codes work, the *#7285# and #22745927 codes do absolutely nothing and the only one that I know of that works is *#*#4636#*#* which doesn't help me at all. Most programs that I use don't detect the phone correctly or my phones just downright wrecked. Example is DFS says CPS N/A in every section and Samsung MEID Repair says "Unhandled exception has occurred in your application" when I try to connect it to my phone.
I'm running CM11 4.4.1 and I had the problem when I was running a 4.3 ROM. Also I have data and I can make calls. Its just that I cant send MMS and I drop to edge over time and stay on edge until I restart.
Any help would be greatly appreciated. Everyone I call is saying it'll cost $65 - $75 IF they can even fix it.
Try to use nv writer to inject the imei.
http://forum.xda-developers.com/showthread.php?t=1804117
Note that if you reinject IMEI, it might screw up your network
audit13 said:
Try to use nv writer to inject the imei.
http://forum.xda-developers.com/showthread.php?t=1804117
Click to expand...
Click to collapse
I wish I could, When I try to use it, it says "Failed.. phone does not answer". Keep in mind that *#7284# doesnt do anything at all.
Did you know that you need to be completely stock in order to use the code?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
pcshano said:
Did you know that you need to be completely stock in order to use the code?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I did not. That helps a LOT. Thank you so much. I havent tried going back yet, I'm gonna be more cautious about what i do now. Can I go back to stock from CM11 4.4.1 without screwing anything up? I keep seeing that you cant downgrade. Is that the case or is it just the case with official android roms?
Thank you so much, I feel like with your help I may be able to fix this. What im thinking that I have to do (I'll wait for your opinion) is that I should flash to stock, use the nv reader/writer, then ill be able to reroot it? When you say that it could screw up the network, what exactly do you mean?
chasetacos said:
I did not. That helps a LOT. Thank you so much. I havent tried going back yet, I'm gonna be more cautious about what i do now. Can I go back to stock from CM11 4.4.1 without screwing anything up? I keep seeing that you cant downgrade. Is that the case or is it just the case with official android roms?
Thank you so much, I feel like with your help I may be able to fix this. What im thinking that I have to do (I'll wait for your opinion) is that I should flash to stock, use the nv reader/writer, then ill be able to reroot it? When you say that it could screw up the network, what exactly do you mean?
Click to expand...
Click to collapse
I'm not sure what bootloader are you using
but IF your phone is fully unlocked, it doesn't matter, just flash 4.3 Stock and you're good to go
check out this post if you need help getting back to stock http://forum.xda-developers.com/showthread.php?t=2658486
the reason why you see people keep saying you can't "Downgrade" is mostly due to the bootloader you have, and it only apply to if and only if you're downgrading from MJB bootloader to a older version of Touchwiz (ie. Touchwiz 4.3 which will obviously come with MJB, thus you can't downgrade to 4.2 or 4.1 versions of touchwiz), not AOSP. if you're on AOSP in which CM is one, yes you can go from one AOSP to another, but no one does it because most of the time newer > older =D
pcshano said:
I'm not sure what bootloader are you using
but IF your phone is fully unlocked, it doesn't matter, just flash 4.3 Stock and you're good to go
check out this post if you need help getting back to stock http://forum.xda-developers.com/showthread.php?t=2658486
the reason why you see people keep saying you can't "Downgrade" is mostly due to the bootloader you have, and it only apply to if and only if you're downgrading from MJB bootloader to a older version of Touchwiz (ie. Touchwiz 4.3 which will obviously come with MJB, thus you can't downgrade to 4.2 or 4.1 versions of touchwiz), not AOSP. if you're on AOSP in which CM is one, yes you can go from one AOSP to another, but no one does it because most of the time newer > older =D
Click to expand...
Click to collapse
Cool. Im using CWM 6.0.4.3. Youre saying flash back to stock, then use the codes and the NV reader/writer? Also, when using the ZIP. am I using this through CWM "install zip"?
chasetacos said:
Cool. Im using CWM 6.0.4.3. Youre saying flash back to stock, then use the codes and the NV reader/writer? Also, when using the ZIP. am I using this through CWM "install zip"?
Click to expand...
Click to collapse
Yes.
but again you might want to update it to latest version since according to this http://forum.xda-developers.com/showthread.php?t=2658486, he mentioned version 6.0.4.5 and 6.0.4.7 though he didn't say if it's necessary to be but to be safe, you should so that you won't run into any issues.
though again, let me warn you, Reinjecting your IMEI, will work, BUT at the same time, it might screw up with your broadband
I experienced it once with one of my S3 and it stuck on either E or G network.. and I had to fix it by copy my efs folder to that phone in order to fix(and unless you have a good friend with S3 phone with same model, or own more than 1 S3, you won't be able to do it since nobody want to share, apply to me as well)
pcshano said:
Yes.
but again you might want to update it to latest version since according to this http://forum.xda-developers.com/showthread.php?t=2658486, he mentioned version 6.0.4.5 and 6.0.4.7 though he didn't say if it's necessary to be but to be safe, you should so that you won't run into any issues.
Click to expand...
Click to collapse
Cool. I Will do this and I will keep you updated. Itll be just a few moments before I complete the process
pcshano said:
Yes.
but again you might want to update it to latest version since according to this http://forum.xda-developers.com/showthread.php?t=2658486, he mentioned version 6.0.4.5 and 6.0.4.7 though he didn't say if it's necessary to be but to be safe, you should so that you won't run into any issues.
though again, let me warn you, Reinjecting your IMEI, will work, BUT at the same time, it might screw up with your broadband
I experienced it once with one of my S3 and it stuck on either E or G network.. and I had to fix it by copy my efs folder to that phone in order to fix(and unless you have a good friend with S3 phone with same model, or own more than 1 S3, you won't be able to do it since nobody want to share, apply to me as well)
Click to expand...
Click to collapse
So when I try to flash the stock I get an error status 7. Any advice?
chasetacos said:
So when I try to flash the stock I get an error status 7. Any advice?
Click to expand...
Click to collapse
funny a lot of people who use CWM got this error when trying to get back to stock lol
try TWRP.. it should definitely fix it
Cool. It may not be till tonight or tomorrow till I respond, I'm about to have a project m competition. I'll let you know how it goes as soon as I get a chance.
pcshano said:
funny a lot of people who use CWM got this error when trying to get back to stock lol
try TWRP.. it should definitely fix it
Click to expand...
Click to collapse
So now that Ive restored to stock, I have a transparent window with yellow text in it. it reads a bunch of info on the phone. It also said that it was in factory mode?
pcshano said:
funny a lot of people who use CWM got this error when trying to get back to stock lol
try TWRP.. it should definitely fix it
Click to expand...
Click to collapse
So despite being stuck in factory mode I was able to write the NV and luckily I dont have any new network problems as far as I know. However my IMEI now says / 00 and in the phone info it says "unknown"
So this is my progress so far. I have made connection with the NV items reader and I have saved the NV file. when i rewrote it i noticed that my imei is / 00 and it says unknown in the phone info. I have my imei and my converted imei and i was going to insert it into line 00550 but that line says "00550 (0x0226) - Inactive item". Factory mode is still on, I have edited the text files for both factory mode and keystr from ON to OFF and back again rebooting my phone each time and getting no result.
So im stuck in factory mode with / 00 imei. I can however make connection with programs now, I feel like im moving forward.
I feel like it may be worth noting that ive never ever seen a nv_data.bin in my phone....
chasetacos said:
So this is my progress so far. I have made connection with the NV items reader and I have saved the NV file. when i rewrote it i noticed that my imei is / 00 and it says unknown in the phone info. I have my imei and my converted imei and i was going to insert it into line 00550 but that line says "00550 (0x0226) - Inactive item". Factory mode is still on, I have edited the text files for both factory mode and keystr from ON to OFF and back again rebooting my phone each time and getting no result.
So im stuck in factory mode with / 00 imei. I can however make connection with programs now, I feel like im moving forward.
I feel like it may be worth noting that ive never ever seen a nv_data.bin in my phone....
Click to expand...
Click to collapse
make sure that you take your SIM out before injecting imei... then try again
and nv_data.bin is in your efs folder which you can only see it if you have some sort of root explorer
pcshano said:
make sure that you take your SIM out before injecting imei... then try again
and nv_data.bin is in your efs folder which you can only see it if you have some sort of root explorer
Click to expand...
Click to collapse
Still nothing, im getting the same result. This Nv data bin file is not in there. i mean, unless i dont know where to look, but ive checked the whole EFS folder and its not in there...
Hi try flash UCUEMJB 4.3 stock rom via odin .. I have same problem and the stock ROM fix my problem
Sent from my GT-P5113 using XDA Premium 4 mobile app
---------- Post added at 06:24 PM ---------- Previous post was at 06:06 PM ----------
I fix mine with this .....
Ok... I hated to see the posts about the tar file bricking a couple of phones. I had taken it down so not to brick anyone else's phone. But with over 400 downloads and only 2 reports I feel that it was fine, but in either case I have redone it. I have flashed it many many time now and my phone is fine.
Please only use Odin 3.0.7 http://forum.xda-developers.com/showthread.php?t=1722686
Make sure Auto Reboot and Re-Partition are checked. Uncheck F. Reset Time and anything else that might be checked.
Check and load the file in the PDA slot.
Start Flash and wait till it the phone reboots.
I747UCUEMJB 4.3 Odin flashable tar.
http://www.androidfilehost.com/?fid=23329332407590581
Sent from my GT-P5113 using XDA Premium 4 mobile app
elcocolo50 said:
Hi try flash UCUEMJB 4.3 stock rom via odin .. I have same problem and the stock ROM fix my problem
Sent from my GT-P5113 using XDA Premium 4 mobile app
---------- Post added at 06:24 PM ---------- Previous post was at 06:06 PM ----------
I fix mine with this .....
Ok... I hated to see the posts about the tar file bricking a couple of phones. I had taken it down so not to brick anyone else's phone. But with over 400 downloads and only 2 reports I feel that it was fine, but in either case I have redone it. I have flashed it many many time now and my phone is fine.
Please only use Odin 3.0.7 http://forum.xda-developers.com/showthread.php?t=1722686
Make sure Auto Reboot and Re-Partition are checked. Uncheck F. Reset Time and anything else that might be checked.
Check and load the file in the PDA slot.
Start Flash and wait till it the phone reboots.
I747UCUEMJB 4.3 Odin flashable tar.
http://www.androidfilehost.com/?fid=23329332407590581
Sent from my GT-P5113 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Unfortunately that did nothing . I might just have to cry about it
Hi all,
I have a Bell Canada Samsung Galaxy S3 that I can't get the modem to work on. I have Philz recovery on it and have tried a few modem files but neither the wireless or the mobile carrier works.
I have tried putting cyanogenmod on it but am back on a stock ROM at this point. I am at a bit of a loss as to what to do.
The phone boots fine, looks all normal but I just can't get on the mobile network(tried multiple SIM's).
I am really hoping you can help!
Does your phone display the correct imei when you dial *#06#??
It does, it shows my IMEI with a /5 at the end.
At this point, I am running I747MVLUEMK5_I747MOYCEMK5_BMC
I also do show cellular signal but can't seem to connect. When I scan wireless networks, I pick nothing up.
Any ideas?
Thanks again!
audit13 said:
Does your phone display the correct imei when you dial *#06#??
Click to expand...
Click to collapse
Is the phone blacklisted?
I don't think so, how can I verify that? I did buy it used just over a year ago and it only broke about a month ago?
audit13 said:
Is the phone blacklisted?
Click to expand...
Click to collapse
You can check your imei here: http://www.protectyourdata.ca/check-the-status-of-your-device-in-canada/
All clean on there!
audit13 said:
You can check your imei here: http://www.protectyourdata.ca/check-the-status-of-your-device-in-canada/
Click to expand...
Click to collapse
You've had the phone for a while so I didn't think it would be blacklisted.
Since you have the 4.3 bootloader, you need to have a compatible modem and, from my experience, only the mk5 modem will work.
Did you use Odin to flash back to stock?
Yes, that is how I put the current stock firmware on it. I had cyanogenmod on it at one point...
audit13 said:
You've had the phone for a while so I didn't think it would be blacklisted.
Since you have the 4.3 bootloader, you need to have a compatible modem and, from my experience, only the mk5 modem will work.
Did you use Odin to flash back to stock?
Click to expand...
Click to collapse
I am at a loss as to why you cannot connect to a network. Which carrier do you want to connect with?
audit13 said:
I am at a loss as to why you cannot connect to a network. Which carrier do you want to connect with?
Click to expand...
Click to collapse
Hello i hope i can help i have to ran into this problem before and here is what i did to fix it.
Flash the modem using the dl from this forum
http://forum.xda-developers.com/showthread.php?t=2745607
also once you are done you will need the nv writer and the i747 dl froim teh same forum that will get you all fixed up i promise. Just follow the steps and ready the whole thing first. I looked for three days and finally resolved it with Larrys help
scoeas1982 said:
Hello i hope i can help i have to ran into this problem before and here is what i did to fix it.
Flash the modem using the dl from this forum
http://forum.xda-developers.com/showthread.php?t=2745607
also once you are done you will need the nv writer and the i747 dl froim teh same forum that will get you all fixed up i promise. Just follow the steps and ready the whole thing first. I looked for three days and finally resolved it with Larrys help
Click to expand...
Click to collapse
Is the i747 modem compatible with the i747m?