Here's what I did with a new T-Mobile Samsung Galaxy S5:
- Started phone in download mode (started it with Volume Down, Home, and Power buttons) and connected it to computer.
- Started Odin3v185, saw yellow COM box.
- Clicked PDA button and selected philz_touch_6.26.2-klte.tar.md5 file.
- Clicked Start button, flashing went fine, phone reset and everything was cool, still with stock ROM. I was able to boot into Philz recovery to verify that flashing worked.
- As part of my goal of installing XtreStoLite ROM 2.2 (Lollipop), the following steps were to install the modem and bootloader for that ROM.
- Started phone in download mode and connected it to computer.
- Started Odin3.09, saw blue COM box.
- Clicked BL button, and selected G900T-LP-UVU1DOB1-BOOTLOADER.tar.md5.
- Clicked CP button, and selected G900T-LP-UVU1DOB1-MODEM.tar.md5.
- Clicked Start to flash. Phone reset, but it froze at the Samsung logo.
I gave it about a half hour just to make sure it wasn't just taking it's time with this first boot after the update, but it stayed at the Samsung logo. Only way to turn it off was to remove the battery. I'm still able to boot into Philz, so I figured a way to fix it might be to just go ahead and install the ROM. So I selected the "install from zip" option and installed XtreStoLite_ROM_v2.2_LP_XXU1BOD3.zip. Now the startup logo is a bit different, but it still stays frozen at the logo. I know from previous times installing this ROM that it does usually take awhile (maybe 5 minutes) on the first boot after installing, but I let it sit again for about 30 minutes with no luck.
The only thing I can see that I did differently this time, which I know realize was dumb, was skipping the step after flashing Philz where I boot into it and install UPDATE-SuperSU-v2.37.zip to root the device. I thought that I'd be able to install the bootloader, modem, and ROM and end up with a rooted OS, but I'm guessing that rooting is separate from those things, and they can't succeed until the phone has been rooted.
So... what can I do now? I'm trying to install the stock ROM (G900T_TMB_G900TUVU1CNK2_G900TTMB1CNK2_original.zip), but Philz gives me a "installation aborted" error before it even starts, with no other error messages. I also suspect I should install the original kitkat bootloader+modem, but I'm not sure where to find those (searching yields a lot of different results).
Any help would be greatly appreciated. Thanks!
The bootloop must be related to the bootloader/modem you've flashed. SU will allow root access once booted, but it won't prevent the system from booting if you skip it. Are you simply trying to root? FWIW, I'd recommend skipping Lollipop altogether, Marshmallow is night and day better than Lollipop. Flash the complete factory image of one of the Marshmallow releases, then flash your recovery and install SU. There are a couple of good, debloated Marshmallow roms available.
I was able to get out of the situation by flashing a stock ROM from here:
http://forum.xda-developers.com/tmo.../compilation-s5-g900t-stock-firmware-t3042400
I first flashed the stock modem and bootloader, though I'm not sure that was required because I think they're included in the ROM itself.
Used the latest 4.4.2 ROM and NK2 bootloader+modem, just because I'm pretty sure it was 4.4.2 that was on the phone when I got it.
Retried my procedure, this time rooting + disabling KNOX before flashing the Lollipop bootloader+modem from the ROM's install instructions, but I still ran into the same "freeze at boot" problem. I don't know what could be the issue, as I've done this exact procedure with two previous S5s. Not really looking to check out Marshmallow ROMs, just because I'm short on time these days, and after trying out a handful over the years, the XtreStoLite is by far the best for me.... really the perfect combo of stock Android with some of the improvements offered by TouchWiz, with all the tweaks to fix annoying "features" that I want fixed (for example, the removal of that damn "are you sure you want to increase the volume? It could damage your hearing" warning when you connect headphones and try to turn up the volume). Also, just stable and fast, compared to most/all the others I've tried.
Sounds to me as if you need stock Marshmallow with a custom recovery and Exposed. Mine is fast as hell, extremely frugal on battery, and Exposed has got rid of all the annoying TW "features", like the volume warning you mention (also, expanded notifications on lockscreen, battery full notification gone, circle battery, etc, etc). There are also alternatives to stock that are good, I tried one a couple of weeks ago that I think I'm probably going to go back to. Lollipop is horrible after using KitKat, Marshmallow brings back the KitKat experience but with dramatically improved battery life. You'll also get some Stagefright improvements.
Sorry for the delayed response, been too busy to deal with this for a couple weeks. How exactly do I get a stock Marshmallow with custom recovery and Exposed? Don't I already have the custom recovery covered with Philz? What Marshmallow ROM would you recommend? Thanks for the feedback!
Just download & Odin the latest complete image, GPI1, then Odin recovery (since Philz doesn't work, try TWRP, it works for me), then flash SU & Exposed. Takes about 15 minutes, although the download may take longer. Not sure if anyone has posted the link, but you can get it from sammobile, albeit slowly.
invisiblewave said:
Just download & Odin the latest complete image, GPI1, then Odin recovery (since Philz doesn't work, try TWRP, it works for me), then flash SU & Exposed. Takes about 15 minutes, although the download may take longer. Not sure if anyone has posted the link, but you can get it from sammobile, albeit slowly.
Click to expand...
Click to collapse
Did you deodex GPI1 before exposed?
invisiblewave said:
Just download & Odin the latest complete image, GPI1, then Odin recovery (since Philz doesn't work, try TWRP, it works for me), then flash SU & Exposed. Takes about 15 minutes, although the download may take longer. Not sure if anyone has posted the link, but you can get it from sammobile, albeit slowly.
Click to expand...
Click to collapse
Does this thread have the info I need for installing Xposed (I'm assuming "Exposed" and "Xposed" are the same thing)?
http://forum.xda-developers.com/showthread.php?t=3034811
Just install a .zip from TWRP, then install the .apk to manage installed modules?
I have "UPDATE-SuperSU-v2.37.zip". Is that sufficient for SU?
Well dammit, I've now spent multiple hours I didn't have trying to get *ANY* ROM other than the stock KitKat one to work. Was just about to give up after trying one last time with XtreStoLite, this time using KToonsez kernel instead of stock. Restarted and it was taking forever to boot, so I assumed it was frozen and was about to pull the battery and call it a night, when it actually made it into the OS! So perhaps there's something going on with the phone that won't let it boot with any stock kernel, other than 4.4.2. Bummer, because I was starting to get excited about trying Marshmallow.
It's because you have KitKat firmware. You just need to flash the entire MM package first.
What is the MM package, if it's not
G900T-(GPI1)-Bootloader.tar
G900T-(GPI1)-Modem-NonHLOS.tar
G900TUVS1GPI1_G900TTMB1GPI1_G900TUVS1GPI1_HOME.tar.md5
?
You don't need to flash the bootloader & modem separately. If you download the complete firmware, that's all you need to flash, it has all the necessary partitions in it. Just flash that, see if it works, then flash the recovery, etc.
I already tried G900TUVS1GPI1_G900TTMB1GPI1_G900TUVS1GPI1_HOME.tar.md5, both with and without the bootloader+modem packages.
I didn't see any mention of you having tried it in your earlier post. You should be able to flash just that package under AP (All Partitions, I assume), and it should install all the partitions it finds inside the tar. My guess is that Odin isn't completing correctly. What does it say in the log on the left? I had to use Odin 9, 10 wouldn't work on my setup for some reason, nor could I get it to work on XP, only on Windoze 8.
Related
I've had my brand new SCH-I545 since thanks giving now. I've been trying to root and get a custom ROM on the phone ever since then and have gotten closer and closer but haven't been able to quite get everything to co-operate.
I may catch scorn for posting such a generic question on a flagship phone but I've been up all night for 2 weeks now trying to get this to work following numerous tutorials but with android everything seems to get outdated when there are so many software variables at hand that are constantly changing like firmwares and build numbers. I've included all the info since it all seems to be vital and have tried to seperate tasks by paragraph so you can skip over what you feel may be arbritrary. So if I could get an up to date breakdown on how I could succeed in my endevour I'd appreciate it greatly.
Out the box I have a 4.4.2 and NK1 build number. I was finally able to get root access through towel root after flashing back to NC5. However even after flashing NC5 through odin, about phone still says my baseband and build number end I545VRUFNK1 but towelroot no longer gives me the "phone not supported" message and I'm able to succesfully atain root access, confirmed by root checker. Is that normal?
So I have root now but want a custom ROM. VZW locks the bootloaders on new phones so I believe that means I can't use a custom recovery like CWM. I've tried and tried but it doesn't work, neither does the CWM Rom manager app. I've managed to get a custom recovery through installing BusyBox and Safestrap. (I had to go through several apk's to get Safestrap to work. Usually I would be able to enter TWRP recovery through it but the recovery won't respond to any of my touches. The power button still works to turn the screen on and off so it is not frozen but it won't respond when I swipe to unlock it. Even now that I have it working, if the screen locks I'm unable to unlock it even if TWRP is performing a task in the backround and clearly not frozen.
One time I was able to more or less successfully flash LiquidSmooth (LS-KK-v3.2-2014-10-04-jflte.zip). This was the closest I ever got to my goal as the ROM succesfully booted up and I was able to browse the home screen and change all the settings and it was a moment of joy until I went to settings and switched wifi on it just wouldn't. It either just wouldn't switch or would switch right back and grey itself out I don't remember exactly. My phone had no service either for calls, text or 4G. So everything worked internally it just couldnt comunicate with any signals coming from outside the phone. Why would this be? If I manage to boot LiquidSmooth again is there something I could download to make the wifi/service work? (I could download through USB or Odin.)
After this I tried to flash CM but the phone wouldnt even start after installation and would just bootloop so I had to flash back to stock to make it work again. Then I tried LiquidSmooth several more times but now I get stuck at the bootscreen for LiquidSmooth where it has the logo and the backround flashing. I've let the animation loop for several minutes multiple times before doing a battery pull.
Basically for 2 weeks I've been flashing NC5->rooting->flashing NK1 back->installing safestrap->installing a rom->soft bricking->flashing back to stock ROM and starting again
Is it possible if I keep doing this proccess that it will just work one time? It may sound silly but I kind of believe just because I've had varrying degrees of success following the exact same procedure.
And when I install a ROM in TWRP I go Wipe->(swipe factory reset)->Install->(select LS.zip and wait for it to say its succesfully installed)->Swipe one more time to wipe cache->Reboot after this the phone either fails to start up or loops the LiquidSmooth animation. As I said, one time it started succesfully.
Let me know what any of this information leads you to believe and if you may have a sollution in mind. Huge thanks to anyone that read this and will try to help me. I've had this phone 2 weeks now and would like to start actually using it.
unorthodocks said:
I've had my brand new SCH-I545 since thanks giving now. I've been trying to root and get a custom ROM on the phone ever since then and have gotten closer and closer but haven't been able to quite get everything to co-operate.
I may catch scorn for posting such a generic question on a flagship phone but I've been up all night for 2 weeks now trying to get this to work following numerous tutorials but with android everything seems to get outdated when there are so many software variables at hand that are constantly changing like firmwares and build numbers. I've included all the info since it all seems to be vital and have tried to seperate tasks by paragraph so you can skip over what you feel may be arbritrary. So if I could get an up to date breakdown on how I could succeed in my endevour I'd appreciate it greatly.
Out the box I have a 4.4.2 and NK1 build number. I was finally able to get root access through towel root after flashing back to NC5. However even after flashing NC5 through odin, about phone still says my baseband and build number end I545VRUFNK1 but towelroot no longer gives me the "phone not supported" message and I'm able to succesfully atain root access, confirmed by root checker. Is that normal?
So I have root now but want a custom ROM. VZW locks the bootloaders on new phones so I believe that means I can't use a custom recovery like CWM. I've tried and tried but it doesn't work, neither does the CWM Rom manager app. I've managed to get a custom recovery through installing BusyBox and Safestrap. (I had to go through several apk's to get Safestrap to work. Usually I would be able to enter TWRP recovery through it but the recovery won't respond to any of my touches. The power button still works to turn the screen on and off so it is not frozen but it won't respond when I swipe to unlock it. Even now that I have it working, if the screen locks I'm unable to unlock it even if TWRP is performing a task in the backround and clearly not frozen.
One time I was able to more or less successfully flash LiquidSmooth (LS-KK-v3.2-2014-10-04-jflte.zip). This was the closest I ever got to my goal as the ROM succesfully booted up and I was able to browse the home screen and change all the settings and it was a moment of joy until I went to settings and switched wifi on it just wouldn't. It either just wouldn't switch or would switch right back and grey itself out I don't remember exactly. My phone had no service either for calls, text or 4G. So everything worked internally it just couldnt comunicate with any signals coming from outside the phone. Why would this be? If I manage to boot LiquidSmooth again is there something I could download to make the wifi/service work? (I could download through USB or Odin.)
After this I tried to flash CM but the phone wouldnt even start after installation and would just bootloop so I had to flash back to stock to make it work again. Then I tried LiquidSmooth several more times but now I get stuck at the bootscreen for LiquidSmooth where it has the logo and the backround flashing. I've let the animation loop for several minutes multiple times before doing a battery pull.
Basically for 2 weeks I've been flashing NC5->rooting->flashing NK1 back->installing safestrap->installing a rom->soft bricking->flashing back to stock ROM and starting again
Is it possible if I keep doing this proccess that it will just work one time? It may sound silly but I kind of believe just because I've had varrying degrees of success following the exact same procedure.
And when I install a ROM in TWRP I go Wipe->(swipe factory reset)->Install->(select LS.zip and wait for it to say its succesfully installed)->Swipe one more time to wipe cache->Reboot after this the phone either fails to start up or loops the LiquidSmooth animation. As I said, one time it started succesfully.
Let me know what any of this information leads you to believe and if you may have a sollution in mind. Huge thanks to anyone that read this and will try to help me. I've had this phone 2 weeks now and would like to start actually using it.
Click to expand...
Click to collapse
The issue is that safestrap is incompatible with the roms you are trying to use. It can be only used with Touchwiz based roms(i.e. using the stock kernel). Try flashing hyperdrive rom. Also, Im not familiar if NK1 can use towelroot and safestrap well. My recommendation would be to
1. clean wipe to nc5
2. towel root
3. install safestrap
4. flash ONLY roms that say they were safestrap compatible.
5. Flash any patches, modems, etc.
Weeks? How about spending a few hours reading up on what you can and can't do with your phone.
Raymondlikesroot said:
The issue is that safestrap is incompatible with the roms you are trying to use. It can be only used with Touchwiz based roms(i.e. using the stock kernel). Try flashing hyperdrive rom.
Click to expand...
Click to collapse
Ok, thanks, I was going to try to flash hyperdrive but the ROM I found was 1.2GB and I didn't have that much space on my SD. I'll borrow an empty one and try it again. Is it not odd that LS did a full boot if it's not compatible with safestrap? And are there any other Touchwiz roms? I don't like Touchwiz and am trying to get as far from it as I can but if I could just delete the bloatware (which I can still only disable after towel root), get SD access and get rid of the battery restrictions.
unorthodocks said:
Ok, thanks, I was going to try to flash hyperdrive but the ROM I found was 1.2GB and I didn't have that much space on my SD. I'll borrow an empty one and try it again. Is it not odd that LS did a full boot if it's not compatible with safestrap? And are there any other Touchwiz roms? I don't like Touchwiz and am trying to get as far from it as I can but if I could just delete the bloatware (which I can still only disable after towel root), get SD access and get rid of the battery restrictions.
Click to expand...
Click to collapse
The reason that LS did a full boot is because certain aosp roms can function with a touchwiz kernel. However, the result is always buggy. There is s4 verizon general thread talking about this.
There are many other tw roms. Just go to andriod devlopment! On the top of my head, I can think of eclipse, hyperdrive, echoe, and empty galaxy.
Ok, so I've rooted and put custom roms on numerous phones. I've been trying to put a custom recovery, twrp or cwm, whatever, on my wife's phone, but have got a wall. I know for sure, 100% that I am rooted. I tired to install twrp and cwm via their respective apps, ends up in either bootloop trying to boot into recovery (and FYI, the screen shows that a custom recovery is installed, just doesn't load into recovery and restarts). And tried both via Odin, but got the same result. Have never ran into this problem before with any of my phone's, all of the galaxy's and Galaxy Note's since the S2. Any help would be greatly appreciated. Thanks homies!
Just to add, yes I made sure double checked, triple checked that I was installing the correct recovery for the phone model. Also, she has done all the ota updates that sprint has pushed as of last week (2/9/15).
Psychotic-Cerebellum said:
Ok, so I've rooted and put custom roms on numerous phones. I've been trying to put a custom recovery, twrp or cwm, whatever, on my wife's phone, but have got a wall. I know for sure, 100% that I am rooted. I tired to install twrp and cwm via their respective apps, ends up in either bootloop trying to boot into recovery (and FYI, the screen shows that a custom recovery is installed, just doesn't load into recovery and restarts). And tried both via Odin, but got the same result. Have never ran into this problem before with any of my phone's, all of the galaxy's and Galaxy Note's since the S2. Any help would be greatly appreciated. Thanks homies!
Just to add, yes I made sure double checked, triple checked that I was installing the correct recovery for the phone model. Also, she has done all the ota updates that sprint has pushed as of last week (2/9/15).
Click to expand...
Click to collapse
OK, from your post it looks like you have done this before. To be sure lets go through the motions one more time.
Your device is updated to 4.4.4 NK4 the latest KitKat version. It's rooted you have supersu icon and run a root checker. First download again ( in case you got a bad download ) a copy of Philz CWM version 6.48.4 here is the link https://goo.im/devs/philz_touch/CWM_Advanced_Edition/hlte/ use "phil'z_touch_6.48.6-hlte.tar.md5" . I like to use odin version v1.85 it's little older but very stable, here is a link https://mega.co.nz/#!oA5xzTAL!LXoVWB...ZlOMSWdRGVX6Uo now flash the .tar file with odin. Make sure you let device boot up on it's own back to the OS, do not pull the cable and boot the device yourself. Then try and boot into recovery.
If it bootloops again, I would backup all your data to the PC desktop, and then do a factory reset get back to bone stock ( that means when your in download mode it says Samsung Official status not custom ) so many times I have seen folks with an unrooted device where the bootloader still says custom and you end up with a dirty flash or worse. It may take a couple factory resets to get back to stock, it doesn't always take the first time. When I flash a custom rom and then decide to go back to stock, I flash the rom two or three times to make sure I'm bone stock.
If the factory reset doesn't work you may have to flash a new stock NK4 OS. Then root again and install the recovery. Here is my thread with all the info you need http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440 , Enjoy !!!
Thanks for taking the time to give me a detailed response. Sounds like I'm gonna have to wait till Wednesday or Thursday when im off work and have some time to do this, but yeah, I was thinking maybe just a factory reset, but I'll use your links and try it one more time first. I'll let ya know. Thanks again
Do you have another link to the older Odin (1.85).the link says the file isn't there... Thanks again
Never got to test it out, but she didn't really want a custom rom anyway, just the WiFi hotspot, and I finally found a method that works, big shout out to idone for his awesome app. If anyone else is looking for WiFi hotspot without root that sees this, check out his tread in the apps and themes, for this phone. Worked like a charm. Thanks again jimzweb1. Much appreciate the reply!
Psychotic-Cerebellum said:
Never got to test it out, but she didn't really want a custom rom anyway, just the WiFi hotspot, and I finally found a method that works, big shout out to idone for his awesome app. If anyone else is looking for WiFi hotspot without root that sees this, check out his tread in the apps and themes, for this phone. Worked like a charm. Thanks again jimzweb1. Much appreciate the reply!
Click to expand...
Click to collapse
Awesome, Ya idone is the man when it comes to enabling the mobile hotspot be careful what you click with app. I will correct that link. Thanks
Psychotic-Cerebellum said:
Ok, so I've rooted and put custom roms on numerous phones. I've been trying to put a custom recovery, twrp or cwm, whatever, on my wife's phone, but have got a wall. I know for sure, 100% that I am rooted. I tired to install twrp and cwm via their respective apps, ends up in either bootloop trying to boot into recovery (and FYI, the screen shows that a custom recovery is installed, just doesn't load into recovery and restarts). And tried both via Odin, but got the same result. Have never ran into this problem before with any of my phone's, all of the galaxy's and Galaxy Note's since the S2. Any help would be greatly appreciated. Thanks homies!
Just to add, yes I made sure double checked, triple checked that I was installing the correct recovery for the phone model. Also, she has done all the ota updates that sprint has pushed as of last week (2/9/15).
Click to expand...
Click to collapse
That's the problem Knox security is getting harder flash engineering boot loader again then try rashr in app store to flash philz
Hi, Followed all the amazing walk through like normal. Not sure what 4.x.x.x I was on, never really check to be honest.
First time this phone has been rooted. (I rooted because I was having problems with the phone, last phone I rooted and was able to fix the problems).
1. Used the download file and instructions by qking...
2. Same with TWRP
3. It rebooted, somehow it screwed up MicroSD card, would no longer read it. Then it rebooted again..
4. Stuck on Sprint screen for last couple hours.
I tried to get back into TWRP and do a factory clean and reset, when it rebooted it, sat at the Sprint Screen for hour or so. Then I searched and a few other people just had to use odin and redo it again and worked fine.
So I did odin again relfashed the file and at reboot it is stuck on Yellow Sprint screen..
That is where im stuck at now is Sprint Screen, thanks in advance!
Swaintan said:
Hi, Followed all the amazing walk through like normal. Not sure what 4.x.x.x I was on, never really check to be honest.
First time this phone has been rooted. (I rooted because I was having problems with the phone, last phone I rooted and was able to fix the problems).
1. Used the download file and instructions by qking...
2. Same with TWRP
3. It rebooted, somehow it screwed up MicroSD card, would no longer read it. Then it rebooted again..
4. Stuck on Sprint screen for last couple hours.
I tried to get back into TWRP and do a factory clean and reset, when it rebooted it, sat at the Sprint Screen for hour or so. Then I searched and a few other people just had to use odin and redo it again and worked fine.
So I did odin again relfashed the file and at reboot it is stuck on Yellow Sprint screen..
That is where im stuck at now is Sprint Screen, thanks in advance!
Click to expand...
Click to collapse
OK first pull battery, now reinsert bat and hold the power, home, and volume down buttons at the same time, then press the volume up button to get into download mode. Don't bother trying to get back to TWRP your past that. While in download mode check the status of the device. Is it Official or custom? Let me know the status.
Now lets flash a fresh stock OS with Odin, to save me a lot of typing go here. http://forum.xda-developers.com/note-3-sprint/general/samsung-note-3-rom-flashin-basics-t2896440
Download the version of odin you want both work fine. Download the version of the KK OS you want to flash, I like NK4. You can follow the steps on my thread listed above to flash an OS with one EXCEPTION!!!
EVEN IF THE DEVICE BOOTS UP AFTER YOU FLASH THE OS THE FIRST TIME, ONCE YOU GET PAST THE SET UP FOR FIRST TIME USE WHICH ( STARTS ABOUT 3-5 MIN AFTER THE SAMSUNG LOGO SCREEN BY THE WAY BE PATIENT ) POWER DOWN THE DEVICE GET BACK INTO DOWNLOAD MODE AND ODIN FLASH THE OS AGAIN !!!
This should get you back to bone stock OS. Once it boots up and get passed first time use set up. Now your ready to root, the way I root is first grab a copy of SuperSU ( latest version is fine its on my thread ) with your PC copy and paste it on the SD card. Next power down completely and boot into download mode, Odin flash a custom recovery TWRP is a good one. The device should boot up after the recovery is flashed on its own, don't try boot up the device yourself to soon, give the recovery a chance to flash completely. Now completely power down the device, hold the power, home, and volume up buttons and boot into recovery. Then flash the SuperSu zip then reboot device you should be off and running . . . .
Here is the first part, im working on the rest now.
Current Binary: Custom
System Status: Custom
Swaintan said:
Here is the first part, im working on the rest now.
Current Binary: Custom
System Status: Custom
Click to expand...
Click to collapse
Ok cool, remember that everything has to fit. Meaning depending on what OS you run i.e. KitKat, Lollipop etc everything should updated to match.
Example : If you run KK NC5 OS then Philz CWM recovery 6.9.12 and later works. TWRP 2.8.3.0 or later works.
If you run Lollipop OC5 then Philz CWM recovery 6.48.4 works. ( link is broken I have a copy if you need it ) TWRP 2.8.6.0 or later works.
As for SuperSU you could go all the way back to v 1.94 and still root the binarys will update automatically. The latest (stable ) version is 2.46 from chainfire.
TY Ill keep you updated, file is taking a long time to download, still sitting at 1 hr to finish up download. Once its downloaded ill continue with the rest of the steps and post updates.
Not been very happy with sprint lately, latest update to my Wifes note 2 screwed her phone way up, only way to fix it was root it. So as soon as I saw mine doing the same thing I hurried to root it, but looks like it was to late. Hopefully this fixes it all, I really do appreciate it.
Swaintan said:
Hi, Followed all the amazing walk through like normal. Not sure what 4.x.x.x I was on, never really check to be honest.
First time this phone has been rooted. (I rooted because I was having problems with the phone, last phone I rooted and was able to fix the problems).
1. Used the download file and instructions by qking...
2. Same with TWRP
3. It rebooted, somehow it screwed up MicroSD card, would no longer read it. Then it rebooted again..
4. Stuck on Sprint screen for last couple hours.
I tried to get back into TWRP and do a factory clean and reset, when it rebooted it, sat at the Sprint Screen for hour or so. Then I searched and a few other people just had to use odin and redo it again and worked fine.
So I did odin again relfashed the file and at reboot it is stuck on Yellow Sprint screen..
That is where im stuck at now is Sprint Screen, thanks in advance!
Click to expand...
Click to collapse
Forgot to say why you flash twice, when the device is corrupted or bootloops. 9 times out of 10 its because something was left behind from the previous OS or something didn't flash in from the new OS. Flashing twice I found through ( trial and error pulling my hair out ) solves this problem.
When I get done with a flashaholic binge and need to get back to a daily user, I always flash back to Stock OS twice, install recovery, and root. Then install a custom OS if want run one this way you always start clean. This way if something doesn't work or stops working you right where to start looking for the problem.
---------- Post added at 07:03 AM ---------- Previous post was at 06:55 AM ----------
Swaintan said:
TY Ill keep you updated, file is taking a long time to download, still sitting at 1 hr to finish up download. Once its downloaded ill continue with the rest of the steps and post updates.
Not been very happy with sprint lately, latest update to my Wifes note 2 screwed her phone way up, only way to fix it was root it. So as soon as I saw mine doing the same thing I hurried to root it, but looks like it was to late. Hopefully this fixes it all, I really do appreciate it.
Click to expand...
Click to collapse
Ya I agree rooting stops the updates. Usually I read up on the update first to see what problems it may be causing. Then decide to unroot and take it, I still run my 4.4.4 NK4 deoexed no knox debloated OS just not a fan of Lollipop to many problems with it, besides there's no themes for it.
You are awesome! Followed your directions and links inside your siggy. So this is where I sit;
I installed (from your siggy)
-SPRINT KK 4.4.4 N900PVPUDNK4
Stock rom : DEODEXED, NO KNOX, and DEBLOATED ( #2 )
Busybox / Zipaligned
Rooted / Superuser
No Knox ( Disabled / Removed )
Volume Mod / 300+ Fonts ( Thanks DevilDog512 )
Custom Kernel ****
-SU 2.46 (it auto updated when I installed)
-TWRP Manager 8.0.1.8
-Recovery TWRP 2.8.7.0
Now I have to start redoing apps etc.. THANK YOU SO MUCH!!!
Edit: Add: Now should be safe to install Wicked Green Theme and get all family n friends to send contact info... that part will be harder then what you had me do, TY again!
Swaintan said:
You are awesome! Followed your directions and links inside your siggy. So this is where I sit;
I installed (from your siggy)
-SPRINT KK 4.4.4 N900PVPUDNK4
Stock rom : DEODEXED, NO KNOX, and DEBLOATED ( #2 )
Busybox / Zipaligned
Rooted / Superuser
No Knox ( Disabled / Removed )
Volume Mod / 300+ Fonts ( Thanks DevilDog512 )
Custom Kernel ****
-SU 2.46 (it auto updated when I installed)
-TWRP Manager 8.0.1.8
-Recovery TWRP 2.8.7.0
Now I have to start redoing apps etc.. THANK YOU SO MUCH!!!
Edit: Add: Now should be safe to install Wicked Green Theme and get all family n friends to send contact info... that part will be harder then what you had me do, TY again!
Click to expand...
Click to collapse
Cool, what stock version KK OS did you flash twice before installed my deodexed 4.4.4 NK4 ?
Not sure, i know i followed each one, so it took me to a site where I had to download it specifically for my phone. My dl history says file name was N900PVPUDNK4_SPR it was the bone stock md5, did that one twice.
Swaintan said:
Not sure, i know i followed each one, so it took me to a site where I had to download it specifically for my phone. My dl history says file name was N900PVPUDNK4_SPR it was the bone stock md5, did that one twice.
Click to expand...
Click to collapse
Cool, that will work fine.
tl;dr - Can't seem to find my way out of a software brick. Have sideloaded the stock OS from 1+ but still forever getting the spinning dots or fastboot screen, depending on which mode i boot into.
Hi all. Signed up to make this thread, but i've been lurking for years.
I have a OnePlus X that is about the least modded smartphone i've ever owned. I've never been pleased enough with a retail product that i didn't feel compelled to strip out the bloat and start over, until this phone. Other than stock, i've just got a gallery app, some apps for manipulating text files or compiling code, couple games, and social media apps.
Anyway, a few days ago i got a notification about a software update. Downloaded. Installed. Updated. No problem.
Maybe yesterday or the day before, it showed up again. This morning i downloaded, installed, and suddenly i have apps closing. It's been over 12 hours so i'm hazy on how it all started, but i was getting something like "package installer" errors when attempting to open some apps. Same deal when i went to adjust permissions of those affected apps. Every time i unfocused a box that had pulled up swype, i would get an error message saying swype crashed or closed or something.
So i started uninstalling third party apps (i don't keep many, and most i've had for years so i think they're probably trustworthy). Same deal. Started uninstalling updates to google apps. Same deal. Went to uninstall and reinstall some non stock apps that i'd kept previously. Nothing.
I went to cook breakfast while an app was reinstalling, and i came back to a red dot on my screen with two white dots chasing each other around it. From what i'm reading that's a sign of a bootloop or software brick. I've taken all steps i could find, including wiping cache and sideloading a fresh stock OS, but to no avail.
Is it that i've ruined my google apps somehow and need to restore them? How would i even go about figuring out what the problem is? Any advice or guidance is appreciated
Hi,
As your device is in bootloop state, try flashing the stock rom. Make sure you wipe data and cache. As far as after update problems, i faced it few times. After updating many app crashed and phone hangs. So i prefer clean flash over dirty flashing, to make sure everything is hazel free. For the time being i upgraded from 3.1.2 to 3.1.3 without wiping data or cache and facing no problem( of course since it was an OTA). But sometimes situation comes when after update phone act weird, so tbe option which i prefer then is clean flashing the stock rom. Hope this helps.
"A09" said:
Hi,
As your device is in bootloop state, try flashing the stock rom. Make sure you wipe data and cache. As far as after update problems, i faced it few times. After updating many app crashed and phone hangs. So i prefer clean flash over dirty flashing, to make sure everything is hazel free. For the time being i upgraded from 3.1.2 to 3.1.3 without wiping data or cache and facing no problem( of course since it was an OTA). But sometimes situation comes when after update phone act weird, so tbe option which i prefer then is clean flashing the stock rom. Hope this helps.
Click to expand...
Click to collapse
I have wiped cache, deleted data, tried a factory reset in the stock bootloader, and i have used ADB to sideload a full stock rom (not upgrade package) that i downloaded from OnePlus.
Flash old stock recovery then 2.2.3. From there you can flash any MM stock firmware.
Exodusche said:
Flash old stock recovery then 2.2.3. From there you can flash any MM stock firmware.
Click to expand...
Click to collapse
Pardon me for being nooby, but how do i do this? Do i just sideload in ADB like i did the ROM? Most instructions i'm finding assume access to the OS either normally or through fastboot. I'm just stuck in the default recovery.
Thanks for the tip, though. Looking for a copy of the old stock recovery now. Did OnePlus alter their stock recovery recently? In some threads i've seen people say that a recent update made them unable to load a non-stock ROM. Is that the new recovery blocking access to non-1+ operating systems?
jtg1984 said:
Pardon me for being nooby, but how do i do this? Do i just sideload in ADB like i did the ROM? Most instructions i'm finding assume access to the OS either normally or through fastboot. I'm just stuck in the default recovery.
Thanks for the tip, though. Looking for a copy of the old stock recovery now. Did OnePlus alter their stock recovery recently? In some threads i've seen people say that a recent update made them unable to load a non-stock ROM. Is that the new recovery blocking access to non-1+ operating systems?
Click to expand...
Click to collapse
Fastboot flash easiest way. Make sure it's the old recovery from 2.2.2. Not the new mm stock recovery.
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
jtg1984 said:
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
Click to expand...
Click to collapse
I m not a dev, i m a newbie like you. i hv done a lot of experiments with my oneplus-x, as for u the first update u got few days back should be oos 3.1.2 and the one u got 2 days before should be 3.1.3. When u upgrade from lollipop to marshmellow, even your stock recovery got upgraded to latest version, which is something different from old lollipop recovery.
You said you have access to recovery mode. thts pretty much gud, what u can do is that wipe data and cache through stock recovery and do a clean install of oos 3.1.3. I ll be providing all the necessary links down below. If you need assistance with fastboot cmds and anything feel free to ask.
Thanks to original link provider @Sachin7843
Useful Links: -
1. Stock Lollipop Recovery - https://s3.amazonaws.com/oxygenos.oneplus.net/OPX_recovery.img
2. Official TWRP Recovery - https://dl.twrp.me/onyx/
3. Blu Spark Recovery - http://forum.xda-developers.com/devdb/project/dl/?id=20236
4. SuperSU for OOS 3.x.x - https://drive.google.com/file/d/0B4K5cvm1zdldcmZpc3RuVnRjUUE/view
5. Unbrick Guide - http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
6. Official Oxygen OS 3.1.3 link - https://s3.amazonaws.com/oxygenos.o...OTA_018_all_201609291837_741146bcf28e4587.zip
7. SD Card Writable fix in MM - http://forum.xda-developers.com/android/software/fix-extsd-fix-v1-0b-2016-01-18-t3296266
8. For Stock MM Recovery - http://forum.xda-developers.com/oneplus-x/general/oxygenos-3-1-0-marshmallow-community-t3445043
Sorry for my bad english
jtg1984 said:
Yes, but how do i install the old stock recovery? I dug around on the forums and found the file, but the phone rejects it when sideloading and doesn't show the .img in the filesystem when inserted on a SD card.
Have to send it off to 1+ maybe? Literally all i can access right now is the (new) stock recovery. I never modded, rooted, etc before the software update sent me into the chasing dots
Click to expand...
Click to collapse
Don't sideload it, use fastboot to flash it. "Fastboot flash recovery name.img" - without he quotes and the image name.
Sorry for vanishing. Had a busy week.
Not sure what happened the first time i tried to put the 2.2.3 image on the SD card, because the file didn't show up in my recovery, but i tried again later (after giving up on flashing the old recovery, since i couldn't figure out how to do that in recovery) and managed to do a clean install of the older OOS version.
That did the trick, and after booting up, my phone proceeded to update again - this time without any crashes or errors with my apps afterward. The phone still does the red dot with the white dots chasing around it when it boots up, which must be the new boot screen. It also seems to stay on that screen for much longer than it stayed on the old morphing shape boot screen, but it still boots up reliably now after 30-60 seconds rather than freezing in boot forever.
I've since enabled dev mode on my phone. Is that going to be enough to enable ADB commands from recovery? I kind of like that i've kept my phone stock, so i'll leave it that way if i can, but it would have been much easier to fix this problem if i'd had access to most of my debug commands. As it was, without dev mode and in the standard recovery, it seemed that sideload was the only command i was able to use, and only when the phone was requesting a sideload over usb
I've been using CM13 on my phone for a long while, but it was heavily bugged (my camera kept crashing, I've kept losing cell reception, couldn't receive calls etc), so I finally decided to try another ROM. I've heard good things about ResurrectionRemix ROMs, so I've decided to give it a try. I did factory reset and wiped cache (using CWM 6. something) and flashed RR 7.1 along with the appropriate gapps and rebooted the phone. It's worth noting that I've put the ROM and Gapps zip files on USB stick and connected it to the phone via micro USB cable. It all went smoothly, and the phone booted right up. However, once I got into the startup setting and choosing the language suddenly it just rebooted all on its own. Same thing happened 2 more times, and I got stuck in a bootloop after that.
So I figured I should flash another ROM, and I wanted to give RR 6.0 a try. I've downloaded it and saved it to my USB stick, however, when I tried to flash any zip files from my stick, it just kept randomly unmounting, disrupting the process, giving me "USBdisc0 idle-unmounted" message. Since I don't have an SD card, only thing I could do was push files to my phone, and I've managed to do so via Quick ADB Pusher. This time, flashing went without a hitch, however, I've tried cleaning my phone completely (formatting all the data and system files), and I think I messed it up a bit when I did that, since I didn't flash SuperSU along with ROP and gapps. Again, I got stuck in a bootloop without any signs of the ROM working.
So I decided to flash CM13 again. At least I was sure it was working on my phone, and I figured it was better to have a crappy phone than no phone at all. So I pushed the CM13 file onto the phone and flashed it, but still got stuck in bootloop. I finally remembered about SuperSU and tried to flash it too, but now my phone kept restarting in the middle of the flashing process. I've tried doing the factory reset and cache wipe, but I can't flash any files now without it restarting only few seconds into the process.
I have no idea what's going on, but seems that my phone is doing worse and worse as time moves on. At least I can still boot into recovery and download mode, so (hopefully) something can still be done. As it's probably painfully obvious, I'm not too knowledgeable about this stuff, I'm just following instructions people smarter than me put out, but seems I've messed it up good this time. Am I beyond help?
Try to download newest firmware from sanmobile.com and flash it with odin. Then root it make backup flash recovery and flash rom that you choose with recovery. There are lots of tutorials here on xda and on youtube. Just remember that flashing stock firmware with odin will delete all of your data so try to back them up somehow (i think that if you boot phone in recovery (twrp) the pc will see it like a pendrive)
Sirius8 said:
...
As it's probably painfully obvious, I'm not too knowledgeable about this stuff, I'm just following instructions people smarter than me put out, but seems I've messed it up good this time. Am I beyond help?
Click to expand...
Click to collapse
TBH you made the mistake many beginners make... Going ahead too fast with insufficient knowledge. But never too late to learn that lesson
Since you are getting more and more confused and your phone seems acting strange I recommend starting from scratch an be analytic about it. This will take just a few minutes more but you can be sure where a problem comes from.
First of all: Take 30 minutes to get acquainted with the basics and read through the first thread in my signature (just do it...)
If you can still get in download mode, get your latest stock rom e.g. from sammobile.com and flash it via ODIN. Run stock for a few minutes to see if everything works correctly (test camera, outgoing/incoming calls, mobile data, wifi, gps etc.). If something does not work STOP HERE and report back.
If all is fine go back to ODIN and install latest TWRP (cwm is seriously outdated, can cause lots of errors). Then boot into TWRP and flash whatever custom rom you like. If you install e.g. LOS 14.1 or RR 7.1.1 make sure you install gapps direcly after you flash the rom (do not reboot in between).
Any questions pop up: Shoot. I'm happy to help.
---------- Post added at 04:49 PM ---------- Previous post was at 04:42 PM ----------
McXred said:
Try to download newest firmware from sanmobile.com and flash it with odin. Then root it make backup flash recovery and flash rom that you choose with recovery. There are lots of tutorials here on xda and on youtube. Just remember that flashing stock firmware with odin will delete all of your data so try to back them up somehow (i think that if you boot phone in recovery (twrp) the pc will see it like a pendrive)
Click to expand...
Click to collapse
Since he already wiped system and data there is no point in a backup of those partitions. Only thing worth saving would be the efs partition.
And you don't need to root stock rom to go further...
If you are unrooted you have to REMOVE the "auto-reboot" checkmark in odin options and then - after the flash of twrp - reboot to recovery (TWRP) manually via holding Power+Home+VolUp for a few seconds.
If you do not uncheck that "auto-reboot" box, an thus allow the unrooted system (stock samsung system) to boot, it will overwrite the new twrp recovery you flashed 2 seconds before...
This is the point where I believe many confusion comes from. If you root first, any recovery you flash will not be overwritten. That is - I think - why many tutorials/tips say you must root stock first before installing a custom rom, which is simply not true.
But you are right that it would help to flash TWRP fist as outlined above, boot into it and make a backup to a microSD card... but of the efs partition (!) as the very first step. Then keep that backup safe and go from there with stock rom, testing for any problems.
So to reiterate the steps I would go:
1) Flash TWRP via odin and boot directly into it
2) Backup efs partition to a microSD card
3) Flash stock rom via ODIN and test
4) Go from there / report baback
Thank you so much for the replies guys, I'm glad there's still hope for my trusty SIII.
Are there any alternatives for sammobile.com though, since it requires premium account for the firmware I need. I've found another mirror on the site mrcrab.net/stockrom/2444.html (mirror 1 leads to sammobile.com, while mirror 2 leads directly to rapidgator), but can I trust it not to mess my phone up further?
Try updato.com for the firmware.
Hawaiihemd said:
If you can still get in download mode, get your latest stock rom e.g. from sammobile.com and flash it via ODIN. Run stock for a few minutes to see if everything works correctly (test camera, outgoing/incoming calls, mobile data, wifi, gps etc.). If something does not work STOP HERE and report back.
Click to expand...
Click to collapse
I've manage to flash stock ROM via Odin, however, as soon as the phone booted up it gave me the "low battery" message, even though I think there was plenty of battery left. But I figured the flashing process must have drained it. As I've tried to tap the OK button, the screen just froze and remained frozen for over 5 minutes. I took battery out and reinserted it, since nothing else worked, and got stuck in bootloop again, just as before flashing stock firmware.
Sirius8 said:
I've manage to flash stock ROM via Odin, however, as soon as the phone booted up it gave me the "low battery" message, even though I think there was plenty of battery left. But I figured the flashing process must have drained it. As I've tried to tap the OK button, the screen just froze and remained frozen for over 5 minutes. I took battery out and reinserted it, since nothing else worked, and got stuck in bootloop again, just as before flashing stock firmware.
Click to expand...
Click to collapse
Try to charge phone without turning it on, when it says its fully charged try to flash it again.
McXred said:
Try to charge phone without turning it on, when it says its fully charged try to flash it again.
Click to expand...
Click to collapse
Good idea. I would also keep it on the charger while booting.
This could be a symptom of a defective battery. So these steps might help.
Looks like you were right guys. I've recharged the battery and tried to flash the stock firmware again, but for some odd reason (it seems like I can't do the same thing twice with this phone ) Odin was giving me grief and couldn't establish proper connection with my phone, even though it recognized it at the beginning of the process. I've tried changing cables and ports, but with no avail.
After I gave that up, I tried booting the phone up anyway, but keeping it plugged in the charger this time. It booted right up, but I expected it to crash and reboot at any moment. So I sped up through the settings a and login processes, but it still worked like a charm. I've checked the camera and everything worked perfectly. So I kept it on charger for a couple of hours, to check if I would have any random crashes, but nothing happened. After I was sure it was stable, I unplugged the charger, and within the second I did that the phone crashed and got stuck in the bootloop again.
I've plugged the charger back in and it booted up just fine. The battery level was 89%, and I left it on charger the whole night (12+ hours). It had 90% when I woke up, it's back at 89% right now.
So, everything points to a faulty battery, but it seems strange to me this happened just as I was flashing another ROM, even though I never had any problems with it before. And even though it wouldn't let me boot, I could use recovery and download mode for as long as I liked, and once I did boot with the charger plugged in, the battery wasn't drained but it was around 90%.
Hawaiihemd said:
TBH you made the mistake many beginners make... Going ahead too fast with insufficient knowledge. But never too late to learn that lesson
Since you are getting more and more confused and your phone seems acting strange I recommend starting from scratch an be analytic about it. This will take just a few minutes more but you can be sure where a problem comes from.
First of all: Take 30 minutes to get acquainted with the basics and read through the first thread in my signature (just do it...)
If you can still get in download mode, get your latest stock rom e.g. from sammobile.com and flash it via ODIN. Run stock for a few minutes to see if everything works correctly (test camera, outgoing/incoming calls, mobile data, wifi, gps etc.). If something does not work STOP HERE and report back.
If all is fine go back to ODIN and install latest TWRP (cwm is seriously outdated, can cause lots of errors). Then boot into TWRP and flash whatever custom rom you like. If you install e.g. LOS 14.1 or RR 7.1.1 make sure you install gapps direcly after you flash the rom (do not reboot in between).
Any questions pop up: Shoot. I'm happy to help.
---------- Post added at 04:49 PM ---------- Previous post was at 04:42 PM ----------
Since he already wiped system and data there is no point in a backup of those partitions. Only thing worth saving would be the efs partition.
And you don't need to root stock rom to go further...
If you are unrooted you have to REMOVE the "auto-reboot" checkmark in odin options and then - after the flash of twrp - reboot to recovery (TWRP) manually via holding Power+Home+VolUp for a few seconds.
If you do not uncheck that "auto-reboot" box, an thus allow the unrooted system (stock samsung system) to boot, it will overwrite the new twrp recovery you flashed 2 seconds before...
This is the point where I believe many confusion comes from. If you root first, any recovery you flash will not be overwritten. That is - I think - why many tutorials/tips say you must root stock first before installing a custom rom, which is simply not true.
But you are right that it would help to flash TWRP fist as outlined above, boot into it and make a backup to a microSD card... but of the efs partition (!) as the very first step. Then keep that backup safe and go from there with stock rom, testing for any problems.
So to reiterate the steps I would go:
1) Flash TWRP via odin and boot directly into it
2) Backup efs partition to a microSD card
3) Flash stock rom via ODIN and test
4) Go from there / report baback
Click to expand...
Click to collapse
Still on charger, still 90 percent.