OK, so I accidentaly formatted the entire internal SD from within ClockworkMod recovery. Now i tried to reflash the stock ROM with Odin, and the phone just goes into a bootloop. I have a copy of what was on there, including EFS backups (about 8 of them), so I hope i can recover from this.
I read something that said I should do a flash with 'Re-partition' which i am trying now, and it seems to be taking forever. Should i just let it continue? or is there another method i should try to recover from this?
BOOT LOOP
http://forum.xda-developers.com/showthread.php?t=1108499
jje
I don't really think this is going to help in this situation. My internal storage is blank, gone, not partitioned. That's why i am getting the bootloop. I need to know how to get my stock partitions back, etc. I will try what is recommended though.
schwags said:
I don't really think this is going to help in this situation. My internal storage is blank, gone, not partitioned. That's why i am getting the bootloop. I need to know how to get my stock partitions back, etc. I will try what is recommended though.
Click to expand...
Click to collapse
Damn, ok, my appologies. I guess I should've tried this first, worked great. Phone seems OK now. Thanks for taking a minute to point me in the right direction!
Related
Hi guys,
I made a huge mistake that I hope there is a way out of. I have been reading everything before I did it, and made a mistake.
I thought in clockworkrecovery, when I selected partition sd, it was partitioning external sd so that I could save image to it. Obviously seems to have formatted the internal sd and now phone boots but after logo, get black screen.
Is there anyway to undo the internal partitioning? I can't get my phone booted up.
Reason for all this is clockworkrecovery backup was only backing up to internal sd, but I wanted to backup to external sd which it wasn't recognizing. So partitioning screwed it all up.
I hope there is a way out.
Anyone pls? Thx.
dpoliteski said:
Hi guys,
I made a huge mistake that I hope there is a way out of. I have been reading everything before I did it, and made a mistake.
I thought in clockworkrecovery, when I selected partition sd, it was partitioning external sd so that I could save image to it. Obviously seems to have formatted the internal sd and now phone boots but after logo, get black screen.
Is there anyway to undo the internal partitioning? I can't get my phone booted up.
Reason for all this is clockworkrecovery backup was only backing up to internal sd, but I wanted to backup to external sd which it wasn't recognizing. So partitioning screwed it all up.
I hope there is a way out.
Anyone pls? Thx.
Click to expand...
Click to collapse
Search the thread for how to odin. Look for the stickies. All u need is to use odin
Sent from the helm of Vibrant Territory!
Should I select re-partition in ODIN, even though the directions say not to? Reason being that I messed it up by creating a partition on the internal sd
dpoliteski said:
Should I select re-partition in ODIN, even though the directions say not to? Reason being that I messed it up by creating a partition on the internal sd
Click to expand...
Click to collapse
Yes, click re-partition.
Alright so here's the backstory. I bought a Vibrant off of ebay that was stuck in a bootloop. I thought to myself, hey I could just shove this thing into download mode and be on my merry way!
Well, I attempted to flash JFD with a jig that I had. Went fine, Odin gave it a PASS.
Still boot looped.
So I then try Eugene's no brick, and after finally getting the right version, it booted up. Then tried to flash to JFD again.
No dice.
Following the directions here I was able to finally get 2.1 to boot, now here is the problem that I'm currently stuck on.
I can't get the internal sd (onboard flash) to mount in the system. If I am at the shell I can browse to /mnt/sdcard and see everything on the phone and on the sd (external_sd).
But when I go into the settings, all I see is space unavailable and the format is grayed out.
The culprit I believe lies in the partition on the internal memory that creates this MBR checksum error every recovery.
Thoughts? Opinions? I know this can be fixed, I've come this far!
Below I've attached some of the voodoo logs, it seems that when trying to make the ext4 partitions, it can't find it. (I was trying this so I could in the end disable it)
Does anyone know what might be going on? Any tips at all?
The only thing that I can figure now is that there might be damage or the internal storage. When looking in /dev/block, there is no reference to mmc anything, like the internal storage isn't even there. Is the flash chip soldered on the motherboard? I'm guessif that it is, which means it would be a difficult fix.
Only other "solution" that I could thing of is if I mod the fstab to mount a microsd as the internal storage. Would this mod be affected by a flashing rom or odining back to stock?
Also is this the right board for this? If not can anyone direct me to the best spot to ask this question?
Thanks a bunch!
Please find my guide on the developers thread and follow it,
You will be bak at no sweat.
Any problems post there.
for this fix, you will need to have a CWM sdcard ready and waiting followed by and drivers properly installed for your tablet.
YOU MUST have CWM running from sdcard to fix this issue. Otherwise nothing will happen.
instructions to install to sdcard are here (I suggest using windows)
Needed files for download:
just download this zip and run the script while booted into cwm from sdcard.
download it here.
Instructions: Boot from sd (don't worry, it will work), ensure sdcard is mounted, and then you just run the fix.bat from the computer after extracting.
Credits: Succulent for the xloader image
Fattire for the idea that it might have formatted mmcblk0p1 (which it dead instead of mmc1)
You're welcome.
Might want to add that the cause of the "brick" appears to be that CM7 is confusing mmc1 and mmc0 and instead of wiping the first partition of the SD card, it's presumably wiping the first partition of the emmc, which contains the x-loader.
I already have said it.
Ah okay... well glad everything is fixed now.
fattire said:
You're welcome.
Might want to add that the cause of the "brick" appears to be that CM7 is confusing mmc1 and mmc0 and instead of wiping the first partition of the SD card, it's presumably wiping the first partition of the emmc, which contains the x-loader.
Click to expand...
Click to collapse
Bowing head in shame here...... Rookie mistake!
Looks like we have to make a bit of a tweak to the system then do some testing.
New download link due to a small scripting error.
Need help
Hi Indirect. I see that you have fixed your NT. I did not use sd i did install cm7 internally but i did format all the mounts . And now it just restarts in CWM. What should i do. Any idea please
Well guys, I'm still having problems. I ran the brick fix before you updated it - didn't work. I then re-ran after you updated it - still didn't work. It'll boot to CWM from SD, but won't boot to any ROM. Tried re-installing CM7 (didn't work), then I tried the Nook141root.zip which supposedly installs the BN 1.4.1 from CWM (also didn't work). Tried re-running the brick fix a handful of times after and before installing each ROM with no luck. Then I tried running it without installing a ROM. Tried the brick fix then I tried the BN 1.4.0 restore file. I tried on multiple freshly formatted SD cards and I even tried on a computer I was working on with a fresh install of Win7 with a fresh install of the drivers just to rule that out.
Before all this I had CWM and CM7 installed internally - if that makes a difference. Ideas?
Edit: More info. When trying to wipe data/factory reset in CWM I get the errror "E:format_volume: make_ext4fs failed on /dev/block/mmcblk1p2"...this occurs right after rebooting from the brick fix.
Edit 2: More info yet...in the brick fix I'm getting the text "error: device not found" twice right after entering "y" then again a handful of times later. Is there anything special I have to do in CWM to get it to detect it? I have sdcard mounted...
Im geting this and then my nt restarts by itself and then im back in cwm again so nothing is fixed.
Fatos said:
Im geting this and then my nt restarts by itself and then im back in cwm again so nothing is fixed.
Click to expand...
Click to collapse
What do you have mounted to get it the fix to detect the tablet? Does it matter?
scsione889 said:
What do you have mounted to get it the fix to detect the tablet? Does it matter?
Click to expand...
Click to collapse
Actually with mine it does not matter . I get till the step y or n without mounting nothing. Than i mount the sd card and press y and enter.
Than as u can see does try to write something and than my nook does reboot .
And the ending is the same. So no progress so far.
Fatos said:
Actually with mine it does not matter . I get till the step y or n without mounting nothing. Than i mount the sd card and press y and enter.
Than as u can see does try to write something and than my nook does reboot .
And the ending is the same. So no progress so far.
Click to expand...
Click to collapse
Were you running from internal or SD when it bricked?
Does it boot to CWM on it's own without an sd in the slot? If it does have you tried restoring/flashing a backup?
Reason I say about the backup is I just bricked my own systems on purpose when running from sdcard, it kept gpoing back to CWM after the xloader was returned to it. Restored an original backup and all is well again
CelticWebSolutions said:
Were you running from internal or SD when it bricked?
Does it boot to CWM on it's own without an sd in the slot? If it does have you tried restoring/flashing a backup?
Reason I say about the backup is I just bricked my own systems on purpose when running from sdcard, it kept gpoing back to CWM after the xloader was returned to it. Restored an original backup and all is well again
Click to expand...
Click to collapse
Yes i have had it internally.Not in an sd.
Yes mine doew boot to CWM on its own without and sd in slot. And yes i have tried restoring to re flash back up. Cause i have installed CM7 once and it did run well. But than after installing some programs became slow so i wanted to redo it again. And than i did format all: bootdata, cache, emmc, rom, system,sd-ext.
And then i installet cm7 again and all the installing went well againg . But it just want start cause is missing something in one of the mounts. So what i think is only needed if ill be able to restore the data that is in all those small partitions like emmc. I know that bootdata,and cached gets backed up but i dont know if the orthers are backed up or not.
Thanks for trying to help.
Edit: I have to go to university now. But if it would make it easier for you to help, I can shot a video afterwards with all the steps what i have done and how is my nook behaving now.Just let me know .
Edit1: I did try to restore to stock or update to 1.4.1 but it tells me MD5 mismatch.
Is it possible that i can push in with adb the files that are in the boot data, eMMc and other mounts i mean one by one.
I was running internal when it bricked. Only boots to cwm from SD now.
Sent from my Incredible 2 using XDA App
Fatos said:
Yes i have had it internally.Not in an sd.
Yes mine doew boot to CWM on its own without and sd in slot. And yes i have tried restoring to re flash back up. Cause i have installed CM7 once and it did run well. But than after installing some programs became slow so i wanted to redo it again. And than i did format all: bootdata, cache, emmc, rom, system,sd-ext.
And then i installet cm7 again and all the installing went well againg . But it just want start cause is missing something in one of the mounts. So what i think is only needed if ill be able to restore the data that is in all those small partitions like emmc. I know that bootdata,and cached gets backed up but i dont know if the orthers are backed up or not.
Thanks for trying to help.
Edit: I have to go to university now. But if it would make it easier for you to help, I can shot a video afterwards with all the steps what i have done and how is my nook behaving now.Just let me know .
Edit1: I did try to restore to stock or update to 1.4.1 but it tells me MD5 mismatch.
Is it possible that i can push in with adb the files that are in the boot data, eMMc and other mounts i mean one by one.
Click to expand...
Click to collapse
I'm in the same boat...I think when we did a format of the rom partition, we lost some data that was not backed up...That being said I have done a lot of reading and I think all hope is not lost.
We did not format the "factory" partition which from what I have been reading may contain a backup of the "rom" and other partitions.
I wonder if it is possible to pull the data from the factory partition, extract the data that we need and then push the appropriate files back to where they belong? It's way beyond my expertise, although I do have ADB working and I think if someone could point us in the right direction, it wouldn't be that difficult...I could be completely off base though...Good Luck and If I make any progress I'll make sure I pass the info along.
Need help!
I got the bloody ADB issue.... I was able to boot to CWM from SD card, and it's mounted. BUT! Adb devices gives me nothing, no device. I did all the troubleshooting of the driver, i got the "Android composite ADB interface" device but still no adb device appearing. Please help! My only idea if this fix can be incorporated into a flashable zip. May be there is some other way?
Thanks.
ElectroMike said:
I got the bloody ADB issue.... I was able to boot to CWM from SD card, and it's mounted. BUT! Adb devices gives me nothing, no device. I did all the troubleshooting of the driver, i got the "Android composite ADB interface" device but still no adb device appearing. Please help! My only idea if this fix can be incorporated into a flashable zip. May be there is some other way?
Thanks.
Click to expand...
Click to collapse
That's exactly what I've got. I'm going to spend a little time on fixing that up today. ADB just won't work through CWM for me.
ElectroMike said:
I got the bloody ADB issue.... I was able to boot to CWM from SD card, and it's mounted. BUT! Adb devices gives me nothing, no device. I did all the troubleshooting of the driver, i got the "Android composite ADB interface" device but still no adb device appearing. Please help! My only idea if this fix can be incorporated into a flashable zip. May be there is some other way?
Thanks.
Click to expand...
Click to collapse
I had thought about a flashable zip. I will look shortly and build one
I tried repartitioning my nook and it really bricked it now. It won't boot from SD. Tried a different card and fresh download of CWM. I think it's totally borked.
Edit for clarification: repartitioned from within CWM on SD
Edit2: Tried a 3rd card (first 2 were 32gb, 3rd was 16gb) and it let me back into CWM. ADB still isn't working though.
Edit2 clarification: I only say ADB isn't working because the brick fix says device not found. If I'm wrong please feel free to correct me.
scsione889 said:
I tried repartitioning my nook and it really bricked it now. It won't boot from SD. Tried a different card and fresh download of CWM. I think it's totally borked.
Edit for clarification: repartitioned from within CWM on SD
Edit2: Tried a 3rd card (first 2 were 32gb, 3rd was 16gb) and it let me back into CWM. ADB still isn't working though.
Edit2 clarification: I only say ADB isn't working because the brick fix says device not found. If I'm wrong please feel free to correct me.
Click to expand...
Click to collapse
Mne does not say that but it restarts my nook. But it does not fix it. I think its just some small starting files missing. But im not so good so i cant help it. So im just sitting and watching around internet if there is any fix. It looks that they have had the same problem with NC to start with to.
Edit: I think i fixed it by "cleaning" with diskpart and using an sd card to copy a rom and flash it, then booting up android and letting it format the internal storage. Will report back if any problems occur! Check post # 6 on this page for the solution. Also, sorry for the erratic writing, it's 4:55AM here and i need to be up at 9AM!
AtrICS rom did a random reboot and was saying something about encryption failed. Strange, i've never used that setting (i don't even have a screen lock). I rebooted the phone and it wouldn't get to the ROM, so i went into recovery and tried restoring a backup. After a few seconds it aborted. Strange. I mounted usb so i could copy a fresh rom.zip to flash, but after a few MB, it was throwing a "cannot read from source disk" error. Internal storage was corrupted.
I can read data from the partition, but after a while it'll lock up. I cannot write to it at all. I also get an error in CWM "unable to write to ums lunfile (no such file or directory)".
How can i fix this? I was thinking full sbf flash, but is that too risky? I'm in the UK (t-mobile), came with stock froyo, unlocked bootloader and flashed gingerbread onwards. Is it safe for me to flash back to froyo or something, or will my unlocked bootloader get me bricked? How can i fully clean this pesky corrupted partition any other way?
Thanks.
coolnow said:
AtrICS rom did a random reboot and was saying something about encryption failed. Strange, i've never used that setting (i don't even have a screen lock). I rebooted the phone and it wouldn't get to the ROM, so i went into recovery and tried restoring a backup. After a few seconds it aborted. Strange. I mounted usb so i could copy a fresh rom.zip to flash, but after a few MB, it was throwing a "cannot read from source disk" error. Internal storage was corrupted.
I can read data from the partition, but after a while it'll lock up. I cannot write to it at all. I also get an error in CWM "unable to write to ums lunfile (no such file or directory)".
How can i fix this? I was thinking full sbf flash, but is that too risky? I'm in the UK (t-mobile), came with stock froyo, unlocked bootloader and flashed gingerbread onwards. Is it safe for me to flash back to froyo or something, or will my unlocked bootloader get me bricked? How can i fully clean this pesky corrupted partition any other way?
Thanks.
Click to expand...
Click to collapse
Sound like the same issue myself and some others are having. I was using the atrics rom and icsrom as well before my phone went to heck. We cannot delete stuff from sd card or flash any other rom..
boonemeat said:
Sound like the same issue myself and some others are having. I was using the atrics rom and icsrom as well before my phone went to heck. We cannot delete stuff from sd card or flash any other rom..
Click to expand...
Click to collapse
Did you mess with the encryption settings? I know i didn't. Whatsapp was throwing errors so i rebooting the phone and now all this has happened. Can't even moto-fastboot flash system because it always gives an error :crying:
coolnow said:
Did you mess with the encryption settings? I know i didn't. Whatsapp was throwing errors so i rebooting the phone and now all this has happened. Can't even moto-fastboot flash system because it always gives an error :crying:
Click to expand...
Click to collapse
Sure did not mess with encryption. Rsd flashing did nothing, fastboot does nothing for me. Now the rom I'm stuck on is getting errors and fc's like crazy and the touch screen is beginning to fail.
boonemeat said:
Sure did not mess with encryption. Rsd flashing did nothing, fastboot does nothing for me. Now the rom I'm stuck on is getting errors and fc's like crazy and the touch screen is beginning to fail.
Click to expand...
Click to collapse
Damn. I would have thought RSD would be the last resort...
I think i've made some progress. I have to be up in 5 hours so i'll be making this short. You will need an SD card.
I was sick of the lockups created by the corrupted /emmc/ partition, so i rebooted my phone, went back into recovery (it would never mount any filesystem after mounting emmc once, so a reboot was needed every time) and mounted emmc. Showed up on my computer, and gave me a chance to copy my photos and all that. Thank you!
I started CMD as an admin and typed in
diskpart
Click to expand...
Click to collapse
When it loaded up, i typed
list disk
Click to expand...
Click to collapse
I saw a 10GB partition as disk 2 so i then
select disk 2
Click to expand...
Click to collapse
then i did
list partition
Click to expand...
Click to collapse
and saw only 1 partition, as partition 1, so
select partition 1
Click to expand...
Click to collapse
then
clean
Click to expand...
Click to collapse
Went into Disk Management and right clicked the black bar "unallocated space" and made a new simple volume, formatted as fat32 and that's that.
I then copied a rom onto my sd card and flashed via cwm. Everything seemed to go well, i could boot up (remember, because of the failed encryption, i was wiping my /system/, /data/ etc to try to get a fresh start so i had no rom to get on.
Will report back any problems. Just had one, i booted up fine but realised my usb cable was still plugged in so sd and internal storage were unmounted. Unplugged USB and phone froze (due to corrupted partition?). I recognise that freeze, i had it earlier on today (is that when the partition got corrupted?). It's rebooting right now, no usb cable plugged in. Wish me luck.
Android gave me a "your internal storage is corrupted" notification and offered to format. I allowed it and everything seems to be well! I will be filling it up right now before going to bed to see if it will lock up, but i think i fixed it!
Well congrats I'm glad you had such luck! It seems our problems are a bit different unfortunately because it goes a little deeper on my end. Thank you so much for the help.
Here is my struggle with the same problem. I have no solution, but maybe something here will help you?
http://forum.xda-developers.com/showthread.php?t=1967620
So, I've no idea specifically where to start, so I'll just go from the beginning. Earlier today, I flashed a stock firmware for my device (I9300XXDLJ4 from the 'Stock Firmwares' thread) using Mobile Odin Pro successfully. No problems, except for when I forgot to factory reset the first time through.
More recently, I tried to re-flash CF-Root 6.4 to regain root, which didn't work as well as I had hoped, as I am now left with an unmountable /data partition on my internal SD, which means I cannot go any further in the 'factory reset -> restore' route. I have no idea what to do anymore - 30 Google searches later and about 20 separate flashes of firmware hasn't helped and I'm at the end of my tether. I really have no idea what other information to supply, so I guess if you guys have any idea you can let me know.
In addition, although a blank, yet working OS and phone would be better than a paperweight, I would like to keep my internal sd-card intact (or at least the partition with all my stuff on it). I also have a CWM6 back-up on my external sd if that could help me in any way.
So, yeah, whatever you can think would be greatly appreciated please and thank you.
(Long story short - unmountable /data partition on my internal sd means I can't boot/flash any 'proper' OS / it's soft bricked.)
UPDATE: Booted into stock Samsung firmware as above, not sure if it's because it's still got all the stuff from before and I haven't wiped it or it's genuinely fixed. May as well spend another half-hour on Odin to see what I can do.
UPDATE 2: Fixed. Mounting the /data partition only worked once I flashed the stock firmware - whether it's because of the recovery or the OS, I'm not entirely sure, but I'm now able to read/write to the /data partiton and I've just booted up my previous CM10 nightly, so... yeah. DO what you will with this thread mods. I'm done here, for now.
Irradium said:
So, I've no idea specifically where to start, so I'll just go from the beginning. Earlier today, I flashed a stock firmware for my device (I9300XXDLJ4 from the 'Stock Firmwares' thread) using Mobile Odin Pro successfully. No problems, except for when I forgot to factory reset the first time through.
More recently, I tried to re-flash CF-Root 6.4 to regain root, which didn't work as well as I had hoped, as I am now left with an unmountable /data partition on my internal SD, which means I cannot go any further in the 'factory reset -> restore' route. I have no idea what to do anymore - 30 Google searches later and about 20 separate flashes of firmware hasn't helped and I'm at the end of my tether. I really have no idea what other information to supply, so I guess if you guys have any idea you can let me know.
In addition, although a blank, yet working OS and phone would be better than a paperweight, I would like to keep my internal sd-card intact (or at least the partition with all my stuff on it). I also have a CWM6 back-up on my external sd if that could help me in any way.
So, yeah, whatever you can think would be greatly appreciated please and thank you.
(Long story short - unmountable /data partition on my internal sd means I can't boot/flash any 'proper' OS / it's soft bricked.)
UPDATE: Booted into stock Samsung firmware as above, not sure if it's because it's still got all the stuff from before and I haven't wiped it or it's genuinely fixed. May as well spend another half-hour on Odin to see what I can do.
UPDATE 2: Fixed. Mounting the /data partition only worked once I flashed the stock firmware - whether it's because of the recovery or the OS, I'm not entirely sure, but I'm now able to read/write to the /data partiton and I've just booted up my previous CM10 nightly, so... yeah. DO what you will with this thread mods. I'm done here, for now.
Click to expand...
Click to collapse
Good to read a thread with a quick "happy ending"!
Good work mate!
// Ohamn