Related
Hello XDA forum! I am new here but I have enjoyed reading through many of the great posts you have available. I have a problem and I'm hoping you can help me. I'm learning quite a bit about the android OS and dabble in some minor tablet repairs but I still consider myself a noob, especially after reading some of the more technical posts! I have a couple of tablets here that are locked up after too many pattern attempts and I'd like to do a factory reset, but I just can't seem to get them into recovery mode. All the normal keystrokes yield no results. For example:
Tablet 1 is a 7" Noria by Chromo that identifies by my computer MID-X15. It's recognized in device manager as being installed with correct drivers. To the best of my knowledge USB debugging is not activated as I have tried both Multi Tools and platform-tools adb, while the device is not shown on either program. I have also tried numerous different key combinations from a powered-down state (vol - & vol + with power, just vol + and power, just vol - and power, and repeatedly pressing different combinations both at and before the manufacturer splash screen). The internet has proven to be less than helpful as I'm on my 3rd hour of forum surfing. I have never flashed a tablet before and I'm not precisely sure if can be done without USB debugging on or without being able to access the system. I am perfectly willing to purchase a TF card and attempt the process but there's not a ton of information about this relatively obscure little tablet.
Tablet 2 is a Klu by Kurtis. It is also a 7" tablet and I have the same problems with the USB debugging being off. On this device I can get into the screen with the android on his back with the red exclamation mark, but the recovery console never starts. Numerous hours of surfing and countless attempts at alternate keystrokes have also yielded no results.
If someone would be so kind as to offer a few suggestions or point me in the correct direction I would seriously appreciate it. Thank you so much!
(close to) 24 hour bump. Hopefully someone may have a suggestion for me. Thanks in advance!
One more bump. Anyone?
Unfortunately, after researching both tabs, I have found that neither tablet is very good quality.
Chromo Noria - This is a very well-known tablet to be problematic for no reason at all, and once this problem occurs, nobody has discovered how to retrieve the system.
Curtis KLU - This also is not the greatest tablet ever. Fortunately, I've found this thread for you to take a look at - it contains instructions on how to boot ClockworkMod.
Hope this helps.
Thank you for the link, thenookieforlife3! I will read over that and give it a shot. I realize these tablets are virtually worthless. It's one reason I don't mind experimenting on them with some more aggressive techniques if any exist. The biggest problem is just getting into the darn things to do anything (aggressive or not, lol). Perhaps something in that thread will give me a technique I can use.
I'm still open for other suggestions as well. These are throw-aways so I'm willing to get creative. I'm wishing there were jumpers or, heck, a couple traces i could short out with a screwdriver to force it back to a factory setting, lol.
[email protected] said:
Thank you for the link, thenookieforlife3! I will read over that and give it a shot. I realize these tablets are virtually worthless. It's one reason I don't mind experimenting on them with some more aggressive techniques if any exist. The biggest problem is just getting into the darn things to do anything (aggressive or not, lol). Perhaps something in that thread will give me a technique I can use.
I'm still open for other suggestions as well. These are throw-aways so I'm willing to get creative. I'm wishing there were jumpers or, heck, a couple traces i could short out with a screwdriver to force it back to a factory setting, lol.
Click to expand...
Click to collapse
I can see that. It's always fun to be aggressive every once in a while.
Don't we all wish that there was a hardware method to factory restore our devices? :laugh:
Am I right?
I too have been tinkering with a chromo noria 7" tablet in my spare time, as my son got one of these last christmas and its been stuck in a boot loop for no reason for almost six months now. Today I decided to play and discovered that adb could see it while it was boot looping and tried adb reboot recovery command and to my surprise it booted the recovery menu. That being said, does anyone know what I can flash from there cuz a wipe/factory reset does not fix the loop. Any advice would be happily welcome and im sorry if I'm posting wrong in any way. Hope at least my findings are helpful.
Sent from my Moto G using XDA Free mobile app
Hi,
I realize many of you will state this has been asked before but I really can't find a fix for the phone so I thought maybe it's best to ask my own question and describe the issue.
So I work in a small company dealing with recycled mobile phones. I've been there about a year and a half, I had no training as it was just me and another guy, so it was just google and a lot of help from this site, so thanks guys for all the great help as I've got most of my answers from previously asked questions. I'm not a complete noob, but still have lots to learn.
This question I will keep related to the Moto G. So in my company we managed to pick up around 20 Moto G XT-1032. However around 6 of them seem to have software issues, after a factory reset (after testing) 6 got stuck on a boot loop. So I searched around and found 'http://forum.xda-developers.com/showthread.php?t=2542219' which I followed and managed to flash the software back to 4.3, I had issues on an XP computer but after trying with a windows 7 it seemed to work and the phone booted up. The 6 which got stuck in a boot loop had previously been factory reset as I could see it was at the factory set-up when I turned them on. So I was quite confused why 6 would get stuck.
So today I actually finally figured out to move to a windows 7 laptop which allowed me to actually flash the phones. After flashing the phone back to 4.3 I tested the phone and all seemed fine, so as these are to be sold I had to factory reset them again (resetting through the standard settings, no special code). So once again they all seemed to get stuck in a bootloop, but instead of an actual bootloop it shows the Motorola logo and then the screen goes black but I can see the backlight is still on, then it just sits there as long as I leave it, over 4 hours so far.
I have attempted a second flash on one of the phones and it's done the same. I'm downloading UK firmware for the xt1032 not the dual sim version. I've held the power button for 120 seconds as someone mentioned that on some random thread. Managed to get to restart and got into the android bios thingy (not sure what it's actually called, hopefully you'll understand what I mean) and attempted a factory reset but it just gets stuck on the black screen (still can see the backlight is on).
I'm now out of ideas, I really don't know what else to try. I'd really appreciate if someone could shine some light on this and what could possibly be causing the issues. The phones look brand new and are known as '14 day returns' meaning someone has returned it from new after 14 days, they are then fully tested by the manufacturer before being sold to companies like ourselves. If it was one phone I'd suspect maybe a hardware issue but because it's 6 I'm just thinking this would be a strange coincidence.
I'd be interested to hear from anyone who could give me advice on, unlocking, flashing and anything else which could help me at my place of work. I work with Sony's, HTC's, Lumia's, Samsung's and Motorola's, and also every now and again ZTE and Huawei's. So feel free to contact me if you think you could offer me any advice, all is welcome.
Thanks for reading, and thanks in advance to any advice.
Chris
kimber015 said:
Hi,
I realize many of you will state this has been asked before but I really can't find a fix for the phone so I thought maybe it's best to ask my own question and describe the issue.
So I work in a small company dealing with recycled mobile phones. I've been there about a year and a half, I had no training as it was just me and another guy, so it was just google and a lot of help from this site, so thanks guys for all the great help as I've got most of my answers from previously asked questions. I'm not a complete noob, but still have lots to learn.
This question I will keep related to the Moto G. So in my company we managed to pick up around 20 Moto G XT-1032. However around 6 of them seem to have software issues, after a factory reset (after testing) 6 got stuck on a boot loop. So I searched around and found 'http://forum.xda-developers.com/showthread.php?t=2542219' which I followed and managed to flash the software back to 4.3, I had issues on an XP computer but after trying with a windows 7 it seemed to work and the phone booted up. The 6 which got stuck in a boot loop had previously been factory reset as I could see it was at the factory set-up when I turned them on. So I was quite confused why 6 would get stuck.
So today I actually finally figured out to move to a windows 7 laptop which allowed me to actually flash the phones. After flashing the phone back to 4.3 I tested the phone and all seemed fine, so as these are to be sold I had to factory reset them again (resetting through the standard settings, no special code). So once again they all seemed to get stuck in a bootloop, but instead of an actual bootloop it shows the Motorola logo and then the screen goes black but I can see the backlight is still on, then it just sits there as long as I leave it, over 4 hours so far.
I have attempted a second flash on one of the phones and it's done the same. I'm downloading UK firmware for the xt1032 not the dual sim version. I've held the power button for 120 seconds as someone mentioned that on some random thread. Managed to get to restart and got into the android bios thingy (not sure what it's actually called, hopefully you'll understand what I mean) and attempted a factory reset but it just gets stuck on the black screen (still can see the backlight is on).
I'm now out of ideas, I really don't know what else to try. I'd really appreciate if someone could shine some light on this and what could possibly be causing the issues. The phones look brand new and are known as '14 day returns' meaning someone has returned it from new after 14 days, they are then fully tested by the manufacturer before being sold to companies like ourselves. If it was one phone I'd suspect maybe a hardware issue but because it's 6 I'm just thinking this would be a strange coincidence.
I'd be interested to hear from anyone who could give me advice on, unlocking, flashing and anything else which could help me at my place of work. I work with Sony's, HTC's, Lumia's, Samsung's and Motorola's, and also every now and again ZTE and Huawei's. So feel free to contact me if you think you could offer me any advice, all is welcome.
Thanks for reading, and thanks in advance to any advice.
Chris
Click to expand...
Click to collapse
Before I start: DISCLAIMER: I DO NOT TAKE ANY RESPONSIBILITY FOR YOUR ACTIONS BY FOLLOWING MY INSTRUCTIONS. YOU ARE FULLY RESPONSIBLE FOR YOUR ACTIONS.
Now we got that out of the way...
Try upgrading to 4.4.2: http://sbf.droid-developers.org/phone.php?device=14 (Get the firmware here)
Use the thread you mentioned: http://forum.xda-developers.com/showthread.php?t=2542219
Hello all
I come today with a question that i hope someone will have an answer for.
Week ago my Nexus 5 turned of and would not turn on, at all. Only times it showed signs of life was when it was charging. Then it would show the google logo for half a second and then turn of, then do the same thing forever. There was no way to enter the recovery or any other part of the phone.
This is how it looks: https://www.youtube.com/watch?v=7wNZfC1LSBA
After reading lots of stuff on the net and contacting Google and LG(with no help from either) i figured it was game over for the phone but i decided to send the phone for repair to a bigger city in my country some 400km away.
Here is where it gets interesting. Today my father delivered the phone and they fixed it literally in 3minutes. When my father asked what they had done, they said to him (or atleast thats how he understood it) that they have done a hardware reset. Apparently the phone got "blocked" somehow and they simply reseted the hardware.
My question is, what the hell is a hardware reset and how do i perform it myself???
I have tried EVERYTHING i could find on the internet to try and fix the phone before sending it, im not the greatest expert but id like to think i know my way around android more then the average user. I have to say again, the phone showed no signs of life, it was impossible to enter recovery so i have no idea how they could have done it.
I would really like to learn how to do this, so i am prepared if it happens in the future.
Thank you for your time
Factory reset?
I was watching a video on my pixel when suddenly the display freezed and turned off. Since then it has been restarting and crashing again and again. I have already done factory reset. I am unable to attach image here which would have given a better idea of the problem ibb. co/ jDdU6b . Remove the spaces in the link to see the photo.
Instead of a factory reset have you tried flashing the factory image via fastboot? I would attempt to backup what is important and run the flash_all.bat with the file unaltered. This will allow the image to be flashed and all user data would be wiped giving a clean install.
Sent from my Pixel using Tapatalk
chaitan123 said:
I was watching a video on my pixel when suddenly the display freezed and turned off. Since then it has been restarting and crashing again and again. I have already done factory reset. I am unable to attach image here which would have given a better idea of the problem ibb. co/ jDdU6b . Remove the spaces in the link to see the photo.
Click to expand...
Click to collapse
Just for humor, it is the same concept!! https://youtu.be/kKAjay0iWwI
Bro, let me know what you find out because this ****ing phone has got me sick and tired of these reboots. It just ****ing reboots at random times and even when it boots up after a reboot it will freeze and reboot again. Honestly, I have never said this to anyone because I am a hardcore nexus user but **** this phone, google really ****ed this one up.
I been having this issue, and preformed a factory reset on Jan 1. I cant say I have seen it re-appear. I am 7.1.2 by the way. If it is across the board with 8 and 7.1.2, then it may be some wonky google app that is common to both. It was not any specific application that it happened on either.
I just did an RMA, my warranty ended in dec 27 and they still sent me a new one. I hope the new one doesn't have problems, it probably is a google app.
Return it before your warranty runs out. This happened to me on december 15th. My warranty expired nov 17th and google refused to do anything and ubreakitifixit cannot fix it. This is a known issue, but google won’t stand behind their product. Eventually your phone will shut down and never turn back on.
carm01 said:
I been having this issue, and preformed a factory reset on Jan 1. I cant say I have seen it re-appear. I am 7.1.2 by the way. If it is across the board with 8 and 7.1.2, then it may be some wonky google app that is common to both. It was not any specific application that it happened on either.
Click to expand...
Click to collapse
I wanted to update this as it is possible I might have stumbled across something.
After wiping it and restoring some apps, I had no issues with it until the week of the 22nd of January. I installed one app and it started to reboot randomly. That app was Android Pay. Once it started to happen I uninstalled it, and have not had any re-boots since again.
Best Regards
This just started happening to my girlfriend's pixel. Bone stock, never rooted. If you even have a HINT that your phone is rebooting for no reason, I suggest you send it in for repair as soon as possible. Her phone now just bootloops, and you can't boot recovery mode either.
Google support said that the warranty expired in October, and so they told me I can go pound sand.
Well I can call UbreakiFix... I got a quote of ~$500 to replace the motherboard + screen, and no one else sells it that I can find.
A flagship phone lasting barely more than a year is not acceptable to me. Google should be offering me a replacement device, and I'm rather pissed that they aren't.
xdraconis said:
This just started happening to my girlfriend's pixel. Bone stock, never rooted. If you even have a HINT that your phone is rebooting for no reason, I suggest you send it in for repair as soon as possible. Her phone now just bootloops, and you can't boot recovery mode either.
Google support said that the warranty expired in October, and so they told me I can go pound sand.
Well I can call UbreakiFix... I got a quote of ~$500 to replace the motherboard + screen, and no one else sells it that I can find.
A flagship phone lasting barely more than a year is not acceptable to me. Google should be offering me a replacement device, and I'm rather pissed that they aren't.
Click to expand...
Click to collapse
Yeah man same thing just happened to me, like wtf
Same here. Just bootlooping... Thanks google
This is what I get for updating my damn phone, Same problem here.
Now happening yet again to my Pixel and this is the 3rd handset I've had in 18 months. Now need to send this back to Google so that'll make 4 Pixels I'll have had before my contract ends and I can escape to a handset that works.
This problem seems to be pretty widespread. Mine Pixel’s been doing this for a while now - sometimes it’ll go days without me at least noticing a reboot, other times it will happen so often as to make the phone useless. I just tried a factory reset - anyone know if there’s a permanent fix to this? It sucks when I’m in the middle of a call and then all of a sudden the phone shuts down and starts rebooting.
I have had extremely bad luck and all sorts of dramas including frying the mainboard of my T-865 while attempting to flash TWRP on my way to get it rooted. I will get my tablet back a few days later after paying 550 bucks for the repair on top of the purchase price of the tablet itself 10 days ago (of course of out warranty since I unlocked the bootloader and tried to install "unauthorized software" according to their warranty terms)
My simple question now is, is there is a way to get the T-865 rooted without having to install a custom recovery (which under no circumstances I will attempt again)? All I need is root, nothing else.
Thanks for the advice
@VeEuzUKY may I ask how your motherboard got fried?
Did you follow the steps mentioned in this thread https://forum.xda-developers.com/galaxy-tab-s6/development/recovery-twrp-3-3-1-t3975587?
Usually if something goes wrong while attempting root, Odin flashing stock rom will bring back the device to working condition..
jaidev.s said:
@VeEuzUKY may I ask how your motherboard got fried?
Did you follow the steps mentioned in this thread https://forum.xda-developers.com/galaxy-tab-s6/development/recovery-twrp-3-3-1-t3975587?
Usually if something goes wrong while attempting root, Odin flashing stock rom will bring back the device to working condition..
Click to expand...
Click to collapse
Dearest jaidev.s.. it's quite of a long story (and a surprising one at that) as I have been flashing, testing and even helping build several custom ROMs for Samsung deviced in the past 12 years without ever getting stuck in a truly unforeseen situation.
To make a very long story short, after doing all my homework through all the available threads and feedback I could find on the matter, I ventured to unlock the bootloader, install TWRP custom recovery, required custom kernel and magisc root files for my T865. And yes, I followed precisely the available guides on it from our community. Things all went pretty much as planned and I eventually booted into a successful fully rooted session on my tablet. I tested all of the tablet's native apps and functionality, installed Root Explorer and a few other apps that I had backed-up APKs for. My session was about 30 minutes long, I never connect to any data in stayed always offline, after which I decided to reboot the tablet. And then, meltdown.
The tablet immediately refused to restart again, completely bypassing the initial standard Samsung splash screen, and going directly into a warning screen that it had been locked due to the "installation of unauthorised software". From that point on any attempt to get the tablet from that state or to simply flash the stock firmware, failed completely. With the help of some other developers we all ventured together if my firmware was actually from another region, all of which I tried without any success. Eventually the tablet got stuck in a state that would not even turn off anymore even if I forced it via the volume down and power button commands. I eventually just waited out until the battery exhausted itself and then that was that.
Upon taking it to Samsung for repair where within seconds they realised that I had unlocked the bootloader and had tried to install a custom recovery, they came back about half an hour later explaining me that the hardware itself would not read or write any data any more despite their efforts, for which they would have to replace the mainboard.
I am yet to try and understand how the the tablet stopped functioning upon a reboot when up to that point everything had been flashed correctly and I had managed to do a session with everything properly configured. This said, I'm facing a $550 repair to what was an $800 tablet purchased just 10 days ago. I will obviously now not venture to try to install custom recovery again. I believe my tablet might have been a one-off with some sort of a preexisting hardware glitch that got ignited by the custom flashing that I did.. I really don't know and it really doesn't matter. At this point as I am about to collect the repaired tablet in a couple of days, the only thing I am interested in doing (a must for me on any device) is to achieve root and let it be. I don't want custom recoveries, kernel overrides or anything else other than having root. Thus my search on what will be be the best venue I have how to get the tablet safely rooted without messing with TWRP again or trying to mod the bootloader. And that's pretty much it..
And let me state, I have received nothing other than truly overwhelming support and help from lots of members of the community on my particular case for which I am extremely thankful and appreciative.
PS - I also have a Note 10 plus, recently purchased to finally replace my daily driver Note 8 that I've had for almost 3 years. Needless to say that I am absolutely dreading about the thought of installing a custom recovery on it as well and achieving root, and having again any kind of bad luck to get myself stuck in another nightmare again. I will first deal with the tablet, and if that eventually goes well, I will try to gain the necessary courage to get myself to flash TWRP and root on it without destroying it next. More than 12 years doing these things with nothing but success on dozens of devices, and suddenly here I am.
Part of me is wondering if Knox's eFuse tripping could have been the reason the board got fired? Perhaps a fault in that. Can't see any other reason reason why modifying software would cause a catastrophic hardware failure.
Anyway, as far as I'm aware the only other way to achieve root is to patch your stock OS in Magisk, then flash the modified file as detailed in this thread...
https://forum.xda-developers.com/galaxy-note-10+/how-to/guide-how-to-root-note-10-t3960031
Which is originally linked from This Thread
I've not tried it myself and it's a process from before TWRP was developed for the Tab S6 - So, you should do further research on it before jumping in to ensure nothing has changed.
Precisely why I am not installing twrp. The threads pages are having so many varied info and people getting bricks following steps, i feel discouraged to try root.
Tab s6 gonna be my first phone in 10 years that m gonna not root. I am using android since éclair and rooting.
"Samsung splash screen, and going directly into a warning screen that it had been locked due to the "installation of unauthorised software". From that point on any attempt to get the tablet from that state or to simply flash the stock firmware, failed completely. "
I had the same experience. I installed everything and rebooted to see this. Was only annoyed that oem unlock won't be an available instantly but it was. I went to download mode flashed stock, installed twrp again and it was fine. If you couldn't go to download mode (with cable inserted into pc! I assume you must know it because you flahed it, thie was another new idiotic introductement by gnus, i thought i have broken tablet because i couldn't get into download mode, when i found out cable must be in not mentioned anywhere in the instructions, just like we must know it, when it never in the universe been the case) then it's weird bug. Because what you are describing sound like standard behavior for these tablets, but why you couldn't get out of it right away i don't kno, because i could. Moreover i had the same on s9 snap. On s9 i also has issues when oem unlock will never appear, until i run some command checking it status and it got instantly unlocked. I shared it tp developer but he only laughed. When i knio there is nothing to laugh, sung's firmware has millions of such unexplainelable behaviors, a lot of people are faced with it. If you had another tablet and got the same result then just pick up non tgy one and it will be good, i promise. Also who knows why you want note 10 and t s6
Extreemator said:
"Samsung splash screen, and going directly into a warning screen that it had been locked due to the "installation of unauthorised software". From that point on any attempt to get the tablet from that state or to simply flash the stock firmware, failed completely. "
I had the same experience. I installed everything and rebooted to see this. Was only annoyed that oem unlock won't be an available instantly but it was. I went to download mode flashed stock, installed twrp again and it was fine. If you couldn't go to download mode (with cable inserted into pc! I assume you must know it because you flahed it, thie was another new idiotic introductement by gnus, i thought i have broken tablet because i couldn't get into download mode, when i found out cable must be in not mentioned anywhere in the instructions, just like we must know it, when it never in the universe been the case) then it's weird bug. Because what you are describing sound like standard behavior for these tablets, but why you couldn't get out of it right away i don't kno, because i could. Moreover i had the same on s9 snap. On s9 i also has issues when oem unlock will never appear, until i run some command checking it status and it got instantly unlocked. I shared it tp developer but he only laughed. When i knio there is nothing to laugh, sung's firmware has millions of such unexplainelable behaviors, a lot of people are faced with it. If you had another tablet and got the same result then just pick up non tgy one and it will be good, i promise. Also who knows why you want note 10 and t s6
Click to expand...
Click to collapse
Thanks for all the info. The Note 10+ is my girlfriend's phone. I use sometimes as well when I don't feel like holding the tablet. The Galaxy A 8" with S-Pen is the perfect device.. not too small, not too big and has the pen. Unfortunately stupid Samsung decided to make it ridiculously low-end with atrocious specs, can't use it for any productivity.
VeEuzUKY said:
Thanks for all the info. The Note 10+ is my girlfriend's phone. I use sometimes as well when I don't feel like holding the tablet. The Galaxy A 8" with S-Pen is the perfect device.. not too small, not too big and has the pen. Unfortunately stupid Samsung decided to make it ridiculously low-end with atrocious specs, can't use it for any productivity.
Click to expand...
Click to collapse
and now Samsung has 11 and 12 inch tablet versions for the s7...lol (next thing will be maybe a 14 inch or 17 inch 'tablet') 8 to 8.9 is the right size for a tablet. Anything bigger is basically looking at an old-school tv screen from the '70s or '80s just 6 inches or so away from your eyes with your entire face lit up by the screen lol
mac231us said:
and now Samsung has 11 and 12 inch tablet versions for the s7...lol (next thing will be maybe a 14 inch or 17 inch 'tablet') 8 to 8.9 is the right size for a tablet. Anything bigger is basically looking at an old-school tv screen from the '70s or '80s just 6 inches or so away from your eyes with your entire face lit up by the screen lol
Click to expand...
Click to collapse
Haha, I absolutely agree with you
I'd love a 17" Tablet. Lol. Personally, I don't like any Tablet less than 10" - If I want something small, I'll use my phone.
@VeEuzUKY did you get your Tab rooted?