Last week something burnt out in my Streak, it wouldn't turn on, so I needed to send it to get repaired/replaced, as a little data insurance I took a dump of the internal SD card (just using dd in Ubuntu).
Now O2 are replacing my Streak, so I'll have a new one with a different IMEI, etc, and I don't want to open this one (I only opened the other one as it was an emergency). So I'm looking for help on restoring the backup I've taken without opening the phone, and once done, leaving it in a warranty-friendly state.
Obviously the first step is going to be rooting it, but what then? Is it simply a matter of copying all the files? Just thinking that might cause conflicts due to the new IMEI.
so i've got a similar (but reciprocal) problem... i had a malformed update.zip that pooched my internal microsd's system partition and the streak won't boot at all... I have a nandroid backup and i've pulled the internal microsd to find an empty ext filesystem that mounts just fine when I plug it into a linux laptop, but there's not a clear mapping from the system.img that I have and the contents of the accidentally wiped system partition...
SO, two things would fix this....
1. someone could send me a link to their raw 'dd' image of the system partition (~200mb)
2. or, I can keep figuring out how to use 'dd' with the system.img that I have to get the same results as the 'flash_image' tool...
would someone be so kind as to speed me along on this by giving me their system partition dump (1) or quickening my learning curve on (2) so that I can restore with the flash_image formatted nandroid dump of a working system partition???
Please, please....
I recently had some disruptive partition troubles. I don't know how they started (must've been a bad flash, or a flash which didn't finish seeing as though i was experimenting with the leaked roms) but basically, my /cache, /system, /data, and /emmc partitions were all corrupted.
Fixing the /emmc, /cache and /system partitions was quite easy. I booted up into fastboot mode, flashed an ADB enabled recovery (the one in the Atrix Development forum works fine) and downloaded ADB.
I booted up into recovery, and in CMD i went into adb shell and used "parted /dev/block/mmcblk0p18" to get into the emmc partition, "rm 1" to remove the corrupted partition and "mkpartfs" to make a new partition as ext2, start 0, end 11.5GB (or something like that) and let it finish. Then i went into Mounts and Storage in CWM and formatted emmc. Did the same for /cache (mmcblk0p15) and /system (mmcblk0p12).
So far so good, my random reboots were fixed and my deadly FC of all apps was gone. But not for long.
I noticed after about 24 hours of normal use, i would start FC everything and multiple reboots + clearing caches (including dalvik) would fix it temporarily. This was a headache as messaging, phone and whatsapp would all crash and not recover.
I chalked this down to the /data partition (also known as /userdata, which houses the dalvik cache). I must be hitting a corrupt part of it during my daily use which messed my device up (once i hit the corrupt part, i could not do ANYTHING with the device, including just checking a partition. I would ALWAYS have to reboot at least twice to even read the partition).
I tried the same method as before (mmcblk0p16 for userdata partition) but i couldn't do it. It would always fail at around 90% and say i/o error and needed a few reboots. If i made a fat32 partition, i couldn't format over it with CWM (error near the end). Same with any kind of partition. This was the partition which couldn't be fixed...
So i decided to go all out. I knew i never flashed OTA 2.3.4 (Gingerbread), so i downloaded the Gingerbread SBF from a quick google search, despite all the warnings (i also THINK you CAN flash this SBF even though you were on OTA 2.3.4, just NOT ANYTHING LOWER SUCH AS FROYO). I booted into RSD mode and hoped for the best. Flashing went fine, but i was in a bootloop (due to data partition). Tried clearing with the stock android recovery and i would get i/o errors even though it said successfully wiped.
It was here when i got angry.
I flashed the ADB enabled recovery via fastboot and booted into it. Went into adb and parted again (first i inspected emmc partition which was mmcblk0p18). Did "print" and it said couldn't find label or something (which meant no partition table was found). ALL my partitions were missing this partition table.
So i created one.
"mklabel msdos" for emmc partition, then mkpartfs to make a primary partition, ext2, start 0, end 11.5GB" (or something like that) and let it happen.
For cache partition, i did "mklabel loop" then mkpartfs ext2, etc etc, with data i did "mklabel loop" and made a partition, same with system.
Then i tried wiping them via CWM. SUCCESS! I formatted them 5 times each just to be sure and sure enough, they were working fine now. I flashed a new ROM (couldn't risk my backup partitions having a corrupt sector or something in them) and heavily used it for a few hours. Downloaded many apps and games, did loads of texting and test calls.
No reboots. No FC, no problems for 24 hours. Hope it stays this way.
I posted this in hopes that others would find a solution with this rare problem. My data partition was the killer, no matter what, i couldn't fix it without flashing sbf. Remember, don't flash froyo sbf, only gingerbread (just to be safe).
Need some help. I have a Dell Venue with 2.2. I have rooted the phone and installed ClockworkMod so I can get to the root directory. I frequently get low memory warnings and even warnings that an SMS message was rejected due to low system memory!
I have moved all of my downloaded Apps to the SD card (and deleted quite a few). I have set my email app to store email on the SD card. I have gone through the root directory and removed system apps that I do not ever use. I have even cleared the cache and the dalvik cache. All of this has helped, but only briefly. After doing all of this, the phone will be ok for maybe a day or two, then the warning returns. When I 1st got the phone a year ago, I had no problem having tons of apps stored on the phone, now I can't hardly have anything.
The warnings start at about 53M of internal storage available. Is there any way to free up more internal storage? Are there unnecessary files that can be deleted?
I really liked this phone when I 1st got it, but now I absolutely hate it and I am stuck with it for another 6months! HELP Please!
/cache and /system are seperate partitions: cleaning them won't give you any more space on /data.
you could move some apps into system if you understand some of the risks:
You have to manually update the copy in /system or you will end up with an old copy in /system and the new one in /data
modifying /system can lead to bricks if you don't understand what you're doing
Thanks!
TheManii said:
/cache and /system are seperate partitions: cleaning them won't give you any more space on /data.
you could move some apps into system if you understand some of the risks:
You have to manually update the copy in /system or you will end up with an old copy in /system and the new one in /data
modifying /system can lead to bricks if you don't understand what you're doing
Click to expand...
Click to collapse
Thanks for the info. Unfortunately, something else has happened and my phone may actually be bricked for some reason. I decide to just factory reset the phone and reload everything from scratch hoping this would clear up the problems. As it goes through the start up, I connect to WiFi, connect to my google account, and when it attempts to start the Dell Stage, it just locks up. I have factory reset it 3 or 4 times with the same results every time. Not sure what happened.
Going to search on here to find a fresh copy of the factory ROM or maybe someone has posted a Nand backup that I can load from the SD card. Any suggestions would be much appreciated!
Hi, I was having some issues on my Nook Tablet 16gb, so I thought I would format everything (actually format every single item 3x) with the goal of having a fresh boot without issues. But then when I installed Slim Rom or any other ROM it installs them and when I hit "reboot system now" on CWM after installing the NEW Rom, it tries to load and goes to the Big N shape boot animation and then back to CWM.
What would you suggest I do?
Thanks a lot!
---
The items I wiped (each 3 times!): ROM, bootdata, factory, system, cache, emmc, data, sdcard, data1.
somerandomname said:
Hi, I was having some issues on my Nook Tablet 16gb, so I thought I would format everything (actually format every single item 3x) with the goal of having a fresh boot without issues. But then when I installed Slim Rom or any other ROM it installs them and when I hit "reboot system now" on CWM after installing the NEW Rom, it tries to load and goes to the Big N shape boot animation and then back to CWM.
What would you suggest I do?
Thanks a lot!
---
The items I wiped (each 3 times!): ROM, bootdata, factory, system, cache, emmc, data, sdcard, data1.
Click to expand...
Click to collapse
Don't press "reboot system now" when you want to exit recovery. Power down system then power it on again. It should boot just fine.
somerandomname said:
Hi, I was having some issues on my Nook Tablet 16gb, so I thought I would format everything (actually format every single item 3x) with the goal of having a fresh boot without issues. But then when I installed Slim Rom or any other ROM it installs them and when I hit "reboot system now" on CWM after installing the NEW Rom, it tries to load and goes to the Big N shape boot animation and then back to CWM.
What would you suggest I do?
Thanks a lot!
---
The items I wiped (each 3 times!): ROM, bootdata, factory, system, cache, emmc, data, sdcard, data1.
Click to expand...
Click to collapse
Your boot-loop problem might be due to invalid or missing data in /bootdata resulted from your having wiped this partition, see http://forum.xda-developers.com/showpost.php?p=21381141&postcount=1. You can try restoring the data by flashing flashable_fix_bootloop.zip from http://goo.im/devs/succulent/acclaim/recovery.
datallboy said:
Don't press "reboot system now" when you want to exit recovery. Power down system then power it on again. It should boot just fine.
Click to expand...
Click to collapse
I tried that didn't work, thanks.
Sent from my SGH-T999 using Tapatalk 2
Wiping ROM seems to have the effect of triggering a recovery every boot, which if you had the stock recovery should recover all the device info stored there. I had to use a repart.img sdcard which loaded stock 1.4.2 or 1.4.3 (Search for files and guides). Then I used a CWM sdcard and put custom recovery and ROM back on.
Sent from my Barnes & Noble Nook Tablet using xda premium
digixmax said:
Your boot-loop problem might be due to invalid or missing data in /bootdata resulted from your having wiped this partition, see http://forum.xda-developers.com/showpost.php?p=21381141&postcount=1. You can try restoring the data by flashing flashable_fix_bootloop.zip from http://goo.im/devs/succulent/acclaim/recovery.
Click to expand...
Click to collapse
This did not work either. thanks
somerandomname said:
This did not work either. thanks
Click to expand...
Click to collapse
The next likely cause of your problem is missing factory-installed device data (e.g., WiFi MAC address, security encryption keys, etc.) that are stored in /rom and /factory partitions which you stated in the OP you had wiped. Unfortunately I am not aware of any way to recover this original set of individual device specific data.
Did you try the stock files like I said before? That got my info back
Sent from my Barnes & Noble Nook Tablet on CM 10.1 using xda premium
dejello said:
Did you try the stock files like I said before? That got my info back
Sent from my Barnes & Noble Nook Tablet on CM 10.1 using xda premium
Click to expand...
Click to collapse
Yeah I was able to use the thread by Adam to redo my tablet with the normal files for Rom through a SD card boot since the touch was not working.
Thank you, this was a great learning experience in my 5 years of playing around first time to cause a brick...
Sent from my SGH-T999 using Tapatalk 2
I'm glad you got it figured out this droid charge i'm on right now used to brick every time i flashed, then started working right one time I've just learned to take it easy and see about fixing things
Sent from my SCH-I510 using xda app-developers app
CWM Bootloop...
Hello all!
It seems I've gotten myself into a bit of trouble with my Nook Tablet. I had been running CM7 for quite some time and finally upgraded to CM10. Very nice! However I landed myself in a CWM boot loop after about a week and have not been able to recover.
First, I attempted to recover back to BN Stock, not knowing that it would not replace CWM with stock recovery. I still have CWM and half of a stock installation (repart.img from bn_142_factory_recovery.zip). From what I understand, the stock BN software is trying to boot to recovery to complete the install, although it was in bootloop before that attempt was made.
Since then, I have tried flashable_fix_bootloop.zip as well as cwm_6.0.2.9_acclaim_recovery_sdcard.img to no avail. I fear that I may have made the mistake of formatting too many things as mentioned at the top of this thread to get into myself here in the first place. What is my next step?
Much appreciated!
-byrd
You could try what I tell the poster in the topic "At wits end". In the beginning of the topic I described an easy way to make a notable COM card. You can then jump to the end of the topic and try to use my backup file. I will remove access to that file later today and I don't know if it will work at all but at least it's worth a try.
asawi said:
You could try what I tell the poster in the topic "At wits end". In the beginning of the topic I described an easy way to make a notable COM card. You can then jump to the end of the topic and try to use my backup file. I will remove access to that file later today and I don't know if it will work at all but at least it's worth a try.
Click to expand...
Click to collapse
Thank you for your reply, asawi!
I've begun the download. From what I understand, this will give me a bootable MicroSD into CM10. If that is correct and it boots as it should, I can then install this image as firmware in some fashion or at least be able to repair the damage done so that I can reinstall CM10?
[Warranty is of no concern. I bought this Nook Tablet in used condition quite some time ago with intent to use CM as primary OS, hence the use of CM7 for well over a year.]
-byrd
If, this works (and that's a HUGE IF), twill leave you with a tablet running CM 1O from internal memory.
It is a two step thing though with two big downloads. The one from Iamafanof will make you a bootable CM10 card. Either you can use it as it's intended, or just use it to get into CWM recovery where you can go to backup and restore and try to restore the backup I made. Unzip my file first, like I tell the other poster.
Edit:I realized I had goofed up when posting the first backup. I have now put up another download of the whole "clockworkmod" folder in my Dropbox. Link in the "at wits end" topic. but I will only leave it up for a very limited time.
asawi said:
If, this works (and that's a HUGE IF), twill leave you with a tablet running CM 1O from internal memory.
It is a two step thing though with two big downloads. The one from Iamafanof will make you a bootable CM10 card. Either you can use it as it's intended, or just use it to get into CWM recovery where you can go to backup and restore and try to restore the backup I made. Unzip my file first, like I tell the other poster.
Edit:I realized I had goofed up when posting the first backup. I have now put up another download of the whole "clockworkmod" folder in my Dropbox. Link in the "at wits end" topic. but I will only leave it up for a very limited time.
Click to expand...
Click to collapse
Using Cyanoboot from the bootable card, I am able to boot into SDC RECOVERY. From there I swap the SD card for another containing your your backup folder, navigate to 'backup and restore'/'restore'/'2013-09-17.16.18.21'. Restore process begins okay, but fails with "Error while restoring /system!"
I then went to 'advanced restore' and attempted restoring /boot, /system, /data, /cache, and /sd-ext individually with these results:
/boot = Restore Complete
/system = Error
/data = Error
/cache = Error
/sd-ext = sd-ext.img not found, Skipping restore...
-byrd
byrdeth said:
Using Cyanoboot from the bootable card, I am able to boot into SDC RECOVERY. From there I swap the SD card for another containing your your backup folder, navigate to 'backup and restore'/'restore'/'2013-09-17.16.18.21'. Restore process begins okay, but fails with "Error while restoring /system!"
I then went to 'advanced restore' and attempted restoring /boot, /system, /data, /cache, and /sd-ext individually with these results:
/boot = Restore Complete
/system = Error
/data = Error
/cache = Error
/sd-ext = sd-ext.img not found, Skipping restore...
-byrd
Click to expand...
Click to collapse
If /boot was successfully restored, that's what matters the most (please, tell me you did NOT erase /rom, because if you did, you're in a really bad situation). You don't need to restore asawi's FULL backup. If the /boot partition is functioning normally now, you should be able to boot into your internally flashed CWM, wipe data/factory reset, wipe dalvik cache, and wipe system, then FLASH the ROM and gapps. You should not be experiencing the bootloops anymore (make sure to take out the SD card BEFORE rebooting to internal CWM).
Back in the day I had my phone encrypted with data as a ext4 partition, I switched to using f2fs for a long time.
Now that I've tried to go back to using data as a ext4 partition while booting android asks for a invalid decryption password
using a really old pin number (I've had it encrypted several times since then using f2fs with different pin numbers) from the first
time I encrypted my partition while it was ext4.
Now when ever I wipe my data partition and try and use it as ext4 while booting android asks for a decryption pin which I can enter
but then complains that the filesystem it is trying to decrypt is corrupt.
I've tried doing a data format in twrp but it automatically formats it f2fs which doesn't solve the problem since
the problem only shows up while data is formated ext4.
I've tried every piece of wisdom I can find on the internet.
factory reset,
formatting all partitions,
dd front and back of userdata and then make_ext4 on userdata,
twrp format data,
recovery --wipe_data --set_encrypted_filesystem=off (from within twrp with the partition formated ext4),
format f2fs then boot up and reset and format ext4,
etc.
How do I give data the ultimate clean slate for being formatted ext4?
Or where is the remnant of the old encryption info stored from the first time I encrypted my phone?
I can format my data partition f2fs but frankly I was a little stunned when I saw the kind of overhead that filesystem has,
its space using overhead is way more then I want to have in a filesystem, or any filesystem I've ever seen.
Also is the problem not what I think it is?
Faced the same behaviour on my xt1524. Would be interesting to know if there is a solution for this
Is there a way to generate a new encryption from within the recovery?
Since it won't boot with data formatted as ext4.
Formatting it ext4 and then putting a new valid encryption on it?
From what I've found it, if the UI to unlock the partition on boot had a cancel button the system would boot as normal.
Unfortunately there is no cancel button on the unlock encrypted partition screen on our device. =/
Tried flashing a different recovery and using it wiping tools on data.
official twrp-3.0.2-0-surnia.img.
mkfs-f2fs -t 0 /dev/block/mmcblk0p44
process ended with ERROR:255
Unable to wipe Data.
Unable to format to remove encryption.
Also data wiping on TWRP is defaulting to trying to format data as F2FS which isn't even the default,
and while the partition has been switched to ext4.
I'd like to fastboot erase userdata and then fastboot format userdata.
But its giving me this error message.
fastboot format userdata
(bootloader) has-slot:userdata: not found
Formatting is not supported for file system with type 'raw'.
I've already done a lot of looking around on this issue, I'm normally not worried about this but
formatting internal system partitions that I don't understand how its different from a standard
desktop computers layout does worry me.
Should I be doing a full wipe and format everything to stock and then back to a custom rom?
God I wish this was a desktop computer right now, wipe the hard drive and reinstall the operating system,
there is something to be said for being simple and straight forward.
WTB cellular modem support in standard operating systems, and handheld devices that
can run standard operating systems.
I'd ditch this overcomplicated vendor locked sht so fast and never look back.
Following this guide to setup a new system encryption with rom in one go from the start with data as ext4 to see if I can bypass it this way.
But I'm getting a cannot find libraries error running cryptfs format command from adb shell or twrp terminal. b(>.<)d
http://android.stackexchange.com/questions/33398/cannot-factory-reset-after-encrypting
All this because someone thought it would be a great idea to take off the cancel button on data decryption
during boot.
This is why god invented beer and soaking you're brain in alcohol.
Damn been at this thing all day and still no luck.
Can I smoke the whole userdata partition with DD without bricking the phone?
In fact what can I effectively zero on a android phone without bricking it?
Am I miss reading this problem? Is the new inbuilt ext4 encryption (ext4 filesystem now has built in encryption support on newer kernels) support assumed to be on?
Never mind not as solved as I thought, But I just found another way to have my partition set to F2FS with letting me know. (^.^)
God this illustrates why formatting utilities that take shortcuts and 'ghetto erase' stuff are bad.
*Edited*
Default filesystem from the factory was F2FS (I have a bad memory : ) looks like it doesn't support putting data on Ext4.
Editing this post because I did a lot of post updates on what I was trouble shooting, but that might have
pissed people off because it does 'bump' the thread.
Sigh I'm throwing in the towel and formatting F2FS and moving on, F2FS is a one way door one which you never get back to ext4 from. > : (
Or ext4 formatting utilities suck balls and don't do their jobs.
Format all partitions to f2fs reboot to recovery again and format system and cache to ext4 now make a factory reset and reboot.