Hi guys, I need some help here. I'm not new to this at all and have rooted TONS of phones for people and myself. Something strange just happened though. I was attempting to flash a ROM (specifically Energy HD 2.0) through CWM. The flash was unsuccessful, which happens at times, so I thought "no big deal, I'll just do a quick restore and try again or try a different one". I chose the backup I wanted to restore to, it did the restore, it said it completed successfully, so I chose reboot. When I looked at it again I realized I never saw the boot animation or anything so I checked it.....dead. The phone wouldn't boot, wouldn't go into recovery, nothing. I've pulled the battery several times, tried both the stock recovery and CWM and I get nothing but a black screened brick. I don't even get the Samsung logo. I have no idea what I could have done here. I attempted the method in this thread - http://forum.xda-developers.com/showthread.php?t=1840030. The only problem there is that I can't even get my device to go to downloading mode. I literally does nothing at all. When I connect to the PC, I get the sound of a USB device being connected, but no access to it and as far as I can tell the PC doesn't even see it. ODIN does nothing either because the device doesn't show up (it was showing up before). I'd really appreciate any help anyone can give on this as this is a brand new phone and I'd hate to think I bricked it beyond recovery somehow. Thanks in advance!
Your bricked because you flashed a rom on your verizon S3 for an international s3 variant. It's amazing you even got far enough to attempt a restore, but the damage was already done, as your nandroid was trying to run on an already corrupted system. You're up the Creek there my friend, sorry. There are links to a company that fixes them for $60, I can't remember the name, so I can't post the link, but will if I do.
---------- Post added at 04:09 AM ---------- Previous post was at 04:06 AM ----------
http://mobiletechvideos.mybigcommerce.com/samsung-galaxy-s-iii-jtag-brick-repair/
Here's the link, thanks prdog for posting in thread below this one.
Stunned at the fact you made the mistake of flashing a rom from a different carrier that is a HUGE NO NO.
Sent from my Galaxy SIII
annoyingduck said:
Your bricked because you flashed a rom on your verizon S3 for an international s3 variant. It's amazing you even got far enough to attempt a restore, but the damage was already done, as your nandroid was trying to run on an already corrupted system. You're up the Creek there my friend, sorry. There are links to a company that fixes them for $60, I can't remember the name, so I can't post the link, but will if I do.
---------- Post added at 04:09 AM ---------- Previous post was at 04:06 AM ----------
Here's the link, thanks prdog for posting in thread below this one.
Click to expand...
Click to collapse
Wow. I seriously can't believe I did that. No more flashing when I'm wasted... :cyclops: Glad I'm still in the 14 days and I can swap it out as DOA. If I can't turn it on to check it, they can't either.
Wow, glad I haven't made that mistake yet. I can see how easy it would be though.
Friends don't let friends flash fried. Good lesson in there somewhere 8 guess.
Alcohol + cell phone + boredom = brick.
The only reason it happened is because instead of going straight to the XDA Android dev thread for the phone like I normally would to find a ROM, I googled "best ROM's for GS3" and the list I got apparently was written by someone overseas (I now realize looking back at the article). I just clicked a link to one of the ROMs that looked cool and the link was actually to XDA anyway so I felt fine about the whole thing. Until my phone bricked that is...
wisdroid said:
Wow. I seriously can't believe I did that. No more flashing when I'm wasted... :cyclops: Glad I'm still in the 14 days and I can swap it out as DOA. If I can't turn it on to check it, they can't either.
Click to expand...
Click to collapse
Yes, committing fraud when you made a mistake yourself it the right thing to do.
Man up and pay to get it Jtagged imo. If you can't afford to get it Jtagged, you shouldn't be flashing ROMS.
Things like this are probably the reason the bootloader was locked in the first place.
Related
If anyone is able....and willing to help, I'd be most grateful.
I know there are many pages in the forum and the net that touch on this, but as one post puts it, almost too many.j
that is the least of the problems. I am a total newbie and get so confused.
When I originally rooted my phone it was with help from someone, now a friend, who I found on YouTube. I always saw confusing ways to root, where you can't miss ONE character. Somehow, don't ask me, feel free to tell me, we rooted with hardly any of that . Some character typing was done, but a lot was using programs, ROM managers, etc.. and hitting buttons.
So it was Rooted and I had no problems flashing ROMS
Now selling. I was gonna sell with MIUI...as I advertised. It was recommended by someone on here to put the factory firmware on .
1. That means flash the original MyTouch 4g firmware/UI/whatever?? ...or does it mean unroot
2. If it means the former, I found one site it gave me this file PD15IMG can I just flash that. It led me to believe I can. It won't be unrooted but it would be the original ROM
3. Or should I unroot. Is anyone willing to walk me thru some steps on here, maybe thru PM...I just get so confused by this stuff because it talks about s=on or ???
4. Lastly, this gent recommended I flash that OR reflash whatever I am gonna send, then Factory wipe. I thought reflashing WAS factory resetting.
Can you tell me how to factory reset AFTER I flash a ROM
LIke I said, I have searched and did find some of this in different places but in jargon I don't understand
So please if you could answer any one or all of the above Id be grateful. If you like I can paypal you 5-10 dollars or a few more if we spend time on it.
Sincerely
Eric
Did you root your phone with Gfree or the root.sh method?
---------- Post added at 09:32 PM ---------- Previous post was at 09:29 PM ----------
Actually you can put the PD15IMG file on your SD card and boot up into bootloader. It will ask you if you want to apply the update...say yes. BE PATIENT. It will get you back to stock.
eric0668 said:
If anyone is able....and willing to help, I'd be most grateful.
I know there are many pages in the forum and the net that touch on this, but as one post puts it, almost too many.j
that is the least of the problems. I am a total newbie and get so confused.
When I originally rooted my phone it was with help from someone, now a friend, who I found on YouTube. I always saw confusing ways to root, where you can't miss ONE character. Somehow, don't ask me, feel free to tell me, we rooted with hardly any of that . Some character typing was done, but a lot was using programs, ROM managers, etc.. and hitting buttons.
So it was Rooted and I had no problems flashing ROMS
Now selling. I was gonna sell with MIUI...as I advertised. It was recommended by someone on here to put the factory firmware on .
1. That means flash the original MyTouch 4g firmware/UI/whatever?? ...or does it mean unroot
2. If it means the former, I found one site it gave me this file PD15IMG can I just flash that. It led me to believe I can. It won't be unrooted but it would be the original ROM
3. Or should I unroot. Is anyone willing to walk me thru some steps on here, maybe thru PM...I just get so confused by this stuff because it talks about s=on or ???
4. Lastly, this gent recommended I flash that OR reflash whatever I am gonna send, then Factory wipe. I thought reflashing WAS factory resetting.
Can you tell me how to factory reset AFTER I flash a ROM
LIke I said, I have searched and did find some of this in different places but in jargon I don't understand
So please if you could answer any one or all of the above Id be grateful. If you like I can paypal you 5-10 dollars or a few more if we spend time on it.
Sincerely
Eric
Click to expand...
Click to collapse
Check the development thread for the RUU file posted by Football. Name it pd15img.zip put it on the root of your sdcard, boot into bootloader and let it flash. That's it. Super easy, no dicking around with anything else.
DON'T FLASH IT WITH RECOVERY!
Sent from my Sensation using xda premium
Phateless said:
Check the development thread for the RUU file posted by Football. Name it pd15img.zip "put it on the root of your sdcard, boot into bootloader and let it flash. That's it. Super easy, no dicking around with anything else.
DON'T FLASH IT WITH RECOVERY!
Sent from my Sensation using xda premium
Click to expand...
Click to collapse
Here you go.
http://forum.xda-developers.com/showthread.php?t=1174344
Sent from my Sensation using xda premium
Much thanks to the 3 of u. It may be a non issue...as I am not hearing back.from the buyer and it was advertised to be sold with MIUI with pics and he may have liked the iPhone 'look' In answer to your questions I was helped by Mack on YouTube to root. I do t k ow which way. I DO know it was the easy way....it involved very little typing and worrying about messing up a character
I have only used ROM Manager and CWM within that. When I reboot I see the option for bootloader. Is it 'dangerous?'
This is what I am gonna do tell me if correct
Take that last link. Hook up to Computerput in root of SD card. Hit restart except dont hit normal
or recovery...hit bootloader...it will restart...maybe hit yes or enter when asked
-only if he gets back to me today if not tomorrow is the 5 th day since he bought it and I have a 4 day turnaround so I will mail as advertised. He has 0 points, sales or purchases on EBay
-for some reason I am getting no email notification for xda when I select it.
-I get some keys that dont type occasionally it may have started with MIUI. could that be beccause of it. Someone on here, a senior told me as good as MIUI is it is unstable
-regardless of which I flash/leave on. How about the factory research tying. Thought that was just the reflashimg. For MIUI I JUST hit wipe data in recovery right after flashing and restart. I guessed that because I did that once by mistake and it restarted with MIUI there
I appreciate all your help and patience here. For all of you I can't give u more than thanks for hopefully getting me thru this. I dont think its my lack of intelligence that can't do it. Its my anxiety, health situation and lack of fundage to be able to brick a phone. No mas for me
That same gent told me that he thinks in HTC phones that once u flash a ROM he thinks u lose ROOT?
I hope to hear back and have a good day
Eric
eric0668 said:
I have only used ROM Manager and CWM within that. When I reboot I see the option for bootloader. Is it 'dangerous?'
This is what I am gonna do tell me if correct
Take that last link. Hook up to Computerput in root of SD card. Hit restart except dont hit normal
or recovery...hit bootloader...it will restart...maybe hit yes or enter when asked
Click to expand...
Click to collapse
No, it is not dangerous. The last link is the RUU (PD15IMG) of the stock ROM. And your steps are good to go. Go into bootloader and let it do its thing.
Flashing rooted ROM's will not make you lose root. You only lose root flashing an unrooted ROM, such as a stock ROM.
CWM Backup and Restore: It backs up fine. But it won't restore. I can't remember the error message...something about rfs and can't mount. I know that's not much help. I was wondering if anyone besides me has had problems restoring with this version of CWM, and has a fix for this problem. I have presently done several backups of my stock rooted GB 2.3.6. And I can't restore any of them. As a noob to the Samsung Charge, I have very little knowledge to work with on this. But it seems to me that I read something somewhere that said I needed to use ADB to do something. Darned if I can remember where I saw it. Any help here would be appreciated. Thanks in advance.
The last version that I know of that had Backup/Restore working properly in was the 0817 version but hell if I know where you can get it.
I have it on my hard drive for my own personal reasons but imnuts has said that I can't upload it or redistribute it in any way. I personally can use the file if I so choose to keep it but I can't upload it to anywhere.
Perhaps you can IM imnuts to send you a copy of the 0817 version.
trparky said:
The last version that I know of that had Backup/Restore working properly in was the 0817 version but hell if I know where you can get it.
I have it on my hard drive for my own personal reasons but imnuts has said that I can't upload it or redistribute it in any way. I personally can use the file if I so choose to keep it but I can't upload it to anywhere.
Perhaps you can IM imnuts to send you a copy of the 0817 version.
Click to expand...
Click to collapse
if you don't mind my asking why is it banned from being posted now? that's the orange 4.0.1.4 version that was up publicly for months and had few issues besides the voodoo menu being removed/disabled... I guess if imnuts ok's it I'll post or pm a link to anyone who needs it
He got pissed at me for having a link to it, that's all. If you want to attach it to your reply, be my guest. I just don't know what will happen.
trparky said:
He got pissed at me for having a link to it, that's all. If you want to attach it to your reply, be my guest. I just don't know what will happen.
Click to expand...
Click to collapse
ah yes I remember, something about imnuts himself wanted to host it to keep track of support and downloads.. nevermind then I won't post publicly but if anyone wants it just pm me
blazing through on my Acer A500 via XDA app
I have found that CWM 5.0.2.7 has removed "Voodoo" from the menu. Anyone know why? I'm just trying to figure out why my nandroid restore function does not restore. Being a noob to the Samsung phone, I can only guess that it has something to do with the existing partition format when restore begins. IOW, is it the same as the backup? If not, it will fail. Am I getting close, or am I still clueless?
Lexus One said:
I have found that CWM 5.0.2.7 has removed "Voodoo" from the menu. Anyone know why? I'm just trying to figure out why my nandroid restore function does not restore. Being a noob to the Samsung phone, I can only guess that it has something to do with the existing partition format when restore begins. IOW, is it the same as the backup? If not, it will fail. Am I getting close, or am I still clueless?
Click to expand...
Click to collapse
backups may or may not work with the new 5.x CWM, some people say they can do it and doesn't work for others so I'd just stick with the 4.x CWM... voodoo options were removed from CWM due to them not working right or not working at all sometimes when trying to disable lagfix which caused bootloops and softbricks
Same problem on Samsung Epic 4G. Backed up rooted stock FC09 & flashed to CM9 Beta 3. Attempted to restore the stock FC09 & error message popped up. I tried this with & without data/cache/dalvic cache etc., etc. wipes. Same problem either way. I also noticed the time stamp on the backup was dated 2005. Wayyy offf ! ! ! Did you have the same incorrect date stamp? I wonder if changing the date on the backup will fix the issue.
---------- Post added at 07:52 PM ---------- Previous post was at 07:14 PM ----------
Just Reposting To Give Further Detailed Info
I'm sure you already know of this issue but, I'll re-post here as from my understanding, this is updated most often & I'm really amped about this project.
Major stock Samsung Epic 4G Gingerbread FC09 restore issue.
I did this exactly:
1) Started stock FC09
2) Odin to cwm-5.0.2.7-epic4g.tar.md5
3) Flashed cm-9-20120507-SNAPSHOT-epicmtd-beta3-pre9.zip using CWM 5.0.2.7 recovery mode (volume down, camera button & power button combo)
4) Backed up rooted stock
5) Attempted to restore the stock FC09 to make sure it works before I got too into the new release
6) Error message popped up
7) I tried this with & without data/cache/dalvic cache etc., etc. wipes. Same problem either way. I also noticed the time stamp on the backup was dated 2005. Wayyy offf ! ! ! Did you have the same incorrect date stamp? I wonder if changing the date on the backup will fix the issue.
Again, my deepest apologies but, right now, I'm like the kid who missed the ice-cream truck. I'm not new to flashing but, am new to trying to run a restore. I only wanted the stock FC09 back because Swype wasn't included in the CM9 Beta 3 release & the text messaging background is white (kinda thwarts the sleek, stealthy black color scheme). Will there be a black text messaging background soon? Let me know if I can install Swype using Titanium Backup or any app backup app. If I can at least have Skype, I'll be good as my Beta 2 Bluetooth issue has been corrected.
---------- Post added at 08:03 PM ---------- Previous post was at 07:52 PM ----------
Sorry. I meant to say I flashed Deodexed-FC09-BML.zip before I flashed cm-9-20120507-SNAPSHOT-epicmtd-beta3-pre9.zip
---------- Post added at 08:23 PM ---------- Previous post was at 08:03 PM ----------
Brain farts today >.< I also ran a CM9 Beta 3 backup before I attempted the stock FC09 restore. After the FC09 restore failed, I tried the CM9 Beta 3 restore & that worked perfectly so, again, my suspicions lye in the wrong date stamp factor. At some point tonight, I'll test this theory and post the results. If anyone beats me to the punch, awesomeness.
So you bumped a 5 month old thread in the Charge forum to say you had a similar issue with an Epic 4G?
Well
Whatever the case may be, the rules of the site are to post similar questions/concerns in a relevant thread that has already been started. I had no idea this was the "charge" forum as nothing above clearly states that. And instead of just saying the generic, "same problem", I opted to give as much detail as possible considering we're dealing with later released software.
Casey Stellar said:
Whatever the case may be, the rules of the site are to post similar questions/concerns in a relevant thread that has already been started. I had no idea this was the "charge" forum as nothing above clearly states that. And instead of just saying the generic, "same problem", I opted to give as much detail as possible considering we're dealing with later released software.
Click to expand...
Click to collapse
You can clearly see at the top of the screen what forum your in. CWM is individually built for each phone, and not every phone is going to support the same features in the same way. Chances are, no one here is going to know anything about the Epic unless someone here just happens to own one.
Wow
Man that thing's tiny. But, as I stated, I didn't notice that & I only posted because the rules say try not to start a new thread concerning a topic that's already been posted. I'm aware each CWM is custom to every phone. I posted the exact details in case someone does notice this thread & has a solution or a definite no it can't be done. I have read on other posts that CWM will restore other custom non-stock ROMs just fine. One source claims people have been able to restore stock back-ups just fine while others have not. But, there were no definite solutions or enough details to go on. Still waiting for a return on that.
XDA (and others) are built around the idea of device specific forums as there are many differences between devices, even in the same family, that prevent anything for one device from working on another. The Droid Charge, as an example, is in the Galaxy S family, but none of the Galaxy S stuff will work directly on it. Even further, the Galaxy S Aviator and the Droid Charge are the same hardware for different carriers, and nothing for the Charge will work on the Aviator. Don't hesitate to make a thread in one device forum just because a thread exists in a different device forum. There's a "Search this forum" button at the top of every subforum. Use it for your device, and post in that forum if you can't find anything.
O.O
Well now I know I've been up to long. I didn't even realize the fact he said "Samsung Charge" nor was I aware there is a Samsung phone called Charge. But, in my defense, I attempted to start a new thread but, as I was typing out a title for the post, the site showed suggestions of other posts that may have my issue already resolved or at least discussed and this one seemed to be the closest. Had I known the Charge was a phone, it may have stuck out more & I would've known I was in the wrong place -_- Silly me. I am glad to announce however that after a little tinkering, I think I have found the solution to my issue. I'll post any results and details in the proper forum. Sorry for any inconveniences.
i was Running Cyanogen Mod the ICS version and my phone was working fine tell it would randomly turn of and boot loop which i was able to fix by reapetably pressing the power button but now that does work and the phone died and i cant get into download mode or Clockwork recovery Any suggestions Would be highly appreciated Thanks!
i am definitley not the sharpest knife in the drawer, but this has happened to me a couple times.
sounds to me the best bet is return to stock.
look into the super everything thread by BigJoe.
either Odin or Heimdall. which ever you are more comfortable with. prefer Odin myself, but everyone has their preference.
if you have never had to do it, read once, read twice. very easy.
if i can do it so can you. u can never go wrong going back to stock. sometimes may be the long way, but for me its safer.
---------- Post added at 04:50 PM ---------- Previous post was at 04:39 PM ----------
super everything thread is in "infuse development".
u probably knew that, but saw your join date and figured it couldnt hurt.
this whole concept was very confusing to me at first. was absolutly paranoid rooting and flashing first time.
i spent first 2 months just reading and trying to understand. figured my phone would blow up.
but i managed to pull it off.
sure u will too.
Alright, so I need a little help here deciding what to do next.
My girlfriend has the SGH-T959v with android 2.2.1 on it.
It had been randomly shutting down when the screen turned off. It was much the same as the Samsung Captivate had its issues.
It also wouldn't charge sometimes and would also not turn on unless the battery was removed.
Well, I replaced the battery with an OEM one from a mobile store.
Now there are no more random shutdowns but there's a whole slew of different issues.
If the phone is turned off you have to remove the battery, put it back in, plug it in quickly, and then turn it on.
If the phone charges too long all the signal stops working until a reboot.
The phone always thinks it's charging even when the battery is draining.
It's a pretty irritating problem especially with the reboot issue because if we're out and away from electricity and it gets turned off accidentally then there's nothing we can do till we get back to the charger.
Has anyone had these issues and solved them with a new ROM?
I had the random shutdowns on my Captivate and solved it with CyanogenMod. I'm thinking about flashing but I don't want to wipe it all and then have it not work or brick the thing (it is unlocked on Straight Talk so I also don't want to relock it to T-Mobile)
Some foresight would be appreciated before I move forward with it.
Thanks
Why don't you try a ROM and find out if it does anything? Questions like this are pointless because you can answer them yourself by just trying it.
Yes, flashing a better ROM will help in certain cases
pisherthefisher said:
Why don't you try a ROM and find out if it does anything? Questions like this are pointless because you can answer them yourself by just trying it.
Click to expand...
Click to collapse
Actually my question was whether or not anyone has had this issue.
I'm trying to see if it's a known firmware problem or a known hardware problem so I don't waste my time.
I don't have all day everyday to backup the phone and flash and test and then reinstall all the apps.
Thanks for the contribution though.
That being said would anyone suggest a TW ROM for this? I don't want to change the functionality because she's used to TouchWiz and not tech savvy
Now I must throw in, you should search around for a TW styled ROM. I don't know if we have one or not, but I can tell you that looking yourself will be a lot quicker then waiting for somebody to feel sorry for you, search for it, and give you a link to it.
Ignore those guys. Dont flash a custom rom YET.
http://forum.xda-developers.com/showthread.php?t=1822626
Read that post follow the directions. I suggest reading the thread it links to while backing up the phone. Then while actually doing the flashing with heimdal follow it.
Now be sure to follow eollies directions of flashing the kernel after the initial boot or wifi will be broken.
This will wipe her phone out and reflash everything plus give you root access to remove bloat and add things like titanium backup.
---------- Post added at 07:49 PM ---------- Previous post was at 07:37 PM ----------
Whoops looks like eollies pulled the file from dropbox.
Just follow the directions in the thread by lumin30 that eollie links too.
I forgot to say why I suggest using a one click. This device sometimes just needs to be reset to factory. And Using a one click will remove all stuff not suppose to be hanging around.
Here's another one that I find much more simple.
Heimdall One Click back to Stock for the T959V
I have the grimlin remover one click on my computer I can upload it later
Cooptx said:
I have the grimlin remover one click on my computer I can upload it later
Click to expand...
Click to collapse
I have it also, but cant get it to upload for whatever reason. So.....
Here's the link: http://forum.xda-developers.com/showthread.php?t=1500427 Post #41 has a working DL. get it, unzip, run it. Maybe it helps him.
Use the heimdall one clicks they are 2.3.3 stock touchwiz. Like I said follow lumin30's guide to the letter. He is a recognized contributor for a damn good reason. That guide has also been featured on the portal. I would flash the antonx kernel after for root and then flash bhundvens latest kernel. This will allow just a bit more control and troubleshooting if something happens.
Alright, I was just throwing it out there xD
Really guys? You're not even answering his question and linking him to old guides that are complicated. If someone needs to go to a stock KJ6 rom just link them to lumin's guide!
Anyway, I doubt you will find anyone on these forums who are still running the 2.2.1 stock rom, I personally haven't run it in over 2 years when I first bought my phone.
Samsung has released an official update from Froyo (what her phone is running) to Gingerbread (the last officially released version for this phone).
I recommend you try that, but know that there is a long-sms bug. If you go over 140 characters the message will get cut off and you will get a "message sending failed" notice when you try to send it. You can instead try to use a 3rd party app like handcent or gosms that will split the message for you if it goes beyond 140 characters.
If you would like an easy to follow, reliable guide WITH PICTURES, then go ahead and follow lumins' guide:
http://forum.xda-developers.com/showpost.php?p=21953878&postcount=2
Just remember that everything on her phone will get wiped, but you can use google to back up contacts. It sounds like it'll be worth it.
Again, lumin's guide will allow you to upgrade her phone to the last official rom Samsung released for our phone.
Good luck!
I wonder if Samsung kies is still upgrading.
Yep so I tried to install CM11
and the last thing was to:
fastboot flash boot boot.img
and that was it. Cannot restore my Nandroid backup - it doesn't boot back up.
Just gets stuck at the HTC page with "This build is for development purposes".
I think I need the stock boot.img but it is no where to be found.
Any help??
Just paid someone to get the RUU and restore then phone. I have no idea how he found the RUU since no one else here has it. If they have it they are not sharing it.
Who did you find to restore your phone?
808phone said:
Just paid someone to get the RUU and restore then phone. I have no idea how he found the RUU since no one else here has it. If they have it they are not sharing it.
Click to expand...
Click to collapse
I have the same problem. Who did you find to restore your phone? Is it possible that I could contact them?
so basically you paid a guy to google the right RUU???
all you had to do is check your CID (its written on fastboot) and search for that, they really arent that hard to find!!
http://forum.xda-developers.com/showthread.php?t=2140967
also if you're going to keep flashing different roms its also a good idea to keep that RUU on your pc somewhere!!
There was no matching ruu. What no one told me was that you could use a newer ruu than the one you have. Another thing, before you judge, there were no replies to help me so I had no choice. Since then look how many times I have helped others.
chrons6 said:
I have the same problem. Who did you find to restore your phone? Is it possible that I could contact them?
Click to expand...
Click to collapse
As I previously posted, you can use a newer ruu than the version you have installed. That's what the guy did.
In not judging at all man, i just couldnt understand as to why you couldnt fine the info... They guy you paid is no different to you or me, che just searched harder... As for the ruu the name itself tells you its an update... No biggie im glad you got it worked out in the end
Sent from my One S using xda app-developers app
zubeedubs said:
In not judging at all man, i just couldnt understand as to why you couldnt fine the info... They guy you paid is no different to you or me, che just searched harder... As for the ruu the name itself tells you its an update... No biggie im glad you got it worked out in the end
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
Did you not read what I said? THERE WAS NO MATCHING RUU! Read OK????
No one told me you could use a NEWER RUU.
If someone - perhaps you had told me, yeah fine, I could have done it. No one helped ok?
BTW: I did a nandroid backup, I had installed custom recovery, rooted with superSU etc... I had adb, fastboot working too. Because I couldn't get an answer I paid someone.
If you have a JTAG machine and you were running a business then maybe you are just like him.
808phone said:
Did you not read what I said? THERE WAS NO MATCHING RUU! Read OK????
No one told me you could use a NEWER RUU.
If someone - perhaps you had told me, yeah fine, I could have done it. No one helped ok?
BTW: I did a nandroid backup, I had installed custom recovery, rooted with superSU etc... I had adb, fastboot working too. Because I couldn't get an answer I paid someone.
If you have a JTAG machine and you were running a business then maybe you are just like him.
Click to expand...
Click to collapse
dude theres no need to get fassy about anything... unless your one s is knock off means that there is a RUU for your device and that you simply couldnt find one in the small amount of time that you searched for one...
and just to gnaw a little more at your flawed logic and sour attitude RUU means "ROM UPDATE UTILITY" so i guess your right in not being able to use a newer one... :good:
AND BTW.. i dont have a jtag but i do run a business and in my line of work we see folk like you everyday, ever so quick to get pi**ed at someone for THEIR OWN mistakes!!!
and maybe if youre that impatient and wound up for your own calamities it serves you right to have paid for a simple task..
---------- Post added at 08:21 PM ---------- Previous post was at 08:14 PM ----------
chrons6 said:
I have the same problem. Who did you find to restore your phone? Is it possible that I could contact them?
Click to expand...
Click to collapse
have a peek at the RUU thread in the dev section and follow the instructions... it really isnt that difficult!!!
? and in my line of work we see folk like you everyday
Right and that's why I have more thanks and posts than you for helping people.
Yes, I know that a RUU has a version number too. I know what it means. If you even took the time to realize that after having to pay, I helped out other people after that so they wouldn't have to pay.
I guess you don't read. I said you COULD use a newer version of the RUU but no one told me.
Where were you when I asked for help? Never mind, you go about yourself and I will continue helping.
In my line of work I know people like you too. You are the type of person people avoid so create your own thread and stop jumping in with unhelpful info.
808phone said:
? and in my line of work we see folk like you everyday
Right and that's why I have more thanks and posts than you for helping people.
Yes, I know that a RUU has a version number too. I know what it means. If you even took the time to realize that after having to pay, I helped out other people after that so they wouldn't have to pay.
I guess you don't read. I said you COULD use a newer version of the RUU but no one told me.
Where were you when I asked for help? Never mind, you go about yourself and I will continue helping.
In my line of work I know people like you too. You are the type of person people avoid so create your own thread and stop jumping in with unhelpful info.
Click to expand...
Click to collapse
about your deluded logic: paying a guy to fix your mistakes is the right info??? seriously?? and thats supposed to help the next guy more than directing him towards the right RUU??? boy you really are a contribution to the comunity...
about your thanks rating: i signed up last month and youve been here since january if youve ever contributed anything on here then you should have more thanks than me, its basic math, also i think i should point out that its a forum and not "thank marathon" nobody wins a prize for them...
as far as helping people: i suppose you have, i dont really care that much either..
lastly: i came on your thread infact to lend a hand, until i saw that youre actually lazy and ready to fire off your mouth at strangers for nothing apart from stating the obvious truth...
so as of now you can take your all your thanks and try and cash them in for the next phone you softbrick and "need" to pay someone else to fix...or maybe not!!!
as for me this discussion is closed as i can only feed a troll so much!!!
808phone said:
As I previously posted, you can use a newer ruu than the version you have installed. That's what the guy did.
Click to expand...
Click to collapse
I understand how the RUU works and how to use it. My problem, though I hope not, may be slightly more unique?
I had previously rooted by ONE S T-Mobile version and it had been working fine. I then decided to try out another rom. I likely flashed an incorrect boot img because it would only reboot into fastboot, but would still allow me to go into recovery. I went to recovery and restored my nandroid backup; however, now the phone will get stuck on the opening HTC screen the red language on the bottom, "this build is for development purposes only." It will hang on this screen for about 20 seconds and then turn off. No loop. When I attempt to power up again, I get a quick horizontal flash of light across my screen and then the orange LED comes on in the top left corner indicating the phone is charging. I then hold down power and again the phone gets stuck on the opening HTC screen with the red language.
My problem is that I cannot get the phone into fastboot
I've received advice on how to enter the bootloader: power off the phone manually by pressing power for 10+ seconds. Then I' should be able to enter the bootloader and fastboot. (Vol down + power)
Unfortunately, no matter how many times I try, using the above method and a variety of other methods, I still can't get past "HTC developmental purposes only" screen. I'm not new to android and have experience with a number of phones, but this is my first HTC. Pretty frustrating thus far. Rather than spend many more hours pulling out my hair and continually going in circles with no progress to show for my efforts, I'd rather pay someone to make the necessary fixes for me.
Any additional advice would be much appreciated.
same problem
zubeedubs said:
about your deluded logic: paying a guy to fix your mistakes is the right info??? seriously?? and thats supposed to help the next guy more than directing him towards the right RUU??? boy you really are a contribution to the comunity...
about your thanks rating: i signed up last month and youve been here since january if youve ever contributed anything on here then you should have more thanks than me, its basic math, also i think i should point out that its a forum and not "thank marathon" nobody wins a prize for them...
as far as helping people: i suppose you have, i dont really care that much either..
lastly: i came on your thread infact to lend a hand, until i saw that youre actually lazy and ready to fire off your mouth at strangers for nothing apart from stating the obvious truth...
so as of now you can take your all your thanks and try and cash them in for the next phone you softbrick and "need" to pay someone else to fix...or maybe not!!!
as for me this discussion is closed as i can only feed a troll so much!!!
Click to expand...
Click to collapse
Just to say that I
chrons6 said:
I understand how the RUU works and how to use it. My problem, though I hope not, may be slightly more unique?
I had previously rooted by ONE S T-Mobile version and it had been working fine. I then decided to try out another rom. I likely flashed an incorrect boot img because it would only reboot into fastboot, but would still allow me to go into recovery. I went to recovery and restored my nandroid backup; however, now the phone will get stuck on the opening HTC screen the red language on the bottom, "this build is for development purposes only." It will hang on this screen for about 20 seconds and then turn off. No loop. When I attempt to power up again, I get a quick horizontal flash of light across my screen and then the orange LED comes on in the top left corner indicating the phone is charging. I then hold down power and again the phone gets stuck on the opening HTC screen with the red language.
My problem is that I cannot get the phone into fastboot
I've received advice on how to enter the bootloader: power off the phone manually by pressing power for 10+ seconds. Then I' should be able to enter the bootloader and fastboot. (Vol down + power)
Unfortunately, no matter how many times I try, using the above method and a variety of other methods, I still can't get past "HTC developmental purposes only" screen. I'm not new to android and have experience with a number of phones, but this is my first HTC. Pretty frustrating thus far. Rather than spend many more hours pulling out my hair and continually going in circles with no progress to show for my efforts, I'd rather pay someone to make the necessary fixes for me.
Any additional advice would be much appreciated.
Click to expand...
Click to collapse
Thankfully I finally figured out how to consistently get my phone to enter into Fastboot; however, no the trouble I'm having is finding the proper RUU. I've tried the 3 T-mobile varients available in the RUU depository found here
http://forum.xda-developers.com/showthread.php?t=2094414
But alas, while I am able to run the RUU program, which enters my phone into a mode where the screen is all black expect for the HTC logo in the middle, I keep on getting error codes. Are there more than 3 RUU varients identified in the depository?
Oh, I should note that I was also able to get into recovery, but my SD was unable to mount so I can't find my Nandroid
Youre at least half Way there, what recovery are you using?? If you can get your PC to see the device try and format the memory to fat32 from PC...
Sent from my One S using xda app-developers app
zubeedubs said:
Youre at least half Way there, what recovery are you using?? If you can get your PC to see the device try and format the memory to fat32 from PC...
Sent from my One S using xda app-developers app
Click to expand...
Click to collapse
I believe I'm using TWRP 6.3.0...I'm at work right now and without the phone, but I'm fairly confident that's the recovery. I'll to get the phone into USB mode and see if I'm offered the opportunity to format the memory.
By the way, thanks for the help...it's much appreciated.
chrons6 said:
I believe I'm using TWRP 6.3.0...I'm at work right now and without the phone, but I'm fairly confident that's the recovery. I'll to get the phone into USB mode and see if I'm offered the opportunity to format the memory.
By the way, thanks for the help...it's much appreciated.
Click to expand...
Click to collapse
That won't help. You can fix the sdcrad bug by flashing stock recovery via fastbot and preform "factory reset + clear storage"