Related
I am a novice. Please excuse if my forum etiquette is not upto the mark
Issues:
1. Phone not booting into recovery or download mode
2. USB Jig not working as well.
3. When turning on from power off, skips Samsung boot screen as well as ROM boot animation and directly opens home screen.
Background:
Followed instructions on this thread to get rid of yellow triangle (As far as I know, followed instructions to the dot) :
http://forum.xda-developers.com/showthread.php?t=1354888
Ever since, I face the three issues listed above.
Sent from my GT-I9100 using XDA App
Have you tried?
if normal boot process is not working then
remove battery
press volume download+middle key+power on
while holding these keys insert battery , it will (should) work
aramil said:
Have you tried?
if normal boot process is not working then
remove battery
press volume download+middle key+power on
while holding these keys insert battery , it will (should) work
Click to expand...
Click to collapse
Thanks for your response, Aramil:
I've tried multiple times to:
1. Boot to recovery mode - Black screen, only the two soft buttons light up.
2. Boot to download mode - Black screen, only the two soft buttons light up.
3. Turn off phone and connect USB Jig - No response.
4. Removed battery and then replaced it while simultaneously pressing volume down+middle key+power on - No Response.
SOLVED!!
Alrighty. I solved it myself!!
After more than a week of very limited help from members, I stumbled upon the solution to this issue.
The problem was with the bootloader. I flashed a stock bootloader, and all my issues were fixed!!
Thanks to those who attempted to help!!
Any suggestions on how I can get more people to post replies? Almost 200 people saw my post, but just Aramil replied! I must say I felt a bit letdown by the community. Anyways, Thanks Aramil!
rvk
190 of those people just didn't know an answer
9 person were not interested and 1 person was just lazy .
Depending on the question posted and the people who view it, you could have 1 million views with no one knowing an answer.
You could also have tried galaxy s2 Q&A forums.
no recovery or download modes and irregular bootup
I have this trouble also and think it is a bootloader problem. Rinuvimal says problem solved by flashing a stock bootloader. How is that done please?
My problem is:
1. I think it started when I bought a USB jig. To use this I needed to flash an old bootloader which I did through Odin.
2. Now I cannot access CWM by using up volume, home and power buttons. Nor can I access download mode using down volume, home and power.
3. Inserting the usb jig does not now load the download mode screen.
4.From off, when I press power, it does not go through usual boot process (nothing showing on screen) but after the soft key lights come on I seem to have booted up and can then use phone as normal.
My settings show Android 4.0.3, Baseband Version i9100BVKJ4, Kernel version i9100XXLP6-CL72050 and Build number lidroid-resurrection remix ics 9.4 black edition by westcrip XXLPH.
Can anyone help me to solve this problem please?
rinuvimal said:
Alrighty. I solved it myself!!
After more than a week of very limited help from members, I stumbled upon the solution to this issue.
The problem was with the bootloader. I flashed a stock bootloader, and all my issues were fixed!!
Thanks to those who attempted to help!!
Any suggestions on how I can get more people to post replies? Almost 200 people saw my post, but just Aramil replied! I must say I felt a bit letdown by the community. Anyways, Thanks Aramil!
rvk
Click to expand...
Click to collapse
I too face the same problem. Can u just tel me what to do and what not to. Thanks in advance.
Not booting , no download & recovery mode, jig failed
Hello dear,
I have a samsung s duos(7562) rooted phone. I flashed the cosmic rom v1.0 with cwm 5.5 . Now the phone does't booting. When i press the power button the logo of samsung is coming and then power off. When i plug in to charge it then rebooting automatically and not show charging logo. I already used keys and usb home made jig(300k) to go download & recovery mode but failed. When i connect it with my computer then showing connecting and disconnecting on computer. Also adb command not working. Please help me to save my galaxy.
Flash stock rom from odin..if this not work then go to service center then they will flash your device from dongle ...and then your problem is solved
Sent from my GT-S5830i using Tapatalk 2
SGS2 G - flashing problem
Edit: sorry, deleted.
rinuvimal said:
Alrighty. I solved it myself!!
After more than a week of very limited help from members, I stumbled upon the solution to this issue.
The problem was with the bootloader. I flashed a stock bootloader, and all my issues were fixed!!
Thanks to those who attempted to help!!
Any suggestions on how I can get more people to post replies? Almost 200 people saw my post, but just Aramil replied! I must say I felt a bit letdown by the community. Anyways, Thanks Aramil!
rvk
Click to expand...
Click to collapse
How did u flash it? I mean without going into the download mode.
Hi guys i have s2 shv e110s now it looks like dead because its not powerin on no display not going to recovery nor to download mode how to fix last time i flass cwm zip through twrp recovery and wipe data , system,and fectory reset n last i select (boot to system) but my phone not goes on
Plz help
rinuvimal said:
SOLVED!!
Alrighty. I solved it myself!!
After more than a week of very limited help from members, I stumbled upon the solution to this issue.
The problem was with the bootloader. I flashed a stock bootloader, and all my issues were fixed!!
Thanks to those who attempted to help!!
Any suggestions on how I can get more people to post replies? Almost 200 people saw my post, but just Aramil replied! I must say I felt a bit letdown by the community. Anyways, Thanks Aramil!
rvk
Click to expand...
Click to collapse
how did you solve the prblm
I don't know what went wrong..
My phone stuck at dialer after i made a phone call..therefore I pulled out the battery,put it back & try to turn it on..but nothing happened.
I tried to go into recovery (volume down+power) but it still wont turn on..
Also i tried to use ADB but my phone not detected..
The phone wont turn on,nothing on the screen,LED light not blinking (even when i connect to PC or wall charger)
Please let me know if you guys got any suggestion or even better if there is a solution..
please dont tell me that my phone is bricked
far8s said:
I don't know what went wrong..
My phone stuck at dialer after i made a phone call..therefore I pulled out the battery,put it back & try to turn it on..but nothing happened.
I tried to go into recovery (volume down+power) but it still wont turn on..
Also i tried to use ADB but my phone not detected..
The phone wont turn on,nothing on the screen,LED light not blinking (even when i connect to PC or wall charger)
Please let me know if you guys got any suggestion or even better if there is a solution..
please dont tell me that my phone is bricked
Click to expand...
Click to collapse
any luck on this??? i jacked mine up trying to flash a new firmware and am stuck in the same boat with my sensation being completely unresponsive.
You could factory reset it:
From the manual:
If you can’t turn HTC Sensation 4G on or access settings, you can still perform a factory reset by using the hardware buttons on HTC Sensation 4G.
1. Remove the battery, wait for a few seconds, then reinsert the battery.
2. Press and hold the VOLUME DOWN button, and then briefly press the POWER button.
3. Wait for the screen with the three Android images to appear, and then release the VOLUME DOWN button.
4. Press VOLUME DOWN to select FACTORY RESET, and then press the POWER button."
Overlord-in-training said:
You could factory reset it:
From the manual:
If you can’t turn HTC Sensation 4G on or access settings, you can still perform a factory reset by using the hardware buttons on HTC Sensation 4G.
1. Remove the battery, wait for a few seconds, then reinsert the battery.
2. Press and hold the VOLUME DOWN button, and then briefly press the POWER button.
3. Wait for the screen with the three Android images to appear, and then release the VOLUME DOWN button.
4. Press VOLUME DOWN to select FACTORY RESET, and then press the POWER button."
Click to expand...
Click to collapse
It was stated that he can't access the bootloader, which is what is required for the "FACTORY RESET"...
There are a number of people reporting this issue. I've even experienced the issue after the device powered down due to a drained battery. Luckily I have a stand alone charger. I put the battery on the charger for about 15 minutes, put it back in the device and it was able to boot, charge, connect usb etc...
I tried for 20 minutes to get any response from the device before trying the charger.
No charging LED isn't a good sign.
There seem to be more and more people reporting with this problem these last few weeks. IT happened with mine....it was not battery drained cuz it went dead when battery was 100% charged. I've been trying to get input as to whether this is related to ROM or firmware we're flashing....but no one seem to know.
Nothing will work...ADB...battery out...etc...I've sent my phone back to HTC...waiting to see what happens.
There are at least 3-4 different post with the same problem the past few weeks.
newr said:
There seem to be more and more people reporting with this problem these last few weeks. IT happened with mine....it was not battery drained cuz it went dead when battery was 100% charged. I've been trying to get input as to whether this is related to ROM or firmware we're flashing....but no one seem to know.
Nothing will work...ADB...battery out...etc...I've sent my phone back to HTC...waiting to see what happens.
There are at least 3-4 different post with the same problem the past few weeks.
Click to expand...
Click to collapse
What rom were you running when this happened?
GROGG88 said:
It was stated that he can't access the bootloader, which is what is required for the "FACTORY RESET"...
There are a number of people reporting this issue. I've even experienced the issue after the device powered down due to a drained battery. Luckily I have a stand alone charger. I put the battery on the charger for about 15 minutes, put it back in the device and it was able to boot, charge, connect usb etc...
I tried for 20 minutes to get any response from the device before trying the charger.
Click to expand...
Click to collapse
Well what i did was that i had a brand new sensation, i got it s-offed, rooted, cwm, superCID. all that done following the guide here on XDA. i wanted to have the new elegancia ICS rom which required the 3.32 firmware with the 4ext recovery. I got the 4ext flashed and then flashed the 3.32 firmware which caused a bootloop. then i panicked and tried to put it back to stock. not realizing that it was prolly bootlooping due the stock rom not being compatible with that firmware (not positive if that caused the bootloop. just a guess) it bricked after trying to put it back to stock. nothing responds. computer doesnt recognize it. new battery doesnt to anything. no charging led. looking back on what i did. I was still able to get into the 4ext recovery when it was bootlooping. If i flashed a compatible rom while it was doing that would it have fixed the issue. can anyone confirm if the bootloop was caused due the the stock TMOUSA rom not being compatible with 3.32? Tmobile is going to send me a brand new one. I'd like that rom but dont wanna repeat the same mistake lol
Thanks
shawn0223 said:
Well what i did was that i had a brand new sensation, i got it s-offed, rooted, cwm, superCID. all that done following the guide here on XDA. i wanted to have the new elegancia ICS rom which required the 3.32 firmware with the 4ext recovery. I got the 4ext flashed and then flashed the 3.32 firmware which caused a bootloop. then i panicked and tried to put it back to stock. not realizing that it was prolly bootlooping due the stock rom not being compatible with that firmware (not positive if that caused the bootloop. just a guess) it bricked after trying to put it back to stock. nothing responds. computer doesnt recognize it. new battery doesnt to anything. no charging led. looking back on what i did. I was still able to get into the 4ext recovery when it was bootlooping. If i flashed a compatible rom while it was doing that would it have fixed the issue. can anyone confirm if the bootloop was caused due the the stock TMOUSA rom not being compatible with 3.32? Tmobile is going to send me a brand new one. I'd like that rom but dont wanna repeat the same mistake lol
Thanks
Click to expand...
Click to collapse
Yep, it was because stock was incompatible with that fw, happened to me two weeks ago when I got my sensation and I started tinkering, I flashed opensensation and I was good to go
Sent from my sensational sensation 4g
yahhboy said:
Yep, it was because stock was incompatible with that fw, happened to me two weeks ago when I got my sensation and I started tinkering, I flashed opensensation and I was good to go
Sent from my sensational sensation 4g
Click to expand...
Click to collapse
so if i do the same process and go flash the new rom right after flashing the fw. i shouldnt have a problem right?
tjamaican said:
What rom were you running when this happened?
Click to expand...
Click to collapse
I installed 6.6.2 Revolution. It booted fine after I installed the ROM...so unlike some others, the installation seems to worked fine. I was able to run Titanium and restalled all the programs....but then when I talked on the phone....it became unresponsive and shutdown and never turned on again
Having similar problem.........only thing my phone just vibrates......the led is red for couple seconds when charger is connected
dreaddie101 said:
Having similar problem.........only thing my phone just vibrates......the led is red for couple seconds when charger is connected
Click to expand...
Click to collapse
WEll..if your phone lights up or have some response.maybe you can still do something by connecting to computer. Mine was completely unresponsive...and can't be detected on computer!
Maybe it's an overclock issue? I've read on different threads that there may be a motherboard issue. The sensation is known for overheating. Maybe it's frying the motherboard.
What frequency were you guys running and was your phones randomly shutting down before it became unresponsive?
i think we guyz got the same problem :S its just turned off with a constant beep
http://forum.xda-developers.com/showthread.php?t=1624293
shawn0223 said:
so if i do the same process and go flash the new rom right after flashing the fw. i shouldnt have a problem right?
Click to expand...
Click to collapse
Yes you should be fine, just make a backup of stock in case something goes wrong when you flash your first rom
Sent from my sensational sensation 4g
yahhboy said:
Yes you should be fine, just make a backup of stock in case something goes wrong when you flash your first rom
Sent from my sensational sensation 4g
Click to expand...
Click to collapse
Awesome, I just got my new sensation yesterday. Worked like a charm.
---------- Post added at 08:29 AM ---------- Previous post was at 08:28 AM ----------
shawn0223 said:
Awesome, I just got my new sensation yesterday. Worked like a charm.
Click to expand...
Click to collapse
Oh and thanks lol
Hi, I am new at this forum and i would like to ask you the following question.
recently i bought a samsung galaxy ace 2 phone and today i decided to try a custom ROM with, being a Linux geek for years...
So i chose Kyrillos Rom for my phone and after several failures i got to understand that before i try to load the custom ROM i had to upgrade my firmware and kernel as described here :http://forum.xda-developers.com/showthread.php?t=1955679
So i used Odin tool , and tried to flash the new firmware as described here :http://forum.xda-developers.com/showthread.php?t=2118119,before proceeding to kernel flash.
Everything went smooth , Odin showed 'pass' indication and my phone after the procedure tried to reboot...and never woke up...
From then i cannot boot my phone at all, i mean neither in usual mode by pressing the power button nor in recovery or download mode. It does not respond to any of those, the screen and the buttons are completely black no matter how many seconds i press them
When i started the procedure my battery level was at 70% and just to be sure i connected it to USB port so as not to empty the battery during the procedure..Now that i connected it to its' charger it does not show the charging indicator
Any ideas as to what happened and how i can fix my problem?
Thank you in advance and keep up the good job!!!
seems motherboard is dead u need to get it replaced anyway did u follow the odin guide carefully cause it seems not
Blackwolf10 said:
seems motherboard is dead u need to get it replaced anyway did u follow the odin guide carefully cause it seems not
Click to expand...
Click to collapse
It seems that i followed the exact directions in the posts mentioned, but my phone is I8160P and not I8160 something that i had not noticed up until tonight,so i think that it has something to do with this, even though i cannot understand how my motherboard died because of the firmware upgrade even thw firmware is made for another model...
VisagenNoir said:
It seems that i followed the exact directions in the posts mentioned, but my phone is I8160P and not I8160 something that i had not noticed up until tonight,so i think that it has something to do with this, even though i cannot understand how my motherboard died because of the firmware upgrade even thw firmware is made for another model...
Click to expand...
Click to collapse
it does have everything to do with that but it seems more like a hardbrick to me so does the phone charge or have u tried a lot of times to boot it or maybe pull the battery out for 5 min then put it back in and try to go to recovery or download if none of these stuff work then i think its dead
Blackwolf10 said:
it does have everything to do with that but it seems more like a hardbrick to me so does the phone charge or have u tried a lot of times to boot it or maybe pull the battery out for 5 min then put it back in and try to go to recovery or download if none of these stuff work then i think its dead
Click to expand...
Click to collapse
Yes i tried both normal boot pressing the power button and recovery - download modes and it did not power on in any of those cases. Also i tried pulling out the battery for 5 - 10 minutes and it did not power on afterwards either.Is this something that happens often because it seems really strange to me. If it has nothing to do with the firmware upgrade and it is a hardware issue then ok, i can sent it to repair it but if i have already lost the warranty due to root and firmware - custom recovery etc.. then what exactly do i have to do..
VisagenNoir said:
Yes i tried both normal boot pressing the power button and recovery - download modes and it did not power on in any of those cases. Also i tried pulling out the battery for 5 - 10 minutes and it did not power on afterwards either.Is this something that happens often because it seems really strange to me. If it has nothing to do with the firmware upgrade and it is a hardware issue then ok, i can sent it to repair it but if i have already lost the warranty due to root and firmware - custom recovery etc.. them what exactly to i have to do..
Click to expand...
Click to collapse
i don't think they will know since the phone won't boot up at all they know by going to download so give it a try and take it to a service and if ur in europe rooting does not affect ur warranty hope this helps
Alright i got 6 hours before tmbobile store opens and i can HOPEFULLY get an exchange, but not banking on it. btw im new to rooting so i wasnt familiar with the process, but regardless i have hard bricked my NEXUS 5. Title says the problem. I followed wwjoshdew's guide to rooting on youtube, and rooted successfully. But i could'nt for the life of me figure out how to create nandroid. I ended up realizing i didnt download cmw recovery mode and downloaded it from the play store. the app took me to a button that said flash recovery and i hit it and my phone asked for permission from unknown source, i hit ok and it shut down, on 70% battery life. Not turning on please help
Try to boot the phone into bootloader mode. Just hold volume down and the power button. From there try to cycle to recovery. You use your volume down to cycle through the options and power but as select. If you can boot into recovery and have that successfully installed then you can erase your phone and try to power it on from there. If you didn't successful install the custom recovery then you'll have the standard Android recovery. You can erase everything from that too.
These phones are hard to brick and not be able to fix it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
ruben8448 said:
Try to boot the phone into bootloader mode. Just hold volume down and the power button. From there try to cycle to recovery. You use your volume down to cycle through the options and power but as select. If you can boot into recovery and have that successfully installed then you can erase your phone and try to power it on from there. If you didn't successful install the custom recovery then you'll have the standard Android recovery. You can erase everything from that too.
These phones are hard to brick and not be able to fix it.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Doesn't turn on dude. No matter what. I am new to roms but i know what a hard brick is.
You should really read the guides and stickied threads at the top of these forums. The guides are very noob friendly and you wouldn't have bricked your phone. There's one to reset your device to stock as well. There's really no need for this thread and on top of that there is a sticky that says no questions in the General forums.
Sent from my Nexus 5 using Tapatalk
Determine your phone is actually off. Plug your phone into charge, if a battery sign appears in the middle of the screen then your phone is off.
If your phone is off, hold down the volume down button with the power button to start the bootloader, press volume down twice and press the power button to enter recovery.
If your screen remains black and doesn't show a battery logo, hold the volume up, volume down and power buttons at the same time for a minute, then let go and hold down the power button. Which should hopefully start your phone.
FuMMoD said:
You should really read the guides and stickied threads at the top of these forums. The guides are very noob friendly and you wouldn't have bricked your phone. There's one to reset your device to stock as well. There's really no need for this thread and on top of that there is a sticky that says no questions in the General forums.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
You should have been around long enough to know that when newbies break their new toys they go nuclear and dismiss all the information around them.
BNNEBULA said:
Alright i got 6 hours before tmbobile store opens and i can HOPEFULLY get an exchange, but not banking on it. btw im new to rooting so i wasnt familiar with the process, but regardless i have hard bricked my NEXUS 5. Title says the problem. I followed wwjoshdew's guide to rooting on youtube, and rooted successfully. But i could'nt for the life of me figure out how to create nandroid. I ended up realizing i didnt download cmw recovery mode and downloaded it from the play store. the app took me to a button that said flash recovery and i hit it and my phone asked for permission from unknown source, i hit ok and it shut down, on 70% battery life. Not turning on please help
Click to expand...
Click to collapse
You bricked a Nexus?
Hold down Volume Down, Up, and Power to get into fastboot mode. Restore from Factory Image.
Normally, to root a nexus, I fastboot Team Win Recovery Project.
Anyways what you did simply could not HARD BRICK the phone.
zeekiz said:
You should have been around long enough to know that when newbies break their new toys they go nuclear and dismiss all the information around them.
Click to expand...
Click to collapse
Seriously lol. Even though the guides are right there in their faces.
Sent from my Nexus 5 using Tapatalk
HELP SOS
FuMMoD said:
You should really read the guides and stickied threads at the top of these forums. The guides are very noob friendly and you wouldn't have bricked your phone. There's one to reset your device to stock as well. There's really no need for this thread and on top of that there is a sticky that says no questions in the General forums.
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
My Nexus5 doesn't flash the Led light or enter bootloader and software . I was flashing the based CM kernel and i followed the instructions nicely, while using TWRP Recovery i pressed reboot system after the flash and the phone suddenly died. I connected it to the PC and the installing drivers popup appeared and it didn't install them, problem(QHSUSB_BULK) it only appeared once. And since that, phone is dead. PLEASE HELP!!!!
Yazan Abzakh171 said:
My Nexus5 doesn't flash the Led light or enter bootloader and software . I was flashing the based CM kernel and i followed the instructions nicely, while using TWRP Recovery i pressed reboot system after the flash and the phone suddenly died. I connected it to the PC and the installing drivers popup appeared and it didn't install them, problem(QHSUSB_BULK) it only appeared once. And since that, phone is dead. PLEASE HELP!!!!
Click to expand...
Click to collapse
Do you have a link to the kernel you flashed? I think you done bricked it good.
Were you using this method?
http://www.youtube.com/watch?v=w3beFx-3Ic4
If yes,I think then all Nexus 5 users should be warned about CF's autoroot issues,because I see more and more topics related to this issue.
Simonna said:
Were you using this method?
http://www.youtube.com/watch?v=w3beFx-3Ic4
If yes,I think then all Nexus 5 users should be warned about CF's autoroot issues,because I see more and more topics related to this issue.
Click to expand...
Click to collapse
I don't believe the issues you're seeing, appears to be failed emmc, is related to chain fire's auto root. Cf is probably the most popular method to root and it's a coincidence. I've seen these failures with other root methods too.
I think the op flashed a kernel not for his device.
jd1639 said:
I don't believe the issues you're seeing, appears to be failed emmc, is related to chain fire's auto root. Cf is probably the most popular method to root and it's a coincidence. I've seen these failures with other root methods too.
I think the op flashed a kernel not for his device.
Click to expand...
Click to collapse
I am not a developer so bear with me. I'm just a guy in mpls with a completely stock N5 from Google Play that encountered similar issue as the original post. There was no damage or water issue, or other problem prior to going dead. It had about 50% battery and maybe 15 minutes after reading an email it was dead when I looked at it again. It just simply turned off while in my pocket. I could not get it to power on or enter bootloader or a recovery screen. After a week of trying to charge via USB and the original wall charger and countless attempts to hold power and volume buttons without success, I decided to pop the back off and disconnected the battery. I put it back together, but that made no difference either. Google play will send me a new phone, but I'd like to get it fired up and extract the last week or so of pics. Any ideas? Again, I am a complete noob and this 3 month old phone has not been modified in any way, other than auto updates from Google play. Thanks for any assistance or guidance.
elf1967 said:
I am not a developer so bear with me. I'm just a guy in mpls with a completely stock N5 from Google Play that encountered similar issue as the original post. There was no damage or water issue, or other problem prior to going dead. It had about 50% battery and maybe 15 minutes after reading an email it was dead when I looked at it again. It just simply turned off while in my pocket. I could not get it to power on or enter bootloader or a recovery screen. After a week of trying to charge via USB and the original wall charger and countless attempts to hold power and volume buttons without success, I decided to pop the back off and disconnected the battery. I put it back together, but that made no difference either. Google play will send me a new phone, but I'd like to get it fired up and extract the last week or so of pics. Any ideas? Again, I am a complete noob and this 3 month old phone has not been modified in any way, other than auto updates from Google play. Thanks for any assistance or guidance.
Click to expand...
Click to collapse
So, your phone doesn't turn on at all?
jd1639 said:
I don't believe the issues you're seeing, appears to be failed emmc, is related to chain fire's auto root. Cf is probably the most popular method to root and it's a coincidence. I've seen these failures with other root methods too.
I think the op flashed a kernel not for his device.
Click to expand...
Click to collapse
Correct. No symbols, no battery icon, no vibrate, etc.
elf1967 said:
Correct. No symbols, no battery icon, no vibrate, etc.
Click to expand...
Click to collapse
I'm afraid there's nothing you can do. It would have to at least get into recovery or bootloader to have a prayer.
jd1639 said:
I'm afraid there's nothing you can do. It would have to at least get into recovery or bootloader to have a prayer.
Click to expand...
Click to collapse
Thanks - was just hoping it was not a hardware failure given the posts about difficulty bricking N5. Any chance if I bought a new battery that came charged it would fire up or replacing the motherboard an option?
p.s. I am not the original poster so not sure if I ticked someone off or not, sorry if I did. Just looking for assistance
elf1967 said:
Thanks - was just hoping it was not a hardware failure given the posts about difficulty bricking N5. Any chance if I bought a new battery that came charged it would fire up or replacing the motherboard an option?
p.s. I am not the original poster so not sure if I ticked someone off or not, sorry if I did. Just looking for assistance
Click to expand...
Click to collapse
It sure sounds like a hardware failure. Doubt a different battery would help. And don't worry about being the original op. This thread is old
jd1639 said:
It sure sounds like a hardware failure. Doubt a different battery would help. And don't worry about being the original op. This thread is old
Click to expand...
Click to collapse
I get the unknown device driver when hooked up USB to computer (QHSUSB_BULK). Think it is worth waiting a few weeks prior to returning it to see if there is a way to access the flash memory via a driver download? Searches for help showed similar unknown driver problem workable on samsung and HTC last year (QHSUSB_DLOAD)
elf1967 said:
I get the unknown device driver when hooked up USB to computer (QHSUSB_BULK). Think it is worth waiting a few weeks prior to returning it to see if there is a way to access the flash memory via a driver download? Searches for help showed similar unknown driver problem workable on samsung and HTC last year (QHSUSB_DLOAD)
Click to expand...
Click to collapse
No, you won't be able to. The memory doesn't mount like a sd card would. For the future use something like drop box or Google drive too backup your photos as you take them.
I'd like to generate a thread with tried and tested ROMs, recovery, and root methods like magisk for the Moto G6
I'd especially like to see a working TWRP (official or unofficial), magisk boot img, and any known working custom ROMs
It's all in Guides, News, and Discussions already.
edit: and there's fairly obviously a thread with a working TWRP build in this section. I don't understand what you're asking?
TheDevl said:
It's all in Guides, News, and Discussions already.
edit: and there's fairly obviously a thread with a working TWRP build in this section. I don't understand what you're asking?
Click to expand...
Click to collapse
Do these work on the pie update?
I was want to see any and all available ROMs for this device
clcombs262 said:
Do these work on the pie update?
I was want to see any and all available ROMs for this device
Click to expand...
Click to collapse
Check out the treble-enabled device forums. For a while, this is more or less what you're going to have to pick through.
TheDevl said:
Check out the treble-enabled device forums. For a while, this is more or less what you're going to have to pick through.
Click to expand...
Click to collapse
Thx
About magisk on pie?
clcombs262 said:
Thx
About magisk on pie?
Click to expand...
Click to collapse
To my knowledge it works the same as it does on oreo.
TheDevl said:
To my knowledge it works the same as it does on oreo.
Click to expand...
Click to collapse
'to your knowledge'?
I haven't actually got the update yet, but I just wanted to check to see if I'd need to wait to root until the update, or do it now and Skip the update
Sent from my Moto G6 using XDA Labs
clcombs262 said:
'to your knowledge'?
I haven't actually got the update yet, but I just wanted to check to see if I'd need to wait to root until the update, or do it now and Skip the update
Sent from my Moto G6 using XDA Labs
Click to expand...
Click to collapse
I'm on Brazilian Pie, was on soak Pie and GSI pie and all rooted fine with Magisk 18.1 :good:
Moto g6 fastboot rom
HueyT said:
I'm on Brazilian Pie, was on soak Pie and GSI pie and all rooted fine with Magisk 18.1 :good:
Click to expand...
Click to collapse
i have a hardbricked G6 and i found the two testpoints inside which i connect and reach QDloader modus...now i want to flash it with Milfashtool but i didnt found a fastboot rom!?
mimi77 said:
i have a hardbricked G6 and i found the two testpoints inside which i connect and reach QDloader modus...now i want to flash it with Milfashtool but i didnt found a fastboot rom!?
Click to expand...
Click to collapse
Mine got brickes too..., can u point me where is these testpoints exactly? And what is milfashtool?
72k said:
Mine got brickes too..., can u point me where is these testpoints exactly? And what is milfashtool?
Click to expand...
Click to collapse
How do you mean bricked? Where is the phone hanging? I assume you already had unlocked your bootloader before attempting rooting/magisk?
theseeker2654 said:
How do you mean bricked? Where is the phone hanging? I assume you already had unlocked your bootloader before attempting rooting/magisk?
Click to expand...
Click to collapse
Yes i had bootloader unlocked but it still unrooted and its got bricked before i even try for rooting. First of all let me tell u the chronologies. I had this phone from someone in US as a gift but i cant use it on my country(because of network) so i give it a try by unlock the bootlooder, it was succeeded and one day comes update which is april 2018 patch. After the update my phone was unstable, self reboot and bootloops and i found that the screen is flickering sometimes. Then at one night it suddenly turned off when i was sleeping. I tried all method combination button but no luck, it is caused by a bad battery or firmware fail? Please help me!!!
Note: i only got led blinking if i press power plus plugged in charger, the led blinking faster after +20 sec
One single blink every 5 sec and then blinking goes faster after +20 sec for about 5 blinks and repeat to state one single blink. Seems like battery related but i have already open the backcase to see, if i unplugged its battery then push the buttons combination the led is blinking faster like the final state -sorry for bad english
theseeker2654 said:
How do you mean bricked? Where is the phone hanging? I assume you already had unlocked your bootloader before attempting rooting/magisk?
Click to expand...
Click to collapse
Hello do u have solution for me? I managed to buy new battery because of this problem, please read all my walkthrough and give me and advice
72k said:
Hello do u have solution for me? I managed to buy new battery because of this problem, please read all my walkthrough and give me and advice
Click to expand...
Click to collapse
what have you done? Did the new battery resolve your issue? Do you know how to install it? Have you tried plugging it into power and then pressing and holding vol down and power for 2minutes?
theseeker2654 said:
what have you done? Did the new battery resolve your issue? Do you know how to install it? Have you tried plugging it into power and then pressing and holding vol down and power for 2minutes?
Click to expand...
Click to collapse
I did nothing except my bootloader is unlocked and do an OTA update (april 2018 if i remember) and its suddenly turn off when i was sleep with state of bootloop days before that. I havent buy any batteries yet because i need to know what is the problem. Yes i've done all of power combination for even 5mnts. It strange because the LED show me different if i press power combination button
---------- Post added at 05:07 AM ---------- Previous post was at 04:54 AM ----------
theseeker2654 said:
what have you done? Did the new battery resolve your issue? Do you know how to install it? Have you tried plugging it into power and then pressing and holding vol down and power for 2minutes?
Click to expand...
Click to collapse
For ex : it wont blinking at all if the battery completely empty. Then if i charge for awhile it would blink if i pressed power with vol down (after 20 sec) as i described above. Untill the final state of LED i release power and vol down and immediatly pressed vol up then its LED will keep blinking fast forever as long as the charger is plugged in
My moto g6 also appears to be bricked
I don't want to hijack this thread, but since I'm a new member I can't start a forum thread. Now on to the issue with my g6...
When I plug in my g6 the only thing that happens is a small white led flashes at the top right part of the unit. After about 20 mins or so it stops flashing. Holding down the vol+power buttons to go into recover just cycles the power off and on, with the white led flashing just like before. No recovery screen appears, no android robot; only the blinking white led--the display is otherwise entirely blank & black (meaning not lit at all).
When I connect the g6 to my PC I hear the usual "USB beep" indicating that it's recognized the phone being connected, but it does not show any drive or device either in Device Manager or in Explorer. I'm using Win10, with all the Motorola drivers+software installed.
I rooted the phone some time ago, and the bootloader was unlocked before the phone went dead. The last thing I did with the phone was to flash an Android 9 image from the forum here while the phone was connected to my PC.
https://forum.xda-developers.com/mo...android-aosp-9-0-pie-android-9-0-0r1-t3847354
I had flashed others images with no problems up to that point, even the one linked above. But I re-flashed that image since I wanted to "reset" the image to it's stock point (I had made some settings and added apps I wanted to remove, start clean again). The ONLY thing I did different was that the battery was about 50% so I left the phone charge on one of my PC's USB ports while the image was installing. When I checked the phone the next morning it was dead. Afterwards I let it charge for a week but nothing.
Last but not certainly least, I have also tried two different batteries I ordered from Amazon. No change with either one (blinking white led), despite charging each with the original charger for one week.
Sorry for being so long-winded, but I wanted to give as much detail as possible to see if someone here may have a solution. My guess is that I made an incredibly stupid mistake by letting the phone charge from my PC while flashing/installing the A9 image; I really should have left it on my moto g6 charger.
Cant flash magisk 20.1 or even any other always stuck on bootloop any suggestions
Device.= Moto g6 4gb ram
Rom= stock rom
Bootloader =unlocked
Recovery=TWRP 3.2/3.3
Can't flash no encryption either always show error 1
rohit1363 said:
Cant flash magisk 20.1 or even any other always stuck on bootloop any suggestions
Device.= Moto g6 4gb ram
Rom= stock rom
Bootloader =unlocked
Recovery=TWRP 3.2/3.3
Can't flash no encryption either always show error 1
Click to expand...
Click to collapse
Don't use anything higher than Magisk 19.3, for some reason higher versions bootloop the phone. After you install Magisk 19.3, you can upgrade normally via Magisk Manager
AgentICS said:
Don't use anything higher than Magisk 19.3, for some reason higher versions bootloop the phone. After you install Magisk 19.3, you can upgrade normally via Magisk Manager
Click to expand...
Click to collapse
Yeah that's works fine just taking longer boot time but that's ok i am giving it to my father so i don't need to root or anything .
Anyway thank you for help it really works...