[Q] Trying to root but having problems - T-Mobile, Samsung Galaxy SIII

I am on a samsung galaxy s3 t-999 and i have tried to root it and have no luck i have followed a video and i have made it up to everything and got my phone into a "modified" state but now i am up to a part where you put the phone in recovery mode and try to install CWM-SuperSU-v0.87.zip and try to choose the package to install and it shows up as a "E:signature verification failed" it looked like the person in the video had a completely different menu in recovery mode so i guess that was my first red flag to getting my hopes up but if anyone knows how to get past this and completely get the S3 rooted i would be sincerely thankful
-Danny

Dannypolodown said:
I am on a samsung galaxy s3 t-999 and i have tried to root it and have no luck i have followed a video and i have made it up to everything and got my phone into a "modified" state but now i am up to a part where you put the phone in recovery mode and try to install CWM-SuperSU-v0.87.zip and try to choose the package to install and it shows up as a "E:signature verification failed" it looked like the person in the video had a completely different menu in recovery mode so i guess that was my first red flag to getting my hopes up but if anyone knows how to get past this and completely get the S3 rooted i would be sincerely thankful
-Danny
Click to expand...
Click to collapse
did you install a custom recovery such as cwm or twrp?

Dannypolodown said:
I am on a samsung galaxy s3 t-999 and i have tried to root it and have no luck i have followed a video and i have made it up to everything and got my phone into a "modified" state but now i am up to a part where you put the phone in recovery mode and try to install CWM-SuperSU-v0.87.zip and try to choose the package to install and it shows up as a "E:signature verification failed" it looked like the person in the video had a completely different menu in recovery mode so i guess that was my first red flag to getting my hopes up but if anyone knows how to get past this and completely get the S3 rooted i would be sincerely thankful
-Danny
Click to expand...
Click to collapse
Its easier just to odin a rooted version of the factory image.
You can find it at the link on the bottom. Just flash the latest JB or ICS root66. If you use ICS, it wont trip your counter. Rooting you way will, so be sure to use triangle away from the playstore to reset your flash counter. Heres the link
http://forum.xda-developers.com/showthread.php?t=1949687

Related

[Q] I need some help please

