Sprint Restore To Stock! (Nandroids CWM+TWRP & Recovery IMG) - Samsung Galaxy Nexus

Forget to make a backup before trying to flash a rom?
Need to return your phone to sprint?
TWRP NANDROID
Unzip then Place these in your TWRP Folder by using ADB (lookup your standard ADB guide) Then restore the nandroid
CWM NANDROID
Unzip then place in your CWM folder sub folder backups then boot to clockwork mod and restore
Stock Recovery Image
use this while in fastboot mode (hold vol up + down + power while phone is off) then on your computer issue cmd fastboot flash recovery recovery.img (search for how to setup adb)
Need Help Rooting? How To Videos Thanks to QBking77!
Need More Help? Join the IRC channel!
Coming Soon:
Radio Fix (if you flashed a verizon radio)
If this helped Donate To Me

Updated with CWM Nandroid and Stock Recovery Image

Sweet thanks
Sent from my Galaxy Nexus using Tapatalk 2

thanks to raiderep for giving me the stock recovery

Well Thanks Let the flashing begin ;P
Here is a link for the drivers from Samsung as well maybe helpfull
http://www.samsung.com/us/support/owners/product/SPH-L700ZKASPR
its the exe file and works well

thanks.. ill get how to videos up soon

qbking77 said:
thanks.. ill get how to videos up soon
Click to expand...
Click to collapse
You a good guy, so is OP.

added thanks to all the guys over on the IRC channel

shabbypenguin said:
thanks to raiderep for giving me the stock recovery
Click to expand...
Click to collapse
Glad to help when I can as always, go android!
Sent from my Galaxy Nexus

Im using twrp rec.
I dont like/trust twrp recovery, where can i get a sprint compatible cwm recovery?
Sent from my Xoom using XDA Premium HD app

malibu_23 said:
Im using twrp rec.
I dont like/trust twrp recovery, where can i get a sprint compatible cwm recovery?
Sent from my Xoom using XDA Premium HD app
Click to expand...
Click to collapse
We do the CWM for the verizon version is the one that works......

What if...
Wordlywisewiz said:
Forget to make a backup before trying to flash a rom?
Need to return your phone to sprint?
TWRP NANDROID
Unzip then Place these in your TWRP Folder by using ADB (lookup your standard ADB guide) Then restore the nandroid
Click to expand...
Click to collapse
What if I tried to use twrp recovery and now my phone refuses to activate. It says there is no sim card installed. I called sprint and they can't make it happen over the phone. They want me to come into the store, but i suspect that it isn't going to work their either. Any suggestions?
Thanks guys!

turbo2125 said:
What if I tried to use twrp recovery and now my phone refuses to activate. It says there is no sim card installed. I called sprint and they can't make it happen over the phone. They want me to come into the store, but i suspect that it isn't going to work their either. Any suggestions?
Thanks guys!
Click to expand...
Click to collapse
same here...says "no sim card"...WTF...

Try doing a factory data reset. Just a shot in the dark...

turbo2125 said:
What if I tried to use twrp recovery and now my phone refuses to activate. It says there is no sim card installed. I called sprint and they can't make it happen over the phone. They want me to come into the store, but i suspect that it isn't going to work their either. Any suggestions?
Thanks guys!
Click to expand...
Click to collapse
same thing has happened to my phone but not with this immage what happened is i accidently flashed a image from a verizon phone to the sprint phone and now is all kinds of messed up
my friend is currently trying to fix it for me (hes a hell of a lot smarter than i am)
ill let u know the results

Same Song.. Several Verses Later
I would really like to find out if any of you figured this out??
I find myself in the same position as I'm finding that many have on here as well. I found this thread interesting because it is dealing with the Sprint Galaxy in particular. I have hosed the radio and the baseband on the Galaxy - likely the EFS parition, not sure.. at this point. It needs to be made very clear to everyone that even has a thought of flashing with this phone to make triplicate backups of the EFS partition before they turn the phone on (exxageration for affect).
That being said - I don't think that gets the rest of us anywhere. I'm a OG owner and a Bionic owner - and the first 72 hours of Samsung ownership has felt like non-stop triage to me..
I have this here.. but this really isn't the specific image for the Sprint the phones...
The link below points to a post for the IMM761 GSM+HSPA - which I believe these phones to be identical.. and since Sprint had locked code for the CDMA versions - is this one the same - in other words, is there an image out there that can be downloaded, flashed, and from there we can we can either fix the EFS and restore IMEI folder and baseband function or at least call warranty?
At this point - I can't reset the counter on the phone, I can't take it to the store (as if the 7 iployees would know what I was talking about) and I'm not about to pay $800 to learn that the EFS partition is the "short" in the term "got you by the short hairs"..
androidforums -
Heat57 says:"
It sounds as so you are on the GSM "maguro" device. In that case I suggest you download the complete ICS 4.0.4 factory image from Google at ... file. Beware! if you have a Windows PC the original download with a .tgz extension will be renamed by Windows automatically to a .tar file, which means that you'll have problems extracting it. In that case simply rename the file by changing the extension to .tgz and all will be well. Note: you'll need the Galaxy Nexus bootloader unlocked in order to flash a factory image and at the end of the procedure you can leave it unlocked and flash a Superuser file to root, if so desired. You'll need the Android SDK installed on your PC and then copy the bootloader, radio and image .img files to your ...android-sdk\platform tools-tools folder and run the adb commands in the windows command shell (note: you must flash each image in this order and wait until each image is flashed completely >bootloader >radio > image). Finally, flash the "image-soju-imm76d.zip" through your cwm recovery. You should end up with a healthy Galaxy Nexus on ICS 4.0.4 and everything working"​

