Database Info

[Q] Uber noob stuck and scared

So I've been reading these forums for days on end now before I touch my phone again. Is my order of things to do correct? (HTC One XL (AT&T))
1. Root
2. Supercid
3. Unlock bootloader
---Currently here---
4. Install CWM/make a backup
5. Relock bootloader
6. Flash a RUU (1.88?)
7. Unlock bootloader
8. Flash a rom
9. Enjoy
As shown above, I rooted, have su on my screen and I can get into the bootloader by vol down+power. I had a scare trying to install RUU 1.85 but I think it failed because my bootloader is unlocked?
Basically everything I do on my phone scares me now. I opened my bootloader today so I can see what stock recovery looked like. I got some weird icons that scared me. I cannot stay where I am because I cannot get OTA updates, and I cannot flash updates myself. HELP!
Thanks, people on this forum are awesome, but you all know too much to be able to write a proper noobs guide.

Valitri said:
So I've been reading these forums for days on end now before I touch my phone again. Is my order of things to do correct? (HTC One XL (AT&T))
1. Root
2. Supercid
3. Unlock bootloader
---Currently here---
4. Install CWM/make a backup
5. Relock bootloader
6. Flash a RUU (1.88?)
7. Unlock bootloader
8. Flash a rom
9. Enjoy
As shown above, I rooted, have su on my screen and I can get into the bootloader by vol down+power. I had a scare trying to install RUU 1.85 but I think it failed because my bootloader is unlocked?
Basically everything I do on my phone scares me now. I opened my bootloader today so I can see what stock recovery looked like. I got some weird icons that scared me. I cannot stay where I am because I cannot get OTA updates, and I cannot flash updates myself. HELP!
Thanks, people on this forum are awesome, but you all know too much to be able to write a proper noobs guide.
Click to expand...
Click to collapse
Those steps are correct EXCEPT for 5, 6 and 7. You don't need those if you're flashing a custom rom, only if you're staying official and using an RUU. We can flash insecure boot.img files now which allow us to jump around firmware versions without blowing up. Just make sure you do a factory reset from recovery before flashing a new custom rom to prevent any weird bugs (you can use Titanium Backup to backup all your apps). Also, I would personally recommend flashing TWRP over CWM. It's a little more friendly in terms of UI and has a bit more functionality baked in.
Edit: And just FYI, the RUU did fail because your bootloader was unlocked. And now you know.

Are you on 1.85 already? If so you are set. But if you aren't, relock the downloader by connecting your phone to your computer via USB in fastboot and typing fastboot OEM lock, upgrade to 1.85 and then unlock the bootloader once again.

stnguyen09 said:
Those steps are correct EXCEPT for 5, 6 and 7. You don't need those if you're flashing a custom rom, only if you're staying official and using an RUU. We can flash insecure boot.img files now which allow us to jump around firmware versions without blowing up. Just make sure you do a factory reset from recovery before flashing a new custom rom to prevent any weird bugs (you can use Titanium Backup to backup all your apps). Also, I would personally recommend flashing TWRP over CWM. It's a little more friendly in terms of UI and has a bit more functionality baked in.
Edit: And just FYI, the RUU did fail because your bootloader was unlocked. And now you know.
Click to expand...
Click to collapse
Thanks for confirming why the RUU failed. I was scared because it never said it failed or errored. I let it run for 90+ minutes and finally did a hard reset on my phone.
I downloaded Titanium but I don't understand where the backups go. How to save them or how to use them for recovery. I also don't understand how people talk about this phone having an SD card when it doesn't.
I saw TWRP and it looked like the better option but I thought a lot of the roms needed CWM to flash from. I guess I really don't fully understand how to flash a rom then.
This is so weird because I jailbroke my iPhone 3g, and tried multiple roms on my cousins Droid X a long time ago.
Easy question. If you stick with roms, any reason to ever relock the bootloader?
Thanks

Lilshaun said:
Are you on 1.85 already? If so you are set. But if you aren't, relock the downloader by connecting your phone to your computer via USB in fastboot and typing fastboot OEM lock, upgrade to 1.85 and then unlock the bootloader once again.
Click to expand...
Click to collapse
I'm on 1.73
As the previous poster said, if I want custom roms I shouldn't even bother with the RUU? Is the RUU just a way to get the most updated factory settings because of root? Also do RUUs cancel root?

