Okay, im done with everything, cant get it back working. So, here is my full story:
Got the HTC one mini, european version
unlocked bootloader, installed cwm, rooted, Backup.
installed xposed framework
everything working like a charm.
than i accidantly flashed the wrong zip file for DSPmanager v3. it was for the HTC One X.
now my HTC boots up : htc logo, blackscreen, htc one logo with animation ( beats audio logo on bottom) but no sound.
than it goes to the homescreen, everything works, but in just a few seconds ( about 5-10) it hangs and reboots -> bootloop.
-tried to recover from backup, no change, still no sound and bootloop.
-tried to recover with OTA update, didnt work, no matter what.
-checked the zip file i installed and found that it just copied some files :
system/app/DSPManager.apk
system/etc/audio_effects.conf
system/lib/soundfx/libaudiopreprocessing.so
libbundlewrapper.so
libcyanogen-dsp.so
libreverbwrapper.so
libvisualizer.so
-also found that the install script tried ( or maybe actualy did) : format("ext4", "EMMC", "/dev/block/mmcblk0p17");
mount("ext4", "EMMC", "/dev/block/mmcblk0p16", "/system");
now i am not quite familiar with the partition list of the mini, but i guess the script delete something importent.....
these are the informations of my bootloader:
***tampered ***
***unlocked ***
M4_UL PVT SHIP S-ON RL
HBOOT-2.21.0000
RADIO-1.22.40e.00.07
OS-2.12.401.1
eMMC-boot 1024MB
any ideas???
btw, sry for any wrong spellings, im from germany, so please be patient with me <-<
forget to mention, adb works within the recovery but not in the short time the Phone is booted up before it shuts down, so no chance of logging the system.... at least none i know
Related
Hi, second phone I work on.
Got this:
DREAM PVT 23B SHIP S-ON d
HBOOT-1.33.0010 (DREA21000)
CPLD-4
RADIO-3.22.20.17
This one was a Rogers post-911 so had trouble. Using flashrec, I was only able to flash using their network address and not the recovery.img on the sd card (amonra 1.7).
Well after doing this, I couldnt get into the recovery menu so rebooted to work back from there.
So had to stop working on it and now the phone ran out of battery. Turning the phone back on gives me the ! mark after the splashscreen.
My friend did factory reset but problem persists.
I can boot into fastboot. Not rooted (S-ON) so I can't seem to flash the recovery image.
Any clue?
You'd need to flash an official (signed) ROM.
Thanks for the answer, really appreciated.
So I would only need to flash the signed rom and then boot and then find a way to flash the recovery and root it, right?
Any indications to a signed rom?
Can I still fastboot flash?
If you have paypal, I'll buy you a beer for helping!
Hi Friends,
I yesterday tried to flash my Desire S but now i have faced a huge problem.It shows and stopped in HTC log.
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 2011, 15:22:13
Here i flashed with clockwork mode recovery.
Rooted using:su-3.0.5-efgh-signed.zip
and finally installed CWM v5.0.2.0.There i successfully fully backed up current ROM too.So far everything was fine and now started the scary part.
after that i downloaded MIUI.us_saga_v4_2.11.9_Eng_Deo_ZipA_Signed.zip and flashed with it.Everything went fine and no errors found and i kept whole night assuming it
would take time to get booted up.But i felt some thing is wrong and tried to restore my initial rom back up via CWM.But it restored with no erros but still stopped with HTC logo.
I did wipe date/factory reset,wipe cache partition, and wipe Dalvik cache and flashed CM 7.2 even result is same.And now i cant run adb where it shows no devices in fast-boot screen.
I feel i did a mistake by not using the boot.img in rom. isn't?Further any idea to make my back up work?
codefreaker00 said:
Hi Friends,
I yesterday tried to flash my Desire S but now i have faced a huge problem.It shows and stopped in HTC log.
*** UNLOCKED ***
SAGA PVT SHIP S-ON RL
HBOOT-2.00.0002
RADIO-3822.10.08.04_M
eMMC-boot
Aug 22 2011, 15:22:13
Here i flashed with clockwork mode recovery.
Rooted using:su-3.0.5-efgh-signed.zip
and finally installed CWM v5.0.2.0.There i successfully fully backed up current ROM too.So far everything was fine and now started the scary part.
after that i downloaded MIUI.us_saga_v4_2.11.9_Eng_Deo_ZipA_Signed.zip and flashed with it.Everything went fine and no errors found and i kept whole night assuming it
would take time to get booted up.But i felt some thing is wrong and tried to restore my initial rom back up via CWM.But it restored with no erros but still stopped with HTC logo.
I did wipe date/factory reset,wipe cache partition, and wipe Dalvik cache and flashed CM 7.2 even result is same.And now i cant run adb where it shows no devices in fast-boot screen.
I feel i did a mistake by not using the boot.img in rom. isn't?Further any idea to make my back up work?
Click to expand...
Click to collapse
used to had that kind of problem...i had to pulled out battery, power + volume button to enter recovery....in recovery re-install the backup......(note: pulling battery is very dangerous as mention everywhere here)
That was a mistake, yes. But if you haven't flashed any boot.img since rooting your phone, I would have expected restoring the backup should have worked.
Or have you flashed a boot.img in between?
1. extract "boot.img" from inside the zip file of the ROM.
2. install the ROM
3. reboot into bootloader and goto fastboot
4. in your PC's command prompt run "fastboot flash boot boot.img"
check this for help http://forum.xda-developers.com/showthread.php?t=1525100
I'm wondering, how many more threads like this can a forum tolerate. At any given time there are 2 threads like that on the front page of the forum. WTF? Should be THE most asked question since HTC released bootloader unlock - and people didn't learn to read/search yet.
FASTBOOT FLASH BOOT BOOT.IMG
Yes, that includes restoring from backups too. If you read that recovery can't flash kernels - it means IT CAN'T EVER FLASH ANY KERNEL FROM ANYWHERE.
hey guys, somehow i've messed up some steps when i first tried to root my phone. I ended up wiping my OS and the phone is only able to boot into fastboot. I've downloaded TWRP 2.6.3.0 and tried to install the roms provided in the development thread but each time, the downloads get stuck installing halfway through. Even after waiting more then 10 mins, the progress bar still sits in the middle.
Heres what i did
Installed TWRP
Cleared catches
Installed superusr
At times, i cant seem to mount /data but it seems like after i installed superusr, the problem cleared, but whenever i try to install any rom after that, it will always stop halfway.
Here is what it says on my fastboot screen
M4_UL PVT SHIP S-ON RL
HBOOT-2.22.0000
RADIO-1.24.40e.00.26
OpenDSP-v19.2.0268.0927
OS-3.10.707.3
eMMC-boot 1024MB
Jan 29 2014, 20:00:29:0
Im at my wits end and i really hope anyone out there could help.
Thanks.
Try to do a factory reset, wipe all cashes etc, and what was the ROM? Are you sure it is compatible?
IF
( Fast Boot is unchecked [in Settings/Power/Fast boot] AND usb cable is attached )
THEN
using the power button to “power down” phone immediately boots to unresponsive TWRP screen.
ENDIF
What is the relationship between Fast boot/Slow boot and the usb cable? Is this usual behavior?
I am assuming this is a problem and show the important information below
HTC One Max Phone state:
*** TAMPERED ***
*** UNLOCKED ***
T6UL PVT SHIP S-OFF RH
CID-VODAP001
HBOOT-2.49.0000
RADI0--4T.24.3218.09
OpenDSP-,v33.120.274_T6.0829
QSC*
OS-
eMMC-hoot 2048MB
Feb 7 2014J15:26:45.0
Here is what I did leading up to this problem:
1. Unlocked bootloader (htcdev)
2. SuperSU (v2.01)
3. Nandroid backup with TWRP (which backed up boot and system and data partitions)
4. Try to install xposed (since I want control over my sd card!) Noticed that it would be easier if I had s-off (and wanted to s-off sometime anyway).
5. S-off using firewater (which worked)
6. Nandroid restore - restored system and data partitions (not boot)
Noticed problem at this point.
Here is what I have done so far in an attempt to fix this problem:
1. booted to TWRP recovery (via adb) and did wipe (factory reset - which wipes data, cache and dalvik). Problem still there.
2. Nandroid restore - restored boot and system and data partitions. Problem still there.
3. TWRP – fix permissions. Problem still there.
It would be beneficial to ther s if you could post in One Max General
Also the right experts would be able to help you.
Hey guys, I sold my One M8 to my little brother's friend a few months ago. It's Unlocked, S=Off, and SuperCID with the following:
HBOOT = 3.16.0.0000
RADIO = 0.56.20.0321
OpenDSP - V38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Apr 1 2014,00:26:53.0
TWRP V2.7.0.2
Since he's had it, he says he's only flashed Liquidsmooth, MIUI, and the stock rom. He swears the phone was running great for the past month or so on the stock rom. According to him, he hasn't flashed anything in at least a month. Last night, he plugged it up like usualand woke up to the phone completely powered off. When he booted it, it boots normally and soon after unlocking it, it reboots. This has been the case since I received it back from him (to fix). It's stuck in a bootloop that I cannot fix. Shortly after booting the rom (stock), it will reboot.
What I've tried:
Flashing a new rom in TWRP.
Wiping everything in TWRP (including system w/ and w/o the system partition mounted)
Fixing permissions in TWRP
Flashing SuperSu in TWRP (don't ask why, Googled it and someone said it fixed theirs)
All of this just continues to reboot to the same stock rom that it was already on. Shortly after booting, it would reboot as if I'd made no changes, wipes, etc.
So I figured I'd update TWRP. I downloaded TWRP_Recovery_2.8.2.1_M8_CPTB.img and flashed it in fastboot (without using fastboot oem rebootRUU) It was successful (or so it seemed). When I reboot recovery it still shows 2.7.0.2. So I downloaded ruuM8_TWRP_2_7.zip, tried to flash it from fastboot but when I "Fastboot oem rebootRUU" it jumps back to the bootloop so I put it on the ext_sdcard and renamed it to 0P6BIMG.zip. Hboot flashed it successfully but still the version didn't change.
So after all has failed, let's flash the stock RUU......So I grabbed this RUU - http://forum.xda-developers.com/showthread.php?t=2727831, renamed it to 0P6BIMG.zip and put in on the external sdcard (remember fastboot just kicks me into a bootloop when I fastboot oem rebootRUU). Using the sd card method, It took forever to flash the system partition, extracting and installing about a half dozen times. Eventually everything passed and it prompted me to press power up to reboot. AND IT BOOTS BACK TO THE SAME LOCK SCREEN.....AND REBOOTS AFTER A FEW SECONDS. I've flashed the stock RUU several times now with the same results. It's as if this phone can't flash anything although it acts as if it flashes successfully.
Anybody have any experience with this? Any suggestions are appreciated.
Sounds like emmc is fried. Send it in for repair.
joshw0000 said:
Hey guys, I sold my One M8 to my little brother's friend a few months ago. It's Unlocked, S=Off, and SuperCID with the following:
HBOOT = 3.16.0.0000
RADIO = 0.56.20.0321
OpenDSP - V38.2.2-00542-M8974.0311
OS-
eMMC-boot 2048MB
Apr 1 2014,00:26:53.0
TWRP V2.7.0.2
Since he's had it, he says he's only flashed Liquidsmooth, MIUI, and the stock rom. He swears the phone was running great for the past month or so on the stock rom. According to him, he hasn't flashed anything in at least a month. Last night, he plugged it up like usualand woke up to the phone completely powered off. When he booted it, it boots normally and soon after unlocking it, it reboots. This has been the case since I received it back from him (to fix). It's stuck in a bootloop that I cannot fix. Shortly after booting the rom (stock), it will reboot.
What I've tried:
Flashing a new rom in TWRP.
Wiping everything in TWRP (including system w/ and w/o the system partition mounted)
Fixing permissions in TWRP
Flashing SuperSu in TWRP (don't ask why, Googled it and someone said it fixed theirs)
All of this just continues to reboot to the same stock rom that it was already on. Shortly after booting, it would reboot as if I'd made no changes, wipes, etc.
So I figured I'd update TWRP. I downloaded TWRP_Recovery_2.8.2.1_M8_CPTB.img and flashed it in fastboot (without using fastboot oem rebootRUU) It was successful (or so it seemed). When I reboot recovery it still shows 2.7.0.2. So I downloaded ruuM8_TWRP_2_7.zip, tried to flash it from fastboot but when I "Fastboot oem rebootRUU" it jumps back to the bootloop so I put it on the ext_sdcard and renamed it to 0P6BIMG.zip. Hboot flashed it successfully but still the version didn't change.
So after all has failed, let's flash the stock RUU......So I grabbed this RUU - http://forum.xda-developers.com/showthread.php?t=2727831, renamed it to 0P6BIMG.zip and put in on the external sdcard (remember fastboot just kicks me into a bootloop when I fastboot oem rebootRUU). Using the sd card method, It took forever to flash the system partition, extracting and installing about a half dozen times. Eventually everything passed and it prompted me to press power up to reboot. AND IT BOOTS BACK TO THE SAME LOCK SCREEN.....AND REBOOTS AFTER A FEW SECONDS. I've flashed the stock RUU several times now with the same results. It's as if this phone can't flash anything although it acts as if it flashes successfully.
Anybody have any experience with this? Any suggestions are appreciated.
Click to expand...
Click to collapse
Had one of these where the radio died. Did the same exact thing. Kmsg revealed an attempt to start the radio and the subsequent failure. I got it back to locked (not relocked) and s-on and opted for a replacement from HTC.
I can't relock it. I can't even overwrite TWRP.
joshw0000 said:
I can't relock it. I can't even overwrite TWRP.
Click to expand...
Click to collapse
Like I said earlier, its broken. Get it fixed if you can.