is it safe to restore back to cm-12.0-YNG1TAS2I3, i am currently on Resurrection Remix Rom 5.1.1, was wondering just starting fresh and going back to stock, anything special i need to do to my phone, i am assuming it will revert back to stock recovery and will this relock the bootloader? thank u.
Bradl79 said:
is it safe to restore back to cm-12.0-YNG1TAS2I3, i am currently on Resurrection Remix Rom 5.1.1, was wondering just starting fresh and going back to stock, anything special i need to do to my phone, i am assuming it will revert back to stock recovery and will this relock the bootloader? thank u.
Click to expand...
Click to collapse
Do you mean restoring a TWRP backup? It won't touch your recovery or your bootloader. Just make sure you wipe properly (system, data, cache, dalvik cache) before restoring.
no doing a full clean restore to stock cm12s, from toolkit
Bradl79 said:
no doing a full clean restore to stock cm12s, from toolkit
Click to expand...
Click to collapse
Don't use a toolkit, they're nothing but trouble and inevitably cause problems. It's perfectly safe to flash the cm-12.0-YNG1TAS2I3 stock images and you'll find detailed instructions in my guide thread:
http://forum.xda-developers.com/showthread.php?t=2839471
Or you can use my re-packaged factory images. It's all automated using a flash-all.bat similar to Nexus devices. Literally a one-click option (with the manual option available too)
EddyOS said:
Or you can use my re-packaged factory images. It's all automated using a flash-all.bat similar to Nexus devices. Literally a one-click option (with the manual option available too)
Click to expand...
Click to collapse
Does your automated script have the "fastboot reboot-bootloader" command between each flash?
Heisenberg said:
Does your automated script have the "fastboot reboot-bootloader" command between each flash?
Click to expand...
Click to collapse
Nope, I've removed all that and they now work (tested on my own OPO)
EddyOS said:
Nope, I've removed all that and they now work (tested on my own OPO)
Click to expand...
Click to collapse
Awesome, I know that rebooting between flashes was causing bricks for some people so that's good to know.
Heisenberg said:
Awesome, I know that rebooting between flashes was causing bricks for some people so that's good to know.
Click to expand...
Click to collapse
Yeah, heard that myself so re-did them. I've only posted the latest CM12S images as I've not the time to go through al the others!
EddyOS said:
Or you can use my re-packaged factory images. It's all automated using a flash-all.bat similar to Nexus devices. Literally a one-click option (with the manual option available too)
Click to expand...
Click to collapse
thank u both for the info, on ur reflash back to stock does it flash stock recovery and relock bootloader? and could i just reflash twrp?
Bradl79 said:
thank u both for the info, on ur reflash back to stock does it flash stock recovery and relock bootloader? and could i just reflash twrp?
Click to expand...
Click to collapse
I think @EddyOS's script does relock the bootloader, which you definitely don't want because once relocked sometimes it won't unlock again. He'll need to confirm that though. It definitely flashes the stock recovery but you can flash TWRP again.
Heisenberg said:
I think @EddyOS's script does relock the bootloader, which you definitely don't want because once relocked sometimes it won't unlock again. He'll need to confirm that though. It definitely flashes the stock recovery but you can flash TWRP again.
Click to expand...
Click to collapse
It doesn't relock, no. I link to a script that does if you want to though
No that's OK I do not want to relock it, thank u both for all ur help
Related
I have to go to uni in 1 hour and updated my bootloader via flashify, now its stuck in bootloader and wont boot. TWRP is the only accesible option for me. Tried to reflash the bootloader via fast boot but nothings happening.
Bootloader : hhz11k
Rom : N5X 5.0 AOSP Ver. 5.4
Wipe cache in TWRP and reboot. If that doesn't work, restore your backup. If THAT doesn't work, flash the factory image when you can get to a PC
EddyOS said:
Wipe cache in TWRP and reboot. If that doesn't work, restore your backup. If THAT doesn't work, flash the factory image when you can get to a PC
Click to expand...
Click to collapse
I'm restoring right now. Doy you know why this happened? Isn't flashify able to flash the bootloader, and if that was the case, shouldn't a flash via fastboot be the solution to my problem?
Anyways thx for your quick answer!
I don't use apps for things I can do manually, I do it all via adb/fastboot
As to why it's happened, not a clue. Also, make sure you're actually using the Nexus 5 images and not from another Nexus device
EddyOS said:
I don't use apps for things I can do manually, I do it all via adb/fastboot
As to why it's happened, not a clue. Also, make sure you're actually using the Nexus 5 images and not from another Nexus device
Click to expand...
Click to collapse
I think the bootloader I flashed is not ment for android 5, thats what happens when you are a lazy **** and try to do important things on your phone...
Now its to late but I wanted to flash Cataclysm anyway
Escoban said:
I think the bootloader I flashed is not ment for android 5, thats what happens when you are a lazy **** and try to do important things on your phone...
Now its to late but I wanted to flash Cataclysm anyway
Click to expand...
Click to collapse
The problem probably is that Flashify doesn't have the functionality to flash bootloaders. It flashes boot image (kernel) Radio and recovery. I bet you flashed a bootloader image to your kernel partition. Lucky you didn't brick
rootSU said:
The problem probably is that Flashify doesn't have the functionality to flash bootloaders. It flashes boot image (kernel) Radio and recovery. I bet you flashed a bootloader image to your kernel partition. Lucky you didn't brick
Click to expand...
Click to collapse
Technically his bootloader would have still been there then to unbrick. Lol
Sent from my Android 5.0 Nexus 5
Ben36 said:
Technically his bootloader would have still been there then to unbrick. Lol
Sent from my Android 5.0 Nexus 5
Click to expand...
Click to collapse
Sometimes unpacking the wrong image in a partition can screw the partition itself up, which wouldn't matter if he had BL or not. Brick doesn't mean wont power up. Brick just means unrepairable without a service centre.
rootSU said:
Sometimes unpacking the wrong image in a partition can screw the partition itself up, which wouldn't matter if he had BL or not. Brick doesn't mean wont power up. Brick just means unrepairable without a service centre.
Click to expand...
Click to collapse
flashify managed to flash the bootloader, the one I flashed just didn#t support android 5. I downloaded the wrong bootloader.
Escoban said:
flashify managed to flash the bootloader, the one I flashed just didn#t support android 5. I downloaded the wrong bootloader.
Click to expand...
Click to collapse
Were you flashing zips instead do you mean?
rootSU said:
The problem probably is that Flashify doesn't have the functionality to flash bootloaders. It flashes boot image (kernel) Radio and recovery. I bet you flashed a bootloader image to your kernel partition. Lucky you didn't brick
Click to expand...
Click to collapse
Glad i said "le'ts google it" before going full wipe, i owe you dude.
I downloaded 5.1 radio and bootloader and flashed them using Flashify, then i got the same problem as OP. Reflashing the kernel fixed it.
*deletes Flashify*
I tried to get rid of root by going into the supersu app and clicking the uninstall option. It then rebooted, but it went into a bootloop. I already wiped multiple times but nothing happened.
Could it be because of xposed being installed?
Thanks.
Was stock recovery used to perform the factory reset?
audit13 said:
Was stock recovery used to perform the factory reset?
Click to expand...
Click to collapse
No, I used TWRP to do it. v2.8.7.0 I think.
Try with stock recovery.
audit13 said:
Try with stock recovery.
Click to expand...
Click to collapse
How would I uninstall TWRP recovery?
Flash the recovery.img file that is included with the stock rom. Fastboot flash recovery recovery.img.
audit13 said:
Flash the recovery.img file that is included with the stock rom. Fastboot flash recovery recovery.img.
Click to expand...
Click to collapse
Hmm, still boot loops. Am I forced to just reflash the fctory image?
Since it still bootloops, I recommend flashing back to a completely stock ROM to make sure the phone still functions properly.
audit13 said:
Since it still bootloops, I recommend flashing back to a completely stock ROM to make sure the phone still functions properly.
Click to expand...
Click to collapse
Dang. I wish I wouldn't have to wipe my files, but there aren't That many important stuff. Thanks.
audit13 said:
Since it still bootloops, I recommend flashing back to a completely stock ROM to make sure the phone still functions properly.
Click to expand...
Click to collapse
Sorry for this, but could you also help me install nonsystemless root? systemless causes trouble with layers so it would be very nice if you could help.
Thanks
Which rom is on the phone? For stock LP, flash supersu from twrp. Many custom mm ROMs are prerooted.
audit13 said:
Which rom is on the phone? For stock LP, flash supersu from twrp. Many custom mm ROMs are prerooted.
Click to expand...
Click to collapse
Wait the nonsystemless root is gotten by just flashing it? I always thought it was the other way.
Thanks so so so much for your help!
Hi, just tried to do this by flashing the old zip trough TWRP, but i always end to boot in recovery, maybe i'm doing something wrong...?
I tried this today and happened the same, i guess you have to clean flash to downgrade.
Also a tip, if you got stuck in recovery and yet cannot decrypt (doesn't ask for password/pin in TWRP), boot to fastboot mode, use the command "fastboot boot <the img file name for twrp>" so that you can boot directly to the img file from your PC. This way it will ask for your password.
Killua96 said:
Hi, just tried to do this by flashing the old zip trough TWRP, but i always end to boot in recovery, maybe i'm doing something wrong...?
Click to expand...
Click to collapse
You might try flashing again when you get booted back to TWRP. That way, you can get 9.01 flashed to both slots if it's not already. No guarantees, but it's worth a try.
maigre said:
You might try flashing again when you get booted back to TWRP. That way, you can get 9.01 flashed to both slots if it's not already. No guarantees, but it's worth a try.
Click to expand...
Click to collapse
I tried this way too but keep getting booted back to TWRP. Even did a wipe of the caches, system and data (not internal storage).
Is there anything I can still try?
jiatern said:
I tried this way too but keep getting booted back to TWRP. Even did a wipe of the caches, system and data (not internal storage).
Is there anything I can still try?
Click to expand...
Click to collapse
Flash Magisk again.
maigre said:
Flash Magisk again.
Click to expand...
Click to collapse
I did as well but it didn't help. Still the same.
jiatern said:
I did as well but it didn't help. Still the same.
Click to expand...
Click to collapse
Backup all your data outside the phone and flash a fastboot rom, it worked with me stuck in fastboot and I got back from that horrible 9.0.2
Killua96 said:
Backup all your data outside the phone and flash a fastboot rom, it worked with me stuck in fastboot and I got back from that horrible 9.0.2
Click to expand...
Click to collapse
Why horrible?
PuCiNhOOO said:
Why horrible?
Click to expand...
Click to collapse
Keyboard continuously crash 'cause the new gesture system, that have longer animations and the recent app one loses the vibration feedback and it' s also a lot confusing.
Anyway you can read the same things in the ota's thread, unfortunately are widespread problems
Killua96 said:
Keyboard continuously crash 'cause the new gesture system, that have longer animations and the recent app one loses the vibration feedback and it' s also a lot confusing.
Anyway you can read the same things in the ota's thread, unfortunately are widespread problems
Click to expand...
Click to collapse
I think they pushed the update too fast from beta to stable... But yes, agree with the gestures bug... Its a fact, but the other stuff is good
Killua96 said:
Backup all your data outside the phone and flash a fastboot rom, it worked with me stuck in fastboot and I got back from that horrible 9.0.2
Click to expand...
Click to collapse
Can you link me to the exact fastboot rom you flashed? Some said I have to use the downgrade zip from OnePlus to Oreo 5.1.1 then only upgrade to 9.0.1. The OP of the fastboot rom said the rom is not for downgrading.
Did you downgrade to Oreo first or directly flash the 9.0.1 fastboot rom?
jiatern said:
Can you link me to the exact fastboot rom you flashed? Some said I have to use the downgrade zip from OnePlus to Oreo 5.1.1 then only upgrade to 9.0.1. The OP of the fastboot rom said the rom is not for downgrading.
Did you downgrade to Oreo first or directly flash the 9.0.1 fastboot rom?
Click to expand...
Click to collapse
I've wiped everything, then downgraded to Pie directly, but I was in a slightly different situation (only fastboot available).
Just to be sure flash the Oreo one and then upgrade to Pie.
With the whole A/B partition layout it should be easier to downgrade too right?
Hey everyone
I first time use Google phone.
This time I bought pixel 3.
I want to ask what will happen to I root and unlocked my phone?
Will it lose its warranty?
Or something can't work?
Because I take Sony phone before
If Sony's phone unlocked then it's camera can't work and lose warranty.
So I want to know what I will lose after unlocking?
Or just relock it and it's ok
Sorry my English is bad.
Root will not void warranty. To get root,. You need to unlock bootloader. Unlocking bootloader resets phone to fresh state. Do that prior to setup. Everything works like normal with root.
noxqzs said:
Root will not void warranty. To get root,. You need to unlock bootloader. Unlocking bootloader resets phone to fresh state. Do that prior to setup. Everything works like normal with root.
Click to expand...
Click to collapse
So if I flash new kernels it's all ok?
And
I flash kernels have to in unlock mode
Then can I relcok after flash custome kernel?
Edemilorhea said:
Then can I relcok after flash custome kernel?
Click to expand...
Click to collapse
Do not relock your phone if it isn't 100 percent stock. You will probably brick it and won't be able to flash it. Why would you want to relock it afterwards?
TonikJDK said:
Do not relock your phone if it isn't 100 percent stock. You will probably brick it and won't be able to flash it. Why would you want to relock it afterwards?
Click to expand...
Click to collapse
Uhh because I just root my phone before when I use Sony phone.
So I can flash custome kernel and not relock and it not make me any trouble？
Is it the same as normal?
If I really want to relock, I have to flash back to original kernal then can be relock?
Sorry I long time haven't do this.
Edemilorhea said:
Uhh because I just root my phone before when I use Sony phone.
So I can flash custome kernel and not relock and it not make me any trouble？
Is it the same as normal?
If I really want to relock, I have to flash back to original kernal then can be relock?
Sorry I long time haven't do this.
Click to expand...
Click to collapse
The only issue with unlocked is that will break Google Pay if you use that. However, almost all custom kernels hide the unlock and Google Pay will be fine. Or if you root with Magisk that will also fix Google Pay
Yes, flash back to stock before you relock it.
Unlocking or relocking will wipe your data, there is no way around that.
TonikJDK said:
The only issue with unlocked is that will break Google Pay if you use that. However, almost all custom kernels hide the unlock and Google Pay will be fine. Or if you root with Magisk that will also fix Google Pay
Yes, flash back to stock before you relock it.
Unlocking or relocking will wipe your data, there is no way around that.
Click to expand...
Click to collapse
Oh I will use Google pay but kernel or magisk can fix, i think that is well, let me backup my files then to try
TonikJDK said:
The only issue with unlocked is that will break Google Pay if you use that. However, almost all custom kernels hide the unlock and Google Pay will be fine. Or if you root with Magisk that will also fix Google Pay
Yes, flash back to stock before you relock it.
Unlocking or relocking will wipe your data, there is no way around that.
Click to expand...
Click to collapse
hello,I have one more question.
is a I flash custom kernel then if I flash Original factory, kernel is original? or still is a custom kernel?
Edemilorhea said:
hello,I have one more question.
is a I flash custom kernel then if I flash Original factory, kernel is original? or still is a custom kernel?
Click to expand...
Click to collapse
You will be back to factory kernel.
TonikJDK said:
You will be back to factory kernel.
Click to expand...
Click to collapse
Oh so i can direct flash original OS, it's all will back be original.
No need to flash back google kernel first.
Question 2
Can I flash out the custom kernel and then directly Flash other custom kernels?
Question 3
Pixel can use xposed?
Really thank you very much.
Give me a big hand
Edemilorhea said:
Oh so i can direct flash original OS, it's all will back be original.
No need to flash back google kernel first.
Question 2
Can I flash out the custom kernel and then directly Flash other custom kernels?
Question 3
Pixel can use xposed?
Really thank you very much.
Give me a big hand
Click to expand...
Click to collapse
1. Yes. Fastbooting the factory image will return you to the stock google kernel. Or, you can just fastboot the boot.img as well.
2. On some of the kernels you can, check with the kernel Dev first. It's always good practice to return to the stock kernel before flashing another custom one.
3. Nope. It's not even working on the P2XL on pie.
Badger50 said:
1. Yes. Fastbooting the factory image will return you to the stock google kernel. Or, you can just fastboot the boot.img as well.
2. On some of the kernels you can, check with the kernel Dev first. It's always good practice to return to the stock kernel before flashing another custom one.
3. Nope. It's not even working on the P2XL on pie.
Click to expand...
Click to collapse
Oh thank you and thanks everyone
But where can i find stock kernel? In the stock.zip?
Edemilorhea said:
Oh thank you and thanks everyone
But where can i find stock kernel? In the stock.zip?
Click to expand...
Click to collapse
Once you extract the factory image, you will see another zip file that has the vendor, system, boot, and other images. The boot.img is the stock kernel and recovery combined.
To go back to Stock from Resurrection using the all in one tool can I just flash the fastboot stock ROM without doing anything special? I tried to do it via the msm tool but got stuck. I did search for this answer but had no luck.
UnicornHub said:
To go back to Stock from Resurrection using the all in one tool can I just flash the fastboot stock ROM without doing anything special? I tried to do it via the msm tool but got stuck. I did search for this answer but had no luck.
Click to expand...
Click to collapse
Yes it work with just flashing fastboot stock rom.
I have not done it but I am sure flashing stock rom via twrp followed by twrp zip (and magisk,if desired) should bring you back to stock. Just to be sure, flash twice to ensure you covered both a/b slots
You need to format data in TWRP then flash OOS in TWRP
Zhuang zhuang said:
You need to format data in TWRP then flash OOS in TWRP
Click to expand...
Click to collapse
I don't have TWRP or root. I lost it after an update.
UnicornHub said:
I don't have TWRP or root. I lost it after an update.
Click to expand...
Click to collapse
If you have PC, you can install TWRP via fastboot easily. I've never used the fastboot rom before, so I don't know about it.