Disclaimer:
These images are mainly provided for Developers to experiment with, if you flash them you do his on your own accord and abide to the following rules:
!!!IF YOU DO FLASH THEM AGAINST MY ADVICE - DO NOT FLASH THEM WITH FASTBOOT!!!
Use the Nandroid.md5 from here, copy them and the md5 file to you sdcard and use Nandroid recovery to flash them.
- You have to wipe before using these images
- Make Backups before using this images. I am not responsible if they brick your device, kill your cat or start World War 3!
- AGAIN: You should not flash this images directly yet, as this is untested and you will loose root.
Update 4: If you have MD5 mismatches, follow the instructions here and download his MD5 file. After that you should not get any more MD5 mismatches. Also if you got a missing SD-Card after pushing the build.prop.frankenrom then change
Code:
ro.build.characteristics=tablet,nosdcard
to
Code:
ro.build.characteristics=tablet
That should fix it
Update 3: Seems like you do not need (some users even point out that you shouldn't as it caused them FCs) to copy the ressources as described in the last update, if you use the AU-Images. You can add you APN manually and it seems to work just fine. You should copy the build.prop, if you want to use regional features of your device, as I think that market and other apps pull information out of it.
Update 2: Thanks to Simba90 there is now a complete set of working instructions to get the AU images on your XOOM with Nandroid. Read here
Update: So I erased my XOOM again to bring you instructions
Make a new directory on your sdacrd for a new Recovery
Code:
/clockworkmod/backup/2011-07-09.22.22.22
Copy the images and the MD5 file into this directory.
Start into CWM go to Backup and Restore -> Advanced Restore and restore the partitions from the created directory. Then boot into fastboot and apply the rooted boot.img from here
Now you have a rooted AU XOOM. I have it working with O2 Germany here, but only after applying my instructions from here because the AU images are missing the right settings and telephony Databases as well as our beloved frankenrom build.prop. After doing that all I copied the Books app from the Tiamat 1.1 Rom to /system/app and it works out of the box, so there is no need for using the US 3.1 anymore. I will update my thread accordingly.
/Update
Hi,
I took the plunge and relocked my XOOM after applying the Australian System images from the Motorola Dev Site to it, then I updated to 3.1 with System Update, unlocked, applied the CWM Recovery and made a Nandroid Backup. So here go the pristine System images (boot.img system.img and data.img).
Download here
I would not recommend doing my procedure for anyone not keen on updating his/her Bootloader, because it is updated if you do an OTA Update. Instead try the provided images but remember to make a Nandroid Backup beforehand. I have tried the images on my Euro XOOM and they worked flawlessly. I hope they help further Development. I for my part will try to integrate them into my EU/US-Frankenrom.
So have fun now, let the hacking begin.
So does the Australian Xoom use the same GSM 3G that the euro versions do?
Thanks.
Seems it does, my 3G Connection was working with no Problems, but I can not say definitely that everything works, because I used it just for a few hours now, as I wanted to share it as soon as possible that users can start to hack around with it.
lowtraxx said:
I would not recommend doing my procedure for anyone not keen on updating his/her Bootloader, because it is updated if you do an OTA Update.
Click to expand...
Click to collapse
If it updates the bootloader, is it possible to go back to stock and re-root?
Yes it is possible to go back to stock and ReRoot, because you still can OEM Unlock and use Nandroid to recover and get your Root back. But I do not kow if the EURO and AU Bootloader differ.
lowtraxx said:
Yes it is possible to go back to stock and ReRoot, because you still can OEM Unlock and use Nandroid to recover and get your Root back. But I do not kow if the EURO and AU Bootloader differ.
Click to expand...
Click to collapse
Don't know if this relates but Telstra uses the 850mhz 3G frequency, same as the US whereas the other Aussie telcos use the same as Europe does (900mhz).
Lowtraxx
Been using your original post since day one for 3.1 on my euro xoom. Does this now mean you will be able to sort out the dropping 3g and incorrect signal bars now.
Cheers
Lowtraxx
Just thinking actually would you be able to modify this new aus 3.1 to be CWM flashable.
Thanks
Is this the official AU 3.1 Update? When did they get it?
Yes this is the actual Update, they started rolling it out yesterday.
It is already CWM flashable, you have to create a new nandroid-backup folder on your SdCard copy the images and the md5 into it, then you have to wipe and with advanced recovery you can flash every one of the partitions back.
Then i hope that it will come for the EU Retail Version soon!
Lowtraxx
When i try and restor Im getting an MD5 mismatch error
THIS THING WORKS!
thank you mr lowtraxx
backed up, flashed the stock, OTA update
Updated the thread with the latest findings
Hi there,
After i push the FrankenRom build.prop to my Xoom, i lose SD Card?
Is there a work around, or am i being numb?
Thanks
Marshall1975 said:
Lowtraxx
When i try and restor Im getting an MD5 mismatch error
Click to expand...
Click to collapse
same here...
davidebeatrice said:
same here...
Click to expand...
Click to collapse
Hi,
follow the instructions here or download the md5 file there. If you do that, you should not get any MD5 Mismatches.
dexta211 said:
After i push the FrankenRom build.prop to my Xoom, i lose SD Card
Click to expand...
Click to collapse
same here ...
malta72 said:
same here ...
Click to expand...
Click to collapse
in the build.prop change
Code:
ro.build.characteristics=tablet,nosdcard
to
Code:
ro.build.characteristics=tablet
That should fix it
lowtraxx said:
in the build.prop change
Code:
ro.build.characteristics=tablet,nosdcard
to
Code:
ro.build.characteristics=tablet
That should fix it
Click to expand...
Click to collapse
Thanks, but this change doesn't fix the access to the sdcard.
I can't see the sdcard in Settings|storage, and ES Datei Manager too.
Related
Light mod official firmware ICS for A101
Acer_AV041_A101_1.014.00_WW_GEN1-root.zip
It is flash through CWM or TWRP Recovery.
Changes:
Official bootloader removed
Updating to official recovery is disabled
Rooted - You must install Superuser. Do not renew busybox!
All the rest is left without changes.
thanks serves to A100?
Thank you for this. I am already rooted using your easy method, but I am sure this will be a lot of help to many others.
Большое спасибо.
peporras said:
thanks serves to A100?
Click to expand...
Click to collapse
Does it say A100? No, it doesn't.
ZeroNull said:
Light mod stock firmware ICS for A101
Acer_AV041_A101_0.004.00_WW_GEN1-root.zip
It is flash through CWM or TWRP Recovery.
Changes:
Official bootloader removed
Updating to official recovery is disabled
Rooted
Added app: ES Explorer and Superuser
All the rest is left without changes.
Click to expand...
Click to collapse
Thanks a lot for this, however, I'd rather try the actual leak file for now (not really bothered about my bootloader etc, which I unlocked but never got around to flashing a custom recovery).
I've found the original Russian forum, and the original leak file, but the instructions really aren't being translated very well by Google... There seem to be 4 update files in the archive, should they all be flashed, one after the other?
Path for the official A101 updating to ICS
Thanks to djinox of 4pda.ru. Original article is published on this site (russian).
Flashing through official recovery:
1. Download this archive. Unpack it. The archive contains 4 files numbered in the order of updating.
2. Rename update1.zip in update.zip and place it on the SD card. Flashing through official recovery.
3. To execute the 2nd point for update2.zip, update3.zip and update4.zip.
The firmware of ICS for A101 is received.
Thanks very much! And also thanks to djinox for the leak.
Wrong thread , sorry.
Can we please get something like this for the A100?
Hi I tried using the steps below to flash, no luck going to ICS.
Anything i might be doing wrong, i change each of the 4 files to update.zip and flashed it one by one, rebooting after each flash.
Flashing through official recovery:
1. Download this archive. Unpack it. The archive contains 4 files numbered in the order of updating.
2. Rename update1.zip in update.zip and place it on the SD card. Flashing through official recovery.
3. To execute the 2nd point for update2.zip, update3.zip and update4.zip.
leomatt said:
Hi I tried using the steps below to flash, no luck going to ICS.
Anything i might be doing wrong, i change each of the 4 files to update.zip and flashed it one by one, rebooting after each flash.
Flashing through official recovery:
1. Download this archive. Unpack it. The archive contains 4 files numbered in the order of updating.
2. Rename update1.zip in update.zip and place it on the SD card. Flashing through official recovery.
3. To execute the 2nd point for update2.zip, update3.zip and update4.zip.
Click to expand...
Click to collapse
What version of an firmware the system shows now?
It still shows up as HC 3.2.1 with wallpaper and desktop settings still intact
leomatt said:
It still shows up as HC 3.2.1 with wallpaper and desktop settings still intact
Click to expand...
Click to collapse
You can look here:
Applications -> Setting -> About tablet -> Build number - firmware version?
leomatt said:
It still shows up as HC 3.2.1 with wallpaper and desktop settings still intact
Click to expand...
Click to collapse
I had that initially. The actual ICS ROM is in update4.zip. You MUST do each one in turn. If you don't get the update, you did it wrong.
Thanks for the replies, I manage to get the update to ICS using CWM method, and almost bricking it, because I was on HC.
But all is good now. Thanks again
Any new ICS leaks
Hi, I am just curious if there will be any custom ICS roms for the A101 in the near future, or more leaks
Thank you
ZeroNull said:
1. Download this archive.
Click to expand...
Click to collapse
Does anyone have a mirror of this file, as the given link is broken?
smokku said:
Does anyone have a mirror of this file, as the given link is broken?
Click to expand...
Click to collapse
Temporary problem. Try once again.
ZeroNull said:
Acer_AV041_A101_0.004.00_WW_GEN1
Click to expand...
Click to collapse
This build does not recognize headphones plugged in and still plays sound via speakers.
So, if you like using headphones with your A101, stay on HC.
Asking for ROM Bugs
Hi all,
Anyone can tell if there are any other bugs in this ROM beside earphone problem please? thx
UPDATED 2013/11/21: Added more warnings.
This is for US SGH-T999 devices ONLY. If there is ANY letter after your model such as 'L' or 'V' DO NOT FLASH THIS OR YOU WILL DEFINITELY BRICK YOUR PHONE! For SGH-T999V VLDLD1 firmware, please see this thread: http://forum.xda-developers.com/showthread.php?p=41701398
DO NOT flash this if you are running latest 4.3 (*MJC) firmware. It WILL brick your device. Currently there is NO way to downgrade from MJC firmware without a brick due to the Knox security stuff added to that firmware release.
Currently I don't have a SGH-T999L firmware update script, sorry. If someone would like to work with me on guinea pigging it and has heimdall installed, PM me and we'll get it done in no time.
This is the latest firmware update for US T-Mobile (SGH-T999) that flashes the UVDMD5 radio and bootloader with a convenient update.zip. Flashing it on anything other than the US SGH-T999 is strongly not advisable. It will likely brick your phone. It CANNOT be used on the Canadian T999V variant.
This script flashes all of the firmware that comes with the UVDMD5 OTA -- this upgrades the firmware as if you had just flashed the whole package through Odin, but without actually touching system, recovery, kernel, etc. There are two versions of the script -- one just does the bootloader+firmware, the other does bootloader+firmware+modem.
What are these firmware files?
rpm.mbn - Resources and Power Manager
sbl2.mbn - Part of Secondary Bootloader
sbl3.mbn - Part of Secondary Bootloader
aboot.mbn - AP Bootloader
tz.mbn - Trust Zone
NON-HLOS.bin - Modem / Radio
Why do I want this?
If your phone has old enough firmware, newer CM10.1 builds will no longer install on it. It is unknown if updating to UVDMD5 from UVDLJC, for example, has any noticeable positive effects. No known negative effects have been reported and the Odin method ends up upgrading all this stuff anyway.
Note that you can flash the above files via heimdall but this updater below is handy as you don't need heimdall, download mode, etc. All you really have to do is flash it in recovery.
Flashable UVDMD5 Bootloader / Firmware / Modem update.zip: https://dl.dropboxusercontent.com/u/173554095/T999 Devel/T999_UVDMD5_firmware_v4.zip (md5: d040ea4193234cbe9a36f95ffa780086)
Above flashable update without modem: https://dl.dropboxusercontent.com/u/173554095/T999 Devel/T999_UVDMD5_noradio_v4.zip (md5: 4c4aa065ee7c86dccea92ec7856a7af4)
OLDER UVDLJC Firmware update.zip script (w/modem) -- only if you specifically need it for some reason.: https://dl.dropboxusercontent.com/u/173554095/T999 Devel/T999UVDLJC_firmware.zip (md5: 537b69ec54ce6a3580a9c56ca379e72c)
Instructions:
(1) Put this .zip file on the root of your sdcard.
(2) Reboot to recovery
(3) Choose .zip file from sdcard and select this file and flash it.
(4) Reboot and you're done. I didn't find any wiping of any kind necessary.
NOTE: If you plan to flash anything else, please at least reboot recovery or it won't pick up the bootloader change.
Changes:
v1: Initial release. Modified someone's UVDLJC firmware update.zip script to update to UVDMD5.
v2: Removed certs from a previous update.zip that could've been causing signature verification errors with some recoveries.
v3: Updated Edify script courtesy of @Aerowinder
v4: Corrected a derp in package_extract_dir() (my fault) that prevented v3 from working at all. I've since tested v4 personally and verified it.
Many thanks to whomever put together the original update.zip and to Khaytsus and invisiblek for pointing me in the right direction. Also many thanks to all who've tested it and provided feedback. There is no greater enjoyment than in helping people.
I've also hacked together a firmware backup script that works for both T999 and T999V: http://forum.xda-developers.com/showthread.php?p=41548550
DISCLAIMER: I do not take any credit for this stuff, I just put it together. I am not liable for your device if you break it, etc etc. READ THE WARNINGS BEFORE PROCEEDING.
Trying crazy stuff like this freaks me out.....but I wonder if anyone has tried it tho!
Sent from my SGH-T999 using Tapatalk 2
I tried the new .zip you made and it worked. Flashed and now have newest bootloader.
Sent from my SGH-T999 using Tapatalk 2
re: bootloader
OhhCoreey said:
I tried the new .zip you made and it worked. Flashed and now have newest bootloader.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
What's the point of having the NEWEST bootloader, how is it any better than a 1 year old bootloader?
Misterjunky said:
What's the point of having the NEWEST bootloader, how is it any better than a 1 year old bootloader?
Click to expand...
Click to collapse
You need the new bootloader to flash new CM10.1 nightlies. Cyanogen posted it.
Sent from my SGH-T999 using Tapatalk 2
itzsmokey said:
Trying crazy stuff like this freaks me out.....but I wonder if anyone has tried it tho!
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
You can always try the original UVDLJC I linked that will work with latest nightlies. I used my own update.zip file that I posted here and my phone works fine now using the latest UVDMD5 full firmware (incl. radio).
Oh yeah -- both these update.zips contain the radio so if you don't want the MD5 or LJC radio, better update it to something else afterward.
You can check my work, read the META-INF/com/google/android/updater-script file. You can dd all those mmcblk0pX partitions to backup files, too. Maybe I'll make a firmware back up script while I'm at it.
There's nothing really scary about this -- you get these exact same files flashed to your phone in the same place if you use the UVDMD5 stuff in Odin, except you'll probably overwrite your recovery and system as well and spend extra time restoring it.
Steps for using it, in case this is unclear:
(1) Put this .zip file on the root of your sdcard.
(2) Reboot to recovery
(3) Choose .zip file from sdcard and select this file and flash it.
(4) Reboot and you're done. I didn't find any wiping of any kind necessary.
I'm running cm10.1-20130513-d2tmo with imoseyeon's leankernel 5.9 on my SGH-T999. Haven't upgraded to the newer nightly yet as nothing looked interesting enough in the changelog.
Oh and:
Code:
[email protected]:/ # getprop ro.bootloader
T999UVDMD5
OhhCoreey said:
You need the new bootloader to flash new CM10.1 nightlies. Cyanogen posted it.
Sent from my SGH-T999 using Tapatalk 2
Click to expand...
Click to collapse
ok, thanks now I know I don't need it because I just am not a fan of the CM10/AOKP/AOSP roms.
Good luck with it.
Misterjunky said:
ok, thanks now I know I don't need it because I just am not a fan of the CM10/AOKP/AOSP roms.
Good luck with it.
Click to expand...
Click to collapse
FWIW, I'm getting much better radio performance after switching to UVDMD5 modem. YMMV but I'm definitely getting better up/down and stronger signal indoor where I had terrible signal. But you you can just flash the modem separately from this .zip -- there's a thread in the d2tmo dev forum with the modems and their recovery flashable update.zip files.
The OP of said thread also undertook a project to allow people to post on some shared Google Map what modem they're using and their results, so you might want to look into what works best for your area too if you care about getting better signal or speed.
Cyanogen pushed the assert for newer bootloaders in the 5/14 nightly I believe as there were lots of people complaining about random crashes and supposedly much fewer reports on newer firmwares. I actually wasn't having this problem very much with LeanKernel, though it did seem to be happening like crazy at some point.
I actually didn't know about all the bootloader versions for our phones until today, it was interesting diving into all this stuff. I discovered at the beginning I was running with the same firmware the device had shipped with and if Cyanogen hadn't pushed for the newer bootloaders, I might have let things be. But since he pushed for it, I decided might as well have the latest stuff.
Cheers
mnasledov said:
You can always try the original UVDLJC I linked that will work with latest nightlies. I used my own update.zip file that I posted here and my phone works fine now using the latest UVDMD5 full firmware (incl. radio).
Oh yeah -- both these update.zips contain the radio so if you don't want the MD5 or LJC radio, better update it to something else afterward.
You can check my work, read the META-INF/com/google/android/updater-script file. You can dd all those mmcblk0pX partitions to backup files, too. Maybe I'll make a firmware back up script while I'm at it.
There's nothing really scary about this -- you get these exact same files flashed to your phone in the same place if you use the UVDMD5 stuff in Odin, except you'll probably overwrite your recovery and system as well and spend extra time restoring it.
Steps for using it, in case this is unclear:
(1) Put this .zip file on the root of your sdcard.
(2) Reboot to recovery
(3) Choose .zip file from sdcard and select this file and flash it.
(4) Reboot and you're done. I didn't find any wiping of any kind necessary.
I'm running cm10.1-20130513-d2tmo with imoseyeon's leankernel 5.9 on my SGH-T999. Haven't upgraded to the newer nightly yet as nothing looked interesting enough in the changelog.
Oh and:
Code:
[email protected]:/ # getprop ro.bootloader
T999UVDMD5
Click to expand...
Click to collapse
Seen this after I flashed it.....it works perfect, I did a clean install just to have things fresh.
Sent from my SGH-T999 using Tapatalk 2
I don't know if I have a newer bootloader or not but flashed cm 10.1 and it runned perfect how do I know if I have it.
mnasledov said:
You can always try the original UVDLJC I linked that will work with latest nightlies. I used my own update.zip file that I posted here and my phone works fine now using the latest UVDMD5 full firmware (incl. radio).
Oh yeah -- both these update.zips contain the radio so if you don't want the MD5 or LJC radio, better update it to something else afterward.
You can check my work, read the META-INF/com/google/android/updater-script file. You can dd all those mmcblk0pX partitions to backup files, too. Maybe I'll make a firmware back up script while I'm at it.
There's nothing really scary about this -- you get these exact same files flashed to your phone in the same place if you use the UVDMD5 stuff in Odin, except you'll probably overwrite your recovery and system as well and spend extra time restoring it.
Steps for using it, in case this is unclear:
(1) Put this .zip file on the root of your sdcard.
(2) Reboot to recovery
(3) Choose .zip file from sdcard and select this file and flash it.
(4) Reboot and you're done. I didn't find any wiping of any kind necessary.
I'm running cm10.1-20130513-d2tmo with imoseyeon's leankernel 5.9 on my SGH-T999. Haven't upgraded to the newer nightly yet as nothing looked interesting enough in the changelog.
Oh and:
Code:
[email protected]:/ # getprop ro.bootloader
T999UVDMD5
Click to expand...
Click to collapse
NM
Sent from my SGH-T999 using xda app-developers app
I thought about making one of these. The only reason I didn't is because I don't know how Odin is working.
If it is just using an equivalent to dd, then why do the filenames have different extensions? Why do they have extensions at all? WTB Odin source code.
Aerowinder said:
I thought about making one of these. The only reason I didn't is because I don't know how Odin is working.
If it is just using an equivalent to dd, then why do the filenames have different extensions? Why do they have extensions at all? WTB Odin source code.
Click to expand...
Click to collapse
It is just DD which is what basically Odin would do anyway. The filenames are irrelevant. It's what data goes to which mmcblk0 partition. The file names are what they are as they are taken from the T999 UVDMD5 Odin .zip and for clarity. Why would I rename aboot.mbn to some random file name?
Just run heimdall print-pit some day and you can see how your eMMC is partitioned and what goes where. I could've flashed all these files with heimdall using the correct named partition identifiers rather than numeric identifiers, but I found it more convenient to make a flashable update.zip.
Update however you want, but as someone who doesn't use Windows and doesn't like screwing around with heimdall / Download Mode much, just dd'ing the files to the correct partitions was the most elegant solution I could find.
Nice work!
I don't know if you just copied the other one, but the comments in the script are great, it's easy to tell what's what. I may try to make one of these that doesn't flash the system bits, so the folks running CM10 that just want the latest nightly can just flash a zip and carry on instead of asking a billion questions. I think that means only including the aboot, rpm, tz, and modem pieces, right? The sbl ones aren't needed if you want to stay with CM.
mondokat said:
I don't know if you just copied the other one, but the comments in the script are great, it's easy to tell what's what. I may try to make one of these that doesn't flash the system bits, so the folks running CM10 that just want the latest nightly can just flash a zip and carry on instead of asking a billion questions. I think that means only including the aboot, rpm, tz, and modem pieces, right? The sbl ones aren't needed if you want to stay with CM.
Click to expand...
Click to collapse
Thanks though I can't take credit for writing the script. I just extracted the UVDLJC firmware updater script written by another dev, substituted the UVDMD5 files in, updated the script with the new SHA1 sums, and re-zipped it, thus making a flashable UVDMD5 updater script.
It does not flash the system -- it just flashes aboot, rpm, tz, modem, and some sbl files. I run CM10.1 and was able to just flash this without killing any of my system stuff. Recovery, system, kernel, etc. are all preserved. You can make a backup (as anyone should anyway), but you shouldn't need to do any restore or even a cache wipe after flashing either UVDLJC or UVDMD5 updater since it's just bootloader, modem, and some other pieces unrelated to system/kernel.
In retrospect, it would've been trivial to extend the script to create backups of the current partitions on the phone. In fact, I'm pondering a "firmware flasher" script that gives one a menu of different firmwares and ability to backup/restore for fun. Then again, I've never touched these firmware bits until Cyanogen necessitated a newer bootloader in CM10.1.
Anyway, I modified this script for myself at first and I had spent the whole day trying to research the topic without too much info. I saw S3s from other carriers had update ZIPs and was frustrated at the lack of one for d2tmo. After testing it on myself successfully and realizing how safe it is, I decided to just release it so people can benefit from it by upgrading their firmware or ripping it apart and learning how it works and/or making it better.
On a side note, do you know what the SBL files are for? You say they're not needed for CM but I ended up updating them anyway (as this script does) and it didn't break anything with CM. I figured it was best practice to just update them, but I could be wrong. Any insight on this would be greatly appreciated as I couldn't find much info.
Thanks for putting this together it has made a huge difference for me with the new radio I have gained 7 mb down and 3 mb up from this I'm running jovy stockoaroma rom right now :thumbup: great idea I was going to odin so I could update that now I don't have to...
Sent from my SGH-T999 using Tapatalk 2
How can you check what bootloader you have?
Sent from my SGH-T999 using xda premium
mnasledov said:
On a side note, do you know what the SBL files are for? You say they're not needed for CM but I ended up updating them anyway (as this script does) and it didn't break anything with CM. I figured it was best practice to just update them, but I could be wrong. Any insight on this would be greatly appreciated as I couldn't find much info.
Click to expand...
Click to collapse
Here's what I found:
http://tjworld.net/wiki/Android/HTC/Vision/BootProcess
SBL = Secondary Boot Loader
According to the article, the sbl is something like an efi bios, basically it turns on a bunch of hardware bits and then hands off to the next stage of booting. So I guess now we know. :silly: I'd think if you are updating the boot loader, you'd want to include the secondary bootloader as well. Probably your zip file is correct in that if you update any of those pieces, you should PROBABLY update all of them to the same revision, just in case.
Which means EXTRA thanks to you, for doing the work. Now when people say "why can't I flash the latest CM10?" we can just point to this thread and say "flash that first".
:highfive:
Thanks op so much for this. Running the latest cm nightlies again
Sent from my SGH-T999 using xda premium
djtheraven said:
How can you check what bootloader you have?
Sent from my SGH-T999 using xda premium
Click to expand...
Click to collapse
Just open up a shell either in your ROM or CWM Recovery (adb shell) and run:
Code:
$ getprop ro.bootloader
It should print out something like "T999UVDMD5"
I had T999UVALG1 before I upgraded the firmware.
EDIT: If you're going to do it in CWM Recovery, you might have to do it as root. Make sure to adb kill-server as root to kill any adb servers that may be running and a subsequent adb shell should grant you access.
Okay so here is my issue. I'm literally stuck! I have no computer to go back and lock my bootloader and I'm not s-off. I have no way, to my knowledge, to install the new firmware to play with the new stock roms. If anybody has any suggestion, that would be terrific!
Are you on stock rom? If yes you only need to flash stock recovery. Relocking bootloader is not needed
stathis95194 said:
Are you on stock rom? If yes you only need to flash stock recovery. Relocking bootloader is not needed
Click to expand...
Click to collapse
How would I go about flashing stock recovery?
Unfortunately you will need a PC for this . Are you on custom recovery now? How did you flash that in the first place?
stathis95194 said:
Unfortunately you will need a PC for this . Are you on custom recovery now? How did you flash that in the first place?
Click to expand...
Click to collapse
I did it from a computer at work. I no longer have that job though. So I'm seriously stuck.
Surely, you know someone with a computer that they will let you use?
redpoint73 said:
Surely, you know someone with a computer that they will let you use?
Click to expand...
Click to collapse
This ^^^^
alright, here's an update. i went to my fiances house and used her mothers computer (worlds slowest internet, i think AOL is faster) and worlds oldest computer ... anyways... i locked my bootloader and flashed a stock recovery, i went back to my stock rom as well and checked the software update from AT&T (which said that I had an update before i did all this) but now when i check for an update it says that i'm currently up to date and when i check information from online and compare it to my information i can confirm that I am on 1.58 but i'm android 4.4.2 and VIPER calls for a stock firmware of 4.4.3 (i think) also i can't find anywhere online on information on what the current radio is of the newest update. i'm trying to make sure that everything that I have is current to date. I don't want to be outdated lol . anways , i'm trying to figure out how to run viper with the current firmware that they require. thank you for any help you can give me now
EDIT : i bought this phone about 3 months ago and i HAVENT made any updates since then. i rooted it as soon as i got it. so im not sure if i am up-to-date
PureLife90 said:
also i can't find anywhere online on information on what the current radio is of the newest update. i'm trying to make sure that everything that I have is current to date. I don't want to be outdated lol .
Click to expand...
Click to collapse
Radio associated with software 1.58 (latest software before the new 2.23 now rolling out) is: 1.16.21331931.LA11G_20.31A.4145.02L
But in any case, the RUU for 2.23 is now available. So you can just run the "official" RUU: http://www.htc.com/us/support/htc-one-m8-att/news/
Or the bootable version (no PC required) here: http://forum.xda-developers.com/att-htc-one-m8/general/att-2-23-502-3-bootable-ruu-pc-required-t2860486
Just relock the bootloader (since you are s-on) and run the RUU. It doesn't matter if anything on the device is not updated, as RUU contains the complete image. Just backup your personal data, as it will be wiped.
stathis95194 said:
Unfortunately you will need a PC for this . Are you on custom recovery now? How did you flash that in the first place?
Click to expand...
Click to collapse
If he was rooted he could have restored the stock recovery without a PC pretty easily.
There used to be a command flash_image in the terminal emulator(Need to download binary for it I think). Don't know if it still works or not though
flash_image recovery /path-to-image/name_of_recovery.img
Even then there is always the "dd" command to use.
Download recovery file to phone, if it's zipped then uzip it and move the recovery.img file to /sdcard/ - Can use ES File explorer or Root explorer.
Open Terminal Emulator.
Type:
su - to get # if you don't have it.
cat /proc/emmc - this will dump all the partition info in the terminal, look for recovery. WWE should all be mmcblk0p43 , just make sure either way.
When you have the partition number for recovery go and type:
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p43 - that's it.
You just "flashed" back stock recovery. No PC required.
Hi, I've talked of this before. The firmware update, I tried returning to stock then attempting to update the firmware through updating the software OTA but that failed no matter what I did. I returned to stock, flashed the stock recovery, and even locked the bootloader. And finally I attempted an RUU but the RUU failed. So now I lost all my data in vain. I rooted the phone again and reflashed it to Insert coin android 4.4.4, ect.. And I currently am really tired of this. Isn't there any way to get through this? I want the new Insert Coin Lollipop but I have S-ON and cant update the firmware. Can someone please help me? It would be really appreciated. Thanks for reading this lousy comment.
Ali7000 said:
Hi, I've talked of this before. The firmware update, I tried returning to stock then attempting to update the firmware through updating the software OTA but that failed no matter what I did. I returned to stock, flashed the stock recovery, and even locked the bootloader. And finally I attempted an RUU but the RUU failed. So now I lost all my data in vain. I rooted the phone again and reflashed it to Insert coin android 4.4.4, ect.. And I currently am really tired of this. Isn't there any way to get through this? I want the new Insert Coin Lollipop but I have S-ON and cant update the firmware. Can someone please help me? It would be really appreciated. Thanks for reading this lousy comment.
Click to expand...
Click to collapse
I don't know anything about Insert Coin. But if you want stock lollipop from Rogers, you could restore a Nandroid backup via TWRP.
For a start, post your fastboot getvar all (without serial no. and imei no.)
Then most probably the nandroid that ikeny mentioned is the right backup.
I'd be more worried about the RUU failing - I wonder what the error code was?
If OP's M8 was Rogers branded, CID ROGER_001, then RUU from Rogers never existed in the first place. Perhaps this explains the error.
ikeny said:
If OP's M8 was Rogers branded, CID ROGER_001, then RUU from Rogers never existed in the first place. Perhaps this explains the error.
Click to expand...
Click to collapse
Yes, that would be correct. That's my first assumption. Although do you have any methods to update my firmware to the latest android 5.1 lolipop?
Ali7000 said:
Yes, that would be correct. That's my first assumption. Although do you have any methods to update my firmware to the latest android 5.1 lolipop?
Click to expand...
Click to collapse
Use the TWRP nandroid backup image at the bottom of the first post -
http://forum.xda-developers.com/htc-one-m8/help/rogers-m8-lollipop-update-error-t3020675
ikeny said:
I don't know anything about Insert Coin. But if you want stock lollipop from Rogers, you could restore a Nandroid backup via TWRP.
Click to expand...
Click to collapse
I'm actually kinda wondering, is there a method to update to lollipop without returning to stock? I don't have S-OFF so I cant update the firmware alone. All I want is to update the firmware somehow and then I'd be able to use the latest Insert Coin Lollipop Rom. Although thanks a ton for that link, I'll use it as my last resort.
ikeny said:
Use the TWRP nandroid backup image at the bottom of the first post -
http://forum.xda-developers.com/htc-one-m8/help/rogers-m8-lollipop-update-error-t3020675
Click to expand...
Click to collapse
So just a confirmation before I get started, I can just restore this backup despite being in a custom rom at the moment? And will this erase all my data on the phone such as media, ext...? Thanks man, appreciate it a lot.
Ali7000 said:
So just a confirmation before I get started, I can just restore this backup despite being in a custom rom at the moment? And will this erase all my data on the phone such as media, ext...? Thanks man, appreciate it a lot.
Click to expand...
Click to collapse
Yes, and yes.
If you want future OTA, replace TWRP with the attached stock recovery as the final step.
ikeny said:
Yes, and yes.
If you want future OTA, replace TWRP with the attached stock recovery as the final step.
Click to expand...
Click to collapse
Hmnn...Thank you very much. I appreciate it a lot. So now that I have downloaded the last link to the first post which named "Rogers_5_0_1.zip" I just have to backup all my media, apps, ect...Then I can restore the lollipop backup, root the phone, then install Insert Coin 5.1. And I'm also assuming the data being wiped is absolutely unavoidable.
Ali7000 said:
Hmnn...Thank you very much. I appreciate it a lot. So now that I have downloaded the last link to the first post which named "Rogers_5_0_1.zip" I just have to backup all my media, apps, ect...Then I can restore the lollipop backup, root the phone, then install Insert Coin 5.1. And I'm also assuming the data being wiped is absolutely unavoidable.
Click to expand...
Click to collapse
After you unzip the file, you will get the TWRP nandroid image. This image is a 100% stock, and all your files and apps will be wiped. Unavoidable. You could follow the second post in the previous link for rooting. Beyond that, you are on your own.
ikeny said:
After you unzip the file, you will get the TWRP nandroid image. This image is a 100% stock, and all your files and apps will be wiped. Unavoidable. You could follow the second post in the previous link for rooting. Beyond that, you are on your own.
Click to expand...
Click to collapse
Thanks man, I appreciate all your support. I also notice that you were the one who posted nandroid. Many thanks for everything pal.
ikeny said:
After you unzip the file, you will get the TWRP nandroid image. This image is a 100% stock, and all your files and apps will be wiped. Unavoidable. You could follow the second post in the previous link for rooting. Beyond that, you are on your own.
Click to expand...
Click to collapse
Hi, I unzipped the Rogers_5_0_1.zip file and it came out a folder named "2015-02-05--12-39-33 LRX22C release-keys" and an img file named "recovery.img." Do I just copy the folder to my backup TWRP folder then ignore the img file? Sorry for being really annoying and asking a lot of question, I just wanna make sure I'm doing it right.
Ali7000 said:
Hi, I unzipped the Rogers_5_0_1.zip file and it came out a folder named "2015-02-05--12-39-33 LRX22C release-keys" and an img file named "recovery.img." Do I just copy the folder to my backup TWRP folder then ignore the img file? Sorry for being really annoying and asking a lot of question, I just wanna make sure I'm doing it right.
Click to expand...
Click to collapse
You don't need the img file now. That was the stock recovery, for later, if you want to replace the TWPR recovery.
ikeny said:
You don't need the img file now. That was the stock recovery, for later, if you want to replace the TWPR recovery.
Click to expand...
Click to collapse
Thanks a ton man, you honestly don't know how thankful I am now. I'm copying the folder right now and I'm gonna restore it.
Hi everybody, i got an european m8 and i was going to OTA to 4.16.401.13 but i modified my build.prop a while ago and the update doesn't start. Can anyone be so kind to post the original build.prop of OTA 4.16.401.10?
Thanks
ture1989 said:
Hi everybody, i got an european m8 and i was going to OTA to 4.16.401.13 but i modified my build.prop a while ago and the update doesn't start. Can anyone be so kind to post the original build.prop of OTA 4.16.401.10?
Thanks
Click to expand...
Click to collapse
I don't think with the original build.prop, OTA will succeed. Once you rooted your ROM, there are many changes made to the system. The best is to restore a 4.16.401.10 system partition only and your data will be there untouched.
Anyway .. here is the original build.prop ...extract it as I put it in zip.
If you need more files later.. then I suggest download a non-rooted nandroid and restore system partition only.
ckpv5 said:
I don't think with the original build.prop, OTA will succeed. Once you rooted your ROM, there are many changes made to the system. The best is to restore a 4.16.401.10 system partition only and your data will be there untouched.
Anyway .. here is the original build.prop ...extract it as I put it in zip.
If you need more files later.. then I suggest download a non-rooted nandroid and restore system partition only.
Click to expand...
Click to collapse
Hi, the OTA worked after i used your file, but now the phone doesn't boot and gets stuck on the start up screen (it plays the start up sound). I guess i need to restore the system folder, i took a look on that link you have in signature but there's no backup for 4.16.401.13. Do you know where i can get o extract it from?
Thanks
EDIT: Problem solved, i re-flashed supersu and xposed and the phone booted!
ture1989 said:
Hi, the OTA worked after i used your file, but now the phone doesn't boot and gets stuck on the start up screen (it plays the start up sound). I guess i need to restore the system folder, i took a look on that link you have in signature but there's no backup for 4.16.401.13. Do you know where i can get o extract it from?
Thanks
Click to expand...
Click to collapse
It's best for you to restore system partition of 4.16.401.10 and its stock recovery and redo the OTA.
(as I mentioned earlier)
Noted your problem solved. In case anyone needs 4.16.401.13 backup, TWRP nandroid is added in my thread (as linked in my signature)