Help with my (bricked?) M9, please? - T-Mobile HTC One (M9)

I've got a T-Mobile M9 with a locked bootloader and no recovery. I am unable to boot into the system and thus can't enable USB debugging. I foolishly relocked it trying to flash an RUU and now it won't boot. I have tried re-unlocking it thru fastboot but the commands are not recognized.
Please help?!?

I would recommend downloading the RUU image, renaming it "0PJAIMG.zip" and then placing it in the root directory of a microsd card and putting that into your device. Then reboot into fastmode (download mode), holding vol-down immediately after powering on. It should hopefully detect the zip image and restore the phone to factory condition.
That's if fastboot is not working. Make sure your commands are correct too. I'm sure you're fully aware but doesn't hurt to double check.
Good luck.
---------- Post added at 07:40 AM ---------- Previous post was at 07:39 AM ----------
BTW, you dont need to relock the bootloader (at least I didnt have to) to install a RUU.

minotauri said:
I would recommend downloading the RUU image, renaming it "0PJAIMG.zip" and then placing it in the root directory of a microsd card and putting that into your device. Then reboot into fastmode (download mode), holding vol-down immediately after powering on. It should hopefully detect the zip image and restore the phone to factory condition.
That's if fastboot is not working. Make sure your commands are correct too. I'm sure you're fully aware but doesn't hurt to double check.
Good luck.
---------- Post added at 07:40 AM ---------- Previous post was at 07:39 AM ----------
BTW, you dont need to relock the bootloader (at least I didnt have to) to install a RUU.
Click to expand...
Click to collapse
Thanks so much, dude! My M9 is back up and running. Looked everywhere on the Internet and didn't see that method anywhere.

I was in the same predicament. Bricked mine trying to install a custom ROM. I get the following error:
Failed: -2, 22: fail to flash via download
Failed: -2, 22: fail to flash via download
Failed: -2, 22: fail to flash via download

minotauri said:
I would recommend downloading the RUU image, renaming it "0PJAIMG.zip" and then placing it in the root directory of a microsd card and putting that into your device. Then reboot into fastmode (download mode), holding vol-down immediately after powering on. It should hopefully detect the zip image and restore the phone to factory condition.
That's if fastboot is not working. Make sure your commands are correct too. I'm sure you're fully aware but doesn't hurt to double check.
Good luck.
---------- Post added at 07:40 AM ---------- Previous post was at 07:39 AM ----------
BTW, you dont need to relock the bootloader (at least I didnt have to) to install a RUU.
Click to expand...
Click to collapse
Thanks so much! I friggin love you for being the only one in the history of the Internet to suggest this very simple solution.

deepdownnyc said:
Thanks so much! I friggin love you for being the only one in the history of the Internet to suggest this very simple solution.
Click to expand...
Click to collapse
Yeah it's actually the most common way of flashing a RUU and it's posted all over. Even a giant thread on it in the international forum. I don't think you looked very hard through "the history of the Internet."

Related

[A] Solved the Seven Vibration Brick

