KFHD won't boot - 7" Kindle Fire HD Q&A, Help & Troubleshooting

Hello guys, my booting problem is bit different from most booting issues. The only rom that works for me was CM11 when i first flashed is after installing 2nd bootloader. I made a backup of it. Now when I try to install other roms( some i port, some i download like kinology and CandyKat) none of them go past the boot animation. They get to the boot animation fine, but they won't boot past it. I give it like 45-90 minutes and it still doesnt boot, so I just turn off the KFHD by holding power button and restore cm11 through twrp. Anyone know a solution?

Might be some selinux xattribs causing issues, might wipe internal storage to fix, I heard twrp 2.7 has better selinux support, if an internal storage wipe doesn't do it I would try a command that wipes internal storage over a adb shell in twrp in such a way that wipes xattribs.
Make sure if you try this to backup your twrp backup first and anything on sdcard you don't want to lose.
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
Might be some selinux xattribs causing issues, might wipe internal storage to fix, I heard twrp 2.7 has better she Linux support, if an internal storage wipe doesn't do it I would try a command that wipes internal storage over a adb shell in twrp in such a way that wipes xattribs.
Make sure if you try this to backup your twrp backup first and anything on sdcard you don't want to lose.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
How would I do this? Clarify please? Thank you a lot!:good:

If you don't already have twrp 2.7 flashed then flash it, then go into twrp and hit wipe and hit advanced and choose internal storage and see if it fixes it. If that doesnt do the trick post back and i'll send you the command you will wanna try next.
As to backing up your twrp backups, just copy and paste the twrp folder off the kindles sdcard.
Sent from my Amazon Kindle Fire HD using Tapatalk

stunts513 said:
If you don't already have twrp 2.7 flashed then flash it, then go into twrp and hit wipe and hit advanced and choose internal storage and see if it fixes it. If that doesnt do the trick post back and i'll send you the command you will wanna try next.
As to backing up your twrp backups, just copy and paste the twrp folder off the kindles sdcard.
Sent from my Amazon Kindle Fire HD using Tapatalk
Click to expand...
Click to collapse
Thanks! I'll try it as soon as I get home.

Related

Looking for Nook HD 2.0.0 CWM Zip File

