Develop Bugs

[Q] Bootloader corrupt WTF?

Sorry for my enthusiasm, but here is my problem:
I want to install Android Revolution on my HTC DHD.
I've done all these steps:
- Successfully created a GoldCard
- Successfully dowgraded from 2.3.3 to 1.32
- Successfully permrooted via Visionary+
- Successfully Radio S-OFFed, SuperCID + SimUnlock via this tool
- Now failed on ENG S-OFF via this tool
{
"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"
}
I opened it as Admin, I am on a Radio-S-OFFed and Permrooted Device with Software <1.7x, I checked "Yes, I have Radio-S-OFF" (or how it was called), I connected my phone via charge only, I enabled USB Debugging, I have all adb drivers (HTC sync), I accepted the superuser request on my phone and I so I have done EVERYTHING mentioned in the threads, which I Have read 2 times before doing it, but now this stupid error and I don't know how to proceed.
I hope you guys can help me. I did of course not reboot my phone, and I am continuosly charging it right now to prevent running out of battery.
EDIT UPDATE: I tried the tool now without the box checked, gives me "connection error" (yes I again accepted superuser request)

Ok, ok nevermind guys, figured it out myself:
Thanks to ratman33 and myself for trying out weird thingds
Ratman33 said:
I had the same error and nearly crapped my pants thinking I bricked my phone. Its not really a big problem. Go to Menu>Settings>Applications>Manage apps and clear the data from Superuser. Reconnect your phone making sure you're on charge only, usb debugging. Run the Eng S-off tool and watch your phone as it attemps to push the data. Superuser should pop up asking to let the Eng tool have privs. Click allow and it should work fine. CWM has been working great for me ever since!
Click to expand...
Click to collapse
But this alone did not work for me. I needed to go to Menu>Settings>Applications and then check "Fastboot" so that it's enabled. Then disconnect your phone from the PC and WAIT min. 5 seconds. Then connect it again and run the tool, and it gives you success message!
But: Can I now be sure everything went right?

Alskarl said:
Ok, ok nevermind guys, figured it out myself:
Thanks to ratman33 and myself for trying out weird thingds
But this alone did not work for me. I needed to go to Menu>Settings>Applications and then check "Fastboot" so that it's enabled. Then disconnect your phone from the PC and WAIT min. 5 seconds. Then connect it again and run the tool, and it gives you success message!
But: Can I now be sure everything went right?
Click to expand...
Click to collapse
It should be. I guess there is only one way to find out, reboot in bootloader and see the results.

or you could have tried with your Wi-fi turned on and connected to a network.....that's the way it worked for me

QPST Connection problem.

I cannot connect to QPST and don't understand why. This is the error message I get every time I try, I have searched Google and XDA for a solution. Perhaps I am retarded, I don't know. Advise?
{
"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"
}

ANYONE????

Somebody please help!!!

I don't know how many people actually know about QPST I sure don't know enough to help. Sorry. Free bump.
Sent from my PC36100 using XDA App

I have been trying to connect my Samsung Admire to qpst for awhile and no luck. I have tried every suggestion on every forum I have found to date. Such as, pull the SD, put the phone in recovery, change the Baud rate, change the port #, use xp not W7, I downloaded every Samsung driver that worked and tried different versions of qpst. Is there not one QPST genius that can direct this noob in the right direction. Thx

For the Samsung,
Sometimes recovery mode helps, but also make sure you are using the stock rom (not aosp or CM). While QPST and others like it access the memory and firmware, the rom actually supplies the conduit. Recovery mode sometimes let's you get around some issues, but the work is still being done by the rom.
Also, while I'm not sure about Samsung, on LG phones you sometimes need LG's version of QPST, called LGnpst Lab in order to access some functions. Samsung may need similar, but I have also heard Samsungs are a bit of a pain at times.
For the OP, I know it's old but in case anyone else comes across this thread again...
Make sure the phone shows up in device manager, for HTC you need to use the HTC diagnostic drivers. If it's there, then you meed to make sure no programs are holding on to the port. CDMA Workshop or DFS, or something else may be holding the port open, the program may have been closed but didn't completely shut down or let go of the port.

