Related
I was trying to root and nand unlock my gfs phone and now Im at a point where usb and nothing is working. All i want do is go back to stock and make it like nothing happened. And no i dont have a nandroid backup. Im screwed. Please help.
i have the sd card error and usb error similar to here: http://forum.xda-developers.com/showthread.php?t=695243
but I cant get into adb because it says device not found.
when I connect USB it says error setting up new hardware in windows.
http://forum.xda-developers.com/showthread.php?t=695243
Sent from my PC36100 using XDA App
she's going to cut his..... SOMEBODY HELP HIM!!!!!
gatorran said:
she's going to cut his..... SOMEBODY HELP HIM!!!!!
Click to expand...
Click to collapse
Yes why is this so much more difficult compared to winmo?
[email protected] said:
http://forum.xda-developers.com/showthread.php?t=695243
Sent from my PC36100 using XDA App
Click to expand...
Click to collapse
Yes read above, I can't get into adb shell to do that. Thanks!
riotburn said:
Yes why is this so much more difficult compared to winmo?
Yes read above, I can't get into adb shell to do that. Thanks!
Click to expand...
Click to collapse
Was adb working for you before? You may need to install some drivers
yes it was. I need this fixed fast she just got it yesterday!, i rather like my testicles, kind of attached to them. I humbly accept all flaming and newbie calling.
riotburn said:
Yes why is this so much more difficult compared to winmo?
Yes read above, I can't get into adb shell to do that. Thanks!
Click to expand...
Click to collapse
so the first part of the commands using fastboot you don't do from adb shell. when you get the phone into fastboot, attach to your computer, you then open command prompt on computer and navigate directories until you are in the android sdk tools folder on your computer wherever it is (most people it is somewhere like c:/android-sdk-windows/tools/)
THEN you type
fastboot oem enableqxdm 0
fastboot reboot
Click to expand...
Click to collapse
no adb shell.
most people have installed adb in such a way that they can access it's tools from any directory. however, at least on my computer, fastboot commands will only work from within the android tools folder where fastboot is located.
hope this helps.
riotburn said:
yes it was. I need this fixed fast she just got it yesterday!, i rather like my testicles, kind of attached to them. I humbly accept all flaming and newbie calling.
Click to expand...
Click to collapse
Did you download the drivers??? they are not the same as the ones installed when you connect the phone....
yea also try pulling the battery and sometimes thats all it takes to get the use to be seen
then tell ur girl to mod the evo her self in case something like this happend my wife rooted and mods her's she love's to tinker
Lol at ruining your girlfriends phone. What tutorial were you following?
Sent from my HTC EVO via XDA App
i love how this is like, atleast the 4th thread someone has ruined there GFs evo due to inexperience, or the inability to read.
seriously, im not even trying to flame. i love reading this stuff.
its like general information for what NOT to do, for us that do read.
if you find the answer that works for you, mind mentioning said message?
i like to see threads that answer the questions at least, rather than have 10 suggestions, and no final response
Dam that sucks
Sent from my PC36100 using XDA App
how do i transfer the files for the second part of the usb is broken?
I was following the one that has pic by pic, and got to the point where pc36 wouldn't work. Saw that with the newest version this method wouldn't work. Went to the tutorial for that workaround and started following that. I think it got mixed up in there and thought i had nand unlocked it. Went to install the new radio, checked the system info and it wasnt the new one and started to get the problems.
Think it is rooted though because i get the # in adb shell.
How does one check to see if they did unlock nand, besides of the problem causing method i did?
I believe i ****ed up the custom recovery part. When I would load custom recovery it would flicker back and forth to the stock recovery, dont know if thats normal.
update: with more searching i found this http://forum.xda-developers.com/showpost.php?p=7136621&postcount=128 to use a update to fix the usb.
I did this and at least now it is charging, still not connecting to computer though it will charge through comp.
Can i flash back to the stock rom now? Will that fix it? How do i flash the stock rom?
Laughed at the thread title. Is the phone messed up, or the girlfriend? Gotta love misplaced modifiers.
If in fact you are rooted, you can use this method. It will put you back to "stock" with root and all the latest updates. If your computer wont mount your phone, you may have to get a micro sd card reader and plug it directly to your usb on your computer to download the files you need. Just make sure the phone is off or you unmount the sd in settings before you remove it. Or you can download them from your phone's browser, but you'll need a file manager to move the files to the root of your sd. If that wont work, your sd card might be corrupted.
http://forum.xda-developers.com/showthread.php?t=715915
dglowe343 said:
If in fact you are rooted, you can use this method. It will put you back to "stock" with root and all the latest updates. If your computer wont mount your phone, you may have to get a micro sd card reader and plug it directly to your usb on your computer to download the files you need. Just make sure the phone is off or you unmount the sd in settings before you remove it. Or you can download them from your phone's browser, but you'll need a file manager to move the files to the root of your sd. If that wont work, your sd card might be corrupted.
http://forum.xda-developers.com/showthread.php?t=715915
Click to expand...
Click to collapse
THANKS! I got it now. I had root but not nand so that prob f'ed it up. The link you sent me requires nand and has go do toasts method. I did that with no problems and had nand unlocked. So I installed the 2.0.... radio and freshevo with no problems. Thanks to everyone who helped, I will post in the first post what I did, at least what i can remember. I love xda, thanks so much guys.
Does anyone know how to fix an EVO that gives this error?
E:Can't mount /dev/block/mmcblk0p1 (or /dev/block/mmcblk0) (No such file or directory) E: Can't mount SDCARD
I was flashing firerant's mtd partition to make up more space to install more apps. When I try to reboot my evo it turns on then vibrates 5 times and shuts down. I can get to hboot mode (volumen down + power). On top instead of s-off it changed to s-on. When I try to use command from my mac's terminal it says error: device not found.
I unrooted by flashing a PC36IMG.zip in hboot. Im in stock now. The phone seems to work fine but now the phone does not recognize the memory card (only in hboot mode) or the usb being plugged in. when i plug in the usb to the computer evo does not give me the notification nor charges or the light come on. Then I tried to root it but it's imposible because I still get terminal's error: device not found because the evo's usb is messed up or something. And since there is no notification to mount the memory card to my computer I can't transfer any files to/from evo.
Then I downloaded Unrevoked3 but still it does not do anything for the same reason the usb is not being detected.
Now I am unroot, evo not detecting memory card (when its on) and usb is messed up (when its on and in hboot mode).
Can Anyone please help me out. Maybe there is a zip that I can flash in hboot mode since is the only place my memory card is being read. Terminal commands through USB doesn't work in hboot or fastboot i dont know why.
Thank you so much everyone.
p.s. I am not blaming this on firerant's mod. I am just describing how it happened. I appreciate all devs work. and I am aware of their disclaimer we can brick our devices. Thank you.
pretty sure you fubar'd your internal partions there buddy.
Go get a new phone. Run over it with your car first.
Sent from my PC36100 using XDA App
Yes that's what I think. The partition is fubar'd, so there is no way to fix that?
Thanks for replying.
mrcamposd said:
Yes that's what I think. The partition is fubar'd, so there is no way to fix that?
Thanks for replying.
Click to expand...
Click to collapse
im sure there is but only by someone who knows what the hell they're doing. lol ;-)
can that person come to the RESCUE :/
lol @ the advice on here. I wouldn't exactly say I know what Im doing but I'll try to help anyway.
From a adb shell run 'cat /proc/mtd' and 'cat /proc/partitions' and that should tell you what your partitions look like. If you can copy them on to here.
Edit: Just remembered he had a custom recovery set up to use with it, were you using that to flash it? You'll most likely need that to recognize the partitions.
If you can flash a zip why not give Caulk's "format all" a try this may restore your partitions. I'm far from a dev but seems like i read about this same problem somewhere and they ran calks zip and presto all was well. I tried to find the thread but couldn't, just what I remember they flashed this then rom then kernel then radios. Of course they were rooted ... maybe rename to PC36IMG.zip ....but if you can flash a zip cant see how this would hurt.
xHausx said:
lol @ the advice on here. I wouldn't exactly say I know what Im doing but I'll try to help anyway.
From a adb shell run 'cat /proc/mtd' and 'cat /proc/partitions' and that should tell you what your partitions look like. If you can copy them on to here.
Edit: Just remembered he had a custom recovery set up to use with it, were you using that to flash it? You'll most likely need that to recognize the partitions.
Click to expand...
Click to collapse
cant adb shell in terminal it does not recognize the device. thanks though
ifly4vamerica said:
If you can flash a zip why not give Caulk's "format all" a try this may restore your partitions. I'm far from a dev but seems like i read about this same problem somewhere and they ran calks zip and presto all was well. I tried to find the thread but couldn't, just what I remember they flashed this then rom then kernel then radios. Of course they were rooted ... maybe rename to PC36IMG.zip ....but if you can flash a zip cant see how this would hurt.
Click to expand...
Click to collapse
thank you so much you are a hero... but will try this next time it happens because I went to the sprint store and told them the new update had messed up my phone hahahaha...
thank you all intelligent people i appreciate your help so much. it means a lot to me.
I'm very happy to announce, that a developer raidzero from rootzwiki forum, has made us a fully working recovery for Samsung Galaxy w i8150!
You can download it from here:
DOWNLOAD
TEMPORARY LINK .... USE THIS IF FIRST ONE DOESN'T WORK
THANKS TO andynroid FOR PROVIDING LINKS!
Flashing recovery is very simple, all you need is root access on your phone, and adb on computer. You just copy downloaded recovery on internal sdcard. Then disconect phone from copmuter. Make sure that USB debugging is on. Now connect it again but don't connect phone memory (computer shouldn't see sdcard and internal memory in Windows explorer), open command prompt and got directory where adb is installed, now enter this:
Code:
adb shell
$su
#dd if=/sdcard/RZR-2.1.4-ancora-rec.img of=/dev/block/mmcblk0p13
This is all. Now turn off phone and turnd it on like this: hold Volume Up + Home + Power button, when Samsung sign appears relese power button but still hold other two, until recovery is loaded. Bamm you are in, and ready to flash something, or backup ! Expolre the recovery, it has a lot of options, you can even choose what color of menus you want .
I would like to thanks raidzero again for all his effort he made! And also big thanks to arco68,for much need informations he provided!
We can now expect, that when developing his recovery and adding new goodies, this recovery will follow others!
great news!! Thanks for your effort!
Has anyone had a chance to test the Recovery?
Will this work on the Samsung Exhibit II?
thanks mate.downloading now. just in case it needs to be recovered. after this we would see custom roms developed by our developers here..
klingel_One said:
great news!! Thanks for your effort!
Has anyone had a chance to test the Recovery?
Click to expand...
Click to collapse
I've tested it and it works
radgoos said:
Will this work on the Samsung Exhibit II?
Click to expand...
Click to collapse
I wouldn't bet that this will work on Exibith II cause every phone has different partitions.
after giving me the command you said to me reacts to: permission denied.. Whi?
lipanz said:
thanks mate.downloading now. just in case it needs to be recovered. after this we would see custom roms developed by our developers here..
Click to expand...
Click to collapse
Definitely...BTW can anyone adv us the rooting method Odin or....
can you show me a screen when you give the command adb?
when I try to restart the device in recovery restarts continuously and never give me the recovery menu
qzem said:
I'm very happy to announce, that a developer raidzero from rootzwiki forum, has made us a fully working recovery for Samsung Galaxy w i8150!
You can download it from here:
www.rzdroid.com/ftp/recovery/gingerbread/2.1.4/RZR-2.1.4-ancora-rec.img
Flashing recovery is very simple, all you need is root access on your phone, and adb on computer. You just copy downloaded recovery on internal sdcard. Then disconect phone from copmuter. Make sure that USB debugging is on. Now connect it again but don't connect phone memory (computer shouldn't see sdcard and internal memory in Windows explorer), open command prompt and got directory where adb is installed, now enter this:
Code:
adb shell
$su
#dd if=/sdcard/RZR-2.1.4-ancora-rec.img of=/dev/block/mmcblk0p13
This is all. Now turn off phone and turnd it on like this: hold Volume Up + Home + Power button, when Samsung sign appears relese power button but still hold other two, until recovery is loaded. Bamm you are in, and ready to flash something, or backup ! Expolre the recovery, it has a lot of options, you can even choose what color of menus you want .
I would like to thanks raidzero again for all his effort he made! And also big thanks to arco68,for much need informations he provided!
We can now expect, that when developing his recovery and adding new goodies, this recovery will follow others!
Click to expand...
Click to collapse
Thanks again, will try this ASAP, just a few questions:
Is /dev/block/mmcblk0p13 the Recovery partition??
Is it been overwritten by the dd if.......of??
Should the original stock recovery?? be backed-up/saved first??
Is there an MD5 or anything to check file integrity:
This could be used on the Device: Android File Verifier
Can the procedure be done using Terminal Emulator on the phone?
Do I need to have stock ROM for it to work?
snake873 said:
after giving me the command you said to me reacts to: permission denied.. Whi?
Click to expand...
Click to collapse
There are two possible reasons for this either you didn't run su command first, or you don't have rooted phone.
irishpancake said:
Thanks again, will try this ASAP, just a few questions:
Is /dev/block/mmcblk0p13 the Recovery partition??
Is it been overwritten by the dd if.......of??
Should the original stock recovery?? be backed-up/saved first??
Is there an MD5 or anything to check file integrity:
This could be used on the Device: Android File Verifier
Can the procedure be done using Terminal Emulator on the phone?
Click to expand...
Click to collapse
1. Yes /dev/block/mmcblk0p13 is recovery partition
2. It is gonna be overwritten with costum one.
3. You can back it up that you reverse dd command. Or I can upload original recovery.
4. There isn't MD5 cause noone made it , you only need MD5 file if you would like to flash this via Odin.
nakTT said:
Do I need to have stock ROM for it to work?
Click to expand...
Click to collapse
Do you know any custom rom for our phone ? But no it is not rom related.
snake873 said:
can you show me a screen when you give the command adb?
when I try to restart the device in recovery restarts continuously and never give me the recovery menu
Click to expand...
Click to collapse
What screen? From computer or phone? Your phone need to be turned on and booted in android when running dd command.
qzem said:
There are two possible reasons for this either you didn't run su command first, or you don't have rooted phone.
1. Yes /dev/block/mmcblk0p13 is recovery partition
2. It is gonna be overwritten with costum one.
3. You can back it up that you reverse dd command. Or I can upload original recovery.
4. There isn't MD5 cause noone made it , you only need MD5 file if you would like to flash this via Odin.
Do you know any custom rom for our phone ? But no it is not rom related.
What screen? From computer or phone? Your phone need to be turned on and booted in android when running dd command.
Click to expand...
Click to collapse
From computer
---------- Post added at 12:09 PM ---------- Previous post was at 11:41 AM ----------
ahahaha ok ok I did thank you very much for your patience
qzem......top marks for your persistence
qzem said:
There are two possible reasons for this either you didn't run su command first, or you don't have rooted phone.
1. Yes /dev/block/mmcblk0p13 is recovery partition
2. It is gonna be overwritten with costum one.
3. You can back it up that you reverse dd command. Or I can upload original recovery.
4. There isn't MD5 cause noone made it , you only need MD5 file if you would like to flash this via Odin.
Click to expand...
Click to collapse
Thanks, gotta learn ODIN first,
btw, thanks for the ODIN d/l........installed it, but still unsure how to proceed???
I have latest Kies installed on my laptop, any reason why you do not use it?? It appears to allow back-ups and restores, also new firmware d/l.
As I am new to Samsung, and also ODIN, but does using ODIN have advantages over Kies, and is it safer to upgrade new f/w with ODIN or Kies, do you lose root, or anything else??
BTW, on the MD5 thing, for the RZR-2.1.4-ancora-rec.img
I used MD5 Checksum Tool from http://www.novirusthanks.org/product/md5-checksum-tool/
to generate the MD5.
File: RZR-2.1.4-ancora-rec.img
Size: 5230592 bytes
Publisher: Unknown
Checksum (MD5): 3b9cc641aa898910b5bad911bd38f675
*File generated by MD5 Checksum Tool*
http://www.novirusthanks.org
Click to expand...
Click to collapse
I just think it is good security practice to check file integrity before applying on your device, as many things can happen, like data corruption, while transferring file from download on Laptop to SD card, and best to check file on device SD or Internal Storage with AFV against MD5 generated at source.........
which I did not check at source, but I am just illustrating for example!!
[BTW, lots of MD5's on rzdroid.com recovery ftp site, here, but not sure of our .img file
The above MD5 is what I got from the d/l file
Thanks again, I saw your stuff with raidzero on rootzwiki.........
top marks for your persistence, and a good result for all i8150 owners.
irishpancake said:
Thanks, gotta learn ODIN first,
btw, thanks for the ODIN d/l........installed it, but still unsure how to proceed???
I have latest Kies installed on my laptop, any reason why you do not use it?? It appears to allow back-ups and restores, also new firmware d/l.
As I am new to Samsung, and also ODIN, but does using ODIN have advantages over Kies, and is it safer to upgrade new f/w with ODIN or Kies, do you lose root, or anything else??
BTW, on the MD5 thing, for the RZR-2.1.4-ancora-rec.img
I used MD5 Checksum Tool from http://www.novirusthanks.org/product/md5-checksum-tool/
to generate the MD5.
I just think it is good security practice to check file integrity before applying on your device, as many things can happen, like data corruption, while transferring file from download on Laptop to SD card, and best to check file on device SD or Internal Storage with AFV against MD5 generated at source.........
which I did not check at source, but I am just illustrating for example!!
[BTW, lots of MD5's on rzdroid.com recovery ftp site, here, but not sure of our .img file
The above MD5 is what I got from the d/l file
Thanks again, I saw your stuff with raidzero on rootzwiki.........
top marks for your persistence, and a good result for all i8150 owners.
Click to expand...
Click to collapse
Well I really don't know that is better to use Kies or Odin. If you want official and (what is supposed to be tested) firmware, tha you better use Kies (but well even with kies your phone could get bricked, I've learned that from one user here ). If you want to flash latest firmware, which sometimes is not availible on all the countries, and you can't get it from Kies fast enaught, than I suggest odin is the choice. I prefere Odin, cause I don't like official stuff .
To use Odin is very simple. You need to turn on phone with Volume Down + Home + Power. When you are prompt (on hte phone),wether to conutioue od cancle, you connect phone and computer with USB cable, and choose contuinu, now you are in download mode. Then all you have to do, to choos proper .ops file (button OPS) in odin, an proper firmware (usually you choos that under One Package button, if you have one package in tar.md5), then you wait for chekcking md5. When is checked you just click Start, and wait for stuff to happen.
Don't forget that there is a possabiltiy that something might go wrong with flashing, but it is not that big one. I suggest, that you first made full nandorid backup with recovery, if something goes wrong, you can boot you phone in recovery and restore it totaly. And one more suggestin when flashing, do it with latop(if possible), so that you have battery and power cable plugged in laptop, if electricyty goes out, that you still have battery to run laptop.
And thanks for the support you guys are showing to me, since I'm not a developer. I try really hard, to get people that are willing to help us developing better roms for our phone !
qzem said:
There are two possible reasons for this either you
Do you know any custom rom for our phone ? But no it is not rom related.
Click to expand...
Click to collapse
Spot on. I just need to know if it is ROM related (that I need a ROM file on my PC).
Thanks for the reply.
Hey there, just a noob question:
Where are adb drivers installed? I'm working under Windows 7.
I tried to google this and ended up here /developer.android.com/sdk/index.html
and downloaded the first two files, but I'm unsure what to do now. Thanks in advance!
Hey qzem,
Am I right, that the adb driver should be installed, when i first installed Kies?
Is your Guide How-To Install the recovery also working on my mac? I think so, or am I wrong?
Perhaps you already figured by now, I'm new to Android!
There is one more thing i can't seem to figure out:
In foreseeable future, there are hopefully some nice custom roms for the Galaxy W. Do I have to install recovery everytime i flash a new Rom? Or is it like a bios, that has nothing to do with the actual Android System?
Thanks for your help in advance
fender90 said:
Hey there, just a noob question:
Where are adb drivers installed? I'm working under Windows 7.
I tried to google this and ended up here /developer.android.com/sdk/index.html
and downloaded the first two files, but I'm unsure what to do now. Thanks in advance!
Click to expand...
Click to collapse
For adb, you need to download Android SDK from here. Download zip file and extract it somwhere. Than go in folder where you have extract it and run SDK Manager, from there you will install adb rivers and everything else. When you are done (it could take a while, to download and install everything), open Command promnt and follow the instrucions I've wrote in first post.
klingel_One said:
Hey qzem,
Am I right, that the adb driver should be installed, when i first installed Kies?
Is your Guide How-To Install the recovery also working on my mac? I think so, or am I wrong?
Perhaps you already figured by now, I'm new to Android!
There is one more thing i can't seem to figure out:
In foreseeable future, there are hopefully some nice custom roms for the Galaxy W. Do I have to install recovery everytime i flash a new Rom? Or is it like a bios, that has nothing to do with the actual Android System?
Thanks for your help in advance
Click to expand...
Click to collapse
The same goes for mac users, there is also Android SDK for mac. You can install Kies before this, but you need both because kies includes drivers for this phone exactly. As far as recoverey goes, if it is not included in ROM, which you flash, I think you'll need to install it again. I hope that developers will include recovery in their roms.
Thanks so far qzem,
It seems like theres someone in your Cyanogenom-Forum-Post qzem, who is trying and willing to help making a custom rom. But he seeks for som guidance!
Perhaps someone with experience like, arco can take him under his wings!
Hi there,
i would like to thank you. Everything works like a charm.
Did the flash, tried the recovery.. and uaaaahhhh....
...i forgot to backup the original recovery!
can someone please, please upload it to somewhere??
thx.
Zetup-EXe
[HOWTO] ClockworkMod Recovery & TWRP - Upgrade/Downgrade (Touch/Non-Touch Recovery)
IF YOU TRASH YOUR PHONE USING THIS PROCEDURE, THEN IT IS A VERY GOOD INDICATION YOU ARE AN IDIOT AND SHOULD NOT BE FLASHING ANY ROMS NOR PARTICIPATING ON THESE FORUMS. . . . JUST SAYIN'. . . .
Please be VERY careful when using this method as you can brick your phone. Make sure you triple check the file you downloaded is the right size and placed in the right area, but most importantly that the command lines you type are exactly right. If you are not comfortable using this method, then please do not and go find a flashable version of these recoveries.
I've posted a procedure to format/'flash' your recovery while on your phone in one of the threads on here and was asked by a Forum Mod to make a quickie guide to be placed as a sticky on the dev boards so others might benefit.
Anyway, here is a very quick and easy way to change your ClockworkMod recovery with a couple of command lines.
The TWRP link is in the second post.
Now for the ClockworkMod Instructions:
1. First, go here and look up your ClockworkMod recovery that pertains to your phone: http://www.clockworkmod.com/rommanager
2. Download the .img file for your phone and save it on your computer.
3. Rename the .img file to recovery.img and save it to your internal sd card of your phone. For example: recovery-clockwork-6.0.1.4-hercules.img ------> recovery.img
4. Open up Terminal Emulator on your phone and type the following 2 commands:
su
dd if=/sdcard/recovery.img of=/dev/block/mmcblk0p22
(please note the second command is a one line command with spaces between "dd & if=" and ".img & of=")
If your Rom identifies your internal sdcard as /emmc instead of /sdcard, then make the adjustment to command line (dd if=/emmc/recovery.img) instead of what is posted above.
That simple.
You can also issue these commands from adb shell if you are connected to your computer.
If Terminal Emulator does not have Superuser or SuperSU permissions for root privileges then make sure it does. You can also go from NON Touch CWM to Touch CWM using this and vice versa. Simply make sure you have the right recovery for your phone and rename it to recovery.img.
As for explanations:
dd if= command is a common Unix program whose primary purpose is the low-level copying and conversion of raw data.
dd stands for "data description"
if stands for "input file"
of stands for "output file"
the = is the location of the data you are using. ie. /sdcard/recovery.img
the /dev/block/mmcblk0p22 is the location/partition of the recovery on your phone.
So essentially you are doing a low level rewrite of the recovery image on your phone via command lines.
***Also, the best way to remember this command line is to not to. Copy the command line and save it to your own personal contact info in Google under Notes and then you will have it with you wherever you go. You really do not want to mess with getting it wrong. You could brick your phone if you mess things up.
Anyway, I hope this helps. . . . it really is very easy to execute without fault.
Works with TWRP too.
This also works with changing to and from TWRP. Download the image (for our phones it's TWRP 2.3.1.1) rename it to recovery.img and follow the above instructions and you are good to go.
Follow this link to get the image file: http://teamw.in/project/twrp2/101
***I attached the old TWRP 2.2.2.0 is case you run into problems with the newer versions not restoring backups properly or renaming backups correctly.***
Excellent Thread, I hope Dev's requiring specific CWM versions can link to your post.
Thanks for your efforts.
Noellenchris
XDA Forum MOD
Thanks for the instructions! Thanks even more for explaining the command lines.
Just thought I'd point out a small bug with the Touch Recovery. If you flash one of the newer ICS roms like Darkside Evolution through the Touch Recovery, once booted, the ROM WILL NOT SLEEP through time out. I've confirmed this with 2 separate ICS roms. Flashing non-touch recovery through Rom Manager fixes this problem.
Wouldn't it be easier to use gscript and run the commands as you need them?
Thanks for the HOW TO I actually was looking for it.
What is wrong with ROM Manager? I use it to go between Touch and normal all the time and it works flawlessly.
dextroamphetamine said:
What is wrong with ROM Manager? I use it to go between Touch and normal all the time and it works flawlessly.
Click to expand...
Click to collapse
For some people Rom Manager doesn't work. On the T-Mobile SGH-T989 Galaxy SII, Rom Manager will only allow you to go to 5.0.2.6 not 5.0.2.7. And, I think you have to upgrade Rom Manager to go to Touch. I bought Rom Manager, and don't use Touch Recovery, so I am not sure.
I like to use the command structure verses program because I know it works, it's fast, and I can see the results if an error occurs.
Oh yeah...this was really simple...Thanks...went from Touch back to Non Touch.
Give this a try
If you want a simple way to flash the Touch Recovery then give this a try. I will be adding the Hard Recovery as well in the next release.
SGSII T989 Root Toolkit
http://forum.xda-developers.com/showthread.php?t=1650908
http://forum.xda-developers.com/showthread.php?p=26200755
I get a write error: No space left on device. 1001+0 records in 1000+0 records out 512000 bytes transferred in 0.132 secs.
I reboot into recovery and it's still on 5.0.2.6
Edit: so i closed the terminal and I ran it again, and now my phone won't turn on. I get a USB device in windows called QHSUSB_DLOAD. I hold the power button, and the device disappears, but it won't turn on. I let go of the button, the same device reappears.
albanianbrotha said:
Edit: so i closed the terminal and I ran it again, and now my phone won't turn on. I get a USB device in windows called QHSUSB_DLOAD. I hold the power button, and the device disappears, but it won't turn on. I let go of the button, the same device reappears.
Click to expand...
Click to collapse
hate to be the dude that tells you this but i'm pretty sure qhsusb_dload is magic windows talk for "hard bricked phone." had that problem a while back. however all is not lost - these guys have a great reputation for Lazarus-ing dead phones.
hobakill said:
hate to be the dude that tells you this but i'm pretty sure qhsusb_dload is magic windows talk for "hard bricked phone." had that problem a while back. however all is not lost - these guys have a great reputation for Lazarus-ing dead phones.
Click to expand...
Click to collapse
Haha no worries bro. I mean worries that it failed for no reason, but I already sent it in, he just got it today. Same person you linked. Definitely trying to install ics again when i get it. Plus I think the ota ics for tmo came out yesterday or something? Probably a better experience than what was already out there with the radio and stuff.
the files from the CWM site are not .img for me, they are .ndif is it the same procedure?
MustangFTW said:
the files from the CWM site are not .img for me, they are .ndif is it the same procedure?
Click to expand...
Click to collapse
No! Do NOT use this procedure with that file extension!
What recovery are you trying to install? And for what phone? I briefly ran my cursor over the various files and the download links are either .img or .zip files. I did not see .ndif file extension.
PM me if you need additional help.
Would you happen to have the .img file for 5.0.2.7??
Edit* Nvm.. a quick google search and I was able to find it. You are a life saver.. I tried updating my recovery to the 6.0.1.2 Hercules port and for a couple days, it was working great up until an hr. ago. Nothing would flash and it would just hang in recovery... so I found this thread and thankfully I was able to downgrade back down to 5.0.2.7.
If you were local, I would take you out and get you piss drunk for helping me save my device. Cheers!!!!
fresherthanU said:
Would you happen to have the .img file for 5.0.2.7??
Edit* Nvm.. a quick google search and I was able to find it. You are a life saver.. I tried updating my recovery to the 6.0.1.2 Hercules port and for a couple days, it was working great up until an hr. ago. Nothing would flash and it would just hang in recovery... so I found this thread and thankfully I was able to downgrade back down to 5.0.2.7.
If you were local, I would take you out and get you piss drunk for helping me save my device. Cheers!!!!
Click to expand...
Click to collapse
You're welcome, I'm glad I could help you. But, the link to the .img files is in the OP instructions. . . .
Unfortunately this method did not work for me... I have tried many ways to update my CWM and none of them worked, it is almost hopeless for me
Good news! You made front page! http://www.xda-developers.com/andro...gn=Feed:+xda-developers/ShsH+(xda-developers)
I figured Id start another thread so no one has to search and read thru all other threads for help like I had to.
I had to write this because i thought other guides were incomplete, and frankly they didnt work.
I will try to update and make things easier to read and use spellchecker when time permits.
and add in-between steps that i left out because i have no dam time. Thats why i call it expert guide-you need some knowledge of doing this.
This is just to help out someone who has had a hard time with other guides
It is not a step by step
Knowledge of cygwin and adb is expected.
Learn it, and how to setup, using google and xda like the rest of us.
I TAKE NO RESPONSIBILITY OF BRICKING YOUR PHONE ANY MORE THAN IT IS.
Here is were I made the mistake:
http://forum.xda-developers.com/showthread.php?t=1745865
These are the 2 files
1.Galaxy-S-fre3-2.51.zip
2.Galaxy-S-fre3-MD4FirmwareModemAIO.zip
First of all I ALWAYS CHECK MDMSUMS
The second zip was flashed first, and wamo no andro
Heres my specs.
Android Ver:
4.3
Baseband Ver:
L710VPUCMK3
Build:
JSS15JL710VPUCMK3
Hardware Ver:
L710.14
Im guessing it bricked my phone because I flashed the Galaxy-S-fre3-MD4FirmwareModemAIO.zip before the actual rom itself "Galaxy-S-fre3-2.51.zip"
Obviosly I should have done it the other way around, well im only hu............ngry. haha, so im a knuklehead.
I refuse to go to that particular site to read the first post and see if there is some sort of DONT FLASH OUT OF ORDER OR RISK LOOSING A LIMB, warning posted.
I thought i lost my device (this is still a bad-ass phone, almost too nice to be in a roofers pouch and getten toren up. But it takes really nice pictures of my custom work, and takes em fast so i can get back to work.
I lost 12 hours for stupid mistake, (im sure someone will say thats the business, of course thats why we do it.)
Not to mention the last device i bricked was my first (Hero) and thought was my last.
When you play the Rom Game you may get Ram'd
I will post this to that fre3 site, however unless the OP makes note of this others will be in the same mess.
The only life left in the device, was red light, when battery removed (when battery was placed in during charge, red light went out in 5 to 10 sec.)
When battery was in unit, no lights at all.
I noticed when usb cable attached to ubuntu, oh **** i forgot what and how i saw it but it was some kind of Qualcomm Device _DLMODE or somthing.
I will edit this post when i find it again, but anyway that led to nothing.
My first attempts were made following this guide: http://forum.xda-developers.com/showthread.php?t=2369125
I couldnt figure out by reading the threads if how I was to format the fat32 partition default 8 or 4 or 1Mg
I couldnt understand why we would have to try to write the image over and over...Why it wouldnt write it right the first time.
I had a hard time trying to write the image file ..debrick_sph_l710.img to sdcard using my v-box..
(Virtual-Box under windows 8 with Ubuntu 13.10 installed ....Android-Kernel-Build ready ).
After trying all the different ways and different images, I said screw it i give up.
.........Till after dinner
wife made a roasted chicken not gonna be late.
Finally I made my own image from my wifes phone, because we bought them at the same time.
One problem hers isnt rooted and she wasnt about to let me touch it.............
Solution: I bought her a galaxy4 for 49.00 /w upgrade, now i have 2 galaxy 3's. But only one works.:/
That was a pain rooting because she always excepts the firmware upgrades when they come over air.
Couldnt get the "seLinux seAndroid" thing so i just went back to 4.1 for now so that i could adb.
Heres What Did It...
http://forum.xda-developers.com/showthread.php?t=2345860
HERES HOW I DID IT
To extract a de-brick image from your phone (an UnBricked Phone) do in an adb shell:
If you know the partition use:
dd if=/dev/block/mmcblk0 of=/sdcard/HomefixSprint_S3_L710.img bs=1048576 count=70
If not use:
dd if=/dev/block/platform/msm_sdcc.1/by-name/modem of=/sdcard/HomefixSprint_S3_L710.img bs=1048576 count=70
MY TERMINAL SHOWS:
C:\Users\dad>adb shell
[email protected]:/ # busybox dd if=/dev/block/mmcblk0 of=/sdcard/HomefixSprint_S3_L710.img bs=1048576 count=70
0 of=/sdcard/HomefixSprint_S3_L710.img bs=1048576 count=70 <
70+0 records in
70+0 records out
73400320 bytes (70.0MB) copied, 4.578239 seconds, 15.3MB/s
Take that image, copy it to your cygwin directory and write it to an unformatted 16mb sdcard using cygwin:
TO GET THE SDCARD READY:
get EaseUS Partition Master Free Edition-Free For Home Users
and find the sdcard, its about 14.82GB, if u have more than 1 your on your own.
Select that one, and delete all partitions.
Then, New partition, select fat32, and then finish by applying the operations.
DO NOT FORMAT
IN CYGWIN:
Get sdcard info:
cat /proc/partitions
MY TERMINAL SHOWS:
[email protected] ~
$ cat /proc/partitions
major minor #blocks name
8 0 976762584 sda
8 1 976759808 sda1
8 16 117220824 sdb
8 17 358400 sdb1
8 18 116859904 sdb2
8 32 976762584 sdc
8 33 976759808 sdc1
8 48 244198584 sdd
8 49 244196001 sdd1
8 64 976762584 sde
8 65 976657408 sde1
8 80 976762584 sdf
8 81 976760001 sdf1
8 96 976762584 sdg
8 97 976760001 sdg1
8 112 976075776 sdh
8 113 976074752 sdh1
8 128 15558144 sdi
8 129 15558110 sdi1
[email protected] ~
$ ls
debrick_sph_l710.img HomefixSprint_S3_L710.img kitchen
[email protected] ~
$ dd if=HomefixSprint_s3_L710.img of=/dev/sdi
143360+0 records in
143360+0 records out
73400320 bytes (73 MB) copied, 338.771 s, 217 kB/s
I DID WHAT I WAS SUPPOSED TO DO:
Put battery in
Connect usb cable
Insert sdcard
Vol-up/Home and Power
I felt the vibration no more than a second after pressing power (along with vol_dwn and home key pressed and held)
As you can imagine, my adrenilin was pumpped to the point of feeling like i smoked a pack of camel ciggirettes, AGAIN, as i try to boot the phone.
I knew i was out of the woods after I saw the samsung logo.
It Skipped past download.
I was able to boot right into my desktop, however there were no signal bars.
and the Baseband ver: was unknown.
I powered down the phone (man that was hard to do) but i did.
Tried to get into download mode but failed at first, recovery failed also.
Finally got to download then i was good.
NOTES:
After I revived the phone I had nothing too loose because now I had 2 S3's, so I played a bit.
Its fun to brick your phone on purpose haha
I fed this PIECE OF S#!+ Galaxy-S-fre3-MD4FirmwareModemAIO.zip to my phone the first time and i lost 12 hrs plus the time write this.
:The debrick_sph_l710.img or the Debrick_Sprint_S3_L710_4.3.img did not work for me
:I did not need the class 10, class 4 worked too
:did not need cable attached
:did not Matter wich order i put battery, sdcard, usb-cord to boot
:did not format card
nly took 1 try to write working image each time ( didnt take several attemts) I wrote and tested 3 different images.
:Upon booting It seems to be the same each time ,couple three four sec (out of a few times playing it may have taken 10sec to boot on one occasion).
:I think the issues with ubuntu was,the sdcard was not ejecting properly and corrupting the image.
:If you have a sucssesful write to sdcard, it may not show up in file explorer until you pull out card reader and re-insert it... then it will show up in file explorer as a folder called "image" with bunch of files or somthing in it, then you know it wrote ok.
:for some reason after i haha... BRICKED MY SG3 ON PURPOSE....Oh my GOD....Im SHOT, booted to my homemade image, i was able to boot into recovery as well as Download.
:Not for nothen I tried to:
dd if=/sdcard/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/boot.img of=/dev/block/platform/msm_sdcc.1/by-name/boot
dd if=/sdcard/modem.img of=/dev/block/platform/msm_sdcc.1/by-name/modem
(Remember i was able to boot to system, so adb worked)
Did not work, however it may have worked if i used the syntax...mmcblk0 and such.
Questions:
Why is my debrick.img smaller than others on this site
Why my image works for my device and no others will work
Are all phones with these snapdragon cpu's have the ability to "sdcard boot"
Why do we spend endless hours with our phones and forget we have a family.
MY FILE:................ http://rooferdave.com/Downloads/sprintsg3.html
Like I replied to you in the other thread, the problem with what you did is that you flashed MD4 firmware while on the MK3 bootloader. It has nothing to do with the ROM.
At the time the MD4 rom was posted, MK3 had not even come out. So anger at the lack of a warning in that thread is misguided.
Further, there are multiple places where you could have found information on this.
1) http://forum.xda-developers.com/showthread.php?t=2541343
2) http://forum.xda-developers.com/showthread.php?t=2637424
I did the EXACT same thing as you did and bricked my S3 this morning.
I've attempted your fix but I am really all over the place.
Is there any way your guide could be simplified/condensed for someone like me?
I can get Ubuntu to run on another machine. I have a 16GB Micro SD. But I am not sure at all on the following things...
a) which file I am supposed to flash to the micro sd card
b) once I open Ubuntu/linux how to find that file by navigating to my Windows installation.
If you don't have time...thanks anyway for your guide..I'm sure I'll get there eventually.
CNexus said:
Like I replied to you in the other thread, the problem with what you did is that you flashed MD4 firmware while on the MK3 bootloader. It has nothing to do with the ROM.
At the time the MD4 rom was posted, MK3 had not even come out. So anger at the lack of a warning in that thread is misguided.
Further, there are multiple places where you could have found information on this.
1) http://forum.xda-developers.com/showthread.php?t=2541343
2) http://forum.xda-developers.com/showthread.php?t=2637424
Click to expand...
Click to collapse
No reason why op didnt take the extra step and warning us this can happen, I would.
My time is very limited lately, and dont have the time to read thru all fourms.
As far as my residual anger, left over from wasting my time, unbricking my phone. Oh well
Like I said I would have placed a warning for half-noobs like myself to prevent this. OTHERS DO!
And not for nutten I still dont see any warning up it up.
edderspcs said:
I did the EXACT same thing as you did and bricked my S3 this morning.
I've attempted your fix but I am really all over the place.
Is there any way your guide could be simplified/condensed for someone like me?
I can get Ubuntu to run on another machine. I have a 16GB Micro SD. But I am not sure at all on the following things...
a) which file I am supposed to flash to the micro sd card
b) once I open Ubuntu/linux how to find that file by navigating to my Windows installation.
If you don't have time...thanks anyway for your guide..I'm sure I'll get there eventually.
Click to expand...
Click to collapse
Sorry I really dont i wasted it unbricking my phone
Look on the bright side, you have a really good shot of unbricking your phone.
wasnt long ago this kind of thing would be impossible.
Good Luck
Homefix said:
Sorry I really dont i wasted it unbricking my phone
Look on the bright side, you have a really good shot of unbricking your phone.
wasnt long ago this kind of thing would be impossible.
Good Luck
Click to expand...
Click to collapse
Actually got it. I got some help on Cygwin in the other thread and trial and error from there. Your debrick file was the one that finally worked. Thanks.
Homefix said:
No reason why op didnt take the extra step and warning us this can happen, I would.
My time is very limited lately, and dont have the time to read thru all fourms.
As far as my residual anger, left over from wasting my time, unbricking my phone. Oh well
Like I said I would have placed a warning for half-noobs like myself to prevent this. OTHERS DO!
And not for nutten I still dont see any warning up it up.
Click to expand...
Click to collapse
The biggest thing that sticks out here is the word READ. You say you don't have time to read the forums, but yet you find the time to search a thread that has not been update since July 2013 in the OP (Last edited by freeza; 31st July 2013 at 12:36 AM.). And yes Noobs will be Noobs, But not all Noobs don't take the time to read before flashing stuff to there phone.
This was the one that worked!!! Thanks!
Question
Where you asay Connect usb cable was it plugged into power or your computer ?
WOW! is all I can really say.
Well that and Freeza! Really!
Freeza, BTW has 9,465 thanks on XDA. oh, I would also add that heaven help us if dev has to start putting warnings on that state "you may have problems with any future upgrades that samsung/sprint may put out in the coming years".
I guess I could say even more. Just won't...
Sent from my SPH-L710 using Xparent Cyan Tapatalk 2