\\\Disclaimer: I am not responsible if you mess this up & break your phone///
Checking Your Situation:
*Phone only boots to Fastboot
*Phone does/Doesn't charge
*Power button Seems useless
*Phone Turns on and only shows-
the X screen & Vibrates 7x's
*LED Only shows Green/ Orange
indication light
Things You'll Need:
*Wall Charger
*USB Cable
*Computer (duh)
*Battery (of course)
*FRG83 ROM file http://tinyurl.com/6bym3vg
*Android ADB Setup
*Fingers Crossed
(Tip: if you are using the same Sdcard when the phone messed up, reformat it or use a new one)
Step One:
Download FRG83 ROM file http://tinyurl.com/6bym3vg
and unzip the package into your AndroidSDK Tools Folder
Step Two:
Watch the battery trick video
http://youtu.be/2O5adV-jj64 (Thanks n1newbie)
Once you've analyzed the video enough
plug your phone (while it's off) to the wall
charger and while doing the wall trick !!Make
sure you hold down the Volume-Down Button!! so
you can boot into fastboot.
Step Three:
Once established fastboot, plug the phone
to your computer and let your computer discover the
device.
!!Make sure the device says Fastboot USB!!
Open Command Promt (CMD). If you already
know how to use Android ADB type these commands:
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
fastboot devices
!!Make Sure You Device ID Shows UP!!
fastboot erase userdata
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Let the phone run everything through and you should
be one Froyo.
Step Four:
Power down your phone
Reboot into Recovery (to see if your phone is still rooted)
If you are able to get into recovery flash any ROM
you like and Enjoy your UnBricked Nexus One
lilj4321 said:
If anyone needs the fix for this soft brick
let me know so i can post instructions!
Click to expand...
Click to collapse
You might as well write them out. You never know when someone will need them.
taodan said:
You might as well write them out. You never know when someone will need them.
Click to expand...
Click to collapse
+1. will be very useful n helpful when that occurs. so pls explain the method. thanx
Sent from my Nexus One using Tapatalk
n1newbie said:
+1. will be very useful n helpful when that occurs. so pls explain the method. thanx
Sent from my Nexus One using Tapatalk
Click to expand...
Click to collapse
+2, hope it won't occurs
hi lilj4321. thanx for the steps frnd
the youtube link that you provided returns 404 error. so you might use this link for video trick (by myself )
PS- sry if i am wrng. will the device boot into fastboot mode after the seven vibration brick happens
Sent from my Nexus One using Tapatalk
fixed the link!
no the phone will stay on the X screen until your battery dies
which is why you have to do the battery trick while holding the
volume-down button during the whole process.
lilj4321 said:
fixed the link!
no the phone will stay on the X screen until your battery dies
which is why you have to do the battery trick while holding the
volume-down button during the whole process.
Click to expand...
Click to collapse
oh okies. thanx for using my video buddy
will try this if seven vibration brick happens. but ill pray it shdnt happen
will be helpful for all if it is stickied :thumbup:
just my 2 cents ...
Sent from my Nexus One using Tapatalk
I hoped for something much more useful.
The method of reflashing to stock using fastboot commands has been posted on Nexus One Wiki for 2.5 years now.
And of course, it won't solve any overheating phone, and no "7-vibration brick".
Thanks for trying to help, but the post is kinda (very) useless.
Stuck in fastboot
My phone went into this rare phenomonen "7vibrations no boot"... its been 2weeks. Im not able to fix it till now.
Firstly , My phone doesnt respond in hboot screen when the sdcard is inserted. So for entering fastboot, I will take out sdcard and go to fastboot and then put my sdcard when the phone is connected to PC so that it doesnt turnoff when i pullout the battery. this i have been facing for quite long. cudnt fix it.
I tried exactly what you said.. but im stuck in the fastboot now.. im not able to flash anything using adb in fastboot.
im getting errors in fastboot.
when i typed 'fastboot flash system system.img"
it gives an error like "error: cannot load 'system.img' : unknown error"
did "fastboot erase" and it worked.
but flashing is not happening.
please help me out
---------- Post added at 08:22 PM ---------- Previous post was at 08:02 PM ----------
i somehow managed to flash all those things what u said in your post...
but still when rebooted after flashing via fastboot, the same 7 vibrations happening.
My phone doesnt boot..
i havent done the battery trick as you said. Im not able to do it. That video doesnt have any instruction and no audio too.
any instruction on how to do it will be helpful.
ajaymkd said:
My phone went into this rare phenomonen "7vibrations no boot"... its been 2weeks. Im not able to fix it till now.
Firstly , My phone doesnt respond in hboot screen when the sdcard is inserted. So for entering fastboot, I will take out sdcard and go to fastboot and then put my sdcard when the phone is connected to PC so that it doesnt turnoff when i pullout the battery. this i have been facing for quite long. cudnt fix it.
I tried exactly what you said.. but im stuck in the fastboot now.. im not able to flash anything using adb in fastboot.
im getting errors in fastboot.
when i typed 'fastboot flash system system.img"
it gives an error like "error: cannot load 'system.img' : unknown error"
did "fastboot erase" and it worked.
but flashing is not happening.
please help me out
---------- Post added at 08:22 PM ---------- Previous post was at 08:02 PM ----------
i somehow managed to flash all those things what u said in your post...
but still when rebooted after flashing via fastboot, the same 7 vibrations happening.
My phone doesnt boot..
i havent done the battery trick as you said. Im not able to do it. That video doesnt have any instruction and no audio too.
any instruction on how to do it will be helpful.
Click to expand...
Click to collapse
After doing all the stuffs, and after fastboot reboot.. The phone on the same state.. Brick state with 7 vibrate + X sign. Why is that so?

My Vivid got stuck on JoupunutBear screen!Help please!

Hi there,
I've been using my Vivid since it came out and been surfing rom to rom but haven't tried to get s-off.
I tried it today but unfortunately, there was an accident. While controlbear was running ( I haven't done the wire trick), my pc crashed and had to reboot. After that, my phone got stuck on JoupunutBear screen and I can't get it boot up again.
I tried to push recovery but cmd windows keep saying writing recovery and did not finish. I tried to oem lock, it said successfully locked but the second line said Failed (too many links). I put the stock rom as PH39IGM.zip on the sd card, the bootloader checked it twice but did not ask me to apply it.
That's every ways I know to save my phone's life but it did not help at all.
I think something can still be done while the bootloader is still accessible, right?
Please help me out! It's the first phone I bought my self!
Any help or idea would be appreciated!
Thank you all!
Relock the bootloader and run stock ruu file may just do the trick
Bigtjmc said:
Relock the bootloader and run stock ruu file may just do the trick
Click to expand...
Click to collapse
I did that first but it did not help. It cant boot in to android so cant run ruu
I followed trouble shooting guide on the site and tried dozens of times till accidentally got in to recovery, flashed a rom but it still stucking there
so exhausted of trying...
So you can't get into hboot ?
Bigtjmc said:
So you can't get into hboot ?
Click to expand...
Click to collapse
I can get in bootloader and recovery
I flashed a rom but it just wont boot up
and I cant push boot.img through fastboot usb
but somehow I got S-Off already
Ok just relock the boot loader via htcdev.com and in this tread download the ruu from here then open the program follow the prompts , once you boot in hboot select fastboot then plug in the USB cord the phone should then say fastboot USB then all you got to do is run the ruu program on ur pc
---------- Post added at 05:29 PM ---------- Previous post was at 05:27 PM ----------
http://forum.xda-developers.com/showthread.php?t=1803750&page=2
Post 14 just click the link and it should down load
Bigtjmc said:
Ok just relock the boot loader via htcdev.com and in this tread download the ruu from here then open the program follow the prompts , once you boot in hboot select fastboot then plug in the USB cord the phone should then say fastboot USB then all you got to do is run the ruu program on ur pc
---------- Post added at 05:29 PM ---------- Previous post was at 05:27 PM ----------
http://forum.xda-developers.com/showthread.php?t=1803750&page=2
Post 14 just click the link and it should down load
Click to expand...
Click to collapse
thanks for your helps!
I saved my phone's life in another way. It booted up right after I finished reading your post!
Lucky me!
some times i cant get in hboot unless i pull the battery then hold the -vol button then power button.
might help also
---------- Post added at 05:35 PM ---------- Previous post was at 05:34 PM ----------
good job .

Stuck in bootloop since OTA due to root

I am stuck in a bootloop right now due to being an idiot and performing the OTA after being rooted. Now I cannot hard reset via the power/vol down or the menu of the phone. I am not familiar with adb or command prompts, etc and I don't know what fastbooting means? I have downloaded the adb/fastboot rar and when i click either all they do is zoom through a list of words and close? what do i have to do to get my phone working again?!
I feel your pain!
I am having the same issues! I get about 30 seconds to quickly flick to something before it powers off again. I found that I can keep it powered off and I can get to a boot menu but all of the options cause the screen to go blank then it restarts again. PLEASE help! my phone is my lifeline and it is required for my work!
NovaSS369 said:
I am stuck in a bootloop right now due to being an idiot and performing the OTA after being rooted. Now I cannot hard reset via the power/vol down or the menu of the phone. I am not familiar with adb or command prompts, etc and I don't know what fastbooting means? I have downloaded the adb/fastboot rar and when i click either all they do is zoom through a list of words and close? what do i have to do to get my phone working again?!
Click to expand...
Click to collapse
You both need to use RSD to flash back to stock firmware.
http://forum.xda-developers.com/showthread.php?t=2446515
You DONT have to rsd !!!! Just fastboot erase user cache
---------- Post added at 03:59 AM ---------- Previous post was at 03:55 AM ----------
http://www.droidrzr.com/index.php/t...et-up-adb-and-fastboot-for-your-windows-7-pc/
If you don't know fastboot/adb here is a good guide how to set it up.
got it to do the fastboot, every time i install the update though i get the same viscious cycle :/

[HELP] MemoPad 7 (176CX) stuck after OTA

Hello,
A fellow colleauge of mine had a MemoPad 7 (176CX) which received an OTA update last week. After the installation the tablet restarted and then a dead droid appeared on the screen with an error message "no command found" then the device restarts automatically and everything starts again (dead droid - no command - reboot - dead droid...). So, it's in a boot loop. (As far as I know the device was rooted and he made a mistake to no un-root before the OTA update but it's irrelevant now)
As he asked for help I checked the XDA forums and found that my idea about reinstalling the factory default firmware should solve the problem. But I'm a little bit afraid of the continous boot loop. How will be able to reflash the firmware when the device keeps rebooting?
Any advice will be helpful.
Thanks in advance.
I know what to do, don't worry. Get into recovery (it's annoying to get into recovery, you need to spam all buttons randomly while the no command screen is up), reboot to bootloader, and boot into a Temporary CWM using a PC.
Reply with questions.
---------- Post added at 01:19 PM ---------- Previous post was at 01:19 PM ----------
I know what to do, don't worry. Get into recovery (it's annoying to get into recovery, you need to spam all buttons randomly while the no command screen is up), reboot to bootloader, and boot into a Temporary CWM using a PC.
Reply with questions.
---------- Post added at 01:22 PM ---------- Previous post was at 01:19 PM ----------
Sorry for the double post.
---------- Post added at 01:22 PM ---------- Previous post was at 01:22 PM ----------
Sorry for the double post.
Hello,
Thanks for the reply. Unfortunatelly the issue seems to be a little bit more complicated.
So, things I checked:
- boot into droidboot with Vol+ + Power - works well, able to boot into droidboot. But see this strange notice in the bottom:
FASTBOOT INIT....
e:Failed to mount device '/dev/block/sda1' as installer partition using fs_type
ition using fs_type 'vfat'
continue fastboot process
E:installer device ignored
FASTBOOT CMD WAITING...
E:installer device ignored
E:No valid installer medium found
Could not open /sys/devices/virtual/backlight
Now, I can select Reboot Droidboot - no luck
Reboot - no luck
Recovery - reboot into bootloop
Power off - yeah, it works and turns of the device.
If I try to boot into Fastboot with Vol - + Powoer receive the dead droid with the No command message.
Any idea where can I go forward?
Nandr0idC0nsumer said:
I know what to do, don't worry. Get into recovery (it's annoying to get into recovery, you need to spam all buttons randomly while the no command screen is up), reboot to bootloader, and boot into a Temporary CWM using a PC.
Reply with questions.
---------- Post added at 01:19 PM ---------- Previous post was at 01:19 PM ----------
I know what to do, don't worry. Get into recovery (it's annoying to get into recovery, you need to spam all buttons randomly while the no command screen is up), reboot to bootloader, and boot into a Temporary CWM using a PC.
Reply with questions.
---------- Post added at 01:22 PM ---------- Previous post was at 01:19 PM ----------
Sorry for the double post.
---------- Post added at 01:22 PM ---------- Previous post was at 01:22 PM ----------
Sorry for the double post.
Click to expand...
Click to collapse
waces said:
Hello,
Thanks for the reply. Unfortunatelly the issue seems to be a little bit more complicated.
So, things I checked:
- boot into droidboot with Vol+ + Power - works well, able to boot into droidboot. But see this strange notice in the bottom:
FASTBOOT INIT....
e:Failed to mount device '/dev/block/sda1' as installer partition using fs_type
ition using fs_type 'vfat'
continue fastboot process
E:installer device ignored
FASTBOOT CMD WAITING...
E:installer device ignored
E:No valid installer medium found
Could not open /sys/devices/virtual/backlight
Now, I can select Reboot Droidboot - no luck
Reboot - no luck
Recovery - reboot into bootloop
Power off - yeah, it works and turns of the device.
If I try to boot into Fastboot with Vol - + Powoer receive the dead droid with the No command message.
Any idea where can I go forward?
Click to expand...
Click to collapse
X2 With the OTA missing partition. Seemed like a straight forward update but completely screwed up my tablet. SOL for the moment. I imagine this post will become popular very quick.
Try the following:
Boot into DROIDBOOT
Download & Install Android Studio
Go into a cmd and type "fastboot devices"
If it shows a device, than:
Use a temp CWM session to flash 182.
Hello,
Nope, in Droidboot the PC cannot see and connect any device.
fastboot devices - return with empty line
fastboot getvar - return with <waiting for device>
minor correcftion. was able to access the device with fastboot devices and it shows the connected device as well. i followed the steps described here : http://forum.xda-developers.com/android/help/instructions-reviving-me170c-me170cx-t3017466 but no luck. what did i missed?
waces said:
minor correcftion. was able to access the device with fastboot devices and it shows the connected device as well. i followed the steps described here : http://forum.xda-developers.com/android/help/instructions-reviving-me170c-me170cx-t3017466 but no luck. what did i missed?
Click to expand...
Click to collapse
Fastboot? AWESOME! You're covered, Jimmy. (If you didn't have access to fastboot, you would be six callers ahead of us...)
Download this temp CWM:
https://www.androidfilehost.com/?fid=23991606952604606
open the batch file (with droidboot open on the tablet, and tethered to the pc), and type "ACCEPT". Now, type "T4", and click enter, and a temporary CWM session should open.
Now, (you'll need a external SD card), flash this file:
http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ME176C-WW-3_2_23_182.zip
And you should be on KitKat... and take OTAs from there to get to lollipop. Use the same temp CWM and flash SuperSU to get root.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
---------- Post added at 01:50 PM ---------- Previous post was at 01:17 PM ----------
Just wondering... did you end up fixing the device? You don't seem to be very active on this fourm.
Nandr0idC0nsumer said:
Fastboot? AWESOME! You're covered, Jimmy. (If you didn't have access to fastboot, you would be six callers ahead of us...)
Download this temp CWM:
open the batch file (with droidboot open on the tablet, and tethered to the pc), and type "ACCEPT". Now, type "T4", and click enter, and a temporary CWM session should open.
Now, (you'll need a external SD card), flash this file:
And you should be on KitKat... and take OTAs from there to get to lollipop. Use the same temp CWM and flash SuperSU to get root.
Click to expand...
Click to collapse
Wondering if you could help me for a sec... I followed what you have here and all works fine but the sd card won't mount, I've formatted with both file systems but no. I'm very new but learning, what did I miss?
jakeco2u said:
Wondering if you could help me for a sec... I followed what you have here and all works fine but the sd card won't mount, I've formatted with both file systems but no. I'm very new but learning, what did I miss?
Click to expand...
Click to collapse
Tell me the exact steps you took.
Did you take the OTAs to Lollipop?
Nandr0idC0nsumer said:
Tell me the exact steps you took.
Did you take the OTAs to Lollipop?
Click to expand...
Click to collapse
Yes, was rooted, OTA to Lollipop and tablet stuck in bootloop. I followed your post and was not able to install your link but had success with WW_V12.10.1.17. The tablet stated it had been installed so I went back and reboot but its still stuck in the bootloop. Hope that makes sense.
Like I said, I'm new to working on these so be nice. Should I install firmware and source code from the Asus website?
jakeco2u said:
Yes, was rooted, OTA to Lollipop and tablet stuck in bootloop. I followed your post and was not able to install your link but had success with WW_V12.10.1.17. The tablet stated it had been installed so I went back and reboot but its still stuck in the bootloop. Hope that makes sense.
Like I said, I'm new to working on these so be nice. Should I install firmware and source code from the Asus website?
Click to expand...
Click to collapse
Did you factory reset after installing the WW_V12.10.1.17 ROM?
Nandr0idC0nsumer said:
Did you factory reset after installing the WW_V12.10.1.17 ROM?
Click to expand...
Click to collapse
I did, back to bootloop.
jakeco2u said:
I did, back to bootloop.
Click to expand...
Click to collapse
Did the Lollipop OTA finish? (As in, did you see all the BIOS updating text?)
Nandr0idC0nsumer said:
Did the Lollipop OTA finish? (As in, did you see all the BIOS updating text?)
Click to expand...
Click to collapse
I'm not sure if the bios updated (I assume we are talking about the first OTA round before the problem). It had finished the download, the droid was shown for a bit, and when I came back after about 1/2 hr. to check on it the 'Asus powered by Android' screen kept cycling about every minute. I didn't see bios updating text. BTW thank for the help...
And as the OP stated in fastboot i get:
E:installer device ignored
continue the fastboot process
E:failed to mount device '/dev/block/sda1' as installer partition using fs_type
ition using fs_type 'vfat'
FASTBOOT CMD WAITING...
E:installer device ignored
E:No valid installer medium found
Could not open /sys/devices/virtual/backlight
jakeco2u said:
I'm not sure if the bios updated (I assume we are talking about the first OTA round before the problem). It had finished the download, the droid was shown for a bit, and when I came back after about 1/2 hr. to check on it the 'Asus powered by Android' screen kept cycling about every minute. I didn't see bios updating text. BTW thank for the help...
And as the OP stated in fastboot i get:
E:installer device ignored
continue the fastboot process
E:failed to mount device '/dev/block/sda1' as installer partition using fs_type
ition using fs_type 'vfat'
FASTBOOT CMD WAITING...
E:installer device ignored
E:No valid installer medium found
Could not open /sys/devices/virtual/backlight
Click to expand...
Click to collapse
Try downloading each ROM from the OP, and flashing them in order.
Nandr0idC0nsumer said:
Try downloading each ROM from the OP, and flashing them in order.
Click to expand...
Click to collapse
Sorry, which ROMs? Are we talking about the firmware and kernels from the Asus website? I'm not seeing any ROMs in this post except the one you posted and the Asus one. And again, thanks for taking the time...
jakeco2u said:
Sorry, which ROMs? Are we talking about the firmware and kernels from the Asus website? I'm not seeing any ROMs in this post except the one you posted and the Asus one. And again, thanks for taking the time...
Click to expand...
Click to collapse
Sorry, didn't make what to download clear enough.
ME176C/X K013 ROMS AND UPDATES:
WW .182 ROM
http://dlcdnet.asus.com/pub/ASUS/Eee...3_2_23_182.zip
WW OTA 191
http://fota.asus.com/delta_package/e...104/update.zip
https://drive.google.com/file/d/0B5G...ew?usp=sharing
http://www26.zippyshare.com/v/49210353/file.html
WW OTA 198
http://www21.zippyshare.com/v/f1NwNFH5/file.html
WW OTA 199
http://www.mediafire.com/download/ec...c8j/update.zip
WW OTA 201
http://www48.zippyshare.com/v/PtRl8YI9/file.html
WW Lollipop release
http://www.mediafire.com/download/2v...1/lollipop.zip
download each one of those (sorry, lots of downloads lol) and flash them each in order using a temp CWM. then do a factory reset and reboot.
EDIT: some links are down. I'm assuming you already have the 182 ROM.
Flash the 182 ROM, and then flash all the updates you can download in order.
Nandr0idC0nsumer said:
Sorry, didn't make what to download clear enough.
ME176C/X K013 ROMS AND UPDATES:
WW .182 ROM
http://dlcdnet.asus.com/pub/ASUS/Eee...3_2_23_182.zip
WW OTA 191
http://fota.asus.com/delta_package/e...104/update.zip
https://drive.google.com/file/d/0B5G...ew?usp=sharing
http://www26.zippyshare.com/v/49210353/file.html
WW OTA 198
http://www21.zippyshare.com/v/f1NwNFH5/file.html
WW OTA 199
http://www.mediafire.com/download/ec...c8j/update.zip
WW OTA 201
http://www48.zippyshare.com/v/PtRl8YI9/file.html
WW Lollipop release
http://www.mediafire.com/download/2v...1/lollipop.zip
download each one of those (sorry, lots of downloads lol) and flash them each in order using a temp CWM. then do a factory reset and reboot.
Click to expand...
Click to collapse
OK, I tried to download these links most are dead and the three that did download came up as errors when attempting to flash them.
I'm going to try and explain the best I can with pictures as I can only assume I'm doing something wrong.
This is what I get when I go into fastboot, or droidboot or whatever.
OK, I install update from Asus website(as its the only file that hasn't caused an error.
After the install...
Wipe data...
Reboot... I don't know why it asks for root on reboot???
Then starts bootloop...
Any thoughts? Or should I just toss it.. It seems there has to be a way but it's beyond my skill set. Thanks again for the help.

Deleted OS?

The other day I was using my phone and it started to die on me so I plugged it in to charge. I guess it was too low power, so when I plugged it in, it powered down and started charging via phone off. Later I come back to turn it on and it just gets stuck in bootloop. I haveTWRP installed so I cleared the dalvik cache and regular cache. That didn't work. So the next time I just did a factory restore, well after the restore I now have no files on my phone. No OS nothing.
When I plug the phone in via USB the computer chimes and lets me know something was plugged in but I don't get any other messages. If I plug my phone in while in recovery it shows the device with zero folders.
I am sure I can fix it from here, but while using WUGS Root Tool Kit my computer keeps telling me that no "FastBoot Devices" found. How do I fix that?
I would like to just flash an image if possible if someone can walk me through the process or any help would be great.
bannworthrulz said:
The other day I was using my phone and it started to die on me so I plugged it in to charge. I guess it was too low power, so when I plugged it in, it powered down and started charging via phone off. Later I come back to turn it on and it just gets stuck in bootloop. I haveTWRP installed so I cleared the dalvik cache and regular cache. That didn't work. So the next time I just did a factory restore, well after the restore I now have no files on my phone. No OS nothing.
When I plug the phone in via USB the computer chimes and lets me know something was plugged in but I don't get any other messages. If I plug my phone in while in recovery it shows the device with zero folders.
I am sure I can fix it from here, but while using WUGS Root Tool Kit my computer keeps telling me that no "FastBoot Devices" found. How do I fix that?
I would like to just flash an image if possible if someone can walk me through the process or any help would be great.
Click to expand...
Click to collapse
you wiped system, which wipes your rom off your phone. its a VERY easy fix.. just move whatever rom/gapps/supersu to your phone via twrp or adb, then flash it via twrp.
---------- Post added at 12:38 PM ---------- Previous post was at 12:37 PM ----------
btw.. dont use toolkits. LEARN how to things yourself, its much easier.
Hello
simms22 said:
you wiped system, which wipes your rom off your phone. its a VERY easy fix.. just move whatever rom/gapps/supersu to your phone via twrp or adb, then flash it via twrp.
---------- Post added at 12:38 PM ---------- Previous post was at 12:37 PM ----------
btw.. dont use toolkits. LEARN how to things yourself, its much easier.
Click to expand...
Click to collapse
Could you point me in the direction to the rom/gapps/superu?
bannworthrulz said:
Could you point me in the direction to the rom/gapps/superu?
Click to expand...
Click to collapse
which rom? there are many. even a twrp flashable stock rom.
bannworthrulz said:
Could you point me in the direction to the rom/gapps/superu?
Click to expand...
Click to collapse
Also I installed a stock version of android off the factory images page and copied it over to my phone but TWRP cannot find the zip file?
simms22 said:
which rom? there are many. even a twrp flashable stock rom.
Click to expand...
Click to collapse
Just any stock ROM, I downloaded one from https://developers.google.com/android/nexus/images#fugu but it doesn't show up in TWRP.
bannworthrulz said:
Also I installed a stock version of android off the factory images page and copied it over to my phone but TWRP cannot find the zip file?
Click to expand...
Click to collapse
to flash a factory image, you need to flaah it while in the bootloader, using fastboot. its not a zip.
---------- Post added at 01:15 PM ---------- Previous post was at 01:12 PM ----------
a stock-like rom http://forum.xda-developers.com/nexus-6/development/rom-rooted-deoxeded-fast-stable-t3252922
simms22 said:
to flash a factory image, you need to flaah it while in the bootloader, using fastboot. its not a zip.
Click to expand...
Click to collapse
Honestly man, you are talking to someone who doesn't understand a lot about these things. I need detailed instruction on how to do this. I now don't have twrp installed. I tried to install CM13 and now its stuck in cyanogen recovery mode. This really sucks and need help on how to fix it. Also while in bootloader mode. It says FASTBOOT DEVICE NOT FOUND if it were found I would not be having this issue. I would have a stock rom installed and be on my way. Since it isn't able to find a FASTBOOT DEVICE that is why I am in this current situation.
NVM I figured it out. Had to install adb-setup-1.4.2.exe and now my phone is fixed and up and running.
bannworthrulz said:
Honestly man, you are talking to someone who doesn't understand a lot about these things. I need detailed instruction on how to do this. I now don't have twrp installed. I tried to install CM13 and now its stuck in cyanogen recovery mode. This really sucks and need help on how to fix it. Also while in bootloader mode. It says FASTBOOT DEVICE NOT FOUND if it were found I would not be having this issue. I would have a stock rom installed and be on my way. Since it isn't able to find a FASTBOOT DEVICE that is why I am in this current situation.
NVM I figured it out. Had to install adb-setup-1.4.2.exe and now my phone is fixed and up and running.
Click to expand...
Click to collapse
yup, installing it first helps out, a lot :silly:
bannworthrulz said:
... WUGS Root Tool Kit my computer keeps telling me that no "FastBoot Devices" found. How do I fix that?
Click to expand...
Click to collapse
Boot twrp recovery first....

Categories

Resources