Heya,
I have some trouble with rooting my Android phone. I thought that maybe you guys might be able to help me out. To explain what happened:
I had my phone with custom firmware and stuff, worked very well. Last saturday I got the idea to check if my recovery had updates. It did and by accident it started downloading and installing the same thing twice, yet it failed the second time. After that I was asked to reboot which I did. I basically screwed my phone up. After some struggling with firmwares I got my phone back on the stock Samsung firmware through Odin. I am now trying to root my device but without success... Can anybody help?
What methods I tried to get my phone rooted/update my phone:
Odin(Worked fine while updating my phone)
Heimdall Suite 1.4(says it has failed to download the PIT file)
Kies(Got an error when trying to update)
Kingo Root gave error 0x1F8232 (I tried both the PC and smarthphone versions.)
I can retry certain methods to get more inside info if you want. ^_^ If you guys have any input, it would be appreciated!
Did you try flashing twrp via Odin and then flashing supersu via twrp?
try CF_Auto root method
Minaaahhh said:
Heya,
I have some trouble with rooting my Android phone. I thought that maybe you guys might be able to help me out. To explain what happened:
I had my phone with custom firmware and stuff, worked very well. Last saturday I got the idea to check if my recovery had updates. It did and by accident it started downloading and installing the same thing twice, yet it failed the second time. After that I was asked to reboot which I did. I basically screwed my phone up. After some struggling with firmwares I got my phone back on the stock Samsung firmware through Odin. I am now trying to root my device but without success... Can anybody help?
What methods I tried to get my phone rooted/update my phone:
Odin(Worked fine while updating my phone)
Heimdall Suite 1.4(says it has failed to download the PIT file)
Kies(Got an error when trying to update)
Kingo Root gave error 0x1F8232 (I tried both the PC and smarthphone versions.)
I can retry certain methods to get more inside info if you want. ^_^ If you guys have any input, it would be appreciated!
Click to expand...
Click to collapse
try CF-Auto root method. download tar file and copy to pc. get into download mode. connect via Odin. flash the tar file. boom!
Related
Hi guys
Sorry this is my first post and it will be a bit long but I've searched everywhere, absolutely everywhere with no luck at all.
So tonight I originally tried to update my MODEM to a Telstra one, and I flashed it via ODIN.
The ODIN flash failed and I stupidly pulled the phone out, and it gave me the dreaded
PHONE-----YELLOW TRIANGLE----- COMPUTER
'Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
I tried flashing a 4.3 KNOX stock rom later on (I realised it was a big mistake), that failed in ODIN as well
I have also tried re-partitioning with a PIT file as well via ODIN but it doesn't really help
ODIN keeps hanging on the "system" flashing command and goes to a red "fail". It won't start flashing "system.ext4.... etc"
I've tried all versions of ODIN and all version of 4.3
I can't use any 4.2.2 roms as the phone only seems to accept 4.3 stock roms now.
I've also tried KIES, but KIES will not recognise my phone, and ODIN hangs at 'system.ext4...' (can't remember, something similar, definitely said system)
So I have a completely bricked phone now... I can only get into TEAMWIN recovery but it won't connect to USB at all.
I absolutely can't flash anything with it failing in ODIN and KIES won't recognise my phone. I've put it in 'download mode' as well..
I've also tried flashing roms through TEAMWIN/CWM recovery but it instantly fails.
Are there any options open to me? I'm really scared that I have an expensive paperweight....
orchid18 said:
Hi guys
Sorry this is my first post and it will be a bit long but I've searched everywhere, absolutely everywhere with no luck at all.
So tonight I originally tried to update my MODEM to a Telstra one, and I flashed it via ODIN.
The ODIN flash failed and I stupidly pulled the phone out, and it gave me the dreaded
PHONE-----YELLOW TRIANGLE----- COMPUTER
'Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
I tried flashing a 4.3 KNOX stock rom later on (I realised it was a big mistake), that failed in ODIN as well
I have also tried re-partitioning with a PIT file as well via ODIN but it doesn't really help
ODIN keeps hanging on the "system" flashing command and goes to a red "fail". It won't start flashing "system.ext4.... etc"
I've tried all versions of ODIN and all version of 4.3
I can't use any 4.2.2 roms as the phone only seems to accept 4.3 stock roms now.
I've also tried KIES, but KIES will not recognise my phone, and ODIN hangs at 'system.ext4...' (can't remember, something similar, definitely said system)
So I have a completely bricked phone now... I can only get into TEAMWIN recovery but it won't connect to USB at all.
I absolutely can't flash anything with it failing in ODIN and KIES won't recognise my phone. I've put it in 'download mode' as well..
I've also tried flashing roms through TEAMWIN/CWM recovery but it instantly fails.
Are there any options open to me? I'm really scared that I have an expensive paperweight....
Click to expand...
Click to collapse
Try another usb port (recommended: back of the computer)
and flash again via Odin stock base rom 4.3
P.S: I was getting the similar problem you have. another usb port helped me
Bordo_Bereli51 said:
Try another usb port (recommended: back of the computer)
and flash again via Odin stock base rom 4.3
Click to expand...
Click to collapse
Thanks Yeah I've tried that, I've tried front, back, on a laptop, but Odin still red fails at the writing 'System' (the largest 'chunk' of the tar.md5 file) no matter which 4.3 rom I try
I so upset :crying:
orchid18 said:
Hi guys
Sorry this is my first post and it will be a bit long but I've searched everywhere, absolutely everywhere with no luck at all.
So tonight I originally tried to update my MODEM to a Telstra one, and I flashed it via ODIN.
The ODIN flash failed and I stupidly pulled the phone out, and it gave me the dreaded
PHONE-----YELLOW TRIANGLE----- COMPUTER
'Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again"
I tried flashing a 4.3 KNOX stock rom later on (I realised it was a big mistake), that failed in ODIN as well
I have also tried re-partitioning with a PIT file as well via ODIN but it doesn't really help
ODIN keeps hanging on the "system" flashing command and goes to a red "fail". It won't start flashing "system.ext4.... etc"
I've tried all versions of ODIN and all version of 4.3
I can't use any 4.2.2 roms as the phone only seems to accept 4.3 stock roms now.
I've also tried KIES, but KIES will not recognise my phone, and ODIN hangs at 'system.ext4...' (can't remember, something similar, definitely said system)
So I have a completely bricked phone now... I can only get into TEAMWIN recovery but it won't connect to USB at all.
I absolutely can't flash anything with it failing in ODIN and KIES won't recognise my phone. I've put it in 'download mode' as well..
I've also tried flashing roms through TEAMWIN/CWM recovery but it instantly fails.
Are there any options open to me? I'm really scared that I have an expensive paperweight....
Click to expand...
Click to collapse
Hello,
For my part, I also encountered problems! the only rom that is passed via ODIN after testing 5 other is:
I9505XXUAMDF_I9505PHNAMD8_PHN
But if Knox! possible that this does not happen either?
*************
For me I do:
1 - Flash with Odin Pit
2 - Flash with ODIN last recovery philz_touch_5.15.8-i9505.zip
3 - Wip full recovery for new rom
4 - Flash the I9505XXUAMDF_I9505PHNAMD8_PHN
And then this happened.
Alan-B said:
Hello,
For my part, I also encountered problems! the only rom that is passed via ODIN after testing 5 other is:
I9505XXUAMDF_I9505PHNAMD8_PHN
But if Knox! possible that this does not happen either?
Click to expand...
Click to collapse
I thought with the official 4.3 new bootloader, we cant downgrade to 4.2.2.
Try another Odin version or extract the .tar file via Winrar (rename it from .tar.md5 to .tar if your file ending at .tar.md5) and flash the system.img.ext4 via this tool http://forum.xda-developers.com/showthread.php?t=2333807 see if you getting error with this tool while flashing the system.img.ext4
and then try to flash again with odin
P.S. While flashing via Odin kill in Task Manager Kies and related process and flash again
Bordo_Bereli51 said:
I thought with the official 4.3 new bootloader, we cant downgrade to 4.2.2.
Try another Odin version or extract the .tar file via Winrar and flash the system.img.ext4 via this tool http://forum.xda-developers.com/showthread.php?t=2333807 see if you getting error with this tool while flashing the system.img.ext4
and then try to flash again with odin
P.S. While flashing via Odin kill in Task Manager Kies and related process and flash again
Click to expand...
Click to collapse
Hey Bordo
Thankyou so much for your suggestion - I will try the individual component flasher later tonight and then write back on what happens
I will also remember to kill Kies with task manager beforehand, before using ODIN or any other flasher :good:
Thankyou so much for your time and effort in trying to help!!!! Much appreciated
Once again i am here looking for help. I was flashing the stock firmware to my Note 3 via odin and something must have gone wrong. It said failed after writing some of the file to the device. Now i am in a soft brick with no recovery. I am only able to get into download mode. I have tried reflashing the firmware via odin but it fails after getting a failure to write error. Is is possible that the phone won't accept the file because maybe the usb debugging option was reset? Phone says this is read letters after the failed download. SWREV checkfail sb(1)fused 2> binary 1. If anyone has any ideas or a link that would help, i would greatly appreciate it.
Mostly fixed.
mcmilldew said:
Once again i am here looking for help. I was flashing the stock firmware to my Note 3 via odin and something must have gone wrong. It said failed after writing some of the file to the device. Now i am in a soft brick with no recovery. I am only able to get into download mode. I have tried reflashing the firmware via odin but it fails after getting a failure to write error. Is is possible that the phone won't accept the file because maybe the usb debugging option was reset? Phone says this is read letters after the failed download. SWREV checkfail sb(1)fused 2> binary 1. If anyone has any ideas or a link that would help, i would greatly appreciate it.
Click to expand...
Click to collapse
So was able to flash twrp via Odin and then reboot into recovery and flash my backup of CM11. But odin never wants to flash stock firmware for me. I like CM but i use the s pen to much so i wanted to go back to rooted stock. Any ideas on why odin isn't working for stock firmware? its still fails after a few seconds. Anyways atleast i have a usable phone for now.
mcmilldew said:
So was able to flash twrp via Odin and then reboot into recovery and flash my backup of CM11. But odin never wants to flash stock firmware for me. I like CM but i use the s pen to much so i wanted to go back to rooted stock. Any ideas on why odin isn't working for stock firmware? its still fails after a few seconds. Anyways atleast i have a usable phone for now.
Click to expand...
Click to collapse
1. You should give us the problem/failure message from Odin so we can read why.
2. You're on the wrong forum if you want N900T specific help.
3. You can always flash a new TW ROM from TWRP
mcmilldew said:
Once again i am here looking for help. I was flashing the stock firmware to my Note 3 via odin and something must have gone wrong. It said failed after writing some of the file to the device. Now i am in a soft brick with no recovery. I am only able to get into download mode. I have tried reflashing the firmware via odin but it fails after getting a failure to write error. Is is possible that the phone won't accept the file because maybe the usb debugging option was reset? Phone says this is read letters after the failed download. SWREV checkfail sb(1)fused 2> binary 1. If anyone has any ideas or a link that would help, i would greatly appreciate it.
Click to expand...
Click to collapse
"SWREV checkfail sb(1)fused 2> binary 1" usually means you are trying to downgrade something in a way that Samsung/T-Mobile does not want you to.
Most likely you need to download the latest firmware (and not the old one):
http://www.sammobile.com/firmwares/1/?model=SM-N900T&pcode=TMB#firmware
Can anyone help?
I was rooted, but on original stock ROM. I tried to unroot using the option in the Super SU app, as a couple of essential apps I use wouldn't work with root. Having clicked the option, my note 4 has gone into a bootloop and I don't know how to recover it.
If I go into recovery I get a message saying "dm-verity verification failed". Any ideas?
I have the international (unlocked) SM-N910F, and I use a mac, so don't have odin. I have Kies installed and Hiemdall, but am really unsure as to what I'm doing with that software....
Thanks in advance!
Further to the last post, I've tried to use Odin 3.09 to flash the stock firmware for my model. I'm using it in Parallels, and it recognises the phone, but won't assign the .md5 file to the AP box to flash it. Not sure why?
I've also tried Heimdall on Mac, but it can't download the PIT file from the phone!
Has anyone got any solutions or workarounds they can suggest?
Thanks in advance....
Try installing stock on a pc then go to recovery and clear cache
I rooted my phone about six months ago so I could have super user permissions. Today, I decided I wanted to try to install cyanogenmod.
After following the instructions to install CM and repeatedly failing (with no apparent harm to the phone), I thought the issue might be that I hadn't unlocked the bootloader. I tried to install TWRP using Odin, but apparently I had installed safestrap back when I rooted. I opened safestrap, attempted to install the packages listed on this post [http://forum.xda-developers.com/ver.../rd-unlocking-galaxys-s5-bootloader-t3337909], and my phone is now apparently/maybe softbricked. I tried to follow the un-bricking instructions on that same page, but I'm getting "fail" messages from Odin.
I do not know what I'm doing. I downloaded what I thought was the stock TAR for my US Verizon Galaxy S5, but it's giving me fail messages when I try to install it with Odin in the AP slot. Am I missing something? Do I need a Pit file or something else in the BL or CP slots? What am I missing?
I would really appreciate any help. I'm out of my league with this.
To add information, I'm getting an error message on my phone saying "[aboot] fused 2 > Binary 1 error" and even after googling that I'm not sure what the fix is.
I just want to get back to non-bricked. Even stock is acceptable.
Go to Sammobile. Com and download ok3 or PB1 firmware for s5 verizon and flash it in odin to your phone
Ok here's what i did wrong. Tried rooting my SM-N910H with CF-Auto-Root, using the wrong d/l ( CF-Auto-Root-tre3g-tre3gxx-smn910h )
My phone was 6.0.1 and i foolishly flashed this file onto it using Odin ( correct me if i'm wrong but it is an earlier version yes? )
So the upshot is my phone will no longer boot up or boot into recovery as i have the "recovery is not seandroid enforcing" error.
Have looked all over the net to find the solution, but no joy. Have tried d/ling latest stock firmware for my phone and flashing with Odin, but it fails everytime.
I think my biggest prob is trying to find THE RIGHT firmware to fix this. Am i on the right track to try and fix this? Any help would be much appreciated.
Blu3sman said:
Ok here's what i did wrong. Tried rooting my SM-N910H with CF-Auto-Root, using the wrong d/l ( CF-Auto-Root-tre3g-tre3gxx-smn910h )
My phone was 6.0.1 and i foolishly flashed this file onto it using Odin ( correct me if i'm wrong but it is an earlier version yes? )
So the upshot is my phone will no longer boot up or boot into recovery as i have the "recovery is not seandroid enforcing" error.
Have looked all over the net to find the solution, but no joy. Have tried d/ling latest stock firmware for my phone and flashing with Odin, but it fails everytime.
I think my biggest prob is trying to find THE RIGHT firmware to fix this. Am i on the right track to try and fix this? Any help would be much appreciated.
Click to expand...
Click to collapse
Instead of flashing any firmware , try to flash the correct cf auto root file.
Reporting Via N910G
Blu3sman said:
Ok here's what i did wrong. Tried rooting my SM-N910H with CF-Auto-Root, using the wrong d/l ( CF-Auto-Root-tre3g-tre3gxx-smn910h )
My phone was 6.0.1 and i foolishly flashed this file onto it using Odin ( correct me if i'm wrong but it is an earlier version yes? )
So the upshot is my phone will no longer boot up or boot into recovery as i have the "recovery is not seandroid enforcing" error.
Have looked all over the net to find the solution, but no joy. Have tried d/ling latest stock firmware for my phone and flashing with Odin, but it fails everytime.
I think my biggest prob is trying to find THE RIGHT firmware to fix this. Am i on the right track to try and fix this? Any help would be much appreciated.
Click to expand...
Click to collapse
Download firmware from sammobiles. com
http://www.sammobile.com/firmwares/database/SM-N910H/
yashthemw said:
Instead of flashing any firmware , try to flash the correct cf auto root file.
Reporting Via N910G
Click to expand...
Click to collapse
Ok well i tried that and that didn't work. However after double checking its seems that i had the correct file in the first place. So what went wrong?
One thing i need to ask. Does your phone NEED to be unlocked in order to root it?
Trex i went to Sammobiles and what my problem is there is WHICH country firmware to i d/l??? there are so many!!! Should any one of them do the trick?
Blu3sman said:
Ok well i tried that and that didn't work. However after double checking its seems that i had the correct file in the first place. So what went wrong?
One thing i need to ask. Does your phone NEED to be unlocked in order to root it?
Trex i went to Sammobiles and what my problem is there is WHICH country firmware to i d/l??? there are so many!!! Should any one of them do the trick?
Click to expand...
Click to collapse
try flashing a custom recovery specific for your phone model and from within flash superSU.
its_me_Sandy said:
try flashing a custom recovery specific for your phone model and from within flash superSU.
Click to expand...
Click to collapse
Ok Sandy thats worked, however i'm stuck on how to install SuperSU. Obviously i want the right ver but my phone will still not bootup,
so how do i get the right ver SuperSU onto my phone? Do i use ADB?
Blu3sman said:
Ok Sandy thats worked, however i'm stuck on how to install SuperSU. Obviously i want the right ver but my phone will still not bootup,
so how do i get the right ver SuperSU onto my phone? Do i use ADB?
Click to expand...
Click to collapse
This is the current supersu 2.78-sr1. It's systemless root for all samsung marshmallow firmware.
http://download.chainfire.eu/1003/SuperSU/SR1-SuperSU-v2.78-SR1-20160915123031.zip
1 Download to phone.
2 Boot into recovery.
3 Click install, and find zip that you downloaded.
4. Reboot, All done
Phone will boot loop once. That is normal.
P.S. If this is first time you installed Twrp, I would make a full backup and save it some where.
:good: if that helped.
aaron74 said:
This is the current supersu 2.78-sr1. It's systemless root for all samsung marshmallow firmware.
http://download.chainfire.eu/1003/SuperSU/SR1-SuperSU-v2.78-SR1-20160915123031.zip
1 Download to phone.
2 Boot into recovery.
3 Click install, and find zip that you downloaded.
4. Reboot, All done
Phone will boot loop once. That is normal.
P.S. If this is first time you installed Twrp, I would make a full backup and save it some where.
:good: if that helped.
Click to expand...
Click to collapse
Well Aaron thats my problem, i can't download it to my phone. The one constant through all this is that i can't turn my phone on as such.
My pc doesn't even recognize it, in fact the only thing that does is Odin, not Kies, not ADB, nothing lol.
I can get the phone into the custom recovery i have flashed (TWRP) and get into "download" mode, but thats it. So where do we go from here?
Ok i have an update on this. PC now sees the phone but only as a modem.
Blu3sman said:
Well Aaron thats my problem, i can't download it to my phone. The one constant through all this is that i can't turn my phone on as such.
My pc doesn't even recognize it, in fact the only thing that does is Odin, not Kies, not ADB, nothing lol.
I can get the phone into the custom recovery i have flashed (TWRP) and get into "download" mode, but thats it. So where do we go from here?
Ok i have an update on this. PC now sees the phone but only as a modem.
Click to expand...
Click to collapse
Oh, I misunderstood.
If that's the case. If you can goto download mode, download stock firmware, then flash with Odin.
To get your csc, since you can go in twrp. Use twrp file explorer. copy the file in /efs/imei folder. Thinks it's called mps_code. Copy to ext sd. Now that file should have your csc region code written in it. Read file in pc. That should be firmware you want to download.
See if that helps.
Blu3sman said:
Ok Sandy thats worked, however i'm stuck on how to install SuperSU. Obviously i want the right ver but my phone will still not bootup,
so how do i get the right ver SuperSU onto my phone? Do i use ADB?
Click to expand...
Click to collapse
Find the correct version of superSU from the above post..put it in a pen drive or in the memory card via card reader.
Flash it via OTG cable or put back the card n flash
ALRIGHT!!!! Ok guys just a heads up. As you can probably guess my phone is WORKING!!!....so far. Was able to do as you suggested and found the txt file, Using TWRP file browser ,that told me what ver firmware i have, inserted an sd card i had in my Tab S, copied file to that, read in my pc card reader, downloaded and installed said firmware and BADA BING BADA BOOM, all good!! I still am unsure on how this happened. I've rooted 3 HTC phones and my Galalxy Tab S successfully, so it's not like i didn't know what i was doing, 1 question that hasn't been answered though is, must the phone be network unlocked in order to root it? Because thats the one thing i didn't do that i did on the others. Want to thank all you guys for all your help. This was doing my head in and without your direction i probably would not have been able to do this.
Many Thanks.
PS: any one suggest a good rooting method for this phone??? lol
hi. i have the exact problem. can you please help,, i dont have twrp or supersu. [email protected] please if anyone can help