Hello, I have a bricked SCH-i925 Verizon. I'm trying to update the rom from odin. It uploaded the file to the device, but what keeps happening is when it gets to write nand it fails. I'm doing it from the odin menu (power+vol down). What might I try to get it to work? I'm using win7 and odin 3.07. I go the majority of them and tried them all, but all do the same. I'm flashing I925VRAMK1_I925VZWAMK1.
tauntt said:
Hello, I have a bricked SCH-i925 Verizon. I'm trying to update the rom from odin. It uploaded the file to the device, but what keeps happening is when it gets to write nand it fails. I'm doing it from the odin menu (power+vol down). What might I try to get it to work? I'm using win7 and odin 3.07. I go the majority of them and tried them all, but all do the same. I'm flashing I925VRAMK1_I925VZWAMK1.
Click to expand...
Click to collapse
Were you able to return the tablet to its original state?
Ura535 said:
Were you able to return the tablet to its original state?
Click to expand...
Click to collapse
Nope she's bricked. Even with the stock rom Odin fails to flash. I think it's the locked bootloader that's why it won't work. Verizon is a useless company.
Related
I was trying to flash my s3 back to 4.1.1. It failed when I was using odin. Now, I get the message Firmware encountered an issue..
I downloaded kies 3 but my phone will not connect to it.
Iv tried many different things and odin keeps failing after a couple lines.
What can I do?
b_rad_1983 said:
I was trying to flash my s3 back to 4.1.1. It failed when I was using odin. Now, I get the message Firmware encountered an issue..
I downloaded kies 3 but my phone will not connect to it.
Iv tried many different things and odin keeps failing after a couple lines.
What can I do?
Click to expand...
Click to collapse
Does your phone still boot? or do you have a Brick?
If it still boots Leave it alone. you can flash any rom you want to as long as there is no bootloader in it.
If you already bricked it, is it a soft brick or hard brick?
theramsey3 said:
Does your phone still boot? or do you have a Brick?
If it still boots Leave it alone. you can flash any rom you want to as long as there is no bootloader in it.
If you already bricked it, is it a soft brick or hard brick?
Click to expand...
Click to collapse
When I insert the battery and power on it has a message saying " firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
above that in the top left it says
odin mode
product name :sgh-1747m
custom binary download: yes (1count)
current binary: samsung official
system status: official
qualcomm secure boot: enable
warranty bit: 0
bootloader rp swrev: 1
This is all it does. I can get into download mode. But everytime I try to flash it says failed.
This is 4.3 touchwiz? or 4.3 custom rom?
If custom, I encountered a similar issue where going back to Odin failed. Trying to turn on the phone and going into recovery mode let "Firmware encountered and issue". I had also encountered the problem of Kies not connecting. It would say "connecting" but nothing would happen.
Can your phone boot in download mode?
If yes, you should be able to recover the firmware with Kies.
You may need to use the previous version of Kies and not Kies 3, as I think Kies 3 is only for 4.3 android touchwiz versions. If you had touchwiz 4.3 from the OTA, you may be stuck as I think people have had problems trying to go back to 4.1.
In Kies go in Firmware Upgrade and Initialisation. You will need to know your phone's model and serial number. They can be found behind the battery.
Follow the steps and you should be able to go back to 4.1.1.
chemicalseb said:
This is 4.3 touchwiz? or 4.3 custom rom?
If custom, I encountered a similar issue where going back to Odin failed. Trying to turn on the phone and going into recovery mode let "Firmware encountered and issue". I had also encountered the problem of Kies not connecting. It would say "connecting" but nothing would happen.
Can your phone boot in download mode?
If yes, you should be able to recover the firmware with Kies.
You may need to use the previous version of Kies and not Kies 3, as I think Kies 3 is only for 4.3 android touchwiz versions. If you had touchwiz 4.3 from the OTA, you may be stuck as I think people have had problems trying to go back to 4.1.
In Kies go in Firmware Upgrade and Initialisation. You will need to know your phone's model and serial number. They can be found behind the battery.
Follow the steps and you should be able to go back to 4.1.1.
Click to expand...
Click to collapse
Its 4.3 touchwiz ota last week.
I will try kies instead of kies 3. With kies 3 it just says connecting, wont connect. When I do the Firmware Upgrade and Initialisation. I type in my model and it just closes.
Im downloading kies right now...
Oh also, I had encountered the closing problem when in Windows.
I was able to not have the random closing problem when using Kies on a Mac.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
b_rad_1983 said:
Its 4.3 touchwiz ota last week.
I will try kies instead of kies 3. With kies 3 it just says connecting, wont connect. When I do the Firmware Upgrade and Initialisation. I type in my model and it just closes.
Im downloading kies right now...
Click to expand...
Click to collapse
Kies has be installed and when I click on tools- Firmware Upgrade...
I type in the model and it says "Please check the model name and enter it". I click ok and it goes back to the main screen, nothing happens.
when i open kies and plug in the phone it says "connecting".... 5mins has passed..same thing..
Hm, yeah it's odd.
I had the same issue with the main screen saying connecting forever, which didn't matter for upgrading the firmware.
Do you have the att version?
I'm assuming you put SGH-I747 for model?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
My fix
I'm not an expert but I had the same problem due to the 4.3 release. You can't go back to an earlier release because the new boot loader is
locked. Nothing worked until I googled and located the exact .pit file and flashed it in Odin. I was rather desperate by then as I had a two day old
phone, lol. Kies doesn't have the newer release so I don't think you can use it. I used cwm mod recovery and flashed to a rooted stock 4.3 rom.
Hope this helps or someone can help more.
chemicalseb said:
Hm, yeah it's odd.
I had the same issue with the main screen saying connecting forever, which didn't matter for upgrading the firmware.
Do you have the att version?
I'm assuming you put SGH-I747 for model?
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Rogers
SGH-I747M
Im currently looking for the stock 4.3 rogers file
I cant find what I need as im not 100% sure what im looking for..
im currently downloading
SGH-I747M_RWC_I747MVLDMF1_I747MOYADMF1_Original.zip
b_rad_1983 said:
I cant find what I need as im not 100% sure what im looking for..
im currently downloading
SGH-I747M_RWC_I747MVLDMF1_I747MOYADMF1_Original.zip
Click to expand...
Click to collapse
I reached the download limit..cant download it
Which Odin are you using? If you arent using it try Odin 3.09.
theramsey3 said:
Which Odin are you using? If you arent using it try Odin 3.09.
Click to expand...
Click to collapse
3.07 is what i used.
b_rad_1983 said:
3.07 is what i used.
Click to expand...
Click to collapse
I just thought about it you have to go back with the 4.3 because if you do succesfully flash anything older you will Hard brick your phone, right now you should be able to recover with the 4.3 odin file.
theramsey3 said:
I just thought about it you have to go back with the 4.3 because if you do succesfully flash anything older you will Hard brick your phone, right now you should be able to recover with the 4.3 odin file.
Click to expand...
Click to collapse
Where can i get the 4.3 odin file?
Check sammobile.com
b_rad_1983 said:
Where can i get the 4.3 odin file?
Click to expand...
Click to collapse
http://www.sammobile.com/firmwares/
You have to register for their site to be able to download. in the search bar about 1/3 page down on right type in SGH-I747M then find your carrier and download the appropriate file.
After that if you still dont like 4.3 you can flash whatever rom you want in CWM or TWRP or atleast thats whats been rumored. I have no clue I like 4.3 and havent had any issues with the rom I had a hard brick that I caused and recovered.
So I just Odin Stock 4.3 and then I applied the update.zip to get it to 4.4.2. After that I tried flashing a ROM and eventually I just stupidly wiped my phone and I have no firmware on it. I went to Odin to get it back to stock 4.3 but due to Knox, I was not able to and now I'm stuck on the "Connect to kies" message. What do I do? I'm at loss here ;(. Please help. And the phone is not showing up on Odin...do I wait for Samsung to release a 4.4.2 tar?
nivekx9 said:
So I just Odin Stock 4.3 and then I applied the update.zip to get it to 4.4.2. After that I tried flashing a ROM and eventually I just stupidly wiped my phone and I have no firmware on it. I went to Odin to get it back to stock 4.3 but due to Knox, I was not able to and now I'm stuck on the "Connect to kies" message. What do I do? I'm at loss here ;(. Please help. And the phone is not showing up on Odin...do I wait for Samsung to release a 4.4.2 tar?
Click to expand...
Click to collapse
Do you have custom recovery installed?
If so just put any ROM on your SD Card, and flash that in recovery. The phone will boot right up and will be working again. From there you can do whatever you want.
Skipjacks said:
Do you have custom recovery installed?
If so just put any ROM on your SD Card, and flash that in recovery. The phone will boot right up and will be working again. From there you can do whatever you want.
Click to expand...
Click to collapse
Nope, otherwise I wouldn't be here . Stuck on that "Connect to Kies" message :/
I am trying to unroot and restore stock ROM so that I can sell my Note 2014 10.1.
I am using ODIN 3.09 and P600UEUCNK1_P600XARCNK1_HOME.tar.md5
ODIN keeps giving me a FAIL. Looks like "Cant Open Serial Port". I have attached a screen shot from ODIN.
Any ideas as to what I can do here?
Thanks
You need to extract the zip file, and edit .md5 off the end, leaving a .tar file to flash. Make sure you unroot via superuser, then factory reset, then download mode.....Will take 7-9 minutes. Wait for reboot, and removed to show in ODIN. Just did this myself, and device shows official, and recovery is stock, without even the Knox splash showing recovery bit! Easy breezy. I flashed on top of 4.4.4 bootloader the 4.4.2 .tar, and let it update OTA. T-Mobile P607-T Gluck!
Worked like a charm my friend...Thanks so much
Sent from my SM-N900P using Tapatalk
I followed these steps. Flashed same tar file, and successful install. Although i cant update software because says my version has been modified. Anyway to still get updates and be totally stock?
Flash updates from Kies instead OTA is never going to work again.
Sent from my SM-P600 using XDA Free mobile app
Please could anyone had the steps ... the same issue is faced with Note 10.1 Gt-8000
I' m using N8000XXUDNF2_N8000OJVDNF3_N8000XXUDNF1_HOME.tar with ODIN 3.07 which is detecting the com 3 or com 6 with it, and failing always and the device is stopped at either ODIN MODE if I used the volume down plus power or at Firmware upgrade encountered an issue. please select recovery mode in kies and try again... it would never enter to the recovery mode or Bootloader, please advise... thanks in advanced.
Having trouble getting stock ROM back on tab pro 8.4.
Flashing newest firmware keeps failing using twrp.
So I read that I need Odin. But what Odin version do I need to flash newest firmware.
Also not sure how to do it.
Is there any new how tos to do it?
I'm keeping twrp and going to reroot
cloud71 said:
Having trouble getting stock ROM back on tab pro 8.4.
Flashing newest firmware keeps failing using twrp.
So I read that I need Odin. But what Odin version do I need to flash newest firmware.
Also not sure how to do it.
Is there any new how tos to do it?
I'm keeping twrp and going to reroot
Click to expand...
Click to collapse
I Am using odin v3.0.7 and it works fine. Flashed latest firmware ANB6.
Open odin
Click PDA, then select your file to be flashed.
Wait for confirmation
Reboot your device to download mode (power button + volume down)
Press volume up to continue
Connect your device to PC ( you should see that your device was "added" in odin)
Then click start.
(Sorry for bad english)
Will this remove custom recovery as well? Im trying to keep that
cloud71 said:
Will this remove custom recovery as well? Im trying to keep that
Click to expand...
Click to collapse
Yes, also it will unroot your device if it is rooted.
OK well got tab back to stock and rooted again.
I loved having a custom rom but battery life was horrible , now with stock I'm back to 3 or 4 days of battery life . Which is awesome.
i've samsung note 4 sm-n910p
was working fine ,tried to install firmware but got bricked
i've tried downloading many firmwares all fail
need someone to send the right firmware for my device
attached the error i get
thanks
And here we go again...... What version software was installed before trying to update? Were you rooted?
zjor2000 said:
i've samsung note 4 sm-n910p
was working fine ,tried to install firmware but got bricked
i've tried downloading many firmwares all fail
thanks
Click to expand...
Click to collapse
Try Flashing CF Auto Root through Odin and reboot your phone and report back please.
w7excursion said:
And here we go again...... What version software was installed before trying to update? Were you rooted?
Click to expand...
Click to collapse
Lol, ikr....
done so ,,but nothing keeps restarting ,,,,loop
it needs a new firmware .. OS
zjor2000 said:
done so ,,but nothing keeps restarting ,,,,loop
it needs a new firmware .. OS
Click to expand...
Click to collapse
Were you on the OG5 OTA and tried to root your phone?
rooted thru odin
now i can't get to OS ,just show samsung sign and loops
Flash whatever firmware u was on in odin
zjor2000 said:
rooted thru odin
now i can't get to OS ,just show samsung sign and loops
Click to expand...
Click to collapse
In Odin, Flash the TWRP recovery
Download notarized,cm12 or sacs and put it on your SD card, and reboot to recovery and install your choice of Rom downloaded.
Reboot and relax.
tried to do thru sd card ,but i get :
dm-verity verification failed
can i just go back to 5.1 lollipop with an official stock rom via odin ?
zjor2000 said:
can i just go back to 5.1 lollipop with an official stock rom via odin ?
Click to expand...
Click to collapse
There is no official rom
any firmware can get me back to lollipop with odin !!!
zjor2000 said:
any firmware can get me back to lollipop with odin !!!
Click to expand...
Click to collapse
Here's what I understand as far as recovering with Odin by build:
All these builds NIE, NK2 (KitKat) and first Lollipop (OB7) were downgradeable; you were free to flash in Odin within these builds. Or KIES but not downgrade.
OE1 didn't have a tar, it also locked out the older ones but was compatible with OF5 to flash Odin or KIES to upgrade. Can only go back to OE1 with nandroid backup from OF5. OE1 introduced reactivation lock to prevent flashing over user locked phone as well as preventing the downgrade to escape the feature. Seems dine could recover from a bit loop by flashing CF Auto Root in Odin.
OF5 was released with a supporting tar eventually but it's the same story as OE1. But I'm not sure if CF Auto Root worked to recover boot when looped.
OG5 locks it further. If you don't have a nandroid, recovering from boot loop options may include flashing CWM recovery or a compatible flash that takes you away from OG5 almost entirely. Sacs, Notarized, and CM12 are reportedly working. Reportedly, can't go back to OF5 with Odin and not sure about nandroid, maybe not.
Depending on certain exceptions unclear, Odin and KIES have been reported to work together, flashing stock OB7 ROM, parts of stock tar with Odin with a flash result that won't boot but connecting KIES in recovery and using the emergency recovery method. If KIES doesn't see your phone on recovery, you may try this fix on your Windows PC:
http://forum.xda-developers.com/showpost.php?p=34864154&postcount=14
I'll add this too: flashing L Speed Mod may fix adb with ADB Insecure in booted mode; ADB Insecure wouldn't be needed in recovery anyway so it works without it. I can report this does work for me with the above MTP fix on OB7.
Sent from my SM-N910P using Tapatalk
samep said:
Here's what I understand as far as recovering with Odin by build:
All these builds NIE, NK2 (KitKat) and first Lollipop (OB7) were downgradeable; you were free to flash in Odin within these builds. Or KIES but not downgrade.
OE1 didn't have a tar, it also locked out the older ones but was compatible with OF5 to flash Odin or KIES to upgrade. Can only go back to OE1 with nandroid backup from OF5. OE1 introduced reactivation lock to prevent flashing over user locked phone as well as preventing the downgrade to escape the feature. Seems dine could recover from a bit loop by flashing CF Auto Root in Odin.
OF5 was released with a supporting tar eventually but it's the same story as OE1. But I'm not sure if CF Auto Root worked to recover boot when looped.
OF5 locks it further. If you don't have a nandroid, recovering from boot loop options may include flashing CWM recovery or a compatible flash that takes you away from OG5 almost entirely. Sacs, Notarized, and CM12 are reportedly working. Reportedly, can't go back to OF5 with Odin and not sure about nandroid, maybe not.
Depending on certain exceptions unclear, Odin and KIES have been reported to work together, flashing parts of stock tar with Odin and connecting KIES using the emergency recovery method. If KIES doesn't see your phone on recovery, you may try this fix on your Windows PC:
http://forum.xda-developers.com/showpost.php?p=34864154&postcount=14
I'll add this too: flashing L Speed Mod may fix adb with ADB Insecure in booted mode; ADB Insecure wouldn't be needed in recovery anyway so it works without it. I can report this does work for me with the above MTP fix on OB7.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Was i incorrect in my method of getting him back on his feet? I should suggest CWM instead of TWRP? Now im confused.
The last thing i want to do is tell someone the wrong procedure, only causing more frustration. I thought i read 'Twrp, Install and Viola!' from many users in the other thread.
xxSTARBUCKSxx said:
Was i incorrect in my method of getting him back on his feet? I should suggest CWM instead of TWRP? Now im confused.
The last thing i want to do is tell someone the wrong procedure, only causing more frustration. I thought i read 'Twrp, Install and Viola!' from many users in the other thread.
Click to expand...
Click to collapse
I think your suggestion is consistent with what we're learning as you gave it. It seems to be evolving with trial and error. The CWM suggestion came from a single experience shared.
http://forum.xda-developers.com/showthread.php?p=62196189
The OP was asking for another solution and it wasn't clear where he started from to correctly recovery so tried to answer including all the options for each build. I added some things that may help depending on his situation.
Sent from my SM-N910P using Tapatalk
i managed to find the right fW ,,,if anyone has same problem u can do it your self
https://1fichier.com/dir/IOjXgJUa
and download this file : N910PVPU3BOF5_SPT3BOF5_SPR_Sprint_USA_5.0.1.zip