Related
I just bought ASUS Memo Pad 7 (ME572C)
but I can't find root message for google
It android kitkat 4.4.2
please help me~
thanks
woff said:
I just bought ASUS Memo Pad 7 (ME572C)
but I can't find root message for google
It android kitkat 4.4.2
please help me~
thanks
Click to expand...
Click to collapse
You're gonna have to wait for a while. It hasn't yet reached general availability. Currently I can only find it for sale on John Lewis in the UK. And they brag about it being exclusive to them.
I just got it at Best Buy, so they're out and available and just waiting to be rooted...
Im also thinking of getting this new Asus Memo 7. Is this new intel chipset rootable?
I just found this for it.
http://www.xxxxxxxxxxxxxxxxxxxxx
Don't know if it's real or not.
Moderator Edit: No it isn't - now obfuscated.
I am also the happy owner of an ASUS Memo Pad 7 (ME572C).
Before this one I had the Nexus 7 (2012), a great tablet. But it broke and I bought the ME572C, which is a kind of up upgraded nexus.
Also waiting for a way to root it, to use all the possibilities of this quick processor.
The link in the mesagge before looks like spam to me.
Anybody any idea when someone will find the way to root it??
I just got an Asus ME572C, I wanted the Nexus 7 (2013) but it was not in stock. And I have to say, that despite is not Google stock, this tablet is a kick ass device.
So I hope and it would be nice, to add a forum for this great tablet and see some development. I think is a great device to work on.
I dont have much time but I will try to do some stuff with It. O if someone do something and want people to test it. Here I'm
I search a way to root this beautiful tablet..... the processor 64 bits is the thing which is difficult to root ?
I'm surprise that dolphin don't run on.
found this, but I haven't try anything yet
Some information [MeMOPad] ME572C of
Talk about the boring part:
Intel Z3560 / Z3580's CPU, boot.img / fastboot.img / recovery.img of HEAD_PADDING back UNKNOWN_SIZE is 728 bytes, but BOOTSTUBSTACK_SIZE is 8192 bytes.
RootZenFone change it to use, and then release a small update late.
Inside sideload recovery is bad, adb port can not open, when to get there to do a software update or not repaired, guess should not want people to use it? fastboot there SD Download, it seems the future of factory image will be .raw format.
The more interesting part:
fastboot there is a small back door, can be used to do the root of the application:
fastboot oem mount <partition> <fs type>
The first instruction is to mount partitions on the phone, will be mounted at / mnt / <partition> data folder, so I'm going to mount the system is ext4 fastboot oem Mount system , that is, you want to mount userdata fastboot oem mount data ext4 can.
fastboot flash <path_to_phone> <path_on_local>
The second instruction is to update the information on the phone route, originally only update existing files , but here I do not know why is modified to replace the existing file or upload , it is very interesting, root application ready. Because it is 4.4 and there is open SELinux, so the best way to modify the existing shell file will be executed, when it related to root after the brush into the program to reboot automatically go into.
The idea is simple:
fastboot oem Mount system ext4
fastboot Flash / mnt / system / xbin / su su
Flash /mnt/system/etc/install-recovery.sh install-recovery.sh fastboot
fastboot Flash /mnt/system/Superuser.apk Superuser.apk
Then find a .sh file can be used to modify the plug plug back in the boot judgment if no /system/etc/.installed_su_daemon run the installation program, produced /system/bin/.ext/ , / system / bin /. ext / su , / system / xbin / sugote , / system / xbin / sugote-mksh , / system / xbin / daemonsu ...
Packaged on a free, self-interested hands.
-----------------------------------------------------------
gabriel-arg said:
found this, but I haven't try anything yet
Some information [MeMOPad] ME572C of
Talk about the boring part:
Intel Z3560 / Z3580's CPU, boot.img / fastboot.img / recovery.img of HEAD_PADDING back UNKNOWN_SIZE is 728 bytes, but BOOTSTUBSTACK_SIZE is 8192 bytes.
RootZenFone change it to use, and then release a small update late.
Inside sideload recovery is bad, adb port can not open, when to get there to do a software update or not repaired, guess should not want people to use it? fastboot there SD Download, it seems the future of factory image will be .raw format.
The more interesting part:
fastboot there is a small back door, can be used to do the root of the application:
fastboot oem mount <partition> <fs type>
The first instruction is to mount partitions on the phone, will be mounted at / mnt / <partition> data folder, so I'm going to mount the system is ext4 fastboot oem Mount system , that is, you want to mount userdata fastboot oem mount data ext4 can.
fastboot flash <path_to_phone> <path_on_local>
The second instruction is to update the information on the phone route, originally only update existing files , but here I do not know why is modified to replace the existing file or upload , it is very interesting, root application ready. Because it is 4.4 and there is open SELinux, so the best way to modify the existing shell file will be executed, when it related to root after the brush into the program to reboot automatically go into.
The idea is simple:
fastboot oem Mount system ext4
fastboot Flash / mnt / system / xbin / su su
Flash /mnt/system/etc/install-recovery.sh install-recovery.sh fastboot
fastboot Flash /mnt/system/Superuser.apk Superuser.apk
Then find a .sh file can be used to modify the plug plug back in the boot judgment if no /system/etc/.installed_su_daemon run the installation program, produced /system/bin/.ext/ , / system / bin /. ext / su , / system / xbin / sugote , / system / xbin / sugote-mksh , / system / xbin / daemonsu ...
Packaged on a free, self-interested hands.
-----------------------------------------------------------
Click to expand...
Click to collapse
thank you
I try it !
woff said:
thank you
I try it !
Click to expand...
Click to collapse
Please send some feedback about how it did go!!
---------- Post added at 06:33 PM ---------- Previous post was at 06:25 PM ----------
and have someone tried NFC on this tablet?
according to all web sites it has NFC, but I cant find any setting about NFC on the tablet.
Did anyone try rooting this device with the rooting tool of Asus Zenfone 5? I think I may work. Currently I don't have this device. I will buy it the next 2 days.
I tried the asus zefone 5 root apk but it says that is only for zenfone....
Root) http://23pin.logdown.com/posts/230216-root-rootzenfone-14r
http://www.asuszenfoneblog.com/2014/10/download-rootzenfone-1464r-apk.html
Thanks a lot it works great
How does this work? Just download and install the apk?
Hello scritchs,
Good to hear it worked for you.
Wondering if it will also work for me...
You just downloaded the RootZenFone 1.4.6.6r, installed the apk and it is rooted now?
I like to know if ours ME572C have the same specs:
Modelnumber K007
Buildnr KVT49L.WW etc
Android 4.4.2
thanks
thanks a lot
I try it~
woff said:
thanks a lot
I try it~
Click to expand...
Click to collapse
Yes i get the apk and its automatic the tab reboot and the root is on.....
This tab is great.... nothing to say
---------- Post added at 09:25 AM ---------- Previous post was at 09:17 AM ----------
I get the apk from the first link 1.4.6.r.6 from asus webstorage all works fine. Thanks again
How about a custom rom to remove the asus bloatware and return to the pure stock android?
@MikeChannon removed OP. please close
what? lol
hi ionioni,
many thanks for your tool. I could successfully create a signed bios file. During the flashing process, i believe, it shows no errors. But after a automatically reboot just the teclast logo appears.
I did a "RESTORE DEFAULT" and "SAVE AND RESET" but when i try to flash android with the mirek tool, it shows the same error message (get_path:344...) .
Do you have any suggestions what i can try to restore a working state?
Thank you.
the_dude_84 said:
During the flashing process, i believe, it shows no errors. But after a automatically reboot just the teclast logo appears
Click to expand...
Click to collapse
at the end of the bios flashing, before the reboot, did you received a "RESTORE COMPLETED! Rebooting the tab to load new BIOS!" message? if not, what messages you got when flashing? what are the steps you are doing? more details ... this tool job is to write a (user provided) bios file, not fixing specific stuff (other) on your tab
later edit: the error 'get_path:344' is normal to be shown. the x98 bootloader (efilinux file) will at first try to get a handle for the device (disk) it was started from, but when it is run directly from the bios, ie dnx mode (normally it loads/executes from his EFI partition on mmc) the call returns no handle (as it should) and this is causing the message. is a normal message if starting from dnx, what is not normal, is if after that the bootloader won't be able to load and execute the kernel from the passed boot image.
the tablet just restarts without such a message you named. I used my prevously saves bios with your tool and flash it. What steps i can do to convince the tablet to start the kernel?
Did you repair the saved BIOS before flash by this new tool?
You have to change from FE FE at 400Dh and 400Eh address to FF FF with a hex editor!
updated OP with v2 of the tool as it seems these x98 tabs are not having the most conforming EFI firmware in the bios (it 'forgets' the consistent mapped device so i hard-coded it in the tool, it would have map to the same path anyways as it is a consistent /virtual/ disk that is used as environment during the flashing, so this 'patch' just helps the non-conforming devices /such as x98 so far/ not limits)
blackbile said:
Did you repair the saved BIOS before flash by this new tool?
You have to change from FE FE at 400Dh and 400Eh address to FF FF with a hex editor!
Click to expand...
Click to collapse
do you know what those two bytes are about? can anyone say that he bricked his tab by flashing a FE FE bios? (i have flashed my bios back dozen times so far on my Lenovo and did not knew about this until read someplace on these posts so i checked my backup bios file and sure thing it did have the FE FE inside at that offset... i guess is something wrong with my tab since it did not bricked )
joke aside, i cannot say whether this IS or IS NOT true, but what i can say is that there were two users i assisted in flashing back their bios backup (on x98 models) and both had FE FE at that offset and they did NOT BRICKED ( @florent.m was on ant the other don't recall)... i wish i knew more about WHY this needs to be done, not just YOU MUST instructions... what i know is that area belongs to the nvram of TXE region (is the EFFSOSID partition of it) but since Intel takes care that no one has access to TXE related info i sure would be interested in someone saying what those two bytes are accounted for (and more of course)...
again someone who has a flash programmer can check easily and safely (i have but as i said i cannot hard-brick it )
I'm still not able to flash. I get this error message upon running fastboot boot image_name.img
Code:
INVALID size (7586586 bytes) for pushed package! This tool will only accept a (md5) BIOS file for input. You MUST run md5add.exe on your BIOS file and push the file it produces.
ABORTING
I did run md5add on the img and I did run fastboot boot on the image it produced (16 bytes larger than the original). What am I doing wrong?
BTW, by pushing does it mean that I have to run anything else besides those 2 commands on fastboot?
andrepd said:
I'm still not able to flash. I get this error message upon running fastboot boot image_name.img
Code:
INVALID size (7586586 bytes) for pushed package! This tool will only accept a (md5) BIOS file for input. You MUST run md5add.exe on your BIOS file and push the file it produces.
ABORTING
I did run md5add on the img and I did run fastboot boot on the image it produced (16 bytes larger than the original). What am I doing wrong?
BTW, by pushing does it mean that I have to run anything else besides those 2 commands on fastboot?
Click to expand...
Click to collapse
read the op again !!! and do exactly the steps detailed there!!! you need to use YOUR signed bios file generated with md5add ... instead you are WRONGLY!!! using some boot image file (luckily for you there is a size check too, otherwise you would have been flashing a kernel on your bios chip, oh boy...)
again:
the first instruction pushes the bios efi flasher tool
the second one pushes YOUR bios (signed) file that you want to flash on your bios chip. to make sure that the bios file that is wrote by the tool is not altered during the transfer i added the extra md5 signing step, so before it will start the effective flashing the efi tool will check the bios file received against the md5 signature appended (this step is normally not needed, but on some PC could be that the usb transfer misbehaves)
Thanks a lot for your efforts and help!!!
ionioni said:
read the op again !!! and do exactly the steps detailed there!!! you need to use YOUR signed bios file generated with md5add ... instead you are WRONGLY!!! using some boot image file (luckily for you there is a size check too, otherwise you would have been flashing a kernel on your bios chip, oh boy...)
again:
the first instruction pushes the bios efi flasher tool
the second one pushes YOUR bios (signed) file that you want to flash on your bios chip. to make sure that the bios file that is wrote by the tool is not altered during the transfer i added the extra md5 signing step, so before it will start the effective flashing the efi tool will check the bios file received against the md5 signature appended (this step is normally not needed, but on some PC could be that the usb transfer misbehaves)
Click to expand...
Click to collapse
But the image I'm flashing isn't even 7586586 bytes... I'm flashing with this tool as per this post http://forum.xda-developers.com/showpost.php?p=64854157&postcount=26 (img in the OP of that thread)
Sorry I'm a bit confused... Is that boot image the wrong one to flash then?
Thank you very much!
I think it worked and is waiting for input or is even done already, but I'm quite cautious now, so I don't want to press anything yet
It says:
FPT operation passed
_
Click to expand...
Click to collapse
In the flash.bat from another tool (TTT-Update the BIOS on your X98 Air II/3G to the latest dual boot version) it should write that status to a log file and continue with either flash passed or failed, but apparently it doesn't continue automatically in my case.
Hope anyone knows if it is safe to do anything. I've pressed the power button shortly as a confirmation command, but that doesn't do anything.
andrepd said:
But the image I'm flashing isn't even 7586586 bytes... I'm flashing with this tool as per this post http://forum.xda-developers.com/showpost.php?p=64854157&postcount=26 (img in the OP of that thread)
Sorry I'm a bit confused... Is that boot image the wrong one to flash then?
Click to expand...
Click to collapse
This is a DIFFERENT tool! that one you are refering to already has a BIOS file in it...
This one flashes a bios file YOU MUST provide!
Bolsnerk said:
Thank you very much!
I think it worked and is waiting for input or is even done already, but I'm quite cautious now, so I don't want to press anything yet
It says:
In the flash.bat from another tool (TTT-Update the BIOS on your X98 Air II/3G to the latest dual boot version) it should write that status to a log file and continue with either flash passed or failed, but apparently it doesn't continue automatically in my case.
Hope anyone knows if it is safe to do anything. I've pressed the power button shortly as a confirmation command, but that doesn't do anything.
Click to expand...
Click to collapse
As said on some x98 devices (having a specific bios?) it seems that after the bios is flashed 100% it hangs... not so much you can do but force a power off/reboot ... you should be fine
ionioni said:
This is a DIFFERENT tool! that one you are refering to already has a BIOS file in it...
This one flashes a bios file YOU MUST provide!
Click to expand...
Click to collapse
Okay, I got it working, phew, I was being a total noob and confusing everything. I took the dual boot BIOS, added the md5 hash with the tool you provided and flashed it with your tool. Everything went well. Thank you for your work and sorry for being a total moron
andrepd said:
Okay, I got it working, phew, I was being a total noob and confusing everything. I took the dual boot BIOS, added the md5 hash with the tool you provided and flashed it with your tool. Everything went well. Thank you for your work and sorry for being a total moron
Click to expand...
Click to collapse
Excellent!
ionioni said:
do you know what those two bytes are about? can anyone say that he bricked his tab by flashing a FE FE bios? (i have flashed my bios back dozen times so far on my Lenovo and did not knew about this until read someplace on these posts so i checked my backup bios file and sure thing it did have the FE FE inside at that offset... i guess is something wrong with my tab since it did not bricked )
joke aside, i cannot say whether this IS or IS NOT true, but what i can say is that there were two users i assisted in flashing back their bios backup (on x98 models) and both had FE FE at that offset and they did NOT BRICKED ( @florent.m was on ant the other don't recall)... i wish i knew more about WHY this needs to be done, not just YOU MUST instructions... what i know is that area belongs to the nvram of TXE region (is the EFFSOSID partition of it) but since Intel takes care that no one has access to TXE related info i sure would be interested in someone saying what those two bytes are accounted for (and more of course)...
again someone who has a flash programmer can check easily and safely (i have but as i said i cannot hard-brick it )
Click to expand...
Click to collapse
IonIoni,
All,
1st - thanks again for your tool, it saved my tablet (teclast C5J8)
2nd - yes the boot file I provided to Ionioni was untouched, a direct copy of the bios as dumped by mirek backup tool, and up to now, everything is working fine, either on android, or on Windows 10.
and when I say everything fine......I want to say as before..........the GPS is still not working (((((((
thanks a lot,
Cheers,
Florent
Holy moley, the last 24 hours have been intense, that is how old my x98 air iii is, and I have read over a thousand pages here on XDA in that time, i've also managed to soft brick it trying to flash a dual boot bios as per Techknights/Techtablets guides, not sure why or where exactly things went bad, now i'm stuck in a boot loop, red Chinese symbols with a tiny arrow beside it, but reading this gives me some hope, no idea how to follow the simple instructions above when you say..
" IMPORTANT: run the md5add tool on your bios file md5add.exe your_bios_file your_signed_bios_file. "
tried a few things and got nowhere, I tried to open the bios file that you said to place in the same folder as the other two files, with the md5add tool and a small window flashed on screen for a millisecond then disappeared, that's all no file was produced lol
Also not sure what this part means too..
"start in dnx mode and input:
fastboot flash osloader bios_flasher.efi.."
I can get into dnx mode ok but thats all how do I input anything?
My head is fried but I will stay up and try again, it's 5am (Ireland)
Am I missing an elephant in the room? like some other software the everyone else has already installed except noobs like me?
pilot error said:
Holy moley, the last 24 hours have been intense, that is how old my x98 air iii is, and I have read over a thousand pages here on XDA in that time, i've also managed to soft brick it trying to flash a dual boot bios as per Techknights/Techtablets guides, not sure why or where exactly things went bad, now i'm stuck in a boot loop, red Chinese symbols with a tiny arrow beside it, but reading this gives me some hope, no idea how to follow the simple instructions above when you say..
" IMPORTANT: run the md5add tool on your bios file md5add.exe your_bios_file your_signed_bios_file. "
tried a few things and got nowhere, I tried to open the bios file that you said to place in the same folder as the other two files, with the md5add tool and a small window flashed on screen for a millisecond then disappeared, that's all no file was produced lol
Also not sure what this part means too..
"start in dnx mode and input:
fastboot flash osloader bios_flasher.efi.."
I can get into dnx mode ok but thats all how do I input anything?
My head is fried but I will stay up and try again, it's 5am (Ireland)
Am I missing an elephant in the room? like some other software the everyone else has already installed except noobs like me?
Click to expand...
Click to collapse
i wonder how could the instructions in this op be more simple...
you must:
1. find a BIOS file for you model, make sure it is the CORRECT one or you might hard-brick when you flash it
2. sign the file using the md5add tool, this will create a new file, the signed bios file
3. start in dnx mode and load the efi bios flasher tool and then you bios signed file (the steps are in the op)
ionioni said:
i wonder how could the instructions in this op be more simple...
you must:
1. find a BIOS file for you model, make sure it is the CORRECT one or you might hard-brick when you flash it
2. sign the file using the md5add tool, this will create a new file, the signed bios file
3. start in dnx mode and load the efi bios flasher tool and then you bios signed file (the steps are in the op)
Click to expand...
Click to collapse
You know what ionioni, they may be simple to you, but this is my FIRST android tab, its only two days old and it's soft bricked on the very first try at bios flashing from following equally simple instructions from techtablets, flashing new bios from within android using update ifwi.apk, I did exactly that chose the 2.02 dual boot bios that everyone else used, copied it to internal storage and pressed the button.
That is all I did to ruin this tablet lol
What techtablets did NOT mention is he was already rooted on mirek190 v6, that is why my tab is softbricked, not because I chose the wrong files.
No idea how to do this step.. "sign the file using the md5add tool", when i search about it, the only results are back in here?
Can you point me in the right direction to learn about md5add?
Thnk you..
pilot error said:
You know what ionioni, they may be simple to you, but this is my FIRST android tab, its only two days old and it's soft bricked on the very first try at bios flashing from following equally simple instructions from techtablets, flashing new bios from within android using update ifwi.apk, I did exactly that chose the 2.02 dual boot bios that everyone else used, copied it to internal storage and pressed the button.
That is all I did to ruin this tablet lol
What techtablets did NOT mention is he was already rooted on mirek190 v6, that is why my tab is softbricked, not because I chose the wrong files.
No idea how to do this step.. "sign the file using the md5add tool", when i search about it, the only results are back in here?
Can you point me in the right direction to learn about md5add?
Thnk you..
Click to expand...
Click to collapse
i give you the tools and the how-to use them...
again, you need to do this:
1. FIND a bios file for your tab model, ask around and some other owner can point you at it, but take care as this is the file that will be programmed in your tablet so if it is not good you will HARD-BRICK (ask ten times before using it once)
2. after you have found the file, use the md5add tool to sign, if for eg the file is named some_bios_file.bin you can input at a command prompt:
md5add.exe some_bios_file.bin signed_bios.bin (the signed_bios.bin file will be generated)
3. start your tab in dnx mode and input:
fastboot flash osloader bios_flasher.efi
fastboot boot signed_bios.bin and this will start the flashing process... messages will be shown on your tab screen while progressing...
the md5add.exe and bios_flasher.efi files can be found in the attachment to the first post (op)
the bios file is your responsibility to find
when done if the bios file you used is correct you should be able to use again the tab (ie no more bootloop)
i must repeat: be careful what bios file you use, if it's a wrong one you can HARD-BRICK! ask around for that...
Hi. I've an unbranded chinese Headunit . With a rockchip px3 and i want to root it . i've folllow step . but now i've an issue . i need to instal supersu trought the recovery but the head unit dont have volume button . i've been able to reboot recovery trought window adb but no command window . only a dead Android with an exclamation .
Is there any body who has aldrealy root a px3 ?
Thx
How did you get Root? I have a chinese Headunit with px3 too.
Thx
Yes ! I've instal kingroot . and it did some magic
Another way is to get an update.img and root the image. That's what I did for pumpkin audio's Lollipop unit
uudruid74 said:
Another way is to get an update.img and root the image. That's what I did for pumpkin audio's Lollipop unit
Click to expand...
Click to collapse
Can you please explain in details how to get an update.img and root the image
Thanks
The images are on the pumpkin forums and in my case, I had a bunch of problems for which they kept saying "download this update and flash it and see if it works" ... and it didn't. So, I looked at it myself.
The images are in a format that is specific to Rockchip. You'll likely need a Linux box and some decent skill to manipulate the images. You unpack the image with 'imgrepackerrk' available on XDA. It makes a folder called update.IMG.dump and inside is things like update-script (I comment out the part that flashes recovery! I'm scared) and a folder called Image. Inside that are your partition images, including system.img!
You can just make a folder and mount that image to it. Then grab a copy of SuperSU and open it. You'll see it runs a shell script to manipulate the /system folder. I manually performed the commands at the Linux command line. However, you MUST know shell scripting. This isn't a simple file. Expect to screw it up a dozen times before you get all the permissions just right.
When done, unmount your image from the folder, repack using the same tool that packed it and stick it on a USB flash drive and take it out to the car. Do the magic dance to get to the recovery, and flash it.
Do not attempt if you can't get to recovery and make sure you comment out the part that flashes recovery since you don't EVER want to lose that recovery. It's your only way into the system if you mess up!
If you have the exact same model as me I can stick mine up somewhere, although its tricky to get the Settings changes working since I haven't re-signed the system apps ... basically, you load with the stock Settings app and then use root to copy my version in place. My version gives a 12 and 24 hr standby time options. Once copied, its good.
Sent from my ONEPLUS A3000 using Tapatalk
Is there any way to create a debrick.img from a downloadable stock rom? (Sammobile). I know you can create a debrick.img from a working phone, but I want to know if it's possible to do it from the rom itself (with hopefully Windows).
I *think* I may have figured this out. My phone might need a USB Jig and maybe that's why it's still not working for me, but if someone else with a bricked phone wants to test this, please let me know your results. Here is how you can create a debrick.img from the stock ROM.
1) Download and install 7-Zip: https://sourceforge.net/projects/sevenzip/
2) Download and install OSFMount: http://www.osforensics.com/tools/mount-disk-images.html
3) Download your stock ROM (if you haven't already). For example, here is mine for the SGH-I257M (I257MVLUAMK5): http://www.sammobile.com/firmwares/database/SGH-I257M/FMC/
4) Download a debrick.img (I suppose any kind will do; like one of these: https://drive.google.com/folderview?id=0B612qYHFMILfWUlMTTEwdUstcXM&usp=sharing)
5) Unzip contents of stock ROM download
6) You will see a .tar.md5 file (mine is I257MVLUAMK5_I257MOYAAMK5_I257MVLUAMK5_HOME.tar.md5)
7) Right click on this file and go to 7-Zip > Open Archive (you might get an error like I did; ignore it)
8) In my file, I saw something called NON-HLOS.bin. I dragged it out of Z-Zip onto my desktop to extract it.
9) Right click on NON-HLOS.bin and go to 7-Zip > Open Archive.
10) You will see a folder called "image." I dragged and dropped this onto my desktop as well.
11) Open OSFMount and click on "Mount new..." and choose the "..." button to choose your debrick.img file.
12) In my debrick.img file, I chose Partition 0 which has 60 MB and says (FAT 12).
13) All the default settings seem fine, but the only thing I changed was unchecking "Read-only drive" near the bottom. Then I clicked OK.
14) Now you will see your drive mounted. Double click on it and you will see a new window pop up with the folder "image."
15) Replace this image folder with your image folder that you saved to your desktop in step 10. Then close the window.
16) Click "Dismount all & Exit."
You're done! Now follow these instructions on how to burn the debrick.img file to a microSD card load onto your phone: http://forum.xda-developers.com/showthread.php?t=2660566
Since I use Windows (Windows 8.1 to be exact), I used win32diskimager-v0.9-binary.zip to burn to my microSD card. I double checked to see if the partitions were there by opening it with MiniTool.
Please, if someone could tell me whether or not this works for them, let me know!
Hello,
thank you very much for your effort! I built one and - Yeah the first try did not seem to work. After the try I wanted to be safe that battery is fully charged, so i plugged it. After a while I saw something on the screen! It might have booted automatically.
Now there are a few lines:
BOOT RECOVERY MODE
Check Boot Partitions..
Copy from T-Flash..
BOOT RECOVERY..
Write 139008 Sectors..
FLASH WRITE FAILURE
ddi: mmc read failed
ODIN MODE
Product Name: GT-I9195
Current Binary: Samsung Official
System Status: Custom
KNOX Kernel Lock: 0x0
KNOX Warranty Lock: 0x0
CSB-Config-LSB: 0x30
BOOTLOADER AP SWAEV: 2
WRITE PROTECTION: Enable
Yeah I think I can now flash with ODIN
Thank you for this post, it might also help others to build their own debrick.img
I will now resume with resurrection
*UPDATE*
Unfortunately I did not succeed in flashing the phone. I think the emmc-Chip has died
First time I flashed, I got an error that there was no PIT.
Then I added one and said "re-partition" in ODIN.
It now found the PIT but failed. On the phone there was written a new line in red:
PIT Fail: Total sectors (0)
Well, I do not think I can do anything more. Or do you have any ideas what I could try in addition?
If not then RIP my beloved S4 Mini.
But this has nothing to do with the topic. The method described to create a debrick out of a stock rom is possible and it was successful.
That's funny that you mention it's an S4 mini. I know I posted in the S6 section about this, but only because I was trying to post where there seems to be (possibly) more traffic. And I figured that it's pretty general because it's about creating a debrick.img and not necessarily about debricking a specific phone.
Nobody was answering any of my questions on the other subsections. I also have an S4 mini that I'm trying to debrick. It's the SGH-I257M. I wasn't sure if my debrick.img wasn't working because I tried on a 2GB card and then a 64GB card (both class 10). So I borrowed a 16GB card (class 10), and still nothing is happening. So I'm just leaving it plugged in (like you said). We'll see what happens!
I wondering if there is a problem with the S4 minis dying. It's a friend's phone and he said it kept randomly shutting off. Then one day it just wouldn't turn back on. Maybe it's the battery. Who knows.
upload debrick.img shv e110s please
Samsung SM-G910S HArd Bricked
my samsung SM-G910S no download mode no recovery no bootup.. can anybody plz give me the unbricked debricked img..... From many munths i have been surching about that issue but i dont got success about to clear this issue... dont you people have Samsung SM-G910s in the Word..? becuz i googled about this model but every where in the world that bloody file dont have to any body... hay guyz help if you can... :crying:
how does this worn if you haven`t a stock rom on your dead phone (i9195) but a custom lineage-14.1 ?
anyone said:
how does this worn if you haven`t a stock rom on your dead phone (i9195) but a custom lineage-14.1 ?
Click to expand...
Click to collapse
did anyone edit my post?
I had a custom rom lineage-14.1 on it before it suddenly died.
Now following just appear after using a i9195 debrick.img which I found on the forum
" boot recovery mode
check boot partitions. .
copy from t-flash. ."
But I`m still not able to start the download mode for odin
need a debrick image
will this work if the phone rom is not the stock i mean that i flash a coustm rom then the phone bircked if i use a stock debrick img will it work or i must use a another img base on the rom i flashed
Hello,
i wants to root my Amazon Fire 7 Gen 9 with the instructions in this Thread (Fire 7 (2019, mustang) unbrick, downgrade, unlock & root).
https://forum.xda-developers.com/am...ire-7-2019-mustang-unbrick-downgrade-t3944365
With Linux Live USB-Stick and Ubuntu.
My problem is, that i cant find the files which i copy (for example with following command: "adb push Magisk-v19.3.zip /sdcard") to the sdcard a second time.
What i have done:
At first i root the fire 7 (i think) like it is explain in post Nr.1 from the "mustang-thread".
The first time i can copy the files (fw.zip, Magisk-v19.3.zip, finalize.zip) with the command adb push... to the sdcard as it is explains. Then i can see this files in TWRP and flash the 3 files .
There are no error displayed so i think the root was ok.
Now i see that there is a new version of Magisk-20. So i copy the new downloaded file to the sdcard with adb push...
The same i do with the GApps.zip file
But now i cant find the new files on the sdcard in/with TWRP to flash them. There are just the 3 files from the first time.
If i normaly start the fire 7 (Android OS), i can see all the three files (form the first time and the second time) on the sdcard. (with Settings, Storage, SD-Card,)
What am I doing wrong?
What can i do?
Perhabs it has something to do with, that after i root and boot the first time, i was ask something like how i want to use the SD-Card (i thought it was mean the extern SD Card)?. I do not know anymore what i chose.
Nobody knows what that could be, or have I expressed myself unclear what I mean
Or is this the wrong area in the forum?