I just got a Note 4 (Korean variant). I plan to root it with CF auto-root and flash a ROM. I am on MM update and my build number is same as the one as in the CF auto-root so I have worries about that. However, I wanted to check my bootloader first and the dialer trick won't work so I installed adb on my laptop. When I enter the command "adb devices" my device would read and thus I proceeded with the command "adb reboot-bootloader". My phone then would ONLY Restart and when typing the command "adb fastboot-devices" nothing would appear. What am I doing wrong? Can someone please help me because it would like to know if my bootloader is locked before proceeding with rooting since my main reason of rooting is to flash a custom ROM. :crying:
AJtheAndroidNoOb said:
I just got a Note 4 (Korean variant). I plan to root it with CF auto-root and flash a ROM. I am on MM update and my build number is same as the one as in the CF auto-root so I have worries about that. However, I wanted to check my bootloader first and the dialer trick won't work so I installed adb on my laptop. When I enter the command "adb devices" my device would read and thus I proceeded with the command "adb reboot-bootloader". My phone then would ONLY Restart and when typing the command "adb fastboot-devices" nothing would appear. What am I doing wrong? Can someone please help me because it would like to know if my bootloader is locked before proceeding with rooting since my main reason of rooting is to flash a custom ROM. :crying:
Click to expand...
Click to collapse
Bootloader is not locked.
Just get twrp recovery and flash via odin.
Boot into twrp.
Then flash supersu.zip from twrp.
Thats it you will be rooted and ready to flash any rom.
Twrp N910K/S/L
https://www.androidfilehost.com/?fid=24052804347844773
Supersu.zip
https://mega.nz/#!TE1VFIQD!XoaYaXoLfMDjxvO-uYvDnxejNC-QQlYex0P_UWlDCZ0
Trex888 said:
Bootloader is not locked.
Just get twrp recovery and flash via odin.
Boot into twrp.
Then flash supersu.zip from twrp.
Thats it you will be rooted and ready to flash any rom.
Twrp N910K/S/L
https://www.androidfilehost.com/?fid=24052804347844773
Supersu.zip
https://mega.nz/#!TE1VFIQD!XoaYaXoLfMDjxvO-uYvDnxejNC-QQlYex0P_UWlDCZ0
Click to expand...
Click to collapse
So I don't have to worry about the bootloader? What should be ticked in Odin (and what version of Odin preferably)?
P. S (Out of Topic) isn't there anything to be worried about the emmc error on my Note 4 SM-N910K?
AJtheAndroidNoOb said:
So I don't have to worry about the bootloader? What be ticked in Odin (and what version of Odin preferably)?
P. S (Out of Topic) isn't there anything to be worried about the emmc error on my Note 4 SM-N910K?
Click to expand...
Click to collapse
Dont worry just follow the steps given below correctly.
1 download odin version 3.10 is stable in my opinion.
2,download Twrp & supersu.zip.( do not extract any file ) move supersu file to phone and Twrp to pc
3,open odin and go to options and uncheck autoreboot.
4,choose AP tab in odin and upload Twrp file.
5, put your device into download mode.
6 connect device in your pc and hit start.
7,once odin shows pass remove battery then insert again.
8,now boot into twrp by pressing 3 buttons (volume up+home+power)
9,in twrp go to install and search for supersu file where it's located.
10, swipe confirm to flash supersu.zip and reboot system.
Your device may reboot twice so dont worry its normal dont touch anything until it reboot to system.
Go to app drawer you will see supersu icon open it and thats it you are rooted 100% with Twrp recovery to flash custom roms.
Trex888 said:
Dont worry just follow the steps given below correctly.
1 download odin version 3.10 is stable in my opinion.
2,download Twrp & supersu.zip.( do not extract any file ) move supersu file to phone and Twrp to pc
3,open odin and go to options and uncheck autoreboot.
4,choose AP tab in odin and upload Twrp file.
5, put your device into download mode.
6 connect device in your pc and hit start.
7,once odin shows pass remove battery then insert again.
8,now boot into twrp by pressing 3 buttons (volume up+home+power)
9,in twrp go to install and search for supersu file where it's located.
10, swipe confirm to flash supersu.zip and reboot system.
Your device may reboot twice so dont worry its normal dont touch anything until it reboot to system.
Go to app drawer you will see supersu icon open it and thats it you are rooted 100% with Twrp recovery to flash custom roms.
Click to expand...
Click to collapse
BTW, I am on Marshmallow 6.0.1. Is there no problems? So sorry for my repetitive questions. :crying:
AJtheAndroidNoOb said:
BTW, I am on Marshmallow 6.0.1. Is there no problems? So sorry for my repetitive questions. :crying:
Click to expand...
Click to collapse
No problem This method works on any os 4.4.4/5.0/5.1.1/6.0.1.
Make sure to follow all steps correctly and most importantly make a backup of your whole device from twrp to microsd card before start flashing any roms or stuff just in case if anything goes wrong you will be able to restore it.
Trex888 said:
No problem This method works on any os 4.4.4/5.0/5.1.1/6.0.1.
Make sure follow all steps correctly.
Click to expand...
Click to collapse
Once I pressed start it is stucked at
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
What to do?
AJtheAndroidNoOb said:
Once I pressed start it is stucked at
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
What to do?
Click to expand...
Click to collapse
Did you got samsung usb drivers installed on your pc ?
Close odin and open again
Upload twrp file into odin
Remove battery and insert again
Boot into download mode
Hit start
If it hapoens again just restart your pc and try again
Trex888 said:
Did you got samsung usb drivers installed on your pc ?
Close odin and open again
Upload twrp file into odin
Remove battery and insert again
Boot into download mode
Hit start
If it hapoens again just restart your pc and try again
Click to expand...
Click to collapse
Wooooot! I just changed USB ports and tried again. Now I have SuperSU and custom TWRP recovery! Thank you very much, to be honest I was scared to try and doubted at first but now I know it does work. Thank you! I can now flash custom ROMs without any problems right?
AJtheAndroidNoOb said:
Wooooot! I just changed USB ports and tried again. Now I have SuperSU and custom TWRP recovery! Thank you very much, to be honest I was scared to try and doubted at first but now I know it does work. Thank you! I can now flash custom ROMs without any problems right?
Click to expand...
Click to collapse
Yes you can but make sure roms that you are going to flash are compatible with your model otherwise you will face some issues.
Dont forget to backup your current rom from twrp.
Congrats and enjoy the freedom and power of root
Screenshot of proof!
Trex888 said:
Yes you can but make sure roms that you are going to flash are compatible with your model otherwise you will face some issues.
Dont forget to backup your current rom from twrp.
Congrats and enjoy the freedom and power of root
Click to expand...
Click to collapse
Woooot! Here's a screenshot
https://imgur.com/a/NHnjd
AJtheAndroidNoOb said:
Woooot! Here's a screenshot
https://imgur.com/a/NHnjd
Click to expand...
Click to collapse
Don't forget to thanks @Chainfire for supersu root and Team win recovery project (TWRP) who made this possible.
All the credits goes to them.
Related
Hi folks,
Having searched the forums I couldn't find an answer.
The problem I'm getting is when I get into download mode. I see the normal green android icon but at the top there is a grey caption saying: Write protection: Enabled.
I've been trying to flash twrp custom recovery but odin tries to do it and at the end it tells me success:0 failed:0.
That's all strange enough as previosly I managed to root the s4 using chainfire's Autoroot.
Could anyone tell me why is this happening and how to jump over it and install TWRP recovery.
//edit
I didn't check before I rooted the device but now I can't access stock recovery.
Cheers.
Ps. the device is: rooted i9505 running XXUAMDC stock rom, network: Three UK.
Attached is a screenshot of what I mean.
Thank you.
Didn't the TWRP site suggest using GooManager to install if you're rooted? Maybe give that a shot.
My unbranded UK s4 also said write protection enabled however I've had no problem installing twrp recovery.
Flashed via odin after putting phone into download mode... Have twrp in pda and it's checked in the box next to it...
Sent from my GT-I9505 using xda premium
chalger said:
Hi folks,
Having searched the forums I couldn't find an answer.
The problem I'm getting is when I get into download mode. I see the normal green android icon but at the top there is a grey caption saying: Write protection: Enabled.
I've been trying to flash twrp custom recovery but odin tries to do it and at the end it tells me success:0 failed:0.
That's all strange enough as previosly I managed to root the s4 using chainfire's Autoroot.
Could anyone tell me why is this happening and how to jump over it and install TWRP recovery.
//edit
I didn't check before I rooted the device but now I can't access stock recovery.
Cheers.
Ps. the device is: rooted i9505 running stock rom, network: Three UK.
Click to expand...
Click to collapse
I have the same issue. I'm stock XXUAMDE with CF-ROOT.
I haven't tried to flash TWRP but I can't boot into stock recovery.
It says 'booting recovery' in blue but then just hangs.
Have you tried using Super SU app and unrooting?
Ok.
I tried using GOOmanager, it cannot find suitable recovery for my device (which is strange as you may find it through TWRP web page).
When I choose in GOO to reboot to recovery it actually gets me to stock recovery (I still can NOT get into recovery using power+home+UP)
When i try to flash TWRP using (newly discovered via GOO) stock recovery it looks like that:
There is a broken android icon (see 1st attached file) and the text
-reboot system now
-apply update via ADB
[.....]
# MANUAL MODE #
Applying Multi-CSC
Applied the CSC-Code : H3G (btw H3G is my carrier, three UK)
Successfully applied multi-CSC
when I choose the recovery file to flash I'm getting response that E:\signature verification failed
Again everything I've done with the phone was CFroot, that is it. No custom rom etc or other playing with it.
//edit
I have the same issue. I'm stock XXUAMDE with CF-ROOT.
I haven't tried to flash TWRP but I can't boot into stock recovery.
It says 'booting recovery' in blue but then just hangs.
Click to expand...
Click to collapse
I've got EXACTLY the same behaviour. I discovered GOO manager allowed me to boot into stock recovery.
Thanks for your interest.
chalger
If you're having problems check the thread here: http://forum.xda-developers.com/showthread.php?t=2266336
It's the same method I used to root my phone and flash TWRP. (I too have write protection enabled)
write protection enabled means nothing
I have the exact same thing written on mine.
I have CF-Auto-Rooted mine AND TWRP 2.5 placed on mine, both using ODIN method.
No issues at all - both work perfectly fine.
chalger said:
(I still can NOT get into recovery using power+home+UP)
Click to expand...
Click to collapse
Try using just the Vol Up+Power. Once the phone vibrates, let go of the power but keep holding the up key until you see something appear on the screen. That works on my non-rooted phone to get into recovery.
Hiya
Just for your information.
I've done factory reset, it preserved root access (which I found strange) and now I've managed to flash twrp recovery (which in my view is way too much touch sensitive )
Thanks for all the replies.
problem rooting i9505
chalger said:
Hiya
Just for your information.
I've done factory reset, it preserved root access (which I found strange) and now I've managed to flash twrp recovery (which in my view is way too much touch sensitive )
Thanks for all the replies.
Click to expand...
Click to collapse
Hi All,
Just got my galaxy s4 i9505 with baseband XXUAME2. Have been trying to root this using CFROOT via odin numerous times but each time it fails. The error message includes "write operation failed" and "No PIT partion".
I have downloaded the correct PIT file and tried again but the same problem again.
I have further tried to flash pre-rooted firmware and another stock firmware but again - nothing I do seems to work.
Have tried the factory reset as well but again does not work.
Have tried flashing using motochopper method but also does not work.
Was hoping if someone could kindly extend his/her expertise - I am completely clueless at this point..
Ok for those getting the following error using Odin,
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Removed!!
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
I was getting the same errors whenever I tried to flash anything and couldn't figure out why. Now I seem to have sorted it.
Try this.
DO NOT HAVE ODIN OPEN YET
Stop KIES on your PC if it is on.
1) Put your phone into Download mode, (Home, Vol Down, Power at same time).
2) Connect your USB to PC/Laptop and phone.
3) Press UP on your phone.
4) now, open ODIN. <---only open AFTER your have pressed UP on your phone. COM and "Added" should be showing.
5) Flash what you need to flash.
(I noticed previously when I had Odin open, then pressed UP, it would show as "Added" and a Com would show, but I would ALWAYS get the Pit error and a Red FAIL)
I have now tried this method several times on the trot, flashed CWM with success, (where as it was always failing previously), and re-flashed other ROMS with success each time.
Hope this helps others.
Still failing to flash anything usin odin
artnada said:
Ok for those getting the following error using Odin,
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Removed!!
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
I was getting the same errors whenever I tried to flash anything and couldn't figure out why. Now I seem to have sorted it.
Try this.
DO NOT HAVE ODIN OPEN YET
Stop KIES on your PC if it is on.
1) Put your phone into Download mode, (Home, Vol Down, Power at same time).
2) Connect your USB to PC/Laptop and phone.
3) Press UP on your phone.
4) now, open ODIN. <---only open AFTER your have pressed UP on your phone. COM and "Added" should be showing.
5) Flash what you need to flash.
(I noticed previously when I had Odin open, then pressed UP, it would show as "Added" and a Com would show, but I would ALWAYS get the Pit error and a Red FAIL)
I have now tried this method several times on the trot, flashed CWM with success, (where as it was always failing previously), and re-flashed other ROMS with success each time.
Hope this helps others.
Click to expand...
Click to collapse
Hi i have tried the above. Same problem persists.
I do not have Kies on my pc. Have tried steps listed above as is but still no luck.
need help
Anjamil said:
Hi i have tried the above. Same problem persists.
I do not have Kies on my pc. Have tried steps listed above as is but still no luck.
need help
Click to expand...
Click to collapse
Me too i have the same problem .. any other method to flash back to original fiemware ?
cheers
Indra
problem solved
I used odin 1.85 and original usb cable that came in the
box. Problem solved am now able to flash all roms
I'm having exxcactly the same problem, but i can't boot the phone, it's just stuck on s4 screen, can someone help?
Thanks in advance.
Thanks for this. That solved my issue.
artnada said:
Ok for those getting the following error using Odin,
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Removed!!
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
I was getting the same errors whenever I tried to flash anything and couldn't figure out why. Now I seem to have sorted it.
Try this.
DO NOT HAVE ODIN OPEN YET
Stop KIES on your PC if it is on.
1) Put your phone into Download mode, (Home, Vol Down, Power at same time).
2) Connect your USB to PC/Laptop and phone.
3) Press UP on your phone.
4) now, open ODIN. <---only open AFTER your have pressed UP on your phone. COM and "Added" should be showing.
5) Flash what you need to flash.
(I noticed previously when I had Odin open, then pressed UP, it would show as "Added" and a Com would show, but I would ALWAYS get the Pit error and a Red FAIL)
I have now tried this method several times on the trot, flashed CWM with success, (where as it was always failing previously), and re-flashed other ROMS with success each time.
Hope this helps others.
Click to expand...
Click to collapse
First time i tried to install a custom recovery on my S4 I9505 LTE. With Odin.. It didn't work..
I knew about heimdall.. And i gave that a try. And it worked perfectly. The one thing that's a bit weird.. After it first worked through heimdall. I could flash any custom recovery through Odin. But I think you should give heimdall a try..
Here is a link to how to install CWM on the cyanogenmod wiki: wiki.cyanogenmod.org/w/Install_CM_for_jfltexx#Installing_a_custom_recovery_on_Galaxy_S4_.28International_LTE.29 (I can't post links yet. So i just removed the http)
i flashed modern , and, it is fail, what wrong
[/url][/IMG]
my phone have this entry : "write protection : enable"
on my phone is also 'write protected- enable' but odin and cwm work fine
Q&A for [ODIN][TAR] 5.0.0 I9505GUEUDNL3 Full Restore
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ODIN][TAR] 5.0.0 I9505GUEUDNL3 Full Restore. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
SamuriHL said:
I specifically decided not to use a rooted image this time due to the fact that being rooted blew up the ota for me. I wanted a place to start from that was clean. I figure our first 5.x update was a good place to kick out a new, fresh baseline build.
Click to expand...
Click to collapse
Are you going to release a rooted version? I used this one for now (Thanks!) but would prefer rooted.
All OK
Hello everyone,
I was wondering why there was a Kernel Source added? Also OTA .zip?
Using the attached downloads (very end of the post): "ODIN 3.09" and "I9505GUEUDNL3_FULL" seemed to work fine for me so far... Lollipop is up and running.
In any event, thanks for sharing.
Alex
pathogen47 said:
Are you going to release a rooted version? I used this one for now (Thanks!) but would prefer rooted.
Click to expand...
Click to collapse
No, these images are pretty big so the one I released is it. Rooting is super easy though. Just download CWM non-touch recovery and then from a command line:
fastboot boot recovery-clockwork-6.0.4.7-jfltexx.img
Go to install, then from sideload
From the command line:
adb sideload BETA-SuperSU.v.2.39.zip (or whatever the latest is at the time you do it)
And you're done.
---------- Post added at 05:08 PM ---------- Previous post was at 05:07 PM ----------
ar.richter said:
Hello everyone,
I was wondering why there was a Kernel Source added? Also OTA .zip?
Using the attached downloads (very end of the post): "ODIN 3.09" and "I9505GUEUDNL3_FULL" seemed to work fine for me so far... Lollipop is up and running.
In any event, thanks for sharing.
Alex
Click to expand...
Click to collapse
I add them for completeness of the post. Sometimes people are just looking for the OTA. Sometimes rom devs use my ODIN images and having the kernel source would be beneficial to them. For most users, the ODIN image is fine.
SamuriHL said:
No, these images are pretty big so the one I released is it. Rooting is super easy though. Just download CWM non-touch recovery and then from a command line:
fastboot boot recovery-clockwork-6.0.4.7-jfltexx.img
Go to install, then from sideload
From the command line:
adb sideload BETA-SuperSU.v.2.39.zip (or whatever the latest is at the time you do it)
And you're done.
Click to expand...
Click to collapse
Ok, didn't quite work like that, so for anyone else trying to do this, here's what I had to do.
Files needed:
I used the touch version of CWM and I used the Odin version: http://forum.xda-developers.com/showthread.php?t=2397108
I got the latest stable of SuperSu: http://forum.xda-developers.com/showthread.php?t=1538053 (don't extract the zip).
Copy the SuperSU zip file to your phone. Internal storage or external sdcard, either will work.
1. Open Odin. Uncheck "Auto Reboot".
2. Click AP and select the CWM touch tar file.
3. Power off your phone. Disconnect from USB.
4. Get into download mode for flashing with Odin. Once Odin sees the phone, click Start.
5. When it's done, hold the power button on the phone to power it down. You can disconnect the USB once it's off.
6. Hold the volume up button and press and hold the power button. This will boot into CWM recovery.
7. Use the volume keys to select Install zip and press the power/hold button to select.
8. Select Install from either sdcard (for internal storage) or sdcard1 for the external sdcard.
9. Find the SuperSU zip and select to install it. Follow the prompts.
10. Done. Once it installs SuperSU, just have CWM reboot the phone and you now have root.
It DOES work like that. I wrote a script that does exactly what i wrote. It's how I rerooted myself after I published this unrooted ODIN image. There's no need to flash custom recovery just to install root.
SamuriHL said:
It DOES work like that. I wrote a script that does exactly what i wrote. It's how I rerooted myself after I published this unrooted ODIN image. There's no need to flash custom recovery just to install root.
Click to expand...
Click to collapse
Didn't work for me. When I tried the fastboot part, it just sat on "waiting for device". I tried rebooting the phone while it was at that, tried having it in download mode, tried going into stock recovery... nothing I tried got it to move past that.
pathogen47 said:
Didn't work for me. When I tried the fastboot part, it just sat on "waiting for device". I tried rebooting the phone while it was at that, tried having it in download mode, tried going into stock recovery... nothing I tried got it to move past that.
Click to expand...
Click to collapse
I guess I just assume people know how to get to fastboot mode by now. Power off the phone, hold volume down, press power. You're now in fastboot mode. It doesn't matter, I rewrote my tool for root that walks you through each step. Posting it in a minute.
SamuriHL said:
I guess I just assume people know how to get to fastboot mode by now. Power off the phone, hold volume down, press power. You're now in fastboot mode. It doesn't matter, I rewrote my tool for root that walks you through each step. Posting it in a minute.
Click to expand...
Click to collapse
Ah, well, I'm not a developer and I've never had to use fastboot with this phone before so yeah, I was not aware of it. In the past, I always just flashed pre-rooted versions with Odin. Never had to know anything about fastboot.
Never too late to learn.
lollipop
Would like to know if others are having problems downloading the full update from the link on this page. Tried many times, but mediafire keeps indicating a redirect error. Tried other browsers and cleaning cache, but still no go.
Just tested on my tablet. No issue.
Thanks Samuri - the Odin flushable ROM worked flawlessly for me.
Pre-flashing procedures?
After flashing this with ODIN I was stuck in a bootloop (with the 4 twirling dots). After having 4.3 for a long time, I've decided I finally want to update to 5.0.0. I've only ever used ODIN to root and flash recovery, so I've never used it to perform a system update. I was wondering if the culprit could be anything I've already done? I tried the Wipe Data Factory Reset afterwords but it still bootlooped.
Do i need to uninstall busybox/x-posed/unroot?
I don't have my bootloader unlocked but I don't think i need to. Am I wrong?
Do I have to update to 4.4 then to 4.4.4 then flash this for it to work?
I also tried just to see if using adb sideload with the .zip would work but it didn't.
My guess would be a data issue, but, if you said you wiped data and it's still bootlooping it may be something else. Try flashing the image again.
SamuriHL said:
My guess would be a data issue, but, if you said you wiped data and it's still bootlooping it may be something else. Try flashing the image again.
Click to expand...
Click to collapse
Flashing again did indeed work. Thanks man.
Glad it worked. You're quite welcome.
How to flash this update without my previous problem.
I Managed to flash the "philz_touch_6.58.7-jflte.tar.md5" trough Odin, and my phone is now working again.
I'm not sure, but I guess I didn't have the USB Debugging Mode On. Not sure if it was the only problem, probably not.
Before failure procedure I Used to have on the phone: Model, GT-i9505G, Version 5.0, Baseband I9505VJUFNC1, SuperSU, Busybox and Googy-Max STweaks. Don't know any more what kernel was on it.
Now I have:
Same as above, but Googy-Max STweaks dont work because of the Kernel (3.4.0-2809293 [email protected]#1 Fri Dec 5 20:45:08 KST 2014)
Now, what do I need to do, to have a clean and fresh phone to use and root it. Do I need to mess with Kernel and Recovery stuff to get my phone working again?
Thank you!
I'll try to give as much Info as I can for now.
I got a used i9505G. It had the CWM 6.0.4.9 on it, and used to have a ROM with final "NC1" 5.0.0 Lollipop. It used to have a SU installed and some other app on home screen about Kernel stuff, and Knox was already Flagged on boot.
So, after a lot of reading, I messed my i9505G. Tried to flash this ROM. Got PIT error, changed USB Ports, and OK.
After new Odin session, clicking start, in few seconds I got this error copied below.
Now I'm stuck at boot animation.
At download screen, gets stuck with tiny blue bar if I try to flash this.
At recovery i get: (Android System Recovery <3e> - LRX21P.S012.141205
There is another info on recovery screen that says: E:Can't open /dev/blcok/plataform/msm_sdcc.1/by-name/misc (Permission Denied).
Already tried wiping data and cache. (Im not sure if I did it too before the whole procedure when I had the CWM).
I've never messed with kernel, recovery, etc, only messed with Stock Roms on my i9505.
Click to expand...
Click to collapse
<ID:0/013> Added!!
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> I9505GUEUDNL3_FULL.tar.md5 is valid.
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/013> Odin v.3 engine (ID:13)..
<ID:0/013> File analysis..
<ID:0/013> SetupConnection..
<ID:0/013> Initialzation..
<ID:0/013> Get PIT for mapping..
<ID:0/013> Firmware update start..
<ID:0/013> SingleDownload.
<ID:0/013> boot.img
<ID:0/013> NAND Write Start!!
<ID:0/013> recovery.img
<ID:0/013> NON-HLOS.bin
<ID:0/013> FAIL! (Auth)
<ID:0/013>
<ID:0/013> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks in advance for any help!
Home button problems
I've flashed this after doing a factory reset (a few times now actually.) The same result each time. When it boots up I go through the setup process and everything is fine. If I reboot my phone the home button single click function goes away as does the ability to lock the screen with power. The other functions still work (double click, long press) If I lock the phone the screen turns off but doesn't lock, If I press power or home the screen just turns back on with no lock screen shown.
I do not have that issue. Try factory resetting it after flashing rather than before.
Dear All,
I'm in need of some urgent help. I have a S4 GT-I9500 which was running Kitkat stock 4.4.2 unrooted. I noticed the Lollipop update available OTA and so I downloaded and applied it. The installation went ok but after that the phone has just not worked. It comes to the homescreen, there comes an error stating that "An application needs and update" and below that "Requested by Google Play services". The homescreen appears on the screen for less than 5 seconds and it reboots. This goes on and on making the device really hot. There was a massive battery drain as well (from 90% to 30% within 30 mins)
Now the worst part is I hadn't even backed up any of my data. Although my photos are on my external SD, contacts are synced to google but there are some application specific data (whatsapp, few games progress, etc) that I would like to save.
Please help me out. At this point, I dont even care about the lollipop as long as I can get my phone back. I'm also open to rooting it, as my warranty period is over.
OK, I booted into recovery and wiped the cache partition too. No luck.
boogey_man said:
OK, I booted into recovery and wiped the cache partition too. No luck.
Click to expand...
Click to collapse
1. Wipe system, cache and cache partition (data no atm).
2. Reboot in DOWNLOAD MODE and flash via ODIN again Lollipop firmware. You will have to download it of Sammobile.com.
3. I hope this will work :highfive:
Joku1981 said:
1. Wipe system, cache and cache partition (data no atm).
2. Reboot in DOWNLOAD MODE and flash via ODIN again Lollipop firmware. You will have to download it of Sammobile.com.
3. I hope this will work :highfive:
Click to expand...
Click to collapse
Thanks for the reply.
But won't this erase all of the data (whatsapp, few games progress, etc) I want to save ?
boogey_man said:
Thanks for the reply.
But won't this erase all of the data (whatsapp, few games progress, etc) I want to save ?
Click to expand...
Click to collapse
Read the step 1.:
- You will have "Advanced Wipe" on your custom recovery. Click only for wipe system, cache and dalvick cache. In TWRP is:
Joku1981 said:
Read the step 1.:
- You will have "Advanced Wipe" on your custom recovery. Click only for wipe system, cache and dalvick cache. In TWRP is:
Click to expand...
Click to collapse
I haven't installed TWRP. I was only using inbuilt recovery (using volume-up, menu and power buttons) until now.
Please correct me if the below steps on installing TWRP are right:
- download latest twrp for s4 from here: http://www.teamw.in/project/twrp2/191
- flash TWRP to my phone using ODIN 3.09 (Download the above file and flash using Odin in the PDA tab.)
boogey_man said:
I haven't installed TWRP. I was only using inbuilt recovery (using volume-up, menu and power buttons) until now.
Please correct me if the below steps on installing TWRP are right:
- download latest twrp for s4 from here: http://www.teamw.in/project/twrp2/191
- flash TWRP to my phone using ODIN 3.09 (Download the above file and flash using Odin in the PDA tab.)
Click to expand...
Click to collapse
1. This will void you warranty: KNOX 0x1. You dont need care if you are out of warranty.
2. The steps are you following are corrects.
Thanks. I tried it but TWRP is just not getting installed. I flashed using ODIN 3.07 and PDA, but when in restart the phone into recovery mode, it goes back to the Samsung's stock recovery and doesn't have the TWRP. Any suggestions?
Use a different USB port, and don't use a hub. Also be sure you're using the original cable, have the drivers installed, and do not have Kies installed or running.
If necessary, find a later copy of Odin. 3.09 is apparently the standard although 3.10 exists.
Strephon Alkhalikoi said:
Use a different USB port, and don't use a hub. Also be sure you're using the original cable, have the drivers installed, and do not have Kies installed or running.
If necessary, find a later copy of Odin. 3.09 is apparently the standard although 3.10 exists.
Click to expand...
Click to collapse
Right....
Now I receive the below error in ODIN:
<ID:0/009> Odin v.3 engine (ID:9)..
<ID:0/009> File analysis..
<ID:0/009> SetupConnection..
<ID:0/009> Initialzation..
<ID:0/009> Get PIT for mapping..
<ID:0/009> Firmware update start..
<ID:0/009> SingleDownload.
<ID:0/009> recovery.img
<ID:0/009> NAND Write Start!!
<ID:0/009> FAIL!
<ID:0/009>
<ID:0/009> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
The COM port gets detected. Also, now the boot loop is gone and is replaced by "firmware upgrade encountered an issue" error.
Should I try downloading Kies now?
Kies wouldn't do you much good, as it would find Android 5.0.1 on your S4 and report that there was no update.
You may need to flash with a PIT file in order to correct this as your S4 after the Lollipop update may have had its partition information changed. If that doesn't work, you may have to bite the bullet and do a complete factory reset, which will cost you the data.
Strephon Alkhalikoi said:
Kies wouldn't do you much good, as it would find Android 5.0.1 on your S4 and report that there was no update.
You may need to flash with a PIT file in order to correct this as your S4 after the Lollipop update may have had its partition information changed. If that doesn't work, you may have to bite the bullet and do a complete factory reset, which will cost you the data.
Click to expand...
Click to collapse
Thanks.
Meanwhile, I've tried on another PC too, same issues. "Complete (Write) operation failed." error in ODIN there as well.
PIT file flashing is next on the list, I guess. Any pointers as to how should I start?
And BTW, I don't know how I can wipe complete data, as now there is no way to access the stock recovery. Pressing the "up+menu+power" just opens the "firmware upgrade encountered an issue" error. The boot loop doesn't happen any more. Its just a soft brick now.
Update: I've tried flashing recovery.img (from both CWM and TWRP) using Heimdall. Both were not helpful.
Code:
C:\Heimdall Suite>heimdall.exe flash --RECOVERY recovery.img
Heimdall v1.4.0
Copyright (c) 2010-2013, Benjamin Dobell, Glass Echidna
http://www.glassechidna.com.au/
This software is provided free of charge. Copying and redistribution is
encouraged.
If you appreciate this software and you would like to support future
development please consider donating:
http://www.glassechidna.com.au/donate/
Initialising connection...
Detecting device...
ERROR: Failed to retrieve config descriptor
Right...
So I was now able to flash stock 4.4.2 along with adonis.pit. This was a PASS! in Odin. However, still the device didn't boot. Stuck on the Samsung logo.
I did manage to flash CWM recovery on it and I'm now able to boot into recovery. I'll take the backup now and then try to wipe data and flash.
can you please show me how to root my G900F BOJ2
i tried Towelroot not supportd
flash CF-AUTO ROOT blocks when going to recovery .. also i unselect auto rebot from odin and trie to boot to recovery manually but the same
tried to flash TWRP then root it ... and it doesn't install tho
This is the only method that seems to work......Follow exactly....
1) deactivate 'Reactivation Lock'.
2) copy SuperSU zip to your device.
3) boot into download mode.
4) Odin flash TWRP 2.8.7.0 (specifically this version).
5) DO NOT allow phone to boot, (uncheck auto reboot in odin and if necessary remove the battery as soon as the TWRP flash has completed) then.....
6) boot directly into recovery. (Vol +, Power & Home button combination)
7) flash SuperSU zip.
8) boot device as normal.
TWRP 2.8.7.0 by Dees_Troy
http://forum.xda-developers.com/showthread.php?t=2727406
superSU zip v2.46 by Chainfire
http://forum.xda-developers.com/showthread.php?t=1538053
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
This is the only method that seems to work......Follow exactly....
1) deactivate 'Reactivation Lock'.
2) copy SuperSU zip to your device.
3) boot into download mode.
4) Odin flash TWRP 2.8.7.0 (specifically this version).
5) DO NOT allow phone to boot, (uncheck auto reboot in odin and if necessary remove the battery as soon as the TWRP flash has completed) then.....
6) boot directly into recovery. (Vol +, Power & Home button combination)
7) flash SuperSU zip.
8) boot device as normal.
TWRP 2.8.7.0 by Dees_Troy
http://forum.xda-developers.com/showthread.php?t=2727406
superSU zip v2.46 by Chainfire
http://forum.xda-developers.com/showthread.php?t=1538053
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
what do you mean by deactivate 'Reactivation Lock'.
joker678 said:
what do you mean by deactivate 'Reactivation Lock'.
Click to expand...
Click to collapse
http://bfy.tw/3vXB
Thanks a lot!
1) deactivate 'Reactivation Lock'.
Is there a way you would recommend this to be done? E.g. http://forum.xda-developers.com/galaxy-s5/help/bypass-reactivation-lock-s5-t3159328 ?
So we first have to flash an old firmware version? This adds a lot more steps to your description. Or did you mean another way?
samuelverner said:
Thanks a lot!
1) deactivate 'Reactivation Lock'.
Is there a way you would recommend this to be done? E.g. http://forum.xda-developers.com/galaxy-s5/help/bypass-reactivation-lock-s5-t3159328 ?
So we first have to flash an old firmware version? This adds a lot more steps to your description. Or did you mean another way?
Click to expand...
Click to collapse
If your phone can boot, disable reactivation lock from settings
If it can't - flash a stock KitKat ROM, log into all accounts, disable reactivation lock from settings
Hi Guys,
first of all sorry for maybe silly question, I spent last week by reading on this forum and I have read probably to much.. got puzzle in my head
Simply question.. I would like to root my G900F running stock rom with Android 5.0
for now nothing else, just to be able to get rid of some operator bloatware and clean the device
Would this steps rooting device trigger Knox or not?
With the root and I understood process described here requires custom recovery.. would it be possible to get OTA once (who knows) the Android 6.0 will be released for our S5?
Again sorry, there are so many threads around but many of those are old or people complaining something went wrong (probably not all steps works on every stock release)
Thanks for answer and suggestions
keithross39 said:
This is the only method that seems to work......Follow exactly....
1) deactivate 'Reactivation Lock'.
2) copy SuperSU zip to your device.
3) boot into download mode.
4) Odin flash TWRP 2.8.7.0 (specifically this version).
5) DO NOT allow phone to boot, (uncheck auto reboot in odin and if necessary remove the battery as soon as the TWRP flash has completed) then.....
6) boot directly into recovery. (Vol +, Power & Home button combination)
7) flash SuperSU zip.
8) boot device as normal.
TWRP 2.8.7.0 by Dees_Troy
http://forum.xda-developers.com/showthread.php?t=2727406
superSU zip v2.46 by Chainfire
http://forum.xda-developers.com/showthread.php?t=1538053
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Hi @cedna......yes, this method will trip knox. It will also set your system status to custom which will break OTA.
You can get official status back by re-flashing a firmware via Odin.......but then you could use Odin to flash any future updates anyway, so OTA isn't strictly speaking necessary.....
The only way to avoid tripping knox is to root (with towelroot) while your device is running KitKat......
http://i.imgur.com/rVnFwJM.jpg
keithross39 said:
This is the only method that seems to work......Follow exactly....
1) deactivate 'Reactivation Lock'.
2) copy SuperSU zip to your device.
3) boot into download mode.
4) Odin flash TWRP 2.8.7.0 (specifically this version).
5) DO NOT allow phone to boot, (uncheck auto reboot in odin and if necessary remove the battery as soon as the TWRP flash has completed) then.....
6) boot directly into recovery. (Vol +, Power & Home button combination)
7) flash SuperSU zip.
8) boot device as normal.
TWRP 2.8.7.0 by Dees_Troy
http://forum.xda-developers.com/showthread.php?t=2727406
superSU zip v2.46 by Chainfire
http://forum.xda-developers.com/showthread.php?t=1538053
http://i.imgur.com/rVnFwJM.jpg
Click to expand...
Click to collapse
Hi,
when i try to add TWRP file in Odin (AP tag), it gives me an error...in chinese!!
What can i do?
Thank you
Where did you see the Chinese language error.....Odin or the phone?
http://i.imgur.com/rVnFwJM.jpg
klaus_24 said:
can you please show me how to root my G900F BOJ2
i tried Towelroot not supportd
flash CF-AUTO ROOT blocks when going to recovery .. also i unselect auto rebot from odin and trie to boot to recovery manually but the same
tried to flash TWRP then root it ... and it doesn't install tho
Click to expand...
Click to collapse
<ID:0/003> Added!!
<ID:0/003> Removed!!
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1100)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> RQT_CLOSE !!
<ID:0/006> RES OK !!
<ID:0/006> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
i have my reactivation lock off i used usb3 and usb2 cable usb debugging is on but i can only boot into stock recovery
i'm using Odin3_v3.10.7
twrp-2.8.7.0-klte.img tar file
auto reboot is off
i run android 5.0
using sm-g900f
what do you think causes this?
i got it to work i just had to do it and redo it a couple of times thanks for sharing this
vitorino_j said:
Hi,
when i try to add TWRP file in Odin (AP tag), it gives me an error...in chinese!!
What can i do?
Thank you
Click to expand...
Click to collapse
The error appears in windows. When in odin
Hi, I hope I can get an answer on this. Purchased the Note 4, just went outside of warranty a few weeks ago, and I'm trying to root it.
I set my phone in debug mode, and tried on both ODIN 3.9 and the last RV to no avail and tried to flash CF-Auto-Root-trltecan-trltecan-smn910w8.tar.md5
I don't understand what it is I'm doing wrong. Installed all drivers with Samsung USB Driver, and KIES
Uninstalled KIES as I heard it was not recommended.
It hangs during the download stage at <ID:0/003> recovery.img
Getting real frustrated as documentation doesn't really cover anything for the latest Android version released for this phone.
Any help would be greatly appreciated.
Thank you in advance!
WarDerp said:
Hi, I hope I can get an answer on this. Purchased the Note 4, just went outside of warranty a few weeks ago, and I'm trying to root it.
I set my phone in debug mode, and tried on both ODIN 3.9 and the last RV to no avail and tried to flash CF-Auto-Root-trltecan-trltecan-smn910w8.tar.md5
I don't understand what it is I'm doing wrong. Installed all drivers with Samsung USB Driver, and KIES
Uninstalled KIES as I heard it was not recommended.
It hangs during the download stage at <ID:0/003> recovery.img
Getting real frustrated as documentation doesn't really cover anything for the latest Android version released for this phone.
Any help would be greatly appreciated.
Thank you in advance!
Click to expand...
Click to collapse
DISCLAIMER-_-Try on your own risk.
This is a universal method if you follow all steps correctly you will have permanent root and also custom recovery for flashing roms,zip files,backup roms etc.
1, download TWRP recovery img.tar.
2,download supersu.zip
3,open odin go to options and "uncheck" autoreboot.
4,choose AP tab in odin and upload TWRP recovery.
5,go to device download mode and connect to pc via usb cable.
6,HIT START in odin once odin shows pass remove battery from device.(DO NOT REBOOT YOUR DEVICE)
7,insert battery again and boot into TWRP recovery by pressing (volume up+home+power button)
8,go to install and flash supersu.zip and reboot.
Your device may reboot twice so dont worry its normal
Enjoy root.
TWRP RECOVERY LINK
https://dl.twrp.me/trltecan/twrp-3.0.2-0-trltecan.img.tar.html
SUPERSU.ZIP LATEST
https://s3-us-west-2.amazonaws.com/supersu/download/zip/SuperSU-v2.79-201612051815.zip
Thanks for the help! I tried that though and now it's just hanging at the Downloading screen again. Going to give it another five minutes but I really hope I'm not ruining it.
<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
Click to expand...
Click to collapse
EDIT: Nothing's happened. Trying with latest RV of ODIN
Tried with the latest version of ODIN. Nothing
can the w8 be rooted?
Reviving an old thread? Yes, W8 can be rooted. I did had similar problem with rooting my W8, but I fixed it using similar steps as Trex outlined above.
If you're still having problems, check and make "lock re-activation" is off. "usb debugging" is on.
HappyPlato said:
Reviving an old thread? Yes, W8 can be rooted. I did had similar problem with rooting my W8, but I fixed it using similar steps as Trex outlined above.
If you're still having problems, check and make "lock re-activation" is off. "usb debugging" is on.
Click to expand...
Click to collapse
Know any way to revive via sd card? I hear it's possible.
Sent from my Samsung SM-N900T using XDA Labs