I am totally stuck: My nexus 9 does not boot anymore (actually it boot but I have a black screen with battery and wifi logo at the right hand corner.
I only can access the boot loader (fast boot mode) and the default android recovery which no allow me to do a lot of things...
I tried to download the Nexus Root Toolkit to try some fix but EOM is locked and adb debugging is not activated in OS (and OS crashes).
Please do you have a solution for me ? Thanks a lot...
Did this happen after an OTA update by any chance?
If so you could try the following: -
If you can get into recovery, you might be able to sideload the OTA again: - http://forum.xda-developers.com/nexus-9/help/failed-marshmallow-update-stock-android-t3226704
February OTA available from here https://gist.github.com/jduck/3ea03fb3ec1a55544842
Click to expand...
Click to collapse
If it was not from OTA update a factory reset might resolve your problems.
Thank you for the reply
I tried to download an update and transferred it via adb sideload, but I got the error "system partition has unexpected contents".
I also tried to do a factory reset (from HBOOT and from android recovery), but now the system crashes on the setup wizard.
I get "Setup Wizard isn't responding.", and "Unfortunately, System UI has stopped." and I cannot open settings, enable usb debugging and unlock EOM lock.
poussinvert said:
Thank you for the reply
I tried to download an update and transferred it via adb sideload, but I got the error "system partition has unexpected contents".
I also tried to do a factory reset (from HBOOT and from android recovery), but now the system crashes on the setup wizard.
I get "Setup Wizard isn't responding.", and "Unfortunately, System UI has stopped." and I cannot open settings, enable usb debugging and unlock EOM lock.
Click to expand...
Click to collapse
Any chance it is still under warranty? RMA it with Google/HTC (or wherever you bought it).
Yes... this is probably my last chance.. unfortunately
If anyone else has another solution I'm interested
Is it possible to install a new rom with adb sideload from the default recovery ?
Is there a solution to reinstall the original rom without EOM unlocked ?
Related
I decided to root my ME302C tablet to remove some bloatware using an app that required a rooted device. I had the latest firmware so I couldn't use any of the rooting guides online, but I tried Kingo Root, an automatic rooting PC program (all I had to do was enabled USB Debugging), and it worked, at least for one session (after a reboot, it appears to stop working).
After I removed the bloatware, I reset the tablet to its factory state without using the remove root option in Kingo SuperUser (not SuperSU) (I did not know that the option existed). I'm not sure if it would have made a difference if I had used that option, but after resetting, Android booted properly, but I had no lock screen, broken default browser, unresponsive on-screen home button, no notification area, and I lost some options that appeared when powering off (airplane mode and mute). I occasionally get "unfortunately *app* has stopped" errors, but it doesn't appear to affect anything. The tablet works fine otherwise.
I would really appreciate it if someone could direct me on how to restore the default firmware entirely. If I factory-reset, it just removes the apps and resets the settings without affecting the system (clears cache and user partitions), and this website confirms that: search for Isn't Factory Reset exactly the same as wiping /data and /cache? stackexchange. I can't link to it directly. Sorry.
I found a post about an unrelated problem while typing the title where somebody attempted to root using an unofficial firmware update and totally bricked their FHD 10. They ran these commands:
fastboot erase cache
fastboot erase system
fastboot flash update "updatename".zip
Suppose that instead of using the unofficial, rooted update.zip he used, I used an official one from this page (it contains links to updates for my tablet's firmware): search for me302c asus. I can't link to it directly. Sorry.
Would that work? I am assuming that a firmware update is a copy of the entire firmware.
If I could use an update, could you please let me know how to flash it exactly? I can boot into recovery mode, Droidboot Provision OS. It has an option to update the firmware, I believe, called "SD DOWNLOAD". If I place an update.zip file named ASUS_BUNDLE.zip on an external SD card and use the option, it'll look like it's updating (there are a few screens, I think they say "clearing cache" and something else, but nothing mentioned of the system partition) - however, it just acts as if it is a factory reset, taking me back to that state where things are borken.
SD Download doesn't look like it is doing something for every random ZIP you put on the SD card, because if I use a ZIP file that has, say, a picture of my cat enclosed, it will not do anything. I think that it does do something with the ASUS_BUNDLE.ZIP, but just not anything that solves my problem.
In Droidboot, if I plug a USB cable into the tablet and the other end into my PC, an icon will appear saying "USB connected". If I enable USB debugging in Android and connect the tablet to my PC in the Droidboot Provision OS recovery mode, should I run the commands then?
I realize that this is a mouthful and thank you for taking the time to read my post.
Did you solve this in the end?
Yes.
_MsG_ said:
Did you solve this in the end?
Click to expand...
Click to collapse
I used the method that I posted to fix the tablet.
Hi I have moto G 2015 osprey XT1541, its unlocked running cyanogenmod
I recently upgraded to CM 14 experienced problems instantly, all the google apps wpuld crash.
Reverted back to CM 12 which worked and it had an error whilst upgrading in recovery,
something like
E:Failed to map file
E:Error exit from the fuse process :0
Installation Failed Installation Aborted
I have tried multiple roms, all come back with same error message. The recovery on the phone is the cyanogenmod one. Also in recovery if I do system reset I get
E: Failed to mount /data (permission denied)
I am having to try installing roms via sdcard as the phone is not recognised by my computer.
Any Ideas?
I would format userdata in bootloader then install TWRP and use that to install the next rom.
es0tericcha0s said:
I would format userdata in bootloader then install TWRP and use that to install the next rom.
Click to expand...
Click to collapse
How do I format userdata? I dont have that option in the bootloader. When I try to install anything using cyanogemod recovery including TWRP I get the same error message.
fastboot format userdata
fastboot format cache
If that doesn't work then you'll want to go back to complete stock with the original firmware for your variant (and carrier if yours came from one originally).
The phone cannot connect to PC with USB for some reason. So I cant use fastboot. I know its not the cable/PC as it works with my tablet so must be the phone.
I have tried wiping data and factory reset in recovery and this does not solve the problem, still stuck in boot loop and recovery cannot flash any roms.
AndyGLowe said:
The phone cannot connect to PC with USB for some reason. So I cant use fastboot. I know its not the cable/PC as it works with my tablet so must be the phone.
I have tried wiping data and factory reset in recovery and this does not solve the problem, still stuck in boot loop and recovery cannot flash any roms.
Click to expand...
Click to collapse
Check out the Device Manager (assuming you're using Windows...) and see if the driver is loading correctly. If not, you should be able to manually update the driver. This is the most common problem that would cause this. Even if the phone is borked, fastboot mode should work and the PC should be able to load the drivers. If that fails, try other ports on your PC or another PC altogether.
Uninstall all the Moto drivers, reboot, reinstall and look into RSD Lite if all else fails.
es0tericcha0s said:
Check out the Device Manager (assuming you're using Windows...) and see if the driver is loading correctly. If not, you should be able to manually update the driver. This is the most common problem that would cause this. Even if the phone is borked, fastboot mode should work and the PC should be able to load the drivers. If that fails, try other ports on your PC or another PC altogether.
Uninstall all the Moto drivers, reboot, reinstall and look into RSD Lite if all else fails.
Click to expand...
Click to collapse
I doesn't even show in Device Manager, I have tried another system with Win 7 on and that comes up with a notification saying a unrecognised device has been attached. But it doesn't make a difference if you install the drivers or look in device manager, had exclamation mark next to device but you cant do anything. I also have Ubuntu dual loaded on this system and that doesn't recognise it either.
Same issue on Xperia ZL... This CM14 ruined my phone.. exactly same issue... Some one help plzzzzzzzzzzzzzzzz
sahil soni said:
Same issue on Xperia ZL... This CM14 ruined my phone.. exactly same issue... Some one help plzzzzzzzzzzzzzzzz
Click to expand...
Click to collapse
did you guys solve your problem I have the same exact issues?
Hello,
I'm stuck into a similar situation reported here [Q] Volume down not working, how to get into recovery? on my LG G5 H850.
I had MM installed and finally wanted to upgrade to N having heared the good news concerning Xposed's availability.
So I've patched the bootloader and then a 20k Complete Stock ROM through TWRP still installed and fully working at this moment.
Boot back to N. OK
Once the upgrade process have finished I had the surprise to discover that I have all my previous apps and settings where still present but I have dozens of FCs polluting the screen !!
e.g. I cannot access com.android.settings
The phone is almost unusable :crying:
Before the upgrade I made some wipes (cache, system I guess and if I look back into my memory) but I don't remember having made a factory reset ... my bad
I don't have root anymore :good:
I made
Code:
adb reboot bootloader
fastboot flash recovery twrp-3.1.x.x.x.img
but cannot "stick" it coz of my volDown button HS
Code:
adb reboot recovery
finishes to a "No command" screen (maybe because of an un"stick"ed twrp)
Code:
adb reboot bootloader
fastboot boot twrp-3.1.x.x.x.img
but got a "FAILED (remote: unknown command)" response
I still have the Official TWRP app manager installer but cannot install a new one (because of the "su" lack)
Questions :
Is there a way to reinstall "su" binaries in these conditions and without TWRP ?
Is there a way to "live" boot into a recovery ?
What can I do with "fastboot boot <something>" ?
Pleease someone ... one good news :fingers-crossed:
i recently got into playing with andorid , and kinda bootlooped my device,
its htc nexus 9 wifi , i rooted it with wrong version supersu
inject.img
patched.img
then it went into bootloop since im new , and panicked i factory reset it , now its stuck in bootloop and i cant enable developer mode.
can i use odin like solution that can get me in , or what are my options
thanks for reading
rohanzakie said:
i recently got into playing with andorid , and kinda bootlooped my device,
its htc nexus 9 wifi , i rooted it with wrong version supersu
inject.img
patched.img
then it went into bootloop since im new , and panicked i factory reset it , now its stuck in bootloop and i cant enable developer mode.
can i use odin like solution that can get me in , or what are my options
thanks for reading
Click to expand...
Click to collapse
If you can boot into bootloader, you can fastboot flash the images from https://developers.google.com/android/images (or just try running the entire N9F27N script) from your fastboot folder in cmd prompt or the Mac equivalent if you use Apple.
Sent from my Nexus 9 using Tapatalk
usb-debug is not enabled.
the thing is , when i rooted i got locked out then i factory reseted it , but it still is in bootloop,
i am unable to connect with device this is what i see when run the script ,
the cmd prompet say "<waiting for device >"
does it ever happened to anyone , getting locked without getting developer mode > usb-debug enabled , and then flashing factory rom ?
Can you still access TWRP, if it was already on the device.
Flash any custom rom, enable the option and flash stock again (if you want).
If it is stock recovery, sideload an OTA image instead.
https://developers.google.com/android/ota
Manually boot recovery and you shouldn't need usb-debug enabled, I hope.
A bit of research and it is required unfortunately
Edit: You don't need usb-debugging for fastboot flashing.
Also Nexus Root Toolkit might prove helpful to setup drivers on your pc and restore your device to working order.
^^^ It is out of date software, so hesitant to recommend it.
rohanzakie said:
the thing is , when i rooted i got locked out then i factory reseted it , but it still is in bootloop,
i am unable to connect with device this is what i see when run the script ,
the cmd prompet say "<waiting for device >"
does it ever happened to anyone , getting locked without getting developer mode > usb-debug enabled , and then flashing factory rom ?
Click to expand...
Click to collapse
Boot to bootloader and use fastboot commands. Fastboot flash system system.img
Etc.
Use the files extracted from factory image.
rohanzakie said:
the cmd prompet say ""
Click to expand...
Click to collapse
I've definitely had this experience. You can try disconnecting the cable then reconnecting. When that doesn't work, you have to remove all the drivers or at least run through "updating" the Android drivers in hardware settings. You won't actually be updating drivers just re-installing from the PC. Wug's toolkit mentioned above may be your best choice if you don't have TWRP. The toolkit will provide you with an exe called usbdeview which enables driver removal. I didn't mention an OTA sideload because I thought you did need ADB for that. If you can get PC to recognize the device in cmd, then you can fastboot flash images.
Sent from my Nexus 5X using Tapatalk
I have 2 of these REVVL + phones and both of them are FRP Locked. When you go to install an apk, you can download the file but the package installer fails right away. Ive tried installing from system storage, installing in safe mode and the trippy thing about it is that both phones do that exact same thing. So I was going to just sideload with the adb or fastboot but theres no adb update or SD card update option in the recovery menu. Tried to find a glitch that would either make setup wizard crash or turn the wifi off at the same time it is searching updates so it would let me set a password or something. Any ideas are greatly appprrishilated!