Database Users

[Q] Milestone 2 Bricked?

I wasn't sure if this was the right thread (or the right site) to post this but I am in desperate need of help D:
Long story short, I bricked my phone while trying to flash back to the stock UK Milestone 2 ROM from the CM7 ROM I had on previously
Using RSDLite 5.6, the flash completed but the phone did not turn on and the computer does not detect the phone (Although the charging light turns on when I plug it into the computer)
I'm not really sure what options I have since I've tried booting into recovery but the phone won't turn on so it isn't really getting me anywhere

Pull the battery out, insert again, and try the hold d-pad up and power to get into bootloader mode. If it manages to turn on to a dull black/grey screen with minimal backlighting it possibly is in bootloader mode, but not displaying. Then you can try to flash with rsd lite from there.
Also how was your battery level before you started all this? Make sure you don't let it drain or it just makes things more complicated
But give that a try and if it doesn't work I'll try to think of something else.
---------- Post added at 08:50 AM ---------- Previous post was at 08:46 AM ----------
Also check this out: http://forum.xda-developers.com/showthread.php?t=1077414
Meant to be what they use in repair centres and stuff to ressurect and flash without batteries etc. Making one of those may be the most direct way to fix this

you not brick your phone. the same thing was with me. its just plug your phone with rsd lite open and push the power button. rsd will recognize your phone and you will be able to apply another sbf.

Thanks for the replies. The reason it wasn't turning on was because of a low battery, but I went home over the weekend and charged up my battery with an external charger.
I have tried several SBF's and in one case it will get stuck in a bootloop, and in another I'll get the black screen (Where I can still flash it).
The bootlooped SBF can still get me in recovery mode, but pressing the @ symbol (or any of the keys) doesn't bring up the menu, so I'm guessing I haven't done something right or it freezes in recovery.

Possible that you are on 2.3 already?
Try to get into the bootloader, pressing up + power for a few seconds (black screen, little bit of text)
Then your phone should be detected. Then use RSD with a stockrom, matching your androidversion you are comming from.

My phone was previously on CM7, and before that was on 2.2.
I've tried several different stock ROMs, but UK ROMs are very hard to come by since Multiupload, Megaupload, and Fileserve links are broken D:

Whoops, I realised Gingerbread had a different method of getting into recovery mode - Volume + & - at the same time. D:
Ok, I think I'll be able to fix it with what you put above

Nexus 7 dead until i connect it to a pc/laptop PLEASE HELP!

So my girlfriend was using her Google Nexus 7 2012 of 32gb only Wi-Fi triying to play the EA game "The Simpsons: Springfield" while the tablet was charging and when the game loaded it was running slowly till it frozen and then she tried to see all apps open with the 3rd button, she could pull down and see the notification drawer, then she push the 3rd button (that one on the right) but the tablet didn´t respond, instead it will just pull back the notification drawer, then the tablet started to show a notification in the middle of the screen that said "the system process is not responding" (We don´t have screenshots from this notification, that´s what she remember's and I am translating into English from the Spanish she saw) with 2 options, "wait" and "close", she pressed "close" and then it showed another notification saying "the user interface is not responding" (We don´t have screenshots from this notification, that´s what she remember's and I am translating into English from the Spanish she saw) with 2 options, "wait" and "close", she pressed "close" and I am pretty d#%n sure that it was in that moment when it got f$#%&d. Then she left it alone for like 10 minuts but it didn´t do anything, so she attempted to restart it by pressing "power + volume down" buttons together for 10 seconds and when she let the buttons go, that´s when she realized it was gone all wrong, what she saw was this "Android Robot with his belly opened with a lot of words on the down - left of the screen which ended up with look state - unlocked, it also had two arrows on the right-top of the screen, one pointing up and one pointing down, there was also on the top of the screen a red arrow with black background and inside that red arrow had written RECOVERY MODE" then she used the arrows on the right to move what was written on the red arrow, there was at least 3 options, she remember´s the first which was "RECOVERY MODE" and the second that was "POWER OFF" she is also pretty sure that it was a 3rd option but so far she doesn't remember. So she chosen power off with the power button and the tablet powered off automatically and she waited to see the tablet charging but it never appeared, later on, she tried to turn it on, it won't happen.
So now the tablet is totally dead and the only sign of life i have seen is that sound when i plug in the tablet into my pc or her laptop and press the power button, that sound that minds that a device has been mounted and the same sound when i unplug it from the pc or laptop. I have no idea of what should I do with her, my best hope is that I found a genius here patient enough to help me out with this peace of technology. :crying:

