Database Info

Desire S stop at boot after flash

hello
I got a new Desire S two week ago, i root it and s-off with the guide i found here without problem.
A few day ago, my phone say that an update with the new sens was avaible so i done it. It don't work because Revolutionary don't let an offcial update erase it (i learned that here to late...)...
I run and old official update and it works again.
I like to "unistall" Revolutionary, i followed this guide http://forum.xda-developers.com/showthread.php?t=1113820 but it didnt work, at the command "adb shell su" the script block waiting that i accept something that didnt show on my phone.
Superuser log a accepted demand but nothing append.
So i use Fastboot to flash the hboot image but it didn't work, it say :
sending 'hboot' (1024 KB)...
OKAY [ 0.202s]
writing 'hboot'...
(bootloader) image update is bypassed!
OKAY [ 0.029s]
finished. total time: 0.232s
I'm out of idea for now and my phone block to the htc logo now...
Can someone help me?
(I apologise for my bad english, long time i don't practice it)

[Q] Need help after erasing /system

Ok good people of XDA, need some help on this one. Did a lot of reading and trying but can not figure this out. I was wiping my phone through TWRP, and without looking wiped /system. Naturally my phone is now getting stuck in HTC spplash screen, I can still get into recovery, but then the when trying to mount USB strage under TWRP was getting unknown format, so like an idiot I formatted FAT32 and anything I put on there recovery does not see. What is the file format for the storage? I also can not RUU the via fastboot as I gives me the following
C:\\Android>fastboot flash boot boot_signed.img
sending 'boot' (6236 KB)... OKAY [ 1.885s]
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.092s
C:\Android>fastboot flash system system.img
sending 'system' (1048572 KB)... FAILED (remote: data length is too large)
finished. total time: 0.006s
Probably because it cant read something. I did lock the boot-loader before doing it. Also, noticed the ADB commands are not working in the power off state either.
What do you guys think?

romka7 said:
Ok good people of XDA, need some help on this one. Did a lot of reading and trying but can not figure this out. I was wiping my phone through TWRP, and without looking wiped /system. Naturally my phone is now getting stuck in HTC spplash screen, I can still get into recovery, but then the when trying to mount USB strage under TWRP was getting unknown format, so like an idiot I formatted FAT32 and anything I put on there recovery does not see. What is the file format for the storage? I also can not RUU the via fastboot as I gives me the following
C:\\Android>fastboot flash boot boot_signed.img
sending 'boot' (6236 KB)... OKAY [ 1.885s]
writing 'boot'... INFOsignature checking...
FAILED (remote: signature verify fail)
finished. total time: 3.092s
C:\Android>fastboot flash system system.img
sending 'system' (1048572 KB)... FAILED (remote: data length is too large)
finished. total time: 0.006s
Probably because it cant read something. I did lock the boot-loader before doing it. Also, noticed the ADB commands are not working in the power off state either.
What do you guys think?
Click to expand...
Click to collapse
If I remember right, it's actually EXT4 and android uses FUSE to make it look like a FAT32 partition to a connected machine.
I would have suggested RUU, but it seems like that's not an option for you. Good luck with your phone, man.

If worst comes to worst just go to att and say it broke randomly, I don't think they can tell it's rooted if you messed it up that badly
Sent from my One X using xda premium

Did you try just running the RUU ?

Ok, I beat it to death.... got it working. Somewhere in my trial and error process I ended up flashing to CWM recovery, which did nothing new for me, then I pushed TWRP again but the 2.1.8, was on 2.2 when the problem started.... all of the sudden ADB started working, not sure what happened on the newer version. I still did not see my SDcard, but I was able to push a version of cleanrom to the system partition. The install did not go, but the the process it formated the sdcard to the proper format.... or it restored some setting. I was then able to mount SD in TWRP and installed newest version of CleanRom.. All good now.... its all a learning process I guess

Bricked my One S?

So I wanted to root my One S and install CWM.
What I did was use http://forum.xda-developers.com/showthread.php?t=1604677 this tool, everything went fine. I used the TWRP recovery, it booted fine.
Tried to install CWM, found out my Hboot was too low (think it was 1.14.0.02).
Extracted the hboot.img from the CWM zip, installed it:
C:\Users\aSCO\Desktop\blabla\fastboot flash boot boot.img
sending 'boot' (5688 KB)...
OKAY [ 0.890s]
writing 'boot'...
OKAY [ 1.390s]
finished. total time: 2.280s
then fastboot reboot.
Now the ühone won't turn one, LED doesn't shine when connected to charger. From time to time it turns on, show the HTC screen (with text 'this is a developer version etc'), then turns back off.
Any hope there for me? What did I do wrong?
EDIT: I managed to get into fastboot, what's the best way to go on from here? The Hboot version number is still the same, is there another recommended boot.img that I could flash?
EDIT2: Managed to fix this, cannot find an option to delete the thread ...
CAN BE CLOSED.

[Q] boot to black screen, can not get into recovery

I just flash a rom(white-heat 5.0.1) onto my phone (nexus 5 rooted, bought from google) and after t was done booting all i have is a black screen with the clock and signal at the top right and a arrow at the bottom left, i can not get into phone to try to fix. so i tried to boot into recovery and see if i could just try it again but when the twrp logo comes up i wait to get into recoovery but it passes by and then boots regular and back to black screen from before.
adb and fast boot are not seeing phone on linux or mac
there must be something i can do,, when the phone boots to black screen when i press the power button i can see home screen for second then black i could hear emails coming in to phone but is all i can do...

You can't boot into recovery because you have TWRP 2.8.2.0 with SMTP enabled.most likely. Flash back to previous version

gordonrjones said:
I just flash a rom(white-heat 5.0.1) onto my phone (nexus 5 rooted, bought from google) and after t was done booting all i have is a black screen with the clock and signal at the top right and a arrow at the bottom left, i can not get into phone to try to fix. so i tried to boot into recovery and see if i could just try it again but when the twrp logo comes up i wait to get into recoovery but it passes by and then boots regular and back to black screen from before.
adb and fast boot are not seeing phone on linux or mac
there must be something i can do,, when the phone boots to black screen when i press the power button i can see home screen for second then black i could hear emails coming in to phone but is all i can do...
Click to expand...
Click to collapse
Try getting into the bootloader and look if the device is detected, if so relash a factory image and start over. At least that what i would do.

need to get into phone to do anything
rootSU said:
You can't boot into recovery because you have TWRP 2.8.2.0 with SMTP enabled.most likely. Flash back to previous version
Click to expand...
Click to collapse
i can not get into my phone to do anything like flashing or settings or recovery, I am not sure if smtp is enabled in TWRP or what version for sure but the last time i was looking at it it has 2.7.? installed
thanks

yes
gee2012 said:
Try getting into the bootloader and look if the device is detected, if so relash a factory image and start over. At least that what i would do.
Click to expand...
Click to collapse
I can get into bootloader but not into recovery, it just shows TWRP for maybe five seconds then continues to regular boot

gordonrjones said:
i can not get into my phone to do anything like flashing or settings or recovery, I am not sure if smtp is enabled in TWRP or what version for sure but the last time i was looking at it it has 2.7.? installed
thanks
Click to expand...
Click to collapse
So you can`t power down the phone and get into bootloader by pressing volume up and down and the power button?

yes
gee2012 said:
So you can`t power down the phone and get into bootloader by pressing volume up and down and the power button?
Click to expand...
Click to collapse
I can power down the phone and get into bootloader, but when i pick recovery it does not go there it starts to but the just continues to boot into black screen, thanks

gordonrjones said:
I can power down the phone and get into bootloader, but when i pick recovery it does not go there it starts to but the just continues to boot into black screen, thanks
Click to expand...
Click to collapse
If you are in bootloader mode connect the phone to the pc and see if it is connected and detected. If so flash a factory image and you`re phone is running again.

gordonrjones said:
i can not get into my phone to do anything like flashing or settings or recovery, I am not sure if smtp is enabled in TWRP or what version for sure but the last time i was looking at it it has 2.7.? installed
thanks
Click to expand...
Click to collapse
You don't need to. Use fastboot.

been trying
rootSU said:
You don't need to. Use fastboot.
Click to expand...
Click to collapse
fastboot has been showing no devices but it just showed me one i am waiting for the thing to stop and boot and see if i still have black screen, if all is good ...
Thanks to you all for your words of wisdom on this Miserable(here) Friday night, cold and wet,... will keep my fingers crossed till then thanks again

hmmmmmm
Still booting 6:45pm:
:hammerhead gordonrjones$ sh flash-all.sh
sending 'bootloader' (2579 KB)...
OKAY [ 0.198s]
writing 'bootloader'...
OKAY [ 0.514s]
finished. total time: 0.712s
rebooting into bootloader...
OKAY [ 0.091s]
finished. total time: 0.091s
sending 'radio' (45521 KB)...
OKAY [ 1.624s]
writing 'radio'...
OKAY [ 3.124s]
finished. total time: 4.749s
rebooting into bootloader...
OKAY [ 0.085s]
finished. total time: 0.085s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
archive does not contain 'system.sig'
--------------------------------------------
Bootloader Version...: HHZ12d
Baseband Version.....: M8974A-2.0.50.2.22
Serial Number........: 03bcc840437d66db
--------------------------------------------
checking product...
OKAY [ 0.100s]
checking version-bootloader...
OKAY [ 0.100s]
checking version-baseband...
OKAY [ 0.100s]
sending 'boot' (8852 KB)...
OKAY [ 0.520s]
writing 'boot'...
OKAY [ 0.765s]
sending 'recovery' (9552 KB)...
OKAY [ 0.546s]
writing 'recovery'...
OKAY [ 0.802s]
sending 'system' (981472 KB)...
OKAY [ 30.972s]
writing 'system'...
OKAY [ 65.984s]
erasing 'userdata'...
OKAY [ 9.308s]
erasing 'cache'...
OKAY [ 0.570s]
rebooting...
finished. total time: 110.169s

Unable to restore Pixel 2 to Factory

Hey everyone!
I'm a long time reader, but never had the occasion to post until now. I have somewhat recently started tinkering with my phones. I'm a programmer by trade so I'm not at all seperated from technology, however, I fear I may have gotten myself into a but of a ?.
So, here's what I broke: I have a Verizon Wireless Pixel 2. A few weeks ago I read that there was a boot loader unlock for it. As such, I rebooted to the boot loader, ran the "fastboot flashing lock_critical" command. After being unlocked I then proceeded to flash TWRP and then Magisk Manager. All was well until my phone had an unrelated warranty issue. As such, I filed a claim, and got my new phone.
Today I was trying to recover my phone to factory and am getting a few errors. I downloaded this Image from Google "8.0.0 (OPD3.170816.023, Nov 2017, Verizon) - https://dl.google.com/dl/android/aosp/walleye-opd3.170816.023-factory-f269631e.zip"). I extracted it, and ran "flash_all.bat". Througout the process I get an error stating that it can't find a recovery.img. I looked in the .zip and found that to be true. I downloaded the standard stock .zip and noticed it doesn't have one either. In addition, when it gets to the part about flashing the system image I get the following error:
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: mw8998-002.0066.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: REMOVED
--------------------------------------------
checking product...
OKAY [ 0.000s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ -0.000s]
sending 'boot' (32768 KB)...
OKAY [ 0.744s]
writing 'boot'...
OKAY [ 0.000s]
sending sparse 'system' (524284 KB)...
OKAY [ 12.589s]
writing 'system'...
OKAY [ -0.000s]
sending sparse 'system' (524284 KB)...
FAILED (remote: No such partition.)
finished. total time: 13.631s
Anyone have any idea how to remedy this? I'm simply trying to get it back to stock. In addition, if I can get it returned to stock is relocking the bootloader even possible?
Thanks in advance for any help!
-Sofie

is your phone currently on 8.0.0 or have you been updated to at least 8.1?
you can't flash to a lower version than what you already have. i have verizon and i plan on flashing back to stock and you should be flashing to the 013 version from January.

iridium7777 said:
is your phone currently on 8.0.0 or have you been updated to at least 8.1?
you can't flash to a lower version than what you already have. i have verizon and i plan on flashing back to stock and you should be flashing to the 013 version from January.
Click to expand...
Click to collapse
It was on 8.1. Makes sense, I'll download the latest and try that. I just chose that because it says "VZW" in the name.

iridium7777 said:
is your phone currently on 8.0.0 or have you been updated to at least 8.1?
you can't flash to a lower version than what you already have. i have verizon and i plan on flashing back to stock and you should be flashing to the 013 version from January.
Click to expand...
Click to collapse
SweetSofie said:
It was on 8.1. Makes sense, I'll download the latest and try that. I just chose that because it says "VZW" in the name.
Click to expand...
Click to collapse
Well, that didn't help at all. :crying:

SweetSofie said:
Well, that didn't help at all. :crying:
Click to expand...
Click to collapse
try everything over and start clean:
1) delete all your stuff from your comp (all previous tools and images)
2) download the fresh set of latest adb tools from google
3) download the latest walleye stock image from google
4) put all those things in the same directory and uncompress them there (so flash-all.bat is in the same folder as adb, along with the img and zip files for walleye).
5) adb reboot bootloader
6) flash-all
are those similar to the steps that you did before?

SweetSofie said:
Hey everyone!
I'm a long time reader, but never had the occasion to post until now. I have somewhat recently started tinkering with my phones. I'm a programmer by trade so I'm not at all seperated from technology, however, I fear I may have gotten myself into a but of a ?.
So, here's what I broke: I have a Verizon Wireless Pixel 2. A few weeks ago I read that there was a boot loader unlock for it. As such, I rebooted to the boot loader, ran the "fastboot flashing lock_critical" command. After being unlocked I then proceeded to flash TWRP and then Magisk Manager. All was well until my phone had an unrelated warranty issue. As such, I filed a claim, and got my new phone.
Today I was trying to recover my phone to factory and am getting a few errors. I downloaded this Image from Google "8.0.0 (OPD3.170816.023, Nov 2017, Verizon) - https://dl.google.com/dl/android/aosp/walleye-opd3.170816.023-factory-f269631e.zip"). I extracted it, and ran "flash_all.bat". Througout the process I get an error stating that it can't find a recovery.img. I looked in the .zip and found that to be true. I downloaded the standard stock .zip and noticed it doesn't have one either. In addition, when it gets to the part about flashing the system image I get the following error:
target reported max download size of 536870912 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.img'
archive does not contain 'system.sig'
archive does not contain 'vendor.sig'
Erase successful, but not automatically formatting.
Can't determine partition type.
FAILED (remote: GetVar Variable Not found)
--------------------------------------------
Bootloader Version...: mw8998-002.0066.00
Baseband Version.....: g8998-00164-1710262031
Serial Number........: REMOVED
--------------------------------------------
checking product...
OKAY [ 0.000s]
checking version-bootloader...
OKAY [ 0.001s]
checking version-baseband...
OKAY [ -0.000s]
sending 'boot' (32768 KB)...
OKAY [ 0.744s]
writing 'boot'...
OKAY [ 0.000s]
sending sparse 'system' (524284 KB)...
OKAY [ 12.589s]
writing 'system'...
OKAY [ -0.000s]
sending sparse 'system' (524284 KB)...
FAILED (remote: No such partition.)
finished. total time: 13.631s
Anyone have any idea how to remedy this? I'm simply trying to get it back to stock. In addition, if I can get it returned to stock is relocking the bootloader even possible?
Thanks in advance for any help!
-Sofie
Click to expand...
Click to collapse
Just so you know, those "archive does not contain" errors are normal. I get them all the time. Always did on the original Pixel too. I'm not sure about the one at the end. Can't say I've ever seen that on either the Pixel 1 or 2.

SweetSofie said:
Well, that didn't help at all. :crying:
Click to expand...
Click to collapse
Were you able to sort out your issue?
If not, I have heard good things about using this tool to install the latest factory image. Just download this script and follow the instructions in that thread.
If that goes well, then you should be able to boot to the latest build and ready to lock the bootloader, which will factory reset the phone as part of the process.
adb reboot bootloader
fastboot flashing lock
If that process makes you feel uncomfortable, I found this post from another thread doing a similar method (but not using the script above)
Good Luck!

robocuff said:
Just so you know, those "archive does not contain" errors are normal. I get them all the time. Always did on the original Pixel too. I'm not sure about the one at the end. Can't say I've ever seen that on either the Pixel 1 or 2.
Click to expand...
Click to collapse
Thanks for the re-assurance. I did notice that the zips literally dont contain a recovery.img. Is that normal for the Pixel 2?

SweetSofie said:
Thanks for the re-assurance. I did notice that the zips literally dont contain a recovery.img. Is that normal for the Pixel 2?
Click to expand...
Click to collapse
Yes. The recovery is in the boot.img now.

Duhman72 said:
Were you able to sort out your issue?
If not, I have heard good things about using this tool to install the latest factory image. Just download this script and follow the instructions in that thread.
If that goes well, then you should be able to boot to the latest build and ready to lock the bootloader, which will factory reset the phone as part of the process.
adb reboot bootloader
fastboot flashing lock
If that process makes you feel uncomfortable, I found this post from another thread doing a similar method (but not using the script above)
Good Luck!
Click to expand...
Click to collapse
I tried this tool and had no luck either. I ultimately just locked the bootloder, as-is, and sent it back. ? Hopefully the think it's just a component level failure since the boot loader is locked. I guess we will see... ?

SweetSofie said:
I tried this tool and had no luck either. I ultimately just locked the bootloder, as-is, and sent it back. ? Hopefully the think it's just a component level failure since the boot loader is locked. I guess we will see... ?
Click to expand...
Click to collapse
They won't even check, they don't care. They will inspect it for physical abuse and water damage. That is all.

TonikJDK said:
They won't even check, they don't care. They will inspect it for physical abuse and water damage. That is all.
Click to expand...
Click to collapse
I think you're right! So far so good. I haven't had any backlash from Verizon so far. Thanks!