So im working on trying to get twrp up on the HD 8 but i need a backup of someones elses recovery. Its located at /dev/block/mmcblk0p7
Update please if you have root, go to adb then type adb shell and then su. after that just run this command dd if=/dev/block/mmcblk0p7 of=/storage/sdcard1/recovery.img, if you want it to go somewhere else then just change the part that says storage/sdcard1(for example if you want it to go to the device storage then just remove the 1) the recovery image should then be on your sd card. please then attach or send the recovery image to me. Thank you
Hi, please find attached the recovery file!
coopmaster said:
Update please if you have root, go to adb then type adb shell and then su. after that just run this command dd if=/dev/block/mmcblk0p7 of=/storage/sdcard1/recovery.img, if you want it to go somewhere else then just change the part that says storage/sdcard1(for example if you want it to go to the device storage then just remove the 1) the recovery image should then be on your sd card. please then attach or send the recovery image to me. Thank you
Click to expand...
Click to collapse
Hi, please find attached the recovery file!
schr01 said:
Hi, please find attached the recovery file!
Click to expand...
Click to collapse
Thank you so much. I needed that so I can compare also because I changed mine and I should have backed it up first.
Any luck on compiling twrp?
madsc13n41s4 said:
Any luck on compiling twrp?
Click to expand...
Click to collapse
would not matter, there is no way to use it
Sent from my KFFOWI using XDA Labs
coopmaster said:
So im working on trying to get twrp up on the HD 8 but i need a backup of someones elses recovery. Its located at /dev/block/mmcblk0p7
Click to expand...
Click to collapse
How die you Figure Out where located?
thebrainkafka said:
How die you Figure Out where located?
Click to expand...
Click to collapse
i think i was following some link i found that explains where the recovery normally is. PM if you want to talk more about it.
Related
I figured since getting a replacement A500 and updating to Acer_A500_1.139.04_COM_GEN1 I would update this post with the images.
System.img - http://www.fileserve.com/file/gvemmYd
Flexrom.img - http://www.fileserve.com/file/Suq5yBG
Boot.img - http://www.fileserve.com/file/sSjqpME
Hope this helps anyone.
Kernel Information: Linux localhost 2.6.36.3 #1 SMP PREEMPT Wed May 11 22:11:55 CST 2011 armv7l GNU/Linux
103 views and no-one is able to do it? I am sure there are quite a few Aussies on this forum. :-(
i would if i knew how
splinter6 said:
i would if i knew how
Click to expand...
Click to collapse
Here is your "knew how"... jejeje
You have to ROOT your A500 first... then use terminal emulator and type SU (this will give it Super User Access) then use the following commands:
dd if=/dev/block/mmcblk0p3 of=/sdcard/system.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/flexrom.img
This will give you the actual system image (first command)
Second command gives you the partition where the update information is located.
Let me know if you need help rooting, its really easy, just remember to have your tablet in PORTRAIT not landscape or Gingerbreak will FORCE CLOSE!!!
Hope this helps... jejeje
I got a replacement A500 from JB HiFi. I will update to Acer_A500_1.139.04_COM_GEN1 then create a system.img.
This would be much appreciated! I'm in Australia, and having some issues too. Thanks again.
koprofile said:
This would be much appreciated! I'm in Australia, and having some issues too. Thanks again.
Click to expand...
Click to collapse
I'm at work today. Will hopefully get the system.img uploaded this evening, should take ~2 hours being 600MB and all. :-(
I'm not sure if the flexrom.img is needed though.
that would be appreciated as i have an issue of not being able to update after rooting and NO BACKUP
eliousneo said:
that would be appreciated as i have an issue of not being able to update after rooting and NO BACKUP
Click to expand...
Click to collapse
Here is the untouched Acer_A500_1.139.04_COM_GEN1 system.img.
http://www.fileserve.com/file/gvemmYd
thank you really appreciate it...
question 2 im a noob to all this so could you please let me know how ot install is
i know that it may sound like a dumb question but i have not got a clue.
I only rooted my a500 to be able to install apps to sd and that was a dissapointing move otherwise i think i may keep it stock from now on
thanking you in advance
eliousneo said:
thank you really appreciate it...
question 2 im a noob to all this so could you please let me know how ot install is
i know that it may sound like a dumb question but i have not got a clue.
Click to expand...
Click to collapse
You should be able to just copy the image onto your A500 and run the following as root: dd if=/dev/block/system-1.139.04.img of=/sdcard/mmcblk0p3
Be careful though, I honestly haven't tested the image but it should be fine.
Sent from my A500 using Tapatalk
so that means use command line and copy image onto SD card?
Sounds simple enough just gotta wait for 8 hours for download
Than again juzman very helpfull
Juzman said:
You should be able to just copy the image onto your A500 and run the following as root: dd if=/dev/block/system-1.139.04.img of=/sdcard/mmcblk0p3
Be careful though, I honestly haven't tested the image but it should be fine.
Sent from my A500 using Tapatalk
Click to expand...
Click to collapse
We ALL should start using the MD5 checksum to rule out corrupted file size produced by online downloading
UnicornKaz said:
We ALL should start using the MD5 checksum to rule out corrupted file size produced by online downloading
Click to expand...
Click to collapse
I used the fsum utility on Windows and believe I created an MD5 checksum: 3A0AF183D5E582CBEA1D1F6BC7A61EA6
Will we need the flexrom as well when flashing this system image?
Also, this thread contains some original kernel modules: http://forum.xda-developers.com/showpost.php?p=13974214&postcount=62
Will the modules linked there be compatible with this current AU system image in the event of gps/wifi issues?
Thanks again!
Juzman said:
I used the fsum utility on Windows and believe I created an MD5 checksum: 3A0AF183D5E582CBEA1D1F6BC7A61EA6
Click to expand...
Click to collapse
Is that definitely the correct md5 checksum? I've downloaded the file twice and both times I get an md5 of 850d68aac56169b211a4913de7e4e8e9
Can anyone else confirm?
mapaz04 said:
Here is your "knew how"... jejeje
You have to ROOT your A500 first... then use terminal emulator and type SU (this will give it Super User Access) then use the following commands:
dd if=/dev/block/mmcblk0p3 of=/sdcard/system.img
dd if=/dev/block/mmcblk0p6 of=/sdcard/flexrom.img
This will give you the actual system image (first command)
Second command gives you the partition where the update information is located.
Let me know if you need help rooting, its really easy, just remember to have your tablet in PORTRAIT not landscape or Gingerbreak will FORCE CLOSE!!!
Hope this helps... jejeje
Click to expand...
Click to collapse
Can you say what terminal emulator to use or which is the best one to use?
urdaddi said:
Can you say what terminal emulator to use or which is the best one to use?
Click to expand...
Click to collapse
I used Better Terminal Emulator (with the extensions installed). Make sure after installing the extensions (after the prompt) to go into options, select root by default, then type exit (or CTRL-D) to close the terminal so it reinitializes with all the extensions (the icon on the taskbar must be gone). Afterwards do your stuff. After flashing the system.img the tablet might reboot (show the android boot logo) and cycle. Just power down holding the button long enough, and power back on, then flash the other img.
Hi Me again
dd if=/sdcard/system.img of=/dev/block/mmcblk0p3
I did the above thingy and it just extracted mmcblk0p3 into sdcard
How do i install it ??
i cant just run it so i presume there is some kind of command or something in terminal?
Is it possible to get the flexrom too?
Thanks
Grrr I going to cry
Ok guys so i change the font using an app and after reboot the device get stuck at bootanimation.
The problem is that i can't have acces to system partition so i'm afraid my mojo is softbrick....
i try to update the device using fastboot command (c:/sdk/fastboot update c:/mojo.zip) but i got the "waiting for device" even when it is pluged
Do you have any idea of what i can do to revert the android ttf to stock ??
[Edit] Ok i have to thanks again Paul OBrien for his root method because i simply edit is own boot.img by adding in the superboot folder the stock font and addind line to the script to put it in the right folder and set correct permissions. I go into fastboot, flash reboot and it's finaly repair
AH AH AH AH AH AH AH AH AH
[Edit] i think if someone could make a system.img with just the stock font in it or the stock system.img i should probably able to flash it
Dead-neM said:
[Edit] i think if someone could make a system.img with just the stock font in it or the stock system.img i should probably able to flash it
Click to expand...
Click to collapse
Idk. Maybe try rooting it and see if you can get it to boot. It's very easy to root if you haven't done so already.
mherma said:
Idk. Maybe try rooting it and see if you can get it to boot. It's very easy to root if you haven't done so already.
Click to expand...
Click to collapse
it's already rooted. I don't know want you wanna do at boot
Dead-neM said:
Grrr I going to cry
Ok guys so i change the font using an app and after reboot the device get stuck at bootanimation.
The problem is that i can't have acces to system partition so i'm afraid my mojo is softbrick....
i try to update the device using fastboot command (c:/sdk/fastboot update c:/mojo.zip) but i got the "waiting for device" even when it is pluged
Do you have any idea of what i can do to revert the android ttf to stock ??
Click to expand...
Click to collapse
I know reading in one of the other threads in the mojo general forum that someone took theirs apart and there is 3 buttons inside. You might see if you can locate that thread on how to disassemble it and try holding down on a button while plugging it in. There is no known documentation on what they do but if your bricked what could it hurt.
willdj79 said:
I know reading in one of the other threads in the mojo general forum that someone took theirs apart and there is 3 buttons inside. You might see if you can locate that thread on how to disassemble it and try holding down on a button while plugging it in. There is no known documentation on what they do but if your bricked what could it hurt.
Click to expand...
Click to collapse
Yes i see that in forum but i don't want to open it because it's avoid the warranty
i repair the mojo by an other method i'll update the thread soon thanks
Dead-neM said:
Yes i see that in forum but i don't want to open it because it's avoid the warranty
i repair the mojo by an other method i'll update the thread soon thanks
Click to expand...
Click to collapse
I think rooting it voids the warranty?? which is why I don't get how MC can advertise instructions on their website.
You should raise a support request with them on their site.
Hopefully kitkat is around soon.
Good luck!
We've decided to take an open stance on rooting - it's your box to do with as you wish. Of course the obvious caveats apply that you run the risk of causing boot issues, as Dead-neM has found!
Dead-neM in the interests of sharing, could you detail exactly what changes you made to the script and exactly what you did so it's explicitly spelled out for anyone else who runs into the same issue?
Yeah, how do you mount the superboot.img and modify the contents?
Ok this what i have do exactly hope it can be helpfull so:
1/ Have cygwin + Android kitchen tool on your pc ( This software is use to decompile the boot.img and it can be find into xda forum ) So open it decompile the boot.img of Paul Obrien MmM3 ( Kitchen can't decompile boot if it have not system.img too so i decompile first the 110ww official zip rom and replace the boot img by the Paul Obrien's )
2/Go onto the folder of the decompile Boot.img : So open /boot.img-ramdisk/superboot/ there is a superboot.sh script open it
You can see all command. What you have to do is to put yours before the 3 last line ( mount -o ro, remount -t ext4 ........)
I type { cat /superboot/Clockopia.ttf>/system/fonts/Clockopia.ttf
cat /superboot/Roboto-Regular.ttf>/system/fonts/Roboto-Regular.ttf
chmod 777 /system/fonts/clockopia.ttf
chmod 777 /system/fonts/Roboto-Regular }
cat is used to move file and chmod to set permission
3/ Now i said to the boot img to replace file and set permission to it i need to put the file into the boot.img folder so i just copy the Clockopia and Roboto font into superboot folder
4/Now you can recompile the boot img using kitchen then flash it using Paul Obrien script
Enjoy i think you can put gapps with this method so if there is a courageous one here your welcome !!
Dead-neM said:
Grrr I going to cry
Ok guys so i change the font using an app and after reboot the device get stuck at bootanimation.
The problem is that i can't have acces to system partition so i'm afraid my mojo is softbrick....
i try to update the device using fastboot command (c:/sdk/fastboot update c:/mojo.zip) but i got the "waiting for device" even when it is pluged
Do you have any idea of what i can do to revert the android ttf to stock ??
[Edit] Ok i have to thanks again Paul OBrien for his root method because i simply edit is own boot.img by adding in the superboot folder the stock font and addind line to the script to put it in the right folder and set correct permissions. I go into fastboot, flash reboot and it's finaly repair
AH AH AH AH AH AH AH AH AH
Click to expand...
Click to collapse
i have a black screen problem.
can you tell how you solved your problem?
thanks
angus1225 said:
i have a black screen problem.
can you tell how you solved your problem?
thanks
Click to expand...
Click to collapse
Did you get it solved?
Sent from my LGMS395 using Tapatalk
Unjustified Dev said:
Did you get it solved?
Sent from my LGMS395 using Tapatalk
Click to expand...
Click to collapse
After reading a lot...yes!
I managed to conect mojo to a tv and a laptop to the mojo. Then i turn on mojo in flastboot and using the commsnds that a copy from the superboot.bat. i boot the mojo in twrp recovery and from there i flash the mojo rom.
And i recover the mojo just as i left it before the problem
I wish this helps someone.
[emoji106]
I just had an idea. What if someone roots a system.img by extracting it from a kdz and then mounting it in linux copying the root files setting the permissions and then flashing that with download mode? A simple
Code:
dd if=/data/local/tmp/system.img of=/dev/block/platform/??????/by-name/system
should do the trick to flash the system.img file replacing the ?????? with the correct directory.
Just a thought.
Wouldn't you have to have read/write access in order to push the system.img?
Impossible,without root.
Sent from my LG-D802 using Tapatalk
l33tlinuxh4x0r said:
I just had an idea. What if someone roots a system.img by extracting it from a kdz and then mounting it in linux copying the root files setting the permissions and then flashing that with download mode? A simple
Code:
dd if=/data/tmp/system.img of=/dev/block/platform/??????/by-name/system
should do the trick to flash the system.img file replacing the ?????? with the correct directory.
-
Click to expand...
Click to collapse
Dennisg34 said:
There's already a thread to discuss root. Please search before posting, thanks.
Sent from my G4 using your mom
Click to expand...
Click to collapse
I think both of the previous threads discussing root have been closed. I haven't seen another - did I miss it?
Already tried something similar. Requires root unless you're one of the lucky few who have such advanced knowledge of hacking bootloaders/exploits....which I unfortunately am not. LOL
rfarrah said:
I think both of the previous threads discussing root have been closed. I haven't seen another - did I miss it?
Click to expand...
Click to collapse
Apologies, I forgot they were.
Hello,
It is possible to rooter lg g4 with : V10B LGH815
thank you :fingers-crossed:
dydyfr said:
Hello,
It is possible to rooter lg g4 with : V10B LGH815
thank you :fingers-crossed:
Click to expand...
Click to collapse
Yes, look in the developer section.
It is possible to dd to partitions using download mode. The only real problem is that the root method would be huge having to include a system.img.
l33tlinuxh4x0r said:
It is possible to dd to partitions using download mode. The only real problem is that the root method would be huge having to include a system.img.
Click to expand...
Click to collapse
Additionally, you'd need a separate one for every carrier/variant.
I guess if it worked though, who cares how many we need or how big they are. Except with dd, one typo and you've got yourself a brick.
tabp0le said:
Additionally, you'd need a separate one for every carrier/variant.
I guess if it worked though, who cares how many we need or how big they are. Except with dd, one typo and you've got yourself a brick.
Click to expand...
Click to collapse
very true.
tabp0le said:
Additionally, you'd need a separate one for every carrier/variant.
I guess if it worked though, who cares how many we need or how big they are. Except with dd, one typo and you've got yourself a brick.
Click to expand...
Click to collapse
l33tlinuxh4x0r said:
very true.
Click to expand...
Click to collapse
Though...wouldn't it still be able to get into download mode? I could be wrong, but that's not on the system partition from my understanding.
I'm on linux and am familiar with dd (I'm a distro-hopper and have no optical drive, so everything gets dd'ed onto usb drive).
Wouldn't we have to specify a block size on that? I know at least on linux distro, if block size isn't specified, I end up in non-boot.
geoff5093 said:
Yes, look in the developer section.
Click to expand...
Click to collapse
Good
Thank's
Sent from my Iconia A3-A20 FHD using XDA Free mobile app
Th3Bill said:
Though...wouldn't it still be able to get into download mode? I could be wrong, but that's not on the system partition from my understanding.
I'm on linux and am familiar with dd (I'm a distro-hopper and have no optical drive, so everything gets dd'ed onto usb drive).
Wouldn't we have to specify a block size on that? I know at least on linux distro, if block size isn't specified, I end up in non-boot.
Click to expand...
Click to collapse
Actually you are correct. The laf partition is the download mode. Flashing recovery is where we have to worry about losing download mode. (I never understood why, but at least with the G2 download mode broke when flashing custom recovery without a certain patch)
The previous root threads were locked because peopel wouldn't stay on topic after multiple warnings...
Eagle1337 said:
The previous root threads were locked because peopel wouldn't stay on topic after multiple warnings...
Click to expand...
Click to collapse
Correction, they were closed per OP request
This one is now clean, lets try to stay on topic,
If anyone feels the urge to regurgitate further horse crap... we'll see what happens
l33tlinuxh4x0r said:
It is possible to dd to partitions using download mode. The only real problem is that the root method would be huge having to include a system.img.
Click to expand...
Click to collapse
How can you confirm being able to dd to partitions using download mode? In download mode isn't the dd running from /system/bin that is mounted as ro. How could you replace /system while it is mounted and running dd from it?
gbgadgets said:
How can you confirm being able to dd to partitions using download mode? In download mode isn't the dd running from /system/bin that is mounted as ro. How could you replace /system while it is mounted and running dd from it?
Click to expand...
Click to collapse
linux loads commands that you are in the process of running into ram. You can even delete a file that you are running and still be able to use it until you close it. Once you close it is when the problem would occur but by that time you would already have the new file in place. Also do NOT run a
Code:
dd if=/dev/zero of=/dev/block/platform/??????/by-name/system
just skip that step otherwise you would lose the ability to dd.
Go directly for a
Code:
dd if=/data/local/tmp/system.img of=/dev/block/platform/??????/by-name/system
also to get a system.img instead of extracting from a kdz you could run
Code:
dd if=/dev/block/platform/??????/by-name/system of=/data/local/tmp/system.img
docfreed said:
Wouldn't you have to have read/write access in order to push the system.img?
Click to expand...
Click to collapse
you can push to /data/local/tmp using adb without root.
So I did the step to here.But do not know how to get system.img/boot.img/bootloader.img(most want).Any developers help?
jackzhu said:
So I did the step to here.But do not know how to get system.img/boot.img/bootloader.img(most want).Any developers help?
Click to expand...
Click to collapse
You could try this not sure if it work haven't tried yet use terminal emulator
Run this first and it will list your img you want
ls -al /dev/block/platform/soc/1da4000.usfhc/by-name
dd if=/dev/block/platform/soc/1da4000.ufshc/by-name (the img you want) of=/sdcard/ (your img)
You can use this command to dump any partition updated command
tattedup said:
You could try this not sure if it work haven't tried yet use terminal emulator
Run this first and it will list your img you want
ls -al /dev/block/platform/soc/1da4000.usfhc/by-name
dd if=/dev/block/platform/soc/1da4000.ufshc/by-name (the img you want) of=/sdcard/ (your img)
You can use this command to dump any partition updated command
Click to expand...
Click to collapse
You mean xxx_a.img is same as xxx_b.img?
jackzhu said:
You mean xxx_a.img is same as xxx_b.img?
Click to expand...
Click to collapse
If you flash the stock restore from invisiblek yes the a and b img should be the same, I think not positive not much knowledge on a and b partitions. But what I got from invisiblek's post is that is correct.
tattedup said:
If you flash the stock restore from invisiblek yes the a and b img should be the same, I think not positive not much knowledge on a and b partitions. But what I got from invisiblek's post is that is correct.
Click to expand...
Click to collapse
Thank you, I will dump it for try .
jackzhu said:
Thank you, I will dump it for try .
Click to expand...
Click to collapse
I'm sure I get the boot.img. do you know which is/are bootloader.img?
I accidentally flashed persist partition on another phone.
As a result, all sensors are not working now.
I haven't backed up that partition.???
Therefore i would like to ask someone to backup persist partition and share the image file with me.
parklrain said:
I accidentally flashed persist partition on another phone.
As a result, all sensors are not working now.
I haven't backed up that partition.
Therefore i would like to ask someone to backup persist partition and share the image file with me.
Click to expand...
Click to collapse
How can I do a backup for you?
see attach, unzip and flash using dd command
foobar66 said:
see attach, unzip and flash using dd command
Click to expand...
Click to collapse
Thanks!
But I don't know how to use the dd command.
Can I use fastboot command to flash?
abenssss said:
How can I do a backup for you?
Click to expand...
Click to collapse
I don't know exactly how, but you can use dd command to back up.
I don't know the exact file path.
foobar66 said:
see attach, unzip and flash using dd command
Click to expand...
Click to collapse
Thank you very much!
The img.persist file was renamed to Persist.img, and the bootloader flash using the fastboot command, and the sensor returned to normal.
My cell phone is alive.
Thank you!!
parklrain said:
Thank you very much!
The img.persist file was renamed to Persist.img, and the bootloader flash using the fastboot command, and the sensor returned to normal.
My cell phone is alive.
Thank you!!
Click to expand...
Click to collapse
i have the same problem. Which code do you type in the shell?
foobar66 said:
see attach, unzip and flash using dd command
Click to expand...
Click to collapse
for what type of phone?