I got a serious issue here. When I turn on my phone, it freezes on the black background/white text "Samsung" screen, and won't load the OS and will stay like that until I pull out the battery. I researched on this site how to fix this issue found out about the 3 button combo (Vol +, Vol -, Power), tried it on my phone, and it didn't work.
I'm panicking now since it seems like I seriously bricked my phone. Did I?? Are there any other solutions??
If it helps, here are details how I ran into this issue:
I tried to install Cyanogen mod using ROM Manager, and it rebooted my phone into what I think is the recovery mode. However, I kept getting this "E: signature verification failed" error which I learned later is what Google implemented with Froyo to prevent people from installing custom roms. I did some research, and I found this xda thread on how to fix it: http://forum.xda-developers.com/showthread.php?p=12321787#post12321787
According to "kisfit2000," I needed to download this file called 3e_recovery_installer.zip and run the install.bat file. I did it and ran into the error:
Installing modified recovery
rm failed for /system/bin/recovery, No such file or directory
failed to copy 'C:\User\HomeDesktop\xxx\xxx' to '/system/bin/recovery': No space left on device'
Unable to chmod /system/bin/recovery: No such file or directory
Click to expand...
Click to collapse
At that point, I gave up and restarted my phone. And that's when the problem began...
See the other thread you made with the same exact post.
Hey guys,
I'm running the galaxy nexus yakju IMM76I, with the stock google image, no root and unlocked bootloader. All of a sudden today, the phone restarted, and hangs on the loading animation and restarts continuously. I've tried 2 things that have both failed and I'm not sure what other route to take.
1) Bootloader - fastboot
I tried flashing the stock images, erase data , stock radio's etc, but every command from fastboot ends with:
"FAILED (status read failed (Too many links))"
as a reuslt, the bootloader screen goes blurry and hangs, requiring a battery pull to restart.
The device is recognized, and I'm following a similar procedure to when I moved to Yakju in the first place, and no commands will work. After this failed I tried booting into CWM and booting into it, it gives errors listing the following:
"E:Can't mount /cache/recovery/command"
BUT, still allows me to navigate clockwork recovery. Any commands that I try to run through cause the phone to crash and reboot.
2) Odin
I tried flashing the recovery images through Odin , and every time, the download mode screen gets blurry and I have to pull the battery to reboot the phone.
So in summary, the phone continously reboots if I try a straight startup, fastboot flashing causes the screen to go blurry, as does Odin flashing from download mode. Not sure what else I can do to get this back to stock. Also, I don't care if my data is wiped, any help would be much appreciated!
Hello folks, hopefully somebody can help me out with this issue or I may just have to bite the bullet and see what the repair costs are going to be from Acer. I have an Iconia A100 that is unlocked and rooted. I never did get around to loading a custom ROM (was waiting for the JB ROMs to get a little bit more stable) and was just running the stock ICS. It also seems that I didn't successfully load a recovery image so I now seem to be totally out of luck. I went to use my tablet while it was still on but the screen refused to turn on after pressing the home button or pressing the power button. So I decided to reset it and figured that would fix it. Now it's stuck booting to the screen with the distorted text at the top and the multiple acer logos at the bottom. I've tried a factory reset to clear the cache and that didn't help although it did say deleting user data and cache. I tried booting into recovery but found that the CWM that I thought I had installed wasn't installed and all I get is a fallen down android icon with a red exclamation over it. If I power up holding down the volume up key and then flicking the screen rotation switch I get it to display that it's in USB fastboot mode but if I type in adb devices it doesn't get listed as an attached device when hooked into my PC. One other note if I leave it at the distorted text and plug it into my PC via USB Windows 7 detects it as a MPT USB Device which it's not able to locate a driver for.
Ok, some additional information:
I was trying to get something out of the screen where I have the fallen down android with the red exclamation point over it and it seems that the default recovery is still installed in Android system recovery (3e). I can't seem to select any menu options on the screen but it does give some additional info. It looks like the eMMC may be partially or completely borked, I'm not sure which. Here's what's on the screen:
Android system recover (3e)
Android system recovery utility
reboot system now
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
Then in yellow text:
E: Can't open /dev/block/mmcblk0p5
(No such file or directory)
E: failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/command
E: failed to mount /cache (No such file or directory)
This goes on for a bit of being unable to open various directories. Is there anyway at this point to re-lock the bootloader and erase traces of doing so? I find it hard to believe that unlocking the bootloader would cause what seems to be a hardware fault but I could be wrong.
nsafreak said:
Hello folks, hopefully somebody can help me out with this issue or I may just have to bite the bullet and see what the repair costs are going to be from Acer. I have an Iconia A100 that is unlocked and rooted. I never did get around to loading a custom ROM (was waiting for the JB ROMs to get a little bit more stable) and was just running the stock ICS. It also seems that I didn't successfully load a recovery image so I now seem to be totally out of luck. I went to use my tablet while it was still on but the screen refused to turn on after pressing the home button or pressing the power button. So I decided to reset it and figured that would fix it. Now it's stuck booting to the screen with the distorted text at the top and the multiple acer logos at the bottom. I've tried a factory reset to clear the cache and that didn't help although it did say deleting user data and cache. I tried booting into recovery but found that the CWM that I thought I had installed wasn't installed and all I get is a fallen down android icon with a red exclamation over it. If I power up holding down the volume up key and then flicking the screen rotation switch I get it to display that it's in USB fastboot mode but if I type in adb devices it doesn't get listed as an attached device when hooked into my PC. One other note if I leave it at the distorted text and plug it into my PC via USB Windows 7 detects it as a MPT USB Device which it's not able to locate a driver for.
Ok, some additional information:
I was trying to get something out of the screen where I have the fallen down android with the red exclamation point over it and it seems that the default recovery is still installed in Android system recovery (3e). I can't seem to select any menu options on the screen but it does give some additional info. It looks like the eMMC may be partially or completely borked, I'm not sure which. Here's what's on the screen:
Android system recover (3e)
Android system recovery utility
reboot system now
apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
Then in yellow text:
E: Can't open /dev/block/mmcblk0p5
(No such file or directory)
E: failed to mount /cache (No such file or directory)
E:Can't mount /cache/recovery/command
E: failed to mount /cache (No such file or directory)
This goes on for a bit of being unable to open various directories. Is there anyway at this point to re-lock the bootloader and erase traces of doing so? I find it hard to believe that unlocking the bootloader would cause what seems to be a hardware fault but I could be wrong.
Click to expand...
Click to collapse
Its a typical emmc brick, there's threads all over about this. All you can do is send it to acer for repair, sorry to say.
Plug it in and let try to boot on its own for an hour or so, what you want is failsafe, blue power led on but screen off. Then send it to Acer.
Sent from my Galaxy Nexus using xda app-developers app
Hello All,
I have GPE version of GPad running Kitkat 4.4 Stock ROM. Last month I have used following link to enable chromecast mirroring. Due to the issues i have uninstalled superuser app and did factory reset. After that all well! I mean no issues with tablet.
http://forum.xda-developers.com/har...experimental-enable-mirroring-device-t2812193
Yesterday I tried to sideload the GPE lollipop update but prompted with following error.
"/system/etc/audio_policy.conf" has unexpected contents.
E:Error in /tmp/update.zip
(Status 7)
Installation aborted.
This morning I saw system update notification for Lollipop upgrade and opted to install it, but without any further msg during the system update it prompted with "Error!" After that I did factory reset. When it reboots starts optimizing 48 apps, but it prompts with following sequence of messages:
"Unfortunately sun beam has stopped. "
None of the apps loaded , no access to setting, just empty screen and on screen buttons at the bottom.
I spent quite some time looking around in xda to restore back to factory, none seems to work.
1. Tried flashing original stock .tot file, getting "Download user image is only available in the online environment!!
2. adb sideload, "/system/etc/audio_policy.conf" has unexpected contents
3. To Flash TWRP i am not getting access to setting to enable USB debugging.
Now i cant even put the G Pad in adb as i dont have access to settings to put in USB debug mode. vol down+power puts into bootloader, but cant access to adb commands.
Now I can only access to recovery and do sideload. but i am stuck with "/system/etc/audio_policy.conf" has unexpected contents error. Can someone share kitkat original version of audio_policy.conf? also how i can replace the exiting file as i dont have access to adb?
Greatly appreciate your help to bring back the G Pad.
regards
Raj
You can boot twrp from fastboot and flash either 4.4.4 or 5.0 back onto your tablet. Look at the thread in Android development for more details on flashing the stock images using twrp
Thanks! I was able to get back to kitkat with following method. I was able to flash recovery its now back to complete stock kitkat now.
http://forum.xda-developers.com/lg-...510-gpe-4-4-4-ktu84p-l002-stock-twrp-t2797883
After this I got system update notification to lollipop. Again got "Error!" msg during the install process.
I tried adb side load, got following error!
failed to verify whole-file signature
signature verification failed
installation aborted.
Any thought whats going wrong there?
Hi,
I need some help with my OnePlus 3 running the latest or close to latest Android 8 OTA stock rom. It started half year ago, suddenly the phone was in a boot loop. I switched it on and off and I managed it to start again, doing a factory reset and wiping cache data. Then I reentered my details and selected a password. It was working for some days again, but I struggled to enter the right password after a while. Not because I'm stupid, it's pretty easy and I did it again and again. Then it was accepted and the phone was running again. I backuped my data and wiped it again just to check whats going on with that password. After restart I reentered all my data with password 0000. After restarting, it started again having trouble to enter the right password... not accepted. Switching on and off and then suddenly 0000 was accepted.... I don't know, I was tired to use this phone anymore and left it on my desktop.
Now half a year later. I want to fix this somehow and I thought, ok nothing to lose. I try that new Android 9 beta with adb sideload. Before that I'll do a full wipe loosing all my data (no problem). The wiping bar stucks at 99% and then it says "Format failed" with the only option "Yes". So stuck there, not started to sideload so far.
Update 1:
If I select that "Yes", I'm back in that erasing menu, with 3 options factory reset, wiping cache and erasing everything... if I select the last option again, it takes a second saying "Format failed"... I could do this forever. But if I select another option like wiping data something strange happens. It opens up a password screen asking for password... none of my passwords are working there. It is starting to decrypt... but stops with vibration and I'm back in that password screen. Only option that is left is "Forget password". If I select that, it is warning me, that I'll lose all my data. I say "Yes" and it's rebooting with a Chinese screen with a bar stucking at 99% again. That after a while the screen turns black. Phone is rebooting into that Chinese screen again, animating the bar to 100% again, switching itself off. If I start normal, Android logo appears, thats it, no OnePlus circle is coming up. Then I did it once more... "Chinese init/wiping loop" again. So I can restart normally having this or restart in recovery to do all the things as before.
Update 2:
After showing up the Chinese init/wipe loop again it restarted but now with red/white OnePlus circle animation. As you read this, it's still rotating...
Are there any thoughts about it... has this phone a hardware damage or what can I do? I appreciate any ideas.
Cheers, cyx
cyx said:
Hi,
I need some help with my OnePlus 3 running the latest or close to latest Android 8 OTA stock rom. It started half year ago, suddenly the phone was in a boot loop. I switched it on and off and I managed it to start again, doing a factory reset and wiping cache data. Then I reentered my details and selected a password. It was working for some days again, but I struggled to enter the right password after a while. Not because I'm stupid, it's pretty easy and I did it again and again. Then it was accepted and the phone was running again. I backuped my data and wiped it again just to check whats going on with that password. After restart I reentered all my data with password 0000. After restarting, it started again having trouble to enter the right password... not accepted. Switching on and off and then suddenly 0000 was accepted.... I don't know, I was tired to use this phone anymore and left it on my desktop.
Now half a year later. I want to fix this somehow and I thought, ok nothing to lose. I try that new Android 9 beta with adb sideload. Before that I'll do a full wipe loosing all my data (no problem). The wiping bar stucks at 99% and then it says "Format failed" with the only option "Yes". So stuck there, not started to sideload so far.
Update 1:
If I select that "Yes", I'm back in that erasing menu, with 3 options factory reset, wiping cache and erasing everything... if I select the last option again, it takes a second saying "Format failed"... I could do this forever. But if I select another option like wiping data something strange happens. It opens up a password screen asking for password... none of my passwords are working there. It is starting to decrypt... but stops with vibration and I'm back in that password screen. Only option that is left is "Forget password". If I select that, it is warning me, that I'll lose all my data. I say "Yes" and it's rebooting with a Chinese screen with a bar stucking at 99% again. That after a while the screen turns black. Phone is rebooting into that Chinese screen again, animating the bar to 100% again, switching itself off. If I start normal, Android logo appears, thats it, no OnePlus circle is coming up. Then I did it once more... "Chinese init/wiping loop" again. So I can restart normally having this or restart in recovery to do all the things as before.
Update 2:
After showing up the Chinese init/wipe loop again it restarted but now with red/white OnePlus circle animation. As you read this, it's still rotating...
Are there any thoughts about it... has this phone a hardware damage or what can I do? I appreciate any ideas.
Cheers, cyx
Click to expand...
Click to collapse
Try THIS version of TWRP to format and flash.
tnsmani said:
Try THIS version of TWRP to format and flash.
Click to expand...
Click to collapse
Update 3:
Before following tnsmani's advice to install TWRP I did something that makes things worse. Because I couldn't wait, I sideloaded the new Android 9 zip without any problems in sideload mode. It was installed and the loading circle was coming up. It took a while and finally the phone switched off. Now the phone is booting up to a new rounded edge OnePlus splash screen without any animation and It's not possible to start the old recovery mode anymore. So I can't connect to adb or fastboot to install that TWRP. All what is coming up are different menus without the options I need. I attached two new pictures to show them. But I can't establish a connection to my pc anymore. No devices showing up.
Update 4:
Ok, it seems that fastboot is communicating when I'm in that green/red menu which says start but my command:
fastboot flash recovery twrp-3.2.3-10-oneplus3.img
fails with the output:
target reported max download size of 440401920 bytes
erasing 'recovery'...
FAILED (remote: Partition erase is not allowed)
finished. total time: 0.019s
Update 5:
Ok, I followed this steps:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
to unbrick the device with MSMDownloadTool and Qualcomm drivers, but with no real success so far. But I can start recovery mode again and adb sideload is working as well.
But with anything else, I have no luck. After a new sideload it's keeps anímating the Oneplus dots and I can't install TWRP to do a clean wipe.
All I want to have is a booting up final or beta stock rom working as before, without any specials.
cyx said:
Update 5:
Ok, I followed this steps:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
to unbrick the device with MSMDownloadTool and Qualcomm drivers, but with no real success so far. But I can start recovery mode again and adb sideload is working as well.
But with anything else, I have no luck. After a new sideload it's keeps anímating the Oneplus dots and I can't install TWRP to do a clean wipe.
All I want to have is a booting up final or beta stock rom working as before, without any specials.
Click to expand...
Click to collapse
Is fastboot/bootloader working or not? If it is, simply flash the TWRP first and then proceed with ROM.
If the MSM Download Tool succeeded, you should be able to boot. If not, it means that it did not succeed. Try it a few more times since for some people, repeated attempts are required before the phone boots.
cyx said:
Update 5:
Ok, I followed this steps:
https://forums.oneplus.com/threads/guide-oneplus-3-3t-unbrick.531047/
to unbrick the device with MSMDownloadTool and Qualcomm drivers, but with no real success so far. But I can start recovery mode again and adb sideload is working as well.
But with anything else, I have no luck. After a new sideload it's keeps an
Click to expand...
Click to collapse
What I noticed from your SS is that your bootloader is locked. So no way you can flash or run a custom recovery til the time you actually unlock your bootloader.
I will advise to unlock bootloader first, flash TWRP fixed version (somewhere in LOS thread is the link), "format" /data partition, flash your desired OOS Rom and then try again and see if it works.
@cyx
Boot into the bootloader and on the PC enter this command: fastboot oem unlock.
This should unlock the bootloader. Then flash TWRP, boot back into it and flash ROM etc.