I had a cable come out while flashing my 6700 rom. I performed the hard reboot and is now stuck in bootloader mode. The top of the screen only shows serial and the bottom shows version 2.05. I read alot of the other threads and downloaded the various programs to fix. However my pc does not recognize the phone via usb. Any suggestions?
I had the same issue. I resolved it by Flashing the rom from the manufacturer then after flashing the custom rom.
Make sure if you plan to use a custom rom that you put device in bootloader mode first. top power + voice memo + soft reset.
Related
I recently purchased an android phone used, and it was pre-rooted.
I'm trying to get it back to stock firmware, as I hit reset data and now it won't boot. I have do the volume-down key fastboot menu and the home+power recovery options, but I have no idea howto restore it to original firmware from Rogers.
When plugging into the computer, it fails to properly install the usb drivers aswell, maybe because I cant boot the phone normally?
I'm really new at this, which is why I want to go to stock, thus I can relearn everything from scratch.
Also, on a side note, anyone know a place to get a replacement LCD screen, or a means of connecting the digitizer that has the ribbon-cable connection part of the lcd screen missing?
Cheers,
Bobbo
I would suggest you download the original rom and then load the original SW using recovery. Press "home and the start button and hold until the recovery menu comes up.
As for installing the ADB, you may not have installed the proper USB driver.....
check to see if your computer recognises the phone....
If not, you can manually install the USB driver.
Awesome, managed to finally restore the original Rogers firmware.
Now I'm getting an error when I try and launch the phone. android.process.acore stopped.
I can get text messages and wifi works, but the phone app crashed each time I try and load it. Any ideas?
So this was I have done to create and to try and solve this issue.
I was running stock CM12 and wanted to flash a different ROMs, so I tried to unlock the bootloader and using "fastboot -i 0x1ebf oem unlock" and without restarting the phone, tried to flash 64bit TWRP recovery, after this the phone no longer booted, but TWRP was booting, with a lot of errors of not being able to mount "/data" and other partitions. So I downloaded the CM12 offical ZIP file to try and do a factory reset, flashed using "fastboot" with the file "flash-all.bat" and here is where the problem started, this process failed, I think because there is a "flash-radio.sh" file where the "fastboot" lines do no have the "-i 0x1ebf" and because of this (I assume it's this lol), this process failed and the phone no longer starts, nothing works, tried in windows, ubuntu and a MAC at work, nothing is able to see the phone any more, the only sign of life I get, is when I remove the battery and connect the usb cable, the red LED from the phone turns on, but the PC still does not detect the phone, followed a recommendation I found, to remove the battery, pressing and holding the volume UP button + connecting the USB cable + connecting the battery, all this whilst the volume UP button is still being pressed and also did not work, no signs at all of life =(
Not sure what to do more, any idea guys?
Can't return because I bought on eBay UK =(
After many failed attepts to encrypt my phone using VanirAOSP ROM (Android 6.0.1), decided to try again, and phone is useless now. As always, encryption even didn't start after phone rebooted, but this time I can't even start Android or properly boot into fastboot/flashmode.
Put simply, if I boot my phone now, it displays Sony logo and then screen goes blank. If I keep pressing volume up button, Cyanogen Recovery starts. But since it has no option to flash a ROM, it's useless to me (I had TWRP installed as well, but this one is somehow gone now). If I boot phone into ADB mode, I see device number, and "unauthorized" message next to it. If I try to boot into fastboot mode, blue light comes in, but list of fastboot devices is empty.
However, if Flashtool is running, it displays a message "device connected in fastboot" mode the same second I try to boot my phone into fastboot. Unfortunately, that's not much help, because if I try to flash original Sony ROM via flashmode, it doesn't work - it displays a popup window "disconnect device and re-connect in flashmode...." but when I do it, nothing happens (the popup is still here, which means device not found). The same happens if I try to do anything what requires fastboot - even if Flash tool shows "device connected in fastboot" message first, it then asks to re-connect phone in fastboot mode (the same popup), and nothing happens agains.
Any ideas on how get the phone working?
did you try to flash advanced stock kernel with recovery?
Problem fixed with Flashtool by flashing another ROM successfully. Several minutes ago I accidentally connected the phone to another USB port on my PC, and it started working. Not sure why this problem occured at all, because that "non-working" USB port worked fine previously, and it also works now when ROM is properly flashed.
Hello, I keep flashing TWRP with Odin but it resets when it's done and recovery does not change. I have tried several different versions of Odin and TWRP from their website and from here. Any idea what to do?
Which TWRP are you flashing? I recommend using version 3.0.1-0 from here, as version 3.0.2-0 has been known to have some problems in the past.
https://forum.xda-developers.com/showthread.php?p=66266209
Maybe try making sure Allow OEM unlock is switched on in Settings-->Developer Options before you flash it too. Obviously make sure your device is being recognized properly by ODIN as well. You should see a little blue box light up in the top left of the ODIN window when you connect the device. Make sure you're flashing it in the AP slot and no other. Also, make sure you have the current Samsung drivers installed for the SM-G360T1 from here:
http://www.samsung.com/us/support/owners/product/galaxy-core-prime-metro-pcs
Hope this helps! Have a good day.
I've honestly tried just about every version here and on the website. Started with 2.8.7 as a ROM I was interested in recommended it, however I am willing to use any that will work at this point I really only wanted my device rooted for one simple task.
My drivers appear up to date -
USB debugging and Boot unlock are both enabled -
Odin shows PASS and reboots my phone on flash -
Everything seems like it's working right, but it's not replacing my recovery. When I reboot it just takes me back to the warning/download screen. Is it possible I might need to downgrade to the original Lollipop that came with this phone first?
Edit -> I tried TrapKernel as well, that disabled my wifi entirely (on/off button would not stay in on position)
Edit -> Tried downgrading to the original Lollipop that came with my phone and it reboots itself as soon as it gets in to Android. Gonna try flashing it again before returning to current Android. :/
OutlawStarX said:
Hello, I keep flashing TWRP with Odin but it resets when it's done and recovery does not change. I have tried several different versions of Odin and TWRP from their website and from here. Any idea what to do?
Click to expand...
Click to collapse
Pull out the battery after the phone comes up on the boot logo when the flash is complete. After that put it back in and press VOL UP + HOME + POWER and it should take you to the TWRP recovery. You do this because the phone will recognize that is not a original recovery, so it replaces with the original one. Make sure to put a custom rom with root in it so it doesn’t replace the recovery again.
Hi, just bought a phone for my son secondhand, it's going to be sold again if I can't fix this! The phone was sold cheap as it had software issues (of course) so I figured I could fix these and get it going (install custom recovery, ROM etc). I'm slightly stumped at the moment, so maybe you can help me.
The phone's defaulting to the bootloader screen, lots of info on this but the key thing I noticed was that it says 'the device is locked status code: 2'.
Clicking 'start' takes me a 'warning unlocked bootloader screen' then it runs through the 'hello moto' startup screen and back to bootloader
Clicking 'recovery' - there is definitely no working recovery on it, I just a get the dead robot with 'no command' underneath.
Clicking 'Factory Mode' allows me so far through the startup (after the bootloader unlocked warning), and you can get so far through setting it up, but because the battery is so low (it's permanently on with the bootloader when plugged in) it never seems to charge up enough, and either way the screen freezes at or around the final setup steps and then it reverts back to bootloader. I thought if I got into developer options and security, I could enable the USB debugging, OEM unlock etc, but no go there.
I've installed Motorola USB drivers but it doesn't seem to be registering on the PC (Windows 10).
There is some suggestion on other forums (less reputable!) that the locked status code may mean the bootloader has been relocked, but this seems contrary to what the phone is telling me.
Any ideas welcome, thanks - it's a lovely phone, just not much use at the moment.
GitManMatt said:
Hi, just bought a phone for my son secondhand, it's going to be sold again if I can't fix this! The phone was sold cheap as it had software issues (of course) so I figured I could fix these and get it going (install custom recovery, ROM etc). I'm slightly stumped at the moment, so maybe you can help me.
The phone's defaulting to the bootloader screen, lots of info on this but the key thing I noticed was that it says 'the device is locked status code: 2'.
Clicking 'start' takes me a 'warning unlocked bootloader screen' then it runs through the 'hello moto' startup screen and back to bootloader
Clicking 'recovery' - there is definitely no working recovery on it, I just a get the dead robot with 'no command' underneath.
Clicking 'Factory Mode' allows me so far through the startup (after the bootloader unlocked warning), and you can get so far through setting it up, but because the battery is so low (it's permanently on with the bootloader when plugged in) it never seems to charge up enough, and either way the screen freezes at or around the final setup steps and then it reverts back to bootloader. I thought if I got into developer options and security, I could enable the USB debugging, OEM unlock etc, but no go there.
I've installed Motorola USB drivers but it doesn't seem to be registering on the PC (Windows 10).
There is some suggestion on other forums (less reputable!) that the locked status code may mean the bootloader has been relocked, but this seems contrary to what the phone is telling me.
Any ideas welcome, thanks - it's a lovely phone, just not much use at the moment.
Click to expand...
Click to collapse
OK, some progress, I have now unlocked the bootloader, so have the UNLOCKED Status Code:3 which is good, unfortunately has not yet helped with my issues. I can't use ADB, but MFastboot tool is working, so can run commands from that (hence me getting to that stage). Tried reinstalling firmware, may try and do this again now bootloader unlocked....
slightly further along...
GitManMatt said:
OK, some progress, I have now unlocked the bootloader, so have the UNLOCKED Status Code:3 which is good, unfortunately has not yet helped with my issues. I can't use ADB, but MFastboot tool is working, so can run commands from that (hence me getting to that stage). Tried reinstalling firmware, may try and do this again now bootloader unlocked....
Click to expand...
Click to collapse
I have now managed to flash stock firmwares using Mfastboot tool, but hasn't unfortunately fixed the boot up issues. However, I have now worked out how to access the recovery, by reading other posts on different Motorola phones:
boot to bootloader, power+vol down
in bootloader select recovery using the volume up/down buttons, press power button to select
phone boots into 'recovery,' showing the dead android with no command
at this point hold down the power and volume up, then release volume up but keep power held down
phones boots, by magic, into android recovery, where you can factory reset, wipe cache adb sideload and install from SD card
I now need to try and get a flashable recovery to sideload, as the attempts to flash it don't work for me. The OS I seem to be on is reteu 7.1.1, so I will try and go for a lower version, and see if that allows me to flash the custom recovery I desperately need.
But....things are improving slowly....:laugh:
GitManMatt said:
I have now managed to flash stock firmwares using Mfastboot tool, but hasn't unfortunately fixed the boot up issues. However, I have now worked out how to access the recovery, by reading other posts on different Motorola phones:
boot to bootloader, power+vol down
in bootloader select recovery using the volume up/down buttons, press power button to select
phone boots into 'recovery,' showing the dead android with no command
at this point hold down the power and volume up, then release volume up but keep power held down
phones boots, by magic, into android recovery, where you can factory reset, wipe cache adb sideload and install from SD card
I now need to try and get a flashable recovery to sideload, as the attempts to flash it don't work for me. The OS I seem to be on is reteu 7.1.1, so I will try and go for a lower version, and see if that allows me to flash the custom recovery I desperately need.
But....things are improving slowly....:laugh:
Click to expand...
Click to collapse
Never try to downgrade using stock firmware.
tyamamoto said:
Never try to downgrade using stock firmware.
Click to expand...
Click to collapse
OK thanks, I read that, but didn't realise it was a thing....should I be able to sideload a custom rom using ADB?