I've messed up my nook HD. I formatted the internal partitions with CWM and now I can't boot at all into the stock ROM (shows "Install Failed").
Does someone have a zip to install the 2.0.0 ROM from CWM just like what was posted for the HD+?
Any help would be much appreciated.
houston
houstondallas said:
I've messed up my nook HD. I formatted the internal partitions with CWM and now I can't boot at all into the stock ROM (shows "Install Failed").
Does someone have a zip to install the 2.0.0 ROM from CWM just like what was posted for the HD+?
Any help would be much appreciated.
houston
Click to expand...
Click to collapse
Did you try the 8 failed boot procedure? If you formatted /rom and /factory with CWM, you are in a big hurt. That has vital info it needs to boot.
If you formatted just /rom you are repairable. But it would take some work.
Sent from my Nook HD+ Running CM10 on SD
leapinlar said:
Did you try the 8 failed boot procedure? If you formatted /rom and /factory with CWM, you are in a big hurt. That has vital info it needs to boot.
If you formatted just /rom you are repairable. But it would take some work.
Sent from my Nook HD+ Running CM10 on SD
Click to expand...
Click to collapse
8 failed boot procedure doesn't work. I can boot into CWM and CM10, but not the stock rom. I also noticed that I don't have wireless in CM10 which I imagine has something to do with what I erased.
Is there anyway I can backup /rom and /factory from another Nook HD and write it to the broken one?
houston
houstondallas said:
8 failed boot procedure doesn't work. I can boot into CWM and CM10, but not the stock rom. I also noticed that I don't have wireless in CM10 which I imagine has something to do with what I erased.
Is there anyway I can backup /rom and /factory from another Nook HD and write it to the broken one?
houston
Click to expand...
Click to collapse
No, the info that was there on /rom is device specific. Your serial number, MAC address, etc. But you can boot into CM10? That tells me your /rom partition is ok. It sounds like you messed up the factory partition. That is what holds the factory.zip that stock recovery tries to install and fails on the 8 failed boot. And if that is what it is, you can use someone else's. It is about 350MB though. And you can use the HD cwm to push it to /factory with adb. What was it you formatted, do you remember?
edit: but you cannot flash that to internal memory with that CWM, it is hard coded to flash things to SD. I am working with bokbokan to make a CWM that you can flash to internal.
Edit 2: I just look at the HD+ factory zip. If the HD factory zip is like that, it might be able to be flashed with the current HD CWM.
Sent from my Nook HD+ Running CM10 on SD
leapinlar said:
No, the info that was there on /rom is device specific. Your serial number, MAC address, etc. But you can boot into CM10? That tells me your /rom partition is ok. It sounds like you messed up the factory partition. That is what holds the factory.zip that stock recovery tries to install and fails on the 8 failed boot. And if that is what it is, you can use someone else's. It is about 350MB though. And you can use the HD cwm to push it to /factory with adb. What was it you formatted, do you remember?
edit: but you cannot flash that to internal memory with that CWM, it is hard coded to flash things to SD. I am working with bokbokan to make a CWM that you can flash to internal.
Edit 2: I just look at the HD+ factory zip. If the HD factory zip is like that, it might be able to be flashed with the current HD CWM.
Sent from my Nook HD+ Running CM10 on SD
Click to expand...
Click to collapse
I probably did format the factory partition as I can't see a MAC address in CM10 when trying to connect to WIFI. If I do a Nandroid backup of my working unit and restore it to my non-working unit, can't I go in and edit the MAC address and serial number within the factory partition?
I'm assuming I can't do any of these things yet though until you release a HD compatible CWM?
Thanks for the help btw, you're a lifesaver!
houston
houstondallas said:
I probably did format the factory partition as I can't see a MAC address in CM10 when trying to connect to WIFI. If I do a Nandroid backup of my working unit and restore it to my non-working unit, can't I go in and edit the MAC address and serial number within the factory partition?
I'm assuming I can't do any of these things yet though until you release a HD compatible CWM?
Thanks for the help btw, you're a lifesaver!
houston
Click to expand...
Click to collapse
You can do it when booted to cm10. Look in /rom. There should be a folder named /devconf. It should have a bunch of files, one of them being MACAddress. It should contain 12 bytes, numbers and upper case letters (hex) and no line return. If there are no files there, go to the next step to see if rombackup.zip exists. If it does, it contains a zip backup made of /rom at manufacture.
You can see /factory too, but you have to mount it in terminal emulator first. Open terminal emulator and type su enter. The prompt should change to #. Then type this line:
mount -t ext4 /dev/block/mmcblk0p7 /data/local/tmp
Then you can go to /data/local/tmp and look at the files there. There should be factory.zip, rombackup.zip, romrestore.zip, and fsck.zip. The first two are the most critical.
You can access files there using your root file manager. The file manager that comes with cm10 is root if you change it to root in its settings. If the files are there, back them up to your SD. (Both /rom and /factory which is displayed at /data/local/tmp now).
Sent from my HD+ rooted stock using Tapatalk
leapinlar said:
You can do it when booted to cm10. Look in /rom. There should be a folder named /devconf. It should have a bunch of files, one of them being MACAddress. It should contain 12 bytes, numbers and upper case letters (hex) and no line return. If there are no files there, go to the next step to see if rombackup.zip exists. If it does, it contains a zip backup made of /rom at manufacture.
You can see /factory too, but you have to mount it in terminal emulator first. Open terminal emulator and type su enter. The prompt should change to #. Then type this line:
mount -t ext4 /dev/block/mmcblk0p7 /data/local/tmp
Then you can go to /data/local/tmp and look at the files there. There should be factory.zip, rombackup.zip, romrestore.zip, and fsck.zip. The first two are the most critical.
You can access files there using your root file manager. The file manager that comes with cm10 is root if you change it to root in its settings. If the files are there, back them up to your SD. (Both /rom and /factory which is displayed at /data/local/tmp now).
Click to expand...
Click to collapse
That worked like a charm. Backed up the four files from my working nook and transferred them over to my non-working nook. Nook rom booted up fine and updated to 2.0.5. The only problem I have at the moment is that both units have the same MAC address. How do I edit that? I edited the MACAdress file with the correct mac address, but CM10 isn't picking it up even though I wiped cache and flashed the newest CM10 zip. Any ideas?
Quick Update
Success! Figured out where the MAC address is stored (WiFiBackupCalibration) and HEX edited it to show the correct MAC address.
Thanks again mate!
Is there a way to recover from a /rom format?
my nook hd+ can't boot into both ROM( cm10 and stock rom ).
fireit said:
Is there a way to recover from a /rom format?
my nook hd+ can't boot into both ROM( cm10 and stock rom ).
Click to expand...
Click to collapse
If your factory partition is intact, yes. But you have to boot into CWM and get adb working. Do the same commands it had the prior user do with terminal emulator using adb. There is a backup there you can unzip and restore.
Sent from my HD+ rooted stock using Tapatalk
leapinlar said:
If your factory partition is intact, yes. But you have to boot into CWM and get adb working. Do the same commands it had the prior user do with terminal emulator using adb. There is a backup there you can unzip and restore.
Sent from my HD+ rooted stock using Tapatalk
Click to expand...
Click to collapse
thank you for your reply.
i've been formatted "/ Rom" , "/ factory" by a stupid mistake.
tried to recover partition["/ dev/block/mmcblk0p5", "/ dev/block/mmcblk0p7"] through "adb shell" but had been failed.
fireit said:
thank you for your reply.
i've been formatted "/ Rom" , "/ factory" by a stupid mistake.
tried to recover partition["/ dev/block/mmcblk0p5", "/ dev/block/mmcblk0p7"] through "adb shell" but had been failed.
Click to expand...
Click to collapse
Will you just convinced me to remove those from the CWM. They should never have been there anyway. That is a very costly mistake on your part. Those partitions held vital information on your device like serial number, MAC address, which both can be recovered, but there were some other keys there that you cannot recover. You may be only able to boot from SD from now on. You might want to return it to B&N while it is still under warranty.
Sent from my HD+ rooted stock using Tapatalk

