Related
so I tried to Root my Dream and choose after a number of failed attempts I have decided to just give up so I want to wipe and restore my phone's OS the factory but when I try though the settings menu the phone restarts then just sits on the "Rodgers" logo for ever so is there anyway to fix that?
Don't give up so soon
I definitely recommend rooting. The rogers firmware sucks by default imo. I did not like my phone at all until I rooted.
Check this guide by HyeProfile, I just used it on a new rogers dream and it worked 100%:
http://forum.xda-developers.com/showthread.php?p=4280573#post4280573
If you really don't want to root, you can follow the steps to try flashing (using the same instructions he gives in that post) with the official rogers radio.img and recovery.img here: http://www.stevebirstok.com/android/losemyroot.zip
well I hate how slow my phone feels so I'm going in for the root again thanks for the push to try again.
ok ran into an issue:
Installing from sdcard...
Finding update package...
E:Can't mount /dev/block/mmcblk0p1 (No such file of directory)
E:Can't mount SDCARD:update.zip
Installation aborted
when trying to apply update.zip
Loading001 said:
ok ran into an issue:
Installing from sdcard...
Finding update package...
E:Can't mount /dev/block/mmcblk0p1 (No such file of directory)
E:Can't mount SDCARD:update.zip
Installation aborted
when trying to apply update.zip
Click to expand...
Click to collapse
that means it can't see your sdcard.
see if dropping into the recovery console(alt+x) and typing
Code:
mount /sdcard
recovery
see if that helps anything since that command will mount your sdcard which it appears to be failing to read.
when I try enter the console all the options are removed form the screen then nothing happens all I see is the yellow text.
The yellow text I'm talking about is the error message I posted.
if you are trying to unroot it, use the same rc package that you use to downgrade it in the bootloader (camera and power) and run the .nbh there
Loading001 said:
ok ran into an issue:
Installing from sdcard...
Finding update package...
E:Can't mount /dev/block/mmcblk0p1 (No such file of directory)
E:Can't mount SDCARD:update.zip
Installation aborted
when trying to apply update.zip
Click to expand...
Click to collapse
Are you sure your sdcard is formatted to FAT32?
I'm going o try that when I get home
ok so it's weird.
E:Multiple firmware images
E:can't store hboot images
E:failure at line 1
write_hboot_image PACKAGE:hboot.img
install aborted
ok so now it just sits on the "Rogers" logo and wont enter any mode (camara+power)
edit: looks like that means I biked the thing hope they will replace it (i'll just blame it on their firmware update thing)
edit2: calling rogers to try get a replacement
will it it read an .nbh in the bootloader?
I don't know how can I test that or see if it will?
I was refering to the dreaimg.nbh from either rc29 or rc7 that you use to downgrade your phone in order to root it, that use the bootloader camera + power
no it wont enter any mode at all just sits on the rogers logo so a new phone should show up in the next 3 to 5 days
this kinda scares me off from trying again but I want to so I might.
got a all new phone and it still wont mount the Sd card like last time
ok so i helped some one root their rogers phone last night. are you trying to flash the radio, or have you followed all of the fastboot commands in the "rogers heres your real root" thread? the guy i was helping couldn't flash the radio but we got it with the fastboot commands
no I'm past loading recovery.img with fastboot and I'm trying to apply the update.zip
thats very odd. so you did all the fastboot commands and still can't get it to work?
is it any rom you try to flash?
well I was following the guide in one of the first posts
Long story short,
Purchased a Tmobile HTC One, Planned on taking it over to Straight Talk.
I have not asked any questions because I can usually figure this out.
Facts:
Unlocked using All In One
TWRP recovery
Issue:
Keep rebooting once it gets to the HTC One screen with Beats Audio
I am about 22 hours into this and very frustrated, it seems as though I do not have an O.S.
Cannot mount E:
rafalk86 said:
Long story short,
Purchased a Tmobile HTC One, Planned on taking it over to Straight Talk.
I have not asked any questions because I can usually figure this out.
Facts:
Unlocked using All In One
TWRP recovery
Issue:
Keep rebooting once it gets to the HTC One screen with Beats Audio
I am about 22 hours into this and very frustrated, it seems as though I do not have an O.S.
Cannot mount E:
Click to expand...
Click to collapse
Use the ADB Sideload option(follow the directions carefully) in the All-in-One Toolkit to load a ROM.
unremarked said:
Use the ADB Sideload option(follow the directions carefully) in the All-in-One Toolkit to load a ROM.
Click to expand...
Click to collapse
I have tried a couple of times (following directions closely - have done this before on a inspire) and keep getting
"E:unable to mount '/data'" on the phone side & "error: closed"
rafalk86 said:
I have tried a couple of times (following directions closely - have done this before on a inspire) and keep getting
"E:unable to mount '/data'" on the phone side & "error: closed"
Click to expand...
Click to collapse
Hmm. Have you attempted to format data while in TWRP recovery? Also a few more details please--once you had unlocked the bootloader and installed TWRP, did you attempt to install a ROM from that point or boot into stock? If it's the latter, have you attempted to fastboot flash a boot.img from a stock ROM/NAND backup?
rafalk86 said:
I have tried a couple of times (following directions closely - have done this before on a inspire) and keep getting
"E:unable to mount '/data'" on the phone side & "error: closed"
Click to expand...
Click to collapse
I have always had better luck with CWM clockworkmod recovery than TWRP for these kind of situations. So you might want to use the all in one and put Clockwork on. Also when sideloading a rom make sure to rename the rom something nice and short like rom.zip no spaces no numbers just simple and short or it will fail.
unremarked said:
Hmm. Have you attempted to format data while in TWRP recovery? Also a few more details please--once you had unlocked the bootloader and installed TWRP, did you attempt to install a ROM from that point or boot into stock? If it's the latter, have you attempted to fastboot flash a boot.img from a stock ROM/NAND backup?
Click to expand...
Click to collapse
1. Have NOT tried to format data
2. Originally tried to install cm touch, which at that time seemed like it didnt work (could not boot into rom) so I tried to install TWRP for some reason
3. I have attempted to boot stock rom, but always gets hung up on "beats audio" audio screen
unremarked said:
Hmm. Have you attempted to format data while in TWRP recovery? Also a few more details please--once you had unlocked the bootloader and installed TWRP, did you attempt to install a ROM from that point or boot into stock? If it's the latter, have you attempted to fastboot flash a boot.img from a stock ROM/NAND backup?
Click to expand...
Click to collapse
Wow, saved my ass. I formatted /data and now I can finally boot into CM after a fresh ROM install.
Thanks
nullkill said:
I have always had better luck with CWM clockworkmod recovery than TWRP for these kind of situations. So you might want to use the all in one and put Clockwork on. Also when sideloading a rom make sure to rename the rom something nice and short like rom.zip no spaces no numbers just simple and short or it will fail.
Click to expand...
Click to collapse
1. Loaded ClockworkMod Recovery v6.0.3.1
2. Rebooted to recovery
Result:
Loaded CM Recovery and at the bottom it says:
"E: Cant mount /cache/recovery/command
E: Cant mount /cache/recovery/log
E: Cant open/cache/recovery/log
E: Cant mount /cache/recovery/last_log
E: Cant open/cache/recovery/last_log"
Q: Should I try formatting the drive
nullkill said:
I have always had better luck with CWM clockworkmod recovery than TWRP for these kind of situations. So you might want to use the all in one and put Clockwork on. Also when sideloading a rom make sure to rename the rom something nice and short like rom.zip no spaces no numbers just simple and short or it will fail.
Click to expand...
Click to collapse
Side loaded the rom through cwm recovery.
"sideload started...
failed to open driver control: No such file or directory
Restarting adbd...
failed to open driver control: No such file or directory
E: Can't mount /cache/recovery/last_install
E: failed to open last_install: Invalid argument
Finding update package...
Opening update package...
Installing update...
E: Cant mount /cache/recovery/log
E: Cant open/cache/recovery/log
E: Cant mount /cache/recovery/last_log
E: Cant open/cache/recovery/last_log"
UPDATE: After I rebooted it just cycles for the CyanogenMod boot then restarts etc etc...
rafalk86 said:
Side loaded the rom through cwm recovery.
"sideload started...
failed to open driver control: No such file or directory
Restarting adbd...
failed to open driver control: No such file or directory
E: Can't mount /cache/recovery/last_install
E: failed to open last_install: Invalid argument
Finding update package...
Opening update package...
Installing update...
E: Cant mount /cache/recovery/log
E: Cant open/cache/recovery/log
E: Cant mount /cache/recovery/last_log
E: Cant open/cache/recovery/last_log"
UPDATE: After I rebooted it just cycles for the CyanogenMod boot then restarts etc etc...
Click to expand...
Click to collapse
Two things here:
1) Clearing Cache fixes the cache issue you see...
2) To fix the boot loop, you need to `Format /data and /data/media` under `Mounts and Storage`.
That should fix you up.... side loading wont fix a bad /data partition.
kenyu73 said:
Two things here:
1) Clearing Cache fixes the cache issue you see...
2) To fix the boot loop, you need to `Format /data and /data/media` under `Mounts and Storage`.
That should fix you up.... side loading wont fix a bad /data partition.
Click to expand...
Click to collapse
1. Cleared cache - fixed
2. Both datas formatted
Q: Its been a long 24hrs, now I load rom, correct?
rafalk86 said:
1. Cleared cache - fixed
2. Both datas formated
Q: Its been a long 24hrs, now I load rom, correct?
Click to expand...
Click to collapse
It sounds like you have a ROM loaded if its cycling at the BeatsAudio screen. Yes, you can do the ROM now. Make sure you do a factory reset before installing the ROM (or after I suppose)
rafalk86 said:
Long story short,
Purchased a Tmobile HTC One, Planned on taking it over to Straight Talk.
I have not asked any questions because I can usually figure this out.
Facts:
Unlocked using All In One
TWRP recovery
Issue:
Keep rebooting once it gets to the HTC One screen with Beats Audio
I am about 22 hours into this and very frustrated, it seems as though I do not have an O.S.
Cannot mount E:
Click to expand...
Click to collapse
Are you using Mac OSX? What is the format of the external_sd card? Is it formatted FAT, FAT32, or EX_FAT?
Clockworkmod does not support EX_FAT, so you must format it to FAT in order for it to mount. OSX can't format FAT32, so you must format FAT.
I'm having issues flashing a custom recovery. After booting into the Clockwork Mod recovery (just flashed) I get the error codes:
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/command
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I also only have 118MB of free space on the SD Card (seen through recovery).
So I'm trying to download the stock recovery from
http://forum.xda-developers.com/showthread.php?t=2158763
so that I can flash it to start all over to see if it helps, but ESET is coming up with it as infected with a trojan. I'd like to flash it but I'm not sure if I can trust it...
Any help?
That link downloads a rar archive that contains the stock recovery image plus other stuff. My virus protection also picked it up, but I downloaded and check it out and even had another user flash that recovery image so I am pretty sure the download is not infected.
Alright, I'm going to flash it.
Any ideas on the error codes?
Looks like you got fungi on your recovery. DON'T LET IT GET EXPOSED TO WATER!
lesson learnt.
jags_the1 said:
Looks like you got fungi on your recovery. DON'T LET IT GET EXPOSED TO WATER!
lesson learnt.
Click to expand...
Click to collapse
Well, I'm not going to pretend that I don't have any clue what that meant
Myrloc said:
Alright, I'm going to flash it.
Any ideas on the error codes?
Click to expand...
Click to collapse
Maybe fastboot erase cache. Perhaps reflash and try TWRP recovery.
Any idea which recovery to flash. The file I downloaded came with a bunch to choose from.
Oh yeah, I remember now. I didn't use those because I thought they were labeled weird. Here is a zip that contains the stock recovery.img :
https://dl.dropboxusercontent.com/u/36946918/ResetRecovery.zip
I would just try to reflash a custom recovery.
Go to this thread and get TWRP. Rename the file to twrp.img and place it in the same folder as your fastboot. Your phone should still be in fastboot, if not, get there.
Type: fastboot erase cache
Type: fastboot flash recovery twrp.img
since acipen
I can't flash any other recoveries...
When I try to flash another one, the one with go to the "Entering recovery" screen for several seconds and then turn off.
Myrloc said:
I can't flash any other recoveries...
When I try to flash another one, the one with go to the "Entering recovery" screen for several seconds and then turn off.
Click to expand...
Click to collapse
I sometimes get those error messages when I go from Twrp to Cwm, but after I do a backup or flash something it goes away the next time I boot into recovery.
Sent from my HTC One using xda premium
The other issue is that when I'm backing up in CW, it says:
Backing up system..
Can't mount /system!
Is this a problem or should I ignore it?
I have CW flashed, but now I can't start my phone. Everything's been flashed (data/factory reset, etc.). I don't think I wiped the system, but now I'm not sure. Any help guys? This kind of blows.
Hi
I was able to s-off, install a recovery and root my device OK.
I installed TWRP as part of that process and then installed Clockworkmod while I was testing out Cyanogenmod.
I want to go back to TWRP (or at least Clockworkmod touch) but my phone will only boot into Clockworkmod (non-touch)
Things I've tried:
Flashed TWRP from fastboot
fastboot erase cache
But every time the phone only boots into Clockworkmod 5.x.x.x
The clockworkmod app tells me I have TWRP and Clockworkmod installed already, but same problem when I try to reboot into TWRP from there.
This log comes up in Clockworkmod. Maybe it's relevant:
E: Can't mount /cache/recovery/command
E: Can't mount /cache/recovery/log
E: Can't open /cache/recovery/log
E: Can't mount /cache/recovery/last_log
E: Can't open /cache/recovery/last_log
Anyone kind enough to help I'll be very grateful
Thanks
Flash TWRP, reboot into the phone. Go back to fastboot, flash TWRP again, and check. A different combination may work. It may take a few tries to get it going.
Fixed
SaHiLzZ said:
Flash TWRP, reboot into the phone. Go back to fastboot, flash TWRP again, and check. A different combination may work. It may take a few tries to get it going.
Click to expand...
Click to collapse
Thanks very much. Got it fixed by basically doing what you suggested.
http://forum.xda-developers.com/showthread.php?t=2173863
Awesome. Hit my thanks button and edit the OP to mark it [SOLVED]
Hello,
premise that I've already seen this and this, I am not able to install su binaries because of the problem described in the first link.
This is the first messages I see on recovery:
ClockworkMod Recovery v6.0.4.3
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
The only way I have to install a .zip file is using sideload but even installing SuperSU or Superuser, in both cases I am not able to get su binaries installed. I've followed all the guides mentioned in the FAQs (i.e. https://www.youtube.com/watch?v=T7GCnbjO1zw and this) but I guess something wasn't gone fine because of the mount problems above.
Could somebody help me please? The topics I've found here didn't help so far.
fbcyborg said:
Hello,
premise that I've already seen this and this, I am not able to install su binaries because of the problem described in the first link.
This is the first messages I see on recovery:
ClockworkMod Recovery v6.0.4.3
E:Can't mount /cache/recovery/command
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
The only way I have to install a .zip file is using sideload but even installing SuperSU or Superuser, in both cases I am not able to get su binaries installed. I've followed all the guides mentioned in the FAQs (i.e. https://www.youtube.com/watch?v=T7GCnbjO1zw and this) but I guess something wasn't gone fine because of the mount problems above.
Could somebody help me please? The topics I've found here didn't help so far.
Click to expand...
Click to collapse
Uhh.. is your variant the Sprint variant (m7wls)? Or the international variant (m7_u or m7_ul)?
StormyNight said:
Uhh.. is your variant the Sprint variant (m7wls)? Or the international variant (m7_u or m7_ul)?
Click to expand...
Click to collapse
How can I check that?
As far as I understand mine should be the UL variant (having both GSM & LTE radio).
fbcyborg said:
How can I check that?
As far as I understand mine should be the UL variant (having both GSM & LTE radio).
Click to expand...
Click to collapse
Go into the boot loader by pressing POWER+VOL DOWN. It should say the device name at the very top.
StormyNight said:
Go into the boot loader by pressing POWER+VOL DOWN. It should say the device name at the very top.
Click to expand...
Click to collapse
Thanks,
this is what I see in the boot loader:
M7_UL PVT SHIP S-ON RH
HBOOT-1.57.0000
Maybe the fact it's still S-ON is also a problem isn't it?
EDIT: I've also found this. Do I have to install this recovery or this one instead?
I reply to myself!
I've finally solved the problem both with su binaries and mount messages installing the Philz Touch Recovery I've mentioned two rows above.