Everything was perfect with 9.5.10 but I rooted and upgraded to 9.5.11. I want to downgrade one version while staying rooted. I just bricked my phone last night and I don't want to take any unnecessary chances since I don't have easy access to a PC (I'm on a Mac) to unbrick my phone if anything happens.
Can someone tell me what steps I should take to downgrade to 9.5.10 and still have root without using a computer?
Which fastboot/ROM should I download, what to flash in twrp, what to wipe, etc. Will be helpful.
Thank you!
Related
I'm kind of new to the whole rooting thing. However, I managed to root the Unlock the bootloader, install the recovery and then root it. However when I tried to install a ROM the phone when off after I had wiped the old OS. So at the moment I am stuck in limbo, all the phone does is flash, any ideas? Thanks.
Waggy2014 said:
I'm kind of new to the whole rooting thing. However, I managed to root the Unlock the bootloader, install the recovery and then root it. However when I tried to install a ROM the phone when off after I had wiped the old OS. So at the moment I am stuck in limbo, all the phone does is flash, any ideas? Thanks.
Click to expand...
Click to collapse
You might want to post in the emergency thread for this.
Someone will chime in I am sure. From what little I know, I would try using the RUU (ROM update utility) to restore the phone.
Before you do that, wait a little while and maybe someone else will post with some other method. The RUU will hopefully restore your phone to stock.
I'm trying to do that now buy it just wont boot up so I can't run the program
So as the title says, I recently sunshine unlocked my 4.2.2 (12.15.15 firmware) MAXX. At this point, I have a custom recovery from the root method I used on the phone a year ago, but other than that I'm just running the stock 4.2.2 Camera update.
What is the easiest way to get up and running on a current 4.4.4 build? Can I use RSDlite to return to stock 4.2.2, or does that not work with an unlocked bootloader? Could I RSDlite to 4.4.4 directly? What about flashing TWRP to my phone now and using that to flash a 4.4.4 rom? I dont care about losing all of my data or anything like that.
I'm a little confused on what I can and can't flash depending on the current version of andoid I'm on, so any help would be greatly appreciated. Thanks!
now that your bootloader is unlocked you can have root on any fw version you decide to update to. but you have to be on stock everything before you update to 4.4.4. if the recovery is the only thing you have changed you can just extract it from the fxz for 4.2.2 if that's what your on right now. flash it using fastboot or the easy way using rashr an app from play store. my fav for flashing recoveries. then take the update. after that you can flash T.W.R.P 2.8.4.0 for obake. then reboot to recovery. reboot to system to gain root if it is removed by updating
Thanks for the reply. I'll look into flashing that recovery and try the OTA. Would flashing the whole fxz (which i believe includes a bootlader) hurt me? Also, is there any way one of the OTA's changes the bootloader in a way that could mess up my unlock?
no. once your bootloader is unlocked then it won't relock unless you lock it by command prompt. yes you could use rsd to go back to stock. it has to be the exact version you are currently on. if you try to rsd a version your not on it will fail.
Will it fail in a "your phone is bricked" kind of way or an error message telling you it wont flash?
it will error telling it was aborted. i have done it once that's all it took for me to realise it needed the exact version. i was lucky to have the right one handy
here is a site for all the stock firmware.
http://motofirmware.center/files/category/
I'm in the same boat and going to do this tonight on my wife's phone.
She's currently on 4.2.2, bootloader is unlocked, rooted, and currently has TWRP installed.
If I'm correct, I need to
1. Flash stock recovery
2. Boot up and take the OTAs
then
3. Flash the latest TWRP
4. Use TWRP to re-root
4. Then I can flash a 4.4.4 rom, such as http://forum.xda-developers.com/showthread.php?t=2716824
Is that correct?
As long as my bootloader is unlocked, can I still regain root with the latest OTA?
Thanks guys, just making sure as the wife will be miffed if I screw up her phone!
Honestly, I doubt you have waited this long, but if you have, here is what I am gathering from your question... You want to run 4.4.4 roms instead of 4.2? While on 4.2.2 (if you still are) you can run OSE, AOSB, CM11, and pretty much any 4.4.4 custom rom. (though i can't get cm12 to work on a mini (same software/bootloader/recovery for the most part) on 19.6.3 so that may be out) The only reason you would have to update would be to be on stock 4.4.4. I haven't read up too much on the new OTA's, but I can say this, YOU CAN NEVER GO BACK TO WHAT YOU ARE ON ONCE YOU UPGRADE STOCK. this may not be a big deal for you, but personally, I liked the JB software the best (specifically 12.7.7 that my DEV MAXX came with) I haven't heard anyone say anything positive (really) about VOLTE or any new features, and honestly, not being able to go back on a DEV EDITION sucks. On a side note, I recently bought a Mini (bc my charge port on my DEV maxx crapped out and Moto doesn't have any more, so i am in phone purgatory waiting for *something* but pretty much anyone I have talked to is useless.) I just fxz'd back to 19.5.3 from 19.6.3, but I cannot go backwards any further *completely* @NWKENT has done it numerous times as best as it *can* be done. also, @NWKENT can confirm you absolutely cannot go back from 4.4.4 to an earlier edition. I hope this helps if you haven't upgraded yet. If you have, for most intents and purposes, you haven't really lost anything.
Hi,
About a year ago I got fed up with Verizon constantly messing with my rooted phone, which I was completely happy with as it was, with their OTA updates. I used some of the guides on here to stop the OTA's and after some trial and error finally got them to stop bugging me. The phone is running Kitkat 4.4.2.
Now a year later I bought a new car and in order for the phone to work with the car it needs to be running at least Lollipop 5.0 but I cannot get the phone to update. I know I used Titanium, the full version, to freeze some of the OTA entries and I tried unfreezing them to no effect. I know I used another program to freeze some of the OTa options but I do not remember what it was. I have also tried doing multiple factory resets and I have tried to update it using Kies. Nothing works. I also used Odin and flashed the stock 4.4.2. Had no effect.
Appreciate any help. I am not that tech savvy but I can usually follow instructions well if anyone can help me out.
Thank you.
If you used Odin to flash an image, whatever you did to freeze the OTA function was completely undone. That's clearly not your problem.
Just follow the instructions in this thread to flash the latest Lollipop image provided, and then root it. http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
painiac said:
If you used Odin to flash an image, whatever you did to freeze the OTA function was completely undone. That's clearly not your problem.
Just follow the instructions in this thread to flash the latest Lollipop image provided, and then root it. http://forum.xda-developers.com/verizon-galaxy-s5/general/root-method-og5-ok3-t3290370
Click to expand...
Click to collapse
Thanks for the reply.
Can I still root the latest build number NRD90M.N920TUVU4EQG3 for the T-Mobile Note 5?
My overall goal in rooting is to revert back to MM. Honestly I hate Nougat and the battery life has dropped significantly so I'd like to flash a MM ROM. I'm sorry if this is in the wrong section or has been asked before. Just looking for some help. The research I did only showed how to root Nougat but didn't specify the particular build number. I forgot to ask also if Odin is the ONLY method I have to root? I've run into issues before with Odin. Just curious if there's another method for rooting.
tech15 said:
Can I still root the latest build number NRD90M.N920TUVU4EQG3 for the T-Mobile Note 5?
My overall goal in rooting is to revert back to MM. Honestly I hate Nougat and the battery life has dropped significantly so I'd like to flash a MM ROM. I'm sorry if this is in the wrong section or has been asked before. Just looking for some help. The research I did only showed how to root Nougat but didn't specify the particular build number. I forgot to ask also if Odin is the ONLY method I have to root? I've run into issues before with Odin. Just curious if there's another method for rooting.
Click to expand...
Click to collapse
You don't have to root to revert. What I did was put the phone into download mode and flashed the MM Rom from QC2, I believe, or whatever the version was from samfirm which is deprecated now. Just remember to have the OEM unlock enabled and USB debugging enabled in developer. You should be able to then use Odin to revert. If it doesn't work then you can try and root the phone using the root QE1 method from the posts in the T-Mobile note 5 thread and follow the guide. I can't say for certain if you can downgrade straight from an unrooted 7.0 rom to an earlier 6.0.1 MM rom in Odin. But what I do know is this. I came from the Khongloi v11 rom and decide to do something stupid.
"After unwittingly turning off OEM unlock and USB debugging and rebooting phone. I lost all my data. Stupid me. I got so used to quick rebooting and all of sudden decided to do a hard reboot, *sigh. Oh well, you live you learn. Just remember if you do root. Leave those options on. Never, ever, ever, ever disable OEM unlock. EVER."
Anyways, try downgrading in Odin 3.10.7 or if you have trouble with any newer Odin versions. If you have trouble with the newer versions, use an older version. If you can't downgrade directly from that rom, might have to try another way.
Thanks for the reply and advice! But just making sure though for general root purposes: I'm able to root the latest build number?
Try and see. I'm actually on the same firmware and haven't tried yet. I'm still considering if I should root again. I miss using game guardian, especially for LDoE: Survival.
I'd do it but I'm nervous I'm gonna mess up my phone. I was hoping someone will chime in and let me know it's good to go lol
No worries. You can't, because Odin will give you an error message if the firmware doesn't allow it. Kinda how it was in previous revisions. I've tried on purpose to brick my device. The only real way to brick a device is to do something super, super stupid. Try, the only thing that can result is you get an error in Odin and it fails.
The reason I say this is because I tried to use Odin to flash Nougat onto my Verizon S7 and I honestly don't know what the hell I did but it continually bootlooped to the point where I couldn't get it in recovery or anything. It was messed up. Had to send it in for another S7 which I sold and got a Note 5 lol. Needless to say I'm a bit nervous to use Odin.
tech15 said:
The reason I say this is because I tried to use Odin to flash Nougat onto my Verizon S7 and I honestly don't know what the hell I did but it continually bootlooped to the point where I couldn't get it in recovery or anything. It was messed up. Had to send it in for another S7 which I sold and got a Note 5 lol. Needless to say I'm a bit nervous to use Odin.
Click to expand...
Click to collapse
Honestly, bootloops can be fixed. Either thru the recovery or by download mode. It must have been something else you flashed. But if you decide to try and root and Odin doesn't take, then you haven't done anything to jeopardize your phone.
DISCLAIMER: I NOW understand I know very little about flashing and have trouble keeping up with all the steps it involved. I once rooted an old Pantech with no issues and bit off a bit more than I could chew this time around.
I have a Sony Xperia XZ Premium Dual (G8142) that was running the US version by stock. I was running the November security patch and Oreo 8.0.0. Yesterday I wanted to try my hand at some rooting and attempted the XperiFIX by //Storm, but after a couple of setbacks decided I wanted to go back to my stock phone and a redditor helped me flash the stock firmware on it to get it working again using a tool called EMMA.
My issue is I ended up flashing the stock EU version of the phone on Nougat (7.1.1) and now I can't seem to update to Oreo (8.0.0). So I wanted to know if the EU versions HAVE gotten the update -*meaning my phone is unable to update*- or if the current update *IS* 7.1.1 with the September security patch -*therefore I could just enjoy it as is and patiently wait for 8.0.0 when it does roll out for EU versions*-.
I'm bad at this flashing thing and I have a bunch of bugs I didn't have before (i.e. green pictures when using camera). I attempted to re-flash stock US version using flasher, but I can't get the flasher to detect the firmware no matter how many times I tried. I just want to either fix the EU version or flash US version. Either ways I'm not smart enough to figure this out. Want to know what are my options for fixing EU version or whatnot. Any and all help will be appreciated.
Xperia XZ Premium Dual G8142
Nougat 7.1.1
Running September security patch
45.0.A.7.137
Unfortunately, you can't relock the bootloader anymore once you've unlocked it. You can't update via OTA either since you unlocked the bootloader. You basically lost that "privilege" with you unlocked the BL.
You can, however, use newflasher to flash the latest firmware. Just download the latest firmware using Xperifirm, then use newflasher to flash. Don't forget to use the DRM fix again.
iArvee said:
Unfortunately, you can't relock the bootloader anymore once you've unlocked it. You can't update via OTA either since you unlocked the bootloader. You basically lost that "privilege" with you unlocked the BL.
You can, however, use newflasher to flash the latest firmware. Just download the latest firmware using Xperifirm, then use newflasher to flash. Don't forget to use the DRM fix again.
Click to expand...
Click to collapse
Thank you, iArvee! I unfortunately had the exact same issue as OP. I was able to get the correct firmware and reinstall. I do have one thing to add though. the Xperifix tool isnt working properly on my US XZ Premium dual sim model and I had to manually flash twrp and the kernel through adb. Then i flashed magisk and the drmfix through twrp and now everything works perfect. I spent hours digging through threads to figure this out but it all worked out
Sony has recently added support for the xz premium for their flash tool. I also ran into countless errors with drivers not installing properly trying to get NewFlasher to recognize the phone. If you want to go back to stock, and even root after that, here are the steps you should take, assuming your issue is you can't get NewFlasher to recognize your phone, or you can't get XperiFix to work. I came back from completely wiping the system partition on my phone to having a working, rooted device with sony's rom, so it is definitely possible.
1) flash the firmware for your device using Sony's flash tool (this will delete your custom recovery if you have that installed)
2) reinstall twrp (there are several guides about how to do this, I'd pull up one on xda and follow it
3) follow the instructions on the old drm fix thread from Storm (DO NOT use the new XperiFix tool that he made, I could never get that to work). Go to the current XperiFix thread and there should be a link to the old thread with manual instructions. Doing it manually is not hard, it should just be flashing 4 files in succession through your custom recovery, so don't let the concept of doing it manually scare you.
4) make a nandroid backup in twrp to prevent you from having this headache in the future.
-if at any point, you mess something up, you can always re-flash sony's firmware using their flash tool. I had to do this multiple times while trying to get the XperiFix tool to work. I eventually gave up and did it manually, but just know you can always start over if you mess it up.
TboneThomas said:
Sony has recently added support for the xz premium for their flash tool. I also ran into countless errors with drivers not installing properly trying to get NewFlasher to recognize the phone. If you want to go back to stock, and even root after that, here are the steps you should take, assuming your issue is you can't get NewFlasher to recognize your phone, or you can't get XperiFix to work. I came back from completely wiping the system partition on my phone to having a working, rooted device with sony's rom, so it is definitely possible.
1) flash the firmware for your device using Sony's flash tool (this will delete your custom recovery if you have that installed)
2) reinstall twrp (there are several guides about how to do this, I'd pull up one on xda and follow it
3) follow the instructions on the old drm fix thread from Storm (DO NOT use the new XperiFix tool that he made, I could never get that to work). Go to the current XperiFix thread and there should be a link to the old thread with manual instructions. Doing it manually is not hard, it should just be flashing 4 files in succession through your custom recovery, so don't let the concept of doing it manually scare you.
4) make a nandroid backup in twrp to prevent you from having this headache in the future.
-if at any point, you mess something up, you can always re-flash sony's firmware using their flash tool. I had to do this multiple times while trying to get the XperiFix tool to work. I eventually gave up and did it manually, but just know you can always start over if you mess it up.
Click to expand...
Click to collapse
You should know that you can't restore a nandroid backup just yet. There seems to be a bug. I'm not sure if that's fixed yet though.
iArvee said:
You should know that you can't restore a nandroid backup just yet. There seems to be a bug. I'm not sure if that's fixed yet though.
Click to expand...
Click to collapse
I'd heard rumors about it not working, but I haven't tried to restore from one yet. Thanks for the info
TboneThomas said:
I'd heard rumors about it not working, but I haven't tried to restore from one yet. Thanks for the info
Click to expand...
Click to collapse
It's not a rumor, it's an actual fact. Hopefully a fix is underway.