Hello,
I've tried flashing the CF-Auto-Root, Philz recovery and TWRP. All keep failing with:
ODIN: <IDL0/005> FAIL! (Auth)
Phone: SECURE CHECK FAIL : recovery
I'm not new to flashing, I've done it many, many, many times to my S4 and others S4s with no issues. I'm using Odin 3 v3.07, even tried the copy that came with the CF-Auto-Root package. Using the PDA box, Re-Partition is not checked. connecting the phone before or after setting up Odin. Tried following the quid in the CF-Auto-Root thread to the T... Always resulting in the same.
I've got an SM-G9000W8 and there has not been an OTA update for it.
Any ideas?
HappyDude69 said:
Hello,
I've tried flashing the CF-Auto-Root, Philz recovery and TWRP. All keep failing with:
ODIN: <IDL0/005> FAIL! (Auth)
Phone: SECURE CHECK FAIL : recovery
I'm not new to flashing, I've done it many, many, many times to my S4 and others S4s with no issues. I'm using Odin 3 v3.07, even tried the copy that came with the CF-Auto-Root package. Using the PDA box, Re-Partition is not checked. connecting the phone before or after setting up Odin. Tried following the quid in the CF-Auto-Root thread to the T... Always resulting in the same.
I've got an SM-G9000W8 and there has not been an OTA update for it.
Any ideas?
Click to expand...
Click to collapse
You already asked this in philz cwm device related thread ?? instead of making this thread..
cheers
Sent from my GT-I9506 using XDA Premium 4 mobile app
HappyDude69 said:
Hello,
I've tried flashing the CF-Auto-Root, Philz recovery and TWRP. All keep failing with:
ODIN: <IDL0/005> FAIL! (Auth)
Phone: SECURE CHECK FAIL : recovery
I'm not new to flashing, I've done it many, many, many times to my S4 and others S4s with no issues. I'm using Odin 3 v3.07, even tried the copy that came with the CF-Auto-Root package. Using the PDA box, Re-Partition is not checked. connecting the phone before or after setting up Odin. Tried following the quid in the CF-Auto-Root thread to the T... Always resulting in the same.
I've got an SM-G9000W8 and there has not been an OTA update for it.
Any ideas?
Click to expand...
Click to collapse
your Bootloader might be locked. Did you check ?
xenix96 said:
You already asked this in philz cwm device related thread ?? instead of making this thread..
cheers
Sent from my GT-I9506 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Tried that. Would be better there then here but you can't post / reply in the development sections until you have posted more then 10 times. This is my second post so I can not post there.
fumes007 said:
your Bootloader might be locked. Did you check ?
Click to expand...
Click to collapse
W8 = Canadian... They are not aloud to lock Bootloaders here...
Figured it out.... You can't have the 'Reactivation lock' in the security settings turned on. :cyclops:
Related
So I tried alot of ways to root my samsung galaxy s4 I337. After multiple attempts I got it to root. With the program called: kingo android root
I wanted to put cm10 on here but I needed a custom recovery i tried odin to put twrp on and It kept on failing giving me errors over and over.
so I found a program called: casual that did a root and custom recovery.
well after that it said reboot. So It did and then It got to odin downloading saying error cant normal boot.
I cant restore my phone, get into recovery, the only way I can get on my phone is if I press power down and the home button. Then it boots up.i want it to be fixed without going through all this haggle.
is there anyway besides kies cuz that aint working to fix my phone.
I check root checker basic and I am no longer rooted.
like I said odin is not working for my phone for whatever reason.
maybe if I wait for 4.3 on the 13th and do the ota update will that help.
im so lost please help me someone.
Need to know what firmware you're on. Mf3? Most likely
This might work, but it will delete everything on your phone and reset it. I hope this works :fingers-crossed:
Follow these steps (On your own risk):
1) get on your phone
2) Make sure you have unknown sources enabled (Settings--More--Security--Unknown Sources)
3) install Safestrap 3.62 (download given below)
4) Open app and click "Install Recovery"
5) then press "Reboot to Recovery"
6) It should boot into Safestrap, if not then turn off your phone and the boot it up as you would to use it and then click the menu button on the phone.
7) Then click Wipe
8) Swipe to Factory Reset
9) Reboot
10) Enjoy!
mrwilson1991 said:
So I tried alot of ways to root my samsung galaxy s4 I337. After multiple attempts I got it to root. With the program called: kingo android root
I wanted to put cm10 on here but I needed a custom recovery i tried odin to put twrp on and It kept on failing giving me errors over and over.
so I found a program called: casual that did a root and custom recovery.
well after that it said reboot. So It did and then It got to odin downloading saying error cant normal boot.
I cant restore my phone, get into recovery, the only way I can get on my phone is if I press power down and the home button. Then it boots up.i want it to be fixed without going through all this haggle.
is there anyway besides kies cuz that aint working to fix my phone.
I check root checker basic and I am no longer rooted.
like I said odin is not working for my phone for whatever reason.
maybe if I wait for 4.3 on the 13th and do the ota update will that help.
im so lost please help me someone.
Click to expand...
Click to collapse
You are most probably on MF3, therefore you cannot install TWRP or CWM recoveries. You can only use Safestrap as of right now.
jd1639 said:
Need to know what firmware you're on. Mf3? Most likely
Click to expand...
Click to collapse
firmware 4.2.2. originally. but after doing whatever I did and connecting to kies it says: Current Firmware version: PDA:MF3 / PHONE:MF3 / CSC:MF3 (ATT)
I am going to try safestrap and let you guys know if it worked.
installed safestrap... had to re-root with kingo did re-root. and did a factory wipe. ok so if i cant use twrp. how should I go along installing cm10 rom?
mrwilson1991 said:
installed safestrap... had to re-root with kingo did re-root. and did a factory wipe. ok so if i cant use twrp. how should I go along installing cm10 rom?
Click to expand...
Click to collapse
You can't install Cyanogenmod. Read through the Safestrap thread and the Q/A thread to see what works.
Sent from my SGH-I337 running Foxhound 2.0
mrwilson1991 said:
installed safestrap... had to re-root with kingo did re-root. and did a factory wipe. ok so if i cant use twrp. how should I go along installing cm10 rom?
Click to expand...
Click to collapse
You can't. On MF3 you cannot run AOSP/AOKP/CM/MIUI based roms. Only custom TW.
Sent from my SGH-I337 using XDA Premium 4 mobile app
mrwilson1991 said:
installed safestrap... had to re-root with kingo did re-root. and did a factory wipe. ok so if i cant use twrp. how should I go along installing cm10 rom?
Click to expand...
Click to collapse
You can only use the roms listed in this thread
Thanks guys,
This means a lot with the help. Now if I can get the WiFi to work on the hyperdrive rom. I'll be good as gold tell y'all what from. Going from a jailbreak iOS themer to android rooting user. It's very different and a lot of looking into and reading.
Now back into looking to get this WiFi to work. Just wanted to say thanks
Did you flash the ATT compatibility package zip that you should have downloaded along side of the Hyperdrive rom ,after those two zips did you flash the MF3 kernel module zip.
I use the Hyperdrive rom now and don't have any issues
Sent from my ATT S4 MF3 using Tapatalk
jball said:
Did you flash the ATT compatibility package zip that you should have downloaded along side of the Hyperdrive rom ,after those two zips did you flash the MF3 kernel module zip.
I use the Hyperdrive rom now and don't have any issues
Sent from my ATT S4 MF3 using Tapatalk
Click to expand...
Click to collapse
no i only installed the hyperdrive rom. I am not sure what to do for the rest.
mrwilson1991 said:
no i only installed the hyperdrive rom. I am not sure what to do for the rest.
Click to expand...
Click to collapse
When you downloaded the rom it is in the same page. You need the compatibility package and the MF3 kernel module on Safestrap for it to work right.go back to the Hyperdrive thread and search for it
Sent from my ATT S4 MF3 using Tapatalk
Use Odin and the files here
Just went through this myself and I'm back and running
http://forum.xda-developers.com/showthread.php?t=2502003
You can root with kingo fine, I rooted again right after recovering but do not install any recovery like twrp or clockwork
Sucks but it's how it is
Sent from my Nexus 7 using xda app-developers app
tevil said:
Use Odin and the files here
Just went through this myself and I'm back and running
http://forum.xda-developers.com/showthread.php?t=2502003
You can root with kingo fine, I rooted again right after recovering but do not install any recovery like twrp or clockwork
Sucks but it's how it is
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
here is my issue now.
I rooted with kinggo android root. Then for custom recover I have Safestrap. I rooted to see what all i could do but after trying different Roms I have noticed I don't care. Much for it.
I unrooted via the kinggo app. And verified with root checker.
But i want to go back to full stock. I noticed Safestrap is still there running in background. But the custom logo is gone.
I just want to go back to stock and have nothing to do with root.
I used the code to remove safestrap. and used kingo to unroot. but when I get the offical files for odin and try to push them into my phone. yes I am in download mode when I enter download mode i get:
odin mode
product name: SGH - 1337
current binary: Samsung official
system status: official
CSB-CONFIG-LSB: 0X30
write protection enabled
when I enter odin put thi the tar file for 4.2.2 I get a pass then a fail. the message log says: <ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
and then there is this in red on my phone:
start [224, 1440]
SW REV. CHECK FAIL : fused : 2, Binary : 1
I know I changed the topic. but after thinking there is really nothing that bennifets me with being rooted. and personally I would rather be stock.
can you guys please help.
Let me start off with I'm an idiot. Now that that's over with let me explain what I did to end up here and what I've tried to do to fix it, to no avail of course.
I was running Android 4.3 rooted with cf-autoroot. My software was messing up and with the news that kitkat was available I wanted to unroot and upgrade.
Using a guide I found online I flashed a version of 4.2.2 android. the file name was I337MVLUAMDJ_I337MOYAAMDJ_RWC.zip
Of course when it finished I had the no sound, no wifi problem because i reverted back to the wrong android system.
I then using twrp flashed VANIR and got wifi but still no sound/calls.
As per other threads I tried flashing I9505XXUDMH8_I9505OXXDMHA_BTU with ODIN but every time i would get the error:
<ID:0/005> Complete(Write) operation failed.
The only somewhat success I had was i was able to flash RWC-I337MVLUEMK6-20131125124040 using ODIN 1.85 which is a 4.3 version but still no wifi/sound/calls.
Other files i have tried to flash are GSM_Modem_XXUFNA5_and_LTE_Modem_XXUFNA5(under phone), I9505XXUDMH8-PRE-ROOTED-KNOX_FREE-ODEX-FULL and even tried a pit file: CSB_signed_Fusion3_EUR_0325_V2.pit
Everytime i get Complete(Write) operation failed.
I've put CWM on but still no luck. I need suggestions or a fix please and thank you.
1. Be sure ur phone is SGH-i337 or SGH-i337M. Take the battery off and take a look the label pls for avoid problems :highfive:
2. Wipe all and flash the latest FIRMWARE android 4.4.2 for ur phone (if is SGH-i337M) through ODIN.
3. When u finish, tell me how it worked. Hi5
Downloading now. It is SGH-i337M. Is it normal to be getting (<ID:0/005> Complete(Write) operation failed.) errors when flashing with ODIN?
drock21d said:
Downloading now. It is SGH-i337M. Is it normal to be getting (<ID:0/005> Complete(Write) operation failed.) errors when flashing with ODIN?
Click to expand...
Click to collapse
Yes if u are trying to downgrade android 4.3 to android 4.2.2 :highfive:
Wow thank you. I did a flash with ODIN 3.09 and that file you sent and it seems to be working great. going to try to put CWM and VANIR on now. seeing as how my warranty is voided by knox anyways. Thanks Joku!
drock21d said:
Wow thank you. I did a flash with ODIN 3.09 and that file you sent and it seems to be working great. going to try to put CWM and VANIR on now. seeing as how my warranty is voided by knox anyways. Thanks Joku!
Click to expand...
Click to collapse
In the OP u wrote: "I was running Android 4.3 rooted with cf-autoroot". Your voided ur warranty that time :highfive:
Hey guys, Trying to install philz touch so i can root my new S5
I don't have a micro sd card atm, So i need to use odin. I get an error when flashing philz touch: secure check fail: recovery (phone) and odin says fail (auth) any idea why?
S5 is SM-G900I
Offica said:
Hey guys, Trying to install philz touch so i can root my new S5
I don't have a micro sd card atm, So i need to use odin. I get an error when flashing philz touch: secure check fail: recovery (phone) and odin says fail (auth) any idea why?
S5 is SM-G900I
Click to expand...
Click to collapse
Make sure to use tar.md5 and not zip.
ecksor said:
Make sure to use tar.md5 and not zip.
Click to expand...
Click to collapse
Not that silly I've flashed plenty of recoverys/roms/kernel's on my old S3. But never ran into this error before.
Also tried TWRP, Same error. I'm not sure if it's the phone or windows 8.1 x64, But secure check fail points to the phone.. hmm
Settings security.. Reactivation lock untick...?
Sent from my SM-G900F using Tapatalk
Christiancs1969 said:
Settings security.. Reactivation lock untick...?
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
That did the job! Thank you very much
Offica said:
That did the job! Thank you very much
Click to expand...
Click to collapse
Did you just odin phils recovery... Or root first?
Sent from my SM-G900F using Tapatalk
Christiancs1969 said:
Did you just odin phils recovery... Or root first?
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
You shouldn't need to root before installing a custom recovery. I never have done on Samsung devices.
radicalisto said:
You shouldn't need to root before installing a custom recovery. I never have done on Samsung devices.
Click to expand...
Click to collapse
Yeah it doesn't matter what one you do first.
Is this a joke? I thought custom recovery was not possible on the S5.
Maybe my statement is only true for Vz.
What carrier are you on?
Sent from my Nexus 7 using Tapatalk
swieder711 said:
Is this a joke? I thought custom recovery was not possible on the S5.
Maybe my statement is only true for Vz.
What carrier are you on?
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Theres Philz,TWRP,CWM just check what version they work for i.e im on G900I and using philz recovery - http://forum.xda-developers.com/galaxy-s5/orig-development
Christiancs1969 said:
Settings security.. Reactivation lock untick...?
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
You are GOD!!!! lol!! rs
Thanks a lot!:laugh:
secure check fail
tryng to flash official lollipop update on my galaxy s5 but when i hit start from odin it says failed and secure check : fail any solutiuon
:victory::victory::victory:
Sending you old lady kisses!
This has vexed me for three days!
Christiancs1969 said:
Settings security.. Reactivation lock untick...?
Sent from my SM-G900F using Tapatalk
Click to expand...
Click to collapse
Hi there.
I'm still fairly new to this whole android world (flashing, rooting,...), so I already apologize in advance for any odd questions from my side, or should any of them sound a bit silly So I was wondering the following: I had Philz Touch Recovery on my previous phone (I9300), and had no issues with it or whatsoever. I've been flashing the Lollipop updated successfully and keeping my device up to date. Which was also the reason why I decided to go with the same recovery on my newer phone model (SM-G900F), which I acquired a couple of days ago. I've done 2 backups already (the so called "nandroid" backup and the backup of the first rom version I flashed).
However...when I was checking out the folder files on my SD card later on I realized that the date stated on those folders is not correct To give an example...my latest backup folders got named "2014-01-26.09.06.40_cm_klte-userdebug_5.1.1_LMY48W" So I was now wondering: does the date on those folders have anything to do here, also can I come across any issue while trying to restore to those backups later on (in case anything goes wrong in any of the future releases)? Due to the wrong stated date on those folders I mean...
Thanks in advance.
Hi all. I just got a second hand SM-G00F a few days ago. I succesfully rooted it, installed the XtreStoLite INTL 2.2 rom it as per the installation guide in that thread. I was able to get into TWRP as normal.
However, today I saw that there was an update in the rom thread (http://forum.xda-developers.com/showpost.php?p=63522473&postcount=13226) with links to a 2.3 version, updated bootloader and modem files. After flashing the updated bootloader file with ODIN, i can no longer access TWRP (reactivation lock). I only flashed the bootloader/modem file, not the 2.3 rom. All via ODIN.
I then rebooted into download mode, and flashed the BL and modem files that was in the 2.2 thread again and the phone booted normally. But still, I can' t go into recovery anymore. Flashing anything besides bl or modem via odin seems to be impossible... I always get
Code:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> SingleDownload.
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> FAIL! (Auth)
<ID:0/004>
<ID:0/004> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
On the phone screen in download mode, it says reactivation lock: on, know warranty void 0x1. After trying to flash, the line "secure check fail: recovery" is added.
From reading around, I gather the problem could well be with the previous owner having enabled the samsung reactivation lock function. But how can I untick this function since i can't find it in the current rom? And because of the nand write errors, I can't seem to flash to stock rom at the moment. Would that be a problem flashing a PIT file might fix? I've been trying and looking around for sollutions, but I can't seem to find what to do now...
What about if this happens and I'm in a bootloop?
Offica said:
That did the job! Thank you very much
Click to expand...
Click to collapse
So if I'm looping when I boot up, and obviously can't get to the settings in order to enable USB debugging, how can I "untick" it from stock recovery or Odin mode? ADB will not recognize the device, and I can't flash any custom recovery because of the auth fail secuirty check message. I know it's got to be Knox because in download mode it says "Reactivation Lock(KK)n." It's Android system recovery <3e> LRX21T.G900PVPU3OK4. I have Ubuntu-Mate 15.10, and Windows 10 dual boot operating systems, so any help from the command line or terminal commands/shell commands would be loads of help if anyone out there could help me out. I'm totally fine with resetting the device completely, not just factory wipe/reset, but the big one that deletes all the partitions and everything if it'll do the trick. I can reflash the firmware at that point from Odin or Heimdall, if I could just get past the reactivation lock.
-Thanks in advance-
ELutts
ELutts said:
So if I'm looping when I boot up, and obviously can't get to the settings in order to enable USB debugging, how can I "untick" it from stock recovery or Odin mode? ADB will not recognize the device, and I can't flash any custom recovery because of the auth fail secuirty check message. I know it's got to be Knox because in download mode it says "Reactivation Lock(KK)n." It's Android system recovery LRX21T.G900PVPU3OK4. I have Ubuntu-Mate 15.10, and Windows 10 dual boot operating systems, so any help from the command line or terminal commands/shell commands would be loads of help if anyone out there could help me out. I'm totally fine with resetting the device completely, not just factory wipe/reset, but the big one that deletes all the partitions and everything if it'll do the trick. I can reflash the firmware at that point from Odin or Heimdall, if I could just get past the reactivation lock.
-Thanks in advance-
ELutts
Click to expand...
Click to collapse
Can you get download mode. If so flash first stock rom for your device/carrier... Then turn off in settings.. I've seen issue/mistake like this before ...there's a few guides ...search on Google. For more ....
Just tag me if you need more help.
Don't worry..
It's fixable[emoji6]
http://forum.xda-developers.com/showpost.php?p=60279880&postcount=51
Sent from my SM-G900F using Tapatalk
@ELutts also try first download mode ...then down button. Should reboot into system.
Sent from my SM-G900F using Tapatalk
New to odin what slot do i use to flash twrp? I got rooted and stock recovery, i figured i might as well do twrp recovery but all i see is slots with 2 letters and idk which one is for recovery.
Please help!!!!
I have a SM-G900F S5.
Just updated to XXU1BNL9 Lollipop.
Not clean install, I upgraded it. All official releases from Sammobile, done with Odin 3.09.
Upgrade went all ok, fine, up & running.
Tried to install TWRP 2.8.4.0, also with Odin 3.09
10/10 times it fails with write error.
Any ideas???
Would like to root my phone, so this first step would be really necessary!
Thx!
I fixed Odin fail with a pit file...
Download pit fie for your device...
Open Odin... Flash firmware
When Odin fail... Unplug cable... Plug it back... Uncheck that box with pda (and leave it there) ... Load pit file... And hit start even if the error is still there... After U hit start button It should finish and auto reboot
I USED THIS METHOD JUST FOR FIRMWARE FAIL... I DON'T KNOW IT WILL WORK WITH CWM FAIL in Odin
Also... You should try to download again twrp... Or another source... Version... Etc im sure that the error it's because of the cwm file
Sent from my SM-G900F using XDA Free mobile app lolipop android
Thx for the ideas, I will try them.
I tried to unplug-replug cable, download other TWRP, also from different sources.
Seems as if it was some writing authentication issue of some kind - but no idea, why.
Sent from my SM-G900F using XDA Free mobile app
sandor.korn said:
Thx for the ideas, I will try them.
I tried to unplug-replug cable, download other TWRP, also from different sources.
Seems as if it was some writing authentication issue of some kind - but no idea, why.
Sent from my SM-G900F using XDA Free mobile app
Click to expand...
Click to collapse
For me... The solution was pit file... Did u tried what I say? Step by step....but instead of firmware u can put Cwm...
Strange I've never seen such a error... With cwm
Sent from my SM-G900F using XDA Free mobile app
terrorblade23 said:
For me... The solution was pit file... Did u tried what I say? Step by step....but instead of firmware u can put Cwm...
Strange I've never seen such a error... With cwm
Sent from my SM-G900F using XDA Free mobile app
Click to expand...
Click to collapse
I tried everything else expect the pit file.
I did not find a pit file for the XXU1BNL9 version.
Also, I did not find ClockworkMod for Lollipop, only for 4.4.x
So, I triedTWRP 2.8.1.0 and 2.8.4.0 - both ending the same way: The recover flashing starts with Odin, and then it is almost immadiately fails with some write problem. It seems as if the recovery tar.md5 is not compatibl with the ROM version, or as if some mysterious Samsung protection would reject the recovery flash.
Strange thing is, that all forums (e.g. droidviews, ibtimes, xda, etc.) give a description about rooting this ROM, and not even one mentiones any phenomenon like this.
hello all,
First of all, sorry about my english, if something isn't clear just tell me.
Device : sm-n900
OS : 4.4.2
For various days I tried to install a custom rom, and when it showed no success I tried anothers.
After that I tried to install the russian Lolipop stock rom(odin) just to try to get some results, but with no success as well.
While trying I didn't manage to install recoveries other than CWM.
All I can "install" are the 4.4.2 stock rom, CWM(and root), restore backup of the 4.4.2.
I assume that there is a connection between the inability to install the other recoveries, Lolipop stock and the custom roms, but I couldn't find it.
This post(http://forum.xda-developers.com/showthread.php?t=2613169) showed me some possible direction, but still not a full one(philiz doesn't work and cwm does and after other recoveries flashing there is no recovery to go to until I flash CWM again).
Thanks in regard for any help .
What kind of errors are you getting with roms. How do you install the recoverys. Do you flash the correct modem and bootloader?
Sent from my SM-N920C using Tapatalk
Zionator said:
What kind of errors are you getting with roms. How do you install the recoverys. Do you flash the correct modem and bootloader?
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
When trying with CWM there is no errors in the script, after "installing" nothing happen(I should see something called aroma installer if I got it right) and the phone get into boot loop.
For CWM I used Odin(worked)
TWRP(app, odin, by CWM recovery - no success in any method)
Philiz(by CWM - no success)
Basicly, I didn't saw in guides to flash bl and modem seperatly. In some experiments I tried to flash BL(I am pretty sure the correct one - In download mode and in the setting>>about phone, I saw the difference).
OK I use twrp recovery. When selecting the twrp from there home page be sure to select the correct one as they got a few versions and only one of them will work with odin. The bootloader is a must if you want lollipop builds and without that you will end up in bootloops. If you got Cwm then just stick with that.
Try flashing hyperdrive rom and see if it works. Hyperdrive is kitkat. It's a very stable rom and it works perfectly for me.
Sent from my SM-N920C using Tapatalk
Zionator said:
OK I use twrp recovery. When selecting the twrp from there home page be sure to select the correct one as they got a few versions and only one of them will work with odin. The bootloader is a must if you want lollipop builds and without that you will end up in bootloops. If you got Cwm then just stick with that.
Try flashing hyperdrive rom and see if it works. Hyperdrive is kitkat. It's a very stable rom and it works perfectly for me.
Sent from my SM-N920C using Tapatalk
Click to expand...
Click to collapse
Is there Hyperdriveis for sm-n900 too?¿ I found this(http://forum.xda-developers.com/showthread.php?t=2709867) and it's for n900t or for versions of n9005.
And about TWRP, you mean that there is the tar file which I can flash via odin. Does it matter which version, because there was something confusing in the home page("TWRP Install (Requires TWRP 2.8.4 or higher already installed)" - contradiction )
Just flash the latest tar file. No need to have a previous version of twrp on the phone.
Just make sure that the version you flash matches your phone.
audit13 said:
Just flash the latest tar file. No need to have a previous version of twrp on the phone.
Just make sure that the version you flash matches your phone.
Click to expand...
Click to collapse
I tried again with caution - I saw in some guides to tick off the auto reboot, flash TWRP, pull off the battery, return it, go streight to recovery
but the result is - stuck on boot screen while going to recovery mode
I used odin3 v3.10 and flashed TWRP 2.8.7.0
elad546 said:
I tried again with caution - I saw in some guides to tick off the auto reboot, flash TWRP, pull off the battery, return it, go streight to recovery
but the result is - stuck on boot screen while going to recovery mode
I used odin3 v3.10 and flashed TWRP 2.8.7.0
Click to expand...
Click to collapse
That's wierd. Are you sure you downloaded for ha3g?
Sent from my SM-N920C
Rosli59564 said:
That's wierd. Are you sure you downloaded for ha3g?
Sent from my SM-N920C
Click to expand...
Click to collapse
Yes, in addition, I tried more than one version
elad546 said:
Yes, in addition, I tried more than one version
Click to expand...
Click to collapse
You said you can flash cwm. Flash cwm through odin. Then find flashable twrp and flash it thru cwm.
Or you can use terminal emulator to flash twrp. You can find the instructions in twrp page as well.
Sent from my SM-N920C
Rosli59564 said:
You said you can flash cwm. Flash cwm through odin. Then find flashable twrp and flash it thru cwm.
Or you can use terminal emulator to flash twrp. You can find the instructions in twrp page as well.
Sent from my SM-N920C
Click to expand...
Click to collapse
Tried thru CWM but it said installation aborted.
Tried thru adb(in ubuntu) as usual stuck in recovery on the boot image.
In the terminal emulator nothing happen(I assume it is my mistake, because it didn't even gave response to the command)
***********************************
EDIT : In one of the previous replies I wrote that I thought I changed the bootloader, but I mistaked it with the baseband(only maybe the bootloader too, I pretty sure yes), sorry about this confusion
elad546 said:
Tried thru CWM but it said installation aborted.
Tried thru adb(in ubuntu) as usual stuck in recovery on the boot image.
In the terminal emulator nothing happen(I assume it is my mistake, because it didn't even gave response to the command)
***********************************
EDIT : In one of the previous replies I wrote that I thought I changed the bootloader, but I mistaked it with the baseband(only maybe the bootloader too, I pretty sure yes), sorry about this confusion
Click to expand...
Click to collapse
Could you attach odin log?. Have you disable reactivation lock?
Sent from my SM-N920C
Rosli59564 said:
Could you attach odin log?. Have you disable reactivation lock?
Sent from my SM-N920C
Click to expand...
Click to collapse
Reactivation lock is disabled.
Odin log for the TWRP flash?¿ if so, it doesn't show something different from CWM flash
----------------------
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1005)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> NAND Write Start!!
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
----------------------
btw I saw in photos/vidios that when they get into recovery mod, there is a messege like "recovery booting". I don't see one, is that part of the problem?¿
Seems legit.
First post you said you managed to install cwm. Now you can't?.
Sent from my SM-N920C
Rosli59564 said:
Seems legit.
First post you said you managed to install cwm. Now you can't?.
Sent from my SM-N920C
Click to expand...
Click to collapse
I still can, but I assume that there is connection between the inability to install the other recoveries and the custom rom, so trying change recovry can make progress too.
The question is what the difference between the CWM to other recoveries, that make it the only one to be able to be installed
elad546 said:
I still can, but I assume that there is connection between the inability to install the other recoveries and the custom rom, so trying change recovry can make progress too.
The question is what the difference between the CWM to other recoveries, that make it the only one to be able to be installed
Click to expand...
Click to collapse
Check your inbox. I've sent you a message.
Sent from my SM-N920C
I manged to install TWRP
I went to an older version(2.6.3.7) and it worked
I will now try to work with it and update if there is a change in the result
**************************************
UPDATE : no success from TWRP eather