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.
.
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
Hello,
The home button of my device (Magic) does not work at all. So, I can not confirm to install the CyanogenMod in the recovery screen.
Am I able to install the ROM via fastboot? or does anybody has another suggestion?
Regards,
Omer
Yes, you can flash ROMs via fastboot, but you'll need a system and data img for the ROM, and I'm not aware of a method to package them up based on an update.zip.
I checked inside the archive and saw the images but there also some scripts need to run. That's why; I couldn't dare to flash.
Is there a method I can follow?
osaatcioglu said:
I checked inside the archive and saw the images but there also some scripts need to run. That's why; I couldn't dare to flash.
Is there a method I can follow?
Click to expand...
Click to collapse
You don't need any scripts, just a system and data to flash.
fastboot flash data.img
fastboot flash system.img
You wont find these images inside the update.zip, the sys/data-imgs need to be created from the sys/data folders. Best bet is to ask someone to perform a nandroid backup, backup the imgs, wipe, flash cyan, send you those imgs, restore their old imgs.
Thank you. But, the someone's device should be identical to magic, right? I have dream also. So, I can use the nandroid backups of it. However; I don't think this would be possible. what do you think?
osaatcioglu said:
Thank you. But, the someone's device should be identical to magic, right? I have dream also. So, I can use the nandroid backups of it. However; I don't think this would be possible. what do you think?
Click to expand...
Click to collapse
I'm really not sure, but I think the device would need to have the same size data and system partitions as the Magic, which the Dream doesn't.
Use mkyaffs2 to make the System and Data .img Files
What operating system do you have because if you have linux or a linux virtual machine you could extract the update zip and use the mkyaffs2 utility code.google.com/p/yaffs2utils/ to make the system and data images.
There is also a much easier program called yaffey http://forum.xda-developers.com/showthread.php?t=1645412 but it is windows only
So this thread is kind of old, but I stumbled upon it looking for stuff.
Im using a google galaxy nexus and have a strange issue where I cant connect it via usb when in a different state than fastboot mode. I replaced the usb port (flex cable) already, but it doesnt help (if you got any advice on that, please tell me)
What I actually want to say is that I can't install cyanogen from recovery because I can't connect my phone when in recovery, but I can flash firmware normally via bootloader, I tried that already, so how exactly do I get the images for cyanogen? Because I don't fully grasp it yet.
I have a problem with mounting my phone in Windows (see here; http://forum.xda-developers.com/showthread.php?t=841645) and I need to return it for testing.
How can I flash it back to stock without a USB connection?
E.E.
Assuming you're rooted and on a custom ROM
You will need unlimited data to try this.
Not sure if this will work, but please do try.
1. Make sure your phone is juiced up.
2. Download the Stock RUU you want from the internet - save to your sdcard
3. Download another sense based ROM that you has no issues with the USB cable - check the post and changelogs.
4. Perform rom backup with ROM manager (get from android market)
5. Wipe and flash new Sense based ROM on your phone.
6. Once your phone is booted, the USB SHOULD WORK.
7. Move RUU to your PC. Link to HTC sync - phone should be set to sync.
8. Install RUU.
And once it is one, you have unrooted and are back to stock ROM.
Should your USB fail at stage 6, you should try a different custom ROM.
If it's still not working, you might want to search how to USB unbrick (i think there's something like that on the forums).
Unfortunately its not a rom problem. The USB issue seems to be a hardware problem.
I have flashed multiple different backups from CM6 to myvery first backup I made of the newly rooted rom.
I just need to put a stock rom on it so that I can get warranteed service. Otherwise I'm pretty sure they'll just shoot it back to me, marked warranty void.
E.E.
Have you tried this?
It's to unbrick your usb
http://forum.xda-developers.com/showthread.php?p=7616115#post7616115
I had also problems with mounting USB, can't tell if they were the same as I don't use windows and can't tell how it behaves. My problem was solved after I flashed the rooted vodafone FroYo. Maybe this could help you, too.
I haven't tested it yet but it may be as simple as downloading the zip from shipped-roms.
(http://shipped-roms.com/download.ph...35.21_release_130330_signed.zip&send_file=yes)
Renaming it to update.zip and flashing it from Recovery.
Can anyone confirm?
E.E.
Actually the best solution I've found yet is this one here from the CM forums.
This using the .img files from the zip I downloaded from Shipped-Roms earlier
Instructions
---------------
1. Boot n1 to fastboot mode
2. Extract the FRG33 files to your tools directory in PC (you need system.img and boot.img)
3. In your tools directory, fastboot the following commands
fastboot flash system system.img
WAIT
fastboot flash boot boot.img
WAIT
Reboot
Alternative method
------------------------
Rename the stock file to passimg.zip
Now you need to use ADB to get it on the SD card, or just copy file to sd card root directory
Command: adb push passimg.zip /sdcard
Now get into the bootloader and it should detect the passimg.zip file and ask if you want to install it.
Click to expand...
Click to collapse
Since I have Fastboot available to me, this seems the most hopeful method.
Can anyone confirm is this not just hopeful thinking?
E.E.
Hey,
I had installed TWRP and CM10.2 with no issue, ioroot11.
I let my buddy use the device, he jacked it up...its stuck in the LG boot logo loop... I can still boot in to TWRP but cm10.2 is gone along with everything else that was on the storage. Its clear now he wiped everything.
I need clear step by step instructions on how to overcome this issue.
Id rather just find a way to get cm back on to the storage but if i have to i will do a stock re install.
I need a list of working drivers, how to get adb set up and working correctly (adb devices says offline for my device atm), what commands to use to push cm10 back on to the device, what state the phone needs to be in order to push the cm10 zip (i only have bootlogo, download mode and twrp as device state options).
or i need a list of everything that is needed to install stock. as far as that goes, i need a direct link to sprints .tot file and directions on how to get that going.
TLR
Stuck in LG logo boot, still have TWRP..need help getting ANY type of rom installed. ADB push or Stock re install....
Thanks ahead of time to anyone who helps.
you guys are awesome!
HEWHOCORRUPTS said:
Hey,
I had installed TWRP and CM10.2 with no issue, ioroot11.
I let my buddy use the device, he jacked it up...its stuck in the LG boot logo loop... I can still boot in to TWRP but cm10.2 is gone along with everything else that was on the storage. Its clear now he wiped everything.
I need clear step by step instructions on how to overcome this issue.
Id rather just find a way to get cm back on to the storage but if i have to i will do a stock re install.
I need a list of working drivers, how to get adb set up and working correctly (adb devices says offline for my device atm), what commands to use to push cm10 back on to the device, what state the phone needs to be in order to push the cm10 zip (i only have bootlogo, download mode and twrp as device state options).
or i need a list of everything that is needed to install stock. as far as that goes, i need a direct link to sprints .tot file and directions on how to get that going.
TLR
Stuck in LG logo boot, still have TWRP..need help getting ANY type of rom installed. ADB push or Stock re install....
Thanks ahead of time to anyone who helps.
you guys are awesome!
Click to expand...
Click to collapse
For back to stock there's a thread in general forums you can also use the Verizon method with sprint files.....or you can read bout adb and download and setup on PC then push a ROM to TWRP and just flash.....you should always make a backup when your up and going again....I didn't post links cause I figured you could Google...instead of me
Thanks for your reply.
I have looked all over and was unable to find any information on what needed to be down to get adb working correctly on my device.
will you kindly link me to something explaining how to get adb working correctly with my phone. links to all the files needed.
when i use adb devices, it lists my device as offline. what state does my phone need to be in?
as for the stock restore, i download the sprint files but when i go to extract the TOT file, it does not extract correctly. will you please link me to the correct drivers needed for this process.
Thanks!
HEWHOCORRUPTS said:
Thanks for your reply.
I have looked all over and was unable to find any information on what needed to be down to get adb working correctly on my device.
will you kindly link me to something explaining how to get adb working correctly with my phone. links to all the files needed.
when i use adb devices, it lists my device as offline. what state does my phone need to be in?
as for the stock restore, i download the sprint files but when i go to extract the TOT file, it does not extract correctly. will you please link me to the correct drivers needed for this process.
Thanks!
Click to expand...
Click to collapse
Did you ever get your device back running? Im having the same problem? any help?
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