Develop Bugs

Clockwork recovery

Has anyone successfully installed clockwork recovery on the continuum? I was tempted to try the fascinate instructions
Sent from my SCH-I400 using XDA App

I have used Titanium Back up with success

Okay, I can officially say that the Fascinate Clockwork Recovery does not work... Fails on "updating from Verizon" or something similar.... Then reboots... Is that Clockwork or the standard recovery?
Okay, I did not backup my stock recovery (stupid stupid stupid stupid), so can anyone get me that file and tell me which directory I need to shove it in?
Sent from my SCH-I400 using XDA App

I cannot remember the process to backup the recovery. What do you need me to do?

ThePravus said:
I cannot remember the process to backup the recovery. What do you need me to do?
Click to expand...
Click to collapse
Use root explorer or something similar, find the recovery file and copy it... Attach it here and let me injure what directory it was in... Please... I appreciate any help...
Sent from my SCH-I400 using XDA App

Or let me know... Somehow Swype changed that to injure...
Sent from my SCH-I400 using XDA App

I believe its more than just a file, you have to flash it.

Weudel said:
Use root explorer or something similar, find the recovery file and copy it... Attach it here and let me injure what directory it was in... Please... I appreciate any help...
Sent from my SCH-I400 using XDA App
Click to expand...
Click to collapse
If you know why the directory is I can post the files. Man, we really need some devs...
Also, you can might not need to flash it, but you would probably need to use ABD then.
Sent from my SCH-I400 using XDA App

Was informed that we could use dump_image to pull it and then flash_image to reflash. Trying to get ADB working at the moment. Typing on the phone is terrible.

ThePravus said:
Was informed that we could use dump_image to pull it and then flash_image to reflash. Trying to get ADB working at the moment. Typing on the phone is terrible.
Click to expand...
Click to collapse
The typing isn't that bad if you use swype or SwiftKey. Is there anything I can do to help?
Sent from my space time Continuum using the XDA App.