Thanks Leslie I have been working on this for awhile now and I've never run across a Samsung version of QPST, I'll look harder.
And as for the stock rom replacement I have tried that twice and of course no luck but again I will try a third time.
My phone does show up in the device manager several different places and I don't have CDMA Workshop or DFS on my computer is there a way to check if some other program might be holding the port. Or should I just reboot my computer then start over? That sounds like a rhetorical question sorry.
Thanks for your help

Well I restored it back to stock, hooked it up to my XP computer and rebooted the computer. It showed up as diagnostic com4 in QPST where it had only showed COM4/unknown in W7.
I'm wondering if Link2sd may have something to do with it since it has two primary partitions. Now that I have put it back stock there is no room to rewrite the script on the second partition so that the phone recognizes the linked apps.
Should I uninstall link2sd and delete the newer partition putting everything back to normal? Or can I just unlink the apps that are linked to the newer partition and restore them to the phones internal memory?
What a freaking nightmare!! I guess I'm just to stubborn to stop trying to get this working thanks in advance to anyone who can help.
Oh and I searched for a Samsung version of QPST but found nothing.

I said there could be a Samsung version, not that there is.
Win7 has driver issues with some of this stuff and so do aftermarket roms, your problem was probably one or both.
If you are seeing a diagnostic port you are halfway there, QPST should see it now. Since it does, you are fine, don't mess with the phone or Win7, just do what you need on the XP computer. I'm sure there is soemthing you can delete on the phone to find room (boot animation, alternate languages, old version of Market, live wallpapers, etc..).
Honestly, if you are doing what I suspect, this is only the first of many similar hurdles you will face. You will have to be stubborn to get through it.

I'm having this same exact issue! I cannot figure it out for the life of me.
Using the EVO 4g with stock Rom, simple root, and amon ra recovery. When I update the drivers on my Vista laptop it says I already have the most up to date drivers.
It's killing me. If anyone can help or steer me in the right direction, that would be so awesome.
Thanks
---------- Post added at 05:50 PM ---------- Previous post was at 05:14 PM ----------
answered my own question with some thorough searching. simple fix, copied the drivers to my driver file, uninstalled in device manager and re-installed and now its showing up and the port is createble!

EVO on life support

Dear XDA Community,
This post will be as detailed as possible for those who enjoy detail.
It’s about the problems my EVO has been experiencing over the past 3 months and, after trying to fix the problems though IRC it seems that the attention should be brought to the forums for a larger audience. It was 3 months ago when I flashed a rom ( cannot remember the rom ) and my EVO took a turn for the worst.
What Happened :
When the rom was flashed and booted for the first time everything seemed normal but, the rom started to freeze at random. At first I though it was a normal process due to new ROM’s installs but, it kept repeating it over and over until it went into a boot loop syndrome.
Prior to these problems I did my daily clean/wipe dalvik rituals for ROM consumptions.​
After 15 - 30 boot-loops my battery dies and the crusade begins.
I begin looking for another ROM to flash, to rid the sickness the previous ROM infected my EVO with. I installed my favorite (SalvageMod) and, the problems began to show. Salvage installed perfectly fine (as always) but, my phone started to lag, the speed was reduced to about 35 - 50%. It’s noticeable big time. The camera stopped working and everything seemed to be falling apart.
(RECENT)In panic I started looking for ways to RUU so I can avoid any other problems. This is when I noticed that usb was not accessible. I couldn’t mount my device; [CLICK HERE FOR VIDEO], so I used a SD card reader to RUU my phone and get it back to stock.
Phone is back on stock settings but, no root and, without usb support revolutionary.io is lightyears ahead of my time.


