Database Info

[Q] S-OFF and OTA

Well I switched to S-OFF to get a new splash screen and now I can no longer install OTA updates for my Hero. I get a signature failure every time I try to install. Does anyone know how to switch this back on? I didn't realize this would kill the ability to do updates as the forums I have read before switching didn't have any mention of it.
Sorry if this has been previously posted and I missed it in the forums.
Any help would be greatly appreciated.

awnorwood said:
Well I switched to S-OFF to get a new splash screen and now I can no longer install OTA updates for my Hero. I get a signature failure every time I try to install. Does anyone know how to switch this back on? I didn't realize this would kill the ability to do updates as the forums I have read before switching didn't have any mention of it.
Sorry if this has been previously posted and I missed it in the forums.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
The signature failure isn't from s-off it's from the custom recovery. What you need to do is to resign the zip.

awnorwood said:
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Just an added note, as far as I know, you can't switch back to S-ON on this
device, at least, not at the moment.. If they get S-ON to work on these phones,
good, but if not, I'm not overly concerned.
http://forum.xda-developers.com/showthread.php?t=759955
and
http://unrevoked.com/rootwiki/doku.php/public/forever
for details..

Asadullah said:
The signature failure isn't from s-off it's from the custom recovery. What you need to do is to resign the zip.
Click to expand...
Click to collapse
Not sure I'm understanding the question. But, if he means receiving updates directly from Sprint then they don't come as zip files. So, how would signing anything help him?
Not sure why you would want to download something from Sprint directly anyway. Whenever an update comes out, they're usually packaged and ready for you to flash via custom recovery by the end of the day if not sooner.

mercado79 said:
Not sure I'm understanding the question. But, if he means receiving updates directly from Sprint then they don't come as zip files. So, how would signing anything help him?
Not sure why you would want to download something from Sprint directly anyway. Whenever an update comes out, they're usually packaged and ready for you to flash via custom recovery by the end of the day if not sooner.
Click to expand...
Click to collapse
The ota (over the air) updates that sprint pushes out and you download are stored in an update zip in /cache then when you choose to install them they are flashed through the stock recovery... but if you don't have the stock recovery you will have to pull the update from your device resign it and then flash it through custom recovery. Also they won't work on anything but a stock or close to stock rom because of the checks it does in the update scripts and most of everything inside is .p files (patch).
I should know because I took the second to last sprint update rooted it and posted it on here. You can actually test this theory by running the ruu rooting it and then when you get an update download it but don't install it right away. You'll find it in /cache (I believe forgotten exactly) or just take my word for it.
If you do do it like that I suggest the original 2.1 ruu just because you'll get your original radio back in the process

Asadullah said:
The ota (over the air) updates that sprint pushes out and you download are stored in an update zip in /cache then when you choose to install them they are flashed through the stock recovery... but if you don't have the stock recovery you will have to pull the update from your device resign it and then flash it through custom recovery. Also they won't work on anything but a stock or close to stock rom because of the checks it does in the update scripts and most of everything inside is .p files (patch).
I should know because I took the second to last sprint update rooted it and posted it on here. You can actually test this theory by running the ruu rooting it and then when you get an update download it but don't install it right away. You'll find it in /cache (I believe forgotten exactly) or just take my word for it.
If you do do it like that I suggest the original 2.1 ruu just because you'll get your original radio back in the process
Click to expand...
Click to collapse
Good information to know. Thanks Asadullah.

Poking at latest OTA update for fun and profit