Wordlywisewiz said:
Forget to make a backup before trying to flash a rom?
Need to return your phone to sprint?
TWRP NANDROID
Unzip then Place these in your TWRP Folder by using ADB (lookup your standard ADB guide) Then restore the nandroid
CWM NANDROID
Unzip then place in your CWM folder sub folder backups then boot to clockwork mod and restore
Stock Recovery Image
use this while in fastboot mode (hold vol up + down + power while phone is off) then on your computer issue cmd fastboot flash recovery recovery.img (search for how to setup adb)
Need Help Rooting? How To Videos Thanks to QBking77!
Need More Help? Join the IRC channel!
Coming Soon:
Radio Fix (if you flashed a verizon radio)
If this helped Donate To Me
Click to expand...
Click to collapse
I think you are right but I do have cwm Also when I followed techfanatic's vid to unroot it said my phone was unrooted but the radio failed error came up. Also I am still on codeandroid. can I actually be unrooted and still be on that? Must I root again? Thanks.

Related

Wildfire ROM update - backup questions

Hi everyone,
I'm using a HTC Wildfire and am considering changing from stock (HTC non-branded) to CyanogenMod for a number of minor reasons. Could anyone just confirm that I got a few points right before I get started:
- Recovery is totally independent from the ROM itself, right? So I can flash ClockWorkMod Recovery only, continue to use the stock ROM, but have the additional features of ClockWorkMod available, such as backup, with which I can create a complete backup of the stock ROM. In case I don't like CyanogenMod, I can restore the stock image and be exactly where I left it, Apps, Settings and everything (of course the new Recovery will still be installed.) Is this correct?
- I'm planning to do the following steps (I read about the details, just want to confirm the basics):
x use the Revolutionary way to S-OFF and install new Recovery
x create full image backup of the stock ROM using the new Recovery
x install new ROM (ClockWorkMod)
x if I don't like CM: restore image created before to return to stock
-> This should work, shouldn't it?
- One more: What will happen if the the phone is S-OFF, an alternative Recovery is installed, and a HTC Firmware-Update is attempted? Will this work at all, will it update just the ROM, or will it update the Recovery, too? S-OFF will not be changed back to S-ON, right?
Thanks for your help.
Regards
1. Yes, the recovery is in it's own partition and is independent from the ROM
2. The recovery creates a "snapshot" of your current ROM. So when you restore, it'll be just the way you left it.
3. There's no need to do any HTC Firmware updates after installing a custom ROM (infact, I'm almost 100% sure that it won't work)
As a basic answer yes you go ahead with what you posted.just make sure your hboot version is compatible with revolutionary 1st etc etc.
As for HTC firmware update question,if your talking about the over the air updates I'm not sure but I think it would update your hboot thus reverting back to s-on status again so best not accept it if you do get one (turn off in settings)
Edit : ninja'd lol
Sent from my HTC Wildfire using XDA App
slymobi said:
As a basic answer yes you go ahead with what you posted.just make sure your hboot version is compatible with revolutionary 1st etc etc.
Click to expand...
Click to collapse
Yes, of course.
As for HTC firmware update question,if your talking about the over the air updates [...]
Click to expand...
Click to collapse
No, the manual ones you can download directly from HTC and install via USB. My understanding was that this would kill everything flashable, including radio and recovery. It would be reassuring to have a worst-case way to go back to stock in case the image-restore fails for whatever reason.
150d said:
Yes, of course.
No, the manual ones you can download directly from HTC and install via USB. My understanding was that this would kill everything flashable, including radio and recovery. It would be reassuring to have a worst-case way to go back to stock in case the image-restore fails for whatever reason.
Click to expand...
Click to collapse
Ah sorry never dealt with any firmware updates. There are ruu.exe to help get back to stock if something goes wrong I think.
Sent from my HTC Wildfire using XDA App
You can go completely back to stock, s-on and all but believe me once you have cwm installed there really is no point unless its for warranty reasons, backup fails are rare with the latest recoveries + if it does fail with your first backup you can always post here and we will explain how to extract a stock Rom from an ruu to put things back to how they where before or you can flash a custom sense Rom and modify it to your liking.
Sent from my HTC Wildfire using xda premium
Scratch0805 said:
You can go completely back to stock, s-on and all
Click to expand...
Click to collapse
That's great.
[...] but believe me once you have cwm installed there really is no point unless its for warranty reasons[...]
Click to expand...
Click to collapse
Yea, exactly. I'm a little on the paranoid side, I know... ;-)
Ok, I'm on my way now. I've performed the "Revolutionary" S-OFF and am now running "Revolutionary CWM v4.0.1.4". Is this an out-of-date version?
I've read about ROM-Manager being able to auto-check for and flash a new Clockworks Recovery, but I've also read that ROM-Manager needs root. I have not yet flashed a new ROM, so I assume that I'm not yet rooted, am I? Can I find a ZIP of CWM that I can directly flash from the SD-card?
Does the CWM-version I'm running have any effect on the "quality" of the image backup? In other words, if I create a backup now, will I be able to restore it later running a different version of CWM?
The "different version backup restore" is a bit wonky and won't always work.
To flash a different recovery from the SD card do this:
1. Place this file on your SD card (Not in any folders!): http://www.multiupload.com/74EW2VPNHL
2. Boot into the bootloader
3. Wait a bit and then it should prompt you to update
4. Click the volume+ key to update
5. Remove SD card
6. Boot into the new recovery and insert the SD card
7. Go under mounts and select Mount USB storage
8. Delete the PCIMG file from your computer
nejc121 said:
1. Place this file on your SD card (Not in any folders!): http://www.multiupload.com/74EW2VPNHL
Click to expand...
Click to collapse
I tried to, but I couldn't use the link. The whole domain seems to be down - maybe another holy crusade of Big Content, who knows. They sure leave fans in their wake, don't they.
Since you indicated that updating would be ok for the wildfire I went to http://www.clockworkmod.com/rommanager and downloaded the file recovery-clockwork-5.0.2.0-buzz.zip.
However, I'm not sure how to handle it: If I put it on the card under this name, nothing happens on bootloader-start. In recovery, I can select the file and install it, and then I immidiatly get a newly colored menu with the new CWM version 5.something. However, once I restart, the old CWM (v4.x) is there again.
I assume I need to use a magic filename so that the bootloader performs the update, not the (already running) recovery. Right?
**EDIT: Ah, disregard. I believe I found the answer myself.
Do you have fastboot?
If you do I can give you the recovery.img I'm using, which you can flash via fastboot.
Yes, fastboot is available.
Thank you.
Okay, here's how you flash a recovery via fastboot.
1. Extract the .zip I attached to the location where you fastboot is
2. Reboot phone in the bootloader
3. Select fastboot and attach USB cable
4. Open up the command prompt and type in "cd [location of fastboot]
5. Type in "fastboot flash recovery recovery.img"
6. You're done
Oh and by [location of fastboot] I mean that you type in the location of fastboot.
Wow - this was fun. There was something really curious going on with my device: Whatever I tried, no "official" way worked to modify CWM v4 to v5. In every case, the menu of the new version showed up and was usable, but was gone again after restart. After the file-on-card method got me nowhere (file was not recognized), I tried the high road and installed ROM-Manager. This complained about missing su. So I installed su. After that ROM-Manager downloaded CWM v5 and put it onto the card (into a file named update.zip - ahh... ) On restart, the CWM-install-screen came up, then the v5 menu.
And after restart, it was gone again. Even ROM-Manager was confused: He showed v5 as "installed", when in fact it was still v4. ;-)
So finally I downloaded the Android SDK (to get fastboot.exe) and performed the flash as you suggested in the first place. And it worked. First try, without hitch, permanently.
Thank you very much for your help!
Regards
The problem with ROM Manager's version is that it's only temporary and can only be accessed from the ROM Manager itself

