Jump to content


Photo

58 mb update

- - - - -

  • Please log in to reply
29 replies to this topic

#21
Darael

Darael

    Newbie

  • Members
  • Pip
  • 26 posts
  • Gender:Male
  • Devices:San Diego: Xolo ICS
  • Twitter:@Meliral

Oh, hells yes.

 

I have just regained root after applying the 58mb patch.

 

I should note that I do *not* have insecure adbd working fully; checking the first box fails, saying it can't patch adbd. The second works fine, and it is automatically granted superuser permissions on launch.

 

So eu.chainfire.adbd might need an update, but I have a functioning /system/xbin/su and Superuser and I am very happy with this.

 

Method follows:

  • "Update" from USB (id est, not OTA; use the 299MB update.zip.  You know the one by now.) to stock ICS.
  • Root with the usual AIO tool.  Follow the instructions, and wait for the various reboots.
  • adb shell:
    su
    mount | grep /config
    #check what device is /config.  For me it was /dev/mmcblk0p5, and that's what I'll use here, but I don't want to risk it being different for anyone else
    mount -o remount,rw /dev/mmcblk0p5 /config #change device if appropriate
    mkdir /config/reroot
    cp /system/xbin/su /config/reroot/
    exit
    exit
    

    And then install the 58MB patch

  • adb shell:

    /config/reroot/su
    #The following lines stolen shamelessly from root_me.sh (with "./adb shell" stripped, since we're already in an adb shell to work around lack of insecure adbd)
    mount -o remount,rw /dev/block/mmcblk0p2 /system
    chmod 06755 /system/xbin/su
    chmod 655 /system/app/Superuser.apk #I confess I didn't check if this and the next line were necessary, but they do no harm, so...
    chmod 755 /system/xbin/busybox
    #OPTIONALLY: remount /config read-write and remove the backup copy of su.  There's plenty of space in there, though, so it's hardly critical.
    

  • 2

#22
BlueMoonRising

BlueMoonRising

    Hardcore

  • Members
  • PipPipPipPipPipPip
  • 1,523 posts
  • Gender:Male
  • Location:Here, there and everywhere...
  • Devices:Orange San Diego, OSF

I'm not a dev so some of what you are saying was a little bit 'whoosh' over my head but do you now have a fully patched Xolo rom WITH root? If so well done  :) . Have you or can you enable the SD slot?


  • 0
Whoever exalts himself will be humbled, and whoever humbles himself will be exalted.

Matthew 23:12

#23
Darael

Darael

    Newbie

  • Members
  • Pip
  • 26 posts
  • Gender:Male
  • Devices:San Diego: Xolo ICS
  • Twitter:@Meliral

Basically, yes.  I think so.  Certainly I have a patched Xolo ICS with the capacity to do things as root; whether or not it yet works in the way we'd expect of a rooted phone I have yet to determine.


  • 0

#24
karthiknr

karthiknr

    Regular

  • Members
  • PipPip
  • 106 posts
  • Gender:Male
  • Location:India
  • Devices:ZTE Blade,Xperia S,OSD

When you flash the 299 MB update.zip,won't the screen start flashing colours?


  • 0

#25
Darael

Darael

    Newbie

  • Members
  • Pip
  • 26 posts
  • Gender:Male
  • Devices:San Diego: Xolo ICS
  • Twitter:@Meliral

When you flash the 299 MB update.zip,won't the screen start flashing colours?

Yes, but a) adb still works if USB debugging was enabled beforehand, and B) I used the HDMI output (which still works mostly when that happens) to see what I was doing.  Once I installed the 58MB patch, the screen worked normally again (as expected).

 

