Related
Good evening/morning all
Just grabbed this new OTA from my One S so i thought i would make an appearance... And before anyone asks, yes - I am working on a ROM
OTA_Ville_U_HTC_Europe_1.78.401.2-1.53.401.2
Please note: This OTA takes you from 1.53.401.2 to 1.78.401.2
Change log from the updater service (rather vague):
System enhancment
Enjoy
P.S > Had no time to analyse the actual content but the OTA contains full firmware updates including HBoot & Radio.
Edit: Just noticed paul has done a repack of the base already.. may still come in handy for you devs out there
I knew you would come just like I asked for and others.
Thanks Lee.
If you can work on a T-Mobile ROM/EU ROM.
Very excited about the LeeDroid
Excellent rum were at Desire
On the one s worth the wait?
Can't wait for some goodness from you!
Sent from my US HTC One S using Tapatalk 2
Dimson75 said:
Very excited about the LeeDroid
Excellent rum were at Desire
On the one s worth the wait?
Click to expand...
Click to collapse
Certainly will be
Sent from my LeeDrOiD One Xtreme loaded HTC One X
woohoo !! about time you made an appearance !! I knew you was hanging around here somewhere
missed you since i left the sensation forums
I know this is probably a really stupid question but I'm going to ask anyway...
Can you actually install an OTA package on the phone somehow or is it just useful to take files out of it?
And the other question, my phone doesn't find any OTA updates anymore since I've 'tampered' with it so is there a way to make it find and install the OTA updates again?
Thanks
As long as you are using the correct stock ruu you can apply it via cwm recovery(unlock needed )... to restore full functionality its best to flash the stock RUU
Sent from my LeeDrOiD One Xtreme loaded HTC One X
LeeDroid said:
As long as you are using the correct stock ruu you can apply it via cwm recovery(unlock needed )... to restore full functionality its best to flash the stock RUU
Sent from my LeeDrOiD One Xtreme loaded HTC One X
Click to expand...
Click to collapse
The other thing is that when I try installing the stock RUU it's telling me it's for the wrong device or something like that, although it's definitelly the correct RUU.
Also, my phone is HTCDev unlocked but is still S-ON so if I install the OTA package usign CWM is it going to update the radio and the hboot (I thought it can't do that if you're S-ON)?
Thanks
you dont install it via CWM, you install it via the stock recovery.. of which you will first need to flash..
Did'nt work for me, wrong CID...
edit the info.txt to match your CID
azzledazzle said:
you dont install it via CWM, you install it via the stock recovery.. of which you will first need to flash..
Click to expand...
Click to collapse
Ok, maybe I'm not getting this right but I'm talking about two separate things:
Issue 1. My understanding is that I can install the OTA zip package using ClockworkMod, is that correct?
Issue 2. The RUU package won't install on my phone:
i) I have restored via ClockworkMod the nandroid image of the stock ROM (image that I've taken straight after I unlocked the boot loader and flashed a custom recovery, but before I rooted the phone). Then, I flashed the stock recovery image using fastboot. So now my phone should be back to stock.
ii) I then tried to install RUU_Ville_U_HTC_Europe_1.53.401.2_Radio_0.15.31501S.19_10.12.31501S.06L_release_251412_signed.exe
When I do this, the RUU goes through right up to the step where it says 'Updating signatures' and then it stops saying 'unknown error' and it leaves my phone on that screen with black background and white HTC logo. Then, I have to hard boot and the phone starts up fine but in the state it was before the RUU - not even the user data is missing. To me this means that for some reason it doesn't even try to flash the RUU onto the phone but it stops when checking the signatures - I just can't understand why this is happening...
Can you help?
Thanks
1. No you cannot flash anything official from HTC using CWM, you MUST use stock recovery. You can find stock recovery in the OTA zip file, It will be named recovery.img OR recovery_signed.img
2. Unknown error is hard to diagnose, Normally we get error codes which we can identify as to what the problem is.. Are you running the RUU in fastboot ?
azzledazzle said:
1. No you cannot flash anything official from HTC using CWM, you MUST use stock recovery. You can find stock recovery in the OTA zip file, It will be named recovery.img OR recovery_signed.img
Click to expand...
Click to collapse
Sorry for my ignorance, but how do I initiate the installation of the OTA zip package using the stock recovery? As I said, I can't actually get it 'over the air' but I've just downloaded the zip package from this thread...
ok put the package on your sd card.
boot into fastboot, flash the stock recovery using the command ''fastboot flash recovery recovery.img'' (or recovery_signed.img) (also no quotes)
when thats done, select recovery from fastboot using volume button..
When you get a red ! press volume UP and power button, That will take you into stock recovery
Then look for the option, install from sd card or something like that
select your OTA package and BOOM !!! job done
Reflash CWM and away you go
Damn... I had no idea that you can actually get into the menu of the stock recovery... It all makes sense now...
me neither till about 3 days ago
I might not seem like a noob,,,,,but deep down i am
azzledazzle said:
2. Unknown error is hard to diagnose, Normally we get error codes which we can identify as to what the problem is.. Are you running the RUU in fastboot ?
Click to expand...
Click to collapse
I've tried that again and it actually breaks down when it gets to 'Checking Header...' and it exits with 'ERROR [155]: UNKNOWN ERROR". Maybe this is a bit more specific...
this is what i found for error 155
ERROR [155~159]: IMAGE ERROR
One of these error messages will appear when you use the incorrect RUU to update and the image file size is larger than the Flash ROM size. In this case, download the correct RUU version and try again.
Alternatively (in some cases) right click on the file and choose "Run as Administrator".
Or use the rom.zip -> PGXXIMG.zip flashing method.
Click to expand...
Click to collapse
I dont know if it will fail when flashing the rom.zip in CWM - usually you have to rename it to the model number and flash in fastboot, however you cant do this with S-ON
Hey All,
Long time reader, first time Soft Bricker. I was flashing the Z Kernel 2.0 over Viper, and am now in a bootloop that doesn't let me get into my Recovery (TWRP). I can get into bootloader, though, and run fastboot. I've read the instructions on how to fix this error by flashing the RUU, but I can't find a link to an RUU where there isn't a $12 fee.
Is there another way to do it? I backed up my stock One S from after I rooted.
Help?
Thanks!
MrPickleFicker said:
Hey All,
Long time reader, first time Soft Bricker. I was flashing the Z Kernel 2.0 over Viper, and am now in a bootloop that doesn't let me get into my Recovery (TWRP). I can get into bootloader, though, and run fastboot. I've read the instructions on how to fix this error by flashing the RUU, but I can't find a link to an RUU where there isn't a $12 fee.
Is there another way to do it? I backed up my stock One S from after I rooted.
Help?
Thanks!
Click to expand...
Click to collapse
Open the zip file for viper rom and extract the boot.img file and move it to the folder on your computer where adb.exe is. Then get into the phone into fastboot connect it to your computer and run this command. "fastboot flash boot boot.img"
That should get you back into viper.
dc211 said:
Open the zip file for viper rom and extract the boot.img file and move it to the folder on your computer where adb.exe is. Then get into the phone into fastboot connect it to your computer and run this command. "fastboot flash boot boot.img"
That should get you back into viper.
Click to expand...
Click to collapse
Thanks, going to take approximately 24 minutes while I wait for the Zip to download then I'll post results. Is Viper different in some way? I've flashed probably 50 roms (including an earlier version of Viper) and haven't run into boot.img issues as long as I've flashed a kernel with it. On H-Boot 1.08.
MrPickleFicker said:
Thanks, going to take approximately 24 minutes while I wait for the Zip to download then I'll post results. Is Viper different in some way? I've flashed probably 50 roms (including an earlier version of Viper) and haven't run into boot.img issues as long as I've flashed a kernel with it. On H-Boot 1.08.
Click to expand...
Click to collapse
You can just pull boot.img from your original download of Viper Rom if it's still on your computer. The reason i suggested that you flash the boot.img is because you said you only have access to fastboot and your problems started with you flashed a new kernel. Since the boot.img from the rom will contain the original viper kernel it should reverse your problem.
dc211 said:
You can just pull boot.img from your original download of Viper Rom if it's still on your computer. The reason i suggested that you flash the boot.img is because you said you only have access to fastboot and your problems started with you flashed a new kernel. Since the boot.img from the rom will contain the original viper kernel it should reverse your problem.
Click to expand...
Click to collapse
I didn't download the rom on my computer the first time around, just had it on my phone's "SD Card". So with our snail mail up here have about 10 minutes left on my computer download. Hoping this works!
You da man! Thanks a ton! Hopefully I'll be able to return this favor to someone else in the future.
MrPickleFicker said:
You da man! Thanks a ton! Hopefully I'll be able to return this favor to someone else in the future.
Click to expand...
Click to collapse
Glad it worked out for you. :good:
Can anyone point me to the thread that tells me how to update to latest 4.2 firmware from older 4.2 firmware using fastboot? I installed TWRP 2.5 on older 4.2 so I do not have TWRP option. I D/L 10.6.1.15.3, there are two files in the zip. Do I rename the .blob? and what do I do with the other one?
TigerDNA said:
Can anyone point me to the thread that tells me how to update to latest 4.2 firmware from older 4.2 firmware using fastboot? I installed TWRP 2.5 on older 4.2 so I do not have TWRP option. I D/L 10.6.1.15.3, there are two files in the zip. Do I rename the .blob? and what do I do with the other one?
Click to expand...
Click to collapse
Yeah have a look here or here
Let me know if you need more info
I feel like a retard i have been trying to get fastboot to read the tablet forever now. When i do volume down and power i have no option for usb and when i go through adb or fastboot and search for devices i get nothing that pops up.
IDK what to do:crying:
when you get the three icons mate fastboot is running then, they took away the the fastboot option and it just runs automatically when you can see the three icons
I finally got it !!!!!
I did the naked driver and then ran moto auto root
and bam i got recovery now time for a rom
Im so stupid i thought you get recovery first then root idk what i was thinking
Hey guys, I'm trying to downgrade to KitKat after all the issues Lollipop is giving me and the incompatible apps I'm trying to run.
I am following instructions here but I came across a problem when flashing the system.img file.
The error it gives me is:
FAILED (remote: Insufficient memory.)
I can't flash over system and can not boot.
What am I missing? I was rooted and my bootloader unlocked prior to starting and I tried with the factory recovery and the 1.2.1 recovery image.
Edit: My issue has been solved. Flashing the Full OTA.zip file will install KitKat over Lollipop. No need to manually flash each file through fastboot. I wish guides would tell you that instead.
BlackDave said:
Hey guys, I'm trying to downgrade to KitKat after all the issues Lollipop is giving me and the incompatible apps I'm trying to run.
I am following instructions here but I came across a problem when flashing the system.img file.
The error it gives me is:
FAILED (remote: Insufficient memory.)
I can't flash over system and can not boot.
What am I missing? I was rooted and my bootloader unlocked prior to starting and I tried with the factory recovery and the 1.2.1 recovery image.
Click to expand...
Click to collapse
I don't know why that wouldn't work. Have you tried just downloading the image from nvidia HERE?
I'm assuming wifi since your sig says 16GB
Keithn said:
I don't know why that wouldn't work. Have you tried just downloading the image from nvidia HERE?
I'm assuming wifi since your sig says 16GB
Click to expand...
Click to collapse
Those are the same files as the ones I downloaded in the other thread.
I got my tablet working again on Lollipop 5.0.1 but that's not where I want to be. I've searched about my error message but most threads I found went unanswered.
Your best bet might just be to try getting a full OTA and flashing it through cwm or something. I'll try with mine when I have some time to backup and flash, probably later tomorrow. If I find anything out I'll post.
Sent from my SHIELD Tablet
BlackDave said:
I got my tablet working again on Lollipop 5.0.1 but that's not where I want to be. I've searched about my error message but most threads I found went unanswered.
Click to expand...
Click to collapse
I just flashed the images and booted.
Did you accidentally try flashing to the wrong place, such as flashing to boot( which would be too small) instead of system? Did you do all of the commands yourself or use the .bat? My shield disconnected after doing the boot.img and system.img for some reason, so I had to select fastboot protocol to reboot the bootloader and continue to flash the userdata.img, blob, and battery.dtb.
was your tablet internal memory full?, try wipping data and chace and you could use the script that the original Nvidia recovery image has zipped. I went up and down like 3 times, im in kitkat right now and not experiencing any problem.
Iams1002 said:
was your tablet internal memory full?, try wipping data and chace and you could use the script that the original Nvidia recovery image has zipped. I went up and down like 3 times, im in kitkat right now and not experiencing any problem.
Click to expand...
Click to collapse
No I wipped internal data since I keep everything on external and it still didn't work.
Keithn said:
I just flashed the images and booted.
Did you accidentally try flashing to the wrong place, such as flashing to boot( which would be too small) instead of system? Did you do all of the commands yourself or use the .bat? My shield disconnected after doing the boot.img and system.img for some reason, so I had to select fastboot protocol to reboot the bootloader and continue to flash the userdata.img, blob, and battery.dtb.
Click to expand...
Click to collapse
So I should just flash the ota.zip?
Also i did everything like the guide. I flashed boot to boot, recovery to recovery. The only thing that gave me an error was system. Userdata, blob, and battery also flashed successfully. After that didn't work, I also tried the .bat and that didn't work either. Flashing the 5.0.1 update got my tablet running again.
BlackDave said:
No I wipped internal data since I keep everything on external and it still didn't work.
So I should just flash the ota.zip?
Also i did everything like the guide. I flashed boot to boot, recovery to recovery. The only thing that gave me an error was system. Userdata, blob, and battery also flashed successfully. After that didn't work, I also tried the .bat and that didn't work either. Flashing the 5.0.1 update got my tablet running again.
Click to expand...
Click to collapse
If you can find a full ota.zip for update 1.2.1 I'd try that. I'm not sure why you would be having this issue. The only other things I can say to try is redownloading and rebooting the boot loader (select fastboot protocol) between images in case something funny is happening there. Let us know how you end up doing.
Sent from my HTC M8
Keithn said:
If you can find a full ota.zip for update 1.2.1 I'd try that. I'm not sure why you would be having this issue. The only other things I can say to try is redownloading and rebooting the boot loader (select fastboot protocol) between images in case something funny is happening there. Let us know how you end up doing.
Sent from my HTC M8
Click to expand...
Click to collapse
I flashed the 1.2.1 OTA update and it worked. The first time I tried, I did using the TWRP recovery but for some reason, that recovery fails to flash OTAs, so I went with CWM and flashed the 2.1 update and all worked again. After a while, I got tired of all the issues lollipop gave me so that's why I tried following that guide to downgrade.
In the end, using CWM and flashing the OTA is the best way to go. Thank you all for you help.
After Failing over and over, I finally was able to flash the latest NOUGAT Update provided in the other thread:
http://forum.xda-developers.com/moto-z/how-to/android-7-international-rollout-t3510790
Download the update.zip file "Blur_Version.24.21.46.griffin.retail.en.US.zip" from one of the posts
Main issue for me was i was on the wrong firmware, simple flash the "XT1650-03_GRIFFIN_ROGERS_MPL24.246-45_cid50_subsidy-RGRCA_regulatory-DEFAULT_CFC.xml" firmware by grabbing it from
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
Notice you need the MPL24.246-45 FIRMWARE , the number 45 plays a major role as it will be verified later. I was running the buildnumber MPL24.246-20 instead of 40
once you get that out of the way and are done flashing the MPL24.246-40 firmware, simply adb sideload the Blur_Version.24.21.46.griffin.retail.en.US.zip from your computer, reboot in stock recovery and then hold power and then press volume up and choose the option adb sideload
My sideload failed at 95%, however when i rebooted, it was running nougat
let me know how it goes for you guys
My bootloader is unlocked, and i did not relock it
This is really sad. They said it was going to be this week and a global roll out.
Nothing!
I can't wait until Samsung release the S8E.. Giving this phone to my 8 years old niece to have!
can u make some order here ?
what is your model ?
if u flashed 24.246-45 then u said it needs to be 40
then did u flash the 40 over 45 ?
thanks
hassanman1997 said:
Download the update.zip file "Blur_Version.24.21.46.griffin.retail.en.US.zip" from one of the posts
Main issue for me was i was on the wrong firmware, simple flash the "XT1650-03_GRIFFIN_ROGERS_MPL24.246-45_cid50_subsidy-RGRCA_regulatory-DEFAULT_CFC.xml" firmware by grabbing it from
Notice you need the MPL24.246-45 FIRMWARE , the number 45 plays a major role as it will be verified later. I was running the buildnumber MPL24.246-20 instead of 40
once you get that out of the way and are done flashing the MPL24.246-40 firmware,
Click to expand...
Click to collapse
This is really helpful. I hit the same snag when I tried to upgrade from -17 firmware.
Any chance you could upload the Canadian Rogers firmware (-45) to Mega? It's so painful waiting for 9 hours for it to fail a few minutes from the end.
Yeah I can try, but I won't be home until night, the only pain was waiting 9 hours, and the firmware is -45, I accidently wrote -40 , I don't think there is any firmware with-40
I tried all the above. Still fails for me.
---------- Post added at 05:14 PM ---------- Previous post was at 05:10 PM ----------
I think because the file has been replaced with a v2 so it's failing verification
I'm uploading the Rogers .45 firmware to mega right now. I'll update this post once its done uploading.
Link: https://mega.nz/#!nssGEDiT!hhLkcTM106hmqbH_fiWfAytEV-fgdlYOhUwpcd_sGJY
Downloaded straight from FileFactory and uploaded directly to Mega
Here is: XT1650-03_GRIFFIN_ROGERS_MPL24.246-45
https://drive.google.com/file/d/0Bw3YYHFxKQxVNTBLeWxadUFZOU0/view?usp=sharing
...Now, can someone help me figure out how to flash it? That would be awesome
svetius said:
Here is: XT1650-03_GRIFFIN_ROGERS_MPL24.246-45
https://drive.google.com/file/d/0Bw3YYHFxKQxVNTBLeWxadUFZOU0/view?usp=sharing
...Now, can someone help me figure out how to flash it? That would be awesome
Click to expand...
Click to collapse
Whats the status of your device right now? Are you purely stock? Rooted? Unlocked? TWRP or stock recovery?
Prfndhatrdofman said:
Whats the status of your device right now? Are you purely stock? Rooted? Unlocked? TWRP or stock recovery?
Click to expand...
Click to collapse
I flashed XT1650-03_GRIFFIN_ROGERS_MPL24.246-45 via this method:
http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
And while the flash was successful, strangely booting into the OS I'm still on -20.
So then I tried to sideload nougat, and it went up to 87% and failed, causing a bootloop. The bootloop can be fixed by manually flashing -45 again (which is so weird because it actually loads -20).
I am unrooted, bootloader locked.
svetius said:
I flashed XT1650-03_GRIFFIN_ROGERS_MPL24.246-45 via this method:
http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
And while the flash was successful, strangely booting into the OS I'm still on -20.
So then I tried to sideload nougat, and it went up to 87% and failed, causing a bootloop. The bootloop can be fixed by manually flashing -45 again (which is so weird because it actually loads -20).
I am unrooted, bootloader locked.
Click to expand...
Click to collapse
You got further than me. ADB Sideload wouldnt even look at the Nougat OTA zip. tried multiple ADB versions too
svetius said:
I flashed XT1650-03_GRIFFIN_ROGERS_MPL24.246-45 via this method:
http://forum.xda-developers.com/showpost.php?p=69065373&postcount=14
And while the flash was successful, strangely booting into the OS I'm still on -20.
So then I tried to sideload nougat, and it went up to 87% and failed, causing a bootloop. The bootloop can be fixed by manually flashing -45 again (which is so weird because it actually loads -20).
I am unrooted, bootloader locked.
Click to expand...
Click to collapse
Sideload was successful for me, but still completely in a bootloop as well..
for me it worked fine with ADB sideload.
my bootloader is unlocked, i tried locking it back to get official OTA but failed to lock it again.
I tried every method that was mentioned but failed over and over
so here is what I did:
1) removed all the personal files from phone (pictures, videos, texts etc) so i don't lose em
2) flashed the rogers [XT1650-03_GRIFFIN_ROGERS_MPL24.246-45_cid50_subsidy-RGRCA_regulatory-DEFAULT_CFC.xml] firmware by using mfastboot, make sure you grab the mfastbootv2, you can google and download it, use mfastboot and flash the firmware by command lines
3)after flashing, rebooted, set up the device and skipping a few steps to get into homescreen, and then powered off the phone.
4)downloaded Blur_Version.24.21.46.griffin.retail.en.US.zip and placed it in the adb folder, make sure you download the latest adb tools, you can google and find them easily too
5) extract the adb folder and place the Blur_Version.24.21.46.griffin.retail.en.US.zip in side that folder
6) reboot the phone and press volume to navigate to recovery, you should boot into stock recovery as you flashed stock firmware
7) hold power button and press volume up and youll see the menu, select update by ota and connect to the phone
8) open command line in the adb tools and use command to flash ota via adb
9) mine failed at 95% because of system image error, so instead of rebooting it, i used the command again and flashed the ota via adb, it failed again, however when i rebooted i was presented by the new red moto boot animation, there i knew it was updated to android N
*Delete*
hassanman1997 said:
After Failing over and over, I finally was able to flash the latest NOUGAT Update provided in the other thread:
http://forum.xda-developers.com/moto-z/how-to/android-7-international-rollout-t3510790
Download the update.zip file "Blur_Version.24.21.46.griffin.retail.en.US.zip" from one of the posts
Main issue for me was i was on the wrong firmware, simple flash the "XT1650-03_GRIFFIN_ROGERS_MPL24.246-45_cid50_subsidy-RGRCA_regulatory-DEFAULT_CFC.xml" firmware by grabbing it from
http://www.filefactory.com/folder/c6cdedc45a775d27/?sort=created&order=DESC&show=25
Notice you need the MPL24.246-45 FIRMWARE , the number 45 plays a major role as it will be verified later. I was running the buildnumber MPL24.246-20 instead of 40
once you get that out of the way and are done flashing the MPL24.246-40 firmware, simply adb sideload the Blur_Version.24.21.46.griffin.retail.en.US.zip from your computer, reboot in stock recovery and then hold power and then press volume up and choose the option adb sideload
My sideload failed at 95%, however when i rebooted, it was running nougat
let me know how it goes for you guys
My bootloader is unlocked, and i did not relock it
Click to expand...
Click to collapse
OK, so i got it working. But there were some difficulties.
I was on 24.246-45 already, but i installed TWRP and a custom kernel. I reflashed the recovery and boot from the BELL 24.246.45 firmware, and proceeded sideloading the update. It errored out, saying system was mounted r/w once (after I installed TWRP, but I never altered it beyond that).
So i flashed the system chunks from the firmware ( "mfastboot flash system system.img_sparsechunk.0" , "mfastboot flash system system.img_sparsechunk.1" etc.), then i retried the sideload, and it worked. The system information still says the build number is MPL24.246-45, but the android version is 7.0, everything seems to be working, including split screen, the new easter egg, quicklaunch ribbon, and new notifications.
gomisensei said:
... The system information still says the build number is MPL24.246-45, but the android version is 7.0, everything seems to be working, including split screen, the new easter egg, quicklaunch ribbon, and new notifications.
Click to expand...
Click to collapse
This should be only a "cosmetic" issue... probably you can fix it by editing build.prop...
enetec said:
This should be only a "cosmetic" issue... probably you can fix it by editing build.prop...
Click to expand...
Click to collapse
meh, i'm not really worried about it, at least not enough to guess what the version SHOULD be...
gomisensei said:
meh, i'm not really worried about it, at least not enough to guess what the version SHOULD be...
Click to expand...
Click to collapse
:laugh:
Does that actually work for other software channels as well?
I'm from india, my software chanel is retin (retail India) can I still flash the one that came for retus?
Sent from my Moto Z using XDA Labs