Ok i came here from here http://forum.xda-developers.com/showthread.php?t=1751796
Droid Incredible 2 runnig GB 2.3.4 -- 6.01.605.05 710RD
TACOROOT
(TCR)
Versions: 6.01.605.05 firmware
Tacoroot is a temp root method discovered by Justin Case that will allow those on the newer firmware to flash an older version and root with Revolutionary. Before you begin, download this zip containing all the files you'll need:
http://d-h.st/yJQ
Extract this zip to C:/Android. You can extract it somewhere else, just replace C:/Android with the path to the wherever you extracted it wherever it comes up. Now, connect your device to your computer with a USB cable, turn on USB Debugging under Settings>Apps>Development, and disable fastboot under Settings>Power. Make sure your phone is fully charged. Open a command prompt by opening the start menu, typing "cmd" and hitting enter. Type in everything that is in black text. Notes and extra instructions will be written in blue. It is reccomended that you copy/paste the code to avoid typos, to do this, copy by highlighting the line and hitting Ctrl+C as usual; to paste, go to your command prompt and click the small black icon in the upper left corner. A menu will pop up, go to Edit>Paste. Make sure you have not highlighted any spaces before or after the line or any of the blue text. Now, begin copying the code:
cd C:/Android
md5sums RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra dio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip Remove the space in the middle of the word radio before hitting enter, I don't know why it won't let me remove it. Result should be cea499f51b40055ffd118960e1e73255, if it isn't, redownload the miniadb zip.
md5sums 1.09.01.0312_vivow_Radio_PG32IMG.zip Result should be ea6b98be48210d7797e62362f49ff751
md5sums tacoroot.sh Result should be 6ec06d776feb212d8b2a55817eddf76d
md5sums misc_version Result should be 050f55d34ddbcc860efa5982491437de
adb devices Result should be your phone's serial number. If it isn't make sure drivers are properly installed and USB Debugging is enabled.("Its all good till i reach this step, i cant see my serial number, i have installed the drivers, the new ones from htc sync, i have reinstalled the drivers but it not work at all...)"
adb push tacoroot.sh /data/local/
adb shell chmod 755 /data/local/tacoroot.sh
adb shell /data/local/tacoroot.sh --setup This will reboot your phone. When you get to a screen with a red exclamation mark, press VolUp+Power until you get to a menu, then press VolUp+VolDown+Power until the phone turns off. Once it is rebooted, continue.
adb shell /data/local/tacoroot.sh --root
adb wait-for-device Running the step before this will reboot your phone again, this time it will be bootlooping, meaning it will not boot fully and get stuck on the boot animation. Once your prompt comes back after this step, you're good to continue even though the phone isn't fully booted.
adb push misc_version /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/misc_version
adb shell /data/local/tmp/misc_version -s 2.18.605.3
adb shell /data/local/tacoroot.sh --undo This will reboot your phone one more time, this time fully stable and will boot completely. Continue once fully booted.
adb reboot bootloader This will reboot your phone to a white screen with a few options. Once you are at this screen, continue with the instructions.
fastboot devices Result should be your phone's serial number, again.
fastboot getvar mainver The result should be 2.18.605.3. If it is not, something was not done correctly, you'll need to restart from the beginning.
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip RUU_Vivo_W_Gingerbread_S_VERIZON_WWE_2.18.605.3_Ra dio_1.09.01.0622_NV_VZW1.92_release_199487_si.zip This will take a bit of time without giving any indication as to when it will be done, be patient and do not interrupt it.
fastboot erase cache
fastboot oem rebootRUU
fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip Same as the above, do not interrupt under any circumstances (unless you really wanted a phone-shaped paperweight )
fastboot reboot
Make sure you have USB debugging enabled, I think it's under Apps>Development.
Sent from my SCH-I535 using Tapatalk 2
It is enabled and the drivers are installed.
I had installed the HTC sync but it never recognized the phone so it make me think that is a problem with the drivers.
Sent from my HTC DROID Incredible 2 using Tapatalk
Killerin said:
It is enabled and the drivers are installed.
I had installed the HTC sync but it never recognized the phone so it make me think that is a problem with the drivers.
Sent from my HTC DROID Incredible 2 using Tapatalk
Click to expand...
Click to collapse
Don't install htc sync, that can mess it up. The drivers from the OP should work, nobody else has had problems with them.
Sent from my SCH-I535 using Tapatalk 2
I also tried that but the drivers of the OP doesn't work for me, I can't even install it. Will upload the screen shots.
I'm using windows 8 could it be a problem?
Sent from my HTC DROID Incredible 2 using Tapatalk
This is what i get when im trying to install the OP's Drivers
Killerin said:
This is what i get when im trying to install the OP's Drivers
Click to expand...
Click to collapse
Translation?
Sent from my SCH-I535 using Tapatalk 2
prototype7 said:
Translation?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
The assistant has been interrupted before finishing installation of the HTC Driver Installer.
Your system has not been modified. To install this program another time execute the installer program again.
Click on finish to leave the assistant.
gtdtm said:
The assistant has been interrupted before finishing installation of the HTC Driver Installer.
Your system has not been modified. To install this program another time execute the installer program again.
Click on finish to leave the assistant.
Click to expand...
Click to collapse
+1, dont know what appeared on spanish lol
Will Install windows 7, probably is W8 the problem with the drivers
thats it!! the problem was Windows 8! now in windows 7 could do everything but got stucked on last step " fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip Same as the above, do not interrupt under any circumstances (unless you really wanted a phone-shaped paperweight )"
C:\Android>fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip
sending 'zip' (13225 KB)... OKAY [ 3.401s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 6.195s
the phone is stucked on HTC logo... now what?
Edit: Had to remove the battery and unplug the usb from the phone to get out of the htc logo screen. now is rebooted and running 2.3.3 the version downgraded i guess is all fine. now will continue with the Revo!
Killerin said:
thats it!! the problem was Windows 8! now in windows 7 could do everything but got stucked on last step " fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip Same as the above, do not interrupt under any circumstances (unless you really wanted a phone-shaped paperweight )"
C:\Android>fastboot flash zip 1.09.01.0312_vivow_Radio_PG32IMG.zip
sending 'zip' (13225 KB)... OKAY [ 3.401s]
writing 'zip'... INFOsignature checking...
FAILED (remote: 12 signature verify fail)
finished. total time: 6.195s
the phone is stucked on HTC logo... now what?
Edit: Had to remove the battery and unplug the usb from the phone to get out of the htc logo screen. now is rebooted and running 2.3.3 the version downgraded i guess is all fine. now will continue with the Revo!
Click to expand...
Click to collapse
I am having the same problem. It sounds like this last step is supposed to take as long as the previous step. The fact that it comes up with the "FAILED (12 signature verify fail) response worries me. If I reboot and continue on with installing revolutionary, will this brick my phone? Or is it supposed to do this (12 signature verify fail)?
I've read a lot of people have that problem. Just move on with rev and go back later and update the radio. A quick search will give you LTS of threads with the instructions to install a new radio. Hint:it's done in boot loader not recovery.
Sent from my Incredible 2 using xda app-developers app
Related
Hey, I've been following Cyanogen mods guide about flash_image to flash PSFmod onto my phone. I can use ADB to push files to my SD card and stuff, but when I follow this:
Code:
Temporarily allow app to run from the sdcard (use mount to find the correct device for your sdcard, ie: the /dev/block/BLAH part)
mount -o remount,exec /dev/block//vold/179:1 /sdcard
cd /sdcard
./flash_image recovery /sdcard/recovery.img
But I get this error:
Code:
error scanning partitions
Does anyone know how to fix it?
You get that error from which of those commands ?
From flash_image.
Whenever I run flash_image from my phone now, I get that partition error.
Is it because I'm on a Desire Z?
Beegee7730 said:
From flash_image.
Whenever I run flash_image from my phone now, I get that partition error.
Is it because I'm on a Desire Z?
Click to expand...
Click to collapse
Where did you get the flash_image utility from ? Was it from somewhere that has verified it to work on DZ ?
Dude u might brick ur phone lol ...try using Rom manager .....its safer
Sent from my HTC Vision using XDA App
I would use fastboot to flash a new recovery. You're sure what you're flashing is ok for the Vision, right ?
steviewevie said:
Where did you get the flash_image utility from ? Was it from somewhere that has verified it to work on DZ ?
Click to expand...
Click to collapse
I got it from the Cyanogen Mod Wiki, should I look for a different version?
theXeffect said:
Dude u might brick ur phone lol ...try using Rom manager .....its safer
Sent from my HTC Vision using XDA App
Click to expand...
Click to collapse
I would but the recovery I'm flashing isn't supported by Rom Manager.
steviewevie said:
I would use fastboot to flash a new recovery. You're sure what you're flashing is ok for the Vision, right ?
Click to expand...
Click to collapse
How do I use Fastboot? It should be okay for it, as it's the G2 version of Psfmod.
Beegee7730 said:
How do I use Fastboot? It should be okay for it, as it's the G2 version of Psfmod.
Click to expand...
Click to collapse
If you've got adb all setup via installing the SDK etc, then fastboot should work fine too. I think you need the engineering bootloader though.
Boot the phone into fastboot by holding down the trackpad button and holding the Power button, with the phone off. Or you can put it into hboot with Volume Down and Power and then select "Fastboot" from the menu.
It should then say "Fastboot" on the phone. With the USB cable plugged in that should say "Fastboot USB", and if you run "fastboot devices" on your PC it should show up your phone in the same way that "adb devices" normally would.
If that's all working you can run "fastboot flash recovery filename.img" to flash "filename.img" to recovery.
steviewevie said:
If you've got adb all setup via installing the SDK etc, then fastboot should work fine too. I think you need the engineering bootloader though.
Boot the phone into fastboot by holding down the trackpad button and holding the Power button, with the phone off. Or you can put it into hboot with Volume Down and Power and then select "Fastboot" from the menu.
It should then say "Fastboot" on the phone. With the USB cable plugged in that should say "Fastboot USB", and if you run "fastboot devices" on your PC it should show up your phone in the same way that "adb devices" normally would.
If that's all working you can run "fastboot flash recovery filename.img" to flash "filename.img" to recovery.
Click to expand...
Click to collapse
Wait a sec.
steviewevie said:
If you've got adb all setup via installing the SDK etc, then fastboot should work fine too. I think you need the engineering bootloader though.
Boot the phone into fastboot by holding down the trackpad button and holding the Power button, with the phone off. Or you can put it into hboot with Volume Down and Power and then select "Fastboot" from the menu.
It should then say "Fastboot" on the phone. With the USB cable plugged in that should say "Fastboot USB", and if you run "fastboot devices" on your PC it should show up your phone in the same way that "adb devices" normally would.
If that's all working you can run "fastboot flash recovery filename.img" to flash "filename.img" to recovery.
Click to expand...
Click to collapse
Tried few days ago with a kernel,but don`t works too.
You mean I need the eng hboot,then it should work,right?
Otherwise fastboot don`t work.
C:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (4214 KB)... OKAY [ 0.891s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 0.891s
C:\android-sdk-windows\tools>
Beegee7730 said:
C:\android-sdk-windows\tools>fastboot flash recovery recovery.img
sending 'recovery' (4214 KB)... OKAY [ 0.891s]
writing 'recovery'... FAILED (remote: not allowed)
finished. total time: 0.891s
C:\android-sdk-windows\tools>
Click to expand...
Click to collapse
You haven't got S-OFF. You need S-OFF to flash a custom recovery.
I do have S-Off, I followed this and when I boot into fastboot it says "S-OFF" in green text at the top.
Beegee7730 said:
I do have S-Off, I followed this and when I boot into fastboot it says "S-OFF" in green text at the top.
Click to expand...
Click to collapse
ok, do you have the engineering bootloader ? Does it say "SHIP" or "ENG" at the top.
steviewevie said:
ok, do you have the engineering bootloader ? Does it say "SHIP" or "ENG" at the top.
Click to expand...
Click to collapse
SHIP.
I assume I need to reflash it with the engineering one?
Beegee7730 said:
SHIP.
I assume I need to reflash it with the engineering one?
Click to expand...
Click to collapse
Yeah I think you need the engineering bootloader for fastboot to work fully. I didn't think you'd get that sort of error for no eng bootloader though.
steviewevie said:
Yeah I think you need the engineering bootloader for fastboot to work fully. I didn't think you'd get that sort of error for no eng bootloader though.
Click to expand...
Click to collapse
Code:
C:\android-sdk-windows\tools>adb push hboot-eng.img /data/local
1598 KB/s (0 bytes in 1048576.000s)
Is that supposed to happen?
Beegee7730 said:
Code:
C:\android-sdk-windows\tools>adb push hboot-eng.img /data/local
1598 KB/s (0 bytes in 1048576.000s)
Is that supposed to happen?
Click to expand...
Click to collapse
Did it work and is the file there in /data/local now ?
Do a checksum on the eng hboot before you flash it, as per the guides, to make sure it's not corrupted.
steviewevie said:
Did it work and is the file there in /data/local now ?
Do a checksum on the eng hboot before you flash it, as per the guides, to make sure it's not corrupted.
Click to expand...
Click to collapse
Ah, managed to flash it.
Will test and report back when done.
EDIT:
It works!
Thanks alot!
steviewevie said:
Yeah I think you need the engineering bootloader for fastboot to work fully. I didn't think you'd get that sort of error for no eng bootloader though.
Click to expand...
Click to collapse
I think too,the same with my HTC Hero.
Fastboot wont work without engineering bootloader/hboot!
So the same at Desire Z.
Anybody know if its poissible to flash the Stock pd98img.zip by using adb shell, i want to return to stock but my volume up key isnt working so is there any way that i can use the adb instead of my volume up key
adilrenzu said:
Anybody know if its poissible to flash the Stock pd98img.zip by using adb shell, i want to return to stock but my volume up key isnt working so is there any way that i can use the adb instead of my volume up key
Click to expand...
Click to collapse
plug the phone in fastboot, you should see fastboot usb in red.
Open a cmd as admin or terminal as root in the pc
type: fastboot oem rebootRUU (you will get a black splash with silver htc)
fastboot flash zip "nameoffile.zip" (no quation marks)
Once it is done (it says OKAY. finished in the CMD session)
fastboot reboot
Make sure that u are in the same folder (in CMD) where the zip file is...This will only be feasible for a RUU...not a rom. It also works for radios and CWM recovery....:good:
glevitan said:
plug the phone in fastboot, you should see fastboot usb in red.
Open a cmd as admin or terminal as root in the pc
type: fastboot oem rebootRUU (you will get a black splash with silver htc)
fastboot flash zip "nameoffile.zip" (no quation marks)
Once it is done (it says OKAY. finished in the CMD session)
fastboot reboot
Make sure that u are in the same folder (in CMD) where the zip file is...This will only be feasible for a RUU...not a rom. It also works for radios and CWM recovery....:good:
Click to expand...
Click to collapse
Hey there, im in this part of the process. Right now is in writing "ZIP"... since around 1 hour. it is normal? how long it will take?
Thank you
fefetron said:
Hey there, im in this part of the process. Right now is in writing "ZIP"... since around 1 hour. it is normal? how long it will take?
Thank you
Click to expand...
Click to collapse
It shouldn´t take that long. Make sure that you are using the oem cable. That USB ports are working fine and there´s no other stuff connected to your USB ports.
glevitan said:
It shouldn´t take that long. Make sure that you are using the oem cable. That USB ports are working fine and there´s no other stuff connected to your USB ports.
Click to expand...
Click to collapse
I only have the mouse in the usb port. im using the HTC cable. i have a htc inspire 4g
fefetron said:
I only have the mouse in the usb port. im using the HTC cable. i have a htc inspire 4g
Click to expand...
Click to collapse
ok, do the following. Eject the sdcard and try again without the sdcard. Report back please. :good:
glevitan said:
ok, do the following. Eject the sdcard and try again without the sdcard. Report back please. :good:
Click to expand...
Click to collapse
Just Waiting for the device.. nothing more
im traying to install new drivers.
i´ll back
glevitan said:
plug the phone in fastboot, you should see fastboot usb in red.
Open a cmd as admin or terminal as root in the pc
type: fastboot oem rebootRUU (you will get a black splash with silver htc)
fastboot flash zip "nameoffile.zip" (no quation marks)
Once it is done (it says OKAY. finished in the CMD session)
fastboot reboot
Make sure that u are in the same folder (in CMD) where the zip file is...This will only be feasible for a RUU...not a rom. It also works for radios and CWM recovery....:good:
Click to expand...
Click to collapse
Many thanks!
I too had this boot problem on a bad flash through the Hack Kit
(my fault by the way). From power on it took 20 mins to get to the first white HTC screen . Then a further 10 mins to start normal boot.
Apart from the LONG boot, everything worked perfectly. Using TermEm I could boot into bootloader and recovery. The rom, IceColdSandwich worked perfectly in every respect but the corrupted boot was doing my head in.
Using your tutorial, I managed to flash the correct bootloader and now all is good.
hboot before was 0.85.2007
hboot after is 0.85.0024
Sorry if this is a long post but I think it is worth it. Here is a log of the fastboot process:
F:\Android\DHD\Bootloader Image\Fastboot>adb devices
adb server is out of date. killing...
* daemon started successfully *
List of devices attached
HT11BRX11244 device
F:\Android\DHD\Bootloader Image\Fastboot>fastboot oem rebootRUU
... OKAY [ 0.375s]
finished. total time: 0.376s
F:\Android\DHD\Bootloader Image\Fastboot>fastboot flash zip PD98IMG.zip
< waiting for device >
sending 'zip' (227 KB)... OKAY [ 0.056s]
writing 'zip'... INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
INFOstart image[hboot] unzipping & flushing...
INFO[RUU]UZ,hboot,0
INFO[RUU]UZ,hboot,100
INFO[RUU]WP,hboot,0
INFO[RUU]WP,hboot,100
OKAY [6586.776s]
finished. total time: 6586.834s
F:\Android\DHD\Bootloader Image\Fastboot>fastboot reboot
rebooting...
finished. total time: 8.532s
F:\Android\DHD\Bootloader Image\Fastboot>
I have to say that the timings, because of the LONG boot, are completely wrong, . I was tempted to pull the plug on a number of occasions but I gave myself a talking to and went for a coffee.
The whole process took about 2 hours and I am now the delighted owner of a normal booting DHD.
To anyone who wants to attempt this procedure, the watchword is patience. Whenever you think nothing is happening, DO NOTHING!
The different stages will eventually happen just as laid out as per Glevitan. Good luck with your attempt.
Once again, many thanks.
Edit: Just an afterthought, at one stage Windows had a failed attempt at installing usb drivers that ended up as an 'Unknown Device'. Just ignore it and keep going.
Edit: I just tried again and it worked, nevermind!
Just fyi: if you get an error after flashing the ZIP, just flash it again.
Thanks! This was helpful.
glevitan said:
plug the phone in fastboot, you should see fastboot usb in red.
Open a cmd as admin or terminal as root in the pc
type: fastboot oem rebootRUU (you will get a black splash with silver htc)
fastboot flash zip "nameoffile.zip" (no quation marks)
Once it is done (it says OKAY. finished in the CMD session)
fastboot reboot
Make sure that u are in the same folder (in CMD) where the zip file is...This will only be feasible for a RUU...not a rom. It also works for radios and CWM recovery....:good:
Click to expand...
Click to collapse
I'm confused.... I'm following all the instructions using the toolkit v10.
I was able to unlock the bootloader without an issue, but when it comes to rooting, I'm having problems.
I use option 16 for the build, then option 4 to root. In the fastboot screen, the bottom Fastboot status says FAILInvalid Command as soon as it pulls up, then it goes to "reboot" after the 30 second wait.
It doesn't reboot automatically, so I press the power button to reboot it myself. then it reboots and then goes back into fastboot with the fail invalid command. Then this comes up:
downloading 'boot.img'
FAILED (remote: Invalid Command)
finished. total time: 0.006s
Waiting for device.
I'm at a loss. I feel like last time did this, I had to get the factory image and the boot.img file from somewhere and place them in the folders within the c:/galaxy nexus toolkit folder.
Any help would be greatly appreciated!
Thanks,
Nick
put on your big boy pants and root your phone this way:
http://forum.xda-developers.com/showthread.php?t=1529058
I have tried that... i get a similar message:
sending 'recovery' (5990 KB)
FAILED (remote: Invalid Argument)
finished. total time: 0.006s
then the fastboot status on the phone changes to "download 005d9800"
not sure what to make of that either.
is the cwm/twrp image actually named recovery? and is it in the fastboot.exe directory?
are you typing the command correctly? ( fastboot flash recovery nameofrecovery.img
It's in the same "platform-tools" folder that the fastboot.exe file is in. it's called recovery-clockwork-touch-6.0.2.3-toro.img, so i type fastboot flash recovery recovery-clockwork-touch-6.0.2.3-toro.img and hit enter. That's what made sense to me in reading that post.
waldo22 said:
It's in the same "platform-tools" folder that the fastboot.exe file is in. it's called recovery-clockwork-touch-6.0.2.3-toro.img, so i type fastboot flash recovery recovery-clockwork-touch-6.0.2.3-toro.img and hit enter. That's what made sense to me in reading that post.
Click to expand...
Click to collapse
Yep that's it
Sent from my Galaxy Nexus using Tapatalk 2
I'm guessing you mean that that's the correct way to do it and not, "yep that's you're problem." Any ideas where to go from there?
crazy... I switched to a different computer, and used the most up to date pdanet drivers, and it's going like a champ.
I tried the guide "How to root Android using Ubuntu" to root my device. It's a matter of overcome absurde limits like the otg, and stuff. My hope was to be using a step by step guide, but that's not completely true, as I sadly discovered. The procedure involves some operations with fastboot to unlock the bootloader and superuser utility to complete the task (already copied the recovery image through fastboot, of course). Now, I didn't realize, nor it was written on that <MOD EDIT-SWEARING> guide, that the su utility had to be put on the internal sdcard BEFORE to start the job.
Thus I started the job, unlocked the bootloader. Then I should have installed the zipfile (the superuser.zip) but not having it on the device, I chose to reboot from the cursor menu. The logic behind this was simple: I have unlocke the bootloader, not erased the os or whatever, thus it shoul restart; I don't have the needed file on the device, thus after a reboot I might copy it over through usb cable, enter again in recovery mode and "install the zip from sdcard".
From then on my device is stuck with the 4 merging/bouncing circles and I *cannot even turn off * it.
I'm a gentoo user, used to read and write guides "in a certain manner", everything was done under gentoo, where I'm now.
Situation now:
Code:
# lsusb
Bus 003 Device 027: ID 18d1:4ee1 Google Inc. Nexus 4 / 10
# fastboot devices
(nothing)
Before my mistake, it was:
Code:
# lsusb
Bus 003 Device 012: ID 18d1:4ee2 Google Inc. Nexus 4 (debug)
or
Code:
Bus 003 Device 014: ID 18d1:4ee0 Google Inc.
and
Code:
# fastboot devices
<myserialnumber-not-publishing-here> fastboot
The exact procedure I followed:
nexus: connected via usb to laptop
nexus: turned on in fastboot mode (hold volume-down + switch)
laptop:
Code:
#fastboot devices
<myserialnumber-not-publishing-here> fastboot
laptop:
Code:
#fastboot oem unlock -s 0a6748e5
...
(bootloader) Unlocking bootloader...
(bootloader) erasing userdata...
(bootloader) erasing userdata done
(bootloader) erasing cache...
(bootloader) erasing cache done
(bootloader) Unlocking bootloader done!
OKAY [ 36.001s]
finished. total time: 36.001s
nexus: choosen to unlock the bootloader (Yes)
Cannot remember if reboot was requested, if yes i did it
nexus: choosen recovery mode (and stay there)
Code:
# fastboot devices
<myserialnumber-not-publishing-here> fastboot
Code:
# fastboot flash recovery recovery-clockwork-6.0.4.4-deb.img
sending 'recovery' (9108 KB)...
OKAY [ 0.291s]
writing 'recovery'...
OKAY [ 0.348s]
finished. total time: 0.639s
To that point I faced the fact that to continue I should have copied the superuser utility before, and rebooted with the hope to be able to copy it on the device and continue from there on. What has been proven false: I'm now stuck on the bouncing circles, any experiment to hold down the 2/3 buttons in every combinations led to nothing, and "fastboot devices" shows nothing.
only positive point, a little hope: it shows a vendor and product ID via usb:
Code:
# lsusb
Bus 003 Device 027: ID 18d1:4ee1 Google Inc. Nexus 4 / 10
Please help! :crying:
Can you go to recovery?
Edit...
You can turn it off by pressing power+volume down, same for going to fastboot/recovery...
In recovery you can flash via adb sideload...
teddy0209 said:
Can you go to recovery?
Edit...
You can turn it off by pressing power+volume down, same for going to fastboot/recovery...
In recovery you can flash via adb sideload...
Click to expand...
Click to collapse
Thank you for the tip. At first, apparently it was not working, I hadn't written that message in such a panic, otherwise. I said myself: another guy, expert on the subject is saying this... must retry again. Worked.
I fully recovered the device by flashing it under windows with the Nexus Root Toolkit, and was able to definitely root it by following a more updated guide for my linux habitat.
Given that, as a newcomer I'm not supposed to post any link, I'll give easy directions (searchable through google) to other panicked newbies like myself.
Part1: the recovery issue (windows)
The communication under windows isnt' that easy, due to the difficult coexistence/conflict between mtp an adb drivers. For the purpose of flashing we need adb drivers. The best way, shamingly overlooked by me, is to read and try (possibly understanding the concept behind) step1...step4 accessible by mean of the large button in the main windows of root toolkit.
Part2: rooting succesfully (inux)
I found a functional guide, with working links, kindly offered by Gregory Schier. Had I followed that one from the start, the process had gone smooth at first shot.
Let me add, for the linux addicted, a reference to the file-transfer-via-usb-cable topic. In my case it was easy and quick after the very short explanation on MTP found in gentoo wiki.
Thank you for your support :good:
Good for you!!!
There are actually many ways to root our device ,specially with unlocked bootloader...
I just used fatboot OEM unlock I find it easier and most definitely safer toolkits work 99.999 % of the time but when they don't you got yourself a mess
Sent from my Nexus 7 using Tapatalk
A couple days ago, I was browsing the internet, then my Nexus 7 2013 suddenly froze. I did a reboot, but it got stuck on the boot animation. So, since it wasn't booting back up, I tried to load from one of my old backups. I managed to get the back up to work, however I needed to download the 4.4.2 update OTA through TWRP. It never officially said it finished, but I restarted the tablet and it's been stuck on the Google screen. I've went to fastboot, but it wont let me into TWRP recovery since it only loads the Google screen. I've also tried this ( http://www.androidbeat.com/2013/11/flash-factory-image-nexus-device/#.U0o0z3nn_0x ) and it didn't work.
When I try to reset through WugFresh, I've flashed KRT16S 4.4 and KOT49H 4.4.2, and and I get
Code:
sending 'bootloader' (3911 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.638s
archive does not contain 'boot.sig'
error: out of memory
I've also tried a few other ways of restoring to factory settings but nothing has worked :crying:
Any help is much appreciated!
I deleted my OS on my nexus... Oops? what I did is I did a ADB Sideload custom rom but if you can't get into twrp you are screwed. Maybe send it to Asus or return it if it is under warranty and get a new one. Just remember don't listen to me, in just a child on a tablet at night trying to unpack full posting privileges.
Sent from my Nexus 7 using XDA Premium 4 mobile app
Any other suggestions..?
Couldn't you go into your bootloader, erase your recovery using ADB, and then flash it?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
codemonkey98 said:
Couldn't you go into your bootloader, erase your recovery using ADB, and then flash it?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I don't think I've tried that yet. Do you have a link on how to do it? I'm not all that experienced...
PieceofSlice said:
I don't think I've tried that yet. Do you have a link on how to do it? I'm not all that experienced...
Click to expand...
Click to collapse
A tutorial can be found here. The tutorial guides you to get the Nexus 7 (2012) original files, please get the actual Nexus 7 (2013) files.
codemonkey98 said:
A tutorial can be found here. The tutorial guides you to get the Nexus 7 (2012) original files, please get the actual Nexus 7 (2013) files.
Click to expand...
Click to collapse
Alright, thanks I'll try this as soon as I get home. Though, when it says to type "fastboot flash bootloader bootloader-grouper-3.34.img" will I just be able to substitute the new 4.4.2 factory image stuff instead of the older? Also, does it matter that I can't set my Nexus into debugging mode?
PieceofSlice said:
Alright, thanks I'll try this as soon as I get home. Though, when it says to type "fastboot flash bootloader bootloader-grouper-3.34.img" will I just be able to substitute the new 4.4.2 factory image stuff instead of the older? Also, does it matter that I can't set my Nexus into debugging mode?
Click to expand...
Click to collapse
Yes you will need to replace by the "bootloader-grouper-3.34.img" by the name of the img in your device archive.
For my Razorg / deb (The LTE version) it will be :
Code:
fastboot flash bootloader bootloader-deb-04.02.img
and
Code:
fastboot -w update image-razorg-kot49h.zip
And for the Razor / flo (Wifi version) it will be :
Code:
fastboot flash bootloader bootloader-flo-flo-04.02.img
and
Code:
fastboot -w update image-razor-kot49h.zip
For reminder, factory images can be found there : https://developers.google.com/android/nexus/images?hl=FR#razor
Debugging mode / ADB is not nessesary until you write the bootloader in fastboot mode
But don't forget to install drivers, except if you already do this step
I hope i helped you.
PieceofSlice said:
Alright, thanks I'll try this as soon as I get home. Though, when it says to type "fastboot flash bootloader bootloader-grouper-3.34.img" will I just be able to substitute the new 4.4.2 factory image stuff instead of the older? Also, does it matter that I can't set my Nexus into debugging mode?
Click to expand...
Click to collapse
You mustn't flash grouper bootloader on flo/deb!
Only the bootloader that belongs to your firmware.
Yet I'm not sure if your USB driver is installed properly.
Are you 100% sure it is?
that link is great!...
Don't worry you are not screwed...just follow the link the person above posted about how to hard reset your nexus device. Since you have a 2013 nexus just make sure that you download the correct nexus image and make sure you flash the correct files and you will be fine. I have used that same tutorial on my nexus 7 2013 flo and deb to fix issues.
Trust me it will work...
-droidshadow
codemonkey98 said:
A tutorial can be found here. The tutorial guides you to get the Nexus 7 (2012) original files, please get the actual Nexus 7 (2013) files.
Click to expand...
Click to collapse
When following the tutorial, I type in "fastboot erase boot." However, when I do that it gives me this error...
Code:
C:\android-sdk\platform-tools>fastboot devices
04988e98 fastboot
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
I have the SDK installed correctly and everything in the correct spot, right?
PieceofSlice said:
When following the tutorial, I type in "fastboot erase boot." However, when I do that it gives me this error...
Code:
C:\android-sdk\platform-tools>fastboot devices
04988e98 fastboot
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
I have the SDK installed correctly and everything in the correct spot, right?
Click to expand...
Click to collapse
The files in folder look fine now
Did you update your SDK manager to the newest version? (Especially sources regarding API 18 and 19 are important). Move the firmware files elsewhere before, because by major updates whole platform-tools folder will be replaced.
Try to use different USB port on your PC. Once when you are in fastboot mode, does this command work?
Code:
fastboot reboot-bootloader
tetakpatalked from Nexus 7
Well, just my 2 cents... I read somewhere else on this forum from someone having the same issue that replacing the cable he used actually did the trick for him. You might try that. Won't hurt..
tetakpatak said:
The files in folder look fine now
Did you update your SDK manager to the newest version? (Especially sources regarding API 18 and 19 are important). Move the firmware files elsewhere before, because by major updates whole platform-tools folder will be replaced.
Try to use different USB port on your PC. Once when you are in fastboot mode, does this command work?
Code:
fastboot reboot-bootloader
tetakpatalked from Nexus 7
Click to expand...
Click to collapse
I haven't updated the SDK. So when I do, just be sure to move the image files and whatnot, and then put them back after the update, correct?
I'll be doing this later
PieceofSlice said:
I haven't updated the SDK. So when I do, just be sure to move the image files and whatnot, and then put them back after the update, correct?
I'll be doing this later
Click to expand...
Click to collapse
Yes just move your firmware files (bootloader and image.zip) out of the folder.
Updating is easy, double-click SDK manager application (you will see it as soon as you open SDK folder) and there you can choose what to update. You just need an internet connection.
tetakpatalked from Nexus 7
i am intrigued to see if this person was able to fix his tablet...
I think that all the suggestions above are very good ones. Making sure he has the most updated software...
Make sure he tries another usb cable or make sure you are using the stock usb cable.
And trying another usb port...
However from this fastboot devices output it did show that his device was connected which i don't think would happen with a default usb cable.
Okay so here is what i think may be causing the problem.
I think you need to unlock your bootloader before you can erase it. Try following this tutorial -> http://forum.xda-developers.com/showthread.php?t=1907796
You have to unlock it before you can erase the bootloader. So you need to do:
command 1: adb reboot-bootloader
command 2: fastboot oem unlock
then you can do:
command 3: fastboot erase boot
try that and see if that helps....
If that does not work then try flashing the new bootloader over the old one.
I hope this has been helpful.
Don't give up...
-droidshadow
LOL, good point @droidshadow!
Hey, @PieceofSlice, is your bootloader possibly still locked? Please make photo of the text in bootloader mode on bottom left and post screenshot of it.
tetakpatalked from Nexus 7
droidshadow said:
i am intrigued to see if this person was able to fix his tablet...
I think you need to unlock your bootloader before you can erase it. Try following this tutorial -> http://forum.xda-developers.com/showthread.php?t=1907796
You have to unlock it before you can erase the bootloader. So you need to do:
command 1: adb reboot-bootloader
command 2: fastboot oem unlock
then you can do:
command 3: fastboot erase boot
try that and see if that helps....
-droidshadow
Click to expand...
Click to collapse
I'm pretty sure my bootloader is unlocked, my tablet has the unlocked padlock at the Google screen. I'll take your advice and try a new cord too
droidshadow said:
i am intrigued to see if this person was able to fix his tablet...
You have to unlock it before you can erase the bootloader. So you need to do:
command 1: adb reboot-bootloader
command 2: fastboot oem unlock
then you can do:
command 3: fastboot erase boot
try that and see if that helps....
If that does not work then try flashing the new bootloader over the old one.
-droidshadow
Click to expand...
Click to collapse
So I actually tried to do this because, even though I updated the Android SDK, when I typed in "fastboot erase boot", it basically froze on "erasing bootloader." When I tried the first command, "adb reboot-bootloader", it said
Code:
C:\android-sdk\platform-tools>adb reboot-bootloader
error: device not found
So I take it I have a problem with ADB or something?
There are two generally different modes by using Android Debugging Bridge:
1. ADB (device booted in OS or recovery)
2. FASTBOOT (device in bootloader mode)
When I tried the first command, "adb reboot-bootloader", it said
Code:
C:\android-sdk\platform-tools>adb reboot-bootloader
error: device not found
So I take it I have a problem with ADB or something?
Click to expand...
Click to collapse
So, if you have tried this command above when your device was in bootloader mode, it was wrong command, as the command should have started with "fastboot...." instead of "adb..."
If the device was booted in OS, this command would have been correct and such response could have two reasons:
* USB debugging was not enabled
* drivers are not installed properly
After updating SDK manager, it is always highly recommended to check if the driver still works.
PieceofSlice said:
when I typed in "fastboot erase boot", it basically froze on "erasing bootloader."
Click to expand...
Click to collapse
Careful, mate, I hope you didn't try to erase your bootloader? That would have fatal results. Actually "boot" means kernel! As long as your bootloader is there = your tab will be fine.
By flashing a factory image the order of doing things is
* erase all (kernel, system, userdata etc)
* flash new bootloader
* reboot bootloader
* flashing whole factory image zip file
tetakpatalked from Nexus 7