Hi all.
Can anyone lend a hand to help me get my phone rooted again? I had originally rooted it when it first turned up, by using the guide on these forums. Since then I (stupidly) did the OTA upgrade not thinking about losing root. I went from 33r to 38r. The first I knew was when Titanium back up wouldn't back up.
My problem is that neither of my computers (desktop - XP) (Laptop - Windows 7) will now see my phone. They will both make a sound when connecting via the USB cable but neither of them show the phone via My Computer. I've un-installed/installed the drivers again and I have tried putting the phone in Fastboot and clicking on Unlock Bootloader, via the Toolbox V3, but the phone will only "reboot" to the home screen. I'm needing a bit of help from someone who knows what they are doing
Thanks in advance for any help... Foz
Once you unlock the bootloader, I don't think you need to unlock it again. If you lose root after an OTA, I think all you need to do is reflash superuser from recovery. And don't touch those toolboxes. They don't help you learn to solve these problems by yourself.
Sent from my A0001 using XDA Free mobile app
I've tried that but it fails...
Turn off phone.
volumedown and on
phone enters cyanogen recovery
apply update
internal storage
(locate to SuperSU -v2.02.zip
INSTALL FAILS.
OKay
reboot system, back to my normal settings/homescreen.
I have SuperSu on my phone BUT get the warning that no binary is installed and I need to re root, hencmy posting here.
adamfoz said:
I've tried that but it fails...
Turn off phone.
volumedown and on
phone enters cyanogen recovery
apply update
internal storage
(locate to SuperSU -v2.02.zip
INSTALL FAILS.
Click to expand...
Click to collapse
If re-downloading the zip doesn't work you should try a newer SuperSU version.
meekrawb said:
If re-downloading the zip doesn't work you should try a newer SuperSU version.
Click to expand...
Click to collapse
I believe I have the latest version from the play store ( 2.14).
adamfoz said:
I believe I have the latest version from the play store ( 2.14).
Click to expand...
Click to collapse
Should have clarified, you should try a newer version of the zip.
download.chainfire.eu/supersu
Just looked again when in cyan recovery. The Supersu is 2.02 and yet google says I have the 2.14 installed.... (and I have to wait betweening posting arrggghh) Ok, Ill have a play and see what happens. thanks guys
adamfoz said:
Just looked again when in cyan recovery. The Supersu is 2.02 and yet google says I have the 2.14 installed.... (and I have to wait betweening posting arrggghh) Ok, Ill have a play and see what happens. thanks guys
Click to expand...
Click to collapse
I think your problem may be that when you installed the OTA, you also clobbered any custom recovery that was there. Next time, uncheck the option to install recovery.
sparkdroid said:
I think your problem may be that when you installed the OTA, you also clobbered any custom recovery that was there. Next time, uncheck the option to install recovery.
Click to expand...
Click to collapse
So... Do I bite the bullet, factory reset and......?
Sent from my A0001 using XDA Free mobile app
adamfoz said:
So... Do I bite the bullet, factory reset and......?
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
no flash twrp or any custom recovery in adb and then you can flash the root zip.
I'm following this guide for rooting http://forum.xda-developers.com/showthread.php?t=2788632 .
I'm assuming that I'm doing things ok to a point, as the CMD prompt is saying adb version is 1.0.32 but when i put the phone in fast boot, and type "fastboot devices" the phone will show up in the cmd prompt. Its when I "fastboot oem unlock" and"fastboot reboot", the phone will reboot as normal. No setting up of the phone. All my apps and settings are still there, indicating to me that something is wrong :/
I'm assuming that my drivers are ok otherwise I wouldn't be seeing the above in the cmd prompts but...
Can someone tell me if my mobile should show up in "my computer" ? it has in the past, but no longer does. and I'm wondering if this could have someing to do with my problems??
Thanks again..Foz
If your rooted, you have already unlocked the boot loader unless you relocked it. Did you? If not don't worry about unlock and flash custom recovery and flash supersu zip
I did have a rooted phone until I did an ota update. This lost my root and i have been trying to get root back, but I'm having no luck. Im guessing if I am still struggling tomorrow night, ill factory reset. I have recent back ups so...
Sent from my A0001 using Tapatalk
adamfoz said:
I did have a rooted phone until I did an ota update. This lost my root and i have been trying to get root back, but I'm having no luck. Im guessing if I am still struggling tomorrow night, ill factory reset. I have recent back ups so...
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
All you need to do is flash SuperSU again. It's normal to lose root during an OTA update.
EDIT: didn't read properly. Have you gotten TWRP to flash yet?
Transmitted via Bacon
Nope. As in post 12. Phones connecting to the pc, its not wiping any data etc after any commands for unlocking boot loader
Sent from my A0001 using XDA Free mobile app
adamfoz said:
Nope. As in post 12. Phones connecting to the pc, its not wiping any data etc after any commands for unlocking boot loader
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
Why are you trying to unlock the bootloader again though? Did you relock it manually at some point?
Transmitted via Bacon
timmaaa said:
Why are you trying to unlock the bootloader again though? Did you relock it manually at some point?
Transmitted via Bacon
Click to expand...
Click to collapse
I'm (wrongly) assuming bootloader needed unlocking again after the ota update because twrp would not install again. I assumed the whole phone needed all 3 processes to gain root again.
Sent from my A0001 using XDA Free mobile app
adamfoz said:
I'm (wrongly) assuming bootloader needed unlocking again after the ota update because twrp would not install again. I assumed the whole phone needed all 3 processes to gain root again.
Sent from my A0001 using XDA Free mobile app
Click to expand...
Click to collapse
The bootloader shouldn't lock again unless you do it yourself. The recovery (unnecessarily because you can uncheck the 'update cm recovery' option in Developer Options to keep your custom recovery) and root (no way around it) are lost during the OTA but the bootloader should remain unlocked. What response do you get when issuing the following command?
Code:
fastboot oem device-info
Please paste the results here.
Transmitted via Bacon
As soon as I'm home, I'll let you know.....
Thanks
Sent from my A0001 using XDA Free mobile app
Is there any way to root without using a pc like I did with my G3 using Stumproot?
Related
Hello all. I just unlocked my bootloader and rooted my phone, or so I thought. Somehow, I did not completely root my phone. Busybox installer would not load. I ran root checker and it said my root was not complete. My questio is, if I were to do a factory reset, would my bootloader relock? Thanks
quicksilver53 said:
Hello all. I just unlocked my bootloader and rooted my phone, or so I thought. Somehow, I did not completely root my phone. Busybox installer would not load. I ran root checker and it said my root was not complete. My questio is, if I were to do a factory reset, would my bootloader relock? Thanks
Click to expand...
Click to collapse
No it wouldn't. Does it say unlocked in purple? Can't remember the specific exploit directions. But you can flash twrp using "fastboot flash recovery twrp.IMG" (obviously change twrp.img to the name or hit tab) and flash a rooted ROM. Haven't done any of the exploits up here, but of you clicked on rooted in my SIG, its a great site you out. Skip to the part after unlocking the bootoader.
Sent from my Carbon-ize Evita using xda-developers app
Herc08 said:
No it wouldn't. Does it say unlocked in purple? Can't remember the specific exploit directions. But you can flash twrp using "fastboot flash recovery twrp.IMG" (obviously change twrp.img to the name or hit tab) and flash a rooted ROM. Haven't done any of the exploits up here, but of you clicked on rooted in my SIG, its a great site you out. Skip to the part after unlocking the bootoader.
Sent from my Carbon-ize Evita using xda-developers app
Click to expand...
Click to collapse
Yes. When I have it in bootloader mode, it had changed from locked to unlocked. Thanks for your help.
Did you install custom recovery (CWM or TWRP) and flash SuperSU or SU, or flash a rooted ROM. Because you need to do that to actually have root (after unlocking the bootloader).
redpoint73 said:
Did you install custom recovery (CWM or TWRP) and flash SuperSU or SU, or flash a rooted ROM. Because you need to do that to actually have root (after unlocking the bootloader).
Click to expand...
Click to collapse
That's right. When he said thanks, I thought he figured it out.
Sent from my Carbon-ize Evita using xda-developers app
Also, I believe the only thing that will relock the bootloader, is you relocking it yourself.
redpoint73 said:
Also, I believe the only thing that will relock the bootloader, is you relocking it yourself.
Click to expand...
Click to collapse
I am fairly certain that is correct. An RUU won't run with a bootloader unlocked unless you are S-OFF and still would not relock. nothing else would touch the bootloader.
I followed the instructions and slashed the recovery, twrp I think it was and I got stumped after there. I am relatively new to rooting. I unlocked both my N7 and N4 a week ago with Wugfresh's toolkit and that was relatively simple for and old guy like me. I will most likely have to go to his website and get complete instructions and try it again.
Sent from my Nexus 4 using xda app-developers app
quicksilver53 said:
I followed the instructions and slashed the recovery, twrp I think it was and I got stumped after there. I am relatively new to rooting. I unlocked both my N7 and N4 a week ago with Wugfresh's toolkit and that was relatively simple for and old guy like me. I will most likely have to go to his website and get complete instructions and try it again.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
well i can help you, i recommend going with twrp and flashing a SU zip file. this post is reserved, and will be back to edit...
Edit; Ok, so in this post is two files you need.
http://forum.xda-developers.com/attachment.php?attachmentid=1907931&d=1366808637
and http://download.chainfire.eu/310/SuperSU/UPDATE-SuperSU-v1.04.zip
Download both of these files.
Put UPDATE-SuperSU-v1.04.zip on the root on your SD card (basically transfer the zip to your phone)
I downloaded the 2.3.3 twrp img file, since that is the most stable for me. If you want to upgrade to 2.5, then be my guess, but others say it is a problem. i have flashed sense roms and aosp roms with no problems. also, pleae read both paragraphs before attempting to do something. if you do not understand, feel free to comment or pm me. i tried to make it as simple as possible.
So first off download the zip, and extract the folder to a simple location (desktop or c:\). i am going to assume you extracted it to c:\. open up a command prompt by going to Start and typing in "cmd" a black window should pop up. type in "cd c:\rootphone." you are already rooted, but it was already the name of my folder. anywho, turn your phone completely off, and go into the bootloader. i assume you know how to do this, since you were able to read off your hboot details. it is the white screen with colorful text. then select fastboot in red. once a usb connection is plugged in, it should turn to fastboot usb. now in the command prompt (black window on the pc), you need to type fastboot flash recovery openrecovery-twrp-2.3.3.0-evita.img (hint: you can type open and hit tab, and it will finish it for you). now you have twrp installed. now boot into recovery, and go tap on Install. find the UPDATE-SuperSU-v1.04.zip, tap it, and then slide to flash. your if successful, your phone should be rooted. go ahead hit reboot, and re-run root checker.
To anyone else (i.e. Venomtester or exad) if i have incorrect info, please let me know
Looks good to me lol. But a more simple method to open the command window is to download adb to desktop. Then all they have to do is open the folder and right-click somewhere away from the files and it will give the option to open command window here. That way they can put the images in the folder and never have to leave it. They tend to mess up hunting the folder down from windows cmd.
Sent from my HTC One X using xda premium
Venomtester said:
Looks good to me lol. But a more simple method to open the command window is to download adb to desktop. Then all they have to do is open the folder and right-click somewhere away from the files and it will give the option to open command window here. That way they can put the images in the folder and never have to leave it. They tend to mess up hunting the folder down from windows cmd.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
When I write guides, I write with assumptions. But I guess you are right.
Sent from my Carbon-ize Evita using xda-developers app
Thanks a lot for the info guys. I will have another go at it when I get home from work tonight.
Sent from my Nexus 4 using xda app-developers app
Well I thought it was a very good guide.
Sent from my HTC One X using xda premium
Venomtester said:
Well I thought it was a very good guide.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
Thanks again guys. I have tried several times since last night to get my phone into bootloader mode. I power it off and the push volume down and power and keep holding both. It starts up and the capacitive buttons flash as I get the quietly brilliant screen and the it just goes black with no flashing. I don't know why it will not go any further. I also get an error report every time. Any guggestions? I have tried to use the commands on the tool kit to get it into bootloader mode but no success.
quicksilver53 said:
Thanks again guys. I have tried several times since last night to get my phone into bootloader mode. I power it off and the push volume down and power and keep holding both. It starts up and the capacitive buttons flash as I get the quietly brilliant screen and the it just goes black with no flashing. I don't know why it will not go any further. I also get an error report every time. Any guggestions? I have tried to use the commands on the tool kit to get it into bootloader mode but no success.
Click to expand...
Click to collapse
Ok I got it into bootloader mode. I forgot to let go of the power buton when the screen went black.
OK just re do it again. Hold down power and volume down (or is it up? I get this confused with Samsung sometimes)
Sent from my Carbon-ize Evita using xda-developers app
Down...
Sent from my HTC One X using xda app-developers app
31ken31 said:
Down...
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Thanks. Figured that.
Sent from my Carbon-ize Evita using xda-developers app
I just got my m8 and want to s-off but I'm traveling and won't be able to figure that out until I'm back on my pc next week. The update keeps prompting me to take it. Is it safe to do so? Sorry if this was already answered trying to figure out the best way to browse with tapatalk.
I don't have root or anything yet...
Sent from my HTC6525LVW using Tapatalk
I used Firewater's method for permanent root, s-off and custom recovery. If I allow my phone to update will I mess things up or lose root?
Same boat here... s-off, permanent root, TWRP
The update to 1.55 downloaded but when I tried to let it install it just rebooted my phone into TWRP and that was it. Rebooted back to system and I'm still on the 1.12.605.11 software. Checking software update status shows "Result: Update Failed,410"
N00bs. Lol. You need a stock recovery to flash an OTA. Also, I am s-off and I had a flashback to a stock recovery to flash the OTA . Everything is still fine and then I flashed back to a custom recovery no problem
Sent from my HTC One M8
Totally a noob here, How do you flash to a stock recovery?
Sent from my HTC6525LVW using Tapatalk
You guys need the stock recovery in order to install the OTA. It won't work with a custom recovery, it'll just boot to the custom recovery and not do anything. You can install the OTA with s off and root but you still need the stock recovery. You install the stock recovery the same way as you did the custom. Adb -> flashboot flash recovery *path of recovery*.
http://www.megafileupload.com/en/file/520717/stockrecovery-img.html
There are also videos on YouTube on flashing recoveries to the m8 if you need more help.
Sent from my HTC6525LVW using Tapatalk
Justintoxicated said:
I just got my m8 and want to s-off but I'm traveling and won't be able to figure that out until I'm back on my pc next week. The update keeps prompting me to take it. Is it safe to do so? Sorry if this was already answered trying to figure out the best way to browse with tapatalk.
I don't have root or anything yet...
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
You can install the update, and when you have the chance you can s-off using the weaksauce/supersu/firewater method. I picked up a new M8 a couple nights ago and took the update, and afterwards did the temproot/firewater method and it worked just fine. Hope this helps.
I flashed stock recovery and tried the OTA and it failed twice. I can't seem to get it on my phone through any of the methods for some reason.
In order to install update, you need to have STOCK recovery and STOCK Rom....NOT debloated or with mods....STOCK.
Again, you need STOCK recovery using a STOCK Rom.
If you have modified the system in anyway, it WONT work until you put it back to STOCK.
Sent from my HTC6525LVW using xda app-developers app
^you can have bloatware frozen and it'll work, just can't be removed.
Sent from my HTC6525LVW
dadams312 said:
I flashed stock recovery and tried the OTA and it failed twice. I can't seem to get it on my phone through any of the methods for some reason.
Click to expand...
Click to collapse
z-man79 said:
Totally a noob here, How do you flash to a stock recovery?
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
KnightDavid said:
Same boat here... s-off, permanent root, TWRP
The update to 1.55 downloaded but when I tried to let it install it just rebooted my phone into TWRP and that was it. Rebooted back to system and I'm still on the 1.12.605.11 software. Checking software update status shows "Result: Update Failed,410"
Click to expand...
Click to collapse
z-man79 said:
I used Firewater's method for permanent root, s-off and custom recovery. If I allow my phone to update will I mess things up or lose root?
Click to expand...
Click to collapse
No need to take ota. Ota us our enemy. Lol. The ota has been pulled an you can simply flash the firmware an that's half of the ota an then flash a stock Rom based off 1.55 or install the backup that was posted of a pure stock 1.55 Rom. After those 2 things you will have the full ota. New radios everything.. flashing a stock recovery taking ota flashing back is not needed.
Sent from my HTC6525LVW using XDA Premium 4 mobile app
Thanks guys it was annoying having that update keep popping up and no real computer to lookup info or soff. As for getting updates after roming the phone usually just wait for authors to incorporate the updates. But I did not realize you can't have two recoveries like you can on Motorola phones which is good to know.
Sent from my HTC6525LVW using Tapatalk
New to android here.
I rooted the device with WeakSauce and use Firewater for S-Off. I didn't flash any custom recoveries. I did freeze some apps with Titanium Backup. If I do the OTA, 1) will it work? and 2) will it remove my root and/or s-off?
NoFanboy said:
You guys need the stock recovery in order to install the OTA. It won't work with a custom recovery, it'll just boot to the custom recovery and not do anything. You can install the OTA with s off and root but you still need the stock recovery. You install the stock recovery the same way as you did the custom. Adb -> flashboot flash recovery *path of recovery*.
megafileupload.com/en/file/520717/stockrecovery-img.html
Click to expand...
Click to collapse
For clarification, after flashing the stockrecovery.img you posted and installing the update, there should be no problem flashing back to CWM recovery after the fact?
Thank you for your help and your time!
skivvies said:
For clarification, after flashing the stockrecovery.img you posted and installing the update, there should be no problem flashing back to CWM recovery after the fact?
Thank you for your help and your time!
Click to expand...
Click to collapse
Nope there will be no problem.
Sent from my HTC6525LVW using Tapatalk
richii0207 said:
In order to install update, you need to have STOCK recovery and STOCK Rom....NOT debloated or with mods....STOCK.
Again, you need STOCK recovery using a STOCK Rom.
If you have modified the system in anyway, it WONT work until you put it back to STOCK.
Sent from my HTC6525LVW using xda app-developers app
Click to expand...
Click to collapse
All your big words confuse me...will it work with custom rom's and recoveries?
I don't remember ever having to have stock recovery and stock rom for my old DNA to take an update. Normally devs would update their rom with the updates and all we had to do was fastboot flash the new radio.
NoFanboy said:
You guys need the stock recovery in order to install the OTA. It won't work with a custom recovery, it'll just boot to the custom recovery and not do anything. You can install the OTA with s off and root but you still need the stock recovery. You install the stock recovery the same way as you did the custom. Adb -> flashboot flash recovery *path of recovery*.
http://www.megafileupload.com/en/file/520717/stockrecovery-img.html
There are also videos on YouTube on flashing recoveries to the m8 if you need more help.
Sent from my HTC6525LVW using Tapatalk
Click to expand...
Click to collapse
So I flash the file you linked to, thank you but when I try to get into recovery I get a red triangle with an exclamation point in it. Seemed pretty straight forward.
sfreemanoh said:
All your big words confuse me...will it work with custom rom's and recoveries?
Click to expand...
Click to collapse
Lol, I had to. I just know someone is going to start a thread saying "update won't work, it just boots into twrp"
Sent from my HTC6525LVW using xda app-developers app
z-man79 said:
So I flash the file you linked to, thank you but when I try to get into recovery I get a red triangle with an exclamation point in it. Seemed pretty straight forward.
Click to expand...
Click to collapse
Hold the volume up button and pressed the power button to get to the recovery menu.
Yesterday I managed to press install on the newest update, 4.4.4 on my Nexus 5. It was rooted and still is, but by installing this OTA it somehow made it crash. Now that I try to get into recovery mode I just get the android which is dead with an ! on it. It was rooted with Xposed and TWRP.
What do I do? Im on a Mac
OTA removed root replaces recovery. I'm amazed it managed to replace recovery whilst Xposed was installed. Anyway, seems like it did.
You must fastboot flash a custom recovery
Sent from my Nexus 5 using Tapatalk
rootSU said:
OTA removed root replaces recovery. I'm amazed it managed to replace recovery whilst Xposed was installed. Anyway, seems like it did.
You must fastboot flash a custom recovery
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I feel embarrassed to ask, but how do I do that on my Mac? When I rooted it I did it on my PC at home, now Im traveling with my Mac for work..
Thanks!
killhaug said:
I feel embarrassed to ask, but how do I do that on my Mac? When I rooted it I did it on my PC at home, now Im traveling with my Mac for work..
Thanks!
Click to expand...
Click to collapse
The same really. Install fastboot and use the "fastboot flash recovery /pathto/your/recovery.img" command
Sent from my Nexus 5 using Tapatalk
rootSU said:
The same really. Install fastboot and use the "fastboot flash recovery /pathto/your/recovery.img" command
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
I did this and now Im stuck in a TWRP loop, wont get into the system. I dont know what to do now, any inputs?
EDIT: Solved it. Thanks!
Is there any tool that will reinstall the stock rom on a Nexus 5 with LOCKED bootloader? Something like emergency reflash from LG Support Tool.
LG Support Tool? There's something LG Flashtool and that works.
albwh said:
Is there any tool that will reinstall the stock rom on a Nexus 5 with LOCKED bootloader? Something like emergency reflash from LG Support Tool.
Click to expand...
Click to collapse
If you have to reinstall the stock firmware why do you care? Just unlock the bootloader, you're going to lose everything anyway.
What situation are you in. There may be ways to save your data
Sent from my Nexus 5 using XDA Free mobile app
The ideea is that I want to root this phone with Towelroot and I've heard that if Google detects a change in the system you can't install any more OTA updates. If this is true, I want to find a method to reflash the stock so I cand get the updates.
albwh said:
The ideea is that I want to root this phone with Towelroot and I've heard that if Google detects a change in the system you can't install any more OTA updates. If this is true, I want to find a method to reflash the stock so I cand get the updates.
Click to expand...
Click to collapse
If you're rooted but otherwise completely stock, you should get OTA updates no problem.
albwh said:
The ideea is that I want to root this phone with Towelroot and I've heard that if Google detects a change in the system you can't install any more OTA updates. If this is true, I want to find a method to reflash the stock so I cand get the updates.
Click to expand...
Click to collapse
Well if you modify any system files you don't get the ota. Your best bet is to root and then flash a custom recovery with flashify and then flash a stock rom zip that will be created shortly after any updates come out. You can also unlock the bootloader without wiping data with boot unlocker after your rooted.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
Well if you modify any system files you don't get the ota. Your best bet is to root and then flash a custom recovery with flashify and then flash a stock rom zip that will be created shortly after any updates come out. You can also unlock the bootloader without wiping data with boot unlocker after your rooted.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
There's a whole sticky on returning to stock so you can get OTAs. </thread>
If you're able to flash the stock ROM, you should be past the point where you need to worry about being able to get any updates.
Yeah. I'd highly recommend just flashing a prerooted busybox stock ROM. You can always do a dirty flash over stock ROM and still keep data.
jd1639 said:
Well if you modify any system files you don't get the ota. Your best bet is to root and then flash a custom recovery with flashify and then flash a stock rom zip that will be created shortly after any updates come out. You can also unlock the bootloader without wiping data with boot unlocker after your rooted.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
You do get the OTA, but if you modify /system/ or something else, the OTA won't install.
It takes 10 minutes to return to stock for an OTA. Just do what you want with the phone now and enjoy!
The next OTA will be months from now. Return to stock then.
You dont need any tool. Download factory image and flash that by executing flash-all.bat (for windows, if you use linux execute flash-all.sh). Flash a custom recovery. Then remove hidden tampered flag by flashing tampered flag remover zip. Then flash stock recovery and lock bootloader by typing fastboot oem lock.
yashade2001 said:
You dont need any tool. Download factory image and flash that by executing flash-all.bat (for windows, if you use linux execute flash-all.sh). Flash a custom recovery. Then remove hidden tampered flag by flashing tampered flag remover zip. Then flash stock recovery and lock bootloader by typing fastboot oem lock.
Click to expand...
Click to collapse
You can do the last 2 steps using bootunlocker from play
Sent from my Nexus 5 using Tapatalk
rootSU said:
You can do the last 2 steps using bootunlocker from play
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Yes that is an awesome app.
yashade2001 said:
Yes that is an awesome app.
Click to expand...
Click to collapse
Yeah agreed. I use it to keep my bootloader locked but so I can unlock it without a wipe on the fly.
rootSU said:
Yeah agreed. I use it to keep my bootloader locked but so I can unlock it without a wipe on the fly.
Click to expand...
Click to collapse
Why do you keep your bootloader locked?
yashade2001 said:
Why do you keep your bootloader locked?
Click to expand...
Click to collapse
So no one can get my data
rootSU said:
So no one can get my data
Click to expand...
Click to collapse
How someone can get my data if i have a unlocked bootloader?
yashade2001 said:
How someone can get my data if i have a unlocked bootloader?
Click to expand...
Click to collapse
Locking the bootloader isn't enough on its own.
Android: adb pull data, MTP (Screen lock can prevent)
Custom recovery: adb pull data, flash zip to turn off android lock screen (Recovery lock can prevent)
Lock bootloader: Prevent replacing locked recovery with unlocked recovery,
Hello i was wondering if you could help me with something. My XT1548 just got an OTA update. And i tried updating too it, but my phone keeps restarting every 2 minutes into TWRP instead of updating
i am on lollipop 5.1.1 trying too get the latest OTA.
SpitFire727 said:
Hello i was wondering if you could help me with something. My XT1548 just got an OTA update. And i tried updating too it, but my phone keeps restarting every 2 minutes into TWRP instead of updating
i am on lollipop 5.1.1 trying too get the latest OTA.
Click to expand...
Click to collapse
When twrp starts, clear caches and reboot. Should be good to go, and don't accept ota again, you must be stock to take ota.
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
When twrp starts, clear caches and reboot. Should be good to go, and don't accept ota again, you must be stock to take ota.
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
So i unrooted VIA superSU
is the next step too install the stock rom?
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
SpitFire727 said:
So i unrooted VIA superSU
is the next step too install the stock rom?
http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Click to expand...
Click to collapse
Maybe... If you had installed Xposed or other root app, it's best to that, or restore your pre-rooted nandroid backup. Otherwise, if you didn't modify system, just fastboot flash stock recovery and take the ota.
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
Maybe... If you had installed Xposed or other root app, it's best to that, or restore your pre-rooted nandroid backup. Otherwise, if you didn't modify system, just fastboot flash stock recovery and take the ota.
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
i removed a bunch of bloatware. mostly sprint junk
SpitFire727 said:
i removed a bunch of bloatware. mostly sprint junk
Click to expand...
Click to collapse
Then an OTA may fail, depending on what the update script checks for. I would flash back to pure stock to be safe.
Sent from my Motorola XT1575 using XDA Labs
i don't have a pre rooted backup :/
SpitFire727 said:
i don't have a pre rooted backup :/
Click to expand...
Click to collapse
Then I would flash back to stock...
Sent from my Motorola XT1575 using XDA Labs
acejavelin said:
Then I would flash back to stock...
Sent from my Motorola XT1575 using XDA Labs
Click to expand...
Click to collapse
could you walk me through all the steps i need too take?
It's not complicated, get the image from this thread: http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Then use these instructions: http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
Well documented and established method, just follow the instructions.
moving discussion to Q&A..
acejavelin said:
It's not complicated, get the image from this thread: http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Then use these instructions: http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
Well documented and established method, just follow the instructions.
Click to expand...
Click to collapse
so i did all the steps, i updated too 6.1. but now i face a new problem, no devices are found in adb when in boot loader mode. it is detected while the phone is started up though.. in the progress of trying too fix this.
acejavelin said:
It's not complicated, get the image from this thread: http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639
Then use these instructions: http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
Well documented and established method, just follow the instructions.
Click to expand...
Click to collapse
so followed all the steps and am now on 6.1, but now i face a new challenge. my adb is not finding any devices while in boot loader but it detects it while the phone is fully booted up.
SpitFire727 said:
so followed all the steps and am now on 6.1, but now i face a new challenge. my adb is not finding any devices while in boot loader but it detects it while the phone is fully booted up.
Click to expand...
Click to collapse
You phone will never be detected with adb in the bootloader, that isn't what adb is intended for, but that is where you use fastboot.
Your situation is completely normal.
acejavelin said:
You phone will never be detected with adb in the bootloader, that isn't what adb is intended for, but that is where you use fastboot.
Your situation is completely normal.
Click to expand...
Click to collapse
oh okay so how too i install TWRP, its in the internal storage and the command fastboot boot twrp.img just says waiting for device
SpitFire727 said:
oh okay so how too i install TWRP, its in the internal storage and the command fastboot boot twrp.img just says waiting for device
Click to expand...
Click to collapse
The TWRP img file needs to be on the computer in the fastboot directory. Start the bootloader and type 'fastboot devices' to make sure the device is recognized, then 'fastboot boot twrp.img' (remember to use the actual filename in place of twrp.img)
Sent from my Motorola XT1575 using XDA Labs