• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Public Mobile

also if you know how to tell one mbn file from the other, that might be extremely helpful for people that have accidentally flashed warp roms, i think that was all we needed was the proper mbns to make that flashing tool work with the diagnostic mode that causes the phone to be stuck in
 
P8 on the og warp is adsp.mbn and to be honest I have no idea what that is... But amss.mbn is the radio on the og warp and unless ZTE threw us a curve ball and named something completely different amss.mbn, mmcblk0p9 is radio on both devices.. dbl.mbn is bootloader on mmcblk0p1 and that is the extent what i am sure of... the rest i refer to as firmware... EMMCBOOT.MBN is not present on the N861 instead there is a appsbl.mbn on mmcblk0p11... I suspect this is part of the bootloader as well on both devices... apart from that the parttions are pretty similar between the two models...
 
that works, we need to figure out which ones would be necessary for that flasher tool so people can fix their phones from a brick
 
What flashing tool were you referring to? I just realised my phone still has dfu mode... and I'm getting the info from the jb ota package script and if you look in the patch folder you will see the files i speak of... i will post the names above where they go tomorrow if you want...
 
SuperR said:
Sweet, thank you!! What are you using to extract/mount the partitions?
Click to expand...

he doesn't extract or mount them, he's trying to say in the OTA updater zip you can easily see which partition is which from the updater-script and by looking through the files in the zip.

For example:


[HIGH]ui_print("Patching adsp image...");
apply_patch("EMMC:/dev/block/mmcblk0p8:5617480:f09ea472961147424d430e97efd35f5dab08a5c3:5601608:4c02b3c5d7db624f3112ab6cebbeba7c64678a75",
"-", 4c02b3c5d7db624f3112ab6cebbeba7c64678a75, 5601608,
f09ea472961147424d430e97efd35f5dab08a5c3, package_extract_file("patch/adsp.mbn.p"));[/HIGH]


from the script you can see that adsp is partition number 8 aka mmcblk0p8. See what he's saying? i thought you knew that while trying to get the jb partitions the other day lol. Anyway yeah thats how most devs finds out what partition is what/does what, through Official OTA updater-scripts. Which is why i kind of hesitate to flash other phones partitions other than my own cause even though we have the name for them in the zip, we dont know what the hell they do lol I remembered an old friend and amazing dev interdpht was working on getting new update rooted on to everyones Transform UItra, he ended up flashing some else IMED partition which automatically gave him the other persons IMEd number haha. In the end he never backed it up which caused him to buy a new ultra
 
chevanlol360 said:
he doesn't extract or mount them, he's trying to say in the OTA updater zip you can easily see which partition is which from the updater-script and by looking through the files in the zip.

For example:


[HIGH]ui_print("Patching adsp image...");
apply_patch("EMMC:/dev/block/mmcblk0p8:5617480:f09ea472961147424d430e97efd35f5dab08a5c3:5601608:4c02b3c5d7db624f3112ab6cebbeba7c64678a75",
"-", 4c02b3c5d7db624f3112ab6cebbeba7c64678a75, 5601608,
f09ea472961147424d430e97efd35f5dab08a5c3, package_extract_file("patch/adsp.mbn.p"));[/HIGH]from the script you can see that adsp is partition number 8 aka mmcblk0p8. See what he's saying? i thought you knew that while trying to get the jb partitions the other day lol. Anyway yeah thats how most devs finds out what partition is what/does what, through Official OTA updater-scripts. Which is why i kind of hesitate to flash other phones partitions other than my own cause even though we have the name for them in the zip, we dont know what the hell they do lol I remembered an old friend and amazing dev interdpht was working on getting new update rooted on to everyones Transform UItra, he ended up flashing some else IMED partition which automatically gave him the other persons IMEd number haha. In the end he never backed it up which caused him to buy a new ultra
Click to expand...

one thing tho is in the ots package the files are in patch form but I was wondering... the jb update is not available through the ZTE ugrading tool? the package sent through the ugrading tool has more info...
 
smartmanvartan said:
one thing tho is in the ots package the files are in patch form but I was wondering... the jb update is not available through the ZTE ugrading tool? the package sent through the ugrading tool has more info...
Click to expand...

