Related
Hi there...
I'm finally considering rooting, however all the guides lead to flashing a custom rom... but actually I don't want to flash a custom ROM, I want to keep everything as it is, with the difference that I (and preferably only I) can become super user on the shell when I need to do some changes (like fixing the stock widget bug in the internal database).
I've read this right now:
http://forum.xda-developers.com/showthread.php?t=724741
And they say I can flash this files called EngTools.zip
Does this also work on the Hero assuming the guide (PossibleGSMRoot or something... fromt he villainforum) works on my phone?
I don't even want to permanently have some kind of AmonRa blabla recovery boot image on my phone. If I need it while I get root that's fine, but I want to get rid of it afterwards. I really don't need root for any applications liek overclocking etc. etc. just for smaller dives into the files system and changes there via adb.
olafos said:
Hi there...
I'm finally considering rooting, however all the guides lead to flashing a custom rom... but actually I don't want to flash a custom ROM, I want to keep everything as it is, with the difference that I (and preferably only I) can become super user on the shell when I need to do some changes (like fixing the stock widget bug in the internal database).
I've read this right now:
http://forum.xda-developers.com/showthread.php?t=724741
And they say I can flash this files called EngTools.zip
Does this also work on the Hero assuming the guide (PossibleGSMRoot or something... fromt he villainforum) works on my phone?
I don't even want to permanently have some kind of AmonRa blabla recovery boot image on my phone. If I need it while I get root that's fine, but I want to get rid of it afterwards. I really don't need root for any applications liek overclocking etc. etc. just for smaller dives into the files system and changes there via adb.
Click to expand...
Click to collapse
Hmmm. If you are on 2.1, then you can use the GSM root i posted over at VR. The recovery needs to be flashed to the phone though, so you can flash zips to the phone from there.
As for your wish to get rid of the patched recovery afterwards, you're missing out a lot, but if you can find the stock recovery img file, you can simply flash that using
"flash_image recovery FilenameHero.img" via the phone's shell or adb (once rooted, presuming you added the flash_image binary).
As for that file, I don't know, as I've never checked if that will work on the hero.
I'd be inclined to say DON'T TRY IT, since it will contain a kernel, and flashing the wrong kernel can brick your device's radio, essentially ruining it.
But if you locate the correct files for the GSM hero, and package them similarly, you could flash that onto your phone via recovery
Bear in mind the stock HTC ROM is basically full on the system partition, so you might have issues actually fitting the files on.
I've been a lurker for some time here but just before I had thought about exactly the same issue as OP... I always wondered why there's no way to just get root access temporarily. Most people told me I'd have to flash a custom ROM.
So today I finally looked into the matter and based on your (anon2122) post on VillainROM and the Eris exploits etc. I managed to do exactly what I wanted... and thought it's time to get an account...
I only really needed root for the Stock app currency issue: [HTTP]://forum[DOT]xda-developers[DOT]com/showthread[DOT]php?t=719149 which I was now able to fix.
HTC Hero GSM soft root guide by ixampl
(... credits belong to / based on: [HTTP]://www[DOT]villainrom[DOT]co[DOT] uk/viewtopic[DOT]php?f=110&t=2096)
1 Flashing a custom recovery image
1.1 Backup (1)
Code:
adb shell mkdir /data/local/backup
adb shell cat /data/local/rights/mid.txt > /data/local/backup/mid.txt
1.2 Uploading custom recovery image and image flashing tool and setting correct permissions
Code:
adb push recovery-RA-hero-v1.6.2.img /data/local/
adb push flash_image /data/local/
adb shell chmod 777 /data/local/recovery-RA-hero-v1.6.2.img
adb shell chmod 777 /data/local/flash_image
1.3 Center piece of the permissions exploit for the recovery ROM
Code:
adb shell ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt
1.4 Normal reboot
Code:
adb reboot
1.5 Now that the recovery ROM (/dev/mtd/mtd1) is accessible: Backup (2)
Code:
adb shell cat /dev/mtd/mtd1 > /data/local/backup/recovery.img
1.6 Flashing the previously uploaded custom recovery image
Code:
adb shell /data/local/flash_image recovery /data/local/recovery.img
1.7 Rebooting into recovery mode
Code:
adb reboot recovery
2 Adding root shell (optional)
2.1 Mounting all devices
Code:
adb shell mount -a
2.2 Adding rootsh
Code:
adb shell cat /system/bin/sh > /system/bin/rootsh
adb shell chmod 4755 /system/bin/rootsh
2.3 Rebooting into system
Code:
adb reboot
After this you can flash the recovery.img you backed up in step 1.5 just as you flashed in step 1.6 (adjust the parameters accordingly).
ixampl said:
I've been a lurker for some time here but just before I had thought about exactly the same issue as OP... I always wondered why there's no way to just get root access temporarily. Most people told me I'd have to flash a custom ROM.
So today I finally looked into the matter and based on your (anon2122) post on VillainROM and the Eris exploits etc. I managed to do exactly what I wanted... and thought it's time to get an account...
I only really needed root for the Stock app currency issue: [HTTP]://forum[DOT]xda-developers[DOT]com/showthread[DOT]php?t=719149 which I was now able to fix.
HTC Hero GSM soft root guide by ixampl
(... credits belong to / based on: [HTTP]://www[DOT]villainrom[DOT]co[DOT] uk/viewtopic[DOT]php?f=110&t=2096)
1 Flashing a custom recovery image
1.1 Backup (1)
Code:
adb shell mkdir /data/local/backup
adb shell cat /data/local/rights/mid.txt > /data/local/backup/mid.txt
1.2 Uploading custom recovery image and image flashing tool and setting correct permissions
Code:
adb push recovery-RA-hero-v1.6.2.img /data/local/
adb push flash_image /data/local/
adb shell chmod 777 /data/local/recovery-RA-hero-v1.6.2.img
adb shell chmod 777 /data/local/flash_image
1.3 Center piece of the permissions exploit for the recovery ROM
Code:
adb shell ln -s /dev/mtd/mtd1 /data/local/rights/mid.txt
1.4 Normal reboot
Code:
adb reboot
1.5 Now that the recovery ROM (/dev/mtd/mtd1) is accessible: Backup (2)
Code:
adb shell cat /dev/mtd/mtd1 > /data/local/backup/recovery.img
1.6 Flashing the previously uploaded custom recovery image
Code:
adb shell /data/local/flash_image recovery /data/local/recovery.img
1.7 Rebooting into recovery mode
Code:
adb reboot recovery
2 Adding root shell (optional)
2.1 Mounting all devices
Code:
adb shell mount -a
2.2 Adding rootsh
Code:
adb shell cat /system/bin/sh > /system/bin/rootsh
adb shell chmod 4755 /system/bin/rootsh
2.3 Rebooting into system
Code:
adb reboot
After this you can flash the recovery.img you backed up in step 1.5 just as you flashed in step 1.6 (adjust the parameters accordingly).
Click to expand...
Click to collapse
That is a nice method.
I've long thought about making something similar, so maybe today I'll try, as an idea has come back to me...
I am thinking that I can avoid the whole recovery flashing, though I'm not going to say the idea till I've thought it through, as someone might try it before I realise how stupid an idea it is...
But I'll certainly see if it can get permanent root sorted out on the phone, although it won't give root adb access, as that is defined in the boot.img, though I guess I could flash that while I'm at it...
Good work.
Thanks!
Yes, a method to (safely) acquire super user access without flashing anything would be highly appreciated There's a small risk involved with flashing. Granted it usually causes no issues, but there is the slight possibility of bricking your phone.
Good work.
Click to expand...
Click to collapse
Thanks, although - as you know - I really didn't do anything special there
[...] although it won't give root adb access [...]
Click to expand...
Click to collapse
Yes, that's a minor annoyance, but really minor ... for the currency fix I naturally couldn't do
Code:
adb pull /data/data/com.htc.dcs.service.stock/databases/stock.db stock.db
or
Code:
adb push stock.db /data/data/com.htc.dcs.service.stock/databases/stock.db
but it's not that hard to just work around that via /data/local:
Code:
adb shell
$ rootsh
# cat /data/data/com.htc.dcs.service.stock/databases/stock.db > data/local/stock.db
then pull from there etc.
I really think "rooting" is a misnomer for most of the current guides.
I can see that most people "root" their phone in order to get custom ROMs (and I have no issue with that, it's just too much overkill for someone who just wanted to fix a small bug ) but In fact most people don't care about rooting per se, they care about flashing a recovery image which enables them to flash custom ROMs.
I actually wanted to try:
Code:
adb shell ln -s /dev/mtd/mtd3 /data/local/rights/mid.txt
...and see what happens if I remount after boot. If it causes the system to follow back the link with user permissions for the recovery ROM, maybe the system ROM could be (write-)accessed as well. Then again, it was my first venture into rooting so naturally there would have been no way to fix a broken system image safe for reflashing the 1.5 RUU.
Do you have any details about what the original purpose of the (original) mid.txt was? I mean, it was there, sitting in a directory named rights... quite an invitation (of course, we didn't actually "set" rights in that file or anything for the exploit, but still...)
Is it safe to delete mid.txt and will it be recreated with some default values by the system?
Click to expand...
Click to collapse
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
I don't have a laptop And I really need to flash the stock ROM of 4.4.2.. I have TWRP installed and that's all.. Is anyone aware of some flashable zip of this stock ROM? Thanks in advance
I wanted to help but I have no idea how to create and update-binary file, so it is not flashable, but you can go back to 4.4.2 without computer. So what you need to is:
Download this: V40010C
Extract and place it onto your sd card!. Make sure all files are under /sdcard/* directory. Boot into the recovery, go to wipe -> advanced wipe -> wipe everything except sd card and internal storage. In recovery, go to advanced, then terminal. Folders should pop on the screen but do not go to any different directory, just press select. Now you should be in the terminal. Now, I'm really sorry but it will take some time, you have to enter each of this commands separately into the terminal:
Code:
dd if=/sdcard/V40010C/bootloader/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/V40010C/bootloader/factory.bin of=/dev/block/platform/msm_sdcc.1/by-name/factory
dd if=/sdcard/V40010C/bootloader/laf.bin of=/dev/block/platform/msm_sdcc.1/by-name/laf
dd if=/sdcard/V40010C/bootloader/rpm.bin of=/dev/block/platform/msm_sdcc.1/by-name/rpm
dd if=/sdcard/V40010C/bootloader/sbl1.bin of=/dev/block/platform/msm_sdcc.1/by-name/sbl1
dd if=/sdcard/V40010C/bootloader/sdi.bin of=/dev/block/platform/msm_sdcc.1/by-name/sdi
dd if=/sdcard/V40010C/bootloader/tz.bin of=/dev/block/platform/msm_sdcc.1/by-name/tz
dd if=/sdcard/V40010C/boot.bin of=/dev/block/platform/msm_sdcc.1/by-name/boot
dd if=/sdcard/V40010C/cust.bin of=dev/block/platform/msm_sdcc.1/by-name/cust
dd if=/sdcard/V40010C/modem.bin of=/dev/block/platform/msm_sdcc.1/by-name/modem
dd if=/sdcard/V40010C/persist.bin of=/dev/block/platform/msm_sdcc.1/by-name/persist
dd if=/sdcard/V40010C/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system
Remember only system is an img file! It is about 2,5GB so to flash it will take about 5-10 min.
Once you flashed everything you can reboot, in my case it said that OS is not installed but the recovery didn't know yet that we just flashed it. So just swipe to reboot and tablet should boot up with 4.4.2 !
If you have any problems just tell me
Adam Myczkowski said:
I wanted to help but I have no idea how to create and update-binary file, so it is not flashable, but you can go back to 4.4.2 without computer. So what you need to is:
Download this: V40010C
Extract and place it onto your sd card!. Make sure all files are under /sdcard/* directory. Boot into the recovery, go to wipe -> advanced wipe -> wipe everything except sd card and internal storage. In recovery, go to advanced, then terminal. Folders should pop on the screen but do not go to any different directory, just press select. Now you should be in the terminal. Now, I'm really sorry but it will take some time, you have to enter each of this commands separately into the terminal:
Code:
dd if=/sdcard/V40010C/bootloader/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/V40010C/bootloader/factory.bin of=/dev/block/platform/msm_sdcc.1/by-name/factory
dd if=/sdcard/V40010C/bootloader/laf.bin of=/dev/block/platform/msm_sdcc.1/by-name/laf
dd if=/sdcard/V40010C/bootloader/rpm.bin of=/dev/block/platform/msm_sdcc.1/by-name/rpm
dd if=/sdcard/V40010C/bootloader/sbl1.bin of=/dev/block/platform/msm_sdcc.1/by-name/sbl1
dd if=/sdcard/V40010C/bootloader/sdi.bin of=/dev/block/platform/msm_sdcc.1/by-name/sdi
dd if=/sdcard/V40010C/bootloader/tz.bin of=/dev/block/platform/msm_sdcc.1/by-name/tz
dd if=/sdcard/V40010C/boot.bin of=/dev/block/platform/msm_sdcc.1/by-name/boot
dd if=/sdcard/V40010C/cust.bin of=dev/block/platform/msm_sdcc.1/by-name/cust
dd if=/sdcard/V40010C/modem.bin of=/dev/block/platform/msm_sdcc.1/by-name/modem
dd if=/sdcard/V40010C/persist.bin of=/dev/block/platform/msm_sdcc.1/by-name/persist
dd if=/sdcard/V40010C/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system
Remember only system is an img file! It is about 2,5GB so to flash it will take about 5-10 min.
Once you flashed everything you can reboot, in my case it said that OS is not installed but the recovery didn't know yet that we just flashed it. So just swipe to reboot and tablet should boot up with 4.4.2 !
If you have any problems just tell me
Click to expand...
Click to collapse
Wow.. Amazing.. I don't know how to thank you man.. That's a lot of helping
BIG THANKS!!
Adam Myczkowski said:
I wanted to help but I have no idea how to create and update-binary file, so it is not flashable, but you can go back to 4.4.2 without computer. So what you need to is:
Download this: V40010C
Extract and place it onto your sd card!. Make sure all files are under /sdcard/* directory. Boot into the recovery, go to wipe -> advanced wipe -> wipe everything except sd card and internal storage. In recovery, go to advanced, then terminal. Folders should pop on the screen but do not go to any different directory, just press select. Now you should be in the terminal. Now, I'm really sorry but it will take some time, you have to enter each of this commands separately into the terminal:
Code:
dd if=/sdcard/V40010C/bootloader/aboot.bin of=/dev/block/platform/msm_sdcc.1/by-name/aboot
dd if=/sdcard/V40010C/bootloader/factory.bin of=/dev/block/platform/msm_sdcc.1/by-name/factory
dd if=/sdcard/V40010C/bootloader/laf.bin of=/dev/block/platform/msm_sdcc.1/by-name/laf
dd if=/sdcard/V40010C/bootloader/rpm.bin of=/dev/block/platform/msm_sdcc.1/by-name/rpm
dd if=/sdcard/V40010C/bootloader/sbl1.bin of=/dev/block/platform/msm_sdcc.1/by-name/sbl1
dd if=/sdcard/V40010C/bootloader/sdi.bin of=/dev/block/platform/msm_sdcc.1/by-name/sdi
dd if=/sdcard/V40010C/bootloader/tz.bin of=/dev/block/platform/msm_sdcc.1/by-name/tz
dd if=/sdcard/V40010C/boot.bin of=/dev/block/platform/msm_sdcc.1/by-name/boot
dd if=/sdcard/V40010C/cust.bin of=dev/block/platform/msm_sdcc.1/by-name/cust
dd if=/sdcard/V40010C/modem.bin of=/dev/block/platform/msm_sdcc.1/by-name/modem
dd if=/sdcard/V40010C/persist.bin of=/dev/block/platform/msm_sdcc.1/by-name/persist
dd if=/sdcard/V40010C/system.img of=/dev/block/platform/msm_sdcc.1/by-name/system
Remember only system is an img file! It is about 2,5GB so to flash it will take about 5-10 min.
Once you flashed everything you can reboot, in my case it said that OS is not installed but the recovery didn't know yet that we just flashed it. So just swipe to reboot and tablet should boot up with 4.4.2 !
If you have any problems just tell me
Click to expand...
Click to collapse
Hey, I know it's been a while since you posted this. but could you help me try to recover my v400? It doesn't boot at all and I believe that the partitions are corrupt. How can I flash them?
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