Hey Folks,
I was having trouble with connections in the past few days and decided to reflash my phone. Before my problems appeared, I had unlocked the phone to try NFSFAN's ROM, but since I didn't like it I downgraded to the Original ROM, which was working great prior to that. That's when I noticed I couldn't simply run the upgrade from the USB anymore! I finally managed to get going OK running extracting the nbh fole from the OEM EXE file then updating from the memory card itself after putting it into boot.
However, after a few days I noticed slowdowns and interrupted data connections so I decided to reflash once again tonight. I must add that my signal strength was just as good as before, so I doubt the issue is with the radio itself.
Before reloading the OEM ROM again, I installed the 0.40 coke unlocker so as to be able to relock the phone during the Bell OEM ROM update from storage card again. It now shows as 2.01.0000 just like it should.
So after everything finished loading, I noticed the phone was off, so I turned it back on from the comm manager, but I noticed no activity in the antenna icon, no 1X or Ev and I got "No Service" on the top left bar. I read elsewhere that I may need an A-Key, when I look at it using EPST (##778#), there is nothing there. Also, I noticed that my activation date (dec 27, 2008) disappeared as well, as did my slot cycle index setting, which reverted to 2 from my setting of 0.
Does flashing mess up the EPST settings? I've tried reflashing twice, to no avail... Still No Serrvice!
Any ideas what I could do myself? I need this phone for work!!!
TIA for your help!
Sounds to me like you need to run the activation and then re-authenticate. Are you on Verizon? If so... dial *228 and <SEND> then choose option #1. Once that completes, soft reset the phone. Try to make a call... if it doesn't work, then call #8899 and talk to mobile security. Tell them you just updated your phone and you need to re-authenticate. Takes about 5 minutes or so...
rzawora said:
Sounds to me like you need to run the activation and then re-authenticate. Are you on Verizon? If so... dial *228 and <SEND> then choose option #1. Once that completes, soft reset the phone. Try to make a call... if it doesn't work, then call #8899 and talk to mobile security. Tell them you just updated your phone and you need to re-authenticate. Takes about 5 minutes or so...
Click to expand...
Click to collapse
Unfortunately I have no signal whatsoever, the phone (radio) simply won't turn on. I am with Bell Mobility. Even with a signal, this type of work needs to be sent out for with Bell Mobility.
I talked to tech service this morning and after trying all the usual things (cold boot, let customizations run...), they basically told me my phone was defective, and that they would send me another one... which would take at least 2 weeks , as they are backordered now!
I have written more about what I did on this post on the ppcgeeks forum, check it out if you have the time, in case that would help...
Thanks for your help, it's much appreciated
I just had a similar problem. I flashed my Sprint TOUCH with an Alltel rom...then i flashed back to WDM's latest. But seems the alltel rom had a radio upgrade, but the WDM rom didnt. So I had to first flash the sprint official rom, then back to WDM and it worked
Thanks for keeping the thread alive
Believe me, I've tried everything I could think of and after much tought everything points towards a hardware problem. The uncontrolled loss of EPST data sure points to that. Heck, how can the "date first activated" simply disappear otherwise? Besides, I barely managed to reflash everything back to OEM, couldn't get it loaded using the OEM Carrier EXE (RUU error 328), even getting an error using the SD card method, saying update failed! I consider myself lucky that it finally flashed after that...
i once lost my service by flashing the wrong carrier and this is what i did.
(i'm with bell)
Step 1
Hammer in ##778#
Pick edit
Tap in unlock code (ESN #)
Tap Menu
Tap OK
Tap Reset Device
Once your device boots back up,
Hammer in ## "ESN"# without the quotations
MDN = your9 digit Cell Number
MSID = your 9 digit Cell number
MENU/then OK
--------------------------------------------------------------------------------------------------------
if still nothing then......
Step 2 and 3
Or try Bell Carrier Cab
or....
If you have OEM rom installed then run the IOTA cab file
---------------------------------------------------------------------------------------------------------
Step 4
If those things didn't work then download the ImCokeMan's Unlocker .40
double click on it with your phone hooked up and follow the directions on your
PC.
After Installed you will then have a bootloader of .40 with which to flash the Bell OEM Rom
After flashing the bell oem rom if you don't have data then go back up to Step 1 and it should
work after that.
After Flashing bell oem rom then go to htc site and download the latest rom from bell for the touch.
Then unlock with unlocker 2.31
after that you can flash a custom rom.
personally i have flashed about twenty times and nfsfan's are the best BAR-NONE.
*then again that is what i did , what u do is entirely up to you and your personal responsibility.
Thanks for your input. Fortunately I've gotten my replacement, and even got a spare one as I can't afford to be without a phone should problems happen again.
As for your step by step plan, it's very nicely written. However, I never loaded anything not for my carrier, and never tried to downgrade the radio so I'm a bit perplexed as to why this could have happened, as if I in fact had loaded incompatible code. Bottom line, my phone simply wouldn't accept running the Carrier EXE anymore, after I decided to revert back to OEM after trying NFSFAN's ROM for a day.
I have since looked it up and it learned that is apparently important to put the device manually in boot loader mode before connecting it to the PC and running the Carrier EXE (OEM RUU) from there. That may have been one important mistake.
Also, something else no one mentions is that when you load the 0.40 unlocker, you must reload your OEM ROM right after. In other words, run the 0.40 and when done, shut the phone down. I don't think you should let your phone turn itself on after that, especially sinmce you have a 3.XX radio on! Next time, I'll simply load the 0.40 unloacker as "VOGUIMG.nbh" from the fat 32 formatted <=2GB SD card, the turn it off, remove the SD card then put it back into boot loader mode, THEN connect to the PC and run the Carrier EXE from there. This is not clearly explained anywhere, and I did not do it this way, and this could have been important mistake number 2.
Running ROMs from SD cards is fine and dandy when you simply want to replace ROMs (or in this case replace the boot loader), however, if you run into a problem serious enough like the one I experienced, that requires reloading the carrier EXE, simply reloading its ROM obviously proved to be insufficient, as the carrier exe also contains another EXE (PPSTPatch.exe), a cab (PPST____.cab) and even a small nbh as well (Special_4350_For_BM.nbh), which are impossible to load by hand (I tried!) and quite possibly are vital to proper operation, simply loading the main VOGUIMG.nbh not being enough to make it run right.
I learned all that the hard way... As for the phone, since the RUU error code basically said "this type of error requires sending to the factory", and nowhere did I find a method, on any of the forums, to correct this error, I didn't have much of a choice but to send it in...
I am however still wondering if this could have been solved by finding an alternate method of reloading the carrier exe (like putting it in boot loader mode before connecting and running the RUU), even if everything seemed to indicate some hardware problem.
So please don't be shy, thank you for your comments and please! Do keep them coming, hopefully we'll be able to get to the bottom of this!
Related
I have been passed a HTC Desire to try and fix after a friend of mine ran into issues trying to put Froyo on it. It was originally with Virgin (Virgin boot screen) but was not locked as other sims were usable.
I've tried various different methods to get it up and running but suspect something he has done with his attempts has caused serious issues - also he is not all that clued up and cannot remember exactly what he did - he did mention that RUU update failed, and also an image he had tried to flash from his sd card had got part way through and then locked up on the radio update.
With the original sim and memory card in, the phone will constantly reboot or just stick at the HTC logo. Take the memory and sim cards out, the phone will boot but system wont launch properly so cant get into settings to enable debugging so I can access the device via ADB. I can get to the fastboot screen, and to the Vol Down-Power screen on start, but if I select recovery it stays on HTC logo and goes nowhere.
I have managed to get HBOOT downgraded to 0.8, but when trying to put on original Virgin RUU it says the main version is older (probably because I'm trying to install an older version over a newer one). The stock Froyo RUU fails and tells me wrong HBOOT and sometimes gives a CID error. Although the phone is not locked, I suspect it will still need a goldcard, but cant create one as I cant get ADB access to the phone.
Sorry if this is a bit of a mess but at work and trying to take calls as well as write this and fix the darned phone. I;m not unfamiliar with methods used to get the phone rooted, but not well up on troubleshooting or working around these issues I have.
Any help would be appreciated.
You should be able to restore it by installing this RUU with a working goldcard:
http://shipped-roms.com/shipped/Bra...3.00.32U_5.09.00.20_release_140022_signed.exe
If you get a CID error your goldcard isn't working. There should be no version error with this.
Thanks for the reply....however how can I create a goldcard when I cant get the phone to a point where I can get my pc to recognise it? All the goldcard methods I have seen/tried involve having the usb plugged in and debugging enabled - cant get to that stage as phone wont boot - reboot loop most of the time and when I do occassionally get to the os it doesnt last, it will reboot after a few seconds. Anything else I could do? Or, could I use the card in other phone and create the goldcard in that and transfer over? I do have my own working Desire handset.
Don't know much about this but have read that a goldcard is unique to the SD card not the phone so you could create one on your phone and then use it in your mates. Also, from what I've read it would be worthwhile wiping your mates SD card (make sure he's not added a partition to it), copying a Rom to it, and try to install it using Rom manager (or whatever recovery program which was used to root the phone)
Ok, I used my own phone to sort out the goldcard and currently trying that out now...will keep you posted. Just started the RUU Stock Froyo and seems to have got further so far. Wish me luck!
Mmmmm....ok the RUU worked, but when it restarted (with original goldcard/memory card in, it kept rebooting. It did start once, got to initial setup then promptly rebooted. I swapped out the memory card (no sim in at all by the way at any point up to now) to my own card and after one final reboot it did start up. It doesnt seem stable at all with the original memory card, and still not entirely stable with my card. Could this be a phone fault? Im assuming if the RUU got through all its stages then all areas and files on the phone have been updated correctly and are all correct? Could past failures at updates etc have caused an issue elsewhere?
Have you wiped the various caches? As far as I can make out you need to make sure everything is wiped. I read a post on the OpenDesire thread which suggested that clockworkrom, if that is the recovery program you have installed, may not wipe one of the caches (possibly the dalvik cache) correctly. They recommended another recovery program called something like AmonRu. Although I can't really help you it might be worthwhile saying how the phone was rooted.
Ok, none of this was to root the phone. It was to debrand and put on the HTC Desire Froyo build. Not a custom rom, the standard RUU.
As far as I was aware, an RUU restore of the phone would wipe the appropiate caches, but correct me if I'm wrong. The phone now starts with the standard HTC startup and sound and for all intents and purposes is working, but just cant explain the random reboots. These seem to be worse with the 8GB card that my mate gave me with it. Although, after trying mine and putting the original one back in it seems to have stayed stable up to now. I'm beginning to wonder if there may be an issue with the memory card slot - another swap of the memory card again will probably trigger the reboots once more.
We will see how it goes anyway.
You've got a hardware fault. The RUU will completely reflash the phone, so if it flashed successfully but is still rebooting randomly, it can't be software.
Your probably right. Just started to try and do a downgrade, and after putting the PB99.IMG file on the gold card I made earlier, then starting the downgrade I noticed it stuck at about 98% on the radio update (second item in the list). I'm going to leave it a while to see if I get an error but I suspect it will not move or do anything.
Having gone through this process before on my own handset, I know it doesn't take anywhere near this long. Thing that confuses me though is that the RUU process I went through before went through with no issues - so why would that be able to successfully install a radio update and not this downgrade process? Anyone else had this happen to them?
Update: Ok, leaving this now as I've exhausted all avenues and its obvious the phone is not going to play ball. On another RUU flash it failed (and looking at the logs it was at the radio section and mentioned a partition update failure). A subsequent RUU flash was successful, so at least I've got it back to stock (although it doesnt stay booted long enough to even get the initial setup wizard done now). Passing it back to my friend tomorrow and hope he can get a warranty repair. Just a shame I couldn't get it back to the Virgin firmware. Thanks all those that helped anyway, much appreciated.
I went to the Sprint store with my friend last week to swap our phones so he could see what using a smartphone is like before actually buying one. The guys there put my phone onto an old Samsung Rant and shortly after, realized that because my phone was running Cyanogen Mod I couldn't get his plan on my phone.
Anyway, they threw my number back on my phone and ever since it has not been able to get on the internet.
I backed up my phone and wiped everything twice. Once with Amon's Recovery, and once using clockwork. Then I did it two more times and put an entire different rom on it (Fresh 3.5.0.1). I updated my radio, as well.
So, in the end I restored back to my original backup of the Cyanogen Mod and haven't done anything after that. I tried to use HTC's stock .exe file to restore it to Stock but I got USB errors and it couldn't find my phone.
If it's any help, when I had the sense rom on it, I got an Error saying
"Error Code 67: Registration failure. Press ok for options. Your PCS Vision username and/or password may be incorrect. Please try again."
Any help is MUCH appreciated.
A colleague of mine has an incredible that every few days reboots into a continuous boot loop. It takes removing the battery for it to boot normally, and then a few days later it does it again.
He has tried a reset, and it doesn't fix the problem. This is an unhacked unrooted stock Incredible with what ever updates came from Verizon/HTC over the air.
I'm wondering if it would help to reflash it to virgin stock in case something is corrupted. In fact its also possible that one of the HTC updates caused the problems, since it seems to have started about the time of an update.
I have a Samsung phone and am familiar with the procedure for Samsung (Kies, Odin, etc) but don't know what to tell him about HTC.
What is the procedure for reflashing to stock, and perhaps selecting a stock version older than the latest for HTC phones?
kmandel said:
A colleague of mine has an incredible that every few days reboots into a continuous boot loop. It takes removing the battery for it to boot normally, and then a few days later it does it again.
He has tried a reset, and it doesn't fix the problem. This is an unhacked unrooted stock Incredible with what ever updates came from Verizon/HTC over the air.
I'm wondering if it would help to reflash it to virgin stock in case something is corrupted. In fact its also possible that one of the HTC updates caused the problems, since it seems to have started about the time of an update.
I have a Samsung phone and am familiar with the procedure for Samsung (Kies, Odin, etc) but don't know what to tell him about HTC.
What is the procedure for reflashing to stock, and perhaps selecting a stock version older than the latest for HTC phones?
Click to expand...
Click to collapse
You can reflash the phone to stock with what incredible users call an ruu (rom update utility), however flashing older versions or downgrading the os is not allowed with s-on (security on). His best bet in my opinion would be to root and s-off the phone, and then flash a custom rom. However if hes not into all of that he can try to do an ruu and see if it fixes things. Doing so will wipe the phone compleetly and he will loose all of his apps and data. A pc running windows xp or newer is required.
1. Download the ruu http://dinc.does-it.net/Stock_Image...0_Incredible_C_hboot_1.02.0000_4.08.605.2.exe, and place it somewhere on your pc.
2. Download and install HTC Sync http://dinc.does-it.net/HTC-Sync/3.0.5606/setup_3.0.5606.exe.
3. On the phone go to menu - settings - applications, uncheck fastboot if it is checked and then select development, and make sure usb debugging is checked.
4. Connect the phone to the pc with the usb cable, and wait for any drivers to install on the pc. The phone should be in charge only mode.
5. On the pc run the ruu file and follow the instructions it gives you.
If all goes well the phone will be like it just came from the factory. If doing all of this is to technical for him he can take it into a verizon store and they will do it for him at little or no charge.
cmlusco said:
If all goes well the phone will be like it just came from the factory. If doing all of this is to technical for him he can take it into a verizon store and they will do it for him at little or no charge.
Click to expand...
Click to collapse
Well not like it came from the factory originally. That would be Froyo, and this procedure would presumably get the last official (and maybe problem some Gingerbread). Is that right?
Also, I'm surprised to hear that a Verizon store could do a flash. My only experience is with T-mobile and they can't do any better than use the "factory reset" menu that just clears settings.
kmandel said:
Well not like it came from the factory originally. That would be Froyo, and this procedure would presumably get the last official (and maybe problem some Gingerbread). Is that right?
Also, I'm surprised to hear that a Verizon store could do a flash. My only experience is with T-mobile and they can't do any better than use the "factory reset" menu that just clears settings.
Click to expand...
Click to collapse
Well not like it originally came from the factory 2 years ago (with froyo), but if they were still selling them today or you get a replacement, that is how it would come from the factory. The last update 4.08.605.2 fixed all the major issues and shouldnt give any major trouble. The only other option would be to root.
Verizion is pretty good with customer service, you may have to find a knowledgable employee but they can do it for you.
We tried the "ruu" approach without success. The drivers installed on the PC, the phone goes into debug mode, and we can even run "adb" manually and talk to the phone. However, when either "ruu" or "Ht Sync" try to talk to the phone they just say the phone is not connected.
If we run the task manager on windows we can actually see "ruu" invoking "adb" and there is no long timeout. It appears that ruu just doesn't like the answers.
Again running adb manually for example with the shell option seems to do all you expect adb to do. This is with both the versions linked above and the updates they end up offering.
Any ideas?
OK, found a mistake. I didn't realize that to do the ruu flash I needed to turn off the phone and vol-down/power it into htboot mode.
With that done the update program sees the phone notices it has lastest firmware and offers to update it to the same version. I say yes, and the phone reboots and the PC tells me it will take 10 minutes to flash, then 2 seconds later tells me it succeeded and the phone reboots.
Obviously it did not flash anything. Am I missing something?
Also any pointers on how to flash an earlier stock rom (and where to find it)?
Okay, I have spent hours upon hours searching the subject and it becomes a bit hard to find a correct procedure as there are tons of hearsay and perhaps singular examples because no one really seems to fully grasp the concept of the issue. So I guess different fixes work for different people.
But here is my issue:
I have a Wind T889V. Was working fine, done lots of ROM ranges, big geek, ETC.
Well, I made a mistake and I flashed T889UVBMD1 Radio. For whatever reason I flashed it since thanks to so many ROMs flashed I forgot that I have a T889V and not a T889.
So that killed my radio. No 3G, no data, IMEI and Baseband, Mobile Network type say "unknown." I tried flashing proper radio immediately after and my phone WOULD bootup but then would reboot about 3-5 minutes into it. The reboot cycle was so short it would hardly let me do anything with it.
Then I read that booting up to an early version of stock might bring IMEI info back. Did not work. In fact, my phone boots up minutes after being being turn on unless I flash the T889UVBMD1 Radio. So I think I am stuck with it. T889V radios I have tried boots the phone up sometimes and sometimes it does not, or it cycles right at the Samsung screen.
Yes, I did a EFS backup when I first rooted. However the process only g=created a IMG file which I kept safe. Which is 20 megs in size. However, when I try to open it with a 7.Zip to look inside it appears to be empty!! I have done a restore multiple times and nothing happens. Even though the process seems to go without errors.
I check the EFS folder on my phone as it is still in there. However I do not see any .bin files. And under IMEI, there is only one file:
mps_cod.dat which when open only has the words GLW in it. That is it. So needless to say, that is not the way it should be.
I have tried to install T889VVLALJ4 (which is the original ROM through CWM) and it soft loops, even though members have said that it has magically saved their phone it sounds to me like perhaps in those cases the EFS folder still had the data and the flashing of the rom simply just rediscovered the info.
I have been reading about a member who was able to inject the IMEI info the folder but I have not been able to get in touch with him or find the exact procedure how it was done.
My last resort would be to try to restore to original, soft looping and all and take it back to the service provider see what they say.
Thoughts? And Thank you.
Try restoring via kies.
http://forum.xda-developers.com/showthread.php?p=46164552
Sent from my SGH-T889 using xda app-developers app
ciphercodes said:
Try restoring via kies.
http://forum.xda-developers.com/showthread.php?p=46164552
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Okay.
For those in the same issue as me, the problem with trying to solve it KIES is that it will look to see if your phone is factory everything. If you are like me, and you go the FACTORY ROM/RESET route then your phone will reboot every 30 seconds to every 2 minutes. So KIES will never have time to recognize your phone, assuming that your phone boots at all.
Then if you go back to the issue I had... which was to put the T889 Modem which stops your phone from rooting, then KIES will tell you the phone is not suitable for an update. So there goes your option.
The best way for the time being is to use the AWS QCN (Google this) route. Which enables the AWS on your phone and allows you to at least to connect to your provider. As of this writing and three days of doing work, I have found a fix, that sort of fixes the phone. I have tested with a few people and they hear some background noise on Wind. So it is not a full fix, but it is a round about way to have your phone sort of back.
The biggest issue I have found after doing in-depth search on this issue and most so-called fixes is that most users have no bloody clue what the issue is so for some it is easier to fix than for others and as such you get a lot of false negative fixes.
The fact is I have found so far is that there is no 100% that I have found.
You first need to know if the issue is with the Modem, your IMEI getting fudged, your EFS folder messing up and whether once it got fudged whether your EFS info still remains on your phone. Different fixes fix different issues.
I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.
gvazquez82 said:
I apologize in advance if any of this makes you roll your eyes at my stupidity.
Good Afternoon
I have an ATT samsung galaxy s3, Because of the glitches with 4.3 I was experiencing I decided to install custom software on my phone. So I looked up guides and got everything I needed. I did manage to get root access, and verified with super user. I also installed TWRP and CWM because each kept giving me errors when I tried to install CM 11 onto my phone. I tried CWM first, and when that didn't work I tried TWRP. It says there was no MD5 information found when I try to install any mod. how ever I have used the md5 file checker program and the MD5 matches up to what was listed in this one for example.
http://forum.xda-developers.com/show....php?t=2518998
Download:
CM 11.0 Unofficial Beta 7 for d2tmo and d2att
MD5: ef93957db1e6704f23f9015231a82826
So the MD5 matches, yet when I try to install it keeps giving me errors. I also tried other versions of CM that I found on here via links. Right now my phone has no OS as another guide I read some where also said to wipe system data (sorry if that was stupid, I was just following a guideline) And even more stupid, no I don't have a backup because in my naivety and stupidity I didn't think I'd need one as it seemed so simple from all the guides and videos I'd seen.
Yesterday a friend of mine knowledgeable with tech stuff took one of the original stock Image ROMs I'd downloaded and using linux and some program he managed to do some crazy stuff I can't even describe on here. All I saw was a lot of typing of command lines and it got my phone working again, how ever it wasn't exactly the stock image I guess because the phone would not make or receive calls/texts.
Since my phone was powering on again and the android OS was loading I figured I could connect it to my computer and use KIES to download the official latest update so my phone would be back on the legit software. But trying to do that...well broke my phone again. So I'm at a loss now of what to do. Right now I can still get to download mode on my phone, but when I try to get into recovery mode I get an error that "firmware upgrade encountered an issue. Please select recovery mode in KIES & try again." Which I've tried, and every time I try it gives me an error message.So I'm at a loss of what to do next.
So I'd like to get a working OS on my phone asap so I can get calls and texts.
Any help would be greatly appreciated. And being new I'm sorry if I broke any taboos or did not give some information that is typically given when describing a problem.
Click to expand...
Click to collapse
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient
MrHaPpY66 said:
same error happened to me yesterday and spent the whole day figuring it out. get into download mode. boot up ODIN and reflash your preferred custom recovery. after that, i couldn't find anything else to restore my phone with so i installed 4.3 leaked from here. doesn't matter which one you select. http://forum.xda-developers.com/showthread.php?t=2498233. place it on your sd card and head into recovery mode, wipe data/factory reset and cache. head to install zip from sd card and select the 4.3 zip you downloaded. reboot system and it should work. the at&t boot screen takes a while so be patient
Click to expand...
Click to collapse
First of all thank you for trying to help me, I hope you are having a good Thanks Giving.
I used the thread you linked to, and downloaded the version with out knox. I followed the instructions
transferred ROM and flashed kernel file to SD card
used odin to flash TWRP,
used twrp to flash rom and kernel file.
and it takes the file thankfully, there's only one issue. My phone can't make or receive calls/texts. Is yours able to?
I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Next Update
the bootloader I flashed apparently flashed to the external sd card? I flashed another one and it is booting from the internal sd. I had to flash a different modem the one in the bootloader/modem file I flashed from the link above didnt take? I got most everything sorted out, but im getting tired, it has been an all night adventure. its 08:23 est now
sorry for the delay in updating this I had to get some rest.
theramsey3 said:
I messed up and was playing with things That I had no business playing with and decided that I should do a restore of a backup (TWRP) I made as soon as I rooted the 4.3 OTA. well it has soft bricked my phone. it was a TWRP 4.3 Nandroid and has me messed up a little.
so far I tried My nandroid (no dice now a soft brick) cleared cache and dalvik, It was booting as far as the white at&t spinning thing,
Factory reset same on booting,
Tried a format of the internal sd this is where it gets sketchy it now goes as far as the second samsung screen(the one that says Samsung GALAXY S III)
4.3 OTA .zip (no dice TWRP wont flash it) same on the booting 2nd samsung boot screen
Tried the files in the link above and got a Hard brick
Used the debricking .IMG file and got TWRP and download mode back
Any suggestions?
Looks like I might need a JTAG/RIFF BOX for this one. If nothing else I spent many Hours of darkness discovering the darkness of android 4.3
If I get recovered from this and with a different rom like 4.1.2 I will be happy. the 4.3 OTA was very stable but I did miss wifi tether and the whole hardbrick thing was kind of a bummer. it would be real nice to have an ODIN file to fix this (AHEM samsung) or atleast perhaps stopped the progression of it to a hard brick.
New update
I got my phone booting up again however there is a catch. That unbrick.img file on my 16GB sd card is still required to boot the phone and I have no cell service what so ever. Tried to check apn settings because at home I sometimes get poor service and I run net10 so I was going to fix my apn and it says insert sim??? the sim is properly inserted???
Click to expand...
Click to collapse
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.
spongdangly said:
Go into Settings, About Phone, Status and check to see if your IMEI and Serial Number are present. If you only lost your IMEI there's a guide on how to inject it back (I'm not sure where the guide is). However if you've lost your serial number and don't have a Nandroid that can restore it I don't know what to do.
Click to expand...
Click to collapse
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I will give that a shot, but what's an APN, sorry. And how do I create one, and is it needed for me to do so?
gvazquez82 said:
i have my serial number showing but no IMEI number. So is that all that's needed for me to be able to call and text again?
Click to expand...
Click to collapse
It should be, I'm working right now so I don't have time to fine the guide on how to inject your IMEI. If I remember correctly it involves using QPST. If you have an old (or any) working Nandroid backup that should fix the problem.
FYI, make sure you don't use the guide for the international S3 as it has different hardware and folder structure/contents.
As for the APN, it should automatically fill itself in since it reads it off the SIM Card (I might be wrong).
theramsey3 said:
I updated my post above and showed my soultion. I simply had to flash a new modem and almost everything was kosher. I also had to flasah a different kernel but that was for preference not because things werent working.
http://forum.xda-developers.com/showpost.php?p=47817339&postcount=23 Modem download
I used that modem, flash it and see if your problems go away. I use Net10 so after I flashed the Modem I had to create an APN aswell, but that is nothing new for me.
Click to expand...
Click to collapse
I tried it and it work!!!!!!!!!!!!!!!!!
67 texts just came in. Sir, I thank you oh so kindly. You have made this gloomy rainy day oh so joyous.
No problem. Glad I could help you.
The real credit should go to -Mr.X-, loserskater and anyone else(no disrespect there were alot of files) whose stuff I tried to flash lastnight thank you all in the dev community who contribute.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.
gvazquez82 said:
So I guess the next question, do I try again to install kit kat on my phone.
I've already made bucks of my existing working phone haha....but I'd still like to have kitkat in place. I believe the issue of my phone not reading MD5 confirmations would still be in place, does anyone know how to remedy that situation?
At the same time I'm more than happy to leave my phone as is.
Click to expand...
Click to collapse
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.
flexfulton said:
Pretty sure you can turn off MD5 checks in TWRP. Probably in CWM too. Sorry if this has been mentioned. Didn't have time to read the whole thread. Just skimmed through.
2nd, there is a major difference between an IMEI that reads 0 and an IMEI that shows unknown. If it shows an unknown simply reflash your ROM and modem and you will be good to go. Sometimes a reboot is all you need. If your IMEI is showing a 0 on the other hand its gone and will require that it be injected back in which is a messy situation that usually results in tour phone being stuck on EDGE.
3rd, as someone mentioned on the previous page, restoring a working nandroid will NOT reinject your IMEI if it shows up as 0. No amount of flashing anything will get it to come back. Not even stock. It needs to be reinjected manually.
Click to expand...
Click to collapse
do you know of a good stable kit kat like ROM I could use for the s3? And any speculation as to why the ROMs werent taking for me?