Related
Yes, we're all noobs!!!
I have a brand new Excalibur (I bricked my first one five mins. out of the box) and I attempt to upgrade following instructions on the tutorial posted on these forums.
What's not stated on said tutorial (and no one tells you, only after you bricked your phone) is that YOU MUST BACK UP YOUR ORIGINAL ROM before the upgrade, because if anything goes wrong, that is the only ROM you can flash to your phone to restore it, otherwise IT IS BRICKED. (Believe me, it happened to me).
So, to all you experts reading these, please, help us noobs and post here a complete guide on how to back up your original ROM.
We will thank and worship you forever!!!
These days, there is no need to backup your own Rom.
We have a collection of ROMs on this site alone. Or in my signature.
I do suggest to download one prior to updating your ROM.
This forum uses most of a collection of ROM i have uploaded for everyone.
Click here for the forum of original ROMS
Mikey1022 said:
These days, there is no need to backup your own Rom.
We have a collection of ROMs on this site alone. Or in my signature.
I do suggest to download one prior to updating your ROM.
This forum uses most of a collection of ROM i have uploaded for everyone.
Click here for the forum of original ROMS
Click to expand...
Click to collapse
I have two questions: Firstly, there is no official O2 Xda Cosmo ROM or? Secondly, if you back up the ROM first, how can you flash it back to the device? Is there a tutorial for this?
Thanks
READ this thread
uccellino said:
I have two questions: Firstly, there is no official O2 Xda Cosmo ROM or? Secondly, if you back up the ROM first, how can you flash it back to the device? Is there a tutorial for this?
Thanks
Click to expand...
Click to collapse
yeah i'm waiting for the official O2 Xda cosmo ROM. i need it badly because my camera doesn't work anymore with new ROM. and i am totally agree to write a clear reminder to backup your original ROM first before upgrading in the upgrading ROM thread. just in case for noob like me....
Mikey1022 said:
READ this thread
Click to expand...
Click to collapse
After rereading, I still have the questions:
1. How is it possible to flash back a saved backup ROM image?
2. If I use a USPL and then something goes wrong while flashing a cooked ROM, can I only re-flash my original ROM (i.e. for XDA Cosmo which doesn't exist)?
Thanks
Okay - maybe I just figured out the answer to my own question: if I flash the USPL-RUU first before flashing a ROM update, maybe this means I can reflash if something goes wrong? Is this correct, or is there a chance that the SPL get overwritten before the error and I still get stuck?
Well, in fact, it is necessary...
Mikey1022 said:
These days, there is no need to backup your own Rom.
We have a collection of ROMs on this site alone. Or in my signature.
I do suggest to download one prior to updating your ROM.
This forum uses most of a collection of ROM i have uploaded for everyone.
Click here for the forum of original ROMS
Click to expand...
Click to collapse
...When I mean original ROM, I mean the ROM that could only work on a CID-Locked-by-a-carrier Excalibur, not the HTC WW ROM release.
Also, many of us noobs are international, I doubt that on the ROM database on this website we'll be able to find, say, the Movistar Mexico HTC Excalibur WM5 1.15.0000 ROM, which in my case, is the only one I would be able to flash in case anything goes wrong on the upgrade attempt. (I dedicated a week searching this ROM for the first Excalibur I bricked, no results)
Therefore - and I really hate to contradict -, for many of us, a ROM backup IS necessary and a tutorial from you experts on how to do it would be a great, great contribution to this community. (And also to the database, 'cause I'll definitively upload my ROM once I back it up)
velascoperroni said:
...When I mean original ROM, I mean the ROM that could only work on a CID-Locked-by-a-carrier Excalibur, not the HTC WW ROM release.
Also, many of us noobs are international, I doubt that on the ROM database on this website we'll be able to find, say, the Movistar Mexico HTC Excalibur WM5 1.15.0000 ROM, which in my case, is the only one I would be able to flash in case anything goes wrong on the upgrade attempt. (I dedicated a week searching this ROM for the first Excalibur I bricked, no results)
Therefore - and I really hate to contradict -, for many of us, a ROM backup IS necessary and a tutorial from you experts on how to do it would be a great, great contribution to this community. (And also to the database, 'cause I'll definitively upload my ROM once I back it up)
Click to expand...
Click to collapse
Actually, it's quite easy to CID unlock your phone to load whatever ROM you want. Much easier in fact, than dumping your current ROM and restoring it. I was able to flash my first ROM within about 30 minutes of reading on this forum, and had no problems at all.
velascoperroni said:
...When I mean original ROM, I mean the ROM that could only work on a CID-Locked-by-a-carrier Excalibur, not the HTC WW ROM release.
Also, many of us noobs are international, I doubt that on the ROM database on this website we'll be able to find, say, the Movistar Mexico HTC Excalibur WM5 1.15.0000 ROM, which in my case, is the only one I would be able to flash in case anything goes wrong on the upgrade attempt. (I dedicated a week searching this ROM for the first Excalibur I bricked, no results)
Therefore - and I really hate to contradict -, for many of us, a ROM backup IS necessary and a tutorial from you experts on how to do it would be a great, great contribution to this community. (And also to the database, 'cause I'll definitively upload my ROM once I back it up)
Click to expand...
Click to collapse
I completely agree with you
I just have no idea how to restore a backed-up ROM and I haven't read anything saying how to do it either. As you say, many of us a stuck with devices CID locked to some international ROM that is impossible to get.
So once again the question: Does anyone know how to re-flash a backed-up ROM?
I'm no expert but all I'm going to say is this. If you have a Rom from a different carrier that has not leaked to the public, then you are probably out of luck. You take the risk of hoping your phone will not have serious problems down the line of your contract or usage. You should pick up insurance on your phone depending on the stipulations your carrier has about lost or stolen or even broken phones. In that case you could return/replace your phone if need be after modifying it to your liking. I also would suggest that the entire reason we are here is that we don't want to be like the norm. We want what we paid for and don't want to be restricted. It's a risk. You must make that choice and succeed or fail that's not anyone's problem but your own. With all the Roms out there you should find one to your liking. If you brick your phone which seems so much more difficult than my razr modding days, than sell it for parts and lesson learned.
In the U.S. the Open Headset Alliance is our future so what we do to our phones in the future will be our choice.
Good Modding
Pfunk
C'mon guys...
Wy all the negativity?
I'm I conspiring against copyright laws if I want to have a backup of the ROM I paid for?
Is backing up a ROM frowned upon on this community? or is it so easy (from what I can gather it requires "dumping" and "restoring") that it is even insulting for me to ask you how to do it?
Yes, we are all here because we don't conform to the norm, but we are all HERE to help each other out. Why the closure? Why the elitism?
Like all of you, I want to take full advantage of the piece of technology I acquired without the restrictions installed on them by the phone corps. Yes, I would like to have the minimum risks while doing so, and yes, I would like to do it as cost effective as I can, just as anyone of you would.
It is a risk to upgrade a Cid.Locked phone with the bypass provided on this website, It happened to me and to many: USB cord unplugs and voila, bricked phone.
One alternative is to pay $40 bucks for a permanent Cid.Unlock, which will allow you to flash and flash and flash, even if you get stuck in the middle of one process.
The other, used by many here who wont pay, is to use the Cid bypass, while having a backup original rom "just in case".
What I only ask (for myself and my peer noobs) is to have this same other alternative as many, many of you.
Really, is it to hard to post the following?
1. Downoad these softwares;
2. Do this to "dump";
3. Do that to "restore";
4. To re-flash, do this.
C'mon, all for one and one for all right?
p.s. For my friend asking how to re-flash a backed up ROM, from what I've gathered, it goes something like this: your backed up ROM must be in a *.bn format (I still don't know how to even achieve this); then you must get a hold of any HTC RUU Software, extract it (Winrar) and replace the *.bn file inside the extracted folder with your *.bn file; with the HTC connected in bootloader mode, run the exe file in the extracted folder.
velascoperroni said:
...I doubt that on the ROM database on this website we'll be able to find, say, the Movistar Mexico HTC Excalibur WM5 1.15.0000 ROM, which in my case, is the only one I would be able to flash in case anything goes wrong on the upgrade attempt. (I dedicated a week searching this ROM for the first Excalibur I bricked, no results)
Therefore - and I really hate to contradict -, for many of us, a ROM backup IS necessary and a tutorial from you experts on how to do it would be a great, great contribution to this community. (And also to the database, 'cause I'll definitively upload my ROM once I back it up)
Click to expand...
Click to collapse
The Official ROMs collection is as full as I can make it. To have more images, we need everyone to upload ones that are missing to something like rapidshare, mediafire, or one of a few dozen other hosting sites, then tell up here on xda dev. Or upload it to several yourself. Spreading things on the net is much easier than ripping the ROM out anyway, and you benefit from the online backups, too.
So, yes, if you aren't going to back up your ROM, hope that someone else already has. Or, even better, be that first guy who does it, to make things easier for the rest of us. Besides, we might want to see what kinda goodies are tucked in the Movistar version
Indeed!
Profezza said:
...Or, even better, be that first guy who does it, to make things easier for the rest of us. Besides, we might want to see what kinda goodies are tucked in the Movistar version
Click to expand...
Click to collapse
Thanks for the support Profezza, indeed I intend to be the first, but in order to do that, I need to know how to do it.
I'll keep my hopes up for someone to post here the procedure for backing up my own ROM.
Also, the Movistar version is pretty lame, at least it would be a language addition to the database since it is originally in Spanish.
velascoperroni said:
Thanks for the support Profezza, indeed I intend to be the first, but in order to do that, I need to know how to do it.
I'll keep my hopes up for someone to post here the procedure for backing up my own ROM.
Click to expand...
Click to collapse
My post kinda ignored that point, as... I don't actually know how it is done.
velascoperroni said:
Also, the Movistar version is pretty lame, at least it would be a language addition to the database since it is originally in Spanish.
Click to expand...
Click to collapse
I think the version # system is controlled by HTC and fairly consistent across brandings, so it looks like it is a rather old one, but yeah, it could handy just for the Spanish. And ya never know, maybe a better graphic or two in some odd corner. I'll come back and bump this if it looks like it is fading away.
velascoperroni said:
p.s. For my friend asking how to re-flash a backed up ROM, from what I've gathered, it goes something like this: your backed up ROM must be in a *.bn format (I still don't know how to even achieve this); then you must get a hold of any HTC RUU Software, extract it (Winrar) and replace the *.bn file inside the extracted folder with your *.bn file; with the HTC connected in bootloader mode, run the exe file in the extracted folder.
Click to expand...
Click to collapse
Hi velascoperroni!
Thank you for your help - this is helping me to get closer to understanding
Basically I have my old ROM image as .img files (actually 5 of them) produced by bkondisk, together with a log file saying what goes where. So now all we need to figure out is how to turn these back into a .bn file and we'll be in business. For info on bkondisk, which lets you save your ROM (as .img files), see this wiki http://wiki.xda-developers.com/index.php?pagename=bkondisk
Could anyone point me to some resources on these two file formats? Then maybe we could come up with a conversion program when one doesnt exist
Getting closer!
Great, it seems we are getting closer to our goal!!!
But still surprises me that no one has posted a complete how to... perhaps the only few who know the deal haven't read this thread yet.
Now we know the following:
1. Bkondisk: software that allows to backup ROM in *.img format.
2. The original format of the ROM is *.bn
We don't know if the *.img file needs to be converted to *.bn or if they are compatible.
I also found out about an easier method to re-flash the ROM:
1. Format your SD Card in FAT32;
2. Copy your *.bn file to your SD Card;
3. Turn off phone, insert SD Card, Turn on phone in bootloader mode;
4. The phone should automatically recognize the ROM and start the flashing process.
Uccelino: Try placing the *.img file in the SD Card instead of the *.bn file. Maybe, just maybe the phone also recognizes *img files!
Getting closer!
Great, it seems we are getting closer to our goal!!!
But still surprises me that no one has posted a complete how to... perhaps the only few who know the deal haven't read this thread yet.
Now we know the following:
1. Bkondisk: software that allows to backup ROM in *.img format.
2. The original format of the ROM is *.bn
We don't know if the *.img file needs to be converted to *.bn or if they are compatible.
I also found out about an easier method to re-flash the ROM:
1. Format your SD Card in FAT32;
2. Copy your *.bin file to your SD Card;
3. Turn off phone, insert SD Card, Turn on phone in bootloader mode.
4. The phone should automatically recognize the ROM and start the flashing process.
Uccelino: Try placing the *.img file in the SD Card instead of the *.bin file. Maybe, just maybe the phone also recognizes *img files!
Also...
Sorry for the double post back there!!
Also check out this thread I started when I bricked my first Excalibur:
http://forum.xda-developers.com/showthread.php?t=378050
I never got a feasible response to wether sprite backup would work or not, and I did not want to spend $30 bucks to find out.
velascoperroni said:
Great, it seems we are getting closer to our goal!!!
But still surprises me that no one has posted a complete how to... perhaps the only few who know the deal haven't read this thread yet.
Now we know the following:
1. Bkondisk: software that allows to backup ROM in *.img format.
2. The original format of the ROM is *.bn
We don't know if the *.img file needs to be converted to *.bn or if they are compatible.
I also found out about an easier method to re-flash the ROM:
1. Format your SD Card in FAT32;
2. Copy your *.bin file to your SD Card;
3. Turn off phone, insert SD Card, Turn on phone in bootloader mode.
4. The phone should automatically recognize the ROM and start the flashing process.
Uccelino: Try placing the *.img file in the SD Card instead of the *.bin file. Maybe, just maybe the phone also recognizes *img files!
Click to expand...
Click to collapse
I just had an idea: I will flash a ROM, back it up, and compare the *.bn files to the *.img files I get from backing up - maybe they are or are almost the same, and we can convert them
I will try. Thanks
I have rooted my Xperia Play and used Titanium Backup to remove the bloat. I've got a backup of the System Apps folder so I can reinstall manually if needed. Is there any sort of Recovery that I can use to make a Nandroid, or is there some file somewhere I can download to restore back to factory when/if ICS is released for Verizon customers? And how do I know if I have an I, X, A, or whatever?
I've tried searching here in the forum, but with all the UK vs US, Orange, Rogers, Verizon, [Insert Your Carrier Here], locked BL vs unlocked BL posts, I can't seem to find answers to those 2 simple questions.
Thanks for your help and your patience. I'm new to this phone, but not new to rooting or Android.
I will help as much as I can
In order for us VZW Plays to have a custom recovery(to create a Nandroid), we have to unlock our bootloader. Which sadly for us VZW users, we have to pay to get ours unlocked by members here on the forum. From what I have read and heard they are great at it and don't leave you hanging. I personally think that VZW will release ICS for us, don't know when, later on Hope I helped.
Well I did read something about FTF (whatever that is) and stock firmware in the development thread, but I don't know which phone they are for. Also, I can't seem to download anything from a DropBox link. I always get a 404 page.
I did figure out if I go into about phone I can find my model (800x) and firmware version information. So that's progress, sort of.
netizenmt said:
Well I did read something about FTF (whatever that is) and stock firmware in the development thread, but I don't know which phone they are for. Also, I can't seem to download anything from a DropBox link. I always get a 404 page.
I did figure out if I go into about phone I can find my model (800x) and firmware version information. So that's progress, sort of.
Click to expand...
Click to collapse
You are on the right track. The R800x State of Development thread is for us Verizon users. The FTF files will get you completely back to stock and does not require an unlocked bootloader. You use a program called Flashtool.
Sent from my R800x using XDA App
I thought so, but I haven't been on this site long enough to post my question there. I tried to download the necessary files, but for some reason, I always get a 404 page when I try to download anything from DropBox.
If I were to delete the bloatware apps and a system update rolls around, I just need to reinstall the removed apps and the update should run, right?
maddog00 said:
If I were to delete the bloatware apps and a system update rolls around, I just need to reinstall the removed apps and the update should run, right?
Click to expand...
Click to collapse
Correct BUT it can be a PIA to remember which ones you removed.
I would either just freeze them with Titanium Backup or flash the FTF files when an update comes out.
HotShotAzn said:
Correct BUT it can be a PIA to remember which ones you removed.
I would either just freeze them with Titanium Backup or flash the FTF files when an update comes out.
Click to expand...
Click to collapse
Yeah, in retrospect, I should have thought to write down what I removed before I did so, but...
Once a noob, always a noob, I guess.
Hey guys, I am new to this forum here but before anyone flames me, I did read the faqs and tried to uninstall from there but it did not work out. Apparently I dont think you can get rid of CM11 since you cant install any stock firmware older than it? Before I installed CM11, I was on jellybean. I had tried to find the latest kitkat update for the s3 (att) and there is no file of it found online (tried sammobile). When I tried flashing an older firmware with ODIN, it just fails at "NAND!". Any help would be appreciated. I am COMPELETELY new at this so specific directions would be appreciated!
I really do love cyanogenmod but there are simply too many glitches and not enough guidance on how to fix em. I am, however, currently using it on my HP touchpad, if anyone remembers what it is . Maybe ill go back to using it in the future.
thanks!
Your rom (cm) has nothing to do with what firmware you can or cannot flash. Once you have updated to 4.3 firmware or newer, you can only flash the same or newer firmware in odin from now on. (Regardless of firmware you can still flash older roms btw)
Using terminal emulator, enter this to find your current firmware build:
getprop ro.bootloader
I suspect you are on a 4.3 build. So odin flash that same firmware. You can find it in these forums. After that you can get the ota to update fully to kk.
There are other methods of updating. Just check the General section. (enewman17 has a few threads that will help)
Note: anytime you go between touchwiz and non touchwiz roms, you will have to factory reset or it'll hang at boot.
DocHoliday77 said:
Your rom (cm) has nothing to do with what firmware you can or cannot flash. Once you have updated to 4.3 firmware or newer, you can only flash the same or newer firmware in odin from now on. (Regardless of firmware you can still flash older roms btw)
Using terminal emulator, enter this to find your current firmware build:
getprop ro.bootloader
I suspect you are on a 4.3 build. So odin flash that same firmware. You can find it in these forums. After that you can get the ota to update fully to kk.
There are other methods of updating. Just check the General section. (enewman17 has a few threads that will help)
Note: anytime you go between touchwiz and non touchwiz roms, you will have to factory reset or it'll hang at boot.
Click to expand...
Click to collapse
..
I am on "I747UCUEMJB"
and i am not sure what build i am on but according to my "build number"this is what it says: "cm_d2att-userbug 4.4.2 KOT49H"
The main issue is, I cannot find 4.3 update anywhere on the internet
The MJB is your current firmware/bootloader build/version.
The build number displayed in settings only represents the rom, which is often different, and doesnt really matter to much.
From this post/thread
http://forum.xda-developers.com/showthread.php?p=52341560
Direct link to MJB firmware
http://www.androidfilehost.com/?fid=23329332407590581
DocHoliday77 said:
The MJB is your current firmware/bootloader build/version.
The build number displayed in settings only represents the rom, which is often different, and doesnt really matter to much.
From this post/thread
http://forum.xda-developers.com/showthread.php?p=52341560
Direct link to MJB firmware
http://www.androidfilehost.com/?fid=23329332407590581
Click to expand...
Click to collapse
i have no idea what MJB means (i google'd it) and i just found out what my bootloader version is via download mode (its at the very bottom) and i have version 2.0?
ok downloading the giant file now. will report details. just follow instructions in the first link?
[sorry, like i said, im a noob so i really apologize for the lack of terms here]
MJB is just short for I747UCUEMJB. Sorry if I confused you. And the S/W revision being 2.0 is what Odin uses to know what firmware it is allowed to flash. In this case 2.0 tells odin it can flash the MJB firmware, or anything newer.
And yes, follow the instructions he posted and you should be fine.
Oh, and if you did not run the getprop command I posted before, please do so before flashing....just to be on the safe side. If it returns I747UCUEMJB, you are good to go. If it returns anything else, let me know before flashing.
DocHoliday77 said:
MJB is just short for I747UCUEMJB. Sorry if I confused you. And the S/W revision being 2.0 is what Odin uses to know what firmware it is allowed to flash. In this case 2.0 tells odin it can flash the MJB firmware, or anything newer.
And yes, follow the instructions he posted and you should be fine.
Oh, and if you did not run the getprop command I posted before, please do so before flashing....just to be on the safe side. If it returns I747UCUEMJB, you are good to go. If it returns anything else, let me know before flashing.
Click to expand...
Click to collapse
Cool! Got it. I think that was my main problem. I could only find 4.0 (or 4.1) and have been trying to use that on ODIN. Perhaps that was the main issue....
Oh already ran it and got "I747UCUEMJB", sorry if didnt say it properly.
Really appreciate the help! Ive at this for days and no solutions. Sometimes the hacking/custom firmware isnt for everybody
Ill update what happens. Download is taking forever.
EDIT: BTW, for the first link, which poster am I gonna have to follow? im assuming "garbage guy"?
I though you did run the command already, but just wanted to be certain is all. For some reason AT&T stopped releasing their firmware, which has been causing all kinds of problems for people.
Anyway, it sounds like you are good to go! Good luck!
Oh, and if the firmware you're downloading is a .zip or .7z file, make sure you extract it first. Odin only flashes .tar and .tar.md5 files.
DocHoliday77 said:
I though you did run the command already, but just wanted to be certain is all. For some reason AT&T stopped releasing their firmware, which has been causing all kinds of problems for people.
Anyway, it sounds like you are good to go! Good luck!
Oh, and if the firmware you're downloading is a .zip or .7z file, make sure you extract it first. Odin only flashes .tar and .tar.md5 files.
Click to expand...
Click to collapse
Thank you so much! It finally worked! I got the reset notification and I am now back on JB
Thank you! should I take any more steps to ensure I made a clean installation or am I good after flashing it?
david12795 said:
Thank you so much! It finally worked! I got the reset notification and I am now back on JB
Thank you! should I take any more steps to ensure I made a clean installation or am I good after flashing it?
Click to expand...
Click to collapse
Weird, I went straight to update phone and it said my phone is up to date? I thought the official 4.4 update came out for the S3?
david12795 said:
Thank you so much! It finally worked! I got the reset notification and I am now back on JB
Thank you! should I take any more steps to ensure I made a clean installation or am I good after flashing it?
Click to expand...
Click to collapse
Awesome!
really glad to hear that! The only thing I can think of thst you might want to do next is backing up your nv data. The following is a copy/past from a post I made a few min ago... root is required to fo this btw, just so you know.
(Since you are looking to update though, I recommend waiting till you have updated before rooting and running this backup)
It's a super simple procedure and will create an on device backup of your nv data. The backup will be stored on a couple of partitions we never touch, not even with firmware flashes. This essentially makes it a permanent backup. The cool thing about it is every time you reboot, the system checks for any corruption, and if detected, it will automatically restore from this backup. So if it were to ever happen, you probably wouldn't ever even notice it!
Install the Terminal Emulator from the play store. Open and enter this:
su
reboot nvbackup
Thats it! Device will reboot and create your backup. This should prevent you from ever suffering from a lost IMEI!
david12795 said:
Weird, I went straight to update phone and it said my phone is up to date? I thought the official 4.4 update came out for the S3?
Click to expand...
Click to collapse
That has been released, but OTA's are generally rolled out in stages over several weeks. Usually done by region. So it msy not have started in your area just yet.
Two alternatives you can try though, install kies on your computer and update through that. Or there are a couple if threads in the General section that provide the ota for download.
Enewman17 has a few threads helping folks to update so I recommend checking them out as well.
Ive heard that some people have gone to best buy and they were able to initiate the update there. I dont know much more about this though.
DocHoliday77 said:
Awesome!
really glad to hear that! The only thing I can think of thst you might want to do next is backing up your nv data. The following is a copy/past from a post I made a few min ago... root is required to fo this btw, just so you know.
(Since you are looking to update though, I recommend waiting till you have updated before rooting and running this backup)
It's a super simple procedure and will create an on device backup of your nv data. The backup will be stored on a couple of partitions we never touch, not even with firmware flashes. This essentially makes it a permanent backup. The cool thing about it is every time you reboot, the system checks for any corruption, and if detected, it will automatically restore from this backup. So if it were to ever happen, you probably wouldn't ever even notice it!
Install the Terminal Emulator from the play store. Open and enter this:
su
reboot nvbackup
Thats it! Device will reboot and create your backup. This should prevent you from ever suffering from a lost IMEI!
Click to expand...
Click to collapse
Thank you! I will look into this. I just figured for some reason...I would have some data left from cyanogenmod, if that makes sense. In other words, i want my phone to be as fresh as possible. I only ask this because when I had CM, i accidentally made a backup of it through rom manager (or clockwork) and I am not sure if its in my partition somewhere.
That has been released, but OTA's are generally rolled out in stages over several weeks. Usually done by region. So it msy not have started in your area just yet.
Two alternatives you can try though, install kies on your computer and update through that. Or there are a couple if threads in the General section that provide the ota for download.
Enewman17 has a few threads helping folks to update so I recommend checking them out as well.
Ive heard that some people have gone to best buy and they were able to initiate the update there. I dont know much more about this though.
Click to expand...
Click to collapse
TIL that OTA arent as fast. Ill download KIES and give it a try.
Just installed KIES and it said my phone has the latest firmware?
david12795 said:
Thank you! I will look into this. I just figured for some reason...I would have some data left from cyanogenmod, if that makes sense. In other words, i want my phone to be as fresh as possible. I only ask this because when I had CM, i accidentally made a backup of it through rom manager (or clockwork) and I am not sure if its in my partition somewhere.
TIL that OTA arent as fast. Ill download KIES and give it a try.
Click to expand...
Click to collapse
Factory resetting with stock recovery installed wipes all data except the external sdcard. I am so sorry I should've mentioned this before. I was thinking you had already done one at some point and didn't have anything left to worry about. Still, I should have asked and I do apologize for that. Hopefully if it was really important it was saved to the external sdcard....
david12795 said:
Just installed KIES and it said my phone has the latest firmware?
Click to expand...
Click to collapse
Ok, I wasn't sure about that. I personally never need or use kies so I didn't know if it was tied to the staged rollouts. It would appear that it is though.
Give me a few min and ill post links to the threads where you can download the ota or update via a different method.
---------- Post added at 03:56 AM ---------- Previous post was at 03:40 AM ----------
UCUEMJB to UCUFNE4 firmware update - thread by enewman17
http://forum.xda-developers.com/showthread.php?t=2808654.
How to update SGH-I747 yo UCUFNE4_4.4.2 - thread by enewman17
http://forum.xda-developers.com/showthread.php?t=2789917
[Download] AT&T Kitkat OTA file - thread by bkong
http://forum.xda-developers.com/showthread.php?t=2788012
I suggest trying the third one by bkong first. He posted a pure OTA file you can try to update with.
The first option is a recovery flashable firmware, but does not include the /system (ROM) portion. To fully update using this you'll flash the firmware per his instructions and then go to his development thread for the stock rom. It is here: http://forum.xda-developers.com/showthread.php?t=2788357
The second option is the OTA file, but it has been slightly modified to skip certain file checks. If the original OTA doesnt work, theres a good chance this will. (Since you are full stock now either one should flash without issue).
Hope those help! I recommend doing a bit of reading about each one (at least the OP and last few pages) and start with whichever you are most comfortable with.
Or, you could always use that most valuable tool, patience, and wait for the OTA to roll out for your area.
Good luck!
DocHoliday77 said:
Factory resetting with stock recovery installed wipes all data except the external sdcard. I am so sorry I should've mentioned this before. I was thinking you had already done one at some point and didn't have anything left to worry about. Still, I should have asked and I do apologize for that. Hopefully if it was really important it was saved to the external sdcard....
Ok, I wasn't sure about that. I personally never need or use kies so I didn't know if it was tied to the staged rollouts. It would appear that it is though.
Give me a few min and ill post links to the threads where you can download the ota or update via a different method.
---------- Post added at 03:56 AM ---------- Previous post was at 03:40 AM ----------
UCUEMJB to UCUFNE4 firmware update - thread by enewman17
http://forum.xda-developers.com/showthread.php?t=2808654.
How to update SGH-I747 yo UCUFNE4_4.4.2 - thread by enewman17
http://forum.xda-developers.com/showthread.php?t=2789917
[Download] AT&T Kitkat OTA file - thread by bkong
http://forum.xda-developers.com/showthread.php?t=2788012
I suggest trying the third one by bkong first. He posted a pure OTA file you can try to update with.
The first option is a recovery flashable firmware, but does not include the /system (ROM) portion. To fully update using this you'll flash the firmware per his instructions and then go to his development thread for the stock rom. It is here: http://forum.xda-developers.com/showthread.php?t=2788357
The second option is the OTA file, but it has been slightly modified to skip certain file checks. If the original OTA doesnt work, theres a good chance this will. (Since you are full stock now either one should flash without issue).
Hope those help! I recommend doing a bit of reading about each one (at least the OP and last few pages) and start with whichever you are most comfortable with.
Or, you could always use that most valuable tool, patience, and wait for the OTA to roll out for your area.
Good luck!
Click to expand...
Click to collapse
No no! Its fine, I wasnt planning using it or anything, I just wanted to get rid of it since I have no use for it, no need to apologize. , I was fully aware that I would lose all files, other than SD ext drive. I just wanted to make sure that all files are in the right place and none of the unnecessary files are taking up space (e.g. files from cyanogenmod)
As for the update, I talked to a samsung representative and they said one can go to Best Buy and get it updated there through a technician, so Ill try that later since I am close to it ATM. If it back fires, Ill try your suggestions.
I really do appreciate for the help , I have been completely lost for days but it turns out I was just using the wrong firmware. Thanks for pointing it out. Good karma is coming your way . Hopefully one day, I will be here again and trying out a new custom firmware.
Glad I could help!
If I remember right, someone who mentioned the best buy thing had said at the time that the first store they went to did not have the update yet. But I think they found another in their area did. So if they say its up to date and cant help, you might find another store close by can. (If there is one of course!)
Just fyi so you're not too surprised if that happens.
DocHoliday77 said:
Glad I could help!
If I remember right, someone who mentioned the best buy thing had said at the time that the first store they went to did not have the update yet. But I think they found another in their area did. So if they say its up to date and cant help, you might find another store close by can. (If there is one of course!)
Just fyi so you're not too surprised if that happens.
Click to expand...
Click to collapse
Ill hope for the best and prepare for the worst.
Of course, if the worst happens, I can just use one of your links you mentioned. :good::good:
Hey guys,
I'm kinda new to the HTC/Android world, found this community a damn good place to find support.. But now I've hit a road block.
Basically, I've been eager to root from day 1 of getting my first htc handset, I came across from jailbreak and loved the fact of customizability with Android.
So I had the Google play edition(I think, all geared towards Google) running Kit Kat 4.4.4. Love it, big Google user so this all tied together lovely.
Here is the Situation.
I found a video on youtube, cannot provide URL as I'm in work at the moment, but it was root guide from scratch. Fresh windows OS, seemingly a phone fresh out the box.. you get the idea.
I used the Hasoon2000 tool to root the device. Installed ADB etc on my pc, signed up as a a dev, got the Key for device, sent in and received my .bin file. I got up to actually rooting my device, well pleased and happy. Using TWRP via Hasoon2000.
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Queried this on another forum, decided to continue to be patient... but no replies, in the mean time I restored my apps and have a fiddle, see what the root function can do for myself.
I installed "Freedom 1.0.6" and a program called "Market Share"- Hate iAP, some games are ridiculously priced for the smallest of things, I just wanted to sandbox plague inc. ;(
Now the device is stuck in a boot loop, phone starts up, see the home screen for a bout 40 seconds/ one minute.. Some times I unlock the device and it goes back to flash screen then.. others I boot an app and its slides away once more.
This happened close to 15x before I left for work this morning and I imagine its just going to repeat this and run the battery - I tried to stop this loop by going into TWRP and possibly choosing to boot system this way may of stopped it.. but when I was on the boot screen with those options.. It said Tampered at top of screen and S-On- which has scared me quite a bit..
What the hell has happened!?
I'm desperate to know and don't want to have this damn thing bricked! Please help.. try explain like I'm 5, as said I'm new to a lot of this! >.<
first off, if the screen comes on, its not bricked.
esenfur said:
But here is where **** hits the fan.
The device needed to update, It took me back to 4.4.2 but Im unsure on how to get back to most up to date OS and keep the root.
But when I reboot to install this, it goes into TWRP. no other way around this.
Click to expand...
Click to collapse
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.
redpoint73 said:
first off, if the screen comes on, its not bricked.
Do you mean you accepted an official OTA? I think that is what you are saying. You should not be accepting OTAs on a phone that has been bootloader unlocked, custom recovery, etc. unless you know exactly what you are doing and what the result will be (which is clearly not the case).
Stock recovery is needed to install an OTA. That is why it keeps going to TWRP, then it doesn't find stock recovery and reboots, hence the loop you are stuck in. Try to find the OTA file and delete it.
Click to expand...
Click to collapse
Thank you for fast response.
Official OTA - being that the phone its self said "Update the OS" - I just accepted this, hit download and began install as a reboot- didnt spot implications. As said, noob, followed a tut. If it highlighted DO NOT UPDATE or.. IF U WANT UPDATE NOW FOLLOW THIS- Great, but nothing of the sort?
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Or do you have any links to tutorials I could possibly follow?
Side note- when this loop started I deleted
esenfur said:
Or do you have any links to tutorials I could possibly follow?
Click to expand...
Click to collapse
This is really your main issue. By following a YouTube video and using a Toolkit, you've failed to actually learn anything or gain any real understanding or knowledge. Do yourself a favor and ditch the tutorials and videos (and toolkit for that matter) and do it the old fashioned way . . . by reading. Videos and step-by-step guides do you no good when things go south (as you've now discovered). And with the prior proper knowledge (usually not gained by following tutorials) this whole mess probably would have never happened in the first place.
A cardinal rule of Android phone modding: DO NOT accept/download/install OTAs (official OS updates) on a modded device unless you know what you are doing, and what the result will be. If in any doubt, simply DO NOT do it.
esenfur said:
Is the OTA file basically the .exe for the OS- so find it and delete it.. although I dont have enough time to navigate and establish where the file actually is located!
Click to expand...
Click to collapse
.exe file is Windows specific. You are looking for a zip file, and it typically starts with "OTA". Don't remember where its saved to, so you will have to search for it. If you can't keep the phone running long enough to do so, mount the memory on your computer and search that way.
Deleting the OTA file worked for me on a past device, although one M8 user in the same position said deleting the file didn't get him out of the loop. Flashing your ROM again, or wiping the internal memory (backup any important personal data first) might be options for you.
redpoint73 said:
you've failed to actually learn anything or gain any real understanding or knowledge.
Click to expand...
Click to collapse
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
redpoint73 said:
Videos and step-by-step guides do you no good when things go south (as you've now discovered).
Click to expand...
Click to collapse
agreed.. theres FAR much more I need to learn.. its scary haha.
redpoint73 said:
DO NOT accept/download/install OTAs (official OS updates)
Click to expand...
Click to collapse
taken on board. I know with my jailbreaks in past it has been a pain, assumed Android would be alot more stable to over write- due to functionality of OS and unlocked features.
I was being generic when I said .exe- basically the installer..
I returned from work to see phone stopped looping.. i could stop the install and deleted the file ASAP.. but now what.. Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?
I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.
Try to re-flash the ROM, with stok ROM, using TWRP and clean install. It should work.
hack14u said:
I am confused to what you are trying to accomplish at this point, is it to install a OTA, or a recovery? What exactly is going down here?
Me personally to take an OTA is to relock bootloader, install stock recovery, and make sure CID matches. I am S-Off so bootloader means very little, but you can unlock and relock at will when you are S-Off. You will not lose S-Off accepting an OTA.
Click to expand...
Click to collapse
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
First of all once the bootloader is unlocked you don't have to relock it to get OTA.
As I undersand you have done the following:
1) Unlock using HTCDev-Method
2) flashed a custom revocery (TWRP in your case)
3) flashed a supersu too!?
To install the OTA means loosing root acces. Thus you have to re-root it after the OTA is done. The other problem ist that STOCK OTAs don't work with a custom recovery. Meaning you would have to flash a stock recovery first, install the OTA second (as long as you didn't change anything an just root), and re-root third.
Let's have a look which stock recovery you would need:
1) reboot to bootloader
2) connect the phone to you PC and open cmd in you adb/fastboot folder
3) enter "fastboot getvar all"
4) paste this information here (but DELETE the IMEI and SERIAL NUMBER before posting!!)
As soon as we know which stock recovery you need we will go on.
esenfur said:
Ive seen quite a fair few ratings for Hasoon2000 and decided to go with it..
Click to expand...
Click to collapse
I'm not saying there is anything "wrong" with the toolkit, per se. For the most part, it does what its intended to do.
But it also shortcuts the learning process, and facilitates folks rooting the phone without gaining the proper knowledge. This is a dangerous thing.
This is just my opinion. But I strongly believe it. If you can't accomplish these things without a toolkit, you shouldn't be rooting your phone in the first place.
Others use the toolkits, and love them. They are more than entitled to have their own opinion. But when things go south, the toolkits aren't going to help; and those folks don't have the proper knowledge and they come running here. So you tell me what is the "best" way to root the phone?
esenfur said:
I was being generic when I said .exe- basically the installer..
Click to expand...
Click to collapse
I already figured this was probably the case. But I found it better to provide the exact information on what file to delete; rather than leaving it open to the possibility of you and/or others being misinformed.
esenfur said:
Phone is still bugging me to update, lost the root(got a checker).. so whats the correct procedure!?
Click to expand...
Click to collapse
Sounds like you still have TWRP installed, so just flash SU or SuperSU to gain root.
After that, you can use Titanium Backup or similar app to find the update process and freeze it, to stop the update notifications.
Don't remember the exact process (this is where searching and reading comes in for you) but its something like "drm..." or "updater".
I have this situation before,what i do is find the right stock recovery and flash..after ota done flash back custom recovery..?
esenfur said:
I am trying to update the phone, root and then some..
What file am I looking for and how do I flash a ROM on a M8
Click to expand...
Click to collapse
At this point after seeing this, I would suggest you take some time and start reading. All of your answers are here in the forums. Knowledge is power and within the pages of this site you will find everything you need.
To take the OTA find a stock recovery, to flash ROM's find the one you like and flash via your favorite recovery.
Hello,
I have recently entered the world of Xiaomi after a history with Sony Devices (Xperia, Xperia SP, Xperia Z3). I'm so far delighted with the Mi 10T Lite, it's feature rich and blazingly fast. However, I miss one feature I had installed on my SP and Z3 that made their batteries live extra long. It's this:
Battery Charge Limit [ROOT] - Apps on Google Play
Stop charging at desired level to preserve battery health for most devices!
play.google.com
With this tool, you can essentially leave your device permanently on the charger and it will stay within the limits you have set. I used to have it set to 71-80%. So when the charge dropped to 70% it started charging, until reaching 80%. I therefore balanced keeping the battery charged for short intervals and at a sweet spot for its health, with having enough charge in case I wanted to grab my phone and leave the house. I really love this app.
The problem is, it requires root privileges.
I understand that rooting my Xiaomi is not particularly hard, but since it is a new device I would not want to void its warranty. It's possible that some defect shows up and I am left without a warranty. It would be a particularly big bummer if I discovered I rooted the device only to see that the app does not work properly with it.
So, could someone with a rooted device try out this fantastic app and let me know if it works? You might end up with a battery life extender you never knew existed!
Many thanks,
Yanni
Athens/Greece
Friendly bump! Could somebody try this nifty app for battery life optimization on their rooted 10T Lite? Let me know if it works so I can go ahead with arcane rooting magick, hehe.
I have been using it for the last two years. It is a great app.
It does work fine on the mi10t lite, you just need to change the control file from default to "input_suspend" pixel2/xiaomi mi6. After that the limit is respected. Another alternative is a magisk muddle called "Advanced Charging Controller" it is more technical than bcl.
egor27 said:
I have been using it for the last two years. It is a great app.
It does work fine on the mi10t lite, you just need to change the control file from default to "input_suspend" pixel2/xiaomi mi6. After that the limit is respected. Another alternative is a magisk muddle called "Advanced Charging Controller" it is more technical than bcl.
Click to expand...
Click to collapse
Thank you! Both for the confirmation and also the control file's location.
I think I'll be rooting my device, using magisk. Briefly browsing a couple of guides, I guess it won't be very involved. Besides voiding warranty I'll be losing OTA firmware updates. I presume I will have the option to manually updating by flashing a new official ROM.
funkyjester said:
Thank you! Both for the confirmation and also the control file's location.
I think I'll be rooting my device, using magisk. Briefly browsing a couple of guides, I guess it won't be very involved. Besides voiding warranty I'll be losing OTA firmware updates. I presume I will have the option to manually updating by flashing a new official ROM.
Click to expand...
Click to collapse
Just FYI - you should not void the warranty (at least in Europe - https://www.piana.eu/root/) and OTA updates will arrive normally. You will need to restore stock boot image from Magisk manager before installing OTA and then re-root the phone afterwards, but that's the only complication.
_mysiak_ said:
Just FYI - you should not void the warranty (at least in Europe - https://www.piana.eu/root/) and OTA updates will arrive normally. You will need to restore stock boot image from Magisk manager before installing OTA and then re-root the phone afterwards, but that's the only complication.
Click to expand...
Click to collapse
Thanks for the link. Besides the EU statutory warranty, a quick search reveals that the company itself allows rooting without voiding your warranty. So I'm a happy camper I guess.
Guys, please, if anyone can upload the .xqcn file generated by the backup in QPST, thank you. It has to be a Mi10T Lite Global or EEA.
Hemerson Silva said:
Guys, please, if anyone can upload the .xqcn file generated by the backup in QPST, thank you. It has to be a Mi10T Lite Global or EEA.
Click to expand...
Click to collapse
You do not need to ask in every unrelated topic. I guess that no one has the file and/or no one wants to share his IMEI publicly.
_mysiak_ said:
You do not need to ask in every unrelated topic. I guess that no one has the file and/or no one wants to share his IMEI publicly.
Click to expand...
Click to collapse
In fact, there is the issue of IMEI. I wanted the file to go through my device and see how it would behave, taking the risks. Unfortunately the XDA community was once more collaborative.
Hemerson Silva said:
In fact, there is the issue of IMEI. I wanted the file to go through my device and see how it would behave, taking the risks. Unfortunately the XDA community was once more collaborative.
Click to expand...
Click to collapse
Maybe if you provide step by step guide how to extract xqcn file and remove sensitive information from it before uploading to the internet, someone will be willing to do it.
In each case, we are heavily offtopic here.
Hello, I thought of hijacking my own thread again.
After painfully waiting for a week (go Xiaomi!), I unlocked my bootloader, and got an instant factory reset with all my data gone (again, go Xiaomi! I didn't expect that).
But now all is unlocked and I am left with the task of rooting my device. I think I 'll use Magisk. From what I understand I need a boot.img file to patch and then flash. Thinking I 'd like to keep my current ROM, I looked around for a full ROM image to get the boot.img file. But I couldn't find it.
My current ROM is MIUI Global 12.0.5.0 (QJSEUVF), which like I said, I could not find anywhere. It must be an early 12.0.5 ROM used on the first phones shipped. I have two questions:
a) Is it possible to somehow extract the boot.img file from the running phone?
b) If not, and if I can't find the installed ROM zip, what ROM zip would you pick to stay as close as possible to the one I have now? The reason I want this is that the phone works pretty damn fine up to now, and I see reports of problems after major upgrades, like version 12.5.
Any info much appreciated!
Best Wishes,
Yanni
Athens/Greece
funkyjester said:
Hello, I thought of hijacking my own thread again.
After painfully waiting for a week (go Xiaomi!), I unlocked my bootloader, and got an instant factory reset with all my data gone (again, go Xiaomi! I didn't expect that).
But now all is unlocked and I am left with the task of rooting my device. I think I 'll use Magisk. From what I understand I need a boot.img file to patch and then flash. Thinking I 'd like to keep my current ROM, I looked around for a full ROM image to get the boot.img file. But I couldn't find it.
My current ROM is MIUI Global 12.0.5.0 (QJSEUVF), which like I said, I could not find anywhere. It must be an early 12.0.5 ROM used on the first phones shipped. I have two questions:
a) Is it possible to somehow extract the boot.img file from the running phone?
b) If not, and if I can't find the installed ROM zip, what ROM zip would you pick to stay as close as possible to the one I have now? The reason I want this is that the phone works pretty damn fine up to now, and I see reports of problems after major upgrades, like version 12.5.
Any info much appreciated!
Best Wishes,
Yanni
Athens/Greece
Click to expand...
Click to collapse
Bootloader unlocking always results in a factory reset (unless vendor seriously screwed up), it's standard security feature of Android since..like pretty much forever.
If you do not have boot.img at hand, the most easy solution is probably to hot boot TWRP ("fastboot boot twrp.img") and flash Magisk from there. Also it might be a good idea to reflash your phone with normal global version which is already available for download, QJSEUVF sounds like Vodafone version, I would certainly get rid of it and replace it with QJSEUXM.
_mysiak_ said:
Bootloader unlocking always results in a factory reset (unless vendor seriously screwed up), it's standard security feature of Android since..like pretty much forever.
If you do not have boot.img at hand, the most easy solution is probably to hot boot TWRP ("fastboot boot twrp.img") and flash Magisk from there. Also it might be a good idea to reflash your phone with normal global version which is already available for download, QJSEUVF sounds like Vodafone version, I would certainly get rid of it and replace it with QJSEUXM.
Click to expand...
Click to collapse
I should have figured out what VF means. I think I will take the straightforward way and use QJSEUXM which I have found readily available. Thanks!