Related
First of all, this is not my work. I only compiled it.
This is the usual ClockworkMod recovery, compiled from the CM7 sources with additions/modifications by j_r0dd. What I've done is only to compile it for the HTC Desire. For details, check out the link to j_r0dd's original thread for the Nexus S.
The credits go to Koush for the recovery itself and to j_r0dd for the modifications.
j_r0dd said:
This is based on the latest CM7 source which I modified for myself. I take no credit for the recovery whatsoever, but I will take all the blame for my mods . We all know this is Koush's hard work. Just some things were driving me crazy personally. First was the confirmation menu. I really got sick of scrolling through all those "No"s just to flash something, so i changed it for me personally and just thought I would share. I also created a proper wipe menu. I got sick of some wipes in the main menu and the rest in the "advanced" menu. I made this more Amon_RA like. See the attached screenshot for my changes. That change has led to a few others by me. flash with fastboot or flash_image. THESE ARE NOT IN ROM MANAGER. Also if you have an issue with this take it up with me NOT Koush.
Click to expand...
Click to collapse
Original Nexus S thread with changelog here.
Download:
recovery-clockwork-5.0.2.7.111102-j_r0dd_mod-bravo.zip
(old) recovery-clockwork-5.0.2.7.111027-j_r0dd_mod-bravo.zip
Change log:
02-Nov-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo again (some bugfixes)
Added option to wipe cache partition and dalvik cache at the same time
27-Oct-2011 (v5.0.2.7):
Merged 5.0.2.7 sources from CM7 repo (support for internal/external sdcard in backup/restore)
07-Oct-2011 (v5.0.2.6):
Rearranged wipe menu to avoid accidental factory wipes
Added "Reboot Bootloader"
Moved SD Card partitioning into a function of its own for both int/ext SD card
Merged 5.0.2.6 sources from CM7 repo
Added a menu choice of ext2/ext3/ext4 when partitioning SD card
25-Sep-2011 (v5.0.2.3):
Updated to j_r0dd's 5.0.2.3 version. Currently no changes made by myself.
17-Jun-2011 (v4.0.0.5):
Moved the "Wipe data/factory reset" to the bottom of the wipe menu to reduce the risk of accidental factory wipes.
19-Jun-2011 (v4.0.0.5):
Added "Reboot bootloader" option in advanced menu.
Added the ext4 modifications kindly supplied by roalex. Needs testing. Please make a proper nandroid backup with a proven working recovery version before trying this.
20-Jun-2011 (v4.0.0.5):
Added "Show log" in the advanced menu. This can help when reporting errors here. Use it.
21-Jun-2011 (v4.0.0.5.z110621):
Reverted and correctly added roalex's ext4 additions.
Modified recovery.fstab for ext4 support on some devices.
23-Jun-2011 (v4.0.0.5.z110623):
Removed NULL ext3 in recovery.fstab to hopefully get ext4 working properly.
06-Jul-2011 (v4.0.0.5.z110706):
Added "Advanced backup". Now you can backup/restore individual partitions.
Some other commits from other devs in github
Changed file limit from 10000 to 50000 in unyaffs. Should help when restoring large data partitions fails.
17-Jul-2011 (v4.0.1.0.110717):
Rebased completely on j_r0dd's 4.0.1.0 source and removed roalex's ext4 additions, as it wasn't working for everyone. Now trying with the original ext4 support which is included in CWM.
20-Jul-2011 (v4.0.1.4.110720):
Bug fixes
Disclaimer
These recoveries are compiled using the latest commits from koush, j_r0dd and others. That means they haven't been thoroughly tested and might have minor/major issues. I take no responsibility for any damages this thing might cause, but most things should work as intended. If you want something guaranteed to work, I think you should stick with one of the older versions.
Source code available here.
it works... thank you
suiller said:
it works... thank you
Click to expand...
Click to collapse
Superb! I'll change the OP to confirmed then.
bit hesitant to flash this, had a few usb bricks from recent clockworks. reckon some people who have flashed it could nandroid backup then restore and check it all works?
sjknight413 said:
bit hesitant to flash this, had a few usb bricks from recent clockworks. reckon some people who have flashed it could nandroid backup then restore and check it all works?
Click to expand...
Click to collapse
Well, like I said, I can't guarantee that it works, especially since I have no Desire to test it on. I've used j_r0dd's source which is based on Koush's source for the official CM7 3.2.0.0 ClockworkMod recovery. It might work, or it might not work. Testing it is up to each person.
zyonee said:
Well, like I said, I can't guarantee that it works, especially since I have no Desire to test it on. I've used j_r0dd's source which is based on Koush's source for the official CM7 3.2.0.0 ClockworkMod recovery. It might work, or it might not work. Testing it is up to each person.
Click to expand...
Click to collapse
dont get me wrong, i didnt mean any disrespect looks like you have done good work! but i have only had my desire 4 days and already had 2 usb bricks! will probably test in a couple of days
sjknight413 said:
dont get me wrong, i didnt mean any disrespect looks like you have done good work! but i have only had my desire 4 days and already had 2 usb bricks! will probably test in a couple of days
Click to expand...
Click to collapse
Don't worry about it, I wasn't offended in any way. I'm wondering though if the USB bricks are caused by flashed (.img) recoveries. As I remember it, USB bricks were common with the earliest attempts to run recoveries by uploading the recovery binary to the phone's RAM while having to keep it plugged in to the computer.
well i know i got the usb bricks whilst restoring nandroids when my phone wasn't plugged in. that help in any way?
sjknight413 said:
well i know i got the usb bricks whilst restoring nandroids when my phone wasn't plugged in. that help in any way?
Click to expand...
Click to collapse
Maybe your misc partition got overwritten with garbage. In my opinion, nandroid shouldn't touch this partition. The USB brick issue is usually caused by a corrupt misc partition.
Sent from my Nexus S using Tapatalk
yeah i dont really know why it does, its easily fixable by reflashing the mtd0.img file generated from your cid and rom version though, its just a massive nuisance!
sjknight413 said:
yeah i dont really know why it does, its easily fixable by reflashing the mtd0.img file generated from your cid and rom version though, its just a massive nuisance!
Click to expand...
Click to collapse
You should check your nandroid backup folder. If there's a misc.img or something like it, maybe you should move that file elsewhere. That way, nandroid shouldn't overwrite your misc (mtd0) partition. I'm only guessing that it does handle that partition.
Is it wiping sd-ext correctly? "Official" 3.2.0.0 posted here some times ago restarted recovery upon sd-ext wipe.
teorouge said:
Is it wiping sd-ext correctly? "Official" 3.2.0.0 posted here some times ago restarted recovery upon sd-ext wipe.
Click to expand...
Click to collapse
No idea, not using sd-ext in any of my phones.
teorouge said:
Is it wiping sd-ext correctly? "Official" 3.2.0.0 posted here some times ago restarted recovery upon sd-ext wipe.
Click to expand...
Click to collapse
I'd like to know this too. Can anyone who's upgraded to this version of 3.2.0.0 let us know their findings?
Jameswgm said:
I'd like to know this too. Can anyone who's upgraded to this version of 3.2.0.0 let us know their findings?
Click to expand...
Click to collapse
It'll probably behave the same way, seeing as this one only changes the menus, I think.
Updated OP to version 4.0.0.0.
Thanks, please see http://forum.xda-developers.com/showpost.php?p=14598355&postcount=357 .
You should mod 3.1.0.1, no later CWM worked ok.
teorouge said:
Thanks, please see http://forum.xda-developers.com/showpost.php?p=14598355&postcount=357 .
You should mod 3.1.0.1, no later CWM worked ok.
Click to expand...
Click to collapse
Yeah, I got that even on my Nexus S.. I'm just cloning & compiling. Got no idea how to downgrade to an earlier version. Limited programming skills.
I fixed the SD card mounting bug. Please re-download 4.0.0.0.
Still buggy. Each time you leave a file list, you'll need to "adb shell umount /sdcard" from your computer. Looking into it.
Added back the 3.2.0.0 version in the OP so you won't have the /sdcard mounting issue. Hopefully it can be resolved soon, so we can start using the 4.0.0.0 version. Sorry for the inconvenience.
Special thanks goes out to everyone who tested for me.
I do not have the device, so I rely heavily on testers to report any bugs.
Here is CWM for the SK4G.
You will need to modify your stock recovery binary to be able to use CWM.
Kernel Devs can also compile CWM into their kernel by extracting the update.zip and building it into their initramfs.
To replace your stock recovery binary with the modified binary:
download this file
DEAD. USE BALI KERNEL
Exatract and take the recovery binary file inside of it and use root explorer or adb push the file to /system/bin.
DO NOT delete the current one there, or rename any files.
Just overwrite it.
I would however, recommend getting Android Commander from www.androidcommander.com It's a lot easier, and a lot more useful.
CWM Final
DEAD. USE BALI KERNEL
Place in the root of your SD.
You can now use Quick Boot from the market, or adb reboot recovery to boot into CWM
I have sent Koush the device tree to have the official update.zip supported within Rom Manager.
UNTESTED:
You can also take the contents from the update.zip and replace the contents that are in noobnl's recovery rerouter/root.
Again, I haven't tested that due to not having the device.
First! Congrats krylon and thank you
Krylon: link 404'd
Sent from my SGH-T839 using XDA App
Thank you very mucho!
Sent from my SGH-T839 using XDA App
i cant dowload recovery zip
I don't know if its just me but the first link is not working
Sent from my SGH-T839 using XDA App
Guys... add a /sk4g to the first url so its like the 2nd url... thank me later
Sent from my SGH-T839 using XDA App
http://www.krylon360.com/file_host/sk4g/recovery.zip
mattpall said:
Guys... add a /sk4g to the first url so its like the 2nd url... thank me later
Sent from my SGH-T839 using XDA App
Click to expand...
Click to collapse
Datlilboricua said:
http://www.krylon360.com/file_host/sk4g/recovery.zip
Click to expand...
Click to collapse
Fixed. thanks.
Thanks lilboricua
Sent from my SGH-T839 using XDA App
Krylon... quick question... how much effort would it be to make a "reorient kernal" similar to wat the captivate had so it could use i9000 roms. Since this phone is basically a galaxy s...
Sent from my SGH-T839 using XDA App
Nand backup error
with the new recovery (remapped buttons) i tried to do a nand backup and it wouldnt start and it'd auto matically say error while backing up boot image... can anyone see if they come across this aswell ..
mattpall said:
Krylon... quick question... how much effort would it be to make a "reorient kernal" similar to wat the captivate had so it could use i9000 roms. Since this phone is basically a galaxy s...
Sent from my SGH-T839 using XDA App
Click to expand...
Click to collapse
this phone is not basically a galaxy S. heck, when the SGS4G came out people said it was basically a vibrant. NOPE. Wrong.
It would be hard to do, but might be doable.
ayoteddy said:
with the new recovery (remapped buttons) i tried to do a nand backup and it wouldnt start and it'd auto matically say error while backing up boot image... can anyone see if they come across this aswell ..
Click to expand...
Click to collapse
didn't you test this?
mattpall said:
Krylon... quick question... how much effort would it be to make a "reorient kernal" similar to wat the captivate had so it could use i9000 roms. Since this phone is basically a galaxy s...
Sent from my SGH-T839 using XDA App
Click to expand...
Click to collapse
if we could get a stock kernel with just the ext4 patch so we would be able to run our system, data and cache on ext4 i'd be pleased enough . idk if anyone with this phone would be able to rebuild the kernel with that patch but if so our phones would easily be 3x faster
I also see the same problem. I didn't think to test backups. What was all changed from the working version to the current version? all that needed to be changed was the lun map and BOARD_USES_CUSTOM_KEYMAP
krylon360 said:
didn't you test this?
Click to expand...
Click to collapse
yes i tested the original one completely and everything worked, the new one you sent me i only tested the buttons and mapping which were fine . but it seems now the nand backup/restore has a problem.
Edit: i just made another nand backup with the original recovery without the back button mapping and it works. seems the edited one got the backup/restore broken somehow
ayoteddy said:
if we could get a stock kernel with just the ext4 patch so we would be able to run our system, data and cache on ext4 i'd be pleased enough . idk if anyone with this phone would be able to rebuild the kernel with that patch but if so our phones would easily be 3x faster
Click to expand...
Click to collapse
not hard to do at all. unpack, add in ext4 mount options, repack, then flash kernel, and script to convert.
sduvick said:
I also see the same problem. I didn't think to test backups. What was all changed from the working version to the current version? all that needed to be changed was the lun map and BOARD_USES_CUSTOM_KEYMAP
Click to expand...
Click to collapse
Omg didn't test backups? :facepalm
Sent from my SGH-T839 using XDA App
ayoteddy said:
yes i tested the original one completely and everything worked, the new one you sent me i only tested the buttons and mapping which were fine . but it seems now the nand backup/restore has a problem.
Edit: i just made another nand backup with the original recovery without the back button mapping and it works. seems the edited one got the backup/restore broken somehow
Click to expand...
Click to collapse
the new one all I did was change key mapping and UMS path... odd.
Ok I did the recovery to system bin and did the update it changed to cwm and I tried nand errors out I reboot and reboot back into recovery I'm back to stock recovery
Sent From My Rooted Sidekick 4g Premium XDA App
The Goal: To create a CWM flash-able .zip that will convert a BML formatted phone to MTD without the need to be included in a rom, creating a standard and simplicity for end-users.
RDU
ROM DEVELOPERS UNITED
AS ONE
CWM BML to MTD Conversion Utility​Supported ROMs:
- Any BML Setup
So here's how it works:
This file will convert your phone's kernel and boot recovery to MTD. Afterwards, you will be able to flash an MTD rom.
ALWAYS make a backup of your data before flashing anything.
If you flash this over an already MTD rom, it will simply abort.
The Latest Version Here. After it finishes, your phone will be stuck in a loop. Pull the battery and 3-finger back into recovery to flash an MTD rom.
UPDATE: (--/--)
Further ideas or customizations from fellow rom developers welcome.
First
This sounds vary usefull on my firends Epics. I think it will speed thing up for me at times depending what they want
Sent from the Drivers Seat of my Suby txting and Driving doing 100MPH+ in a school zone! Ha.
zman519 said:
First
This sounds vary usefull on my firends Epics. I think it will speed thing up for me at times depending what they want
Sent from the Drivers Seat of my Suby txting and Driving doing 100MPH+ in a school zone! Ha.
Click to expand...
Click to collapse
Please note, this is a test version.
It's based on a version I used myself, but being on MTD, I can't test it easily.
There are 3 current scenarios it could yield:
1. Nothing happens.
2. It works perfectly.
3. It works, but puts the phone into a bootloop. This is what the old version did to me... Pop the battery. Boot into recovery. Profit.
So this would theoretically convert a BML ROM to MTD on a person's phone. Sounds great.
As a note to all remember as always to back up before flashing ANYTHING.
Sent from my SPH-D700 using xda premium
kennyglass123 said:
So this would theoretically convert a BML ROM to MTD on a person's phone. Sounds great.
As a note to all remember as always to back up before flashing ANYTHING.
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Right now it should format your phone and prep it for a Rom. If it works properly, I'd like to rewrite it to convert and PRESERVE a BML Rom into an MTD Rom.
RandomKing said:
Please note, this is a test version.
It's based on a version I used myself, but being on MTD, I can't test it easily.
There are 3 current scenarios it could yield:
1. Nothing happens.
2. It works perfectly.
3. It works, but puts the phone into a bootloop. This is what the old version did to me... Pop the battery. Boot into recovery. Profit.
Click to expand...
Click to collapse
I understand ;-)
If my budy ever gets a new sdcard, I'll use his phone as a test dumey. The worst that could happen is I have to bust out the usb cable & fire up ODIN
Sent from the Drivers Seat of my Suby txting and Driving doing 100MPH+ in a school zone! Ha.
Ok so currently no data or apps are preserved. It is mostly a blank MTD slate?
Sent from my SPH-D700 using xda premium
kennyglass123 said:
Ok so currently no data or apps are preserved. It is mostly a blank MTD slate?
Sent from my SPH-D700 using xda premium
Click to expand...
Click to collapse
Yup. I need someone to confirm that it works properly. As I mentioned, I previously used a simpler version to convert myself to MTD and it worked, but it put me in a bootloop. I'm hoping to solve the bootloop so I can create a version to preserve a setup.
RandomKing said:
Yup. I need someone to confirm that it works properly. As I mentioned, I previously used a simpler version to convert myself to MTD and it worked, but it put me in a bootloop. I'm hoping to solve the bootloop so I can create a version to preserve a setup.
Click to expand...
Click to collapse
Well if you ran this and it put you in a boot loop, then it most likely worked properly since this would have formatted/converted your partition map to MTD. The BML rom would have either been erased or just unable to run due to the conversion.
Just a curious question here:
What would you need to do to actually convert an existing BML install to work on the MTD partition map?
nikon120 said:
Well if you ran this and it put you in a boot loop, then it most likely worked properly since this would have formatted/converted your partition map to MTD. The BML rom would have either been erased or just unable to run due to the conversion.
Just a curious question here:
What would you need to do to actually convert an existing BML install to work on the MTD partition map?
Click to expand...
Click to collapse
He said that it worked right in the post you quoted... lol
And I have no diea about the question... I'm kinda curious about this too...
nikon120 said:
Well if you ran this and it put you in a boot loop, then it most likely worked properly since this would have formatted/converted your partition map to MTD. The BML rom would have either been erased or just unable to run due to the conversion.
Just a curious question here:
What would you need to do to actually convert an existing BML install to work on the MTD partition map?
Click to expand...
Click to collapse
Because formatting destroys the existing file structure (it doesn't actually erase files, just overwrites the data that maps out the locations of those files), everything would need to be copied to a temporary location before converting the original location to the new partition type. Then the temp data (backup) would need to be copied back to the original location using the new format.
It is not possible to just change the format while leaving the data in place - those warnings on every format command (in every computerized device - windows, mac, etc) were not a design decision, but a result of a design limitation. The backup/format/restore method is the only way.
flastnoles11 said:
He said that it worked right in the post you quoted... lol
And I have no diea about the question... I'm kinda curious about this too...
Click to expand...
Click to collapse
He also said he was trying to solve the boot-loop problem, not a formatting problem. The clarification was not to assert that the formatting worked - the focus was on explaining the cause of the boot loop, to point out that there is no problem to be solved there because a BML kernel should boot loop when the rest of the partitions are freshly formatted MTD partitions.
The standard BML kernel can't read MTD, so the fact that those partitions are empty is irrelevant. Even if the partitions were converted without data loss (via a backup/convert/restore), the kernel would still need to be MTD-capable (so this by itself will not convert a BML rom to MTD)
Hopefully this clears up some of the confusion...
Sent from my SPH-D700 using XDA
nikon120 said:
Well if you ran this and it put you in a boot loop, then it most likely worked properly since this would have formatted/converted your partition map to MTD. The BML rom would have either been erased or just unable to run due to the conversion.
Just a curious question here:
What would you need to do to actually convert an existing BML install to work on the MTD partition map?
Click to expand...
Click to collapse
A kernel that supports MTD and copy all system, data and cache folder then paste it back after the conversion with the new kernel.
Sent from my SPH-D700 using xda premium
flastnoles11 said:
He said that it worked right in the post you quoted... lol
And I have no diea about the question... I'm kinda curious about this too...
Click to expand...
Click to collapse
Yes he did. I too read his reply.
My response to Random was that since he's put in the bootloop, then it worked for him due to the lack of converting the rom over. Therefore my reply implied that testing more won't hurt anything at all and would be good protocol, but may not be needed since it worked for him given his output.
styles420 said:
Because formatting destroys the existing file structure (it doesn't actually erase files, just overwrites the data that maps out the locations of those files), everything would need to be copied to a temporary location before converting the original location to the new partition type. Then the temp data (backup) would need to be copied back to the original location using the new format.
It is not possible to just change the format while leaving the data in place - those warnings on every format command (in every computerized device - windows, mac, etc) were not a design decision, but a result of a design limitation. The backup/format/restore method is the only way.
Click to expand...
Click to collapse
Ahh yea, I wasn't 100% sure if this was the case. Good breakdown though.
Doesn't seem to be working, I'll be uploading the version I use later on with directions.
I understand the theory, prepping a 100% BML setup for it's MTD future; just out of curiosity, Q: would there be a way to reverse this process so that if you arrive at your destination MTD ROM + change your mind, would it be possible to choose to convert an MTD ROM back to BML w/out having to ODIN (md5.tar + pit...........the way we do currently)?
BTW, am looking forward to testing your proposed conversion utility, just wondering.
nikon120 said:
Well if you ran this and it put you in a boot loop, then it most likely worked properly since this would have formatted/converted your partition map to MTD. The BML rom would have either been erased or just unable to run due to the conversion.
Just a curious question here:
What would you need to do to actually convert an existing BML install to work on the MTD partition map?
Click to expand...
Click to collapse
All I know is that it'd need an mtd kernel. Also, maybe it could work like rfs to ext4 where it backs everything up then restores and flashes an mtd compatible kernel. Theoretically, that should work on samsung tw based roms.
Sent from my SPH-D700 using XDA
Randomking, to fix the bootloop issue, try having it reboot recovery like the cm/miui mtd install scripts do (I think).
Sent from my SPH-D700 using XDA
sonarchist said:
I understand the theory, prepping a 100% BML setup for it's MTD future; just out of curiosity, Q: would there be a way to reverse this process so that if you arrive at your destination MTD ROM + change your mind, would it be possible to choose to convert an MTD ROM back to BML w/out having to ODIN (md5.tar + pit...........the way we do currently)?
BTW, am looking forward to testing your proposed conversion utility, just wondering.
Click to expand...
Click to collapse
Not possible since BML is proprietary. Odin is the only way to get this top secret partition information on our phone.
Sent from my SPH-D700 using xda premium
Thank You!
Edit
NVRMIND
I know in the new JB roms there is a mtd converter file and i was wondering if a bml convert file could be made
Sent from my Nice 'n' Stock-y Infuse 4G
isaiahe97 said:
I know in the new JB roms there is a mtd converter file and i was wondering if a bml convert file could be made
Sent from my Nice 'n' Stock-y Infuse 4G
Click to expand...
Click to collapse
I think its possible...if I knew more about conversions I would definatly look into it...I did however look at the updater.sh and it did give me an idea...
After looking at it this is what seems to be the process...(summarized)
Flashes boot.img then reboots, after reboot it then creates the mount points
Now what I'm thinking is this...if we edit the mtd parts to represent our old file system format...maybe that would work? Like switch put the mtd mounts with bml mounts...idk though...
That's just me brainstorming when its past midnight
But I'm positive its possible...just don't know the process
Sent from my SGH-I997 using Tapatalk 2
mg2195 said:
I think its possible...if I knew more about conversions I would definatly look into it...I did however look at the updater.sh and it did give me an idea...
After looking at it this is what seems to be the process...(summarized)
Flashes boot.img then reboots, after reboot it then creates the mount points
Now what I'm thinking is this...if we edit the mtd parts to represent our old file system format...maybe that would work? Like switch put the mtd mounts with bml mounts...idk though...
That's just me brainstorming when its past midnight
But I'm positive its possible...just don't know the process
Sent from my SGH-I997 using Tapatalk 2
Click to expand...
Click to collapse
Process is as follows, correct me if I'm wrong JT:
Begin flash from CWM, which starts updater script and runs bml_to_mtd, setting mount points and such. Then formatting of all partitions except for maybe boot.
Once done, updater script has a "oneshot" flag so that flashing to MTD only need happen once. after mounts set and partitions formatted, reboot.
second run checks format and, if MTD, begins flash.
Without looking at the updater script file (or anything else in the conversion process for that matter), the above would be my best guestimate, as it's been a REALLY long time since I've had to script anything like this to be done. I've done custom Linux installs and scripted the formatting of partitions, but that was on hard drives that already had all their mount points set.
I think we need something like this...http://forum.xda-developers.com/showthread.php?t=1375272
Hope that guy can figure it out...if he can then all we would have to do is edit to match our device and our format (I think...correct me if I'm wrong)
Sent from my HTC PH39100 using Tapatalk 2
mg2195 said:
I think we need something like this...http://forum.xda-developers.com/showthread.php?t=1375272
Hope that guy can figure it out...if he can then all we would have to do is edit to match our device and our format (I think...correct me if I'm wrong)
Sent from my HTC PH39100 using Tapatalk 2
Click to expand...
Click to collapse
Well, at least its easier now than it used to be. I remember having to set static memory locations (IE 0F0D3000-0F0D38AA), but this seems a whole lot easier since all you have to do is set partition sizes and mount points...
Sent from my SGH-I997 using xda app-developers app
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.