[Q][Panic] HD+ won't boot, can access CWM SD but can't mount sdcard or emmc.

So my Nook HD+ has been running Evergreen's CM 10.1 EMMC fine for a couple weeks. I've had some lag issues so I ran Lagfix and it worked great (though that's another topic). Today, I ran Lagfix again and my HD+ froze. I pressed the power button for 12 seconds to shut it off and it wouldn't boot, just a black screen. Crap.
Ok, no panic. I try pressing the power button for 30 seconds, plug it in, etc. Nothing. Ok, no biggie, going to have to reflash, right? So I download the updated 6/13 Cm10.1 EMMC, copy it over to my CWM SD card, stick it into my HD+ and boot. Boots into CWM no problem. First thing I see is:
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
Click to expand...
Click to collapse
Well I've seen that before, so I don't panic as I seem to recall its not a serious error. So I wipe cache thinking that maybe its corrupted. Not sure if that was smart or stupid but it seems it doesn't matter, because I try and install from SDcard and I get can't mount SDcard. Yikes! I choose install from internal SD and I get can't mount EMMC. Yikes!! I try and restore a backup, there is no backup as sdcard can't mount! Ok so I reboot and try it again a few times, the same error. I try running chkdsk on the SD card on my desktop and it checks out fine, no errors. I tried swapping in another clean and newly formatted fat32 SD card with only CM10.1 on it and it won't mount either.
I try going to advance->boot to recovery and pull out the sdcard. My HD+ boots and then is stuck at the screen where it says "NOOK" in white. Right before recovery should load. Its like recovery is missing or something.
Ok, I'm getting nervous that I have a serious problem. I boot my CWM SD card again and plug the HD+ into my desktop (Windows) and run ADB. I can adb shell, so I try and mount sdcard from the shell. I get
mount: mounting /dev/block/mmcblk1p1 on /sdcard failed: no such file or directory.
Click to expand...
Click to collapse
Ok, lets try sideload: adb sideload cm.zip.
failed to write data 'protocol fault (no status)
Click to expand...
Click to collapse
Ok, I have a trick I did one time before when I had a similar problem. I try and run:
adb shell mount -t tmpfs none /sdcard
This should mount my ram as sdcard and then I can push the rom to ram and flash from there. However, the error I get is like tmpfs doesn't exist. Ok, I am no expert so at this point I am stuck.
I didn't want to wipe anything yet as I don't know what that would do. At this point being able to boot into my CWM SD card is the only thing that works and I don't want to mess with it as I am now out of my knowledge area.
Anyone know what I can do here? I mean I can't restore a backup or flash a new rom. Does the HD+ have a download mode so I can use Odin? Is fastboot an option here? I am a few days behind on my backup but I can live with a factory reset if that is called for, no problem.
I've hit panic time, please help! Thanks!
Isn't lagfix that zip that reformats your partitions? How did you flash that on an HD+?
Sent from my Galaxy Tab 2 using XDA Premium
leapinlar said:
Isn't lagfix that zip that reformats your partitions? How did you flash that on an HD+?
Sent from my Galaxy Tab 2 using XDA Premium
Click to expand...
Click to collapse
I'm glad you saw this, as I could use your Nook guruness right about now. This is it: https://play.google.com/store/apps/details?id=com.grilledmonkeydonate.lagfix&feature=search_result. Its just a GUI for fstrim and it runs it on /data.
Is there a download mode on the Nook by any chance? If I could Odin this rom on there, I think I'd be all set, but I have to say, the fact that CWM SD can't mount or find EMMC has me worried.
silkshadow said:
I'm glad you saw this, as I could use your Nook guruness right about now. This is it: https://play.google.com/store/apps/details?id=com.grilledmonkeydonate.lagfix&feature=search_result. Its just a GUI for fstrim and it runs it on /data.
Is there a download mode on the Nook by any chance? If I could Odin this rom on there, I think I'd be all set, but I have to say, the fact that CWM SD can't mount or find EMMC has me worried.
Click to expand...
Click to collapse
That sounds like a dangerous thing to be playing with. There is not a download mode and Odin is for Samsung devices.
It sounds like you borked your partitions. Did you replace the stock recovery with CWM or TWRP?
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
That sounds like a dangerous thing to be playing with. There is not a download mode and Odin is for Samsung devices.
It sounds like you borked your partitions. Did you replace the stock recovery with CWM or TWRP?
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
I did initially (like 2 weeks ago) replace the stock recovery with TWRP. I've run TWRP backups a bunch since then. Of course, those are useless with CWM SD, but I have 2 CWM nandroids on my CWM SD (which I can't access since CWM can't mount the SD ). BTW I am using, and used originally, your CWM SD image.
If I screwed up my partitions, is there a fix I can perform from CWM SD or adb?
Edit: BTW, Lagfix also runs fstrim on /cache as well, I had forgotten.
silkshadow said:
I did initially (like 2 weeks ago) replace the stock recovery with TWRP. I've run TWRP backups a bunch since then. Of course, those are useless with CWM SD, but I have 2 CWM nandroids on my CWM SD (which I can;t access since CWM can't mount the SD ). BTW I am using, and used originally, your CWM SD image.
If I screwed up my partitions, is there a fix I can perform from CWM SD?
Click to expand...
Click to collapse
If you had not replaced stock recovery with TWRP you could have done the 8 failed boot reset, but you cannot with TWRP. Also those TWRP backups are worthless because the TWRP emmc backup/restore is broken for the HD+.
You can try to repair the partitions with ADB when booted to CWM. First thing I would try is to DD the boot.img and recovery.img from your CWM backups. Boot.img goes to partition 4 and recovery.img goes to p3.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
If you had not replaced stock recovery with TWRP you could have done the 8 failed boot reset, but you cannot with TWRP. Also those TWRP backups are worthless because the TWRP emmc backup/restore is broken for the HD+.
You can try to repair the partitions with ADB when booted to CWM. First thing I would try is to DD the boot.img and recovery.img from your CWM backups. Boot.img goes to partition 4 and recovery.img goes to p3.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
I've actually been wanting to put CWM instead of TWRP, but I've been nervous about messing with recovery since I had a problem doing that on an old Samsung. Man I wish I had just bit the bullet and re-flashed CWM.
I know how to DD, but repairing the partitions is a step above what I've done before. Is there a tutorial on how to do this? Thanks!
Edit: Wait maybe I don't know how to DD. cat proc/mtd gives an error. How do I identify what to backup?
Edit2: Nevermind, I knew I saw it somewhere and there it is in your tips thread. Sorry, my bad. I'll report back after I have done it.
Ok, I'm stuck, sorry. How do I get the boot.img from my PC to my Nook? CWM won't mount SDcard. Can I just push the file to /data and then restore it from there?
Edit: Fastboot doesn't seem to work in CWM recovery?
silkshadow said:
Ok, I'm stuck, sorry. How do I get the boot.img from my PC to my Nook? CWM won't mount SDcard. Can I just push the file to /data and then restore it from there?
Click to expand...
Click to collapse
Maybe, if your /data is still ok.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
Maybe, if your /data is still ok.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Thanks, trying it now.
Ok:
~ # dd if=/data/boot.img of=/dev/block/mmcblk0p4
dd if=/data/boot.img of=/dev/block/mmcblk0p4
32768+0 records in
32768+0 records out
16777216 bytes (16.0MB) copied, 0.445588 seconds, 35.9MB/s
~ # dd if=/data/recovery.img of=/dev/block/mmcblk0p3
dd if=/data/recovery.img of=/dev/block/mmcblk0p3
30720+0 records in
30720+0 records out
15728640 bytes (15.0MB) copied, 0.397918 seconds, 37.7MB/s
Click to expand...
Click to collapse
Ok, this is a stupid question but how do I tell if it worked? The HD still won't boot without CWM SD card and sdcard or EMMC doesn't mount in CWM SD. Reboot ot recovery in CWM SD, then removing SD card, still gives me "nook" start up screen hang.
Was /data able to take the *.img files? If so, would it be a good idea to push the cm 10.1 rom to it and try and do a full flash? That doesn't have a boot partition though, right?
Edit: BTW, /data was empty in adb shell (except for the 2 img files i pushed there). There was a "media" subdir but it was also empty.
silkshadow said:
Ok:
Ok, this is a stupid question but how do I tell if it worked? The HD still won't boot without CWM SD card and sdcard or EMMC doesn't mount in CWM SD. Reboot ot recovery in CWM SD, then removing SD card, still gives me "nook" start up screen hang.
Click to expand...
Click to collapse
Take the card out, boot holding the power and n key. It should try to boot to recovery. Which backup did you use, stock or one you did after the CM10.1 install?
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
Take the card out, boot holding the power and n key. It should try to boot to recovery. Which backup did you use, stock or one you did after the CM10.1 install?
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
The HD still doesn't boot at all without the CWM SD card in. Just black screen. I can get it to boot without the SD card only if I choose advanced->boot to recovery in CWM SD. Then it just hands at the "nook" screen (the one before Cyanogenmod boot universal boot should appear).
I *think* it was the one from CM 10.1 but I cannot be 100% sure. Its the last backup I did on the CWM SD, and I recall thinking that I should have a backup of CM 10.1 but sometimes I am an idiot and don't listen to myself.
silkshadow said:
Was /data able to take the *.img files? If so, would it be a good idea to push the cm 10.1 rom to it and try and do a full flash? That doesn't have a boot partition though, right?
Edit: BTW, /data was empty in adb shell (except for the 2 img files i pushed there). There was a "media" subdir but it was also empty.
Click to expand...
Click to collapse
no, putting the CM10.1 rom zip on /data will do no good. You can't get to it to flash it. And the cm zip does include the boot partition.
/data being empty means that data was wiped somehow.
Sent from my Nook HD+ running CM10.1 on emmc.
---------- Post added at 09:20 AM ---------- Previous post was at 09:16 AM ----------
silkshadow said:
The HD still doesn't boot at all without the CWM SD card in. Just black screen. I can get it to boot without the SD card only if I choose advanced->boot to recovery in CWM SD. Then it just hands at the "nook" screen (the one before Cyanogenmod boot universal boot should appear).
I *think* it was the one from CM 10.1 but I cannot be 100% sure. Its the last backup I did on the CWM SD, and I recall thinking that I should have a backup of CM 10.1 but sometimes I am an idiot and don't listen to myself.
Click to expand...
Click to collapse
It would be best if you could restore the boot and recovery from a stock backup. Then stock can try to repair itself.
Edit: if it will not turn on without the SD inserted, you may have also messed up xloader and bootloader partitions.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
no, putting the CM10.1 rom zip on /data will do no good. You can't get to it to flash it. And the cm zip does include the boot partition.
/data being empty means that data was wiped somehow.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Ouch but /data loss is not too big, especially at this point. I just want to say you are awesome and thank you so much for helping me here! Anything I can do next? I am not sure what I could've done to wipe data. My HD was lagging a bit today but nothing serious. Just ran lagfix and it froze, but as soon as it froze I shut the Nook down.
Is it strange that I cannot mount EMMC? Is it possible that CWM is not seeing /data on EMMC but just a virtual /data?
Edit: Ok, will try to restore from stock imgs right now.
Ok these are definitely the stock boot and recovery CWM backup images:
~ # dd if=/data/recovery.img of=/dev/block/mmcblk0p3
dd if=/data/recovery.img of=/dev/block/mmcblk0p3
30720+0 records in
30720+0 records out
15728640 bytes (15.0MB) copied, 0.401123 seconds, 37.4MB/s
~ # dd if=/data/boot.img of=/dev/block/mmcblk0p4
dd if=/data/boot.img of=/dev/block/mmcblk0p4
32768+0 records in
32768+0 records out
16777216 bytes (16.0MB) copied, 0.443817 seconds, 36.1MB/s
Click to expand...
Click to collapse
Here's a strange thing. I was expecting to have to go into /data and delete the older boot.img and recovery.img before pushing the new ones. However, /data was empty again.
Ok stock img (I hope) were restored. HD will still not boot (black screen) :crying:. CWM SD advanced ->boot to recovery still hangs at "nook" boot screen the first time. The 2nd time, just black screen and now nothing but black screens.
More weirdness, I've had to plug the HD in and hold down the power button to get it to boot off the CWM SD card every time I take the CWM SD card out and try to boot without it. I just noticed that when I do this the charge light is green and stays green until CWM loads and then it turns amber.
Could this be a bootloader issue? Is there a way to restore that too?
silkshadow said:
Ok these are definitely the stock boot and recovery CWM backup images:
Here's a strange thing. I was expecting to have to go into /data and delete the older boot.img and recovery.img before pushing the new ones. However, /data was empty again.
Ok stock img (I hope) were restored. HD will still not boot (black screen) :crying:. CWM SD advanced ->boot to recovery still hangs at "nook" boot screen the first time. The 2nd time, just black screen and now nothing but black screens.
More weirdness, I've had to plug the HD in and hold down the power button to get it to boot off the CWM SD card every time I take the CWM SD card out and try to boot without it. I just noticed that when I do this the charge light is green and stays green until CWM loads and then it turns amber.
Could this be a bootloader issue? Is there a way to restore that too?
Click to expand...
Click to collapse
When you say black screen without the SD in, you mean it will not turn on?
It looks like the stock stuff took. I might be able to post my stock Xloader and bootloader img files for you. Hang on.
Sent from my Nook HD+ running CM10.1 on emmc.
leapinlar said:
When you say black screen without the SD in, you mean it will not turn on?
It looks like the stock stuff took. I might be able to post my stock Xloader and bootloader img files for you. Hang on.
Sent from my Nook HD+ running CM10.1 on emmc.
Click to expand...
Click to collapse
Yes, It doesn't seem to boot at all.
You.Rule. Thanks!
silkshadow said:
Yes, It doesn't seem to boot at all.
You.Rule. Thanks!
Click to expand...
Click to collapse
try dding these.
http://d-h.st/SG6
Sent from my Nook HD+ running CM10.1 on emmc.
Thank you very much! I will download and DD right now.