I'll try and give as much info as possible so that hopefully this is easy to figure out.
My phone is a Samsung Galaxy s3 sch-r530u the US Cellular version. I didn't see a US Cellular forum and read someplace that it's the same as the at&t one so that's why I'm posting in here.
About a month or so ago I rooted and installed cyanogenmod with the installer and it installed I believe 11.1 maybe 11.2. The Android version my phone said it was I'm pretty sure was 4.4.2. Today in about phone in the settings I got a new version available message so I tried to do an update, which I was understanding that it was a cyanogenmod update and not a stock update but maybe I was wrong.
Right after the update my phone would boot to the boot screen with the blue robot guy on it and freeze basically. I was able to get into CWM and also into download mode. I did a little looking around and went into CWM and did the factory reset/wipe and cleared the cache and dalvik and that changed nothing.
Then I tried to flash the cyanogenmod 10.2 from inside CWM because I read someplace that it fixed the problem for someone else and it just failed when I tried. I also tried to fix via Kies and it isn't accepting my serial number for some reason. Then I found the teamuscellular website and grabbed both roms that say are stock roms and tried to flash both of those (not at the same time) via Odin and when I did the first one I got the something happened during firmware upgrade error.
I eventually fixed that by flashing the pit file with Odin and now I'm back to being stuck on the blue robot boot screen. When I try to flash either stock rom from teamuscellular in Odin they fail at some point and then I have to reflash the pit file again.
Somewhere along the line I couldn't get into CWM anymore and had to reflash that and I now have the philz touch 6.09.2 version of that.
I currently can get into both CWM and Download mode but for the life of me nothing I try works. When I go into Download mode what reads in the top left corner is this
odin mode, in red letters
Product name: SCH-R530U, in white letters
Custom binary download: Yes (4 counts), in white letters
Current Binary: Custom, in white letters
System Status: Custom, in white letters
Qualcomm Secureboot: Enable, in grey letters
Waranty bit: 1, in red letters
Bootloader Ap Swrev: 1, in grey letters
When I try and flash a rom and it fails I get some other line of text in red but I forget what it says
Any help is greatly appreciated
Thanks in advance
EDIT - Also a number of places directed me to samsungs updates websites to get the stock mod for my phone but there isn't one there for the SCH-R530U.
Also I'm looking at the how to guide for unbricking and I see something there about the status 7 error, which I do believe I got when I tried to flash the 2 teamuscellular stock mods but I don't remember for certain. I know one thing I didn't try was updating my bootloader.
I've also tried fixing with the simple upgrade tool and it fails also.
OK so I went ahead and tried the simple upgrade tool again to see the errors it gave me and in the bottom left corner of the program it had gone through a few things and failed when it said ABOOT.
And also at that same time on the download mode screen it added this line in red text at the bottom of the list in the top left corner on my phone screen
SW REV CHECKFAIL: FUSED1>Binary0
Based on a quick search, your phone supports CDMA and the AT&T version is GSM so they are not identical.
Your phone has the 4.3 bootloader with knox security. Since you flashed a custom recovery, it tripped the knox counter which voids any existing warranty.
The 4.3 bootloader cannot be downgraded to an older version and attempts to do so, either in download or recovery, may brick the phone.
In order to flash the phone in Odin, you would need to have a full and completely stock 4.3 ROM and not just a OTA update of the 4.3 ROM.
I suggest that you upgrade your recovery to the latest version and flash a custom ROM to try and get your phone functioning.
audit13 said:
Based on a quick search, your phone supports CDMA and the AT&T version is GSM so they are not identical.
Your phone has the 4.3 bootloader with knox security. Since you flashed a custom recovery, it tripped the knox counter which voids any existing warranty.
The 4.3 bootloader cannot be downgraded to an older version and attempts to do so, either in download or recovery, may brick the phone.
In order to flash the phone in Odin, you would need to have a full and completely stock 4.3 ROM and not just a OTA update of the 4.3 ROM.
I suggest that you upgrade your recovery to the latest version and flash a custom ROM to try and get your phone functioning.
Click to expand...
Click to collapse
OK. What exactly should I be looking for when you say I should upgrade my recovery? If I remember right I thought I removed that stupid Knox crap or maybe I just disabled it I forget exactly.
Thequass said:
OK. What exactly should I be looking for when you say I should upgrade my recovery? If I remember right I thought I removed that stupid Knox crap or maybe I just disabled it I forget exactly.
Click to expand...
Click to collapse
You can try and fix your phone by updating your recovery to the latest version of CWM for your phone. Then, download an install a custom ROM for your phone.
If you are not sure of what or how to do upgrade your recovery, don't do it until you have done some research and really understand the process.
As with any software change, there is no guarantee you won't brick your phone in the process.
Yeah I understand, I just wanted to make sure you meant CWM. So you think I should try reflashing a 4.3 custom rom over a 4.4? It was running 4.4.2 totally fine for a month ish.
If you want to install another ROM, I recommend doing a full wipe, including the system, cache, Davik, and data, before installing the new ROM.
I have switched between older and newer ROMs without a problem on my i747m.
Ok. I'll definitely wipe everything as I did in the past maybe there's one that I'm missing somehow. I wipe everything and somehow the blue robot boot screen is still there.
Thanks for all of your help. Your suggestions definitely led me in the right direction. I ended up finding a modified stock 4.3 with the bootloader file removed and since it seemed like my issues were related to that I figured what the hell I'll try it, I was almost at the point of going and getting a new phone anyhow. Because it wasn't completely bricked I wanted to try everything I could though and this worked!!!
Thanks again!!

[Q] Unique Situation ATT Galaxy Note 2 Help

