CONTEXT: My phone no longer charges (USB port doesn't work), but I have insurance. VZW sent me a replacement phone and I need to send back the old phone after doing a factory reset. The phone won't factory reset and I need your help. I think this will be an easy one for you guys. Here is my sense of the problem. I rooted the phone when I got it right away right after it was released aprox 2.5 years ago. I downloaded the classic root files like Clockworkmod, Wanam Xposed, Titanium Backup, Busy Box Pro, ROM Manager, ROM Installer, ROM Toolbox Pro, Root Explorer, Super SU, ...etc. After that I never changed the ROM. So I still have OEM ROM with lots of app updates. I did change the recovery.img in order to use one of those apps. I think it was to use Clockworkmod. Anyways now when I go to factory reset the phone it says it is missing the recover.img file. My sense is if I put back that file on my phone in the right spot it will then allow me reset to stock. Does that sound right? If so how do I do that? If not what else should I try consider? Grateful for any help I can get! THANK YOU in advance.
Things are really dead around here as you can tell by the lack of responses, but to answer your question the only way to restore unrooted stock is by downloading the stock firmware and using ODIN. The recovery img file is in that firmware too. I suggest getting your USB port fixed or you are screwed. If you do that, then follow these steps:
Download stock firmware here: http://www.sammobile.com/firmwares/database/SM-N900V/
Download ODIN here: https://mega.nz/#!nZoThZ5a!TrPzLGDrtQJSmJfH8UkOFAkfc9wSLl_lPhrVusQoRJ8
After you unpack the zip files, turn off your phone. Then hit the power, home and volume down buttons all at the same time for download mode. Confirm by hitting volume up as instructed. Plug the phone into your PC and open ODIN. You should see the COM port open. Next select the AP option, then browse to the file you unzipped the firmware to. Double click and wait until the md5 is done being verified. Hit start and wait, it takes about 4 or 5 minutes. Once it's finished and the phone starts rebooting, unplug the phone and pull the battery (you don't want to let it boot all the way or you'll get FCs out the ying yang). Now replace the battery, boot into stock recovery by hitting power, home and volume up all at the same time. Recovery will come up and then do your factory reset. You should be good to go after that.
ArtfulDodger said:
Things are really dead around here as you can tell by the lack of responses, but to answer your question the only way to restore unrooted stock is by downloading the stock firmware and using ODIN. The recovery img file is in that firmware too. I suggest getting your USB port fixed or you are screwed. If you do that, then follow these steps:
After you unpack the zip files, turn off your phone. Then hit the power, home and volume down buttons all at the same time for download mode. Confirm by hitting volume up as instructed. Plug the phone into your PC and open ODIN. You should see the COM port open. Next select the AP option, then browse to the file you unzipped the firmware to. Double click and wait until the md5 is done being verified. Hit start and wait, it takes about 4 or 5 minutes. Once it's finished and the phone starts rebooting, unplug the phone and pull the battery (you don't want to let it boot all the way or you'll get FCs out the ying yang). Now replace the battery, boot into stock recovery by hitting power, home and volume up all at the same time. Recovery will come up and then do your factory reset. You should be good to go after that.
Click to expand...
Click to collapse
Thanks - is there any way to do this without the USB port? I can still get new files to the phone via the MicroSD card. Or use Root explorer to mess with all the files on the phone.
mozenter said:
Thanks - is there any way to do this without the USB port? I can still get new files to the phone via the MicroSD card. Or use Root explorer to mess with all the files on the phone.
Click to expand...
Click to collapse
Refer to this thread: http://forum.xda-developers.com/showthread.php?t=2426162. But keep in mind, your bootloader MUST be unlocked to use mobile ODIN. If you are on KK 4.3 & up, I think you might be SOL.
ArtfulDodger said:
Refer to this thread: http://forum.xda-developers.com/showthread.php?t=2426162. But keep in mind, your bootloader MUST be unlocked to use mobile ODIN. If you are on KK 4.3 & up, I think you might be SOL.
Click to expand...
Click to collapse
Thanks I apprecaite the effort! I tried Mobile Odin. I purchased Mobile Odin Pro, but it doesn't work with VZW variant of Galaxy Note 3. Any other ideas? Thanks again for all the help!
mozenter said:
Thanks I apprecaite the effort! I tried Mobile Odin. I purchased Mobile Odin Pro, but it doesn't work with VZW variant of Galaxy Note 3. Any other ideas? Thanks again for all the help!
Click to expand...
Click to collapse
Sorry, sounds like without that USB port you are stuck with that phone then unless you can get it repaired. Thanks for the update, I kind of wondered if anything got resolved. Good luck!
ArtfulDodger said:
Sorry, sounds like without that USB port you are stuck with that phone then unless you can get it repaired. Thanks for the update, I kind of wondered if anything got resolved. Good luck!
Click to expand...
Click to collapse
One last attempt to get this fixed. I really just need to know where the recovery imagine is located in the note 3. Here again is a quick summary of the issue. I also just posted in the CWD thread.
"I have a Galaxy Note 3. I successfully put CWD on it when I purchased it several years ago. The USB port no longer charges the phone. I have insurance with VZW, but I need to send the phone back in stock. I can't put the phone back in stock because I have the CWD recovery image is in there. I recall I left the old recovery image on the phone and just changed the extension. So all I need to do to fix the phone is go back into the folder where the recovery image is and delete the CWD image and change original image extension back to its original form (which I think is IMG). The problem is I don't where on the phone these recovery images are. Can anyone help me with this situation? Thanks!!!"
mozenter said:
One last attempt to get this fixed. I really just need to know where the recovery imagine is located in the note 3. Here again is a quick summary of the issue. I also just posted in the CWD thread.
"I have a Galaxy Note 3. I successfully put CWD on it when I purchased it several years ago. The USB port no longer charges the phone. I have insurance with VZW, but I need to send the phone back in stock. I can't put the phone back in stock because I have the CWD recovery image is in there. I recall I left the old recovery image on the phone and just changed the extension. So all I need to do to fix the phone is go back into the folder where the recovery image is and delete the CWD image and change original image extension back to its original form (which I think is IMG). The problem is I don't where on the phone these recovery images are. Can anyone help me with this situation? Thanks!!!"
Click to expand...
Click to collapse
The recovery image is the recovery partition and you have overwritten it. You MAY be able to dig an image out of a firmware such as founf on sammobile but you still need a way to flash it. Without an unlocked bootloader or USB port.. I believe you're out of luck. You should simply send the phone back to VZW... I seriously doubt the shop it really goes to cares if it's stock or not.
Sent from my SM-N900V using Tapatalk
I'm sorta confused.
If it was rooted a few years ago & it was a retail device, a "true" replacement recovery (e.g. CWM) wouldn't boot because of the Samsung signing checks. This isn't a Developer Edition device, is it?
If it had SafeStrap installed, then:
- that already comes with a pseudo-recovery which is a mod of TWRP.
- the whole thing boots out of /system using the stock boot partition, and all it's magic happens inside of /system (with some loopback blobs for the non-stock slots stored in /data)
Does the OP know that a "factory reset" is an Android misnomer? There is no "resetting" back to factory of a device which has had customization of the /system partition. That has to be done either manually or through restoration of backups. The android "Factory Reset" only wipes the /data file system. It doesn't magically repair random customizations to /system, and that's what causes the "Custom" icon during boot.
About the only way I can think that the OP can resolve this is if he happens to have a Safestrap (pseudo-) TWRP backup of the stock slot. I guess the approach would be to:
- get the correct release "recovery.img" file out of the Odin Stock tarball, and "dd" it to the recovery partition ( mmcblk0p15 on the SM-N900V)
- restore the original, virginal "stock slot" backup onto the stock slot from the Safestrap+TWRP backup
- make sure to set the active slot to the stock slot
- reboot, go back into Safestrap recovery and:
- delete all other slots
- uninstall Safestrap.
This of course would only be feasible if the stock slot backup was taken immediately after installation of SafeStrap, so it's uninstall would restore /system to approximately the same condition as Stock. Maybe after running that ROM for a little bit the TIMA attribution would revert the "Custom" status indicator. It might even allow a download of an OTA.
There is another method of restoring to stock without USB that I can think of, but it would involve the bootloader unlock and booting a real (true) custom recovery, which would blow the Knox Warranty bit, so - given the OP's desires - I don't see much point in it.
donc113's comments should be considered as well: what is the chance that the warranty returns department is going to "go all CSI" on your returned phone? They probably have to deal with hundreds of dead phones per day. I suppose it depends a bit on luck and who is doing the warranty returns, but there have been more than one person on XDA report "I just returned the phone in it's trashed state and didn't bother to clean anything up, and no complaints."
good luck
donc113 said:
The recovery image is the recovery partition and you have overwritten it. You MAY be able to dig an image out of a firmware such as founf on sammobile but you still need a way to flash it. Without an unlocked bootloader or USB port.. I believe you're out of luck. You should simply send the phone back to VZW... I seriously doubt the shop it really goes to cares if it's stock or not. Sent from my SM-N900V using Tapatalk
Click to expand...
Click to collapse
I have an unlocked bootloader, but no USB port. So any ideas you have would greatly be apprecaited. VZW cares a lot. It will cost me $300 if I can't fix it.
mozenter said:
I have an unlocked bootloader, but no USB port. So any ideas you have would greatly be apprecaited. VZW cares a lot. It will cost me $300 if I can't fix it.
Click to expand...
Click to collapse
Did you unlock the bootloader or is that the way it came? Since you put CWM on it a long time ago... I would think that it's a developer edition and if so... It will be engraved inside with "Developer Edition" under the battery.
If it is a developer edition.... To the best of MY knowledge (i certainly could be wrong) Verizon never sold them... Only Samsung did... Thus Verizon never had a warranty on it.
But, no matter what version it is, since you loaded a non VZW recovery...you can not put back 100% to stock because the "warranty fuse" is blown and can not be reset.
I presume you have tried Odin to flash a stock firmware load that includes stock recovery but that requires the USB port be working (but doesn't require the charge circuit to work).
Beyond Odin... I have no other ideas.
Sent from my SM-N900V using Tapatalk
mozenter said:
I have an unlocked bootloader, but no USB port. So any ideas you have would greatly be apprecaited. VZW cares a lot. It will cost me $300 if I can't fix it.
Click to expand...
Click to collapse
Read this all the way through - twice at a minimum. You should understand how and why every step works before you begin. You should also verify md5 signatures of any files transferred around from place to place. (busybox and twrp both have "md5sum" command). You know - compute the MD5's after extracting them from the Odin archives, and then verify the same md5 sigs after you move/copy them to the phone /sdcard
Your idea that a "factory reset" with the stock recovery alone is going to return your phone back to factory stock is not sound.
You can rewrite the /system partition by booting into a custom recovery and using one other small trick*. If you were to then also overwrite the recovery partition with the stock recovery in the same (custom recovery boot) session, you would be able to:
1) boot into the stock recovery and
2) use the stock recovery (and a stock /system) to perform a factory reset.
This would give you a completely stock phone that has been factory reset, but with one small flaw: that your Knox warranty flag was blown to 0x1. (From everything you've said we think it is already blown, though)
twrp-3.0.2-0-hltevzw-4.3.img dd'ed into the recovery partition will let you do these operations via a terminal command session from the screen of the phone. No USB port needed, no ADB needed. All you will need to do is get the .img files onto the phone, either with a SDcard or wirelessly on a LAN/dropbox, etc.
0) Get the Stock Odin Tarball corresponding to your (rooted) ROM release (e.g. sammobile.com) ; use "tar" or 7-zip to extract "recovery.img" and "system.img" from this tarball.
1) Download twrp-3.0.2-0-hltevzw-4.3.img from twrp.me and get it onto your /sdcard (internal)
2) Get the stock "recovery.img" file (from the Odin tarball) onto your phone's /sdcard
*3) Convert the "system.img" file (from the Odin tarball) into a non-sparse system image file via the "simg2img" command, e.g.
<Unix-prompt>$ simg2img system.img system-nonsparse.img
I don't know if the Windows version of Google/Android developer tools has the "simg2img" tool; if not you are going to have to do this in a Linux VM (e.g. Ubuntu).
4) Get the latter file ("system-nonsparse.img") onto your phone /sdcard
5) From a root shell (in your current rooted ROM, use a terminal emulator and type "su" to get a root prompt)
dd if=/sdcard/twrp-3.0.2-0-hltevzw-4.3.img bs=2048 of=/dev/block/mmcblk0p15
this installs the custom TWRP recovery to your recovery partition
6) Boot into the TWRP recovery. Using Advanced->Terminal in TWRP, then:
7) dd if=/sdcard/recovery.img bs=2048 of=/dev/block/mmcblk0p15
(this step puts the stock recovery back onto the phone)
8) dd if=/sdcard/system-nonsparse.img bs=2048 of=/dev/block/mmcblk0p23
(this step puts the full stock /system back onto the phone)
9) Do a "reboot recovery" in TWRP. This will put you into the stock recovery, from which you can do a full factory wipe.
Voila! Factory Firmware and wiped - but with a blown Knox Warranty flag.
* the "one other small trick" is to convert the "system.img" file found in the stock Odin tarball to a non-sparse image using the Android tool "simg2img". Normally this unpacking job is handled by the bootloader when Odin is uploading the (sparse) system.img file to the phone, but you would be putting system.img back onto the phone by raw-writing it with "dd" the same way you would manually flash a recovery image to the recovery partition (using "dd").
The thing is, based on everything you have said so far, your phone already has a blown Knox Warranty flag. (Either that or you had a Developer Edition phone, or are confused about the difference between a true custom recovery and a fake one that lives inside safestrap). But what the heck, if that's the case, at least the phone will look fully stock if it is booted normally, and that's at least a little bit of an improvement.
This won't fix the Knox Warranty fuse; the only thing it will fix is the appearance of the "Custom" icon during booting. (Getting this to go away might even require booting the fully reset stock ROM and letting it run for a while as well so that the stock attribution processes can complete).
If you do this, you have to understand the whole process all the way through, as you will only have one chance at it. As soon as you have re-written the /system partition and put the stock recovery back on the phone, root is gone at that point. (Additionally note that step 8 CAN NOT be accomplished with the normal ROM booted - it can only be done from a custom recovery. You will lock up the system and the write will fail if you try it from the "regular" ROM.)
good luck.
bftb0 said:
Read this all the way through - twice at a minimum. You should understand how and why every step works before you begin. You should also verify md5 signatures of any files transferred around from place to place. (busybox and twrp both have "md5sum" command). You know - compute the MD5's after extracting them from the Odin archives, and then verify the same md5 sigs after you move/copy them to the phone /sdcard
Your idea that a "factory reset" with the stock recovery alone is going to return your phone back to factory stock is not sound.
You can rewrite the /system partition by booting into a custom recovery and using one other small trick*. If you were to then also overwrite the recovery partition with the stock recovery in the same (custom recovery boot) session, you would be able to:
1) boot into the stock recovery and
2) use the stock recovery (and a stock /system) to perform a factory reset.
This would give you a completely stock phone that has been factory reset, but with one small flaw: that your Knox warranty flag was blown to 0x1. (From everything you've said we think it is already blown, though)
twrp-3.0.2-0-hltevzw-4.3.img dd'ed into the recovery partition will let you do these operations via a terminal command session from the screen of the phone. No USB port needed, no ADB needed. All you will need to do is get the .img files onto the phone, either with a SDcard or wirelessly on a LAN/dropbox, etc.
0) Get the Stock Odin Tarball corresponding to your (rooted) ROM release (e.g. sammobile.com) ; use "tar" or 7-zip to extract "recovery.img" and "system.img" from this tarball.
1) Download twrp-3.0.2-0-hltevzw-4.3.img from twrp.me and get it onto your /sdcard (internal)
2) Get the stock "recovery.img" file (from the Odin tarball) onto your phone's /sdcard
*3) Convert the "system.img" file (from the Odin tarball) into a non-sparse system image file via the "simg2img" command, e.g.
<Unix-prompt>$ simg2img system.img system-nonsparse.img
I don't know if the Windows version of Google/Android developer tools has the "simg2img" tool; if not you are going to have to do this in a Linux VM (e.g. Ubuntu).
4) Get the latter file ("system-nonsparse.img") onto your phone /sdcard
5) From a root shell (in your current rooted ROM, use a terminal emulator and type "su" to get a root prompt)
dd if=/sdcard/twrp-3.0.2-0-hltevzw-4.3.img bs=2048 of=/dev/block/mmcblk0p15
this installs the custom TWRP recovery to your recovery partition
6) Boot into the TWRP recovery. Using Advanced->Terminal in TWRP, then:
7) dd if=/sdcard/recovery.img bs=2048 of=/dev/block/mmcblk0p15
(this step puts the stock recovery back onto the phone)
8) dd if=/sdcard/system-nonsparse.img bs=2048 of=/dev/block/mmcblk0p23
(this step puts the full stock /system back onto the phone)
9) Do a "reboot recovery" in TWRP. This will put you into the stock recovery, from which you can do a full factory wipe.
Voila! Factory Firmware and wiped - but with a blown Knox Warranty flag.
* the "one other small trick" is to convert the "system.img" file found in the stock Odin tarball to a non-sparse image using the Android tool "simg2img". Normally this unpacking job is handled by the bootloader when Odin is uploading the (sparse) system.img file to the phone, but you would be putting system.img back onto the phone by raw-writing it with "dd" the same way you would manually flash a recovery image to the recovery partition (using "dd").
The thing is, based on everything you have said so far, your phone already has a blown Knox Warranty flag. (Either that or you had a Developer Edition phone, or are confused about the difference between a true custom recovery and a fake one that lives inside safestrap). But what the heck, if that's the case, at least the phone will look fully stock if it is booted normally, and that's at least a little bit of an improvement.
This won't fix the Knox Warranty fuse; the only thing it will fix is the appearance of the "Custom" icon during booting. (Getting this to go away might even require booting the fully reset stock ROM and letting it run for a while as well so that the stock attribution processes can complete).
If you do this, you have to understand the whole process all the way through, as you will only have one chance at it. As soon as you have re-written the /system partition and put the stock recovery back on the phone, root is gone at that point. (Additionally note that step 8 CAN NOT be accomplished with the normal ROM booted - it can only be done from a custom recovery. You will lock up the system and the write will fail if you try it from the "regular" ROM.)
good luck.
Click to expand...
Click to collapse
Thanks you rock. I REALLY appreciate the effort. I fully realize that Knox won't be fixed. This is NOT a developer phone. These instructions a little over my head as I'm not that experienced with custom ROMs. I have really only dabbled a little bit with my last few phones.
mozenter said:
Thanks you rock. I REALLY appreciate the effort. I fully realize that Knox won't be fixed. This is NOT a developer phone. These instructions a little over my head as I'm not that experienced with custom ROMs. I have really only dabbled a little bit with my last few phones.
Click to expand...
Click to collapse
There is a possibility... That there is a script called install_recovery.sh or install_original_recovery.sh in your /system/etc directory. You must have root to execute them IF they even exist.
It depends on when and how CWD was installed.
Sent from my SM-N900V using Tapatalk
Related
Hello. I'm really new to the g1, I got it just two weeks ago, and right now I have JFv1.50 ADP1.5 installed right now. I'm not familiar with many of the technical terms, but I'm starting to understand everything.
I went through the root process, trying to follow some guide using a root.apk application to download/ install the right files, but it bricked my phone. I was able to manually get it to JFv1.50 ADP1.5 later on though.
Now my problem is that I believe I still have the normal recovery image on the phone. In recovery mode there is a picture of an exclamation mark in a triangle.
So I figured I'd go try to use JF's 1.43 recovery image. I put the zip on my SD card and renamed it update.zip. When I go into recovery mode now, though, and press ALT+S, I see the installation/ update bar pop up for like 3 seconds, enough for the orange progress bar to move a few millimeters, and then it just stops. No error message or anything.
I tried installing the test keys recovery image also, but it didn't work at all.
I really need JF's recovery image though, so I can make backups etc.
I've searched for this, but the closest problem I can see is this one:
http://forum.xda-developers.com/archive/index.php/t-505950.html
But for me, I don't even get an error message when using the update.zip...
Sorry for my lack of technical knowledge here, but try to bear with me
Thanks for any help you can give me!
The cooked roms are signed with testkeys, so the original recovery mode will refuse to flash them. You'll have to get the recovery image modified by JF and flash it. The latest version is included in JF v1.43. You can find recovery.img in a folder called data in that zip.
Copy it to your sdcard or adb push it to somewhere on the phone. Then type these commands on the phone:
su
flash_image recovery /path/to/recovery.img
You must have root in order to do this. Alternatively, you can push the file to /system and the init script will flash it for you the next time you boot.
billc.cn said:
The cooked roms are signed with testkeys, so the original recovery mode will refuse to flash them. You'll have to get the recovery image modified by JF and flash it. The latest version is included in JF v1.43. You can find recovery.img in a folder called data in that zip.
Copy it to your sdcard or adb push it to somewhere on the phone. Then type these commands on the phone:
su
flash_image recovery /path/to/recovery.img
You must have root in order to do this. Alternatively, you can push the file to /system and the init script will flash it for you the next time you boot.
Click to expand...
Click to collapse
Thanks so much! I couldn't figure this out until now. It's working perfectly now.
Feel free to close this thread. Thanks again
Rooting and updating your MotoActv is about to get significantly easier! No more waiting games for developers to update their ROMs or tools when Motorola pushes a new OTA; now you can do it yourself! I honestly have not seen these types of files ANYWHERE else, so I had to create these myself (with quite a bit of help from [mbm]). But enough blabbing, here are the files and how to use them:
(Note: all these methods assume we have full fastboot access! -- Which we still have at this point)
- Stock Images:
These are not just mere update.zips that you might be accustomed to elsewhere in Android. Nor are these mere fxzs that you might be accustomed to elsewhere with newer Motorola devices. They are in fact both and more. There are 3 main ways to flash these files onto your device, giving you options based on what OS you run and how comfortable you are flashing files to your device.
1) FXZ:
- Operating System: Windows
- Requires: RSD Lite with FXZ Support
- Instructions: Simply load up the file as any standard fxz (it is very straight-forward)
2) Recovery:
- Operating System: Anything that can mount your device
- Requires: The ability to get into recovery
- Instructions: Place the file on the sdcard, boot into recovery, flash as normal
- Note: Recovery does not wipe your device, it is suggested that you do so before flashing stock images
3) Fastboot:
- Operating System: Windows/Linux/Mac
- Instructions (Windows): Unpack the zip, run flash-all.bat (if it fails, run as administrator)
- Instructions (Linux/Mac): Unpack the zip, run flash-all.sh (it should already have proper permissions)
Miscellaneous Images:
These miscellaneous images are nothing you haven't seen before at this point, but their purposes are new, so they too require explanation.
1) AnyRoot:
AnyRoot is based on koush's AnyKernel in the sense that it unpacks and repacks the boot.img on the fly. However, as the name suggests, AnyKernel is meant for kernels, while AnyRoot, actually roots the device on the fly. This will work on any MotoActv device. It is flashed as a normal update.zip and everything is done in the background so you won't noticed much. However, for ease of access, the stock and rooted boot.img is exported to your sdcard in /sdcard/recovery/. Also note, that if you happen to flash AnyRoot over an already rooted device, nothing will happen as it has built-in error checking.
2) rebootRecovery:
rebootRecovery is another fxz type zip, the same as the stock and rooted images, except it can't be flashed in recovery (would be a little redundant don't you think?). This flashes a specially made misc.img by [mbm] that tells the device to reboot into recovery from boot. This means you can flash AnyRoot on any stock device.
How Tos / FAQs:
Now that you know what the files do, I can explain in short steps how to use these files to get what you want:
1) How to Return the Device to Stock?
- flash a stock image using any of the 3 methods
- you can now update via Motocast if you so wish
2) How to Root a Stock Device?
- update your device via Motocast to the latest version (suggested)
- place AnyRoot on your sdcard
- boot into fastboot, and flash rebootRecovery using either of the 2 methods
- flash AnyRoot in recovery
- reboot
3) How do I update my Rooted Device?
- flash a stock image using any of the 3 methods
- update your device via Motocast to the latest version
- place AnyRoot on your sdcard
- boot into fastboot, and flash rebootRecovery using either of the 2 methods
- flash AnyRoot in recovery
- reboot
Q: After using rebootRecovery I can't get out of recovery!?
A: You are using an old recovery that doesn't clear the 'reboot-recovery' command; use the newer recovery: https://dl.dropbox.com/u/5849675/android/f100/CWMR5x_F100_recoveryB2.img
Q: What do these ROM offer over other custom ROMs?
A: Nothing, they are simply stock images, but you can upgrade with them.
Q: How much battery should I have when I flash?
A: Performing any kind of these flashes will drain at least 10% of your battery, I wouldn't suggest you flash below 60% ESPECIALLY IF YOU FLASH rebootRecovery!
Q: What happens if I flash a 16gb zip on my 8gb or visa-versa?
A: Don't freak, it will still boot, but it's not the best thing in the world to do, just go back and flash the correct model zip.
Q: Can I extract the images from your zips and flash them my own way?
A: yep (couldn't really think of anything else to say)
Q: I manually flashed the stock-boot.img from AnyRoot, and now I can't update. Why?!
A: The boot.imgs need to be truncated before they can be flashed to correctly work with Motorola's updates, just use the stock images.
Q: What's next?
A: HyprActv -- What's this?
Stock Images (w/ md5sums):
8gb-NA: https://dl.dropbox.com/u/5849675/android/f100/MA_1710_8GB_NA.zip (5e228bf56a67aced012c8cbb2d7f7c76)
16gb-NA: https://dl.dropbox.com/u/5849675/android/f100/MA_1710_16GB_NA.zip (21b067dc629f7ccd18b43799d8d5fb17)
8gb-EU: https://dl.dropbox.com/u/5849675/android/f100/MA_1710_8GB_EU.zip (5b79a46d87728303fc2c920eec71c2e8)
Miscellaneous Images (w/ md5sums:
AnyRoot: https://dl.dropbox.com/u/5849675/android/f100/MA_AnyRoot.zip (2f867b006da42865ef861094db0eb6e6)
Reboot Recovery: https://dl.dropbox.com/u/5849675/android/f100/MA_RebootRecovery.zip (1623c9c61462db9bb20b55bc8f1144aa)
Mirror (thanks Iownox!): http://www.androtransfer.com/?developer=lownox&folder=MotoACTV
This is Reserved.
I rooted and flashed in recovery (the stock 4.55.97 and the the rooted version 4.55.97) and I stay on 4.55.78 no matter what! The flashes go through successfully... But nothing has changed and the System version still says 4.55.78... But like I said, the flashes both completed! I did a factory reset... and the updater-script wipes system, so what could be my issue?
Moose8106 said:
I rooted and flashed in recovery (the stock 4.55.97 and the the rooted version 4.55.97) and I stay on 4.55.78 no matter what! The flashes go through successfully... But nothing has changed and the System version still says 4.55.78... But like I said, the flashes both completed! I did a factory reset... and the updater-script wipes system, so what could be my issue?
Click to expand...
Click to collapse
It sounds like you flashed that old boot.img. Do you have the battery percentage in the status bar? According to TheEndGame7 that is another surefire way to tell if you are on 4.55.97, if you used any of the root tools, it's possible that they automatically flash the old boot.img.
CEnnis91 said:
It sounds like you flashed that old boot.img. Do you have the battery percentage in the status bar? According to TheEndGame7 that is another surefire way to tell if you are on 4.55.97, if you used any of the root tools, it's possible that they automatically flash the old boot.img.
Click to expand...
Click to collapse
I think I did flash the old boot.img (root tools :O ). I'll try flashing the modified boot img again. Thanks! I had no idea the root tool took me back to the old boot img
Moose8106 said:
I think I did flash the old boot.img (root tools :O ). I'll try flashing the modified boot img again. Thanks! I had no idea the root tool took me back to the old boot img
Click to expand...
Click to collapse
Yes, any and all tools that exist so far will need to be updated.
I wiped data / cache and used recovery (b) to install the rooted-4.55.97 zip and didn't have any luck either. I did not use the root tools to flash. Also wiped dalvik cache after and fastboot -w for fun.
innovatelife said:
I wiped data / cache and used recovery (b) to install the rooted-4.55.97 zip and didn't have any luck either. I did not use the root tools to flash. Also wiped dalvik cache after and fastboot -w for fun.
Click to expand...
Click to collapse
Did you end up doing any restore of some kind after you flashed?
Update
There are "new" instructions that might fix the issue where the rooted 4.55.97 appears to not flash. Simply wipe the boot.img image before you flash. And don't use the root tools until they are updated.
Also, if you have success, please post it. Usually "Thanks, it works" is annoying, but in this case where I don't have the device, I need to make sure this is working on some level.
I formated everything from recovery, now I got stuck with Moto logo with no animation when it starts, how to get out of this?
NA
Is there any mirrors for the download of these roms? the dropbox links are down
NORCALkID said:
Is there any mirrors for the download of these roms? the dropbox links are down
Click to expand...
Click to collapse
They were pulled, they're not working. There has been some form of mis-communication when I did my testing. I am not working on these until I can get the device from utkanos. Check Update 2, in the initial post.
Success
CEnnis91
I was lucky the second time, first time I succeeded to upgrade to rooted 4.55.97 but for some reason I didn't get the battery percentage on the status bar but all other issues are OK and status indicated version number 4.55.97, I repeated flash from recovery but after wiping and remounting all folders, this time for stock 4.55.97
Now I'm on stock 4.55.97 with battery percent on status bar and syncing from my mac.
thanks CEnnis91
NA
I went into recovery>mounts, and didn't see any wipe for boot. I took a shot at system since I had already wiped cache and data. Didn't seem to help either. Tried 'fastboot erase boot" and re-flashed. No go. Couldn't start back up the device at all. Tried flashing the latest rooted image using "fastboot flash boot boot.img". No go.
I messed around trying to get the device to boot back up for a while, but it won't even charge right. Only charges long enough to kick off the Motorola 'M', and that is it. On attempts at loading fastboot, I just keep getting an error saying that the battery is low. I know I can only blame myself for this. No fastboot access and no adb access. All attempts at resetting the device have failed.
Before I attempted all of this, my battery was full. Unfortunately, wouldn't charge anymore even plugged into the wall. Any ideas?
Hopefully nobody else makes my mistake.
Man I can't wait till this is perfect, you guys are fricken awesome. I raped your thanks buttons op lol
MoPhoACTV Initiative
Will be working on this tonight. I just found out how to make the flash script clear cache and dalvik for you, pre-install. That'll probably save some headache, but it works only in edify format. Not sure what the stock recovery uses...
Anyways, I'm home!
ClearD said:
Will be working on this tonight. I just found out how to make the flash script clear cache and dalvik for you, pre-install. That'll probably save some headache, but it works only in edify format. Not sure what the stock recovery uses...
Anyways, I'm home!
Click to expand...
Click to collapse
All recoveries will now use edify, amend is old and depreciated, you will only find that on old devices.
Corrupt Kernel...
innovatelife said:
I went into recovery>mounts, and didn't see any wipe for boot. I took a shot at system since I had already wiped cache and data. Didn't seem to help either. Tried 'fastboot erase boot" and re-flashed. No go. Couldn't start back up the device at all. Tried flashing the latest rooted image using "fastboot flash boot boot.img". No go.
I messed around trying to get the device to boot back up for a while, but it won't even charge right. Only charges long enough to kick off the Motorola 'M', and that is it. On attempts at loading fastboot, I just keep getting an error saying that the battery is low. I know I can only blame myself for this. No fastboot access and no adb access. All attempts at resetting the device have failed.
Before I attempted all of this, my battery was full. Unfortunately, wouldn't charge anymore even plugged into the wall. Any ideas?
Hopefully nobody else makes my mistake.
Click to expand...
Click to collapse
This is a classical case of a corrupt Kernel. Not that the images are corrupt, but somewhere along your update, your boot.img did not install the kernel properly and now you have a broken power manager within kernel.
What I would do is the following:
Hook your watch to the charger and let the M sign show up.
Even if it hangs on the M, leave your watch hooked over night.
Try downloading an older image and use fastboot to erase everything and then flash everything back again. This should return your watch to a working state again.
You may then choose to customize it as you see fit.
Root tool > "return to stock"
Sent from my HTC Inspire 4G using XDA-funded carrier pigeons
simx said:
CEnnis91
I was lucky the second time, first time I succeeded to upgrade to rooted 4.55.97 but for some reason I didn't get the battery percentage on the status bar but all other issues are OK and status indicated version number 4.55.97, I repeated flash from recovery but after wiping and remounting all folders, this time for stock 4.55.97
Now I'm on stock 4.55.97 with battery percent on status bar and syncing from my mac.
thanks CEnnis91
NA
Click to expand...
Click to collapse
I'm about to try this.. but it's making me think... Do you think the updater-script doesn't correctly format system? Think about it... our devices say 4.55.97 (mine changed to that after a reboot or two), and we only had partial features... sounds like something isn't wiping correctly.
Can I recover my dead SG5 with system dump via CWM?
What can I do with it?
It is far from clear what you want to know?
You didn't say what happened to your phone, why it is "dead" or exactly what you mean by dead. CWM is a custom recovery but you didn't even tell us if you had it instlaled and therefore presumably have backups. Or if you are hopeful that CWM will fix your unspecified problem. And system dump is a vague term usually referring to making a backup on the command line using the dd utility.
We need a lot more information if you need help with something. Such as what happened to your phone, whether it boots to recovery or download mode, loads an ADB shell and so forth.
.
fffft said:
It is far from clear what you want to know?
You didn't say what happened to your phone, why it is "dead" or exactly what you mean by dead. CWM is a custom recovery but you didn't even tell us if you had it instlaled and therefore presumably have backups. Or if you are hopeful that CWM will fix your unspecified problem. And system dump is a vague term usually referring to making a backup on the command line using the dd utility.
We need a lot more information if you need help with something. Such as what happened to your phone, whether it boots to recovery or download mode, loads an ADB shell and so forth.
.
Click to expand...
Click to collapse
[Q] Somebody give me SCL23's build.prop(original)
I changed build.prop
My android phone is SCL23
AKA Galaxy S5
I am Korean but now I live in Japan for work.
So I used GalaxyS5 for KDDI AU
Some application didn't work on my phone.
Even impossible to install
So I tried to root. Then changed model and vendor from GalaxyS5 to Galaxy S4
But it didn't work for using those apps
So I copy all of texts of build.prop of GalaxyS4.
Then my phone dead.
AU's logo is the only thing I can see.
Before did that
I had do googling and find SCL23's CWM with Chinese letters.
It works well.
Factory reset? YES
Boot? NO
Can not normal boot
Odin mode
I connected phone to PC.
Fail to install USB driver.
I think it cause of phone's hardware and build.prop is not same.
I have external SDCard.
Odin work via USB
And I can go into CWM recovery mode.
So I think if I can find .zip, able to flash, of SCL23's build.prop
I can copy it into extsdcard with friend's android
Then go into CWM and flash it.
I need SCL23's build prop
And somebody make it .zip please
I don't know how to make it.
Please help me.
And thank you for read this poor English
fffft said:
It is far from clear what you want to know?
You didn't say what happened to your phone, why it is "dead" or exactly what you mean by dead. CWM is a custom recovery but you didn't even tell us if you had it instlaled and therefore presumably have backups. Or if you are hopeful that CWM will fix your unspecified problem. And system dump is a vague term usually referring to making a backup on the command line using the dd utility.
We need a lot more information if you need help with something. Such as what happened to your phone, whether it boots to recovery or download mode, loads an ADB shell and so forth.
.
Click to expand...
Click to collapse
I wrote it few days ago.
Nobody replied to me.
So I thought many ways and did googling for recover.
I found link of system dump of SCL23.
So now I want to know about what can I do with it for my android phone's revive.
Please help me
If you have a system dump made while your phone was working properly, you can simply restore that to resolve your problems. It's not clear that that is the actual case though.
In the alternative, the apparent cause of your problems is a non-viable build.prop. You should be able to boot to CWM and then use a ADB shell under CWM to rename or delete /sideload the bad build.prop file and replace it with a good copy. If you didn't keep a good copy, you can download the stock firmware for your phone and use winrar to extract the proper stock build.prop for your phone.
More than likely, if you can boot to recovery mode, then you will be able to boot to download mode as well. So Odin use should be possible. You can use Kies to install a driver. But try CWM first.
.
fffft said:
If you have a system dump made while your phone was working properly, you can simply restore that to resolve your problems. It's not clear that that is the actual case though.
In the alternative, the apparent cause of your problems is a non-viable build.prop. You should be able to boot to CWM and then use a ADB shell under CWM to rename or delete /sideload the bad build.prop file and replace it with a good copy. If you didn't keep a good copy, you can download the stock firmware for your phone and use winrar to extract the proper stock build.prop for your phone.
More than likely, if you can boot to recovery mode, then you will be able to boot to download mode as well. So Odin use should be possible. You can use Kies to install a driver. But try CWM first.
.
Click to expand...
Click to collapse
I tried everything you told to me.
But very problem is install USB driver.
Kies failed to find and install USB driver. It worked well before I did it.
So I can not do anything with ADB commands because of USB driver.
But only Odin work to phone.
So I can install CWM. And I can go into CWM recovery mode.
Of course I can go to Download mode.
Can I do something with Linux?
Can I mount My Phone with Linux without install USB driver and then change build.prop.bak to build.prop?
I really appreciate to your reply.
Thanks to your kindness.
If your USB driver was properly installed before the problem, it will continue to work just fine, at least for CWM mode. Build.prop will not interfere with that. So just go to the CWM command line and use the ADB commands to push (replace) the build.prop file.
Are you certain that Odin doesn't recognize the phone in download mode. Ensure that you are entering download mode by removing the phone battery, replacing it, then pressing and holding in order, the volume down, then home, then power key until you see the screen light up. Odin should see the phone and it should not matter if the build.prop file is corrupt. Only the normal boot will be affected by that.
If you have problems connecting ADB or Odin, a far more likely suspect is a bad USB cable. Try a different cable or USB port. And ensure that you are entering download mode in the manner described above. When Odin recognizes your phone, you can write a stock firmware image to you phone to recover.
I haven't used CWM for quite a while (I much prefer TWRP), but it should offer you a command line. So as an alternative, use your PC to write a good copy of the build.prop file to your SD card. Then in CWM you could mount the external SD card, then copy the file from the card to your system directory. In this method, you wouldn't even require the USB driver.
You have lots of options and there are lots of ttutorials on using CWM, ADB and so forth if you need elaboration. You should certainly be able to resolve this issue even though it may be a pain in the neck or somewhat intimidating if it is unfamiliar territory. Nevertheless you can fix it if you are patient.
If the worst case,an alternative would be to pay a cellular repair shop to do the software repair for you. Entirely up to you which is the better approach.
.
So I wanted to create a thread dedicated to performing this function. I know as someone who does this quite often, I like to have all my ducks in a row to ensure everything works perfectly. I'm not big on fragging my phone and then frantically trying to find a way to undo all the chaos. I do a lot of research and ask a lot of questions before doing anything.
On that note I would like to first thank all the amazing people on here, whether they be developers or just experienced Tech Guru's, everyone is always a big help. I take absolutely no credit for any of the awesomeness that can be found on XDA, I'm just creating a thread that I hope will help folks find everything in one place for this function. So here we go, I'm going to explain the way I did it, which is the way I have been doing stuff like this for years. I have a preferred method as it has always resulted in perfect flashes and no bricks, not even soft bricks. So I feel it works pretty well.
Just so it is understood, this is for the Moto X Pure, which has been bootloader unlocked and has TWRP and root installed. Also it should be noted that you need to have Developer Options enabled and USB Debugging enabled. You should also be familiar with the ADB process, to some extent, maybe you have at least heard of it.
Steps to follow:
1. Use Titanium Backup and backup all your User Apps, NOT SYSTEM APP's, system apps will not restore across updates and will most often corrupt your new install.
2. Make a Nandroid backup using TWRP, I backed up system, boot, data, and EFS, but I don't think EFS is necessary.
3. Make sure you have the Motorola Drivers installed, get them from here http://www.motorola.com/getmdmwin
4. Get Shawn5162's Restore to Stock Tool, I know others have said it's not necessary to perform a complete restore, but this is part of my process that I have always done, and it's always worked. Get it here by using one of the mirror's created by patt2k in post 6, and don't forget to thank him for the mirrors http://forum.xda-developers.com/moto-x-style/development/windows-tool-moto-x-style-pure-edition-t3199905
5. Unzip Shawn5162's zip to a folder on your desktop, and before you move onto the next step, make sure you have backed up everything valuable on your phone, such as pictures, messages, etc..., because everything is going to be erased in the next step, except for the stuff on your MicroSD. I'm so anal, I even remove the MicroSD before flashing. Connect your phone to your computer using a USB and make sure you have USB debugging enabled under Developer Options.
6. Inside the folder you created run the FLASH-ALL.bat, which will reboot your device to the bootloader and begin the restore to stock flash. This will remove root and TWRP, but will not remove the fact you have an unlocked bootloader. Your phone will reboot when complete and should boot back into your system within a short period of time.
7. Once you are rebooted, you may need to do a little setup before you get the message that a System Update is available. DO NOT waste your time installing any apps, wait until you have full root on MM before doing any of that. Once the Update message appears, accept it and download the MM update file, then install it once it is finished downloading and asks if you want to install.
8. The update takes about 20 - 25 minutes so be patient. Once complete your phone will once again boot back to system, now you have MM in it's complete unrooted greatness.
9. Now go into settings, about phone, and tap on build number a bunch of times to enable Developer Options. Then go into developer options and enable USB Debugging.
10. Next download a bunch of stuff from the following links, if you desire to install TWRP and regain root.
TWRP 2.8.7.1 here https://dl.twrp.me/clark/twrp-2.8.7.1-clark.img
Modified Boot Image from here, required to perform systemless root , not sure about the Cowboy hat dude, but click on him, it will download the file.
SuperSU 2.52 from here https://download.chainfire.eu/743/SuperSU/BETA-SuperSU-v2.52.zip?retrieve_file=1
11. Next copy the modified boot file and SuperSU file directly to your internal or external SD on your phone, either works fine, although I prefer my External SD.
12. Next copy the TWRP file you downloaded into the same folder you made for Shawn5162's files. This folder has all the adb and fastboot files you need to perform the TWRP flash. Now hold shift and right click and choose open a command window here. Then ensure your device is detected by running the command adb devices, it should show your phones S/N and the word device. If it doesn't, you may need to look at your phone and respond to the prompt about allowing your computer to have access to adb. Try the command again after that. Then run the command adb reboot bootloader, which should reboot your phone to bootloader fastboot mode.
13. Once it fastboot mode run fastboot devices just to make sure your device is still detected, then run the command fastboot flash recovery twrp-2.8.7.1-clark.img. That will flash TWRP to your recovery partition. Then type the command fastboot reboot twrp-2.8.7.1-clark.img or use the volume rocker to toggle to recovery then select the power key to boot to it. Make sure you choose the slider at the bottom to allow modification. Once on the main screen you can choose reboot and then select recovery. This makes sure that you have booted to TWRP at least once, and ensures by rebooting to it, you can get back to it.
14. Now perform a Nandroid Backup, using the TWRP Backup option, of your completely stock MM system, data, boot, and EFS partitions. Enable compression if you like and store it to your External SD if you have one. This allows you to have an unrooted backup on your SD, which is good for future updates. After the Nandroid is complete now flash the modified boot image zip using the TWRP Install feature, and when it's complete, then flash the SuperSU zip file. After I always perform the option to erase Dalvik and Cache, I just think it is a good thing to do, it's probably placebo, but I do it anyhow.
15. Go back to TWRP Home and choose reboot and select system. Your device will reboot and you now have a fully updated and rooted Moto X Pure on MM.
Thanks go out to all the folks who have contributed to the many threads that contain this information. Special thanks to Shawn5162, DaMadOne, Chainfire, and Hashbang173 for their awesomeness. Hope this helps folks that are concerned about performing these procedures. I can say that it worked perfectly for me with no issues at all, but of course I take no responsibility if it doesn't work for you and causes your device to fail. Again these are similar steps I have taken in the past with other devices and I have never had a single brick, so hopefully it works for others as well.
Enjoy!!
I have a Moto X Pure as described with the bootloader unlocked and rooted. The popup message to upgrade to MM comes up constantly now - what happens if you just let it try to update?
I think I am in way over my head. I am receiving my phone Friday and was looking to unlock to root but from the looks of it, I will not be able to do that.
I've never unlocked & rooted a phone before. So all that looks like the bible to an uneducated man "me".
superkev72 said:
I have a Moto X Pure as described with the bootloader unlocked and rooted. The popup message to upgrade to MM comes up constantly now - what happens if you just let it try to update?
Click to expand...
Click to collapse
If I'm not mistaken it will download to your phone but not be able to be installed because of an error
Is there no way to upgrade from LP to MM without a wipe?
superkev72 said:
Is there no way to upgrade from LP to MM without a wipe?
Click to expand...
Click to collapse
Yeah, if you rooted already, you must reflash the original boot.img. Then update, and then restore your root. Read here:
http://forum.xda-developers.com/mot...t-moto-x-style-xt1572-br-marshmallow-t3259380
At the bottom of the post, you get the original file you need and it is mentioned here:
And enjoy!
Now you have a rooted MotoX Style Marshmallow. To apply any OTAs, you only need reflash stock boot.
K?
Why would you want to update without a wipe? You must like sluggish performance
i have no wifi after this
No WIFI either
I ended up with no WIFI after following these steps also.
is it true, we cannot downgrade from 601 to 6.0 or 5.1.1?
skimaniaz said:
I ended up with no WIFI after following these steps also.
Click to expand...
Click to collapse
Same here. Anybody got a fix?
So the last three posts complain of no wifi yet people keep using this method?
The modified boot zip breaks the wifi. You can root by flashing superSU 2.62, I think, or any SuperSU zip that is specifically systemless.
ilovemeow said:
is it true, we cannot downgrade from 601 to 6.0 or 5.1.1?
Click to expand...
Click to collapse
Not true.
lafester said:
Not true.
Click to expand...
Click to collapse
coz i tried before, it fail in first 2 flash steps
Are you unlocked?
ilovemeow said:
coz i tried before, it fail in first 2 flash steps
Click to expand...
Click to collapse
The partition always fails. Just ignore it. You should be able to downgrade the bootloader. I have been able to so I don't know why you would be having issues with that unless your bootloader is locked/re-locked.
Sent from my XT1575 using XDA Labs
So is this safe or not?
lafester said:
Are you unlocked?
Click to expand...
Click to collapse
yup, it's unlocked, but currently fine for using android M at this moment
Hi all,
How are you?
I've been looking at these forums for most of the day, though am still quite confused. If someone could assist to clarify it would be much appreciated (as I would like to avoid to brick my phone).
I'm currently running Stock Android, Marshmallow version 6.0.1 with the 1 November 2016 Security Patch.
The model of my phone SM-G900I (Australian edition).
So I've come across the following links with the instructions on how to root and install recovery, though quite confusing.
http://forum.xda-developers.com/show....php?t=2699648
Recovery Query?
I understand that you need to download the Samsung Drivers and Odin.
I've downloaded the TWRP files for my phone - twrp-3.0.2-2-klte.img.tar and twrp-3.0.2-2-klte.img.tar.asc
Do I need to use the twrp-3.0.2-2-klte.img.tar.asc file at all?
Root Query
Is the towelroot method of rooting the S5 still relevant. The reason I ask, is that when I had posted an initial question on the XDA assist, I was advised that this may not work.
If the towelroot method is no longer relevant, would the CF-Autoroot method below work?
http://forum.xda-developers.com/show....php?t=2696537
If neither of the above methods work I have seen mentions of "flashing root" via TWRP.
Are there any known instructions on how to do that on XDA or any other website?
Or is it just a matter of obtaining the superSU zip file from https://download.chainfire.eu/696/supersu/ and flashing it?
The other information seems straight forward re using the Samsung Tool to backing up the device and the EFS .
Any help would be much appreciated.
Thank you.
just flash the .img file in download mode, and dont use the asc file at all. also dont use twrp 3.0.2-2, just use 3.0.2 (not 3.0.2-1 or 3.0.2-2 as they can be pretty buggy). Towelroot has long since become irrelevant back in the 5.0 days unfortunately so all you need to do is find the appropriate supersu.zip file and put it on your phones sd card (either internal or external), boot into recovery an install that zip via TWRP then reboot. Should be good to go. The classic "root via recovery" method
Paul_Lunardi said:
Hi all,
How are you?
I've been looking at these forums for most of the day, though am still quite confused. If someone could assist to clarify it would be much appreciated (as I would like to avoid to brick my phone).
Recovery Query?
I understand that you need to download the Samsung Drivers and Odin.
I've downloaded the TWRP files for my phone - twrp-3.0.2-2-klte.img.tar and twrp-3.0.2-2-klte.img.tar.asc
Do I need to use the twrp-3.0.2-2-klte.img.tar.asc file at all?
Root Query
Is the towelroot method of rooting the S5 still relevant. The reason I ask, is that when I had posted an initial question on the XDA assist, I was advised that this may not work.
If the towelroot method is no longer relevant, would the CF-Autoroot method below work?
http://forum.xda-developers.com/show....php?t=2696537
.
.
Click to expand...
Click to collapse
1. Plug in your phone and let the drivers load.
If phone unrecognized then head to Playstore you can find loads of apps for drivers
2.unplug your phone and turn it off
3.Load odin.
Some versions of Odin are outdated. So watch for that.
4.Holding your turned off phone. Hold the volume down power and home buttons. Done correctly it should bring you to a page saying custom Roms can damage your blah blah. Volume up to continue down to reboot. Plug your phone in then Push volume up if you feel ready to Join us Oh Padawan.
Now I am sorry for the lengthy information, most likely you have already gotten to this point, but I just want to make the same page for you and future readers. No point in asking a bunch of potentially irrelevant questions when one explanation is sufficient.
5. Odin should find your phone which will be represented by a lit up colored square on the left side indicating a Com:value# which number is of little consequence just tells you which port it found it at. Do not dwell on this.
6. Using an extraction program such as .7z take your CF auto root .Tar file, not the .Asc, and extract. You should be able to find an file with ap in the extension.
7.Take the path from the URL bar of this window including the name of the ap file and copy it over to Odin. In Odin you will see the place to put it is represented by AP.
8. CLICK START AND WAIT WITH JEOPARDY MUSIC.
9. IT MAY REBOOT A FEW TIMES BUT UNTIL IT SAYS success OR FAIL IN ODIN DO NOT TOUCH.
10. Repeat steps 7-9 for twrp.img
10. Now taking this was a success turn your phone off. Unplug and holding volume UP power and home Gets you into twrp recovery. If all is well you can reboot into system. Ignore the kernel warning.
^^^^^ theres the long explanation LoL ^^^^^^^^ i disagree with step 9, but meh
Hi all,
Thanks for the detailed instructions.
So it appears that you can perform the task in 2 ways, ie
* By initially flashing TWRP first using Odin (whilst phone is in download mode), then running the TWRP and then copying over the supersu file to the sd card, then flashing this.
Or alternatively, following the above steps which first
* roots the phone by using Odin within download mode and the "cf auto root" file. Then once again using odin and flashing the TWRP file via odin.
This is my understanding.
Please let me know if I've misunderstood, otherwise thanks all. I'll be giving it a try soon.
My eventual goal is to install the Resurrection Remix Rom, so fingers crossed.
Paul_Lunardi said:
Hi all,
Thanks for the detailed instructions.
So it appears that you can perform the task in 2 ways, ie
* By initially flashing TWRP first using Odin (whilst phone is in download mode), then running the TWRP and then copying over the supersu file to the sd card, then flashing this.
Or alternatively, following the above steps which first
* roots the phone by using Odin within download mode and the "cf auto root" file. Then once again using odin and flashing the TWRP file via odin.
This is my understanding.
Please let me know if I've misunderstood, otherwise thanks all. I'll be giving it a try soon.
My eventual goal is to install the Resurrection Remix Rom, so fingers crossed.
Click to expand...
Click to collapse
the cf auto root file usually isnt necessary, nor is flashing supersu really as the newer twrps have the root function built right in. Itll ask you if you want to enable superuser rights the first time you boot into it. Just swipe right and its rooted. Alternatively, flashing supersu from within twrp or the cf auto root also work. CF is the acronym for the dev ChainFire, he is the man (or she, and conversely "the woman" or whatever LOL)!! But the crux of what you need is twrp installed, from there youre usually set. Get rooted, make a nand of your stock setup and flash away. Also, id make sure to download the stock tar.md5 file of your phones firmware in case all goes awry (or to hell in a handbasket or enter clever euphemism for stuff going bad here) so you can flash the stock tarball in Odin if you get stuck in an endless bootloop and your stock restore file doesnt work. Also, when resoring from AOSP to TouchWiz or vice versa, does require a few boxes to be checked for it to work, but it happens all the time. Happy flashing and feel free to ask away if you run into anything man!
Thanks all for clarifying.
I did have some difficulties along the way though I did successfully install twrp.
So I downloaded one of the latest versions of odin on mums computer. Laiche the twrp tar file in the ap section. Loaded it then restarted the device. Ran recovery though it was still the default android recovery ie it appeared as though nothing had changed. I looked at another forum which suggested to turn ooff the auto reboot option in odin and perform a battery pull and then launch directly into twrp. This actually worked after much agony.
I then loaded a superuser zip and flashed it onto the phone.
Rebooted confirmed that the phone was rooted.
I then relaunched the twrp recovery and ran a nand? backup of my device. Then I attempted to install a custom rom ie resurrection remix. Unfortunately it did load though the screen appeared to freeze after boot and was therefore unusable. Thank goodness the restoring of the backup worked.
I'll reattempt the installation of a custom rom very soon. Fingers crossed.
Thanks.