Related
Hi everyone.
I just made a backup/full wipe/restore with CWM latest version available on rom manager.
The backup are good (their MD5 sums are correct) but clockworkmod recovery is not able to restore the data.img
(while restoring it hangs and exits)
The problem is in the yaffs .img file (incorrectly created by the recovery).
If you try to unyaffs it the software begins the extraction and then
Code:
C:\Users\Lino\Desktop\secure>unyaffs data.img
read image file
: Bad file descriptor
read image file
: Bad file descriptor
DO NOT TRUST ON BACKUPS made by cwm 3.0.2.6 if you don't want to lose your data.
You are warned.
UPDATE in post #20
FIX in post #24
I'm sure I can speak on behalf of many people here. I have been using cwm for years on 3 different devices without any issues. Just because you are having an issue does not mean you should post a thread claiming no one should trust cwm.
I did it too but in latest (published) version of CWM there must be a bug in yaffs creation.
You can ignore this if you think I'm wrong.
I'm not stating that in EVERY version there was a problem...
I'm warning everybody that THIS version does.
The created IMG is corrupted even if its MD5 is correct and the recovery "crashes" when trying to restore the backup. try it yourself.
Steps:
Full backup.
Wipe data/factory reset.
Restore.
....the restore process aborts while restoring.
Maybe you are trying to backup/restore an EXT4 rom with an EXT3 CWM version (3.0.2.6)
No, I'm not.
The restore process starts and restores correctly about 600mb of data (on a total of 800) after that the recovery reboots (without restoring android secure, I suppose it gets restored after data).
The phone can boot up but with crippled data.
I successfully restored android secure unyaffsing the img and copying manually the data back to the card but I have no way to extract the remaining 200 mb from data.img because the image is bad.
The only time I've had this issue was when I made a backup without paying attention to how much space I had left on my SDcard, it was practically full, but Recovery happily completed and generated an md5. Needless to say my backup didn't work, but really it was my own fault for not making sure I had enough space on my card.
Nope. 5 gb still free.
Even the backups made with 3.0.2.5 are damaged.
..and I'm reading there was a similar problem (in the backup part) in the past:
1.8.4.3 Fix bug in yaffs2 where the max path was set to 500, rather than PATH_MAX. This was causing issues when creating yaffs2 images of files with very long names that were generated by a process gone bad, or the like. This causes a segfault during backup of the cache and the recovery reboots. The "symptom" is a missing md5 file.
Click to expand...
Click to collapse
This time the backup completes but the restore reboots the recovery leaving the restore process incomplete.
@LinoX
I can confirm your findings since I already hit the problem sometime ago.
I already mentioned this problem and since now has to use my own method of backup using dd
(I no longer use nandroid of cwm to backup). I already PM to CWM's author without any reply received since.
http://forum.xda-developers.com/showpost.php?p=14714800&postcount=319
http://forum.xda-developers.com/showthread.php?t=1124939
dnlilas said:
http://forum.xda-developers.com/showpost.php?p=14714800&postcount=319
Click to expand...
Click to collapse
YESSS!! IT IS EXACTLY THE SAME PROBLEM!!!
It's definitely the CWM broken.
I don't want to "restore" with dd because dd will write the partition directly to nand (transferring to nand the yaffs problem)... did you find a solution?
Did you try the 'Quick Backup and Restore' option from RM? I've struggled with a backup in the past with similar symptoms you described and enabling it helped along with 2 other steps:
1. Manually Advance Restore boot, system etc.
2. Fix permissions after then repeat step 1.
LinoX said:
YESSS!! IT IS EXACTLY THE SAME PROBLEM!!!
It's definitely the CWM broken.
I don't want to "restore" with dd because dd will write the partition directly to nand (transferring to nand the yaffs problem)... did you find a solution?
Click to expand...
Click to collapse
There is no problem using dd for backup/restore. Just make sure all partitions are unmounted before using dd.
Jacob1369 said:
Did you try the 'Quick Backup and Restore' option from RM? I've struggled with a backup in the past with similar symptoms you described and enabling it helped along with 2 other steps:
1. Manually Advance Restore boot, system etc.
2. Fix permissions after then repeat step 1.
Click to expand...
Click to collapse
I can't try... I have a partially recovered phone.. the backup I have is already "broken"..so that's a warning for everybody: don't trust nandroid backups.
Use DD method for backing up partitions (check 10 times command line before restoring, 'cause if you restore to the wrong partition you brick the phone)
I don't care about losing a couple of files.. I need a way to read a "broken" yaffs filesystem (in order to copy all "good files" skipping the damaged one)
maybe a mount -t yaffs?
dnlilas said:
There is no problem using dd for backup/restore.
Click to expand...
Click to collapse
Yes but it's a risky operation.. And I was referring to my damaged yaffs filesystem. The data partition should be ext3 so I need a way to "gracefully skip" the yaffs errors in order to read every file after the "error".. do you know if is there a way to do it?
http://androidforums.com/android-ap...workmod-recovery-failing-restore-backups.html
here's the same problem, f**k!
Well i never faced any problem so far...
LinoX said:
I need a way to read a "broken" yaffs filesystem (in order to copy all "good files" skipping the damaged one)
maybe a mount -t yaffs?
Click to expand...
Click to collapse
No way..
Code:
# mount -t yaffs2 -o ro,loop /sdcard/clockworkmod/backup/2011-07-05.09.38.18/data.img /sdcard/bkdata
mount -t yaffs2 -o ro,loop /sdcard/clockworkmod/backup/2011-07-05.09.38.18/data.img /sdcard/bkdata
ioctl LOOP_SET_FD failed: Device or resource busy
I never faced any problem...
Anyways will be careful next time.....
it would be interesting to see if we could replicate this and try to find out what is actually corrupting the image.
Ricey
Sad to say if the yaffs image is broken it is broken.
Yaffs is a filesystem stored in an image. It has indices and all. if unyaffs cannot read the file system it would be like guessing wich filename matches which part of the data. In a way that would be riskier than not putting data at all.
Do you have an older backup that is intact? It might save your Phone.
OK. I found the problem!!!
The yaffs image is NOT corrupted!!!
It's the UNYAFFS code that actually is broken.
I downloaded the unyaffs.c because I wanted to debug it (skipping the part of the damaged file) and extracting every possible file.
The recovery seems to use the SAME unyaffs code (because the exception is the same).
The problem is in the MAX number of files!!!!!
the code has a limit hardcoded in:
Code:
[COLOR=Blue]#define[/COLOR] MAX_OBJECTS 10000
when I debugged it it halted with an access violation simply because the number of files was bigger.
Modifying the unyaffs.c (increasing the constant to 50000) allowed me to extract every file (50.000 is the maximum defined in the "backup code")
So... at the moment your backup are good (unless we find some other error) but you can't restore them with every cwm so far (it will halt at the 10.000th file/dir).
please help my phone has no imei after flash a custom rom framework * # 06 # get this IMEI null / null http://imageshack.us/photo/my-images/546/sc20120828223834.png/
http://imageshack.us/photo/my-images/266/sc20120828223733.png/
Try flashing a different modem
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
dutchthomas said:
Try flashing a different modem
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Click to expand...
Click to collapse
I tried ics and ginger stock and nothing
See if this helps you http://forum.xda-developers.com/showthread.php?t=1611796
kishke said:
See if this helps you http://forum.xda-developers.com/showthread.php?t=1611796
Click to expand...
Click to collapse
I try this method and repair the lock screen that did not work but still not working imei imei null / null thank
That is REALLY BAD.... Not sure what to tell you... Heard someone else did that and they were screwed....
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
If it's only IMEI number that's missing use the search, there was a thread a while back with someone having the same issue, he got told to edit some file and enter his IMEI from the phone's sticker.
aiyoros02 said:
please help my phone has no imei after flash a custom rom framework * # 06 # get this IMEI null / null
Click to expand...
Click to collapse
Exactly what rom framework did you flash?
cschmitt said:
Exactly what rom framework did you flash?
Click to expand...
Click to collapse
Just install the Alpha 3 rom CyanogenMod 10 Chopsticks eat as usual, but I think the problem arose when trying to unlock the sim with an online payment program, since then insert * # 06 # and IMEI it says null / null
aiyoros02 said:
Just install the Alpha 3 rom CyanogenMod 10 Chopsticks eat as usual, but I think the problem arose when trying to unlock the sim with an online payment program, since then insert * # 06 # and IMEI it says null / null
Click to expand...
Click to collapse
Ok, first off did you follow the other post regarding repairing /efs/imei/keystr file if necessary?
Otherwise, sounds like the hidden EFS partitions are corrupt.
Do you have a recent nandroid backup (prior to the unlock attempt)? If so, check the data.ext4.tar for an efs1.bin, efs2.bin, and efs3.bin located in /data/qcks directory.
If you have the efs?.bin files I can walk you through flashing them back into the EFS partitions on the phone. That'll restore the IMEI.
cschmitt said:
Ok, first off did you follow the other post regarding repairing /efs/imei/keystr file if necessary?
Otherwise, sounds like the hidden EFS partitions are corrupt.
Do you have a recent nandroid backup (prior to the unlock attempt)? If so, check the data.ext4.tar for an efs1.bin, efs2.bin, and efs3.bin located in /data/qcks directory.
If you have the efs?.bin files I can walk you through flashing them back into the EFS partitions on the phone. That'll restore the IMEI.
Click to expand...
Click to collapse
if you use the method / efs / imei / keystr, and retrieve the Parameter Display Lock was corrupt, but does not appear imei,
I have nothing, everything was erased trying to repair the error, I did all the wipe and factory reset. maybe find another method
aiyoros02 said:
if you use the method / efs / imei / keystr, and retrieve the Parameter Display Lock was corrupt, but does not appear imei,
I have nothing, everything was erased trying to repair the error, I did all the wipe and factory reset. maybe find another method
Click to expand...
Click to collapse
Sorry to say then, without a nandriod backup you're SOL.
cschmitt said:
Sorry to say then, without a nandriod backup you're SOL.
Click to expand...
Click to collapse
I'm facing same issue with my Skyrocket. Did anyone found any solution for this null/null IMEI?
talk2sharn said:
I'm facing same issue with my Skyrocket. Did anyone found any solution for this null/null IMEI?
Click to expand...
Click to collapse
Check out these threads, there are solutions but you got to pay up at least €10
http://forum.xda-developers.com/showthread.php?t=2288390
http://forum.xda-developers.com/showthread.php?t=2287136
how to use efs1.bin efs2.bin and efs3 bin to restore imei
cschmitt said:
Ok, first off did you follow the other post regarding repairing /efs/imei/keystr file if necessary?
Otherwise, sounds like the hidden EFS partitions are corrupt.
Do you have a recent nandroid backup (prior to the unlock attempt)? If so, check the data.ext4.tar for an efs1.bin, efs2.bin, and efs3.bin located in /data/qcks directory.
If you have the efs?.bin files I can walk you through flashing them back into the EFS partitions on the phone. That'll restore the IMEI.
Click to expand...
Click to collapse
Hi,
I found myself in exact same situation (0 IMEI, corruct EFS, no nv_data.bin files on i727). I however have a nandroid backup and I found and extracted the efs1-3.bin files from /data directory.
Could you please let me know how to flash them into the EFS partition to restore the IMEI.
you are my last hope !!!!!
bmyury said:
Hi,
I found myself in exact same situation (0 IMEI, corruct EFS, no nv_data.bin files on i727). I however have a nandroid backup and I found and extracted the efs1-3.bin files from /data directory.
Could you please let me know how to flash them into the EFS partition to restore the IMEI.
you are my last hope !!!!!
Click to expand...
Click to collapse
howto backup/restore efs
dont know if it will fix the imei though
Hi, I have a t959v and I have been trying to restore my IMEI (that's because I was able to backup my /efs partition).
However, after I flash CM 10.1 for my device, my IMEI is gone, or has turned to 0000000.... or has turned to ASCII characters that I couldn't even read. I tried restoring my nv_data.bin file, done everything I could(googled and tried so many posts, I've lost count already.) and ended up with still, a corrupted/missing IMEI. Well after tinkering with my device, I've found out that the reason why my nv_data.bin (5.2 Mb) corrupts as I transfer it to the /efs partition--it's because my /efs partition is a little bit small, that's why my nv_data.bin ends up in an incompleted transfer state(corrupted file). From 5.2Mb, it falls to around 3-4Mb. No, it's not compressed or anything, it's cut-off, or "cropped" if it's the right term(which I doubt). Now, the my question is, is it possible to resize or grow my /efs partition? If yes, then how? First of all, thanks for spending some time in reading my post. Now, could anybody help me? or if it's such a pain to do, is there an alternative to CM 10.1 that has minimal glitches or bugs? 'Coz it's a pity if I couldn't upgrade from GB. The hardware of this phone is good enough, but the firmware is kinda frustrating(slow, freezes, and worst of all, GB), don't get me wrong, I don't hate GB but for the hardware of this phone, it's too good to just stay in GB. Thanks again!
Reflash back to gingerbread. That should restore your ieme number. Than try again.
Sent from my BNTV250A using XDA Free mobile app
cryzone77 said:
Hi, I have a t959v and I have been trying to restore my IMEI (that's because I was able to backup my /efs partition).
However, after I flash CM 10.1 for my device, my IMEI is gone, or has turned to 0000000.... or has turned to ASCII characters that I couldn't even read. I tried restoring my nv_data.bin file, done everything I could(googled and tried so many posts, I've lost count already.) and ended up with still, a corrupted/missing IMEI. Well after tinkering with my device, I've found out that the reason why my nv_data.bin (5.2 Mb) corrupts as I transfer it to the /efs partition--it's because my /efs partition is a little bit small, that's why my nv_data.bin ends up in an incompleted transfer state(corrupted file). From 5.2Mb, it falls to around 3-4Mb. No, it's not compressed or anything, it's cut-off, or "cropped" if it's the right term(which I doubt). Now, the my question is, is it possible to resize or grow my /efs partition? If yes, then how? First of all, thanks for spending some time in reading my post. Now, could anybody help me? or if it's such a pain to do, is there an alternative to CM 10.1 that has minimal glitches or bugs? 'Coz it's a pity if I couldn't upgrade from GB. The hardware of this phone is good enough, but the firmware is kinda frustrating(slow, freezes, and worst of all, GB), don't get me wrong, I don't hate GB but for the hardware of this phone, it's too good to just stay in GB. Thanks again!
Click to expand...
Click to collapse
Interesting...
champ1919 said:
Reflash back to gingerbread. That should restore your ieme number. Than try again.
Click to expand...
Click to collapse
Sure, but that doesn't answer the original question. Going back to BML (which was on Gingerbread, of course) will restore the original /efs partition. This is because all of the MTD installs do not overwrite the original BML /efs partition.
Now, the concerning issue is that the nv_data.bin shouldn't be getting any bigger then the original (I don't have my sgs4g on hand to verify), but what may have happened is yaffs2 partition options in the kernel may not be the same or formatting may have added more partition data to the filesystem layout that makes the available free space on the partition less. (does this paragraph not make sense? If so, ask and I'll go into more detail)
So, let me ask you to do a test.
WARNING!!! Make sure you backup the EFS partition while on GB before emptying the directory!
Backup EFS (do this from recovery with adb shell):
Code:
su -
mount /efs
mount /sdcard
cd /
tar cf /sdcard/efs-backup.tar /efs
Go back to stock GB. There are Cne-Clicks I made to do this. Root the install and post the output of:
Code:
su -
rm -rf /efs/* /efs/.*
df /efs
Restore EFS (again, from recovery, adb shell):
Code:
su -
mount /efs
mount /sdcard
cd /
tar xf /sdcard/efs-backup.tar
Next, do the same for cm-9.1.0.
After that, do the same with which ever cm-10 or 4.4.x kernel you're using.
Post all of the values here and lets debug that way. I'll bet you that the available free space and total size are DIFFERENT when the partition is empty.
You don't need to restore the EFS on MTD installs, but MAKE VERY SURE you restore the EFS on the BML (Gingerbread) install!!!
Maybe also try different CM10.x and 4.4.x kernels and see if there is a difference. For each test, note which kernel, which rom. Also for each test, flash back to Gingerbread (bml, from the oneclick) before flashing a new rom!
All the nv_data.bin files I have are 262.1kB.
The tar backups the installtion script creates for you should be 700kB or less.
It sounds like something went seriously wrong with the nv_data.bin file you are trying to restore, so I recommend you follow the advice @champ1919 gave you and go back to gingerbread an flash your ROM again.
After you flash make sure that the nv_data.bin file under /efs/root/afs/settings/nv_data.bin is exactly 262.1kB. If that's the case then save the efs backup the install script made for you in a safe place.
Mine from froyo are 256.0 KB for locked and 260 for unlocked., weird..
champ1919 said:
Mine from froyo are 256.0 KB for locked and 260 for unlocked., weird..
Click to expand...
Click to collapse
Interesting. I think all the ones I got were from phones built at around the same time since they have similar text in the nv_data files.
The locked/unlocked files should be the exact same file size every time. All the tends to change is a single 1 in the file becomes a 0 to unlock it.
I had stored them in Dropbox. I betcha one is from the vibrant I lost, but, I thought I deleted it so I would not goof. As soon as I can get to a PC, I'll dig into it somemore. I wonder who wrote that guide years a go on how to hexedit that file. I should give them another thanks.
bhundven said:
Interesting...
Sure, but that doesn't answer the original question. Going back to BML (which was on Gingerbread, of course) will restore the original /efs partition. This is because all of the MTD installs do not overwrite the original BML /efs partition.
Now, the concerning issue is that the nv_data.bin shouldn't be getting any bigger then the original (I don't have my sgs4g on hand to verify), but what may have happened is yaffs2 partition options in the kernel may not be the same or formatting may have added more partition data to the filesystem layout that makes the available free space on the partition less. (does this paragraph not make sense? If so, ask and I'll go into more detail)
So, let me ask you to do a test.
WARNING!!! Make sure you backup the EFS partition while on GB before emptying the directory!
Backup EFS (do this from recovery with adb shell):
Code:
su -
mount /efs
mount /sdcard
cd /
tar cf /sdcard/efs-backup.tar /efs
Go back to stock GB. There are Cne-Clicks I made to do this. Root the install and post the output of:
Code:
su -
rm -rf /efs/* /efs/.*
df /efs
Restore EFS (again, from recovery, adb shell):
Code:
su -
mount /efs
mount /sdcard
cd /
tar xf /sdcard/efs-backup.tar
Next, do the same for cm-9.1.0.
After that, do the same with which ever cm-10 or 4.4.x kernel you're using.
Post all of the values here and lets debug that way. I'll bet you that the available free space and total size are DIFFERENT when the partition is empty.
You don't need to restore the EFS on MTD installs, but MAKE VERY SURE you restore the EFS on the BML (Gingerbread) install!!!
Maybe also try different CM10.x and 4.4.x kernels and see if there is a difference. For each test, note which kernel, which rom. Also for each test, flash back to Gingerbread (bml, from the oneclick) before flashing a new rom!
Click to expand...
Click to collapse
thanks for the fast response bhundven and the rest...
i apologize for not being able to reply as soon as you posted.
going back... i tried reflashing to stock and backed up my efs... however, when i looked at how big it was as a tar(ive tried making an rfs then put it into a tar. this is from the commands cat /dev/block/stl3 > /sdcard/efs.rfs or something like that. im sure that code came from a post here in xda too.) its size is 6.2mb.
and also... i have the log files of my cm10.1 upgrade attempt. posting it in case it would help...
also tried reflashing to stock ang flashing slimkat but the problem persists.
thanks for giving your time in helping me. i will try to reply as soon as i can. thanks again.
Q: is t959v the same as vibrant? been googling but posts are really confusing.. XD
cryzone77 said:
thanks for the fast response bhundven and the rest...
i apologize for not being able to reply as soon as you posted.
going back... i tried reflashing to stock and backed up my efs... however, when i looked at how big it was as a tar(ive tried making an rfs then put it into a tar. this is from the commands cat /dev/block/stl3 > /sdcard/efs.rfs or something like that. im sure that code came from a post here in xda too.) its size is 6.2mb.
Click to expand...
Click to collapse
Nope, that does not work. That is also not what my directions said to do.
cryzone77 said:
and also... i have the log files of my cm10.1 upgrade attempt. posting it in case it would help...
also tried reflashing to stock ang flashing slimkat but the problem persists.
thanks for giving your time in helping me. i will try to reply as soon as i can. thanks again.
Click to expand...
Click to collapse
You kinda buggered up the Quoting of the post, kinda hard to follow. So I removed what I wrote and only quoted what you said so it makes sense. But even after that, I can't really make sense of what you are doing and why you can't follow my directions?!?
cryzone77 said:
Q: is t959v the same as vibrant? been googling but posts are really confusing.. XD
Click to expand...
Click to collapse
It's not confusing at all. SGH-T959V (VibrantPlus) is not the same as SGH-T959 (Vibrant). They are not compatible, and flashing roms between the two will lead to bricks. Make sure that under the battery it says: SGH-T959V
The only thing these two devices have in common is their original provider: T-Mobile
Otherwise, go to the right forum for your phone before following any directions in this forum.
champ1919 said:
Reflash back to gingerbread. That should restore your ieme number. Than try again.
Sent from my BNTV250A using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the quick reply!
Well, the reason why I was trying to flash CM10.1 is to upgrade from GB so if I were to reflash to GB then I would've defeated my purpose.
But, I did try that, and backed up my EFS so as to restore it later on after I have flashed CM10.1 but to no avail.
cryzone77 said:
Thanks for the quick reply!
Well, the reason why I was trying to flash CM10.1 is to upgrade from GB so if I were to reflash to GB then I would've defeated my purpose.
But, I did try that, and backed up my EFS so as to restore it later on after I have flashed CM10.1 but to no avail.
Click to expand...
Click to collapse
Which phone model do you have?
Im running the new slimkat with no issue. Fb's cm11 was just as good. I bounce between those and back to GB when I need tv out with no issues.
Sent from my BNTV250A using XDA Free mobile app
bhundven said:
Nope, that does not work. That is also not what my directions said to do.
You kinda buggered up the Quoting of the post, kinda hard to follow. So I removed what I wrote and only quoted what you said so it makes sense. But even after that, I can't really make sense of what you are doing and why you can't follow my directions?!?
It's not confusing at all. SGH-T959V (VibrantPlus) is not the same as SGH-T959 (Vibrant). They are not compatible, and flashing roms between the two will lead to bricks. Make sure that under the battery it says: SGH-T959V
The only thing these two devices have in common is their original provider: T-Mobile
Otherwise, go to the right forum for your phone before following any directions in this forum.
Click to expand...
Click to collapse
Im sorry for the messed up reply sir, and thanks again for your reply,
Just to confirm, my device is INDEED T959V.
I did the cat > /sdcard/efs.rfs bla bla bla thing in the hope to make an ODIN flashable "fix" in the hope of getting my IMEI and baseband fixed.
And, just as you said, it didn't work. I also tried erasing the /efs by erase_image then mkdir -p /efs and then cd /efs then tar xf /sdcard/efs.tar but that also produced a "cropped" nv_data.bin. Im sorry I can't try your directions as of now because I'm currently using my phone for work, however, I will do as you said as soon as I can free up my device.
Q: Do I need to take my backup before I flash a custom kernel? or is it ok if back it up while using a custom kernel?
Q: So T959V is VibrantPlus, is it the same as Samsung Galaxy S 4G?
Q: So if T959V is VibrantPlus, should I look for ROMs with the naming convention of <rom name>-vibrantplusmtd?
champ1919 said:
Which phone model do you have?
Im running the new slimkat with no issue. Fb's cm11 was just as good. I bounce between those and back to GB when I need tv out with no issues.
Sent from my BNTV250A using XDA Free mobile app
Click to expand...
Click to collapse
I have a T959V.
I tried the SlimKat and SlimSabre but I still got no IMEI even after manual restore. I also tried the CM11 and still have the same problem.
So, when you go back to gingerbread, your number is still hosed?
Sent from my BNTV250A using XDA Free mobile app
cryzone77 said:
Im sorry for the messed up reply sir, and thanks again for your reply,
Just to confirm, my device is INDEED T959V.
I did the cat > /sdcard/efs.rfs bla bla bla thing in the hope to make an ODIN flashable "fix" in the hope of getting my IMEI and baseband fixed.
Click to expand...
Click to collapse
I have no clue where you got those directions.
cryzone77 said:
And, just as you said, it didn't work. I also tried erasing the /efs by erase_image then mkdir -p /efs and then cd /efs then tar xf /sdcard/efs.tar but that also produced a "cropped" nv_data.bin. Im sorry I can't try your directions as of now because I'm currently using my phone for work, however, I will do as you said as soon as I can free up my device.
Click to expand...
Click to collapse
Here it sounds like you are mixing up directions.
cryzone77 said:
Q: Do I need to take my backup before I flash a custom kernel? or is it ok if back it up while using a custom kernel?
Click to expand...
Click to collapse
Go back to stock gingerbread with my oneclick. Read all of the directions here first.
cryzone77 said:
Q: So T959V is VibrantPlus, is it the same as Samsung Galaxy S 4G?
Click to expand...
Click to collapse
Yes
cryzone77 said:
Q: So if T959V is VibrantPlus, should I look for ROMs with the naming convention of <rom name>-vibrantplusmtd?
Click to expand...
Click to collapse
No, we don't call it vibrantplus, because it cause so much confusion with vibrant. we call it galaxys4g for bml or galaxys4gmtd for mtd.
champ1919 said:
So, when you go back to gingerbread, your number is still hosed?
Click to expand...
Click to collapse
I'd like to know the answer to this as well. Good question!
bhundven said:
I have no clue where you got those directions.
Here it sounds like you are mixing up directions.
Go back to stock gingerbread with my oneclick. Read all of the directions here first.
Yes
No, we don't call it vibrantplus, because it cause so much confusion with vibrant. we call it galaxys4g for bml or galaxys4gmtd for mtd.
I'd like to know the answer to this as well. Good question!
Click to expand...
Click to collapse
Well I've tried many posts about restoring nv_data.bin but none of them seems to work. I even tried to edit nv_data.bin by hex. That's how desperate I am to upgrade. XD
By hosed, you mean corrupted or invalid? I use OneClick Heimdall by sir bhundven I believe..
and to answer the question, I get my IMEI and baseband back everytime I flash the OneClick. It's when I try to upgrade to CM++ that I get the null baseband and IMEI.
and to clarify, I got that backup process directions from this post http://forum.xda-developers.com/showthread.php?t=859914
cryzone77 said:
Well I've tried many posts about restoring nv_data.bin but none of them seems to work. I even tried to edit nv_data.bin by hex. That's how desperate I am to upgrade. XD
By hosed, you mean corrupted or invalid? I use OneClick Heimdall by sir bhundven I believe..
and to answer the question, I get my IMEI and baseband back everytime I flash the OneClick. It's when I try to upgrade to CM++ that I get the null baseband and IMEI.
Click to expand...
Click to collapse
Ok, so you go back to gingerbread and get your imei back.
cryzone77 said:
and to clarify, I got that backup process directions from this post http://forum.xda-developers.com/showthread.php?t=859914
Click to expand...
Click to collapse
NO This is not the right place to look for help. Although the 'Galaxy S 4G' is a 'Galaxy S' based-device, it is VERY different from the i9000!!!
Do not use instructions from other device forums!!!
We have documented a lot for this phone in this device forum and on our wiki
As I mentioned before (in this thread) instructions on backing up your efs, and restoring it. Use my instructions and let us know in this thread if you have any problems!
bhundven said:
Ok, so you go back to gingerbread and get your imei back.
NO This is not the right place to look for help. Although the 'Galaxy S 4G' is a 'Galaxy S' based-device, it is VERY different from the i9000!!!
Do not use instructions from other device forums!!!
We have documented a lot for this phone in this device forum and on our wiki
As I mentioned before (in this thread) instructions on backing up your efs, and restoring it. Use my instructions and let us know in this thread if you have any problems!
Click to expand...
Click to collapse
1st, YES I got my IMEI and baseband back, but its a shame if I can't upgrade to CM++(because I don't get my IMEI and baseband after flashing meaning I can't use my phone for work.) because it's a cool rom, it has everything I'm looking for in a custom rom.
AND yeah, I wasn't aware that they were THAT different. Anyways, thanks for pointing that out.
Q: Is there an upgrade path or something that I need to do aside from the standard flashing procedure for these roms?
Bhundven's modified kernel should give you root. You could skip that step of using the oneclickroot and use the heimdall one click (of his kernel) and get cwm & root in one step. It's linked in the link he gave you.
After you install cwm, is that when you loose the imei number? Are you letting the phone fully boot? How were you getting cwm in order to flash the cm?
champ1919 said:
Bhundven's modified kernel should give you root. You could skip that step of using the oneclickroot and use the heimdall one click (of his kernel) and get cwm & root in one step. It's linked in the link he gave you.
After you install cwm, is that when you loose the imei number? Are you letting the phone fully boot? How were you getting cwm in order to flash the cm?
Click to expand...
Click to collapse
Sorry,
What I meant by OneClick is using Heimdall in flashing the purely stock GB rom. After that, I root using Framaroot(successful) then I flash a custom kernel(bhundven's blastoff...IMEI and baseband still ok after this), then I flash CM++ ROM, this is where it gets ugly--I lose my IMEI(null) and baseband(also null). and YES I let the phone fully boot, I even wait around 15mins and try to turn the radio on and off to see if I got my IMEI and baseband back, I also tried taking out the battery and letting the phone loose all it's power and then turning it on, again, to no avail. And to answer the other question, I get CWM through the blastoff kernel.
Hi everyone. Got a bootloop, so had to format the persist partition. I made a backup of it with adb before formatting, but forgot to save permissions/owners of every file.
Could anyone just make an "ls -l" in all folders of /persist? Thank you.
P.S. I'd appreciate if anyone makes a full image backup of /dev/block/platform/msm_sdcc.1/by-name/persist
To make it, just do a dd if=/dev/block/platform/msm_sdcc.1/by-name/persist of=/sdcard/persist.img and post the file on any file hosting.
Slavon-93 said:
Hi everyone. Got a bootloop, so had to format the persist partition. I made a backup of it with adb before formatting, but forgot to save permissions/owners of every file.
Could anyone just make an "ls -l" in all folders of /persist? Thank you.
P.S. I'd appreciate if anyone makes a full image backup of /dev/block/platform/msm_sdcc.1/by-name/persist
To make it, just do a dd if=/dev/block/platform/msm_sdcc.1/by-name/persist of=/sdcard/persist.img and post the file on any file hosting.
Click to expand...
Click to collapse
Why don't you just try doing a factory reset after bootloop?
Anyways,here's the file that you were asking for-
https://drive.google.com/file/d/0BxysuRdzsJeWNi02b0NmSUVwbE0/view?usp=drivesdk
Mr.Ak said:
Why don't you just try doing a factory reset after bootloop?
Anyways,here's the file that you were asking for-
https://drive.google.com/file/d/0BxysuRdzsJeWNi02b0NmSUVwbE0/view?usp=drivesdk
Click to expand...
Click to collapse
Because it was a bootloop just right after a flashed the ROM on a completely clean factory reset device. Now I understand that it was a problem with the ROM, that's why I made a backup. And your image will help me know if I miss any files in this partition and know their permissions.
Slavon-93 said:
Because it was a bootloop just right after a flashed the ROM on a completely clean factory reset device. Now I understand that it was a problem with the ROM, that's why I made a backup. And your image will help me know if I miss any files in this partition and know their permissions.
Click to expand...
Click to collapse
Which ROM?
Mr.Ak said:
Which ROM?
Click to expand...
Click to collapse
hyperUnicorns. For some reason any build I try to install since the end of June gives me reboots. I thought it was some incompatibility with Multirom 33e and MIUI, but after I flashed the full Cyanogen package, nothing changed, that led me to google and some posts, saying it can be a damage of persist partition.
Slavon-93 said:
hyperUnicorns. For some reason any build I try to install since the end of June gives me reboots. I thought it was some incompatibility with Multirom 33e and MIUI, but after I flashed the full Cyanogen package, nothing changed, that led me to google and some posts, saying it can be a damage of persist partition.
Click to expand...
Click to collapse
That rom worked fine for me..maybe it doesn't support multi-rom.
I think you should ask on the rom's thread.
hi , as u can tell by the tittle , i just flashed Paranoid Andrid 7.2.3 which does not support F2fs. i realize it in the middle of flashing that my phone is on F2fs format not ext4 , now its stuck on oneplus logo , but i can still boot into TWRP. and when i open file manager on TWRP , there's nothing in there , tried to use my laptop too , yet still nothing there. any chance i recover my data plz or fix my phone ? thxx
Try the "fsck.f2fs" command from TWRP's terminal, with the -a and/or -f arguments. I've never needed to use it, but it's worth a try.
thx for ur reply . any chance of my data will be back ? *bad englsh
No idea. But it can't hurt to try.
As for the device (partition) names, for our device:
/dev/block/mmcblk0p16 (cache)
/dev/block/mmcblk0p14 (system)
/dev/block/mmcblk0p28 (data)
Make sure to unmount these partitions before you run any commands on them.
Let me know how it goes for you.
but how about the internal ?
update : tried to use fsck.f2fs but it says Error : Device not specified
Azhar_Fahry said:
but how about the internal ?
Click to expand...
Click to collapse
Internal data is a subdirectory of /data. So by targeting the data partition, you are also implicity targeting your personal data as well.
Sent from my A0001 using Tapatalk
---------- Post added at 07:20 AM ---------- Previous post was at 07:18 AM ----------
Azhar_Fahry said:
but how about the internal ?
update : tried to use fsck.f2fs but it says Error : Device not specified
Click to expand...
Click to collapse
Specify the data partition as mentioned above.
Sent from my A0001 using Tapatalk
yep , done , it fix my phone , but i think i still lost all the files
Azhar_Fahry said:
yep , done , it fix my phone , but i think i still lost all the files
Click to expand...
Click to collapse
Darn. Sorry to hear that.
Maybe someone else here has more information.
Sent from my A0001 using Tapatalk
aight thx so much for ur help btw at least i studied from my own mistake