my device was working fine after replacing the battery (0onite 2070mah) and screen. i lend the phone to a friend, when he tried to charge the device, it went to boot loop.
so my phone is stuck on boot loop ( it shows the blue motorola ( a google company) logo,on and off)
device wont charge,can only be on when connected to charger or laptop.
when i go to recovery mode,it blacks out in a second, then goes to startup
i dont know what to do. i got some flash tools from youtube.
Motorola drive
Driver Installation 6.4.0
and a firmware restore lock and more (cant post link)
help!
its not a rooted phone......
well,i dont know wich stickies i should read about my situation?
Related
Dear android experts,
I had CM 5.0.7 installed on my HTC Dream, and I stupidly installed ROM Manager, wanting to upgrate to CM 5.0.8, and used the application to do a backup - after I clicked the 'backup' function, the phone rebooted, and is now stuck on the startup logo (and has been stuck for the last hour). I have already tried pulling out the battery and booting the phone into recovery mode, however it cannot access recovery mode, and still hangs at the startup logo. Is there any way to get past this startup logo, or is there no hope for my phone? Is there any way to push the phone into recovery mode via adb? I am a complete amateur, who follows step-by-step instructions - please help me!
P.S. If this tells you anything, while my phone is stuck at the startup T-mobile logo, if I plug in the USB cable, a message on a red background appears at the top of the 'G1 T-mobile' logo, saying 'FASTBOOT USB'.
P.P.S. In case this is a detail that could help me, while my phone is in Fastboot Mode, I have four options available:
HBoot Mode
Reset Device
Restart to HBoot
Power Down
Could any of these help me?
yeah:) said:
Dear android experts,
I had CM 5.0.7 installed on my HTC Dream, and I stupidly installed ROM Manager, wanting to upgrate to CM 5.0.8, and used the application to do a backup - after I clicked the 'backup' function, the phone rebooted, and is now stuck on the startup logo (and has been stuck for the last hour). I have already tried pulling out the battery and booting the phone into recovery mode, however it cannot access recovery mode, and still hangs at the startup logo. Is there any way to get past this startup logo, or is there no hope for my phone? Is there any way to push the phone into recovery mode via adb? I am a complete amateur, who follows step-by-step instructions - please help me!
P.S. If this tells you anything, while my phone is stuck at the startup T-mobile logo, if I plug in the USB cable, a message on a red background appears at the top of the 'G1 T-mobile' logo, saying 'FASTBOOT USB'.
P.P.S. In case this is a detail that could help me, while my phone is in Fastboot Mode, I have four options available:
HBoot Mode
Reset Device
Restart to HBoot
Power Down
Could any of these help me?
Click to expand...
Click to collapse
i have the same problem.............. did anyone ever help you out??? if the did let me know please!!!
alroco20 said:
i have the same problem.............. did anyone ever help you out??? if the did let me know please!!!
Click to expand...
Click to collapse
This thread is old, and OP is ignorant and wants to blame ROM Manager for his own problems. If you can't get into recovery, chances are you are using one built for another phone. Find the one for the G1.
Or ran into the know issue of cm5.0.7 that fash_image sometimes (more than not) fails.. thus applications using it sometimes fail.
But you have danger spl right? So flash the recovery via fastboot.. and if you don't have fastboot/adb and intended to run these custom roms its about time you installed it.
Hello guys, I have a big problem with my GT-I9001,
I have installed the clockworkmod and cyanogenmod by ivendor, (Alpha 7) http://forum.xda-developers.com/showthread.php?t=2000828
If I try to start my Galaxy it stuck's on the Splashscreen where I can see the Galaxy S Plus and the Cyanogenmod logo. After a few Minutes the screen goes of but you have to take the batterie out of the Handy to start it again.
If I try to boot into recoverymode, after the samsung logo the screen goes off, and again I have to take the batterie out.
At both Situations, if i touch the menu or return button it lights up, but not off anymore. At Situation 2 after a few Minutes.
The Download mode still works but if I try to Flash, for example with a Stock Firmware, it seems to go through with no problem, but instead of rebooting it only gets a blackscreen.
When i have flashed it and I start it the Splashscreen still has the Cyanogenmod logo on it, also if i flashed it with a Stockfirmware.
Another thing is, that if i try to charge my Smartphone, the normal shown batterie is stuck too.
Some people already mentioned the BroodRom, but on the download mode appears the Sentence: MMC boot: MBR read failed, and at Booting normaly is no change.
I tried to connect with adb to the Handy while it is on that black screen. It works, but if i try to enter: recovery --wipe_data, but in the cmd it only says: "/sbin/postrecoveryboot.sh not found" and nothing changed.
So this is the List of things that don't work or i already tried. I hope you guys will find a solution. If not i want to ask what Smartphone you would buy.
Problem found
I searched the whole net and i think i found the problem, It seems to be the memory controller.
I came to this because if i pushed something onto my Handy via adb it was there only till a restart. And some communities tell me, that the problem can be solved by exchanging the memory controller. But i don't think i can do that.
Hi there,
Yesterday I was trying to copy a movie on the internal memory of my device. The device froze and when I forced restart the phone, it just got stuck on the bootloop screen. The phone shows the Moto Logo and then vibrates and black screen and boots again.
I tried to go into recovery but when I press recover, it just reboots. Let me mention that bootloader is locked.
When I took it to a mobile shop, the person told me he tried to connect it to the computer. Maybe he was trying to flash it or unlock the bootloader, but he said that the phone did not detect on the computer.
Can anyone please help me?
If possible, some detailed steps on how to proceed.
(This is the Indian Dual Sim version - XT 1068. Not rooted, no custom rom, running on 4.4.4 KitKat)
Can anyone help with any links which will start the phone again. Fastboot etc r alien words to me so any detailed instructions will be helpful.
Thanks
Hello,
First of all, sorry for my english as it is not my mother language
I've tried today flashing CM13 on my Wiko Rainbow, but I either failed following the instructions or the files I had were corrupted, leading to a never-ending boot.
I don't know if it was already a soft-brick back then, as the phone turned off while booting just after the installation, but 40min after it (obviously because of en empty battery, which was at 37% before installation)
At first, when the phone was plugged into the computer, the phone was booting up, showing the charging icon for a few seconds, and then was going into the infinite boot for 10 seconds, and then rebooting for the same process.
When I was charging the phone on a wall plug, the phone was just in an infinite loop.
The problem was that, when I did the Volume down + Volume up + power thing, I had a choice between Factory mode and Custom mode, but both of them led me to a black screen, and the phone powered off.
I then searched how to install a custom recovery with a soft-bricked phone, and I got a tutorial on SP Flash Tool, that told me to use a MT6582 scatter file, and to select only a Recovery. I downloaded a TWRP for my phone, and then started download, retracted the battery and plugged the phone on the computer.
I got this message : "brom error s_fthnd_file_is_not_loaded_yet"
The software told me to format the Flash, which I did, and this error now became this : "BROM ERROR : S_DL_GET_DRAM_SETTING_FAIL (5054)"
The thing is that now, the soft brick is now a hard brick, and I can't get the phone to boot anymore, adb doesn't recognize my device, and after installing and reinstalling my phone drivers, no solution came out yet, so I'm hopping that you'll find a solution to help my problem
Thanks.
Regards.
MichelFou said:
Hello,
First of all, sorry for my english as it is not my mother language
I've tried today flashing CM13 on my Wiko Rainbow, but I either failed following the instructions or the files I had were corrupted, leading to a never-ending boot.
I don't know if it was already a soft-brick back then, as the phone turned off while booting just after the installation, but 40min after it (obviously because of en empty battery, which was at 37% before installation)
At first, when the phone was plugged into the computer, the phone was booting up, showing the charging icon for a few seconds, and then was going into the infinite boot for 10 seconds, and then rebooting for the same process.
When I was charging the phone on a wall plug, the phone was just in an infinite loop.
The problem was that, when I did the Volume down + Volume up + power thing, I had a choice between Factory mode and Custom mode, but both of them led me to a black screen, and the phone powered off.
I then searched how to install a custom recovery with a soft-bricked phone, and I got a tutorial on SP Flash Tool, that told me to use a MT6582 scatter file, and to select only a Recovery. I downloaded a TWRP for my phone, and then started download, retracted the battery and plugged the phone on the computer.
I got this message : "brom error s_fthnd_file_is_not_loaded_yet"
The software told me to format the Flash, which I did, and this error now became this : "BROM ERROR : S_DL_GET_DRAM_SETTING_FAIL (5054)"
The thing is that now, the soft brick is now a hard brick, and I can't get the phone to boot anymore, adb doesn't recognize my device, and after installing and reinstalling my phone drivers, no solution came out yet, so I'm hopping that you'll find a solution to help my problem
Thanks.
Regards.
Click to expand...
Click to collapse
You're going to need the firmware (not just TWRP) to fix your phone. Have you been able to download it?
Hovatek said:
You're going to need the firmware (not just TWRP) to fix your phone. Have you been able to download it?
Click to expand...
Click to collapse
using SP Tool gives directly through the USB
Hey
yesterday i almost bricked or maybe bricked my phone. Accidentally changed partition from B to A. Today my phone boot only to nokia logo and stuck on it
Many hours readed about this phone back to life. Recover mode not work, fastboot mode not work. This phone one chance to turn off is completly battery discharge.
If no chance to get back this phone to normal i will get throw it to trash
Classic example of a softbrick can't really call it a hardbrick tbh. PM me all of the details and I'll later make a tutorial if we manage to fix it up.
mati5000 said:
Hey
yesterday i almost bricked or maybe bricked my phone. Accidentally changed partition from B to A. Today my phone boot only to Nokia logo and stuck on it
Many hours reading about this phone back to life. Recover mode not work, fastboot mode not work. This phone one chance to turn off is completely battery discharge.
If no chance to get back this phone to normal i will get throw it to trash
Click to expand...
Click to collapse
I did the same thing.
- Downgrade to Oreo
- unlocked officially bootloader
-fastboot boot twrp.img
booted to twrp- Flashed zip on both slot with latest twrp
Changed slot A to slot B and
we have same problem.
How did you solve your issue?
Did you wait for battery-drain?
Or other combination of buttons.
I tried all the button-combination without success.
Hope you could give advice
Regards
Edit: How to solve!
I simply waited until the battery ran out
When battery was completely dead and no Nokia-logo any more
Then I charged the battery 3% juice without booting
and from there I entered recovery-mode with the help of a USB cable.
Holding the volume+ button while connecting the USB-cable
From TWRP-recovery I changed to the other inactive slot
and whooala, that's it!
I have OEM unlocked my nokia 8 boot loader by nokia official method ,
Then I decide to flash twrp and magick
When boot twrp it give an error that locked
Then I checked some forums and find a way ,
I do what is guided in that forum
Change boot slot b to a ... and I flashed twrp then I flash rom , at the end of flash slide to reboot , then I reboot but after that there is no response in device it went blank and black.....
If I connected to PC in some flash tool it show hs com 3008 and connecting sound in pc but mobile being blank and i cant even get to fast boot mode becoz device get blank ( while connected in pc if I power on or hold power but connection sound will come from my pc but no device or unknown device )
Pls help friends, really dunno what to do
Pls help !
Respond soon pls
Same as me bro.. my ta 1004 is dead after unlocking bootloader official method. And i flash boot twrp and magisk. But my phone always bootlop. I try to flash with ost la. An qfil to recover. But i stuck in download mode. And i try to flash with twrp slide load .
And my phone is dead now.. i can do anithing. My phone can turn on now... i charge it .. but still not respond
Anyone help me