Develop Bugs

Desire won't boot

Hi
Messed up my desire a while back. It won't boot. When I turn it on I get this screen
When I plug it in to PC then unplug it I get this screen
Can't flash any RUU. Can't access recovery. Just nothing. Anyone any ideas what I can do?
Sent from my GalaxyS2 with CM9

Hm, no fastboot. Does it recognize it if you connect the phone to your pc? Your PC may see a USB serial console that accepts commands.
Google for "HbootAnalysis" to get a list of commands.
The gotofastboot commands looks worth a shot. Once in fastboot you should be able to flash anything you want.

The phone reacts, and the computer knows there is something there. Just not a phone...
Sent from my GalaxyS2 with CM9

So you cannot even access fastboot?

No
Sent from my GalaxyS2 with CM9

This is probably extremely unhelpful so I apologise but what did you do/what happened to the Desire to make it (what seems to be) stuck in a loop?

this is a partition/radio brick
it usually happens when you try and RUU a device when its using the new alpharev hboots that do not have the right sizes (hes using the sense hboot which doesnt use stock sizes)
so basically it kills the partitions. this is because alpharev put that "annoying" hboot protection on to stop RUU's from overwriting it. i love the alpharev team but that really isnt needed
I dont think its possible to fix this without being able to get to fastboot as we need to get the hboot flashed with stock sizes

Stuck on the way RRU
I encountered the same problem today:
My solution:
You need Android-sdk with fastboot command
"fastboot devices" work for me
I got my last backup ClockworkMod on my sdcard
/clockworkdmod/backup/2012-01-16-18.04.51/
width these files:
boot.img
data.yaffs2.img
system.yaffs2.img
recovery.img
...
I flashed these files
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.yaffs2.img
fastboot flash userdata data.yaffs2.img
Then I tried the boot
fastboot oem boot
Iit worked !
After the reboot I stood on this page RUU (hboot)
To erase the RRU Flag on fastboot:
fastboot oem resetRUUflag
And now all is working on my cyanogen 7 NB
Try for Yourself
fxjumper

fxjumper said:
I encountered the same problem today:
My solution:
You need Android-sdk with fastboot command
"fastboot devices" work for me
I got my last backup ClockworkMod on my sdcard
/clockworkdmod/backup/2012-01-16-18.04.51/
width these files:
boot.img
data.yaffs2.img
system.yaffs2.img
recovery.img
...
I flashed these files
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.yaffs2.img
fastboot flash userdata data.yaffs2.img
Then I tried the boot
fastboot oem boot
Iit worked !
After the reboot I stood on this page RUU (hboot)
To erase the RRU Flag on fastboot:
fastboot oem resetRUUflag
And now all is working on my cyanogen 7 NB
Try for Yourself
fxjumper
Click to expand...
Click to collapse
indeed this should work
he said he cant boot to fastboot though, are you saying you can use fastboot in the RUU screen?

yes i can enter fastboot command
but after these stuff, i loosed my name/serial_number in adb but not in fastboot
my new adb username/serial_number is 1234567890ABCDEF

Stock Kernel for Primo U (CID HTC__J15)?

Hi guys,
I was wondering if anyone had the stock Kernel for the PrimoU HTC One V. If anyone does, can they supply me with it?
Thank you,
-M

Here you go...

Umm, is that what I need to revert to stock? (Kernel + Recovery?)
-M

Flashing RUU to revert to stock
- you must have the correct RUU for your device.
- if you are not sure, download CID Getter from Play Store and run it, it will show your CID.
- with your CID, you may be able to find a correct RUU for your device
then (even though some people may not agree with this, but this will bring no harm and it is noob-proof) do this:
1- flash a stock recovery.img
fastboot flash recovery recovery_signed.img
fastboot reboot-bootloader
fastboot erase cache
2- flash a stock boot.img
fastboot flash boot boot_signed.img
fastboot reboot-bootloader
fastboot erase cache
3- re-lock bootloader
fastboot oem lock
fastboot reboot-bootloader
fastboot erase cache
4- flash RUU

[Q] Flashed boot.img now looping splash screen

Hello,
I've been running ARHD ICS for a while now so decided to upgrade to ARHD JB tonight. Flashed HBOOT and boot.img fine, however for some reason after flashing boot.img my phone tried to reboot. Reaches the white HTC splash screen (with the green HTC logo) and doesnt go any further.
When I try to reboot back into recovery, nothing happens it just gets stuck at the splash screen again!
Any ideas? I assume this is because I'm running JB firmware and a ICS rom at the minute, so I just need to get back into recovery to flash the JB ROM.
Any help would be appreciated

Whats your hboot version ? did you ever updated the phone to JB ?
do :
fastboot getvar version-main
and post the result here please

Mr Hofs said:
Whats your hboot version ? did you ever updated the phone to JB ?
do :
fastboot getvar version-main
and post the result here please
Click to expand...
Click to collapse
version-main: 1.29.061.11
I've managed to flash ARHD 21. However still the same thing happens. Reboot gets stuck at the splash screen.

