Related
Hey guys, im new to the scene, and while fiddling around with my Galaxy S3, i have managed to brick it! Here is what happened.
I rooted the phone using a tutorial from here:
http://galaxys3root.com/galaxy-s3-r...gh-t999sgh-i747sph-l710-fail-proofnoob-proof/
Everything worked fine and the phone successfully rooted. But than i came across roms ... and i found a tutorial that told me how to install CyanogenMod 9:
http://forum.xda-developers.com/showthread.php?t=1778165
I tried to follow the instructions, but i would get (Error 7), and i realized that this tutorial instructed me to install the ClockworkMod Recovery version 5.8.4.7. So i downloaded the file from ClockworkMod's website, and it was in a .img format. When i had rooted my phone and installed ClockworkMod i used a .tar version via Odin, and this time i had a .img. After going through many tutorials, i found someone that showed how to install the .img varient via Android Terminal Emulator. So i followed the instructions:
http://forum.xda-developers.com/showthread.php?t=1363132
After i was finished following the instructions i rebooted the phone. And boom, it would not turn on. I tried all variants of holding the external buttons etc. Than i plugged the phone into a Windows PC. and the phone shows up in device manager as "QHSUSB DLOAD". So after tirelessly researching, i finally found the drivers for this and installed them. And know the phone shows up in Odin as COM10 in yellow. So i tried to flash the stock Image. I fire up Odin, select PDA, than the stock image, and click start. This is all that happens in the "Message Log":
<ID:0/010> Added!!
<ID:0/010> Odin v.3 engine (ID:10)..
<ID:0/010> File analysis..
<ID:0/010> SetupConnection..
(I have attached a screenshot of the above)
Please guys, i just got the phone and now it is bricked, any help would be greatly appreciated. Thanks!!
First download the correct version of Odin and drivers for s3's here ;
http://forum.xda-developers.com/showthread.php?t=1722686
Then download and flash the full stock rom from here;
http://forum.xda-developers.com/showthread.php?t=1752729
Hopefully that will get your phone to boot.
Then once you have reapplied the rooted system image download "rom manager" from the market and flash the updated recovery from there to avoid the error you encountered when attempting to flash cm9.
Good luck!
Hi, Thanks for your reply. I tried using a "Jig" and it did not put the S3 into download mode. LIke i said previously. When the S3 is connected to my PC it shows up as "QHSUSB DLOAD". And no Samsung drivers would work with it. I had to research and find the drivers that finally worked and allowed Odin v1.85 to see the phone as "COM10", and i select the ROM under the PDA and click the "Start" button. But than it does not go past SetupConnection. I thought maybe the "Jig" was faulty and didnt work, but i tested it with another working Samsung Galaxy S2, and it worked exactly as it was supposed to. Should i still try your suggestion or is it pointless?
neubauej said:
First download the correct version of Odin and drivers for s3's here ;
http://forum.xda-developers.com/showthread.php?t=1722686
Then download and flash the full stock rom from here;
http://forum.xda-developers.com/showthread.php?t=1752729
Hopefully that will get your phone to boot.
Then once you have reapplied the rooted system image download "rom manager" from the market and flash the updated recovery from there to avoid the error you encountered when attempting to flash cm9.
Good luck!
Click to expand...
Click to collapse
Ouch.
It sounds like your bootloaders might be borked, so kinda pointless.
I would get ahold of Josh at www.mobiletechvideos.com as it sounds like jtag might be required.
Hey, Thanks for the info. But the image i flashed via the Android mobile terminal app on the phone, i was flashing a ClockworkMod v5.4.8.1, that was made for the AT&T i747 (I have the Bell i747M, which i am told is the same thing?) , is that the bootloader? I know someone here that is local that does the jTag repair. But im not sure if the problem i have is in relation to the bootloader. Please let me know. As the phone still does show up when connected to the PC.
neubauej said:
Ouch.
It sounds like your bootloaders might be borked, so kinda pointless.
Get ahold of Josh at as it sounds like jtag might be required.
Click to expand...
Click to collapse
I tried your solution. The phone when connected to the PC with does not show up in Odin 3.07 (Correct version for my phone, from your link), But if i turn on Odin 1.85, the phone shows up fine in that as COM10 in yellow. So does my phone need a jTag? Samsung Canada told me to send the phone in for service and they will reset it and send it back. At the moment the phone does not turn on or go into download mode, and when connected to the computer it shows up as HS-USB QDLoader. So my question is: If i send it to Samsung, will they discover that i have Rooted it and void my warranty and not fix the phone?
neubauej said:
First download the correct version of Odin and drivers for s3's here ;
http://forum.xda-developers.com/showthread.php?t=1722686
Then download and flash the full stock rom from here;
http://forum.xda-developers.com/showthread.php?t=1752729
Hopefully that will get your phone to boot.
Then once you have reapplied the rooted system image download "rom manager" from the market and flash the updated recovery from there to avoid the error you encountered when attempting to flash cm9.
Good luck!
Click to expand...
Click to collapse
If you send it to Samsung its unlikely they will notice or care that its rooted.
I have sent them 2 devices that I wanted them to reflash after I did stupid things and hardbricked, fully expecting to pay for it, and it was returned to me flashed and at no charge. This was after I told the customer service rep that I was flashing custom firmware and i screwed it up.
YMMV.
The worst case scenario there is they void your warranty and charge you a minimal fee to reflash it.
As for your bootloaders, you pushed a custom recovery that failed, corrupted, or was an incorrect application. The recovery lies in the bootloader..
If it doesn't power up, won't go into download mode, and Odin won't flash it I'd say its jtag or send it to sammy time.
I see, well i do not care if they charge me anything. Money is not an issue, Ok well i just got the email from Samsung with the shipping label. Thanks for your information.
neubauej said:
If you send it to Samsung its unlikely they will notice or care that its rooted.
I have sent them 2 devices that I wanted them to reflash after I did stupid things and hardbricked, fully expecting to pay for it, and it was returned to me flashed and at no charge. This was after I told the customer service rep that I was flashing custom firmware and i screwed it up.
YMMV.
The worst case scenario there is they void your warranty and charge you a minimal fee to reflash it.
Click to expand...
Click to collapse
Goodluck!
Fyi 5.4.8.7 is the clockwork version I'm running.
After doing some more research, i found that another person with a different Samsung phone. Followed the same instructions to flash ClockworkMod via Android Mobile Terminal using the same instructions i did and got the same problem. On his post somebody told him that the flash was made to the wrong partition or something like that. So ... Lesson for next time. READ EVERYTHING BEFORE TRYING IT!
neubauej said:
Goodluck!
Fyi 5.4.8.7 is the clockwork version I'm running.
Click to expand...
Click to collapse
Yeah just go to Samsung. Its too bad u never read that the newer versions of CWM recovery don't work on the 747m. The 747 and our m variants are close but still a bit different in a few ways although when coming here for rooms and stuff we have to use this at&t 747. Section. There is a great rooting post under the development stickies and it mentions the UNICERSAL VERSION OF CWM RECOVERY FOR 747m phones and that is the one I used and all of us 747m users should install. 5.4.0.4 or something like that. Definitely not 5.8.x.x. I could have told u that would brick your phone and most proper posts would too. And unfortunately yes the recovery resides in the boot loader area so it can cause a brick.. so keep that in mind when u get your phone fixed. Either use the earlier cwm rec version or just change to TWRP RECOVERY which I just did and many recommend now anyways.
Good luck and I'll come back to post the link with the best root and cwm rec install forOUR 747M phones and remember there are some differences and not all 747 mods will work for us so please read up first
Sent from my SGH-I747M using xda premium
pchemerys said:
Yeah just go to Samsung. Its too bad u never read that the newer versions of CWM recovery don't work on the 747m. The 747 and our m variants are close but still a bit different in a few ways although when coming here for rooms and stuff we have to use this at&t 747. Section. There is a great rooting post under the development stickies and it mentions the UNICERSAL VERSION OF CWM RECOVERY FOR 747m phones and that is the one I used and all of us 747m users should install. 5.4.0.4 or something like that. Definitely not 5.8.x.x. I could have told u that would brick your phone and most proper posts would too. And unfortunately yes the recovery resides in the boot loader area so it can cause a brick.. so keep that in mind when u get your phone fixed. Either use the earlier cwm rec version or just change to TWRP RECOVERY which I just did and many recommend now anyways.
Good luck and I'll come back to post the link with the best root and cwm rec install forOUR 747M phones and remember there are some differences and not all 747 mods will work for us so please read up first
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
I don't think the version he used was the issue as other Canadian users report that 5.8.x.x works fine.
http://forum.xda-developers.com/showthread.php?p=29664739
Edit: the link with instructions for terminal emulator on the op is for the lg thrill which writes the recovery onto block 6. On this phone it needs to be written to block 18.
Sent from my HTC One S using xda app-developers app
Frowben said:
I don't think the version he used was the issue as other Canadian users report that 5.8.x.x works fine.
http://forum.xda-developers.com/showthread.php?p=29664739
Edit: the link with instructions for terminal emulator on the op is for the lg thrill which writes the recovery onto block 6. On this phone it needs to be written to block 18.
Sent from my HTC One S using xda app-developers app
Click to expand...
Click to collapse
Ah yes..that makes sense. That would pooch the phone. As for cwm it appears I was mislead as I read on few posts that newest versions don't work or not recommended for Canadian variant but it appears u might be right and I'm now seeing more and more report that it is installable. I'll have to check it out. Thanks
You flashed a recovery for the LG Thrill 4G. At what point in time did you assume it was the same phone as the I747M? You have bricked your phone. It needs JTAG service. Samsung will probably cover it under warranty, or you can pay someone that has the equipment to do it. You have no other options at this point. When you get it back from repairs, make sure you only flash AT&T/Bell/Telus/Rogers I747(M) software to the phone....
Ya i got the phone back from Samsung after waiting 3 weeks. They had to change the motherboard on the phone. Yes, it was the wrong instructions i followed which screwed me over! Since than i re-rooted how i did the first time i got the phone. Just a few days ago i saw the new CyanogenMod 10 M1 Rom, which i wanted to install. And again like last time in order to install it i had to upgrade my CWM to the newest version. This time i did not rush into it like last time and consulted with my buddy who is an expert in Android. The problem i had last time was i downloaded the new CWM in an .img file, and this time i ended up finding the newest CWM in a .tar and used Odin to flash it successfully. Than i just installed the rom and was good to go. My main reason for wanting to install a custom rom was i was getting absolutely HORRIBLE battery life from my S3. I ended up buying a juice pack which greatly helped me out. But now that i have CM10 my battery life is phenomenal, + the juice pack i now go maybe 2 days without having to charge. Now my sister who has the Wind Mobile S3 T999V wants me to upgrade her rom to the same as mine. I have found the T-Mobile CWM for her phone, and all the relevant software, but i am still hesitant to install the CWM on her phone. The T-Mobile CWM 6.0.1.2 is compatible with the Wind Mobile S3 T999V right? Or do i have to use a different version?
just to be clear about where you went wrong (im sure its been said already)
the guide you followed to install cwm is from the lg thrill forum. so the command dd if=... of=... had the wrong device id which is the most common cause of a brick
its actually pretty difficult to mess up your phone as long as you don't use mods designed for other devices
jefferson9 said:
just to be clear about where you went wrong (im sure its been said already)
the guide you followed to install cwm is from the lg thrill forum. so the command dd if=... of=... had the wrong device id which is the most common cause of a brick
its actually pretty difficult to mess up your phone as long as you don't use mods designed for other devices
Click to expand...
Click to collapse
Yes, i know that. I realized after i had done everything that the instructions where for another phone. Now im trying to find the CWM 6.0.1.2 for my sister phone T-Mobile S3 T999V that is in a .tar file already. Any suggestions on where i can get it?
I use cwm 5.8 .0.4 i think and it works fine go to the dev stickies and its there
Sent from my SAMSUNG-SGH-I747 using xda premium
JB calhoun said:
I use cwm 5.8 .0.4 i think and it works fine go to the dev stickies and its there
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
Ya for my sisters phone i have that version as a flashable tar, however to install CM 10 M1 i need to install CWM 6.0.1.2.
Did u try rom manager
Sent from my SAMSUNG-SGH-I747 using xda premium
Since the new Jelly Bean bootloaders have shown up, I see a lot of people talking about updating them. There are a few things I would recommend to do when flashing them. The first is the small, but present, danger that you can hard brick your phone. And I mean the "Need jtag to make it work" hard brick. Typically the cause of these bricks is an error or interruption of communications between the device and the computer. The other is mismatched or outright improper bootloaders.
Below is a list of things to decrease the possibility of permaborking. Keep in mind that following this list will not 100% remove the danger of flashing bootloaders, but will increase the chances of a successful flash.
Flashing bootloaders is dangerous. They are one of the few things that has the possibility of hard bricking your phone. For that reason, here are some good things to do to prepare for flashing them.
Have a good, reliable data cable. Interruption of communication between your phone and pc will most likely cause a hard brick with bootloaders.
Use a usb port on the back of your computer (or #1 on a laptop). Communication, again.
Have a jig. Not much help if you hard brick, but if you soft brick its very nice to have.
I personally flash bootloaders from a good laptop with a fully charged battery. If there is a power outage, the battery in the laptop will have saved my phone.
When flashing bootloaders,or anything with Odin, don't touch your phone after you connect it in dl mode until the phone reboots. Goes back to the communication issue.
For problems/tips on connection issues, look HERE
To determine which bootloader you have, check out this app:
https://play.google.com/store/apps/details?id=org.freeandroidtools.root_checker
To check your bootloader version
(thanks to KorGuy123 for the link)
For those that like to use Terminal Emulator, just type this:
HTML:
su
getprop ro.bootloader
Hi,
I know this is close to impossible, but still want to bring it up to see if anyone here knows.
My s3's USB port seems damaged physically or something. It charges fine, but it always shows unrecognized USB device when connecting to PC. No matter it is in download mode or booted mode and how hard I try(install updated USB driver, change PC etc. )
No the question comes - can I upgrade boot loader without USB? If not I will be stuck with older version of cm10.1 for ever
TIA
Sent from my SAMSUNG-SGH-I747 using xda premium
xlj1000 said:
Hi,
I know this is close to impossible, but still want to bring it up to see if anyone here knows.
My s3's USB port seems damaged physically or something. It charges fine, but it always shows unrecognized USB device when connecting to PC. No matter it is in download mode or booted mode and how hard I try(install updated USB driver, change PC etc. )
No the question comes - can I upgrade boot loader without USB? If not I will be stuck with older version of cm10.1 for ever
TIA
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
No, you need a usb port to do it. You might try using Heimdall, as it uses a different driver. If you use heimdall, you will need to do a lot of research as it operates a little differently than Odin.
Flashing Bell Galaxy S3 Bootloader on AT&T phone
Would it be possible to flash a SGH-I747M (Bell) bootloader on a SGH-I747 (AT&T). I would like to have the option to toggle LTE off when I am in a non LTE area without going through the Network Control option discussed on xda, as I have been doing.
If it's not the exact bootloader for your phone, don't flash it.
mrhaley30705 said:
No, you need a usb port to do it. You might try using Heimdall, as it uses a different driver. If you use heimdall, you will need to do a lot of research as it operates a little differently than Odin.
Click to expand...
Click to collapse
Maybe use Mobile Odin?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
It is not recommended to write bootloader with Mobile Odin. Furthermore, it just won't do it:
From Chainfire:
All partitions are supported, as are loose files, .tar files and .tar.md5 files. Mobile ODIN will even check the MD5 signatures before flashing. While in theory Mobile ODIN can repartition and flash EFS and bootloaders, it will cowardly refuse to do so, for your own safety.
mrhaley30705 said:
It is not recommended to write bootloader with Mobile Odin. Furthermore, it just won't do it:
From Chainfire:
All partitions are supported, as are loose files, .tar files and .tar.md5 files. Mobile ODIN will even check the MD5 signatures before flashing. While in theory Mobile ODIN can repartition and flash EFS and bootloaders, it will cowardly refuse to do so, for your own safety.
Click to expand...
Click to collapse
Awesome, gotcha. Learn something new every day.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
mi modelo is i747m telcel mexico which should flash
Obridgenut said:
Would it be possible to flash a SGH-I747M (Bell) bootloader on a SGH-I747 (AT&T). I would like to have the option to toggle LTE off when I am in a non LTE area without going through the Network Control option discussed on xda, as I have been doing.
Click to expand...
Click to collapse
I have no idea why you would have to do that. If you have your setting correct it will do it automatically. My does on Telus. Or did you follow some of the instuctions here and loaded a bad image to your phone. Best to flash a stock image to your phone that has been rooted and then use rom manger or goomanager to flash a recovery to your phone if you want one. I have a rooted stock rom and I no recovery as they are a waste of time. I used triangle to reset the trip and I can update OTA with no issues and it states my devise status is normal. I had used some other rom on my phone and it drained the battery all the time. Now it works like a charm. I can even use back track or other linux distro's on it,
As for the other guy having an issue, you can update your phone over Kies. Your issues sound like its a bad rom you put on your phone. And you can never brick your phone. Its what people to say to scare you to get you to use their methods.
Is it possible that installing a custom rom would have installed the latest bootloader. I didn't install myself and it looks like I have the latest per the device info app I downloaded from the play store
Sent from my SGH-I747 using xda premium
osmxgohan said:
mi modelo is i747m telcel mexico which should flash
Click to expand...
Click to collapse
The correct firmware from your provider should have bootloader in then
andy_d0 said:
Is it possible that installing a custom rom would have installed the latest bootloader. I didn't install myself and it looks like I have the latest per the device info app I downloaded from the play store
Sent from my SGH-I747 using xda premium
Click to expand...
Click to collapse
It's possible that the ota update to jelly bean pushed the latest bootloader to your phone.
TheStrokerace said:
I have no idea why you would have to do that. If you have your setting correct it will do it automatically. My does on Telus. Or did you follow some of the instuctions here and loaded a bad image to your phone. Best to flash a stock image to your phone that has been rooted and then use rom manger or goomanager to flash a recovery to your phone if you want one. I have a rooted stock rom and I no recovery as they are a waste of time. I used triangle to reset the trip and I can update OTA with no issues and it states my devise status is normal. I had used some other rom on my phone and it drained the battery all the time. Now it works like a charm. I can even use back track or other linux distro's on it, ]
The AT&T SGH-I747 does not offer the option to toggle LTE off under the Settings Menu, as do the Bell, Telus etc SGH - I747Ms. And although I can and have flashed all sorts of different ROMs, the AT&T modem is RAT locked and I so far have been unsuccessful flashing any modems other than AT&T modems. I am not sure whether this is a software issue or whether it is to do with the AT&T bootloader, hence the question about flashing a Bell bootloader. Any time that I try to flash a non-AT&t MODEM, I temporarily lose my IMEI number and the phone will not work at all. But there is a work around by entering into the Phone Control settings as discussed on xda, ( http://forum.xda-developers.com/showthread.php?t=2116346) which I have been using successfully.
Click to expand...
Click to collapse
I don't think changing the bootloader will change that for you.
mrhaley30705 said:
I don't think changing the bootloader will change that for you.
Click to expand...
Click to collapse
OK, Thanks anyway for your help.
How can I tell what version my bootloader is?
Hey all~
1st, my internet is so sluggish today, I can almost do nothing on the forums, so if this is a repeat question, forgive me, simply reply with the link please.
What I would like to know is how can I find out what version my bootloader is?
I am running CM 10.0 Stable on my Galaxy S3 i747 [AT&T]
I want to update to 10.1 RC4, but I've read warnings relating to the old version of the bootloader, but nothing saying how to tell what version bl I have ...
suggestions?
Thanks
~Jason
ubuntujason said:
Hey all~
1st, my internet is so sluggish today, I can almost do nothing on the forums, so if this is a repeat question, forgive me, simply reply with the link please.
What I would like to know is how can I find out what version my bootloader is?
I am running CM 10.0 Stable on my Galaxy S3 i747 [AT&T]
I want to update to 10.1 RC4, but I've read warnings relating to the old version of the bootloader, but nothing saying how to tell what version bl I have ...
suggestions?
Thanks
~Jason
Click to expand...
Click to collapse
Install this, hit check, goto second screen and it'll say bootlader
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Easiest way to check is install terminal emulator.
Type
su
Grant it permission
Now type:
getprop ro.bootloader
These commands are case sensitive, so type carefully
So, I recently bought a galaxy s4 from ebay, and it seems to work on the network, so I don't think the IMEI is blacklisted. However, when I tried the steps here http://forum.xda-developers.com/showthread.php?t=2282683 and here http://forum.xda-developers.com/showthread.php?t=2283068, I am unable to complete the process. When I do the latter, which seems more like what I did with my S3, I get the same message "unable to process request". I remember I was getting this message on my S3 when I had the SlimKat ROM on it. But when I look at my S4, it looks like it has the OEM ROM on it, so I am not sure what is happening. I looked at my boot loader/baseband, and this is what I have: m919uvufnh7. I know that with my S3 I had to make sure I used the correct ROM to flash my phone, so I could get it unlocked the free method. So, does anyone know what bootloader and ROM could help me accomplish these steps in the second thread?
I am thinking I should flash a different ROM on my phone.
mji2015 said:
So, I recently bought a galaxy s4 from ebay, and it seems to work on the network, so I don't think the IMEI is blacklisted. However, when I tried the steps here http://forum.xda-developers.com/showthread.php?t=2282683 and here http://forum.xda-developers.com/showthread.php?t=2283068, I am unable to complete the process. When I do the latter, which seems more like what I did with my S3, I get the same message "unable to process request". I remember I was getting this message on my S3 when I had the SlimKat ROM on it. But when I look at my S4, it looks like it has the OEM ROM on it, so I am not sure what is happening. I looked at my boot loader/baseband, and this is what I have: m919uvufnh7. I know that with my S3 I had to make sure I used the correct ROM to flash my phone, so I could get it unlocked the free method. So, does anyone know what bootloader and ROM could help me accomplish these steps in the second thread?
I am thinking I should flash a different ROM on my phone.
Click to expand...
Click to collapse
Have you tried contacting T-Mobile? If the phone is paid for in full, they are supposed to unlock it for free.
This worked for me:
http://forum.xda-developers.com/showthread.php?p=58645651
Sent from my SGH-M919 using XDA Free mobile app
rlichtefeld said:
Have you tried contacting T-Mobile? If the phone is paid for in full, they are supposed to unlock it for free.
Click to expand...
Click to collapse
Thanks for the response, but I have not tried it, because I don't think it is that easy. I also purchased AT&T tablets and tried unlocking them, but AT&T said they were 'active' under someone else. They were not not showing as stolen, but active. I am not sure what that entails, but I am guessing I have to register it under my account first, before I can request to unlock it. So before I try going through the long process of figuring out how T-Mobile can unlock my device, I thought I would give this a try. It seems simpler and since I plan on modding my phone after I unlock it, I see it as just part of the process. (At least I hope so.)
radoo7701 said:
This worked for me:
http://forum.xda-developers.com/showthread.php?p=58645651
Sent from my SGH-M919 using XDA Free mobile app
Click to expand...
Click to collapse
I will try this. But I was trying to make sure that there was no problem with downgrading, as I am currently on 4.4.4. And I know that on my S3 there was a big warning about downgrading from 4.3 to 4.1. To avoid bricking my phone, I thought I would ask and make sure.
So thanks again to both of you for the responses!
I will try this. But I was trying to make sure that there was no problem with downgrading, as I am currently on 4.4.4. And I know that on my S3 there was a big warning about downgrading from 4.3 to 4.1. To avoid bricking my phone, I thought I would ask and make sure.
So thanks again to both of you for the responses![/QUOTE]
You only have to downgrade the modem. This should not brick your phone.
Sent from my SGH-M919 using XDA Free mobile app
Would you please posts step by step on what you did to successfully unlock 4.4.4 T-Mobile which I assume is version M919UVUFNK2.
How to Unlock Samsung Galaxy S4 M919 4.4.4
c627627 said:
Would you please posts step by step on what you did to successfully unlock 4.4.4 T-Mobile which I assume is version M919UVUFNK2.
Click to expand...
Click to collapse
Alright, I was able to get mine to work, so maybe I will list my steps. However, I must say that I had some failed attempts (in part due to not understanding the post referred to by radoo7701) and some issues with my phone. But those steps wont be included. Also, my version was m919uvufnh7, not NK2. I would think it does not make a difference, as long as you reflash back to NK2 at the end.
1. I locaed the modem for M919UVUAMDL and m919uvufnh7 modem (as I did not make a backup of mine before starting)
2. I used Odin 3.07 to flash the AMDL modem
3. I tried the steps here http://forum.xda-developers.com/showthread.php?t=2283068, but this would not work, I could not even get the menu to pull up, as it would say request unable to complete. So I tried this http://forum.xda-developers.com/showthread.php?t=2282683 and that actually worked, so I went through these steps successfully.
4. Use cf-auto-root to root your phone
5. Download regionlockaway and transfer it to phone, then install it on phone and run it.
6. flash m919uvufnh7 modem and booted up with my AT&T sim, and it did not ask for unlock code. It just worked!
NOTE: I did have to use a T-Mobile sim card to do the menu process, but radoo claims that he did not do the menu portion. I had already done the menu portion when I finally got to reading his comment. So I can't say that it will work or not. Either way, his suggestion worked for me and I am content with the result!
Thanks radoo7701!
Please post link to files in step 1 you specifically used. And also links for step 5 you used.
Edit: The Verizon repair assistant put my phone back to PHE build [100% battery].
Man I knew I shouldn't have tried to root after all this time. I'm not sure which firmware my phone was on [it was the 60% battery update], either PHE or PK1, as it displays in recovery right now. I tried to follow Lrileys modification of freeza's root guide, which neither of them specify a base firmware to go off of, lol.
Anyways, flashing the userdebug sprint firmware with ODIN 3.12.4 failed and my device softbricked. It boots into recovery and download mode.
I have tried factory reset, wiping cache partition, flashing an AP PH1 firmware, and repair through Verizon software/upgrade assistant.
The closest I've gotten to restoring it was with VUA, however when I go to the repair assistant page, it tells me to put phone in download mode [which I do] but the repair button stays greyed out.
Any help would be greatly appreciated.
Edit: The Verizon Upgrade Assistant wasn't starting, saying it was missing mfc90.dll. Well I downloaded the dll, dropped it in the folder, and was able to get UA to recognize phone. Repair assistant is downloading software right now, we'll see how it goes.
IF you would have read there is no root for the PHE.. you also could have checked this via phone settings before you rooted.
You can also use the verizon app to restore your firmware from even the most bricked of phones. Also in in this forum..(looks like you might have tried this?)
I wouldnt even bother at this point, go get your temp phone =]
ars0n said:
IF you would have read there is no root for the PHE.. you also could have checked this via phone settings before you rooted.
You can also use the verizon app to restore your firmware from even the most bricked of phones. Also in in this forum..(looks like you might have tried this?)
I wouldnt even bother at this point, go get your temp phone =]
Click to expand...
Click to collapse
Well the repair assistant seems to be working atm, so hopefully it goes through without any problems. Neither of these threads in the original post mentioned anything about incompatible firmware though [https://forum.xda-developers.com/verizon-note-7/how-to/root-vzw-note-7-t3448711 and https://forum.xda-developers.com/sprint-note-7/how-to/root-super-leaky-bros-sprint-galaxy-t3447202]. I suppose I should have known trying to use a method that dated.
You shouldn't be messing with this stuff if you don't even know how to see what version your on and read.
very helpful
jjayzx said:
You shouldn't be messing with this stuff if you don't even know how to see what version your on and read.
Click to expand...
Click to collapse
Thank you for the gratuitous reply. Despite your sour attitude I was able to return to PHE through VUA. I was running PK1 firmware, however, again, neither root method specified/recommended/listed a base or stock firmware to flash from [or even posted what they were running]. This place used to be helpful.
Hi, I recent bought this phone and I love it, but, the sprint firmware is really bad, have a lot of bugs nad it makes the phone slow. Im looking for a safe way to change it.
Thanks You!
See my post #81 from another thread....
Rika Kunisaki said:
Hi, I recent bought this phone and I love it, but, the sprint firmware is really bad, have a lot of bugs nad it makes the phone slow. Im looking for a safe way to change it.
Thanks You!
Click to expand...
Click to collapse
Thread link: https://forum.xda-developers.com/z2-force/development/factory-image-moto-z2-force-nash-retail-t3699306/page9
Actually, read the whole thread from the beginning.
You can change the firmware, it's relatively easy, the only thing you will be stuck with is the Sprint baseband (i.e. basically, your phone will still use the GSM/4G frequencies enabled in the Sprint baseband). You will also need to manually update the firmware as the OTA will most likely fail because it will be Sprint's OTA as opposed to generic USA retail firmware.
I did this the other day and have today updated to Oreo, it worked ok. So, basic steps are:
1/ Unlock bootloader via Moto website. Follow their instructions.
2/ Download the generic Z2 force firmware from the same thread above, unzip it, and effectively follow reflashing as indicated in the flashfile.xml.
3/ Put the phone into the fastboot/adb mode and use fastboot command to flash.
It goes quickly, of course you need to have Android tools installed (fastboot/adb) and you need to have your phone connected to the PC via USB(-C) cable.
That's pretty much it. As I said, you will be stuck with the Sprint software channel which I don't know how to change. If you figure out, please share...
collaborator said:
Thread link: https://forum.xda-developers.com/z2-force/development/factory-image-moto-z2-force-nash-retail-t3699306/page9
Actually, read the whole thread from the beginning.
You can change the firmware, it's relatively easy, the only thing you will be stuck with is the Sprint baseband (i.e. basically, your phone will still use the GSM/4G frequencies enabled in the Sprint baseband). You will also need to manually update the firmware as the OTA will most likely fail because it will be Sprint's OTA as opposed to generic USA retail firmware.
I did this the other day and have today updated to Oreo, it worked ok. So, basic steps are:
1/ Unlock bootloader via Moto website. Follow their instructions.
2/ Download the generic Z2 force firmware from the same thread above, unzip it, and effectively follow reflashing as indicated in the flashfile.xml.
3/ Put the phone into the fastboot/adb mode and use fastboot command to flash.
It goes quickly, of course you need to have Android tools installed (fastboot/adb) and you need to have your phone connected to the PC via USB(-C) cable.
That's pretty much it. As I said, you will be stuck with the Sprint software channel which I don't know how to change. If you figure out, please share...
Click to expand...
Click to collapse
Thank you!! Ill read it and see
With this software installed, could we downgrade using a flashall? Just in case it's needed for warranty purposes?