Connect to Nexus Root Kit and try to flash stock ROM. There is option for non bootable devices
Sent from my Nexus 4 using Tapatalk

Which Nexus Root Kit?
I only found here the Wugs Nexus Root Toolkit, I already installed the Wugs Nexus Root Toolkit v2.1.6 but I couldn't find the proper way to use it for a non bootable device.
Am I using the correct Nexus Root Kit?
If yes, please tell me: where can i find a step by step guide to solve the problem?
If nope, where can i find the correct Nexus Root Kit with a step by step guide?
Thank's so much in advance for your help, I already tried with the Wugs Nexus Root Toolkit v2.1.6 to flash stock ROM but as the tablet is dead, I couldn't boot it to bootloader, obviously I couldn't either turn the tablet on to allow usb debugging, for all matters, the toolkit need's adb connection to work, and I couldn't find the way to start an adb connection.

Make sure the tablet is not stuck in APX mode. To get out of this: connect the tablet for some time (at least for about 1 hour) to the charger then press for about >=20 sec the power button *only*. Release the button. If the tables was stuck in APX mode, now it should have exited that mode. Now you should be able to boot to bootloader / recovery / system. If this does not work, I suppose your tablet is bricked ...

Its correct NRT. First step is to download correct drivers and make sure it passes full driver test and adb and fastboot work. If that's the case then everything can be flashed (bootloader, recovery and ROM). Here is link to a manual process that shows steps but NRT does it automatically. Look at flashall script
http://www.laptopmag.com/articles/how-to-hard-reset-a-bricked-nexus-7-with-your-pc
Also try connecting to charger, keep it charging for 30 min or so and then try power button
Sent from my Nexus 4 using Tapatalk

Thank's!
Thank's to much for your glorious help!
I tried connecting to a charger about an hour and half and then power button, nothing happened, in approximately 24 housr from now I will follow the step by step guide to unbrick the tablet, thank's for the link, I hope it work's, I let you know later on.

If your device is really bricked, there is no change for reviving it, sorry.

Try installing just adb/fastboot (adb-setup-1.4.3.exe) from https://drive.google.com/file/d/0B0MKgCbUM0itNVB1elljU2NPR0k After installing open cmd window as admin, go to c:\adb and see if "fastboot devices" returns anything. If yes, then download recovery TWRP image (twrp-3.0.2-0-grouper.img) to same folder and type "fastboot boot twrp-3.0.2-0-grouper.img". If recovery comes up then you have options to flash some ROM. To permanently install recovery "fastboot flash recovery twrp-3.0.2-0-grouper.img" Boot loader can be flashed in the same cmd window, If it worked then reboot into bootloader with fastboot.

Why is everyone giving him advice on unbricking when he can't even power on the tablet.
Yeah, you can use ADB to fix a tablet that won't power on so the computer can even load a driver for it. LOL
<sarcasm>
Look, the Nexus 7 has random charging issues especially when it gets drained down to zero battery.
I deal with it on mine sometimes.
Not saying this is your problem, but since you can't even power the device on, it's the first thing I'd look at.
Gotta pop the back cover and reseat the battery connector.
Then try charging again for a couple hours.
Ugh, I've got to do it to mine right now too.
For the third time since I've owned it.
---------- Post added at 12:12 PM ---------- Previous post was at 11:56 AM ----------
Yep, reseating the battery cable fixed it once again for me.
https://www.youtube.com/watch?v=x8u8xSnfCOA

Moto G4 XT1621 DEAD after nougat update...

