Related
i tried to update via phone (after the notification), but after green bar was full, my phone rebooted and stuck in white screen with htc logo... if i try to enter in recovery i see this
h*tp://i39.tinypic.com/xdxnc5.jpg
it seems to be s-off (i bought it used) ...what have i to do for make it work again??
tnx.. and sorry for my bad english
same problem here, help is needed!
A golden rule: never update OTA on a modified device (custom ROM even modified Stock one, custom Recovery, Revolutionary hboot!, etc.)
How to fix:
do not pull battery!
flash a custom recovery (e.g. 4EXT) with the fastboot command (search for a how-to)
reboot to recovery, wipe all partitions and install custom ROM
Ok, to late with the battery, have already pulled that one out!
I also have S-Off on my phone, really dont understand the how to fix a recovery??
And is it really neccessary to flash a new ROM for this?
An official release that screwes the phones up?
I think the general issue is that an 'Official' OTA upgrade should not screw up your phone - enough testing by HTC should make sure of that.
Hoever, if you have modified your phone (e.g. by rooting it, installing custom recovery etc) then you can not expect to blame HTC when their upgrade doesn't work as expected. They can't be held responsible for problems caused by modifications you make to the phone.
But all I have done is S-Off, I have not installed another ROM or anything else?
So the update should work I really think!
Can I install a custom recovery without have to be able to start the phone?
Akerhage said:
But all I have done is S-Off, I have not installed another ROM or anything else?
So the update should work I really think!
Can I install a custom recovery without have to be able to start the phone?
Click to expand...
Click to collapse
The OTA flashes a new hboot also.
If you S-OFFed with Revolutionary your hboot has to be version 6.98.000x. This hboot has a protection and cannot be overwritten. This is the point where the update process is interrupted. The result is a bootloop, because the new system is incomplete.
If you can boot to bootloader (hboot) you should be able to flash a custom recovery with the fastboot command (in the 4EXT Recovery thread there is an attachement - a zip file that contains recovery.img). Extract the archive and flash it with this command from cmd (there is a guide how to make fastboot working in my signature):
Code:
fastboot flash recovery {path to file on your PC}/recovery.img
If this works reboot to recovery, wipe all partitions and flash a custom ROM. Then your phone should be working again.
Then if you want the OTA flash a 0.98.2000 hboot, then use the 1.47.401.4 RUU (if you are using European unbranded) or the corresponding for your brand/region to return back to complete Stock and S-ON. Then you will be prompted to update and you will have the latest OTA on your device
Okay, I have now fixed the 4EXT Recovery and it is working!
Do I have to put a new ROM on the SD-card or is there another way to install a ROM (from cmd with the ROM on the computer etc?)
I dont have an adapter to the SD-card, but maybe I can put the ROM on the sdcard with a command in cmd aswell?
What ROM do you recommend to use? (sense, no sense doesnt matter)
Edit: I did a backup as well, thinking that I should do that...
Can you link to zip file you used for recovery i have exactly same issue and same software versions as you have.
@ Mooler. First of follow the guide that was posted here regarding the adb-drivers.
After that download this: http://forum.xda-developers.com/attachment.php?attachmentid=631186&d=1308596026
Then install that one as described with the cmd-command.
After that just put a custom ROM or a shipped ROM on the SD-card, wipe data/cache and install the ROM you want. That solved the problem for me!
Good Luck and thanks for the help I got here! Xda always delivers
Damn this phone! After hours of fixing with this problem!
I managed great, installed new kernels, radios, ROMs etc. And the first thing I did was to drop it on the floor so the whole damn display cracked!
Thanks for both of you.
I managed to restore the phone quickly after i got the correct recovery file. 30 mins and custom ROM was up and running. Good bye official update.
Akerhage: sad to here, it really was hours of reading and trying before you get it right.
I found this thread and since i am a newbie when i read it a few questions came on my mind
Alternative Firmware update Method
1. Decompress downloaded .zip file (it will be another .zip)
2. Rename it to EP201_768_SDUPDATE.zip
3. Format FAT32 the MicroSD card that you will be using for the update process
4. Copy the file to (the root directory of) your MicroSD
5. Insert it into the tablet
6. Shutdown (power off) the tablet
7. Power it on by pressing and holding VOLUME DOWN and POWER buttons simultaneously
8. When you see white text in the top left corner of the screen, release the buttons ^^ and press VOLUME UP button until you see Android logo and process bar
9. Wait patiently for 10 minutes or so
10. Enjoy!
Also remember that you will probably need to use RootKeeper to regain root privileges and reinstall BusyBox too (firmware update changes the /system partition).
That's the thread i have read and the questions that came to my mind are:
1.Do i use the same method for any update?
2.Is it a safe way to update my firmware because after you unlock bootloader no OTA update but only manual update is possible.So is this the right way to manually update any version of firmware update from now on?
3.Is there any other way to manually update my Asus?
4.Do i have to follow another way of installing the update because of the custom recovery that i have installed? (TWRP)
5.If i format the SD Card using exFAT will this method work or not?
I appreciate any help you could give me since i am a noob and some things seem really scary to me due to the fear of bricking my device,
Thank you in advance for your patience reading my questions:angel:
Help with OTA
Dino,
I have a few quesitons for you (just to verify).
Is your boot loader unlocked?
If so, are you running a custom recovery?
If not, then why don't you just use the over the air update?
If your boot loader is unlocked, and you are running a custom recovery (which I understand you are), then yes, you will likely need to update from SD Card from here on out. Once you unlock the boot loader you can no longer get OTA updates. I would recommend following this thread: http://forum.xda-developers.com/showthread.php?t=1915079
If you are already rooted then you can use SuperSU, and OTA Rootkeeper to regain root after the update. There are tons of threads that discuss this. If you are doing root for the first time, you should read this: http://forum.xda-developers.com/showthread.php?t=1916762
The SD Card format needs to be FAT32. In regards to being a "noob" and scared, you should be. Did you make a recovery image using NvFlash before you touched your tablet in the first place? If not, then I would recommend that once you get to JB that you never attempt to load anything on your tablet ever again, at least not until you are no longer a "noob", and you are understanding and accepting of the fact that you may hard brick your tablet some day.
dinothenino said:
I found this thread and since i am a newbie when i read it a few questions came on my mind
Alternative Firmware update Method
1. Decompress downloaded .zip file (it will be another .zip)
2. Rename it to EP201_768_SDUPDATE.zip
3. Format FAT32 the MicroSD card that you will be using for the update process
4. Copy the file to (the root directory of) your MicroSD
5. Insert it into the tablet
6. Shutdown (power off) the tablet
7. Power it on by pressing and holding VOLUME DOWN and POWER buttons simultaneously
8. When you see white text in the top left corner of the screen, release the buttons ^^ and press VOLUME UP button until you see Android logo and process bar
9. Wait patiently for 10 minutes or so
10. Enjoy!
Also remember that you will probably need to use RootKeeper to regain root privileges and reinstall BusyBox too (firmware update changes the /system partition).
That's the thread i have read and the questions that came to my mind are:
1.Do i use the same method for any update?
2.Is it a safe way to update my firmware because after you unlock bootloader no OTA update but only manual update is possible.So is this the right way to manually update any version of firmware update from now on?
3.Is there any other way to manually update my Asus?
4.Do i have to follow another way of installing the update because of the custom recovery that i have installed? (TWRP)
5.If i format the SD Card using exFAT will this method work or not?
I appreciate any help you could give me since i am a noob and some things seem really scary to me due to the fear of bricking my device,
Thank you in advance for your patience reading my questions:angel:
Click to expand...
Click to collapse
droidhaxxor said:
Dino,
I have a few quesitons for you (just to verify).
Is your boot loader unlocked?
If so, are you running a custom recovery?
If not, then why don't you just use the over the air update?
If your boot loader is unlocked, and you are running a custom recovery (which I understand you are), then yes, you will likely need to update from SD Card from here on out. Once you unlock the boot loader you can no longer get OTA updates. I would recommend following this thread: http://forum.xda-developers.com/showthread.php?t=1915079
If you are already rooted then you can use SuperSU, and OTA Rootkeeper to regain root after the update. There are tons of threads that discuss this. If you are doing root for the first time, you should read this: http://forum.xda-developers.com/showthread.php?t=1916762
The SD Card format needs to be FAT32. In regards to being a "noob" and scared, you should be. Did you make a recovery image using NvFlash before you touched your tablet in the first place? If not, then I would recommend that once you get to JB that you never attempt to load anything on your tablet ever again, at least not until you are no longer a "noob", and you are understanding and accepting of the fact that you may hard brick your tablet some day.
Click to expand...
Click to collapse
Thank you very much for your kind reply.I am rooted but still have not unlocked Bootloader. After i've read several threads i was too scared to unlock my bootloader,that's why i was waiting for some answers in order to do it. Basically the only reason for me to unlock the bootloader is the fact that i can keep a backup of my whole device (nandroid if i say it correctly) by using a custom recovery, that's it and that is for me the only reason to do it. I am not interested in flashing custom ROMs just Backup my device.
So what is your suggestion for me to do, with the fact in mind that i want to backup my device.
As for the other thing that you mentioned "nVFlash" i don't know how to do it and although i have read some threads about it i am still very confused how to do it. If you could guide me through it, in simple steps, i would be very grateful. I am on .26 version if that helps.
So to sum up,I got my Asus rooted, locked bootloader, firmware version .26, stock recovery, help is always appreciated !!!
Thank you again in advance,
dinothenino said:
Basically the only reason for me to unlock the bootloader is the fact that i can keep a backup of my whole device (nandroid if i say it correctly) by using a custom recovery, that's it and that is for me the only reason to do it. I am not interested in flashing custom ROMs just Backup my device.
So what is your suggestion for me to do, with the fact in mind that i want to backup my device.
Click to expand...
Click to collapse
If you really just want to backup all your apps and your data, you do not need to unlock or install a custom recovery at all. Just use something like Titanium Backup and that's it. Everything else (kernel, system and recovery) can be restored from the official Asus firmware image.
dinothenino said:
So to sum up,I got my Asus rooted, locked bootloader, firmware version .26, stock recovery,
Click to expand...
Click to collapse
That's exactly the same as I have (locked, rooted, .26), and I am still not sure whether I want to unlock my bootloader and void my warranty. I am at least interested in trying some custom ROMs later, but first I need to understand what exactly the locked bootloader prevents me to do (flashing and loading custom recovery/kernel images and using fastboot - anything else?).
_that said:
If you really just want to backup all your apps and your data, you do not need to unlock or install a custom recovery at all. Just use something like Titanium Backup and that's it. Everything else (kernel, system and recovery) can be restored from the official Asus firmware image.
That's exactly the same as I have (locked, rooted, .26), and I am still not sure whether I want to unlock my bootloader and void my warranty. I am at least interested in trying some custom ROMs later, but first I need to understand what exactly the locked bootloader prevents me to do (flashing and loading custom recovery/kernel images and using fastboot - anything else?).
Click to expand...
Click to collapse
You pretty much say it all, with unlocked bootloader, you could flash, custom recovery, kernel, rom, using fastboot, scripts excepted for boot animation for now, cause you need a kernel that supporting it, once we have a custom kernel that support boot animation, you could do that too.
Back to the OP topic, if you have locked bootloader, rooted and running .26 build, you have 2 options to upgrade, but first make sure you read the thread about how to make a backup of your bootloader using NVFLASH before upgrade to .30 or JB. This is extremely important and since you're still at .26, consider yourself a lucky one. Next make sure you have Voodoo OTA installed and make a backup of your root. Also verify that indeed you do have root by download "root checker" from the market. Also use Titinum backup and backup your device. Finally, you have 2 easy options to upgrade.
A. OTA,(incremental upgrade), automatic download and upgrade your device push out by Asus.(No brainer)
B. Manual upgrade, if you prefer to do a full version (fresh install). It is recommended that you do a factory reset before and after the upgrade.
1) Download the correct latest firmware from Asus site, for JB the firmware called US_epad_user_10_4_4_16_UpdateLauncher.zip (this is US version).
2) Extract the .zip file, it will be another .zip file. This zip named EP201_768_SDUPDATE.zip.
3) Copy the file EP201_768_SDUPDATE.zip from your PC to the root of your MicroSD card.
4) Insert the MicroSD card in your tablet and use this button combination to go to recovery --> Start the tablet by pressing Volume Down and POWER together for 5 seconds ,a message will inform you that you have 5 seconds to enter the recovery,press Volume UP before the 5 seconds expire. At this point the device will go in recovery and should start updating your firmware.
5. If you upgrade from .30 to JB, you could skip step 4 and after step 3, just reboot your device and it should find and prompt you to update.
Thats it ..profit!!
There are couple more, but mainly used if you soft brick or issue, like extract the blog file from Asus download and use fastboot to push etc..but I don't think we need that right now.
I'd like to know more about the details of using fastboot and the blob file. Can you link me to a thread that shows that?
johnlgalt said:
I'd like to know more about the details of using fastboot and the blob file. Can you link me to a thread that shows that?
Click to expand...
Click to collapse
Here you go:
http://forum.xda-developers.com/showthread.php?t=1915598
I found that using fastboot from your pc is working bit better.
Actually, quite funny as I was just reading that. I'm attempting to downgrade to 9.4.5.30 now so I can root and then Keep Root and then re-upgrade and see if I can repair root.
I suppose this would be a bad time to think about 'blobbing' the tablet to JB
I would be more worried about the process except for the fact that I checked the binary-script file and all it does it put the blob on the device. No stupid patching like in Motorola devices. Makes like easier to deal with (in terms of applying updates) but a heck of a lot more bandwidth used (in terms of OTAs).
Speaking of which, are the OTAs the same files, full on blob installs, or are they patches? Just curious....
johnlgalt said:
Speaking of which, are the OTAs the same files, full on blob installs, or are they patches? Just curious....
Click to expand...
Click to collapse
The OTAs contain patches for files in /system, and a blob for kernel, bootloader, recovery (EBT, SOS, LNX).
Hey guys I apologize if this has been answered, I searched but found nothing that addressed my question directly.
My friend decided I should root my One X, the problem is he used an old Clockwork Mod that is no longer supported. What I need to do now is unroot my phone because I'm having nothing but problems with this Rom. From what I understand from videos and everything else is I need to lock the bootloader and flash the stock rom. The issue I have is every guide I've come across so far all start out with "Only use this guide if you first rooted your phone using this method [insert author's rooting guide here]!"
Needless to say, I didn't use any of their methods. I've looked through the guides here and I see various recovery options, I'm just concerned about replacing my recovery tool. Any help or direction would be greatly appreciated!
If you want to go back to stock non rooted Sense, relock your bootloader and run a ruu. Check here for more info http://forum.xda-developers.com/showthread.php?t=1671237
If you want to run another custom rom, you should actually just flash another recovery (read here http://forum.xda-developers.com/showthread.php?t=1677447) and flash another rom.
just flash stable cwm recovery-clockwork-6.0.2.8-evita.img
you can just flash it using Flash Image GUI if you can boot into your current rom, reboot recovery and flash the rom you want to flash. i wouldn't go back to pure stock seems like a waste of a good phone imo =)
Hi all,
I apologize if this has been answered before, but I had trouble finding it here. I am currently rooted on a stock backup, but I am running a custom recovery. I am not sure where to find the stock recovery image for my device. I am using the HTC One M8 through Verizon, and I know that the new firmware update is coming out soon, and I'd like to be able to just OTA update my phone so that I can reflash a custom recovery and install the newest VenomROM. I have flashed a custom recovery before (obviously), but I didn't know if it mattered which firmware base you are running. I read somewhere that the recovery is totally separate from the OS, and it is meant to be an alternative to booting into the OS in case of a problem, but I want to be sure. If there is a specific recovery I need to use and someone here knows where I can find it, that'd be great. I found the collection of stock recoveries, but I'm having trouble figuring out which one I need to use. Any and all help is appreciated, thanks.
EDIT: My CID is VZW__001
My VERSION-MAIN is nothing. There's is just nothing next to this label.
I tried locating it on the collection of stock recoveries, but couldn't find it. I'm not sure why this is.
It takes more than stock recovery to take the OTA. The /system has to be essentially stock. Some mods (e. g. enabling powersave) may also csuse the OTA install to fail. There is a thread with a pseudo RUU. You ought to be able to get stock recovery there.
My name is Harold and I'm a flashaholic....
hgoldner said:
It takes more than stock recovery to take the OTA. The /system has to be essentially stock. Some mods (e. g. enabling powersave) may also csuse the OTA install to fail. There is a thread with a pseudo RUU. You ought to be able to get stock recovery there.
My name is Harold and I'm a flashaholic....
Click to expand...
Click to collapse
Hi there,
I actually just used the psuedo RUU tool (I assume this is the one you are talking about? http://forum.xda-developers.com/showthread.php?t=2727831)
I just finished using this tool, but when I went to check the recovery, all I get is a big red triangle with an exclamation point in the middle. Nothing else. So, I'm guessing that recovery didn't flash properly? But I'm honestly not completely sure. I would screenshot it, but I can't do that. Any help is appreciated.
EDIT: I found out that pressing volume up and power gives more options. I assume I am all good to go now? I am still rooted, and I'm not sure if that is a problem. I am stock, s-off and rooted, but I don't have any mods installed.
You can't do anything in stock recovery except take an OTA, assuming everything else is stock. You can't do Nandroids, flash zips, etc. Looks like you have stock recovery.
My name is Harold and I'm a flashaholic....
hgoldner said:
You can't do anything in stock recovery except take an OTA, assuming everything else is stock. You can't do Nandroids, flash zips, etc. Looks like you have stock recovery.
My name is Harold and I'm a flashaholic....
Click to expand...
Click to collapse
Yeah I just figured out how the more options appear. I assume I'm good to go for the OTA now? I've got stock recovery, running a stock backup, s-off and I'm still rooted, but I think those are not a problem. I am not running any mods.
ChuckFinley1992 said:
Yeah I just figured out how the more options appear. I assume I'm good to go for the OTA now? I've got stock recovery, running a stock backup, s-off and I'm still rooted, but I think those are not a problem. I am not running any mods.
Click to expand...
Click to collapse
You should be good to go. A cautionary note, however, is that if you are rooted (even if S-OFF), it's not always advisable to take the OTA because frequently OTA's plug exploits used to secure root, etc. There was a definite difference between the original stock Verizon M8 ROM releated 3/25/14 and the minor update which followed, and some were unable (myself included) to secure stable root and/or S-OFF with weaksauce, having to acquire a license to Sunshine instead.
I intend to stick on my custom ROM and recovery and trust the developers to massage the OTA once it's out and have, literally within days if not hours, an updated ROM/firmware zip file that will more than adequately fit the bill.
hgoldner said:
You should be good to go. A cautionary note, however, is that if you are rooted (even if S-OFF), it's not always advisable to take the OTA because frequently OTA's plug exploits used to secure root, etc. There was a definite difference between the original stock Verizon M8 ROM releated 3/25/14 and the minor update which followed, and some were unable (myself included) to secure stable root and/or S-OFF with weaksauce, having to acquire a license to Sunshine instead.
I intend to stick on my custom ROM and recovery and trust the developers to massage the OTA once it's out and have, literally within days if not hours, an updated ROM/firmware zip file that will more than adequately fit the bill.
Click to expand...
Click to collapse
That does sound pretty appealing. I've never flashed firmware before though, and I wouldn't want to mess anything up. I remember seeing on the VenomROM firmware section, the easiest way to flash new firmware is to just grab the OTA update. The other way involved using some other program that I have not used before. I am overestimating how difficult installing new firmware is?
ChuckFinley1992 said:
That does sound pretty appealing. I've never flashed firmware before though, and I wouldn't want to mess anything up. I remember seeing on the VenomROM firmware section, the easiest way to flash new firmware is to just grab the OTA update. The other way involved using some other program that I have not used before. I am overestimating how difficult installing new firmware is?
Click to expand...
Click to collapse
Firmware (splash screen, radios, hboot, recovery) are "flashed" with an S-OFF handset via fastboot from the bootloader, while connected to PC. I believe (again, based upon the RUU thread I mentioned previously which you seem to have found) that it may also be possible to flash from hboot using an update.zip file (I think the M8 file is called PB06IMG.zip, but don't hold me to that --- every phone has its own such file format/name.)
ROMs and mods are typically flashed via recovery.
hgoldner said:
Firmware (splash screen, radios, hboot, recovery) are "flashed" with an S-OFF handset via fastboot from the bootloader, while connected to PC. I believe (again, based upon the RUU thread I mentioned previously which you seem to have found) that it may also be possible to flash from hboot using an update.zip file (I think the M8 file is called PB06IMG.zip, but don't hold me to that --- every phone has its own such file format/name.)
ROMs and mods are typically flashed via recovery.
Click to expand...
Click to collapse
Okay, I may look into that. I've only seen an RUU flashed via hboot, so I'd have to look into it. At the very least though, I'd imagine someone will post the instructions on how to flash the firmware when it comes out.
Thanks so much for your help!
hgoldner said:
I intend to stick on my custom ROM and recovery and trust the developers to massage the OTA once it's out and have, literally within days if not hours, an updated ROM/firmware zip file that will more than adequately fit the bill.
Click to expand...
Click to collapse
+100 for this!
I am reading dozens of posts in all kinds of threads of people just dying to take that OTA...
Why???
I would not touch that new firmware with a 100 foot pole until the devs have figured out what it breaks!!!
I predict a flood of posts in the line of:
"I flashed back to stock to take the OTA and now weaksauce is not working - how do I get root back?"
What's the hurry?????
Im just curious, what is the exact reason devs ignore these phones? Is there anything specific that makes them undesirable to work with? I dont think I have seen an HTC device be ignored this much since the HTC Snap?
Like i said... just curious
Cheers,
disco
It's just a phone that didn't really do well in the market, and no one wants to work on a phone that has little buyers...
What I'm wondering is why the Sprint version gets even less love than the out of date AT&T version which at least has a semi-working CM build.
Ok, thanks. Sucks that bad sales numbers can make a pretty decent phone so ignored.
Do you know if M9 or M8 are at all similar enough to A9 to maybe mod one of those roms for A9?
disco_y2k said:
Ok, thanks. Sucks that bad sales numbers can make a pretty decent phone so ignored.
Do you know if M9 or M8 are at all similar enough to A9 to maybe mod one of those roms for A9?
Click to expand...
Click to collapse
I'm not sure on that one, never worked with either, so it's kind of hard to tell, maybe put up a thread in the Q&A section with your question. And yes it does suck ????
This a copy/paste from somewhere in this forum, but I think its due to these reasons:
With the A9 (and the M9 prior to it), HTC has moved to a block-based OTA system. This means that even mounting system as read-write (as TWRP typically does during startup checks) will nullify the device's ability to take an OTA. Any other changes to the system partition will also cause an OTA to fail (even if that check is removed from the OTA zip) due to "unexpected contents."
Since the A9 has dm-verity enabled and forces encryption by default, root can only be achieved using the new "systemless" root methods. There are two currently working methods:
seSuperuser (this requires flashing only flashing a zip and installing an app from the Play Store)
SuperSU (automatically disables forced encryption & dm-verity, but requires a "Format Data" in TWRP)
There is also no way to take an OTA after you root. However, prior to rooting, you can take a fully untouched system image backup with TWRP, which can be used to restore a fully stock system to the device in order to take an OTA.
How do I backup stock recovery prior to flashing TWRP?
You can't. The "fastboot boot" command appears to be disabled on the A9's ABOOT, so TWRP must be fastboot flashed over stock recovery. The firmware zip included in the OTA will include a usable stock recovery image. That can be extracted and flashed after stock system is restored so that the OTA can be applied.
How do I restore stock system so that I can accept an OTA?
Check the "Mount system as read-only" box in the Mount menu.
Restore stock "System Image" backup (This will only work if you've made a System Image backup prior to making any modifications to /system).
Fastboot flash stock recovery (fastboot flash recovery recovery_signed.img)
NOTE: It is also possible to restore stock recovery via the TWRP GUI. Rename the stock recovery file to "recovery.emmc.win" and place in the backup folder with the stock system image. Recovery will then show as a restore option. MAKE SURE YOU REALLY WANT TO DO THIS, AS TWRP WILL BE GONE WHEN YOU REBOOT OUT OF RECOVERY!!
Reboot to system, install OTA.
What if I have an RUU? Do I need to worry about all this OTA nonsense?
Not if you don't care about losing all your data. If you're S-ON and have an RUU available for your exact variant (model ID and CID must match) and software number (main version must be the same or newer), then you can get back to a fully stock state by relocking (fastboot oem lock) and flashing an RUU. However, if you'd prefer to take an OTA to keep your data intact, the method stated above is how to do so. Or, you can just run a custom ROM and wait for your ROM chef to update their ROM to the latest software (though you'll still have to find a way to update your firmware if you're not S-OFF)
After I go through all this and successfully apply an OTA, how do I make sure I have a clean starting point again?
After the OTA is applied and TWRP is flashed, it will once again detect an untouched system, which will mount system read-only and allow you to make a fully stock backup and start the process over again, this time with the new base.
My ota works fine. Im rooted and you can backup by formatting data partition in the beginning. Fastboot works fine, flashing wirks fine. Really have not had any issues described above.
Oh well