" x " appears on the screen - Nexus One General

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

Related

Fastboot> Recovery dosen't find *.img file on SD card

Hi Guys!
I am trying to root my nexus, unlocked it, installed the right usb drivers, I can see the phone and everything looks right.
Downloaded Superboot for ERE27 with himem enabled and ran this. no problem.
I put the img file on the SD card and when I boot the phone in Fastboot / Recovery it does not find and img files on the SD card.
I tried 2 different cards and also different img files.
When I do this I get first the message no images found than I see the droid with a triangle and a ! in it. - Have to pull the battery.
Ideas anyone?
Thanks
What are you trying to do?
1) you had to unlock the bootloader which enables you to install a new recovery image (which is needed to allow you to install new roms)
2) you had to apply the recovery image Amon RA via a command prompt and a batch file if you use Windows. The phone's USB connection needs to be in development mode and once the batch file executes and successfully finishes you need to reboot the phone.
3) you restart the phone into bootloader mode, use the volume rocker to select the recovery console. If you end up with an andriod and exclamation symbol the Amon RA recovery file was not installed.
4) the new recovery console allows you to clean the SD card. Install roms from the SD card and some other commands. The Roms for the Andriod are in ZIP format and do not need to be unziped. In other words all you need to copy to the SD card is the full ZIP file (approx 75MB) and install that directly from the recovery console.
If your android stays in the booting sequence which is shown as the X with flying little pixels, it's most likely because you did not wipe the device clean first. That item is in the recovery console as well.
Hope this helps. I am just as new to this as you are.
You didn't unzip them did you?
You're trying to root with superboot. Great, but the recovery is not capable of flashing .img files, only .zip updates and roms and such. .img files have to be flashed using fastboot, not recovery, and are flashed from the connected computer.
If you read the superboot instructions from wherever you got the file, you'll see that you have to put the .img in the same directory ON YOUR COMPUTER as fastboot, connect via USB, boot the phone into fastboot, then enter the appropriate command line on the computer to flash the file.
If you've done that, then you are officially DONE with the rooting process.
Also, make damn sure that the superboot version matches the software version on your phone. They're both ERE27, right?
I'm not sure what anosis's post is talking about, but that looks more like the process for installing a custom rom (ie cyanogenmod), than rooting.
To root your phone, you DO NOT need Amon-RA's recovery. You only need that if you want to install custom roms, etc. It wont hurt to have it, as it includes many more functions than the stock recovery, but just to root, you don't need it.
Summary:
If you flashed the superboot.img from your computer via fastboot, your phone is rooted. Done.
You don't need to do anything in the recovery at all for rooting. Only for installing update.zips and custom rom.zips.
Hey, So I have been scouring the forums trying to find some answers about this and you seem to be the closet to my situation. Here is what I did:
So I was running a CM9 Aplha, reverted back to stock 2.3.6 [1ada25375426.signed-soju-ota-189904.1ada2537]) so that I could then apply ICS update [VQ8PQk_V]) which I sucessfully did. This was about a month ago and it was all going well.
Then yesterday I wanted to upgrade to 4.0.4 [hR7QFEtn] so I did and superuser wasn't working properly but then I reinstalled it and got it to work. However I got to the point where everything was working fine EXCEPT for the Google Play store kept on force closing. I spent hours trying last night and could not find a solution.
I tried restoring the previous ICS update that I had and it worked, and then I tried updating again. Also side: My clockwork was on the fritz lately so I was using Zedowmaxs force into clockwork recovery image [fastboot boot recovery3101.img] to force it in sometimes.
Anyway bottom line here is where my REAL ISSUE begins. I decided just to wipe everything and start anew. I factory reset/ wiped properly [cache partition and davliche cache] and then locked my bootloader again. Then tried rebooting. Got stuck on Google screen. Then I unlocked my bootloader again. Tried again, same issue.
So, here is where I am at. Cannot get into recovery from fastboot, takes me back to fastboot. AND, everything is wiped because I locked/unlocked my bootloader. All I can do is adb commands.
I don't know what to do from here and there is a lot of things going on. If you could help that would be great!? What I am going to try next is to flash some recovery on, but I don't know which one/ try to mount a file to my sd card from adb commands.
Daboxk said:
Hey, So I have been scouring the forums trying to find some answers about this and you seem to be the closet to my situation. Here is what I did:
So I was running a CM9 Aplha, reverted back to stock 2.3.6 [1ada25375426.signed-soju-ota-189904.1ada2537]) so that I could then apply ICS update [VQ8PQk_V]) which I sucessfully did. This was about a month ago and it was all going well.
Then yesterday I wanted to upgrade to 4.0.4 [hR7QFEtn] so I did and superuser wasn't working properly but then I reinstalled it and got it to work. However I got to the point where everything was working fine EXCEPT for the Google Play store kept on force closing. I spent hours trying last night and could not find a solution.
I tried restoring the previous ICS update that I had and it worked, and then I tried updating again. Also side: My clockwork was on the fritz lately so I was using Zedowmaxs force into clockwork recovery image [fastboot boot recovery3101.img] to force it in sometimes.
Anyway bottom line here is where my REAL ISSUE begins. I decided just to wipe everything and start anew. I factory reset/ wiped properly [cache partition and davliche cache] and then locked my bootloader again. Then tried rebooting. Got stuck on Google screen. Then I unlocked my bootloader again. Tried again, same issue.
So, here is where I am at. Cannot get into recovery from fastboot, takes me back to fastboot. AND, everything is wiped because I locked/unlocked my bootloader. All I can do is adb commands.
I don't know what to do from here and there is a lot of things going on. If you could help that would be great!? What I am going to try next is to flash some recovery on, but I don't know which one/ try to mount a file to my sd card from adb commands.
Click to expand...
Click to collapse
It looks like the time when you were locking-unlocking the bootloader, you messed up the recovery. Since your phone can get into bootloader menu, I think you can get out of this issue.
Here is what I would do.
1. Unlock the bootloader.
2. flash clockworkmod recovery using fastboot USB.
3. Download recovery-RA-passion-v2.2.1.img, put it in C:\fastboot\
4. Shut down your phone. Then start your Nexus One in Fastboot mode by holding down the Trackball and press the Power button.
5. Connect your phone to your computer. Open a Command Prompt (Start -> All Programs -> Accessories -> Command Prompt), and run the following commands:
cd C:\fastboot
fastboot devices
fastboot flash recovery recovery-RA-passion-v2.2.1.img
now see if you can get into recovery. If you can, just flash a custom rom using install zip from sd card option in the recovery
I didn't read all the replies but fastboot reads from your PC's disk not the sdcard, unless you are running it through shell or something?

