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?

Superwiped without rom

Hi!
I think I may have bricked my phone. I superwiped but I forgot to put a ROM
so now I have nothing on my phone.
Can I flash a ROM from my computer to my phone?
Thx in advance!

Flash a stock image using the Google images, then you can re-flash a custom one

If you still have cwr, mount USB in cwr, put a rom on there, flash from. If you don't have a recovery, you should be able to adb push the recovery file and flash through boot loader, then mount USB in recovery, copy rom to phone, flash.
Sent from my Galaxy Nexus using XDA App

Fastboot and download mode are your friends ;-)
Sent from my Galaxy Nexus using xda premium

EddyOS said:
Flash a stock image using the Google images, then you can re-flash a custom one
Click to expand...
Click to collapse
Where do I find them? I am sorry im a n00b :S

Cutting-TM said:
Fastboot and download mode are your friends ;-)
Sent from my Galaxy Nexus using xda premium
Click to expand...
Click to collapse
+1 What he said! /\
look at thread that has the odin stock rom

If you're a n00b then why on earth did you unlock the phone in the first place? Surely you should've researched what you were doing in case something like this happened?

Kotd424 said:
Hi!
I think I may have bricked my phone. I superwiped but I forgot to put a ROM
so now I have nothing on my phone.
Can I flash a ROM from my computer to my phone?
Thx in advance!
Click to expand...
Click to collapse
all is very easy to fix
1. Change ROM name to rom.zip
adb shell
mount /data
exit
adb push rom.zip /data/media
Now reboot into recovery and flash ROM.

Its all in here
http://groups.google.com/group/android-building/msg/43c3a418144fc6c5
This has helped me out twice already, and its where the factory images will be when the OTAs start, so of you're impatient and want them as soon as you can get them here
Sent from my Galaxy Nexus using Tapatalk

I think we need to put up a sticky again explaining what "brick" means.

mike1986. said:
all is very easy to fix
1. Change ROM name to rom.zip
adb shell
mount /data
exit
adb push rom.zip /data/media
Now reboot into recovery and flash ROM.
Click to expand...
Click to collapse
Hi, when I write adb shell, it says device not found.
i have install usb drivers but it dosent work
spences10 said:
Its all in here
http://groups.google.com/group/android-building/msg/43c3a418144fc6c5
This has helped me out twice already, and its where the factory images will be when the OTAs start, so of you're impatient and want them as soon as you can get them here
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
thx!

nbdysreal said:
If you still have cwr, mount USB in cwr, put a rom on there, flash from. If you don't have a recovery, you should be able to adb push the recovery file and flash through boot loader, then mount USB in recovery, copy rom to phone, flash.
Sent from my Galaxy Nexus using XDA App
Click to expand...
Click to collapse
Mount usb isn't working yet on Galaxy Nexus CWM 5.5.0.2 recovery you need to have a working rom to put your files in the phone

ok, nobody knows why I get error: device not found when i type adb shell?
I cant make it work... :S would really appreciate it

Kotd424 said:
ok, nobody knows why I get error: device not found when i type adb shell?
I cant make it work... :S would really appreciate it
Click to expand...
Click to collapse
Did adb work before? Sounds like the drivers aren't installed properly
And if you are trying to use the images from what I linked earlier you need to be in fastboot not adb
Sent from my Galaxy Nexus using Tapatalk

spences10 said:
Did adb work before? Sounds like the drivers aren't installed properly
And if you are trying to use the images from what I linked earlier you need to be in fastboot not adb
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
ok i also have the fastboot but what do I write?
fastboot boot <image name> ? that didnt work for me

Got it working now.
Thx everybody for the help. I didnt know that you should use adb in recovery mode.

[ROM] Stock yakjuux ITL41F

I thought i would post this, since I haven't seen it anywhere, and in case it helps someone out.
This is a nandroid backup of a stock yakjuux ITL41F build: http://www.filefactory.com/file/c3a77cd/n/2011-12-21.18.22.20.zip
What I did was factory reset my device and take a backup using CWM. (It should still be rooted, and with busy box installed.)
It is a nandroid backup of the system, data, cache and boot images, as well as the CWM recovery. To restore this, extract the directory from the zip and place it in the /sdcard/clockworkmod/backup directory on your device, reboot into CWM and restore.
I have not included the bootloader, stock recovery or radio - the radio can be found in my signature. The stock recovery is the same as the yakju build posted on Google's factory image site. As for the bootloader, I have no idea how to dump it.
Sent from my Galaxy Nexus using Tapatalk
EDIT: Link updated.
EDIT: This nandroid backup works. I've tested it myself. If you are having problems, then see here and here.

thanx dood! i was looking for this to make my emergency stocking kit!

