[FW R5A WIFI/3G] NEW! custom preROOTed newest stock nbx03 R5A with R1A's recovery!

[condi]

Hi guys

I've prepared ready-to-flash nbx03 fw.
What's the difference between stock and that one?


Features:

• prerooted,
• 'rescue-backdoored'
• init.d added
• write permissions for ext-sdcard enabled,
• replaced locked recovery with one from R1A!

So you will have newest R5A with still adb shell enabled in recovery!
Benefits? You will be able to use 'prerooted' firmware in future releases!
Official stock R5A disables shell in recovery - means no more functions
like flashing custom, decrypting etc!


Requirements:

• no R5/R5A flashed before, because of recovery locked down.
  (= will not work on downgraded from R5/R5A devices)
• root
• newest AiO

How-to?:

• download fw and rename it as 'custom_update_signed.zip',
• put custom_update_signed.zip on root of your extSD,
• run AiO - choose '3' & '4' - Flash signed zip, choose automatic.
• just sit, wait and enjoy
  PS. wipe is not required, but recommended.

If after wipe or reboot your device will boot to old firmware (which is still on 2nd /system partition),
then you should use v2 doubleFLASH custom zip - which updates both /system0&1 partitions when flashing
This prevents from such problems!
You can flash 1st regular version of custom zip, or directly v2 with doubleFLASH


Easy as hell

Download:

NEW R5A with 3G! doubleFLASH!: (will update both /system0&1 partitions)
custom_prerooted_doubleFLASH_R5A_nbx03_016-ota-121116077.zip

NEW R5A with 3G!:
custom_prerooted_R5A_nbx03_016-ota-121116077.zip


NEW R5A WiFi only! doubleFLASH!: (will update both /system0&1 partitions)
custom_prerooted_doubleFLASH_R5A_nbx03_001-ota-121116036.zip


old R5 WiFi only custom_prerooted_nbx03_001-ota-120914044_by_condi.zip

-----------------------
mirror on Google Drive
-----------------------



br
condi

 

[stifilz]

Hi guys

I've prepared ready-to-flash US nbx03_001-ota-120914044.
What's the difference between stock and that one?

Features:

• prerooted,
• 'rescue-backdoored'
• init.d added
• write permissions for ext-sdcard enabled,
• replaced locked recovery with one from R1!

So you will have newest R5 with still adb shell enabled in recovery!
Benefits? You will be able to use 'prerooted' firmware in future releases!
Official stock R5 disables shell in recovery - means no more functions
like flashing custom, decrypting etc!

Requirements:

• R1 firmware currently on device,
• no R5 flashed before, because of recovery locked down.
  (= will not work on downgraded from R5 devices)
• root
• AiO

How-to?:

• download fw and rename it as 'custom_update_signed.zip',
• put custom_update_signed.zip on root of your extSD,
• run AiO - choose '3' & '4' - Flash signed zip.
• just sit, wait and enjoy

Easy as hell

br
condi

----uploading...

Great work once again!!!!

Still no progress with already flashed R5 I take it? Damn.... Still someone had to take the fall, for someone else to RISE

YOU ARE A TREASURE TO THIS COMMUNITY

Stifilz

 

[condi]

Great work once again!!!!

Still no progress with already flashed R5 I take it? Damn.... Still someone had to take the fall, for someone else to RISE

YOU ARE A TREASURE TO THIS COMMUNITY

Stifilz

im pretty sure that sooner or later we will figure something out to get r5+'s recoveries back to the game
treasure? noooooo... just a simple man, and his hobby but thanks friend !

condi

 

[stifilz]

im pretty sure that sooner or later we will figure something out to get r5+'s recoveries back to the game
treasure? noooooo... just a simple man, and his hobby but thanks friend !

condi

You SIR are toooooooooooo modest.

So you can still pre-root install to HC I assume? I have not been able to get back since the R5 recovery installed itself

Well time will tell and we WILL get there! LOL

Is it as simple as a setting turned off somewhere or is it a full part of the recovery.img?

I have not looked in your prerooted file yet..... Can you inject your recovery (the on the fly one) as a permanent solution?