I am poking around the latest official OTA update (get it here).
I am trying to see if there is anything useful for aftermarket roms. I will post
here my findings, if any, and all the questions that pop to my mind. Hopefully
someone in the community will have answers.
The updating script does the following:
1) several checks on bootloader/recovery/cid/device version
2) copy fotaBoot to /data/system/fotaBoot to trigger some changes at reboot
3) checks on files to be patched
4) delete several files from /data (notably adio_checksum, DxDr,
SuplRootCert_injected)
5) delete lots of files form /system
6) apply patches
7) copy files into /system
8) set permissions
9) flash firmware.zip via
Code:
write_firmware_image("PACKAGE:firmware.zip", "zip");
Among the files being modified there are a couple of firmwares (yamato_pfp.fw
yamato_pm4.fw). I do not have them on my system (I run CM7) and I have no idea
which piece of hardware they refer to. There is also an app whose purpose I
ignore (HTC-DPM-GB-2.3-48637-11.1.apk) and a mysterious recovery.img in /system
(more on this later).
Does anyone know the exact procedure by which firmware.zip is flashed? Will any
check be performed on it? Its content is the following:
* android-info.txt: ASCII file with some version numbers.
* boot.img: should be the new kernel+ramdisk; I tried booting it with few
expectations and indeed it wont boot with a non-sense /system
* hboot_8x60_DOT_1.45.0013_20111121_signedbyaa.nb0: the new bootloader; I see no
reason to flash this unless it provides some new features.
* radio.img: fat image with radio files (should be safe to flash)
* rcdata.img: ???
* recovery.img: this won't boot; may it require the above mentioned recovery.img?
Anyway this is completely useless
* rpm.img: ???
* sbl1.img: ???
* sbl2.img: ???
* sbl3.img: ???
* tz.img: ???
Anyone has ideas on what the other files are? I assume that if we avoid flashing
hboot we will always have fastboot available to us and S-OFF to flash anything
we would like to, correct? Revolutionary team can you please explain how you
make the phone S-OFF once your exploit gives you the right privileges? Will any
of those files affect it? Has anyone here any idea of which partitions should
they be flashed to?
As I said I tried to boot both recovery.img and boot.img to get a config.gz and
kernel version with scarce success. I'd like to see whether they made some modifications to the
kernel which improved battery life. I think I will repack the new kernel with
CWM recovery and get the info from there.
Ideas of things to poke at? Comments? Helpful insights?

Related info: here .
sbl*.img might be the boot loader. (secured/secondary boot loader???) but why in 3 separate chunks?

More info: here
rcdata.img is text; it should be the configuration of the radio but if I check the content of the corresponding partition (mmcblk0p18) on my phone there is a lot of binary junk together with the small amount of text. The options are the same except for one (AGPSNVSetting) that is missing in the updated rcdata.img
Code:
# cat /dev/block/mmcblk0p18 | strings | tail -n 9
QCT_UMTS_RADIO_VER=1
DisH=2
AGPSNVSetting=1
EnDTM=0
MSCMode=10
HSDPACat=10
HSUPACat=6
GEA3=0
QCT_UMTS_RADIO_END=1

I know probably the biggest request from the community is to figure out how to root the update; it seems that the Rev. team has been notified that the exploit they used before seems to have been patched in this update.
Also very profitable would probably be zips for the new kernel and radio, if possible. Early reports have indeed been of better battery life, and also higher quadrant scores.
Anyway, many thanks for this thread, and for looking at the update

Etn40ff said:
Among the files being modified there are a couple of firmwares (yamato_pfp.fw
yamato_pm4.fw).
Click to expand...
Click to collapse
Just a shot in the dark, but Yamato is refered to here:
http://code.google.com/p/synergy-ki.../system/etc/adreno_config.txt?spec=svn41&r=41
It seems to have something to do with the adreno chipset...

There's a Pre Rooted Version of the OTA Update on Rootzwiki. I would imagine those on XDA would be rooted all ready. I understand trying to find a way to Root the OTA Update for those who had it before they could root. But wouldn't a simple Temp Root, then Downgrade work? That's what I had to do with my G2 and G1.
Sent from my MyTouch_4G_Slide using xda premium

Litesorrows said:
There's a Pre Rooted Version of the OTA Update on Rootzwiki. I would imagine those on XDA would be rooted all ready. I understand trying to find a way to Root the OTA Update for those who had it before they could root. But wouldn't a simple Temp Root, then Downgrade work? That's what I had to do with my G2 and G1.
Sent from my MyTouch_4G_Slide using xda premium
Click to expand...
Click to collapse
the version on Rootzwiki isn't the newest update, the one that just came out 3 days ago. and the newest update has proven impervious even to temp-root so far. the only way to downgrade is if you were S-OFF before updating. there is a thread on this in the general section.....

If you updated, please view this thread.
http://forum.xda-developers.com/showthread.php?t=1405859

I had pulled the new google talk app and made it flashable on request, here's the link:
Gtalk update
There are a couple others if anyone wants them - deskclock, wifi calling, t-mo mall and carbon backup, netflix, and two logging utilities.
The rest is all small updates to a lot - what I wanted to look into first were the GPS updates to make sure my patch stays as current as possible.
You can either pull apart the package directly, or flash the update and do an adb pull to grab new stuff - backup guide in my sig tells you all about using the adb pull command.
Now that we know you can rewind the changes and get root back after the update, either should be fine. I've been going through the download zip, but haven't had much time at my workstation.
I have a couple emergency shifts to work, kept me offline yesterday & today, I'll check back on a break later and see if I have anything else to add.
Sent from my Bulletproof_Doubleshot using xda premium