[Howto] Install a Recovery

NOTE: If anyone has any further questions about recoveries on the S3, please note that I have moved on to another device. Sorry!
So you've got your device rooted, and you want to install a custom recovery? Great! Don't just follow any guide you stumble across though, as some of the early recovery packages for the "AT&T" model were actually just copies of the custom Sprint recovery, and then you'll have all sorts of fun trying to install ROMs. ("Status 7" errors anyone? )
I'd like to talk about 4 ways to get the custom recovery of your choice onto your device.
Using mskip's Toolkit CWM [link]
Follow the instructions posted in his thread, and if you have any problems, direct them there as well!
Using ROM Manager CWM [link]
For some reason, ROM Manager doesn't always offer the correct list of devices to flash a recovery for and you won't see the SGS3 (AT&T) in the list. If that happens, force-close the app from Settings > Applications and try again. If this method just won't work for you, move on to option 4.
Using GooManager TWRP [link]
If you've been looking at ROMs, you may have noticed Goo.IM is a popular hosting website for Android developers. It's so popular, in fact, that they have produced an Android app that searches their website for updates for your ROM, and can even install TWRP with only a few simple clicks! Just open up GooManager, tap Menu, and tap "Install OpenRecoveryScript". You will be guided step-by-step from there by the app.
Note: Some people (myself included) have reported issues with this method, where the app claims to have installed the recovery, but when you reboot into recovery mode, nothing has changed. This issue may have been resolved in newer versions; I was able to successfully install TWRP using this method on Sept 26 2012.
Manually via ADB or Terminal Emulator CWM or TWRP [Terminal Emulator link]
If the other options just won't work for you, or if you would rather do an install by hand to ensure you're getting the latest version, read on...
Manually Installing a Recovery​
While this may seem difficult, it's really not. Grab a recovery image (these files end in ".img") such as ClockWork Mod (CWM) or Team Win Recovery Project (TWRP) for your device. Most ROM developers say to use CWM, but they both work equally well.
In our case, we need an image for the Samsung Galaxy S3 AT&T. Telus, Rogers, Bell, and SaskTel phones are (almost*) the exact same phone as AT&T, if you have one of these devices, you will be installing the AT&T recovery.
Now, transfer the ".img" file you downloaded onto your device. I'd suggest somewhere with a nice short path, like "/sdcard/<file>.img" (you'll thank me later, especially if you're using terminal emulator on the device)
Now, let's back up your existing recovery. If things go wrong, you can use this backup to get back to where you started.
Code:
$ su
# dd if=/dev/block/mmcblk0p18 of=/sdcard/recovery-backup.img
That should have created a "recovery-backup.img" on your phone's internal storage.
Here's the part you've been waiting for: Flashing the new image, which installs it as your recovery system. You do this from either an ADB shell or inside Terminal Emulator.
Code:
$ su
# dd if=/sdcard/[B]<file>[/B].img of=/dev/block/mmcblk0p18
You're done. Reboot into your new recovery by holding VolUp and Home while you power on your device.
If you need to return to the stock recovery, that IMG can be downloaded here: stock-recovery.img - 10.00 MB
*NOTE: While we're on the topic, let's take a second to talk about what makes the Canadian I747M different from the AT&T I747.
The short version is... The modem. AT&T is using completely different and incompatible modem firmware in their phones when compared with the Canadian models. Rogers, Bell, Telus, and any other Canadian I747M are the same device (Samsung worked some strange voodoo and got all the Canadian carriers to agree on the same hardware!) which means that if Rogers releases a new modem firmware update, a SaskTel user could install it without issue. AT&T modem updates will not work on Canadian models, nor will Canadian updates work on AT&T phones! I've tried it. Trust me. You don't want to deal with the hassle of fixing it.
Please remember to click/stick/lick/kick the "Thanks" button if you found this guide helpful!
How bout a 4th method for TWRP?
This should come in handy for some of the newer users
Well, the other TWRP method assumes that you already have a custom recovery installed to flash the ZIP from... If you've gotten that far already, I don't think you should need me to tell you how to flash a ZIP.
theres also GooManager from the market. its how I installed TWRP just download the app open it hit menu you'll see some options come up hit "install Open Recovery Script" it will ask if your sure hit ok and your done the whole process will take 30secs
Moved to General so new members can post questions
and stuck
FNM
Anyone know where to get stock sammy recovery img? Searched but didn't see it.
Edit: Got it.
dhostetter said:
Anyone know where to get stock sammy recovery img? Searched but didn't see it.
Edit: Got it.
Click to expand...
Click to collapse
Where'd you get it from? I'll add it to the OP.
There is a touch CWM for d2att available for manual installation.
http://www.clockworkmod.com/rommanager
tonymtl said:
There is a touch CWM for d2att available for manual installation.
http://www.clockworkmod.com/rommanager
Click to expand...
Click to collapse
There sure is! One of the benefits of manual installation is that you can find exactly what you want to use, and not rely on ROM Manager or other tools to make the decision for you!
Sent from my SAMSUNG-SGH-I747M
dstruct2k said:
Where'd you get it from? I'll add it to the OP.
Click to expand...
Click to collapse
+1. I am also looking for stock recovery...
Sent from my SAMSUNG-SGH-I747 using xda premium
I rooted my phone just after I bought it but was holding off on installing recovery due to how many hours I spend at work. Haven't had the time. I was also waiting on clear instructions on doing it manually, as it's easier for me since I'm not home often enough to use my PC and can't use the USB cord at work. Thank you SO much! Worked perfectly!
Edit: Spoke a little too soon. I'm seeing my backup dated 1970....
nekkidtruth said:
I rooted my phone just after I bought it but was holding off on installing recovery due to how many hours I spend at work. Haven't had the time. I was also waiting on clear instructions on doing it manually, as it's easier for me since I'm not home often enough to use my PC and can't use the USB cord at work. Thank you SO much! Worked perfectly!
Edit: Spoke a little too soon. I'm seeing my backup dated 1970....
Click to expand...
Click to collapse
That's a known issue with any recovery on the SGS3, it seems that the hardware clock cannot be accessed by the recovery no matter which recovery you use.
Did you happen to make a backup of your stock recovery? If so, I'd like to get a copy of it to add to the OP.
Nice HowTo, but the glaring omission is using the GooManager app to flash TWRP.
A lot of people are moving on from the old CWM to "something better".
zmore said:
Nice HowTo, but the glaring omission is using the GooManager app to flash TWRP.
A lot of people are moving on from the old CWM to "something better".
Click to expand...
Click to collapse
I could never get that to actually work in the past, so I guess I forgot about it. I just tested it now, and it worked fine, so I've updated the OP. Thanks!
dhostetter said:
Anyone know where to get stock sammy recovery img? Searched but didn't see it.
Edit: Got it.
Click to expand...
Click to collapse
See my Index for flash back to stock. There is a great vid tutorial.
PS dstruct2k I have added this thread to the INDEX. Nice work
Thanks, just flashed latest CWM Touch. External SD Card support rocks
For some after doing the manual install of cwm its not holding it as I enter recovery after I'm done it still shows old recovery. Trying to install cm10 I'm currently on kyanrom
Sent from my SGH-I747M using xda app-developers app
HAVOK83 said:
For some after doing the manual install of cwm its not holding it as I enter recovery after I'm done it still shows old recovery. Trying to install cm10 I'm currently on kyanrom
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
Then you're skipping a step, or typing something incorrectly. Once DD is done its work, you should get a response saying "Copied 10MB OK" or something similar. If it says that, then the stock recovery no longer exists.
HAVOK83 said:
For some after doing the manual install of cwm its not holding it as I enter recovery after I'm done it still shows old recovery. Trying to install cm10 I'm currently on kyanrom
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
Please visit this post and follow from step 11-15. Shows kind of messed up on the XDA app so view it on your desktop. Very detailed guide for those who are confused. Thank you.
http://forum.xda-developers.com/showthread.php?t=1912335
Sent from my T&K Blessed SGH-I747
I followed those same steps but from a different thread and it still wasn't upgrading my clockwork recovery and kept getting status 7 when trying to flash cm10. Now I installed touch version hoping I would be able to get cm10 installed but still getting status 7. Any help appreciated
Sent from my SGH-I747M using xda app-developers app