OK this is the best I can do I think.
I dumped the recovery block with the awesome help from Da_G]NARF[ on the XDA IRC chan.
AFAIK this should fix it.
Extract boot.rar
Copy boot.bin to your sdcard
Unmount the SDcard if you copied from your computer.
Open a terminal either with ADB shell or im assuming a term emulator would work.
SU for root privs. then use this command:
Code:
dd if /dev/block/bml1 of=/sdcard/boot.bak bs=4096
This will backup your current one.
Code:
dd if=/sdcard/boot.bin of=/dev/block/bml1 bs=4096
This will rewrite with the new one.
Reboot.

dfgged said:
The typing isn't that bad if you use swype or SwiftKey. Is there anything I can do to help?
Sent from my space time Continuum using the XDA App.
Click to expand...
Click to collapse
If you can pull the stock recovery and post it, that would be great...
Otherwise, could one of you try booting into the stock recovery and see what it does... I tried to load the Fascinate Clockwork using ROM Manager and I'm not sure if it actually did anything or not... I don't think Clockwork would check with Verizon for updates.... All I have experience with is Amon Ra on my Eris..... Would be great if it just failed to change it.....

ThePravus said:
OK this is the best I can do I think.
I dumped the recovery block with the awesome help from Da_G]NARF[ on the XDA IRC chan.
AFAIK this should fix it.
Extract boot.rar
Copy boot.bin to your sdcard
Unmount the SDcard if you copied from your computer.
Open a terminal either with ADB shell or im assuming a term emulator would work.
SU for root privs. then use this command:
Code:
dd if /dev/block/bml1 of=/sdcard/boot.bak bs=4096
This will backup your current one.
Code:
dd if=/sdcard/boot.bin of=/dev/block/bml1 bs=4096
This will rewrite with the new one.
Reboot.
Click to expand...
Click to collapse
Awesome, thanks...
Looks like it worked... I guess I might not know for sure until the 2.2 OTA comes out.... Fingers crossed...

I've been working on porting clockwork. After running
Code:
build/tools/device/mkvendor.sh device_manufacturer_name device_name /your/path/to/the/boot.img
with the path substitution, I get
Code:
unpackbootimg not found. Is your android build environment set up and have the host tools been built?
Does anyone have any suggestions?

I am new to these forums Well, i have been looking around here for a while for my Continuum phone, i just haven't said anything
I may be completely wrong... But do these steps (The ones in the beginning) install Clockwork? Or is that for something completely different?
and this is probably the wrong place to ask... But in order to install the Voodoo lagfix, you need Clockwork, right?
Thank you for your help everyone

trailblazer101 said:
I am new to these forums Well, i have been looking around here for a while for my Continuum phone, i just haven't said anything
I may be completely wrong... But do these steps (The ones in the beginning) install Clockwork? Or is that for something completely different?
and this is probably the wrong place to ask... But in order to install the Voodoo lagfix, you need Clockwork, right?
Thank you for your help everyone
Click to expand...
Click to collapse
Well this the right place to ask, and the steps you see are steps to flash the stock recovery back. Also, yes, we do need clockwork for voodoo.
Sent from my space time Continuum using the XDA App.

dfgged said:
Well this the right place to ask, and the steps you see are steps to flash the stock recovery back. Also, yes, we do need clockwork for voodoo.
Sent from my space time Continuum using the XDA App.
Click to expand...
Click to collapse
There currently is not a Clockwork Recovery for the Continuum, but it is in the works...

Has anyone other than Weudel tried using this supposed stock recovery?
Sent from my SCH-I400 using XDA App

I'm using a Terminal Emulator on my phone trying to run the command to backup my current boot image. I'm typing "su" first for root privileges then typing "dd if /dev/block/bml1 of=/sdcard/boot.bak bs=4096" but I'm getting an error saying uknown operand if. Help?
Nevermind, I've discovered the problem. The code to backup your current boot image is "dd if=/dev/block/bml1 of=/sdcard/boot.bak bs=4096". There was an equal sign missing in the post above.

So I've completed the steps listed above and was under the impression this would restore my phone to stock. However, I still don't have the Verizon bloatware I deleted. Did I not understand what this process was meant to accomplish?

need to go back to stock

I have the newest cyanogen 6.1 on my g2 and I dont have the stock zip anymore, How do I go back to stock, I need a stock froyo download, I dont care if I lose root...

Go to the development section and look at the sticky. You'll find one that has the how to revert back to stock using a hex editor. In the 6th page of the how to thread I posted a link to a hex editor. It's cake.
Sent from my HTC Vision using XDA App

ddgarcia05 said:
It's cake.
Click to expand...
Click to collapse
Mmhhh.... Tasty

Did it.... But now superuser is still there lol ... I want to go back to CM 6 but what should I do so if I ever want to go back to stock it will be there, also what should I do to get all my apps over on CM 6.1

and now my wifi doesnt work, It just says error when I click the check box on in settings

Stock image did you use? I used the one linked in the how to and had no problem.
Sent from my HTC Vision using XDA App

I used that one as well, also did superuser still show up when you were back to stock?

Your probably didn't flash all the way. After restoring from an official image you should be completely stock.

how do I flash all the way? I did what the steps said, and this is what im running now:
Android 2.2
Baseband:
12.22.60.09bU_26.02.01.15_M2
Kernel Version:
[email protected]#1
build number:
1.19.531.1 CL255798 release-keys
I see that it still says cyanogen mod on the kernel version...
But when I boot up it boots regular and does not have the CM 6.1 screen and has the G2 screen instead, and looks like stock froyo....
I try using the method stated above and get the error, then Im stuck on this part I guess:
"**IMPORTANT**
If the flash has failed you must reboot back into the OS and use HexEditor which i have attached to the thread. DO NOT PROCEED UNTIL YOU HAVE DONE THIS!!
Open up an ADB Shell and run the following command:
dd if=/dev/block/mmcblk0p17 of=/sdcard/misc.img
this will then export the misc.img file we need to edit to the root of the sdcard.
Mount your sdcard and save the misc.img file to your PC and Open the file with HexEditor.
You should now see the version number on the right hand side of the application and it should read "1.22.531.8" YOU MUST CHANGE THIS TO "1.19.531.1" you can now save the file as miscnew.img and place it on the root of your sdcard and then unmount the sdcard from windows.
Now go back to your ADB Shell and run the following command
dd if=/sdcard/miscnew.img of=/dev/block/mmcblk0p17
you can now make sure you have copied the PC10IMG.zip file to the root of your SDCARD and power off your phone and proceed to step 2."

I am using terminal emulator and it says "cannot open for readermission denied, " when I enter this in the emulator "dd if=/dev/block/mmcblk0p17 of=/sdcard/misc.img"
NVM forgot to su lol silly me
will keep updated on my progress

Okay, I am back to stock, thanks to you all who pointed me in the right direction... Now If I go back to CM 6.1, what should I do to back up my phone in its stock state?

icolorado303 said:
Okay, I am back to stock, thanks to you all who pointed me in the right direction... Now If I go back to CM 6.1, what should I do to back up my phone in its stock state?
Click to expand...
Click to collapse
You can only back up the phone from it's stock rooted state. Correct?
Anyways, if you going to reroot the phone I highly suggest you use rage instead of visionary.

where do I get rage from? and Is it a similar process.... and IDK you tell me lol, I am new to the android scene, coming from an iphone 4 on tmobile.... I have read lots and lots before attempting to root, lots of stickies etc, all I ever heard about was visionary nothing about rage...

icolorado303 said:
where do I get rage from? and Is it a similar process.... and IDK you tell me lol, I am new to the android scene, coming from an iphone 4 on tmobile.... I have read lots and lots before attempting to root, lots of stickies etc, all I ever heard about was visionary nothing about rage...
Click to expand...
Click to collapse
http://forum.xda-developers.com/wik...sion#Rooting_the_Vision_.28G2.2FDZ.29_and_DHD
Start here. The instructions and files are all there and work. I've just done 3 G2s using this method and had no problems at all.

Also, you'll need to get adb working on your PC to be able to use rage.
See this guide on adb - http://forum.xda-developers.com/showthread.php?t=865685

will the method discussed work for me? I'm on the current build of cyanogenmod and used the gfree method to free all (super cid, sim unlock, real s-off). I need to revert to stock to send phone back because I'm getting a replacement due to signal issues. Any help is appreciated thanx.

anyone? 10char

mcp2009 said:
will the method discussed work for me? I'm on the current build of cyanogenmod and used the gfree method to free all (super cid, sim unlock, real s-off). I need to revert to stock to send phone back because I'm getting a replacement due to signal issues. Any help is appreciated thanx.
Click to expand...
Click to collapse
You're on a G2, right ?
This should work for you - http://forum.xda-developers.com/showthread.php?t=831398

steviewevie said:
You're on a G2, right ?
This should work for you - http://forum.xda-developers.com/showthread.php?t=831398
Click to expand...
Click to collapse
yea using g2 thnx man I'll try when my replacement gets here. Is it a sure thing? Says for temp root and I'm perm rooted. Gosh I feel like a noob lol.

mcp2009 said:
yea using g2 thnx man I'll try when my replacement gets here. Is it a sure thing? Says for temp root and I'm perm rooted. Gosh I feel like a noob lol.
Click to expand...
Click to collapse
That guide will let you downgrade to the stock ROM, yes. There's a note at the bottom saying it's not a rooting method (not sure why that note is there really), is that what you mean ?

[Q] Problem with adb remount

OK I know this problem has been posted hundreds times before but i've read several of them but still can't find out what i did wrong. SO: I got my G2 rooted with S-OFF as i looked in the bootloader. I rooted the phone using rage method. So if i have my S-OFF that's obviously that i am rooted right?
And I definitely have my adb set up right cuz i could not root my phone if i didn't have adb set up. The question is Why every time I try to do adb remount, it will keep saying remount failed operation not permitted.
Even when I try doing adb shell and su it would say access denied too.
Just a little frustrating, What can i do to fix this?

wang1404 said:
OK I know this problem has been posted hundreds times before but i've read several of them but still can't find out what i did wrong. SO: I got my G2 rooted with S-OFF as i looked in the bootloader. I rooted the phone using rage method. So if i have my S-OFF that's obviously that i am rooted right?
And I definitely have my adb set up right cuz i could not root my phone if i didn't have adb set up. The question is Why every time I try to do adb remount, it will keep saying remount failed operation not permitted.
Even when I try doing adb shell and su it would say access denied too.
Just a little frustrating, What can i do to fix this?
Click to expand...
Click to collapse
I am not %100 if this is your problem but i think you need ENGINEERING HBOOT
to run adb commands ,you can do it by reading the wiki http://forum.xda-developers.com/wik...Z.2FG2.2FDHD.29_-_OPTIONAL_and_UNNECESSARY.21
But if you want to do it be very very carefull becasue if you do it wrong you will brick your phone and there is no way back

S-OFF is different from having your phone rooted, so it sounds like your rooting hasn't worked. If you have S-OFF and the eng hboot, you could use fastboot to flash Clockwork recovery and then install a custom pre-rooted ROM.
Or you will need to go through the rooting procedure again to see what has gone wrong.
Sent from my HTC Desire Z

If that's the case that my phone hasn't been rooted. My rom manager worked. I flashed clock work successfully and I did checked that I had it by rebooting into recovery. I even used n1 torch high brightness to make sure I was rooted. Then extra step was asking su in my terminal emulator too. But I still had hboot.img tho. Should I do an engineering hboot ?
Sent from my Nexus One using XDA App

steviewevie said:
Or you will need to go through the rooting procedure again to see what has gone wrong.
Click to expand...
Click to collapse
I did notice that while I was rooting. A command said no such file or directory. So I wonder if that was it? I thought it was supposed yo happen tho lol
Sent from my Nexus One using XDA App

wang1404 said:
If that's the case that my phone hasn't been rooted. My rom manager worked. I flashed clock work successfully and I did checked that I had it by rebooting into recovery. I even used n1 torch high brightness to make sure I was rooted. Then extra step was asking su in my terminal emulator too. But I still had hboot.img tho. Should I do an engineering hboot ?
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
If you can boot into CWM recovery just flash a custon rom they all have root built into them.

joemm said:
If you can boot into CWM recovery just flash a custon rom they all have root built into them.
Click to expand...
Click to collapse
It's my wifes phone so I don't wanna do something too complicated for her. I mean the easier for her to use the phone the better. But will that fix the problem? Adb remount problem? If yes than hell yeah I would flash cyan right away lol.
Sent from my Nexus One using XDA App

wang1404 said:
It's my wifes phone so I don't wanna do something too complicated for her. I mean the easier for her to use the phone the better. But will that fix the problem? Adb remount problem? If yes than hell yeah I would flash cyan right away lol.
Sent from my Nexus One using XDA App
Click to expand...
Click to collapse
Should fix any problems with mounting, heres a link for a stock rooted rom, so she wont be able to tell the diffrence, also since you can boot into CWM recovery make a backup of your current rom before flashing this:
http://forum.xda-developers.com/showthread.php?t=836042

joemm said:
Should fix any problems with mounting, heres a link for a stock rooted rom, so she wont be able to tell the diffrence, also since you can boot into CWM recovery make a backup of your current rom before flashing this:
http://forum.xda-developers.com/showthread.php?t=836042
Click to expand...
Click to collapse
The ADB remount command requires the ro.secure property to be set to 0 (even if you are rooted). If you want to remain on the stock ROM, flashing the linked ROM will do it for you (and is way easier than doing it yourself manually). Most (if not all) of the custom ROMs will set this property for you if you wanted to try others as well.

Thank you guys very much. I never faced this problem before since my n1 was rooted and flashed rom using the phone not adb our anything related to computer.so thanks guys. Case closed. Happy me lol
Sent from my Nexus One using XDA App

How to gain ROOT back after JellyBean OTA flash

Maybe it is interesting also for others, how to get back ROOT access after flashing JB OTA. I did it with YAKJU.
The steps:
1.) adb reboot bootloader
2.) download recovery-clockwork-5.5.0.2-maguro.img
2.) fastboot boot recovery-clockwork-5.5.0.2-maguro.img
3.) adb kill-server
4.) adb start-server
5.) adb devices
6.) mount the system in CWM
7.) adb shell ls -al /system/bin/su
8.) adb shell chmod 4755 /system/bin/su
9.) adb shell ls -al /system/bin/su
10.) reboot
Dont forget to use fastboot with su or sudo -i in Linux.
Steps 3, 4 and 5 are only to ensure that your ADB works correctly with your device.
Steps 7 and 9 is also only for paranoid users like me
That's it.

