Hi there! Recently I updated my phone after using KitKat for quite a while as I grew a bit bored of KitKat and thought Lollipop would do some good. Previously, I had KitKat then went to Lollipop but I didn't like Lollipop so I flashed to KitKat. Then, after some time I am where I am now, stuck on Lollipop. So I am trying to revert back to KitKat again, but on my computer after I load KitKat into Odin and press start, the console log gets stuck on aboot.mbn. Everything works fine until that point, which it then just sits there. My phone also displays a loading bar on the download mode, but sits at the very beginning. Something is wrong here. I would really appreciate any help.
Somethings you may need to know:
- Yes I have successfully gone back to KitKat before on the same phone.
- I have the correct Verizon Retail KitKat Software
- I have Odin 3.0.9
- I am running 5.0.1
- I have done a factory reset and cleared cache partition as well, but nothing seems to work.
Thanks, I look forward to your feedback!
Did you update OTA or flash the safe 5.0.1 update using odin? If you took the OTA upgrades then you are stuck, you will NOT be able to flash that phone again.
Sent from my Galaxy Note 4 using Tapatalk
outcasted2003 said:
Did you update OTA or flash the safe 5.0.1 update using odin? If you took the OTA upgrades then you are stuck, you will NOT be able to flash that phone again.
Sent from my Galaxy Note 4 using Tapatalk
Click to expand...
Click to collapse
I did download a security update after the initial 5.0.1 update, so I'm guessing that's what's doing it? Right after I posted my thread I saw the warning in this forum area, so I think that may be the case. I guess oh well, think there maybe a solution in the future for KitKat? Lollipop isn't too bad after a reset but I would prefer KitKat over time.
Related
Hi guys! I hope someone could help me. I just bought a Galaxy Note 3 (international version) yesterday. The phone's fine. It's just that I am unable to update. I am able to download it but when my phone reboots it shows a dead android with a red triangle on its chest. I read flashing the firmware via odin can fix it but problem is our internet is hella slow. I couldn't even complete downloading my brother's Note 2 firmware. Any way I can make it install the firmware successfully? By the way it's OTA. I am able to download the update, just won't let me finish installing it. Goes around 35% then the android on the black screen dies with a red triangle on its chest.
EDIT:
I have official firmware, never rooted, just got it yesterday. Still factory new.
version 4.3, build # JSS15J.N9005ZHUBMI7, baseband version N9005XXUBMI5, Kernel version 3.4.0-1626679
Have you tried reseting your phone go into recovery mode factory reset
Mygadgetgeek.com
mygadgetgeek.com said:
Have you tried reseting your phone go into recovery mode factory reset
Mygadgetgeek.com
Click to expand...
Click to collapse
not yet, but i have a lot of data now on my phone. will try that though. in case that doesn't work, any other advice?
cptnappy said:
Hi guys! I hope someone could help me. I just bought a Galaxy Note 3 (international version) yesterday. The phone's fine. It's just that I am unable to update. I am able to download it but when my phone reboots it shows a dead android with a red triangle on its chest. I read flashing the firmware via odin can fix it but problem is our internet is hella slow. I couldn't even complete downloading my brother's Note 2 firmware. Any way I can make it install the firmware successfully? By the way it's OTA. I am able to download the update, just won't let me finish installing it. Goes around 35% then the android on the black screen dies with a red triangle on its chest.
EDIT:
I have official firmware, never rooted, just got it yesterday. Still factory new.
version 4.3, build # JSS15J.N9005ZHUBMI7, baseband version N9005XXUBMI5, Kernel version 3.4.0-1626679
Click to expand...
Click to collapse
Was your phone brand new? And did you check your KNOX status? -- reason I ask, after you've rooted a phone you are unable to recieve OTA updates, unless you use Wanam to fake system status, then you can download the OTA update but it stalls on the install about 35% or so in..
Best advice, is grab the stock image from sammobile (ballache to download I know) then use ODIN to flash her back to original state.
radicalisto said:
Was your phone brand new? And did you check your KNOX status? -- reason I ask, after you've rooted a phone you are unable to recieve OTA updates, unless you use Wanam to fake system status, then you can download the OTA update but it stalls on the install about 35% or so in..
Best advice, is grab the stock image from sammobile (ballache to download I know) then use ODIN to flash her back to original state.
Click to expand...
Click to collapse
i didn't root the phone when i got it. it's fresh and on official firmware. have no idea about KNOX, that's new to me. if it helps, my device status says "official"
unfortunately the internet in my area is very slow, i couldn't download firmwares from sammobile. i tried several times
cptnappy said:
i didn't root the phone when i got it. it's fresh and on official firmware. have no idea about KNOX, that's new to me. if it helps, my device status says "official"
unfortunately the internet in my area is very slow, i couldn't download firmwares from sammobile. i tried several times
Click to expand...
Click to collapse
Ah Ok, if it says Official it should be good to go. Seems like maybe the download has gotten corrupt due to an intermittent internet connection.
cptnappy said:
i didn't root the phone when i got it. it's fresh and on official firmware. have no idea about KNOX, that's new to me. if it helps, my device status says "official"
unfortunately the internet in my area is very slow, i couldn't download firmwares from sammobile. i tried several times
Click to expand...
Click to collapse
OK, then maybe you should learn a few things before trying to update - Knox is a security system in latest Samsung phones that is supposed to be triggered/set when you root (or install any custom kernel/recovery). Your initial (old) firmware could still let you root without triggering the Knox flag, and then you can update to the latest firmware for your region using Mobile Odin Pro and still keep your root AND without triggering the Knox flag. However once you update using Samsung OTA / Odin / Kies to a firmware more recent than MJ3 you can no longer root without also triggering your Knox warrany flag - read more about this in the Universal Root De La Vega thread!
i gave up after several tries, since i'm on 4.3 i think that would do for now. maybe it's just downloading a stability update or something? everytime i do an OTA update, it tells me that the download of the new firmware is complete then reboot. when i get to 32% the droid falls flat on its back and shows the red triangle on its chest, over and over. i don't lose my phone data or anything. just won't update. i'll wait for 4.4 Kitkat instead. hope i'll be able to update to that when it comes out.
EDIT: i tried going into recovery mode, wiping cache, and factory reset.. still no dice. maybe Odin's the only way i guess. problem is my internet connection lol
@cptnappy - i also have the same problem...got my note3 n9005 a week ago and I also have the same problem as you....error at 30+%
tried update thru Kies with no luck...same error appears
Sent3 said:
@cptnappy - i also have the same problem...got my note3 n9005 a week ago and I also have the same problem as you....error at 30+%
tried update thru Kies with no luck...same error appears
Click to expand...
Click to collapse
i managed to update mine using Samsung Kies3 (not Kies, but Kies3). Hope updating OTA is fixed in the future with the update i just did
I had my S5 rooted a few months ago, but then the update came out that was supposed to fix the bluetooth (last July), and my phone automatically downloaded and tried to install it. My phone was still rooted, so the updated failed. However, my root also failed as well. I could no longer access root applications like Titanium Backup, and towel root told me that it was unable to root my phone. Basically, my phone became frozen in time and was unable to update or do root-level things since this update last July. Now that Lollipop is out, I really want to upgrade, but factory resets do not solve my problem and I do not know of any more permanent way to get my phone back to basics so thatr I can receive OTA updates and have them actually work. Any help is greatly appreciated, as I really do want to upgrade my phone.
Start by downloading your firmware from sammobile, then flash it with Odin......
You'll then be fully unrooted and should be able to receive OTAs......
BTW.....Some people on here say that if knox has been tripped, that can affect OTA too.......
If that is the case, simply download the lollipop firmware from sammobile and Odin flash that instead......no need to OTA upgrade then...
Sent from my rooted kn0x0 SM-G900F S5
keithross39 said:
Start by downloading your firmware from sammobile, then flash it with Odin......
You'll then be fully unrooted and should be able to receive OTAs......
BTW.....Some people on here say that if knox has been tripped, that can affect OTA too.......
If that is the case, simply download the lollipop firmware from sammobile and Odin flash that instead......no need to OTA upgrade then...
Sent from my rooted kn0x0 SM-G900F S5
Click to expand...
Click to collapse
Thank you for this advice. I used to flash stuff from my computer with my old phone, but haven't done so in years and didn't know which program to use. I was unsure if it worked at first, because my phone was the exact same after running Odin and I was expecting a factory reset, but I downloaded and ran the 4.4.4 update and it worked! Again, thanks so much for the help. I didn't really mind hitting "skip download until tomorrow" every day, but I wanted to upgrade to Lollipop.
Glad you got it sorted fella.......If it turns out that lollipop isn't all you'd hoped for, you can use odin to downgrade back to KitKat..........
.....but I think you have to remember to factory reset after the flash, otherwise you'll get bootloops and stuff......
Sent from my rooted kn0x0 SM-G900F S5
Hi everyone,
This is my first post and I hope that I am in the right section.
As per info in the thread title, I have a Malaysian Samsung Galaxy Note 3 updated to the last available firmware 4.4.2
I am trying to flash Lollipop with Odin (i followed all the instructions in the guide, literally step by step).
I have tried with the italian Lollipop update branded Vodafone, but Odin always failed and the phone was soft bricked.
I have reinstalled the original malaysian firmware 4.4.2 that i had prior this attempt. phone booted ok and worked perfectly fine.
Then i downloaded the lollipop firmware from poland, this thime odin completed the process and gives me a pass. but the phone goes in boot loop (samsung logo at booting never goes away). I have tried to reboot in recovery mode and wipe the cache. but still boot loop.
Would anyone be so kind to explain what i am doing wrong and how i could install lollipop on my malaysian galaxy note 3?
Any help would be much appreciated.
Luc81
Wipe all before flash lollipop.
Joku1981 said:
Wipe all before flash lollipop.
Click to expand...
Click to collapse
Thanks,
actually I have just managed to flash it correctly about 1 hour ago. i didn't need to wipe my data. Now it works properly.
Thanks anyway for your help!
hows your experience ?
just let us know what was the mistek, so others wont have to ask the same question again ...hehehe
all the best!
note 3 lolipop(Malaysia) N9005
Guys good news because this morning when I was checking my software update ... Thru Ota is about 860mb and thru keis 3 is about 1.3gb. Took me couple hours to download and about 1hour ++ to install. Booting up took some time and luckily everything is working fine for the time being.
Anyone updated and how's the battery draining issue.
i try update my note3 using kies3, it confirmed lollipop 5.0 available to update, but unfortunately my note3 repeatedly crash during upgrade and window on kies top up said "PC cant recognized my phone". Maybe cause of my knox warranty void 0x1 (trip). i hack on local C:\Users\YOUR NAME\AppData\Local\Temp and get copy of *.zip files (N9005DXUGBOD1_N9005OLBGBOD1_HOME.zip). It was lollipop firmware version for malaysia. Upgrade it using Odin and succesfull installed.
Lolipop
I was having the same issue while updating thru keis. So I downloaded it thru OTA. Battery sucks after lolipop. If you are facing any issue just send me a mail
I'm on the factory 5.0.1 image right now. What's happening is, when I download the OTA 5.1 image, it reboots and tries to install. Then I get the dead android with the red triangle.
I know that the answer is probably obvious, but I've been googling for about 3 days and can't find the original thread that had the instructions on how to install the custom modem. I know that if I put the factory modem back on, it will more likely than not fix the glitch.
I did NOT use Nexus 4 LTE flasher to update the modem, because at the time it wasn't working on Lollipop, I did the manual install method. Now that it is working, I downloaded it and tried to use it to install the stock modem. Well, that doesn't work, either. Dead Android on reboot.
Anyway, I can't find that original thread to manually install the factory modem firmware, so I can't do any OTA upgrades at this time.
Help me Obi Wan Kenobi, you're my only hope.
Nexus 4 5.1.0 LTE modem not working
theblooms said:
I'm on the factory 5.0.1 image right now. What's happening is, when I download the OTA 5.1 image, it reboots and tries to install. Then I get the dead android with the red triangle.
I know that the answer is probably obvious, but I've been googling for about 3 days and can't find the original thread that had the instructions on how to install the custom modem. I know that if I put the factory modem back on, it will more likely than not fix the glitch.
I did NOT use Nexus 4 LTE flasher to update the modem, because at the time it wasn't working on Lollipop, I did the manual install method. Now that it is working, I downloaded it and tried to use it to install the stock modem. Well, that doesn't work, either. Dead Android on reboot.
Anyway, I can't find that original thread to manually install the factory modem firmware, so I can't do any OTA upgrades at this time.
Help me Obi Wan Kenobi, you're my only hope.
Click to expand...
Click to collapse
I ran into the same problem. I used Skipsofts installer to dD/L the new 5.1 factory image and install because my OTA kept crashing.
Now I have lost 4g LTE on T-Mobile. back to 3G. I used Nexus Root Toolkit v2.0.5 to flash the LTE enabler but had no luck.
I'd like to hear how you are solving the problem? I did have LTE 4G while using Lollipop 5.0.2 but not since I went to 5.1.0
:good:
so i am an idiot and didn't do proper reading and tried to root my t-mobile S5 running 5.1.1 firmware using CF root method, which got it stuck on the startup samsung screen (with the "powered by android" at the bottom). factory reset and cache clear did not fix the problem. currently i am downloading the stock firmware for it, will take a while.
my questions are the following:
1. Am i doing the right steps to fix this problem? I assume downloading the stock firmware and flashing it with odin is the right thing to do.
2. I'm hearing some people who have had problems after unrooting S5's, saying that they are unable to receive official updates because they get an error saying the phone has been modified in an "unauthorized way" even after unrooting. something about a knox counter? sorry, i have no idea. What are the chances i run into this problem?
Yes, yes and yes. (I don't get the updates)
Sent from my SM-G900W8 using Tapatalk
I am getting the same message when it tried to update my s5 after almost bricking it while trying to flash a custom rom. Had to unroot it from what I'm told to fix the problem and I thought before it is rooted again I'd go ahead and b update. No such luck, man T mobile really wants us to have their darn TV app on our devices . Either way it won't let me update and I'm hoping there's a way around tha f before I gr ugh rooting b it b again. On the brigbt b side I was b able t ok b install Tasker again which for skme b reason seems to be a b issue with lollipop.