SD card and Permissions Error

Morning,
First of all:
s-off and bootloader unlocked
CWM touch 6.0.3.2 (latest)
InsertCoin 2.0.5 - first time installing custom ROM.
I have installed InsertCoin however whenever i click on the stock camera (or any camera downloaded) i get the following message: Unable to save to SD card due to insufficient file permissions. I have even tried to format and re-install the ROM however I still get the same issue. I have no idea how to fix it. If i download an image from google this works correctly and gets place in the download folder. I have tried clearing the data of the camera but this also did not work.
I moved all of my data from /data/media to the folder /data/media/0 as this is what a tutorial said regarding file paths if you move to the new 4.2.2. However for some reason now when i go into /data the folder is empty. All of my data is in the folder storage/emuated/0 (or /sdcard) I have taken 2 backups using CWM yet I have no idea where these are.
Also, when i was initially the recovery, when i first installed the recovery and entered it my computer stated 'usb device not recognised' and no adb commands would work, but as soon as i reboot manually to bootloader it was recognized. Is this normal?
Using the app 'disk usage' it states my storage card has a total size of 26206 MiB.
Clearly I have borked something up along the way.
If somebody could help that would be great, and this is rather annoying and starting to wreck my head haha.
Thanks,
Vizzy
Have you tried fix permissions in the advanced menu in CWM? Give that a go, if it doesn't work back everything up, wipe cache and SD card in CWM and re-install the rom via push or using a OTG
Okay I'll give it a go, when I'm hone tonight . Do I have to format the card into a specific format or is it just literally 'wipe SD card' like it is for cache etc.
Is the USB not recognised issue normal ? I don't fancy wiping everything then finding out I can't adb push.
Adb method: adb push ROM.zip /sdcard/ROM.zip
OTG doesn't work in the latest CWM, correct?
Sent from my HTC One using Tapatalk 4 Beta
Try with the TWRP...
Try what ? Everything in general ?
Sent from my HTC One using Tapatalk 4 Beta
vizzy said:
Try what ? Everything in general ?
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
Yes, everything!
TWRP support OTG, and is better then CWM
It's clean and simple
From my point of view ..Any mistake occurred at migration with 4.1. on 4.2. symlinks for compatibility with the previous version 4.1 aren't created correctly. Be restored with nandroid backup and try to flash stock 4.2 ROM, and only then custom 4.2.2.
The only back up I have is when I booted into recovery and took a nandroid. The one I took after I installed recovery is lost.
Sent from my HTC One using Tapatalk 4 Beta
If I understand correct , you don't have 4.1 nandroid backup ,only 4.2 ?
If yes.. save you apps and data to PC and make factory reset with formating SD (under 4.2 ) and then restore your apps and data.
Nandroid backups in 4.2.2 can be found on phone (not SD card) under data/media btw