Blue6IX said:
I had pulled the new google talk app and made it flashable on request, here's the link:
Gtalk update
There are a couple others if anyone wants them - deskclock, wifi calling, t-mo mall and carbon backup, netflix, and two logging utilities.
The rest is all small updates to a lot - what I wanted to look into first were the GPS updates to make sure my patch stays as current as possible.
You can either pull apart the package directly, or flash the update and do an adb pull to grab new stuff - backup guide in my sig tells you all about using the adb pull command.
Now that we know you can rewind the changes and get root back after the update, either should be fine. I've been going through the download zip, but haven't had much time at my workstation.
I have a couple emergency shifts to work, kept me offline yesterday & today, I'll check back on a break later and see if I have anything else to add.
Sent from my Bulletproof_Doubleshot using xda premium
Click to expand...
Click to collapse
could i get deskclock, wifi calling, and netflix

Yamato is gpu proprietary files. U would use them in a compile against source code for the improvements. I would say kernel fixes would be the main thing if reports are better quadrant and battery life
Sent from my MB525 using XDA App

I flashed the t-mobile signed stock rom PP59IMG.zip through the bootloader then proceeded to download the OTA's. After that I placed the new recovery image in the appropriate place and rebooted bootloader to prepare pushing the recovery through fastboot. What I noticed is that even after installing the OTA in a unrooted totally stock rom, S-off remains, however where "revolutionary" once was written now displays "**Locked**" , so apparently HTC has managed to relock the bootloader even though it shows S-off. It's not totally locked, as I had to reflash the PP59IMG.zip to downgrade hboot again so that I could reuse the revolutionary tool to flash the 4.0.0.8 recovery, then install CWM to update the recovery. As long as "Locked" was sitting where "revolutionary" normally is, I found it impossible to use fastboot, so my guess is security remains off but fastboot is locked. Just my guess anyway.

Where did you get the stock/signed T-Mo PP59IMG.zip? Can't find it anywhere here. Thanks.