That would be TOPS.

Thanks again

Stifilz

 

[condi]

You SIR are toooooooooooo modest.

So you can still pre-root install to HC I assume? I have not been able to get back since the R5 recovery installed itself

Well time will tell and we WILL get there! LOL

Is it as simple as a setting turned off somewhere or is it a full part of the recovery.img?

I have not looked in your prerooted file yet..... Can you inject your recovery (the on the fly one) as a permanent solution?

That would be TOPS.

Thanks again

Stifilz

have you tried oldest 3.2 fw? (not 3.2.1) someone here have written that he downgraded (dont know if thats true).
adb probably is being disabled through kernel, init.rc or somewhere there.
about injecting - for now - unfortunatelly no.

br

 

[stifilz]

have you tried oldest 3.2 fw? (not 3.2.1) someone here have written that he downgraded (dont know if thats true).
adb probably is being disabled through kernel, init.rc or somewhere there.
about injecting - for now - unfortunatelly no.

br

Will change to US and try.... but doubt it.... oldest I have for NZ is 0035 (3.2.1)... Does Sony Tab S have installer file (like Tab P) i have searched high and low for one. LOL

Stifilz

 

[condi]

Will change to US and try.... but doubt it.... oldest I have for NZ is 0035 (3.2.1)... Does Sony Tab S have installer file (like Tab P) i have searched high and low for one. LOL

Stifilz

check P's partition table and... you can always try P installer fw
to flash it you will have only to change region via AiO to P, and ro.product.device and ro.build.product to nbx02!

btw you know whats the difference on -ota- and -installer- fw?
does it overwrites hidden.img no matter lower/higher present version???
maybe that "hidden_full.img" will overwrite r5's hidden! ??

br

 

[stifilz]

check P's partition table and... you can always try P installer fw
to flash it you will have only to change region via AiO to P, and ro.product.device and ro.build.product to nbx02!

btw you know whats the difference on -ota- and -installer- fw?
does it overwrites hidden.img no matter lower/higher present version???
maybe that "hidden_full.img" will overwrite r5's hidden! ??

br

Hmmm. Change to Tablet P region successfully. (nearly shat myself, seemed like forever to boot LOL)
Changed to nbx02 in build.prop where it was nbx03.
Also mounted the other system partition and changed the build.prop there too.

Still got this error.

-- Install /sdcard ...
Finding update package...
I:Update location: /sdcard/signed-nbx02_001-installer-01202.009.zip
Desklunvr update package...
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1465 bytes; signature 1447 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Checking version is passed, 11110404 -> 110705000
Checking detailed SKU[27550200] is passed
Installing update...
installing nbx updater extensions
script aborted: assert failed: getprop("ro.product.device") == "nbx02" ||
       getprop("ro.build.product") == "nbx02"
