I have tried and tried several solutions all over the place to update. Nothing is working or maybe I am not understanding any of it. PLease please please someone help me with step by step process of updating the phone without having to unroot and root. It was days of efforts for me to get it rooted. would hate to go through that again. I am a rookie at this, so please bear with me if I am not able to understand some super techy words.
here's what I have:
One S from t-mobile.
Rooted. Have TWRP and SuperSu. Also have Titanium Backup Pro (set to backup weekly).
I think I am on stock ROM (how do I check that?)- unsure.
From the "about" phone:
software information:
Android version: 4.0.4
HTC sense version: 4.1
Software number: 2.35.531.7 710RD
HTC SDK API level: 4.23
HTC extension version: HtcExtension_403_1_GA_20
Kernel version: 3.08-01583-ge547c5e
[email protected]#1
SMP preempt
I get notifications (annoying) every few minutes to update to:
System Update 2.35.531.12
axast said:
I have tried and tried several solutions all over the place to update. Nothing is working or maybe I am not understanding any of it. PLease please please someone help me with step by step process of updating the phone without having to unroot and root. It was days of efforts for me to get it rooted. would hate to go through that again. I am a rookie at this, so please bear with me if I am not able to understand some super techy words.
here's what I have:
One S from t-mobile.
Rooted. Have TWRP and SuperSu. Also have Titanium Backup Pro (set to backup weekly).
I think I am on stock ROM (how do I check that?)- unsure.
From the "about" phone:
software information:
Android version: 4.0.4
HTC sense version: 4.1
Software number: 2.35.531.7 710RD
HTC SDK API level: 4.23
HTC extension version: HtcExtension_403_1_GA_20
Kernel version: 3.08-01583-ge547c5e
[email protected]#1
SMP preempt
I get notifications (annoying) every few minutes to update to:
System Update 2.35.531.12
Click to expand...
Click to collapse
You need to have stock recovery to flash the ota update and it shouldn't remove root.
Darknites said:
You need to have stock recovery to flash the ota update and it shouldn't remove root.
Click to expand...
Click to collapse
Pardon me for my ignorance. But...
1. How do I get stock recovery?
2. what next, lets say I get stock recovery. Do I run the OTA update? and then.... do you mind laying out some steps for me please. TIA.
Here for stock recovery, http://www.mediafire.com/view/?d8velqlrjor0wx9. Flash it with the all in one toolkit. Get update and let it update for you.
Hey man if u need some help holla my way I can walk you through it you want it rooted w/ a custom ROM its just better that way
Sent from my One S using xda premium
Not getting it still.
This is what i did.
1. I have phone connected to laptop. USB debugging on. on Data mode (as opposed to charge only).
2. downloaded stock recovery from the link specified above. it is called recovery.img. I have it on my computer's c drive. Also transferred it to phone's download directory. wasn't sure where i store it.
3. downloaded all in one kit on my pc.
4. clicked on "your own recovery". The phone went to bootloader mode. Meanwhile, my pc came up with a dialog box for me to pick recovery. i chose the recovery from my c: drive (phone was not even an option to pick from). it keeps asking to burn recovery.img to D drive (my dvd). no other option for me to chose. doesn't matter what i hit - burn or cancel. it keeps asking me the same thing.
something is not right.
Search for 'fastboot flash recovery recovery_signed.img' then...
i am extremely new to the rom/flashing/rooting scene. i recently used a "back door" rooting process, which worked great and i did all the recomended actions and apps: supersu titanium backup, root browser, etc. then i wanted to change my boot animation->samsung device-> flash a zip file to allow bootanimation.zip->samsung requires signature verification from stock recovery mode->cwm recovery(which flashes itself to the phone... curious why a custom recovery...or any recovery for that matter is even required if it isnt necessary...) -> recovery menu no longer accesible. i cant flash anything to my phone i tried changing the recovery to twrp but no dice. its giving me this dialog along with caution sign:"system software not authorized by verizon wireless has been found on your phone...etc" the phone is a samsung galaxy legend on verizon prepaid plan it is the jasper version of the samsung galaxy stellar. now for the question... What do i do so that i can flash files to my device?
i dont know much about unlocking the bootloader except that doing so with the wrong program will brick your phone and since im doing this recreationally on my primary phone i dont want to buy a new one. how can i regain access to my recovery menu/ unlock my bootloader?
its not a popular phone so i doubt anyone is going to be able to offer a one touch application to unlock the bootloader but any information would be helpful.if youre still reading this i thank you for any advice and i apologize if i : posted in the wrong section, offended anyone, or came off as a cheap experience-less n00b
EDIT: my phone is running 4.1.2 jellybean, baseband:i200ppvramh1, kernel: 3.0.31, build: jzo54k.i200ppvramh1, dont know if that will help any and before anyone criticizes me remember i am completely new to this forum posting thing but i guarentee i have scrounged this site the world over trying to get help but there just seems to be noone working on this problem the same as me...
So...
I'm coming from a Fascinate running CM10. Pretty easy install, etc. etc.
Finally got some info from the S3 I'm restoring, and trolling around trying to find info (or finding too much).
This is what I have:
Android Version - 4.3
Baseband version - I535VRUCML1
Kernel Version - 3.0.31
Build - JSSI5J.I535VRUCML1
So I'm basically looking for the RTFM replies.
How do I find if the the bootloader is locked (I have been able to avoid installing ADB on my PC, but would have no troubles running basic linux command line stuff)?
I think I can install either TWRP or CWM, because it doesn't actually touch the bootloader, correct?
Can I install any ROM (I have read threads that I can install any "4.3 compatible ROM")? Is that all I need to look for?
What is the purpose of "safestrap" ? is it needed, and why (didn't need this on the Fascinate).
I am familiar with ODIN, and used CWM to install CM10, but with all the warning about "YOU WILL BRICK YOUR PHONE" have got me to a point of such confusion, I feel like a deer stuck in the headlights (or even worse, a Q-Beam).
Thanks in advance for any RTFM replies.
Eric
ejaf said:
So...
I'm coming from a Fascinate running CM10. Pretty easy install, etc. etc.
Finally got some info from the S3 I'm restoring, and trolling around trying to find info (or finding too much).
This is what I have:
Android Version - 4.3
Baseband version - I535VRUCML1
Kernel Version - 3.0.31
Build - JSSI5J.I535VRUCML1
So I'm basically looking for the RTFM replies.
How do I find if the the bootloader is locked (I have been able to avoid installing ADB on my PC, but would have no troubles running basic linux command line stuff)?
I think I can install either TWRP or CWM, because it doesn't actually touch the bootloader, correct?
Can I install any ROM (I have read threads that I can install any "4.3 compatible ROM")? Is that all I need to look for?
What is the purpose of "safestrap" ? is it needed, and why (didn't need this on the Fascinate).
I am familiar with ODIN, and used CWM to install CM10, but with all the warning about "YOU WILL BRICK YOUR PHONE" have got me to a point of such confusion, I feel like a deer stuck in the headlights (or even worse, a Q-Beam).
Thanks in advance for any RTFM replies.
Eric
Click to expand...
Click to collapse
You ain't in Kansas anymore.
your bootloader is locked. your stuck with safestrap and roms compatible with a locked bootloader
ejaf said:
So...
I'm coming from a Fascinate running CM10. Pretty easy install, etc. etc.
Finally got some info from the S3 I'm restoring, and trolling around trying to find info (or finding too much).
This is what I have:
Android Version - 4.3
Baseband version - I535VRUCML1
Kernel Version - 3.0.31
Build - JSSI5J.I535VRUCML1
So I'm basically looking for the RTFM replies.
How do I find if the the bootloader is locked (I have been able to avoid installing ADB on my PC, but would have no troubles running basic linux command line stuff)?
I think I can install either TWRP or CWM, because it doesn't actually touch the bootloader, correct?
Can I install any ROM (I have read threads that I can install any "4.3 compatible ROM")? Is that all I need to look for?
What is the purpose of "safestrap" ? is it needed, and why (didn't need this on the Fascinate).
I am familiar with ODIN, and used CWM to install CM10, but with all the warning about "YOU WILL BRICK YOUR PHONE" have got me to a point of such confusion, I feel like a deer stuck in the headlights (or even worse, a Q-Beam).
Thanks in advance for any RTFM replies.
Eric
Click to expand...
Click to collapse
To add to the above, no you cannot install TWRP or CWM. You didn't need safestrap on the Fascinate because the bootloader was unlocked on it. You need to read this thread and the links that are contained in the OP of the thread to get your answers:
http://forum.xda-developers.com/showthread.php?t=2639337
Thanks...I would have expected that sticky thread to be in this forum...hadn't even started searching the dev forums yet.
I'll read up on safestrap...sounds as if it allows other ROMS to run on a locked bootloader.
No, I am definitely not in Kansas anymore. Can I click my heels together three times, and have CM11 running :silly:
Eric
Welcome to my stock rooted ROM thread!
These ROMs are built from either the official HTC RUUs posted here, or stock boot & system backups posted in the forum.
Code:
[CENTER][SIZE="3"]*** DISCLAIMER ***
Anything you flash from this thread is done AT YOUR OWN RISK!!
I will not be held responsible if something from this thread breaks your device![/SIZE][/CENTER]
Now that that's out of the way, here are the details:
ROM Features:
- Recovery-Flashable (TWRP Recommended)
- Rooted (SuperSU 2.65)
- Forced encryption disabled
- dm-verity disabled
Instructions:
- Unlock Bootloader
- Flash TWRP
- Format Data in TWRP to remove encryption (Wipe -> Format Data -> type "yes")
- Reboot Recovery
- Copy ROM of your choice to device over USB
- Flash ROM zip
- Reboot device (device will reboot once automatically at the beginning of the boot animation to install SuperSU)
- Profit!
IMPORTANT NOTES:
- You cannot use the external SD card as internal storage, because that would require dm-verity to be enabled, which isn't possible on a custom ROM.
Available ROMs:
Unlocked/Developer Edition (GSM compatible):
1.57.617.20 Dev Edition - Android 6.0.1 - thanks @Wonders_Never_Cease
1.55.617.4 Dev Edition - Android 6.0.1 | Mirror (BasketBuild) - thanks @Frago for posting the stock images
1.12.617.6 Dev Edition - Android 6.0 | Mirror (BasketBuild)
Carrier-specific versions:
AT&T
1.57.502.20 AT&T - Android 6.0.1 - thanks @Wonders_Never_Cease
1.27.502.5 AT&T - Android 6.0 | Mirror (BasketBuild)
Sprint
1.60.651.4 Sprint - Android 6.0.1 (thanks @holofractal)
1.57.651.1 Sprint - Android 6.0.1 (thanks @holofractal)
1.10.651.1 Sprint - Android 6.0 | Mirror (BasketBuild) - thanks @entrpn for posting the stock images
All Downloads (includes firmware from RUUs)
Thanks:
@kmdm for unruu , bruutveal & ruuveal for RUU extraction and decryption
@nkk71 for his help with RUU decryption
@SuperR. for SuperR's Kitchen, which is how all the ROMs were built
XDA:DevDB Information
A9 Base ROMs, ROM for the HTC One A9
Contributors
Captain_Throwback
ROM OS Version: 6.0.x Marshmallow
ROM Kernel: Linux 3.10.x
Based On: Sense
Version Information
Status: Stable
Created 2015-12-30
Last Updated 2016-06-25
First
Congratulations, Nice job :good::good:
Stupid question probably, is this for Sprint only or will my att unlocked work with this ?
lsun06 said:
Stupid question probably, is this for Sprint only or will my att unlocked work with this ?
Click to expand...
Click to collapse
Is what for Sprint only? There are two ROMs.
Sprint Edition is for Sprint (obviously). Dev Edition is for GSM. There's also an AT&T RUU on the HTC site, but I haven't downloaded it. Hopefully someone else can do that and build their own ROM (one of the points of this thread).
That's what I needed to know. I still can't get it to go bast first boot image. It reboots after 6-10 seconds then never comes back on. I'm unlocked, supercid, on 1.12.617.6. Followed directions about wipe and format, flashed. Still nothing. I'll backup and punt for now. I tried numerous times.
My bad, just realized there is a deodexed version. Works great!
I've the same issue as Isun06.
Tryed the HIAE_DEV_EDITION_1.55.617.4_ROOTED_CPTB-deodex.zip and also HIAE_DEV_EDITION_1.55.617.4_ROOTED_CPTB-odex.zip on a European model (2PQ910000). It's S-Off and bootloader unlocked, Super-CID. MID changed to 2PQ912000.
I followed also the directions, but unfortunately it didn't work. I restored my backup which is working.
lsun06 said:
That's what I needed to know. I still can't get it to go bast first boot image. It reboots after 6-10 seconds then never comes back on. I'm unlocked, supercid, on 1.12.617.6. Followed directions about wipe and format, flashed. Still nothing. I'll backup and punt for now. I tried numerous times.
Click to expand...
Click to collapse
SpeziesTR said:
I've the same issue as Isun06.
Tryed the HIAE_DEV_EDITION_1.55.617.4_ROOTED_CPTB-deodex.zip and also HIAE_DEV_EDITION_1.55.617.4_ROOTED_CPTB-odex.zip on a European model (2PQ910000). It's S-Off and bootloader unlocked, Super-CID. MID changed to 2PQ912000.
I followed also the directions, but unfortunately it didn't work. I restored my backup which is working.
Click to expand...
Click to collapse
my previous reply, was luckily deleted, by me fortunately pressing f5,
"it didn't work", "it doesnt work", are not the most useful of statements, so 2 choices
start logging, from the recovery flash, the kmsg/ramoops (whatever this device uses), etc
you should also include what firmware you are running and so on and so forth,
seriously, people, the OP just released this a few hours ago, and he get's, yet another "it doesnt work" post?? -__-
what device do you have (specific, not vague)
getvar all (excluding IMEI, MEID, serial number)
what firmware are you running
has the ROM flashed properly in recovery
is the kernel in place
logcat, kmsg, etc
etc
if YOU want to help, i'm sure it would be appreciated, but the OP need specifics and exact details
I'm not trying to be one of those people, just simply stating I can't seem to get past the first boot . It reboots and is dead. I stated I'm on a fresh install of the dev unlocked 1.12.617.6. I went through the wipe format etc. I supercid. Mid is same as 2PQ912000.
In recovery it said completed and no issues. I'm sure its me. I was just stating I can't seem to move past that first boot.
Thank you for the work, I do appreciate the folks that work on these. Without you this site would be useless and, frankly, I would have stayed w apple years and years ago.
lsun06 said:
I'm not trying to be one of those people, just simply stating I can't seem to get past the first boot . It reboots and is dead. I stated I'm on a fresh install of the dev unlocked 1.12.617.6. I went through the wipe format etc. I supercid. Mid is same as 2PQ912000.
In recovery it said completed and no issues. I'm sure its me. I was just stating I can't seem to move past that first boot.
Thank you for the work, I do appreciate the folks that work on these. Without you this site would be useless and, frankly, I would have stayed w apple years and years ago.
Click to expand...
Click to collapse
Have you tried installing the 6.0.1 Dev Edition firmware to see if that helps? Typically the ROM and firmware should correspond.
I flashed the img from the other topic that listed the convert from what I'm on now to the 6.0.1. I'm assuming it was the img as it stated it was to be flashed after the ROM backup. The 2PQxxx img. I'm assuming it's the firmware ? This phone is a different animal from the m8 and back. I've done numerous HTC phones and this one is confusing the hell out of me. It's my fault. Not yours.
lsun06 said:
I flashed the img from the other topic that listed the convert from what I'm on now to the 6.0.1. I'm assuming it was the img as it stated it was to be flashed after the ROM backup. The 2PQxxx img. I'm assuming it's the firmware ? This phone is a different animal from the m8 and back. I've done numerous HTC phones and this one is confusing the hell out of me. It's my fault. Not yours.
Click to expand...
Click to collapse
fastboot getvar all from Download mode might help us see what situation your device is currently in. It sounds like you need to RUU and start over, tbh. A clean slate always helps.
You also need to be more specific with the information you provide. You're referring to vague files, so without knowing exactly what you flashed, it's difficult to help.
To be fair, the purpose of this topic is not to help people figure out why they can't flash a ROM; I already know the ROMs work. This is a Development thread to aggregate the stock rooted bases. As such, the spurious discussion really belongs in Q&A.
Is there anyway you could make a debloated version? Not trying to push it as I greatly appreciate your work done here!
@Captain_Throwback
Thank you for sharing your work.
I read the thread about rooting the A9 but it seems not all devices can be rooted (I am not sure), so I asked the OP there and waiting for his reply.
The one I have is 16GB/2GB model with Build number: 1.27.401.5 CL656287 release-keys, so would the method you mentioned work?
I also have another question but it is off topic, it is regarding the 2GB vs 3GB variants, where can I ask you regarding that? As someone was trying to help me and he told me that you can help.
Thank you so much
Sent from my HTC One A9 using Tapatalk
tharwatq said:
@Captain_Throwback
Thank you for sharing your work.
I read the thread about rooting the A9 but it seems not all devices can be rooted (I am not sure), so I asked the OP there and waiting for his reply.
The one I have is 16GB/2GB model with Build number: 1.27.401.5 CL656287 release-keys, so would the method you mentioned work?
I also have another question but it is off topic, it is regarding the 2GB vs 3GB variants, where can I ask you regarding that? As someone was trying to help me and he told me that you can help.
Thank you so much
Sent from my HTC One A9 using Tapatalk
Click to expand...
Click to collapse
Your entire post is off-topic for this thread. As I just stated:
The purpose of this topic is not to help people figure out why they can't flash a ROM; I already know the ROMs work. This is a Development thread to aggregate the stock rooted bases. As such, the spurious discussion really belongs in Q&A.
Click to expand...
Click to collapse
I don't know what the "method you mentioned" refers to, but I do know that the FAQ in the TWRP thread answers several root questions. The root method in @jcase's Root thread is largely deprecated with the advent of @Chainfire's latest Beta zips, which automatically patch the boot image. It seems to me that you're making it more complicated than necessary.
And all questions belong in the Q&A forum. If you have a question that you need my feedback on, just mention me and I'll see it.
Now please, let's get this thread back on topic.
I'm going to also upload the firmware extracted from these RUUs to the Downloads tab of the DevDB project. That may help with some of the compatibility issues people are having with the ROMs. Note, however, that the firmware is for people with S-OFF ONLY, and you may need to add your MID and/or CID to the android-info.txt included in the zip for it to flash on your variant. Before you do that, MAKE SURE THE FIRMWARE YOU'RE FLASHING IS FULLY COMPATIBLE WITH YOUR VARIANT!!!! That means - don't flash GSM firmware on your CDMA device and vice versa - the radios are incompatible and will undoubtedly break data for you.
I'm uploading the AT&T firmware now (from the HTC-posted RUU), as I'm about to build a stock rooted for that and upload.
Captain_Throwback said:
I'm going to also upload the firmware extracted from these RUUs to the Downloads tab of the DevDB project. That may help with some of the compatibility issues people are having with the ROMs. Note, however, that the firmware is for people with S-OFF ONLY, and you may need to add your MID and/or CID to the android-info.txt included in the zip for it to flash on your variant. Before you do that, MAKE SURE THE FIRMWARE YOU'RE FLASHING IS FULLY COMPATIBLE WITH YOUR VARIANT!!!! That means - don't flash GSM firmware on your CDMA device and vice versa - the radios are incompatible and will undoubtedly break data for you.
I'm uploading the AT&T firmware now (from the HTC-posted RUU), as I'm about to build a stock rooted for that and upload.
Click to expand...
Click to collapse
Great to hear you uploading an att version. I'm stock rooted with s-on. I'll gladly be the lab rat for the rom
Sent from my HTC One A9 using Tapatalk
scott8281 said:
Great to hear you uploading an att version. I'm stock rooted with s-on. I'll gladly be the lab rat for the rom
Sent from my HTC One A9 using Tapatalk
Click to expand...
Click to collapse
AT&T version is up.
Captain_Throwback said:
AT&T version is up.
Click to expand...
Click to collapse
Awesome. Downloading now
Sent from my HTC One A9 using Tapatalk
Captain_Throwback said:
AT&T version is up.
Click to expand...
Click to collapse
I can confirm the At&t rom is working fine. I did a clean install and set up everything like new. Runs great.
Sent from my HTC One A9 using Tapatalk
Hey first time posting on xda devs and would like to know how to unlock bootloader, root the phone, and install custom ROM.
Now I have spent entire day backing up and searching the different people root but if someone can help me and point me in the right direction that would be great.
So I have a S3 from ATT Model: SGH-I747, Version: 4.1.2 JellyBean, BaseBand Version: I747UCDMG2, Kernel: 3.0.31 - 1300972. It is a stock ROM, I have never done anything to the phone at all before.
Now I will admit I followed a youtube video call "How to Root AT&T Galaxy S3 SGH-I747!" by High on Android and I did everything in the video. I used odin v1.85, I did the PDA to the CWM.tar file, phone rebooted and I added the CWM superuser file and that is when I tried to get to CWM recovery mode and all I got was the phone's default recovery mode and not the CWM one.
From what I understand I believe I need to unlock bootloader first, but again this is a my first doing this and I hoping someone can point me in the right direction. Forum post state that you should follow guides that is exactly the same to the phone you would like to install custom ROMs.
Honestly I would like to ultimately be able to install a recovery mode that works with my phone that I am able to create snapshot image of my stock phone in case anything happens or I would like to go back to my stock image (which I highly doubt if everything goes fine) and install a custom ROM (I know there are different ROMs if someone can point me to where I can check out all the custom ROMs and not necessarily install those custom ROMs that would be awesome) and finally get rid of ATT loading screen when booting up the phone and install a custom boot loading screen, but of course I care more about getting the custom ROM install first.
If anyone can help that would be great.
Hi
Please use the below link to register a XDA Account first, prior to start posting and replying onto our forums.
Join the Experts
When you complete your registration, I would invite you to post your request in the below forum as our team mates there should be able to help you:
AT&T Galaxy S III Q&A, Help & Troubleshooting
Best regards and good luck.
.
XDA Visitor said:
Hey first time posting on xda devs and would like to know how to unlock bootloader, root the phone, and install custom ROM.
Now I have spent entire day backing up and searching the different people root but if someone can help me and point me in the right direction that would be great.
So I have a S3 from ATT Model: SGH-I747, Version: 4.1.2 JellyBean, BaseBand Version: I747UCDMG2, Kernel: 3.0.31 - 1300972. It is a stock ROM, I have never done anything to the phone at all before.
Now I will admit I followed a youtube video call "How to Root AT&T Galaxy S3 SGH-I747!" by High on Android and I did everything in the video. I used odin v1.85, I did the PDA to the CWM.tar file, phone rebooted and I added the CWM superuser file and that is when I tried to get to CWM recovery mode and all I got was the phone's default recovery mode and not the CWM one.
From what I understand I believe I need to unlock bootloader first, but again this is a my first doing this and I hoping someone can point me in the right direction. Forum post state that you should follow guides that is exactly the same to the phone you would like to install custom ROMs.
Honestly I would like to ultimately be able to install a recovery mode that works with my phone that I am able to create snapshot image of my stock phone in case anything happens or I would like to go back to my stock image (which I highly doubt if everything goes fine) and install a custom ROM (I know there are different ROMs if someone can point me to where I can check out all the custom ROMs and not necessarily install those custom ROMs that would be awesome) and finally get rid of ATT loading screen when booting up the phone and install a custom boot loading screen, but of course I care more about getting the custom ROM install first.
If anyone can help that would be great.
Click to expand...
Click to collapse