I am about a week or so away from receiving my V20, was curious if there is anything a Sprint user would miss after unlocking the bootloader and using a custom ROM.
Do you miss the AM/FM radio?
Is the development community slower than usual when a firmware update hits and the custom ROMs don't update their side as quick?
Besides disabling the AM/FM radio are data speeds or any other radios (blueooth/wifi/LTE bands) performing better/worse/differently?
And lastly, since it is impossible to go back to a stock phone after rooting, do you regret rooting and wish you could go back to stock?
If those out there could answer any or all of those questions I would greatly appreciate it.
Thank you!
williamvito said:
I am about a week or so away from receiving my V20, was curious if there is anything a Sprint user would miss after unlocking the bootloader and using a custom ROM.
Do you miss the AM/FM radio?
Is the development community slower than usual when a firmware update hits and the custom ROMs don't update their side as quick?
Besides disabling the AM/FM radio are data speeds or any other radios (blueooth/wifi/LTE bands) performing better/worse/differently?
And lastly, since it is impossible to go back to a stock phone after rooting, do you regret rooting and wish you could go back to stock?
If those out there could answer any or all of those questions I would greatly appreciate it.
Thank you!
Click to expand...
Click to collapse
FM radio works. AM never existed. I am fairly quick on patching the stock roms but for custom(or stock custom) roms thats on other devs. I have noticed no issues with my connections compared to before rooting. I was the 3rd LS997 rooted if I remember right(This was before root was released). I can go back to stock at anytime if I want. Its not possible via a KDZ but I have already figured it out manually. Im not going to make the method public though because it is VERY involved and if someone messes up doing it, it WILL brick your phone. Then I would be blamed. So I have no plans to release it unless i get an easier way to do it. Just know that the hard part of figuring out if its possible is done...
Do keep in mind if you receive the ls997 on zv6 or zv7 you cannot root.
If you haven't noticed who I am look at the poster of the LS997 root method
me2151 said:
FM radio works. AM never existed. I am fairly quick on patching the stock roms but for custom(or stock custom) roms thats on other devs. I have noticed no issues with my connections compared to before rooting. I was the 3rd LS997 rooted if I remember right(This was before root was released). I can go back to stock at anytime if I want. Its not possible via a KDZ but I have already figured it out manually. Im not going to make the method public though because it is VERY involved and if someone messes up doing it, it WILL brick your phone. Then I would be blamed. So I have no plans to release it unless i get an easier way to do it. Just know that the hard part of figuring out if its possible is done...
Do keep in mind if you receive the ls997 on zv6 or zv7 you cannot root.
If you haven't noticed who I am look at the poster of the LS997 root method
Click to expand...
Click to collapse
The good news, I received the phone on ZV5(!). The bad news? I followed your excellent tutorial until the very end when my over confidence didn't do a full wipe and now I have the secure start-up issue.
The unfortunate reality was me reading AFTER THE FACT your very clear warning:
**************
*****ALL USERS*****
If you encounter a "Secure Boot" Password then booting the first time you did not Format data properly.
To reiterate: To properly decrypt the device you need to boot into TWRP and go to WIPE->FORMAT DATA and you will be prompted to type "yes" to format and decrypt.
Click to expand...
Click to collapse
So now I'm stuck, I've tried booting back into TWRP via hardware buttons and without having the password I can't even go back in to re enable USB debugging.
Am I completely out of options here?
williamvito said:
The good news, I received the phone on ZV5(!). The bad news? I followed your excellent tutorial until the very end when my over confidence didn't do a full wipe and now I have the secure start-up issue.
The unfortunate reality was me reading AFTER THE FACT your very clear warning:
So now I'm stuck, I've tried booting back into TWRP via hardware buttons and without having the password I can't even go back in to re enable USB debugging.
Am I completely out of options here?
Click to expand...
Click to collapse
No you arnt. You need to reinstall twrp through fastboot and then pull battery to turn off phone. Insert battery the use Hw Keys method by holding vol- and power til you the Lg the only let go of power then holding both again until you see factory reset. Do yes twice.
me2151 said:
No you arnt. You need to reinstall twrp through fastboot and then pull battery to turn off phone. Insert battery the use Hw Keys method by holding vol- and power til you the Lg the only let go of power then holding both again until you see factory reset. Do yes twice.
Click to expand...
Click to collapse
You're the man, thanks for the quick reply! I will give this another go tomorrow.
me2151 said:
No you arnt. You need to reinstall twrp through fastboot and then pull battery to turn off phone. Insert battery the use Hw Keys method by holding vol- and power til you the Lg the only let go of power then holding both again until you see factory reset. Do yes twice.
Click to expand...
Click to collapse
One last thing before I attempt this because I don't want to create another problem for myself, I'm lost as to how i'm supposed to reinstall TWRP from fastboot on my PC if I can't get the phone into fastboot mode. Is there a hardware method I need to do to get the phone into fastboot mode?
williamvito said:
One last thing before I attempt this because I don't want to create another problem for myself, I'm lost as to how i'm supposed to reinstall TWRP from fastboot on my PC if I can't get the phone into fastboot mode. Is there a hardware method I need to do to get the phone into fastboot mode?
Click to expand...
Click to collapse
Once youve started the dirtysanta method it installs a new bootloader. you can access bootloader(fastboot) by holding VOL- and plugging iin the phone when powered off
Related
Hi! I was using my N7 3G reading the news and suddenly it became unresponsive. It took about 2 seconds to recognize my touch. So i decided to turn it off and turn it back on. But after it turned back on the touch screen is completely dead. I can't even unlock it. Power and volume buttons still work. I'm on CM 10.1.3
I even forced reboot it many times by holding the power button for about 20s but that didn't help. Anyone ever had this issue too? It seems like a hardware problem. If that's the case i would have it repaired by ASUS but I'm afraid that I won't get warranty because I'm not on stock ROM+rooted+unlocked bootloader
Can you get into recovery? If so, try wiping the cache partition first to see if that helps.
If that doesn't help, do you have usb debugging enabled? If so,
should be able to use the Nexus 7 toolkit. Just boot your tablet, plug it in your machine, fire up the Nexus 7 toolkit and have it unroot and relock your BL.
You might also want to try and see if you can backup your data partition and your internal storage with the N7 toolkit. If you can do that, then you won't lose any of your data or application settings.
You should also be able to flash it back to stock as well via the toolkit and have it erase the user data.
If usb debugging is NOT enabled, then you might be hosed. You could at least do a factory reset in the main recovery.
Other than that, not much else can probably be done unless you want to open your tablet yourself and ensure all the connections are tight. There might be a lose connection for the digitizer and that's all you would need to do to fix it. Of course, that voids your warranty if you open it yourself. I don't know exactly where the hook up is. I'm sure a quick Google will tell you how to fix this if it's possible.
It definitely sounds like either your digitizer is bad or it's got a lose connection.
Good luck!
Sent from my Nexus 7 using Tapatalk 4
thanks for your help. I was going to plug it in my PC BUT IT'S WORKING AGAIN. I was like WTF lol :laugh: . So it must be a lose connection i guess .
By the way, I'm planning to go back to stock in case it happen again so that i can get my warranty at ASUS. And I don't know much about rooting/ flashing so I want to ask some questions .
1. Can I flash google's stock ROM just like flashing other ROMs like CM with bootloader unlocked?
2. Have you tried KitKat. If so have you experienced battery drain? The only reason I rooted and installed CM is that I hate the battery draining issue. I had it since I updated my N7 3G to 4.2.2 and it kept happenings in 4.3
Anyway thanks a lot :good:
So far no major issue with battery and yes flashing process is the same just be careful u need to update ur bootloader to go to 4.4 and flashing wrong bootloader will brick ur device to be careful and read every thing.
Please ignore my spelling mistakes. English is not my native language.
xateeq said:
So far no major issue with battery and yes flashing process is the same just be careful u need to update ur bootloader to go to 4.4 and flashing wrong bootloader will brick ur device to be careful and read every thing.
Please ignore my spelling mistakes. English is not my native language.
Click to expand...
Click to collapse
Well, I used wug's nexus root toolkit to root and unlock bootloader. If I use the option:"go back to stock lock bootloader and flash stock", can I install update from OTA like normal again?
Choriandus said:
Well, I used wug's nexus root toolkit to root and unlock bootloader. If I use the option:"go back to stock lock bootloader and flash stock", can I install update from OTA like normal again?
Click to expand...
Click to collapse
YES
The other thread was just too messy with too much cross information.
So, here's the quick and dirty. If you're on 4.4. and rooted you can upgrade to 4.4.2 after disabling Gravity Box and ANY mods (wifi tether, etc) and you will keep root but you will lose the ability to write to the system. This effectively makes root useless.
It's unlikely 4.4.2 will ever be rooted, but there is some sliver of hope that a solution will be found (likely involving SBF) that allows you to retain root and /system RW but it can't be taken for granted.
There's lots of other info, but this thread is just designed to separate out the discussions.
Just to add..
Inside the OTA is a manifest file which which contains check sums for files which need to exist on your phone. If the expected files are not on your phone, or the checksums of the files don't match the manifest, the OTA will fail. Hence why you need to undo some of the "hacks" and "mods"
Addtioinally to install the OTA, you need to have stock recovery on your phone. If its not on there, the OTA will either fail, or worse, put you in a boot loop! (erasing your phone's cache can help you out of the loop... mfastboot erase cache )
Once you are on 4.4.2, you can not downgrade your rom to 4.4 or older!! Trying to downgrade can/will result in bricking your device.
Can anyone comment on the "This will be permanent" warning from when rooting with SlapMyMoto/MotoWPNoMo?
I'm trying to get all my ducks in a row before I update to 4.4.2 and lose a functional root.
I'm thinking of reflashing /sys or restoring tether hack, and accepting OTA.
evandena said:
Can anyone comment on the "This will be permanent" warning from when rooting with SlapMyMoto/MotoWPNoMo?
I'm trying to get all my ducks in a row before I update to 4.4.2 and lose a functional root.
I'm thinking of reflashing /sys or restoring tether hack, and accepting OTA.
Click to expand...
Click to collapse
When MotoWPNoMo came its disabling write protection was "permanent" (it survived flashing between the roms which were out at that time) however it does NOT survive the 4.4.2 OTA.
The statement in the initial post... "keep root but you will lose the ability to write to the system. This effectively makes root useless. " is 100% accurate for those with locked bootloaders.
I got the notification this morning when I woke up that the OTA was downloaded and ready to install. It was a persistent notification, and I didn't want it there. I long pressed on it and went to app info, which was MotoOTA. I force stopped it, which did remove the notification, but it came back immediately.
I then unchecked the "show notifications" box and it was gone. I'm not really a fan of freezing apps with TiBu or anything like that, so this worked for me. I don't really care to update unless I can keep root and have write protection off.
I didn't see anything in the changelog that really implied that I'm missing much by not upgrading, for now at least. I decided to get the Moto Maker edition because I valued the customization more than then unlocked bootloader. The phone works great and does everything I need it to right now, so I have no desire to upgrade and lose root yet.
One question though, I read somewhere before that booting through recovery disables write protection, and allows you to install Xposed and other root stuff. I assume that write protect being off only lasts until the next reboot? And then you'd need to boot through recovery again, and possibly apply things through Xposed each time? Or is it just for initial setup?
fury683 said:
One question though, I read somewhere before that booting through recovery disables write protection, and allows you to install Xposed and other root stuff. I assume that write protect being off only lasts until the next reboot? And then you'd need to boot through recovery again, and possibly apply things through Xposed each time? Or is it just for initial setup?
Click to expand...
Click to collapse
You don't have to boot into recovery each time. You do need to soft reboot each time after a hard reboot though for it to stick
evandena said:
Can anyone comment on the "This will be permanent" warning from when rooting with SlapMyMoto/MotoWPNoMo?
I'm trying to get all my ducks in a row before I update to 4.4.2 and lose a functional root.
I'm thinking of reflashing /sys or restoring tether hack, and accepting OTA.
Click to expand...
Click to collapse
Well that didn't work. I'm stuck in a boot loop now. Guess I'll try flashing /sys when I get home.
fury683 said:
...One question though, I read somewhere before that booting through recovery disables write protection, and allows you to install Xposed and other root stuff. I assume that write protect being off only lasts until the next reboot? And then you'd need to boot through recovery again, and possibly apply things through Xposed each time? Or is it just for initial setup?
Click to expand...
Click to collapse
The early root processes (RockMyMoto and SlapMyMoto) replaced stock recovery with a trick that booted the phone with write protect disabled. To take the OTA, you need to put stock recovery back, thus removing this trick.
Later, MotoWPNoMo replaced the trick of booting to a tricked recovery, and allowed Write Protection to be disabled for normal boot too, and allowed stock recovery to be put back on, but this doesn't survive the OTA.
---------- Post added at 05:35 PM ---------- Previous post was at 05:34 PM ----------
evandena said:
Well that didn't work. I'm stuck in a boot loop now. Guess I'll try flashing /sys when I get home.
Click to expand...
Click to collapse
No. Put your phone in bootloader mode... then...
mfastboot erase cache
KidJoe said:
No. Put your phone in bootloader mode... then...
mfastboot erase cache
Click to expand...
Click to collapse
Can that be done from the phone with fastboot, or do I need my computer? I haven't messed with this stuff since November, so I'm a little rusty.
evandena said:
Can that be done from the phone with fastboot, or do I need my computer? I haven't messed with this stuff since November, so I'm a little rusty.
Click to expand...
Click to collapse
Have to enter that command from the PC
Wifi Tether require Write Protection?
I wasn't able to find an answer on this so I'm asking here. The only thing I really use root for on my Moto X is the wifi tether because I still have unlimited data. I am wondering if I can keep root through the OTA and keep using the Wifi Tether app after it reenables write protection. Thanks in advance.
Reserved Name said:
I wasn't able to find an answer on this so I'm asking here. The only thing I really use root for on my Moto X is the wifi tether because I still have unlimited data. I am wondering if I can keep root through the OTA and keep using the Wifi Tether app after it reenables write protection. Thanks in advance.
Click to expand...
Click to collapse
You'll probably have to keep the file on your phone to replace each time you do a hard reboot. Without R/W, your changes won't stick after a boot. Otherwise, I think you can still use the entitlement trick without an issue other than it not sticking.
Reserved Name said:
I wasn't able to find an answer on this so I'm asking here. The only thing I really use root for on my Moto X is the wifi tether because I still have unlimited data. I am wondering if I can keep root through the OTA and keep using the Wifi Tether app after it reenables write protection. Thanks in advance.
Click to expand...
Click to collapse
I'd like to know this too. At this point the only thing I really use root for is Greenify, which no longer requires root, tethering with my unlimited data (VZ), and bypassing the exchange pin requirement.
KidJoe said:
Have to enter that command from the PC
Click to expand...
Click to collapse
I'm having problems getting into recovery. Once I select Recovery from the fastboot menu, it boots straight into normal mode.
*edit* maybe I don't need adb to recognize the phone for fastboot erase cache to work. Playing with it now...
*edit 2* ok, it looks like that stopped my boot loops. Now to figure out why the update didn't work the first time...
CartlandSmith said:
you select recovery by hitting vol up button.
Click to expand...
Click to collapse
Yep, was. It was booting to safe mode when Recovery was selected.
I should clarify, I don't use the entitlement hack I just use the Wifi Tether apk. Just wondering if it requires write protection to be disabled or not. Thanks.
If I take the OTA and have root but no system RW, is it still possible to install Xposed, soft reboot, and it works normally until a hard reboot happens? Or is Xposed completely broken?
Reserved Name said:
I wasn't able to find an answer on this so I'm asking here. The only thing I really use root for on my Moto X is the wifi tether because I still have unlimited data. I am wondering if I can keep root through the OTA and keep using the Wifi Tether app after it reenables write protection. Thanks in advance.
Click to expand...
Click to collapse
You're talking "wifi tether for root" like this -> https://code.google.com/p/android-wifi-tether/
I don't think it will work due to the changes it makes when you start and stop tethering. (It appears to update files in the normally write protected area). Then again, if temp changes can be made after 4.4.2 is installed, it might work.
I think you and I are the only ones who use that app.. most everyone else is using Xposed or the hacked entitlement apk.
evandena said:
I'm having problems getting into recovery. Once I select Recovery from the fastboot menu, it boots straight into normal mode.
*edit* maybe I don't need adb to recognize the phone for fastboot erase cache to work. Playing with it now...
*edit 2* ok, it looks like that stopped my boot loops. Now to figure out why the update didn't work the first time...
Click to expand...
Click to collapse
If it's booting normally when you select recovery, it's because your recovery is missing - probably because you used SlapMyMoto.
You need to restore your recovery... you can boot into fastboot, then write the correct recovery to your phone with fastboot flash recovery recovery.img, where recovery.img is a file pulled out of the SBF package for whatever version you're running.
You guys really should just wait! Even if a new root method isn't discovered, you will be able to flash a stock 4.4.2 ROM or Eclipse's stock-based ROM via Safestrap soon enough. Certainly not worth risking losing root! Patience!
Sent from my Moto X
I have successfully rooted my Spring LG V20 using DirtySanta and it seems to be working for the most part, but I'm not really impressed with the benefits of rooting at this point. What's even more disappointing was the lack of a method for reverting to stock. My question is--can I bring this in to a Sprint store and ask them to restore it to stock? I checked fastboot for oem status and everything reads false. I don't have SuperSU or any other root apps installed on the phone. The only thing that shows up is the damn red triange every time I boot. Anyone have any experience with this? I don't really want to get in trouble for rooting, but I'd really like to get back to factory stock. Doesn't look like we'll be getting a restore method any time soon either, correct? Thanks in advance...
I don't think there is a revert method (inside or outside the store). I know it's after the fact, but on your next device, you may want to figure out exactly what you'd want to do with root before you go through with it. I typically only do it for TB backup purposes and XPOSED, but I've found that I can back up in other ways, and I dig stock enough not to risk rooting. I don't knock you for rooting (there are plenty of good reasons to), this is just my advice going forward. In the meantime, you should look around XDA, you may find your golden goose app that you can leverage root for. Good luck.
bgibson72 said:
I have successfully rooted my Spring LG V20 using DirtySanta and it seems to be working for the most part, but I'm not really impressed with the benefits of rooting at this point. What's even more disappointing was the lack of a method for reverting to stock. My question is--can I bring this in to a Sprint store and ask them to restore it to stock? I checked fastboot for oem status and everything reads false. I don't have SuperSU or any other root apps installed on the phone. The only thing that shows up is the damn red triange every time I boot. Anyone have any experience with this? I don't really want to get in trouble for rooting, but I'd really like to get back to factory stock. Doesn't look like we'll be getting a restore method any time soon either, correct? Thanks in advance...
Click to expand...
Click to collapse
hey sorry to hear that your having issues,
but you and the other poster are correct, sprint never released a restore file that wasn't encrypted.
And to my knowledge the repair centers would not be able to fix this issues, and sadly lg would more then likely deny a
warranty claim as this was modifications done by the end user.
A good chance in the future that we will get the files needed or a process to revert back to stock, but currently there is no SAFE method to try, and pushing the stock aboot and system.img back to the device WILL hard brick the device.. @me2151 attempted the restore process once, and failed, so please be careful as you may have issues.. The red warning triangle is due to your aboot "bootloader" being swapped for the debug version and will never go away, unless we get a dev willing to risk his device for a .png swap of the warning RED img. Other wise its there forever.
The static on boot up can be removed using a custom kernel but be aware it WILL break things in return. Typically update to prl and profile
fm radio, comfort view and a few other little things..
Hey, thanks for the reply. I can deal with the red warning screen, I just get a little anxious when I can't use the touchscreen or my cellular data gets hosed. As long as there are fixes here (which there have been--thanks to all) and I can use my phone, we're good. I figured if someone could break encryption on government files then why would an encrypted KDZ file be such a challenge? At any rate, I appreciate the help. I'll just keep my fingers crossed for a PNG swap!
Hello my friends.
I bought my U Ultra in December 2017.
Now I decided to flash LeeDroid Oreo on my phone.
It works great.
I backed up in TWRP the parititions "System Image" and "System" in case for going back.
Now my question.
Is it possible to go for going to stock when I recover it all?
Can I lock the bootloader after that?
How to use the "System Image" partition? Can I fully flash my phone to stock with it? With Recovery and so on, because there is no RUU available for me?
My System Version was 2.21.401.1 and my region is Europe/Germany.
Regards
inFiniTyz_Z said:
I backed up in TWRP the parititions "System Image" and "System" in case for going back.
Is it possible to go for going to stock when I recover it all?
How to use the "System Image" partition? Can I fully flash my phone to stock with it? With Recovery and so on, because there is no RUU available for me?
Click to expand...
Click to collapse
If you have TWRP backup you simply recover the backup, wipe data and you are back to stock-ish. Naturally due to lack of original recovery you won't be able to receive/flash OTA. For HTC you simply do not exist.
inFiniTyz_Z said:
Can I lock the bootloader after that?
Click to expand...
Click to collapse
Kind of. You can make OEM lock but it won't be the factory lock. It will be relock. And if you have a custom ROM at that point the phone may not let you boot up.
QDT said:
If you have TWRP backup you simply recover the backup, wipe data and you are back to stock-ish. Naturally due to lack of original recovery you won't be able to receive/flash OTA. For HTC you simply do not exist.
Click to expand...
Click to collapse
In case when I flash the stock recovery too?
inFiniTyz_Z said:
In case when I flash the stock recovery too?
Click to expand...
Click to collapse
If you restore whole system then you will get the OTAs. (This is how I upgraded to Oreo in the first place).
Problem is with TWRP/custom recovery not being capable of performing the factory update (people are soft-bricking their phones).
QDT said:
If you restore whole system then you will get the OTAs. (This is how I upgraded to Oreo in the first place).
Problem is with TWRP/custom recovery not being capable of performing the factory update (people are soft-bricking their phones).
Click to expand...
Click to collapse
When I flash the RUU for my CID from nougat to my phone, and perform an upgrade to oreo, would it result in a hard brick?
inFiniTyz_Z said:
When I flash the RUU for my CID from nougat to my phone, and perform an upgrade to oreo, would it result in a hard brick?
Click to expand...
Click to collapse
There is a topic explaining how to recover first to Nougat and then let you phone receive OTA for Oreo.
I don't know from where you can get RUU for your CID. Keep in mind it has to be the version you have or newer if you are not going to unlock the bootloader and use 3rd party tools to trick force update.
QDT said:
There is a topic explaining how to recover first to Nougat and then let you phone receive OTA for Oreo.
I don't know from where you can get RUU for your CID. Keep in mind it has to be the version you have or newer if you are not going to unlock the bootloader and use 3rd party tools to trick force update.
Click to expand...
Click to collapse
I have the ROM for my CID.
But I would know if it works without hard brick.
I am little bit afraid from it, because I tried this two years ago on my Motorola Moto G2. For one, two, times it worked, then came marshmallow with a new bootloader, so you bricked this phone like ****.
inFiniTyz_Z said:
I have the ROM for my CID.
But I would know if it works without hard brick.
I am little bit afraid from it, because I tried this two years ago on my Motorola Moto G2. For one, two, times it worked, then came marshmallow with a new bootloader, so you bricked this phone like ****.
Click to expand...
Click to collapse
I cannot give you the guarantee. It is for you to decide. The topic explains it really good. I did it several times and no sweat at all. Other ways I don't know.
QDT said:
I cannot give you the guarantee. It is for you to decide. The topic explains it really good. I did it several times and no sweat at all. Other ways I don't know.
Click to expand...
Click to collapse
And I can downgrade to nougat and upgrade with OTA to oreo without hard brick? Did you tried that?
inFiniTyz_Z said:
And I can downgrade to nougat and upgrade with OTA to oreo without hard brick? Did you tried that?
Click to expand...
Click to collapse
Yes, I did that. I went through the described procedure and restored the phone to pristine Nougat and then let it to update via OTA to Oreo.
If your phone is s-on then there hardly any chance you will hard brick it. Soft bricks can happen, naturally. But then, dependently on the case, you can recover from it by reflash, wipe or making the downgrade again via RUU.
One important key combination you have to keep in mind. By pressing (and holding) power with volume down you will see the buttons flashing. Keeping them pressed for ca. 15 sec (shorter, longer depends) forces the phone to reboot.
Good luck.
QDT said:
Yes, I did that. I went through the described procedure and restored the phone to pristine Nougat and then let it to update via OTA to Oreo.
If your phone is s-on then there hardly any chance you will hard brick it. Soft bricks can happen, naturally. But then, dependently on the case, you can recover from it by reflash, wipe or making the downgrade again via RUU.
One important key combination you have to keep in mind. By pressing (and holding) power with volume down you will see the buttons flashing. Keeping them pressed for ca. 15 sec (shorter, longer depends) forces the phone to reboot.
Good luck.
Click to expand...
Click to collapse
It worked. After my question I did the procedure and upgraded to oreo!
Thank you.
No Brick, but I had to erase the data and cache partition again after the first start, because it stucked at the HTC Logo after booting.
But the funfact is: I wanted to do a hard reset after my first try to boot it up, and the phone did a screenshot with the logo!
inFiniTyz_Z said:
It worked. After my question I did the procedure and upgraded to oreo!
Thank you.
No Brick, but I had to erase the data and cache partition again after the first start, because it stucked at the HTC Logo after booting.
But the funfact is: I wanted to do a hard reset after my first try to boot it up, and the phone did a screenshot with the logo!
Click to expand...
Click to collapse
Good. Have fun with the phone. It is quite nice piece of hardware. I like it.
QDT said:
Good. Have fun with the phone. It is quite nice piece of hardware. I like it.
Click to expand...
Click to collapse
Thanks. You too!
And the software status is currently still on modified. Would it change when I lock the bootloader?
inFiniTyz_Z said:
Thanks. You too!
And the software status is currently still on modified. Would it change when I lock the bootloader?
Click to expand...
Click to collapse
What software status? If you restore the original recovery there is no additional message during boot. If you lock the bootloader it will report as "relocked".
QDT said:
What software status? If you restore the original recovery there is no additional message during boot. If you lock the bootloader it will report as "relocked".
Click to expand...
Click to collapse
In the bootloader mode you see your software status. And it is still with stock rom and stock recovery on "modified"
inFiniTyz_Z said:
In the bootloader mode you see your software status. And it is still with stock rom and stock recovery on "modified"
Click to expand...
Click to collapse
And to my knowledge it will be like that. You have flashed unlocked (from HTC but always) bootloader and this has to be noted. It is not that drastical as KNOX for Samsung, doesn't influence the phone functioning.
inFiniTyz_Z said:
It worked. After my question I did the procedure and upgraded to oreo!
Thank you.
No Brick, but I had to erase the data and cache partition again after the first start, because it stucked at the HTC Logo after booting.
But the funfact is: I wanted to do a hard reset after my first try to boot it up, and the phone did a screenshot with the logo!
Click to expand...
Click to collapse
When you say you followed the procedure, which exactly do you mean? Can you please help me by giving me a quick summary of the steps?
I would like to know the procedure as well.
Hi! I've installed a custom ROM, now I would like to go back to the stock ROM, I don't have a nandroid backup, what can I do?
Pretty much what the title says. I've been trying to unlock the bootloader on my sprint v20 to install lineage 16, but I can't seem to get it to fastboot. I tried both using adb commands as well as holding volume down + plugging the cable in, but both ways simply boot the phone without doing anything. Can someone help?
i95swervin said:
Power off the phone, press & hold volume up
( if I'm not mistaken )
and plug in the power cord connected to a PC.
Good luck
Click to expand...
Click to collapse
Hey. Doing this sent my phone to a "download" screen with two icons for a few seconds, and then a firmware update screen. Is this what fastboot looks like? Because I hear people describing it as a menu with options.
Thanks.
Anwiday said:
Hey. Doing this sent my phone to a "download" screen with two icons for a few seconds, and then a firmware update screen. Is this what fastboot looks like? Because I hear people describing it as a menu with options.
Thanks.
Click to expand...
Click to collapse
Wrong volume key.
But you've got an ls997 mate. If you've taken an ota in about the last 18 months Sprint helpfully eliminated any chance of you unlocking the bootloader and rooting.
The last software version it was possible to revert futher back to an actually rootable version was ZV7, way back in the early-mid nougat versions.
Once updated past ZV7 Sprint helpfully physically burned fuses embedded in the CPU to keep you from going back and rooting. Hail overlord Sprint.
Phoenix591 said:
Wrong volume key.
But you've got an ls997 mate. If you've taken an ota in about the last 18 months Sprint helpfully eliminated any chance of you unlocking the bootloader and rooting.
The last software version it was possible to revert futher back to an actually rootable version was ZV7, way back in the early-mid nougat versions.
Once updated past ZV7 Sprint helpfully physically burned fuses embedded in the CPU to keep you from going back and rooting. Hail overlord Sprint.
Click to expand...
Click to collapse
Damn. So there's no way to install a custom ROM then?
Anwiday said:
Damn. So there's no way to install a custom ROM then?
Click to expand...
Click to collapse
Nope. Once it's past ZV7 it's never going back and you need to go back to root and install custom roms.