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
Related
Title.
Everytime i try applying update.zip this error message appears.
Tried almost everything possible but can't find a solution for this problem.
How can i get into fastboot-mode?
bump
I also have this problem.
About a month ago Milestone was upgraded through cable to official Froyo.
Today, GOT_RTEU_2_2_1FULL.sbf was flashed with RSD Lite 4.9, using this guide
http://forum.xda-developers.com/showthread.php?t=698059
and
http://forum.xda-developers.com/showthread.php?t=983516
After going to recovery (x + power, vol up + camera) and trying to update previously copied Open Recovery 3.3, following problem occurs:
Code:
E:Can't open /cache/recovery/command
E:Can't mount /dev/block/mmcblk0p1 (or else)
Screenshot: http://dl.dropbox.com/u/20342824/2011-06-23 14.09.06.jpg
I've read that I can have my recovery reverted to non-vulnerable because of having flashed official OTA (and I can't undo this step)
Could this be the cause for such error message?
This is my wife's Moto, we really need to put a decent FW on it, stock Froyo is very disappointing
Hi.
I'm trying to fix my boss' tab, SPH-P100 (Sprint).
I have tried all kinds of things and nearly bricked it (got the phone ! computer symbol, but it still accepted uploads, so I was OK).
Here's the issues:
- Continuous loop of Samsung logo on boot
- From Recovery screen, I performed a factory reset, but it didn't help - same logo loop
- In the Recovery screen, I get errors similar to the ones quoted above:
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
I read all kinds of posts about simply flashing the stock ROM, and I found the ROM that was mentioned multiple times in these forums to be the right one for this tab (it did change the first boot animation, though...). The ROM I used is tab_sprint_noModem_20101226.tar inside Tab_Stock_-_No_Modem.rar.
I tried:
-ODIN with the stock ROM posted in this thread. It works, but it doesn't fix anything. I tried with and without the PIT file (one thread specifically warned NOT to use the PIT file, but in the end I tried it anyway - I think I did NOT hit Repartition, so it probably didn't do anything...).
-Heimdall doesn't seem to work at all for me. I found version 1.3.1, and the instructions in post 21 of the thread linked above don't seem to apply to this version. I finally figured out that I need to be in the FLASH tab, but I can't add files without the PIT file, it won't let me add the zImage file for recovery (or at least complains that there's no .bin file ending), and when I checked "Repartition", I got the error:
ERROR: Partition corresponding to -21 argument could not be located
Ending session...
Yes, I installed the drivers that came with Heimdall.
-Following other posts with very similar errors, I formatted the SD card in Windows using FAT32 - no change.
-I looked into another thread talking about parted, but I don't have root on that device, and I'm not sure what my boss would think about me rooting his pad... I also don't know enough to figure out which rooted ROMs would go with it - I'm scared enough with the "official stock rom" I'm using
I'm fairly tech savvy, know a little about Linux and have used adb to root my own phone, but otherwise a lot of the things I read here only make enough sense to me to follow the instructions and not get lost.
Maybe there's a different version of Heimdall that I should be using, or maybe I did something else wrong, but I'm sure I followed the instructions here.
Any help would be greatly appreciated!
Thanks in advance!
(PS, I originally posted this at the end of the thread I mentioned here but did not get an answer - I'm sorry, I had not read the post about not asking questions in that forum, even if it was attached to another post where similar questions were asked and answered, so I'm moving this post here instead.)
Update:
Found a different Rom in this thread - same situation:
I can flash it, but nothing changes, and I still get the error message I showed. The main change is that this ROM is the first I have found that has the same Sprint boot animation that the tab originally had.
The new information is that once it resets after flashing, it briefly shows a few messages - one said that if failed to wipe the cache, and I think the others showed the same error about /dev/block/mmcblk0p1 but I can't be sure (tried to get video of it, but I was too slow, and it's blurred - I'll try again later to get the exact error messages).
Update 2:
Found yet another ROM in this thread and tried it, and this one doesn't seem to work at all with this tab (tried with and without pit/re-partitioning) - the boot fails and immediately boots into Recovery by itself and shows the following:
-- bootmode=7 from cmdline
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/command
-- Wiping data...
Formatting /data...
E:format_volume: rfs format failed on /dev/block/mmcblk0p2
Formatting /dbdata...
Formatting/cache...
E:format_volume: rfs format failed on /dev/block/mmcblk0p1
Data wipe failed.
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/recovery_kernel_log
E:copy_kernel_file :: Can't open /cache/recovery/recovery_kernel_log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
E:failed to mount /cache (No such file or directory)
Click to expand...
Click to collapse
Will try to flash the other ROM again to try and get a precise look at its error message...
UPDATE 3:
Flashed the first ROM again - no error message, just the same Samsung logo cycle that freezes briefly and then starts over.
Flashed the second ROM again (the one that has the correct Spring animation), and this time I got the error messages on video.
-- Wiping DATA:...
Formatting DATA:...
DATA: wipe failed.
-- Wiping CACHE:...
Formatting CACHE:...
CACHE: wipe failed.
--Wiping DBDATA:...
Formatting DBDATA:...
E:Can't mount /dev/block/mmcblk0p2
(No such file or directory)
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
E:Can't mount CACHE:log/recovery.log
E:Can't open CACHE:log/recovery.log
E:Can't mount /dev/block/mmcblk0p1
(No such file or directory)
Rebooting...
Click to expand...
Click to collapse
Still hoping for ideas, but I think I'm at the end of what I can try...
Is it likely or possible that the internal memory got damaged?
I don't know exactly what my boss did to the tab, but he mentioned something about "the cold" meaning Minnesota winter cold - we had about 12 degrees last week, so maybe that's the cause...
Have you found and tried the EA24 stock flash tool?
Sent from my SPH-P100 using xda premium and ICS
Thanks for the reply!
If that's this file:
Sprint Galaxy Tab EA24 Flasher.zip
Then I have tried the ROM in it with Odin, but not the actual tool that came with it.
I'll see if I can get my boss to give me another shot with it (unless he's already returned it - I've had it for a few days already...).
Thanks!
has anyone found a solution to this? I am having the exact same issue...
Not sure why or how it happened everything was fine one day and next day wont go past logo and keeps rebooting.
Same problem here
My P100 started this problem last night, which was the first time it's been turned in in several days. It's fully stock, never had any rooting or flashing performed on it.
Booting into recovery mode shows failed mounts on everything it tries to do, and all the options for recovery also fail - except for "reboot system now", which does reboot it, but then it just sits on the pulsing Samsung logo endlessly. And I do mean endlessly, I let it go four hours last night, after which the battery ran out. Plugged it in after that, and it's right back to the same thing.
Every other thread I've found with this problem listed it as an after-effect of having attempted to flash a new ROM, but that is not the case with mine...
Hoping someone has the answer...
Thanks!
-mike
Same exact symptoms, and when I tried CM9 or other ICS ROMs this errors lead into the dreaded "Encryption Unsuccessful" bug.
At this point I'm just trying to get the device to boot consistently.
ChrisCTX said:
Same exact symptoms, and when I tried CM9 or other ICS ROMs this errors lead into the dreaded "Encryption Unsuccessful" bug.
At this point I'm just trying to get the device to boot consistently.
Click to expand...
Click to collapse
Did you try to do full restock (include bootloader and repartition)?
or you can try CM9 again with a fixed kernel by cdesai or jt. look at this conversation:
http://forum.xda-developers.com/showpost.php?p=28584567&postcount=2320
yappoe said:
Did you try to do full restock (include bootloader and repartition)?
or you can try CM9 again with a fixed kernel by cdesai or jt. look at this conversation:
http://forum.xda-developers.com/showpost.php?p=28584567&postcount=2320
Click to expand...
Click to collapse
I'm on it ASAP, thanks a ton for that
Edit: If possible mind giving a link to that specific kernel (or flashable .zip with it)?
Do you have this on your screen:
http://forum.xda-developers.com/attachment.php?attachmentid=1193979&d=1342124106
If so, we're in the same boat
Btw, I used a full repartition and boot following this thread:
http://forum.xda-developers.com/showpost.php?p=17817287&postcount=2
and same error occurs.
Bump in hopes of solving this issue.
My tab is basically bricked. I have this same issue after putting CM9 on it. Those errors consistently pop up. and thats it.
I guess its a paper weight now.
you may try flashing pit file and stock rom with micro SD inserted during flashing. that's what I did to my Samsung GT-I9003 when it failed to read the internal SD. At first, the camera may not work. Just root the device after flashing pit/ROM and do SD Swap Mod (external SD as internal SD).
Not sure if it's gonna work with Galaxy Tab. Give it a try. Hope this helps.
Hey guys, it appears JimRich is working on a solution for the CDMA (verizon and sprint) versions of thsi device, keep checking and be sure to let him know there are other people with this problem. http://forum.xda-developers.com/showthread.php?t=1789728
I am getting this error when i goto recovery mode and select "Apply sdcard:update.zip"
i copied the update.zip file in SDcard but i show this error:
e:can't mount /dav/block/mmcblk0p1
(No such file or directory)
E: Can't mount SDCARD: update.zip
installation aborted.
Please help me which this.
i am rooting my Samsung GTI9000M..
Previously i used many roms but phone keeps on rebooting, finally i applied this procedure: http://androidforums.com/vibrant-su...6959-samsung-vibrant-bricked.html#post1664065
now it come to recovery mode plz tell me what should i do now!!
Step 1: You post this in the correct forum for your device. This is for the SGH-I897.
http://forum.xda-developers.com/forumdisplay.php?f=656
Step 2: Stop! Go back to Step 1.
Step 3: Why are you even reading step 3?
Step 4: Nevermind. I give up.
tnx for help!
bt87 said:
tnx for help!
Click to expand...
Click to collapse
I'm glad you could see the humor! Have a great day and good luck on your problem.
bt87 said:
I am getting this error when i goto recovery mode and select "Apply sdcard:update.zip"
i copied the update.zip file in SDcard but i show this error:
e:can't mount /dav/block/mmcblk0p1
(No such file or directory)
E: Can't mount SDCARD: update.zip
installation aborted.
Please help me which this.
i am rooting my Samsung GTI9000M..
Previously i used many roms but phone keeps on rebooting, finally i applied this procedure: http://androidforums.com/vibrant-su...6959-samsung-vibrant-bricked.html#post1664065
now it come to recovery mode plz tell me what should i do now!!
Click to expand...
Click to collapse
when you boot to recovery mode do recovery mode show some message like can't mount... can't mount.... if yes then try to flash the recovery again
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.