Related
Hello, sorry for the title error (2.3.6).
This is the way to restore your Nexus One to 100% stock Android 2.3.6, waiting ICS Android 4 official OTA updates (if there will be one).
This rom contains:
hboot
radio
recovery
system ...
(all things return stock except the unlocked bootloader but it isn't a problem)
Thank to Football for the rom e to the XDA wiki for the guide. I decided to create this thread for who is in truble (as me some days ago) and for who wants to return stock before the possible relasing of ICS. Before everything backup your data (and sd card for security) and from custom recovery do:
-wipe battery stats (if you want)
-wipe data and cache
-wipe dalvik cache
Now:
1)Download the shipped rom GRK39F from PASSIMG_Passion_Google_WWE_3.13.1700.1_GRK39F_relase_signed.zip
2)Rename the downloaded ZIP file to PASSIMG.ZIP.
3)Transfer the provided PASSIMG.ZIP file to the root of your SD card.
4)Power down your phone.
5)Hold down the Volume Down button as you power your phone back on.
6)A screen should appear showing your phone's system searching for various files. This will take up to 2 minutes.
7)The phone will ask you if you want to start the update. Press the Volume Up button to start the update.
8)If you followed these steps correctly - congratulations, you are now on stock 2.3.6 ROM.
MD5: 3052bd01807a6a757330523498148cc9
SHA1: bb8a7b616f22630407302655d4d4d491b16f55fb
I'm not responsible if you do some mistakes.
Please give me thanks that if it was helpful for you
Hallo. I've been looking for this instruction. Thank you. BTW your signature shows that you own Nexus S, not Nexus One. Are you sure the instruction you wrote is for Nexus One?
Yes i had also a nexus one this guide works perfectly for me...i took this from XDA wiki and i updated the latest build
Sent from my Nexus S using Tapatalk
Thank you man, but I wonder if Google would give 4.0 to us Nexus One users...
Thanks a lot, the most recent stock ROM in the FAQ was FRF91.
Edit: The file hosting you link to says it can't find the file (AFTER the stupid wait 60 seconds ) Would you mind re-uploading this to a more reputable file host?
Yes this afternoon i'll upload it on dropbox
Sent from my Nexus S using Tapatalk
ale.landra91 said:
Yes this afternoon i'll upload it on dropbox
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
I updated the link! Download it!
ale.landra91 said:
I updated the link! Download it!
Click to expand...
Click to collapse
Excellent, I got it! Thanks!
Dumb question, but there's no reason I can't just flash this in Amon-Ra or CW, is there? Your instructions are for stock recovery, but as far as I know it should work in any recovery, shouldn't it? (Obviously stock recovery will be flashed on reboot with a stock ROM, I know that.)
you can't flash it by stock recovery or custom recovery. This is not a custom or stock rom...it is a shipped image (in fact you have to name it not in "update" but in "passimg"). You don't have to enter in any recovery...while you boot in the bootloader all is automatic without using recovery! i don't know if im clear, i don't speak english very well
ale.landra91 said:
5)Hold down the Volume Down button as you power your phone back on.
6)A screen should appear showing your phone's system searching for various files. This will take up to 2 minutes.
7)The phone will ask you if you want to start the update. Press the Volume Up button to start the update.
Click to expand...
Click to collapse
No recovery request in the passage
Your English is fine I forgot that the bootloader handles the updates, not the recovery (which is why the name has to be specific, it looks for that file in the boot sequence). Answers my real question, anyway, which was whether I'd need to revert to stock recovery to apply it (I don't).
Thank you for your help.
No you don't have to...this method works for every rom and recovery
Sent from my Nexus S using Tapatalk
Hi , could you put a mirror download link .thanks in advance
Nexus74 said:
Hi , could you put a mirror download link .thanks in advance
Click to expand...
Click to collapse
Sorry but if you click "here" the download starts automatically...i can't upload it to another host site...if you upload it to another site after downlading please give me the link and i'll add it
thank you
I think ur ROM have some problem while u had uploaded
would u please check one again!
many thank
Didn't work
I followed thee steps you suggested. But after it scanned the SD card it didn't ask for anything.It just sat there at the bootloader screen. I'm using CM7.1 right, don't know if that affects anything.
No it is not a problem cm7 ...i Think that you should do this passage if you are using windows:
1) rename in PASSIMG (without .zip)
2) copy it in the root of SD card (not in a folder)
this should be the solution
Sent from my Nexus S using Tapatalk
ale.landra91 said:
No it is not a problem cm7 ...i Think that you should do this passage if you are using windows:
1) rename in PASSIMG (without .zip)
2) copy it in the root of SD card (not in a folder)
this should be the solution
Sent from my Nexus S using Tapatalk
Click to expand...
Click to collapse
Hey
yea that's what I did. But I didn't clear cache and data via recovery beforehand. Could that be the reason?
I think not....but for a good use of stock ROM you have to clear everything. If the file is complete downloaded and named correctly the bootloader has to recognize it. Sorry
Sent from my Nexus S using Tapatalk
Hey
I think the zip file has an issue. It said something while searching for files in the bootloader. Can you reupload maybe?
Sent from my Nexus One using XDA App
Earlier this week I bought a Samsung Galaxy S III for ATT. It already had Ice Cream Sandwich 4.0.4 on it and so I rooted it. Well the day after rooting it I get a message in my notification bar that there's a new software update available from ATT. Am I safe to do this update since my phone is rooted? I doubt the update is anything major, but does that make a difference?
fa7592 said:
Earlier this week I bought a Samsung Galaxy S III for ATT. It already had Ice Cream Sandwich 4.0.4 on it and so I rooted it. Well the day after rooting it I get a message in my notification bar that there's a new software update available from ATT. Am I safe to do this update since my phone is rooted? I doubt the update is anything major, but does that make a difference?
Click to expand...
Click to collapse
Check out this thread: http://forum.xda-developers.com/showthread.php?t=1768826
You can apply the update if you're rooted using the method in that thread or by installing OTA Rootkeeper before you apply the OTA. If you apply the OTA directly, you'll need to go back to stock recovery, then install CWM again when it's done. You'll also probably want to backup the Google Search widget (I forget the exact .apk -- search the forums) and restore it after to avoid losing Universal Search.
But the easiest way is to just flash the zip in the thread above through your CWM recovery.
As for the contents of the OTA: It updates the kernel, bootloader, lots of applications, some system libraries, wpa_supplicant and it's firmware (I think that's for wifi), and the modem. I've got it installed and didn't notice a huge difference, but you might. The thread above also includes separate flash files for the kernel and modem in case you want to try just those.
Good luck!
drothenberger said:
Check out this thread: http://forum.xda-developers.com/showthread.php?t=1768826
You can apply the update if you're rooted using the method in that thread or by installing OTA Rootkeeper before you apply the OTA. If you apply the OTA directly, you'll need to go back to stock recovery, then install CWM again when it's done. You'll also probably want to backup the Google Search widget (I forget the exact .apk -- search the forums) and restore it after to avoid losing Universal Search.
But the easiest way is to just flash the zip in the thread above through your CWM recovery.
As for the contents of the OTA: It updates the kernel, bootloader, lots of applications, some system libraries, wpa_supplicant and it's firmware (I think that's for wifi), and the modem. I've got it installed and didn't notice a huge difference, but you might. The thread above also includes separate flash files for the kernel and modem in case you want to try just those.
Good luck!
Click to expand...
Click to collapse
Thank you very much. I appreciate the quick response and the help.
drothenberger said:
Check out this thread: http://forum.xda-developers.com/showthread.php?t=1768826
You can apply the update if you're rooted using the method in that thread or by installing OTA Rootkeeper before you apply the OTA. If you apply the OTA directly, you'll need to go back to stock recovery, then install CWM again when it's done. You'll also probably want to backup the Google Search widget (I forget the exact .apk -- search the forums) and restore it after to avoid losing Universal Search.
But the easiest way is to just flash the zip in the thread above through your CWM recovery.
As for the contents of the OTA: It updates the kernel, bootloader, lots of applications, some system libraries, wpa_supplicant and it's firmware (I think that's for wifi), and the modem. I've got it installed and didn't notice a huge difference, but you might. The thread above also includes separate flash files for the kernel and modem in case you want to try just those.
Good luck!
Click to expand...
Click to collapse
would I just have to reflash the kernel I'm on now if I were to update that way?
Sent from my SAMSUNG-SGH-I747 using xda premium
jrbaker624 said:
would I just have to reflash the kernel I'm on now if I were to update that way?
Click to expand...
Click to collapse
No. There's a zip file there with the OTA but with the bootloader and kernel updates removed. You can flash that to keep your kernel. There's another zip file there with just the bootloader if you want to update that, too. Just flash both (No Bootloader No Kernel, the Bootloader).
drothenberger said:
Check out this thread: http://forum.xda-developers.com/showthread.php?t=1768826
You can apply the update if you're rooted using the method in that thread or by installing OTA Rootkeeper before you apply the OTA. If you apply the OTA directly, you'll need to go back to stock recovery, then install CWM again when it's done. You'll also probably want to backup the Google Search widget (I forget the exact .apk -- search the forums) and restore it after to avoid losing Universal Search.
But the easiest way is to just flash the zip in the thread above through your CWM recovery.
As for the contents of the OTA: It updates the kernel, bootloader, lots of applications, some system libraries, wpa_supplicant and it's firmware (I think that's for wifi), and the modem. I've got it installed and didn't notice a huge difference, but you might. The thread above also includes separate flash files for the kernel and modem in case you want to try just those.
Good luck!
Click to expand...
Click to collapse
UPDATE:
okay so I followed the steps in the thread you provided, and when I go to flash the update zip in recovery mode, i get an error and it aborts the installation. Heres the error:
assert failed: getprop("ro.product.device") =="
d2att" | | getprop("ro.build.product") =="
d2att"
E:Error in /emmc/I747UCALG1_OTA.zip
(status 0)
Installation aborted.
Any idea as to what this may mean?
I am also getting same error I was on team epics recovery then saw it wouldn't work for that recovery so I flashed a new recovery and still get the same error.
Tried flashing the no boot loader zip. And the no boot loader and no kernel zip
Sent from my SAMSUNG-SGH-I747 using xda premium
fa7592 said:
assert failed: getprop("ro.product.device") =="
d2att" | | getprop("ro.build.product") =="
d2att"
E:Error in /emmc/I747UCALG1_OTA.zip
(status 0)
Installation aborted.
Any idea as to what this may mean?
Click to expand...
Click to collapse
It means you're using the Team Epic recovery and not the one from clockworkmod.com. Try installing the 5.8.4.5 version of clockworkmod.com recovery from here: http://forum.xda-developers.com/showthread.php?p=28612095. That link has zip files you can flash from your current CWM recovery.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
drothenberger said:
It means you're using the Team Epic recovery and not the one from clockworkmod.com. Try installing the 5.8.4.5 version of clockworkmod.com recovery from here: http://forum.xda-developers.com/showthread.php?p=28612095. That link has zip files you can flash from your current CWM recovery.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Oh I see. So should I just download that file and replace the CWM zip file thats already on my phone. Or do I have to do something in Odin again?
fa7592 said:
Oh I see. So should I just download that file and replace the CWM zip file thats already on my phone. Or do I have to do something in Odin again?
Click to expand...
Click to collapse
Download OTA Rootkeeper from the play store, save root, then install the OTA. Reboot and OTA rootkeeper restore root.
drothenberger said:
It means you're using the Team Epic recovery and not the one from clockworkmod.com. Try installing the 5.8.4.5 version of clockworkmod.com recovery from here: http://forum.xda-developers.com/showthread.php?p=28612095. That link has zip files you can flash from your current CWM recovery.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Downloaded that one instead of the third one you had linked all together and it worked. Thank you
Sent from my SAMSUNG-SGH-I747 using xda premium
Download the zip file for recovery, apply it using your current recovery, reboot recovery from the advanced menu, then apply the OTA zip.
Or use OTA Rootkeeper as also suggested. I prefer my OTA zip personally, but either way will work.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
drothenberger said:
Download the zip file for recovery, apply it using your current recovery, reboot recovery from the advanced menu, then apply the OTA zip.
Or use OTA Rootkeeper as also suggested. I prefer my OTA zip personally, but either way will work.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Click to expand...
Click to collapse
Okay. Wow. So after a lot of trial and error (i think i bricked my phone somehow in the middle of everything, but its okay I found out how to fix it) I have managed to get that update applied. Theres one last problem though. I applied the update by flashing it in CWM recovery. I know I have the update installed because now under baseband version instead of saying I747UCLEM it says I747UCLG1. And Ive tested the google search widget and it's still giving me local search results so that's all good. The problem is that in my notification bar the ATT software update notification is still there. I have currently postponed it for 8 hours, but its still there and the only button I'm able to press is the continue button. I dont want to press this because im afraid the normal ATT update will install over the modded one and the google search widget will mess up and stop displaying the local search results. Also under about device, when I click software update the option for "check for update" is grayed out. Any thoughts on this?
fa7592 said:
Okay. Wow. So after a lot of trial and error (i think i bricked my phone somehow in the middle of everything, but its okay I found out how to fix it) I have managed to get that update applied. Theres one last problem though. I applied the update by flashing it in CWM recovery. I know I have the update installed because now under baseband version instead of saying I747UCLEM it says I747UCLG1. And Ive tested the google search widget and it's still giving me local search results so that's all good. The problem is that in my notification bar the ATT software update notification is still there. I have currently postponed it for 8 hours, but its still there and the only button I'm able to press is the continue button. I dont want to press this because im afraid the normal ATT update will install over the modded one and the google search widget will mess up and stop displaying the local search results. Also under about device, when I click software update the option for "check for update" is grayed out. Any thoughts on this?
Click to expand...
Click to collapse
What does it say under build number? IMM76D.I747UCALG1? If not, then somehow you only got the modem installed.
I have the update applied, but I had frozen AT&T Software Update in Titanium Backup, so I wasn't getting the notification. I just tried unfreezing it and checking for an update and was surprised when it said there was one! I postponed it, did a Wipe Data for AT&T Software Update in TiBu, then rebooted and now all is well. When I check for an update now it says I'm up-to-date. So try that.
drothenberger said:
What does it say under build number? IMM76D.I747UCALG1? If not, then somehow you only got the modem installed.
I have the update applied, but I had frozen AT&T Software Update in Titanium Backup, so I wasn't getting the notification. I just tried unfreezing it and checking for an update and was surprised when it said there was one! I postponed it, did a Wipe Data for AT&T Software Update in TiBu, then rebooted and now all is well. When I check for an update now it says I'm up-to-date. So try that.
Click to expand...
Click to collapse
Yeah, under build number it says IMM76D.I747UCALG1.
I'll give what you said a shot and see what happens. But one thing first, what's TiBu? And also, I'm about to flash a custom ROM on my phone, so is the update issue something that can wait, or should I take care of that before I put on a custom ROM?
fa7592 said:
Yeah, under build number it says IMM76D.I747UCALG1.
I'll give what you said a shot and see what happens. But one thing first, what's TiBu? And also, I'm about to flash a custom ROM on my phone, so is the update issue something that can wait, or should I take care of that before I put on a custom ROM?
Click to expand...
Click to collapse
Sorry, "TiBu" is my shorthand for Titanium Backup. Chances are any custom ROM you install will remove the AT&T Software Update application, so you won't need to worry about this anymore.
drothenberger said:
Sorry, "TiBu" is my shorthand for Titanium Backup. Chances are any custom ROM you install will remove the AT&T Software Update application, so you won't need to worry about this anymore.
Click to expand...
Click to collapse
Oh okay. In that case I'll go ahead and put in that custom ROM and report back when everything is done. Again, thanks for the help and patience.
Okay, so I have applied the ROM and everything is good! Well for the most part. At times when there isn't a WiFi signal available and it has to use mobile data, the 4G LTE doesn't work. It will connect to HSPA or 3G. And it happens in areas I know has 4G LTE available. But other than that everything seems to be working good. Just thought I'd share in case anyone was thinking of using the AOKP ROM.
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
Hey! I am having problem flashing the OTA zip (LRX21L-->LRX21R). It simply wont let me sideload the .zip file because my device can't be found after i reboot to the bootloader. Can anyone please help me with this?
My device has an unlocked bootloader and is rooted using Chainfires first root for the nexus 9. Thanks in advance!
acceh said:
Hey! I am having problem flashing the OTA zip (LRX21L-->LRX21R). It simply wont let me sideload the .zip file because my device can't be found after i reboot to the bootloader. Can anyone please help me with this?
My device has an unlocked bootloader and is rooted using Chainfires first root for the nexus 9. Thanks in advance!
Click to expand...
Click to collapse
Flash the 21l boot.img in fastboot. Then try the ota. Chain fire modified the boot image and that's why it isn't working
Sent from my Nexus 9 using XDA Free mobile app
Where do i get that 21l img file? And how to flash if fastboot is not recognized? I have twrp installed, could someone provide a flashable zip? Thanks
GeneralSmart said:
Where do i get that 21l img file? And how to flash if fastboot is not recognized? I have twrp installed, could someone provide a flashable zip? Thanks
Click to expand...
Click to collapse
Yeah...., I could go with this too, actually. I had pretty much everything from the board loaded. Including @Chainfire 's recov. I then later attempted to update the *poluza rom parts. It was failing any which way I tried in or out of twrp. Unfortunately, I am not much of a fastboot user, nor twrp.
I thought that maybe it had something to do with this updated vendor img. By the time I was done I had reformatted several times and started from scratch not leaving out steps. As far as I know. With just these images and no device trees nor a proper updater script, there is no way to tell really.
Currently and for a few days, it's been down to bare metal, and only a fastboot to look at. lol
I can't even seem to make a new factory image flash.
Never since my first android have I been this lost frankly.....
Maybe they have them now, I will look but it would also be helpful if the guys used a bit of ......'if.....then......' in their 'OP's'
"If you are using the included recovery, then......"
"If you are using this recovery then do......."
"If you wanted to use @Chainfire s recovery, then simply paste it......."
etc.
Could anyone possibly help and provide a way to update??? I unlocked bootloader and I am rooted, but now I want to have a working way to update....ANY HELP??
I found a solution: check out the video and download his tool...he did a great job there and it worked like a charm for me!!!!!!!!!!!!!!!!!!!!!!!!!!
https://www.youtube.com/watch?v=bsU1r6wKMiA
its the tool on the second link under the video...around 750 MB sized
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.