Clockwork recovery - Continuum Android Development

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?

Related

New and Improved way to Unroot your device (much easier) [difficulty level 4]

So I am moving onto a new phone so I will not be supporting this thread anymore. Please help each other the best you can. Also if anyone wants to take over and support this thread feel free. Last but not least if anyone wants to use any of the items I put into this also feel free. Remember that android is made possible with contrbutions from viewers like you!
Check out my new guide its much easier and automated now!!
Sorry but I no longer have the files that were in the zip as my laptop that they were on no longer has a charger so I really don't have a way to pull them off until I come up with extra funds to buy a charger for that dinosaur!
I have updated the commands so everything will be working correctly.
Please note this a guide to unrooting your device and returning it to stock, if you have nothing stock and didn't back anything up i.e. modded rom, changed recovery, eng. bootloader.
If you didn't follow the ultimate guide then you will not need to follow steps 1-7. Just follow from 8 on.
Also keep in mind this was created assuming you followed the ultimate guide to permaroot turning radio s=off and changing cid thus unlocking phone.
I am not responsible for any damage to your phone blah blah blah.
Also if I am incorrect in any of these steps someone please let me know.
Also this is just a guide that I wrote using all the others. Please thank and donate to grankin01 for providing the original guide and also thank/donate to tiger013 for providing a stock nandroid. Also thank Football for providing new rom.
With that said here we go:
Download the PD15IMG file and rename it to PD15IMG.zip
1. Copy PD15IMG.zip and "part7backup-whatevernuberitscalled.bin" to the root of your sdcard
2. Connect your phone to your computer and navigate to your sdk folder then type adb push gfree /data/local
3. Open up terminal emulator or adb shell and type "su" press enter to get root privileges.
4. Type "cd /data/local" and hit enter
5. Type "chmod 777 gfree" and hit enter to make the program executable.
6. Now type "./gfree -f" press enter to run gfree again. It will disable wp on the emmc and remove the brq filter in the kernel. (as well as make another backup. delete this)
7. Now run the "dd if=/sdcard/part7backup-whatevernumberitscalled.bin of=/dev/block/mmcblk0p7" and it should show the output:
xxxx bytes in
xxxxbytes out
xxxxxxxxxx copied in xxxxxxxxxxx
8. Run "sync" and then reboot.
9. Let phone load then boot into bootloader again by holding volume down and pressing power
10. Let it load image and select yes to update.
11. Let it do its work it will reboot once this is normal.
And that should be it. Enjoy stock rom.
Great job! I un-rooted worked fine! Then I re-rooted worked fine also!
Sent from my HTC Glacier using XDA App
I assume this will not work if you have made a backup with clockwork? Also your instructions say apply nandroid backup, but there is no option in recovery for appy nandroid backup. There are options to update from update.zip and another one from a zip file. The folder inside you unroot package is not a zip file?
bobsbbq said:
I assume this will not work if you have made a backup with clockwork? Also your instructions say apply nandroid backup, but there is no option in recovery for appy nandroid backup. There are options to update from update.zip and another one from a zip file. The folder inside you unroot package is not a zip file?
Click to expand...
Click to collapse
Well like I said this was done using no backups made.
Under clockworks recovery theres an option for backups and restore - this is the nandroid restore.
Sent from my HTC Glacier using XDA App
where does the "part7backup-whatevernuberitscalled.bin" file in step 11 come from?
vw671 said:
where does the "part7backup-whatevernuberitscalled.bin" file in step 11 come from?
Click to expand...
Click to collapse
Its the file that was created when you followed the ultimate guide for permaroot
Sent from my HTC Glacier using XDA App
jjjackson56 said:
Its the file that was created when you followed the ultimate guide for permaroot
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
What if you don't have that file? Can you skip that step?
thanks.
vw671 said:
What if you don't have that file? Can you skip that step?
thanks.
Click to expand...
Click to collapse
I'm sure you can but you won't have true stock. I could also upload my copy but I'm not positive if it will work for your phone.
Sent from my HTC Glacier using XDA App
This is awesome! I'm getting a replacement mt4g in the mail soon, now I will be able to send my existing phone back 'unrooted'. Thank you!
Is this unroot like out of the box type deal. So that i can get future ota updates. I used ultimate guide to perm root. I am using stock rom. I am notsure if i should just do unroot.zip to unroot for future ota updates.
Sent from my HTC Glacier using XDA App
If performed correctly is should take you back to out of the box stock.
(in theory)
I'm guessing you can't do this strictly from terminal emulator?
Sent from my HTC Glacier using XDA App
hawaiian.monzta said:
I'm guessing you can't do this strictly from terminal emulator?
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
You may be able to but I don't know how nor do I care to figure it out. If someone wants to write instructions pm me them and I'll post them in the op
Sent from my HTC Glacier using XDA App
jjjackson56 said:
You may be able to but I don't know how nor do I care to figure it out. If someone wants to write instructions pm me them and I'll post them in the op
Sent from my HTC Glacier using XDA App
Click to expand...
Click to collapse
A guide for terminal emulator would be welcome.
I did S=off with it (plus radio) with root explorer and terminal emulator only. It was much easier and quicker.
gaww said:
A guide for terminal emulator would be welcome.
I did S=off with it (plus radio) with root explorer and terminal emulator only. It was much easier and quicker.
Click to expand...
Click to collapse
You could pm me the steps and I'll gladly post them in the op
Sent from my HTC Glacier using XDA App
quick question, does following this take you back to factory ROM? for exampe im on iced glacier 1.1.1, will it take me to factory ROM?
mrpanic7 said:
quick question, does following this take you back to factory ROM? for exampe im on iced glacier 1.1.1, will it take me to factory ROM?
Click to expand...
Click to collapse
Yes it will hence stock
Sent from my HTC Glacier using XDA App
so...?
I put the nandroid file on my sdcard, but in recovery when i go to restore there it says no files. What do I need to do to get this to work. I have a replacement coming to me so I need to figure this out.
Edit: Sorry I'm an idiot. I got it know. Thank you so much for posting this.
Edit2: Crap! Ok I have s=on now but i still have hboot 0.86.0000 Shouldn't I have the old one now?
Where is the "part7backup" located? Also, what is it?
this sucks... i followed everything perfectly but now my recovery is screwed up ugh this is so frustrating i have that stupid phone with a red triangle thing when i try to boot into recovery (yes im aware its supposed to be stock recovery not clockwork)

