Database Develop

phone softbricked, unflashable, cannot use fastboot or adb, even more issues.

so i need some serious advice. i had my phone rooted, and i screwed up and while attempting to fix the tiny storage size bug (it was 2 AM), i formatted EVERYTHING because i somehow managed to forget what the word 'format' means. so now; it is softbricked, the sdcard has no rom files on it to be flashed, i cant mount it anyway, i get an error saying 'missing UMS lunfile' when i try to mount the usb, adb wont detect my phone, fastboot just sits there, the RUU says it cant find any devices, i cant lock my phone's bootloader either. . my hboot is 1.28, i was using a custom version of ICS, and it was bought in australia a few days before the update. i rooted while running ICS.

PlasticTurd said:
so i need some serious advice. i had my phone rooted, and i screwed up and while attempting to fix the tiny storage size bug (it was 2 AM), i formatted EVERYTHING because i somehow managed to forget what the word 'format' means. so now; it is softbricked, the sdcard has no rom files on it to be flashed, i cant mount it anyway, i get an error saying 'missing UMS lunfile' when i try to mount the usb, adb wont detect my phone, fastboot just sits there, the RUU says it cant find any devices, i cant lock my phone's bootloader either. . my hboot is 1.28, i was using a custom version of ICS, and it was bought in australia a few days before the update. i rooted while running ICS.
Click to expand...
Click to collapse
Have u tried lex's multi tool . http://forum.xda-developers.com/showthread.php?t=1865265 that's the only thing I can think of regarding to help ur situation.
Sent from my HTC Sensation XL with Beats Audio X315e using xda app-developers app

PlasticTurd said:
so i need some serious advice. i had my phone rooted, and i screwed up and while attempting to fix the tiny storage size bug (it was 2 AM), i formatted EVERYTHING because i somehow managed to forget what the word 'format' means. so now; it is softbricked, the sdcard has no rom files on it to be flashed, i cant mount it anyway, i get an error saying 'missing UMS lunfile' when i try to mount the usb, adb wont detect my phone, fastboot just sits there, the RUU says it cant find any devices, i cant lock my phone's bootloader either. . my hboot is 1.28, i was using a custom version of ICS, and it was bought in australia a few days before the update. i rooted while running ICS.
Click to expand...
Click to collapse
U can flash the rom.zip(extracted from the ruu) using fastboot command fastboot flash zip rom.zip
Sent from my HTC One XL using xda premium

fshami said:
U can flash the rom.zip(extracted from the ruu) using fastboot command fastboot flash zip rom.zip
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
okay, update :L
i still cannot use adb. i have howerver managed to get fastbot working, so i tried to flash a rom; no luck. so i locked my phone and ran the RUU. no stupid error message this time, because this time it was retarded: WRONG RUU VERSION, PLEASE USE THE CORRECT UTILITY.
see, im in australia, and there are only 2 ruu for the land down under. this is the second one ive tried, after th first one GAVE ME THE SAME ERROR
soi have some questions:
1) is it possible i have a european or otherwise overseas model?
2) this one is badly worded and confusing, so bear with me:
i dont have clockworkmod on account of locking again, but i think the inabilty to flash the phone may come from the inability to contact the sdcard. is there a command in fastboot that would set the partitions back up from scratch? if i can do that, i could then flash the adb drivers back on my phone, then use adb push to force the damn rom.zip onto my strorage then use clockworkmod to flash the rom? (all my grammar are belong to hulk)
i need a speedy reply as ive got my boss breathing down my neck about this (if i dont fix it they cant contact me if im not in the office or home)

