Hello,
I, ve been reading xda for many years and had many android devices (recently SGSII for 2 years). I have quite an experience flashing roms, using recoveries etc... But this time on HTC One X+ (international) I really need XDA users help, thats why I decided to write this post.
I have a new unbranded HOX+, managed to unlock its bootloader, flash TWRP (for my version of HOX+) and from there flash superuser.zip. All worked ok (didn't produce any errors). Root is ok. But after a while, when I turned on the phone and tried to install an APK from PlayStore or read gmail - phone rebooted.
And it stills constanly do this whatever I try to do. Phone reboots whithout any change. I cannot relock bootloader, wipe, flash, install apps or copy files to phone. Every time I try to simpy use it, it just reboots with state reverted to the moment of first boot after rooting. If I leave it alone it still reboots, but after a while.
Adb and fastboot connections are available , but it looks like they are unable to commit any change. Stock rom with TWRP. I can boot to TWRP, but nothing there give a result. I can wipe, format, fix permissions, it all says operation went ok, but after a reboot, my system is unchanged.
Fastboot flashes of boot.img or recovery.img report success, but after reboot kernel / recovery aren't changed. Same with relocking bootloader, it reports that has been locked, and in bootloader mode i still see big, pink "UNLOCKED". So I also cannot flash RUU.
It seems I am unable to normally use my brand new smartphone and change anything.
Does anyone have a clue how to fix it?
Please help. I desperately need suggestions.
Thanks.
Htc ONE X+ Help!!
7virage7 said:
Hello,
I, ve been reading xda for many years and had many android devices (recently SGSII for 2 years). I have quite an experience flashing roms, using recoveries etc... But this time on HTC One X+ (international) I really need XDA users help, thats why I decided to write this post.
I have a new unbranded HOX+, managed to unlock its bootloader, flash TWRP (for my version of HOX+) and from there flash superuser.zip. All worked ok (didn't produce any errors). Root is ok. But after a while, when I turned on the phone and tried to install an APK from PlayStore or read gmail - phone rebooted.
And it stills constanly do this whatever I try to do. Phone reboots whithout any change. I cannot relock bootloader, wipe, flash, install apps or copy files to phone. Every time I try to simpy use it, it just reboots with state reverted to the moment of first boot after rooting. If I leave it alone it still reboots, but after a while.
Adb and fastboot connections are available , but it looks like they are unable to commit any change. Stock rom with TWRP. I can boot to TWRP, but nothing there give a result. I can wipe, format, fix permissions, it all says operation went ok, but after a reboot, my system is unchanged.
Fastboot flashes of boot.img or recovery.img report success, but after reboot kernel / recovery aren't changed. Same with relocking bootloader, it reports that has been locked, and in bootloader mode i still see big, pink "UNLOCKED". So I also cannot flash RUU.
It seems I am unable to normally use my brand new smartphone and change anything.
Does anyone have a clue how to fix it?
Please help. I desperately need suggestions.
Thanks.
Click to expand...
Click to collapse
Hi, you can change the recovery? TOUCH tries CWM Recovery v6.0.2.7 (CONFIRMED WORKING CHARGING MODE OFF). Try it, I recommend Android Revolution HD 7.0 + boot.img forum for 7.x find it, good luck and excuse my English.
Flash recovery with HTC One X + All-In-One Toolkit V3.0 [7-16-2013] [PERM ROOT] [Noob-Proof], sorry if I can not do much, I hope to see this more and serve you better help.
thacruz said:
Hi, you can change the recovery? TOUCH tries CWM Recovery v6.0.2.7 (CONFIRMED WORKING CHARGING MODE OFF). Try it, I recommend Android Revolution HD 7.0 + boot.img forum for 7.x find it, good luck and excuse my English.
Flash recovery with HTC One X + All-In-One Toolkit V3.0 [7-16-2013] [PERM ROOT] [Noob-Proof], sorry if I can not do much, I hope to see this more and serve you better help.
Click to expand...
Click to collapse
Hey, .
Sadly, recovery does not change. I am able to flash it through fastboot, it reports succes, but after reboot I still see my old TWRP.
Thats my issue, my phone is magical, nothing seems to affect its state
Thanks for your advice!
Htc ONE X+ Help!!
7virage7 said:
Hey, .
Sadly, recovery does not change. I am able to flash it through fastboot, it reports succes, but after reboot I still see my old TWRP.
Thats my issue, my phone is magical, nothing seems to affect its state
Thanks for your advice!
Click to expand...
Click to collapse
one more attempt, try doing it on another PC, and that the Toolkit is in C:. And that the folder has a short name, such as C :/ Toolkit or something, someone else help us, is an impressive smarthphone.
thacruz said:
one more attempt, try doing it on another PC, and that the Toolkit is in C:. And that the folder has a short name, such as C :/ Toolkit or something, someone else help us, is an impressive smarthphone.
Click to expand...
Click to collapse
Thanks for ideas, but it still does not work. Phone reverts its state. It's trully magical. Every time it reboots to the moment just after rooting. I have never seen anything like it before. Bootloader is always unlocked and memory chip state cannot be changed.
At least I haven't figure out how to do it yet
Anyone, please help!
EDIT:
A tried ADB sideload today, but after the file is sideloaded it can't be flashed - TWRP considers it corrupted and it vanishes after rebooting - AS EVERY CHANGE
I hope I didn't ruined my phone the first hour I got it, and XDA members could still help me. PLEASE
Hmm, it seems like everything fails to write to the emmc chip on your device, I would try to take it to a shop that does JTAG fixes, it could be a defective memory/emmc chip, sadly HTC will probably make you pay full price
Sent from my Desire HD using Tapatalk 4 Beta
humzaahmed155 said:
Hmm, it seems like everything fails to write to the emmc chip on your device, I would try to take it to a shop that does JTAG fixes, it could be a defective memory/emmc chip, sadly HTC will probably make you pay full price
Sent from my Desire HD using Tapatalk 4 Beta
Click to expand...
Click to collapse
Hi, I think also it's is the explanation for HOX+ radio lacks, permanent screen locks after the sleep, etc... fails in my AT&T's unlocked HOX+, defective emmc or emmc firmware.. It´s possible?
You also can see it: http://forum.xda-developers.com/showthread.php?t=2404393
Related
Sorry I'm a noob at all of this. Successfully rooted my phone today thanks to Honsoon2000's excellent tutorial and toolkit. Then I went to install Android Revolution, which appeared to go successfully and then after I flashed the kernel the phone wouldn't load and just hangs at the quietly brilliant screen. I followed Honsoon's tutorial to the T (or so I thought) and everything went perfectly until right at the end when I flashed the kernel. I can make it back to the bootloader screen though it says "failed to load usb master mode". I can still make it into fastboot and recovery mode...tried recovery, and the process seemed to go sucessfully, but the phone still wouldn't load after...tried reinstalling ARHD-- it's still on the sd card and the install procedure still goes off without a hitch, but the phone still won't load. I've searched around and tried everything I can, to no avail. Any help would be muchly appreciated, and I apologize in advance for being a noob wasting people's time.
Edit: For example, when I follow the steps outlined in the FAQ it asks me to enter the command 'fastboot flash boot boot.img' , but when I do it says 'error: cannot load boot.img'.
Edit 2: So I put my boot.img file from Android Revolution into the data directory of the rooting toolkit and was able to complete the above flashboot command. I was also able to install the ROM off my SD card...however the phone still hangs on the Quietly Brilliant screen...I can't even power the phone down...whenever I try it just reboots...frustrating...really hoping someone can help me...cheers.
Before you begin, make sure that the drivers for the One X+ are installed.
Place the boot image being used on the computer's hard drive.
Boot in to recovery and flash the ROM.
When that is done, boot in to bootloader and connect the phone to the PC via a USB cable.
If the phone isn't in fastboot mode already, use the volume keys to highlight the word "fastboot", then press the power button.
Now, there should be text at the bootloader screen that says "Fastboot USB".
Finally, use the toolkit or command line and flash the kernel with the fastboot command.
This should successfully flash the ROM and the kernel. Make sure you full wipe before flashing a new ROM. If you can't seem to get the new ROM booting, the final choice is to relock the bootloader and run a RUU.
Which phone version you do own? International or AT&T / TELUS?
Did you flashed the correspondant boot.img? Did you cleared the cache? ( fastboot erase cache)
I'm trying to run an RUU but it keeps saying the battery isn't charged enough to flash anything...and this after it's been plugged in all day. Oh dear I think my phone might be done...really sucks :/
Also, it won't let me power the phone down-- every time i try it shuts the phone off briefly and then opens back up to the bootloader screen.
Fixed thanks to sarcasticphoenix. Cheers.
OK so I've tried 3 times to flash a new ROM onto my phone (Android Revolution twice and Eleganzia once) using Honsoon's toolkit...I've followed every instruction to the T as far as I can tell and all 3 times the process has gone perfectly right until the end when I flash the kernel...after that when I reboot the phone it just hangs at the Quietly Brilliant screen. I know how to relock the bootloader, flash the custom rom and get my phone back...but I really want to know what I'm doing wrong so I can install a custom ROM. I know I'm using the right ROM for my phone and am wondering what gives. Being driven crazy here...any ideas what's going wrong here would be helpful. BTW on the last attempt right after I finished and the phone hung I went into the boot loader and followed the instructions in the FAQ for fixing a bootloop...still nothing.
Edit: Solved my problem-- I managed to successfully load eleganzia...the only thing i did differently the last time was flash the kernel BEFORE installing the ROM off the SD card.
jrockwell said:
OK so I've tried 3 times to flash a new ROM onto my phone (Android Revolution twice and Eleganzia once) using Honsoon's toolkit...I've followed every instruction to the T as far as I can tell and all 3 times the process has gone perfectly right until the end when I flash the kernel...after that when I reboot the phone it just hangs at the Quietly Brilliant screen. I know how to relock the bootloader, flash the custom rom and get my phone back...but I really want to know what I'm doing wrong so I can install a custom ROM. I know I'm using the right ROM for my phone and am wondering what gives. Being driven crazy here...any ideas what's going wrong here would be helpful. BTW on the last attempt right after I finished and the phone hung I went into the boot loader and followed the instructions in the FAQ for fixing a bootloop...still nothing.
Edit: Solved my problem-- I managed to successfully load eleganzia...the only thing i did differently the last time was flash the kernel BEFORE installing the ROM off the SD card.
Click to expand...
Click to collapse
That's usually what I do first, flash the kernel and then install the zip via recovery
Sent from my HTC One X+ using xda premium
Which kernel are you referring too? Actually there is one or two kernels available but only for the International version, not the AT&T/TELUS which you seem to have.
I strongly suspect that your boot looping was because you didn't flash the boot.img file correctly or not at all. And you don't seem to install the good ROM version for your phone.
Elegancia has two ROM versions one for International and one for AT&T/TELUS users.
ARHD is for International users.
Please read Q12 of the FAQ.
Lucky Thirteen said:
ARHD is for International users.
Click to expand...
Click to collapse
Lol...yeah I don`t know how I missed that. I ended up getting elegancia successfully flashed and loaded so all is well. In retrospect this was a good experience because there`s nothing like having to get yourself unforked from a bad situation to gain an understanding of what`s going on. Cheers.
I have a couple questions and since I`m not allowed to post yet in the elegancia thread I'll try in this thread first:
1) An elegancia question: Is there a way (widget) to toggle data roaming on and off in this ROM?
2) Is there a way to tweak settings (transparent pull down, selection of launcher etc.) without wiping and reflashing the ROM?
3) What are people's favorite launcher for that ROM? I tried Atom but it was just a guess because I hadn't heard of any of them. I like it so far but am curious about the others.
I have the HTC One X Plus International and recently recovered from it only being able to go into Bootloader Mode because of the System being erased without a backup. I finally was able to learn how to find the correct RUU for my make and model to bring it back to life. Before accomplishing this, this current problem still existed.
Each time now when I boot-up, it starts perfectly well, no problem. But when I try going into Bootloader Mode and choose Recovery, it shuts itself down. So, since I am unable to Root it, or at least I don't know how to do so under these circumstances, how do I get around this obstacle? Thanks.
Jussi31 said:
I have the HTC One X Plus International and recently recovered from it only being able to go into Bootloader Mode because of the System being erased without a backup. I finally was able to learn how to find the correct RUU for my make and model to bring it back to life. Before accomplishing this, this current problem still existed.
Each time now when I boot-up, it starts perfectly well, no problem. But when I try going into Bootloader Mode and choose Recovery, it shuts itself down. So, since I am unable to Root it, or at least I don't know how to do so under these circumstances, how do I get around this obstacle? Thanks.
Click to expand...
Click to collapse
I don't know if this is too obvious.. but have you flashed the recovery again??
When you run the RUU, it is overwritten. You need to download a recovery and flash it through fastboot:
fastboot flash recovery recovery.img
Actually, around six or seven times now, with no luck. Now when attempting to get into Recovery, it hangs on the white screen. The thing is, I successfully had TWRP 2.5.0.0 on it. (Long story.) I am now trying to figure out how to root it through Fastboot, if that's even possible. Otherwise, I am out of ideas.
Through trial-and-error, I finally was able to get it rooted. However, no matter how many times I try flashing TWRP-Touch (various versions), it maintains its inability to boot into Recovery Mode. Go figure.
I use twrp venom without any issues, maybe try that one?
http://forum.xda-developers.com/showthread.php?p=37300312
Sent from my Viper One X+
Oh wow, it actually worked! God love you. Thanks much.
No problem
Sent from my Viper One X+
When you were hanging on the white screen, did it say anything on the screen?
I can't recite it exactly, HTC, something. But know that it is the first screen you would see upon rebooting.
Update
00mpollard said:
No problem
Sent from my Viper One X+
Click to expand...
Click to collapse
Hey 00mpollard, I just wanted to thank you for both recommending a working Recovery IMG (that works great) for my HTC One+, and as well as introducing me to the corresponding Viper One X+ ROM, that I also decided to install, and I couldn't be happier. Thanks again.
No problem, glad i could help!
I love Viper rom, very stable & lots of customizations Can't go wrong!
Jussi31 said:
I can't recite it exactly, HTC, something. But know that it is the first screen you would see upon rebooting.
Click to expand...
Click to collapse
I was just curious because if it said something about waiting on SD card or SDdata, something along those lines, I get that issue when the phone is plugged in. Unplugging the cable allowed me to enter hboot with no issues.
Hi Guys,
i have a Sony Tablet S (first version, not Xperia) with 4.0.3 r5a (prerooted with AiO and old hidden.img) and it gets stuck on every second reboot, that means:
- Tablet is powered off
- Power on Tablet
- Tablet stuck on Sony logo (Logo refresh one time as you can see on the screen)
- Hold Power for 10 seconds to power down
- Tablet is powered off
- Power on Tablet
- Tablet boots normally
- Reboot Tablet from adb shell or app or just reboot manually (power off/power on)
- Tablet stuck on Sony Logo
- Power off 10 seconds
- Power on
- Tablet boots normally
........ and so on
What i have tried:
- Downgrade to 4.0.3 r1
- Connect via adb while stuck (not possible, adb does not recognize the device in this state)
- Wipe data (through recovery mode)
- Tried to find some log files which gives information (failed badly, logcat only produces output when tablet is already booted, no other logfile found)
Any ideas what could be the reason or what i should check?
Btw, the tab works perfect once it has booted up.
Keep on rockin'
Sony tablets have 2 boot partitions, one of yours is corrupt so the tablet boots to the other one. I think Condi's flasher can fix it, because it flashes both
Sent from my Nexus 4
lopezk38 said:
Sony tablets have 2 boot partitions, one of yours is corrupt so the tablet boots to the other one. I think Condi's flasher can fix it, because it flashes both
Sent from my Nexus 4
Click to expand...
Click to collapse
This is true, or since you have old recover you can use condi's double flash. If you use flasher please install the new recovery as well so it doesn't mess anything up.
I just reflashed 4.0.3 r5a with the actual AiO but so far the problem persists. Flashing went through flawlessly except the stuck on sony logo on the reboots and also the wipe after flash went through with no problems. Device is rooted and working, but still stuck on every second reboot.
Any other ideas?
Keep on rockin'
EDIT: I also tested it now with Flasher 3.0 (not AiO but also from condi) where i chose option 1 4.0.3 r5a wifi+3g and also flashed old recovery (option 2). I had no problems in the update process but the problem is still there.
i got same problem at 4.0
flash stock rom(root-able ver) then root it,the system is ok.
i guess aio tool have some bugs with none us regsions(my is china)
check your regaion.zip,file content,version and permition
Use his flasher tool, not the AiO
@robin
What exactly should i check on region.zip, anything special to look out for?
@lopezk38
As you might have read i also tried with the flasher tool, it wrote both partitions (current system and second system) but the problem persists.
Any other ideas how to fix this?
Keep on rockin'
Still nobody with an idea?
Just flashed custom_prerooted_doubleFLASH_R5A_nbx03_016-ota-121116077.zip from condi's thread @ http://forum.xda-developers.com/showthread.php?t=2020911 but still no luck, always stuck on second boot.
Although i had at least a little bit success with flashing 3.2.1 via AiO, after flashing it and getting stuck on reboot i wiped data in recovery mode and was able to boot at least once into 3.2.1, but after reboot i got stuck again and on second reboot it booted back to 4.0.3
At least that tells me that it is possible to boot from the partition, but something is still wrong.
I really appreciate all the help and the work from you guys.
On another note, i'm pretty firm with shell commands (long time linux user), anything i could try to check via adb shell?
Keep on rockin'
Corrupted for sure on the second boot partition, if double flashing does not help then something is really wrong with the second partition.
Sent from my Nexus 4 using xda app-developers app
andyabc said:
Corrupted for sure on the second boot partition, if double flashing does not help then something is really wrong with the second partition.
Click to expand...
Click to collapse
Leaves the question if there is a way to repair it, maybe by copying an image from the working partition with dd to the bad partition. I don' want to give up yet
DudemeisterAT said:
Leaves the question if there is a way to repair it, maybe by copying an image from the working partition with dd to the bad partition. I don' want to give up yet
Click to expand...
Click to collapse
Exactly same issue here since i rooted the device with last AIO 6.4 tool. Still searching for a solution too.
In the meantime i tried two more things to fix this problem.
First i copied the working partition to the not working partition with dd
dd if=/dev/mmcblk0p3 of=/dev/mmcblk0p2
The writing of the partition went through with no problems but it did not help at all. In my last effort to get system0 working again i tried flashing the OTA update (knowing that i will loose adb shell in recovery), but to my surprise after finishing the update successfully i was stuck with the same problem and a working adb shell. It seems OTA was flashed to system0 but is still not able to boot from it
I am running out of ideas and thinking about buying a new tablet (definitlely NOT a Sony Device anymore). Hopefully someone has another idea.
DudemeisterAT said:
In the meantime i tried two more things to fix this problem.
First i copied the working partition to the not working partition with dd
dd if=/dev/mmcblk0p3 of=/dev/mmcblk0p2
The writing of the partition went through with no problems but it did not help at all. In my last effort to get system0 working again i tried flashing the OTA update (knowing that i will loose adb shell in recovery), but to my surprise after finishing the update successfully i was stuck with the same problem and a working adb shell. It seems OTA was flashed to system0 but is still not able to boot from it
I am running out of ideas and thinking about buying a new tablet (definitlely NOT a Sony Device anymore). Hopefully someone has another idea.
Click to expand...
Click to collapse
I have the same problem, have you found a solution?
Sadly i was not able to fix it, i even tried to let the battery run out completely (was my last hope) but no change at all. I am thinking of sending it back again to sony for repair, cause now I am absolutely out of ideas, i think i tried everything possible.
Keep on rockin'
Sent from my Sony Tablet S using xda app-developers app
Any updates on this problem... BUMP
Sent from my Galaxy Nexus using Tapatalk 4
Sadly no, anyway i use my sgs4 more than the sony, much better Hardware just smaller screen. If there is a tab with the same or better specs (like sgs 4) i will buy a new one and give the sony to my brother. Farewell sony, i have enough of your crap.
Sent from my GT-I9505 using xda app-developers app
I have the same problem ! Any help would be greatly appreciated !
Did you try the things written in this thread?
Sent from my GT-I9505 using xda app-developers app
I don't know if there are still people interested in this but i finally got my tablet working again normally and booting up everytime.
Today i powered on the tablet after loading it fully and realised that there was no wifi anymore, i couldnt even enable the wifi adapter itself. After some other issues, including loosing root, i tried to reflash my backup. I went to recovery and selected the zip to flash which resulted in the "error in base sku" message. I tried different rom files which i had saved (custom signed, officialy signed) and none of them seemed to work. Rooting the device also did not work anymore, even if i tried manually executing all the commands, mostly i just got shut down by permission denied.
Anyway, after failing to try and flash the rom named signed-nbx03_016-ota-121116095.zip i luckily got the idea of renaming it to update.zip and put it in the root of the external sd card. I went back to recovery mode and selected the update.zip, flashing started and went through completely. The tablet rebooted and finished installing the rom and i ended up on the standard ics screen. I then took condis AiO and went to root the tablet and after the tablet rebooted it surprisingly booted again normally and after a quick check with super su i knew it was rooted. I did a couple of reboots with and without cable/ac adapter attached and now i am sure, it boots up every single time.
It looks like that the filename update.zip might tell the tablet to flash differently than with another name, at least i like to hope so. Maybe it helps someone out there with the Tab S.
Funny sidenote, two weeks ago i bought a SM-T805
Have fun
Don't really need some special help here, just want the device to function again no matter what way. (Don't care if it's factory reset completely it has nothing on it I was just using it for a bit of experimenting).
So anyway, I have an HTC One x that I tried to install Cyanogenmod mod on but when trying to flash it (I was a bit impatient and just did what I thought would work), it didn't work and I'm stuck on the HTC Boot screen. I can still restart the phone and get to the recovery menus or whatever they're called. But even when doing a factory reset it still just won't get past the boot screen.
I'm just someone who has a good love for android and got given this phone for free so I thought I might experiment with rooting and all that, (I don't want to do this to my main driver, the Z1, for the life of me).
Any help here would be great.
Thanks
MHarris333 said:
Don't really need some special help here, just want the device to function again no matter what way. (Don't care if it's factory reset completely it has nothing on it I was just using it for a bit of experimenting).
So anyway, I have an HTC One x that I tried to install Cyanogenmod mod on but when trying to flash it (I was a bit impatient and just did what I thought would work), it didn't work and I'm stuck on the HTC Boot screen. I can still restart the phone and get to the recovery menus or whatever they're called. But even when doing a factory reset it still just won't get past the boot screen.
I'm just someone who has a good love for android and got given this phone for free so I thought I might experiment with rooting and all that, (I don't want to do this to my main driver, the Z1, for the life of me).
Any help here would be great.
Thanks
Click to expand...
Click to collapse
If you had just used htcdev.com to unlock the bootloader and are still S-On, you need to pull/extract the boot.img from the CyanogenMod zip and install via fastboot.
es0tericcha0s said:
If you had just used htcdev.com to unlock the bootloader and are still S-On, you need to pull/extract the boot.img from the CyanogenMod zip and install via fastboot.
Click to expand...
Click to collapse
She's running all good now, thanks for that
MHarris333 said:
She's running all good now, thanks for that
Click to expand...
Click to collapse
You're welcome. Pretty common issue when people are getting used to how it works for HTCs.
Pro Tip: If you want to simplify the process, you can use this: https://play.google.com/store/apps/details?id=com.cgollner.flashify and install the boot.img with the phone while booted, then boot to recovery and finish the rom install. Recommend doing a nandroid recovery first, just in case the boot,img/rom combo does not work properly, otherwise if you flash it first THEN do a backup, the new boot.img will be matched with the old rom and might cause issues upon restoring if they are not compatible.
Alternative: S-Off. Depending on which hboot you are on, you should be able to do S-Off. It can be a bit of a pain to set up, but once you do, then you can install roms just like normal as the boot.img will be able to be flashed from recovery along with the rom like in most phones.
I have recently rooted my HTC One X+. I made a nandroid as well as an titanium backup. I tried to install this rom cynamogen 11.2 nightly
Unfortunately the installation went wrong due to the following reasons (MD5 file not found). Then I tried to restored my nandroid backup .
This operation was succesfull however after restarting the phone is still stucked on the splash screen (htc quietly brilliant).
I can still have access to bootloader as well as the TWRP 2.6 and restoring again and again !
So what i have to do !
zekinan said:
I have recently rooted my HTC One X+. I made a nandroid as well as an titanium backup. I tried to install this rom cynamogen 11.2 nightly
Unfortunately the installation went wrong due to the following reasons (MD5 file not found). Then I tried to restored my nandroid backup .
This operation was succesfull however after restarting the phone is still stucked on the splash screen (htc quietly brilliant).
I can still have access to bootloader as well as the TWRP 2.6 and restoring again and again !
So what i have to do !
Click to expand...
Click to collapse
I'm having the same problem. Somebody got a solution to this? Bootloader works, Recovery works, it just won't boot, and WinDroid HTC Tookit detects my device, but when I try to flash or run a command it says "A phone has bot been recognized by this toolkit". I unlocked my phone successfully, flashed a recovery, but when I click flash ROM and when I try to push a file I get that error.
EDIT:
I fixed my issue using Kubuntu. I'm sorry mate, if you use Windows I can't help you there. That's why I never really like Windows it's a retarded and flawed OS. Linux? Not so much. Get Linux and you can practically fix the issue yourself, if no one comes up with a solution for Windows.
Did you flash the boot.img ? ...
Thread cleaned,
Guys back on topic please. Do not flame other users on a public forum. If you have an issue with a users post, report it to us and we will deal with it.
Many thanks,
Ghost
similar stuff going on here
I tried to flash the latest venom kernel having already done this when i first got the phone back in 11/12 or 1/13 somewhere round there.
I hadnt read all the instructions and hadnt updated the loader or recovery. now its stuck on boot screen. I can get to recovery. unfortunately the only zip thats on the phone is the new (wrong one). The windroid sees a number and recognises that its in recovery but is unable to do anything with it, no adb side load push pull, nowt. I just happened to buy a micro usb host cable. I was wondering if there are any commands that I could put into terminal that would allow it to see a memory card or any help at all..
Daryll99 said:
I'm having the same problem. Somebody got a solution to this? Bootloader works, Recovery works, it just won't boot, and WinDroid HTC Tookit detects my device, but when I try to flash or run a command it says "A phone has bot been recognized by this toolkit". I unlocked my phone successfully, flashed a recovery, but when I click flash ROM and when I try to push a file I get that error.
EDIT:
I fixed my issue using Kubuntu. I'm sorry mate, if you use Windows I can't help you there. That's why I never really like Windows it's a retarded and flawed OS. Linux? Not so much. Get Linux and you can practically fix the issue yourself, if no one comes up with a solution for Windows.
Click to expand...
Click to collapse
Hi mate, can you plz tell me how you got ure problem solved with linux ? thx
lha18 said:
Hi mate, can you plz tell me how you got ure problem solved with linux ? thx
Click to expand...
Click to collapse
I extracted the "boot.img" file from the zip file of my desired ROM, then I open terminal, booted my phone into Fastboot and typed "fastboot flash boot boot.img".