Malfunction " x " appears on the screen !! help me what is going on
Haha... you'll need more information than that if you want real help.
Based on the limited information though I suspect your phone is stuck in a bootloop. I'd hook it up to the PC via USB and check the logcat. Probably something screwed up.. Maybe time to restore your latest backup.
Did you flash any ROM if so, did you clean your Dalvic+REgular Cache
If you don't have an Recovery:
- Connect your Micro SD on PC
- Download and insert on SD the stock ROM of your Nexus One
- Power ON your Nexus with Volume Down Pressed.
- Autmotically Restore Nexus (You should say Yes xD)
At this time, you decide if you want to be root and install other ROM
you better just list your setup info before doing anything
locked/unlocked bootloader
rooted/unrooted
which recovery are you using
what rom are you running stock/custom
what were you doing when this happened
a couple safe things you can do in meantime is to pull battery and reinsert and power on
if it goes back to X, pull battery and DO NOT power on. Hold down the pwr button and trackball at same time and see if you can get into recovery
the third is hold down trackball/vol-/power at same time while X is on screen and see if you can get to recovery that way
if you can't get to recovery you will need to fastboot new recovery, assuming you are unlocked
once you get into recovery do a nandroid if you are rooted
and copy it to pc as a secondary backup
it is possible you may need to try the passimg method in wiki
http://forum.xda-developers.com/wiki/Nexus_One/Guides_&_Tutorials#Unroot_.2F_Restore_your_Nexus
also to do fastboot commands you need usb debugging selected on phone--hope it is
Hello, i have a similar problem with my n1
the phone starts and just shows the nexus X - (waited for 15 min. nothing happend)
i can go to the bootloader / fastboot menu with PWR + (Vol-) but i can not go to the recovery mode. -> the phone reboots and get stuck at the X
the phone is rooted
blackrose / hboot 7.35.5017
radio 5.12.00.08
recovery was ext4
i had a german ics miui rom installed and tryed to install the latest ics miui us rom after it didn't booted the miui us rom i turned the phone off and tryed a few hours later to turn it on to reflash the german ics miui rom.
1.)
i tryed to install a new recovery image ->
recovery-clockwork-5.0.2.0-passion &
recovery-RA-passion-v2.2.1
(still get stuck at the X if i try to go to recovery mode)
2.)
i tryed this one with the passimg.zip but nothing happens if i put in the sd card :/
(with nothing i mean the green text show that the sd card is checking for PASSDIAG.zip and PASSIMG.zip but dosn't found it)
i also tryed:
3.)
erased boot
flash boot from passimg.zip (PASSIMG_Passion_Google_WWE_2.18.1700.1_FRG83_release_signed)
4.)
erased cache
erased userdata
started again with 1.)
5.)
got frustrated and erased system -.-
any ideas?
study it ,thank you
study it ,thank you
Hmm, sorry if its obvious but i have no idea what it could be or what i have to search to find the solution. Would be nice if you could give me a hint. Of course im not asking for a step by step solution. Thank you.
Send from my awesome SE K800i
not sure why you are flashing boot images
do you have a nandroid--copy your sdcard with the nandroid to pc--all of sdcard
are you flashing thru fastboot in command window
did you read my post above on getting to the fastboot screen--can you do that--the one with the 3 androids
pwr/vol-/trackball same time, may take 20-30 seconds
if you can get there, put your recovery image in your fastboot folder on pc, normally tools--assuming you have sdk installed, your phone must have usb debugging checked--I hope
open a command window and change directory to the tools folder or wherever the fastboot.exe file is. Something like:
cd/
cd/ android/android-sdk-windows/tools for me
then on same line type
fastboot devices (it should show your phone H#)
fastboot erase system
fastboot flash recovery recovery.img (or the exact name of the recovery image, checked by right clicking on the img file in your tools folder and looking under properties)
I would use amonra you listed above and check the md5 if possible
hopefully the recovery will flash
if not you can go to the wiki link i posted above and try passimg metthod from there, use correct one. don't add the .zip. Windows will had it automatically.
a side note, DON"T flash different roms without wiping all including System 3 times before flashing--prevents a lot of problems
rugmankc said:
a side note, DON"T flash different roms without wiping all including System 3 times before flashing--prevents a lot of problems
Click to expand...
Click to collapse
thank you very much
i already tryed everything else what you wrote but i didn't wiped 3 times... after erasing recovery partition 3 times i was able to flash a new recovery and it started.
Thanks a lot!
Glad that you got it
Last night, I tried to flash gapps using goomanager. I must have used the wrong gapp files. Now, I have a problem. When I turn on tablet, an endless loop of mesages including "Unfortunately Setup Wizard has stopped working". Now I cannot access anything; no notifications, no access to settings, etc. Anyone have an idea where I can start to troubleshoot this?
That seems like a lot of work compared to just dirty-flashing the same ROM you were using before the gapps flash.
If you have a Nandroid backup using TWRP, you could just selectively restore the system partition.
OR, just start over by doing a factory reset in the custom recovery and then re-installing a ROM from scratch. (You didn't say whether saving data was of any concern to you.)
bftb0 said:
That seems like a lot of work compared to just dirty-flashing the same ROM you were using before the gapps flash.
If you have a Nandroid backup using TWRP, you could just selectively restore the system partition.
OR, just start over by doing a factory reset in the custom recovery and then re-installing a ROM from scratch. (You didn't say whether saving data was of any concern to you.)
Click to expand...
Click to collapse
Saving data is not important. I should have a backup of the Nandroid. I made one after rooting the tablet. The part that confuses me is how to get to those options? I can get into fastboot mode on the tablet. However, from the methods I've tried, they all say I do not have abd. I cannot access usb debugging. How would I reset to factory settings?
captainNT said:
Saving data is not important. I should have a backup of the Nandroid. I made one after rooting the tablet. The part that confuses me is how to get to those options? I can get into fastboot mode on the tablet. However, from the methods I've tried, they all say I do not have abd. I cannot access usb debugging. How would I reset to factory settings?
Click to expand...
Click to collapse
What custom recovery is on the tablet?
I would think that no matter what installer you used (I'm not familiar with "goo manager"), the ROM file that you downloaded would still be present on your device's /sdcard.
If that is the case, you boot your custom recovery (get the tablet into fastboot mode, and press the vol-down or vol-up button to until "start recovery" shows up, and then press the Power button).
From there perform a factory reset and then flash the ROM on your /sdcard from the custom recovery menu.
Long term you really need to straighten out your driver issues. You can see why, right? Alternatively, the TWRP recovery can mount USB flash drives in order to get files to a blank tablet that still has a working custom recovery - you just need the USB key drive and a working OTG cable.
bftb0 said:
What custom recovery is on the tablet?
I would think that no matter what installer you used (I'm not familiar with "goo manager"), the ROM file that you downloaded would still be present on your device's /sdcard.
If that is the case, you boot your custom recovery (get the tablet into fastboot mode, and press the vol-down or vol-up button to until "start recovery" shows up, and then press the Power button).
From there perform a factory reset and then flash the ROM on your /sdcard from the custom recovery menu.
Long term you really need to straighten out your driver issues. You can see why, right? Alternatively, the TWRP recovery can mount USB flash drives in order to get files to a blank tablet that still has a working custom recovery - you just need the USB key drive and a working OTG cable.
Click to expand...
Click to collapse
New problem now. I think I have no custom recovery installed. When I go into recovery from fastboot mode, it shows the droid with a red exclamation mark. Trying to diagnose that now but I can't access the tablet settings.
captainNT said:
New problem now. I think I have no custom recovery installed. When I go into recovery from fastboot mode, it shows the droid with a red exclamation mark. Trying to diagnose that now but I can't access the tablet settings.
Click to expand...
Click to collapse
That is the stock recovery.
Which means you need to get fastboot working from a PC; you really have no choice any longer. Have a look at the fastboot / unroot sticky thread.
Used a toolkit to get back to stock settings. Good to go. Thank you.
Hi,
my Nexus 4 is stuck in a boot loop since 2 days. I found it turned off and assumed it crashed (has done that once or twice before), but after turning it on it's gets stuck on the boot up screen. I've tried restarting it numerous times, left it on the boot screen for hours - nothing.
I can access the recovery mode and according to most things I've found while searching the internet for a solution a "wipe data/factory reset" would hopefully do the trick, but the thing is... I haven't backed up my device in ages. (Stupid, I know.) I'm travelling and took a lot of pictures that I would hate to loose.
Is there any way to save them? I don't care for app data or anything else.
I wouldn't mind rooting it (was thinking about doing that anyway), but I'm pretty much a n00b when it comes to Android, haven't done more with it than simply using it.
I have read up quite a bit about rooting in the last two days (here on the forum and everywhere else) but I'm still not sure how exactly to do it, since all methods seem to require unlocking the bootloader and therefore deleting my photos (or just don't give much in the way of explanation).
I'm using a mac, but if necessary I also have Windows installed. I have installed Adb and fastboot following this guide.
The phone is not rooted, I don't have developer options or USB debugging enabled and it's running on 4.4.4.
I would be really grateful for help.
If you can boot into the bootloader you can install a custom recovery, I'd recommend twrp. Then booting into the custom recovery you could use adb to pull files off your device . But your bootloader needs to be unlocked. If it isn't I'm afraid you won't be able to get your photos
Sent from my SAMSUNG-SGH-I957 using XDA Free mobile app
bootloop issue
A.
Try to go into safe mode and backup your data.
Boot into Safe Mode:
1. Press/Hold Power button until power menu shows up
2. Tap/Hold Power off option
3. Choose OK to reboot in safe mode
B.
For bootloop problem:
Boot into Stock Recovery
1. Power+VolUp while booting to enter recovery
2. You can release buttons after you see Google on screen
(Note: Must be this sequence Press/Hold Power, THEN Press/Release VolUp, release Power)
3. Android fallen down screen - VolUp to toggle recovery menu
Now wipe Cache & Dalvik Cache in recovery and reboot the phone.
C.
If the (Option B) does not solved then try to flash the stock rom with the below given mentioned steps.
First download any stock rom and also the related usb drivers. Install the drivers into the PC.
Boot into the bootloader.
Open (fastboot.exe) Cmd prompt as admin. Put the stock rom into that particular folder.
fastboot flash bootloader filename.img
reboot the phone and return back to the bootloader.
Then, we will flash all other partitions.
fastboot flash radio filename.img
Again reboot the phone and go back into the bootloader
fastboot flash boot filename.
fastboot flash recovery filename.img
fastboot flash userdata filename.img
fastboot flash system filename.img
If you want to relock the bootloader of your device after flashing the device, put the device back in fastboot mode. Then type in the following command in the Terminal or Command Window you had opened earlier -:
fastboot oem lock
This will re-lock the bootloader of your Nexus device, restoring your warranty and putting the device back to complete stock.
I hope this helps you out.
Thank you, but is there a way to boot into safe mode if the phone isn't turned on? I can not get to the power menu since I can't turn the phone on...
I can only access the recovery menu.
Data backup
Alternate method you can do is that you have to download a software by name 'DROID EXPLORER' - (try to google it) you will find this software from the internet. Then install the software on your PC or Laptop. Once you open the software it will take some time to download the sdk files from the internet then install the windows sdk files also.
Later you go into the recovery mode with the usb cable connected to your PC. Then open the Droid Explorer software you will see your phone connected picture. Now double click and open it go to sdcard and copy all your pictures and other files to your system.
Finally, Once you backed up all your files now you can reflash with the proper rom from the recovery mode. From directly inserting the rom.zip file into the sdcard and run the custom rom after you wipe the partitions properly in recovery.
Note: Before wiping the partitions always unmount the system, data, cache and then wipe it.
I presume I'm stuck, but just in case…
I used TWRP to flash the latest LineageOS, and for some reason the bootloader got erased/corrupted (I'm not entirely sure how this can happen).
As a result, the tablet is now stuck in APX mode when booting up. Inconvenient to say the least…
I can still access TWRP, but any attempt to access Fastboot (ie adb reboot bootloader) results into the unit getting into NVIDIA recovery mode (ie APX)
And of course I don't have a backup of the boot keys.
Since I can access TWRP, is there anyway I can get access to the boot keys to reconstruct my bootloader ?
Regards
Ashram56 said:
I presume I'm stuck, but just in case…
I used TWRP to flash the latest LineageOS, and for some reason the bootloader got erased/corrupted (I'm not entirely sure how this can happen).
As a result, the tablet is now stuck in APX mode when booting up. Inconvenient to say the least…
I can still access TWRP, but any attempt to access Fastboot (ie adb reboot bootloader) results into the unit getting into NVIDIA recovery mode (ie APX)
And of course I don't have a backup of the boot keys.
Since I can access TWRP, is there anyway I can get access to the boot keys to reconstruct my bootloader ?
Regards
Click to expand...
Click to collapse
Hi, Ashram56...
Just to confirm, we are talking about the Nexus 7 (2012) tablet here? Because if you can still access TWRP, the bootloader is not 'dead'. If the bootloader were corrupted or erased, the device would not boot at all... ever! Not even in TWRP!
If it is a Nexus 7, you should be able to manually boot the device into its bootloader by long pressing and holding the volume down button, and at the same time, press the power button.
With regard to doing it via a command prompt, I think you need...
Code:
fastboot reboot bootloader
...as ADB commands only work when Android is fully booted.
Hope this helps.
Rgrds,
Ged.
GedBlake said:
Hi, Ashram56...
Just to confirm, we are talking about the Nexus 7 (2012) tablet here? Because if you can still access TWRP, the bootloader is not 'dead'. If the bootloader were corrupted or erased, the device would not boot at all... ever! Not even in TWRP!
If it is a Nexus 7, you should be able to manually boot the device into its bootloader by long pressing and holding the volume down button, and at the same time, press the power button.
With regard to doing it via a command prompt, I think you need...
Code:
fastboot reboot bootloader
...as ADB commands only work when Android is fully booted.
Hope this helps.
Rgrds,
Ged.
Click to expand...
Click to collapse
Yes this is a Nexus 7 2012
However that's the point: I can boot TWRP (hence adb mode), however if I select "adb reboot bootloader", or if I select "Bootloader" using the Power+Volume Down menu, I don't get into fastboot, I only get into APX, which is recovery
I was under the impression that the bootloader was corrupted, I'm glad this is not the case. Now I just need to figure out how to recover from where I am at this point
And to clarify even further:
- I tried to use TWRP to flash boot.img that I extracted from LineageOS, still boots into recovery
- Did the same with the recovery image, same behaviour
- I realized that I had performed (my bad) a complete "internal storage" wipe, after flashing originally, which might have caused the issue
Bootloader indeed seems to be intact, the info page on the recovery menu (ie before booting TWRP) states 4.23
Ashram56 said:
Yes this is a Nexus 7 2012
However that's the point: I can boot TWRP (hence adb mode), however if I select "adb reboot bootloader", or if I select "Bootloader" using the Power+Volume Down menu, I don't get into fastboot, I only get into APX, which is recovery
I was under the impression that the bootloader was corrupted, I'm glad this is not the case. Now I just need to figure out how to recover from where I am at this point
Click to expand...
Click to collapse
I suspect some confusion of technical terms is going on here.
Can you as describe, as precisely as possible, exactly what your Nexus 7 is displaying, when you enter what you think is, or might be, APX mode.
A picture/photograph would be even better.
APX/nvFlash mode is NOT Recovery. These are very, very different things.
Recovery is either the devices Stock Recovery, or a Custom Recovery, such as TWRP or CWM.
Rgrds,
Ged.
---------- Post added at 07:07 PM ---------- Previous post was at 06:52 PM ----------
Ashram56 said:
And to clarify even further:
- I tried to use TWRP to flash boot.img that I extracted from LineageOS, still boots into recovery
- Did the same with the recovery image, same behaviour
- I realized that I had performed (my bad) a complete "internal storage" wipe, after flashing originally, which might have caused the issue
Bootloader indeed seems to be intact, the info page on the recovery menu (ie before booting TWRP) states 4.23
Click to expand...
Click to collapse
OK, just seen this post.
You dont use TWRP to flash .img files, you use fastboot, so for example, you'd use the following command lines...
Code:
fastboot flash boot [name-of-boot-file].img
...or...
Code:
fastboot flash recovery [name-of-recovery-file].img
...with the Nexus 7 booted into fastboot mode and USB connected to a laptop or a PC.
Rgrds,
Ged.
Hi, again Ashram56...
Some further thoughts regarding your situation...
Ashram56 said:
Bootloader indeed seems to be intact, the info page on the recovery menu (ie before booting TWRP) states 4.23
Click to expand...
Click to collapse
So that would be on the fastboot menu then, and not the recovery menu. I'm not trying to be needlessly pedantic here, but when dealing with this kind of thing, and when asking for advice, it's important to use the correct terms, otherwise confusion can arise.
Anyhow, your reporting of this indicates that your Nexus 7's bootloader is alive and well, which means the device is almost certainly recoverable.
Furthermore, bootloader v4.23 is the latest and the very last bootloader version this device will ever receive.
Whatever you chose to do, I'd strongly recommend against reflashing the bootloader again, as this process is the 'Achilles Heel' of the Nexus 7, and it's a potential terminal weakness. A bad bootloader flash, perhaps via a dodgy USB connection, can corrupt the bootloader, and render the device permanently hardbricked. And the only realistic solution to that is a motherboard replacement.
And which brings me to this...
Ashram56 said:
And of course I don't have a backup of the boot keys.
Since I can access TWRP, is there anyway I can get access to the boot keys to reconstruct my bootloader ?
Click to expand...
Click to collapse
I'm aware that you mentioned in your original post, something you called 'boot keys'. I assume you refer to the Nexus 7 'flatline' procedure for generating bootloader 'blobs', described here...
https://forum.xda-developers.com/showthread.php?t=2455927
Such 'blobs' can ONLY be used on the original Nexus 7 with which they were originally generated. They are NOT transferable from one N7 to another N7.
Running the 'flatline' procedure is a fairly high risk venture, and requires a good knowledge and a high level of familiarity with using fastboot commands, because it involves flashing a special build of the bootloader. I ran it myself, a few years ago, and it's a pretty nerve wracking experience, wondering if your Nexus 7 will ever boot again!
Mine did, and I now have my N7 bootloader 'blobs', stored on my laptop ~ but I have absolutely no idea at all, if they'd be of any use should I have need to dig myself out of an APX shaped hole!
Fortunately that hasn't happened yet, and my 'blobs' will now likely forever remain untested, as I rarely use my Nexus 7 these days.
------------------------------------
Ashram56 said:
I used TWRP to flash the latest LineageOS, and for some reason the bootloader got erased/corrupted (I'm not entirely sure how this can happen
Click to expand...
Click to collapse
...And it can't happen!. A TWRP flash of a Custom ROM, such as LineageOS, goes nowhere near the bootloader partition. It doesn't touch it at all. Same with a TWRP Nandroid restore. Bootloader partition is left alone, unmodified and untouched.
------------------------------------
Anyhow, and in conclusion, it sounds like your bootloader is still working, and you should therefore be able to recover the device.
The easiest way of doing this, is to download a Google Factory Stock image for the Nexus 7 and flash it via fastboot, and which you can find here...
https://developers.google.com/android/images#nakasi
------------------------------------
Good luck with getting your Nexus 7 up and running again, and I hope this helps.
Rgrds,
Ged.
You are correct to ask to be very precise, as words have different meaning, and can lead to confusion, as is the case here
I used the word "recovery" by mistake (I'm actually in HW Embedded design, and APX mode is called "recovery" mode in a lot of Tegra related literature). So to be clear, I will only refer to APX mode.
APX mode is essentially a mode the chip enters when it cannot find a valid bootloader, or when the bootloader fails to load a valid kernel (see similar details here for those who really want to get their head spinning: http://developer.nvidia.com/embedded/dlc/jetson-fuse-burning-secure-boot-28-2-ga , need registration to access the document though). You can also access this mode by asserting some HW pins at boot up (which are not exposed on the Nexus 7 2012 anyway)
Screen is black in this case, since the kernel has not loaded
Symptoms I have:
- I can access the "Boot select" menu, through Power+Volume- menu
- I can access from the "Recovery", which launches TWRP
- If I use the "Reboot" option from TWRP, or the "Bootloader" option from the "Boot select" menu in 1/, I get a black screen, and the tablet appears to be in APX mode (seen through simple linux lsusb command)
It turns out that in "some" instances I was able to actually turn on the tablet and boot the OS, but I can't figure what sequences (ie I can't find a reproducible way of booting correctly, 9 times out of 10 I get into APX mode).
I'll try to figure out further what the heck is going on. My suspicion is that the bootloader is attempting to load the kernel, and the first copy is corrupted. In most Tegra implementations, this should be covered through redudancy of the kernel at multiple locations (same for bootloader actually), but I'm not knowledgeable enough about Android to determine if this is the case as well here.
Thanks for the help in any case
And to add to that:
when in "Boot select" menu, units does appear in Fastboot mode, however "fastboot reboot bootloader" gets me into APX mode (black screen, tablet seen as APX device, fastboot and adb not functional), same as booting to Bootloader from TWRP or "select" menu.
I'm quite puzzled...
Just a note: one time out of 10 I can boot into the OS
I'll settle for that for the moment
Reviving this 4y old thread...
So, recently I unburied my Nexus 7, to use it as a secondary device for some home automation application.
Took me a while to find my bearings again, but here's a summary of where I stand:
- If I power on normally (ie power button) the tablet for the first time or do a reboot (either through the UI or the adb command), it enters "NVIDIA Tegra recovery mode", ie device driver appears as APX
- When is this mode, if I press the power button for 10s or so it powers off
- When fully off, if I simultaneously press Volume - + power button, I can enter the bootloader mode (ie Fastboot mode), with the small droid, the info text at the bottom left, and a big "Start" button on the upper right corner.
Info reported in the bottom left in that case:
Fastboot mode
Product name - grouper
Variant name - grouper
HW version - ER3
Bootloader version - 4.23
Basedband version - N/A
Serial Number - sequence of numbers
Signing - not defined yet
Lock state - Unlocked
- in this mode, the volume keys do not have any effect, I can't select anything, only "Start" is available. I can indeed "Start" the tablet using the power button
It starts Android (in my case LineageOS), but in safe mode only, so limited functionality
And I'm stuck, since I can't use the tablet.
I know it's a very old thread, but if anyone has any clue on how to resolve this, I'm interested
Regards
[EDIT] Some additionnal data
- First, looks like my volume buttons are actually broken. I don't get any response inside Android UI, that would explain why I can't select anything in when in fastboot besides "Start" option
- I reverted back to the stock image, but I'm still stuck in safe mode.
I can't install LineageOS back, since I can't navigate in fastboot menu and access twrp (unless I can do that using a fastboot command) ?