Voodoo OTA Rootkeeper?
In another thread, a poster reported that Voodoo OTA Rootkeeper was unable to restore root after flashing JellyBean. I wonder if others have had the same experience? Thanks!

gibosi said:
In another thread, a poster reported that Voodoo OTA Rootkeeper was unable to restore root after flashing JellyBean. I wonder if others have had the same experience? Thanks!
Click to expand...
Click to collapse
I was able to make it work...I hit restore su... then it took like a minute little pop up saying su restore successful ..opened superuser app...went back to ota root keeper...hit restore su again...that's when superuser prompted me to allow superuser access.
Sent from my Galaxy Nexus using xda premium

Based on your experience, I flashed Jellybean this afternoon and Voodoo OTA Rootkeeper restored root. Thanks!

i think i've become lazy these days, i just selected - "root phone" in the nexus tool kit 7.4 after flashing the update to get root back.
i dont even bother typing the fastboot commands to boot CWM recovery in CMD anymore, i just select the option in the toolkit.

gibosi said:
In another thread, a poster reported that Voodoo OTA Rootkeeper was unable to restore root after flashing JellyBean. I wonder if others have had the same experience? Thanks!
Click to expand...
Click to collapse
Placing this here in case it can help anyone else:
I downloaded the Jelly Bean .zip file, placed it in /cache, and used the stock recovery to update. After installation, I had lost root. su was gone from /system/xbin and OTA Rootkeeper was unable to restore root. Neither CWM Touch 5.8.0.2 nor CWM 5.5.0.2 were able to mount /sdcard in order to apply su.zip. However, /system/usr/we-need-root/su-backup was still there with the proper permissions so I was able to restore root manually by using it.