Phone Not booting after build.prop changed

I have Samsung Galaxy s3 ATT rooted - clockworld mod v-6.0.1.2. I was trying to install google wallet.
One of instructions was to change the following in the build.prop file.
ro.product.model=htc_jewel
ro.product.name=htc_jewel
ro.product.device=htc_jewel
I changed it. Installed custome google wallet. Reboot my phone and it gets stuck in the samsung logo, and then the screen blanks out.
What do I do?
Thanks
:crying:
Restore the cwm backup you should've made before editing the file.
Sent from my Motorola DynaTAC 8000X
mitchdickson said:
Restore the cwm backup you should've made before editing the file.
Sent from my Motorola DynaTAC 8000X
Click to expand...
Click to collapse
Unfortunately the backup I had done was a long time ago. And I had deleted the backup.
pkirangi said:
Unfortunately the backup I had done was a long time ago. And I had deleted the backup.
Click to expand...
Click to collapse
I'm thinking you need to find the stock at&t Rom put your phone in download mode and flash through Odin.
Sent from my SGH-I747M using xda premium
kojobaafi said:
I'm thinking you need to find the stock at&t Rom put your phone in download mode and flash through Odin.
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
Thanks. Where would I get the stock ROM?
pkirangi said:
Thanks. Where would I get the stock ROM?
Click to expand...
Click to collapse
I was able to download the boot-stock-att-sgh-i747.tar and flashed it using ODIN.
But still the same affect. After the samsung log, screen blanks out.
Thanks
pkirangi said:
I have Samsung Galaxy s3 ATT rooted - clockworld mod v-6.0.1.2. I was trying to install google wallet.
One of instructions was to change the following in the build.prop file.
ro.product.model=htc_jewel
ro.product.name=htc_jewel
ro.product.device=htc_jewel
I changed it. Installed custome google wallet. Reboot my phone and it gets stuck in the samsung logo, and then the screen blanks out.
What do I do?
Thanks
:crying:
Click to expand...
Click to collapse
Are you sure you didn't accidentally delete it? I've booted a bunch of times with wrong build prop info but I doubt phone would be boot if build prop didn't exist
Sent from my Nexus 7 using Tapatalk 2
mobilehavoc said:
Are you sure you didn't accidentally delete it? I've booted a bunch of times with wrong build prop info but I doubt phone would be boot if build prop didn't exist
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
I dont think I have deleted it. But how do I verify that..?
Go here... http://forum.xda-developers.com/showthread.php?t=1927198
This will tell you how to fix your build.prop so that your phone will boot again
ibanezbass said:
Go here... http://forum.xda-developers.com/showthread.php?t=1927198
This will tell you how to fix your build.prop so that your phone will boot again
Click to expand...
Click to collapse
Thanks I did try it. I am getting another issue. When I try the "adb shell" command as pointed by thread above - it throws a error - device not found. I have installed my drivers multiple times - but does not seem to be helping. when I connect the phone to the laptop - it is in clockworld recovery mode with the initial set of options.
That sounds all correct. Go back into the SDK manager and under extras there are a few drivers. Check and install those. Try it again.
If that doesn't work, I'll send you the necessary drivers as soon as I get a chance.
Sent from my Galaxy SIII using xda app-developers app
ibanezbass said:
That sounds all correct. Go back into the SDK manager and under extras there are a few drivers. Check and install those. Try it again.
If that doesn't work, I'll send you the necessary drivers as soon as I get a chance.
Sent from my Galaxy SIII using xda app-developers app
Click to expand...
Click to collapse
Thanks ibanezbass. From the extras I downloaded Google USB drivers/Web drivers. But still no avail. I have the latest drivers from ATT downloaded. But for some reason, the phone wont recognized when I do the "adb shell" .
pkirangi said:
Thanks ibanezbass. From the extras I downloaded Google USB drivers/Web drivers. But still no avail. I have the latest drivers from ATT downloaded. But for some reason, the phone wont recognized when I do the "adb shell" .
Click to expand...
Click to collapse
I was able to flash my SG3 with stock ROM using ODIN in download mode. So back in shape. Thanks for everybodies suggestion on this.
As a bonus, AT&T had a RMA and were ready to exchange it for a new phone, which I am declining now.
Ah, I'm sorry to hear that you had to use ODIN and wipe all your data. I solved your driver problem. I apologize about the length of time it took. If you ever need to fix the build.prop again, I've updated my OP to include the driver section. Happy modding!
ibanezbass
ibanezbass said:
Ah, I'm sorry to hear that you had to use ODIN and wipe all your data. I solved your driver problem. I apologize about the length of time it took. If you ever need to fix the build.prop again, I've updated my OP to include the driver section. Happy modding!
ibanezbass
Click to expand...
Click to collapse
No Worries. Thanks for your help.
got a major problem
Hi guys I have yet another crazy issue I am faced with
My Samsung galaxy tab p3110 model has just got the black screen of death after having replaced build.Prop file however I did create a backup of the build. Prop file only its inside the root folder of the tablet at stake. I only seem to have access to Odin mode and I need a way of moving the original built.Prop file back in its place. Does anyone here have any ideas of how I may go about doing this without risking screwing up my tablet further
Any help is greatly appreciated
Gloftking said:
Hi guys I have yet another crazy issue I am faced with
My Samsung galaxy tab p3110 model has just got the black screen of death after having replaced build.Prop file however I did create a backup of the build. Prop file only its inside the root folder of the tablet at stake. I only seem to have access to Odin mode and I need a way of moving the original built.Prop file back in its place. Does anyone here have any ideas of how I may go about doing this without risking screwing up my tablet further
Any help is greatly appreciated
Click to expand...
Click to collapse
You're in the i747/i747m Galaxy S3 forum, so use anything you find here with care. You might want to consult the Galaxy Tab forum for more device specific advice; however, fixing a build.prop brick should be a pretty generic procedure for an android device.
Here is a guide for fixing build.prop errors using adb. You'll probably have to track down different drivers than the ones linked to that thread for your device unless they happen to be generic Samsung drivers. Here's a minimal adb installer so you don't have to mess with the whole Android SDK, just to use one tiny tool
If you have a custom recovery or wouldn't mind using Odin to install one (again, consult your device's forum for specific issues - this may or may not be safe depending on your bootloader), you could just use the file tools built into TWRP or Aroma file manager to replace your modified build.prop with your backup. Be sure to set permissions to 644 after moving the file or you might still be bricked. This might be easier than getting adb working or it might not, depends on your comfort level with Odin and how tricky your device is to mod safely. I see custom ROMs in the Galaxy Tab forum, so it definitely can be done.
Slightly confused
Thanks for your quick response
However I am still a bit confused. Does flashing TWRP recovery through odin mean that all the data and apps currently installed on the tablet will be wiped
Gloftking said:
Thanks for your quick response
However I am still a bit confused. Does flashing TWRP recovery through odin mean that all the data and apps currently installed on the tablet will be wiped
Click to expand...
Click to collapse
Your data and apps will not be affected by flashing TWRP; that Odin package will just be a recovery, not a full firmware update like they are a lot of the time. It will just replace your stock recovery with a custom recovery that has more functionality.
TWRP basically gives you a mini operating system on your phone for creating backups or flashing ROMs. TWRP also has some file tools in its Advanced tab you could use to copy your build.prop backup to /system and set the permissions, so you should be able to use it to fix your soft brick. It is independent of your ROM, so it will unaffected by your main system's build.prop error. There should be a hardware key combo you hold with the tablet off to boot into recovery. A lot of the time its vol up + power (i747 has a physical home button and recovery boot is vol up + home + power).
Thanks
jason2678 said:
Your data and apps will not be affected by flashing TWRP; that Odin package will just be a recovery, not a full firmware update like they are a lot of the time. It will just replace your stock recovery with a custom recovery that has more functionality.
TWRP basically gives you a mini operating system on your phone for creating backups or flashing ROMs. TWRP also has some file tools in its Advanced tab you could use to copy your build.prop backup to /system and set the permissions, so you should be able to use it to fix your soft brick. It is independent of your ROM, so it will unaffected by your main system's build.prop error. There should be a hardware key combo you hold with the tablet off to boot into recovery. A lot of the time its vol up + power (i747 has a physical home button and recovery boot is vol up + home + power).
Click to expand...
Click to collapse
BTW is there a default recovery partition that your supposed to be able to access because when I press and hold "power + volume up" the tab just restarts and shows the Samsung logo over and over again. Also I could swear that I did install TWRP at the time when I rooted but there is no sign of it.