Problems :
Not mountable through usb cable [SD Card Reader option / Software Error]
System lag noticeable slower (BestBuy rep even confirmed its unresponsiveness)
Device will not charge when on [Either mount / Software Error],
Camera problems.
[Click Here For Second Video]
{
"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"
}
So can you guys help a member get his EVO back in business, my wallet would greatly appreciate it.
Thanks,
samthewildone
Aspiring Mathematician

​

Well, the easy way out is that now that you're back on stock and a rep has agreed the phone is not working properly and you have no USB, trade it in

I would right click on that device and uninstall the drivers. then hook the phone up to the PC and see if it automatically installs the correct drivers or find better drivers.
This may have been covered, and it looks like there's a lot more going on then just drive issues, but to get this phone into a state in which you can root it and wipe it again, you need to eliminate that variable.
Not saying that the USB drivers are even an issue, but its something worth exploring first and foremost.

Tried that, as in my thread. I uninstalled and reinstalled drivers and, it just keeps showing what that picture shows above. The phone isn't damaged but, the software is borked due to a bad bad kernel or ROM flash.

Not a solution to your problem, but if you are still s-off then you don't need Revolutionary. You can put a PC36IMG of a (reliable, ie Amon Ra) recovery on your SD card. From there you can wipe thoroughly and try flashing something else.
Unfortunately it seems like some sort of hardware failure, so the only fix could be getting a replacement.
Supersonic Evo 4G | MIUI | Tapatalk

Seems like you've gone through the same steps I would've gone through to fix it. Apart from the possible driver issue the phone should still charge when plugged into a wall charger. The fact that it doesn't, in tandem with the inability to access USB via computer, tells me that most likely you've got a hardware failure. Take it to Sprint and get a replacement. Problem solved.

Zuk Z2 Hard Brick

