Hello all,
PROBLEM
I while ago I had flashed my tattoo with a ROM that came with ROMmanager (wich is able to flash a custom recovery within Android) and the result was that my recovery was corupted and I couldn't flash another rom anymore, since I have a locked SPL.
POSSIBLE SOLUTION
What you can try is to download the latest RUU for your device and try to update the tattoo. However, I know that alot of people will get the error code 170 or 171: USB not connected. Don't panic, I have found after so many days of searching the solution to this problem.
WHAT WILL YOU NEED ?
The correct RUU for your device forum.xda-developers.com/showthread.php?t=591746"]
Procmon, this is a Process Monitor. You will need this to extract the rom.zip file from the RUU. technet.microsoft.com/en-us/sysinternals/bb896645.aspx"]
The android SDK and ADB set up correctly ( just search it on Google, and you'll find it).
LETS GET STARTED
The first thing you'll need to do is to open your prefered RUU you just downloaded from the link above, and wait till it says "welcome to the htc update..."
Just click next once, and leave the RUU open.
NOTE: The RUU can't be minimalized, so I sugest to slide it down to the taskbar.
Next, open the Procmon application, it will show you all open tasks (don't start searching like a fool, there are too many processes running to find the file we're searching for!).
Still in the Procmon, search in the for a filter button (the sixth button, white with a bleu thing above it), and click on it, now there will popup a screen.
Change the first tab (Architecture) to Path, and the seccond one (is) to contains, then in the box type rom.zip, and leave the Include tab how it is.
Now press add, and then press apply and ok. And search to one of the path's that ends with rom.zip in the list.
Right-click on it, and select Jump To, now you will see the rom.zip file in a temporary windows folder. Copy the rom to whereever you want (e.g. on your desktop) and close the RUU and Process Monitor.
Now, we have found and extracted the original rom that comes with the tattoo, so we're ready to flash this rom manually to our tattoo:
Open up command prompt, and cd to adb (where you have installed the SDK).
Now connect the tattoo to your pc and make sure its recognized under ADB Devices in device manager in windows.
Go back to the command prompt, and type
Code:
adb devices
If ADB is setup how it should, then you'll see the tattoo there (a long number)
Now type:
Code:
adb shell
adb reboot oem-78
The tattoo is now going to reboot in RUU mode, so we can do fastboot commands. (You will see only HTC logo on the tattoo)
Copy the rom.zip you extracted from the RUU to the tools folder of your SDK.
Now type:
Code:
fastboot flash zip rom.zip
(rom.zip is the name of your extracted rom, if you renamed it, then use the name of your rom).
Wait for the flashing procedure to finish, you'll see some message of completed or done or something, and unplug your tattoo, it should be in the bootloader screen (with 3 skateboards) and in the middle you should see RUU in orange.
Reboot your device, and hold the HOME + END button till the tattoo screen comes up, and wait till you see a screen with an exlimation mark, now shortly press on the HOME+END butten and you should be able to see the recovery menu now!
OPTIONAL
Redoo the 'root the tattoo in one click', and you'll get a custom recovery and root acces. IF YOU DO SO, I STRONGLY RECOMMEND YOU TO FLASH ANOTHER CUSTOM RECOVERY TO THE TATTOO, JUST SEARCH ONE ON THE FORUM HERE AND YOU'LL ALSO FIND HOW TO DO SO TROUGH ADB COMMANDS.
Once you have a custom recovery, you can flash rom's again from the recovery.
Hope this tread was helpfull !
Very usefull tnx
Sent from my Tattoo using XDA App
Now I'm even less afraid of flashing my a.. of. :-D
Thanx man!
Sent from my Tattoo using Tapatalk
MOdel ID checl Failed
Hi ,
I am getting this error
C:\androidtools\tools>fastboot flash zip "C:\My Folder\Datas\Mobile\Tattoo\rom.z
ip"
sending 'zip' (88968 KB)... OKAY [ 12.422s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 40.079s
C:\androidtools\tools>
soulaiman said:
Hello all,
PROBLEM
I while ago I had flashed my tattoo with a ROM that came with ROMmanager (wich is able to flash a custom recovery within Android) and the result was that my recovery was corupted and I couldn't flash another rom anymore, since I have a locked SPL.
POSSIBLE SOLUTION
What you can try is to download the latest RUU for your device and try to update the tattoo. However, I know that alot of people will get the error code 170 or 171: USB not connected. Don't panic, I have found after so many days of searching the solution to this problem.
WHAT WILL YOU NEED ?
The correct RUU for your device forum.xda-developers.com/showthread.php?t=591746"]
Procmon, this is a Process Monitor. You will need this to extract the rom.zip file from the RUU. technet.microsoft.com/en-us/sysinternals/bb896645.aspx"]
The android SDK and ADB set up correctly ( just search it on Google, and you'll find it).
LETS GET STARTED
The first thing you'll need to do is to open your prefered RUU you just downloaded from the link above, and wait till it says "welcome to the htc update..."
Just click next once, and leave the RUU open.
NOTE: The RUU can't be minimalized, so I sugest to slide it down to the taskbar.
Next, open the Procmon application, it will show you all open tasks (don't start searching like a fool, there are too many processes running to find the file we're searching for!).
Still in the Procmon, search in the for a filter button (the sixth button, white with a bleu thing above it), and click on it, now there will popup a screen.
Change the first tab (Architecture) to Path, and the seccond one (is) to contains, then in the box type rom.zip, and leave the Include tab how it is.
Now press add, and then press apply and ok. And search to one of the path's that ends with rom.zip in the list.
Right-click on it, and select Jump To, now you will see the rom.zip file in a temporary windows folder. Copy the rom to whereever you want (e.g. on your desktop) and close the RUU and Process Monitor.
Now, we have found and extracted the original rom that comes with the tattoo, so we're ready to flash this rom manually to our tattoo:
Open up command prompt, and cd to adb (where you have installed the SDK).
Now connect the tattoo to your pc and make sure its recognized under ADB Devices in device manager in windows.
Go back to the command prompt, and type
Code:
adb devices
If ADB is setup how it should, then you'll see the tattoo there (a long number)
Now type:
Code:
adb shell
adb reboot oem-78
The tattoo is now going to reboot in RUU mode, so we can do fastboot commands. (You will see only HTC logo on the tattoo)
Copy the rom.zip you extracted from the RUU to the tools folder of your SDK.
Now type:
Code:
fastboot flash zip rom.zip
(rom.zip is the name of your extracted rom, if you renamed it, then use the name of your rom).
Wait for the flashing procedure to finish, you'll see some message of completed or done or something, and unplug your tattoo, it should be in the bootloader screen (with 3 skateboards) and in the middle you should see RUU in orange.
Reboot your device, and hold the HOME + END button till the tattoo screen comes up, and wait till you see a screen with an exlimation mark, now shortly press on the HOME+END butten and you should be able to see the recovery menu now!
OPTIONAL
Redoo the 'root the tattoo in one click', and you'll get a custom recovery and root acces. IF YOU DO SO, I STRONGLY RECOMMEND YOU TO FLASH ANOTHER CUSTOM RECOVERY TO THE TATTOO, JUST SEARCH ONE ON THE FORUM HERE AND YOU'LL ALSO FIND HOW TO DO SO TROUGH ADB COMMANDS.
Once you have a custom recovery, you can flash rom's again from the recovery.
Hope this tread was helpfull !
Click to expand...
Click to collapse
If this post does what it says it does, it should maybe be made a sticky so that everyone who bricks their device knows EXACTLY what to do to fix it.........
This metod work,excelent
nkaderfe said:
Hi ,
I am getting this error
C:\androidtools\tools>fastboot flash zip "C:\My Folder\Datas\Mobile\Tattoo\rom.z
ip"
sending 'zip' (88968 KB)... OKAY [ 12.422s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 40.079s
C:\androidtools\tools>
Click to expand...
Click to collapse
Hmm, seems like adb can't verify the model of your phone. Try a different ROM or Reinstall the sdk tools. If that doesn't make sense, then try to recreate your goldcard, but I don't think that that would make some difference at all.
soulaiman said:
WHAT WILL YOU NEED ?
The correct RUU for your device forum.xda-developers.com/showthread.php?t=591746"]
Procmon, this is a Process Monitor. You will need this to extract the rom.zip file from the RUU. technet.microsoft.com/en-us/sysinternals/bb896645.aspx"]
The android SDK and ADB set up correctly ( just search it on Google, and you'll find it).
Click to expand...
Click to collapse
Well, the rom.zip is always located in %tmp% (Start->run->%tmp% and then enter). Search the folders and somewhere you will find the rom.zip then...procmon is a little over-engineered
nkaderfe said:
Hi ,
I am getting this error
C:\androidtools\tools>fastboot flash zip "C:\My Folder\Datas\Mobile\Tattoo\rom.z
ip"
sending 'zip' (88968 KB)... OKAY [ 12.422s]
writing 'zip'... INFOadopting the signature contained in this i
mage...
INFOsignature checking...
INFOzip header checking...
INFOzip info parsing...
INFOchecking model ID...
FAILED (remote: 41 model id check fail)
finished. total time: 40.079s
C:\androidtools\tools>
Click to expand...
Click to collapse
Then you have a vendor specific build - Vodafone? Orange? You have to flash this in order to get the flashing started...
/EDIT: Did u create a goldcard?
Getting stuck.
When I type adb shell it responds with: -exec '/system/bin/sh' failed: No such file or directory <2> -
adb reboot oem-78
fastboot flash zip rom.zip
<waiting for device>
My phone is plugged in but doesn't want to boot past tattoo screen.
Plz help if you know the problem.
timlambo said:
Getting stuck.
When I type adb shell it responds with: -exec '/system/bin/sh' failed: No such file or directory <2> -
adb reboot oem-78
fastboot flash zip rom.zip
<waiting for device>
My phone is plugged in but doesn't want to boot past tattoo screen.
Plz help if you know the problem.
Click to expand...
Click to collapse
Hi,
You have to boot your phone first in bootloader mode, to do so you have to pull out battery, put it back in, hold in the down volume button while pressing power, it wil bring you in a white screen with at the bottom three androids on skeatboards.
Hope this helps you.
soulaiman said:
Hi,
You have to boot your phone first in bootloader mode, to do so you have to pull out battery, put it back in, hold in the down volume button while pressing power, it wil bring you in a white screen with at the bottom three androids on skeatboards.
Hope this helps you.
Click to expand...
Click to collapse
I know. That is where I were. I think the problem were with my rom, found old backup om pc and restored to that, but now it is working again.
Thanks for the help.
Related
can anyone tell me if they know how to push a update through fastboot? i just did a update and nandroid isnt working, so can anyone provide help on doing a push through fastboot?
errors i get trying to re apply update.zip of jf1.5
the original rc29file? what should i do?
cmd error
Code:
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Kiefer Anderson>cd desktop
C:\Users\Kiefer Anderson\Desktop>cd fastboot
C:\Users\Kiefer Anderson\Desktop\fastboot>fastboot flashall update.zip
error: neither -p product specified nor ANDROID_PRODUCT_OUT set
C:\Users\Kiefer Anderson\Desktop\fastboot>fastboot update update.zip
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.img'
error: update package missing system.img
C:\Users\Kiefer Anderson\Desktop\fastboot>fastboot update {update.zip}
error: failed to load '{update.zip}'
C:\Users\Kiefer Anderson\Desktop\fastboot>fastboot update update.zip
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
C:\Users\Kiefer Anderson\Desktop\fastboot>fastboot update {update.zip}
error: failed to load '{update.zip}'
C:\Users\Kiefer Anderson\Desktop\fastboot>
I tried two different update files, one i added the two .txt files then it asks for the img files, i dont get it.. anyone HELP plzzzzz, if you help ill donate money to your paypal i swear
why dont you just do it through the recovery ?
To mount the sdcard in recovery type the following in adb
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
thanks to JesusFreke for figuring this out.
dpgc213 said:
why dont you just do it through the recovery ?
Click to expand...
Click to collapse
i dont have anything to connect my phone to another usb device..
im not very good at this stuff, but for some reason im stuck at the android loading screen, i think theres something wrong with the 2nd loading screen, idk what to do, i tried doing recovery with nandroid but i get an error, then i tried re apllying the update.zip file and still something wrong, im stuck and need help
so to do recovery, i do home + end button, which brings up everything right? alt stuff..
so what do i do from there, im sorry, but i fyou help me through this, ill do anything.. how do i enter those commands in the recovery?
1. fastboot doesn't work on recovery update zips. It is used on images made from nandroid backup (or img files made from building the source). In other words, fail.
2. Dev forum is not for troubleshooting.
u can mount your phone to your computer in recovery mode but using the code in my above post
dpgc213 said:
u can mount your phone to your computer in recovery mode but using the code in my above post
Click to expand...
Click to collapse
Microsoft Windows [Version 6.0.6001]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Users\Kiefer Anderson>echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mas
s_storage/lun0/file
The system cannot find the path specified.
C:\Users\Kiefer Anderson>
still cant figure it out.. im in recovery mode, i did that echo thing, but yeh..
when i had my phone working and connected, it would connect as f:/ sooo what do i do
press alt x and then type that in on the phone
dpgc213 said:
press alt x and then type that in on the phone
Click to expand...
Click to collapse
hmm didnt work, i just get a
"
/ #
"
didnt work i dont think :/
i dont see my sdcard connected, ill try again
not sure then sorry, u sure u copied exactly how it is? or maybe u hav to type su 1st, not sure tho
dpgc213 said:
not sure then sorry, u sure u copied exactly how it is? or maybe u hav to type su 1st, not sure tho
Click to expand...
Click to collapse
uhm in device manager its connected as HTC dream instead of mass usb
gonna try both thanks for helping, if i figure this out, ill be contacting you
gonna cry now
lol sh: su: not found
so su not working idk
ok i got my dads phone, gonna try re installing jf 1.5 i hope it works :/
EDIT update
im sorry to bother you guys, i just want to say thanks for trying to help, withouut you i would be no where, i might of just went in my closet and cryed myself to death..
used my dads nokia to help
thanks guys
Can i Mount Nexus s without enabling USB debugger from Phone(as I cant go past google logo on nexus s)
jashsu said:
1. fastboot doesn't work on recovery update zips. It is used on images made from nandroid backup (or img files made from building the source). In other words, fail.
2. Dev forum is not for troubleshooting.
Click to expand...
Click to collapse
So you can only use the .img files from AndroidSDK to update in fastboot? Im trying to fix an HTC G2 Vision (T-Mobile) for a friend, it doesnt boot and is NOT rooted, it will not seem to accept any official T-Mobile update or any i try to push or flash through fastboot. I have the nandroid backup images from another HTC G2 Vision (both phones stock rom) as well as the official T-Mobile updates yet they wont flash through fastboot or Hboot, ADB wont recognize it,fastboot will, i get failed to verify whole-file signature on most updates, but have gotten Main Version is older! mesage from 1 of the OTA updates i got from T-Mobile, and one that said something like failed to stat sytem/build.prop no such file or directory E:error in /tmp/sideload/package.zip (status7) everytime i boot her phone into recovery i get E:set_bootloader_message_block: emmc_read_data_fail! I thought if i could reflash bootimg or hboot or flashall i could fix it? am i wrong in this aassupmtion? I have reached out over half a dozen sites/forums for help and have not got any real help, if anyone can assist id appreciate it, u can alway pm me instead of dirtying the thread, Thank you!
C:\Users\roger>C:\AndroidSDk\tools\fastboot flash boot C:\AndroidSDK\tools\boot.img
sending 'boot' (2560 KB)...
OKAY [ 0.446s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.770s
IVXX said:
So you can only use the .img files from AndroidSDK to update in fastboot? Im trying to fix an HTC G2 Vision (T-Mobile) for a friend, it doesnt boot and is NOT rooted, it will not seem to accept any official T-Mobile update or any i try to push or flash through fastboot. I have the nandroid backup images from another HTC G2 Vision (both phones stock rom) as well as the official T-Mobile updates yet they wont flash through fastboot or Hboot, ADB wont recognize it,fastboot will, i get failed to verify whole-file signature on most updates, but have gotten Main Version is older! mesage from 1 of the OTA updates i got from T-Mobile, and one that said something like failed to stat sytem/build.prop no such file or directory E:error in /tmp/sideload/package.zip (status7) everytime i boot her phone into recovery i get E:set_bootloader_message_block: emmc_read_data_fail! I thought if i could reflash bootimg or hboot or flashall i could fix it? am i wrong in this aassupmtion? I have reached out over half a dozen sites/forums for help and have not got any real help, if anyone can assist id appreciate it, u can alway pm me instead of dirtying the thread, Thank you!
C:\Users\roger>C:\AndroidSDk\tools\fastboot flash boot C:\AndroidSDK\tools\boot.img
sending 'boot' (2560 KB)...
OKAY [ 0.446s]
writing 'boot'...
(bootloader) signature checking...
FAILED (remote: signature verify fail)
finished. total time: 0.770s
Click to expand...
Click to collapse
http://forum.xda-developers.com/forumdisplay.php?f=508
try the G2 forum
Make a new topic there
here are three replacement splash images I made for the mytouch
all you need to do is to copy the image you want to flash to your sdk tools directory and hook up your phone is fastboot mode. Turn phone off press and hold back and power and then connect usb cable and run the following command.
Code:
fastboot flash splash1 image.rgb565
just replace the word image above with the name of the file that you have and then use
Code:
fastboot reboot
enjoy new splash
im still a little confused....
What are you confused about? All it is, is a replacement splash screen. The screen that you see the first when the phone is powering up. All you do is extract to the SDK/tools folder on your computer from the android sdk that should be installed on your computer. Start the phone is fastboot like i mentioned above and the type the commands. with a more direct example say you want the middle one, once you have extracted and done the other steps (if you are unsure of above search around the forum there are steps elsewhere)
the command for the middle image is
fastboot flash splash1 badtouch.rgb565
fastboot reboot
and then that image will be your new splash screen on the device. very simple.
ha! M.J.'s BAD
you think you could make a "don't worry this mytouch has root" splash screen like the on for the g1
Haven't seen that one. Have a link?
Error
I get this error while trying to flash the boot screen
sending 'splash1' (300 KB)... FAILED (remote: not allow)
What am I doing wrong
Sounds like you still have the original locked spl. You will need to flash a unlocked spl to do this. Just look at the how to root unroot MyTouch thread. It goes over the how to.
I love the 1bad splash! Thanks!
Hi everyone i´m new to this forum. I own a Asus ME176CX and updated to official lollipop 5 from asus.com. The device is rooted and it was a little bit slow so i decided to uninstall via root uninstall some of the Bloat Apps.
The Result is ... I messed it up. I deinstalled too many apps, and it seems that i uninstall some system apps too. When my device is booting it wont stop booting and i´m only able to turn the device off.
I can get into fastboot but my recovery mode says only failed when i try to start it. I´m really new to Android and asking for some advise here. I tried a lot of this workarounds here but nothing worked for me
#pleasehelpthenoob
Thanks in Advance
Waido1981 said:
Hi everyone i´m new to this forum. I own a Asus ME176CX and updated to official lollipop 5 from asus.com. The device is rooted and it was a little bit slow so i decided to uninstall via root uninstall some of the Bloat Apps.
The Result is ... I messed it up. I deinstalled too many apps, and it seems that i uninstall some system apps too. When my device is booting it wont stop booting and i´m only able to turn the device off.
I can get into fastboot but my recovery mode says only failed when i try to start it. I´m really new to Android and asking for some advise here. I tried a lot of this workarounds here but nothing worked for me
#pleasehelpthenoobA
Thanks in Advance
Click to expand...
Click to collapse
If you want lollipop, take it to warranty. If you don't mind getting stuck on kitkat (after lollipop update you can run windows or linux on this tablet, and maybe use custom rom if anyone will make it using my idea), just say and I will write you steps how to get kitkat back.
Waido1981 said:
Hi everyone i´m new to this forum. I own a Asus ME176CX and updated to official lollipop 5 from asus.com. The device is rooted and it was a little bit slow so i decided to uninstall via root uninstall some of the Bloat Apps.
The Result is ... I messed it up. I deinstalled too many apps, and it seems that i uninstall some system apps too. When my device is booting it wont stop booting and i´m only able to turn the device off.
I can get into fastboot but my recovery mode says only failed when i try to start it. I´m really new to Android and asking for some advise here. I tried a lot of this workarounds here but nothing worked for me
#pleasehelpthenoob
Thanks in Advance
Click to expand...
Click to collapse
Did you manage to work it out as I'm in the same boat at the moment - I can get to fastboot and can power on and off but stuck at boot! recovery efforts just show dead android and "Error"!
Anyone?
Cheers
noggin-the-nog said:
Did you manage to work it out as I'm in the same boat at the moment - I can get to fastboot and can power on and off but stuck at boot! recovery efforts just show dead android and "Error"!
Anyone?
Cheers
Click to expand...
Click to collapse
yeah my girlfriend has the same tablet. I took a backup with girlfriends device with fbrl and get it on my device. Just had to change settings and accounts and everything works well again.
Hi Everyone, I'm new here too.
I have the same problem in this topic.
I can use fastboot mode Only, I can't use adb mode, and the bootloader is locked.
when i was trying to install original firmware with this command:
fastboot update update.zip
I get this messege:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
I need solution for this.
I haven't problem to installing any operating system, like Windows, Ubuntu, Tizen, Android x86, or other.
Please, I really need help, more than five months i am looking for a way out from this problem but it's all failed, because the boot loader was locked.
Any help would be very appreciated.
Thank you in advance.
Hi
Doesn't anybody have any ideas to help me ?
Maybe I must unlock bootloader to solve my problem.
But how I can do that ?
Waido1981 said:
Hi everyone i´m new to this forum. I own a Asus ME176CX and updated to official lollipop 5 from asus.com. The device is rooted and it was a little bit slow so i decided to uninstall via root uninstall some of the Bloat Apps.
The Result is ... I messed it up. I deinstalled too many apps, and it seems that i uninstall some system apps too. When my device is booting it wont stop booting and i´m only able to turn the device off.
I can get into fastboot but my recovery mode says only failed when i try to start it. I´m really new to Android and asking for some advise here. I tried a lot of this workarounds here but nothing worked for me
#pleasehelpthenoob
Thanks in Advance
Click to expand...
Click to collapse
For people with access to bootloader:
1- Download .17 and extract it on desktop
2- go to META-INF\com\google\android\updater-script and open it with notepad ++, and delete first 2 lines
3- compress it and rename it to update.zip and place it in adb folder (for me its c:\\adb)
4- shutdown the tablet and press (power and vol-) to go to bootloader.
5- write on adb "adb push update.zip /sdcard/" wait until it finishes (dont leave bootloader)
6- Download Temp Recovery: www.androidfilehost.com/?fid=24052804347782876
7- On windows, open temp recovery program, and say "ACCEPT", and press 2 then press T4 and it should boot to the temp recovery on the tablet.
8- then install the update.zip, and then format cache and dalvik, then reboot and it should be fixed.
//////////////////////////////////////////////////////
//////////////////////////////////////////////////////
For people without access to bootloader:
1- Download .17 and extract it on desktop
2- go to META-INF\com\google\android\updater-script and open it with notepad ++, and delete first 2 lines
3- compress it and rename it to update.zip and place it in adb folder (for me its c:\\adb)
4- copy droidboot.img from .17 and put in in adb folder
5- go to fastboot and write "fastboot boot droidboot.img" it should boot to bootlaoder *do it at least 10 times because sometimes, the tablet boots to software and not bootloader*
6- if you are in bootloader then, Download Temp Recovery: www.androidfilehost.com/?fid=24052804347782876
7- After downloading, On windows, open temp recovery program, and say "ACCEPT", and press 2 then press T4 and it should boot to the temp recovery on the tablet.
8- then install the update.zip, and then format cache and dalvik, then reboot and it should be fixed.
//////////////////////////////
Good Luck! :laugh:
//////////////////////////////
Ruben Craveiro said:
For people without access to bootloader:
1- Download .17 and extract it on desktop
......
7- After downloading, On windows, open temp recovery program, and say "ACCEPT", and press 2 then press T4 and it should boot to the temp recovery on the tablet.
Click to expand...
Click to collapse
Hi Ruben,
What do you mean from step 1 ? Where can I find the (.17) to i can download it ?
When I perform step 7, it gave me error.
Overall, I had sent my problem to Asus support and their interaction was bad enough to hates them.
My problem has now ten months I have not found a solution, and the company asking me to send the device to America and I'm outside America.
I promise you I will avoid buying Asus devices from today onwards.
Thank you for trying to help us.
Venting said:
Hi Ruben,
What do you mean from step 1 ? Where can I find the (.17) to i can download it ?
When I perform step 7, it gave me error.
Overall, I had sent my problem to Asus support and their interaction was bad enough to hates them.
My problem has now ten months I have not found a solution, and the company asking me to send the device to America and I'm outside America.
I promise you I will avoid buying Asus devices from today onwards.
Thank you for trying to help us.
Click to expand...
Click to collapse
Did you manage to boot into the temp TWRP recovery or is that not working either?
lambdadroid said:
Did you manage to boot into the temp TWRP recovery or is that not working either?
Click to expand...
Click to collapse
Hello lambdadroid,
No, It's not work.
Venting said:
Hello lambdadroid,
No, It's not work.
Click to expand...
Click to collapse
You said you have access to fastboot though? Then you should also be able to boot into the temp recovery (e.g. TWRP)
lambdadroid said:
You said you have access to fastboot though? Then you should also be able to boot into the temp recovery (e.g. TWRP)
Click to expand...
Click to collapse
OK ..
I don't flashed the TWRP Recovery, and I can't get into fastboot / droidboot mode.
But when I press on this buttons (Volume up + Volume down + and Power) while booting, the device stopped on the ASUS logo screen, and in this status my PC connected with my Tablet device, and I can use fastboot commands, no thing other.
I can't use the ADB commands.
Also, When I tried flashing the firmware with ASUS Flash Tool, or CMD shell, I got the same message: FAILED (remote failure).
When I was trying to install the original firmware through CMD Shell with this command: "fastboot flash update update.zip"
I got this message:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
When I tried with IntelAndroid-FBRL-07-24-2015 to flash TWRP or CWM Recovery, I got the error messages such as:
FAILED (data transfer failure (Unknown error))
FAILED (command write failed (No such device or address))
FAILED (command write failed (Unknown error))
I can't write anything to the device, That's everything.
I think i must unlock the bootloader to solve my problem.
But how do I do that ?
Venting said:
OK ..
I don't flashed the TWRP Recovery, and I can't get into fastboot / droidboot mode.
But when I press on this buttons (Volume up + Volume down + and Power) while booting, the device stopped on the ASUS logo screen, and in this status my PC connected with my Tablet device, and I can use fastboot commands, no thing other.
I can't use the ADB commands.
Also, When I tried flashing the firmware with ASUS Flash Tool, or CMD shell, I got the same message: FAILED (remote failure).
When I was trying to install the original firmware through CMD Shell with this command: "fastboot flash update update.zip"
I got this message:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
When I tried with IntelAndroid-FBRL-07-24-2015 to flash TWRP or CWM Recovery, I got the error messages such as:
FAILED (data transfer failure (Unknown error))
FAILED (command write failed (No such device or address))
FAILED (command write failed (Unknown error))
I can't write anything to the device, That's everything.
I think i must unlock the bootloader to solve my problem.
But how do I do that ?
Click to expand...
Click to collapse
What you're saying doesn't make much sense. How did you actually mess up your tablet?
Please also tell me the following:
- What happens if you power on the tablet normally?
- What happens if you power on the tablet using Vol+ and the power button?
- What happens if you power on the tablet using Vol- and the power button?
Unlocking the bootloader is not possible on this device and it wouldn't help you anyway if you can't get into fastboot (the droidboot screen). As far as I know the fastboot screen you can enter with Vol+ and Vol- and the power button is pretty much useless, you need the droidboot screen to recover your tablet.
lambdadroid said:
What you're saying doesn't make much sense. How did you actually mess up your tablet?
Please also tell me the following:
- What happens if you power on the tablet normally?
- What happens if you power on the tablet using Vol+ and the power button?
- What happens if you power on the tablet using Vol- and the power button?
Unlocking the bootloader is not possible on this device and it wouldn't help you anyway if you can't get into fastboot (the droidboot screen). As far as I know the fastboot screen you can enter with Vol+ and Vol- and the power button is pretty much useless, you need the droidboot screen to recover your tablet.
Click to expand...
Click to collapse
If I press on the power button normally
Or I press on Volume up button, and Power button
Or I press on Volume down button, and Power button
The result is the same, It's a red line is showing on screen bottom, then the device stops working.
You can see this Picture here
Venting said:
If I press on the power button normally
Or I press on Volume up button, and Power button
Or I press on Volume down button, and Power button
The result is the same, It's a red line is showing on screen bottom, then the device stops working.
You can see this Picture here
Click to expand...
Click to collapse
How did you actually mess up your tablet?
I don't think you'll have many options to repair your tablet at this point. You could have luck if you have a powered OTG hub, by booting something like Linux and flashing the necessary stuff back to the internal storage, although depending on how much you messed up, that may not make things better. The other option is sending it in to ASUS.
Venting said:
Hi Ruben,
What do you mean from step 1 ? Where can I find the (.17) to i can download it ?
When I perform step 7, it gave me error.
Overall, I had sent my problem to Asus support and their interaction was bad enough to hates them.
My problem has now ten months I have not found a solution, and the company asking me to send the device to America and I'm outside America.
I promise you I will avoid buying Asus devices from today onwards.
Thank you for trying to help us.
Click to expand...
Click to collapse
what i mean with .17 is the software (first lollipop release)
you can get it here: http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/UL-K013-WW-12.10.1.17_KK-user.zip
and to run the temp recovery make sure you have access to bootloader and have all drivers installed, if your computers says something about adb drivers for bootloader add these drivers so that it works: http://dlcdnet.asus.com/pub/ASUS/EeePAD/ME176C/ADB_driver.zip if you still cant acces is because you did not installed properly all the needed drivers. I wish u luck.
---------- Post added at 08:49 PM ---------- Previous post was at 08:44 PM ----------
[/COLOR]
Venting said:
If I press on the power button normally
Or I press on Volume up button, and Power button
Or I press on Volume down button, and Power button
The result is the same, It's a red line is showing on screen bottom, then the device stops working.
You can see this Picture here
Click to expand...
Click to collapse
if you cant access bootloader or fastboot the only way to get it back, is to have a otg powered hub, and run uefi, and then boot linux and then reinstall the android partitions. (im very newbie at this so i cant tell u much about it)
---------- Post added at 09:00 PM ---------- Previous post was at 08:49 PM ----------
Venting said:
OK ..
I don't flashed the TWRP Recovery, and I can't get into fastboot / droidboot mode.
But when I press on this buttons (Volume up + Volume down + and Power) while booting, the device stopped on the ASUS logo screen, and in this status my PC connected with my Tablet device, and I can use fastboot commands, no thing other.
I can't use the ADB commands.
Also, When I tried flashing the firmware with ASUS Flash Tool, or CMD shell, I got the same message: FAILED (remote failure).
When I was trying to install the original firmware through CMD Shell with this command: "fastboot flash update update.zip"
I got this message:
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
When I tried with IntelAndroid-FBRL-07-24-2015 to flash TWRP or CWM Recovery, I got the error messages such as:
FAILED (data transfer failure (Unknown error))
FAILED (command write failed (No such device or address))
FAILED (command write failed (Unknown error))
I can't write anything to the device, That's everything.
I think i must unlock the bootloader to solve my problem.
But how do I do that ?
Click to expand...
Click to collapse
well you have made some stuff wrong, BUT i think you can get it back, first of all its not supposed for you to actually install twrp or cwm, and you need this file: (droidboot.img) https://drive.google.com/file/d/0B3h_JptTNZeeRjdXdE1rWlNLYnM/view?usp=sharing
and place it in c:\\adb and then do fastboot boot droidboot.img and then it should boot to the bootloader if it doesnt, then do it again and again until it does.. (you need to do it several times to make it work, at least thats how i got out of bootloop), then in the bootloader you have access to adb commands so temp recovery should be working, if it still doesnt then it means it needs the adb drivers for the bootloader, after u loaded twrp recovery load .17 update(place the update in microsd, or adb push update.zip /sdcard/) and it should work
lambdadroid, Ruben Craveiro
Thank you guys so much for trying help me.
I tried everything except OTG powered hub.
I will try with OTG powered hub, and I hope solves my problem.
Thank you for everything.
Ruben Craveiro said:
For people with access to bootloader:
1- Download .17 and extract it on desktop
2- go to META-INF\com\google\android\updater-script and open it with notepad ++, and delete first 2 lines
3- compress it and rename it to update.zip and place it in adb folder (for me its c:\\adb)
4- shutdown the tablet and press (power and vol-) to go to bootloader.
5- write on adb "adb push update.zip /sdcard/" wait until it finishes (dont leave bootloader)
6- Download Temp Recovery:
7- On windows, open temp recovery program, and say "ACCEPT", and press 2 then press T4 and it should boot to the temp recovery on the tablet.
8- then install the update.zip, and then format cache and dalvik, then reboot and it should be fixed.
//////////////////////////////////////////////////////
//////////////////////////////////////////////////////
For people without access to bootloader:
1- Download .17 and extract it on desktop
2- go to META-INF\com\google\android\updater-script and open it with notepad ++, and delete first 2 lines
3- compress it and rename it to update.zip and place it in adb folder (for me its c:\\adb)
4- copy droidboot.img from .17 and put in in adb folder
5- go to fastboot and write "fastboot boot droidboot.img" it should boot to bootlaoder *do it at least 10 times because sometimes, the tablet boots to software and not bootloader*
6- if you are in bootloader then, Download Temp Recovery
7- After downloading, On windows, open temp recovery program, and say "ACCEPT", and press 2 then press T4 and it should boot to the temp recovery on the tablet.
8- then install the update.zip, and then format cache and dalvik, then reboot and it should be fixed.
//////////////////////////////
Good Luck! :laugh:
//////////////////////////////
Click to expand...
Click to collapse
Hello
I tried these two methods to recover my unrooted Memo tab. The push method doesn't do anything and the second method says "wating for device"
A little background info on how I got here. The tablet got stuck on the loading screen after the last OTA update. I tried to do the factory reset from the tablet but I get the following messsage, "E: Can't open /dev/block/by-name/misc"
I have also tried to load the zip file using sideload and get the following message.
E:failed to verify whole-file signature
E:signature verification failed
Not sure what else to try...any help is appreciated.
wifebeeter said:
Hello
I tried these two methods to recover my unrooted Memo tab. The push method doesn't do anything and the second method says "wating for device"
A little background info on how I got here. The tablet got stuck on the loading screen after the last OTA update. I tried to do the factory reset from the tablet but I get the following messsage, "E: Can't open /dev/block/by-name/misc"
I have also tried to load the zip file using sideload and get the following message.
E:failed to verify whole-file signature
E:signature verification failed
Not sure what else to try...any help is appreciated.
Click to expand...
Click to collapse
make sure your device is conected to pc and that it has all the drivers needed (adb drivers)...boot into bootloader and load temp recovery and flash latest version
---------- Post added at 10:10 PM ---------- Previous post was at 10:00 PM ----------
Venting said:
lambdadroid, Ruben Craveiro
Thank you guys so much for trying help me.
I tried everything except OTG powered hub.
I will try with OTG powered hub, and I hope solves my problem.
Thank you for everything.
Click to expand...
Click to collapse
you can access dnx mode(fastboot starting #1#2#3), so you can go into bootloader, heres how: get the file efilinux.efi and droidboot.img and put them in adb folder (you can get the droidboot.img on update.zip and if u look on .33 version theres a zip inside of it that its called ESP, you can find efilinux.efi from there) after doing that go into DnX mode on the tablet, and do these fastboot commands: "fastboot flash osloader efilinux.efi" and do "fastboot boot droidboot.img" and this will certainly make you boot to droidboot/bootloader and from there you can load temp recovery and flash the software, and no need for otg hub
Ruben Craveiro said:
make sure your device is conected to pc and that it has all the drivers needed (adb drivers)...boot into bootloader and load temp recovery and flash latest version
HI
I tried temporary recovery and I get the following messege.
error: closed
<waiting for device>
Click to expand...
Click to collapse
this is my firs thread D:
I'm going to teach you how to root your HTC A9S
REQUIREMENTS:
1) I have the bootloader unlocked, i dont know if is posible be root with locked bootloader
STEPS:
1) download and install magisk apk: http://magisk-manager.uptodown.com/android/descargar
2)download Boot.img patched with Magisk: https://drive.google.com/open?id=0B7kstm3RHGpkeExWQjZhbmJGdHM
3)download adb folder for flash boot.img: https://drive.google.com/file/d/0B7kstm3RHGpkNWZwVGhLNlMxOUk/view?usp=drivesdk
4)(you must have all HTC drivers in your pc: HTC Sync Manager) if you have the drivers, plug your device to the PC and copy and paste boot.img to adb folder
5)press Shift + right clic and select (open command window here / Open PowerSheld window here / open CMD here)
6)write the next line: ".\adb devices" (windows 10) / "adb devices" (windows 8.1-) (ONLY WHAT IS INSIDE THE QUOTATION MARKS)
7)if you haver the drivers properly installed your pc, the CMD looks like this: https://dl.xda-developers.com/4/2/8/5/1/9/2/Captura2.JPG?ey=ETeVFqxicI6Z6lSg7LQzoQ&ts=1506538864
8)ok, now write this: ".\adb reboot-bootloader" (windows 10) / "adb reboot-bootloader" (windows 8.1-) (ONLY WHAT IS INSIDE THE QUOTATION MARKS) your device is going to enter to white screen like this: https://dl.xda-developers.com/4/2/8/5/1/8/8/Captura.JPG?key=64lY1gzJZUOGg_uKLLNorw&ts=1506538854 and you must to select "boot download mode" (move in options with volume control and select with power button)
9)write ".\fastboot flash boot boot.img" (windows 10) / "fastboot flash boot boot.img" (windows 8.1-)" (ONLY WHAT IS INSIDE THE QUOTATION MARKS)
10)enjoy your root and magisk modules
TELL ME IF YOU WANT TO MAKE A COMPILATION OF THE BEST MODULES FOR MAGISK
THANKS TO @Captain_Throwback (Y)
PD: im sorry for my so bad english :'v im colombian
Download for ADB folder is spam
NO download available for the ADB folder, website is just a bunch of spam.
Dragon's Fedora said:
NO download available for the ADB folder, website is just a bunch of spam.
Click to expand...
Click to collapse
I share a new URL for download
Thanks
Jesus David Otero said:
I share a new URL for download
Click to expand...
Click to collapse
Yep worked great
Hi, nice, A9s root, but i think it should not be called amd but adb.
Who you have unlocked your phone? I geht this errormessagen to flash boot.img
Code:
C:\adb>fastboot.exe flash boot a9sboot.img
target reported max download size of 1185600000 bytes
sending 'boot' (10594 KB)...
OKAY [ 1.436s]
writing 'boot'...
(bootloader) HOSD CL#812859
FAILED (remote: 9 RU_SECURITY_FAIL boot and bootloader isn't BL_UNLOCKED)
linuxdep said:
Hi, nice, A9s root, but i think it should not be called amd but adb.
Who you have unlocked your phone? I geht this errormessagen to flash boot.img
Code:
C:\adb>fastboot.exe flash boot a9sboot.img
target reported max download size of 1185600000 bytes
sending 'boot' (10594 KB)...
OKAY [ 1.436s]
writing 'boot'...
(bootloader) HOSD CL#812859
FAILED (remote: 9 RU_SECURITY_FAIL boot and bootloader isn't BL_UNLOCKED)
Click to expand...
Click to collapse
Yes men, I have unlocked my bootloader and Android 6.0.1
Oh... And im Colombian, my english isn't so good :"u
and how did you unlock it?
HTCDEV webpage?
linuxdep said:
and how did you unlock it?
HTCDEV webpage?
Click to expand...
Click to collapse
Yeah men, YouTube have so much tutorial about that
I tried with this «https://youtu.be/2bevq4O-aEs» is in spanish but, the steps are simple
so a ****, now he has the phone comeback reset by the unlock ... SHEET
since I have probably read something over this.
linuxdep said:
so a ****, now he has the phone comeback reset by the unlock ... SHEET
since I have probably read something over this.
Click to expand...
Click to collapse
Yeah men, when you unlock your device, alwais is going to reset :"v
Who can read is clearly in the advantage.
Hi, yesterday i had updated magisk to my crypted phone, after reboot decrytion don't work.
I can read, "pin for decryption is correct, but i shut reset the phone" ok, so i reset my phone, but it is in loop. How can i reset to factory mode, without encryption?
Hi men, I was trying yesterday reset my device, but i couldn't; my device show this:
E: can not munt /data partition.
Error mounting /data partition
Error.
Jesus David Otero said:
this is my firs thread D:
I'm going to teach you how to root your HTC A9S
REQUIREMENTS:
1) I have the bootloader unlocked, i dont know if is posible be root with locked bootloader
STEPS:
1) download and install magisk apk: http://magisk-manager.uptodown.com/android/descargar
2)download Boot.img patched with Magisk: https://drive.google.com/open?id=0B7kstm3RHGpkeExWQjZhbmJGdHM
3)download adb folder for flash boot.img: https://drive.google.com/file/d/0B7kstm3RHGpkNWZwVGhLNlMxOUk/view?usp=drivesdk
4)(you must have all HTC drivers in your pc: HTC Sync Manager) if you have the drivers, plug your device to the PC and copy and paste boot.img to adb folder
5)press Shift + right clic and select (open command window here / Open PowerSheld window here / open CMD here)
6)write the next line: ".\adb devices" (windows 10) / "adb devices" (windows 8.1-) (ONLY WHAT IS INSIDE THE QUOTATION MARKS)
7)if you haver the drivers properly installed your pc, the CMD looks like this: https://dl.xda-developers.com/4/2/8/5/1/9/2/Captura2.JPG?ey=ETeVFqxicI6Z6lSg7LQzoQ&ts=1506538864
8)ok, now write this: ".\adb reboot-bootloader" (windows 10) / "adb reboot-bootloader" (windows 8.1-) (ONLY WHAT IS INSIDE THE QUOTATION MARKS) your device is going to enter to white screen like this: https://dl.xda-developers.com/4/2/8/5/1/8/8/Captura.JPG?key=64lY1gzJZUOGg_uKLLNorw&ts=1506538854 and you must to select "boot download mode" (move in options with volume control and select with power button)
9)write ".\fastboot flash boot boot.img" (windows 10) / "fastboot flash boot boot.img" (windows 8.1-)" (ONLY WHAT IS INSIDE THE QUOTATION MARKS)
10)enjoy your root and magisk modules
TELL ME IF YOU WANT TO MAKE A COMPILATION OF THE BEST MODULES FOR MAGISK
THANKS TO @Captain_Throwback (Y)
PD: im sorry for my so bad english :'v im colombian
Click to expand...
Click to collapse
Everything works as described. Thanks!
lol
it took me legit over 3 hours but looks like ive finally done it thank you so much
deleted
kativiti said:
deleted
Click to expand...
Click to collapse
what deleted?
Jesus David Otero said:
what deleted?
Click to expand...
Click to collapse
my post was deleted by me because isn't relevant anymore.
thats working greatly
How can i unroot it?
Hello, i bought this phone used a few years ago and it had cyanogen mod, it was working fine till about a year ago where i stopped using it for like half a year. Then borrowed it to a parent and when they started using it started malfunctioning, there was problem installing apps i think and then it just got stuck on boot saying "optimizing apps xx of 96" and it would stay like that nonstoop and it became VERY HOT. I wiped it but it gave me error when trying to install apps, and then it got stuck on boot again just like before. I did a recovery and it lets me boot now but i don't wanna risk it doing the same again so i just want to have it back to 100% stock.
Now i'm kinda a noob at this, but i do know quite a lot a bout PCs so it shouldn't be much of a problem.
I saw a guide by @alray which seemed easy enough:
"Quote:
Originally posted by @alray
HTC ONE M7_U/M7_UL - ADB PUSH & FLASH A ROM - DETAILED INSTRUCTIONS
Quote:
Prerequisites:
You need ADB and FASTBOOT on your computer,
either by installing the Android SDK or Minimal ADB and FASTBOOT
You need to know how to start a fastboot/adb command prompt:
You need TWRP recovery on your device.
We still recommend to use version 2.6.3.3 for all roms
except if another version is specified in the rom OP.
Use 2.7.1.1+ for roms that require "block:by-name" support (CM11)
You need your HTC drivers correctly installed on your PC:
Quote:
Procedure:
Make sure the ROM you want to flash is in the same folder where ADB and FASTBOOT are.
(C:\adt-bundle-windows-x86_64-<DATE>\sdk\platform-tools or C:\Program Files (x86)\Minimal ADB and Fastboot)
Connect your phone to computer using usb cable
Reboot phone in recovery mode (TWRP):
Make sure your phone is booted in TWRP main menu:
transfer the rom to your /sdcard folder:
Code:
adb push name_of_rom.zip /sdcard/
In TWRP main menu, select ''INSTALL''
Browse the installation menu and select your rom zip file inside /sdcard folder:
Swipe to confirm you want to flash the rom
Reboot phone"
But i can't find my exact phone model thus i don't know which ROM to get and where to get it.
Phone model is PN07110 (says at the back), when i go into the "about" tab on OS it just says "HTC ONE" on model. Done an Imei check and it says Customer: MOBILE DISTRIBUTION GROUP, INC. Country: US. How can i find the exact model and room for it?
Also i've checked at is S-on
Thanks in advance guys!
NickTheConqueror said:
Hello, i bought this phone used a few years ago and it had cyanogen mod, it was working fine till about a year ago where i stopped using it for like half a year. Then borrowed it to a parent and when they started using it started malfunctioning, there was problem installing apps i think and then it just got stuck on boot saying "optimizing apps xx of 96" and it would stay like that nonstoop and it became VERY HOT. I wiped it but it gave me error when trying to install apps, and then it got stuck on boot again just like before. I did a recovery and it lets me boot now but i don't wanna risk it doing the same again so i just want to have it back to 100% stock.
Now i'm kinda a noob at this, but i do know quite a lot a bout PCs so it shouldn't be much of a problem.
But i can't find my exact phone model thus i don't know which ROM to get and where to get it.
Phone model is PN07110 (says at the back), when i go into the "about" tab on OS it just says "HTC ONE" on model. Done an Imei check and it says Customer: MOBILE DISTRIBUTION GROUP, INC. Country: US. How can i find the exact model and room for it?
Also i've checked at is S-on
Thanks in advance guys!
Click to expand...
Click to collapse
To know your phone info, you'll need to use the "fastboot getvar all" command:
Install Minimal adb and fastboot on your computer and the latest htc drivers (you can install the latest drivers by installing htc sync manager from htc's website).
Once adb and the drivers are installed, connect your phone to your pc, reboot the phone in bootloader mode (hold power + volume down button until you see a white screen like this). Make sure your phone is in bootloader mode (like on the right picture, showing "FASTBOOT USB" in red. If it's bootloader mode (HBOOT in blue) use you volume up/down key to highlight the FASTBOOT option and use the power button to enter fastboot menu.
Then on your computer click the start menu ---> program ---> minimal adb and fastboot ---> minimal adb and fastboot.exe.
This will open a command window. Type "fastboot getvar all" without the quotes, hit Enter and copy paste (or screenshot) the output in your next post. Make sure to delete the IMEI and SERIALNO lines before posting.
alray said:
To know your phone info, you'll need to use the "fastboot getvar all" command:
Install Minimal adb and fastboot on your computer and the latest htc drivers (you can install the latest drivers by installing htc sync manager from htc's website).
Once adb and the drivers are installed, connect your phone to your pc, reboot the phone in bootloader mode (hold power + volume down button until you see a white screen like this). Make sure your phone is in bootloader mode (like on the right picture, showing "FASTBOOT USB" in red. If it's bootloader mode (HBOOT in blue) use you volume up/down key to highlight the FASTBOOT option and use the power button to enter fastboot menu.
Then on your computer click the start menu ---> program ---> minimal adb and fastboot ---> minimal adb and fastboot.exe.
This will open a command window. Type "fastboot getvar all" without the quotes, hit Enter and copy paste (or screenshot) the output in your next post. Make sure to delete the IMEI and SERIALNO lines before posting.
Click to expand...
Click to collapse
Done, thanks for the help man.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
NickTheConqueror said:
Done, thanks for the help man.
Click to expand...
Click to collapse
The latest RUU version for your phone is 6.15.599.101
Download these 2 files and save them in the same folder where is installed minimal adb and fastboot on your computer
https://androidfilehost.com/?fid=24052804347843559
https://androidfilehost.com/?fid=24341993505161791
Reboot your phone in bootloader (fastboot usb) menu and lunch minimal adb and fastboot.exe
In the terminal window type (commands are case sensitive):
Code:
fastboot oem rebootRUU
Your phone will reboot in RUU mode, a black screen with a silver HTC logo
Then flash the RUU with this command:
Code:
htc_fastboot flash zip PN07IMG_M7_U_K443_SENSE60_MR_HTC_LA_SPA_6.15.599.101_Radio_4T.28.3218.04_10.33E.1718.01D_release_388532_signed.zip
The flash will begin and the first part of the RUU will be flashed. After a few seconds, your phone will reboot to ruu mode (you'll get generic error message in your terminal window saying: "Failed remote: 90 Hboot pre-update! Please flush image again immediately" don't worry that's normal) and flash the second part of the RUU (should take about 10 minutes).
Once the flash is done you should see in your terminal window the message:
Code:
Successful
OKAY
Finished. Total time: XXX seconds
(The green progress bar on your phone screen might not show exactly 100% that's normal.)
If yes it's now safe to reboot your phone using this command:
Code:
fastboot reboot
Then wait for your phone to boot (first boot after flashing a RUU can take longer than usual)
If something goes wrong during the ruu flash do not reboot your phone. Rebooting the phone during an incomplete ruu flash can brick it. Make sure to have your battery fully charged before proceeding. If your bootloader is unlocked (bootloader lock/unlock status is shown in pink when in bootloader mode) you must re-lock it before flashing the RUU using the
Code:
fastboot oem lock
command.
alray said:
The latest RUU version for your phone is 6.15.599.101
Click to expand...
Click to collapse
Hey, the first file (the big one) gives me errors when i try to extract it to the folder, says the files are corrupt, i've already downloaded it twice.
NickTheConqueror said:
Hey, the first file (the big one) gives me errors when i try to extract it to the folder, says the files are corrupt, i've already downloaded it twice.
Click to expand...
Click to collapse
The file is encrypted that's why. You don't need to extract it.
alray said:
The file is encrypted that's why. You don't need to extract it.
Click to expand...
Click to collapse
Ok, i've put the rar and the other file in the Minimal ADB folder like you told me, opened Minimal ADB and put the code you said but it apparently failed. Also, some of the instructions are not very clear, this part ""Failed remote: 90 Hboot pre-update! Please flush image again immediately" don't worry that's normal) and flash the second part of the RUU (should take about 10 minutes). " How do i flash the second part?, do i input the same code again or is it automatically done?. My phone is now with a black screen and the silver HTC logo. What should i do now?, my phone is still conected to the USB and i haven't closed the bat file.
Here's the info on the bat.
BTW: on the bat it says the file is a zip apparently, but in my computer it shows as a rar file, i don't have winzip, just winrar. Could that be the problem?
UPDATE: I've input the same code again and it didn't work. The bat just updated with the same exact text as before.
New text :
C:\Program Files (x86)\Minimal ADB and Fastboot>htc_fastboot flash zip PN07IMG_M7_U_K443_SENSE60_MR_HTC_LA_SPA_6.15.599.101_Radio_4T.28.3218.04_10.33E.1718.01D_release_388532_signed.zip
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 6.15.599.101
found large-zip header, file count: 5
processing file 1/5...
sending 'zip' (42551 KB)...
OKAY [ 2.676s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 8.913s
htc_fastboot finished. total time: 9.441s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Just as before.
NickTheConqueror said:
Ok, i've put the rar and the other file in the Minimal ADB folder like you told me, opened Minimal ADB and put the code you said but it apparently failed. Also, some of the instructions are not very clear, this part ""Failed remote: 90 Hboot pre-update! Please flush image again immediately" don't worry that's normal) and flash the second part of the RUU (should take about 10 minutes). " How do i flash the second part?, do i input the same code again or is it automatically done?. My phone is now with a black screen and the silver HTC logo. What should i do now?, my phone is still conected to the USB and i haven't closed the bat file.
Here's the info on the bat.
BTW: on the bat it says the file is a zip apparently, but in my computer it shows as a rar file, i don't have winzip, just winrar. Could that be the problem?
UPDATE: I've input the same code again and it didn't work. The bat just updated with the same exact text as before.
New text :
C:\Program Files (x86)\Minimal ADB and Fastboot>htc_fastboot flash zip PN07IMG_M7_U_K443_SENSE60_MR_HTC_LA_SPA_6.15.599.101_Radio_4T.28.3218.04_10.33E.1718.01D_release_388532_signed.zip
htc_fastboot v3.0.9.2 (2015-05-29)
target rom version: 6.15.599.101
found large-zip header, file count: 5
processing file 1/5...
sending 'zip' (42551 KB)...
OKAY [ 2.676s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) rom parsing start ...
(bootloader) rom parsing finish ...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) Read zipped android_info fail
FAILED (remote: 99 unknown fail)
finished. total time: 8.913s
htc_fastboot finished. total time: 9.441s
C:\Program Files (x86)\Minimal ADB and Fastboot>
Just as before.
Click to expand...
Click to collapse
is your bootloader still unlocked?
alray said:
is your bootloader still unlocked?
Click to expand...
Click to collapse
No idea. What should i do now?
NickTheConqueror said:
No idea. What should i do now?
Click to expand...
Click to collapse
Go back in bootloader mode and check if your bootloader is unlocked or locked (first line of text in pink). If its unlocked use this command to re-lock:
fastboot oem lock
Then try again
alray said:
Go back in bootloader mode and check if your bootloader is unlocked or locked (first line of text in pink). If its unlocked use this command to re-lock:
fastboot oem lock
Then try again
Click to expand...
Click to collapse
Ok, but how do i leave out of the black screen with the silver logo?, is it safe to just power it down?
NickTheConqueror said:
Ok, but how do i leave out of the black screen with the silver logo?, is it safe to just power it down?
Click to expand...
Click to collapse
You can leave ruu mode typing
fastboot reboot-bootloader
Or using power + volume down.
Yes safe to reboot, nothing flashed yet
alray said:
You can leave ruu mode typing
fastboot reboot-bootloader
Or using power + volume down.
Yes safe to reboot, nothing flashed yet
Click to expand...
Click to collapse
Ok, did it. Now it says "Relocked" "Security Warning" in pink, is it ok now?, do i do the same as before?. Also for the second part of the flash do i have to input the same code again or what?
NickTheConqueror said:
Ok, did it. Now it says "Relocked" "Security Warning" in pink, is it ok now?, do i do the same as before?. Also for the second part of the flash do i have to input the same code again or what?
Click to expand...
Click to collapse
That's fine now go back in ruu mode using
Code:
fastboot oem rebootRUU
and once there proceed with
Code:
htc_fastboot flash zip PN07IMG_M7_U_K443_SENSE60_MR_HTC_LA_SPA_6.15.599.101_Radio_4T.28.3218.04_10.33E.1718.01D_release_388532_signed.zip
You don't need to input the command twice, the phone will reboot itself after the first part and once back in ruu mode the second part will start to flash automatically.
alray said:
That's fine now go back in ruu mode using
Code:
fastboot oem rebootRUU
and once there proceed with
Code:
htc_fastboot flash zip PN07IMG_M7_U_K443_SENSE60_MR_HTC_LA_SPA_6.15.599.101_Radio_4T.28.3218.04_10.33E.1718.01D_release_388532_signed.zip
You don't need to input the command twice, the phone will reboot itself after the first part and once back in ruu mode the second part will start to flash automatically.
Click to expand...
Click to collapse
All done, phone is now stock and working apparently (fingers crossed till i put a sim and try to install wsp xd). Thanks man, you're a genius and a real life saver!
Just another off-topic question, if i wanna sell the phone and wanna wipe out all my personal info, what do i have to do? Thanks again.
NickTheConqueror said:
All done, phone is now stock and working apparently (fingers crossed till i put a sim and try to install wsp xd). Thanks man, you're a genius and a real life saver!
Just another off-topic question, if i wanna sell the phone and wanna wipe out all my personal info, what do i have to do? Thanks again.
Click to expand...
Click to collapse
A factory reset will remove all your personal info from the phone.
It can be done from bootloader (3rd option when in the hboot menu) or from the OS: Settings --> Backup & reset --> Reset phone
You're welcome