Related
Hello,
I visit this forum every day to stay up to date with all the ROMs. Im trying to help fix a friend's phone and I apologize if this is in the wrong forum but I think this forum contains the audience who can help with this. Basically my friend brought me his G2 (which I rooted and put CM7 on it for him) and it wouldnt boot. I know all the regular ways to recover it but when booting into recovery I get these errors:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
Here is a Pastebin with the recovery log:
http://pastebin.com/qT4KMrUj
Cannot update to the newest recovery using fastboot (CWM version is 3.0.0.5) but i booted to CWM 3.0.2.4 with the fastboot boot recovery.img command. I cannot restore a backup, cannot format /boot or /system (get the "error formatting /system" message). I wiped cache and data and this didnt help. Tried loading a new cm7 zip. If I try to flash the latest recovery in fastboot it doesnt work:
c:\download\android-sdk-windows\tools>fastboot flash recovery recovery-clockwork
-3.0.2.4-vision.img
sending 'recovery' (4466 KB)... OKAY [ 0.760s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 0.780s
I tried loading a PC10IMG.zip from an RUU and I get a failed update on the first item. Im thinking this is some kind of partition issue. Does anyone have any ideas? Ive been searching the whole morning and there are a few threads in other forums regarding this and the best luck someone had was flashing with the PC10IMG.zip to fix it. The phone has the engineering hboot.
Code:
c:\download\android-sdk-windows\tools>fastboot oem listpartition
... INFO[merge_mfg]:(MERGEMFG, 10) block start=0,
size=0 (0 KB)
INFO[radio]:(OTHER, 4) block start=0, size=163840 (0 KB)
INFO[merge_emmc]:(RAW, 4) block start=0, size=4194304 (655360 KB
INFO)
INFO[fat]:(RAW, C00) block start=0, size=0 (0 KB)
INFO[local]:(RAW, 0) block start=0, size=0 (0 KB)
INFO[spcustom]:(RAW, 0) block start=0, size=0 (0 KB)
INFO[microp]:(OTHER, 0) block start=0, size=0 (0 KB)
INFO[cpld]:(OTHER, 0) block start=0, size=0 (0 KB)
INFO[rcdata]:(OTHER, 0) block start=0, size=0 (0 KB)
INFO[a1026]:(OTHER, 0) block start=0, size=0 (0 KB)
INFO[tp]:(OTHER, 0) block start=0, size=0 (0 KB)
INFO[wimax]:(RAW, 0) block start=0, size=0 (0 KB)
INFO[nv]:(OTHER, 0) block start=0, size=0 (0 KB)
INFO[htcdata]:(RAW, 7404) block start=143363, size=2048 (1233216
INFO KB)
INFO[radio_reserve]:(RAW, 7504) block start=145412, size=17915 (
INFO1661741 KB)
INFO[dzsystem]:(DEZERO, 8) block start=197122, size=851453 (4257
INFO26 KB)
INFO[dzdata]:(DEZERO, 8) block start=1048576, size=2723841 (1361
INFO920 KB)
INFO[misc]:(RAW, 7601) block start=163328, size=512 (256 KB)
INFO[hboot]:(RAW, 4701) block start=163841, size=2048 (1024 KB)
INFO[sp1]:(RAW, 3401) block start=165890, size=2048 (1024 KB)
INFO[wifi]:(RAW, 3601) block start=167939, size=2560 (1280 KB)
INFO[recovery]:(RAW, 7101) block start=170500, size=17402 (8701
INFOKB)
INFO[boot]:(RAW, 4801) block start=187903, size=8192 (4096 KB)
INFO[mfg]:(RAW, 7301) block start=196096, size=512 (256 KB)
INFO[misc2]:(RAW, 3101) block start=196609, size=512 (256 KB)
INFO[system]:(EXT3, 8301) block start=197122, size=851453 (42572
INFO6 KB)
INFO[userdata]:(EXT3, 8301) block start=1048576, size=2723841 (1
INFO361920 KB)
INFO[cache]:(EXT3, 8301) block start=3772418, size=419431 (20971
INFO5 KB)
INFO[devlog]:(EXT3, 1901) block start=4191850, size=40960 (20480
INFO KB)
OKAY [ 0.153s]
finished. total time: 0.153s
Thanks!
I just have to comment on the purple smileys all over nice touch lol!
Sent from my HTC Vision using XDA Premium App
xsteven77x said:
I just have to comment on the purple smileys all over nice touch lol!
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Yep, I fixed that with the code box. LOL
Can you use fastboot to boot the newest recovery?
"fastboot boot recovery recovery.img"
It sounds like the paritions are formatted in way the recovery is having a hard time with. The best thing to do would be to flash the older CWR from the 2 series then format and wipe all over the place. The try booting a froyo based rom and you should be good.
Then you can try to go back to CWR 3 series.
1wayjonny said:
Can you use fastboot to boot the newest recovery?
"fastboot boot recovery recovery.img"
It sounds like the paritions are formatted in way the recovery is having a hard time with. The best thing to do would be to flash the older CWR from the 2 series then format and wipe all over the place. The try booting a froyo based rom and you should be good.
Then you can try to go back to CWR 3 series.
Click to expand...
Click to collapse
Yep I tried this. I booted into the CWM 2.5.1.3 and tried to wipe and format /boot and /system but I get errors just like in CWM3.
I had this same issue one time and thought my phone was shot, just take the original shipping rom and flast it via fastboot boot as the PC10IMG.zip to fix this issue.
I know you have tried already, I have been at this stage just keep trying the PC10IMG.zip from a different source but that is the correct way to fix your issue if you tried previous CWR's.
try manually mounting the partition:
e2fsck -p /dev/block/mmcblk0p27
mount /dev/block/mmcblk0p27 /cache
1wayjonny said:
I had this same issue one time and thought my phone was shot, just take the original shipping rom and flast it via fastboot boot as the PC10IMG.zip to fix this issue.
I know you have tried already, I have been at this stage just keep trying the PC10IMG.zip from a different source but that is the correct way to fix your issue if you tried previous CWR's.
Click to expand...
Click to collapse
Can you recommend a particular file to use? Im looking at a list here:
http://shipped-roms.com/index.php?category=android&model=Vision
I would try these:
http://shipped-roms.com/download.php?category=android&model=Vision&file=PC10IMG_Vision_TMOUS_1.12.531.0_Radio_12.18.60.05P_26.01.00.17_M2_test_144460.zip
If that doesn't work try this one
http://shipped-roms.com/download.ph....09b_26.02.01.15_M2_release_149459_signed.zip
If these dont work I would be surprised and yes something more may be messed up.
I'm glad that this issue is getting more attention today. It has been occurring with more and more frequency since the release of the new CWM Recovery and CM7...
Well I thought I was the only one, this happened from using a specific build of the CWR 3 series.
Nice to know its wasn't just me but I def think its has to do with formatting of the partition but could be wrong.
Well, neither of those PC10IMG.zip worked. Im looking at another thread here to hopefully help out. Looks like a partition issue like I thought. Only thing is how to fix it?
http://forum.cyanogenmod.com/topic/6433-solved-messed-up-partitions-on-internal-storage/
Guys, I finally figured out how to fix this issue. It took me forever and I thought my recovery was lost but this fixed it.
Couple of things you have to do:
Download the latest ClockworkMod and rename it to recovery.img
adb reboot bootloader
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
Try to restore again
Yes erase the cache twice from fastboot.
open1your1eyes0 said:
Guys, I finally figured out how to fix this issue. It took me forever and I thought my recovery was lost but this fixed it.
Couple of things you have to do:
Download the latest ClockworkMod and rename it to recovery.img
adb reboot bootloader
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
Try to restore again
Yes erase the cache twice from fastboot.
Click to expand...
Click to collapse
The problem is that i cant get it to do anything.
Code:
c:\download\android-sdk-windows\tools>fastboot erase cache
erasing 'cache'... FAILED (remote: erasing error!)
finished. total time: 2.829s
c:\download\android-sdk-windows\tools>adb reboot bootloader
error: device not found
c:\download\android-sdk-windows\tools>fastboot flash recovery recovery-clockwork
-3.0.2.4-vision.img
sending 'recovery' (4466 KB)... OKAY [ 0.765s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 0.784s
c:\download\android-sdk-windows\tools>
In the thread i posted above, they talk about using "parted" to get the partitions back but I dont see where you can do thoe ADB commands. They suggest you can do them in recovery but I tried and there is no ADB device when in CWM.
Hopefully this isn't too off topic, but is there a tool that can be used to perform a health check of the internal and external storage of our phones? Everything on my phone is working just fine, but would love that guarantee that it's in good order.
Thanks.
amazinglarry311 said:
try manually mounting the partition:
e2fsck -p /dev/block/mmcblk0p27
mount /dev/block/mmcblk0p27 /cache
Click to expand...
Click to collapse
Where can I issue these commands? I cannot get a shell.
Stupid question about the PC10IMG.zip method...
It probally is but confirm the card is formatted as FAT32 for fastboot
Also is there any swap partitions etc..
If the SDCARD has partitions redo it as one FAT32 partition or use an alternate SDCARD with one FAT32 partition
popokrew said:
The problem is that i cant get it to do anything.
Code:
c:\download\android-sdk-windows\tools>fastboot erase cache
erasing 'cache'... FAILED (remote: erasing error!)
finished. total time: 2.829s
c:\download\android-sdk-windows\tools>adb reboot bootloader
error: device not found
c:\download\android-sdk-windows\tools>fastboot flash recovery recovery-clockwork
-3.0.2.4-vision.img
sending 'recovery' (4466 KB)... OKAY [ 0.765s]
writing 'recovery'... FAILED (remote: image update error)
finished. total time: 0.784s
c:\download\android-sdk-windows\tools>
In the thread i posted above, they talk about using "parted" to get the partitions back but I dont see where you can do thoe ADB commands. They suggest you can do them in recovery but I tried and there is no ADB device when in CWM.
Click to expand...
Click to collapse
Oh the issue appears to be the fact that adb cannot find your device. Go into device manager and see if you see any missing drivers with the exclamation mark (should be called ADB or something like that).
Force install these drivers I have uploaded: Link
Also after you do "adb reboot bootloader" command you need to install the drivers again because it reboots into another mode.
Make sure you select "Android ADB Interface" as the driver and if it asks you that its not compatible just click Yes anyways.
open1your1eyes0 said:
Guys, I finally figured out how to fix this issue. It took me forever and I thought my recovery was lost but this fixed it.
Couple of things you have to do:
Download the latest ClockworkMod and rename it to recovery.img
adb reboot bootloader
fastboot erase cache
fastboot flash recovery recovery.img
fastboot erase cache
Try to restore again
Yes erase the cache twice from fastboot.
Click to expand...
Click to collapse
nvm found it. for those who might be following this thread and also need it you can find it here
http://mirrorbrain.cyanogenmod.com/cm/recoveries/recovery-clockwork-3.0.2.4-vision.img
open1your1eyes0 said:
Oh the issue appears to be the fact that adb cannot find your device. Go into device manager and see if you see any missing drivers with the exclamation mark (should be called ADB or something like that).
Force install these drivers I have uploaded: Link
Also after you do "adb reboot bootloader" command you need to install the drivers again because it reboots into another mode.
Make sure you select "Android ADB Interface" as the driver and if it asks you that its not compatible just click Yes anyways.
Click to expand...
Click to collapse
I can't use adb because I can only get to fastboot and thus, I can only use the fastboot command. Unless I'm missing something? I do have the device in device manager with the driver loaded. I have loaded many radios through fastboot so I know the connection is working. The trick is to get an adb shell, but what state do you want the phone in? Right now I can only get to fastboot or recovery (can't do adb there either).
Sent from my HTC Vision using XDA App
Hi
I have tried going back to Sense stock after trying out GPE edition lollipop flavour.
Unfortunately somewhere along the way something has gone horrible wrong and I'm now stuck in a bootloop with a Red Triangle
My bootloader is currently locked, althougth I am S-Off. I can still access fastboot and RUU but the problem is when I try to flash standard or twrp recovery i get the following error message
From RUU
./fastboot flash recovery recov.img
target reported max download size of 1830711296 bytes
sending 'recovery' (16092 KB)...
OKAY [ 1.442s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.447s
So I currently have no os, no recovery and no way of loading a recovery back on as you can see above... am I screwed ???
Have now managed to put stock recovery back (via ruu) on and at the top of the screen it says entering recovery but never gets any further ...
Have tried again to install twrp ... no joy there what so ever
Dont' Worry I got the same problem but I fixed it!!
gsusx said:
Hi
I have tried going back to Sense stock after trying out GPE edition lollipop flavour.
Unfortunately somewhere along the way something has gone horrible wrong and I'm now stuck in a bootloop with a Red Triangle
My bootloader is currently locked, althougth I am S-Off. I can still access fastboot and RUU but the problem is when I try to flash standard or twrp recovery i get the following error message
From RUU
./fastboot flash recovery recov.img
target reported max download size of 1830711296 bytes
sending 'recovery' (16092 KB)...
OKAY [ 1.442s]
writing 'recovery'...
FAILED (remote: not allowed)
finished. total time: 1.447s
So I currently have no os, no recovery and no way of loading a recovery back on as you can see above... am I screwed ???
Click to expand...
Click to collapse
Hi
Press power,volume up and down for 90 seconds.It will enter into bootloader.
Then press recovery. If it is not going to recovery,stay in the bootloader mode. Connect to the pc.
Download this software from this website.
http://www.hasoon2000.info/
Click your phone model.
(If it is HTC ONE M8 CLICK this link http://www.hasoon2000.info/?device=One%202014%20(M8))
Unzip it.
open the software.
Unlock the bootloader by following the step shown on the software.
After,
Click any recovery but I prefer TWRP.
Install custom rom and you are good to go
Absolute legend ... thank you !!!
Posted in the general thread, but no replies.
I seem to have softbricked my phone by rooting then applying the OTA update. I've tried re-rooting, wiping cache, factory resetting, etc., and nothing seems to work. Following the steps in http://forum.xda-developers.com/zenf...d-zf2-t3127835 I can get to step 7, but when I submit any of the commands I get this:
Code:
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash fastboot droidboot.img
target reported max download size of 536870912 bytes
sending 'fastboot' (14822 KB)...
OKAY [ 0.666s]
writing 'fastboot'...
FAILED (remote: Permission denied
)
finished. total time: 0.839s
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (11882 KB)...
OKAY [ 0.545s]
writing 'recovery'...
FAILED (remote: Permission denied
)
finished. total time: 0.716s
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash boot boot.img
target reported max download size of 536870912 bytes
sending 'boot' (11868 KB)...
OKAY [ 0.522s]
writing 'boot'...
FAILED (remote: Permission denied
)
finished. total time: 0.694s
C:\Users\Elliott\Downloads\CWM_Zenfone_2_Intel>fastboot flash system system.img
target reported max download size of 536870912 bytes
erasing 'system'...
FAILED (remote: Permission denied)
finished. total time: 125.564s
It wasn't clear if it was a windows permission error or an android permission error, so I tried an admin command prompt but that didn't change anything.
Any suggestions? Thanks in advance
Bump in hopes of a solution
And another bump, any help would be greatly appreciated
I'm wondering if it has to do with having a bootloader installed being over a certain version. I had 2 Asus Zenfone 2s and I get the same error messages. I can't remember what my first ZF2 had for firmware to start, but I was a dummy and updated it all the way to 2.20.40.90 stock. Everytime I tried to write via fastboot, Permission Denied. My new ZF2 on 2.20.40.59 also has the same problem. I feel like Asus patched the ability to fastboot these files or something. Running CMD as Administrator doesn't help the situation.
bumping because I'm having the same issue, coming back to stock after having CM12.1
As easy as it sounds, the solution was just flashing the newest software from the ASUS website, using adb sideload UL-Z00A-WW-2.20.40.97-user.zip
I can't imagine why I wouldn't have done that sooner, but it fixed it. Whether that worked due to something else I did, i have no idea, but my phone is now working
I had that before but fortunately I was able to fix it.
Get a microsd, but a firmware from Asus website, make sure that it is the correct one if you have WW then download WW, download it from Asus website or it will not work.
Then put the micro sd on the phone., rename the file MOFD_UPDATE don't put zip cause it will be doubled.
Boot to bootloader then boot to recovery. Automatically the phone will restore itself.
Hi I'm currently facing a similar problem. Connected the phone via USB to a laptop and it rebooted all of a sudden and is in bootloop. It was not rooted and it was on 2.19.40.23, the phone is ZE550ML or Z008. There are 6 gigs of photos on internal memory which I want to recover.
I tried fastboot flashing preroot images and recovery boot and bootdroid images. Didn't work
I tried sideloading stock image from the Asus website. Didn't work
When I go into recovery the message - failed to map file /sdcard/MOFD_SDUPDATE comes up, last post said MOFD_UPDATE on my phone comes up different.
I also tried "adb pull / " - started pulling stuff but stops at some point.
I also tried flashing CWM and trying to mounts the internal storage as external device, didn't work.
I was also unable to mount the SD card, might have something to do with MOFD not being mapped.
Don't know if TWRP has any similar functionality but when I tried flashing any other recovery, after the process when I go into recovery itself the stock one takes over...
Any help would be greatly appreciated.
KylarBStern said:
Hi I'm currently facing a similar problem. Connected the phone via USB to a laptop and it rebooted all of a sudden and is in bootloop. It was not rooted and it was on 2.19.40.23, the phone is ZE550ML or Z008. There are 6 gigs of photos on internal memory which I want to recover.
I tried fastboot flashing preroot images and recovery boot and bootdroid images. Didn't work
I tried sideloading stock image from the Asus website. Didn't work
When I go into recovery the message - failed to map file /sdcard/MOFD_SDUPDATE comes up, last post said MOFD_UPDATE on my phone comes up different.
I also tried "adb pull / " - started pulling stuff but stops at some point.
I also tried flashing CWM and trying to mounts the internal storage as external device, didn't work.
Don't know if TWRP has any similar functionality but when I tried flashing any other recovery, after the process when I go into recovery itself the stock one takes over...
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Do what i have posted above
Sent from my ONE A2001 using Tapatalk
ebanreb37 said:
Do what i have posted above
Sent from my ONE A2001 using Tapatalk
Click to expand...
Click to collapse
I already tried it, I wrote in my post that I tried it. And it didn't work.
KylarBStern said:
I already tried it, I wrote in my post that I tried it. And it didn't work.
Click to expand...
Click to collapse
SD card MUST be FAT32 or 32gb or less. If you are using anything else it won't detect the sd card.
Cheers...
Ok it's been a while since I've tried anything with this phone and just now I did what you said, copied the firmware file which I downloaded from ASUS to a 2GB sd card formatted in fat32, rebooted to recovery phone applied the update sucessfully and restarted but I am still stuck in bootloop ? I tried every method so I asume the phone is ****ed and I should send it back for RMA ?
My M9 suddenly hang und went off... so ok i rebooted. but after boot animation off again.
i can boot into recovery and bootloader and download, but nothing else. ruu fails on pc and on sd. twrp shows system partition as 0Mb. i think something fckd up partition tables or so. i think i need a real pro to get this baby running again or at least to make it look like stock for return. if i try to flash stock recovery in download mode it says finished but still twrp on it. please please help me.
I was running Leedroid rom plus kernel.
device ist supercid and soff
nobody?? :'(
Sashtheflash said:
My M9 suddenly hang und went off... so ok i rebooted. but after boot animation off again.
i can boot into recovery and bootloader and download, but nothing else. ruu fails on pc and on sd. twrp shows system partition as 0Mb. i think something fckd up partition tables or so. i think i need a real pro to get this baby running again or at least to make it look like stock for return. if i try to flash stock recovery in download mode it says finished but still twrp on it. please please help me.
I was running Leedroid rom plus kernel.
device ist supercid and soff
Click to expand...
Click to collapse
Weird. Since you have TWRP, flashing a new ROM sounds like the best option. Maybe a full wipe beforehand? As long as you use a ROM that matches your firmware, it should work.... in theory, at least.
computerslayer said:
Weird. Since you have TWRP, flashing a new ROM sounds like the best option. Maybe a full wipe beforehand? As long as you use a ROM that matches your firmware, it should work.... in theory, at least.
Click to expand...
Click to collapse
since my phone cant find an internal memory i cant flash anything... i think partition tables are ****ed up or so. fastboot flash recovery ends in old state locking bootloader via fastboot results in bootloader still open.
Never had a problem like that and im here since the g1
Yikes. I'm afraid I don't have any further advice. Are there any threads around the M9 forums that talk about corrupted partitions?
Hello, please see my answer on pm regarding help.
Until then, please boot into TWRP and connect to adb and run cat /proc/emmc to get a listing of partitions and their sizes.
Then head over to my firmware thread, find the link to my partition table document and compare with yours. Output should be 100% identical, if not, you're right about your suspicion.
I rather assume you've got a permission / security issue which renders some partitions inaccessible. I doubt they're actually broken.
Please also make sure you always leave precise and concise info on what steps you tried and what the outcome was. This will help keep this short and helpful for others too.
Sneakyghost said:
Hello, please see my answer on pm regarding help.
Until then, please boot into TWRP and connect to adb and run cat /proc/emmc to get a listing of partitions and their sizes.
Then head over to my firmware thread, find the link to my partition table document and compare with yours. Output should be 100% identical, if not, you're right about your suspicion.
I rather assume you've got a permission / security issue which renders some partitions inaccessible. I doubt they're actually broken.
Please also make sure you always leave precise and concise info on what steps you tried and what the outcome was. This will help keep this short and helpful for others too.
Click to expand...
Click to collapse
unfortunately my device wont let me boot in recovery again... now it states: Failed to boot to recovery mode Press Volume up to back to menu.
seems my tries to flash single parts of firmware messed this up
Ok please keep it safe now. Don't do anything else to it for the time being. I can try to connect to it via team viewer tomorrow if you allow me into your machine.
What is your time zone? Will you be having time tomorrow afternoon/evening my time? I'm located in GMT +1 (Germany).
Sneakyghost said:
Ok please keep it safe now. Don't do anything else to it for the time being. I can try to connect to it via team viewer tomorrow if you allow me into your machine.
What is your time zone? Will you be having time tomorrow afternoon/evening my time? I'm located in GMT +1 (Germany).
Click to expand...
Click to collapse
Im from Germany, too ( Heilbronn) Ok i leave my fingers from it until tomorrow. Thank you a lot for trying !!!
im have also m9 dead after flash now my phone read on pc qload any one have idea to rework my phone again ?
logy122 said:
im have also m9 dead after flash now my phone read on pc qload any one have idea to rework my phone again ?
Click to expand...
Click to collapse
Yeah yours is a real brick while the OP's phone is more likely damaged NAND. Two very different things.
QHUSB on your PC when you connect it means you've managed to actually brick it.
For this, you'll need to open the phone and connect it to some special tool like the riff jtag box and rewrite the corrupted bootloader.
@Tecardo can do this for you in Germany. I'm not sure where you are but Tec has all the equipment and skills needed to fix that.
Sneakyghost said:
Yeah yours is a real brick while the OP's phone is more likely damaged NAND. Two very different things.
QHUSB on your PC when you connect it means you've managed to actually brick it.
For this, you'll need to open the phone and connect it to some special tool like the riff jtag box and rewrite the corrupted bootloader.
@Tecardo can do this for you in Germany. I'm not sure where you are but Tec has all the equipment and skills needed to fix that.
Click to expand...
Click to collapse
im also can open phone and replace emmc |> im only need boot file to write to phone and back to work
Yes you need to rewrite aboot. That's only possible with a jtag box and maybe, maybe, under Linux because the qhusb connection has no stable functioning driver on Windows. It's almost impossible to flash anything via qhusb on Windows. It could work in Linux though. I remember having had a half-stable connection to my HTC One S this way, back in 2012. I managed to rewrite the hboot back then. But afaik that never worked on the M7,8,9...
Gesendet von meinem HTC 10 mit Tapatalk
I don't want to start a new thread. I have a similar problem. I have an HTC one M9 S-OFF Unlocked. I returned my phone to stock after doing a nandrod backup. I realised I had a sms backup in the nandroid that I need so I thought I would install twrp and do a restore the nandroid. I installed twrp and afterward it bootlooped when I went to recovery mode. It goes from white HTC screen to black screen an back. I tried to go to download mode to do a fresh install but it bootloops there as well. It also bootloops if I try to turn it off with it connected to power. I have tried installing different version of twrp but I get the same problem. If I install a stock recovery it says failed to boot to recovery mode and stays on the white HTC screen. Does anyone know of a solution
Best way is to flash a RUU.
after, for your nandroid backup, flash twrp (same version you have made the backup) and don't accept supersu at the end if proposed...
bzhmobile said:
Best way is to flash a RUU.
after, for your nandroid backup, flash twrp (same version you have made the backup) and don't accept supersu at the end if proposed...
Click to expand...
Click to collapse
I get the following when I fastboot flash rom "fastboot flash rom /Users/.../Android/OPJAIMG.zip
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1013258477 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 474585325 is not a multiple of the block size 4096
sending sparse 'rom' (521267 KB)...
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
OKAY [ 15.122s]
writing 'rom'...
FAILED (remote: partition table doesn't exist)
finished. total time: 15.140s"
Sneakyghost said:
Yes you need to rewrite aboot. That's only possible with a jtag box and maybe, maybe, under Linux because the qhusb connection has no stable functioning driver on Windows. It's almost impossible to flash anything via qhusb on Windows. It could work in Linux though. I remember having had a half-stable connection to my HTC One S this way, back in 2012. I managed to rewrite the hboot back then. But afaik that never worked on the M7,8,9...
Click to expand...
Click to collapse
It was also possible w/Linux on the One XL. I too have never heard of it working on the M7 and later phones, though I've seen the odd post here claiming it is possible. No examples of anyone having done it, however.
copy the OPJAIMG.zip on the root of your Sdcard and reboot in the booloader and follow the instructions (vol +)...
or
with htc_fastboot
download Htc_fastboot.exe et copy it in your fastboot folder with the OPJAIMG.zip
fastboot oem lock , not needed if you're S-OFF
fastboot oem rebootRUU , to reboot
htc_fastboot flash zip OPJAIMG.zip
fastboot reboot
don't forget to unlock again youre device
djkfree said:
I get the following when I fastboot flash rom "fastboot flash rom /Users/.../Android/OPJAIMG.zip
target reported max download size of 536870912 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1013258477 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 474585325 is not a multiple of the block size 4096
sending sparse 'rom' (521267 KB)...
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1546750189 is not a multiple of the block size 4096
OKAY [ 15.122s]
writing 'rom'...
FAILED (remote: partition table doesn't exist)
finished. total time: 15.140s"
Click to expand...
Click to collapse
bzhmobile said:
copy the OPJAIMG.zip on the root of your Sdcard and reboot in the booloader and follow the instructions (vol +)...
or
with htc_fastboot
download Htc_fastboot.exe et copy it in your fastboot folder with the OPJAIMG.zip
fastboot oem lock , not needed if you're S-OFF
fastboot oem rebootRUU , to reboot
htc_fastboot flash zip OPJAIMG.zip
fastboot reboot
don't forget to unlock again youre device
Click to expand...
Click to collapse
I get bootloop when I fastboot oem rebootRUU
So,
go to download mod (option in the bootloader ) and apply the fastboot command
htc_fastboot flash zip OPJAIMG.zip
Hello! I'm new to this forum but love the assist people lend others.
Now ofcourse I'm here because i'm struggling,
i cant get my phone to load a TWRP recovery..
i've been following the instruction of this vid: /watch?v=WuHFcGvUjwA and everything went as planned until 20:00 min of the vid, i cannot load or flash the recovery..
I've checked every single file there is to download for the HTC one M8 from the official TWRP website
it gives an error on the 1/2 recovery saying :
target reported max download size of 16777216 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 10479616 is not a multiple of th
e block size 4096
sending sparse 'recovery' 1/2 (15836 KB)...
error: write_sparse_skip_chunk: don't care size 10479616 is not a multiple of th
e block size 4096
error: write_sparse_skip_chunk: don't care size 10479616 is not a multiple of th
e block size 4096
OKAY [ 1.639s]
writing 'recovery' 1/2...
FAILED (remote: image error! (BootMagic check fail))
finished. total time: 1.643s
now like i said - ive tried the newest version all the way down to the oldest one.
Although the versions 2.7.0.1 and 0.2 DO load or flash, as soon as i hit the recovery option in my bootloader is gets stuck on the HTC logo.
What i see in bootloader menu:
***UNLOCKED*** (since i've followed those steps unlocking my bootloader menu
S-on
Hboot 3.19.0.0000
[email protected]
OS-2.10.401.1
I also read something about using an SD card since my phone doesnt have enough room for it to flash the image, so i did buy a 32gb one, formatted it to be part of the phone and tried it all again, still no effect.
please see the vid, or skip through it to know my proccess and know where i am at atm.
Thanks you very very much in advance! every help is appreciated
Are you sure your device is M8 ?
Your details don't look like one.
ckpv5 said:
Are you sure your device is M8 ?
Your details don't look like one.
Click to expand...
Click to collapse
Yes, well it's a M8s.
but many downloads said it was for all types of m8
All type of M8 means applicable for GSM, Sprint & Verizon.
M8s is not regular M8, it's totally different device.
Check M8s section for your device version. One of the thread has TWRP for M8s.
http://forum.xda-developers.com/htc-one-m8/one-m8s-general
Any question, ask in that section.
ckpv5 said:
All type of M8 means applicable for GSM, Sprint & Verizon.
M8s is not regular M8, it's totally different device.
Check M8s section for your device version. One of the thread has TWRP for M8s.
http://forum.xda-developers.com/htc-one-m8/one-m8s-general
Any question, ask in that section.
Click to expand...
Click to collapse
Okay, i realise now that im in the wrong section of the forums - but if you could lend me some help it would be highly appreciated.
I now did the HTC_fastboot flash recovery twrp-3.0.2-0-m8.img and it loaded just fine, giving me the message:
sending 'recovery' (20046 KB)... OKAY
writing 'recovery'... OKAY
Execution time is 3(s)
but when i go to bootloader and select recovery it still freezes at the HTC powered by.. logo
Any suggestions pls?
twrp-3.0.2-0-m8.img is for regular M8 only, won't work for your device.
You need something that read twrp-x.x.x.x-m8s-qlul.img
I think you can still use twrp-recovery-2.8.6.0-m8s-qlul.img to root ... available and all details are here : http://forum.xda-developers.com/htc-one-m8/one-m8s-general/make-custom-recovery-htc-one-m8s-t3114245
Important : When using this recovery, do not accept root offer by the TWRP .. you need install the latest SuperSU 2.76 because yours is Marshmallow.
http://download.chainfire.eu/supersu-stable
You can ask there whether they have any newer TWRP version for M8s.
I can't help much as I don't have this device .. sorry.
ckpv5 said:
twrp-3.0.2-0-m8.img is for regular M8 only, won't work for your device.
You need something that read twrp-x.x.x.x-m8s-qlul.img
I think you can still use twrp-recovery-2.8.6.0-m8s-qlul.img to root ... available and all details are here : http://forum.xda-developers.com/htc-one-m8/one-m8s-general/make-custom-recovery-htc-one-m8s-t3114245
Important : When using this recovery, do not accept root offer by the TWRP .. you need install the latest SuperSU 2.76 because yours is Marshmallow.
http://download.chainfire.eu/supersu-stable
You can ask there whether they have any newer TWRP version for M8s.
I can't help much as I don't have this device .. sorry.
Click to expand...
Click to collapse
Fixed it and got it all running now. thanks for the assist about needing the m8s twrp file, got that, used the HTC_fastboot flash recovery <recovery file name>.img and got it to work