yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] iTzMac:
Odin is giving me an error when i try to flash the default ROM back to my phone

Hey there, I hope you can help I have a samsung galaxy note 3 (SM-N900T) and I went ahead and downloaded the ROM for my phone and tried to flash it and Odin gives me this error: see below

My initial problem was trying to use flash fire to flash an sdk file to my phone so when my phone began to flash and give me a wall of text, the phone rebooted and it was stuck on the T-Mobile logo, my phone can enter download and recovery mode, but in recovery mode after wiping my cache and "factory resetting" i rebooted the phone and I was still stuck on the T-mobile screen after turning on my phone. I have also tried Fastboot and i downloaded the application opened a command window and after i gave the commandit said waiting for device when my phone was plugged in and in download mode.

<ID:0/013> Added!!

<ID:0/013> Odin engine v(ID:3.1005)..

<ID:0/013> File analysis..

<ID:0/013> SetupConnection..

<ID:0/013> Initialzation..

<ID:0/013> Get PIT for mapping..

<ID:0/013> Firmware update start..

<ID:0/013> SingleDownload.

<ID:0/013> sboot.bin

<ID:0/013> NAND Write Start!!

<ID:0/013> FAIL!

<ID:0/013>

<ID:0/013> Complete(Write) operation failed.

<OSM> All threads completed. (succeed 0 / failed 1)
[Android Q&A, Help & Troubleshooting] bambus76:
gsmart gigabyte roma rx bootloop

Hello,i have problem with my gsmart gigabyte roma rx its stuck on logo screen and constantly restarting ,i can acces recovery mode with button because i was mess my cwm recovery i try to install latest cwm made it for t211 in recovery and first its writte install complete but whan i again restart in recovery mode nothing hapend its been still same old cwm but its still working, after that i use Rashr - Flash Tool and again try flash ziped cwm for t211 and than i lose my cwm,after that i make big big mistake i open Rashr - Flash Tool again and try to flash recovery.img from cwm backup folder after that my phone go to bootloop and constantly restarting,pc dont recognize my phone anymore so i cant even use adb to try fix,its anybody have some solution for me tanks.phone is rooted and have tick usb debuging.
[Android Q&A, Help & Troubleshooting] Helpme-1:
The Samsung Galaxy S4 i9506

I tried what you said, it says recovery mode at the left top corner and then it starts loading and when loading finishes the phone restarts, instead of going into recovery mode.
[Android Q&A, Help & Troubleshooting] Droidriven:
You don't have a recovery then. Does your device have a locked bootloader? Did you flash a recovery made for your specific model number?

Try flashing recovery again, use a different recovery or a different version of the recovery you have. You may have to flash a copy of your stock recovery.

My thoughts are you have a locked bootloader or you didn't use the right recovery, if your bootloader is locked then you won't be able to flash a custom recovery as long as it is locked, gotta unlock it if it is unlockable then flash recovery. If its locked then you'll have to flash your stock recovery or the entire stock firmware to get out of bootloop.
[Android Q&A, Help & Troubleshooting] Helpme-1:
It's Fixed

Fixed it, using Samsung kies. I reinstalled the original android (kitkat 4.4.2) this process wiped the phone completely. And when it turned on it did an automatic update and now i have android 5.0.1. I didn't use the specific model number in odin that's probabily why it didn't work properly.