Zuk got hard brick. I can`t run system, telephone only show this:
{
"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"
}
I can't do it anything. Zuk is after flashing.

Same problem, with a description
I am experiencing the same problem.
I bought this phone off someone, and it had the official indian firmware. I unlocked the bootloader, flashed TWRP, then flashed Mokee 7.1.1 and the phone worked great.
Then I got curious and started playing with the phone after I noticed issues with the GPS. What is did to get in this pickle is:
1- Reinstalled Indian official firmware (MM) qith QFIL, which was uneventful. When I set up the phone, I couldn't get OTAs, phone was being read as rooted (which was not);
2- Relocked the bootloader after flashing official Indian ROM (MM), was able to get OTA; Somehow, the phone still was being identified as rooted.
3- Again, with QFIL, I flashed official Chinese MM 1.9.063_ST. Uneventful again, the phone was completely back to stock, no root detected, all official status.
4- After this, once again, with QFIL, I flashed official Chinese Nougat 2.5.334_ST. Uneventful flashing, back to stock;
5- I installed Gapps via apk packages, got the phone to sync my calendar, contacts, etc. I was happy with this but noticed that the phone would not timely display notifications. I could have lived with this by manually checking the phone every now and then for gmail, hangouts, whatsapp, but noooooo, I had to get my hand into it again
6- I tried unlocking the bootloader again, but this time the phone would not be identified or seen by my computer, I could not open port 9008
7- I completely reinstalled windows 10, android studio, drivers (in that order), set up the PC to disable signature verification, etc. I was able to open the port 9008
8- I read on Zukfans that you could get proper Gapps integration by using/flashing Chinese MM 1.9.044_ST with QFIL, and then installing Gapps. I tried that, it worked at times, but still, notifications and sync were basically set to fetch, so I again went back to QFIL nougat chinese official ROM. All this time, the phone was working;
9- I decided to simply go back to Mokee 7.1.1, as it was the best experience I had on this phone. This time I could not unlock the bootloader, I could not open port 9008, and this after a fresh installation of windows 10 (I did try on windows 7 as well, nothing would open the port);
10- I rebooted to bootloader with adb command, and then I accidentally entered the diagnostics/engineering mode. I got the same screen that Człowiek`u posted in the picture and the phone has been stuck in it since;
11- I tried flashing again the official chinese nougat with QFIL and also MiFlash. The port would not open, and I was unable to turn off the phone. The only way I had to shut it down was to the the battery run out completely.
12- I finally used the deep flash method (peeling the charging cable and "short circuiting" the wires), and I finally got the 9008 port open, so I went back to flashing official MM with QFIL. The process worked, and upon restart, the screen would only display the ZUK logo for a few moments, to then simply start flickering black and white; I repeated the process with MiFlash, same result
13- Back to QFIL, this time with Nougat official. After opening the port with deep flash method, flash successfully only for the phone to boot automatically into the diagnostics/engineering mode screen (at least it didn't flicker this time). I repeated the process by using MiFlash, same result.
Does anyone here know of a way to hard reset the bootloader (I guess that's what I have to focus on) so that it does not enter the diagnostics/engineering mode automatically on reboot? Flashing with QFIL, MiFlash is successful, and it should reset everything to normal, but this keeps happening.
When I use the deep flash method for opening port 9008, the phone does go black screen as it should, and the tools correctly identify it as COM3, 4, etc with 9008 open, I get none of those Sahara errors, no 900E message. What can I do?

hey any update i got the same problem here. is it working now?

Pixel 2 XL (rooted) bootlooping to TEAMWIN splash after factory reset

I am helping someone with this phone, so I don't have all the details, but I know the phone was rooted and most likely it was running stock Android 10. It had been working fine until a factory reset (from Android settings I am assuming) was done on it.
1. Now when it turned on, it displays the "Bootloader unlocked" warning:
{
"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"
}
2. After the message, it goes to the Google logo for a second and then to the TEAMWIN splash screen, and it just stays there. I have to long-press the power button to power it off.
3. I can get into the bootloader using the power and volume-down keys, and the "Barcodes", "Restart bootloader" and "Power off" option work, but "Start" and "Recovery mode" just take me back to step 1 and then 2.
So, I cannot get into "Recovery mode". I have also connected the phone to my pc (Ubuntu), but the OS does not detect it, so I cannot use fastboot either.
Any ideas on how to fix this?

If you cant connect to it via fastboot while its in bootloader mode things are grim, thats your best bet at fixing it...
Connect to PC and flash the Android 10 stock ROM by running flash-all.bat while phone is at bootloader
Without editing the flash-all.bat file to remove the -w flashing stock ROM will format user data
Thats it
The state of the phone in the pic does not inspire confidence....
Im starting to think the two things are related....

73sydney said:
If you cant connect to it via fastboot while its in bootloader mode things are grim, thats your best bet at fixing it...
Connect to PC and flash the Android 10 stock ROM by running flash-all.bat while phone is at bootloader
Without editing the flash-all.bat file to remove the -w flashing stock ROM will format user data
Thats it
The state of the phone in the pic does not inspire confidence....
Im starting to think the two things are related....
Click to expand...
Click to collapse
After connecting a working and identical phone to my PC, I found out that the reason my PC didn't detect this phone was that the USB port on phone was dirty and the connector didn't go all the way in.
After I cleaned the USB port I was able to flash the stock ROM to it. I was getting an error mid-way through, so I removed the "-w" as per your advice, tried again and it worked. The phone works now. Thank you 73sydenay!

I would like to mark this thread as solved, but I am not sure how to do that, I don't see an option to edit the title.

droidmart said:
I would like to mark this thread as solved, but I am not sure how to do that, I don't see an option to edit the title.
Click to expand...
Click to collapse
Hi,
You could press edit > advanced and edit your title with:
[SOLVED] Pixel 2 XL (rooted) bootlooping to TEAMWIN splash after factory reset
Cheers...
Sébastien.