Does anyone know where I can get the stock recovery?
Nevermind. dottat has it covered per usual.
http://forum.xda-developers.com/verizon-htc-10/how-to/verizon-official-ruu-1-19-605-9-t3377586
What did you need it for ? Factory reset of radios doesn't happen on the 10 using stock recovery like it did on the 8
Slowly figuring this out. haha
I guess for nothing anymore
Do we not need the stock recovery for Ota?
I'm seriously confused now.
@Icyman if you have everything 100% you can ota. But if you are on a custom rom why not simply flash the updated firmware zip?
deleted
Related
I did a dumb thing while flashing a rom. Used the format rather wipe. Now I get stuck on reboots. Can reflash a ROM and get going again but get stuck on the next reboot.
Back to Stock via Odin, right? So, AdamOutler has a thread on Odin back to stock.
1) Does this alone fix the partition or do I then factory reset to fix the partition?
2) Will I be on a stock recovery then or will I the retain custom recovery?
At this point, what's the next step to get back my root and way cool custom ROM?
I'm finding scattered info, but nothing that spells it out and I don't want to mess this up.
Thanks!
.
As long as you aren't on mf3 booloaders it is okay to use the back to stock Odin package. It will fix your partitions. You will be stock recovery and no root. An out of the box experience. Reroot with adams tool. I suggest philz touch recovery (the latest). Stay away from twrp
Sent from my SGH-I337 using Tapatalk 2
here's a link and posts by some experienced members--don't know if you saw it
you may always get multiple suggestions
good luck
http://forum.xda-developers.com/showthread.php?t=2405127
Locoman_ said:
I did a dumb thing while flashing a rom. Used the format rather wipe. Now I get stuck on reboots. Can reflash a ROM and get going again but get stuck on the next reboot.
Back to Stock via Odin, right? So, AdamOutler has a thread on Odin back to stock.
1) Does this alone fix the partition or do I then factory reset to fix the partition?
2) Will I be on a stock recovery then or will I the retain custom recovery?
At this point, what's the next step to get back my root and way cool custom ROM?
I'm finding scattered info, but nothing that spells it out and I don't want to mess this up.
Thanks!
.
Click to expand...
Click to collapse
Well you're running TWRP so you are obviously not on MF3. Just Oden back to stock and re-root and loki away again. Its just a mistake you wont make again... Trust me I learned the hard way too.
fosser2 said:
Well you're running TWRP so you are obviously not on MF3. Just Oden back to stock and re-root and loki away again. Its just a mistake you wont make again... Trust me I learned the hard way too.
Click to expand...
Click to collapse
Thanks guys. Odin to stock, facrory reset, reroot and back to xvision. compulsively did this late into the night.. now its smooth sailing
Hi,
I'm currently downloading the firmware for my Note 3 from SamMobile.
I was going to flash back to stock, and assume by doing this I would lose root.
What would happen about me having TWRP installed? I know the Note 3 has Knox, so would I get stuck in a bootloop or anything else bad by having a custom recovery on a stock, unrooted phone?
Thanks.
paulschofield76 said:
Hi,
I'm currently downloading the firmware for my Note 3 from SamMobile.
I was going to flash back to stock, and assume by doing this I would lose root.
What would happen about me having TWRP installed? I know the Note 3 has Knox, so would I get stuck in a bootloop or anything else bad by having a custom recovery on a stock, unrooted phone?
Thanks.
Click to expand...
Click to collapse
Yeah root will go and twrp
Thanks for that. Losing root wouldn't be a problem, I was just worried about what would happen if twrp stayed in the phone. I didn’t realise flashing back to stock would also put the stock recovery back on my phone too
paulschofield76 said:
Thanks for that. Losing root wouldn't be a problem, I was just worried about what would happen if twrp stayed in the phone. I didn’t realise flashing back to stock would also put the stock recovery back on my phone too
Click to expand...
Click to collapse
did for me when i had to go back to stock
I'm a total moron, I'll just start there. Was running KOT49H【4.4.2】Google Edition and wanted to go back to vision x since your latest update. Full wipe in twrp, installed vision x, icy theme, went to install ktoonsez kernel and it failed. Somehow between people distracting me, I decided it didn't fail. Reboot, and now bricked. Flashed stock firmware 4.2.2 mdl in odin, but no dice on the reboot. It's because I'm still on a 4.4.2 kernel, isn't it...
Now what do I do? Let kies fix me? Can kies even fix me with 4.4.2 not even being released yet? Kicking myself for being so dumb!!!
First, you're not on 4.4.2. Sounds like you're on 4.3. See if this helps you http://forum.xda-developers.com/showthread.php?p=48557730
This is for the i337
jd1639 said:
First, you're not on 4.4.2. Sounds like you're on 4.3. See if this helps you http://forum.xda-developers.com/showthread.php?p=48557730
This is for the i337
Click to expand...
Click to collapse
ok, I'm just saying, it wasn't booting after I put vision x 4.3 rom on without flashing the loki'd ktoonsez 4.3 kernel. Will updating flash the 4.3 kernel too?
xjimmy said:
ok, I'm just saying, it wasn't booting after I put vision x 4.3 rom on without flashing the loki'd ktoonsez 4.3 kernel. Will updating flash the 4.3 kernel too?
Click to expand...
Click to collapse
What bootloader are you one ? It seems to me you are on MDL and I can't see why you would need to flash the MK2. You are just stuck in recovery correct ? If you can get in recovery just flash the vision x rom again.
You didn't state if you can get into recovery or not. Everytime to flash a rom you flash a kernel so even KT's kernel failed you still have a kernel. You might need to explain some more
EDIT: your other post said you cant get into recovery. When you say no dice on the reboot does that mean it's in a bootloop and all you get is the sammy slash screen ? Can you try ODIN again and flash the MDL firmware. I'm not sure but back in the S3 days if you flashed older firmware you had a bootloop after but then had to just do a factory reset in stock 3e recovery and it would boot
hednik said:
What bootloader are you one ? It seems to me you are on MDL and I can't see why you would need to flash the MK2. You are just stuck in recovery correct ? If you can get in recovery just flash the vision x rom again.
You didn't state if you can get into recovery or not. Everytime to flash a rom you flash a kernel so even KT's kernel failed you still have a kernel. You might need to explain some more
EDIT: your other post said you cant get into recovery. When you say no dice on the reboot does that mean it's in a bootloop and all you get is the sammy slash screen ? Can you try ODIN again and flash the MDL firmware. I'm not sure but back in the S3 days if you flashed older firmware you had a bootloop after but then had to just do a factory reset in stock 3e recovery and it would boot
Click to expand...
Click to collapse
I did an emergency formware recovery via kies. It reset everything stock on 4.2.2 mdl! I thought for sure it would've bumped me to 4.3 that way. Thank you for taking the time to respond and try to help. I will be much more careful moving forward and am considering this luck for my crazy mistakes. Yay!!
I need this fixed asap as I need my phone for school.. I have no idea what Happened honestly, I just restarted my phone and it started doing this. The only thing i recall doing is possibly disabling SuperSU on accident before I restarted my phone.
All I've done so far is download the stock firmware from SamMobile and attempted to flash it, but when i do i get an (auth) failed code from Odin, I've been searching for hours and haven't found anything that has helped..
If you have TWRP installed, try removing SuperSU via the file manager in recovery, or flash SuperSU again
The Auth! problem is likely due to you trying to flash an older ROM version than is installed, and the bootloader won't allow it
Tried clearing caches from recovery / factory reset?
Can you help with a newer model?
*Detection* said:
If you have TWRP installed, try removing SuperSU via the file manager in recovery, or flash SuperSU again
The Auth! problem is likely due to you trying to flash an older ROM version than is installed, and the bootloader won't allow it
Tried clearing caches from recovery / factory reset?
Click to expand...
Click to collapse
i don't have anything recovery installed, its jsut the normal android recovery. I thought about reflashing supersu but I'm not sure how without a recovery..
Have you tried the factory reset from normal recovery?
*Detection* said:
Have you tried the factory reset from normal recovery?
Click to expand...
Click to collapse
Yea.. Ive hit it so many times Id be surprised if it even remembers how to power on lol..
What about a SM-G900P?
TheAgonistxX said:
Yea.. Ive hit it so many times Id be surprised if it even remembers how to power on lol..
Click to expand...
Click to collapse
Lost count of the number of threads about bricked G900A and G900P these last few weeks
Something about the latest Lollipop firmware, locks the bootloader from downgrading, even to just an earlier version of Lollipop, and it's a nightmare to try and find ODIN flashable ROMs for the latest release
Right now, unless someone else can think of something, all I can suggest is either taking / sending it in for repair, or wait for Marshmallow to arrive, and hope an ODIN flashable ROM arrives for that
Might as well give flashing TWRP a try (via ODIN), I don't expect it will work, but if you could get custom recovery running, you might be able to flash a custom ROM
Another thread with a similar issue, you could try this, but I'm expecting the same Auth! error
http://forum.xda-developers.com/showpost.php?p=65234333&postcount=28
*Detection* said:
Lost count of the number of threads about bricked G900A and G900P these last few weeks
Something about the latest Lollipop firmware, locks the bootloader from downgrading, even to just an earlier version of Lollipop, and it's a nightmare to try and find ODIN flashable ROMs for the latest release
Right now, unless someone else can think of something, all I can suggest is either taking / sending it in for repair, or wait for Marshmallow to arrive, and hope an ODIN flashable ROM arrives for that
Might as well give flashing TWRP a try (via ODIN), I don't expect it will work, but if you could get custom recovery running, you might be able to flash a custom ROM
Another thread with a similar issue, you could try this, but I'm expecting the same Auth! error
http://forum.xda-developers.com/showpost.php?p=65234333&postcount=28
Click to expand...
Click to collapse
Tried flashing TWRP with the same end result.. This is dumb really frustrating -.- is there any way to install Supersu without a recovery?
CF Auto Root, but it'll likely fail too due to the bootloader
II have been working on mine same model and it is because once you screw up ,which i did,the locked boot loader wont let anything by. a relative pretty much started the problem by flashing a ROM and erasing everything. this one wont even go into recovery. still wont give up until I figure out a way just because.......
I was able to flash custom roms(CM,AICP,etc), but not anymore.
flashed the vanilla FW via batch file(5.1.1 xt1575), cannot ota to 6.0(fails.).
trying to flash CM13? No dice. always gets stuck on the alien screen. even after 30 minutes. any idea?
MortaLPortaL said:
I was able to flash custom roms(CM,AICP,etc), but not anymore.
flashed the vanilla FW via batch file(5.1.1 xt1575), cannot ota to 6.0(fails.).
trying to flash CM13? No dice. always gets stuck on the alien screen. even after 30 minutes. any idea?
Click to expand...
Click to collapse
I suggest go back to stock rom ie flash the latest 6.0.1
https://firmware.center/firmware/Motorola/Moto X Pure (XT1575)/
This contain lots of stock from lollipop to Marshmallow...
I recommend u to flash mm if it fails flash lp and it shud work
Then u root ur phone install twrp and flash any rom...
It will work..
MortaLPortaL said:
I was able to flash custom roms(CM,AICP,etc), but not anymore.
flashed the vanilla FW via batch file(5.1.1 xt1575), cannot ota to 6.0(fails.).
trying to flash CM13? No dice. always gets stuck on the alien screen. even after 30 minutes. any idea?
Click to expand...
Click to collapse
I have the same problem. I can flash stock ROM and everything is good but if I try to flash any custom ROM, I bootloop.
MortaLPortaL said:
I was able to flash custom roms(CM,AICP,etc), but not anymore.
flashed the vanilla FW via batch file(5.1.1 xt1575), cannot ota to 6.0(fails.).
trying to flash CM13? No dice. always gets stuck on the alien screen. even after 30 minutes. any idea?
Click to expand...
Click to collapse
Why would you flash Lp? Your issue is that you're trying to force a MM ROM to boot with a Lp bootloader.
Sent from my XT1575 using Tapatalk
Yup, flash 6.0 agian, and all files
try reflashing twrp, see if it helps