Thank you for your help
[Android Q&A, Help & Troubleshooting] jakemalakas:
I'm having a problem with my phone .. I accidentally deleted my build.prop and my phone just restart.. :( now it won't pass the brand screen. I tried to wipe the data using recovery mode.. but still.. it's stuck.. can you please help me? :(
[Android Q&A, Help & Troubleshooting] Droidriven:
If you have custom recovery you can extract a copy of your build.prop from your stock firmware(if you're on stock) or extract build.prop from whatever custom ROM you're using(if you as using custom ROM).

Then use adb to adb push your build.prop to /system folder then reboot.
[Android Q&A, Help & Troubleshooting] ccie.muyiwa@gmail.com:
Hi, I have a Lenovo Yoga Tablet 10 HD+ (B8080-F). I got it bricked when I flashed a wrong ROM on to it. Before I got it bricked, it was rooted and with TWRP recovery. I have a TWRP backup made and still available. My OS is Android 4.4.2.

In one of the guide I was following, I was asked to remove all partitions, and create one big partition, which I did. So I have messed up the partitions. However, I can still get access to fastboot. I tried to flash TWRP to it, which it accepts but would not boot to TWRP recovery. I tried to flash boot without success.

What can I do to revive the phone? Is it possible to repartition again? Is there a tool for that?

I have tried flashing through QPST, but failed with error that it cannot switch to download mode. I hope you would be able to help me.

Looking forward to hear from. Thanks so much.
[Android Q&A, Help & Troubleshooting] Droidriven:
Read through all of the threads in the forum linked below and see if any seem like they can help with your issue. If you don't find any threads that help you then try posting a new thread in that forum about your issue or post your question in the most recently active thread in that forum that possibly applies to your issue.

developers.com/thinkpad-tablet/general?nocache=1&z=1675500595010817

And for future reference, don't flash anything that wasn't specifically built for your exact model number. Flashing stuff from a different device ends in bricking the device 95% of the time or more. It just isn't a good idea unless you see it documented and proven to work on your model number. Experimentation and taking chances by flashing wrong model number just to see if you can upgrade will go wrong for you 100 times more than it will ever go right for you. For every 1 device model that you get lucky and successfully flash with no issue, there will be 50-100 that didn't successfully flash. The odds are extremely against it ever working when flashing a different model number on your device.
[Android Q&A, Help & Troubleshooting] ccie.muyiwa@gmail.com:
Thanks so much, Droidriven. Please check again the correct url. The one posted above took me to a web page described as being under development.
[Android Q&A, Help & Troubleshooting] Droidriven:
Try this

http://xdaforums.com/thinkpad-tablet/general?nocache=1&z=2120360219851136&nocache=1

Pay attention when looking through all of the threads in that forum, they may be for other device models than yours but they may have the same issue as your device has, typically whatever they did to fix their device is what you need to do with yours, you just need to use files for your device if flashing is required instead of the file they used on their device, do you understand what I mean? Use same method they did but make sure you use your devices files if any are needed.
[Android Q&A, Help & Troubleshooting] ccie.muyiwa@gmail.com:
Thanks so much.

Will report back on my findings.

:highfive::good
[Android Q&A, Help & Troubleshooting] ccie.muyiwa@gmail.com:
Hurraayyy! I got my Lenovo B8080-F tablet back. I got it up again. I bricked the device since May 16. I have been searching for a solution since. What a wonderful feeling....

Thanks to Droidriven for his encouragement and pushing me in the right direction where to look. I got inspired from one of the threads on Fastboot commands. I was inspired by the command "fastboot boot recovery.img". I reasoned that since I have TWRP backup, I would be able to restore the backup, if I can get into TWRP recovery. I have tried all to get the recovery flashed, but no way, as I re-partition the device memory. Then yesterday, the inspiration to try "fastboot boot" command came. I tried with one stock recovery I downloaded and it worked. Waoh! That opened my eyes.

So this morning, I got the TWRP recovery for the device and use "fastboot boot" command, and there staring me in the face is TWRP on my device. I restored my TWRP backup and waooH, my device came back to life.

Thanks to the XDA community.
[Android Q&A, Help & Troubleshooting] Droidriven:
Good to go, glad you got it working, just remember to learn from the experience that got you there to begin with and make sure you don't make the same mistake again.
[Android Q&A, Help & Troubleshooting] jhu2006:
Can I fix this phone or is it bricked?

I posted this in one of the threads in the Atrix HD forum, but I think those forums are dead. I was hoping to someone may be able to guide me a bit on what my options are with regard to my phone.

I have an Atrix HD which gets stuck on the AT&T logo when booting. It had been acting up for a little while before it did this. Just about any app I would try to open would either not open at all or it would start to open and then pop right back to the home screen. I would have to restart the phone to get an app to open, but they would still be unstable and not work for long.

I have researched for hours on end over the past week and tried just about everything I could. One of the problems is I'm a complete noob when it comes to tinkering with Android. The phone is not rooted and the bootloader I assume is locked since I haven't played with anything. Stock ROM running 4.1.1. I added very few apps on the phone maybe 3-4 over the 3 years I've had it. I have wiped the cache and have done the factory reset from recovery, but still no luck.

I have tried to use RSD Lite and Minimal ADB and Fastboot to see if I could download the stock ROM online and then use one of those to push it to the phone, but the phone doesn't appear in the device window in RSD Lite, and when I type "adb devices" at the CMD prompt in ADB the list of devices attached is empty unless I choose the option in recovery to "apply update using ADB" in which case it says "TA2490D74Q sideload". I downloaded the updated drivers from Motorola. I was going to try and use MythTools, but I thought I read somewhere that the bootloader needed to be unlocked to use it. Can I use MythTools on a completely stock phone?

I don't know if USB debugging is enabled. I don't remember going into the developer options and doing so myself. Is there a way to tell through either recovery or fastboot?

I have seen countless websites online say that phones stuck in bootloops are considered "soft bricked" and for the most part should be fixable, but for someone whose phone is not rooted, and bootloader not unlocked, is that really the case? I am long overdue for an upgrade, and ordinarily would just do that, but the problem is I am currently out of the U.S. and phones where I am now are ridiculously priced compared to the U.S. so I would prefer it if I could at least fix this phone until I can get back and get a new one.

Sorry for the length. I wanted to add as much useful info as I could. Any suggestions/help would really be appreciated. This s&%t can be really frustrating when everything you try turns out to be a dead end.
[Android Q&A, Help & Troubleshooting] Droidriven:
So a google search for:

"Return to stock (your model number)"

That should give you links to your firmware if it exists, the tools you'll need to flash it and instructions.
[Android Q&A, Help & Troubleshooting] falafelwiener:
intstructions to complicated, got **** stuck in microwawe
[Android Q&A, Help & Troubleshooting] Droidriven:
What model number is your device?

What did you do to cause an issue?

What state is the device in right now?
[Android Q&A, Help & Troubleshooting] Demure Deviant:
bricked phone with no recovery, no fastboot access

I just bought a new android phone running Lollipop 5.1. flashed custom recovery (a modified recovery based on clockword mode recovery). Then flashed a buggy custom rom. In which many of the functions does not running properly Including many options in settings. Power off restart is not working, plus; theres no baseband installed which effects the inactivity of the SIM, wifi, bluetooth and microsd card also not shown as well.

Accedently i was trying to install the original clockword mode recovery with the "Android One Toolkit". there's no original clockword mode recovery for the phone the only one is i have flashed before.

Somehow it erased the recovery and do not installed the new recovery i was trying to install. There's no recovery anymore, when every i try to boot into recovery by hardware buttons it never starts and brings the system to that buggy custom rom. either theres no way to boot into bootloader or fastboot. I have tried everythihng including many apps "Rom manager" "king root" for gaining access root but all are failed to do the task due to the non availability of wifi or internet on the phone. this buggy custom rom is not doing anything properly which can leads me to the solution, not even rebooting. I have to forced reboot it by pressing buttons vol+,vol- and power button. after the options came on to the screen. "vol up for recovery" vol down for factory reset options". both options bring me to that buggy custom rom after some time.

I am stuck, Is there any way to get back to the phone. i have never used the backups before flashing. thanks in advance!! the phone is "Qmobile Z10" MTK 6753/35 i think the custom recovery i flashed waas "Clarvik Recovery etc" i forget the exact name but after the name was written "A recovery based on Clockword mode recovery" the custom rom i currently have in may phone is "experience rom for TT175 by EMRESAYGIN"

thanks in advance
[Android Q&A, Help & Troubleshooting] Droidriven:
You can try finding and flashing another recovery, or you can try finding a copy of your stock firmware and flashing the device back to factory system.
[Android Q&A, Help & Troubleshooting] Demure Deviant:
but how can i flash another recovery. coz i dont have access to fastboot/bootloader and not even to the recovery. coz custom recovery i just had flashed gone and erased.:rolleyes:
[Android Q&A, Help & Troubleshooting] Droidriven:
Try using adb and a dd command to flash your recovery.IMG if you know which mmcblk0 your recovery goes in.
[Android Q&A, Help & Troubleshooting] Demure Deviant:
Can you please guide me that how can i find my mmcblk0 and how can i flash recovery by using dd command.:angel:
[Android Q&A, Help & Troubleshooting] Droidriven:
You will have to do some reading and searching about your model number to find the mmcblk0, then you get your recovery.img and make sure it is renamed to "recovery.img", put it in your PC somewhere

Then Google "How to dd recovery.img", then you look at how the dd command is "written", in the path of the command you enter where the recovery.img is stored on PC then you enter where you want the recovery.img to be placed on the device. Then open a adb terminal, type your dd command, you must get the command 100% correct or you will only damage the device worse.

I'm not gonna hold your hand and walk you through this. I've given you the things you need to know, you just need to do some searching and reading to fill in the blanks and understand what I'm referring to.
[Android Q&A, Help & Troubleshooting] pshyco<me:
SOME HELP?

http://xdaforums.com/grand-quattro/help/stuck-recover-loop-cwm-bootloop-t3465826:eek::eek::eek::eek:
[Android Q&A, Help & Troubleshooting] Demure Deviant:
Yup thanks. but whenever n where ever i got stuck. can i ask here from you? :confused:
[Android Q&A, Help & Troubleshooting] pshyco<me:
HELP

http://xdaforums.com/grand-quattro/help/stuck-recover-loop-cwm-bootloop-t3465826#post68788956
[Android Q&A, Help & Troubleshooting] Droidriven:
Maybe you didn't understand, I said I wasn't gonna hold your hand to do this..

It's very complicated so that means you would ask help with each and every step and I'm not helping you with every single step you make. That would be me doing the work with your hands going through the motions. If you can't do it or don't understand then take the device to a professional and pay them to fix it. Otherwise, do some research, learn some things until you understand what you need to do.

In the future, don't do things that you don't know how to fix.
[Android Q&A, Help & Troubleshooting] Demure Deviant:
yup thanks for the help but some how i flashed the stock rom downloaded from the internet from the given link to my qmobile z10 mtk6753, using SP flashtool

https://docs.google.com/uc?export=download&confirm=45sO&id=0B_Wm2RQP1PtfcnVpaG1oVmhPLTQ

and it was successfully flashed into the phone by a tick mark. after that the phone doesn't turned on by pressing the power button neither by forcing it to be in the selection of recovery or factory restore options by pressing vol up vol down n power. now what? is it hard bricked? Not turning on. just black screen. no boot logo, no recover or factory reset etc nothing.

Now when ever i connect the phone with the pc. it doesn't recognize the phone despite all drivers have been installed already. and gives unknown device. when i opened the device manager it gives this "Unknown USB device(Device descripter request failed)". I have googled it and found some solution to this generic problem by changing the power options etc and all the solutions on the internet. but it remains the same. Is there any solution to this problem is it the hard brick? if it is how can i overcome this problem.?:(:confused: thanks in advance
[Android Q&A, Help & Troubleshooting] jlorn21:
bootloop after reflash

hello guys, :confused::(:(:(:(

i hope somebody help me, i just reflash my aquaris 5 using sp flash tool 5.13.52.200 it went complete, but after i boot up it still bootloop even if i used the right firmware( Latest for my smartphone). someone can give me how to fix this. Realy appreciate it. Thnxs in Advance.
[Android Q&A, Help & Troubleshooting] somadsul:
Try Factory reset from recovery once

sent from my Tencent OS G900H
[Android Q&A, Help & Troubleshooting] ignite619619:
i have samsung galaxy tab 3 neo

and the tab is going directly under recovery mode repeatedly

and i cant find any solution

whenever i restart the phone it goes in recovery mode
[Android Q&A, Help & Troubleshooting] Droidriven:
See if it will boot to download mode(volume down+power), if so, find your stock firmware and flash that in Odin.
[Android Q&A, Help & Troubleshooting] ankitsteve:
Help

I have a Karbonn Titanium Octane plus which is stuck in boot loop . I cant go into recovery mode .

Already reinstalled orignal Rom but no luck.

Just to tell it started vibrating one day in pocket and when I removed battery and restarted it this happend.

Thank you
[Android Q&A, Help & Troubleshooting] BoraxJake:
Bootloop that can't be reset or wiped

Hi I am stuck in a Bootloop no matter what I do. I have tried more than a dozen ROM's and a few different CWM's. All help messages and tutorials say "wipe Dalvik cache, wipe cache and factory reset then its fixed" but no matter how many times I do this it is not fixed. Everytime I install a different ROM for my Mlais M9 it is the same and no wipe or reset allows the phone to get past the bootloop. Is there something I am not understanding as have read dozens of Fix It posts??

I have used ADB to install custom Recovery. Using Phils Touch for Mlais M9 tried both OPT1 and OP2. Have many ROM's on Sdcard in phone. I "clean to install a new rom" each time. Then install ROM, Wipe Cache, Wipe Dalvik, Factory Reset then Reboot and BOOTLOP. Every time.

Thanks for helping.
[Android Q&A, Help & Troubleshooting] jess00001:
omg i forgot to backup before rebooting. what do i do now? i'm stuck in a bootloop
[Android Q&A, Help & Troubleshooting] Droidriven:
First, it depends on what you did that caused the boot loop, some are easy to fix, some not.

Second, what device model number do you have?

Can you still get to recovery?

Can you boot to fastboot or download mode, whichever you have?

I DO NOT PROVIDE HELP IN PM, KEEP IT IN THE THREADS FOR EVERYONE TO SHARE
[Android Q&A, Help & Troubleshooting] jess00001:
I rooted my kobo arc using github.com/zhuowei/arctic. then reboot it using cmw recovery. That's when the bootloop started, I follow some tips i saw online and click wipe data/factory reset when that didn't work I also wiped out the cache then clicked reboot system now. But nothing work, Still stuck in the bootloop. I waited like an hour after that. then my tablet's screen when black. I connected my charger and it went to the charging screen. I can't go to recovery now. Though If i hold the power button long enough it will go back to bootloop screen :confused:

---------- Post added at 11:58 AM ---------- Previous post was at 11:02 AM ----------

update i can still go to recovery screen but with android system recovery
[Android Q&A, Help & Troubleshooting] med007:
Nexus S

Soft Brick

Not rooted

Not Unlocked

Stock settings from factory

Did over the air update (this occurred years ago)

Start rebooting randomly.

Eventually went in to a boot loop (I eventually put the phone in a drawer thinking I needed a hair dryer to continue troubleshooting).

I was trying to save a photo in the downloads (from SMS) folder (this was prior to google photos backing up the downloads folder)

Therefore I did not want to do a factory reset.

I started working on the phone again this weekend after years of sitting in a drawer. I believe it is now software related and not hardware related.

I can get to Recovery page.

I deleted the cache.

Still in a boot loop.

I watched a few youtube videos on getting Samsung phones out of boot loop... nothing working

I get the google sign and then the Cross or X (4 colored old nexus symbol?) and then it repeats

I was hoping to use ADB to somehow install and update to get the operating system to work again given I believe that it is software related given it occurred after an update.

I did also try replacing the battery.

I even tried a hair dryer to heat up the connections.

I cannot get to safe mode.

I tried Nexus Root Toolkit by Nugfresh, but it seems like I was stuck because I wasn't rooted.

I tried saying i'm in the softbrick and to do a no-wipe... but the phone wasn't detected in the USB drive (windows 10 surface pro 3).

Do I need to install a driver to detect the phone?

Thank you for your help.

I tried finding the one-click system, but the google code file doesn't exist anymore.
[Android Q&A, Help & Troubleshooting] pankaj18:
how to fix bootloop because of font change. my phone is stuck in boot animation and because of that i cant get su root permition in android commander an adb and my phones power button is broken please help. thanks!
[Android Q&A, Help & Troubleshooting] Droidriven:
do a Google search for:

"Return to stock Nexus S"

find the stock firmware for your specific model number of Nexus S then find instructions for flashing it.
[Android Q&A, Help & Troubleshooting] med007:
will this delete the data?

will this delete the data?
[Android Q&A, Help & Troubleshooting] Droidriven:
Probably, use adb to create an adb backup or you can try flashing a custom recovery then using it create a backup then flash the device with stock firmware then flash the custom recovery again then use custom recovery to restore your data using the advanced restore feature to only restore data and nothing else.
[Android Q&A, Help & Troubleshooting] devrieshh:
recovery bricked(?)after flashing cwm doogeex5

(SOLVEDdownloaded inifix HOT 2 6_0 from http://www.needrom.com/category/doogee/serial-x-doogee/x5-doogee/ flashed it and the twrp recovery from the rom worked.) After flashing cwm with sp_flash_tool on my doogeex5 MTK6580 i got an android logo with warning sighn(see picture) with some chinese text...

My phone isnt rooted so maybe thats wy.

I cant flash the original nor other,twrp recovery.

i can flash other roms,but recovery stays like it is , only the chinese text dissapeard.

Tryed to root the phone with king root,but after 27%rooted it failed to continue...

thanks for some advice
[Android Q&A, Help & Troubleshooting] lamphoe:
USB Debugging disabled

My phone is stuck in a bootloop (or bricked idk) I cant enter recovery for whatever reason so what do I do?