NO os htc one

i have team win recover project v2.5.0.0 i went to wipe advance wipe and selected dalvik cache, cache, data and system and swipe to wipe
then i went to reboot and it mark no os installed. help?
seanpx said:
i have team win recover project v2.5.0.0 i went to wipe advance wipe and selected dalvik cache, cache, data and system and swipe to wipe
then i went to reboot and it mark no os installed. help?
Click to expand...
Click to collapse
OH MAN!!
What you think could wiping system partition mean? Exactly: you wiped your system partition and because of that, there is no more system to boot from anymore...
So go back to recovery and flash a rom of your choice. If you have no flashable rom on your sdcard, you have to sideload a downloaded zip from your pc. There are howto´s how to do that with TWRP here on XDA. Before you do that, you should update your recovery to the latest version of TWRP (2.6.3.0)http://forum.xda-developers.com/showthread.php?t=2173870&highlight=twrp
I wish you luck
SpeedyCarv said:
OH MAN!!
What you think could wiping system partition mean? Exactly: you wiped your system partition and because of that, there is no more system to boot from anymore...
So go back to recovery and flash a rom of your choice. If you have no flashable rom on your sdcard, you have to sideload a downloaded zip from your pc. There are howto´s how to do that with TWRP here on XDA. Before you do that, you should update your recovery to the latest version of TWRP (2.6.3.0)http://forum.xda-developers.com/showthread.php?t=2173870&highlight=twrp
I wish you luck
Click to expand...
Click to collapse
i do have a backup would that work if i have a usb otg cable but i dont have one is there any other way
i can not access my internal storage from pc
Look up ADB push or ADB sideload, either will get you where you want.
Don't worry, you haven't messed up your phone
Sent from my Nexus 4 using xda app-developers app
seanpx said:
i do have a backup would that work if i have a usb otg cable but i dont have one is there any other way
i can not access my internal storage from pc
Click to expand...
Click to collapse
You don't need to access internal storage. Just have ADB installed on your cpu and make sure it reads your device. Reboot into recovery go into adb sideload and push a Rom from the terminal of your computer. YouTube it for step by step process
Sent from my HTC One using XDA Premium 4 mobile app
thank u all i was able to used Quick-ADB-Pusher_v0.5 to put Android_Revolution_HD-One_30.0 and install it

