first of all i would like to thank anyone who tries to help me. i am somewhat new to the motodroid i own an evo and i am trying to help a friend. the phone is a verizon motodroid 1. the phone has been rotted for about a year he was running i think buggless beast at the time it died the initial problem was his baseband along with a few other software info went to unknown status. first he tried a backup, after not fixing the problem he contacted me and i decided to take a look at it after researching on multiple websites the best conclusion i found was to download the drivers for the phone, rsd lite, and the sbf files to reflash the phone back to stock.
i tried all of this with no good results know the phone wont boot past the M logo screen in the boot animation. the phone is unable to restore any backups at this point. every time i run rsd lite it seems to work and at what i believe is the end i get a fail. then when i hold up on the d-pad when turning on the device it reads.
bootloader
2c.7c
code corrupt
and the phone is now unable to charge the battery also the only thing i was successful at accomplishing was flashing the sbr recovery but still could not flash any rom or the update zip that someone had mentioned to flash
any help would be appreciated
ok my best hit at it is resetting the hone. i bought a used droid 1 and the previous owner had left the " connect the dot " lock screen on it so after googling some **** i came accross a site that said something about booting into recovery. hers the steps
slide screen up and press and hold " x " and power until you get a triangle on your screen. now press both, the volume up key and camera simatainiously untill text appears then select reset or factory reset. this worked for me so hope this helps.
that was all done before i tried to use rsd lite and had no results after using rsd lite it completly removes the stock image then rewrites a new one. the problem is the removal of the image passes but writing the image fails so i am left with nothing.
Related
Hi,
Full version as a note. Droid 1
Flashed clockworkmod recovery (2.5.0.1), went fine. Made a backup of stock rooted ROM, worked fine. Next flashed bugless beast .6, while clearing data & cache, no problem.
Now i want to flash to cm - trying out different ROMs - trying to reboot into recovery or flash another ROM both fail to get me to a bootloader. Instead i see the motorola boot logo for 30-45 seconds, followed by what looks like a regular boot (motorola M, then Droid eye, & booted.). I have also tried fixing permissions.
If anyone has any idea why this is happening or can direct me to a forum link it would be greatly appreciated. Sorry if this is in the wrong section, and yea I've tried looking through the forums for a while.
Thanks
just a little baby sized pump...
This happened to me too after working perfectly for several months. All of the sudden I just couldn't get to clockwork. I am running CM7 Nightlies. After not being able to fix the issue for several days I decided that a full wipe via the .sbf method was in order. I've got everything up and running again but it was an annoying process. Can anyone out there help us to understand why this happened so we don't have to deal with this again?
Do you have a link for the method you described about? That would be really helpful!
An ever so slightly larger bump
I really am not trying to be lazy, but all the .sbf methods I've read so far seem require you getting to a boot loader. If I could get to a boot loader this wouldn't be a problem, as I made a back up of my stock ROM. I have a functioning bugless beast ROM, just no recovery / boot loader, and no way to flash back to my recovery.
And possibly solved..
One: Please pardon my ignorance, doing these things on my Eris was far easier, or at least what I got used to.
Two: Please also ignore the word boot loader in my previous posts, as it was the recovery console that I could not get to load. Sorry Again.
Three: Its magically working. My methods were unscientific to say the least, but the Droid is now in "ClockworkMod's Recovery v2.5.0.1".
Things I finally did:
NOTE - I DO NOT BELIEVE ANY OF THIS TO BE THE PROPER ORDER OF THINGS. PLEASE VERIFY WITH SOMEONE FAR MORE INTELLIGENT THAN ME. THE FOLLOWING REFLECTS THE PROCESS I DID, AND SHOULD PROBABLY NOT BE FOLLOWED UNLESS A MOD ACTUALLY SAYS THIS WAS CORRECT
1. Pulled Battery, hold power button down for a few seconds, and then put back in
2. Hold Up on D-pad while holding the Power Button
3. You see the following
Code:
bootloader 2c.7c
battery ok
ok to program
connect usb
data cable
4. Connect USB data cable to PC running RSD Lite. You will also want a .sbf recovery file from a trusted source.
5. Select the .sbf in RSD Lite. Tell it to start. I used the clockwork recovery only .sbf
*** Where things got officially weird for me ***
6. The .sbf file I told it to load seemed to work, as the progress bar moved. The phone almost instantly rebooted, back to the ROM I was running minutes earlier. Clockwork had not been working previously trying to reboot into recovery, but almost instantly upon trying this time, I was in recovery mode.
NOTE - The USB cable was still plugged in as well. I don't know which combination of things actually got this to work, but it did.
Hope this helps someone else out.
Hey guys!
So I've got an issue I'm struggling with on the Moto G (2014). First I'll tell you as much as I can about the phone: I bought it from the Motorola website, so I think it's running whatever the stock firmware is. Also, it's the 8 GB US model and isn't tied to any carrier. (I have it on T-Mobile, but got it directly from Motorola. I was trying to figure out what the firmware is but the closest I've been able to get is by running the Motorola Device Manager app while the phone is in fastboot mode. It says there are no available updates for: 21.11.17.titan_retuaws.retuaws.en.us The bootloader is locked and the phone is not rooted. It's pure stock, though it might have automatically gotten an OTA update to the latest official release, I can't be sure because I bought it for someone else.
Okay, so the problem. I'd bought the phone for my dad and set it up and it worked fine for about two months. Yesterday, he came by my place and asked if I could take a look at it because it was stuck on one screen and since there was no removable battery, he didn't know how to reset it. The screen it was stuck on is the boot screen where the Motorola logo is supposed to come up. It was up, but the bottom half of the logo was stretched to the side and pixelated so my first reaction was "crap, he hit it against something and there's damage to the screen." But there was no visible damage to the screen anywhere (neither from a hard hit or from pressure) and he's got the flip case for it and he said it hadn't been hit or anything.
I tried to power it down by holding down the power button, but as soon as it went off, it tried to start up again. A bootloop that always froze on that messed up Motorola boot screen. I set it on the charger for a bit and let it run through the loop a few times and at one point it got as far as the "world" screen where it shows a cartoon planet. This extended down past where the weird stretch happened on the motorola graphic and it was perfectly clear so I realized there was no damage to the screen, just some sort of boot error.
So then I tried booting into fastboot (hold both volume buttons down along with the power button for a few seconds, release) and I was able to get into fastboot. I tried scrolling down to recovery and then hitting the volume up key to select it but the second I hit the volume up key (the selection key in this mode) it reboots the phone. It doesn't go into the recovery screen, just turns off the phone. I tried this for the "Factory" (reset) option, for the "Normal Powerup" option, and the others. Instead of getting anything different, selecting any of them turns the phone off and nothing happens. The computer is recognizing that there's a device connected to it when I have the phone plugged in via usb in fastboot to my Windows 8 laptop. It also appears that I can enter commands in fastboot. (Though I'm not sure what to put in to fix this so I'm turning to you guys.)
So I can't figure out what's wrong. I've got some experience in flashing roms, both manually and with some of the tools, but haven't had to deal with what I'm assuming is a soft brick before.
Can anyone offer any help?
Thanks very much.
Watch this video and try again
https://www.youtube.com/watch?v=vf2sOPoE2b4
Roldorf said:
Watch this video and try again
https://www.youtube.com/watch?v=vf2sOPoE2b4
Click to expand...
Click to collapse
Unfortunately that didn't work. I was able to click the "restore to factory" part and it seemed to do that but I tried it again with the "wipe cache partition" and it just reset. I tried to restart normally and nothing happened. I will start boot and go to the Motorola logo but will always fail there, no matter what I try.
I'm still stuck with the soft-bricked phone. Any help going from Fastboot to somehow getting it to work?
(As I stated in the OP, the recovery options don't work. It seems only the Fastboot area is working.)
try to reflash the rom via fastboot, using the commands on 4.2 on this thread
if you have fastboot working they must work and re-flash the stock rom and everything back to stock...
to have the XML zip of yours rom search in here and download the file regards yours model and OS version that you wanna...
download, very slow download, unzip, to the some folder of mfastboot and give the commands a try... :good:
This is how to solve *ANY* softbrick on the Moto G 2014 (2nd Gen Moto G)
Try unlocking your bootloader with the given instructions on Motorola's website. You can flash a recovery like TWRP or CWM using mfastboot-v2. After flashing the recovery you can reinstall a custom ROM or stock ROM to fix the soft brick. ADB is only available if you enabled USB debugging although it will allow few commands. Using mfastboot-v2 after unlocking the bootloader will play the main factor in resolving the soft brick.:laugh::good:
eyhajee said:
Try unlocking your bootloader with the given instructions on Motorola's website. You can flash a recovery like TWRP or CWM using mfastboot-v2. After flashing the recovery you can reinstall a custom ROM or stock ROM to fix the soft brick. ADB is only available if you enabled USB debugging although it will allow few commands. Using mfastboot-v2 after unlocking the bootloader will play the main factor in resolving the soft brick.:laugh::good:
Click to expand...
Click to collapse
hello eyhajee.
My Moto G 2014 xt1068, running on Android 5.0.2 has some softbrick issue.
I have unlocked its bootloader, rooted it, unrooted it and while I was trying to lock its bootoader, I forgot to enable USB debugging and now it's stuck on fastboot mode.
So I wanna ask that can flashing a custom ROM turn my phone on??
I think so. If you are able to run some basic commands you should be able to flash it to emergency mode.
Hi, well it looks like i have probably hard bricked my phone. After updating to nougat i decided to do afresh clean install. I wanted my phone to as if i had just bought it and came with nougat/emui 5 installed. So i did a factory reset from within the settings menu. But then i thought i would completely erase everything and start from the latest build before nougat, so emui 4.1.2/ marshmallow. So after wiping all the partitions in twrp and then doing a volume up + power to do complete factory wipe followed by using the three button method to install the B130 UPDATE.APP in dload folder on my sdcard, all worked as expected. The update completed at 100% and then rebooted. So there i am waiting for my phone to boot to start the setup process as i have done dozens of times before...BUT...my phone will not boot to the initial setup wizard. It just stays stuck on the Honor logo pulsing animation for ever and ever and ever!!!!!!
So i do the volume up + power button to get to stock recovery and do factory wipe and cache wipe as well. It works as expected so i reboot and once again use the 3 button method to install the update.app on my sdcard. That works as expected and at 100% says its succeeded and reboots. Once again i wait for it to boot to the initial setup wizard but....ALAS...it stays on that DAMN pulsing Honor logo. Ive tried rebooting it several times, redoing the factory wipe and install several times, but nothing. Ive gone into fastboot mode (volume down + power) to try and flash the boot.img and system.img ive extracted from update.app but get the error message -- remote: command failed -- and the same if i try to unlock bootloader. Obviously its not going to work because my bootloader isnt unlocked and nor can i got in to developer settings to enable oem unlock and turn USB debugging on because my phone wont boot past that bloody honor logo.
The only thing i havent done yet is to use eRecovery but i dont have broadband and i doesnt seem to work over public wifi! So i will go to my friends tomorrow and use their broadband and hopefullly eRecovery will download/restore the latest firmware. The only other thing i can think of is to download the original nem-l51c432B102 that came with my phone when bought, extract the update.app file and replace the B130 i have on my sdcard dload folder at present.
Sorry for such a long post but i wanted to expalin evrything in detail to hopefully resolve my problem without going backwards and forwards with questions and answers and taking for ever.
So ANYONE and EVERYONE who managed to read the whole post, if you have even the slightest idea of how to get my phone working, please oh please share it with me. Also my phone is still under warranty so if i needed to send it to a huawei centre to get it fixed would they do it and do it for free??? because eseentialy all i did was a factory wipe/reset and install a frmware and it goes KAPUT!! thats not my fault right????!!???
Thank you to one and all for any wisdom you can share. :crying::crying:
iantechie1979 said:
Hi, well it looks like i have probably hard bricked my phone. After updating to nougat i decided to do afresh clean install. I wanted my phone to as if i had just bought it and came with nougat/emui 5 installed. So i did a factory reset from within the settings menu. But then i thought i would completely erase everything and start from the latest build before nougat, so emui 4.1.2/ marshmallow. So after wiping all the partitions in twrp and then doing a volume up + power to do complete factory wipe followed by using the three button method to install the B130 UPDATE.APP in dload folder on my sdcard, all worked as expected. The update completed at 100% and then rebooted. So there i am waiting for my phone to boot to start the setup process as i have done dozens of times before...BUT...my phone will not boot to the initial setup wizard. It just stays stuck on the Honor logo pulsing animation for ever and ever and ever!!!!!! So i do the volume up + power button to get to stock recovery and do factory wipe and cache wipe as well. It works as expected so i reboot and once again use the 3 button method to install the update.app on my sdcard. That works as expected and at 100% says its succeeded and reboots. Once again i wait for it to boot to the initial setup wizard but....ALAS...it stays on that DAMN pulsing Honor logo. Ive tried rebooting it several times, redoing the factory wipe and install several times, but nothing. Ive gone into fastboot mode (volume down + power) to try and flash the boot.img and system.img ive extracted from update.app but get the error message -- remote: command failed -- and the same if i try to unlock bootloader. Obviously its not going to work because my bootloader isnt unlocked and nor can i got in to developer settings to enable oem unlock and turn USB debugging on because my phone wont boot past that bloody honor logo. The only thing i havent done yet is to use eRecovery but i dont have broadband and i doesnt seem to work over public wifi! So i will go to my friends tomorrow and use their broadband and hopefullly eRecovery will download/restore the latest firmware. The only other thing i can think of is to download the original nem-l51c432B102 that came with my phone when bought, extract the update.app file and replace the B130 i have on my sdcard dload folder at present.
Sorry for such a long post but i wanted to expalin evrything in detail to hopefully resolve my problem without going backwards and forwards with questions and answers and taking for ever.
So ANYONE and EVERYONE who managed to read the whole post, if you have even the slightest idea of how to get my phone working, please oh please share it with me. Also my phone is still under warranty so if i needed to send it to a huawei centre to get it fixed would they do it and do it for free??? because eseentialy all i did was a factory wipe/reset and install a frmware and it goes KAPUT!! thats not my fault right????!!???
Thank you to one and all for any wisdom you can share. :crying::crying:
Click to expand...
Click to collapse
Can you please edit your post ? Add some space, here and there if you want some help... It is nothing but pain for both eyes and mind to read you.
Onto related topic, did you manage to get your phone back to a functionnal state ? Note that the boot sequence can take time after a wipe so maybe it's not broken at all.
As for eRecovery, it never helped me to restore my device, tried on two different Wi-Fi networks after two completely unrelated issues.
Concerning warranty, I guess it depends on your country and where you bought your phone. I went to the carrier which provided me mine this morning since I ended up with a strong brick last night and I'll get a new phone in a couple of weeks.
Zarou said:
Can you please edit your post ? Add some space, here and there if you want some help... It is nothing but pain for both eyes and mind to read you.
Onto related topic, did you manage to get your phone back to a functionnal state ? Note that the boot sequence can take time after a wipe so maybe it's not broken at all.
As for eRecovery, it never helped me to restore my device, tried on two different Wi-Fi networks after two completely unrelated issues.
Concerning warranty, I guess it depends on your country and where you bought your phone. I went to the carrier which provided me mine this morning since I ended up with a strong brick last night and I'll get a new phone in a couple of weeks.
Click to expand...
Click to collapse
finally a reply! okay so ill edit my post once ive finished replying to you. First off thanks for taking your time to read my post, i am most greatfull. In response to your questions,suggestions i can tell you:
i went to my friends, connected to their broadband and attempted to use eRecovey to update/restore my device. ALAS it did not work! I tried several times and it gets to downloading package from server only to end in a FAIL.. I got home tried connecting to public wifi and doing eRecovery but it just fails. So like you I have never managed to get eRecovery to work.
As for the booting sequence, as i explained before, whether i access stock recovery and wipe cache and wipe phone it does this no problem, reboots, only to get stuck on the honor logo boot animation. The same goes for installing updatte.app with three button method. it says its installed succesfully but does not get past the honor logo boot animation. Unfortunately your suggestion that it might just take a long time to boot is not the case I have left it for hours you see and it never gets to the setup wizard :crying:
As for warranty, i am in uk, bought the phone via amazon, and it was unlocked, so not from a carrier like you. So i guess ill just have to find my nearest huawei service centre and have them look at it.
Does anyone know the procedure as far as doing this. Do i phone them or email my problem and then send my phone to them or what?? Any help is very welcome.
Thanks for your time and patience.
Please, please help...i'm desperate
So sorry for my original long post people, i simply wanted to give as much detail and info as possible because being vague doesnt help anyone. It seems that might have worked against me.
Please,please any suggestions would be appreciated to the N'th degree! I have tried everything i can think of and i am truly desperate now. I dont understand why i cant get it to work...
I can go into stock recovery and wipe the cach and do factory reset and that works fine, no errors.
I can hold the 3 buttons down to install the firmware package(ive got update.app from B130 build) and that works fine, gets to 100% and says 'success' and then reboots, with no errors.
But either way the phone refuses to boot past the honor logo boot animation and ive left it for hours hoping,praying, it will work after the 32nd time...
I can access fastboot but that is useless because my bootloader is not unlocked and i cant get to developer options to enable 'usb debugging' and 'oem unlock'. So i just get error message 'remote: Command Failed' with any command i type.
But thats madness, i cant comprehend why it wont boot because everything seems to work!?!
There has to be a way to get my device functioning again.
I am pulling my hair out, i am at a complete loss, it doesn't make sense. PLEASE ANYONE ..... please help....
Thanks HONOR-able enthusiasts for any help, no matter how small! :good: :fingers-crossed: :angel:
iantechie1979 said:
So sorry for my original long post people, i simply wanted to give as much detail and info as possible because being vague doesnt help anyone. It seems that might have worked against me.
Please,please any suggestions would be appreciated to the N'th degree! I have tried everything i can think of and i am truly desperate now. I dont understand why i cant get it to work...
I can go into stock recovery and wipe the cach and do factory reset and that works fine, no errors.
I can hold the 3 buttons down to install the firmware package(ive got update.app from B130 build) and that works fine, gets to 100% and says 'success' and then reboots, with no errors.
But either way the phone refuses to boot past the honor logo boot animation and ive left it for hours hoping,praying, it will work after the 32nd time...
I can access fastboot but that is useless because my bootloader is not unlocked and i cant get to developer options to enable 'usb debugging' and 'oem unlock'. So i just get error message 'remote: Command Failed' with any command i type.
But thats madness, i cant comprehend why it wont boot because everything seems to work!?!
There has to be a way to get my device functioning again.
I am pulling my hair out, i am at a complete loss, it doesn't make sense. PLEASE ANYONE ..... please help....
Thanks HONOR-able enthusiasts for any help, no matter how small! :good: :fingers-crossed: :angel:
Click to expand...
Click to collapse
How comes you have TWRP with a locked bootloader ?
Zarou said:
How comes you have TWRP with a locked bootloader ?
Click to expand...
Click to collapse
??? hi, I.m sorry, i think you must of misread some of my post. I dont blame you, it was bloody long and confusing!
I only mentioned twrp in the very beggining to run you through the steps to my never ending being stuck on honor logo boot animation. I used TWRP to wipe all partitions and format. From there i used 3 button method to install the update.app(B130) on my sd-card. this was succesfull, no errors and rebooted. I didn't expect any problems. But as i explained it never gets past boot logo.
Obviously now, twrp has gone, i am back to stock recovery and my bootloader is locked.
*I can access stock recovery to wipe cache and wipe the phone no problem and all works with no error messages.
*I can access fastboot(bootloader) but the fastboot commands are useless because my bootloader is locked once again and i cant turn on usb debugging or oem unlock in developper options....because my phone wont boot past honor logo...
*Three button method works everytime, 100% success, no errors, reboots but guess what?? IT WONT GET PAST THAT DAMN HONOR BOOT LOGO!!!!!!!!!
Ive tried everything, but NO LUCK. I came up with this idea today though--- download theB130 rollback from nougat to MarshMallow update.zip. Extract the update.app and put that in my sd-card/dload folder and do 3 button install method.
I might even do the same with the nougat B350 just to cover all bases. So i am downloading now, gonna cross my fingers and any other body parts, pray to all the gods...and hopefully i wont be a crying,sniveling,howling piece of mess by tomorrow.
UNLESS OF COURSE SOMEONE HAS THE KNOWLEDGE I SEEK AND IS WILLING TO SHARE IT :fingers-crossed:
thanks Honor-able friends....
iantechie1979 said:
??? hi, I.m sorry, i think you must of misread some of my post. I dont blame you, it was bloody long and confusing!
I only mentioned twrp in the very beggining to run you through the steps to my never ending being stuck on honor logo boot animation. I used TWRP to wipe all partitions and format. From there i used 3 button method to install the update.app(B130) on my sd-card. this was succesfull, no errors and rebooted. I didn't expect any problems. But as i explained it never gets past boot logo.
Obviously now, twrp has gone, i am back to stock recovery and my bootloader is locked.
*I can access stock recovery to wipe cache and wipe the phone no problem and all works with no error messages.
*I can access fastboot(bootloader) but the fastboot commands are useless because my bootloader is locked once again and i cant turn on usb debugging or oem unlock in developper options....because my phone wont boot past honor logo...
*Three button method works everytime, 100% success, no errors, reboots but guess what?? IT WONT GET PAST THAT DAMN HONOR BOOT LOGO!!!!!!!!!
Ive tried everything, but NO LUCK. I came up with this idea today though--- download theB130 rollback from nougat to MarshMallow update.zip. Extract the update.app and put that in my sd-card/dload folder and do 3 button install method.
I might even do the same with the nougat B350 just to cover all bases. So i am downloading now, gonna cross my fingers and any other body parts, pray to all the gods...and hopefully i wont be a crying,sniveling,howling piece of mess by tomorrow.
UNLESS OF COURSE SOMEONE HAS THE KNOWLEDGE I SEEK AND IS WILLING TO SHARE IT :fingers-crossed:
thanks Honor-able friends....
Click to expand...
Click to collapse
OK, sorry for the misunderstanding. Yeah, try that and if this is still not working, I guess all you can do is try the same with other packages.
Hi guys,
I got a G5S+, which got stuck the other day.
It was booting, showing the blue Motorola screen but ended up with a lying down android with a red questionmark and saying 'no command'.
I read through a couple of threads and finally decided, I need to flash stock again.
I did not have switched on USB debugging and so on, as the phone was quite new to me.
I decided to run with that tutorial here:
https://forum.xda-developers.com/g5-plus/how-to/solution-to-flash-stock-romfactory-t3691396
Which seemed to be the right one.
Said so, booted into bootloader, installed the driver on my Win10 PC and ran through the steps.
I gut stuck on 'fastboot flash system system.img_sparsechunk.3' (15mins waiting..... after the steps before required about 12 Sec each) and needed to disconnect and connect the phone again.
Started with the same command and it worked.
Anyway when I got to the command 'fastboot flash system system.img_sparsechunk.5' I realized in the Potter Retail, there is no such file (neither there is 6 or 7).
I skipped the commands and continued.
When it came to rebooting the phone disconnected and thats it.
Since then I am not able to turn my phone back on.
Sometimes there seems to be a small notofication led showing up when trying to turn on the phone.
And you can hear the USB connect sound when I connect it to my computer.
Did anyone of you guys experience the same issue or has an idea what to do?
I have no idea what I shall so.
Best regards,
Matt
Which stock ROM did you flash? I'm hoping that following that guide, you flashed a stock ROM for sanders (i.e. the codename for Moto G5S Plus) and not for potter (codename for G5 Plus), which appear to be not compatible with each other.
Your original issue appears to be your device is booting into the stock recovery (which the start of is the 'no recovery' screen).
Do you know what model number or retail software channel, or the software build you had on your device before it failed? If so, we may be able to flash the correct sanders stock ROM to your device and get it going again. Another user appears to have gotten their device working when they incorrectly flashed the potter stock ROM and not sanders. https://forum.xda-developers.com/moto-g5s-plus/help/bricked-moto-g5s-plus-t3747064 Ideally you will want to flash the correct stock ROM for your device.
Oha damn you are right.
I am an idiot and tried to flash Potter to a G5S Plus.
Oh boy. I should not flash a cellphone after a long day at work.
I had the latest safety update installed and the latest release.
I am not sure though which software that used to be.
Unbelievable.....
Anyway, so my screen does not show anything anymore.
I guess the display driver dows not work or something like that.
The cellphone is still working I think, as the USB sound still appears.
Does anyone have an idea what to do if the screen stays black.
I still cannot believe it.....
Thanks though for your help!
EDIT: fastboot still reckognizes the phone. I guess this is good.
But the command 'fastboot oem fb_mode_set' runs into an error.
Edit2:
I skipped the first command and everything ran through (with some error messages though).
I hope it works now.
Device is currently rebooting and showing the blue motorola screen.
Lucky me.....
Okay, at least your device is booting now (ish)... I saw your other post and was wondering if you were able to boot from the bootloader.
1)Boot to fastboot (probably easiest by powering off your device, then hold down power and volume down keys until your device boots).
2)Once in the fastboot menu (with details about your device, like bootloader version), check that 'Start' is selected, and press the Power button to select. If 'Start' is not showing, use the volume keys to scroll through the options until 'Start' appears. Sometimes, this booting via fastboot bypasses an auto-boot to recovery mode.
Failing that, if you're on the 'no command' screen, then hold down the power button and tap the volume up key. Release both and it should let you into the recovery menu. Then, you can try to reboot to system.
Hi there,
I ran through all the steps you said.
But I ended up having the same issue. I always get back to the broken droid.
Is there a way to flash a completely new ROM to the device in its current condition?
I don't mind having a customrom, but I want to get it working again.
Thanks!
Matt
I solved my problem:
It was the SD card. I cannot believe it.
I got myself another G5S Plus and swapped everything:
Same issue.
So I removed the memory card and all good again.
I am quite sad though not having figured that out earlier, becoz all my data is lost now....
Thanks for your help though!
My problem goes a little further than that. I flashed the stock ROM back onto my phone after having RROS 5.8.5 for quite some time and all of a sudden now I cannot boot my phone past this message on the Lenovo/Motorola splash screen:
Code:
=>FASTBOOT mode...
=>Device lockbroken
on top of this, I'm sure something has happened to he phone through a possible incorrect/incomplete flashing when trying to get my SP Flash Tools to work like it used to (It worked fine before, but this time SPFT didn't want to work giving me BROM errors and mostly error 6045 - FYI I sorted this out by running CCleaner registry clean a few times).
So now, my phone is stuck on this message and when I enter fastboot mode to try to query the phone with
Code:
fastboot devices
, my serial apparently has changed to 0123456789ABCDEF?!
How do I restore my original serial number and get rid of the "lockbroken" message (is there anything to do with NVRAM? Did I wipe it or something?), so I can get on with unlocking and re-rooting my phone? I've not been able to use my phone for about two weeks when I first wiped the OS and my PC just decided not to let SPFT work properly, so now, I've finally got it to flash the stock ROM back on, the last hurdle now is to get past this lockbroken crap!
Thanks in advance,
(don't be afraid to talk techy - I'm not that bad!)
Nathan
try to roll back like on this link: roll back