I flashed a wrong PDA file onto my cdma tab. Now my screen and backlights do not come on. I am still able to flash via Odin and also Heimdall. I have no idea as to what it is that is causing it.
-And I know this is supposed to be in the general Q/A however I needed master devs to see this.
well I had never seen or saw any troubleshooting on this weird issue. I'm sending mine in to Samsung, nevertheless info may be helpful.
mods please move
if you are on verizon you might want to read this link
http://www.droidforums.net/forum/samsung-galaxy-tab/113084-how-restore-vzw-galaxy-tab-stock-dj11.html
I hope this will help you.
Good luck
Related
Hi All,
I've recently realized that none of my notifications will cause my EVO to vibrate.
I rooted my phone using unrevoked about 4 months ago, and up until about a month ago everything was working fine, when the vibration notifications suddenly stopped.
I have tried checking all settings (which are set correctly), downloading the Sound Manager application, and most recently (today), flashing to the Fresh 4.1 ROM, all to no avail.
I have also attempted (unsuccessfully) flashing back to the original EVO ROM (3.2 i think), after setting S-chip back to "On", but was receiving an error message stating that the main version I was trying to flash is older than the current one.
Attempts to revert back to factory defaults also did not correct this problem.
I have been searching different sites for about 3 days now hoping to find some information on how to correct this or perhaps someone who has has a similair issue.
Any assistance would be appreciated.
Thanks in advance.
Dude, you're begging to be banned already. don't post in a title that rooting caused your vibration to fail. It has NOTHING to do with rooting. its a hardware failure. If you have a warranty, then unroot your phone and revert it back to normal. then send your phone in to be replaced. btw, what are you 12?
EDIT, THROUGH ALL YOUR RESEARCH YOU COULDN'T FIND ANYONE ELSE WITH YOUR ISSUE. LMAO. take that back you're 5 years old. lmao btw, if you have a question. go post in the questions part of the forum.
Thanks for the reply.
No, I am not begging to get banned, and I am obviously not 5 years old. THE IRONY OF SOMEONE TYPING IN CAPS INFERRING SOMEONE ELSE'S IMMATURITY IS AMUSING, BTW.
To clarify, I have been searching for someone who has had the issue and could also assist me with correcting it. As I mentioned, the corrective approaches that I have found up to this point have not worked.
I appreciate the fact that you believe this may be a hardware issue, so I am certainly interested in finding out how to successfully unroot the phone, as I mentioned in my post, I have had several issues when trying to do this.
This post does, however, belong in the questions forum, which I had mistakenly navigated from, so +1 to you.
Thoughts?
I've been noticing that there doesn't seem to be much activity around the Sprint Version of the HTC One. Correct me if i'm wrong. I did manage to get the recovery changed and the device rooted.
Recovery didn't go too smoothly because i didn't realize there was a different TWrp for sprint and i assume the same goes for clockwork. I tried using both and wouldn't work until i found a very brief mention of a sprint TWRP file that ended in wls.
I really wanted to try the Revolution HD ROM but quickly noticed that it seemed like most all version of the htc one are supported except the sprint version. There is a v9.4 but i have yet to find it.
Question: Is the sprint version that different from the others? That difficult to work with? or is the interest just too low?
I was thinking i'd try to have this thread (easily searchable for sprint users) with some quick info on how to deal with those devices. Though i will admit i'm not that skilled in software mods. Just a member of the community that appreciates all the work you guys put in on all these devices and supporting the freedom we enjoy to use our devices as WE please.
If anyone want to join in and commenting about Sprint specific devices and issues.. feel free.
Sorry the sprint version tends to lag behind others because of the cmda chip. Since all international leaks are probably going to be from gsm models, they are only going to be usable on gsm versions of the phone. Until someone leaks a cdma version of 4.2.2 there's not much we can do.
Sent from my HTC One using Tapatalk 4 Beta
This thread shouldn't be here. This should be in the General thread.
Thread Moved
Please only post development related threads in the dev section.
Recovery Experience
Step 1 - Unlocking Boot Loader
I used the Revolution HD thread as a start point. It is very detailed and easy to follow. It directed me to this flashing Guide http://forum.xda-developers.com/showthread.php?t=2265618... The bootloader process is easy and pain free.
Step 2 - Flashing to a more advanced recovery
The guide doesn't suggest which to use. I went to the Device essentials (sticky thread of the forum). The choices seem to be TWRP and Clockwork ... (if there are more feel free to suggest). Unfortunately this didn't go as planned because I was unaware that the recoveries for a sprint device were different ... So for you ... if you are using TWRP you must use the recovery specifically for Sprint devices .. currently the file name is "openrecovery-twrp-2.5.0.0-m7wls.img". I will try to find a link or anyone can volunteer it.
1. The first thing it allows you to do is save your current recovery. I was unable to do this because i had the wrong recovery and by the time realized it i had tried to flashboot flash. However, you can flashboot boot .. which basically allow you to load the recovery and save your current recovery. then you can flash and replace your recovery with the new one.
That is it.. that is kind of where i am at for now. I haven't flashed a ROM .. and i will say i am having some difficulty with both "superuser" it keeps asking to update but then fails and Wifi Tether .... so i'll return with answers to that when i find them.
Hope this helps someone
seemed like a development issue to me ..
original_ganjaman said:
Thread Moved
Please only post development related threads in the dev section.
Click to expand...
Click to collapse
instructions on how to avoid some development / installation problems? I thought that would fit into development. Apologies if it doesn't fit. Thanks for the move.
makes sense ..
syaoran68 said:
Sorry the sprint version tends to lag behind others because of the cmda chip. Since all international leaks are probably going to be from gsm models, they are only going to be usable on gsm versions of the phone. Until someone leaks a cdma version of 4.2.2 there's not much we can do.
Sent from my HTC One using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thanks. That both sucks and makes sense.
_sunz said:
instructions on how to avoid some development / installation problems? I thought that would fit into development. Apologies if it doesn't fit. Thanks for the move.
Click to expand...
Click to collapse
That's just it, it is an issue. If you have issues with a particular custom ROM then you should post in that thread. Development thread is for development and not "issues" with a development.
_sunz said:
instructions on how to avoid some development / installation problems? I thought that would fit into development. Apologies if it doesn't fit. Thanks for the move.
Click to expand...
Click to collapse
Nope, this contains no development, its more of a discussion thread. I can see the confusion, so no problem.
_sunz said:
Step 1 - Unlocking Boot Loader
I used the Revolution HD thread as a start point. It is very detailed and easy to follow. It directed me to this flashing Guide http://forum.xda-developers.com/showthread.php?t=2265618... The bootloader process is easy and pain free.
Step 2 - Flashing to a more advanced recovery
The guide doesn't suggest which to use. I went to the Device essentials (sticky thread of the forum). The choices seem to be TWRP and Clockwork ... (if there are more feel free to suggest). Unfortunately this didn't go as planned because I was unaware that the recoveries for a sprint device were different ... So for you ... if you are using TWRP you must use the recovery specifically for Sprint devices .. currently the file name is "openrecovery-twrp-2.5.0.0-m7wls.img". I will try to find a link or anyone can volunteer it.
1. The first thing it allows you to do is save your current recovery. I was unable to do this because i had the wrong recovery and by the time realized it i had tried to flashboot flash. However, you can flashboot boot .. which basically allow you to load the recovery and save your current recovery. then you can flash and replace your recovery with the new one.
That is it.. that is kind of where i am at for now. I haven't flashed a ROM .. and i will say i am having some difficulty with both "superuser" it keeps asking to update but then fails and Wifi Tether .... so i'll return with answers to that when i find them.
Hope this helps someone
Click to expand...
Click to collapse
Resolved SuperSU and Wifi Tether Issue. The issue was the binary update. HOwever i am not sure how i fixed it. i just tried using the TWRP/CWM method for a third time and it work. it rebooted into recovery, installed the binary file and booted back into the OS. SuperSU worked and then i tried Wifi Tether and it started to work as well .. FYI "settings for Wifi Tether" that i use
1. Device profile "Generic ICS/JB (wlan0)". 2. Wifi-Driver reload (checked).
Now I just need the awesomest best ROM .. any suggestions!?
I rooted my MF3 updated galaxy s4, had a problem which I fixed with the kies triangle fix. I decided to go back to stock so I unrooted through supersu. Then I started having this issue. And now it's just stuck on custom system. I ran the mf3 update through recovery and it applied fine, yet I still have custom system. I'm planning to go to the att store to get a replacement but I can't because of this issue. Anyone have an idea?
I suggest you search for "sysscope" to get more information about the issue and then you can go to the general section and here in the Q&A section and look through the first couple of pages on both sub-forums (or use the search function) to find similar threads that have solution that might work for you. There is a lot of information that could solve your issue. Good luck.
Thanks for the reply, I over looked something :silly:
scott14719 said:
I suggest you search for "sysscope" to get more information about the issue and then you can go to the general section and here in the Q&A section and look through the first couple of pages on both sub-forums (or use the search function) to find similar threads that have solution that might work for you. There is a lot of information that could solve your issue. Good luck.
Click to expand...
Click to collapse
I did my first rooting blah, blah, blah and it was a success on the exception I have no sound now. everything works fine except I can't call anyone and or listen to music. I did tons of research on this before posting this, but I still didn't get my problem resolved which in turn forced me to pester ya'll. I found a thread of others having this problem and tried a fix about trying to install a different modem with odin and it keeps failing.
I installed the MJA upgrade (how to root sph-l720) I saw on youtube. after the rooting etc.. is when I lost sound. everything else worked (data) (wifi) (texting) (googleplay) etc......
I could only find one other modem to try, but like I said it failed to install.
after 3 days of browsing and getting things done by myself, I'm burned out and could really use help on this. I'm very new to this phone thing so please, if there is a way to fix this, be as detailed as possible.
I didn't have time to read forum rules so I didn't post any links cause I was not sure if I was allowed to. If I am and ya'll would like me to post where I learned the rooting and a so called fix to my problem. I can do that. just let me know.
Thanks!
Well this section is for not for your version of the S4. So you would probably have more luck in this section:
http://forum.xda-developers.com/galaxy-s4-sprint
You give way to few details to help you.
- What rooting method did you use?
- What is the excact file that you used for rooting (filename is good enough).
- What is the excact firmware that you are using?
My guess would be that you flashed the wrong file for rooting (if you used cf-root). Just try to reflash the firmware you are on with Odin. That should probably fix it.
You don't need to flash a different modem. I don't think that thats the problem.
Give us more then a name to a youtube video (I can't even find it). Be specific. The more details the better.
Lennyz1988 said:
Well this section is for not for your version of the S4. So you would probably have more luck in this section:
http://forum.xda-developers.com/galaxy-s4-sprint
You give way to few details to help you.
- What rooting method did you use?
- What is the excact file that you used for rooting (filename is good enough).
- What is the excact firmware that you are using?
My guess would be that you flashed the wrong file for rooting (if you used cf-root). Just try to reflash the firmware you are on with Odin. That should probably fix it.
You don't need to flash a different modem. I don't think that thats the problem.
Give us more then a name to a youtube video (I can't even find it). Be specific. The more details the better.
Click to expand...
Click to collapse
Hi Lenny,
thanks for responding
I reposted this in your link, but heres the answer to your question anyways. the exact name of the youtube video is,
(How to Install Android 4.3 Custom ROM on Sprint Galaxy S4!) this video has all the exact files i used on my rooting. I did however use a more updated philz touch recovery. 6.15. something. not sure if that matters or not.
Thanks in advance.
I really need help, my Samsung Galaxy S7 Edge has just got a red screen since i installed a Kernel and i cant use my phone at all.
Any help would be greatly appreciated.
The Kernel I uses was Super Kernel and I also had the Super Man ROM
Thanks A Lot Guys
Just flash stock boot.img from TWRP recovery and you will be fine if you cant get into recovery go to download mode and flash stock firmware with odin
Sent from my SM-G935F using Tapatalk
Why did you flash a kernel? Do you know what a kernel is, and what is does? Do you know how to recover in case things go wrong? Nope, so you should probably do some reading before you decide to modify anything next time.
You probably flashed the "Flat" kernel. Download the Edge kernel and install it.
I always do a nandroid,and back up recovery and boot via Flashify.
Your phone will live.
Sent from my SM-G935F using XDA-Developers mobile app
J.Biden said:
Why did you flash a kernel? Do you know what a kernel is, and what is does? Do you know how to recover in case things go wrong? Nope, so you should probably do some reading before you decide to modify anything next time.
Click to expand...
Click to collapse
he asked for help not a lecture.
simonhcai said:
he asked for help not a lecture.
Click to expand...
Click to collapse
He still needs to do his research and tons of reading
"And on that bombshell!"
Sent from my Gorgeous Echoe driven AEL Kernel Powered G935F
simonhcai said:
he asked for help not a lecture.
Click to expand...
Click to collapse
Do you really think that people are lining up here to help people that have not read a single guide or anything? Do you think people are getting paid helping around here? I'm not giving him a lecture, but it's expected that you know what the F you're doing before doing anything. You must be new around here.
J.Biden said:
Do you really think that people are lining up here to help people that have not read a single guide or anything? Do you think people are getting paid helping around here? I'm not giving him a lecture, but it's expected that you know what the F you're doing before doing anything. You must be new around here.
Click to expand...
Click to collapse
How do you know he hasnt read a single thing?everyone's a noob at some point and if hes made a genuine mistake then maybe asking for help from people who could stop him from ruining his phone which he might have a long contract on,if you know how to help him the time you spent replying you maybe could of solved this problem for him.
simonhcai said:
How do you know he hasnt read a single thing?everyone's a noob at some point and if hes made a genuine mistake then maybe asking for help from people who could stop him from ruining his phone which he might have a long contract on,if you know how to help him the time you spent replying you maybe could of solved this problem for him.
Click to expand...
Click to collapse
He would know how to recover from this if he had done some proper reading. If he isn't even aware what a kernel is, or how to recover, he hasn't been reading, has he? The solution is not to first flash, fail, and then ask questions. Read, read and read, then flash and succeed.
TL;DR: Read.
J.Biden said:
He would know how to recover from this if he had done some proper reading. If he isn't even aware what a kernel is, or how to recover, he hasn't been reading, has he? The solution is not to first flash, fail, and then ask questions. Read, read and read, then flash and succeed.
TL;DR: Read.
Click to expand...
Click to collapse
Basically sums up XDA. Also don't like people who go on spamming "HALP" without posting a logcat (or a last_ksmg in case of kernels) or any other info that could possibly help identify the issue and expecting devs to magically help them. People really need to read this: http://forum.xda-developers.com/showpost.php?p=2031989&postcount=45
Although I would like to add that sometimes it's not totally the user's fault, as many kernel threads don't really provide any information regarding the behavior of the kernel in certain conditions, or the OP of the thread does a poor job at explaining which files to grab or how to flash and whether to wipe any cache partitions (or whatever the post-flash requirements are) or the requirements of the kernel. For example, I installed jesse's kernel and it caused my phone to fail verification on bootup, even when I had dm-verity disabled. Now, people should read the thread before flashing, because there's a possibility that someone else had a certain issue that you may face upon installation, but I feel the OPs should have a section called "Common/Rare Issues" in the thread where user-verified solutions to common/rare problems found when flashing the OP's kernel/ROM are available, so you don't have to search hundreds of pages to find a fix. If you look at the threads of some popular ROMs/kernels, they have one, for the same reason. In my case, I was the first one to face it, so I had to figure out on my own why it happened and find my own fix, that took me a couple of hours. But having such a section saves you time, which is helpful regardless of whether you're capable of identifying the cause of a problem and fixing it yourself or not. I have a "Common problems" section in my app's descriptions for the same reason, because I like to think from the user's perspective as well, plus I don't want my users to be spamming my inbox asking for fixes to common problems, it's more efficient to have a FAQ.
But yeah, READ, UNDERSTAND, LEARN, instead of just expecting people to magically help you with your problems.
Hello !
1. Download Samsung-smart-switch.
2. Install it and run it.
3. Choose more on Top of program and choose the first Part of the menu (intialize software...or so)
4. Follow the instructions on screen and voila .....
YOUR PHONE IS BACK WITH ALL ON STOCK
Hope it helps you