Related
Hello everyone, first of all I am a total newbie not just to rooting but also today was my first time ever using linux so please bear with me. Having said that, I have done my best to learn and understand the linux commands in the effin manual and followed all instructions as best as I could though I couldn't understand them well enough which is why I am here.
I am using Ubuntu 11.04 64 bit live cd but managed to install the i32-libs as stated in the effin manual. This is the only version of Ubuntu I could get from my friends as I have very slow internet connection and cannot download the new version or just the 32 bit one.
Anyway, on to the problem at hand.
I first ran the aahk, going through all the steps in the effin manual. My phone was originally on 2.3.5 and Sense 3 so I had to downgrade and the aahk downloaded the necessary rom(?) or RUU (?) to do this.
Once that was done, aahk carried on until the step where my phone rebooted.
This was where things started going wrong for me.
When the phone rebooted into 2.3.3 and started the wizard to set up my phone, I went through all that.
If I recall, at this point the aahk screen was up to “Once the downgrade is successful, press a key to return to the menu.... Otherwise, cut and paste the output to the screen into a text file for evaluation... then press a key. Press any key to continue...”
However, the step before that, “The phone will now reboot into HBOOT. If everything is okay, the phone will prompt you to continue by pressing VOLUME UP. It will reboot, flashing twice.”
PUSH POWER WHEN THIS STEP COMPLETES
I don't recall this happening for me or maybe it did but I did not notice. I did not press VOLUME UP nor see the flashing twice but surely it happened? Otherwise I would have been able to reboot into the phone environment correct? My head is spinning now...
Okay, this is where I may have gotten ahead of myself when reading the effin manual. You have to understand, I was just brimming with joy “thinking” I had successfully rooted my first ever and one and only smartphone.
I started looking for BusyBox or Superuser but couldn't find anything.
Not knowing what else to do, I rebooted the phone MANUALLY (hold power button and reset).
Then everything started going wrong.
Please don't get mad. I did not realise the aahk had to reboot several times. I thought once and that was it. I just found that out now.
However, between that time and when I found this out I believe I caused all sorts of damage.
When the phone rebooted, it got stuck on the white screen with HTC logo and aahk was no longer working.
The wrong things I did were to to go into HBOOT and RECOVERY and WIPE EVERYTHING (DATA, CACHE, DAVLIK, EVERYTHING) *SORRY!*
And so here I am, hoping someone can help me.
After searching around the forums some similarities I had with other users in the past was that the phone is still showing S-ON and because of what I had done, aahk did not get to work properly so my phone has no ROM and no RECOVERY.
And I also JUST realised I made things worse by deleting USB debugging when I WIPED everything!.
Please help.... (_ _”)
I can help you out. Can you still go in Hboot?
Sent from my Desire HD using XDA
dnplee said:
Hello everyone, first of all I am a total newbie not just to rooting but also today was my first time ever using linux so please bear with me. Having said that, I have done my best to learn and understand the linux commands in the effin manual and followed all instructions as best as I could though I couldn't understand them well enough which is why I am here.
I am using Ubuntu 11.04 64 bit live cd but managed to install the i32-libs as stated in the effin manual. This is the only version of Ubuntu I could get from my friends as I have very slow internet connection and cannot download the new version or just the 32 bit one.
Anyway, on to the problem at hand.
I first ran the aahk, going through all the steps in the effin manual. My phone was originally on 2.3.5 and Sense 3 so I had to downgrade and the aahk downloaded the necessary rom(?) or RUU (?) to do this.
Once that was done, aahk carried on until the step where my phone rebooted.
This was where things started going wrong for me.
When the phone rebooted into 2.3.3 and started the wizard to set up my phone, I went through all that.
If I recall, at this point the aahk screen was up to “Once the downgrade is successful, press a key to return to the menu.... Otherwise, cut and paste the output to the screen into a text file for evaluation... then press a key. Press any key to continue...”
However, the step before that, “The phone will now reboot into HBOOT. If everything is okay, the phone will prompt you to continue by pressing VOLUME UP. It will reboot, flashing twice.”
PUSH POWER WHEN THIS STEP COMPLETES
I don't recall this happening for me or maybe it did but I did not notice. I did not press VOLUME UP nor see the flashing twice but surely it happened? Otherwise I would have been able to reboot into the phone environment correct? My head is spinning now...
Okay, this is where I may have gotten ahead of myself when reading the effin manual. You have to understand, I was just brimming with joy “thinking” I had successfully rooted my first ever and one and only smartphone.
I started looking for BusyBox or Superuser but couldn't find anything.
Not knowing what else to do, I rebooted the phone MANUALLY (hold power button and reset).
Then everything started going wrong.
Please don't get mad. I did not realise the aahk had to reboot several times. I thought once and that was it. I just found that out now.
However, between that time and when I found this out I believe I caused all sorts of damage.
When the phone rebooted, it got stuck on the white screen with HTC logo and aahk was no longer working.
The wrong things I did were to to go into HBOOT and RECOVERY and WIPE EVERYTHING (DATA, CACHE, DAVLIK, EVERYTHING) *SORRY!*
And so here I am, hoping someone can help me.
After searching around the forums some similarities I had with other users in the past was that the phone is still showing S-ON and because of what I had done, aahk did not get to work properly so my phone has no ROM and no RECOVERY.
And I also JUST realised I made things worse by deleting USB debugging when I WIPED everything!.
Please help.... (_ _”)
Click to expand...
Click to collapse
Do not panic...although you did a factory reset and disabled usb debugging, you can solve your situation. Just flash the RUU (PD98IMG-GBx.zip) file you used to downgrade the phone. It has to be in the PD98IMG folder of the Hack Kit. Make sure that it is that file and no other. Rename it PD98IMG.zip and then put it in the root of the sdcard. Then boot in hboot and update pressing volume up. Let it finish....then you will have a working phone. Then re run the hack kit to Gain S-OFF and Root....if you can´t do it just hit the IRC Channel that is stated in the OP of the Hack Kit thread.
benydc, glevitan, thank you both for the offers of help and advice.
I eventually found my way to the IRC aahk support channel and was blessed to get the help of attn1, one of the ops there.
He helped me through my problem and now everything is as is should be. Thankfully I have a working rooted phone.
Everyone there was very friendly and helpful, not just attn1. He must have spent the last two hours or so juggling with helping out three users (probably more). We even got to make some friendly banter amongst ourselves.
Though I was freaked out initially, I am glad everything works now and from the support I got there, I am somehow not going to shy away from trying to learn about rooting.
I managed to save all the text during our conversation so when I get the time, I will try and build a simple but detailed walkthrough of how attn1 got my phone working again. I will post it here so that it may help others who find themselves in a similar position one day.
Many thanks you guys. This is a great community.
same problem,s-on,no recovery
hey there...ive got similar problem with u and i try putting the PG98IMG on the root of the SD card which i get from the folder from AAHK...but when i go to HBOOT and try to install the PG98IMG, it failed and it says MAIN VERSION IS OLDER ! what should i do?
hi
i have same phone whith you
2.3.5 sens 3.0
i used AAHK but the file name downloaded is "PD98IMG-GB2"
you can rename "PD98IMG" on "PD98IMG-GB2"
Hello XDA,
I have used your services in the past but this time I'm stuck. Usually I had better luck just using the search function for what I needed but this time I can't seem to find what I need so this is my first post. Yes i basically I troll
Anywho, my ion is stuck in a boot loop (barely gets to the home screen and freezes then repeats that over and over and over) and when I hold the volume down plus power button, I get the green light which I read is flash mode, my problem is when I try to start the flash process I get a warning that says "must install drivers first".
How can I do that with the phone being in a boot loop and it won't sit long enough for the computer to recognize the phone and download the necessary drivers?? It seems like the computer only wants to download drivers when it's on and not in flash mode.
Currently I did what I'm assuming is a hard reset. Held the volume down and power button past the 3 vibrations then I had to let the phone sit for 16+ hours charging. The red light turned on eventually and it has finally turned off again. I think it is ready to be flashed except I'm not sure what to do.
I purchased the phone second hand and it has already been upgraded to ICS 4.0.4 I believe and it had a lot of junk on it. All I want to do is wipe the hard drive (and all its content) and install a fresh copy of ICS 4.0 and just get it back to factory.
Thanks for helping out this confused troll
Oh just in case your wondering, I was deleting apps and the previous owners email accounts when it crashed and thats when it went into a boot loop. Thanks again for your help I really do appreciate it.
The drivers are in the flashtool folder, /flashtool/drivers. Run the exe. Select your model & fastboot & flashmode drivers. Then keep trying it should get recognized and then flash. However it may take several attempts
Good luck
~Jaramie
Sent from my ION
ToledoJab said:
The drivers are in the flashtool folder, /flashtool/drivers. Run the exe. Select your model & fastboot & flashmode drivers. Then keep trying it should get recognized and then flash. However it may take several attempts
Good luck
~Jaramie
Sent from my ION
Click to expand...
Click to collapse
I'm doing something wrong I think because I'm not finding what your referring to...
I opened the flash tool and even tried running it as administrator-clicked on help - check drivers - and all I get is ( list of ADBLOCK drivers/none, List of fast boot devices - none)
Even under firmware selections all I see under devices is the x10/ version - v1/ branding - blrelock. I seen screenshots under firmware and there is usually a list but for some reason mine doesn't have that. I downloaded the .ftf file so technically it should work right? Or am I missing something here??
ToledoJab said:
The drivers are in the flashtool folder, /flashtool/drivers. Run the exe. Select your model & fastboot & flashmode drivers. Then keep trying it should get recognized and then flash. However it may take several attempts
Good luck
~Jaramie
Sent from my ION
Click to expand...
Click to collapse
Never mind!! I think I just found what you were talking about!! Thank you!!!!!!!! I'll keep you posted....
Please ask all questions in Q&A. Thread moved there.
Hello everyone, i have used this site for root another phones on past but now i can't understand how to fix my problem by myself. Thats why i'm here to kindly ask(beg) for help.
I tryed to root the phone, first i used the Framaroot, i thought it worked but look likes not, i'm getting the Secure booting Error! Couse: boot certification verify.
Ok, looks not a big deal, lots of guys got it and solved their problems with this post. But now is where i ask sorry because i couldn't make it.
I can enter on dowload mode, i tried all the steps on the post and did not worked. I need a light.
When i used the KDZ_FW, i got a message of error on extrating file.
When i tryed make a Recovery Hard Reset, i got the message Secure booting Error! Couse: boot certification verify.
When i try to turn it on by pressing the power + volumerdown = nothing happen.
I have a Optimus G E977, and the software was the E97710d.
Thanks for the attention.
http://forum.xda-developers.com/showpost.php?p=45355871&postcount=1
Question 5. I know it's hard to read before..i see things didn't changed around since i left. I see same lazy people,rushing into things before looking around....pffff....
Maybe U can help me too.
Everything was fine with my OG but problems start when installing CM11. I decided to go back to stock later (I did it) but then couldnt be able to enter recovery or download mode. I tried several methods like re root, unlock again and lately using ROM Manager and trying to install another recover all get screwed up. Only black screen. Trying and trying I could install KDZ firmware
So then I root, unlock boatloader with method one from here: http://forum.xda-developers.com/showthread.php?t=2667398
Ok i dont know if boatloader is unlocked now but i know I cant enter recovery or download mode. Im afraid to use freegee to try to unlock again.
What should I do.
Thanks
kimitza said:
http://forum.xda-developers.com/showpost.php?p=45355871&postcount=1
Question 5. I know it's hard to read before..i see things didn't changed around since i left. I see same lazy people,rushing into things before looking around....pffff....
Click to expand...
Click to collapse
kimitza said:
http://forum.xda-developers.com/showpost.php?p=45355871&postcount=1
Question 5. I know it's hard to read before..i see things didn't changed around since i left. I see same lazy people,rushing into things before looking around....pffff....
Click to expand...
Click to collapse
I appreciate your intention to help, maybe its because i'm a Braziliam guy, with not the best english, that i can't figure how to use the FREEGEE app if i can't start the cellphone.
Thanks again.
OBS: I have used that app too before get this error. And was just becouse tryed to enter on recovery mode that i got that message.
I understand that your celphone cant turn on or enter download mode or recovery?
If thats your situation maybe I can help U (I think)
Fuguets said:
I appreciate your intention to help, maybe its because i'm a Braziliam guy, with not the best english, that i can't figure how to use the FREEGEE app if i can't start the cellphone.
Thanks again.
OBS: I have used that app too before get this error. And was just becouse tryed to enter on recovery mode that i got that message.
Click to expand...
Click to collapse
Well, i'll try to explain all to not get missunderstood.
My situation is, without the USB cable the celphone don't respond to any button press.
With USB cable, by the momment that i plug it, the screen shows the error message.
With the USB cable and in the error message screen, i can press the volume buttons +- and power, after that the phone restart and shows the download mode.
What i know so far is, if i can enter download mode, and here is your words, all is not lost.
Knowing that, all solutions i found on this site doesn't work with me. Or, what is possible, i didn't make it right.
The phone do not enter on recovery mode.
I gess this is all. For now
Thanks for the patience to teach who needs to be teached.
ErnestoD said:
I understand that your celphone cant turn on or enter download mode or recovery?
If thats your situation maybe I can help U (I think)
Click to expand...
Click to collapse
My previous problem was far worst than yours.
I recommend U to uninstall all LG stuff from your PC and follow this guide: http://www.htcmania.com/forumdisplay.php?f=1026
Its in spanish so I think U wont have much problem
I did it yestesrday and save me. Whit it U will install a new KDZ firmware, even if it is bigger than 1GB
Good luck
QUOTE=Fuguets;51799238]Well, i'll try to explain all to not get missunderstood.
My situation is, without the USB cable the celphone don't respond to any button press.
With USB cable, by the momment that i plug it, the screen shows the error message.
With the USB cable and in the error message screen, i can press the volume buttons +- and power, after that the phone restart and shows the download mode.
What i know so far is, if i can enter download mode, and here is your words, all is not lost.
Knowing that, all solutions i found on this site doesn't work with me. Or, what is possible, i didn't make it right.
The phone do not enter on recovery mode.
I gess this is all. For now
Thanks for the patience to teach who needs to be teached.[/QUOTE]
As I see, if i'm looking for the guide you are refering, of install the original rom, is the same one that i already tried and i got message error of extract file.
I deleted all lg stuff from computer, downloaded everything of the guide and the message is the same.
Any more suggestion ?
PS: I prefer english version , at least to read is easy to me.
Edit1:I wonder if the fact of my kdz file be bigger than 1gb causes that ?
Edit2: When i try the guide on this link the step 7 does not show to me, and my phone or some similar does not show on the Usb Controler list to install.
Thanks again
ErnestoD said:
My previous problem was far worst than yours.
I recommend U to uninstall all LG stuff from your PC and follow this guide
Its in spanish so I think U wont have much problem
I did it yestesrday and save me. Whit it U will install a new KDZ firmware, even if it is bigger than 1GB
Good luck
QUOTE=Fuguets;51799238]Well, i'll try to explain all to not get missunderstood.
My situation is, without the USB cable the celphone don't respond to any button press.
With USB cable, by the momment that i plug it, the screen shows the error message.
With the USB cable and in the error message screen, i can press the volume buttons +- and power, after that the phone restart and shows the download mode.
What i know so far is, if i can enter download mode, and here is your words, all is not lost.
Knowing that, all solutions i found on this site doesn't work with me. Or, what is possible, i didn't make it right.
The phone do not enter on recovery mode.
I gess this is all. For now
Thanks for the patience to teach who needs to be teached.
Click to expand...
Click to collapse
[/QUOTE]
I didnt see that on XDA. I used this method with 2 kdz´s, one smaller and another one bigger than 1gb.
Maybe U missed something.
Fuguets said:
As I see, if i'm looking for the guide you are refering, of install the original rom, is the same one that i already tried and i got message error of extract file.
I deleted all lg stuff from computer, downloaded everything of the guide and the message is the same.
Any more suggestion ?
PS: I prefer english version , at least to read is easy to me.
Edit1:I wonder if the fact of my kdz file be bigger than 1gb causes that ?
Edit2: When i try the guide on this link the step 7 does not show to me, and my phone or some similar does not show on the Usb Controler list to install.
Thanks again
Click to expand...
Click to collapse
[/QUOTE]
Now I am really worried about that. I just can't acces the phone by any kind of way.
When i try the Unlock Botloader, it says that didn't found my device.
Now, after restart the computer, it says: The system cannot find the patch specified.
Is there no more options for me ?
The drivers I have downloaded here was automaticly updated from 8.0xx to 10.0xx, I unterstand this is a good thing, am I wrong ?
Could U flash KDZ using the method from htc mania?? (Im using it rigth now with 1.2GB KDZ firmware)
How did U come to that situation?
Fuguets said:
Now I am really worried about that. I just can't acces the phone by any kind of way.
When i try the Unlock Botloader, it says that didn't found my device.
Now, after restart the computer, it says: The system cannot find the patch specified.
Is there no more options for me ?
The drivers I have downloaded here was automaticly updated from 8.0xx to 10.0xx, I unterstand this is a good thing, am I wrong ?
Click to expand...
Click to collapse
I did that, while i use the KDZ one minute after start unpacking the file, it shows the error message and finish the procces. I don't know if is that what you were asking.
When I tried the button Read Phone Information, it tells me Emergency Not Support Batt Level Check.
Is that the problem ?
ErnestoD said:
Could U flash KDZ using the method from htc mania?? (Im using it rigth now with 1.2GB KDZ firmware)
How did U come to that situation?
Click to expand...
Click to collapse
Did U overwrite LGMOBILEAX folder was stated and (step 2). Did U edit hosts file as stated (step 3=
In my case i previously have a black screen, nothing more, but connecting phone to PC while pressing both volum keys aloud PC to recognice the phone.
If U receive extraction error that means that the patch is wrong. Do not press anything more in the program There is no need to
Fuguets said:
I did that, while i use the KDZ one minute after start unpacking the file, it shows the error message and finish the procces. I don't know if is that what you were asking.
When I tried the button Read Phone Information, it tells me Emergency Not Support Batt Level Check.
Is that the problem ?
Click to expand...
Click to collapse
I did not overwrite that folder, maybe we are looking for different guides because if that was something that i supose to do i didn't saw that on the guide.
I did not edit hosts file.
I restarted the computer now again, and now my message is: device not found.
Can you place the link of exacly guide i need to look ? Couse the link you send me before has a various of them.
ErnestoD said:
Did U overwrite LGMOBILEAX folder was stated and (step 2). Did U edit hosts file as stated (step 3=
In my case i previously have a black screen, nothing more, but connecting phone to PC while pressing both volum keys aloud PC to recognice the phone.
If U receive extraction error that means that the patch is wrong. Do not press anything more in the program There is no need to
Click to expand...
Click to collapse
http://www.htcmania.com/showthread.php?t=802175
Remenber to start from zero
Tested on WIN7 64 bits
ErnestoD said:
http://www.htcmania.com/showthread.php?t=802175
Remenber to start from zero
Tested on WIN7 64 bits
Click to expand...
Click to collapse
Helo again, i just finish the proccess now. Again i got the same message, I attached the log file, if you please have a look on that i appreciate.
I don't know, all the problem looks to be batterys fault. I hope not. Thanks.
Edit1: I foun this guide, do you think it could help me ?
But I didn't understand that well, looks like I need to be able to start the OS of the phone, which i can't.
Im sad to hear that , This is beyond my knowledge. It worked for me but...
Fuguets said:
Helo again, i just finish the proccess now. Again i got the same message, I attached the log file, if you please have a look on that i appreciate.
I don't know, all the problem looks to be batterys fault. I hope not. Thanks.
Click to expand...
Click to collapse
ErnestoD said:
Im sad to hear that , This is beyond my knowledge. It worked for me but...
Click to expand...
Click to collapse
What about my edit, where i found that someone said it solve the problem on 15%, do you think it could work ?
I just don't understant well, do I need to be able to start my phone rom ? Or i can do on my situation ?
Hello guys,
I am so happy that I wanted to share this with you. As I still have headache from googling how to flash back your stock rom (which didn't work out because the flash tool gave an error every time at 15%), I can save you a lot of headache with this very very simple fix.
For some people the tool works just fine, but when you have some google bootloader or a newer freegee unlocked one and you want back to stock, lots of people cant follow this thread because of the error at 15%.
The fix is EASY and I found it on the Optimus L9 section, thanks to that guy on XDA.
Follow exactly Davevinci's great thread except for one thing:
http://forum.xda-developers.com/show....php?t=2498102
Step 4 is now:
4.GO TO DOWNLOAD MODE POW+BOTH VOL BUTTON PRESSED+CONNECT USB
But step 4 should be:
- Boot up your phone in any stock based rom, for example SAVVY Rom V5
- Enable USB debugging and connect your phone through USB using the LG PC Suite option (make sure to kill PC suite in tast manager).
Now you should see the driver installation of LGE Android MTP device as usual and then just run the flash tool from the guide. Also de mode DIAG is now the right one. The flashtool will reboot your phone to download mode automatically when it's needed.
Still an error? Don't worry, disable virus scanner and firewall and just reconnect your phone. I got an error one time, during flashing, but I followed the steps the flashtool suggested me and now everything went fine.
Click to expand...
Click to collapse
The link U provide is not working and U didnt upload any log, I didnt see it.
As I read to perform that action u must be able to turn on your phone.
Did U try to flash a smaller then 1gb kdz or try another ones.
As U can see U wont receive to much help in LG forum. There are good guides but on time help is another thing.
Did U try this guide (method 1): http://forum.xda-developers.com/showthread.php?t=2667398
Is your phone properly detected in your PC?
Fuguets said:
What about my edit, where i found that someone said it solve the problem on 15%, do you think it could work ?
I just don't understant well, do I need to be able to start my phone rom ? Or i can do on my situation ?
Click to expand...
Click to collapse
I did not tried with a smaller archive because I can't download it. Among the Brazilian files I only can download the version 10D. I am on phone now but I will send the link that I'm trying asap. I really appreciate your help man. Even that I didn't found the solution yet is nice count with some experience help.
Enviado de meu XT1032 usando Tapatalk
Edit: From this list http://forum.xda-developers.com/showthread.php?t=2093382 , all brazilian links show Access Denied
And from here http://lg-phone-firmware.com/index.php?id_mod=20, only the V10D of Brazil.
I'm looking for the number 16, CLR/CLARO(BRAZIL) which is less than 1GB. Maybe i'm wrong, but when i clic on the name, a page of TNY shows a link of ADFLY that after i clic on close advertisement nothing happen.
About the method 1, I did try that, but sometimes it says "device not found" or "the system cannot find the patch specified". I'll try that from another computer, i let you know if i have some lucky. But the guy of the guide said:
!enable usb debugging
connect as MTP
follow the script"
Maybe its not for me.
Look what happen. (I'm using download mode)
*********************************************
* Tool Unlock BL Optimus G - Update 0414 *
* *
*********************************************
*** Select a number ***
1. UNLOCK BOOTLOADER
Seclect a number : 1
1. [Unlock] Optimus G JB 4.1.2 Selelct
Seclect a number : 1
FreeGee UNLOCK
Thanks to Team Codefire
1. JB 4.1.2
╣Seclect a Number : 1
1. KT
2. SKT
3. LGU+
╣Seclect a number : 1
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
error: device not found
Unlock BL success.
╕Reboot [y]/[n] :
About my phone get propper detected, i guess it is, at least on my devices map it shows "Lg AndroidNet Phone"
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?
Hey guys,
I've had my Z1C for quite some time now and have messed around with various ROMs and such and if I ever came across a problem, I would always find a solution for it online, but this time it's different. I've done a lot of searching already, and found some similar problems on the internet, but none of them were quite like the one I've got right now.
Okay, first of all, for quite some time now I've been successfully using SlimKat and only updating every couple of months or so (and yes, since SlimKat officially came out on Z1C, I've been using the official version). It all began when I decided to update to a new version today. I went to the SlimRoms website, found my device on supported devices list, downloaded the zip file, downloaded gapps, and flashed them following the instructions. I've done this many times before already and it always worked without problems, but this time after the flashing finished (which was successful), my phone wouldn't turn on. After trying one thing after another, I realized that at first this was a driver problem, then I found out that my Z1C is now recognized as a Z1. Then I went back to SlimRoms website, and check it out- after clicking on Z1C (amami) on the supported devices list, it directs you (at least it directs me) to Z1 (honami) download page. I didn't even notice the different name, because every time I did this I didn't have any problems. So that's my current story. I will now list all the major symptoms.
- After holding volume up + power button until it shuts off I plug it into a wall charger or a pc through usb cable, first I get a red LED for like a second, then a pink/purple one for a two or three seconds, then it turns yellow and stays that way (charging?). After a few seconds I get the ability to browse the phone's files, but the device is named 'Z1'. If I plug it in without force shutting it off, it goes straight into yellow LED.
- If I try to repair it with Sony PC Companion, it gives me an error that the device is running modified software. Obvious.
- If I plug it in with flashtool on, at first it gives me an error that it cannot be identified and gives me a list of devices to choose from and then asks if I want my device to be permanently recognized as the one I chose. But this doesn't seem to work, because it gives me the same error every time I try to do it again. And if I try to flash a stock firmware, I get an error ERROR - Cannot delete C:\Flashtool\.\firmwares\prepared\boot. Previously it gave me errors regarding drivers, but no matter how many times I tried to install them with the driver installer from flashtool, uninstalling the device through device manager and so on, it didn't help. But after something I did that I'm not very sure about, I don't seem to get this error anymore.
- If I try to turn it on, it vibrates once as usual, gives me the pink/purple led for a couple seconds and then nothing.
There might be something I haven't mentioned, so feel free to ask. Not sure if that matters, but I'm on unlocked bootloader.
I seriously hope there's a fix for that, not sure if my unlocked bootloader would help with a warranty repair.
I guess that's all. Thanks in advance everyone.
VidmuxD said:
There might be something I haven't mentioned, so feel free to ask. Not sure if that matters, but I'm on unlocked bootloader.
Click to expand...
Click to collapse
Flash a Z1C kernel with fastboot and try the flashtool again.
XperienceD said:
Flash a Z1C kernel with fastboot and try the flashtool again.
Click to expand...
Click to collapse
Man, thanks a lot! Worked like a charm. I was thinking about flashing something via fastboot because it seemed to be working, but I didn't want to mess up anything else before making sure it was safe. Apparently the solution was simple. You've got my gratitude!