Related
See my reply to this thread on page 2 for the resolution.
---
So I unlocked and rooted my VZW LTE galaxy nexus a couple months ago, no problems with the process.
I looked into updating from 4.0.2 to 4.0.4 and found this walkthrough for YAKJU IMM76D:
androidadvices.com/update-galaxy-nexus-official-ics-404-firmware-odin/2/
Page 1 goes through checking USB debugging, what to back up first, etc. USB debugging was enabled already.
Page 2 (link above) provides the instructions on what to download, how to run it, etc. I followed the steps there. It went through:
---
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> bootloader.img
<ID:0/008> NAND Write Start!!
<ID:0/008> boot.img
<ID:0/008> recovery.img
<ID:0/008> system.img
<ID:0/008> userdata.img
<ID:0/008> radio.img
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
---
As it stands, if I put the battery in the phone, the screen will turn on and display an icon of a mobile device, two dots, a warning ! triangle, two dots, and a PC monitor.
Pressing the power button "reboots" back to this screen - it just turns off, then turns back on.
Vol up and power does the same thing - does not go into recovery
vol down and power does the same thing
vol up, vol down, and power does the same thing
pulling/replacing the battery does the same thing
I am able to re-run Odin3 v1.85 with the PDA download option checked, specifying that same .tar. It will still go through 95% of the process and end the same way, with "FAIL!" shown in Odin and an almost-complete blue progress bar on the phone below that other error image described above.
So, I *think* this should be salvageable, but I don't know how or what/where to find the file(s) that I should be using to fix this.
THANK YOU for reading and any advice you have, and let me know if anything needs clarification. Screenshot of Odin results attached (seems to not be working... imgbucket link alternative: imgbucket.info/photo/ggnkdlyyu/Odin3_v1_failed.jpg)
Youre phone has nothing to boot from. That's what that means... (Check my signature) use that, reflash stock 4.0.2, try again... And do a backup, first!!
If you're very unlucky, you buggered up the whole memory unit. That means, loss of EVERYTHING...
Oh, and: Stop being a whimp Be a man. Stand above it. Think: "I can do it!!"...
It may sound harsh, at first. But, if you would know, how many times, that has happend, with a Samsung Phone, to me... And if I would have given up, I wouldn't have gotten me a developers phone
So, be strong, (Use my root helper) And tell that phone, who's boss!
Ok, thanks. I'll try that. I don't care that I "lost" everything on the phone as long as I can "fix" the phone. Email, photos, contacts, music, etc - all very easy to replace, or it's just cloud stuff anyways.
trevordyck said:
Ok, thanks. I'll try that. I don't care that I "lost" everything on the phone as long as I can "fix" the phone. Email, photos, contacts, music, etc - all very easy to replace, or it's just cloud stuff anyways.
Click to expand...
Click to collapse
I like your way, of thinking
Like a man!
The yakju build is for the GSM model only. Stock images for the Verizon version are called mysid.
They are not interchangeable.
Currently the most recent Verizon version is 4.0.2.
Sent from my Xoom using XDA Premium HD app
El Daddy said:
The yakju build is for the GSM model only. Stock images for the Verizon version are called mysid.
They are not interchangeable.
Currently the most recent Verizon version is 4.0.2.
Sent from my Xoom using XDA Premium HD app
Click to expand...
Click to collapse
OH, well that explains everything! Thanks for that clarification... now back to trying to un-bork my handiwork.
Time to try to get into Odin mode.
Sent from my Galaxy Nexus
Time to "stay" in Odin mode... playing with Odin (ignorantly, a bit) is what got me here...
axne1 said:
Time to try to get into Odin mode.
Click to expand...
Click to collapse
Well I haven't made any progress on the phone, but I've done a few things to try familyguy's stuff. I think I have the latest version of that, and the 4.0.2 downloaded via the program, but I get this error message every time I try to flash a stock LTE ROM with it. Do I need to do this with Odin, this program, or something else?
I think you should read this
http://forum.xda-developers.com/showthread.php?t=1600203
Sent from my Galaxy Nexus
Aha! Thank you much for that. Following a few links I think I can fix it just by specifying a suitable firmware, because Odin does actually run the "PDA" flash until the end (progress bar still shows up on my "soft bricked" display and Odin indicates it's copying stuff). So, when I land later tonight I'll download and give this a try:
dl.google.com/dl/android/aosp/mysid-icl53f-factory-65895fa8.tgz
I guess I'm not really asking any useful question here so much as tracking my attempts... hope I get this sorted before work in the AM!
Awesome!!!
Keep us updated!
Sent from my Galaxy Nexus
No luck yet. I can still run the GSM "Phone" flash in Odin until 95% complete when it fails, but all of my attempts at using Google's archived 4.0.2 for CDMA are stopping at about 15%, and I have to R&R battery to restart it. This is as far as I can get:
<ID:0/008> Added!!
<ID:0/008> Odin v.3 engine (ID:8)..
<ID:0/008> File analysis..
<ID:0/008> SetupConnection..
<ID:0/008> Initialzation..
<ID:0/008> Get PIT for mapping..
<ID:0/008> Firmware update start..
<ID:0/008> boot.img
<ID:0/008> NAND Write Start!! (*sits here indefinitely)
Any pointers on what is required for the various fields to flash a stock setup to this thing using Odin?
It sounds like it's looking for some type of backup like a nandroid
Sent from my Galaxy Nexus
There is a tool on amazon.com that should help it's called a jig or something like that.
Sent from my Galaxy Nexus
AHHHH! FIXED!
Things I learned:
- Odin is a Samsung product and needs special samsung-y .tar files to flash the phone. Regular ROM stuff doesn't work. (pardon the ignorance in terminology)
- "mysid" specifies a VzW compatible build for the GNEX
- If you accidentally flash a GSM tar to your VzW phone using Odin, Odin is the only thing that will get you out of your sitch (of the things I could figure out how to try. I didn't try any command line stuff. That's last ditch for me - takes more time for me to learn, and a busy Monday morning at work wasn't helping me)
- I found the resolution here: http://forum.xda-developers.com/showthread.php?t=1426207&page=5 - a factory Odin pair of files for CDMA/VzW, one for PHONE and one for PDA. Saved. My. Bacon.
- The $10 wifi on Alaska Airlines is slow as junk.
- Starting this whilst abroad is a bad idea. (HAHA!)
Regarding the walkthrough I followed that got me in this mess - nowhere that I saw did the author (or readers) specify that the flash I was about to try was GSM only. Maybe I missed that detail, but if not it would make sense to me that someone reading a tutorial on how to flash their phone probably would have NO IDEA that yukjiwhatever is GSM and mysid was for CDMA. That would have been good to read, like, in the first paragraph of the article. Anyways...
I have a working phone and somewhere unicorns are grazing in a field. I hope this helps some other equally poor sap recover his phone.
To start, you will need
Recovery-cmw-hercules.tar (doesn't have to be the latest, you can update it later). This can be found in other recovery threads, as the process remains the same.
Odin3 v1.85 (or any other compatible version)
root.zip found Here
Steps:
1) Make sure Kies is exited, and you have the drivers installed for Odin. If not, check the other threads as this has been covered many times
2) Just select your CWM recovery for PDA once you are in DL mode (which is achieved by holding down VOL Up and VOL Down when the phone is off as you plug in the cable). Select vol up to confirm dl mode.
3) In Odin, leave the default boxes (Auto reboot and F. Reset time), and then select PDA and choose the .tar file we found earlier. Make sure odin sees your phone properly and start this!
4) once you have CWM recovery installed copy the root.zip to your sd card, and boot into CWM recovery. Do a Nand Backup and then install root.zip and enjoy!
5) Delete that crappy bloat!
For those having connection issues in Odin, try the following.
1) Exit Kies
2) Change to a different USB port
3) Reinstall your USB drivers.
I kept getting an error, and the above fixed that.
Thank you!
Root.zip being stock ics official tmo release??
Sent from my Galaxy SII T-mobile using XDA
Thanks a lot for posting this for everyone. Hopefully this will quell the 50 billion requests that could be handled by using search or google.
TheTechNiq said:
Root.zip being stock ics official tmo release??
Sent from my Galaxy SII T-mobile using XDA
Click to expand...
Click to collapse
Its should work the same, my official tmo 4.03 ics
was just rooted doing this
so it's the same process?
Not working for me. Get the following odin error:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Teo032 said:
so it's the same process?
Click to expand...
Click to collapse
Yes but make sure you download the root.zip file OP posted a link to.
Once you're done with the odin part, having the recovery-cmw-hercules .tar all done.
You should see CWM rom manager in your app, you can click on it but cant really use it. because you don't have superuser permission, That why you need to copy the root.zip file to your sd card. Now get in to CW recovery by turning off the phone.
hold vol. up+down,and hit the power on button, scroll down and install the root zip.
then reboot. now you should have superuser permission and can now uninstall, or freeze all the junk with Titanium backup.
kwilsonjr said:
what do you mean 'leave the default boxes'?!? leave them checked? leave them unchecked? leave them alone? what? I'm assuming you mean leave the boxes alone (default).
Click to expand...
Click to collapse
Don't touch anything but the PDA button, select the .tar file, and click start.
For those worried about using the GB root process with the new ICS ROM, the Kies flashing does not put a new recovery on it. It's the same one that shipped with your phone. Therefor overwriting the the recovery with CWM 5.0.2.6 (via Odin) is the exact same. The root.zip flashed from VWM just installs su, busybox, and the superuser.apk into the OS, this has been done on many ICS roms already.
TL;DR: the process is identical, and confirmed working.
Rooted! T989 with Stock ICS update!
Thank you So Much! It Worked!!! For all of you who are doing this:
You will first need to install Busy Box update before Titanium will work. It takes a few seconds (20 - 30secs) then you will see "Allow Super User..."
Thanks again Starting to delete Crap ware now!
ResidentJack said:
Thank you So Much! It Worked!!! For all of you who are doing this:
You will first need to install Busy Box update before Titanium will work. It takes a few seconds (20 - 30secs) then you will see "Allow Super User..."
Thanks again Starting to delete Crap ware now!
Click to expand...
Click to collapse
Busybox is included in the root.zip in this post?
Worked like a charm thanks!
Damn... Stuck on "Goodbye"
Ok, so I rooted and it worked perfectly, only problem is I'm now getting stuck on "Goodbye" screen when shutting down, or when restarting. I have removed the battery for 2 minutes, wiped cache, wiped dalvik...
Still the same thing...
Anyone have any ideas?
Thanks
kwilsonjr said:
Not working for me. Get the following odin error:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Can't open the serial(COM) port.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
OK. Don't know what the heck is going on. Closed and re-opened odin 5 times and tried each time. It finally took on the 5th try. weird.
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> RQT_CLOSE !!
<ID:0/005> RES OK !!
<ID:0/005> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
<ID:0/005> Removed!!
<ID:0/007> Added!!
What did you guys use to remove all the bloatware?
n/m found it.
Blackleopord187 said:
What did you guys use to remove all the bloatware?
Click to expand...
Click to collapse
I freeze it with titanium backup.
I can confirm the reboot hang issue.
ian577416 said:
I can confirm the reboot hang issue.
Click to expand...
Click to collapse
maybe its an isolated incident on some devices? (I used the OP's root method) I just tried restarting and turning off my phone and i get no hangs on the goodbye screen or anything.
No hang issues here. Root method works great.
Bloat removed,,,,,ALL OF IT!!!!!
galaxy note 2:
hi there guys. I am a practising noob. I am facing similar problems to a small portion of people here. Tried different PCs and cables.
when i attempt to go into recovery, my screen goes grey with horizontal lines across. I am able to get into download but cannot go any further.
I had Omega Rom v22 which was 4.3 installed and one day it froze on the logo screen. i turned it off and put it back on. no luck. Kies keeps trying to connect but doesn't recognise it.
now on the downloading screen, im displaying,
ODIN MODE (in red)
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Update:
N7100XXDMB2_N7100OXADMA5_N7100XXDLK7_FACTORY_XEF\N7100XXDMB2_N7100OXADMA5_N7100XXDLK7_FACTORY_XEF.TAR
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
Also this phone was bought through ebay and the warranty has expired, on top of that, somehow it was imported from UAE, but i was led to believe it was an UK product because i bought it from a UK seller. silly me lol.
Guys i want to thank you in advance with whatever help you can offer me. i have withdrawl symptoms without my phone.
XXM3G4XX said:
galaxy note 2:
hi there guys. I am a practising noob. I am facing similar problems to a small portion of people here. Tried different PCs and cables.
when i attempt to go into recovery, my screen goes grey with horizontal lines across. I am able to get into download but cannot go any further.
I had Omega Rom v22 which was 4.3 installed and one day it froze on the logo screen. i turned it off and put it back on. no luck. Kies keeps trying to connect but doesn't recognise it.
now on the downloading screen, im displaying,
ODIN MODE (in red)
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Update:
N7100XXDMB2_N7100OXADMA5_N7100XXDLK7_FACTORY_XEF\N7100XXDMB2_N7100OXADMA5_N7100XXDLK7_FACTORY_XEF.TAR
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
Also this phone was bought through ebay and the warranty has expired, on top of that, somehow it was imported from UAE, but i was led to believe it was an UK product because i bought it from a UK seller. silly me lol.
Guys i want to thank you in advance with whatever help you can offer me. i have withdrawl symptoms without my phone.
Click to expand...
Click to collapse
Make sure you have usb debugging checked in developer options. I had thew same problem as you but once I selected usb debugging it worked..
Phone doesn't turn on
colint3 said:
Make sure you have usb debugging checked in developer options. I had thew same problem as you but once I selected usb debugging it worked..
Click to expand...
Click to collapse
Hi Colint3 thank you for the first person to reply. Much appreciated.
How can I select USB debugging if the phone doesn't come on for me to access the option.
Although if I remember correctly, I already had it on before this incident occurred.
Update 05/02/2014
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> BL_N7100XXUEMK9_2138564_REV04_user_low_ship.tar.md5 is valid.
<OSM> AP_N7100XXUEMK9_2138564_REV04_user_low_ship.tar.md5 is valid.
<OSM> CP_N7100XXUEMJ9_REV08_CL1423182.tar.md5 is valid.
<OSM> CSC_OXX_N7100OXXEMK4_2174777_REV04_user_low_ship.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
still nothing. Any further ideas guys?? thanks again.
XXM3G4XX said:
galaxy note 2:
hi there guys. I am a practising noob. I am facing similar problems to a small portion of people here. Tried different PCs and cables.
when i attempt to go into recovery, my screen goes grey with horizontal lines across. I am able to get into download but cannot go any further.
I had Omega Rom v22 which was 4.3 installed and one day it froze on the logo screen. i turned it off and put it back on. no luck. Kies keeps trying to connect but doesn't recognise it.
now on the downloading screen, im displaying,
ODIN MODE (in red)
PRODUCT NAME:
CUSTOM BINARY DOWNLOAD: No
CURRENT BINARY: Samsung Official
SYSTEM STATUS: Custom
Update:
N7100XXDMB2_N7100OXADMA5_N7100XXDLK7_FACTORY_XEF\N7100XXDMB2_N7100OXADMA5_N7100XXDLK7_FACTORY_XEF.TAR
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Set PIT file..
<ID:0/004> DO NOT TURN OFF TARGET!!
<ID:0/004> Get PIT for mapping..
Also this phone was bought through ebay and the warranty has expired, on top of that, somehow it was imported from UAE, but i was led to believe it was an UK product because i bought it from a UK seller. silly me lol.
Guys i want to thank you in advance with whatever help you can offer me. i have withdrawl symptoms without my phone.
Click to expand...
Click to collapse
i guess you have tick marked repartition..you should not do that..
all these roms all request pit files
iprabhsingh said:
i guess you have tick marked repartition..you should not do that..
Click to expand...
Click to collapse
i have followed so many guides its unbelievable. some say to tick, some says dont.
any roms i try to put on always gets stuck around the partition section.
im looking for a good n7100 pit file thats pretty new and is known to work please. would be really helpful. thanks.
XXM3G4XX said:
i have followed so many guides its unbelievable. some say to tick, some says dont.
any roms i try to put on always gets stuck around the partition section.
im looking for a good n7100 pit file thats pretty new and is known to work please. would be really helpful. thanks.
Click to expand...
Click to collapse
just tell me what you really want to do..do you want to install custom rom..or stock rom..was your device rooted before..??
iprabhsingh said:
just tell me what you really want to do..do you want to install custom rom..or stock rom..was your device rooted before..??
Click to expand...
Click to collapse
My device was rooted. I want to get it to work. Doesn't matter with the roms. Any rom that makes it come on is good enough for me.
When I attempt to get it into recovery, all I get is a blank grey screen with white horizontal lines. Download menu doesn't show the device name and all other details are there.
I have tried everything that I've gathered from different threads as well. Keep on getting stuck on pit section.
I've spoken to samsung and sending it for repairs.
I've looked at other threads and from, that I've gathered its half sds and it's a hardware problem which according to the forums will be replaced as the technicians themselves cannot put roms on so they'll change the faulty parts, install a stock rom and send it back.
I could be wrong, so if there are anything else I could try, please advise. Many thanks.
XXM3G4XX said:
My device was rooted. I want to get it to work. Doesn't matter with the roms. Any rom that makes it come on is good enough for me.
When I attempt to get it into recovery, all I get is a blank grey screen with white horizontal lines. Download menu doesn't show the device name and all other details are there.
I have tried everything that I've gathered from different threads as well. Keep on getting stuck on pit section.
I've spoken to samsung and sending it for repairs.
I've looked at other threads and from, that I've gathered its half sds and it's a hardware problem which according to the forums will be replaced as the technicians themselves cannot put roms on so they'll change the faulty parts, install a stock rom and send it back.
I could be wrong, so if there are anything else I could try, please advise. Many thanks.
Click to expand...
Click to collapse
In my opinion if you are not able to find anything from xda or any other site..i think you should go to samsung service center..
or i guess you have bad recovery..just try to flash a new recovery like cwm or philz recovery through odin..May be this might help you.
Update to the issue NOW lol
Hi guys, hope all is well with everyone. I sent the phone to the service centre and got it back unresolved but better than originally. I have new issues which is explained in a new thread. Please advise and help if possible. Many thanks again guys. much respect.
http://forum.xda-developers.com/showthread.php?t=2658220
Hello everyone!
Today, while I was using my phone (GT-N7105) just as usual, it crashed and rebooted. "Okay", I thought, "a little annoying but it happens."
Well, I was wrong. After being stuck on the Boot Logo ("Samsung Galaxy Note 2") I held down the power button to force another restart. What I saw next really shocked me:
Again, the Samsung Logo appeared on screen, but this time with lots of white stripes all around the screen (like something was corrupted).
The next restart made it only worse.
I can't boot or access recovery mode, the only thing I can access is the Download mode.
But even this isn't working correctly, it says:
"Product Name: [This is actually blank]"
I tried flashing Stock Samsung rom with ODIN, but to no avail. I also tried it with a PIT file, but again, no luck.
I either get:
Code:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
or
Code:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Before the crash, I was happily using the latest SlimKat rom ( 4.4.2 (build 5) ).
I also tried using the Android Toolkit, but of course it doesn't find my device.
I hope that there is still something I can do... Thanks for your help!
I'm not quite sure but it looks like your internal memory died. Or it got corrupted.
Sent from my GT-N7100
PLEASE HELP US
THE SAME PROBLEM LIKE THERE
http://forum.xda-developers.com/showthread.php?t=2774775
It's the sudden death syndrome, probably we need a JTAG for our Phones or .... changing the EMMC card.... or Changing the motherboard if failing
Experts must find the cause of this problem because lot of people suffered of this problem recently (virus ? )
note2nooby said:
I'm not quite sure but it looks like your internal memory died. Or it got corrupted.
Sent from my GT-N7100
Click to expand...
Click to collapse
Mhh, that doesn't sound very good. Is there anything I can do about this?
microlynz said:
PLEASE HELP US
THE SAME PROBLEM LIKE THERE
http://forum.xda-developers.com/showthread.php?t=2774775
It's the sudden death syndrome, probably we need a JTAG for our Phones or .... changing the EMMC card.... or Changing the motherboard if failing
Experts must find the cause of this problem because lot of people suffered of this problem recently (virus ? )
Click to expand...
Click to collapse
Okay, this definitely is the SDS, this seems really, really discomforting :/
You can only do a hardware replacement to get your phone working. SDS can shut down the device permanentaly.
Sent from my GT-N7100 using Tapatalk
nice find.....
Theofrastus said:
Mhh, that doesn't sound very good. Is there anything I can do about this?
Click to expand...
Click to collapse
The only thing you can do is give it to repair. When you bought your phone?
The early note 2 had the SDS syndrome.
Well samsung updated to 4.2.1 supposedly to fix/prevent SDS. Also it could be something else you never know because you must open your phone and have a special tools to perform tests.
Best option service center diagnosis, i think it should be for free. Later you decide if you can afford repair.
Sent from my GT-N7100
Phew, I was just at the shop I bought it from, I'll get a new one, no fees or anything.
Lucky me!
A friend of mine had the same thing happen to him today (Galaxy Note 2 as well), he bought a new phone.
Please, can you ask them what is the problem and the solution
because I dont have warranty for my phone
microlynz said:
Please, can you ask them what is the problem and the solution
because I dont have warranty for my phone
Click to expand...
Click to collapse
Today, I got my new Note 2. They gave me an completely new one, and the guy handing it to me said that there was no use repairing the old one. I asked for details, but he didn't know more than that.
Sorry to let you down!
Got Black Note 7 from Verizon yesterday.
As we all know, V's firmware messed up with the original system quite a lot. So after a bit search, I decided to flash it to T-Mobile Firmware.
With Odin3, easily done. However, LTE not working, not cellular either, emergency call only. Then decided to flash to AT&T according to one of the threads(maybe link later).
After flashing to AT&T firmware, still no LTE, emergency call only.
When I tried to flash it back to Verizon, Odin3 stopped me from doing so and gives SHA256 error.
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1205)..
<ID:0/004> File analysis..
<ID:0/004> skip file list for home binary
<ID:0/004> persist.img.ext4
<ID:0/004> Home Binary Download
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> FAIL! SHA256 is invalid
<OSM> All threads completed. (succeed 0 / failed 1)
Searched around for solutions but with no luck. Anyone kindly give some suggestions?
Odin is 3.12.4
T-Mobile firmware is N930TTMB1APGC_N930TTMB1APGC_TMO
AT&T firmware is N930AUCS1APH1_N930AATT1APH1_ATT_FULL
The verison I tried to flash back is AP_N930VVRS1APH1_CL8720001_QB10528330_REV00_user_low_ship_MULTI_CER
Also, I'm still in the 14 days return period. Anyone has an idea if they'll allow me to return the device after I flashed the AT&T firmware on it?
(went to a Verizon store asking for help but they told me "we don't flash things")
geeknerdlab said:
Got Black Note 7 from Verizon yesterday.
As we all know, V's firmware messed up with the original system quite a lot. So after a bit search, I decided to flash it to T-Mobile Firmware.
With Odin3, easily done. However, LTE not working, not cellular either, emergency call only. Then decided to flash to AT&T according to one of the threads(maybe link later).
After flashing to AT&T firmware, still no LTE, emergency call only.
When I tried to flash it back to Verizon, Odin3 stopped me from doing so and gives SHA256 error.
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1205)..
<ID:0/004> File analysis..
<ID:0/004> skip file list for home binary
<ID:0/004> persist.img.ext4
<ID:0/004> Home Binary Download
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> FAIL! SHA256 is invalid
<OSM> All threads completed. (succeed 0 / failed 1)
Searched around for solutions but with no luck. Anyone kindly give some suggestions?
Odin is 3.12.4
T-Mobile firmware is N930TTMB1APGC_N930TTMB1APGC_TMO
AT&T firmware is N930AUCS1APH1_N930AATT1APH1_ATT_FULL
The verison I tried to flash back is AP_N930VVRS1APH1_CL8720001_QB10528330_REV00_user_low_ship_MULTI_CER
Have you tried this modified Odin to flash back to Verizon?
https://drive.google.com/file/d/0B-bHEKYqWJXEZ3hRQnk3NEdMQjQ/view
Click to expand...
Click to collapse
coton said:
geeknerdlab said:
Got Black Note 7 from Verizon yesterday.
As we all know, V's firmware messed up with the original system quite a lot. So after a bit search, I decided to flash it to T-Mobile Firmware.
With Odin3, easily done. However, LTE not working, not cellular either, emergency call only. Then decided to flash to AT&T according to one of the threads(maybe link later).
After flashing to AT&T firmware, still no LTE, emergency call only.
When I tried to flash it back to Verizon, Odin3 stopped me from doing so and gives SHA256 error.
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1205)..
<ID:0/004> File analysis..
<ID:0/004> skip file list for home binary
<ID:0/004> persist.img.ext4
<ID:0/004> Home Binary Download
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> FAIL! SHA256 is invalid
<OSM> All threads completed. (succeed 0 / failed 1)
Searched around for solutions but with no luck. Anyone kindly give some suggestions?
Odin is 3.12.4
T-Mobile firmware is N930TTMB1APGC_N930TTMB1APGC_TMO
AT&T firmware is N930AUCS1APH1_N930AATT1APH1_ATT_FULL
The verison I tried to flash back is AP_N930VVRS1APH1_CL8720001_QB10528330_REV00_user_low_ship_MULTI_CER
Have you tried this modified Odin to flash back to Verizon?
Oh WOW! There we go!
Really Appreciate it!
Turns out I'm still amateur at Android sigh......
Click to expand...
Click to collapse
Click to expand...
Click to collapse
geeknerdlab said:
coton said:
geeknerdlab said:
Got Black Note 7 from Verizon yesterday.
As we all know, V's firmware messed up with the original system quite a lot. So after a bit search, I decided to flash it to T-Mobile Firmware.
With Odin3, easily done. However, LTE not working, not cellular either, emergency call only. Then decided to flash to AT&T according to one of the threads(maybe link later).
After flashing to AT&T firmware, still no LTE, emergency call only.
When I tried to flash it back to Verizon, Odin3 stopped me from doing so and gives SHA256 error.
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1205)..
<ID:0/004> File analysis..
<ID:0/004> skip file list for home binary
<ID:0/004> persist.img.ext4
<ID:0/004> Home Binary Download
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> FAIL! SHA256 is invalid
<OSM> All threads completed. (succeed 0 / failed 1)
Searched around for solutions but with no luck. Anyone kindly give some suggestions?
Odin is 3.12.4
T-Mobile firmware is N930TTMB1APGC_N930TTMB1APGC_TMO
AT&T firmware is N930AUCS1APH1_N930AATT1APH1_ATT_FULL
The verison I tried to flash back is AP_N930VVRS1APH1_CL8720001_QB10528330_REV00_user_low_ship_MULTI_CER
Have you tried this modified Odin to flash back to Verizon?
Oh WOW! There we go!
Really Appreciate it!
Turns out I'm still amateur at Android sigh......
Click to expand...
Click to collapse
Great news!
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Had this issue on the s7 edge when I was on the "u" firmware. Very similar except everything except texting worked. Had to use the princecomsey Odin(sha256 patched) to get back to at&t which I use for a daily driver
tjthecat said:
Had this issue on the s7 edge when I was on the "u" firmware. Very similar except everything except texting worked. Had to use the princecomsey Odin(sha256 patched) to get back to at&t which I use for a daily driver
Click to expand...
Click to collapse
I also flashed firmware on s7 edge but they worked all fine even from u to v. Odin sometimes feels tricky to work around.
We're your APN setting adjusted after you flashed from Verizon to the other roms?
geeknerdlab said:
Got Black Note 7 from Verizon yesterday.
As we all know, V's firmware messed up with the original system quite a lot. So after a bit search, I decided to flash it to T-Mobile Firmware.
With Odin3, easily done. However, LTE not working, not cellular either, emergency call only. Then decided to flash to AT&T according to one of the threads(maybe link later).
After flashing to AT&T firmware, still no LTE, emergency call only.
When I tried to flash it back to Verizon, Odin3 stopped me from doing so and gives SHA256 error.
<ID:0/004> Added!!
<ID:0/004> Odin engine v(ID:3.1205)..
<ID:0/004> File analysis..
<ID:0/004> skip file list for home binary
<ID:0/004> persist.img.ext4
<ID:0/004> Home Binary Download
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> FAIL! SHA256 is invalid
<OSM> All threads completed. (succeed 0 / failed 1)
Searched around for solutions but with no luck. Anyone kindly give some suggestions?
Odin is 3.12.4
T-Mobile firmware is N930TTMB1APGC_N930TTMB1APGC_TMO
AT&T firmware is N930AUCS1APH1_N930AATT1APH1_ATT_FULL
The verison I tried to flash back is AP_N930VVRS1APH1_CL8720001_QB10528330_REV00_user_low_ship_MULTI_CER
Also, I'm still in the 14 days return period. Anyone has an idea if they'll allow me to return the device after I flashed the AT&T firmware on it?
(went to a Verizon store asking for help but they told me "we don't flash things")
Click to expand...
Click to collapse
So at last did you successfully flash the tmobile firmware? I am wondering doing the same thing.
Hi can someone tell me if you where able to flash t mobile firmware on your verizon phone. I changed to t mobile but cant use wifi calling and voice over lte and cant get a definitive answer on if you can flash it. I Have a verizon phone rooted but would like to flash to t mobile and still use tmobiles root is that possible thanks