January 22, 2018, 06:14:37 PM

collapse

* 'Like' And 'Follow' Us!

* Le Pan Market

If you like LePanForum.com please consider making a small donation to help keep our site free.

Author Topic: ROM developement  (Read 3546 times)

Rabid1

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 724
  • Popularity: 32
    • View Profile
ROM developement
« on: April 03, 2014, 07:46:20 PM »
So after soft bricking 2 TC802a I decided to take a break. All of the things that should have worked didn't I can pull the boot.img edit it and push it back. And it dies with no edits.

I was working with a bunch of other people on the Venue 8 when  it hit me why the Mini won't flash even an unmodified boot.img. It uses the same partition system. Basically bootloader recovery and bootimg take the same partition then are emulated on smaller partitions. Not sure if that is the best description but it's close. Dell released the developer version of their software which does a system edit so that they become flashable through fastboot individually. I have found similar toolts for the MTK processor in the Mini. I have got it to see the device a couple of times but it is tricky. Something is missing on the Mini that allows the software to dump the stock firmware but I may be able to make it flash a modified system image.

So that is where we are at. If I brick another I am pretty sure they won't replace it. LOL

sgschwend

  • Newbie
  • *
  • Posts: 45
  • Popularity: -1
  • Model II, and S
    • View Profile
Re: ROM developement
« Reply #1 on: April 04, 2014, 07:19:34 PM »
Do you mean this is a locked bootlaoder? So that an image change even a copy image requires a unique new key?
Steve,

Rabid1

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 724
  • Popularity: 32
    • View Profile
Re: ROM developement
« Reply #2 on: April 04, 2014, 07:41:50 PM »
Do you mean this is a locked bootlaoder? So that an image change even a copy image requires a unique new key?

No, it's the partitioning. A normal device has boot at something like /dev/block/XXXXX0 then recovery at /dev/block/XXXXX01 etc... This device hae kernel, boot, and recovery all on dev/block/mmcblkp0 then emulate /dev/block/ addresses for boot and recovery. Without the offsets we can't edit the boot.img and reflash it.

sgschwend

  • Newbie
  • *
  • Posts: 45
  • Popularity: -1
  • Model II, and S
    • View Profile
Re: ROM developement
« Reply #3 on: April 05, 2014, 06:29:45 PM »
A hard coded method, in this day an age?
A first year programer would never do this.
Steve,

Rabid1

  • Global Moderator
  • Hero Member
  • *****
  • Posts: 724
  • Popularity: 32
    • View Profile
Re: ROM developement
« Reply #4 on: April 09, 2014, 11:47:53 AM »
I am trying to find out how to build a "scatter" file for MTK tools. That is what is missing, or at least part of what is missing for the mini to use these tools..

thanoseid

  • Newbie
  • *
  • Posts: 2
  • Popularity: 0
    • View Profile
Re: ROM developement
« Reply #5 on: December 16, 2017, 02:54:54 AM »
Actually.. You, all 3 are wrong..  4.2.2 is basically 4.3 (touchwiz)  and if you understand what I just said then you understand that A-boot is going to be the only option basically. (safestrap)the bootloaders are locked, but that is not the main issue..  The main issue is that the boot.img etc,  is all on one partition. Making it impossible to flash a custom recovery the usual way. An e'en I've ttried going as far as writing my own twrp..  To no avail..  And every damn thing is write protected / signed.  So yes, in a way the op is thinking right,  just not Broad enough.  I can say this..  If anyone is brave enough to do it......  Odin flash Phil's touch recovery and once it's flashed (make sure autoreboot is off)  power down the device,  then manually boot into recovery and it should give the option for Phil's recovery.  Now the real work is going to come in figuring out what parts of the build to edit...  Ro.debuggable=1 system.secure=0 I'm not TELLING you to go change the USB abilities or build defaults or such..  I'm not saying you should...  I'm not responsible if you were to. Figure it out...  Have a great day...