jayc89 said:
version-main: 1.29.061.11
I've managed to flash ARHD 21. However still the same thing happens. Reboot gets stuck at the splash screen.
Click to expand...
Click to collapse
yeah you need to update the hboot first in order to run JB....none of them will run.
i will get you a ruu to get back to full stock, then you can update to ICS 404 and then to JB 3.14

Mr Hofs said:
yeah you need to update the hboot first in order to run JB....none of them will run.
i will get you a ruu to get back to full stock, then you can update to ICS 404 and then to JB 3.14
Click to expand...
Click to collapse
Hmmm, strange. In fastboot, HBOOT says it's at version 1.36.0000
I flashed it from Mike's thread here; http://forum.xda-developers.com/showthread.php?t=1957376
My CIDNUM is ORANG001

oke what commands did you use ?
Try this :
fastboot erase cache (and try to enter the recovery)
did you made a full wipe before installing the new rom ?
and this is the command for flashing the boot.img :
fastboot flash boot boot.img (not fastboot boot boot.img, that will indeed reboot the phone)

Mr Hofs said:
oke what commands did you use ?
Try this :
fastboot erase cache (and try to enter the recovery)
did you made a full wipe before installing the new rom ?
and this is the command for flashing the boot.img :
fastboot flash boot boot.img (not fastboot boot boot.img, that will indeed reboot the phone)
Click to expand...
Click to collapse
erase cache got me into recovery but still doesnt pass the white screen when I reboot.
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot
fastboot oem get_identifer_token
fastboot flash unlocktocken Unlock_code.bin
fastboot flash recovery recovery-clockwork-touch-5.8.3.1-endeavoru.img
fastboot erase cache
fastboot reboot
*Flashed ARHD 21 from CWM*

jayc89 said:
erase cache got me into recovery but still doesnt pass the white screen when I reboot.
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot
fastboot oem get_identifer_token
fastboot flash unlocktocken Unlock_code.bin
fastboot flash recovery recovery-clockwork-touch-5.8.3.1-endeavoru.img
fastboot erase cache
fastboot reboot
*Flashed ARHD 21 from CWM*
Click to expand...
Click to collapse
C:\Android\android-sdk\platform-tools>fastboot flash boot boot.img
sending 'boot' (4982 KB)...
FAILED (command write failed (Unknown error))
finished. total time: 0.648s

jayc89 said:
erase cache got me into recovery but still doesnt pass the white screen when I reboot.
fastboot oem lock
fastboot oem rebootRUU
fastboot flash zip firmware.zip
fastboot reboot
fastboot oem get_identifer_token
fastboot flash unlocktocken Unlock_code.bin
fastboot flash recovery recovery-clockwork-touch-5.8.3.1-endeavoru.img
fastboot erase cache
fastboot reboot
*Flashed ARHD 21 from CWM*
Click to expand...
Click to collapse
EDIT : UNLOCK the bootloader first !
first flash a new recovery, yours is old. https://www.dropbox.com/s/qsurumd3gs0vkar/Philz recovery 5.3.0.img
then flash the boot.img from the ARHD rom
fastboot erase cache
fastboot flash boot boot.img
fastboot erase cache
then make a full wipe in the recovery
Factory reset
wipe cache partition
advanced - wipe dalvik cache
mounts and storage - format cache, data, system
then install the new rom !

Thanks for that, I've managed to boot into the new ROM, however I dont have any signal now. I've gone to select the operator manually and Orange isnt available. My SIM works fine in another phone.

jayc89 said:
Thanks for that, I've managed to boot into the new ROM, however I dont have any signal now. I've gone to select the operator manually and Orange isnt available. My SIM works fine in another phone.
Click to expand...
Click to collapse
Did you actually flash the boot.img that is inside the ARHD rom.zip ? If not, do so !

Mr Hofs said:
Did you actually flash the boot.img that is inside the ARHD rom.zip ? If not, do so !
Click to expand...
Click to collapse
Yes I have.

well i could say , try a different rom .....just to test. otherwise reflash the firmware again all over. fastboot getvar version-main should also give a 3.14 number !

I reflashed the boot.img again after flashing the ARHD ROM and it looks to be working now. Thanks for all your help!

jayc89 said:
I reflashed the boot.img again after flashing the ARHD ROM and it looks to be working now. Thanks for all your help!
Click to expand...
Click to collapse
Ah nice ! Very good :thumbup:
CASE CLOSED !

Mr Hofs said:
Ah nice ! Very good :thumbup:
CASE CLOSED !
Click to expand...
Click to collapse
Wow! I just had the same problem! But it is solved now thanks to your excellent help! :laugh:

well thanks tosti ! hahah nice name
Your case is CLOSED TOO !

No bootloader , no recovery!

So,recently i switched from cm14.1 back to cm13 and when i did that, i forgot to downgrade the bootloader,so after i flashed the rom I went to the bootloader and made the downgrade,Successfully booted into cm13,but when i tried going to recovery to flash xposed,i found out there's bootloop ( stuck on asus logo ) ! Everytime i try to boot into bootloader or recovery! nothing works!