PlasticTurd said:
okay, update :L
i still cannot use adb. i have howerver managed to get fastbot working, so i tried to flash a rom; no luck. so i locked my phone and ran the RUU. no stupid error message this time, because this time it was retarded: WRONG RUU VERSION, PLEASE USE THE CORRECT UTILITY.
see, im in australia, and there are only 2 ruu for the land down under. this is the second one ive tried, after th first one GAVE ME THE SAME ERROR
soi have some questions:
1) is it possible i have a european or otherwise overseas model?
2) this one is badly worded and confusing, so bear with me:
i dont have clockworkmod on account of locking again, but i think the inabilty to flash the phone may come from the inability to contact the sdcard. is there a command in fastboot that would set the partitions back up from scratch? if i can do that, i could then flash the adb drivers back on my phone, then use adb push to force the damn rom.zip onto my strorage then use clockworkmod to flash the rom? (all my grammar are belong to hulk)
i need a speedy reply as ive got my boss breathing down my neck about this (if i dont fix it they cant contact me if im not in the office or home)
Click to expand...
Click to collapse
Well, i don't really understand a thing, why people don't use recovery + S-OFF.
The best way to ensure your device works as it should and avoid future problems, is to have a custom recovery, and S-OFF, this avoids soft-bricking, and i never really understanded soft-brick term as long as you have fastboot...
You can always unlock your bootloader, and flash a recovery again, use XL Multi Tool.
Flash a recovery, flash a ROM, flash S-OFF, flash a new RUU, and as far as i know you don't need ro lock bootloader in order to flash a new RUU if you are S-OFF, so try it like this
Hope this helps

[Solved] Stuck on white hboot screen while downgrading