erosgulo said:
thanx dood! i was looking for this to make my emergency stocking kit!
Click to expand...
Click to collapse
Don't forget that you will need to remove su, Superuser.apk and busybox in order to make it completely stock.
Sent from my Galaxy Nexus using Tapatalk

I don't have CWM flashed but could I soft-boot it and restore to this backup?

scratch42069 said:
I don't have CWM flashed but could I soft-boot it and restore to this backup?
Click to expand...
Click to collapse
Yup
Sent from my Galaxy Nexus using Tapatalk

efrant said:
Yup
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
Ok thanks. Good to know for when I start flashing.

Hello,
Was following your posts and am also on a nexus on Rogers.
my question is if I'm currently connected to an exchange server using active synch and am doing so in a corporate worl using mobile iron...can I update to the Stock yakju ICL53F build?
and If I do so using your backup and restore guide will I lose my connection to iron mobile when I restore?

adamat said:
Hello,
Was following your posts and am also on a nexus on Rogers.
my question is if I'm currently connected to an exchange server using active synch and am doing so in a corporate worl using mobile iron...can I update to the Stock yakju ICL53F build?
and If I do so using your backup and restore guide will I lose my connection to iron mobile when I restore?
Click to expand...
Click to collapse
I'm not sure what iron mobile is, but you certainly can flash yakju ICL53F and use ActiveSync on an Exchange server (I am) -- you just need to set up your account on your device after you flash.

Is it possible to dump system partition as img file instead using nandroid? Nandroid does not restore file modification times

leobg said:
Is it possible to dump system partition as img file instead using nandroid? Nandroid does not restore file modification times
Click to expand...
Click to collapse
Not sure if it is possible.

can you update the link as it is not working atm

RogersGnex said:
can you update the link as it is not working atm
Click to expand...
Click to collapse
I'll do it over the next couple of days.

RogersGnex said:
can you update the link as it is not working atm
Click to expand...
Click to collapse
Anyone know of a good free uploading service?

efrant said:
Anyone know of a good free uploading service?
Click to expand...
Click to collapse
uploaded dot to is good and so is filefactory dot com

anterus said:
uploaded dot to is good and so is filefactory dot com
Click to expand...
Click to collapse
Ok, I'll re-upload it tomorrow morning.

I re-uploaded the file. Link in first post updated.

Tried restoring this. I get an MD5 mismatch and it refuses to proceed.

cmstlist said:
Tried restoring this. I get an MD5 mismatch and it refuses to proceed.
Click to expand...
Click to collapse
After you unzip the file into the right directory, try doing this before booting into CWM:
# cd /sdcard/clockworkmod/backup/2011-12-21.18.22.20
# rm nandroid.md5
# md5sum *.* > nandroid.md5

efrant said:
After you unzip the file into the right directory, try doing this before booting into CWM:
# cd /sdcard/clockworkmod/backup/2011-12-21.18.22.20
# rm nandroid.md5
# md5sum *.* > nandroid.md5
Click to expand...
Click to collapse
Umm... Doesn't that just constitute overriding the security check? If the backup is uncorrupted, the md5 calculated on my phone should equal the one calculated on yours. That's a really dangerous suggestion.
Sent from my Galaxy Nexus using Tapatalk

cmstlist said:
Umm... Doesn't that just constitute overriding the security check? If the backup is uncorrupted, the md5 calculated on my phone should equal the one calculated on yours. That's a really dangerous suggestion.
Sent from my Galaxy Nexus using Tapatalk
Click to expand...
Click to collapse
CWM has been know to mess up in the past when you transfer backups to different devices. (It worked fine for me on my device, but it is my back-up image.)
And besides, you were just flashing it to apply the update in order to get the radio, anyway, so how is it dangerous.
P.S. I already posted the radio in the radio thread.

Help backing up stock JB kernel

