Related
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
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
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 .
I did however finally installed the drivers using the drivescape driver with extracting driver , restarting with no driver signature and installing the driver using device manager update driver.Fastboot still does not see the tablet.
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
Duplicate, Please see my response from here:
http://forum.xda-developers.com/general/xda-assist/recovery-command-t3519232
Closed.
Hi all!
Long story short, basically my OnePlus Nord gen 1 is bricked (no recovery, no ROM). In the current state all it is able to do is boot into the bootloader. The bootloader gives several 'options' such as "boot to recovery", and more importantly, "power off". But no matter what option I choose, the phone ends up rebooting back into the bootloader.
I've tried to follow guides on XDA instructing how to unbrick the device, to no avail. The main guide I'm trying to follow is the MSMdownloadTool guide, but that requires me to power off the device to enter EDL mode (which it isn't doing).
The device seems to be stuck in fast boot mode, but isn't using fastbootd so I can't make changes to critical partitions. Since it is stuck in fastboot mode, adb commands don't work. I've tried reflashing the recovery, but that didn't work. I've tried clearing cache but there I'm running into 'cannot generate userdata' (fastboot erase cache spat out "failed; check device logs").
As for hardware buttons, using volume down + volume up or even volume down+power does nothing, volume up + power button or holding all 3 just restarts the bootloader, and holding just the power button does nothing except for repeatedly select "start"(causing it to reboot back into bootloader).
I feel if I can just get it into EDL mode somehow, everything else will fall into place. Any help at all will be much appreciated
zeuses23 said:
Hi all!
Long story short, basically my OnePlus Nord gen 1 is bricked (no recovery, no ROM). In the current state all it is able to do is boot into the bootloader. The bootloader gives several 'options' such as "boot to recovery", and more importantly, "power off". But no matter what option I choose, the phone ends up rebooting back into the bootloader.
I've tried to follow guides on XDA instructing how to unbrick the device, to no avail. The main guide I'm trying to follow is the MSMdownloadTool guide, but that requires me to power off the device to enter EDL mode (which it isn't doing).
The device seems to be stuck in fast boot mode, but isn't using fastbootd so I can't make changes to critical partitions. Since it is stuck in fastboot mode, adb commands don't work. I've tried reflashing the recovery, but that didn't work. I've tried clearing cache but there I'm running into 'cannot generate userdata' (fastboot erase cache spat out "failed; check device logs").
As for hardware buttons, using volume down + volume up or even volume down+power does nothing, volume up + power button or holding all 3 just restarts the bootloader, and holding just the power button does nothing except for repeatedly select "start"(causing it to reboot back into bootloader).
I feel if I can just get it into EDL mode somehow, everything else will fall into place. Any help at all will be much appreciated
Click to expand...
Click to collapse
You might be able to enter EDL mode by opening the device and using a jumper to touch certain contact points on the board and force it into EDL mode. I don't know your hardware so I don't know which points to tell you to use the jumper on, you'll have to do some research to figure that out based on the specific device you have.
zeuses23 said:
The device seems to be stuck in fastboot mode, but isn't using fastbootd so I can't make changes to critical partitions.
Click to expand...
Click to collapse
unrelated. you can flash super.img from fastboot. flashing critical partitions maybe needs unlocking.
Hello if this can help my device was dead , not even fastboot or recovery was working and was bootlooping. What i did is installing MTK authentication bypass ( i dont know if your phone is mtk cpu ) , then i instaled libUsb driver that came packed with that tool.
Then you open libusb driver installer, and when you keep pressed power + vol down to enter Brom mode, it should detect a com port that disappear in few seconds, what u need to do is click install driver as soon you see that com port appear.
Now you open the bypass tool with phone disconnected, click on bypass, and then connect the cable, now enter Brom mode with power + vol down, and the tool will say Success.
Now your phone is ready to use with any flash tool ,like sptools.
Hope this helps.
Droidriven said:
You might be able to enter EDL mode by opening the device and using a jumper to touch certain contact points on the board and force it into EDL mode. I don't know your hardware so I don't know which points to tell you to use the jumper on, you'll have to do some research to figure that out based on the specific device you have.
Click to expand...
Click to collapse
Hey, thanks for the suggestion! But i would very much prefer not to open up my device. I've also heard that there is an EDL cable, but I don't know if that'll work either. Lets see
aIecxs:
unrelated. you can flash super.img from fastboot. flashing critical partitions maybe needs unlocking.
Click to expand...
Click to collapse
Thanks for your reply! A silly question, but what does super.img do? I tried flashing the critical partitions after running "fastboot oem unlock_critical", but that still gave me the error.
innergat:
Hello if this can help my device was dead , not even fastboot or recovery was working and was bootlooping. What i did is installing MTK authentication bypass ( i dont know if your phone is mtk cpu ) , then i instaled libUsb driver that came packed with that tool.
Then you open libusb driver installer, and when you keep pressed power + vol down to enter Brom mode, it should detect a com port that disappear in few seconds, what u need to do is click install driver as soon you see that com port appear.
Now you open the bypass tool with phone disconnected, click on bypass, and then connect the cable, now enter Brom mode with power + vol down, and the tool will say Success.
Now your phone is ready to use with any flash tool ,like sptools.
Hope this helps.
Click to expand...
Click to collapse
Hey innergat, unfortunately I believe my phone has a qualcomm chipset, so this probably won't work
Dynamic partitions are logical partitions hosted in physical super partition. logical partitions can only be accessed from fastbootd, physical partitions from fastboot.
To enter EDL mode try selecting power off and then immediately hold volume up + volume down.
Hi. After installing ROM from TWRP and restart, i got this as a bootloop. The problem is, it cannot boot into recovery despite the recovery word at the bottom left. So it looped on this page over and over. I tried all the known buttons and i cannot find anything similiar to my problem elsewhere. Anyone can help?
fireflyzzz said:
Hi. After installing ROM from TWRP and restart, i got this as a bootloop. The problem is, it cannot boot into recovery despite the recovery word at the bottom left. So it looped on this page over and over. I tried all the known buttons and i cannot find anything similiar to my problem elsewhere. Anyone can help?
Click to expand...
Click to collapse
A bit more information , like phone model , how and which version you flashed.
otherwise pull battery (or wait to drain) charge and reboot back to download mode and reflash recovery.
this time making sure you do it right.
atleast ths is my procedure on samsung phones
dandudikof said:
A bit more information , like phone model , how and which version you flashed.
otherwise pull battery (or wait to drain) charge and reboot back to download mode and reflash recovery.
this time making sure you do it right.
atleast ths is my procedure on samsung phones
Click to expand...
Click to collapse
Hi. Phone model Realme C2. TWRP flashing Realme UI. I think i made the mistake of formatting first or something before installing the ROM. I did took off the battery cable. Just that when the phone is powered on thru the cable, it also powered into the pic shown, which is a bootloop but can't boot into recovery. I believe this is an extremely rare situation. I'd be happy if it can boot into adb, then i can at least install back the original phone ROM.
Sometimes i managed to press and hold (vold down power) at the right time. on samsung phones
(right after it screen goes black i think) to get in to download mode during some bootloops.
But i am unfamiliar with fastboot mode i think your phone uses.
Try holding the physical buttons needed for you phones downloadmode/fastbootmode
while it is off and then plug the cable in ? just a guess though.
first google links for 'Realme C2 fastboot physical buttons'
How to Boot Realme C2 Recovery Mode and Fastboot Mode - Droid Recovery
Want to Boot Realme C2 into Recovery Mode or Fastboot Mode or Bootloader Mode? Then follow the instructions listed on this page to successfully Boot Realme C2 to Fastboot Mode or Recovery Mode.Realme C2 Recovery Mode allows the users to perform advanced operations like flashing Root Package and...
droidrecovery.com
https://www.hardreset.info/devices/realme/realme-c2/fastboot-mode/
dandudikof said:
Sometimes i managed to press and hold (vold down power) at the right time. on samsung phones
(right after it screen goes black i think) to get in to download mode during some bootloops.
But i am unfamiliar with fastboot mode i think your phone uses.
Try holding the physical buttons needed for you phones downloadmode/fastbootmode
while it is off and then plug the cable in ? just a guess though.
first google links for 'Realme C2 fastboot physical buttons'
How to Boot Realme C2 Recovery Mode and Fastboot Mode - Droid Recovery
Want to Boot Realme C2 into Recovery Mode or Fastboot Mode or Bootloader Mode? Then follow the instructions listed on this page to successfully Boot Realme C2 to Fastboot Mode or Recovery Mode.Realme C2 Recovery Mode allows the users to perform advanced operations like flashing Root Package and...
droidrecovery.com
https://www.hardreset.info/devices/realme/realme-c2/fastboot-mode/
Click to expand...
Click to collapse
Hi. Nope. It will still boot into the screen on the pic, and it will loop over and over again. I took off the battery cable but when i plug the USB cable, it will also reboot into the pic with bootloop.
I felt that this is a very rare case of the phone screwing up. My initial intention was to install a light rom so i can use the extra space (even after root, App2SD doesnt work). Sigh.
if you remove the cable and let it drain , when it is off and you hold correct buttons for download/fastboot mode
and then plug the cable in it goes it to recovery mode ?
and keep trying press and hold different time in the loop , around the point of black screen/reboot point,
just before/at/and after.
dandudikof said:
if you remove the cable and let it drain , when it is off and you hold correct buttons for download/fastboot mode
and then plug the cable in it goes it to recovery mode ?
and keep trying press and hold different time in the loop , around the point of black screen/reboot point,
just before/at/and after.
Click to expand...
Click to collapse
Sorry, nope. It will boot into the Realme Logo and the recovery mode word on bottom left as shown in the pic. And then bootloop into the same thing again. It cannot enter recovery mode. I tried every combination of buttons with the battery attached and without. I believe the recovery section is erased, or it might be in another part of the memory but inaccessible.
fireflyzzz said:
Sorry, nope. It will boot into the Realme Logo and the recovery mode word on bottom left as shown in the pic. And then bootloop into the same thing again. It cannot enter recovery mode. I tried every combination of buttons with the battery attached and without. I believe the recovery section is erased, or it might be in another part of the memory but inaccessible.
Click to expand...
Click to collapse
are you sure you are trying button combinations for download/fastboot mode (not recovery).
we know recovery is fubared. so is system most probably.
you need to get in to download/fastboot to reflash recovery or stock firmware .
(hold buttons till you see download/fastboot , not just push and let go)
try correct button combination at all the different times in the loop.
and i had a siimmular problem once with a phone turning itself on and looping,
(turned out to be a glitchy power button , try fiddling with that , excersize it to get to unbind if it is)
dandudikof said:
are you sure you are trying button combinations for download/fastboot mode (not recovery).
we know recovery is fubared. so is system most probably.
you need to get in to download/fastboot to reflash recovery or stock firmware .
(hold buttons till you see download/fastboot , not just push and let go)
try correct button combination at all the different times in the loop.
and i had a siimmular problem once with a phone turning itself on and looping,
(turned out to be a glitchy power button , try fiddling with that , excersize it to get to unbind if it is)
Click to expand...
Click to collapse
Yes sir, i did. Tried all button combination at different times. The only thing that worked is the on/off button. When it is on, i press and hold a long time, and let go when the screen is off to turn off. And to turn it on, i press and hold a long time until the screen is on to turn on.
As noted, i might have screw up the installing 3rd party ROM process. I screwed up many times earlier, but i managed to reinstall back the original ROM because it was in adb. And now it isn't. Phones in my country aren't cheap, so if possible, i'd like to save this phone. My initial purpose to install a 3rd part ROM is to make use of the extra internal memory space (i rooted initially but i wasn't able to use App2SD).
so when you hold the power button and it turns off. then you need to use the
combination of buttons for fast boot to turn it on , not just power button .
make sure you have the correct buttons , double , tripple check with the correct buttons
and when to let them go.
also look at
Hard Brick Fix Realme C2
Requirements PC Bypass Extracted OFP Sourceforge or AndroidFileHost C2 Keep restarting from download mode to keep c2 in download mode run brom.bat then connect device holding volume up, down & power after that install drivers (you can install...
forum.xda-developers.com
maybe you need to start from beginning