After successfully installing Android 11 on a brand-new nexus 4 i got, i then went to try the same thing on a used one (for my dad)
The phone now as it stands is stuck on lineage recovery and i get this message.
error: android failed to bind mount /mnt/staging/emulated/media/0
I choose wipe cache/data etc because it was running an older rom i think Droid 7 or 8
Then after reboot just stuck in recovery and can't use adb on pc or anything
I can't even use ADB it doesn't list the device
So what do i do? anyway i can install a stock rom if so how?
I fear my dads Nx4 is BRICKED lol
Going to use the nexus rootkit to bypass that crap and install a stock rom for my dad
Related
i flashed a custom rom on my nexus 7, it woked fine except installing the gapps
i used goomanager to downloaded latest gapps but it downloaded the one for 4.1.1 and i have 4.2.1, so when i boot the device i got an error
i used cwr to wipe all the data in it and now i got the google logo when i boot
i still have the booloader but i cant connect to my pc, it doesnt recognize my n7
any sugestion?
if theres not a way to restore it, is there a way to remove bootloader so i can exchange it at the store?
IAmNice said:
Can you go into fastboot? If you can flash a stock image
Click to expand...
Click to collapse
i managed to load the stock img using the tool kit, the problem was the adb drives, but i managed to install them
now i installed paranoid 2.99,it works fine but when i try to open the play store it doesnt do anything
hey guys, im back with stupid questions...
I wanted to upgrade my Nexus 7 32gb UMTS to 4.3 and used the Nexus 7 Toolkit (by Mark Skippen).
I was on a custom Rom and wanted to get back to Stock, so i could just use the update process by Google.
Downloading and Installing the ROM (including wipe of user data) by the Toolkit seemed to work and didnt show any error messages.
As is tried to boot my device into Android I got stuck in the bootloader.
When I tried to start it, a small white message "Booting failed" appeared in the top left corner. Nothing else happend.
I did everything again, no changes.
Next step was to google for a few mins, then I tried to install a custom recovery via Toolkit (which worked) and install a zip-file Rom via sideload.
Connection was there, the files got pushed onto the device but then "An Error Occured" popped up and everything stopped.
Installing a zip via usb-otg seemed promising, but this got me errors like "unable to mount /system" and "unable to mount /cache"...
when I tried to reboot from TWRP or ClockwordMod Recovery (tried the earlier described things with both recovieres) I got a message saying
"there is no OS installed, are you sure you want to reboot?"
Please help me, I really dont know how to fix this and I will need my Nexus 7 in 2 days (thats why I tried to reinstall and polish everything )
thanks for your help, I really appreciate it
Edit: tl;dr
Stuck in fastboot, no OS is installed. sideload / installing ROM via ADB / installing ROM via usb-otg doenst work, most certainly because /system and /cache cant be mounted
so AFAIK the real problem is that I cant mount those partitions, otherwise I could install a ROM and get out of fastboot/recovery easily. (just mounting them in custom recoveries didnt work btw)
IchStelleDummeFragen said:
hey guys, im back with stupid questions...
I wanted to upgrade my Nexus 7 32gb UMTS to 4.3 and used the Nexus 7 Toolkit (by Mark Skippen).
I was on a custom Rom and wanted to get back to Stock, so i could just use the update process by Google.
Downloading and Installing the ROM (including wipe of user data) by the Toolkit seemed to work and didnt show any error messages.
As is tried to boot my device into Android I got stuck in the bootloader.
When I tried to start it, a small white message "Booting failed" appeared in the top left corner. Nothing else happend.
I did everything again, no changes.
Next step was to google for a few mins, then I tried to install a custom recovery via Toolkit (which worked) and install a zip-file Rom via sideload.
Connection was there, the files got pushed onto the device but then "An Error Occured" popped up and everything stopped.
Installing a zip via usb-otg seemed promising, but this got me errors like "unable to mount /system" and "unable to mount /cache"...
when I tried to reboot from TWRP or ClockwordMod Recovery (tried the earlier described things with both recovieres) I got a message saying
"there is no OS installed, are you sure you want to reboot?"
Please help me, I really dont know how to fix this and I will need my Nexus 7 in 2 days (thats why I tried to reinstall and polish everything )
thanks for your help, I really appreciate it
Edit: tl;dr
Stuck in fastboot, no OS is installed. sideload / installing ROM via ADB / installing ROM via usb-otg doenst work, most certainly because /system and /cache cant be mounted
so AFAIK the real problem is that I cant mount those partitions, otherwise I could install a ROM and get out of fastboot/recovery easily. (just mounting them in custom recoveries didnt work btw)
Click to expand...
Click to collapse
Well . what you can try for now is download the latest factory images and flash them manually via fastboot .. See how that turns out. You can install any ROM via fastboot .. No issues what so ever.
In the factory images there will be a bootloader IMG.. Flash that first and then flash the remaining images ( I suggest manually or via the .bat or .sh files ) and then see if you can boot up android. Mostly should be possible.
And did you try rebooting inspire of the message " no is installed " appearing on the screen ? Maybe it will boot a ROM ? I remember facing this message after just flashing a rom sometimes. So don't worry.
As long as you have access too fast boot everything can be fixed at least w.r.t software.
Red Devil said:
Well . what you can try for now is download the latest factory images and flash them manually via fastboot .. See how that turns out. You can install any ROM via fastboot .. No issues what so ever.
In the factory images there will be a bootloader IMG.. Flash that first and then flash the remaining images ( I suggest manually or via the .bat or .sh files ) and then see if you can boot up android. Mostly should be possible.
Click to expand...
Click to collapse
It worked!!! Thank you so much.
Still wondering why it didnt flash the factory image as a whole while flashing every part step by step worked perfectly fine...
Red Devil said:
And did you try rebooting inspire of the message " no is installed " appearing on the screen ? Maybe it will boot a ROM ? I remember facing this message after just flashing a rom sometimes. So don't worry.
Click to expand...
Click to collapse
Yes, tried booting, but the device just restarted and returned to fastboot mode.
many thanks again
help plz
this is where I am at as well how do you get out of this. kinda a noob at this so a step by step would be great thanks
I've been using the built-in CM updater almost daily for weeks now with no issues. Today, I noticed the CM11 nightlies were out. I excitedly downloaded it and installed it. It rebooted into ClockworkMod Recovery (which I don't recall it ever doing with CM10 nightlies) and gave a "set_metadata_recursive some changes failed . . . (Status 7)" error.
After doing some research, I think the issue may be that I'm still using an outdated CMR v6.0.1.9.
Should I have USB access when in CMR? When I plug the cable in, Windows says the device has malfunctioned
Assuming CMR is my issue, how can I update it without USB access?
I tried a factory reset, but it's still stuck in a boot loop.
I don't recall if USB access to the internal storage card is enabled while in CWM recovery or not, but for sure you can adb sideload any zip if you have adb setup on your PC. I suggest you to update your recovery then manually flash latest cm11. Then you'll use again the built-in updater for upcoming nightlies
clem_ita said:
I don't recall if USB access to the internal storage card is enabled while in CWM recovery or not, but for sure you can adb sideload any zip if you have adb setup on your PC. I suggest you to update your recovery then manually flash latest cm11. Then you'll use again the built-in updater for upcoming nightlies
Click to expand...
Click to collapse
Sideloading is new to me. I'll give it a shot this afternoon and post back. Thanks!
It is your outdated CWM recovery. Get the latest cwm recovery and it will all be fine
Had the same issue with Nexus 4, Nexus 7 and Galaxy S3
Was always caused by older version of cwm
You don't have usb access? Just restore a backup then
If you fastboot flash the new cwm recovery and ROM, wipe cache you will be golden. Without loss of data
Sent from my Nexus 4 using Tapatalk
hi this is the first device ive ever rooted and so while flashing a rom and trying to get it to work i unistalled the os completely. now my nexus 6p wont go past the google white logo. Is there any way to solve this? I do have TWRP recovery installed and my desktop os is mac. ( if that is required) . any help would be appreciated as this is my primary device and i really need it to work
Install Android File Transfer from the following link;
https://www.android.com/filetransfer/
This app will run automatically as soon as you attach your device to mac.
I believe your internal memory will appear while in twrp recovery. Copy your desired rom to internal memory and flash it.
Hi,
I have 2 nexus 7's (2012). One started boot looping a while back but it was on my todo list (and I still had a working one). Then I decided to allow an OTA upgrade to 5.02 and broke that one. I've used NRT 2.19 to reflash stock kitkat (4.4.4) and got that one working again. Having dug out the tools I then tried to fix my other one. It won't take. It seems like I flash and nothing happens. I can't even get twrp installed. NRT boots an image of twrp ok and I've managed to push the twrp image local storage and used twrp to install but nothing seems to work. It says it worked and something worked to fix the other nexus 7. It's like the flash is still locked even though it says it isn't. Any ideas?
Thanks
BTW TWRP gives some errors which are odd. When I try to wipe I get "Error opening: data/data/com.google.android.music/cache/logs:main/com.google.....2011361.log (I/O error)" and also "Error opening: data/data/com.estrongs.android.pop/shared_pref/runtime.xml (I/O error)". I can see these files with TWRP filemanger but I can't delete them or the folder they are in.
Also if I go to downloads then I can't delete a file there either. And since I have repeatedly done wipe date/factory reset I don't know why there is anything in downloads.