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
So, I'm having a big problem with my S4 at the moment. After having some problems with several apps, being that I couldn't properly open, restore, or uninstall them (I think it has to do with Foldermount), I decided to format my external SD card, and perform a factory reset. Everything seemed like it was working well, and when it rebooted and asked if I wanted to repair root access, I said 'yes' (not sure if that has anything to do with the issue). Then, after some time, it went on with the boot up. However, it was stuck at the samsung logo. So, I tried to go into download mode, like people were suggesting. I held down UP volume, and the power button, but all this does for me is turn off the device. I can't seem to get into recovery mode to perform another reset, and I can't even get into download mode. Also, when I try to turn off my phone using the power button, while it's in the seemingly infinite boot up, it instantly turns back on. The only way I can turn it off is by removing the battery. So, any help would be greatly appreciated, I have no idea what to do. Thanks in advance
To get into download mode hold vol down, power, and home buttons. You might have to flash the stock firmware in Odin at this point. What recovery are you using?
Sent from my Nexus 5 using XDA Free mobile app
Huh, well, download mode works. Could've sworn I'd already tried that combination. I guess I'll try using Odin. Sorry, what do you mean by 'what recovery'?
Update: Just tried the flash recovery with Odin. I think I did it right. I then went into recovery mode (turns out was doing it wrong), and cleared the caches, did another factory reset, then did the recovery reboot. Even after that, I still can't get past the infinite boot up load screen. Any suggestions? Thanks
lordcrunch said:
Update: Just tried the flash recovery with Odin. I think I did it right. I then went into recovery mode (turns out was doing it wrong), and cleared the caches, did another factory reset, then did the recovery reboot. Even after that, I still can't get past the infinite boot up load screen. Any suggestions? Thanks
Click to expand...
Click to collapse
What recovery are you trying to flash in Odin? And do you know what firmware version your device is on? my guess is that you're on a firmware version that you can't use a custom recovery other than safestrap. You're most likely going to have to flash the stock firmware in Odin to get your device to work.
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
What recovery are you trying to flash in Odin? And do you know what firmware version your device is on? my guess is that you're on a firmware version that you can't use a custom recovery other than safestrap. You're most likely going to have to flash the stock firmware in Odin to get your device to work.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
I'm currently trying to find a proper download link for the stock firmware for my phone. My version is 4.4.2 by default. I was trying to flash the wrong recovery at first, and then I tried a clockworkmod touch recovery, which hasn't helped. Unfortunately, I can't find a legit download for the stock firmware. I337MVLUFNI2 – TLS, it's the name of the stock version of my phone, while using the latest 4.4.2
lordcrunch said:
I'm currently trying to find a proper download link for the stock firmware for my phone. My version is 4.4.2 by default. I was trying to flash the wrong recovery at first, and then I tried a clockworkmod touch recovery, which hasn't helped. Unfortunately, I can't find a legit download for the stock firmware. I337MVLUFNI2 – TLS, it's the name of the stock version of my phone, while using the latest 4.4.2
Click to expand...
Click to collapse
You have an i337m. Go to sammobile.com for the stock firmware.
Sent from my Nexus 5 using XDA Free mobile app
Your not using the right stock firmware do as above said.
So About 2 months ago, I attempted to downgrade from lolipop 5.0 to kitkat 4.4.2. After seeing 30+ guides that were more or less identical all claiming success, I tried flashing The kitkat firmware, and instead of downgrading ended up with my phone stuck in a bootloop. Now after seeing another 30+ guides on how to fix your softbricked phone, all claiming success, downloading countless files, including 4 or 5 different versions of odin, I have made no progress. I made a thread about a month ago asking for tar files for the lolipop 5.0 firmware. I got several responses, directing me twoards links that they hadnt even bothered to check if it contained the 5.0 firmware, because the websites didnt. None of the "official sites where you'd get android firmware from have the lolipop 5.0 firmware. NOTICE: PLEASE DO NOT SUGGEST FLASHING STOCK FIRMWARE, OR FLASHING VARIOUS VERSIONS OF KITKAT, I HAVE TRIED THIS AT LEAST 50 TIMES IN 4 DIFFERENT VERSIONS OF ODIN, YOU CAN NOT DOWNGRADE. idk if this is the same for all android phones, but when your phone is stuck in a bootloop, you cannot charge the battery. So after spendings over 15 hours trying to fix my phone and taking a road trip, I came back to find my battery dead. After getting back I bought a micro sd card for my phone. However connecting your phone to your computer will not let you enter recovery mode. Therefore the 5.0 firmware I had on the sd card could not be copied to my phone through recovery mode (I have found lolipop 5.0 firmware, however it isnt flashable, rather it is a large collection of various file types and sub folders.) Eventually I was able to recharge my battery by flashing/installing twrp recovery. The next day I copied the 5.0 firmware from the sd card to the phone. At first it appeared to work" "installing update" then it rebooted and bam, back to the twrp recovery mode screen. With twrp recovery on, I am not able to access normal recovery mode, just download mode and the modified recovery mode.
Here is the screen when my s5 boots:
[red text] android system recovery <3e>
KOT49H.G900AUCU1ANCE
volume up/down to move highlight;
power button to select [/red text]
[blue text] reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache [/blue text]
picture of dead android centered with its chest open and red triangular exclamation sign in chest
directly underneath the android: no command.
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : ATT
Successfully applied multi-CSC
thats whats on the screen, please ignore the code tags, that was stating the color of the text
Now ive tried messing around with ADB from the android sdk but all of those commands arent recognized by windows cmd. I've read several tutorials to try and get them recognized but cant find any of the needed files because where the files are saved on your pc appear to have competely changed since the tutorials are made. Im also not sure if I should or How to remove twrp recovery.
Just to specify again, I have a Samsung Galaxy S5 g900A (AT&T) that was running some early varriant of Lolipop 5.0 (updated in may) before it unfortunately lost its operating system.
I believe you are unable to post links here so please send them to meowmix226(at)gmail(dot)com with xda as the subject
If any of you kind souls on xda can fix this, you will be rewarded.
Any help or new insights is greatly appreciated
thank you
-Kyle
fluffyseal said:
So About 2 months ago, I attempted to downgrade from lolipop 5.0 to kitkat 4.4.2. After seeing 30+ guides that were more or less identical all claiming success, I tried flashing The kitkat firmware, and instead of downgrading ended up with my phone stuck in a bootloop. Now after seeing another 30+ guides on how to fix your softbricked phone, all claiming success, downloading countless files, including 4 or 5 different versions of odin, I have made no progress. I made a thread about a month ago asking for tar files for the lolipop 5.0 firmware. I got several responses, directing me twoards links that they hadnt even bothered to check if it contained the 5.0 firmware, because the websites didnt. None of the "official sites where you'd get android firmware from have the lolipop 5.0 firmware. NOTICE: PLEASE DO NOT SUGGEST FLASHING STOCK FIRMWARE, OR FLASHING VARIOUS VERSIONS OF KITKAT, I HAVE TRIED THIS AT LEAST 50 TIMES IN 4 DIFFERENT VERSIONS OF ODIN, YOU CAN NOT DOWNGRADE. idk if this is the same for all android phones, but when your phone is stuck in a bootloop, you cannot charge the battery. So after spendings over 15 hours trying to fix my phone and taking a road trip, I came back to find my battery dead. After getting back I bought a micro sd card for my phone. However connecting your phone to your computer will not let you enter recovery mode. Therefore the 5.0 firmware I had on the sd card could not be copied to my phone through recovery mode (I have found lolipop 5.0 firmware, however it isnt flashable, rather it is a large collection of various file types and sub folders.) Eventually I was able to recharge my battery by flashing/installing twrp recovery. The next day I copied the 5.0 firmware from the sd card to the phone. At first it appeared to work" "installing update" then it rebooted and bam, back to the twrp recovery mode screen. With twrp recovery on, I am not able to access normal recovery mode, just download mode and the modified recovery mode.
Here is the screen when my s5 boots:
[red text] android system recovery <3e>
KOT49H.G900AUCU1ANCE
volume up/down to move highlight;
power button to select [/red text]
[blue text] reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache [/blue text]
picture of dead android centered with its chest open and red triangular exclamation sign in chest
directly underneath the android: no command.
# MANUAL MODE #
-- Appling Multi-CSC...
Applied the CSC-code : ATT
Successfully applied multi-CSC
thats whats on the screen, please ignore the code tags, that was stating the color of the text
Now ive tried messing around with ADB from the android sdk but all of those commands arent recognized by windows cmd. I've read several tutorials to try and get them recognized but cant find any of the needed files because where the files are saved on your pc appear to have competely changed since the tutorials are made. Im also not sure if I should or How to remove twrp recovery.
Just to specify again, I have a Samsung Galaxy S5 g900A (AT&T) that was running some early varriant of Lolipop 5.0 (updated in may) before it unfortunately lost its operating system.
I believe you are unable to post links here so please send them to meowmix226(at)gmail(dot)com with xda as the subject
If any of you kind souls on xda can fix this, you will be rewarded.
Any help or new insights is greatly appreciated
thank you
-Kyle
Click to expand...
Click to collapse
I dont care if its not what you want to hear, you need to flash stock lollipop. Part of your issue is that the g900a is you cannot flash recoveries, so even though the twrp flash may have been succssful it didnt actually flash, the recovery menu you described is stock recovery. So end of story, stock flash lollipop, if you got it from OTA you cant downgrade so dont try again, and you cant root.
Sent from my Tw5ted SM-G900A using Tapatalk
---------- Post added at 22:02 ---------- Previous post was at 21:58 ----------
Rakuu said:
I dont care if its not what you want to hear, you need to flash stock lollipop. Part of your issue is that the g900a is you cannot flash recoveries, so even though the twrp flash may have been succssful it didnt actually flash, the recovery menu you described is stock recovery. So end of story, stock flash lollipop, if you got it from OTA you cant downgrade so dont try again, and you cant root.
Sent from my Tw5ted SM-G900A using Tapatalk
Click to expand...
Click to collapse
This looks like what you need http://forum.xda-developers.com/showthread.php?t=
Sent from my Tw5ted SM-G900A using Tapatalk
Rakuu said:
I dont care if its not what you want to hear, you need to flash stock lollipop. Part of your issue is that the g900a is you cannot flash recoveries, so even though the twrp flash may have been succssful it didnt actually flash, the recovery menu you described is stock recovery. So end of story, stock flash lollipop, if you got it from OTA you cant downgrade so dont try again, and you cant root.
Sent from my Tw5ted SM-G900A using Tapatalk
---------- Post added at 22:02 ---------- Previous post was at 21:58 ----------
This looks like what you need http://forum.xda-developers.com/showthread.php?t=
Sent from my Tw5ted SM-G900A using Tapatalk
Click to expand...
Click to collapse
It said no thread specified on the link you posted, and there doesnt appear to be a flashable version of lolipop. the only version of lolipop I was able to find was a collection of files and folders in various syntax's. No .tar files, If you know of one that round be really helpful, when i bought my s5 it was on kitkat.
fluffyseal said:
It said no thread specified on the link you posted, and there doesnt appear to be a flashable version of lolipop. the only version of lolipop I was able to find was a collection of files and folders in various syntax's. No .tar files, If you know of one that round be really helpful, when i bought my s5 it was on kitkat.
Click to expand...
Click to collapse
i am sorry i can understand the frustration you are going through i am not an expert on anything just going to try to help you with whatever limited knowledge i have.
First of all download pit file from here http://forum.xda-developers.com/showthread.php?t=2737448 (download the one for 900a 16 gb) version if ur phone is 16gb.
Second download this http://www.sammobile.com/firmwares/download/28224/G900AUCU1ANCE_G900AATT1ANCE_ATT/
Third, download odin 3.10.6 from http://forum.xda-developers.com/showthread.php?t=2711451
Procedure > Peform a factory reset in recovery + clear cache if you can otherwise ignore this step
1) turn off the phone completely
2)Put it in download mode (volume down + menu+ power) and then press volume up for confirmation when it asks.
4)Open Odin on your Pc
5) connect phone "ID:COM" should blink greenish.
6) Click on AP and choose the firmware you downloaded from sammobile (you may need to extract it otherwise it wont be visible here)
7 open the "PIT tab" on odin and select the pit file you downloaded before.
8 open options tab on odin and check "Re-partition" Keep "autoreboote and f reset time checked" ...no other options then these 3 should be checked"
8 click start.
9 Kindly report back if it worked.
dork997 said:
i am sorry i can understand the frustration you are going through i am not an expert on anything just going to try to help you with whatever limited knowledge i have.
First of all download pit file from here http://forum.xda-developers.com/showthread.php?t=2737448 (download the one for 900a 16 gb) version if ur phone is 16gb.
Second download this http://www.sammobile.com/firmwares/download/28224/G900AUCU1ANCE_G900AATT1ANCE_ATT/
Third, download odin 3.10.6 from http://forum.xda-developers.com/showthread.php?t=2711451
Procedure > Peform a factory reset in recovery + clear cache if you can otherwise ignore this step
1) turn off the phone completely
2)Put it in download mode (volume down + menu+ power) and then press volume up for confirmation when it asks.
4)Open Odin on your Pc
5) connect phone "ID:COM" should blink greenish.
6) Click on AP and choose the firmware you downloaded from sammobile (you may need to extract it otherwise it wont be visible here)
7 open the "PIT tab" on odin and select the pit file you downloaded before.
8 open options tab on odin and check "Re-partition" Keep "autoreboote and f reset time checked" ...no other options then these 3 should be checked"
8 click start.
9 Kindly report back if it worked.
Click to expand...
Click to collapse
That is NCE(4.4.2), that wont help, they need stock lollipop.
Sent from my Tw5ted SM-G900A using Tapatalk
i have pmed you the link for stock lollipop.
dork997 said:
i have pmed you the link for stock lollipop.
Click to expand...
Click to collapse
You PMed the wrong person, just lwtting you know, op needs it not me.
Sent from my Tw5ted SM-G900A using Tapatalk
dork997 said:
i have pmed you the link for stock lollipop.
Click to expand...
Click to collapse
also could you please include a brief tutorial such as what should i flash (everything but the bootloader etc) and what version of odin should i use
tysm
I just wrote an essay on that....please read above u have to flash the whole Os + pit file. Try with kitkat
dork997 said:
I just wrote an essay on that....please read above u have to flash the whole Os + pit file. Try with kitkat
Click to expand...
Click to collapse
Rakuu said:
You PMed the wrong person, just lwtting you know, op needs it not me.
Sent from my Tw5ted SM-G900A using Tapatalk
Click to expand...
Click to collapse
Sorry for the delayed response. So I tried the method and it didnt work but It was stated that I needed stock lolipop. However dork pmed it to the wrong person. Could i get a link for that please.
Thanks!
fluffyseal said:
Sorry for the delayed response. So I tried the method and it didnt work but It was stated that I needed stock lolipop. However dork pmed it to the wrong person. Could i get a link for that please.
Thanks!
Click to expand...
Click to collapse
This thread has oc4 http://forum.xda-developers.com/showthread.php?t=3137519 i dont see any reason why it wouldnt work with of2, its the KK roms you can't flash.
Sent from my Tw5ted SM-G900A using Tapatalk
rakuu said:
this thread has oc4 http://forum.xda-developers.com/showthread.php?t=3137519 i dont see any reason why it wouldnt work with of2, its the kk roms you can't flash.
Sent from my tw5ted sm-g900a using tapatalk
Click to expand...
Click to collapse
that thread had the solution thank you so much
giving you and everyone else on this thread thanks on each of your posts
2 days ago i flashed twrp on my pure stock note 4, i did backup my rom including EFS using twrp and then flash kyubi rom with nameless kernel, it all went well. just now i wipe data ,system, cache on twrp and restore my backup stock rom and it went well too...and then i try to flash stock rom using odin so i can get back the stock recovery mode for OTA update when MM releases.. the flashing was a sucess and phone booted but my data inside werent wipe.
so i went to recovery mode and saw this dm-verity verification failed on the bottom i proceed to wipe data and reboot my phone, its all working now no problems except i cant reset my phone with the setting inside it will just bring me to recovey mode and stay there with that message.
now i did some research, some saying will bootloop and stuffs but mine is all ok no problem except i cant reset it inside the settings..
anyone can help me get rid of that message/problem?
If you format everything in advance format in twrp and then flash stock firmware this message will go away.
got the same problem. Then I went to a local store. They helped me. Here are steps
1. Pull out your battery, check your serial number (S/N:....)
2. Download smart switch, enter emergency software recovery..... Enter your serial number
3. Turn off your phone. Enter download mode or sth ( I don't remember it clearly. just power + vol down or up. just try it)
4. Smart switch will recognize your phone. Choose a firmware to download. then wait
5. Enjoy stock firmware
Use kies3 reinstall drivers, then use emergency recovery in kies to reinstall your current firmware or opt to update to latest or most recent release or version then follow kies instructions
rooted s5 smg900r4
Hello everyone
I have found a way to fix dm-verity and DRK issues and it works like official, meaning no errors in stock recovery and OTA works with Official firmware, the problem is related to corrupted/deleted 3 files on /efs partition. I have tested it on SM-N910C so I guess it works on other Exynos variants, perhaps even on snapdragon if the partition layout is similar? Kies won't restore DRK or dm-verity check because it doesn't write to EFS. I can fix yours if someone is interested via Team Viewer, you will need the following:
1. PM contact me for Skype ID
2. Stock rom, rooted (any root method)
3. Adb debugging enabled and drivers installed (Kies or SmartSwitch)
After repair you can enter your stock recovery and confirm there is no DRK/dm-verity red letters error.
Regards,
magix01
please guide us the proceedure here .. i have a phone with same problem & i have to update it to MM ...
dork997 said:
If you format everything in advance format in twrp and then flash stock firmware this message will go away.
Click to expand...
Click to collapse
Mine still says fail. but it also says "need to check drk first" could anyone possibly help me im stuck.the phone loads up and everything. but when i try to root or anything or flash any other firmware than n910pvpu5dqi5 it fails about 4 seconds in to flashing on odin. ive downloaded every possible firmware specific to the SM-N910P but only one worked.
im a big noob with the note 4 this is my first luckily its not my daily phone yet. im very familiar with the note 3 n900t but im finding they are very different. any advice would be appreciated!
Sir, please reply
When i unlocked my bootloader on my redmi phone this warning comes, but after clicking power button it will successfully boot to system but i m confused did i flash any rom in it, is it safe or not
Manish_k said:
Sir, please reply
When i unlocked my bootloader on my redmi phone this warning comes, but after clicking power button it will successfully boot to system but i m confused did i flash any rom in it, is it safe or not
Click to expand...
Click to collapse
If you just unlocked your bootloader and thats it, your rom should still be the stock one.
Hi,
My phone has TWRP installed and I have tried getting into recovery with vol up, home and power but I just get stuck on the regular boot screen (Samsung Galaxy S5 with Set Warranty Bit: Kernel). I have tried using Odin to flash TWRP in download mode (no Pit file error) which fails. I can't get my device to show up in adb or fastboot. I can't enable USB debugging because my device won't boot.
The only mode I can get into is download mode (vol down, home and power). Is there any hope of getting into recovery or accessing my files from there?
I have read through countless threads and posts without finding a solution. I really appreciate any suggestions.
Device: SM-G900T
zanmat0 said:
Hi, My phone has TWRP installed and I have tried getting into recovery with vol up, home and power but I just get stuck on the regular boot screen (Samsung Galaxy S5 with Set Warranty Bit: Kernel). I have tried using Odin to flash TWRP in download mode (no Pit file error) which fails. I can't get my device to show up in adb or fastboot. I can't enable USB debugging because my device won't boot...
Click to expand...
Click to collapse
I don't have this variant but, your best bet is to post this question within the following Official TWRP thread for your device.
https://forum.xda-developers.com/showthread.php?t=2727406
If all else fails, try posting your question within the following Q&A thread that's specific to your device.
https://forum.xda-developers.com/showthread.php?t=2700073
Good Luck!
~~~~~~~~~~~~~~~
I DO NOT PROVIDE SUPPORT VIA PM UNLESS ASKED/REQUESTED BY MYSELF.
PLEASE KEEP IT IN THE THREADS WHERE EVERYONE CAN SHARE
zanmat0 said:
............
The only mode I can get into is download mode (vol down, home and power). Is there any hope of getting into recovery or accessing my files from there?
.........
Device: SM-G900T
Click to expand...
Click to collapse
Hi,
That's not a good symptom.
Just to be sure:
Did you try installing full stock firmware from odin via download mode?
Does download mode confirm that your phone model is SM-G900T? Is that model in line with a label under the battery?
Many40 said:
Hi,
That's not a good symptom.
Just to be sure:
Did you try installing full stock firmware from odin via download mode?
Does download mode confirm that your phone model is SM-G900T? Is that model in line with a label under the battery?
Click to expand...
Click to collapse
I tried installing TWRP with Odin, if I install stock firmware, will all my data be wiped? All I wanted was to get into TWRP to save the data.
Yes download mode confirms SM-G900T same as under battery.
zanmat0 said:
I tried installing TWRP with Odin, if I install stock firmware, will all my data be wiped? All I wanted was to get into TWRP to save the data.
Yes download mode confirms SM-G900T same as under battery.
Click to expand...
Click to collapse
The question is what happened before that your phone doesn't boot?
If a phone doesn't boot the basic way to fix it is to reflash it with stock firmware. It will not wipe your files in internal storage like pictures, downloads etc but it will most likely wipe your apps, settings, contacts, messages etc.
By the way what version of TWRP have you tried installing?
Many40 said:
The question is what happened before that your phone doesn't boot?
If a phone doesn't boot the basic way to fix it is to reflash it with stock firmware. It will not wipe your files in internal storage like pictures, downloads etc but it will most likely wipe your apps, settings, contacts, messages etc.
By the way what version of TWRP have you tried installing?
Click to expand...
Click to collapse
OK I tried reflashing with stock firmware, but same error "There is no pit binary. Flash read failure".
TWRP 3.2.1.
The thing is I'm not sure what happend because my screen broke, the phone was still working fine but I tried to reboot into recovery without a functional screen many times, perhaps some combination of buttons I pressed bricked it...
zanmat0 said:
OK I tried reflashing with stock firmware, but same error "There is no pit binary. Flash read failure".
TWRP 3.2.1.
The thing is I'm not sure what happend because my screen broke, the phone was still working fine but I tried to reboot into recovery without a functional screen many times, perhaps some combination of buttons I pressed bricked it...
Click to expand...
Click to collapse
Try to falsh this firmware only file with TWRP and pit (use AP slot in Odin): https://mega.nz/#!XksGAThB!oQnTcnp7YHJfEfekbQMaihm2SGItBNMihPPfzQehUq4
You cannot brick the phone with just a buttons' pressing.
To say the truth, your story sounds like a memory failure and there's almost no chance to get your data.
bbsc said:
Try to falsh this firmware only file with TWRP and pit (use AP slot in Odin): https://mega.nz/#!XksGAThB!oQnTcnp7YHJfEfekbQMaihm2SGItBNMihPPfzQehUq4
You cannot brick the phone with just a buttons' pressing.
To say the truth, your story sounds like a memory failure and there's almost no chance to get your data.
Click to expand...
Click to collapse
Same error looks like (There is no PIT binary).
I see, well in any case, thank you very much for your help. Its bizarre because the phone was working fine as the screen was slowly breaking up until it finally went dark forever.
A bit late to the party, but I found my GS5 wouldn't go into recovery if the USB/Charge cable was plugged in.
zanmat0 said:
Same error looks like (There is no PIT binary).
I see, well in any case, thank you very much for your help. Its bizarre because the phone was working fine as the screen was slowly breaking up until it finally went dark forever.
Click to expand...
Click to collapse
If Odin is requiring the PIT file for the SM-G900T device, you can obtain it on the following link.
Downloads for : Samsung Galaxy S5 | AndroidFileHost.com | Download GApps, Roms, Kernels, Themes, Firmware and more. Free file hosting for all Android developers.
Download GApps, Roms, Kernels, Themes, Firmware, and more. Free file hosting for all Android developers.
www.androidfilehost.com
The PIT file is the Partition Information Table that Odin uses for what goes into which partition from the Firmware.
I hope I had explained this okay via text.
There's a little helper guide on the following thread as well.
[FIRMWARE/PIT]T-Mobile Samsung Galaxy S5{SM-G900T/KLTETMO}[ODIN]
OFFICIAL FIRMWARE/PIT COLLECTION T-Mobile Samsung Galaxy S5 {SM-G900T/KLTETMO} {The above image is a refrence of all the Stock Firmware, Release Dates, etc...} CLICK HERE TO EXPANDED THE ABOVE IMAGE DISCLAIMER/FYI - This thread DOES...
forum.xda-developers.com
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. [Sent from the room next door.]
Many40 said:
Hi,
That's not a good symptom.
Just to be sure:
Did you try installing full stock firmware from odin via download mode?
Does download mode confirm that your phone model is SM-G900T? Is that model in line with a label under the battery?
Click to expand...
Click to collapse
Just an FYI...
The attached image is an example of where to locate the actual model number of your device (which is the second line down from the top of the screen).
Good Luck!
~~~~~~~~~~~~~~~
Unless asked to do so, PLEASE don't PM me regarding support. [Sent from the room next door.]