I can't load the stock rogers rom, odin3 keeps crashing, it crash with the stock root file I used to root my phone as well. I'm using virtualbox (I have a mac book pro), I recently formated my hard drive, I was sure to save the VM as is so everything is still the same, odin3 runs see my phone checks the file but when it gets to flashing it it crash no matter what file I try.. Is there something I do before flashing back to stock,I've searched but I can't find anything.
I'm not sure if Odin can be used in a VM.
It can, I used it to root my phone a few times, it worked great, reason why care about returning to stock is because Rogers or Samsung not sure one sent me a replacement phone so I want to send this one back stock.
Related
Hello everyone, first off, I read these two posts in their entirety:
http://forum.xda-developers.com/showthread.php?t=1009969
and
http://forum.xda-developers.com/announcement.php?f=943
I apologize if this might not be the best forum to post in, but as I just signed up I didn't have enough posts to post in the first thread like other people.
So I kinda have a good understanding of what I need to do with my phone, but need someone to recommend the best thing for me to do to change my firmware to 6.05.6 or 6.05.9, so allow me to share my rooting experience:
First off, I am running Windows 7 64-bit and I have never rooted a phone before and my Thunderbolt was my first droid device that I got 5 days ago on April 2nd, but I have plenty experience with flashing firmware for other devices such as routers, DVD drives etc. Initially I was not going to bother rooting my phone because of how complicated it looked, but then I found the one-click method and was becoming increasingly annoyed by not being able to get rid of the bloatware such as the Blockbuster app, Bitbop, Lets Golf 2, Rockband, Peep, and a couple others, so I decided to give the one-click method a shot.
Initially I had an issue with the ADB driver as Windows failed to install it successfully, after many agonizing minutes and a couple forums later, I installed HTC Sync and that fixed the issue, so now my batch file was working thus far. My second problem was the hbooteng.nb0 file. I had extracted the files from the exploits.zip correctly to the platform-tools folder, but my mistake was that instead of using the RUU filed and renaming it for the first flash, I initially flashed it with the one that was already name PG05IMG, so basically I thought I had done it correctly until I ran into the hbooteng.nb0 issue and realized I had flashed with the wrong file, leaving my phone basically unchanged and unrooted, but working perfectly fine.
Sooo I started over, this time knowing for sure I was using the correct files, and the process went pretty smoothly and the oneclick method told me my phone was rooted and to install the SU and ROM Manager so I did. Also did the clockworkmod thing as well.
But here is where my current problem is: My firmware is the 605.10 version and I would like it to either be back at the stock 605.6 or the newer 605.9. My phone works modestly well with the 605.10 so far EXCEPT it isn't correctly detecting my location. I live in Indiana, but the clock keeps setting itself to Rio de Janeiro. Also if I try to use Google Earth and do "find my location" with the GPS enabled, it takes me to Rio de Janeiro!
So here is my question: Which method of getting to the 605.6 or 605.9 firmware is the safest for me to use? And will using the one-click batch file to flash to either of those firmwares be safe since in the beginning it says that method does not work unless it is already at 605.6 or 605.9? Or should I attempt to do the option of factory resetting my phone through the SDcard settings, and what will I lose, and will I be back at 605.6, OR am I somehow supposed to use the ROM Manager app to flash to 605.6 or 605.9?
Many thanks in advance!
Ok so I ended up using ROM Manager and flashed to the 1.12.605.06 and it worked successfully but now my phone is no longer rooted since the ShootMe app doesn't work.
When I first got my S2 I rooted it to remove some bloatware like orange backup and maps. I was looking to also remove the orange startup and shutdown logos but never found how to do this. Now I want to undo all I've done (not much really) and put it all back the way it was.
Having searched the webs I find all the results about flashing using Odin to a new custom ROM, but I'm sure this is what I want to do.
I am sure I made a backup of the original files but I can't find them anywhere on my computer. However, I have managed to find some files I must have originally used to root/flash.
Odin
S2Root 1.4.3
GT-I9100_XXKG3_insecure
GT-I9100_XXKG3_original
I have rebuilt my computer since I originally rooted my handset, so when I needed the drivers and installed Samsung Kies it told me I had an update to ICS. I've completed this but Sky Go is still saying my device is rooted and will not work. I've downloaded and tried superoneclick (latest version) but this crashes every time. Opening S2Root, which I'm assuming I used originally, and trying to Unroot it tells me my device is not rooted and aborts the operation.
How can I fix this now?
Thanks in advance
Boxa786 said:
When I first got my S2 I rooted it to remove some bloatware like orange backup and maps. I was looking to also remove the orange startup and shutdown logos but never found how to do this. Now I want to undo all I've done (not much really) and put it all back the way it was.
Having searched the webs I find all the results about flashing using Odin to a new custom ROM, but I'm sure this is what I want to do.
I am sure I made a backup of the original files but I can't find them anywhere on my computer. However, I have managed to find some files I must have originally used to root/flash.
Odin
S2Root 1.4.3
GT-I9100_XXKG3_insecure
GT-I9100_XXKG3_original
I have rebuilt my computer since I originally rooted my handset, so when I needed the drivers and installed Samsung Kies it told me I had an update to ICS. I've completed this but Sky Go is still saying my device is rooted and will not work. I've downloaded and tried superoneclick (latest version) but this crashes every time. Opening S2Root, which I'm assuming I used originally, and trying to Unroot it tells me my device is not rooted and aborts the operation.
How can I fix this now?
Thanks in advance
Click to expand...
Click to collapse
You in the right thread?
Sent from my SPH-L710 using xda premium
I have rooted many mobile devices and flashed numerous ROMS. However I recently purchased a Galaxy Note 10.1 2014 edition and have not been able to get very far in my attempts to root, etc. I have tried Odin and CF-Auto-Root and although it appears to be successful the device is not rooted. I want to install TWRP and then the knox free stock ROM. I am able to push the necessary files to the sdcard with ADB and I can see that the files are in /sdcard using ES File explorer. However when I boot into recovery mode /sdcard is red and at the top of the list and it will not let me navigate to it to install any zip files. I though at first it might be because of the MobileIron I use for company email but I did a factory reset and still have this problem. I just need to root the device so I can use Titanium BU to remove the Samsung apps I don't want. Any help with this would be most appreciated. What do I need to do?
~metafizik
Ultimately I think the first thing I need to resolve is that even though the Odin rooting process appears to be working according to Odin(PASS). The fact is that regardless which combination of Odin 3.07/3.09 and CF-Auto-Root (tried 2 versions) even though Odin says it was successful it turns out the device is not getting rooted. This should be a no brainer but for for whatever reason this device will not root so far.
Bumping this as I have not received any replies. I am hoping that someone has run across a similar situation and can offer some guidance.
Thank you,
~metafizik
metafizik said:
Ultimately I think the first thing I need to resolve is that even though the Odin rooting process appears to be working according to Odin(PASS). The fact is that regardless which combination of Odin 3.07/3.09 and CF-Auto-Root (tried 2 versions) even though Odin says it was successful it turns out the device is not getting rooted. This should be a no brainer but for for whatever reason this device will not root so far.
Click to expand...
Click to collapse
Did you install super su?Did you try to flash twrp.If your not rooted twrp will ask to root.Have you tried to install a root app and see if the permissions pop up?
When you say recovery do you mean the stock one?Im pretty sure i had same problem.It was rooted but i thought it wasnt.
mikep2323 said:
Did you install super su?Did you try to flash twrp.If your not rooted twrp will ask to root.Have you tried to install a root app and see if the permissions pop up?
When you say recovery do you mean the stock one?Im pretty sure i had same problem.It was rooted but i thought it wasnt.
Click to expand...
Click to collapse
This is a very strange deal. As previously stated I have tried various combinations of Odin and CF-Auto-Root and the Odin process completes with PASS. However when I boot the OS and run Titanium it is never able to gain root access and Root Checker says it is not rooted. Unfortunately even after doing a factory reset the MobileIron Admin console at work says it is rooted so I can't use it for company email. I have definitely tripped the Knox bit. Also I want to install TWRP and have pushed the file to /sdcard and can see it there using a file explorer app. However when I boot into stock recovery I cannot see any of the zip files I have copied there. I also tried to flash TWRP with Odin and again it completes with PASS but TWRP never gets installed. And yes I installed SuperSU but did so from the Play Store.
I purchased this device just last week. I am wondering if maybe Samsung has changed things in the past few weeks and locked these friggin things down even more? This is the first device of many I have owned that I couldn't root or install a custom recovery or ROM. In any case this will definitely be my last Samsung device. I would however like to do whatever I so desire with it since I paid good money for it.
I have resolved all of the problems I was having. They were all due to Knox and my inexperience with it. I was fortunate to have customized my Note 2 before it received the Knox updates. All is well and there is no new unknown vodoo lurking in the latest iteration of Samsung devices.
Hey All!
I have this very interesting problem with my SGH-T989D.
I have for years been installing customs ROMs unto my phone. The last ROM I used was CM11 20141201 Sultan Hercules, with the provided GApps. This was installed using CWM 6.0.4.3. I ran this for months with no issues. Earlier this week, I decided I would try something else. I rebooted and went into CWM recovery and did a few things first. I went and Fixed permissions, and formatted various partitions, and also did a factory reset/wipe of the device. Now when I fixed permissions the time it took seemed odd too me. Like almost a minute, and since then I have been having install issues like crazy. So, I basically ended up using ODIN 1.85 to flash a stock ROM I had from T-Mobile. Which seemed to work fine. When i was satisfied the phone was functioning properly, I then proceeded to install CWM 6.0.4.3 using ODIN. It flashed successfully, and it rebooted my device. However, it brought me to the ODIN emergency download window. where it tells you to plug in your phone to the pc and use KIES to recover to the device. Ok, fine I thought to myself, I'll try that. Now KIES doesn't recognize my device. It's definitely not a driver issue because it used to work fine before these problems. I am assuming it has something to do with the firmware counter on my device. Since it says it's at 6 now, even though it's an official ROM. I have also tried using Lorains thread to re-partition the internal memory using the his unmodified PIT file. But Odin crashes at the SET PARTITION screen when trying to flash it So, honestly I'm at a dead end as to what's going on with my device at the moment. Even when I try to flash an early stock version of a Telus ROM, it just keeps going back to emerg ODIN screen, even though ODIN flashes successfully.
Does anyone have any suggestions for me? If you require more information I will do my best to answer.
Thanks a million in advance.
DrexxHaze said:
Hey All!
I have this very interesting problem with my SGH-T989D.
I have for years been installing customs ROMs unto my phone. The last ROM I used was CM11 20141201 Sultan Hercules, with the provided GApps. This was installed using CWM 6.0.4.3. I ran this for months with no issues. Earlier this week, I decided I would try something else. I rebooted and went into CWM recovery and did a few things first. I went and Fixed permissions, and formatted various partitions, and also did a factory reset/wipe of the device. Now when I fixed permissions the time it took seemed odd too me. Like almost a minute, and since then I have been having install issues like crazy. So, I basically ended up using ODIN 1.85 to flash a stock ROM I had from T-Mobile. Which seemed to work fine. When i was satisfied the phone was functioning properly, I then proceeded to install CWM 6.0.4.3 using ODIN. It flashed successfully, and it rebooted my device. However, it brought me to the ODIN emergency download window. where it tells you to plug in your phone to the pc and use KIES to recover to the device. Ok, fine I thought to myself, I'll try that. Now KIES doesn't recognize my device. It's definitely not a driver issue because it used to work fine before these problems. I am assuming it has something to do with the firmware counter on my device. Since it says it's at 6 now, even though it's an official ROM. I have also tried using Lorains thread to re-partition the internal memory using the his unmodified PIT file. But Odin crashes at the SET PARTITION screen when trying to flash it So, honestly I'm at a dead end as to what's going on with my device at the moment. Even when I try to flash an early stock version of a Telus ROM, it just keeps going back to emerg ODIN screen, even though ODIN flashes successfully.
Does anyone have any suggestions for me? If you require more information I will do my best to answer.
Thanks a million in advance.
Click to expand...
Click to collapse
I think you might have to re-partition your phone. Sultan's ROMs partition your phone a certain way and there is a fix for your phone somewhere on here to allow you to install regular types of custom roms.
I was using Chrome when the phone froze. I restarted it, and now the phone just hangs at the Samsung logo.
I have a completely stock unrooted Sprint SPH-L710. I'm moderately sure the phone is on MD4 since I didn't want Knox. It would be nice if there were a way to double check, though, since I don't remember why it stopped pestering me to upgrade. The phone doesn't boot far enough to get into safe mode, but it will enter recovery and download mode. Clearing the cache in recovery had no effect.
My PC and Kies don't see it when I connect it.
My contacts and photos are mostly backed up, so I'm more worried about salvaging other things, like Chrome bookmarks. My bookmarks aren't synchronized with Google. Apparently root is required to access them, so I never got around to it. It would be nice to recover text messages and gamesaves too. I haven't tried a factory reset yet since that would wipe everything.
What should I do from here? Is it possible to install a custom recovery at this point and use that to backup files?
Or should I try to flash a stock rom from the SD card or Odin? Or will that wipe everything or cause other problems?
I don't have USB debugging activated, so is there anything useful I'd be be able to do with ADB?
Or should I just shrug and go for the factory reset?
Thanks guys.
It's been an educational experience.
Without root or USB debugging enabled, it's apparently impossible to install custom firmware from soft bricked status.
ADB was never even able to see my phone. Not even in recovery or download modes.
Odin is a surprisingly temperamental program. It would see my phone, but not successfully flash until I uninstalled Kies. Rwilco's ROM's and one click flashes were all entirely unsuccessful. It's difficult to find older GS3 ROM's since link rot has claimed nearly all of them. There's about a million skeychy Samsung firmware/update sites, and most of them are worthless.
Heimdall is a little disappointing. You can't just point it at a ROM. You have to track down a Heimdall specific package. I couldn't find a suitable one.
Eventually, I found a sketchy Samsung firmware site that had the MD4 ROM, and it actually flashed in Odin. Then Odin stopped seeing my phone entirely.
So, I ordered a Tmobile Note 4 to use on Ting. It's cheaper, and I like the removable battery and microSD. Just for kicks, I factory reset the S3. To my surprise, the factory reset worked. I guess I should have tried that before I ordered a new phone
In the meantime, I guess I will still try to recover files, demote the S3 to media player/backup phone status, and use the incoming Note 4 as my daily driver.
From here on, I guess it means rooting and monthly backups.
Thanks guys.
When you boot into download mode you'll see your Knox flag if the phone has been upgraded to a Knoxed up firmware. I'm too lazy to check but it looks something like Knox: 0x0 or 0x1.