Develop Bugs

[Q] Help Rooting 2.2.1 - I've tried that edition.

I, for the life of me, being a compute tech since the mid 90's, can't root this mytouch g3 slide. I have android 2.2.1 installed, I know I know, I hate it when people don't RTFM, I have tried the following:
(USB Deugging is on, charge mode only when plugged in, full android SDK kit installed and working. PDAnet drivers installed, I have superoneclick 1.9 computer see the phone fine, Goldcard works perfectly.)
1. I've tried Cyanogenmod's instructions (wiki.cyanogenmod.com/wiki/TMobile_myTouch_Slide:_Full_Update_Guide)
-Nothing happens after 2nd to last command line of step 8
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
2. I have tried this "New way to downgrade from 2.2 to 2.1" (http://forum.xda-developers.com/showthread.php?t=1108316)
-4a. , It does not give me the option to "hit vol up to update"esrpimg" just flashes error no image found error messages:
3/ I have tried ULTRA EASY ROOTER (http://forum.xda-developers.com/showthread.php?t=999121)
same problem as #2's problem, just error messages.
4. And I have tried this: "How-To [Root][NewLinks] The myTouch 3GS if you updated to Offical 2.2.1 and lost root" (http://forum.xda-developers.com/showthread.php?t=1025336)
-Everything goes smooth until I type in this line "chmod 04755 *" which I get a bank carraige return, and I can type to my hearts content, nothing happens, can't exit, etc, have to CRTL + C to get out out of it. similar problem as #1's problem. I have tried again and again and again.
Help.

Make a goldcard and install the img from the bootloader.
Then try again.
sent from my MT3GS running CM7 nightly

thanks for the reply poormanq45. I did make a goldcard, maybe it doesn't like my MicroSD card? Which image do you want me to install from the bootloader? Which instructions should I be following?
Which set of instructions talk about having a swap partition as your 3rd partition on the SD card?
poormanq45 said:
Make a goldcard and install the img from the bootloader.
Then try again.
sent from my MT3GS running CM7 nightly
Click to expand...
Click to collapse

I don't remember which img I used. IIRC there are three different ones. Just try each one until one works.
It's possible that your MicroSD card isn't capable of being a goldcard. I had to try two different ones
sent from my MT3GS running CM7 nightly

My Stock 2.2.1 Process
My warranty replacement came with stock 2.2 and all of the tutorials here and elsewhere fell short. I did notice a lot of the other guides were based on "if you upgraded to 2.2"; that did not completely apply in my situation. I to am an industry professional with 14 years experience and am a stickler for detail. I had the gold card created on a SanDisk 2gb micro sd acquired from Walgreen's. I had followed all the steps in order, but the update on the first reboot never happened, it never asked and selecting the update.zip failed signature verification. I knew S-ON was set (which is the whole problem) but the guides I saw to disable it required you already be rooted (which I wasn't).
This past week I did something different. Using the official HTC MyTouch 3G Slide Froyo installer (not selecting anything just having RUU opened) I copied the folder structure (a crazy GUID looking thing) that was in my %TEMP% directory to another location. I closed out of the installer and went to that copied folder. I moved the existing "rom" file and copied the 2.1 "ESPRIMG" image there and renamed it to rom.zip. I then executed the RUU from that folder. It being an HTC official rom did allow the RUU to complete and the slide was officially downgraded to 2.1. After the reboot I verified the ROM was the older version and went ahead with what I was used to.
After that; some of my previous attempts to root were evident because I already had the "#" prompt in the adb shell. Regardless, I did repeat some of the documented steps (just in case my eyes deceived me) from the exploid method (what I used on my previous phone that was an original build). I originally flashed the CM 7.03 while the goldcard (2gb) sd was still in there. I then installed my 32GB card, then hit a nightly, then hit a few more older CM builds (had issues with sd-ext, couldn't find the original guide i used to set it up - new card as well). I did format boot, data, system, sd-ext, and the cache from the clockworkmod recovery screen before settling on CM 7.1 RC 1
If you find it necessary to create the sd-ext partition, format the fat partition in windows, format the other two in the shell. I do not recommend logging (app sync) on the first rom. Build the sd-ext first; re-rom, before doing all the account/app setup. While the phone is USB debugging mode you can use DriodExplorer to shortcut some things (especially if u have all your apks in a backup folder on your computer). I do not recommend using certain busy-box commands from the DriodExplorer terminal. The output can be out of sync at times. I have a 32gb SD and have about 29.3G on FAT, 896MB on SD-EXT (ext3 file system), and the rest on cache. After that Simple2Ext will allow for you to tell CM7 to use the SD-EXT. I do not use .android secure (the froyo apps2sd) because that causes issues when using the fat partition as disk in windows and you have something like a theme installed. Because of themes, games, and other apps I am now using 62% of the sd-ext partition. And an earlier comment I saw on the thread is right. The partition order is FAT, SD-EXT, CACHE. Where the guide is I don't recall.
Also note: If you are doing ADB commands and notice it often says the process is stale; uninstall the HTC sync (this does not affect the drivers, drivers are installed as a pre-req before HTC Sync is installed).
My only outstanding issue is the radio version might have been affected; it's not showing a version number on my info app. So I need to find a guide on verifying/upgrading the radio (one that does not involve installing the htc froyo rom).

Stuck... help.
First of all, sorry I can't past in links to the images, because I need a minimum of eight posts.
-----
Okay, I have made sure my phone has 25MB free. (it told me I needed this)
I have Turn USB Debugging on.
The phone is set to charge mode only.
The phone is plugged in and drivers installed. PDANet is not running.
I've tried it with a goldcard in it and out of it.
tagr.org/ScreenShot084.jpg
I Downloaded "T-Mobile_myTouch_3G_Slide_Software_Update_2.15.531.3.exe" from here the website, (I can't post the links)
I ran setup, and left it open while I went to the temp folder and copied it all out to another location.
I went to the NEW location and deleted "rom.zip" and replaced it with the 140 MB "ESPRIMG.zip" into that folder and renamed it rom.zip
In the new folder, I ran "ARUWizard.exe", agree, agree, okay, etc.
All goes okay, I get to this screen:
tagr.org/ScreenShot091.jpg
I say next, About two minutes into it, the phone reboots, put the HTC logo on it. Then on the computer, I get to this screen:
tagr.org/ScreenShot089.jpg
The phone is stuck on the "HTC" logo when the USB is plugged in. When USB is unplugged, the screen turns to this:
tagr.org/ScreenShot090.jpg
Stuck meaning, can't reboot, turn off, etc. So I have to pull the battery. When it turns on, all seems okay, it's still at 2.2.1 though.
Thoughts?

What the... why could I post pics my first post, but not my third...new policy?
eckre said:
First of all, sorry I can't past in links to the images, because I need a minimum of eight posts.
Click to expand...
Click to collapse

Okay I've figured it out and wrote up a NEW Guide: http://forum.xda-developers.com/showthread.php?t=1189485
No goldcard is needed, no console typing ADB shell etc. blah blah blah, so easy now.

[GUIDE] Full Phone Backup without Unlock or Root

Like a lot of you, I have been putting off unlocking the bootloader on my Nexus because I didn't want to have to go through the hassle of backing up everything manually and restoring individual application data; logging back into apps; saving settings; etc. I found an undocumented (at least as far as my googling was able to find) feature in the latest version of the ADB platform tools (for Android 4.0+) that allows you to create a full system backup, including app apks, their respective data, as well as the internal storage.
Keep in mind this is experimental and not exactly publicized as a feature of ICS, so don't count on this as your only method of backup!
This guide assumes you have already installed the Android SDK, and updated the Android SDK Platform Tools to the latest version (currently Rev 10) using the SDK Manager.
1. Connect your device via USB, and open a command prompt.
2. Optionally, type the command 'adb devices' to ensure that your device is properly recognized. If you're comfortable with ADB already, just skip this.
There is a command, 'adb backup' (to be detailed shortly), that will now allow you to create a full system backup.
The command parameters format is:
adb backup [-f <file>] [-apk|-noapk] [-shared|-noshared] [-all] [-system|nosystem] [<packages...>]
Click to expand...
Click to collapse
The most basic command you can use* is simply:
adb backup -all
Click to expand...
Click to collapse
This will use the defaults to backup only app and device data (not the APKs themselves) to the current directory as 'backup.ab'
* This may not work for every setup. If you get an error such as "adb: cannot open file ./backup.ab", use:
adb backup -all -f C:\backup.ab
Click to expand...
Click to collapse
Or substitute the path of your choice in place of C:\.
To explain the parameters:
-f <file>
Click to expand...
Click to collapse
Use this to choose where the backup file will be stored, e.g. '-f /backup/mybackup.ab', which will save it at the root of your drive (C:\ for Windows, etc.) in a folder called backup, as a file named 'mybackup.ab'. I recommend using this flag to set a location manually, as with my first backup test, it said that it completed successfully, but I was unable to locate the backup file. I have no idea where it was saved, but it wasn't where it should have been located.
-apk|-noapk
Click to expand...
Click to collapse
This flags whether or not the APKs should be included in the backup or just the apps' respective data. I personally use -apk just in case the app isn't available in the Market, so that I don't have to go hunt it down again. The default is -noapk.
-shared|-noshared
Click to expand...
Click to collapse
This flag is used to "enable/disable backup of the device's shared storage / SD card contents; the default is noshared.", which for the Nexus I would certainly flag to -shared, but from my test, it did not restore all of the contents of my internal storage, so I recommend backing up music, pictures, video, and other internal storage items manually, just to be on the safe side. The default is -noshared.
-all
Click to expand...
Click to collapse
This flag is just an easy way to say to backup ALL apps. The packages flag (further on) can be used to choose individual packages, but unless you're just wanting to backup a specific application, use -all for a full system backup.
-system|-nosystem
Click to expand...
Click to collapse
This flag sets whether or not the -all flag also includes system applications or not. I used -system, but this is probably unnecessary, and I would almost guess that it is safer to use -nosystem, but use your own judgment on this. The default is -system.
<packages...>
Click to expand...
Click to collapse
Here you can list the package names (e.g. com.google.android.apps.plus) specifically that you would like to backup. Use this only if you're looking to backup a specific application.
3. Once you've made your decision on how to perform the backup, simply type the command as you would like it; in my case, this is the command that I used:
adb backup -apk -shared -all -f C:\backup20111230.ab
Click to expand...
Click to collapse
4. You will see a screen like the following:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
5. Enter a password (if desired) for encryption of the backup file. RETAIN THIS PASSWORD FOR RESTORING LATER.
6. This process will take several minutes to complete, depending on the settings you've chosen, but when completed, you will get a toast on-screen saying 'Backup Complete', or if you miss that, you'll know once your phone returns to the home screen.
7. Now go unlock your bootloader (not going to go into the process for this guide, but you probably know how already, and if not, there are several guides a search away).
8. Once you're booted back into Android, you can choose to add your account now, or skip that for later. I skipped it for later, but I think it might make the process more smooth to sign in before the restore. YMMV.
9. To restore, with your device connected open your command prompt again, and type:
adb restore C:\backup20111230.ab
Click to expand...
Click to collapse
replacing 'C:\backup20111230.ab' with the location of your backup file.
10. You will see a screen like the one below:
11. Simply type in your current encryption password (if you've set one), and the password with which the backup was encrypted (if you chose to set a password), and the restore will begin. It again will take several minutes depending on the size of the backup and the options chosen.
12. You're back to normal, short of possibly some widgets on the home screen. My wallpaper was even restored, my app folders remained just as I had them before, my alarms remained, and for most applications, I didn't even have to log back in; it kept everything.
________________________
NOTE: I did have an issue with not all files being restored to the Internal Storage; in particular, the Gallery still displayed all the folders and files that it had cached (which it expected to be there) as only gray boxes, and would not display the images, nor would it rescan the media. I simply copied the files back to the Internal Storage directory manually, and all was well again. Again, YMMV.
NOTE 12/31: Also to note, this will not back up SMS messages, so if you're concerned about those, you may want to look into an alternative application to back up SMS.
NOTE 06/12: There seems to be a bug in which backup and restore operations will fail unless a desktop backup password is set under Developer Options. It will not work with a blank password.
Hope this is able to help! If so, give me a thanks )) and let me know how your experience goes.
- Kevin

In earlier build of ics there's an option to do such backup under back up and restore settings.
However it's not there in final ics.
I've done it once when I flashed one of those early build of ics on nexus s.

faizalmzain said:
In earlier build of ics there's an option to do such backup under back up and restore settings.
However it's not there in final ics.
I've done it once when I flashed one of those early build of ics on nexus s.
Click to expand...
Click to collapse
Interesting. They must have deemed it not quite ready for primetime yet. Seems like it should show up in a future version sometime in the not-too-distant future, then. Until then, this seems to work pretty well.

I just finally rooted. The longer you wait the more painful it will be to start over, so just get it over with. If the adb method qorkks then great. I've flashed and rooted so many phones that its just better to get it over with as pukemon will tell you.

RogerPodacter said:
I just finally rooted. The longer you wait the more painful it will be to start over, so just get it over with. If the adb method qorkks then great. I've flashed and rooted so many phones that its just better to get it over with as pukemon will tell you.
Click to expand...
Click to collapse
While that's true, if you're already past the point of painful return, why start over when this backup method is available? It's not a question of if it works (it does work).

my first post. i have successfully taken a full backup using your guide and it worked great. thanks! my question is can i now unlock the boot loader and root then restore my backup and i will have all my settings and apps along with still having the unlocked boot loader and root?

sahakiap said:
my first post. i have successfully taken a full backup using your guide and it worked great. thanks! my question is can i now unlock the boot loader and root then restore my backup and i will have all my settings and apps along with still having the unlocked boot loader and root?
Click to expand...
Click to collapse
Yes, as shown in the guide, just use the 'adb restore' command after unlocking the bootloader. You may wish to backup your Internal Storage manually, just to be safe, and backup your SMS with a third party app, if you care to keep them. Obtaining root isn't covered in this guide, but yeah, you can root it once you've unlocked the bootloader.

I have been trying to do this, but when after i "backup" the backup file shows no size. Am I missing a step?

ktulu029 said:
I have been trying to do this, but when after i "backup" the backup file shows no size. Am I missing a step?
Click to expand...
Click to collapse
Interesting. Could you post the exact command that you used, and also what OS you're running?

copkay said:
Interesting. Could you post the exact command that you used, and also what OS you're running?
Click to expand...
Click to collapse
Code:
adb backup -apk -shared -all -f /c/backup.ab
I am running win 7 x64, and my phone is running 4.0.2 if that is useful information.
It runs everything on the phone like prompted, just doesn't save any data.

ktulu029 said:
Code:
adb backup -apk -shared -all -f /c/backup.ab
I am running win 7 x64
Click to expand...
Click to collapse
Did the screen show up on your phone requesting permission? If so, did you allow it permission, and wait until it said that the backup was completed to check the file size?

Wow, this should be a freakin STICKY!!!

copkay said:
Did the screen show up on your phone requesting permission? If so, did you allow it permission, and wait until it said that the backup was completed to check the file size?
Click to expand...
Click to collapse
Correct. I went through all of the permissions asked on the phone.
i.e. the screen you posted in step 4.

ktulu029 said:
Correct. I went through all of the permissions asked on the phone.
i.e. the screen you posted in step 4.
Click to expand...
Click to collapse
After allowing the backup, did you get a Toast saying "Backup Started"?

I do. And shortly after, maybe 5 sec I get one saying backup complete. I just did one just using the -apk code, and it took about 10 min, but still rendered me with a .ab file with 0kb.

ktulu029 said:
I do. And shortly after, maybe 10 sec I get one saying backup complete. I just did one just using the -apk code, and it took about 10 min, but still rendered me with a .ab file with 0kb.
Click to expand...
Click to collapse
I apologize if this is a stupid question, but it's one worth asking: have you tried refreshing the folder? Initially the file starts out as 0b and builds up as it goes, and it's possible the file has a size, but the window just hasn't updated to show it.

copkay said:
I apologize if this is a stupid question, but it's one worth asking: have you tried refreshing the folder? Initially the file starts out as 0b and builds up as it goes, and it's possible the file has a size, but the window just hasn't updated to show it.
Click to expand...
Click to collapse
Ha, it is ok and very reasonable to ask that. I have, and same result. I have been going through and toggling things to see what I have on or off that should be otherwise. Just to get the next one out of the way, USB debugging is on.

ktulu029 said:
Ha, it is ok and very reasonable to ask that. I have, and same result. I have been going through and toggling things to see what I have on or off that should be otherwise. Just to get the next one out of the way, USB debugging is on.
Click to expand...
Click to collapse
Haha, okay. Hmm, well if it's getting as far as that there's no question that ADB is connecting. For some reason, it's just not writing out the files. You're on 4.0.2, I'm sure? (not that it should make a difference), and are you GSM or LTE? I really don't think it should matter; I'm just grasping at straws...
I just tried the same exact command you mentioned; I'm also on Win7 x64; LTE Nexus with 4.0.2; backed up directly to C:/c/backup.ab.

copkay said:
Haha, okay. Hmm, well if it's getting as far as that there's no question that ADB is connecting. For some reason, it's just not writing out the files. You're on 4.0.2, I'm sure? (not that it should make a difference), and are you GSM or LTE? I really don't think it should matter; I'm just grasping at straws...
I just tried the same exact command you mentioned; I'm also on Win7 x64; LTE Nexus with 4.0.2; backed up directly to C:/c/backup.ab.
Click to expand...
Click to collapse
I am running the same setup as you. Would the version of SDK tools and Platform tools matter? I am running Rev 16 and 10 repectively. When I run the comands I am in the C:/ prompt, but that doesnt seem to matter from what I can tell. I am using the USB computer connection of MTP rather than PTP if that matters.
I am still pretty green to this, as the last phone I really messed with was the Eris, and with that it has still been awhile. Things have really come a long way since then.

ktulu029 said:
I am running the same setup as you. Would the version of SDK tools and Platform tools matter? I am running Rev 16 and 10 repectively. When I run the comands I am in the C:/ prompt, but that doesnt seem to matter from what I can tell. I am using the USB computer connection of MTP rather than PTP if that matters.
I am still pretty green to this, as the last phone I really messed with was the Eris, and with that it has still been awhile. Things have really come a long way since then.
Click to expand...
Click to collapse
The versions might matter, but you're on the same revisions I'm on. Now, I will say that I am running from C:/Program Files(x86)/Android/android-sdk/platform-tools/ rather than just the straight C:/ prompt, just because I've been too lazy to add ADB to my system variables. I'm also using MTP, which shouldn't affect it.
Yeah, things have changed quite a bit; going from the Droid line to the Fascinate was my last jump.
The only thing I can think of to try is to make sure that you are running your Command Prompt as Administrator. The fact that it's creating a file at all seems to disprove that this would have an effect, but it's worth a try.

Unlock bootloader on GT-I9250 without wipe and without root

Hi! After latest OTA update I was left with an unbootable Galaxy Nexus (zygote couldn't start) and I lost root (su needed activitymanager up). So I needed to unlock to revive the phone, but I really didn't want to lose my data. After some exploration I could come up with a way to unlock bootloader without wipe and without root. I have seen several questions about this here and this was deemed impossible, so I decided to share my findings and expect they might help someone. Should work with GSM tuna phones.
Components for success:
— unlocking without wipe via putting a byte in param partition (needs root):
[1] http://forum.xda-developers.com/showthread.php?t=1650830&page=15
— OMAPFlash, a low-level utility for manipulating and flashing chipset (usually used to unbrick phones)
[2] http://forum.gsmhosting.com/vbb/f63...9250-galaxy-nexus-gt-i9100g-gt-i9300-1465412/
Take the two of them and you have a solution. I could successfully flash unlock byte to param partition using OMAPFlash.
A sketch of a guide:
1. Boot windows xp, download OMAPFlash (http://d-h.st/XNv), connect a turned off phone without battery, install drivers for omap device. (Mod edit: I've updated the download link.)
2. Dump a part of param partition. You don't need to dump the whole partition, but I think it is safer if you dump a sector-aligned area (512*n). I used 4KB (8 sectors).
Code:
OMAPFlash -omap 4 -2 -p OMAP4460_TUNA_8G_HS_PRO -t 36000 chip_upload [email protected] 1000 param.img
chip_upload is for downloading data from device memory
[email protected] is the start of params partition (check /sys/block/mmcblk0/mmcblk0p4/start, multiply by sector size 512 and convert to hex)
1000 is to copy 4KB.
Sometimes the process stalls (esp if you try to download larger dumps), just reconnect and retry.
3. Verify that the content is similar to first 4 KB of the dumps of param partitions attached in the thread [2]. For me they matched entirely.
4. Change the byte at offset 124 (0x7C) from 01 to 00.
Code:
echo -ne "\x00" | dd obs=1 count=1 seek=124 of=param.img conv=notrunc
5. Flash it back to the device.
Code:
OMAPFlash -omap 4 -2 -p OMAP4460_TUNA_8G_HS_PRO -t 36000 chip_download [email protected] param.img
Reboot, you are unlocked.
Additional links:
[3] http://forum.gsmhosting.com/vbb/f634/gt-i9250-pinout-enjoooy-1463061/ GT-I9250 JTAG pinout. Not directly releavant to the guide, but I found it while searching for solution, thought that can help someone in future.

Additional reading
The dangers of OTA when you have root, or why I was stuck with an unbootable phone at all
I learned the hard way that OTA may cause unpleasant results if you are trying to preserve root and mess with filesystem.
I was trying to preserve root in a way similar to one used by rootkeeper apps: put a copy of su somewhere in /system and make it immutable. So I went and put my su to /tts (thought that it's unprobable that OTA will do something there), and made it immutable.
And then the update came. As part of the the update process it copied a new version of /system/usr/share/zoneinfo/zoneinfo.version file and the file got 660 perms (package_extract_dir("system", "/system") in the update_script). Then it went on to recursively fix permissions so that the mentioned file would be made readable (set_perm_recursive(0, 0, 0755, 0644, "/system")). But the set_perm_recursive was met by immutable su in tts directory, chmod returned error and the recursive process was stopped before it got to zoneinfo.version file. So the latter file remained unreadable.
Unfortunately during startup zygote preloadsClasses, static constructor in some sqlite class needs DateFormat, and DateFormat reads zoneinfo. And fails cause it's unreadable. Exception, System.exit. Phone boot stuck.
To work my copy of su needs to send a message to ActivityManager service using binder. I wrote a dirty mock for AM but servicemanager didn't accept my fraud, it checked uid. I tried to bypass preloadClasses with overflowing system file descriptors count to prevent zygote from reading preload class list, but somehow it didn't succeed. Thus the only option I had was unlocking bootloader.
So it may end bad if you mess with /system on a stock rom with locked bootloader and want to receive OTA. It may seem natural, but sometimes the changes seem irrelevant, and then a chain of small failures leads you to loss of everything: boot, root, and data.

This is great work! Kudos to you for figuring it out.
By the way, where did you find the syntax for OMAPFlash commands?

efrant said:
This is great work! Kudos to you for figuring it out.
By the way, where did you find the syntax for OMAPFlash commands?
Click to expand...
Click to collapse
There are some docs in OMAPFlash_tuna.zip package. The most interesting is OMAPFlash.txt that lists options and commands and has some examples.
Also I was lucky that there is a complete example for unbricking GT-I9250 in Targets/Projects/tuna. This is where I took the options specific for this device.

nichtverstehen said:
There are some docs in OMAPFlash_tuna.zip package. The most interesting is OMAPFlash.txt that lists options and commands and has some examples.
Also I was lucky that there is a complete example for unbricking GT-I9250 in Targets/Projects/tuna. This is where I took the options specific for this device.
Click to expand...
Click to collapse
Exactly. I haven't needed this yet, but i had looked in those board files, cross examining with omap 4460 manual that can be found on the web. Thanks for sharing.
I was not aware that JTAG method had been found. Great news.
Sent from my i9250

Works!
Awesome - this worked for me! Unlocked, unrooted, TAKJU Galaxy Nexus w/JB 4.2.2. I used OMAPFlash_tuna.zip (download link).
I had issues when the downloaded param.img file was long, so I replaced 1000 with 200 in the commands. Regardless, it still took me probably 5-10 tries on each command to get it working (unplugging and replugging the phone in between), and sometimes it would freeze up and I'd have to restart Windows. If it takes longer than 5 seconds, you should press Ctrl+C and restart that step.
My problem was that one of my volume buttons is messed up, and as a result the fastboot screen doesn't work - Windows doesn't detect a fastboot device, and none of the hardware buttons or the touchscreen works either. As a result I needed to unlock the bootloader without using fastboot (oem unlock), and this did the trick!
Also, on Windows, I downloaded a hex editor (i.e., HxD) to do the editing. My modified param.img (only 512 bytes) is attached as well.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Thank you!!! It worked for me too!
The volume buttons on my Galaxy Nexus didn't work and I can't recharge the battery via USB. The USB works only as data connection. Despite all these issues on my phone, it worked for me too!!
I replaced the size in the commands from 1000 to 400 (1024 bytes = 2*512), and I had to put the battery on the phone.

Sweet jesus I cannot express enough gratitude for this post. While I was a little worried about bricking my device, it would up working perfectly.
A couple of confusing points for anyone out there trying to do this:
- The dump / reflash should only take a few seconds each. If it hangs, cancel and re-start the process.
- Install the drivers with the device OFF but plugged in. You will have an OMAP device without a driver in your device manager. Update the device driver and you're good to go.
- I didn't know how to get the dd command to work on windows, so I also went the Hex editor route it it worked flawlessly
- The only snag I ran into was that it did not boot into my flashed CWM after doing an "adb reboot recovery" from the stock rom. It went back to the stock android recovery. From there I did "fastboot boot cwmrecovery.img" and installed my rom and gapps. After that initial boot, it rebooted into recovery just fine! It seems like a weird glitch (maybe just a one-off).
Cheers

techobrien said:
- Install the drivers with the device OFF but plugged in. You will have an OMAP device without a driver in your device manager. Update the device driver and you're good to go.
Click to expand...
Click to collapse
This is a critical step right here. This thread either should be linked on the 101 FAQ if it's not already or stickied.
a maguro wrote this.

techobrien said:
- The only snag I ran into was that it did not boot into my flashed CWM after doing an "adb reboot recovery" from the stock rom. It went back to the stock android recovery. From there I did "fastboot boot cwmrecovery.img" and installed my rom and gapps. After that initial boot, it rebooted into recovery just fine! It seems like a weird glitch (maybe just a one-off).
Cheers
Click to expand...
Click to collapse
Sounds like you are getting hit with the /system/recovery-from-boot.p file. When you boot into Android, this file checks to see if you have stock recovery...if not, it replaces it with stock recovery. You can rename, move, delete the file safely. It shouldn't exist in custom ROMs, which would explain why after installing a ROM and Gapps you were fine.
This is pretty cool. Nice find OP.

cupfulloflol said:
Sounds like you are getting hit with the /system/recovery-from-boot.p file. When you boot into Android, this file checks to see if you have stock recovery...if not, it replaces it with stock recovery. You can rename, move, delete the file safely. It shouldn't exist in custom ROMs, which would explain why after installing a ROM and Gapps you were fine.
This is pretty cool. Nice find OP.
Click to expand...
Click to collapse
This post thread have not been getting the attention it deserves..
Beamed from my Maguro.

cupfulloflol said:
Sounds like you are getting hit with the /system/recovery-from-boot.p file. When you boot into Android, this file checks to see if you have stock recovery...if not, it replaces it with stock recovery. You can rename, move, delete the file safely.
Click to expand...
Click to collapse
Good to know for next time round. The flimsy headphone ribbon cable is the bane of my existence and it seems like a somewhat common problem. I didn't think that the custom rom would touch the bootloader so I was confused, but /system/ makes sense. Thanks for the tip.

Just in case anybody was wondering, this method also worked for my Verizon GNex LTE. I also used a HEX editor.

Hi,
i'm thinking to use this method to unlock my Nexus' bootloader, in order to gain root privileges without wiping the memory.
This because i need to try and undelete files i have lost on my phone, to do this i need the root but i can't use the normal procedure that would wipe forever all the data i need to restore.
As i am new to this kind of operations, i never even rooted my Android phones, i wanted to ask if this procedure can fit my situation, and if there are any risks....
Thank you very much
EDIT: It worked perfectly!!
Thank you very much!!

Did anybody try it on MAGURO device? Does it require any change in the procedure?

Um... The op (and others) did it on a maguro? After all, the title says "on GT-I9250".

Isn't a i9250 a Maguro?
Beamed from my Grouper

Mod edit: removed quote of the OP.
Is WinXP really required for this process or will it work on newer versions of Windows ie Win8?

mielli1 said:
Is WinXP really required for this process or will it work on newer versions of Windows ie Win8?
Click to expand...
Click to collapse
Please do not quote the first post of threads when you reply.
As for your question, if you can get the driver to install on Windows 8, the program will work fine. The driver installs fine in Windows 7 by the way.
Don't forget to disable driver signature verification if you are trying to install drivers in Windows 8.

Windows 8 - stuck at installing drivers
beekay201 said:
This is a critical step right here. This thread either should be linked on the 101 FAQ if it's not already or stickied.
a maguro wrote this.
Click to expand...
Click to collapse
I have a Nexus with a broken volume up button, so am trying this method as a way of unlocking the bootloader and rooting my device.
When I plug the powered off device into the usb port, constantly get the sounds of a device being inserted, and then unplugged (two different beeps.) This continues until I unplug the phone.
Is this the step where I should get a "found new hardware" notification? It is not happening for me, and I'm wondering if this is Windows 8 related.
FYI - I have already disabled driver signature verification.

[TUT] [ROOT] Backup restore IMEI manually

Automatic Backup Restore IMEI TOOL by Sector1369 is HERE .
(Only Require Custom recovery)
Automatic backup restore CMD script added by "deadlyindian" at Post#5
(Require PC ,ADB drivers & Root permissions )
If you still want to do this manually, look below
IMEI backup of redmi 1s
Require ROOT permissions
We all known that EFS partition holds the imei,sn ,wifi mac & other important data.
In Snapdragon the EFS partition are modemst1 ,modemst2 & FSG partitions. so it's important to take backup of these partitions.
1.connect your phone to PC , adb debugging enabled & goto adb shell by,
Code:
adb shell su
OR
Open terminal emulator app in your phone & take super user permissions, by
Code:
su
2.type following commands to backup imei partitions.
Code:
dd if=/dev/block/mmcblk0p16 of=/sdcard/mmcblk0p16_modemst1
dd if=/dev/block/mmcblk0p17 of=/sdcard/mmcblk0p17_modemst2
dd if=/dev/block/mmcblk0p20 of=/sdcard/mmcblk0p20_fsg
also these are some important partition you should consider to backup.
modem, fsc, bk1, ddr.
Code:
dd if=/dev/block/mmcblk0p23 of=/sdcard/mmcblk0p23_modem
dd if=/dev/block/mmcblk0p9 of=/sdcard/mmcblk0p9_DDR
dd if=/dev/block/mmcblk0p12 of=/sdcard/mmcblk0p12_bk1
dd if=/dev/block/mmcblk0p18 of=/sdcard/mmcblk0p18_fsc
Now the backup is stored in you internal storage ,store these files in safe place.
in case u get invalid imei or unknown, restore these partitions.
To restore these partitions,
Code:
dd if=/sdcard/mmcblk0p16_modemst1 of=/dev/block/mmcblk0p16
dd if=/sdcard/mmcblk0p17_modemst2 of=/dev/block/mmcblk0p17
dd if=/sdcard/mmcblk0p20_fsg of=/dev/block/mmcblk0p20
dd if=/sdcard/mmcblk0p23_modem of=/dev/block/mmcblk0p23
dd if=/sdcard/mmcblk0p9_DDR of=/dev/block/mmcblk0p9
dd if=/sdcard/mmcblk0p12_bk1 of=/dev/block/mmcblk0p12
dd if=/sdcard/mmcblk0p18_fsc of=/dev/block/mmcblk0p18
Working on Aroma EFS backup restore tool..
NOTE:-
Don't use tools or commands from other device because different devices has different partition address, that will result in wrong backups.
To use this method to backup other phones EFS , u should find your partition info.
Redmi 1s Partition tables can be found HERE
ENJOY,

Thanks man...it would be alot helpful if i gone to any trouble [emoji7]

But the problem with lost imei is for Redmi with MediaTek processor. Redmi Qualcomm don't suffer from this problem.

pgreed said:
But the problem with lost imei is for Redmi with MediaTek processor. Redmi Qualcomm don't suffer from this problem.
Click to expand...
Click to collapse
i know but it's always better to take bakup,who knows what 'll happen...
there is no way to generate imei,wifi mac data for qualcomm (as far as i know) ...
so it will come handy...

Auto IMEI Backup & Restore Tool
Backup restore IMEI Automatically
FIRST INSTALL THE ADB DRIVERS FOR THE 1S ► GO HERE ◄
Requires Phone to be ROOTED & USB Debugging turned ON
This is for Xiaomi Redmi 1S Only
I've created a CMD script that will automatically backup the IMEI & Also Restore it back again if you want to...
Backed Up files are inside MYIMEI folder of your selected backup storage.
NOTE : Enable root access for adb if you're on Custom ROM based on CyanogenMod
to do that ► Open Settings ► Superuser ► Superuser Access ► Select Apps and ADB ► done
► Download it from attachment
► Extract it
► Run R1SBAR.exe & follow instructions.
While restoring make sure the backed up files are inside the MYIMEI folder of either Internal Memory or External or it wont work.
If you face any error do tell me!
AGAIN ITS ONLY FOR REDMI 1S

deadlyindian said:
Backup restore IMEI Automatically
Requires Phone to be ROOTED & USB Debugging turned ON
This is for Xiaomi Redmi 1S Only
I've created a CMD script that will automatically backup the IMEI & Also Restore it back again if you want to...
Backed Up files are inside MYIMEI folder of your selected backup storage.
► Download it from attachment
► Extract it
► Run R1SBAR.exe & follow instructions.
While restoring make sure the backed up files are inside the MYIMEI folder of either Internal Memory or External or it wont work.
If you face any error do tell me!
AGAIN ITS ONLY FOR REDMI 1S
Click to expand...
Click to collapse
It working perfectly.Thank you.

pgreed said:
It working perfectly.Thank you.
Click to expand...
Click to collapse
You're Welcome :good:

[Backup restore IMEI Automatically] works like charm. thanks :good:

lavizta said:
[Backup restore IMEI Automatically] works like charm. thanks :good:
Click to expand...
Click to collapse
im glad it help :good:

deadlyindian said:
Backup restore IMEI Automatically
Requires Phone to be ROOTED & USB Debugging turned ON
This is for Xiaomi Redmi 1S Only
I've created a CMD script that will automatically backup the IMEI & Also Restore it back again if you want to...
Backed Up files are inside MYIMEI folder of your selected backup storage.
► Download it from attachment
► Extract it
► Run R1SBAR.exe & follow instructions.
While restoring make sure the backed up files are inside the MYIMEI folder of either Internal Memory or External or it wont work.
If you face any error do tell me!
AGAIN ITS ONLY FOR REDMI 1S
Click to expand...
Click to collapse
Great work :good::good:

None of the usual ROM / kernel flashing result in loss of these partitions .
If someone is able to screw up partitions, chances are that he will remove the partition table too ..
and with that he will not be able to fastboot anymore , to use backups made here.
Don't get me wrong, but its of little use imo.
Sector1369 said:
Code:
dd if=/dev/block/mmcblk0p23 of=/sdcard/mmcblk0p23_modem
dd if=/dev/block/mmcblk0p9 of=/sdcard/mmcblk0p9_DDR
dd if=/dev/block/mmcblk0p12 of=/sdcard/mmcblk0p12_bk1
dd if=/dev/block/mmcblk0p18 of=/sdcard/mmcblk0p18_fsc
ENJOY,
Click to expand...
Click to collapse

kapil.git said:
None of the usual ROM / kernel flashing result in loss of these partitions .
If someone is able to screw up partitions, chances are that he will remove the partition table too ..
and with that he will not be able to fastboot anymore , to use backups made here.
Don't get me wrong, but its of little use imo.
Click to expand...
Click to collapse
U never know when sh*t happens there is no harm in taking the backup. Had personally lost imei on couple of Samsung phone while flashing roms and was able to restore it with the efs backup.

rkkaranrk said:
U never know when sh*t happens there is no harm in taking the backup. Had personally lost imei on couple of Samsung phone while flashing roms and was able to restore it with the efs backup.
Click to expand...
Click to collapse
I mean backing up DRM keys and TA partitions made sense since they are wiped in some bootloader unlocking..
You almost make it sound like, I can restore someone else's IMEI too :silly: ..
I still have my old nokia phones with me of which I can rob their identities ?
Some random Redmi dev can give surprise to actually make an app for this..
Chinese phones have already been a pain in a$$ for Indian Govt due to lack / duplicate of this IMEI modules.

kapil.git said:
I mean backing up DRM keys and TA partitions made sense since they are wiped in some bootloader unlocking..
You almost make it sound like, I can restore someone else's IMEI too :silly: ..
I still have my old nokia phones with me of which I can rob their identities ?
Some random Redmi dev can give surprise to actually make an app for this..
Chinese phones have already been a pain in a$$ for Indian Govt due to lack / duplicate of this IMEI modules.
Click to expand...
Click to collapse
I'm pretty sure u have been using a Sony phone and have limited knowledge so don't jump and compare the phones with the same thing.
As for the imei take help of google and search for z3x/cyclone/nspro/magma what are they used for:silly:

it might come in handy or it might not
nevertheless i'm putting it in safekeeping.
thanks for the work & effort.
:good:

rkkaranrk said:
I'm pretty sure u have been using a Sony phone and have limited knowledge so don't jump and compare the phones with the same thing.
Click to expand...
Click to collapse
Yes you are correct , been using Sony for a while
As for the imei take help of google and search for z3x/cyclone/nspro/magma what are they used for:silly:
Click to expand...
Click to collapse
mmmkaay..

@deadlyindian,
Thanks for providing the automated script to back up imie.
I did go through your post and did as per the instructions mentioned step by step. However, I am unable to proceed after getting the message "Please connect usb cable now" after running R1SBAR. I do have root access(checked from root checker app) and have also enabled USB Debugging. I also inserted cable after getting the message.
Does it take a lot of time(more than 5 mins) to backup imei cause I continued till 5 mins before closing the cmd prompt.
Hope you can help me here.
PS: I am using MIUI v45 global version "JHCCNBH45.0 （V5） " in case if you need.

ADB Drivers & instructions...
fanboy_android said:
@deadlyindian,
Thanks for providing the automated script to back up imie.
I did go through your post and did as per the instructions mentioned step by step. However, I am unable to proceed after getting the message "Please connect usb cable now" after running R1SBAR. I do have root access(checked from root checker app) and have also enabled USB Debugging. I also inserted cable after getting the message.
Does it take a lot of time(more than 5 mins) to backup imei cause I continued till 5 mins before closing the cmd prompt.
Hope you can help me here.
PS: I am using MIUI v45 global version "JHCCNBH45.0 （V5） " in case if you need.
Click to expand...
Click to collapse
Have you installed the ADB drivers for the 1S? ► ADB Drivers ◄
After installing Run R1SBAR.exe & follow the below screens
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

deadlyindian said:
Have you installed the ADB drivers for the 1S? ► ADB Drivers ◄
After installing Run R1SBAR.exe & follow the below screens
Click to expand...
Click to collapse
Yes, it seems adb drivers were missing after which I was able to successfully backup my IMIE. Thanks for your help.
Perhaps you could add this link in your earlier post as a pre-requisite so that newcomers won't face this issue. Just a suggestion
Kudos and keep rocking.

fanboy_android said:
Yes, it seems adb drivers were missing after which I was able to successfully backup my IMIE. Thanks for your help.
Perhaps you could add this link in your earlier post as a pre-requisite so that newcomers won't face this issue. Just a suggestion
Kudos and keep rocking.
Click to expand...
Click to collapse
Done!!

ASUS ZenPad Z8 (ZT581KL) (P008) (Verizon) - Firmware

I found some firmware files for the Asus Zenpad Z8 ZT581KL for Verizon. Neither Asus or Verizon host any firmware for this device, despite having other similar device firmware available (like the ZT500KL, etc), which sucks.
VZW_ZT581KL_V3.4.16_all_user_M101901_16.0.0_160519.zip
ASUS Factory VZW_ZT581KL_V5.4.1_all_user_M101901_16.0.0_170202 androidhost.ru.zip
ZT581KL_T3.3.8_pre_burn_image_20160516.zip
ZT581KL_Z581KL_EMERGENCY_DLOAD.7z
ZT581KL_FUSE_Security_Keybox_160728.rar
Z581KL_initrd_diff.zip
ASUS.Flash.Tool.v1.0.0.45.zip
Running a stock, factory reset device, I was able to flash VZW_ZT581KL_V3.4.16_all_user_M101901_16.0.0_160519.zip using Asus Flash Tool 1.0.0.45, which successfully downgraded Tablet from V3.4.23 to V3.4.16.
I tried flashing ZT581KL_T3.3.8_pre_burn_image_20160516.zip but it did not work and error-ed out with no brick or anything. Usually the firmware is in a .raw format so you can flash either via zip file which has raw file in root folder of archive, or via the raw file itself. I tried both and was not successful. For some reason this archive had a .bin file instead of a .raw file. I tried renaming them but still didn't work. However, I was able to extract the .bin to find the firmware files inside just like the other version firmwares (that were in raw). One thing I have not tried yet, is to try manually flashing the individual firmware files from the extracted bin, and see if that works--or if someone else with this tablet wants to try, here are the files. If successful, it might lower kernel version down more to allow root exploits to root device.
I have not tried flashing V5.4.1, but I'm confident it will work. I do not know if via the Asus Flash Tool/Asus Tablet will allow doing a flash to V5.4.1 and downgrade back down to V3.4.16, but just did V.3.4.23 (stock orig fw already on device) to V.3.4.16 and it worked. I did receive an OTA to upgrade to V3.4.18 (or was it V.3.4.21, I can't remember) and took the upgrade (then flashed back to V.3.4.16), so it appears that when doing an OTA it will "leap-frog" to the next higher version release until you are on the newest build, so the first OTA you get won't do a direct upgrade from V3.4.16- to V5.4.1 or V5.4.5, but will upgrade it in an incremental way, via the next higher version release.
Hopefully someone can try to root their tablet if any of these files are of any help. I might work up courage to try 3.38 again via manual fastboot, but if you do it and succeed, I would love to hear about it.
The other files hosted ZT581KL_Z581KL_EMERGENCY_DLOAD.7z and ZT581KL_FUSE_Security_Keybox_160728.rar have to do with re-flashing the Qualcomm Snapdragon SoC (un-bricking), and the other one something to do with clearing/setting FUSE when the phone leaves factory or something, I'm not sure. Hopefully they can be of some use to someone to unlock this device. It would be nice. So here u go.
https://www.androidfilehost.com/?w=files&flid=289525 - link to ASUS_ZenPad_Z8_ZT581KL_P008_Verizon files

Has anyone tried flashing 'ZT581KL_T3.3.8_pre_burn_image_20160516' yet? Just wondering if it was successful; I haven't tried it yet.

smokejumper76 said:
Has anyone tried flashing 'ZT581KL_T3.3.8_pre_burn_image_20160516' yet? Just wondering if it was successful; I haven't tried it yet.
Click to expand...
Click to collapse
can you tell me how to extract the .raw from .bin, I will try to flash the device.

fuyangui said:
can you tell me how to extract the .raw from .bin, I will try to flash the device.
Click to expand...
Click to collapse
I used 7zip to extract the firmware from the archive.. Open 'ZT581KL_T3.3.8_pre_burn_image_20160516.zip' with 7zip. It should come up with a folder named 'ZT581KL_T3.3.8_pre_burn_image_20160516'. Go in that folder. There will then be a file shown called 'userdata.bin'. In 7zip, if you right click that file, then select 'Open Inside', it should open inside the .bin file and show the firmware files. From there, you can extract them somewhere. Hopefully, you can try to apply each .img file separately (fastboot), one at a time, and see if it works. Thank you!

Sorry to resurrect this old thread but I might have some info that will help others.
First off thanks for the OP for the download links as I cannot find the OEM ROMS anywhere for this device.
Second here are some more instructions that you may need if you are having issues with this device.
Use ASUS FLash Tool v1.0.0.45, it has the device model that you need and was the one that worked for me. Then download ASUS Factory VZW_ZT581KL_V5.4.1_all_user_M101901_16.0.0_170202 androidhost.ru.zip from the link the OP posted, it should be the first file, then this is the step that I missed and took forever to figure out. You have to open that zip file and extract the .raw file, so you should have a file called ZT581KL_all_VZW_user_V5.4.1.raw. That is the file that you need to select in the Asus Flash Tool by clicking the little box with a down arrow inside it, then boot your tablet into Fastboot (Hold down the Power and Volume Down buttons) then once in fastboot, make sure you select the right model for this tablet it should be, ZT581KL, then I left Wipe Data as no, then connect your tablet to your computer with a USB cable, and you should see your Serial Number and a round icon under the State column. Then once that is all correct click the Start button, you may get an error about some FPS thing that can't be downloaded or something just hit OK, then you should see under the Description column that it's flashing the ROM, wait for a while and you should then have a "Flash Image Successfully (The serial number for your device will show here)" under the description and your tablet will reboot.
My tablet was originally on v5.4.5, this ROM will take you back to v5.4.1 but then through the tablet settings you can do an upgrade to v5.4.4 then do another one and it will be at v5.4.5 then you are all set.
So the issue I was having with the tablet was after a factory reset it would freeze at the setup screen and not let me continue, it took me forever to find out how to get it fixed and the instructions above worked for me, so if anyone else is having similar issues then hopefully this will help. I literally spent days and searched through about 70 forums to try and find a fix for it, I even reached to Asus for help, which they basically told me I had to pay to send it in and have it fixed, I was just about to give up when I came upon this thread and the OP's download links, so thanks again smokejumper76. If anyone has any questions about my instructions feel free to reply/comment.
Thanks!

Downgrade success
I used the files provided by OP and was able to successfully flash from 5.4.1 to 3.4.16. I got this tablet from a friend a few years back that he acquired from his work when it went out of business. It has the frp lock on it and im looking at the few available options. So, since this tablet had been sitting for two years. Its Guinea pig time. I'll flash the 3.3.8 and check back. It seems you can go forward or backward in so versions with the flash tool. So I'm not too worried about brick. If I can just get usb debugging on I'll be gold. Possible exploits if it runs.

Well. The 3.3.8 is not packaged properly for flashing. And that 600mb file expands to 9gb. There is a file "system.img" inside that's roughly the right size as the system and has the correct file structure. I have a friend who is going to help me repack that rom correctly for flashing. Meanwhile I am going to look into the 3.4.16 rom and see if I can't set usb debug to on and flash the modded image. From there I should be able to sideload su. I'll report back.

mofugggz said:
Well. The 3.3.8 is not packaged properly for flashing. And that 600mb file expands to 9gb. There is a file "system.img" inside that's roughly the right size as the system and has the correct file structure. I have a friend who is going to help me repack that rom correctly for flashing. Meanwhile I am going to look into the 3.4.16 rom and see if I can't set usb debug to on and flash the modded image. From there I should be able to sideload su. I'll report back.
Click to expand...
Click to collapse
Any update? Thank you for your efforts!

smokejumper76 said:
Any update? Thank you for your efforts!
Click to expand...
Click to collapse
I have the same tablet as well. Root would be great, any chance of unlocking the BL?

klister said:
I have the same tablet as well. Root would be great, any chance of unlocking the BL?
Click to expand...
Click to collapse
hi
any advance with this?
Enviado desde mi P008 mediante Tapatalk

WHat is the password to the files

I used the emergency download file to unbrick the Japanese version of z581kl. However, maybe the partition structure is different, when I try to write to the system partition, it says that there is no partition. What should i do? I'm sorry for my bad English.

allisondanielle said:
WHat is the password to the files
Click to expand...
Click to collapse
https://www.asusflashtool.com/ - Description Page with Password
Unzip Password: asusflashtool.com

I installed ZT581KL_T3.3.8_pre_burn_image_20160516.zip on my z581kl.
That resulted in Android 6.0 AOSP working!
There is a bug that screen rotation is not possible, but everything else is fine.
There is a bug that the screen cannot be rotated, but other than that, everything is fine. After installing TWRP, you need to mount /system and the location of system.img, and then execute the following command from the TWRP terminal.
mkdir new-system
mount system.img new-system
cp -a -R -p new-system/* /system
Translated with www.DeepL.com/Translator (free version)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

清水侑磨 said:
I installed ZT581KL_T3.3.8_pre_burn_image_20160516.zip on my z581kl.
That resulted in Android 6.0 AOSP working!
There is a bug that screen rotation is not possible, but everything else is fine.
There is a bug that the screen cannot be rotated, but other than that, everything is fine. After installing TWRP, you need to mount /system and the location of system.img, and then execute the following command from the TWRP terminal.
mkdir new-system
mount system.img new-system
cp -a -R -p new-system/* /system
Translated with www.DeepL.com/Translator (free version)View attachment 5251235View attachment 5251237View attachment 5251239
Click to expand...
Click to collapse
I flashed the zt581kl image using EDL mode as described in this blog because the partition structure of the zt581kl is different from that of the zt581kl.
z581klでEDLモードに入る方法
xxxxx
itgameinfo.blogspot.com

Hi. New to the forum. I’m looking to downgrade my asus zt581kl so that I can root. Can someone show me the exactly step by step to downgrade my table? The above replies are a bit confusing to follow.

Tmupt said:
Hi. New to the forum. I’m looking to downgrade my asus zt581kl so that I can root. Can someone show me the exactly step by step to downgrade my table? The above replies are a bit confusing to follow.
Click to expand...
Click to collapse
Maybe start here:
https://www.getdroidtips.com/v5-4-1-nougat-verizon-asus-zenpad-z8/

I've been messing around with some of the files, and I was able to brick and unbrick the device following the firehose SOP PDF instructions. It basically flashes a barebones boot w/o any OS, and you have to flash a complete firmware to it to restore it back.
I was also able to install TWRP but it showed 0 space avail, I think because I didn't wipe it. I'll play with that later.
Used these links (use google translate)
z581klでEDLモードに入る方法
xxxxx
itgameinfo.blogspot.com
zenpad 3 8.0に簡単にTWRPを導入する+fastbootの裏技
xxxxx
itgameinfo.blogspot.com
I need to ask @清水侑磨 about how to flash ZT581KL_T3.3.8_pre_burn_image_20160516.zip. I think the userdata.bin file is a NAND dump created by Chinese Miracle 2 / Infinity Box but I'm having problems getting it to read the partitions. I was able to get the tablet in EDL mode, so I'm not sure what I'm doing wrong.

Anyone have a QPST .QCN file for ZT581KL for this device? Flashing 3.3.8 from that preburn file will nuke your IMEI. Mine got changed to all 1s and lost provisioning connectability w/ carrier. in fastboot/adb, so I need to restore it. If anyone could make a QCN (with your IMEI removed of course) so I can do that I would be most appreciative.

smokejumper76 said:
I've been messing around with some of the files, and I was able to brick and unbrick the device following the firehose SOP PDF instructions. It basically flashes a barebones boot w/o any OS, and you have to flash a complete firmware to it to restore it back.
I was also able to install TWRP but it showed 0 space avail, I think because I didn't wipe it. I'll play with that later.
Used these links (use google translate)
z581klでEDLモードに入る方法
xxxxx
itgameinfo.blogspot.com
zenpad 3 8.0に簡単にTWRPを導入する+fastbootの裏技
xxxxx
itgameinfo.blogspot.com
I need to ask @清水侑磨 about how to flash ZT581KL_T3.3.8_pre_burn_image_20160516.zip. I think the userdata.bin file is a NAND dump created by Chinese Miracle 2 / Infinity Box but I'm having problems getting it to read the partitions. I was able to get the tablet in EDL mode, so I'm not sure what I'm doing wrong.
Click to expand...
Click to collapse
Sorry for the late reply.
To boot AOSP, instead of burning the system.img from edl or fastboot, use adb.
The method is as follows
1、Start TWRP.
2、Connect your PC to USB.
3、Go to the directory where system.img is located, and press
adb push system.img /sdcard/
4、Enter the shell
adb shell
5、Mount system.img.
mkdir new-system
mount system.img new-system
6、Copy the contents of the mounted system.img to the system partition.
cp -a -R -p new-system/* /system
(If this fails, check that the system partition is mounted. If the system partition is mounted but you cannot write to it, format the system partition.)
7、After rebooting, you should see an Android message
Translated with www.DeepL.com/Translator (free version)