I've not done too much with my phone over the years, flashed the odd root package and whatnot and never really had an issue before.
This time i'm pretty stumped.
Wife got a new phone for christmas, so i figured i'd try installing CM13 on her old Nexus 4
Did fastboot oem unlock, that worked fine, flashed the latest TWRP (2.8.7.0) using fastboot and that also worked fine.
Rebooted into TWRP and it was complaining about /data not being mountable. Wiped system/cache/data etc and got TWRP to format data which fixed the error.
Copied the latest nightly of CM13 over as well as opengapps nano, and flashed them.
Flashing worked fine, with no errors displayed, and then i rebooted the phone.
It gives me the google screen, then boots into TWRP again.
tried flashing an earlier build of CM13, and also tried not flashing the opengapps, but everything has the same result, phone just boots into recovery. Even tried flashing an unofficial build from this thread:
http://forum.xda-developers.com/nexus-4/development/rom-unofficial-cm13-marshmallow-builds-t3236487
Same thing.
What am i doing wrong?!
Fixed it.
Reflashed factory firmware and started from the beginning and it worked fine this time.
Thanks for the help.
Aragorn84 said:
Fixed it.
Reflashed factory firmware and started from the beginning and it worked fine this time.
Thanks for the help.
Click to expand...
Click to collapse
That happens because system partition's filesystem gets corrupted fyi. That's why reflashing factory image fixes it , it re-formats the partition. You can also do that manually , without flashing the factory image. Inspect the .bat file of the factory image in notepad , you'll see the code.
Related
I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks
I've the same problems with my nexus 4
gerardgerard said:
I am trying to flash my N4 with cyanogenmod following the official wiki.
I'm at the point where I've installed TWRP into recovery, I've wiped everything (I've even formatted them since I couldn't wipe all of it initially), and the only error I see is "unable to mount /usb-otg".
Then, I've "installed" the CN zip files for the 13 and 12 versions, none of them works in the sense that when I reboot the system, I'm always coming back to TWRP.
What's wrong? Any suggestion?
Thanks
Click to expand...
Click to collapse
Hi gerardgerard,
I also wanted to flash my Nexus 4 with Cyanogenmod 12.1. So I installed TWRP into recovery and wiped everything, like it's explained in the wiki. I can also see the error "unable to mount /usb-otg". When I want to reboot the system I always get back to TWRP. Cyanogenmod doesn't boot correctly. Did you find a solution for the problem?
same problem
Hi
I'm having the same problem. As follows:
Cause (my mistake): I have been using Cyanogen-mod nightlies for a couple of months on my Nexus 4, and made the grave mistake of leaving the phone to upgrade one night but without it being plugged in properly - and it ran out of power part way through! (At least, that's what I think happened).
Fortunately, it would boot into bootloader and I could use adb/fastboot. I (re)installed TWRP 2.8.7.0 (from my Mac, using fastboot). And that works fine - I can boot into twrp ok.
Next I loaded the latest nightly from cm (using fastboot - is this what people call sideloading?) and used twrp to install it. It goes through the installation fine (the only error message is that it can't mount /usb-otg). But when I reboot it just goes back to twrp.
I then tried installing the earlier cm nightly that I know worked, but with the same result.
Finally, before I first installed cm I did a backup (using twrp), and I have tried recovering that. It seems to do all the right things, but again when I reboot it just goes back to twrp.
Any suggestions would be welcome.
Thanks
J
Flash back to a completely stock ROM and run through the set up to make sure everything works. Then copy CM to the phone, reboot to fastboot, flash twrp, immediately boot into recovery using the volume and power button without leaving fastboot, wipe data, cache, system, flash CM, reboot.
If the phone will not boot after flashing a stock ROM, boot to fastboot, flash the userdata.img file, and immediately go to stock recovery without leaving fastboot, wipe data/cache, reboot.
It works now!
I managed to fix the problem ... I found this guide for the Nexus 5:
http://forum.xda-developers.com/google-nexus-5/general/tutorial-how-to-flash-factory-image-t2513701
and I applied those instructions. It didn't work first time, so I just repeated them and now it's working. I used the 5.1.1 stock downloaded from https://developers.google.com/android/nexus/images#occam.
I guess this is what audit13 means in their post - so thanks are due there.
I will next reinstall twrp and cm and I don't expect any problems with that (having done it successfully before).
Smaje
Hi all,
I was running the official Google 5.1.1 version until this morning. I now did an oem unlock using fastboot and installed the latest twrp recovery 3.0.0, and finally copied overy CM-13 nightly (and Chroma-2016-02 for testing purposes) using adb.
Flashing itself work flawless, there is no warning or error message, but when hitting "Reboot" within twrp the Google logo shows up for a few seconds and it directly boots into twrp again. This is with both, CM-13 and the latest Chroma.
So I basically cannot get my Nexus-4 bootet regulary any more.
Any ideas what the problem might be?
Any help is welcome,
regards, mistersixt.
Mmmh, strange, I did a factory installation (latest 5.1.1 from Google) and started the same thing from scratch ... and guess what... the system is booting fine now.
No idea why it did not work on my first attempt .
Regards, mistersixt.
mistersixt said:
Hi all,
I was running the official Google 5.1.1 version until this morning. I now did an oem unlock using fastboot and installed the latest twrp recovery 3.0.0, and finally copied overy CM-13 nightly (and Chroma-2016-02 for testing purposes) using adb.
Flashing itself work flawless, there is no warning or error message, but when hitting "Reboot" within twrp the Google logo shows up for a few seconds and it directly boots into twrp again. This is with both, CM-13 and the latest Chroma.
So I basically cannot get my Nexus-4 bootet regulary any more.
Any ideas what the problem might be?
Any help is welcome,
regards, mistersixt.
Click to expand...
Click to collapse
Same here. Running stock until today, wanted to see a different ROM, flashed TWRP 3.0.0, it refused to boot anything else. Tried to flash DU, then tried Chroma. Did a full wipe, then an advanced wipe selecting everything, then a full format, same thing. Installed TWRP 2.8.7, same thing. Finally installed latest stock, it is now booting, optimizing apps. I don't know if installing a custom rom will work or not yet.
Edit: Yeap, after flashing stock 5.1.1 and installing TWRP 3 again, the phone is now booting into DU.
First time I did a wipe with TWRP, it complained that it couldn't mount /data. Since this is the first time doing it, I assumed it was normal. After going through a full format, it didn't complain about data anymore, but it did complain about something to do with /dev/zero and another file under /dev/. I assume it was trying to dd /dev/zero to a file under /dev/ that didn't exist.
+1
Done the whole process from scratch again and worked like a charm
Hello, same story here.
First I:
- unlocked bootloader
- flashed TWRP (last version)
- flashed Chroma and Gapps
- reboot
=> I consistently rebooted on TWRP. No way to properly install the ROM. No error message at all.
Then I found this thread, and did as described:
- flashed the latest stock ROM
- flashed TWRP again (took me ages to manage to do this: TWRP would not install. I don't know how I finally did it, but at some point it suddenly worked. Probably a driver problem)
- flashed Chroma and Gapps again
Bingo, this time it worked! I don't know why it didn't work the first time. Could it be linked to the bootloader unlock thing?
I have been running the No Limits Nougat build for a while with no issues. Decided to flash the Oreo build yesterday.
Followed the directions, ran a backup and checked it, and wiped (not a rookie, have flashed plenty of phones previously) but afterwards I'm having major issues.
The initial flash seemed like it went fine, the phone tried booting but went back to recovery and when I looked at the files it looks like they have been encrypted. I'm not getting a message when TWRP starts to put in my password which I thought was the issue. I've tried different recoveries and different ROMs but if I can sideload the ROM on and flash it after I restart it goes back to TWRP with encrypted files.
I know I've lost the data on the phone which is fine, I had dragged some backups to my computer but I can't figure out why every time I flash anything the phone is getting encrypted and pretty much bricked. I figured that once I factory reset and clean installed the encryption would be gone. Am I out of luck? I tried flashing the stock ROM from TWRP and get 'Updater Process ended with ERROR: 7'.
Not sure what to try next, HELP!
oneunder311 said:
I have been running the No Limits Nougat build for a while with no issues. Decided to flash the Oreo build yesterday.
Followed the directions, ran a backup and checked it, and wiped (not a rookie, have flashed plenty of phones previously) but afterwards I'm having major issues.
The initial flash seemed like it went fine, the phone tried booting but went back to recovery and when I looked at the files it looks like they have been encrypted. I'm not getting a message when TWRP starts to put in my password which I thought was the issue. I've tried different recoveries and different ROMs but if I can sideload the ROM on and flash it after I restart it goes back to TWRP with encrypted files.
I know I've lost the data on the phone which is fine, I had dragged some backups to my computer but I can't figure out why every time I flash anything the phone is getting encrypted and pretty much bricked. I figured that once I factory reset and clean installed the encryption would be gone. Am I out of luck? I tried flashing the stock ROM from TWRP and get 'Updater Process ended with ERROR: 7'.
Not sure what to try next, HELP!
Click to expand...
Click to collapse
Which guide did you follow? What steps did you exactly take and which version nougat rom you have and which oreo build(stable/beta) do you want to install?
There are plenty of instructions, like this one here: https://forum.xda-developers.com/showpost.php?p=75155514&postcount=8618
I've had this happen before on other phones, usually fixed by just installing a different rom or restoring a backup. Not here.
I finally unlocked my bootloader on the XT1607 (the Motorola site just randomly worked one day), installed TWRP & the 7.1.1 Soak Test (from here). I forgot to backup 6.0.1, so I backed up the soak test which was booting and working flawlessly. I was using it for a while, but I did a factory reset inside TWRP and it randomly said "cannot mount storage" and when I rebooted, it was into TWRP. It wasn't working at all, so I got LineageOS 15.1 and flashed that. Same error, "cannot mount storage" and back to TWRP. I went into Wipe>Format Data and then reinstalled Lineage. The "cannot mount storage" error was gone, but still booting into TWRP. I tried AOSP Extended, CyanogenMod, Paranoid Android. roms with gapps, roms without, with & without supersu or magisk. Nothing worked. So then I thought that restoring my backup (of all partitions) would fix the issue. It didn't, still booting back into TWRP. I'd also like to mention that plugging the phone in still worked, I can view the files in file manager, sd card works, etc.
So, no clue what to do here. What's wrong? It all started with that simple factory reset from twrp.
edit: I found that if I boot into bootloader and press start it will go into android, but hardly a permanent solution.
Same thing happened to me but my issue resolved after restoring back to stock rom with stock recovery and after that u can again flash twrp it will work fine
sumit1327 said:
Same thing happened to me but my issue resolved after restoring back to stock rom with stock recovery and after that u can again flash twrp it will work fine
Click to expand...
Click to collapse
Heyyy, thanks man. Worked like a charm.
I installed LineageOS with and without Gapps and it still crashes my Shield. Should I try a different build from Lineage's page? I was running 12/15/21 with Gapps 12/17/21. Is it common for LineageOS to crash, freeze and reboot by itself?
I installed the build from 12/15/2021 and have not experienced a crash, freeze or reboot yet. I have never tried to install gapps. So if you followed the installation instructions in the LineageOS wiki, it should work.
Did you wipe your partitions prior to building? Sometimes flashing a new system onto the existing one without doing so, can result in, such undesirable behavior.. If you didn't this could help explain how and why, code is in description box
would also download the latest Lineage Build, they do Nightlys
jenneh said:
Did you wipe your partitions prior to building? Sometimes flashing a new system onto the existing one without doing so, can result in, such undesirable behavior.. If you didn't this could help explain how and why, code is in description box
would also download the latest Lineage Build, they do Nightlys
Click to expand...
Click to collapse
I wiped the partitions in TWRP using your guide. I have not tried wiping those partitions manually in fastboot. That could explain the issue I was having. Thank you
Delete the partitions with TWRP unfortunately did not work for me. TWRP has not recognized any memory. So I flashed the lineage_recovery and everything worked as it should.
Kladderadatsch said:
Delete the partitions with TWRP unfortunately did not work for me. TWRP has not recognized any memory. So I flashed the lineage_recovery and everything worked as it should.
Click to expand...
Click to collapse
Thank you for sharing, this will Surely help someone else in the same shoes. Glad you got it working!~!
Unfortunately it still reboots on its own. I tried wiping all the partitions you listed and flashed the proper files to get LineageOS working. It's better to wait until the build gets more stable
Skel40 said:
Unfortunately it still reboots on its own. I tried wiping all the partitions you listed and flashed the proper files to get LineageOS working. It's better to wait until the build gets more stable
Click to expand...
Click to collapse
I'm sorry to hear that! But thank you for being honest and letting us know you are still having problems! I think you are correct that waiting for a more stable build is a good step.
I have only gotten my feet wet in kernel editing and manipulation, so It's A lot Lineage does for us, its just a matter of them getting the Science down to a good, clean, consise, logic
I have now replaced the lineage recovery with TWRP and the memory is now recognized.
I must say everything runs stable, without crashes or so.
Also wiping the partitions messes up with fastboot booting TWRP. I only was able to have Lineage recovery flashed and booted up using boot recovery kernel found in bootloader mode. I don't know what I'm doing wrong here but another issue is the recovery itself directly from Lineage. I tried to factory reset as it told me to after wiping the partitions and it failed. Emmc is not supported, factory reset failed.
What wouldn't make sense is it's not the Shield's power supply issue or any of the components failing after booting into LineageOS. Nvidia's OS works perfectly without constant freezing and reboots. Hopefully this issue can be resolved at some point. It's a bummer I've tried everything to get this far.
I the same problem and i noticed an error in the fastboot flash of mdarcy.dtb
I checked the batch file that you tasked it to and found
Fastboot flash mdarcy.dtb mdarcy.dtb.img
I changed it to fastboot dtb mdarcy.dtb.img
And it corrected the partition