Possibly Bricked? I'm an idiot.

I believe I may have bricked my Fire HD 7". I decided to flash a new ROM. Something I've done many many times. However, this time I decided to wipe the SD card because I wanted to get rid of all the app folders, my documents, music, etc. and start from a clean state. The problem is that it occurred to me half a second after the wipe that the ROM zip as well as the backup were on the internal SD.
So now I'm in TWRP trying to mount the device, but Windows (8.1) will not recognize the internal storage and mount it as a drive. I have the latest drivers installed but nothing...
It seems I have no way of getting a new ROM onto the internal SD card so that I can flash as normal. Help?
sicembaylor said:
I believe I may have bricked my Fire HD 7". I decided to flash a new ROM. Something I've done many many times. However, this time I decided to wipe the SD card because I wanted to get rid of all the app folders, my documents, music, etc. and start from a clean state. The problem is that it occurred to me half a second after the wipe that the ROM zip as well as the backup were on the internal SD.
So now I'm in TWRP trying to mount the device, but Windows (8.1) will not recognize the internal storage and mount it as a drive. I have the latest drivers installed but nothing...
It seems I have no way of getting a new ROM onto the internal SD card so that I can flash as normal. Help?
Click to expand...
Click to collapse
Use a Linux distro live CD to side load the ROM.
Sent from my device running CyanogenMod 11
SafinWasi said:
Use a Linux distro live CD to side load the ROM.
Sent from my device running CyanogenMod 11
Click to expand...
Click to collapse
Tried that under Ubuntu. I get an error message that the volume (Kindle) can't be mounted.
Figured out the solution. Neither Windows nor Linux would mount the device, so that I could transfer the ROM to internal storage the easy way. What worked was using ADB sideload. Now I'm relieved! For anyone else having this issue or a similar issue because they had a brain fart and wiped the internal storage AFTER wiping the ROM -- this is the solution to the problem. Use ADB sideload in TWRP.
So what are the steps
sicembaylor said:
Figured out the solution. Neither Windows nor Linux would mount the device, so that I could transfer the ROM to internal storage the easy way. What worked was using ADB sideload. Now I'm relieved! For anyone else having this issue or a similar issue because they had a brain fart and wiped the internal storage AFTER wiping the ROM -- this is the solution to the problem. Use ADB sideload in TWRP.
Click to expand...
Click to collapse
I'm in the exact same situation you were in (pre-brain fart) - I want to get a "fresh start" with my kindle. What are the steps I should take? I see in TWRP that I can wipe Dalvik, Data, Internal Storage, Cache and System.
I'm guessing I should wipe System, Cache, Dalvik, Flash the ROM, flash gapps, then wipe data/internal storage -- does this sound right?
Thanks
chiph72 said:
I'm in the exact same situation you were in (pre-brain fart) - I want to get a "fresh start" with my kindle. What are the steps I should take? I see in TWRP that I can wipe Dalvik, Data, Internal Storage, Cache and System.
I'm guessing I should wipe System, Cache, Dalvik, Flash the ROM, flash gapps, then wipe data/internal storage -- does this sound right?
Thanks
Click to expand...
Click to collapse
No need to wipe internal storage.
Re: No need to wipe internal storage
Rushead said:
No need to wipe internal storage.
Click to expand...
Click to collapse
Thanks - can you explain though? OP wanted to get rid of all of the music/documents/etc... Isn't the internal storage where these are? If not, what is stored here?
You can wipe internal if you want to, but be sure you can adb push your rom. I don't like to do this b/c it leaves you no backup plan. Besides, "fresh start" is mostly placebo imo.

Categories

Resources