Related
Well, here goes nothing.... With a little effort, I've got this done...
1. A system partition nandroid of the Jelly Bean 10.4.2.15 update created using TWRP 2.2.2
2. A modified TWRP 2.2.2 recovery which works with the new bootloader
This system nandroid image has been created for developer use. So, it's not for everyone to play around with. It does not have the new bootloader or boot image, both of which are required to use this system image. It was created using my modified copy of the TWRP 2.2.2 recovery image.
The TWRP 2.2.2 recovery image below is a modified version of the original TWRP 2.2.2 recovery (credits TeamWin). I have merely replaced the kernel within the recovery image with the new JB kernel, thereby allowing it to work with the new bootloader. This is an un-blob'd recovery image. If you wish to directly flash this image, you need to have nvFlash enabled. Else you need to make a blob pack and flash it.
I've now added a zip with the de-odexed system apps and framework jar. This zip only has the /system/app & /system/framework folders. Just to make it easier if anyone wants to create an update zip.
I've also added blobpacked version of the new JB bootloader, kernel, stock recovery and my modified TWRP recovery. Be careful. If you don't know what your are doing and don't have nvFlash enabled, you could brick your device.
USE AT YOUR OWN RISK!!! THE NEW TF201 JB BOOTLOADER IS ESSENTIAL REQUIREMENT!!! BE CAREFUL OR YOUR COULD BRICK YOUR DEVICE
Let the modding begin!!!
tf201-jro03c-system.ext4.win (The system nandroid image)
twrp-2.2.2-jb.img (The un-blob'd modified TWRP recovery)
tf201-jro03c-deodex.zip (De-odexed system apps and framework jars only)
tf201-jb-bootloader.blob (Blobpack of the new JB bootloader)
tf201-jb-kernel.blob (Blobpack of the new JB kernel)
tf201-jb-stock-recovery.blob (Blobpack of the new JB stock recovery)
tf201-jb-twrp-recovery.blob (Blobpack of the my modified TWRP recovery)
I've use Wook's custom JB TWRP , Can I use this system NANDROID?
Thanks for posting.
Are you going to post the boot image?
Turge said:
Thanks for posting. Can you fix the link to the boot image? It's just pointing to d-h.st.
Click to expand...
Click to collapse
If anyone else needs this its at the link here, Craig was working hard and missed it
http://d-h.st/JMk
Thanks for putting this together Craig, you've done alot for us as of late, loved your CM10 builds
thank you for pulling this together, i look forward to what comes from this
ravenholm said:
I've use Wook's custom JB TWRP , Can I use this system NANDROID?
Click to expand...
Click to collapse
Wookie modified it so it would work for the TF300 JB base so my guess would be no.
Trying to get from HB 1.2 to stock JB with Nvflash bootloader as well...
---------- Post added at 05:52 PM ---------- Previous post was at 05:47 PM ----------
craigacgomez said:
Well, here goes nothing.... With a little effort, I've got this done...
1. A system partition nandroid of the Jelly Bean 10.4.2.15 update created using TWRP 2.2.2
2. A modified TWRP 2.2.2 recovery which works with the new bootloader
...
Click to expand...
Click to collapse
A little pointer here guys would be appreciated? Just where do I start with these files e.g. let's say from Stock ICS .28 to get to this one? e.g. copy files to device internal SDcard or use from PC? I see the one file is named .win? Not sure how to handle that?
Moe5508 said:
Trying to get from HB 1.2 to stock JB with Nvflash bootloader as well...
---------- Post added at 05:52 PM ---------- Previous post was at 05:47 PM ----------
A little pointer here guys would be appreciated? Just where do I start with these files e.g. let's say from Stock ICS .28 to get to this one? e.g. copy files to device internal SDcard or use from PC? I see the one file is named .win? Not sure how to handle that?
Click to expand...
Click to collapse
if you don't know what to do with these files, DO NOT DO ANYTHING WITH THEM.
I cannot stress this enough ATM. Yes, we know what to do with them, but until it is deemed safe, or until a better was of flashing is created, only very experienced users/devs should try this.
biggem001 said:
if you don't know what to do with these files, DO NOT DO ANYTHING WITH THEM.
I cannot stress this enough ATM. Yes, we know what to do with them, but until it is deemed safe, or until a better was of flashing is created, only very experienced users/devs should try this.
Click to expand...
Click to collapse
Em, boss, I hear you but we've probably not understood one another on the kind of clarity I'm looking for? What's the reference point for using this? (e.g. current ROM, operating system of PC etc etc)
For example am running a Linux machine at the moment and can easily run the following command to flash the recovery image using fastboot:
./fastboot-linux -i 0x0b05 flash recovery twrp-2.2.2-jb.img
or something to that effect and then would continue to reboot to recovery, copy the nandroid and restore from there?
Anyway, never mind...I take your advice and keep my fingers clear...
Moe5508 said:
Em, boss, I hear you but we've probably not understood one another on the kind of clarity I'm looking for? What's the reference point for using this? (e.g. current ROM, operating system of PC etc etc)
For example am running a Linux machine at the moment and can easily run the following command to flash the recovery image using fastboot:
./fastboot-linux -i 0x0b05 flash recovery twrp-2.2.2-jb.img
or something to that effect and then would continue to reboot to recovery, copy the nandroid and restore from there?
Anyway, never mind...I take your advice and keep my fingers clear...
Click to expand...
Click to collapse
The reference point is a cleanly wiped system. I'm creating a rom from this but you need the new bootloader and recovery. I had the androidroot bootloader installed, wiped system and factory reset. I flashed my JB stock rom and it did replace the bootloader and recovery with a modified TWRP from Craiggomez. The only issue I'm having is that wifi won't connect. I'll figure it out.
What I'm saying is that if you were to flash this image with the old bootloader and recovery, you'd have serious issues.
Ahhh, waiting a few more weeks/months wont hurt anyone ;p
jermaine151 said:
The reference point is a cleanly wiped system. I'm creating a rom from this but you need the new bootloader and recovery. I had the androidroot bootloader installed, wiped system and factory reset. I flashed my JB stock rom and it did replace the bootloader and recovery with a modified TWRP from Craiggomez. The only issue I'm having is that wifi won't connect. I'll figure it out.
What I'm saying is that if you were to flash this image with the old bootloader and recovery, you'd have serious issues.
Click to expand...
Click to collapse
Is it possible to take the bootloader from the its system dump file that's floating around? Or can twrp also backup downloader?
Sent from my HTC Sensation Z710e using xda premium
jermaine151 said:
The reference point is a cleanly wiped system. I'm creating a rom from this but you need the new bootloader and recovery. I had the androidroot bootloader installed, wiped system and factory reset. I flashed my JB stock rom and it did replace the bootloader and recovery with a modified TWRP from Craiggomez. The only issue I'm having is that wifi won't connect. I'll figure it out.
What I'm saying is that if you were to flash this image with the old bootloader and recovery, you'd have serious issues.
Click to expand...
Click to collapse
Yay, thanks for working on that! I am tempted to flash the jb stock image (from unpack) and do all the above, but still, I'd rather have a more reliable method step by step instruction set.
And yes, there is a new partition scheme. Flashing the image with old partition scheme intact will cause errors that could be fixed by nvflash.
Hawke84 said:
Is it possible to take the bootloader from the its system dump file that's floating around? Or can twrp also backup downloader?
Sent from my HTC Sensation Z710e using xda premium
Click to expand...
Click to collapse
Yes, the bootloader is out but just give me a little time to fix wifi and you'll have a safe package to flash. I don't post threads here so you'll find it at rootz. I will post a link in this thread. That's assuming that someone else doesn't post a stock JB build for unlocked bootloaders before I do.
I've now added a zip with the de-odexed system apps and framework jar. This zip only has the /system/app & /system/framework folders. Just to make it easier if anyone wants to create an update zip.
Any I'm going to state this again... unless you have the new TF201 JB bootloader, do not attempt to use the recovery or nandroid image...
jermaine151 said:
Yes, the bootloader is out but just give me a little time to fix wifi and you'll have a safe package to flash. I don't post threads here so you'll find it at rootz. I will post a link in this thread. That's assuming that someone else doesn't post a stock JB build for unlocked bootloaders before I do.
Click to expand...
Click to collapse
Thanks, no rush mate
Sent from my HTC Sensation Z710e using xda premium
I think I understood this correctly but if I'm going to be able to flash this with an unlocked bootloader (I flash cm10 nightlies with cwm) Jermaine or whomever will be getting a pretty good chunk of my paycheck.... I use cm10 on a lot of my devices but it's not the best on the prime. I regret unlocking my bl but I know there's a way for official tfp jb.....
Regards,
Transmitted from my GALAXYSIII running Jelly Bean. XDA premium
ManOnTheMoon said:
I think I understood this correctly but if I'm going to be able to flash this with an unlocked bootloader (I flash cm10 nightlies with cwm) Jermaine or whomever will be getting a pretty good chunk of my paycheck.... I use cm10 on a lot of my devices but it's not the best on the prime. I regret unlocking my bl but I know there's a way for official tfp jb.....
Regards,
Transmitted from my GALAXYSIII running Jelly Bean. XDA premium
Click to expand...
Click to collapse
Yes, we will soon have an update zip for unlocked users... I have created an update zip, but haven't tested it yet... and jermaine has one in the works too...
I've also added blobpacked version of the new JB bootloader, kernel, stock recovery and my modified TWRP recovery. Be careful. If you don't know what your are doing and don't have nvFlash enabled, you could brick your device.
craigacgomez said:
Yes, we will soon have an update zip for unlocked users... I have created an update zip, but haven't tested it yet... and jermaine has one in the works too...
Click to expand...
Click to collapse
Let me know if u want me to test I have nvflash and some time this evening. I also half know what I'm doing
Sent from my HTC Sensation Z710e using xda premium
I have a Singapore T6UL running on 4.3 S-OFF, Bootloader unlocked, rooted. When the 4.4.2 OTA came, I tried installing using the stock recovery. But it is complaining about HtcSoundRecorder.apk and Weixin.apk and abort the installation.Problem is HTCSoundRecorder is removed automatically when I unlocked the bootloader. Can anyone help to provide me with these 2 apk? :crying:
Here is the soundrecorder - http://forum.xda-developers.com/showpost.php?p=48759137&postcount=2
---------- Post added at 10:52 PM ---------- Previous post was at 10:50 PM ----------
lowtengbeng said:
I have a Singapore T6UL running on 4.3 S-OFF, Bootloader unlocked, rooted. When the 4.4.2 OTA came, I tried installing using the stock recovery. But it is complaining about HtcSoundRecorder.apk and Weixin.apk and abort the installation.Problem is HTCSoundRecorder is removed automatically when I unlocked the bootloader. Can anyone help to provide me with these 2 apk? :crying:
Click to expand...
Click to collapse
Do you have a screen shot for us ? that sounds pretty interesting to look at.
I have never heard of anything beibg removed with unlocking thr bootloader. It is possible unlocking the bootloader makes some apps not function properly (or even show up) but the apk should definitely still be there.
I tried using the HtcSoundRecorder.apk that pradeepvizz provides, Still same issue. Complaining about "\data\preload\HtcSoundRecorder.apk has unexpected contents Installation aborted" Tried with the apk extracted from a couple of roms in the dev section. Same issue,
The original doesn't have the "\data\preload" directory. So I thought that creating that directory and copying in the apk should work but it doesn't.
It seems that the \data\preload folder is removed after I unlocked the bootloader via htcdev...
Any ideas?
I am on software version: 1.23.707.1 Any kinds soul have the backup for this version? :highfive:
Jiggity Janx said:
I have never heard of anything beibg removed with unlocking thr bootloader.
Click to expand...
Click to collapse
lowtengbeng said:
It seems that the \data\preload folder is removed after I unlocked the bootloader via htcdev...
Click to expand...
Click to collapse
I do still learn something new every day...
---------- Post added at 11:04 PM ---------- Previous post was at 10:50 PM ----------
So I thought we had a preload partition vice the preload folder? Unless I am just thinking of my samsung devices. Cant look up the partitions right at this second but that would make sense to me (and why I thought nothing was deleted from system or data).
Trying to update from 1.23.707.1 to 2.61.707.1
Tried factory reset. Still doesn't bring back that folder for me...
Funny for HTC to remove those stuff after unlocking bootloader.
lowtengbeng said:
Trying to update from 1.23.707.1 to 2.61.707.1
Tried factory reset. Still doesn't bring back that folder for me...
Funny for HTC to remove those stuff after unlocking bootloader.
Click to expand...
Click to collapse
Did you miss a OTA in the middle like 1.54 or something?
pradeepvizz said:
Did you miss a OTA in the middle like 1.54 or something?
Click to expand...
Click to collapse
I don't think so. I didn't get any software update prompt except for the latest 4.2.2 update since I bought the Max on day 1 launch in Singapore.
Some options that I am thinking:
Option 1: Edit the ota update script to remove checks for sound recorder and weixin. This will make the zip to be unsigned and I am thinking whether this can be flashed using TWRP or CWM as stock recovery shouldn't allow it to be flashed due to unsigned package.
Option 2: Lock the bootloader. Factory reset. I am wondering if this can bring back to 100% stock state. I am from the Windows CE world and this works on CE as it will reload everything from the ROM image.
lowtengbeng said:
I tried using the HtcSoundRecorder.apk that pradeepvizz provides, Still same issue. Complaining about "\data\preload\HtcSoundRecorder.apk has unexpected contents Installation aborted" Tried with the apk extracted from a couple of roms in the dev section. Same issue,
The original doesn't have the "\data\preload" directory. So I thought that creating that directory and copying in the apk should work but it doesn't.
It seems that the \data\preload folder is removed after I unlocked the bootloader via htcdev...
Any ideas?
Click to expand...
Click to collapse
did you try to extract the apk from virtuous ROM? that was only the ROM which i remember to have these files. the Apk files that i had linked were collected it from various posts on XDA, so that could be something causing the mismatch
I am not sure if CWM/TWRP can flash a edited zip using "install update.zip" but i think you can do that via adb sideload in TWRP/CWM.
Do you have the OTA link or the file, can you please upload so that the experts here can use it / help you with it?
pradeepvizz said:
did you try to extract the apk from virtuous ROM? that was only the ROM which i remember to have these files. the Apk files that i had linked were collected it from various posts on XDA, so that could be something causing the mismatch
I am not sure if CWM/TWRP can flash a edited zip using "install update.zip" but i think you can do that via adb sideload in TWRP/CWM.
Do you have the OTA link or the file, can you please upload so that the experts here can use it / help you with it?
Click to expand...
Click to collapse
Yep. I tried with the apk from virtuous ROM having the same issue. I checked the sha-1 of 5 copies of the apk from different sources and none of them has the matching sha-1 that the update script is asking for.
Can you share what is the differences between flashing via adb sideload and "install update.zip"?
I will try to upload the ota file when I get back from work tonight, :highfive:
HTC is spending theiir resources at the wrong place!
lowtengbeng said:
Yep. I tried with the apk from virtuous ROM having the same issue. I checked the sha-1 of 5 copies of the apk from different sources and none of them has the matching sha-1 that the update script is asking for.
Can you share what is the differences between flashing via adb sideload and "install update.zip"?
I will try to upload the ota file when I get back from work tonight, :highfive:
HTC is spending theiir resources at the wrong place!
Click to expand...
Click to collapse
i understand your frustration, but i believe this is part of Google's security improvement in the OTA process.
i am not sure on the difference between adb sideload and update.zip, just did a little bit of Google and found that TWRP may work with the OTA - http://forum.xda-developers.com/showthread.php?t=2573565
Hope something works out.
I just extracted this apk from OTA_T6_UL_JB43_SENSE55_HTC_Europe_1.54.401.1-1.19.401.2_release_341451bchda87kitj44eh9.zip
This is the EURO OTA from 1.19 to 1.54, not sure if that will help you.
i checked the update-script on this OTA and it seemed to all good and should work with CWM / TWRP if all the executables are there..
Hope for the best!
Jiggity Janx said:
So I thought we had a preload partition vice the preload folder?
Click to expand...
Click to collapse
Has anyone looked at this possibility? I thought someone posted all the partitions for the Max but havent come across it yet to check.
pradeepvizz said:
I just extracted this apk from OTA_T6_UL_JB43_SENSE55_HTC_Europe_1.54.401.1-1.19.401.2_release_341451bchda87kitj44eh9.zip
This is the EURO OTA from 1.19 to 1.54, not sure if that will help you.
i checked the update-script on this OTA and it seemed to all good and should work with CWM / TWRP if all the executables are there..
Hope for the best!
Click to expand...
Click to collapse
Thanks for your help. Tried this same issue. :crying:
Later going to try out the lock bootloader and factory reset method. Will keep the progress updated.
This is the ota that I am trying to flash.
https://drive.google.com/file/d/0BwoPVL5J45ITdjUxcXY2Q3FNRk0/edit?usp=sharing
I confirmed that locking bootloader + factory reset does not bring back the \data\preload folder and contents. HTC post load it on top of the rom.
lowtengbeng said:
I confirmed that locking bootloader + factory reset does not bring back the \data\preload folder and contents. HTC post load it on top of the rom.
Click to expand...
Click to collapse
Well, if you are able to find an RUU for your phone, that can be the only clean way to do it.
you can edit the script and removed the lines which specifies soundrecorder apk and then flash it with TWRP / CWM.
pradeepvizz said:
Well, if you are able to find an RUU for your phone, that can be the only clean way to do it.
you can edit the script and removed the lines which specifies soundrecorder apk and then flash it with TWRP / CWM.
Click to expand...
Click to collapse
There is no RUU released for this version yet.
I tried the script editing method and use trwp n cwm. Both failed. Trwp gave an update binary error
I just captured the new Sense 6 update also ...Enjoy [June 4 2014]
http://www.androidfilehost.com/?fid=23501681358542441
MD5: 317bae285618b070279b3a58b2e308e5
============================================================
Posted this in the other 4.4.2 thread I figured it would be easier to find in it's own thread.
http://www.androidfilehost.com/?fid=23329332407573841
MD5: 0b2648c271f52d0d543246119dfb2a8d
Flash in Stock recovery >Recovery_Cingular_US_3.17.502.3.img >> http://d-h.st/6bH
flashing stock recovery
download the above file and put it with your fastboot / adb files
boot the phone to fastboot usb
open command prompt from the fastboot folder
type
fastboot flash recovery Recovery_Cingular_US_3.17.502.3.img
fastboot erase cache
fastboot reboot-bootloader
now your ready to flash the ota.zip
Many have problems just using the stock recovery alone.. if this is your situation you need to RUU back to 3.17.502.3 First.
I posted the link here >> http://www.androidruu.com/getdownlo...13_10.38j.1157.04_release_334235_signed_2.exe
If your s-on you'll have to lock the bootloader before flashing the RUU
fastboot oem lock
Here is a mirror...
https://www.dropbox.com/s/90b05vd22i5uot3/OTAPkg.zip
AT&T 4.4.2 OTAPkg.zip
And of course if your looking to just flash the firmware, just click the link in my sig!?
clsA said:
Posted this in the other 4.4.2 thread I figured it would be easier to find in it's own thread.
http://www.androidfilehost.com/?fid=23329332407573841
MD5: 0b2648c271f52d0d543246119dfb2a8d
Flash in Stock recovery >Recovery_Cingular_US_3.17.502.3.img >> http://d-h.st/6bH
I'll post more instructions if needed
Click to expand...
Click to collapse
thank much! i downloaded the update, and then immediately realized that i didn't have stock firmware. I could have flashed the stock rev, but then i would have to wait till tomorrow to download again, since at&t won't let me.
clsA said:
Posted this in the other 4.4.2 thread I figured it would be easier to find in it's own thread.
http://www.androidfilehost.com/?fid=23329332407573841
MD5: 0b2648c271f52d0d543246119dfb2a8d
Flash in Stock recovery >Recovery_Cingular_US_3.17.502.3.img >> http://d-h.st/6bH
I'll post more instructions if needed
Click to expand...
Click to collapse
i have a big problem. i tried to flash the update zip, and it said failed. then i tried to flash what i though was the stock recov that i downloaded. but it had a bunch of number and letters. forgot that it was an IMG file. so then i rebooted and it said "android is upgrading" now when o boot i get
system ui has stopped" and "dialer has stopped" i thought i made a backup from a previous rom, but it's not there. I NEED TO GET THE PHONE BACK ON! HOW? i can access recovery but that's it.
---------- Post added at 01:09 AM ---------- Previous post was at 01:06 AM ----------
clsA said:
Posted this in the other 4.4.2 thread I figured it would be easier to find in it's own thread.
http://www.androidfilehost.com/?fid=23329332407573841
MD5: 0b2648c271f52d0d543246119dfb2a8d
Flash in Stock recovery >Recovery_Cingular_US_3.17.502.3.img >> http://d-h.st/6bH
I'll post more instructions if needed
Click to expand...
Click to collapse
i have a big problem. i tried to flash the update zip, and it said failed. then i tried to flash what i though was the stock recov that i downloaded. but it had a bunch of number and letters. forgot that it was an IMG file. so then i rebooted and it said "android is upgrading" now when o boot i get
system ui has stopped" and "dialer has stopped" i thought i made a backup from a previous rom, but it's not there. I NEED TO GET THE PHONE BACK ON! HOW? i can access recovery but that's it. i can't adb sideload either.. well i don't know how. i can enable it but how can i get the zip over to the phone. if i can do that i should be fine
vividblu2020 said:
i have a big problem. i tried to flash the update zip, and it said failed. then i tried to flash what i though was the stock recov that i downloaded. but it had a bunch of number and letters. forgot that it was an IMG file. so then i rebooted and it said "android is upgrading" now when o boot i get
system ui has stopped" and "dialer has stopped" i thought i made a backup from a previous rom, but it's not there. I NEED TO GET THE PHONE BACK ON! HOW? i can access recovery but that's it. i can't adb sideload either.. well i don't know how. i can enable it but how can i get the zip over to the phone. if i can do that i should be fine
Click to expand...
Click to collapse
don't panic if you can access recovery your fine
download a rom and push it to your phone
boot phone to recovery / go advanced / screen / timeout never
on you pc you should have a folder with adb and fastboot
put the rom you choose in the folder with adb
then open a command prompt in the same folder (shift + right click - command prompt here)
in the window type
adb devices
your serial number should be here
adb push rom.zip /sdcard/
let it copy is takes a few min and you can tell it's done
now from your phone go to install
find the rom.zip and flash
you should be up and running
Is the RUU available yet? Can someone please provide a link if it is? Thanks.
Sent from my HTC One using xda app-developers app
clsA said:
don't panic if you can access recovery your fine
download a rom and push it to your phone
boot phone to recovery / go advanced / screen / timeout never
on you pc you should have a folder with adb and fastboot
put the rom you choose in the folder with adb
then open a command prompt in the same folder (shift + right click - command prompt here)
in the window type
adb devices
your serial number should be here
adb push rom.zip /sdcard/
let it copy is takes a few min and you can tell it's done
now from your phone go to install
find the rom.zip and flash
you should be up and running
Click to expand...
Click to collapse
i"ll be sure to do that if i get in the shape again, i was so upset that i forgot i had a rom i could just flash. so im gonna put that mirror link ota on my phone, and flash it. but is their a stock i can use as a base? can i just use any stock rom, and then update my phone that way? and what about root? is their a root method for 4.4.2??
vividblu2020 said:
i"ll be sure to do that if i get in the shape again, i was so upset that i forgot i had a rom i could just flash. so im gonna put that mirror link ota on my phone, and flash it. but is their a stock i can use as a base? can i just use any stock rom, and then update my phone that way? and what about root? is their a root method for 4.4.2??
Click to expand...
Click to collapse
you seem very confused .. you can't flash any of these OTA like a rom it won't work !!
users using custom ROMs can't download latest OTA from HTC,
1) If you want to download and flash latest OTA, your device must have completely stock system partition and recovery. Every OTA update is checking MD5 of each file on system partition to ensure .apk patch can be applied. If even one of 1000 files won't match, OTA update installation will fail. In this case you need to flash the latest official update you can find (A RUU) (even one year old) and later download official OTA updates.
Click to expand...
Click to collapse
Here's the RUU I posted in another thread
http://dl3.htc.com/application/RUU_...13_10.38j.1157.04_release_334235_signed_2.exe
clsA said:
you seem very confused .. you can't flash any of these OTA like a rom it won't work !!
Here's the RUU I posted in another thread
http://forum.xda-developers.com/showpost.php?p=50573283&postcount=43
Click to expand...
Click to collapse
its not that im confused, its just that i thought the ota was the same as a rom zip. but it makes sense now that you have to be completely stock to use the ota.
anyway! thanks for the link
---------- Post added at 03:07 AM ---------- Previous post was at 02:13 AM ----------
vividblu2020 said:
its not that im confused, its just that i thought the ota was the same as a rom zip. but it makes sense now that you have to be completely stock to use the ota.
anyway! thanks for the link
Click to expand...
Click to collapse
so do i need to relock my bootloader? i am s-off and I'm downloading the link for "s-off"
vividblu2020 said:
so do i need to relock my bootloader? i am s-off and I'm downloading the link for "s-off"
Click to expand...
Click to collapse
No.
cschmitt said:
No.
Click to expand...
Click to collapse
thanksss
Have you all been able to unlock your bootloader again and flash your custom recovery after the update? And, does the Ota preserve your user data?
Sent from my HTC One using xda premium
after i flash the IMG file to fastboot using ADB what do i need to do next? cause i don't know how to flash the update zip. When I was in the bootloader I tried to get into what I thought was the flashed stock. But it showed a black screen and it was just a picture of my phone with a circular arrow inside a circle. and i had to options before i flashed the RUU and went back to stock. the only one is "unlocked" so i still have S-Off? it doesn't say tampered
Has some issues...I would advise NOT taking the update....heres one issue thats pretty big if your like me and like to take pics and use the editing features...
https://drive.google.com/file/d/0Bx5-C2BrwNVxTDNBRFNoMTFQNjg/edit?usp=sharing
Wonders_Never_Cease said:
Has some issues...I would advise NOT taking the update....heres one issue thats pretty big if your like me and like to take pics and use the editing features...
https://drive.google.com/file/d/0Bx5-C2BrwNVxTDNBRFNoMTFQNjg/edit?usp=sharing
Click to expand...
Click to collapse
I'm not seeing the issue in the video you shared. What happens to the picture?
Sent from my HTC One using Tapatalk
Photo editing functions are all broken....
guy4jesuschrist said:
I'm not seeing the issue in the video you shared. What happens to the picture?
Sent from my HTC One using Tapatalk
Click to expand...
Click to collapse
Wonders_Never_Cease said:
Photo editing functions are all broken....
Click to expand...
Click to collapse
Is that only in the stock camera/gallery app, or in any photo editing app you've tried? I
If only stock, it wouldn't be a big deal for me since I use Snapseed, PicsArt, Photogrid, and Instagram.
Are there any other issues you've heard of or had in this new update?
Sent from my HTC One using Tapatalk
Wonders_Never_Cease said:
Photo editing functions are all broken....
Click to expand...
Click to collapse
Stock HTC One, at&t, just updated to 4.4.2 yesterday morning (approx 11am EST).
I was able to successfully edit three pictures... The first, a simple rotate, changed the pic and ovetwrote the original. The second, also from a separate folder, I cropped a pic and saved it. This created a second image of the edited content. Finally, I edited a pic from the camera pic folder, which included crop and effects. This saved correctly as a separate file as well.
Sent from my secret lair in an undisclosed mountainside.
Some people havce this issue some do not, do not know why this occurs, but its been confirmed from [email protected] in photo editing software....so we shall see
The title says it all. My M8 has the bootloader unlocked, it's S-off and rooted with Teamwin recovery installed. I started dicking around with it, and messed it up. I went to HBOOT and factory reset. I now have no OS, so obviously, my phone won't start up. I appear to be really stuck. If you guys help me and talk me through this, I'll stop dicking around. :-/
Also, I would like to load my stock bootloader, 1.12.502.18 (CID CWS__001). I've found the kernel source code as well as a 1.3 GB file from here http://forum.xda-developers.com/showthread.php?t=2701376 that supposedly houses this Nandroid backup, but I have no idea how to use it. God, I feel stupid.
Ok. I got the Nandroid backup recovery.emmc.win file pushed to the phone. Now, I have a red triangle in the middle of the screen and I can't get to recovery or fastboot.
Flash twrpCopy the rom to where your adb and fastboot are located connect phone via twrp run this command
adb push nameofrom.zip /sdcard/. exactly as shown here change nameofrom.zip to the name of the rom your trying to flash...this will put a rom on your internal storage and it then can be flashed via twrp
Wonders_Never_Cease said:
Flash twrpCopy the rom to where your adb and fastboot are located connect phone via twrp run this command
adb push nameofrom.zip /sdcard/. exactly as shown here change nameofrom.zip to the name of the rom your trying to flash...this will put a rom on your internal storage and it then can be flashed via twrp
Click to expand...
Click to collapse
I was able to get into TWRP just fine. When I pushed the file, it moved the file, but I can no longer get to TWRP. So the ROM is there, I just can't access it. Thoughts?
Ok, I got Recovery going. I'm now in TWRP. Where did adb stick the file I pushed?
take out sdcard if using one and only use internal storage..Have to push a flashable rom zip not nand backup.once is pushed it should take awhile,youll go to install like any other custom rom from the install menu. Or if you cant get that going use adb sideload command
Make sure command is correct
adb push nameofrom.zip /sdcard/.
Dumb question. Where in the world do I find the stock recovery zip? I can't find any zip...only img, etc.
You dont need stock recovery right now follow instructions to get a rom back on the device first...download any custom rom and follow what i said
---------- Post added at 12:56 AM ---------- Previous post was at 12:54 AM ----------
Guy in my rom thread had basically same issue hes back up and running by following what ive told you
Wonders_Never_Cease said:
You dont need stock recovery right now follow instructions to get a rom back on the device first...download any custom rom and follow what i said
---------- Post added at 12:56 AM ---------- Previous post was at 12:54 AM ----------
Guy in my rom thread had basically same issue hes back up and running by following what ive told you
Click to expand...
Click to collapse
Thanks for the help. Downloading your ROM now.
If you can get in recovery choose the option "adb sideload" put the ROM on your desktop and name it rom. Then in a command window type adb sideload rom.zip , TWRP will automatically recognize the update script and flash it for you.
Sent from my HTC One_M8 using Tapatalk
I took the direction of Wonders_Never_Cease and followed it to the letter. FUBAR no longer. Though I did panic a little, I learned a lot from this direction going forward. Thanks, Wonders_Never_Cease. Thanks also to everyone else who offered help.
Glad it all worked out for you...
ImNraged said:
I took the direction of Wonders_Never_Cease and followed it to the letter. FUBAR no longer. Though I did panic a little, I learned a lot from this direction going forward. Thanks, Wonders_Never_Cease. Thanks also to everyone else who offered help.
Click to expand...
Click to collapse
Wonders_Never_Cease said:
Glad it all worked out for you...
Click to expand...
Click to collapse
Not so much. I've run into another problem while trying to get it back to where I want it. SD Card will not mount. What can I do?
Aaaaand, nevermind. Youtube was my friend in this case.
Wonders_Never_Cease said:
You dont need stock recovery right now follow instructions to get a rom back on the device first...download any custom rom and follow what i said
---------- Post added at 12:56 AM ---------- Previous post was at 12:54 AM ----------
Guy in my rom thread had basically same issue hes back up and running by following what ive told you
Click to expand...
Click to collapse
I don't think he was asking that. I am pretty sure he was asking where he managed to find the stock recovery, which is why the red exclamation, probably because he didn't pull or nand the recovery as a raw or img file before flashing something custom (the user that asked, that is).
I doubt is is a stock AT&T ship recovery from an RUU dump or ota, since there haven't been any for AT&T that I know of yet, so it's likely just a raw dump or was part of the nand backup he restored.
Already been sorted thank you fot you insight
GSLEON3 said:
I don't think he was asking that. I am pretty sure he was asking where he managed to find the stock recovery, which is why the red exclamation, probably because he didn't pull or nand the recovery as a raw or img file before flashing something custom (the user that asked, that is).
I doubt is is a stock AT&T ship recovery from an RUU dump or ota, since there haven't been any for AT&T that I know of yet, so it's likely just a raw dump or was part of the nand backup he restored.
Click to expand...
Click to collapse
So out of curiosity I went to the ZTE USA website and checked when the next batch of Axon 7's would ship as I wanted to buy another one (don't judge) and I go down to Support, Software updates, and I see this(attached):
Is this the stock image that ZTE said they would post? It sure looks like it as its almost 2GB in size
Link: https://www.zteusa.com/axon-7
Thanks for the heads-up. Interesting that they would post an image for B20, not one of a later version.
xtermmin said:
Thanks for the heads-up. Interesting that they would post an image for B20, not one of a later version.
Click to expand...
Click to collapse
What's interesting is that they haven't announced it yet
This looks like the factory image of the B20 pre-bootloader. I'm downloading the zip now, so we'll know more after analysts. So much about getting B27 or B29 as factory, but makes sense since that's where the sig change happened. And it specifically mentions it as image for fixing OTA failures because of B20_Boot OTA
It could be what we have been hoping for - at least that is a factory image. We can always use their OTA system to update from there
---------- Post added at 09:26 PM ---------- Previous post was at 08:56 PM ----------
DrakenFX - check this out here. I just downloaded it and took a look at the updater script in it. This may help with an instruction set for turning future OTA updates into TWRP flashable zips.
we need to get this updated here:
http://forum.xda-developers.com/axon-7/development/axon-7-chinese-stock-roms-t3436817
Well what do you know its announced: https://community.zteusa.com/thread/13133
bkores said:
Well what do you know its announced: https://community.zteusa.com/thread/13133
Click to expand...
Click to collapse
So with this image, how would you flash it to a bricked phone? Do you have to have access to recovery to use the file as posted?
Nice find @bkores , posted on the 10/26 .....still this can be very helpful
imp3r10 said:
So with this image, how would you flash it to a bricked phone? Do you have to have access to recovery to use the file as posted?
Click to expand...
Click to collapse
I guess you do as you have to update from the sd card. I don't know why they couldn't have made it fastboot flashable but you should be able to flash the boot and recovery inside the zip with fastboot. As for the system I think you can convert the system.new.dat to system.img with some program and then flash. Someone feel free to correct me on this.
Can devs start "cooking" this? Removing stock apps etc etc?
bkores said:
I guess you do as you have to update from the sd card. I don't know why they couldn't have made it fastboot flashable but you should be able to flash the boot and recovery inside the zip with fastboot. As for the system I think you can convert the system.new.dat to system.img with some program and then flash. Someone feel free to correct me on this.
Click to expand...
Click to collapse
This is basically a full (not-OTA) update file for B20 version. It is really only good for downgrades to fix soft brick where your recovery is still accessible or to get OTAs. It will not help with bricks where phone won't boot past ZTE logo or into fastboot. It will also not help with stock mods since zip file is signed. And it cannot be flashed via EDL or DFU mode. I hope this is not the thing they were talking about when they posted that meme with brick wall and stock market recovery.
For fastboot restore, we would need new fastboot image, since i think there is a flash (or pull) limit on file size in the current one around 500MB or so IIRC
---------- Post added at 03:49 PM ---------- Previous post was at 03:41 PM ----------
nsane said:
Can devs start "cooking" this? Removing stock apps etc etc?
Click to expand...
Click to collapse
Since this is a signed zip, there is no modifying it. Flashing modded rom would still require TWRP and could already be done since we have full /system dumps. And to use this to save you from bad flash, you will need to have access to recovery. TWRP could flash it i guess, but if you are in bootloader loop then not much help
This will remove the unlocked bootloader from your device at this time
Click to expand...
Click to collapse
I'm guessing this is because it replaces the emmc_appsboot.mbn / aboot file? Wonder if one can just delete that line from the flashing script to keep it unlocked.
peramikic said:
This is basically a full (not-OTA) update file for B20 version. It is really only good for downgrades to fix soft brick where your recovery is still accessible or to get OTAs. It will not help with bricks where phone won't boot past ZTE logo or into fastboot. It will also not help with stock mods since zip file is signed. And it cannot be flashed via EDL or DFU mode. I hope this is not the thing they were talking about when they posted that meme with brick wall and stock market recovery.
For fastboot restore, we would need new fastboot image, since i think there is a flash (or pull) limit on file size in the current one around 500MB or so IIRC
---------- Post added at 03:49 PM ---------- Previous post was at 03:41 PM ----------
Since this is a signed zip, there is no modifying it. Flashing modded rom would still require TWRP and could already be done since we have full /system dumps. And to use this to save you from bad flash, you will need to have access to recovery. TWRP could flash it i guess, but if you are in bootloader loop then not much help
Click to expand...
Click to collapse
If you are stuck on the ZTE logo on a bootloop, couldn't you use tenfar's tool to flash stock recovery and then use this full image to flash stock B20? It does have a boot.img in it that it installs during this process.
peramikic said:
This is basically a full (not-OTA) update file for B20 version. It is really only good for downgrades to fix soft brick where your recovery is still accessible or to get OTAs. It will not help with bricks where phone won't boot past ZTE logo or into fastboot. It will also not help with stock mods since zip file is signed. And it cannot be flashed via EDL or DFU mode. I hope this is not the thing they were talking about when they posted that meme with brick wall and stock market recovery.
For fastboot restore, we would need new fastboot image, since i think there is a flash (or pull) limit on file size in the current one around 500MB or so IIRC
---------- Post added at 03:49 PM ---------- Previous post was at 03:41 PM ----------
Since this is a signed zip, there is no modifying it. Flashing modded rom would still require TWRP and could already be done since we have full /system dumps. And to use this to save you from bad flash, you will need to have access to recovery. TWRP could flash it i guess, but if you are in bootloader loop then not much help
Click to expand...
Click to collapse
I am bootloader unlock and have TWRP.
I hope that Devs start "cooking" stock ROMS. Taking out system apps. Bloat etc etc
Kernel development would also be nice
*fingers crossed*
I'm really happy that they did something, but why couldn't they have just compressed the boot, recovery, and system img files into a tar file like Google does with their Nexus/Pixel devices? That way we would've been able to flash them in fastboot mode which could've fixed almost any brick with the exception of EDL/DFU mode in which case we could have used tenfar's tool.
If you remove this from the updater-script inside the update.zip, it is even flashable with TWRP takes some time to flash but it works!
Code:
getprop("ro.product.device") == "ailsa_ii" || abort("This package is for \"ailsa_ii\" devices; this is a \"" + getprop("ro.product.device") + "\".");
assert(getprop("ro.product.name") == "P996A01");
ui_print("Target: ZTE/P996A01/ailsa_ii:6.0.1/MMB29M/20160707.171254:user/release-keys");
show_progress(0.850000, 180);
i believe i mention this somewhere, been crazy busy for me today
* You can either Flashed using TWRP or Install using Stock System Update app or Install using Stock recovery.
but that B20 update.zip will get you to Complete B20 software.
Click to expand...
Click to collapse
beside that here are a few good point of what is going to happen :
-However you will not be able to update to newer builds just yet.
-SD card update will erase everything on your device. (but i'm sure External Storage (SDCard) is safe )
-We recommend only users with advanced skills use this file.
Click to expand...
Click to collapse
so anyone who want to use that file need to take that in consideration.
DrakenFX said:
i believe i mention this somewhere, been crazy busy for me today
beside that here are a few good point of what is going to happen :
so anyone who want to use that file need to take that in consideration.
Click to expand...
Click to collapse
You can just remove the format line inside the updater-script to keep your data
bkores said:
You can just remove the format line inside the updater-script to keep your data
Click to expand...
Click to collapse
LoL, just notice that line ....haven't had time to bother and check the file , but yeah just need to remove
Code:
format("ext4", "EMMC", "/dev/block/bootdevice/by-name/userdata", "0", "/data");
but still, internal storage will be is safe but you'll still need to wipe data and reinstall app (Encryption thing)