Related
I tried rooting my phone, but when I flashed CWM my Nexus S stopped booting... it freezes on the Google screen in the intro. I can boot into Fastboot, and cwm, but I cant connect the Internal memory to the computer without it booting like it is supposed to. Does anybody know of anything I can do to fix my phone and bring it back to stock??
There are guides for returning to stock stickied in the Nexus S 4G Android Development forum.
Before you do that though, try flashing a different recovery, like the one linked to here or here.
Btw, which guide did you use? You're not the first person to have this problem, and it's really bugging me (though probably not as much as it's bugging you :-o).
Maximilian Mary: I tried to post the link, but since I'm a new member I have to wait 8 posts before I can post a URL.... :/
I will try a different recovery, but how would I flash a rom if I can connect my phone via usb mount?
deadzunehd said:
Maximilian Mary: I tried to post the link, but since I'm a new member I have to wait 8 posts before I can post a URL.... :/
Click to expand...
Click to collapse
What's the title of the thread?
.
I will try a different recovery, but how would I flash a rom if I can connect my phone via usb mount?
Click to expand...
Click to collapse
I'm a little out of my depth here, but I think it's
fastboot flash system system.img.
You don't need to put the rom image on the sdcard. Just put it in the same folder as fastboot.
It was titled "How to Root Nexus S!"
And I will try to flash recovery and try that rom command, thank you )
deadzunehd said:
It was titled "How to Root Nexus S!"
And I will try to flash recovery and try that rom command, thank you )
Click to expand...
Click to collapse
Hmmm. I can't find that exact title. Could you pm me the link?
deadzunehd said:
thank you )
Click to expand...
Click to collapse
There's a button for that.
I got the link. Thanks. I looks like you flashed a boot image that is incompatible with your phone. That guide was for the T-Mobile Nexus S. (Why they're screwing with the boot.img to begin with, I really don't understand.)
Download the attached file, and unzip it to the same folder as fastboot. The md5 sum is d4a9508f9321eb25df3383f00f571e8b. Then
Code:
fastboot flash boot boot.img
You'll probably also want to use one of the recoveries listed above to
Code:
fastboot flash recovery recovery.img
, but leave system alone for now. Flash that only as a last resort.
deadzunehd said:
I tried rooting my phone, but when I flashed CWM my Nexus S stopped booting... it freezes on the Google screen in the intro. I can boot into Fastboot, and cwm, but I cant connect the Internal memory to the computer without it booting like it is supposed to. Does anybody know of anything I can do to fix my phone and bring it back to stock??
Click to expand...
Click to collapse
I had this problem after flashing the wrong ROM onto my phone. I got the phone back to stock using ODIN.
My thread can be found here
http://forum.xda-developers.com/showthread.php?p=14172335#post14172335
hope it helps
Acnescar said:
I had this problem after flashing the wrong ROM onto my phone. I got the phone back to stock using ODIN.
My thread can be found here
http://forum.xda-developers.com/showthread.php?p=14172335#post14172335
hope it helps
Click to expand...
Click to collapse
OMG!! im having the same issue. could you please post the link for ODIN so i can return to stock and take it from there please? I rely on my phone so much and i need it asap thank you.
same problem with me.
but in my case, the phone not only freeze after the google logo before boot. I tried several times to pull the battery and start the phone again, it took several times until the phone can boot normally again.
After that, my nexus s can work as usual. but it only takes 3-4 hour until it freeze/hangs or reboot automatically and show image of green robot lay down with red alert triangle...
sometimes I noticed all application force closed like gmail, gtalk, etc. (its a basic apps instead of 3rd party app)
History :
- root GB 2.37 using superoneclick
- upgrade OTA to ICS 4.04
- problem happens
- root using guide : nexusshacks.com
- unroot using guide : nexusshacks.com
- back to factory setting on GB 2.34
- upgrade OTA to ICS 4.04
- Still got that problem.....
I'm using Nexus S 4G Sprint, pls help me guys...
nexus s won't boot
I had the same problem and read elsewhere that heating the phone with a hairdryer solves the problem.
I must say, indeed it did.
I removed the battery and the SIM card, then heated up the phone (so it really feels warm) put back the battery and sim and simsalebim the phone started again. and is still working since (now already a few day's)
It seems that a component in the phone is heat sensitive, the question in my mind is when will this show again and do I need to consider buying a new phone.
But sofar it works
PS I also tried hard reset factory reset the lot, but in the end only heating up helped.
Good luck, David
I fixed this problem! but I had to wipe all user data by rooting it using nexusrootICS. It finally boots up and the phone works now... that's all I need.
So I wanted to wake up my nexus 5 with the volume buttons. Looking online I found that you could add code to your build.prop.. which I did.. then rebooted...
Now my phone does 'nothing'... When I press the power button it vibrates 2 times and nothing happens...
Help!.. Have no idea what i can do to get things running again
P.S. I've got Slimkat ROM running
S.Phrenic said:
So I wanted to wake up my nexus 5 with the volume buttons. Looking online I found that you could add code to your build.prop.. which I did.. then rebooted...
Now my phone does 'nothing'... When I press the power button it vibrates 2 times and nothing happens...
Help!.. Have no idea what i can do to get things running again
P.S. I've got Slimkat ROM running
Click to expand...
Click to collapse
Can you get into bootloader? Recovery?
Lethargy said:
Can you get into bootloader? Recovery?
Click to expand...
Click to collapse
Currently, nope... I'm trying.. I see that sometimes the screen is on... sometimes I see the Google Logo... but Can't fully figure out when that happens
[EDIT]YES!!!!!!!!! Got in.!!!!!!... *pfieuw*.. now what do i do?
Reflash the factory with the nexus root toolkit
Croc on Nexus 5 with Mahdi + ElementalX
Croc97 said:
Reflash the factory with the nexus root toolkit
Croc on Nexus 5 with Mahdi + ElementalX
Click to expand...
Click to collapse
Please don't use toolkits.
Croc97 said:
Reflash the factory with the nexus root toolkit
Croc on Nexus 5 with Mahdi + ElementalX
Click to expand...
Click to collapse
Don't exaclty know what you mean with that..
I've downloaded Kwongger's Nexus 5 All-In-One Toolkit , I hope that's what you meant. And then it says it's missing the hammerhead.image.zip... which I assume is the stockROM?.. If so, shouldn't I Reflash to Slimkat?
Sorry for being such a Noob. I've had Samsung for years and just switched to Nexus (bought it last week). Still need to learn my way around things
S.Phrenic said:
Don't exaclty know what you mean with that..
I've downloaded Kwongger's Nexus 5 All-In-One Toolkit , I hope that's what you meant. And then it says it's missing the hammerhead.image.zip... which I assume is the stockROM?.. If so, shouldn't I Reflash to Slimkat?
Sorry for being such a Noob. I've had Samsung for years and just switched to Nexus (bought it last week). Still need to learn my way around things
Click to expand...
Click to collapse
Read my reply to your PM and the 2nd link in my signature, then refer to the first link if you need
Lethargy said:
Read my reply to your PM and the 2nd link in my signature, then refer to the first link if you need
Click to expand...
Click to collapse
Let me start with, Thank you so much for your time
However, It seems like I'm unable to install the right drivers on my PC for my phone and adb doesn't detect my device (which is strange as CF-auto-root did see the device and worked fine)
I walked through multiple tutorials about installing drivers. Actually have windows detecting my phone fine (I see it in device manager) and I've reinstalled google USB drivers multiple times now, rebooting my PC and deleting drivers and reinstalling them
I've justed factory reset my phone, but that just got me to a Google logo stuck (which I read about in your link in your signature)..
Because adb doesn't detect my device I'm unable to pull build.prop... which means I feel stuck again.
Would you have a direction for me to go towards to continue my journey through Nexus5-Land?
S.Phrenic said:
Let me start with, Thank you so much for your time
However, It seems like I'm unable to install the right drivers on my PC for my phone and adb doesn't detect my device (which is strange as CF-auto-root did see the device and worked fine)
I walked through multiple tutorials about installing drivers. Actually have windows detecting my phone fine (I see it in device manager) and I've reinstalled google USB drivers multiple times now, rebooting my PC and deleting drivers and reinstalling them
I've justed factory reset my phone, but that just got me to a Google logo stuck (which I read about in your link in your signature)..
Because adb doesn't detect my device I'm unable to pull build.prop... which means I feel stuck again.
Would you have a direction for me to go towards to continue my journey through Nexus5-Land?
Click to expand...
Click to collapse
If you're using Windows 8, 8.1 or 8.1U1 you'll need to disable driver signature enforcement.
Try flashing the factory images in fastboot?
Could somebody not just make a flashable zip with the correct build.prop?
Failing that, just reflash the ROM.
Lethargy said:
If you're using Windows 8, 8.1 or 8.1U1 you'll need to disable driver signature enforcement.
Try flashing the factory images in fastboot?
Click to expand...
Click to collapse
It seems like it worked! Completly back to StockROM but the phone works again. Thank you so much for your time.
And you're right, I should learn to read and understand what I'm doing before I do anything with my phone. Sorry for the inconvenience and thank you for the help you've given.
S.Phrenic said:
It seems like it worked! Completly back to StockROM but the phone works again. Thank you so much for your time.
And you're right, I should learn to read and understand what I'm doing before I do anything with my phone. Sorry for the inconvenience and thank you for the help you've given.
Click to expand...
Click to collapse
Glad you got it worked out
S.Phrenic said:
It seems like it worked! Completly back to StockROM but the phone works again. Thank you so much for your time.
And you're right, I should learn to read and understand what I'm doing before I do anything with my phone. Sorry for the inconvenience and thank you for the help you've given.
Click to expand...
Click to collapse
Glad you got it sorted but, unless you couldn't boot into recovery, you didn't need to go back to stock.
Flashing the correct build.prop or ROM you were using should have sorted it out, without losing any data (you would have lost any system mods if you flashed the ROM again, though).
I'm only mentioning this in case somebody else searches and finds this thread for the same problem.
I've changed the build.prop loads of times on many devices and only once it went into a bootloop. Flashing a build.prop zip sorted it.
I have a rooted StraightTalk SCH-S968C Samsung Galaxy S III (with the stock AOSP ROM) that I just screwed up. I had used EZ-Recovery to flash TWRP 2.2.0 to the phone. Now TWRP says there is no OS! I can only boot into TWRP - nothing else. It won't even let me power-down the phone. Is there some way I can recover from this, or do I now have a very expensive electronic brick (that runs TWRP)? I have adb installed on my laptop and I know it works, so that's one possible route to recovery. Any help would be much appreciated!
ScottDB said:
I have a rooted StraightTalk SCH-S968C Samsung Galaxy S III (with the stock AOSP ROM) that I just screwed up. I had used EZ-Recovery to flash TWRP 2.2.0 to the phone. Now TWRP says there is no OS! I can only boot into TWRP - nothing else. It won't even let me power-down the phone. Is there some way I can recover from this, or do I now have a very expensive electronic brick (that runs TWRP)? I have adb installed on my laptop and I know it works, so that's one possible route to recovery. Any help would be much appreciated!
Click to expand...
Click to collapse
I'm pretty sure it's possible to return it completely to stock with the COMBINATION_S968CUDUAMH1_S968CTFNAMH1_1304014_REV09_user_low_ship.tar.md5 file through Odin. I just to happen to have the file right here.. small warning though, it's 1.2 gigs.
https://mega.co.nz/#!gRI3DD5L!dRW8ORzfQI5j1JyKHVBTNifomPCXoqL14B9GF4oxvQY
aekel87 said:
I'm pretty sure it's possible to return it completely to stock with the COMBINATION_S968CUDUAMH1_S968CTFNAMH1_1304014_REV09_user_low_ship.tar.md5 file through Odin. I just to happen to have the file right here.. small warning though, it's 1.2 gigs.
https://mega.co.nz/#!gRI3DD5L!dRW8ORzfQI5j1JyKHVBTNifomPCXoqL14B9GF4oxvQY
Click to expand...
Click to collapse
That's the file I am offering to host on my Website, since nobody seems to be able to download it from Dropbox. I'm having trouble downloading it from Mega... Since the file is over 1 GB, Mega insisted I needed to download their extension, but it's not compatible with Firefox 22. I tried Chrome, and Mega says that Chrome on my laptop is "a bit outdated"... sheesh! I'll try and update it.
(added later) - I found a Dropbox link for the file and it's downloading now.
If you want to FTP the file to my Website, let me know by PM and I'll give you the username and password.
I tried using fastboot to install CWM Recovery, but fastboot is eternally "waiting for device" even though it's there (adb can see it).
Aug. 7 - Got the file I needed, but didn't use it since Windows7 would not recognize the phone even after I installed the drivers. (I think it was an issue with automatic updates being disabled...) In the meantime... I tried the button-combo for the bootloader (which I swore I tried the day before and it didn't work), and the phone booted into the bootloader! From there, I pressed "Volume down" to cancel & reboot the phone, and it went into the stock system - it was all still there! First thing I did was immediately use EZ-Recovery to flash CWM 5.8.4.5. - Issue resolved!
Deleted.
ScottDB said:
That's the file I am offering to host on my Website, since nobody seems to be able to download it from Dropbox. I'm having trouble downloading it from Mega... Since the file is over 1 GB, Mega insisted I needed to download their extension, but it's not compatible with Firefox 22. I tried Chrome, and Mega says that Chrome on my laptop is "a bit outdated"... sheesh! I'll try and update it.
(added later) - I found a Dropbox link for the file and it's downloading now.
If you want to FTP the file to my Website, let me know by PM and I'll give you the username and password.
I tried using fastboot to install CWM Recovery, but fastboot is eternally "waiting for device" even though it's there (adb can see it).
Aug. 7 - Got the file I needed, but didn't use it since Windows7 would not recognize the phone even after I installed the drivers. (I think it was an issue with automatic updates being disabled...) In the meantime... I tried the button-combo for the bootloader (which I swore I tried the day before and it didn't work), and the phone booted into the bootloader! From there, I pressed "Volume down" to cancel & reboot the phone, and it went into the stock system - it was all still there! First thing I did was immediately use EZ-Recovery to flash CWM 5.8.4.5. - Issue resolved!
Click to expand...
Click to collapse
Thank you!!!! I just had the same problem. However even when using cwm i get errors in the recovery. Unable to mount anything or do anything besides reboot. Any ideas?
need stock Firmware
Have any idea where i can get this file? Ive bricked my phone too. Durnnit!
iamwaynes said:
Have any idea where i can get this file? Ive bricked my phone too. Durnnit!
Click to expand...
Click to collapse
This is the h1 stock you need. type this in google you should find the download if not I have it.
COMBINATION_S968CUDUAMH1_S968CTFNAMH1_1304014_REV0
Dont use e-z recovery. I had the same problem neither cwm or twrp from ez recovery worked and then cwm said no os on my phine so I flashed that file from download mode and was back to stock.
How did u find a recovery that worked mine is saying the same thing
Sent from my SM-N900T using Tapatalk
iamwaynes said:
How did u find a recovery that worked mine is saying the same thing
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1771398
In that thread go down to method 2 of getting a custom recovery. I downloaded cwm touch from the link there and then installed it with android terminal emulator using the codes that it says to type in. I tried to look up that stock rom but I didnt find it. Its on the forum somewhere in a thread about how to root the straight talk s3 and how first you need to download and flash the h1 baseband stock rom
Thanks I found the stock rom fixing it now.
Sent from my SM-N900T using Tapatalk
iamwaynes said:
Thanks I found the stock rom fixing it now.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Ok I've re rooted and tried to install recovery. Odin put it in wrong place. Says no operating system . What now?
Sent from my SM-N900T using Tapatalk
iamwaynes said:
Ok I've re rooted and tried to install recovery. Odin put it in wrong place. Says no operating system . What now?
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Have you gotten recovery installed and straightened out yet?
Let me know if you need some help, tell me where you're at and what you've got going on with what you have.
I returned phone to stock. The recovery wasn't in the right place obviously. So that's where I am . Stuck back at stock. Thanks for any help you can give.
Sent from my SM-N900T using Tapatalk
iamwaynes said:
I returned phone to stock. The recovery wasn't in the right place obviously. So that's where I am . Stuck back at stock. Thanks for any help you can give.
Sent from my SM-N900T using Tapatalk
Click to expand...
Click to collapse
Are you on stock not rooted or you are rooted?
Do you have stock recovery or custom.
I can get you to wherever you need or want. Tell me what you need or where you'd like to be.
Droidriven said:
Are you on stock not rooted or you are rooted?
Do you have stock recovery or custom.
I can get you to wherever you need or want. Tell me what you need or where you'd like to be.
Click to expand...
Click to collapse
I have combined 2 s3's to make one good one. This is the proper thread for the model of the chipset. The phone has been worked on buy someone who only thought they were a genious. I've found traces and from surfing the forums I'm pretty sure I know what they did even. I'm gonna grab these stock images and flash back to stock. I just wanted to put a word in now to see how dead this thread is. BTW just for the record easy safe root is achievable with safroot for Att g s 4. I've confirmed that. Root is no issue. Modem drivers are jacked up. I want what I have now with WiFi in tact and custom recovery. Just wanted to get the word in in case I hit a wall with recovery as I am now before the flash to stock. Thanks in advance for any help. Sorry for the ramble
---------- Post added at 07:23 AM ---------- Previous post was at 07:03 AM ----------
ScottDB said:
That's the file I am offering to host on my Website, since nobody seems to be able to download it from Dropbox. I'm having trouble downloading it from Mega... Since the file is over 1 GB, Mega insisted I needed to download their extension, but it's not compatible with Firefox 22. I tried Chrome, and Mega says that Chrome on my laptop is "a bit outdated"... sheesh! I'll try and update it.
(added later) - I found a Dropbox link for the file and it's downloading now.
If you want to FTP the file to my Website, let me know by PM and I'll give you the username and password.
I tried using fastboot to install CWM Recovery, but fastboot is eternally "waiting for device" even though it's there (adb can see it).
Aug. 7 - Got the file I needed, but didn't use it since Windows7 would not recognize the phone even after I installed the drivers. (I think it was an issue with automatic updates being disabled...) In the meantime... I tried the button-combo for the bootloader (which I swore I tried the day before and it didn't work), and the phone booted into the bootloader! From there, I pressed "Volume down" to cancel & reboot the phone, and it went into the stock system - it was all still there! First thing I did was immediately use EZ-Recovery to flash CWM 5.8.4.5. - Issue resolved!
Click to expand...
Click to collapse
Does anyone have a good link for h1 stock. All the links I can find including aa51 are dead. I need to go stock to fix the modem. I can handle everything from there I just need stock and I've trolled XDA , aa51, and several others. All links are dead. Probably for a long long time . any help is greatly appreciated
---------- Post added at 07:42 AM ---------- Previous post was at 07:23 AM ----------
sazendrak said:
I have combined 2 s3's to make one good one. This is the proper thread for the model of the chipset. The phone has been worked on buy someone who only thought they were a genious. I've found traces and from surfing the forums I'm pretty sure I know what they did even. I'm gonna grab these stock images and flash back to stock. I just wanted to put a word in now to see how dead this thread is. BTW just for the record easy safe root is achievable with safroot for Att g s 4. I've confirmed that. Root is no issue. Modem drivers are jacked up. I want what I have now with WiFi in tact and custom recovery. Just wanted to get the word in in case I hit a wall with recovery as I am now before the flash to stock. Thanks in advance for any help. Sorry for the ramble
---------- Post added at 07:23 AM ---------- Previous post was at 07:03 AM ----------
Does anyone have a good link for h1 stock. All the links I can find including aa51 are dead. I need to go stock to fix the modem. I can handle everything from there I just need stock and I've trolled XDA , aa51, and several others. All links are dead. Probably for a long long time . any help is greatly appreciated
Click to expand...
Click to collapse
Finally found it here
https://forum.xda-developers.com/showthread.php?t=2516498&page=28
I just got my hands on the sprint note edge (such an amazing device!) and i've been trying to root it with cf auto root but every time i flash with Odin, it fails with the progress bar on the phone only about halfway. Any suggestions? I'm on the latest firmware, nk1, which matches the version listed on the cf auto root site.
Thanks in advance
Edit:
HEY, YOU. YEAH YOU. READ THIS BEFORE YOU POST:
We figured out the solution quite a while back, but I know no one wants to read the entire thread, so here's a summary c/p'd from the end:
But to summarize, we've been able to get root by flashing CF auto root, letting it fail, then immediately flashing TWRP. To fix any issues encountered with xposed framework (stock sms not working, lagginess, installations taking forever, etc.), freeze with titanium/delete data for shealth, health services, and private mode, install securestorage module in xposed or use the equivalent option in Wanam, reboot, and unfreeze.
Click to expand...
Click to collapse
Now if you've tried this and you're still having issues, then post ahead. If you haven't tried this, or need help with specifics, read the thread. There's a post by me halfway through or so with 4 XDA links in it. If you want more info on the problem with xposed, check out those links.
jooniloh said:
I just got my hands on the sprint note edge (such an amazing device!) and i've been trying to root it with cf auto root but every time i flash with Odin, it fails with the progress bar on the phone only about halfway. Any suggestions? I'm on the latest firmware, nk1, which matches the version listed on the cf auto root site.
Thanks in advance
Click to expand...
Click to collapse
You may check out this thread: http://forum.xda-developers.com/note-edge/general/easy-steps-stock-odin-n915tuvu1anjl-sm-t2943993
Its for a Tmobile version, but it looks like they may have had the same issue, but figured it out... I haven't tried it yet, but am REAL close to giving it a shot. It looks to me that flashing TWRP after the fail, may be the key to making it successful? I have the Sprint model too, but am still on NJL build.
Does TWRP fully support the note edge yet? Some of those steps (disabling screen timeout) make it seem otherwise. I'm usually hesitant to go for workarounds rather than actual fixes... :/ tell me if you do try it out though.
Next1776 said:
You may check out this thread: http://forum.xda-developers.com/note-edge/general/easy-steps-stock-odin-n915tuvu1anjl-sm-t2943993
Its for a Tmobile version, but it looks like they may have had the same issue, but figured it out... I haven't tried it yet, but am REAL close to giving it a shot. It looks to me that flashing TWRP after the fail, may be the key to making it successful? I have the Sprint model too, but am still on NJL build.
Click to expand...
Click to collapse
I'm not sure about TWRP, but was going to try the Note 4 version. I updated to NK1 now, so may give it a whirl... Nah - You go first, lol. I'll post if I decide to go through with it.:good:
Next1776 said:
I'm not sure about TWRP, but was going to try the Note 4 version. I updated to NK1 now, so may give it a whirl... Nah - You go first, lol. I'll post if I decide to go through with it.:good:
Click to expand...
Click to collapse
Too Funny.. I heard the note 4 files where working from an undisclosed source.. I haven't powered mine on yet, Still waiting on a screen protector and case.. Lol
z31k said:
Too Funny.. I heard the note 4 files where working from an undisclosed source.. I haven't powered mine on yet, Still waiting on a screen protector and case.. Lol
Click to expand...
Click to collapse
to clarify, is that the SPRINT note 4 cf auto root files you're referring to?
Just checked. Sprint Note 4 cf auto root is for NIE. Is this even safe to try on the Edge?
jooniloh said:
to clarify, is that the SPRINT note 4 cf auto root files you're referring to?
Just checked. Sprint Note 4 cf auto root is for NIE. Is this even safe to try on the Edge?
Click to expand...
Click to collapse
That's what I was told.. Sprint note 4 auto root...
I would wait up if you feel uneasy about it.. lol
at least until they have a edge auto root. I may try the note 4 sometime next week when the screen protector comes in..
z31k said:
That's what I was told.. Sprint note 4 auto root...
I would wait up if you feel uneasy about it.. lol
at least until they have a edge auto root. I may try the note 4 sometime next week when the screen protector comes in..
Click to expand...
Click to collapse
There is an edge auto root. It just happens to be failing at the moment (for sprint anyways). There are workarounds for the T-Mobile auto root (which is also failing) but we're all too chicken here to try it on our new shiney Note Edges . . . Lol
jooniloh said:
There is an edge auto root. It just happens to be failing at the moment (for sprint anyways). There are workarounds for the T-Mobile auto root (which is also failing) but we're all too chicken here to try it on our new shiney Note Edges . . . Lol
Click to expand...
Click to collapse
Lmfao!!
OK. I wasn't too chicken... and should have been! HELP!!!!!
I attempted the ODIN flash with the proper CF that states that it is for the Sprint Edge... and now have a soft (I hope) bricked phone. The message I have on the screen right now is:
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Like I said.... HELP!!!!!
I'm not familiar with KIES but I guess I'll get that way....
Update: I am able to get into download mode... now now if I could just get my hands on a STOCK ROM to ODIN... ANYONE?
beejmeister said:
OK. I wasn't too chicken... and should have been! HELP!!!!!
I attempted the ODIN flash with the proper CF that states that it is for the Sprint Edge... and now have a soft (I hope) bricked phone. The message I have on the screen right now is:
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Like I said.... HELP!!!!!
I'm not familiar with KIES but I guess I'll get that way....
Update: I am able to get into download mode... now now if I could just get my hands on a STOCK ROM to ODIN... ANYONE?
Click to expand...
Click to collapse
Nope. That's what we all tried and it failed for us too. We're trying to figure out a fix or alternative to this. Anyways, to fix your device, take the .tar.md5 file found inside the CF auto root directory and open it with an archiver like 7zip. Extract the recovery.img to somewhere and run this tool on it. Then open up the odin included in CF auto root and choose the recovery.tar.md5 you created rather than the usual file. Flash in download mode and you're good to go.
jooniloh said:
Nope. That's what we all tried and it failed for us too. We're trying to figure out a fix or alternative to this. Anyways, to fix your device, take the .tar.md5 file found inside the CF auto root directory and open it with an archiver like 7zip. Extract the recovery.img to somewhere and run this tool on it. Then open up the odin included in CF auto root and choose the recovery.tar.md5 you created rather than the usual file. Flash in download mode and you're good to go.
Click to expand...
Click to collapse
If there is one thing I've learned in my many years on XDA... DON'T PANIC! Someone will help you. I didn't panic... You helped me hugely. Figured I'd go home and reactivate my Note 3... but didn't even have to do that. THANKS jooniloh! Many thanks...
beejmeister said:
If there is one thing I've learned in my many years on XDA... DON'T PANIC! Someone will help you. I didn't panic... You helped me hugely. Figured I'd go home and reactivate my Note 3... but didn't even have to do that. THANKS jooniloh! Many thanks...
Click to expand...
Click to collapse
No problem. Glad I could help. Now let's just hope for a stable root method soon! Out of curiosity, are you also on NK1? I wonder if anyone who didn't upgrade was able to get root successfully . . .
beejmeister said:
OK. I wasn't too chicken... and should have been! HELP!!!!!
I attempted the ODIN flash with the proper CF that states that it is for the Sprint Edge... and now have a soft (I hope) bricked phone. The message I have on the screen right now is:
"Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again."
Like I said.... HELP!!!!!
I'm not familiar with KIES but I guess I'll get that way....
Update: I am able to get into download mode... now now if I could just get my hands on a STOCK ROM to ODIN... ANYONE?
Click to expand...
Click to collapse
Man, this is happening fast... I just got it done successfuly rooting my Sprint Edge. Don't freak, follow the instructions on this thread which works on Tmobile devices. I didn't install the SD card fix file yet, but may if I need it. You are basically starting at the FAIL point of that thread. Although you need the SU file on your phone, which you may be able to get it by putting it on a Microsd and accessing it from recovery that way. Good Luck, and don't panic, lol.
EDIT: See my post here : http://forum.xda-developers.com/note-edge/general/info-galaxy-note-edge-sm-n915-t2945942 for more details on what worked for me
jooniloh said:
No problem. Glad I could help. Now let's just hope for a stable root method soon! Out of curiosity, are you also on NK1? I wonder if anyone who didn't upgrade was able to get root successfully . . .
Click to expand...
Click to collapse
Yup! On NK1. Did the update yesterday when I first got the phone. Guess we're seeing a pattern here!
---------- Post added at 06:16 PM ---------- Previous post was at 06:15 PM ----------
Next1776 said:
Man, this is happening fast... I just got it done successfuly rooting my Sprint Edge. Don't freak, follow the instructions on this thread which works on Tmobile devices. I didn't install the SD card fix file yet, but may if I need it. You are basically starting at the FAIL point of that thread. Although you need the SU file on your phone, which you may be able to get it by putting it on a Microsd and accessing it from recovery that way. Good Luck, and don't panic, lol.
Click to expand...
Click to collapse
OK. Now I'll ask THE question: Next1776, are YOU on NK1?
Next1776 said:
Man, this is happening fast... I just got it done successfuly rooting my Sprint Edge. Don't freak, follow the instructions on this thread which works on Tmobile devices. I didn't install the SD card fix file yet, but may if I need it. You are basically starting at the FAIL point of that thread. Although you need the SU file on your phone, which you may be able to get it by putting it on a Microsd and accessing it from recovery that way. Good Luck, and don't panic, lol.
Click to expand...
Click to collapse
Can you tell me exactly what you did step by step? Also are you on the latest sprint firmware?
And what version of TWRP did you use?
beejmeister said:
Yup! On NK1. Did the update yesterday when I first got the phone. Guess we're seeing a pattern here!
---------- Post added at 06:16 PM ---------- Previous post was at 06:15 PM ----------
OK. Now I'll ask THE question: Next1776, are YOU on NK1?
Click to expand...
Click to collapse
NK1
---------- Post added at 06:12 PM ---------- Previous post was at 05:47 PM ----------
jooniloh said:
Can you tell me exactly what you did step by step? Also are you on the latest sprint firmware?
And what version of TWRP did you use?
Click to expand...
Click to collapse
I actually downloaded the Chainfire file yesterday for the SM N915P, but was still too chicken to try it. After I saw this thread today, I decided to go for it. All I basically did was follow the instructions in TEKHD 's thread for the SM915T.
-Dowloaded Chainfire's Sprint AutoRoot file, Unzipped it.
-Put phone in download mode, selcted the Chainfire's Sprint AutoRoot tar file and hit Start.
-ODIN flashed "FAIL".
-I then flashed a 2.8.0.0 TWRP file for the Note 4, which ODIN said was successful, but it would not boot into recovery (so don't do that).
-I flashed the 2.8.1.1 Tmobile TWRP file from TEKHD's thread, ODIN said success.
-Booted into recovery, adjusted settings for brightness in TWRP, (TWRP was acting really flaky, but I pressed on) I couldn't find the UPDATE-SuperSU-v2.16.zip file in recovery, (I put the file on my removable SD card) so I rebooted recovery, and this time was able to find the UPDATE-SuperSU-v2.16.zip, and flashed it.
-Wiped cache/ Dalvik Cache. Hit Reboot-> System, TWRP said it didn't appear to have root, do I want to root? Hit yes, go , whatever, it rebooted, let settle for a few minutes, and ROOT was born!
Hope that helps and I didn't miss something, but thats how it went down for me.
To sum it up, Follow TEKHD's Tmobile thread, with the exception of the Tmobile Chainfire file, (use the Sprint one obviously) I also did not flash the SD card fix from that thread.
Let me know if you have questions, but I will have to bug out for a while here until this evening...
Good Luck everyone!
Next1776 said:
NK1
---------- Post added at 06:12 PM ---------- Previous post was at 05:47 PM ----------
I actually downloaded the Chainfire file yesterday for the SM N915P, but was still too chicken to try it. After I saw this thread today, I decided to go for it. All I basically did was follow the instructions in TEKHD 's thread for the SM915T.
-Dowloaded Chainfire's Sprint AutoRoot file, Unzipped it.
-Put phone in download mode, selcted the Chainfire's Sprint AutoRoot tar file and hit Start.
-ODIN flashed "FAIL".
-I then flashed a 2.8.0.0 TWRP file for the Note 4, which ODIN said was successful, but it would not boot into recovery (so don't do that).
-I flashed the 2.8.1.1 Tmobile TWRP file from TEKHD's thread, ODIN said success.
-Booted into recovery, adjusted settings for brightness in TWRP, (TWRP was acting really flaky, but I pressed on) I couldn't find the UPDATE-SuperSU-v2.16.zip file in recovery, (I put the file on my removable SD card) so I rebooted recovery, and this time was able to find the UPDATE-SuperSU-v2.16.zip, and flashed it.
-Wiped cache/ Dalvik Cache. Hit Reboot-> System, TWRP said it didn't appear to have root, do I want to root? Hit yes, go , whatever, it rebooted, let settle for a few minutes, and ROOT was born!
Hope that helps and I didn't miss something, but thats how it went down for me.
To sum it up, Follow TEKHD's Tmobile thread, with the exception of the Tmobile Chainfire file, (use the Sprint one obviously) I also did not flash the SD card fix from that thread.
Let me know if you have questions, but I will have to bug out for a while here until this evening...
Good Luck everyone!
Click to expand...
Click to collapse
No need to flash the SD card fix. there's apps on the play store that will patch the necessary files for that (and you can delete the app afterwards). Interesting that the TMO twrp worked . . . Someone should try that with the SPRINT twrp 2.8.1.1 found here.
Edit: I tried repeatedly to flash both 2.8.1.1 and 2.8.1.0 versions of the SPRINT NOTE 4 twrp and odin consistently crashed on "File analysis".
Edit: I took the plunge and went with the tmobile method. Nothing went wrong. Everything seems to be working fine. The TMO Note 4 recovery is annoying though (two strips of white on both sides of the screen). I didn't have any issues with how it ran like Next1776 did though.
Edit: I'm experiencing some odd issues. The primary one is that anything I install through xposed or f-droid takes FOREVER to install. Anyone else getting this?
jooniloh said:
No need to flash the SD card fix. there's apps on the play store that will patch the necessary files for that (and you can delete the app afterwards). Interesting that the TMO twrp worked . . . Someone should try that with the SPRINT twrp 2.8.1.1 found here.
Edit: I tried repeatedly to flash both 2.8.1.1 and 2.8.1.0 versions of the SPRINT NOTE 4 twrp and odin consistently crashed on "File analysis".
Edit: I took the plunge and went with the tmobile method. Nothing went wrong. Everything seems to be working fine. The TMO Note 4 recovery is annoying though (two strips of white on both sides of the screen). I didn't have any issues with how it ran like Next1776 did though.
Edit: I'm experiencing some odd issues. The primary one is that anything I install through xposed or f-droid takes FOREVER to install. Anyone else getting this?
Click to expand...
Click to collapse
BUt just to confirm, jooniloh.... you do have confirmable root? Guess my clue should be that you are using xposed.... but just wanted to confirm before I went down the rabbit hole....
jooniloh said:
No need to flash the SD card fix. there's apps on the play store that will patch the necessary files for that (and you can delete the app afterwards). Interesting that the TMO twrp worked . . . Someone should try that with the SPRINT twrp 2.8.1.1 found here.
Edit: I tried repeatedly to flash both 2.8.1.1 and 2.8.1.0 versions of the SPRINT NOTE 4 twrp and odin consistently crashed on "File analysis".
Edit: I took the plunge and went with the tmobile method. Nothing went wrong. Everything seems to be working fine. The TMO Note 4 recovery is annoying though (two strips of white on both sides of the screen). I didn't have any issues with how it ran like Next1776 did though.
Edit: I'm experiencing some odd issues. The primary one is that anything I install through xposed or f-droid takes FOREVER to install. Anyone else getting this?
Click to expand...
Click to collapse
Awesome. Glad you are able to join the party!
I'm not having any issues right now. I have installed Xposed and Wanam without any issues so far. I did disable Knox and Secure storage with Wanam (under security hacks) as another poster suggested. Maybe also try wiping Cache and dalvik in recovery ? Hopefully we will have a stable custom recovery available soon. I say stable, but I guess this one is "stable" - its just not real pretty...
ON: Galaxy S3 4.4.2 Verizon(d2vzw) -->OK, I know you all may think I didn't read the other debrick threads, your wrong. I made this new thread because i HAVE tried endlessy every method of debrick on this forum and the internet, and no success. I was messing around with safestrap and decided to try and flash a rom called flashingdroid: for some reason. So i did as usual, boot into recovery(safestrap 3.75) and wipe current os and flash the new one. So i wiped my stock rom(after making a backup) and installed/flashed the new one(flashingdroid) and after seemingly a successful flash, i pressed reboot. Then it went downhill. One second after i pressed reboot, the screen flashed quickly, then shutoff, for good. I couldn't boot it or get into recovery or odin or ANYTHING. I tried the microsd method of debricking with minimal success. It will only give me one vibration, then black scree with that method. Nothing else has worked. I know this was a noob mistake somehow, but does anyone know any special tricks or something? Will a good jig maybe work? I have doubt verizon or samsung will accept it back(it was well rooted!). Please anything/anybody help! I really don't want to buy a new phone or jtag it. Thanks!:crying:
You may have read the debrick threads, but what you should have done from the beginning was read and pay attention to which forum you were in. You flashed a ROM for the International version of the S3 onto your Verizon S3. You almost certainly turned your phone into a shiny paper weight. JTAG may be your only hope. If you don't have one, check out mobiletechvideos.com. I'm not familiar enough with safestrap to know if that may have actually saved you since it is not a traditional recovery and I don't know if it touches all the partitions. In the future, research, research, and research, and pay very close attention to exactly what you are flashing onto your phone. For the Verizon S3, you should only flash ROMs from this sub-forum. And when using safestrap, you are restricted to only flashing ROMs with the same build number as what your phone is currently on in a stock condition.
Ok...Thanks
landshark68 said:
You may have read the debrick threads, but what you should have done from the beginning was read and pay attention to which forum you were in. You flashed a ROM for the International version of the S3 onto your Verizon S3. You almost certainly turned your phone into a shiny paper weight. JTAG may be your only hope. If you don't have one, check out mobiletechvideos.com. I'm not familiar enough with safestrap to know if that may have actually saved you since it is not a traditional recovery and I don't know if it touches all the partitions. In the future, research, research, and research, and pay very close attention to exactly what you are flashing onto your phone. For the Verizon S3, you should only flash ROMs from this sub-forum. And when using safestrap, you are restricted to only flashing ROMs with the same build number as what your phone is currently on in a stock condition.
Click to expand...
Click to collapse
Im kinda tired of my so confined locked bootloader and phone model anyways. Im going to purchase a $20 JTAG service off ebay, hope that works.
Root Wizard said:
Im kinda tired of my so confined locked bootloader and phone model anyways. Im going to purchase a $20 JTAG service off ebay, hope that works.
Click to expand...
Click to collapse
I'd be very careful with eBay, they tend to be junk. I've been an eBay member over 10 years and ran into a lot of it
Sent from my Nexus 5
Try MicroSD 16GB (2GB not work)
Confused About What's Possible for Modding a Stock Verizon S3
Can someone please steer me in the right direction? I have a Verizon Galaxy S3 running 4.4.2 stock. I recently rooted my phone, but I realize I am very limited as to any mods I can make due to the locked bootloader. Am I able to modify my OS in some way at all (Safestrap) to make my phone run better, or am I just too late in going about this? I've read so much on this subject, but the more I read, it seems the more confused I get. I want to be careful not to brick my phone and would love to see some precise directions on what I could do. Thanks a million for any help at all!
straykat said:
Can someone please steer me in the right direction? I have a Verizon Galaxy S3 running 4.4.2 stock. I recently rooted my phone, but I realize I am very limited as to any mods I can make due to the locked bootloader. Am I able to modify my OS in some way at all (Safestrap) to make my phone run better, or am I just too late in going about this? I've read so much on this subject, but the more I read, it seems the more confused I get. I want to be careful not to brick my phone and would love to see some precise directions on what I could do. Thanks a million for any help at all!
Click to expand...
Click to collapse
You should be able to install xposed but as far as mods your very limited to what you can do with it
Sent from my Nexus 5
ShapesBlue said:
You should be able to install xposed but as far as mods your very limited to what you can do with it
Sent from my Nexus 5
Click to expand...
Click to collapse
Hey, thanks a lot for that! As much as I've read, I've never heard of xposed. I'll research it and see what it takes and what it will do for my phone. If it helps at all, which I'm sure it will, that would be great. Thanks again for your reply!
straykat said:
Hey, thanks a lot for that! As much as I've read, I've never heard of xposed. I'll research it and see what it takes and what it will do for my phone. If it helps at all, which I'm sure it will, that would be great. Thanks again for your reply!
Click to expand...
Click to collapse
Your very welcome. That's what xda is all about. Helping others
Sent from my Nexus 5
XDA Forum - the best place for learning...
ShapesBlue said:
Your very welcome. That's what xda is all about. Helping others
Sent from my Nexus 5
Click to expand...
Click to collapse
ShapesBlue-
It's hard to compare this forum with the others. I believe the people here are the most knowledgeable and, like you, very helpful. Funny enough, or not, I posed a related question on another site (initials AC), and it took over 150 views and a week later before anybody offered a reply. Anyway, I can see there is lots of information on this forum about xposed, so now I'll go and learn as much as I can about it. Thanks again for your help!
Btw, here's a link for others like me who are clueless about xposed: http://forum.xda-developers.com/showthread.php?t=2299428
straykat said:
ShapesBlue-
It's hard to compare this forum with the others. I believe the people here are the most knowledgeable and, like you, very helpful. Funny enough, or not, I posed a related question on another site (initials AC), and it took over 150 views and a week later before anybody offered a reply. Anyway, I can see there is lots of information on this forum about xposed, so now I'll go and learn as much as I can about it. Thanks again for your help!
Btw, here's a link for others like me who are clueless about xposed: http://forum.xda-developers.com/showthread.php?t=2299428
Click to expand...
Click to collapse
I've been around the web going on nearly 20 years and I'd have to agree some are more helpful than others. I find xda to be a great resource for anything android or windows phone related. And yes I agree some are a lot more helpful than others. The guys and gals still lurking around the VZW S3 forums have been here since the beginning for this phone and even though mine is no longer active I still use it daily, mostly for games but will probably never give it up. It was my first true (I'm comparing it to the HTC thunderbolt) android phone
Sent from my Nexus 5
Can't Believe What I - did! - - - Need Help Rebooting Phone
ShapesBlue said:
I've been around the web going on nearly 20 years and I'd have to agree some are more helpful than others. I find xda to be a great resource for anything android or windows phone related. And yes I agree some are a lot more helpful than others. The guys and gals still lurking around the VZW S3 forums have been here since the beginning for this phone and even though mine is no longer active I still use it daily, mostly for games but will probably never give it up. It was my first true (I'm comparing it to the HTC thunderbolt) android phone
Sent from my Nexus 5
Click to expand...
Click to collapse
ShapesBlue-
I seem to have gotten into big trouble - I hope there's a solution. I learned all about Xposed and installed it along with about a dozen modules. Everything was working great, except the torch/flashlight... [I wanted that! ] so, I saw a download for a module on this forum to fix the flashlight... http://forum.xda-developers.com/xposed/modules/xposed-flashlight-fixer-fix-devices-t2867267 . Well, since doing that, I think I realized that I should have left the flashlight alone! When I tried to reboot after adding the module to xposed, I ended up in what i believe is a boot loop. The Samsung screen comes on, and then it gets stuck on the red Verizon screen. I never dreamed that a module installation could cause this; and I guess I figured if it ever happened I could get into recovery mode and restore everthing. Btw, I had done a complete backup of my phone using Titanium on my sd card.
So, here's what I can/can't do now. I can push "down-volume-button" + home + power to get to screen where you can download a cusom OS - then pushing volume-up-button goes to screen that says "Downloading...Do not turn off target!! (Nothing seems to happen from here.) - - - I cannot enter recovery mode by pressing "volume-up" + home + power keys. When I do that I get the big yellow triangle with message - System software not authorized...go to nearest Verizon store. hmmmm.... So, am I hard bricked or soft bricked? Do I have a way out? Thanks very much for any help with this!
straykat said:
ShapesBlue-
I seem to have gotten into big trouble - I hope there's a solution. I learned all about Xposed and installed it along with about a dozen modules. Everything was working great, except the torch/flashlight... [I wanted that! ] so, I saw a download for a module on this forum to fix the flashlight... http://forum.xda-developers.com/xposed/modules/xposed-flashlight-fixer-fix-devices-t2867267 . Well, since doing that, I think I realized that I should have left the flashlight alone! When I tried to reboot after adding the module to xposed, I ended up in what i believe is a boot loop. The Samsung screen comes on, and then it gets stuck on the red Verizon screen. I never dreamed that a module installation could cause this; and I guess I figured if it ever happened I could get into recovery mode and restore everthing. Btw, I had done a complete backup of my phone using Titanium on my sd card.
So, here's what I can/can't do now. I can push "down-volume-button" + home + power to get to screen where you can download a cusom OS - then pushing volume-up-button goes to screen that says "Downloading...Do not turn off target!! (Nothing seems to happen from here.) - - - I cannot enter recovery mode by pressing "volume-up" + home + power keys. When I do that I get the big yellow triangle with message - System software not authorized...go to nearest Verizon store. hmmmm.... So, am I hard bricked or soft bricked? Do I have a way out? Thanks very much for any help with this!
Click to expand...
Click to collapse
No problem. Your soft bricked and it seems your on the latest firmware, correct me if I'm wrong
4.4.2 NE1? If so you can use Odin to flash back to stock 4.4.2 and you should be ok
Sent from my Nexus 5
ShapesBlue said:
No problem. Your soft bricked and it seems your on the latest firmware, correct me if I'm wrong
4.4.2 NE1? If so you can use Odin to flash back to stock 4.4.2 and you should be ok
Sent from my Nexus 5
Click to expand...
Click to collapse
ShapesBlue-
That's great news!!! Thanks!
I believe my phone was on 4.4.3. A file I used in my rooting process using Towelroot was I535VRUDNE1_I535VZWDNE1_VZW; I used Odin before for the root procedure, so the program of course is on my PC. Is there a thread around with instructions how to flash back to the stock firmware? Thanks again a million for getting back to me!
straykat said:
ShapesBlue-
That's great news!!! Thanks!
I believe my phone was on 4.4.3. A file I used in my rooting process using Towelroot was I535VRUDNE1_I535VZWDNE1_VZW; I used Odin before for the root procedure, so the program of course is on my PC. Is there a thread around with instructions how to flash back to the stock firmware? Thanks again a million for getting back to me!
Click to expand...
Click to collapse
But of course. Check this out which should get you what you need
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my Nexus 5
Try kies
straykat said:
ShapesBlue-
That's great news!!! Thanks!
I believe my phone was on 4.4.3. A file I used in my rooting process using Towelroot was I535VRUDNE1_I535VZWDNE1_VZW; I used Odin before for the root procedure, so the program of course is on my PC. Is there a thread around with instructions how to flash back to the stock firmware? Thanks again a million for getting back to me!
Click to expand...
Click to collapse
Instead of odin, you could try using samasung kies 3 and use its emergencey firmware recovery tool which dl's and intalls the correct, latest firmware on your device.
What you do:
Install kies 3 on your computer.
Boot to odin mode on your phone.
Click on tools in kies.
Select emergency firmware recovery option.
Follow on screen directions.
Hope I helped!
ShapesBlue said:
But of course. Check this out which should get you what you need
http://forum.xda-developers.com/showthread.php?t=2639337
Sent from my Nexus 5
Click to expand...
Click to collapse
Shapes Blue & Root Wizard,
Thanks much for your replies. Is it possible for me, having had 4.4.3 on phone, to go to 4.3 instead of 4.4.2? Seems some people think that's an advantage, but I'm not sure. If I did do that, could I still run xposed?
Btw, RW, I tried using your idea, but when I was attempting to do the emergency Firmware Recovery, it asked for a computer code...??? So, that method doesn't seem to be a good route for me, but thanks for the tip!
You guys don't know how happy I am to have you come to the rescue! I've been using an old iPhone 4 for calls, etc.... during the day which I don't like at all! I'll be real glad to get back to AndroidLand. Thanks again!!!
straykat said:
Shapes Blue & Root Wizard,
Thanks much for your replies. Is it possible for me, having had 4.4.3 on phone, to go to 4.3 instead of 4.4.2? Seems some people think that's an advantage, but I'm not sure. If I did do that, could I still run xposed?
Btw, RW, I tried using your idea, but when I was attempting to do the emergency Firmware Recovery, it asked for a computer code...??? So, that method doesn't seem to be a good route for me, but thanks for the tip!
You guys don't know how happy I am to have you come to the rescue! I've been using an old iPhone 4 for calls, etc.... during the day which I don't like at all! I'll be real glad to get back to AndroidLand. Thanks again!!!
Click to expand...
Click to collapse
I'm 100% sure the last update on the VZW S3 was 4.4.2 NE1. As long as you can root the phone you should be able to run xposed without an issue
And no you cannot downgrade to anything other than what your currently on
Sent from my Nexus 5
---------- Post added at 06:51 PM ---------- Previous post was at 06:50 PM ----------
Root Wizard said:
Instead of odin, you could try using samasung kies 3 and use its emergencey firmware recovery tool which dl's and intalls the correct, latest firmware on your device.
What you do:
Install kies 3 on your computer.
Boot to odin mode on your phone.
Click on tools in kies.
Select emergency firmware recovery option.
Follow on screen directions.
Hope I helped!
Click to expand...
Click to collapse
Kies won't always work as it should
Sent from my Nexus 5
Still Not Up & Running...
ShapesBlue-
Believe-it-or-not, I still haven't been able to get my s3 back up & running. When I open Odin3 v 3.09 and try to flash the firmware 1534VRUDNE1 . . . . .tar.md5 , it doesn't successfully load to the s3. I've attached a screenshot showing the Odin screen. It show "All threads completed. (succeed 0 failed 1) - btw, when I click on the firmware file within Odin, nothing appears in the box to the right of the AP field; is that correct?
Thanks for any guidance you can provide.
straykat said:
ShapesBlue-
Believe-it-or-not, I still haven't been able to get my s3 back up & running. When I open Odin3 v 3.09 and try to flash the firmware 1534VRUDNE1 . . . . .tar.md5 , it doesn't successfully load to the s3. I've attached a screenshot showing the Odin screen. It show "All threads completed. (succeed 0 failed 1) - btw, when I click on the firmware file within Odin, nothing appears in the box to the right of the AP field; is that correct?
Thanks for any guidance you can provide.
Click to expand...
Click to collapse
I can't open it. It's in the newest word format docx. I personally haven't had to do this myself and it's been awhile since I've used Odin. Damn MS having to have all files in there own format
Edit: trying to download docs by Google and seeing if it opens
Sent from my Nexus 5
---------- Post added at 08:48 PM ---------- Previous post was at 08:40 PM ----------
straykat said:
ShapesBlue-
Believe-it-or-not, I still haven't been able to get my s3 back up & running. When I open Odin3 v 3.09 and try to flash the firmware 1534VRUDNE1 . . . . .tar.md5 , it doesn't successfully load to the s3. I've attached a screenshot showing the Odin screen. It show "All threads completed. (succeed 0 failed 1) - btw, when I click on the firmware file within Odin, nothing appears in the box to the right of the AP field; is that correct?
Thanks for any guidance you can provide.
Click to expand...
Click to collapse
Can you get into recovery?
I was able to open it once I downloaded docs by google. It's been so long since I used it though. I can't recall off hand how to use it to be honest
Sent from my Nexus 5