Develop Bugs

[Q] Boot looping / Corrupted data partition

Been using the Alpha version of CM7 for the t989 for over 2 weeks now. Seems like when I rebooted it today it managed to corrupt the data partition.
Symptoms:
-Normal starts loop just after the kernel screen.
-CWM boots and works
-ODIN boots.
-CWM crashes when doing factory reset or restoring the data partition of a backup or formatting the data partition
This happened to me 2 days after installing CM7, the same version I'm still using. I was similarly stuck, but then I tried restoring my nandroid backup and eventually I could re-apply the CM7 zip and the phone started fine to a blank android.
Is there a way to solve this issue with my partitions? I am not too comfortable with re-partitioning it because I'm awake this can damage the boot sectors and brick it quickly if I don't do it just right.
Advice?

Just flash this http://forum.xda-developers.com/showthread.php?t=1391174 from Odin, reflash cwm, cm7, and you are done. I have done this thrice.
Sent From The Best Phone of 2011

GBGamer said:
Just flash this http://forum.xda-developers.com/showthread.php?t=1391174 from Odin, reflash cwm, cm7, and you are done. I have done this thrice.
Sent From The Best Phone of 2011
Click to expand...
Click to collapse
did it work???

Thank you
I'm so glad I found this thread, I thought my phone may be unreparable. I was experiencing exactly the same symptoms as the OP on my skyrocket and had considered using ODIN to restore to stock, but I thought the corrupted data partition could cause it to crash during the restore and hard brick the phone.
The restore was successful, but it boot looped for some reason. I then followed the ODIN root method to flash CWM recovery, flashed CM7 from there, booted and used the ROM Manager app to apply a recent backup. All is well.

Screwed up my phone. HELP!!

So, I was running CM9 with D2SD but wanted to remove it because I was getting some problems so I tried to restore my backup with the normal CM9. It didn't restore properly. I then thought that anyways the internal member is very low on CM9 then I should try out MTDPartition. I forgot to edit the txt file which is using while flashing CM7 . It installed but didn't pass the boot screen. I tried flashing again but no use. So I downloaded CWM again and flashed it. Then tried installing CM7. Didn't install! So I flashed CWM again and tried with MTD. It installed.
Everything was working normally. I wanted to flash a theme so I rebooted into recovery and flashed that theme (Which I was using since over a month). It just didn't start my phone then.
Now everytime I reboot, my phone starts the boot screen and then suddenly gets stuck and restarts again. This happens again and again. I tried flashing CM7 and CM9 again but same thing happens always
Please HELP!

Have you tried installing CWM recovery again?
I would recommend, install CWM again, then run superwipe, then MAKE SURE YOU REBOOT INTO RECOVERY (NOT REBOOT SYSTEM), then flash your rom again.
(thanks to blueridge wfs team for the sharing superwipe script).

Before flashing your rom, did you perform the following steps?
1. Wipe Data/Factory Reset
2. Wipe Cache
3. Wipe Dalvik
If not, try to do that first, then flash your rom.

CWM Recovery Problem

Hi,
I just recover my phone with a cwm backup.
But after this, my phone stuck on bootloop.
That's why, I've wiped dalvik cache.
But now, on boot, Android is such as new, no more apps, ...
So, What's the way to get back as more data as possible?
I was thinking that you could get back your mobile as before with cwm!
Thanks for your help

Well, when the phone gets a bootloop after restoring a nandroid backup, it's maybe because you have a different kernel from the one that's on the backup file.
If you want, try flashing with Flash Tools the stock ROM, get onto Fastboot mode and do a hotboot of a CWM kernel (because you will lose the complete install, by now) then restore your old backup.
It will keep all the data.
Sent from my Arc S using xda premium

The backup date of yesterday so, it's not a kernel problem.

[Q] defy help can't restore backup or install new rom

hello everyone i am new but i have read many posts and none of them have helped me, ok i can't seem to restore any of my backups or install a new rom
i have installed cm 10 before this
(mb525 red lenses)
i have tried doing this many times:
http://forum.gsmhosting.com/vbb/archive/t-1412358.html (were i got the firmware.sbf Fixed SBF file from)
http://forum.xda-developers.com/showthread.php?t=1216982
http://forum.xda-developers.com/showthread.php?t=1818520
http://forum.xda-developers.com/showthread.php?t=1618718
http://forum.xda-developers.com/showthread.php?t=1054447
(and lots more)
so i restore from an sbf file the ones i have tried:
JORDN_U3_6.36.0_SIGNED_USAJRDNTMOB1B4B5DE1028.0R_JORDANTMO_P022_HWp3_Service1FF.sbf
JORDN_U3_97.21.51.sbf
when i restore from them i use SuperOneClick v2.3.1 to root then i install the SndInitDefy_2.3.apk
when i do that i can't boot into boot menu unless i flash firmware.sbf after installing it and when i do that i can't go back into stock
or if i use defy_recovery-1218-0326-signed.apk to get into a old clockwork that wont restore back ups and it installs the rom way to fast so it isn't installing at all it just says it is and then if i reboot it boot loops i have tried wiping in every way before and after but what i can do is install
touchbootmenuV2.0beta_multibootV0.8-20120829-signed.zip that gives me a newer clockwork mod but half the time the sd card or the cashe won't mount but when they do system and data can not be restored to and when i install a rom it boot loops but it installs slower than before but still to fast
and when ever i get a boot loop i have to start this all over again i have been looking everywhere but i cant find a way to fix this i have also tried flashing different kernels before and after flashing the rom and using defy_fullwipe_ext3.zip and defy_fullwipe_ext4.zip but i think the problem is that i can't restore system or data
anything would be very help full
thanks.

