Related
I have been reading around for a while now, and noticed a lot of ppl soft-brick there device and are asking devs for help. I have noticed a lot of issues revolve around people trying to hop form on ROM to another.
A very easy way to recover from any sort of brick(or issue) is to use nvFlash. Its is very easy to setup and use and I highly recommend that everyone should setup nvFlash. You can find the guide on how to set it up from http://forum.xda-developers.com/showthread.php?t=861950
I think after the update last night a lot of people will brick there devices trying to mod it, and nvFlash will help you recover. I think we can really help out the dev if we all learn how to use nvFlash, because then they wont have to ans to alot of the support issues that keep coming up, and it will free up some of there time which they can use to create newer roms that will work with the new update.
If for some reason you follow that guide and are not scussefull in setting up nvFlash, then feel free to leave me a pm and i'll help you set it up.
I setup NVFLash a couple of days ago on my Windows laptop.
Am I correct in stating it replaces my need for CWM?
If so is there a site or link on how to use NVFLASH to complete the different task?
Example
Installing a Rom, Kernal, backup, data, etc
steve1040 said:
I setup NVFLash a couple of days ago on my Windows laptop.
Am I correct in stating it replaces my need for CWM?
If so is there a site or link on how to use NVFLASH to complete the different task?
Example
Installing a Rom, Kernal, backup, data, etc
Click to expand...
Click to collapse
No its not a replacement for cwm. NVFlash will help you recover if you every brick your device and need to go back to stock image.
Couple of scenarios where it will be helpful is if you update to the new stock update from VS and decided you want to go back to one of the custom roms like Vegan GB RC1, then you will need nvFlash to go back to stock, otherwise you will brick your device.
Also I have noticed that I have to use nvFlash if I want to go from GB rom to FORYO rom.
Cannot get NV Flash to finish?!?
Very new to this but with the forums help I put TNT 4.2.4 on my Gtab and loved it. I had a hard crash last week and figured I need to use NV Flash to go back to stock or another rom. I put tablet into correct mode and by using USB drivers I am able to load NV Flash, it finished and on tablet the screen says "Entering NVFlash recovery mode / Nv3p Server" and that is it! It never reboots and if I manually reboot I have the same problem - all I get is the birds forever...if I try to boot using vol+ it says "Recovery Key Detected" "Booting recovery kernel image" and it sits forever...need help desperatley!
Thanks for listening
Mike
nvflash unsuccessful or wrong version
sk01bim said:
Very new to this but with the forums help I put TNT 4.2.4 on my Gtab and loved it. I had a hard crash last week and figured I need to use NV Flash to go back to stock or another rom. I put tablet into correct mode and by using USB drivers I am able to load NV Flash, it finished and on tablet the screen says "Entering NVFlash recovery mode / Nv3p Server" and that is it! It never reboots and if I manually reboot I have the same problem - all I get is the birds forever...if I try to boot using vol+ it says "Recovery Key Detected" "Booting recovery kernel image" and it sits forever...need help desperatley!
Thanks for listening
Mike
Click to expand...
Click to collapse
Sounds like the nvflash wasn't successful. The message you are getting when you boot to recovery...Power + vol(+) indicates that CWM is installed. If you nvflashed a stock version, cwm would not be there (unless you nvflashed a stock version with cwm preinstalled). Are you sure you flashed with the correct bootloader version. You should have used the 1.1 b/l version. Here is a link to b/l 1.1 version 3588 with cwm preinstalled http://www.mediafire.com/file/picrzt9pdkuqbj0/gtab.nvflash.1.1.branch.20110422%20with%20cwmv8.zip. Nvflash this & see what happens. By the way. when doing the nvflash, the cmd shell output should look something similar to the attached file...won't be exact since this was for a bl1.2 4349 version I nvflashed yesterday.
Al
sk01bim said:
Very new to this but with the forums help I put TNT 4.2.4 on my Gtab and loved it. I had a hard crash last week and figured I need to use NV Flash to go back to stock or another rom. I put tablet into correct mode and by using USB drivers I am able to load NV Flash, it finished and on tablet the screen says "Entering NVFlash recovery mode / Nv3p Server" and that is it! It never reboots and if I manually reboot I have the same problem - all I get is the birds forever...if I try to boot using vol+ it says "Recovery Key Detected" "Booting recovery kernel image" and it sits forever...need help desperatley!
Thanks for listening
Mike
Click to expand...
Click to collapse
My website linked in signature. You're a code red.
Hello, thanks for the response! I am downloading now and will let you know shortly...
Mike
goodintentions said:
My website linked in signature. You're a code red.
Click to expand...
Click to collapse
What is a code red?
Code Red is the condition of your G Tab. If you follow the link in the signature of Goodintentions post (Viewsonic G-Tablet for Dummies) you will find complete and simple instructions on how to recover your G Tablet. You can also find links to the files you will need. It's a great site for anyone having problems with their tablets. It's where I got all my information when I first started.
Hello, i recently bought a xoom (wifi only) and now im in a quite frustrating situation.
When i got it first i flashed CWM recovery and rooted it successfully, it worked all fine for a few days.
yesterday i left the xoom on charger over night and today morning it was stuck on the red M logo saying "Dual Core Technology".
well, my situation is like:
- i can restart the xoom using power + volume up, but every time it stucks on the M logo again
- i can boot into RSD with volume up while starting
- i can boot into fastboot with volume down while starting
- i can NOT boot into recovery, when i try it gets stuck at "Reading ODM fuse: 1"
i reflashed the original ROM from MOTODEV, but the device still behaves the same like before..
normal boot gets stuck at the M logo, recovery gets stuck on Reading ODM fuse: 1, just fastboot working fine (unlocking & flashing works fine)
i also searched for similar problems on the forums, but any promising solution links to filesonic links wich are not working/down
any ideas what i can do now? any help is appreciated
thanks
unlock the bootloader and flash Rogue Recovery v1.3.0
then try to enter cwm
are u on stock? or customrom? and have u tried to lock the bootloader using a customrom? cauz locking the bootloader with customrom = not good
hi, thanks for your reply.
im on stock rom and my bootloader is unlocked. i did relock the bootloader once, but only after flashing the original ROM from MOTODEV to my device, now it is unlocked again.
i first flashed the CWM 3.2.0.0 wich is available as .img via fastboot, but it does not start (Stuck on "Reading ODM Fuse: 1").
now i flashed the recovery.img inside of Rogue Recovery 1.3.0 (since i read in the corresponding thread that it works also this way), but again: Stuck on "Reading ODM Fuse: 1"
Maybe u r 2 quick? Turn on your xoom - if u see the M wait 3 sec then press vol down and then vol up
But as i said wait 3 secs - if u r 2 quick it will stuck at entering recovery
okay, so you flashed a new recovery image (did you verify the images md5-sum?) and without trying to reboot into android you cannot get into recovery? That is really odd.
If so, I suspect that something has really screwed up your internal memory. You might be able to fix it using a factory cable.
Btw: after flashing the recovery image, does the xoom say that it succeeded in writing the recovery image to its memory?
There should be a command to reboot the device to recovery? A function reboot to recovery is possible on eos 1.0 maybe theres a adb or fastboot command 4 that?
llama-power said:
okay, so you flashed a new recovery image (did you verify the images md5-sum?) and without trying to reboot into android you cannot get into recovery? That is really odd.
If so, I suspect that something has really screwed up your internal memory. You might be able to fix it using a factory cable.
Btw: after flashing the recovery image, does the xoom say that it succeeded in writing the recovery image to its memory?
Click to expand...
Click to collapse
after flashing the recovery, i can read
"Flashing StorMgr partition recovery STATUS: done!" on the xoom
the recovery image is fine, and until today i was able to boot into CWM 3.2.0.0
what is the thing with the factory cable?
about the factory cable: seems to be a modified usb-cable with two terminals on the micro-usb end being connected with each other. As far as I read, it should enable you to write to the xooms memory as long as the hardware is still okay, no matter how much you f***ed up your software I haven't had to use yet, though.
@what Unholy said: sure, adb reboot recovery will boot your xoom into recovery, but only if you have a working android running and usb-debugging enabled.
Reading ODM Fuse: 1, according to my information, means that the thing is trying to boot into recovery. Why nothing else shows up: I have no clue.
here is a thread where some us-users had a similar problem. They tried to root their xoom after getting the 4g-upgrade and ended up with the red M-Logo. After some screwing around, they even managed to wreck the fastboot-mode, thus only enabling rsd access. So no help on that side.
What especially bothers me about your problem is that it just appeared on its own. Right before your xoom showed its issues, you weren't flashing anything. Just charging shouldn't cause any of this.
I am beginning to suspect a hardware failure that can naturally be only fixed by motorola. But that's only my current opinion.
If I was you, I would try downloading the files from motorola again, check their md5-sums and then flash those using fastboot using these instructions.
If that still doesn't help, there may be a way to get a .sbf file from motorola for your xoom. That is a file which can be flashed using the windows software rsd-lite, but I haven't used that in a long time and it has been reported to not work really well with the xoom.
Next, I'd research a little on the factory cable thing, but I'd be careful with that.
As a last resort, I'd send the xoom to my dealer. Unluckily, there is a way to determine if you have had your bootloader unlocked, at least as long as fastboot is still working...
About the factory cable - with that cable u can flash your xoom if nothing else is working anymore (adb or cwm)
To build a factory cable u have to tie pin 1 (+) to pin 4 on the micro usb plug
I build one but never used it and hope i will never have to
i did download the original ROM from motodev again, checked the md5, and flashed according to the tutorial posted by llama-power, but the device still wont boot neither the rom nor into recovery.
since its now on 15% battery i think i will let it run out of power and then try to boot again...
The_Revenge said:
i did download the original ROM from motodev again, checked the md5, and flashed according to the tutorial posted by llama-power, but the device still wont boot neither the rom nor into recovery.
since its now on 15% battery i think i will let it run out of power and then try to boot again...
Click to expand...
Click to collapse
does the xoom charge when connected to ac power? I know that other devices (cellphones) wouldn't charge without working os.
However, I do not think that letting the battery run low will help you. Lithium ion batteries should not be low discharged as that will most likely destroy them and lead to a massive risk of explosion upon the next charge. Because of that, devices powered by a lithium ion battery will power down before depleting the battery, the xooms mainboard itself will most likely still be supplied with some power.
If you really want to cut the power supply to the mainboard, you'll have to open the xoom (two screws) and unplug the battery (the connector is held down by another two screws) for a couple of seconds. (here is a teardown of the xoom with pictures)
by the way, if you want to track your battery status without booting android (as that would obviously not work), you can use fastboot getvar battery-status.
well my xoom actually charges when i connect it to power, and the LED also lights up, so (thinking of what you said) it seems like the os and everything still is present, just like the bootloader cant load it or something?! is there maybe any way to update the bootloader itself?
yeah, i can also check the battery status when i'm booting with power and volume up (RSD) =)
well i'm actually thinking about disconnecting the battery, but i'm a bit unsure, i will study that now..
The_Revenge said:
well my xoom actually charges when i connect it to power, and the LED also lights up, so (thinking of what you said) it seems like the os and everything still is present, just like the bootloader cant load it or something?!
Click to expand...
Click to collapse
not neccessarily. Maybe the xoom just doesn't need any software to charge the battery.
The_Revenge said:
is there maybe any way to update the bootloader itself?
Click to expand...
Click to collapse
don't know, but since fastboot works I suspect that the bootloader itself is still fine.
The_Revenge said:
well i'm actually thinking about disconnecting the battery, but i'm a bit unsure, i will study that now..
Click to expand...
Click to collapse
have fun, but I wouldn't get my hopes up too high. I still suspect some sort of a hardware failure... Also, opening the device might leave some traces (botched screws, etc) that could lead motorola to say that you messed with your xoom if you should finally decide to send it in
well thats the same i thought about opening the device..
do you know any way to dump the partitions to the pc (maybe with fastboot?)
The_Revenge said:
do you know any way to dump the partitions to the pc (maybe with fastboot?)
Click to expand...
Click to collapse
nope, not without a working recovery.
fastboot erase partition_name should be able to clear your partitions, though. Replace partition_name with boot, system, userdata, cache or recovery
http://www.xoomforums.com/forum/xoo...ery-stuck-red-m-logo-fastboot-works-help.html
apparently that user seems to have had the same problem, he says he fixed it using 1.35 Everest Bootloader (SBF).
i also had that idea some time earlier and found a thread with the SBF files here on xda, also for the wifi model, but the only links i could find to SBF files were filesonic links wich are not working ._.
i'm now up to googling for SBF files (for the wifi only model), if i cant find anything promising i'll send it back tomorrow.
btw, erasing the partitions does not help, i've already tried that
Have u done the lte update?
UnholyX said:
Have u done the lte update?
Click to expand...
Click to collapse
he's got an wifi-only model (as stated in post #1) and is from germany (at least that's what his location and flag says). LTE upgrade is neither available in germany, nor for wifi-only-xooms. So I'd say no
@OP: that sounds quite promising. .sbf-files still seem to be available on some sites, downloading one for my xoom right now, just in case that site goes down in the future...
Yes he got the wifi version like me but something must happened ,-)
I also charge my xoom and nothing happens. He got wifi version but he maybe flashed a false update or so
There r people flashing stingray instead of the wingray version etc. - just asking what happened before - thats the reason - something must happened before ;-)
it seemed promising, but i cannot find any usable sbf file
i think i'll send the unit back tomorrow
So I think I might have a bricked xoom. Its the 3G/WIFI version. I tried to downgrade it to WIFI only version and got stuck from there.
Now the Xoom is stuck at the red M when booted.
If you go through recovery it says: "Reading ODM fuse:1."
If you go through fastboot it says: "Starting fastboot protocol support."
RSD: battery level
The Xoom freezes after each option is selected and that's about as much action as I can get from it. So am I screwed? If not, what can I do?
Is it recognised via ADB?
Send to service center and they should have special tool to recover it!
re-flashing Rogue Recovery
mikeay93 said:
So I think I might have a bricked xoom. Its the 3G/WIFI version. I tried to downgrade it to WIFI only version and got stuck from there.
Now the Xoom is stuck at the red M when booted.
If you go through recovery it says: "Reading ODM fuse:1."
If you go through fastboot it says: "Starting fastboot protocol support."
RSD: battery level
The Xoom freezes after each option is selected and that's about as much action as I can get from it. So am I screwed? If not, what can I do?
Click to expand...
Click to collapse
If you are getting "Starting fastboot protocol support" then you should be able to then plug in the USB cable and use ADB. I would then try re-flashing Rogue Recovery, then with a working recovery kernel you can flash the correct ROM.
Grege50 said:
If you are getting "Starting fastboot protocol support" then you should be able to then plug in the USB cable and use ADB. I would then try re-flashing Rogue Recovery, then with a working recovery kernel you can flash the correct ROM.
Click to expand...
Click to collapse
Thanks for the help guys,
So I tried re-flashing the Rogue Recovery, and other kernels, but the Xoom says,
"Device still locked. Device must be unlocked first.
Failed to process command error (0x8)"
I'll be some research too and let you guys know what happens
mikeay93 said:
So I think I might have a bricked xoom. Its the 3G/WIFI version. I tried to downgrade it to WIFI only version and got stuck from there.
Now the Xoom is stuck at the red M when booted.
If you go through recovery it says: "Reading ODM fuse:1."
If you go through fastboot it says: "Starting fastboot protocol support."
RSD: battery level
The Xoom freezes after each option is selected and that's about as much action as I can get from it. So am I screwed? If not, what can I do?
Click to expand...
Click to collapse
could you be more specific with your device details before the flash, during the flash, after the flash?
Before the flash; model mz???, ICS/JB, Rooted, custom rom, unlocked bootloader, custom recovery.....etc.
During the flash: you said that you downgraded to the WiFi version......which version? Did you fast boot the image files? Did you use RSD lite and sbf image? Which image and rsd lite image?
After; in detail explain what you did after the flash up til now.
I know that this is a lot but it will help.
From first guess it sounds like your bootloader is locked or you downgraded your boot loader to an earlier version prior to the latest ver#1050 when you downgraded your device to a WiFi version. This would also keep your device in the condition you describe or worse. I would try to unlock your boot loader.....if that fails then you need to find the latest 3G image version sbf (if there is one) using rsd lite. If that is not an option then try to flash with RSD lite the 604 combo sbf for the mz604. I had to flash it a couple times plus do a manual factory restore......good luck.
Galaxy Nexus (SCH-I515 VZW/LTE) using Tapa2
cdexsw said:
could you be more specific with your device details before the flash, during the flash, after the flash?
Before the flash; model mz???, ICS/JB, Rooted, custom rom, unlocked bootloader, custom recovery.....etc.
During the flash: you said that you downgraded to the WiFi version......which version? Did you fast boot the image files? Did you use RSD lite and sbf image? Which image and rsd lite image?
After; in detail explain what you did after the flash up til now.
I know that this is a lot but it will help.
From first guess it sounds like your bootloader is locked or you downgraded your boot loader to an earlier version prior to the latest ver#1050 when you downgraded your device to a WiFi version. This would also keep your device in the condition you describe or worse. I would try to unlock your boot loader.....if that fails then you need to find the latest 3G image version sbf (if there is one) using rsd lite. If that is not an option then try to flash with RSD lite the 604 combo sbf for the mz604. I had to flash it a couple times plus do a manual factory restore......good luck.
Galaxy Nexus (SCH-I515 VZW/LTE) using Tapa2
Click to expand...
Click to collapse
Ok its a MZ600 Xoom 3G+WiFi, rooted, don't know the rom but I can find out.
I don't know too much about the details as to how this problem occurred, but if it is absolutely necessary to know, I can find out.
I can successfully flash all of these images using fastboot. But after I flash all images, clear cache, lock oem, and restart it leads me to the motorola logo and a message that says "Failed to boot LNX 0x0004; Starting RSD mode 2; (battery level)." I tried flashing this sbf file but it gave an error reading "Failed flashing process". (My device is recognizable in RSD) But it's not a recognized device when I run adb devices
So I can scroll through RSD, Fastboot, and Android Recovery fine, but I've tried several images to flash yet I still get stuck on the "M" .
mikeay93 said:
Ok its a MZ600 Xoom 3G+WiFi, rooted, don't know the rom but I can find out.
I don't know too much about the details as to how this problem occurred, but if it is absolutely necessary to know, I can find out.
I can successfully flash all of these images using fastboot. But after I flash all images, clear cache, lock oem, and restart it leads me to the motorola logo and a message that says "Failed to boot LNX 0x0004; Starting RSD mode 2; (battery level)." I tried flashing this sbf file but it gave an error reading "Failed flashing process". (My device is recognizable in RSD) But it's not a recognized device when I run adb devices
So I can scroll through RSD, Fastboot, and Android Recovery fine, but I've tried several images to flash yet I still get stuck on the "M" .
Click to expand...
Click to collapse
the problem is when you relocked the bootloader. It was a "bad lock". You need to UNLOCK the bootloader then the device should boot up normal......RSD will recognized your device but with a screwed up bootloader nothing will flash.......also fastboot and adb will have the same result because of this
**here is what to do**
Option#1 - Try this first
1. connect Xoom to PC with Moto USB Cable (the one shipped with Xoom if possible)
2. ADB command: fastboot reboot-bootloader
3. It will show
4. Then Press Pwr + Vup (reset xoom)
5. When Xoom go into black screen (before the Moto logo appear), press and hold volume down button. I was then successfully get into Fastboot.
In step no. 5, you must press and hold the volume down button, if you release the button, Xoom will reset by itself and you will again caught in the "Failed to boot LNX 0x0004" screen. If you accidentally let go the volume down button, repeat step 4 - 5, and make sure you will not let go the volume down button this time.
Then, one of your hand is holding the volume down button, use your another hand to enter an ADB command: "fastboot oem unlock", you will be able to unlock your bootloader, and xoom will reboot normally.
Yes, I understand your xoom is not working proper but this may take 5 or 6 tries......keep at it. This has had many successes.
-------------
Option#2 - If option#1 does not work
Follow these steps to modify your USB cable to a programming cable
http://forum.xda-developers.com/showthread.php?t=1108518&page=2
Here is a tutorial if you decided to go this route
http://www.droidforums.net/forum/droid-labs/146492-how-why-make-your-own-motorola-factory-cable.html
This too works......but make sure your contacts/wires do not touch other wise you zoom may die when everything gets plugged making the cable is a pain but it's a life saver.
------------
Those are your ONLY options for recovering from this brick.
NOTE - DO NOT RELOCK BOOTLOADER WHEN CONVERTING FROM 3G TO WIFI ONLY. I recommend never touching it after it is unlocked, ever.
The only time locking the bootloader will work is only when you return the device to its original factory condition..........and the only time. Best advice.......after you unlock the bootloader never touch it again.
I hope this helps. Good luck.
Sent from my Xoom using Tapatalk 2
Oh ya I forgot to mention that I've been able to unlock the device, but the problems are still there.
Cdexsw, I'll use the second method as a last resort.
mikeay93 said:
Oh ya I forgot to mention that I've been able to unlock the device, but the problems are still there.
Cdexsw, I'll use the second method as a last resort.
Click to expand...
Click to collapse
Do you know what version of the bootloader you currently have on your Xoom?
Galaxy Nexus (SCH-I515 VZW/LTE) using Tapa2
I've been swamped with work and finals guys I didn't forget about this. As soon as school finishes I'll put more time into trying to find a solution in case anyone is going through the same thing. Thanks to anyone trying to help out.
Hey guys I'm back. My memory is a little rusty on the topic so let me just tell you where I'm at.
I will be convinced that I have a messed up bootloader once someone explains me this... the Xoom model number on the box says MZ600. Using RSD lite, I have several sbf files downloaded: MZ600, MZ602, MX604. Running the program under administrator, I can only start RSD with the MZ604 sbfs loaded. But once again, my model is a MZ600 yet it will not load that sbf file. Can someone explain to me what is going on here?
Cdexsw, as for the bootloader I have no idea which one is installed.
The error I get from RSD when I flash the mz600 is "Failed flashing process. Unable to retrieve installation values from INI file. (0x7029); phone connected"
The only difference that sets the 600 apart from the 604 is is 3G chip in the 600. They are basically the same units other than that. You can flash a 604 SBF on a 600 with no issues, hence the term "Gedified" my xoom which means converted a 3G/4G to a WiFi only Google Experience Device.
The bootloader issue......not sure on this. Don't flash any bootloader older than 1050 (I think). And stay away from 601, 602 and other SBF files. Use only 600 or 604.
Have you tried fastboot to flash ALL the images instead of the sbf/rsd? There is a thread in this forum containing all of the stick images from HC, ICS, and JB (wifi only). Start with the images for 600, if no work then try the 604 images.
Here is the link for the images
http://forum.xda-developers.com/showthread.php?t=1049485
Oh and if your bootloader is unlocked, DO NOT LOCK IT!!! Skip any step that says to lock it......again, skip ANY step that says to lock it.....trust me......I am saving you a potential headache since you already have enough issues.
Sent from my Galaxy Nexus using Tapatalk 2
cdexsw said:
The only difference that sets the 600 apart from the 604 is is 3G chip in the 600. They are basically the same units other than that. You can flash a 604 SBF on a 600 with no issues, hence the term "Gedified" my xoom which means converted a 3G/4G to a WiFi only Google Experience Device.
The bootloader issue......not sure on this. Don't flash any bootloader older than 1050 (I think). And stay away from 601, 602 and other SBF files. Use only 600 or 604.
Have you tried fastboot to flash ALL the images instead of the sbf/rsd? There is a thread in this forum containing all of the stick images from HC, ICS, and JB (wifi only). Start with the images for 600, if no work then try the 604 images.
Here is the link for the images
http://forum.xda-developers.com/showthread.php?t=1049485
Oh and if your bootloader is unlocked, DO NOT LOCK IT!!! Skip any step that says to lock it......again, skip ANY step that says to lock it.....trust me......I am saving you a potential headache since you already have enough issues.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I tried flashing various boot, system, recovery, and userdata files and they all successfully get flashed through. But on reboot, I still get stuck on the Motorola logo. I tried several 604 images, because those are the only ones that actually start in RSD, but those fail as well. I tried finding out my bootloader information with the command fastboot oem get_unlock_data but the command fails and gives an error on the xoom saying Failed to process command error(0x120000)
So I'm really stuck on what to do next...
Where did you buy it
Reading the posts, you have not indicated which country you are in or where the Xoom came from.
I live in Australia and have a European model MZ601 Xoom purchased in Hong Kong. All of that makes a difference in which ROMs I use and why.
Grege50 said:
Reading the posts, you have not indicated which country you are in or where the Xoom came from.
I live in Australia and have a European model MZ601 Xoom purchased in Hong Kong. All of that makes a difference in which ROMs I use and why.
Click to expand...
Click to collapse
U.S.A....
mikeay93 said:
U.S.A....
Click to expand...
Click to collapse
OK, I will butt out. My only other thought is going into recovery and using the format option to re-format the internal partitions, then re-flash.
Read this thread
http://forum.xda-developers.com/showthread.php?t=2069809
I have a razr hd. I can boot into ap fastboot but thats it. Anything else it sits on red m logo. Cant boot into recovery or anything. I can flash xml using one of matts utility without any fails but rebooting just sits on red m.Please help.
meat-rack said:
I have a razr hd. I can boot into ap fastboot but thats it. Anything else it sits on red m logo. Cant boot into recovery or anything. I can flash xml using one of matts utility without any fails but rebooting just sits on red m.Please help.
Click to expand...
Click to collapse
we are going to need a bit more information to possibly help you.
what did you do to get into this predicament?
are you locked or unlocked?
if locked, what was your system version prior to the issue?
bweN diorD said:
we are going to need a bit more information to possibly help you.
what did you do to get into this predicament?
are you locked or unlocked?
if locked, what was your system version prior to the issue?
Click to expand...
Click to collapse
Same issue for me after OTA. Just processed the OTA as normal and phone will not climb out of the Red M loop. Non rooted, locked device. Attempted to utilize RSD with a few flash files and no luck. Very inexperienced with this. Sorry to be so dense, just looking for any direction possible.
Slickville said:
Same issue for me after OTA. Just processed the OTA as normal and phone will not climb out of the Red M loop. Non rooted, locked device. Attempted to utilize RSD with a few flash files and no luck. Very inexperienced with this. Sorry to be so dense, just looking for any direction possible.
Click to expand...
Click to collapse
i wish i could help you but without knowing exactly what the ota flashed before failing, any advice i give has the real possibility of making your phone worse or possibly perma bricked. the problem is you are locked and we dont yet have a fxz for kk.
that being said, if you still want to try and fix it against my advice i will tell you what to try but I AM NOT RESPONSIBLE IF THIS BRICKS YOUR PHONE OR MAKES IT WORSE IN ANY WAY.
download this xml file http://www.mediafire.com/view/p217akcxwmijcr7/VZW_XT926_4.1.2_9.8.1Q_62_VQW_MR-2_VQW_CFC_DOWN.xml
download the 9.30.1 ota from sbf droid devs
extract it to a folder and DELETE the xml file, then copy the one above into the folder
make sure you have the latest rsd, i think its 6.1.5 (not positive)
load the xml file into rsd and flash as usual
if this does not work, there is no way to fix your phone until the kk fxz is leaked, assuming this doesnt make it worse.
6.1.6 is the newest RSDLite I've seen.
Go here if you haven't applied the OTA yet and your bootloader is locked.
http://www.droidrzr.com/index.php/topic/45494-how-to-xt926-upgrade-to-kitkat-ota/
If you have applied the OTA and you're locked, don't do it. You'll have to wait for the FXZ to come out. Otherwise, it will brick even further.
If you have applied the OTA AND your bootloader is UNLOCKED, then you can use the tool to flash back to stock 9.30.1.
I too am bricked. unrooted and locked. Ran the ota and when it reset, it now hangs at the red M. Can get into fast boot and recovery. Tried factory restore and wipe cache. Once I did that my phone now randomly boots to andy all opened up, waiting for me to press the buttons to go into recovery. If I leave it like that, it just reboots after a time and does it all over again . I'm going to assume the only way forward is the xfz file? Any body have an idea of when that might become available and where about I can pick it up? I.E. which forum might have it and will it be a new thread?
Grimaldus3320 said:
I too am bricked. unrooted and locked. Ran the ota and when it reset, it now hangs at the red M. Can get into fast boot and recovery. Tried factory restore and wipe cache. Once I did that my phone now randomly boots to andy all opened up, waiting for me to press the buttons to go into recovery. If I leave it like that, it just reboots after a time and does it all over again . I'm going to assume the only way forward is the xfz file? Any body have an idea of when that might become available and where about I can pick it up? I.E. which forum might have it and will it be a new thread?
Click to expand...
Click to collapse
This has been posted many times. When installing the OTA manually via recovery, a few things happen:
The first time you apply the OTA in recovery, it replaces the recovery with a new recovery and reboots the phone. This new recovery requires a new key combo to get into it. The new key combo is vol-up + power.
So, after you attempt to apply the OTA the first time, you need to be around so when it reboots into the Andy screen, you can use the new key combo. Otherwise, if you leave it alone, it will reboot and then you'll see the red Moto logo which means you'll have to reboot the phone and then hold vol-up + power to get the boot menu and select "Recovery" and then go to the next step.
After getting back into the new recovery, you must apply the OTA again so it can continue to upgrade your phone. After this, you'll be upgraded to Kit Kit.
iBolski said:
This has been posted many times. When installing the OTA manually via recovery, a few things happen:
The first time you apply the OTA in recovery, it replaces the recovery with a new recovery and reboots the phone. This new recovery requires a new key combo to get into it. The new key combo is vol-up + power.
So, after you attempt to apply the OTA the first time, you need to be around so when it reboots into the Andy screen, you can use the new key combo. Otherwise, if you leave it alone, it will reboot and then you'll see the red Moto logo which means you'll have to reboot the phone and then hold vol-up + power to get the boot menu and select "Recovery" and then go to the next step.
After getting back into the new recovery, you must apply the OTA again so it can continue to upgrade your phone. After this, you'll be upgraded to Kit Kit.
Click to expand...
Click to collapse
Right. By reading your earlier posts instructions I got into recovery. That is how I was able to factory reset and wipe cache. I'm talking about AFTER I did all that, instead of just being hung at red m screen, it hangs for a few seconds, then flickers, hangs a few more seconds, and then goes into andy screen. If I don't touch it for a few minutes, it reboots, and that same process starts over, ending with the andy screen again...Its like it WANTS me to be in recovery to fix it .
I noticed you also said to others that us lot are pretty much screwed until the fxz file is out, which I assume is this OTA as a zip so we can flash with recovery? Any idea when that will be coming out? and where should I look for it once its out?
Heck, because I was unrooted and locked and it was the official OTA from verizon, maybe I should go in to them and demand they replace my phone with the moto x. Though, I rather liked my razr hd and don't quite wanna give up on it...
Grimaldus3320 said:
Right. By reading your earlier posts instructions I got into recovery. That is how I was able to factory reset and wipe cache. I'm talking about AFTER I did all that, instead of just being hung at red m screen, it hangs for a few seconds, then flickers, hangs a few more seconds, and then goes into andy screen. If I don't touch it for a few minutes, it reboots, and that same process starts over, ending with the andy screen again...Its like it WANTS me to be in recovery to fix it .
I noticed you also said to others that us lot are pretty much screwed until the fxz file is out, which I assume is this OTA as a zip so we can flash with recovery? Any idea when that will be coming out? and where should I look for it once its out?
Heck, because I was unrooted and locked and it was the official OTA from verizon, maybe I should go in to them and demand they replace my phone with the moto x. Though, I rather liked my razr hd and don't quite wanna give up on it...
Click to expand...
Click to collapse
No, the FXZ is the full kit-kat image, not an update like the OTA. The FXZ can be used to flash your phone back to full stock, whether you are locked or not. If you are locked, then you can only flash the version that is currently on your phone or newer. You cannot flash back to a previous version unless your bootloader is unlocked.
The ota is used to only update a previous version to the current version, in this case from JB to KK, but once it's applied, you cannot apply it again since you are already upgraded to that version. It's only an upgrade, not a full image like an FXZ.
iBolski said:
No, the FXZ is the full kit-kat image, not an update like the OTA. The FXZ can be used to flash your phone back to full stock, whether you are locked or not. If you are locked, then you can only flash the version that is currently on your phone or newer. You cannot flash back to a previous version unless your bootloader is unlocked.
The ota is used to only update a previous version to the current version, in this case from JB to KK, but once it's applied, you cannot apply it again since you are already upgraded to that version. It's only an upgrade, not a full image like an FXZ.
Click to expand...
Click to collapse
I see, makes sense. Every days a school day I suppose. Thanks for the info. Guess I have to decide to either wait for the FXZ or go to verizon and see if they can get me a new phone.
Same thing happened to my wife, completely stock now stuck at red m. After calling verizon they suggested the factory reset which just gives you a boot to dead android guy to get into recovery on every boot. Then after a couple minutes just reboots and does the same thing, stuck in a loop. They then said it's not their software, rather Motorola's, so Verizon's only recourse is to sell me an overpriced refurb or upgrade to the edge plan. Screw them. I said unacceptable and they gave me a number for Motorola. Moto said that they put in a request to extend my factory warranty because it was the software update that caused the issue and they will let me know tomorrow. I understand stuff happens, but this is not acceptable when their harassing update causes thee issue. I knew I should've unlocked the boot loader on it when I had the chance.
al2fast said:
Same thing happened to my wife, completely stock now stuck at red m. After calling verizon they suggested the factory reset which just gives you a boot to dead android guy to get into recovery on every boot. Then after a couple minutes just reboots and does the same thing, stuck in a loop. They then said it's not their software, rather Motorola's, so Verizon's only recourse is to sell me an overpriced refurb or upgrade to the edge plan. Screw them. I said unacceptable and they gave me a number for Motorola. Moto said that they put in a request to extend my factory warranty because it was the software update that caused the issue and they will let me know tomorrow. I understand stuff happens, but this is not acceptable when their harassing update causes thee issue. I knew I should've unlocked the boot loader on it when I had the chance.
Click to expand...
Click to collapse
Then you're almost there. At the "dead android" screen, press and hold vol up and then press power and then release both buttons. This gets you into recovery.
At this point, reinstall the OTA via the recovery so it can start into the 2nd stage and then you'll be done.
iBolski said:
Then you're almost there. At the "dead android" screen, press and hold vol up and then press power and then release both buttons. This gets you into recovery.
At this point, reinstall the OTA via the recovery so it can start into the 2nd stage and then you'll be done.
Click to expand...
Click to collapse
I don't know how to reinstall the OTA via stock recovery. I tried it do the install update.zip option and nothing happened. Any pointers would be appreciated.
al2fast said:
I don't know how to reinstall the OTA via stock recovery. I tried it do the install update.zip option and nothing happened. Any pointers would be appreciated.
Click to expand...
Click to collapse
Did you download it to your phone? If so, it needs to be on your external SD card and you choose the option to install from there. You'll have to navigate to where you stored it on the external SD card.
If you didn't download it, then you should be able to push it via ADB PUSH when in the recovery. Just hook up your phone to your PC and do it that way. Just obtain the OTA from this thread. Somewhere, someone provided a link to it. Download it to your PC and then do an adb push to the external SD card of the OTA and then install it that way.
iBolski said:
Did you download it to your phone? If so, it needs to be on your external SD card and you choose the option to install from there. You'll have to navigate to where you stored it on the external SD card.
If you didn't download it, then you should be able to push it via ADB PUSH when in the recovery. Just hook up your phone to your PC and do it that way. Just obtain the OTA from this thread. Somewhere, someone provided a link to it. Download it to your PC and then do an adb push to the external SD card of the OTA and then install it that way.
Click to expand...
Click to collapse
Thanks for the tips. I must have done something wrong when I installed adb, I could not see the phone with the adb devices command, yet I could see the phone in the Matt utility as well as in RSD Lite. I'll give it a shot again, can't hurt. Called Moto and they escalated it and are sending me a replacement device.
Okay guys, now I baught a moto g x1032 from ebay, gave it a try and It seemed laggy and buggy, went to settings and found that it was running a custom rom, so I wanted to go back to stock and I found a tutorial and I pretty much followed the tutorial, the tutorial said to download mfastboot, the firmware file, and adb fastboot as well as the drivers.
I did all of that, I installed the stock firmware and went to turn the phone on and it just shows the motorola logo then restarts.
I'm not sure what to do to get it working, I even downloaded another stock rom but it was in .zip format so I needed to transfer it to the phone and install it via cwm, I tried to install it via sideload but I kept getting the error on adb: error device not found.
I can still get into the fastboot menu by holding down the volume down + power.
I have also read that you apparantly need to have debug mode enabled, but how am I supposed to enable that when I can't get past the boot screen?
All i can think of is that maybe i was trying to downgrade the device when i shouldn't be?
If anyone can help me with this or point me in the right direction to fixing this phone back to stock that would be great.
Thank you.
What version of android did the phone come with? And what version did you try to flash?
I believe it came with 4.4 and I tried flashing 4.4 normal edition.
The phone now boots up but there is no sound or vibration or anything, tried making a call and the phone freezes, any ideas?
Which retail 4.4.4 are you needing? I can upload the UK version I use.
ramo55 said:
Okay guys, now I baught a moto g x1032 from ebay, gave it a try and It seemed laggy and buggy, went to settings and found that it was running a custom rom, so I wanted to go back to stock and I found a tutorial and I pretty much followed the tutorial, the tutorial said to download mfastboot, the firmware file, and adb fastboot as well as the drivers.
I did all of that, I installed the stock firmware and went to turn the phone on and it just shows the motorola logo then restarts.
I'm not sure what to do to get it working, I even downloaded another stock rom but it was in .zip format so I needed to transfer it to the phone and install it via cwm, I tried to install it via sideload but I kept getting the error on adb: error device not found.
I can still get into the fastboot menu by holding down the volume down + power.
I have also read that you apparantly need to have debug mode enabled, but how am I supposed to enable that when I can't get past the boot screen?
All i can think of is that maybe i was trying to downgrade the device when i shouldn't be?
If anyone can help me with this or point me in the right direction to fixing this phone back to stock that would be great.
Thank you.
Click to expand...
Click to collapse
You can flash one from here via recovery: http://forum.xda-developers.com/moto-g/development/rom-stock-motorola-rom-collection-t2854688 then reboot.