[Guide] Unlocking HTC Desire HD using HTCDEV method and installing CyanogenMod

I'm pretty new here but as I documented the process of modding my own phone I thought I'd share it with you. I didn't invent any of these processes and this information is available from many different sources. I've tried to credit any source material that I've used verbatim. I am by no means an expert.
Please reply back with any corrections and I'll be happy to edit the post.
This guide describes how to take a HTC Desire HD (mine was fully patched with OTA updates including Sense 3.0), unlock it and install CyanogenMod onto it. It worked for me but it might not for you. I don't take any responsibility for you turning your phone into a brick!
Pro Tips
Remember, in any steps requiring the phone to be powered off, just give it a minute to make sure that it is properly turned off.
Understand what's happening! If you get what's going on, you've more chance of fixing it if it goes wrong. This process describes how to use HTCs official method to unlock the bootloader. This allows you to change the operating system on the phone. The phone contains a recovery system which we an engineer can boot into to replace the main operating system if it becomes unbootable. We are going to replace this stock recovery system with a modified one which allows us do fiddle about with the phone's internal partitions. Once we have the modified recovery system in place we use it backup the existing phone operating system and replace it with a modified one. We can also use it to restore the original one again if things go wrong.
Read all of the instructions properly first! Don't go off half-****ed!
As far as I'm aware you can't reverse the official HTC bootloader unlock (i.e put your phone back *exactly* as it was) and it may effect your warranty. You have been warned!
Unlock the Bootloader
INFO: You can use the HTCDEV unlock bootloader method from HTC as an 'official' means of unlocking the bootloader. Confused? Check out the official site: http://htcdev.com/bootloader/ I'm not going to describe it step by step here because HTC do that quite well enough themselves.
Quick tip. If when going from one step to another on the HTC website you come to a white screen, that may be because you've been logged out. Just go back to the first page, log in again, then go back to the last step you completed.
Another quick tip. Make sure you properly install everything HTC tells you to. We'll need it all later...
Installing recovery mode
INFO: The stock recovery mode itself is pretty basic and can't do much, so we need to replace it with a custom recovery image.
We're going to use the clockworkmod recovery image which you grab from here: http://dl.dropbox.com/u/4518713/archive/recovery-clockwork-5.0.2.7.111102-j_r0dd_mod-ace.zip (originally seen here: http://forum.xda-developers.com/showthread.php?t=1118865)
Make sure that the fast boot mode on your phone is disabled. You can find this in your power settings menu.
If the phone is connected via a USB cable then unplug it.
Power off the phone using the power button and leave it alone for a minute.
INFO: To flash the new recovery image to the phone, you need to reboot the phone into the bootloader so that you can select a new image to boot. The bootloader is known as HBOOT.
Boot into HBOOT by holding down the 'volume down' button and pressing the power button.
By default FASTBOOT is selected so just press the power button to access it.
Attach the USB cable and note that FASTBOOT changes to FASTBOOT USB
On your PC open cmd prompt and cd to the platform-tools directory of the android sdk. Mine is at C:\Program Files (x86)\Android\android-sdk\platform-tools>
Copy the .img file from the clockworkmod zip file we downloaded earlier to the platform-tools directory. Rename it recovery.img
Go to your command prompt and issue this command:
Code:
fastboot flash recovery recovery.img
INFO: The recovery image will then be written to your phone, and as long as everything went well you'll get a message saying OK.
Ensure that BOOTLOADER is selected in the HBOOT menu and press POWER button to select it. Now you're back at the HBOOT menu.
Use the volume buttons to highlight RECOVERY and press the power button to select it. After showing you the HTC logo, the phone should boot into recovery mode!
Backing up your phone
Using the volume buttons to select move to the 'backup and restore' option in the menu. Use power to select and use the backup option. This backs up your current phone setup to the SD card.
Select power off to turn off you phone. Leave it a few secs - select reboot system now.
When your phone is backup and running, mount it in mass storage mode and navigate to the root of your SD card. See the folder called 'clockworkmod'? copy that along with everything in it to your computer and put it somewhere safe. That's your backup. If needs be, you can use this backup your phone back to the original state!
Installing CyanogenMod (other mods may vary)
Mostly taken from http://wiki.cyanogenmod.com/wiki/Nexus_One:_Full_Update_Guide with some extra stuff that messed with me when I tried to do it.
Download the latest version of CyanogenMod from http://download.cyanogenmod.com/?type=stable&device=ace
Download the Google Apps for the device. http://wiki.cyanogenmod.com/wiki/Latest_Version/Google_Apps
Place the CyanogenMod update.zip file on the root of the SD card.
Place the Google Apps .zip on the root of the SD card also.
Boot into the ClockworkMod Recovery.
Once the device boots into the ClockworkMod Recovery, use the side volume buttons to move around, and the power button to select.
Select the option to Wipe data/factory reset.
Then select the option to Wipe cache partition.
And the option to wipe the Dalvik cache
Select Install zip from sdcard.
Select Choose zip from sdcard.
Select the CyanogenMod update.zip.
Select Install zip from sdcard
Select Choose zip from sdcard
Select the Google apps zip
These extra steps seem to have been required by people in this thread. All credit due to marsdta and theluckster for their suggestions. I've edited this guide to include the instructions here where they are more visible.
On your computer extract the ROM zip (e.g. update-cm-7.1.0-DesireHD-signed.zip) and there should be a file inside it called boot.img. This should be flashed automatically, however for some reason via the HTCDEV method it is not.
To do it manually, you need to enter fastboot mode, as per the instructions above:
Boot into HBOOT by holding down the 'volume down' button and pressing the power button.
By default FASTBOOT is selected so just press the power button to access it.
Attach the USB cable and note that FASTBOOT changes to FASTBOOT USB
Then on your PC, in the directory you extracted the zip file run:
fastboot flash boot boot.img
Click to expand...
Click to collapse
Once the installation has finished, select Go Back to get back to the main menu, and select the Reboot system now option. The phone should now boot into CyanogenMod.
Now wait for what seems like an incredibly long time with the phone showing the 'htc' screen.
INFO: The phone should now boot into CyanogenMod!
Restoring your phone - When things go wrong
OK, so you flashed a bad mod. Time to restore.
First up, put the backup you made in the previous step onto the root of your SDcard (if it isn't already there). Then, I came across this video which seems to explain things pretty well
http://www.youtube.com/watch?v=mUYGe8mmNWU
The basic gist of it is, boot into recovery mode, format the cache, data and system partitions, wipe the Dalvik cache, then restore the backup from your SD card.
Wow thanks a lot!
I personally have 1 problem:
Step 12 of the "installing recovery mode" when i type in the command in command prompt is says:
'error: cannot load recovery.img'
I placed it in the same folder as fastboot en renamed it "recovery.img".
I unlocked the bootloader succesfully btw..
Any thoughts?
I think you should contemplate using attn1's ace hack kit to gain bootloader unlock instead of voiding your warranty.
Hunt3r.j2 said:
I think you should contemplate using attn1's ace hack kit to gain bootloader unlock instead of voiding your warranty.
Click to expand...
Click to collapse
Well I've already unlocked the bootloader through htcdev.
But tried the Attn1's as well...ended up saying:
/data/local/tmp/goldcard.img: cannot open for read: No such file or directory
starting downgrade...
** The phone will now reboot into HBOOT.
** It will then check the file just sent.
** If everything is okay, the phone will
** prompt you to continue by pressing
** VOLUME UP. It will reboot, flashing twice.
The phone did not prompt me to continue by pressing volume up.
When i start clockwork recovery it states i should root my phone...
So a lot going wrong and i can't figure out what..
how long the htc screen? I'm waiting for a looooong time
Thanks for the tutorial. I've followed the instructions and managed to unlock the bootloader and install ClockworkMod, however after flashing CM7 and rebooting it is stuck on the H3G boot screen (isn't flashing CM7 supposed to overwrite the boot logo?). I'm trying to flash:
update-cm-7.1.0-DesireHD-signed.zip
gapps-gb-20110828-signed.zip
I've double checked /data, /system, /cache and Dalvik-Cache have been wiped before flashing but still no avail
Here are the versions from the bootloader:
***UNLOCKED***
ACE PVT SHIP S-ON RL
HBOOT-2.00.0029
MICROP-0438
RADIO-26.14.04.28_M
eMMC-boot
Dec 22 2011, 14:28:19
I am able to restore the backup, but flashing any other ROM just doesn't boot.
The guide is missing one key step . Flashing the boot image.
So after flashing your from boot back into boot loader and flash your roms boot.img.(just copy it over to your fast boot file)
Then run the command
Fastboot flash boot boot.img
Reboot . Done.
You'll have to do this every time you flash different roms. 4ext has a nice feature of doing this for those that have HTC unlocked you should try it out
Sent from my Inspire 4G using XDA
Awesome, thanks marsdta! It is working now, good work!
thelucster said:
Awesome, thanks marsdta! It is working now, good work!
Click to expand...
Click to collapse
can you repeat it more clear for me because i have the same problem.
Thank you Thelucster. You have saved me from a big mistake.
crom1 said:
can you repeat it more clear for me because i have the same problem
Click to expand...
Click to collapse
First flash the Cyanogen ROM and Google Apps, as per the instructions above. Then on your computer extract the ROM zip (e.g. update-cm-7.1.0-DesireHD-signed.zip) and there should be a file inside it called boot.img. This should be flashed automatically, however for some reason via the HTCDEV method it is not.
To do it manually, you need to enter fastboot mode, as per the instructions above:
Boot into HBOOT by holding down the 'volume down' button and pressing the power button.
By default FASTBOOT is selected so just press the power button to access it.
Attach the USB cable and note that FASTBOOT changes to FASTBOOT USB
Click to expand...
Click to collapse
Then on your PC, in the directory you extracted the zip file run:
fastboot flash boot boot.img
Click to expand...
Click to collapse
I didn't set notifications on this post and forgot it existed till today. I've updated the guide with the information posted by marsdta and theluckster to make things clearer. Sorry about any confusion caused by missing that step out.
the boot screen shows cyanogen(mod)7 instead of the regular HTC sign!! Following each and every step I landed up here. And now I am stuck, cuz this boot screen has been there for like half-an hour....does it mean something is wrong or does it take this much time to load first???
Hello,
for HTC dev unlocked bootloader (about what is added after step 15 in "installing cyanogen" phase) : it seems that the boot.img must be flashed before installing the .zip from sdcard.
I got stuck for that. Could be worth to make it clear.
Great tutorial anyway, thank you !
zarkenciel said:
Hello,
for HTC dev unlocked bootloader (about what is added after step 15 in "installing cyanogen" phase) : it seems that the boot.img must be flashed before installing the .zip from sdcard.
I got stuck for that. Could be worth to make it clear.
Great tutorial anyway, thank you !
Click to expand...
Click to collapse
It shouldn't matter. I've seen people do it both ways and it worked fine for them.
@ash win. Your in a boot loop. Did you do a full wipe before flashing? Could be just a bad flash. Go back and reflash the rom and boot.img. you should also verify the md5hash to make sure yous didn't get a corrupt download file.
Just finished the tutorial, works perfectly. Thanks for writing it.
Does this unlock you from the network, i.e. is this the alternative to paying £15 for an unlock code?
I do understand this is for modding and flashing to a new ROM, but I am wondering if it also unlocks the phone from your network (or maybe that is IMEI based).
This is not for any illegal purposes, just I fancy a new ROM and I am now out of contract, so happy to experiment with flashing.
ohforfs said:
Does this unlock you from the network, i.e. is this the alternative to paying £15 for an unlock code?
I do understand this is for modding and flashing to a new ROM, but I am wondering if it also unlocks the phone from your network (or maybe that is IMEI based).
This is not for any illegal purposes, just I fancy a new ROM and I am now out of contract, so happy to experiment with flashing.
Click to expand...
Click to collapse
No, you need the aahk for that. That gives you sim unlock as well. Just Google attn1 aahk and you'll find it
marsdta said:
No, you need the aahk for that. That gives you sim unlock as well. Just Google attn1 aahk and you'll find it
Click to expand...
Click to collapse
Thanks - very kind of you to point me in the right direction, I've found it
Hi,
and how do i root my phone after HTCDev Unlock??
I want install the Custom Rom "Sabsa Prime". Do i need root to flash it?
Sorry for my bad english.
You may also want to include wiping battery stats in the advanced option of cwm in your guide