You could by possibly switching your build.prop with our b9 build.prop which should automatically get the ota update since that's how you get it. Through the updater tool its different. It checks more than just the build.prop it checks partitions too.
 
chevanlol360 said:
You could by possibly switching your build.prop with our b9 build.prop which should automatically get the ota update since that's how you get it. Through the updater tool its different. It checks more than just the build.prop it checks partitions too.
Click to expand...

correct the updating tool checks the bootloader... I know because on the N860 for Public we had a different bootloader and I needed a copy of the boost mobile bootloader for some tests. I wanted the b10 bootloader and to get it I had to flash the B07 firmware on my phone to fool the updating tool into thinking i needed an update... but from what i have read around these parts, the b09 is the last update available through the updating tool... is that correct?

Thankfully i had the b07 boost updating package backed up... for thew longest time it was available on a french site but when i needed it i couldn't find it but thankfully i hoard data on my computer.. :p

on the public mobile stock update.zip(because public doesn't update through ota or an online tool) the firmware is in the zip...
 
smartmanvartan said:
correct the updating tool checks the bootloader... I know because on the N860 for Public we had a different bootloader and I needed a copy of the boost mobile bootloader for some tests. I wanted the b10 bootloader and to get it I had to flash the B07 firmware on my phone to fool the updating tool into thinking i needed an update... but from what i have read around these parts, the b09 is the last update available through the updating tool... is that correct?

Thankfully i had the b07 boost updating package backed up... for thew longest time it was available on a french site but when i needed it i couldn't find it but thankfully i hoard data on my computer.. :p

on the public mobile stock update.zip(because public doesn't update through ota or an online tool) the firmware is in the zip...
Click to expand...

Not sure I think they might have changed the version to b11 on the tool by now. Back on the N860, the last ota updater. Whatever "B0 number" it was, was the public warp also updated to that b0 number?
 
the public mobile version would not update with that tool because it is specifically for the boost mobile version... The boost warp is a "N860" and the public warp is the "PMI-N860" so the updater would just say that the device is up to date...
 
when i get the replacement for my phone tomorrow I'll give the b09 firmware a test and try to update through the online updating tool so i can get my hands on the b11 package... if it is available through the online tool that is...
 
smartmanvartan said:
when i get the replacement for my phone tomorrow I'll give the b09 firmware a test and try to update through the online updating tool so i can get my hands on the b11 package... if it is available through the online tool that is...
Click to expand...

Why do it through the tool? Why not the over the air? You'll get the ota to b11 when you flash back to b09
 
I want to have the firmware files in their original form... i can just get the b11 update through here if that was my goal... but updating though the updating tool will allow me to grab the n861v1.0.0b11.zip package that will be downloaded in my tmp folder... that package is formatted differently... if i do get it I'll post it up...
 
chevanlol360 said:
from the script you can see that adsp is partition number 8 aka mmcblk0p8. See what he's saying? i thought you knew that while trying to get the jb partitions the other day lol. Anyway yeah thats how most devs finds out what partition is what/does what, through Official OTA updater-scripts. Which is why i kind of hesitate to flash other phones partitions other than my own cause even though we have the name for them in the zip, we dont know what the hell they do lol I remembered an old friend and amazing dev interdpht was working on getting new update rooted on to everyones Transform UItra, he ended up flashing some else IMED partition which automatically gave him the other persons IMEd number haha. In the end he never backed it up which caused him to buy a new ultra
Click to expand...

That is how we discovered which partitions were being updated and which ones needed to be replaced...but like you I have no clue what they do lol. Just decided to take a risk and it worked out this time for this device.
 
SuperR said:
That is how we discovered which partitions were being updated and which ones needed to be replaced...but like you I have no clue what they do lol. Just decided to take a risk and it worked out this time for this device.
Click to expand...

you know for your b11 rom you could grab that patch folder in the ota package and in your update script paste the patch lines for those parttions and make your rom a one shot installer... it's been done on the N860...
 
smartmanvartan said:
you know for your b11 rom you could grab that patch folder in the ota package and in your update script paste the patch lines for those parttions and make your rom a one shot installer... it's been done on the N860...
Click to expand...

Well that would have been easy when super was making the update zip
 
You must log in or register to reply here.
Back
Top Bottom