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

Help! I soft bricked my Pumpkin head unit and need help fixing it!!!

I have a pumpkin rk3188, 2gb ram, 32gb nand, 7" head unit (http://www.autopumpkin.com/car-dvd-...-gps-obd2-wifi-3g-steering-wheel-control.html) and I tried to get @Malaysk rom on it, but it wouldn't let me into bootloader or recovery no matter what I did, even with root bootloader just rebooted system and recovery went to recovery but just ran a factory reset script without giving me any options. So I tried to flash a factory image using the gps sd and naming it update.img, now the boot logo is different and it's stuck in a boot loop and I still can't get into bootloader or recovery. And I've tried to put another update.img on the sd card, but it does nothing. Is there anything I can do or am I sol?

I did the alt prtscr I trick with a USB keyboard plugged in n seem to have gotten to some menu but it's off the screen for some reason. I can see the edge of a highlight bar that I can move with the arrows up n down, n a thin line at the end of the list, whatever the list says idk. There's 7 options tho, it seems like the first attempts to boot, the second n third do something bit idk what, n the rest just return to this menu. It's orange btw. I'm going to upload pics of what I see. Can anyone help me figure out what this menu is n if I can use it to fix me unit? Thx!
{
"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"
}
Sent from my VS990 using XDA-Developers mobile app

Same here bro. Flashed malaysk rom. Lost the recovery.

chezimus said:
Same here bro. Flashed malaysk rom. Lost the recovery.
Click to expand...
Click to collapse
I GOT IT!!!! I got it back up n running the pumpkin firmware!!! Idk about u man, but I figured out/git lucky with the orange recovery or bootloader I had n couldn't see the writing. I got the official firmware from pumpkin for this unit n downloaded the right mcu img, put them both on the sd card n put it into the GPS slot, then used the keyboard to get to the orange screen n the option that worked was the 3rd one down. It took a while, 15-20 minutes of nothing but a black screen, but it finally came back up with the boot logos. It was stuck at the boot logos again so I reset n did the alt prtscr I trick again to get to recovery again n it wiped n reinstalled the img n bam it worked! Slow first load but it worked! Let me know if u need the files or help.
Sent from my VS990 using XDA-Developers mobile app

I've been fighting the same problems. I would love the files too. Which mcu img did you use.

For my pumpkin unit it's a bin file, they call it project-car.bin. There's a mcu updater that uses bin files in the settings. The stock recovery doesn't recognize mcu.img sadly. I uploaded the project-car.bin here (https://drive.google.com/file/d/0B2T5FQZ-WJDQS3hXVFFFTnIwaGc/view?usp=drivesdk) and you can get the stock rom from pumpkin here (https://mega.nz/#!lc9HAbLK!nAIsEvYnSwqCV47vCmMRKBVivygxaJbGD3KPV0pxvZ8)
Sent from my VS990 using XDA-Developers mobile app

They same thing happened here too. Just a boot loop and no way to get into recovery with the buttons.
Could you please tell how the mentioned trick works?
alt prtscr I trick with a USB keyboard
Click to expand...
Click to collapse
Thank you very much in advance!

Could you please tell how the mentioned trick works?
Use a USB keyboard attached to the head unit's USB port. Either port should work. After powering the HU or resetting, press and hold the alt and prtscr keys, then press and release the "i" key. It should then boot into recovery. If not, repeat.

Hello， can you tell me what can bus options you have in factory settings. Mine have only BMW 1，2，3，4 . no another car. And reverse camera is to black.
Thank you.

Xiaomi MI5S is dead after MIUI update?!

Hi everyone,
After last MIUI update, my MI5S (Global) is not responsive anymore. I tried all the combinations of power and volume buttons, but the screen remains black.
The only answer I got is an error after running MiFlash :
{
"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, summing up:
1) Doesn't startup on pressing power button.
2) Phone doesn't start in recovery mode.
3) Phone doesn't enter fastboot mode ( power + volume down).
4) No notification led showing battery charging status.
Best regards,
Tiago

tbmm said:
Hi everyone,
After last MIUI update, my MI5S (Global) is not responsive anymore. I tried all the combinations of power and volume buttons, but the screen remains black.
The only answer I got is an error after running MiFlash :
So, summing up:
1) Doesn't startup on pressing power button.
2) Phone doesn't start in recovery mode.
3) Phone doesn't enter fastboot mode ( power + volume down).
4) No notification led showing battery charging status.
Best regards,
Tiago
Click to expand...
Click to collapse
Find any Linux PC, install adb on it and install recovery through fastboot mode ( Mi bunny on phone, fastboot command in console ).

Hi BlackJetCat,
The thing is, I cannot see any bunny on the phone because the screen is always black and besides that, I'm getting the message ""waiting for device" after executing "fastboot boot recovery.img".
I don't know if I'm doing something wrong.
Thanks for your help.

Wow, you don't see anything on screen? Try to press Vol- + Power for until you see FASTBOOT text and picture. If not helped, try to find any unbricking instruction for SD821. Also you can turn off and on battery [only by taking off back cover]. Maybe your problem related to screen or power controller.
sorry for bad english, this is my 3rd language

Maybe you can try "deep flash", search on web about it, it needs a simple cable to flash. Search deep flash for mi5s.

BlackJetCat said:
Wow, you don't see anything on screen? Try to press Vol- + Power for until you see FASTBOOT text and picture. If not helped, try to find any unbricking instruction for SD821. Also you can turn off and on battery [only by taking off back cover]. Maybe your problem related to screen or power controller.
sorry for bad english, this is my 3rd language
Click to expand...
Click to collapse
I cannot see anything on the screen. I already searched for some unbricking solutions, but without success. I was able to flash the phone using Mi Flash, but nothing more. Mi Flash is the only place where the phone is detected.
Creative9170 said:
Maybe you can try "deep flash", search on web about it, it needs a simple cable to flash. Search deep flash for mi5s.
Click to expand...
Click to collapse
I didn't try deep flash or removing the battery. Do you know if that would void the warranty?
Thanks for your help.

