Related
I loaded jacheroskivr1.5 last night and everything was fine(even the leds were working) all of a sudden it cuts off, it takes a few minutes for it to come back on if at all, then it freezes so i wiped the phone now its bootloopin..
wtf happened and wtf do i do?
Did you re flash the rom after? Maybe try repartitioning your sd or atleast wiping your ext2/3.
I can't because im at work right now, but i don't understand what actually happened. It was working fine all day and then it just started cutting off on its own, not even resetting but just cutting off all together.
I don't think i should've wiped it..
so f'n tired of repartitioning my sd card casue with all the music/photos/vids its takes up to an hour for me to transfer it all back from my back up...
So repartition, and flash rom again.. got it.
Yea I have no idea why it went screwy on you but my guess to fix it would be wipe, repartition, then flash. Someone else here with more knowledge might know why it happened to begin with.
Coopaman said:
I loaded jacheroskivr1.5 last night and everything was fine(even the leds were working) all of a sudden it cuts off, it takes a few minutes for it to come back on if at all, then it freezes so i wiped the phone now its bootloopin..
wtf happened and wtf do i do?
Click to expand...
Click to collapse
Don't wipe on hero, ever. It will always give you a bootloop.
Here's what I do if I find myself in a bootloop.
Wipe the EXT2/3 partition from console
(press enter)
#
# mount -o rw /dev/block/mmcblk0p2 /system/sd
# rm -rf /system/sd/*
# reboot recovery
wipe in recovery
repair ext partitions (twice if the first time fails)
reflash.
Always fixes any problems I have.
OK.
So for the last week or two I've been trying to get myself fixed in this thread:
629469
You can read that for some background info. Seeing as this a new problem, I've posted a new thread.
I've pushed SuperD, signed-spl (danger) and ota-radio 2_22_19_26i to the phone.
But now I cant apply these updates. I choose "apply sdcard:choose zip"
and it says:
e:can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(Invalid Argument)
E:Can't mount SDCARD:
HELP.
Wave invites for help (I'll try that one again)
I've run into the same problem but I got there a slightly different way.
I recently switched ROMs from kingklick's aosp 2.1 v1.5 to openeclair 1.5, and I wanted to switch back. I went to do the usual partition, wipe everything, apply update.zip and I got almost exactly the same error message that you got:
E: can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0)
(File not found)
E: can't mount SDCARD:
With my limited knowledge of Unix, I decided to jump into the console and dig around in the dev folder, I didn't see anything in /dev/block that was called mmcblk0, there were several files called "loopX", and also "mtdblkX".
It seems like my phone is acting as though I do not have an SD card at all. I've been testing out different things, I started the process over again by trying to partition the SD card and noticed it finished almost instantly. And now when I connect it to the computer and turn on the USB connection, my computer does not recognize it as a storage device. I then popped out the SD card and put it into the computer itself, it seems fine but there were some extra dm files that I did not expect to see. Not sure what those files are or how they got there.
I have the Death SPL, and the last ROM I used was KingKlick's AOSP 2.1 v1.5
Does anyone out there have any idea why this happened or how I can fix it?
Both of you, it sounds like your sd card is formatted wrong or corrupt. From amon-ra recovery you should try to wipe again, including the SD, and repair SD EXT. If that doen't work go back and use the "format SD" option.
One more thing, please take a few minutes and put together a signature on the forum with all your info, phone, spl, rom, sd setup, what you like for breakfast, all that stuff. Much easier to tell where to start.
Edit...if this should happen to accidentally work, please don't send any wave invites. I will probably never get rid of my 25.
Wipe data - worked (supposedly)
Wipe dalvik - Error : Run 'wipe dalvik' via console!
Wipe SD:ext partition - Error : Run 'wipe ext' via console!
Repair SD:ext - Error : Run 'fs repair' via console!
I don't see an option for "Format SD" in Amon Ra's recovery v1.5.2, so I attempted to Partition SD and give 0 space to swap and ext2. That SAID it completed successfully, but it finished suspiciously fast, and upon inserting the SD into my computer, I can see that it was not re-partitioned nor wiped.
I went into the console and tried the commands mentioned in the error messages and got "No ext partition found!" from each command. I then went back to recovery to "partition" the SD with Swap - 192MB, Ext2 - 1024MB, Fat32 - remainder (approx 2.75GB). I then tried wiping and repairing again, and got the same error messages, then went back to console to try wiping from there, and again was told "No ext partition found!"
I noticed that my SD is class 4, but class 6 is recommended, I'm considering going to buy a new class 6 SD, do you think that will help?
Filled in my sig, did I miss any info?
dracoaffectus said:
Wipe data - worked (supposedly)
Wipe dalvik - Error : Run 'wipe dalvik' via console!
Wipe SD:ext partition - Error : Run 'wipe ext' via console!
Repair SD:ext - Error : Run 'fs repair' via console!
I don't see an option for "Format SD" in Amon Ra's recovery v1.5.2, so I attempted to Partition SD and give 0 space to swap and ext2. That SAID it completed successfully, but it finished suspiciously fast, and upon inserting the SD into my computer, I can see that it was not re-partitioned nor wiped.
I went into the console and tried the commands mentioned in the error messages and got "No ext partition found!" from each command. I then went back to recovery to "partition" the SD with Swap - 192MB, Ext2 - 1024MB, Fat32 - remainder (approx 2.75GB). I then tried wiping and repairing again, and got the same error messages, then went back to console to try wiping from there, and again was told "No ext partition found!"
I noticed that my SD is class 4, but class 6 is recommended, I'm considering going to buy a new class 6 SD, do you think that will help?
Filled in my sig, did I miss any info?
Click to expand...
Click to collapse
to format it, just go to partition, then select 0 for the first two and rest for fat 32. You don't need a new card unless you're running a hero rom, and a class 4 is actually pretty fast. If formatting it doesn't work its done. This happened to me on a brand new class 6 transcend. Sent it back and got a sandisk. Good luck
I have the same problem wiht my G1 and am sending back my phone to HTC for this.
I have made a post here:
http://forum.xda-developers.com/showthread.php?p=5594269
All our phones have activated a memory debugging mode from from hboot. Modifying anything while booted to recovery or system doesn't affect anything because the trigger is happening from hboot.
You can still use fastboot while stuck in this mode. But your phone has no sd card access at the moment because it is locked by the hboot for writing debug logs.
I found that I was not able to flash in fastboot, as my hboot showed S-ON. However it was still possible to use fastboot boot.
Run cat /proc/cmdline
You will see that it says something like the following:
board_trout.disable_uart3=1 board_trout.usb_h2w_sw=1 board_trout.disable_sdcard=1 smisize=64 androidboot.baseband=3.22.26.17 androidboot.cid=ROGER001 androidboot.carrier=Rogers androidboot.keycaps=qwerty androidboot.mode=normal androidboot.serialno=HT********** androidboot.bootloader=1.33.2005 no_console_suspend=1 con
sole=null
You could mount the cache partition to your sdcard directory for flashing files:
adb shell mount -t yaffs2 /dev/block/mtdblock4 /sdcard
I've had this problem for more than a week. I have tried changing SPL, unrooting, recompiling my boot.img, and appending kernel commands.
You can also force your recovery/system to mount the sdcard, but your phone will error out because both the hboot and system will try to write to the sdcard. There is a high chance of corrupting the sd card (correctable by reformatting) this way, but you can generate a gold card:
fastboot -c "board_trout.disable_uart3=0 board_trout.usb_h2w_sw=0 board_trout.disable_sdcard=0" boot recovery.img
The -c switch appends to the kernel cmdline at the end.
There is a working solution if you have SPL 1.76.x in your HBOOT. The command to disable memory debug logs is simply
fastboot oem enableqxdm 0
However I have never seen this SPL for the dream. 32B magic users who flashed this SPL with the accompanying radio ended with semi-bricks, with their SPLs showing 32A board. Attempts to downgrade back to 1.33.x have not worked. Here's the thread:
http://forum.xda-developers.com/showthread.php?t=625604
I did theorize that we might have been able to upgrade our spl and radio to 1.76.x, run the enableqxdm command, and then downgrade back to 1.33.2010 using the test ruu. The 1.33.2010 works for the 32A magic, the 32B magic and the dream. This is one of the variants of the so called danger spl. If you have 1.33.2005 you already have a spl from the magic.
hiddengopher said:
to format it, just go to partition, then select 0 for the first two and rest for fat 32. You don't need a new card unless you're running a hero rom, and a class 4 is actually pretty fast. If formatting it doesn't work its done. This happened to me on a brand new class 6 transcend. Sent it back and got a sandisk. Good luck
Click to expand...
Click to collapse
Ok, I tried that already and it didn't work. So you're saying the SD card is useless now and I just need to get a new one?
and Xaueious, I read your post and I have one question. What do you recommend I do?
dracoaffectus said:
Ok, I tried that already and it didn't work. So you're saying the SD card is useless now and I just need to get a new one?
and Xaueious, I read your post and I have one question. What do you recommend I do?
Click to expand...
Click to collapse
Try this first.
Enter recovery then console
1. type parted /dev/block/mmcblk0
2. type rm 2 to remove ext
3. type rm 3 to remove swap
to resize fat32:
4. type print to get start value and sdcard size
5. type resize 1 <start> <sdcard size> (if i were doing this for my card it would be resize 1 512B 8169M)
Then put the card in computer and format fat32. (just to be sure)
Put it back in the phone and recovery and partition.
If no other way works, the card may be corrupt.
You could use GPARTED in linux for this. Even a GPARTED live cd would be good. In fact that may be your best option.
billquinn1 said:
Try this first.
Enter recovery then console
1. type parted /dev/block/mmcblk0
2. type rm 2 to remove ext
3. type rm 3 to remove swap
to resize fat32:
4. type print to get start value and sdcard size
5. type resize 1 <start> <sdcard size> (if i were doing this for my card it would be resize 1 512B 8169M)
Then put the card in computer and format fat32. (just to be sure)
Put it back in the phone and recovery and partition.
If no other way works, the card may be corrupt.
You could use GPARTED in linux for this. Even a GPARTED live cd would be good. In fact that may be your best option.
Click to expand...
Click to collapse
also, you're going to want to go to "go to console" in recovery to do this
billquinn1 said:
Try this first.
Enter recovery then console
1. type parted /dev/block/mmcblk0
2. type rm 2 to remove ext
3. type rm 3 to remove swap
to resize fat32:
4. type print to get start value and sdcard size
5. type resize 1 <start> <sdcard size> (if i were doing this for my card it would be resize 1 512B 8169M)
Then put the card in computer and format fat32. (just to be sure)
Put it back in the phone and recovery and partition.
If no other way works, the card may be corrupt.
You could use GPARTED in linux for this. Even a GPARTED live cd would be good. In fact that may be your best option.
Click to expand...
Click to collapse
I went to console and typed "parted /dev/block/mmcblk0" and it said "Error: Could not stat device /dev/block/mmcblk0 - No such file or directory"
I tried "parted /dev/block/mtdblock0" instead and got into parted, but when I tried any command such as "print", I got "Error: /dev/block/mtdblock0: unrecognised disk label"
dracoaffectus said:
I went to console and typed "parted /dev/block/mmcblk0" and it said "Error: Could not stat device /dev/block/mmcblk0 - No such file or directory"
I tried "parted /dev/block/mtdblock0" instead and got into parted, but when I tried any command such as "print", I got "Error: /dev/block/mtdblock0: unrecognised disk label"
Click to expand...
Click to collapse
I would say the sd card is dead. Try someone else's or a spare.
Picked up a 2GB microSD at the store for like $10 and got the same results right from the beginning.
So this means it's something wrong with my phone, and not the SD card.
Any suggestions?
....can I unroot?
I don't know if this matters, but I noticed some dm files on my sdcards after trying to startup my phone.
EDIT: I managed to UNroot my phone back to RC29 following the instructions on theunlockr.com. Now I have to contemplate if I'm ready to jump straight back into hacking again.
EDIT2: Ok, so now I'm back on the latest OpenEclair. The key to "fixing" it was to get a totally clean start by UNrooting my phone (http://bit.ly/5qbzIU thanks Unlockr.com). I wasn't able to do step 1 cause I was getting the same errors as before, so I skipped straight to loading the DreaIMG.nbh file, then continued to update to cupcake, load the latest radio, danger SPL, and openEclair, now my phone is working again. (p.s. already on Wave, so no need to send that invite Lachy95 )
Thanks
Its all fixed.
Used a different sd card, im stupid.
Thanks you thank you thank you
ill always remember
I noticed more people are having same issue as me and I wanted to create a thread to find the solution.
I was running CM7 RC4 / OC 40311 - It was running fine and one day system hung and so I rebooted and that was it.
Symptom :
System boots and pass the "Touch the future Reading" and displays "ANDROID _" on the bottom of the screen and after 10-15 sec it reboots and loop this process.
Things I tried so far :
CWR 3.0.0.5
- Repratition to stock nook.
- Getting error when I try to format system and data - I thought it was because CM7 was setting system to ext4.
- ADB and DD boot.img, System.img and copy Factory to mmcblk0p3
- Try to restore from back up I made
- Nothing works but goes back to boot loop
CWR 3.0.0.6 - One I got from CM7 install to emmc thread
- System format works
- Install latest nightly
- Restore from back up
- ADB can't find device - This is odd and couldn't find a way to fix it yet.
- Tried to install Stock zip but going back to CM7 boot loop
CWR 3.0.1.0
- Can't format data/system
- ADB to delete partitions and create them again but it doesn't help
- Tried all zip files to bring it back to stock - no go
- ADB to copy Factory.zip to emmc partition - umount and mount again then file I copied is gone.
- Deleted partitions and reboot but some how I got back to CM7 loop
If you are having same issue please post and share your experiences so we can find the solution!!!
tuxhacker said:
Symptom :
System boots and pass the "Touch the future Reading" and displays "ANDROID _" on the bottom of the screen and after 10-15 sec it reboots and loop this process.
Click to expand...
Click to collapse
This means the kernel is loading, and most likely the init.encore.rc is running as well. Have you tried grabbing a log from adb logcat? Or perhaps checking if the shell works?
tuxhacker said:
Things I tried so far :
CWR 3.0.0.5
- Repratition to stock nook.
Click to expand...
Click to collapse
How are you repartitioning?
tuxhacker said:
- Getting error when I try to format system and data - I thought it was because CM7 was setting system to ext4.
Click to expand...
Click to collapse
What is the error?
tuxhacker said:
CWR 3.0.1.0
- Can't format data/system
Click to expand...
Click to collapse
Again- if its getting an error, what is that error? Have you tried formatting manually?
tuxhacker said:
- ADB to delete partitions and create them again but it doesn't help
Click to expand...
Click to collapse
Errors? Logs?
You have to be more specific.
- I was flashing "repartition-boot-with-stock.zip" also tried to delete the partitions using fdisk - from adb shell
- And I was getting "Error formatting / system!" and "Error formatting /Data!" from CWR format system and format data
I also tried to format it manually using "mke2fs /dev/block/mmcblk0p1,2 and 3..."
And could you please tell me how to get the log?
Thank you.
have you tried booting off an cwr 3.0.1.0 bootable sd card and formatting reinstalling?
john10101 said:
have you tried booting off an cwr 3.0.1.0 bootable sd card and formatting reinstalling?
Click to expand...
Click to collapse
Yes I have. I tried several times. It seems like my nook is a read only device now. It won't take any changes.
tuxhacker said:
Yes I have. I tried several times. It seems like my nook is a read only device now. It won't take any changes.
Click to expand...
Click to collapse
unpossible!
chisleu said:
unpossible!
Click to expand...
Click to collapse
Here's one example. I did this from CWR 3.0.1.0.
- Mount mmcblk0p3 to emmc
- Copied factory.zip to emmc
- ls -l /emmc to check the new file
- umount /emmc
- Mount /emmc again
- ls -l as you can see old file date again.
Code:
~ # mount -w /dev/block/mmcblk0p3 /emmc
mount -w /dev/block/mmcblk0p3 /emmc
~ # mount
mount
/dev/block/mmcblk0p3 on /emmc type ext2 (rw,errors=continue)
~ # exit
C:\Program Files\Android\android-sdk\platform-tools>adb push factory.zip /emmc
3779 KB/s (168335604 bytes in 43.492s)
C:\Program Files\Android\android-sdk\platform-tools>adb shell
~ # ls -l /emmc
ls -l /emmc
-rw-rw-rw- 1 root root 168335604 Apr 17 04:06 factory.zip
drwx------ 2 root root 12288 Oct 23 05:27 lost+found
-rw-rw-rw- 1 root root 2567 Nov 17 22:27 rombackup.zip
~ # umount /emmc
umount /emmc
~ # mount /dev/block/mmcblk0p3 /emmc
mount /dev/block/mmcblk0p3 /emmc
~ # ls -l emmc
ls -l emmc
-rwxrwxrwx 1 root root 168332495 Nov 11 23:35 factory.zip
drwx------ 2 root root 12288 Oct 23 05:27 lost+found
-rw-rw-rw- 1 root root 2567 Nov 17 22:27 rombackup.zip
~ #
May I ask why you had to mess around with the partitions at all?
lechiffre said:
May I ask why you had to mess around with the partitions at all?
Click to expand...
Click to collapse
It was keep rebooting itself so I was trying to reflash CM7 but didn't work. Next I was going back to stock to start over and that didn't work. Found one thread about DD boot.img, system.img and factory.zip to mmcblk0p3 then 8 failed attempt to restore to stock. etc...
I'm sure that while I was trying to fix I made more mess.
I did adb logcat and got the permission denied error.
Code:
C:\Program Files\Android\android-sdk\platform-tools>adb logcat
- waiting for device -
- exec '/system/bin/sh' failed: Permission denied (13) -
Did you try going into clockwork recovery and using the fix permissions option?
tuxhacker said:
It was keep rebooting itself so I was trying to reflash CM7 but didn't work. Next I was going back to stock to start over and that didn't work. Found one thread about DD boot.img, system.img and factory.zip to mmcblk0p3 then 8 failed attempt to restore to stock. etc...
I'm sure that while I was trying to fix I made more mess.
Click to expand...
Click to collapse
I still don't get why you decided the partitions were faulty.
This might not help you now but might help others in you situation. IMO the process should be when you encounter bootlooping:
1. Reflash current OS using CWR 3.1.0 uSD.
2. If Step 1 fails, using CWR 3.1.0 uSD: format /system /data /cache. Attempt to install CM7. If CM7 install fails, attempt to install stock.
3. ***Requires a a working CWR backup which should contain your original boot partition***
If Step 2 fails, using CWR 3.1.0 uSD: format /system /data /cache and /boot. Restore stock /boot partition only via advanced restore. Attempt to install CM7 or stock.
4. ONLY if the previous steps fail should you even touch any partition tool. I've never had to use any, but I've never messed with the partitions in the first place (ie double booting off eMMC).
Just wanted to share that getting stuck on the boot screen may not have anything todo with what or how you've flashed.
On a fresh install/flash of CM7 I can reboot just fine as many times as I want. As soon as I restore all my apps and reboot I get stuck on the boot screen.
So SOMETHING amongst all the apps I have backed up gets me stuck on the boot screen. Really don't want to go through a reboot for each app one at a time though
FIXED - wipe battery status in CWM
This problem seems to occur when the battery runs out, Nook is plugged in and then it hangs at "the future..."
So to fix this problem, boot into CWM (using CWM for SD) and go to Advanced-Recovery and Wipe Battery Status. Remove the CWM SD and go back to the root menu and reboot.
Your CM7 would boot now just fine. I don;t know what the problem is yet, but that seems to fix it. It saved me from reinstall.
the Nook gets into this state only when the battery is completely drained.
TuxHacker, did you ever resolve your issue of what seems to be the internal memory being in a write-protected state? I'm in the exact same boat you are but instead of CM7 I got CWR 3.0.0.5 installed on my boot and brianf's custom froyo installed.
I agree it seems like the device is now write protected as I've mounted boot/system/media and deleted everything in there, ls'd to double check, but once I remount, all the old stuff is back there again.
I also tried using samuelhalff's NookUMC app to mount all the partitions in windows, deleted everything, and upon remount, all the files are back. The NookUMC app was the one I initially used to copy a bunch of mp3's and vids to the media partition in the first place and now this partition behaves as if it was write-protected as well.
lechiffre said:
I still don't get why you decided the partitions were faulty.
This might not help you now but might help others in you situation. IMO the process should be when you encounter bootlooping:
1. Reflash current OS using CWR 3.1.0 uSD.
2. If Step 1 fails, using CWR 3.1.0 uSD: format /system /data /cache. Attempt to install CM7. If CM7 install fails, attempt to install stock.
3. ***Requires a a working CWR backup which should contain your original boot partition***
If Step 2 fails, using CWR 3.1.0 uSD: format /system /data /cache and /boot. Restore stock /boot partition only via advanced restore. Attempt to install CM7 or stock.
4. ONLY if the previous steps fail should you even touch any partition tool. I've never had to use any, but I've never messed with the partitions in the first place (ie double booting off eMMC).
Click to expand...
Click to collapse
I can't speak for TuxHacker, but mucking around with the partitions seems to be a last ditch effort to at least *change* anything on the device. I've followed a few guides on here about showing the partition table and mine matches a stock partition table. I haven't gotten around to actually modifying any of the partitions yet though...
In all of your steps, the first sub-step is to format one or all of /system /data /cache /boot. This is precisely the step that fails for us with "Error Formatting /system!" or any of the others The only CWR that it doesn't fail on is CWR 3.0.0.6, but any flashes don't take, the NC just reverts back to what it was just before the system decided to go read-only.
I'm running off SD now but that is a pretty crappy experience... if anyone can fix the mess we got ourselves into I will def buy that guy a cold one!
drazil22 said:
In all of your steps, the first sub-step is to format one or all of /system /data /cache /boot. This is precisely the step that fails for us with "Error Formatting /system!" or any of the others The only CWR that it doesn't fail on is CWR 3.0.0.6, but any flashes don't take, the NC just reverts back to what it was just before the system decided to go read-only.
I'm running off SD now but that is a pretty crappy experience... if anyone can fix the mess we got ourselves into I will def buy that guy a cold one!
Click to expand...
Click to collapse
Yes. And on CWR 3.0.0.6 I can't connect via ADB so can't do much with it. On CWR 3.0.1.0 and CWR 3.0.0.5 I can connect via ADB but can't format. I tried all the ADB connect tips and tricks but no go.
I think it coubd be a permission issue since I get - exec '/system/bin/sh' failed: Permission denied (13) - when I tried ABD logcat while its rebooting.
I'm also running off SD now and it is really bad.
I'm in the same boat as you guys and I just wanted to add my two cents.
I've tried multiple times to use the partitioning tools that drazil22 is talking about, but every time I reboot, the partitions come back. What is weird is that while I'm still in adb, after I've written the partition table back to the device, is that it shows the new partition table when I tell it to print it out. I can exit all the way out of adb and, unless I've rebooted my nook, the partitions are back to the way they were. However, once I reboot my nook, the partitions come back...
I've gone as far as deleting every single partition and then rebooting just so that I could have a brick to take back to B&N, but the stupid partitions keep coming back...
lol that's what I was thinking too... brick the thing and get the store to reflash it, as someone else with a bricked nook did. I think the store must have another utility or device to reflash it back to stock.
The weird thing is any changes I make stay for the session until I unmount. I tried to copy the system.img and boot.img which is a little over 500MB to the /media partition (mmcblk0p8) but because I filled it with mp3's and videos, only about 200MB was free and of course the adb push errored out saying not enough space. I then navigated to the /media partition, deleted a bunch of videos and was able to adb push the two files over. I was also able to run the dd commands and got the expected results. Upon reboot, of course nothing got dd'd, the two .img files I copied to /media were gone, and the videos I deleted to free up space were back!
I was also hoping that with the new B&N update to 1.20, they might have released a flashing utility but I guess that was wishful thinking...
Edit: one other peculiar thing I noticed is that when I use adb when booted into CM7 (using the SD), it shows the serial number as 11223344556677. When I use adb booted up using the CWR on my boot partition, or with a bootable SD, it shows the actual serial number written on the sticker behind the sd cover.
getllamasfast said:
I'm in the same boat as you guys and I just wanted to add my two cents.
I've tried multiple times to use the partitioning tools that drazil22 is talking about, but every time I reboot, the partitions come back. What is weird is that while I'm still in adb, after I've written the partition table back to the device, is that it shows the new partition table when I tell it to print it out. I can exit all the way out of adb and, unless I've rebooted my nook, the partitions are back to the way they were. However, once I reboot my nook, the partitions come back...
I've gone as far as deleting every single partition and then rebooting just so that I could have a brick to take back to B&N, but the stupid partitions keep coming back...
Click to expand...
Click to collapse
This is odd, but I dont think this is limited to CM7 as I've seen it happen with different phones running AOSP. Over on the Evo there was numerous accounts of peoples devices suddenly rebooting and then getting stuck in a bootloop, all partitions seemed to be corrupted including the recovery partition and there was absolutely no way to write to the system anymore. Complete booting brick. No one was able to find the cause and no one was able to find a fix.
RileyGrant said:
This is odd, but I dont think this is limited to CM7 as I've seen it happen with different phones running AOSP. Over on the Evo there was numerous accounts of peoples devices suddenly rebooting and then getting stuck in a bootloop, all partitions seemed to be corrupted including the recovery partition and there was absolutely no way to write to the system anymore. Complete booting brick. No one was able to find the cause and no one was able to find a fix.
Click to expand...
Click to collapse
I really hope this isn't true...
On an unrelated note: Do you think that B&N would notice if I microwaved my nook for a few seconds?
Hi all,
Tearing my hair out here (and I have SFA left anyway)
My Father-in-law's SGS i9000 seems to have real issues. Initially problem I was having was that there was an app I could not uninstall- it would reappear on reboot. I initially suspected malware or such, but it appears to be a real problem with the internal memory. I had MIUI installed on it, but wanted to change to a more stock ROM.
First time I really started to worry was when I found that every time I put a new rom onto the internal sdcard, it disappeared at reboot (and thus wasn't there to install when rebooted into CWM)
Since then, haven't had a functioning phone.
adb push to sdcard still not persistent on reboot.
Cannot flash new ROM with ODIN either, although KERNEL changes, filesystem no longer mounts.
I think the version of MIUI I was using used an ext4 lagfix, as inside an adb shell, I can see the partitions:
parted /dev/block/mmcblk0
a "print" lists two partitions:
Number Start End Size Type File system Flags
1 32.8kB 14.4GB 14.4GB primary fat32 lba
2 14.4GB 16.4GB 2013MB primary ext4 lba
rm 1, rm 2
to try to delete the partitions and start again- doesn't work. Nothing happens
If I load partition 2 into parted:
parted /dev/block/mmcblk0p2
print
Model: Unknown (unknown)
Disk /dev/block/mmcblk0p2: 2013MB
Sector size (logical/physical): 512B/512B
Partition Table: loop
Number Start End Size File system Flags
1 0.00B 2013MB 2013MB ext4
Can;t check any partitions as ext4 isn't supported by parted.
I cannot remove any partitions, reformat them or anything.
e2fsck errors as it cant read superblock flags on any of the partitions.
Any other ideas? Anyone?
I don't want to toss the phone out
http://forum.xda-developers.com/showthread.php?t=845708
i dont know if this will help u but u can try this guy instruction. See link above
compacity said:
http://forum.xda-developers.com/showthread.php?t=845708
i don't know if this will help u but u can try this guy instruction. See link above
Click to expand...
Click to collapse
If that worked, it would have been just what I was looking for
I googled the hell out of this problem, and that one never came up, but others I'd seen led me to try that same plan.
Where it fails on my device, is that deleting the partitions in "parted" fails- rm1 followed by rm 2 to delete the partitions. "Print" reveals they're still there.
Any other partition tools worth trying?
I got it back to square one:
Flashed kernel thru Odin with a version of CWM that worked.
reboot into recovery.
Flash update from SDcard- card contents still the same, so could re-flash MIUI.
reboot, bootloop. Re-enter CWM recovery and reflash.
Back to Square One - MIUI 1.12.16 (JVK)
Cannot install anything - nothing is persistent after reboot, even WIFI settings disappear
If it is any help to anyone who knows what they're talking about:
Now that MIUI boots I can look at the filesystem better.
Can anyone point me in the direction of what I should be looking for/trying to do to figure out what is wrong here?
try finding solution here, its PIT stop for i9000 problem
http://forum.xda-developers.com/showpost.php?p=30415128&postcount=1
Mine seems to be a bit tougher than these solutions can deal with.
Tried assorted ROMs over past day. No install works.
Cannot install anything from internal memory, as nothing dropped into that card will remain after a reboot.
Installing anything from an external card just throws up bootloops etc- as the only thing that seems to be able to retained between boots is the kernel/CWM.
If I install a new ROM, first flash says partition table is incompatible and /data will be overwritten (no problems, nothing on it). I accept the inevitable and re-select the ROM.
Reboot bootloops, as expected, reboot into CWM (now a new version with the Kernel), try reflashing the ROM image- Error 0 or 7. Try from External Memory- same. Try sideloading image. Same. All I can do is re-flash the MIUI image on internal SDcard (which works)
It looks like the internal memory refreshes itself from a recovery image at each boot? (I think).
Anyway- can't get anything to stick, except MIUI
edit:
http://forum.xda-developers.com/showthread.php?t=761537&page=3
http://forum.xda-developers.com/showthread.php?t=1230059&page=3
hav u try this 2 link as this is da only thread matches ur MBR problem
compacity said:
did u try any jb kernel out there? as its also ext4 n push it using adb. juz a suggestion though.
Click to expand...
Click to collapse
Good suggestion Logical
I'd thought that also- The JB kernels should support ext4.
No joy though
The version of CWM recovery that is stable with the MIUI install is 5.0.2.7, and it doesn't have any voodoo/lagfix options
When I flash a kernel with a CWM with lagfix, and try to use the CWM lagfix toggles, nothing changes.
Doesn't matter what I select inside CWM, it reads the status from memory as "Lagfix on, Debug off"
The reason I asked about ext4 tools in ADB is that running filesystem commands in a shell just throws up errors I can't seem to fix.
e2fsck just throws up superblock errors (on both /dev/block/mmcblk0 and the partition /dev/block/mmc0p2.
Defining one of the backup superblocks doesn't help- they're all bad.
"parted" doesn't work anymore (i note it isn't in /sbin, so I am picking this kernel doesn't install it), but even when I did have it, "parted" doesn't support ext4. Using "rm" to remove a partition did exactly nothing.
Starting to think the only way forward would possibly be flashing a custom .pit file to define partitions that move the data off an obviously bad block? Above my skill level however LOL
refresh browser see my post above again
I have a problem with my phone. I'm using one of unofficial roms but it's not its fault since i went back to the original rom and the same thing happens. Basically whenever I'm trying to access internal memory, usually through file manager or even using windows my phone crashes and restarts. After opening file manager, it freezes for 2-3 secs and restarts. Surprisingly I can open for example quickpic and browse my photos, the same with music in poweramp. Could it be that my memory is damaged. Should I format it from recovery? Thanks in advance
ma_ko said:
I have a problem with my phone. I'm using one of unofficial roms but it's not its fault since i went back to the original rom and the same thing happens. Basically whenever I'm trying to access internal memory, usually through file manager or even using windows my phone crashes and restarts. After opening file manager, it freezes for 2-3 secs and restarts. Surprisingly I can open for example quickpic and browse my photos, the same with music in poweramp. Could it be that my memory is damaged. Should I format it from recovery? Thanks in advance
Click to expand...
Click to collapse
Try e2fsck in recovery first. Boot to recovery go to mount options and make sure all partitions are unmounted, and connect your usb cable. Check adb is working with
Code:
adb devices
if you get the expected output follow up with
Code:
adb shell
e2fsck dev/block/mmcblk0p35
e2fsck dev/block/mmcblk0p36
e2fsck dev/block/mmcblk0p37
exit
Reboot and see if it still restarts when trying to access storage. If the problem remains it's worth trying "Format Data" in TWRP Recovery. Be warned this will format the entire device including any installed Rom. So make sure you have a Rom or backup to push/copy to the device afterwards. Also after the format you must reboot recovery to rebuild the partitions or you will get "failed to mount" errors :good:
Seems like formatting data from TWRP menu did the job. Thank you very much.