Related
Hello Everyone. First and foremost, thanks for all the helpful tips you guys have provided, been lurking here for a year or so.
Okay so heres the deal. I used skunkApes rooting method to root my phone last year. I just used the files included there and didn't do any custom roms or anything.
The last OTA update, didnt remove my root so after a few drinks and seeing that notification bar, i said why not. Well this one did. I checked SuperSU and it said no binary files found, must re-root. And my root checker says no root access. In developer menu, i dont see a tab for root to tick.
I tryed unistalling superSU, and that didnt work when i reinstalled. I can get to Download mode, but when I do recovery, it looks like its the stock android recovery.
Any help woul be much appreciated.
oh and sorry if this is in the wrong place, i wasnt sure if should had tagged this in teh "How to root" thread.
Phone infor- Spring G3, USA,
SPH-L710android version 4.3
Thanks
Use caution. If you aren't already aware, the 4.3 OTA update came with a sneaky bonus in the form of the KNOX bootloader. You're definitely going to want to familiarize yourself with it if you've got it because it looks like it's here to stay and it's got real potential for screwing you.
As for regaining root, all the resources you're likely to need are here: http://forum.xda-developers.com/showthread.php?t=2541900
I've been preaching that link all morning as my own personal Jesus Christ.
cwm
FallenZen said:
Use caution. If you aren't already aware, the 4.3 OTA update came with a sneaky bonus in the form of the KNOX bootloader. You're definitely going to want to familiarize yourself with it if you've got it because it looks like it's here to stay and it's got real potential for screwing you.
As for regaining root, all the resources you're likely to need are here: http://forum.xda-developers.com/showthread.php?t=2541900
I've been preaching that link all morning as my own personal Jesus Christ.
Click to expand...
Click to collapse
Hey Fallenzen, Thanks for the response, i see that you have been busy helping members this week!
Ok, so, when I try to go to recovery, Vol Up,menu and power, it looks like my clockwork recovery is gone and it shows the default one. No option to clear cache or make back up, just the android in surgery picture.
How do I get it back?
Thanks
Praz21 said:
Hey Fallenzen, Thanks for the response, i see that you have been busy helping members this week!
Ok, so, when I try to go to recovery, Vol Up,menu and power, it looks like my clockwork recovery is gone and it shows the default one. No option to clear cache or make back up, just the android in surgery picture.
How do I get it back?
Thanks
Click to expand...
Click to collapse
I've really just been trying to share what I learned from my recent update nightmare, I'm still just another noob. Anyhow, you should just be able to reflash CWM using ODIN. I am uncertain whether or not this will trip the KNOX warranty bit though (I don't know when I triggered mine since I wasn't even aware it existed until too late). If you haven't already triggered it, you might want to exercise patience and just keep reading what the devs are figuring out because once KNOX fires there's no going back, short of replacing the motherboard, at this time on account of the physical change it makes to your hardware.
I don't have a link handy, but I've been reading about Root De La Vega, which exploited a hash vulnerability to allow custom flashing without triggering KNOX. Samsung has patched the vulnerability, so it may or may not be an option for you but it's probably at least worth looking into.
FallenZen said:
I've really just been trying to share what I learned from my recent update nightmare, I'm still just another noob. Anyhow, you should just be able to reflash CWM using ODIN. I am uncertain whether or not this will trip the KNOX warranty bit though (I don't know when I triggered mine since I wasn't even aware it existed until too late). If you haven't already triggered it, you might want to exercise patience and just keep reading what the devs are figuring out because once KNOX fires there's no going back, short of replacing the motherboard, at this time on account of the physical change it makes to your hardware.
I don't have a link handy, but I've been reading about Root De La Vega, which exploited a hash vulnerability to allow custom flashing without triggering KNOX. Samsung has patched the vulnerability, so it may or may not be an option for you but it's probably at least worth looking into.
Click to expand...
Click to collapse
Custom recovery and custom ROMS will trip knox. If you have knox you can not flash backwards (back to 4.1.2 or lower than 4.3) because it will brick ur device. If ur not worried about tripping knox...iv got a note 3 and I tripped knox the first day I bought it...then by all means root and flash a custom recovery. If u haven't updated yet don't if you want the ROMS that are 4.1.2 or check out the 4.3 options in android development that left the knox bootloader out. If you choose to flash one of those that do not have the knox bootloader you can flash backwards. I'd suggest reading cnexus' "knox and you" in general. Lots of good info out here...keep reading and asking questions.
http://i.imgur.com/qrByUGN.jpg
same issue
I got the same issue here. Did not expect to lose root with the 4.3 OTA update, but I have! I got ODIN to flash CWM recovery and I got into recovery boot mode, and was able to install superuser. Once the phone booted up I got that bullS*it gray shield icon notice about "attempt to access secure area" (KNOX?) and now I cant get root access. WTF?! Please help, I need TrevEMod back in my life!
question
Since i am so new I cant post this reply in the following thread,
http://forum.xda-developers.com/showthread.php?t=2541900
but Ill ask here.
Will flashing this ROM work AFTER updated to 4.3 OTA with this KNOX already installed? I dont know, havent tried it yet?
onion root
bigpappags3 said:
Custom recovery and custom ROMS will trip knox. If you have knox you can not flash backwards (back to 4.1.2 or lower than 4.3) because it will brick ur device. If ur not worried about tripping knox...iv got a note 3 and I tripped knox the first day I bought it...then by all means root and flash a custom recovery. If u haven't updated yet don't if you want the ROMS that are 4.1.2 or check out the 4.3 options in android development that left the knox bootloader out. If you choose to flash one of those that do not have the knox bootloader you can flash backwards. I'd suggest reading cnexus' "knox and you" in general. Lots of good info out here...keep reading and asking questions.
Thanks for the info. Yea, my phone is already a year old so from what Ive read from that thread is that it just voids the warranty.
I guess i have to re-visit the rooting process. I just would like to get root back so I could use my wifi teather and bluput to control my ps3 again.
Any help is much appreciated.
Click to expand...
Click to collapse
Guessing I'm going to wait until a .tar file is released to flash custom recovery and root. I need a flawless phone and a lot of issues being reported in the use of cnex 4.3 rom release.
Sent from my SPH-L710 using xda app-developers app
SwellVermin said:
Since i am so new I cant post this reply in the following thread,
http://forum.xda-developers.com/showthread.php?t=2541900
but Ill ask here.
Will flashing this ROM work AFTER updated to 4.3 OTA with this KNOX already installed? I dont know, havent tried it yet?
Click to expand...
Click to collapse
Simple answer I believe is no. ... You have the knox bootloader. . That room will brick you device because ur trying to put an older bootloader on your phone.
http://i.imgur.com/qrByUGN.jpg
Got Root Back
But not all apps functioning. I used ChainFire's Auto Root method in ODIN to get root back, downloaded SuperSU from play store and used it to disable KNOX.
Now TrevEMod WifiTether not working. Help?
SwellVermin said:
But not all apps functioning. I used ChainFire's Auto Root method in ODIN to get root back, downloaded SuperSU from play store and used it to disable KNOX.
Now TrevEMod WifiTether not working. Help?
Click to expand...
Click to collapse
Out of curiosity is your SELinux status "Permissive" or "Enforcing"? Also, tethering is a known issue on 4.3 stock update, TrevEMod probably isn't going to work regardless. Is that the only app giving you problems?
We have a member who figured out a wireless tether fix on Android Forums, check out this link:
http://androidforums.com/virgin-mobile-galaxy-s3-all-things-root/800923-solved-mk5-4-3-stock-working-wireless-tether.html
It is for Virgin Mobile but should still work for Sprint or Boost for that matter since all three are SPH-L710.
SwellVermin said:
Since i am so new I cant post this reply in the following thread,
http://forum.xda-developers.com/showthread.php?t=2541900
but Ill ask here.
Will flashing this ROM work AFTER updated to 4.3 OTA with this KNOX already installed? I dont know, havent tried it yet?
Click to expand...
Click to collapse
That ROM worked for me after the OTA update to 4.3 screwed up my phone. I have the KNOX bootloader. I have tripped the Warranty Void bit, but since my phone is flashed from Sprint to Verizon I don't much care about that. My phone, with this ROM and the appropriate fixes (sprint hotspot, wifi, etc) works flawlessly. I have observed a bit of response lag on the lock screen, but it is not excessive and the lag is display-oriented as I can enter my lock code at full speed and it detects every touch just fine. I don't even notice it at this point.
Hope that helps.
Mr. Struck said:
Out of curiosity is your SELinux status "Permissive" or "Enforcing"?
Click to expand...
Click to collapse
What? lol Where is this setting found?
---------- Post added at 03:53 PM ---------- Previous post was at 03:41 PM ----------
FallenZen said:
That ROM worked for me after the OTA update to 4.3 screwed up my phone. I have the KNOX bootloader. I have tripped the Warranty Void bit, but since my phone is flashed from Sprint to Verizon I don't much care about that. My phone, with this ROM and the appropriate fixes (sprint hotspot, wifi, etc) works flawlessly. I have observed a bit of response lag on the lock screen, but it is not excessive and the lag is display-oriented as I can enter my lock code at full speed and it detects every touch just fine. I don't even notice it at this point.
Hope that helps.
Click to expand...
Click to collapse
But if this is the only way to get my wifi hot spot back, then I guess ill try it out. Theres a lot of steps to do to get this working correctly, huh? Im not that advanced and Im afraid Ill F something up!!
SwellVermin said:
What? lol Where is this setting found?
---------- Post added at 03:53 PM ---------- Previous post was at 03:41 PM ----------
But if this is the only way to get my wifi hot spot back, then I guess ill try it out. Theres a lot of steps to do to get this working correctly, huh? Im not that advanced and Im afraid Ill F something up!!
Click to expand...
Click to collapse
Well, here are my notes from my installation procedure. You can judge for yourself whether or not you're comfortable doing so, but be aware that this WILL trip your KNOX Warranty Void bit.
These notes were created for my own use in the event that I want to duplicate this procedure later since my pre-KNOX notes were rendered useless by the OTA update.
----------------------------------------
http://forum.xda-developers.com/showthread.php?t=2541900
Save all files to the phone's internal memory and remove microSD card.
Use ODIN3 to flash CWM-Recovery-LTE-SGS3-v5.tar.md5 to the phone with the PDA function.
Boot phone into the Recovery Console.
- Install SPHL710_MK3_rooted_odexed.zip
Use ODIN3 to flash CF-Auto-Root-d2spr-d2spr-sphl710.tar.md5 to the phone using the PDA function.
* Note, after this you might find you need to flash CWM Recovery to the phone again if the Android recovery console reappears.
From the CWM Recovery Console:
- Install Knox_APP_remover.zip
- Install wifi_fix_mk3.zip
- Install UPDATE-SuperSU-v1.80.zip
- (optional) Install MK3HotspotMod-odex.zip
- (optional) Install MK3_more_toggles.zip
Reboot the phone. If all goes well, it should load smooth as silk. Then all you need to do is execute the SuperSU app before attempting to operate any other apps that require root access and you should be golden.
----------------------------------------
It should be noted that I use ODIN 3.07 for this and am no longer on v1.85
Let me know if you need any clarification on the notes and I'll do my best.
Edit:
Also, do NOT use TriangleAway. I haven't tried it, but all of my reading suggests that it is a one way ticket to Bad News Blvd.
SwellVermin said:
What? lol Where is this setting found?
Click to expand...
Click to collapse
Settings/About Phone, scroll to the bottom. More of an issue for 4.4 than 4.3, as the default for 4.3 is Permissive and the default for 4.4 is Enforcing. In Enforcing mode it will sometimes block root-related apps, but it can manually be set to Permissive for 4.4 users.
FallenZen said:
Well, here are my notes from my installation procedure. You can judge for yourself whether or not you're comfortable doing so, but be aware that this WILL trip your KNOX Warranty Void bit.
These notes were created for my own use in the event that I want to duplicate this procedure later since my pre-KNOX notes were rendered useless by the OTA update.
----------------------------------------
http://forum.xda-developers.com/showthread.php?t=2541900
Save all files to the phone's internal memory and remove microSD card.
Use ODIN3 to flash CWM-Recovery-LTE-SGS3-v5.tar.md5 to the phone with the PDA function.
Boot phone into the Recovery Console.
- Install SPHL710_MK3_rooted_odexed.zip
Use ODIN3 to flash CF-Auto-Root-d2spr-d2spr-sphl710.tar.md5 to the phone using the PDA function.
* Note, after this you might find you need to flash CWM Recovery to the phone again if the Android recovery console reappears.
From the CWM Recovery Console:
- Install Knox_APP_remover.zip
- Install wifi_fix_mk3.zip
- Install UPDATE-SuperSU-v1.80.zip
- (optional) Install MK3HotspotMod-odex.zip
- (optional) Install MK3_more_toggles.zip
Reboot the phone. If all goes well, it should load smooth as silk. Then all you need to do is execute the SuperSU app before attempting to operate any other apps that require root access and you should be golden.
----------------------------------------
It should be noted that I use ODIN 3.07 for this and am no longer on v1.85
Let me know if you need any clarification on the notes and I'll do my best.
Edit:
Also, do NOT use TriangleAway. I haven't tried it, but all of my reading suggests that it is a one way ticket to Bad News Blvd.
Click to expand...
Click to collapse
Ok, tried to do the first step here. This is what ODIN says when I try to load the CWM-Recovery-LTE-SGS3-v*.tar.md5 file.
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> CWM-Recovery-LTE-SGS3-v5.tar.md5 is invalid.
<OSM> End...
Not sure what to do here. Please let me know what you think?
I just tried to boot into recovery mode and of course it's the stock android recovery. Bah!
SwellVermin said:
Ok, tried to do the first step here. This is what ODIN says when I try to load the CWM-Recovery-LTE-SGS3-v*.tar.md5 file.
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> MD5 hash value is invalid
<OSM> CWM-Recovery-LTE-SGS3-v5.tar.md5 is invalid.
<OSM> End...
Not sure what to do here. Please let me know what you think?
I just tried to boot into recovery mode and of course it's the stock android recovery. Bah!
Click to expand...
Click to collapse
I'm not sure, but the first thing I'd suggest is to try redownloading the file. Possibly from another source. Sounds like a bad download. If it continues to be a problem, I'll compile the exact files from my computer and make 'em accessible on my dropbox or something so you can try to use them... But that shouldn't be necessary. Also, remember that you want to flash the file via ODIN using the PDA option and make sure that both Auto Reboot and F. Reset Time are checked but that nothing else is.
yeah I tried that
FallenZen said:
I'm not sure, but the first thing I'd suggest is to try redownloading the file. Possibly from another source. Sounds like a bad download. If it continues to be a problem, I'll compile the exact files from my computer and make 'em accessible on my dropbox or something so you can try to use them... But that shouldn't be necessary. Also, remember that you want to flash the file via ODIN using the PDA option and make sure that both Auto Reboot and F. Reset Time are checked but that nothing else is.
Click to expand...
Click to collapse
I downloaded from 3 different sources, all the same result when loading the file into ODIN via PDA function. Hmph! Is it because I am on a stock recovery and ROM?
SwellVermin said:
I downloaded from 3 different sources, all the same result when loading the file into ODIN via PDA function. Hmph! Is it because I am on a stock recovery and ROM?
Click to expand...
Click to collapse
Shouldn't be... I'm also on a stock recovery and ROM. What version of ODIN are you using?
I was trying to install the Quantum Rom on my ATT Samsung Galaxy S3.
It failed a few times until someone posted that I need to update my bootloader to I747UCUEMJB. I was able to install the ROM after the update but now my phone won't recognize the SIM card that's worked flawlessly till I performed the bootloader update.
Is my phone done for good or is there something I can do here? Please help!!
Did you flash a compatible or updated modem?
audit13 said:
Did you flash a compatible or updated modem?
Click to expand...
Click to collapse
Sorry not really sure what that means. Also, just went in to my settings and under Baseband version I am seeing Unknown.
I checked the size of the bootloader I downloaded and it's only at 1.1 mbs and I just found the same bootloader online but at 623 mbs. I am assuming the bootloader I installed might be corrupt/fake?
I am downloading the larger file now and am going to try and install that too see if that helps?
There is no way the bootloader would be 623 MB.
Try flashing a modem from here: http://forum.xda-developers.com/showthread.php?t=1831898
audit13 said:
There is no way the bootloader would be 623 MB.
Try flashing a modem from here: http://forum.xda-developers.com/showthread.php?t=1831898
Click to expand...
Click to collapse
Yeah figured as much, especially after looking at the contents of the file, I decided not to use it.
Thanks for the link. Just downloaded modem_CWM_I747UCUEMJB.zip and I have my network signal back up now. I am hoping this means I am good. Will let you know soon. Thanks!!!
theproman23 said:
Sorry not really sure what that means. Also, just went in to my settings and under Baseband version I am seeing Unknown.
I checked the size of the bootloader I downloaded and it's only at 1.1 mbs and I just found the same bootloader online but at 623 mbs. I am assuming the bootloader I installed might be corrupt/fake?
I am downloading the larger file now and am going to try and install that too see if that helps?
Click to expand...
Click to collapse
Your baseband/modem is indeed corrupt. Before downloading or flashing ROMs please research thoroughly to be sure you know what you are doing and understand the difference between all the different files. The file you saw at 623mb is most likely the system or ROM file itself. The bootloader file itself is a much smaller file - consistent with a 1MB+ download. If you succeed with the file you are trying to download, you most probably would be updating your ROM although I'd be very doubtful if it would work. I'm not too certain but the 623MB file looks like the 4.3 update zip which usually works only when you are doing a manual update from an earlier ROM especially the immediate predecessor 4.1.2.
To correct your modem, I would suggest you try downloading and flashing the 4.3 modem file.
You may also need to install custom recovery (e.g. TWRP or CWM) for an easier installation. I presume warranty is no longer an issue with your phone in view of the firmware history.
Edit;
Just saw the last post from Audit after sending mine. Glad to know all is OK now.
Larry2999 said:
Your baseband/modem is indeed corrupt. Before downloading or flashing ROMs please research thoroughly to be sure you know what you are doing and understand the difference between all the different files. The file you saw at 623mb is most likely the system or ROM file itself. The bootloader file itself is a much smaller file - consistent with a 1MB+ download. If you succeed with the file you are trying to download, you most probably would be updating your ROM although I'd be very doubtful if it would work. I'm not too certain but the 623MB file looks like the 4.3 update zip which usually works only when you are doing a manual update from an earlier ROM especially the immediate predecessor 4.1.2.
To correct your modem, I would suggest you try downloading and flashing the 4.3 modem file.
You may also need to install custom recovery (e.g. TWRP or CWM) for an easier installation. I presume warranty is no longer an issue with your phone in view of the firmware history.
Edit;
Just saw the last post from Audit after sending mine. Glad to know all is OK now.
Click to expand...
Click to collapse
I completely understand what you're saying. Truth is I don't enough about all this to do what I did. Lesson learned for sure!
So. I was able to install the Modern bootloader and have my LTE signal back up and confirmed things are working given someone already called me and the call came through fine.
Now, the last thing I need to figure out is how to get WIFI to work. It's connecting to my router and has gone through authentication and has saved my network on the list of WIFI spots but I can't seem to connect and start downloading apps without eating my data.
Never mind, finally got wifi to work. Thanks again!!
Are you using any sort of encryption on your wifi network (i.e. WPA, WPA2, etc.)? Can it connect if you disable encryption?
Does anyone have a stock firmware of their S6 Edge T-Moible? that's ODIN flashable. I bricked my S6 trying to root it and had the KNOX security on. Now it just boot loop. :crying:
Protomize said:
Does anyone have a stock firmware of their S6 Edge T-Moible? that's ODIN flashable. I bricked my S6 trying to root it and had the KNOX security on. Now it just boot loop. :crying:
Click to expand...
Click to collapse
hey you're not alone! a lot of people are in your situation right now including me. we have to wait until there is a firmware available on Sammobile. hang tight.
samanbabah said:
hey you're not alone! a lot of people are in your situation right now including me. we have to wait until there is a firmware available on Sammobile. hang tight.
Click to expand...
Click to collapse
I managed to find a solution. Go here: http://forum.xda-developers.com/tmo...ow-to-brick-s6-s6-edge-knox-security-t3075720
Protomize said:
I managed to find a solution. Go here: http://forum.xda-developers.com/tmo...ow-to-brick-s6-s6-edge-knox-security-t3075720
Click to expand...
Click to collapse
That doesn't fix issues for those of us that need to have the full stock firmware to re-Odin with. Guess those of us in the same boat wait a week or so. My problem was removing the knox files with root explorer. Bad move. Makes the phone unbootable. Called Samsung tech support and they confirmed that. Rooting no problem. Recovery screen totally blank. Never get to see the the white/green screen some say they have for a recovery screen. The magic use volume up keys 7 times etc I have seen posted don't work for me. Samsung specifically told me the stock firmware is proprietary, so they wouldn't give it to me. I can wait a week or so for developers to get their hands on appropriate files, including a custom recovery that actually works...like good old TWRP :victory:
Protomize said:
Does anyone have a stock firmware of their S6 Edge T-Moible? that's ODIN flashable. I bricked my S6 trying to root it and had the KNOX security on. Now it just boot loop. :crying:
Click to expand...
Click to collapse
have you tried to flash the S6 file? not the S6 edge but the S6. Try to get yourself in download mode and do that. Make sure you are using the correct odin. That is what happened to me and I was able to obtain ROOT.
If you can get into download mode, you can now use Kies to install the stock firmware. Just did it about 3 mins ago.
SuperSport said:
If you can get into download mode, you can now use Kies to install the stock firmware. Just did it about 3 mins ago.
Click to expand...
Click to collapse
Where did you get the stock firmware. I'm not talking rooting file. I'm talking the full on tar to use to ODIN and flash the complete full stock firmware.
Docmjldds said:
Where did you get the stock firmware. I'm not talking rooting file. I'm talking the full on tar to use to ODIN and flash the complete full stock firmware.
Click to expand...
Click to collapse
I used Kies to restore the Firmware. Unfortunately, I was unable to find the Firmware file on my computer (Or could not figure out how to use it). I did see a temp file that was the correct size, but it's name and extension were wrong. I tried to open the file using 7-Zip and WinRar, but neither would open it. At that point, I just allowed Kies to do it's job, and it worked well. Removed ROOT and am now running Stock Firmware and Stock Recovery. KNOX is still tripped, but I don't care at this point.
In Kies, use the option: "Firmware Upgrade and Initialization". You will need your Model Name and Serial Number. Found on the box or in Settings if you can get there. I've got a T-Mobile Edge, so my Model Name is SM-G925T. Your serial will be unique.
SuperSport said:
I used Kies to restore the Firmware. Unfortunately, I was unable to find the Firmware file on my computer (Or could not figure out how to use it). I did see a temp file that was the correct size, but it's name and extension were wrong. I tried to open the file using 7-Zip and WinRar, but neither would open it. At that point, I just allowed Kies to do it's job, and it worked well. Removed ROOT and am now running Stock Firmware and Stock Recovery. KNOX is still tripped, but I don't care at this point.
In Kies, use the option: "Firmware Upgrade and Initialization". You will need your Model Name and Serial Number. Found on the box or in Settings if you can get there. I've got a T-Mobile Edge, so my Model Name is SM-G925T. Your serial will be unique.
Click to expand...
Click to collapse
I deleted via root explorer a slew of knox fies. Samsung told me by doing this, it renders the phone non bootable. That is why I need a full stock firmware tar file I can use in Odin, to flash the original complete firmware for my 925 Edge.Removing root, re-rooting, will not help. Chainfire said that SamMobile rleased the firmware files but all I get is web page not available. Grrrrr. Really wish someone would post the file in the Development sections or at least provide a working link.
Docmjldds said:
I deleted via root explorer a slew of knox fies. Samsung told me by doing this, it renders the phone non bootable. That is why I need a full stock firmware tar file I can use in Odin, to flash the original complete firmware for my 925 Edge.Removing root, re-rooting, will not help. Chainfire said that SamMobile rleased the firmware files but all I get is web page not available. Grrrrr. Really wish someone would post the file in the Development sections or at least provide a working link.
Click to expand...
Click to collapse
I had also removed all of the KNOX files, and most of the Samsung Files trying to get close to AOSP, but it became unstable. Kies re-installed the COMPLETE firmware again and all the stock files returned. I don't mean it removed ROOT only, it flashed the complete firmware. Kies uses ODIN internally to do the flash.
SuperSport said:
I had also removed all of the KNOX files, and most of the Samsung Files trying to get close to AOSP, but it became unstable. Kies re-installed the COMPLETE firmware again and all the stock files returned. I don't mean it removed ROOT only, it flashed the complete firmware. Kies uses ODIN internally to do the flash.
Click to expand...
Click to collapse
it's weird I can't use Kies at all.
samanbabah said:
it's weird I can't use Kies at all.
Click to expand...
Click to collapse
I can't use Kies either. Says phone not supported. I get the same exact error message. Oh my life savings for a nice .tar file to odin with
Wait
I think you should wait until pushed ODIN firmware over web...
dreamytricks said:
I think you should wait until pushed ODIN firmware over web...
Click to expand...
Click to collapse
Well, someone (Pagel) already posted the 920 stock tar file in the S6 thread. so there MUST be a source currently. Wish I knew why Sammobile web site returns errors for me about unable to open web page. That's the source most state is where to go.
Docmjldds said:
I can't use Kies either. Says phone not supported. I get the same exact error message. Oh my life savings for a nice .tar file to odin with
Click to expand...
Click to collapse
Okay I was able to find a workaround on how to restore my phone through Kies without getting an error.
do the following: 1) open Kies, click on tools, Firmware upgrade and initialisation, enter your model number and serial number and let it download the firmware, after an hour or so depending on your connection speed the firmware will be downloaded and your phone will reboot into recovery to install the firmware. done
samanbabah said:
Okay I was able to find a workaround on how to restore my phone through Kies without getting an error.
do the following: 1) open Kies, click on tools, Firmware upgrade and initialisation, enter your model number and serial number and let it download the firmware, after an hour or so depending on your connection speed the firmware will be downloaded and your phone will reboot into recovery to install the firmware. done
Click to expand...
Click to collapse
That's exactly what I was saying to do a few posts back. Did it yesterday and it worked fine.
EDIT: I'm going to run through it again and see if I can find the downloaded file. I believe I found it last time, but it was not a TAR file, rather a temp file specific to MY phone. But I'll try again, and if I get it, will post it here.
SuperSport said:
That's exactly what I was saying to do a few posts back. Did it yesterday and it worked fine.
EDIT: I'm going to run through it again and see if I can find the downloaded file. I believe I found it last time, but it was not a TAR file, rather a temp file specific to MY phone. But I'll try again, and if I get it, will post it here.
Click to expand...
Click to collapse
oh OK I didn't see your previews post.
samanbabah said:
oh OK I didn't see your previews post.
Click to expand...
Click to collapse
No problem, as long as we all get there at some point. The temp file that Kies downloads is called tmpE635.tmp It ends up being about 1.6GB in size. I tried to open it using 7-Zip and WinRar, but neither will open it. I'll post it in case anyone wants to try using it in ODIN. I don't know if it is specific to MY phone, or the T-Mobile S6 Edge in general (SM-G295T).
But, honestly, I would suggest you use Kies yourself so you are positive to get the correct file. You WILL get the error message that says Kies does not support your phone, just ignore that and keep going.
Phone Serial Number
I just realized that the Serial Number Kies is asking for is not on my Box. It's in the settings/about/status menu, and also on a sticker that is stuck to the Plastic Wrap that was around the phone in the box. Looks sort of like this: R58G31D1PBA. So, if you cannot get into your settings, or don't have that plastic, I'm not positive how you will get it to start the download. Maybe if you just use someone elses serial number, that will start the download???
EDIT: Link to the Temp File from Kies (not sure you'll be able to do anything with it)
https://mega.co.nz/#!39gwRAKS!H81yfo1vCQkMOujTaQJaU2INXoPNtUF6cgnF46jAfXI
WTF
Had the download stall on me twice, 35 and 47 percent.
old m9 ended up kicking the bucket sorta (usb died, so no way to charge the phone) so i bought a used one from swappa. it came with the latest ruu flashed, but i decided to reflash again to make sure it was totally clean (RUU_HIMA_UL_M60_SENSE70_ATT_MR_Cingular_US_3.38.502.12.exe). it went fine and so i began the process of unlocking it and flashing recovery (twrp 3.0.2.0) and flashing a rom (arhd 20 which is marshmallow) and titanium backuping back into shape. it unlocked and flashed recovery fine, however when i flashed the rom and did the first boot, i noticed i had no signal even though the stock rom had 4 bars of lte. it was also very laggy and had issues with crashing apps and for some reason still had at&t bloatware even though i did a dalvik/cache/system/data wipe beforehand and then a data wipe during the install and was missing inbuilt htc apps like internet. in the settings it shows that the imei, baseband, and other things related are all "unknown". i researched and came across a fix where you flash back your stock boot image, and it worked, except it would fail to boot after the first reboot. so that was useless.
i decided to try flashing arhd 14 (lollipop) because its what my old m9 had since forever and never gave me an issue. surprisingly, it actually installed and ran just fine even though the phone is on marshmallow firmware, as well as much quicker and smoother than arhd 20. however, i have the same issue. no signal, and imei and stuff "unknown". it does show my imei in download mode so i know the phone itself didnt forget it somehow. i have no idea what is going on here because ive literally never had this problem with any phone, even with my old m9 and i absolutely refuse to use a stock rom and have to manually deal with all of the bloatware especially with selinux making anything remotely "dangerous" an excessive hassle. can someone help me figure out this unnecessary pita?
this is what is shown in the download mode screen:
*** UNLOCKED ***
HTC_HIMAULATT PVT S-ON
LK-1.0.0.0000
RADIO-01.01_U11440801_96.01.51207A_F
OPENDSP-15.6.1.00522.8994_1026
OS-3.38.502.12
Did You Get Any Solutions ? :crying:
nope.
daktah said:
nope.
Click to expand...
Click to collapse
Can you please give me the link of stock img which helped you to get signal at first boot ? i am running on viper marshmallow rom.advance thanks to you
---------- Post added at 12:57 AM ---------- Previous post was at 12:55 AM ----------
and yes exact same problem is also happening with me It shows imei in fastboot,but In the settings and phone info,Imei shows unknown and no cell signals .I Just Bought THe phone 2 Days ago Happened after flashing the Ar Hd Rom
i used the boot from the nandroid i made of the stock ruu image before i tried to install arhd
I know I sound stupid, but actually I did'nt take any backup before flashing would you please upload it to somewhere and give me a link. It would mean a lot to me, thanks
daktah said:
i used the boot from the nandroid i made of the stock ruu image before i tried to install arhd
Click to expand...
Click to collapse
Are you S-OFF? if so, are you sure that you used the correct firmware. Never had this issue myself, but am remembering from the days on the M9 that such an issue could occur if a wrong firmware is flashed.
Another chance could be the following one: if your RUU didn't download correctly it might be damaged and thus have caused the problem. This may be the case as you're missing stock Apps after flash. Have you checked if the md5 of the downloaded file is correct.
Edit: report back if it helped.
Sent from my htc_pmeuhl using XDA Labs
5m4r7ph0n36uru said:
Are you S-OFF? if so, are you sure that you used the correct firmware. Never had this issue myself, but am remembering from the days on the M9 that such an issue could occur if a wrong firmware is flashed.
Another chance could be the following one: if your RUU didn't download correctly it might be damaged and thus have caused the problem. This may be the case as you're missing stock Apps after flash. Have you checked if the md5 of the downloaded file is correct.
Edit: report back if it helped.
Sent from my htc_pmeuhl using XDA Labs
Click to expand...
Click to collapse
Yeah turns out the latest arhd is made for 3.35 and I'm on 3.38, so that's why it's all jacked up. And of course there is no way to "downgrade" (see: upgrade) to a lower firmware without $25 s off. Pretty ridiculous I have to pay just to s off so I can put my phone on an older software that works better because of "security" (see: money).
daktah said:
Yeah turns out the latest arhd is made for 3.35 and I'm on 3.38, so that's why it's all jacked up. And of course there is no way to "downgrade" (see: upgrade) to a lower firmware without $25 s off. Pretty ridiculous I have to pay just to s off so I can put my phone on an older software that works better because of "security" (see: money).
Click to expand...
Click to collapse
I still think something went wrong when flashing RUU. A 3.35 based ROM shouldn't jack up anything, as long as your firmware is even a later one than the ROM base. Btw 25 bucks are well invested regarding all the work they do, but it's the wrong place to discuss. Did you check if the RUU downloaded correctly and the md5 after download still is the same as given in the dl link. Missing stock Apps after flashing an RUU are a major indicator for a bad download, and if firmware parts where missing in this download as well, you'll end up just as you'd described in your opening post.
Sent from my htc_pmeuhl using XDA Labs
I used the ruu 2 or 3 times and it worked fine every time and the stock rom runs just fine. It's when trying to flash the rom it doesn't work, and I used one I downloaded from my computer, from my phone, and one I already had on my SD and they all ended up with the same result.
5m4r7ph0n36uru said:
A 3.35 based ROM shouldn't jack up anything, as long as your firmware is even a later one than the ROM base.
Click to expand...
Click to collapse
It actually does. That's why thicklizard made his custom kernel. The 3.3x firmware versions for SKUs which skipped the 3.35 version are not compatible with 3.35 roms unless that kernel gets flashed.
Edit: I just read that the mono-revisited kernel is only for AOSP roms. I'm sorry but it seems like I don't have a solution for sense roms.
5m4r7ph0n36uru said:
Missing stock Apps after flashing an RUU are a major indicator for a bad download, and if firmware parts where missing in this download as well, you'll end up just as you'd described in your opening post.
Click to expand...
Click to collapse
Doesn't daktah say in the OP that he was missing those apps after flashing ARHD20? I never used that rom but it sounds like they got uninstalled during the installation. Does ARHD have an aroma installer like the Viper rom does where you can select which apps to install or not to install?
Sent from my HTC One S using XDA Labs
Flippy498 said:
Doesn't daktah say in the OP that he was missing those apps after flashing ARHD20? I never used that rom but it sounds like they got uninstalled during the installation. Does ARHD have an aroma installer like the Viper rom does where you can select which apps to install or not to install?
Click to expand...
Click to collapse
Thanks for the clarification mate.
Didn't remember this one.. guess it's already to long since I used my M9. I'm not sure if he tried to state exactly what I quoted from your post, cause he jumps from RUUing right to the flash of ARHD. never used it myself, this I don't know if it comes with an Aroma Installer at all. Either way it would be interesting to know what happens if he just boots into his stock ROM, to make sure the cause isn't a bad download of the RUU. Feel free to correct me if I'm mistaken
Sent from my htc_pmeuhl using XDA Labs
In theory you're right but I guess we both missed the post located directly above mine.
Sent from my HTC One S using XDA Labs
We did indeed. Blind I've become, as Yoda would state now.
Sent from my htc_pmeuhl using XDA Labs
So I managed to fix it... By replacing the USB/aux board in my phone. Only cost 10 bucks for a new one . However now i have a problem where my phone will not charge at full speed and will actually give me the "using too much power to charge" message when doing a titanium backup even on the stock charger. The battery was at dead flat 0 for like 5 days before I fixed it, so do I need to replace it or is there something else I can do to fix it? When it's full it holds a charge for as long as it did before, just charging is not working correctly it seems.
i have nandroid backup of 3.38.841.6 let me know if i can be any help, i"ll upload it on mediafire and give you link,
btw i had the same problem yesterday, i flashed my nandroid backup and things went smooth
i got no imei no network after flash AEHD20, so i flash back boot img from backup, everything fine but without root. i down load twrp backup from http://forum.xda-developers.com/one-m9/general/stock-nand-backup-ota-update-collection-t3132698, select the correct CID match your phone. my CID is HTC__044 with 3.42.708.3. After download backup unzip the file, done once backup boot file, copy the file from download overwrite your backup, then restore the file from backup. good luck. don't wipe!!!!!!
17/09/16
I install Viber one still no imei, restore back up boot, imei back but no root, install super su 2.65 everything fine got root and imei.
Install twrp 2.8.5.0 first then update to twrp 3.0.2.0
Hey arcslt18,
arcslt18 said:
i have nandroid backup of 3.38.841.6 let me know if i can be any help, i"ll upload it on mediafire and give you link,
btw i had the same problem yesterday, i flashed my nandroid backup and things went smooth
Click to expand...
Click to collapse
Do you still have that nandroid backup handy?
I think i do, Currently at work. i'll contact you as soon as i get my hands on it.
I've had this quite a lot of times but flashing a different kernel usually sorts of out right away
Edit: The Verizon repair assistant put my phone back to PHE build [100% battery].
Man I knew I shouldn't have tried to root after all this time. I'm not sure which firmware my phone was on [it was the 60% battery update], either PHE or PK1, as it displays in recovery right now. I tried to follow Lrileys modification of freeza's root guide, which neither of them specify a base firmware to go off of, lol.
Anyways, flashing the userdebug sprint firmware with ODIN 3.12.4 failed and my device softbricked. It boots into recovery and download mode.
I have tried factory reset, wiping cache partition, flashing an AP PH1 firmware, and repair through Verizon software/upgrade assistant.
The closest I've gotten to restoring it was with VUA, however when I go to the repair assistant page, it tells me to put phone in download mode [which I do] but the repair button stays greyed out.
Any help would be greatly appreciated.
Edit: The Verizon Upgrade Assistant wasn't starting, saying it was missing mfc90.dll. Well I downloaded the dll, dropped it in the folder, and was able to get UA to recognize phone. Repair assistant is downloading software right now, we'll see how it goes.
IF you would have read there is no root for the PHE.. you also could have checked this via phone settings before you rooted.
You can also use the verizon app to restore your firmware from even the most bricked of phones. Also in in this forum..(looks like you might have tried this?)
I wouldnt even bother at this point, go get your temp phone =]
ars0n said:
IF you would have read there is no root for the PHE.. you also could have checked this via phone settings before you rooted.
You can also use the verizon app to restore your firmware from even the most bricked of phones. Also in in this forum..(looks like you might have tried this?)
I wouldnt even bother at this point, go get your temp phone =]
Click to expand...
Click to collapse
Well the repair assistant seems to be working atm, so hopefully it goes through without any problems. Neither of these threads in the original post mentioned anything about incompatible firmware though [https://forum.xda-developers.com/verizon-note-7/how-to/root-vzw-note-7-t3448711 and https://forum.xda-developers.com/sprint-note-7/how-to/root-super-leaky-bros-sprint-galaxy-t3447202]. I suppose I should have known trying to use a method that dated.
You shouldn't be messing with this stuff if you don't even know how to see what version your on and read.
very helpful
jjayzx said:
You shouldn't be messing with this stuff if you don't even know how to see what version your on and read.
Click to expand...
Click to collapse
Thank you for the gratuitous reply. Despite your sour attitude I was able to return to PHE through VUA. I was running PK1 firmware, however, again, neither root method specified/recommended/listed a base or stock firmware to flash from [or even posted what they were running]. This place used to be helpful.