Hi!
Last friday my Moto G4 XT1621 get the last nougat update. I started the update without any problem, but when it finished, my phone didn't boot again.
Now the phone only boots on fastboot, I can't enable the developer options and I don't know how to recover my new phone.
Please, help me! I don't know about Android and this things!
Some pics of my phone.
https://goo.gl/photos/PaDjEQrn4VtFH6oP9
Thanks

Here try this mate had the same problem after i tried to side load the nougat rom, my phone would start but get stuck on the boot logo (white screen blue m logo). You will need a pc as this rom cant be sideloaded. If you have any problems post in that forum and ill help u best i can.
https://forum.xda-developers.com/moto-g4-plus/how-to/install-official-firmware-soak-test-t3531296
---------- Post added at 10:45 PM ---------- Previous post was at 10:39 PM ----------
ROM: https://drive.google.com/file/d/0B2XJ90Yz2bQmYUoySkNYTURiUG8/view?usp=drivesdk
These are the steps.
1. Install moto g4 drivers
2. Download minimal adb fastboot and install it
3. Download the rom provided, and unpackage the .rar file to the minimaladb installation location usually found in programfilesx86/minimaladb
4.boot the phone into fastboot by holding power and volume down at the same time and connect to the pc
5.double click the flashall file and a command prompt will open and continue to flash the phone takes between 5/10 mins Do Not remove the phone during this process.
6.after installation remove the phone from the pc and boot the phone it will take awhile to boot the first time so bear with it you should see that you have a new boot animation (The hello moto).

Mykstabrum0121 said:
Here try this mate had the same problem after i tried to side load the nougat rom, my phone would start but get stuck on the boot logo (white screen blue m logo). You will need a pc as this rom cant be sideloaded. If you have any problems post in that forum and ill help u best i can.
https://forum.xda-developers.com/moto-g4-plus/how-to/install-official-firmware-soak-test-t3531296
---------- Post added at 10:45 PM ---------- Previous post was at 10:39 PM ----------
ROM: https://drive.google.com/file/d/0B2XJ90Yz2bQmYUoySkNYTURiUG8/view?usp=drivesdk
These are the steps.
1. Install moto g4 drivers
2. Download minimal adb fastboot and install it
3. Download the rom provided, and unpackage the .rar file to the minimaladb installation location usually found in programfilesx86/minimaladb
4.boot the phone into fastboot by holding power and volume down at the same time and connect to the pc
5.double click the flashall file and a command prompt will open and continue to flash the phone takes between 5/10 mins Do Not remove the phone during this process.
6.after installation remove the phone from the pc and boot the phone it will take awhile to boot the first time so bear with it you should see that you have a new boot animation (The hello moto).
Click to expand...
Click to collapse
Thank you!! I'll try this and will told you if it have worked!

Ok mate yeah let me know

Mykstabrum0121 said:
Ok mate yeah let me know
Click to expand...
Click to collapse
I'm having bad luck. My G4 bike apparently ran out of battery because it does not turn on and the white led flashes 4 times and goes off. I connected the original charger but it still does not turn on. If I connect it to the computer, it recognizes it as fastboot mode but nothing appears on the phone display.

I think the battery has completley drain to 0% Try to just leave the phone plugged into the charger for at least 10/15 mins then try holding power for 30 seconds. If it turns on, and you boot it into fastboot when you connect the phone to the pc start the command prompt and type adb devices if it shows a device connected then try to flash the rom. If it doesnt flash then Im not sure what the problem is its either a hardware error or the battery charger have you tried a different charger plug/wire. Could also try to Press and hold the Volume Up and Power button for 10-20 seconds whilst the phone is plugged into the charger?

No, the battery is okay. Last night I left the phone off to continue today and this morning appeared so. I supposed it was that the battery had run out, but I just checked it with a tester and it's charged. Since last night until today not install or probe anything, I had hopes of doing the tests that you told me today, but the phone is worse than before. When I connect the phone to the pc, the "safely remove hardware" system tray appears as "Eject fastboot S".

