Related
I rooted my GT-N7105 using CWM6 and desktop Odin when I got it. I wanted to update to 4.1.2 without losing Root, so I decided to use Mobile Odin Pro with the EverRoot feature turned on.
I downloaded the new ROM to the root of the device (not the external SD card) and set Mobile Odin to install the new ROM and retain Root.
The device rebooted to the Mobile Odin icon, and then nothing... can't reboot, can't seem to recover, every time I try anything, it just reverts to the Mobile Odin icon.
Any Help?
How can I restore my phone?
flagg1209 said:
I rooted my GT-N7105 using CWM6 and desktop Odin when I got it. I wanted to update to 4.1.2 without losing Root, so I decided to use Mobile Odin Pro with the EverRoot feature turned on.
I downloaded the new ROM to the root of the device (not the external SD card) and set Mobile Odin to install the new ROM and retain Root.
The device rebooted to the Mobile Odin icon, and then nothing... can't reboot, can't seem to recover, every time I try anything, it just reverts to the Mobile Odin icon.
Any Help?
How can I restore my phone?
Click to expand...
Click to collapse
Hi mate, I would suggest you to use the odin from desktop and flash a stock rom and then try rooting again using odin from desktop with cf-autoroot.
With a little more searching, I discovered I had a broken cache. Installed a fix using desktop odin and am back where I started. When I get home later will try flashing a stock rom.
Do I need to use triangleaway first?
Broken cache was issue with very old recovery by chenglu, (i think that is already removed)
If so then just flash CF auto root package it should solve.
BTW what option you are selecting to flash ROM with Mobile Odin?
My unit is running 4.1.1 rooted with cwm6. I wanted to update to 4.1.2 and retain root. I downloaded the correct new rom for my carrier (Starhub in Singapore) from sammobile and extracted it to the root of my phone, then opened the file using Odin Mobile and told it to flash with EverRoot enabled.
That's where the process died and I was left with the Odin Mobile android logo frozen on my phone.
After unplugging and trying to reboot - it kept goign to the Odin Mobile logo so I rebooted into recovery mode and tried Odin Desktop to flash the Rom - no luck.
Then tried Odin Desktop with the cache fix I found earlier and that reset everything as if I hadn't started this process.
Now I'm unsure how to proceed.
Should I unroot, flash the stock rom then re-root? If so to flash the stock rom (using Desktop Odin, I assume), do I need to reset the counter? Using Triangleaway?
Am new to this phone so am not sure how to proceed. Any help would be appreciated.
First you check you have latest Mobile odin, if it happens with that too, do this
As per OP, you have CWM so your counter will be already 1 or more.
Simply flash new ROM with PC odin.(though it won't raise counter)
Reroot with Cf auto root.(this will raise flash counter)
Install triangle away and reset counter.
before doing this backup your important data, though above mention method won't erase anything, but in any step if you get bootloops, you may need to factory reset and that will erase data.
I've got it figured, I reckon.
I installed the new rom using Odin, then rooted using CF-Auto-Root
All seems well.
Thanks for the replies - I probably should have been a little more patient and worked it out myself!
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
I am in the middle of rooting my TMO GS3 with 4.1.2 and I am getting Android System Recovery instead of CWM recovery. What did I do wrong?
cybrguy1 said:
I am in the middle of rooting my TMO GS3 with 4.1.2 and I am getting Android System Recovery instead of CWM recovery. What did I do wrong?
Click to expand...
Click to collapse
What process did you try?
T-Mobile SGS III
re: sure way to root - success everytime
cybrguy1 said:
I am in the middle of rooting my TMO GS3 with 4.1.2 and I am getting Android System Recovery instead of CWM recovery. What did I do wrong?
Click to expand...
Click to collapse
There are dozens of ways to root your phone, some methods work better than others and some don't work at all.
Here is the way to root your phone with the T999 Jellybean 4.1.2 rom.
This method works all the time and every time, no more trial and errors.
Easy and sure way to have a fully rooted T999 Galaxy S3 - Here is s step by step guide:
Download the newest pre-rooted Samsung Galaxy S3 T999 Jellybean v4.1.2 rom: T999_UVDMD5
After downloading make a folder on your computer's desktop and unzip the
file using Winzip or 7zip so the .TAR file is in the new folder you just made.
Download and extract Odin into the same folder you made containing the TAR file
Here is the link for Odin: http://d-h.st/Q14
Download ODIN which is required for flashing the stock rooted firmware (a windows app)
Download the Odin Flash firmware for T999 Tmobile then copy it to the same folder as Odin
Run Odin by double clicking the Odin.exe within the same folder as the TAR file you extracted
Turn off your phone and boot into DOWNLOAD MODE (Volume Down + Home + Power Hold until phone powers up, then release and press Volume Up to enter Download Mode)
Once in Download Mode, connect the USB/Charger cable to the phone and plug into the USB port on your computer.
You should now see a COM** port listed toward the top-left of Odin (under ID:COM)
Click on the PDA button in the middle-right area of Odin.
Browse to and select the Firmware you downloaded (TAR file)
Make sure Auto-Reboot and F. Reset Time are the only options checked and that PDA is the only other thing checked.
TRIPLE CHECK your settings and that you have selected the correct firmware for your model phone and are using the correct options.
If you are using a laptop, make absolutely sure you are plugged in, or if on battery, that it is charged enough and will not go into sleep mode during flash.
Click Start to begin the flash. This will take a while, so be patient!
Once complete, in the top-left box in Odin, it will say PASS and the phone should have automatically rebooted.
You may unplug the phone and close Odin if you wish.
Wait at least 5-10 minutes for the system to boot the first time and then build its cache!
(It may seem to hang during boot, this is normal and you must be patient!!!)
Once it's rooted be sure to make a nandroid backup of the rom using cwm or twrp recovery.
Good Luck!
The above advice is irrelevant to the problem, way to read the OP. When you flash CWM with Odin, when you reboot your device, you need to drop to recovery before the device is allowed to boot. Do you understand? Flash CWM > boot straight into recovery. Once there you can exit. You will be prompted to disable some recovery crap. Do that.
mt3g said:
What process did you try?
T-Mobile SGS III
Click to expand...
Click to collapse
I've been following Max's galaxys3root.com video instructions. Used Odin 1.85, got the yellow COM indicator, ran the clockworkmod.tar, got the pass indicator and rebooted. Copied the CWM file to the phone. Can't seem to get into CWM recovery mode. Gives me Samsungs...
cybrguy1 said:
I've been following Max's galaxys3root.com video instructions. Used Odin 1.85, got the yellow COM indicator, ran the clockworkmod.tar, got the pass indicator and rebooted. Copied the CWM file to the phone. Can't seem to get into CWM recovery mode. Gives me Samsungs...
Click to expand...
Click to collapse
See my signature, too. Stop using files that are older than I am.
cybrguy1 said:
I've been following Max's galaxys3root.com video instructions. Used Odin 1.85, got the yellow COM indicator, ran the clockworkmod.tar, got the pass indicator and rebooted. Copied the CWM file to the phone. Can't seem to get into CWM recovery mode. Gives me Samsungs...
Click to expand...
Click to collapse
Do what aerowinder said.
T-Mobile SGS III
Aerowinder said:
See my signature, too. Stop using files that are older than I am.
Click to expand...
Click to collapse
OK, took your advice to heart and reflashed the newer (6.0.3.1) CWM, and I can now boot to it. Did an image.
Now, one of the main reasons I rooted the phone is so that I can add other programs to the MultiView feature. I most want Dolphin and my (stock) contact tool. Just dragging them to the tray doesn't get them there. I can imagine Dolphin may need to be reinstalled, but what would I need to do to get the built in contact tool to work with it?
Somehow I got the impression that rooting the phone would make everything available to MultiView...
You have to install the firmware with your recovery. Then it'll be available. Look in to the development section for the mod.
T-Mobile SGS III
mt3g said:
You have to install the firmware with your recovery. Then it'll be available. Look in to the development section for the mod.
T-Mobile SGS III
Click to expand...
Click to collapse
Sorry to be thick, but I don't know what you mean. I'm not sure what firmware you mean for me to install.
Rooting your device grants you permission to be able to do things. Not grant you things. You still need to flash a superuser root access .zip, a recovery doesn't grant root. I'm not on a PC so I'm not sure if what Aero pointed you towards also has the .zip you need included. Look in your app drawer and look for a superuser app. If its there then download this http://forum.xda-developers.com/showthread.php?t=2278022, And search how to flash a .zip in recovery. Make sure you read up a little more, and then ask questions before messing your phone up.
T-Mobile SGS III
Thanks, I do understand that rooting doesn't do anything but enable. I thought, though, that superuser was all I needed to enable most apps for multiview. I did flash SU when I rooted but mistakenly thought that would be enough for this feature.
There is an app that will grant the feature also, I don't use it but its out there. "multi window manager" that requires root so install it open it and follow instructions.
mt3g said:
There is an app that will grant the feature also, I don't use it but its out there. "multi window manager" that requires root so install it open it and follow instructions.
Click to expand...
Click to collapse
Thank You! That was exactly what I was looking for, and it works just fine.
https://play.google.com/store/apps/details?id=com.bjbinc.multiwindowmanager&hl=en
No worries. Forgot about the app for a few minutes glad I remembered lol.
T-Mobile SGS III
I have PayPal for which I will use to donate an amount to the person(s) who can help me.
I just recently got a new GS4 becuase of an insurance replacement. I looked at the specs before I flashed TWRP. After failing to install 4.2.2 ROMS, I finally found a 4.3 mk2 stock ROM to install. I have the phone working. But TWRP is not installed. My phone tests positive for ROOT with Rootchecker
Currently I'm getting this message everytime I boot "Kernel is not seandroid enforcing"
I have multiple 4.4.2 and 4.3 ROMs I like to use on my SD card, I'd like to continue from a TWRP backup i've made using that recovery.
Here are my current specs:
Model
SGH-M919
Android Version
4.3
Baseband
M919UVUEMK2
Kernel Version
[email protected] #1
Build Number
JSS15J.M919UVUEMK2
SELinux status
Permissive
Secure boot status
Type: Samsung
The replacement phone was probably already on the MK2 bootloader and modem when you received it. Which means you had Knox pre-installed and tripped it when you rooted the phone. The "kernel is not seandroid enforcing" error message does not affect the functioning of your phone in any way. It's just a part of the Knox bootloader. You can continue to re-install TWRP recovery and flash any ROM you want. Your phone will function as normal. Just don't try reverting to the 4.2.2 MDL baseband/modem because it won't work. There's currently no way to revert to 4.2.2 MDL if you're on MK2 or higher. If you want to get rid of the message just flash the stock kernel in a recovery.
Try to be careful with your replacement phone now since you tripped Knox. It might be harder to get a replacement depending on how T-Mobile is.
No donations are needed for these kinds of things.
Ok Im flashing Infamous 4.4.2 Version 3.7 after ODIN flashing TWRP 2.6.3.1
The only reason I'm flashing that ROM is because no backups are not showing theirselvesin the Restore option, what would cause that?
Is TWRP 2.5.0.2 better?
Did I miss a step? All my actions were using odin to flash the twrp recover, and then flash another ROM, or restoring a Previous Back. Should I have flashed a rooted bootloader, or rooted firmware or anything besides those two?
nopotential said:
Ok Im flashing Infamous 4.4.2 Version 3.7 after ODIN flashing TWRP 2.6.3.1
The only reason I'm flashing that ROM is because no backups are not showing theirselvesin the Restore option, what would cause that?
Is TWRP 2.5.0.2 better?
Click to expand...
Click to collapse
The backups could either be stored on the internal or external SD card. Try switching between both and see if they appear. They'll be in the TWRP folder on the root of either the internal/external storage.
I've had no problems with the latest TWRP v2.7.0.1. If you have problems then use v2.5.0.2.
If you have connection problems after installing Infamous 4.4.2, you might need to Odin the newest KitKat NB4 modem found here.
Download the file and flash MODEM.bin via Odin under the phone slot.
Personally, since you already tripped Knox, you should just Odin flash the complete NB4 KitKit stock ROM which will give you the newest modem without having to mess with anything else or do various flashing of things. Everything for flashing NB4 KitKit can be found here. Download the full 4.4 firmware from here.
brian117 said:
The backups could either be stored on the internal or external SD card. Try switching between both and see if they appear. They'll be in the TWRP folder on the root of either the internal/external storage.
I've had no problems with the latest TWRP v2.7.0.1. If you have problems then use v2.5.0.2.
If you have connection problems after installing Infamous 4.4.2, you might need to Odin the newest KitKat NB4 modem found here.
Download the file and flash MODEM.bin via Odin under the phone slot.
Personally, since you already tripped Knox, you should just Odin flash the complete NB4 KitKit stock ROM which will give you the newest modem without having to mess with anything else or do various flashing of things. Everything for flashing NB4 KitKit can be found here. Download the full 4.4 firmware from here.
Click to expand...
Click to collapse
I want to use a custom ROM because of the features. Should I still flash the latest firmware, the KitKat NB4?
nopotential said:
I want to use a custom ROM because of the features. Should I still flash the latest firmware, the KitKat NB4?
Click to expand...
Click to collapse
You will still be able to flash the custom ROM after you Odin flash the KitKat NB4 firmware. The steps are as followed:
1. Open Odin v3.07.
2. UNcheck the boxes that say auto reboot and f. reset time.
3. Power off your phone and enter Download Mode by holding down the Vol DOWN + Home + Power buttons at the same time. Hit Vol UP after the warning message comes up.
4. Connect your phone to your PC and wait for it to appear in the COM: box in Odin.
5. Click the PDA tab and select the "M919UVUFNB4_HOME.tar.md5" file that you extracted from http://www.cheatersedge.org/android/m919/M919UVUFNB4_M919TMBFNB4_TMB_FENNY_FIXED.zip.
6. Wait for it to run an MD5 check. The program will freeze and unfreeze when it's done.
7. Click start and let Odin flash the ROM.
8. When it says PASS, unplug the phone and long press the power button until the phone turns off and reboots on its own. Leave it alone for about 2 minutes and then power it off.
9. Reboot back into Download Mode and then flash the CF-Autoroot found here.
10. Flash that via the PDA slot in Odin, reboot, and you should now be rooted. You can then continue to do everything else such as install TWRP and flash Infamous 4.4.2.
brian117 said:
You will still be able to flash the custom ROM after you Odin flash the KitKat NB4 firmware. The steps are as followed:
1. Open Odin v3.07.
2. UNcheck the boxes that say auto reboot and f. reset time.
3. Power off your phone and enter Download Mode by holding down the Vol DOWN + Home + Power buttons at the same time. Hit Vol UP after the warning message comes up.
4. Connect your phone to your PC and wait for it to appear in the COM: box in Odin.
5. Click the PDA tab and select the "M919UVUFNB4_HOME.tar.md5" file that you extracted from http://www.cheatersedge.org/android/m919/M919UVUFNB4_M919TMBFNB4_TMB_FENNY_FIXED.zip.
6. Wait for it to run an MD5 check. The program will freeze and unfreeze when it's done.
7. Click start and let Odin flash the ROM.
8. When it says PASS, unplug the phone and long press the power button until the phone turns off and reboots on its own. Leave it alone for about 2 minutes and then power it off.
9. Reboot back into Download Mode and then flash the CF-Chain's Autoroot found here.
10. Flash that via the PDA slot in Odin, reboot, and you should now be rooted. You can then continue to do everything else such as install TWRP and flash Infamous 4.4.2.
Click to expand...
Click to collapse
Thanks for the step by step. I'm following it now. The NB4_HOME.tar.md5 is taking a long time to flash with ODIN. But I will follow it closely, if everything looks good I'll send out a donation, I appreciate your help.
nopotential said:
Thanks for the step by step. I'm following it now. The NB4_HOME.tar.md5 is taking a long time to flash with ODIN. But I will follow it closely, if everything looks good I'll send out a donation, I appreciate your help.
Click to expand...
Click to collapse
Like I said donations are not needed. It does take a while for it to flash through Odin so that's normal.
It was boot looping, went into optimizing apps to something about media database multiple times. I went into the stock recovery and cleared cache and factory reset. It's trying to boot now.
nopotential said:
It was boot looping, went into optimizing apps to something about media database multiple times. I went into the stock recovery and cleared cache and factory reset. It's trying to boot now.
Click to expand...
Click to collapse
My Wifi is unable to be turned on in this stock rom. I'm going to flash TWRP and then Infamous
nopotential said:
It was boot looping, went into optimizing apps to something about media database multiple times. I went into the stock recovery and cleared cache and factory reset. It's trying to boot now.
Click to expand...
Click to collapse
Yes that will happen. You just boot into recovery and factory reset and it will boot. Let me know if that works.
nopotential said:
My Wifi is unable to be turned on in this stock rom. I'm going to flash TWRP and then Infamous
Click to expand...
Click to collapse
If you continue to have WiFi problems, flash this via recovery.
brian117 said:
Yes that will happen. You just boot into recovery and factory reset and it will boot. Let me know if that works.
If you continue to have WiFi problems, flash this via recovery.
Click to expand...
Click to collapse
It looks like everything is looking good by following your list. Thank you.
nopotential said:
It looks like everything is looking good by following your list. Thank you.
Click to expand...
Click to collapse
Awesome! Good to hear man. Enjoy KitKat and the newest modem. The new modem has gave a significant reception boost for a lot of people. Hope it's the same for you. And please check your PM.
-Deleted-
After trying to update to kit kat my note 2 will not get past the "note 2" splash screen. What sucks even worse is that I can't get into recovery to install a new rom. I've been searching tons of threads and whatnot across XDA and other websites but nothing has worked.
What I've tried:
-Flashing TWRP, CWM, Philz recoveries. Odin says they succeeded but I still can't get to any of them.
-Flashing srock roms downloaded from multiple sources. When I try this I get an error in odin, usually fails right after sboot.bin
-Using other versions of Odin, different usb's, etc. Same stuff happens no matter what.
-Kies, but it won't connect and says device is unsupported.
-Android toolkit, but i couldn't really do much with it in this state
-I even tried re-partitioning with some t0lte pit file. This really didn't change anything.
-I found an "mk4_recovery.tar" file in a thread on here. That finished and succeeded, but I still can't get anywhere, However I did notice that this changed the "current binary" on my phone from "custom" to "official samsung binary." I'm not sure if that is important or not.
I feel like I am running out of options and my phone is hard-bricked. You guys are my last hope and I'm hoping there's something you guys can help me with!! If you have anything I can try please let me know!!!
SCAND1UM said:
After trying to update to kit kat my note 2 will not get past the "note 2" splash screen. What sucks even worse is that I can't get into recovery to install a new rom. I've been searching tons of threads and whatnot across XDA and other websites but nothing has worked.
What I've tried:
-Flashing TWRP, CWM, Philz recoveries. Odin says they succeeded but I still can't get to any of them.
-Flashing srock roms downloaded from multiple sources. When I try this I get an error in odin, usually fails right after sboot.bin
-Using other versions of Odin, different usb's, etc. Same stuff happens no matter what.
-Kies, but it won't connect and says device is unsupported.
-Android toolkit, but i couldn't really do much with it in this state
-I even tried re-partitioning with some t0lte pit file. This really didn't change anything.
-I found an "mk4_recovery.tar" file in a thread on here. That finished and succeeded, but I still can't get anywhere, However I did notice that this changed the "current binary" on my phone from "custom" to "official samsung binary." I'm not sure if that is important or not.
I feel like I am running out of options and my phone is hard-bricked. You guys are my last hope and I'm hoping there's something you guys can help me with!! If you have anything I can try please let me know!!!
Click to expand...
Click to collapse
This happened to me today too. I didn't like the OTA 4.4 so I was trying to get a custom rom again. Thanks to jlmancuso he made the best solution here:
http://forum.xda-developers.com/showpost.php?p=53035491&postcount=287&nocache=1&z=4473536636214703
Simply download the attached file. It is BRICKED heaven! (worked for me.) and have your recovery (twrp, philz, cwm) file. And have Odin.
1) Extract all files fix / recovery (if haven't already) / and odin (again if haven't already)
2) Open Odin in PDA put in the "fix" file. BEFORE continuing, UNCHECK Auto Reboot. (HAS TO BE UNCHECKED)
3) Connect phone to computer
4) Once the file has finished (Odin will say pass) disconnect the phone.
DO NOT TAKE THE BATTERY OUT
5) Put it back in Recovery Mode (home / volume up / power )
Give it a minute and it will load a custom recovery.
If you were stuck at a bootloop you probably don't have a rom on your phone (cleaned and empty).
If so try flashing this in Odin as well (https://drive.google.com/file/d/0B0CWousOd0ntTHl2RmxPbHJWODQ/edit?usp=sharing}
When the custom recovery loads you can flash what you want.
Odin will not let you downgrade from NE2 to anything below (bootloader). I suggest flash over Philz and flash that way.
http://forum.xda-developers.com/showthread.php?t=2768847
Has a NE2 rooted already. Flash this and save a backup. YOU WILL NEED IT.
Once in the custom recovery that comes up I suggest to flash the M2 Stock with Count Reset. (back to complete stock) then can do what you want from there.
**If the custom recovery does not show up**
Repeat the steps above (Odin / add fix to PDA / Uncheck Auto Reboot / Connect Phone / start flash)
Then again DO NOT PULL BATTERY ... (once it shows pass) disconnect and reboot back in download mode ( home / volume down / power )
Flash over your recovery ... (do not pull battery) and try the Recovery Mode ... my first time I thought it was still stuck in bootloop so give it a second.
michael85tx said:
Once in the custom recovery that comes up I suggest to flash the M2 Stock with Count Reset. (back to complete stock) then can do what you want from there.
Click to expand...
Click to collapse
What a nightmare!
I odined back to stock MK4, did the 4.4.2 OTA last night. Then did the CF Auto Root via odin, installed custom recovery. The phone is currently on pageplus network. I started messing around, did the GSM Mod, then tried the international and domestic sim unlock procedures. The result was not satisfying, so I tried flashing different modems. Eventually CDMA works, but GSM not. So I made a huge mistake by attempting to downgrade from NE2. And of course failed. Now the phone can't register on either CDMA or GSM.
So once I flash M2 Stock with Count Reset, I can play with the 4.4.2 OTA zip again to get a 100% 4.4.2 system?
michael85tx said:
This happened to me today too. I didn't like the OTA 4.4 so I was trying to get a custom rom again. Thanks to jlmancuso he made the best solution here:
http://forum.xda-developers.com/showpost.php?p=53035491&postcount=287&nocache=1&z=4473536636214703
Simply download the attached file. It is BRICKED heaven! (worked for me.) and have your recovery (twrp, philz, cwm) file. And have Odin.
1) Extract all files fix / recovery (if haven't already) / and odin (again if haven't already)
2) Open Odin in PDA put in the "fix" file. BEFORE continuing, UNCHECK Auto Reboot. (HAS TO BE UNCHECKED)
3) Connect phone to computer
4) Once the file has finished (Odin will say pass) disconnect the phone.
DO NOT TAKE THE BATTERY OUT
5) Put it back in Recovery Mode (home / volume up / power )
Give it a minute and it will load a custom recovery.
If you were stuck at a bootloop you probably don't have a rom on your phone (cleaned and empty).
If so try flashing this in Odin as well (https://drive.google.com/file/d/0B0CWousOd0ntTHl2RmxPbHJWODQ/edit?usp=sharing}
When the custom recovery loads you can flash what you want.
Odin will not let you downgrade from NE2 to anything below (bootloader). I suggest flash over Philz and flash that way.
http://forum.xda-developers.com/showthread.php?t=2768847
Has a NE2 rooted already. Flash this and save a backup. YOU WILL NEED IT.
Once in the custom recovery that comes up I suggest to flash the M2 Stock with Count Reset. (back to complete stock) then can do what you want from there.
**If the custom recovery does not show up**
Repeat the steps above (Odin / add fix to PDA / Uncheck Auto Reboot / Connect Phone / start flash)
Then again DO NOT PULL BATTERY ... (once it shows pass) disconnect and reboot back in download mode ( home / volume down / power )
Flash over your recovery ... (do not pull battery) and try the Recovery Mode ... my first time I thought it was still stuck in bootloop so give it a second.
Click to expand...
Click to collapse
You, sir, helped the hell out of me! I thought my phone was screwed and I've already tried everything. Thank you soo much!
Just curious, did you ever get kitkat to work? I've tried going to MC2 stock then upgrading a couple more times but it ends up doing the bootloop again every time :/ did you ever get that to update?
I'm so glad to have a working phone now though! Thanks!
SCAND1UM said:
You, sir, helped the hell out of me! I thought my phone was screwed and I've already tried everything. Thank you soo much!
Just curious, did you ever get kitkat to work? I've tried going to MC2 stock then upgrading a couple more times but it ends up doing the bootloop again every time :/ did you ever get that to update?
I'm so glad to have a working phone now though! Thanks!
Click to expand...
Click to collapse
I did the procedure everything went well but is there any way to update lastest firmware kitkat as i tried to and keep having to do the same procedure to unbrick it? thanks
brooklynman2020 said:
I did the procedure everything went well but is there any way to update lastest firmware kitkat as i tried to and keep having to do the same procedure to unbrick it? thanks
Click to expand...
Click to collapse
The best way to do the upgrade (since you know how to get your phone back if it happens again) is to just simply use Odin now to flash the 4.4.2 tar file thanks to "garwynn" for taking the time in making it.
http://forum.xda-developers.com/showthread.php?t=2780984
since most of my links don't work after I post lol I'm giving the download too. I tried uploading it but the file size is too big to post. So I hope this link works let me know and I'll re-upload it and post another link if the link stops working. 4.4.2 stock rom .tar
---------- Post added at 03:05 AM ---------- Previous post was at 02:55 AM ----------
lilila said:
What a nightmare!
I odined back to stock MK4, did the 4.4.2 OTA last night. Then did the CF Auto Root via odin, installed custom recovery. The phone is currently on pageplus network. I started messing around, did the GSM Mod, then tried the international and domestic sim unlock procedures. The result was not satisfying, so I tried flashing different modems. Eventually CDMA works, but GSM not. So I made a huge mistake by attempting to downgrade from NE2. And of course failed. Now the phone can't register on either CDMA or GSM.
So once I flash M2 Stock with Count Reset, I can play with the 4.4.2 OTA zip again to get a 100% 4.4.2 system?
Click to expand...
Click to collapse
sorry for the late reply but yes you can. I have gone back and forth trying to decide which 4.4.2 works best for service and style. lol right now I'm on 4.4.2 stock rooted (took FOREVER to get rooted I think it just finally clicked in I had given up). but there's already a .tar file for 4.4.2 you can just flash the .tar file and you have a OTA STOCK (unrooted) version of 4.4.2 for SPRINT only. It's the easiest way to get your phone back to working if it' soft bricked or just won't load recovery.
...NOTE... you can UPGRADE flash your bootloader (i.e. ... M2 .. MK4 ...N2) from Odin. You just CAN NOT downgrade firmware via Odin if you're going to go back to 4.1/4.2/4.3 versions. You will 99% of the time get "failed" at write to sboot .. for recovery I recommend Philz as it clears your cache and such when you flash roms and gapps and such for you.
---------- Post added at 03:10 AM ---------- Previous post was at 03:05 AM ----------
SCAND1UM said:
You, sir, helped the hell out of me! I thought my phone was screwed and I've already tried everything. Thank you soo much!
Just curious, did you ever get kitkat to work? I've tried going to MC2 stock then upgrading a couple more times but it ends up doing the bootloop again every time :/ did you ever get that to update?
I'm so glad to have a working phone now though! Thanks!
Click to expand...
Click to collapse
You're welcome lol when it happened to me I wanted to punch a wall or something because I couldn't make a call to help me and there was no way Sprint would have helped me. It took me 8 hours to find it that day lol I had almost started giving up hope
You may already know this, but you also want to read up and see what versions of odin people are having success with. As well as what custom recoverys (and versions) seem to be working.
I used Odin v3.09 with no problems. Heard that others had success with v3.07
Flashed and running Philz custom recovery v6.0.4.5
I flashed update-supersu-v1.94.zip (originally flashed cwm-supersu-v0.94.zip, which DID NOT work). Supersu is a little buggy. On both the note2 and s3, after install apk would fc. Went to play store and updated supersu, supersu will then work (even "partially" disables knox for you)
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
g_money said:
You may already know this, but you also want to read up and see what versions of odin people are having success with. As well as what custom recoverys (and versions) seem to be working.
I used Odin v3.09 with no problems. Heard that others had success with v3.07
Flashed and running Philz custom recovery v6.0.4.5
I flashed update-supersu-v1.94.zip (originally flashed cwm-supersu-v0.94.zip, which DID NOT work). Supersu is a little buggy. On both the note2 and s3, after install apk would fc. Went to play store and updated supersu, supersu will then work (even "partially" disables knox for you)
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2
Click to expand...
Click to collapse
Yeah that's true I use Odin 3.09 Philz Recovery (latest version if that doesn't work the 6.07.09 has had some good success) and SU v1.93 is the one I have.
Stuck with 4.4.2 OTA
michael85tx said:
This happened to me today too. I didn't like the OTA 4.4 so I was trying to get a custom rom again. Thanks to jlmancuso he made the best solution here:
http://forum.xda-developers.com/showpost.php?p=53035491&postcount=287&nocache=1&z=4473536636214703
Simply download the attached file. It is BRICKED heaven! (worked for me.) and have your recovery (twrp, philz, cwm) file. And have Odin.
1) Extract all files fix / recovery (if haven't already) / and odin (again if haven't already)
2) Open Odin in PDA put in the "fix" file. BEFORE continuing, UNCHECK Auto Reboot. (HAS TO BE UNCHECKED)
3) Connect phone to computer
4) Once the file has finished (Odin will say pass) disconnect the phone.
DO NOT TAKE THE BATTERY OUT
5) Put it back in Recovery Mode (home / volume up / power )
Give it a minute and it will load a custom recovery.
If you were stuck at a bootloop you probably don't have a rom on your phone (cleaned and empty).
If so try flashing this in Odin as well (https://drive.google.com/file/d/0B0CWousOd0ntTHl2RmxPbHJWODQ/edit?usp=sharing}
When the custom recovery loads you can flash what you want.
Odin will not let you downgrade from NE2 to anything below (bootloader). I suggest flash over Philz and flash that way.
http://forum.xda-developers.com/showthread.php?t=2768847
Has a NE2 rooted already. Flash this and save a backup. YOU WILL NEED IT.
Once in the custom recovery that comes up I suggest to flash the M2 Stock with Count Reset. (back to complete stock) then can do what you want from there.
**If the custom recovery does not show up**
Repeat the steps above (Odin / add fix to PDA / Uncheck Auto Reboot / Connect Phone / start flash)
Then again DO NOT PULL BATTERY ... (once it shows pass) disconnect and reboot back in download mode ( home / volume down / power )
Flash over your recovery ... (do not pull battery) and try the Recovery Mode ... my first time I thought it was still stuck in bootloop so give it a second.
Click to expand...
Click to collapse
Followed this procedure after accepting OTA and couldn't get chainfire autoroot to work. This worked flawlessly for me and I'm flashing again !!!!
lewisyiv said:
Followed this procedure after accepting OTA and couldn't get chainfire autoroot to work. This worked flawlessly for me and I'm flashing again !!!!
Click to expand...
Click to collapse
Where is the fix file for download? I cant flash the tar file, all time show fail in odin, I was try with firmware 4.4.2, 4.2, 4.1.2 and nothing my note 2 enter in download mode but not in recovery mode, alwais is in bootloop in logo... maybe I have brick?
vegitamaster66 said:
Where is the fix file for download? I cant flash the tar file, all time show fail in odin, I was try with firmware 4.4.2, 4.2, 4.1.2 and nothing my note 2 enter in download mode but not in recovery mode, alwais is in bootloop in logo... maybe I have brick?
Click to expand...
Click to collapse
Two post above you or in the quote above you has the link for fix. You need to follow the first link (xda thread link) and it will take you to my post that has the upload.
Sent from my SPH-L900 using XDA Premium 4 mobile app
Second post in this thread helped me immensely. Thank you!
I broke my note 2 that I had rooted and was running rwilco's mostly stock rom on.
Got another note 2 off craigslist and decided I should root it too for speed and for tethering. Tried the liquid smooth rom and it failed leaving me with no ROM.
Every ROM I tried failed until I found this thread and used Odin to flash "ALL_SPT_L900VPUCNE2_L900SPTCNE2_1561791_REV04_user_low_ship.tar.md5" that was linked.
So phone is now running 4.4.2 can I safely try again to load a custom ROM?
What do I need to do to make sure I don't have the same problem?
I'm not really savvy with this stuff but I can follow destructions
does any of the above steps wipe internal data?
Background:
I'm a post grad university student that takes a lot of annotated notes on powerpoint PDFs. My reason to root was because I wanted to be able to annotate my files and have them saved on a microSD since there isn't enough room on the device, with EZPDF reader then have that synced to my dropbox using dropsync.
My device is an Australian build number: KOT49H.P600XXUCNH3, Model: SM-P600, Android version: 4.4.2
What happened:
-I tried to root using Odin309, used the autorootp600mj4.tar.md5
-Appeared successful, superSU was in my app tray
-used Odin309 to flash recovery.tar.md5
-downloaded titanium backup and SDFix: Kitkat writable microSD apps
-tried to execute SDfix app --> didn't work, tried to access titanium backup --> no root access
-opened superSU --> "There is no SU binary installed, and SuperSU cannot install it. This is a problem! If you just upgraded to Android 4.3, you need to manually re-root - consult the relevant forums for your device!"
-I think that's weird --> try to do the whole re-root process again using Odin
-This time, there is no superSU app in the tray --> go to google play store and try to install superSU and google play has error and closes --> test download random game and it works fine, I'm led to believe that this only shuts down when trying to install the superSU app
-Try again once more to re-root using Odin --> no surprise, nothings changed
-Uninstall titanium backup and SDFix apps and just leaving it alone for now
Current state:
For the most part, everything seems normal, I can still annotate but just have to deal with the tedious manual way of saving onto the SD card so this isn't an emergency, and I can still take my notes.
Main questions:
1. Where exactly is my tablet in terms of root? Obviously it doesn't recognize that it is (so probably not rooted) but the regular Odin root method won't work.
2. I would still like to be able to achieve my original goal of rooting to be able to use apps to easily write onto my SD card and have it work with dropsync: what should I do?
3. Where can I find the proper stock ROM/firmware in case I need to undo everything?
thanks in advance
Stock firmware for SM-P600 (Australia)
CF-Auto-Root for SM-P600 4.4.2
Make sure you're using the CF-Auto-Root for 4.4.2, and not the older one for 4.3
Follow the instructions in the post to the letter, including using Odin 3.07 that comes with it, not 3.09
Might want to reflash stock firmware in Odin 3.09, then attempt to re-root.
Should work fine as long as you are using the correct file.
Just tagging to follow. I just put an almost identical message in the ChainFire instructions link on the Android development page! Exact same symptoms as you.
I wanted to share my experience as I just rooted my SM-P600 (US model - XAR) with the latest rom - P600UEUCOB1 (Feb 2015). I did however, use a different method - by flashing TWRP.
1. I downloaded the .tar file of TWRP, for the latest version - 2.8.5.1, from this link:
http://techerrata.com/browse/twrp2/lt03wifiue
2. I used ODIN ver 3.09
3. Power down the tablet; hold Vol Down and press power button until I see the instruction of pressing Vol Up to continue to download mode. Followed to click Vol Up.
4. Plug tablet to Windows computer running ODIN
5. Click AP or PDA, select the TWRP tar file; uncheck auto-reboot, uncheck F. Reset Clock (i.e., all boxes are unchecked).
6. Start to flash the file, wait until it is done.
7. **IMPORTANT STEP**
Manually power down by holding Power button. As soon as the tablet screen goes black, release Power button, then immediately press and hold both Power button and Vol Up button until you see Samsung logo on screen again. Then release Power button BUT keep holding Vol Up until you see the TWRP boot screen. Now you can let go of all buttons.
8. After TWRP finish loading, you select "Reboot", "System". It will detect that the tablet is not rooted, confirm that you want it to root, and swipe to confirm. It will then reboot.
9. Finally, it will boot into Touch wiz, and it will ask you to download SuperSU. Follow the prompt, I selected download by Play Store.
10. The very last two steps are:
Update SuperSU binary - I chose the regular update method (not TWRP method);
Disable Knox - First time doing it, the app will just pause when trying to disable. Just back to exit, and restart tablet. Run SuperSU again, and the 2nd time will work fine in disabling Knox.
When all of the above, rooting was successfully done.
Hope it helps.
blindmanpb said:
Stock firmware for SM-P600 (Australia)
CF-Auto-Root for SM-P600 4.4.2
Make sure you're using the CF-Auto-Root for 4.4.2, and not the older one for 4.3
Follow the instructions in the post to the letter, including using Odin 3.07 that comes with it, not 3.09
Might want to reflash stock firmware in Odin 3.09, then attempt to re-root.
Should work fine as long as you are using the correct file.
Click to expand...
Click to collapse
Perfect! Thanks for pointing me in the right direction. SuperSU works and titanium backup is a go!