Related
Hi guys, it just came to my mind that test-key signed update.zip files were working back in the eclair days, so i guess the problem is the new recovery in the froyo builds needing Samsung signed files. Same problem was present on the sgs when it moved to froyo, but the devs there managed to change back to old recovery to make them work again, would be nice if someone could find a similar solution for the sg3 also... for more info search for recovery 2e 3e howto in sgs dev section... i am very busy at the moment and go for vacation on Sunday so wont find time to look into this before beginning of March, but eventually someone else could do it and just needed the hint....
Ok, to give this a bump, i need someone with a eclair rom installed and a rooted system. What i need is two files: /sbin/recovery and /sbin/recovery.sh
I think if we swap those files in jpf or whatever Froyo version we could use update.zip files again...
FadeFx
I have JK1 but in sbin directory I have only recovery file, no signs of recovery.sh
sorry, my bad, recovery.sh is part of the modified clockwork mod recovery on sgs custom kernel. also i am in conversation with hardcore about this, and eventually wed have to change the file in initramfs of the kernel... but we will see. to bad i go on vacation tomorrow and will be away for 3 weeks (going to thailand, cant wait to be there...) so i wont have time to complete this, but i will gather info and eventually gsam101 could compile a zimage with old recovery...
Ok, here is my pm conversation with hardcore, seems it can be done easily with loosing new recovery, or the complicated way keeping new recovery for system calls (CSC changes and stuff) and loading old recovery when using 3 button combo. All this is done by recovery.sh
hardcore said:
No u replace /system/bin/recovery in the rom, not kernel.
For kernel if u want to reroute to another recovery u have to use some shell script logic. Check out the initramfs source of my kernel for recovery.sh.
ok, thanx... so we would have to change the file /system/bin/recovery in the zimage´s initramfs to exchange recovery, right?
can we also put the replacement recovery into /sbin to replace the original? and if how is it then called when actually entering recovery mode so we dont enter the old recovery?
thanx Gerd
The recovery executable that comes with the ROM is actually in /system/bin/recovery
Modified kernels like mine have another CWM recovery in the kernel which is in /sbin/recovery which is compiled into the kernel's read-only initramfs.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Content of recovery.sh:
(lagfix stuff is about sztupys lagfix for the sgs and can be ignored for g3 at the moment.
This replaces stock froyo recovery (3e) with clockwork recovery, but same procedure applies to old 2e recovery.
Code:
#!/sbin/busybox sh
/sbin/busybox cp /sbin/fat.format /system/bin/fat.format
# use default recovery from rom if we have an update to process, so things like CSC updates work
# Use CWM if we simply entered recovery mode by hand, to be able to use it's features
if /sbin/busybox [ -f "/cache/recovery/command" ];
then
# if we use the original recovery it might modify the filesystem, so we erase our config, in order to avoid regeneration
# of the filesystems. The drawback is that the lagfix has to be re-applied by hand
/sbin/busybox rm /system/etc/lagfix.conf
/sbin/busybox rm /system/etc/lagfix.conf.old
rm /sdcard
mkdir /sdcard
#/sbin/rec2e &
/system/bin/recovery &
else
# TODO: CWM is a bit more intelligent, but it might fail to
/sbin/recovery &
fi;
Hope someone can make use of this to get update.zip working again...
Nobody looked into this yet? This would make much things easier for us...
Bump
....
realy hope we get some good progress and development on this thread....
sry but im just a noob and flashing is all i do right now
but if i can give any help feel free to ask
Gonna check this out. If I get OCD about this, v1.2 will be delayed.
This could be really useful. For everyone.
Sent from my Lestatious v1.2 Galaxy 3 FROYO
Lestat, i think this is info enough, if not pm me with the questions and ill do my best to find out.
FadeFx said:
Lestat, i think this is info enough, if not pm me with the questions and ill do my best to find out.
Click to expand...
Click to collapse
Alright. Will do chief. Gonna bookmark this thread so I remember tomorrow.
Sent from my Lestatious v1.2 Galaxy 3 FROYO
I have the 2.1 recovery file. . If anyone interested i think i can post if xda allows. ..
Sent from my GT-I5800 using XDA App
I was going to respond, but you responded for me: I tried to make some change to the recovery, basically to make Clockworkmod Recovery work. It seems that in Samsung's phones, the recovery is stored in /system, which is a total nonsense. I managed to get CWN almost work, but it was really buggy.
Gsam101 said:
I was going to respond, but you responded for me: I tried to make some change to the recovery, basically to make Clockworkmod Recovery work. It seems that in Samsung's phones, the recovery is stored in /system, which is a total nonsense. I managed to get CWN almost work, but it was really buggy.
Click to expand...
Click to collapse
How buggy is it?
And i noticed that's where recovery was also. I was like, Hmm. Strange.
The Dark Lestat said:
How buggy is it?
And i noticed that's where recovery was also. I was like, Hmm. Strange.
Click to expand...
Click to collapse
Like i had to flash my phone back to make it work ^^
Did u use the sgs version of cwm or did u do an own port for the g3? I guess the sgs version wont run due to different bml layout
Gsam101 said:
I was going to respond, but you responded for me: I tried to make some change to the recovery, basically to make Clockworkmod Recovery work. It seems that in Samsung's phones, the recovery is stored in /system, which is a total nonsense. I managed to get CWN almost work, but it was really buggy.
Click to expand...
Click to collapse
Hi Gsam101
I interested in compile custom recovery too.
Can You please share build configs for apollo projects?
just wanted to bump this thread, since i think we should now have devs that should be capable of doing such stuff, update.zip support is normally a must have for any android device
is this helpful in any way? -> http://forum.xda-developers.com/showpost.php?p=12244509&postcount=159
No, not yet. Clockwork needs to be ported to our device to run, which i am not able to do. If u can port it i can eventually give some hints...
i have wrote to the developer of ROM Manager APP (Clockwork Recovery) asking him to support our phone. I wrote just because i saw
Don't see your phone? Email me if you want to help me get it working!
Click to expand...
Click to collapse
on his page (http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html)
i'm not good at programming so i think if the developer replies and the answer will be yes then someone like FadeFx or anyone else who can help should contact [email protected] or [email protected]
Guys, I've got a 2.2 dev firmware transformer unit for tonight only. Are there any files I should rip before I have to send it back tomorrow? Seems like lots of dev tools installed. I know there are dumps out there, but perhaps the files can be useful.
3.0 version arriving tomorrow hopefully.
It makes sense to dump root and system partitions. Data can also have some useful stuff, but no partition dump needed, may be just /data/app directory. Could you try playing YouTube videos using native app? Does it drops frames?
Sent from my Transformer TF101 using Tapatalk
dd if=/dev/block/mmcblk3 of=/<sdcard with enough space for a 16GB dump>
Once compressed that shouldn't be too large.
Roach2010 said:
dd if=/dev/block/mmcblk3 of=/<sdcard with enough space for a 16GB dump>
Once compressed that shouldn't be too large.
Click to expand...
Click to collapse
Seriously. There's been a whole lot of dicking around on this, when this would give us everything to pore over offline. Don't let another one go to waste!
Also get the output from 'cat /proc/partitions' so we know where to split up the partitions.
Why does anybody want the 2.2? Not in a ass way,just actually curious.
Sent from my Nexus S 4G using XDA Premium App
jinsoku3g said:
Why does anybody want the 2.2? Not in a ass way,just actually curious.
Sent from my Nexus S 4G using XDA Premium App
Click to expand...
Click to collapse
It's not about the Froyo ROM, nobody wants that on his TF, really
But since it's a dev device, our devs hope that it is less locked down and perhaps flashable with nvflash for example. This would give us great opportunities. I'm no dev myself, but I hope I could help.
qwer23 said:
It's not about the Froyo ROM, nobody wants that on his TF, really
But since it's a dev device, our devs hope that it is less locked down and perhaps flashable with nvflash for example. This would give us great opportunities. I'm no dev myself, but I hope I could help.
Click to expand...
Click to collapse
Ah I see so clearly now lol I never thought about that. Thanks
Sent from my Nexus S 4G using XDA Premium App
get the files from the /data/ folder.
We believe some dev tools are in the /data/ folder instead of /system/app/, since other people had some apps disappear after they did a factory reset.
I'd back up everything I could.. assuming MicroSD is at /Removable/MicroSD...
Feel free to sub values according to busybox df -h.. for example, if there are 300MB of files on the data partition... create an image accordingly..
busybox dd if=/dev/zero of=/Removable/MicroSD/data.img bs=1M count=768
Bold indicates that it may have to be done in linux.. in this case.. I'm talking about making the ext4 file system on the created images.. in which case.. loop devices wouldn't be in /dev/block/...
for the acutal script..
busybox dd if=/dev/zero of=/Removable/MicroSD/data.img bs=1M count=768
busybox dd if=/dev/zero of=/Removable/MicroSD/system.img bs=1M count=300
busybox losetup /dev/block/loop2 /Removable/MicroSD/data.img
busybox losetup /dev/block/loop3 /Removable/MicroSD/system.img
mkfs.ext4 /dev/block/loop2
mkfs.ext4 /dev/block/loop3
mkdir /Backups
mkdir /Backups/data
mkdir /Backups/system
busybox mount /dev/block/loop2 /Backups/data
busybox mount /dev/block/loop3 /Backups/system
cd /data/
cp -aR ./ /Backups/data/
cd /system/
cp -aR ./ /Backups/system/
then you can use 'dd' to grab whatever other partitions you can find..
I guess this 'offer' is over with.. but I still have a quesiton.. what size was the device? 16 or 32?
pokey9000 said:
Seriously. There's been a whole lot of dicking around on this, when this would give us everything to pore over offline. Don't let another one go to waste!
Click to expand...
Click to collapse
Agree, would be great to have the whole thing
I'm mostly interesting in the stuff on the /data partition, since they have apps installed on there that are not in the current system dump
I sent itback and got a nice new 3.0 version. Had to pay again though and wait for ebuyer to collect and spend a week checking the old one though before i get my money back. Consider this very bad customer service.
Managed to rip all the apps from app and system/app. Got the ones that were deleted in a factory reset too! Will find a way to make them available soon.
ryukent said:
I sent itback and got a nice new 3.0 version. Had to pay again though and wait for ebuyer to collect and spend a week checking the old one though before i get my money back. Consider this very bad customer service.
Managed to rip all the apps from app and system/app. Got the ones that were deleted in a factory reset too! Will find a way to make them available soon.
Click to expand...
Click to collapse
I'm r34p3rex and I approve of this message.
pokey9000 said:
Seriously. There's been a whole lot of dicking around on this, when this would give us everything to pore over offline. Don't let another one go to waste!
Click to expand...
Click to collapse
Guys im not trying to be negative but did no one read what i posted with the last one ? I did post the partitions as well... the 2.2 version is nothing but a device flashed with wrong software.. the sbk is locked it is all locked and the partitions are all different, take the apps if you want but these devices dont hold any keys or secrets for us. :-(
ryukent said:
I sent itback and got a nice new 3.0 version. Had to pay again though and wait for ebuyer to collect and spend a week checking the old one though before i get my money back. Consider this very bad customer service.
Managed to rip all the apps from app and system/app. Got the ones that were deleted in a factory reset too! Will find a way to make them available soon.
Click to expand...
Click to collapse
Sweet, nice work.
Hello everyone. I need a small BIG favor...someone with a rooted ATT/puertorico LG G4 please run this command
using adb shell terminal
Code:
dd if=/dev/block/mmcblk0 bs=1 count=17408 of=/data/media/0/gpt_backup.img
And post the file here. Trying to make to make a file to unbrick completely dead phone.
Thank you
Sunderwear said:
Hello everyone. I need a small BIG favor...someone with a rooted ATT/puertorico LG G4 please run this command
using adb shell terminal
Code:
dd if=/dev/block/mmcblk0 bs=1 count=17408 of=/data/media/0/gpt_backup.img
And post the file here. Trying to make to make a file to unbrick completely dead phone.
Thank you
Click to expand...
Click to collapse
What partition is MMCBLK0?
mmcblk0 is the internal storage media, the partitions corrospond to the offsets, so mmcblk0p1 0p2 etc, since the phone is in download mode the system isnt mounted fully and you need to calculate the offset to capture the partition with dd.
just an fyi to the op, I was already working on doing this, once im done capturing everything and testing it there will be a guide up
diedemus said:
mmcblk0 is the internal storage media, the partitions corrospond to the offsets, so mmcblk0p1 0p2 etc, since the phone is in download mode the system isnt mounted fully and you need to calculate the offset to capture the partition with dd.
just an fyi to the op, I was already working on doing this, once im done capturing everything and testing it there will be a guide up
Click to expand...
Click to collapse
Thanks a lot for your efforts! Hopefully we have a guide to go back to AT&T stock in the event we mess our devices up!
diedemus said:
mmcblk0 is the internal storage media, the partitions corrospond to the offsets, so mmcblk0p1 0p2 etc, since the phone is in download mode the system isnt mounted fully and you need to calculate the offset to capture the partition with dd.
just an fyi to the op, I was already working on doing this, once im done capturing everything and testing it there will be a guide up
Click to expand...
Click to collapse
mu3g said:
Thanks a lot for your efforts! Hopefully we have a guide to go back to AT&T stock in the event we mess our devices up!
Click to expand...
Click to collapse
This might be a silly question but I would like someone to clarify... Why don't we get everyone to simply back up their system.img before/after rooting using the same method mentioned in the root thread and always keep on the internal storage that way if they soft brick they can just put the device in download move and restore to that? I know if you hard brick your device you have no choice but as long as it boots that should work or was I mislead? I think when you flash the PR firmware then you are committed because all your partitions change right? If I'm wrong I'd really like an explanation just in case I brick my device
Thats correct, once you go to PR the partition table changes. If you have an issue on ATT with a bootloop and have your factory system.img on the internal storage you just drop to download mode and push it with dd
I set up a donate button on the left and am waiting to hear back from mods on what my options are for it.
diedemus said:
Thats correct, once you go to PR the partition table changes. If you have an issue on ATT with a bootloop and have your factory system.img on the internal storage you just drop to download mode and push it with dd
I set up a donate button on the left and am waiting to hear back from mods on what my options are for it.
Click to expand...
Click to collapse
If this is the case, for a soft brick, can we just put the phone in download mode and flash the rooted 10g system image from the root thread using dd....would that work to get out of a soft brick?
mu3g said:
If this is the case, for a soft brick, can we just put the phone in download mode and flash the rooted 10g system image from the root thread using dd....would that work to get out of a soft brick?
Click to expand...
Click to collapse
yeah, I made a backup before I did anything for this. Should be the first line of defense and really should be one of the steps of rooting just so people know that's an option
Hey guys. Apparently I've done exactly what you talk about I regards to flashing the PR system.img to the internal SD card because after bootlooping, my internal SD card was completely full except for less than 1 GB. Is there a tutorial to fix this and flash the rooted system.img for the 810g?
Sent from my ASUS_Z00AD using XDA Premium HD app
Once you are on the pr rom you cant go back to at&t right now. Myself and a couple others are working on a method but I have been extremely busy the past week
Thank you for your hard work! I'll keep checking the thread. I bought a ZenFone 2 in the meantime to hold me over.
Sent from my ASUS_Z00AD using XDA Premium HD app
Sorry if it's been asked but interesting in rooting my phone but my build number is h81010o, don't see a root image for it anywhere does it exist? Thanks and sorry again if it's redundant.
Sent from my LG-H810 using Tapatalk
Yes
Cor-master said:
Sorry if it's been asked but interesting in rooting my phone but my build number is h81010o, don't see a root image for it anywhere does it exist? Thanks and sorry again if it's redundant.
Sent from my LG-H810 using Tapatalk
Click to expand...
Click to collapse
Yes there is if you can give me some time I'll find you the link becasue it took me about 30 minutes the first time but it should be in me history so I'll edit when I get it
https://drive.google.com/file/d/0ByR1n8l45m82dUdicXY0dW9IaTA/view
Here is the link @Cor-master it was in my Google drive recents just to make it clear I didn't upload it I just found it
dslix... What about the flash code for the att h81010o? Do you know where i could find it or would the code for the h81010g work? Could it work if i changed the 10g in the code to 10o?
Solice01 said:
dslix... What about the flash code for the att h81010o? Do you know where i could find it or would the code for the h81010g work? Could it work if i changed the 10g in the code to 10o?
Click to expand...
Click to collapse
Follow this guide. Just follow the directions for the H810, and then when you get to this command:
Code:
dd if=/data/media/0/system.rooted.h81010g.img bs=8192 seek=65536 count=579584 of=/dev/block/mmcblk0
Change it to the name of the rooted h81010o image. So it'd become:
Code:
dd if=/data/media/0/system.rooted.h81010o.img bs=8192 seek=65536 count=579584 of=/dev/block/mmcblk0
That's how I rooted mine.
Thanks for the help guys, now I just gotta find time to pull the trigger. I wouldn't even care about root if LG had set the dpi properly. Everything is too big by default, really makes typing a pain and negates the screen size. Used the adb method to change it and it's much better but there's graphical issues that aren't present when you change it the proper way by editing the build prop.
Sent from my LG-H810 using Tapatalk
Please make sure to make a backup of your stock system.img, before flashing the rooted 10o .img, you'll thank me later.
Wont let me download for some reason
Trying to backup before installing the rooted image i get:
[email protected]:/ $ dd if=/dev/block/mmcblk0 bs=8192 skip=65536 count=579584 of=/data/media/0/system.img
lock/mmcblk0 bs=8192 skip=65536 count=579584 of=/data/media/0/system.img <
dd: /dev/block/mmcblk0: Permission denied
Any idea what I'm doing wrong?
*edit - Nevermind...It helps to read lol. I wasn't in download mode before running the command
Rooted 10o with this method. Very easy as long as you read every word of post. Thank You!!
loustu said:
Rooted 10o with this method. Very easy as long as you read every word of post. Thank You!!
Click to expand...
Click to collapse
Is it safe to delete both system.img and systemROOTED.img from internal storage once rooted?
Yes
loustu said:
Is it safe to delete both system.img and systemROOTED.img from internal storage once rooted?
Click to expand...
Click to collapse
Yes if your talking about the ones u move to your phone in the middle of rooting then yes after completing root that one ur told to move to your phone can be deleted
Yes. I saw the two of them together, and I'm guessing the other one is the backup I made of my factory system.img.
Just to clarify... Use the system.rooted.h81010o.img from this thread instead of using the 10g.tar.gz from the guide snowrelyt posted? I ask because they are 2 different size files and want to make sure im doing it right the first time. I know the 10g wont work if I'm on 10o but wasnt sure if one was .img and the other was a tar.gz
antonpace said:
Just to clarify... Use the system.rooted.h81010o.img from this thread instead of using the 10g.tar.gz from the guide snowrelyt posted? I ask because they are 2 different size files and want to make sure im doing it right the first time. I know the 10g wont work if I'm on 10o but wasnt sure if one was .img and the other was a tar.gz
Click to expand...
Click to collapse
If you wanted to root your device just used the .img file..
Thanks for this thread. Finally rooted without a problem!
antonpace said:
Thanks for this thread. Finally rooted without a problem!
Click to expand...
Click to collapse
i rooted success. but if i restart my device, it's show " android system has stoped working". i cant do anything. i must tot to the stock firmware and my device come back unroot
Hey I tried this with the 10o image but something has gone wrong. I was moving it to root of phone and windows made the usb disconnect sound. Now my phone is read only. I've tried mtp. Drag and drop from sd card. I even factory reset phone and even tried flashing 10o firmware with tot file but it's still not writable. Any ideas. Thanks
Cor-master said:
Thanks for the help guys, now I just gotta find time to pull the trigger. I wouldn't even care about root if LG had set the dpi properly. Everything is too big by default, really makes typing a pain and negates the screen size. Used the adb method to change it and it's much better but there's graphical issues that aren't present when you change it the proper way by editing the build prop.
Sent from my LG-H810 using Tapatalk
Click to expand...
Click to collapse
Can you explain this a bit? Just got this phone and trying to learn a bit about it. TIA
gsx1000r02 said:
Can you explain this a bit? Just got this phone and trying to learn a bit about it. TIA
Click to expand...
Click to collapse
Basically in a nutshell the dpi setting is the scaling method, and the lower the number, the smaller everything is on the screen. Allows you to get more screen real estate for your size basically. LG has it set way to high by default. Status bar and navbar end up being huge as a result, and all your ui element's as well. Basically the g4 is set to scale for a 5 inch screen not a 5.5 inch screen
Sent from my SHIELD Tablet K1 using Tapatalk
Cor-master said:
Basically in a nutshell the dpi setting is the scaling method, and the lower the number, the smaller everything is on the screen. Allows you to get more screen real estate for your size basically. LG has it set way to high by default. Status bar and navbar end up being huge as a result, and all your ui element's as well. Basically the g4 is set to scale for a 5 inch screen not a 5.5 inch screen
Sent from my SHIELD Tablet K1 using Tapatalk
Click to expand...
Click to collapse
So this is a build.prop edit you are doing correct? How is it done
There two level of boot animation of an android device, right? And to change the system one is to go to /system/media or /system/customize/resource to change the boouanimation.zip. But is there any method for me to change the animation show earlier than the system one ( perhaps it is from /boot ? I dont know, I want to search for clues but I even dont know what the keyword is ).
I am using an htc 2014 phone btw.
iSaidyiu said:
There two level of boot animation of an android device, right? And to change the system one is to go to /system/media or /system/customize/resource to change the boouanimation.zip. But is there any method for me to change the animation show earlier than the system one ( perhaps it is from /boot ? I dont know, I want to search for clues but I even dont know what the keyword is ).
I am using an htc 2014 phone btw.
Click to expand...
Click to collapse
Usually not, as that part is in the bootloader, and only the manufacturer can change that.
jisoo said:
Usually not, as that part is in the bootloader, and only the manufacturer can change that.
Click to expand...
Click to collapse
Thanks for your reply!!!!
However, will there be any ways ( perhaps the OEM method ? idk.... ) for us to export the bootloader so that we can modify it?
iSaidyiu said:
Thanks for your reply!!!!
However, will there be any ways ( perhaps the OEM method ? idk.... ) for us to export the bootloader so that we can modify it?
Click to expand...
Click to collapse
To install a modified bootloader, usually it needs to be cryptographically signed, and only the OEM has the signing keys. So in practical terms, it is not possible for us users to modify the bootloader in any way.
There are some cases where some of the files used by the bootloader are stored on user-accessible storage, and in this case modifying those is feasible. But this is more exception than norm, and you'll need to read through your device forums to see if anyone has investigated this.
I will take a look in it. Thanks for your reply after all!!!