Database Info

[Q] How does it boot? (Or, why doesn't mine boot?)

Short version:
My HTC Wildfire gets into HBOOT, but no farther. If I try to load recovery or boot the normal system, it hangs on the normal HTC boot screen. I managed to flash it using RUU_Buzz_Froyo_HTC_WWE_2.22.405.1_Radio_13.55.55.24H_3.35.20.10_release_160191_signed.exe, and the new version numbers are reflected in HBOOT and fastboot getvar, but it still won't boot. What else could be messed up on my phone that would prevent it from loading the system? Can I get diagnostic messages via USB as it loads secondary bootstrap, kernel, etc.?
Long version:
Got Wildfire. Rooted using unrevoked3. Installed CyanogenMod. Everything was great for about a month. Multiple reboots, did some backups with Titanium, installed some seemingly innocent apps.
Friday, I got a new retractable USB cable for my laptop. Plugged it in to the laptop, then the phone. Immediately, the screen went dark. (This was just after updating the Google Maps app.) Phone wouldn't respond to any buttons, so I removed the battery, replaced it, and powered it back up. Ever since, it won't boot anything past HBOOT. If I try to load recovery, or if I try to boot the system normally, it locks hard and I have to remove the battery again.
I've tried loading a PC49IMG.zip from SD, and I tried making a goldcard, but it says, "No Image!" regardless. When it's sitting in HBOOT, I can detect it using fastboot, but not using adb. Fastboot lets me query variables, but nothing jumps out at me as obviously wrong. Of course the phone won't boot a kernel via "fastboot boot ..." either.
I eventually got tired and tried flashing it with the image named above. The RUU claims it worked, and HBOOT gives new version numbers corresponding to what's in the RUU. But the phone still won't boot. (Sadly, it's now HBOOT-1.01.0001.)
After messing around a bit more, I tried flashing the same RUU again, and this time it claims I have the wrong CID. Fastboot says my CID is HTC__038. Here's output of "fastboot oem boot":
Code:
... INFOsetup_tag addr=0xBC900100 cmdline add=0x9C0734CC
INFOTAG:Ramdisk OK
INFOTAG:smi ok, size = 0
INFOTAG:hwid 0x1
INFOTAG:skuid 0x2490B
INFOTAG:hero panel = 0x0
INFOTAG:engineerid = 0x0
INFOMCP dual-die
INFOMCP dual-die
INFOTAG:mono-die = 0x0
INFODevice CID is not super CID
INFOCID is HTC__038
INFOsetting->cid::HTC__038
INFOserial number: [removed]
INFOcommandline from head: no_console_suspend=1 console=null
INFOcommand line length =489
INFOactive commandline: board_buzz.disable_uart3=0 board_buzz.us
INFOb_h2w_sw=0 board_buzz.disable_sdcard=0 diag.enabled=0 board_
INFObuzz.debug_uart=0 smisize=0 userdata_sel=0 androidboot.emmc=
INFOfalse androidboot.baseband=3.35.20.10 androidboot.cid=HTC__
INFO038 androidboot.batt_poweron=good_battery androidboot.carrie
INFOr=HTC-India androidboot.mid=PC4910000 androidboot.keycaps=qw
INFOerty androidboot.mode=normal androidboot.serialno=HT0CSPY021
INFO94 androidboot.bootloader=1.01.0001 zygote_oneshot=off no_co
INFOnsole_suspend=1 console=null
INFOaARM_Partion[0].name=misc
INFOaARM_Partion[1].name=recovery
INFOaARM_Partion[2].name=boot
INFOaARM_Partion[3].name=system
INFOaARM_Partion[4].name=cache
INFOaARM_Partion[5].name=userdata
INFOpartition number=6
INFOValid partition num=6
INFODelay 99994(us) for dpram command before goto AMSS...
FAILED (status read failed (Too many links))
finished. total time: 1.073s
...so, is there any to tell what's going wrong when it tries to boot?

Downgrade htc rhyme

Hi. sorry for bad english
this guide for downgrade htc rhyme on stock rom 1.29.401.3 (RST)
because when you unlocked bootloader, rom increases on 2.0.0.3.....
Recover the full Stock except Relock bootloader.
all the responsibility on you. All personal data will certainly be affected
This procedure will consist of several steps
1 Changing the version number, in order to downgrade firmware was possible.
2 Downgrade device
condition: device must be unlock and have root
Step 1: Changing the version number
condition: bootloader unlock, device is loaded and connected, debugging on.
1. Put the files downloaded from here (aks me) in the tools folder in the root of drive C:
2.Open a command prompt and enter the following code (after each line enter):
cd c:\tools
adb push misc_version /data/local/tmp/misc_version
adb shell chmod 777 /data/local/tmp/misc_version
adb shell
/data/local/tmp/misc_version -s 1.00.000.0
After the introduction of these commands, you should have the following:
--set_version set. VERSION will be changed to: 1.00.000.0
Patching and backing up partition 17...
Note: If you will have an error «Error opening backup file.», Make sure that your memory card is inserted into the phone, not in the computer (make sure the phone is not switched to USB Storage).
3. Enter the code:
# sync
Double-check back to write code and make sure that all the work you have done correctly with the code:
dd if=/dev/block/mmcblk0p17 bs=1 skip=160 count=10
After entering the code should appear:
1.00.000.010+0 records in
10+0 records out
10 bytes transferred in 0.001 secs (10000 bytes/sec)
STEP 2:
1. At the command prompt, type the following command to restart the boot menu (bootloader):
adb reboot bootloader
1.1 Open another command window (not the previous close) and lock bootloader using the instructions from htcdev
1.2 After the locking bootloader device will be reboot ..... hold the lower volume button to enter the bootloader and select the power button fastboot
and back to the first command line window
2. Make sure that your device is recognized by entering the following command:
fastboot-windows devices
3. If your device is properly recognized, it is necessary to return the serial number. Use the code:
fastboot-windows oem rebootRUU
4. Your phone will now restart. The screen of your phone will be black with a gray-silver logo «HTC».
5. After that, we need to reinstall the original firmware. It may take a few minutes, as the transfer of distribution firmware from PC to phone is not fast. Enter the code:
fastboot-windows flash zip StockRom.zip
In rare cases, the installation stops and the user pops up a warning that it is necessary to immediately repeat the installation. Do not panic, just type «fastboot-windows flash zip StockRom.zip» again and it will work.
7. Once it's over, wait a few minutes, then restart your phone, using the code:
fastboot-windows reboot
it's all
You have to be installed in the phone firmware version 1.29.401.3
Is performed on the RST(Russia) rhyme. But there is a chance that this can return any stock rom on any cid. just before it in the folder TOOLS needed to replace an existing zip StockRom, your original zip

download tools from where?

ezab said:
download tools from where?
Click to expand...
Click to collapse
You can get misc_version from here: http://forum.xda-developers.com/showthread.php?t=1399331

hi
actually i have followed all of ur step
but this error always occured
about hboot version is older
C:\Android>fastboot flash zip rom.zip
sending 'zip' (407580 KB)...
OKAY [ 56.535s]
writing 'zip'...
(bootloader) adopting the signature contained in this image...
(bootloader) signature checking...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) checking main version...
(bootloader) checking hboot version...
FAILED (remote: 44 hboot version check fail)
finished. total time: 127.671s

Moto G7 Power is bricked and blank flash will not work.

Hey everyone! First time posting so ill get right into it.
So i have owned the g7 power for a year now and finally decided to root it and install TWRP and a custom ROM.
So i was unable to unlock the boot loader and install TWRP (twrp-installer-3.3.1-2-ocean) then i installed a custom rom (lineage-16.0-20200310-UNOFFICIAL-ocean) and as soon as the install was complete It bricked.
So the Ive installed QDLoader HS-USB Driver_64bit_Setup to have the pc detect the device as "9008"
When I try to run blank flash (blankflash_ocean_PDOS29.114-134-2) this is what i get
Motorola qboot utility version 3.40
[ -0.000] Opening device: \\.\COM5
[ -0.000] Detecting device
[ -0.000] ...cpu.id = 186 (0xba)
[ -0.000] ...cpu.sn = 1780332355 (0x6a1db743)
[ -0.000] Opening singleimage
[ -0.000] Loading package
[ -0.000] ...filename = singleimage.pkg.xml
[ 0.016] Loading programmer
[ 0.016] ...filename = programmer.mbn
[ 0.016] Sending programmer
[ 0.300] Handling things over to programmer
[ 0.300] Identifying CPU version
[ 0.300] Waiting for firehose to get ready
[ 60.712] Waiting for firehose to get ready
[121.226] ...MSM8953 unknown
[121.226] Determining target secure state
[121.226] Waiting for firehose to get ready
[181.712] ...secure = no
[181.747] Initializing storage
[181.747] Waiting for firehose to get ready
[242.376] Configuring device...
[242.376] Waiting for firehose to get ready
[302.984] Waiting for firehose to get ready
[363.522] Waiting for firehose to get ready
[424.147] Waiting for firehose to get ready
[484.660] Initializing storage
[484.660] Waiting for firehose to get ready
[545.187] Configuring device...
[545.187] Waiting for firehose to get ready
[605.781] Waiting for firehose to get ready
[666.434] Waiting for firehose to get ready
[726.988] Waiting for firehose to get ready
[787.535] Waiting for firehose to get ready
[848.115] Configuring device...
[848.118] Waiting for firehose to get ready
[908.767] Waiting for firehose to get ready
[969.484] Waiting for firehose to get ready
[1030.091] Waiting for firehose to get ready
[1090.591] ERROR: do_package()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error
[1090.591] Check qboot_log.txt for more details
[1090.591] Total time: 1090.591s
[1090.591] There were some hiccups in backup and restore.
[1090.591] Please save the following files and see a Bootloader member.
[1090.591] 1) ./qboot_log.txt
[1090.591] 2) ./backup_0x6A1DB743_2020-05-05_130117.img
[1090.591]
FAILED: qb_flash_singleimage()->do_package()->do_recipe()->do_configure()->buffer_read()->device_read()->IO error
And now im stuck. Nothing happens. What am i doing wrong, or maybe im doing it right and I messed up. HELP!!
Thank you!!