Hi,
I had unlocked boot loader through HTCdev on latest GB stock ROM. So, obviously I was S-ON.
Meanwhile, I tried many ROMs but manually flashing boot image in hastboot.
I had following status of last running mobile when I tried to get S-OFF
Bootloader status: unlocked
S-ON
HBOOT 2.00.0000
Recovery: CWM
ROM: CynovivoX (JB 4.1.2)
Yesterday, I tried to get S-off by downgrading as per following thread
http://forum.xda-developers.com/showthread.php?t=1705913
There were lots of error while script was running, but one I remember was related to goldcard.
While running RUU, It goes well till I find something Error 131, Customer ID related and than exit.
After trying script and RUU many times, my status is
Bootloader status: Relocked
S-ON
HBOOT 2.00.0000
Recovery: ? (can't see or access anymore)
ROM: -
when running fastboot devices, my device is appearing
but in adb devices, nothing there
So, is there still any possibility to recover from this bricked state?
Desperately looking for expert help as I am not developer but somehow....tried this thinking would not be that difficult business....so help.

Try running the latest RUU and restarting everything over. Make sure to pick the right RUU for your region. The latest build number should be 4.14.XXXXX...
Also, in fastboot, your device isn't supposed to be visible with command of adb devices.
Another thing u could try is to unlock the bootloader again and see if u can access recovery again. Adb works in recovery
Sent from the head of the Hammer

If you can get into fastboot but don't have a recovery installed, can't you just flash a new recovery? E.g. grab clockworkmod, connect your phone to your computer via usb and:
Code:
fastboot flash recovery recovery-clockwork-5.0.2.0-vivo.img
(obviously replace above code with actual name of .img file)

err this might be stupid, but click on bootloader > recovery.
Looks like you are already in a sub menu when you boot the bootloader.
The error while downgrading is related to you not relocking your phone before downgrading. Always relock before downgrading with an RUU.
Sent from my Nexus 5

Thanks all guys.
But problem fixed. I have unlocked the bootloader again through htcdev and it worked.
Now let me share issue for all other nondevelopers like me who may also face such issue...
runme script is suppose to push some files through adb commands and then reboot to fastboot mode to lock bootloader.
I had adb drivers installed as I got prompt from statusbar.
However still, while running downgrade script (runme), phone was not detected in adb mode and hence no file was pushed to phone. After reboot, phone detected in fastboot and OEM successfully relocked.
I am really surprised why device not found error not appeared and script not stopped. Later I came to know this by running the script without connecting phone and it ran with asking Q&A with found device, and also reading log file.
Then I ran RUU who wiped everything.
So, my device left without any ROM and with OEM locked. I can't access or install recover, ROM etc and RUU was having goldcard error.
Somehow tried to unlock again through token provided by HTCDev earlier (around 2 years back).
And thing become normal and in my control.
My advise: always check "adb devices" before running the script as I found script is misleading of found device and finally locking device. And if such thing happen, easiest one is to get in unlocked from HTCDev and restart whole process.

RmatriX1218 said:
Thanks all guys.
But problem fixed. I have unlocked the bootloader again through htcdev and it worked.
Now let me share issue for all other nondevelopers like me who may also face such issue...
runme script is suppose to push some files through adb commands and then reboot to fastboot mode to lock bootloader.
I had adb drivers installed as I got prompt from statusbar.
However still, while running downgrade script (runme), phone was not detected in adb mode and hence no file was pushed to phone. After reboot, phone detected in fastboot and OEM successfully relocked.
I am really surprised why device not found error not appeared and script not stopped. Later I came to know this by running the script without connecting phone and it ran with asking Q&A with found device, and also reading log file.
Then I ran RUU who wiped everything.
So, my device left without any ROM and with OEM locked. I can't access or install recover, ROM etc and RUU was having goldcard error.
Somehow tried to unlock again through token provided by HTCDev earlier (around 2 years back).
And thing become normal and in my control.
My advise: always check "adb devices" before running the script as I found script is misleading of found device and finally locking device. And if such thing happen, easiest one is to get in unlocked from HTCDev and restart whole process.
Click to expand...
Click to collapse
From what I'm reading, I'm getting a much clearer image of what happened. I believe your problem to be just driver errors...
The script itself is supposed to run regardless of whether phone is properly connected with proper drivers and whatnot. After all, it's just a set of commands in cmd.
But seeing as you ONLY got Error 131, you could have solved this by simply creating a goldcard.

072665995 said:
From what I'm reading, I'm getting a much clearer image of what happened. I believe your problem to be just driver errors...
The script itself is supposed to run regardless of whether phone is properly connected with proper drivers and whatnot. After all, it's just a set of commands in cmd.
But seeing as you ONLY got Error 131, you could have solved this by simply creating a goldcard.
Click to expand...
Click to collapse
Phone was connected in adb mode. This I can say by checking notifications in android and statusbar prompt in windows 7. While running script only, something got wrong getting adb mode not detected.
Anyway, Goldcard was also in my next line of action, but not sure even after creating Goldcard, I may stuck as version-main was not downgraded to 2. However, tried and got resolved with much simpler effort of unlocking through htcdev.
May be, I am also not that competent to understand developing world and only good enough to simply flash ROMs and updates as per instructions.
Anyway, thanks.

S-OFF for Desire 500?

Is there a way of getting S-OFF for this device? I am having major problems without it...
Okay, so I'll start at the beginning. Once upon a time (two days ago), I bought a Desire 500 from ebay that was stuck at the bootloader screen. It arrived today and I have unlocked the bootloader with HTCDEV, but I cannot flash recovery with fastboot. It seems to accept the flash on my computer, but when I try to enter recovery the phone just hangs. I have tried to flash the zip with fastboot, but the error message:
FAILED (remote: not allowed)
keeps coming up. AFAIK this is because I don't have S-OFF, but I should still be able to flash recovery.
Can anyone help?
EDIT - OK, so rumrunner can S-OFF it, but you have to have a ROM installed to use it...

I don't understand....
I literally don't know what I'm doing wrong. I've even found the ROM with the correct CID and tried to flash it through fastboot and RUU mode but it's not working.
Somebody help please... I have tried searching for the answer...
EDIT - I have flashed the correct CWM for my hboot and it has hung on:
Entering Recovery...
with the white HTC screen. It has been like this for ten minutes...

rumrunner didn't s-off my dual desire500.
it's fully rooted
has cwm on it
has not busybox n i wanted to s-off my phone in order to push busybox in it.
any idea?

Dead phone
First of all in order to install the original firmware (so called stock rom) your device needs to be in locked status. Other than that :
I also wanted to s-off my phone which is also stuck both on HTC screen and when trying to enter the recovery. Many articles and threads are saying you need to enable usb debugging in phone options but if you are phone can not load the android os and the corrresponding menu, applying this setting it is not possible. Therefore you can consider your phone is nothing but a flashlight at the moment.
Regarding my searchs our phone's emmc is corrupt or needs to be reprogrammed or something like it. It is not possible to load the official firmware using RUU files or any other custom ROMs.
kiaheyrati038 said:
rumrunner didn't s-off my dual desire500.
it's fully rooted
has cwm on it
has not busybox n i wanted to s-off my phone in order to push busybox in it.
any idea?
Click to expand...
Click to collapse

Bootlooping Tmobile HTC One M9 - Please help

Heya!
Totally new to all of this, so please be gentle. My M9 is now bootlooping and the past hour of research hasn't helped me.
I've just done the following with my Tmobile marshmallow M9:
1) Used HTC's dev tools to unlock the bootloader
2) Flashed twrp-2.8.7.1_CPTB-B1-hima.img using fastboot
3) Immediately after flashed BETA-SuperSU-v2.66-20160103015024.zip using twrp
4) Backed up everything using twrp
My phone is now boot looping. I tried clearing cache/dalvik/data with no luck. Honestly, I'm fine with either loading a stock rom or going to viper like I originally intended, but I don't know how - I don't have either of those on my SD card and I know that I need to get them off of my computer onto the phone, but ADB and my device manager don't see the phone when I'm in TWRP. When I'm in the bootloader, I see "My HTC" in device manager and HTC sync picks up like it sees the phone.
I just want a working phone again. I hear that SuperSU 2.65 is probably more stable, but I don't care whether I root and viper or go back to stock as long as the phone works. I would have figured driver issues if not for the perfectly functional/device manager viewable fastboot. Without ADB seeing the device in twrp, I can't sideload, push files or mount storage to get a new rom on there to fix it. I'm not even sure whether it's TWRP or the SuperSU flash that boot looped me, though I figured that by clearing /data/dalvik/cache I killed SuperSU so it might be twrp.
All solutions I've found so far assume that ADB is working/the device can be seen or assume that simple driver reinstalls will fix the problem, but I haven't had any luck with that so far even though I've tried uninstalling/reinstalling drivers a few times.
Any ideas? Please help me - I'm stumped!