Ok, this is my first post so forgive if this is in the wrong section...
I have a friend's Galaxy Note 2 ATT that was stuck on the Galaxy Note 2 Boot screen, and it wouldn't go any further.
Because I work for Samsung at the Samsung Experience Shop, I tried running it through our smart reflash tool
-----> This didn't work because it would fully download it onto the phone, but when it got to the Android with the thing spinning in its chest, it would stop and ALWAYS freeze halfway.
Next step I tried doing was going through Samsung Kies and downloading the stock OS and load that, but the same Android with the spinning thing in its chest would show up and it would freeze.
Due to this guy being my friend I told him I would try anything to get his phone to work again (root, to custom recovery, to custom rom)
My steps so far:
1. I have successfully rooted my device via ODIN 1.85 by using CF-Auto-Root
2. Afterwards, I loaded on a custom recovery via ODIN 1.85 which now is philz_touch_6.07.9
Here is my problem now, I've tried searching everywhere and I can't really find the answer...
Whenever I try to side load a rom through ADB through Android tools (its in the right directory and everything because it transfers over), I keep getting an error message "E: Error in /tmp/update.zip (status 7) Installation Aborted."
Now before I get that error I get stuff like getprop("ro.product.device")==t0lte" ||getprop("ro.build.product").... etc. and it goes on and on.
So far the ROMs that I have tried were Cyanogenmod 10.1 and the Pacman Rom, and yes, both are for the correct device like the model name/number match up. And now how I said I thought I rooted the device, whenever I try to reboot into recovery via Philztouch, it says at the top Root Access is missing. Root device, and I click yes. When it reboots into recovery and I want to turn the phone off again, it still says Root Access is missing.
I am open for anything really. My friend just wants his phone to work again. and I've literally exhausted all of my ideas as I keep running into the same issue.
What am I doing wrong? and is something like this possible to fix? Or is my friend SOL?
Thanks for all the help. It's much appreciated.
Your recovery is outdated. Status 7 error.
I use TWRP from the original development section.
rangercaptain said:
Your recovery is outdated. Status 7 error.
I use TWRP from the original development section.
Click to expand...
Click to collapse
+1 to this^^^^^
Look here»»» http://forum.xda-developers.com/showthread.php?t=1981198
And why not give him something stock instead of a CM Rom??[emoji37]
Plenty of stock 4.3 Rom's in the development section...
Sent from my SAMSUNG-SGH-I317 using Tapatalk
Good advice ^^^^ for your friend.
Ok, thanks for the direct response. I've downloaded the latest TWRP recovery and when I try to push it through ODIN, I still have PhilZ Touch 6..? Sorry, I feel like I'm skipping something simple...
according to a guide, I have to make sure when I'm pushing a custom recovery through ODIN I have to leave Auto Reboot and F. Reset Time UNCHECKED. I made sure they were, and for some reason after it says PASS and thread successful 1 failed 0. When I disconnect the phone and turn it back on into recovery mode, I still has PhilZ Touch...
Use your recovery to flash TWRP. There's a zip version and an odin version.
Ok, I got stock recovery on there just by redoing the CF-Auto Root package through ODIN.
I figured well I can apply the ROM the adb through the stock recovery...
It was going well until I got this error. The last line before the error stated:
"Veryfying update package..."
Error:
E: failed to verify whole-file signature
E: signature verification failed
is that due to the fact that i'm using stock recovery?
In the mean time since that didn't work I'm going to flash TWRP and hopefully that fixes the issue.
I'm kinda just documenting my steps here in case anyone wants to follow and chime in if i'm doing something wrong.
Thanks for the help guys!
************3AM EDIT*****************
Ok so I managed to get TWRP 2.7 on the device as I needed the ability to adb sideload the update.zip to the phone since I can't boot into the phone's OS whatsoever.
This is the error I'm receiving now:
Checking for MD5 file...
Skipping Md5 check: no MD5 file found.
then it restarts and I'm stuck at the Samsung GALAXY Note II screen... what's my next step..? Find a different ROM?
**********Another Edit**************
It has just come to me, I shouldn't have to adb sideload the update.zip or the custom rom... even though I can't get into the phones OS and can't copy and paste to the root of the device. Can't I just copy and paste it to a micro SD card and mount that, and then apply the update from there? And as far as those errors I had earlier, I'm still not sure why I received them...
Again, thanks for all the help
Adb won't work if USB debugging wasn't enabled.
In TWRP you can disable md5 checking.
And you don't unzip the zip file.
Thanks for the reply. ADB didn't work because, in fact, since I haven't been able to turn the phone on, I know USB debugging isn't turned on.
And as far as having the MD5 check, it is unchecked.
I received a success message. However, when I try to boot the phone it still gets stuck at the Samsung Galaxy Note II screen.
******Edit******
Ok ended up using a different ROM, I think PacMan rom? It seemed to work until it got to extracting system files and then the phone sits for a couple minutes, screen turns black. And when I try to wake the screen, only the back and menu buttons come up...
Another thing, even though I've already rooted my device using CF-Auto-Root, When I reboot my device with TWRP I go to reboot and then recovery. Then it warns me saying no OS bla bla bla, and then it says it notices that my phone isn't rooted? And that SuperSU isn't on the device. It asks to install it by swiping. I swipe it starts to install, phone reboots. When I reboot it again, it still tells me that the phone isn't rooted. And with the phone not being rooted, I'm coming to the conclusion why I'm having trouble trying to flash Roms.. Is this a possibility?
Why are you using ADB? just drop the .zip for the ROM you wish to flash onto a micro SD card, and flash from within the TWRP. Don't try to extract the .zip whatsoever.

