i'm using the legend i bought in singapore which shipped with htc asia rom 1.31.707.2.....but later when i went to root it which i downgraded from 2.05.707.1 to 1.31.405.4....but now i wanna unroot it back to 1.31.707.2
i did a restore backup from rom manager in azure rom and i went back to 1.31.405.4
but when i put plug my phone to my pc the ruu wont recognize my phone...i keep getting error 170....
something funny is that i use the 1.26.707.1 rom it can read my device...but i get the error of the different version of bootloader
in the 1.31.707.2 rom normally in the second step it shows the steps you need to do normally is 3 steps like the phone will be ready for flashing the rom...
but i get this: Connect the Smartphone to the USB cable
abd dfksfsafjsdfkklsj
then later if i go on i get the error 170
i've redownloaded the same rom twice i still get this error
help pls =(
Help I have this same error (abd dfksfsafjsdfkklsj) on my htc one X, did you ever fix it?
Cheers
Fixed!
I was trying to flash the original software that came with he phone, however because I updated the phone's software I should have flashed the latest software.
Related
I have rooted my HTC hero and installed different rom onto it. Then I wanted to install stock rom to go back to orginal but accidently I have installed HTC Hero Spirit's stock rom. I found the Original HTC Hero Stock Rom but it doesnt let me install it and I get only this screen on phone. Nothing else.. Please help me out :S
postimage .org / image / 4bi9n0s49/
Get the Hero GSM stock RUU, start your phone into this and run the RUU
I did and the stock rom program gives error 170: Usb error. I use win 8 and driver is already installed. It recognise the phone as Android 1.0.
GG.Darknez said:
I did and the stock rom program gives error 170: Usb error. I use win 8 and driver is already installed. It recognise the phone as Android 1.0.
Click to expand...
Click to collapse
http://community.htc.com/na/htc-forums/android/f/17/p/2467/9420.aspx
3 seconds worth of google...
Hi everyone,
So I bought my friends HTC ONE X PLUS off him even though he had boot loop following a botched Custom ROM installation.
Stupidly I thought I could fix it.
It is an international device locked to O2. It loops at the HTC logo and allows boot into bootloader and CWM. The problem I have is that the PC doesnt even recognise it as a USB MASS (even after downloading the latest drivers - several times ) CWM wont even mount the storage.
Ive tried sideloading and everything else but no joy. The RUU I need to flash back to stock isnt out yet ? 1.17.206.1 and I cant ( as mentioned ) just dump an img/zip into the root as I cant get access to the storage. Its shows on the PC as removable storage but when I click it it asks me to insert a disk.
When I adb device/fastboot device it gives a number and says fastboot. ADB shows nothing in list of attached devices.
Any suggestions? If anyone in the UK would be happy for me to post it to them so they can have a go Id be happy to fund a beer or 2 in return
Thanks all.
mikejasonsmith said:
Hi everyone,
So I bought my friends HTC ONE X PLUS off him even though he had boot loop following a botched Custom ROM installation.
Stupidly I thought I could fix it.
It is an international device locked to O2. It loops at the HTC logo and allows boot into bootloader and CWM. The problem I have is that the PC doesnt even recognise it as a USB MASS (even after downloading the latest drivers - several times ) CWM wont even mount the storage.
Ive tried sideloading and everything else but no joy. The RUU I need to flash back to stock isnt out yet ? 1.17.206.1 and I cant ( as mentioned ) just dump an img/zip into the root as I cant get access to the storage. Its shows on the PC as removable storage but when I click it it asks me to insert a disk.
When I adb device/fastboot device it gives a number and says fastboot. ADB shows nothing in list of attached devices.
Any suggestions? If anyone in the UK would be happy for me to post it to them so they can have a go Id be happy to fund a beer or 2 in return
Thanks all.
Click to expand...
Click to collapse
The reason why the phone does not boot up anymore is that you friend probably forgot to flash the proper kernel/boot.img for the rom he installed. The kernal can't be flashed in recovery because the phone is still S-ON. In the HTC One X+ General forum you will find two tutorials with everything you need to know about unlocking/rooting/flashing using this phone. If you read both of them carefully, you should be able to solve your problem. Don't forget to press Thanks for the two guys who made these guides!!!
Also here you should be able to find the correct RUU for your CID. But since it needs relocked bootloader, you probably will have to read the to guides anyway and it is probably much easier to stay with unlocked bootloader and do the right flashing procedure.
Hello, yesterday I tried to update my Vodafone Smart Prime 6. I download my lollipop 5 update but when I tried to install the update my phone it didnt boot up anymore. I tried everything I know but it doesnt boot up anymore. and it also doesnt show as an usb device on my laptop. and when I tried adb sideload it gave an error that it failed to verify whole-file signature.
can someone help me?
I have that same phone and when I first booted up it automatically updated itself from 5.0.1 to 5.0.2.
I'm sure you uninstalled VF apps so when you updated the phone it detected that the system was modified so that's why it bricked, maybe. You are supposed to have all the VF crap before updating or you get bricked. Yeah, I know...
It could went out of battery while updating, it happens sometimes.
You probably have to take it to VF so they repair it, if you did not rooted the phone I'm sure they will fix it or give you a new one.
Sorry for any language mistakes.
Sent from my VF-895N using XDA Free mobile app
...have you tried with SUGAR tool ?
Sugar tool download
Hey guys, im newb, so excuse me while i ask for help---
So a few weeks back, i was at whatever update verizon pushed out. (not 5.1)
i decided it was a year of no updates and used your guys' guides to get me into 5.0.2... well........ VZW pushed out 5.1.1 and i'd really like to get the most updated version i can---
with that being said, im trying to roll back to 4.4.4 so i can get the verizon push update because i cant get it with my leaked lollipop version.
when i try to flash back to 4..4.4, i get the errors
"16/036/2016 10:36:40 - ERROR - Error flashing. Aborted
16/036/2016 10:36:41 - ERROR - Drivers need to be installed for connected device.
16/036/2016 10:36:41 - ERROR - You can find them in the drivers folder of Flashtool"
first it makes me choose which to identify my device as, as soon as i open flashtool- ive tried closing it, and choosing z3, with no luck- same errors.....
i go to reset my phone, get the "Upgrading, do not disconnect" screen- but then it cant read the drivers?
thats where i'm at.
giga save me
I went through the same thing last night. I google the drivers for it and then installed them and restarted the phone and made sure it was in flash mode. Once i installed the drivers for the phone manually i was able to flash the 4.4.4 and then i just got the update today and going to try and root the phone now so i can start to use it again. thanks
oh here are the drivers that i used to get mine to work. thanks
www.gizmobolt.com/2014/02/11/downlo...pack-v1-3-windows-drivers-xperia-smartphones/
I got the update all installed and now I have to figure out how to replace KingRoot with supers. But did the driver's works for you. Thanks.
I'll try to get as straight tot he point as possible.
Been using my Mobile one touch pix 7 for a little over a year and always installed Ota updates. Well I rooted the tablet not too long ago, forgot which method I used, but was working fine.
an Ota update came through and totally forgot it was rooted, and tried to install it, at which point the whole tablet got bricked.
It ended up in recovery, and I selected due to failure, to format and wipe the data.
Anyhow, The unit will stay at the boot screen for a while then show command error and then show the recovery screen, my only options are:
reboot
update from sd card
update via adb
update via memory
reboot Bootloader
power off
Well I've tried updating by downloading system images via adb, they return a verification error.
I've tried using adb side load to try to install an Ota update file I found for it, returns a verification error.
I cannot get into download mode, fast boot mode I think does not work as windows reports 3 android devices, but the mobile update software cannot see anything, and fast boot gets stuck at waiting for devices.
I suspect the tablet is for lack of a better description totally bricked and just a paperweight.
I am at a loss of what to try from this point. I'm sure wiping the data after the failed update killed it completely but not sure.
Anyone have any guidance here? I've downloaded a few images from the web I found that say they are for this tablet model, but still getting verification error.
Is there any flashing software I can get that may be able to access the tablet or can I copy a file to the scared and have it try to run an update from there. I don't care if it is rooted or not, just want to get it usable again.
I can run Mac OS, windows 10, windows 7, windows xp, or even have no issue getting a linux version going, whatever will work best for this I can use it. windows 10 I was able to manually add the drivers but windows 7 is not letting me do it the same way. I can connect via adb sideload only, no other adb functions seem to work.
I'm not a total news when it comes to custom rooms, as I have done it with another tablet, and an android car radio, but those were pretty straight forward and bootable so never ran into a brick issue yet.
I have a feeling this is toast and I hope that is not the case.
If anyone here can help out, I would appreciate it.
Thanks again....
Need help here to. Been searching with no luck. Any my issue is.
Rooted kingroot, flashed twrp with flashify and now I'm stuck on twrp. Been searching for any custom stock rom. I forgot to unlock the bootloader but I did enable usb debugging (i didn't see any oem options).
Any k 28532Jonsunf of help would be greatly appreciated.
This sorta happen to me. I rooted pixi 7 with kingroot, and was able to delete a lot of bloatware. However, when I was using lucky patcher it pretty much messed up the play store. But it was fine. I could download stuff through the Internet. But sooner or later I needed to fix it. Tryed a lot of ways but it didn't help. So I factory reset the tabletand now im stuck at the Setup Wizard. It just won't let me let me through. I thought its was over, but then I get a message saying there is an update available. So I download it and installed it. But all I get at the end is error. So now I need to flash it with stock. I tried the img. too, but it doesnt show up in the recover menu. If you found a solution please tell me
Can anyoonneee help me find a good Custom Rom for the alcatel one touch pixi 7 (9006W)? Sucks that there's not much info for this device (probably cause the device sucks lol) I'm running on lollipop 5.0.2 and am not able to get OTA update due to rooting. Unrooting didn't help. It seems only answer is custom rom but don't want to risk bricking it as I don't have a computer at home. Also, I am new to this so if anyone can share some insight, I'd be eternally grateful
P.s
It's a t mobile device but I only use it on wifi.
Am using kingroot.
Have never installed a custom rom
****ing device is 8 gigs. 1 gig Ram.
Is it possible to get Nougat?
Help meeee lol