Related
Hello all, I am starting a new thread because the search is down and google is failing me.
I just updated to the newest radios with the combo zip in fastboot. no errors but upon completion i opted to reboot, shows android with box and arrow.
Am I officially bricked?
I can no longer access hboot, recovery, nothing.
plugging it into usb while hitting power or while android guy is up doesn't register anything on my pc.
any help is appreciated while the search function is down. ( already pricing another one )
for reference i was running cm7 stable with stock cm7 kernel, and was on Radio_2.15.00.09.01.
civicsr2cool said:
Hello all, I am starting a new thread because the search is down and google is failing me.
I just updated to the newest radios with the combo zip in fastboot. no errors but upon completion i opted to reboot, shows android with box and arrow.
Am I officially bricked?
I can no longer access hboot, recovery, nothing.
plugging it into usb while hitting power or while android guy is up doesn't register anything on my pc.
any help is appreciated while the search function is down. ( already pricing another one )
for reference i was running cm7 stable with stock cm7 kernel, and was on Radio_2.15.00.09.01.
Click to expand...
Click to collapse
If it completed successfully there shouldn't be any issue.
So when you turn it on it will boot to an android with a box and an arrow and just stay there forever?
If you can't access your bootloader or anything then it is likely you're bricked.
mattykinsx said:
If it completed successfully there shouldn't be any issue.
So when you turn it on it will boot to an android with a box and an arrow and just stay there forever?
If you can't access your bootloader or anything then it is likely you're bricked.
Click to expand...
Click to collapse
thats correct it boots directly to the android and box and arrow..
no search results for an evo jtag either
civicsr2cool said:
thats correct it boots directly to the android and box and arrow..
no search results for an evo jtag either
Click to expand...
Click to collapse
And pressing the volume down button while powering on yields the same result?
When you flash a radio that screen is the update screen don't battery pull let it run its course.
Sent from my PC36100 using Tapatalk
NVM all is well, i let it set for a few minutes. im ignorant i guess. thank you all for the help, you saved the day!
As Khilbron said, That is the screen that you see when it is updating the radio. It takes a while. Let if finish. Pulling the battery while it is flashing the radio is one of the only ways that you can truly brick your Evo. As long as you see that screen when the Evo powers up you may still be ok. Just let it finish. If you get nothing at all when the Evo powers up, just a black screen, then you are likely toast.
m20120 said:
As Khilbron said, That is the screen that you see when it is updating the radio. It takes a while. Let if finish. Pulling the battery while it is flashing the radio is one of the only ways that you can truly brick your Evo. As long as you see that screen when the Evo powers up you may still be ok. Just let it finish. If you get nothing at all when the Evo powers up, just a black screen, then you are likely toast.
Click to expand...
Click to collapse
thanks man. got it all figured out now. mods plz delete.
for anyone that may find this thread with a similar problem in the future. here is solution that worked in the radio thread.
http://forum.xda-developers.com/showpost.php?p=17041666&postcount=2668
civicsr2cool said:
thanks man. got it all figured out now. mods plz delete.
Click to expand...
Click to collapse
Have more patience.
That's why I asked if it "just stay there forever?"
mattykinsx said:
Have more patience.
That's why I asked if it "just stay there forever?"
Click to expand...
Click to collapse
i was ignorant and kinda thought to myself duh, but i guess not lol
I am glad that it worked out for you. I will have to admit that I kind of freaked out the first time I flashed the radio when I saw that screen but I did not touch it and it finished while I was googling to find out what was happening. I have no idea what HTC was thinking putting up a screen like that... why not any text along with the graphic? It would save many bricked evos.
Hi, let me explain my problem:
I have a desire with power button broken.
last 6 months i use it normally wiht a rooted room (but s-on). When i want to turn on the device I pull off and on the battery twice.
Recently i installed an application and after a reboot the device keeps stuck in the initial splash animation.
So, i ONLY can access to HBoot (0.93 S-on). But i can't enter to recovery to erase userdata and format all and reboot a new room (as usual) because Hboot enter key is the ****ing power button XD.
I tryed to S-OFF in linux with alpharev 1.8 or revolutinary when showing splash but they start and suddenly stop because smthg was wrong.
So the only thing i can do is send basic HBoot commands.
any idea?
You might get more response posting in the correct forum.
Sent from my HTC Desire using Tapatalk
You can download Quick Boot (Reboot) from market. Use it to Reboot, Recovery, Bootloader or Power Off.
Anyway, you're posting this in wrong section, should be in Q&A.
ckpv5 said:
You can download Quick Boot (Reboot) from market. Use it to Reboot, Recovery, Bootloader or Power Off.
Anyway, you're posting this in wrong section, should be in Q&A.
Click to expand...
Click to collapse
Mate, his device is not even reaching the bootanimation, I wonder what kind of market you suppose him to have to use it in splashscreen or bootloader?
Sent from nowhere
tajimura said:
Mate, his device is not even reaching the bootanimation, I wonder what kind of market you suppose him to have to use it in splashscreen or bootloader?
Sent from nowhere
Click to expand...
Click to collapse
Haha.. I got confuse with his statement " When i want to turn on the device I pull off and on the battery twice." So I thought he can boot the phone Wrong section wrong answer
Thanks anyway
Code:
[strike]fastboot oem gencheckpt[/strike]
Good development you've got going here.
Mate flash an original wwe stock rom with its own flash utility (just run the executable) but you will loose root after that use the alpharev utility once your phone has started.
Sent from my HTC Desire using XDA
I had this same problem a while ago. Tried many apps to work around power button (mine was stuck "pressed"). Got to the point where I couldn't do anything without getting into recovery. Used a spare phone until I ordered the flex cable assembly from Ebay.. $40 or so..
Despite many years of working with electronics, it was still quite nerve racking to swap the part out... you have to re-use your camera module and a couple plastic parts stuck to the original (on back of volume buttons i think).
Read instructions and watched videos online several times before starting, and again as I did the work, and size/fit was ever so slightly off... but everything works now and I am a relieved and happy camper
I see the development is active for 4 days now.
Sent from my HTC Desire using Tapatalk
Questions or Problems Should Not Be Posted in the Development Forum
Please Post in the Correct Forums & Read the Forum Rules
Moving to Q&A
And please do not swear in Posts
I'm afraid I might have bricked my KF
It's stuck on the bootscreen...
I used KFU and installed CWR
Using CWR I followed the install instructions for installing cm-7.2.0-RC0-blaze-KANG-20120308
After that I choose reboot into fastboot, and now it's stuck on the boot screen.
KFU doesn't see the KF anymore, and when I hold the powerbutton to boot into recovery it doesn't, it just turns off after a while...
I've browsed several threads (and might be missing something obvious, if so I sincerely apologize in advance, but I'm really lost now).
muppetmaster said:
I've browsed several threads (and might be missing something obvious, if so I sincerely apologize in advance, but I'm really lost now).
Click to expand...
Click to collapse
As ususal, I found the answer after posting *facepalm*
http://forum.xda-developers.com/showpost.php?p=24682516&postcount=3
Use the utility and set it to boot normal with the kindle off, them it'll say waiting for device, connect the kindle turn it on and voila.
Click to expand...
Click to collapse
Sorry for bothering you all, and I hope this helps someone in the future
Hey all,
This is my official "first" post. I rooted the A100 while it was on Honeycomb. Everything was fine. I got an ota update and updated to 3.2.1. Rooted it again and everything SEEMED fine. I got the ota ICS update and the tab would hang at the green android and give me a "!" after about 5 seconds. I fiddled with the update for a while and took it to a friend that knows more about this than I. He proceded to try and unlock the bootloader with the ICS unlock, while it was on Honeycomb. Now my tab is bricked with the green Acer logo, it will not boot. I have no access to recovery, fastboot, adb, bootloader. I can get it to APX mode. I tried to NVflash it, but when I use any NVflash commands, device manager just kicks my device off and the command doesnt execute. I cant use the EUU, because it keeps telling me my CPU ID is wrong, even though I KNOW its correct. I have searched the forums and sent PM's to everyone that has experienced this and fixed it, but no one has answered. Could SOMEONE, ANYONE, PLEASE help!!!!!!
Thank you in advance!!!!!
Cory
Really
No one out there has any insight into this? Ive seen that there are a couple people in the forums that have fixed this issue, but in their posts it doesn't really describe how because they were being PM'd. PLEASE, any info would be GREATLY appreciated!!!!
cooki3monst3r77 said:
No one out there has any insight into this? Ive seen that there are a couple people in the forums that have fixed this issue, but in their posts it doesn't really describe how because they were being PM'd. PLEASE, any info would be GREATLY appreciated!!!!
Click to expand...
Click to collapse
Try using the search on the forums, it's been discussed several times and the only way to fix it currently is to send it in to acer for repair and hope they replace it with a different board that the euu works with. Please stop posting this same question when its been asked repediatly already there are 4 separate posts with this same question being asked by 3 different people
Sent from my MB860 using XDA
OK
I have searched the forums for the past I cant tell you, how many hours. I have looked and looked and in one forum, it looks as though someone fixed this issue because they were able to somehow get to fastboot. I would not just post this on here without my resources having been exhausted. The problem is, in EVERY FORUM I CHECK, the answers and such are PM'd to each other! I have even PM'd the people that seemed to get something working.......to which I have received no reply. Ive seen the posts on this, Ive tried NVflash, I tried to boot holding EVERY combination of buttons, EUU doesnt work, because of the CPUID being "wrong". I have done my research, sir. Please PM me if you think I have wronged you in some way by posting something in a forum meant for helping others, instead of putting me on blast because you think Ive been lazy and not searched the forums.
cooki3monst3r77 said:
No one out there has any insight into this? Ive seen that there are a couple people in the forums that have fixed this issue, but in their posts it doesn't really describe how because they were being PM'd. PLEASE, any info would be GREATLY appreciated!!!!
Click to expand...
Click to collapse
can you boot into fastboot mode?
dunno
Im not sure if I can get to fastboot. There are a couple of people that, it seems, could get to fastboot and APX. Could you direct me on the ways of getting to fastboot? Adb doesn't work for me. Only APX mode. It boots to the green Acer logo. When I try to get to recovery (VOL+PWR), it hangs and will not go to recovery.
Sorry for being short earlier, Im just so frustrated with this. Ive been researching this issue for DAYS. (NVflash, APX, bootloaders, adb, etc....) No progress on it. I even have a DEV friend who may try to decompile the EUU and see if he can force push it to the tab....he just has to find the time. lol
done
At this point Im willing to use the tablet for target practice. If anyone wants it, to mess around with or whatever, you can pay for shipping and keep it.
cooki3monst3r77 said:
At this point Im willing to use the tablet for target practice. If anyone wants it, to mess around with or whatever, you can pay for shipping and keep it.
Click to expand...
Click to collapse
Well that is a hard offer to pass up...
Sent from my LG-P999 using Tapatalk 2
If you and orient fastboot and has the bootloader on the A200 prepare to unlock and install cwm recovery and is saved
hard-resset first try with the buttons
1 tablet off completely its
2 lock button on the screen is right
3 hold down power and volume - that is left
4 when the tablet vibrate release the power button and quickly move the screen lock button to the right and left without releasing the volume -
5 your tablet should start
but it works I say and try fastboot
I dont know if the boot loader is locked or not. I cant flash cwm because I cant get to recovery/adb/fastboot/etc. I tried the hard reset and the tablet hangs on the green Acer screen after reboot. NVflash doesnt work because ???, device manager just drops it when I try to send commands and nvflash says something about not being able to write to usb. And yes, I have the Nvidia apx drivers installed.
peporras said:
1 tablet off completely its ( holding it in landscape)
2 lock button on the screen is right
3 hold down power and volume - that is left
4 when the tablet vibrate release the power button and quickly move the screen lock button to the right and left without releasing the volume -
5 your tablet should start in fastboot mode
are you able to get fastboot going?
if so try to flashing a custom recovery from thor 17 ( google it)
i had a problem like this and was able to fix it by flashing the leak isc rom through this recovery. it might be worth a try.
Click to expand...
Click to collapse
hi everybody,
I'm usually more active on auto forums but I need your help.
wanting to install a custom rom, I'm a but lost in the manipulations. Last night when I wanted to turn on the tab (only with the power button), I had the google logo that was displayed at the top right and the small rectangle of recovery menu (start, recovery, reboot bootloader and poweroff). With buttons I could choose one of four functions. I had access to the recovery menu, when I choosen restart bootloader, it well reboot and poweroff worked well too. By when I clicked start I had a small line at the top left telling me "boot failed"
I try to flash everything thanks to a tutorial.
So I'm DL the original elements but still the same issue. Having struggled until 3am I give up. This morning when I tried to turn on the tab, I did even more than what I have explained below whatsoever with the power button or volume down + power nothing happens the screen stays black.
Any Ideas?
PS sorry for the language I'm french
If you bought it from a local store or if a local store carries it, I'd recommend just retuning for a new one. Haven't seen anyone having your problem. If it won't even turn on, then any store should exchange it, or return it, with no questions ask once they see how your tablet is behaving!!
SwiftKey'ed from my White Sprint Note 2 using XDA Premium
stanglifemike said:
If you bought it from a local store or if a local store carries it, I'd recommend just retuning for a new one. Haven't seen anyone having your problem. If it won't even turn on, then any store should exchange it, or return it, with no questions ask once they see how your tablet is behaving!!
SwiftKey'ed from my White Sprint Note 2 using XDA Premium
Click to expand...
Click to collapse
I'm seriously thinking of this solution but I'm afraid before they give me a new one they send it to their after sales service. If they find out I have rooted it and unlock the bootloader they will make nothing for me
Have you tried returning it to stock to see if it'll boot then? It could just be a bad flash.
sfreemanoh said:
Have you tried returning it to stock to see if it'll boot then? It could just be a bad flash.
Click to expand...
Click to collapse
I tried every thing.I downloaded nakasig-jwr66v-factory-aebc7b11 and I flash everything but nothing happens. Yesterday evening I was able to boot it (even if it was a bad bood I had only access to recovery mode), but from this morning I tried everything but nothing happens. Even if I plug it to my PC impossible to boot it. The PC do not recognize it (I checked in ADB mode and fastboot mode but the PC do not recognize it)
Good English friend. Can you boot into TWRP? If yes, install any custom ROM after a thorough wipe in recovery. Good luck!
Sent from my Nexus 4 using Tapatalk 4 Beta
swagstr said:
Good English friend. Can you boot into TWRP? If yes, install any custom ROM after a thorough wipe in recovery. Good luck!
Sent from my Nexus 4 using Tapatalk 4 Beta
Click to expand...
Click to collapse
Thank you .
No it doesn't works. For the time being my first to issue is to succeed to boot it at least as yesterday evening.
So if I'm understanding you correctly the Nexus 7 won't even turn on at all now, right? Try holding the power button down for at least 30 seconds and see if it will turn on.
Also, the Nakasig image is for the 2012 version of the Nexus 7 and won't work with the new one. The new 2013 version is named Flo but Google hasn't released the factory images for it yet. However, if you can get the device to power on and back into bootloader mode you should be ok as there are a few unofficial versions of the Flo image on the forum.
One last thing, to quickly boot into bootloader mode hold the Volume Down button while pressing the power button. But try just the power button for at least 30 seconds first to see if you can get it to turn on at all.
geckocavemen said:
One last thing, to quickly boot into bootloader mode hold the Volume Down button while pressing the power button. But try just the power button for at least 30 seconds first to see if you can get it to turn on at all.
Click to expand...
Click to collapse
+1 Try plugging it in for awhile too. You want to get to the bootloader - the screen with the Android where you go through the options with the volume buttons. Once there,you can use fastboot to flash TWRP and fix from there. Again, stay away from the OLD Nexus files.
Sent from my Nexus 7 using Tapatalk 4
geckocavemen said:
So if I'm understanding you correctly the Nexus 7 won't even turn on at all now, right? Try holding the power button down for at least 30 seconds and see if it will turn on.
Also, the Nakasig image is for the 2012 version of the Nexus 7 and won't work with the new one. The new 2013 version is named Flo but Google hasn't released the factory images for it yet. However, if you can get the device to power on and back into bootloader mode you should be ok as there are a few unofficial versions of the Flo image on the forum.
One last thing, to quickly boot into bootloader mode hold the Volume Down button while pressing the power button. But try just the power button for at least 30 seconds first to see if you can get it to turn on at all.
Click to expand...
Click to collapse
I tried to keep on the power button during 1 min with and without charger and pluged to PC : nothing happens. I tried the same thing with volume down + power and nothing happens either
I'm not sure what might help next. Perhaps someone with more experience will come along with advice. If it were me I would probably return it and tell them the power button stopped working.
stef77972 said:
I tried every thing.I downloaded nakasig-jwr66v-factory-aebc7b11 and I flash everything but nothing happens. Yesterday evening I was able to boot it (even if it was a bad bood I had only access to recovery mode), but from this morning I tried everything but nothing happens. Even if I plug it to my PC impossible to boot it. The PC do not recognize it (I checked in ADB mode and fastboot mode but the PC do not recognize it)
Click to expand...
Click to collapse
So you flashed everything from the file nakasig-jwr66v-factory-aebc7b11.tgz? It's for the 1st gen Nexus 7 Mobile version. It would also flash the bootloader and radio. I am guessing that flashing the wrong bootloader might have bricked your device. Someone please correct me if i am wrong.
I'm seriously thinking of this solution. I'm just worry if asus find out everything I made
andyli1985 said:
So you flashed everything from the file nakasig-jwr66v-factory-aebc7b11.tgz? It's for the 1st gen Nexus 7 Mobile version. It would also flash the bootloader and radio. I am guessing that flashing the wrong bootloader might have bricked your device. Someone please correct me if i am wrong.
Click to expand...
Click to collapse
Hmm.. This is possible. If your device will not turn on, I'm thinking you are SOL my friend. Or in your native tongue: merde pas de chance. Hopefully that conveys it
Sent from my Nexus 7 using Tapatalk 4
andyli1985 said:
So you flashed everything from the file nakasig-jwr66v-factory-aebc7b11.tgz? It's for the 1st gen Nexus 7 Mobile version. It would also flash the bootloader and radio. I am guessing that flashing the wrong bootloader might have bricked your device. Someone please correct me if i am wrong.
Click to expand...
Click to collapse
Yes I used this one but I think I have the old version
stef77972 said:
Yes I used this one but I think I have the old version
Click to expand...
Click to collapse
Oh boy... *Grabs popcorn*
Sent from my Nexus 7 using Tapatalk 4
stef77972 said:
Yes I used this one but I think I have the old version
Click to expand...
Click to collapse
the old nexus 7 or the new 2013 model with a camera on the back? is yours wifi only or 3g capable?
The only thing i can think of is to plug into your pc's usb port and hold the power button for 30sec.
Then unplug from PC and press power button for about 15sec and you should see the google logo - if not, i think your bootloader is bricked from flashing the wrong one.
If you do see the google logo, keep holding power and also press vol down as soon as you see the logo - should get you into the bootloader.
Messing up the bootloader is the only way you can brick a nexus, feel sorry for ya man
noob question: so you are using a Nexus 7 (2013) and you flashed an old-nexus-7 ROM on your device? If you're using the new one, here is the ROM for the new one http://forum.xda-developers.com/showthread.php?p=44054613.
I have just had the same problem. Flash the old nexus 7 kernel on the new one, luckily I fixed it
There is a different forum for the 2012 Nexus 7 here. This forum is for the 2013 version.