tbmm said:
I cannot see anything on the screen. I already searched for some unbricking solutions, but without success. I was able to flash the phone using Mi Flash, but nothing more. Mi Flash is the only place where the phone is detected.
I didn't try deep flash or removing the battery. Do you know if that would void the warranty?
Thanks for your help.
Click to expand...
Click to collapse
It doesn't need opening the phone, you just need to make a simple cable or buy it and flash device with Xiaomi Flash tool.
Here is a guide: https://forum.xda-developers.com/mi-5s/how-to/guide-flash-xiaomi-mi-5s-chinese-rom-to-t3530834
Update: I think it doesn't void warranty because its not kind of unlocking or opening the phone case.

Fix Blootloader and Logo

I have a problem with a Nexus 5x and I wanted to see if you can help me. I would really appreciate it
Yesterday I answered a spam call . And from there and I had problems, I was slow, I quickly downloaded the battery and suddenly it went out, hence it is no longer the Google logo.
I am not so new in this. I tried to enter the recovery mode and delete everything, but it will not let me enter, it returns to Fastboot mode.
- Have the boot manager blocked.
- I do not have the OEM option open.
-I can not enter the recovery mode.
- The PC if it recognizes it by Fastboot mode
What I can do?
I hope you can help me. Thanks for your attention.

al3al3al3jandr0 said:
I have a problem with a Nexus 5x and I wanted to see if you can help me. I would really appreciate it
Yesterday I answered a spam call . And from there and I had problems, I was slow, I quickly downloaded the battery and suddenly it went out, hence it is no longer the Google logo.
I am not so new in this. I tried to enter the recovery mode and delete everything, but it will not let me enter, it returns to Fastboot mode.
- Have the boot manager blocked.
- I do not have the OEM option open.
-I can not enter the recovery mode.
- The PC if it recognizes it by Fastboot mode
What I can do?
I hope you can help me. Thanks for your attention.
Click to expand...
Click to collapse
When you try to enter recovery mode what does it look like? Can you post a picture?
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
When you try to enter recovery mode what does it look like? Can you post a picture?
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
1.- I put in fastboot mode
2.- I give it in recovery mode
3.- The logo starts and from there it repeats repetitively in the logo
{
"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 it never gets to recovery. It just tries to reboot? Without oem unlock I'm not sure what you'll be able to do.
Sent from my [device_name] using XDA-Developers Legacy app

jd1639 said:
So it never gets to recovery. It just tries to reboot? Without oem unlock I'm not sure what you'll be able to do.
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
It never starts, it just stays there.
There is some way to force it to start?

al3al3al3jandr0 said:
It never starts, it just stays there.
There is some way to force it to start?
Click to expand...
Click to collapse
Not sure if this would really help but keeping your phone in the refrigerator for few hours would let you turn it on. Then quickly enable the USB Debugging and OEM Unlocking. I had the bootlooping issue and freezing the phone really worked in terms of enabling the USB Debugging and OEM Unlocking. Then you should be able to sideload an update.

What's the Expected Level of Support from Google Support?

TL;DR: Really three questions
What kind of effort can/should we expect from Google Support?
Is there an escalation support path for real troubleshooting?
What's the best course of action to attempt to determine root cause?
The Setup
While driving to work this morning my stock Pixel 2 XL (locked, not rooted etc.) entered a boot loop then settled on this error (image):
Code:
Android Recovery
Can't load Android system. Your data may be corrupt. If you continue to get this message, you may need to perform a factory data reset and erase all user data stored on this device
I couldn't do much since I was driving but I selected 'Try again' a number of times when traffic stopped before giving up.
When I arrived at work I continued fiddling with it for a few hours, select 'Try again', power off, power on, fastboot etc.
Although debugging was enabled prior, could only see a device in fastboot or when in adb sideload mode.
When I attempted to go into recovery mode it would just take me back to the same screen.
I just assumed I'd have to wipe and start over
About 2 hours ago I was getting ready to factory reset/wipe the phone but thought I'd try fidgeting once more like I had been doing all day.
I don't know what I did but it booted to a screen displaying this error:
Code:
No valid operating system could be found.
The device will not boot.
Visit this link on another device
g.co/ABH
{
"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"
}
Then the phone turned off.
I turned it back on, and I don't think I did anything differently, and suddenly it booted normally.
The only unusual thing I saw was a notification stating that Android was finishing up system updates - or something to that effect.
With the phone up, I backed up what little data had not yet been backed up, booted into safe mode then booted back into normal mode.
So far so good...?
My Complaint
I contacted Google support earlier in the day and the experience was just sad.
The person said that I would need to factory reset my phone.
But then quickly said that before doing so I would need to backup my data.
So I asked "How?" and they said "plug it into your machine and you can see it on your computer"
I went along with their script, specifically asking for detailed step by step instructions on what to do, how to do it and what to look for.
When I said it didn't work they said I would have to take it to a repair center first to get it repaired then once fixed I could back it up then perform the factory reset.
*smh*
Later, about 2.5 hours ago now, once the phone came back up, I backed up what little data needed backing up and contacted support a second time.
This time, the person said: "Now, if we need to restart the phone and check if the boot looping is triggered or not. If it does, then we need to do some troubleshooting steps here."
So I naturally asked "What are the troubleshooting steps if it enters into that state again?" but they couldn't provide any.
I just want to know root cause. Since this was an OS boot problem, surely there's a log somewhere that might reveal what happened or at the very least provide a clue. Right?