Database Info

Bricked stuck on RSD mode 3

Hi everyone, so my father's tablet booted and bricked itself, it was working fine for about 2 months since last update. he says it froze on lock screen, he forced a reboot and then the problem happened
Problem:
Motorola xoom tablete MZ604 (wifi only) is stucked on Motorola Logo with "starting RSD mode 3" , if I press & hold " Volume Up & Power" it rebootss back into the same screen. If I press & hold "Volume up & power" then release and press Volume Down, it sticks at the Motorola Logo but without the "starting RSD Mode 3 ".
Already tried
Cant turn it off, get to fastboot or recovery options.
when displaying the Starting RSD mode 3, if I connect the tablet to my pc I hear the Dond dong and I can see the computer running the Motorola flash interface driver on the device manager BUT no adb devices are listed on command prompt or anything on Computer but C:..
I even tried bridgeing ( I believe that's the correct word in english) the micro usb cable so line 1 and 4 had the voltage, ( I saw this as a solution for having the "factory cable" ) but NO RESULT
all sort of combination of pressing volume and power buttons for 20 secs. no result
Background info
I was able to unlock it, root it , and I was running team eos wingray and the gpu OC and all that sweet stuff for several weeks my pc has the sdk tools and google usb driver package all updated.
Im desperate please HELP

mate, i literally just had this problem, right now! Was trying to do some fastboot stuff and something went wrong (obviously because otherwise i wouldn't be here). The way i solved it was:
Hard reboot it (power and volume up)
Then as the splash screen comes (even a bit before) keep pressing the volume down button repeatedly. With me the RDS mode 3 onwire thing then didn't come up, turns out it was in fastboot mode when I connected it to the PC to see if was in luck. Turns out I was. Then I fastboot flashed a recovery.img and now it's all gravy.
Hope this works for you

[Q] No Fastboot No Recovery .. Is it dead ?

While i was trying to install the latest official rom to my device (The new Padfone Infinity A86 T004) it is bricked, Now i am facing a very bad (miserable) situation.
When turning on the device it shows me the ASUS logo and in top of the screen a message says : ERROR: Can not boot Invalid boot image!!
And my big problem is that i can't access any of ADB, recovery mode or even fastboot. the phone is undetectable by my PC at all.
I don't know how to force fastboot ... if i can reach the beautiful fastboot mode i will be able to handle the next steps in the fixing journey.
I have red that as long as the device shows something it means that it is not totally bricked .. but how to get out of this situation?
Any suggestions ?

Sorry my englsih is´nt good.
So you can´t broken your phone with OTA Updates
You can delet all files and sysfile and the asus isn´t broken.
you just need patience.
make sure you have the correct driver
turn off your phone,
press vloume up and power, so the phone stay with boot logo, so you are in the fastboot mode.
there you can use my exploit btw the howto downgrade A86, but the downgrade dosent works.
so unzip the newest rom .zip out of asus page....
copy the boot.img and recovery.img in your minimal fast adb folder
so you can:
c:\ADB>fastboot -w ( really wipe all partions and data of your phone!)
c:\ADB\fastboot flash boot boot.img
c:\ADB>fastboot flash recovery recovery.img
copy the complete OTA Update Zip on your phone (internal sd or external is matter)
reboot phone and install the zip out of recovery.
there may be errors come to the first, if that should be the case
then repeat the case up to 3 times
I hope you can read and understand it .
if you need further assistance , please contact me at any time , like even on my homepage lange23.de
BerayekZ said:
While i was trying to install the latest official rom to my device (The new Padfone Infinity A86 T004) it is bricked, Now i am facing a very bad (miserable) situation.
When turning on the device it shows me the ASUS logo and in top of the screen a message says : ERROR: Can not boot Invalid boot image!!
And my big problem is that i can't access any of ADB, recovery mode or even fastboot. the phone is undetectable by my PC at all.
I don't know how to force fastboot ... if i can reach the beautiful fastboot mode i will be able to handle the next steps in the fixing journey.
I have red that as long as the device shows something it means that it is not totally bricked .. but how to get out of this situation?
Any suggestions ?
Click to expand...
Click to collapse

Thank you for your help.
The issue is that the phone now is not detected by the pc at all , i can not access the fast boot ...

Do you really pressed Volume up and Power at the same time, if startet???
If the phone during normal start at the stops bootlogo that's not fastboot!!!
Turn really off an than hold volume up an press Powerbutton, hold it up to boot logo.
then you are really in fastboot mode!
BerayekZ said:
Thank you for your help.
The issue is that the phone now is not detected by the pc at all , i can not access the fast boot ...
Click to expand...
Click to collapse

after turning off
when i press volume up + power button the phone vibrates and the asus logo displayed. then i release power button and keep pressing volume up button => and after 1 second an error appears ERROR: Can not load Invalid boot image!!
when pressing power button + volume down button a menu appears with two options 1.Enter recovery mode and 2.Exit update mode.
when choosing option 1 , the menu disappeared and the asus logo appears without the previous error message.
when choosing option 2 , the the menu disappeared and the asus logo appears and the previous error message.
all these cases the phone didn't go to fastboot mode and never detected by the pc.

when i press volume up + power button the phone vibrates and the asus logo displayed. then i release power button and keep pressing volume up button don´t keep pressing volume up,
fasboot mode only power & up, until the logo. Pressing this two to logo and then left them. the logo sty tuned in display so you re in fastboot
if you pressing up too jump in question menü,
if you pressing at startup power & down jumped directly into question menü, but this menü is wrong for you. you need only fastboot nothing more
BerayekZ said:
after turning off
when i press volume up + power button the phone vibrates and the asus logo displayed. then i release power button and keep pressing volume up button => and after 1 second an error appears ERROR: Can not load Invalid boot image!!
when pressing power button + volume down button a menu appears with two options 1.Enter recovery mode and 2.Exit update mode.
when choosing option 1 , the menu disappeared and the asus logo appears without the previous error message.
when choosing option 2 , the the menu disappeared and the asus logo appears and the previous error message.
all these cases the phone didn't go to fastboot mode and never detected by the pc.
Click to expand...
Click to collapse

keep pressing on volume up button is not jumping in question menü, but shows logo + error message (can not load invalid boot image)
also pressing them to logo then releasing also shows logo + the error message.
i am also uploading a video to youtube to verify..

https://youtu.be/uw4Esyppq_c

and without recovery its right?
And with error message and logo your pc find nothing new unkown devices?
CMCC Composite ADB Interface?
?
BerayekZ said:
https://youtu.be/uw4Esyppq_c
Click to expand...
Click to collapse

Yes, no recovery
And yes PC does not find any new devices

I can not understand it...
I once the boot.img deleted in the phone and also get such error message .
but my systems find an Android device and i can use the fastboot

Any way , a good news that the phone was only few days out of its package and i managed to return it back to the seller and will send to me a new one.
But i am really disappointed with ASUS not to make any unlock tool for the new padfone infinity.
Once, i believed that as long as there is no physical damage in the phone, there will be always a way around to fix it by fastboot. but it discovered that it is not correct and the fast boot itself can be damaged..
Any way thank you so much the only man helped me here sinus23.

I got this problem too
Me too
I got this problem

guys you got to do this , i am having yureka plus5510a no fastboot no recovery
bros no recovery no fastboot boot loop tried all combination not charging nothing what you think you guys are genius give me some let me tell you the whole thing how i ended here .. its all started with the king root(worst decision ) i wanted to flash twrp in my yu yureka plus 5510a no idead what " A" stands for then i used flashify from playstore and downloaded the twrp by the official twrp and flashed it with the flashify and boom boot stuck with no recovery some how removing battery and connecting the phone goes to the charging disp from where i did enable the fast boot but cmd was not able to identify adb devices nor the flashboot commands were working so i did same with win 10 powershell but nothing no devices , so i decided to use a method of ygdp , much hopes with this used ***** 5.1.153.00.P0.160604.8675_I02.def.CPB ******* dont know where the log file is but it was showing old bootloader error downloading and error and error and terminated at 2 % , then this one of your thread by unziping the official files and clicking on flash-all.bat file which he provided img(1) "some trials your phone will be all right " i tried with some "waiting devices error " message but then it just started something happened oem unlock blah_blah and then successful , tried to boot again but this time phone was automatically jumping into fastboot mode , then i finally tried one last time in that power shell thing by typing using cmd and applied fastboot code , even no devices was showing in powershell ,, but then i used some different code something like "fastboot ix902 recovery " and i was able to install a real old twrp recovery.. phone was showing the cyanogen loading ....but later after 1 hour i felt its stuck = + = but luckily recovery was working but but dont know why the buttons setup used to go in fastboot mode was now taking me in recovery,, and fastboot was no longer acessable , i was fine with it so i downloaded latest recovery from your respected thread file named as " twrp-3.0.2-0-20160604-UNOFFICIAL-tomato.img " i wanted to install nougat aosp so i thought its a nice idea to update the recovery first i. so i did the normal recovery update from the recovery it self , and now i guess that recovery was so old , the new one was kinda mindblower for the older one and booom no recovery , no fastboot , tried all the combination and came up with this one volume+ vol- and power shown img (2) same as boot logo but a small "official" tag
pls help i know this post dont suits your professional level , right now i havent slept from kinda like three days cause of exams and this sarcasm of being in trouble.. like my every devices is rooted o in onyx m in tab 2 , it frustating pls help ........i will edit this and make it more polite but if you are one who can solve this .. i am ready to donate man. cause u deserve it , it will gonna be learning experience with you i will be totally into the reply and pls dont scream for drivers i did installed coolpad driver adb drivers everything required i feel yureka is a real fake company their parts isnt distinguishable i did al the steps nicely and cleanly except the (kingroot ) and pls dont brag about the old threads , they didnt helped me much.. and probably why my phone is kinda dead

[Completed] Recovery only shows no command.

Hello.I have a Gigaset qv1030 with Nvidia Tegra 4 cpu.
The main idea is that i cannot enter the android due to not knowing the password.So i ''tried'' to went to recovery for a fresh wipe/factory reset.Problem is no key combination does start up recovery.
Power+volume up does only power up the tablet / Power volume down does nothing and freezes the tablet (need to hold power for it to resests).
Only thing that does work however is if i press Volume up and power , after first vibration pressing volume down (with all 3 button now pressed) goes me into bootloader (says Unlocked) , and have the following options continue , reboot , fastboot protocol , recovery kernel , power off.
Fastboot protocol only restarts the tablet at the same point back into the bootloader (useless i guess)
Recovery kernel brings up an green android sitting on it's back with a red triangle saying no command. (tried every combination found , nothing seems to work)
Adb debugging is not set up in the settings i guess , and fastboot does appear in device manager if connected to a PC but it just does not accept any drivers (neither the modified google_usb drivers with tegra enabled , neither some found on the internet trough drivescape).So no device is found by the PC .
Connecting it while on the password screen, PC does recognize the tablet but that's it . No adb recognition.
This is as far as i got , idk what to do . Please help?
# PS yes i did not own the tablet , i got scammed by someone , and hoped to do the best out of the situation.
i think it is android 4.2

Hello, and welcome to Assist,
I'm afraid we can't really help if you've lost/forgot your password. The password is there to protect the information that is contained in the file.
You'll have to create an account to post in the main forums if you have any other questions.
Good luck
Razvan

Neffos X-1 stuck in bootloop

Heya folks,
I have just attempted my first time flashing TWRP on my TP-Link Neffos X-1 following this guide: https://rootmygalaxy.net/twrp-root-...nd_Install_TWRP_Recovery_On_TP-Link_Neffos_X1.
Its looking kinda grim. It starts with the orange state Message and that the device will boot in 5 seconds, however after that it starts with an infinite bootloop. I also cannot access the Recovery (vol up + power), for it simply doesnt work anymore after the guide. When I plug it into my pc, it will automatically start with the bootloop (I can shut the phone off with vol down + power).
Attempting to get into fastboot mode over ADB (adb reboot bootloader), returns with the message error: device '(null)' not found. I think that is due to it not being recognized in the device manager(it doesnt show my phone anymore but unknown device). I tried to install the phone driver for the uknown device, however that keeps failing. I think its due to the phone permanently connecting and reconnecting to the pc.
So I'm wondering of what to do. I guess the biggest issue is that the drivers are not recognized, but as long as the phone keeps on restarting every couple of seconds i doubt i can properly install the driver. You guys got any ideas?

My guess is you haven't installed on Windows PC the appropriate Android USB Driver matching the device

I mean the appropriate USB driver had to be there for me to flash it with the TWRP in the first place, right?

Think I clearly said that the additionally required USB-driver has to be installed on Windows PC.

I have this one installed https://rootmydevice.com/download-neffos-usb-drivers/, is this the additionally required usb driver?

So far, despite what driver I pick for the device, it shows the code 10, device couldnt be started - probably because it never gets past the starting screen but keeps rebooting

slayingduck said:
Heya folks,
I have just attempted my first time flashing TWRP on my TP-Link Neffos X-1 following this guide: https://rootmygalaxy.net/twrp-root-...nd_Install_TWRP_Recovery_On_TP-Link_Neffos_X1.
Its looking kinda grim. It starts with the orange state Message and that the device will boot in 5 seconds, however after that it starts with an infinite bootloop. I also cannot access the Recovery (vol up + power), for it simply doesnt work anymore after the guide. When I plug it into my pc, it will automatically start with the bootloop (I can shut the phone off with vol down + power).
Attempting to get into fastboot mode over ADB (adb reboot bootloader), returns with the message error: device '(null)' not found. I think that is due to it not being recognized in the device manager(it doesnt show my phone anymore but unknown device). I tried to install the phone driver for the uknown device, however that keeps failing. I think its due to the phone permanently connecting and reconnecting to the pc.
So I'm wondering of what to do. I guess the biggest issue is that the drivers are not recognized, but as long as the phone keeps on restarting every couple of seconds i doubt i can properly install the driver. You guys got any ideas?
Click to expand...
Click to collapse
Try this TWRP file: TWRP_3.2.3_NeffosX1_TP902A_by_kiruha_21.img

The thing is, I cannot flash anything due to my phone constantly rebooting while inserted in the pc usb-slot. Neither ADB nor my device manager recognize the device and as mentioned before, I cannot install any drivers

slayingduck said:
The thing is, I cannot flash anything due to my phone constantly rebooting while inserted in the pc usb-slot. Neither ADB nor my device manager recognize the device and as mentioned before, I cannot install any drivers
Click to expand...
Click to collapse
Some MTK devices has this: Press both VOL+ & Power buttons. Only remove 2 buttons when you see Bootloader mode (recovery; fastboot; reboot system) or directly in the Recovery mode. Now you can use fastboot.
With the SPFT you can use same tip above. In the SPFT choose DOWNLOAD and plug USB device. Process to flash stock ROM or stock recovery.img & boot.img start.
If not start pugging USB: choose DOWNLOAD - press VOL- and plug USV device. You can try with buttons like only VOL- or VOL+ or combo buttons VOL+&VOL- or VOL-&VOL+ or other button combination.
You can try FIRMWARE UPGRADE too.
That's depend about LOCKED or Unlocked bootloader process that you made before actions!
If you unlocked bootloader so only need patience. If not so that's no good.

ADB Devices is EMPTY but phone is connected

My phone stuck on Realme Powered by Android.
I googled, installed ADB and connect my phone with my PC.
Then I do ADB Devices, but the list is empty.
Anyone know how to fix this?

If USB Debugging is enabled in Android settings then wrong Android USB driver in use: download and install the one matching your phone:
Download And Install Realme USB Drivers With How To Guide
From this tutorial, you could download and install the latest Realme USB Drivers onto your PC. The smartphone market is brimming with new offerings. Among
www.getdroidtips.com

adb daemon requires android booted. stuck at splash screen = not booted. force device in fastboot mode with Vol down + Power, install drivers as suggested and fix from fastboot.exe (no adb/usb-debugging required)

aIecxs said:
adb daemon requires android booted. stuck at splash screen = not booted. force device in fastboot mode with Vol down + Power, install drivers as suggested and fix from fastboot.exe (no adb/usb-debugging required)
Click to expand...
Click to collapse
According to Google's documentation - what hasn't changed over the last years - ADB consists of 3 softwares
1. ADB Server ( Desktop PC - establishes TCP connecion with Android Device )
2. ADB Client ( Desktop PC - sends ADB commands to Android Device )
3. ADB Daemon ( Android Device - processes ADB comannds sent )
So it should be clear that to execute ADB commands all these 3 softwares must be present and running.

So how to solve it if the phone only stuck at the powered by android screen?
xXx yYy said:
According to Google's documentation - what hasn't changed over the last years - ADB consists of 3 softwares
1. ADB Server ( Desktop PC - establishes TCP connecion with Android Device )
2. ADB Client ( Desktop PC - sends ADB commands to Android Device )
3. ADB Daemon ( Android Device - processes ADB comannds sent )
So it should be clear that to execute ADB commands all these 3 softwares must be present and running.
Click to expand...
Click to collapse
I tried with volume down + power but nothing happen.
aIecxs said:
adb daemon requires android booted. stuck at splash screen = not booted. force device in fastboot mode with Vol down + Power, install drivers as suggested and fix from fastboot.exe (no adb/usb-debugging required)
Click to expand...
Click to collapse
Any ideas guys?
Thanks in advance.

we don't know what is the reason for, you didn't tell anything what you did to cause this state. we don't know why you want adb access, I can only tell you that fastboot is available without usb-debugging.
power off device, check for proper key combo especially for your device model to enter fastboot mode.
https://www.hardreset.info/devices/realme/realme-5/fastboot-mode
if still no success, it might be fastboot mode is disabled intentionally (to prevent bootloader unlocking). in that case you are left with MSM Download Tool

Actually,you'l need to long-press the power button till the phone reboots then power + volume down IMMEDIATELY.

aIecxs said:
we don't know what is the reason for, you didn't tell anything what you did to cause this state. we don't know why you want adb access, I can only tell you that fastboot is available without usb-debugging.
power off device, check for proper key combo especially for your device model to enter fastboot mode.
https://www.hardreset.info/devices/realme/realme-5/fastboot-mode
if still no success, it might be fastboot mode is disabled intentionally (to prevent bootloader unlocking). in that case you are left with MSM Download Tool
Click to expand...
Click to collapse
So actually the phone have the volume up button and power button damage. at one time, it suddenly keep restarting. Then I let it be until the power fully gone. I ordered new volume and power button and change them.
Then I connect power supply to turn it on. But it seems it is stuck in "Realme Powered By Android" screen.
I tried to force shut down it and restart but still the same.
So I want to fast boot the phone but I am not successful.
Any Idea how I can do it?

sd369888 said:
Actually,you'l need to long-press the power button till the phone reboots then power + volume down IMMEDIATELY.
Click to expand...
Click to collapse
I tried 3 minutes pressing power button but nothing change. Then I restart using volume up + power button then immediately press volume down + power when it is turned off. But it seems it is the same too.