Hi,
I'm trying to upgrade my SM-900 (ha3g) from Kitkat to Lollipop.
I've flashed the latest TWRP and the 5.0 bootloader via ODIN.
I then use TWRP to flash the ROM (I've tried CM and a couple others) - I wipe the necessary file systems prior to wiping and then select the zip to flash it. It flashes fine. I reboot the system and after the Samsung SM-900 screen comes up, it just remains black. Nothing appears. I've waited quite a while in the event it was just initializing, but that's not the case. I've also tried to wipe the caches and factory reset AFTER flashing, but that does not fix the issue.
The phone will just not boot.
Anyone ever experience something like this?
Thanks!
Is a stock LP ROM available for your phone one sammobile.com? If there is, it can be flashed via Odin.
There is, before I try that, is that really my only option? I mean, there must be logical explanation as to why this is happening. I just can't find it via search here or on google .
Three things,
1- Make sure you are using a ROM for N900, not N9005.
2- Check the MD5 value of the ROM you are flashing.
3- How long are you waiting after flashing the ROM? It actually takes quite a long for the first boot, around 5 minutes or so.
Let us know what happens.
Tried those to no avail, unfortunately...
So I flashed a stock ROM with ODIN, and then flashed Cyanogen and it worked. Maybe the modem or some other image wasn't updated and interfering. No idea.
So, mystery solved.
Thanks guys .
Related
So I've been running a rooted Note 3 for a while. When the Note 3 Kitkat update came out, I updated it via Odin as OTA update was not available since I was rooted.
All the posts I read had mentioned that updating to 4.4.2 from 4.3 would erase all my data but after updating via odin all my data was in place. I had only lost root which I rooted again though CF Auto Root.
The problem now is that when I try to install CWM (via Odin) or TWRP (via Goo or Odin), it goes through the installation but then the phone goes into a boot loop of sorts..It's NOT the normal boot loop which gets stuck on the Samsung logo.
What happens is that the phone vibrates twice (with a 1 sec interval in between), then the Samsung Note 3 N-9005 screen appears with "Booting Recovery..." on the top left and within a sec it goes blank and then back to 2 vibrates and the screen come on to show Samsung Note 3 N-9005.
The only way I found to fix this was a battery pull and then turning on the device holding the power, home and down vol key to boot into recovery and then flashing CF Auto Root again.
I don't know why am I not able to install any of these recoveries. I've made sure I try to install the latest versions of them which are Kitkat compatible.
Anyone else with this problem or a solution?
Can a Cache and data wipe fix this? But the problem again being I won't be able to backup my ROM since i can't get these recoveries to install!
There is a script in official firmware that checks for official recovery and if it finds a custom one it tries to overwrite with official one. If i remember correct it's called install-recovery. sh
PhilZ recovery handles it automatically.
It's impossibe to flash anything other than the leaked 4.4.2 stock because you flashed your bootloader to kitkat, no you MUST stay on sammy 4.4.2 till the devs found a solution for this. Thats why you have to read carefully be4 you flash.
silentvisitor said:
There is a script in official firmware that checks for official recovery and if it finds a custom one it tries to overwrite with official one. If i remember correct it's called install-recovery. sh
PhilZ recovery handles it automatically.
Click to expand...
Click to collapse
No luck!
I tried PhilZ recovery from the below link.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltexx
What are my other options?
sid8907 said:
No luck!
I tried PhilZ recovery from the below link.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/hltexx
What are my other options?
Click to expand...
Click to collapse
This one seems to be the only one working with 4.4.2 right now.
Possible solution
The way I can suggest is to create a little update.zip file with little updater-script to remove install-recovery.sh file from device (just one line needed).
Ok, I found a zip which I am attaching below. You(or anyone) may review the script before flashing.
Place this on your external (or internal) sdcard.
In ODIN don't check Auto reboot
Flash Recovery. Remove phone when it says PASS.
Remove battery. Start in Recovery mode by pressing buttons.
You should now be in new Recovery.
Flash that zip file.
Reboot.
You should be good.
The Auto Reboot for some reason is faded out. Tried different versions of Odin and also tried to open it with the phone connected/disconnected.
I am out of ideas.
I would suggest you to wait for someone to come up with working solution. Being too adventurous with ODIN could brick your device.
sid8907 said:
The Auto Reboot for some reason is faded out. Tried different versions of Odin and also tried to open it with the phone connected/disconnected.
Click to expand...
Click to collapse
Clear out all your ODIN caches etc, delete all files and keep 1.85.
Flash this (only working recovery on 4.4.2) via PDA in ODIN, If it doesn't reboot auto after saying PASS or RESET.. just turn phone off, reboot into recovery and it'll be fine.
EDIT: Just re-read, Re flash your Stock 4.4.2 (Use XEO not the leaked one!) and then start again
Thanks!
Maybe a little off topic, but is there a way to install CM11 on Stock 4.4.2 on the Note 3?
I've been reading Samsung is out with a new bootloader so there is no way round this?
radicalisto said:
Clear out all your ODIN caches etc, delete all files and keep 1.85.
Flash this (only working recovery on 4.4.2) via PDA in ODIN, If it doesn't reboot auto after saying PASS or RESET.. just turn phone off, reboot into recovery and it'll be fine.
EDIT: Just re-read, Re flash your Stock 4.4.2 (Use XEO not the leaked one!) and then start again
Click to expand...
Click to collapse
Thanks!!
sid8907 said:
Thanks!
Maybe a little off topic, but is there a way to install CM11 on Stock 4.4.2 on the Note 3?
I've been reading Samsung is out with a new bootloader so there is no way round this?
Click to expand...
Click to collapse
You may have to do a little reading but I believe CM11 is now working on the KK bootloader...
sid8907 said:
So I've been running a rooted Note 3 for a while. When the Note 3 Kitkat update came out, I updated it via Odin as OTA update was not available since I was rooted.
All the posts I read had mentioned that updating to 4.4.2 from 4.3 would erase all my data but after updating via odin all my data was in place. I had only lost root which I rooted again though CF Auto Root.
The problem now is that when I try to install CWM (via Odin) or TWRP (via Goo or Odin), it goes through the installation but then the phone goes into a boot loop of sorts..It's NOT the normal boot loop which gets stuck on the Samsung logo.
What happens is that the phone vibrates twice (with a 1 sec interval in between), then the Samsung Note 3 N-9005 screen appears with "Booting Recovery..." on the top left and within a sec it goes blank and then back to 2 vibrates and the screen come on to show Samsung Note 3 N-9005.
The only way I found to fix this was a battery pull and then turning on the device holding the power, home and down vol key to boot into recovery and then flashing CF Auto Root again.
I don't know why am I not able to install any of these recoveries. I've made sure I try to install the latest versions of them which are Kitkat compatible.
Anyone else with this problem or a solution?
Can a Cache and data wipe fix this? But the problem again being I won't be able to backup my ROM since i can't get these recoveries to install!
Click to expand...
Click to collapse
here's the link for twrp for ya'll http://forum.xda-developers.com/showpost.php?p=50333147&postcount=398
sid8907 said:
So I've been running a rooted Note 3 for a while. When the Note 3 Kitkat update came out, I updated it via Odin as OTA update was not available since I was rooted.
All the posts I read had mentioned that updating to 4.4.2 from 4.3 would erase all my data but after updating via odin all my data was in place. I had only lost root which I rooted again though CF Auto Root.
The problem now is that when I try to install CWM (via Odin) or TWRP (via Goo or Odin), it goes through the installation but then the phone goes into a boot loop of sorts..It's NOT the normal boot loop which gets stuck on the Samsung logo.
What happens is that the phone vibrates twice (with a 1 sec interval in between), then the Samsung Note 3 N-9005 screen appears with "Booting Recovery..." on the top left and within a sec it goes blank and then back to 2 vibrates and the screen come on to show Samsung Note 3 N-9005.
The only way I found to fix this was a battery pull and then turning on the device holding the power, home and down vol key to boot into recovery and then flashing CF Auto Root again.
I don't know why am I not able to install any of these recoveries. I've made sure I try to install the latest versions of them which are Kitkat compatible.
Anyone else with this problem or a solution?
Can a Cache and data wipe fix this? But the problem again being I won't be able to backup my ROM since i can't get these recoveries to install!
Click to expand...
Click to collapse
jp.26 said:
here's the link for twrp for ya'll http://forum.xda-developers.com/showpost.php?p=50333147&postcount=398
Click to expand...
Click to collapse
so.... yeah i just updated my bootloader to 4.4.2 and this drove me literally insane. ive been working on it for 4 hours now. i encountered so many problems with installing the bootloader. exact same problem as SID8907. i gotta tell you tho.... you worked some magic my friend. i tried almost everything. then i came across your link. i was like why not? so i flashed the img in odin..... anddddd :drumroll pleaseeeeee:: IT WORKED. ahhh....... so much frustration and the problem is solved!!! thank you so much JP.26 :good::laugh:
is there any word on how to fix this been looking for hours tmobile note beast dont want to put any roots down on my phone before i find a way to flash cm or a non bloated note rom would be nice.
I'll that I've managed is to root and flash twrp I found a way to turn cwm recovery into a tar file and flash through odin. But i just get into a boot loop with cwm due to the boot loader I presume but tarp works fine I just can't flash cm11. I get boot loop every time
Sent from my SM-N900T using XDA Premium 4 mobile app
im sorry but im confused here... does this all simply mean that there is not yet a working cwm for 4.4.2 yet? and that while we can root, there is no working recovery for this version?
I'm not sure myself tarp works but I can't flash cm11
Sent from my SM-N900T using Tapatalk
Phillz cwm Dev edition I think that's the name works its a themed touch cwm. This works great but still can't flash cm so gayyyy
Sent from my SM-N900T using Tapatalk
I was wondering what happened to the cmw too.
The modded cmw by Chenglu is the only one working that I know of.
Link to thread: http://forum.xda-developers.com/showthread.php?t=2454079
I have a SM-N900W8 canadian note 3. I just installed new DOC4 lollipop rom via odin. I did clean install by wiping data. I root with CF-Root and flash latest TWRP. Everything seems to work perfectly until i try to made some small mod to add datamobile button in quicksettings using this thread. : http://forum.xda-developers.com/showthread.php?t=2342370
After it boots up to a black screen and a pop up shows up for nearly all of my apps that says they are not responding so all I get is that and a black screen. I reflash the rom via odin without wiping my data, re-root and everything went back fine and my mod works. ???!! I now have my datamobile button.
Later, i made a nandroid backup with TWRP. After reboot i got the same errors.... So i Reflash-rom, re-root, everything back to normal.
TO make a short story, everytime i access recovery or flash something in recovery or modify my system partition i got this errors....
I suspect having partition mismatched ... i don't know...
Any idea ???
Any help appreciated...
Which version of TWRP did you use? As far as I know, the latest only supports up to kitkat (4.4)
Maybe this is what causes your problems?
That's what i thought, I'm using the latest one (2.8.6.0). I ask other users in another thread and they said this version is working flawlessly with lollipop...
I have the same phone, and I flashed lollipop DOC4 using Odin yesterday, with CF-auto-root and TWRP 2.8.6.0.
I just tried (litterally minutes ago) adding the data toggle, and it worked, but I could not reproduce your problem.
Which version of TWRP did you use? The hltecan one or the hltexx?
Tornade69 said:
I have a SM-N900W8 canadian note 3. I just installed new DOC4 lollipop rom via odin. I did clean install by wiping data. I root with CF-Root and flash latest TWRP. Everything seems to work perfectly until i try to made some small mod to add datamobile button in quicksettings using this thread. : http://forum.xda-developers.com/showthread.php?t=2342370
After it boots up to a black screen and a pop up shows up for nearly all of my apps that says they are not responding so all I get is that and a black screen. I reflash the rom via odin without wiping my data, re-root and everything went back fine and my mod works. ???!! I now have my datamobile button.
Later, i made a nandroid backup with TWRP. After reboot i got the same errors.... So i Reflash-rom, re-root, everything back to normal.
TO make a short story, everytime i access recovery or flash something in recovery or modify my system partition i got this errors....
I suspect having partition mismatched ... i don't know...
Any idea ???
Any help appreciated...
Click to expand...
Click to collapse
1. Are you sure you installed correct TWRP? The correct one for your device: HERE.
2. Seems that mod for datamobile button doesn't work for your device. Reflash rom, re-root and don't install that mod. Try that update firmware for some days and tell me how it works :highfive:
I used HLTECAN 2.8.6.0. When i was on 4.4.2 NB7, i was using the same file and i had not problems at all. If you re-read my first post, i said my data toggle is working fine now but i needed to re-flash the entire rom without wiping data to get rid of the many apps errors. I guess i need to reflash everything from scratch... Will use another USB wire and another USB port. Maybe it'll help... Or maybe i should try another root method ??? I used CF-Root for SM-n900w8...
I suggest trying with hltexx, since it is the version I used, and I encountered no problem at all so far.
Let's check for any other difference between devices. I got :
Baseband N900W8VLUBMJ4
Bootloader N900W8UBUCNA2
PDA Version N900W8VLU2DOC4
CSC Version N900W8OYADOC4
Stock Kernel
how do you root n900w8 lollipop rom ?
phberb said:
I have the same phone, and I flashed lollipop DOC4 using Odin yesterday, with CF-auto-root and TWRP 2.8.6.0.
I just tried (litterally minutes ago) adding the data toggle, and it worked, but I could not reproduce your problem.
Which version of TWRP did you use? The hltecan one or the hltexx?
Click to expand...
Click to collapse
I want to root my n900w8 too ...tell me intrusions before tell is it safe .
phberb said:
I suggest trying with hltexx, since it is the version I used, and I encountered no problem at all so far.
Let's check for any other difference between devices. I got :
Baseband N900W8VLUBMJ4
Bootloader N900W8UBUCNA2
PDA Version N900W8VLU2DOC4
CSC Version N900W8OYADOC4
Stock Kernel
Click to expand...
Click to collapse
Hi, can I root N900W8 running N900W8UBU2DOG2 firmware from region TTT with twrp? If not is there any other method I can use to root my device ?
Alright, I have a Virgin Mobile S4. I rooted it a year ago with towelroot and installed clockwork mod on it to install cyanogenmod. I tried it, didn't like it so I restored my backup of the stock rom using CWM.
Fast forward to now. I tried to update my S4 OTA for Lollipop, but it would give me an error. I figured it was because I had changed the recovery software. So I went and downloaded the virgin mobile lollipop stock rom from sammobile. ( I337MVLUGOC4_I337MOYAGOC4_VMC ).
I tried to flash it onto my S4 using Odin 3.09. To no avail, it always failed at the system4.img.ext or something. From there I tried to make it work by using 3.10. Still failed. I googled for a fix or workaround and found something about reinstalling clockwork mod. I also tried reinstalling the PIT file for I337M. It was still not working. So I tried to flash back to my stock backup.
1st time I flashed, I kept having program that didn't want to start errors. I wiped dalvik, I wiped cache, I factory reset. Still bugged. So as a last resort I restored the backup again after having done all this. It worked! But...
Well, I'm at a lost now, I can't update using OTA, I can't update with Odin, I can't update with Kies. Now what? Is there a way to go back to the stock recovery and let the OTA or Kies update go through unhindered?
The proper place to ask this is in the AT&T S4 Forum as there are more people with that device who are able to help you. This is the International S4 forum, and while we can help you in a general sense, there may be something device specific we'll miss.
With that out of the way, with the ROM you downloaded, there would be no OTA updates when you installed it as it is the most current ROM available. Since Odin should have worked but didn't, you likely need to use a different USB port, and make sure you're not using a hub. Changing the port can often fix issues with Odin.
As @Strephon Alkhalikoi says this is not the place for it.
But there is one thing I notice. You are flashing an I337M firmware. Are you sure that's your model and you don't have an I337 (without M.
I need this fixed asap as I need my phone for school.. I have no idea what Happened honestly, I just restarted my phone and it started doing this. The only thing i recall doing is possibly disabling SuperSU on accident before I restarted my phone.
All I've done so far is download the stock firmware from SamMobile and attempted to flash it, but when i do i get an (auth) failed code from Odin, I've been searching for hours and haven't found anything that has helped..
If you have TWRP installed, try removing SuperSU via the file manager in recovery, or flash SuperSU again
The Auth! problem is likely due to you trying to flash an older ROM version than is installed, and the bootloader won't allow it
Tried clearing caches from recovery / factory reset?
Can you help with a newer model?
*Detection* said:
If you have TWRP installed, try removing SuperSU via the file manager in recovery, or flash SuperSU again
The Auth! problem is likely due to you trying to flash an older ROM version than is installed, and the bootloader won't allow it
Tried clearing caches from recovery / factory reset?
Click to expand...
Click to collapse
i don't have anything recovery installed, its jsut the normal android recovery. I thought about reflashing supersu but I'm not sure how without a recovery..
Have you tried the factory reset from normal recovery?
*Detection* said:
Have you tried the factory reset from normal recovery?
Click to expand...
Click to collapse
Yea.. Ive hit it so many times Id be surprised if it even remembers how to power on lol..
What about a SM-G900P?
TheAgonistxX said:
Yea.. Ive hit it so many times Id be surprised if it even remembers how to power on lol..
Click to expand...
Click to collapse
Lost count of the number of threads about bricked G900A and G900P these last few weeks
Something about the latest Lollipop firmware, locks the bootloader from downgrading, even to just an earlier version of Lollipop, and it's a nightmare to try and find ODIN flashable ROMs for the latest release
Right now, unless someone else can think of something, all I can suggest is either taking / sending it in for repair, or wait for Marshmallow to arrive, and hope an ODIN flashable ROM arrives for that
Might as well give flashing TWRP a try (via ODIN), I don't expect it will work, but if you could get custom recovery running, you might be able to flash a custom ROM
Another thread with a similar issue, you could try this, but I'm expecting the same Auth! error
http://forum.xda-developers.com/showpost.php?p=65234333&postcount=28
*Detection* said:
Lost count of the number of threads about bricked G900A and G900P these last few weeks
Something about the latest Lollipop firmware, locks the bootloader from downgrading, even to just an earlier version of Lollipop, and it's a nightmare to try and find ODIN flashable ROMs for the latest release
Right now, unless someone else can think of something, all I can suggest is either taking / sending it in for repair, or wait for Marshmallow to arrive, and hope an ODIN flashable ROM arrives for that
Might as well give flashing TWRP a try (via ODIN), I don't expect it will work, but if you could get custom recovery running, you might be able to flash a custom ROM
Another thread with a similar issue, you could try this, but I'm expecting the same Auth! error
http://forum.xda-developers.com/showpost.php?p=65234333&postcount=28
Click to expand...
Click to collapse
Tried flashing TWRP with the same end result.. This is dumb really frustrating -.- is there any way to install Supersu without a recovery?
CF Auto Root, but it'll likely fail too due to the bootloader
II have been working on mine same model and it is because once you screw up ,which i did,the locked boot loader wont let anything by. a relative pretty much started the problem by flashing a ROM and erasing everything. this one wont even go into recovery. still wont give up until I figure out a way just because.......
Hello everyone. I used Albe95 N5+S6 Port rom for my GT-i9500 and it worked flawlessly. I had TWRP recovery. After a lot of using I thought to re-flash the rom and start using it new, so I reinstalled the Rom file on my external SD card and flashed the rom using TWRP recovery and it was a success, but then I noticed I accidentally backed up some things which I didn't wanted to I re-flashed the Rom again, but this time when I (in recovery mode) wiped the data, I chose "Advanced Wipe" or "Advanced Reset" (It was something like that I don't exactly remember. So after that I reflashed the rom and when I had to press "Reboot" a message appeared above saying "Looks like super user is not installed in your phone. Do you wish to install it?" I said Yes and the screen went blank. I tried to reboot but It didn't. I removed the battery and then put it back again and tried to get into recovvery but recovery seemed to be lost and I ended up in Samsung's own factory mode where we have options like reboot, flash using external sd card, flash using adb, enable cp logging and etc. I tried to flash back everything but nothing works. Tried Odin and tried flashing custom firmware but it fails. If I reboot Samsung Galaxy S4 GT-i9500 comes on screen and then it goes blank no boot animation or anything like that. Please help me, Your help will be highly appreciated
I used advanced wipe many times before, I'm pretty sure something else caused your dilema.
And most Odin fail messages are caused by the USB cable, PC USB ports (back ports are recommended) and Windows version.
So what should I do now?
If the problems are caused by the above mentioned, you should obviously try to change things up.
It appears that your phone is in soft-brick.
Also, you lost your TWRP.
Check your bootloader version and install the stock firmware via odin. (If you still fail in odin, As GDreaper pointed out, odin fail could cause by usb cable, port and windows version so you need to keep changing until it works)
Root the phone. Reinstall the TWRP.
Then flash the custom rom again. When you install the custom rom please follow the cooker (custom rom maker) instructions on wiping.
Thanks for your comment. I'm kind of a noob, how do I check bootloader version? and how will I know after checking my bootloader version which stock firmware to install?
Bootloader has nothing to do with it.
If you flash a stock firmware, the Bootloader will also be updated to whatever Bootloader the download firmware has.
The only situation where the Bootloader would matter is if you try to go from lollipop to kitkat, in which case it will fail.
Thank you. My device is back now.
I am glad to hear that your problem is solved.
When I was on kit-kat, I did not check my bootloader version and flash the stock firmware with older version of bootloader which tripped the knox counter on my i 9500. That was why I said to check the bootloader version before installing the stock firmware. You can use app like phone info to see the bootloader info. Then install the firmware with the same or newer bootloader.
I recomend to Update drivers, Windows, Bootloader install Samsung Kies and Install TWRP again, After stock