Related
Blur_Version.6.16.203.XT912.Verizon.en.US)Blur_Version.6.12.181.XT912.Verizon.en.US *
some notes2!SD card package 6.12.181-6.16.2038€@€J...P ZSverizon/spyder_vzw/cdma_spyder:2.3.6/6.5.1-167_DHD-14_M3-8/120308:user/release-keys
This is what was found over at droidrzr, there was another leak 6.14.79.XT912 but the one I'm talking about was last modified yesterday and it comes with the Color for Facebook app preinstalled & last but not least its ANDROID 4.0.4. Discuss away.
EDIT: This was confirmed to not be able to downgrade you, not even to gingerbread. But people were saying temple run works perfectly. Link is at the bottom but BE WARNED, NOT FASTBOOTABLE OR DOWNGRADEABLE. FLASH AT YOUR OWN RISK.
EDIT 2: So this is a New Leak 6.16.204 found by fellow member mattlgroff. Still 4.0.4 and still not FASTBOOTABLE OR DOWNGRADEABLE.
http://rombot.droidhive.com/ROMs/spyder/moto/ICS-LEAK-6.16.203/
http://rombot.droidhive.com/ROMs/spyder/moto/ICS-LEAK-6.16.204/
Sent from my Galaxy Nexus using Tapatalk 2
Really looks like Verizon maybe working on a 21st release. Or at least moving forward.
via Razr MAXX
anthony2558 said:
Really looks like Verizon maybe working on a 21st release. Or at least moving forward.
via Razr MAXX
Click to expand...
Click to collapse
This is kind of on the edge but I'm thinking this might be the OTA just because it says release keys and is packed with Color for Facebook.
Sent from my Galaxy Nexus using Tapatalk 2
link: http://rombot.droidhive.com/ROMs/spyder/moto/ics leak 203/
flash over 181...DONT KNOW IF ITS FASTBOOTABLE BACK TO GB
FLASH AT YOUR OWN RISK
ezcats said:
link: http://rombot.droidhive.com/ROMs/spyder/moto/ics leak 203/
flash over 181...DONT KNOW IF ITS FASTBOOTABLE BACK TO GB
FLASH AT YOUR OWN RISK
Click to expand...
Click to collapse
OK I didn't know where the link was but this is not fastbootable people so download if you like but DO NOT FLASH. I repeat DO NOT FLASH. And ezcats thanks for the link.
Sent from my Galaxy Nexus using Tapatalk 2
Interesting
wait - so this is 4.04 - has anybody at all installed this? Nobody confirmed this is not fastbootable?
mikeymax said:
wait - so this is 4.04 - has anybody at all installed this? Nobody confirmed this is not fastbootable?
Click to expand...
Click to collapse
No confirmation if its fastbootable, the devs are checking it out. And yes this is 4.0.4
Sent from my Galaxy Nexus using Tapatalk 2
Damn. I been on the last 84 leak. What's the odds of me being able to run this zip over the leak I am on, thru stock recovery, and it actually updating?
stkiswr said:
Damn. I been on the last 84 leak. What's the odds of me being able to run this zip over the leak I am on, thru stock recovery, and it actually updating?
Click to expand...
Click to collapse
0. You need to be running .181 or it'll fail right out.
Sent from my Galaxy Nexus using XDA
times_infinity said:
0. You need to be running .181 or it'll fail right out.
Sent from my Galaxy Nexus using XDA
Click to expand...
Click to collapse
That's weak.
Does this take a RAZR off the upgrade path, and can I flash stock recovery? Voodoo protect root?
Sent from my DROID RAZR using XDA
Would love to see a screenshot with 4.04 as i'm sure everyone else
Sent from my DROID RAZR using XDA
I'm pretty sure at this point all ics leaks after 75 take you off the upgrade path. Being on 84 and not being able to go back to gingerbread is fine. But being in 84 and not being able to install this is not. If fastboot files are released then once the ota hits it looks like I will have to downgrade to 181 and accept newer version. I am really hoping one of our very talented devs can come up w a way to make it attempt to just update from 84 to this leak or an ota without the need to do all the other. Its clearly not easy due to how the process is setup to install from moto.
That's why I never jumped to ics when they leaked in the first place. Sorry to hear of your hassle
Sent from my DROID RAZR using XDA
hasbrobot said:
That's why I never jumped to ics when they leaked in the first place. Sorry to hear of your hassle
Sent from my DROID RAZR using XDA
Click to expand...
Click to collapse
I choose it. Its my fault. Not sad as 84 runs awesome. But I assumed I could update to newer. Not concerned about going backwards. Hopefully someone can come up w something. I have it downloaded and ready to roll in case
Link is broken now apparently...
The 4.0.4 leak has been confirmed to be unfastbootable back to GB. It will strand you like the .84/.85 leaks, taking you off the update path with no way to return. The 4.0.3 leak (.79), on the other hand, is fastbootable back to GB so it's safe to play with like the .75 leak.
All of this has been confirmed by the devs @ Droidrzr.com.
Sent from my DROID RAZR using Tapatalk 2
Link is not broken guys. And yes, there's an update .203 blur.
http://rombot.droidhive.com/ROMs/spyder/moto/
Edit: I've saved the file in case anything went wrong.
Cheers
Any screenshots yet?
Not yet, still waiting
Sent from my DROID RAZR using XDA
So been away fir awhile and I guess 4.4 is out. Can 4.4 be rooted without tripping knox
Sent from my SM-N900P using Xparent Purple Tapatalk 2
cherylbaker said:
So been away fir awhile and I guess 4.4 is out. Can 4.4 be rooted without tripping knox
Sent from my SM-N900P using Xparent Purple Tapatalk 2
Click to expand...
Click to collapse
No sir. If you're on KitKat, you're stuck. If you're on MJ4 but haven't made the jump, then you can. Check out the general forum for guidance. Thread title is self-explanatory.
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
No sir. If you're on KitKat, you're stuck. If you're on MJ4 but haven't made the jump, then you can. Check out the general forum for guidance. Thread title is self-explanatory.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Knew I shouldn't have taken the OTA to kitkat. That really stinks.
Sent from my SM-N900P using Tapatalk
micmars said:
No sir. If you're on KitKat, you're stuck. If you're on MJ4 but haven't made the jump, then you can. Check out the general forum for guidance. Thread title is self-explanatory.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Am I doing something wrong here? I'm on KK NAB with KK TWRP but was unable to flashing any kk rom. It keep on saying "usb not mount" then fail. Any advice would be appreciated.
K.0.0.L. said:
Am I doing something wrong here? I'm on KK NAB with KK TWRP but was unable to flashing any kk rom. It keep on saying "usb not mount" then fail. Any advice would be appreciated.
Click to expand...
Click to collapse
Reflash stock rom, reinstall TWRP, reflash rom.
Basically start over.
That happened to me about 2 weeks ago. Sucks, but that was my only out.
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
Reflash stock rom, reinstall TWRP, reflash rom.
Basically start over.
That happened to me about 2 weeks ago. Sucks, but that was my only out.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Alright, I'll try that when I get home from work.
micmars said:
Reflash stock rom, reinstall TWRP, reflash rom.
Basically start over.
That happened to me about 2 weeks ago. Sucks, but that was my only out.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
No luck at all.
K.0.0.L. said:
No luck at all.
Click to expand...
Click to collapse
Sorry to hear about this.
Have you tried doing this by wiping your internal memory, and checking your SD card for issues? There are a few whom have reported that restoring everything to out-of-the-box new got them back on their feet.
A nasty amount of work, but it could be an option. Having recovery with no way to use it seems awful.
Check Rwilco12 NAB one-click thread, last few posts, for the means another used to eliminate these types of errors.
Keep us apprised.
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
Sorry to hear about this.
Have you tried doing this by wiping your internal memory, and checking your SD card for issues? There are a few whom have reported that restoring everything to out-of-the-box new got them back on their feet.
A nasty amount of work, but it could be an option. Having recovery with no way to use it seems awful.
Check Rwilco12 NAB one-click thread, last few posts, for the means another used to eliminate these types of errors.
Keep us apprised.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I'll give it a shot.
micmars said:
Sorry to hear about this.
Have you tried doing this by wiping your internal memory, and checking your SD card for issues? There are a few whom have reported that restoring everything to out-of-the-box new got them back on their feet.
A nasty amount of work, but it could be an option. Having recovery with no way to use it seems awful.
Check Rwilco12 NAB one-click thread, last few posts, for the means another used to eliminate these types of errors.
Keep us apprised.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
I appreciated your support. I didn't notice that you are a moderator in here until I hit the "thanks" icon. Just an update, it's a no go for me. I have restored back to stock unroot then odin TWRP but still not able to flash any rom.
K.0.0.L. said:
I appreciated your support. I didn't notice that you are a moderator in here until I hit the "thanks" icon. Just an update, it's a no go for me. I have restored back to stock unroot then odin TWRP but still not able to flash any rom.
Click to expand...
Click to collapse
I'm not your moderator my man, but I am here to serve all, users and devs alike, and only at the will of those whom appointed me.
I just own the device, and love the fine folks here, and all that xda is.
Sent from my SM-N900P using Xparent BlueTapatalk 2
I can send messages and calls but I can't receive. I'm running cyanogen mod 11. This happened once before and I had to flash back to tw and then reflash cyanogen. It seems like I can't update my scms number (not sure if that's the exact acronym.) any way to fix without wiping and reflashing?
Sent from my SM-N900P using xda app-developers app
bump- Please help me guys.
BumpinPanda said:
bump- Please help me guys.
Click to expand...
Click to collapse
I think your answer resides in the OP, though I'm not too familiar with AOSP roms, I do know that a lot of updates have hit, and the firmware registers with the towers.
Likely have to update on TouchWiz to the latest.
Perhaps someone else that uses those roms can chime in.
Sent from my SM-N900P using Xparent BlueTapatalk 2
micmars said:
I think your answer resides in the OP, though I'm not too familiar with AOSP roms, I do know that a lot of updates have hit, and the firmware registers with the towers.
Likely have to update on TouchWiz to the latest.
Perhaps someone else that uses those roms can chime in.
Sent from my SM-N900P using Xparent BlueTapatalk 2
Click to expand...
Click to collapse
Thats what ive tried to do. I flashed stock unrooted and it did nothing. I dont know what else to do. Theres barely any documentation on this issue and barely anyone trys to help... Ive searched these forums and others for weeks.
Try This Thread...
BumpinPanda said:
Thats what ive tried to do. I flashed stock unrooted and it did nothing. I dont know what else to do. Theres barely any documentation on this issue and barely anyone trys to help... Ive searched these forums and others for weeks.
Click to expand...
Click to collapse
This thread should give you a starting-point. You may also try the AOSP threads. Remember, this is a starting point; I have no idea what base you were on prior to flashing your AOSP rom (MJ4, NAB, NC5), but this was someone using AOSP CM11 and started with MJ4. Please tread with caution.
Good luck!
micmars said:
This thread should give you a starting-point. You may also try the AOSP threads. Remember, this is a starting point; I have no idea what base you were on prior to flashing your AOSP rom (MJ4, NAB, NC5), but this was someone using AOSP CM11 and started with MJ4. Please tread with caution.
Good luck!
Click to expand...
Click to collapse
Is there any way I can figure out if it is MJ4 etc now? I can boot into touchwiz after installing from Samsung forum download.
BumpinPanda said:
Is there any way I can figure out if it is MJ4 etc now? I can boot into touchwiz after installing from Samsung forum download.
Click to expand...
Click to collapse
Look at your about device in settings
Sent from my SM-N900P using Xparent BlueTapatalk 2
So I've been having this issue ever since I upgraded to kitkat. I'll be messing with my phone normally for all day and then once in awhile when I lock it and and go to pull it back out or unlock it, the phone is turn off. I know it shuts off because I have to hold the power button and all of a sudden the Samsung Galaxy S4 screen pops up like it usually does from boot up. This is really frustrating and I don't know why it keeps doing this. It's not usally a daily thing but I'll happen once every 3 to 4 days and sometimes happens twice a day. Has anyone else had this issue or know any suggestions how to fix it??????? Any help would be greatly appreciated! !!! My s4 is the Mk2 version btw.
Sent from my SCH-I545 using Tapatalk
You're on KitKat but you're on MK2?
Sent from my SCH-I545 using Tapatalk
My S4 baseband version is the Mk2.
Sent from my SCH-I545 using Tapatalk
RECKLESS PAIN said:
My S4 baseband version is the Mk2.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
You're baseband version only represents the modem you're on. When people say they're "on MK2" or "on MDK" they mean the bootloader version. What method did you use to upgrade to 4.4? Are you on the leak, NC2 or the official update NC5?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Official OTA Update
Sent from my SCH-I545 using Tapatalk
joshm.1219 said:
You're baseband version only represents the modem you're on. When people say they're "on MK2" or "on MDK" they mean the bootloader version. What method did you use to upgrade to 4.4? Are you on the leak, NC2 or the official update NC5?
Sent from my SCH-I545 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Anyway I can fix.this issue? Still need help!!!((
Sent from my SCH-I545 using Tapatalk
RECKLESS PAIN said:
Anyway I can fix.this issue? Still need help!!!((
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Were you rooted or anything, or completely stock when you took the OTA? If you were completely stock, then the baseband should've updated to NC5 as well, so something went wrong with your update. Can you screenshot your about phone screen?
I wonder, if the modem didn't update with your OTA, then something might've went wrong with the boot.img/kernel as well, which is the most common culprit with this type of issue.
I'm going to say try a factory reset first and if the issue persists then you will need to use Odin to flash a fresh NC5 tar image.
joshm.1219 said:
Were you rooted or anything, or completely stock when you took the OTA? If you were completely stock, then the baseband should've updated to NC5 as well, so something went wrong with your update. Can you screenshot your about phone screen?
I wonder, if the modem didn't update with your OTA, then something might've went wrong with the boot.img/kernel as well, which is the most common culprit with this type of issue.
I'm going to say try a factory reset first and if the issue persists then you will need to use Odin to flash a fresh NC5 tar image.
Click to expand...
Click to collapse
Well I didn't realize on either updated it my baseband version changed from MK2 to NC5. So yeah it did change along with the OTA update. But see I DID have my phone rooted like 2 weeks before the OTA and decided I didn't want root on my S4 so I uninstalled, eveything. From SuperSU. To busybox. So when I took the update no I was not at the time rooted. But I'm thinking some old root filed are still on my phone causing it to do this random power off thing. So I don't know really what to do yet besides factory reset:C
Sent from my SCH-I545 using Tapatalk
RECKLESS PAIN said:
Well I didn't realize on either updated it my baseband version changed from MK2 to NC5. So yeah it did change along with the OTA update. But see I DID have my phone rooted like 2 weeks before the OTA and decided I didn't want root on my S4 so I uninstalled, eveything. From SuperSU. To busybox. So when I took the update no I was not at the time rooted. But I'm thinking some old root filed are still on my phone causing it to do this random power off thing. So I don't know really what to do yet besides factory reset:C
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Yeah, unfortunately that seems like the only option. You might want to wait for someone else to chime in with an idea, but personally I don't care about the data on my phone so I would factory reset.
joshm.1219 said:
Yeah, unfortunately that seems like the only option. You might want to wait for someone else to chime in with an idea, but personally I don't care about the data on my phone so I would factory reset.
Click to expand...
Click to collapse
I'll give that a try. I didn't want to do that unless it.was absolutely the last choice I had. I'll see what it does after reseting it. Anyone have any other suggestions or have this hopping to them.as well?
Sent from my SCH-I545 using Tapatalk
Yea I'm with Josh in that I don't care about the data on my phone so when things like this pop up I can just either factory reset or use Odin. You can at least save all your important stuff to your PC or external sd first. Hard to say what's causing it really... If you were able to flash a new kernel I'd suggest that but that's not an option right now... Unless surge or someone can extract the 4.4 stock kernel to use with Odin.... Most likely Odin the full kit kat image though should definitely help worse case
Sent from my jflte using Tapatalk
I flashed the nc5 modem a day it's all been fine but I can't call anyone now. It dials but I don't hear anything and others can't hear me. Anyone else experiencing this on my and the nc5 modem. It was from the thread around here with the modem only.
Thanks.
Sent from my SCH-I545 using Tapatalk
sevron said:
I flashed the nc5 modem a day it's all been fine but I can't call anyone now. It dials but I don't hear anything and others can't hear me. Anyone else experiencing this on my and the nc5 modem. It was from the thread around here with the modem only.
Thanks.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
What is build is your bootloader? Flash the corresponding non-hlos modem and see if that helps. If not then probably either try a different ROM or a No Wipe Odin image.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
What is build is your bootloader? Flash the corresponding non-hlos modem and see if that helps. If not then probably either try a different ROM or a No Wipe Odin image.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Gotta say watching the last couple days of s4 people going to HD 16 and having to do downgrade/upgrade process has not been disappointing.....hanging back has served me well
sent by safestrap enabled bajarom
decaturbob said:
Gotta say watching the last couple days of s4 people going to HD 16 and having to do downgrade/upgrade process has not been disappointing.....hanging back has served me well
sent by safestrap enabled bajarom
Click to expand...
Click to collapse
Yea what a nightmare it's been huh? Almost all the questions in q&a have been to do with the NC5 upgrade/downgrade/root deal and all the problems that come with it. Gotta say if I still had the fully locked down S4 and not this MDK one I probably would have just done what you did.... Wait and see.
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Yea what a nightmare it's been huh? Almost all the questions in q&a have been to do with the NC5 upgrade/downgrade/root deal and all the problems that come with it. Gotta say if I still had the fully locked down S4 and not this MDK one I probably would have just done what you did.... Wait and see.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
I don't get it. I took the OTA, followed the directions to downgrade, root, then upgrade (and keep root), flash Hyperdrive 16 (then 16.1) and have had zero problems. Every step worked perfectly the first time.
riker147 said:
I don't get it. I took the OTA, followed the directions to downgrade, root, then upgrade (and keep root), flash Hyperdrive 16 (then 16.1) and have had zero problems. Every step worked perfectly the first time.
Click to expand...
Click to collapse
Well I guess q great deal of people aren't to familiar with Odin and then hop right into something like that you know.. Just have to read the instructions and have all the needed files and be 110% sure your ready
Sent from my SCH-I545 using Tapatalk
Mistertac said:
Well I guess q great deal of people aren't to familiar with Odin and then hop right into something like that you know.. Just have to read the instructions and have all the needed files and be 110% sure your ready
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
Jump first...then look.
sent by safestrap enabled bajarom
sevron said:
I flashed the nc5 modem a day it's all been fine but I can't call anyone now. It dials but I don't hear anything and others can't hear me. Anyone else experiencing this on my and the nc5 modem. It was from the thread around here with the modem only.
Thanks.
Sent from my SCH-I545 using Tapatalk
Click to expand...
Click to collapse
i'm having the same problem now..i have the mdk bootloader...bluetooth seems to still work, its the only way i can send/receive calls...
Sent from my SM-P900 using Tapatalk
I'm having the same problem, has anyone had any break through concerning this information technology question.. I got problems and jokes! there is a work around Ive found but it's annoying. once conect ress the speaker button and yo can here them and they can here you. click back to spaker off and it's working fine waa laa.... It's a terrible bug though