Hello,
I recently found my old Droid Razr Maxx again and wanted to know if any of you know a way to restore it to its former glory, so to say.
I jumped into a lake with it after forgetting that it was in my pocket a few years ago and ever since, the data parts of USB have been dead. I continued to use it for some time after the accident, but unfortunately I managed to soft-brick it with no way to re-flash the firmware with RSD Lite.
Connecting a regular USB cable to the device with the battery removed just lights up the white LED, which indicates that it receives power over USB, but not enough to boot. When I use a factory cable, the device boots, which leads me to the conclusion that pin 1 and 4 still work like they should.
The device then gets stuck on the Motorola bootsplash, but I'm able to get into the bootloader, fastboot mode, and stock recovery with the key combos. I already tried to place a few signed .zip's (OTAs) on the SD card and flash them through the stock recovery, but all .zip's I've tried so far fail as they check system files of the current ROM that are supposed to be in place. They just include the incremental update parts anyway, so I don't know if they would help, even if I could install them.
I wrote a small script that executes "fastboot devices" every second, booted into fastboot and tried to connect the USB data pins directly to the lines that go into the motherboard (in case just the port is corroded), but I've had no luck so far, as it doesn't get recognized. I tried to connect to the Test Points near the microUSB port in various combinations, hoping that they are connected to the data pins, but my Razr just reboots in most cases, or does nothing. It still doesn't get recognized.
Does anybody know how I could get a working firmware on the device? :silly:
Here are some images: https://imgur.com/a/oz3bo
Related
HELLO GUYS, I need Help BAD! First off my Razr was going dead. It said battery to low to boot. I connected a external battery to it to charge it then I left it for a while. I don't know exactly what happened but I went into the Utility screen. I have been on it before per Forum directions to go to recovery and delete the cache. I was scrolling down and I accidentally clicked the up key to go up to recovery and clicked up on AP Fast Boot. Now My Razr is stuck in what I think is called a Boot Loop. The Motorola symbols just keeps popping up over and over. I can go back into the Utility screen I tried to go into recovery but the Motorola symbols just pops back up OVER AND OVER. I have the Razr plugged to the factory moto plug but a white light comes on and no charging screen pops up. I don't believe it charging. The battery feels Hot but when I go back into the AP Fastboot screen it says Battery Low. I may just need to leave it on there longer or it may not charge I don't know. I am AMATEUR.I am rooted per Forum instructions with Razr Blade utility. ANY HELP WOULD BE GREATLY APPRECIATED. I have no clue what to do and the more stuff I try I think Im screwing more up. When I go to AP Fast Boot it says battery low but when I plug it up it a white light on the front comes on the Moto Logo keeps popping up over and over. It wont go to recovery. I tried going to BP TOOLS, that done nothing. WHAT DO I DO??? I just want it to boot up. The only back ups I have are on my Ext SD card and thats just of the apps, contacts and I think theme. (Backed up per Titanium and ROM Toolbox) Do I need to make an Ins claim with Verizon Thanks Jason
#1 Am I stuck in Fastboot?
#2 If so am I stuck bc the battery is dead?
#3 If I get the battery charged will I be able to just choose Normal Boot and the Razr will Boot Up?
#4 If so How do I ensure its charging? I read on another site plugging it to the factory charge while stuck in fast boot will still charge the Razr (slow)
5# If none of the above, What in the World have I done and how do I get out of it?
Just adding to my Nightmare
I read somewhere I needed to connect my Razr to a PC and Update the Drivers. I went back into FastBoot, used my factory USB cable and plugged it to the PC. The driver started updating (it even said the name of the driver) I stood up and knocked my Razr off the desk. The driver failed to update. Then I hooked it back to the PC and the Drivers Failed. I hooked it to 2 other USB ports they All Failed. It keeps saying unrecognizable device. I rebooted the PC in hopes that when I hooked the Razr back up to the PC it would start to update the drivers. Now I if I hook the Razr to the Factory plug (it gets Hot) I go to the Utility Screen then to Fastboot and it still says Battery Low. I unplug it from the charger to hook it to the PC and it Blinks OFF and does NOTHING when I hook it the PC. My Razr is Factory other than the Razr Blade Root. Stock ROM and Everything. Any Help would be Greatly Appreciated, I am a NOOB so Detailed instructions would definitely increase my chances for success. Thanks Jason T.
jasonsc1 said:
I read somewhere I needed to connect my Razr to a PC and Update the Drivers. I went back into FastBoot, used my factory USB cable and plugged it to the PC. The driver started updating (it even said the name of the driver) I stood up and knocked my Razr off the desk. The driver failed to update. Then I hooked it back to the PC and the Drivers Failed. I hooked it to 2 other USB ports they All Failed. It keeps saying unrecognizable device. I rebooted the PC in hopes that when I hooked the Razr back up to the PC it would start to update the drivers. Now I if I hook the Razr to the Factory plug (it gets Hot) I go to the Utility Screen then to Fastboot and it still says Battery Low. I unplug it from the charger to hook it to the PC and it Blinks OFF and does NOTHING when I hook it the PC. My Razr is Factory other than the Razr Blade Root. Stock ROM and Everything. Any Help would be Greatly Appreciated, I am a NOOB so Detailed instructions would definitely increase my chances for success. Thanks Jason T.
Click to expand...
Click to collapse
I had this problem some months ago! mine came because of installing a rom with low battery (bad idea always...) the rom did not get installed properly, so the phone couldnt boot up, neither charge. As it was at low battery it also couldnt go fastboot to recover the stock system. I found somewhere a post (i dont remember now, but search for it, you may find) where a guy gave instructions for charging the battery by opening the phone and connecting the battery directly to the positive and negative terminal of an usb cable. This may sound too difficult, but once I had connected the battery I could go fastboot and reinstall the stock system.
Ask me if you cant find the post. It worked for me!! good luck
I found it, Charged it and I'm STILL in a Boot Loop. I won't boot to recovery or normal boot up. I'm STUCK BRICKED
Sent from my DROID RAZR using Tapatalk
You will have to download the fastboot files for your device. Flash them via RSD Lite.
Make sure you have a lot of charge before flashing the files.
FastBoot files:- http://sbf.droid-developers.org/cdma_spyder/list.php
RSD Lite v5.7:- http://www.mediafire.com/download/6c7krihb3ggj88g/RSDLite5.7.rar
Motohelper drivers:- http://www.mediafire.com/download/t3tfh3p2xcy2861/MotoHelper_2.1.40_Driver_5.5.0.exe
Install the drivers and RSD Lite. Open RSD Lite and connect your phone via the USB Cable while in AP Fastboot. The software should detect your phone and your device should appear in the list. Then simply open the fastboot files in RSD and flash them. Make sure that the process isn't interrupted.
Hope it helps.
Here ya go. Hope it helps. http://forum.xda-developers.com/showthread.php?t=2431617
Sent from my XT912 using xda app-developers app
Hello, I have issues connecting my S3 international model (i9300) to any PC. It has CM11 since at least 6+ months and it worked just fine and connected to my PC two days ago just fine.
Some days ago, it started bootlooping because of the common power button stuck problem [turned on by itself when battery inserted, and rebooted in the Samsung logo, which doesn't even let you go to DOWNLOAD mode or Recovery because it just reboots after a few seconds]
Yesterday I disassembled it following fixit guides and youtube step by step guides to make sure I didn't break anything. I saw the button problem was internal (the button apparently works fine, but internally it has a closed circuit so it seems as pressed). I assembled my phone again and went to bed. Today it was working without bootloop. I saw this as an opportunity to make all the required backups just in case it went to bootloop again but I couldn't get anything from it. Windows doesn't recognize it at all, not even during boot. Here is what I tried:
*Tried in several PCs/Notebooks/OS with different cables that work with other phones
*In all cases it charges the battery, but the PC doesn't see it as a device.
*I rebooted the phone by software (so I don't press the power button at risk of getting bootloop again) going to terminal emulator and using 'reboot' command.
*Rebooting the phone connected to the PCs doesn't either cause any device to be detected by the PC during the booting of the phone.
*Thinking it might be the port of my phone, I tried an OTG adaptor and several pendrives. They all were detected by the phone and I was able to write and read the USB drives.
Click to expand...
Click to collapse
At first I suspected I left a ribbon/flex cable not connected to the board, but being able to use OTG USB drives and being able to charge it didn't convince me it was the case. I want to avoid disassembling it without knowing first which ribbon to look at and any other test/information you could tell me to provide in order to find the solution.
Actually i just recovered from an extreme hard bricked Motorola Droid RAZR but there is a little problem.
Things i did to recover:
- I opened it's back and unveiled the two switches to manually recharge phone, this was the only way to get to fasboot in OKAY mode (it served as charger only).
- After that, i connected another USB from the original port which connected the phone to PC (it served as recovery only).
- After that, i used RSDLite to recover the system from the scratch.
Now i can only boot my phone as long as it is connected to power source, NOT PC! However, i can get to boot options using PC which confirms that it is not really plug n play, any way to fix it?
Fixed it myself.
Hi,
I've got a Nubia N1 Lite (NX597J) to mess around with, and wanted to try modifying the ROM. I can enter developer mode and allow bootloader unlocking, adb also works. What I can't do is use USB while booting, or in the recovery menu. No fastboot or sending ROM images via adb to the recovery software. The phone doesn't connect to the computer at all (I'm using Linux, it should at least show up in dmesg). Recovery log says
Code:
musb_pullup 2498: no USB cable, don't need to turn on USB
A couple times, even though the cable is connected and works in Android proper. I've tried USB2 and 3 ports, on a hub and directly on the motherboard. It shows up as 0e8d:2000 MediaTek preloader when turned off and, very briefly, as 0e8d:2008 when booting into recovery.
Am I missing something, or is the recovery image just broken on this phone? I've tried both the EU and US firmware, which is a bit more recent.
Do I need some tool that interacts with the preloader, maybe? I have found this guy who's been messing with a phone that has the same SoC.
Have you managed to get it into recovery mode? I just get a dead android picture :/
I've accidentally broken it by flashing the US ROM but my phone is the EU version. Boots up okay but has lost the IMEI and once the screen turns off won't turn on again - unless I reboot it.
Have so far failed to re-flash with the correct EU ROM - it just fails half-way through.
No, and I'm in the same situation with the firmware.
I've been booting LibreELEC/CoreELEC from SD card on my AZW (Beelink) W95 (S905W) box for years now. Yesterday I tried booting into the stock Android system (7.1 I think- I haven't done it for a while) but it wouldn't boot. Not being one to leave well enough alone I decided to try a reset using a toothpick in the reset hole by the power plug. It flashed the start screen for a split second and then stopped. After that it wouldn't boot off the CoreELEC SD card either.
I've tried a clean CoreELEC install, stock firmware, Amlogic Burn Card Maker, and TWRP on the SD card - none of them get me past a black screen.
I don't think the reset button is doing anything (I depress it while plugging in the power jack). In fact, I don't know if it ever worked. My box had previously always booted off a SD card if it was inserted in the slot without having to do anything special.
My box isn't completely dead but comatose. The signs of life are:
1) The blue LED comes on when I plug in the power cord.
2) After about 20 minutes or so the blue LED will go off. If I press the power button on the remote it comes back on.
3) My router sees it on my network as active. But I get connection refused when I try access it using Windows File Explorer or try to SSH into it using Putty.
4) When I insert a SD card into the slot it writes Andriod and LOST.DIR folders to it.
I haven't tried the Amlogic USB Burning Tool yet because I don't have an USB 2.0 Type A male to male cable - but I've ordered one. My concern is I won't be able to put it in reset mode since I'm not sure the reset button does anything (but I can feel it click).
Is there anything else I should try while I'm waiting for my cable to arrive?
Any recommendations on how I should proceed once my cable arrives?
Thanks
RKCRLR said:
I've been booting LibreELEC/CoreELEC from SD card on my AZW (Beelink) W95 (S905W) box for years now. Yesterday I tried booting into the stock Android system (7.1 I think- I haven't done it for a while) but it wouldn't boot. Not being one to leave well enough alone I decided to try a reset using a toothpick in the reset hole by the power plug. It flashed the start screen for a split second and then stopped. After that it wouldn't boot off the CoreELEC SD card either.
I've tried a clean CoreELEC install, stock firmware, Amlogic Burn Card Maker, and TWRP on the SD card - none of them get me past a black screen.
I don't think the reset button is doing anything (I depress it while plugging in the power jack). In fact, I don't know if it ever worked. My box had previously always booted off a SD card if it was inserted in the slot without having to do anything special.
My box isn't completely dead but comatose. The signs of life are:
1) The blue LED comes on when I plug in the power cord.
2) After about 20 minutes or so the blue LED will go off. If I press the power button on the remote it comes back on.
3) My router sees it on my network as active. But I get connection refused when I try access it using Windows File Explorer or try to SSH into it using Putty.
4) When I insert a SD card into the slot it writes Andriod and LOST.DIR folders to it.
I haven't tried the Amlogic USB Burning Tool yet because I don't have an USB 2.0 Type A male to male cable - but I've ordered one. My concern is I won't be able to put it in reset mode since I'm not sure the reset button does anything (but I can feel it click).
Is there anything else I should try while I'm waiting for my cable to arrive?
Any recommendations on how I should proceed once my cable arrives?
Thanks
Click to expand...
Click to collapse
Hi, your device seems to be in a strange state currently, only thing i can reccomend is trying a few firmwares to see what works for you, you should be able to flash most s905w based roms, if your device cant be detected by USB burn tool you might need to use ask Rom Mode" to force your box to be detected by burn tool, this makes it almost impossible to brick a box
Thanks for the suggestions, I'm a complete newbie at this.
Is the Ask ROM Mode an option in USB Burning Tool?
I have an OEM W95 firmware update file (in both .img and and an OTA in .zip format) but they may be older than what is currently on the box. I also found a TWRP file for the S905W. But I don't know how to use any of these.
I downloaded the AMLogic Tools 6.0.0 and tried the AMLogic Flash Tool since it seems to work through the Ethernet port. I assumed this because you access the box via an IP address but I really don't know. I watched the video but couldn't find any detailed instructions on how to use it.
When I pressed the Connect button it said it connected and I had the green Connected display (I was connecting through my LAN - I don't know if I should connect directly with an ethernet cable). I loaded my .img file and said Flash. It says it is flashing and a second or so later it says SUCCESS! However the box still doesn't boot. I tried both Boot and Recovery (I don't know which option I should choose). I think that the SUCCESS! message is incorrect since I get the message even if I press the Flash button without the box connected. However, I can't connect to the box without the ethernet cable connected so the connected message seems correct.
Am I using the AMLogic Flash Tool correctly?
I was thinking about trying the S905W atvExperience ROM but thought I'd wait until I got my USB cable before before doing something more drastic.
Any other suggestions?
Thanks
OK, so my male to male USB cable arrived and I managed to get my box un-bricked using AMLogic USB Burning tool with a factory .img file. It took several tries. I kept getting errors when it tried to erase the bootloader or would get to 7%, progress would stop for about a minute, and then Burning Tool would close.
I finally got it to proceed all the way by holding in the reset button, plugging in the USB cable (no power cable), and keeping the reset button pushed the whole time (I don't know if this was just a coincidence). Also, I hadn't closed Burning Tool after the previous error erasing the bootloader. I'm posting all this in case someone else has a similar problem.
After that, it still wouldn't boot of the CoreELEC SD card with the reset button pushed down. It would go straight into the Android OS. I got it to boot into CoreELEC by installing the Reboot to LibreELEC app. Now it always restarts in CoreELEC the way it used to when the SD card is left in. I think this is how I got LibreELEC working years ago.
So, now I'm contemplating installing atvXperience but I have a couple of questions:
What would be the best way to install atvXperience without being able to the reset button to put the box into recovery mode?
What would be the best way to prepare for not being able to use the reset button to put the box into recovery mode if something were to go wrong during flashing?
Thanks for any help.
OK, so my male to male USB cable arrived and I managed to get my box un-bricked using AMLogic USB Burning tool with a factory .img file. It took several tries. I kept getting errors when it tried to erase the bootloader or would get to 7%, progress would stop for about a minute, and then Burning Tool would close.
I finally got it to proceed all the way by holding in the reset button, plugging in the USB cable (no power cable), and keeping the reset button pushed the whole time (I don't know if this was just a coincidence). Also, I hadn't closed Burning Tool after the previous error erasing the bootloader. I'm posting all this in case someone else has a similar problem.
After that, it still wouldn't boot of the CoreELEC SD card with the reset button pushed down. It would go straight into the Android OS. I got it to boot into CoreELEC by installing the Reboot to LibreELEC app. Now it always restarts in CoreELEC the way it used to when the SD card is left in. I think this is how I got LibreELEC working years ago.
So, now I'm contemplating installing atvXperience but I have a couple of questions:
What would be the best way to install atvXperience without being able to the reset button to put the box into recovery mode? (I did try flashing atvXperience once using USB Burning Tool but I got the same error erasing bootloader)
What would be the best way to prepare for not being able to use the reset button to put the box into recovery mode if something were to go wrong during flashing?
Thanks for any help.
Another follow up post for anyone with the same problem. I did some searching and found out I'm not the only one with a box that the reset button doesn't work. A work around for them was to connect the male to male USB cable, load the image into Burning Tool, press Start, and then plug in the power supply. The image file would then start flashing.
However, my box would start booting as soon as I connected the USB cable (didn't need the power supply). So I loaded the image into Burning Tool, pressed Start, and then connected the USB cable. This appears to be the work around for my box (I probably did this when I got my box to recover the first time - holding the reset button was probably irrelevant).
This procedure works for the stock firmware but when I try to flash the atvXperience image file the box hangs at 7%. So I still need some help there.
Also, is there a ATV ROM better suited for my S905W box (2/16 GB)?
W95 is really ****ing box whenever you feel you get off from the current problem will be into next one.
I have installed atvx Rom but afterthat when I tried adian rom my device bricked.
Without Ubt flashing it's connect but as I start flash it's sound unknown device and give flash error