Valitri said:
Thanks for confirming why the RUU failed. I was scared because it never said it failed or errored. I let it run for 90+ minutes and finally did a hard reset on my phone.
I downloaded Titanium but I don't understand where the backups go. How to save them or how to use them for recovery. I also don't understand how people talk about this phone having an SD card when it doesn't.
I saw TWRP and it looked like the better option but I thought a lot of the roms needed CWM to flash from. I guess I really don't fully understand how to flash a rom then.
This is so weird because I jailbroke my iPhone 3g, and tried multiple roms on my cousins Droid X a long time ago.
Easy question. If you stick with roms, any reason to ever relock the bootloader?
Thanks
Click to expand...
Click to collapse
1. You never need to relock the bl unless you're RUU'ing
2. TWRP and CWM do the same thing, what you can do with one you can pretty much assume you can do with the other
3. Titanium Backup (I refer to it as TiBu) stores the backup files on your phone in a Titanium Backup folder on your sd card. You use the TiBu app itself to batch restore your apps. So this mean you're gonna have to redownload it manually from the Play Store after a factory wipe. You also have the option or restoring your apps with data and also restoring system data. In my experience, restoring system data is always a bad idea and will cause weird behavior. Restoring app data also sometimes has weird consequences, depending on the app, so I usually just restore my apps without data and individually restore data to apps I know will have no issue and are a pain to set up again.
4. We refer to it as an sd card because it technically still is one, just soldered onto the board.
5. Yes, RUU will get rid of root. It returns your phone to its factory state (except it doesn't touch your user data)
---------- Post added at 02:35 PM ---------- Previous post was at 02:33 PM ----------
Lilshaun said:
Are you on 1.85 already? If so you are set. But if you aren't, relock the downloader by connecting your phone to your computer via USB in fastboot and typing fastboot OEM lock, upgrade to 1.85 and then unlock the bootloader once again.
Click to expand...
Click to collapse
Upgrading to 1.85 isn't necessary since we can flash boot.img and jump between versions

Thank you. I will run a backup from titanium and download it to my computer. Then I will flash TWRP, then try some roms.

Valitri said:
Thank you. I will run a backup from titanium and download it to my computer. Then I will flash TWRP, then try some roms.
Click to expand...
Click to collapse
You can have TiBu sync to a Dropbox, Google Drive, or Box account too. The scheduling feature is real nice. I have mine running the 2 default scheduled backup tasks every morning at 6am and then automatically uploading to Google Drive provided that I am plugged in and on WiFi.
I have it run every morning just in case I do something stupid during the day.
Oh and make sure to watch your internal storage space. CWM/TWRP backups take up A LOT of space, around 1GB (that's off the top of my head, I know it's around there somewhere). Manage your backups carefully, deleting ones you don't need.

you dont need to bootloader unlock before you upgrade to 1.85. just get the unlock code and then, with a locked bootloader, update RUU to 1.85. then afterwards unlock bootloader with unlock code.bin.

Valitri said:
Thank you. I will run a backup from titanium and download it to my computer. Then I will flash TWRP, then try some roms.
Click to expand...
Click to collapse
Titanium is just for backing up apps not the entire phone. Sorry if you knew that, it just sounded like you didn't.
You need to flash TWRP and do a backup with it. This will backup your entire phone. In case you ever run into issues you know that you have a backup of your phone from when it was fully functional. This stays on your phone and if you ever need to restore it you do so from within TWRP.

pside15 said:
Titanium is just for backing up apps not the entire phone. Sorry if you knew that, it just sounded like you didn't.
You need to flash TWRP and do a backup with it. This will backup your entire phone. In case you ever run into issues you know that you have a backup of your phone from when it was fully functional. This stays on your phone and if you ever need to restore it you do so from within TWRP.
Click to expand...
Click to collapse
Right, think of a TWRP/CWM backup as the equivalent of a Windows System Restore Point or a Mac Time Machine Backup. It's pretty much a snapshot of your system that you can jump back to in order to revert anything you did that screwed things up.

Restoring to stock

Some months ago I followed guides here to SuperCID, s-off and install a custom ROM. The past few days my touch screen has become unresponsive, at first this was fixed by reflashing the ROM, but now, nothing will fix it, and the touch screen is completely unresponsive. So it seems I will have to return it to the shop to send off for repair. Of course I don't want them to have any reason to say it was the custom ROM that has caused it, warranty void blah blah so need to restore it to stock.
So far I have re-flashed with a stock ROM and changed the CID to what it was, and s-on. I can't remember whether I changed the MID, currently it is PG58*****, though I believe it should be PG5813001, and I'm not sure how to go about changing this (or if it needs changing, will they look into that?)
Another thing I'm unsure of, I downloaded the ROM from here: http://forum.xda-developers.com/showthread.php?t=1074559 I don't know if these ROMs are rooted or not? Is there any way to tell? Or is it a safe assumption they are not?
And finally, hboot, before flashing the stock ROM, this was 1.17, now it is 1.18. Is there anything in here that might suggest the phone has been tinkered with in ways they don't like? I just want to make sure I have covered everything so they don't immediately refuse to repair. If I have missed anything else please let me know.
Thanks.
Edit: I've also read about flashing stock recovery, though this may be included in the the stock ROM RUU I used, can someone confirm?

None of the 130 viewers have any advice on this one?

HB489 said:
Some months ago I followed guides here to SuperCID, s-off and install a custom ROM. The past few days my touch screen has become unresponsive, at first this was fixed by reflashing the ROM, but now, nothing will fix it, and the touch screen is completely unresponsive. So it seems I will have to return it to the shop to send off for repair. Of course I don't want them to have any reason to say it was the custom ROM that has caused it, warranty void blah blah so need to restore it to stock.
So far I have re-flashed with a stock ROM and changed the CID to what it was, and s-on. I can't remember whether I changed the MID, currently it is PG58*****, though I believe it should be PG5813001, and I'm not sure how to go about changing this (or if it needs changing, will they look into that?)
Another thing I'm unsure of, I downloaded the ROM from here: http://forum.xda-developers.com/showthread.php?t=1074559 I don't know if these ROMs are rooted or not? Is there any way to tell? Or is it a safe assumption they are not?
And finally, hboot, before flashing the stock ROM, this was 1.17, now it is 1.18. Is there anything in here that might suggest the phone has been tinkered with in ways they don't like? I just want to make sure I have covered everything so they don't immediately refuse to repair. If I have missed anything else please let me know.
Thanks.
Edit: I've also read about flashing stock recovery, though this may be included in the the stock ROM RUU I used, can someone confirm?
Click to expand...
Click to collapse
To Flash stock recovery read 2 in HERE I believe these ROMs are not rooted, to check just look for SuperSU or Superuser app, if it is not installed you are not rooted. Don't worry at all they'll never find out you rooted your phone, usually they never check. Read THIS guide it has the answer to all your questions regarding revert to stock

elvisypi said:
To Flash stock recovery read 2 in HERE I believe these ROMs are not rooted, to check just look for SuperSU or Superuser app, if it is not installed you are not rooted. Don't worry at all they'll never find out you rooted your phone, usually they never check. Read THIS guide it has the answer to all your questions regarding revert to stock
Click to expand...
Click to collapse
Thanks, though unfortunately I can't check what apps are installed due to the touch screen being unresponsive. But if that's not something they'll look into then fair enough.
The second thread doesn't quite answer everything (whether the ROMs are rooted for example), however, the first thread details extracting stock recovery from an RUU, so I guess that means I don't need to worry about that as it would have been flashed with the ROM.
One other thing - do they require the SD card to be sent also? Is there anything on there that should be removed? Any data relating to apps that use root privileges might raise an eyebrow; is it safe to do a reformat of the SD card? I'm not sure how much is on there that is vital the system.
Thanks for your answer.

HB489 said:
Thanks, though unfortunately I can't check what apps are installed due to the touch screen being unresponsive. But if that's not something they'll look into then fair enough.
The second thread doesn't quite answer everything (whether the ROMs are rooted for example), however, the first thread details extracting stock recovery from an RUU, so I guess that means I don't need to worry about that as it would have been flashed with the ROM.
One other thing - do they require the SD card to be sent also? Is there anything on there that should be removed? Any data relating to apps that use root privileges might raise an eyebrow; is it safe to do a reformat of the SD card? I'm not sure how much is on there that is vital the system.
Thanks for your answer.
Click to expand...
Click to collapse
No the ROMs in the second post are not rooted they are stock. The whole point of the post is to restore stock( read 3. RUU to restore stock). Stock recovery is smth else from stock ROM. You also need stock recovery to install OTA updates from google. Use Android Recovery Manager to download and install your stock recovery. Than in fastboot the stock recovery.img. I can't assure you that they won't notice you were rooted, but they usually don't. Keep in mind that when you unlocked your bootloader you accepted to void your warranty, and your serial number is in HTCs website. (theoretically) you can never be sure they won't discover you, but practically installing stock ROM, stock recovery, locking bootloader and getting back to s-on is enough to not get spotted
And you can format the SD Card if you want, you made a fresh install so there shouldn't be any files regarding it, just the files from the old system, but do a backup first just in case

elvisypi said:
No the ROMs in the second post are not rooted they are stock. The whole point of the post is to restore stock( read 3. RUU to restore stock). Stock recovery is smth else from stock ROM. You also need stock recovery to install OTA updates from google. Use Android Recovery Manager to download and install your stock recovery. Than in fastboot the stock recovery.img. I can't assure you that they won't notice you were rooted, but they usually don't. Keep in mind that when you unlocked your bootloader you accepted to void your warranty, and your serial number is in HTCs website. (theoretically) you can never be sure they won't discover you, but practically installing stock ROM, stock recovery, locking bootloader and getting back to s-on is enough to not get spotted
And you can format the SD Card if you want, you made a fresh install so there shouldn't be any files regarding it, just the files from the old system, but do a backup first just in case
Click to expand...
Click to collapse
Thanks again. If I recall correctly I used revolutionary, not HTC dev so I don't think they'll have my imei? Android recovery manager doesn't have the correct version for my phone, but further down the post it another method is extracting the recovery from the RUU, which is why I assumed stock recovery would have been installed when I flashed the RUU. I guess there is no harm in manually flashing the recovery to be sure though.

HB489 said:
Thanks again. If I recall correctly I used revolutionary, not HTC dev so I don't think they'll have my imei? Android recovery manager doesn't have the correct version for my phone, but further down the post it another method is extracting the recovery from the RUU, which is why I assumed stock recovery would have been installed when I flashed the RUU. I guess there is no harm in manually flashing the recovery to be sure though.
Click to expand...
Click to collapse
No HTCdev is not a recovery, it's the only way of unlocking your bootloader, which you have done for sure. But don't worry I assure you they don't go so deep. There's nothing wrong in flashing manually the recovery. Good luck

[Q] Stuck in Bootloader and TWRP

I have an AT&T HTC One X that's rooted. I wanted to put Cyanogenmod 10 on it, but I accidently wiped the System files instead of the cache. Now it can't boot up regularly, I've tried using Rom Update Utility but it doesn't seem to work. Factory Reset doesn't seem to work either. I didn't expect this to happen because my friend just flashed his a couple of days ago. I've tried making a backup and restoring but no matter what I can't get the phone to start up normally. Unless I put it in TWRP (Team Win Recovery Project) or the HBoot/Bootloader I really can't use it for anything. Any suggestions? I would greatly appreciate it. Also when bootloader opens it says "Tampered" and under it "Unlocked" because I did root it. It didn't have "Tampered" when I first rooted it.
I don't care about Cyanogenmod 10 anymore I just want to have it working again.
Everything else about the phone is in perfect condition but what I just said is the only problem.

Wiping /system means you wiped the OS. Naturally, it can't boot up with no rom in place. You need to flash something.

iElvis said:
Wiping /system means you wiped the OS. Naturally, it can't boot up with no rom in place. You need to flash something.
Click to expand...
Click to collapse
Well, I've already flashed it to a few things and so far it hasn't changed anything. Got any links?

Did you fastboot flash boot boot.IMG ? Don't know what hboot you are on, but could be it.
Sent from my Carbon-ize Evita using xda-developers app

Cant get rid of "RELOCKED" in bootloader

I recently got my HTC one back from repairs, I had custom software on it before I shipped it off. So when I got it back, I wanted to install the custom software back on it. I did the root process, got it rooted. Installed recovery, wiped the needed files and then tried to flash the software. It failed. I got worried because I didnt make a backup before I did this. So I had to RELOCK and install stock software. I then try to do the process again. I root, and then try to install the recovery. I get an error. Turns out, when I rooted, the bootloader was still "RELOCKED" but it was s-off. I then try to install revone. I try to do the process where I unlock it. Except I cant run the command "su" because I dont have a recovery.
Right now im kinda just stuck. I dont know what to do to fix it...
It would be helpful if someone would tell me how to get it to unlocked, or anything like it.

Difference between the two??

Is there a difference between the Samsung J327P and the Samsung J320P? I'm trying to determine a difference so I can find the correct root file and process to root my phone. Every way I've tried so far has gotten stuck at trying to unlock my bootloader.

Vikings09876 said:
Is there a difference between the Samsung J327P and the Samsung J320P? I'm trying to determine a difference so I can find the correct root file and process to root my phone. Every way I've tried so far has gotten stuck at trying to unlock my bootloader.
Click to expand...
Click to collapse
They are completely different, one has Exynos chips and the other is Qualcomm chipset, one has marshmallow and the other has lollipop, rear camera is different, the hardware and Kernel are different.
You need files specifically for the model you have.
Are you saying that you've successfully rooted your device another way but you're getting stuck at unlocking the bootloader? If you are truly rooted then it isn't a problem with how you rooted. Are you sure your bootloader can be unlocked?
Sent from my SM-S903VL using Tapatalk

Droidriven said:
They are completely different, one has Exynos chips and the other is Qualcomm chipset, one has marshmallow and the other has lollipop, rear camera is different, the hardware and Kernel are different.
You need files specifically for the model you have.
Are you saying that you've successfully rooted your device another way but you're getting stuck at unlocking the bootloader? If you are truly rooted then it isn't a problem with how you rooted. Are you sure your bootloader can be unlocked?
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I'm not rooted, I attempted attempted to flash TWRP and it seemed to be a success till I tried to enter TWRP and it just boots the phone up. So ATM, I seem to have no recovery as TWRP isn't working and the stock ROM isn't available for me to flash back on. So can I get stock recovery back just be doing a reset from my settings or do I just have to wait it out till it's supported?

Vikings09876 said:
I'm not rooted, I attempted attempted to flash TWRP and it seemed to be a success till I tried to enter TWRP and it just boots the phone up. So ATM, I seem to have no recovery as TWRP isn't working and the stock ROM isn't available for me to flash back on. So can I get stock recovery back just be doing a reset from my settings or do I just have to wait it out till it's supported?
Click to expand...
Click to collapse
You'll have to flash a copy of your stock recovery or your stock firmware, if you can find a copy.
Next time, do a better job of searching about your device and what can and CAN'T be done on whatever device you might have.
No, a factory reset won't fix it, in fact, a factory reset from settings on rooted devices only bricks the device and then the WHOLE OS has to be reflashed.
It isn't the same on mobile devices as it is on PC. On PC there is a partition that has a copy of your OS stored on it and factory reset reflashes that back to your main partition.
On mobile, factory reset only wipes what you've installed in user partition, your recovery is not in user partition so you'll still have the issue after resetting.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
You'll have to flash a copy of your stock recovery or your stock firmware, if up can find a copy.
Next time, do a better job of searching about your device and what can and CAN'T be done on whatever device you might have.
No, a factory reset won't fix it, in fact, a factory reset from settings on rooted devices only bricks the device and then the WHOLE OS has to be reflashed.
It isn't the same on mobile devices as it is on PC. On PC there is a partition that has a copy of your OS stored on it and factory reset reflashes that back to your main partition.
On mobile, factory reset only wipes what you've installed in user partition, your recovery is not in user partition so you'll still have the issue after resetting.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I'm just gonna leave it as is rn because the phone works tbh, I just don't have a working recovery. The stock ROM doesn't seem to be available atm as the phone was just recently released. I'm sure it will be released at some point, and I'm not too worried about it. If anything, I can just pay it off and upgrade to a different phone.

Use crom apk by Samsung to unlock your bootloader.....till the files come out that's as far as me or ne of us r getting
Update twrps have been tried to compile with no success till Ashyx (our luck to have his services) recieves the kernel source
https://forum.xda-developers.com/android/development/samsung-j3-root-t3544157/page9
There is a rooted boot.img that ill be testing since i havbe access to exclusive stock firmware and have recourse should ne th ing be wrong....ie a brick.
https://forum.xda-developers.com/android/development/samsung-j3-root-t3544157/page9
Kindly redirect to this thread