Related
I'm running a 100% stock sensation and the OTA update hasn't hit my phone yet.
Is there an easy way to install it from my sd card? I read somewhere that i'd need to boot into recovery, but I can't get that to work either.
Any help would be greatly appreciated.
download the zip file
rename it to update.zip
put it on the root of your microsd card.
boot into recovery.
either TURN OFF FAST BOOT in the power menu and turn off phone, or pull the battery and put it back in
hold down volume down and power.
you'll get into bootloader.
use the volume buttons to go up/down and select recovery. press power to select.
you'll get triangle with ! on it.
press power then volume up real quick/at the same time
you'll get the stock recovery.
go down to select install update.zip.
Download the OTA to the root of the sd card. Then take batt out. Put batt back in. Then hold- vol down + power. That will take to you the hboot menu. Let it look for the .img and then it will take you to a new menu. From there click on 2nd icon, recovery. It will either start for you or you will get a red triangle. If you get the red triangle. press vol up+ power. then click on update from sd card, then click on the update file. Hope this helps.
Edit- I was too slow typing
Root folder would just be /sdcard if I'm using root explorer, right?
Can't get it to work, I'm sure I'm doing something stupid and not realizing it.
When I select 'apply update from sdcard' it says Invalid Operation and then reboots the phone without updating anything
It also says: "E:Can't open/cache/recovery/command" when I open up that second console.
Any clue why that's happening?
RuizGT said:
Root folder would just be /sdcard if I'm using root explorer, right?
Can't get it to work, I'm sure I'm doing something stupid and not realizing it.
Click to expand...
Click to collapse
Yes. If you have custom recovery, it's not going to work. Has to be stock recovery.
mtbaird5687 said:
When I select 'apply update from sdcard' it says Invalid Operation and then reboots the phone without updating anything
It also says: "E:Can't open/cache/recovery/command" when I open up that second console.
Any clue why that's happening?
Click to expand...
Click to collapse
Did you rename the zip file to update.zip?
nxt said:
Yes. If you have custom recovery, it's not going to work. Has to be stock recovery.
Click to expand...
Click to collapse
That's what I'm using. Phone is still stock.
Yep I renamed it to update.zip. Below is what shows up right after I click 'install update from sd card'
--Invalid Operation--
success rebooting by reasonem-00
mtbaird5687 said:
Yep I renamed it to update.zip. Below is what shows up right after I click 'install update from sd card'
--Invalid Operation--
success rebooting by reasonem-00
Click to expand...
Click to collapse
Same here.
This is really frustrating, I hope it doesn't affect my ability to get the OTA update.
Does anyone have any idea why we're getting the "Illegal Operation" error?
I didn't rename the OTA. It kept it as it was.... all though one thing that I did notice was that I would continue to get an error until the OTA was at the top of the list... Sounds weird but just keep trying.
Ok, on my phone when it downloaded the update, it put it in the /download/ folder on my microsd card.
You guys should try that maybe.
nxt said:
Ok, on my phone when it downloaded the update, it put it in the /download/ folder on my microsd card.
You guys should try that maybe.
Click to expand...
Click to collapse
I'll try that right now.
nope, same thing.I'll try to re-dl and keep the regular file name.
Double edit; tried the full file name in download folder, same thing again.
nxt said:
download the zip file
rename it to update.zip
put it on the root of your microsd card.
boot into recovery.
either TURN OFF FAST BOOT in the power menu and turn off phone, or pull the battery and put it back in
hold down volume down and power.
you'll get into bootloader.
use the volume buttons to go up/down and select recovery. press power to select.
you'll get triangle with ! on it.
press power then volume up real quick/at the same time
you'll get the stock recovery.
go down to select install update.zip.
Click to expand...
Click to collapse
Do you know which one I would need for Canada's Virgin Mobile and where I can find it? I tried Searching and I couldn't find it.
mtbaird5687 said:
When I select 'apply update from sdcard' it says Invalid Operation and then reboots the phone without updating anything
It also says: "E:Can't open/cache/recovery/command" when I open up that second console.
Any clue why that's happening?
Click to expand...
Click to collapse
I am getting the same error.stock ROM never rooted...may be European update don't work for Asian....
Sent from my HTC Sensation Z710e using XDA App
Asian HTC Sensation Z710e
no go for me either. I get a same error message...
I've used OTA file for European and also US T-Mobile phones. It just wont work on my (Asian WWE) HTC Sensation.
It seems like I am destined to wait until end of September before I get my update...
I have purchased my phone at negrielectronics.com
Any other users of this version of Sensation? What's your experience?
I gave up, did s-off, and did a 1.45 based rom instead, heh.
I was lucky enough to get the OTA today and the other errors I had didn't prevent me from getting the update.
Good luck guys!
mtbaird5687 said:
I was lucky enough to get the OTA today and the other errors I had didn't prevent me from getting the update.
Good luck guys!
Click to expand...
Click to collapse
Nice. I work at a tmo retailer, the demo sensation had the ota update symbol in the notification bar when I was unplugging phones this morning, it installed fine, just pissed me off more about mine. :|
Hi,
I just tried performing the ICS update on my Transformer. However during this process, the tablet showed a yellow triangle with a black exclamation mark in it. I waited for about 10 minutes to see if anything would happen, but it just stayed on this screen. So I powered it down and tried turning it back on, but it just gets stuck on the Asus/Nvidia splash screen on boot.
I have tried holding the power button and volume down and entering recovery mode, however I get the same yellow triangle as I had before. If I wait without going in to recovery I get the option of performing a cold boot or wiping the data on the tablet. If I select cold boot, it just hangs, I have left it there for 10 minutes or so to see if it would work but get nothing. I have also tried wiping the data from this menu then retrying all the steps I have mentioned above, but it still doesn't work.
It is not rooted and I have applied all other updates to it without trouble so far. Is there anything I can do to fix this?
Thanks,
Ryan
I had the exact same problem. Got it fixed. Use the method from this thread: tabletroms.com/forums/transformer-rom-development/1071-asus-transformer-nvflash-stock-3-1-stock-3-2-recovery-roms-unbricking-tools.html
Thanks for your reply. I noticed on that page that it says that if the serial number is BD70 or above (which mine is) do not use the tool. Has there been an update that allows this to be used on the newer units?
Thanks,
Ryan
Hi there!
I got a similar problem yesterday and the error was that a file inside the DATA partition could not be deleted. I noticed when doing a factory reset from CWM.
If you have CWM and you can flash the "super wipe tool" you can fix the problem. Then you re-flash the ROM. I got it working and now I'm on a clean clean clean clean.... clean shiny install
check my threat if you want:
http://forum.xda-developers.com/showthread.php?t=1516204
Hope it helps!
I'm guessing I do not have CWM as I do not know what it is?
Thanks,
Ryan
sh.assassin said:
Hi,
I just tried performing the ICS update on my Transformer. However during this process, the tablet showed a yellow triangle with a black exclamation mark in it. I waited for about 10 minutes to see if anything would happen, but it just stayed on this screen. So I powered it down and tried turning it back on, but it just gets stuck on the Asus/Nvidia splash screen on boot.
I have tried holding the power button and volume down and entering recovery mode, however I get the same yellow triangle as I had before. If I wait without going in to recovery I get the option of performing a cold boot or wiping the data on the tablet. If I select cold boot, it just hangs, I have left it there for 10 minutes or so to see if it would work but get nothing. I have also tried wiping the data from this menu then retrying all the steps I have mentioned above, but it still doesn't work.
It is not rooted and I have applied all other updates to it without trouble so far. Is there anything I can do to fix this?
Thanks,
Ryan
Click to expand...
Click to collapse
Ok, I'm going to help you unbrick your device. But you need to forget everything other people in here have told you. Ok? And just do. Don't question. Just follow the steps.
(1) Go to the following asus webpage, choose android as OS and download your version of the 21 firmware. WW, US, TW, etc.
http://www.asus.com/Eee/Eee_Pad/Eee_Pad_Transformer_TF101/#download
(2) Rename the downloaded zip file to "EP101_SDUPDATE.zip"
(3) Move zip file to a micro sdcard.
(4) Insert microsdcard into the TF.
(5) Turn off TF.
(6) Power on by pressing power button and volume down buttons at the same time. When white texts appear on upper left hand corner, release power button and volume down buttons and press volume up button.
(7) Watch your TF unbricking itself.
(8) Leave it alone to do its thing.
(9) Write me a check for 2,000 yen.
Thanks, that has sucessfully unbricked the tablet.
However if I try to attempt the ICS update again it says checking integrity of firmware file and then says update failed.
Does anyone have any ideas as to why this is happening?
Thanks,
Ryan
british.assassin said:
Thanks, that has sucessfully unbricked the tablet.
However if I try to attempt the ICS update again it says checking integrity of firmware file and then says update failed.
Does anyone have any ideas as to why this is happening?
Thanks,
Ryan
Click to expand...
Click to collapse
Download is corrupted. Have you tried again?
Yes I have, about 10 times and it always comes up with that error.
I had the same failure and had to install .13 and update 3times to get to ICS. Got it from the Unlockr link. Worked great and then rooted with ViperMod.
A clean install is seemingly not having as many issues. Plus I already have an AOKP ICS rom on my phone, so I already know most of the ICS features.
I did try downloading .13 and installing it the same way as I did .21 (putting in on the micro sd and powering on with power & vol - to get into recovery mode), however when I try this I get the yellow triangle and black exclamation mark again, only this time it does not stop my tablet from booting back in to .21.
british.assassin said:
Yes I have, about 10 times and it always comes up with that error.
Click to expand...
Click to collapse
This error comes up when you have a corruption in your stock recovery.
You won't be able to "downgrade" to .13 the way you did with this. Unfortunately, there's no easy way for you to go about this. Here is what you need to do. Yeah, it will be a little long.
(1) Root via nachoroot.
(2) Install CWM via recovery installer. Can be found in the app portion of this forum.
(3) Download the repacked .13 version from the following link.
http://dl.project-voodoo.org/transformer-roms/3.0.x/
(4) Download stock recovery.
http://forum.xda-developers.com/attachment.php?attachmentid=606402&d=1306284085
(5) Flash the repacked .13 version via CWM.
(6) Restart the TF.
(7) Flash the stock recovery.
(8) Restart TF.
(9) Upgrade via OTA. One of the updates will give you the appropriate stock recovery.
Failure to follow my instructions precisely will result in brick.
Hi,
Someone gave me a Tf700t. On bootup it says unlocked, shows the Asus screen and then keeps rebooting. If I reboot and hold down the volume down arrow I get the menu with four choice ROC, Android, USB, Wipe.
When I press ROC I get the red triangle.
I've read many threads and I think this indicates its bricked and can't be recovered. I just want to confirm before I sell it for parts.
Thanks in advance for the help.
Mark
mmanis said:
Hi,
Someone gave me a Tf700t. On bootup it says unlocked, shows the Asus screen and then keeps rebooting. If I reboot and hold down the volume down arrow I get the menu with four choice ROC, Android, USB, Wipe.
When I press ROC I get the red triangle.
I've read many threads and I think this indicates its bricked and can't be recovered. I just want to confirm before I sell it for parts.
Thanks in advance for the help.
Mark
Click to expand...
Click to collapse
Actually, since you do have access to the bootloader this may be recoverable.
You have 4 icons in the BL menu, so it's a ICS bootloader. The dead Droid on his back when you select RCK is normal - it's the stock recovery not finding a valid update file.
The easiest way to try to get your tablet back to life would be to download the full Asus firmware from here: http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS Transformer Pad Infinity TF700T&p=28&s=1
Select "Android" as the OS. From the resulting list, choose the firmware for your SKU: US if you are in the USA.
If you are considering running a custom rom do yourself a favor and go for the 10.6.1.14.8 version, NOT the latest firmware 10.6.1.14.10. The .8 version can be rooted, the .10 not.
Download the .zip file, extract it ONCE, getting another zip and rename that file to: EP201_768_SDUPDATE.zip
Copy that file to a FAT32 formatted microSD (that's the factory default) and insert it into the tablet.
Boot into recovery (Power and Volume Down, then Volume Up to select RCK) and hopefully the recovery will recognize the file and start to flash it. Be patient - it'll take a while. Wait for it to reboot.
berndblb said:
Actually, since you do have access to the bootloader this may be recoverable.
You have 4 icons in the BL menu, so it's a ICS bootloader. The dead Droid on his back when you select RCK is normal - it's the stock recovery not finding a valid update file.
The easiest way to try to get your tablet back to life would be to download the full Asus firmware from here:
Select "Android" as the OS. From the resulting list, choose the firmware for your SKU: US if you are in the USA.
If you are considering running a custom rom do yourself a favor and go for the 10.6.1.14.8 version, NOT the latest firmware 10.6.1.14.10. The .8 version can be rooted, the .10 not.
Download the .zip file, extract it ONCE, getting another zip and rename that file to: EP201_768_SDUPDATE.zip
Copy that file to a FAT32 formatted microSD (that's the factory default) and insert it into the tablet.
Boot into recovery (Power and Volume Down, then Volume Up to select RCK) and hopefully the recovery will recognize the file and start to flash it. Be patient - it'll take a while. Wait for it to reboot.
Click to expand...
Click to collapse
Well that partially worked. Thanks so much!!!
It was able to flash the firmware. It rebooted 5 times before the os came up. I then shut it down. When I turned it on it goes to the Asus screen and then keeps on rebooting indefinitely. I then hit the volume up and power button to reset and then it rebooted 5 times before the OS came up. BTW I flash with 10.6.1.14.10.
Any ideas?
Thanks again,
Mark
mmanis said:
Well that partially worked. Thanks so much!!!
It was able to flash the firmware. It rebooted 5 times before the os came up. I then shut it down. When I turned it on it goes to the Asus screen and then keeps on rebooting indefinitely. I then hit the volume up and power button to reset and then it rebooted 5 times before the OS came up. BTW I flash with 10.6.1.14.10.
Any ideas?
Thanks again,
Mark
Click to expand...
Click to collapse
Hmm, still bootlooping.
Next thing I would try is to boot into the bootloader, select 'Wipe Data' with the Volume Down button, hit Volume Up execute.
And actually, before even booting back to system (that would be choosing the Android), I would reflash the firmware - just for good measure after the data wipe.
Can't wait to hear if that solves it!
So I downgraded to .8. Rooted. Was able to install TWRP. Reflashed, wiped and it still reboots multiple time before coming up. I tried to flash CyanogenMod but all I get is the spinning Cyanogen wheel. I was able to restore .8. Its not bricked anymore. Its just weird that it keeps rebooting before coming up. But at least its now consistent and will come up every time whether from power on or reset.
Thanks,
Mark
mmanis said:
So I downgraded to .8. Rooted. Was able to install TWRP. Reflashed, wiped and it still reboots multiple time before coming up. I tried to flash CyanogenMod but all I get is the spinning Cyanogen wheel. I was able to restore .8. Its not bricked anymore. Its just weird that it keeps rebooting before coming up. But at least its now consistent and will come up every time whether from power on or reset.
Thanks,
Mark
Click to expand...
Click to collapse
Great job so far! That you got TWRP installed is very good and gives you many more options. It's version 3.6.1? Have you tried to capture a logcat of the boot process?
The logcat may reveal the cause of this and then you could target the problem easier.
If you can't get a logcat my next step would be to format the data partition. Since you probably do not have that much data on it yet, this is the perfect time for that. Always a good idea when you move to a different rom and major framework change.
Go for a Wipe > Advanced > Format Data. It could be that there's something left behind from a former installation that causes the bootloop.
After the format you have to reflash the rom - or restore your .8 nandroid. Although I would go for CROMi-X 5.0.4. Love that rom. Excellent support too.
sbdags, creator of this rom, also provides a bootloader and several kernels.
I mean, if you flash a new bootloader and kernel, format data, clean install the rom and you still get bootloops, it's got to be hardware related. At least I would be out of ideas at that point.
berndblb said:
Great job so far! That you got TWRP installed is very good and gives you many more options. It's version 3.6.1? Have you tried to capture a logcat of the boot process?
The logcat may reveal the cause of this and then you could target the problem easier.
If you can't get a logcat my next step would be to format the data partition. Since you probably do not have that much data on it yet, this is the perfect time for that. Always a good idea when you move to a different rom and major framework change.
Go for a Wipe > Advanced > Format Data. It could be that there's something left behind from a former installation that causes the bootloop.
After the format you have to reflash the rom - or restore your .8 nandroid. Although I would go for CROMi-X 5.0.4. Love that rom. Excellent support too.
sbdags, creator of this rom, also provides a bootloader and several kernels.
I mean, if you flash a new bootloader and kernel, format data, clean install the rom and you still get bootloops, it's got to be hardware related. At least I would be out of ideas at that point.
Click to expand...
Click to collapse
Hi, how do you capture a logcat. FYI, I flashed with CROMi. It kept hanging on reboot. Finally it booted and worked. I shut it down and now I'm back into the endless looping boot cycle. One thing I didn't mention before when the unit is off the only way it will turn on is if I hold the power button down for 10 seconds.
Thanks,
Mark
mmanis said:
Hi, how do you capture a logcat. FYI, I flashed with CROMi. It kept hanging on reboot. Finally it booted and worked. I shut it down and now I'm back into the endless looping boot cycle. One thing I didn't mention before when the unit is off the only way it will turn on is if I hold the power button down for 10 seconds.
Thanks,
Mark
Click to expand...
Click to collapse
Did you format data?
http://forum.xda-developers.com/showthread.php?t=1378491
berndblb said:
Did you format data?
http://forum.xda-developers.com/showthread.php?t=1378491
Click to expand...
Click to collapse
Yes I formatted data. Its very weird it only will boot correctly after I re-flash or about once every 10 times.
Thanks again.
Mark
mmanis said:
Hi, how do you capture a logcat
Click to expand...
Click to collapse
This was at the top of the xda portal http://forum.xda-developers.com/showthread.php?t=2274119
best bookmark it for future reference its a really good tutorial
mmanis said:
Yes I formatted data. Its very weird it only will boot correctly after I re-flash or about once every 10 times.
Thanks again.
Mark
Click to expand...
Click to collapse
At this point only a bootloop logcat can shed light on this. Check the tutorial JTR recommended. It's truly good - thanks for the link!
Hi,
I've attached the logcat. What I did first was do a total wipe, system, data, cache and then reinstalled the rom.
Still having trouble booting once I shutdown and turn it back on.
All the help is greatly appreciated.
Thanks,
Mark
mmanis said:
Hi,
I've attached the logcat. What I did first was do a total wipe, system, data, cache and then reinstalled the rom.
Still having trouble booting once I shutdown and turn it back on.
All the help is greatly appreciated.
Thanks,
Mark
Click to expand...
Click to collapse
Great! Now we need to try to get someone's attention who can actually read and interpret the logcat - that is where my usefulness ends...
@sbdags, @_that, @JoinTheRealms to the rescue???
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
berndblb said:
Great! Now we need to try to get someone's attention who can actually read and interpret the logcat - that is where my usefulness ends...
@sbdags, @_that, @JoinTheRealms to the rescue???
Sent from my ASUS Transformer Pad TF700T using Tapatalk 4
Click to expand...
Click to collapse
Right try booting without the microsd card in. Something is wrong with it. Also turn off the Bluetooth, what ever it is trying to connect to is adding lots of entries to the log.
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.
I tried to update my HTC One [m7] unlocked/international to the new Android Lollipop with the OTA update that got pushed yesterday. However, it keeps failing. My HTC is rooted, and is currently running 6.12.161.9 (trying to update to 7.18.616.2). It is S-ON and has an hboot 1.57. Now, the problem keeps appearing in the following way.(I installed stock recovery of 6.12.161.9 :crying:version) The phone starts the update process normally. It goes to the recovery and the progress bar starts to move. However as soon as it reaches about 1/4 of its way (always the same), it stops the installation and returns to the recovery title screen (the red triangle and exclamation mark). When I then press volume up and power button to see the recovery menu, it gives me the following readout at the bottom on the console:
Code:
"/system/lib/modules/ansi_cprng.ko" has unexpected contents
What i have to do now....?
Am i going correct..?:crying:
abhishek7008 said:
I tried to update my HTC One [m7] unlocked/international to the new Android Lollipop with the OTA update that got pushed yesterday. However, it keeps failing. My HTC is rooted, and is currently running 6.12.161.9 (trying to update to 7.18.616.2). It is S-ON and has an hboot 1.57. Now, the problem keeps appearing in the following way.(I installed stock recovery of 6.12.161.9 :crying:version) The phone starts the update process normally. It goes to the recovery and the progress bar starts to move. However as soon as it reaches about 1/4 of its way (always the same), it stops the installation and returns to the recovery title screen (the red triangle and exclamation mark). When I then press volume up and power button to see the recovery menu, it gives me the following readout at the bottom on the console:
Code:
"/system/lib/modules/ansi_cprng.ko" has unexpected contents
What i have to do now....?
Am i going correct..?:crying:
Click to expand...
Click to collapse
first go the easy way .format external memory and reset the phone to factory ......then give it a try.. make sure you backup first
if it doesnt help then follow this thread http://forum.xda-developers.com/showthread.php?t=2358738
zargham khan said:
first go the easy way .format external memory and reset the phone to factory ......then give it a try.. make sure you backup first
if it doesnt help then follow this thread http://forum.xda-developers.com/showthread.php?t=2358738
Click to expand...
Click to collapse
factory resetting doesnt helped me....installation stopped in half with red eclamation mark!
can i use RUU for making my htc stock(because i am S-ON)...if yes can you please suggest the best suited RUU according to my configuration.... or if anybody have easier way please help me!
i got messed up in these things
Thanks ah lot in advance....:good:
abhishek7008 said:
factory resetting doesnt helped me....installation stopped in half with red eclamation mark!
can i use RUU for making my htc stock(because i am S-ON)...if yes can you please suggest the best suited RUU according to my configuration.... or if anybody have easier way please help me!
i got messed up in these things
Thanks ah lot in advance....:good:
Click to expand...
Click to collapse
check the following threads .you will find your answer there
http://forum.xda-developers.com/showthread.php?t=2784985
http://forum.xda-developers.com/htc-one/help/help-flashing-bricked-htc-one-m7-t2874526
http://forum.xda-developers.com/htc-one