Hi,
Today I helped a friend flash a custom rom on a galaxy gio and I opened cmw on my phone to help him go to the right menu's in cmw.
I think I changed the ext4 partition to 0mb (don't realy know how :s) and now when I boot android Instead of the bootscreen with the red m I get some white text with some different options (like boot in adb (about 10 options)) it also tells me I can move change option with volume down and accept with volume up, but these don't do anything :s.
After I wait for a while android just starts booting like normal and everything seems fine, but when android has booted it seems like the touchscreen move up for like a centimeter (if I want to press a button I need to touch the screen under the button) and my soft keys don't work anymore (but I think this is because of the moved touchscreen)
What did I do and how can I make it normal again? I'm running the latest GB Mrom.
Edit:this is the screen I get when there normally is a red circle with the white M in:
Uploaded with ImageShack.us
Thnx if anyone can help me!
I've been trying somethings and if I don't have my usb cable plugged in I can choose some options on the menu, it seems now that I somehow removed my clockwordmod recovery and went back to old recovery? Is this even possible?
Should I just reflash cmw with fastboot again?
Plz help me
I would hold of on flashing another recovery until someone more knowledgeable than I comes along. There might be a chance where you can do permanent damage. Seems like it could have simply deleted their boot logo, and now instead of those options being normally hidden, are being shown. (like when you boot while holding volume down). What happens if you try booting with volume button held down?
Edit: If all else work as it should, just leave it. Makes it look like verbose mode. Forget Motorola and their stupid 'm'. =P
Sent from my MB860 using xda app-developers app
thesummoner101 said:
I would hold of on flashing another recovery until someone more knowledgeable than I comes along. There might be a chance where you can do permanent damage. Seems like it could have simply deleted their boot logo, and now instead of those options being normally hidden, are being shown. (like when you boot while holding volume down). What happens if you try booting with volume button held down?
Edit: If all else work as it should, just leave it. Makes it look like verbose mode. Forget Motorola and their stupid 'm'. =P
Sent from my MB860 using xda app-developers app
Click to expand...
Click to collapse
If I hold volume down + power while booting I get the same thing, and everything works normaly, BUT my touchscreen is messed up, the every touch gets detected to high (if I want to hit app drawer I need to push between the home and back soft button) and the soft buttons don't work.
Oh right, you did mention that, my bad. Well, I'd say hold off for someone that might know what happened as I've never read about or experienced something like this. Maybe try posting in the main XDA Q&A section not specific to Atrix as someone might have had a similar issue with another device (maybe even a Moro) Sorry can't be of much help. Good luck.
Sent from my MB860 using xda app-developers app
touchscreen problems are usually related to the pds partition. Did you by any chance make a backup before these problems started?
I don't know if the bootscreen is related to the PDS partition but it might be that this partition is corrupted.
jorno88 said:
touchscreen problems are usually related to the pds partition. Did you by any chance make a backup before these problems started?
I don't know if the bootscreen is related to the PDS partition but it might be that this partition is corrupted.
Click to expand...
Click to collapse
but could that also explain the weird boot message with the options? (or is it also called animantion, because the Mrom annimations works normal (the blue android guy))
I had mistakenly done something that resulted in your exact problems once. What I did to fix. First you'll need to fastboot a recovery again. Next you'll have to do the pds partition fix. Then lastly flash the proper boot logo back to get the m screen. The first step is dependent on you being able to get into fastboot so hopefully you can.
pre4speed said:
I had mistakenly done something that resulted in your exact problems once. What I did to fix. First you'll need to fastboot a recovery again. Next you'll have to do the pds partition fix. Then lastly flash the proper boot logo back to get the m screen. The first step is dependent on you being able to get into fastboot so hopefully you can.
Click to expand...
Click to collapse
thnx for the reply!
you mean the Fix in this thread?
http://forum.xda-developers.com/showthread.php?t=1131649
And I'm guessing i'll need the one for gingerbread?
M_K_ said:
thnx for the reply!
you mean the Fix in this thread?
http://forum.xda-developers.com/showthread.php?t=1131649
And I'm guessing i'll need the one for gingerbread?
Click to expand...
Click to collapse
Yes that is the right file and yes for gb.
Ok, I just reflashed the recovery with fastboot and then I flashed the PDS partition fix and the touchscreen works perfectly again. Only the red M is still gone.
Any Idea how to get it back?
And Thank You so much!
Now I can use my phone again
M_K_ said:
Ok, I just reflashed the recovery with fastboot and then I flashed the PDS partition fix and the touchscreen works perfectly again. Only the red M is still gone.
Any Idea how to get it back?
And Thank You so much!
Now I can use my phone again
Click to expand...
Click to collapse
Somewhere in the forum is the boot logo. I believe its in the apps section. Search for stock boot logo. Glad I was able to help.
Actually here you go. http://forum.xda-developers.com/showthread.php?t=1423763
Related
Hi guys, I am feeling really nervous about this... So, the problem is, that I've just rooted my HTC GSM Hero and installed 2.2 ROM (http://forum.xda-developers.com/showthread.php?t=767886). Then I downloaded this app http://forum.xda-developers.com/showthread.php?t=892297. There I chose wrong icon (I didn't notice the icon was for FroydVillain) and rebooted device... Now I can't boot device into normal mode (it shows hero for a while, then turns into black screen, and nothing more happens) or recovery mode (it stucks when it shows HERO). I tried this: http://forum.xda-developers.com/showpost.php?p=4467471&postcount=13 but it didn't work. I'm a complete beginner. Any ideas? Is my device really bricked? THANKS.
Boot into recovery, reflash the room. I dont know why would you anything to spl...
Sent from my HTC Hero using XDA App
brat.haneq said:
Boot into recovery, reflash the room. I dont know why would you anything to spl...
Sent from my HTC Hero using XDA App
Click to expand...
Click to collapse
But I can't boot into recovery... That's the problem... It stucks when it shows HERO
matthew31 said:
Hi guys, I am feeling really nervous about this... So, the problem is, that I've just rooted my HTC GSM Hero and installed 2.2 ROM (http://forum.xda-developers.com/showthread.php?t=767886). Then I downloaded this app http://forum.xda-developers.com/showthread.php?t=892297. There I chose wrong icon (I didn't notice the icon was for FroydVillain) and rebooted device... Now I can't boot device into normal mode (it shows hero for a while, then turns into black screen, and nothing more happens) or recovery mode (it stucks when it shows HERO). I tried this: http://forum.xda-developers.com/showpost.php?p=4467471&postcount=13 but it didn't work. I'm a complete beginner. Any ideas? Is my device really bricked? THANKS.
Click to expand...
Click to collapse
Stay calm... it's not necessarily bricked yet
First thing i would like you to do is charge your phone to max!
Try and turn on the phone and hold to "On" key and "Home" key together for 60 seconds. If this doesn't boot you to recovery, try again one more time! It's happened to me that i didn't realise the button wasn't pressed all the way down.
If that doesn't work then let it boot as normal and even though it goes to the black screen don't panic.
Do you have any of the android tools installed?
http://forum.xda-developers.com/showthread.php?t=502010
See there for help on how to get adb up and running and then come back here.
Another thing i'm curious about while we're here... when you boot the device as normal.. connect it to power, the orange (or green) led at the top should be off for a few seconds while the hero boots up... when it goes to this black screen that you see.. does the light come on?
Bantu85 said:
Stay calm... it's not necessarily bricked yet
First thing i would like you to do is charge your phone to max!
Try and turn on the phone and hold to "On" key and "Home" key together for 60 seconds. If this doesn't boot you to recovery, try again one more time! It's happened to me that i didn't realise the button wasn't pressed all the way down.
If that doesn't work then let it boot as normal and even though it goes to the black screen don't panic.
Do you have any of the android tools installed?
http://forum.xda-developers.com/showthread.php?t=502010
See there for help on how to get adb up and running and then come back here.
Click to expand...
Click to collapse
OK, so, SDK is being installed now, and the phone is charging. What should I do next?
Bantu85 said:
Another thing i'm curious about while we're here... when you boot the device as normal.. connect it to power, the orange (or green) led at the top should be off for a few seconds while the hero boots up... when it goes to this black screen that you see.. does the light come on?
Click to expand...
Click to collapse
When my phone is off, the led is red. When I see that black screen, it is off... Is that bad??
Not necessarily.. it could just mean that it's not finishing it's boot up... let it charge for a while.
Your phone is most likely fine. You just confused it so it can't start up normally. We'll get you back in recovery mode and then you can reinstall your 2.2 rom.
Bantu85 said:
Not necessarily.. it could just mean that it's not finishing it's boot up... let it charge for a while.
Your phone is most likely fine. You just confused it so it can't start up normally. We'll get you back in recovery mode and then you can reinstall your 2.2 rom.
Click to expand...
Click to collapse
So I'll charge the phone the whole night, and I'll try booting it in recovery mode tomorrow morning - I will post the result here Thanks
yes.. if it boots into recovery mode (which it should!) wipe everything and reflash... that should sort you out.
Bantu85 said:
yes.. if it boots into recovery mode (which it should!) wipe everything and reflash... that should sort you out.
Click to expand...
Click to collapse
No, it unfortunately didn't boot.. I left it for an hour but it still didn't help.. I'll retry booting it, but anyway, any more ideas? Anyways, thanks.
Hi there
I'm assuming, that You know how to get into recovery, as You flashed a couple of things. Perhaps Your home key is broken
Question: do You have adb set up on Your computer? if yes - does it recognize Your phone ?
There is always option to run RRU...have You tried that ?
with regards
brat.haneq
have you tried booting holding VOLUME DOWN?
brat.haneq said:
Hi there
I'm assuming, that You know how to get into recovery, as You flashed a couple of things. Perhaps Your home key is broken
Question: do You have adb set up on Your computer? if yes - does it recognize Your phone ?
There is always option to run RRU...have You tried that ?
with regards
brat.haneq
Click to expand...
Click to collapse
Yes, I have ADB, but when I type adb devices, it only writes: "List of devices attached" (does that mean that it recognize my phone?)
I'm not sure I know what RRU is
bonesy said:
have you tried booting holding VOLUME DOWN?
Click to expand...
Click to collapse
Yes, it finds HEROIMG,zip, then loads it, then checks it, and adter that nothing happens - the phone still doesn't boot.
ok, volume down key response is good
ADB apears not to discover Your phone, probably drivers problem ;/
Look for RRU file it's used for factory reseting entire phone.
You can download it from HTC.com site.
With regards
brat.haneq
EDIT: go to htc.com site. look for downlaoding software for Your phone. You will have to provide Your imei. and You will receive .exe file - that You will have to run on Your PC. You can also look for it on this forum, they should be around here somewhere (or perhaps shipped roms.com)
brat.haneq said:
ok, volume down key response is good
ADB apears not to discover Your phone, probably drivers problem ;/
Look for RRU file it's used for factory reseting entire phone.
You can download it from HTC.com site.
With regards
brat.haneq
EDIT: go to htc.com site. look for downlaoding software for Your phone. You will have to provide Your imei. and You will receive .exe file - that You will have to run on Your PC. You can also look for it on this forum, they should be around here somewhere (or perhaps shipped roms.com)
Click to expand...
Click to collapse
When I enter the S/N in the htc.com site, it shows: Sorry, this software download is not suitable for your device. I can download it from xda forum, but will this work?
Maybe there's some way to flash my recovery img via hboot (POWER + VOLUME DOWN)?
Try downloading usbdeview HERE plug the phone in,turn it on,leave it for 10-15 seconds for windows to recognize it...load usbdeview and uninstall and delete anything with android,htc,mass storage or adb in it thats showing as connected (on the right hand side) unplug phone......then download and install HTC Sync HERE let it install,then reboot (to be safe) plug the phone in and let its do its business,DONT let windows search and direct it to program files/htc sync/drivers (or similar) you should then have adb! If you dont it could be a problem with your misc.img i had this with my magic and fixed it with a post on this forum but will post it up if the first bit doesnt work
Any troubles gtalk me [email protected]
matthew31 said:
Maybe there's some way to flash my recovery img via hboot (POWER + VOLUME DOWN)?
Click to expand...
Click to collapse
you have to do that with fastboot
I solved this problem! I just put the correct RUU in my sdcard and named it HEROIMG.zip and then turned on hboot - it flashed the RUU and now I got my phone alive! thanks for your help guys
Sent from my Hero using XDA App
I'm just going to get straight to the problem here: my Atrix won't boot because something went wrong with a ROM I was trying to install. I was using the package from here Project kitchen sink, and selected aokp. I have Clockwork Recovery 5.8.1.8, so it boots into recovery.
The problem is that my volume rocker is broken, I *think* because of pds, so I cannot navigate the menu. I have tried using RSDLite and Fastboot, hoping that I could work through the recovery boot menu, but it's useless. And since my volume keys refuse to work, I can't set the phone to boot into RSD mode. I'm stuck in an endless loop of not-able-to-do-jack-****, and I don't think I'll be able to send it in to Moto for a replacement.
I don't know if the failure is due to a hardware issue (my Atrix was shipped to me from my family, since I live in Puerto Rico), the CM7 ROM I had before, or a recent crash (the battery was also giving me problems, and lately crashed the phone several times, not turning on unless I pulled it.)
Sparr159 said:
I'm just going to get straight to the problem here: my Atrix won't boot because something went wrong with a ROM I was trying to install. I was using the package from here Project kitchen sink, and selected aokp. I have Clockwork Recovery 5.8.1.8, so it boots into recovery.
The problem is that my volume rocker is broken, I *think* because of pds, so I cannot navigate the menu. I have tried using RSDLite and Fastboot, hoping that I could work through the recovery boot menu, but it's useless. And since my volume keys refuse to work, I can't set the phone to boot into RSD mode. I'm stuck in an endless loop of not-able-to-do-jack-****, and I don't think I'll be able to send it in to Moto for a replacement.
I don't know if the failure is due to a hardware issue (my Atrix was shipped to me from my family, since I live in Puerto Rico), the CM7 ROM I had before, or a recent crash (the battery was also giving me problems, and lately crashed the phone several times, not turning on unless I pulled it.)
Click to expand...
Click to collapse
PDS does not affect volume buttons.
And what happens when you boot? Boot loop is not very specific...
I read a post on here that said it did...
And what happens is that it boots once, stays on the Moto logo, then blacks out, boots again and goes into recovery. Since I have no way to do anything, I press the power button and it goes again.
What I need is either
1) A way to work with RSD through the recovery, or
2) A way to work with ADB through recovery, or
3) Someone to just tell it to me straight: I'm f*cked and I need to send it in to Moto (Which I doubt they would take it.)
Sparr159 said:
I read a post on here that said it did...
And what happens is that it boots once, stays on the Moto logo, then blacks out, boots again and goes into recovery. Since I have no way to do anything, I press the power button and it goes again.
What I need is either
1) A way to work with RSD through the recovery, or
2) A way to work with ADB through recovery, or
3) Someone to just tell it to me straight: I'm f*cked and I need to send it in to Moto (Which I doubt they would take it.)
Click to expand...
Click to collapse
I would tell you to flash touch recovery however I don't think you can and how it would help you recover from this situation.
Sent from my MB860 running Jokersax's CM9
The weird thing is that I had flashed touch recovery before I started with kitchen sink, and it fixed the touch problems I was having there, but now the touch doesn't work. I downloaded it from the clockwork website, because I don't want to pay for something that is available for free, and I flashed it in fastboot.
Now I have Clockwork Recovery 1.8, which should be touch, no?
Sparr159 said:
The weird thing is that I had flashed touch recovery before I started with kitchen sink, and it fixed the touch problems I was having there, but now the touch doesn't work. I downloaded it from the clockwork website, because I don't want to pay for something that is available for free, and I flashed it in fastboot.
Now I have Clockwork Recovery 1.8, which should be touch, no?
Click to expand...
Click to collapse
You mean 5.8.1.8? If so then yes. And if touch is not working in touch recovery then it does sorta confirm you need the PDS fix...
We are finally getting somewhere: yes, it is 5.8.1.8, touch doesn't work. I know I need the PDS fix, and I applied it. Twice. I patched in fastboot before I started with kitchen sink, and I thought it had worked, since the Aroma installer was touch-enabled after I patched. But now the recovery menu is not working. I tried pressing the search key, like with the Aroma installer, but I knew it wouldn't have any effect.
Sparr159 said:
We are finally getting somewhere: yes, it is 5.8.1.8, touch doesn't work. I know I need the PDS fix, and I applied it. Twice. I patched in fastboot before I started with kitchen sink, and I thought it had worked, since the Aroma installer was touch-enabled after I patched. But now the recovery menu is not working. I tried pressing the search key, like with the Aroma installer, but I knew it wouldn't have any effect.
Click to expand...
Click to collapse
Can you point me to the thread where it says volumer rocker is linked to pds because i searched and cant find it.
How are you booting...i mean with what key combination? Im assuming your booting normally(only power button) and end up going into recovery. Try booting with power button and volume down.
Sorry I'm not quoting anybody, first off.
Second, I can't find the link. I spent around an hour searching and found it through duckduckgo, but now I can't remember the search term I used. If I find it, I'll post it.
And yes, I'm booting only with power button, because the volume down key isn't working. That is where the pds problem comes in: I can't use the volume down or up key because the keys don't work.
My friend told me that I could use adb to manually boot it into fastboot mode. That works fine, but I don't know how to flash anything other than the recovery/pds partitions. I know fastboot has a "flashall" command, but I don't know how to use that or if it is even going to help. **Essentially** I can boot into fastboot mode, but I want to know if it is even possible to just flash a rom through that. Messy, of course, but if I can just get even a basic ROM working, I can go on from there.
I think you have 2 options:
1. if you can get to fastboot you can reflash everything using uncle cemka's method: http://forum.xda-developers.com/showthread.php?t=1501532
you basically take an .sbf unpack it and flash each part separately.
2. buy a atrix audio jack/camera flex cable from ebay and install it yourself, be especially careful when installing because the very small flex/ribbon that goes to your volume buttons stress fractures very easily if bent very much when installing, hence your volume buttons stop working.
I'm using cemka's method now. I'm waiting for the stock ROM to download, the one from his post. When I finish the whole process, I'll let you guys know how it worked out.
UPDATE: Thank you to whoever referred me to uncle cemka's method, I was able to use it to flash stock ROM. I have functionality back, can boot, and won't waste around $90 on a paperweight.
However, the first problem is still there: The volume keys still don't work. I still need to fix those before everything is %100 percent, so this issue is still open... Sorry guys
Hello,
about 2 hours ago I decided that I would unlock my device (before that I read maximum informations that I could). Unlocking went fine and I also installed TWRP 2.1.3 (through ViperMod). So far so good.
Then I made backup in TWRP in case something goes wrong. I was going to try AOKP v40 so I downloaded it via goo manager and then I flashed it in TWRP Install option (and also installed gapps) and wiped cache. Device rebooted and I was stuck at AOKP boot animation for about 15 minutes when I decided to recover back. So I rebooted, restored and rebooted.
Now I'm stuck at first boot logo (eee pad). When I try to do VolDown+Power to get into recovery it doesn't ask for VolUp, but goes straight to selection of Wipe or USB. When I select fastboot or wait 10 secs device frozes. (I haven't tried wipe, just in case it would be needed to unbrick).
I read thread about unbricking (http://forum.xda-developers.com/showthread.php?t=1514088) and to me it seems like option 3, but I don't see recovery option.
In device manager I have 'ASUS Fastboot Interface'.
Here's video how it looks like: http://www.youtube.com/watch?v=7BGd1PIVbn8
Please please could anyone help me?
Btw: Is there any chance to shut down? Holding power button just resets, so does pinhole... :/
qery said:
Hello,
about 2 hours ago I decided that I would unlock my device (before that I read maximum informations that I could). Unlocking went fine and I also installed TWRP 2.1.3 (through ViperMod). So far so good.
Then I made backup in TWRP in case something goes wrong. I was going to try AOKP v40 so I downloaded it via goo manager and then I flashed it in TWRP Install option (and also installed gapps) and wiped cache. Device rebooted and I was stuck at AOKP boot animation for about 15 minutes when I decided to recover back. So I rebooted, restored and rebooted.
Now I'm stuck at first boot logo (eee pad). When I try to do VolUp+Power to get into recovery it doesn't ask for VolUp, but goes straight to selection of Wipe or USB. When I select fastboot or wait 10 secs device frozes. (I haven't tried wipe, just in case it would be needed to unbrick).
I read thread about unbricking (http://forum.xda-developers.com/showthread.php?t=1514088) and to me it seems like option 3, but I don't see recovery option.
In device manager I have 'ASUS Fastboot Interface'.
Here's video how it looks like: http://www.youtube.com/watch?v=7BGd1PIVbn8
Please please could anyone help me?
Btw: Is there any chance to shut down? Holding power button just resets, so does pinhole... :/
Click to expand...
Click to collapse
Shouldn't it be volume and power down to get to the option to press volume up for recovery?
Are you familiar with fastboot flashing recoveries? Either way that will be helpful info for us to have.
Most important thing, this is no big deal at all, it's really a minor issue. Don't let yourself get stressed out over it, the community will make sure you're good to go.
CharliesTheMan said:
Shouldn't it be volume and power down to get to the option to press volume up for recovery?
Click to expand...
Click to collapse
Yes sure my bad, it was typo (I was kinda sleepy and tired when I was writing)
CharliesTheMan said:
Are you familiar with fastboot flashing recoveries? Either way that will be helpful info for us to have.
Click to expand...
Click to collapse
Nope, this is my first time flashing.
You say you dont see the VOL_UP message. From the video it looks like it is there. You just did not press it within 5 seconds.
Once it comes up, let go of the buttons ;p
leppie said:
You say you dont see the VOL_UP message. From the video it looks like it is there. You just did not press it within 5 seconds.
Once it comes up, let go of the buttons ;p
Click to expand...
Click to collapse
nope it's not there. I was holding voldown from the start and as soon as it should say 'press volup for recovery' (time 0:04) it jumps (skips 5 seconds of waiting) directly to wipe/fastboot options (wipe is one that is selected on video)
Ok so I managed to fix my problem thanks to hanzo001's thread (http://forum.xda-developers.com/showthread.php?t=1662158). Someone should add this instructions to the [HOW-TO] Unbrick your Transformer Prime (or not) thread.
qery said:
Ok so I managed to fix my problem thanks to hanzo001's thread (http://forum.xda-developers.com/showthread.php?t=1662158). Someone should add this instructions to the [HOW-TO] Unbrick your Transformer Prime (or not) thread.
Click to expand...
Click to collapse
glad it's fixed, im sure hanzo001 will appriciate a simple thanks on his thread too..and let others know it worked for you
Hi all,
My Transformer Prime will not boot past the initial Asus screen. It's remains stuck on this screen but when I hold power down, the device reboots. I am not able to get into recovery using power and vol down, then vol up. I cant turn the device off, it reboots every time. When I try to hold vol down while rebooting, the normal white writing doesn't appear, it just continues in the same loop at the Asus screen. I dont even get as far as the EeePad splash screen. I'm at a loss for what to try. I can get into recovery or fastboot and it wont connet to the pc. Am I screwed? All of the advice I can find needs recovery etc. The problem started when I tried to wipe the device. Could it have deleted the recovery image, rom etc? Any input would be greatly appreciated.
Thanks
santiago84 said:
Hi all,
My Transformer Prime will not boot past the initial Asus screen. It's remains stuck on this screen but when I hold power down, the device reboots. I am not able to get into recovery using power and vol down, then vol up. I cant turn the device off, it reboots every time. When I try to hold vol down while rebooting, the normal white writing doesn't appear, it just continues in the same loop at the Asus screen. I dont even get as far as the EeePad splash screen. I'm at a loss for what to try. I can get into recovery or fastboot and it wont connet to the pc. Am I screwed? All of the advice I can find needs recovery etc. The problem started when I tried to wipe the device. Could it have deleted the recovery image, rom etc? Any input would be greatly appreciated.
Thanks
Click to expand...
Click to collapse
First, this belongs in q&a or general. Your problems have nothing to do with development.
Secondly, I posted a link a while back in the EOS3 ROM thread in reference to recovering from the exact scenario . The post includes which tools, drivers, and the process in detail on how I recovered down to the command for fast boot flashing the recovery ( which had a specific value for the device ).
EDIT:
Here is my detailed post. Try that and see if fastboot works for you. I was literally in the exact same boat not terribly long ago.
http://forum.xda-developers.com/showpost.php?p=33197007&postcount=508
MODS please move to the appropriate section.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
---------- Post added at 06:45 PM ---------- Previous post was at 06:30 PM ----------
Aso I forgot to ask.... were you already on a JB boot loader? If you were on ICS, make sure you download the ICS blob for twrp from the link and not the JB blob. That's crucial because if you flash the wrong recovery, you are screwed lol.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
santiago84 said:
I am not able to get into recovery using power and vol down, then vol up. I cant turn the device off, it reboots every time. When I try to hold vol down while rebooting, the normal white writing doesn't appear, it just continues in the same loop at the Asus screen.
Click to expand...
Click to collapse
I'm confused, you say here you cannot access the boot menu or recovery selection.
santiago84 said:
I can get into recovery or fastboot and it wont connet to the pc.
Click to expand...
Click to collapse
But here you say you can access recovery and fastboot which you would not be able to if what you said first was true.
lilstevie said:
I'm confused, you say here you cannot access the boot menu or recovery selection.
But here you say you can access recovery and fastboot which you would not be able to if what you said first was true.
Click to expand...
Click to collapse
He likely wiped all of his partitions ( including recovery ) like I did by accident. Fast boot was a pain in the arse for me until I used the -i command along with the new drivers. Hopefully my post resolved his issue.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Thank you for your response so far and apologies for putting the thread in the wrong section. The instructions given were great, only I am unable to get into fastboot. When I try and turn on the device holding vol down, it just boots normally. It doesn't give me the white writing and options I had before. I can't seem to turn the device off either. When I hold the power button it reboots, but doesn't shut down. What can I try to get into fast boot?
Thanks
Sent from my Galaxy Nexus using Tapatalk 2
pyraxiate said:
He likely wiped all of his partitions ( including recovery ) like I did by accident. Fast boot was a pain in the arse for me until I used the -i command along with the new drivers. Hopefully my post resolved his issue.
Sent from my SAMSUNG-SGH-T989 using xda app-developers app
Click to expand...
Click to collapse
Sorry, it was a typo. I meant that I cant get into recovery or fastboot. No matter what I try. Ive never heard of fastboot disappearing. Any thoughts?
santiago84 said:
Sorry, it was a typo. I meant that I cant get into recovery or fastboot. No matter what I try. Ive never heard of fastboot disappearing. Any thoughts?
Click to expand...
Click to collapse
Did you do the nvflash process at any time and keep the blob files?
If you didn't and you cannot get to fastboot then I'm afraid that you are hard bricked
flumpster said:
Did you do the nvflash process at any time and keep the blob files?
If you didn't and you cannot get to fastboot then I'm afraid that you are hard bricked
Click to expand...
Click to collapse
No I didnt do the Nvflash. I unlocked and rooted a while ago, before nvflash was around and havent looked back since. Has anyone ever heard of fastboot being deleted? Ive always been able to get into it.
santiago84 said:
No I didnt do the Nvflash. I unlocked and rooted a while ago, before nvflash was around and havent looked back since. Has anyone ever heard of fastboot being deleted? Ive always been able to get into it.
Click to expand...
Click to collapse
Try holding the down and power button while its on to force shut down, then keep holding volume down as it reboots?
Also, what were you in the process of doing right before the issues began? Did you install something with a different bootloader? You could have wiped bootloader which means you are hosed . . . ..
Sent from my Transformer Prime TF201 using xda app-developers app
pyraxiate said:
Try holding the down and power button while its on to force shut down, then keep holding volume down as it reboots?
Also, what were you in the process of doing right before the issues began? Did you install something with a different bootloader? You could have wiped bootloader which means you are hosed . . . ..
I
Sent from my Transformer Prime TF201 using xda app-developers app
Click to expand...
Click to collapse
I've tried holding the buttons down while it reboots but nothing happens. If I hold the vol up and vol down while pressing power, the device turns off completely.
The problem started when I tried a factory reset in CWM. It crashed after a few seconds and the device rebooted. Not there doesnt appear to be anything on the device. I havent heard of CWM doing this before.
santiago84 said:
I've tried holding the buttons down while it reboots but nothing happens. If I hold the vol up and vol down while pressing power, the device turns off completely.
The problem started when I tried a factory reset in CWM. It crashed after a few seconds and the device rebooted. Not there doesnt appear to be anything on the device. I havent heard of CWM doing this before.
Click to expand...
Click to collapse
try volume up + power,if you see APX and you dont have nvflash then sent it back to ASUS and there is a charge to repair it.Sorry, happens to me
:crying::crying::crying::crying::crying::crying:
santiago84 said:
Sorry, it was a typo. I meant that I cant get into recovery or fastboot. No matter what I try. Ive never heard of fastboot disappearing. Any thoughts?
Click to expand...
Click to collapse
Without fastboot and nvflash there is no hope for recovery except for calling asus and requesting an RMA.
It sounds like your device has the boot to recovery flag, but with a broken recovery, something which the bootloader has no exit path from.
pyraxiate said:
You could have wiped bootloader which means you are hosed . . . ..
Click to expand...
Click to collapse
Without a bootloader you will not get any output from the device, the bootloader is what displays the asus splash screen. Without it the device would just drop into apx mode.
lilstevie said:
Without fastboot and nvflash there is no hope for recovery except for calling asus and requesting an RMA.
It sounds like your device has the boot to recovery flag, but with a broken recovery, something which the bootloader has no exit path from.
Without a bootloader you will not get any output from the device, the bootloader is what displays the asus splash screen. Without it the device would just drop into apx mode.
Click to expand...
Click to collapse
This is probably a silly question but if I send it back to asus for rma should I just claim complete ignorance as to how this happened? Or should I come clean? Has anyone done a rma before? Any idea of time scales or cost etc? Thanks
Sent from my Galaxy Nexus using Tapatalk 2
santiago84 said:
This is probably a silly question but if I send it back to asus for rma should I just claim complete ignorance as to how this happened? Or should I come clean? Has anyone done a rma before? Any idea of time scales or cost etc? Thanks
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Do not lie but don't tell the whole truth if you know what I mean
Don't go into too much info and get straight to the point, also don't show any technical knowledge.
"It doesn't turn on any more, it just flashes on a screen showing Asus".
"It wont turn off"
If you are lucky and they just look at it and not check what has happened they might just switch motherboard rather than messing with it.
Also try to run the battery out first. Harder to check
You shouldn't be covered at all because you agreed to that when you unlocked, but you might get lucky while staying truthful
p.s. I find my grandmother can get away with it more than me
So, what has two thumbs and screwed up his first phone and too inept to recover?? This guy.
Was running fine on CM10.1 with CWM for recovery until my OCD kicked in and I wanted to put CWMTouch on top of CWM.
Wiped Cache
Factory Reset
Wiped All Partitions except Recovery
Phone will not power off, will not reboot, will not boot into recovery. Windows will not recognize the device and I have the correct drivers installed.
I'm thinking that I will have to let it die and try to reboot into recovery. If anyone else has any ideas, I'm open to suggestions. Thanks for your time in advance.
- Rick
rfedeli said:
So, what has two thumbs and screwed up his first phone and too inept to recover?? This guy.
Was running fine on CM10.1 with CWM for recovery until my OCD kicked in and I wanted to put CWMTouch on top of CWM.
Wiped Cache
Factory Reset
Wiped All Partitions except Recovery
Phone will not power off, will not reboot, will not boot into recovery. Windows will not recognize the device and I have the correct drivers installed.
I'm thinking that I will have to let it die and try to reboot into recovery. If anyone else has any ideas, I'm open to suggestions. Thanks for your time in advance.
- Rick
Click to expand...
Click to collapse
That explains it, you wiped system so now you have no OS.
Sent from my HTC One using Tapatalk 2
I was unaware that not having an operating system renders hardware functions inoperable.
Not sure if sarcastic or not so if you format the hard drive on your computer should it still boot?
That said, you can fix it by pushing a rom to the phone with adb while in recovery, or get a USB otg cable and a flash drive and install a rom from it.
[SOLVED] Thanks for help.
gunnyman said:
Not sure if sarcastic or not so if you format the hard drive on your computer should it still boot?
That said, you can fix it by pushing a rom to the phone with adb while in recovery, or get a USB otg cable and a flash drive and install a rom from it.
Click to expand...
Click to collapse
I would never be sarcastic when asking for help. A computer most certainly boots without software, but it will not boot to a particular function.
Apparently, the phone will not reboot without proper lighting. Not joking.
Thanks doarderillion.
rfedeli said:
I would never be sarcastic when asking for help. A computer most certainly boots without software, but it will not boot to a particular function.
Apparently, the phone will not reboot without proper lighting. Not joking.
Thanks doarderillion.
Click to expand...
Click to collapse
If you call booting up to a screen saying MBR not found then, yeah it boots.
Anyhow, glad you have it sorted.
Hold down the power button, you will see your capacative buttons flash. Keep holding it down until the screen turns off, then let go of the power button and immediately hold only the volume down key and you should be able to get the screen to choose boot into recovery.
Something similar happened to me and that is how I got back into recovery.
nest75068 said:
Hold down the power button, you will see your capacative buttons flash. Keep holding it down until the screen turns off, then let go of the power button and immediately hold only the volume down key and you should be able to get the screen to choose boot into recovery.
Something similar happened to me and that is how I got back into recovery.
Click to expand...
Click to collapse
It was a very strange. I normally work in low-lighting and tried to do that quite a few times. I turned a light on and held the phone under the light, and it worked the first time I tried it. It is just what I had experienced. I had gotten a tip from from another XDAer where he had a screen protector that covered his light sensor and experienced something similar.
rfedeli said:
It was a very strange. I normally work in low-lighting and tried to do that quite a few times. I turned a light on and held the phone under the light, and it worked the first time I tried it. It is just what I had experienced. I had gotten a tip from from another XDAer where he had a screen protector that covered his light sensor and experienced something similar.
Click to expand...
Click to collapse
I was just coming to post the bright light thing. WEIRDEST FIX EVER