Ok, So i've been having problems with Overclocking my Nook Color
First of all Thanks for your help:
I have downloaded the Kernels I want to try out, I've done this process several times but when I overclock my Nook Color will not Charge. Here is the error messages I get when I go through the process, it installs the Kernel, but when I plug to charge it won't, but when i go back to stock it works, so I'm wondering if the following is the issue:
Wiping cache...
Formatting /cache...
Cache wipe complete.
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
Then I wipe the Dalvik Cache and it freezes, so I reboot holding N to enter into Recovery Mode and install Kernel but it won't work. Any help is appreciated.
try clearing the dalvik-cache via ADB
try clearing the dalvik-cache via ADB
this can be done from a nookie froyo bootable SD Card
>adb shell mount -o remount,rw /dev/block/mmcblk0 / (there is a space after the 0)
>adb shell
#cd /data/dalvik-cache
#rm *
#reboot
(You might get more help if you post your question in the thread where you downloaded the kernel from)
Thank-you but I need ten posts to be able to post there. My question
Sent from my LogicPD Zoom2 using XDA App
Me too...
edgariraheta said:
Thank-you but I need ten posts to be able to post there. My question
Sent from my LogicPD Zoom2 using XDA App
Click to expand...
Click to collapse
You're getting there!
I'm a little confused "I reboot holding N to enter into Recovery Mode and install Kernel but it won't work." Installing the kernel doesn't work?
Or you can get the kernel installed and then your problem is it wont charge? Does it not charge both if it's on and if it's off?
I wiped dalvik and it got stuck/frozen. I posted here and was told that is normal. I get the same E:can't message that you do, but it still clearly says cache wipe complete.
edgariraheta said:
Ok, So i've been having problems with Overclocking my Nook Color
First of all Thanks for your help:
I have downloaded the Kernels I want to try out, I've done this process several times but when I overclock my Nook Color will not Charge. Here is the error messages I get when I go through the process, it installs the Kernel, but when I plug to charge it won't, but when i go back to stock it works, so I'm wondering if the following is the issue:
Wiping cache...
Formatting /cache...
Cache wipe complete.
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
Then I wipe the Dalvik Cache and it freezes, so I reboot holding N to enter into Recovery Mode and install Kernel but it won't work. Any help is appreciated.
Click to expand...
Click to collapse
When I install the Kernel it works fine, except my nook will not charge when I plug it into electricity. Only the stock kernel lets me charge it. I hope it makes sense.
Sent from my LogicPD Zoom2 using XDA App
That is really really strange. I think (???) the overclocked kernels are stock base.
Just for grins, have you tried charging via usb? Have you tried charging while turned off?
Reply and lets get you enough posts to ask in the kernel's thread that you are using ! (have you read of anyone there having the same problem?)
edgariraheta said:
When I install the Kernel it works fine, except my nook will not charge when I plug it into electricity. Only the stock kernel lets me charge it. I hope it makes sense.
Sent from my LogicPD Zoom2 using XDA App
Click to expand...
Click to collapse
p.s. look down this same page and it appears as though one other person has had the same problem.
I have tried that, it is really strange. I hope I can get it fixed, the Overclocked Kernels work great as far as speed, it's just charging now.
Ok, this will get me my tenth post. Thank you for helping me get it done. I appreciate it!
Related
Ok so i tried flashing Epic got into a bootloop...so went to stock KF1...ODINed the Cognition kernel with CWM...flashed Fasty II V2.0 onto it...The ROM booted up just fine!
Then I went to Market to Download TiBu..but got a error message saying "Device doesn't have sufficient space blah blah" ...I know this..just need to wipe cache partition and am back up running...but when I boot into Recovery...I get this message:
E: can't open /cache/recovery/command
E: can't open /cache/recovery/log
E: can't open /cache/recovery/log
E: can't open /cache/recovery/last_log
E: can't open /cache/recovery/last_log
And every time I try to wipe cache partition..it just skips the wipe and gives the above error again
Shot a PM to LostLogic...till then anyone else who knows the solution to the problem please help me
How do I remove these errors?
Mount cache in cwm before wipe?
Sent from my MB860
Pirateghost said:
Mount cache in cwm before wipe?
Sent from my MB860
Click to expand...
Click to collapse
It gave Error can't mount cache...
Anyways I fixed this by :
1) ODINed back to Stock KF1
2) ODINed the Stock KH3 tar file onto it
3) ODINed boog's kernel
4) Installed Fasty II V2.0 using CWM 4.0
Now everything seems to be fine again.
No errors while going into Recovery!
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 installed CUSTOM Kernel
now the phone is stoked
won't boot (stoc on lg logo / and after boot in recovery )
and when you turn on your phone now automatically goes into recovery with the following errors:
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
won't boot in s/w update ??
any help
THX
Can you get into CWM with power + volume down?
LarsPT said:
Can you get into CWM with power + volume down?
Click to expand...
Click to collapse
yes but into recovery with the following errors:
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
Can't mount /system
Can't mount / emmc
Can't mount /data
Do you think it would be possible to plug the phone into your PC and reflashing recovery?
EDIT: Also, have you explored NVFlash?
http://forum.cyanogenmod.com/topic/32319-optimus-2x-stuck-on-lg-logo/
yes but i get this error
and i can't set the port
This?
http://thehowto.wikidot.com/lg-optimus-2x
-> Restore your dead/semi-dead LG O2X
this is the error
Have you done a backup with cwm before?
Sent from my LG-P990 using xda premium
iExitus said:
Have you done a backup with cwm before?
Sent from my LG-P990 using xda premium
Click to expand...
Click to collapse
YES - i can restore it
but when i reboot - i am back to recovery
Have you tried NVFlash?
Datasafe Disaster via NVFlash
hi, take a look in Optimus 2x Android Development. There is a thread written by Rusty called "DataSafe Disaster via NVFlash". It install a full clean MCW recovery, then you restore your backup.
Also you can use SmartFlash.
Scougar said:
Have you tried NVFlash?
Click to expand...
Click to collapse
on NVFlash -
presto_92_ said:
hi, take a look in Optimus 2x Android Development. There is a thread written by Rusty called "DataSafe Disaster via NVFlash". It install a full clean MCW recovery, then you restore your backup.
Also you can use SmartFlash.
Click to expand...
Click to collapse
no.. still nothing .. it boot in CWM again again and again
final - after HARD reset / format all -emmc / data / cache / system - was corrupted / installed BIN_LGP990AT-01-V10c-226-01-FEB-26-2011+0
but when tried to restore backup -> same prob .
remaining on stock for the moment
Thx all for the support / help
Have you tried smartflash?
That means you got it working?? That's great man, happy for you I hope you'll be back into flashing ROMs again in the future
Have you found something?
I got the same problem when flashing custom kernel.
Have tried NVFlash, smartflash tool and I'm out of ideas.
I flashed back to Rocketrom GB V23 after the eMMC HARDBRICK warning.
My previous rom was Criskelo V2 ICS one
Is is possible to check the condition of the eMMC on the Samsung Galaxy NOTE?
I tried in terminal emulator:
su
(to gain root permission)
Than type in
cat /sys/class/block/mmcblk0/device/name
and got result: VYLOOM
I don't know what result i should get on a healty eMMC
anyone?
Thanks in advance
I would also like to know what that means I'll have to do some reading lol
Cyberdutch said:
I flashed back to Rocketrom GB V23 after the eMMC HARDBRICK warning.
My previous rom was Criskelo V2 ICS one
Is is possible to check the condition of the eMMC on the Samsung Galaxy NOTE?
I tried in terminal emulator:
su
(to gain root permission)
Than type in
cat /sys/class/block/mmcblk0/device/name
and got result: VYLOOM
I don't know what result i should get on a healty eMMC
anyone?
Thanks in advance
Click to expand...
Click to collapse
+1
We all have that serial name, the problem isn't that one! Galaxy Nexus also has the same eMMC!
zylor said:
We all have that serial name, the problem isn't that one! Galaxy Nexus also has the same eMMC!
Click to expand...
Click to collapse
So: f we have that name then all is good
I'm interested in this as well. Does anyone know how to run a full-scan of the EMMC to identify any possible bad blocks/sectors that have occurred?
+1 to this thread, also i got that VYL00M. is it possible to check if emmc is broken or not
I'm interested also, but I think we need not worry too much. If there is a bad block, the firmware will mark it as such and it will not be used anymore. The only consequence is a lower available storage space.
Sent from my GT-N7000 using XDA
Latoc said:
I'm interested also, but I think we need not worry too much. If there is a bad block, the firmware will mark it as such and it will not be used anymore. The only consequence is a lower available storage space.
Sent from my GT-N7000 using XDA
Click to expand...
Click to collapse
I've read that typing "dmesg" through the terminal will reveal any bad blocks. I'm not sure if this is dependent on a properly configured kernel or not.
If you want to output it, you can do "dmesg > /sdcard/dmesg.txt".
I found several interesting links for other methods....but so far, here's what my homework gathering has turned up.
http://www.slatedroid.com/topic/29039-rom-12-beta-ics-40x-team-drh-update-042112/page__st__4400
http://forum.xda-developers.com/showpost.php?p=25487137&postcount=22
http://forum.xda-developers.com/showthread.php?t=1284196
I recommend that you only READ through those links and do not attempt to try them as they are for completely different phones.
i think also if you see at cwm recovery this:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
your emmc is broken ^^
EdgaBimbam said:
i think also if you see at cwm recovery this:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
your emmc is broken ^^
Click to expand...
Click to collapse
Nope, if your eMMC is broken your phone won't boot. Something else is amiss if you get those errors in recovery.
mcmaddcatt said:
Nope, if your eMMC is broken your phone won't boot. Something else is amiss if you get those errors in recovery.
Click to expand...
Click to collapse
oh ok thanks for the info. By the way if i have reset binary count, no yellow triangle and if i would fck up emmc, will warranty will be valid or no? ;D
No, they'll have no way of checking. It would just be faulty eMMC from their perspective. With other words: warranty will be valid if phone contains stock rom for your region with no root off course.
EdgaBimbam said:
i think also if you see at cwm recovery this:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
your emmc is broken ^^
Click to expand...
Click to collapse
dam are u sure about that, because i get this message in cwm, but i flashed back to GB and runs fine, are u sure about the above which happens to me when i try to wipe dalvik cache, but when i select dalvik cache it wipes it.
again please can u confirm your statements above
@hykleif, don't worry about it. As long as it boots in gingerbread your Note's fine. I always had to select wipe dalvik twice to get it to wipe even before the ICS repacks. The errors stated in the previous post might as well be an error in CWM included in specific kernels. I've had the errors since i switched to speedmod 2k11-12 wich has khoush's CWM version, unlike Chainfire's CWM version wich is included on most kernels. For example i've never had the error on the Franco versions 3 to 10.
PoisonWolf said:
I've read that typing "dmesg" through the terminal will reveal any bad blocks. I'm not sure if this is dependent on a properly configured kernel or not.
If you want to output it, you can do "dmesg > /sdcard/dmesg.txt".
I found several interesting links for other methods....but so far, here's what my homework gathering has turned up.
http://www.slatedroid.com/topic/29039-rom-12-beta-ics-40x-team-drh-update-042112/page__st__4400
http://forum.xda-developers.com/showpost.php?p=25487137&postcount=22
http://forum.xda-developers.com/showthread.php?t=1284196
I recommend that you only READ through those links and do not attempt to try them as they are for completely different phones.
Click to expand...
Click to collapse
Thanks, nice research.
Checked dmesg.txt, no bad blocks messages in there. so i recon my eMMC is healthy.
EdgaBimbam said:
i think also if you see at cwm recovery this:
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't open /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
your emmc is broken ^^
Click to expand...
Click to collapse
nope. imo it has something to do with the external sd card
---------- Post added at 12:55 AM ---------- Previous post was at 12:37 AM ----------
I think I have a solution to see if you have any bad blocks.
When I was a HD2 owner it had a two types of nand memory, one of them was Samsung (yea weird but true). And it was harder to make a bad block on Samsung. I run a test to see if there are ant BBs after flashing hundreds of roms, results - 0 ! So it is a good news for us
Ok guys so here is what you can do to test Note for BBs. I didn't try it myself so I'm not sure if it will work:
-Do a standard procedure of flashing a new rom.
-Do not reboot!
-In cwm menu go into advanced -> error report
-a log txt file will be copied on your sd card
-Mount USB SD
-On your computer navigate to your drive.
-Look for a folder called: clockworkmod. (If you have external sd card look there)
-10) Inside you will find a file called: recovery.log
11) Copy this to your Desktop.
12) Open with Wordpad or Notepad++
If anywhere except "system/xbin/badblocks" you can see something that says "bad blocks" you probably have them.
Hope this will help you.
That test is not representative. It is dependent on how much space the ROM used up. For example, if it only wrote to 250mb out of say the TMOUS HD's 1 GB internal ROM space, it would only report if it had difficulty writing to the 250mb portion of it I think.
I do not think it is a representation of the entire 1 GB. Somebody correct me if I'm wrong on this.
If I'm right, one easy way would be to simply flash a ROM that has been modified to use all of the phone's internal storage (or at least close to it) in terms of app storage. Only then would the test be a good indicator of bad blocks.
Abagnale said:
nope. imo it has something to do with the external sd card
---------- Post added at 12:55 AM ---------- Previous post was at 12:37 AM ----------
I think I have a solution to see if you have any bad blocks.
When I was a HD2 owner it had a two types of nand memory, one of them was Samsung (yea weird but true). And it was harder to make a bad block on Samsung. I run a test to see if there are ant BBs after flashing hundreds of roms, results - 0 ! So it is a good news for us
Ok guys so here is what you can do to test Note for BBs. I didn't try it myself so I'm not sure if it will work:
-Do a standard procedure of flashing a new rom.
-Do not reboot!
-In cwm menu go into advanced -> error report
-a log txt file will be copied on your sd card
-Mount USB SD
-On your computer navigate to your drive.
-Look for a folder called: clockworkmod. (If you have external sd card look there)
-10) Inside you will find a file called: recovery.log
11) Copy this to your Desktop.
12) Open with Wordpad or Notepad++
If anywhere except "system/xbin/badblocks" you can see something that says "bad blocks" you probably have them.
Hope this will help you.
Click to expand...
Click to collapse
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.