Ok so the title says it all really i have a zoostorm 10.1 inch playtab it is also rooted
i just can not get it in flash mode to install custom recovery image
do i hold a button ?
i tried holding volume and that i get a picture of a droid on his back with a x - no command
any one out there with any info for me would be sweet thanks for taking the time to read this
hopefully you can help on here great forum
please read
bump
Related
hello all,
I rooted my xoom following the instructions on the [GUIDE] XOOM 3G Euro Root Instructions + Files.(http://forum.xda-developers.com/showthread.php?t=1049901) thread and then installed CWM from http://forum.xda-developers.com/showthread.php?t=1038870
I later installed Tiamat Xoom Kernel Boot Image and Kernel from http://forum.xda-developers.com/showthread.php?t=978013
My xoom wont pass the motorola dual core screen
tried the power button n volume down n up options but on my command prompt am getting Error: device not found
any suggestions how can I get my Xoom to work
any help would be much appreciated
many thanks
Not sure i can help, but this should be posted in Q & A.
Sent From My Evo
Not development. Moved to Q&A.
At what point did you get stuck at the red m? What had you just flashed?
It sounds like a problem with the boot image. Are you sure you used the correct one (wifi or 3g)?
Try holding power and volume up for a good 15 seconds yo try to kill power. If you manage it, use power and the volume button (I think down) to get into fastboot and reflash a new download of the right boot image.
Sent from my GT-I9000 using XDA Premium App
Hey guys,
I followed the instructions from the following URL:
http://forum.xda-developers.com/showthread.php?t=1227618
In regards to Rooting my Phone which is now running Telus Stock Gingerbread.
I have no problems flashing the Speedmod kernel with odin but i am unable to boot into recovery mode [vol up & down + power button].
I've tried the [Home + Vol up + power button] but still no luck. Wondering why other Telus Fascinate owners are able to boot into recovery when I can't.
Does anyone know why I can't get into recovery mode?
Thanks,
I did hear that a few of the telus fascinates do not have the actual hardware option enabled to get into recovery mode.
Has anybody else that owns a telus fascinate having problems getting into recovery mode?
Sent from my SGH-T959D
When you are trying to boot into recovery (holding vol up&down+power) are you letting go of the power once the boot screen appears (The one that says SGH-T959D)?
I notice that if I don't let go out power it will continuously reboot. I see that another user in the link you posted is having issues with that CWM. Maybe try posting in that thread or wait for a response.
Are you looking for simply stock 2.3.3 rooted with CWM? Or something like CM7?
Thanks for you reply.
I would like to post it in that forum but I do not have enough posts yet to post in the other development forums.
I do let go of the power button at the right time because I'm use to getting it into 'Download' mode without any issues. Plus the fact that I have also tried almost every Volume up, down and home combination to try get it into recovery. No such luck through.
All I'm wanting right now is to simply get Gingerbread rooted on my phone.
Sorry guys it finally worked after numerous trys.
Cheers
Sent from my SGH-T959D
Sorry about this question, but I have a blank screen at my samsung captivate after doing failed flashing with odin. I have bricked my Galaxy? No matter what I do always show me blank screen (usb port, charging the phone, power on, etc)-
Thanks and wait any reply asap.
What firmware are you currently running? Where in the flashing did it fail? Provide more information please.
If you can enter download mode (Home + Vol Down + Power) then you can simply flash it again. In this case, your device is not bricked at all. If you cannot enter download mode, you may be in a bind, but please provide more information to see if we can help.
Also, this would have been the proper forum to post in.
Hi upichie, well, I've tested the gingerbread from this link "/posts/celulares/12869092/Personalizar-Samsung-Captivate-a-fondo_.html at taringa" and during the process of flashing is stuck at factory.rfs, I've tested 2 times and always get the same and I havent a failed download of the rom file.
Then after searching in google, I've read that I can test another rom, then I've downloaded the 2.3.4 from this link "/comunidades/soandroid/3821213/(Aporte)Actualizar-Samsung-Captivate-Android-2_3_4-+-Root.html at taringa" and stuck at cache.rfs a long time more than 20minutes then I remove from usb and then I've got the white screen at the entire display like a torch no matter what I do. Sorry by my english people .
try to access download mode by take out the battery and press vol up + vol down + power or vol down + home + power .when u can access to download model and flash again wit stock rom
Please use the Q&A Forum for questions Thanks
Moving to Q&A
Hello people, no matter what I do, always I get the same screen, now I've attached an screenshot to you people, thanks
I only want a reply to confirm that I've bricked my captivate hard or soft thanks alot.
Hello people, after searching a solution one dude say to me that Was a bootloader brick
I have to sold my captivate, but thanks to all your replies.
Sent from my ST18a using xda app-developers app
Hi everyone,
I just bricked my A510 and I am unable to fix it. My tablet does not have a bootlader at the moment and it won't boot. I found this guide in the forums but this guide does not work for A510 :
http://forum.xda-developers.com/showthread.php?t=1585907
I also tried to enter the APX mode by following this thread : http://forum.xda-developers.com/showthread.php?t=1747802 but I also had no luck there.
If I can enter the APX mode then maybe I can flash a new bootloader and then using recovery I might be able to install one of the ROMs I found here. But so far no go.
Any help with unbricking my tablet will be greatly appreciated.
Thank you all
sad,
how did it happen ?
sorry, no answer to help currently
The method for the 500 tab for APX mode, was press and hold the reset (paper clip hole on the bottom). Then press and hold PWR till it vibrates. Then count to 3 seconds, release PWR, then 1 second later release the paper clip.
This should leave you with a black screen, and the PWR light should be on.
This was for the 500/501 series tabs.
the method for APX is described in one of the quoted post of the OP. However the only way to check the A510 is in APX is to plug it to the computer.
In this cas you have to press and hold both volume keys, press reset with a paper clip, and the release the volume keys. The screen will stay black and the power led will not lit either.
However APX mode is only for flashing via nvflash and we don't have any element to flash an A510 this way...
None of the shortcut methods for entering APX mode discussed in these forums worked for A510. They only make the tablet turn on as usual and it just gets stuck in the boot screen with Acer logo. I guess I will have to wait until someone finds a way. Please keep me posted if you find out or hear any solution.
Thank you
One of the old tricks (hold PWR & Vol- & toggle rotation lock) still works.
Moscow Desire said:
One of the old tricks (hold PWR & Vol- & toggle rotation lock) still works.
Click to expand...
Click to collapse
This also did not work on A510
Thanks to everyone who replied and tried to help though.
Any new suggestions will be highly appreciated.
Tegra 3 nvflash
shredler said:
Hi everyone,
I just bricked my A510 and I am unable to fix it. My tablet does not have a bootlader at the moment and it won't boot. I found this guide in the forums but this guide does not work for A510 :
http://forum.xda-developers.com/showthread.php?t=1585907
I also tried to enter the APX mode by following this thread : http://forum.xda-developers.com/showthread.php?t=1747802 but I also had no luck there.
If I can enter the APX mode then maybe I can flash a new bootloader and then using recovery I might be able to install one of the ROMs I found here. But so far no go.
Any help with unbricking my tablet will be greatly appreciated.
Thank you all
Click to expand...
Click to collapse
I have the same problem. Have you tried this tegra 3 nvflash method?
http://forum.xda-developers.com/showthread.php?t=1927818
Click to expand...
Click to collapse
I think that tegra 3 no longer support nvflash from tegra 2. Well it's for transformer prime but it worth a try. It's tegra 3 too. Just I don't know how to modify it to work on Acer A510.
Dear all,
If you haven't updated it, don't do it.
My situation now is:
1. It stucks at the red dual core logo; (I think it shouldn't be called a boot loop)
2. It can't be powered down; (even I press and hold the power button forever!)
3. If I reboot it, I can still press the -vol button to choose between modes, but there are one 3: NvFlash; RSD; and fastboot. No "android recovery" option.
As of now, I put it into Nvflash mode so that the screen will not keep shining with the red logo.
May anyone suggest how I could unbrick it, or the worst case, reinstall everthing to stock?
Thanks very much for your help!
tech.arthur said:
Dear all,
If you haven't updated it, don't do it.
My situation now is:
1. It stucks at the red dual core logo; (I think it shouldn't be called a boot loop)
2. It can't be powered down; (even I press and hold the power button forever!)
3. If I reboot it, I can still press the -vol button to choose between modes, but there are one 3: NvFlash; RSD; and fastboot. No "android recovery" option.
As of now, I put it into Nvflash mode so that the screen will not keep shining with the red logo.
May anyone suggest how I could unbrick it, or the worst case, reinstall everthing to stock?
Thanks very much for your help!
Click to expand...
Click to collapse
Back to stock is best, For a pure 4.2 JB hassle free try links..
http://forum.xda-developers.com/showthread.php?t=1997434
http://forum.xda-developers.com/showthread.php?t=1999897
tumpy said:
Back to stock is best, For a pure 4.2 JB hassle free try links..
http://forum.xda-developers.com/showthread.php?t=1997434
http://forum.xda-developers.com/showthread.php?t=1999897
Click to expand...
Click to collapse
Thanks for your reply. But seems that the post doesn't teach me how I could restore it to that stock given my situations?
tech.arthur said:
Thanks for your reply. But seems that the post doesn't teach me how I could restore it to that stock given my situations?
Click to expand...
Click to collapse
If you lost recovery then you need to ADB into the unit to force it into recovery (if you don't know what I'm talking about get a friend who does).
In either case you will need to have the developer tools installed on a computer and connect via USB to be able to flash Stock Rom via fastboot.
Back to EOS4 203 build!
Sent from my Xoom using Tapatalk 4 Beta
Dear Guys,
Thanks you for your opinions.
1. I would like to flash back to 203. Would any one care to give me some step by step guides how to do that, given my situation, being stucked at the start up and couldn't go into recovery?
2. If I have a friend who is so technically superb, I wouldn't have to come up here to ask for help. As I always think here is where the genius gather.
Looking forward to a solution. Thanks again for all of you who cares.
re-install earlier ROM
tech.arthur said:
Dear all,
If you haven't updated it, don't do it.
My situation now is:
1. It stucks at the red dual core logo; (I think it shouldn't be called a boot loop)
2. It can't be powered down; (even I press and hold the power button forever!)
3. If I reboot it, I can still press the -vol button to choose between modes, but there are one 3: NvFlash; RSD; and fastboot. No "android recovery" option.
As of now, I put it into Nvflash mode so that the screen will not keep shining with the red logo.
May anyone suggest how I could unbrick it, or the worst case, reinstall everthing to stock?
Thanks very much for your help!
Click to expand...
Click to collapse
Try the power + vol up +vol down reboot... this should get you to a bootloader screen, from there you can select recovery and that should allow you to re-install the 203 nightly. BTW... the problem was noted in the developer forum soon after the 204/205 file were posted.
ADVICE:: you might want to review any files in the forum before jumping on any upgrade.
if the above doesn't work then try -
Re-install your recovery - using the same steps that originally were used to root and install a recovery.
You may have to use ADB to push the files out to the device. (do a search for adb in this forum, or perhaps root kit)
With this it should be simple to recover.
I was fortunate that I was able to return to recovery and install 203 with no issues other than a anxious moments wondering what I did wrong
hope this helps