[Q] Nexus 7 Newb would like feedback on plan for setting up my device

I recently picked up a Nexus 7, unlocked it, and loaded KitKat yesterday with the factory image. I have set the device up now and would like to use a custom backup to take an image of the 7 and then store that image off of the device on an external drive since I only have a 16gb 7.
I have downloaded Clockworkmod ROM Manager to do this. Is it easily feasible to make a stock image and then transfer the image to an external drive? I'm having an issue installing the Clockworkmod Recovery tool, but I posted a question about that in a different forum.
Any advice would be appreciated.
Thanks,
Rick
I presume you have a custom recovery installed in addition to the ClockWorkMod Manager? If not, use the WugFresh Nexus Root Toolkit to install that, then boot into the recovery and select the backup option. It will create a folder on the root of your device called clockworkmod which will contain your backups. Just copy that to your PC, and transfer it back to the device when you need it.
C5Longhorn said:
I recently picked up a Nexus 7, unlocked it, and loaded KitKat yesterday with the factory image. I have set the device up now and would like to use a custom backup to take an image of the 7 and then store that image off of the device on an external drive since I only have a 16gb 7.
I have downloaded Clockworkmod ROM Manager to do this. Is it easily feasible to make a stock image and then transfer the image to an external drive? I'm having an issue installing the Clockworkmod Recovery tool, but I posted a question about that in a different forum.
Any advice would be appreciated.
Thanks,
Rick
Click to expand...
Click to collapse
I've used ROM Manager a fair amount for creating backups. It works well, but like was said previously, you'll need to flash a custom recovery. The two main choices are Clockworkmod (CWM) and Team Win Recovery Project (TWRP). CWM works well with ROM Manager in my experience on another device.
I've found TWRP much easier to use though. It features a touch interface. You'll be able to customize the backup file name if you initiate a backup in recovery mode. The file name will also allow spaces, while CWM doesn't.
Check it out at teamw.in/project/twrp2. I think the recoveries are the same, but make sure you select the correct Nexus 7 model (LTE or Wi-Fi). You can flash the image in the bootloader using fastboot. Instructions are avalaible on the TWRP website.
Wrngway said:
I've used ROM Manager a fair amount for creating backups. It works well, but like was said previously, you'll need to flash a custom recovery. The two main choices are Clockworkmod (CWM) and Team Win Recovery Project (TWRP). CWM works well with ROM Manager in my experience on another device.
I've found TWRP much easier to use though. It features a touch interface. You'll be able to customize the backup file name if you initiate a backup in recovery mode. The file name will also allow spaces, while CWM doesn't.
Check it out at teamw.in/project/twrp2. I think the recoveries are the same, but make sure you select the correct Nexus 7 model (LTE or Wi-Fi). You can flash the image in the bootloader using fastboot. Instructions are avalaible on the TWRP website.
Click to expand...
Click to collapse
TWRP will also allow you to backup, restore, and flash from a USB drive if you get a USB OTG cable.
Sent from my SM-P600 using XDA Premium HD app
nrage23 said:
TWRP will also allow you to backup, restore, and flash from a USB drive if you get a USB OTG cable.
Sent from my SM-P600 using XDA Premium HD app
Click to expand...
Click to collapse
I don't think TWRP is working with 4.4 build number KRT16S
Can anyone confirm? I just tried to flash the latest TWRP recovery 2.6.3.1 and it was not working when I rebooted into recovery. I was still getting the stock image.
Rick
C5Longhorn said:
I don't think TWRP is working with 4.4 build number KRT16S
Can anyone confirm? I just tried to flash the latest TWRP recovery 2.6.3.1 and it was not working when I rebooted into recovery. I was still getting the stock image.
Rick
Click to expand...
Click to collapse
TWRP working fine here..
C5Longhorn said:
I don't think TWRP is working with 4.4 build number KRT16S
Can anyone confirm? I just tried to flash the latest TWRP recovery 2.6.3.1 and it was not working when I rebooted into recovery. I was still getting the stock image.
Rick
Click to expand...
Click to collapse
Just backed up stock KitKat to a thumb drive and flashed newest 4.4 Omni Rom from thumb Drive. Use the WugFresh Nexus Toolkit to flash recovery. It makes it much simpler.
C5Longhorn said:
I don't think TWRP is working with 4.4 build number KRT16S
Can anyone confirm? I just tried to flash the latest TWRP recovery 2.6.3.1 and it was not working when I rebooted into recovery. I was still getting the stock image.
Rick
Click to expand...
Click to collapse
From what I've read, the stock recovery for KRT16S is the same as KRT16O. I'm running the latest TWRP on KRT16O without issue.
Assuming your bootloader is unlocked, you shouldn't have an issue. Can you list the steps you're using to flash recovery? Maybe you're missing something.
If you have the correct driver on your computer and you're using fastboot, the command should be "fastboot flash recovery [insert recovery file name].img" from the fastboot directory.
Wrngway said:
From what I've read, the stock recovery for KRT16S is the same as KRT16O. I'm running the latest TWRP on KRT16O without issue.
Assuming your bootloader is unlocked, you shouldn't have an issue. Can you list the steps you're using to flash recovery? Maybe you're missing something.
If you have the correct driver on your computer and you're using fastboot, the command should be "fastboot flash recovery [insert recovery file name].img" from the fastboot directory.
Click to expand...
Click to collapse
Ok, maybe I was doing something wrong. The command line indicated it was installing correctly when I flashed it. However, when I rebooted to recovery it was never TWRP.
I just installed Clockworkmod Recovery so it was probably an error on my end.
Now, since I have made a backup, how can I identify where it is stored? I would like to move it to my computer since I only have a 16gb 7.
Thanks for all the replies,
Rick
I can't remember the default location. I think it's sdcard/clockworkmod/backups.
If you remember the file name, you can just search for that using ES File Explorer or a similar app.
Wrngway said:
I can't remember the default location. I think it's sdcard/clockworkmod/backups.
If you remember the file name, you can just search for that using ES File Explorer or a similar app.
Click to expand...
Click to collapse
great, thanks for all the help. I will probably reflash back to stock and then rebuild my device and backup. I have OCD about making sure I've got the cleanest install and right now don't know that for sure since it's been trial and error.
They are saved in /mnt/shell/emulated/clockworkmod/backup
They are hidden from other apps, so you need a file explorer with root to move them.
Great, thank you for the reply. The help from folks on the forum has been fantastic and really helps a newb.
Rick