assert failed: getprop("ro.product.device") == "nbx02" ||       getprop("ro.buil
d.product") == "nbx02"
E:Error in /tmp/desklunvr/desklunvr.zip
(Status 7)
Installation aborted.

Have a feeling and hoping this will work....... Do I have to change buildinfo.sh? "# autogenerated by buildinfo.sh"
Do we have access to this?

When tabs are returned to Sony they come back as 3.2!!

Stifilz

 

[condi]

Hmmm. Change to Tablet P region successfully. (nearly shat myself, seemed like forever to boot LOL)
Changed to nbx02 in build.prop where it was nbx03.
Also mounted the other system partition and changed the build.prop there too.

Still got this error.

-- Install /sdcard ...
Finding update package...
I:Update location: /sdcard/signed-nbx02_001-installer-01202.009.zip
Desklunvr update package...
Opening update package...
I:1 key(s) loaded from /res/keys
Verifying update package...
I:comment is 1465 bytes; signature 1447 bytes from end
I:whole-file signature verified against key 0
I:verify_file returned 0
Checking version is passed, 11110404 -> 110705000
Checking detailed SKU[27550200] is passed
Installing update...
installing nbx updater extensions
script aborted: assert failed: getprop("ro.product.device") == "nbx02" ||
       getprop("ro.build.product") == "nbx02"
assert failed: getprop("ro.product.device") == "nbx02" ||       getprop("ro.buil
d.product") == "nbx02"
E:Error in /tmp/desklunvr/desklunvr.zip
(Status 7)
Installation aborted.

Have a feeling and hoping this will work....... Do I have to change buildinfo.sh? "# autogenerated by buildinfo.sh"
Do we have access to this?

When tabs are returned to Sony they come back as 3.2!!

Stifilz

check /datapp/vendor/vendor0&1/vendor.prop for nbx values

 

[[email protected]]

So if we have R5 then we shouldn't even bother with this?

 

[Ultimate Chicken]

check /datapp/vendor/vendor0&1/vendor.prop for nbx values

Quick question - do you need to be on 3.2 before you can flash this? I got a different assert.

Copy system image...
assert failed: file_getprop("/system/build.prop", "ro.build.fingerprint") == "Sony/nbx03_003/nbx-3"3.2/THMAS11001/11001.003:user/release-keys" ||
file_getprop("/system/build.prop", "ro.build.fingerprint") == "Sony/nbx03_003/nbx03:3.2.1/THMASU0035/0035.003:user/release-keys"

 

[stifilz]

So if we have R5 then we shouldn't even bother with this?

Correct because we have already lost adb shell in recovery.... so can't flash modded roms like this one.

Stifilz

---------- Post added at 05:13 PM ---------- Previous post was at 05:10 PM ----------

Quick question - do you need to be on 3.2 before you can flash this? I got a different assert.

Don't worry about that, that was condi and I trying to figure something out. Didn't work BTW.

As in first post you need to be on R1A/R2A. US is the only region with R5 out atm. Apparently the other regions are due out mid DEC....

Stifilz

 

[ianfretwell]

Must be doing something wrong....

Hi,

I'm trying to flash a UK 4.0.3 R1a tablet with the details in this thread.

The tablet was rooted via the b1nry method (when that method was first discovered).

All appears to work OK but then I get a failed assert.


Told the device to do a full wipe, then rooted using the AiO5.2 - this worked fine.
Then attempted the flash again, still no joy, same error message.

What am I doing wrong ? Should I changed the tablet to US region before attempting the flash ?


Thanks
Ian

---------- Post added at 07:46 PM ---------- Previous post was at 07:40 PM ----------

In answer to my own query - no that doesn't help either, the error this time coming much sooner (whilst verifying update package) :-

Erohibit update as a result of checking version or base sku

 

[ianfretwell]

Attached should be a pic of the actual error I receive...if that helps at all..

 

[condi]

Attached should be a pic of the actual error I receive...if that helps at all..

That error is 100000% ok.
Use 'adb devices' and tell me if there is device there - im pretty sure that there will be none.

Probably you have not installed drivers for adb in recovery (yes it needs to be installed aside from regular drivers in normal boot. So enter device manager and there should be new device without driver. You will have to install it manually.

Oh and if you have changed region to US, then go to AiO\files directory and delete _hack_recovery.zip.

 

[ianfretwell]

Condi - many thanks, you were, of course, absolutely correct and the flash has now succeeded !!

Apologies for being the noob!!

Ian.

 

[Cat McGowan]

I've prepared ready-to-flash US nbx03_001-ota-120914044.
So you will have newest R5A with still adb shell enabled in recovery!

Does this really contain 4.0.3 release 5a, which is scheduled to be released mid-December 2012? I ask because I am pretty sure the update file nbx03_001-ota-120914044.zip contains 4.0.3 release 5, not release 5a.

 

[biablo]

I agree with you. That may be tiny mistake. The incremental numba says that it s from US 4.0.3.r5.

 

[condi]

Does this really contain 4.0.3 release 5a, which is scheduled to be released mid-December 2012? I ask because I am pretty sure the update file nbx03_001-ota-120914044.zip contains 4.0.3 release 5, not release 5a.

I agree with you. That may be tiny mistake. The incremental numba says that it s from US 4.0.3.r5.

yes, just a typo, my bad ive lost count with all that incrementals lol

 

[sapphire88]

wifi only rom, right?