From what ive read and understand, if you try to flash to 4.3 after already having upgraded to 4.4.2, you will brick your phone or it just wont work? Is this true or not, please help! IF you can flash to a previous OS, can anyone post a link on how to do it the right way or explain how to do this, preaze?
you should be able to flash the stock mj4 .tar thru ODIN once is flash you may get stock on boot screen, go into stock recovery and clear cache and reset data and reboot.
If this dont work you can flash KK .tar and be back at square one.
from what i understand you cant downgrade, it will brick it. But i wonder if you downgrade just the modem if it will have the same issue
no downgrade...........yet hopefully
If you try to flash the stock MJ4 ROM after upgrading to KK, your phone will do nothing but reboot over and over, going no farther than the Galaxy note 3 splash screen. You CAN downgrade just the modem without bricking the phone, but I will tell you that when I did, I lost Wi-Fi. I have had horrible signal strength and signal since moving to KK 4.4.2. Even worse, something I didn't find out until after going to KK, SMS blockers won't work. Apparently there is something with the default messaging app where a notification will get sent no matter what to the default messaging app. So you'll get two notifications. You'll get get one in the blocker program and one in the default messaging app. Way to go Google on not preparing devs better, fail. Anyway, here is a link to a thread where you can get the MJ4 and NAB modems as well as the engineering bootloader. The stock bootloader is there too, but I think merely for entertainment purposes lol Anywho, here's the link http://forum.xda-developers.com/showthread.php?p=51165389 As I stated before, I lost Wi-Fi when I flashed MJ4. So just flash MJ4 first, then NAB, and you should see some........some improvement in signal strength.
Related
I got the S4 back when it first came out, and messed around with some CM ROMs and other custom ROMs that worked fairly well. The big killers for me though were bluetooth audio not working, not being able to use headphone microphones, and the proximity sensor being all weird. So I reverted to stock but kept root, and eventually upgraded to MJ7 while keeping root. When I boot I still get the 'Samsung Custom' bootscreen.
I've never been happy with Touchwiz, and have all of the Samsung features turned off. The stock messaging app is really the thing that bugs the hell out of me, since it takes forever to get messages (sometimes up to an hour, while Handcent will get them right away), and I love my Nexus 7 experience. I'd really like to get as close to a 'Google' phone as possible, but I'm currently stuck on Verizon.
I've tried using GooManager to download the recovery managers again, but it's having problems with 404 errors downloading the scripts. I tried ROM Manager and it says it installs ClockworkMod (6.0.44 in fact), but it refuses to boot into recovery mode. Most of the tools I'm finding are not for MJ7, so I'm kind of hesitant to solutions that aren't for my current version. Since I can't make any backups without being able to boot into a proper recovery mode, that's another kind of notch against using most of the guides.
I don't mind the actual process of doing the work, I'm just not sure where to go from here. What are my options?
dragonmantank said:
I got the S4 back when it first came out, and messed around with some CM ROMs and other custom ROMs that worked fairly well. The big killers for me though were bluetooth audio not working, not being able to use headphone microphones, and the proximity sensor being all weird. So I reverted to stock but kept root, and eventually upgraded to MJ7 while keeping root. When I boot I still get the 'Samsung Custom' bootscreen.
I've never been happy with Touchwiz, and have all of the Samsung features turned off. The stock messaging app is really the thing that bugs the hell out of me, since it takes forever to get messages (sometimes up to an hour, while Handcent will get them right away), and I love my Nexus 7 experience. I'd really like to get as close to a 'Google' phone as possible, but I'm currently stuck on Verizon.
I've tried using GooManager to download the recovery managers again, but it's having problems with 404 errors downloading the scripts. I tried ROM Manager and it says it installs ClockworkMod (6.0.44 in fact), but it refuses to boot into recovery mode. Most of the tools I'm finding are not for MJ7, so I'm kind of hesitant to solutions that aren't for my current version. Since I can't make any backups without being able to boot into a proper recovery mode, that's another kind of notch against using most of the guides.
I don't mind the actual process of doing the work, I'm just not sure where to go from here. What are my options?
Click to expand...
Click to collapse
Well unfortunately for you you're on MJ7 which means your only options right now are rooting and Xposed. Other than that though, there's really nothing else you can do at the moment. If you were on ME7 or MI1 still you could at least run Safestrap, but even then you would be limited to Touchwiz based roms. Unless you're willing to go on the hunt for an MDK S4 you'll just have to deal with your limited options for now. Oh and before you ask, there is absolutely no way to revert back to earlier firmwares. Once you update, you're stuck.
Crawshayi said:
Well unfortunately for you you're on MJ7 which means your only options right now are rooting and Xposed. Other than that though, there's really nothing else you can do at the moment. If you were on ME7 or MI1 still you could at least run Safestrap, but even then you would be limited to Touchwiz based roms. Unless you're willing to go on the hunt for an MDK S4 you'll just have to deal with your limited options for now. Oh and before you ask, there is absolutely no way to revert back to earlier firmwares. Once you update, you're stuck.
Click to expand...
Click to collapse
Yeah, I know I couldn't revert the firmware to something earlier. Is it possible to revert to stock even? At this point I think I just want to revert it and sell this phone off and get something else. I don't care about KNOX status, just getting it back to stock so that whomever buys it won't keep getting security notifications.
dragonmantank said:
Yeah, I know I couldn't revert the firmware to something earlier. Is it possible to revert to stock even? At this point I think I just want to revert it and sell this phone off and get something else. I don't care about KNOX status, just getting it back to stock so that whomever buys it won't keep getting security notifications.
Click to expand...
Click to collapse
Yes I believe it's possible, I found this thread that gives you an Odin image to flash: http://forum.xda-developers.com/showthread.php?t=2507217
The security notification was actually fixed and supposedly an update was pushed out, but maybe yours didn't grab the update properly? I'm not sure, but that Odin image should get you back to factory stock. If I were you I would get an HTC One if you can live with not having a removable battery and sd card.
Awesome, thank you very much.
I'm re-flashing today take it back. I'll have a look at the HTC One, since it wasn't out when I got my S4. I know that (at the time) the S4 was the only Android phone I had found, with the One a close second but not available. I would really love a Google phone, but I get the feeling that will probably never happen on VZW.
Hey guys, has anyone had this issue where your camera refuses to focus on anything further away than say about 6 inches? It can focus just fine close up, but beyond that it's garbage. It goes through the 'animation' of focusing, turns red like i can't focus, and doesn't actually adjust the focus at all. It started in about October and has persisted through 3 or 4 ROMs and various camera APKs.
Has anyone replaced their camera before? I doubt verizon would trade me for a new phone seeing as I've rooted it and flashed a lot of ROMs on it. What should I do? What have you done if this has happened to you? This thread outlines exactly the same thing I'm experiencing and seems as they've concluded it's hardware failure.
Thoughts?
Bump in hopes of someone's experience or advice.
falkon114 said:
Hey guys, has anyone had this issue where your camera refuses to focus on anything further away than say about 6 inches? It can focus just fine close up, but beyond that it's garbage. It goes through the 'animation' of focusing, turns red like i can't focus, and doesn't actually adjust the focus at all. It started in about October and has persisted through 3 or 4 ROMs and various camera APKs.
Has anyone replaced their camera before? I doubt verizon would trade me for a new phone seeing as I've rooted it and flashed a lot of ROMs on it. What should I do? What have you done if this has happened to you? This thread outlines exactly the same thing I'm experiencing and seems as they've concluded it's hardware failure.
Thoughts?
Click to expand...
Click to collapse
I think you're right on the hardware issue. You could always use ODIN to restore the phone back to stock and turn it in for replacement. Verizon can't tell the difference as long as you restore it with the proper factory image. Bad thing is, replacement will probably come locked down with the currently unlockable 4.3 bootloader. At the very least you can restore it with ODIN just to see if it helps the focus issue.
*see below*
Jiggabitties said:
I think you're right on the hardware issue. You could always use ODIN to restore the phone back to stock and turn it in for replacement. Verizon can't tell the difference as long as you restore it with the proper factory image. Bad thing is, replacement will probably come locked down with the currently unlockable 4.3 bootloader. At the very least you can restore it with ODIN just to see if it helps the focus issue.
Click to expand...
Click to collapse
Yeah, i think I might try going back to stock. I wanted to a little while ago just to remember what it was like having a stock system, but I can't find all the files I need. Wasn't there a sticky with Odin and all the right files in one thread? Thought it was stickied, but either I'm blind, or I'm not finding it.
Edit:
Nvm, I'm an idiot
falkon114 said:
Yeah, i think I might try going back to stock. I wanted to a little while ago just to remember what it was like having a stock system, but I can't find all the files I need. Wasn't there a sticky with Odin and all the right files in one thread? Thought it was stickied, but either I'm blind, or I'm not finding it.
Edit:
Nvm, I'm an idiot
Click to expand...
Click to collapse
Yeah sometimes I go back to stock for a day or two just to remind myself why crack flashing is so worth it. But sometimes it's just needed to iron out some bugs. I was having radio issues not too long ago, tried different roms and radios and couldn't fix it. Flashed back to stock, worked like a charm. Haven't had an issue since.
Jiggabitties said:
Yeah sometimes I go back to stock for a day or two just to remind myself why crack flashing is so worth it. But sometimes it's just needed to iron out some bugs. I was having radio issues not too long ago, tried different roms and radios and couldn't fix it. Flashed back to stock, worked like a charm. Haven't had an issue since.
Click to expand...
Click to collapse
Alright, so I remember having some problems when I was first rooting/modifying/Custom recovery-ing...
Couple questions.
1. I use TWRP as my recovery of choice. Can I backup my current ROM as is and store it through there like I normally would when going to a new ROM in case I want to after I go back to stock? Or will going back to stock completely erase all saved ROM images?
If I go back to stock, can I boot into TWRP again like I do now, or is there some process I'll need to follow again to be able to flash my current ROM image? Should I flash the Root66 stock VRALJB 4.1.1 (12/2/12) in the previously linked thread so I can still use custom recovery?
What else should I know? I've become quite good and confident in flashing ROMs, but I'm nervous going back to stock since it seems easier to brick it/lock it down. I remember when I first downloaded and tried installing TWRP, it showed that infamous Yellow Triangle saying the device found unauthorized software and to take it to Verizon, and I remember spending hours trying to flash things to get past that, I don't want to have to deal with that again.
falkon114 said:
Alright, so I remember having some problems when I was first rooting/modifying/Custom recovery-ing...
Couple questions.
1. I use TWRP as my recovery of choice. Can I backup my current ROM as is and store it through there like I normally would when going to a new ROM in case I want to after I go back to stock? Or will going back to stock completely erase all saved ROM images?
If I go back to stock, can I boot into TWRP again like I do now, or is there some process I'll need to follow again to be able to flash my current ROM image? Should I flash the Root66 stock VRALJB 4.1.1 (12/2/12) in the previously linked thread so I can still use custom recovery?
What else should I know? I've become quite good and confident in flashing ROMs, but I'm nervous going back to stock since it seems easier to brick it/lock it down. I remember when I first downloaded and tried installing TWRP, it showed that infamous Yellow Triangle saying the device found unauthorized software and to take it to Verizon, and I remember spending hours trying to flash things to get past that, I don't want to have to deal with that again.
Click to expand...
Click to collapse
Yes, backup your current ROM, if you use the root66 Odin image it should not erase anything you have stored. But to be safe, I would copy your TWRP backup to either an external SD or to your computer for safe keeping. TWRP should survive, as long as you use root66, the others will overwrite recovery and lock the bootloader.
The only reason you should ever get the "Yellow Triangle", or trip any sort of security is if you attempt to install a custom recovery or ROM while the bootloader remains locked, or, you attempted to install the recovery via ODIN.
The most important thing here is, whatever you do, under any circumstance, DO NOT accept any OTA updates. As long as you don't accept the 4.3 OTA, you should be able to keep your TWRP.
You may want to try this flashable version of the stock VRAMC3 before you resort to ODIN http://forum.xda-developers.com/showthread.php?t=2261478
Jiggabitties said:
Yes, backup your current ROM, if you use the root66 Odin image it should not erase anything you have stored. But to be safe, I would copy your TWRP backup to either an external SD or to your computer for safe keeping. TWRP should survive, as long as you use root66, the others will overwrite recovery and lock the bootloader.
The only reason you should ever get the "Yellow Triangle", or trip any sort of security is if you attempt to install a custom recovery or ROM while the bootloader remains locked, or, you attempted to install the recovery via ODIN.
The most important thing here is, whatever you do, under any circumstance, DO NOT accept any OTA updates. As long as you don't accept the 4.3 OTA, you should be able to keep your TWRP.
You may want to try this flashable version of the stock VRAMC3 before you resort to ODIN http://forum.xda-developers.com/showthread.php?t=2261478
Click to expand...
Click to collapse
Thanks. I tried the last link there, and am back to relatively stock and still have the camera issue.
I'm excited for the 4.3 update to be hacked since I would really, really like multi-window and SNote capabilities on my 4.3 ROM, but who knows when that might happen.
Thanks for you help man!
falkon114 said:
Thanks. I tried the last link there, and am back to relatively stock and still have the camera issue.
I'm excited for the 4.3 update to be hacked since I would really, really like multi-window and SNote capabilities on my 4.3 ROM, but who knows when that might happen.
Thanks for you help man!
Click to expand...
Click to collapse
Glad I could help in any way. Bummer about your camera.
I was running VRAMC3 with root and unlocked bootloader and decided to try CM11. I followed the instructions to upgrade on the official nightly page (install latest CWM, install rom/gapps, do a factory reset, reboot), however when I booted into CM11 I found that I had no signal and my baseband said "Unknown" under phone status. I read that flashing stock through odin and redoing the entire root/unlock process would allow me to restore my baseband. I tried flashing VRAMC3 stock, but I am still receiving no signal and even worse I am now stuck on a setup page that reads "Please wait while your phone connects to Verizon Wireless and automatically activates". Obviously it is never going to activate if it can't even get a signal. Does anyone have any ideas on how I can return signal to the phone?
Thanks
Edit: After waiting forever it finally let me skip activation. However, the baseband is still Unknown so I am basically back where I started.
Edit: Solved! Just in case anyone runs into this in the future this is what I did:
1) Flash whatever stock came with the phone (VRAMC3 in my case)
2) Wait for the stupid activation to fail (takes forever)
3) Enable ADB and use the casual tool to root/unlock again
4) Install the t0lte mj9 firmware (NOT the whole mj9 stock file)
5) Baseband magically works again
6) Install whatever 4.3 rom (I'm too scared to try CM11 again)
Don't ask me why it works or what even went wrong in the first place but just in anyone else runs into the problem this is what I did.
I flashed Beans MJ9 firmware. Have flashed back n forth before multiple aosp ROMs and Alliance ROMs. Have no issues with lost data/signal. If you have the latest recovery installed should resolve your lost signal issue. Use either TWRP or philz touch cwm.
Sent from my SCH-I605 using Tapatalk
Shortbusdriver said:
I was running VRAMC3 with root and unlocked bootloader and decided to try CM11. I followed the instructions to upgrade on the official nightly page (install latest CWM, install rom/gapps, do a factory reset, reboot), however when I booted into CM11 I found that I had no signal and my baseband said "Unknown" under phone status. I read that flashing stock through odin and redoing the entire root/unlock process would allow me to restore my baseband. I tried flashing VRAMC3 stock, but I am still receiving no signal and even worse I am now stuck on a setup page that reads "Please wait while your phone connects to Verizon Wireless and automatically activates". Obviously it is never going to activate if it can't even get a signal. Does anyone have any ideas on how I can return signal to the phone?
Thanks
Edit: After waiting forever it finally let me skip activation. However, the baseband is still Unknown so I am basically back where I started.
Edit: Solved! Just in case anyone runs into this in the future this is what I did:
1) Flash whatever stock came with the phone (VRAMC3 in my case)
2) Wait for the stupid activation to fail (takes forever)
3) Enable ADB and use the casual tool to root/unlock again
4) Install the t0lte mj9 firmware (NOT the whole mj9 stock file)
5) Baseband magically works again
6) Install whatever 4.3 rom (I'm too scared to try CM11 again)
Don't ask me why it works or what even went wrong in the first place but just in anyone else runs into the problem this is what I did.
Click to expand...
Click to collapse
Wouldn't be scared to flash cm11 again.. If it happens again instead of Odin back to ramc3 just flash mj9 firmware again and it will fix your problem..
As far as no signal for cm11 couple ?'s..
Are you sure you flashed the one for this device?
Before you flashed, did you wipe everything? Cache, delvik, system and data..
Sent from my SCH-I605 using xda app-developers app
I have a Verizon SCH-I605 Note 2. I rooted and unlocked the boot loader when it was on 4.1.2. I have since then flashed 4.3 Roms through TWRP and because of that, it didn't install KNOX at all.
I was having issues with the Bluetooth and WiFi radios recently. Randomly they would stop working and not turn on at all. The toggles would turn light green and act like they were gong to turn on but didnt. They just turned grey again. Then a few hours to a day later they would randomly work and turn on and work. Then randomly they wouldn't work again. I tried to see if there was a pattern to when they would stop working but there wasn't.
At first I thought it was an app that I had installed that was causing it. So I flashed the same and other roms after wiping "everything". That would seem to work for a while but soon it happened again. It even did it without installing any additional apps after flashing. I decided to flash the stock rooted 4.3 OTA. That didn't work either. I then decided to flash stock and unrooted 4.3 using mobile Odin and inject superuser and mobile Odin. Right of the bat WiFi and Bluetooth didn't work. I am ALMOST convinced that it is hardware related now. Any thoughts on what would be causing it?
Also when I flashed it stock and unrooted with mobile odin, It kept root but I lost TWRP. And when I boot into download mode, it doesn't show the KNOX counter line at all so i am assuming that it didnt install it. Is it possible to flash back stock to 4.1.2 with odin and then re root and unlock the boot loader? Or is there another way to get TWRP back?
Any help or feedback is greatly appreciated
I decided to get my girlfriend a Verizon SCH-I545 to replace her T-Mobile Galaxy S3. It was working great on our T-Mobile service. Then I saw online that Verizon had released lollipop on their S4, so I figured I would plug the phone into Kies and update it from 4.4.2 to 5.0.1. I updated it overnight. When she went to use it in the morning, everything worked great, except it wouldn't send a text message. T-Mobile and Samsung support said that it is because T-Mobile hasn't released their lollipop rom for the S4 yet. I figured the best thing to do would be to roll back the firmware. Having done some rooting and custom roms on my old galaxy S2 Epic 4g Touch, I felt like I knew exactly what to do. I downloaded multiple ROMs and tried to install them through ODIN and through stock recovery. Nothing took. Finally after trying about 10 things, I soft bricked the phone. I can still get into download (ODIN) mode, but I can't get into stock recovery anymore. When I try to go into stock recovery it gives me this message: "Software Update Failed" "Your device didn't update successfully. Use the Verizon Software Repair Assistant on a computer to repair your device and complete the update." But, while the phone was still able to boot into android, the phone installed the Verizon Software Repair Assistant. I attempted to use it to rollback to 4.4.2 and the Assistant told me that it couldn't do anything to repair 5.0.1.
What I need to accomplish is either getting the phone back to 4.4.2 or 5.0.1 with text messaging working by any means necessary. Before I soft bricked the phone, I was hoping to avoid changing from stock recovery, but at this point I'm willing to do whatever I need to. For compatibility reasons, I hoped to try to keep her on a stock rom. If anyone knows of a rom with no bugs and a close to stock experience, I'll gladly set her up any way you guys think I should.
Thank you in advance for your assistance. I apologize for being "long winded" but I wanted to try and give as much detail as possible.
Still looking for any help I can get in resolving these issues.
You can't flash custom recovery for anything newer than 4.3 you will just jack up your phone trying.
Is both Talk & Data working??? SMS might be just improper APN settings. Google the APN for T-Mobile and that should fix it.
Since you installed 5.0.1 over Kies you are kind of stuck cause that would have updated the baseband and you can't have anything older than the baseband version.
Try installing this over Odin:
https://www.androidfilehost.com/?fid=23991606952596145
If you have Odin 3.09 or 3.10 choose AP to load the file. Make sure its unzipped too.
google luck!
somewhat resolved
I'm no longer soft bricked. I just got that back up and going. However the phone will still not send text messages. From what I've found, this only happens on 4g LTE. But, data, incoming texts, phone calls, mms, and everything else has been working just fine.
Yeah, you can curse Verizon for this. They lock down everything. A lot of people are flashing the Verizon version of Lollipop which screws their phone. I would show you a fix for that, but you need root, and OC1 doesn't have it yet. No fix for this because you can't Odin back and there is no root.
if you look at the link i posted its a version of Lollipop that lets you flash back to KitKat. It only works if you never installed lollipop. Unfortunately for me my phone wont read my sim card anymore its pretty much just a small tablet.
cwa82 said:
if you look at the link i posted its a version of Lollipop that lets you flash back to KitKat. It only works if you never installed lollipop. Unfortunately for me my phone wont read my sim card anymore its pretty much just a small tablet.
Click to expand...
Click to collapse
Sadly I had upgraded to lollipop, which is what created my problems to begin with. If I had never updated, text messages would've always worked, and ib never would have soft bricked the phone trying to roll back to kit-kat. I'm just glad I got the soft brick fixed, now I just have to wait for a fix on the text messaging.
bigg6987 said:
Sadly I had upgraded to lollipop, which is what created my problems to begin with. If I had never updated, text messages would've always worked, and ib never would have soft bricked the phone trying to roll back to kit-kat. I'm just glad I got the soft brick fixed, now I just have to wait for a fix on the text messaging.
Click to expand...
Click to collapse
You might be better off just buying her a different phone and selling that one.