Hello, Iv'e looked at all the threads pertaining to this issue but haven't found any solution.
I use a rooted I717, running Padawan V2 ROM. Recovery is TWRP 2.6, the latest one. All the other issues that look like mine either use CWM or an older version of TWRP.
Issue: I'm unable to flash absolutely anything.Tried Stock ROM's, AOSP, AOKP ROM's. Tried downgrading TWRP to see if it works, but of course it doesn't flash.
Tried flashing using Odin, but that doesn't work either. Its never able to set up a connection. The only thing that does work is installing the same ROM all over again.
Hope someone can help me.
Illumin4tion said:
Hello, Iv'e looked at all the threads pertaining to this issue but haven't found any solution.
I use a rooted I717, running Padawan V2 ROM. Recovery is TWRP 2.6, the latest one. All the other issues that look like mine either use CWM or an older version of TWRP.
Issue: I'm unable to flash absolutely anything.Tried Stock ROM's, AOSP, AOKP ROM's. Tried downgrading TWRP to see if it works, but of course it doesn't flash.
Tried flashing using Odin, but that doesn't work either. Its never able to set up a connection. The only thing that does work is installing the same ROM all over again.
Hope someone can help me.
Click to expand...
Click to collapse
never able to set up connection?
connecting what to what?
all of it sounds odd, but this caught my eye. makes me think could this be a good starting point.
Odin > Phone
captemo said:
never able to set up connection?
connecting what to what?
all of it sounds odd, but this caught my eye. makes me think could this be a good starting point.
Click to expand...
Click to collapse
Odin (v3.07) to my phone. When flashing a stock ROM or anything for that matter, even though my phone is connected and in USB mode, it never gets past the 'Setting up connection...' step in Odin. I have a feeling this is a problem with the ROM, because transferring data to the SD card is a painful process. Most of the time the device 'stops responding' and I have to use Airdroid.
But of course this is a smaller part of the main issue.
In order to use Odin you need to be in download mode. When you're in download mode you're not using a rom so a rom can't be the problem. Try using Odin version 1.85 in download mode and flash twrp .tar file.
440bro said:
In order to use Odin you need to be in download mode. When you're in download mode you're not using a rom so a rom can't be the problem. Try using Odin version 1.85 in download mode and flash twrp .tar file.
Click to expand...
Click to collapse
Right! I totally forgot about that. Jeez
My apologies. Ill get back if the overall issue is or isn't solved.
Also, I already have TWRP 2.6, unless you're suggesting something else.
Thanks for reminding me about Odin mode. I got that working, flashed to stock, flashed TWRP 2.6.
Then followed proper procedures for PACman ROM and now it finally works.
Many thanks to both of you. Apologies for overseeing this simple process.
:good:
Illumin4tion said:
Thanks for reminding me about Odin mode. I got that working, flashed to stock, flashed TWRP 2.6.
Then followed proper procedures for PACman ROM and now it finally works.
Many thanks to both of you. Apologies for overseeing this simple process.
:good:
Click to expand...
Click to collapse
Good choice flashing PAC first. Padawan is nice, but it lags on my Note like mad
Padawan actually works like a charm for me. Super stable. Did you try changing things using the trickster mod?
Sent from my SAMSUNG-SGH-I717 using XDA Premium 4 mobile app
Related
So I rooted my Note a few weeks back using the non-counter advancing rooting method via odin. Worked flawlessly, and I'm rooted without issue. Tired of waiting for stock ICS to come out so I want to start flashing ROM's. Trying to install the newest CWM through Odin....well Odin doesn't recognize when the phone is connected. Tried 2 different windows 7 VM's and one W7 machine. I flashed via one of the VM's and it worked fine. It's not working on any machine that I have. I also have a mac book pro, but no idea if there is a apple Odin. What do I do? Don't have the android APK and really don't wanna go that route through ADB.
Can I just reboot into recovery and 'install via sd' or whatever the selection is, navigate to CWM touch recovery zip and install? or will that potentially do some serious damage?
Also if it's available on the CWM website as a DL why isn't it an option through the app to install? Would make my life WORLDS easier at this point.
A rooted phone would not interfere with Odin, completely unrelated. Perhaps your cable is bad, or you are installing the wrong drivers.
That said, once you have CWM on your phone, there should be no reason to use odin again. The updates for CWM are flashable via CWM. Most every single ROM is flashable via CWM. I can't really tell from your description if you were successful installing a custom recovery yet.
jpeg42 said:
A rooted phone would not interfere with Odin, completely unrelated. Perhaps your cable is bad, or you are installing the wrong drivers.
That said, once you have CWM on your phone, there should be no reason to use odin again. The updates for CWM are flashable via CWM. Most every single ROM is flashable via CWM. I can't really tell from your description if you were successful installing a custom recovery yet.
Click to expand...
Click to collapse
Trying to install a custom recovery. Sorry may not have made that clear in my rant. I've tried a couple different cables, and same luck. I DLed the CWM app from the Google Play, but have not installed a custom recovery. Trying to get CWM touch installed. Galaxy Note isn't an option when I try and install a custom recovery(CWM Touch Recovery...or hell any CWM recovery Note isn't an avialable model) via CWM.
So the options I've found so far are: Install custom recovery(CWM) via Odin, or install via ADB using android APK.
Are there other options to installing CWM recovery?
Sorry kind of a newb to all of this. I had a Dell Streak before this as my first android and it was a PITA to install Custom ROM's and root that I didn't mess with it much. Did root it and managed to soft brick my phone and bring her back to life. lol Then figured it was too much a pain to deal with.
ROM manager does not support our phone. I wouldn't use that app for now. So you're booting into download mode and Odin doesn't see your phone? I'm assuming you're in download mode?
froidroid said:
ROM manager does not support our phone. I wouldn't use that app for now. So you're booting into download mode and Odin doesn't see your phone? I'm assuming you're in download mode?
Click to expand...
Click to collapse
This...if not restart everything from scratch. Uninstall the drivers and re-install them again and restart Odin. Also make sure you are using the latest version of Odin.
froidroid said:
ROM manager does not support our phone. I wouldn't use that app for now. So you're booting into download mode and Odin doesn't see your phone? I'm assuming you're in download mode?
Click to expand...
Click to collapse
Correct isn't recognized in DL mode. The phone is recognized just fine when I plug it in regularly. Can transfer back and forth all day long.
The ICS ROM I wanna try uses CWM recovery to install. So trying to get everything to line up as to not end up with a brick. lol
babymatteo said:
This...if not restart everything from scratch. Uninstall the drivers and re-install them again and restart Odin. Also make sure you are using the latest version of Odin.
Click to expand...
Click to collapse
Believe I've done that before, but will try again. Latest version of Odin higher than 1.8.5 or something like that? If so that's what I'm using.
ROM manager does not support our phone. I wouldn't use that app for now. So you're booting into download mode and Odin doesn't see your phone? I'm assuming you're in download mode?
darkion2411 said:
ROM manager does not support our phone. I wouldn't use that app for now. So you're booting into download mode and Odin doesn't see your phone? I'm assuming you're in download mode?
Click to expand...
Click to collapse
Not sure what's going on with XDA, but my reply didn't post. So here goes: Yes that is correct I would boot into DL mode and odin didn't see my phone.
So I opened one of my VM's( the one previously used to root) uninstalled/reinstalled the drivers and voila odin sees my phone again. CWM touch recovery installed. Now off to flash Team Perfections ICS. Only chose them as they have a step by step video of installation and it seems stupid easy. Also seems to be the most stable from reading. Could be wrong. I'll try it out and wait for official CM9.
Have you tried using a different PC. I remeber my desktop wouldnt let me odin all the sudden one day. I tried my laptop worked no problem. using a VM sounds sketchy id be afraid there were too many facets or some risk of data corruption on its way. That may be incorrect but data > virtual hardware > hardware > phone. just too much for me -_-
Wing_Zero_Custom said:
Have you tried using a different PC. I remeber my desktop wouldnt let me odin all the sudden one day. I tried my laptop worked no problem. using a VM sounds sketchy id be afraid there were too many facets or some risk of data corruption on its way. That may be incorrect but data > virtual hardware > hardware > phone. just too much for me -_-
Click to expand...
Click to collapse
I tried my physical windows machine and it wouldn't even install the drivers. Failed every time regardless what I did.
I got the VM to work fine. CWM recovery touch is installed now.
sukemecuke said:
Not sure what's going on with XDA, but my reply didn't post. So here goes: Yes that is correct I would boot into DL mode and odin didn't see my phone.
So I opened one of my VM's( the one previously used to root) uninstalled/reinstalled the drivers and voila odin sees my phone again. CWM touch recovery installed. Now off to flash Team Perfections ICS. Only chose them as they have a step by step video of installation and it seems stupid easy. Also seems to be the most stable from reading. Could be wrong. I'll try it out and wait for official CM9.
Click to expand...
Click to collapse
All roms are that easy to flash once you have cwm, it's just booting into recovery, wiping, and flashing.
Try em all and see which one works best fir you
studacris said:
All roms are that easy to flash once you have cwm, it's just booting into recovery, wiping, and flashing.
Try em all and see which one works best fir you
Click to expand...
Click to collapse
I hear ya. Just when I start reading about some ROM's they say: oh and you need to flash this, this and this or else your phone will blow up and likely kill your whole family.
Being somewhat new to the flashing business just flashing ONE zip file is enough for me. Yet alone a bunch of other things. Just starts to confuse me with the multiple flashes......do I install all the same( as far as "flashing" goes)? Just boot into recovery navigate to file...double click and it'll do it's thing? If so I suppose that's not all that difficult. I like the one and done approach though. lol
Yup.
If there are multiple zips, flash them all like the main ROM.
Sweet! Flashed the Objection ICS. Like it so far. Seems like the modem is kinda all over the map for lte speeds.
Sent from my SAMSUNG-SGH-I717 using XDA
Hello Sirs,
Today I was about to flash the long awaited CM9-RC1 on my Samsung Galaxy S2 device with ROM Manager. After downloading it with Rom Manager I checked the three options:
Wipe Factory/Reset
Wipe Dalvik
Backup Device
Phone reboots and screen turns black. I waited for a good 15 minutes yet nothing happens. I popped the battery out and tried to fire it up again but now it wont start properly. It will be detected by computer as a "Unrecognized Device" only. The phone shows the Samsung logo + the flashcounter warning I assume? (Yellow triangle with exclamation mark.).
I cant access recovery-mode (clockworkmod) the only thing I am able to access is "Downloading Mode" but the device remains "Unrecognized Device" by computer. I did a little research about this problem - I only found some tips on changing cables/clean usb-port. None of which worked out to any advantage. I cant access the phone with adb either, and USB Debugging is not enabled as far as I know.
Odin nor Heimdall wont recognize the phone.
Downloading Mode
Code:
ODIN MODE
PRODUCT NAME: GT-i9100
CUSTOM BINARY DOWNLOAD: YES (2 Counts)
CURRENT BINARY: CUSTOM
Previously installed on the phone was 20120624-CM9-NIGHTLY along with Siyah Kernel SGS2 v3.3.2.
Worth to mention is that this happened to two phones at the same time. My brother also flashed his today and got the same result. Also with Siyah kernel as mentioned above.
I've tried 4 different USB-cables, and two different Windows 7 computer. Also I've reinstalled one of the computers to try a little more. No success.
This tells me that there is something with the Siyah kernel that borks the phone somehow. Yet it seems possible to fix it since I can access the "Downloading Mode". Dont you think? Anyone with similiar issues and maybe have a solution for this?
And if there is no software solution to this is it possible that a USB-JIG would sort this out?
Sincerely,
Your problem is likely rom manager instead of siyah kernel or otherwise. Rom Manager does not work properly on our phone and is known to cause problems when installing things with it. Did you install drivers with the other computers you tried?
Went through this today too. My fault for using Siyah
Don't freak out, just grab Odin 1.85, and flash the noob-proof build available in the Discussion thread from Download Mode.
Your data will be wiped btw. A safer way would be to flash the Recovery via Odin, and once in recovery, reflash CM9.
The lesson of the story is to not use Siyah, as it's not supported under CM9
Nushio said:
The lesson of the story is to not use Siyah, as it's not supported under CM9
Click to expand...
Click to collapse
That's not true. There's a whole thread full of people using Siyah and CM9 here.
Nushio said:
Went through this today too. My fault for using Siyah
Don't freak out, just grab Odin 1.85, and flash the noob-proof build available in the Discussion thread from Download Mode.
Your data will be wiped btw. A safer way would be to flash the Recovery via Odin, and once in recovery, reflash CM9.
The lesson of the story is to not use Siyah, as it's not supported under CM9
Click to expand...
Click to collapse
Well I am kinda freaking out since the device keeps showing up as "Unrecognized Device"! So I am not able to flash anything since it doesnt show up anywhere. I cant do anything to touch the phones software. Its just b0rked I guess.
I actually have the same problem with a S2 LTE which suffered from the same symptoms as stated above. Im starting to suspect maybe a crappy USB cable is the underlying reason for this, causing the usbport on the phone to fry or something.
Did you install drivers with the other computers you tried? Yes sir I installed the proper drivers there aswell.
I tried flashing the latest RC of cm9 and it went well even though i have siyah as the kernel. You shouldn't have flashed through rom manager. I flashed it through recovery
Sent from my GT-I9100 using xda premium
ephraim033 said:
I tried flashing the latest RC of cm9 and it went well even though i have siyah as the kernel. You shouldn't have flashed through rom manager. I flashed it through recovery
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
I hate ROM Manager. Is some app that I will never trust. The only purpose of ROM Manager: money, and placebo [you think it's the easiest way to flash stuff]. Can't find out why they put this in the ROM. At least they could make some OTA download. What is the Software update for at settings? Don't know...
ROM manager is crap. Never use it. That is what caused the issue. I am using CM9 based ROM with Siyah without any problem.
marcellocord said:
I hate ROM Manager. Is some app that I will never trust. The only purpose of ROM Manager: money, and placebo [you think it's the easiest way to flash stuff]. Can't find out why they put this in the ROM. At least they could make some OTA download. What is the Software update for at settings? Don't know...
Click to expand...
Click to collapse
ambar_hitman said:
ROM manager is crap. Never use it. That is what caused the issue. I am using CM9 based ROM with Siyah without any problem.
Click to expand...
Click to collapse
So what are you suggesting I should use instead? I'm hoping to return
the phone in topic when ive jigged it and demand a new one since there is still warranty hehe.
Don't use Rom Manager with kernels which have CWM/CWRecovery I.E. Siyah, CWM is more than capable of doing all the flashing/backups/restores/etc you need. If you end up using CM9 & Siyah again, make sure you freeze Rom Manager with TI or similar.
goopen said:
So what are you suggesting I should use instead ?
Click to expand...
Click to collapse
MistahBungle said:
Don't use Rom Manager with kernels which have CWM/CWRecovery I.E. Siyah, CWM is more than capable of doing all the flashing/backups/restores/etc you need. If you end up using CM9 & Siyah again, make sure you freeze Rom Manager with TI or similar.
Click to expand...
Click to collapse
So the weirdest of things just happened. I left the phone discharging with the download mode active during the night. Today I bought a new phone (4100SEK /$585USD) and I thought maybe, just maybe it works now. I put the device in Download Mode and now popped it into the computer with the same cable as yesterday. And there it was "Device installed successfully!". Holy ****. Fired up Odin v1.85 and just pushed that damn recovery image onto the phone and bam! Rebooting, works like a charm. Now thats just f**king unbeliveable. But of course this wouldnt have happened if I DIDNT buy a totally new phone. The irony.
Moderator you may close this thread and save it for future reading.
Sincerely,
Another satisfied customer
Noob here,
Originally i was trying just to root my phone. I didn't want to flash any roms or anything like that just root it so i can get rid of the bloatware, and so after much reading i found that the only way to do it on ICS required a method that might have a bricking bug. Well i went for it anyway, did it successfully. All was well, saw the superuser icon, purchased mobile odin pro did the whole bit. It seemed to be working great. Then i had to immediately change kernels since the stock kernel seems to be the culprit with the whole bricking bug situation. Alrighty, well i went and did that sort of successfully? I chose Siyah since thats what most people in the thread chose. Flashed it with mobile odin pro then it got stuck on boot. After more research i figured out where i went wrong, apparently the first link to the siyah kernel was a CWM/jb kernel or some such situation. I apparently should have downloaded the one further down. My fault for being so quick to try to get it all over with. Now my issue now is i'm stuck at boot, Is it possible to somehow flash the zimage of the proper kernel from the recovery menu? Or would i need to flash a tar file or zip file? would that still work if i used a brand new sdcard or would it have had to have been installed previously? Any help or guidance would be very appreciated. Thank you!
cnidaria said:
Noob here,
Originally i was trying just to root my phone. I didn't want to flash any roms or anything like that just root it so i can get rid of the bloatware, and so after much reading i found that the only way to do it on ICS required a method that might have a bricking bug. Well i went for it anyway, did it successfully. All was well, saw the superuser icon, purchased mobile odin pro did the whole bit. It seemed to be working great. Then i had to immediately change kernels since the stock kernel seems to be the culprit with the whole bricking bug situation. Alrighty, well i went and did that sort of successfully? I chose Siyah since thats what most people in the thread chose. Flashed it with mobile odin pro then it got stuck on boot. After more research i figured out where i went wrong, apparently the first link to the siyah kernel was a CWM/jb kernel or some such situation. I apparently should have downloaded the one further down. My fault for being so quick to try to get it all over with. Now my issue now is i'm stuck at boot, Is it possible to somehow flash the zimage of the proper kernel from the recovery menu? Or would i need to flash a tar file or zip file? would that still work if i used a brand new sdcard or would it have had to have been installed previously? Any help or guidance would be very appreciated. Thank you!
Click to expand...
Click to collapse
I don't understand, what the hell did you flash, more information is needed.
Sent from my Xoom using Tapatalk 2
cnidaria said:
Noob here,
Originally i was trying just to root my phone. I didn't want to flash any roms or anything like that just root it so i can get rid of the bloatware, and so after much reading i found that the only way to do it on ICS required a method that might have a bricking bug. Well i went for it anyway, did it successfully. All was well, saw the superuser icon, purchased mobile odin pro did the whole bit. It seemed to be working great. Then i had to immediately change kernels since the stock kernel seems to be the culprit with the whole bricking bug situation. Alrighty, well i went and did that sort of successfully? I chose Siyah since thats what most people in the thread chose. Flashed it with mobile odin pro then it got stuck on boot. After more research i figured out where i went wrong, apparently the first link to the siyah kernel was a CWM/jb kernel or some such situation. I apparently should have downloaded the one further down. My fault for being so quick to try to get it all over with. Now my issue now is i'm stuck at boot, Is it possible to somehow flash the zimage of the proper kernel from the recovery menu? Or would i need to flash a tar file or zip file? would that still work if i used a brand new sdcard or would it have had to have been installed previously? Any help or guidance would be very appreciated. Thank you!
Click to expand...
Click to collapse
Good job doing all the reading you did. Sorry this happened If the jellybean kernel flashed and went to reboot you should have CWM recovery!!! If you download the 4.3.3 ICS no mic swap kernel Yes you can transfer the kernel to a microSD card from your PC with the adapter then insert it in the phone and then flash it in CWM install zip from Sdcard. You can transfer it from your PC to your phone using CWM, and flash the .zip I have never done this so I cant give you detailed info how to do it but I hope some one cool will help you with that if you need it. All you need to do is flash the ICS kernel in CWM and you will be good to go!! Worse case flash the stock rooted ICS package again in Odin and it will flash the stock ICS kernel with the firmware again then flash the right ICS Kernel in Mobile Odin .... GL
http://www.mediafire.com/?39q3t5yjsgj66cb Link to the right ICS kernel.
Nick281051 said:
I don't understand, what the hell did you flash, more information is needed.
Sent from my Xoom using Tapatalk 2
Click to expand...
Click to collapse
He rooted, used mobile odin, flashed mali jb kernel got into bootloop. OP just hold volume up, down and power until CWM pops up and you can mount storage and flash another kernel from there.
122ninjas said:
He rooted, used mobile odin, flashed mali jb kernel got into bootloop. OP just hold volume up, down and power until CWM pops up and you can mount storage and flash another kernel from there.
Click to expand...
Click to collapse
This is exactly what happened. Thank you! will try this next
Thank you! worked great
So, I was on 4.1.2 (running CM 11), and I downloaded the toltevzw_mj9_official_firmware1.tar.md5 and Odin 3.07.
I loaded the toltevzw_mj9_official_firmware1.tar.md5 into the PDA section of ODIN, and booted into download mode.
I ran Odin, and it seemed to work--restarted, Odin said it was successful, but now I have no cellular service and my Baseband Version is "unknown".
I've tried this multiple times, with different computers and different cords. I even flashed back to stock to get the modem back, then tried again. Same result.
Am I using ODIN wrong? Can anyone help me? Please? I have searched these forums, but every thread I found was unhelpful.
Thank you.
beans3660 said:
So, I was on 4.1.2 (running CM 11), and I downloaded the toltevzw_mj9_official_firmware1.tar.md5 and Odin 3.07.
I loaded the toltevzw_mj9_official_firmware1.tar.md5 into the PDA section of ODIN, and booted into download mode.
I ran Odin, and it seemed to work--restarted, Odin said it was successful, but now I have no cellular service and my Baseband Version is "unknown".
I've tried this multiple times, with different computers and different cords. I even flashed back to stock to get the modem back, then tried again. Same result.
Am I using ODIN wrong? Can anyone help me? Please? I have searched these forums, but every thread I found was unhelpful.
Thank you.
Click to expand...
Click to collapse
What I have found to help me and not run into this issue is flash back to stock, and re-root using the causal tool. Then I would install the lastest CWM or TWRP, install 4.3TW rom, boot up, reboot back into download mode, run odin package of the firmware (make sure you have a good md5, a bad download can affect it accepting the upgraded firmware), then wipe data,cache, dalvik and reboot. Then once rebooted confirm your modem was accepted and working, then get a GPS lock, then upgrade to CM11 if thats what you prefer.
bigmike35 said:
What I have found to help me and not run into this issue is flash back to stock, and re-root using the causal tool. Then I would install the lastest CWM or TWRP, install 4.3TW rom, boot up, reboot back into download mode, run odin package of the firmware (make sure you have a good md5, a bad download can affect it accepting the upgraded firmware), then wipe data,cache, dalvik and reboot. Then once rebooted confirm your modem was accepted and working, then get a GPS lock, then upgrade to CM11 if thats what you prefer.
Click to expand...
Click to collapse
So I did most of this, installed Alliance Rom. Now, ODIN won't recognize my device when it is in download mode. It will recognize it when I boot up normally, however. Yet, as soon as I boot into download mode, nothing.
Why is this such a pain in the ass for me? I haven't seen anyone have this much trouble.
beans3660 said:
So I did most of this, installed Alliance Rom. Now, ODIN won't recognize my device when it is in download mode. It will recognize it when I boot up normally, however. Yet, as soon as I boot into download mode, nothing.
Why is this such a pain in the ass for me? I haven't seen anyone have this much trouble.
Click to expand...
Click to collapse
That is a common problem, no worries man.
You need to go into device manager and delete/uninstall the casual/Samsung driver. Look under android development, then droid style, a sticky thread which shows you to delete driver. When you do that, that should do the trick for you!
Thank you bigmike35, so much. Everything you said worked.
To anyone else with this problem, try installing a 4.3 rom first before the mJ9. I wasted hours and hours by not doing this.
beans3660 said:
Thank you bigmike35, so much. Everything you said worked.
To anyone else with this problem, try installing a 4.3 rom first before the mJ9. I wasted hours and hours by not doing this.
Click to expand...
Click to collapse
Can you post a Link to this 4.3 Rom? or even the Rom name? thanks
"Firmware Upgrade Encountered an Issue" "Device not responding" Samsung Kies
I tried to flash an Android 5.0 ROM earlier, and my phone was only booting to the stock recovery (Safestrap was installed but I did a factory reset). Now, if the phone was turned off by removing the battery, it won't turn on when I hold the power button, or attempt to go into download/recovery mode. Nothing happens. If I plug it in, I can use whatever button combinations as normal. However, I don't think I can get to recovery mode. Both volume down/power and volume down/power/home enter download mode to the phone. I tried to flash a stock ROM in Odin, but it failed. Otherwise, it shows a screen that says " Firmware Upgrade encountered an issue. Please select recovery mode in kies and try again" And when I open kies, it just says "connecting" for an extremely long time until it eventually says "Device not responding" and I can't do anything. What do I have to do to fix this? I can't find anything for this phone that has had this problem or knows how to fix it. I've tried a few different things so far but flashing nothing in odin has worked. Any help is appreciated, thanks in advance.
Bumping for others to hopefully see... I've still made no progress and am in the same situation and simply can't find what I need to do.
What build were you on before you started? What file are you trying to flash with Odin?
Jmick363 said:
I tried to flash an Android 5.0 ROM earlier, and my phone was only booting to the stock recovery (Safestrap was installed but I did a factory reset). Now, if the phone was turned off by removing the battery, it won't turn on when I hold the power button, or attempt to go into download/recovery mode. Nothing happens. If I plug it in, I can use whatever button combinations as normal. However, I don't think I can get to recovery mode. Both volume down/power and volume down/power/home enter download mode to the phone. I tried to flash a stock ROM in Odin, but it failed. Otherwise, it shows a screen that says " Firmware Upgrade encountered an issue. Please select recovery mode in kies and try again" And when I open kies, it just says "connecting" for an extremely long time until it eventually says "Device not responding" and I can't do anything. What do I have to do to fix this? I can't find anything for this phone that has had this problem or knows how to fix it. I've tried a few different things so far but flashing nothing in odin has worked. Any help is appreciated, thanks in advance.
Click to expand...
Click to collapse
Here's the issue: since you have safestrap installed that means you're on the new bootloader. We cannot install anything other than TW based roms from nothing newer than nc5 base. If you can get into download mode, you'll need to flash the full wipe nc5 tar file through Odin. That will get you back on stock and you can re-root from there.
Hightower24 said:
Here's the issue: since you have safestrap installed that means you're on the new bootloader. We cannot install anything other than TW based roms from nothing newer than nc5 base. If you can get into download mode, you'll need to flash the full wipe nc5 tar file through Odin. That will get you back on stock and you can re-root from there.
Click to expand...
Click to collapse
Crap. You're right. I completely forgot about that last night. I was getting frustrated with Hyperdrive because when I was trying to install version 20, the WiFi would never work no matter which modules.zip I flashed.
I got fed up and just wanted to flash something else and I did this without even thinking about it... I can get the phone into download mode, but when I try to flash this in odin, it fails.
I saw someone with the same screen as me with a Note 2 and someone said something about flashing a PIT file or something like that? I think I'm going to look into that next, hopefully I can find some useful links.
riker147 said:
What build were you on before you started? What file are you trying to flash with Odin?
Click to expand...
Click to collapse
Sorry I didn't see this post at first. The file I'm using in Odin is mentioned in the above post. Before I had done anything, I was successfully using Hyperdrive 17.something. I did a factory reset, flashed the Hyperdrive 20 rom, flashed the modules.zip (I used like 3 or 4 different ones and none of them got WiFi to work) and rebooted and let the phone sit for 10 minutes, and when I would try to toggle WiFi, it wouldn't work. To make things worse, every time, when I rebooted, SafeStrap wouldn't load. So I had to go back to the ROM and install Towelroot and root the phone again, then install safestrap and install the recovery again and then I could boot to it. But I could never get the WiFi to work a single time.
Jmick363 said:
Sorry I didn't see this post at first. The file I'm using in Odin is mentioned in the above post. Before I had done anything, I was successfully using Hyperdrive 17.something. I did a factory reset, flashed the Hyperdrive 20 rom, flashed the modules.zip (I used like 3 or 4 different ones and none of them got WiFi to work) and rebooted and let the phone sit for 10 minutes, and when I would try to toggle WiFi, it wouldn't work. To make things worse, every time, when I rebooted, SafeStrap wouldn't load. So I had to go back to the ROM and install Towelroot and root the phone again, then install safestrap and install the recovery again and then I could boot to it. But I could never get the WiFi to work a single time.
Click to expand...
Click to collapse
Use this wifi fix module. It works best for me:
https://www.androidfilehost.com/?fid=23487008491963696
Hightower24 said:
Use this wifi fix module. It works best for me:
https://www.androidfilehost.com/?fid=23487008491963696
Click to expand...
Click to collapse
Thanks for this, but right now I need to be more concerned with actually getting to Safestrap... or stock touchwiz for that matter. Hopefully this will work if I manage to fix the phone.
Jmick363 said:
Thanks for this, but right now I need to be more concerned with actually getting to Safestrap... or stock touchwiz for that matter. Hopefully this will work if I manage to fix the phone.
Click to expand...
Click to collapse
My bad. Here's a link to the tar files. I suggest using the full wipe nc5:
http://forum.xda-developers.com/showthread.php?t=2735172
Hightower24 said:
My bad. Here's a link to the tar files. I suggest using the full wipe nc5:
http://forum.xda-developers.com/showthread.php?t=2735172
Click to expand...
Click to collapse
Using the Full Wipe method on that link, I was able to resolve the problem and at least get back to a working phone. From here I'll use towelroot to root and install safestrap and then install hyperdrive 20 with those modules you linked. To be more specific for anyone reading years from now with the same problem as me, I used odin 1.85 (though many versions work) with the pit file provided from that link with "re=partition, auto reboot and f. reset time" checked in the options. At first, I was having some trouble, but I think it was because the phone had low battery. I plugged it in for a bit, booted it up, and am setting it up right now. Thanks for the help everyone, it's much appreciated. I very much hope that the modules you linked work for me, because if they don't, I have no idea what ROM to use.
I was reading a thread last night where someone listed all of the ROMS working with SafeStrap, but it was from like 2 years ago and almost all of the ROMs had been abandoned.... Is there a more updated list of options? Or just something to look for to make sure a ROM will work right away?
Jmick363 said:
Using the Full Wipe method on that link, I was able to resolve the problem and at least get back to a working phone. From here I'll use towelroot to root and install safestrap and then install hyperdrive 20 with those modules you linked. To be more specific for anyone reading years from now with the same problem as me, I used odin 1.85 (though many versions work) with the pit file provided from that link with "re=partition, auto reboot and f. reset time" checked in the options. At first, I was having some trouble, but I think it was because the phone had low battery. I plugged it in for a bit, booted it up, and am setting it up right now. Thanks for the help everyone, it's much appreciated. I very much hope that the modules you linked work for me, because if they don't, I have no idea what ROM to use.
I was reading a thread last night where someone listed all of the ROMS working with SafeStrap, but it was from like 2 years ago and almost all of the ROMs had been abandoned.... Is there a more updated list of options? Or just something to look for to make sure a ROM will work right away?
Click to expand...
Click to collapse
Hyperdrive and echoerom seem to be the most talked about. I'm running echoe v39.1
Hightower24 said:
Hyperdrive and echoerom seem to be the most talked about. I'm running echoe v39.1
Click to expand...
Click to collapse
So right now things aren't going as smoothly as I would've hoped.... The first time I flashed Hyperdrive and then that modules zip you linked, and the phone got stuck on the Samsung custom screen in some sort of loop. I reset it with odin and just the PDA from the link from before, and I then installed towelroot and safestrap again then flashed hyperdrive and modules and now I'm stuck on the hyperdrive red screen... It's just the boot animation and nothing else. When I take out the battery, the power button does nothing if the phone is not plugged in. When I plug the phone in and hold down the power button, it just shows an empty battery with a loading icon in the middle. I can't do anything else.... I'm going to reset it again now and maybe try installing this echoe rom.... Are you talking about this?
Jmick363 said:
I'm going to reset it again now and maybe try installing this echoe rom.... Are you talking about this?
Click to expand...
Click to collapse
Hightower24 said:
Hyperdrive and echoerom seem to be the most talked about. I'm running echoe v39.1
Click to expand...
Click to collapse
With EchoeRom, where do I find the signal bar fix? Is the wifi fix the thing you linked already? or is it separate from modules zip?
Jmick363 said:
With EchoeRom, where do I find the signal bar fix? Is the wifi fix the thing you linked already? or is it separate from modules zip?
Click to expand...
Click to collapse
Sorry! I had started this reply earlier in the morning then got busy with work. The link for the signal bar fix is in the OP from the forum you found by jds. It's down by the link for v26. I sent you the wifi fix that works for me. If you're going to use v39.1, you will need jrkruse's nk2 patch found here:
http://forum.xda-developers.com/showthread.php?t=2674280
The echoe site is here:
http://echoerom.com/roms/echoefull/s4/i9505/
Flash in this order:
Rom
Nk2 patch (not needed for v29/29.1)
Signal bar fix
WiFi fix
Updated supersu.zip (optional)
Be sure to verify the md5 of the downloads. Good luck!
Hightower24 said:
Sorry! I had started this reply earlier in the morning then got busy with work. The link for the signal bar fix is in the OP from the forum you found by jds. It's down by the link for v26. I sent you the wifi fix that works for me. If you're going to use v39.1, you will need jrkruse's nk2 patch found here:
http://forum.xda-developers.com/showthread.php?t=2674280
The echoe site is here:
http://echoerom.com/roms/echoefull/s4/i9505/
Flash in this order:
Rom
Nk2 patch (not needed for v29/29.1)
Signal bar fix
WiFi fix
Updated supersu.zip (optional)
Be sure to verify the md5 of the downloads. Good luck!
Click to expand...
Click to collapse
No need to apologize!! Your job isn't to monitor me, and I can't thank you enough for all the help. I'm going to give this a shot at some point today, hopefully it'll work. I'll comment back in the thread whatever happens... As you can probably tell, I typically have horrible luck with these things.
So I have had the same issue as the OP after trying to flash to a 5.0 ROM, but my issue is still ongoing, as when I try to flash the stock ROM from this link I get the error that it failed in Odin.
madhavok09 said:
So I have had the same issue as the OP after trying to flash to a 5.0 ROM, but my issue is still ongoing, as when I try to flash the stock ROM from this link I get the error that it failed in Odin.
Click to expand...
Click to collapse
Are you flashing the full wipe? Good download? Check MD5? Using the cable that came with the phone? Try a different USB port?
Sent from my NCC-1701 using Tapatalk.
riker147 said:
Are you flashing the full wipe? Good download? Check MD5? Using the cable that came with the phone? Try a different USB port?
Sent from my NCC-1701 using Tapatalk.
Click to expand...
Click to collapse
Well the OP said he did the wipe with that link I listed, and I would assume it's a good link. I am flashing the full wipe with the PIT file, using the cable that came with the phone, and I have tried using a different USB port. I have tried 3 different MD5 files as well and still have had no luck.
Edit (2:13 PM Eastern): Had the wrong file after some digging, and got the NC5 instead of the MK2. Phone is booting normally. Thanks for the help.