Hi! I recently installed a cm12 nightly on my nexus 5 and now I can't get rid of it ad return back to stock. I tried using nrt and doing it manually but after everything is finished my device doesn't reboot like it's supposed to, it just stays in fastboot mode and when I manually reboot it it boots into cm again and messages pop up saying that system UI has stopped etc so I can't use the device. I tried using force flash mode in nrt and although it did reboot it rebooted in cm again and the same messages pop up.
Any help is appreciated! Thank you!
Did you restore stock kernel?
.
I thought the google factory image would do that? Do i have to do it manually and if yes how do i do it?
ftsagkris said:
I thought the google factory image would do that? Do i have to do it manually and if yes how do i do it?
Click to expand...
Click to collapse
If you are using WugFreshs NRT you can do this within Advanced Utilities - Fastboot Flash - press Boot (Kernel). Restore stock one and then flash stock image.
You can also try if phone will boot up immediately after you restore kernel. If I remember wright, that is enough.
I should also note that when I try to manually install the factory image manually it successfully installs the bootloader the radio and all the other imgs except the system img. It fails to install that
ftsagkris said:
I should also note that when I try to manually install the factory image manually it successfully installs the bootloader the radio and all the other imgs except the system img. It fails to install that
Click to expand...
Click to collapse
It hapeness somethime, but just try again. It also hapenned to me. So. First select your device with current version of android you are using. Leave NRT to update all necessary files. Restore stock kernel. Flash stock image that you downloaded.
You should be ok.
I tried that. When i asked it to download it manually during hashcheck it said mismatched. So I installed it manually and then tried to factory reset with force flash mode off and it said system img was missing. So I enabled force flash and it said it couldn't load system.img. After that it booted in CM again
ftsagkris said:
I tried that. When i asked it to download it manually during hashcheck it said mismatched. So I installed it manually and then tried to factory reset with force flash mode off and it said system img was missing. So I enabled force flash and it said it couldn't load system.img. After that it booted in CM again
Click to expand...
Click to collapse
Hashcheck of what file?
That happened when I pressed boot(kernel) from advanced option. so it was the hashcheck of boot.img when i asked nrt to automatically download it
ftsagkris said:
That happened when I pressed boot(kernel) from advanced option. so it was the hashcheck of boot.img when i asked nrt to automatically download it
Click to expand...
Click to collapse
Pull boot.img from downloaded factory image and flash it.
zagorteney said:
Pull boot.img from downloaded factory image and flash it.
Click to expand...
Click to collapse
Ok. I have already done that. I tried formatting the device and did everything again. I manually installed everything but when I get to system.img I get an error message saying "cannot load system.img"
I also tried re-downloading the factory image from google's site to make sure that I didn't have any corrupted files but the same problem keeps coming up
ftsagkris said:
Ok. I have already done that. I tried formatting the device and did everything again. I manually installed everything but when I get to system.img I get an error message saying "cannot load system.img"
I also tried re-downloading the factory image from google's site to make sure that I didn't have any corrupted files but the same problem keeps coming up
Click to expand...
Click to collapse
Flash bootloader and radio first. Boot in fastboot. Fastboot flash recovery, boot and system. If this doesn't work I don't know how to help you.
Regards, Zagor
zagorteney said:
Flash bootloader and radio first. Boot in fastboot. Fastboot flash recovery, boot and system. If this doesn't work I don't know how to help you.
Regards, Zagor
Click to expand...
Click to collapse
I have done that several times now and it just won't flash system.img
Thank you very much for your help though.
ftsagkris said:
I have done that several times now and it just won't flash system.img
Thank you very much for your help though.
Click to expand...
Click to collapse
After flashing the bootloader/radio, you need to reboot the bootloader.
This is important.
I will put myself in recovery now.
zagorteney said:
After flashing the bootloader/radio, you need to reboot the bootloader.
Click to expand...
Click to collapse
Thank you. I knew that I have read almost every tutorial I could find online. I just did it on my mac and it worked. I don't know why it would't work on my pc.
Thank you very much for your time though!
ftsagkris said:
Thank you. I knew that I have read almost every tutorial I could find online. I just did it on my mac and it worked. I don't know why it would't work on my pc.
Thank you very much for your time though!
Click to expand...
Click to collapse
No problemo. I didn't do anything, but I really hate that things like that, hapeness to people like you.
I just remembered that I have exactly same situation and resolve it that way. That's why I preffered stock from then on.
Regards, Zagor
Related
Sorry, for bothering you with this but unfortunately, I have soft-bricked my phone. It's a WIND Canada HTC One S with S4 cpu, CID is GLOBA001 with HBOOT 1.14.0004.
I had Cyanogenmod 10 installed, ran in some problems, tried to find a solution (among others this: http://forum.xda-developers.com/showthread.php?t=1630459 didn't work) and bricked it: boot loop, unmountable /sdcard, no working recovery. I have tried for hours all the tips I found in the forums but none helped. I even downloaded a RUU but I couldn't install it (probably the wrong version).
Current state is: I can only get into the bootloader which is re-locked (by courtesy of one of my repair attempts). Connecting via USB to fastboot works. Nothing else, for all purposes the phone is clean, empty and oh so very much dead.
How do I proceed from here? In the end I want to have working version of Cyanogenmod back.
Thank you in advance, guys!
el_Harmakhis said:
Sorry, for bothering you with this but unfortunately, I have soft-bricked my phone. It's a WIND Canada HTC One S with S4 cpu, CID is GLOBA001 with HBOOT 1.14.0004.
I had Cyanogenmod 10 installed, ran in some problems, tried to find a solution (among others this: http://forum.xda-developers.com/showthread.php?t=1630459 didn't work) and bricked it: boot loop, unmountable /sdcard, no working recovery. I have tried for hours all the tips I found in the forums but none helped. I even downloaded a RUU but I couldn't install it (probably the wrong version).
Current state is: I can only get into the bootloader which is re-locked (by courtesy of one of my repair attempts). Connecting via USB to fastboot works. Nothing else, for all purposes the phone is clean, empty and oh so very much dead.
How do I proceed from here? In the end I want to have working version of Cyanogenmod back.
Thank you in advance, guys!
Click to expand...
Click to collapse
Unlock it first, you can't do anything with it locked.
Darknites said:
Unlock it first, you can't do anything with it locked.
Click to expand...
Click to collapse
Okay, the device is unlocked again. How do I continue?
Thanks a lot, by the way!
el_Harmakhis said:
Okay, the device is unlocked again. How do I continue?
Thanks a lot, by the way!
Click to expand...
Click to collapse
Flash TWRP recovery and try to mount the sd and connect it to the pc.
Darknites said:
Flash TWRP recovery and try to mount the sd and connect it to the pc.
Click to expand...
Click to collapse
Okay, flashing TWRP worked. I then booted into recovery, clicked on "mount" and then "mount usb device". After some driver installs I can no see the internal storage. Apart from a folder for TWRP and .android_secure it's empty. Is this where I now put the Cyanogenmod file and install it via the recovery?
el_Harmakhis said:
Okay, flashing TWRP worked. I then booted into recovery, clicked on "mount" and then "mount usb device". After some driver installs I can no see the internal storage. Apart from a folder for TWRP and .android_secure it's empty. Is this where I now put the Cyanogenmod file and install it via the recovery?
Click to expand...
Click to collapse
Ya place it where you want and then flash it but you will need to fastboot the boot.img file thats in the rom zip, you can use the All-In-One Toolkit to do that.
Darknites said:
Ya place it where you want and then flash it but you will need to fastboot the boot.img file thats in the rom zip, you can use the All-In-One Toolkit to do that.
Click to expand...
Click to collapse
Copying the ROM and then installing via TWRP worked though I saw that TWRP displayed an error, saying it was unable to mount /cache. When I tried to wipe the Cache & Dalvik Cache I got the same error.
Nevertheless I then went ahead and copyed the boot.img (extracted that one from the Cyanogenmod zip) via fastboot and rebooted the device. Now the phone is stuck in the Cyanogenmod boot loop.
el_Harmakhis said:
Copying the ROM and then installing via TWRP worked though I saw that TWRP displayed an error, saying it was unable to mount /cache. When I tried to wipe the Cache & Dalvik Cache I got the same error.
Nevertheless I then went ahead and copyed the boot.img (extracted that one from the Cyanogenmod zip) via fastboot and rebooted the device. Now the phone is stuck in the Cyanogenmod boot loop.
Click to expand...
Click to collapse
Hmm think you going to have flash the stock recovery then do a factory reset in the bootloader then go back to TWRP and copy over the rom again then factory reset in TWRP and then wipe system and then flash the rom. Do not lock the bootloader.
Darknites said:
Hmm think you going to have flash the stock recovery then do a factory reset in the bootloader then go back to TWRP and copy over the rom again then factory reset in TWRP and then wipe system and then flash the rom. Do not lock the bootloader.
Click to expand...
Click to collapse
Okay, I will try that! Where might I get the stock recovery? I don't want to pick the wrong!
el_Harmakhis said:
Okay, I will try that! Where might I get the stock recovery? I don't want to pick the wrong!
Click to expand...
Click to collapse
Go here for it.
Darknites said:
Go here for it.
Click to expand...
Click to collapse
Ha! It finally worked! Thank you very much! Have a nice weekend!
el_Harmakhis said:
Ha! It finally worked! Thank you very much! Have a nice weekend!
Click to expand...
Click to collapse
Np dude, you too.
LG D821 16GB after power on continue rebooting with Google logo..
I flashed factory image successfully except image version 5.
any help here?
Make sure you're using the latest adb/fastboot files from the SDK
Have you tried to remove the erase userdata flag and then running it? Or maybe you'll need to flash each image individually as some people are doing.
srkhan said:
LG D821 16GB after power on continue rebooting with Google logo..
I flashed factory image successfully except image version 5.
any help here?
Click to expand...
Click to collapse
I also had the same error last night. Just wipe data/factory reset from stock recovery and reboot.
varuntis1993 said:
I also had the same error last night. Just wipe data/factory reset from stock recovery and reboot.
Click to expand...
Click to collapse
not solved
srkhan said:
not solved
Click to expand...
Click to collapse
Have you done what I said?
srkhan said:
not solved
Click to expand...
Click to collapse
are you trying to flash again? No need to if u are doing that.You have flashed, now go into stock recovery and just wipe and reboot the phone. That did it for me.
Can't say whether its an issue with old fastboot files or not because I have setup my device after flashing 4 times with that error and dont want to flash it again just now. In case it matters I had no issue with flashing flo , but got that error with hammerhead.
Do what @EddyOS says. Maybe that's the issue.
Flashing/Booting up L for the first time takes a lot more time than previous Android versions, as ART pre-compiles everything. Give it time, just let it boot. If you used flash-all, you'll be fine.
varuntis1993 said:
are you trying to flash again? No need to if u are doing that.You have flashed, now go into stock recovery and just wipe and reboot the phone. That did it for me.
Can't say whether its an issue with old fastboot files or not because I have setup my device after flashing 4 times with that error and dont want to flash it again just now. In case it matters I had no issue with flashing flo , but got that error with hammerhead.
Do what @EddyOS says. Maybe that's the issue.
Click to expand...
Click to collapse
recovery and just wipe and reboot the phone. That did not work for me.
beekay201 said:
Flashing/Booting up L for the first time takes a lot more time than previous Android versions, as ART pre-compiles everything. Give it time, just let it boot. If you used flash-all, you'll be fine.
Click to expand...
Click to collapse
i flashed all . but still rebooting after Google logo with a lock sign bottom of the screen.
Hey Guys. Im running cm12s on my oneplus one, and i would like to switch to oxygenOS because they are getting the touchscreen firmware fixes. Ive flashed recoveries onto multiple phones without this issue before.
I downloaded twrp, booted the phone into fastboot, unlocked it, got the success signal, flashed it, again, success, and then rebooted. Then i powered down and booted to recovery aaaand..... stock recovery. WTF? So i wipe all user data and clear the cache with the stock recovery and try again. Nope. Its still the stock recovery. i dont understand it. I tried with CWM aswell. It says success, so why did it not work? I booted into the OS and checked developer settings, and disabled update recovery and all that, Nevertheless, when i flash TWRP or CWM, it does not work. I dont understand how this could happen.
I followed the steps from the Official guide on the official oneplus forum, It wont let me post a link.
I am using an OEM samsung cable.
Can anyone help me?
fastboot reboot-bootloader ; just after recovery flash.
Orphee said:
fastboot reboot-bootloader ; just after recovery flash.
Click to expand...
Click to collapse
Alright, I've just tried that. After flashing it, i Ran this command and as expected it rebooted back to the bootloader. Nothing else todo there, so i rebooted and booted to the recovery. It STILL boots to the stock recovery! So i tried again, but this time, i flashed it a second time after rebooting to the bootloader, but that still has not worked. is my unit defective? I will try now with another computer.
Read the FAQ:
http://forum.xda-developers.com/oneplus-one/help/faq-oneplus-one-frequently-questions-t2895136
XDA Moderator
Transmitted via Bacon
I figured it out!
I figured it out. Instead of rebooting after flashing the custom recovery and allowing cyanogen to re write it, i simply turned the phone off and booted directly to recovery and sure enough, TWRP. Problem solved. I dont understand why cyanogen would do that to me and not anyone else!
theangrynoob5 said:
I figured it out. Instead of rebooting after flashing the custom recovery and allowing cyanogen to re write it, i simply turned the phone off and booted directly to recovery and sure enough, TWRP. Problem solved. I dont understand why cyanogen would do that to me and not anyone else!
Click to expand...
Click to collapse
CM didn't just do that to you, it's happened to every single person who's tried to flash TWRP after taking the Lollipop update, that's why the question is included in the FAQ thread.
XDA Moderator
Transmitted via Bacon
Hello, my tablet seems to be stuck in a boot loop and i've tried flashing the recovery and supersu again to no avail. I've also tried that exitrecovery zip floating around. I think I might have flashed a kernel by accident want trying to root.
Background
Tried using WinDroid Universal Android ToolKit. <- was successful in unlocking bootloader only. tried various times to install twrp but nothing would happen. The "recovery mode" in BL would just show android with caution triangle. I then used WinDroid's "commands" section to try and flash recovery. I may have flashed kernel instead? I have CWM 6.0.5.0. Help would be appreciated. This is what i get for trying to take the easy way out -_-.
Update: I tried "SHIELD TABLET RECOVERY IMAGE FLASHING INSTRUCTIONS" from nvidia itself and now it just hangs in the nvidia logo screen forever. I tried both the "flash-all.bat" and the manual line by line one. any clues?
If someone could tell me how to just make the wipe the whole thing i wouldn't mind restarting to root properly.
Any one got any info? =D
Cveezy said:
Any one got any info? =D
Click to expand...
Click to collapse
Its not hard, just restore it back to factory, a couple of quick google searches:
https://developer.nvidia.com/sites/...s/HowTo-Flash-SHIELDTablet-Recovery-Image.txt
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
When you download the images make sure you do a MD5 on them.
The good news its very hard to kill this tablet, and very easy to unlock/flash/root.
jpierson said:
Its not hard, just restore it back to factory, a couple of quick google searches:
https://developer.nvidia.com/sites/...s/HowTo-Flash-SHIELDTablet-Recovery-Image.txt
http://forum.xda-developers.com/shi...k-recovery-images-ota-library-guides-t2988881
When you download the images make sure you do a MD5 on them.
The good news its very hard to kill this tablet, and very easy to unlock/flash/root.
Click to expand...
Click to collapse
I tried flashing and doing a full OTA rom install to no avail. I however unsure what MD5 is and would that have a effect on my outcome.
Cveezy said:
I tried flashing and doing a full OTA rom install to no avail. I however unsure what MD5 is and would that have a effect on my outcome.
Click to expand...
Click to collapse
You restored the recovery, boot, system, and userdata per the instructions and it still boot loops?
Check out this post:
http://forum.xda-developers.com/shield-tablet/help/help-stuck-nvidia-boot-screen-t3076462
jpierson said:
You restored the recovery, boot, system, and userdata per the instructions and it still boot loops?
Check out this post:
http://forum.xda-developers.com/shield-tablet/help/help-stuck-nvidia-boot-screen-t3076462
Click to expand...
Click to collapse
Yeah, its werid that its still stuck. I have tried doing it both way manual tell adb each file to flash and through the flash-all.bat way as well. Im going to try the link you sent in a bit.
How long did you let it sit at the boot logo? If you are booting on a clean install it may take a bit longer.
Just download and use fastboot (fastboot flash recovery image.img) to flash twrp. I'd suggest using adb/fastboot anyway since it's simple enough and a good thing to learn if you plan on doing this sort of thing. After that you can just flash from there. The ota zips, super su, etc. and wipe.
Ok so never mind i got into teamwin TWRP phew. But Alpha2 but isn't it suggested that you don't recover using twrp? I don't know what to DO.
silvernirvash said:
Ok so never mind i got into teamwin TWRP phew. But Alpha2 but isn't it suggested that you don't recover using twrp? I don't know what to DO.
Click to expand...
Click to collapse
Download TWRP RC1 and flash it with TWRP alpha. Then download PN and follow the flashing instructions OR use your PC to flash back to stock and start over.
Edit: if you've made a backup using TWRP alpha, you can try to restore it using TWRP alpha.
k.s.deviate said:
Download TWRP RC2 and flash it with TWRP alpha. Then download PN and follow the flashing instructions OR use your PC to flash back to stock and start over.
Edit: if you've made a backup using TWRP alpha, you can try to restore it using TWRP alpha.
Click to expand...
Click to collapse
I don't have ADB or USB debugging enabled on my device. I can't DO anything. And i go and mount my storage onto my PC it just shows a **** ton of folders with random letters and numbers. i can't copy any files onto the device nor will minimal ADB and fastboot work when i type adb devices to detect the device. i don't know what to do!
silvernirvash said:
I don't have ADB or USB debugging enabled on my device. I can't DO anything. And i go and mount my storage onto my PC it just shows a **** ton of folders with random letters and numbers. i can't copy any files onto the device nor will minimal ADB and fastboot work when i type adb devices to detect the device. i don't know what to do!
Click to expand...
Click to collapse
ADB debugging does not need to be enabled on the device. All fastboot commands will work when you're in bootloader.
The files/folders with random names are showing up because TWRP didn't decrypt properly, reboot TWRP until the files/folders show up properly on the device then the files will show up properly on your PC and enable you to transfer files.
What's the background here, were you running stock rooted or a custom ROM?
k.s.deviate said:
ADB debugging does not need to be enabled on the device. All fastboot commands will work when you're in bootloader.
The files/folders with random names are showing up because TWRP didn't decrypt properly, reboot TWRP until the files/folders show up properly on the device then the files will show up properly on your PC and enable you to transfer files.
What's the background here, were you running stock rooted or a custom ROM?
Click to expand...
Click to collapse
stock rooted with substratum installed. i had a substratum theme that worked for the most part perfectly fine but then i found orange kittens and the colored kittens addon to change the color to something i wanted people told me it would work just fine on the pixel 7.1 and when it rebooted BAM bootloop. i didn't have adb or usb debugging enabled when i did it and i wasn't thinking because i've done this kinda stuff in the past so i thought i'd be fine. but i guess i wans't.
k.s.deviate said:
ADB debugging does not need to be enabled on the device. All fastboot commands will work when you're in bootloader.
The files/folders with random names are showing up because TWRP didn't decrypt properly, reboot TWRP until the files/folders show up properly on the device then the files will show up properly on your PC and enable you to transfer files.
What's the background here, were you running stock rooted or a custom ROM?
Click to expand...
Click to collapse
I GOT ACCESS TO MY FILES AGAIN! I THINK I CAN MOVE STUFF OVER TO IT PERFECTLY NOW! Oh so could i just copy over the stock 7.1 zip flash it with twrp and i'll be set? or should i just flash the latest OTA update image? and whichever i have to do do i do it using the install option or do i do it using the advanced ADB sideload?
also what is PN? i'm confused by that one.
silvernirvash said:
stock rooted with substratum installed. i had a substratum theme that worked for the most part perfectly fine but then i found orange kittens and the colored kittens addon to change the color to something i wanted people told me it would work just fine on the pixel 7.1 and when it rebooted BAM bootloop. i didn't have adb or usb debugging enabled when i did it and i wasn't thinking because i've done this kinda stuff in the past so i thought i'd be fine. but i guess i wans't.
Click to expand...
Click to collapse
ok, bootloop form theme. After TWRP has successfully decrypted, this might take a few reboots.. Go to sd card, you will see a folder named Substratum, in there are two zip files, flash the SubstratumRescue_Legacy.zip then reboot.
IF that does not work, go back into TWRP and go to mount - system. back out and go to advanced - file manager navigate to /system/vendor/overlay and delete the entire folder. Ive done that only once on the Pixel, you might have to go to /system/system/vendor/overlay and delete the folder then reboot.
silvernirvash said:
I GOT ACCESS TO MY FILES AGAIN! I THINK I CAN MOVE STUFF OVER TO IT PERFECTLY NOW! Oh so could i just copy over the stock 7.1 zip flash it with twrp and i'll be set? or should i just flash the latest OTA update image? and whichever i have to do do i do it using the install option or do i do it using the advanced ADB sideload?
Click to expand...
Click to collapse
That is interesting, my first experience with the Pixel I had bought it close to when Best Buy was closing (they were offering the $10.00/month promotion) and the device had not finished updating. However, the person checking me out let me go before it had completely finished and said it "will finish the updates shortly and be usable". Well, i guess in his haste to get blackout drunk and attempt lame pick up lines, he did something wrong. After the update finished, The phone was stuck in a constant boot loop. My first experience with my beloved Pixel was a nightmare. Of course, I had it replaced with a new one in the store the next day, but it was very strange. I had not even got into the OS at all and it was stuck in this strange bootloop.
Glad your situation worked out, when I saw the title to this post my heart sunk a little bit because I certainly know the look.
silvernirvash said:
I GOT ACCESS TO MY FILES AGAIN! I THINK I CAN MOVE STUFF OVER TO IT PERFECTLY NOW! Oh so could i just copy over the stock 7.1 zip flash it with twrp and i'll be set? or should i just flash the latest OTA update image? and whichever i have to do do i do it using the install option or do i do it using the advanced ADB sideload?
Click to expand...
Click to collapse
No, just read my post and see if that works.
k.s.deviate said:
ok, bootloop form theme. After TWRP has successfully decrypted, this might take a few reboots.. Go to sd card, you will see a folder named Substratum, in there are two zip files, flash the SubstratumRescue_Legacy.zip then reboot.
IF that does not work, go back into TWRP and go to mount - system. back out and go to advanced - file manager navigate to /system/vendor/overlay and delete the entire folder. Ive done that only once on the Pixel, you might have to go to /system/system/vendor/overlay and delete the folder then reboot.
Click to expand...
Click to collapse
ZOMG it rebooted! i already did a restore so i have to set up my phone again in terms of apps and stuff but that's fine. but now it keeps saying android.process.acore keeps stopping. i'm assuming it has to do with the substratum theme and i guess that means i should just delete that folder huh?
silvernirvash said:
ZOMG it rebooted! i already did a restore so i have to set up my phone again in terms of apps and stuff but that's fine. but now it keeps saying android.process.acore keeps stopping. i'm assuming it has to do with the substratum theme and i guess that means i should just delete that folder huh?
Click to expand...
Click to collapse
How did you restore? I've never seen that process stop before.
It might be best to (since you have to set up your apps again) flash a factory image and start over.
---------- Post added at 05:02 AM ---------- Previous post was at 04:56 AM ----------
And if your going to be playing with themes.. PN is the way to go. PN is Pure Nexus rom. Follow the instructions word for word and you won't have any troubles. It is as stable as stock with some extra goodness baked in.
k.s.deviate said:
How did you restore? I've never seen that process stop before.
It might be best to (since you have to set up your apps again) flash a factory image and start over.
Click to expand...
Click to collapse
oh i did a quick cache and data wipe. it's what you're supposed to do when flashing new or updated roms in the first place. at the top right of TWRP it says wipe. i thought that would restore it back to default settings including substratum theme application but it seems all it did was set me back to stock settings with apps uninstalled lol. gotta set up my device again sadly. but now like i said now i keep getting this stupid android.process..acore keeps crashing error.
and i restored using the legacy zip you told me to use in the substratum folder using the install option at the top left.
Just hit the thanks button. ?
and by recovering i lost root....great....now i need to reroot.....damn it all =w=;;
k.s.deviate said:
Just hit the thanks button.
Click to expand...
Click to collapse
oh hey can i download and flash the latest version of android 7.1.1 manually using TWRP with out losing TWPR or my locked bootloader? just curious. i'm about to go back and reroot but i know updating to 7.1.1 = losing root and requiring me to root again after the fact which is why i'm holding off for NOW until i get an answer.
silvernirvash said:
oh hey can i download and flash the latest version of android 7.1.1 manually using TWRP with out losing TWPR or my locked bootloader? just curious. i'm about to go back and reroot but i know updating to 7.1.1 = losing root and requiring me to root again after the fact which is why i'm holding off for NOW until i get an answer.
Click to expand...
Click to collapse
No you can't flash factory images using TWRP, I would however highly suggest flashing the factory image to stop that crashing process.
k.s.deviate said:
No you can't flash factory images using TWRP, I would however highly suggest flashing the factory image to stop that crashing process.
Click to expand...
Click to collapse
so i gotta flash using minimal adb and fastboot huh? :/ damn lol. wouldn't that in turn remove TWRP tho? or am i mistaken on that one?
silvernirvash said:
so i gotta flash using minimal adb and fastboot huh? :/ damn lol. wouldn't that in turn remove TWRP tho? or am i mistaken on that one?
Click to expand...
Click to collapse
It would remove TWRP, but after the flash-all.bat is done.. set up your phone. Reboot to bootloader, fastboot boot TWRP install TWRP via zip and flash super su.
Then going forward to update every month, download the newest factory image, right click on the flash-all.bat click edit, scroll over and remove the -w. Then boot into bootloader and run the flash-all.bat, when it's done your still in bootloader, fastboot boot TWRP, flash TWRP zip and flash super su. Reboot.
k.s.deviate said:
It would remove TWRP, but after the flash-all.bat is done.. set up your phone. Reboot to bootloader, fastboot boot TWRP install TWRP via zip and flash super su.
Then going forward to update every month, download the newest factory image, right click on the flash-all.bat click edit, scroll over and remove the -w. Then boot into bootloader and run the flash-all.bat, when it's done your still in bootloader, fastboot boot TWRP, flash TWRP zip and flash super su. Reboot.
Click to expand...
Click to collapse
this would in fact wipe my phone every time i do it tho right? like EVERYTHING including music and photos and stuff right?