the OP's instructions worked for me. I flashed the OTA with CWM by the way (the stock failed on the package checking because I was rooted) ?
Anyway, I ran Titanium Backup to check the root worked per OP's instructions and it did but it complained that permissions weren't optimal so I let it change them to 6755 instead (which gives super to both the owner and the group).
Works like a charm now so far.... only 5 minutes with it though

I forgot to run root keeper before the 4.1.2 OTA. I presume this is still valid?
Can someone confirm that this wont wipe the device?
Ta

aidanbree said:
I forgot to run root keeper before the 4.1.2 OTA. I presume this is still valid?
Can someone confirm that this wont wipe the device?
Ta
Click to expand...
Click to collapse
Let me make this a little easier, do the first couple of steps then once you are in recovery flash this: http://androidsu.com/superuser/
You are rooted.

Why are you trying to make this so hard?
Boot in to CWM Recovery and flash the zip. Takes about 5 seconds.

Couldn't we just adb push a su apk to system/app and maybe a adb install su?
Sent from my Nexus 7 using Tapatalk 2

BrianDigital said:
Couldn't we just adb push a su apk to system/app and maybe a adb install su?
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
You could but I still think my way would be easier, just my opinion though.
Sent from my Galaxy Nexus using Tapatalk 2

miketoasty said:
You could but I still think my way would be easier, just my opinion though.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I see but if you took the 4.1.2ota you were on stock recovery and someone wanting to get ota'the same way would have to revert back to stock recovery once this was done.
Sent from my Nexus 7 using Tapatalk 2