I am really liking the stock JB kernel but I also have been using and liked Franco's kernel for the past few months, especially the customizability. I want to try it out too but I don't want to lose the stock kernel in the process. Can someone provide any of the following:
1. A guide to extracting/backing up the stock kernel.
2. A link to any such guide. (I looked around but couldn't find one.)
3. A link to the actual kernel. (If someone, somewhere has already done this and posted it.)
Thanks in advance!

mtmjr90 said:
I am really liking the stock JB kernel but I also have been using and liked Franco's kernel for the past few months, especially the customizability. I want to try it out too but I don't want to lose the stock kernel in the process. Can someone provide any of the following:
1. A guide to extracting/backing up the stock kernel.
2. A link to any such guide. (I looked around but couldn't find one.)
3. A link to the actual kernel. (If someone, somewhere has already done this and posted it.)
Thanks in advance!
Click to expand...
Click to collapse
Here's the stock kernel for you

Thanks! Out of curiosity, do you mind explaining how you got it? Is it super complicated? I'm just trying to learn by doing as much as I can to avoid having to ask all the time=/
Edit: Oh, also is that zip flashable via CWM?
Sent from my Galaxy Nexus using Tapatalk 2

I got it from one of the Jellybean threads, but with the sheer volume of JB threads today, I can't remember which. I think it's the main JB thread in General.
The only thing I did was rename it from StockKernel.zip and added the JB prefix so as not to lose it in my mess of files

Ah, sounds good. Thanks again!
Sent from my Galaxy Nexus using Tapatalk 2

mtmjr90 said:
Thanks! Out of curiosity, do you mind explaining how you got it? Is it super complicated? I'm just trying to learn by doing as much as I can to avoid having to ask all the time=/
Click to expand...
Click to collapse
This is the right attitude to have! :good:
The easiest way to back up your stock kernel is through CWM. It makes a backup of the image and saves it to your /sdcard/clockworkmod/... This file should be easily flashable using fastboot.
Another way, but less elegant, is to use dd (root and busybox required of course):
dd if=dev/block/platform/omap/omap_hsmmc.0/by-name/boot of=/sdcard/boot.img
That will place a file called boot.img in the root of /sdcard. (Not this file will likely not be flashable via fastboot, but can easily be flashed with dd:
dd if=/sdcard/boot.img of=dev/block/platform/omap/omap_hsmmc.0/by-name/boot

efrant said:
This is the right attitude to have! :good:
The easiest way to back up your stock kernel is through CWM. It makes a backup of the image and saves it to your /sdcard/clockworkmod/... This file should be easily flashable using fastboot.
Another way, but less elegant, is to use dd (root and busybox required of course):
dd if=dev/block/platform/omap/omap_hsmmc.0/by-name/boot of=/sdcard/boot.img
That will place a file called boot.img in the root of /sdcard. (Not this file will likely not be flashable via fastboot, but can easily be flashed with dd:
dd if=/sdcard/boot.img of=dev/block/platform/omap/omap_hsmmc.0/by-name/boot
Click to expand...
Click to collapse
Is that via a terminal emulator on the device then?

efrant said:
This is the right attitude to have! :good:
The easiest way to back up your stock kernel is through CWM. It makes a backup of the image and saves it to your /sdcard/clockworkmod/... This file should be easily flashable using fastboot.
Click to expand...
Click to collapse
Can you go into more details on this? I don't see an option to backup just the kernel. Do you have to pull it out of a complete backup?

mtmjr90 said:
Is that via a terminal emulator on the device then?
Click to expand...
Click to collapse
Either or.
---------- Post added at 11:59 AM ---------- Previous post was at 11:53 AM ----------
drewcam888 said:
Can you go into more details on this? I don't see an option to backup just the kernel. Do you have to pull it out of a complete backup?
Click to expand...
Click to collapse
You are right, you can NOT back up just the kernel using CWM, but you CAN restore just the kernel. (I was thinking of a different recovery.)

efrant said:
You are right, you can NOT back up just the kernel using CWM, but you CAN restore just the kernel. (I was thinking of a different recovery.)
Click to expand...
Click to collapse
I don't see any option to restore only the kernel. Where is this option?

drewcam888 said:
I don't see any option to restore only the kernel. Where is this option?
Click to expand...
Click to collapse
Under "backup and restore" under "advanced restore", select boot image.
Sent from my Galaxy Nexus using Tapatalk 2

Only a little bug for me:
From settings-->storage (memoria in italian) It can't see all the files in the sdcard, also doesn't see a lot of music (but I can see those music files with play music app)...
Any other thing is working fine, good battery life, much faster on homescreen and on the appdrawer, maybe a little laggier on temple run...
Waiting for the official release...

So I guess that if I download factory image for my NS and extract boot.img out of it (it is in tgz-tar-zip ), I should be able to flash it and restore stock kernel using fastboot flash boot boot.img. Am I right?
But I noticed that boot.img in zip provided by harveydent takes 2x more space than the one in the factory image.

jenda.69 said:
So I guess that if I download factory image for my NS and extract boot.img out of it (it is in tgz-tar-zip ), I should be able to flash it and restore stock kernel using fastboot flash boot boot.img. Am I right?
Click to expand...
Click to collapse
Yes, you are right.
jenda.69 said:
But I noticed that boot.img in zip provided by harveydent takes 2x more space than the one in the factory image.
Click to expand...
Click to collapse
If harveydent used dd to dump the image, it will be padded with a bunch of zeros at the end. Both will work fine, although you cannot flash the untrimmed one using fastboot, you need to use recovery or dd.
Sent from my Galaxy Nexus using Tapatalk 2

[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