So did you try typing adb devices in command prompt when you plugged it into the pc

Mykstabrum0121 said:
So did you try typing adb devices in command prompt when you plugged it into the pc
Click to expand...
Click to collapse
No, I didn't. My G4 is totally dead and when I plug it to the charger, a white led starts blinking. I let the phone charging about a day, but nothing changes.
If I connect the phone to my PC, nothing happen, It don't recognice the phone.
Really I never again buy back a motorola again.

How long you had the phone it may still be under warranty?

Mykstabrum0121 said:
How long you had the phone it may still be under warranty?
Click to expand...
Click to collapse
The phone was bought in October in the USA, but now it is in Argentina. I have no warranty here, I would have to try to take it to the technical service.

If you have proof of purchase (receipt) it may be covered under manufacturers waranty as its usually 12months from the date of purchase, i would contact motorola to see if they can do anything for you. Best of luck.

same issue
Did you find the solution for that

OP6T bricked hard

My 6T is currently a paperweight (bricked, screen won't turn on, no fastboot, no nothing) and here's the succession of events that led to it:
I live in the US and bought the unlocked 6T.
1) A few weeks ago I rooted it with same steps described in this post --> https://www.xda-developers.com/oneplus-6t-unlock-bootloader-root/. Everything seemed to go well, I had Magisk and my phone worked just fine.
2) About a week later I got a notification that my phone had a software update ready. I idiotically obliged and installed it. After the install, I still got the bootloader unlocked screen at start up so I thought my phone might still be rooted. However, I couldn't download any mods on Magisk and my root checker said I was no longer rooted. So basically, my phone appeared rooted (apps like Google Pay wouldn't work, I got the warning about the Bootloader at start-up, etc.) but I no longer had the benefit of being able to install mods through Magisk.
3) A few weeks later (yesterday) I decided I would explore options for un-rooting, mainly so I could use Google Pay again. Remember, my phone wasn't actually rooted anymore, since the update. So I thought locking the bootloader should fix my problems. I did that with fastboot oem lock and then my phone was stuck in a fastboot loop. I tried every option in fastboot and would just end up right back there. I started looking for fixes and came across the MSMDownload Tool --> http://https://forum.xda-developers.com/oneplus-6/how-to/tool-msmdownloadtool-v4-0-international-t3798892. I downloaded the driver, it recognized my device, I downloaded the tool, then ran it. At 16 seconds, the download stopped and I got an error saying "Sahara communication failed." After looking up a fix that involved holding down the volume+ button, I decided I'd try again. This is where I f*cked up. I unplugged my phone without stopping the download, and that leads us to this very moment. My phone does not turn on at all. I have no access to fastboot or anything. My computer does recognize it when I plug it back in (I'm on Windows).
If you read this it's probably obvious that I only know enough to be dangerous and bricking my phone was inevitable. Feel free to call me an idiot, I only ask that you provide some useful information, preferably on the subject of getting my phone working again. Thank you all in advance. I hope this post isn't redundant. I didn't find anything on here that was a fix for my situation. I'm also open to contacting OnePlus if anyone thinks I should do that first. I genuinely thank anyone that takes the time to read/help! xd

Use the msm tool...doesn't use fastboot
Edit...nevermind

You need to get your phone to show up as "US8_BULK" like in the MSM thread you linked. You can do this even if your phone wont boot properly. I have done it multiple times before. When in the Qualcom flashing mode the screen will not light up at all.
Hold all the buttons until it resets. This could take up to 30 seconds of holding the buttons. The just follow the steps in the MSM thread starting with this one:
Power off the phone, then hold for 5 seconds vol up and plug the usb to computer. Now you have to see US8_BULK as new device connected and you can also see in device manager; if you can't notice it, repeat the process until you see it (power on, power off, hold...) there is a full youtube guide for op5 and it's the same process - (https://www.youtube.com/watch?v=PpLvmID1wdI)
Edit: It can take some practice to get the timing down, especially if your screen is not coming on at all. Just keep trying as you will be able to get into that Qualcom flashing mode unless there is physical hardware damage to your phone.

Jager said:
You need to get your phone to show up as "US8_BULK" like in the MSM thread you linked. You can do this even if your phone wont boot properly. I have done it multiple times before. When in the Qualcom flashing mode the screen will not light up at all.
Hold all the buttons until it resets. This could take up to 30 seconds of holding the buttons. The just follow the steps in the MSM thread starting with this one:
Power off the phone, then hold for 5 seconds vol up and plug the usb to computer. Now you have to see US8_BULK as new device connected and you can also see in device manager; if you can't notice it, repeat the process until you see it (power on, power off, hold...) there is a full youtube guide for op5 and it's the same process -
Edit: It can take some practice to get the timing down, especially if your screen is not coming on at all. Just keep trying as you will be able to get into that Qualcom flashing mode unless there is physical hardware damage to your phone.
Click to expand...
Click to collapse
Awesome, that worked! I kept seeing I needed to hold volume+ and power but holding both and power is what actually worked for me. Thanks a lot my friend

@lapitman, glad to see that you finally got it to work!

Finally! FRP bypass TB-X606F

After trying tons of different methods to bypass FRP on this TB-X606F without any success, I was FINALLY able to bypass it. I was not expecting this to work, so I wasn't documenting or taking screen shots. I typical solutions with sp_tool I was unable to get to work.
Was tested on
TB-X606X_RF01_220613
TB-X606X_USR_S300673_2206131545_V9.56_BMP_ROW
I only set the location of the 3 files as shown in the screen shot. Nothing else. Pressed "download"
Connected to computer while off, did not do anything initialy. Believe I pressed power + vol up or power + vol down and sp_tool immediately started the download, took maybe 30 seconds, green check mark when done.
https://imgur.com/AvdFpFs
uploaded: https://anonfiles.com/B382E8ncze/TB_X606F_FRP_Bypass_Verified_April_2023_Full_7z
hope this helps someone.
Edit: I did have the vcom drivers installed from here: https://www.getdroidtips.com/install-mediatek-mt65xx-usb-vcom-drivers/
Initially I was having a hell of a time trying to get it to boot into the correct mode. I was briefly able to see it connect with the vcom driver and com port, when sp_tool would attempt kinda sometimes to start, but would always fail.
Also make sure battery is 100%
Edit 2: During my initial resetting (tried the obvious first, wipe data/factory reset in recovery. Then used lenovos recovery tool which I had read would erase FRP. It did not, and also updated me to the newest version). I bought this tablet "new open box" on eBay, on the cheaper end, seller failed to mention was FRP locked. I figured ehhhh, easier just to flash it than start a case, send it back, etc etc... When I messing with SP flash tool, I was being slightly dumb and had a battery with maybe 30% charge, which didn't matter, since I knocked the tablet while it was attempting to start to do things and it became unplugged. Not sure if SP flash tool was doing anything, task manager showed it seemed like it was, but the program was mostly frozen and not giving me any info. Kept charging it up on the wall charger, but all I could get was a solid red light, no attempt to boot, and windows claimed unrecognized device. In hindsight, I'm wondering if I did not have the vcom drivers installed at the time, or correctly installed them (could have had a conflict, dunno) I was actually just going to RMA it since it looked nice and bricked. Left it on a charger for a week, was busy and just kinda forgot about it. I went to grab it the day I posted this and saw oh... 100% charged battery icon...... that's new... Turned it on, and I was back at the initial setup still FRP locked.
I also do not think that with the tablet off and plugging it in with with Vol Up an Down buttons pressed is correct. I haven't had that do anything for me. Cable aside, Power + Vol Down will get you into fastboot, Power + Vol Up *sometimes* would get me into recovery? It seemed pretty hit or miss. Tried a download mode jig, no dice, tried (forget what the name of it is...) a FRP/Boot/Programming cable thing, no dice on that either.
Again, I hoping this helps someone. I tried everything to get FRP bypassed, even shady shady "tools" and blatantly out of focus click bait virus linked YouTube videos.