BrianDigital said:
I see but if you took the 4.1.2ota you were on stock recovery and someone wanting to get ota'the same way would have to revert back to stock recovery once this was done.
Sent from my Nexus 7 using Tapatalk 2
Click to expand...
Click to collapse
Good point, I don't regularly use the stock recovery so I wasn't thinking about it.
Sent from my Galaxy Nexus using Tapatalk 2

miketoasty said:
Good point, I don't regularly use the stock recovery so I wasn't thinking about it.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
I am going to do this today, my girlfriend needs roots for silly things like changing the on screen button. I'll document it and leave it in here.
This way she can have her root and I dont have to be like "I needs to update your phone/tablet" when google pushes something new, and maybe other people might find it useful

[HOWTO]Recover From a Bad Flash - Now automated

Ok so you accidentally tried to Odin or CWM the wrong file to your phone. Well the good news is that if you can get into CWM with access to the sdcard(s) or access ADB we can fix it. If the phone won't power on at all, you can't access cwm with sdcard(s), ADB or Odin you are unfortunately out of luck. You will need to get it repaired by Sprint or send it off for a jtag repair.
Disclaimer: I am not responsible for anything that happens to your phone. You do this at your own risk.
If you don't own the E4GT do not use this guide because if your partitions are not the same as ours you will brick your phone.
If by chance you can get into Odin mode and your computer can see the phone go buy a lottery ticket J/K. All you have to do is download a full tar and Odin it back on. I won't go into details for that as it is well documented. Or you can still use this zip if you prefer.
I have automated the process of the restore. What this zip will do is flash the Agat 0.5.4 source kernel so you have cwm. It will flash the FH13 boot.bin, hidden.img, param.lfs and Sbl.bin. It will wipe Cache and Dalvik also.
This will not flash the modem, wipe data or replace system. So after you use this zip if your modem is also hosed flash a modem zip from CWM. Once you have recovered the phone you can flash whatever you want back on the phone.
Download CWM Odin Restore To FH13: http://d-h.st/3yZ
Copy the zip file to your phone and flash in custom recovery.
If you don't have access to the sdcard(s) but do have access to ADB proceed to the second post.
If you need some direct assistance you can PM me and I will work with you when possible.

