Related
First things first, if you flashed a previous version of Clockwork Recovery using Odin, FLASH BACK TO A STOCK KERNEL using this Odin package:
http://koush.tandtgaming.com//test/kernel-captivate-stock.tar.md5
This recovery is *very* safe to use. It does NOT flash your kernel; it is a completely uninvasive recovery method.
How it works: The recovery is packaged as an update.zip that you run from STOCK recovery. The update.zip unpacks Clockwork Recovery onto the ramdisk and restarts recovery. When you reboot, it reverts back to the original, unmodified, stock recovery. So, you will need to keep the recovery on the root of your SD card as an update.zip, and apply the zip every time you want to start Clockwork.
HOWEVER, if you use ROM Manager, all of the recovery installation and management instructions are done for you!
Installation instructions:
Download ROM Manager from the Market.
Flash Recovery.
Choose Captivate as your phone.
Accept the Superuser prompt.
Use ROM Manager to create a Backup.
On the very FIRST boot of Clockwork, you may need to manually select "reinstall packages" if Clockwork does not start. You should only ever have to do this once. It will be automatic from then on.
Watch the backup go!
That's it! This is completely painless and safe! There is no need for Odin anymore to replace the recovery or flash updates!
If you appreciate my work, please buy the Premium version of ROM Manager!
Sweet!
Nandroid'd!
Ah yeah....smooth like butter baby!!! Great work once again. Remember to donate people!!!
big99gt said:
Ah yeah....smooth like butter baby!!! Great work once again. Remember to donate people!!!
Click to expand...
Click to collapse
For us Noobs, can we get more information on where and when to use this?
In reading everything I get some of it, but not all. This is my first hackable android phone, so I am still learning the lingo.
With other phones, I would just Flash a custom ROM or Flash Factory ROM back.
So how do ROM Manager and Clockwork recovery come into play?
Are there any tutorials - not that just give step by step (like above) but explain what is happening in each step or why?
alphadog00 said:
For us Noobs, can we get more information on where and when to use this?
In reading everything I get some of it, but not all. This is my first hackable android phone, so I am still learning the lingo.
With other phones, I would just Flash a custom ROM or Flash Factory ROM back.
So how do ROM Manager and Clockwork recovery come into play?
Are there any tutorials - not that just give step by step (like above) but explain what is happening in each step or why?
Click to expand...
Click to collapse
The long and short of it is that you can now flash ROMs and make backups, and restore, without your computer.
The recovery is the tool that lets you do the backups and installations. ROM Manager is a convenient Android front end to the recovery.
After these steps you won't really have to "hack" your phone lol. Root your phone and download Rom Manager from the Android market...then have it flash a recovery (the first selection at the top) choose your device when prompted. Now after that finishes select "reboot into recovery" and as the above post states you may need to select "reinstall packages" (I did). Once that goes through, you'll see your new custom recovery menu. DO A NANDROID BACKUP of your current Rom as soon as you can....then (as long as your current rom isn't messed up, if its stock your fine) from there on out you can play as much as you want with very little risk of bricking your phone. There are others who can explain it better but your stuck with me till they chime in lol. Its a very easy process and nearly foolproof.
Koush said:
That's it! This is completely painless and safe! There is no need for Odin anymore to replace the recovery or flash updates!
If you appreciate my work, please buy the Premium version of ROM Manager!
Click to expand...
Click to collapse
Awesome work! Premium version has been purchased by me. Thank you for the efforts.
Didn't work at first for me.
I installed Rom Manager (premium)
Installed CW recovery
Accepted SU
Tried to backup from within Rom Manager
I got a "Can't find update.zip" message.
When I rebooted and opened Rom Manager again, I got the "Error Occured" message, but it locked up on me and became unresponsive.
I uninstalled Rom Manager, rebooted, then reinstalled. I flashed CW recovery again, rebooted normally, opened rom manager again, and flashed CW recovery again.
After that I was able to use rom manager to reboot into recovery and backup.
Not sure if mine was just a fluke or what, but I figured I would share.
MSigler said:
Didn't work at first for me.
I installed Rom Manager (premium)
Installed CW recovery
Accepted SU
Tried to backup from within Rom Manager
I got a "Can't find update.zip" message.
When I rebooted and opened Rom Manager again, I got the "Error Occured" message, but it locked up on me and became unresponsive.
I uninstalled Rom Manager, rebooted, then reinstalled. I flashed CW recovery again, rebooted normally, opened rom manager again, and flashed CW recovery again.
After that I was able to use rom manager to reboot into recovery and backup.
Not sure if mine was just a fluke or what, but I figured I would share.
Click to expand...
Click to collapse
Titanium Backup did that to me also the first time I ran it....I've had quite a few freezes and slowdowns when opening a program for the first time and waiting for SU to kick in.
It should also be noted that when you chose to partition the sdcard via the recovery menu, it partitions the internal sdcard and not the external.
Maybe that can be made an option? I would like to do my nandroid backup to my external card so I have it for safe keeping.
Everything else working as expected, I enabled advanced options and downloaded the superuser package (from Extras) just to test things. Havent experienced any problems other than the sdcard wipe (which wasnt totally unexpected).
If something should happen to your phone (brick, unrecoverable error, etc), how can we reboot into this custom recovery to reflash the nandroid backup? Can we get into it via adb (adb reboot recovery)?
Yeah, having an external SD Nandroid would be a great option. Not just for safekeeping, but for easy transfer in case of hardware loss or replacement.
dweebs0r said:
It should also be noted that when you chose to partition the sdcard via the recovery menu, it partitions the internal sdcard and not the external.
Maybe that can be made an option? I would like to do my nandroid backup to my external card so I have it for safe keeping.
Everything else working as expected, I enabled advanced options and downloaded the superuser package (from Extras) just to test things. Havent experienced any problems other than the sdcard wipe (which wasnt totally unexpected).
If something should happen to your phone (brick, unrecoverable error, etc), how can we reboot into this custom recovery to reflash the nandroid backup? Can we get into it via adb (adb reboot recovery)?
Click to expand...
Click to collapse
I just did a reboot into recovery mode (the normal way, not with rom manager) and I had to click "reinstall packages" to get into the ClockworkMod recovery menu. So I'm not sure but I'm guessing (hoping) that its still available if we run into problems later.
Yep. It's pretty much how the Droid and N1 people are used to doing it anyway.
Clockwork is hella handy to manage and switch between working ROMs on the fly, as well as triggering recovery mode without keypress acrobatics, but having update.zip on the SD card to fall back on using the normal restore and the stock kernel is great in case of semi-bricking, and as this last week has shown us, the Galaxy phones are a bit prone to this.
THANK YOU!!! Been waiting for this since I got the phone, you are the man, I'll be adding to your Paypal account shortly!
Works like a charm. Thanks Koush!
Thank you. I am new to the scene, but looks like I chose the right hardware for hacking. The swift and easy way in which I have been able to advance my freedom on this gorgeous hardware makes me forget for a while that I am on AT&T, home of the fruit carrying zombie army.
Sweet! Can't wait to try this on my phone later tonight. Will deff be buying ROM Manager Pro
Thanks for this...I just bought the premium version...Since this is my first Android phone I have a question. I previously rooted my phone and uninstalled alll the AT&T bloatware, My question is about the backup I just made using this. If I restore the backup will it restore a rooted backup with out all the AT&T bloatware? Also when I ran the backup I go 2 messages at the end
No /sdcard/.andriod_secure found. Skipping backup of applications on external storage.. Is this normal?
No sd-ext found. Skipping backup of sd-ext. Is this normal?
Also I now have 2 ROM Manager icon in my application screens. 1 will open the program and the other tells me that the aplication is not installed on my phone. I tried to delete that icon but it won't go away, Any ideas? FIXED..I rebooted my phone and the extra icon went away...
Thanks for all help and these great apps...
jhernand1102 said:
Thanks for this...I just bought the premium version...Since this is my first Android phone I have a question. I previously rooted my phone and uninstalled alll the AT&T bloatware, My question is about the backup I just made using this. If I restore the backup will it restore a rooted backup with out all the AT&T bloatware? Also when I ran the backup I go 2 messages at the end
No /sdcard/.andriod_secure found. Skipping backup of applications on external storage.. Is this normal?
No sd-ext found. Skipping backup of sd-ext. Is this normal?
Thanks for all help and these great apps...
Click to expand...
Click to collapse
i got the same message, im assuming that you dont have an external sd card thats why it generated the message...
rabbivj said:
i got the same message, im assuming that you dont have an external sd card thats why it generated the message...
Click to expand...
Click to collapse
I do have one in my phone but there is nothing installed on it yet..maybe that's why..
So I have been trollin through a bunch of threads and searching before I ask. I am rooted running Stupidfast v1.23 and jt super clean rom on DI01. I was reading through flashing back to stock package via oden, but i noticed you need a stock nandroid recovery. I currently have CW. Do I need to get the stock nandroid or just flash the package?
If this has been asked a million times, I am sorry. Please direct me where to go.
Anyone?? There has to be an answer out there somewhere...
I believe if you go to the development forum and check the stickies there a post with the Odin to stock info that has the stock nandroid in it. I think that's where it is - I go to so many forums I can never remember where I saw what. I'm on my phone right now but I will check later to make sure.
Sent from my SCH-I500 using XDA App
You don't need a nandroid backup if you just want to go back to stock.
http://forum.xda-developers.com/showthread.php?t=782204
Or, flash adrynalyne's DI01 Odin package to get you back to 2.1-update1.
http://forum.xda-developers.com/showthread.php?t=867648
Stock nandroid is in the dev forum. Probably a few pages in though.
I'm retarded. I meant to say do i need a stock recovery (not stock nandroid) or does the package provide all of it.
A Nandroid backup is just a backup image taken through CW Recovery. You can't have one without the other (at least, not on this phone -- some other devices have different custom recovery tools you can choose to use)
But that doesn't matter anyways, because Odin flashes work regardless of what you have or don't have on your phone. It's like restoring Windows from a recovery disk -- it wipes and replaces everything. That'd be why it's named after a god. Doesn't matter if you're rooted, doesn't matter if you have CWR installed, it'll wipe the slate clean and start you off fresh.
P.S. I'm not sure "trollin" means what you think it means. If you'd gone trolling in a bunch of threads, it's highly unlikely anyone would help you.
Trolls smell bad, live under bridges, and cause hazard to passers thorough. I knew what you meant.
You wanted a stock nandroid recovery. That brings your phone back to before you messed it up. Nandroid is a backup program that is run via Clock Work Recovery (which can be run from recovery mode - to run, flash a special clockwork recovery in odin, install rom manager app, run that, click the install button which in turn downloads and copies an update.zip file to the root of your sd card, then from recovery mode *vol +&- while powering up* you ' install' update.zip which essentially runs it)
You run nandroid from therein... or from the Rom Manager front end.
Actually you would run it, except you cannot.
# Nandroid is a BACKUP program. You need to have made your own image before hand for it to be helpful! #
However, thanks to Adrynalyne, you have another option for restoring your phone to stock:
http://forum.xda-developers.com/showthread.php?t=867648
A caveat. It is a large file, and somewhat of a strain to host. You only need to use it if your phone is totally borked and you do not know what else to do. Otherwise, you can often repair your woes by opening up CWR and using the clear data commands (which do not touch the sd card) & the install from sd card option, which in turn lets you find a rom you previously installed on your sd card and rerun it. Unless of course you installed voodoo, in which case you need a whole other thread before proceeding....
SIDE NOTE: Here its the classic piecewise restore I used back in the day, which includes stock kernel, stock system rom, and Odin:
http://forum.xda-developers.com/showthread.php?t=782204
Unfortunately the only di01 (first vzw updated modem) posted publicly is the one in the first link. If you need to replace your modem/radio/baseband, then you need to find dj05 separately, or simply have used adrynalyne's restore (linked up top) in the first place.
However, when you do get your phone back to happy - my tired finger asks you to do just one thing:
Run the "Backup Current ROM" option the moment you install Rom Manager - or don't install it!
Swyped w/ XDA App. When in doubt, mumble. Nandroid: Don't use Rom Manager without it.
So I rooted my friends Vibrant last night. I rooted my Vibrant a few months ago and didn't run into this issue. But I rooted using the same program "Vibrant One Click Root/Unroot" and followed the same steps as I did when I rooted my phone. However, once I installed ROM Manager and installed Clockworkmod Recovery and booted into recovery and clicked reinstall packages, the phone just rebooted. I remember when I rooted my phone when I clicked reinstall packages it did its thing, then went back to the blue recovery screen. Then I clicked reinstall packages again and it took me to the green recovery screen where I was able to then install zip from sd. My friends phone just keeps booting to the blue recovery screen where I can only reboot now, reinstall packages, clear user data, and clear cache. He had to leave so I did not have time to troubleshoot.
Any ideas as to if I missed a step? Any input would be appreciated.
Thanks in advance!
Sorry for the n00bish attitude, if this was my phone, I would put a little more effort into finding the answer. I'm just trying to get this done as soon as possible.
Are you using the actual clockwork app to boot into recovery? If so id just go back to stock and redo the root
Sent from my SGH-T959 using XDA App
creglenn said:
Are you using the actual clockwork app to boot into recovery? If so id just go back to stock and redo the root
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
Yeah, I went into ROM Manager and clicked "boot into recovery". Where it brings me to the blue recovery screen. So you think I should unroot then re root? Because everything with the root seemed to work fine. It installed superiser and I had no problems downloading Titanium Backup or ROM Manager and allowing superuser permissions. Which made me think I was just forgetting something...but I might just try that. Thanks!
if your rooting stock 2.2 your gonna need a modded 3e recovery or one of supercurios voodoo kernels with CWM & root already built in. Superoneclick will root stock 2.2. If its 2.1, then you may need to hit reinstall packages a couple of times to get it to take.
drscott333 said:
So I rooted my friends Vibrant last night. I rooted my Vibrant a few months ago and didn't run into this issue. But I rooted using the same program "Vibrant One Click Root/Unroot" and followed the same steps as I did when I rooted my phone. However, once I installed ROM Manager and installed Clockworkmod Recovery and booted into recovery and clicked reinstall packages, the phone just rebooted. I remember when I rooted my phone when I clicked reinstall packages it did its thing, then went back to the blue recovery screen. Then I clicked reinstall packages again and it took me to the green recovery screen where I was able to then install zip from sd. My friends phone just keeps booting to the blue recovery screen where I can only reboot now, reinstall packages, clear user data, and clear cache. He had to leave so I did not have time to troubleshoot.
Any ideas as to if I missed a step? Any input would be appreciated.
Thanks in advance!
Sorry for the n00bish attitude, if this was my phone, I would put a little more effort into finding the answer. I'm just trying to get this done as soon as possible.
Click to expand...
Click to collapse
All you should need to do is hit reinstall packages again. When you do it the first time it will boot back into the same blue recovery again. Hit it once more then it should boot to the green recovery. If that doesn't work you probably have a bad zip file on the phone. In which case you'd re flash CWM again.
If you're not getting the superuser request when you flash CWM then root didn't take. Make sure root works first.
Did you actually run install cwm from rom manager so the update. zip is there?
Just make sure with Astro or another file manger that you have a .zip file and it should be 1.72 MB in size and you want that on your internal SD card....Then when you boot to recovery it should let you hit reinstall packages with no problem
I'm new here, but I have flashed 3 vibrants since last week. I had the same problem you did.
When I flashed my phone last week it was stock 2.2, so I had to flash the modified 3e recovery which fixed my issue getting into CWM to install my ROM. Today i was flashing a co-worker's vibrant who also was on stock 2.2. However, on his it would keep rebooting when reinstalling packages, even though i did the 3e recovery flash. I ended having to Odin back to 2.1 on his phone before i could flash the new ROM.
I just used AIO Vibrant Toolbox 2.5. Hope this helps.
Thanks for all the feedback!! I don't have the phone with me to check if the update.zip folder was for sure there. But if it is, I'll try reinstalling the packages again. Otherwise I'm just going to unroot and try rerooting with the AIO Toolbox. I'm not going to be able to do this until tomorrow though since our work schedules were pretty much opposite today. But once again, huge thanks to all of you!!! However I've never unrooted before...if I haven't flashed any ROMs, I shouldn't have any problems should I? Just click unroot?
Let me give you the timeline. A few days ago I rooted the device using the method outlined in this video. I verified my root status with Root Checker and my device was indeed successfully rooted. I installed BusyBox (basic) and TitaniumBackup Pro. Made a backup of my user apps+data to the external SD. I then downloaded Goomanager and used it to install the latest version of TWRP.
All of this was successful. I went into TWRP and created a NAND backup. I backed up: Boot, System, and Data. I did not back up EFS, Preload, Cache, or Recovery.
I performed a wipe and format of user data. Flashed to SlimBean, had some issues. Wiped. Flashed CM10.1. Again, some issues. I decided I'm going to wait a while for these roms to stabilize a bit before I try using any of them on a regular basis. I wiped and restored my original NAND backup of my stock rooted ROM. The restore appeared to go fine. I don't know if this will have anything to do with anything but I went ahead and ran a PRL and Profile update. The device was functioning okay until...
I noticed that the time was off. The lockscreen time was correct but the time in the upper right status bar was stuck at about an hour before. I decided I'd just try restarting the device to see if that fixed anything. Well when I did it wouldn't boot. I'd get stuck on the first Samsung Galaxy S4 logo screen. Took the battery out, waited, put it back in, restarted. Still... stuck on the logo screen. I tried booting into recovery (Vol. Up + Power). The black SGS4 logo would come up with a tiny blue notification in the upper left corner (Recovery Boot). Then the device would restart and get stuck at the SGS4 logo screen again.
Eventually I was able to get it to boot to TWRP (maybe I was just holding the power button too long?)
I wiped. It failed. I tried again. It worked. I recovered my CM10.1 setup and it's been working "okay" on CM10.1 ever since.
I want to get back to my stock rooted rom but I want to understand what happened first.
Anyone? Please?
Stu_Gots said:
Anyone? Please?
Click to expand...
Click to collapse
What version of TWRP were you on? If it was 2.5.0.3 then there's your culprit. That version of TWRP is known to have issues. You need to flash version 2.5.0.2 found here.......http://forum.xda-developers.com/showthread.php?t=2277480. Scroll down to install Alternate recovery and download the 2.5.0.2 .img file.
Once you've downloaded the file, go to your Goo Manager folder and delete the file there. Then paste the file you downloaded from the above link into that same folder. After that, open Goo Manager and go to Install Recovery Script. It should see the file you have in your folder and then download it from their server. Make SURE it says you are downloading 2.5.0.2. Once Goo does its thing, reboot into Recovery and make sure you're running the 2.5.0.2 version of TWRP. Now you can flash all you want because it will function properly. I would first download a stock rom and clear out any skeletons in the closet. Then go into TWRP and wipe EVERYTHING. This includes data, dalvik cache, cache, system and then factory reset as well 3 times each. MAKE SURE you don't delete the internal or external sd cards. Flash the stock rom, set it up how you wish, make a nand of that file( Include EFS and Preload because it can't hurt to be safe) and then flash whatever you like. You should be good to go.
---------- Post added at 01:20 PM ---------- Previous post was at 01:17 PM ----------
Stu_Gots said:
Anyone? Please?
Click to expand...
Click to collapse
Another question I have is what version of software/firmware are you on? Go to Settings/More/About Phone and check what your software and baseband versions are? If its MDC, then rooting via MotoChopper was a good method to use. If it says MDL, that could also be the reason why the phone was acting so quirky. There is a new method to rooting if you are on MDL and it's also found in Mudavo's thread found here...http://forum.xda-developers.com/showthread.php?t=2277480
For the record. I was using the phone stock rooted for a week or so without any problems. I hadn't had any issues until after restoring the backup I made in TWRP. When I wiped prior to installing SlimBean/CM10.1 I did the standard auto-wipe AND I wiped data
Oh yeah. To answer your questions.
TWRP Version: 2.5.0.2
Software/Baseband versions: L720VPUAMDL
Earlier today I just tried wiping (default TWRP 2.5.0.2). Then restoring the backup again. This was so I could get you the information on what software/baseband version I was on. When the restore completed I went to reboot. The phone stuck on the SGS4 logo screen. I then rebooted in recovery and wiped as before and then I wiped data. The phone was then able to boot into the stock rooted rom. I have so far noticed the times being out of sync from the lock screen and the status bar. I reset the phone again. Stuck at SGS4 logo again.
My trouble getting back into TWRP was my own fault. I was holding the buttons down too long. I can get back into TWRP no problem.
So. What are my options at this point? I would like to be on the latest stock everything... with root and stock wireless tether enabled. The way I was. If I can't restore my backup then I'm going to have to reflash the stock rom. I can't seem to find a comprehensive index of information. Every time I think I've got something figured out I stumble on new bits of information.
Stu_Gots said:
For the record. I was using the phone stock rooted for a week or so without any problems. I hadn't had any issues until after restoring the backup I made in TWRP. When I wiped prior to installing SlimBean/CM10.1 I did the standard auto-wipe AND I wiped data
Oh yeah. To answer your questions.
TWRP Version: 2.5.0.2
Software/Baseband versions: L720VPUAMDL
Earlier today I just tried wiping (default TWRP 2.5.0.2). Then restoring the backup again. This was so I could get you the information on what software/baseband version I was on. When the restore completed I went to reboot. The phone stuck on the SGS4 logo screen. I then rebooted in recovery and wiped as before and then I wiped data. The phone was then able to boot into the stock rooted rom. I have so far noticed the times being out of sync from the lock screen and the status bar. I reset the phone again. Stuck at SGS4 logo again.
My trouble getting back into TWRP was my own fault. I was holding the buttons down too long. I can get back into TWRP no problem.
So. What are my options at this point? I would like to be on the latest stock everything... with root and stock wireless tether enabled. The way I was. If I can't restore my backup then I'm going to have to reflash the stock rom. I can't seem to find a comprehensive index of information. Every time I think I've got something figured out I stumble on new bits of information.
Click to expand...
Click to collapse
Honestly, at this point, you need to unroot and reroot again using the method in Mudavo's post. You used the wrong method to root with motochopper. Motochopper was only for the MDC version. That could be why you are having the issues that you are. That's all I can suggest at this point. Start with a clean slate and try it again. Trust me you aren't the only one to do this. I've done it a few times myself. It sucks but at least you know you did everything right. You're going to have to flash a stock MDC rom that came shipped with the phone via Odin. Then take the OTA to update your phone to MDL and then just follow Mudavo's post to root the proper way when you're on the MDL version.
What about the TWRP recovery I have installed? Am I going to have to deal with that in some way?
What are the advantages of Odin over TWRP? I'm not trying to question your judgment btw. I'm legit curious because I've only ever used TWRP to
Flash roms.
Sorry for all the dumb questions.
Btw . While I was waiting for your reply I tried trouble shooting a bit myself. To see if I could fix my own problem. I found a thread with MDL stock rooted and a bunch of firmware and kernel files. I flashed to it in TWRP and it's working reasonably well so far. I'm still dtf for other methods if mine is somehow flawed.
My method didn't work. When I restarted from TWRP (after no other issues) the phone for stuck.
The phone was restarted several times and booted fine. It wasn't until I restarted into TWRP then and then back into normal boot that I had issues
this time. So I'm going to do what you suggested. I just have a couple questions.
If my rom/recovery is corrupted how do I fix my problem. I would need a working rom AND recovery to flash stock rom. I'm not sure where to start since everything is all messed up.
Thank you so much for your help. You're the best!
You should do a Full Odin restore to Stock and start from scratch if you continue to have issues.
http://forum.xda-developers.com/showthread.php?t=2270065
You can also try this thread to ensure a full wipe before flash
http://forum.xda-developers.com/showthread.php?t=2277261
gharlane00 said:
You should do a Full Odin restore to Stock and start from scratch if you continue to have issues.
http://forum.xda-developers.com/showthread.php?t=2270065
You can also try this thread to ensure a full wipe before flash
http://forum.xda-developers.com/showthread.php?t=2277261
Click to expand...
Click to collapse
Installed Mobile ODIN Pro from the play store for $5... I hope that's the right Odin!
Stu_Gots said:
Installed Mobile ODIN Pro from the play store for $5... I hope that's the right Odin!
Click to expand...
Click to collapse
download Odin 1.85 or 3.07 on your PC don't use mobile version for something like this
Sent from my SPH-L720 using xda premium
Do I need to flash the stock kernal too? Will this eliminate my TWRP recovery installation as well?
If you odin back to stock it also has the kernel and stock recovery this will start you all over. Also of it doesnt boot past galaxy s4 screen then boot into recovery and wipe data after you odin back.
Sent from my SPH-L720 using xda premium
devoureddreams said:
If you odin back to stock it also has the kernel and stock recovery this will start you all over. Also of it doesnt boot past galaxy s4 screen then boot into recovery and wipe data after you odin back.
Sent from my SPH-L720 using xda premium
Click to expand...
Click to collapse
Alright... so another problem. I need the latest Samsung USB driver right? Unfortunately...
1.5.25.0 as linked to in this thread cannot be downloaded because uploaded.com or whatever says I've exceeded my allowance. Trouble is... I haven't downloaded anything from them ever. I have this problem all the time because of my ISP (Satellite Internet).
Is there a rehost? Do these drivers not install themselves automatically when the device is plugged into the PC?
http://downloadcenter.samsung.com/c...ng_USB_Driver_for_Mobile_Phones_v1.5.14.0.exe
Sent from my SPH-L720 using xda premium
I'm so freaking frustrated by this whole process. It looks like by all accounts there are a dozen different ways to do everything and I just know i'm going to mess it up.
I'm following the directions in this video.
http://www.youtube.com/watch?v=ZD5CHlrPQJQ&feature=youtu.be
When I extract the file I downloaded I get an MD5 file not an ODIN file.
Stu_Gots said:
I'm so freaking frustrated by this whole process. It looks like by all accounts there are a dozen different ways to do everything and I just know i'm going to mess it up.
I'm following the directions in this video.
http://www.youtube.com/watch?v=ZD5CHlrPQJQ&feature=youtu.be
When I extract the file I downloaded I get an MD5 file not an ODIN file.
Click to expand...
Click to collapse
Follow this tutorial here
http://www.sxtpdevelopers.com/showthread.php?p=2599
Sent from my SPH-L720 using xda premium
Alright guys. I got it done a while back. Phone is back to normal stock.
Perusing the internet I found this video.
http://www.youtube.com/watch?v=s_hXUJ-u-cw
As it happens I linked to the wrong video in my OP. The method in that video is exactly what I did to root in the first place. The proper way. I installed TWRP from GooManager.
So if I rooted correctly and I installed TWRP correctly what do you suppose caused my problem? I want to root and install custom recovery again!
If I root using the CF-Auto-Root method will I then be able to install custom recovery in goomanager or does custom recovery need to be installed in some other special way?
Stu_Gots said:
If I root using the CF-Auto-Root method will I then be able to install custom recovery in goomanager or does custom recovery need to be installed in some other special way?
Click to expand...
Click to collapse
thats all there is to it.
I just flashed a 802d stock ROM through TWRP 2.7 (AutoRec). I started out by wiping dalvik cache, cache and data. I then pressed Install and found the zip and installed that. After it was done, I did a dalvik + cache wipe again just to be safe (It asked if I wanted and I complied). Rebooted into system. It was quite buggy to begin with, so I wanted to try re-flashing, but it looks like my custom recovery has disappeared. I assume my root access went with it.
Everytime I try to get into recovery. It doesn't show the TWRP recovery, but merely ask if I want to factory reset my phone.
Currently, I'm downloading a clean kdz of the 802d ROM (it's taking a while) and aim to start all over with rooting and installing custom recovery and re-installing apps, but if anyone has a different solution, it would be most welcome. I'm quite the noob here. I thought TWRP would be fool-proof and would therefore allow me to restore a backup at any time. But currently, that does not appear to be the case.
Please do prove me wrong
Depends on what custom rom you were installing.
Trixanity said:
I just flashed a 802d stock ROM through TWRP 2.7 (AutoRec). I started out by wiping dalvik cache, cache and data. I then pressed Install and found the zip and installed that. After it was done, I did a dalvik + cache wipe again just to be safe (It asked if I wanted and I complied). Rebooted into system. It was quite buggy to begin with, so I wanted to try re-flashing, but it looks like my custom recovery has disappeared. I assume my root access went with it.
Everytime I try to get into recovery. It doesn't show the TWRP recovery, but merely ask if I want to factory reset my phone.
Currently, I'm downloading a clean kdz of the 802d ROM (it's taking a while) and aim to start all over with rooting and installing custom recovery and re-installing apps, but if anyone has a different solution, it would be most welcome. I'm quite the noob here. I thought TWRP would be fool-proof and would therefore allow me to restore a backup at any time. But currently, that does not appear to be the case.
Please do prove me wrong
Click to expand...
Click to collapse
Ok first if you really do have custom recovery in the factory reset screen clicking the power button three times will boot you into recovery, if you can boot into the Rom then download a root checker app to check if you still have root
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
XxZombiePikachu said:
Ok first if you really do have custom recovery in the factory reset screen clicking the power button three times will boot you into recovery, if you can boot into the Rom then download a root checker app to check if you still have root
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2736854 <- this is the ROM I flashed. It's a stock ROM containing the latest d firmware for the D802.
I just checked for root access - it's not there anymore. I will try to boot into recovery now through the method you suggested. I'll edit my post with the results.
Edit: Your method worked My recovery is there. Great! I thought it would boot straight into recovery, so the factory reset option mislead me. Now, I have to ask: did I do anything wrong in my flashing? For example. In the Mount section, only Data and Cache is mounted. Should system be mounted or is it irrelavant? Is there anything in particular I need to do in Wipe? I merely pressed Advanced Wipe and seleceted Dalvik Cache, Data and Cache and swiped to wipe. That's it.
Trixanity said:
http://forum.xda-developers.com/showthread.php?t=2736854 <- this is the ROM I flashed. It's a stock ROM containing the latest d firmware for the D802.
I just checked for root access - it's not there anymore. I will try to boot into recovery now through the method you suggested. I'll edit my post with the results.
Click to expand...
Click to collapse
well if you would have noticed in the install process it states to flash supersu after flashing the rom
XxZombiePikachu said:
well if you would have noticed in the install process it states to flash supersu after flashing the rom
Click to expand...
Click to collapse
Yeah, I did read that. This might sound stupid, but I figured that the listed SuperSU update was meant for people with an older version of SuperSU as in making sure to have the latest version of SuperSU, since I already had the latest version, I neglected to do that step. My bad. I will copy the zip in question to my phone and try re-flash both zips and see what happens. At least I have my backups to fall back on.
Another dumb question if you will. Since I didn't wipe any of my data. My apps are still present in the file system, but they are not installed nor do they have market links. Is there a way to install them or should I try to recover them through Titanium Backup? Or is it easier to simply wipe the data as well and use Titanium Backup to restore my apps?
Trixanity said:
Another dumb question if you will. Since I didn't wipe any of my data. My apps are still present in the file system, but they are not installed nor do they have market links. Is there a way to install them or should I try to recover them through Titanium Backup? Or is it easier to simply wipe the data as well and use Titanium Backup to restore my apps?
Click to expand...
Click to collapse
I think you should wipe and restore from tibu since there isn't a guarantee that redownloading your apps from the playstore will keep there old data
Thank you so much for taking your time to answer my questions. The second flash seemed succesful, but it didn't fix my biggest reason for flashing the ROM in the first place: the hissing audio bug. So I'll just try to do a restore of my latest backup and I'll make do with my temporary fix that actually works.
While it may seem to that I have wasted everyone's time, I think I've learned some valuable lessons, so I don't think it was entirely a bad thing
Hopefully, my restore will be succesful
Trixanity said:
Thank you so much for taking your time to answer my questions. The second flash seemed succesful, but it didn't fix my biggest reason for flashing the ROM in the first place: the hissing audio bug. So I'll just try to do a restore of my latest backup and I'll make do with my temporary fix that actually works.
While it may seem to that I have wasted everyone's time, I think I've learned some valuable lessons, so I don't think it was entirely a bad thing
Hopefully, my restore will be succesful
Click to expand...
Click to collapse
just in case since you don't mention the fix, I know the kk audio bug has a fix with g2tweaksbox over in the faq of first post it explains what needs to be done
XxZombiePikachu said:
just in case since you don't mention the fix, I know the kk audio bug has a fix with g2tweaksbox over in the faq of first post it explains what needs to be done
Click to expand...
Click to collapse
I did try that fix. It didn't remove the hiss entirely for me. Maybe removed 50% of the hiss, but I've heard of it working 100% for a lot of people. I've been using the ELT > Audio Loopback test from the hidden menu. It removes the hiss by about 99%. Only annoying thing is that I need to do it on every reboot which is why I wanted a more permanent fix.
Seems like my restore has caused a bootloop. Everything went accordingly, except the installation of SuperSU afterwards. Kept saying it failed to copy to the system folder despite system being mounted. The bootloop started when trying to boot into system after restore + failed SuperSU installation.
Edit: Fixed the SuperSU failure to install by wiping dalvik etc. but bootloop persists. I somewhat assume this is because the restore function doesn't work when the current ROM is different from the ROM the backup was made with? The backup was made with D802 20b firmware and the current ROM which is the one I flashed was the D802 20d firmware. Am I on to something?
Trixanity said:
I did try that fix. It didn't remove the hiss entirely for me. Maybe removed 50% of the hiss, but I've heard of it working 100% for a lot of people. I've been using the ELT > Audio Loopback test from the hidden menu. It removes the hiss by about 99%. Only annoying thing is that I need to do it on every reboot which is why I wanted a more permanent fix.
Seems like my restore has caused a bootloop. Everything went accordingly, except the installation of SuperSU afterwards. Kept saying it failed to copy to the system folder despite system being mounted. The bootloop started when trying to boot into system after restore + failed SuperSU installation.
Edit: Fixed the SuperSU failure to install by wiping dalvik etc. but bootloop persists. I somewhat assume this is because the restore function doesn't work when the current ROM is different from the ROM the backup was made with? The backup was made with D802 20b firmware and the current ROM which is the one I flashed was the D802 20d firmware. Am I on to something?
Click to expand...
Click to collapse
A backup restore should always work whether different versions or not, are you able to get into download mode?have you tried kdz to stock?
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
XxZombiePikachu said:
A backup restore should always work whether different versions or not, are you able to get into download mode?have you tried kdz to stock?
Sent from my LG-D800 running stock kk, rooted with philz using XDA app
Click to expand...
Click to collapse
I just fixed it by going into recovery and flashing the D802 20d firmware again. It'll do for now. Honestly don't know why the restore from backup didn't work. Either the backup was corrupt or I've done something wrong.
I did restore my apps (so far) flawlessly and the rom does appear to perform similarly to my older firmware. Plus there's added features such as knock code so it's not all bad.
I do have a D802 20d kdz firmware available on my computer in case I want to go completely stock and/or start over. But I'll give this one a try over the next few days and see whether I'll keep this.
Trixanity said:
I just fixed it by going into recovery and flashing the D802 20d firmware again. It'll do for now. Honestly don't know why the restore from backup didn't work. Either the backup was corrupt or I've done something wrong.
I did restore my apps (so far) flawlessly and the rom does appear to perform similarly to my older firmware. Plus there's added features such as knock code so it's not all bad.
I do have a D802 20d kdz firmware available on my computer in case I want to go completely stock and/or start over. But I'll give this one a try over the next few days and see whether I'll keep this.
Click to expand...
Click to collapse
yea I'm still waiting for that knock code update on my g2, times like these make you hate being with carriers