Related
I had been looking into Flashing the NEW Radio recently and was put off by people saying you can easily brick your device "CAUTION" and use ADB and push this here and push this there and it gave alot of people an uneasy fealing. So now that I was schooled on how to do it the EASY WAY I figured I would pass this on to anyone needing the correct info. Always Verify your MD5 SUM Prior to installation.
1: Find the new radio of your choice. Make sure it is named PD15IMG!! ( It should be allready )
2: Use an MD5Sum tool, such as ManD5 from the Android Market to compare the MD5 hash of the original download to the MD5 of your downloaded radio image. FLASHING A CORRUPTED RADIO IMAGE WILL BRICK YOUR PHONE.
3: Place the PD15IMG radio zip file onto your SD card (just like you would a new ROM).
4: Boot into H-BOOT. I use quick boot from the market (just push Bootloader button)
5: Once in H-BOOT select BootLoader. it will ask you to apply update? Yes
6: Let file load completely. you will see a status bar on top right of screen.
7: It will prompt you to reboot... do so and let it load. you will now have a new radio.
This turned out to be so easy.
But as with all the different ways to do somthing, you do this @ your own risk. I cant be responsible if YOU F-UP!!
With that being said, Happy EASY Radio Flashing.
I used this exact Method on my MT4G and it worked Flawless. NOTE: I did Delete the PD15IMG file on SD after proper install, so I would not have any issues with the file after installation. Also so it would'nt get confused with other radio files.
NOTE: It doesnt matter if you used G-Free Method to ROOT, or VISIONary/ROOT.SH method. This will work. I do recommend that you have the ENG. BOOTLOADER.
Correct MD5's for the New Radio's:
•26.03.00.04
md5: ea7a58f16a6f9a7d8ffe96d42db10485
•26.03.02.26 (Stock)
md5: e4e7cb2e5bf58a5222cb1f8ae91499e1
•26.08.04.30
md5: 3d054d4bdbb0e6b81954e5742c8ba24f
•26.09.04.26
md5: f27e4686302fa7e6a72965f80495df44
It's not that people are trying to scare you by going the adb route to install the radio, it's just that you can check md5sum easily that way. If you download a corrupted file and try to flash it, YOU WILL BRICK YOUR PHONE. This method is fine for people who are familiar with flashing on android but to noobs it's very dangerous. I think you should add to op that you can download an app from the market like Android File Verifier for free to check md5sum, that way someone doesn't try your method and end up bricking their phone. And believe me, it its very possible to download a corrupted file. Just the other day I went to flash the newest radio, I downloaded, checked the md5sum and it wasn't even close, so I deleted it, downloaded from the same link and got the correct one on second try. If I would have flashed without verifying, I would have an expensive paper weight on my hands. Better to be safe than sorry!
Sent from my HTC Glacier using XDA Premium App
I been wanting to flash a new radio, but I'm not sure if I can because I went with the visionary and root.sh route and I read that s-off with radio is different with being just s-off. So, Im wondering, is still possible to flash a radio without going thru the g-free way?
vabeach454 said:
1: Find the new radio of your choice. Make sure it is named PD15IMG!!
2: Place the PD15IMG radio zip file onto your SD card (just like you would a new ROM).
3: Boot into H-BOOT. I use quick boot from the market (just push Bootloader button)
4: Once in H-BOOT select BootLoader. it will ask you to apply update? Yes
5: Let file load completely. you will see a status bar on top right of screen.
6: It will prompt you to reboot... do so and let it load. you will now have a new radio.
Click to expand...
Click to collapse
That is horrible advice. Your steps skip verifying the files MD5 signature. If you try to flash a radio from a corrupt file, you will brick your phone. The chances of a bad download a low, but I would never ever risk it...
Also, the method above is the exact same actual flashing method as what's in the official radio thread in the Dev section. You just use another method to move the file to your SD and skip the MD5 verification. If ADB scares you so much, you can always use an app like ManD5 instead. Whatever method you use, verify the MD5 before flashing!
Yes visionary will allow for radio flashing. I'm running sense 3.0 virtuous, newest videotron radio. All with visionary, never touched gfree on this device.
Sent from my HTC Vision using XDA App
I totally agree with doing it the easy way, but not at the risk of skipping the step on verifying md5. Adb is essentially doing the same thing as dropping the file onto root of sd anyways. Run the verifier and then complete original steps. Happy flashing!
Sent from my HTC Glacier using XDA App
TeeJay3800 said:
That is horrible advice. Your steps skip verifying the files MD5 signature. If you try to flash a radio from a corrupt file, you will brick your phone. The chances of a bad download a low, but I would never ever risk it...
Also, the method above is the exact same actual flashing method as what's in the official radio thread in the Dev section. You just use another method to move the file to your SD and skip the MD5 verification. If ADB scares you so much, you can always use an app like ManD5 instead. Whatever method you use, verify the MD5 before flashing!
Click to expand...
Click to collapse
I been having this app for a while now and never figured out how to use it lol.
TeeJay3800 said:
That is horrible advice. Your steps skip verifying the files MD5 signature. If you try to flash a radio from a corrupt file, you will brick your phone. The chances of a bad download a low, but I would never ever risk it...
Also, the method above is the exact same actual flashing method as what's in the official radio thread in the Dev section. You just use another method to move the file to your SD and skip the MD5 verification. If ADB scares you so much, you can always use an app like ManD5 instead. Whatever method you use, verify the MD5 before flashing!
Click to expand...
Click to collapse
ADB doesnt scare me!! It sure does scare alot of people that are unsure how to use it. You guys are correct and I will add to the OP The APP that shows how to find your MD5 SUM.
But really Bashing me for this EASY WAY to do things is pathatic!! Go Troll somewhere else.
The Method here is not the same as the radio OP. That OP is ADB specific!! Get your FACTS Straight!! I was done in 2 Minutes doing it this way.
The only thing I ever really used ADB for was to Flash new splashscreens and even now you can do it with terminal emulator.
Thanks! I, myself was afraid to flash it but your way totally was a piece of cake! Don't mind the simple people.
Sent from my HTC Glacier using XDA Premium App
vabeach454 said:
ADB doesnt scare me!! It sure does scare alot of people that are unsure how to use it. You guys are correct and I will add to the OP The APP that shows how to find your MD5 SUM.
But really Bashing me for this EASY WAY to do things is pathatic!! Go Troll somewhere else.
The Method here is not the same as the radio OP. That OP is ADB specific!! Get your FACTS Straight!! I was done in 2 Minutes doing it this way.
The only thing I ever really used ADB for was to Flash new splashscreens and even now you can do it with terminal emulator.
Click to expand...
Click to collapse
I really hope you were talking about the other guy and not me. I wasn't bashing or trolling, just stating facts. Android File Verifier is really easy to use, just open app, find file, then long press the file and select check md5sum. I agree that your way is easier, just not as safe, unless you add some sort of way to verify the file.
Edit: I now see that you quoted the other guys post lol
Edit again: lol just seen updated op too!
I'm trying to protect users from screwing up their phones and you accuse me of trolling? Give me a break.
YOU need to get your facts straight. The official radio thread uses the exact same method of flashing as your instructions (through hboot). The only difference is you omit the important step of verifying the MD5.
Sent from my HTC Vision using XDA Premium App
sckboy78 said:
Thanks! I, myself was afraid to flash it but your way totally was a piece of cake! Don't mind the simple people.
Sent from my HTC Glacier using XDA Premium App
Click to expand...
Click to collapse
Thanks... I am glad I could help. This way is the easiest I know of and I hope it will help alot of people to flash the new Radio's we have the EASY WAY.
TeeJay3800 said:
I'm trying to protect users from screwing up their phones and you accuse me of trolling? Give me a break.
YOU need to get your facts straight. The official radio thread uses the exact same method of flashing as your instructions (through hboot). The only difference is you omit the important step of verifying the MD5.
Sent from my HTC Vision using XDA Premium App
Click to expand...
Click to collapse
Go to another thread allready. Your negativity is not needed here. I am trying to HELP People With this thread. Read the OP it is updated for Users to Verify There MD5.
vabeach454 said:
Go to another thread allready. Your negativity is not needed here. I am trying to HELP People With this thread. Read the OP it is updated for Users to Verify There MD5.
Click to expand...
Click to collapse
I'm glad I was able to spare users from bricking their phones as per your original instructions.
AHHHH finally got the courage to do it. I'm now on 26.08.04.30, I'll do a bit of testing over a couple days and see how it goes.
I used a simple MD5 checker on my pc and then android file verifier on my phone, then did it. I notice that I'm getting 2 bars of H in my room, usually get weak 3g or edge.
kimbernator said:
AHHHH finally got the courage to do it. I'm now on 26.08.04.30, I'll do a bit of testing over a couple days and see how it goes.
I used a simple MD5 checker on my pc and then android file verifier on my phone, then did it. I notice that I'm getting 2 bars of H in my room, usually get weak 3g or edge.
Click to expand...
Click to collapse
Did you use this method? I am trying to show everyone ( New & Experienced ) how easy it really is. I am using the Newest Radio 26.09.04.26 and getting Full bars on H.
vabeach454 said:
Did you use this method? I am trying to show everyone ( New & Experienced ) how easy it really is. I am using the Newest Radio 26.09.04.26 and getting Full bars on H.
Click to expand...
Click to collapse
That's not a bad idea. I want you to know the only reason I said anything is because skipping the file integrity verification is a bad idea. There's nothing wrong with avoiding using ADB if you can accomplish the same thing with other methods, but I know people who have bricked their phones by flashing a radio from a file that was corrupt (they didn't check the MD5, one guy with an OG Droid and one with an Incredible). The guy who posted the original radio thread knows what he's talking about, that's why he included that very important step in his procedure. So all I was doing was pointing out what missing, and probably came across too harsh.
I wasn't trying to troll or start a flame war or anything. Just trying to help others in the same way as I've been helped over the years. As it stands now, your procedure is indeed easier and safe as well.
vabeach454 said:
Did you use this method? I am trying to show everyone ( New & Experienced ) how easy it really is. I am using the Newest Radio 26.09.04.26 and getting Full bars on H.
Click to expand...
Click to collapse
You can flaunt this method all you want, but it's really just the same as the ADB one, just no commands and a different form of checking the MD5. Not to detract from the fact that you made doing this much more understandable and a little less daunting which was very good of you to do. But in any case, yes. I used this method.
TeeJay3800 said:
That's not a bad idea. I want you to know the only reason I said anything is because skipping the file integrity verification is a bad idea. There's nothing wrong with avoiding using ADB if you can accomplish the same thing with other methods, but I know people who have bricked their phones by flashing a radio from a file that was corrupt (they didn't check the MD5, one guy with an OG Droid and one with an Incredible). The guy who posted the original radio thread knows what he's talking about, that's why he included that very important step in his procedure. So all I was doing was pointing out what missing, and probably came across too harsh.
I wasn't trying to troll or start a flame war or anything. Just trying to help others in the same way as I've been helped over the years. As it stands now, your procedure is indeed easier and safe as well.
Click to expand...
Click to collapse
Cool... I should have added it from the start because I do know better, but I was reminded to add to check MD5 Promptly. I am not trying to upstage anyone saying it's the only method, but IMHO is the most easy & fastest way I have seen. As you can see a couple of people have tried it and agree. I think we should all be able to get along in this thread as its is only an attempt at Helping people out. Mainly newer members. Peace...
Sent from my HTC GLACIER using XDA Premium App
I agree. There is a way to say things and a way to help people without being pompous and rude. Maybe post "important correction" instead of telling someone they're giving "horrible" advice in italics.
My sister have a Galaxy Player 50 with eclair...this PMP seems to be the same as the galaxy 3 (same resolution...and some other things) so can I flash lestatious or other rom on it ?
This hardware is not a phone...but maybe ?
Maybe I can try to flash...but if the pmp become soft bricked...it's over since i can't found an galaxy's 50 firmware...
Darius, I'm stuck with a brick galaxy player. I can try to flash with a galaxy 3 firmware if you want
Do you know how to make a dump of your device so you can share with me the original firmware?
http://forum.xda-developers.com/showthread.php?p=14493414
I don't know...but I'll try to find
Thanks!
I tried the firmware of galaxy 3, but didn't work
I dont think that its possible, first of all, despite being an android device, it doesnt have radio features, gsm 3g etc, only wifi, there are features that our phone does not support
Anyone found a solution for this yet? Not being able to test this device to it's full potential is really frustrating. Games are laggy and apps just do not run smooth on this one.
Has anyone tried z4root on this? I did and it freezes at "acquiring root shell".
@fedeff: how did you brick it?
Darius_AWS said:
My sister have a Galaxy Player 50 with eclair...this PMP seems to be the same as the galaxy 3 (same resolution...and some other things) so can I flash lestatious or other rom on it ?
This hardware is not a phone...but maybe ?
Maybe I can try to flash...but if the pmp become soft bricked...it's over since i can't found an galaxy's 50 firmware...
Click to expand...
Click to collapse
First root using One click root.
Give these commands in Terminal emulator
su
mount
Check for system partition.Suppose it is stlx (x=6,7,8 etc depending on system partition)
give this command to dump system...
dd if=/dev/block/stlx of=/sdcard/factoryfs.rfs
Copy it from sdcard and upload. I need to check it then i can help u out.
arunmcops said:
First root using One click root.
Give these commands in Terminal emulator
su
mount
Check for system partition.Suppose it is stlx (x=6,7,8 etc depending on system partition)
give this command to dump system...
dd if=/dev/block/stlx of=/sdcard/factoryfs.rfs
Copy it from sdcard and upload. I need to check it then i can help u out.
Click to expand...
Click to collapse
I'd gladly try it as long as Samsung gives me firmware, don't want to end up with a nice looking little brick here.
Is there any way that that an installer/firmware file could be saved in the device for backup purposes or something?
anon3524 said:
I'd gladly try it as long as Samsung gives me firmware, don't want to end up with a nice looking little brick here.
Is there any way that that an installer/firmware file could be saved in the device for backup purposes or something?
Click to expand...
Click to collapse
factoryfs.rfs is ur firmware backup....
@arunmcops: Thanks for the instructions. If someone try this and upload it'd be great for me.
@anon3524: I accidentally reseted the device to factory, trying to fix a problem with wifi (it suddenly stopped working one day).
arunmcops said:
factoryfs.rfs is ur firmware backup....
Click to expand...
Click to collapse
Ok, I am down to do this process you just explained as long as you or anyone explains to me how to recover the device with this "factoryfs.rfs" in case it gets bricked. You'd have to explain with detail how to grab this file and what to do with it etc. Also, if you could give further details on the initial process, that'd be great since a few things are unclear (to a brave noob like me).
Other than that, I am willing to try it to see the results.
BRING IT OON! *warface*
@arunmcops - I've got one of these, so have uploaded the file you wanted here - sorry, not allowed to post links yet:
dl.dropbox.com/u/6491656/Samsung/factoryfs.tar.gz (please don't flash this, its not a full rom)
I haven't made any changes to the base firmware other than renaming a couple of the phone.apk's to .old (cell standby was eating battery, and this device doesn't have a sim).
For fun, i've also uploaded a dmesg log
dl.dropbox.com/u/6491656/Samsung/dmesg.log
One other thing, i think the partition layout might be slightly different on this (might be wrong, don't have the phone) in that the internal sd card is mounted as /sdcard and the external one is /sdcard/sd.
Hope this helps!
Chris
@ctaylr Thanks for uploading the file.
I tried to load it using Odin, but it get stuck while uploading the file. The device is detected, but I think it's not transfering anything.
Is it possible to restore it form sd card?
fedeff said:
@ctaylr Thanks for uploading the file.
I tried to load it using Odin, but it get stuck while uploading the file. The device is detected, but I think it's not transfering anything.
Is it possible to restore it form sd card?
Click to expand...
Click to collapse
Hi...thats probably because it isn't intended as a flashable rom. Its just a dump of the stock firmware so that arunmcops asked to see to see if it had any resemblance of the galaxy 3 f/w, to see what we'd have to do to get a working custom ROM on this device..
Please don't attack it with any kind of Norse God ...especially until there is a confirmed route back to stock. All thats contained in the files is what you have on your device already - so there is also absolutely no point (for now).
If your having trouble with your device now, you could try doing a factory reset or playing about in Kies - i've fixed my device once after I got curious and flashed a custom ROM on here (which fyi completely messed it up - something like E:multi_csc: error: open /efs/imei/mps_code.dat because we dont have an IMEI code on this device) and then got it back working again - unfortunately i can't remember exactly what I did. Otherwise if this doesn't work I'll see if i can make a working stock package for Odin.
@ctaylr, yes I'm having problems with my device. It got soft bricked. I couldn't make it work using Kies. The only thing I can do is to start it in Download mode. If you can make a working package for oding that'd be great
This might help
http://forum.xda-developers.com/showpost.php?p=9515709&postcount=14
Thanks!
@fedeff Ok. i'll have a look over the weekend and see if i can make something that flashes.
Quick questions
1) do you have the 8gb or 16gb version?
2) have you tried going into recovery utils and doing a "wipe data/factory reset?" - you can do this by holding down home, volume down and volume up while turning the unit on - i seem to remember this fixed it for me, but it probably depends on how far Odin got while flashing. If your unit is already bricked, i can't see it doing much further harm
Thks
ctaylr said:
@fedeff Ok. i'll have a look over the weekend and see if i can make something that flashes.
Quick questions
1) do you have the 8gb or 16gb version?
2) have you tried going into recovery utils and doing a "wipe data/factory reset?" - you can do this by holding down home, volume down and volume up while turning the unit on - i seem to remember this fixed it for me, but it probably depends on how far Odin got while flashing. If your unit is already bricked, i can't see it doing much further harm
Thks
Click to expand...
Click to collapse
1) I have the 8gb version
2) By doing "wipe data/factory reset" is how I got it soft bricked. (the device wifi suddenly stopped working, and I thought that would help) After that it kept entering in the recovery mode. Then I tried to flash it with odin, now the only thing I can do is enter the download mode
Thanks again for helping me!
News?
Hi! I also like the others I am interested because my Galaxy player has 50 brick and I need someone to do dump the firmware so I can flash through odin! Please would you be my salvation and many other who have this player and would like to fix without waiting for the assistance of a month
Waiting for an answer I greet and thank all users who want to help me
sorry if English is not correct, but I'm using google translator (I'm Italian)
EDIT:
listen to me: http://forum.xda-developers.com/showthread.php?t=726673 This is the guide on how to get the dump of your fimrware if someone kindly did this process with its galaxy player 50 and then upload the file . tar obtained would help all
I don't think it is as simple as that.
If you fully read that topic above, it tells you. That will ONLY tarball the files in the /system folder. It doesn't dump the the bootloaders, efs or produce the initrd, which is also part of the firmware.
In fact that backup is exactly what i linked to earlier here, and doesn't flash properly through Odin. I don't know Odin very well (i use a ZTE Blade and clockworkmod normally ) but i'm going to take an educated guess it needs all of this information to successfully flash the player, and trying to flash without all of that probably won't work so well.
If i'm wrong, please let me know and i'll do what i can to help.
ctaylr said:
I don't think it is as simple as that.
If you fully read that topic above, it tells you. That will ONLY tarball the files in the /system folder. It doesn't dump the the bootloaders, efs or produce the initrd, which is also part of the firmware.
In fact that backup is exactly what i linked to earlier here, and doesn't flash properly through Odin. I don't know Odin very well (i use a ZTE Blade and clockworkmod normally ) but i'm going to take an educated guess it needs all of this information to successfully flash the player, and trying to flash without all of that probably won't work so well.
If i'm wrong, please let me know and i'll do what i can to help.
Click to expand...
Click to collapse
ok then I'm sorry I read the topic in a hurry and did not realize that you can not do what I say but re-reading now I understand!
ctaylr what do you advise me to do then? wanted to try an get into recovery and restore but I think the 3 keys are disabled enters only download ..
Google traductor sorry
A day or two ago I unlocked my ChaCha using the HTCDev.com instructions. I then used DooMLoRD_v4_ROOT-zergRush-busybox-su to root it. Everything was going fine until I apparently deleted one too many system apps and now my phone is in extremis.
The problem: As the phone boots up and reaches the HTC logo screen, just when the main interface should appear, an error pops up. It says:
Code:
Sorry!
The process com.htc.bg has stopped unexpectedly. Please try again.
[Force close]
When I close it, the HTC logo appears again as the main GUI is reinitialised, which leads to the same error popping up again, thus entering into an infinite loop.
I can just about manage to connect the phone to my PC as a disk drive, but it's not connected in such a way that RUU or unrooting applications can "find" it from within Windows, so if I'm to fix this it's gotta be from the SD card/Hboot.
Details:
* HTC ChaCha with the latest Android firmware.
* Unlocked and rooted, but remains S-ON (Superuser was installed and worked).
* Used Titanium to delete apps, but made backups and have them on my hard drive for safe keeping but can't access the phone in order to restore them properly.
* I was unable to restore backed-up system apps prior to this critical problem emerging, which I think is because my phone isn't "truly" rooted. I can apparently remove from but not add to the protected areas of the phone.
* I've tried flashing the device with numerous recovery ROMs and they all fail (wrong image, etc.). I'm having an extremely difficult time finding the original ROM anywhere and more importantly finding one which will work without the phone being connected to the PC at any stage of the flashing job.
* Factory resets and recovery boots don't seem to have any effect.
* It's a carrier-locked/branded phone, from Three/Hutchison 3G UK. I'm locked into my contract for another year at least.
* Before I rebooted the phone for the last time [prior to the beginning of the above problem] I noticed that my ringtones and related media were all gone and I was unable to download new ones even using third-party apps; the "unable to download sound" error was constantly popping up and when I received messages or phone calls the phone would vibrate but wouldn't play any tones.
* My brother and I spent the better part of 6 hours scouring the net and trying every combination of steps we could think of to try and resolve this. I wouldn't have posted here if I wasn't at the end of my tether and if I hadn't tried every solution I could find from others on various forums including this one, nor would I be so quick to reveal myself to be a deletion-happy moron to a forum of experts (I saw that anti-noob YouTube clip!).
Is there any hope of fixing this issue given my obvious lack of critical faculties?
Thank you for reading this.
You can always install clockworkmod recovery and from there a custom rom. Check the relevant thread, it is pinned.
OK,
don't panic. I almost thought you'd hard bricked your phone when modifying the NAND. This is a soft brick and ALL soft bricks can be recovered, they just take a bit of pain and suffering. Sometimes more suffering than others, but that's irrelevant.
Question, you say you can't restore system apps? How did you try? If a phone is perm rooted, it's rooted. Obviously a temp root is different to a perm root, but I believe this is a perm root as you can REMOVE apps from the system memory. If a root wasn't perm, every app would be sandboxed so no app, including titaniumbackup would work.
* Unlocked and rooted, but remains S-ON (Superuser was installed and worked).
Click to expand...
Click to collapse
S-ON is part of HTC's snap on BL protection. The fact your phone is S-ON is now not that important, the BL is unlocked, thats what matters.
* Used Titanium to delete apps, but made backups and have them on my hard drive for safe keeping but can't access the phone in order to restore them properly.
Click to expand...
Click to collapse
Ok, important advice here (for future ref), you shouldn't go mad with deleting unless you've tried freezing first. Freezing allows you to recover by simply doing a factory reset. Most bootloaders (including HTC's) allow you to perform an emergency factory reset from there. You might lose all the **** on there, but you will have a working phone. You also need to be careful with TitaniumBackup, I'm sure you didn't remove the obvious important ones, but the fact you lost access to your audio means you removed a sound/media package. Next time, google "HTC chacha, safe to remove" as more people root this phone in the next few weeks, safe to remove lists will appear. For SGS (my phone) there is a whole shared google doc with a list of system apps, and the consequence of removing them.
* I was unable to restore backed-up system apps prior to this critical problem emerging, which I think is because my phone isn't "truly" rooted. I can apparently remove from but not add to the protected areas of the phone.
Click to expand...
Click to collapse
You can't restore a system app if there is a conflict. Try and identify the conflict.
* I've tried flashing the device with numerous recovery ROMs and they all fail (wrong image, etc.). I'm having an extremely difficult time finding the original ROM anywhere and more importantly finding one which will work without the phone being connected to the PC at any stage of the flashing job.
Click to expand...
Click to collapse
By the sounds of it, you are using ROMs designed for CWM. If you are going to do that, flash CWM first. There are shed loads of tutorials. If you want to install the stock rom all over again, just download the stock RUU.
* Factory resets and recovery boots don't seem to have any effect.
Click to expand...
Click to collapse
See above about freezing.
* It's a carrier-locked/branded phone, from Three/Hutchison 3G UK. I'm locked into my contract for another year at least.
Click to expand...
Click to collapse
Doesn't matter, you'll fix it, guarantee it.
* Before I rebooted the phone for the last time [prior to the beginning of the above problem] I noticed that my ringtones and related media were all gone and I was unable to download new ones even using third-party apps; the "unable to download sound" error was constantly popping up and when I received messages or phone calls the phone would vibrate but wouldn't play any tones.
Click to expand...
Click to collapse
See what I said above.
* My brother and I spent the better part of 6 hours scouring the net and trying every combination of steps we could think of to try and resolve this. I wouldn't have posted here if I wasn't at the end of my tether and if I hadn't tried every solution I could find from others on various forums including this one, nor would I be so quick to reveal myself to be a deletion-happy moron to a forum of experts (I saw that anti-noob YouTube clip!).
Click to expand...
Click to collapse
Have you tried every combination of steps? You've clearly not tried CWM. I'm not suggesting that as a silver bullet (personally, I try to avoid CWM if I can) but it's the best way to give you low level access to the NAND so you could easily flash an OTA ROM, modded ROM or even return it to stock dead quick.
For a safe to remove list, check the Themes and Apps section.
skezza said:
OK,
don't panic. I almost thought you'd hard bricked your phone when modifying the NAND. This is a soft brick and ALL soft bricks can be recovered, they just take a bit of pain and suffering. Sometimes more suffering than others, but that's irrelevant.
Click to expand...
Click to collapse
Music to my ears!
skezza said:
Question, you say you can't restore system apps? How did you try? If a phone is perm rooted, it's rooted. Obviously a temp root is different to a perm root, but I believe this is a perm root as you can REMOVE apps from the system memory. If a root wasn't perm, every app would be sandboxed so no app, including titaniumbackup would work.
Click to expand...
Click to collapse
In Titanium Backup I tried restoring the backups I made; the "Recovering Backup" notice would just hang indefinitely until I forced TB to close. This only happened with system apps. The backed up files are still on my PC hard drive from when I copied them from my SD card, but I'm not sure they're of any use at this stage.
skezza said:
S-ON is part of HTC's snap on BL protection. The fact your phone is S-ON is now not that important, the BL is unlocked, thats what matters.
Click to expand...
Click to collapse
Ahhh, this is probably my problem then. I ignored most of the fixes and workarounds listed as [S-OFF] because I didn't think they'd work for my device haha.
skezza said:
Ok, important advice here (for future ref), you shouldn't go mad with deleting unless you've tried freezing first. Freezing allows you to recover by simply doing a factory reset. Most bootloaders (including HTC's) allow you to perform an emergency factory reset from there. You might lose all the **** on there, but you will have a working phone. You also need to be careful with TitaniumBackup, I'm sure you didn't remove the obvious important ones, but the fact you lost access to your audio means you removed a sound/media package. Next time, google "HTC chacha, safe to remove" as more people root this phone in the next few weeks, safe to remove lists will appear. For SGS (my phone) there is a whole shared google doc with a list of system apps, and the consequence of removing them.
Click to expand...
Click to collapse
I'm disappointed in myself for being so haphazard in my deleting, I'm usually not that stupid but I think I was a little overexcited to have finally gotten rid of some of the bloatware that'd irritated me for so long haha. I was like "oh boy, I can save even more battery power and internal space if I just remove a little more!". Lesson learnt
skezza said:
By the sounds of it, you are using ROMs designed for CWM. If you are going to do that, flash CWM first. There are shed loads of tutorials. If you want to install the stock rom all over again, just download the stock RUU.
...
Have you tried every combination of steps? You've clearly not tried CWM. I'm not suggesting that as a silver bullet (personally, I try to avoid CWM if I can) but it's the best way to give you low level access to the NAND so you could easily flash an OTA ROM, modded ROM or even return it to stock dead quick.
Click to expand...
Click to collapse
As I said above I didn't realise I could make use of [S-OFF] materials so I didn't even attempt them for fear of making matters worse. I just now attempted to flash CWM and it hung on "parsing" which is what happened with previous flash attempts. If a flash attempt doesn't hang on "parsing" it parses for a second and then goes back to the main menu, apparently having no effect.
I'd be lying if I said I'm not overwhelmed by all of this; the tutorials I've read seem to assume a fair degree of prior knowledge that I definitely don't have haha. I hope I don't stretch anyone's patience here, but if you could explain it to me like a 6-year-old whose mother drank heavily during pregnancy I think it will help move things along!
Thank you for the thorough reply, much appreciated
Follow this to flash CWM, you need to do it with your computer and using fastboot, this is needed for S-ON phones.
http://forum.xda-developers.com/showthread.php?t=1449681
dapaua said:
Follow this to flash CWM, you need to do it with your computer and using fastboot, this is needed for S-ON phones.
http://forum.xda-developers.com/showthread.php?t=1449681
Click to expand...
Click to collapse
Unfortunately I can't do anything via my computer; my phone isn't "discovered" by the command line, unrooting tools or anything else. It does allow me to access the SD card as a hard drive but that's all it does. Obviously this wasn't the case before my problems started, because I used my PC to root and unlock the phone originally, but now the phone's boot process can't reach a point where it becomes receptive to the PC's commands. I don't know why it lets me access the SD card though.
Is there any way to do this without my PC being involved beyond transferring files to the SD card? If not, am I screwed? haha
Thanks mate!
Can you boot into the bootloader (Whith the phone off, press Volume down + power for five seconds)?
Then boot into it, move up with the volume keys and then choose fastboot.
Then follow the procedures in the link I posted previously http://forum.xda-developers.com/showthread.php?t=1449681 (start from step 3). Fastboot mode should be recognized.
The fastboot binary is here C:\Program Files (x86)\Android\android-sdk\tools , if you installed the android SDK, which I asume you did.
Good luck, I hope this works!
dapaua said:
Can you boot into the bootloader (Whith the phone off, press Volume down + power for five seconds)?
Then boot into it, move up with the volume keys and then choose fastboot.
Then follow the procedures in the link I posted previously http://forum.xda-developers.com/showthread.php?t=1449681 (start from step 3). Fastboot mode should be recognized.
Click to expand...
Click to collapse
Dear CHRIST thank you for that - I didn't know about this feature, and it worked! I was able to connect to my PC and do everything I needed to. I used the command line to flash the CWM, then followed instructions for partitioning the SD card and installing a custom ROM. I feel like a real [email protected] I wonder if Anonymous are looking for any new recruits...
dapaua said:
Good luck, I hope this works!
Click to expand...
Click to collapse
It did - I'm back in business!! Thank you mate, if I could fellate you via WiFi I probably would. You'd have to be wearing some anti-virus trousers though, I'm not a slut.
Cheers!
PaddyM said:
Dear CHRIST thank you for that - I didn't...
Click to expand...
Click to collapse
Great news (I thought you already knew about the recovery menu feature otherwise I'd have mentioned it).
As I said in my reply earlier, every soft brick can be fixed somehow. Some are just harder than others. If I'm honest, it seems like yours was pretty straightforward once you got into the Recovery menu.
By the way, if you decide you want to return to stock, you can do that quite easily. Also, if I was you, do the freezing technique I suggested earlier and use the safe list that's available.
If you keep CWM, do a Nandroid backup. You don't have to keep it on your SD, but they are great for doing a very fast recovery. I can usually restore my phone in about 10 - 15 minutes using Nandroid.
PaddyM said:
Dear CHRIST thank you for that - I didn't know about this feature, and it worked! I was able to connect to my PC and do everything I needed to. I used the command line to flash the CWM, then followed instructions for partitioning the SD card and installing a custom ROM. I feel like a real [email protected] I wonder if Anonymous are looking for any new recruits...
It did - I'm back in business!! Thank you mate, if I could fellate you via WiFi I probably would. You'd have to be wearing some anti-virus trousers though, I'm not a slut.
Cheers!
Click to expand...
Click to collapse
I'm happy it worked. Let's hope WiFi technology improves in the future
skezza said:
Great news (I thought you already knew about the recovery menu feature otherwise I'd have mentioned it).
Click to expand...
Click to collapse
I knew about the recovery menu (the stock one, at least) but I didn't realise I could go into the Fastboot option and for the phone to then be recognisable to the PC, thus making it possible to flash via the command line. If I had known that I probably wouldn't have needed to post this thread at all haha.
skezza said:
As I said in my reply earlier, every soft brick can be fixed somehow. Some are just harder than others. If I'm honest, it seems like yours was pretty straightforward once you got into the Recovery menu.
Click to expand...
Click to collapse
Yeah... I think if it happened to one of you guys you probably would have had it sorted in about 6 minutes. 3 days isn't bad for my first attempt though! hahaha
skezza said:
By the way, if you decide you want to return to stock, you can do that quite easily. Also, if I was you, do the freezing technique I suggested earlier and use the safe list that's available.
If you keep CWM, do a Nandroid backup. You don't have to keep it on your SD, but they are great for doing a very fast recovery. I can usually restore my phone in about 10 - 15 minutes using Nandroid.
Click to expand...
Click to collapse
Thanks for the advice man, I'll definitely be looking into the Nandroid backup option, although I hope I've learnt enough from this experience to have no need for it
Thanks to everyone who posted here, I appreciate the patience and the tolerance of my noobery.
Funnily enough, I tried TitaniumBackup today and the original poster is correct. While you can freeze, remove apps etc, you can't return them. especially system. I've not tried any of the alternative install methods that TB uses, but it's quite interesting.
TB is a bit quirky, I think. The system apps won't restore at all, but sometimes apps that I've downloaded myself will restore and other times they won't (the "Restoring App" notice just hangs there indefinitely). I usually find that forcing TB to close and then trying again does the trick, but I can't figure out why it happens in the first place.
Im wondering if anyone else has worked out a good configuration that will allow it to work every time?
Hey everyone,
Recently I came across an interesting thread in the SGS3 forums that there is a command for ADB and terminal emulator that resets the flash counter of a device. I was thinking, and correct me if I'm wrong, that the partitions of our phones must be very similar. I ran the commands in terminal emulator with no issues at all, but I'm not sure if it reset my flash counter. I am showing that I have no custom binary and I'm running Samsung official firmware when I boot into download mode. I am also running CM9 flashed from recovery. So, while my device shows that this possibly worked, I don't know if it is just me or not.
What I am asking is if I could have someone or a couple of people with a flash counter greater than 0 on the custom binary counter, under the impression that this could potentially be DEVASTATINGLY DANGEROUS to their device and may brick it, to run terminal emulator with the following command:
su
echo -n '\x00' | dd obs=1 count=1 seek=4193796 of=/dev/block/mmcblk0
The "\x00" is what you want the flash counter to read.
The post that gave me this idea are below. I really have no idea if it works, but maybe it does. I don't know much about how our devices are partitioned in comparison to the SGS3. I would highly suggest that those of you using MTD do not try this.
All this being said I am not responsible for bricking your device or causing any damage to it. Please try this at your own risk. I did, and I had no issues at all, but that doesn't mean you won't. This is strictly theoretical and potentially very dangerous.
Thanks to: enderblue and AdamOutler
Lastly, if this doesn't work, does anyone have any ideas on how we can figure out how to make it work for our device?
Thanks to all who can help out!
Original thread that gave me the idea: http://forum.xda-developers.com/showthread.php?t=1781471
Sorry, but you don't want to do this. The SGS3 is set up differently than the Infuse. mmcblk0 is the location of the pit partition on the SGS3. The Infuse uses bml partitions. Totally different setup, so you don't want to use dd to write those bits to a random partition.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
stratatak7 said:
Hey everyone,
Recently I came across an interesting thread in the SGS3 forums that there is a command for ADB and terminal emulator that resets the flash counter of a device. I was thinking, and correct me if I'm wrong, that the partitions of our phones must be very similar. I ran the commands in terminal emulator with no issues at all, but I'm not sure if it reset my flash counter. I am showing that I have no custom binary and I'm running Samsung official firmware when I boot into download mode. I am also running CM9 flashed from recovery. So, while my device shows that this possibly worked, I don't know if it is just me or not.
What I am asking is if I could have someone or a couple of people with a flash counter greater than 0 on the custom binary counter, under the impression that this could potentially be DEVASTATINGLY DANGEROUS to their device and may brick it, to run terminal emulator with the following command:
su
echo -n '\x00' | dd obs=1 count=1 seek=4193796 of=/dev/block/mmcblk0
The "\x00" is what you want the flash counter to read.
The post that gave me this idea are below. I really have no idea if it works, but maybe it does. I don't know much about how our devices are partitioned in comparison to the SGS3. I would highly suggest that those of you using MTD do not try this.
All this being said I am not responsible for bricking your device or causing any damage to it. Please try this at your own risk. I did, and I had no issues at all, but that doesn't mean you won't. This is strictly theoretical and potentially very dangerous.
Thanks to: enderblue and AdamOutler
Lastly, if this doesn't work, does anyone have any ideas on how we can figure out how to make it work for our device?
Thanks to all who can help out!
Original thread that gave me the idea: http://forum.xda-developers.com/showthread.php?t=1781471
Click to expand...
Click to collapse
Not sure if it really matters, the easiest way is just plug in jig. It works on my phone
qkster said:
Not sure if it really matters, the easiest way is just plug in jig. It works on my phone
Click to expand...
Click to collapse
This, and flashing an Odin unbrick package with pit partitioning will reset the counter on the Infuse.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Chainfire has an app to reset the counter - he is very specific in his OP that it only works on the International GT I9300, SGS3. ( I have it on my GT I9300 and it works great.) I have seen other threads, mostly for GT I9300 roms where a few have flashed them on US SGS3 versions and their phones are bricked. With all due respect, the SGS3 is not an upgraded Infuse therefore as Jscott30 and qkster stated above, not a good idea to play with fire. I may have missed it, but I do not recall a thread where not resetting the counter on the Infuse was a major issue.
Pony Express said:
Chainfire has an app to reset the counter - he is very specific in his OP that it only works on the International GT I9300, SGS3. ( I have it on my GT I9300 and it works great.) I have seen other threads, mostly for GT I9300 roms where a few have flashed them on US SGS3 versions and their phones are bricked. With all due respect, the SGS3 is not an upgraded Infuse therefore as Jscott30 and qkster stated above, not a good idea to play with fire. I may have missed it, but I do not recall a thread where not resetting the counter on the Infuse was a major issue.
Click to expand...
Click to collapse
Chainfire's Triangle Away app has been updated and now works for the AT&T SGS3 also. But like Pony Express said, this method isn't for the Infuse, just as the SGS3 dd method isn't for the Infuse.
Sent from my SAMSUNG-SGH-I747 using Tapatalk 2
Thanks so much for your replies. I knew this was a long shot but I figured what the hell. I was hoping we could have similar results on our device by figuring out the correct partition sizes and find the right command for our device.
I'm very familiar with the jig and Odin methods, but I was hoping there was a way to implement a similar method on the infuse.
I don't know, is this a lost cause? I think it's a really great and easy method.
I saw another one that flashed CWM over 256 times (256 is the max the flash counter goes before going back to 0) but something about that makes me really leary.
I'd really like to figure this out if it's even possible. If not, I'll just have this thread closed and keep my mouth shut from now on.
Sent from my SGH-I997 using xda app-developers app
Imo, asking new questions is a good thing for all- give others more time to view and hopefully reply.
stratatak7 said:
Thanks so much for your replies. I knew this was a long shot but I figured what the hell. I was hoping we could have similar results on our device by figuring out the correct partition sizes and find the right command for our device.
I'm very familiar with the jig and Odin methods, but I was hoping there was a way to implement a similar method on the infuse.
I don't know, is this a lost cause? I think it's a really great and easy method.
I saw another one that flashed CWM over 256 times (256 is the max the flash counter goes before going back to 0) but something about that makes me really leary.
I'd really like to figure this out if it's even possible. If not, I'll just have this thread closed and keep my mouth shut from now on.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
it is quite possible that a dd command will work but it wont be the same one. what dd does is write on a binary level, it can make system images that you can flash in odin/heimdall, do a true delete (overwrite with either random bits or all zeros to make recovery of files imposible, (hint, if you do anything ilegal) the images are exact binary copies of the partition not just a file containing the contents, so it has all the deleted data, timestamps, metadata, etc... you can even do a search and replace of your whole file system that can't be detected if you say want to remove all record of something since unlike a text editor there wont be any log of changes or possibility of a temporary backup file that has a small chance of being recovered.
what you would have to do is dump a few copies of the partition that contains param.ifs with the counter at various numbers and look for the hex code that correlates to that number in a hex editor, find the position of that hex number and work out the details for the dd command.
the easy way is to just reflash param.ifs from a froyo package(i think that's what does it anyway). the sgs 3 keep the data somewhere else or has a way to keep it from being reset easily with odin.
oh yeah and messing up the device path and accidentally writing into a bootloader could hardbrick the phone, writing to the wrong block could brick it as well but is likely to only softbrick it.
Dani897 said:
it is quite possible that a dd command will work but it wont be the same one. what dd does is write on a binary level, it can make system images that you can flash in odin/heimdall, do a true delete (overwrite with either random bits or all zeros to make recovery of files imposible, (hint, if you do anything ilegal) the images are exact binary copies of the partition not just a file containing the contents, so it has all the deleted data, timestamps, metadata, etc... you can even do a search and replace of your whole file system that can't be detected if you say want to remove all record of something since unlike a text editor there wont be any log of changes or possibility of a temporary backup file that has a small chance of being recovered.
what you would have to do is dump a few copies of the partition that contains param.ifs with the counter at various numbers and look for the hex code that correlates to that number in a hex editor, find the position of that hex number and work out the details for the dd command.
the easy way is to just reflash param.ifs from a froyo package(i think that's what does it anyway). the sgs 3 keep the data somewhere else or has a way to keep it from being reset easily with odin.
oh yeah and messing up the device path and accidentally writing into a bootloader could hardbrick the phone, writing to the wrong block could brick it as well but is likely to only softbrick it.
Click to expand...
Click to collapse
Wow that's great information. Thanks so much. I would really like to try that. Can anyone help me get started?
Guys I'm learning how to do everything one step at a time. Is there anyone that would be willing to help me out? I've never dived into android development or messed with the file system before but I think it's time for me to start learning. I certainly have the hardware for it. I'm just tired of sitting around and watching instead of doing. I've had the infuse since its release last year on day one. It's been the best phone I've ever had because of all of you. Let's keep making it better and count me in.
Sent from my SGH-I997 using xda app-developers app
stratatak7 said:
Wow that's great information. Thanks so much. I would really like to try that. Can anyone help me get started?
Guys I'm learning how to do everything one step at a time. Is there anyone that would be willing to help me out? I've never dived into android development or messed with the file system before but I think it's time for me to start learning. I certainly have the hardware for it. I'm just tired of sitting around and watching instead of doing. I've had the infuse since its release last year on day one. It's been the best phone I've ever had because of all of you. Let's keep making it better and count me in.
Sent from my SGH-I997 using xda app-developers app
Click to expand...
Click to collapse
i've never done anything like this, just kinda understand the concept, i might be missing some important stuff and would need to read up on the options available in dd to make sure i understand how to tell it to write where you want it to. i dunno, maybe i could take a stab at it but i can't say i'm an expert.
Dani897 said:
i've never done anything like this, just kinda understand the concept, i might be missing some important stuff and would need to read up on the options available in dd to make sure i understand how to tell it to write where you want it to. i dunno, maybe i could take a stab at it but i can't say i'm an expert.
Click to expand...
Click to collapse
As far as I'm concerned, any help is good help. That would be so great of you. I'll see if I can PM the OP whose idea this was on the SGS3 and see if he can give his two cents too. Maybe Adam as well
Ty Guys.
This software worked perfectly with my Asus Transformer TF101 B70 - IML74K.WW_epad-9.2.1.27-20120615.
It was bricked because clockworkmod no read my MicroSD Card.
Besides all the problems I inadvertently deleted all my data using clockworkmod, result, only the left clockworkmod no more walks beyond the internal memory without OS.
Now ty guys, after 15 days I am happy again.
Ty XDA Developers, Ty EasyFlash.
How to donate?
NINJUTSU said:
This software worked perfectly with my Asus Transformer TF101 B70 - IML74K.WW_epad-9.2.1.27-20120615.
It was bricked because clockworkmod no read my MicroSD Card.
Besides all the problems I inadvertently deleted all my data using clockworkmod, result, only the left clockworkmod no more walks beyond the internal memory without OS.
Now ty guys, after 15 days I am happy again.
Ty XDA Developers, Ty EasyFlash.
How to donate?
Click to expand...
Click to collapse
Congrats on getting your prob fixed...
But...I'm confused how this fixed your phone...isn't only supposed to reset flash counter?
Can you please explain what you did...I'm curious...(btw never ran or even downloaded this tool...but if it cam be used to help unbrick phones then its worth looking into...)
Edit...just realized this is all done from terminal...no download neccessary...
Sent from my HTC PH39100 using Tapatalk 2
Hello! I apologize in advance for my lack of knowledge.
First of all here is my phone info
Rooted RAZR maxx hd with unlocked bootloader (XT926)
My main objective is to flash custom ROMs and see if any are better and faster than stock.
My problem is I have no idea what I'm doing. I can't seem to find any threads that are simple enough for me to understand what I need to do and in what order I need to do those things.
Supposedly I need to back up my phone which seems to be the same thing as having a recovery???
If there is a thread that simplifies backing up and using a custom recovery please post a link.
I don't understand how to back up my phone, or if I use my computer or phone to do said back up.
I don't understand how to use the app ROM manager, my phone isn't listed on it when I try to download clockworkmod. So I downloaded a file cwm.img and I don't know what the heck to do with it?
I think I have adb on my computer?
I'm so confused and there's too much information and it makes no sense to me. Can someone please help me or post links to SIMPLE walk throughs of what I need to do and tell me what order I'm supposed to do them in?
I'm sorry if you think I haven't searched because I've been searching for a long time over a few days and all I've found is information that is too complex for me.
I appreciate any help! I'm new and I don't want to hurt my phone.
boost4life17 said:
Hello! I apologize in advance for my lack of knowledge.
Click to expand...
Click to collapse
First of all here is my phone info
Rooted RAZR maxx hd with unlocked bootloader (XT926)
Mine is a Razr HD (XT925) But it's mainly the same except roms and some tools (and probably some other things I don't know...)
My main objective is to flash custom ROMs and see if any are better and faster than stock.
Which is the idea I had a week ago
My problem is I have no idea what I'm doing.
I was exactly in the same position since this is my first smartphone ever ^^
I can't seem to find any threads that are simple enough for me to understand what I need to do and in what order I need to do those things.
Well I had to search a while cause I first of all wanted to backup the most I could before doing anything.
Supposedly I need to back up my phone which seems to be the same thing as having a recovery???
This is a good thinking But there are limitations on what you can do without making the first thing which is rooting your phone "and then unlocking it".
If there is a thread that simplifies backing up and using a custom recovery please post a link.
I don't understand how to back up my phone, or if I use my computer or phone to do said back up.
The first thing I could do, was to backup the Apps/Contacts/etc... by using some apps like : MyBackup
The thing is : these applications are limited until you are rooted, because you wont be able to save apps data like your game scores or whatever
The second way to backup, is to make an entire backup of your system and data, which can only be made after unlocking the bootloader (by installing a custom recovery).
Be careful, unlocking your bootloader will ENTIRELY WIPE the data you have so make backups BEFORE.
I don't understand how to use the app ROM manager, my phone isn't listed on it when I try to download clockworkmod. So I downloaded a file cwm.img and I don't know what the heck to do with it?
Not sure about it because I never got that app before unlocking my bootloader.
I think I have adb on my computer?
To get adb on your computer, you need Android-SDK.
I'm so confused and there's too much information and it makes no sense to me. Can someone please help me or post links to SIMPLE walk throughs of what I need to do and tell me what order I'm supposed to do them in?
If you need more infos, dont hesitate to ask me on your post Ill subscribe to it in case of
I'm sorry if you think I haven't searched because I've been searching for a long time over a few days and all I've found is information that is too complex for me.
I can understand, personnaly im working in IT and I understand how this can be a pain when you have no knowledge at all on that subject :/
I appreciate any help! I'm new and I don't want to hurt my phone.
Once again, good thinking, but even thought, going where you are going is very risked.
And I can tell...because I nearly bricked my phone...as you can see here : http://forum.xda-developers.com/showthread.php?t=2631547
boost4life17 said:
Hello! I apologize in advance for my lack of knowledge.
First of all here is my phone info
Rooted RAZR maxx hd with unlocked bootloader (XT926)
My main objective is to flash custom ROMs and see if any are better and faster than stock.
My problem is I have no idea what I'm doing. I can't seem to find any threads that are simple enough for me to understand what I need to do and in what order I need to do those things.
Supposedly I need to back up my phone which seems to be the same thing as having a recovery???
If there is a thread that simplifies backing up and using a custom recovery please post a link.
I don't understand how to back up my phone, or if I use my computer or phone to do said back up.
I don't understand how to use the app ROM manager, my phone isn't listed on it when I try to download clockworkmod. So I downloaded a file cwm.img and I don't know what the heck to do with it?
I think I have adb on my computer?
I'm so confused and there's too much information and it makes no sense to me. Can someone please help me or post links to SIMPLE walk throughs of what I need to do and tell me what order I'm supposed to do them in?
I'm sorry if you think I haven't searched because I've been searching for a long time over a few days and all I've found is information that is too complex for me.
I appreciate any help! I'm new and I don't want to hurt my phone.
Click to expand...
Click to collapse
Start
Use Recovery Tools from play to flash your fav img.
TWRP check my Problems post in HD gen. Pocket proof, easy
Not pocket proof:
CWMR be careful of the double touch conformation!-you can use the keys til you are versed w/ the input flukes that inspired Philz recovery. Otherwise solid & simple.
I use Philz which may support everything in Rom Manager soon.
RM works w/ Photon Q recovery works on all the msm8960 phones, xt907, 925, 926, mb886. keys only.
All recoveries
Just because you can format it, it still may not be supported in the backup or even the xml restore (/persist)
edit
Get a SANDISK 64 GB CARD, FORMAT FROM RECOVERY to default format-fat32. Then when in doubt BACKUP.
All for now
bye
No offense intended, but if it's too difficult for you, than you probably shouldn't touch the phone until you understand everything. Before you start modding, you need to know how to recover it so we don't have another brick. Once you start to understand the minor things, it will be like a light switch and the more complex things will start to make sense.
Hybris95 said:
First of all ..
Click to expand...
Click to collapse
Be careful, unlocking your bootloader will ENTIRELY WIPE the data you have so make backups
>>>>
This only happens on a moto factory UL.
Not the one for the xt907, 926 & mb886.
I do believe a 925 can save themselves the bother of the factory path if they do not mind it being not reversible. Yet both are irreversibly noticeable.
aviwdoowks said:
Be careful, unlocking your bootloader will ENTIRELY WIPE the data you have so make backups
>>>>
This only happens on a moto factory UL.
Not the one for the xt907, 926 & mb886.
Click to expand...
Click to collapse
Sorry about that I thought XT926 were close enough from XT925 (which is the only device I own) to have the same unlocking process.
My bad ^^
well if you're already unlocked and rooted, use this
http://wiki.cyanogenmod.org/w/Install_CM_for_xt925
follow the instructions, go to the development forum, download TWRP, CWM whichever floats your boat, and just use adb and fastboot.
id reccomend a backup, nandroid, titianium, etc.
djvita said:
well if you're already unlocked and rooted, use this
http://wiki.cyanogenmod.org/w/Install_CM_for_xt925
follow the instructions, go to the development forum, download TWRP, CWM whichever floats your boat, and just use adb and fastboot.
id reccomend a backup, nandroid, titianium, etc.
Click to expand...
Click to collapse
Is post # 5 true for you & your 925 unlock?
Thanks
RikRong said:
No offense intended, but if it's too difficult for you, than you probably shouldn't touch the phone until you understand everything. Before you start modding, you need to know how to recover it so we don't have another brick. Once you start to understand the minor things, it will be like a light switch and the more complex things will start to make sense.
Click to expand...
Click to collapse
This is an excellent point. When I first got into this a couple of years ago, I soft bricked my Bionic. I was able to recover it, but I could have avoided the problem if I had read a little more first. Now I read, read, read before trying something new. I found YouTube videos very helpful when I was a noob. Rootjunky is one resource, online and on YouTube. rootjunky.com
Sent from my Nexus 7 using xda app-developers app
aviwdoowks said:
Is post # 5 true for you & your 925 unlock?
Thanks
Click to expand...
Click to collapse
yes i supposedly backed up with cwm, but the last time i got in that option, it did not find that backup.
at least there is a firmware superthread, but my cwm is for 4.4 only, so id have to flash another cwm to go back to stock jb
i find a titanium backup to be better, just backup my sms/calls, wifi keys, and user apps...
RikRong said:
No offense intended, but if it's too difficult for you, than you probably shouldn't touch the phone until you understand everything. Before you start modding, you need to know how to recover it so we don't have another brick. Once you start to understand the minor things, it will be like a light switch and the more complex things will start to make sense.
Click to expand...
Click to collapse
No offense taken! I appreciate the constructive criticism. That is why I posted this question. I am reading all I can and I won't be attempting anything more until I understand the concepts. I just didn't know where to go for a more simple explanation of these concepts since apparently I'm not as intelligent as 90% of you guys on this forum!
I have already rooted and unlocked my phone so that's a good start haha. I will now follow the advice given in this thread and hopefully learn enough to understand these more complex concepts!
I appreciate everyone's information and responses!
Thanks ya'll
Jess
Good to hear you've placed these flammers where they have to be ^^
Anyway Nice job on what is done, the hardest and risky is still to come :/
Envoyé de mon XT925 en utilisant Tapatalk
its easy, the scripts i used are noob friendly, most important part is to backup your info!
djvita said:
yes i supposedly backed up with cwm, but the last time i got in that option, it did not find that backup.
at least there is a firmware superthread, but my cwm is for 4.4 only, so id have to flash another cwm to go back to stock jb
i find a titanium backup to be better, just backup my sms/calls, wifi keys, and user apps...
Click to expand...
Click to collapse
???
Cwm=Cwmr?
Recovery is made for phone not any particular rom.
I'm glad you didn't take offense. Just keep learning, you are off to a good start.
Sent from my Droid RAZR MAXX HD using xda app-developers app