an update
ok, i was able to get cm 7 on my phone today by doing this:
Flash this SBF file: JORDN_U3_97.21.51.sbf
Root my phone with super one click
Install 2nd Init 1.4.2
Flash Fixed SBF: firmware.sbf
Reboot to CMW recovery, and wipe Data/Cache.
Restore this Nandroid Backup: 2011-06-11.14.14.27
Install CM7 then install Google Apps.
but when i do this and try to install:
CM10-20120924-NIGHTLY-mb525.zip
CM10-20121205-NIGHTLY-mb526.zip
CM10-20121204-NIGHTLY-mb526.zip
after it flashes the blue led it flashes red then reboots

another update i was able to get cm 7 on my phone but now i only have 128mb i have tried:
http://forum.xda-developers.com/showthread.php?t=1162464
http://forum.cyanogenmod.org/topic/35640-internal-space-only-128mb-language-resets-at-reboot/
they did not help me i'm starting to hate this phone
and if i do a stock wipe before installing cm7 it does nothing but with miui it doesnt boot at all

i fixed it
i flashed
DEFYPLUS_U3_4.5.1-134_DFP-137_ND_SIGN_SIGNED_UCADEFYEMARAB1B80AA004.0R_PDS03C_USAJRDNGIBRRTNORD_P009_A011_HWp3_Service1FF
then stock factory wipe in stock recovery then rooted with SuperOneClick Installed 2ndinitDefy 1.4.2
then i got the error: E:Can't make /tmp/update_binary
fixed it with this: http://forum.xda-developers.com/showthread.php?t=1540372
Then a CWM factory wipe
Then flashed CM10 and gapps
now it works with full sized data partition and everything

[Q] Include 'Preload' in Nandroid of Stock 4.1.2?

I noticed in TWRP 2.5 that there is the option to backup/restore 'Preload'. I have also read that the ROMs based on TMo 4.1.2 need preload working properly to boot, unlike previous ROMs. Should that option to include it be checked when backing up and restoring the stock 4.1.2-based ROMs?
I've also noticed that the the Preload size is 0 when backing up other roms in TWRP, so I haven't concerned myself with it. Before TWRP 2.5, I knew nothing of preload (I guess I still don't really know anything). Any thoughts?

Well, I guess I'll find out what to do by trial (and error?). I backed up JMT JB3 (including preload) to flash the Koodo update and run it for a while. I'll restore it later on and see how it boots.

I'm not sure how it works. I'm on JMT3 myself right now. I used ODIN to update to the official release when it came out, and it was doing fine, but I wanted to try some of the custom ROMs out there that are based on it. I was rooted with CWM, and did the usual backup that has worked since I can remember. I don't remember what ROM I tried next, but I didn't like it much, so I restored my back up. It restored correctly, or so I thought. After some use I started getting FC here and there. I couldn't fix it, so I did a factory reset from within the phones settings, not through recovery. As soon as it tried to reboot I kept getting a boot loop. I never was able to get it booted. I was able to boot to recovery, flash cache and wipe scripts that were recommended, and flashed JMT3. All is good now. I know trying a cache wipe or factory reset through CWM won't work since I tried it before, so I didn't even try it for this one.
So long story short I don't know how CWM (or any recovery) handles the preload. All I know is the scripts work to flash clean, or wipe cache/dalvik/fix perms, but I haven't gotten them to work after restoring a back up. My thinking is to be careful until someone figures it out because I don't think backing up will help if I ever need to. I'll have to start fresh each time I want to flash anything.
Here are the scripts I'm talking about: http://forum.xda-developers.com/showthread.php?t=2235141

Thanks for sharing your experience. I have those same scripts handy - had to use them when I flashed JMT3.
If or when I restore, I figure I'll wipe my current preload and restore the preload in my JMT backup, then flash the Infamous cache wipe script (or equivalent function in recovery if TWRP develops something similar). I'll post again to share my results when the time comes.

I ended up wanting to restore old stock 4.0.4 in TWRP 2.5.0.0 recovery. Part of me wanted to do it just so I could test the backup/restore of the preload.
I first backed up my current rom (stock Koodo/Telus 4.1.2) with the cache and preload included. I then wiped data, system, caches and preload, and ran the restore of my old backup. The 4.0.4 booted just fine. Once I was done checking for the info that I wanted, I went back to recovery and wiped all the same stuff (everything except internal and external SD) under advanced wipe options. I then restored my stock Koodo/Telus 4.1.2 backup. It seems to be running fine now although I haven't experimented much to test for any FCs. It didn't seem to have any issues booting at least.
I may have been doing some excessive wiping - I assume restoring a partition also formats it before overwriting it. I'm not even sure I needed to wipe anything to restore 4.0.4, but I didn't want a preload (110 mb) causing issues in a rom that doesn't need it at all. In any case, I know what can be done to avoid issues restoring stock 4.1.2, although I'm still not sure what needs to be done to avoid issues.

You did it exactly right. When using a 4.1.2 Samsung rom, be it custom or stock, and backing up or restoring; the preload folder is just as important as data or system. Basically the point of the preload patition is to get the system partition to fit. By symlinking the apps from preload to system Samsung has saved room and allowed a bigger rom to work on our hardware.
As an example, I am on TWRP 2.4.? and cannot backup preload. When I tried a different rom, then went back to my backup I had FCs like crazy. Because I had used the Infamous wipe script it had wiped the preload folder but there was nothing to restore to it from my backup. I had to reflash the rom I was using (really I just wanted the preload folder installed) and then restore my backup to get it working.
I hope all this makes sense. I'm going to Twrp 2.5 so I can backup my preload folder (when I stop being lazy).
Thanks guys.