Would like to return phone to Normal State

I ended up having to use CF auto-root, I was able to update cwm from within it.
After I tried rooting (didn't notice the guide I was using was 3 years old until it was too late) my phone got the "KERNEL IS NOT SEANDROID ENFORCING" and "SET WARRANTY BIT: KERNEL" . And it would not ****ing start up. My phone was 4.4.4 and I was trying to flash some 4.2.2 or later stuff onto it I guess, it messed my phone up. The only one and I mean ONLY one that would work was the 4.2.2 auto-root.
I was on kies before all of it and now kies won't even read my phone. Any way I can get my phone back to normal now, and possibly try the rooting again? It's slow and laggy now, my SD card won't be read, and my wifi doesn't work. I'm quite miserable but at least my phone works.. I have root access now so maybe I can fix it from within the phone? I appreciate the help!
EDIT: I tried getting cyanogen rom onto it and it got all messed up again after that, wouldn't get past cyanogen loading animation so I had to figure out how to fix it again for another 3 hours -.-
dameware said:
I ended up having to use CF auto-root, I was able to update cwm from within it.
After I tried rooting (didn't notice the guide I was using was 3 years old until it was too late) my phone got the "KERNEL IS NOT SEANDROID ENFORCING" and "SET WARRANTY BIT: KERNEL" . And it would not ****ing start up. My phone was 4.4.4 and I was trying to flash some 4.2.2 or later stuff onto it I guess, it messed my phone up. The only one and I mean ONLY one that would work was the 4.2.2 auto-root.
I was on kies before all of it and now kies won't even read my phone. Any way I can get my phone back to normal now, and possibly try the rooting again? It's slow and laggy now, my SD card won't be read, and my wifi doesn't work. I'm quite miserable but at least my phone works.. I have root access now so maybe I can fix it from within the phone? I appreciate the help!
EDIT: I tried getting cyanogen rom onto it and it got all messed up again after that, wouldn't get past cyanogen loading animation so I had to figure out how to fix it again for another 3 hours -.-
Click to expand...
Click to collapse
Go to this thread: http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
Download the NH7 or NK2 firmware (both are 4.4.4) and flash it using ODIN. Not sure why Kies isn't seeing your phone, it should, but ODIN should work. You may have to flash, pull battery, flash again, all without rebooting, for it to take.
This will get you back to stock. Then, if you want to root, get the CFAutoRoot for the phone, this will flash a non-stock recovery to give you root. This will give you the SEANDROID messages you were seeing. Use Triangle Away, if you want to get rid of them.
Rob
rlichtefeld said:
Go to this thread: http://forum.xda-developers.com/galaxy-s4-tmobile/general/firmwares-official-mdl-mk2-nb4-t2816508
Download the NH7 or NK2 firmware (both are 4.4.4) and flash it using ODIN. Not sure why Kies isn't seeing your phone, it should, but ODIN should work. You may have to flash, pull battery, flash again, all without rebooting, for it to take.
This will get you back to stock. Then, if you want to root, get the CFAutoRoot for the phone, this will flash a non-stock recovery to give you root. This will give you the SEANDROID messages you were seeing. Use Triangle Away, if you want to get rid of them.
Rob
Click to expand...
Click to collapse
It won't read it because my phone is now too old of a device for the program (2.2.2 or whatever). Thank you very much I'm trying all this right now, finally a firmware download that doesn't take 6 hours because of horrible servers!
I will update on if this works or not, I'm guessing it will
I am having a similar situation. I used CM installer to root my S4 then the screen went white and the Installer stopped working. I tried to reset but only got the same Enforcing and warrant messages and the CyanogenMod loading screen.
I am trying to get to recovery mode by doing power+home+volume up button. I got into there and seeing a menu of commands. What should I do now? Will factory reset get me back into original state or I need to install a zip?
Lopakas said:
I am having a similar situation. I used CM installer to root my S4 then the screen went white and the Installer stopped working. I tried to reset but only got the same Enforcing and warrant messages and the CyanogenMod loading screen.
I am trying to get to recovery mode by doing power+home+volume up button. I got into there and seeing a menu of commands. What should I do now? Will factory reset get me back into original state or I need to install a zip?
Click to expand...
Click to collapse
EDIT:
Done and done! It all worked out, thank you thank you!
Now to try cyanogen and my device will be back to beast mode.
Just do what he says and you should be fine; factory reset never did anything for me :/

Note 2 stuck at Start Up screen. Please help

My Galaxy Note 2 is stuck at the Start up screen screen. Where its an all black bg and simply says Samsung Galaxy Note II
I have tried using recovery mode, cleared cache, and reset to factory. Neither troubleshoot method worked.
I have tried numerous Odin autoroots. none work. Whenever I try to root it fails. Im guessing it might be because I dont have Dev Debug enable and I cant get into my phone to enable it. because of this issue
I have tried looking for TWRP .tar but every file I download the file is always a .img
The Model of the phone is a SGH-T889 (T-mobile Note II)
I am all out of ideas, and I dont know what to do. I have been search for answers for hours and everytime I think I found a solution it doesnt work.
What ROM was your phone on when this happened ?
Can you get int to download mode ? If yes try flashing stock ROM and see if it helps.
ciphercodes said:
What ROM was your phone on when this happened ?
Can you get int to download mode ? If yes try flashing stock ROM and see if it helps.
Click to expand...
Click to collapse
It was on the offical default rom. the phone was never modded, or rooted.
My niece downloads a bunch of kiddie games onto the phone, we constantly have to uninstall them. My thoughts and the T-mobile tech suspects that it the crash may have been caused my too many updates or a bad updated file most likely due to the games or game.
I can get the phone into download mode, and recovery mode.
In reovery mode I have 6 options
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cashe partition
apply update from cache
I have tried Apply update from cache, Wipe cache partition, then Wipe data.factory reset. I also attempted to put a CF auto root .md5 file and a KIES .md5 file which I believe is a stock firmware file on a SD card. to try to use the apply update from external storage option, but neither file showed up when I went into the option. So I guess I didnt have the right sort of file.
So recovery didnt work so I tried using Odin v3.07 and Odin v3.09 with CF auto root files for the SGH-T889, that didnt work, ecerytime I tried to apply it, It was always Fail within seconds. I tried other root files that are made for other versions of the Galaxt Note 2 like the GT-N1700 but those also simply failed.
I tried using what I believe to be stock frimware files with Odin. and those also Failed.
Im not exactly the best person with these. I learn mostly what I know from the internet and reading various forums, youtube videos, and other people experiences. I cannot find anyone who's problem has not yet been fixed through the above methods. so I really dont know where to go from here.
I think the reason I cant Flash from PC is because it might be possible USB Debugging is not enabled. Not sure if this is what is causing all the Fails in odin
BramaKnox said:
It was on the offical default rom. the phone was never modded, or rooted.
My niece downloads a bunch of kiddie games onto the phone, we constantly have to uninstall them. My thoughts and the T-mobile tech suspects that it the crash may have been caused my too many updates or a bad updated file most likely due to the games or game.
I can get the phone into download mode, and recovery mode.
In reovery mode I have 6 options
reboot system now
apply update from ADB
apply update from external storage
wipe data/factory reset
wipe cashe partition
apply update from cache
I have tried Apply update from cache, Wipe cache partition, then Wipe data.factory reset. I also attempted to put a CF auto root .md5 file and a KIES .md5 file which I believe is a stock firmware file on a SD card. to try to use the apply update from external storage option, but neither file showed up when I went into the option. So I guess I didnt have the right sort of file.
So recovery didnt work so I tried using Odin v3.07 and Odin v3.09 with CF auto root files for the SGH-T889, that didnt work, ecerytime I tried to apply it, It was always Fail within seconds. I tried other root files that are made for other versions of the Galaxt Note 2 like the GT-N1700 but those also simply failed.
I tried using what I believe to be stock frimware files with Odin. and those also Failed.
Im not exactly the best person with these. I learn mostly what I know from the internet and reading various forums, youtube videos, and other people experiences. I cannot find anyone who's problem has not yet been fixed through the above methods. so I really dont know where to go from here.
I think the reason I cant Flash from PC is because it might be possible USB Debugging is not enabled. Not sure if this is what is causing all the Fails in odin
Click to expand...
Click to collapse
Lets see if we can get this resolved.
1) Do you remember what version of Android the phone was on 4.3 or 4.1.2 ?
2) Put your phone in download mode then connect to your computer via usb. Start Odin in admin mode (right click and run as admin).
3) Now do you see ID:COM section turn blue ? Under message you can see "Added!". If you see this then phone is recognized by Odin.
4) If your phone was on 4.3 then download this most up to date firmware - from here http://www.sammobile.com/firmwares/download/22863/T889UVUCMK7_T889TMBCMK7_TMB/
5) Once downloaded, extract the file(use 7zip or winrar), once extracted you will see a file with .md5 extension.
6) Now going back to ODIN, click on PDA and then browse to this file which you just extracted.
7) This takes some time, once done you should see a message like "Checking MD5 finished successfully", "Leave CS".
8) You can leave Auto reboot and F-reset time checked.
9) Now click Start and let the process finish.
10) If everything goes fine you should see a green message "Pass"
Let me know how it goes.
I have the same problem as the OP (boots only up to Samsung logo with black bg) but it was not caused by niece downloading games but instead from trying to install jedi masterx2 rom.
I did what ciphercodes recommended and put phone in download mode and odin went through the motions of installing the stock os (in my case version 4.3) but after apparently installing the rom it again booted up to Samsung note II logo in black bg.
luckily I can install either Clockword mod recovery v6.0.4.3 or teamwin v2.8.6.0
The clockword mod recovery can read the external sd card (whereas funnily enough the teamwin can't) and I can attempt recovery from previous backups on cmr or to install a rom from zip file but neither of these work - reboots again to Samsung logo in black background after apparently installing the rom.
both teamwin and cwr mention that they can't mount system and that's probably why no rom is install either using cwr or odin so my guess is that I have to reformat the partitions cause probably efs file is corrupt but I don't know how to do that and I have done extensive search in google but have not found a solution
so ciphercodes if you or anyone reading this can help please reply to this message
ciphercodes said:
Lets see if we can get this resolved.
1) Do you remember what version of Android the phone was on 4.3 or 4.1.2 ?
2) Put your phone in download mode then connect to your computer via usb. Start Odin in admin mode (right click and run as admin).
3) Now do you see ID:COM section turn blue ? Under message you can see "Added!". If you see this then phone is recognized by Odin.
4) If your phone was on 4.3 then download this most up to date firmware - from here
5) Once downloaded, extract the file(use 7zip or winrar), once extracted you will see a file with .md5 extension.
6) Now going back to ODIN, click on PDA and then browse to this file which you just extracted.
7) This takes some time, once done you should see a message like "Checking MD5 finished successfully", "Leave CS".
8) You can leave Auto reboot and F-reset time checked.
9) Now click Start and let the process finish.
10) If everything goes fine you should see a green message "Pass"
Let me know how it goes.
Click to expand...
Click to collapse
I am uncertain of which version the phone was on. If you need I can call t-mobile and have them tell me which version it was on.
I did these steps. the file took a hour to download. and It still didn't work. I follow all steps down to the exact. and when I pressed start. within one second it said FAIL. just the other attempts I made.
BramaKnox said:
I am uncertain of which version the phone was on. If you need I can call t-mobile and have them tell me which version it was on.
I did these steps. the file took a hour to download. and It still didn't work. I follow all steps down to the exact. and when I pressed start. within one second it said FAIL. just the other attempts I made.
Click to expand...
Click to collapse
Unless your t889 Note II was sitting in a drawer and not being updated for the last year or so you probably have 4.3
When you go to download mode do you see "custom binary download: yes ..."
and do you see "knox warranty void:" ?
if so, your phone has been rooted.
but unlike your case, when I try to install stock rom through Odin, it goes through the motions of installing and gives message pass - that is that the stock rom has been installed, but unfortunately it has not installed any rom that my phone can read.
koyanishi said:
Unless your t889 Note II was sitting in a drawer and not being updated for the last year or so you probably have 4.3
When you go to download mode do you see "custom binary download: yes ..."
and do you see "knox warranty void:" ?
if so, your phone has been rooted.
but unlike your case, when I try to install stock rom through Odin, it goes through the motions of installing and gives message pass - that is that the stock rom has been installed, but unfortunately it has not installed any rom that my phone can read.
Click to expand...
Click to collapse
No it says
Product Name: SGH-T889
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Official
Knox Warranty Void: 0
RP SWAEV: A2
BramaKnox said:
No it says
Product Name: SGH-T889
Custom Binary Download: No
Current Binary: Samsung Official
System Status: Official
Knox Warranty Void: 0
RP SWAEV: A2
Click to expand...
Click to collapse
Then you have an un rooted 4.3 rom because the 4.1.2 did not have knox
koyanishi said:
Then you have an un rooted 4.3 rom because the 4.1.2 did not have knox
Click to expand...
Click to collapse
Okay thank you, well then link ciphercodes gave me for the firmware was the right one. But still Failed. *Sigh*
BramaKnox said:
Okay thank you, well then link ciphercodes gave me for the firmware was the right one. But still Failed. *Sigh*
Click to expand...
Click to collapse
Since your phone is not rooted then I think that ciphercodes advice will not work as you can only install a stock rom that way only if your phone is first rooted.
Probably you should try to root your phone using instructions from this thread
http://forum.xda-developers.com/showthread.php?t=2562994
But this might not work for you as it could be that efs file is corrupted or something else as we both boot up to a black screen that only has Samsung logo
koyanishi said:
Since your phone is not rooted then I think that ciphercodes advice will not work as you can only install a stock rom that way only if your phone is first rooted.
Probably you should try to root your phone using instructions from this thread
http://forum.xda-developers.com/showthread.php?t=2562994
But this might not work for you as it could be that efs file is corrupted or something else as we both boot up to a black screen that only has Samsung logo
Click to expand...
Click to collapse
Yeah the chainfire root fail as well. I have tried every file for all the Galaxy II's including mines. none work. Always FAIL in Odin. I'm guessing there is just nothing I can do
BramaKnox said:
Yeah the chainfire root fail as well. I have tried every file for all the Galaxy II's including mines. none work. Always FAIL in Odin. I'm guessing there is just nothing I can do
Click to expand...
Click to collapse
Since your phone is not rooted you may be able to get it repaired under warranty. I think that Samsung warranty is only good for a year, but if you purchased your phone with a American Express gold card (I think other gold cards will also apply) your warranty is extended to double what the original was. So perhaps you have a chance to have your credit card pay for the repair.
Otherwise:
I am no expert but if you want to continue playing with your phone before you get expert advice you may want to play with the recovery mode. To enter recovery mode press volume up and home and power buttons at the same time. once you feel vibrate or after a while release the power button but continue to hold volume up and home buttons and then you will enter recovery mode. you may want to go to menu that says wipe data/factory reset and see if that works. It may be that it is like my phone and the system cannot be mounted in which case you will get that message. After you are through to get out of this menu remove the battery.
But please be aware that I am no expert and you are using this info at your own risk
but I think of doing something catastrophic using this advice in my non expert opinion is small.
koyanishi said:
Since your phone is not rooted you may be able to get it repaired under warranty. I think that Samsung warranty is only good for a year, but if you purchased your phone with a American Express gold card (I think other gold cards will also apply) your warranty is extended to double what the original was. So perhaps you have a chance to have your credit card pay for the repair.
Otherwise:
I am no expert but if you want to continue playing with your phone before you get expert advice you may want to play with the recovery mode. To enter recovery mode press volume up and home and power buttons at the same time. once you feel vibrate or after a while release the power button but continue to hold volume up and home buttons and then you will enter recovery mode. you may want to go to menu that says wipe data/factory reset and see if that works. It may be that it is like my phone and the system cannot be mounted in which case you will get that message. After you are through to get out of this menu remove the battery.
But please be aware that I am no expert and you are using this info at your own risk
but I think of doing something catastrophic using this advice in my non expert opinion is small.
Click to expand...
Click to collapse
Yeah the warranty is expired. and I have tried recovery mode. thats actually the first step before trying to apply a firmware. So recovery hasnt worked either. Guess I will just have to get a new phone. thank you all for oyu help tho. I apperciate it
I was just reading through the thread.. It doesnt seem like you tried flashing Tmobiles Stock 4.3 Firmware in download mode. If you tried to flash a 4.1.2 Firmware when the phone was already updated then I think thats where it failed. Try again but with the 4.3 Firmware through ODIN. After it finishes try rebooting it manually and/or if it doesnt boot again then go back into recovery and factory/data reset again...shouldnt hurt to try..
Double0EK said:
I was just reading through the thread.. It doesnt seem like you tried flashing Tmobiles Stock 4.3 Firmware in download mode. If you tried to flash a 4.1.2 Firmware when the phone was already updated then I think thats where it failed. Try again but with the 4.3 Firmware through ODIN. After it finishes try rebooting it manually and/or if it doesnt boot again then go back into recovery and factory/data reset again...shouldnt hurt to try..
Click to expand...
Click to collapse
From my knowledge the other person who first replied gave me 4.3 firmeware fild link. But in the chances of it could u provide me with a link to a 4.3 firmware u believe will work, because all the ones I found have not worked