(when I say the HDMI output works mostly, I mean the usual issue of the device thinking it's rotated by 90 degrees (but with the touchscreen acting as though it were displaying normally).  Takes a bit of getting used to, and it helps to enable showing touch positions and/or events beforehand, so they act as a guide on the external screen, but it works.)


  • 1

#26
karthiknr

karthiknr

    Regular

  • Members
  • PipPip
  • 106 posts
  • Gender:Male
  • Location:India
  • Devices:ZTE Blade,Xperia S,OSD

Yes, but a) adb still works if USB debugging was enabled beforehand, and B) I used the HDMI output (which still works mostly when that happens) to see what I was doing.  Once I installed the 58MB patch, the screen worked normally again (as expected).

 

(when I say the HDMI output works mostly, I mean the usual issue of the device thinking it's rotated by 90 degrees (but with the touchscreen acting as though it were displaying normally).  Takes a bit of getting used to, and it helps to enable showing touch positions and/or events beforehand, so they act as a guide on the external screen, but it works.)

I managed to do it using HDMI but i enabled the Show Touches option in the Developer Settings menu which helped a lot.

It works but it doesn't seem to give any root access to applications. It's like it's there but it doesn't do anything.

Great work though! :)


  • 0

#27
karthiknr

karthiknr

    Regular

  • Members
  • PipPip
  • 106 posts
  • Gender:Male
  • Location:India
  • Devices:ZTE Blade,Xperia S,OSD

Also,the 58MB update obviously has something to do with the video of the device,so can we intercept the download into a file and check if we can add the graphics files using root later to get the display to work?


  • 0

#28
karthiknr

karthiknr

    Regular

  • Members
  • PipPip
  • 106 posts
  • Gender:Male
  • Location:India
  • Devices:ZTE Blade,Xperia S,OSD

I got root access to work properly by copying the su and busybox to /system/bin/ instead of /system/xbin/


  • 0

#29
Darael

Darael

    Newbie

  • Members
  • Pip
  • 26 posts
  • Gender:Male
  • Devices:San Diego: Xolo ICS
  • Twitter:@Meliral

I managed to do it using HDMI but i enabled the Show Touches option in the Developer Settings menu which helped a lot.

It works but it doesn't seem to give any root access to applications. It's like it's there but it doesn't do anything.

Great work though! :)

 

Yeah, I encountered that.  That's most of the reason I posted that it was possible to get a working su, actually: I figured someone here would probably be able to work out how to get from there to appspace root.

 

Also,the 58MB update obviously has something to do with the video of the device,so can we intercept the download into a file and check if we can add the graphics files using root later to get the display to work?

 

I haven't a clue.  Is there a known way of intercepting an OTA update?  I'm willing to use such a thing and host the result myself.  Answers on a postcard.

 

EDIT: a wee bit of googling suggests that I should be able to find it somewhere in /cache... which makes sense.  I'll have a poke around, but the request for automatic tools stands, because I like it when things make my life easier :-P

 

I got root access to work properly by copying the su and busybox to /system/bin/ instead of /system/xbin/

 

Oh, sweet.  Good going.  Thanks for letting us know!


Edited by Darael, 12 February 2014 - 07:23 PM.

  • 0

#30
Darael

Darael

    Newbie

  • Members
  • Pip
  • 26 posts
  • Gender:Male
  • Devices:San Diego: Xolo ICS
  • Twitter:@Meliral

Having tried to enable the external SD card slot, I have found the following:  Enabling it works fine.  Enabling mass storage seems to work fine.

 

Stage 3, however (enabling both at once) bootloops the phone after the update is applied.  Trying to do it after applying the update and regaining root just bootloops it at next boot.  I think we'll need an updated framework-res.apk to fix that, though I'm not completely sure.

 

I have yet to try swapping the SD card and internal storage, but mMy experiments confirm for anyone interested that SDXC cards are supported (Before updating I was able to use a 64G MicroSDXC card).  That last bit should probably go in a more relevant thread, come to think of it.

 

Update: swapping the card with the internal storage works just fine.


Edited by Darael, 17 February 2014 - 09:09 PM.

  • 1




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users