Develop Bugs

[Q] Xperia S dead + W8.1 drivers issues

First of all sorry for my bad english
Today i've tried to install the SlimKat rom i made the process exactly and i didn't have any trouble, when i restarted the phone just died the screen didn'd react, the only response was a short vibration... Then i plugged the phone to restore to a stock rom through Flashmode, when i did it it just long like 3~8 seconds and my PC doesn't recognize flashmode (forgot to install drivers, facepalm) so i've made that process and tryed again... Same problem, so i decided to make a hard reset (power buttor and volume + and wait for the 3 vibrations), plugged the phone again and the same issue.
Any way to save my device or just make my pc recognize Flashmode?
Thanks and merry xmas.
PS: Xperia S with locked bootloader.

power buttor and volume + and wait for the 3 vibrations = power off (switched off)
power buttor and volume + and wait for the 1 vibrations = restart phone
phone is switched off: vol up + usb = fastboot mode (flashtool)
phone is switched off: vol down + usb = flash mode (flashtool)

mmarta said:
power buttor and volume + and wait for the 3 vibrations = power off (switched off)
power buttor and volume + and wait for the 1 vibrations = restart phone
phone is switched off: vol up + usb = fastboot mode (flashtool)
phone is switched off: vol down + usb = flash mode (flashtool)
Click to expand...
Click to collapse
I know that but flashboot last no more than 5 seconds...

EXACT same issue here man, will let you know if I have any solutions.

I had the same issue, but got it working now.
You need to turn off Windows driver signature enforcement in Windows 8 and above. Google "disable driver signature enforcement windows 8" (without quotes), you'll find plenty of How-tos with screenshots. After you got that, install Flashtool-drivers.exe from Flashtool drivers folder. Windows should recognize your phone as Bootloader interface, or something like that.

Doctor0710 said:
I had the same issue, but got it working now.
You need to turn off Windows driver signature enforcement in Windows 8 and above. Google "disable driver signature enforcement windows 8" (without quotes), you'll find plenty of How-tos with screenshots. After you got that, install Flashtool-drivers.exe from Flashtool drivers folder. Windows should recognize your phone as Bootloader interface, or something like that.
Click to expand...
Click to collapse
I don't know, I have been trying to do this on my 8.1 and didn't worked.

yUlekk said:
I don't know, I have been trying to do this on my 8.1 and didn't worked.
Click to expand...
Click to collapse
What he said works only on W8,on W8.1 i found no solution yet.What i did is install W7 on a other partition of my HD,only to install and run ADB and Flashtools.

[Q] LG P 350 is not turning on

My LG P 350 is not turning on .When switched on its stuck in the initial black screen with the LG logo in the center . This is what I did.
I rooted my LG P350 with gingerbreak .
Then I installed ClockWorkRecovery after that I flashed MiniCM10-4.0.2-20121207-UNOFFICIAL-ALPHA2-p350.zip from the clockworkmod ROM recovery page .
The phone then rebooted and went into fastboot mode from there I followed these instructions:
1. Firstly download Android Flash Recovery & Amonra Recovery to your machine & unzip it.
2. Now switch on your phone & wait for the fastboot message. Connect it to your Computer using USB Cable.
3. Next step is to execute androidflashrecovery.exe from the Android Flash Recovery folder. You should get the message Device:Connected at the bottom of the window.
4. In case your device is not discovered/Connected then try below options & Retry Step 3.
- Try from a Different Machine preferably Windows XP.
- Download PDANet & Install the Application (Let it Install the Drivers).
5. Now click on the browse button & select recovery file under recovery-amonra folder.
6. Check the status in your device, in 2-3 minutes the device should go into recovery mode.
But step 6 just did not happen the phone rebooted and got stuck in the black screen with the LG logo and after sometime the back light of the soft buttons starts blinking like crazy. No buttons work . I cant even switch it off.

Hard Brick Solution for MI MAX 2 (when device manager shows Qualcomm HS-USB 9008)

This method works for the Mi Max 2 phones (or probably for other Mi phones) when the screen is stuck in black and power button does not work and when you connect device to the PC you see it as Qualcomm HS-USB 9008 or 9006....
(if you see QHUSB_BULK in device manager (or nothing) you should install drivers as mentioned in link below otherwise skip this) en.miui.com/thread-737909-1-1.html
1. Download Fastboot Rom from this link (the file extension should be .tar or .tgz or .tg) be careful in selecting right device:
en.miui.com/a-234.html
2. Download and install MiFlash tool on PC:
xiaomiflashtool.com/category/download
3. Extract Downloaded rom into a folder
4. Run MiFlash and Browse to select the folder you extracted rom
5. (IMPORTANT STEP, READ CAREFULLY) hold down VOL+ and VOL- buttons simultaneously and connect phone to PC, as soon as possible click on REFRESH and then FLASH buttons. (THIS MUST BE DONE QUICKLY otherwise you will face the error cannot receive hello packat. if you face this error, disconnect the phone from PC, hold down POWER button for at least 20 seconds NOT LESS and close MiFlash and re-open it and repeat step 5)
6. Wait until flashing is done.
7. Disconnect Phone from PC and hold down POWER button until it vibrates.

Android 11 not booting Magisk

Hello -
upgraded from Android 10 to 11 with Odin in the usual way.
However the old key combo no longer works. I managed to boot with magisk only once. Reflashed the magisk patched.
I can boot into recovery by insterting a USB-C headphone cable, pressing power on, then pressing volume-up and power on.
I only managed to boot into Magisk once "by accident". A long press on volume down with power causes the phone to reboot. A short press on volume down with power does nothing. A long press on volume up with power brings me into recovery.
Any hints? tried reflashing Android 10 but of course the bootloader doesn't let be because of rollback protection.
How does one boot into Magisk now that recovery needs a cable?
Thanks

