Related
i have searched, read and read more. but i am totally stuck on getting a custom theme and dock setup on my rooted phone. is there a how to that is better written than the ones i have come across on start to end on programs, apps, w/e i need to get one of these custom themes working. seems i follow what is there, but get stuck on area's of it, than i search on that to come up with nothing or no info. maybe im just over doing it all in one day on learning all this, lol. im a video person, but havent seen a install video of this. any help or links or something? thanks
tyhodge07 said:
i have searched, read and read more. but i am totally stuck on getting a custom theme and dock setup on my rooted phone. is there a how to that is better written than the ones i have come across on start to end on programs, apps, w/e i need to get one of these custom themes working. seems i follow what is there, but get stuck on area's of it, than i search on that to come up with nothing or no info. maybe im just over doing it all in one day on learning all this, lol. im a video person, but havent seen a install video of this. any help or links or something? thanks
Click to expand...
Click to collapse
Youre asking how to install a theme?? Find once compatible for your rom. Stick it on your sd card. Boot into recovery, and flash it.
Post what problems you are having. Good luck.
Sent from my PC36100 using XDA App
Dredge said:
Youre asking how to install a theme?? Find once compatible for your rom. Stick it on your sd card. Boot into recovery, and flash it.
Click to expand...
Click to collapse
im not even sure which rom to use, i have tried a couple but the adk is where i am stuck at, when i go to command prompt it isnt at the c://adk/etc.. like what all the write ups are at, its at c://user/applications or something of that nature and i type what should be typed in on the /adk part of it and says it can not be found. i tried reinstalling the adk again and same problem, im doing something wrong somewhere i assume or stuck in a spot that i keep doing wrong and not noticing. i just rooted it, so whatever rom i have i am assuming is the stock one since i havent gotten past this yet.
Your in over your head man, seriously, YOU put the sdk where you want it, me, I just put it in C:\sdk to make my life easy when changing directories.
If command line work is not something your familiar with, have patience, enjoy your rom as it is right now and wait until the super easy one click gui programs are created.
Did you buy the phone already rooted, or did you root it yourself?
Dredge said:
Did you buy the phone already rooted, or did you root it yourself?
Click to expand...
Click to collapse
i rooted it myself. also when i right click on tools and im supposed to see open in comand promp or something, that doesnt appear?
tyhodge07 said:
i rooted it myself. also when i right click on tools and im supposed to see open in comand promp or something, that doesnt appear?
Click to expand...
Click to collapse
You say you rooted it yourself, which is great, but the questions you're asking are so far out that it makes it urprising that you did.
UNLESS... you rooted using simpleroot or some ****? If sooooooo, that makes ur questions make a lot more sense.
Anyways you just boot into recovery, and flash the zip from that menu.
It has nothing to do with adb, cmd, or any of that other bull**** you're talking about. Just do what's bolded and stop going 3 miles outside of the box.
TJDuckett said:
You say you rooted it yourself, which is great, but the questions you're asking are so far out that it makes it urprising that you did.
UNLESS... you rooted using simpleroot or some ****? If sooooooo, that makes ur questions make a lot more sense.
Anyways you just boot into recovery, and flash the zip from that menu.
It has nothing to do with adb, cmd, or any of that other bull**** you're talking about. Just do what's bolded and stop going 3 miles outside of the box.
Click to expand...
Click to collapse
I agree, OP, you are way over complicating it dude. What is your build number? Settings> about phone> software information.
If I didn't know better I would almost bet you're trying to troll us. Being a brand new account and all.
Dredge said:
I agree, OP, you are way over complicating it dude. What is your build number? Settings> about phone> software information.
If I didn't know better I would almost bet you're trying to troll us. Being a brand new account and all.
Click to expand...
Click to collapse
build number
1.17.651.1 cl160858
ive tried the reboot and flash thing and nothing happened, said missing filie or something and erased my phone and now vibrate doesnt work? this is after placing them theme on there i want to use and trying to load it in the boot screen. dont know all these names for the android system. prob just so used to messing with the iphones which is what is making this so hard for me, lol.
tyhodge07 said:
build number
1.17.651.1 cl160858
ive tried the reboot and flash thing and nothing happened, said missing filie or something and erased my phone and now vibrate doesnt work? this is after placing them theme on there i want to use and trying to load it in the boot screen. dont know all these names for the android system. prob just so used to messing with the iphones which is what is making this so hard for me, lol.
Click to expand...
Click to collapse
I don't believe you anymore. Even Root tutorials direct you to install a rom after rooting, which would put you at 1.47.65 or whatever even without 2.2 upgrading.
Trying to flash a zip that isn't valid doesn't do anything at all to your phone... it just... doesn't work and sends you on your way. Absolutely nothing you type comes off as a "real" problem.
Anyways, I'm just going to say straight out, that I think you're trolling and that it's sad that you made an account just to waste your time.
I'm done with this thread.
TJDuckett said:
I don't believe you anymore. Even Root tutorials direct you to install a rom after rooting, which would put you at 1.47.65 or whatever even without 2.2 upgrading.
Trying to flash a zip that isn't valid doesn't do anything at all to your phone... it just... doesn't work and sends you on your way. Absolutely nothing you type comes off as a "real" problem.
Anyways, I'm just going to say straight out, that I think you're trolling and that it's sad that you made an account just to waste your time.
I'm done with this thread.
Click to expand...
Click to collapse
think what you would like, im not a kid. ive answered your questions. computers or phones is nothing new to me. family works for sprint, but will not mess with the rooting part of it. so i was left alone on this. ive searched and searched and what u have read is where i am at. basically i am wanting a custom theme. i have tethering and all that crap that works fine. but a theme wont work and a rom to be 1.47 or whatever was never put on, i have what i posted and have everything a rooted phone should have. obviously im stuck on that rom part of it. no reason to be a **** or call someone a troll or say their trolling, when their asking questions. if ur intentions wernt to help, than dont reply. u wasted ur own time.
Is there anyway to deodex the Infuse yet?
probably the same as a galaxy s. gtg465x posted one but we are haveing trouble getting a successful odin package to fix the phone when things go wrong so people were not willing to try it.
Thank you for the fast respond, are we gonna lose the phone if something goes wrong. or if something goes wrong is there a way to fix it.
sinan2010 said:
Thank you for the fast respond, are we gonna lose the phone if something goes wrong. or if something goes wrong is there a way to fix it.
Click to expand...
Click to collapse
well with samsung we are lucky enough to have odin which is a factory flash tool. unfortunately it is not working on the infuse 100%, there may be a new build of it just for the infuse but it hasnt been leaked yet as far as we know. there is also an opensource application called heimdall that works in place of odin. there has been some success with heimdall but the one user that restored with it is having random vibrate issues.
there are still things to figure out, but there is no reason you cant flash with cwm, there are just no proven roms or reliable methods to restore if it goes wrong.
Thanks again. I'll just wait since I'm not good in doing these kind of things.
Just to chime in, you can definitely softbrick the phone if you try to deodex the rom and something goes wrong. I know from experience (happened to me yesterday ) As far as I know, I'm the only one who has successfully flashed back to stock using h8rift's original test tar but now there's confusion about whether it's reliable or not due to other testers' experiences. We're gonna get there just hang tight.
beatblaster said:
Just to chime in, you can definitely softbrick the phone if you try to deodex the rom and something goes wrong. I know from experience (happened to me yesterday ) As far as I know, I'm the only one who has successfully flashed back to stock using h8rift's original test tar but now there's confusion about whether it's reliable or not due to other testers' experiences. We're gonna get there just hang tight.
Click to expand...
Click to collapse
So there are already some people brick their devices and good to know that you have successfully flashed it back.
I just have no idea how to do these kind of things this is my first Android device. I had HD2 and was so easy to do anything. I'm just afraid to brick my infuse, so I'll just wait
I just need to deodex it so I can be able to read and write in Arabic.
Thanks
So I know there's been some controversy and scares going around about the US version, since it JUST came out. I'm here to calm you guys down. I have now rooted mine, flashed an interim CWM touch version (not permanent) and have flashed a ROM......ALL successfully.
Here's what I did:
UNLOCKING:
Unlock your bootloader by registering at HTCdev.com and following the unlock instructions. Under device, choose "All other devices", as the One S is not yet listed. It'll walk you through getting your unlock token and flashing it.
ROOTING
Follow Paul O Brien's instructions on rooting your phone. I flashed the r3 superboot file he had. The first time it didnt take and just booted the phone back up. Second time it took, and seems to have stuck, at least for apps. Please note that my phone says *TAMPERED* along with the *UNLOCKED* notification. I have no idea what that means exactly, but everything works great for me.
This means if you dont want to leave Sense but want to get the tons of useless and annoying T-Mobile and other bloatware apps out, you can. T-Mo are dicks and make almost 100% of the apps on it by default SYSTEM apps, therefore unremovable. So you'll need root and Titanium Backup to freeze or delete them. I'd recommend freezing the non-TMo one's just in case.
FLASHING ROMS
1. Flash Paul O Brien's intermin CWM touch version. You MUST use this interim CWM version for the moment, as the others do not work properly. Some things like USB mount dont work in this interim version, but the important functions like wipe and flash, backup and restore, and restart do work. The CWM recovery seems permanent, based on my initial trials, so no worries about reflashing it each restart.
2. Flash your ROM of choice from Clockworkmod Recovery. I'm using Black Dragon right now, but there are others out there as well. I'm personally looking forward to CM9, but its a little ways away, usability-wise.
So there you have it, all you US guys. Don't be afraid to mod your phone. Remember all the warranty void disclaimers as always. I'm not responsible for you bricking your phone. This is just my experience in just under 24hrs of use. Things are looking good for the One S.
bump... i see US users still asking.
Mods, can we perhaps sticky this post of mine? I don't want to take credit for the actual methods of rooting, since Paul O Brien and others deserve that credit, but I think it'd be helpful for US users, since many don't know whether or not the international method works.
That, or perhaps editing the Intl guides to make it clear that the US version accepts the same methods and ROMs.
Worked great for me
Sent from my HTC VLE_U using xda premium
So if we root and flash a custom ROM is there any way to get the phone back to factory state, and get rid of the *TAMPERED* and *UNLOCKED* notification??
Did anyone else get a bit of a sad chuckle out of the first step in the instructions being "remove and reinsert battery"?
cyberchuck9000 said:
Did anyone else get a bit of a sad chuckle out of the first step in the instructions being "remove and reinsert battery"?
Click to expand...
Click to collapse
Great, now my blisters on my fingers will heal.
But still.... I cannot imagine not needing a batt pull.
nickmv said:
Mods, can we perhaps sticky this post of mine? I don't want to take credit for the actual methods of rooting, since Paul O Brien and others deserve that credit, but I think it'd be helpful for US users, since many don't know whether or not the international method works.
That, or perhaps editing the Intl guides to make it clear that the US version accepts the same methods and ROMs.
Click to expand...
Click to collapse
+1
androidcues said:
Great, now my blisters on my fingers will heal.
But still.... I cannot imagine not needing a batt pull.
Click to expand...
Click to collapse
If you need to perform a hard reset on the One S, you hold down the power button for about 7-10 secs.
First of all, thanks for this thread...I used the HTC One S All in one tool kit to unlock my phone, unfortunately I miss understood one of the directions(#5) and stopped using the tool kit and followed another thread, much to my surprise, my bootloader is unlocked, hooray My question is, how do I get back to the original state if that is possible? The reason I ask, is I would like to go back and do it correctly...I used better terminal emulator to see if I had root, but all I got was the $ sign instead of the # sign So I would like to start over...
Thanks in advance for the help
I'm honestly not sure what the procedure is for relocking an HTC bootloader. Perhaps do some Google research on some of the latest models, and I bet you'll find something.
That being said, once you unlock the bootloader a single time, the best you can do is go to **RELOCKED** state. You'll never get back **LOCKED**. Once it's gone it's gone. I'm curious about the **TAMPERED** message though. That's an ugly word.
not sure what exactly went wrong.
somehow flashed CWM and now thats the only thing my phone will boot to, even after re-flashing the stock recovery.
can't get the phone to turn on, only CWM every single time.
suhailtheboss said:
not sure what exactly went wrong.
somehow flashed CWM and now thats the only thing my phone will boot to, even after re-flashing the stock recovery.
can't get the phone to turn on, only CWM every single time.
Click to expand...
Click to collapse
Uh oh that doesn't sound good
Sent from my HTC VLE_U using xda premium
yeah, tried reflashing both CWM & stock recovery. phone still boots to CWM everytime.
Luckily i can still access the phone via ADB, (while in recovery) so i'm sure i'll be able to sort it out. just need to take a fresh crack at it tomorrow. gonna switch back to my galaxy nexus tonight. (oh wait, i dont have any other phones that use microsim)
haha.
Hmm, interesting. Did you flash the interim recovery that Paul O Brien posted, and not another version? Just wanna make sure. I've heard of this happening in my past experience with the Nexus S, but I can't recall what the deal was. Regardless, I don't think you're in trouble. As with your GNex, it's very hard to completely brick the device unless you flash perhaps a bad hboot file, however I'm not really familiar with HTC devices.
This is my first HTC so I'm still trying to learn how the hboot and other processes work together. Sry to hear you had bad luck.
UPDATE: You should try the root install script. It tells the phone to boot after install. That might get you booted atleast.
Some thoughts:
1. Flash the stock recovery back and reflash CWM
2. Clear cache and dalvik within CWM, and make sure to use the 'Reboot System' option if you aren't already.
From what I can tell, your "boot-to-recovery" flag is set on the phone, and isn't getting cleared.
nickmv said:
So I know there's been some controversy and scares going around about the US version, since it JUST came out. I'm here to calm you guys down. I have now rooted mine, flashed an interim CWM touch version (not permanent) and have flashed a ROM......ALL successfully.
Here's what I did:
UNLOCKING:
Unlock your bootloader by registering at HTCdev.com and following the unlock instructions. Under device, choose "All other devices", as the One S is not yet listed. It'll walk you through getting your unlock token and flashing it.
ROOTING
Follow Paul O Brien's instructions on rooting your phone. I flashed the r3 superboot file he had. The first time it didnt take and just booted the phone back up. Second time it took, and seems to have stuck, at least for apps. Please note that my phone says *TAMPERED* along with the *UNLOCKED* notification. I have no idea what that means exactly, but everything works great for me.
This means if you dont want to leave Sense but want to get the tons of useless and annoying T-Mobile and other bloatware apps out, you can. T-Mo are dicks and make almost 100% of the apps on it by default SYSTEM apps, therefore unremovable. So you'll need root and Titanium Backup to freeze or delete them. I'd recommend freezing the non-TMo one's just in case.
FLASHING ROMS
1. Flash Paul O Brien's intermin CWM touch version. Some things like USB mount dont work, but the important functions like wipe and flash and restart do. The CWM recovery seems permanent, based on my initial trials, so no worries about reflashing it each restart. I cant speak for the non-interim solutions, but from what I can gather, they are problematic, so avoid them for now.
2. Flash your ROM of choice from Clockworkmod Recovery. I'm using Black Dragon right now, but there are others out there as well. I'm personally looking forward to CM9, but its a little ways away, usability-wise.
So there you have it, all you US guys. Don't be afraid to mod your phone. Remember all the warranty void disclaimers as always. I'm not responsible for you bricking your phone. This is just my experience in just under 24hrs of use. Things are looking good for the One S.
Click to expand...
Click to collapse
Is this part a must? Would you mind PM'ing me with how to do this part if it's a must? I have Unlocked and rooted my phone, just waiting for a good ROM to come by.
Thongvilay said:
Is this part a must? Would you mind PM'ing me with how to do this part if it's a must? I have Unlocked and rooted my phone, just waiting for a good ROM to come by.
Click to expand...
Click to collapse
That step is only if you want to flash ROMs, or need to wipe cache, dalvik, etc. CWM is used for flashing and recovery/backup purposes. If you're not using ROMs yet, then you have no need for it.
nickmv said:
Hmm, interesting. Did you flash the interim recovery that Paul O Brien posted, and not another version? Just wanna make sure. I've heard of this happening in my past experience with the Nexus S, but I can't recall what the deal was. Regardless, I don't think you're in trouble. As with your GNex, it's very hard to completely brick the device unless you flash perhaps a bad hboot file, however I'm not really familiar with HTC devices.
This is my first HTC so I'm still trying to learn how the hboot and other processes work together. Sry to hear you had bad luck.
UPDATE: You should try the root install script. It tells the phone to boot after install. That might get you booted atleast.
Some thoughts:
1. Flash the stock recovery back and reflash CWM
2. Clear cache and dalvik within CWM, and make sure to use the 'Reboot System' option if you aren't already.
From what I can tell, your "boot-to-recovery" flag is set on the phone, and isn't getting cleared.
Click to expand...
Click to collapse
thanks for the tips, i had tried clearing cache/dalvik within CWM and it still would not work. and yes i did flas the interim CWM from paulobrien
luckily the phone would work via ADB while in CWM. So i pushed three different ROMS to the phone, at first each oen would lock up and reboot within 20 seconds of doing anything. I then went back into recovery & wiped data/cache/dalvik maybe 10 times out of sheer frustration. Then re-flashed a fresh copy of black_dragon_v4.0, didnt do anything after boot. just let it sit there till this morning.
now the phone seems to be working perfectly...
so hopefully if anyone encounters this problem my last couple posts will help them out!
suhailtheboss said:
thanks for the tips, i had tried clearing cache/dalvik within CWM and it still would not work. and yes i did flas the interim CWM from paulobrien
luckily the phone would work via ADB while in CWM. So i pushed three different ROMS to the phone, at first each oen would lock up and reboot within 20 seconds of doing anything. I then went back into recovery & wiped data/cache/dalvik maybe 10 times out of sheer frustration. Then re-flashed a fresh copy of black_dragon_v4.0, didnt do anything after boot. just let it sit there till this morning.
now the phone seems to be working perfectly...
so hopefully if anyone encounters this problem my last couple posts will help them out!
Click to expand...
Click to collapse
Wow, I have no idea dude. That sounds kinda crazy. Hopefully all will be well in the future and you won't come across it again.
the only variable i can think of is that i did have the phone about a week before launch. HTC mailed it to me directly.
I thought maybe that had somethign to do with it, but as far as i can tell the phone was the final shipping version.
I sent you a PM, trying to find a solution.
I heard that shabby was working on it but the thread they were posting in just stalled out, So has anyone heard any news of a stock tar file for Samsung Galaxy Exhilarate being worked on?
we have pretty much everything except the stock recovery image. need someone to mod kernel for root so w can get stock recovery off an unmodified phone. I've tried but really don't know what I'm doing.
Nanition said:
I heard that shabby was working on it but the thread they were posting in just stalled out, So has anyone heard any news of a stock tar file for Samsung Galaxy Exhilarate being worked on?
Click to expand...
Click to collapse
Hi Nanition:
As j3r3goss stated, Shabby needs someone to help out. We need an unrooted phone so that we can grab the original recovery that comes on the phone. If you have an unrooted exhilarate and can donate some time/effort, Shabby would be the best person to contact. You can reach him by going to http://webchat.irondust.net/?channels=hitsquad Just type in his name (Shabbypenguin) and if he's lurking he'll respond.
Shabby had someone volunteer, but he said it didn't work out (no details as to why or what happened).
V/R
BlackWolf
Black-wolf said:
Hi Nanition:
As j3r3goss stated, Shabby needs someone to help out. We need an unrooted phone so that we can grab the original recovery that comes on the phone. If you have an unrooted exhilarate and can donate some time/effort, Shabby would be the best person to contact. You can reach him by going to [10 posts] Just type in his name (Shabbypenguin) and if he's lurking he'll respond.
Shabby had someone volunteer, but he said it didn't work out (no details as to why or what happened).
V/R
BlackWolf
Click to expand...
Click to collapse
Unfortunatly when I was rooting the phone something weird happened and nearly hard bricked it, but I am currently running Tmobile blaze 4g on it with no sound or calling. So hopefully sometime soon someone will be able to help Shabby get a stock tar figured out and ran.
Nanition said:
Unfortunatly when I was rooting the phone something weird happened and nearly hard bricked it, but I am currently running Tmobile blaze 4g on it with no sound or calling. So hopefully sometime soon someone will be able to help Shabby get a stock tar figured out and ran.
Click to expand...
Click to collapse
Shabby has the system.img and boot.img from my phone. Contact him and see if he can explain how to get back to a stock image. Also, if he can't help, get w/ j3r3goss about this as he had the very same issue, but I think he got his back to running the way it's supposed to.
Hope that helps!
V/R
BlackWolf
stock tar
Here's what I used to get the stock OS back, minus recovery of course. The tar contains the system and boot and can be pushed via Odin. For some reason when I had the radio files in the tar it would fail in Odin so I found a script to update those via CWM. I'm not sure what all needs to be done but since mine was extremely messed up I pushed the system tar via Odin then booted into CWM Recovery flashed the radio.zip then performed factory reset x3, format cache x3, format dalvik cache x3 and fixed permissions. It took a bit but booted just and I have had no issues.
You will need to perform a touch key fw update after you boot recovery, but everything else appears to be fully functional. We still need to get some assistance in getting the boot.img rooted so that we can get a dump of the stock recovery.img.
Hope this helps.
Obviously these are to be used at your own risk.
I577 GB Radio UCLD2
http://d-h.st/9PF
I577 ICS Radio UCLH3
http://d-h.st/xka
j3r3goss said:
Here's what I used to get the stock OS back, minus recovery of course. The tar contains the system and boot and can be pushed via Odin. For some reason when I had the radio files in the tar it would fail in Odin so I found a script to update those via CWM. I'm not sure what all needs to be done but since mine was extremely messed up I pushed the system tar via Odin then booted into CWM Recovery flashed the radio.zip then performed factory reset x3, format cache x3, format dalvik cache x3 and fixed permissions. It took a bit but booted just and I have had no issues.
You will need to perform a touch key fw update after you boot recovery, but everything else appears to be fully functional. We still need to get some assistance in getting the boot.img rooted so that we can get a dump of the stock recovery.img.
Hope this helps.
Obviously these are to be used at your own risk.
Click to expand...
Click to collapse
Thanks for your help! I'll try these and get back to you on the results.
worked
Glad to hear it worked.
Sent from my SAMSUNG-SGH-I577 using xda premium
Working on a Custom ROM
Nanition said:
Thanks for your help! I'll try these and get back to you on the results.
worked
Click to expand...
Click to collapse
I am about to start working on a custom System ROM for this phone. What Apps should be included, what apps should be removed (AT&T crapware of course - but what else)?
I want to make a basic one with just a few key apps, and a more advance one for the ultimate tweaker/hacker.
All suggestions (but please be polite) are welcome!
We also still don't have the original restore.img - so if you want to help w/ that, let me know, I may have an angle that we can get it with.
V/R
BlackWolf
ROM
Black-wolf said:
I am about to start working on a custom System ROM for this phone. What Apps should be included, what apps should be removed (AT&T crapware of course - but what else)?
I want to make a basic one with just a few key apps, and a more advance one for the ultimate tweaker/hacker.
All suggestions (but please be polite) are welcome!
We also still don't have the original restore.img - so if you want to help w/ that, let me know, I may have an angle that we can get it with.
V/R
BlackWolf
Click to expand...
Click to collapse
Right now the biggest things for me are bloat and launcher. Everything AT&T needs to go. Is there a way to seperate Google apps or do they pretty much install together? Ther are way to many Google apps that I don't use or ever care to use. Not a big fan of the TW so I'm using ADW, but that can be easily changed by the user. One thing I have been trying to find is support for volume rocker music controls. I use this thing for for music all the time and hate having to skip tracks from the screen.
j3r3goss said:
Right now the biggest things for me are bloat and launcher. Everything AT&T needs to go. Is there a way to seperate Google apps or do they pretty much install together? Ther are way to many Google apps that I don't use or ever care to use. Not a big fan of the TW so I'm using ADW, but that can be easily changed by the user. One thing I have been trying to find is support for volume rocker music controls. I use this thing for for music all the time and hate having to skip tracks from the screen.
Click to expand...
Click to collapse
j3r3: The Google apps can all be installed separately AFAIK. What's TW? I'm familiar with ADW so I assume it's a launcher?
I think there is an app that does the vol control switch, but I don't know what it is off the top of my head.
V/R
BlackWolf
TW = TouchWiz
Custom Binary Counter Reset
I take absolutely no credit for this, I merely tried it and it does infact work for our phone as well. I was at 42 BTW.
http://forum.xda-developers.com/showthread.php?t=1694529
j3r3goss said:
Right now the biggest things for me are bloat and launcher. Everything AT&T needs to go. Is there a way to seperate Google apps or do they pretty much install together? Ther are way to many Google apps that I don't use or ever care to use. Not a big fan of the TW so I'm using ADW, but that can be easily changed by the user. One thing I have been trying to find is support for volume rocker music controls. I use this thing for for music all the time and hate having to skip tracks from the screen.
Click to expand...
Click to collapse
Hey bud. Does shabby need som1 to send him a phone? I got one of these phones. Stock of course. I'd like to root it. I'm hip to flashing. I've got the note running flapjaxxx rom. Samsung s2 running blu kuban. So anyhow. What does he need?
I don't know what's going on with Shabby. As far as I know there are some people trying to get ahold of him to test his rooted kernel and he's not responding nor has he posted his rooted kernel.
Sent from my SAMSUNG-SGH-I577 using xda premium
harley1rocker said:
Hey bud. Does shabby need som1 to send him a phone? I got one of these phones. Stock of course. I'd like to root it. I'm hip to flashing. I've got the note running flapjaxxx rom. Samsung s2 running blu kuban. So anyhow. What does he need?
Click to expand...
Click to collapse
I don't know if Shabby needs a phone or not. I personally, haven't heard from Shabby since a couple of weeks ago.
You can always go to his site and PM him and make the offer.
I was actually hoping my wife would buy one of these, and I was going to try to grab the stock restore, but she opted for a Galaxy S II SkyRocket instead (larger screen, more memory, thinner, etc. - but she did like that my phone is smaller (edge-to-edge)).
Anyway, we're pretty much stuck at the moment. We don't have the original restore, and we can't seem to get it.
I think I know what needs to be done, but I'd have to consult w/ Shabby and j3r3. If you're willing to try yourself, you need to get the rooted ROM, and get it installed on your phone. Then, as I understand it, you need to adb the phone and dd a restore.img. Once we have that, we can then install custom ROMs and revert back to stock if needed.
Other than that, we have full root, and I have been able to uninstall AT&T crapware, Samsung Crapware, and also most of the other system stuff that isn't needed/wanted.
The next step is, as I find time, to create a minimal ROM that has only what is necessary for the phone to function. There will be a couple of other apps (to verify root, and allow you access to all files and system settings), but other than that - that'll be it.
Let me know if you think you'd be willing to be a guinea pig on this - and you should let j3r3 and shabby know as well (if shabby is still interested).
V/R
BlackWolf
---------- Post added at 02:37 AM ---------- Previous post was at 02:25 AM ----------
j3r3goss said:
I don't know what's going on with Shabby. As far as I know there are some people trying to get ahold of him to test his rooted kernel and he's not responding nor has he posted his rooted kernel.
Sent from my SAMSUNG-SGH-I577 using xda premium
Click to expand...
Click to collapse
Since I just read this: I will post a rooted Kernel here in a day or so...
V/R
BlackWolf
Got the Original Kernel and Platform.tar files
So, I found, DL'd and am currently uploading the original Samsung Exhilarate SGH-i577 Opensource Kernel and Platform Files... Good find? I think (hope) so.
If you need them, go here: https://docs.google.com/folder/d/0B7...VmckQwRnc/edit
You can DL any of the files I have posted there, or you can just DL the entire zip here: https://docs.google.com/open?id=0B7nWFHy_HCE7aTBEbF83T2Z0Mzg11.
Or you can just them from where I did: The files were DL'd from the Samsung Open Source website: http://opensource.samsung.com/index.jsp - just do a search for "i577".
V/R
BlackWolf
ROM for Exhilarate?
Hi
I am new to this...
I was able to successfully root my Galaxy Exhilarate (Thank you) - trying to unlock it so I can use it with other carriers - do I need a specific ROM file? are the files posted by Black-wolf what I need?
Thanks
GHORR
GHORR said:
Hi
I am new to this...
I was able to successfully root my Galaxy Exhilarate (Thank you) - trying to unlock it so I can use it with other carriers - do I need a specific ROM file? are the files posted by Black-wolf what I need?
Thanks
GHORR
Click to expand...
Click to collapse
GHORR: Here's the deal: As of right now, there is no way to unlock your phone for use with other carriers unless you can convince AT&T to send you the unlock code. To do that (I know this from experience), you'll need to be able to explain why you want it unlocked to them. Read this thread for more info: http://forum.xda-developers.com/showthread.php?t=1812976
I know that doesn't help. However, you can also do a search for "SIM Unlock" - there are some phones that have had their system files hacked and you might be able to unlock it that way. Note, I am in no way responsible for anything that happens to your phone. This is at your own risk.
Good luck
V/R
BlackWolf
Thanks for replying - but I thought that by flashing the ROM it removes the lock, did I get it wrong?
I posted this somewhere else, but I figured it was more appropriate to place it here.
After rooting and installing CWM using the method in the sticky at the top of the development section, (darkman's unnoficial CWM Recovery), My touchscreen no longer responds to finger input. The pen works fine, and is the only way I can navigate the tablet. Touch input doesn't work in CWM-touch either. I have tried: flashing a custom rom, flashing a stock rom through CWM, flashing stock firmware through Odin (both 4.0.4 and 4.1.2), resetting the triangle count, factory wipe/data reset, re-installing stock recovery, and changing various options in the settings. Nothing helped at all. I'm currently waiting for a reply on filing a warranty claim, but would really like not to have to send it in and wait for a new one. I've seen other people with similar issues, but most of them are either the s-pen doesn't work, or both s-pen and touch don't work. Does anyone have any idea of how to fix it, or is it definitely a hardware issue?
Thanks,
Reffu
Hi,
same issue here. Today the touchscreen stopped working suddenly after i flashed the Android Revolution HD 5.0 Rom yesterday. However, the S-Pen is still working fine. Installing other ROMs and the Stock ROM via Odin did not help. Issue allso appears in Touch-enabled-Recovery.
I see no reason, why this should be a hardware issue, although my N8000 came back from service a few days ago, where they also replaced the screen and digitizer.
Had anyone this issue before and was abled to resolve it?
Greets
I have the same problem on an n8013. Installed Revolution ROM HD version 5, rebooted and lost me touchscreen completely. Nothings worked. Flashed back to stock 4.1.2 but still no go.
Sent from my SCH-I535 using Tapatalk 2
to read this as a Note 10.1 newbie is not very encouraging. are there any similar facts between all of you like
which Note model do you have
how did you jaibreak (which method)
which rom did you have before
which rom do you have now
how did you flash a new rom
...
is there a way to find out whether the touchscreen is really "dead for touch"?
This is a bit scary - my Note 10.1 is arriving today, and I plan to root it at a minimum. I actually don't mind Touchwiz all that much on my Note 2 (which is running CleanROM ACE), so I think I might just root the 10.1 for now.
So restoring completely back to stock (via Odin) doesn't fix it? That is really odd that ROM-ing this thing might cause a hardware failure...
jiggyman said:
I have the same problem on an n8013. Installed Revolution ROM HD version 5, rebooted and lost me touchscreen completely. Nothings worked. Flashed back to stock 4.1.2 but still no go.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
I would be tossing my cookies at this point ........ Did you also do a factory reset after flashing back to factory ROM?
kkretch said:
I would be tossing my cookies at this point ........ Did you also do a factory reset after flashing back to factory ROM?
Click to expand...
Click to collapse
Did anyone solve this, I'm having the same problem.
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
reffu said:
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
Click to expand...
Click to collapse
Just curious - did you just root, or did you root and install a ROM?
I am only rooted so far - haven't felt the need to ROM yet - partially due to worries about this happening. I bought a refurb from Best Buy and only get 90 days of warranty.
reffu said:
I never actually ended up solving this. I sent it in for repair (I had just bought it about a week before attempting to root) after flashing back to stock, and now I have a "new" one . I really want to root it, but I'm afraid the same thing is going to happen again. I really don't want to have to check if the warranty will cover the same issue twice, even if they don't know I rooted.
Click to expand...
Click to collapse
If they say you got a new one, you got one. They'll tell you otherwise if there's an issue over the phone.
But I wouldn't be afraid of ROMs, but to be more diligent and wise when it comes to choosing them. It's like choosing a poisonous mushroom versus an edible one to make stroganoff or stir fry. If you know what to avoid for the next time and follow the correct process to doing the root and flashing, there will not be an issues.
This is from someone who has soft-bricked my first tablet and learned how to unbrick my SIM-less Captivate and Note 10.1. It's how you apply the method and how much attention you practice not getting stuck into these situations is what matters. Especially since I bricked my tablet via experimentation and un-bricked it on the same day with ease.
It's not some big complex deal of rocket science or something only the mere geniuses can do, its how you perceive yourself and how you act. If you believe that you will suck and brick it to kingdom come , it will happen intentionally or subconsciously.
In this case, it was a freak accident where the file/s accessed and deleted the wrong files which allowed for capacitive touchscreen use, and it should be reported to x developers if you have not done so already.
I have rooted and used the Revolution HD rom, the Rom where you customize the colors of the bar/other things, and on the Captivate, the AOKP Collective. I further customized the latter with the Xperia launcher as it zips.
Did anyone find a repair for this besides replacement? My Note 2 is doing the same thing now.
Has anyone found a fix for the touch screen not working yet??
Anyone have any ideas?
Technicians input for touch problem
I am a technician and been repairing electronic devices for over 30 years and I would say the majority of repairs I have done were caused by people not happy with how their standard brand new device works and feel they need to make it better by modifying it in some way or other.
Now with smartphones if you didn't want the device as a standard rom and operating system why buy it ?
If you think the phone would be so much better with a modified rom then buy one working with a modded rom to start with as most of you put as much effort into modding as you did in your school work.
Anyone with half a brain that follows the instructions on the mod sites exactly as shown step by step will never have a problem, all those that do end up with paper weights or bricks didn't follow the instructions in numerical order.
Believe it or not even if after you have modded a rom and brought it back to standard they know it has been modded as they have a list of problems associated with repairs after roms have been modded so you are only fooling yourself they don't.
Same as the smoker that tells his Dr he has given up even though all the symptoms prove he really didn't.
So in my expert opinion if you play with modding and stuff it up why should you be eligible for a warranty claim ? The manufacturer has sold you or supplied a working item that you decided to f_ck around with and because of your stupidity expect some one else to pay for it.
I am not saying don't mod your phone with all the great roms out there but please to save yourself a lot of pain and cost some poor smuck trying to run a business in these economic times a lot of out of pocket from sending items back for replacement or warranty plus the time it takes to do all the paperwork and such, please please please read the instructions 300% or triple check you are doing everything exactly as the instructions say and you will be enjoying all the new benefits of that customised rom and laughing at all the noobs stuffing up their brand new device from not doing so.
I know this won't fix your problem but reread that last bit it was your problem as you are to clever to follow some one else's instructions
anyone have solution regarding this issue, mine have issue also, can anyone spare how to fix it without changing hardware?
---------- Post added at 06:47 AM ---------- Previous post was at 06:28 AM ----------
i hope anyone can solve my issue with touch not responding
WOW.. on TOPIC Flashing .pit might help ???
Gardum said:
I am a technician and been repairing electronic devices for over 30 years and I would say the majority of repairs I have done were caused by people not happy with how their standard brand new device works and feel they need to make it better by modifying it in some way or other.
Now with smartphones if you didn't want the device as a standard rom and operating system why buy it ?
If you think the phone would be so much better with a modified rom then buy one working with a modded rom to start with as most of you put as much effort into modding as you did in your school work.
Anyone with half a brain
Click to expand...
Click to collapse
------------------------------------------------------------------
WOW.. And you come to XDA For ? Most of the time The modded roms often fix manufacture issues and add features the manufacturer decided users do NOT Need ..Being your first post on xda . I do NOT think attacking users is the way to go. Also your post adds nothing to help the users..
ON TOPIC
Have any of you who have this issue try to do a full Wipe and flash pit file for your device.. Something is being left behind and not over written is most likely the Cause.. Also post this in the Rom developers forum So maybe he can look into it more as its his Creation..
Good Luck
erica_renee said:
------------------------------------------------------------------
WOW.. And you come to XDA For ? Most of the time The modded roms often fix manufacture issues and add features the manufacturer decided users do NOT Need ..Being your first post on xda . I do NOT think attacking users is the way to go. Also your post adds nothing to help the users..
ON TOPIC
Have any of you who have this issue try to do a full Wipe and flash pit file for your device.. Something is being left behind and not over written is most likely the Cause.. Also post this in the Rom developers forum So maybe he can look into it more as its his Creation..
Good Luck
Click to expand...
Click to collapse
thanks for reply can you give us a hint how to find pit files to flash it in Odin, pit files + official firmware tar.md5 right sir? my model is n8020 i will give it a try, thanks for reply sir
popohunters said:
thanks for reply can you give us a hint how to find pit files to flash it in Odin, pit files + official firmware tar.md5 right sir? my model is n8020 i will give it a try, thanks for reply sir
Click to expand...
Click to collapse
i Have seen them floating around random threads. There is a Thread in the General section with .pit files. Buy you MUST have the one for your Device..
Sorry i cant help I have 8013 device .
erica_renee said:
i Have seen them floating around random threads. There is a Thread in the General section with .pit files. Buy you MUST have the one for your Device..
Sorry i cant help I have 8013 device .
Click to expand...
Click to collapse
thanks sir, im done the flashing with pit files+ official firmware but touch screen is still missing, is there a modem file for touch screen maybe i missed it while its in downloading process before i brick the touch screen
any hope out there?????
confused and need help
i have a n8000 , base band version N8000XXCLL1, my touch screen stoped responding while playing a game , only Spen works , tried resetting , but no help, I'm a no-voice when it comes to programing and need a step by step guide >>>> many thanks in advance for all your help
reffu said:
I posted this somewhere else, but I figured it was more appropriate to place it here.
After rooting and installing CWM using the method in the sticky at the top of the development section, (darkman's unnoficial CWM Recovery), My touchscreen no longer responds to finger input. The pen works fine, and is the only way I can navigate the tablet. Touch input doesn't work in CWM-touch either. I have tried: flashing a custom rom, flashing a stock rom through CWM, flashing stock firmware through Odin (both 4.0.4 and 4.1.2), resetting the triangle count, factory wipe/data reset, re-installing stock recovery, and changing various options in the settings. Nothing helped at all. I'm currently waiting for a reply on filing a warranty claim, but would really like not to have to send it in and wait for a new one. I've seen other people with similar issues, but most of them are either the s-pen doesn't work, or both s-pen and touch don't work. Does anyone have any idea of how to fix it, or is it definitely a hardware issue?
I got the same problem after rooting my phone.... I used the following method and got ride of that Problem. ..
type this star code in in it Phone dialler *#2663#
Now you should see "TSP"
<update>
TAP on TSP ......it will take 5 seconds only....
......
NOW ENJOY ☺☺
Click to expand...
Click to collapse