[Q] Stuck in boot loop - Save Photos?

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.

[Q] N4 stuck in boot loop after OTA update

Hello,
I saw that the OTA update to Lollipop was available on my phone today, so I went ahead and let it download. Upon completion of the download, it restarted and applied patches, then restarted again and has been stuck in boot loop for about an hour. After reading several other threads on how to try to reset the phone, I'm stuck. When I try power + volume up or down, the LED status indicator flashes red and I never get to any kind of other screen. Am I completely screwed? I previously had stock 4.4.2 with no modifications.
Finally was able to get to the bootloader menu. Apparently having the phone plugged into the charger was preventing me from getting there for some reason. I ended up having to wipe the phone to get it to boot
so you can get into clock recovery right? download nexus 4 toolkit..that might save your phone. I suggest you to unroot and flash everything to stock and then unlock again and start everything from scratch. good luck.
Similar issue on an OTA upgrade to an unrooted N4. It's stuck on the Lollipol boot screen with the rotating Circle thingies.
I can get to the Android System Recovery but there's no CWM or TWRP on my N4. I'm guessing a factory reset will fix it but is there a way to preserve my pics/files on the phone before doing so?
Sportfreunde said:
Similar issue on an OTA upgrade to an unrooted N4. It's stuck on the Lollipol boot screen with the rotating Circle thingies.
I can get to the Android System Recovery but there's no CWM or TWRP on my N4. I'm guessing a factory reset will fix it but is there a way to preserve my pics/files on the phone before doing so?
Click to expand...
Click to collapse
I guess TWRP Recovery has option to enable MTP and you can access the internal SD card by connecting mobile with computer using usb cable.
---------- Post added at 06:37 PM ---------- Previous post was at 05:37 PM ----------
Sportfreunde said:
Similar issue on an OTA upgrade to an unrooted N4. It's stuck on the Lollipol boot screen with the rotating Circle thingies.
I can get to the Android System Recovery but there's no CWM or TWRP on my N4. I'm guessing a factory reset will fix it but is there a way to preserve my pics/files on the phone before doing so?
Click to expand...
Click to collapse
Flash TWRP Recovery using fastboot.
1. If you have otg y cable, connect it and use file manager to copy all the files.
2. OTG method is failed then select “Mount”, then select only “Data” and connect your Nexus 4 to your computer and Enable MTP in TWRP. now you can use adb pull and push commands.
I ended up going the factory reset route, which wasn't really a bad thing. My photos had been backed up in dropbox and the play store remembered all the apps and were able to reload them. The only things I really had to do was reload some music onto the phone and re-enter passwords for apps.
Same story here: sideloaded the OTA zip file, then had bootloop. Tried a few approaches, but none worked. In the end only wiping the data was the solution for me. Lost some userdata in a few important Apps...
I went through this yesterday. The only way to get it to boot is a Factory Reset from Recovery. It works like magic, but sucks you lose the data.
Got the OTA yesterday and also got a bootloop(stuck in boot screen animation). I couldnt afford losing my photos/videos as i had no backup , so i figured out a super easy to get it to boot without wiping data .
I was unrooted with stock recovery running stock 4.4.2, bootloader was unlocked. I flashed CWM recovery through fastboot and wiped chache+ Dalvik from there then simply rebooted the phone .
I had already tried wiping cache from the stock Android recovery,needless to say that didnt work for me.
If anyone else is having the same problem please try the method above and report back, cheers!
I post this on Google Product Forum 2 days ago. Hope it helps
https://productforums.google.com/for...Q/wDzRUm4b2UsJ
(updated 29/11/2014)[not perfect but it is a SOLUTION]
The idea of this is to downgrade your nexus 4 without wiping your data, which means stuff you will need includes:
1. adb and fastboot on your computer (I am using mac but you can find it on windows as well. There are tones of website and forums telling you the latest method of getting it onto your computer)
2. factory image of nexus 4(I use 4.4.4, since that's what it was. I don't have the time and energy to try to do the same thing with lollipop. you can try can leave a comment).
update: do NOT try to flash 5.0 rom using this method. You will be stuck at boot loop again
3. usb cable
4. nexus 4 with unlocked bootloader(the process of unlocking bootloader will wipe your device)
5. computer
steps
1. unzip the factory image (something.tgz)
2. for me, after unzipping the .tgz, I still find another .zip inside. unzip that too.
3. hold vol+, vol-, and power button simultaneously to enter fastboot mode
4. open terminal(mac)(it would probably be cmd for windows)
5. connect your nexus 4(in fastboot)
6. to make sure it connect successfully, type "fastboot devices". if something like "005040c0d54bb291 fastboot" appears, you are good. Otherwise, try reconnect your device/boot to fastboot again/use another usb cable
7.now we need to tell the terminal to navigate to the location of the unzipped factory image. to do that, i suggest you put the unzipped folder to somewhere easy to find, like desktop. these are some commands to help you navigate:
"ls" allows you to look at whats inside the current directory of the terminal. For example, this is the output after typing "ls" for me:
some folder Photos
nexus4image.tgz how many folders do you have
5.zip occam-ktu84p
more folder occam-ktu84p.zip
after knowing where you are, use "cd" (below) to go to your folder
"cd" means change directory. For example. "cd Photos" will brings me to the "Photos" folder. And then if I type ls, I will see a whole bunch of photos in my photos. If you go to the wrong folder, type "cd ..", and it will bring you back to the previous folder.
8. flash bootloader.
enter the following command, BUT REMEMBER TO CHANGE THE NAME TO FIT YOURS(DIFFERENT VERSIONS HAVE SLIGHTLY DIFFERENT FILE NAME AT THE END(type ls first to help you type the correct name)
fastboot flash bootloader bootloader-mako-makoz30d.img
9. reboot bootloader. just copy and paste
fastboot reboot-bootloader
10. flash radio
enter the following command, BUT REMEMBER TO CHANGE THE NAME TO FIT YOURS(DIFFERENT VERSIONS HAVE SLIGHTLY DIFFERENT FILE NAME AT THE END(type ls first to help you type the correct name)
fastboot flash radio radio-mako-m9615a-cefwmazm-2.0.1701.03.img
11. reboot bootloader. just copy and paste
fastboot reboot-bootloader
12. flash system
system.img is located inside the zip, use ls to help you navigate. This steps takes the longest time, total time on this step is 87 seconds while the others are less then 1 second
fastboot flash system system.img
13. flash boot
boot.img is located inside the zip, use ls to help you navigate.
fastboot flash boot boot.img
14. flash recovery
fastboot.img is located inside the zip, use ls to help you navigate.
fastboot flash recovery recovery.img
15. format cache(not the memory, so everything should be fine)
fastboot format cache
16. reboot and wait
this will reboot your device. You probably have to wait for a while to initialise all the apps. after than you are good to go!
fastboot reboot
credit: my friend for giving me this idea + http://forum.xda-developers.com/nexu...image-t2010312 + HelpMyNexus

[HELP] Bricked Umi Zero

Hello. Sorry for my english. I want flash my phone via rootjoy to Arcatarc's MIUmIZERO and i only can see miui logo. next i want back to stock rom from needrom via sp flash tool, i followed instructions and i stop, when red status back not change for 20 minutes. and i can't charge my phone, can't conected to pc, can't turn on, looks like dead. How unbrick my phone? please help
problem solved
how did you solve it? please let me know as i am in the same boat
If it's stuck on the MIUI screen then it's possible the bootloader wasn't flashed properly.
If you can reboot the phone in fastboot you can flash the bootloader via PC.
it is dead . the phone wont turn on . the pc wont recognise it anymore , it was fine ... untill i tried to flash stock through sp flash tool .
i was running antarcts emui,.... tried flashing using the method on umi digi forum : http://umidigi.com/forums/topic/how-to-restore-rom-version-3-03-2/ ... preloader was unticked, and when i tried firmware uopgrade option...nothing happened, and the phone was dead after that.
thepopos said:
If it's stuck on the MIUI screen then it's possible the bootloader wasn't flashed properly.
If you can reboot the phone in fastboot you can flash the bootloader via PC.
Click to expand...
Click to collapse
I managed to make it boot.
The problem is I have twrp and some chinese recovery . And I cant go back to stock.
Fastboot cant flash recovery for some reason ... so I can go back to rootjoy.
use adb side load an try to flash a working rom, the original one from umi website or emui.
can you get in recovery mode? volume (+ or - try both) and power button for some seconds
if yes go adb side load, (check google) and transfer an original rom, then flash it again in the recovery
My Umi Zero is bricked, because I cannot mount /system. I can get into the TWRP, but I cannot do anything, even restore my backup because of this. Does anyone have idea what to do?
Pospa420 said:
My Umi Zero is bricked, because I cannot mount /system. I can get into the TWRP, but I cannot do anything, even restore my backup because of this. Does anyone have idea what to do?
Click to expand...
Click to collapse
If the system is unstable with popups etc or with damaged partitions you can get past that with TWRP.
Boot into recovery Wipe/Advanced Wipe. Then after that is completed, without rebooting, Format Data. That should sort out your partitions.
Then Install ROM from the recovery. It will need to be on the device. If your new ROM is not already there plug in a USB lead and transfer the zip file from your pc.
If you want to re-install your backup, do that instead.
If that doesn't work Backup in TWRP, even though there is no system. Then copy your Nandroid backup (must have been made via TWRP) and paste into the same folder as the Backup you just made, overwriting if asked.
I have had to do all this myself!
Good luck
Hi all!
I have the simular problem.
Umi Zero can not start.
But recovery seems to be working.
1) TWRP recovery 2.8.2
After full wipe, my TWRP recovery write "Unable to mount /SYSTEM"
The same message I have if I try to flash original 3.10 ROM via TWRP.
It is impossible to mount or format or repair SYSTEM via recovery
But it is possible to see files in FileManager and go to Fastboot and ADB mode
2) ADB and Fastboot mode.
Impossible to flash any partition.
"boot" - checksum error
"recovery" - "not support flash" message
"system" - filesystem created, start "erasing" and freeze. If I disconnect phone, have got message "failed (too many links)"
adb sideload does not work also
3) SP Flash Tool
I tried with full 3.10 ROM and with CRT 3.0 recovery
Download mode and Format+Download mode.
The same result: yellow bar finished and got message "Checksum error" or something like that.
All this experiments change nothing in phone. I still have TWRP recovery and "unable to mount /SYSTEM" message.
Any advices?
I am not English-speaking guy, as you guess), sorry.
It looks like memory become write-protected...
YrP said:
Hi all!
I have the simular problem.
Umi Zero can not start.
But recovery seems to be working.
1) TWRP recovery 2.8.2
After full wipe, my TWRP recovery write "Unable to mount /SYSTEM"
The same message I have if I try to flash original 3.10 ROM via TWRP.
It is impossible to mount or format or repair SYSTEM via recovery
But it is possible to see files in FileManager and go to Fastboot and ADB mode
2) ADB and Fastboot mode.
Impossible to flash any partition.
"boot" - checksum error
"recovery" - "not support flash" message
"system" - filesystem created, start "erasing" and freeze. If I disconnect phone, have got message "failed (too many links)"
adb sideload does not work also
3) SP Flash Tool
I tried with full 3.10 ROM and with CRT 3.0 recovery
Download mode and Format+Download mode.
The same result: yellow bar finished and got message "Checksum error" or something like that.
All this experiments change nothing in phone. I still have TWRP recovery and "unable to mount /SYSTEM" message.
Any advices?
I am not English-speaking guy, as you guess), sorry.
Click to expand...
Click to collapse
Hi
Did you Advance Wipe and Format Data?
I found that worked.
Alternatively, you could use Rootjoy to put just about any ROM on. CM 12.1 works ok.
Once you have a stable installation, install a custom recovery like TWRP 2.8.7 from Needrom. I used Mobileuncle, an app from the Playstore. However, I looked just now and it doesn't seem to be available.
I have tried Rashr, but couldn't get it to work.
Once you have it all stable you can flash the ROM you really want via TWRP.
Good luck
Advance Wipe and Format Data or flashing new stable ROM via TWRP did not work for me. The same result- unable to mount /system.
Rootjoy and Mobileuncle could be used if phone is working. My phone works in recovery mode only.
I tried to flash different recoveries but did not find the way to do this. As I wrote, Sp Flash Tool, Fastboot and Adb Sideload did not make any changes to my recovery. I think, flash new recovery will help if I found the way)
Or if I discover the method to test and\or repair /system partition from PC
But thank you for answer)
@YrP
Rootjoy works from your pc
Yes, Rootjoy- works)
But for establish connection phone must work too.
And not in recovery mode.
@YrP
I have already done all this with my daughter's Zero.
However, it's in bits at the moment while we wait for a part from China. So I can't go through the process with you live, step by step.
I am in the UK.
If you send the phone to me I will try and fix it for you.
PM me if you want to go ahead and I will let you have my address.
I am in Ukraine, it is too far from UK)
I will keep trying to find the way to fix it by myself.
But thank you very much for your attention and advices.
@YrP
I have got my daughter's phone back together and fixed (mostly).
Did you manage to get your Zero going?
Sent from my Nexus 4 using XDA-Developers mobile app
@goldbear
My UMI is still bricked(
It is flash memory problem, I think.
I am trying to find the tool to remap internal memory, to move SYSTEM part to other physical place. But did not find it yet.
What was your way?
Zero stutters, processes crash or the phone will not boot into System
Have you already tried a Factory Reset or re-installed the ROM?
What can you do?
You could try the following. However, if your phone blows up, orders a takeaway or elopes with your girl-friend, please don’t blame me.
1. Provided you already have TWRP custom recovery installed and your phone is powered down boot into Recovery: hold the volume down and power buttons until the Zero logo appears then let go
2. Select Wipe/Advanced and select Dalvik Cache, System, Cache and Data. Slide to execute
3. Select Format Data/ type yes and slide to execute
4. Reboot into Recovery without installing a new ROM
5. Select Backup, choose SD card rather than internal storage and give the file a memorable title like Blank Backup and date. Select Boot, Logo, Recovery and Uboot. Slide to execute
6. The next step requires you to have a Nandroid backup made via TWRP already made of a stable ROM. If it isn’t stable or you don’t have one I have attached a clean backup below. It’s derived from Cyanogen Mod 12.1. This is based on Lollipop 5.1, with Gapps and rooted. I have found this to work. As the title of the file suggests, it’s a factory reset, ie no personal data included. Download it to your pc unzip and save it.
7. Connect your phone to your pc via USB cable and open Windows Explorer
8. Find your stable backup or the one below and drill down until you see the folder with 15 files, starting with data.info and ending with uboot.emmc.win. Select all and Copy.
9. Open another window and find the TWRP folder on the SC card of your phone. Drill down to the same folder containing similar files as to step 8 above. Click in folder and Paste. When prompted select Copy and Replace, all and Ok
10. If your pc doesn’t show your phone and the SD card, in recovery select Mount and USB storage.
11. In Recovery select Restore and the Blank Backup (or whatever file name you gave it, now populated with usable ‘data’). Slide to execute
12. Give it time to load and boot up
13. You should be good to go!
If you don’t like CM 12.1 installing a new Launcher from the Playstore, like Cheetah will make it run smoother. Everything after that is down to you.
Of course, you could flash another ROM via TWRP
The backup below was made via TWRP 2.8.6. This is also attached below. You can install this via a previous version of TWRP as an image. Unzip it first.
Assuming this doesn’t wreck your phone and you like the guide please click Thanks below.
https://drive.google.com/file/d/0ByoLjFrSKxLwc01UUWZBZEQtbWs/view?usp=sharing
https://drive.google.com/file/d/0ByoLjFrSKxLweGhqNGJuVGV1a0U/view?usp=sharing

Categories

Resources