Fixed. A module was causing Magisk not to load. Here is the incantation to load Magisk on a Note 10+ with that bad operating system:
a) on the computer:
1) install the latest adb
2) open a "powershell" (shift and right-click on an open space in the folder where adb has been extracted)
3) start the adb daemon with ./adb start-server
b) on the working phone
1) turn off USB debugging
2) revoke authorisations
3) turn on USB debugging
4) connect the phone to the computer with a cable - allow USB debugging from this computer "all the time" (not once!)
5) detach phone
6) turn off phone
c) on the computer:
1) give the command ./adb wait-for-device shell magisk --remove-modules
d) back to the phone
1) attach the phone to the computer
2) turn it on by pressing shortly just the power key, you will get a warning about "phone bad, bootlocker unloaded"
3) quickly press power and volume up, keep them pressed "a short while" (you will get it by trial and error)
4) you then will get a second triangle on the bottom saying press power to start
5) it will seem like the phone is stuck in the bootscreen, it's not
6) let it boot. The command in the "powershell" will execute, it won't show success or anything
7) the phone will reboot
8) unplug the phone from the computer
9) turn the phone off again
repeat steps d1 to d5. While the phone is booting "after some time" unplug it again from the computer
if you are lucky then maybe you booted up with Magisk and no modules.
Very simple and straight-forward. With the hardware key-attestation and this I see that Google and Samsung with every update are getting more friendly for the consumer. Somehow imho they don't understand that if Android users wanted an "applified" phone that they can't play with, they would get an apple.
Good luck

Surface RT stack on BSOD's 0xc000000f & 0xc0000428

Hello! Last week I bought used Surface RT 64 Gb Model: 1516 with next problem:
BSOD
Recovery​​Your PC needs to be repaired.​​A required device isn't connected or can't be accessed.​Error code: 0xc000000f​​You'll need to use the recovery tools on your installation media. If you don't have any​installation media (like a disc or USB device), contact your system administrator or PC manufacturer.​
If I try to press the Windows key to "try again", I get:
BSOD
Recovery​​Your PC needs to be repaired.​​Windows cannot verify the digital signature for this file.​​File: \WINDOWS\System32\winload.efi​Error code: 0xc0000428​
You'll need to use the recovery tools on your installation media. If you don't have any
installation media (like a disc or USB device), contact your system administrator or PC manufacturer.
I've tried download the Recovery Image from Microsoft for my Surface RT (using serial number). Use official manual for creating Recovery USB (format flash in FAT32 and copy files from downloaded archive, Press Volume- & Power Release & Release Volume- after Surface logo shown). Trying to boot from USB - nothing happen, I got BSOD! Trying to enter UEFI/BIOS (Press Volume+ & Power Release & Release Volume+ after UEFI/BIOS shown) - nothing happen, I got BSOD! Everytime I got same errors: first 0xc000000f and 0xc0000428 after pressing Win Key.
I use different Recovery Images for different regions with Win 8.0RT and Win 8.1RT, find & download ready custom images and trying to boot from... Use USB flash-drive 2.0 and 3.0 (different sizes 8 Gb, 32 Gb)
The tablet does not respond to connected USB flash-drive (but USB port is Ok). I've tried to boot from MicroSD :/ And nothing again!
I am tired please help me to solve this problem

silkway said:
Hello! Last week I bought used Surface RT 64 Gb Model: 1516 with next problem:
BSOD
Recovery​​Your PC needs to be repaired.​​A required device isn't connected or can't be accessed.​Error code: 0xc000000f​​You'll need to use the recovery tools on your installation media. If you don't have any​installation media (like a disc or USB device), contact your system administrator or PC manufacturer.​
If I try to press the Windows key to "try again", I get:
BSOD
Recovery​​Your PC needs to be repaired.​​Windows cannot verify the digital signature for this file.​​File: \WINDOWS\System32\winload.efi​Error code: 0xc0000428​
You'll need to use the recovery tools on your installation media. If you don't have any
installation media (like a disc or USB device), contact your system administrator or PC manufacturer.
I've tried download the Recovery Image from Microsoft for my Surface RT (using serial number). Use official manual for creating Recovery USB (format flash in FAT32 and copy files from downloaded archive, Press Volume- & Power Release & Release Volume- after Surface logo shown). Trying to boot from USB - nothing happen, I got BSOD! Trying to enter UEFI/BIOS (Press Volume+ & Power Release & Release Volume+ after UEFI/BIOS shown) - nothing happen, I got BSOD! Everytime I got same errors: first 0xc000000f and 0xc0000428 after pressing Win Key.
I use different Recovery Images for different regions with Win 8.0RT and Win 8.1RT, find & download ready custom images and trying to boot from... Use USB flash-drive 2.0 and 3.0 (different sizes 8 Gb, 32 Gb)
The tablet does not respond to connected USB flash-drive (but USB port is Ok). I've tried to boot from MicroSD :/ And nothing again!
I am tired please help me to solve this problem
Click to expand...
Click to collapse
Hi I have same problem and have tried everything you have did you fix it

There is a bare metal recovery guide here:
Bare Metal Recovery - Windows
Resetting a Windows RT device using a recovery image
jwa4.gitbook.io
The device is not bootable from SD and it will only boot from USB if holding volume - while powering on.

jwa4 said:
There is a bare metal recovery guide here:
Bare Metal Recovery - Windows
Resetting a Windows RT device using a recovery image
jwa4.gitbook.io
The device is not bootable from SD and it will only boot from USB if holding volume - while powering on.
Click to expand...
Click to collapse
Thanks buddy I will give it a go