I was using the Nightly ROM and when i tried to flash an update, my NEXUS 9 went into a boot loop(I had lost root earlier). I was able to go into recovery but even after flashing the lastest zip, had the same bootloop problem. SO i decided to flash an updated SU hoping to get back root privelages. and reflash Nightly, G apps and SU. Still bootloop (Overnight)
After all this i did the mistake of doing an Advanced Wipe which wiped all the data on the device. When I go into recovery i get the "Keep system read only message"
Unable to load any ROM or Flash it. Please help.
Trying to use fastboot to load the factory image
At the moment , trying to flash in the factory image for the NEXUS 9 to restore the system , boot.
https://forum.xda-developers.com/nexus-9/general/guide-how-to-unlock-bootloader-flash-t3035153
is very useful.
But i am wondering is there another way around this mistake.
Nightroad69 said:
I was using the Nightly ROM and when i tried to flash an update, my NEXUS 9 went into a boot loop(I had lost root earlier). I was able to go into recovery but even after flashing the lastest zip, had the same bootloop problem. SO i decided to flash an updated SU hoping to get back root privelages. and reflash Nightly, G apps and SU. Still bootloop (Overnight)
After all this i did the mistake of doing an Advanced Wipe which wiped all the data on the device. When I go into recovery i get the "Keep system read only message"
Unable to load any ROM or Flash it. Please help.
Click to expand...
Click to collapse
You have to select not to keep system read only. If you're having trouble flashing the factory image, try using wugfresh nexus root toolkit. It's here in the forum. It installs on PC and it downloads and flashes everything for you. It has some great features.
https://forum.xda-developers.com/nexus-9/development/toolkit-wugs-nexus-root-toolkit-v1-9-8-t2945451
I am currently having the same issue. I am using wugfresh toolkit. to get it back to stock and start over. Don't know why it is not wanting to read data. Never had this issue until today. It looks like wugfresh saved the day.
Related
So I was able to successfully root my AT&T HTC One X and decided I wanted to install the CM 10 ROM (1st ROM install). I did all the data backups with Titanium, downloaded the latest zip files from cyanogenMod (both the 12/13 and 12/14 nightly versions), transferred them to my phone, booted into recovery (TWRP), did a back-up, did a system wipe, flashed the ROM and then did a reboot. However, when it boots it gets stuck in the boot-up screen (bootloop) and doesn't do anything. I have read on this and it keeps saying to wipe system data again and flash the ROM again and it keeps doing this. I want to install this ROM, but I need some help. Any suggestions on what I did wrong?
Do I need to manually flash the boot.img file or should I only need to transfer the zip to my phone and install after wiping/doing a factory reset?
Well, that didn't work either as the zip file failed completely during install. So I downloaded the latest "stable" version just for giggles and wiped everything again and did an install. Just like before, the install was successful and on reboot it locks up on the boot screen. I am at a loss on what to do.
Hey buddy, i had cm10 running on my HOX, when i did it i had to flash the boot img through fastboot as well.
I found a tutorial on youtube by cursed forever helpful, sorry I'd post a link but my thread counts not high enough yet
So, I was able to successfully unlock my bootloader, got TWRP 2.6 on it, and put a few different ROMs on my machine; however, I have yet been able to install a ROM and get it to move past the boot animation.
I have tried the latest nightly ROMs for CyanogenMod 10.1 and 10.2 for my TF201, both of which get stuck in CM's boot animation. I just tried the same with the newest Baked ROM, only to be stuck in its boot animation as well.
I'm trying to figure out if there was something I forgot to do. I have been able to revert to a backup of my stock Jellybean 4.1.1 that I stored using TWRP, but haven't been able to use anything else.
Are there any thoughts on this? Have I missed something? I was able to use the unlocker utility and each boot offers the confirmation in the top-left that my bootloader is unlocked. I am able to enter TWRP from the recovery mode. Shouldn't it be as simple as selecting a ROM's zip archive and installing it from TWRP?
Have you done a full wipe before installing, including cache and dalvik cache partitions?
Sent from my SAMSUNG-SGH-I337 using Tapatalk 4
Try installing twrp 2.5. AS I just read in another thread there are problems with 2.6..
Sent from my MB526 using xda app-developers app
Factory reset
After flashing CM 10.1 nightly last night i had the same issue. I booted into my recovery console (flatline cwm) and performed a factory reset. This seemed to clear whatever issue was bothering the tablet. Still sat there for about five minutes on the animation after the reset but then progressed into setup.
Doubt if it makes a difference but mine was connected to the dock too.
If you're still stuck the method that worked for me yesterday was:
Used Flatline CWM as the recovery, installed using fastboot
Used an external memory card to copy the relevant zip files to my sdcard, recovery couldnt find them otherwise using adb push
Installed from zip using Flatline CWM
Installed gapps using Flatline CWM
Booted, got the issue you had
Booted into recovery, performed a factory reset
Told recovery to restart the machine
Booted into setup screen after loading for a few minutes
Figured I'd post this here since I didn't get any other replies in the Nexus forum.
I have been trying to wipe my Nexus 7 (2012) clear but the wipe functionality doesn't appear to work.
I've been rooted on stock (using TWRP) but recently sideload 4.4.2 and removed root in the process.
OTA installed and I root was removed but recovery is now showing "no commands".
I have been able to get past that sometimes but not consistently and using the recovery wipe/factory reset doesn't do anything.
I tried to fastboot and do a wipe from the command line but that doesn't seem to be working either.
The device won't boot properly, it crashes after a few seconds once loaded and automatically restarts so I wanted to clean everything up and start fresh.
I tried custom temp recovery (since it's the only option available to boot from fastload) and while I can get into temp TWRP the wipe option doesn't do anything.
I also tried to reinstall the bootloading from the 4.4.2 image but that didn't help.
Any ideas what else I may be able to try?
I was using my phone and all had been working fine for ages. It was in my pocket for a while and when i took it out to use it I saw that it was on the boot animation of CM11. My phone was already on when I last used it so I had assumed it had crashed. I took the battery out and turned the phone on again but it got stuck on the CM boot animation. The last time I turned on my phone before that was when I flashed a supersu zip file to make my root work as I was having some problems. After flashing the supersu zip and told my CWM recovery to restart the system, it prompted me to "fix root" or something like that, and I clicked yes and it booted normally. That was the last time it booted normally before being stuck as it is now. First thing I did after it got stuck was go into recovery and reflash my current rom ( a CM11 snapshot) I then got faced with a status 7 error and so couldnt flash the rom. So then I flashed multiple other CM11 roms, none of which worked, so I flashed a CM10.2 stable rom which worked. I then got faced with the fix root before reboot thing and so I clicked yes. Still had the stuck booting thingy. I tried many things, flashing kernals roms gapps etc and nothing made a difference. I wiped cache, dalvik cache and no difference. I even wiped the system and tried to flash roms but only the 10.2 one would work, still got a status 7 with the CM11 ones. When I wiped my data however and flashed CM 10.2, it booted. I still couldn't flash the CM11 roms though even after a factory reset. So I have the reason to believe something in the data is wrong, not cache system or anything like that. What could it be? I don't want to have to lose all my data in order to be able to use my phone again, even then, something is still wrong as my phone won't flash CM11 roms anymore. So my questions are;
What things could have caused this?
Can this be a problem from flashing the supersu zip (a root issue)
Is it possible to somehow view or copy the internal data on a computer (since I cant get into the operating system), and this would allow me to get all my pictures contacts music etc anything so I can use my phone by wiping data?
Thanks, sorry this is quite long and probably hard to understand whats going on, but help is appriciated thanks
Don't fix root if you wish to use SuperSU instead builded-in cm superuser. Also try to flash via Odin latest recovery. TWRP should be fine. You can mount partitions from recovery level to download data to your computer. Of course if it still exists. If not, if they are corrupted you need to flash stock ROM and repeat whole cm11 adventure again. If Odin successfully flash the stock then it's a chance your partition layout and user data are untouched.
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2
Hi Everyone,
I just followed the instruction and unlocked my bootloader.
I am in marshmallow and then used twrp to flash supersu 2.64.
When i was flashing to root twrp asked me about the partition change which i dont understand so swiped it and now i cant get past the htc one bootscreen. I have tried factory reset and wipe dalvik cache.
What do i do?
kisshell99 said:
Hi Everyone,
I just followed the instruction and unlocked my bootloader.
I am in marshmallow and then used twrp to flash supersu 2.64.
When i was flashing to root twrp asked me about the partition change which i dont understand so swiped it and now i cant get past the htc one bootscreen. I have tried factory reset and wipe dalvik cache.
What do i do?
Click to expand...
Click to collapse
Go back and change partition to read and write in twrp (I think), sounds like you set it to read only if you are getting stuck at that screen. If all else fails I'd try running the RUU then re flashing twrp , but are you s off? I've been s off since sunshine came out (which I highly recommend) and don't know how things work being s-on. Also which version of twrp are you using?
Go read up about how twrp works , that way when you are prompted with things that could prevent you from obtaining root you will know what to do. #4 in the link below might be able to help you... but once again read all the information provided.
http://forum.xda-developers.com/showpost.php?p=59745198&postcount=3
you need to update your TWRP to 3.0.0. Flash it through CMD or sdcard way, reboot to recovery, "Mount as Read Only" message swipe to right. You want it to be that way for an untouch system backup(if you wanted to do). Reflash MM ROM.
got it
The problem was twrp was asking to flash the supersu from itself even after i had flashed the su manually from twrp. i just installed badboyz and then flashed the su and did not accept the twrp option to flash supersu again and it is working again. To add more, i think i even got it dsu with the recent guide posted here which saved me few bucks. I love xda!