Hello,
I have the following problem on my desire and would appreciate your help.
I used to have 2.1 and just upgraded to Paul's 2.2 r8 version. There were some strange restarts so I decided to start from scratch, create the gold card again, root, etc etc.
I used the unlocker.com as a guide to do all those and here is what happens when I try to root the phone. I also want to mention that right now the phone doesnt boot up and I am stuck in the "triangle" screen, but this one looks different than the one that I knew with the triangle in the middle; it just says htc in the middle and there are 4 small triangles in the corners.
I run the step 1 batch file from unlocker and there are no errors; however, there is a progress bar on the phone's screen that is normally green and for a quick second it turns red and then back to green. I was able to see that this happens when the radio is being written (as per the progress in cmd).
When I pull the cable to the pc off, it gets to a RUU white "screen" and there isnt any button that will have an effect; once I plug back the cable it goes back to the triangles screen with htc in the middle.
ADB is not working even though I reinstalled the drivers, etc. only fastboot works. (by working I mean that the device doesnt show in adb, but it shows in fastboot)
Bootloader is 0.80 and the version that I get using fastboot is 1.21.405.1
Any clue on how to access recovery and just flash a ROM that will be fine? Must be something related to the recent rom upgrade to Paul's r8 Froyo I guess, but I dont know where I messed it up.
Thanks a ton guys and sorry for the long post but it is a strange one and tried to explain somehow the symptoms.
Re-install using a RUU (Can be done from fastboot screen I think), then use unrEVOked to root, no messing with batch files.
Hi again,
I tried running different RUUs, both 2.1 and 2.2, but I get the same error at the end of the install wizard: Error 110: file open error (The rom update utility cannot open the requested files or the files are damaged...)
The thing is that the install wizard seems to go through all the steps (checking signature, updating system, radio, recovery, etc.) and only at the end this error comes up.
One other aspect is that again the progress bar on the phone screen is green but flashes red when the radio is being written on the phone (as per the install wizard); then it goes back green when writing recovery, system, etc and there is another triangle with ! showing up on the right side of the progress bar (is not there when it starts).
The info showing up in the RUU "menu" on the phone (the only one I can see when the phone is not plugged to the pc) is showing a bootloader version of .9x after RUUing the froyo's and changes back to .8x after using the 2.1 RUUs. The only thing that remains the same is the radio version that still shows 4.06.00.02_2 irrespectible of the RUU that I try to install (2.1 or 2.2), hence I believe that there is something wrong around the radio part. I remember that Paul mentioned on the thread where I got the r8 froyo pre-baked zip file originally that it includes a radio version 5.10.x while the froyo RUUs that I tried to flash are having 5.09.x, maybe this is the problem as it might be that one cant flash an older RUU than what the phone has, but its strange since the bootloader is "upgraded" and downgraded without problems.
Any other suggestions on what can I do further? (right now I only have access to the RUU menu when I turn on the phone and to fastboot commands in cmd...the phone doesnt start so I cant access anything else as per my current understanding).
Thanks again for the help guys!
So you can acces hboot and bootloader only??
And when you tried to enter to recovery get stuck on htc logo screen??
Volume up/down button work ok?
nope, buttons are not working at all, only power up when the phone is off.
here is the sequence providing the phone is off and has a valid gold card in it (I dont get the CID error); doesnt matter if the cable is connected to the pc or not:
1. push power button, phone starts up to a screen showing the following: HTC in the middle (with some water shade under it) and the 4 small triangles in the screen corners (they have a ! mark inside).
- any combination of power + back or + vol down dont start the phone
- when I first rooted the phone having 2.1 there was just 1 triangle (bigger) with the same ! mark in the middle of the screen, that's it and of course all the hboot and recovery menus were ok
2. plug cable to pc and run RUU.... .exe, install starts on pc and also on phone there is a green progress bar under "HTC". bar goes red for a second when the pc app shows something like writing radio. bar gets back to green when the pc apps writes system, bootloader, etc., but there is another small triangle showing up at the end of the progress bar on the phone.
3. error shows on the pc app, error 130 above, then the phone shuts down and if restarted it gets back to the same triangle screen with htc in the middle like it was before the ruu attempt.
- if when I power up the phone (after pulling up the battery) and then remove the pc cable, the screen changes into a white background one with something that I would call a RUU menu; looks just like the one that you get when you power up pressing "back" on the phone, but only with RUU as an option (like you have in the oter Recovery, Restart, etc etc and you navigate with vol up/down and select with power). here no button works, or any buttons combination.
- the screen changes back to the "triangles" one as soon as I plug the pc cable into the phone and switches back again and so on when I pull out the cable from the phone.
- te bootloader version that I can see on the RUU "menu" when I plug out the cable is changing acording to the RUU that I try to write and it goes above 0.8xx and comes back under it easily...the firmware version and radio remain the same though (radio is 4.06.xx, firmware 1.21.xx)
- via cable I can use only fastboot command in cmd, as adb doesnt list the device (I tried reinstalling the drivers). firmware in fastboot is the same as the one that the pc app "sees" on the phone when trying to install the RUU, and the device shows up using fastboot command
That's it...kind of strange, at least to my knowledge at the moment.
And to ask to your questions I dont have access to recovery and not to hboot I believe, only to that one showing RUU as the only option...
Those 4 triangles in each corners look familiar to me. You forgot to give the most important information: HBOOT, radio, etc.
A few minutes on Google gave me this: Google is your best friend. Keywords were: htc desire triangle corner error. Here is the link to the search page: Google is your friend
it's not a triangle in the corner...there are more but that's not the point.
hboot is above 0.80xx and radio 4.06xx, but again, as mentioned the hboot version changes depending on the RUU that I try to write, radio and firmware not.
thanks for the link though, added a reply maybe something happened in the mean time...
and btw, google is everybody's friend
popepope said:
it's not a triangle in the corner...there are more but that's not the point.
hboot is above 0.80xx and radio 4.06xx, but again, as mentioned the hboot version changes depending on the RUU that I try to write, radio and firmware not.
thanks for the link though, added a reply maybe something happened in the mean time...
and btw, google is everybody's friend
Click to expand...
Click to collapse
I think you miss something here: if I recall properly, those 4 triangles in ALL for corners appear when you try to root a SLCD Desire with a AMOLED rom, thus 'killing' your screen. Try the downgrade HBOOT 0.83-0.92 to HBOOT 0.80 root method and you'll safe. You have to root your phone according to the HBOOT and downgrade it if you need to.
hmm...the thing is that i rooted the phone before with the same approach as I had now, so same rom and it behaves different now versus the first time; but it worked then so not sure if it is related to the amoled vs slcd screens.
I am already on hboot 0.80xx so the downgrade wont help, right? i am not able to access hboot menu irrespectible of the bootloader version that I see in the RUU menu (I mentioned that based on the RUU that I try to write the hboot version changes up and then also down just by attempting to write a RUU). plus, adb comms are not working, only fastboot...
i think the amoled vs slcd issue was that the screen is not working, but the phone is booting up, etc.
would appreciate some more help pls
I have read other posts here about the 4 triangle thing - never saw how any of them turned out though. I'm not having a crack at you here for not searching, but have you had a look here to see whether you can find someone who has had similar problems? With so many members, you can almost bet that someone else has had the same problem as you in the past....
Good luck in getting things sorted.
tried to contact via PM the users having the same problem, but no reply as of now. will post the solution when found for sure, but at the moment I still cannot get adb functionality, so completely out of ideas, waiting for others
Hey Popepope - did you manage to fix this issue? I have exactly the same problem as you have described, and I can see the boot screen after removing the cable following the RUU error and it says "Radio_V2 - Fail-PU". I get the same red progress bar when it is updating the radio. Something is clearly broken here...did you manage to fix yours or did you send off for a replacement?
Is your screen a SLCD one or a Amoled one? If it is a SLCD one, flash a SLCD RUU. If its a Amoled one then PM me and ill see if I can help you with a problem as I ran a Tuition a few days ago. As you say that the error you get at the end is dew to a damaged file or something, can you try downloading the RUU from a mirror? Again if you need a mirror, pm me and ill post on on my dropbox. The method I used for flashing Ruin was much better and easier so you can hope to find a fix. Pm me. Good Luck anyway!
I managed to fix the issue by leaving the phone to charge overnight, running the same RUU that failed before on a full battery and it worked! I now have a working phone
I ran the update on win 7 64 so it shouldnt matter what operating system you use - if you have the same issue as I did just make sure the battery is fully charged before running the RUU. Still having reboot loop issues though :E
Hey Popepope did your problem solve i have the same 4 triangle each side with HTC logo in middle tried most i can but didn't find solution here is the screenshot i had attached
Right, so, I've done some googling and some searching about here and there but either I'm being dense and the solution is really simple, or nobody's done what I've done with this tablet before and, again, I'm being dense. Here's my issue:
Kindle Fire 2 (2nd gen, also second-hand) tablet: stock, rooted, that worked fine with the tool by bin4ry.
Rebooted after that, verified root was working, adb and fastboot perfectly fine (sidenote: linux user, no shonky Windows drivers at fault here)
My ultimate goal is to get CM on this device, so, started after this to follow the instructions in this thread regarding getting the second bootloader on the tablet.
Realised I need a factory cable, ordered, delivered, works but not all the time, I'm not sure if it's a dodgy cable or not but did get into fastboot.
Got new bootloader installed, saw Kindle Fire logo in blue. Proceeded to boot the stock rom after this and use adb push to put the CM 11 zip and the gapps zip files on /sdcard.
adb shell, su, reboot recovery, intending to boot into TWRP to flash new rom
Tablet reboots, but is now stuck with the stock boot logo (orange) and then a black screen with a white triangle and exclamation mark on it. I haven't seen any references to this particular delight.
Fastboot cable does not, no matter how I fiddle with it, put the tablet in fastboot mode. Holding down the power button for five minutes did nothing.
I've read that if it turns on, it can probably be recovered, but I don't know what to do from here. Can anyone render assistance?
So, after much fiddling, I discovered that my problem was actually that my fastboot cable was loose in the microUSB end, and not contacting properly with the pins - thus not sending the tablet the requisite signal to enter fastboot mode.
I've successfully got TWRP onto the fire and thus CM 10.1 now.
I hope this update helps anyone who finds themselves in a similar situation; fastboot still works, keep wiggling.
xyonofcalhoun said:
So, after much fiddling, I discovered that my problem was actually that my fastboot cable was loose in the microUSB end, and not contacting properly with the pins - thus not sending the tablet the requisite signal to enter fastboot mode.
I've successfully got TWRP onto the fire and thus CM 10.1 now.
I hope this update helps anyone who finds themselves in a similar situation; fastboot still works, keep wiggling.
Click to expand...
Click to collapse
I had this problem with a 2nd gen Kindle that was also second hand.
Phoned Amazon UK, described the problem (not mentioning I'd done it myself) and they replaced it.
Seems there's not a lot they won't replace.
The phone hard-bricked, and I already went through a bunch of guides, none worked to get me to fastboot, so that I could flash the firmware.
My computer correctly detects the phone as a Moorefield device, and the xfstk unbrick process appeared to had worked, because it went as expected. But after it continues to OS, first the little USB screen appears, then, after multiple boots, the 4 color screen is the only thing that appears on the screen...
Not even a hint of fastboot (tried to watch the output of fastboot devices but it never outed anything)
Should I try another GP key? (using 0x80000807), should I get another xfstk .bin files? (extracted mine from sal358-amtech) thanks in advance...
did you find any solution bro?
Same
Hello everyone,
I'm having a weird problem with a friend's Moto G6 Play.
From what I know, the phone auto-updated overnight a few months ago and since then the display is essentially dead. While the backlight starts up when I plug it in to the USB, I cannot see anything else on the screen.
So, I tried to connect using ADB and fastboot. Unfortunately, the RSA fingerprint has not been approved for my PC and there's no way I can approve it now without getting the display working.
fastboot does detect the device, but unfortunately I cannot do anything else.
I tried to boot through fastboot using a twrp image, but it just got stuck. Any other fastboot command, just shows "< waiting for any device >".
I've also downloaded the stock image, but am stuck at this point.
Hope you guys can help me out here.
Thanks in advance.
P.S. I checked this thread, but the problem is different than mine.
pranavlawate said:
Hello everyone,
I'm having a weird problem with a friend's Moto G6 Play.
From what I know, the phone auto-updated overnight a few months ago and since then the display is essentially dead. While the backlight starts up when I plug it in to the USB, I cannot see anything else on the screen.
So, I tried to connect using ADB and fastboot. Unfortunately, the RSA fingerprint has not been approved for my PC and there's no way I can approve it now without getting the display working.
fastboot does detect the device, but unfortunately I cannot do anything else.
I tried to boot through fastboot using a twrp image, but it just got stuck. Any other fastboot command, just shows "< waiting for any device >".
I've also downloaded the stock image, but am stuck at this point.
Hope you guys can help me out here.
Thanks in advance.
P.S. I checked this thread, but the problem is different than mine.
Click to expand...
Click to collapse
Check device manager. Does it say Qcom ha USB mode 9008? Then your phone is hard bricked, and it's not your display the issue. Use qfil and a blank flash to fix it.
Hello XDA community,
Recently I ordered a second hand motherboard (from chinese third party) for my old LG G3 to have it as a secondary phone (for waze and whatever, to not affect my note 20 ultra battery ) and when I received it and replaced the old one (which had BSOD) everything seemed to be fine, but it wasn't because in fact it had a firmware version LGD855-V10m-ISR or something like that and I couldn't update it from official means. I said "no problem", root it, flash custom recovery and flash LineageOS to have new software on it. I managed to root it with OneClickRoot script but when I tried to enter recovery i was surprised to find out it wouldn't work (tried physical buttons, software, ADB - nothing works). When trying to boot to recovery, a "Fastboot has started" screen shows up (but device isnt in fastboot in fact because fastboot tool doesnt detect it). The only thing that worked was Download mode, but when i tried to flash LGD855-V10-eur (which i remember i first had on old motherboard) with LG FlashTool, it failed (some error about partition change at 6%) and also erased the system and now only Download mode is available. Now my question is: where can I find the model on the motherboard because i doubt this is a simple D855 and the firmware version differs. Also some context: now the LGFlashTool says state "READY" on the com port but won't start a software flash when i plug the USB in, LGUP said model unknown from the beginning. I didn't manage to find it by myself on the motherboard (maybe i need a magnifier or something) and I'm requesting your assistance.
where did u buy the motherboard from