tmobile galaxy s6 edge g925t, missing OS. HELP!!!

I recently rooted my galaxy s6 edge g925t and was successful, but i couldn't stop there, i wanted to upgrade to android 6.0. i spent hours searching for a custom ROM/firmware and found one that i thought would work. I installed that custom OS through TWRP installer. After i finished the installation i tried to restart the phone but it just stayed at the "Samsung Galaxy S6 EDGE" boot logo and didn't play the boot animation. I searched online for ways of unbricking the phone and i eventually got to the recovery mode and tried to wipe the internal storage. then i restarted the phone and was back to the same Samsung logo. I again tried to get back to the recovery mode, but this time i did an advanced wipe and i ended up deleting the OS. if tried installing the stock ROM/firmware via Odin but can't get it to work. Is there anything i can still do? Can anyone please help me?
What happens when you try and flash the Odin image? The Rom you flashed, did that flash a new bootloader or firmware? If so it might have messed up the partitions on the phone.
M9x3mos said:
What happens when you try and flash the Odin image? The Rom you flashed, did that flash a new bootloader or firmware? If so it might have messed up the partitions on the phone.
Click to expand...
Click to collapse
The phone doesn't accept that either.
What custom ROM did you install? And what stock ROM did you try to ODIN flash?
Also, what is happening when you do that. I gathered out didn't work, but what error comes up?
zabrador said:
What custom ROM did you install? And what stock ROM did you try to ODIN flash?
Click to expand...
Click to collapse
TyrannusRomV23.1.zip is the custom rom, and SM-G925T_1_20150327095252_d1ygbqk7km (1) is the name of the stock i tried.
also the error that ODIN shows is that it FAILed and the phone shows in red letters in the top corner "check fail. DEVICE: 3, BINARY: 1
i dont know the entire message from the phone b/c my screen is blacked out in the top corner, but thats what i can see.
micahtjosaas said:
TyrannusRomV23.1.zip is the custom rom, and SM-G925T_1_20150327095252_d1ygbqk7km (1) is the name of the stock i tried.
also the error that ODIN shows is that it FAILed and the phone shows in red letters in the top corner "check fail. DEVICE: 3, BINARY: 1
i dont know the entire message from the phone b/c my screen is blacked out in the top corner, but thats what i can see.
Click to expand...
Click to collapse
Yeah, I don't think TyrannusRom is runnable on a G925T :/
Flashing stock with ODIN should do the trick. It's hard to tell where that stock file is from, so I would try to download the latest directly from SamMobile here (this is specifically for the G925T). If it's still not working, copy/paste the error ODIN is giving you here if you can.
Also, this thread seems to suggest you might be able to just re-flash the bootloader.
THANK YOU so much!!! that worked, iv looke on sammobile before but couldn't get anything to work, thanks so much
micahtjosaas said:
THANK YOU so much!!! that worked, iv looke on sammobile before but couldn't get anything to work, thanks so much
Click to expand...
Click to collapse
No problem! Glad you're back up and running

Categories

Resources