Related
Hi,
Own a 8125/Wizard, and it never vibrated on startup/reboot.
So, my 8925 is annoying the heck out of me when it vibrates on boot!
Any way to disable it? Doesn't seem that a registry hack would process the desired change so early in the HTC startup sequence. (Sorry if this has been asked before -- I couldn't find it in a google/wiki search.)
Thx.
Yes, it has been asked for hundreds times before; and still has no solution. You can always put it (Kaiser) in your shock if you find boot up vibration is annoyed; or you may want to take out the vibrator, too.
I don't find it annoying at all. I find it really informative so in case I turn it off and I accidentally turn it on, if I feel that vibration, I can quickly take out the battery before any sound can come out of the phone.
phi11yphan said:
Hi,
Own a 8125/Wizard, and it never vibrated on startup/reboot.
So, my 8925 is annoying the heck out of me when it vibrates on boot!
Any way to disable it? Doesn't seem that a registry hack would process the desired change so early in the HTC startup sequence. (Sorry if this has been asked before -- I couldn't find it in a google/wiki search.)
Thx.
Click to expand...
Click to collapse
How often do you need to reboot? Other than software installs I rarely need to reboot, is it really that much of an inconvenience?
Nghiem said:
Yes, it has been asked for hundreds times before; and still has no solution. You can always put it (Kaiser) in your shock if you find boot up vibration is annoyed; or you may want to take out the vibrator, too.
Click to expand...
Click to collapse
Put it in my shock?
It was asked before? Sorry -- didn't see anything related, using searches on "disable" and "vibrate" and ("*boot*" or "*start*").
wizzzard said:
How often do you need to reboot? Other than software installs I rarely need to reboot, is it really that much of an inconvenience?
Click to expand...
Click to collapse
In this case, it's an inconvenience. (But if it were preference, would that change the question at all? )
I've been needing to reboot my Kaiser frequently because of a battery drain problem. Reboot triggers the vibrate, which is not helping my low battery situation.
I don't turn off my phone -- I always keep it on (unless it dies as described above), and charge every night. So, I don't need to know when it turns on. The vibrate notification on boot is only wasting battery for me -- even without a drain problem. (But I wouldn't want to permanently disable the vibrate, in case I need vibrate mode once every ~2 months or so, like in a noisy environment.)
Put it like this guys -- was there ever any good purpose for when your computer beeps on boot? Just because it can, does that mean it should? Default should be 'disabled'. Otherwise, HTC should at least provide us with an OPTION to disable! Just like the bios option to disable a computer speaker's beep on boot.
As to battery drain, that's another issue. (If anyone is curious, it's the original 1350 mAh, and it's heating to 108 F using up to 650 Ah. Haven't isolated which app might be doing it. Tried WM5 and WM6 roms. Hard resets. Reflash. Disabled BT, GPS, HSPD, and took all apps off auto-download data. Ordered new 2400 and 1600 mAh batteres, in case my battery is fried.... but I think that's just me being optimistic.)
Computer beeps on Startup
phi11yphan said:
Put it like this guys -- was there ever any good purpose for when your computer beeps on boot? Just because it can, does that mean it should? Default should be 'disabled'. Otherwise, HTC should at least provide us with an OPTION to disable! Just like the bios option to disable a computer speaker's beep on boot.
Click to expand...
Click to collapse
I don't know about the whole vibrate on startup thing as it does not bother me since I rarely re-boot the phone, but the beep on start up on a computer did originally (and possibly still does) serve a good purpose. The beeps were used to convey error codes. For example, on one of my old pc's, 1 beep meant things were ok. two beeps indicated an error in the processor, etc.
I know this was off post... sorry
Hey everyone, I'm trying to upgrade from Myn's Warm Eclair [BETA 1] (I know, I know, lol I should check here more often...) to Incubus26Jc's Super FroYo 2.2 [Deodexed] [RLS10] [7/8/10] (the download link that says "DOWNLOAD RLS10" in large orange font underneath the "What Doesn't Work" secton on his 1st post.
I'm doing what I usually do to install android, which is:
download the .nbh (which is voguimg-240x320-froyo-08-07-10.nbh)
rename it to RUU_signed.nbh
place it in the ROMUpdateUtility
add the ANDBOOT folder to the root of my SD card
placing the androidinstall.tar file inside
holding the power and camera buttons to boot into the RGB 'usb' screen
then running the ROMUpdateUtility to install it and boot up the linux
in linux I hold down the center button to get the the install menu
then install both system and data to the NAND (since I don't have partitions on my 8 gig SD
Here's the problem that I'm running into, once it formats and goes to install it says allot of random stuff then goes through about 15 lines of code saying "no such file or directory exists"
I was wondering if I'm doing something wrong or using the wrong files together.
Any help would be greatly appreciated!
this happens to me all the time. the question you need to ask is "is the device getting to the desktop?" and "is the operating system fully loading to a usable state?"
in my experience answering either of these questions 'yes' puts you in a good position. there have been reports of boot sequence taking up to 20 mins. personally, i can make it to desktop in about 10 mins every time.
hope it helps.
sometimes you just need to format the sd card to fat32 again then try reinstalling after putting the files back on the card of course. if the sdcard is formatted wrong then it wont be able to read the directory and will give you that error
Darkstarrdp said:
Here's the problem that I'm running into, once it formats and goes to install it says allot of random stuff then goes through about 15 lines of code saying "no such file or directory exists"
I was wondering if I'm doing something wrong or using the wrong files together.
Any help would be greatly appreciated!
Click to expand...
Click to collapse
It's not a problem - this is the permission setting - ignore the messages
Just let it get back to the install screen, and then hit Quit or soft-reset device.
Then wait about 10-15 minutes for first boot and go through startup setup
Reboots are quicker, maybe anywhere from 2-4 minutes.
I overclocked my vogue to 496mhz with no issues & I guess some people hit 510mhz safely.
Just to add, Ive been running at 520 for a month now without noticing any major adverse effects...Sorry to chime in
I second wisconsinated's note -- I had this problem last night. I reformatted the card as FAT32 and things went as expected after. Not sure why they tanked in the first place, but I suppose that's not important, right?
ill third that. a reformat of my microsd did the trick.
i think it says on most of the eclair builds that you should just run the installer then let it sit for a good 10 15 minutes and you should be good to go.
ericbond said:
i think it says on most of the eclair builds that you should just run the installer then let it sit for a good 10 15 minutes and you should be good to go.
Click to expand...
Click to collapse
oddly enough, with an experimental operating system, one needs to exercise extreme patience at times.
glad its all in order for you now
Thanks guys, I got it to finally install after the third try, I guess it was just having hiccups trying to install. Everything's good now.... OS installation side at least.
Now I have a different problem... my touch sensitivity is kinda out of whack.
it's like touch screen is dead half the time, on my stock sprint ROM it will work perfectly, but, on the newer builds of android (2.1's) the touch screen won't react most of the time. Like, I'll have to hit the screen over and over a few time's before it'll finally pick it up. I've used the calibration tool to get it all lined up, but when I go to test the calibration I notice that it will only recognize my touch between the .50's and .60's range, it's like it's locked into that area and won't pick up anything else. I also drew a circle around my screen about 10 times once I got it to recognize my pressure and out of the 10 circles 4 or 5 drew a line directly to the bottom right corner of the screen then it would bounce back to where I was actually pressing. It makes it really hard to get anything done on a touch phone if the screen doesn't want to pick up lol.
Like I say, when I move back to my original sprint rom everything is fine and dandy using WinMo 6.1 but who wants to use 6.1 now adays
So, is there any way to fix my touch sensitivity? or is my screen just crapping out on me?
Digitizer going bad
Ok, I've been looking around on the forums, it seems my digitizer is going bad, this is my second vogue (the first one's power button broke). I've only had this vogue for about 8 months so far and I really don't want to pay another $100 dollars to get Asuiron to send me another replacement. So I was wondering if there is any way to salvage my phone, maybe a screen pressure threshold setting within android to help the sensitivity issue?
Is there any way to fix this? Any help would be greatly appreciated! =)
Darkstarrdp said:
Ok, I've been looking around on the forums, it seems my digitizer is going bad, this is my second vogue (the first one's power button broke). I've only had this vogue for about 8 months so far and I really don't want to pay another $100 dollars to get Asuiron to send me another replacement. So I was wondering if there is any way to salvage my phone, maybe a screen pressure threshold setting within android to help the sensitivity issue?
Is there any way to fix this? Any help would be greatly appreciated! =)
Click to expand...
Click to collapse
I am not sure this can help, are you familiar with terminal?
open terminal or adb and type
Code:
cat /sys/module/tsc2003/parameters/sensitivity
to see current setting, it usually is 8192
write it down and change the param to lower value like 3072
Code:
echo "3072" > /sys/module/tsc2003/parameters/sensitivity
check the result
Code:
cat /sys/module/tsc2003/parameters/sensitivity
it should now display 3072
HTH
Although the various Android boot screens are very colorful and exciting I was wondering if it was possible to display the processes being executed during boot instead of the boot animation. If so please post how in this thread!
the Android kernel does not report/print/output its loading status.
Are you sure? If you connect ADB Debugger during booting I can see ton of code whistle by, it's not the same as you'd get with linux install on a PC but could provide quite a nice alternative to boot animation Just need someone to redirect that output to the screen...
.FxN
That would require someone reworking 'ze code that handles boot animations to handle a live stream. Although crazy difficult, it would be awesome if possible.
Old school
The G1 would display a few seconds of code back in the JF ROM days when u went to boot into recovery. It was probably a random fluke occurrence on my end for not holding the home button long enough or something. At that time I was not to Android smart then, if i still had my G1 i would attempt to see if i could replicate it. I may still have some of his ROMs backup up on my server somewhere if someone wants to attempt to prove me wrong lol. I do agree with the OP it would be nice to have a live feed of the boot code instead of the animation.
kaotikking said:
The G1 would display a few seconds of code back in the JF ROM days when u went to boot into recovery. It was probably a random fluke occurrence on my end for not holding the home button long enough or something. At that time I was not to Android smart then, if i still had my G1 i would attempt to see if i could replicate it. I may still have some of his ROMs backup up on my server somewhere if someone wants to attempt to prove me wrong lol. I do agree with the OP it would be nice to have a live feed of the boot code instead of the animation.
Click to expand...
Click to collapse
That was actually just JF calling logcat as soon as it starts booting recovery and quitting when everything was fully loaded... :-(
That would probably be slow as hell... and if it wasn't, you'd never be able to read a single line.
There is a live wallpaper that does this, though. :O
Verbose boot would be pretty cool, in a geeky kinda way. Useless, but cool.
Just looking for opinions. I have a stock note 5, no jail breaking or weird loads. Just a run of the mill Note with way too many candy crush saga apps. We weren't even using it a couple days ago when it turned itself off. Reboot just got it stuck in an endless boot cycle. Loading normal or safe mode gets you the android 'no command' blue screen of death.
I figured maybe bad update...possibly load new firmware. Samsung's smart link application doesn't work, as apparently I don't have a S/N, it doesn't exist and you need that for smart link. (It's not the IMEI.) Anyway, Samsung over the phone told me to try a best buy samsung rep, they'd flash it for free. I thought that sounds safe. But they couldn't get it to recognize my phone....Verizon won't help me, I'm past the year warranty. But still owe too much money to pay it off and get a new one through them...That leaves flashing it myself with Odin. So I did. It went ok, it said it PASSED, the phone rebooted....It started a little config in what looks to be a factory reset type screen...it got to 'erasing', refresh arrow spinning to show me it was going, then it just stops. The world stops and no amount of letting it sit every gets it to go again. Rebooting still has 'no command' and no signs of life.
Any thoughts on what might be going on? Anything else to load or try? The phone's no good to me ****ed, so I'm open to suggestions. Likewise, does it sound like any hardware related things? Is there any hope? would love to hear a first impression from someone more experienced with phones and Android.
Try flashing the latest stock firmware in Odin using "Nand erase all" ticked under options..
Let us know how it goes..
CompuTechnoPro™ said:
Try flashing the latest stock firmware in Odin using "Nand erase all" ticked under options..
Let us know how it goes..
Click to expand...
Click to collapse
Same Problem it looks like. Odin does it's thing for about 3 minutes. Says 'PASS'. Phone restarts, does some initializing bar moving stuff for 10 seconeds, it switches to 'Erasing' then the phone just stops
That's unfortunate dude.
I'm really sick of Samsung phones. They're just terrible. As someone who's had to replace their screen twice and battery three times, it shouldn't be difficult to replace the motherboard.
This happened to my NOTE 5 (SM-N920V) as well
YOUR NOT ALONE! THIS SAME THING HAPPENED TO MY NOTE 5
I was fishing, this morning at about 7am when my phone rebooted all on its own to the same Samsung Boot Logo screen then stuck as well. NO RYHME NO REASON, I have never, ever cracked, hacked or smacked this phone either,:highfive:
"The only updating that has been done has come via Verizon/Samsung..." But none recently ...that I recall as in, the last week or so.
While I will admit doing "it" (hacking,cracking,modding,) to other android phones (Obviously or I wouldn't have a membership here). But this Note 5? No... Maybe perhaps that's why its broken now? LOL...
It does always seem that my continued membership here is not in vain though, ......
For now, I will do whatever it takes to get it back... .......next to buying a new phone or it not coming back on ever.
I will share here what I did to resolve the issue. And I will without a doubt utilize "EVERY" resources here at XDA-DEVELOPERS to do it, and happily without the help of Verizon or Samsung.
So far I have determined that my Note 5 version is not commonly referenced here which is: the SM-N920V (Verizon U.S)
Thank you XDA-Developers this is why we need informational communities like this in our lives! :victory:
Even though I may still go nutz during this repair... if it happens.... Wish us luck!
chroniclogic said:
YOUR NOT ALONE! THIS SAME THING HAPPENED TO MY NOTE 5
I was fishing, this morning at about 7am when my phone rebooted all on its own to the same Samsung Boot Logo screen then stuck as well. NO RYHME NO REASON, I have never, ever cracked, hacked or smacked this phone either,:highfive:
"The only updating that has been done has come via Verizon/Samsung..." But none recently ...that I recall as in, the last week or so.
While I will admit doing "it" (hacking,cracking,modding,) to other android phones (Obviously or I wouldn't have a membership here). But this Note 5? No... Maybe perhaps that's why its broken now? LOL...
It does always seem that my continued my membership here is not in vain, ......as for now, I will do whatever it takes to get it back... .......next to buying a new phone or it not coming back on ever.
I will share here what I did to resolve the issue. And I will without a doubt utilize "EVERY" resources here at XDA-DEVELOPERS to do it, and happily without the help of Verizon or Samsung.
So far I have determined that my Note 5 version is not commonly referenced here which is: the SM-N920V (Verizon U.S)
Thank you XDA-Developers this is why we need informational communities like this in our lives! :victory: Even though I may still go nutz during this repair... if it happens.... Wish us luck!
Click to expand...
Click to collapse
might be bad emmc look into booting from sd card not possible on all devices but may be a start,I had a note 4 do the same thing and most def was bad emmc
Unfortunately, my sd card is internal on the Note5 the unique thing is the Note5 does not have an pop of back plate that covers the battery as, like previous versions which allow the back cover to be removed easily, I mean yeah I can take this thing apart, but its not conventional.
chroniclogic said:
Unfortunately, my sd card is internal on the Note5 the unique thing is the Note5 does not have an pop of back plate that covers the battery as, like previous versions which allow the back cover to be removed easily, I mean yeah I can take this thing apart, but its not conventional.
Click to expand...
Click to collapse
Oh yea and i owned one of these most def not conventional I had mine apart many times.
Mine just shut off one day and wouldn't do anything plugged in or not ended up being the battery
chroniclogic said:
Unfortunately, my sd card is internal on the Note5 the unique thing is the Note5 does not have an pop of back plate that covers the battery as, like previous versions which allow the back cover to be removed easily, I mean yeah I can take this thing apart, but its not conventional.
Click to expand...
Click to collapse
Is there any good way guides on how to find/test eemc or battery or whatever? I can't find many resources at all on how to help me troubleshoot.
Resplendentowl said:
Just looking for opinions. I have a stock note 5, no jail breaking or weird loads. Just a run of the mill Note with way too many candy crush saga apps. We weren't even using it a couple days ago when it turned itself off. Reboot just got it stuck in an endless boot cycle. Loading normal or safe mode gets you the android 'no command' blue screen of death.
I figured maybe bad update...possibly load new firmware. Samsung's smart link application doesn't work, as apparently I don't have a S/N, it doesn't exist and you need that for smart link. (It's not the IMEI.) Anyway, Samsung over the phone told me to try a best buy samsung rep, they'd flash it for free. I thought that sounds safe. But they couldn't get it to recognize my phone....Verizon won't help me, I'm past the year warranty. But still owe too much money to pay it off and get a new one through them...That leaves flashing it myself with Odin. So I did. It went ok, it said it PASSED, the phone rebooted....It started a little config in what looks to be a factory reset type screen...it got to 'erasing', refresh arrow spinning to show me it was going, then it just stops. The world stops and no amount of letting it sit every gets it to go again. Rebooting still has 'no command' and no signs of life.
Any thoughts on what might be going on? Anything else to load or try? The phone's no good to me ****ed, so I'm open to suggestions. Likewise, does it sound like any hardware related things? Is there any hope? would love to hear a first impression from someone more experienced with phones and Android.
Click to expand...
Click to collapse
What you need to do is in Odin options... Uncheck auto reboot. Find the exact .PIT file for your model and put it in odins PIT spot and ignore that it says it's for developers only just add the PIT anyway and in options again where you unchecked auto reboot make sure you check NAND erase all and then add your firmware and after odin flashes it and finally says PASS then disconnect the phone and then hold the volume down button and power button at the same time and when the screens turns off let them go and as soon as it comes back on select nothing but factory reset and when it gets into the recovery mode if it list options and you see factory reset a few lines down use the volume down button to move down to highlight the factory reset option and hit the power button and on the next page again go down to YES and hit the power button again and then let it finish and reboot and least give the phone a good 20 minutes after it's rebooted to get itself setup and to the point where you can start setting it up the same way you did the day you turned it on for the very first time.. Let me know if this works and don't skip any steps.
---------- Post added at 01:55 AM ---------- Previous post was at 01:35 AM ----------
Resplendentowl said:
Is there any good way guides on how to find/test eemc or battery or whatever? I can't find many resources at all on how to help me troubleshoot.
Click to expand...
Click to collapse
The newer Samsung's do not use eMMc they use the newer UFS 2.0 which is why the note 5 and S6 never got micro sd slots. I could be wrong here but I don't think so.
MrMike2182 said:
What you need to do is in Odin options... Uncheck auto reboot. Find the exact .PIT file for your model and put it in odins PIT spot and ignore that it says it's for developers only just add the PIT anyway and in options again where you unchecked auto reboot make sure you check NAND erase all and then add your firmware and after odin flashes it and finally says PASS then disconnect the phone and then hold the volume down button and power button at the same time and when the screens turns off let them go and as soon as it comes back on select nothing but factory reset and when it gets into the recovery mode if it list options and you see factory reset a few lines down use the volume down button to move down to highlight the factory reset option and hit the power button and on the next page again go down to YES and hit the power button again and then let it finish and reboot and least give the phone a good 20 minutes after it's rebooted to get itself setup and to the point where you can start setting it up the same way you did the day you turned it on for the very first time.. Let me know if this works and don't skip any steps.
______________________________________________________________________
Worth a shot.
Where the hell can I find pit files at? why is this **** so obscure on google search. I can't find **** all. It took me forever to find a fireware that appears to work. I'm having no luck finding .pit files
Click to expand...
Click to collapse
Resplendentowl said:
MrMike2182 said:
What you need to do is in Odin options... Uncheck auto reboot. Find the exact .PIT file for your model and put it in odins PIT spot and ignore that it says it's for developers only just add the PIT anyway and in options again where you unchecked auto reboot make sure you check NAND erase all and then add your firmware and after odin flashes it and finally says PASS then disconnect the phone and then hold the volume down button and power button at the same time and when the screens turns off let them go and as soon as it comes back on select nothing but factory reset and when it gets into the recovery mode if it list options and you see factory reset a few lines down use the volume down button to move down to highlight the factory reset option and hit the power button and on the next page again go down to YES and hit the power button again and then let it finish and reboot and least give the phone a good 20 minutes after it's rebooted to get itself setup and to the point where you can start setting it up the same way you did the day you turned it on for the very first time.. Let me know if this works and don't skip any steps.
______________________________________________________________________
Worth a shot.
Where the hell can I find pit files at? why is this **** so obscure on google search. I can't find **** all. It took me forever to find a fireware that appears to work. I'm having no luck finding .pit files
Click to expand...
Click to collapse
What service provider do you have?
Click to expand...
Click to collapse
MrMike2182 said:
Resplendentowl said:
What service provider do you have?
Click to expand...
Click to collapse
the Note 5 in question is a version phone. So n920V. I've honestly googled and opened about 30 ****ty websites, cant find a single one with actual pit files. Just copy pasted generic guides and broken links
Click to expand...
Click to collapse
Resplendentowl said:
MrMike2182 said:
the Note 5 in question is a version phone. So n920V. I've honestly googled and opened about 30 ****ty websites, cant find a single one with actual pit files. Just copy pasted generic guides and broken links
Click to expand...
Click to collapse
Download it from my android file host
.PIT Verizon Galaxy Note 5
Click to expand...
Click to collapse
MrMike2182 said:
Resplendentowl said:
Download it from my android file host
.PIT Verizon Galaxy Note 5
Click to expand...
Click to collapse
Well ****, we're worse off than when we were before. I don't know if this in indicative of a hardware problem, but now that the battery has had time to drain, I plugged it in and left if for a day, but any time the cord is plugged in the phone is stuck in an infinite no command/reboot loop, and I can't get to download mode with up arrow + home + power like I could before. With the phone unplugged it has no life whatsoever.
Could this be a battery issue the whole time?
Click to expand...
Click to collapse
Resplendentowl said:
MrMike2182 said:
Well ****, we're worse off than when we were before. I don't know if this in indicative of a hardware problem, but now that the battery has had time to drain, I plugged it in and left if for a day, but any time the cord is plugged in the phone is stuck in an infinite no command/reboot loop, and I can't get to download mode with up arrow + home + power like I could before. With the phone unplugged it has no life whatsoever.
Could this be a battery issue the whole time?
Click to expand...
Click to collapse
Yes and it sounds like a hardware issue by draining that fast.. Did you try holding the volume down button and power button until it reboots?
Click to expand...
Click to collapse
MrMike2182 said:
Resplendentowl said:
Yes and it sounds like a hardware issue by draining that fast.. Did you try holding the volume down button and power button until it reboots?
Click to expand...
Click to collapse
So When it was plugged in to my comp it would not go into download mode...If I unplugged the cord, it would not turn on.
I got a wall outlet charger instead, with that plugged in I could get to download mode, and when I tried to turn the phone on without the wall charger it gave a 'battery 0%' warning...
Anyway, I got it to down load mode, unplugged the wall charger, moved it to the comp and did the flash with the pit file...Odin said it passed. I restarted the phone, picked factory reset. It installs a few quick things, goes to 'erasing' and after about 20 seconds, freezes, same as last time. Now it's back to no command
Click to expand...
Click to collapse
Resplendentowl said:
MrMike2182 said:
So When it was plugged in to my comp it would not go into download mode...If I unplugged the cord, it would not turn on.
I got a wall outlet charger instead, with that plugged in I could get to download mode, and when I tried to turn the phone on without the wall charger it gave a 'battery 0%' warning...
Anyway, I got it to down load mode, unplugged the wall charger, moved it to the comp and did the flash with the pit file...Odin said it passed. I restarted the phone, picked factory reset. It installs a few quick things, goes to 'erasing' and after about 20 seconds, freezes, same as last time. Now it's back to no command
Click to expand...
Click to collapse
How long did you let it sit there? Do the factory reset again and let it sit there for a little bit and see if it eventually goes. If not boot into recovery again and read to see what version firmware is listed.
Click to expand...
Click to collapse
MrMike2182 said:
Resplendentowl said:
How long did you let it sit there? Do the factory reset again and let it sit there for a little bit and see if it eventually goes. If not boot into recovery again and read to see what version firmware is listed.
Click to expand...
Click to collapse
It kicks itself off and goes to a 'no command' after the erasing screen gets stuck and quits 'twirling' for awhile. I don't know how to see a firmware listing. I can't get to a recovery mode(using that terminology to google some screenshots, I don't have that). The phone boots to maintenance mode only...any option I pick there goes to no command. I can use the vol down + home + power to get into download mode so it will be seen by the pc. That's about it
Click to expand...
Click to collapse
Resplendentowl said:
MrMike2182 said:
It kicks itself off and goes to a 'no command' after the erasing screen gets stuck and quits 'twirling' for awhile. I don't know how to see a firmware listing. I can't get to a recovery mode(using that terminology to google some screenshots, I don't have that). The phone boots to maintenance mode only...any option I pick there goes to no command. I can use the vol down + home + power to get into download mode so it will be seen by the pc. That's about it
Click to expand...
Click to collapse
That means that it didn't flash fully.. What firmware version did you flash in odin? And you can see the phone version again by going into download mode too it should be right at the top after pressing the volume up.
Click to expand...
Click to collapse
I have a Moto G6 XT1925-5 (64GB version) which doesn't want to start up. It's all totally stock, been updated to Android Pie.
It gets as far as the boot animation, and does that for about 2 minutes, then it boot loops and starts all over again. When it bootloops it gets stuck at the first Moto logo screen (not the animated one) for about 3 minutes before carrying on to the boot animation...
This happened once or twice before, we left it overnight and eventually it started up normally. But it's now been five days and it still hasn't started.
I'm not very experienced with Android hacking/modding, etc but willing to try anything. I managed to get into recovery mode and at the top it says (I presume this indicates the firmware version):
motorola/ali_retail/ali
9/PPSS29.55-37-7-6/16c5a7
Unfortunately USB debugging is not enabled. Is there anything that we can do to recover the data that was on the phone before we wipe it - or is there another method we can try to get it to start up? I saw there's a command adb logcat which looks like it might be useful to diagnose the problem but that also requires USB debugging.
Thanks in advance for any suggestions
There is no chance for you to recover your data in this mode.
WoKoschekk said:
There is no chance for you to recover your data in this mode.
Click to expand...
Click to collapse
Thanks for getting back to me so quickly.
There are several other modes available from the bootloader BP Tools, QCOM, etc but I can't work out how any of them are supposed to work.
One question - on the recovery menu, there is an option 'Mount /system'.
I pressed it and it says at the bottom /system mounted, but then there don't seem to be any obvious ways to access anything.
Is there a way to use this to access OS/kernel logs which might give a clue as to what is going wrong?
Thanks again
Step by step...
The first level of the system, which is accessible for you, is called bootloader menu (fastboot menu). From here you can boot into recovery, system, bootloader itself and some other options you mentioned in your post.
None of these options would help you to solve your problem. These are developer's options.
This level is more or less a one way data connection. The main advantage of this menu is to flash single partitions of your device. But there is no way to get a data output of any partition.
In recovery menu you find the options to wipe your data and to mount /system. Mounting /system won't help you, too. This partition doesn't store anything of personal data. It's read only and not writable for anyone. To be honest, nobody knows exactly the meaning of it in this context. Also you won't access any logs from here.
Generally you can't access the system logs. These informations are only buffered data which is cleared with every reboot. The error message of e.g. the kernel log produced by your system when having a bootloop, is only accessible while your device is looping/freezing. The next reboot erases the logs. They aren't stored somewhere on your device. Even for developers it's very tricky to view the log in such cases.
But what would you do if you get the reason for looping? You are not able to access any system partition. You need root user permissions for that. But rooting your phone will erase all data.
Apart from all that your data is encrypted and remains encrypted until you unlock your screen by fingerprint, PIN or password. No chance to get any useful data as a "third person" outside. It would take several years to decrypt it without the matching key for it.
Thanks so much for this detailed explanation, I really appreciate that you took the trouble to answer the questions in detail and explain what the various options are for.
phone5774 said:
Thanks so much for this detailed explanation, I really appreciate that you took the trouble to answer the questions in detail and explain what the various options are for.
Click to expand...
Click to collapse
No problem!
Maybe you'll find some of your personal data in your Google Drive account...
How the story ended
Thought I'd come back and post in case it's useful for anyone else:-
Due to a religious festival, we left the phone switched off for three days. After the festival ended, we switched it on, and immediately it did the same thing that it had been doing all along (spend a long time on the initial boot screen then a while on the boot animation before boot looping). Bizarrely even though it had been off it did not prompt for the PIN code.
We then held the power button as though to turn it off (but for some reason, throughout the usual power button never actually turn the phone off, it always attempted to restart immediately) and then next time it came on it asked for the PIN and started up normally!
So all in all that was a grand total of 9 days after the problem first happened. Very inconvenient not to be able to use it for 9 days, but it's now working again. We haven't dared to try to restart it since!
Some closing thoughts:
The storage is very full (99%), we wonder if that had something to do with this problem
We have now enabled USB debugging and bootloader unlocking to make recovery easier in future
phone5774 said:
Thought I'd come back and post in case it's useful for anyone else:-
Due to a religious festival, we left the phone switched off for three days. After the festival ended, we switched it on, and immediately it did the same thing that it had been doing all along (spend a long time on the initial boot screen then a while on the boot animation before boot looping). Bizarrely even though it had been off it did not prompt for the PIN code.
We then held the power button as though to turn it off (but for some reason, throughout the usual power button never actually turn the phone off, it always attempted to restart immediately) and then next time it came on it asked for the PIN and started up normally!
So all in all that was a grand total of 9 days after the problem first happened. Very inconvenient not to be able to use it for 9 days, but it's now working again. We haven't dared to try to restart it since!
Some closing thoughts:
The storage is very full (99%), we wonder if that had something to do with this problem
We have now enabled USB debugging and bootloader unlocking to make recovery easier in future
Click to expand...
Click to collapse
When I read this last post, I immediately think of a sticky power button, because if you keep holding the power button after the phone has booted it will turn off again, and start up again. And it would also explain the weird behavior you just described of not turning off but rebooting straight away. I'd say: see if you are able to clean de button with a very thin needle or a crafts- or surgical knife around the edges, is might just solve your problem...
mcremco said:
When I read this last post, I immediately think of a sticky power button...
Click to expand...
Click to collapse
Thanks for that suggestion. Interesting, not something I'd thought of.
For now the phone is working perfectly, provided that have to restart it (i.e. we make sure not to shut it down or let the battery run out) but I'll definitely bear this in mind if the issue happens again.
The power button is working normally to turn the screen on or off meanwhile.
Thanks again for your input which is really appreciated.
First time trying to restart after the above
Since posting the above messages the phone has been kept on all the time and not restarted.
Today for the first time we accidentally let the battery run out and the phone shut itself down.
We nervously plugged it in and tried to switch it back on... and it started properly first time, so perhaps the underlying problem was simply that the storage somehow got too full (in the meanwhile we have transferred many photos and other media to the computer and deleted them off the phone to free up space).
Posting this in case it helps someone else experiencing a similar problem.