https://forum.xda-developers.com/g7-power/help/moto-g7-power-xt1955-5-unlocked-retail-t4070947
SO i fixed it using that link but now i need assistance on how to install the factory rom using fast boot

pluminam said:
https://forum.xda-developers.com/g7-power/help/moto-g7-power-xt1955-5-unlocked-retail-t4070947
SO i fixed it using that link but now i need assistance on how to install the factory rom using fast boot
Click to expand...
Click to collapse
Code:
fastboot getvar all
To find the correct codename and software channel for the firmware
Product = codename
securestate = bootloader locked or unlocked
carrier_sku = Model #
ro.carrier = Software Channel
See
https://forum.xda-developers.com/general/rooting-roms/guide-flashing-motorola-firmware-t4042039

Mine keeps saying singleimage failed

Punkfool18 said:
Mine keeps saying single image failed
Click to expand...
Click to collapse
Change your PC, use different USB cable, different USB ports. Join Telegram group for more help here, they helped me to fix mine.
here
https://t.me/mG7Power

Moto G7 Power XT1955-2 HardBrick Solution
Link of Auto Installer by Strakios:
drive.google.com/file/d/1Wi85_qqKNBxRDzVkTUUcU2HTtiuz6hHt/view
Strakios 13/05/2020
XT1955-2 OCEAN_PPOS29.114-134-10
Todo el Contenido se Instala en C:\XT1955-OCEAN
1 - INSTALAR DRIVERS
2 - ACTIVAR EDL MODE(EMERGENCY DOWNLOAD MODE)
3 - INSTALAR SLOT A/B (BLANKFLASH)
4 - DESCARGAR ROM STOCK PARA XT1955-2 OCEAN
5 - FLASHEAR STOCK FIRMWARE
drive.google.com/file/d/1Wi85_qqKNBxRDzVkTUUcU2HTtiuz6hHt/view

