Related
Is there a file in the android system that, sort of like an autoexec.bat, lists what to do on startup? For example forcing the system into recovery or download on power on?
I flashed the latest Vibrant firmware and did so with the option to repartition, which Im now finding out was not the right way to flash this one.
Long story short, it didnt contain the dbdata directory information and now, I am unable to boot and unable to get to download. I still have ADB access, it just isnt responding to ADB reboot download, it just comes right back up booting into recovery to flash the last stage of odin before it starts up.
Is there a way to force the phone back into download mode or force it to stop rebooting into recovery?
Pull battery out and USB to use the hardware buttons to manually get into download mode?
P.S. wrong forum
Aren't there some apps that can do that? I do it manually but like you said its not working for you, p.s im downloading that firmware
Sent from my SGH-T959 using XDA App
iwillkillyou said:
Aren't there some apps that can do that? I do it manually but like you said its not working for you, p.s im downloading that firmware
Sent from my SGH-T959 using XDA App
Click to expand...
Click to collapse
OP said that he isn't able to boot so I believe he's stuck on the loadup to Android.
zephiK said:
Pull battery out and USB to use the hardware buttons to manually get into download mode?
P.S. wrong forum
Click to expand...
Click to collapse
Manual buttons arent seemingly working, so far ive tried every conceivable combination of vol up down and power, even if all I do is plug the phone in Im back in recovery before the battery turns green.
(ps. I know, but I had a billion percent better chance not getting a mouthbreather response, despite the definite chance of flame posts lol)
Viralblack said:
Manual buttons arent seemingly working, so far ive tried every conceivable combination of vol up down and power, even if all I do is plug the phone in Im back in recovery before the battery turns green.
(ps. I know, but I had a billion percent better chance not getting a mouthbreather response, despite the definite chance of flame posts lol)
Click to expand...
Click to collapse
Try every step here: http://forum.xda-developers.com/showthread.php?t=771247
Have you successfully gotten into Download mode with hardware buttons before? Or are you one of those vibrants with "locked download?"
I have a feeling mines locked, Ive never used the buttons to successfully get into download mode, just adb reboot download
EDIT: Tried the posts suggestions, problem is second I plug in the USB and the battery pops up it goes right to recovery. Even if im holding the buttons before hand.
Viralblack said:
I have a feeling mines locked, Ive never used the buttons to successfully get into download mode, just adb reboot download
EDIT: Tried the posts suggestions, problem is second I plug in the USB and the battery pops up it goes right to recovery. Even if im holding the buttons before hand.
Click to expand...
Click to collapse
x_x don't know what to tell you then. With locked hardware, you have to be really careful because if something goes wrong you cant manually get back in there. Do you have Clockwork Recovery? try restoring to a previous nandroid backup.
zephiK said:
x_x don't know what to tell you then. With locked hardware, you have to be really careful because if something goes wrong you cant manually get back in there. Do you have Clockwork Recovery? try restoring to a previous nandroid backup.
Click to expand...
Click to collapse
I was working with that a bit, but it just kept getting to datadata and being unable to wipe or flash to it due to the odin botch. I tried wiping it clean and it just wouldnt let me do that to reflash.
So now im stuck at the samsung recovery screen without the ability to get into clockwork or flash lol
This smells like 130 bucks for a new phone I think... brick number two >.>
Viralblack said:
I was working with that a bit, but it just kept getting to datadata and being unable to wipe or flash to it due to the odin botch. I tried wiping it clean and it just wouldnt let me do that to reflash.
So now im stuck at the samsung recovery screen without the ability to get into clockwork or flash lol
This smells like 130 bucks for a new phone I think... brick number two >.>
Click to expand...
Click to collapse
Why did you change update.zip? Update.zip should always lead to Clockwork :|
zephiK said:
Why did you change update.zip? Update.zip should always lead to Clockwork :|
Click to expand...
Click to collapse
I didnt! But when I was formatting and it failed to reapply the nandroid completely cause of the section it couldnt mount, now when I hit reinstall packages it just reboots. Same with shell, it just yells at me and tells me to die in a fire.
if you didnt figure this out, the way to fix it is to first flash WITH ODIN the original JVD firmware and check repartition, then flash the new one IN ODIN without the repartition box checked.
first update includes the dbdata that the phone is looking for.
Yeah, I figured it out now, but Odin is seriously the devil if your phone doesnt have the hardware buttons enabled.
Now heres a question, if I can still get into stock recovery... is there a way to like, you know, recover using the stock system? lol
BUT THE GOOD NEWS IS that Tmo is letting me warranty out my phone for free, shipping me a new one, and gave me a loner while I wait.
TMo for the win.
Viralblack said:
BUT THE GOOD NEWS IS that Tmo is letting me warranty out my phone for free, shipping me a new one, and gave me a loner while I wait.
TMo for the win.
Click to expand...
Click to collapse
lol looks like you and I are in the same boat man. Hardware lock FTMFL. I have never been able to get into download mode, or recovery mode with the hardware keys, only with adb reboot recovery/download and terminal emulator app with SU privs. I wish there was a jumper we could reset to unlock it haha that'd be the s*# son. Good old pentium 133 in the palm of the hands, but no . Atleast they are taking care of the people who don't do things properly.
I did the same thing and ended up with the same problem, but i was able to get in into download mode. When i would plug it in it would try to boot into recovery after the battery screen i would use the keys to make it boot to download mode instead of recovery, it was a *****, but i got it, though idk if there is another way for people with locked down phones.
OK i've searched and read until my eyes crossed but even the most promising threads seem to peter out when people run out of ideas.
I'm clinging to the popular assertion that "if it boots it's not bricked", someone please help me prove it?
The trouble began when was i was starting over with the instructions here:
(Google - How To: Recover your G1 from a bring Bricked. - Project Hosting on Google Code, involving installation of RC29)
That's as far as i got. The flash seemed to go OK but then it booted to the white triangle with the exclamation point.
The only keys that work are ALT+L and ALT+S. I can't get an adb or fastboot connection. ALT+W doesn't do anything at all and it doesn't reboot from pressing Home+Back, i've got to remove the battery.
Message at the top of the recovery screen says "E:Can't open /cache/recovery/command.
Help?
Thanks
- joe
I don't think it is bricked as recovery is trying to run something ( and failing )
can you boot to the bootloader with power + cam?
what hboot version do you have?
is it 1.33.2005 ?
if it is have you got the newest adb drivers ( this is assuming you are using windows )
assuming the above is true, then get to fastboot mode with power + back ( or power + cam, then press back )
then try
Code:
fastboot erase cache
and try to get to recovery again ( reboot by pressing menu and then hold home )
if that doesn't work then supply the version numbers you get on the bootloader screen
it will help to workout what nbh files you can flash etc
also do you know what recovery version you have?
Effdee said:
can you boot to the bootloader with power + cam?
Click to expand...
Click to collapse
All i get from any button combination is the white triangle with the excalmation point and the dead phone, whatever all that is supposed to mean.
Effdee said:
what hboot version do you have?
is it 1.33.2005 ?
Click to expand...
Click to collapse
I'm sorry i don't know what that means. ALL i get is the triangle screen, i have to press ALT+L to toggle a log display with instructions for what the other button combinations (should) do. There are no numbers of any sort.
My drivers are all up to date and prior to this incident fastboot and adb both worked and i could tether my phone. But since i can't get a connection now and ALT+W (wipe) doesn't do anything, i seem to be limited to loading update.zips and watching the log as they fail to do anything helpful. Generally they fail (as, e.g., Ohsaka's Superwipe) with a "No Signature Verification Failed" or in the case of signed firmware updates, with a much longer and inscrutable error.
But thanks for the response, any advice or possibilities are appreciated.
- joe
passingthru said:
All i get from any button combination is the white triangle with the excalmation point and the dead phone, whatever all that is supposed to mean.
I'm sorry i don't know what that means. ALL i get is the triangle screen, i have to press ALT+L to toggle a log display with instructions for what the other button combinations (should) do. There are no numbers of any sort.
My drivers are all up to date and prior to this incident fastboot and adb both worked and i could tether my phone. But since i can't get a connection now and ALT+W (wipe) doesn't do anything, i seem to be limited to loading update.zips and watching the log as they fail to do anything helpful. Generally they fail (as, e.g., Ohsaka's Superwipe) with a "No Signature Verification Failed" or in the case of signed firmware updates, with a much longer and inscrutable error.
But thanks for the response, any advice or possibilities are appreciated.
- joe
Click to expand...
Click to collapse
so you are trying to flash custom zips with stock recovery?
you need to flash an official update ( with official signatures ) then you need to root and flash a custom recovery so that custom zips will work
http://forum.xda-developers.com/showthread.php?t=442480
flash the appropriate nbh as instucted
you didn't specifically say that powering on whilst holding the camera button doesn't work so I will assume that it does actually work
then follow
Rooting your RC29 or lower phone
using recovery.img from here http://forum.xda-developers.com/showthread.php?t=566669 )
that will give you RA1.7.0 , which you can then use to flash custom zips
but you will need to flash spl 1.33.2005 (danger), which is redundant , you want 2708 for extra 15mb which needs spl 1.33.0013d
http://forum.xda-developers.com/showthread.php?t=831139
read that post a few times, the bit you need is Flashing From a Stock SPL
( which will get you to this post http://forum.xda-developers.com/showpost.php?p=6510019&postcount=76 )
make sure you read all of those links a few times so you understand everything you need to do before you try to do it
Its a learning curve , but it is easy once you understand it
I did get lots of help from a couple of guys in a pub, Mike and Wil , especially Wil who pointed me here ( xda ) and told me who to trust ( ezterry ) and who to just ignore ( pretty much everyone else )
Effdee said:
so you are trying to flash custom zips with stock recovery?
Click to expand...
Click to collapse
Well in my initial ignorance, yes i did try to do that but it didn't work. So i tried e.g. an official signed RC30, which failed with aforementioned inscrutable error. I can try again if the specific error is relevant, but i've tried it at least a half dozen times, with different downloads and verifying same and formatting my SD card FAT32 and only putting the update on it and then safely ejecting the card and ensuring that the file is named update.zip and not update.zip.zip and etc and so on. I've been reading a lot...
Effdee said:
you didn't specifically say that powering on whilst holding the camera button doesn't work so I will assume that it does actually work
Click to expand...
Click to collapse
I said "any" button combination gives me the same result, i.e. the screen with the triangle and exclamation point. So specifically, no the camera button doesn't work, it would be great if it did. I don't think the button itself is broke though, because it had to work in order to get me into this mess.
The link you gave is approximately the process i was attempting, (as a new user i'm not permitted to post links yet), and it was directly after flashing to RC29 that my phone booted to this triangle screen.
So like i said, i am pretty much limited to flashing update.zips since that's all that this interface provides apart from wiping, which doesn't do anything. I was hoping someone could point me to an official signed firmware upgrade (or downgrade or anything really) which would give me some sort of starting point. Or, something. Anything... i'm really in a pickle without my phone.
Thanks again,
- joe
EDIT: Just for the sake of curiosity, i see that Windows recognizes my phone as a storage device only with "no media" so i wonder if that's an ext3 partition, which makes me wonder if i could mount it with a Mac and wipe it so i could try the RC29 flash again. I know very little of *nix or Macs, i'm just going "hmmm".
Something...
I managed to install the CRB43 cupcake update, or anyway according to the console the process completed. I was hoping it would make all my buttons work so i could start over but it booted right to the triangle again.
At the end of the upgrade process it wants me to use Home+Back to reboot but that doesn't work so i have to remove the battery... could this be the problem and if so is there anything else i can do instead?
Thanks,
- joe
So are we calling it a brick?
I don't mean to be impatient but i need to know if i should let go and move on, or if perhaps there is a more appropriate area of the forum to ask this particular question.
I need closure. Or maybe more importantly to all the folks in similar circumstances who are Googling like mad and seeing similar threads just sorta fade away, it would be nice to have a definitive expert opinion like e.g. "if the camera button doesn't work and you can't get an adb connection then it is a hopeless brick". Just for example.
Thanks
- joe
passingthru said:
So are we calling it a brick?
I don't mean to be impatient but i need to know if i should let go and move on, or if perhaps there is a more appropriate area of the forum to ask this particular question.
I need closure. Or maybe more importantly to all the folks in similar circumstances who are Googling like mad and seeing similar threads just sorta fade away, it would be nice to have a definitive expert opinion like e.g. "if the camera button doesn't work and you can't get an adb connection then it is a hopeless brick". Just for example.
Thanks
- joe
Click to expand...
Click to collapse
If you are in recovery (Ie alt-L gives you some options) you are in theory not bricked)
Depending on what is installed powering on with power+camera, pawer+back, power+send (send seems only on the 2000 series dreams and only with some bootloaders) you can access fastboot and at the least use an nbh to restore a working system.
In some cases however there is a stuck home button forcing the booting of recovery and a stock recovery.. or an issue with the misc partition failing to cleae the boot mode.. In these cases booting fastboot is hard and something needs to be done with the hardware issue. in particular if you have a stock recovery w/o test keys.
Last if you are not in a recovery (stock or otherwise) and can't boot to recovery, system, or fastboot; and niether fastboot or adb works, you are "bricked" however if you power on while holding the trackball and see the led turn blue the jtag methods can restore your phone as long as all hardware buttons are operational.
Most of us (including myself) have not been stuck in recovery where rebooting holding camera didn't switch us to fastboot.
passingthru said:
So are we calling it a brick?
I don't mean to be impatient but i need to know if i should let go and move on, or if perhaps there is a more appropriate area of the forum to ask this particular question.
I need closure. Or maybe more importantly to all the folks in similar circumstances who are Googling like mad and seeing similar threads just sorta fade away, it would be nice to have a definitive expert opinion like e.g. "if the camera button doesn't work and you can't get an adb connection then it is a hopeless brick". Just for example.
Thanks
- joe
Click to expand...
Click to collapse
you need a custom recovery, ( the triangle is stock recovery and is very limited )
to install a custom recovery you need root
to get root , read the links I gave
ezterry said:
...however if you power on while holding the trackball and see the led turn blue the jtag methods can restore your phone...
Click to expand...
Click to collapse
Thank you for that. I was panicked because i didn't have a phone but now i've gone out and got a shiny new HD2 and i have a G1 in my desk drawer, the JTAG thing looks like fun. I still want to resurrect my old phone because i still love it.
ezterry said:
...as long as all hardware buttons are operational.
Click to expand...
Click to collapse
Could a few drops of water, like from getting a little bit rained on, have permanently messed up my buttons?
Thanks much,
- joe
EDIT: Also, you said,
ezterry said:
...or an issue with the misc partition failing to cleae the boot mode..
Click to expand...
Click to collapse
If this were the case would i see an error to that effect in the recovery? I had hoped that "E:Can't open /cache/recovery/command" would be a major clue but all the Google returns on that error were people who could still access fastboot.
passingthru said:
If this were the case would i see an error to that effect in the recovery? I had hoped that "E:Can't open /cache/recovery/command" would be a major clue but all the Google returns on that error were people who could still access fastboot.
Click to expand...
Click to collapse
in the recovery log.. /tmp/recovery.log .. but if you have a stock recovery w/o test keys, or adb I'm not sure how to go about checking it. (without somehow getting a custom recovery installed)
misc is not cache.. so misc errors are not reported as cache errors.
ezterry said:
misc is not cache.. so misc errors are not reported as cache errors.
Click to expand...
Click to collapse
Understood, i was just trying to eliminate (or confirm) possible issues. So i wondered if the /misc error would be reported in the recovery console like my /cache error is, and/or if they might represent a similar sort of failure. Because you seemed to be classifying that (the misc error) as a hardware issue which would need dealt with apart from the JTAG procedure.
I was researching the process and it doesn't seem worth the money when i can get a broken G1 from eBay for $35, so maybe whether it's hardware or software, i'd be likelier to get it fixed by mixing and matching parts?
Thanks again.
- joe
I find my newly purchased tab 8.9 very laggy with the stock TouchWiz
Before returning it I wanted ti try the Overcome rom to see if it can get any smoother.
I carefully followed there instructions but I am unable to go past the downloading droid. once I validate with the right button volume, the tablet simply reboots.
Does anyone else have this issue?
josibarns said:
I find my newly purchased tab 8.9 very laggy with the stock TouchWiz
Before returning it I wanted ti try the Overcome rom to see if it can get any smoother.
I carefully followed there instructions but I am unable to go past the downloading droid. once I validate with the right button volume, the tablet simply reboots.
Does anyone else have this issue?
Click to expand...
Click to collapse
Let me get this right: you sucessfully flashed Overcome, and want to ODIN but when you try to get in Download Mode, it reboots, is that it? If so, that's the first time I've heard this issue. How are you trying to enter Download Mode?
nirogu325 said:
Let me get this right: you sucessfully flashed Overcome, and want to ODIN but when you try to get in Download Mode, it reboots, is that it? If so, that's the first time I've heard this issue. How are you trying to enter Download Mode?
Click to expand...
Click to collapse
I am still with the Samsung original
I wanted to try the overcome ROM see if the lag disapears.
I am stuck in the first step when I need to flash CWR using Odin. I can't get into the download menu
josibarns said:
I am still with the Samsung original
I wanted to try the overcome ROM see if the lag disapears.
I am stuck in the first step when I need to flash CWR using Odin. I can't get into the download menu
Click to expand...
Click to collapse
I see. The Overcome thread also has the CWM Recovery as a .zip file which is flashable through Stock Recovery (same procedure as flashing Root). You just put the file in your internal SDcard and flash away. If you still have doubts, read a little bit here, as I'm sure that will clear any doubts you might have.
josibarns said:
I find my newly purchased tab 8.9 very laggy with the stock TouchWiz
Before returning it I wanted ti try the Overcome rom to see if it can get any smoother.
I carefully followed there instructions but I am unable to go past the downloading droid. once I validate with the right button volume, the tablet simply reboots.
Does anyone else have this issue?
Click to expand...
Click to collapse
u have to press the power and the left-volume button for about 15sec
nirogu325 said:
I see. The Overcome thread also has the CWM Recovery as a .zip file which is flashable through Stock Recovery (same procedure as flashing Root). You just put the file in your internal SDcard and flash away. If you still have doubts, read a little bit here, as I'm sure that will clear any doubts you might have.
Click to expand...
Click to collapse
Perfect it worked! And I was also able to install the Overcome ROM It seems to be more battery hungry and a bit faster
DonKomposto said:
u have to press the power and the left-volume button for about 15sec
Click to expand...
Click to collapse
Yes I have done that and I get to the menu with the droid blinking with "downloading" written under it. The issues is when I validate instead of showing the dowload menue it simply reboots...
josibarns said:
Perfect it worked! And I was also able to install the Overcome ROM It seems to be more battery hungry and a bit faster.
Click to expand...
Click to collapse
Don't expect perfection from a port, ever (port = a ROM that's not native to the device). The motley kernel, along with UV can help you in the battery department.
Sent from my GT-P7310
Sorry to comeback to it but after having flashed a couple or ROM with CWM I want to come back to the stock rom using ODIN and I cannot enter the dowload menu.
My system right now is a stock ROM us retail P7310UEKHA flashed with CWM and CWM and I want to install a 3.2 stock ROM using ODIN.
The way I try to access the download menu is
1. Turn off the tab
2. wait 30 sec
3. restart with the down volume pressed
4. when the reaching the menu between recovery and dowloading. Select dowloading with the down volume button and validate with the up volume button.
Result: a black screen for 3 seconds and then the tab reboots
josibarns said:
Sorry to comeback to it but after having flashed a couple or ROM with CWM I want to come back to the stock rom using ODIN and I cannot enter the dowload menu.
My system right now is a stock ROM us retail P7310UEKHA flashed with CWM and CWM and I want to install a 3.2 stock ROM using ODIN.
The way I try to access the download menu is
1. Turn off the tab
2. wait 30 sec
3. restart with the down volume pressed
4. when the reaching the menu between recovery and dowloading. Select dowloading with the down volume button and validate with the up volume button.
Result: a black screen for 3 seconds and then the tab reboots
Click to expand...
Click to collapse
A corrupt bootloader that may be. Reflash KHA (CWM version alterbridge posted) to see if it solves it.
Sent from my SGH-T959.
Just to precise this issue was present out of the box when I got it from best buy...
josibarns said:
Just to precise this issue was present out of the box when I got it from best buy...
Click to expand...
Click to collapse
flash a stock bootloader and a stock recovery using nvflash, im in a hurry now and dont have time to explain, use google, you will find all the info in the tab 10.1 forum.
lupu666ro said:
flash a stock bootloader and a stock recovery using nvflash, im in a hurry now and dont have time to explain, use google, you will find all the info in the tab 10.1 forum.
Click to expand...
Click to collapse
Thanks lupu666ro. I've tried installing stock Rom with CMW but nothing works. I have found very sparse info about nvflash. It looks like the solution but I'm a bit wary about tring this without a instructions. Could give me more info or point me to a tutorial
Thanks!
Still no luck...
So I have tried reflashing the stock US retail ROM and ran the EULA3 OTA update over it. I can't seem to figure this out.
The OTA update entered the download mode for a few seconds during the update so I am wondering if I don't simply have a locked bootloader.
I have made a video to show the problem: http://youtu.be/b09-x31ldbs
josibarns said:
So I have tried reflashing the stock US retail ROM and ran the EULA3 OTA update over it. I can't seem to figure this out.
The OTA update entered the download mode for a few seconds during the update so I am wondering if I don't simply have a locked bootloader.
I have made a video to show the problem: http://youtu.be/b09-x31ldbs
Click to expand...
Click to collapse
here is a tutorial on how to use nvflash, this will repair you tablet. http://forum.xda-developers.com/showthread.php?t=1130574
On the download warning screen you are hitting volume down, not up. Volume up is the button closest to the headphone jack..
josibarns said:
So I have tried reflashing the stock US retail ROM and ran the EULA3 OTA update over it. I can't seem to figure this out.
The OTA update entered the download mode for a few seconds during the update so I am wondering if I don't simply have a locked bootloader.
I have made a video to show the problem: http://youtu.be/b09-x31ldbs
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I957 using XDA App
neubauej said:
On the download warning screen you are hitting volume down, not up. Volume up is the button closest to the headphone jack..
Click to expand...
Click to collapse
Ok I am really ashamed on this one, you were right I've been hitting the wrong button for all my attempts
Thanks a lot neubauej!!!!!
Lol, no problem, glad it was simple.
Sent from my SAMSUNG-SGH-I777 using XDA App
Hey guys,
I just recently got a refurb Droid 3 after my old one had the backlight go out, I hand't had a chance to bootstrap it and put ICS on it. But I was able to get it rooted. I restarted my phone today and ever since it has been stuck at the M logo screen and I've tried everything I can find to remedy this.
I updated this morning to the most recent OTA update (5.7.906 I believe) and then rooted it.
To fix the issue I've tried a few different things. I tried Pete's SBF to 5.7.890 but I was getting an error about the cbt.bin file. I found that with the recent changed to 5.7.906 you aren't able to directly flash over it to go back to 5.7.890. I then found another post on here which had a script to go back to 5.7.890 from 5.7.906. I ran that and still had the same result.
Any other ideas or anything that I am missing?
I can get into fastboot, I've been using the scripts with moto-fastboot. Normal boot is just leaving me at the M logo, booting into recovery yields the same result.
Any help would be appreciated since I have no clue what else I can do at this point...
seems like a soft brick... should be fixable...
With the phone off, hold me, then the power button... then go down to BT TOOLS and select it ( volume up is the select button _ so when u do that it doesnt go to it?
try following this thread
http://forum.xda-developers.com/showthread.php?t=1336980
heres a download link
http://minus.com/lbkaxv58pO5MDp
Juicy555 said:
seems like a soft brick... should be fixable...
With the phone off, hold me, then the power button... then go down to BT TOOLS and select it ( volume up is the select button _ so when u do that it doesnt go to it?
try following this thread
http://forum.xda-developers.com/showthread.php?t=1336980
heres a download link
http://minus.com/lbkaxv58pO5MDp
Click to expand...
Click to collapse
I don't have a BT Tools selection. I do have BP Tools though. I selected it and it just sits there on the M logo as well...
I've tried a few of Pete's scripts with no luck so far (worked on the old Droid 3 when I put it back to stock before shipping it back).
Juicy555 said:
seems like a soft brick... should be fixable...
With the phone off, hold me, then the power button... then go down to BT TOOLS and select it ( volume up is the select button _ so when u do that it doesnt go to it?
try following this thread
http://forum.xda-developers.com/showthread.php?t=1336980
heres a download link
http://minus.com/lbkaxv58pO5MDp
Click to expand...
Click to collapse
Gave the one that you linked a try, get "Preflash validation failure" for Recovery and Boot.
Any other ideas?
imperpetual said:
Gave the one that you linked a try, get "Preflash validation failure" for Recovery and Boot.
Any other ideas?
Click to expand...
Click to collapse
it will not flash if your phone is not charged to at least 50%.. make sure its charged...
Juicy555 said:
it will not flash if your phone is not charged to at least 50%.. make sure its charged...
Click to expand...
Click to collapse
It is charged. When it's not charged it gives the "LOW BATTERY" error.
click the link in my signature
and follow the directions in my thread and you will be fine
you updated your phone to. 906 all of the older sbf's wont work..but mine will as it is specifically for. 906
ovelayer said:
click the link in my signature
and follow the directions in my thread and you will be fine
you updated your phone to. 906 all of the older sbf's wont work..but mine will as it is specifically for. 906
Click to expand...
Click to collapse
Your 1 Click SBF ran fine and completed without errors but I'm still getting the same result, stuck at M logo.
Is there something I could be missing which is making it not boot that most SBFs don't include? That's the only thing I can think of at this point.
imperpetual said:
Your 1 Click SBF ran fine and completed without errors but I'm still getting the same result, stuck at M logo.
Is there something I could be missing which is making it not boot that most SBFs don't include? That's the only thing I can think of at this point.
Click to expand...
Click to collapse
okay right after you use the 1click sbf
go HERE
download the. 906 update
place it on your external sdcard..
reboot into STOCK recovery and install the update
reboot
try that
ovelayer said:
okay right after you use the 1click sbf
go HERE
download the. 906 update
place it on your external sdcard..
reboot into STOCK recovery and install the update
reboot
try that
Click to expand...
Click to collapse
I'm fairly certain that could work, if I could ever get into the Stock recovery....I'm not able to boot into anything. Going to try a few other things, if nothing else works I'll just take it in and see if I can get yet another warranty replacement.
Thanks for the responses, if you have any other ideas just let me know.
I think the main thing that needs to be addressed is that I need to be able to get into recovery and then I will be set to fix it. Right now it just sits at the M logo for Recovery (and any other options from the boot menu).
Well I decided to call Google about the boot loader recovery not working as it should. I was hoping this call would help them to work on another update but they say that's the way its supposed to work. Here's the email Instructions:
1. Power down your device
2. Press and hold both volume keys and the power button to enter
Bootloader mode
3. Press the volume keys to cycle to the Recovery mode option
4. Press the power button to select Recovery mode
5. From the Recovery mode screen, press and hold the Power button then
press the Volume up button.
6. Use the volume buttons to select wipe data/factory reset.
7. Select Yes -- delete all user data.
8. The factory data reset process will now start. Once its finished,
select 'Reboot system now.'
The only option we have in the new recovery is to wipe data. Maybe for those having problems accessing twrp or cwm will be able to a access it with step 5. I don't know haven't rooted yet. So I decided to ask about nvflash and they said they're not going to release any nvflash tools or files.
um, yup. thats how stock bootloader and stock recovery work. lol
whats the issue? if your not even rooted, you wouldn't even know if you have an issue or not with the new bootloader.
Are you saying that you can't flash a different recovery? Or that when you do you still get the same stock recovery? I'm not quite sure what the issue is here, because that is exactly how the stock bootloader, and recovery are supposed to work.
Are you making sure to unlock fastboot before trying to flash recovery. I don't recall seeing or hearing anyone say anything about not being able to get to clockwork mod once its installed.
xjman said:
Are you saying that you can't flash a different recovery? Or that when you do you still get the same stock recovery? I'm not quite sure what the issue is here, because that is exactly how the stock bootloader, and recovery are supposed to work.
Are you making sure to unlock fastboot before trying to flash recovery. I don't recall seeing or hearing anyone say anything about not being able to get to clockwork mod once its installed.
Click to expand...
Click to collapse
No. I saw people posting they couldn't get go cwm and could only see the red exclamation point. And I was just saying maybe after choosing recovery then holding volume up and power it would then go to cWm or twrp. I was hoping for someone to try it who is still on 3.41 Recovery. A lot of people downgraded back to 3.39 or whatever version it was
kieso said:
I was hoping for someone to try it who is still on 3.41 Recovery. A lot of people downgraded back to 3.39 or whatever version it was
Click to expand...
Click to collapse
I can confirm that to get in to the stock recovery you hold down 'power' and then tap 'vol up'.
At present I am running the latest CWM touch recovery. This boots straight into it from the bootloader without any extra button presses.
My personal preference to go into CWM is from either QuickBoot or ROM Manager.
Sent from my Nexus 7 using xda app-developers app
smirkis said:
didn't know being informed makes me an asshole. stupid me, reading and understanding.
for what its worth, im on the newest bootloader, and selecting recovery goes straight to twrp. which is the recovery i installed.
Click to expand...
Click to collapse
I wonder why some on 3.41 can't go straight to twrp and some can. Sorry for the ahole comment I thought you were trying to be a smartass towards me. I'm just trying to find out as much info from people before I root. I am experienced at flashing and a little adb but I just read a lot of HELP BRICKED MY NEXUS posts. Did you use wugs toolkit or adb to unlock and root?
mr_tris said:
I can confirm that to get in to the stock recovery you hold down 'power' and then tap 'vol up'.
At present I am running the latest CWM touch recovery. This boots straight into it from the bootloader without any extra button presses.
My personal preference to go into CWM is from either QuickBoot or ROM Manager.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
Thanks for the info. I'm going to try unlocking and rooting when I get home. I really want to use the OTG cable and the 720p mod.
kieso said:
I wonder why some on 3.41 can't go straight to twrp and some can. Sorry for the ahole comment I thought you were trying to be a smartass towards me. I'm just trying to find out as much info from people before I root. I am experienced at flashing and a little adb but I just read a lot of HELP BRICKED MY NEXUS posts. Did you use wugs toolkit or adb to unlock and root?
Click to expand...
Click to collapse
When I first flashed TWRP onto my Nexus 7 after that official 4.1.2 OTA update, I wasn't able to boot into it. I then flashed it again via fastboot, and then booted the TWRP image that was on my computer, and then TWRP loaded.
I believe TWRP does work normally now as well (I can boot into it and reboot into it).
kieso said:
I'm going to try unlocking and rooting when I get home.
Click to expand...
Click to collapse
Well if I was you I'd just use mskips toolkit, its absolutely epic it'll save you a lot of farting around. I take it that your fully updated? ( Not that it matters) You seem to know and understand your way around adb so just go for it and enjoy.
Its works smooth as silk and save you a lot off time. The options available to you are just staggering!
http://forum.xda-developers.com/showthread.php?t=1809195
Sent from my Nexus 7 using xda app-developers app
Thread Cleaned​
No need for personal insults, lets just try to help each other out and show each other some respect.​
going to recovery from bootloader works fine after 3.41.....wat r u talkin abt? (i m stock rooted+twrp)
oh yea...u hav 2 remove that recovery stock.p file thingy first.
There are plenty of people that are having issues with recovery on 3.41 bootloader.... Its confirmed some have it some don't.
The issue is that with 3.41 bootloader on some Nexus 7 Devices a custom recovery is unbootable no matter how you try, every time it will try to load recovery and fail at a black screen then reboot into the OS. It does not matter how you try from ADB reboot to recovery or from bootloader with USB attached or not.
psycho2097 said:
going to recovery from bootloader works fine after 3.41.....wat r u talkin abt? (i m stock rooted+twrp)
oh yea...u hav 2 remove that recovery stock.p file thingy first.
Click to expand...
Click to collapse
Ohh crap I read about that in some thread. Any idea exactly what has to be done. The only way I can get into cwm is with ROM toolbox but I have to reflash cwm every time then hit boot into recovery.
kieso said:
Ohh crap I read about that in some thread. Any idea exactly what has to be done. The only way I can get into cwm is with ROM toolbox but I have to reflash cwm every time then hit boot into recovery.
Click to expand...
Click to collapse
In your system folder there's a file called 'recovery-from-boot.p'
Go into a file manager with w/r access and rename it ' recovery-from-boot.p.bak'
When the system boots it reads that file and resets the recovery to stock, by changing the name you remove the problem.
Sent from my Nexus 7 using xda app- app developers
mr_tris said:
In your system folder there's a file called 'recovery-from-boot.p'
Go into a file manager with w/r access and rename it ' recovery-from-boot.p.bak'
When the system boots it reads that file and resets the recovery to stock, by changing the name you remove the problem.
Sent from my Nexus 7 using xda app- app developers
Click to expand...
Click to collapse
Thank you for all the help! I appreciate it.
kieso said:
Thank you for all the help! I appreciate it.
Click to expand...
Click to collapse
No problem, a click on the 'Thanks' button for me and my colleagues on this thread would really make our day. :thumbup:
I hope you get sorted mate, I wouldn't be able to sleep at night until I got custom recovery working properly on any of my devices!
Sent from my Nexus 7 using xda app-developers app
i tried changing the name of the file, but.. after reboot, the tablet gets stuck on google screen, recovery never loads... any suggestion? Thanks =)