Related
I tried rooting my phone, but when I flashed CWM my Nexus S stopped booting... it freezes on the Google screen in the intro. I can boot into Fastboot, and cwm, but I cant connect the Internal memory to the computer without it booting like it is supposed to. Does anybody know of anything I can do to fix my phone and bring it back to stock??
There are guides for returning to stock stickied in the Nexus S 4G Android Development forum.
Before you do that though, try flashing a different recovery, like the one linked to here or here.
Btw, which guide did you use? You're not the first person to have this problem, and it's really bugging me (though probably not as much as it's bugging you :-o).
Maximilian Mary: I tried to post the link, but since I'm a new member I have to wait 8 posts before I can post a URL.... :/
I will try a different recovery, but how would I flash a rom if I can connect my phone via usb mount?
deadzunehd said:
Maximilian Mary: I tried to post the link, but since I'm a new member I have to wait 8 posts before I can post a URL.... :/
Click to expand...
Click to collapse
What's the title of the thread?
.
I will try a different recovery, but how would I flash a rom if I can connect my phone via usb mount?
Click to expand...
Click to collapse
I'm a little out of my depth here, but I think it's
fastboot flash system system.img.
You don't need to put the rom image on the sdcard. Just put it in the same folder as fastboot.
It was titled "How to Root Nexus S!"
And I will try to flash recovery and try that rom command, thank you )
deadzunehd said:
It was titled "How to Root Nexus S!"
And I will try to flash recovery and try that rom command, thank you )
Click to expand...
Click to collapse
Hmmm. I can't find that exact title. Could you pm me the link?
deadzunehd said:
thank you )
Click to expand...
Click to collapse
There's a button for that.
I got the link. Thanks. I looks like you flashed a boot image that is incompatible with your phone. That guide was for the T-Mobile Nexus S. (Why they're screwing with the boot.img to begin with, I really don't understand.)
Download the attached file, and unzip it to the same folder as fastboot. The md5 sum is d4a9508f9321eb25df3383f00f571e8b. Then
Code:
fastboot flash boot boot.img
You'll probably also want to use one of the recoveries listed above to
Code:
fastboot flash recovery recovery.img
, but leave system alone for now. Flash that only as a last resort.
deadzunehd said:
I tried rooting my phone, but when I flashed CWM my Nexus S stopped booting... it freezes on the Google screen in the intro. I can boot into Fastboot, and cwm, but I cant connect the Internal memory to the computer without it booting like it is supposed to. Does anybody know of anything I can do to fix my phone and bring it back to stock??
Click to expand...
Click to collapse
I had this problem after flashing the wrong ROM onto my phone. I got the phone back to stock using ODIN.
My thread can be found here
http://forum.xda-developers.com/showthread.php?p=14172335#post14172335
hope it helps
Acnescar said:
I had this problem after flashing the wrong ROM onto my phone. I got the phone back to stock using ODIN.
My thread can be found here
http://forum.xda-developers.com/showthread.php?p=14172335#post14172335
hope it helps
Click to expand...
Click to collapse
OMG!! im having the same issue. could you please post the link for ODIN so i can return to stock and take it from there please? I rely on my phone so much and i need it asap thank you.
same problem with me.
but in my case, the phone not only freeze after the google logo before boot. I tried several times to pull the battery and start the phone again, it took several times until the phone can boot normally again.
After that, my nexus s can work as usual. but it only takes 3-4 hour until it freeze/hangs or reboot automatically and show image of green robot lay down with red alert triangle...
sometimes I noticed all application force closed like gmail, gtalk, etc. (its a basic apps instead of 3rd party app)
History :
- root GB 2.37 using superoneclick
- upgrade OTA to ICS 4.04
- problem happens
- root using guide : nexusshacks.com
- unroot using guide : nexusshacks.com
- back to factory setting on GB 2.34
- upgrade OTA to ICS 4.04
- Still got that problem.....
I'm using Nexus S 4G Sprint, pls help me guys...
nexus s won't boot
I had the same problem and read elsewhere that heating the phone with a hairdryer solves the problem.
I must say, indeed it did.
I removed the battery and the SIM card, then heated up the phone (so it really feels warm) put back the battery and sim and simsalebim the phone started again. and is still working since (now already a few day's)
It seems that a component in the phone is heat sensitive, the question in my mind is when will this show again and do I need to consider buying a new phone.
But sofar it works
PS I also tried hard reset factory reset the lot, but in the end only heating up helped.
Good luck, David
I fixed this problem! but I had to wipe all user data by rooting it using nexusrootICS. It finally boots up and the phone works now... that's all I need.
Hi,
since this morning I have this problem that my Nexus S just boots until the Google logo appears.
I have no idea what caused this. I was just reinstalling the youtube app and rebooted after that and it booted.
Then I noticed that my phone would not change the screen orientation and because it worked in the past I started another reboot. But then it got stuck at the Google logo.
To solve this problem I just wanted to flash my nandroid backup but that didn't work as well cause the recovery was not able to mount the sdcard.
E:Can't mount /sdcard
Does anyone have an idea how to solve this problem? By the way is it possible to pull the Nandroid backup from the phone to my computer with ADB for example. Would be great because (of course) I just have an backup on my phone... (but if not... well, **** happens)
Thanks in advance!
PedroBustamonte said:
Hi,
since this morning I have this problem that my Nexus S just boots until the Google logo appears.
I have no idea what caused this. I was just reinstalling the youtube app and rebooted after that and it booted.
Then I noticed that my phone would not change the screen orientation and because it worked in the past I started another reboot. But then it got stuck at the Google logo.
To solve this problem I just wanted to flash my nandroid backup but that didn't work as well cause the recovery was not able to mount the sdcard.
E:Can't mount /sdcard
Does anyone have an idea how to solve this problem? By the way is it possible to pull the Nandroid backup from the phone to my computer with ADB for example. Would be great because (of course) I just have an backup on my phone... (but if not... well, **** happens)
Thanks in advance!
Click to expand...
Click to collapse
flasgh stock via fastboot and wipe everything DONE!
i had this problem when i flashed a non-cm kernel on a cm-based rom. try flashing a different kernel. know what kernel your rom is compatible to,
Cascabreu said:
flasgh stock via fastboot and wipe everything DONE!
Click to expand...
Click to collapse
So there's no way to get the content of the sdcard before I wipe everything?
ej8989 said:
i had this problem when i flashed a non-cm kernel on a cm-based rom. try flashing a different kernel. know what kernel your rom is compatible to,
Click to expand...
Click to collapse
I'm using ParanoidAndroid with Mamite (the version for cm based roms since PA is also based on cm)
PedroBustamonte said:
So there's no way to get the content of the sdcard before I wipe everything?
I'm using ParanoidAndroid with Mamite (the version for cm based roms since PA is also based on cm)
Click to expand...
Click to collapse
Go to mounts and storage in CWM Recovery and "mount usb storage". That will let you get to your SD card to backup. Then I suggest just a clean wipe and start over.
Note: mount /sdcard just mounts it to the phone. You are wanting to mount it to your computer to pull the files off the external.
mdean1981 said:
Go to mounts and storage in CWM Recovery and "mount usb storage". That will let you get to your SD card to backup. Then I suggest just a clean wipe and start over.
Note: mount /sdcard just mounts it to the phone. You are wanting to mount it to your computer to pull the files off the external.
Click to expand...
Click to collapse
Yup thank you. Already tried that and a lot of other stuff. Seems like my phone's broken. I can't write on or erase /system or /sdcard. I'll try today to lock the bootloader and then unlock it. Maybe that solves the problem...
It will also wipe everything if I remember well
Envoyé depuis mon Nexus S avec Tapatalk
PedroBustamonte said:
Yup thank you. Already tried that and a lot of other stuff. Seems like my phone's broken. I can't write on or erase /system or /sdcard. I'll try today to lock the bootloader and then unlock it. Maybe that solves the problem...
Click to expand...
Click to collapse
dont lock it cuz u wont be able to unlock it after. unlocking requires being able to erase the sdcard
tested it my self yesterday on a phone with the same issue
Cascabreu said:
dont lock it cuz u wont be able to unlock it after. unlocking requires being able to erase the sdcard
tested it my self yesterday on a phone with the same issue
Click to expand...
Click to collapse
Yes you're right. But I really can't think of any thing I could try.
PedroBustamonte said:
Yes you're right. But I really can't think of any thing I could try.
Click to expand...
Click to collapse
It's interesting and maybe fortuite that this is happening to you just as something almost equal happens to me (see here: http://forum.xda-developers.com/showthread.php?t=1972447 ) You should also enter the recovery via adb from your computer if you have it, and check if a) you have mmc* files in /dev/block and b) have mmc error messages in dmesg (in the phone: "dmesg|grep mmc" and look for lines with "error" in them).
Btw to the person who suggested flashing stock thorough fastboot, do you mean stock system, system+boot or system+boot+recovery ? and where could I find those stock .img please? Mine's an i9020a
Blissfull said:
It's interesting and maybe fortuite that this is happening to you just as something almost equal happens to me (see here: http://forum.xda-developers.com/showthread.php?t=1972447 ) You should also enter the recovery via adb from your computer if you have it, and check if a) you have mmc* files in /dev/block and b) have mmc error messages in dmesg (in the phone: "dmesg|grep mmc" and look for lines with "error" in them).
Btw to the person who suggested flashing stock thorough fastboot, do you mean stock system, system+boot or system+boot+recovery ? and where could I find those stock .img please? Mine's an i9020a
Click to expand...
Click to collapse
Factory Images for Nexus Devices
https://developers.google.com/android/nexus/images
Hi ^^
I had the same problem with my Nexus S a long time ago and never found out how to solve it. It seems that the internal memory is corrupted and nothing but replacing the motherboard can solve it. Since I bought mine in the USA but I live in Belgium I never got mine repaired. Sometimes I come back here to see if there is still no solution but each time I'm disappointed...
Sorry.
PedroBustamonte said:
Yes you're right. But I really can't think of any thing I could try.
Click to expand...
Click to collapse
Cascabreu said:
dont lock it cuz u wont be able to unlock it after. unlocking requires being able to erase the sdcard
tested it my self yesterday on a phone with the same issue
Click to expand...
Click to collapse
I can confirm this. I had the same thing happen to my Nexus S 4G recently. I was never able to salvage any data off the sdcard no matter what I tried (various mounting attempts in recovery, any adb command I thought might be helpful, etc.). As a last resort I tried to lock/unlock the bootloader - once I locked it, I was unable to unlock it again, it just froze up after asking me if I was sure I wanted to unlock. I guess that's what happens when the internal sdcard goes to hell. I ended up taking it to my local Sprint store and they replaced the phone with a refurbished one from Samsung (for approximately $35).
Rooted my N5 yesterday and it was working fine. Then today, I was trying to flash the Camera app from Jinshu when I got stuck on the dancing circles screen... went back into TWRP recovery and, I think, accidentally flashed the entire internal storage...
I can still get into TWRP, but when I click reboot > system , I get a warning message "No OS Installed! Are you sure you wish to reboot?" :crying:
I am using a Mac and have the SDK etc. installed, but I don't even see the device as a USB device in order to try and figure out how to get the system files back on the device.
Any help would be appreciated.
Thanks,
A
You've got a few options...forgive me if you've tried any of these already...I'm just offering ideas for you to find one that works for you...
1) restore a nandroid backup if you have one
or
2) ADB sideload a zip for one of the roms in the development sections
or
3) ADB push then flash a zip from the development sections
or
4) Flash the factory images using fastboot
DaMonster said:
Rooted my N5 yesterday and it was working fine. Then today, I was trying to flash the Camera app from Jinshu when I got stuck on the dancing circles screen... went back into TWRP recovery and, I think, accidentally flashed the entire internal storage...
I can still get into TWRP, but when I click reboot > system , I get a warning message "No OS Installed! Are you sure you wish to reboot?" :crying:
I am using a Mac and have the SDK etc. installed, but I don't even see the device as a USB device in order to try and figure out how to get the system files back on the device.
Any help would be appreciated.
Thanks,
A
Click to expand...
Click to collapse
Download this ROM (Odex)
http://forum.xda-developers.com/showthread.php?t=2507861
Boot in TWRP, and either use adb sideload:
./adb sideload path_to_hammerhead_KRT16M_odex_signed.zip
or use adb push
./adb push path_to_hammerhead_KRT16M_odex_signed.zip /data/media/0
Then proceed with flashing it from recovery.
Yep, you have plenty of options so don't panic. Personally, I'd use this as an opportunity to teach yourself how to setup and use ADB and Fastboot commands to flash factory images. Once you teach yourself how to do this properly you will no longer get overly concerned when another situation like this inevitably occurs. This will be a learning experience that you will benefit from later on.
If you are on a Mac, follow THIS GUIDE to properly setup ADB/Fastboot for use. Then use THIS GUIDE to learn how to properly flash a factory image.
Thanks for your quick responses guys...
While I was searching, I found this site: liciousroms dot com slash nexus5_restore.html (sorry, cannot post URLs just yet!)
I was able to get the stock .img files from the download package for system, recovery and boot, and as you guys pointed out, learned the utility of fastboot to get the images onto the device
Recovered, booted, and just getting back in business.
Thanks so much !!!
- A
For other folks that will run into this problem, note that TWRP 2.6.3.1 supports USB OTG. You can load a ROM into an sd card, plug it into the USB OTG cable and then into the phone and TWRP will mount it.
DaMonster said:
Thanks for your quick responses guys...
While I was searching, I found this site: liciousroms dot com slash nexus5_restore.html (sorry, cannot post URLs just yet!)
I was able to get the stock .img files from the download package for system, recovery and boot, and as you guys pointed out, learned the utility of fastboot to get the images onto the device
Recovered, booted, and just getting back in business.
Thanks so much !!!
- A
Click to expand...
Click to collapse
A few things:
1) I wouldn't download stock images from any websites other than official. People could bake in all kinds of stuff. There's no need for other sites to re-host official stock images, so there's usually a reason why they would.
2) I mean no offense by this, but if you're unsure enough in what you're doing to accidentally format the entire internal storage then you should do a lot more research before attempting this stuff. This is reversible, your next accident might not be. I don't ordinarily assume, but judging by your username and the accident you've committed I'd assume you're fairly young...so blowing another $400 on a new device because you bricked this one from a mistake is probably a big deal. Take some time and understand, completely, what you're doing.
3) That being said, Nexus devices are made to be open. They're made for people to modify and have fun with. Explore and experiment all you want, just make sure to have a good NANDROID backup before you do.
hotleadsingerguy said:
1) I wouldn't download stock images from any websites other than official. People could bake in all kinds of stuff. There's no need for other sites to re-host official stock images, so there's usually a reason why they would.
3) That being said, Nexus devices are made to be open. They're made for people to modify and have fun with. Explore and experiment all you want, just make sure to have a good NANDROID backup before you do.
Click to expand...
Click to collapse
Good point. I'll reflash to the openrecovery-twrp-xxx version shortly anyway, but the point is valid and I'll make sure to have an official image and regular NANDROID backups handy for future experiments
hotleadsingerguy said:
2) I mean no offense by this, but if you're unsure enough in what you're doing to accidentally format the entire internal storage then you should do a lot more research before attempting this stuff. This is reversible, your next accident might not be. I don't ordinarily assume, but judging by your username and the accident you've committed I'd assume you're fairly young...so blowing another $400 on a new device because you bricked this one from a mistake is probably a big deal. Take some time and understand, completely, what you're doing.
Click to expand...
Click to collapse
None taken. I'm not really young, just new to Android/ tinkering. In any case, blowing $400 on a device is still a big deal and I want to avoid that like a plague Alas, youth has no monopoly on stupid.
zerogun said:
For other folks that will run into this problem, note that TWRP 2.6.3.1 supports USB OTG. You can load a ROM into an sd card, plug it into the USB OTG cable and then into the phone and TWRP will mount it.
Click to expand...
Click to collapse
Thanks for the info. I have a USB-OTG cable on order (for a different purpose), and this is good for future reference.
DaMonster said:
Thanks for the info. I have a USB-OTG cable on order (for a different purpose), and this is good for future reference.
Click to expand...
Click to collapse
Okay guys, im in serious trouble too. ADB sideload does not seem to work for me.
ADB devices is resulting into finding my device but sideload is not working... What to do now?
J_Dutch said:
Okay guys, im in serious trouble too. ADB sideload does not seem to work for me.
ADB devices is resulting into finding my device but sideload is not working... What to do now?
Click to expand...
Click to collapse
Use "adb push" to copy a zip from your PC to your phone.
The command would be like this:
adb push path/to/zip data/media/0
same issue
I am in the same boat as this guy. tried to load the sideloader via twrp but i get a...
E: unable to mount ;/usb-otg'
then it attempts to load it but it has been doing so for the last 15mins
minerva330 said:
I am in the same boat as this guy. tried to load the sideloader via twrp but i get a...
E: unable to mount ;/usb-otg'
then it attempts to load it but it has been doing so for the last 15mins
Click to expand...
Click to collapse
Just restore a nandroid in twrp
still a noob
jd1639 said:
Just restore a nandroid in twrp
Click to expand...
Click to collapse
Excuse my ignorance: but should I back all the partitions? Also, if the system has been wiped, what's the point?
minerva330 said:
Excuse my ignorance: but should I back all the partitions? Also, if the system has been wiped, what's the point?
Click to expand...
Click to collapse
I wouldn't worry about backing up at this point
still a noob
jd1639 said:
I wouldn't worry about backing up at this point
Click to expand...
Click to collapse
Sorry, I misunderstood your previous statement.
I have no back-up to restore (don't even get me started, I am quite ashamed)
minerva330 said:
Sorry, I misunderstood your previous statement.
I have no back-up to restore (don't even get me started, I am quite ashamed)
Click to expand...
Click to collapse
Dude, your kidding me. You have a custom recovery and no backup. It would have made your life so easy. Now you'll have to flash the factory image
truly ashamed
jd1639 said:
Dude, your kidding me. You have a custom recovery and no backup. It would have made your life so easy. Now you'll have to flash the factory image
Click to expand...
Click to collapse
I know...that one time I don't (not one of my better moments). It's a new phone. I have done this a hundred times before
I have the factory image on my computer but I can't get it to push to my phone. My ADB driver are installed but my phone wont mount from the USB in TWRP.
minerva330 said:
I know...that one time I don't (not one of my better moments). It's a new phone. I have done this a hundred times before
I have the factory image on my computer but I can't get it to push to my phone. My ADB driver are installed but my phone wont mount from the USB in TWRP.
Click to expand...
Click to collapse
Boot into boot loader and use the flash-all.bat that's inside the factory image. Unzip it using 7-zip. You'll see it in there. Boot into bootloader, plug your usb cable in and run the bat file
Edit, you'll lose everything on your phone
jd1639 said:
Boot into boot loader and use the flash-all.bat that's inside the factory image. Unzip it using 7-zip. You'll see it in there. Boot into bootloader, plug your usb cable in and run the bat file
Edit, you'll lose everything on your phone
Click to expand...
Click to collapse
How can I unzip a file from the factory image on my phone if it is on desktop? Am I missing something (thanks for tolerating this)?
At this point I could care less about loosing any apps, data, or pics,
Hey guys when i was flashing a new rom i mistakenly wiped the whole internal storage and /system folder now there is no OS and also sideload and adb push fails giving me a device not found error. i have installed the drivers too!! guys please help me!! i also unlocked bootloader now no warranty!! itz been a day since i bought it!! pls help me ppl!! is there a way to mount the internal storage as usb or sumthng?? i have twrp and unlocked bootloader.
yeshwanthvshenoy said:
Hey guys when i was flashing a new rom i mistakenly wiped the whole internal storage and /system folder now there is no OS and also sideload and adb push fails giving me a device not found error. i have installed the drivers too!! guys please help me!! i also unlocked bootloader now no warranty!! itz been a day since i bought it!! pls help me ppl!! is there a way to mount the internal storage as usb or sumthng?? i have twrp and unlocked bootloader.
Click to expand...
Click to collapse
Flashing a ROM effectively writes over /system anyway, you need to do some reading to understand what you are actually doing. But basically you need to boot into bootloader and use fastboot not adb. Many tutorials exist so a search on xda will be all you need to so the rest.
scott_doyland said:
Flashing a ROM effectively writes over /system anyway, you need to do some reading to understand what you are actually doing. But basically you need to boot into bootloader and use fastboot not adb. Many tutorials exist so a search on xda will be all you need to so the rest.
Click to expand...
Click to collapse
now my device isnt charging and not booting up!!! am thinking of replacing it. is it psbl? coz i unlocked my bootloader but i have a 30 day replacement guarantee and my device isnt turning on now?? itz been 2 days since i bought it.
I would ask you to get it service centre to flash the system again, and PAY them the normal service charge. You can ask the service centre guy to install a new motherboard , because i think that will come with Memory and OS pre-installed.
I am not expert on this matters, suggest you to search deeply on XDA or wait for an Expert to answer otherwise; i have listed the options available to you.
You could also try leaving it on charger for a day to see if charging starts.
Since your whole memory is wiped clean, it basically a Bricked device.
aayush_neov said:
I would ask you to get it service centre to flash the system again, and PAY them the normal service charge. You can ask the service centre guy to install a new motherboard , because i think that will come with Memory and OS pre-installed.
I am not expert on this matters, suggest you to search deeply on XDA or wait for an Expert to answer otherwise; i have listed the options available to you.
You could also try leaving it on charger for a day to see if charging starts.
Since your whole memory is wiped clean, it basically a Bricked device.
Click to expand...
Click to collapse
No it didn't brick the device, he has wiped system that's all.
scott_doyland said:
No it didn't brick the device, he has wiped system that's all.
Click to expand...
Click to collapse
Just get the right StockRom and flash it via PC ...thats all ...install all necessary drivers ...and go on ...if system is formatted then no need to go to service center ....
prachetas13 said:
Just get the right StockRom and flash it via PC ...thats all ...install all necessary drivers ...and go on ...if system is formatted then no need to go to service center ....
Click to expand...
Click to collapse
First he needs power in his Battery
Moto E4 XT1766
Partition Index & Bootloader Updater
Build No. NCQ26.69-64
TWRP Flashable Installer
WARNING: DO NOT use this updater.zip if your device has been updated to any firmware version newer than NCQ26.69-64. Downgrading can hard brick your device. If your device has been upgraded to a newer build, or if you aren't sure, proceed to this thread: https://forum.xda-developers.com/moto-e4/how-to/firmware-restoring-moto-e4-xt1766-t3820749, which is the latest firmware -- NCQS26.69-64-5.
DISCLAIMER: Although I have thoroughly tested this update installer, I am not responsible for any adverse effects incurred from using it. Because this installer does flash bootloader and other sensitive partitions on your device, charging your device to at least 50% is recommended prior to proceeding.
PURPOSE:
This installer updates your partition index and bootloader components to Build No. NCQ26.69-64. If you are not running the stock Android OS, or have never updated your device to Build No. NCQ26.69-64, this installer will update your partition index (gpt.bin) and bootloader components to the most current firmware version. For custom ROM users, this alleviates the task of reverting to an unmodified stock Android OS, installing OTAs, and then reinstalling your daily driver custom ROM -- all to simply update your bootloader and partition index. Specifically, this installer updates the following partitions:
/rpm - primary bootloader
/sbl1 - secondary bootloader
/aboot - application bootloader
/tz - trust zone (bootloader component)
/devcfg - device configuration (component)
/keymaster - bootloader component
/cmnlib - bootloader component
/cmnlib64 - bootloader component
/prov - bootloader component
INSTRUCTIONS:
Download the updater zip from the below link and save it to internal or external storage. Boot into TWRP, install the zip, and reboot. Your partition index and bootloader are now up to date. Note: this update can be installed on a stock or custom ROM.
DOWNLOAD LINK:
https://drive.google.com/file/d/18eFi6E1YnNB68OwmEJeH0FGmAVsE89Jo/view?usp=drivesdk
Very cool, thanks brother
Sent from my XT1766 using Tapatalk
@MotoJunkie01 it worked fine, but I got this error. Anything to worry about?
Thanks for this bro.
@madbat99, nothing to worry about. It's a pseudo-error due to a conflict in the update-binary. I'll iron it out just because it messes with my OCD. :good:
MotoJunkie01 said:
@madbat99, nothing to worry about. It's a pseudo-error due to a conflict in the update-binary. I'll iron it out just because it messes with my OCD. :good:
Click to expand...
Click to collapse
I figured. Just thought I'd ask. Thanks again
madbat99 said:
@MotoJunkie01 it worked fine, but I got this error. Anything to worry about?
Thanks for this bro.
Click to expand...
Click to collapse
How did you screenshot in the recovery?
frederickrl said:
How did you screenshot in the recovery?
Click to expand...
Click to collapse
Same way as in the os. Power + volume down
madbat99 said:
Same way as in the os. Power + volume down
Click to expand...
Click to collapse
I thought it may be, twrp is so advanced thx!
Hard bricked
I need help my phone is hard bricked just showing on PC as an unknown usb device..
I have flashed wrong firmware my device sperry xt1766..
Please help
My phone xt1766 is bricked by flashing wring firmware on pc showinh qhs usb dload and unable to power on...
please help
hassanshaikhhyd said:
My phone xt1766 is bricked by flashing wring firmware on pc showinh qhs usb dload and unable to power on...
please help
Click to expand...
Click to collapse
Your phone is most likely in edl not sure what solution would be at this time
skullkid383 said:
Your phone is most likely in edl not sure what solution would be at this time
Click to expand...
Click to collapse
is there change of its solution in future
hassanshaikhhyd said:
is there change of its solution in future
Click to expand...
Click to collapse
I might be getting second more e4 when I get paid as a test subject cause my friend had same problem so I want to find a solution for this if and when I do I'll me u know
Bricked
Same prob, flashed it on twrp and everything looked good until it shut off completely and never powered back on.
Tried hard reset. won't even go into recovery/
I just forresst gumped my xt1765 too, i just noticed this update was for xt1766, not xt1765. Been trying out RR, AICP and Lineage with minor bugs, then thought this update might correct minor bugs since not build as specified here. Anyways, flashed favorite after trying all custom roms for few weeks at a time and decided that LineageOS was my favorite with least bugs/issues but after flashing LineageOS it felt just right. Like finding your favorite fitting lost pair of jeans or hooking up with an ex again....just felt right...anyways, short story and heartbreak after I flashed this zip, my beloved moto gen E4, my nickname, get it Jenny no. 4? Our last kiss was the reboot system kiss and caress....and just like that, she was gone forever...no power, no recovery, no nothing at all... and just now the small print cognizant epiphany opened my dreamy happily perpetually sleeping eyes. the perfect device, fast as i wanted, tweaked like i liked and she never complained or got mad or talked back well she did when i needed googlies answered...this zip was for the sperry xt1766...now my moto genE4 is gone forever....
Ive been flashing for years all kinds of different devices and never have I had this type of problem..there was always the fallback flashing back to stock if bootlooped or soft bricked. Flash, boom, fixed, start over. Never have I encountered the no power no charge no nothing one last kiss goodbye, EVER. Well, life lesson learned. I just needed to get that off my chest. I feel a little better now guys, thanks for listening.
cuervo233 said:
I just forresst gumped my xt1765 too, i just noticed this update was for xt1766, not xt1765. Been trying out RR, AICP and Lineage with minor bugs, then thought this update might correct minor bugs since not build as specified here. Anyways, flashed favorite after trying all custom roms for few weeks at a time and decided that LineageOS was my favorite with least bugs/issues but after flashing LineageOS it felt just right. Like finding your favorite fitting lost pair of jeans or hooking up with an ex again....just felt right...anyways, short story and heartbreak after I flashed this zip, my beloved moto gen E4, my nickname, get it Jenny no. 4? Our last kiss was the reboot system kiss and caress....and just like that, she was gone forever...no power, no recovery, no nothing at all... and just now the small print cognizant epiphany opened my dreamy happily perpetually sleeping eyes. the perfect device, fast as i wanted, tweaked like i liked and she never complained or got mad or talked back well she did when i needed googlies answered...this zip was for the sperry xt1766...now my moto genE4 is gone forever....
Ive been flashing for years all kinds of different devices and never have I had this type of problem..there was always the fallback flashing back to stock if bootlooped or soft bricked. Flash, boom, fixed, start over. Never have I encountered the no power no charge no nothing one last kiss goodbye, EVER. Well, life lesson learned. I just needed to get that off my chest. I feel a little better now guys, thanks for listening.
Click to expand...
Click to collapse
The old dreaded hard brick. Lights out time. Been there done that. Have you read this method to restore your device using a microSD card? https://forum.xda-developers.com/moto-e4/how-to/untested-moto-e4-xt1765-metropcs-t3843657
This guide for the xt1766 gives overview to the method as well. https://forum.xda-developers.com/moto-e4/how-to/e4-sprint-xt1766-unbrick-easy-sdcard-t3833408/page2
Basically, download the unbrick image for your xt1765 from the 1st link I posted above. Then, see the second link on the xt1766 for instructions on attempting the unbrick.
I had 1766 that broke so I put the back of it in another Moto e4 plus....just wondering if I have any options...
Amphetmine Gene said:
I had 1766 that broke so I put the back of it in another Moto e4 plus....just wondering if I have any options...
Click to expand...
Click to collapse
Wait...seen this before. Bad form pooping the same post in multiple threads.
https://forum.xda-developers.com/mo...droid-7-1-1-rom-moto-e4-t3885821/post79275927
Davey126 said:
Wait...seen this before. Bad form pooping the same post in multiple threads.
https://forum.xda-developers.com/mo...droid-7-1-1-rom-moto-e4-t3885821/post79275927
Click to expand...
Click to collapse
Thanks man, yea only 2nd time I've ever posted anything...but good to no
No permission to downloader
HI.
I need this file.
Google not permission to downloader