Database Users

[Q] Stock AU A500

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

SDCARD hard brick recovery WIP, need dumps

I am working on getting a proper MJE SDCARD debrick image. I will need memory dumps of the boot partitions.
From ADB shell or terminal emulator run the following command
dd if=/dev/block/mmcblk0 of=/sdcard/unbrick.img bs=512 count=524288
This will place a file called unbrick.img into /sdcard (not your actual memory card (extSdCard) but your internal device memory. All I need you to do is upload this file anywhere you see fit so I can download it. I greatly appreciate your time!
At this time, I am only looking for retail SM-N900V MJE dumps.

ryanbg said:
I am working on getting a proper MJE SDCARD debrick image. I will need memory dumps of the boot partitions.
No sensitive data will be dumped with this command, and you will be helping the community out greatly if you have the time.
From ADB shell or terminal emulator run the following command
dd if=/dev/block/mmcblk0 of=/sdcard/unbrick.img count=524288
This will place a file called unbrick.img into /sdcard (not your actual memory card (extSdCard) but your internal device memory. All I need you to do is upload this file anywhere you see fit so I can download it. I greatly appreciate your time!
At this time, I am only looking for retail SM-N900V MJE dumps.
Click to expand...
Click to collapse
Retail or DE? Or does it matter?

cam30era said:
Retail or DE? Or does it matter?
Click to expand...
Click to collapse
Preferably retail, but if you have DE, go ahead anyways. Maybe I'll be able to find something new. As long as it's MJE.

ryanbg said:
Preferably retail, but if you have DE, go ahead anyways. Maybe I'll be able to find something new. As long as it's MJE.
Click to expand...
Click to collapse
That may be a problem. While baseband is MJE, ROM is CM11. That surely won't work. Sorry about that.

cam30era said:
That may be a problem. While baseband is MJE, ROM is CM11. That surely won't work. Sorry about that.
Click to expand...
Click to collapse
It won't grab anything from CM11, don't worry. These are just the boot partitions which would remain unmodified after installing CM11.

Deleted

PM sent.
Retail N3, up to date firmware.
<Note3>

OP: did you find or get a copy of a debrick img file for the SM-N900V? my retail edition is definitely hard bricked.

trevorcobb said:
OP: did you find or get a copy of a debrick img file for the SM-N900V? my retail edition is definitely hard bricked.
Click to expand...
Click to collapse
Let us know your results from the thread over in the General forum:
http://forum.xda-developers.com/verizon-galaxy-note-3/general/howto-recover-hard-brick-t2834419

bftb0 said:
Let us know your results from the thread over in the General forum:
http://forum.xda-developers.com/verizon-galaxy-note-3/general/howto-recover-hard-brick-t2834419
Click to expand...
Click to collapse
Long time no see old friend.

ryanbg said:
Long time no see old friend.
Click to expand...
Click to collapse
@ryanbg
Sorry for not getting in touch - I know I disappeared as if I had died. Life - and work - intervened to the point of needing to drop something on the floor, and unfortunately that was my XDA involvement. (As it is, even this post is a little bit of hooky). But all is well; I see you are still fighting the good fight. Thanks for your efforts.

Root ANY LG G4 Variant 100% Success Directives | Root Injection | Less Bricks

Hi everyone. As I found out there's root for the G4 but doing this isn't easy especially if your variant is hard to find or has less users. This may result in you waiting for longer than you should. This thread is for those who can take things into their own hands and do it themselves. The tools are available everywhere but I'll give you the best order and steps. I'm using the China LG G4 H818 Dual SIM variant but this method is UNIVERSAL FOR ALL LG G4s.
The process will involve extracting a system image, injecting root and reflashing this image. Most of the steps are effortless and need just copy and paste with keen eyes. Do it slowly. You need an Ubuntu installation for step 2 of this 3-step tutorial. I used universal USB installer and put in on my 8GB USB. Anywhere will do so far as it boots&works. Beware this thread is not dumb-proof but this will not wipe your data or void your warranty if done successfully.
Step 1 -> Getting the proper system image.
Check here and skip to step 3 if you have your rootedsystem.img
>Don't worry because this doesn't require searching. It is from your device. Every device has a system partition and this method will pull it out as an image without root required.
1--Make sure all drivers are installed properly. I'll not be talking about this. We're on XDA not kindergarten.
2--Download the LG_root file or send command file from here and extract it. US Carrier specific check here
3--Put your device in download mode and connect it to your PC.
4--Open(double-click duh) port.bat and make sure to write down the number after com. There maybe different com numbers but choose the com on the DIAG1 line and write down that number. This is important.
5--Hold shift and right-click in any empty space in the extracted folder. Choose open command windows here.
6-- In that copy and paste this
Code:
[FONT=Lucida Console][COLOR=#ff8c00]Send_Command.exe \\.\COM[/COLOR][COLOR=#00ff00][*insert your number here][/COLOR][/FONT]
7--Now you're in send command mode. Nothing looks different on your phone but that's ok. It should just remain in download mode.
8-- On the computer screen in the window you now see #.
9--Now in this post copy the Backup system to internal storage command specific to your device model number. Check in you settings >general >about if in doubt. This is the most important step. Copy the whole line of code. Highlight with your mouse, select everything on the line and copy.
10--You didn't come all this way to fail so do it. Remember it is device model specific.
11-- Paste it in the command window and hit enter. It should take a while so wait until you see#reappear.
12--Now typeLEAVEall in capital letters. Your device will reboot. Check using the file manager if you have a file called system.img in your internal storage. If yes step 2 is next and you did well. If no repeat it and follow the steps properly. Make sure drivers are installed especially windows 10/8/8.1 users. Check device manager
Step 2 -> Root injection.
1--Prepare your Ubuntu USB or virtual machine or computer.
2--Download inject_root zip from here and extract.
3--Copy the system.img from your phone to the extracted inject_root folder on your PC.
4-Reboot into Ubuntu.
5--Here open a terminal.
6--Gain root access on Ubuntu by typing or copy and paste sudo -i
7--You should either be asked for your password which you have to enter or if you used a USB drive like me you'll see the name change to[email protected]
8--Navigate to the inject_root folder by using cd commands. This can also be done by typing cd then [space] then dragging and dropping the folder into the terminal and hitting enter.
9--You'll now see the name in the terminal become longer with the name of the folder in it.
10--Now type chmod +x autoroot.sh
11--Hit enter then sudo ./autoroot.sh
12--If you get any thing like command not recognized or something of the sort use sudo sh autoroot.sh
-That worked for me.
13--If you're successful the name of the file should change from system.img torootedsystem.img
-Please note don't rename the files. Leave them as they are.
14--Now go back to Windows let's finish this.
Step 3 ->Root
1--Transfer the rootedsytem.img to your phones internal storage.
2--Put your phone in download mode and connect it to your PC.
3--Get into send command mode as in step one.
-Put your device in download mode and connect it to your PC.
-Open port.bat and make sure to write down the number after com. There maybe different com numbers but choose the one that has DIAG1 on the same line as it. Note it down this is important.
-Hold shift and right click in any empty space in the extracted folder. Choose open command windows here.
- In that copy and paste this
Send_Command.exe \\.\COM[*insert your number here]
-Now you're in send command mode. Nothing looks different on your phone but it's find. It should just remain in download mode.
4-Now grab your command to flash system.img line of code from this post. It isn't the same as step one. Copy that an paste in the command window. Make sure it is for your device. They are model specific.
5--This should take a while so wait until you see the # again.
6--After thatLEAVEand upon reboot you should have root.
To Un-root just flash a KDZ file compatible with your device here.
Testimonies
Spudnubs said:
Rooted H812 10g for my fellow Canadians. Enjoy!
https://www.androidfilehost.com/?fid=24052804347821979
Click to expand...
Click to collapse
Wildsheep said:
This root method works for my G4 purchased in Singapore (H815 SEA)
Click to expand...
Click to collapse
luongquang said:
Thanks to @hackarchive, H818p10f done with tut.
Click to expand...
Click to collapse
player911 said:
Fantastic. This method will also ease devs for future rooted firmwares. I really cannot see LG being able to patch this, since this is basically a 3rd party LG Flashing tool. If they block this method, then their own tool will ultimately die with it.
Click to expand...
Click to collapse
GavTheStoner said:
Fantastic! I had almost given up hope of root on my EE LG G4. Have just used this method and now rooted perfectly!
hackarchive You rock! Have a thanks!
Click to expand...
Click to collapse
articular said:
everything worked fine and i successfully got my g4 rooted
my variant is H815TR
all steps easy only the ubuntu part was a bit hard especially for a windows user ( finding an ubuntu version and usb install etc. not root injection part)
ty ty ty again )
Click to expand...
Click to collapse
rirozizo said:
if it were for me to decide if we should delete the low effort root method, i'd totally delete it.
"The more 'manual', the better"
Click to expand...
Click to collapse
Moe5508 said:
Only method that roots my device successfully...I updated to 10e of the H815P and using this method (and only this!0 I was able to root my phone...ah felt so good...
The other 1-click rooting methods I came across in other parts of this forum just fail on the G4...
Click to expand...
Click to collapse
Marshmallow and root situation read here
Hit thanks if you appreciate. Hope I helped.
Credits to them whom without this won't be possible :good:
Thecubed
Team Codefire
ManhIT

This is a good method, thanks for writing this up.
I would like to add a few points....
I recommend you do keep your original system.img on your phones regular internal storage. If you encounter any boot issues you can then re-enter download mode and write the original system.img over the top of the failed root attempt. Use the same command from "step 3: root" but replace rootedsystem.img with system.img. This should still be on your phone from step 1 and will recover your phone from a failed root injection attempt. Note that it will not recover your phone if you messed up the dd command and overwrote other partitons. Be sure to use the right dd command and cut n paste to prevent seek/offset typeos.
I also recommend that you keep a backup of your system.img on your pc. When you run autoroot.sh in step 2 the copy on your pc will be renamed and patched. I suggest copying system.img somewhere else first, or re-copy it off your phone.
Additional credits to blog.lvu.kr. This is the blog of the hobbyist who reverse engineered the download mode protocol, created send_command.exe and gave it to the world. Kudos to you.

How is this any easier than the original method....if anything this requires even more work

kyle1867 said:
How is this any easier than the original method....if anything this requires even more work
Click to expand...
Click to collapse
It's for those who have rare variants.

psycho_asylum said:
It's for those who have rare variants.
Click to expand...
Click to collapse
Then you should probably take out the claim that this method is easier from the OP

Can this be used to inject Xposed as well for those of us with locked BLs.

djkinetic said:
Can this be used to inject Xposed as well for those of us with locked BLs.
Click to expand...
Click to collapse
No, we need to wait for a custom recovery.

psycho_asylum said:
No, we need to wait for a custom recovery.
Click to expand...
Click to collapse
Just used flash fire it worked rocking xposed now on 810!

djkinetic said:
Just used flash fire it worked rocking xposed now on 810!
Click to expand...
Click to collapse
Oh nice! I wasn't adventurous enough to try it. I'll make a system backup and give it a whirl!

Very nice thread, thank you. The steps were short, few, and fairly concise.
I was waiting for something like this where I could modify my own image and I wouldn't have to wipe everything or replace it with a new image.
One thing you might want to mention is that if your phone is encrypted, you'll need to unencrypt it first.
Can anyone link me to some instructions on how to disable OTA updates for an unlocked/international H815T?

kyle1867 said:
How is this any easier than the original method....if anything this requires even more work
Click to expand...
Click to collapse
This is what XDA is all about. It tells you how to inject root into your OWN system image. it's the opposite of spoon feeding. it's about teaching members how to do things for themselves. Too many people come here expecting to be spoon fed and have thigns done for them. This thread teaches people how to do their own work, while learning something at the same time.
Good work OP! :good:

the_scotsman said:
This is what XDA is all about. It tells you how to inject root into your OWN system image. it's the opposite of spoon feeding. it's about teaching members how to do things for themselves. Too many people come here expecting to be spoon fed and have thigns done for them. This thread teaches people how to do their own work, while learning something at the same time.
Good work OP! :good:
Click to expand...
Click to collapse
Thanks. I guess people don't know what XDA is about. Seeing noobs and others trying to spit on hard work when I used my time and device as Guinea pig. Also people don't know this is almost brick-proof because the system image if from their devices. Unless they use wrong commands but all here is just copy and paste. They see lot's of text and get cold feet. Anyways will be updating the OP with system images. If yours is available please share. If you see your image available and you have drivers and LG_root downloaded proceed to step 3.

The only downside is that I have to drag out my windows laptop instead of doing everything on the ubuntu machine I use at work.
But if that's the biggest of my problems then I don't really have a problem

hi, thx for this tutorial, looks good
when flashing back the rooted img,does it wipe everything ? apps, data ... etc
thx
EDIT: just correct me if im wrong
using this method WILL NOT wipe everything on my device cause im rooting my system with everything on it
correct ???
must make sure before i go ahead
thx

How to calculator extractly bs/seek/count ?

Is there a possibility of any personal data being written to /system on a phone during normal use? I can provide 10c Optus AU (carrier 505-02) if I can be sure its not identifying, but ive been using the phone a couple of weeks.
Download link:
https://www.androidfilehost.com/?fid=24052804347799013

optiplex2012 said:
using this method WILL NOT wipe everything on my device cause im rooting my system with everything on it
correct ???
Click to expand...
Click to collapse
correct.
---------- Post added at 06:01 PM ---------- Previous post was at 05:29 PM ----------
djkinetic said:
Can this be used to inject Xposed as well for those of us with locked BLs.
Click to expand...
Click to collapse
HTCuser90 said:
How to calculator extractly bs/seek/count ?
Click to expand...
Click to collapse
I would also like to know this. You can resolve system by running the following. Note that this is for the H815T and is not the same on all variants.
# ls -lZ /dev/block/bootdevice/by-name/system
You'll get something like:
lrwxrwxrwx root root ubject_r:block_device:s0 system -> /dev/block/mmcblk0p47
Which tells you the actual block device (partition its on).
And you can see the size of that with:
# cat /proc/partitions
where you see:
major minor #blocks name
<snip>
259 15 4239360 mmcblk0p47
<snip>
However I dont know how to identify how large a block is or how to calculate the start offset in the main partition.

ok, it worked great
wasnt easy, since im not so familiar with using ubuntu, but all is ok
the explanation of the how to... was great and nothing lost
my H815L is now rooted
thx guys

djkinetic said:
Just used flash fire it worked rocking xposed now on 810!
Click to expand...
Click to collapse
I know it's kind of going off topic, but I figured I'd mention that Flash Fire doesn't work on VS986. It just goes to a black screen and sits there forever. I left it sit for almost an hour. I saw elsewhere it has something to do with automount, I'll have to mess with it further.

hackarchive said:
Hit thanks if you appreciate. I spent hours trying to root so hope I helped.
Click to expand...
Click to collapse
Appreciated but you should include a way to unroot (undo) as well, ie how do we get back to stock (if required) ?

[Q]Flashing bootlogo MXPE 6.0 Custom Rom Custom Kernel

Is there a flashing bootlogo for MXPE 6.0 Custom Rom & Custom Kernel guide?
Screenshot below as to what I am running on my my phone. I am specically looking to replace the unlock bootloader warning bootlogo with something nice.
About Phone:

Hitti2 said:
Is there a flashing bootlogo for MXPE 6.0 Custom Rom & Custom Kernel guide?
Screenshot below as to what I am running on my my phone. I am specically looking to replace the unlock bootloader warning bootlogo with something nice.
About Phone:
Click to expand...
Click to collapse
This thread has what you need to get rid of the unlocked bootloader warning. Make sure you read carefully and get the marshmallow logo for your rom.
Here's a kernel tuning guide.

jason2678 said:
This thread has what you need to get rid of the unlocked bootloader warning. Make sure you read carefully and get the marshmallow logo for your rom.
Here's a kernel tuning guide.
Click to expand...
Click to collapse
It says its for
LPH23.116-18
Mine is

Hitti2 said:
It says its for
LPH23.116-18
Mine is
Click to expand...
Click to collapse
The one attached to the OP is for lollipop. You need the marshmallow one that Spasticdroid posted about a dozen pages in.

Gotya.
As if you hadnt known,I am new at this.
What can I use to get the location for the logo after downloading.
Is there like a copy url in es file explorer?
Then I can paste then write it down on paper.

Hitti2 said:
Gotya.
As if you hadnt known,I am new at this.
What can I use to get the location for the logo after downloading.
Is there like a copy url in es file explorer?
Then I can paste then write it down on paper.
Click to expand...
Click to collapse
The easiest thing to do would be to download it to a computer, unzip it, and use fastboot to flash logo.bin with the command in the OP of the logo thread.
Alternately you could probably use dd to flash it if you don't have access to a PC or just don't want to use one. I have not tested and would not recommend that.
Fastboot worked fine. It is far too easy to make a typo and trash your phone with dd; it isn't nicknamed disk destroyer for no reason. Assuming you download it to the default folder, unzip it there with a utility like es file explorer, and are the primary user of this device the command would look like this:
Code:
su
dd if=/data/media/0/Download/logo.bin of=/dev/block/mmcblk0p31
If you do go this route and get a command not found for dd, then you probably need to install busybox. Triple check all your inputs if you do this. Typos with dd can be nasty. I've modded plenty of devices this way, but just use fastboot when it is available. The syntax is easier with fastboot, and you don't have to worry about writing to the wrong block device since it handles them all by name.

Thanks a bunch. Be fire i proceed
Is there a way to backup the unlocked bootloader logo?
So if I ever need to replace it back.
Perferrably through fastboot. I've got a pc ready for adb and fastboot.

Hitti2 said:
Is there a way to backup the unlocked bootloader logo?
Click to expand...
Click to collapse
Essentially just reverse the arguments in the command I posted above.
Code:
su
dd if=/dev/block/mmcblk0p31 of=/data/media/0/Download/logo.img
That should leave you with an image of the logo partition in your /sdcard/Download folder.

jason2678 said:
Essentially just reverse the arguments in the command I posted above.
Code:
su
dd if=/dev/block/mmcblk0p31 of=/data/media/0/Download/logo.img
That should leave you with an image of the logo partition in your /sdcard/Download folder.
Click to expand...
Click to collapse
Do I have to use dd to backup the logo? Is there a cmd in fastboot or adb?
Thnx.

Hitti2 said:
Do I have to use dd to backup the logo? Is there a cmd in fastboot or adb?
Thnx.
Click to expand...
Click to collapse
You could use adb shell, but that just lets you use your computer keyboard instead of trying to type in a terminal app. The command to get a single partition remains the same.
There is an app called partitions backup & restore that can handle this without any command line use. Its available on the play store.

jason2678 said:
You could use adb shell, but that just lets you use your computer keyboard instead of trying to type in a terminal app. The command to get a single partition remains the same.
There is an app called partitions backup & restore that can handle this without any command line use. Its available on the play store.
Click to expand...
Click to collapse
Yea, I don't think I can use dd.
http://www.noah.org/wiki/Dd_-_Destroyer_of_Disks#Why_use_dd_instead_of_cp.3F
For linux. I am on a WIn7x64 computer.
And for Partitions Backup & Restore
one comment
Bricked. So it kinda works. It did keep my phone's efs/imei info. But upon reinstalling by phone was stuck in bootloop. I had to set my phone back to Android 4.0 which means some newer apps do not not work. & trying to reinstall different/newer android ROM is now impossible. I was barely able to get it back to working condition, but now slower than before. Unless you know how to reprogram the partitions, i would not mess with this app.
Click to expand...
Click to collapse
I think Ima leave the bootlogo alone.

Hitti2 said:
Yea, I don't think I can use dd.
http://www.noah.org/wiki/Dd_-_Destroyer_of_Disks#Why_use_dd_instead_of_cp.3F
For linux. I am on a WIn7x64 computer.
Click to expand...
Click to collapse
You're correct, dd is part of GNU coreutils, but you'll be able to use it even if you use adb shell from a windows computer. The dd binary resides on your phone (which is pretty much a linux environment, just android/linux instead of GNU/linux), not on the computer.
I don't think dd is there by default in a typical stock rom, but busybox adds the utilities stock android leaves out. I'm using busybox on rails from the play store with this phone.
I've been using linux for about 15 years, so have a comfortable, if uneasy, feeling for using dd. It is a powerful tool, but it is not fault tolerant and you usually have to run it as root to get the job done. Make a little typo or have an absent minded moment and reverse the if and of arguments and you can have a really bad day.

How can we dump the img we need?

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?