Firstly, my apologies if this issue has been solved before here, but neither a search of the forum nor the automatically found "similar threads" based on the title have revealed such a problem as this.
Last night, I attempted (and eventually succeeded) at reverting my SGH-I747 to the stock 4.1.1 ROM, with the intention of subsequently installing the 4.3 and 4.4 OTAs. However, I was unable to do this because the phone behaved as though no SIM had been inserted, despite the fact that one had. At various points throughout today, I've performed factory resets, re-flashed the 4.1.1 ROM, and gone back to CM11 (under which my cellular connection had been fully functional up until last night), all with no results. My next thought was that the SIM card itself had somehow broken*, so I looked through AT&T's process for ordering a new SIM. However, I am unable to view the phones IMEI (which is required for such ordering) through software. Obviously, I could just pull out the battery and look at the IMEI there, but I worry that the lack of ability to view it in software is indicitave of some sort of problem with the phone.
My main concern is, is this a problem that I can easily solve? Or have I irrevocably screwed up my phone's SIM slot (or some other piece of related hardware) which I need to replace in order to recieve mobile communication?
Any help much appreciated.
*Before anyone asks, I am unable to test the SIM in a different device, as neither I nor anyone I know has a device on AT&T with a micro-SIM slot whose phone I can borrow for that purpose.
dhmmjoph said:
Firstly, my apologies if this issue has been solved before here, but neither a search of the forum nor the automatically found "similar threads" based on the title have revealed such a problem as this.
Last night, I attempted (and eventually succeeded) at reverting my SGH-I747 to the stock 4.1.1 ROM, with the intention of subsequently installing the 4.3 and 4.4 OTAs. However, I was unable to do this because the phone behaved as though no SIM had been inserted, despite the fact that one had. At various points throughout today, I've performed factory resets, re-flashed the 4.1.1 ROM, and gone back to CM11 (under which my cellular connection had been fully functional up until last night), all with no results. My next thought was that the SIM card itself had somehow broken*, so I looked through AT&T's process for ordering a new SIM. However, I am unable to view the phones IMEI (which is required for such ordering) through software. Obviously, I could just pull out the battery and look at the IMEI there, but I worry that the lack of ability to view it in software is indicitave of some sort of problem with the phone.
My main concern is, is this a problem that I can easily solve? Or have I irrevocably screwed up my phone's SIM slot (or some other piece of related hardware) which I need to replace in order to recieve mobile communication?
Any help much appreciated.
*Before anyone asks, I am unable to test the SIM in a different device, as neither I nor anyone I know has a device on AT&T with a micro-SIM slot whose phone I can borrow for that purpose.
Click to expand...
Click to collapse
You're quite lucky you didn't brick your phone downgrading like that.
You're gonna need nv-reader/write to get your IMEI back.. Look here.
BWolf56 said:
You're quite lucky you didn't brick your phone downgrading like that.
You're gonna need nv-reader/write to get your IMEI back.. Look here.
Click to expand...
Click to collapse
Firstly, thanks for your reply.
Secondly, the procedure to which you linked requires an nv file from another identical phone, to which I don't have access. Do you know of anywhere online where I may be able to get such a file?
dhmmjoph said:
Firstly, thanks for your reply.
Secondly, the procedure to which you linked requires an nv file from another identical phone, to which I don't have access. Do you know of anywhere online where I may be able to get such a file?
Click to expand...
Click to collapse
No, sorry. And I doubt you'll find one.
dhmmjoph said:
Firstly, thanks for your reply.
Secondly, the procedure to which you linked requires an nv file from another identical phone, to which I don't have access. Do you know of anywhere online where I may be able to get such a file?
Click to expand...
Click to collapse
Before you try the NV re-write, I would suggest you first check to see your modem hasn't been corrupted. Go to settings and see what is showing under Baseband version. If it reads <Unknown>, then you may be able to fix it by flashing the 4.3 MJB modem. I don't know what procedure you used to downgrade from 4.3 to 4.1.1 without hard-bricking your phone. It is indeed possible to downgrade the ROM only without downgrading the bootloader. However, the 4.3 bootloader and modem are in a tight and unbreakable marriage so if you downgrade the ROM and modem, you would end up losing your modem and consequently all cellular functioning even if you didn't up in a hard brick.
If your baseband version is indeed showing as unknown, then you can go to the link below to download the modem and flash via custom recovery ....
http://www.androidfilehost.com/?fid=23212708291680823
Larry2999 said:
Before you try the NV re-write, I would suggest you first check to see your modem hasn't been corrupted. Go to settings and see what is showing under Baseband version. If it reads <Unknown>, then you may be able to fix it by flashing the 4.3 MJB modem. I don't know what procedure you used to downgrade from 4.3 to 4.1.1 without hard-bricking your phone. It is indeed possible to downgrade the ROM only without downgrading the bootloader. However, the 4.3 bootloader and modem are in a tight and unbreakable marriage so if you downgrade the ROM and modem, you would end up losing your modem and consequently all cellular functioning even if you didn't up in a hard brick.
If your baseband version is indeed showing as unknown, then you can go to the link below to download the modem and flash via custom recovery ....
Click to expand...
Click to collapse
The baseband version is shown as "unknown"
I downloaded the file and moved it to the sd card in my phone, but the file doesn't appear in TWRP's "Select Zip to install" dialog. Does the file extension need to be changed? or do I need to flash some other recovery?
Thanks for your help!
dhmmjoph said:
The baseband version is shown as "unknown"
I downloaded the file and moved it to the sd card in my phone, but the file doesn't appear in TWRP's "Select Zip to install" dialog. Does the file extension need to be changed? or do I need to flash some other recovery?
Thanks for your help!
Click to expand...
Click to collapse
You said you moved it to your sd card? You might have to change TWRP's mounting to it.
BWolf56 said:
You said you moved it to your sd card? You might have to change TWRP's mounting to it.
Click to expand...
Click to collapse
I should clarify. I downloaded the file using my laptop, then connected the phone to the laptop, and moved the file to the root of the external SD. Using a file explorer app on the phone, I can see the file in that location, as well as several flashable ZIPs which I've put there in the past. However, when using TWRP to select a file to flash, I can navigate to the root of the external SD and see (and flash, if I wanted to) the other files, but not the .bin, presumably (though it's possible - or likely - that I'm wrong here) because TWRP expects all flashable files to be .ZIPs, and so doesn't display files that don't end in .zip. So, the question is, in order to flash this file, do I need to change the extension to .zip? or flash a different custom recovery? or use some other method for flashing altogether?
dhmmjoph said:
I should clarify. I downloaded the file using my laptop, then connected the phone to the laptop, and moved the file to the root of the external SD. Using a file explorer app on the phone, I can see the file in that location, as well as several flashable ZIPs which I've put there in the past. However, when using TWRP to select a file to flash, I can navigate to the root of the external SD and see (and flash, if I wanted to) the other files, but not the .bin, presumably (though it's possible - or likely - that I'm wrong here) because TWRP expects all flashable files to be .ZIPs, and so doesn't display files that don't end in .zip. So, the question is, in order to flash this file, do I need to change the extension to .zip? or flash a different custom recovery? or use some other method for flashing altogether?
Click to expand...
Click to collapse
I'm not so sure what file you downloaded but it should be a zip. In order to flash, you need a zip with META-INF folder in it (to put it simply).
Here's what you need: http://forum.xda-developers.com/showthread.php?t=1831898 (The MJB one).
dhmmjoph said:
The baseband version is shown as "unknown"
I downloaded the file and moved it to the sd card in my phone, but the file doesn't appear in TWRP's "Select Zip to install" dialog. Does the file extension need to be changed? or do I need to flash some other recovery?
Thanks for your help!
Click to expand...
Click to collapse
The file should be a zip. Just checked the link I sent you and I'm just seeing it's a*.bin file. You could try the one from the link forwarded by BWolf although this appears to be for CWM.
After this, you may also want to see if you won't be better off going to full stock 4.3. I'm not sure the hybrid firmware (4.1.1 ROM with 4.3 Bootloader/Modem) offers any real benefits.
Larry2999 said:
The file should be a zip. Just checked the link I sent you and I'm just seeing it's a*.bin file. You could try the one from the link forwarded by BWolf although this appears to be for CWM.
After this, you may also want to see if you won't be better off going to full stock 4.3. I'm not sure the hybrid firmware (4.1.1 ROM with 4.3 Bootloader/Modem) offers any real benefits.
Click to expand...
Click to collapse
Here's a TWRP flashable zip for the modem if the CWM doesn't work.
Related
I just bought this metro s3 and wanted to root it, well supersu was giving error everytime I tapped it so I decided to try an unroot with many of the methods on here and along the way ended up where my phone will not get past the galaxy siii sgh-t999n boot screen.
I used odin to do this, my phone is not being recognized under auto play but pc makes the connection sound when I plug usb in to my pc.
anyways I'm stuck at that screen and can only enter odin recovery on my phone and I have tried factory reset and still end up at the same boot screen and left it like that all night an woke up to the same screen.
I'm hoping this is not not a $300. brick.
I did download the files from a thread that described the files below were for the "T999l & T999n" and IF there was any difference int he files then the OP would point that out he said and I tripple checked to make sure in the section of the listed files to download did not mention the T999n was not for those specific files but there was nothing mentioned..
Please link the said thread.
You have not specified the firmware and android version you had before all this happened. Please specify that. Next Course of action depends on as much information you could provide about previous setup, Bootloader, Rom, Kernel & Baseband.
I think you only have a Non-Bootable Rom. I'd call that as a soft-Brick and not Hard-Brick. So there's no chance of you getting a $300 Paperweight. :laugh:
Having said that, given that all you want is Root, then
1. Flash Root66 version of your Firmware.
Perseus71 said:
Please link the said thread.
You have not specified the firmware and android version you had before all this happened. Please specify that. Next Course of action depends on as much information you could provide about previous setup, Bootloader, Rom, Kernel & Baseband.
I think you only have a Non-Bootable Rom. I'd call that as a soft-Brick and not Hard-Brick. So there's no chance of you getting a $300 Paperweight. :laugh:
Having said that, given that all you want is Root, then
1. Flash Root66 version of your Firmware.
Click to expand...
Click to collapse
Well I have solved my boot issues my installing CWM (which before would not stick after boot) and flashing 3 files from Docholiday on a thread but now the phone boots up as a T999L 4g LTE and has changed the model number under about phone. I have to unlock the phone as I only have a tmobile sim for this said Metropcs T999N device so I will see what happens after I try to unlock it.
thanks you for your prompt response!!
If Settings > About > Model is the only problem you have, then use Build.prop Editor from Playstore and change the value for RO.BUILD.DISPLAY.ID. Set it to what your device is.
Im not bothered by it myself as long as it wont effect my device?? also effect any future updates or when a program tries to sync with my device or anything other??
I don't believe there would be issues of this nature.
I was trying to install the Quantum Rom on my ATT Samsung Galaxy S3.
It failed a few times until someone posted that I need to update my bootloader to I747UCUEMJB. I was able to install the ROM after the update but now my phone won't recognize the SIM card that's worked flawlessly till I performed the bootloader update.
Is my phone done for good or is there something I can do here? Please help!!
Did you flash a compatible or updated modem?
audit13 said:
Did you flash a compatible or updated modem?
Click to expand...
Click to collapse
Sorry not really sure what that means. Also, just went in to my settings and under Baseband version I am seeing Unknown.
I checked the size of the bootloader I downloaded and it's only at 1.1 mbs and I just found the same bootloader online but at 623 mbs. I am assuming the bootloader I installed might be corrupt/fake?
I am downloading the larger file now and am going to try and install that too see if that helps?
There is no way the bootloader would be 623 MB.
Try flashing a modem from here: http://forum.xda-developers.com/showthread.php?t=1831898
audit13 said:
There is no way the bootloader would be 623 MB.
Try flashing a modem from here: http://forum.xda-developers.com/showthread.php?t=1831898
Click to expand...
Click to collapse
Yeah figured as much, especially after looking at the contents of the file, I decided not to use it.
Thanks for the link. Just downloaded modem_CWM_I747UCUEMJB.zip and I have my network signal back up now. I am hoping this means I am good. Will let you know soon. Thanks!!!
theproman23 said:
Sorry not really sure what that means. Also, just went in to my settings and under Baseband version I am seeing Unknown.
I checked the size of the bootloader I downloaded and it's only at 1.1 mbs and I just found the same bootloader online but at 623 mbs. I am assuming the bootloader I installed might be corrupt/fake?
I am downloading the larger file now and am going to try and install that too see if that helps?
Click to expand...
Click to collapse
Your baseband/modem is indeed corrupt. Before downloading or flashing ROMs please research thoroughly to be sure you know what you are doing and understand the difference between all the different files. The file you saw at 623mb is most likely the system or ROM file itself. The bootloader file itself is a much smaller file - consistent with a 1MB+ download. If you succeed with the file you are trying to download, you most probably would be updating your ROM although I'd be very doubtful if it would work. I'm not too certain but the 623MB file looks like the 4.3 update zip which usually works only when you are doing a manual update from an earlier ROM especially the immediate predecessor 4.1.2.
To correct your modem, I would suggest you try downloading and flashing the 4.3 modem file.
You may also need to install custom recovery (e.g. TWRP or CWM) for an easier installation. I presume warranty is no longer an issue with your phone in view of the firmware history.
Edit;
Just saw the last post from Audit after sending mine. Glad to know all is OK now.
Larry2999 said:
Your baseband/modem is indeed corrupt. Before downloading or flashing ROMs please research thoroughly to be sure you know what you are doing and understand the difference between all the different files. The file you saw at 623mb is most likely the system or ROM file itself. The bootloader file itself is a much smaller file - consistent with a 1MB+ download. If you succeed with the file you are trying to download, you most probably would be updating your ROM although I'd be very doubtful if it would work. I'm not too certain but the 623MB file looks like the 4.3 update zip which usually works only when you are doing a manual update from an earlier ROM especially the immediate predecessor 4.1.2.
To correct your modem, I would suggest you try downloading and flashing the 4.3 modem file.
You may also need to install custom recovery (e.g. TWRP or CWM) for an easier installation. I presume warranty is no longer an issue with your phone in view of the firmware history.
Edit;
Just saw the last post from Audit after sending mine. Glad to know all is OK now.
Click to expand...
Click to collapse
I completely understand what you're saying. Truth is I don't enough about all this to do what I did. Lesson learned for sure!
So. I was able to install the Modern bootloader and have my LTE signal back up and confirmed things are working given someone already called me and the call came through fine.
Now, the last thing I need to figure out is how to get WIFI to work. It's connecting to my router and has gone through authentication and has saved my network on the list of WIFI spots but I can't seem to connect and start downloading apps without eating my data.
Never mind, finally got wifi to work. Thanks again!!
Are you using any sort of encryption on your wifi network (i.e. WPA, WPA2, etc.)? Can it connect if you disable encryption?
Hey all, Was wondering if anybody had some time to help me troubleshoot why I cannot for the life of me get this method to work and maybe explain to me a few things that are confusing to me...
Basically my phone is hard bricked:
Samsung Galaxy S3 SGH-i747 (AT&T)
- Began with Stock 4.1.2 (almost %100 positive)
- Attempted flash to 4.4.4 Task650's AOKP ROM (Flashed ok but stuck at boot animation) via CWM
- Attempted reverting back to stock with the file below via Odin but I must have missed a step...
I747UCUEMJB_2024954_REV04_user_low_ship.tar.md5
Now I am hard bricked and don't know where to go from here. I've tried several solutions:
- Homemade Jig (didn't work)
- 3 button combo / download mode (doesn't work)
- Odin does not read phone
- Connected to a pc (red power light appears but nothing else)
- SD card method - Using Win32DiskImager to write images to a 16gb class 10 micro sd
- Debrick images used: 4.1.2, 4.1.1, (should i try 4.0.4, 4.3, or even 4.4?)
- How do I tell if the image is writing correctly and partitioning the drive right?
- When the sd card is seen in the computer I see a folder on it named "image" with several files inside it but I don't know how to see partitions
I have screenshots too if you'd like to see them. Let me know if you have any suggestions or have seen anyone with this same issue able to fix it. I'd appreciate it. Thanks.
- Chris
not very knowledgeable about this stuff , but here is a thread (hardbricked 4.1.1) with link to debrick images 4.3/4.4.
http://forum.xda-developers.com/showthread.php?t=2880002
thanks to @DocHoliday77
hopefully someone will come along with some real help.
good luck.
err on the side of kindness
If that firmware was the full firmware, and it appeared to flash, you'll probably need to use the 4.3 debrick.img. also try different sd cards. Many just don't work, where others will.
Look at Tmobiles debrick thread stickied in the development section there. It tells you how to use a Linux liveCD to partition and check the card. The method will work, just use the files from here if you try it.
Chances are, if it doesn't work with the 4.3 image, you'll need a different sd card though.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
If that firmware was the full firmware, and it appeared to flash, you'll probably need to use the 4.3 debrick.img. also try different sd cards. Many just don't work, where others will.
Look at Tmobiles debrick thread stickied in the development section there. It tells you how to use a Linux liveCD to partition and check the card. The method will work, just use the files from here if you try it.
Chances are, if it doesn't work with the 4.3 image, you'll need a different sd card though.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Ok thanks. I'm going to attempt this again tonight using an SD card adapter instead of using another mobile device as the adapter to see if that makes a difference. If that doesn't do the trick I will try the LinuxLiveCD method. I'm using a Lexar 16gb Class 10 micro sd card so I don't think it that is the issue but I guess it wouldn't hurt to try a different brand.
Just curious, has anybody here successfully debricked their phone using another mobile device as the sd card adapter?
Not sure about using the mobile device, but you'd be surprised about the sd cards! I've seen Samsung 16GB Class 10 fail for some people, but work for others. It's really odd as there is no rhyme or reason to it. More of a crap shoot than anything from what I can tell.
I've seen generic 32GB class 4 cards work for people who couldn't get a name brand class 10 one to work at all.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
Not sure about using the mobile device, but you'd be surprised about the sd cards! I've seen Samsung 16GB Class 10 fail for some people, but work for others. It's really odd as there is no rhyme or reason to it. More of a crap shoot than anything from what I can tell.
I've seen generic 32GB class 4 cards work for people who couldn't get a name brand class 10 one to work at all.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Good to know, but just to clarify when you say it "fails"... what exactly fails - writing the image file, partitioning the card, or does it write everything to the card ok and then just not boot up? I'm just asking so I know what to look for if it ever happens.
Thanks for the responses as I'm still new to this process and this phone and every little thing helps!
It usually appears to create the debrick sd card just fine. It just doesn't work when you try to boot.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
It usually appears to create the debrick sd card just fine. It just doesn't work when you try to boot.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
So, it appears that the issue was using the mobile device as the sd card reader. After writing the debrick file to the same sd card with an actual sd card reader, I am able to boot into the stock recovery. From here, I should just be able to flash a stock ROM to it correct or no?
Ok, which debrick.img did you end up using? If you used 4.3, you must flash the MJB firmware. If it was an older image, you will have a choice.
Either way, if you're ready to update to 4.3, and the recovery you are able to boot into is Twrp or cwm, you can flash this:
https://www.androidfilehost.com/?fid=23269279319197285
It is the full mjb base firmware. does not include recovery or system. After flashing this, you should be able to boot at least recovery and download mode without the sd card. If your rom is intact, you'll be able to boot it as well. If not, choose one and flash it.
If you are not ready to update to 4.3, we will have to find another, older version of what I linked above. Or I can make one if required.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
Ok, which debrick.img did you end up using? If you used 4.3, you must flash the MJB firmware. If it was an older image, you will have a choice.
Either way, if you're ready to update to 4.3, and the recovery you are able to boot into is Twrp or cwm, you can flash this:
https://www.androidfilehost.com/?fid=23269279319197285
It is the full mjb base firmware. does not include recovery or system. After flashing this, you should be able to boot at least recovery and download mode without the sd card. If your rom is intact, you'll be able to boot it as well. If not, choose one and flash it.
If you are not ready to update to 4.3, we will have to find another, older version of what I linked above. Or I can make one if required.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
Ok, after playing with the phone for awhile I have found out that I can boot into download mode now. After rebooting, I was able to boot into the stock 4.3 ROM but I noticed I lost root access. Now the problem is I cannot enter the recovery to even flash the file you mentioned above (I flashed CWM via Odin but I can't boot into it). The phone can be seen in Odin now as well. I've done a little bit of research on achieving Root access again but I came across a post that mentioned I could ruin my IMEI number by flashing a "CF-Autoroot" file, should I be worried about doing this now that I'm on 4.3 or am I ok since I didn't use the OTA 4.3 ??
Again, thank you so much for the advise! I'm so glad this phone isn't a brick anymore.
Ok. Since you can get download mode, that changes things.
Boot download mode, remove the sdcard and flash the MJB firmware in Odin. Download here:
http://forum.xda-developers.com/showthread.php?t=2722660
Then, use Towelroot to root the device. (I posted a good guide for this. It should be on page 1 in the Tmobile General section: http://forum.xda-developers.com/showthread.php?t=2793071)
Towelroot is by far the easiest root you'll ever use! Just make sure you read the first two posts before starting!
At this point you should be fully recovered and running stock rooted MJB.
Now before anything else, since you mentioned the imei, backup your NV Data. Very easy!
Install and open Terminal Emulator from the store and enter this:
Code:
su
reboot nvbackup
It'll reboot and create a hidden, permanent, on device backup of your NV data. If corruption is ever detected it'll auto restore during boot, so it essentially protects you from ever losing your imei!
After that, you can do as you wish! If you want to update to 4.4.2 though, I recommend doing that before you root. After flashing MJB, reboot and you should be able to get the official OTA. Then continue with the rest if the instructions above.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
DocHoliday77 said:
Ok. Since you can get download mode, that changes things.
Boot download mode, remove the sdcard and flash the MJB firmware in Odin. Download here:
http://forum.xda-developers.com/showthread.php?t=2722660
Then, use Towelroot to root the device. (I posted a good guide for this. It should be on page 1 in the Tmobile General section: http://forum.xda-developers.com/showthread.php?t=2793071)
Towelroot is by far the easiest root you'll ever use! Just make sure you read the first two posts before starting!
At this point you should be fully recovered and running stock rooted MJB.
Now before anything else, since you mentioned the imei, backup your NV Data. Very easy!
Install and open Terminal Emulator from the store and enter this:
Code:
su
reboot nvbackup
It'll reboot and create a hidden, permanent, on device backup of your NV data. If corruption is ever detected it'll auto restore during boot, so it essentially protects you from ever losing your imei!
After that, you can do as you wish! If you want to update to 4.4.2 though, I recommend doing that before you root. After flashing MJB, reboot and you should be able to get the official OTA. Then continue with the rest if the instructions above.
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I flashed the files from the link you posted in Odin and now I am golden! I attempted to upgrade OTA to 4.4.2 and it's saying that I'm up to date and that there are no updates available for my phone and to check back in 24 hrs. After seeing that, I checked the system status and it says "OFFICIAL" so I don't really understand why I can't upgrade OTA. I noticed that something I've done has tripped the warranty bit But whatever, I am perfectly fine with staying on 4.3 for now - I didn't see too much to really need to upgrade to 4.4.2 quite yet... although I might try to upgrade again tomorrow and see what happens. I don't really need root at the moment but if I attempt to flash to anything else in the future, I'll give towelroot a shot.
Again, thanks for your help - I owe ya one DocHoliday
CornfedChris said:
.... I attempted to upgrade OTA to 4.4.2 and it's saying that I'm up to date and that there are no updates available for my phone and to check back in 24 hrs.
... although I might try to upgrade again tomorrow and see what happens.
Click to expand...
Click to collapse
I've seen reports of this more than once where someone going back to stock initially receives the no updates available msg and then after 24 hrs or so it becomes available. So, your plan sounds good.
CornfedChris said:
I flashed the files from the link you posted in Odin and now I am golden! I attempted to upgrade OTA to 4.4.2 and it's saying that I'm up to date and that there are no updates available for my phone and to check back in 24 hrs. After seeing that, I checked the system status and it says "OFFICIAL" so I don't really understand why I can't upgrade OTA. I noticed that something I've done has tripped the warranty bit But whatever, I am perfectly fine with staying on 4.3 for now - I didn't see too much to really need to upgrade to 4.4.2 quite yet... although I might try to upgrade again tomorrow and see what happens. I don't really need root at the moment but if I attempt to flash to anything else in the future, I'll give towelroot a shot.
Again, thanks for your help - I owe ya one DocHoliday
Click to expand...
Click to collapse
Right on! Glad to hear you got it all fixed up! If that update does become available later, please let us know. I've been telling several people to wait a day, but I haven't heard if it actually came through for any of them yet.
If you do decide to root in the future, just don't forget about that backup!
Sent from my SAMSUNG-SGH-I747 using Tapatalk
So tonight while I was watching TV I looked down at my phone and noticed it decided to just go ahead and update itself to 4.4.2, haha. So apparently there's an auto-update defaulted in the settings somewhere. I haven't really noticed too many differences yet but I'm liking it so far. :good:
Hello all,
I have an HTC ONE M8 that is currently running a Kit Kat Venom rom. I want to update to something newer but my USB port doesn't work for data transfers etc, only can charge with it. I have only seen steps to update involving using PC, am I out of luck?
I also do not have my stock rom back anymore (laptop died and lost all information) , and the phone was originally bought in Kuwait so I am not sure how I go about getting the stock ROM back...
M8
jpeezy1977 said:
Hello all,
I have an HTC ONE M8 that is currently running a Kit Kat Venom rom. I want to update to something newer but my USB port doesn't work for data transfers etc, only can charge with it. I have only seen steps to update involving using PC, am I out of luck?
I also do not have my stock rom back anymore (laptop died and lost all information) , and the phone was originally bought in Kuwait so I am not sure how I go about getting the stock ROM back...
Click to expand...
Click to collapse
If you are already running venom then you are rooted so it should be fairly easy to do it from your phone. You need to know which firmware you will need, I'm guessing you probably have a European model.
I have a Verizon phone so the firmware is different but the process should be the same. I found my firmware and downloaded it directly to my phone, placed it in the root of the SD card (not in a folder), renamed it, rebooted to the bootloader, it recognized the renamed firmware and installed it. For my phone there were stock marshmallow sense ROM's that were prerooted and it was the same process, you download it to your phone, place it in the root of the SD card (not in a folder), rename it, reboot to bootloader and it should recognize it and install it.
Once you have successfully flashed it, then delete it or your phone will Try to install it every time you boot to the bootloader.
Is your USB Port physically damaged? If not then it could be dirty, have you tried blowing it out with compressed air?
And after you update your firmware you will probably need to update your recovery image (TWRP, etc).
I had read that many international models with GSM radios may be able to use the developer edition from the HTC website. There may be more info in the venom forum, at their website or at the HTC site. However, I would recommend you research it before giving it a try.
You need to find out what firmware you need and find the correct forum.
Good luck.
morr22066 said:
If you are already running venom then you are rooted so it should be fairly easy to do it from your phone. You need to know which firmware you will need, I'm guessing you probably have a European model.
I have a Verizon phone so the firmware is different but the process should be the same. I found my firmware and downloaded it directly to my phone, placed it in the root of the SD card (not in a folder), renamed it, rebooted to the bootloader, it recognized the renamed firmware and installed it. For my phone there were stock marshmallow sense ROM's that were prerooted and it was the same process, you download it to your phone, place it in the root of the SD card (not in a folder), rename it, reboot to bootloader and it should recognize it and install it.
Once you have successfully flashed it, then delete it or your phone will Try to install it every time you boot to the bootloader.
Is your USB Port physically damaged? If not then it could be dirty, have you tried blowing it out with compressed air?
And after you update your firmware you will probably need to update your recovery image (TWRP, etc).
I had read that many international models with GSM radios may be able to use the developer edition from the HTC website. There may be more info in the venom forum, at their website or at the HTC site. However, I would recommend you research it before giving it a try.
You need to find out what firmware you need and find the correct forum.
Good luck.
Click to expand...
Click to collapse
Thanks! I will do some research to see which firmware I need. When you say you renamed it after putting it on your SD card, what did you rename it to?
I tried cleaning out my USB port, with canned air , but no luck. If I plug in an OTG cable in it will detect that it is an OTG cable, but it wont read anything from there. I believe I will have to replace the charging port, fortunately for the M8 it is separate from the main board. Also, another indication I believe it is a faulty USB charge port is that it seems to take forever to charge..
jpeezy1977 said:
Thanks! I will do some research to see which firmware I need. When you say you renamed it after putting it on your SD card, what did you rename it to?
I tried cleaning out my USB port, with canned air , but no luck. If I plug in an OTG cable in it will detect that it is an OTG cable, but it wont read anything from there. I believe I will have to replace the charging port, fortunately for the M8 it is separate from the main board. Also, another indication I believe it is a faulty USB charge port is that it seems to take forever to charge..
Click to expand...
Click to collapse
For my Verizon phone the image had to be named OP6BIMG.ZIP. It may be the standard name but once you find the correct firmware thread it will most likely tell you what to name it. And remember, the system will most likely add the "zip" part to the end of the name so double check it after you rename it to see that it is not named ".zip.zip" before you go into the bootloader.
morr22066 said:
For my Verizon phone the image had to be named OP6BIMG.ZIP. It may be the standard name but once you find the correct firmware thread it will most likely tell you what to name it. And remember, the system will most likely add the "zip" part to the end of the name so double check it after you rename it to see that it is not named ".zip.zip" before you go into the bootloader.
Click to expand...
Click to collapse
Ok, thanks! I appreciate your help.
M8
jpeezy1977 said:
Ok, thanks! I appreciate your help.
Click to expand...
Click to collapse
No problem. Good luck.
Ok so in the last thread I started I learned how flashing ROMS works, with the matching firmware, CID's, and other stuff, but now I have another issue... The ROM that I was able to flash was the TeamVenom Viper One ROM for Android L (Lolipop)....The ROM version I used was Viper 3.5.0, but now I would like to upgrade to Viper 6.1.0, but it requires Android M (HTC Firmware 3.x).... I do not have a stock ROM to go back to update, and the HTCDev RUU.exe to update gives error code 132 (similar to error code 12, Thanks for the ReadMe page btw @Flippy498), which is a signature error (which is odd because it is straight from HTCDev) and I cannot find a zip file of 3.xx.502.xx to flash that isn't A) corrupted upon download, or B) has a working link... I don't think I can update Viper because it says "Flashing the new Android M firmware is a must, else your phone won’t boot!!" (trust me it doesn't boot, I've tried)... But I read somewhere that having a Team Venom account will allow you to receive OTA updates, yet when I check for OTA updates through the Venom app in the app drawer it doesn't find any available updates, which I know is incorrect because as I said I'm still on Android L (5.1)... What would I need to do from here, how would I A)fix HTC installer, or B) does anybody have a WORKING flashable stock android zip to update from Lollipop to Marshmallow...
Thanks in advanced!
Forum N00b,
qwsderter
qwsderter said:
but now I would like to upgrade to Viper 6.1.0, but it requires Android M (HTC Firmware 3.x)
Click to expand...
Click to collapse
It's actually recommended to use firmware 4.x for Viper 6.1.0 (although the rom boots on 3.x, as well).
qwsderter said:
I do not have a stock ROM to go back to update, and the HTCDev RUU.exe to update gives error code 132 (similar to error code 12, Thanks for the ReadMe page btw @Flippy498), which is a signature error (which is odd because it is straight from HTCDev)
Click to expand...
Click to collapse
It's not odd at all. Re-read the explanation of the error or the RUU section. Both explain why the flash fails.
qwsderter said:
I cannot find a zip file of 3.xx.502.xx to flash that isn't A) corrupted upon download, or B) has a working link
Click to expand...
Click to collapse
I checked the link in the ReadMe thread. It'sworking fine. If the file gets corrupted during the download then it's due to your setup (e.g. an interruption of your internet connection during the download, etc.).
qwsderter said:
But I read somewhere that having a Team Venom account will allow you to receive OTA updates, yet when I check for OTA updates through the Venom app in the app drawer it doesn't find any available updates, which I know is incorrect because as I said I'm still on Android L (5.1)
Click to expand...
Click to collapse
There is no OTA for updating Venom 3.5.0. Custom roms can't update your firmware. Therefore, you need to update it on your own and to flash a full rom whenever the rom's base get's changed. The OTAs only update the rom (e.g. from 3.0.0 to 3.1.0). That's why there isn't an OTA for 6.0.0 -> 6.1.0, either. 6.1.0 is based on a different firmware than 6.0.0. You might want to read the article that is labeled as "The difference between rom and firmware" in the further reading section of the ReadMe thread.
Flippy498 said:
It's actually recommended to use firmware 4.x for Viper 6.1.0 (although the rom boots on 3.x, as well).
It's not odd at all. Re-read the explanation of the error or the RUU section. Both explain why the flash fails.
I checked the link in the ReadMe thread. It'sworking fine. If the file gets corrupted during the download then it's due to your setup (e.g. an interruption of your internet connection during the download, etc.).
There is no OTA for updating Venom 3.5.0. Custom roms can't update your firmware. Therefore, you need to update it on your own and to flash a full rom whenever the rom's base get's changed. The OTAs only update the rom (e.g. from 3.0.0 to 3.1.0). That's why there isn't an OTA for 6.0.0 -> 6.1.0, either. 6.1.0 is based on a different firmware than 6.0.0. You might want to read the article that is labeled as "The difference between rom and firmware" in the further reading section of the ReadMe thread.
Click to expand...
Click to collapse
Hey thanks Flippy you are the clutch, but I can verify that the files ARE corrupt.... I have downloaded it twice, and I have google fiber so I can guarantee that the connection was consistent. Winrar said the file was corrupted, along with when trying to flash TWRP would flash.... Any other ideas, you are the master at this Flippy, there must be another way...
qwsderter said:
Hey thanks Flippy you are the clutch, but I can verify that the files ARE corrupt.... I have downloaded it twice, and I have google fiber so I can guarantee that the connection was consistent. Winrar said the file was corrupted, along with when trying to flash TWRP would flash....
Click to expand...
Click to collapse
You should re-read the ReadMe thread. They're not corrupt. I thought that with "corrupt" you meant the MD5 checksum wouldn't match after the download. That WinRar error message is expected behaviour.
Flippy498 said:
You should re-read the ReadMe thread. They're not corrupt. I thought that with "corrupt" you meant the MD5 checksum wouldn't match after the download. That WinRar error message is expected behaviour.
Click to expand...
Click to collapse
Ah gotcha... So I used the decryption tool to make a SD flashable zip, and what do you know, TWRP crashes when I swipe to flash... How come I can flash other ROMs but I can't flash stock roms without it crashing (Device turns off)
Please don't tinker around without knowing what you're doing and (as said before) read what got written in the FAQ and the RUU section. Extracting the *.zip wasn't needed at all since there already is a download link for an extracted *.zip. In addition, there are step by step instructions how RUUs can/need to get flashed.
Sent from my HTC One M9 using XDA Labs
Flippy498 said:
Please don't tinker around without knowing what you're doing and (as said before) read what got written in the FAQ and the RUU section. Extracting the *.zip wasn't needed at all since there already is a download link for an extracted *.zip. In addition, there are step by step instructions how RUUs can/need to get flashed.
Sent from my HTC One M9 using XDA Labs
Click to expand...
Click to collapse
Ok thank you "again" I have officially read your ENTIRE guide 3 times now, Not trying to offend you or make shame of your work, but the problem is I "THINK" that I am following your work.... I download the RUU for my phone (in this case SKU: 502 - CID: CWS__001 VERSION 2.11.502 (I have also tried 3.38.502.41 to no avail)) and everything is going as planned, I have verified that BOTH the CID and MID are matching that of my phone.... But when I plug SD card into Phone in download mode I get no such asked if I want to flash the file (as your guide says to do).... Ok so if I try to flash through TWRP it crashes, and if I try to Fastboot Flash the file I get what is seen in the picture attachment, and then nothing happens, except the bootloader page says "Under flash" and adds another line saying Under flash everytime I press the power button... My phone is S-OFF, is there another possible way to do this.... I swear to go I have read your ReadMe thread and I'm not just being arrogant, but my phone WILL not flash to ANY STOCK ROM downloaded anywhere from the Internet... @Flippy498 I promise there has to be something I missed in your ReadMe (I HAVE NO IDEA HOW I COULD) or i'm getting damaged ROMs... I'm sorry that you have to put up with me and help me thus far, and let me say the XDA community deserves people like you, and less people like me who think they know what they are doing until something breaks...
EDIT: It seems the phone is missing a located at /dev/fastboot_download_j in the CMD screenshot. Should that be said issue how would I go about fixing that...
Your SD card isn't bigger than 32gb and formatted to fat32? The file is placed in the root directory of the card and renamed to 0PJAIMG.zip (not 0PJAIMG.zip.zip and not OPJAIMG.zip)? The SD card method as it is written there already got used by a lot of users without any issues. The problem in this case must be on your end. What kind of error is stated at the bottom of your download mode? The M9 always tells you what's wrong. Either the SD card isn't mounted correctly (in other words you're using an unsupported format) or the 0PJAIMG.zip file is missing (in other words either non-existent on your sd card, placed in the wrong direction or renamed wrongly).
And of course TWRP crashes. Not every *.zip file can get flashed via TWRP just because it's a *.zip. (Just like not every *.zip can/should get unzipped just because it's a *.zip.) The only methods that can be used for flashing a RUU are mentioned in the ReadMe thread. And that's what I meant with "don't tinker around". You're doing things with files they're not meant to be done with.
The fastboot flash on the other hand can't work with the commands shown in your screenshot. That's a mistake in my guide. :silly: And it's even explained in the text above the instructions. I'm wondering why nobody (including me) noticed that before. I can only assume that it's because fastboot flashing doesn't get used that often for RUUS. The commands need to start with "htc_fastboot" not "fastboot". The normal fastboot isn't able to flash RUUs. I've fixed that part. Thanks for making me aware of that.
And in regard to the "damaged roms": The ReadMe thread explains how to check whether your downloads are fine (key word: md5).
Flippy498 said:
Your SD card isn't bigger than 32gb and formatted to fat32? The file is placed in the root directory of the card and renamed to 0PJAIMG.zip (not 0PJAIMG.zip.zip and not OPJAIMG.zip)? The SD card method as it is written there already got used by a lot of users without any issues. The problem in this case must be on your end. What kind of error is stated at the bottom of your download mode? The M9 always tells you what's wrong. Either the SD card isn't mounted correctly (in other words you're using an unsupported format) or the 0PJAIMG.zip file is missing (in other words either non-existent on your sd card, placed in the wrong direction or renamed wrongly).
And of course TWRP crashes. Not every *.zip file can get flashed via TWRP just because it's a *.zip. (Just like not every *.zip can/should get unzipped just because it's a *.zip.) The only methods that can be used for flashing a RUU are mentioned in the ReadMe thread. And that's what I meant with "don't tinker around". You're doing things with files they're not meant to be done with.
The fastboot flash on the other hand can't work with the commands shown in your screenshot. That's a mistake in my guide. :silly: And it's even explained in the text above the instructions. I'm wondering why nobody (including me) noticed that before. I can only assume that it's because fastboot flashing doesn't get used that often for RUUS. The commands need to start with "htc_fastboot" not "fastboot". The normal fastboot isn't able to flash RUUs. I've fixed that part. Thanks for making me aware of that.
And in regard to the "damaged roms": The ReadMe thread explains how to check whether your downloads are fine (key word: md5).
Click to expand...
Click to collapse
Once again Thank you for helping me out, the htc_flashboot command was what I needed, I was able to flash the stock rom through the command.... May I just say, you sir know what you are doing, and I wish you continue to help other people on this forms just like you've helped me.... I Installed the 2.x rom, but the OTA update didn't work for some reason... so I'm gonna flash the 4.x and then install ViperOne again...
And when I was saying "Damaged Roms" I was not implying that it was corrupted over the internet, but rather that they were never working in the first place...
Oh, that microSD card I had is in the trash now, since the only device that recognizes it is my pc, I assume it is on the brink of death...
Thanks again,
qwsderter
qwsderter said:
I Installed the 2.x rom, but the OTA update didn't work for some reason
Click to expand...
Click to collapse
That's probably like that due to AT&T denying OTAs to phones that currently aren't using an AT&T sim card. You wouldn't be the first user that isn't able to receive AT&T updates for the M9. Don't ask me why they're allowed to do so. Something like that wouldn't be possible in the EU.
qwsderter said:
so I'm gonna flash the 4.x and then install ViperOne again
Click to expand...
Click to collapse
Don't forget that you need to flash one of Sneakyghost's firmware packs if you want to be able to flash 4.x RUUs. (Keyword: encryption keys)
qwsderter said:
And when I was saying "Damaged Roms" I was not implying that it was corrupted over the internet, but rather that they were never working in the first place
Click to expand...
Click to collapse
That's actually the difference between my ReadMe thread and most of the RUU collections on other websites. The files only get linked if they're known to be working whereas other sites link every RUU they can find. There are a lot more RUUs for the M9 out there than the ones I listed. However, these RUUs either aren't able to get flashed successfully or their roms aren't able to receive any OTAs - e.g. there's a second RUU for firmware 1.32.401.15 than the one that is linked in my thread and if you flash that other RUU you're stuck on its firmware version until you flash a different RUU.
qwsderter said:
Oh, that microSD card I had is in the trash now, since the only device that recognizes it is my pc, I assume it is on the brink of death
Click to expand...
Click to collapse
If it's really broken you should thank whichever god you believe in that your phone wasn't able to recognize the card. Since your phone is S-OFF all security checks on your phone are disabled. That means if a file gets corrputed on the SD card due to its partition being messed up your phone would still accept the broken RUU, nonetheless. This would most likely lead to unrecoverable damages. In other words, chances are high in such situations that you create a fancy but expensive paperweigth.
Flippy498 said:
That's probably like that due to AT&T denying OTAs to phones that currently aren't using an AT&T sim card. You wouldn't be the first user that isn't able to receive AT&T updates for the M9. Don't ask me why they're allowed to do so. Something like that wouldn't be possible in the EU.
Click to expand...
Click to collapse
Funny, I thought the same thing, until I realized it was ATT who I am paying every month to rip my girlfriend and I off. Well oh well, I know you are in Germany (From your profile) but if you ever come to the United States, I will say from my personal experience (my opinion, not facts) ATT has seemed to have the broadest coverage, but also is the (2nd) most constrictive (Verizon seems very constraining), to me ATT feels premium but they are also (in my opinion) the most likely to royally screw up... Oh well, no OTA time to flash!!!
Flippy498 said:
If it's really broken you should thank whichever god you believe in that your phone wasn't able to recognize the card. Since your phone is S-OFF all security checks on your phone are disabled. That means if a file gets corrputed on the SD card due to its partition being messed up your phone would still accept the broken RUU, nonetheless. This would most likely lead to unrecoverable damages. In other words, chances are high in such situations that you create a fancy but expensive paperweigth.
Click to expand...
Click to collapse
Trust me, when I tried the SD card in the phone I thought, "That is a little odd", then both of my ASUS MemoPads didn't detect it either EVEN THOUGH THEY WERE RUNNING, I just assumed that they didn't work because MemoPads are the most budget friendly tablets ever and something broke, so I go to my Nexus 7 and realize it doesn't have an SD card slot so I couldn't test, so I popped the card in our Camera... Low and behold it doesnt detect.... Now the true question, why did my desktop detect it, eh whatever not worth my time.... The gods were looking down on me, they broke my $10 microSD and not my more than 10$ phone.....
Once again thank you for the help Flippy, you have no idea how much it hurt using my iPhone 5 for 2 days, I felt so inferior