so I've rooted a couple of eris' so far and its all turned out fine but on my brothers (his came with 2.1) i tried and everything worked but in recovery it doesnt respond to anything except the action button to select reboot now. Did i possibly do something wrong? the trackball just doesnt scroll, i guess thats the only problem
dyefalcon1 said:
so I've rooted a couple of eris' so far and its all turned out fine but on my brothers (his came with 2.1) i tried and everything worked but in recovery it doesnt respond to anything except the action button to select reboot now. Did i possibly do something wrong? the trackball just doesnt scroll, i guess thats the only problem
Click to expand...
Click to collapse
I don't think that has much to do with the Amon_RA recovery, although I sort of remember other people reporting a similar phenomena.
If the problem is repeatable, and the trackball works when you are in the regular Eris OS, then I would just fully charge your battery and re-flash the Amon_RA (v1.6.2) recovery image (of course, after making sure of matching md5sum signature).
I had the problem you describe exactly once - but it went away by powering down the phone and rebooting (back into recovery), so I didn't really associate it with the Amon_RA recovery; just assumed it was a momentary problem with the trackball.
Or maybe if the problem persists, maybe try altering how you get into recovery? (e.g. instead of going in directly from power-off state by Vol-Up+End, go into HBOOT first and then Recovery from there?)
bftb0
I've tried toing into recovery both ways and reflashing still no luck...
Same issue
I am wondering if whoever made the recovery could redirect the function of the track ball scrolling up and down to the vol up and vol down keys?
well those keys are supposed to also do the up and down function but nothing responds except the action button
i'm having the same problem.. had this eris rooted for months now.. switch between roms plenty of times but today when i went into recovery.. no scrolling at all.
Even rooted with P000 img again and pushed the recovery img again but still the same troubles.
I guess i'll try with a fully charged battery.
If that doesn't work for you try clockwork recovery. My trackball works in every direction but down, so I couldn't use amon's recovery. In clockwork you use the volume up/down to navigate.
Sent from my Eris using XDA App
I would try all other fixes or options before flashing Clockworks Recovery...it has been known to cause an Eris to brick. Which is why ROM manager is not used by us.
while letting the batt charge..
i went ahead and reformatted the sd card incase that was an issue.. no dice.. still no trackball / vol up / vol down movement.
any adb codes to wipe and install zip from flash ?
still waiting to try full battery (at about 60% )
your trackballs are broken you need to return your devices for refurbs
or wiggle your usb cable around inside of the port while in recovery and playing with the wheel to find out where yours works at
Second option works.. wiggling the usb cable at the point where it connects into the phone while moving the trackball does the trick.... i don't understand why though.
Trackball works fine scrolling up and down in notepad program and usb cable charges phone/connect to computer fine
But it does work so thanks for the suggestion
Sjflowerhorn said:
your trackballs are broken you need to return your devices for refurbs
or wiggle your usb cable around inside of the port while in recovery and playing with the wheel to find out where yours works at
Click to expand...
Click to collapse
Related
I had the nandroid recovery rom working perfectly, then I flashed the Eris based 2.1 rom (did a backup with nandroid prior to it), however, when I went to flash Fresh 2.0b on top of that, I noticed that holding the home key whilst booting did not boot into the recovery rom. Currently the only way for me to get into it is with adb reboot recovery.
This problem still persists after doing a wipe of the Eris based, and a flash of Fresh 2.0b. It's not a huge deal (I only go into it when flashing, and that's when by a computer anyway) but just knowing I can't is somewhat irritating.
Any ideas? Thanks in advance!
this may be obvious, but you're not holding the HOME button after the screen turns on, are you?
you have to hold the home button WHILE the phone is still off and then press the power button, so basically press the home button before the power button.
if that is what you did, try reflashing your recovery image. 1.6.2 is out.
I think I tried it both ways, will try again. I hope it's not something as stupid as that, I'd feel like a tard
I did install the newest to see if that would make a difference.
Edit: Yeah, holding first worked. Could've sworn I did that. Maybe when I had the USB plugged in it didn't like that? Oh well, thanks and now I shall stay quiet for I feel stupid.
I just reset mytouch 4g phone and during restart the recovery screen just come out but I can't move down or up anything on the screen it just stuck..
I just update cm to version 3 of something
please I really need help on this my phone is already S-off
when I plug the phone with USB it response something by HBOOT has changed to HBOOT USB PLUG
I use Stock Rom just update Kernal only
Need more specifics. "3 of something" is too vague.
If you flashed clockwork mod recovery 3 (the text is orange) while using a stock ROM you will have issues. Clockwork 3 is for gingerbread based ROMs only.
If that is so, download CyanogenMOD 7 RC1 and try to flash it. Rebooting may help get recovery working right again. If not, and you are unable to re-flash a ROM, you will need to use fastboot to re-flash a good recovery image.
Marine6680 said:
Need more specifics. "3 of something" is too vague.
If you flashed clockwork mod recovery 3 (the text is orange) while using a stock ROM you will have issues. Clockwork 3 is for gingerbread based ROMs only.
If that is so, download CyanogenMOD 7 RC1 and try to flash it. Rebooting may help get recovery working right again. If not, and you are unable to re-flash a ROM, you will need to use fastboot to re-flash a good recovery image.
Click to expand...
Click to collapse
when I upplug battery, and turn the phone on, it won't boot it just re direct to the Clockwork Mod screen and the screen lock volume up and down can't navigate anything power botton won't work tooo..I try to un plug battery again and turn on again the result is the same...
wibul_10 said:
when I upplug battery, and turn the phone on, it won't boot it just re direct to the Clockwork Mod screen and the screen lock volume up and down can't navigate anything power botton won't work tooo..I try to un plug battery again and turn on again the result is the same...
Click to expand...
Click to collapse
In clockwork you use the trackball to navigate. Volume buttons won't work.
Lakeshow423 said:
In clockwork you use the trackball to navigate. Volume buttons won't work.
Click to expand...
Click to collapse
no response on trackball too. it just stuck on this screen and can't move anywhere....any solution
Your attached image is of the Bootloader, not CWM Recovery.
The Bootloader is controlled by volume up / volume down to move between selections, and the power button is used to select.
jggimi said:
Your attached image is of the Bootloader, not CWM Recovery.
The Bootloader is controlled by volume up / volume down to move between selections, and the power button is used to select.
Click to expand...
Click to collapse
when I turn the phone on everytime it just show this bootloader and no response on all volume up/down and power button...only way to turn off is to unplug battery ....
You might see if the Bootloader can communicate with fastboot on your PC. If so, you will have options for un-bricking from your PC.
See http://forum.xda-developers.com/showthread.php?t=928370 for info on installing adb and fastboot to your PC, and using them.
Fastboot is designed to communicate with the bootloader. As far as I know, however, adb requires a functioning Android or Recovery system.
jggimi said:
You might see if the Bootloader can communicate with fastboot on your PC. If so, you will have options for un-bricking from your PC.
See http://forum.xda-developers.com/showthread.php?t=928370 for info on installing adb and fastboot to your PC, and using them.
Fastboot is designed to communicate with the bootloader. As far as I know, however, adb requires a functioning Android or Recovery system.
Click to expand...
Click to collapse
One more question, after following your advice, I found that I now can restart my phone again but when I shut down the phone and turn it on again it still stuck on bootloader screen all the times...any suggestion would be appreciate...
You can "restart my phone again" -- is it running Android at that point? If so, you can restore your phone to stock, and do a full factory reset, by putting the P15IMG.zip file on the root of your SD card and rebooting. The bootloader (if it is functional) should find it and begin the restore procedure.
Dowload, rename this, and stick it on your SD card, and reboot. If after a successful return to factory defaults, your phone still isn't working, the problem is likely not software.
http://www.filedropper.com/pd15imgglaciertmous1175312radio1228b60140e26030226mrelease155771signed
(Link borrowed from Phateless's .sig)
jggimi said:
You can "restart my phone again" -- is it running Android at that point? If so, you can restore your phone to stock, and do a full factory reset, by putting the P15IMG.zip file on the root of your SD card and rebooting. The bootloader (if it is functional) should find it and begin the restore procedure.
Dowload, rename this, and stick it on your SD card, and reboot. If after a successful return to factory defaults, your phone still isn't working, the problem is likely not software.
http://www.filedropper.com/pd15imgglaciertmous1175312radio1228b60140e26030226mrelease155771signed
(Link borrowed from Phateless's .sig)
Click to expand...
Click to collapse
I can't download it...need new link
anyway thank very much for your help
Okay so I seem to have run into a little problem I was planning on updating cleanrom up to 1.2.5 but was on cwm. I had managed to switch over successfully to twrp 2.2.0. I went ahead and used goo manager to download the updated zip of 2.2.1 and tried flashing it thru twrp. Now I am stuck in google bootloop and cant get into recovery or more importantly bootloader. I have been trying last 30mins to hold power and both volume buttons but it either keeps rebooting back to the google screen or not doing anything at all just have to repress to to turn it off but it will turn back on automatically. I tried hooking it up to my usb and labtop but it looks like it wont even recognize it. I just fully charged it so I am good for now just a little worried cant get out of this mess.
I ran into a problem like that with clockwork recovery it kept on rebooting in recovery but I could still go into download mode I was at work away from my computer so I had no choice but to keep trying that three button magic until it finally restored a backup I had on my external card.just keep on trying to pull the battery then try to go into recovery. You might 've gotten a bad download
Sent from my SGH-T999 using xda premium
problem is I cant get into recovery. or the green screen to get to bootloader. It just completely stuck in a bootloop on the google screen mocking me... I am really contemplating opening it up and taking out battery but is that a good idea? Or is there anything else I can do?
so I pulled off the back cover but really dont want o disconnect the battery might mess something up but I cannot get the device to shut off.
disconnecting the battery does nothing it shuts it off and keeps it off but when I connect it to the charger the battery symbol pops up for a second and then goes completely blank. I went ahead and tried again to boot into bootloader pressing power vol up + down and all combinations of power vol -, power vol +
power turbo press vol +/- but no luck still in google screen.
If you're in a bootloop you need to connect your Nexus 7 to a computer. Then you will be able to access recovery via the Power button and volume buttons.
is it going to make a difference that everytime i try to reboot it just the black google screen? I have tried it connected to the wall charger and connected usb to the labtop but nothing.
clago87 said:
is it going to make a difference that everytime i try to reboot it just the black google screen? I have tried it connected to the wall charger and connected usb to the labtop but nothing.
Click to expand...
Click to collapse
It's supposed to do that when you're trying to go to recovery from bootloader without the USB cable plugged into a computer, may need to have the drivers installed on said computer. It's an issue with the nexus 7 bootloader and every one of them does it. What your experiencing is perfectly normal if you tried to go to recovery from bootloader with the bolume buttons and then got the google screen bootloop.
If it doesn't work when you plug it in and try, then try unplugging it, manually rebooting with it plugged in first, or vice versa
Update: I can get on Team Viewer and remotely reboot you into recovery through the PC if you want, or at least give it my best shot.
ok so i disconnected battery and have the device off. I should then try connecting it to the pc and try booting up holding down all buttons?
clago87 said:
ok so i disconnected battery and have the device off. I should then try connecting it to the pc and try booting up holding down all buttons?
Click to expand...
Click to collapse
Have you installed the right drivers on the computer you're using, for ADB and the device drivers, when you unlocked and rooted?
Answer to your question is yes try that. But I wouldn't be disconnecting and reconnecting it, I can't recommend that and then learn tomorrow that static zapped something important.
yea I am getting nothing by connecting to pc. I have all the drivers adb and fastboot installed when I rooted and unlocked couple weeks back but it looks like device is not being recognized or read at all by the pc.
connecting to the pc holding the volume + button gets it recognized for a second and tries to install a driver apx but unsuccessfully.
I am not making any progress whatsoever kinda sucks starting the weekend like this. I have gone thru some bad stuff with my atrix but nothing like this were I cant even access my bootloader boot into recovery or even fastboot. Should I try and get it to just stay off and see if overnight it works its own magic? Hate going to sleep witht his on my mind but I think with a clear mind in the morning something good will happen.
I can get it to stay off by holding both vol+ and vol- but trying to turn it off with just the power button just keeps it turning back on/off...
so I slepted on it thru the night let the tablet rest but went back this morning and I still cant get into bootloader or recovery. Is there anything I can do?
Has anyone else had this problem where they cant boot into recovery or bootloader? It's like the power button and vol keys are unresponsive even though they still work to turn on the device.
are you sure that you flashed the right recovery? but you should still be able to get the bootloader. are you pressing power + volume down(volume down, not both volume buttons. i noticed you wrote both volume buttons) to get into the bootloader?
I think I chose the right recovery the first version downloaded thru goo manager but it was the 2.2.0 version. I had the option on the of downloading the 2.2.1 zip or the .img but i downloaded the .img to just to flash with the current version of twrp that was working. There have been times were I have not been able to get into recovery on my atrix or htc but I've always been able to get into the bootloader this is the first time I've been locked out of my device kind of got me scared its not even a month old. So you say to get into bootloader you dont have to hold down both volume buttons? I will try again to power back up using the volume down and power button at same time... Wish me luck
clago87 said:
I think I chose the right recovery the first version downloaded thru goo manager but it was the 2.2.0 version. I had the option on the of downloading the 2.2.1 zip or the .img but i downloaded the .img to just to flash with the current version of twrp that was working. There have been times were I have not been able to get into recovery on my atrix or htc but I've always been able to get into the bootloader this is the first time I've been locked out of my device kind of got me scared its not even a month old. So you say to get into bootloader you dont have to hold down both volume buttons? I will try again to power back up using the volume down and power button at same time... Wish me luck
Click to expand...
Click to collapse
good luck!
yea, only power button and the volume down button.
quick question before I connect the battery does it make a difference whether or not I have it plugged in charging or connected to the PC while trying to boot into bootloader?
Does anyone know if a mouse using an otg cable will work in multiboot TWRP recovery mode (also the multirom screen, but thats not as important right now) or if the screen rotates. Looking at the OP i noticed a "tablet look". Is this on the nexus 7? I cracked my screen (digitizer cracked, LCD is fine) an am looking for a way to flash new roms but not dont want to restart my tab because im afraid i wont be able to get out of recovery mode if i boot into it.besides the thirty second power button hold (bottom half of screen is unresponsive and i cant access the onscreen buttons to reboot from recovery or to go to the advance menu which are located at the bottom). im running m-kernel 32a with multiboot. I cant even remember if that recovery supports hardware button presses.
chaostrodamis said:
Does anyone know if a mouse using an otg cable will work in multiboot TWRP recovery mode (also the multirom screen, but thats not as important right now) or if the screen rotates. I cracked my screen (digitizer cracked, LCD is fine) an am looking for a way to flash new roms but not dont want to restart my tab because im afraid i wont be able to get out of recovery mode (bottom half of screen is unresponsive). im running m-kernel 32a with multiboot. I cant even remember if that recovery supports hardware button presses.
Click to expand...
Click to collapse
TWRP 2.2.2.0 now with USB OTG
Click to expand...
Click to collapse
A quick 'google' has answered the question. Anyway, if you cannot use the mouse in recovery for whatever reason (and haven't flashed or done anything, and its unlikely you would since the mouse isn't working) then you can just open up the back of the nexus 7 and take out the battery? Or try holding down power and vol down to get to fastboot (and use volume/power) to reboot back to normal.
Good luck
Mmmm. That is a bit of a dilemma.
I was going to suggest - IF your bootloader is unlocked, you would (in principle) have the option to "soft-boot" different recoveries (even a plain-ole normal OS boot image for that matter) via the command line (or perhaps with a toolkit - I have no knowledge of them).
fastboot boot boot-or-recovery-image-file.img
which would allow you to use just the volume rocker and power button on the alternate recovery. Obviously, you need to have fastboot communications set up (drivers for your PC) as a pre-requisite,
(Nothing about that suggests you need to flash a replacement recovery to the device - soft boot what you need for a single session at a time.). That gives you the option to play around with mouse experiments at your leisure.
In order to do that, though you certainly would need to quit your current boot. Two finger salute for that? Or perhaps doing the reboot through ADB failing the former?
Just an idea anyway. Since you are using multiboot, I might not be aware of kinks between a different TWRP version and getting multiboot kernels to come up - but you said in the OP that you were interested in replacing ROMs, not saving the one that that is there....
cheers
Fallon9111 said:
A quick 'google' has answered the question. Anyway, if you cannot use the mouse in recovery for whatever reason (and haven't flashed or done anything, and its unlikely you would since the mouse isn't working) then you can just open up the back of the nexus 7 and take out the battery? Or try holding down power and vol down to get to fastboot (and use volume/power) to reboot back to normal.
Good luck
Click to expand...
Click to collapse
I think the catalog is talking about stick mounts and USB storage. I couldnt find anything on using a mouse in recovery. even youtubed it, only one person shows that a keyboard works on CWM recovery. nothing about TWRP.
Good evening everyone, i'm having a serious issue with my samsung A5. It was rooted, with custom recovery and custorm rom (Android 6.1 i think).
2 Days ago, a chewingum got stuck on my screen. I tried to remove it with nail paint remover, it did the trick but then my home button stopped working: the button itself can be pressed normally, but it won't work. I also experienced randomly long home button press actions, so i decided to turn them off. I thought that few drops of liquid may actually have gone beneath the home button. Few hours later, i experienced more issues: volume going up without anyone pressing the button (and the buttons are not stuck at all, and that side never got close to liquids), power button not doing his job etc. I tried to do a soft reset by recovery (cleaning cache and dalvik) but i ended up aslo factory resetting it for a distraction. Reconfigured the device, everything was back to normal (except the home button) but then i also experienced a couple of random volume up and crashes upon making phonecalls. SO i decided to reflash the entire rom, downloaded it + gapps, put into the decide, rebooted in recovery. Wipe cache, dalvik and also system i think, then i tried to intall the zip files but they were not there (probably i should have avoided wiping system, i get confused sometimes). I turned the device off and on, and now i'm stuck on bootloop (regular mode), can reboot it but it seems i can't go in either recovery or donwload mode (so no odin flash). Device is not recognized by the Pc. I keep rebooting it with power + home + volume down and as soon as i see the screen turn black, i try to press again volume up + home to enter recovery, but it goes straight to bootloop.
Any idea on how getting out of this situation? Thank you in advance
Dharmost said:
Good evening everyone, i'm having a serious issue with my samsung A5. It was rooted, with custom recovery and custorm rom (Android 6.1 i think).
2 Days ago, a chewingum got stuck on my screen. I tried to remove it with nail paint remover, it did the trick but then my home button stopped working: the button itself can be pressed normally, but it won't work. I also experienced randomly long home button press actions, so i decided to turn them off. I thought that few drops of liquid may actually have gone beneath the home button. Few hours later, i experienced more issues: volume going up without anyone pressing the button (and the buttons are not stuck at all, and that side never got close to liquids), power button not doing his job etc. I tried to do a soft reset by recovery (cleaning cache and dalvik) but i ended up aslo factory resetting it for a distraction. Reconfigured the device, everything was back to normal (except the home button) but then i also experienced a couple of random volume up and crashes upon making phonecalls. SO i decided to reflash the entire rom, downloaded it + gapps, put into the decide, rebooted in recovery. Wipe cache, dalvik and also system i think, then i tried to intall the zip files but they were not there (probably i should have avoided wiping system, i get confused sometimes). I turned the device off and on, and now i'm stuck on bootloop (regular mode), can reboot it but it seems i can't go in either recovery or donwload mode (so no odin flash). Device is not recognized by the Pc. I keep rebooting it with power + home + volume down and as soon as i see the screen turn black, i try to press again volume up + home to enter recovery, but it goes straight to bootloop.
Any idea on how getting out of this situation? Thank you in advance
Click to expand...
Click to collapse
Sadly, no software can fix broken hardware, it's probably best, as you'll now know, not to pour chemical liquids onto electrical devices, and just what kind of chewing gum exists that requires such extreme cleaning measures from a flat, non-porous surface I'll never know.
That said, as for rebooting, a force-restart on your device *doesn't* require you to hold Home+Volume down+Power, that should only reboot you to bootloader/download mode.
Try again only holding Power+Volume Down. THEN, when your screen goes fully black, immediately switch to Power+Volume up+Home.
You should then boot into recovery mode without any loop.
Good luck!
D4ND310 said:
Sadly, no software can fix broken hardware, it's probably best, as you'll now know, not to pour chemical liquids onto electrical devices, and just what kind of chewing gum exists that requires such extreme cleaning measures from a flat, non-porous surface I'll never know.
That said, as for rebooting, a force-restart on your device *doesn't* require you to hold Home+Volume down+Power, that should only reboot you to bootloader/download mode.
Try again only holding Power+Volume Down. THEN, when your screen goes fully black, immediately switch to Power+Volume up+Home.
You should then boot into recovery mode without any loop.
Good luck!
Click to expand...
Click to collapse
I didn't dip the smartphone into a cup of liquid, i just took a piece of cotton, poured a bit of nail pain remover (don't know the exact name in english, sorry) on it and then scratched the part where the chewing gum was on (on the soft touch back key, which works 100% fine).
I am trying using the method you described, but it seems i can't go into recovery. Maybe i'm not quick enough! will keep trying. If you have any other suggestions i will be glad to hear that!
You could try to make a USB jig, or buy one off of eBay. They're really cheap. Its basicly just a resistens that force the phone to download mode. It have worked fine for all my Sammy's including A310 so it probably works for A (15) series as well.
Just put it in USB connector and press power for a few secs and you should be in download mode.
Just an idea if everything else fails
Sent from my Honor 5X using Tapatalk
go to samsung
A hardware problem could NEVER be fixed by software ways... Unfortunatelly...
It seems that liquid made some changes on your PCB (maybe dissolved some isolators inside??)...
Anyway, go to service or replace it!
Hello everyone, i've updates about my problem and i would be glad if you could kindly point me in the right direction.
I purchased an USB Jig as suggested by one of you guys, i forced the device into dowload mode and installed a fresh stock firmware + custom recovery. When i try to boot i get a bootloop on samsung logo, and can't go into recovery probably because of the broken home button. I would like to enter recovery by using ADB command, i used to do it in the early days of Android but i'm a bit rusty and all the guides tell the procedure from an already functioning device. Since i can start it properly, is there a way to reboot it in recovery via ADB?
Thank you in advance
Dharmost said:
Hello everyone, i've updates about my problem and i would be glad if you could kindly point me in the right direction.
I purchased an USB Jig as suggested by one of you guys, i forced the device into dowload mode and installed a fresh stock firmware + custom recovery. When i try to boot i get a bootloop on samsung logo, and can't go into recovery probably because of the broken home button. I would like to enter recovery by using ADB command, i used to do it in the early days of Android but i'm a bit rusty and all the guides tell the procedure from an already functioning device. Since i can start it properly, is there a way to reboot it in recovery via ADB?
Thank you in advance
Click to expand...
Click to collapse
if you can access Download mode try this. hold volume down+home+power button. once the screen is black simply turn your finger to volume up while still holding the power and home button then release when SAMSUNG appears.
Sent from my SM-A500F using xda premium
babyyeobo14 said:
if you can access Download mode try this. hold volume down+home+power button. once the screen is black simply turn your finger to volume up while still holding the power and home button then release when SAMSUNG appears.
Sent from my SM-A500F using xda premium
Click to expand...
Click to collapse
Thanks for the suggestion, but still couldn't get into recovery. I think the home button is really broken, therefore i need to access recovery in another way.
Cause i flashed the stock samsung firmware twice with odin and i can't still start the phone properly, every guide says that a wipe of cache and dalvik solves the situation. But i need to get into recovery for that.
I can't go into recovery with normal procedure probably because the home button is not working, and all the guides about adb commands say that you need to plug in your phone when it has fully started. So i either need a way to force the device into recovery with my computer, or a firmware that once flashed doesn't give me bootloop