You only have ADB access
For this method you will need CWM, ADB, Root and the image files to restore.
If you don't have ADB installed I have attached it to this post. I have also provided a link to the FH13 image files.
If you don't have ADB, extract the ADB directory to the root of C:. So you should see C:\ADB
You need to know where your ADB directory is located. If you used step 1 ADB it is C:\ADB. If you installed it on your own you should know where to find it.
Extract the images.zip into the ADB directory. You should now have the Images folder in the ADB folder.
Boot into CWM and attach your phone to the computer.
Open a command prompt and change directory to the ADB directory cd C:\ADB (or wherever your directory is).
Type adb push Images /tmp and hit enter.
You should see something like 6 files pushed. 0 files skipped.8465 KB/s (19271020 bytes in 2.223s).
Type adb shell and hit enter.
This part is critical. Make sure it is typed exactly or you can/will destroy your phone.
Copy and paste or type the following commands. If you copy and paste make sure you don't copy any leading or trailing spaces. Hit enter after each command.
You can skip any of the following commands if you know you don't need them. For example, if you know you only installed the Sbl.bin then you only need to enter that command. I have provided them all to cover all of the needs. If you are not sure just do them all.
dd if=/tmp/boot.bin of=/dev/block/mmcblk0p0
dd if=/tmp/hidden.img of=/dev/block/mmcblk0p12
dd if=/tmp/param.lfs of=/dev/block/mmcblk0p4
dd if=/tmp/Sbl.bin of=/dev/block/mmcblk0p2
dd if=/tmp/zImage of=/dev/block/mmcblk0p5
dd if=/tmp/zImage of=/dev/block/mmcblk0p6
You should see something like 2560+0 records in, 2560+0 records out, 1310720 bytes (1.3MB) copied, 0.265521 seconds, 4.7MB/s after each command.
Reboot your phone and it should boot up.
If it still doesn't boot something didn't take and we will need to work one on one.
Download the Images.zip: http://d-h.st/8gY

