Still on April patch, with TWRP, need some guidance on what steps to take before I screw something up. I think I installed the recovery on b partition or something. I saw links to all the stock stuff around here before, just unsure in which order to flash things or if there's something more that I need to do. There's a thread on how to go back to stock on Oreo, but would it work for Pie too? https://forum.xda-developers.com/nokia-8/how-to/guide-restore-nokia-to-stock-t3867646
Any help please?
Related
NOTE: This was posted in the past, but I messed up the wording... probably why I didn't get help. I said that I had forgot to flash, but what I forgot to do was to Root my phone. Here's a copy-paste of my previous post, but with fixed wording.
Hi there!
First of all, yes, I'm completely new to modding Android phones. Not so new to modding in general though, which makes me question why I made such a nooby mistake... but alas, I now have to ask what many might think to be a nooby question in order to fix said mistake.
Just as the title said, I accidentally installed CWM before rooting my phone, and am now unable to launch into Recovery Mode. I know that there's a way to get it revert it to stock recovery, but as far as I've been able to tell, there's no way to do that without going into the Recovery menu in the first place. Does anybody have an idea what I can do?
My phone can still launch to the firmware (stock firmware, but am planning on installing Cyanogenmod 11), so for now I'm alright but considering the OTHER problems I'm having with the stock firmware, I'd really like a way to get back to my installation ASAP. If I can't, I'll get to my problems with the stock FW later...
-Coover55
If u remove & insert battery, & then try entering recovery mode(Home+Power keys)...u surely have accessed recovery by now
Coover55 said:
NOTE: This was posted in the past, but I messed up the wording... probably why I didn't get help. I said that I had forgot to flash, but what I forgot to do was to Root my phone. Here's a copy-paste of my previous post, but with fixed wording.
Hi there!
First of all, yes, I'm completely new to modding Android phones. Not so new to modding in general though, which makes me question why I made such a nooby mistake... but alas, I now have to ask what many might think to be a nooby question in order to fix said mistake.
Just as the title said, I accidentally installed CWM before rooting my phone, and am now unable to launch into Recovery Mode. I know that there's a way to get it revert it to stock recovery, but as far as I've been able to tell, there's no way to do that without going into the Recovery menu in the first place. Does anybody have an idea what I can do?
My phone can still launch to the firmware (stock firmware, but am planning on installing Cyanogenmod 11), so for now I'm alright but considering the OTHER problems I'm having with the stock firmware, I'd really like a way to get back to my installation ASAP. If I can't, I'll get to my problems with the stock FW later...
-Coover55
Click to expand...
Click to collapse
Which CWM version did you use? Are you running a Stock rom?
I need some help here, and I need to stop bothering the guys in the ROM forum about it so I'm asking here instead.
It's a t-mobile note 4. I was running Dynamic Kat on it and it was suggested I update the modem and bootloader with a partial flash file. Now my phone is stuck in a bootloop.
I CAN get into both download mode and TWRP, however, so it seems like this should be fixable. I'd be happy with even going back to fully stock and rerooting it.
I found this thread: http://forum.xda-developers.com/not...to-downgrade-cod6-to-nk4-upgrade-nk4-t3095585 which seems to about flashing back to stock NK4 or cod6. I know those are bootloaders, but I don't really understand what they mean beyond that.
Or can I just flash to the new stock lollipop t-mobile put out this week? If so, how? If anyone has the time to help me with this, I would really appreciate it.
Edit: I found instructions on sammobile.com. Going to try them. *fixed
Caelrie said:
I need some help here, and I need to stop bothering the guys in the ROM forum about it so I'm asking here instead.
It's a t-mobile note 4. I was running Dynamic Kat on it and it was suggested I update the modem and bootloader with a partial flash file. Now my phone is stuck in a bootloop.
I CAN get into both download mode and TWRP, however, so it seems like this should be fixable. I'd be happy with even going back to fully stock and rerooting it.
I found this thread: http://forum.xda-developers.com/not...to-downgrade-cod6-to-nk4-upgrade-nk4-t3095585 which seems to about flashing back to stock NK4 or cod6. I know those are bootloaders, but I don't really understand what they mean beyond that.
Or can I just flash to the new stock lollipop t-mobile put out this week? If so, how? If anyone has the time to help me with this, I would really appreciate it.
Edit: I found instructions on sammobile.com. Going to try them.
Click to expand...
Click to collapse
Easy fix. ODIN flash the stock COD6 software. Then start over again with cf auto root. There is a thread that had all of the files you need in one zip.
Sent from my SM-N910T using XDA Free mobile app
Yayyy I think it worked! Stock Lollipop is booting up. It's in the Optimizing apps phase.
Caelrie said:
Yayyy I think it worked! Stock Lollipop is booting up. It's in the Optimizing apps phase.
Click to expand...
Click to collapse
Are you the same one who renamed the tar.md5 file to tar? If so, when you ask for help you really should mention all the steps you took to get there. Where it went wrong, etc.
When in doubt, Odin flash full firmware to get back to stock. There are other steps you could have taken as well but Odin is almost always a surefire bet.
(Also remember to hit the thanks button for those who have helped you get things sorted, like that fella above and the people who helped you in the rom thread- not me of course because I didn't do anything but for those who did I'm sure they would appreciate it)
absinthesummer said:
Are you the same one who renamed the tar.md5 file to tar? If so, when you ask for help you really should mention all the steps you took to get there. Where it went wrong, etc.
When in doubt, Odin flash full firmware to get back to stock. There are other steps you could have taken as well but Odin is almost always a surefire bet.
(Also remember to hit the thanks button for those who have helped you get things sorted, like that fella above and the people who helped you in the rom thread- not me of course because I didn't do anything but for those who did I'm sure they would appreciate it)
Click to expand...
Click to collapse
Yah, that was me. I came over here to ask for help instead because I shouldn't be bothering you guys in the ROM thread. I was making progress though. By the time I made this thread, I'd figured out that if I could get into TWRP or download mode, I could odin my way out of it. Just needed some help on that doing that, but then I figured that out too thanks to sammobile
Caelrie said:
Yah, that was me. I came over here to ask for help instead because I shouldn't be bothering you guys in the ROM thread. I was making progress though. By the time I made this thread, I'd figured out that if I could get into TWRP or download mode, I could odin my way out of it. Just needed some help on that doing that, but then I figured that out too thanks to sammobile
Click to expand...
Click to collapse
Cool, glad you got it sorted. Yeah as long as you can access download mode you're golden, and a bonus if you can get into recovery as well.
Excellent job actually searching and reading and fixing your problem, far too many people want answers just handed to them, so kudos to you for that.
Just for the future if you need help, try to remember and list all steps you took (even if you don't know where you went wrong) in excruciating detail because it helps us troubleshoot and figure out what the problem is. Without certain pertinent info it could take a lot longer to solve it.
Overall good job, glad you're up & running.
Go to rapture download the rom and load it to sd card. Then follow directions exactly and u will be ok. No loading anything. Fresh start
BAD ASS NOTE 4
I am in the same boat with the boot loop. I flashed the partial firmware file as well and I did not rename it and the flash went fine. After that it boot to the screen that says powered by Android then it reboots over and over. Currently downloading the stock cod so I can odin that.
ElAguila said:
I am in the same boat with the boot loop. I flashed the partial firmware file as well and I did not rename it and the flash went fine. After that it boot to the screen that says powered by Android then it reboots over and over. Currently downloading the stock cod so I can odin that.
Click to expand...
Click to collapse
Technically you shouldn't be flashing just the partial firmware. It sets up a base so that you can flash a lollipop rom in recovery without issues. I'm not sure why someone is recommending just flashing the partial firmware only. I guess they figured it wouldn't cause issues.
Anyway, here is how the partial firmware should be used:
Flash partial firmware in Odin
Flash flashable stock lollipop in recovery.
Set up rom, make a backup.
From here you can restore your old kitkat backups without the problems that some are seeing (those who Odin the full firmware are having problems restoring kitkat backups/flashing kitkat roms without Odining ank4 first). The partial firmware prevents that but it's designed to be flashed right before flashing a lollipop rom.
I hope that helps some of you who are having issues.
Hey guys, I was wondering if anoyone could help me find the stock odin file for my tab S2 Tmobile? I rooted and I have twrp and everything. I wanna go back to having LTE while I wait for a custom kernel that can support it. I have had some problems locating said odin file. Any help would be greatly appreciated.
One of the most important reasons for having a custom recovery such as twrp is so you can make a full backup PRIOR to making any modifications.
I don't know how many times I have said this yet still people go ahead and flash regardless.
The firmware you are looking for is not available yet.
You're only hope is to ask someone who has the same model with unrooted firmware to make a backup of the system and boot partitions and upload them.
Or you may be able to unroot with supersu then flash just the boot.img.
If unrooting doesn't work then you may be able to flash the boot and system partition from the firmware below with Flashfire.
http://samsung-firmware.org/model/SM-T817P/
Make that backup first.
ashyx said:
One of the most important reasons for having a custom recovery such as twrp is so you can make a full backup PRIOR to making any modifications.
I don't know how many times I have said this yet still people go ahead and flash regardless.
The firmware you are looking for is not available yet.
You're only hope is to ask someone who has the same model with unrooted firmware to make a backup of the system and boot partitions and upload them.
Or you may be able to unroot with supersu then flash just the boot.img.
If unrooting doesn't work then you may be able to flash the boot and system partition from the firmware below with Flashfire.
http://samsung-firmware.org/model/SM-T817P/
Make that backup first.
Click to expand...
Click to collapse
I thank you for your assistance, but I must say that I am not a novice when it comes to rooting, flashing, odining etc. etc.
I was merely asking if anyone came across the stock odin file I listed above, if they could link it to me. I am having a hard time finding it and as you pointed out, is because it isn't there to be found. So I will continue to wait patiently and use wifi until it is released.
Thank you.
Hi I have a few questions for my nexus 6 that I am getting today
1) I am going to flash a the new marshmallow update, which one should I pick because for root you need a specific build but on the google factory images the latest build is not supported? I really don't know.
2) After I flash 6.0 can I just do the fastboot flash recovery twrp.img without flashing the boot.img
3) When I go to a new rom like Chroma by Zephik do I still need to change the boot.img to flash the beta super user
For now these are all my questions and I would really appreciate if you could answer it.
side note: I cannot use NRT becuase I am on a mac, if you guys have any alternatives I would really appreciate it too.
1) Flash any of them, they are all rootable. I would recommend going with the latest one. Unless I am mistaken, I believe K, N, and R each have the same radio so there effectively would be no real difference in the end result, as a custom ROM will overwrite everything else.
2) Yes, there is no need to have a modified boot image or root if you plan on flashing a custom ROM.
3) This depends on the ROM, they should have instructions in their post as to what they require. I am pretty sure Chroma comes with a custom kernel already, and I believe it comes pre-rooted as well. It could be that you have to root the ROM after you flash it if you want root though, there are some ROMs that are like that. The OP should have installation instructions.
As for your side note, I don't recommend using a toolkit of any sort. I recommend learning how to use fastboot, and doing it manually. That way if you were to need to fix something in the future, you would have a general understanding of what you did and why, and perhaps that will help you in how to fix it. Rather than clicking a couple buttons in a toolkit. Also, toolkits can fail, and not tell you why. It is often hard to figure out what went wrong when it is doing multiple steps at once, rather than one at a time like if you were to do it the manual way. It really isn't that difficult, and it is very well documented process at this point with tons of guides with pictures and even videos out there.
cupfulloflol said:
1) Flash any of them, they are all rootable. I would recommend going with the latest one. Unless I am mistaken, I believe K, N, and R each have the same radio so there effectively would be no real difference in the end result, as a custom ROM will overwrite everything else.
2) Yes, there is no need to have a modified boot image or root if you plan on flashing a custom ROM.
3) This depends on the ROM, they should have instructions in their post as to what they require. I am pretty sure Chroma comes with a custom kernel already, and I believe it comes pre-rooted as well. It could be that you have to root the ROM after you flash it if you want root though, there are some ROMs that are like that. The OP should have installation instructions.
As for your side note, I don't recommend using a toolkit of any sort. I recommend learning how to use fastboot, and doing it manually. That way if you were to need to fix something in the future, you would have a general understanding of what you did and why, and perhaps that will help you in how to fix it. Rather than clicking a couple buttons in a toolkit. Also, toolkits can fail, and not tell you why. It is often hard to figure out what went wrong when it is doing multiple steps at once, rather than one at a time like if you were to do it the manual way. It really isn't that difficult, and it is very well documented process at this point with tons of guides with pictures and even videos out there.
Click to expand...
Click to collapse
Thanks so much, I actually used adb/fastboot when I was rooting my mytouch 4g so this knowledge should come in handy, one other question if I were to root the latest factory image can I use the MRA58K.img that Chainfire posted for 6.0 or do I have to find a modified boot img that matches the latest factory image which is MRA58R, thank you so much again
Hello, does anyone know how to revert back to stock ROM? Any guides? I can't seem to find any guides that aren't few years old.
Also will phone storage be repartitioned to stock values after flashing?
I want to flash newest LineageOS, but want to make sure i can go back in case something goes wrong.