Post-factory reset problems

I performed a factory reset on my Redmi Note 6 Pro and it seems things went wrong as it now won't boot. When I turn it on, I get the Mi.com screen for a few seconds then nothing. I did some googling and decided to try a fastboot flash. This did not work with an error "Flash xbl error"
Here is the log:
MiFlash 2020.3.14.0
vboytest index:1
idproduct: 53261 idvendor: 6353
Thread id:10 Thread name:95c0959
image path:C:\Users\User\Desktop\tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global
env android path:"C:\Users\User\Desktop\MIUI_Flash\Source\ThirdParty\Google\Android"
script :C:\Users\User\Desktop\tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global\flash_all_lock.bat
Physical Memory Usage:1044480 Byte
start process id 2968 name cmd
info1:$fastboot -s devicename getvar product 2&1 | findstr /r /c:"^product: *tulip" || echo Missmatching image and device
info1roduct: tulip
info1:$fastboot -s devicename getvar product 2&1 | findstr /r /c:"^product: *tulip" || exit /B 1
info1roduct: tulip
info1:$set CURRENT_ANTI_VER=4
info1:$for /F "tokens=2 delims=: " %i in ('fastboot -s devicename getvar anti 2&1 | findstr /r /c:"anti:"') do (set version=%i )
info1:$(set version=4 )
info1:$if [4] EQU [] set version=0
info1:$if 4 GTR 4 (
info1:echo current device antirollback version is greater than this package
info1: exit /B 1
info1
info1:$fastboot -s devicename flash xbl C:\Users\User\Desktop\tulip_global_images_V12.0.1.0.PEKMIXM_20201229.0000.00_9.0_global\images\xbl.elf ||
info2:Sending 'xbl' (2504 KB) OKAY [ 0.078s]
info1:"Flash xbl error"
info2:Writing 'xbl' FAILED (remote: 'Flashing is not allowed in Lock State')
info2:fastboot: error: Command failed
begin FlashDone
error:"Flash xbl error"
process exit.
flashSuccess False
isFactory False CheckCPUID False
before:flashSuccess is False set IsUpdate:True set IsDone True
after:flashSuccess is False set IsUpdate:false set IsDone true
Click to expand...
Click to collapse
Can anyone assist? I see the "flashing is not allowed in lock state" message but my various googlings seem to suggest I shouldn't need to unlock? Perhaps I do (I did start down that path but got a bit stuck - will persevere if that is the issue).

Managed to get into Recovery mode on the device and that fixed it. No need to flash after all.

how to unlock frp huawei p9 lite

this is a google translation sorry for mistakes.
I have a huawei p9 lite vns l31. i unlocked both frp and bootloader to try to root. I have installed the recovery revolution.
surely I made wrong maneuvers and now I find myself with this situation:
Bootloader unlocked
FRP lock
the operating system is blocked
when I try to start in recovery mode revolution appears for a few seconds and then the phone turns off and restarts with the message "your device is booting now" and remains blocked.
all the commands I send on the pc with fastboot returns me
"" C: \ adb> fastboot flash recovery twrp.img
target reported max download size of 471859200 bytes
sending 'recovery' (22432 KB) ...
OKAY [0.552s]
writing 'recovery' ...
FAILED (remote: Command not allowed)
finished. total time: 0.561s ""
this is probably due to the blocked FRP?
Correct??
If this is the cause how can I unlock FRP ??

People typically remove all existing locks as also FRP before modding Android.
If phone is accessible by ADB you can try these ADB commands - one by one - to remove FRP lock:
Code:
adb devices
adb shell "am start -n com.google.android.gsf.login/"
adb shell "am start -n com.google.android.gsf.login.LoginActivity"
adb shell "content insert --uri content://settings/secure --bind name:s:user_setup_complete --bind value:s:1"
adb reboot