monakh said:
Where did you get the stock/signed T-Mo PP59IMG.zip? Can't find it anywhere here. Thanks.
Click to expand...
Click to collapse
Link in quote below:
yogi2010 said:
sure Blue, it is pretty much the usual...
To undo the update/restore the stock firmware that came with the phone:
(Note: this will only work if you are still S-OFF even tho you have the new HBOOT version. If you are S-ON with the new HBOOT, then at this time there is no known way to revert... hopefully we can get the devs. of Revolutionary, etc, to update the root methods. Also, if you want to update just to check it out, make sure to turn S-OFF first if you'd like to give yourself the option to revert later.)
1. Download the stock firmware package from here: http://forum.xda-developers.com/showthread.php?t=1178082
2. Rename it PG59IMG.zip and put it on the root of your sdcard.
3. Boot into the bootloader('adb reboot bootloader' or power down the phone then hold volume down + power), let it read the update package, and press 'volume up' to update when prompted.
4. At the end it will prompt you to press Power to reboot. It scared me because when i pressed Power, the screen went off and seemed to not come back on, so i pressed power once again, and it booted into the system.
That's it! Just remember that if you do this, it will of course erase all your data... your phone will be like it was out of the box.
Click to expand...
Click to collapse

I'm not sure if this helps anyone, but here is the boot.img taken from my nandroid of the newest OTA ROM:
http://db.tt/GHfzWNIj
come to think of it, looks like you might already have this in the OTA zip... although this one is a bigger file...

Two questions:
1. How do you flash this update? When I click the HTC Update, it gave me the ~5MB update, however not the ~40MB one. So is there a way to manually flash it?
2. Is there a way to doing so without loosing the recovery and root?

Sinfamy said:
Two questions:
1. How do you flash this update? When I click the HTC Update, it gave me the ~5MB update, however not the ~40MB one. So is there a way to manually flash it?
2. Is there a way to doing so without loosing the recovery and root?
Click to expand...
Click to collapse
You can download the update and run it manually. I can't remember if I renamed it update.zip and flashed it through stock recovery or used the bootloader.
If it was the bootloader, rename the downloaded zip to PG59IMG.zip, put it on the root of your sdcard and boot into the bootloader. The device's screen should prompt you with install instructions.
As for keeping root and recovery, no. As long as you are S-OFF *before* doing this, however, you can re-flash a custom recovery and re-root using these instructions: http://forum.xda-developers.com/showthread.php?t=1433805

Yeah, the update flashed nicely thru the stock recovery. I learned once you get to the recovery screen, you press volume up + power to get the options to show up.

[Q] Can't receive OTA Htc updates - What now?

I have a HTC chacha which I have unlocked s-on and rooted using HTC dev method,
CWM-based Recovery v5.0.2.8 and su-2.3.6.1-ef. I have partitioned my sd card (Fat32, Ext2) to install Link2sd and all is well.
I tried to install an OTA update however, this is the message that appeared in CWM:-
E: Can't mount SDCARD:download/OTA_Chacha_HTC_Europe_1.54.401.3-1.54.401.2_release_257016cuxtfbx8dmv4o4ai.zip
Installation aborted.
(1) Is there another way to install this and future htc updates to my phone?
I only rooted to free up some more space using Link2sd and have achieved that so I don't want to modify my phone anymore if it is not absolutely necessary.
(2) Should I install Cyanogen?
I am a newbie and have tried to read as much posts as possible and thank those who have taken the time to impart their knowledge. I am still slowly finding my way round this so please forgive me if these seem silly questions to ask.
I would be grateful if you would steer me on the right path. I'm nearly there.

You need stock recovery to flash OTA updates. Replace your CWM with a stock recovery. Make sure you check the versions and regions so you won't mix them up.

Alex C. said:
You need stock recovery to flash OTA updates. Replace your CWM with a stock recovery. Make sure you check the versions and regions so you won't mix them up.
Click to expand...
Click to collapse
How do I replace my CWM with stock recovery?

Alex C
Thanks.
Looking at your index of downloads Alex, is this the version for UK chacha?
OTA_Chacha_HTC_Europe_1.54.401.2-1.33.401.1_release_224463.zip
OR is it this one? chacha_eu_1.54_default_signed.zip
Thanks

It might be neither of them. There might be a different version for the UK region. Check the threads in dev and general (there are a few section pages). I'm not sure, but it's a possibility. The best bet is to get your stock ROM back, as it was provided by the carrier since they are releasing the OTA's (with the extra-carrier bloatware).

Error in the process of Rom installation (status 0)

Hello
I need your support because I can´t install any rom but it´s not clear for me the reason
I already did the next activity without problem
1. Root the phone
2. I installed Recovery-clockwork-2.5.1.2-infuse(I don’t know if this is the last version but according with the update process I didn’t find another one)
I tried to install the some rooms but I can´t do it because when I’m doing the process of install from Zip I received the next message
 error flashing rom status 0 infuse 4g (Installation aborted)
Honesty speaking I don’t know.
I tried to install another rom but the same error message and put the file directly in the location, etc. but the same result please help my does anybody have any idea about this problem
Thanks for your support :fingers-crossed:

lgluna20 said:
Hello
I need your support because I can´t install any rom but it´s not clear for me the reason
I already did the next activity without problem
1. Root the phone
2. I installed Recovery-clockwork-2.5.1.2-infuse(I don’t know if this is the last version but according with the update process I didn’t find another one)
I tried to install the some rooms but I can´t do it because when I’m doing the process of install from Zip I received the next message
 error flashing rom status 0 infuse 4g (Installation aborted)
Honesty speaking I don’t know.
I tried to install another rom but the same error message and put the file directly in the location, etc. but the same result please help my does anybody have any idea about this problem
Thanks for your support :fingers-crossed:
Click to expand...
Click to collapse
Only thing I can think of is install CWM another way, that is, a stock ROM with CWM built in (via Odin),
If your phone is AT&T (Option D preferably, but I hear downloads are hard to find as of late - unfortuanately I don't have a mirror for this one):
http://forum.xda-developers.com/showthread.php?t=1613523
If yours is Rogers:
http://forum.xda-developers.com/infuse-4g/help/rogers-infuse-4g-i997r-help-upgrading-t2998162
Hope this helps.
UPDATE:
What ROM are you going to? Did you disable Voodoo Lagfix? Are you going straight to Kitkat?
Try installing CM9 first if the last two answers are No and Yes, respectively.

Ya same here good thread post!
Facing same troubles!
Sent from my HM 1SW using XDA Free mobile app

joel.maxuel said:
Only thing I can think of is install CWM another way, that is, a stock ROM with CWM built in (via Odin),
If your phone is AT&T (Option D preferably, but I hear downloads are hard to find as of late - unfortuanately I don't have a mirror for this one):
http://forum.xda-developers.com/showthread.php?t=1613523
If yours is Rogers:
http://forum.xda-developers.com/infuse-4g/help/rogers-infuse-4g-i997r-help-upgrading-t2998162
Hope this helps.
UPDATE:
What ROM are you going to? Did you disable Voodoo Lagfix? Are you going straight to Kitkat?
Try installing CM9 first if the last two answers are No and Yes, respectively.
Click to expand...
Click to collapse
Hello
First thanks for your early answer
I forget to put some information
1. My phone is AT&T
2. Currently is android froyo
3. I have tried to install the next Rooms
a. CARBON-KK-NIGHTLY-20141106-1249-infuse4g (4.4.2 Kitkat)
b. C-RoM-4.4.2_v6.6_infuse4g
But the same result ( status 0 Installation aborted)
What do you think
Do you think that first I need to install previous version of 4.4.2Kitkat
Thanks

lgluna20 said:
Hello
First thanks for your early answer
I forget to put some information
1. My phone is AT&T
2. Currently is android froyo
3. I have tried to install the next Rooms
a. CARBON-KK-NIGHTLY-20141106-1249-infuse4g (4.4.2 Kitkat)
b. C-RoM-4.4.2_v6.6_infuse4g
But the same result ( status 0 Installation aborted)
What do you think
Do you think that first I need to install previous version of 4.4.2Kitkat
Thanks
Click to expand...
Click to collapse
Kitkat (even Jellybean) is often too much of a jump for a CWM of that vintage (unless you are lucky in disabling voodoo lagfix). Try flashing CM9 (this will upgrade your CWM as well). If you still get an error, you will need to OTA to Gingerbread first. This can be achieved by Odining one of the stock ROM's, first link in my previous post.

joel.maxuel said:
Kitkat (even Jellybean) is often too much of a jump for a CWM of that vintage (unless you are lucky in disabling voodoo lagfix). Try flashing CM9 (this will upgrade your CWM as well). If you still get an error, you will need to OTA to Gingerbread first. This can be achieved by Odining one of the stock ROM's, first link in my previous post.
Click to expand...
Click to collapse
Hello
Thanks for your answer
do you know another link where I can find the files? Because the files were deleted from the links
According with your recomendation I Looking for Option D
Thanks

lgluna20 said:
Hello
Thanks for your answer
do you know another link where I can find the files? Because the files were deleted from the links
According with your recomendation I Looking for Option D
Thanks
Click to expand...
Click to collapse
You can always ask around on the thread - sorry, I don't have any leads (I only downloaded the important stuff for the Rogers version, which will be no good to you).
Good luck though!
UPDATE: I just PM'ed everyone who I've recommended those packages in the past. Hopefully I get a bite.

[Q] Rooted with Recovery Now What???

I have an unlocked xperia z3 d6603 I bought brand new in january I believe. I just today rooted and installed recovery but am stuck on the 23.0A.2.93 tft rom which it shippped with. It would have normally been running unrooted the latest rom from sony which was just pushed out a couple months ago. I'm in california and need a rooted d6603 generic global rom, or even unrooted, and I can't seem to find the down link here. In xpreifirm 3.6a latest, I keep getting a java error so can't use that and I've already uninstalled and installed the latest 64bit java8 update 40. I was going to just flash it with the moonwalker rom but it days I need to be on a different tft altogether. Any help here would be appreciated. I have installed a firewall, changed dns servers, and uninstalled a few things using rom toolbox. Hoping to just update it to the recent tft or even better, a working custom rom which won't mess up the default phone capabilities. I'm on kitkat 4.4.4, at&t lte, rom 23.0.A.2.93
Again I need a rooted global generic 577 tft for a z3, a nonrooted one, or even better, a custom one I can just flash to it so I can get back to my life.

since you have a working recovery just flash this one 23-0-1-5-77-deodexed-zipaligned it's the latest KK
ps: I'm on AT&T in CA as well and running that firmware just fine for a while now, it's generic global so no worries...

awesome. THANKS. Gonna try it now. Been at it all day from like 10am to about 5 when I had to break

How do you flash a zip file
tweker said:
awesome. THANKS. Gonna try it now. Been at it all day from like 10am to about 5 when I had to break
Click to expand...
Click to collapse
I rebooted with TWRP in recovery mode, reset device (Wipe Data, Cache and Dalvik Cache), saw no way of flashing from recovery mode. Shut phone off. Plugged in in flash mode with the zip file in the firmwares folder and it was not recognized by flash tool. Where are the directions for flashing a zip?

Choose the second option in recovery
Install custom zip

I used NDR to reboot into recovery. The zip was on both internal and external at root. First time I selected the one from internal and it gave no errors. Wiped cache and rebooted and still on stock 93. Did the exact same thing again choosing zip on sd card and it still says 93. Third time I did it from sd card but no cache wipe. Still on23.0.A.2.93. WTF???
Where can I find a working ftf. NDR doesn't work for ****. BTW, phone is setup in dev mode with mock, airplane mode etc with supersu free working. I think
BTW, why in the hell does the thread with all the roms not have any current ones???? rooted or not

What for are you trying to flash? Please provide a link.
What does the recovery log say? It really helps if you tell us this.
FTF files are geberally not uploaded anymore as it is very easy to download any you want from the sony servers and create your own FTF using flashtool and Xperia firm.
Ps, it may be nice to watch your language. The issue is not NDR, it works fine.

I'm using D6603_23.0.1.A.5.77_deodex.zip from here: http://forum.xda-developers.com/z3/development/deodex-23-0-1-5-77-deodexed-zipaligned-t3015178 on top of D6603_23.0.A.2.93_Generic_20GLOBAL.ftf which was rooted and dual recovered. I have flashed the above 5.77 zip file like 5 times from recovery mode and still on 93. This last time I noticed I had no file mgr. Installed es, mounted system rw like it says to do after root, reflashed the 77 deodexed zip, wiped dalvik and cache, reupdated supersu zip in recovery, rebooted, and stil on93. What am I doing wrong? Is there not a dern ftf file I can use instead? OR, should and could I just wait for another official update?

tweker said:
I'm using D6603_23.0.1.A.5.77_deodex.zip from here: http://forum.xda-developers.com/z3/development/deodex-23-0-1-5-77-deodexed-zipaligned-t3015178 on top of D6603_23.0.A.2.93_Generic_20GLOBAL.ftf which was rooted and dual recovered. I have flashed the above 5.77 zip file like 5 times from recovery mode and still on 93. This last time I noticed I had no file mgr. Installed es, mounted system rw like it says to do after root, reflashed the 77 deodexed zip, wiped dalvik and cache, reupdated supersu zip in recovery, rebooted, and stil on93. What am I doing wrong? Is there not a dern ftf file I can use instead? OR, should and could I just wait for another official update?
Click to expand...
Click to collapse
That is not a ROM file, it does not contain a ROM. It just deodex's your system files if you are on that firmware.
And, No, there is not a FTF you can flash that is rooted. FTF files have to be completely stock as we cannot sign them with Sony's keys as we do not know them. The only way to flash something rooted is via recovery

Post#2 told me I could flash the zip over and it would work. No wonder it doesn't work because it doesn't do anything. I don't want to unlock boot because I may fail official updates. I really just want to update to a working global generic 77 rooted dual recovered system. So basically even if I had the official 77, unrooted, I still couldn't use (nor root) it right? Thanks for the help. I at least know to go another route.

tweker said:
Post#2 told me I could flash the zip over and it would work. No wonder it doesn't work because it doesn't do anything. I don't want to unlock boot because I may fail official updates. I really just want to update to a working global generic 77 rooted dual recovered system. So basically even if I had the official 77, unrooted, I still couldn't use (nor root) it right? Thanks for the help. I at least know to go another route.
Click to expand...
Click to collapse
Post #2 is wrong. Also the thread stated in the first line that a requirement for that to work is that you are already on .77 firmware.
There is no need to unlock your boot.
Just flash a .77 prerooted ROM.
If you cannot find one then make one yourself. Follow the guide in the thread called PRFCreator (Just google it)
Once you have the files downloaded it takes 7 minutes and it is all automated for you

Thank You Very Much. At present I have access to two pc's. One is my roomies (win8.1) and mine (win7). My roomies has some sort of java issue and xperifirm fails right when you click the file you want. Tried fixing java didn't work. Mine is wireless, dns disabled, mac changed, hosts file, and tiny wall fw. Experifrm says no net access even though it works fine. Tried a cable and for the life of me got the same error (couldn't quite reconfigure it to work correctly-pita). If I ever get the file I will do the prfcreator magic, and I'm assuming, flash it through ndr tools in recovery mode. In the mean, I might request an xda user in another thread to grab one for me and post it. Should help lots of people not just me. Again, thank you for your help, saved a lot of hair pulling.

tweker said:
Thank You Very Much. At present I have access to two pc's. One is my roomies (win8.1) and mine (win7). My roomies has some sort of java issue and xperifirm fails right when you click the file you want. Tried fixing java didn't work. Mine is wireless, dns disabled, mac changed, hosts file, and tiny wall fw. Experifrm says no net access even though it works fine. Tried a cable and for the life of me got the same error (couldn't quite reconfigure it to work correctly-pita). If I ever get the file I will do the prfcreator magic, and I'm assuming, flash it through ndr tools in recovery mode. In the mean, I might request an xda user in another thread to grab one for me and post it. Should help lots of people not just me. Again, thank you for your help, saved a lot of hair pulling.
Click to expand...
Click to collapse
Sorry about the confusion, indeed the first link that I provided was just a patch to deodex your room (I always use deodex so I can mod my rom)....anyway you can use this one it's a generic prerooted .77 from the z3 android development section in this forum, then you can patch it with the other one if you have the need to...just follow the instructions in this link and you should be on your way
Again sorry about that first post, I rooted my phone the minute root was available on locked bootloader so it's been some time now

I have been to that link. The only one I can see that says generic global is the 23.0.A.2.93 one. The others say, Generic_DE, Generic_NCB, or Generic_AU. Which looks to me like Deutch, Generic Nordic?, and Australian? Since I speak english and am nowhere near any of those places, I did not touch them. Which one is safe to use and will there be any post config for my locale and radios?? Plus I have no clue what the purpose is of de-odexing the file system (flashing that zip) does. I still have read write issues with apk's I install when I tell them to use my 128gb sd card. I did recover my setup prior to the zip flash you pointed me to which I still have-thank you.

tweker said:
I have been to that link. The only one I can see that says generic global is the 23.0.A.2.93 one. The others say, Generic_DE, Generic_NCB, or Generic_AU. Which looks to me like Deutch, Generic Nordic?, and Australian? Since I speak english and am nowhere near any of those places, I did not touch them. Which one is safe to use and will there be any post config for my locale and radios?? Plus I have no clue what the purpose is of de-odexing the file system (flashing that zip) does. I still have read write issues with apk's I install when I tell them to use my 128gb sd card. I did recover my setup prior to the zip flash you pointed me to which I still have-thank you.
Click to expand...
Click to collapse
1) its called a FTF file not a TFT file. It's a FlashTool File.
2) your sd write card issues are a feature of KK, and nothing to do with any error or bug to do with your phone. Just Google KK write to sd card to read more about it and how to circumnavigate this issue that was deliberately introduced by Google.
3) i have read some of the advice you have banded about in several of the thread here. Some of it is just plain wrong. Although not dangerous to anyones device it may be worth reading and learning a bit more first.
4) please stick to asking questions in just one thread, there is no need to ask in several thread because the first time you did not get an immediate answer
5) you can safely flash a FTF from any region as long as it is for the same model you have. Especially as you are only going to be on that version for a few minutes whilst you root them immediately upgrade.

Ok, great. I'll grab the de one. As for not trying to help; I put down what worked for me. If I don't know everything I can still give input with the little I know. That's how people learn, myself incl. I just got my pc running not two weeks ago so a little overwhelmed with having just rooted as well. Thanks very much for all your help.

tweker said:
Ok, great. I'll grab the de one. As for not trying to help; I put down what worked for me. If I don't know everything I can still give input with the little I know. That's how people learn, myself incl. I just got my pc running not two weeks ago so a little overwhelmed with having just rooted as well. Thanks very much for all your help.
Click to expand...
Click to collapse
No worries. I did not mean to imply that you should not help, only that you should be sure that what you are saying is in fact correct information.
We do all have to learn, but its hard to learn when incorrect information is posted and stated as "fact"
Greg

From install to booted took 4 min. Just had to update supersu and remove a few things. This is awesome! NDR Utils is worth paying for. Now I can finally encrypt my phone. TYSM