[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

Need Help Testing for Temp Root in DL17

Folks,
I need someone on DL17 to test for root access. Due to the small community, I haven't heard if anyone is rooted on DL17.
While I can build kernels and get clockwork working for DJ20, for DL17, I need the stock kernel dumped, and for that I need root.
Steps:
1. Go to Index of /files and download rage.bin. (right click, save as)
2. Copy or adb push rage.bin to /data/local/tmp on your phone.
3. In adb shell:
Code:
chmod 755 /data/local/tmp/rage.bin
Then
Code:
/data/local/rage.bin
It will give you a wall of text. Wait a few minutes, hit ctrl-c to close adb shell, then type
Code:
adb kill-server
Then do adb shell again. It should (hopefully) take you to a # prompt. Please report back.
Thanks.
adrynalyne said:
Folks,
I need someone on DL17 to test for root access. Due to the small community, I haven't heard if anyone is rooted on DL17.
While I can build kernels and get clockwork working for DJ20, for DL17, I need the stock kernel dumped, and for that I need root.
Steps:
1. Go to Index of /files and download rage.bin. (right click, save as)
2. Copy or adb push rage.bin to /data/local/tmp on your phone.
3. In adb shell:
Code:
chmod 755 /data/local/tmp/rage.bin
Then
Code:
/data/local/rage.bin
It will give you a wall of text. Wait a few minutes, hit ctrl-c to close adb shell, then type
Code:
adb kill-server
Then do adb shell again. It should (hopefully) take you to a # prompt. Please report back.
Thanks.
Click to expand...
Click to collapse
Bro I just used my one click...works fine. Full root and busybox.
Sent from my SCH-I400 using XDA App
Great. Can you post the DL17 zImage?
Thanks.
adrynalyne said:
Great. Can you post the DL17 zImage?
Thanks.
Click to expand...
Click to collapse
Give me a sec.
Sent from my SCH-I400 using XDA App
have you tried my clockwork recovery? It works on DJ20, but I need more tests on DL17.
adrynalyne said:
have you tried my clockwork recovery? It works on DJ20, but I need more tests on DL17.
Click to expand...
Click to collapse
No
Sent from my SCH-I400 using XDA App
Can you give it a shot and if it doesn't work, give me the exact error message?
adrynalyne said:
Can you give it a shot and if it doesn't work, give me the exact error message?
Click to expand...
Click to collapse
Sure linke to it.
Sent from my SCH-I400 using XDA App
http://adrynalyne.us/files/odin/cont_cwm_recovery_2.tar.md5
http://www.mediafire.com/?3m25rg785awfjsh DL17 zImage
One thing you should note though is the data mounting problem jt fixed with voodoo clockwork, koush never got to it. Im porting 3.0.1 now.
Sent from my SCH-I400 using XDA App
I was just building clockwork for them because I noticed they had the cdrom/mass storage bug with DL17, and there was NO recovery to flash a kernel with...
You can flash a kernel with adb commands.
Sent from my SCH-I400 using XDA App
Im fully aware how to. Most are not. Its for them, not for me. I rather make it easy than hard.
I get what your saying, but a one click works just fine and so does odin... are you working on 2.0 or 3?
Sent from my SCH-I400 using XDA App
Im working on getting these guys through the dark ages, today, instead of a month from now.

[Q] Alternate method of flashing CWM3

Is there a method of flashing CWM3 via update.zip in samsung recovery? I don't have a functional USB cable to use with the One Click method :/. Sorry if this has already been answered, I couldn't find an answer through searching. Thanks in advance!
No, but luckily USB cables are dirt cheap these days, I'm sure you can find one for < $5, or if worst comes to worst go to Sprint and beg a rep to replace your cable.
Lost the one that came with the phone, only have one which I stole from another charger and the device isn't recognized at all (tried it on multiple pcs). I really don't want to buy one as I never use it except for the CWM flash. I have a SD card reader to eliminate the need for cables.
Well, you need one if you're going to flash CWM, if anything just think of it as making your life easier in the long run, no more taking the SD card out just to put files on it.
Frankly I wouldn't mind if there were a way to do it manually in terminal.
*bump* Anyone have any ideas for a method of using terminal to do this?
it can be done in terminal, just open the batch file and read what it does via adb and do that in terminal
I started to do that but cant get past the exploit (rageagainstthecage). I get permission errors and can't even copy the file to /data/local/tmp. Any ideas?
EDIT: It's because the data partition cannot be modified without root access. Somehow adb bypasses this.
Adb runs with root access i suppose... let me look at something..
I basically need a method of obtaining temporary root on the device without using a computer. If i can do that, I can flash cwm using redbend_ua and then flash a rom/kernel for perm root. If it helps, i'm on OTA EC05
EDIT: Does redbend_ua require root access?
EDIT2: Nevermind. I tried running redbend_ua to flash the recovery image and got an error about /data/local/fota missing.
does z4root work on froyo?
http://forum.xda-developers.com/showthread.php?t=833953
if it does.. then
Code:
su
cp /sdcard/redbend_ua /data/local
chmod 755 /data/local/redbend_ua
cp /sdcard/zImage /data/local/tmp/zImage
/data/local/redbend_ua restore /data/local/tmp/zImage /dev/block/bml8
chris41g said:
does z4root work on froyo?
http://forum.xda-developers.com/showthread.php?t=833953
if it does.. then
Code:
su
cp /sdcard/redbend_ua /data/local
chmod 755 /data/local/redbend_ua
cp /sdcard/zImage /data/local/tmp/zImage
/data/local/redbend_ua restore /data/local/tmp/zImage /dev/block/bml8
Click to expand...
Click to collapse
I thought of z4root, and no it doesnt work on froyo, not since eb13 it appears :/. I then thought "if ONLY i hadn't updated to ec05 (my phone came with di18)". Is there a way to get back to di18 without odin or custom recovery? Thanks for all your efforts thus far by the way.
trobertson said:
Is there a way to get back to di18 without odin or custom recovery?
Click to expand...
Click to collapse
No. invisible text
063_XOBX said:
No. invisible text
Click to expand...
Click to collapse
Is there another method of rooting I can do manually? That's the real problem here. I need root to run redbend_ua and from there i can do everything using clockwork. OR some other way to flash clockwork that doesnt require root but it seems that doesn't exist.
Well previously koush had an update.zip that would run in stock recovry and install cwm.. but it stopped working as of froyo, I'm assuming the recovery signature changed. Maybe contact him via twitter or something and see if he ever made a new one..
Sent from my SPH-D700 using XDA App
chris41g said:
Well previously koush had an update.zip that would run in stock recovry and install cwm.. but it stopped working as of froyo, I'm assuming the recovery signature changed. Maybe contact him via twitter or something and see if he ever made a new one..
Sent from my SPH-D700 using XDA App
Click to expand...
Click to collapse
Thanks for the heads up, I PM'd koush. Crossing my fingers on this one >.<!
trobertson said:
Thanks for the heads up, I PM'd koush. Crossing my fingers on this one >.<!
Click to expand...
Click to collapse
Doesn't look like he's going to answer me. I tried getting him on IRC as well and was simply ignored :/.
I don't think he checks these forums often
Sent from my SPH-D700 using XDA App

[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

Categories

Resources