My verizon note 2 is stuck in the boot screen that shows SAMSUNG GALAXY NOTE II. It just keeps FLASHING every 2-3 seconds.
Odin keeps failing, Ive already done the root yesterday and installed a rom and than i got a samsung update and it downloaded and went into installing it which all went well. But when it restarted I got stuck as mentioned above.
Please advice me on what to do. I'm not new to odin and I have flashed the gn2 yesterday to original formware but today it just fails????
Please help with ideas. THANKS
How about a batttery pull. Then hold power home and up key and see if u have custom recovery and if so then do a restore of your back up. Or just flash another rom.
Sent from my SCH-I605 using xda premium
Sent from my SCH-I605 using xda premium
highwaybandit said:
How about a batttery pull. Then hold power home and up key and see if u have custom recovery and if so then do a restore of your back up. Or just flash another rom.
Sent from my SCH-I605 using xda premium
Sent from my SCH-I605 using xda premium
Click to expand...
Click to collapse
As i do that the logo keeps flashing every 2-3 seconds and nothing ever happens.
I this because of the logo words are flashing nothing works when I try to do the normal/usual restore tricks.
If the logo words would stay still/freeze in place I would be golden. But as they just keep flashing I cant do nothing.
This is one serious problem Im thinking. Anyone that gets me out of this is a GENIUS, PURE GENIUS!!
JasjarMan said:
My verizon note 2 is stuck in the boot screen that shows SAMSUNG GALAXY NOTE II. It just keeps FLASHING every 2-3 seconds.
Odin keeps failing, Ive already done the root yesterday and installed a rom and than i got a samsung update and it downloaded and went into installing it which all went well. But when it restarted I got stuck as mentioned above.
Please advice me on what to do. I'm not new to odin and I have flashed the gn2 yesterday to original formware but today it just fails????
Please help with ideas. THANKS
Click to expand...
Click to collapse
Can you boot into download mode (power, home, vol. down), then flash a new rom through your computer? I'd start with rom, then if that doesn't work try flash a new recovery.
AndroidSurman said:
Can you boot into download mode (power, home, vol. down), then flash a new rom through your computer? I'd start with rom, then if that doesn't work try flash a new recovery.
Click to expand...
Click to collapse
I can but like I mentioned odin fails. Heres what I get:
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
JasjarMan said:
I can but like I mentioned odin fails. How do I flash a RECOVERY?
Click to expand...
Click to collapse
Download a custom recovery zip from TWRP, If you used odin, just boot into download, and flash through odin.
Edit: I didn't realize odin was failing. Scratch that.
Three things we need more info about how Odin is failing, but I have a guess it says sboot then fails. So in that case go here
http://forum.xda-developers.com/showthread.php?p=35265728
Get the alternate restore and use that in Odin. Or you could try the pit file, some day that fixes them up. Second had you read at all or looked in the stickies you would have got that answer in 10 seconds. Third, and finally never post in development until you develop something. Especially when you're getting help here, that's spam and can get you banned, plus normally I and others will not help you for that.
Sent from my SGH-T889 using xda app-developers app
kintwofan said:
Three things we need more info about how Odin is failing, but I have a guess it says sboot then fails. So in that case go here
http://forum.xda-developers.com/showthread.php?p=35265728
Get the alternate restore and use that in Odin. Or you could try the pit file, some day that fixes them up. Second had you read at all or looked in the stickies you would have got that answer in 10 seconds. Third, and finally never post in development until you develop something. Especially when you're getting help here, that's spam and can get you banned, plus normally I and others will not help you for that.
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
- I tried the pit no go.
- who said I did not look at the stickies?Maybe I should have mentioned that I did.
I did do as what was said in that link the first day I but my phone and it DID work.
Now it does not work and thats why I was asking her for help.
- I cant believe posting here is SPAM but ok I should have know better.
- Glad I got help regardless, thanks to everyone.
But I still have the issue.
JasjarMan said:
- I tried the pit no go.
- who said I did not look at the stickies?Maybe I should have mentioned that I did.
I did do as what was said in that link the first day I but my phone and it DID work.
Now it does not work and thats why I was asking her for help.
- I cant believe posting here is SPAM but ok I should have know better.
- Glad I got help regardless, thanks to everyone.
But I still have the issue.
Click to expand...
Click to collapse
No posting the same question in multiple spots is spam. You still haven't said what Odin says when it fails. Saying it fails helps no one help you
Sent from my SGH-T889 using xda app-developers app
kintwofan said:
No posting the same question in multiple spots is spam. You still haven't said what Odin says when it fails. Saying it fails helps no one help you
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
post #5 I pasted this:
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
And this:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<ID:0/003> Added!!
<OSM> All threads completed. (succeed 0 / failed 1)
JasjarMan said:
And this:
Enter CS for MD5..
Check MD5.. Do not unplug the cable..
Please wait..
CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.tar.md5 is valid.
Checking MD5 finished Sucessfully..
Leave CS..
Odin v.3 engine (ID:3)..
File analysis..
SetupConnection..
Initialzation..
Get PIT for mapping..
Firmware update start..
boot.img
NAND Write Start!!
Complete(Write) operation failed.
Added!!
All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Much better, but it looks like you still didn't do what I said and you didn't read the stickies so...
Sent from my SGH-T889 using xda app-developers app
Try that out and see if it works, I'm going to bed so post your results
Sent from my SGH-T889 using xda app-developers app
kintwofan said:
Try that out and see if it works, I'm going to bed so post your results
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Will do. THANKS!
JasjarMan said:
Will do. THANKS!
Click to expand...
Click to collapse
So since you're not posting a bunch I'm assuming this fixed you? You can at least stop in to say it worked and thank the people who spent there time helping you
Sent from my SGH-T889 using xda app-developers app
Related
I installed CWM touch, and superuser zip folder on my Galaxy note (att)
So I read a tut that said to wipe everything so I did on recovery mode, booted it up, worked good, went back because superuser didnt work right. I installed 3-4 times before it said success, now its goes to a crisp samsung logo, then goes blurry and stops.....
Stupid noob mistake I didnt backup anything. Figured it was simple as jailbreaking an iphone (which you cant mess up on, plug in, hit button, done)
I been trying it all but just cant get it to work.
If your phone still boots up
youre not bricked...
Odin back to a stock firmware (GB or ICS)
and start again
jayRokk said:
If youre phone still boots up
youre not bricked...
Odin back to a stock firmware (GB or ICS)
and start again
Click to expand...
Click to collapse
+1.
And if you can't find how to do that, you need to read more before flashing
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
It boots to the samsung logo, but not lock screen. And I'm phoneless now Lol.
Since I was just updated to ICS (att) and did CWM/superuser, would I just have to use odin>PDA with a tar file?
if so which file? I tried that but no luck.
welchertc said:
+1.
And if you can't find how to do that, you need to read more before flashing
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
I been reading alot but seems like there is a hundred different explanations or ways to do it, and hard to find the right way?
liftedzuki said:
Since I was just updated to ICS (att) and did CWM/superuser, would I just have to use odin>PDA with a tar file?
if so which file? I tried that but no luck.
Click to expand...
Click to collapse
Yes its a .tar file
And search for it buddy there is a whole thread on official ICS and with it the CWM file and SU file to get you going
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
http://forum.xda-developers.com/showthread.php?t=1566976
Tried this tar, and it
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> FixRecovery.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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
liftedzuki said:
http://forum.xda-developers.com/showthread.php?t=1566976
Tried this tar, and it
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> FixRecovery.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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> zImage
<ID:0/005> NAND Write Start!!
<ID:0/005>
<ID:0/005> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
You need to stop flashing before you mess up your phone
Stop and read
Why are you flashing that?!?!?!
You have an NOTE
Really stop and read read read
I'm surprised you haven't bricked it yet
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
jayRokk said:
You need to stop flashing before you mess up your phone
Stop and read
Why are you flashing that?!?!?!
You have an NOTE
Really stop and read read read
I'm surprised you haven't bricked it yet
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2
Click to expand...
Click to collapse
:silly: I got it from a link in this note section, I should have seen that though.
So if I flash it, does it flash over the other flash? or does it add to it.
I'll continue readin.
Not all Samsung's are the same. You should only be getting tar files from your specific section. Keep in mind you need to match the model number
Sent from my SPH-L710 using Tapatalk 2
I would suggest going here and flashing one of these one clicks in Odin:
http://forum.xda-developers.com/showthread.php?t=1647756
Sent from my SPH-L710 using Tapatalk 2
And if I'm not mistaken you want the first link. I don't have a note so maybe someone here can chime in.
Sent from my SPH-L710 using Tapatalk 2
That link worked good. Thanks so much to everyone, I about had a heartache as I got my phone like 3 months ago, and just got ICS on it.
This time I'm gonna read alot more before I try it again.
Good idea. Glad it worked. If ya ever have any questions in the future , don't hesitate to ask BEFORE flashing.
Sent from my SPH-L710 using Tapatalk 2
Definitely not gonna be doing it til next weekend. I didnt plan on doing it today just was messin with my phone since galaxy S3 is out, and wanting to make my phone a little cooler, and did it before I had lots of research under my belt. :silly:
Haha it happens. Just be glad ya didn't end up with a huge note shaped paperweight
Sent from my SPH-L710 using Tapatalk 2
liftedzuki said:
Definitely not gonna be doing it til next weekend. I didnt plan on doing it today just was messin with my phone since galaxy S3 is out, and wanting to make my phone a little cooler, and did it before I had lots of research under my belt. :silly:
Click to expand...
Click to collapse
OP if your good to go, can you put Solved in your title....
thank you sir
Hello.
So, I will explain what i did first.
Last night, I was trying to root my note 2, using following link.
http://galaxynote2root.com/galaxy-note-2-root/how-to-root-verizon-galaxy-note-2-sch-i605/
(it was the first link from google search, stupid me...)
Anyway, after following instruction on that link, my phone got stuck in a boot loop. (ie. when i turn on, the samsung screen comes on, then verizon LTE and then back to samsung and so on.)
So, I tried to fix using following links
http://galaxynote2root.com/galaxy-n...ootunbrick-galaxy-note-2-with-stock-firmware/
http://forum.xda-developers.com/showthread.php?t=2272066&page=18
http://forums.androidcentral.com/ve...-do-i-restore-sboot-bin-causes-odin-fail.html
Samsung Kies
and still can't fix it.
Since you need more than these, here are some results from running odin, etc.
When I run odin with PDA file, I get following
<ID:0/008> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> CI605_I605VRLJB_I605VRALJB_CL414933_HWID04_HW-Rev0406_low_ship_user.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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!!
<ID:0/008> cache.img
<ID:0/008> hidden.img
<ID:0/008> modem.bin
<ID:0/008> param.bin
<ID:0/008> recovery.img
<ID:0/008> sboot.bin
<ID:0/008>
<ID:0/008> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
When I power up the machine, I get following message.
"Firmware upgrade encountered an issue. Please select recovery mode in Kies &try again"
However, when I connect with Kies, Kies won't recognize my phone, and cannot go into recovery.
When I try CASUAL to unbrick, CASUAL doesn't connect. Also, when I try the download mode (via double-clicking the "DISCONNECTED"), it still can't recognize.
On "My computer", I do not see the I drive (my phone), so I don't think it is connecting....?
I have tried deleting driver and installing and Zadig program as well.
Can anyone help me with going back to original condition?
I would really appreciate and more than willing to pay for your effort.
Please help me.
Let me know, if you need more results.
http://forum.xda-developers.com/showthread.php?p=39299305
Please read the stickies. There's your answer right at the top of this page. Also, I think you learned, but I highly recommend you stay with xda for guides. As you can see these sites just repost xda info and a lot if times it's incorrect or out of date and result in a brick.
Or you could have skimmed and saw where this was addressed just yesterday.
http://forum.xda-developers.com/showthread.php?p=37255435
Sent from my SGH-T889 using xda app-developers app
Did you include the pit file? That may be the problem. Also make sure you right click odin and run as administrator.
Sent from my SCH-I605 using Tapatalk 2
Lodingi it's not the pit. It's a locked bootloader and the op trying to write sboot.bin (which is blacklisted on the newer updates. That's why we use alternate restore because it doesn't contain sboot.bin so it will pass on Odin.
Edit to fix your name, sorry
Sent from my SGH-T889 using xda app-developers app
kintwofan said:
Lodingi it's not the pit. It's a locked bootloader and the op trying to write sboot.bin (which is blacklisted on the newer updates. That's why we use alternate restore because it doesn't contain sboot.bin so it will pass on Odin.
Edit to fix your name, sorry
Sent from my SGH-T889 using xda app-developers app
Click to expand...
Click to collapse
Gotcha. Thanks.
Sent from my SCH-I605 using Tapatalk 2
Lodingi said:
Gotcha. Thanks.
Sent from my SCH-I605 using Tapatalk 2
Click to expand...
Click to collapse
Ya man, i typed lodingo at first, I guess I edited it before you even saw.
Sent from my SGH-T889 using xda app-developers app
I'm interested in rooting my new Galaxy S4 but I also would like the original stock rom in case if I ever need to go back to it. Would anyone by any chance have the original stock ROM?
Model: SCH-I545
Android Version: 4.2.2
*If any other details are needed, let me know.
This is a Verizon phone fyi.
Also, could someone please link me to a tutorial/guide for rooting the S4 and some other links that have ROMs that are a "must-get".
Thanks,
Hydra
Read the development forums. The stock image is ready enough to find, as are step by step root instructions. As to your last question, that is the type of thing that gets a thread locked. Read the dev forums, pick a few roms that pique your interest, and give them a test drive.
Sent from my Nexus 7 using Tapatalk HD
najaboy said:
Read the development forums. The stock image is ready enough to find, as are step by step root instructions. As to your last question, that is the type of thing that gets a thread locked. Read the dev forums, pick a few roms that pique your interest, and give them a test drive.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
I'm new here so tried my best to find the correct section, and did search for guides.
I'm currently using this guide, http://forum.xda-developers.com/showthread.php?t=2290798 , but upon flashing the prerelease kernal, it failed.
http://i.imgur.com/MjbRPrK.png
Also, in case of anything, how can I leave ODIN mode on the phone? Do I just power it off and reboot?
CM10.1 has been treating me pretty well. Haven't had any crashes or anything and runs fast and stable.
The only issue I noticed is you can't get a GPS lock while Network & Wireless location is on. Once you disable it GPS locks right in.
Sent from my SCH-I545 using Tapatalk 2
I now have a huge problem. I'm at the screen: Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. Need to resolve this as soon as possible.
HydraS4 said:
I now have a huge problem. I'm at the screen: Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again. Need to resolve this as soon as possible.
Click to expand...
Click to collapse
Go to this guide and download the .tar image to be used in Odin http://forum.xda-developers.com/showthread.php?t=2301259. Boot into Odin mode following this guide http://forum.xda-developers.com/showthread.php?t=2290771. Follow all the instructions exactly and ask questions here if you have any.
Ryno77 said:
Go to this guide and download the .tar image to be used in Odin http://forum.xda-developers.com/showthread.php?t=2301259. Boot into Odin mode following this guide http://forum.xda-developers.com/showthread.php?t=2290771. Follow all the instructions exactly and ask questions here if you have any.
Click to expand...
Click to collapse
The tar file is 1.8 Gbs, is this the only method? I have horrible download speed and going to take 3 hours to download it.
Btw, can someone educate me on what just happened? Did I brick my phone? Will I lose any data?
Thanks,
Hydra
HydraS4 said:
The tar file is 1.8 Gbs, is this the only method? I have horrible download speed and going to take 3 hours to download it.
Btw, can someone educate me on what just happened? Did I brick my phone? Will I lose any data?
Thanks,
Hydra
Click to expand...
Click to collapse
Can you get into regular android recovery?
Ryno77 said:
Can you get into regular android recovery?
Click to expand...
Click to collapse
Nope, I'm working on trying Samsung Kies, maybe that will do it but I tried to get into recovery mode thru the phone but takes me to that same window.
I'm also downloading the stock firmware.
Did you try just flashing the stock kernel back using Odin? Everything you've done is listed in this thread, right? Technically if you tried to flash the pre release kernel and it failed nothing should have happened.
Ryno77 said:
Did you try just flashing the stock kernel back using Odin? Everything you've done is listed in this thread, right?
Click to expand...
Click to collapse
No, I haven't. Is that the one in the guide? If so, I'll do it soon. I have to go out, and now without a phone so going to be a problem for me.
Thanks for the quick support btw, appreciate it.
HydraS4 said:
No, I haven't. Is that the one in the guide? If so, I'll do it soon. I have to go out, and now without a phone so going to be a problem for me.
Thanks for the quick support btw, appreciate it.
Click to expand...
Click to collapse
I don't know if it will work but it's worth trying. The stock Odin should definitely fix your problem though. Yes it's in the thread.
Ryno77 said:
I don't know if it will work but it's worth trying. The stock Odin should definitely fix your problem though. Yes it's in the thread.
Click to expand...
Click to collapse
Code:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> SCH-I545_MDK_562219_Kernel.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
Is what I get upon flashing kernel to the stock kernel. I am downloading the stock ROM as I type this. 1 Hour left to download it. Btw, does it matter what type of ROM I download?
Is there a difference from, http://www.rwilco12.com/downloads.p...Galaxy S4 (Verizon) (SCH-I545)/Stock ROMs/TAR and http://forum.xda-developers.com/showthread.php?t=2301259 ?
I'm guessing it's the No Wipe feature?
And what's the worst case scenario with rooting the phone? Anything permanent? If this stock ROM fixes the current problem, then I'll attempt to root once more.
Thanks,
Hydra
Code:
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> VRUAMDK_NoWipe.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/003> Removed!!
<ID:0/003> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Added!!
What is the PIT partition? Is that my internal storage?
Are you using the factory charging cable to connect to the computer? I don't know why everything keeps failing.... Odin has never failed for me. Do you have another computer you can try this on? Stock charging cable, different usb port or another computer are the things I would try next. I don't know anything about pit files.
Sent from my SCH-I545 using xda premium
Ryno77 said:
Are you using the factory charging cable to connect to the computer? I don't know why everything keeps failing.... Odin has never failed for me. Do you have another computer you can try this on? Stock charging cable, different usb port or another computer are the things I would try next. I don't know anything about pit files.
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
Tried two types of cables, a generic one and factory/original one. I tried two different computers with 2 different OS. Tried 3 different ports per computer.
Don't know what else I can do.
Since you're able to boot into Odin mode I think this can be fixed but it may require a pit file. Since I know nothing about pit files or why Odin kept failing for you I'm going to let someone else try and help you. I do not think your phone is beyond hope at this point. Good luck.... I hope someone chimes in with the help you need.
Sent from my SCH-I545 using xda premium
Ryno77 said:
Since you're able to boot into Odin mode I think this can be fixed but it may require a pit file. Since I know nothing about pit files or why Odin kept failing for you I'm going to let someone else try and help you. I do not think your phone is beyond hope at this point. Good luck.... I hope someone chimes in with the help you need.
Sent from my SCH-I545 using xda premium
Click to expand...
Click to collapse
Alright, I appreciate all the help. Thanks!
Hopefully someone can help me out before I head over to Verizon later today.
HydraS4 said:
Alright, I appreciate all the help. Thanks!
Hopefully someone can help me out before I head over to Verizon later today.
Click to expand...
Click to collapse
Yeah, no problem. I'm sorry nothing worked for you.
Sent from my SCH-I545 using xda premium
Does anyone know if Verizon will replace it if it isn't my fault? There is no proof of rooting just a messed up system.
I just tried to root my MI1 phone using Odin and appropriate downloads.
On flashing, got failure as below:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> VRUDMI1_Root_de_la_vega_jfltevzw.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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> cache.img.ext4
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Tried 2 computers with USB 2 direct connection -> same result. Can't boot, only get to "Firmware upgrad encountered an issue. Please select recovery mode in Kies & try again."
yearn2burn said:
I just tried to root my MI1 phone using Odin and appropriate downloads.
On flashing, got failure as below:
<ID:0/005> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> VRUDMI1_Root_de_la_vega_jfltevzw.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> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> cache.img.ext4
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
Tried 2 computers with USB 2 direct connection -> same result. Can't boot, only get to "Firmware upgrad encountered an issue. Please select recovery mode in Kies & try again."
Click to expand...
Click to collapse
Which download did you try to flash first?
This postpost?
http://forum.xda-developers.com/showthread.php?p=41977487
Sent from my SCH-I545 using xda app-developers app
Mightycaptain said:
Which download did you try to flash first?
This postpost?
http://forum.xda-developers.com/showthread.php?p=41977487
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
rootdelavegajfltevzw
exact file in the zip is VRUDMI1_Root_de_la_vega_jfltevzw.tar.md5
You can see it in the log.
You know, it's my wife's phone. I was going to root it last night but waited. Maybe it updated from MI1 and I didn't check again. God I hope not. If that's the case, should it be fixable when the next root comes out??? Or could it be fixable now???
yearn2burn said:
rootdelavegajfltevzw
exact file in the zip is VRUDMI1_Root_de_la_vega_jfltevzw.tar.md5
You can see it in the log.
You know, it's my wife's phone. I was going to root it last night but waited. Maybe it updated from MI1 and I didn't check again. God I hope not. If that's the case, should it be fixable when the next root comes out??? Or could it be fixable now???
Click to expand...
Click to collapse
Go ahead and try the no wipe factory mi1 from the thread I posted.
If it fails you might have had a phone on mj7.
There is no data wipe for that as well. just a different thread in Android dev.
Is the phone soft bricked?
Sent from my SCH-I545 using xda app-developers app
Mightycaptain said:
Go ahead and try the no wipe factory mi1 from the thread I posted.
If it fails you might have had a phone on mj7.
There is no data wipe for that as well. just a different thread in Android dev.
Is the phone soft bricked?
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
It only will boot to the Odin mode. Trying a regular boot just gets to the error screen "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
yearn2burn said:
It only will boot to the Odin mode. Trying a regular boot just gets to the error screen "Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Click to expand...
Click to collapse
Okay. Try what I said before.
Sent from my SCH-I545 using xda app-developers app
Mightycaptain said:
Okay. Try what I said before.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
downloading MI1 now. I'll update...
yearn2burn said:
downloading MI1 now. I'll update...
Click to expand...
Click to collapse
Failed. Same error. Must have updated since yesterday???
Ughhh. Wife's gonna kill me!!!!
yearn2burn said:
Failed. Same error. Must have updated since yesterday???
Ughhh. Wife's gonna kill me!!!!
Click to expand...
Click to collapse
Any other suggestions? Just have to wait for the next version root?
yearn2burn said:
Any other suggestions? Just have to wait for the next version root?
Click to expand...
Click to collapse
I would download mj7 tar and flash in odin. Then just wait for a root method. It'll happen soon.
Sent from my SCH-I545 using xda app-developers app
stuckintheskull said:
I would download mj7 tar and flash in odin. Then just wait for a root method. It'll happen soon.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
There is a root method already out there, but some people suspect it has embedded malware, but it's not confirmed. A lot of people have used it without issue.
Crawshayi said:
There is a root method already out there, but some people suspect it has embedded malware, but it's not confirmed. A lot of people have used it without issue.
Click to expand...
Click to collapse
Yeah I've actually done it and it worked but kinda freaks me out a bit. Hopefully one of the devs around here can do it so it's trustworthy.
Sent from my SCH-I545 using xda app-developers app
stuckintheskull said:
Yeah I've actually done it and it worked but kinda freaks me out a bit. Hopefully one of the devs around here can do it so it's trustworthy.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
I don't trust it either. There are already devs working on pulling it apart to get to the bottom of it, so I'm sure we'll get an answer soon on the matter.
stuckintheskull said:
I would download mj7 tar and flash in odin. Then just wait for a root method. It'll happen soon.
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Link to the tar file? Hopefully would flash in Odin as PDA flash to save data?
Sent from my HTC6435LVW using Tapatalk
yearn2burn said:
Link to the tar file? Hopefully would flash in Odin as PDA flash to save data?
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=47010231
Sent from my SCH-I545 using xda app-developers app
Mightycaptain said:
http://forum.xda-developers.com/showthread.php?p=47010231
Sent from my SCH-I545 using xda app-developers app
Click to expand...
Click to collapse
Thanks. I'll flash it tonight. Confirmed with wife after due ear full that her phone updated just before she gave it over to me last night...
Sent from my HTC6435LVW using Tapatalk
Please read forum rules before posting
Questions and help issues go in the Q&A and Help section
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
Back up and running with no data loss! Thanks so mucho!
Sent from my HTC6435LVW using Tapatalk
yearn2burn said:
Thanks. I'll flash it tonight. Confirmed with wife after due ear full that her phone updated just before she gave it over to me last night...
Sent from my HTC6435LVW using Tapatalk
Click to expand...
Click to collapse
this is why you always check BEFORE attempting root, no matter what even if someone tells me they didn't update their phone or their phone is running blah blah, i always double check because you can never be too safe
Crawshayi said:
There is a root method already out there, but some people suspect it has embedded malware, but it's not confirmed. A lot of people have used it without issue.
Click to expand...
Click to collapse
Is this a method separate from the one allowing you to maintain root through the MJ7 update? Is it allowing people to root after taking the update without root?
Hi everyone. I've been meaning to sell my old S4 for awhile now and I haven't been keeping up with the root scene, so clearly I might have screwed something up. I was originally running my S4 rooted with Hyperdrive S15 (Android 4.3) with TWRP + Safestrap 3.71. I deleted the hyperdrive slot and booted into the stock ROM. After that, I used TWRP to wipe everything (dalvik cache/cache/data/factory reset) then after rebooting the phone, it just stays loads up the "Samsung" Screen with the custom symbol under it. I've tried looking at guides online to try to unbrick/fix this phone, but still have no idea what to do. I've tried booting it into download mode, but for some reason, it only goes into recovery mode (I do Vol Up + Home + Power, then as soon as it vibrates, I don't press the power button anymore). I was trying to use Odin but I can't get it to go into download mode, so when I plug it in, Odin doesn't see it. Can anyone give me some ideas/info on how to fix this?
EDIT: Here are the things I have tried doing:
1. I have used both Odin v1.85 and 3.09 to try and flash the VRUEMK2 firmware and the absolute newest firmware (4.4.2 NK2). Here's the log:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUFNK1_I545VZWFNK1_I545VRUFNK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> modem.bin
<ID:0/003> NON-HLOS.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Fails on both old and new Odins.....hmmmm...
2. Kies 2.6 and Kies 3 do not seem to be able to find the device when I load them.
Download mode is Power + Vol Down + Home. Press and hold all 3 until you see a warning on phones screen. Once you are at warning screen simply press Vol up once. If this doesn't work you may have to get a download mode jig. I had to buy one for my old S2, they can be found on ebay pretty cheap so you know.
Hope this helps!
Sent from my A0001 using XDA Free mobile app
Klown80 said:
Download mode is Power + Vol Down + Home. Press and hold all 3 until you see a warning on phones screen. Once you are at warning screen simply press Vol up once. If this doesn't work you may have to get a download mode jig. I had to buy one for my old S2, they can be found on ebay pretty cheap so you know.
Hope this helps!
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Wow I feel dumb now....thanks! It's in download mode now. I'll try to do the rest from here!
Hmmm..how long does it normally take for Odin to do it's thing? I'm following this guide:
http://www.androidrootz.com/2013/06/how-to-unroot-unbrick-galaxy-s4.html
It's been in the "downloading" screen for quite awhile.
EDIT: It says "failed". Hmmm. Figured I should have paid attention to when the article was written. I was previously on VRUEMK2 so I'm going to try this guide:
http://forum.xda-developers.com/showthread.php?t=2578209
Would these be the correct files?
ma70ent said:
Hmmm..how long does it normally take for Odin to do it's thing? I'm following this guide:
http://www.androidrootz.com/2013/06/how-to-unroot-unbrick-galaxy-s4.html
It's been in the "downloading" screen for quite awhile.
EDIT: It says "failed". Hmmm.
Click to expand...
Click to collapse
Sent from my A0001 using XDA Free mobile app
Looking at that link it shows 4.2.2 firmware for your VZW S4, going by your first post you were on a stock based 4.3 rom since you are using safestrap recovery. If that is correct then your issue is that you need a 4.3 or higher firmware, Samsung made it so you cannot downgrade most firmwares now. If I remember correctly, xda doesn't want us posting links to Samsung Web pages so please Google "sammobile" this will pull up Samsung mobile firmware download page as first result. Click on that link and then enter you model number in search box in top right of page. Enter model number and hit enter. This will pull up a list of firmwares for your model, make sure you choose 4.3 or higher firmware (4.3, 4.4, 4.4.2, or 4.4.4) and download it. Once downloaded please try Odin again.
You will have to make an acct on Samsung site to download firmware but it only takes a few mins and it's free.
Hope this helps, good luck!
Sent from my A0001 using XDA Free mobile app
Klown80 said:
Sent from my A0001 using XDA Free mobile app
Looking at that link it shows 4.2.2 firmware for your VZW S4, going by your first post you were on a stock based 4.3 rom since you are using safestrap recovery. If that is correct then your issue is that you need a 4.3 or higher firmware, Samsung made it so you cannot downgrade most firmwares now. If I remember correctly, xda doesn't want us posting links to Samsung Web pages so please Google "sammobile" this will pull up Samsung mobile firmware download page as first result. Click on that link and then enter you model number in search box in top right of page. Enter model number and hit enter. This will pull up a list of firmwares for your model, make sure you choose 4.3 or higher firmware (4.3, 4.4, 4.4.2, or 4.4.4) and download it. Once downloaded please try Odin again.
You will have to make an acct on Samsung site to download firmware but it only takes a few mins and it's free.
Hope this helps, good luck!
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Went to sammobile, registered, and downloaded the VRUEMK2 firmware (android 4.3). I tried using Odin 3.09 for this and it failed again. Should I try to flash 4.4 firmware on it? I'm only selecting the "AP" option. Should I use any other options other than f.reset, auto reboot, and AP?
Also, when I try to turn it on normally or even try recovery mode (vol up + home + power) it says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
ma70ent said:
Went to sammobile, registered, and downloaded the VRUEMK2 firmware (android 4.3). I tried using Odin 3.09 for this and it failed again. Should I try to flash 4.4 firmware on it? I'm only selecting the "AP" option. Should I use any other options other than f.reset, auto reboot, and AP?
Also, when I try to turn it on normally or even try recovery mode (vol up + home + power) it says "Firmware upgrade encountered an issue. Please select recovery mode in Kies and try again"
Click to expand...
Click to collapse
You could try the 4.4, or you could just download Kies and see if it will restore it for you. Yes you are using correct space (AP) and right things checked. Another though would be to try a lower version of Odin and use the PDA slot to flash it, I vaguely remember someone having trouble on here using newest version to restore phone, he had to use older version.
Sent from my A0001 using XDA Free mobile app
Klown80 said:
You could try the 4.4, or you could just download Kies and see if it will restore it for you. Yes you are using correct space (AP) and right things checked. Another though would be to try a lower version of Odin and use the PDA slot to flash it, I vaguely remember someone having trouble on here using newest version to restore phone, he had to use older version.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Yup. Tried Kies 3 and it says device wasn't compatible, but Kies 2.6 seems to be "Connecting" forever. I'll just wait until my 4.4 firmware finishes downloading and I'll try both the new Odin and the old Odin.
Klown80 said:
You could try the 4.4, or you could just download Kies and see if it will restore it for you. Yes you are using correct space (AP) and right things checked. Another though would be to try a lower version of Odin and use the PDA slot to flash it, I vaguely remember someone having trouble on here using newest version to restore phone, he had to use older version.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Okay I just went at it again. Quick question, if Odin runs through but fails right at the end (literally write as the thing is almost over, it says "Complete Write Operation Failed"), should I just keep trying?
ma70ent said:
Okay I just went at it again. Quick question, if Odin runs through but fails right at the end (literally write as the thing is almost over, it says "Complete Write Operation Failed"), should I just keep trying?
Click to expand...
Click to collapse
What part is it failing on, system? That is strange that it's still failing since you are trying to flash the newest firmware available for your device. You can try it again but if it failed once it will most likely keep failing. You might want to check md5 sums on the downloads to be sure your not getting a corrupt download.
Sent from my A0001 using XDA Free mobile app
Klown80 said:
What part is it failing on, system? That is strange that it's still failing since you are trying to flash the newest firmware available for your device. You can try it again but if it failed once it will most likely keep failing. You might want to check md5 sums on the downloads to be sure your not getting a corrupt download.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Here's the log:
<ID:0/003> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I545VRUFNK1_I545VZWFNK1_I545VRUFNK1_HOME.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<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> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl2.mbn
<ID:0/003> sbl3.mbn
<ID:0/003> rpm.mbn
<ID:0/003> tz.mbn
<ID:0/003> boot.img
<ID:0/003> recovery.img
<ID:0/003> system.img.ext4
<ID:0/003> cache.img.ext4
<ID:0/003> hidden.img.ext4
<ID:0/003> modem.bin
<ID:0/003> NON-HLOS.bin
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Fails on both Odins.....hmmmm...
Klown80 said:
What part is it failing on, system? That is strange that it's still failing since you are trying to flash the newest firmware available for your device. You can try it again but if it failed once it will most likely keep failing. You might want to check md5 sums on the downloads to be sure your not getting a corrupt download.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Alright. Actually, I did a lot of online searching and actually switched the usb port that I was using. After switching USB ports, I tried Odin again, flashed it, and it actually worked. Wow.
Anyways, I've thanked all of your posts, and of course, I thank you for spending the entire day with my problem.
ma70ent said:
Alright. Actually, I did a lot of online searching and actually switched the usb port that I was using. After switching USB ports, I tried Odin again, flashed it, and it actually worked. Wow.
Anyways, I've thanked all of your posts, and of course, I thank you for spending the entire day with my problem.
Click to expand...
Click to collapse
Sweet! Glad to hear you got it fixed! That was going to be my next suggestion. We're you by chance using a USB3 port? (it is blue if you look inside the USB port if it's usb3). For some reason most Android programming needs USB2 ports as they don't play very well with USB3.
Either way, Congratz on fixing your device, I may have given you a few pointers or helpful hints but you fixed it all on your own!
Sent from my SGH-I337 using XDA Free mobile app
Klown80 said:
Sweet! Glad to hear you got it fixed! That was going to be my next suggestion. We're you by chance using a USB3 port? (it is blue if you look inside the USB port if it's usb3). For some reason most Android programming needs USB2 ports as they don't play very well with USB3.
Either way, Congratz on fixing your device, I may have given you a few pointers or helpful hints but you fixed it all on your own!
Sent from my SGH-I337 using XDA Free mobile app
Click to expand...
Click to collapse
Actually my desktop has usb ports in the front (which aren't a direct connection to the mobo as far as I know) and of course, there are the normal usb ports in the back of it. I switched from the front one to the back one and all was well.
ma70ent said:
Actually my desktop has usb ports in the front (which aren't a direct connection to the mobo as far as I know) and of course, there are the normal usb ports in the back of it. I switched from the front one to the back one and all was well.
Click to expand...
Click to collapse
Yep it is usually best to connect directly to mobo instead any type of a USB hub, Android doesn't play very nice with those either!
Sent from my SGH-I337 using XDA Free mobile app
Klown80 said:
Yep it is usually best to connect directly to mobo instead any type of a USB hub, Android doesn't play very nice with those either!
Sent from my SGH-I337 using XDA Free mobile app
Click to expand...
Click to collapse
Hopefully this thread will help those in the future who make the same dumb mistakes I have. Haha...