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
Anyone know where I can find the AT&T Factory ROM i forgot to do a backup and need to put this ROM back on the device.
i can not find it.maybe few months later,you can get it here.
Is it weird that there's no RUU? It's been a while since I had an GTC phone so I don't remember how long it took to have one on a new phone.
gunnyman said:
Is it weird that there's no RUU? It's been a while since I had an GTC phone so I don't remember how long it took to have one on a new phone.
Click to expand...
Click to collapse
I feel like it is weird, though the One is the only device I got close to release. My Vivid and Inspire were both purchased a few months after release, and iirc the ATT RUUs were available when I got it, but I guess that doesn't mean they were available at release.
Wasuhz said:
Anyone know where I can find the AT&T Factory ROM i forgot to do a backup and need to put this ROM back on the device.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2242319&highlight=stock
I flashed the odex version and returned it to AT&T. Worked like a charm. Unfortunately no one has posted the stock AT&T recovery but I used the stock international version. You can find that here:
http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
Actually, this leads to a nagging question I have as a first time rooter. I want to use the stock ATT Rom, but root the phone so I can install apps than requre root access and am all about taking back total contole of my device.
SO If I want to keep the stock rom and just root it, I would need to back up the device?
So if someone could throw me a bone How would I gain root access to the device whilst keeping the stock ROM?
I plan on using Hasoon's Tool kit.
android_lurker said:
Actually, this leads to a nagging question I have as a first time rooter. I want to use the stock ATT Rom, but root the phone so I can install apps than requre root access and am all about taking back total contole of my device.
SO If I want to keep the stock rom and just root it, I would need to back up the device?
So if someone could throw me a bone How would I gain root access to the device whilst keeping the stock ROM?
I plan on using Hasoon's Tool kit.
Click to expand...
Click to collapse
flash the stock rom through recovery and then flash superuser.zip in recovery. boom. rooted on stock
If you are completely stock then Once you unlock your bootloader flash twrp recovery. Then boot to recovery. Then reboot from recovery. Twrp is smart enough to recognize you don't have root and prompt you to install superuser and binaries. After that I found a busybox flashable zip via google, as the busybox installer from the market wouldn't work for me. This leaves you on a stock odexed Rom with root. Note that unlocking your bootloader will wipe data..so backup anything important first
Sent from my HTC One using Tapatalk 2
sk8erwitskil said:
flash the stock rom through recovery and then flash superuser.zip in recovery. boom. rooted on stock
Click to expand...
Click to collapse
oh hell yes thank you for the assistance.
so I will flash the stock rom instead of say CWM then flash supersu after that? Where do I like "get" the stock rom from? will it already be on the sd card?
Delete me..
grukko said:
http://forum.xda-developers.com/showthread.php?t=2242319&highlight=stock
I flashed the odex version and returned it to AT&T. Worked like a charm. Unfortunately no one has posted the stock AT&T recovery but I used the stock international version. You can find that here:
http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
Click to expand...
Click to collapse
Hi i just want to know how do you flash the stock odex?
BADBOY1412 said:
Hi i just want to know how do you flash the stock odex?
Click to expand...
Click to collapse
i just used twrp. after that i flashed the stock recovery back using fastboot.
grukko said:
i just used twrp. after that i flashed the stock recovery back using fastboot.
Click to expand...
Click to collapse
If you're talking about the ATT stock recovery, Can you please post it....I been looking for that
android_lurker said:
oh hell yes thank you for the assistance.
so I will flash the stock rom instead of say CWM then flash supersu after that? Where do I like "get" the stock rom from? will it already be on the sd card?
Click to expand...
Click to collapse
1) unlock bootloader
2) fastboot flash cwm (you can use the shiny new one i just posted in the orig dev section )
3) boot to recovery and make a backup
4) flash the pre-rooted stock rom here http://forum.xda-developers.com/showthread.php?t=2242319
5) reboot and enjoy
grukko said:
http://forum.xda-developers.com/showthread.php?t=2242319&highlight=stock
I flashed the odex version and returned it to AT&T. Worked like a charm. Unfortunately no one has posted the stock AT&T recovery but I used the stock international version. You can find that here:
http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
Click to expand...
Click to collapse
did the international stock recovery work for you ? i was able to flash it but when i try to go into recovery its just black screen no recovery. Your reply appreciated
Thanks
If you flash stock recovery successfully and you try to boot to said recovery, you won't have any options to do anything. I never cared to look at it on this device but usually all you'll see is a triangle with an exclamation point. That's stock recovery. If you want to flash anything, you can't use stock
Sent from my HTC One using Tapatalk 2
Not sure what's up but I have been searching all over the work pc's for a HTC one ruu with no damn luck even talked to a few buddies in tech support and they have not seen one as of yet
Sent from my HTC One using Tapatalk 2
homeslice976 said:
If you flash stock recovery successfully and you try to boot to said recovery, you won't have any options to do anything. I never cared to look at it on this device but usually all you'll see is a triangle with an exclamation point. That's stock recovery. If you want to flash anything, you can't use stock
Sent from my HTC One using Tapatalk 2
Click to expand...
Click to collapse
cool , i was confused because i have only used samsung phones before and their stock recovery has some menu options to do factory reset etc.
Stock recovery has a menu, just press volume up.
grukko said:
http://forum.xda-developers.com/showthread.php?t=2242319&highlight=stock
I flashed the odex version and returned it to AT&T. Worked like a charm. Unfortunately no one has posted the stock AT&T recovery but I used the stock international version. You can find that here:
http://android-revolution-hd.blogspot.com/p/android-revolution-hd-mirror-site-var.html
Click to expand...
Click to collapse
I don't think anyone's still following this thread, but did you relock the bootloader before returning it? i was thinking of just flashing recovery back. I don't think anyone at the store would bother to look at that anyway. Whenever I go there, the employees seem to know less than nothing about phones lol.
Hi,
I'm using only stock rom, rooted and with xposed mods on my Nexus devices. Because of trying some things out, I want to have a stock rom update.zip from the latest Factory Image on my device to have the security to flash it back to stock without a computer.
So, I've managed with some help this update.zip. It's absolutely pure stock. Not rooted, not deodexed or anything else (to root, there is a link below)
I think, some of you are thinking the same and so I want to share this update zip. I hope you have fun with it.
It works with CWM and TWRP Recovery!
Romversion
KOT49H Hammerhead
Tweaks / Changes
Nothing
Download
Stock ROM KOT49H Hammerhead
MD5 Checksum: 864626c54510b0c0eb3dac8a23e66f45
Thanks to
vetzki
caho
for their kindly help!
Infos
- You want root, you only have to flash, this file here, too: SuperSU Download
- the install process is slow. Please wait, it really installs. It takes about 5 Minutes. If someone has the ability to show me how to make it faster: Please, please!!!
Have Fun!
So, do you recommend a full wipe and cache clear when installing this?
Let's say I want to go stock in anticipation of a new update to android. I would go to Recovery (I use twrp), wipe data/erase everything from my previous rom, and then flash update.zip (and supersu at the same time), and I'll be set with stock everything including kernel, etc?
You won't be able to get an update with a rooted rom. Google checks before sending the files that your rom matches the md5
Sent using reversed alien technology...
howard bamber said:
You won't be able to get an update with a rooted rom. Google checks before sending the files that your rom matches the md5
Sent using reversed alien technology...
Click to expand...
Click to collapse
Well, question still stands. I still want to ensure this thing catches kernels and everything else provided I do a full wipe, and I assumed a full wipe is recommended (as with most things on this site). I wanted to get clarification before hand.
xybur said:
Well, question still stands. I still want to ensure this thing catches kernels and everything else provided I do a full wipe, and I assumed a full wipe is recommended (as with most things on this site). I wanted to get clarification before hand.
Click to expand...
Click to collapse
Yes if you want to flash the ROM you should do a full wipe just in case there are any mods left over from the previous ROM/kernel.
What the previous poster was informing you of is that flashing this ROM won't give you the update directly from Google itself. You will need to flash the new update manually as the md5 sum gets checked when they send out updates.
It's nothing to worry about just flash the new update when it comes. Most of the time you can flash the new update before Google would send it out to your phone anyways.
Mo'HAWK said:
Yes if you want to flash the ROM you should do a full wipe just in case there are any mods left over from the previous ROM/kernel.
What the previous poster was informing you of is that flashing this ROM won't give you the update directly from Google itself. You will need to flash the new update manually as the md5 sum gets checked when they send out updates.
It's nothing to worry about just flash the new update when it comes. Most of the time you can flash the new update before Google would send it out to your phone anyways.
Click to expand...
Click to collapse
Gotcha, thanks for the help/clarification.
As far as I know, google send updates to rooted devices, too.
But I don't want to swear
A full wipe is indeed better if you come from another rom.
But with a nandroid backup, you can try.
Sent from my IPhone 7s
howard bamber said:
You won't be able to get an update with a rooted rom. Google checks before sending the files that your rom matches the md5
Click to expand...
Click to collapse
FormelLMS said:
As far as I know, google send updates to rooted devices, too.
But I don't want to swear
Click to expand...
Click to collapse
Hello,
All is here about OTA and root: [INFO] Nexus 5 OTA Help-Desk...
Thanks!
So it's right.
Flash this rom, don't delete or change a file. No new Kernel and you can receive the update.
Sent from my IPhone 7s
howard bamber said:
You won't be able to get an update with a rooted rom. Google checks before sending the files that your rom matches the md5
Sent using reversed alien technology...
Click to expand...
Click to collapse
very wrong. first off, Google does not check. secondly, you can get an update while having root, as long as you do not change system files. why do you think we get so many "i updated ota and lost root" threads?
I'm just curious, I thought that the recovery was supposed to be stock to receive ota updates? Tia
Sent from my Nexus 5 using JellyBombed Tapatalk 2
Would you care to share how did you make flashable stock room?
Sent from my Nexus 5 using Tapatalk
Hey,
this thread here shows the most:
http://forum.xda-developers.com/showthread.php?t=2285831
You have to know, that you need the extracted system.img as the system folder in your update.zip.
Then you need the boot.img unextracted.
This is a all easy. A bit complicated is the meta-inf folder.
I've used this folder from other aosp roms.
I have to learn that now, too.
Sent from my IPhone 7s
Download link not working????
Sent from my Nexus 5 using XDA Free mobile app
I'll try and keep this short and to the point. If you unlocked your bootloader and flashed TWRP and SuperSU, theirs a Good chance your phone will not return to stock and take OTA updates. Many of us have tried but for some reason the updates just fail.
Well we are lucky and someone captured and posted the 3 known updates and I'm going to show you how to flash them
New ~ All in One ~ update Instructions in Post 2
We now have a new way to do this, So the information below is just for information sake So bare with me while I get the Guide updated...
Other Files you may need
H1611.TWRP.New.img <<- This is the New Twrp by yuweng I Highly recommend everyone use this Version
minimal_adb_fastboot_v1.4.1_setup.exe
Huawei_Android_phone_drivers(1).rar
I have been working on this for some time and I now have an ALL in One Flash solution
This will allow you to flash a Single Rom to Update or Downgrade your firmware and Rom
As with any firmware update or downgrade I'm not responsible to what happens to your phone you do this at your own risk
(rest assured I have tested all these files and my phone is fine)
The Flash instructions are the same as any rom flash on this phone
Step one is to Boot to the bootloader and boot H1611.TWRP.New.img
fastboot boot H1611.TWRP.New.img
Swipe to allow modifications to System
then choose Mount and check system and cust
Select Storage Micro SDcard
Next is install and choose your Bxxx_Full_Update.zip
Swipe to flash
Reboot
That's really all their is too it, Just choose the File below that you want to update or downgrade too
Note: The phone always loads the AT&T logo and reboots the first time and then loads normally
First boot will take you to the setup screen if you formatted data
Another thing i noticed while test flashing these files is that the Data partition becomes Encrypted after the flash
This means before you can restore a data backup or flash a Rom like CleanRom (it includes data) you'll need to Format Data to UN-encrypt it
Also some roms may need to have SuperSU flashed after the Rom or the phone may not boot the first time after the upgrade.
AS Always make a complete backup of your phone before you start any flashing
Downloads
~New~ B180_Full_Update.zip
Note about B180 - If you have no wifi or the phone won't boot simply extract the boot.img from the rom and flash it with TWRP (Install Image) or fastboot (fastboot flash boot boot.img) also the AT&T Logo is missing for now but everything else works
Thanks To @madvane20 Download >> B170 Stock Full Update with Firmware
B160_Full_Update.v2.zip
B150_Full_Update.zip
I had to make B140 into 2 flashes but it works the same just copy both files to your phone and Flash A then B
B140_Full_Update.A.zip
B140_Full_Update.B.zip
B130_Full_Update.zip
Huge thanks to @madvane20 for helping with the partition layouts and testing and to @worstenbrood for the Huawei Update Extractor tool
Where do I start if I have B140 rooted on my XT? Maybe some numbers or section titles would help answer that. Thanks .
divineBliss said:
Where do I start if I have B140 rooted on my XT? Maybe some numbers or section titles would help answer that. Thanks .
Click to expand...
Click to collapse
You start at the 2nd half of the updated guide B140 to B150
the process is the same no matter what version your on
So I should start with B130 stock files even though I'm in B140 rooted right now?
clsA said:
You still start at the top and substitute the B150 files where their needed
the process is the same no matter what version your on
Click to expand...
Click to collapse
divineBliss said:
So I should start with B130 stock files even though I'm in B140 rooted right now?
Click to expand...
Click to collapse
... no you would start at returning your phone to Stock B140 and continue from their
flashing the B150 firmware then the B150 stock system and /cust
We have the B150 files and the guide is updated
If I can get back to B140 stock and take the B150 OTA, which files do you need?
clsA said:
The guide is not complete ... no you would start at returning your phone to Stock B140 and continue from their
flashing the B150 firmware then the B150 stock system and /cust
We don't have the B150 files yet so it's hard to complete the guide
Click to expand...
Click to collapse
divineBliss said:
If I can get back to B140 stock and take the B150 OTA, which files do you need?
Click to expand...
Click to collapse
is that a trick question ? if you could get back to stock and take the OTA this post wouldn't be necessary now would it ?
The whole point of the thread is that no one who rooted has been able to return to stock and take an OTA
Why bother updating? Isn't someone working in Lineage for this phone?
guest_2011 said:
Why bother updating? Isn't someone working in Lineage for this phone?
Click to expand...
Click to collapse
no one has posted any threads about it
you should still try and be on the latest security patch while you phone is stock
@RN_ReFlux Thank You ! for getting the B150 backup and /cust.img
guest_2011 said:
Why bother updating? Isn't someone working in Lineage for this phone?
Click to expand...
Click to collapse
Yes, someone is working on it but it is best to have your ROM up to date. You may not see a need for it but a lot of others see a need.
clsA said:
@RN_ReFlux any luck getting the B150 backup and /cust.img ?
Click to expand...
Click to collapse
Yes, I have them, am working on zipping some of the larger files, then will upload to drive or dropbox, since I don't have developer access to afh yet.
Only think I forgot to do was get the post-root backup in TWRP. If you need that, I've already asked my cousin to perform the backup, I'll ask her to zip and upload them to me.
RN_ReFlux said:
Yes, I have them, am working on zipping some of the larger files, then will upload to drive or dropbox, since I don't have developer access to afh yet.
Only think I forgot to do was get the post-root backup in TWRP. If you need that, I've already asked my cousin to perform the backup, I'll ask her to zip and upload them to me.
Click to expand...
Click to collapse
Thanks ... I'll post the files to my AFH account if you can share them through google or dropbox ..etc
If you request developer access, it doesn't take that long to get it ........ a few hour maybe if I recall correctly .
RN_ReFlux said:
Yes, I have them, am working on zipping some of the larger files, then will upload to drive or dropbox, since I don't have developer access to afh yet.
Only think I forgot to do was get the post-root backup in TWRP. If you need that, I've already asked my cousin to perform the backup, I'll ask her to zip and upload them to me.
Click to expand...
Click to collapse
divineBliss said:
If you request developer access, it doesn't take that long to get it ........ a few hour maybe if I recall correctly .
Click to expand...
Click to collapse
Requested it about 12 hours ago
Uploading to drive now.
Sent from my SM-T530 using Tapatalk
divineBliss said:
...
Click to expand...
Click to collapse
All the files are uploaded for your B140 to B150 update...
I'll be updating the guide soon.
The steps in a nutshell are
flash your stock B140 system/boot/recovery and stock b140 /cust
force flash the dload/update.app for b150 with the dialer code
boot TWRP restore stock B150 system and dd the B150 /cust
Flash SuperSU and Factory Reset (< optional)
reboot system and it boots to a clean B150
Click to expand...
Click to collapse
Guide is updated !
Has anyone been able to follow the OP to get up to B150 from either B140 or B130? Or even B130 to B140? Thanks!
clsA said:
All the files are uploaded for your B140 to B150 update...
I'll be updating the guide soon.
The steps in a nutshell are
Guide is updated !
Click to expand...
Click to collapse
divineBliss said:
Has anyone been able to follow the OP to get up to B150 from either B140 or B130? Or even B130 to B140? Thanks!
Click to expand...
Click to collapse
Yeah me
Sent from my Nexus 6P using Tapatalk
Be careful upgrading from B130 to B140. Went from stock non-rooted B130 to B140 using the SD card update method and hidden menu. While it went through the update process without reporting an error but after auto reboot it still showed the same version but lost WIFI functionality, mac address showed mostly 00s and can't restore full backup from TWRP without errors on /data, etc.
Anyone know if there are .img equivalent of 2017-01-26-H1611.B130.stock.complete to attempt restore from either fastboot flash or dd?
OTA zip (Qualcomm) retail 3.3.2018 "Blur_Version.26.11.27.owens.retail.en.US"
Hello everyone. I saw that there was an update pending on my Moto E4 Plus today so I DLed it and put it into OneDrive. I don't have much time available to do much with it for now but in case anyone else can do something with it, you can DL it HERE.
Chad The Pathfinder said:
Hello everyone. I saw that there was an update pending on my Moto E4 Plus today so I DLed it and put it into OneDrive. I don't have much time available to do much with it for now but in case anyone else can do something with it, you can DL it HERE.
Click to expand...
Click to collapse
Thanks, @Chad The Pathfinder. Good to see you here.
I'm on boost mobile e4 plus stock but rooted. Is this zip for twrp flashing to bring rooted stock versions up to date?
shezzy83 said:
I'm on boost mobile e4 plus stock but rooted. Is this zip for twrp flashing to bring rooted stock versions up to date?
Click to expand...
Click to collapse
It is for the retail XT1775 only. It's an official OTA update.
---------- Post added at 06:21 PM ---------- Previous post was at 05:40 PM ----------
Chad The Pathfinder said:
Hello everyone. I saw that there was an update pending on my Moto E4 Plus today so I DLed it and put it into OneDrive. I don't have much time available to do much with it for now but in case anyone else can do something with it, you can DL it HERE.
Click to expand...
Click to collapse
I can probably make this work to flash with TWRP, but you'll need to have your system, oem and boot.img original stock before flashing. If anyone is willing to test it for me, I will modify the ota zip when I have a chance. I have the Boost XT1766 so I can't test it myself. Let me know if anyone is willing to test it because if not, I won't waste my time modifying the ota.
Sent from my Moto E (4) Plus using XDA Labs
I'm willing to try it. I'm a little confused about the requirements you mentioned though. I'm on stock but with a few modifications I've made here and there. Would I need to uninstall Magisk?
Chad The Pathfinder said:
I'm willing to try it. I'm a little confused about the requirements you mentioned though. I'm on stock but with a few modifications I've made here and there. Would I need to uninstall Magisk?
Click to expand...
Click to collapse
If you look inside the ota zip, there are patches for the boot.img, system.img, oem.img, modem.img, etc. If you don't have the original stock versions of these it may fail to install properly and will likely cause problems. Hence the reason for the asserts in the OTA zip to check for the proper unmodified versions of these. If I had the XT1775 I would just flash stock firmware and update officially then pull the imgs, make an updated stock ROM with the system and boot, and make an make a twrp flashable ota zip with the other modem, fsg and oem.imgs. So, you basically have to do the same as if you were going to update officially minus reflashing stock recovery. You almost might as well just flash your latest stock firmware and take the ota update, then pull the modem, fsg and oem and make a system and boot backup with twrp which I can make an updated ROM and twrp flashable ota for others to update without that hassle. Your choice. I asked another user to provide me with a backup after they updated, but they had to go somewhere for a few days and said they would when they returned. I could give you a stock ROM flashable so you don't have to flash firmware with fastboot. I already have one made, I just haven't uploaded and posted it yet.
Sent from my Moto E (4) Plus using XDA Labs
Goose03 said:
If you look inside the ota zip, there are patches for the boot.img, system.img, oem.img, modem.img, etc. If you don't have the original stock versions of these it may fail to install properly and will likely cause problems. Hence the reason for the asserts in the OTA zip to check for the proper unmodified versions of these. If I had the XT1775 I would just flash stock firmware and update officially then pull the imgs, make an updated stock ROM with the system and boot, and make an make a twrp flashable ota zip with the other modem, fsg and oem.imgs. So, you basically have to do the same as if you were going to update officially minus reflashing stock recovery. You almost might as well just flash your latest stock firmware and take the ota update, then pull the modem, fsg and oem and make a system and boot backup with twrp which I can make an updated ROM and twrp flashable ota for others to update without that hassle. Your choice. I asked another user to provide me with a backup after they updated, but they had to go somewhere for a few days and said they would when they returned. I could give you a stock ROM flashable so you don't have to flash firmware with fastboot. I already have one made, I just haven't uploaded and posted it yet.
Sent from my Moto E (4) Plus using XDA Labs
Click to expand...
Click to collapse
Sure. If you want to send me the flashable you have I'll do that tonight and see what happens.
Chad The Pathfinder said:
Sure. If you want to send me the flashable you have I'll do that tonight and see what happens.
Click to expand...
Click to collapse
I'll have to modify the ota zip for you first so you can flash it after the stock ROM. As soon as I have a chance to, I'll upload that and the stock ROM zip for you. You didn't modify your oem partition at all did you? If so, I'll give you a flashable oem zip to restore that back the way it was also. Just make sure you have stock firmware ready to flash with fastboot in case something doesn't go right. Most of the ota is modem related, no bootloader patches, so it should work fine and hard bricking shouldn't be a concern.
Sent from my Moto E (4) Plus using XDA Labs
Goose03 said:
I'll have to modify the ota zip for you first so you can flash it after the stock ROM. As soon as I have a chance to, I'll upload that and the stock ROM zip for you. You didn't modify your oem partition at all did you? If so, I'll give you a flashable oem zip to restore that back the way it was also. Just make sure you have stock firmware ready to flash with fastboot in case something doesn't go right. Most of the ota is modem related, no bootloader patches, so it should work fine and hard bricking shouldn't be a concern.
Sent from my Moto E (4) Plus using XDA Labs
Click to expand...
Click to collapse
I did not modify the oem partition. I've just made small changes like changed the boot animation, splash screen and some other things like that. Nothing major. have attempted to make a deodex version with a couple of different kitchens to make some other changes but haven't had enough time to really get into anything.
Chad The Pathfinder said:
I did not modify the oem partition. I've just made small changes like changed the boot animation, splash screen and some other things like that. Nothing major. have attempted to make a deodex version with a couple of different kitchens to make some other changes but haven't had enough time to really get into anything.
Click to expand...
Click to collapse
I'm uploading the ROM now. I just got done modifying the ota zip and I'll give you links as soon as they're done uploading. I made a deodexed Sprint variant version. Was planning on deodexing the retail version also. I may as well wait for the newer version though. The trick is, you need to deodexed the oem apps and framework also or it won't boot.
Sent from my Moto E (4) Plus using XDA Labs
Thanks. I'm in town right now. I'll check when I get home and flash if its ready. If all goes well, you want me to send you a twrp backup of boot and system only right?
Chad The Pathfinder said:
Thanks. I'm in town right now. I'll check when I get home and flash if its ready. If all goes well, you want me to send you a twrp backup of boot and system only right?
Click to expand...
Click to collapse
Yes. It'll be a little while, uploads are going really slow and keep failing on AFH. I had it almost uploaded twice and it keeps failing.
Sent from my Moto E (4) Plus using XDA Labs
I couldn't even log into AFH earlier. That's why I used OneDrive in the op.
Chad The Pathfinder said:
I couldn't even log into AFH earlier. That's why I used OneDrive in the op.
Click to expand...
Click to collapse
I have been having issues uploading to AFH too. Man, I wish they would finally get this fixed.
Chad The Pathfinder said:
I couldn't even log into AFH earlier. That's why I used OneDrive in the op.
Click to expand...
Click to collapse
Finally got it
ROM: https://www.androidfilehost.com/?fid=746010030569959248
OTA:
So, here's what I want you to do.
1. Make a backup before you do anything.
2. Flash a Magisk uninstaller.
3. Flash the ROM. (if it should fail to flash, please get a recovery log so I can see exactly what failed.)
4. Flash the OTA zip. (again, if it should fail to flash, please get a recovery log so I can see exactly what failed.)
5. If everything flashes ok, reboot recovery to make sure you don't lose twrp.
6. Make a system backup.
7. Use fastboot to pull the boot.img, modem.img, fsg.mbn, and the oem.img.
Edit: actually, if you could pull everything you see in a stock firmware package and pull them so they have the same name and file extension, that would be great.
I'll be working until about 8 tonight. (3.5.18) I'll work on it tonight and let you know what happens.
Edit: I managed to get the "Blur_Version.26.11.27.owens.retail.en.US--XT1775_TWRP_flashable" down loaded but the other was taking too long and failed a couple of times. I will try again when I can.
so glad you guys are working on this My daughter and her moms xt1775 just popped the update message and im not "allowed" to work on them too often so i cant experiment with you. So a twrp flashable update would be great if i dont have to unroot reroot stock.img etc etc it will be a painless (for me) update.
A Sort-of Related Question
I installed the update by using RSD Lite to go back to stock, taking the update as an OTA, then reflashing TWRP and Magisk. All was fine, until I tried to restore a back up. Which failed, unable to mount System. Thereafter, all reboots take me to Bootloader. I can't use RSD Lite again, as I have updated to a later version. (Believe me, I have tried multiple times!) I tried flashing the two zips, but I fail at the OTA. I was able to load Lineage, which works, but still reboots to Bootloader, then to the ROm.
I have tried fastboot oem fb_mode_clear via both ADB and TWRP Terminal but that fails as well.
Any thoughts on clearing this?
NEVER MIND - Tried a different PC and the mode clear command worked! Whew! The good news is that is something that might be worth trying if you get stuck.
koop1955 said:
I installed the update by using RSD Lite to go back to stock, taking the update as an OTA, then reflashing TWRP and Magisk. All was fine, until I tried to restore a back up. Which failed, unable to mount System. Thereafter, all reboots take me to Bootloader. I can't use RSD Lite again, as I have updated to a later version. (Believe me, I have tried multiple times!) I tried flashing the two zips, but I fail at the OTA. I was able to load Lineage, which works, but still reboots to Bootloader, then to the ROm.
I have tried fastboot oem fb_mode_clear via both ADB and TWRP Terminal but that fails as well.
Any thoughts on clearing this?
NEVER MIND - Tried a different PC and the mode clear command worked! Whew! The good news is that is something that might be worth trying if you get stuck.
Click to expand...
Click to collapse
The modified ota zip I posted failed to flash? Did you happen to get a recovery log?
Sent from my Moto E (4) Plus using XDA Labs
Goose03 said:
The modified ota zip I posted failed to flash? Did you happen to get a recovery log?
Sent from my Moto E (4) Plus using XDA Labs
Click to expand...
Click to collapse
Of course, sent to you via PM.
I don't think that it is a quality of your zip, I think it is related to my earlier attempt at installing the OTA itself.