Develop Bugs

[Q] Missing boot menu item

I installed HTC Sync then, unistalled (keeping the drivers).
I installed the HBOOT modified drivers in device manager. it now says:
"Android device"
|
"My HTC"
I ran unrevoked3, successful, done. I did one click only and let it run.
I then downloaded Wildpuzzle 2.2 froyo (kept it zipped copied it to SDcard).
I powered down phone then pressed volDown and power together to go to boot menu.
my boot menu looks different to that of a video I saw:
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
shouldn't it look like this?:
FASTBOOT
RECOVERY
CLEAR STORAGE
SIMLOCK
HBOOT USB
note- it doesn't make a difference if my wildfire is plugged in to the pc, or if I'm running unrevoked at this point.
I wait for the update scan check thing, then I go down one to RECOVERY (If I'm running unrevoked at this point communication is lost) this takes me to ClockworkMod Recovery v (black screen, green text).
I choose "-wipe data/factory re" then "-install zip from sdc" choose my zip blaa blaa...
I see the install bar and it does it in a second, completed.
- reboot system now
I wait till phone is ready (have a sandwich very nice)
check menu/settings/about phone/software information.... still says:
Firmware version
2.1-update 1
Ahhhhhhhhh
I keep trying for three days different roms, typing here is last resort by papa roach!
HOW . DO . THIS . ?

edit your post and add a title.. please be more observant..

I hope you are not selecting the update.zip under the sdcard which might be the clockworkmod recovery image (rom manager based recovery installation keeps it there). Since clockworkmod recovery has that as an option above the zip file selection, it is a possibility (especially based on the sped of the update)

hackworks said:
I hope you are not selecting the update.zip under the sdcard which might be the clockworkmod recovery image (rom manager based recovery installation keeps it there). Since clockworkmod recovery has that as an option above the zip file selection, it is a possibility (especially based on the sped of the update)
Click to expand...
Click to collapse
No I'm not selecting update.zip

i have this same problem
please guide me ...i have this same problem...without hboot usb option in the boot menu...how can i install the hboot drivers?

u successfully rooted ur device. but have u installed clockworkmod recovery. i doubt this. and u also need to update the clockwork mod recovery. and then only u can install custom roms. dont forget to wipe all data and clear cache.

[Q] Flashed EU HOX with AT&T stuff and BRICKED! Please help

I'm desparate, please help me!
I flashed the remove-3-dot for the AT&T HOX, but I have another one. Now I cannot go back, since the device doesn't completely boot.
It is stuck with the HTC figures showing up and halfway the music stops and the device hangs.
I can go to recovery, but since the Àll-In-One Kit from Hasoon2000 doesn't see the device when in recovery (CWM 5.8.2.7 Touch), I cannot even put anything to the SD card, so I cannot even flash anything else!
Please help me before the battery dies out!! (I cannot turn it off since lonng press of the power button only restarts the booting)

If you have CWM did you made a nondroid backup?

Bright.Light said:
I'm desparate, please help me!
I flashed the remove-3-dot for the AT&T HOX, but I have another one. Now I cannot go back, since the device doesn't completely boot.
It is stuck with the HTC figures showing up and halfway the music stops and the device hangs.
I can go to recovery, but since the Àll-In-One Kit from Hasoon2000 doesn't see the device when in recovery (CWM 5.8.2.7 Touch), I cannot even put anything to the SD card, so I cannot even flash anything else!
Please help me before the battery dies out!! (I cannot turn it off since lonng press of the power button only restarts the booting)
Click to expand...
Click to collapse
THIS will help you

@muamers: Thanks!!
I already found out how to turn the device off, not draining the battery anymore.
I also flashed the new CWM 5.8.3.1 so it should have some ability to charge.
I am currently downloading the latest stock 1.29.401.11 and will try to flash that one.
I did search, but it's difficult currently. However, I made a permanent link to the Wiki - it's more than useful (the reason it exists, I know...)
Oh - it wasn't bricked (because it still did some stuff)
@jeyml: No, I did not do that (didn't know it was possible)
Does that mean that I could recover with the rom exactly as it was put on the device? (including installed ZIP files)

Bright.Light said:
@muamers: Thanks!!
I already found out how to turn the device off, not draining the battery anymore.
I also flashed the new CWM 5.8.3.1 so it should have some ability to charge.
I am currently downloading the latest stock 1.29.401.11 and will try to flash that one.
I did search, but it's difficult currently. However, I made a permanent link to the Wiki - it's more than useful (the reason it exists, I know...)
Oh - it wasn't bricked (because it still did some stuff)
@jeyml: No, I did not do that (didn't know it was possible)
Does that mean that I could recover with the rom exactly as it was put on the device? (including installed ZIP files)
Click to expand...
Click to collapse
Yup.It is actualy quite simple,i always do a backup before i flash something or update my ROM and other stuff.You keep the volume down + power button.After that you enter recovery mode (you will need to have CWM) and you have an option there "backup and restore",enter there and make a backup.Next time if you have any problems just enter again in the CWM,go to "backup and restore" and restore the backup you've made.It saves everything you have (i mean the ROM setting and such.Apps and other stuff must be backed up with Titanium Backup).
The backups you made are saved in the SD card in the nandroid directory if i remember corectly,so if you update you're ROM to...1.29 for example and have a 1.28 backup just enter there and delete it and make a new backup of the 1.29 so you don't get confused in so many backups and if you ever have problems and restore a 1.28 backup on you'r 1.29..well...you realize that the phone isn't going to work anymore.So,be carefoul.

Didn't work... I downloaded this rom: RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.11_Radio_1.1204.105.14_release_260491_signed
did everything this page told us: http://forum.xda-developers.com/showthread.php?t=1609190
But I do not see anything change... It's still stuck in the boot process.
I don't know what I am doing wrong...
I also didn't find a clear guide for how to do things - it's all pieces which everyone has to put together, making it hard when there is a real problem.
If this can be solved, I will investigate the nand backup for certain!
For now I need my phone, but it does not work...
Oh - how does the charging with the new clockwork work? I don't see anything happen, so I am afraid the battery will be down soon.
edit: It was on power all night and when I looked it had the screen on. Unplugging and replugging and the gren light went on. Does that mean the battery is filled?
One important fact: the adb command cannot find the device and I don't know why!

How did you flash the RUU? You have to connect the phone in FASTBOOT to the PC and then run it (with a locked bootloader) and it replaces the entire system

EddyOS said:
How did you flash the RUU? You have to connect the phone in FASTBOOT to the PC and then run it (with a locked bootloader) and it replaces the entire system
Click to expand...
Click to collapse
with a LOCKED bootloader?
Mine is unlocked...
I will try to relock the boorloader (saw somewhere a snippet)

Tried with a locked one:
Code:
D:\One_X_All-In-One_Kit_v1.0\Data>fastboot oem lock
... INFOLock successfully...
OKAY [ 0.143s]
finished. total time: 0.143s
D:\One_X_All-In-One_Kit_v1.0\Data>fastboot flash boot boot_signed.img
sending 'boot' (4288 KB)... OKAY [ 0.667s]
writing 'boot'... FAILED (remote: not allowed)
finished. total time: 0.874s
D:\One_X_All-In-One_Kit_v1.0\Data>fastboot flash system system.img
sending 'system' (963584 KB)... FAILED (remote: (00000008))
finished. total time: -0.000s
The bootloader loocks relocked ok (as it shows on top of that screen)
But flashing is impossible and, of cause, I don't know why

Adb will work in recovery but only if you boot the recovery from fastboot.
Fastboot boot recovery recovery.img

ok, next approach:
- Booted to fastboot
- unlocked bootloader with the unlock .bin file
- fastboot boot Recoveries\CWM5.8.3.1.img
- adb push rom.zip /sdcard/
- waited 5 minutes until done
- in recovery: Install zip from sdcard
- manual selected the rom.zip (yes, it was actually on the SDcard, so adb did its job)
- got an error that the image was bad:
ClockworkMod Recovery v5.8.3.1
-- Installing: /sdcard/rom.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/rom.zip
I think I will have to get another image, right?
This one was extracted from
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.11_Radio_1.1204.105.14_release_260491_signed.exe
I started the program and searched for the rom.zip in my temp folder. Was this ok?

Run .11 RUU, wait until load all completely, now go to %temp% in your pc and find a folder that contain a ROM.ZIP file... Unzip the files and flash the boot_signed.img and the recovery_signed.img, then relock your phone fastboot oem lock) do a factory reset (with the new recovery) and then try to run the .11 RUU.
THAT SHOULD WORK
pd: sorry for my poor english.
Sent from my HTC One X using XDA

Bright.Light said:
ok, next approach:
- Booted to fastboot
- unlocked bootloader with the unlock .bin file
- fastboot boot Recoveries\CWM5.8.3.1.img
- adb push rom.zip /sdcard/
- waited 5 minutes until done
- in recovery: Install zip from sdcard
- manual selected the rom.zip (yes, it was actually on the SDcard, so adb did its job)
- got an error that the image was bad:
ClockworkMod Recovery v5.8.3.1
-- Installing: /sdcard/rom.zip
Finding update package...
Opening update package...
E:Can't open /sdcard/rom.zip
I think I will have to get another image, right?
This one was extracted from
RUU_ENDEAVOR_U_ICS_40_HTC_Europe_1.29.401.11_Radio_1.1204.105.14_release_260491_signed.exe
I started the program and searched for the rom.zip in my temp folder. Was this ok?
Click to expand...
Click to collapse
You haven't a clue have you?
You don't flash an RUU from CWM, it's a Windows application!
1. Boot phone into FASTBOOT
2. Connect to the PC
3. Lock the bootloader
4. Run the RUU
Job done

@wolfraim: Yes, the factory reset was the one culprit, it seems!
EddyOS: Tried that so many times, but finally wolfraim added a crucial point: Factory reset!
Now the RUU install from the PC is working... (Have to wait for some time ...)
* I have to go for now, right after the flash is done.
When I've got the time, I will try to make some more notes and maybe another step-by-step story on how to make the device work again.
Thank you very much for your patience and help!
This is why I love the xda-developers site so much!
(and all possible ways included on XDA to brick my device is the reason why I hate xda sometimes... )
edit: Flashing has succeeded! Software number: 1.29.401.11, so it seems I also have the latest ROM update now.
I'll make a recovery backup asap and will try the titanium backup too.
Oh, this one is SU-locked of cause, so I will have to install the SU zip file again... Much work is to be done yet. Maybe I should look for a good ROM in the Android development area.

Stuck in WFS Recovery (White HTC Logo)

It all goes like this - I wanted to root my WPS to solve space problem, although, there was a solution for it without rooting, I figured I will be wanting to use some apps that need root access and some roms sooner or later.
So I did a search and found few ways to root my phone. Being a lazy ass I decided to use "the simple" one click solutions - gingerbreak (http://forum.xda-developers.com/showthread.php?t=1044765) or Root Unlocker (http://www.unlockroot.com/) This was no success. Gingerbreak kept rooting when I launched the app, but Root Unlocker displayed " FAIL TO GET SHELL ROOT". I figured that problem with Gingerbeak might be that I updated the software to the latest version -
Then I went on and tried another tutorial(http://forum.xda-developers.com/showthread.php?t=1195275). Everything was fine till I selected Recovery from bootloader. It got stuck with white HTC logo. Took out the battery tried to use newer version of ClockworkMod Recovery, but still was a no-go. I also can't do a factory restart. I can't do it from bootloader or settings > SD & phone storage > Factory data reset. (But could do it at first. Before trying to root my device I did a factory reset once.)
Is there a way to use another Recovery (not CMR) or force Recovery from fastboot? As I found there are some other people that got stuck with similar problem.
Other problems:
My phone doesn't show up in HTC Sync. Althought, when I tipe adb devices in cmd, it shows up. I did turn my AntiVirus off when I installed HTC Sync, but it still didn't display my phone.
I also found that I can't boot when I connect powered off phone to my pc. I have to take off my batery.
Here are my specs:
Model HTC Wildfire S A510e
It shows Marvel in bootloader.
Phone was S-OFF when I bought it.
Android 2.3.5
HTC Sence 2.1
Software number 2.26.401.3
I bought my phone without a contract from a local internet shop. I am from Baltics.
The phone might be somewhere from Europe.
My bet would be Poland. (guessing that manual language is Polish, but I might be wrong)
Thanks in advance.
UPDATE!
I took the original recovery img from http://forum.xda-developers.com/showthread.php?t=1426611 and flashed it. All went well. I did a restart (after doing this I was able to boot power my device while connected to pc) and had another try with CMR recovery, but it didn't work. I also I tried http://forum.xda-developers.com/showthread.php?t=1406321 recovery img, but it didn't help, I still can't get into.

How to root Wildfire S S-OFF the easy way
First download this
Put it in your memory card
then press and hold voldown+Power
It will load the bootloader follow the instructions on the screen and update accordingly
Then Turn off
Remove that PG76IMG from sdcard
After that download this and put in your memorycard and update same way, it will flash the CMR5.0.2.8 (after flashing dont forget to remove this PG76IMG from sdcard as well).
Now download this put it in your mmc and flash this from recovery.
Done.. U have successfully rooted Ur S-OFF device Now In CWM do factory reset install new custom rom according to the way devs say. I can assure U that this process will even remove Ur white screen

im stuck too on the recovery s-on btw and bootloader unlocked

ME TOO
but i m s-on

Same problem here, unlock by htc-dev worked. Recovery flashed but device stays stuck on the HTC logo. So my daughter's phone is unlocked but that's it.

Thanks, but now I am simply stuck with white htc logo on black background with purple line after entering recovery.
There might be another work around with fastboot, but also have a fastboot remote: not allowed.

Let me know
7axew3ku said:
Thanks, but now I am simply stuck with white htc logo on black background with purple line after entering recovery.
There might be another work around with fastboot, but also have a fastboot remote: not allowed.
Click to expand...
Click to collapse
I dont understand. If ur splash screen changed means u have installed cwm. Just select recovery and install a rom. Like this one
Download the rom. Put in ur sdcard.
remove battery
press vol down+power
press vol down
press power to select recovery
In recovery to move press vol up/down, to select press power
Wipe data/factory reset
Wipe cache partition
Advanced>> Wipe Dalvik cache then also wipe battery stats
Go back
Install zip from sdcard
Select the romname.zip put in sdcard
that should be it instructions are also found in that rom. thread so simple!!

7axew3ku said:
Thanks, but now I am simply stuck with white htc logo on black background with purple line after entering recovery.
There might be another work around with fastboot, but also have a fastboot remote: not allowed.
Click to expand...
Click to collapse
Here is a flash file you can try since you are S-Off. It should flash the default splash image, CWM 5.0.2.8, hboot 1.03 and re-calibrate the touch panel.
Hope it works for you.

Deleted

Problems persist
I have the same problem. My bootloader is unlocked via HTCDEV.com, though with S-ON. In any case...
My WFS is running 2.3.5, it's A510e.
installed recovery image 5.0.2.8 via console (had trouble installing it from the SD card).
each time I attempted to go HBOOT > RECOVERY, my phone would reboot, but would be stuck in black screen with the nav buttons at the bottom lit up (HOME, MENU, BACK, SEARCH).
installed recovery image 6.0.1.0 via SD card, going to HBOOT > RECOVERY will restart the phone, but it freezes on the white screen with the green HTC logo
downgraded to recovery image 6.0.0.3 via console, same problem - frozen on the white screen with the green HTC logo.
at this point, I'm out of ideas, but it seems that recovery image is at fault here?
*** UNLOCKED ***
MARVEL PVT SHIP S-ON RL
HBOOT-1.09.0099
MICROP-7.57.39.10M
Feb 8 2012,18:29:31
Is there a way to execute the ROOT.ZIP script on the phone but via the console on PC?

Return back to Normal after BOOT-LOOP !
muckz said:
I have the same problem. My bootloader is unlocked via HTCDEV.com, though with S-ON. In any case...
My WFS is running 2.3.5, it's A510e.
installed recovery image 5.0.2.8 via console (had trouble installing it from the SD card).
each time I attempted to go HBOOT > RECOVERY, my phone would reboot, but would be stuck in black screen with the nav buttons at the bottom lit up (HOME, MENU, BACK, SEARCH).
installed recovery image 6.0.1.0 via SD card, going to HBOOT > RECOVERY will restart the phone, but it freezes on the white screen with the green HTC logo
downgraded to recovery image 6.0.0.3 via console, same problem - frozen on the white screen with the green HTC logo.
at this point, I'm out of ideas, but it seems that recovery image is at fault here?
*** UNLOCKED ***
MARVEL PVT SHIP S-ON RL
HBOOT-1.09.0099
MICROP-7.57.39.10M
Feb 8 2012,18:29:31
Is there a way to execute the ROOT.ZIP script on the phone but via the console on PC?
Click to expand...
Click to collapse
Hi,
I read boot-looped for many in this thread...
I Hope this method would solve all your problems....
Follow and flash these system.img, boot.img and recovery.img file as in the link. (You must have installed .net framework on your PC).
http://forum.xda-developers.com/showpost.php?p=21891784&postcount=1
Hope this may useful!! (If really just press 'Thanks")......

Senthamil said:
Hi,
I read boot-looped for many in this thread...
I Hope this method would solve all your problems....
Follow and flash these system.img, boot.img and recovery.img file as in the link. (You must have installed .net framework on your PC).
http://forum.xda-developers.com/showpost.php?p=21891784&postcount=1
Hope this may useful!! (If really just press 'Thanks")......
Click to expand...
Click to collapse
Nope didn't work. I reflashed each of the boot.img, system.img, and recovery.img, manually though, since the utility didn't work for me. To do this, I booted into HBOOT, then FASTBOOT, and ran commands from my machine "fastboot flash <image type> <image.img>", where <image type> is either boot, recovery, or system, and <image.img> is the corresponding image (boot.img, recovery.img, system.img).
It seems my recovery cannot boot from HBOOT. It simply gets stuck.
With clockwork recovery 5.0.2.6, the phone appears to shut off completely.
With clockwork recovery 5.0.2.8, the phone will shut off except the Android buttons at the bottom are lit up.
I don't know if I can use later CW recovery images, but I tried 6.0.0.3 and I get stuck at the white background with green HTC logo when attempting to go into RECOVERY. Downgraded back to 5.0.2.8.
However, I gave the HTC SuperTool v3 another try, and this time it worked. Previously was giving me errors.
So... to those that are stuck, boot your phone normally. Make sure to go into Settings > Applications > Development and enable USB debugging. Also enable 3rd party installs, just in case.
Then proceed to STEP 3 on this page http://www.htcwildfiresblog.com/2012/03/guide-to-rooting-htc-wildfire-s-235-s.html

For those who want more info, here's another thread:
http://forum.xda-developers.com/showthread.php?t=1725398
It appears that the latest Wildfire S has a slightly different firmware, possibly for the video chip, which causes the CWM Recovery not to work. Perhaps there'll be a fix released eventually, but for now you can follow the thread above for some possible workarounds and more info.

Try mg all in one tool. Here: http://forum.xda-developers.com/showthread.php?t=1697985
It should sort out you guys problems.

muckz said:
Nope didn't work. I reflashed each of the boot.img, system.img, and recovery.img, manually though, since the utility didn't work for me. To do this, I booted into HBOOT, then FASTBOOT, and ran commands from my machine "fastboot flash <image type> <image.img>", where <image type> is either boot, recovery, or system, and <image.img> is the corresponding image (boot.img, recovery.img, system.img).
It seems my recovery cannot boot from HBOOT. It simply gets stuck.
With clockwork recovery 5.0.2.6, the phone appears to shut off completely.
With clockwork recovery 5.0.2.8, the phone will shut off except the Android buttons at the bottom are lit up.
I don't know if I can use later CW recovery images, but I tried 6.0.0.3 and I get stuck at the white background with green HTC logo when attempting to go into RECOVERY. Downgraded back to 5.0.2.8.
However, I gave the HTC SuperTool v3 another try, and this time it worked. Previously was giving me errors.
So... to those that are stuck, boot your phone normally. Make sure to go into Settings > Applications > Development and enable USB debugging. Also enable 3rd party installs, just in case.
Then proceed to STEP 3 on this page http://www.htcwildfiresblog.com/2012/03/guide-to-rooting-htc-wildfire-s-235-s.html
Click to expand...
Click to collapse
It finally worked. I am rooted. Thanks mate and everybody (who hasn't already received a thanks) that joined this posts receives virtual cookie from me and thanks.
I flashed stock http://forum.xda-developers.com/showpost.php?p=21891784&postcount=1 and run SuperTool and it worked.
It took me a week, but it is finally done. Let the good times roll.:laugh:

7axew3ku said:
It finally worked. I am rooted. Thanks mate and everybody (who hasn't already received a thanks) that joined this posts receives virtual cookie from me and thanks.
I flashed stock http://forum.xda-developers.com/showpost.php?p=21891784&postcount=1 and run SuperTool and it worked.
It took me a week, but it is finally done. Let the good times roll.:laugh:
Click to expand...
Click to collapse
It appears that CWM 5.0.2.8 actually works, but it doesn't provide any output to the screen. With ROM Manager, you can automate starting into CWM Recovery and installing a custom ROM, so it doesn't matter if the screen is blank.

Nexus 7 completely bricked?

So I have no OS on my Nexus 7, nor can I flash one. All conventional methods of installing an operating system on to this POS have met with utter failure.
Brief histroy:
-Had CM 11 nightly build until it "imploded" (any shortcut would take me to a PIN screen, users deleted profiles deleted themselves, random reboot every 5 minutes) and stopped functioning.
-Decided to return to an earlier of CM, so I dl'd an earlier version and pushed the .zip to CWM recovery. Big mistake. CWM decided to repartition everything in an erroneous manner rather than just wipe Dalvik cache.
-Now CWM will not open any .zip pushed through ADB. Just a generic "failed to open file" message.
-Sheer desperation and four hours of driver Hell finds me in fastboot and trying to flash a stock image.
-Latest Android system image will not flash. Period. Using the flashall.bat script, the error about a missing system.img pops up. I am staring at system.img right next to the .bat.
-Download Android L preview and run flashall.bat, operating system installs after about 30 minutes and numerous errors that the script "seemed" to fix about missing partitions.
-Reflash TWRP
-Android L gets stuck in non-bootable state (spinning colored ball logo thing) after a random restart.
-Now TWRP cannot find any .zip that I manually push through ADB. I can see it in File Manager, but nowhere else. Flashing custom ROM at this point not possible.
-Return to Android KitKat stock image and manually flash system.img through fastboot. Tablet will not boot, goes directly to black screen after bootloader.
So WTF do I do at this point? I have just about had it with all things Android right now. CWM doesn't work. TWRP doesn't work. Stock images don't work. Fastboot doesn't work. What else is there?

Cortimi said:
So I have no OS on my Nexus 7, nor can I flash one. All conventional methods of installing an operating system on to this POS have met with utter failure.
Brief histroy:
-Had CM 11 nightly build until it "imploded" (any shortcut would take me to a PIN screen, users deleted profiles deleted themselves, random reboot every 5 minutes) and stopped functioning.
-Decided to return to an earlier of CM, so I dl'd an earlier version and pushed the .zip to CWM recovery. Big mistake. CWM decided to repartition everything in an erroneous manner rather than just wipe Dalvik cache.
-Now CWM will not open any .zip pushed through ADB. Just a generic "failed to open file" message.
-Sheer desperation and four hours of driver Hell finds me in fastboot and trying to flash a stock image.
-Latest Android system image will not flash. Period. Using the flashall.bat script, the error about a missing system.img pops up. I am staring at system.img right next to the .bat.
-Download Android L preview and run flashall.bat, operating system installs after about 30 minutes and numerous errors that the script "seemed" to fix about missing partitions.
-Reflash TWRP
-Android L gets stuck in non-bootable state (spinning colored ball logo thing) after a random restart.
-Now TWRP cannot find any .zip that I manually push through ADB. I can see it in File Manager, but nowhere else. Flashing custom ROM at this point not possible.
-Return to Android KitKat stock image and manually flash system.img through fastboot. Tablet will not boot, goes directly to black screen after bootloader.
So WTF do I do at this point? I have just about had it with all things Android right now. CWM doesn't work. TWRP doesn't work. Stock images don't work. Fastboot doesn't work. What else is there?
Click to expand...
Click to collapse
Is this an LTE or WiFi model? Do you have the nexus root tool kit installed on your computer and able to get to fastboot?

someolddude said:
Is this an LTE or WiFi model? Do you have the nexus root tool kit installed on your computer and able to get to fastboot?
Click to expand...
Click to collapse
WiFi model, fastboot and adb are fine, no toolkits.

Cortimi said:
WiFi model, fastboot and adb are fine, no toolkits.
Click to expand...
Click to collapse
Get the toolkit by wugfresh and you should be able to restore it.

someolddude said:
Get the toolkit by wugfresh and you should be able to restore it.
Click to expand...
Click to collapse
Nope. Using the Flash Stock + Unroot option gives the exact same error as doing it manually.
Flash Stock + Unroot...
------------------------------------------------------------------
sending 'bootloader' (3911 KB)...
OKAY [ 0.129s]
writing 'bootloader'...
OKAY [ 1.283s]
finished. total time: 1.412s
rebooting into bootloader...
OKAY [ 0.006s]
finished. total time: 0.006s
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
failed to allocate 754455404 bytes
error: update package missing system.img
Booting up your freshly flashed stock device...
------------------------------------------------------------------
Wait for your device to finish booting up...
- It may appear to be boot looping; just wait...
- It could take 5-10 minutes; please be patient...
When its finally booted back up, please remember
to re-enable USB debugging if you plan on using
the toolkit to perform other operations.
NOTE: If this process was too quick and your device
is still in bootloader mode, then flashing stock may
have failed or been incomplete. Simply check the
log above: if you notice it skipped steps because it
didn't meet certain requirements, like the bootloader
or baseband version, then consider enabling 'Force Flash'
mode in the toolkits options menu and trying the
'Flash Stock + Unroot' processs again. Cheers.
Press any key to exit...
Click to expand...
Click to collapse
Attempting to flash CWM recovery (found here: http://forum.xda-developers.com/showthread.php?t=2583845) results in a stuck bootloader screen. I was able to re-flash TWRP, but it is still useless as it simply does not function in any useful manner whatsoever.

Cortimi said:
Nope. Using the Flash Stock + Unroot option gives the exact same error as doing it manually.
Attempting to flash CWM recovery (found here: http://forum.xda-developers.com/showthread.php?t=2583845) results in a stuck bootloader screen. I was able to re-flash TWRP, but it is still useless as it simply does not function in any useful manner whatsoever.
Click to expand...
Click to collapse
Same problem with mine, cm11 as well.
I like some of the CM features but ever device Ive flashed and had trouble with it has been when Ive went with "Cyanide Mod"
You figure something out, please let me know and I will do the same.

I've got the LTE but my daughter has the WiFi only and is also unlocked. I can make a bone stock backup of here's which is on 4.4.4 if you want to try and restore it to yours.

Made an stupid error when flashing my phone - help needed eventually

Hi,
have to say it was my first try ever to flash a phone.
I've followed the ReadMe-Thread to the letter and with a little bit of try&error I got it done smoothely until I came to flashing the CustomRom "lineage-18.1-20210311-UNOFFICIAL-hima".
The instruction is " Choose "Wipe" and wipe everything except for "Micro SDcard", "USB-OTG" and "SD-Ext" via the advanced wipe. ".
What I did was exactly the opposite. I did mark "Micro SDcard", "USB-OTG" and "SD-Ext" and wiped it. There was an error message but as I was shocked about my mistake I can not remember any detail.
I've done it the right way after this error without booting the device and as far as I see it the flash was successful. The phone now starts Lineage and seems to work. Not sure yet as I have not got a new prepaid SIM but it's underway already. But the "rest" of it works. Have installed some apps with adb already.
BUT: It seems as I have destroyed the recovery mode at least. When I try to boot into recovery I only get a normal boot into LineageOS. Means that I start to bootloader mode and then select "Boot to recovery" the screen becomes black and then after some time the LineageOS starts. I can also switch between download ans bootloader mode but can not reach recovery.
AND the htc_fastboot command does not have any effect, will say NO devices are visible.
May someone in the know please enlighten me what I've done and how I may eventually recover the recovery mode?
Thank you very much for reading this and if I've written absolute nonsense here please bear with me, I'm German.

I guess you can flash custom recovery again using fastboot and reinstall Lineage!

Thanks.
When I try to use htc_fastboot there is no reaction and "htc_fastboot devices" shows nothing.

Same problem with me. to negligence, i didn't do this " "Wipe" and wipe everything except for "Micro SDcard", "USB-OTG" and "SD-Ext" via the advanced wipe" and installed the lineage 18.1. and now I don't have Recovery and the phone boot to lineage os but it will not boot totally. it will shut down and then boot again. (loop)
please help me.
I can boot to download mode
unlocked
s-on
Os-4.28.401.3
any help is much appreciated. thank you in advance

Hello,
I have a similar problem. It is an m9 with an unblocked bootloader. I got it from a colleague.
It had a cyanogen mod and TWRP on it. I set the cyandogen mod to factory settings and then activated the developer options so that I can boot directly into the recovery from the operating system.
It also worked perfectly. Then I wanted to update TWRP with the TWRP app.
It worked until I was asked whether I wanted to flash TWRP into the recovery or into the boot.
I chose recovery and thus rendered the phone unusable. It only boots into the bootloader or into download mode.
My attempts to flash a stockrom via adb or an executable file on a windows pc failed.
With the latter, the smartphone at least responds via the usb port. But so far I have not found the right RUU file for the phone.
Unfortunately, it also does not respond to 0PJAIMG.zip files on an sdcard formatted with FAT32.
Is there a way to force-flash TWRP onto the phone?
Many greetings
Draal