Saumitraa said:
So,recently i switched from cm14.1 back to cm13 and when i did that, i forgot to downgrade the bootloader,so after i flashed the rom I went to the bootloader and made the downgrade,Successfully booted into cm13,but when i tried going to recovery to flash xposed,i found out there's bootloop ( stuck on asus logo ) ! Everytime i try to boot into bootloader or recovery! nothing works!
Click to expand...
Click to collapse
if no boot loader you have to use unbrick threads.
If you had a flashed back a stock recovery and boot.img if on rooted mm bl with giovix modder tool , you could've downgraded via sd card and stock recovery ..in my link below
There were 2 different cm 13s , one with mm bl and one based on 5.
.

Unbricked
So i unbricked the phone! Everything was success! xfstk worked then i got the 4 color screen and after that the bootloader!
Extracted the .raw file and then flashed using commands, but when the phone tries to reboot, it gets stuck on the ASUS logo! waited half an hour for that! Service center people say that its a motherboard problem! Any advice ?

Saumitraa said:
So i unbricked the phone! Everything was success! xfstk worked then i got the 4 color screen and after that the bootloader!
Extracted the .raw file and then flashed using commands, but when the phone tries to reboot, it gets stuck on the ASUS logo! waited half an hour for that! Service center people say that its a motherboard problem! Any advice ?
Click to expand...
Click to collapse
did you get any error in any command. if you got bootloader it must work
flash xfstk again and and run these commands after extracting raw.. tell me if any of the command fails or give error
1. fastboot devices ( see if it is recognized: else plug out usb and plugin again)
2. fastboot oem erase_osip_header
3. fastboot oem start_partitioning
4. fastboot flash /tmp/partition.tbl partition.tbl
5. fastboot oem partition /tmp/partition.tbl
6. fastboot erase system
7. fastboot erase cache
8. fastboot erase data
9. fastboot erase APD
10. fastboot erase ADF
11. fastboot oem wipe splashscreen
12. fastboot oem stop_partitioning
13. fastboot flash splashscreen splash_sign.bin
14. fastboot flash token MFG_BOM_Full.bin
15. fastboot flash ifwi ifwi-prod.bin
16. fastboot flash boot boot_sign.bin
17. fastboot flash recovery recovery_sign.bin
18. fastboot flash fastboot droidboot_sign.bin
19. fastboot flash APD APD.img
20. fastboot flash system system.img
21. fastboot reboot

No errors
I flashed everything again, no errors whatsoever! The phone just wont boot! Stuck on Asus logo for an hour , then switched off the phone

Saumitraa said:
I flashed everything again, no errors whatsoever! The phone just wont boot! Stuck on Asus logo for an hour , then switched off the phone
Click to expand...
Click to collapse
Which build number raw file you use ?

Saumitraa said:
I flashed everything again, no errors whatsoever! The phone just wont boot! Stuck on Asus logo for an hour , then switched off the phone
Click to expand...
Click to collapse
send me log of cmd when you run commands

timbernot said:
Which build number raw file you use ?
Click to expand...
Click to collapse
This one : WW_ZE551ML_2.20.40.194_20160713

Booting into Recovery Automatically!

I unlocked my bootloader. Installed TWRP and when I was on stock I updated my moto z play to 7.1.1. I know never update through OTA when custom recovery is installed. But I didn't know that earlier. Device got rebooted and directly booted into TWRP and nothing happened. I then rebooted to bootloader and started the device and it booted up!
The problem is each time the phone is rebooted it goes into recovery and i have to reboot it to bootloader to start!
How can I solve this?
I'm currently on Resurrection remix Rom!
Thanks!

Fastboot command
adb reboot bootloader
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
fastboot erase cache
fastboot reboot

Nikepel said:
Fastboot command
adb reboot bootloader
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
Thanks!
I'll try this tomorrow.
Will update after I'm done!

Got the same problem - unlocked bootloader, installed TWRP, did dual sim mod for a friend and then the "idiot" did an ota - now phone is stuck into booting to TWRP.
I tried the fastboot commands and they went through fine, but phone is still only booting into twrp - with fastboot and "start" its booting up though.
There must still be some "do-ota" flag enabled somewhere.. ?!
---
EDIT: ok well **** it - after i booted it up once normal over the fastboot start it boots normal again!

+1 with same problem.
zroice said:
EDIT: ok well **** it - after i booted it up once normal over the fastboot start it boots normal again!
Click to expand...
Click to collapse
Can you give some more details on how you managed to fix it?

I have the same problem was on stock with root and tried OTA :silly:
These fastboot commands don't work for me, does anyone have another solution?

Nikepel said:
Fastboot command
adb reboot bootloader
fastboot oem fb_mode_set
fastboot oem fb_mode_clear
fastboot erase cache
fastboot reboot
Click to expand...
Click to collapse
Perfect !!!
After flashing the android 8 version, my phone could not start normally (directly into the bootloader.)
The command lines saved my Moto lol ?
Thank you very much !