WARNING: DO NOT TRY THIS! IT'S A WORK IN PROGRESS AND WON'T WORK AT THIS STAGE!
A lot of people in this forum would like to try flashing custom ROMs or just de-branding their phone to an unbranded stock ROM but are concerned about voiding their warranty. I'm one of those.
Information on how to backup and restore back to original condition seems difficult to find so I thought I'd create a post that could be updated to form an easy-to-follow guide. There's a lot of gaps to fill in so please contribute if you can. Progress so far...
1. Backing up your original hboot, boot and recovery. I think this script should do it (modified from sfjuocekr's post /showthread.php?t=835746). Run from ConnectBot or similar terminal emulator on your phone (or ADB - just drop 'busybox' from the md5sum command):
Code:
#!/system/bin/sh
dd if=/dev/block/mmcblk0p18 of=/sdcard/DHD/hboot_orig0.img
dd if=/dev/block/mmcblk0p18 of=/sdcard/DHD/hboot_orig1.img
dd if=/dev/block/mmcblk0p21 of=/sdcard/DHD/recovery_orig0.img
dd if=/dev/block/mmcblk0p21 of=/sdcard/DHD/recovery_orig1.img
dd if=/dev/block/mmcblk0p22 of=/sdcard/DHD/boot_orig0.img
dd if=/dev/block/mmcblk0p22 of=/sdcard/DHD/boot_orig1.img
busybox md5sum /sdcard/DHD/*.img
echo ""
echo "IF THE ABOVE MD5 SUMS DO NOT MATCH"
echo "SOMETHING IS WRONG WITH YOUR BACKUP"
2. Permroot with VISIONary r12.
3. Load Clockwork MOD Recovery and make Nandroid backup. I need help with this section.
[Questions: Does it require S-OFF? Can you load the current test Clockwork recovery using 'fastboot boot' and run Nandroid from that?]
4. To restore, use the normal Nandroid restore procedure and then dd your backup files back to their original locations.
[Questions: Is it better to use 'fastboot flash boot boot.img'? I'm assuming I'll still have to use dd for the hboot and the phone will have to be in bootloader mode?]
Finally, will this work? Is this more complicated than it needs to be? Can you simply use dd to backup/restore the system and userdata partitions too?
Sorry if this is out of place. I thought I'd put in the initial effort and people who actually know what they are talking about might be so kind as to fill in the blanks.
I'm sorry to post this in the Fascinate forum, but as you all know Cellular South's version the "Showcase" is identical in hardware as is the Mesmerize, but there isn't a forum for either of them..
I see there's plenty of kernels and etc.. But is there just a simple lag fix that I can do to my Showcase that will make every day use better and less laggy?
A simple yes or no is fine with me.
if there is a way a link post or explanation would be VERY appreciated.
Thanks,
Elijahblake
(PS)Sort of on the same subject, but I read that gingerbread is going to support ext4 file system. I know the Galaxy S uses the RFS file system which I believe is where we get the lag in the first place.. Will it be possible to switch file system formats?
I'm not real familiar with all these Linux formats. Would it be similar to reformatting like from FAT32 to NTFS?
If you can provide some additional information and files, I can port some things such as Voodoo lagfix to your device.
Needed:
stock kernel
stock mbr
mount output
All of the following can be done through adb on a rooted device.
To dump the kernel do:
cat /dev/block/bml7 > /sdcard/zImage
To dump original mbr do:
dd if=/dev/block/mmcblk0 of=/sdcard/showcase.mbr bs=512 count=1
To get mount output do:
mount
then paste the output of that command as well as upload the showcase.mbr and zImage files here.
jt1134 said:
If you can provide some additional information and files, I can port some things such as Voodoo lagfix to your device.
Needed:
stock kernel
stock mbr
mount output
All of the following can be done through adb on a rooted device.
To dump the kernel do:
cat /dev/block/bml7 > /sdcard/zImage
To dump original mbr do:
dd if=/dev/block/mmcblk0 of=/sdcard/showcase.mbr bs=512 count=1
To get mount output do:
mount
then paste the output of that command as well as upload the showcase.mbr and zImage files here.
Click to expand...
Click to collapse
Ok will do, what's the best, easiest root method
Sent from my sch-i500 Showcase using XDA app
elijahblake said:
Ok will do, what's the best, easiest root method
Sent from my sch-i500 Showcase using XDA app
Click to expand...
Click to collapse
look for the thread in the fascinate forum simply titled "root"
also you will need to locate the thread explaining how to get clockworkmod recovery on the showcase in the same forum
jt1134 said:
look for the thread in the fascinate forum simply titled "root"
also you will need to locate the thread explaining how to get clockworkmod recovery on the showcase in the same forum
Click to expand...
Click to collapse
will do.. May take me some while to get all this info gathered..
quick question? I've read of some people not being able to see certain apps in the market after rooting.. Is this still the case?
If my phone is rooted and 2.2 finally does come out (officially) will have to un root and remove any lag fix to upgrade? How hard will this be?
elijahblake said:
If my phone is rooted and 2.2 finally does come out (officially) will have to un root and remove any lag fix to upgrade? How hard will this be?
Click to expand...
Click to collapse
To get the upgrade, you shouldn't have to un-root, but you should probably disable voodoo first as the update will almost certainly have a new kernel, and applying the update without disabling voodoo could cause quite a headache.
If you do apply the update right away, you could quite possibly loose root, so you may want to wait until the devs re-root the update. This could make things easier for you as the rooted update will also likely be cleaned up some.
To disable voodoo, you'd just need to create a file called "disable_lagfix" in /sdcard/voodoo and then reboot your phone. See the thread in the dev forum about removing voodoo for more details if you want.
ok well it looks like I'm rooted.. Now I tried to open the ADB that came in the fascinate root zip but it's not opening for more than a split second... you have a download link?
Also can uninstall all this bloatware now??
edit.. thought I had Android SDK on this laptop.. Downloading it now
jt1134 said:
If you can provide some additional information and files, I can port some things such as Voodoo lagfix to your device.
Needed:
stock kernel
stock mbr
mount output
All of the following can be done through adb on a rooted device.
To dump the kernel do:
cat /dev/block/bml7 > /sdcard/zImage
To dump original mbr do:
dd if=/dev/block/mmcblk0 of=/sdcard/showcase.mbr bs=512 count=1
To get mount output do:
mount
then paste the output of that command as well as upload the showcase.mbr and zImage files here.
Click to expand...
Click to collapse
Alright, so i'm rooted now and got ADB set up.. And this is the first time I've done any of this. So can you please tell me the exact commands to enter. I really don't want to mess anything up.
Thanks,
elijahblake
elijahblake said:
Alright, so i'm rooted now and got ADB set up.. And this is the first time I've done any of this. So can you please tell me the exact commands to enter. I really don't want to mess anything up.
Thanks,
elijahblake
Click to expand...
Click to collapse
I have c:\androidsdk
I put ADB inside tools and it sees my device when I run ADB devices
But on the commands you listed nothing happens, I'm not sure if that's the entire commands or if I'm supposed to add something to them..
Try to run the following
Code:
adb shell cat /dev/block/bml7 > /sdcard/zImage
adb shell dd if=/dev/block/mmcblk0 of=/sdcard/showcase.mbr bs=512 count=1
adb shell mount
or just typing "adb shell" and entering the commands at the new prompt, and typing "exit" to get back to the normal command prompt.
here's what happened..
the first two commands didn't work. DO i need to create a folder name zImages?
The second command said access denied..
You tell me if the mount worked haha..
jt will have to comment on whether that is what he needs from the mount command. Can you try the following to see if it works?
Code:
adb shell
su
shell cat /dev/block/bml7 > /sdcard/zImage
shell dd if=/dev/block/mmcblk0 of=/sdcard/showcase.mbr bs=512 count=1
exit
well, it granted me SU rights.. but still a no go...
i figured since i was in shell i shouldn't type that.. still got no directory found...
imnuts said:
jt will have to comment on whether that is what he needs from the mount command. Can you try the following to see if it works?
Code:
adb shell
su
shell cat /dev/block/bml7 > /sdcard/zImage
shell dd if=/dev/block/mmcblk0 of=/sdcard/showcase.mbr bs=512 count=1
exit
Click to expand...
Click to collapse
would root explorer make this any easier?
I just tested out all of the commands on my Fascinate and they all worked, so I'm guessing that the Showcase is putting stuff in a different place. jt will have to help you out further as I'm not sure of where else to look for the info he needs.
elijahblake said:
i figured since i was in shell i shouldn't type that.. still got no directory found...
Click to expand...
Click to collapse
for the cat command it should bml as in lowercase L, not 1. And it looks like you added a space between the of and = on the dd command.
GeekMouse said:
for the cat command it should bml as in lowercase L, not 1. And it looks like you added a space between the of and = on the dd command.
Click to expand...
Click to collapse
I typed it exactly the way you said.. still got this..
Can you take a shot at it?
elijahblake said:
I typed it exactly the way you said.. still got this..
Can you take a shot at it?
Click to expand...
Click to collapse
It doesn't need shell at the beginning.
elijahblake said:
I typed it exactly the way you said.. still got this..
Can you take a shot at it?
Click to expand...
Click to collapse
This is how it should be typed
Code:
adb shell
su
cat /dev/block/bml7 > /sdcard/zImage
dd if=/dev/block/mmcblk0 of=/sdcard/showcase.mbr bs=512 count=1
exit
hi guys
as you all know that some of the devices (i9300i) are hard bricked by flashing indian 4.4.4 so to unbrick we need a debrick.img which you guys can help us get by flashing this file https://copy.com/1ggUuyIqHUrF it will create a debrick.img into your sd card which you can upload and share
source http://forum.xda-developers.com/show....php?t=2439367
OR
Use this procedure to create the image
Enable USB Debugging.
Open cmd and navigate to your adb folder.
Run adb shell
Now type 'SU' to enable superuser, your may have to grant access to ADB from a popup screen of your phone's superuser app
next copy and paste the following code and change the phone model to your phone i.e. dd if=/dev/block/mmcblk0 of=/sdcard/debrickI710-16GB.img bs=1M count=128
dd if=/dev/block/mmcblk0 of=/sdcard/debrick[phonemodel-memorysize].img bs=1M count=128
6. Now type Exit on cmd and then use following the command to copy this image to your adb folder
adb pull /sdcard/debrick[phonemodel-memorysize].img
7. upload the image and share its link here.
[B]It will just take few minutes further you can compress the file (zip or rar) to reduce its size so that it can be upload easily.[/B]
Thanks in advance
:crying: i need it plz else my device will be useless
cmon guys it will not take more than 5 min plz help if it works ill make a thread about how to unbrick a hard bricked neo
I Hope it can helps you ...
I just run it on GT-i9300i ( Brazilian ) with Lastest HongKong 4.4.4 firmware + root and TWRP 2.7.0.1
Just tell me if you need anything else my friend.
PHP:
https://mega.co.nz/#!DVcSTA7R!0D0ah1pSaJzORvU95on2eyPxkE_866M2Ea0NmngPQX4
ygor.almeida said:
I Hope it can helps you ...
I just run it on GT-i9300i ( Brazilian ) with Lastest HongKong 4.4.4 firmware + root and TWRP 2.7.0.1
Just tell me if you need anything else my friend.
PHP:
https://mega.co.nz/#!DVcSTA7R!0D0ah1pSaJzORvU95on2eyPxkE_866M2Ea0NmngPQX4
Click to expand...
Click to collapse
thank u soooo much bro i just successfully un brick my device tomorrow i will make a thread again thanks for ur time and million thanks to u :laugh:
Hi, I've used your CWM script but it doesn't have created the ZIP file with the debrick image.
I've searched it on all memories (also the system folder) but nothing. I've a GTI9301I ITV Firmware UANI1
I've tried also the adb shell and when i type adb pull /sdcard/debrick[phonemodel-memorysize].img it show me no devices (but it's enabled and the phone receive correctly commands)
can't boot my phone cause I have deleted my efs folder becasue in one of the guides here someone said that if you had full recovery of your efs and you sure that your efs folder is damged than delete the folder and recover, well so I did... (I downgrade from lolipop to 4.4.2, lost my imei in the "process"
I had the efs.img backup on my computer and I moved it to my phone, I deleted my efs folder using root browser and than I used some adb app to type the commend "dd if=/sdcard/efs.img of=/dev/block/mmcblk0p3 bs=4096" and I restred my phone, but it never left samsmung logo and I can't boot up my phone I tried to go to stock channgeing roms, nothing helps, in recovery mode it says "E:/can't mount efs" something like that.. and the phone won't boot up, just stuck on samsung logo.
somone have any Idea what can i do?
After flashing a stock ROM, did you perform a factory wipe before booting the phone for the first time?
audit13 said:
After flashing a stock ROM, did you perform a factory wipe before booting the phone for the first time?
Click to expand...
Click to collapse
you mean when I downgrade from lolipop to the stcok rom?, if yes Than I didn't and that what cause me losing my imei and started this whole efs problem...
Did you try flashing back to stock LP? Flashing stock kk would not normally damage the efs.
audit13 said:
Did you try flashing back to stock LP? Flashing stock kk would not normally damage the efs.
Click to expand...
Click to collapse
yey I manged to fix ti!!!! god that was hard **** yes!! to me!
if someone will see this so this is what I did
1) I flashed to stock rom based lolipop but still had the issue of "E:failed to mount /efs" cause it didn't recvoer the folder and my phone still won't boot up, so I found a fix
right here http://forum.xda-developers.com/galaxy-s3/general/how-to-fix-efailed-to-mount-efs-invalid-t2858056
adb shell
Code:
mke2fs /dev/block/mmcblk0p3
Code:
mount -w -t ext4 /dev/block/mmcblk0p3 (this line dind't even work for me so I skipped it)
Code:
reboot
affter I did it phone boot up finally but I still had a fake Imei so next I used this guide (this time I ain't deleting the efs folder like he wrote"
2)http://forum.xda-developers.com/showthread.php?t=2392632, I alredy had efs.img as back up so all I did is install latest "su" and the latest busybox than I installed "Terminal Emulator"
and used the second method
"Put your efs.img on your phone memory(not external sd card!) in the main memory, not inside folder.
Open terminal emulator
Write the following:
Code:
su
Then click enter. It will ask for super user permission, give it permissions.
Then write:
Code:
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p3 bs=4096"
my phone rebooted and now I have my imei back!
Congratulations on your success and posting your solution!
worked for me
okdark4 said:
"Put your efs.img on your phone memory(not external sd card!) in the main memory, not inside folder.
Open terminal emulator
Write the following:
Code:
su
Then click enter. It will ask for super user permission, give it permissions.
Then write:
Code:
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p3 bs=4096"
my phone rebooted and now I have my imei back!
Click to expand...
Click to collapse
Hi okdark4,
thanks for sharing!
For me, I hat to use a slightly different command - just for the others to know:
su
dd if=/sdcard/efs.img of=/dev/block/mmcblk0p3
reboot
That's it!
Hi mates, thank you for helping!
Really a complicated story mine, had on this phone already issues with baseband (when I bought it had LL 5.01) when I upgraded it to RR 7.1.2, then I figured out I needed to upload the latest stock 6.0.1 G900PVPS3CQD1 to have it working, I also PITted the phone before, it worked for 5-6 monts, then the signal went off.
I've tried different solutions:
1) in TWRP typed in its terminal the commands I've found here:
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1
dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst2
It said "not enough space" but it looks in the end it copied around 3MB. Rebbited but no changes
2) Again thr TWRP:
dd if=/dev/block/platform/msm_sdcc.1/by-name/efs of=efs.bak
dd if=/dev/block/bootdevice/by-name/modemst1 of=modemst1.bak bs=4096
dd if=/dev/block/bootdevice/by-name/modemst2 of=modemst2.bak bs=4096
find /efs -exec ls -l {} \; > efs-permissions
nothing changed
3) updated to lineage 15.1, it says "no sim card" (the sim works fine in another 900V) with rooted ADB shell tried the "dd if=/dev/zero of=/dev/block/bootdevice/by-name/modemst1" but no such file. Then I decided to flash stock LL 5.01 BOK but like in stock 6.01 says "invalid sim card".
4) I run in adb:
adb shell
mount
and can't see /stl4 /efs so this is why I assume that efs is corrupted.
Somebody says to flash (under Odin PDA) EFS-Fix-regalstreak.tar.md5, but I won't risk to flash other phones data on my phone, including its IMEI.
Someone else says I have to backup EFS (I suppose this is possibile because when I executed adb commands it never said me that the files don't exist) and reflash it to fix the corruption. How this is possible to do? Thank you!
PS: I attached the backupof EFS made by TWRP, seems all good (not corrupted), why sim doesn't work?
I'm now on stock LL BOK, using in adb mount I have this
/dev/block/platform/msm_sdcc.1/by-name/efs /efs ext4 rw,seclabel,nosuid,nodev,noatime,discard,journal_checksum,journal_async_commit,noauto_da_alloc,data=ordered 0 0