Related
Guys, need some help here
I'm generally ok at fixing these sorts of problems but this one has got me well and truly stumped.
Been trying without much luck to flash a working fw onto i9000 since updating to rom with voodoo and forgetting to disable lage fix before flashing non voodoo rom. Even flashing back with voodoo rom doesnt help.
I think I've finally managed to ascertain the root cause of the issue seems to be that either the internal sd card is somehow write protected or the current journalling on the ext4 partition is undoing and changes to that partition (where does journal reside?). I seem to be in a viscious circle as well. I cant mkfs a new ext2 partition as it complains that it wasnt unmounted cleanly, If I ignore I get a segmentation fault. If I e2fsck the partition it complains it cant write to the superblock, If I use alternate superblock it complains there is data in the journal, trys to replay the journal and complains it cant write the superblock. If I tunefs to disable the journal it complains that the needs_recovery flag is set so need to e2fsck the filesystem first :-S.
I've flashed kernel that has recovery option to disable lagfix. If I choose this and reboot it just sits at Galaxy S boot screen indefinite (over an hour waited). If I mount USB using same recovery mode, I can see the files in the partition, I can (through windows) delete the files so folder shows no files however disk still shows a percentage used. If I eject and remount all the files are back. I have formatted the partition as fat32 and re-labeled the drive. Format completes succesfully (done this both using cmd line and right click format). on eject and remount, label change has remained but files are back again. Partition still shows up as ext4 when looking via adb shell.
Have tried to use parted, but despite all parted functions giving success indicator, no changes are ever made.
I'm now at a loss on how to proceed?
Anyone any ideas on what next steps could yield any further results?
I had a similar issue... what solved it was to flash Darky's ressurection rom. Had to flash it 3 times in a row.. Flashed with Odin 1.7.
Hope it helps, i know how frustrating it is.
Sent from my GT-I9000 using Tapatalk
I have tried Darkys res rom, It wouldnt boot, just stuck at Galaxy S boot screen so didnt persue it. I'll try doing it multiple times as you suggest and let you know. Ta
EDIT: Nope tried it 4 times, same result, boots to Galaxy S screen, I get the voice prompt saying its coverting system, will take approx 2 mins, then another voice prompt about restore, then it sits there indefinetly (waited about 20 mins each time). Whilst its in this state adb devices shows device in recovery, and I can get an adb shell, however there seems to be no commands accesible, cd, ls, mount etc
nivenj said:
I have tried Darkys res rom, It wouldnt boot, just stuck at Galaxy S boot screen so didnt persue it. I'll try doing it multiple times as you suggest and let you know. Ta
Click to expand...
Click to collapse
I have a way that may fix your bricked phone. If it gets to the SGS logo boot animation, I would try flashing CM7. Try it out and then try reverting back to a stock rom.
Here are the instructions:
http://forum.cyanogenmod.com/topic/15275-gt-i9000-cyanogenmod-7-we-love-bugs-version-20110211/
You MUST follow the instructions to the letter though. Do not deviate from them!
How do I know this may work? Because it happened to me. My phone was bricked, then I flashed CM7 and now it works again. I've tested going back to stock rom and it works. Give it a try. It may be tough reverting back to stock since CM7 gingerbread is awesome! lol
If that doesn't work try flashing one of the earlier Froyo ROMs, I used XXJP2, and then moving on from there. The key is to ensure that whatever ROM you use has all three files (PDA, Modem, & CSC) and tick Re-Partitioning on Odin.
Again this is what worked for me and my device was restored to great working order.
robbiev80 said:
I have a way that may fix your bricked phone. If it gets to the SGS logo boot animation, I would try flashing CM7. Try it out and then try reverting back to a stock rom.
Here are the instructions:
http://forum.cyanogenmod.com/topic/15275-gt-i9000-cyanogenmod-7-we-love-bugs-version-20110211/
You MUST follow the instructions to the letter though. Do not deviate from them!
How do I know this may work? Because it happened to me. My phone was bricked, then I flashed CM7 and now it works again. I've tested going back to stock rom and it works. Give it a try. It may be tough reverting back to stock since CM7 gingerbread is awesome! lol
Click to expand...
Click to collapse
Thanks for the suggestion but this wont work, as I said above, the root of my problem is that the internal SD card wont keep any changes I make to it. Once I upload the zip file and the phone reboots into download mode in order to flash with Odin, the files I would have put on the internal SD card will no longer be there. It seems to me that the FS cant set the recovery_flag to clean and therefore keeps replaying the journal and overwriting any changes on reboot.
I sort of proved this earlier, by managing to flash JP4 with speedmod kernel. This allows the phone to boot, but it has major force close issues. I can take a photo, see it in images, I can even mount it via USB and see it on my laptop. When I reboot, the photo is gone and anything I've deleted is back again.
Fundamentally I need someone who maybe has some experience fixing the filesystem, I cant see any Roms working until this manages to get resolved
thecrucible said:
If that doesn't work try flashing one of the earlier Froyo ROMs, I used XXJP2, and then moving on from there. The key is to ensure that whatever ROM you use has all three files (PDA, Modem, & CSC) and tick Re-Partitioning on Odin.
Again this is what worked for me and my device was restored to great working order.
Click to expand...
Click to collapse
Ive tried JP2, but no joy. Also tried
JFF,JS5,DDJG4,Darkys Res,JP4,JM8,JS3,EUGENE373,JPC,JP3,JM5 & Finally JPU, All with a mixture of partitioning and not.
got an ext-sd card? if so remove it, format sd, then try factory reseting,
edit : flash an old rom, like jm2, ascertain its function then yell again (missed a line *doh*)
azuresystem said:
got an ext-sd card? if so remove it, format sd, then try factory reseting,
edit : flash an old rom, like jm2, ascertain its function then yell again (missed a line *doh*)
Click to expand...
Click to collapse
Yep tried all that, tried formating via recovery mode, says successful, but all data still exists on reboot. Have tried formating using windows, via command line, via adb shell, they all say they are succesfull but on reboot, same problem exists and all data is still there :-S
nivenj said:
Ive tried JP2, but no joy. Also tried
JFF,JS5,DDJG4,Darkys Res,JP4,JM8,JS3,EUGENE373,JPC,JP3,JM5 & Finally JPU, All with a mixture of partitioning and not.
Click to expand...
Click to collapse
I am sorry, not sure where to go from there. Keep Googling and maybe you'll come across something helpful.
Sent from my Galaxy S using Tapatalk
Hi. Has anyone come across a solution to this problem. Any changes to the data on my internal SD card are lost on reboot, and many of my apps are not working.
jm_928 said:
Hi. Has anyone come across a solution to this problem. Any changes to the data on my internal SD card are lost on reboot, and many of my apps are not working.
Click to expand...
Click to collapse
Try editing the void.fstab to swap the internal sd card and external sd card. --- it won't address issues with internal card, but it may get you up and going again..
fooman123 said:
Try editing the void.fstab to swap the internal sd card and external sd card. --- it won't address issues with internal card, but it may get you up and going again..
Click to expand...
Click to collapse
Thanks fooman123. Can you tell me where I can find the void.fstab file?
jm_928 said:
Thanks fooman123. Can you tell me where I can find the void.fstab file?
Click to expand...
Click to collapse
see this tread:
http://forum.xda-developers.com/showthread.php?t=1088474&page=14
use the correct void.fstab for your phone (i9000 and i9003 are different)
backup the original and compare the new and old void.fstab file..
Ok fellas, my nook color has been out of commission for over 2 months. I can boot from sd but not from internal emmc.
Sam has been helpin me but it has been difficult due to him being in a different part of the world. From what i've been told my emmc is corrupt and my partitions need to be rebuilt or formatted.
I have tried the different fixes here and still i am stuck on the N screen.
I am trying to return my NC to stock form.
I will let Sam chime in also. I know there are a lot of talents on this forum and pretty sure this can be fixed.
Thanks everyone..
Sent from my SGH-T959 using XDA App
Hi,
As Wendell said, I've tried helping him with his corrupt emmc.
The problem is:
The emmc semms to be corrupt, or at least some sectors of it. Wendell cannot return it, because it boots to CWR. That's the strange part, though the disk seems totally corrupt, it still seems to be able to boot. I guess some sectors and still working. But I don't know of any way to find out which..
This is what I know so far:
The internal emmc generally returns I/O error when trying to use fdisk or parted.
But, somehow, depending on the bs and count, I can dd /dev/zero to it.
Even after having dd zeros to it, it still seems to boot to internal CWR. So, the dd isn't working. Still don't know why, or how to remedy to it.
If someone could give us a clue or two here, it would be very much appreciated. I must admit I'm really no HDD expert..
Thanks!!
Sam
http://nookdevs.com/Flash_back_to_clean_stock_ROM
Have you guys tried this? Or has an internal EMMC rom been flashed?
Any idea how the partition became corrupt? Did you dual-boot?
Partition became corrupt after flashing a couple of the very first OC kernels. Not sure if thats what caused it but wouldn't boot past N screen. Since then i have been trying to fix it by doing the several fixes to no avail and possibly damaging the emmc even more.
Sent from my SGH-T959 using XDA App
fprice02 said:
http://nookdevs.com/Flash_back_to_clean_stock_ROM
Have you guys tried this? Or has an internal EMMC rom been flashed?
Click to expand...
Click to collapse
Please correct if I'm wrong but i think i need the stock recovery for this method. Unfortunately, the stock was replaced with CWR and now i cannot even get rid of CWR off the internal. If I could do it again, I would not place CWR on internal but rather run it off sd. I installed CWR via rom manager because the sd method was not yet available.
Try option number 3 in the thread I made in the general forum. the clockworkmod recover + stuck at " " screen. Flashing cwm via rom manager can cause corrupted /boot partition
Sent from my Vortex using Tapatalk
Woot , thanks for your response.
I have tried those methods to no avail. I can currently boot into CWR via 'home+N' but here is the crazy part, I cannot use the zip that sam made to remove CWR from emmc or even try to update to 3.0.1.0 via the CWR zip. My CWR on the emmc will not budge at all.
Sam, has even tried to erase my emmc totally from being able to boot to CWR just so I can get it looked at by B&N but CWR will not budge.
Excuse my ignorance, but will linux run off the sd card on the nook?
What about using something like GParted? Perhaps the USB bootable image on the sd card might work?
I know you are all trying to help. But please keep in mind that there aren't any obvious answers here. The emmc is corrupt. You can't flash anything to it.. and as I already stated, parted won't work either, it returns I/o error.
The only strange thing is that the nook still boots.. I can't understand that as the emmc lacks any partition table.
We need someone with hdd repairing experience. None of the answers found on existant threads will help Wendell..
Thank you.
Sam
Sent from my Desire HD using XDA App
samuelhalff said:
The only strange thing is that the nook still boots.. I can't understand that as the emmc lacks any partition table.
Click to expand...
Click to collapse
The boot may be from real hardware/non-eemc rom.
I know you said it's a emmc error - but have you tried to flash back to stock using CWM off of the SD with thecubed's MonsterRoot pack?
Yes
Sent from my SGH-T959 using XDA App
I'm sure you have tried this... but just in case...
Can you fdisk the partitions... then dd image img files to it?
I don't know if you will have any way of saving mmcblk0p2 and 3 to save your device specific information.
I believe sam has already tried
Sent from my SGH-T959 using XDA App
Here is what i would try.
First thing, get a cwm sd card setup that is bootable and has a decent amount of space so you can backup your emmc. The cwm sd card will allow us to adb in, but not worry about having any emmc partitions mounted (booting to a full android image would want at least the mmcblk0p2 partition mounted).
Make sure you have adb setup and working, so you can adb in once you've booted into cwm from the sd card. Make sure you know how to use adb pull and adb push to get files onto and off of the device easily.
Boot from the card, adb shell into the device. make sure when you are doing dd commands you are pulling from and writing to image files in a directory on the sd card, not on the emmc. you probably shouldn't even have any emmc partitions mounted at all.
Note: dd and bzip2 are both on the cwm 3.0.10 ramdisk, dunno about the earlier versions
I'd make a backup image of your emmc just in case things go from bad to worse:
Code:
dd if=/dev/mmcblk0 | bzip2 -9 > backup.img.bz2
This will take a while.
Now you'll need a MBR from someone with a stock partition table (i'm dual booting so mine probably won't work, otherwise i'd make one for you). Any volunteers?
Code:
dd if=/dev/mmcblk0 of=mbr.img bs=512 count=1
Once you have this file, just dump the image onto your emmc.
Code:
dd if=mbr.img of=/dev/mmcblk0
once you have a working partition table, you should be on your way to using the standard recovery techniques peppered throughout the forums.
btw, this won't fix any corruption in the extended partition table, that would take a little more effort (i'd have to read up on where/how that info is saved). Also obviously if it's a hardware problem rather than just corrupted data you have more problems than this will fix.
p.s. cwm loading witch a corrupt partiton table isn't that weird imho. the bootloader has barely over 400 bytes to load up the boot file and hand things off, it's probably not taking a close look at the partition map when it does this.
I know am probably being a stupid noob...have you tried the 8 failed boots?
Sent from my NookColor using Tapatalk
wendellc said:
Woot , thanks for your response.
I have tried those methods to no avail. I can currently boot into CWR via 'home+N' but here is the crazy part, I cannot use the zip that sam made to remove CWR from emmc or even try to update to 3.0.1.0 via the CWR zip. My CWR on the emmc will not budge at all.
Sam, has even tried to erase my emmc totally from being able to boot to CWR just so I can get it looked at by B&N but CWR will not budge.
Click to expand...
Click to collapse
Again..probably being a noob...are the file permissions set as ro? Mayhaps you need to change permissions?
Sent from my NookColor using Tapatalk
Lol.
Thanks for all your input.
DD and fdisk return i/o error. DD only works if I use i.e 1M as BS.
It seems there isn't any partition table on the emmc.
I guess some sectors are dead. The idea would be to identify which ones and erase them.
Although simply being able to remove the bootloader would allow Wendell to bring it back to the shop..
Maybe someone has a clue as to how to delete completely the first X sectors of emmc..?
Thanks.
Sent from my Desire HD using XDA App
samuelhalff said:
Lol.
Thanks for all your input.
DD and fdisk return i/o error. DD only works if I use i.e 1M as BS.
It seems there isn't any partition table on the emmc.
I guess some sectors are dead. The idea would be to identify which ones and erase them.
Although simply being able to remove the bootloader would allow Wendell to bring it back to the shop..
Maybe someone has a clue as to how to delete completely the first X sectors of emmc..?
Thanks.
Sent from my Desire HD using XDA App
Click to expand...
Click to collapse
Did you read my post? It is exactly telling you how to replace the first sector of the emmc. you can source it from /dev/zero with a bs=512 and a count=1 if you really wanna wipe the bootloader, but better would be just getting it working yeah? all our nooks have the same partition map (unless we are dual booting) and that map is stored on the first sector. My instruction tell how to pull the first sector with dd, and how to push it back on. notice i'm accessing the mmc directly? not the partitions? so unless his hardware is bad (or the extended partition is corrupt too) then my instructions will work. He just needs a copy of the first sector of a working nook. I'd put mine up but i'm not sure it would work, i have two extra partitions from stock. It probably wouldn't matter, but i'm not 100% sure on that, so i'd rather it be someone else that makes the image from a nook with a stock partition map (the contents of the partitions can be whatever, as long as they are all in the same place as stock).
Hi,
Thanks. Yes, I read your post. dd, for some reason, only works if I set bs to at least 1M. I don't have the NC, but maybe Wendell could confirm that.
Wendell: go to "adb shell" and type [dd if=/dev/zero of="/dev/block/mmcblk0" bs=512 count=1] without the [].
Please confirm that this returns an I/O error.
But for some reason, using 1M or greater as bs works, but the bootloader still isn't erased.. it still boots to CWR..
I'm pretty sure all the I/O error i've had mean that there's a hardware failure.. But that's my opinion, nothing more..
Thanks.
My problem is almost similar to this , except the cause, and the seriousness
http://forum.xda-developers.com/showthread.php?t=2325101.
Could anyone report the rom problem to the official(i do not know how to access to them) and could the official give a solution? :crying:
If anyone could help me solve the problem, please tell the method step by step , i am not good at computer. If solving the problem need any files please post the downloading threads.Thanks.
I think the reason why I could not install the cm10.2 again maybe caused by load the internal memory too much. I saw someone said to install the cm would not format the data in the internal memory. When the memory is almost full , it won't install apps . Maybe it can not rewrite the rom. If so , how can i delete my personal data .?Now i can not boot the tablet , and even can not connect it to a PC. I am at a loss and very worried. I am out of USA , and it is almost impossible for me to return it to B&N to have it repaired. Could anyone here give some advice to repair it .
I asked verygreen , and he gave me an answer
There appears to be a bug in internal storage software used in Nook HDs that leads to internal storage dying under certain conditions, though the conditions are not exactly clear, but it also seems to do with a new feature added in Android 4.3
I disabled this feature on 8/15, though it's not yet clear if 8/15 nightly was built with that added or not.
The bug is not unique to Nooks too, Some Galaxy Note devices that use a very similar samsung-branded internal storage also have this problem.
But not gave the solution , could anyone solve this problem and give the solution step by step to me, thanks. i am just at a loss here
I'm having a similar issue except I can get the nook logo on screen and sometimes the Cyanoboot Universal Bootloader screen. Both freeze at that point though.
Sent from my M470BSA using xda app-developers app
Ogre6473 said:
I'm having a similar issue except I can get the nook logo on screen and sometimes the Cyanoboot Universal Bootloader screen. Both freeze at that point though.
Sent from my M470BSA using xda app-developers app
Click to expand...
Click to collapse
I think this fatal problem is very common . Does anyone else have the same problem? If so , reporting here to get the officials' attention . Now verygreen is working on it , but he hasn't given the solving date .
nookhdplus said:
I think this fatal problem is very common . Does anyone else have the same problem? If so , reporting here to get the officials' attention . Now verygreen is working on it , but he hasn't given the solving date .
Click to expand...
Click to collapse
looks like we have the same problem you can try requesting to verygreen here http://forum.xda-developers.com/showthread.php?t=2221289
Same problem here.
I'm using cm-10.2-20130815-NIGHTLY-ovation and gapps-jb-20130813-signed. Same problem as above. boots to Nook loading screen and that's it. I left the device connected to my PC copying files and came back to a dead device. Charged it and now it's not booting at all.
brickinit said:
I'm using cm-10.2-20130815-NIGHTLY-ovation and gapps-jb-20130813-signed. Same problem as above. boots to Nook loading screen and that's it. I left the device connected to my PC copying files and came back to a dead device. Charged it and now it's not booting at all.
Click to expand...
Click to collapse
Now I can nearly confirm there is a fatal bug in the 8/15 rom , so many are affected by it .I recommand others not to update to the cm10.2 before the problem is solved and the official should offshelve it from the website and give a solution as quickly as possible.
talha970 said:
looks like we have the same problem you can try requesting to verygreen here http://forum.xda-developers.com/showthread.php?t=2221289
Click to expand...
Click to collapse
BTW, which rom did you use when the problem occured ? Is it the 8/15 version?
brickinit said:
I'm using cm-10.2-20130815-NIGHTLY-ovation and gapps-jb-20130813-signed. Same problem as above. boots to Nook loading screen and that's it. I left the device connected to my PC copying files and came back to a dead device. Charged it and now it's not booting at all.
Click to expand...
Click to collapse
Booting to Nook loading screen (with no sdcard in) is different symptoms from the total emmc brick, because when emmc is bricked, so no loading scring could be possible.
In any case, the important part is, if somebody has a total bricked device and would like to donate it to me for further research on unbricking (and I will return it if succeeded), shoot me a PM.
Or if you have a brick and feel technically advanced enough to be able to run various custom kernels, CWMs, have adb working and know how to use it and are familiar with linux and willing to try to help, also PM me.
verygreen said:
Booting to Nook loading screen (with no sdcard in) is different symptoms from the total emmc brick, because when emmc is bricked, so no loading scring could be possible.
In any case, the important part is, if somebody has a total bricked device and would like to donate it to me for further research on unbricking (and I will return it if succeeded), shoot me a PM.
Or if you have a brick and feel technically advanced enough to be able to run various custom kernels, CWMs, have adb working and know how to use it and are familiar with linux and willing to try to help, also PM me.
Click to expand...
Click to collapse
I would donate my totally bricked tablet to you but there is too much personal info in it.
Riddleric said:
I would donate my totally bricked tablet to you but there is too much personal info in it.
Click to expand...
Click to collapse
The info is likely not recoverable without some significant effort anyway, but I certainly can understand this decision too.
Count me too in the list of bricked HD+s. I was on CM10.2 0815.
It started with a reboot, but the boot process got rebooted again. Now it would just hang on Cyanoboot screen. I have tried SD Recovery but it showed that sd card or EMMC cannot be mounted. Now it will not even boot to recovery from SD card. I have tried the bootloader which gives you an option to choose SD recovery or boot normally and the boot loader loads but it cannot boot to either EMMC or SD recovery.
Worse part is that it hangs on the Cyanoboot screen. Not sure even Nook will honor the warranty.
Edit: BTW I never installed fstrim or anything like that. It probably was the 0813 version that initiated it but I wonder why it failed in 0815 when trim has been removed?
excalibar001 said:
Count me too in the list of bricked HD+s. I was on CM10.2 0815.
It started with a reboot, but the boot process got rebooted again. Now it would just hang on Cyanoboot screen. I have tried SD Recovery but it showed that sd card or EMMC cannot be mounted. Now it will not even boot to recovery from SD card. I have tried the bootloader which gives you an option to choose SD recovery or boot normally and the boot loader loads but it cannot boot to either EMMC or SD recovery.
Worse part is that it hangs on the Cyanoboot screen. Not sure even Nook will honor the warranty.
Click to expand...
Click to collapse
if it boots into CM logo with no sdcard in, then your emmc is at least answering, chances are you can just flash stock zip from leapinlair's stock hints thread from my noemmc sdcard cwm (or his from his thread)
Also failing that if you are just interested in warranty service, boot from my noemmc cwm, adb shell in and execute this:
dd if=/dev/zero of=/dev/block/mmcblk1p1
dd if=/dev/zero of=/dev/block/mmcblk1p2
this will make the cyanogen logo display go away and you'll just have black screen on boot.
verygreen said:
if it boots into CM logo with no sdcard in, then your emmc is at least answering, chances are you can just flash stock zip from leapinlair's stock hints thread from my noemmc sdcard cwm (or his from his thread)
Click to expand...
Click to collapse
Thank you verygreen, you are very kind to respond to each and everyone.
I have tried a number of different sdcard recoveries including cwm-early7.1 and leapinlair's as well, but the tablet never finishes booting even the recovery. If it is just SD card recovery, it will keep showing the cyanoboot screen. I modified the recovery (from Leapinlair's provided file) that gives you an option to boot into SD card recovery or into Stock rom (which does not exist for me but just an option). I get the option screen but selecting the SD card recovery just freezes the tablet.
I was planning to
1) write the recovery to sdcard,
2) increase the size of the recovery partition using EASUS partition manager,
3) putting emmc recovery, stock or CM rom, and gapps in the expanded partition
4) booting into it and installing all of these
but I never get into booting into recovery with or without expanded sd recovery. I also tried every sdcard recovery out there. No success.
excalibar001 said:
Thank you verygreen, you are very kind to respond to each and everyone.
I have tried a number of different sdcard recoveries including cwm-early7.1 and leapinlair's as well, but the tablet never finishes booting even the recovery. If it is just SD card recovery, it will keep showing the cyanoboot screen. I modified the recovery (from Leapinlair's provided file) that gives you an option to boot into SD card recovery or into Stock rom (which does not exist for me but just an option). I get the option screen but selecting the SD card recovery just freezes the tablet.
I was planning to
1) write the recovery to sdcard,
2) increase the size of the recovery partition using EASUS partition manager,
3) putting emmc recovery, stock or CM rom, and gapps in the expanded partition
4) booting into it and installing all of these
but I never get into booting into recovery with or without expanded sd recovery. I also tried every sdcard recovery out there. No success.
Click to expand...
Click to collapse
try recovery from this post: http://forum.xda-developers.com/showpost.php?p=44790925&postcount=67
note it reverts sdcard and emmc, so now sdcard is mmc0 and emmc is mmc1 (does not matter for stock as it installs using named aliases anyway, but matters if you plan to do any commands by hand in terminal).
This recovery certainly works even when emmc is totally dead so should work for you too.
verygreen said:
try recovery from this post: http://forum.xda-developers.com/showpost.php?p=44790925&postcount=67
note it reverts sdcard and emmc, so now sdcard is mmc0 and emmc is mmc1 (does not matter for stock as it installs using named aliases anyway, but matters if you plan to do any commands by hand in terminal).
This recovery certainly works even when emmc is totally dead so should work for you too.
Click to expand...
Click to collapse
Hi Verygreen, what's your suggestion on contacting b&n? since it's still under warranty and I can't even turn it on so should I send it in for repair or replace?
Riddleric said:
Hi Verygreen, what's your suggestion on contacting b&n? since it's still under warranty and I can't even turn it on so should I send it in for repair or replace?
Click to expand...
Click to collapse
it does not really matter. "repair" is a codeword for "replace" these days, it's just they get your unit in and then send you one of their pile of repaired units, then see if they can fix yours and if they can, they add it to the refurbished pile to send to whoever send their stuff in next, or to sell through some side channel.
And of course I do recommend you to go the repair/replace route (unless you want to donate a broken unit to me for further research, of course ). Who knows, you might even win the emmc lottery and get emmc that is not buggy too.
verygreen said:
try recovery from this post: http://forum.xda-developers.com/showpost.php?p=44790925&postcount=67
note it reverts sdcard and emmc, so now sdcard is mmc0 and emmc is mmc1 (does not matter for stock as it installs using named aliases anyway, but matters if you plan to do any commands by hand in terminal).
This recovery certainly works even when emmc is totally dead so should work for you too.
Click to expand...
Click to collapse
Thanks verygreen
I have noticed something else. When I connect the nook to pc without a sdcard, I can see a Blaze_Tablet while if i (try to boot) from sdcard, it shows a B&N Nook HD+ with a question mark. Does it tell you anything.
When it shows that a nook has been connected, I tried installing the drivers from LeapinLair page but windows says that no compatible drivers found. I think I have to get to install those drivers before I could connect using ADB.
When and if I boot to sdcard recovery, what should be I doing next to fix the tablet?
excalibar001 said:
Thanks verygreen
I have noticed something else. When I connect the nook to pc without a sdcard, I can see a Blaze_Tablet while if i (try to boot) from sdcard, it shows a B&N Nook HD+ with a question mark. Does it tell you anything.
When it shows that a nook has been connected, I tried installing the drivers from LeapinLair page but windows says that no compatible drivers found. I think I have to get to install those drivers before I could connect using ADB.
When and if I boot to sdcard recovery, what should be I doing next to fix the tablet?
Click to expand...
Click to collapse
see if you can mount /cache:
in adb shell:
mount /dev/block/platform/omap/omap_hsmmc.1/by-name/cache /cache
if that does not work, try reformatting it:
mke2fs -t ext4 /dev/block/platform/omap/omap_hsmmc.1/by-name/cache
see if that succeeds.
then try rebooting again without sdcard and see if that helped.
Hello,
I figure someone here might be able to help since most of where I found information regarding my issue came from this subforum. My phone is i897 (Captivate), but I think it should be similar; I posted there as well but no luck .
I normally can get by pretty well, and I have done numerous searches before posting for help. This time I have really run into a brick wall, and I really need help here.
Basically, I did something really stupid where I did not know that the phone had been booting off a external SD (my mom gave it back to me like that). Actually, I suspected that it did because the phone would have not booted without the card, however, I could flash my phone even if I removed the external SD card (as if the internal SD were there, but it wasn't), but it had always required me to insert the card back in for it to reboot from a flash. So I thought maybe internal SD was fine.
Originally, I had a Samsung 8gb class 6, but I wanted to change it to a 32gb class 10 ( to help the OS run smoother IF it were running on external SD). This is where I made a great mistake; I formatted the 32gb card and made 3 partitions. The first one is in FAT32 of 24 gb, 2nd is in EXT4 4gb, 3rd is the rest in EXT 4 as well. The original setup that was working had about 5.5gb in FAT32 and about 1.88gb of EXT(not sure which). The mistake was that I also formatted the 8gb card as well. In chronological order, these were what has happened:
1. I did a Odin stock reset to 2.3.5 with CWM injected
2. Installed Corn Kernel
3. Formatted both external SDs and repartition as mentioned above
4. At this point, I didn't know there was an issue. CWM sees the external SD and I tried to install CM 10.3 since I read in one of the threads that JB has a weird file systems and it needed to be installed twice to fix sdcard0 and sdcard1
5. CM10.3 installed kernel, and failed afterward since there was no /system and /data. At this point, I have Neat Kernel installed and lost bootloader along with fastboot and cannot access download mode.
6. I have tried to change EXT4 to EXT3 or EXT2 to see if there would be any luck in file system recognition, but no luck
7. The only way I can connect to the phone was through ADB, and verified that my internal SD card was dead because mmcblk0 was not there when I removed external SD
8. I tried to mount mmcblk0p1 (4gb EXT4 partition) and mmcblk0p2 as /system and /data, but I had been getting an error
9. I tried to use USB mount in TWRP, but no additional drive showed up (confirmed dead internal SD)
9. I tried to look for vold.fstabs but /system does not exist. The only *.fstabs file founds were in /etc file (not /system/etc) and is, for example, aries.fstabs
I know for the fact that it can be done because the phone was working before, but I really don't have enough linux knowledge or the what the phone looks at in chronological order in order to figure out how to remedy this. I would really appreciate if someone can guide me to a right direction. Thank you.
Below are major references I have gone through (not including youtube videos, etc..):
http://forum.xda-developers.com/showthread.php?t=2057004
http://forum.xda-developers.com/showthread.php?t=1897918
http://forum.xda-developers.com/showthread.php?t=2057004
http://forum.xda-developers.com/showthread.php?t=2199215
http://forum.xda-developers.com/showthread.php?p=30415128#post30415128
http://forum.xda-developers.com/showpost.php?p=31017954&postcount=5335
http://forum.xda-developers.com/showthread.php?t=911228
http://forum.xda-developers.com/showthread.php?t=1463756
http://forum.xda-developers.com/showthread.php?t=1241574
http://forum.xda-developers.com/showthread.php?t=845708&page=2
PMrjn83 said:
Hello,
I figure someone here might be able to help since most of where I found information regarding my issue came from this subforum. My phone is i897 (Captivate), but I think it should be similar; I posted there as well but no luck .
I normally can get by pretty well, and I have done numerous searches before posting for help. This time I have really run into a brick wall, and I really need help here.
Basically, I did something really stupid where I did not know that the phone had been booting off a external SD (my mom gave it back to me like that). Actually, I suspected that it did because the phone would have not booted without the card, however, I could flash my phone even if I removed the external SD card (as if the internal SD were there, but it wasn't), but it had always required me to insert the card back in for it to reboot from a flash. So I thought maybe internal SD was fine.
Originally, I had a Samsung 8gb class 6, but I wanted to change it to a 32gb class 10 ( to help the OS run smoother IF it were running on external SD). This is where I made a great mistake; I formatted the 32gb card and made 3 partitions. The first one is in FAT32 of 24 gb, 2nd is in EXT4 4gb, 3rd is the rest in EXT 4 as well. The original setup that was working had about 5.5gb in FAT32 and about 1.88gb of EXT(not sure which). The mistake was that I also formatted the 8gb card as well. In chronological order, these were what has happened:
1. I did a Odin stock reset to 2.3.5 with CWM injected
2. Installed Corn Kernel
3. Formatted both external SDs and repartition as mentioned above
4. At this point, I didn't know there was an issue. CWM sees the external SD and I tried to install CM 10.3 since I read in one of the threads that JB has a weird file systems and it needed to be installed twice to fix sdcard0 and sdcard1
5. CM10.3 installed kernel, and failed afterward since there was no /system and /data. At this point, I have Neat Kernel installed and lost bootloader along with fastboot and cannot access download mode.
6. I have tried to change EXT4 to EXT3 or EXT2 to see if there would be any luck in file system recognition, but no luck
7. The only way I can connect to the phone was through ADB, and verified that my internal SD card was dead because mmcblk0 was not there when I removed external SD
8. I tried to mount mmcblk0p1 (4gb EXT4 partition) and mmcblk0p2 as /system and /data, but I had been getting an error
9. I tried to use USB mount in TWRP, but no additional drive showed up (confirmed dead internal SD)
9. I tried to look for vold.fstabs but /system does not exist. The only *.fstabs file founds were in /etc file (not /system/etc) and is, for example, aries.fstabs
I know for the fact that it can be done because the phone was working before, but I really don't have enough linux knowledge or the what the phone looks at in chronological order in order to figure out how to remedy this. I would really appreciate if someone can guide me to a right direction. Thank you.
Below are major references I have gone through (not including youtube videos, etc..):
http://forum.xda-developers.com/showthread.php?t=2057004
http://forum.xda-developers.com/showthread.php?t=1897918
http://forum.xda-developers.com/showthread.php?t=2057004
http://forum.xda-developers.com/showthread.php?t=2199215
http://forum.xda-developers.com/showthread.php?p=30415128#post30415128
http://forum.xda-developers.com/showpost.php?p=31017954&postcount=5335
http://forum.xda-developers.com/showthread.php?t=911228
http://forum.xda-developers.com/showthread.php?t=1463756
http://forum.xda-developers.com/showthread.php?t=1241574
http://forum.xda-developers.com/showthread.php?t=845708&page=2
Click to expand...
Click to collapse
Have you looked over this guide ? or this ?
Höhenheim said:
Have you looked over this guide ? or this ?
Click to expand...
Click to collapse
Thanks. I'll try when I get home to my desktop. For some reason, my laptop does not recognize the phone through adb. It shows "SGH-i897" in device manager with an exclamation mark. And yes, I have tried quite a few drivers, etc... :/
I might need to try this...
http://forum.xda-developers.com/showthread.php?t=1761968
Höhenheim said:
Have you looked over this guide ? or this ?
Click to expand...
Click to collapse
I just had a chance to look at it more thoroughly. The biggest problem for me is that my phone does not have an OS, and it's on semaphore kernel where I cannot access download mode nor fastboot. I have tried to install gingerbread kernel to try to recover download mode/fastboot (speedmods), but I kept running into error 0. I have also tried to modify the su.binary, but that didn't work :/. Any idea how to start? Thanks.
PMrjn83 said:
I just had a chance to look at it more thoroughly. The biggest problem for me is that my phone does not have an OS, and it's on semaphore kernel where I cannot access download mode nor fastboot. I have tried to install gingerbread kernel to try to recover download mode/fastboot (speedmods), but I kept running into error 0. I have also tried to modify the su.binary, but that didn't work :/. Any idea how to start? Thanks.
Click to expand...
Click to collapse
Based on your earlier comments on the partitions failing to mount, you should format: system, data, datadata, cache.
gsstudios said:
Based on your earlier comments on the partitions failing to mount, you should format: system, data, datadata, cache.
Click to expand...
Click to collapse
Well, I tried. If it doesn't mount at all, how can you format?
Hey, I got a Virgin Mobile HTC Desire 510. Y'know, the blue one....
I fudged up severely the other evening and installed another rom which bricked my phone. I did manage however restore a stock back-up I managed to find online, however the phone was still rooted, tampered and TWMP(did I get the abbreviation correct?) is still on it. So I go and install Supersu and Busybox in an attempt to go back to where I left off as I've been attempting to get the phone to do the internal to SD card bit but no success thus far, especially not right now. In anycase, after reinstalling Supersu, I load it up and get the message of "There is no SU binary installed and SuperSU cannot install it. This is a problem! If you just upraded to Android 4.3, you need to manually re-root. consult the relevant forums for your device.". I attempted to reinstall threw recovery and it seems to be working till I get the actual phone's Google ROM running and click on the SuperSU program only to get that message.
Any suggestions or advice on how to do this and get SuperSU back up? How do I exactly re-root or can I somehow install the binary via PC or flash?
Can the HTC Desire 510(Virgin Mobile version) even have the the script/rom/trick setting to have the SD Card used as Internal memory or is this quest just wasted time?
Thanks
EDIT- Device version is 0PCV1
Okkvltist said:
Hey, I got a Virgin Mobile HTC Desire 510. Y'know, the blue one....
I fudged up severely the other evening and installed another rom which bricked my phone. I did manage however restore a stock back-up I managed to find online, however the phone was still rooted, tampered and TWMP(did I get the abbreviation correct?) is still on it. So I go and install Supersu and Busybox in an attempt to go back to where I left off as I've been attempting to get the phone to do the internal to SD card bit but no success thus far, especially not right now. In anycase, after reinstalling Supersu, I load it up and get the message of "There is no SU binary installed and SuperSU cannot install it. This is a problem! If you just upraded to Android 4.3, you need to manually re-root. consult the relevant forums for your device.". I attempted to reinstall threw recovery and it seems to be working till I get the actual phone's Google ROM running and click on the SuperSU program only to get that message.
Any suggestions or advice on how to do this and get SuperSU back up? How do I exactly re-root or can I somehow install the binary via PC or flash?
Can the HTC Desire 510(Virgin Mobile version) even have the the script/rom/trick setting to have the SD Card used as Internal memory or is this quest just wasted time?
Thanks
EDIT- Device version is 0PCV1
Click to expand...
Click to collapse
Hello and welcome to xda,
Where exactly did you get the back-up from that you used to restore?
You were close it is TWRP or Team Win Recovery Project.
I believe the reason you can't install SuperSU is because you don't have a write protect removed kernel installed. You can find one here. Check out their related forums and see which one you like best. They are pretty much all great. Some aren't being supported anymore as a heads up. To flash a kernel, in case you didn't know how:
Go into Settings-About-Software information-More-Kernel version and write down the name of the Kernel
1. Power the phone down
2. Hold "Down" button then hold "Power" key while still holding "Down" button, until you get into the bootloader
3. Release "Down" and "Power" button
4. Tap "Power" key once and it will change from "HBOOT" in white letters with blue background to "FASTBOOT" in white letters with red background on your phone
5. Connect your USB cable and it will say "FASTBOOT USB" on your phone
6. Navigate to the folder you have your fastboot.exe from Android Studio or wherever you obtained it from (Mine is in C:\Users\myusername\Android\sdk\platform-tools)
7. Hold the "Shift" key then right click in any empty space in that folder
8. Select "Open command window here"
9. Type
Code:
fastboot devices
in the command window, then press Enter just to make sure it is picking up your phone
10. You should see something like:
Code:
HT42PXU89475 fastboot
if you don't make sure your USB cable is inserted all the way and you are in "FASTBOOT USB"
11. Make sure your recovery.img or whatever the name of the recovery is, is in the folder you are currently in
11. Type
Code:
fastboot flash boot boot.img
in the command window
You should see something like:
Code:
C:\Users\yourusername\Android\sdk\platform-tools>fastboot flash boot boot.img
sending 'boot' (12932 KB)...
OKAY [ 1.350s]
writing 'boot'...
OKAY [ 1.030s]
finished. total time: 2.385s
Your phone will still be in FASTBOOT USB mode
To test it out to see it was correctly flashed, reboot the phone
Go into Settings-About-Software information-More-Kernel version and see that the version changed
You can follow my little guide to use SD as Internal memory. Let me know if you need any help.
I won't be able to get to this til tomorrow but another issue is I can't d/l apps off Google play. It comes up with some server issue and some weird code that starts with an R. Sorry I can't give full details as I'm at work :/.
Okkvltist said:
I won't be able to get to this til tomorrow but another issue is I can't d/l apps off Google play. It comes up with some server issue and some weird code that starts with an R. Sorry I can't give full details as I'm at work :/.
Click to expand...
Click to collapse
Is your phone completely stock or do you have any custom ROMs? I have seen errors like that.
blaqueknight said:
Is your phone completely stock or do you have any custom ROMs? I have seen errors like that.
Click to expand...
Click to collapse
I'm fairly certain I reinstalled Busybox when I was installing(or trying to) Supersu. I'm giving the kernel bit a shot.
Oh the stock back-up is this(No, I didn't back up my phone since I didn't see a reason, I had everything I needed on the computer/sd) file:
http//qc-.androidfilehost-com/dl/PObYV5uN55P2PGDNrX1pLQ/1430391523/95832962473396445/2014-12-02--16-24-34+KOT49H+Stock.not.rooted.rar
(can't post links since i'm a newb)
Had to make a backup of my empty phone and put the files into the empty back up to restore it.
UPDATE- Flashed over Modded Kernel V2.6.1 since that looked like a safe bet. Installed correctly. Tried to reinstall Supersu. Got "Android is upgrading". Supersu Installed. Next is the SD Card bit.
Okkvltist said:
I'm fairly certain I reinstalled Busybox when I was installing(or trying to) Supersu. I'm giving the kernel bit a shot.
Oh the stock back-up is this(No, I didn't back up my phone since I didn't see a reason, I had everything I needed on the computer/sd) file:
http//qc-.androidfilehost-com/dl/PObYV5uN55P2PGDNrX1pLQ/1430391523/95832962473396445/2014-12-02--16-24-34+KOT49H+Stock.not.rooted.rar
(can't post links since i'm a newb)
Had to make a backup of my empty phone and put the files into the empty back up to restore it.
Click to expand...
Click to collapse
I'm sorry, please disregard that last comment. I was posting like your only problem was the Play Store. lol Sorry. But yea, check out those things I mentioned to you and you should be able to get SuperSU back up, if not I'll help you with anything else.
Okkvltist said:
I'm fairly certain I reinstalled Busybox when I was installing(or trying to) Supersu. I'm giving the kernel bit a shot.
Oh the stock back-up is this(No, I didn't back up my phone since I didn't see a reason, I had everything I needed on the computer/sd) file:
http//qc-.androidfilehost-com/dl/PObYV5uN55P2PGDNrX1pLQ/1430391523/95832962473396445/2014-12-02--16-24-34+KOT49H+Stock.not.rooted.rar
(can't post links since i'm a newb)
Had to make a backup of my empty phone and put the files into the empty back up to restore it.
UPDATE- Flashed over Modded Kernel V2.6.1 since that looked like a safe bet. Installed correctly. Tried to reinstall Supersu. Got "Android is upgrading". Supersu Installed. Next is the SD Card bit.
Click to expand...
Click to collapse
UPDATE 2- When partioning the sd card, it continues to come up as ext2. When I go into Link2SD and I go to select I get the message on whatever I select- "Mount script cannot be created. mount: invalid argument"
Okkvltist said:
UPDATE 2- When partioning the sd card, it continues to come up as ext2. When I go into Link2SD and I go to select I get the message on whatever I select- "Mount script cannot be created. mount: invalid argument"
Click to expand...
Click to collapse
Are you using Aparted? What was the method you used to partition? You should partition as ext4.
Yeah, I downloaded Aparted, went in to partition the SD card("8" gigs) and selected ext4 but it comes out ext2. Do I need S-OFF and/or 4EXT Recovery?
Okkvltist said:
Yeah, I downloaded Aparted, went in to partition the SD card("8" gigs) and selected ext4 but it comes out ext2. Do I need S-OFF and/or 4EXT Recovery?
Click to expand...
Click to collapse
Did you select Create then Format? If it still comes out ext2 after that, I don't know what the problem is. Format will take a while because it is creating journals.
blaqueknight said:
Did you select Create then Format? If it still comes out ext2 after that, I don't know what the problem is. Format will take a while because it is creating journals.
Click to expand...
Click to collapse
It's saying the partition doesn't exist when I go to format after creating the partition. Even when creating the proper ext from the create screen, it still doesn't come up as ext4.
other info
device- /dev/block/mmcblk1.
when I opened up link2sd its asking me for mmcblk1p2 but there is no mmcblk1p2
Okkvltist said:
It's saying the partition doesn't exist when I go to format after creating the partition. Even when creating the proper ext from the create screen, it still doesn't come up as ext4.
other info
device- /dev/block/mmcblk1.
when I opened up link2sd its asking me for mmcblk1p2 but there is no mmcblk1p2
Click to expand...
Click to collapse
Are you trying to partition the whole SDcard as ext4? To properly partition the card to be used with Link2SD you have to:
1. Delete the sdcard
2. Create a FAT32 partition of any size of your choosing
3. Format the FAT32 partition
4. Create an ext4 partition of any size of your choosing
5. Format the ext4 partition (this will take a long time, as it will create journals that are used to recover from an error such as removing the device while files are being copied)
After following those steps, Link2SD should properly create the script/mount and you should be able to link to your sdcard
If you are doing those steps perfectly and you still have an error, we have to find out another solution
Ok, I still can't get it to make Ext4......
However, weirdness- I made a Fat32 Partition and went into Link2SD. Link2SD was able to use/read the Fat32 partition. Tried to create/change the Fat32 and it didn't work. Tried to make a third partition under ext4 and it comes up ext2. Openned Link2SD and it doesn't read/use the ext2. Uses the additional Fat32 no sweat. I don't know how much of it is working(tried downloading Brave Frontier and had to delete loads of stuff in general) usual memory bull**** ensures and I see theres a lock for the full copy of Link2SD....
another thing; I can't get into/mount the open part of my SD card. Should I go back to square one or should I blow the meager 3 bucks for the full copy and see if I can do it from there?
PS- Does the class of the sd decide on if I can partition an ext3-4? Cause if so, mine is only a class 4 SD card.
Okkvltist said:
Ok, I still can't get it to make Ext4......
However, weirdness- I made a Fat32 Partition and went into Link2SD. Link2SD was able to use/read the Fat32 partition. Tried to create/change the Fat32 and it didn't work. Tried to make a third partition under ext4 and it comes up ext2. Openned Link2SD and it doesn't read/use the ext2. Uses the additional Fat32 no sweat. I don't know how much of it is working(tried downloading Brave Frontier and had to delete loads of stuff in general) usual memory bull**** ensures and I see theres a lock for the full copy of Link2SD....
another thing; I can't get into/mount the open part of my SD card. Should I go back to square one or should I blow the meager 3 bucks for the full copy and see if I can do it from there?
PS- Does the class of the sd decide on if I can partition an ext3-4? Cause if so, mine is only a class 4 SD card.
Click to expand...
Click to collapse
I just made a couple of very simple tutorials to use Aparted and Link2SD and they are both working for me. Check them out: Aparted tutorial, Link2SD tutorial. I believe the ext2 that you are talking about is around the 10 second mark in the Link2SD video. Do you mean the /data/sdext2? That is just the name of the second sdcard partition.
If you can, you should buy the full copy of Link2SD to link external data and whatever other options become available.
The class of sdcard shouldn't have anything to do with the partition. That's just a classification of the speed of the card.
If needed, I'll make more videos to show exactly how everything is done. I think sometimes it is better to show than simply explain how something is done.
Hope this helps.
Wow.......I mean seriously, holy zen, it worked.
I had to start over from scratch since my f'ling screwed so much crap up but after everything was reinstalled and flashed and what not, It made the ext4. I don't know why the programming is so touchy you have to create it threw such weird steps but I believe it worked. Upgraded the link2sd. Next question and I'm pretty sure on the answer- Are you able to remove the SD card or is it perma-bound to the phone(IE- if I change SD cards around, will everything crash?)? Thank you so much
Okkvltist said:
Wow.......I mean seriously, holy zen, it worked.
I had to start over from scratch since my f'ling screwed so much crap up but after everything was reinstalled and flashed and what not, It made the ext4. I don't know why the programming is so touchy you have to create it threw such weird steps but I believe it worked. Upgraded the link2sd. Next question and I'm pretty sure on the answer- Are you able to remove the SD card or is it perma-bound to the phone(IE- if I change SD cards around, will everything crash?)? Thank you so much
Click to expand...
Click to collapse
I'm happy it worked out good for you.
Yes, you are able to remove your sdcard. Be aware that your apps are on your sdcard so if you remove it, you remove them. They are placed on your sdcard and symlinked so Android thinks they are still on your phone in the place they would normally be. Nothing should crash, they just shouldn't show up. There is some great info about Link2SD here.
@blaqueknight..
nice videos man.