Related
my verizon xperia is not recognized by either pc companion or seus. I am trying to do a hard reset due to the fact the lockscreen doesnt work. I have read that I can press and hold the back and search keys on front while powering on to factory reset the phone, however that does not seem to be the case. Can anyone give me some suggestions if the two button factory reset does work and that maybe I am just doing it wrong. And any suggestions as to how to get my phone to connect with seus so I can reset if teh 2 button trick is indeed not an option. Thank you to all in advance.
Doesnt anyone have an idea? I follow seus instructions. Power off wait 30 seconds, then plug in the usb cord to the pc, then press and hold the back button then inserting the usb cable into the phone... and then I wait for it to connect which it doesnt.
have you tried removing the battery wait a bit and put it back and then try again. I had something similar happen when I first got mine.
yes.... I waited beyond the 30 seconds it suggests. I eve waited about 2 hours once. Still nothing......I really want to get this device working.....it does power up. Everything seems like its supposed to work but it isn't. Thank you for helping me... I really really appreciate it.
hey, if youre comfortable, we can unlock the bootloader on it. if we do that, then you can just use fastboot and the files you can get off of my State of Development thread to return you back to stock. You could also root it. If that interests you, send me a pm with your ESN and Ill get you an unlock code.
Or do you still wanna try to figure out the **** fest that is SEUS?
I would love to unlock the bootloader. I have always had motorola android phones so even though i have never unlocked the bootloader I would love to.
Where would I find the ESN #? I am not able to get past the lock screen....so all I can do it make emergency calls
I have PM'd you my phones info. Thank you for your assistance
What is preventing you from passing the lock screen exactly? Programming?
the phone says that the pattern lock attempts has been exceeded... and the only way to unlock is to enter either a gmail info or answer the question. Neither of which I know.
Ahh! phew i thought it was more serious than that. Were you able to have the phone activated on your Verizon account okay? The esn wasnt blacklisted or anything?
And the funny thing is, even if you HAD got seus working, it would not have fixed that problem. SUES doesnt wipe the device as far as I know.
the *#06# in the emergency dialer doesnt show anything?
also the MEID is under the battery.
I have not activated the phone as I cant really use it in its current state. I did check with Verizon and the phone can be activated no problems.
I do have the MEID #, is it safe to list it here?
Also, the phone does not take the #* code, says its not an emergency number
K, i have successfully unlocked my bootloader on my phone..... I am trying to make sense of what to do next
YAY!!!!!. I unplugged and rebooted the phone after unlocking the bootloader and now my phone is back... I can sign into google now
you should use this command and reflash the stock system
fastboot flash system system.sin -w
this will erase usersettings and reinstall the stock rom.
make sure you have the rom downloaded.
edit- Never mind.
jgregoryj1 said:
YAY!!!!!. I unplugged and rebooted the phone after unlocking the bootloader and now my phone is back... I can sign into google now
Click to expand...
Click to collapse
Thats great! totally forgot that actually unlocking the bootloader performs a factory reset. So awesome! Go get you some root!
now that I have it restored, the screens touch sensitivity is all over, it keeps thinking I am trying to load up voice commands. I would like to flash a rooted ROM, and from what I have read on kernals for the r800x theres nothing worth flashing just yet. Can anyone point me in the right direction on how to flash a rooted stock rom?
Also, I am still not able to enter Flash mode with the whole back button while inserting usb cable. the light is still blue.... any suggestions?
You shouls be holding the search key.
sent from the original unlocked R800X.
i will try the search button instead. Also I flashed a kernal and now the phone is super slow. How do I flash the stock ROM and stock kernal. I am doing some reading but I am still lost. seems like I get routed to xperia arc pages...... can anyone give me some guidance. sorry to be a pain, but I am excited to learn
jgregoryj1 said:
i will try the search button instead. Also I flashed a kernal and now the phone is super slow. How do I flash the stock ROM and stock kernal. I am doing some reading but I am still lost. seems like I get routed to xperia arc pages...... can anyone give me some guidance. sorry to be a pain, but I am excited to learn
Click to expand...
Click to collapse
Hey, everything you need to know is in the many pages (and the initial post which is constantly updated) on my State of Development thread. Read through there and you will see that everyone else is also having problems with the kernels and roms making the phone unresponsively slow. The first post also has links for stock files that you might need.
Basically if you get your phone into fastboot mode (turn off, hold search key, plug in USB line, solid blue light turns on) you can do two commands to get you back to stock, and then follow the rooting instructions that I have on the R800x Rooting thread. Its linked in the state of development thread. Second item, i believe, below the link to Bin4rys.
The two commands would be "fastboot flash system system.sin" and "fastboot flash boot kernel.sin". the first command might not be necessary even, just the kernel one might fix you.
OK,
So a friend of mine asked me to help him fix his Nexus 7 2013 FLO (WiFi only).
According to him he hasn't even unlocked the bootloader (and the info displayed while in fastboot mode confirms this). Apparently what happened, a few months ago, he downloaded an OFFICIAL KitKat OTA, clicked OK to upgrade, and since then, the tablet will not get past the screen that says Google. I can get it into fastboot mode but cannot flash anything, and when I attempted to use The Nexus Root Toolkit by WugFresh to unlock the bootloader at the very least, I can get it to display the screen that says "please use the arrow key to navigate Yes or No. Unlocking your bootloader allows you to load a custom OS, but may void your warranty, etc. etc. etc."
I tried using CMD to erase the cache and userdata and after giving it upwards of 20 minutes, during which the window (in CMD) simply said "erasing cache" and never actually made any progress whatsoever...
Any idea what (if anything) can be done?
Sound off in the comments!
Thanks a million!
Stephen Spigelman
I can't help... but am in the same boat as of last night with the 5.0 update.
Were you able to unlock the bootloader? You did say that you were able to get to the screen to unlock it. If not, i dont think much of anything can be done.
Bricked
Virgin N7 2013... No hacking... Bootloader locked... started acting weird and I attempted a system restore. It now gets stuck at the Google screen. Fastboot gets stuck at erasing userdata. I have tried multiple USB cables on Win7, OSX, and Ubuntu. Help!!!
im wondering how this happens?, I already unlocked my bootloader just cause of this.. maybe the chip just dies?
When my 2013 was stuck at the Google screen, I RMAed and they had to replace the motherboard. Unfortunately, I think this is a hardware issue.
ariesgodofwar said:
When my 2013 was stuck at the Google screen, I RMAed and they had to replace the motherboard. Unfortunately, I think this is a hardware issue.
Click to expand...
Click to collapse
Too many of us with the exact same problem after trying to to flash Lollipop. Cant believe we re all having hardware problems at the same time.
tigerdim said:
Too many of us with the exact same problem after trying to to flash Lollipop. Cant believe we re all having hardware problems at the same time.
Click to expand...
Click to collapse
Mine did not occur after flashing any firmware, but the symptom was the same in that I could get into the bootloader, attempt to flash new system images, appear as if all would be well, and then on reboot would stick at the Google screen. Not sure if folks are seeing the same thing here, but when I tried to get into Recovery from the Bootloader menu, it would reboot as if going there, but still never make it past the Google screen. It happened within 18 hours of unboxing a remanufactured N7 G2. Asus advised on the packing slip that is was a LED (Indicator) Error (whatever that is), and they they subsequently had to replace the board to fix it.
I hope it is a software issue, but not sure to tell you how to go about correcting it if you cannot flash new images via ADB or the bootloader and get it to boot successfully.
When i boot to recovery i get the TWRP startup screen but stays stuck.
Bump
bump.. any ideas?
i have the same :/
kobi_shalom said:
i have the same :/
Click to expand...
Click to collapse
Its driving me nuts.
I have found though that if I try a "Erase Boot" or similar and pull the cable after a second or so I do get a "OK" instead of being stuck with "Erasing boot..." Seems to work for Boot, Cache etc..
The problem is that when I try OEM Unlock it needs to perform 5 different erases, so pulling the cable wont work for this. I just stay stuck on "Erasing userdata...r..."
tigerdim said:
Its driving me nuts.
I have found though that if I try a "Erase Boot" or similar and pull the cable after a second or so I do get a "OK" instead of being stuck with "Erasing boot..." Seems to work for Boot, Cache etc..
The problem is that when I try OEM Unlock it needs to perform 5 different erases, so pulling the cable wont work for this. I just stay stuck on "Erasing userdata...r..."
Click to expand...
Click to collapse
So you success?
NO success because I cannot unlock the bootloader.
I have been looking for the past couple days and have not found an obvious answer for my issue. So hopefully this isn't an answered repeat but if so pleas link ^-^.
I received my HTC One M8 dev edition the other day and was hoping to get it unlocked with probably cynogenmod installed while it was fresh but I am having issues with the bootloader unlock. So far I am able to get my unlock code from HTC and when I flash it the command window shows success but I never receive the prompt on the phone to commit to the unlock. I found out the hard way that it didn't auto accept since I soft bricked installing twrp and no longer have access to the recovery even after reflashing a stock one (but at least I have phone access again).
Has anyone had and found a solution to this problem? I was really looking forward to having a nice custom rom but seem to be stuck with the factory dev edition which is still loads better than the carrier edition. I will consider a non HTC bootloader unlock if I have to but the dev unlock seems nice and easy.
Hopefully some one can just tell me I did something retarded and all will be good ^-^.
Also I have tried Squabbi's toolkit but it ends up the same way, but less command prompts.
Thanks
Dlome said:
I have been looking for the past couple days and have not found an obvious answer for my issue. So hopefully this isn't an answered repeat but if so pleas link ^-^.
I received my HTC One M8 dev edition the other day and was hoping to get it unlocked with probably cynogenmod installed while it was fresh but I am having issues with the bootloader unlock. So far I am able to get my unlock code from HTC and when I flash it the command window shows success but I never receive the prompt on the phone to commit to the unlock. I found out the hard way that it didn't auto accept since I soft bricked installing twrp and no longer have access to the recovery even after reflashing a stock one (but at least I have phone access again).
Has anyone had and found a solution to this problem? I was really looking forward to having a nice custom rom but seem to be stuck with the factory dev edition which is still loads better than the carrier edition. I will consider a non HTC bootloader unlock if I have to but the dev unlock seems nice and easy.
Hopefully some one can just tell me I did something retarded and all will be good ^-^.
Also I have tried Squabbi's toolkit but it ends up the same way, but less command prompts.
Thanks
Click to expand...
Click to collapse
You should be able to enter recovery by going to fastboot and using the volume keys to navigate to the recovery option, and picking it by pressing the power button.
To enter fastboot with your phone on, hold down the power button and vol. up until your phone turns off (20 seconds or so). AS SOON AS IT TURNS OFF, switch to power button and vol. down. Then go to the recovery option, and you are in.
And while you are in fastboot, you might as well try running the unlock key again. If it doesn't work, go back to HTCDev for another. I'm not sure how that works, but I think you could get another code if you can't get this one to work.
xunholyx said:
You should be able to enter recovery by going to fastboot and using the volume keys to navigate to the recovery option, and picking it by pressing the power button.
To enter fastboot with your phone on, hold down the power button and vol. up until your phone turns off (20 seconds or so). AS SOON AS IT TURNS OFF, switch to power button and vol. down. Then go to the recovery option, and you are in.
And while you are in fastboot, you might as well try running the unlock key again. If it doesn't work, go back to HTCDev for another. I'm not sure how that works, but I think you could get another code if you can't get this one to work.
Click to expand...
Click to collapse
Currently when I try to enter recovery it enters a boot loop and freezes on the HTC screen. From what I read this is from trying to install a custom recovery with a locked bootloader. That part I can live with for now since it does not seem to be an issue, just the outcome of my mistake. My biggest issues seems to be the bootloader unlock not working. unless the two are related which could be as I am fairly new to this process.
Dlome said:
Currently when I try to enter recovery it enters a boot loop and freezes on the HTC screen. From what I read this is from trying to install a custom recovery with a locked bootloader. That part I can live with for now since it does not seem to be an issue, just the outcome of my mistake. My biggest issues seems to be the bootloader unlock not working. unless the two are related which could be as I am fairly new to this process.
Click to expand...
Click to collapse
So, have you tried the code again? And/or have you gone back to the HTCDev site for a new unlock code?
I have tried two unlock tokens so far and tried both of them several times. It's almost like I'm submitting something wrong and don't know it. When I submit the token I am including both the start and end brackets which is what it appears to be asking for and not just the string between them.
Dlome said:
I have tried two unlock tokens so far and tried both of them several times. It's almost like I'm submitting something wrong and don't know it. When I submit the token I am including both the start and end brackets which is what it appears to be asking for and not just the string between them.
Click to expand...
Click to collapse
Are you copying and pasting the very first part of the code?
The part that looks like:
"(bootloader) < please cut following message >
(bootloader)" ?
IMMEDIATELY after that is what you copy and paste.
The copy should start when it says "<<<< identifier token start >>>>"
I am only copying the <<<< identifier token start >>>> and <<<< identifier token end >>>> along with the string between and leaving out the bootloader tag that is on each line.
I guess one question I should be asking is are there any settings on the phone that I need to set? I have developer options activated, usb debugging on, and the fastboot option unchecked in the power settings. Other than that the phone is stock settings. I remember my s4 needed to be in a specific usb connection mode but since they are completely different phones im not sure if that will apply here.
Dlome said:
I guess one question I should be asking is are there any settings on the phone that I need to set? I have developer options activated, usb debugging on, and the fastboot option unchecked in the power settings. Other than that the phone is stock settings. I remember my s4 needed to be in a specific usb connection mode but since they are completely different phones im not sure if that will apply here.
Click to expand...
Click to collapse
You seem to be doing everything right. I'm stumped. Hopefully someone else comes along with a solution. @redpoint73?
That's what I was afraid of haha. I don't know why but while I am no expert in this area I do not feel I'm ignorant either yet I always seem to have problems even when I follow the steps correctly >.<
I do appreciate the troubleshooting greatly thank you. I will keep trying things and see what I can find and if I figure it out you bet I will add it here because I can't be the only one getting stuck haha.
Can you please post the results of
fastboot getvar all
Make sure you remove your IMEI before posting.
xunholyx said:
Hopefully someone else comes along with a solution. @redpoint73?
Click to expand...
Click to collapse
Ummm, yeah . . . in fact I think I do:
Maybe I'm missing something here. But the Dev Edition comes already bootloader unlocked, and therefore should be no reason to do so.
I think the prompt to unlock never comes up on the phone, since its already unlocked.
---------- Post added at 10:20 AM ---------- Previous post was at 10:19 AM ----------
bloodhawk said:
Can you please post the results of
fastboot getvar all
Make sure you remove your IMEI before posting.
Click to expand...
Click to collapse
Yes, this will tell us a lot.
Or boot into bootloader and just see if it says LOCKED, RELOCKED or UNLOCKED.
I bet it says UNLOCKED.
Seems a few are having the same problem as me after trying to flash 5.0
My Nexus will no longer boot past the Google Logo (White one). I can only access the Bootloader. When I try to go to recovery I see the TWRP logo but stays stuck there. I tried flashing a new image a few times but always had the same problem.
I then tried to relock the bootloader and unlock again again to prepare a fresh install. This is where it gets worse. I managed to lock the bootloader but I can no longer unlock. I get to the screen warning that data will be wiped if I choose "YES", but when I do proceed, I stay stuck on "Erasing userdata...". I left it for 5 hours and was still stuck with the same message.
I cant see what else I can do now.
Ive read a few threads saying its a motherboard issue. Seems weird that it appeared when I tried to install Lollipop. Also seems Im not the only one.
this worked for me
I'm sure someone wiser will respond to you later but ..... I've been in a similar situation.
I use Windows 7 64bit and always connect device with usb 2 port (i.e. not usb3).
I was getting stuck on the google logo with an open lock symbol low on the screen - indicating unlocked bootloader. Like you could get into recovery but unable to get any further once there.
Try using Wugfresh's Nexus Root Tool. Look in the development thread. I'd suggest reading his faq's.
Download and install the latest version 1.9.6 (as I recall) - I had problems when using the earlier versions.
Get an stock image downloaded.
Then you should be able to flash the image using the force flash method he mentions in his faq. You set it in the options menu.
Set USB debugging on the device and usb options for storage to ptp rather than mtp - that's what worked for me.
You'll probably see repeated "installing driver" messages and new "open location" popups as you go through it.
(if your bootloader is locked you'll need to unlock it first. - just re-read your original post and I'm hoping that the latest NRT version will get you unlocked OK.)
If you have problems with this at first try going through the driver installation section of the tools.
After that you can use the same tool to root it. That didn't work completely but did allow me to use an OTG flash drive. If you need full root there's a patch you need to flash - Key Pie patch - took me a while to find it but it's somewhere on these forums.
After the problems I had everything went smoothly in the end. Just be prepared to watch it go through various rebootings while the magic is being done.
Apologies if this is a bit haphazard - I tend to try and rush through things and then forget what it was exactly I did!
I have tried NRT but cant do anything as I cant unlock the bootloader. I have tried both Fastboot and NRT, they both block at "erasing userdata".
Just a thought
Sorry to hear that.
Have you tried "Flash Stock + unroot" with the "Soft-bricked/Bootloop" option in NRT? I now recall that's something that helped me get mine recovered. Just a thought.
I recall reading forum posts that suggested I might have motherboard issues - but I didn't believe it was likely to be the case so I kept trying.
Tried all NRT options including force flash.
Problem is none work with the locked bootloader.
Nexus Root Toolkit v1.9.7 out now
Change log:
What’s new in Nexus Root Toolkit 1.9.7: November 16th, 2014
· Included the latest Masterlists to prevent users who never utilized the “Update” in the kit from getting the AutoIt error (for KTU84P Nexus 7 2013). This error was due to the modified boot.img for that build being accidentally removed from the server. Its was then reuploaded and the masterlists were updated, but those users who never updated would still get the error.
· No longer will the “Force Flash” recommendation be made to N4 users, because it seems to cause a bootloop – however factory resting will fix that either way.
IDEM
I spent exactly the same as you, I also lock the bootloader and now I can not do anything, always get "write failure" and when I try to unlock stays forever "erase ..."
There will be some way to revive it?
Cursed Android 5.0!
If the problem is confirmed to be Android 5.0, Google can help solve these problems?
Use the instructions to reflash your bootloader.
http://blog.laptopmag.com/how-to-hard-reset-a-bricked-nexus-7-with-your-pc
Note replace the instructions to download 4.1.1. with the correct version of the ROM you want to flash. Make sure you grab the correct version for your device. Flashing the wrong bootloader can hard brick your NEXUS with no chance of recovery. Also don't relock your bootloader unless you are certain that you will never want to flash again. Unlocking wipes all of your data and you also can't be rooted if you lock it again.
Doesnt work. Cant get passed the first step. After 1 hour its still "erasing boot..."
I flashed 5.0 successfully... You can't send it to Google with warranty? Try on other computer, do it manually using fastboot and don't give up!
As long as you can still boot into Fast Boot..
Your device can be restored..
I suggest using Wugfresh's Nexus toolkit
http://www.wugfresh.com/nrt/
The issues coming from the latest upgrade are common problems when ever we upgrade..
Its always better if you know how, just use the Nexus Toolkit and install the factory image..
Then it will sit at bootup for about 5-7 mins, then restore your apps... Profit
OTAs will always cause issues with some devices..
Zaphodspeaks said:
As long as you can still boot into Fast Boot..
Your device can be restored..
I suggest using Wugfresh's Nexus toolkit
http://www.wugfresh.com/nrt/
The issues coming from the latest upgrade are common problems when ever we upgrade..
Its always better if you know how, just use the Nexus Toolkit and install the factory image..
Then it will sit at bootup for about 5-7 mins, then restore your apps... Profit
OTAs will always cause issues with some devices..
Click to expand...
Click to collapse
Again.. I cant unlock the bootloader whether manually trying with fastboot or running NRT. Flashing a stock image is not possible.
tigerdim said:
Again.. I cant unlock the bootloader whether manually trying with fastboot or running NRT. Flashing a stock image is not possible.
Click to expand...
Click to collapse
If you have not tried the latest version of NRT, you may of fried your locked bootloader..
Regardless, don't give up... Someone will come to the rescue.. Nexus devices are pretty robust..
Try using another cable, make sure you have the correct driver, double check in Device Manager...
Then try again with the lastest NRT.. Mine just updated.. As a rule of thumb its better not to use a USB hub if thats the case.. Try swapping out your cable, make sure you have the Nexus drivers... I had to re install mine..
tigerdim said:
Doesnt work. Cant get passed the first step. After 1 hour its still "erasing boot..."
Click to expand...
Click to collapse
I'm in the exact same spot. Also, I know that I don't have USB debugging enabled, so not sure if I'm blocked out because of that. Very frustrating.
The computer sees the tablet though. If I click on List Devices in NRT Advanced Utilities, it shows my serial # fastboot.
update: I tried the Unlock command and it goes to the Unlock Bootloader screen. I click Yes, but then the device just hangs on that screen (I let it sit for 30-40 minutes). Ideas?
dayz3r0 said:
I'm in the exact same spot. Also, I know that I don't have USB debugging enabled, so not sure if I'm blocked out because of that. Very frustrating.
The computer sees the tablet though. If I click on List Devices in NRT Advanced Utilities, it shows my serial # fastboot.
update: I tried the Unlock command and it goes to the Unlock Bootloader screen. I click Yes, but then the device just hangs on that screen (I let it sit for 30-40 minutes). Ideas?
Click to expand...
Click to collapse
It hangs because its probably stuck at "erasing userdata". If you do it manuall with fastboot oem unlock you will see this in the cmd window.
tigerdim said:
It hangs because its probably stuck at "erasing userdata". If you do it manuall with fastboot oem unlock you will see this in the cmd window.
Click to expand...
Click to collapse
yep, it does
I ve given up . Bought a Nexus 9. Wasted too much time on this.
Having the same problem
My Nexus 7 (2013 32gb wifi) was working just fine on Monday. Had an unusual freeze up when I was reading something on Adobe Acro., but a quick reboot had it running again. I remember a notification about a system update but didn't pay it much mind. Later that evening I went to pick the N7 up and it was stuck on the Google loading screen. Freezes at Google loading screen when I attempt Recovery mode from Fastboot. Fastboot OEM unlock gives me the same stall at 'erasing user data' as mentioned above (left it on for this for 12+ hours yesterday and nothing). I haven't tried a different cable other than stock yet but I have tried multiple ports and two different machines to unlock the bootloader so I can flash the OS. No other functions with NRT (1.9.9) work including forced flash+unroot. I can't even flash the bootloader or erase or format any partitions. Feeling a little SOL here and I think it has something to do with Lollipop update.
N7 was unrooted and used for reading for the past couple weeks, so pretty vanilla use over the recent past.
4 months out of warranty with Asus and they want an est. $100 for RMA. Google tossed me to them after dragging me through the basic stuff I've been doing the past few days. Going to keep messing with it I suppose once exams are over but feel like I'm running out of things to try. If anyone has any suggestions, questions or a solution, posting them here would be much appreciated.
My upgrade from 4.4.4 to 5.0.1 took ages. It was like bouncing the four small balls for perhaps 5 minutes. Just have patience.
I would recommend not to use xposed or titanium backup as I expect those programs mess with /system files and that can break the android upgrade script. Just disable any unwanted bloatware in regular application control. At least all my updates have been successful so far. Yes, I am rooted.
Good luck.
---------- Post added at 12:51 AM ---------- Previous post was at 12:45 AM ----------
For Wugfresh excellent "Nexus Root Toolkit" to work you need to enable usb debugging in developer menu. You enable the developer menu by tapping a lot on your version information.
The usb debugging gets reset on every upgrade.
Mordecai253 said:
My Nexus 7 (2013 32gb wifi) was working just fine on Monday. Had an unusual freeze up when I was reading something on Adobe Acro., but a quick reboot had it running again. I remember a notification about a system update but didn't pay it much mind. Later that evening I went to pick the N7 up and it was stuck on the Google loading screen. Freezes at Google loading screen when I attempt Recovery mode from Fastboot. Fastboot OEM unlock gives me the same stall at 'erasing user data' as mentioned above (left it on for this for 12+ hours yesterday and nothing). I haven't tried a different cable other than stock yet but I have tried multiple ports and two different machines to unlock the bootloader so I can flash the OS. No other functions with NRT (1.9.9) work including forced flash+unroot. I can't even flash the bootloader or erase or format any partitions. Feeling a little SOL here and I think it has something to do with Lollipop update.
N7 was unrooted and used for reading for the past couple weeks, so pretty vanilla use over the recent past.
4 months out of warranty with Asus and they want an est. $100 for RMA. Google tossed me to them after dragging me through the basic stuff I've been doing the past few days. Going to keep messing with it I suppose once exams are over but feel like I'm running out of things to try. If anyone has any suggestions, questions or a solution, posting them here would be much appreciated.
Click to expand...
Click to collapse
They quote you $100 RMA, but once you send it in they will send you an invoice for $200. $165 for the motherboard, $25 labor and $10 return shipping. I fought it and they eventually dropped $10 for the return shipping. Last time I ever deal with Asus.
Sent from my Nexus 9 using Tapatalk
When I boot up my tablet, I get nonstop error messages telling me things have stopped working. I tried getting help from someone else on a different site, and this is what they told me to say: I flashed the GROUPER lollipop ROM onto a FLO. Someone please help me!!! It's a totally clean tablet. no files on it except android.
Go to Google's Nexus firmware page, download the appropriate firmware, follow the instructions: https://developers.google.com/android/nexus/images
Only thing I don't know is whether or not you'll have to repartition the internal flash.
I'm a dummy.
nhizzat said:
Go to Google's Nexus firmware page, download the appropriate firmware, follow the instructions:
Only thing I don't know is whether or not you'll have to repartition the internal flash.
Click to expand...
Click to collapse
i don't understand how to do all that though I'm not good with command prompts... and nexus root tool kit has done me no good. Could you dumb down the instructions for me?
Then it's time for you to learn. The page has step-by-step instructions. There isn't any way too dumb down the instructions.
You have to start somewhere. Now is a good time. If you had learned before, you wouldn't be in this predicament.
So sit down, take a couple deep breaths, then read the instructions a few times. Download the Android SDK and factory image, then get everything set up. Don't panic, it's not nearly as difficult as you're making it out to be. Stop psyching yourself out. Take it step by step. If you get stuck, leave the cmd prompt and post the issue you've run into here.
Might help if you type out the instructions here after you've read them over several times. I'm glad to help but you gotta take ownership of your tablet and put in some effort to learn and educate yourself.
Just try, I'm sure you'll understand it by the end of tonight or the end of the weekend. You don't have to be a master of fastboot and adb, I sure as hell am not. I never recommend the use of toolkits, especially by those with no understanding of fastboot and adb. Once you have a basic understanding of fastboot and adb, go ahead and use any toolkit you want because by then you'll know how to get yourself out of any jams using those 2 tools.
It is almost impossible to hard brick this device, even if you flash the wrong ROM on this device..
Download this utility and it will bring your Nexus back to life....
http://www.wugfresh.com/nrt/
Giving up
nhizzat said:
Then it's time for you to learn. The page has step-by-step instructions. There isn't any way too dumb down the instructions.
You have to start somewhere. Now is a good time. If you had learned before, you wouldn't be in this predicament.
So sit down, take a couple deep breaths, then read the instructions a few times. Download the Android SDK and factory image, then get everything set up. Don't panic, it's not nearly as difficult as you're making it out to be. Stop psyching yourself out. Take it step by step. If you get stuck, leave the cmd prompt and post the issue you've run into here.
Might help if you type out the instructions here after you've read them over several times. I'm glad to help but you gotta take ownership of your tablet and put in some effort to learn and educate yourself.
Just try, I'm sure you'll understand it by the end of tonight or the end of the weekend. You don't have to be a master of fastboot and adb, I sure as hell am not. I never recommend the use of toolkits, especially by those with no understanding of fastboot and adb. Once you have a basic understanding of fastboot and adb, go ahead and use any toolkit you want because by then you'll know how to get yourself out of any jams using those 2 tools.
Click to expand...
Click to collapse
I'm officially giving up. Nothing works. It boots into the OS and then pops up a bunch of error messages. I've tried lollipop, kitkat, cyanogenmod, locked bootloader, unlocked bootloader, and I'm done. GR! Thank you though, for your help.
Boucherwayne78 said:
I'm officially giving up. Nothing works. It boots into the OS and then pops up a bunch of error messages. I've tried lollipop, kitkat, cyanogenmod, locked bootloader, unlocked bootloader, and I'm done. GR! Thank you though, for your help.
Click to expand...
Click to collapse
So that means you will sell it to me for $20?
Boucherwayne78 said:
I'm officially giving up. Nothing works. It boots into the OS and then pops up a bunch of error messages. I've tried lollipop, kitkat, cyanogenmod, locked bootloader, unlocked bootloader, and I'm done. GR! Thank you though, for your help.
Click to expand...
Click to collapse
Nothing works? Just flash the factory image. Flashing Roms in recovery isn't going to help you. Before you give up, just use wugs toolkit to save it. If you give up without even trying the right procedure (fastboot flash factory image) then i recommend you not root again after you fix it. But wugfresh toolkit will fix it for you with a couple clicks.
I tried NRTK
madbat99 said:
Nothing works? Just flash the factory image. Flashing Roms in recovery isn't going to help you. Before you give up, just use wugs toolkit to save it. If you give up without even trying the right procedure (fastboot flash factory image) then i recommend you not root again after you fix it. But wugfresh toolkit will fix it for you with a couple clicks.
Click to expand...
Click to collapse
The toolkit doesn't work. I tried that 9 times, both downloading my own OS to flash, and letting the toolkit download it. Every time it either boot loops it or does the error message spam thing again. That's why I was trying to use SDK... And that didn't work either. And my drivers NEVER INSTALL RIGHT, so it's all just slowly killing me inside...
Make sure fastboots working first. Put the tablet in bootloader mode by shutting it off then holding power and volume down (or up I forget, you want the screen that says start at the top and has device info at the bottom left.)
Connect to computer then go into the platform-tools folder in the SDK folder, hold shift and right click over the window>open command prompt here.
Type fastboot devices and hit enter. Does it show a serial number or does it show nothing? (waiting for device or something like that) If nothing you should uninstall all drivers for the tablet in device manager and install the google usb driver from the sdk manager in the sdk you installed.
Once you see the serial number you're almost done. If your bootloader is locked type fastboot oem unlock
Now from the factory image copy the image-razor.zip, bootloader.img and flash-all.bat to the platform-tools folder.
Double click flash-all.bat
That's it.
I think that it will be beneficial for you to look into using virtual machines (VM's). It allows you to run different operating systems directly from your computer.
The second half to this equation is learning to use Linux (Ubuntu is my choice). Since Android is built from Linux, you don't need special drivers to recognize your devices.
Another option to run Ubuntu is to create a Virtual Hard Drive on your PC, and install Ubuntu onto it (YouTube it, and follow the directions carefully).
Lastly, you can always get a flash drive that is 8gb or greater (16gb or 32gb is recommended), and install Ubuntu onto it was well. It will move little slower than your PC, but your issues will be solved and manageable.
Why am I advocating for Ubuntu? Because it works. PM me if your are interested in learning more, but don't expect me to do all of the work. You need to educate yourself a bit to actually follow my instructions.
____________________________
Please remember to:
Check Q & A forums before asking!
Search forum for similar post before creating!
Hit "thanks" to everyone who may have helped you (it costs nothing)!
Read the OP!!!!
Boucherwayne78 said:
The toolkit doesn't work. I tried that 9 times, both downloading my own OS to flash, and letting the toolkit download it. Every time it either boot loops it or does the error message spam thing again. That's why I was trying to use SDK... And that didn't work either. And my drivers NEVER INSTALL RIGHT, so it's all just slowly killing me inside...
Click to expand...
Click to collapse
First off, let me explain that this device is almost impossible to destroy by flashing the wrong rom. Your over reacting due to inexperience, your Nexus is fine as long as you can boot into Fastboot. When the device is powered down, press the power button and the Volume down key for about 30 seconds, if you can boot into Fastboot, your device is just fine.. Nexus devices are extremely hard to hard brick.. RELAX and realize this is a good time to learn something new, this device is the perfect device to experiment with... You seem to not have the patients and you just need to relax watch a few youtube videos.. No one is going to do it for you.. About 5 years ago I was in the same place you are right now, and I took the time to figure how to fix what ever I did to mess it up.. Its not hard once you realize what your doing. The Toolkit is a swiss army knife of tools that can fix, repair and flash stock roms. Did you unlock the bootloader? Take a breather, give it some time and figure it out like we all did at one time or another, none of us here had our hands held during the learning process with Android devices..
Edit: I'm almost sure you did not unlock your device, to know for sure if your device is unlocked you would see a small padlock that appears to be in the unlocked position at the bottom of your screen while powering on.. If you power your Nexus on, and you DO NOT see a unlocked symbol at the bottom of your screen, you DID NOT unlock your device, thus meaning you have to unlock it to flash it properly.. There are dozens of people in this forum right now that would be more than happy to buy your device cheap and fix it themselves.. If they can do it, you can too..
^Yeah like my last post, those are perfectly fine instructions. If that don't work, stuck at "erasing user data" or something you're ****ed. Most likely.Try a different cord/usb 2.0/computer
Tried a few things. Got any other ideas?
Zaphodspeaks said:
First off, let me explain that this device is almost impossible to destroy by flashing the wrong rom. Your over reacting due to inexperience, your Nexus is fine as long as you can boot into Fastboot. When the device is powered down, press the power button and the Volume down key for about 30 seconds, if you can boot into Fastboot, your device is just fine.. Nexus devices are extremely hard to hard brick.. RELAX and realize this is a good time to learn something new, this device is the perfect device to experiment with... You seem to not have the patients and you just need to relax watch a few youtube videos.. No one is going to do it for you.. About 5 years ago I was in the same place you are right now, and I took the time to figure how to fix what ever I did to mess it up.. Its not hard once you realize what your doing. The Toolkit is a swiss army knife of tools that can fix, repair and flash stock roms. Did you unlock the bootloader? Take a breather, give it some time and figure it out like we all did at one time or another, none of us here had our hands held during the learning process with Android devices..
Edit: I'm almost sure you did not unlock your device, to know for sure if your device is unlocked you would see a small padlock that appears to be in the unlocked position at the bottom of your screen while powering on.. If you power your Nexus on, and you DO NOT see a unlocked symbol at the bottom of your screen, you DID NOT unlock your device, thus meaning you have to unlock it to flash it properly.. There are dozens of people in this forum right now that would be more than happy to buy your device cheap and fix it themselves.. If they can do it, you can too..
Click to expand...
Click to collapse
Thank you for your reply. Do you have any suggestions though for my situation? My bootloader was unlocked. I did try locking it then unlocking it several times though. I've tried two seperate stock ROMs, different usb cables, different usb ports, and it now tells me that fastboot is not working. even a link is greatly appreciated. I think it is a driver problem. My tablet does boot into the OS though. I can use the ui for about 10 seconds, then a notification pops up mid-screen: "unfortunately, the process android.process.acore has stopped." Please, even a link is greatly appreciated. I've tried just about everything to get these drivers working, and to get this tablet working. I will continue to research as well. Wish me luck!
Wug's tool has been invaluable to me in the past. I have gone from KitKat to Lollipop, back and forth, different ROMS, stuck boots, bad flashes. Like Zap says if you can get it to Bootloader then get Wug's tool to connect in fastboot, it will do the rest.
A couple times I have ran into problems where my computer has not seen my Nexus 5 because of the drivers, just google nexus usb drivers and install the latest ones.
azsgolf said:
Wug's tool has been invaluable to me in the past. I have gone from KitKat to Lollipop, back and forth, different ROMS, stuck boots, bad flashes. Like Zap says if you can get it to Bootloader then get Wug's tool to connect in fastboot, it will do the rest.
A couple times I have ran into problems where my computer has not seen my Nexus 5 because of the drivers, just google nexus usb drivers and install the latest ones.
Click to expand...
Click to collapse
Got any ideas on Fastboot.exe stopping working when the flash process begins? it fails sending bootloader and then fastboot.exe fails. It says on the screen when i close the error message it's booting into bootloader, but the tablet never restarts. it stays on bootloader(where i had it in the first place.) It should turn off the screen and go back into bootloader. Please, any feedback is appreciated.
Have you tried selecting the option of hardbrick on the tool?