Darael

Members
  • Content count

    26
  • Joined

  • Last visited


Community Reputation

12 Good

About Darael

  • Rank
    Newbie

Previous Fields

  • Your Current Device(s) San Diego: Xolo ICS
  • Your Twitter username Meliral

Darael's Activity

  1. Darael added a post in a topic [SOLVED] Problem of screen flashing different colors after flashing update.zip after installing 37mb or 12mb update on xolo ICS rom!   

     
    If you don't have an HDMI cable and suitable screen, you can still use this method to update and get your screen working again, as long as you have fastboot (from the Android SDK) on your computer - boot the phone into fastboot (turn it on with vol-down held and keep holding both power and vol-down for several seconds after it powers on - the screen will do the same thing as always but behind the scenes it's entering fastboot mode instead of Android proper), connect it to the computer via USB, and then use "fastboot -i 0x8087 flash update /path/to/58M/update.zip" to do the update.  If it hangs on "<waiting for device>", ensure fastboot is running with access to the phone - easiest way is to run it from an administrative command prompt (windows) or with sudo (osx/linux).  If it still hangs there, the phone isn't in fastboot mode.  Turn it off and try entering fastboot again.  No need to disconnect from USB or interrupt the command; it'll go as soon as the phone is ready.
    • 0
  2. Darael added a post in a topic [SOLVED] Problem of screen flashing different colors after flashing update.zip after installing 37mb or 12mb update on xolo ICS rom!   

     
    I never did mention in this thread, did I?  You can do the two things with the SD card that involve vold.fstab (enable, mounted at /mnt/sdcard_ext, but not shown in Storage; enable, switched with the internal storage, mounted at /mnt/sdcard and shown in Storage but the internal storage is at /mnt/sdcard_ext as the other), but the one that would make the slot behave as on devices where the manufacturer allows its users access doesn't work, because modifying /system/framework/framework-res.apk bootloops the phone.  With a large enough SD card (and I can confirm SDXC is supported, because I'm using a 64G one myself) effectively-no-access to the internal storage at /mnt/sdcard_ext becomes a non-issue.
    • 0
  3. Darael added a post in a topic 58MiB Update: What You Need To Know   

    I've made a little progress on the SD cards, and also some on the screen-not-working-after-downgrade, but unfortunately not a lot.
     
    This is what I know about the cards:
    The mod to enable both cards modifies two APKs: the MediaProvider, and framework_res. The latter of these is the fundamental framework APK for the whole system The main change in this file is to /res/xml/storage_list.xml The change is not quite what it should be in any case I can decompile the 65M-patched version with apktool I cannot recompile this file even without altering the decompiled version because ant complains about some things in the plurals files I can make the changes to these that were also made in the mod. This allows me to recompile the apk with apktool, even if I change storage_list.xml as well Pushing this new modded framework_res.apk causes a bootloop from which I have to use recovery to downgrade-sidegrade-upgrade-reroot. Presumably the updated system is checking the certificate used to sign framework_res.apk  
    Now for the screen:
    Using the AIO tools to change the video libs does not seem to fix the problem I adb pulled /system after downgrading and compared it to /system in the Xolo stock update.zip with diff Only a few files differed All of these were files that existed in the post-downgrade system and not the dump All of those were libraries with filenames that ended in .so where the dump only had versions with .so.majorversion.minorversion (or some similar scheme) removing these libraries did not fix the screen From this I conclude that the problem is not caused by a change to anything in /system.
    • 0
  4. Darael added a post in a topic Re-root after 37MB updated.   

    I've been using a slightly different method, which will work whether you use the Xolo ROM or the Orange one, and has a couple of advantages:  Firstly, the only files it needs that we don't already use as part of the AIO tool's functionality are the official patch update.zips, and secondly, once you've got it set up it becomes a one-line ADB command to re-root the phone, whatever it may be running.
     
    Originally I was only able to get this to work for Xolo, because I couldn't manage to flash my phone back to Orange ICS, but I've since had a handset replacement under Orange Care because the capacitative layer of the screen - but not the top glass layer or the actual display underneath - cracked so that most of the surface was unresponsive to touch, and the new one went back to Orange without problem.  As a result, I also have a copy of the 65MiB update.zip which takes Orange stock ICS to the latest patch, pulled with adb.  For anyone interested, the update.zip is downloaded to /cache/fota/ipth_config.bin and kept there until it's applied - this may be useful in case of future updates.
     
    Anyway, you don't care about that so much as you want to know what to do.  You will need your phone to be rooted before we begin, which may require a downgrade and the use of a µHDMI cable.  Having done the setup, though, you can downgrade or upgrade at will, because even if you can't see what's happening you can root the phone, and you can use "adb reboot-bootloader" and fastboot to patch so you get your display back.
     
    The procedure is as follows:
    Root device.  Doesn't matter what version it's running at this point, so long as it's rooted. adb push this shell script (someone mirror this, please?  I can handle the bandwidth but don't want it to go unavailable if my box goes down) to /data/local/tmp (or other location of your choice, in which case adapt the below appropriately) Get an ADB root shell.  Be that with insecure ADB, adb shell then su, whatever, I don't care.  Then run these:
    #/config is the partition other than /system which *isn't* mounted nosuid noexec #and updates leave it alone, so we exploit this and stash our su, Superuser, and busybox here #we can't use adb remount because it's not /system mount -o remount,rw /config mkdir /config/reroot # the subfolder is just for neatness #This assumes su and busybox are in /system/bin. They may be in /system/xbin, and if so, adjust accordingly. #After patching they'll need to be in /system/bin but we'll get to that cp /system/bin/su /system/bin/busybox /system/app/Superuser.apk /config/reroot/ #the usual mv binary fails across partition boundaries but busybox mv doesn't busybox mv /data/local/tmp/do-reroot.sh /config/reroot/ #these next shouldn't strictly be necessary but don't hurt #except for the chmod on the script, that's important chown -R root.root /config/reroot chmod 755 /config/reroot/busybox /config/reroot/do-reroot.sh chmod 644 /config/reroot/Superuser.apk chmod 6755 /config/reroot/su #clean up mount -o remount,ro /config Update in whatever manner you wish.  I pulled the patch update.zip, so my preferred procedure is "adb reboot-bootloader" followed by "fastboot flash update [...]/updatezips/65M/orange/update.zip but you can do whatever you like. run the following magic command from your computer: "adb shell /config/reroot/su -c /config/reroot/do-reroot.sh". Strictly, the script isn't needed, but I wrote it to save myself time given that my experiments with getting both the SD card and the internal storage properly active at once have involved a fair number of bootloop-downgrade-upgrade-reroot cycles.  All it does is copy the three other files into the right places, relying on it being run with elevated permissions thanks to the copy of su to give it the access it needs.
     
    I also have a script that does all the above automatically (downgrades to Xolo-stock, roots if this setup hasn't been done before, sets up the above, does the Orange sidegrade, updates, re-roots), but it's written in bash (sh-compatible save for the presence of a pushd and a popd) and my Windows-batch is rusty enough that I have no idea how to translate it.  PM me for a copy; I've tried to encapsulate procedures in functions so as to make it more extensible (and also easier to do things like cut out the Orange sidegrade)
    • 1
  5. Darael added a post in a topic 58MiB Update: What You Need To Know   

    Ooh!
     
    While this is an interesting exercise, I've just discovered that I *do* in fact have a backup copy of the 58M update.zip, which I shall upload to the dead server's replacement at the same address (which is http://darael.tpchq.org/SanDiego/updatezips/58MiB-patch/xolo/update.zip - just to save you a trip back to the top) immediately.
    • 0
  6. Darael added a post in a topic 58MiB Update: What You Need To Know   

     
    Hmm.  That, according to my command history, is definitely what I used - and I'm pretty sure I wasn't rooted when I got it.  Besides, I'd expect an "access denied" message rather than a "does not exist" one if it needed root access.
     
    Perhaps try using "adb shell" to see what's in /cache/fota?  I'd suggest using "busybox ls -lh /cache/fota" if busybox is in place, as this'll show file sizes in a more-easily-human-readable form.
     
    If there's nothing of a likely-looking size there, then frankly I'm stumped.
    • 0
  7. Darael added a post in a topic 58MiB Update: What You Need To Know   

    Unfortunately, the machine on which I was mirroring those files had a total hard drive failure two days ago, and the SanDiego files are not in my most recent backup set.
     
    This *sucks*.
     
    I can, however, tell you that if you download the OTA update, then before you install it the update.zip file will be on the phone as /cache/fota/ipth_package.bin and can be retrieved with adb pull (I used "adb pull /cache/fota/ipth_package.bin 58M-update/xolo/update.zip" because I thought I might go and get the Orange one at some point, but you can put whatever path you like for the destination, though I suggest making the filename part update.zip).  Yes, it's got a .bin extension, but run "file" on it and you'll see that it *is* a zip archive.  Note that after actually installing the update it'll be deleted from the phone, so there's quite a small window in which to get it.
     
    If you can get it in this way, I'm happy to host it on the replacement machine at the same address for anyone else who wants it.
    • 1
  8. Darael added a post in a topic Bootloop/Blank screen Problem. Need help.   

    Given the mention of using Ubuntu, I suggest running "adb kill-server" rather than trying to find a task manager.  Alternatively, "killall adb".
    • 0
  9. Darael added a post in a topic Bootloop/Blank screen Problem. Need help.   

     
    Yeah, the vendor ID we need to use is 8087, which we pass with the '-i 0x8087' flag.  'fastboot devices' won't return anything unless the device is actually in the bootloader at the time (hence the mention of holding the vol- key when powering it on), and under Linux I've found that fastboot works most reliably across different distros if run as root.
    • 0
  10. Darael added a post in a topic Bootloop/Blank screen Problem. Need help.   

    Can you access fastboot by powering it on with the vol- key held?  If all else fails you will then be able to use fastboot to flash the 299MiB update.zip.  Sure, you'll lose a whole lot of settings, but at least you'll have a working phone.
    • 0
  11. Darael added a post in a topic root after 58 mb update   

    You may be able to fix it by using fastboot to flash Xolo stock ICS (which is what the "Fix brick" option in the AIO tools does) - it's possible that you'll need to erase the cache to make that work ("fastboot -i 0x8087 erase cache" while the phone's in the bootloader).
    • 0
  12. Darael added a post in a topic 58MiB Update: What You Need To Know   

    Well, I've heard mention of the update solving certain issues with overheating, but otherwise no, I don't know of any. It would help if we knew exactly what the update changed and why.
    • 0
  13. Darael added a post in a topic root after 58 mb update   

    Just in case you weren't following:  We now know it's possible to regain root after updating to 58MiB, but not without downgrading as an intermediate step (or having prepped first).
     
    Details in this thread.
     
    I have no news on USB OTG, though.  Sorry.
    • 0
  14. Darael added a topic in Orange San Diego Development   

    58MiB Update: What You Need To Know
    Some of the information below also applies to the 37MiB update, but I have no idea what, so don't ask me.  Do, however, feel free to give any extra information you have regarding the 58MiB patch.
     
    It is not possible to use the AIO tool to root your phone while the 58MiB patch is applied. It is possible to downgrade by flashing the 299MiB update.zip, but this tends to mess up the screen, needing an HDMI cable to actually do anything Both recovery from this state and obtaining a 58MiB-patched rooted OSD are possible, and that is the subject of the next part of this post.  
    Recovery from the flashing-screen state is probably easiest to do by using fastboot to apply the 58MiB patch.  This is the method I'm going to suggest, but it's also doable by changing the GPU drivers in use (which has the advantage that it's not necessary to apply the dreaded patch) or by using HDMI output to OTA-upgrade (which has the advantage of not needing to have fastboot installed on your PC).  That said, the purpose of this post is to provide information about the patch, so that's the only method we'll discuss here.
     
    THIS IS SLIGHTLY TECHNICAL, but frankly I don't think the rooted 58MiB-patched version of the ROM is ready for use by those who can't handle a bit of technical stuff yet (and if you disagree, feel free to update the AIO tools and drop me a link so I can put it in my mirror of such things).
     
    IF YOU ARE A NON-TECHNICAL PERSON, STICK TO STOCK ICS (with as many changes using the AIO tools as you like)
     
    So, to obtain a patched-yet-rooted phone (the same principle, adjusted as appropriate, should work for the 37MiB patch (but why would you bother?)):
    Gather your tools: Ensure that you have both adb and fastboot installed on your PC.  As mentioned, I'm writing for a relatively-technical audience, so I'm sure you can work out how.  Bear in mind that fastboot will need the "-i 0x8087" option and under Linux may need to be run as root.  If your phone is in the bootloader and fastboot still hangs on "<waiting for device>", try running it as root. Make sure you have both the Xolo stock ICS 299MiB update.zip and the corresponding 58MiB update.zip.  Both can be found on my server at http://darael.tpchq.org/SanDiego/updatezips/ if you don't have them already .  Unfortunately my mirror suffered a hard drive failure and I no longer have these files.  See post 7 in this thread for another way to get the 58M update.zip.  The former you'll only need to get back to stock if you aren't there already, but hey, it can't do any harm (unless you really can't afford to download 299MiB) Disable anything you applied with the AIO tool that is listed in this post's final section as not working with the patched ROM.  Fail to do this and you will be stuck in a bootloop and have to use fastboot to get out of it - if you find yourself in that situation, follow the advice on doing this whole thing a second time, hidden in my explanation for the use of fastboot in Step 5. Back everything up.  You shouldn't need to, but it's safest, just in case anything goes wrong. Enable USB debugging.  If you haven't done that automatically knowing what we're doing... shame on you. The next two steps can be skipped if you run through this process a second time (or more) on a given phone, as the changes made will persist pretty much whatever you do to it. Now you need a root ADB shell.  If you've applied the 58MiB update, then the first time you do this you'll need to downgrade and use the AIO tool to change the graphics drivers in use, or use an HDMI display to re-root.  Sorry.  There are guides elsewhere on this forum. Having obtained a rooted, stock-ICS phone, you can begin your prep.  su and busybox are in /system/xbin/.  You're going to need spare copies of these, because the 58MiB update will remove the suid and sgid permissions from su and may delete busybox.  As such, you need to stick copies somewhere that a) doesn't ignore suid and B) won't be overwritten by the update.  A quick look at the output of "mount" on the phone suggests /config is a good bet (and it is.  I tried it.  It works.).  Problem is, it's mounted read-only.  As such, we'll need to remount it.  I'll give the command to do that in a sec, but first:  The next thing is to make a new directory in /config - I'll call it reroot - and finally to copy su and busybox there.  The commands, in that order (with remounting /config read-only at the end for neatness) are as follows: mount -o remount,rw - /config mkdir /config/reroot cp /system/xbin/su /system/xbin/busybox /config/reroot/ mount -o remount,rw - /config It's time to apply the update.  We're going to use fastboot rather than anything while the phone is booted, because it's much easier the second and later times one runs through this process due to not needing the screen to be usable (fastboot "update" to stock, use adb to reboot to the bootloader, fastboot to apply the patch).  Now, you can get the phone into the bootloader by powering it off, then on while holding the volume-down button, sure, but there's an easier way.  Issue "adb reboot-bootloader" on your computer.  This will also work if the dash is replaced with a space. Now that you're in the bootloader, flash the update.  I'm going to use /path/to/58M/update.zip as a shorthand, but if you're on Windows then you need to use Windows-style paths with backslashes and a drive letter if appropriate... obviously.  This is done as follows: "fastboot -i 0x8087 flash update /path/to/58M/update.zip" The phone should reboot, and you'll be in a fully-functional (but unrooted) patched ICS.  If you get bootlooped instead, you applied some mod or other that disagreed with the patch.  Use fastboot as above to revert to stock ICS, then immediately again to patch it - YOU DO NOT NEED TO REDO STEPS 1-4, which means you also do not need to be able to see what you're doing as you can use adb to get into the bootloader since USB debugging should still be enabled.  After we're done here you can apply the mods from the tool one at a time to see which caused the bootloop, and get back to me so I can add it to the incompatible-mods list. Finally, it's time to regain root.  Here's how.  First, get an adb shell.  It won't be a root shell but that doesn't matter right now.  Then issue the following commands: /config/reroot/su #this should work, and the last character of the prompt change to # - you're acting as root mount -o remount,rw - /system #mount /system read-write cp /config/reroot/su /config/reroot/busybox /system/bin #note NOT /system/xbin. Don't know why but that no longer works. reboot #not strictly necessary but does no harm and keeps things clean exit #you may or may not get the chance before the reboot terminates the shell anyway exit #see above (first exited su, second exited adb shell) Be aware that you can skip everything past the hash (#) in those lines *or* leave it in.  They're comments and will have no effect either way.
    Your phone will reboot.  Congratulations; you have a rooted 58MiB-patched phone, and root-using apps should work fine (including insecure ADB, SuperUser, &c.). Now, three more things and then I'll shut up for a bit.
     
    Firstly, some of the options in the AIO tool are irrelevant to a phone in the state we've just got to - rooting, especially, would be kind of pointless since it's already rooted.  Don't bother!  I'll mention others
     
    The following options from the AIO tool are confirmed to work on a rooted phone with the 58MiB patch - if something's not listed here or in the next list I for one would be grateful if someone would try it out and see whether or not it works:
    Brick-fixing (of course; it works regardless of the ROM on the phone.  Just uses fastboot.) Reverting to stock Xolo Flashing boot logos Enabling the µSD card slot Swapping the internal storage and the card in the µSD slot Probably others.  More testing needed. The following I know NOT to work after applying the 58MiB patch and rerooting (and if anyone wants to provide fixes, I am happy to host them, but dev discussions should probably go in the main dev thread, or threads of their own, rather than here):
    The "enable both SD card" option.  This WILL bootloop the phone.  Personally I suspect framework-res.apk rather than MediaProvider.apk to contain the conflict but I haven't the skill to prove anything. Probably others.  More testing needed.
    • 11 replies
    • 1373 views
  15. Darael added a post in a topic [share] Non-bandwidth-limited source for update.zip files   

    At some point I shall bother telling Apache to be case-insensitive on those paths, but until then remember that SanDiego is capitalised.  I've seen a couple of failed downloads in my logs because of that.
    • 0

MoDaCo is part of the MoDaCo.network, © Paul O'Brien 2002-2015. MoDaCo uses IntelliTxt technology.