Ok so, me messing up and not thinking that Samsung devices would be so difficult to root compared to others, I tried downgrading my Note 3 from 4.4.2 to 4.3 in Odin. I used 3.09. Something had happened where I thought everything was fine but now it only boots up to the screen that says "Samsung Galaxy Note 3" and nothing more before Vibrating 2 times and starting over. I can go into download mode and if I try recovery it says recovery but when I let go of the button need to do so nothing happens but a boot back to the first screen. What did I do or need to do to get back to stock 4.4.2? I have tried everything but maybe not the right combo of things. Please I know that a answer may be in a thread from way back when but this is asap. I need it for tomorrow and have been working on it and researching it for 12 hours now before posting. Thanks in advance/.
Not to kick your head while you're drowning but a little more searching before rooting that 4.4.2 att note 3 could've saved you going to best buy to reflash the official firmware. It is unrootable at the moment. Also check out a thread by carl1961. It would get you booting again but it wouldnt be the official firmware.
Sent from my SM-N900A using Tapatalk
Related
First, MODS: I apologize if this is posted in the wrong thread, but I can't find anything along the lines of help I need, and since I started here, I was thinking I'd end here... Please move if necessary.
So I have recently learned that not all Android devices are as easily rooted/modded as my EVO (rooted my GF's Optimus S, and ended up on the couch for months, and around the same time, rooted the Sprint SGT she got me for X-Mas, and have only gotten the Optimus S working again, but remain on the couch for bricking my SGT).
I am in dire need of help getting my SGT back to stock (if that's even possible) or at least back to rooted with a stock ROM. I rooted my SGT in preparation for the Honeycomb port (which was apparently a bust(?) and after flashing that port, then Boushh's AOSP ROM, I can boot to download mode (with neither Heimdall or Odin reognizing the device) or I can attempt to boot to recovery and get nothing but the Samsung splash.
I have all drivers installed, and I PROMISE I have learned my lesson, and should have never rooted to begin with, but if ANYONE could please help me get my SGT back, I would TRUELY appreciate it!
I have just recently gotten semi-familiar with ADB again (Optimus S fix) but I'm not really in a place to start pushing commands without guidance.
I'm sorry again if this is the incorrect thread, I didn't know where else to post, but I REALLY need help. We really couldn't afford the SGT to begin with, so I feel horrible that I've bricked it, and can't do anything with it anymore.
Sorry to be a gnat...
IP IHI II IL said:
I'm sorry again if this is the incorrect thread, I didn't know where else to post
Click to expand...
Click to collapse
Read HERE or HERE
IP IHI II IL said:
First, MODS: I apologize if this is posted in the wrong thread, but I can't find anything along the lines of help I need, and since I started here, I was thinking I'd end here... Please move if necessary.
So I have recently learned that not all Android devices are as easily rooted/modded as my EVO (rooted my GF's Optimus S, and ended up on the couch for months, and around the same time, rooted the Sprint SGT she got me for X-Mas, and have only gotten the Optimus S working again, but remain on the couch for bricking my SGT).
I am in dire need of help getting my SGT back to stock (if that's even possible) or at least back to rooted with a stock ROM. I rooted my SGT in preparation for the Honeycomb port (which was apparently a bust(?) and after flashing that port, then Boushh's AOSP ROM, I can boot to download mode (with neither Heimdall or Odin reognizing the device) or I can attempt to boot to recovery and get nothing but the Samsung splash.
I have all drivers installed, and I PROMISE I have learned my lesson, and should have never rooted to begin with, but if ANYONE could please help me get my SGT back, I would TRUELY appreciate it!
I have just recently gotten semi-familiar with ADB again (Optimus S fix) but I'm not really in a place to start pushing commands without guidance.
I'm sorry again if this is the incorrect thread, I didn't know where else to post, but I REALLY need help. We really couldn't afford the SGT to begin with, so I feel horrible that I've bricked it, and can't do anything with it anymore.
Sorry to be a gnat...
Click to expand...
Click to collapse
No worries buddy, I know how it feels, since you posted already here's how your proceed:
1. get Odin 1.7
2. if you want stock, go to samfirmware.com and download the ROM corresponding to your device
3. Bear in mind that most stock ROM are shipped with locked bootloader, if you don't care skip step 4/5
4. download super one click root from shortfuse.org
5. root your device and either get a ROM with removed bootloaders or get the bootloader patch by chainfire, found in this forum somewhere
6. While being in the "yellow" screen flash using odin
Hope this helps.
He has a cdma tab. Sprint right?
Try this: http://forum.xda-developers.com/showthread.php?t=969892&highlight=sprint+stock
As your last resort. If not go back to sprint tell them tab isnt switxhing on.
How about flashing a kernel that installs cwm?
Sent from my GT-P1000 using Tapatalk
As long as you flash the no modem software you are good. That is the key. No modem.
Probably a driver issue if it's not being seen in ODIN.
if its not seen it doesnt matter either, you turn off and turn on again, you'll see a black screen with some kind of logo, then I usually flash a rotohammer release, this is always the life saver
shoman24v said:
As long as you flash the no modem software you are good. That is the key. No modem.
Probably a driver issue if it's not being seen in ODIN.
Click to expand...
Click to collapse
Usually when having both, Odin and Heimdal installed, one of them needs to be removed...
RunTimeWorld said:
Usually when having both, Odin and Heimdal installed, one of them needs to be removed...
Click to expand...
Click to collapse
Yup. ODIN takes a separate driver that conflicts with heimdall and vice versa.
Sent from my SPH-P100 using Tapatalk
Hi I can't even enter download mode after my Odin update failed. It's just a black screen and when I plug it into the computer it's not recognised at all.
Any ideas on how to fix this?
Please anyone, any help is greatly appreciated. I seem to have really messed up my friends Galaxy Tab (VZW). I've tried countless times to flash custom ROMS and they all just reboot when it says "Installing update..." Then it just reboots and does the same thing over and over. Right now I'm trying to use Heimdall to restore it back to stock but then it just boots the Verizon start up and then vibrates 3 times and loops forever. Nothing is working! It's so frustrating. It's even more frustrating that at one point I had 4.0.2 running fine but then all hell broke lose once I tried to upgrade to 4.1.2. So even trying to reinstall the initial 4.0.2 using the exact same method I used before doesn't work. I'm out of ideas, patience, and losing my mind. Please someone, help!
Hi,
Have you tried using Odin?
I'd also suggest to check of the stock room you are using is correct.
Regards
Sent from my GT-P1000
time4fun said:
Please anyone, any help is greatly appreciated. I seem to have really messed up my friends Galaxy Tab (VZW). I've tried countless times to flash custom ROMS and they all just reboot when it says "Installing update..." Then it just reboots and does the same thing over and over. Right now I'm trying to use Heimdall to restore it back to stock but then it just boots the Verizon start up and then vibrates 3 times and loops forever. Nothing is working! It's so frustrating. It's even more frustrating that at one point I had 4.0.2 running fine but then all hell broke lose once I tried to upgrade to 4.1.2. So even trying to reinstall the initial 4.0.2 using the exact same method I used before doesn't work. I'm out of ideas, patience, and losing my mind. Please someone, help!
Click to expand...
Click to collapse
There's a new thread which should help you get back to stock http://forum.xda-developers.com/showthread.php?t=2383201
Hey guys,
Basically today I was getting tired of the android 5.0 install I had running on my S5 so I figured I would reinstall 4.4.2 via Odin - a process which I had done a few times previously. I didn't really think about the fact that I was going from one version of the OS to another, and whether this would create an issue, but it has. My phone now loads up the samsung logo, but doesn't finish the animation and then freezes. A few seconds later, the screen will go black and the LED on the top of the phone will just glow blue. The phone will sit like this forever, and never boot. I have tried re-installing the AP in Odin a few times, all of which show pass in Odin, but to no avail. I have also wiped all data and the cache within the recovery. I don't know where to go from here. Any suggestions?
Thanks
Philpro said:
Hey guys,
Basically today I was getting tired of the android 5.0 install I had running on my S5 so I figured I would reinstall 4.4.2 via Odin - a process which I had done a few times previously. I didn't really think about the fact that I was going from one version of the OS to another, and whether this would create an issue, but it has. My phone now loads up the samsung logo, but doesn't finish the animation and then freezes. A few seconds later, the screen will go black and the LED on the top of the phone will just glow blue. The phone will sit like this forever, and never boot. I have tried re-installing the AP in Odin a few times, all of which show pass in Odin, but to no avail. I have also wiped all data and the cache within the recovery. I don't know where to go from here. Any suggestions?
Thanks
Click to expand...
Click to collapse
I think you need to find the lollipop kernel. But I'm not 100 percent sure.
try opening kies with your phone connected and look for a menu option to the effect of restore/repair device
sent from my galaxy a5 (SM-G900AZ) on Cricket
I'm not sure if this helps you or not, but I did the same thing, trying to downgrade. I did not take the OTA update when I went from KitKat to Lollipop, instead I flashed one of the Lollipop ROMs, so be wary of that. If you took the OTA update, I don't know if this will work for you.
Anyways, I spent the better half of a day trying different kernels and stock ROMs using the factory recovery etc and nothing was working, each time I would either end up frozen at the Samsung screen or the initial splash screen when you power the phone on. I found this thread here:
http://forum.xda-developers.com/att...w-to-update-to-g900aoca-5-0-keeproot-t3076803
Under "notes", step 4 I downloaded the file G900A_Downgrade_to_NCE.tar and flashed through Odin. This is the file that got me out of this hole, so maybe it will work for you as well. After flashing, it rebooted and went past the Samsung screen to the initial first time setup screen. Looks like this put me back at stock UNrooted 4.4.2.
Good luck, hope this helps someone else out.
Wait, are you saying that you updated your phone using the stock recovery? Were you rooted? @mangomango
Its_Tim said:
Wait, are you saying that you updated your phone using the stock recovery? Were you rooted? @mangomango
Click to expand...
Click to collapse
I flashed through Odin, but yes I was rooted when I went from KK to LP.
I purchased an AT&T sm-g900a that was supposed to come with 4.4.2 according to info on site and sticker on the box indicated it originally had 4.4.2 on it too. I have no way of knowing if someone flashed it with the whole 5.0 file or just updated it. It was sold to me as a new and unlocked phone, and I got a good deal. The phone looks new with an AT&T screen cover attached, packaging, etc. and contents were still in sealed packaging. Will this work? https://www.androidpit.com/how-to-downgrade-galaxy-s5-from-lollipop-to-kitkat ? Is this the same file as the downgrade one referred to? Sammobile only has the 4.4.2 file. There is a significant cost difference in this model and the t-mobile version. Otherwise, I would just return it. I do not like the newer software at all.
I had the same thing happen today with my g870a. I tried 5.0, and 4.4.2 kernels, 4.4.2 firmware (which I knew wasn't corrupt) in Odin but nothing worked. The whole reason was to go redo my Alliance Rom and use FF beside Safestrap (the LP kernal would get rid of the SS). What I ended up doing was going into stock recovery and went to where it says "install update from ext SD". Then I went into my FF backup and found twrp.zip and selected it. It's did some things, said some stuff failed, then booted up enough to get me to FF to get it straight. One problem...my g870a thinks it's a 900, wtf?
Sent from my SAMSUNG-SM-G900A using Tapatalk
hello,
ive been searching around for about an hour and i havent found a thing.
Let me describe my phone:
Safestrap
rooted
android 4.4.2
Scenario:
got a nasty ad virus yesterday, so i restarted my phone today and went into safestrap. Then i installed my previous back up from about a month ago. (not sure if i needed to delete anything left of the device) I restored data and system and it worked fine. I was in android for about 5 minutes then it restarted. so i assumed it was normal then it did it continuously.
First off im not sure what a bootloop is but i assume it doesnt post to the android system and continuously loops the boot logos.
Whats happening to me is that my phone will boot for a few seconds, sometimes minutes, and i can get on android for a few. Then the phone restarts. Ive been looking around for a few hours now and i cant find a fix or a way to restore my phone to the restore i made on 4/22/17.
ANY help would be greatly appreciated and please correct me if i did something i wasnt supposed to.
If you need more info i will gladly post more
-LL
I am no expert, but I think you would have to do a factory reset on your phone if you wanted to have a proper restore. When I did rooting on 4.4.4 and 5.0 I always flashed the phone with Odin.
Sicuro said:
I am no expert, but I think you would have to do a factory reset on your phone if you wanted to have a proper restore. When I did rooting on 4.4.4 and 5.0 I always flashed the phone with Odin.
Click to expand...
Click to collapse
I got it fixed i had to flash a new stock rom and root it again. up and running from a softbrick. Its also running Android 4.4.2
Going back to stock from my rooted PopRocksV14. Haven't flashed ROMs in a while, so super rusty. Input welcome. TIA!
Questions:
1 Any faster mirror for N910TUVU2EQI2 than https://www.sammobile.com/firmwares/galaxy-note4/SM-N910T/TMB/?
2 How is the latest stock FW? Any reason not to upgrade? I'm just looking to get a stable phone and decent battery life, don't care about bloat
3 I'm looking to overwrite any Kernel and partition changes that PopRocks might have made, so is flashing back to stock rom going to do this?
Steps:
1 Make sure Samsung drivers installed
2 Download Odin 3.13 - https://odindownload.com/download/#.WyvXuCAnbAQ
3 Download EQI2 rom
4 Factory reset N910T
5 Run Odin as Admin
6 Start N910T in Download mode
7 Connect phone to PC via USB cable
8 Check Odin that COM is connected
9 Click PDA and select EQI2 tar file
10 Make sure Auto Reboot and F.Reset Time are checked, all other options disabled
11 Click start and wait for update to complete and phone to reboot
12 Factory reset N910T
I went ahead and tried it after the Sammobile download completed and it worked!
sfsilicon said:
I went ahead and tried it after the Sammobile download completed and it worked!
Click to expand...
Click to collapse
@sfsilicon - hope you're still monitoring this old thread. I'm trying to revive my old Note 4 I found in a junk drawer - for my 6yo boy. It had some custom rom on it, and I've now attempted with Odin to restore the image EQ12 you had listed - it appears to be the most recent.
Oden gets about 99% done then fails and now the phone is stuck in some sort of emergency mode. I can get into download, but not recovery. I assume I hosed it - maybe the bootloader was the wrong kind from the prior custom rom (and I didn't take note of what it was since I was just wiping it out).
Bummer.
Sorry to hear about your problems. It has been a while since I reflashed back to stock. Did it on two note 4s. From your description only thing I can think of would be that you flashed from a rom that was from an earlier Android version to the latest and it is missing some files or partitions that would normally be part of that type of transition. E.g. if you had done all the updates via OTA vs gone from your custom rom to the latest stock TMO release.
So try to figure out what Android revision your custom rom was before this latest flash. Then check the posts about moving from that revision to the next latest one and see if there is anything special in between. You can then look for the stock TMO rom that matches your custom ROM then flash back to that. Once you have a ROM working, even an older you can flash the next updates till you reach the final/latest TMO version or just OTA it.
One other thing to check is if your custom ROM did any changes to the kernel files or other stuff. Then check with the old custom ROM how to reverse them. Not sure if flashing a stock TMO rom undos all this. Its been a while but would think so but its still a step to check.
Hope this helps and good luck! I'm actually using my N4 currently. I use it to hold a foreign SIM when I am travelling. Sort of a glorified hotspot. Gave my 2nd one to my mom where the large screen helps with reading text. Its still a nice phone.
Thanks for getting back with me. I was under the impression that regardless of what custom rom may have been on the phone, Odin was a way to wipe the slate clean and put it back to day-1 state. I have no idea what OS was on there, but I do recall a warning about the bootloader being modified and it may be impossible to roll back. That's going off of memory (which has a very low confidence level).
Now I can't even get it to power up at all. I think I'm going to bail and just get a cheap Chinese android phablet - don't need cell service. It's getting to the point that my time and patience is worth more than what I'm spending to rehab this thing. Sucks too... When I first got the N4, I was pretty proficient at swapping roms... But since I've not played with them in years, I've all but forgotten the basics.
Thanks for the suggestions, tho...
E