The bootloader restore has been proven to work on one phone so far. Thanks to pjkingphd for testing and confirming that it works.

great share!thanks for the tutorial.

crawrj said:
Please sticky this thread.
Click to expand...
Click to collapse
Hopefully this will be done.
Sent from my SPH-D710 using Xparent SkyBlue Tapatalk 2

Crawrj my man.
Tappin' Typin'

md5 sums might be nice. Don't want bricked phones due to bad downloads.
Sent from my Galaxy Nexus using xda app-developers app

times_infinity said:
md5 sums might be nice. Don't want bricked phones due to bad downloads.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
But then we wouldn't have anyone to test this... would we..
Great tutorial crawrj
Sent from my SPH-D710 using Xparent Blue Tapatalk 2

Very nice. Thank you.

times_infinity said:
md5 sums might be nice. Don't want bricked phones due to bad downloads.
Sent from my Galaxy Nexus using xda app-developers app
Click to expand...
Click to collapse
If the md5 is not right it will say so when you try to restore in cwm. It won't restore if they don't match. But I can throw up md5 for the sbl.
Sent from my SPH-D710 using xda premium

MD5 added. Sticky this please.

I have now automated the restore process in a zip file. You must be able to copy the zip file to the phone for it to work. I have flashed it about a dozen times but I would like to get a few brave testers to try it on your phone for me. Make sure you do a backup first! I have moved the manual commands to post two and revamped the instructions.

+1
Sticky or move to original development.
Sent from my piece of crap Zio until i get my E4GT back from Samsung, using XDA Premium app

Thread stuck. Thank you for helping out the community. :highfive:

jayharper08 said:
Thread stuck. Thank you for helping out the community. :highfive:
Click to expand...
Click to collapse
Thank you sir :highfive:

Sooo... uhm ,,, say I know a certain someone who botched their custom boot logo and has been lazy..... and has the draw failure start up...
This would restore that to stock without any other ramifications except for a kernel swap, correct??
Edit: Guess after a day Ill just assume yes and hope it cant brake anything....

PhAkEer said:
Sooo... uhm ,,, say I know a certain someone who botched their custom boot logo and has been lazy..... and has the draw failure start up...
This would restore that to stock without any other ramifications except for a kernel swap, correct??
Edit: Guess after a day Ill just assume yes and hope it cant brake anything....
Click to expand...
Click to collapse
Yeah this will fix you up. Once you get recovered you can flash whatever you want back on. Since you are an advanced user if you have a particular setup that you want to restore, just pull those files from the tar and place them in the Images folder of the zip.

You never can be too sure.. Lol I just always expect the one time I make an assumption will be regretted.
Good idea btw... And thanks.
And Ive actually been meaning to flash a param.lfs..... I have like 4 OCs it just they are all the way on my backup backup card ...(see my level of sloth ?!?!?!)

PhAkEer said:
You never can be too sure.. Lol I just always expect the one time I make an assumption will be regretted.
Good idea btw... And thanks.
And Ive actually been meaning to flash a param.lfs..... I have like 4 OCs it just they are all the way on my backup backup card ...(see my level of sloth ?!?!?!)
Click to expand...
Click to collapse
LOL nice. Let me know how it turns out.

crawrj said:
LOL nice. Let me know how it turns out.
Click to expand...
Click to collapse
Good as gold, as expected. I did end up only using the param.lfs but Im sure the rest will work great when I need it =)
Thanks again.... Itd been a long time since I last saw that sweet , sweeet gaudi_bootimage.jpg
Sent from my SPH-D710 using xda premium