Hi.i have a GT-i5801 stock I5801DXJPC FW and is also rooted..i want to enable JIT on this FW but cant seem to work.i followed the instructions in this thread http://forum.xda-developers.com/showthread.php?t=1026870 but when i copy the lib files into the lib folder in the system by root explorer the app seems to close and i seem to lose my superuser.can you please give me the simpliest instructions or please provide a I5801DXJPC with JIT enabled.
Thank you very much and i hope you all the best.please help me:'((
Try to use a ADB-command to put the files there, there was a command somewhere here on XDA
can you please give me a detailed instruction about how to push files using adb?
macalino22 said:
can you please give me a detailed instruction about how to push files using adb?
Click to expand...
Click to collapse
no command need. just extract the "jit" folder (is into the zip) and run the batch script
link: http://forum.xda-developers.com/attachment.php?attachmentid=563441&d=1302230974
where will i extract the zip and can you please tell me what is a batch script?
when i extracted the zip and put my CP on debugging mode i clicked the enable_jit.cmd but it says that when it chmod it was operation not permitted
With the new OTA being released many are asking how to restore stock recovery. I think that the original /system/etc/install-recovery.sh file is required, unfortunately I did not make a backup. Does anyone have a copy of the original version of this file? Please post it here if you have it and anyone who knows how to restore stock recovery please post any helpful instructions here. If I get the file and proper instructions I will update the OP accordingly. Thanks.
I made a backup but have no idea how to extract that file.
You have to write which TPT you have.
US or....?
16, 32 or 64GB?
toenail_flicker said:
I made a backup but have no idea how to extract that file.
Click to expand...
Click to collapse
What did you backup with? If you backed it up after installing CWM then it was probably already gone (which is why I don't have it).
In the ROW instructions they cleverly added this line to the install instructions:
cp /system/etc/install-recovery.sh /system/etc/install-recovery.sh.backup
which creates a backup of the file in /system/etc/
If you did this then you should be able to copy the file install-recovery.sh.backup from /system/etc/ using root explorer or adb.
I have the US 32GB version, I'm not sure if the files are the same but I would guess that they are. Anyway if you can get the file that would be great.
I have 183827U 64GB. Yes, I made a Nandroid backup after installing CMW. I also have Titanium and MyBackup saves, but have no idea if they save the file. I'll go looking for it with RE and let you know what I find.
---------- Post added at 01:47 PM ---------- Previous post was at 01:41 PM ----------
Seems I have install-recovery.sh but the date is recent, so I guess it's from when I rooted. No backup of the same name.
Mine is:
#!/system/bin/sh
if ! applypatch -c EMMC:/dev/block/mmcblk0p1:2048:0a48c18ee1ca32bba5a785d8ea8b6976fc0a190e; then
log -t recovery "Installing new recovery image"
applypatch EMMC:/dev/block/mmcblk0p2:3170304:fa229b8ff37128302094316ea4ced3d68ad5edcf EMMC:/dev/block/mmcblk0p1 53a249cd150c483f9255eba03adccdf6e7c014a6 3524608 fa229b8ff37128302094316ea4ced3d68ad5edcf:/system/recovery-from-boot.p
else
log -t recovery "Recovery image already installed"
fi
WE-TPT-64GB
OK . We all i believe find it chaotic to organize in forums now. So this is a thread just for ideas and problem with cwm or twrp on our device.
All that i have found now is that recovery.img is somehow backed with boot.img. So i have to ask if there is any developer that can look inside this.
Help appreciated. We (developers) have already compiled TWRP and CWM ( me via ubuntu and clockworkmod recovery builder) and none of them is booting.
You might want to look at xperia p boot.img??? Same processor u8500 same screen size. I'm a noob. Just said what I felt. Coming from xperia device where our recoveries are always packed inside boot.img
In ramdisk . /sbin/recovery is where our recovery binary is present.
#pitchblack5691#
thanks for help ! i will definetely looo for it
Might be useful
http://forum.xda-developers.com/showthread.php?t=2020895
http://forum.xda-developers.com/showthread.php?t=1903017
#pitchblack5691#
also coming from xperia forum and for My xperia U and have also novathor u8500 and i have asked dev to explain mothod used in XU for port this method to GIII mini but no reply from him now in XU the recovery are in tar and flashable to phone without odin or another flash only by ADB + run me script in commande window inside recovery tar we have unziped recovery ( icone ....) and some files relative to phone ( fstab ..... )
How is it going? Did everyone stop developing or are you guys just moving in silence trying to figure things out?
Sent thru time and space from my s3mini.
silently moving
Shapeshift said:
silently moving
Click to expand...
Click to collapse
Good to know! Give us a shout if we can help somehow.
currently working on cwm 6. dont know why i cant boot
Perhaps need to no only make recovery but also kernel ?
If this 2 filz run together
Sent from my GT-I8190 using xda app-developers app
From what I understand, You just need to write a piece of code in the ramdisk init files to execute the recovery during boot. No need to modify the kernel.
#pitchblack5691#
If any one is interested i got a dumped ram disk also a got it rebuild-ed,
and yes the recovery scripts are there plus the pngs etc.
I also believe that the device has 2 recovery's, they are the same one just acts as a backup.
is an idea
i explain when you make recovery and extract it you find some files inside ( fstab , RC , init , propr ...
now we have also one with CM device info the device have not CM rom and also have not CM kernel her why i posted this comment because when you extract stock recovey you find kernel part and when you extract boot.img find recovery part now this 2 files perhaps have dependency to work together ? is an idea do not yell at me :silly:
spawk said:
is an idea
i explain when you make recovery and extract it you find some files inside ( fstab , RC , init , propr ...
now we have also one with CM device info the device have not CM rom and also have not CM kernel her why i posted this comment because when you extract stock recovey you find kernel part and when you extract boot.img find recovery part now this 2 files perhaps have dependency to work together ? is an idea do not yell at me :silly:
Click to expand...
Click to collapse
They had the internet in 1969?
Take your time. We have root and what roms we have are stable.
Sent from Spaceball One.
Hahaha!
Sent thru time and space from my s3mini.
xd the error is not from me haha i have corect date and time
is new technologie hahahaha retoure backwards in android
and if you see here you can read need new builded kernel to make CWM just read thread 2# and 3# http://forum.xda-developers.com/showthread.php?t=1771347
Help ful apps find on playstore this apps need busybox 2.1 and rooted rom and he let you backup your rom but without boot.img and recovery.img but bacup all system data ..... here is https://play.google.com/store/apps/details?id=com.pommedeterresautee.twoborange3
spawk said:
Help ful apps find on playstore this apps need busybox 2.1 and rooted rom and he let you backup your rom but without boot.img and recovery.img but bacup all system data ..... here is https://play.google.com/store/apps/details?id=com.pommedeterresautee.twoborange3
Click to expand...
Click to collapse
I sent info about device to that developer. That app is now supporting our golden for full backup incl boot & recovery.img with .zip from here. Only problem is we dont have a working custom recovery to flash that .zip with :/
as Faria wrote above should change the recovery that is in the kernel and the same meter and the same rom in it and in the kernel for which you go just tell me that the two are complementary if a move (size , addition, retirees), the other answers are more about the two is that one feature that the other is that we will say to his control as .
now change I believe that both will adjust in any case theoretically
Normally, I would post this in the MultiROM thread, but I can't post in there without 10 posts. Thus, I am posting it in the Q&A.
Anyway, is it possible to take a nandroid backup of a specific rom which I multiboot using MultiROM. Ie, so I could flash to internal, move between devices, or copy back to MultiROM after a factory restore.
If you find this explanation confusing, please ask and i'll try and fix it.
I did google/search around for a while before asking, I found nothing though.
Bump +1
--------------
Did a little digging, it seems that the only way to do this right now is a manual process. Please, someone, tell me I'm wrong! You'll have to tar out the root directory with this command after booting into the rom:
cd root
sudo tar --numeric-owner -zpcf root.tar.gz ./*
You'll then need to use the information on https://github.com/Tasssadar/multirom/tree/nexus7/ref_install_zip to create the proper file/folder structure. Slap your /root.tar.gz into that folder structure, zip it up, and you have yourself a flashable zip backup.
Remember:
-Root cannot exceed ~850MB
-This is a pain in the @$$
-I'd try scripting this for you but its Friday and I'm beat
Indeed....
HumanCaviar said:
Bump +1
--------------
Did a little digging, it seems that the only way to do this right now is a manual process. Please, someone, tell me I'm wrong! You'll have to tar out the root directory with this command after booting into the rom:
cd root
sudo tar --numeric-owner -zpcf root.tar.gz ./*
You'll then need to use the information on to create the proper file/folder structure. Slap your /root.tar.gz into that folder structure, zip it up, and you have yourself a flashable zip backup.
Remember:
-Root cannot exceed ~850MB
-This is a pain in the @$$
-I'd try scripting this for you but its Friday and I'm beat
Click to expand...
Click to collapse
Bump +1 plus whatever it takes.
This method is very time consuming, and onandroid botches the whole backup thing with a disk space error while in an alternate ROM. Sigh... wish there was an easy solution to this.
HumanCaviar said:
Bump +1
--------------
Did a little digging, it seems that the only way to do this right now is a manual process. Please, someone, tell me I'm wrong! You'll have to tar out the root directory with this command after booting into the rom:
cd root
sudo tar --numeric-owner -zpcf root.tar.gz ./*
You'll then need to use the information on (urlstripped) to create the proper file/folder structure. Slap your /root.tar.gz into that folder structure, zip it up, and you have yourself a flashable zip backup.
Remember:
-Root cannot exceed ~850MB
-This is a pain in the @$$
-I'd try scripting this for you but its Friday and I'm beat
Click to expand...
Click to collapse
OK, where do you issue these commands from? Can't be the N7 because it doesn't have a sudo command... and can't seem to write to /root...
Is it possible to take backup of all roms at once?
Skyshayde said:
Normally, I would post this in the MultiROM thread, but I can't post in there without 10 posts. Thus, I am posting it in the Q&A.
Anyway, is it possible to take a nandroid backup of a specific rom which I multiboot using MultiROM. Ie, so I could flash to internal, move between devices, or copy back to MultiROM after a factory restore.
If you find this explanation confusing, please ask and i'll try and fix it.
I did google/search around for a while before asking, I found nothing though.
Click to expand...
Click to collapse
Is it possible to take backup of all roms at once?
Hello,
Please and thanks in advance for any assistance!
I've successfully rooted my HD8 7th gen fire tablet, thanks to the many helpful posts here. However during some of my failed attempts while using Magisk, TWRP App, etc, I've somehow managed to wipe out my stock Recovery partition/files. I can do normal booting fine and I'm sure that I have root, as confirmed by the # at ADB shell and the Root Checker apps available.
I've tried the following:
-Entered Fastboot mode and tried several commands there: always resulting in a 'the command you input is restricted on locked hw' (So, obviously, my bootloader is locked (but I've overwritten it somehow, so it makes me think that at some point I was able to unlock it and overwrite it?)
-Flashfire, TWRP, Magisk and Flashify apps - successful messages every time I try, but no joy when trying to enter recovery mode (it's possible I'm trying to flash the wrong recovery.img file? - does anyone have it and what is it's size? i searched my tablet for the file and found two: one 17mb and the other 8mb - both "flashed" successfully, but no joy when trying to boot into them)
-adb su commands
-Giving up and doing a full Factory Restore via the GUI - it just tries to reboot to the recovery mode, which doesn't exist, so i can't do anything.
-Giving up and doing a full Factory Restore via Fastboot mode - 'the command you input is restricted on locked hw'
I was so happy I was able to obtain root, but if something gets wonky or I decide to try the much raved about resurrection image, i need to have the recovery boot available if/when everything goes wrong.
Please and thanks again for any advice.
Daveychan said:
Please and thanks again for any advice.
Click to expand...
Click to collapse
It's fairly simple but cumbersome to recreate recovery with root. You need to locate the original install-recovery script for your Rom. You may search in /etc or /system/etc . Most likely though your SuperSu deleted it.
So you download your particular Rom version from amazon, unpack it into a system image via mtk-extractor, mount that system image, and find the files.
You can mount this extracted system.bin either on Linux, or directly on your tablet. Just push it to /sdcard, and do this: https://stackoverflow.com/questions/36448234/how-to-mount-a-loop-device-in-android
Then you run the full install-recovery script which will patch your boot.img into recovery partition.
Alternatively, you can beg someone here to dump their HD8 2017 recovery, and upload the image here. So you can dd it in using root into the appropriate partition.
See, I told you - it's all very simple !
Edit: @dondraper23 - can you help a fellow XDA-er? Just dd your HD8 2017 recovery, and post it here.
Code:
dd if=/dev/block/platform/soc/by-name/recovery of=/sdcard/recovery.img
Then zip it, and post it here.
Thank you very much for the fast reply. Much appreciated!
I’ll give this a try ASAP and post back.
If anyone has the recovery.img for the HD8 Gen7, please do post it.
Thank you again!
Okay, i've spent several hours on this and I need to ask for more help.
I managed to get the system.img file from the Amazon .bin as you described. (I used the MTK Extractor for that. It's 1.57 GB by the way.) Next, I moved the system.img file to my Fire's SD card, then I connected the Fire to my Linux, and mounted the system.img file in Linux so I can see the file directory.
I can now see the install-recovery.sh file, located in the /bin folder of the mounted image, but it's read-only. Even by opening to that path via terminal with SU and trying to chmod 777 the file, it's still locked as read-only.
So, I don't know what to do next. I can't copy the file, and I don't see how to run the file via Fire anyway. (Was I supposed to somehow mount the system.img file via ADB commands and then run it that way? If so, I don't know how to do that.)
Sorry if I've asked something obvious or silly. As before, I appreciate the assistance!
Please and Thanks!
Daveychan said:
Okay, i've spent several hours on this and I need to ask for more help.
I managed to get the system.img file from the Amazon .bin as you described. (I used the MTK Extractor for that. It's 1.57 GB by the way.) Next, I moved the system.img file to my Fire's SD card, then I connected the Fire to my Linux, and mounted the system.img file in Linux so I can see the file directory.
I can now see the install-recovery.sh file, located in the /bin folder of the mounted image, but it's read-only. Even by opening to that path via terminal with SU and trying to chmod 777 the file, it's still locked as read-only.
So, I don't know what to do next. I can't copy the file, and I don't see how to run the file via Fire anyway. (Was I supposed to somehow mount the system.img file via ADB commands and then run it that way? If so, I don't know how to do that.)
Sorry if I've asked something obvious or silly. As before, I appreciate the assistance!
Please and Thanks!
Click to expand...
Click to collapse
Sure, just copy that install-recovery.sh file to your tablet, into /data/local/tmp. There is also another file you will need, it's /system/recovery-from-boot.p . Copy this one to /data/local/tmp as well. Then edit your install recovery script, to point to this /data/local/tmp/recovery-from-boot.p . Then just su, chmod 777 your install recovery script, and run it. It should take your boot, and patch it into recovery using recovery-from-boot.p patch file.
Thank you for the fast reply. But because that sh file its read-only, I can't open it or copy it.
Error when running the script
Hello again,
I managed to get around the read-only problem (opening everything as Superuser in Linux was the trick to making that work, for other noobs who may be following along with my pain here.)
I grabbed those two files as you indicated and followed the instructions. Unfortunately I was met with a ton of error messages. Here they are:
=====================
[email protected]:/data/local/tmp # /data/local/tmp/install-recovery.sh
contents of partition "/dev/block/platform/mtk-msdc.0/by-name/recovery" didn't match EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery:7022592:38eeb844c578f6bbfb6edf8ddf7ba1112200a25c
file "EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery:7022592:38eeb844c578f6bbfb6edf8ddf7ba1112200a25c" doesn't have any of expected sha1 sums; checking cache
failed to stat "/cache/saved.file": No such file or directory
failed to load cache file
patch EMMC:/dev/block/platform/mtk-msdc.0/by-name/boot:4720640:9dc6d0ebab0b237a7b2f31ae0fabe026da83cda5: LoadPartitionContents called with bad filename (EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery)
contents of partition "/dev/block/platform/mtk-msdc.0/by-name/recovery" didn't match EMMC:/dev/block/platform/mtk-msdc.0/by-name/recovery
contents of partition "/dev/block/platform/mtk-msdc.0/by-name/boot" didn't match EMMC:/dev/block/platform/mtk-msdc.0/by-name/boot:4720640:9dc6d0ebab0b237a7b2f31ae0fabe026da83cda5
source file is bad; trying copy
failed to stat "/cache/saved.file": No such file or directory
failed to read copy file
=====================
I'm attaching the two files i pulled from the system.img file - as converted from the .bin file downloaded from Amazon (as above), in case you are still willing to help out and can take a look. (I edited the install-recovery.sh file to the correct path already, so it's not the original anymore.)
MUCH APPRECIATED!
Thank you!
Daveychan said:
Hello,
Please and thanks in advance for any assistance!
I've successfully rooted my HD8 7th gen fire tablet, thanks to the many helpful posts here. However during some of my failed attempts while using Magisk, TWRP App, etc, I've somehow managed to wipe out my stock Recovery partition/files. I can do normal booting fine and I'm sure that I have root, as confirmed by the # at ADB shell and the Root Checker apps available.
I've tried the following:
-Entered Fastboot mode and tried several commands there: always resulting in a 'the command you input is restricted on locked hw' (So, obviously, my bootloader is locked (but I've overwritten it somehow, so it makes me think that at some point I was able to unlock it and overwrite it?)
-Flashfire, TWRP, Magisk and Flashify apps - successful messages every time I try, but no joy when trying to enter recovery mode (it's possible I'm trying to flash the wrong recovery.img file? - does anyone have it and what is it's size? i searched my tablet for the file and found two: one 17mb and the other 8mb - both "flashed" successfully, but no joy when trying to boot into them)
-adb su commands
-Giving up and doing a full Factory Restore via the GUI - it just tries to reboot to the recovery mode, which doesn't exist, so i can't do anything.
-Giving up and doing a full Factory Restore via Fastboot mode - 'the command you input is restricted on locked hw'
I was so happy I was able to obtain root, but if something gets wonky or I decide to try the much raved about resurrection image, i need to have the recovery boot available if/when everything goes wrong.
Please and thanks again for any advice.
Click to expand...
Click to collapse
You shuld try:
-Extract an ota update in a folder
-Run from the folder with the extracted files
Code:
fastboot flash boot boot.img
the recovery is in boot.img, doing this helped me on a similar situation
Thanks to @bibikalka for pointing me to this thread
On the 7th gen fire hd8 TWRP doesn't work yet
t0x1cSH said:
You shuld try:
-Extract an ota update in a folder
-Run from the folder with the extracted files
Code:
fastboot flash boot boot.img
the recovery is in boot.img, doing this helped me on a similar situation
Thanks to @bibikalka for pointing me to this thread
On the 7th gen fire hd8 TWRP doesn't work yet
Click to expand...
Click to collapse
It's not enough to reflash boot.img ! Recovery is created on boot by patching boot.img, but the OP's fire has messed up recovery creation scripts due to SuperSu. So he needs to either re-run the recovery creation script manually - which seems to produce errors, or simply flash a full recovery image - hence my request to extract it from a fire with working recovery.
Hey, I'll pull the recovery off mine tomorrow
NFSP G35 said:
Hey, I'll pull the recovery off mine tomorrow
Click to expand...
Click to collapse
That would be fantastic! Thank you much!
Here you go
Daveychan said:
That would be fantastic! Thank you much!
Click to expand...
Click to collapse
Just FYI, to flash this image file into recovery (assuming you have the recovery image sitting in /sdcard/recovery.img):
Code:
dd if=/sdcard/recovery.img of=/dev/block/platform/mtk-msdc.0/by-name/recovery
bibikalka said:
It's not enough to reflash boot.img ! Recovery is created on boot by patching boot.img, but the OP's fire has messed up recovery creation scripts due to SuperSu. So he needs to either re-run the recovery creation script manually - which seems to produce errors, or simply flash a full recovery image - hence my request to extract it from a fire with working recovery.
Click to expand...
Click to collapse
this is the recovery partition straight from my hd8 2017
but i am very curious about a thing, if you look at booth the boot.img and the recovery partition they contains exactly the same data, in the same structure so why cant he simply flash boot.img?
t0x1cSH said:
this is the recovery partition straight from my hd8 2017
but i am very curious about a thing, if you look at booth the boot.img and the recovery partition they contains exactly the same data, in the same structure so why cant he simply flash boot.img?
Click to expand...
Click to collapse
They do have a lot of similarities, that's why recovery is created by patching boot via a relatively small patch file. But, they are still different! That recovery menu is contained entirely within the recovery image, while the boot image does not do that.
Just to add to this, you don't need to flash the boot.img to use install-recovery.sh.
You can also modify the script to read boot from an img file.
k4y0z said:
Just to add to this, you don't need to flash the boot.img to use install-recovery.sh.
You can also modify the script to read boot from an img file.
Click to expand...
Click to collapse
Do you care to post a script that does that, and writes into a recovery image file? The syntax of that patch command is a bit messy, so I would not mind having a debugged working script
Hello again,
My apologies for the delay, work was busy this week, and I couldn't find the time to check the solution until now.
I'm so VERY HAPPY to report that all worked well, and the recovery.img and the command line you provided worked perfectly. (WOW! Thank you!)
For those who want the details, the message after the command in the terminal was:
==
#dd if=/sdcard/recovery.img of=/dev/block/platform/mtk-msdc.0/by-name/recovery
----
34816+0 records in
34816+0 records out
17825792 bytes transferred in 1.159 secs (15380320 bytes/sec)
==
I then did a full power down, and then a started it up again while holding the top-left Volume key and the Power key, and look at that! I'm sitting at the Amazon system recovery screen again! <insert YAY! here>
I'm not sure if it matters, but I thought I'd mention it. At the bottom of the screen in orange letters, it says:
===
E:Error in /cache/recovery/last_kmsg
(No space left on device)
===
So, after a little bit of searching, I selected "wipe cache partition", rebooted again into recovery, and the error is gone now.
Another normal reboot started the "Optimizing apps..." thingy, but it finished quickly and I can confirm that all my stuff is still there. Just to be sure, I did another reboot to recovery, no error messages this time, and then another regular reboot, with no optimizing.
It appears that everything in my world is good again!
My sincerest gratitude and appreciation to all who helped contribute and support this solution.
THANK YOU VERY MUCH!
Daveychan said:
the much raved about resurrection image .
Click to expand...
Click to collapse
Out of curiosity, what is this? There is an image, other than stock, for the 7th Gen HD8?
Resurrection-remix
xnatex21 said:
Out of curiosity, what is this? There is an image, other than stock, for the 7th Gen HD8?
Click to expand...
Click to collapse
It's a WIP for the HD8 I've read. My friend has this on his HD7 and swears it's twice as fast as the regular.
Here's some info:
https://forum.xda-developers.com/kindle-fire-hd/7-development/rom-resurrection-remix-5-1-x-t3234535
and here:
https://forum.xda-developers.com/le-pro3/development/9-0-resurrection-remix-v7-0-t3894663