How do I backup my stock recovery?

I want to be able to flash my stock recovery when I no longer want TWRP or CWM. How would I go about doing this?
tcmoffitt said:
I want to be able to flash my stock recovery when I no longer want TWRP or CWM. How would I go about doing this?
Click to expand...
Click to collapse
Hello,
Thanks for using XDA Assist.
What device do you have?
___
v7
XDA Assist
v7 said:
Hello,
Thanks for using XDA Assist.
What device do you have?
___
v7
XDA Assist
Click to expand...
Click to collapse
HTC One m8 Tmobile
Thanks for the help guys I really appreciate it. This forum is just so helpful............. ---____---
Which T-Mobile ?
If it is T-Mob US .. there's a dedicated section for T-Mob US and you can find any info there.
tcmoffitt said:
Thanks for the help guys I really appreciate it. This forum is just so helpful............. ---____---
Click to expand...
Click to collapse
This is not possible to backup your stock recovery. When you need that you can download it simply (base on your phone's build number). Also you can extract stock recovery frome your ota zip update(the file with img format inside of firmware folder)
Arsinn said:
This is not possible to backup your stock recovery.
Click to expand...
Click to collapse
Actually, the following usually works:
This has to be done before flashing custom recovery. Unlock bootloader, then fastboot boot recovery.img
With "recovery.img" being a TWRP file located in your fasboot folder. This will boot into TWRP without actually flashing it. From there, you can pick recovery in the backup options, to backup stock recovery.
But yes, I agree that stock recovery images are pretty easy to obtain from these forums, or extracting from a OTA or ROM.zip.
redpoint73 said:
Actually, the following usually works:
This has to be done before flashing custom recovery. Unlock bootloader, then fastboot boot recovery.img
With "recovery.img" being a TWRP file located in your fasboot folder. This will boot into TWRP without actually flashing it. From there, you can pick recovery in the backup options, to backup stock recovery.
But yes, I agree that stock recovery images are pretty easy to obtain from these forums, or extracting from a OTA or ROM.zip.
Click to expand...
Click to collapse
Hi, redpoint73...
Maybe I'm missing something here, but I'm not seeing an option to backup the Recovery in TWRP 2.8.7.0... Just Boot, Cache, System, Data and Android Secure are available (see attached screenshot). I remote booted TWRP from my laptop, as I did when I rooted Marshmallow around a fortnight ago, in order to keep the stock recovery intact.
It would certainly be useful to be able to backup the stock recovery via TWRP... I just haven't found a way of accomplishing it .
-----
But a possible option to backup the stock recovery would be to use the Flashify app...
Remote boot TWRP from your PC, acquire root, and then run Flashify...
Flashify PlayStore link...
https://play.google.com/store/apps/details?id=com.cgollner.flashify
XDA discussion thread...
http://forum.xda-developers.com/showthread.php?t=2349847
This app uses <dd=if/of> commands to backup and potentially restore the boot and/or recovery images.
Although it does require root to work.
I've used Flashify on my Nexus 7 and Nexus 9 in the past, but never on my M8, except to backup... never to restore, so I cannot personally vouch for it's safety on the M8.
-----
What I'm unsure of about Flashify...
@redpoint73, @ckpv5, maybe you guys could shed some light on this...
Would such a <dd=if/of> created backup of stock recovery be flashable via fastboot?
And would it be safe to do so?
I know that TWRP uses <dd=if/of> commands, having looked through TWRPs logs... but I'm not quite sure how fastboot works when it comes to flashing stuff, and I'm very wary about doing it myself or recommending it for others.
Normally, you'd just use the Flashify app to restore any recovery/boot.img backups you've previously made...
But Flashify requires root to work, and with an unrooted system, this is isn't viable. So could one use fastboot in the normal way to flash such a previously made backup of the stock recovery?
-----
Anyhow, it's not critical at the moment for me, because I've not flashed TWRP to my M8, my stock recovery remains intact.
-----
I would recommend anybody reading this seeking to root their Marshmallow M8 to just remote boot TWRP from their PC with fastboot boot twrp.img (ie., don't actually flash it), perform an unrooted Nandroid backup first...
...and then flash Chainfire in the usual way.
This leaves the stock recovery intact, which will be required for future OTAs.
And there still might be some...
My Nexus 9 receives monthly security patches from Google (probably after the StageFright debacle of last year), and it may well be that the M8 will also continue to receive security patches, despite it being nearly two years old.
So you need to be ready... with an unrooted/untouched Nandroid of your own creation and the stock recovery.
I know that Chainfires systemless root method is supposed to address this issue, but if you're going to mess with system, you should have a Nandroid backup anyway...
...just in case.
Rgrds,
Ged.
Funny, I use the fastboot boot option to boot into TWRP saving my original recovery.

Categories

Resources