Relock bootloader and run an RUU.
HTC One M9

Jtsessions said:
Heya!
Totally new to all of this, so please be gentle. My M9 is now bootlooping and the past hour of research hasn't helped me.
I've just done the following with my Tmobile marshmallow M9:
1) Used HTC's dev tools to unlock the bootloader
2) Flashed twrp-2.8.7.1_CPTB-B1-hima.img using fastboot
3) Immediately after flashed BETA-SuperSU-v2.66-20160103015024.zip using twrp
4) Backed up everything using twrp
My phone is now boot looping. I tried clearing cache/dalvik/data with no luck. Honestly, I'm fine with either loading a stock rom or going to viper like I originally intended, but I don't know how - I don't have either of those on my SD card and I know that I need to get them off of my computer onto the phone, but ADB and my device manager don't see the phone when I'm in TWRP. When I'm in the bootloader, I see "My HTC" in device manager and HTC sync picks up like it sees the phone.
I just want a working phone again. I hear that SuperSU 2.65 is probably more stable, but I don't care whether I root and viper or go back to stock as long as the phone works. I would have figured driver issues if not for the perfectly functional/device manager viewable fastboot. Without ADB seeing the device in twrp, I can't sideload, push files or mount storage to get a new rom on there to fix it. I'm not even sure whether it's TWRP or the SuperSU flash that boot looped me, though I figured that by clearing /data/dalvik/cache I killed SuperSU so it might be twrp.
All solutions I've found so far assume that ADB is working/the device can be seen or assume that simple driver reinstalls will fix the problem, but I haven't had any luck with that so far even though I've tried uninstalling/reinstalling drivers a few times.
Any ideas? Please help me - I'm stumped!
Click to expand...
Click to collapse
Go back to TWRP and flash the stable SuperSU 2.65. Beta bootlooped for me too and then I went back to TWRP and flashed 2.65 and it was fine.
When you're in TWRP you should be able to connect the device to your computer and copy the 2.65 to phone storage and then be able to flash it.

Need help please.

I got an M9. Wanted to root it to remove bloatware. Everything was going fine until I flashed supersu zip through TWRP. I didn't let TWRP install supersu as per instructions but I ran into the bootloop issue and decided to just go back to stock. Well I made a noob mistake and relocked the bootloader. Now the phone fails to enter recovery and when I reboot, it boots directly into the bootloader. I've been researching for hours and hours trying to find a resolution to just flash the stock RUU but when I run the file it comes up with the error no device is attached. The phone shows up in my device manager just fine but won't connect to ADB or when I tried running the RUU exe even that said there were no devices attached Also my phone is now not able to be found in adb or fastboot. If you could lend any assistance as to what I might be able to do just to even get it back to stock I would greatly appreciate it.
It's a T-Mobile HTC M9
bootloader is showing relocked.
S-On
Thanks for any help.
Update. I tried using Squabbi M9 toolkit but again the same issue with no devices attached. I'm guessing it has to do with usb debugging not being enabled? I'm not sure. It was enabled when I started the whole process but now that I can't boot into the phone itself I can't check anything. If anyone could offer at least a little assistance I would greatly appreciate it.