Related
Hey guys I need to get my phone back to complete stock in order to warranty it. Now I'm fine with flashing the stock rom for the i9020a, what I need some help with is getting back to the stock recovery and re-locking the bootloader.
Currently I'm running CWM so that has to be replaced with the stock recovery, wondering how to go about this,
and I also need to re lock the bootloader so that the lovely little unlocked padlock disappears.
Any help or a link to a guide for would greatly appreciated.
First backup all data you need, sdcard and phone, since you're taking it in for warranty.
Have your stock image ready on the sdcard. Go into recovery and factory reset, format /system and format /boot. Now install the stock full rom.
Reboot the phone and skip through the setup. Now go back into recovery and make sure it is stock now, you'll see an android and exclamation mark. Now reboot again and connect to computer. Now on the computer issue:
fastboot oem lock
Now you should be ready.
Hi Guys,
So I unlocked my phone's bootloader, flashed ClockworkMod Touch Recovery and then tried to flash CM10.... something went wrong and now my phone is stuck on the HTC Logo with the red text that says "This build is for development purposes only......".
I have tried just about everything I have read about, and I am still just as screwed. Have I permanently bricked my phone?
Thanks for your help.
First for the One XL it is suggested you use TWRP and not CWM
You can get it here from their website .
It tells you how to fastboot flash it.
If you did an OTA to 2.20 or your device came with 2.20 you probably need to flash the boot.img /kernel
So in your CM10 zip, extract the boot image.
and use fastboot to flash the boot img with the command
fastboot flash boot boot.img
and that should help you out.
I also suggest reflashing the rom with TWRP just in case. Hope this helps.
Can adb see the phone?
FrustratedAndConfused said:
Hi Guys,
So I unlocked my phone's bootloader, flashed ClockworkMod Touch Recovery and then tried to flash CM10.... something went wrong and now my phone is stuck on the HTC Logo with the red text that says "This build is for development purposes only......".
I have tried just about everything I have read about, and I am still just as screwed. Have I permanently bricked my phone?
Thanks for your help.
Click to expand...
Click to collapse
This is the one xl correct, not the international on x?
If you can get anything on your screen, your phone isn't hard-bricked.
First, which phone do you have? ClockworkMod Touch Recovery does not work on the AT&T One X (One XL). If you tried flashing a ROM through it, it's not going to work and it's probably not booting up because the ROM is corrupted.
I would start with flashing a new recovery in adb. Use TWRP, because even the basic CWM is not supported for this phone and can cause issues.
Can you get into recovery? If so is the SD card mountable?
First time I flashed i had a similar issue where the SD couldn't mount. I ended up having to run the factory RUU after relocking the bootloader & then start again. I waited for a later nightly to come out. Also seems to go better if you flash a different rom first like viper.
NismoR31 said:
Can you get into recovery? If so is the SD card mountable?
Click to expand...
Click to collapse
Doesn't matter. He flashed the wrong recovery (not for our phone). There is not Touch CWM for our version.
i should really refresh pages before replying
Hi, I have a rooted nexus 5 which I want to sell, I really don't mind selling it rooted or not but all I want to do is factory reset it so none of my old data is on there. Can I just factory reset it in settings or Do I need to flash a stock image. It has the stock rom, with Super Su installed, and a custom recovery has also been installed. I also want to make sure the customer will be able to update the device normally. I have seen many ways to unroot the device and bring it back to stock, but I wanted to make sure which route to go as the last thing I want is the device to be bricked or anything like that. :'(
Factory reset should be enough. Make sure you haven't modified any system files and Xposed isn't installed and he should be able to update. I would go ahead and update the recovery to. Use TWRP as CWR is buggy as hell
#AndroidL
If it were me, I'd flash the stock firmware in fastboot, lock the bootloader and sell it like that.
Sent from my Nexus 5 using XDA Free mobile app
jd1639 said:
If it were me, I'd flash the stock firmware in fastboot, lock the bootloader and sell it like that.
Sent from my Nexus 5 using XDA Free mobile app
Click to expand...
Click to collapse
I would to. I would also use the SDK kit to securely wipe my device properly as well.
#AndroidL
Thanks for the replies, I think I'm just gonna flash the stock image via fastboot, but I was just thinking can't I just factory reset in TWRP?
josephlavagna said:
Thanks for the replies, I think I'm just gonna flash the stock image via fastboot, but I was just thinking can't I just factory reset in TWRP?
Click to expand...
Click to collapse
All that does is wipe /data and /cache. SuperSU binaries/apk are in /system.
josephlavagna said:
Hi, I have a rooted nexus 5 which I want to sell, I really don't mind selling it rooted or not but all I want to do is factory reset it so none of my old data is on there. Can I just factory reset it in settings or Do I need to flash a stock image. It has the stock rom, with Super Su installed, and a custom recovery has also been installed. I also want to make sure the customer will be able to update the device normally. I have seen many ways to unroot the device and bring it back to stock, but I wanted to make sure which route to go as the last thing I want is the device to be bricked or anything like that. :'(
Click to expand...
Click to collapse
There is more than one option to wipe your personal info and sell it rooted and hopefully I can add to the confusion. This is what I've done in the past when selling or giving away any device that the new owner wants to have rooted. I fastboot flash the system and boot images that are extracted from the factory image. Flashing the system image will make 100% sure that no modified system files will be lurking around trying to cause problems in the future. After flashing the system and boot images, while your device is in the bootloader screen, use the buttons to boot into recovery and flash the SuperSu installable zip that you will have downloaded to your device storage before flashing any images. After installing SuperSu while still in TWRP go to Wipe/Advanced Wipe and check the boxes for Cache, Internal Storage, Data and Dalvik Cache. Do NOT check System, you will have no OS to boot into if you do! If you're extra cautious/paranoid or have OCD (like myself) you can do a factory reset from inside your device settings after it boots up. TWRP has very recently been updated so that image can be flashed with the other images or beforehand using Flashify, if it needs to be updated. The above is just one of the ways to get to the same outcome, making sure there are no modified files in the system and that all personal info has been removed!
josephlavagna said:
Thanks for the replies, I think I'm just gonna flash the stock image via fastboot, but I was just thinking can't I just factory reset in TWRP?
Click to expand...
Click to collapse
You can use factory reset but if the seller want to recover your old file; its possible.
http://www.cnet.com/news/android-phone-wiping-fails-to-delete-personal-data/
Good luck!
I believe encrypting your device prior to doing a factory reset will prevent recovery of your files, but I haven't been able to confirm that.
Restola said:
I believe encrypting your device prior to doing a factory reset will prevent recovery of your files, but I haven't been able to confirm that.
Click to expand...
Click to collapse
Yes it would because the files left on the device after a factory reset will be inaccessible.
good thinking...
Possibly most efficient way:
fastboot oem lock (if currently unlocked)
boot into Android then go to Settings and turn on encryption
reboot to bootloader (or "adb reboot bootloader") and then fastboot oem unlock (this will absolutely erase everything on your device!)
boot into recovery and use ADB sideload to flash SuperSU (TWRP should support this)
(optional) relock bootloader?
That should result in a completely wiped, stock, rooted device with TWRP and unrecoverable personal data without having to reflash anything other than SuperSU?
chaosdefinesorder said:
Possibly most efficient way:
fastboot oem lock (if currently unlocked)
boot into Android then go to Settings and turn on encryption
reboot to bootloader (or "adb reboot bootloader") and then fastboot oem unlock (this will absolutely erase everything on your device!)
boot into recovery and use ADB sideload to flash SuperSU (TWRP should support this)
(optional) relock bootloader?
That should result in a completely wiped, stock, rooted device with TWRP and unrecoverable personal data without having to reflash anything other than SuperSU?
Click to expand...
Click to collapse
1. Encrypt.
2. Flash and wipe everything with fastboot (flash-all.bat/sh).
3. Relock bootloader
4. Sell.
Alternatively, use LG Flashtool and it'll automatically reflash/wipe + relock bootloader + reset tamper flag. Then it would be three steps.
Lethargy said:
1. Encrypt.
2. Flash and wipe everything with fastboot (flash-all.bat/sh).
3. Relock bootloader
4. Sell.
Alternatively, use LG Flashtool and it'll automatically reflash/wipe + relock bootloader + reset tamper flag. Then it would be three steps.
Click to expand...
Click to collapse
I was going for the route that did not require downloading the full ROM first...
chaosdefinesorder said:
I was going for the route that did not require downloading the full ROM first...
Click to expand...
Click to collapse
Quite a few of us always keep a set of factory images on a PC anyways
Edit: also, there are many people on custom ROMs or have modified /system. Factory reset within Android only wipes /data (internal storage included) and doesn't do anything else. Same with bootloader unlock. If you deleted an .apk in /system for example, where would a factory reset/bootloader unlock get it back from?
chaosdefinesorder said:
I was going for the route that did not require downloading the full ROM first...
Click to expand...
Click to collapse
To keep rooted but give a good clean up - you can
-download rooted rom.zip and flash via recovery.
-Lockock bootloader and reset flag via bootunlocker app.
-Encrypt.
-Wipe.
Easy. Can even flash a different recovery first although, if rooted, custom recovery is good idea. Still best to unroot if you ask me, which you can easily do via the superuser app..
-download rooted rom.zip and flash via recovery.
-Flash stock recovery zip
-Lockock bootloader and reset flag via bootunlocker app.
-Uroot via supersu
-Encrypt.
-Wipe.
Flashed “BETA-SuperSU-v2.66-20160103015024.zip”. System now stuck on "Warning Bootloader unlocked" screen. I can get to Android recovery. I did wipe cache but same condition exists. Is it safe to do a factory reset at this point?
Although I recovered by restoring a Nandroid backup, I am still curious if selecting factory reset from stock recovery would have worked, or is this not an advisable method for soft brick recovery?
MrTooPhone said:
Although I recovered by restoring a Nandroid backup, I am still curious if selecting factory reset from stock recovery would have worked, or is this not an advisable method for soft brick recovery?
Click to expand...
Click to collapse
Flash BETA-SuperSU-v2.62-3-20151211162651.zip in xt1550 moto g3. Done and working fine
MrTooPhone said:
Flashed “BETA-SuperSU-v2.66-20160103015024.zip”. System now stuck on "Warning Bootloader unlocked" screen. I can get to Android recovery. I did wipe cache but same condition exists. Is it safe to do a factory reset at this point?
Click to expand...
Click to collapse
First flash system firmware.. then flash TWRP recovery.. then Flash BETA-SuperSU-v2.62-3-20151211162651.zip SuperSU Package.. Done..
sieze.s said:
Flash BETA-SuperSU-v2.62-3-20151211162651.zip in xt1550 moto g3. Done and working fine
Click to expand...
Click to collapse
Maybe I did not use the best words to ask my question. Can you recover from a system stuck on "Warning Bootloader unlocked" screen by simply doing a factory reset?
Did the same thing
MrTooPhone said:
Flashed “BETA-SuperSU-v2.66-20160103015024.zip”. System now stuck on "Warning Bootloader unlocked" screen. I can get to Android recovery. I did wipe cache but same condition exists. Is it safe to do a factory reset at this point?
Click to expand...
Click to collapse
I did the same thing could someone help me? I updated to 6.0 a couple days ago (I just got the phone) and decided to unlock the bootloader. Everything worked fine. I have minimal ADB and fastboot set up and all the drivers are set up properly too.
I then decided to flash TWRP. I didn't check "Read Only". Everything seemed fine. I swiped to reboot and was told to install supersu so I did and then rebooted.
Now I can't get past the white "Warning Bootloader Unlocked" screen. I can access the bootloader and TWRP, I'm just not sure what exactly to do next.
I have a Moto G 2015 2GB on T-Mobile USA
dcalf94 said:
I then decided to flash TWRP. I didn't check "Read Only". Everything seemed fine. I swiped to reboot and was told to install supersu so I did and then rebooted.
Now I can't get past the white "Warning Bootloader Unlocked" screen. I can access the bootloader and TWRP, I'm just not sure what exactly to do next.
I have a Moto G 2015 2GB on T-Mobile USA
Click to expand...
Click to collapse
You should not have installed supersu. Not sure why that option exists.
MrTooPhone said:
You should not have installed supersu. Not sure why that option exists.
Click to expand...
Click to collapse
What can I do to fix it?
dcalf94 said:
What can I do to fix it?
Click to expand...
Click to collapse
Did you make a Nandroid backup before flashing SuperSU? If so, restore your backup and start again.
MrTooPhone said:
Did you make a Nandroid backup before flashing SuperSU? If so, restore your backup and start again.
Click to expand...
Click to collapse
I do not have a back-up :/ Is it still safe to flash the 5.1.1 stock firmware if I was already on 6.0 via OTA? I tried a factory reset in TWRP, but that did't work.
dcalf94 said:
I do not have a back-up :/ Is it still safe to flash the 5.1.1 stock firmware if I was already on 6.0 via OTA? I tried a factory reset in TWRP, but that did't work.
Click to expand...
Click to collapse
If you are going to reflash, why not 6.0 firmware?
Is flashing my only option since I have no back-up?
MrTooPhone said:
If you are going to reflash, why not 6.0 firmware?
Click to expand...
Click to collapse
I haven't been able to find the 6.0 stock firmware for it. only 5.1.1
If all I have to do is flash 6.0 stock firmware and my phone is fixed could I do it in TWRP? Like, just drag the firmware into my phone's download folder and just install in TWRP?
MrTooPhone said:
If you are going to reflash, why not 6.0 firmware?
Click to expand...
Click to collapse
Did you look at http://forum.xda-developers.com/2015-moto-g/general/index-moto-g-factory-firmware-images-t3169639 or http://firmware.center/firmware/Motorola/Moto G (3rd gen-2015)/Stock/
dcalf94 said:
I haven't been able to find the 6.0 stock firmware for it. only 5.1.1
If all I have to do is flash 6.0 stock firmware and my phone is fixed could I do it in TWRP? Like, just drag the firmware into my phone's download folder and just install in TWRP?
Click to expand...
Click to collapse
You also may want to look at http://forum.xda-developers.com/2015-moto-g/development/rom-stock-motorola-rom-collection-t3296964
MrTooPhone said:
Maybe I did not use the best words to ask my question. Can you recover from a system stuck on "Warning Bootloader unlocked" screen by simply doing a factory reset?
Click to expand...
Click to collapse
Yes you can.
Edit - My phone was also stuck at this screen only - "Warning Bootloader unlocked"
I also soft bricked my phone 3-4 days ago but got it back.
Follow below steps and you are good to go -
1. Download and install Motorola Moto Drivers
2. download stock firmware from http://forum.xda-developers.com/2015...mages-t3169639 for your Moto G3 model (in my case it was XT1550)
3. download TWRP from http://forum.xda-developers.com/devd...1051#downloads [ i used twrp-osprey-2.8.7-r5.img version ]
4. download SuperSU from http://forum.xda-developers.com/show...25&postcount=3 [make sure you download BETA-SuperSU-v2.62-3-20151211162651.zip version only else you'll again brick your phone]
Now as you have all required things to get your phone back, now follow below steps -
Now flash stock ROM, Instruction here -> http://forum.xda-developers.com/2015...ctory-t3187750
Now flash TWRP - fastboot flash recovery your_recovery_name_here.img
now start your phone (takes 15 minutes around)
now go to recovery and flash BETA-SuperSU-v2.62-3-20151211162651.zip and start your phone [ do not allow TWRP to root your phone when it asks you to root your phone just tap not now (or whatever i don't remember right now)]
Starting up phone now takes 25-30 minutes approx.
Rooted
[Don't brick and blame me , do it at your own risk ]
The point where things went wrong was that last screen where TWRP asks you if you want to root the phone - NEVER let it do that, ever, even after you properly root it the right way (which is manually flashing that specific version of SuperSU or a later version).
I've had instances where on a random reboot into TWRP - on a properly rooted Moto G3 - where that question screen comes up. It should not come up when the phone is actually rooted but I've seen it once or twice. Again, the point is: NEVER EVER let TWRP do it's own internal rooting process because that's what breaks things on the Moto G3.
- flash stock firmware complete
- go back and flash TWRP
- use TWRP to manually flash the SuperSU version (at least 2.62 beta which is what the Moto G3 running Marshmallow requires)
- make sure after that flash of SuperSU you do NOT use the TWRP option to root the device when you close out TWRP, ever
- flash a replacement logo so you don't see the bootloader is locked splash screen
That's about it.
I just unlocked BL. How long does it take to restart the phone from ADB recovery screen? Seems like forever.
guest_2011 said:
I just unlocked BL. How long does it take to restart the phone from ADB recovery screen? Seems like forever.
Click to expand...
Click to collapse
It is basically a factory reset. Not sure you need adb at this point.
MrTooPhone said:
It is basically a factory reset. Not sure you need adb at this point.
Click to expand...
Click to collapse
I kept holding pow button, it kept restarting back to the same BL unlocked message, then finally booted back to MM. Took a while i thought i bricked it.
guest_2011 said:
I kept holding pow button, it kept restarting back to the same BL unlocked message, then finally booted back to MM. Took a while i thought i bricked it.
Click to expand...
Click to collapse
same problem with me. almost an hour and the same page "BL Unlocked". how long did it take for your phone to spring back to life?
So, My phone was rooted and I unlocked the bootloader. I have relocked bootloader and flashed my stock recovery so I can update to Marshmallow. Here is the problem:
When the update downloads and verifies the phone usually reboots so it can download. The progress bar doesn't even finish and the phone opens the recovery which shows State 7 installation aborted. Running stock OS 5.0.1 Lollipop. Help is aprecciated
Not sure what process you used to re-lock your boot loader. A couple of things you can try: 1st you may not want to loose your data but you could try a factory reset. 2nd if factory reset doesn't work you could use RUU to set device back to factory check this thread here
Recovery errors?
HeckNoTechnO said:
Not sure what process you used to re-lock your boot loader. A couple of things you can try: 1st you may not want to loose your data but you could try a factory reset. 2nd if factory reset doesn't work you could use RUU to set device back to factory check this thread here
Click to expand...
Click to collapse
Quick last question, when I open the recovery itself, it shows some errors like bitmap error oem, and down on thr bottom it says something like CW files not found skipped CW installation. Do I still proceed with the factory reset because i dont wsnna end up bricking my phone? Thanks for the quick reply, aprecciate it.
DreamFantom said:
Quick last question, when I open the recovery itself, it shows some errors like bitmap error oem, and down on thr bottom it says something like CW files not found skipped CW installation. Do I still proceed with the factory reset because i dont wsnna end up bricking my phone? Thanks for the quick reply, aprecciate it.
Click to expand...
Click to collapse
I think in your situation to get stock recovery on your device you may want to use the RUU method.
Sent from my Nexus 6 using Tapatalk