I used factory reset and now my phone is stuck at the tmobile logo. I was rooted before but I removed SuperSU before doing the factory reset. I also tried wiping out the data at recovery mode but I'm still having the same problem. Is there anyone that can help me fix my Note 2?
kevzz01 said:
I used factory reset and now my phone is stuck at the tmobile logo. I was rooted before but I removed SuperSU before doing the factory reset. I also tried wiping out the data at recovery mode but I'm still having the same problem. Is there anyone that can help me fix my Note 2?
Click to expand...
Click to collapse
I hope you didn't wipe system my mistake
Wiping /system is a trivial problem to solve, just flash again and voilà.
What are you trying to accomplish exactly? If you want back to stock, flash the appropriate ROM with Odin, boot to stock recovery, factory reset and call it a day. Unless you've messed up your NV items or done something incorrect with the bootloader, that's pretty much all there is to it.
I wiped out the cache partition at recovery mode and now my phone is working just fine. The reason I factory reset my phone because I want to try if the system will let me update OTA after a reset. Unfortunately it won't let me update still because my phone was rooted. Is there a way to bypass this so I'd be able to update my phone?
Ah! Flashing back to a non-rooted ROM would allow the OTA mechanisms to work normally.
There's inherently a risk for a ROM update to patch something that's been modified in ways it does not expect, such as root on a stock ROM.
In the case of Samsung devices, you could always Odin flash back to stock, or a pre-rooted stock image.
Darkshado said:
Ah! Flashing back to a non-rooted ROM would allow the OTA mechanisms to work normally.
There's inherently a risk for a ROM update to patch something that's been modified in ways it does not expect, such as root on a stock ROM.
In the case of Samsung devices, you could always Odin flash back to stock, or a pre-rooted stock image.
Click to expand...
Click to collapse
Well I've always been on stock. I just rooted my phone before for some apps and that's it. I never use any custom rom. Im still at stock but wont let me update still
Consider yourself as "custom" the moment you change anything on your /system partition, that includes root.
Samsung ROMs have this check that's displayed somewhere in settings, where your ROM will say if it thinks it's been modified. If so, OTA updates will be disabled.
Factory reset alone won't completely unroot you. You must unroot, then factory reset.
At this point, since you just want a stock rooted ROM and have already factory reset, you could flash the latest pre-rooted ROM with Odin. Will probably be simpler than prodding the phone into getting the OTA.
Related
Hey guys hopefully you can help me. I was rooted for like 3 or 4 months now and have had not many problems or not anything I couldn't fix my self. My phone gets stuck on the Samsung Galaxy s4 screen anytime I reboot. I have tried different roms, different kernels, I even odin back to stock. I was using TWRP 6.0 then reverted back to TWRP 5.2 to see if that was causing the problem. Still have problems. I am going to re download the stock tar to see if it was a bad download but Odin checks the md5 and says it was good. Odin says passed every time also. Odin version is 3.07.
I get a error before and when trying to wipe dalvic cashe. I can wipe reg cash no problem. I think my phone is not mounting the internal storage when it reboots. I could be way off but need help asap. If I format super wipe with twrp then restart twrp and then factory reset I can install or restore a rom some times but still cant restart the phone. Any hope would be greatly appreciated.
EDIT
I wanted to edit my previous commet. LiquidSmooth seems to be running fine. So TW roms and GE roms **** up on my phone when I restart. so is it the internal systems when I have TW roms. I think it has something to do with partictions messing around maybe.
I like TW roms and want to continue to use them... Thank you
Get into recovery and do a factory reset, it is a must after you odin back to stock. Make sure you are also using a tmo kernel.
Thanks you
I got this problem a few days ago and found some topic including this one. You should check it out.
Well, what worked for me was Odin to stock firmware, root again, install recovery then custom rom. Now it's working fine. Try to downloading it again to see if it works. I downloaded mine from here, rooted and recovery it using this one.
TheAxman said:
Get into recovery and do a factory reset, it is a must after you odin back to stock. Make sure you are also using a tmo kernel.
Thanks you
Click to expand...
Click to collapse
+1 to what he said. I bet if you go into the stock recovery after odin flashing it will say something like cannot mount /data partition. Factory reset there, and it should fix that and make it mountable. (Its important to use the stock recovery factory reset after the odin, don't flash a custom recovery right after flashing)
This was incredibly helpful. I had the same issue. Thank you.
This is also applicable to the Verizon Wireless model.
Hello guys. I got my Note 8 at the holidays, I used OTA to get the 4.2.2 update, and I used autoroot, and just checked my recovery and I have Philz touch 5 installed.
When I check for OTA updates, I find the message your device has been modified, no updates available.
I am running stock 4.2.2. Do I need to unroot and return to stock recovery for OTA updates? I did not remove any apps or freeze anything. The only difference is recovery and being rooted. This question is in anticipation of the release of 4.4 kitkat, slated to be pushed to our device- but I'm not holding my breath for when that will be.
Thanks for your input!
sashusmom said:
Hello guys. I got my Note 8 at the holidays, I used OTA to get the 4.2.2 update, and I used autoroot, and just checked my recovery and I have Philz touch 5 installed.
When I check for OTA updates, I find the message your device has been modified, no updates available.
I am running stock 4.2.2. Do I need to unroot and return to stock recovery for OTA updates? I did not remove any apps or freeze anything. The only difference is recovery and being rooted. This question is in anticipation of the release of 4.4 kitkat, slated to be pushed to our device- but I'm not holding my breath for when that will be.
Thanks for your input!
Click to expand...
Click to collapse
Hi, I had rooted my 4.2.2 and installed a bunch of root apps... At this time, my Kies says there are no updates available. You will have to wait for 4.4.3 to come out for any update feature to work.
For myself I will do a factory system reset to bring my tablets update apps out of freeze and clear out any cache and the apps that were installed. Once the tablet is booted, I use Kies to push the new firmware once it is released.
Care should be used in restoring apps... many are not 4.4.3 compatible like 4.2.2. So some issues will arise with using customizations. I may hold off another year before installing 4.4.3... I don't like being a tester, been doing that for 30 years now, and like the stability of 4.2.2.
gooberdude said:
Hi, I had rooted my 4.2.2 and installed a bunch of root apps... At this time, my Kies says there are no updates available. You will have to wait for 4.4.3 to come out for any update feature to work.
For myself I will do a factory system reset to bring my tablets update apps out of freeze and clear out any cache and the apps that were installed. Once the tablet is booted, I use Kies to push the new firmware once it is released.
Care should be used in restoring apps... many are not 4.4.3 compatible like 4.2.2. So some issues will arise with using customizations. I may hold off another year before installing 4.4.3... I don't like being a tester, been doing that for 30 years now, and like the stability of 4.2.2.
Click to expand...
Click to collapse
Thanks for that reply. So, will putting back to factory system reset take root off too? And restore factory recovery? Thanks again gooberdude.
I have kies set up. And good tip about apps not being compatible with updated platform. I hope to remember that when the time comes!!
sashusmom said:
Thanks for that reply. So, will putting back to factory system reset take root off too? And restore factory recovery? Thanks again gooberdude.
I have kies set up. And good tip about apps not being compatible with updated platform. I hope to remember that when the time comes!!
Click to expand...
Click to collapse
Actually if you are using SuperSU you can do a complete wipe of root... Titanium Backup also has a root remover option. I think both force a reboot when given the ok to wipe. I found by doing the factory reset clears out root and all the apps as well all in one stroke. Though it will take some time while it initializes a fresh copy of the OS.
Rooting does not play with boot loaders, or partitioning. It is just like any common app so to speak but are system files to allow root access permissions with apps. So even if you leave a root alone, a ROM upgrade should overwrite the root files as they are not protected or hard encoded into a partition in any way.
I do believe any full ROM upgrade will remove all system mods. But it is good practice to wipe the old OS settings by doing a factory reset. Kies will do all that is needed for installing a new ROM. As it is designed to do that function in the best manner possible.
For the most part Odin is a tool that requires a certain amount of user input to perform tasks... it is not fully automatic as to clearing and formatting key areas before loading custom firmware. As custom firmwares may load differently than OEM ROMs.
gooberdude said:
Actually if you are using SuperSU you can do a complete wipe of root... Titanium Backup also has a root remover option. I think both force a reboot when given the ok to wipe. I found by doing the factory reset clears out root and all the apps as well all in one stroke. Though it will take some time while it initializes a fresh copy of the OS.
Rooting does not play with boot loaders, or partitioning. It is just like any common app so to speak but are system files to allow root access permissions with apps. So even if you leave a root alone, a ROM upgrade should overwrite the root files as they are not protected or hard encoded into a partition in any way.
I do believe any full ROM upgrade will remove all system mods. But it is good practice to wipe the old OS settings by doing a factory reset. Kies will do all that is needed for installing a new ROM. As it is designed to do that function in the best manner possible.
For the most part Odin is a tool that requires a certain amount of user input to perform tasks... it is not fully automatic as to clearing and formatting key areas before loading custom firmware. As custom firmwares may load differently than OEM ROMs.
Click to expand...
Click to collapse
That's what I thought too. I am surprised that OTA says I have altered the OS, so I can't do OTA upgrade. The only thing I think I have done is root. I just can't remember 3 months ago if I tweaked it any other way.
I have used ODIN- mostly when I got this tablet back in November. Had to learn how to use it, but it was fine. I always read 3 times, and do things correctly Sort of like measure twice, cut once:silly: Most likely will odin back to stock when the time comes. More work, more brain power required
sashusmom said:
That's what I thought too. I am surprised that OTA says I have altered the OS, so I can't do OTA upgrade. The only thing I think I have done is root. I just can't remember 3 months ago if I tweaked it any other way.
I have used ODIN- mostly when I got this tablet back in November. Had to learn how to use it, but it was fine. I always read 3 times, and do things correctly Sort of like measure twice, cut once:silly: Most likely will odin back to stock when the time comes. More work, more brain power required
Click to expand...
Click to collapse
I re-read your original post... you said you installed a custom recovery. The only way to get your OTA back is to do a factory root load. There was one to download somewhere on a rooting thread, or on a custom recovery thread.
If you do perform the custom recovery removal, you may also have to run triangle away to clear out the counters and reset to zero.
Since I had a full custom setup before reverting back to OEM, I had everything done in order. Triangle away running to clear counter, custom recovery and SuperSu.
Before I started with Odin to load my factory ROM, I first removed root with SuperSU, as Triangle Away was properly setup to perform the clear counter. Once I removed SuperSU and rebooted. I then ran Triangle Away and had it reset to boot to stock recovery uploader. Then used Odin to perform the factory ROM install.
=================
Now since you are probably jumping around... I would try seeing if your custom recovery is still intact. Try to boot into your custom recovery, an if so clear all cache and userdata and format your partition, and load the factory ROM from SD. It may perform all the actions for your OEM ROM to be detected properly.
If you by chance have cleared out the custom recovery, then it is a matter of installing Triangle away, and performing the reset of counters. Once done and rebooted, Kies should show your device's ROM info without any issues from your previous customizations.
gooberdude said:
I re-read your original post... you said you installed a custom recovery. The only way to get your OTA back is to do a factory root load. There was one to download somewhere on a rooting thread, or on a custom recovery thread.
If you do perform the custom recovery removal, you may also have to run triangle away to clear out the counters and reset to zero.
Since I had a full custom setup before reverting back to OEM, I had everything done in order. Triangle away running to clear counter, custom recovery and SuperSu.
Before I started with Odin to load my factory ROM, I first removed root with SuperSU, as Triangle Away was properly setup to perform the clear counter. Once I removed SuperSU and rebooted. I then ran Triangle Away and had it reset to boot to stock recovery uploader. Then used Odin to perform the factory ROM install.
=================
Now since you are probably jumping around... I would try seeing if your custom recovery is still intact. Try to boot into your custom recovery, an if so clear all cache and userdata and format your partition, and load the factory ROM from SD. It may perform all the actions for your OEM ROM to be detected properly.
If you by chance have cleared out the custom recovery, then it is a matter of installing Triangle away, and performing the reset of counters. Once done and rebooted, Kies should show your device's ROM info without any issues from your previous customizations.
Click to expand...
Click to collapse
Great info! Thank you Gooberdude! And I don't Jump .LOL. I just take it one step at a time....Smoothe, then if things are screwed up, I jump around!!! And call out for help!!! And duh- I forgot custom recovery is a problem.
I think I have access to both recoveries. Is that possible? I think I can get into the stock recovery by holding down the correct buttons sequence, but can get into Philz by using my cheat app that I really love, Flapps PowerTool. I'll review what I have and how to do the button sequence to pull up stock recovery and post back.
Thank you for the detailed instructions...Appreciate it. It will probably be awhile before kit kat is put out for our Note 8's anyway.
*********************************************************
Nope. Just Philz custom.
sashusmom said:
Hello guys. I got my Note 8 at the holidays, I used OTA to get the 4.2.2 update, and I used autoroot, and just checked my recovery and I have Philz touch 5 installed.
When I check for OTA updates, I find the message your device has been modified, no updates available.
I am running stock 4.2.2. Do I need to unroot and return to stock recovery for OTA updates? I did not remove any apps or freeze anything. The only difference is recovery and being rooted. This question is in anticipation of the release of 4.4 kitkat, slated to be pushed to our device- but I'm not holding my breath for when that will be.
Thanks for your input!
Click to expand...
Click to collapse
Here ya go http://forum.xda-developers.com/showthread.php?p=50156744
Sent from my SM-N900V using Tapatalk
Hey !
I manually flashed to 4.4.2 a while back since I had my KNOX tripped and it wouldn't update via ordinary means, but after flashing firmware with Odin, all my apps were still installed and all my data was intact. That is after flashing with Odin, installing Philz, factory resetting and installing a Hyperdrive ROM - which I had some issues with battery life / wake locks. I just flashed stock firmware again and all my stuff is again, still there, maybe together with wake locks
How is this possible and why does this happen? It's extremely weird.
As a side question: Is there any better/faster website to download firmwares from than Sammobile?
@shiinkotheone isnt the point of TWRP being able to do a factory reset yet keep all apps and app data, I'm sure I read you have to select an option so it deletes everything.
P.s I'm a novice at this stuff and learning myself so don't trust me 100% haha.
Sent from Galaxy Note 10.1 2014 Edition via Tapatalk.
I'm actually using Philz not TWRP, but that doesn't really matter. But the point of factory reset is to keep only system apps and the OS or something close to that (It's supposed to format /data/ and /cache/)
What really freaks me out though is the fact that all my stuff is still there AFTER flashing complete official firmware with Odin, I've flashed firmwares before and data has never been kept.
this happened to me once. i has softbricked tablet trying out some test versions of twrp when it first came out. i ended up having to odin back to stock, but somehow it kept all my data in the restocking. dunno why or how and i've never had this happen with any other device when using odin.
I am trying to restore a backup made with TWRP. Here's what has happened so far:
Flashed TWRP several weeks ago. I've made several backups with no problems.
Flashed NK2 radio with no apparent problems.
Full wipe of phone. Phone was not rooted at this point.
Flashed 5.01 GPE ROM.
Phone boots and I get the "Kernal not SELinux enforcing" message (ugh...KNOX). Phone won't boot to new rom. I can only get to TWRP.
Try to restore backup. TWRP checks MD5 on backup-it passes and then screen blanks and TWRP reboots. It does this several times.
After research I restore phone to stock MB4 through Odin.
Phone boots into Android and is indeed 4.4.2 MB4.
Using Unified Toolkit re-flash TWRP and then proceed to root phone. After procedure SuperSU gives me "SuperSU has stopped" msg. Follow toolkit procedure to get around KNOX. SuperSU runs and I also install Busybox. Reboot phone. Root not held. Redo toolkit procedures to attain root. Still lose it upon reboot.
TWRP still reboots when trying to do anything involved with the filesystem (restore backup--wipe cache and dalvik--none works. TWRP blanks and reboots.) . At this point I'm scratching my head. I'd like to restore the backup and also root and change to GPE. I'm thinking this comes down to not being able to do anything in the filesystem due to root not being held. Any suggestions as to how to get root to stick so I can do the restore and change ROMS? Thanks folks.
Steve KS4KJ
If you don't have root you wouldn't have twrp, you would have the stock recovery.
You need to do a factory reset and start from there.
If you can't do it in twrp, flash back to stock with Odin, then do a factory reset. At this point you may have corrected what got borked by flashing the 5.0 rom.
I would recommend flashing to latest firmware NH7 or NK2 and running phone for 24hrs just to make sure there are no issues and that everything works.
ShinySide has links in general section.
Pp.
PanchoPlanet said:
If you don't have root you wouldn't have twrp, you would have the stock recovery.
You need to do a factory reset and start from there.
If you can't do it in twrp, flash back to stock with Odin, then do a factory reset. At this point you may have corrected what got borked by flashing the 5.0 rom.
I would recommend flashing to latest firmware NH7 or NK2 and running phone for 24hrs just to make sure there are no issues and that everything works.
ShinySide has links in general section.
Pp.
Click to expand...
Click to collapse
In flashing the stock 4.4.2 rom (which is where my phone was when I started this journey) I have done a reset haven't I? That is what I did when the 5.0 GPE rom wouldn't boot. I can certainly try loading the 4.4.4 NK2 rom and seeing what that will do. Pretty sure I did not root before using the toolkit to replace the stock recovery with (originally) CWM and then later with TWRP. I remember wanting to do a Nandroid backup before installing the 4.4.4 OTA (which then didn't work because I had changed the stock recovery). I keep thinking that KNOX is involved with this but not sure what to try to remedy it (other than the 4.4.4 suggestion which I will try). Thanks for the reply.
Steve
The only thing Knox does is tell Samsung if you rooted and installed a custom recovery, and that is only while your still under warranty (12 months ) after you get the phone. After that warranty runs out they don't give a hoot what you do to your phone.
You need to flash it twice so that it works properly, after d/l Samsung info app, in play store and check that you have current bootloader and modem .
And use Chainfire's auto root to root afterwards.
Pp.
PanchoPlanet said:
The only thing Knox does is tell Samsung if you rooted and installed a custom recovery, and that is only while your still under warranty (12 months ) after you get the phone. After that warranty runs out they don't give a hoot what you do to your phone.
You need to flash it twice so that it works properly, after d/l Samsung info app, in play store and check that you have current bootloader and modem .
And use Chainfire's auto root to root afterwards.
Pp.
Click to expand...
Click to collapse
I'll try that. Thanks again.
So here's what happened. First I had Cyanogen 12.1 (Lollipop 5.1.1) working fine. I was looking to upgrade so I flash ed Emotion AOSP rom (Marshmallow 6.0.x) (LINK). But it didn't quite fly with my system and I was getting random crashes on my system. These crashes would leave my phone unbootable, until I plugged my phone to charge. This was pretty funky, so I figured there's something up with my kernel. So I thought of flashing beastmode kernel (Marsmallow PD1) (LINK).
This made sense to me because the ROM was Marsmallow, so Marsmallow kernel would work right? I then flash the kernel, which made it so my phone couldn't even boot past the Emotion ROM app load sequence. After, I tried factory reseting and clearing cache + dalvik but that didn't work. By now, I've had enough and just wanted stock marshmallow.
I then try flashing PD1 stock tar and PC1 stock tar with and without factory reset + full wipe (with TWRP) before it. Here, I get stuck on the boot splash screen (the "Powered by Android" screen for clarification) every time, no errors on odin though. I've also tried, after much forum browsing, flashing PIT and Nand erase along with PD1 + PC1 stock tar flashing to no avail (also getting stuck on boot splash screen, and no errors on odin).
Does anyone have an idea of what can be done to hopefully fix my device?
Device (for clarifcaiton purposes): N910P
Thoughts on Methods for Repair:
1) JTAG
2) Go home (call it quits) and switch to iPhone.
EDIT:
Problem turned out to be battery.
Where did you get the TAR files from? there are some on here that are COMPLETELY full stock with bootloaders and kernels.
Also, after you use odin I would suggest booting to recovery and wiping all caches and factory reset
joshka89 said:
Where did you get the TAR files from? there are some on here that are COMPLETELY full stock with bootloaders and kernels.
Also, after you use odin I would suggest booting to recovery and wiping all caches and factory reset
Click to expand...
Click to collapse
I get the TAR from here (xda).
For OK1 I've used this one (LINK).
For PC1 I've used this one (LINK).
For PD1, I've used this one (LINK).
I want the ones that are completely stock right? How do I know if they are? By their size?
Also, after Odin, should I factory reset and wipe cache immediately after?
-Thanks
Eluderei said:
I get the TAR from here (xda).
For OK1 I've used this one (LINK).
For PC1 I've used this one (LINK).
For PD1, I've used this one (LINK).
I want the ones that are completely stock right? How do I know if they are? By their size?
Also, after Odin, should I factory reset and wipe cache immediately after?
-Thanks
Click to expand...
Click to collapse
The stock tars are just that... stock. Rom tars are complete roms. ota update zips are usually just patches meant to update an existing software and can only be applied by download it and applying the update on the phone itself. These ota zip files can't be used for any other purpose. Odin flashable tars are meant to be used on your pc and are complete rom, modem & bootloader, carrier packages so this is the best way to updat if you want a clean slate and don't mind backing up your internal storage and wiping your device first. As for your boot problem... Sometimes you can have leftover data on your internal storage or sd card that can cause the phone to hang at boot. When this happens just do a factory reset in the stock recovery and reboot the phone and it should boot up just fine. Always try this first when that happens after flashing a known good rom whether custom or stock.
tx_dbs_tx said:
The stock tars are just that... stock. Rom tars are complete roms. ota update zips are usually just patches meant to update an existing software and can only be applied by download it and applying the update on the phone itself. These ota zip files can't be used for any other purpose. Odin flashable tars are meant to be used on your pc and are complete rom, modem & bootloader, carrier packages so this is the best way to updat if you want a clean slate and don't mind backing up your internal storage and wiping your device first. As for your boot problem... Sometimes you can have leftover data on your internal storage or sd card that can cause the phone to hang at boot. When this happens just do a factory reset in the stock recovery and reboot the phone and it should boot up just fine. Always try this first when that happens after flashing a known good rom whether custom or stock.
Click to expand...
Click to collapse
I tried fr + fw and then Odin flashing Odin Flashable OK1 from (LINK). After installing, I went to recovery mode and did as you said fr and also clear cache. After, I sitll had bootloops. What can I do about this?
Thanks for the response
-Eluderei
Eluderei said:
I tried fr + fw and then Odin flashing Odin Flashable OK1 from (LINK). After installing, I went to recovery mode and did as you said fr and also clear cache. After, I sitll had bootloops. What can I do about this?
Thanks for the response
-Eluderei
Click to expand...
Click to collapse
Make sure you flash the stock OK1 kernel. then do a factory reset once more.
tx_dbs_tx said:
Make sure you flash the stock OK1 kernel. then do a factory reset once more.
Click to expand...
Click to collapse
Flashed stock OK1 kernel from here (LINK). Tried to boot in to recovery. Phone would boot to android robot, but would crash back to boot screen and wouldn't load the recovery menu. I flashed TWRP via Odin to FR and clear Cache + Dalvik and rebooted, phone still has bootloops. Also, interesting thing, the phone can't boot to TWRP recovery unless it's plugged in to a computer/outlet. What do you think this means? Also, where do you think I can go from here?
Thanks again
-Eluderei
Eluderei said:
Flashed stock OK1 kernel from here (LINK). Tried to boot in to recovery. Phone would boot to android robot, but would crash back to boot screen and wouldn't load the recovery menu. I flashed TWRP via Odin to FR and clear Cache + Dalvik and rebooted, phone still has bootloops. Also, interesting thing, the phone can't boot to TWRP recovery unless it's plugged in to a computer/outlet. What do you think this means? Also, where do you think I can go from here?
Thanks again
-Eluderei
Click to expand...
Click to collapse
It sounds like there is a system app that isn't optimizing at boot and/or your bootloader doesn't match the software & kernel. they all need to be from the same software version. If you get that done it should boot fine.
tx_dbs_tx said:
It sounds like there is a system app that isn't optimizing at boot and/or your bootloader doesn't match the software & kernel. they all need to be from the same software version. If you get that done it should boot fine.
Click to expand...
Click to collapse
Brought it to Sprint today, problem turned out to a battery. Tech guy put his battery in my phone, it booted up just fine. Buying battery soon. Can't wait to install the MOAR Rom that you've worked on. Thanks in advance for that. Thanks for all the help along the way as well