I have a Nexus 7 WiFi 16GB running stock rooted and 2 custom roms via multiboot.
The custom roms stoped booting and now if you select any rom in multiboot it just boots the stock.
I tried to remove multirom (by reflashing boot.img to the device) and there were no errors but multirom remains.
I then thought I would reflash everything, bootloader, recovery, system the works. All of these processes reported 0 errors but the systems remains exactly the same.
I have also noticed that if I make any changes to the stock rom (install an app or change a setting) when the device restarts it's not there. It's as if the system isn't persistent.
Can anyone help???
Almost sounds like something in the file system got switched to read only.
What are you using to flash the device?
When I was playing with Multirom I think all I had to flash using Wug's was the stock kernel found under advanced options in order to remove multiboot.
The whole thing about making changes to the system that fail to persist is almost like root is borked or the bootloader is locked.
Does anyone know if its even possible to lock the bootloader once rooted?
KMDDesign said:
I have a Nexus 7 WiFi 16GB running stock rooted and 2 custom roms via multiboot.
The custom roms stoped booting and now if you select any rom in multiboot it just boots the stock.
I tried to remove multirom (by reflashing boot.img to the device) and there were no errors but multirom remains.
I then thought I would reflash everything, bootloader, recovery, system the works. All of these processes reported 0 errors but the systems remains exactly the same.
I have also noticed that if I make any changes to the stock rom (install an app or change a setting) when the device restarts it's not there. It's as if the system isn't persistent.
Can anyone help???
Click to expand...
Click to collapse
Did you read the OP?????
4. Uninstaller
MultiROM uninstaller: multirom_uninstaller.zip
Flash this ZIP file to remove MultiROM from your device. It will erase all secondary ROMs. If you don't want MultiROM menus in recovery, re-flash clean TWRP, but it is not needed - those menus don't do anything if MultiROM is not installed.
Could've sworn there was an Q&A section
WooHooGuy said:
Almost sounds like something in the file system got switched to read only.
What are you using to flash the device?
When I was playing with Multirom I think all I had to flash using Wug's was the stock kernel found under advanced options in order to remove multiboot.
The whole thing about making changes to the system that fail to persist is almost like root is borked or the bootloader is locked.
Does anyone know if its even possible to lock the bootloader once rooted?
Click to expand...
Click to collapse
I have tryed flashing from commandline with fastboot as well as using both Wug's and Nexus7 Toolkit. I have tried flashing the stock kernel with Wug's and no change. The bootloader certainly says unlocked.
bonzer2u said:
Did you read the OP?????
4. Uninstaller
MultiROM uninstaller: multirom_uninstaller.zip
Flash this ZIP file to remove MultiROM from your device. It will erase all secondary ROMs. If you don't want MultiROM menus in recovery, re-flash clean TWRP, but it is not needed - those menus don't do anything if MultiROM is not installed.
Click to expand...
Click to collapse
Tried that first
-PiLoT- said:
Could've sworn there was an Q&A section
Click to expand...
Click to collapse
Apologies, it was late, I was flustrated and I didn't see... if I knew how to move it I would.
I had the same problem trying to remove multirom, it just wouldn't budge!! I found the best way was to just erase everything on the tablet with fastboot commands and then just re-flash a stock image of Jellybean.
There's nothing like dusting off the old cobwebs once in a while to get that out of the box feel again!
Sent from my all singing and dancing Nexus 7 using xda app-developers app
mr_tris said:
I had the same problem trying to remove multirom, it just wouldn't budge!! I found the best way was to just erase everything on the tablet with fastboot commands and then just re-flash a stock image of Jellybean.
There's nothing like dusting off the old cobwebs once in a while to get that out of the box feel again!
Sent from my all singing and dancing Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Exactly what im trying to do.
I have ran:
fastboot erase system
fastboot erase userdata
fastboot erase cache
all with no errors but nothing was actually erased?!?
Start again but follow it in this order. But you also need to flash a stock ROM too. Your only doing half a job.
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot -w update stockromfilename.zip
Sent from my Nexus 7 using xda app-developers app
Related
My Nexus 10 stopped working after I've transferred about 14gb of movies on it. I copied them in windows 8 when nexus was plugged in USB.
It doesn't boot pass Google logo now, doesn't even reach Nexus symbol.
I can boot device in a bootloader and load a recovery. I did wipe/factory reset and also cleaned the cache, but that didn't help to solve the problem.
I have a suspicion that a filesystem is corrupt and e2fsck needs to run and fix the problems but I don't know how to start it.
I'm running a stock 4.2.1 not rooted or unlocked.
The battery level is above 70 and devices has been charging from the wall for 2 hrs at least.
Can anyone advice something to resolve the problem?
well, you still have a warranty.
that'd be my best bet, since if you hack it and its' still broken, you *might* not have a warranty.
Did you try flashing a stock image off the forums?
Sent from my Galaxy Nexus using Tapatalk 2
Less than a month old too..
Sent from my HTC PH39100 using xda app-developers app
I would replace it. It would suck to tinker with it and find out you can't fix it and the warranty is void.
Either get it replaced, or attempt to root it and flash a new ROM. I know you said wiping didnt help, but when you unlock it does a complete wipe of EVERYTHING so it might make a difference.
THe faster option to try is obviously rooting it, the safer option is probably just to get it RMA'd
Guys, Thanks for replies and suggestions.
So what I tried to do in last few days was:
I downloaded official 4.2 stock Rom and tried to reflash it together with a bootloader. I used "fastboot" to erase all partitions first, then flashed a bootloader and then flashed Rom. I had to run "oem unlock" otherwise fastboot didn't want to perform an operation.
The tablet still doesn't work, it's stuck on Google logo on a boot stage, not even reaching nexus symbol.
I didn't try to root it and install a custom Rom, because I'm afraid that I with loose a warranty. I believe the procedure above does wipe everything possible on a filesystem so I didn't go for a custom Rom solution.
I don't see a possible solution to restore a device now so I will return it on a warranty.
jodvova said:
My Nexus 10 stopped working after I've transferred about 14gb of movies on it. I copied them in windows 8 when nexus was plugged in USB.
It doesn't boot pass Google logo now, doesn't even reach Nexus symbol.
I can boot device in a bootloader and load a recovery. I did wipe/factory reset and also cleaned the cache, but that didn't help to solve the problem.
I have a suspicion that a filesystem is corrupt and e2fsck needs to run and fix the problems but I don't know how to start it.
I'm running a stock 4.2.1 not rooted or unlocked.
The battery level is above 70 and devices has been charging from the wall for 2 hrs at least.
Can anyone advice something to resolve the problem?
Click to expand...
Click to collapse
If you want to try e2fsck look at this quote/post: http://forum.xda-developers.com/showpost.php?p=34865732&postcount=162
wptski said:
If you want to try e2fsck look at this quote/post: http://forum.xda-developers.com/showpost.php?p=34865732&postcount=162
Click to expand...
Click to collapse
As I understand I need to be rooted with a custom recovery?
Can I run "adb" under a stock recovery?
jodvova said:
Guys, Thanks for replies and suggestions.
So what I tried to do in last few days was:
I downloaded official 4.2 stock Rom and tried to reflash it together with a bootloader. I used "fastboot" to erase all partitions first, then flashed a bootloader and then flashed Rom. I had to run "oem unlock" otherwise fastboot didn't want to perform an operation.
The tablet still doesn't work, it's stuck on Google logo on a boot stage, not even reaching nexus symbol.
I didn't try to root it and install a custom Rom, because I'm afraid that I with loose a warranty. I believe the procedure above does wipe everything possible on a filesystem so I didn't go for a custom Rom solution.
Click to expand...
Click to collapse
A custom ROM wouldnt help I dont think. The procedure you did is the important part before flashing a new ROM so if it didnt work then dont bother with anything custom.
jodvova said:
As I understand I need to be rooted with a custom recovery?
Can I run "adb" under a stock recovery?
Click to expand...
Click to collapse
ADB commands are run when you are booted into the tablet if I remember right.
Now that you've installed a stock ROM, go into recovery and factory reset. This may help your bootloop issue.
Sent from my Galaxy Nexus using Tapatalk 2
Blueback22 said:
Now that you've installed a stock ROM, go into recovery and factory reset. This may help your bootloop issue.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I did that couple of times, it didn't help.
Guys,
Looks like a partition table got screwed up, because when I run e2fsck on any of partitions (system, userdata, boot), it says: "attempt to read block from filesystem resulted in short read".
Does anyone know how to fix it?
Or where can I find Nexus 10 PIT file?
jodvova said:
Guys,
Looks like a partition table got screwed up, because when I run e2fsck on any of partitions (system, userdata, boot), it says: "attempt to read block from filesystem resulted in short read".
Does anyone know how to fix it?
Or where can I find Nexus 10 PIT file?
Click to expand...
Click to collapse
Have you tried to go into stock recovery, and select the adb side load and try manually push the files like that?
Sent from my Nexus 10 using xda app-developers app
evolishesh said:
Have you tried to go into stock recovery, and select the adb side load and try manually push the files like that?
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Can you elaborate here?
Which files should I push? A Rom?
I am facing the same situation and it is not going past the nexus logo screen lol. I tried flashing factory images from here in fastboot mode but its still not working. In recovery, its showing can't mount SD card even after I tried mounting SD card and i tried wiping, factory reset and nothing. SD card still can't mount also and I wonder if that is the problem. I'm try some more.
So, I just fixed it and my nexus 10 boots up and all good again. Basically in bootloader, you just need to flash the userdata.img and cache.img also from the extracted files of the factory image file as I noticed it wasn't flashing those 2 files when I just flashed/updated the image.zip file with this command fastboot -w update image-mantaray-jop40c.zip and it was only flashing the system.img, recovery.img, boot.img so I extracted this image-mantaray-jop40c.zip file and I flashed the userdata.img and cache.img files manually and rebooted and its all good again back to stock.
NeverAlwaysEver said:
So, I just fixed it and my nexus 10 boots up and all good again. Basically in bootloader, you just need to flash the userdata.img and cache.img also from the extracted files of the factory image file as I noticed it wasn't flashing those 2 files when I just flashed/updated the image.zip file with this command fastboot -w update image-mantaray-jop40c.zip and it was only flashing the system.img, recovery.img, boot.img so I extracted this image-mantaray-jop40c.zip file and I flashed the userdata.img and cache.img files manually and rebooted and its all good again back to stock.
Click to expand...
Click to collapse
Just to clarify did you use fastboot to flash userdata.img? Which command did you use "fastboot -w update userdata.img"?
Also where did you find userdata.img ???
It doesn't come in nexus 10 factory image. It only has boot, cache, recovery, system and a bootloader.
I want to completely wipe/format all of my nexus and then install a custom ROM without installing the stock 4.2 rom and then having to download the custom ROM and installing it with cwm if possible. I have installed lots of ROMs and it feels like the kernels are not making much difference and would like to do a fresh start now I know the ROM/kernel I want. I also have never been able to install a recovery from the nexus tool kit and wonder if wugs is better.
Just trying to save a step.
Sent from my Nexus 7 using Tapatalk 2
http://forum.xda-developers.com/showthread.php?t=1907796
Just do these steps :
Code:
> fastboot erase boot
> fastboot erase cache
> fastboot erase recovery
> fastboot erase system
> fastboot erase userdata
> fastboot flash bootloader bootloader-grouper-4.13.img
> fastboot reboot-bootloader
Then install TWRP : http://teamw.in/project/twrp2/103
Then use "adb push" command to push your rom to your device using adb, then install it using TWRP
Thank you. That is what I want but never read that thread because it says factory ROM.
Sent from my Nexus 7 using Tapatalk 2
I'm sure it works well with a stock install but I had two problems I could not fix. First was twrp wanted a password and second even after I redid everything but with cwm the flash said it could not mount any partition.
Sent from my Nexus 7 using Tapatalk 2
You have to be booted into android in order to ADB push correct? So how would this work from a wiped device?
Figured out how
I figured out how to do this. I got sick of having to install stock after a complete wipe and format only to immediately flash a custom rom. The only reason I was flashing stock was to put the rom zip on my SD. After wiping everything I re installed TWRP with fastboot and boot into recovery. TWRP wants a password to mount data. I just pushed cancel and was let into the main menu. Still couldn't mount data until I reboot back into recovery from recovery. Once I did that data was auto mounted. I choose ADB sideload. Then had to open a terminal on my linux machine in the dir. that contained my rom. Then su in terminal and do command- adb sideload /path/to/rom.zip. It would only work with su otherwise I got a permission error. After it pushed over I just flashed it from TWRP and boot up like normal.
Thank you. That should work. I didn't try a reboot after twrp install.
Sent from my Nexus 7 using Tapatalk 2
k29er said:
I want to completely wipe/format all of my nexus and then install a custom ROM without installing the stock 4.2 rom and then having to download the custom ROM and installing it with cwm if possible. I have installed lots of ROMs and it feels like the kernels are not making much difference and would like to do a fresh start now I know the ROM/kernel I want. I also have never been able to install a recovery from the nexus tool kit and wonder if wugs is better.
Just trying to save a step.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I use TWRP its way better then CWM. Very simple you can also get it through root capabilites with a toolkit. im up to the latest Jelly bean software then rooted and installed with toolkit. Sideload your rom clean delvik cache and regular cache do factory reset and instal rom and enjoy :laugh:
So.... i installed paranoid android and after... there were no connections at all! no internet, no usb, nothing. So i bootet into fastboot and now i just want to flash a clean cm10 or something. Sh1t on my data and anything, everything is in my cloud what is the command to flash a simple zip via fastboot? i did not find anything related to n4 in the internet and i want to get sure i am using the right one for the nexus 4 and no old device
You dont flash zips through fastboot.
At least not the type of zips you're talking about.
You boot into recovery. Do a full wipe. Factory reset + format system. Then flash cm10.1 plus the gapps.
albundy2010 said:
You dont flash zips through fastboot.
At least not the type of zips you're talking about.
You boot into recovery. Do a full wipe. Factory reset + format system. Then flash cm10.1 plus the gapps.
Click to expand...
Click to collapse
The problem is, there is no ROM on my sd and i cant find my device via adb. so sideload also wont work.
//Edit
Got it working. It bootet. I found a mysterious backup on my sd and restored it Ô.o i never did one, but, hey, it works^^. next try to flash cm10.1^^ and first i drop it to my sd.
//Edit 2
Franco Kernel r72 + paranoid android = no USB. Simple math.
If you end up in that position again, you can flash the stock images using fastboot (*.img files on your pc, phone at bootloader).
fastboot flash system system.img
fastboot flash boot boot.img
etc.
I encrypted my nexus 4 a couple of months ago, and I had no issues until I wanted to flash a custom rom. I installed a custom recovery (Clockwork Recovery), and tried to wipe the cache, find the zip file, but it said that it was unable to mount sdcard. I figured that this was due to the encryption, and tried to factory reset the phone. I was unable to do so through the recovery and through the settings app. I followed instructions from the following thread to flash a stock image: http://forum.xda-developers.com/showthread.php?t=2010312 , which was unsuccessful. In the end, I still have all my data, and the encryption remains. Any ideas how to get rid of it?
When running encryption you have to side load everything. Try to side load the ROM you want. if that dose not work download factory image and fast boot it over.
illru said:
When running encryption you have to side load everything. Try to side load the ROM you want. if that dose not work download factory image and fast boot it over.
Click to expand...
Click to collapse
Could you give me directinos on how to do this? Or a link to another thread or video?
SpectralFlames said:
Could you give me directinos on how to do this? Or a link to another thread or video?
Click to expand...
Click to collapse
I believe to sideload you use adb and place the zip you want in the adb's folder, plug your phone into recovery, and use the command adb sideload (zip file name) or something or the sort and you should be good to go, have you tried
fastboot erase system
data
cahc?
Sent from my Nexus 4 using Tapatalk
IRX120 said:
I believe to sideload you use adb and place the zip you want in the adb's folder, plug your phone into recovery, and use the command adb sideload (zip file name) or something or the sort and you should be good to go, have you tried
fastboot erase system
data
cahc?
Sent from my Nexus 4 using Tapatalk
Click to expand...
Click to collapse
When in recovery it says that it can't mount sdcard so it doesnt allow me to do anything through recovery. That was the main issue when trying to flash a rom
I'm trying to upgrade my SuperSu to the latest beta so I can install Viper4Android for Angler. However, the instructions for SuperSu Beta states "If you are coming from any SuperSU install in /system, you must re-flash the stock system (and vendor and oem, if present) partition contents prior to installing this."
I was wondering if I could get some Nexus 6P specific instructions for doing that without screwing everything up. I assume this doesn't wipe my user apps. Thanks.
If you are comfortable with using ADB and fastboot, follow Section 10 of this guide. All you need to do is "fastboot flash system," just download the factory image that matches your current rom.
http://forum.xda-developers.com/showthread.php?t=3206928
Flashing just the system partition does not wipe app data.
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
If you are comfortable with using ADB and fastboot, follow Section 10 of this guide. All you need to do is "fastboot flash system," just download the factory image that matches your current rom.
http://forum.xda-developers.com/showthread.php?t=3206928
Flashing just the system partition does not wipe app data.
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
Yeah, I'm pretty comfortable using adb and fastboot. I'll try it out. Thanks!.
Quick question, can I keep the TWRP recovery or do I need to flash stock recovery too? Thanks again.
hull22 said:
Yeah, I'm pretty comfortable using adb and fastboot. I'll try it out. Thanks!.
Quick question, can I keep the TWRP recovery or do I need to flash stock recovery too? Thanks again.
Click to expand...
Click to collapse
Cool! There is no need to touch the recovery partition. Just fastboot the system and vendor img's then boot right into TWRP and install SuperSU
Sent from my Nexus 5X using Tapatalk
SlimSnoopOS said:
Cool! There is no need to touch the recovery partition. Just fastboot the system and vendor img's then boot right into TWRP and install SuperSU
Sent from my Nexus 5X using Tapatalk
Click to expand...
Click to collapse
I screwed it up. Flashed everything just fine. Didn't have the SuperSu beta on the phone yet, booted to system. It tried to re-encrypt the device. I interrupted it because it seemed to be stuck. Now, I have to factory reset and lose all of my data. Not sure where I have to restart now, root, etc...
hull22 said:
I screwed it up. Flashed everything just fine. Didn't have the SuperSu beta on the phone yet, booted to system. It tried to re-encrypt the device. I interrupted it because it seemed to be stuck. Now, I have to factory reset and lose all of my data. Not sure where I have to restart now, root, etc...
Click to expand...
Click to collapse
Ahh dang, were your able to get set up? If the rom is messed up, you'll likely have to fastboot flash system, boot, and vendor IMG's for the 6.0.1 OTA you already downloaded.
I wasn't aware that you were decrypted, I would have been more expressive about not booting until things were flashed in recovery. SuperSU removes "force encrypt" from the stock boot.img so that would not have occurred.
Sent from my Nexus 5X using Tapatalk