Related
Hi all!!!
Fist of all Im Not insulting anybody... This is for our BENEFIT.
After some post and time, in XDA general forum Im exposing this problem:
We have too much BRICKED Devices in wizard forums, cause our devices have too DOC CHIP Flash versions inside and the people dont reads enough information, to know where to go and ask whatever they think. So We suggest a solution... when somebody register on the forum it must be some fill spaces about his device like ours... but it is imposible!!! and they are right, the reason is We cant obligate everybody to do this, even if is an important Info to avoid damages.
So... Flar (MOD) told me that we can get a Stickie Thread to let knows to everybody in wizard forums to fill their signature with the information we need to answer their questions, its a great Idea!!!!
So the hope is the last thing to die....
PLEASE EVERYBODY FILL YOUR SIGNATURE WITH YOUR DEVICE INFO
So let me tell you what Info is important to fill in:
Device Model Provided if not in front cover under the battery in the label that say the IMEI and serial (If you want the name that carriers use, I think is not important but i see some people wit his HTC UNIVERSAL using Roms for wizards!!!) BRICKED PDA!!!
IPL and SPL version, provided by a softreset on the second screen(this info is shown on the second splash screen when device boots)
Radio version provided too in the second splash screen (when the phone starts or boot after the softreset under the name GSM!)
OS Version its shown again in the second splash screen (are just number like 1.0.0.0. or something like that)
The Rom you are currently using, Developer and Windows mobile version too, give to the chefs his fame and reputation too!!! they deserve lots of congrats even the ROM is ugly... cause it costs too much than a bricked device. if you have an original ROM please provide the link to it and all the info.
CID/SIM locked or unlocked SuperCID(G3), softSPL or HardSPL (G4) if you never do the unlock process on tutorial... You Are locked!!!
Its important that you read carefully the wiki Cause it has so much informatino like knowing about your DOC CHIPSET G3 or G4 (IPL, SPL can do it too) there is some Faq Manual if you can read a little too.
IF you got any question or suggest PM me you can found ME around Here.
Thanks To all!!!!! and mods to let me put this Stickie on every Topic in wizard forums.
Thanks to all the new members that recah his limits just for revives his devices or upgrade his devices we are here for help y'all.
Thanks to all Seniors, Administrators and Moderators for support our forum...
Im kinda MISS UNIVERSE????!!!!!
See on the upper lever bar of this web it says... USER CP click it and then on the Left bar see the option Signature... to edit your info
Just if you dont know what am I talking about.
I filled mine in a while back, for the same reason you suggest. When someone is talking about a ROM, it's nice to know what they are using.
It is the Meaning!!!
Thanks to support it... Yes you are right thats the reason too. thanks a lot.
There are certainly cases where this could save troubleshooting time; I hope that your thread is educational. However, some of us are clever enough to provide necessary info when seeking help but avoid spamming the forum with a huge signature when it serves no purpose.
No offense intended.
some of us are clever enough
Click to expand...
Click to collapse
if you were clever enough, you wouldnt be saying this ****
No offense intended.
Nice Work Que, Keep it up
done it already
Great idea, I ALWAYS thought this should have been right under a poster's
name and FORCED to be filled out just like your user name and password.
This will make things easier for most people. Although, I wish some people who get right of those giant signature pictures! Shameless, self-promotion SORRY, I voted for you to go to hell in the poll anyways!
Hahaha!
Great idea
I see it!!!
Go to hell 2 votes!!!
FUNNY!!!
Yes it is not crap info... so maybe when you get in troubbles maybe not in he same day you can take back functional your device... so let me save your name to obligate you to give us your info when you were in troubbles...
Its necessarly but no obligate I'm ok with forum rules so... do it. its for our benefit as I said. Keep our devices happy and functional Srs.
Thanks for the effort to all. Really apreciated.
An example...
I like my siggy as it is, however, if I have issues, I make certain I give ALL necessary info. Some who come here don't always realize that this info, whether listed in the thread posting, or in their siggy is vital for us to be able to help them. I don't think it should be REQUIRED in the siggy, but do absolutely agree that it needs to be put in the post!!
For those new to xda...an example of how to post for help without device specifications in the siggy...
TITLE- Bricked phone after spilling coffee on it (don't just say Help, bricked phone, give us a brief insight)
THREAD POST- Help I bricked my phone and am freaking out! I have a Wizard with IPL/SPL 2.26 (insert your info, found when booting, or in settings) and am running a custom rom by NTS--Jag 3.1 (insert name and chef of your custom rom, or tell us if it is stock). My radio is 2.37 (insert your radio, again found when booting or in settings). I spilled coffee on my device after dropping my phone and my coffee when I caught my significant other making out with our dog AND my best friend...or whatever you did to brick your phone. I have taken these steps to fix it...first I kicked my significant others ass, then I kicked my best friends ass, next I cried, then I prayed really hard that my phone wasn't dead, finally I tried to hard boot it...but it will not even go to the tri-color boot screen (insert steps you already took to remedy issue, and results you got from your actions). Am I screwed? Thank you in advance for your help.
PS- if you bricked your Wizard trying to install a custom rom...DID YOU UNLOCK YOUR DEVICE FIRST USING DIRECTIONS GIVEN IN STICKIED THREAD??? We need to know this info too, if it pertains to your devices issue.
OR---List your device specifications in your siggy before posting. Either way, we need to know this stuff if we are going to help you.
Yes but you are Senior
akashastrega said:
I like my siggy as it is, however, if I have issues, I make certain I give ALL necessary info. Some who come here don't always realize that this info, whether listed in the thread posting, or in their siggy is vital for us to be able to help them. I don't think it should be REQUIRED in the siggy, but do absolutely agree that it needs to be put in the post!!
For those new to xda...an example of how to post for help without device specifications in the siggy...
TITLE- Bricked phone after spilling coffee on it (don't just say Help, bricked phone, give us a brief insight)
THREAD POST- Help I bricked my phone and am freaking out! I have a Wizard with IPL/SPL 2.26 (insert your info, found when booting, or in settings) and am running a custom rom by NTS--Jag 3.1 (insert name and chef of your custom rom, or tell us if it is stock). My radio is 2.37 (insert your radio, again found when booting or in settings). I spilled coffee on my device after dropping my phone and my coffee when I caught my significant other making out with our dog AND my best friend...or whatever you did to brick your phone. I have taken these steps to fix it...first I kicked my significant others ass, then I kicked my best friends ass, next I cried, then I prayed really hard that my phone wasn't dead, finally I tried to hard boot it...but it will not even go to the tri-color boot screen (insert steps you already took to remedy issue, and results you got from your actions). Am I screwed? Thank you in advance for your help.
PS- if you bricked your Wizard trying to install a custom rom...DID YOU UNLOCK YOUR DEVICE FIRST USING DIRECTIONS GIVEN IN STICKIED THREAD??? We need to know this info too, if it pertains to your devices issue.
OR---List your device specifications in your siggy before posting. Either way, we need to know this stuff if we are going to help you.
Click to expand...
Click to collapse
And you know what happend to this things.... providing the info we can make it faster... isnt it? so read the wizard and upgrade forums... a guy post twice ethe same thing.... what happend to this...?
You know what are you talking about lil monkey!!!
I never filled it in, but now I saw this sticky I filled it...... sounds kinda usefull?
Good!!!
Gwystyl said:
I never filled it in, but now I saw this sticky I filled it...... sounds kinda usefull?
Click to expand...
Click to collapse
very usefull men! you will se the difference.
I agree this is a great thing. But my opinion is that it should be space limitated. Because some users do not have sensitive ratio. And it is always hard to orientate through the posts if signatures are much bigger than the posts itself So i made my signature (because it is very useful), but i made it discreet...
Why my picture its not showing up, Some help pls.
Pic????
kristijan said:
Why my picture its not showing up, Some help pls.
Click to expand...
Click to collapse
Wich Picture men???
on your signature?
on your avatar??????
ask to mods or administrators please... maybe you dont have the correct extension .jpg or gif or bmp... check the file size and dimentions too..
Maybe there is a way to add space in our edit your details page to fill this information.
Then it could be extracted and placed on the title of our posts between out name and the service provider information like this:
+ Que PPC ......................Device Model, etc. ............................Join Date:
Senior Member ................IPL and SPL version ........................Location:
Join Date: Mar 2007 ........Radio version ...................................Sevice provider
Location: Guadalajara ....OS Version ........................................Country
Posts: 772 ......................CID/SIM
........................................The Rom you are currently using
(sorry, had to add the dots to get spacing)
Good point!!!!
but it means redraw the CP... the Post design and it tooks too many time and efforts by the administrators of the site.
And they say it is not highly important for all devices you know some devices dont need to show this info cause is not relevant to ask for something (well I understands that) but is a nice point of view.
Thank you,
I kind of thought it would be a big undertaking now that everything is set up.
my sig would just be too long adding 7 devices with all spec
A friend rooted his phone using the update.zip method and wanted to flash CM7. He tried several times and told me that it would just sit there. 15 minutes later, still nothing. So I told him to swing by and I would have a go. I tried flashing CM7 in CWM and same result. I thought maybe he had a faulty recovery so I tried reflashing in ROM Manager. I noticed two different options for the Captivate; Galaxy S Captivate and Captivate (MTD). I read the instructions on the CM7 thread here and it said to use MTD. He originally used the other one. So I tried to flash the MTD and it gave me an error. Something like this: "Rom manager has been set up to use your existing recovery installation." Nothing happens after that. I try to flash in recovery again and nothing. Then he informs me that he hasn't done a full wipe yet. So I back up his apps, boot into CWM recovery and perform a wipe. The wipe hangs...same as flashing.
So back to stock with Heimdall I go so I can start from scratch and know that anything that is wrong is not due to something he did before and forgot about or anything like that. Clean slate, so to speak. That went well, no problems. Re-rooted, flashed CWM recovery for Captivate (MTD) rebooted into CWM recovery and all operations still hang. What am I missing here? If there is some piece of vital info I am not giving out here, just ask and I'll get right back and answer.
I appreciate any help I can get. And Just FYI, I do not currently have the device with me but I am relaying this thread to my friend who does so he can stop by and answer questions that I can't and try things out himself.
Thanks in advance.
This sounds like one of those "my friend at school has this problem" stories you tell your dad.
boborone said:
This sounds like one of those "my friend at school has this problem" stories you tell your dad.
Click to expand...
Click to collapse
Does it really matter whose phone it actually is? The problem still remains regardless. And yes it is a friend's phone. I'm not sure why you think I would lie about this on an anonymous forum. And if you look at my posts, they are pretty much all in the Thunderbolt and OG Droid forums. I'm simply trying to help a friend out and this thread was a bit of last resort. I guess I should have learned back when I had problems with my wife's phone and posted a help thread on XDA. I got no real help. Just a few people telling me that they never had a problem like mine. I re-posted the same thing in the android central forums and within 20 minutes got real responses and finally someone walked me through fixing the problem one-on-one through G-Talk. If these are the type of responses I get, I'll just repost this there and really get help.
I really do like this forum and a lot of great development happens here but if someone needs help and all members do is take shots at people, chastise them, or flood a thread with frivolous posts, maybe forum admins should consider ridding the site of general help sub-forums.
I am glad you found your issue which could have been solved by reading threads. Oh and XDA doesn't have a general help section. We have General for device news and info. Q&A for questions, Android devoloment for devlopment, accessories for cool phone gear and themes and apps for themes and apps. XDA is not about spoon feeding info to new members. We expect you to put in a good effort to find the info you need. While I understand it can be ruff with all the info around.
Thread closed
Since after rooting my HTC Desire S phone and Installing Custom ROM - Fallout_Evolution_V5.0, Everytime I turn off my phone and start it again It comes on and restart itself, It does not reboot from scratch but does something called HOT RESTART (like when logging off a computer). Also it sometimes freezes. I have tried to check for ROM updates but the but it never goes through. Its not worse than ever, Yesterday my phone when through HOT Restart a million times it took all day and I couldn't even use it. and its been like that for a while now.
Device Details
HTC Desire S
Android 2.3.5 - default
Android 4.03 - Current
Software Number - Fallout Evolution V5.0.0
Device History
Originally Android 2.3.5
Unroot
Locked HBoot and S-ON
Unlocked HBoot and S-ON
Rooted using HTC_QuickRoot_1.1.13_Release
Installed SuperSU
Flashed Custom ROM
Installed Custom ROM - Fallout Evolution V5.0.0
Troubleshooting Attempts
Tried looking for a ROM Update -- Failed
Tried Reducing Startup App -- Failed
Uninstalled Some Apps --- Failed
Removed Battery ---- Failed
Replace Battery ---- Failed
Sent Reports to HTC ---- Failed
Please Can someone Help troubleshoot this Problem?
Please Note: Rude Comments are not Appreciated, Every solution given would be useful for me and many other Users experiencing the same issue, and please be clear and precise. I have searched the forum and did not find a solution to this specific problem, Please help out Kindly.and receive a Thank You Notification
I'm going to report this thread anyway. You asked this in the 'Noob Questions' thread, and then opened your own thread for the same question. That is against the rules of XDA.
Pointless Anwser (Not Accepted)
SimonTS said:
I'm going to report this thread anyway. You asked this in the 'Noob Questions' thread, and then opened your own thread for the same question. That is against the rules of XDA.
Click to expand...
Click to collapse
@SimonTS, If you notice, I said no rude comment and also stade in Bold "be clear and precise", your reply is so pointless to my question. and It was Wise of me to create a new thread in regards to my issue. I initially posted under Noobs Thread thinking I would get a quick response But then I realised they are so many request on his thread and since mine was peculiar and more technical I found it wise to create a new thread for better result.
Moreover, I saw your reply to my Request Under Noobs Thread and you didn't even have a Precise solution for me neither could you help me, and not to even talk of it, You are the only one who did make an attempt to give a solution It seems no one else has knows How to resolve it. Please next time before making comments like this, always think twice and see reasons to ones idea.
Topzturvins07 said:
@SimonTS, If you notice, I said no rude comment and also stade in Bold "be clear and precise", your reply is so pointless to my question. and It was Wise of me to create a new thread in regards to my issue. I initially posted under Noobs Thread thinking I would get a quick response But then I realised they are so many request on his thread and since mine was peculiar and more technical I found it wise to create a new thread for better result.
Moreover, I saw your reply to my Request Under Noobs Thread and you didn't even have a Precise solution for me neither could you help me, and not to even talk of it, You are the only one who did make an attempt to give a solution It seems no one else has knows How to resolve it. Please next time before making comments like this, always think twice and see reasons to ones idea.
Click to expand...
Click to collapse
I don't need to see the reasons behind your double-posting - it is against the rules of XDA. If that is too confusing then that's your problem, not mine.
I did reply to you on the 'Noob' thread with a few ideas, but you didn't bother coming back to say whether any of those things had worked or not - you can't expect assistance if you don't provide information. I didn't have a "Precise solution" (as you put it), because 99.9% of the 'problems' that people report on here are caused by them not reading, not understanding or simply diving in and then regretting it.
In one of the other threads you created (about rooting) you stated
I didnt try HTC Dev bcoz its process was a bit confusing and since They said Quick root does it all I thought.
Click to expand...
Click to collapse
If HTC Dev is too confusing and "They said quick root does it all I thought" then you need to do far more reading - HTC Dev is simple and straightforward.
Yes, it is possible that you have a really, really rare fault that only applies to you because you are special, but it is extremely unlikely. As for developing an attitude with the people who have put many, many hours into helping other users on here and also tried to help you - not a good idea.
You signed up to XDA, asked your questions about rooting and then went off-line for a month. You came back, asked these questions about your strange problem and then disappeared for three weeks. XDA is a COMMUNITY, not a help-desk. If you want to pay me (or one of the other guys who know far more than I do) for us to act as a helpdesk then it's not a problem - the standard industry rates are $120 per hour.
Oh, and as a PS - but I'm sure that you searched and found this - HTC Desire S > Desire S General > FAST BOOT have you tried disabling Fast Boot as a lot of apps really don't like it.
Anyone Here to Help?
Hello everyone,
PLease can someone help me here, Please help me resolve my initial Problem. Please see First Post abovehttp://1.2.3.11/bmi/forum.xda-developers.com/images/smilies/good.gif
Please do not mind SimonTS Post, I created a new thread so as to allow experience and expert developers view and help resolve this issue. I initailly posted in NOOBs Help and Troubleshooting Thread, Not until I realised that there were over 100 threads and request under that forum, which I then realised that my request might not be solved due to the technical difficulties involved and I was right No one except simon was able to reply to it (and yet not solved).
Please Can someone Help me Out Here? Its been 3 weeks without a solution. Thnaks
:fingers-crossed:
Be wise and Be careful
@SimonTS, You clearly are naive and lack some essential skills like Wisdom.
You fail to realise, that some people have got other important work aside from their Phones and their work takes most of their time rather than them toying with their phone. If I did know how to troubleshoot my phone properly, I wouldn't have bothered putting up a post on here. And Yeah, I did get answers from wise and expert people on here but not from you. I Never asked for you to be troubled by my post and is My post aches your eyes then take your eyes off my Post. I do not need you to comment on this post if you do not have anything positive to say in regards to my request and if you're Tired of helping people on this forum kindly remove yourself from it. No one forced you to Help out, you volunteered to willingly and if it upsets you in helping people resolve their query, Like you said
because 99.9% of the 'problems' that people report on here are caused by them not reading, not understanding or simply diving in and then regretting it.
Click to expand...
Click to collapse
then deactivate your account and stop helping. It is called "Customer Friendly and Volunteering". You do not need to act unwisely if someone ask for you help, If you can't help then don't help.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi
1. Hae you tried to reinstall the rom
2. Have you flashed boot.img from that rom ( fallout )
3. Have you tried another rom
4. Do you perform < full wipe > before flashing
5. Have you checked whether your device's battery sits firmly in its place
if there are any movements it is likely to cause reboots
5.may try to update your bootloader and radio to the latest( not directly related but...)
6. You may also try to start from skratch:
- lock bootloader
-flash ics ruu
-unlock bootloader
- flash recovery
-flash superuser.zip ( or a prerooted rom )
Check whether it happens on other drivers ( roms )
try a few...
By the time you'll finish to try all options you'll know whether this is software or hardware issue...
Neither I, nor anyone else, sits next to your phone so only you have a chance to fully test it
Edit: whatever approach of the answers may be,
be certain that we all try to help without any discrimination,
This is a free forum, and the users are ussualy discouraged in demanding anything...
None of XDA members is paid for giving a hand or for their work,
this is free and good will what drives us all here, to learn, share and teach what we know...
this will start a flame war soon. anyway, the members here are helping you. but somehow you are bashing them up their advice. I take it as you are new... people here are generally friendly and knowledgeable. when I bricked my desire s for the first time, it was @SimonTS who helped me got my DS alive and kicking again. just because your issue is more technical, doesn't give you the right to post multiple times. in my few months here, I learnt that this is a dev forum, not a child playground for you to throw tantrums
P. S rooting isn't for you
Sent from my supercharged :tank:
Hi
Let me start by offering you some friendly advice. You are the guy with the one weird problem nobody else seems to have. You are the new member, or 'noob' if you wish. Therefore you would do well to behave in a courteous and non-wise-ass-y manner towards your fellow XDA forum members. You have no rights to demand anything from us, you are asking for our advice and it's only in your best interest to try to get on our good side rather than our bad side.
Now, as for your problem. The most likely reason is that the kernel you're running is incompatible with the modules your ROM is shipping. I.e.: you made a #1 new-user mistake and did not (correctly) flash the boot.img of your new ROM.
A second possibility is that there's genuinely something wrong with either your ROM or your device itself.
To check for both issues at the same time, please do the following:
Reboot your phone
Create a dmesg ('adb shell dmesg') and a logcat ('adb logcat') log
Use your phone until the problem occurs
Immediately after, create a new dmesg and logcat
Post all four logs
Thank you for your co-operation
hisname said:
this will start a flame war soon. :
Click to expand...
Click to collapse
Sadly, you may be right about that...
So now, when our younger member has been given a few pointers,
( moderators seem to be very patient with us this time )
we could draw a thick line under this
and sit back to the table- shall we...
We are all friends here, or should be....
Thanks for your suggestions.
asgardr said:
Hi
1. Hae you tried to reinstall the rom
2. Have you flashed boot.img from that rom ( fallout )
3. Have you tried another rom
4. Do you perform < full wipe > before flashing
5. Have you checked whether your device's battery sits firmly in its place
if there are any movements it is likely to cause reboots
5.may try to update your bootloader and radio to the latest( not directly related but...)
6. You may also try to start from skratch:
- lock bootloader
-flash ics ruu
-unlock bootloader
- flash recovery
-flash superuser.zip ( or a prerooted rom )
Check whether it happens on other drivers ( roms )
try a few...
By the time you'll finish to try all options you'll know whether this is software or hardware issue...
Neither I, nor anyone else, sits next to your phone so only you have a chance to fully test it
Edit: whatever approach of the answers may be,
be certain that we all try to help without any discrimination,
This is a free forum, and the users are ussualy discouraged in demanding anything...
None of XDA members is paid for giving a hand or for their work,
this is free and good will what drives us all here, to learn, share and teach what we know...
Click to expand...
Click to collapse
Thank you @asgardr , When I rooted my HTC Desire S, I followed this guide ( http://forum.xda-developers.com/showthread.php?t=1525100) posted by @n0elite. It was simple and easy and I did flash the boot.img, I have checked the battery and even changed my battery it is certainly not the battery fault. Although, I haven't tried to reinstall the ROM because I didn't want to follow the same guide in case something was missing in it. I have also tried reading other threads on here but I am not sure of which Guide to follow because I came across some negative comments on it. I haven't tried another ROM yet and thats because I do not know of any Updated ROM and most people seem to say the "Fallout v5.0.0" is most recent.
However, I have tried to find an update on the fallout but haven't found one, I also have SuperSU installed but I don't know how to tweak it and therefore haven't tampered with it so as not to cause damage to my phone. I know some losers on here would say why didn't I try any of these or make any attempt to. Well my reasons are well best known to me, I lost some data on my last rooting even though I tried backing up all my data, some of my previous apps failed to work and I lost previous progress on some of my important work in which i was working on due to compatibility issues. Therefore, I am trying to thread carefully and make my research and findings before making any attempts on my phone or I could loose the all phone all together.
I do appreciate your solutions and clicked on the thanks button because only you have been sensible and helpful on this matter and precise without going of point and being rude and insultive.
TO others
@Aquous You have no rights to demand anything from us, you are asking for our advice and it's only in your best interest to try to get on our good side rather than our bad side.
Click to expand...
Click to collapse
Please not I wasn't demanding anything from you, I asked The XDA-developers Forum and no one is bragging rights with you. anyways thanks for your suggestion.
@hisname, this will start a flame war soon. anyway, the members here are helping you. but somehow you are bashing them up their advice. I take it as you are new... people here are generally friendly and knowledgeable. when I bricked my desire s for the first time, it was @SimonTS who helped me got my DS alive and kicking again. just because your issue is more technical, doesn't give you the right to post multiple times. in my few months here, I learnt that this is a dev forum, not a child playground for you to throw tantrums
P. S rooting isn't for you
Click to expand...
Click to collapse
I am a web Designer, and Yeah rooting is not my field so Why force it on me, and If my multiple post disturbs you, why didn't you reply to the my initial post?
Thanks once again @asgardr:good:
asgardr said:
Sadly, you may be right about that...
So now, when our younger member has been given a few pointers,
( moderators seem to be very patient with us this time )
we could draw a thick line under this
and sit back to the table- shall we...
We are all friends here, or should be....
Click to expand...
Click to collapse
@asgardr, Thanks for your humble attitude, Exactly what is expected from all users, Humble and friendly approach. Please can you recommend to me any Custom ROM and Recovery that is very at least 90% or more efficient and most up to date? as I shall try what all your suggestions again. Thanks.
After unlocking bootloader installing recovery, rooting,.....
flashing a custom rom is a matter of rebooting into recovery, flashing the rom.zip
and afterwards boot.img via fastboot- that's all you'd need to do...
Redownloding and reflashing the rom again
( after wiping clean all partitions-in recovery )
very often corrects some errors and bugs, happening within the system,
after the first flash...
This is the link to the kernel thread,
( sense4_boot.img , as well supports fallout rom)
http://forum.xda-developers.com/showthread.php?t=1845039
which may also be an option on the way to resolve this
rather rare device's malfunction
Edit: 4ext recovery is said to be most efficient for our device.
I'am still using clockworkmod touch 5.8.1.5 though, and all is fine on my end....
Most of the time, my device's daily drivers including htc sense in it are:
-ViperSaga ( sense 4.1 full )
-DesireXS ( sense 4.1 lite )
-Endymion 3.5 ( almost perfect- my favorite for a very long time )
These roms are my personal choices...
but, to tell the truth, I did not try every single one from the whole array,
so, among others available, one still may find very nice surprise....
@Topzturvins07 I'm not sure if you are just insanely stubborn or not, but at the same time as I originally reported this as a duplicate thread, I posted a reply to you in the 'Noob Thread' as below;-
Verify the checksum of the ROM first. Carry out a full wipe and reflash, try running with no apps installed and see if the problem still happens.
Disable 'fast boot' from the settings.
Try a different ROM, although I have no problems with Fallout on my old DS.
Make sure you haven't installed any task-killers.
Describe better what actually happens and what you see on screen.
Just a few suggestions.
Click to expand...
Click to collapse
You never bothered to reply to my post and provide more information. The only real description you have given of the problem is (probably because you are not a techie person) very vague and unhelpful. I have worked in customer support and consultancy for 20 years now and the biggest problem when you can't actually see the problem for yourself is trying to get a user to describe exactly and precisely what is going on.
If you want to ask for help then you need to answer the questions that are asked of you by the very people whose help you desire. Communication requires two-way talk, and you will find that the people willing to help on here do not ask questions simply for the fun of it.
Topzturvins07 said:
why didn't you reply to the my initial post?
the reason is simple, you don't deserve it
Click to expand...
Click to collapse
Topzturvins07 said:
Please not I wasn't demanding anything from you, I asked The XDA-developers Forum and no one is bragging rights with you. anyways thanks for your suggestion.
Click to expand...
Click to collapse
Very well, if I misread you I humbly apologize. Writing isn't the easiest medium to convey emotions
Now, if you could post those two dmesg and logcat logs I asked for? I am confident they will shed more light on where exactly your issues come from.
LOG Report
Aquous said:
Now, if you could post those two dmesg and logcat logs I asked for? I am confident they will shed more light on where exactly your issues come from.
Click to expand...
Click to collapse
Well despite not knowing how to generate the Logcat and dmesg, I was able to get a guide from @blindndumb and I came up with loads of Junks I can't interpret. You'll find in attach three txt file,
one is the :
dmesg.txt
logcat1.txt (before sudden logoff)
logcat2.txt (after the first sudden logoff)
logcat3.txt (after the second sudden logoff)
Please help yourself, because I cannot interpret what is produced.
Well, this is peculiar. I was expecting to see loads of '<service> has died' errors in your logcat, because that is usually the cause of a spontaneous hot restart. Your logcat actually looks rather normal.
Was the dmesg log taken directly after a hot restart?
Also, could you please reboot your phone and take another dmesg immediately after the system has finished loading? I'm mostly interested in the log of the boot-up, which has unfortunately been completely overwritten by a slur of error messages (which are completely normal by the way, it's the result of a debugging option that's enabled in the stock kernel sources and the guy who compiled your kernel probably forgot to turn that off).
Aquous said:
Well, this is peculiar. I was expecting to see loads of '<service> has died' errors in your logcat, because that is usually the cause of a spontaneous hot restart. Your logcat actually looks rather normal.
Was the dmesg log taken directly after a hot restart?
Also, could you please reboot your phone and take another dmesg immediately after the system has finished loading? I'm mostly interested in the log of the boot-up, which has unfortunately been completely overwritten by a slur of error messages (which are completely normal by the way, it's the result of a debugging option that's enabled in the stock kernel sources and the guy who compiled your kernel probably forgot to turn that off).
Click to expand...
Click to collapse
I have tried a couple of time to catch all the logcat report but there seem to be a million lines of logs immediately I start the phone and they all run within a blink of an eye, and my CMD cannot hold back so many. The ones you see is what I could retrieve but I could try changing the properties of my cmd and see if I can catch more of it.
I believe a relative attempted to install via oden, A Verizon based module on this phone using odin. I am so unlearned about the android os that I do not know the terminology even to use here. Not complaints but just info, I am now victim to two arsons and thus homeless and rebuilding and so little time this is first chance I have had to post about this in some time.
I am not very adept at finding articles here so would appreciate any help any can provide.
I wish to and will learn all there is to know about Android some time in future and will master most of it except programing.
For now any help with any post or articles or what have you would be appreciated as well as any live help should someone so care to provide
You are welcome to PM or email me as well. [email protected].
If I am allowed to post this, I would consider paid help as well. If not allowed to post any part of this or if in wrong area, please help me correct my actions.
Thank you all in advance.
Gh / Charlie
GH
Gladhatter said:
I believe a relative attempted to install via oden, A Verizon based module on this phone using odin. I am so unlearned about the android os that I do not know the terminology even to use here. Not complaints but just info, I am now victim to two arsons and thus homeless and rebuilding and so little time this is first chance I have had to post about this in some time.
I am not very adept at finding articles here so would appreciate any help any can provide.
I wish to and will learn all there is to know about Android some time in future and will master most of it except programing.
For now any help with any post or articles or what have you would be appreciated as well as any live help should someone so care to provide
You are welcome to PM or email me as well. [email protected].
If I am allowed to post this, I would consider paid help as well. If not allowed to post any part of this or if in wrong area, please help me correct my actions.
Thank you all in advance.
Gh / Charlie
GH
Click to expand...
Click to collapse
Hi,
Here is a thread on returning your device to stock with Odin, http://forum.xda-developers.com/not...mware-firmware-kernel-modem-recovery-t2942937
And as far as wanting to learn about Android and the things found on XDA, my only advice is to read read read. There is a lot of info out there, just search on terms or procedures you are curious about and read through the search results.
For your device, you can start with this thread to learn more about it... http://forum.xda-developers.com/note-4-verizon/general/guide-to-note-4-wip-t2939288
You can ask questions there as well!
Good luck!
Ty, Darth. Sorry for my noobness. I cannot seem to locate in the reccomended thereds, any thing about USCelluar phones or any link to any Rom, Kernal or what ever it is called. I do now know odin was improperly used and possibly a verizon upload was made to the phone and then on panic odin was ran and all possible options tried like flash tlock partition and any other options except pit.
I have not a clue where to start to fix it. I have been reading but if I seen any possible solutions, I missed them. Can someone please point me to some factory iriginal files for the USC NOTE 4 and some knowledge of how to use them? If some other files would work, where verizon or what have you, glad to try that to. The phone in question has never been on line or assigned any phone number since new. Not sure that matters. I do not mind messing it up further or experimenting to learn or help devs if any needed.
Thanks
Gh
I suggest then asking about your device here, http://forum.xda-developers.com/note-4/help/noob-friendly-question-t2866810
But I will tell you... Reading and research is a part of this hobby. Without doing a lot of that, people end up with big problems usually.
Here is the main note 4 section, I recommend reading through some of the sticky threads in the general and Q&A sections. Those are the threads at the top with a thumb tack symbol beside them. :good:
http://forum.xda-developers.com/note-4
After you've read up and know a little more, then I'd worry about roms and whatnot. And any further questions can be asked in the first thread I linked in this post.
Good luck again!
I am confident in only big solutions. I thank you for your kindness and patience. I am only sorry that I do not know a rom from a kernal or a brick for now. I regret, I am not smart enough as well to follow the links so well or derive from then when I can. I do have unbreakable tenacity however and never lose a war due to it. The outcome for me is obvious but the time frame not so nice to me as I will not have time to read much for some months and now seek a quuick fix for a quick fix of feeling human again, for now. Any advise for a direct link to some adb and fast boot drivers? Seems this may be the sutipn and not odin for now. Seems I need to get what ever the file is called into the phone or files to recover to as mine goes to recovery every time but then losds the bum files it has stired. Would be nice to know how to idenify the files but all in good time.
You will need to ask in the threads provided. Xda Assist is here to help navigate the site, not for support.
If you have no time to read, and want things done quick, then I suggest to you that your heading down a risky path... And your device could suffer.
Also, XDA is a place to learn and share... Without doing your part here, meaning reading, you will have trouble getting people to help.
Thanks, and thread closed.
Hello Everybody, I'm new to this specific site so I apologize in advance if I posted this in the wrong forum section. I have a OP7P that I was running BlissRom. Today I decided to check out the EX kernel app. After installing. There was a pop-up that said "There is an Kernel update would you like to update mow, so I accepted and it asked me to reboot, like always after a system flash. And it's boots into Fastboot. I tried everything from Selecting Start to selecting recovery. To holding Vol and power buttons and Fastboot is where it goes no matter what. So I said at least it's in Fastboot. I'll just reflash the TWRP img file. Then. I noticed I was in trouble when my PC didn't detect the device at all. I plugged another device into the cable to make sure the cable was good and it was. So I ran Fastboot devices command and No devices detected rebooted it back into Fastboot. Tried it again and same thing. Someone please tell me I'm not totally screwed. I've bricked phones on a few occasions and always have gotten them back. This is my personal device. Fingers crossed my kids didn't just get a new frisby. Thanks everyone in advance!
kbs3251 said:
Hello Everybody, I'm new to this specific site so I apologize in advance if I posted this in the wrong forum section. I have a OP7P that I was running BlissRom. Today I decided to check out the EX kernel app. After installing. There was a pop-up that said "There is an Kernel update would you like to update mow, so I accepted and it asked me to reboot, like always after a system flash. And it's boots into Fastboot. I tried everything from Selecting Start to selecting recovery. To holding Vol and power buttons and Fastboot is where it goes no matter what. So I said at least it's in Fastboot. I'll just reflash the TWRP img file. Then. I noticed I was in trouble when my PC didn't detect the device at all. I plugged another device into the cable to make sure the cable was good and it was. So I ran Fastboot devices command and No devices detected rebooted it back into Fastboot. Tried it again and same thing. Someone please tell me I'm not totally screwed. I've bricked phones on a few occasions and always have gotten them back. This is my personal device. Fingers crossed my kids didn't just get a new frisby. Thanks everyone in advance!
Click to expand...
Click to collapse
https://forum.xda-developers.com/oneplus-7-pro/how-to/msm-tool-guac-t3934691
As many thorough threads for unbricking this device that people invested a lot of time to make 100% idiot proof we somehow keep getting these same cry for help post SMDH
mookiexl said:
As many thorough threads for unbricking this device that people invested a lot of time to make 100% idiot proof we somehow keep getting these same cry for help post SMDH
Click to expand...
Click to collapse
Kind of ignorant to be calling people idiots when they follow the same process theybalways have to update their ROM and things go south. Not every method works for the same device.
If you're not going to help, don't comment.
OP, check out my thread. I had something similar happen to me last week.
https://forum.xda-developers.com/oneplus-7-pro/help/issues-rooting-oneplus-7-pro-installing-t4094885
knightsriot said:
Kind of ignorant to be calling people idiots when they follow the same process theybalways have to update their ROM and things go south. Not every method works for the same device.
If you're not going to help, don't comment.
OP, check out my thread. I had something similar happen to me last week.
https://forum.xda-developers.com/oneplus-7-pro/help/issues-rooting-oneplus-7-pro-installing-t4094885
Click to expand...
Click to collapse
Never called anybody idiot brother and if you are older than twelve you should be familiar with the terminology and context of which I used idiot proof. Rather than giving answers that can be easily found why not promote the use of the search function? If we continue to just give answers these forums will continue to be full of meaningless space keeping threads like this one that only point you to another thread while the useful information gets pushed out.
There's a reason we didn't make all A's from teachers giving us all the answers or you don't just tell you're kids to listen to you count to 100 or sing the ABCs and it's because we wouldn't learn jack ish. Your reply was less helpful than mine. I stated that the threads were available hoping the OP attempts to use the search feature to find them. You just made the most useful tool (SEARCH) obsolete.
mookiexl said:
Never called anybody idiot brother and if you are older than twelve you should be familiar with the terminology and context of which I used idiot proof. Rather than giving answers that can be easily found why not promote the use of the search function? If we continue to just give answers these forums will continue to be full of meaningless space keeping threads like this one that only point you to another thread while the useful information gets pushed out.
There's a reason we didn't make all A's from teachers giving us all the answers or you don't just tell you're kids to listen to you count to 100 or sing the ABCs and it's because we wouldn't learn jack ish. Your reply was less helpful than mine. I stated that the threads were available hoping the OP attempts to use the search feature to find them. You just made the most useful tool (SEARCH) obsolete.
Click to expand...
Click to collapse
Could've just used fail-proof or other terminology, Hulk Hogan. No need to be passive aggressive to people are getting the hang this device.
This is the first time I've triggered a neckbeard. Nice.
knightsriot said:
Could've just used fail-proof or other terminology, Hulk Hogan. No need to be passive aggressive to people are getting the hang this device.
This is the first time I've triggered a neckbeard. Nice.
Click to expand...
Click to collapse
Lol I'm just frustrated to not be able to help . I check the questions and answers regularly to see if I can assist someone but the questions and answers forum is only filled with "Bricked" threads of which non are unique to anything posted in the Mega Unbrick and MSM Tool thread. I've had about every Bricked situation possible for this device and never once had to create a thread or even ask a question in a thread because I know the power of search. This device will always Unbrick as long the mother board isn't fried.
That Hulk Hogan was nice ?
mookiexl said:
Lol I'm just frustrated to not be able to help . I check the questions and answers regularly to see if I can assist someone but the questions and answers forum is only filled with "Bricked" threads of which non are unique to anything posted in the Mega Unbrick and MSM Tool thread. I've had about every Bricked situation possible for this device and never once had to create a thread or even ask a question in a thread because I know the power of search. This device will always Unbrick as long the mother board isn't fried.
That Hulk Hogan was nice
Click to expand...
Click to collapse
True. Nah, I'm just coming from OP's point of view. I've rooted my tablet and other phones and have never come close to bricking a device besides this one. I got all the way down to the Qualcomm crash dump message. I was so frustrated. All I did was literally download an update ROM build and applied it the exact same way I had the previous build, but something messed up along the way. I tried different methods til I finally found that All-in-One tool. I tried all the others and they didn't work for me.
Anyway, my bad for being rude. I know I'm not dealing with the typical YouTube type of people here
SMH.
mookiexl said:
As many thorough threads for unbricking this device that people invested a lot of time to make 100% idiot proof we somehow keep getting these same cry for help post SMDH
Click to expand...
Click to collapse
I literally said that I'm new to XDA and I'm not apart of any other forums or websites, and for one I looked up unbricking this device. None of them had an issue with their computer detecting their device in Fastboot mode. Therefore I reached out for help. The real problem is that people are so bored and have nothing to do that they just complain about other people's threads. What's the point in having a forum on this subject if you can't use it without dealing with this **** I could have done without a smartass response. If you missed the part where I stated that the USB-C port was not functional in Fastboot mode. Then please read my entire thread before adding input. I see your a senior member. I respect that and you probably have tons of knowledge that could be useful. So you should want to encourage instead of downgrade people for their questions. This hobby is slowly dying. Help the younger crowd. Theyre gonna be afraid to ask questions if they feel the experienced guys are gonna make them feel stupid. No disrespect I just didn't see the point in your response and with my bricked device having something uncommon from the other threads. I still feel that my question was a valid ask for help
Thanks!
Thanks Knightsriot
mookiexl said:
As many thorough threads for unbricking this device that people invested a lot of time to make 100% idiot proof we somehow keep getting these same cry for help post SMDH
Click to expand...
Click to collapse
knightsriot said:
Could've just used fail-proof or other terminology, Hulk Hogan. No need to be passive aggressive to people are getting the hang this device.
This is the first time I've triggered a neckbeard. Nice.
Click to expand...
Click to collapse
knightsriot said:
True. Nah, I'm just coming from OP's point of view. I've rooted my tablet and other phones and have never come close to bricking a device besides this one. I got all the way down to the Qualcomm crash dump message. I was so frustrated. All I did was literally download an update ROM build and applied it the exact same way I had the previous build, but something messed up along the way. I tried different methods til I finally found that All-in-One tool. I tried all the others and they didn't work for me.
Anyway, my bad for being rude. I know I'm not dealing with the typical YouTube type of people here
Click to expand...
Click to collapse
.
I'm glad there's still people out there who are willing to help. Update on the problem. I got frustrated with it and went to bed. It died overnight and when I plugged it in the next morning by the grace of God it decided to boot into TWRP 3.3.1-79. Where I had done a backup a few days prior! ?. I do have another quick question. I'm back on stock OOS 10.3.2 running renovate Ice. How come none of the changes I make in the rice tweaks app will actually change. None of them. Sorry in advance if this is a "stupid" question
kbs3251 said:
.
I'm glad there's still people out there who are willing to help. Update on the problem. I got frustrated with it and went to bed. It died overnight and when I plugged it in the next morning by the grace of God it decided to boot into TWRP 3.3.1-79. Where I had done a backup a few days prior! . I do have another quick question. I'm back on stock OOS 10.3.2 running renovate Ice. How come none of the changes I make in the rice tweaks app will actually change. None of them. Sorry in advance if this is a "stupid" question
Click to expand...
Click to collapse
Search the RICE thread for the ''overlay mount fix''. Its a magisk module.
---------- Post added at 05:16 PM ---------- Previous post was at 04:27 PM ----------
kbs3251 said:
I literally said that I'm new to XDA and I'm not apart of any other forums or websites, and for one I looked up unbricking this device. None of them had an issue with their computer detecting their device in Fastboot mode. Therefore I reached out for help. The real problem is that people are so bored and have nothing to do that they just complain about other people's threads. What's the point in having a forum on this subject if you can't use it without dealing with this **** I could have done without a smartass response. If you missed the part where I stated that the USB-C port was not functional in Fastboot mode. Then please read my entire thread before adding input. I see your a senior member. I respect that and you probably have tons of knowledge that could be useful. So you should want to encourage instead of downgrade people for their questions. This hobby is slowly dying. Help the younger crowd. Theyre gonna be afraid to ask questions if they feel the experienced guys are gonna make them feel stupid. No disrespect I just didn't see the point in your response and with my bricked device having something uncommon from the other threads. I still feel that my question was a valid ask for help
Thanks!
Click to expand...
Click to collapse
Dude all I'm saying is search is the key. Note that I still helped just not the way you wanted. I don't have over 300 thanks for nothing.