Related
[Q] Tried to install Beatmod ICS, stuck on "screensaver" usb and recovery won't work
Hi guys,
I've watched the n00b video and been googling for the last few hours as well as reading through various pages on the XDA forum. I've found a lot of problems that are kinda similar and tried various solutions but don't seem to be quite getting there.
Basically I had Virtuous Affinity as the OS and clockworkmod installed (should be the most up to date versions of both, they were put on no more than a week ago) as well. I also had a backup of current OS and so on on the SD card, as well as the original zip of the rom.
I decide I want to give ICS a go and so I downloaded the betamod ICS and then loaded it. It asked me if I wanted to do a dalvik cache wipe, a dalvik cache + data wipe and a third option I don't recall. I went with the dalvik cache wipe (at the time I was under the impression that was the correct course of action) then put it back in my pocket while ICS installed.
I get my phone out of my pocket later and it's kinda stuck on what looks like (but logically isn't, I'm guessing it was meant to be a splash screen type thing while ICS installed or some such) a screensaver which just loops endlessly. The only thing you can really do is take the battery out and turn her on again, in which case you once again end up in the endless screensaver loop.
I've tried booting to recovery using volume - and the power button and unfortunately it just boots straight into the looping screensaver again.
Getting a bit worried and feeling adventurous I tried seeing what I could do with ADB, however the computer seemed unable to recognise that any device was connected with ADB devices not listing anything.
I've read up a lot and I'm at a loss as to what to do - there's a rom on the SD card and there also should have been a backup but I just can't get it into recovery.
I do have the ability to view the SD card on another device and interact with it, so if there's a potential SD fix, that's certainly not out the window.
But yeah, I'm clueless how to proceed here and very green at the whole rom business. Can anyone advise what I might try to do from here? I don't care what state I end up going back to, or if I lose my data, I can get all that back, I just want the phone in some semblance of basic operation.
I'll be keeping an eye on the thread, if I've left out any pertinent data ask away and thanks in advance for anyone with a clue how I can fix this mess .
EDIT: Post may be better off in ICS thread above and I do apologise if so, I would move it but I seem unable to delete it.
Remove battery for 5 seconds and then try again to boot into recovery using volume -and power button.
ik222 said:
Remove battery for 5 seconds and then try again to boot into recovery using volume -and power button.
Click to expand...
Click to collapse
I have, it doesn't work. I've left the battery out for a fairly long period. Volume - + power still just brings it back to the "screensaver" loop.
Thanks for the suggestion though.
Turn the phone off completely; pull the battery out for a bit then replace it and don't touch anything. Don't try to turn it on. Plug the phone by usb to your pc (still turned off). At the command prompt in the folder containing adb.exe type "adb reboot recovery" - the phone should power on and go to recovery where you can wipe properly and reflash whatever you want.
You should be able to boot to recovery using the volume down + power button combo (hold the volume-down key, then press and hold the power button and keep both held until you get to the bootloader menu); the only thing that's wrong with your phone is that you've flashed one ROM over another without wiping it first, so the ROM can't load but this shouldn't affect your bootloader or recovery.
Worst case you can flash a RUU which will restore it to the official firmware; you'll then need to re-root and re-install a recovery image to be able to flash custom ROMs again.
Very helpful post, thanks! I'll try all that and see how I go, I'll post if I still have trouble.
Yeah I dunno why I can't boot to recovery it's weird. The volume button wasn't working, so I removed it and am pressing in the volume down portion of the volume button with a pen while holding down the power button. It's possible perhaps I'm not successfully depressing volume down, but I'm 99% sure I am and that that's not it. I am however doing it as you and other guides advise, depress volume down, hold it and then depress power and hold both for about three seconds, no joy!
Anyway, as said, I'll try what you're recommending and see how I go. Thanks!
hopscotchjunkie said:
At the command prompt in the folder containing adb.exe type "adb reboot recovery"
Click to expand...
Click to collapse
Curious what you mean by this? Cause there's no command prompt in the folder ADB is in. Do you mean in command prompt, be in the folder, i.e. c:\abd kinda thing? I tried just loading command prompt and typing abd reboot recovery, no device detected - no joy.
Ethicistabdiel said:
Curious what you mean by this? Cause there's no command prompt in the folder ADB is in. Do you mean in command prompt, be in the folder, i.e. c:\abd kinda thing? I tried just loading command prompt and typing abd reboot recovery, no device detected - no joy.
Click to expand...
Click to collapse
Yeah that was what I meant; I've got a feeling that that only works when the phone is powered off if you had USB debugging activated on the phone beforehand, so if that's not working that might be why.
c:\adb
results in error: device not found.
ADB app itself is in C:\adb\platform-tools but when I try that it goes The System cannot find the path specified. I've tried cd/adb and I can get that far but I can't get to adb/platform-tools.
EDIT:
Okay, I managed to get to c:\adb\platform-tools but adb reboot recovery is still advising error: device not found. Guessing perhaps I didn't have usb debugging enabled. Are you able to suggest another work around at all? I'm happy to flash it to whatever, I don't mind losing data, just want to get it in working order again. I don't see how I can though when I seemingly don't have access to recovery or USB...hrmm, must be some way around.
Accidental double post, sorry.
You need to try get into recovery mode, where you can do a full wipe and see if that fixes anything.
Firstly, remove your battery then re-install it, your phone should still be turned off at this stage. Press and hold the volume down button, then additionally press and hold the power butter, until something appears on the screen. If the bootloader appears, you can then boot into recovery from there.
If the above fails to work, report back with your results and hopefully something else will be suggested.
Ethicistabdiel said:
c:\adb
results in error: device not found.
ADB app itself is in C:\adb\platform-tools but when I try that it goes The System cannot find the path specified. I've tried cd/adb and I can get that far but I can't get to adb/platform-tools.
EDIT:
Okay, I managed to get to c:\adb\platform-tools but adb reboot recovery is still advising error: device not found. Guessing perhaps I didn't have usb debugging enabled. Are you able to suggest another work around at all? I'm happy to flash it to whatever, I don't mind losing data, just want to get it in working order again. I don't see how I can though when I seemingly don't have access to recovery or USB...hrmm, must be some way around.
Click to expand...
Click to collapse
Your only other option to get into recovery is the volume-down/power-on combination. Like I said, I can't think why that's not working unless it's related to your missing volume button (maybe it's not maintaining a constant pressure on the button when you're using whatever to press through the hole).
If you still can't get that to work, I would suggest finding a stock RUU and flashing that. It's an .exe file that runs from your PC and will return your ROM, bootloader and radio back to stock. Obviously that means you'll lose root and your custom recovery so you'll need to do all that again from scratch. There's a sticky in the dev section with a link to a thread with various RUUs (it's named something along the lines of "shipped & test ROMs" - I'll check that and link to it once I've dragged myself out of bed to the computer). You'll lose all your data, but if you took a backup beforehand you can restore that once you're back up and running.
//sent from my Desire HD using Tapatalk; all errors entirely intentional.
Yeah I'm starting to think perhaps the down button is just broken.
What state should the phone be for the RUU, turned off with usb plugged in or turned on? Bearing in mind, that when on, all it will do is the "screensaver". Will it work in either of those states?
Thanks, will deffo research more when I get home. Appreciate the help immensely.
http://forum.xda-developers.com/showthread.php?t=824357&page=5
Guessing you mean that as far as the ruu thread. Am downloading a stock rom atm, with shaped internet till tomorrow, meh! Will see how I go. Have a feeling phone was probably Vodafone branded at stock though, so that could make for extra fiddling but yeah, fingers crossed.
If you are able too install a stock-rom you can work from their than install 4EXT recovery
touch than you doen't need the volume buttons.
I downloaded the most recent stock rom on the link above. When I try to install it though, phone off or on, it advises a USB connection error. Is this likely to be because I originally had vodafone stock and need to make a gold card, or should it still at least be recognising it? It does advise not to run any programs on the phone or anything when while installing the update, but of course, as long as my phones turned on it's stuck on the damned screensaver loop.
http://forum.xda-developers.com/archive/index.php/t-841890.html
Gonna give that a go, fingers crossed!
D'oh, just found out my mobile was Three at stock and not Vodafone, the search continues .
Gah, I'm about tearing my hair out here, I want my damned phone back . Stuck using a $79 Huwawei Vodafone thing at the moment and it's so so so awful.
Anyway. I was under the impression that making a goldcard would mean I could RUU a non-Three stock rom on the phone. I made a goldcard following these instructions; http://www.addictivetips.com/mobile/how-to-make-gold-card-for-htc-desire-hd/
Then I turned the phone on as the RUU advises, (meaning it's scrolling through the feckin' "screensaver") and start the process and once again get a USB connection error.
What's the better process at this stage, try and take it back to Three stock? I don't see how I can at the moment, the only Three stock I can find seems to be rom, not RUU, meaning I'd need to load from the phone, which I can't due to no recovery. Or should I keep trying to get the goldcard thing to work, maybe try some different RUU's or something?
I'm open to any other suggestions as well. Had a bit more of a fiddle around with my volume down button, no matter what I do though, I can't get recovery mode. Always boots first to the white HTC screen and then starts the infernal "screensaver" loop.
Ethicistabdiel said:
Yeah I'm starting to think perhaps the down button is just broken.
What state should the phone be for the RUU, turned off with usb plugged in or turned on? Bearing in mind, that when on, all it will do is the "screensaver". Will it work in either of those states?
Thanks, will deffo research more when I get home. Appreciate the help immensely.
Click to expand...
Click to collapse
How come the volume down button be broken. When you were using Affinity Rom weren't you able to use your volume button for music. Remove SD card from phone then press "First - Volume down gently for 2 sec" & press-hold power button when it goes into bootload place your sd card back select option "REBOOT RECOVERY". I think your panicking too much just be patient nothing is wrong, i think your just hurrying it up...
The volume button didn't work before either. I had to manually adjust volume from settings. I thought it was just because of the dodgy plastic button on top, but using a pen to depress the button underneath doesn't work either.
Believe me, I've been trying to fix this for days now, every different way of depressing volume down in order to get to recovery has not worked. Short of taking the phone apart and seeing if I can see what's wrong with the button (doubtful with my level of expertise) then it ain't happening via that method.
Got a little bit hopeful with this;
http://www.htcdev.com/bootloader/ruu-downloads
But that too requires my phone to be in usb debugging mode, which of course, it isn't.
Is there anyway to force the phone into usb debugging mode using some form of hack or some such? The thing is, it is powered and everything, I can turn it on, the screen works and all that jazz and indeed the phone will charge from USB and the computer makes a noise when I plug or unplug it, the phone itself however won't do anything other than the "screensaver" ICS installation loop. I guess I'm thinking where there's life there's hope and perhaps there's some way in that state I can get it to switch debugging on, though I think I'm reaching at this point .
Ethicistabdiel said:
The volume button didn't work before either. I had to manually adjust volume from settings. I thought it was just because of the dodgy plastic button on top, but using a pen to depress the button underneath doesn't work either.
Believe me, I've been trying to fix this for days now, every different way of depressing volume down in order to get to recovery has not worked. Short of taking the phone apart and seeing if I can see what's wrong with the button (doubtful with my level of expertise) then it ain't happening via that method.
Got a little bit hopeful with this;
http://www.htcdev.com/bootloader/ruu-downloads
But that too requires my phone to be in usb debugging mode, which of course, it isn't.
Is there anyway to force the phone into usb debugging mode using some form of hack or some such? The thing is, it is powered and everything, I can turn it on, the screen works and all that jazz and indeed the phone will charge from USB and the computer makes a noise when I plug or unplug it, the phone itself however won't do anything other than the "screensaver" ICS installation loop. I guess I'm thinking where there's life there's hope and perhaps there's some way in that state I can get it to switch debugging on, though I think I'm reaching at this point .
Click to expand...
Click to collapse
The only option i can think of is "Fix your volume button from your nearest Service centre". Without that you cant do anything. I am Sorry....
First let me say I *did* try to find information before posting here. Truly.
I have a 2nd generation Kindle Fire, which keeps on looping at the stock "kindle fire" screen.
I do not know how it got into that state, this is how I got it.
Here is the setup:
1) Device is certainly kindle fire 2
2) I am running on WIndows Vista, but I can change to other Windows or Linux if necessary
3) I have a factory cable which allows me to boot into FastBoot; it is definitely the original Amazon FastBoot and not a replacement/dual boot
4) The Kindle battery is clearly low as it simply can't charge it enough. Once it charges enough it reboots, shows the "Kindle fire" logo for 2 seconds, never runs the wave through it, then shuts off and restarts again.
I could not get it to charge more than that, but I do not think this is a hardware/battery problem; I have long experience with electronics and just trust my guts here.
5) Booting into FastBoot with factory cable is OK however fastboot.exe does NOT see the device as listed. Neither does ADB.
6) Windows reports the device as "Kindle Fire" and even though FastBoot does not see it in "fastboot devices" it can still send commands to it
7) Cleaning the user data and the cache was the only thing I tried; they took a lot of time to complete (1 and 3 minutes respectively whereas articles mention 20-30 seconds), but that didn't change anything
I guess what I am trying at this stage is to re-flash the system/bootloader partitions with stock ones in hope that will allow the device to boot successfuly.
Can I do that?
Or what else can I do?
Thank you for all you do!
The main thing that I think you have wrong is this-
There is no original Amazon fast boot cable. The fastboot cable is a special cable you either buy or build NOT something Amazon gives you.
Once you are sure you have a real fast boot cable u SHOULD be able to recover fine.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
I do not think I've said I have an "original Amazon fastboot cable".
I made the cable myself and i must say it isn't a rocket science to do one if you're in electronics.
Apparently it works since it allows me to get into fastboot mode and clear cache and user data.
If there's something that may not be correct it would instead be on the driver side.
I had a hard time finding a set of drivers that would make the device recognizable.
Now the question I have is can someone who knows how to flash Android partitions, let me know if I can and how can I re-flash the partitions of this KF2?
Specifically where to find partition images and are they safe to flash or are they unique for each device out there (i.e. bound to some other unique ID of the device) or the same for the whole class of devices, e.g. all KF2 devices would have same binary partition images which can be flashed?
Supposedly and hopefully the second, but if it were so simple then restoring a Kindle to factory default state should be piece of cake and it doesn't sound like it is.
I must be missing several things.
But the cable sure isn't one of them.
kolevbg said:
I do not think I've said I have an "original Amazon fastboot cable".
I made the cable myself and i must say it isn't a rocket science to do one if you're in electronics.
Apparently it works since it allows me to get into fastboot mode and clear cache and user data.
If there's something that may not be correct it would instead be on the driver side.
I had a hard time finding a set of drivers that would make the device recognizable.
Now the question I have is can someone who knows how to flash Android partitions, let me know if I can and how can I re-flash the partitions of this KF2?
Specifically where to find partition images and are they safe to flash or are they unique for each device out there (i.e. bound to some other unique ID of the device) or the same for the whole class of devices, e.g. all KF2 devices would have same binary partition images which can be flashed?
Supposedly and hopefully the second, but if it were so simple then restoring a Kindle to factory default state should be piece of cake and it doesn't sound like it is.
I must be missing several things.
But the cable sure isn't one of them.
Click to expand...
Click to collapse
Just to clarify...
Are you no longer dealing with a low battery?
soupmagnet said:
Just to clarify...
Are you no longer dealing with a low battery?
Click to expand...
Click to collapse
Nothing has changed in regards to the low battery.
I do not the logic of its charging, but it shows the low battery battery symbol when unit is not connected.
When connected with normal cable it charges for some time (orange LED) then starts the ever-looping process during which it seems to discharge just as much as it manages to charge; I can't get it in a stable "power off" condition to just charge.
I do have means of securing a charged battery to see if it will make a difference. I do not think it will unless there is a piece of memory in the battery block itself (like with the PSPs) and that one got corrupt.
I am betting against this because unit can clearly boot in fastboot mode.
I have no idea why wouldn't it show in neither fastboot devices nor adb list though.
kolevbg said:
Nothing has changed in regards to the low battery.
I do not the logic of its charging, but it shows the low battery battery symbol when unit is not connected.
When connected with normal cable it charges for some time (orange LED) then starts the ever-looping process during which it seems to discharge just as much as it manages to charge; I can't get it in a stable "power off" condition to just charge.
I do have means of securing a charged battery to see if it will make a difference. I do not think it will unless there is a piece of memory in the battery block itself (like with the PSPs) and that one got corrupt.
I am betting against this because unit can clearly boot in fastboot mode.
I have no idea why wouldn't it show in neither fastboot devices nor adb list though.
Click to expand...
Click to collapse
We can deal with the connection issue later. Right now, you need to get your device charged. The best way to do that, is plug it in to a power source, and hold the power button until it shuts down. If it powers down and stays off, leave it plugged in for a few hours. That should take care of the charging problem.
Also, 'fastboot devices' doesn't work, so if you're expecting to get a response from it, you'll be waiting a long time. Instead, issue 'fastboot -i 0x1949 getvar product', then plug your device (still powered down) into the computer and let it boot on it's own. If your drivers are working properly, you should see the word "kindle" show up in the command prompt after a few seconds. Otherwise, it will just sit at "waiting for device" and do nothing. Then you'll need to either fix your drivers or try alternative methods (Linux).
kolevbg said:
I do not think I've said I have an "original Amazon fastboot cable".
Click to expand...
Click to collapse
kolevbg said:
3) I have a factory cable which allows me to boot into FastBoot; it is definitely the original Amazon FastBoot and not a replacement/dual boot.
Click to expand...
Click to collapse
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mindmajick said:
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I think he's talking about the bootloader and fastboot itself, not the cable, but I see where you would get that.
soupmagnet said:
I think he's talking about the bootloader and fastboot itself, not the cable, but I see where you would get that.
Click to expand...
Click to collapse
I get that now lol. But I couldn' let it go
Let me know if he can't get the image. I still have them saved on my hd and can upload them if necessary. I just have really slow DSL for uploads.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mindmajick said:
I get that now lol. But I couldn' let it go
Let me know if he can't get the image. I still have them saved on my hd and can upload them if necessary. I just have really slow DSL for uploads.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
Compressing for upload now.
Will upload soon and open a thread in the dev section
Edit: uploading now. Eta- 2.5 to 3 hrs
--
Sent from my mind to your screen.
Yes I was talking about the fastboot and not the cable.
But I agree I could have said it better.
In threads I read people always ask which fastboot is installed so I focused on answering that.
Can the Kindle charge *without* the orange LED being on indicating charge?
I think I can't get this particular device charge its battery, but as I indicated I have means of securing a charged battery (for the record, by simply charging it on a working device).
Will try the suggested 'fastboot -i 0x1949 getvar product' when I get back in town Sunday and report.
Can you guys please clarify if flashing back stock partitions can be done without superuser rights, i.e. hacking?
My understanding is that it is not possible for all partitions.
And that to make it possible I need ADB in orderto implement a hack and get su rights.
Is that correct?
kolevbg said:
Yes I was talking about the fastboot and not the cable.
But I agree I could have said it better.
In threads I read people always ask which fastboot is installed so I focused on answering that.
Can the Kindle charge *without* the orange LED being on indicating charge?
I think I can't get this particular device charge its battery, but as I indicated I have means of securing a charged battery (for the record, by simply charging it on a working device).
Will try the suggested 'fastboot -i 0x1949 getvar product' when I get back in town Sunday and report.
Can you guys please clarify if flashing back stock partitions can be done without superuser rights, i.e. hacking?
My understanding is that it is not possible for all partitions.
And that to make it possible I need ADB in orderto implement a hack and get su rights.
Is that correct?
Click to expand...
Click to collapse
1) Yes, the device can (and does) in fact charge from a powered off state with no LED.
2) You can flash stock partitions back to the device without root in fastboot mode.
3) This (fastboot) is available for each of the partitions you need to restore (system, recovery, boot), and there should be no reason to use ADB to restore your partition images.
Also, to answer your previous questions...
There is nothing "safe" about flashing a bootloader, especially on the 2nd generation devices. A sudden power surge, sudden loss of power, Blue Screen of Death, accidentally unplugging the usb cable at the wrong time, flashing the wrong image, flashing an image that has been corrupted, or flashing the wrong image entirely, will absolutely brick your device...permanently. Make sure you pay attention, be careful...and it probably wouldn't hurt to hold your breath.
And as long as you have stock partition images for your build (KF2, KFHD7, KFHD8.9) they will work on your device. There is no user specific digital signatures for the partitions, and each partition will have the same digital signature as the other partitions for the same build. Just be sure and check the md5sum to confirm your downloads haven't been corrupted.
http://forum.xda-developers.com/showthread.php?p=43569633
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
soupmagnet said:
We can deal with the connection issue later. Right now, you need to get your device charged. The best way to do that, is plug it in to a power source, and hold the power button until it shuts down. If it powers down and stays off, leave it plugged in for a few hours. That should take care of the charging problem.
Also, 'fastboot devices' doesn't work, so if you're expecting to get a response from it, you'll be waiting a long time. Instead, issue 'fastboot -i 0x1949 getvar product', then plug your device (still powered down) into the computer and let it boot on it's own. If your drivers are working properly, you should see the word "kindle" show up in the command prompt after a few seconds. Otherwise, it will just sit at "waiting for device" and do nothing. Then you'll need to either fix your drivers or try alternative methods (Linux).
Click to expand...
Click to collapse
'fastboot -i 0x1949 getvar product' returns
product: Otter2-Prod-04
finished. total time: 0.017s
'fastboot devices'
still doesn't return anything.
What is the recommended course of action?
Should I try to reflash with the files from mindmajick or should I try to burn and learn linux until I get 'fastboot devices' to actually return usable information?
Also I do understand the concept of "not being such a thing as a safe flashing".
I also understand how it is even more difficult in systems which at hardware level prevent booting from partitions with invalid header chechsum even though I am not familiar where the header stays and what other information it contains. It's better, but not really required to know the in-depth details to understand the concept.
At the end of the day, though, flashing is the only option and it seems a big part of fastboot's functionality is to provide it.
And if I brick a device because a cable moved or battery died that's OK.
What I don't want to brick device for is doing something I do not quite understand , e.g. not following proper order of flashing (if one exists) or flashing improper image and other actions that can make me feel stupid.
Loose cables, power surges, children and pets...are part of life you just have to take as it comes
Did I say "kindle"? I meant " Otter2-Prod-04". But, whatever....it works.
The 'fastboot devices' command won't work, so don't waste your time with it. Just flash stock system, recovery, and boot images and maybe even the u-boot from the 2nd bootloader thread and you will be good to go.
Personally, I would be wary of the images posted by mindmajik because he isn't 100% sure if they are for the KF2 or not, and flashing images from a different device will probably ruin your day.
soupmagnet said:
Did I say "kindle"? I meant " Otter2-Prod-04". But, whatever....it works.
The 'fastboot devices' command won't work, so don't waste your time with it. Just flash stock system, recovery, and boot images and maybe even the u-boot from the 2nd bootloader thread and you will be good to go.
Personally, I would be wary of the images posted by mindmajik because he isn't 100% sure if they are for the KF2 or not, and flashing images from a different device will probably ruin your day.
Click to expand...
Click to collapse
Um. Yes I am. It's for the kf2 and I've flashed them myself. Just not sure of the version. Not sure how you got that impression.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
mindmajick said:
Um. Yes I am. It's for the kf2 and I've flashed them myself. Just not sure of the version. Not sure how you got that impression.
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
Click to expand...
Click to collapse
I see. I must have misunderstood you.
I probably wasn't clear lol
Sent from my SAMSUNG-SGH-I727 using Tapatalk 2
success!
Well first of all thank you again to everyone who answered one way or another to my questions.
I want to thank soupmagnet for the detailed answers and mindmajick for the upload and following up with the thread so that I didn't have to ask more questions with clarifications.
Don't know what you guys do for living, but when I was a full time software developer I have to admit I was spending a lot of time improving my own software, a little less helping my own customers and definitely less (than you are) helping others.
So hats off to you for what you do here and I say that with the full understanding that all the information I needed is practically free out there and you are just serving spoiled brads like me who are too lazy to dig it themselves.
Recovering the looping KF2 was as easy as making a factory cable, waiting out on the KF2 to charge and running mindmajick's bat file...I mean it can't get much simpler than that, can it?
But it raises the logical question: instead of going through stack overflow planting, twarp installation etc. can't I just please get a zip with bins that I can flash and end up with a fresly rooted device with proper dual boot, factory etc?
I thought this would be the way CyanogenMod works, but apparently not, at least from the two videos I watched.
Anyway, I should be able to just run by the standard guides from here...thanks again!
On a side note one of the two devices I have definitely has a bad USB port. I see they go for $20 on eBay and that's a shame, so I spent a little time and ordered from elsewhere for $2 a piece alternatives. As I mentioned I am now in electronics so I have good hopes they'll fit the bill even though not being exact same as the originals (nor are the ones on eBay it seems).
If you ever need one you can ping me in August when I would have already tried them.
I'm an IT support guy. Run my own business..
Plus I'm weird. I get off on helping others
Not sure why soup is so helpful but he's definitely a great dude.
Thanks for the REAL thanks BTW.
--
Sent from my mind to your screen.
Yes, i searched not only here, i did in the whole internet before.
I have a problem with my nearly new Nexus 7 2013 Wifi model.
First the story hat happened, maybe it has to do with it:
I bought it in August and now updated it to the last version, 4.4.2 Kitkat.
All was fine, i never had any problems until 2 days ago. I saw that the battery was running out but since it was night i let it be. In the morning i heard the sound for an empty battery for the last time, but i didnt check screen. After 20 minutes i looked at the screen and saw the Google-letters only. It didnt respond to the Power button beeing pressed so i thought the battery is too empty to let the device start and decided to plug it to the charger.
Just now i saw that the cable was not plugged in the charger, it was plugged in the PC instead, connected to an USB port (of course). As soon as i saw it i plugged out the cable from PC-USB and put it into the charger. Im afraid this wasnt good. Not sure what happened here exactly.
Now the problem
Anyway, nothing happened after plugging into charger, the Google letters where there but no symbol that the battery is loaded or anything. I thought ok, maybe thats normal if battery fully dry so i let it charge for at least 3 hours. I saw a symbol now and it showed the battery 80% full. Now i tried to start the device but nothing at all happened. Still the Google letters showed up and not more. I know about the fastboot menu (power+volume down) and did that. The fastbook menu shows up and i can select all kind of things like "Start", "Restart bootloader", "Recovery" and "Shut off". Following things happen when i press them:
1. Start > 1 second after pressing start the Google letters show up and nothing happens anymore, no X, nothing
2. Restart bootloader > bootloader restarts (works also over tools like Nexus 7 Root Toolkit, i can restart here too)
3. Recovery > same as 1., the Google letters show up, not more.
4. Shut off > Device shuts off
Now im also developing for Android and that means i have SDK and drivers and all that iinstalled. And it worked always, i could push an app to the device over ADP etc. That just as a side note.
So now i tried to unlock the bootloader to flash my own one, with fastboot. When i enter "fastboot oem unlock" it is stuck right at the first point, wipe userdata. The device has an id so the drivers are ok i think. I just cannot erase the userdata. This will stay like this until i power of the device. Then it continues and says "failed".
The real question
Now without to be able to continue past this im not able to flash anything, if im correct yes.? So do you think this is a hardbrick? Are there other options?
Thanks for any help and tipps, im really out of options.
Btw, exactly same behaviour i have with tools like Nexus Root Toolkit or any, fastbook cannot erase user-data on bootloader and stuck
Saenchai said:
Yes, i searched not only here, i did in the whole internet before.
I have a problem with my nearly new Nexus 7 2013 Wifi model.
First the story hat happened, maybe it has to do with it:
I bought it in August and now updated it to the last version, 4.4.2 Kitkat.
All was fine, i never had any problems until 2 days ago. I saw that the battery was running out but since it was night i let it be. In the morning i heard the sound for an empty battery for the last time, but i didnt check screen. After 20 minutes i looked at the screen and saw the Google-letters only. It didnt respond to the Power button beeing pressed so i thought the battery is too empty to let the device start and decided to plug it to the charger.
Just now i saw that the cable was not plugged in the charger, it was plugged in the PC instead, connected to an USB port (of course). As soon as i saw it i plugged out the cable from PC-USB and put it into the charger. Im afraid this wasnt good. Not sure what happened here exactly.
Now the problem
Anyway, nothing happened after plugging into charger, the Google letters where there but no symbol that the battery is loaded or anything. I thought ok, maybe thats normal if battery fully dry so i let it charge for at least 3 hours. I saw a symbol now and it showed the battery 80% full. Now i tried to start the device but nothing at all happened. Still the Google letters showed up and not more. I know about the fastboot menu (power+volume down) and did that. The fastbook menu shows up and i can select all kind of things like "Start", "Restart bootloader", "Recovery" and "Shut off". Following things happen when i press them:
1. Start > 1 second after pressing start the Google letters show up and nothing happens anymore, no X, nothing
2. Restart bootloader > bootloader restarts (works also over tools like Nexus 7 Root Toolkit, i can restart here too)
3. Recovery > same as 1., the Google letters show up, not more.
4. Shut off > Device shuts off
Now im also developing for Android and that means i have SDK and drivers and all that iinstalled. And it worked always, i could push an app to the device over ADP etc. That just as a side note.
So now i tried to unlock the bootloader to flash my own one, with fastboot. When i enter "fastboot oem unlock" it is stuck right at the first point, wipe userdata. The device has an id so the drivers are ok i think. I just cannot erase the userdata. This will stay like this until i power of the device. Then it continues and says "failed".
The real question
Now without to be able to continue past this im not able to flash anything, if im correct yes.? So do you think this is a hardbrick? Are there other options?
Thanks for any help and tipps, im really out of options.
Btw, exactly same behaviour i have with tools like Nexus Root Toolkit or any, fastbook cannot erase user-data on bootloader and stuck
Click to expand...
Click to collapse
Did you try using NRT and check device unresponsive or whatever it is on the right hand side? Option is normal and bootloop or something like that?
hkgrob said:
Did you try using NRT and check device unresponsive or whatever it is on the right hand side? Option is normal and bootloop or something like that?
Click to expand...
Click to collapse
No, because i thik i have to unlock the bootloader fist to do that, or not?
Edit: Yes it is like that. Cannot flash roms without unlocking bootloader first. It gets stuck and command line shows error after "boot" command > bootloader locked.
I cannot do anything in ADB, only fastboot-menu (Advanced Utilities > Launch). But btw, i found this here, im just a bit afraid to use it. Rooting/flashing Roms WITHOUT unlocked bootloader and ADB
http://forum.xda-developers.com/showthread.php?p=43993722
This is a long shot, but you said you're developing for Android. Any other devices? What drivers are you using? I use these. http://developer.android.com/sdk/win-usb.html
What happens if you try "fastboot devices"?
What happens when you run fastboot erase cache
Sent from my Nexus 6 using Tapatalk 4
Pandae said:
This is a long shot, but you said you're developing for Android. Any other devices? What drivers are you using? I use these. http://developer.android.com/sdk/win-usb.html
What happens if you try "fastboot devices"?
Click to expand...
Click to collapse
Yes i use that ones, from latest SDK. But i also tried others by now, its all the same.
fastboot devices shows me an id like:
04e7df fastboot
xdhall said:
What happens when you run fastboot erase cache
Sent from my Nexus 6 using Tapatalk 4
Click to expand...
Click to collapse
Wow this one bugs me.... it shows i dont have a partition table anymore...
FAILED <remote: Partition table doesnt exist>
What the hell, as i said, i did NOTHING exactly, how can a partition table be erased from a device that a battery runs dry? You have to know that im one that takes extremley care what apps i install, there are basically only apps from well know devs, like Dropbox, ES File Explorer, Flipboard and Google Apps (non root as i said). Or what should that warning tell me?
And the best of all is, the shop where i bought it doesnt want to change it, they want to send it in (its one month old). And they told me already that due to christmas it can take up to a MONTH until i get it back. In a month im not in this country anymore, i move back to Bangkok, so what can i really do now.... I hate it.
Saenchai said:
Wow this one bugs me.... it shows i dont have a partition table anymore...
FAILED <remote: Partition table doesnt exist>
What the hell, as i said, i did NOTHING exactly, how can a partition table be erased from a device that a battery runs dry? You have to know that im one that takes extremley care what apps i install, there are basically only apps from well know devs, like Dropbox, ES File Explorer, Flipboard and Google Apps (non root as i said). Or what should that warning tell me?
And the best of all is, the shop where i bought it doesnt want to change it, they want to send it in (its one month old). And they told me already that due to christmas it can take up to a MONTH until i get it back. In a month im not in this country anymore, i move back to Bangkok, so what can i really do now.... I hate it.
Click to expand...
Click to collapse
That confirms it. You're beyond my help. I'm fairly certain there's a way to unbrick from where you are. You'll just need someone with more experience than I have.
Sent from my Nexus 6 using Tapatalk 4
Saenchai said:
Yes i use that ones, from latest SDK. But i also tried others by now, its all the same.
fastboot devices shows me an id like:
04e7df fastboot
Click to expand...
Click to collapse
Fastboot appears to be working fine, but this is a bit of a problem. Let's hope this works to recreate:
fastboot oem part-add cache:552
I'm not sure if the 2013 N7 auto-resizes or if it's really this size, but 552 megs is size right now on mine.
What about using fastboot to erase the others?
fastboot erase boot
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Pandae said:
Fastboot appears to be working fine, but this is a bit of a problem. Let's hope this works to recreate:
fastboot oem part-add cache:552
I'm not sure if the 2013 N7 auto-resizes or if it's really this size, but 552 megs is size right now on mine.
What about using fastboot to erase the others?
fastboot erase boot
fastboot erase recovery
fastboot erase system
fastboot erase userdata
Click to expand...
Click to collapse
Not sure why my last post wasnt posted (or got deleted?) but i commented here already yesterday.
As i saw in abother post here there are many others with the same problem, and most times it happened same way too > battery run dry and this is the result, like mine.
Any command in fastboot fails sadly. I did send it in now... guess its really hardbricked from just an empty battery.
Saenchai said:
Not sure why my last post wasnt posted (or got deleted?) but i commented here already yesterday.
As i saw in this post (and a few others) there are many others with the same problem, and most times it happened same way too > battery run dry and this is the result, like mine.
Any command in fastboot fails sadly. I did send it in now... guess its really hardbricked from just an empty battery.
Click to expand...
Click to collapse
I have found that disconnecting the battery terminal clip (yes you must remove the back cover, which is easy, no tools needed & no seals broken) & then after 5 minutes, if you plug the battery back in (the battery, not the power cord), it fixes a whole bunch of issues like this. In doing this to mine, I also discovered my screen/digitizer ribbon cable was loose, causing touch screen 7 display issues galore.
At any rate, since doing this to mine, no issues.
GSLEON3 said:
I have found that disconnecting the battery terminal clip (yes you must remove the back cover, which is easy, no tools needed & no seals broken) & then after 5 minutes, if you plug the battery back in (the battery, not the power cord), it fixes a whole bunch of issues like this. In doing this to mine, I also discovered my screen/digitizer ribbon cable was loose, causing touch screen 7 display issues galore.
At any rate, since doing this to mine, no issues.
Click to expand...
Click to collapse
Thank you very much for this tip. I heard of it but was afraid that it would break seals. I will keep this in mind should i have another problem like this.
The device is now send to repairs. i hope to get it back soon...
Good luck! Sorry we couldn't give you a working remedy to do yourself.
Hi All,
Apologies if this has already been covered somewhere but I've been scouring the internet for most of the day and come up with nothing.
tldr: My Pixel 6 Pro has been running absolutely fine for 9 months, no issues what so ever through all the automatic updates, I powered it off this morning to apply a new screen protector went to turn it back on and its been stuck in fast boot since with every option that can be selected returning to the same screen. Not been fiddled with, no root nor boot loader unlock.
Simply turned it off put the screen protector on turned back on and it has been stuck in fast boot ever since with a list of things below I have tried;
Restarted, no change straight back to fastboot.
Recovery Mode, no luck same as 1.
Rescue mode and using googles update/repair tool, cannot connect result is the same as number 1.
Restart bootloader, no luck same as 1.
Flashed barcode setting on and off (i know), device state & NOS Production some times change see non error image.
Flashing via android flash tool, boot loader locked wont allow. 'error getting device locked state -1'
Using force options confirms bootloader needs unlocking.
Connected to fastboot.exe on pc.
fastboot devices, correctly recognises the device is connected.
fastboot set_active a, FAILED (remote: 'error getting device locked state -1') message.
fastboot set_active a --force, same as above.
fastboot set_active other, same as above
fastboot reboot --slot a, accepts command with slower restart than normal but reverts to b.
fastboot getvar all, works list in attachments if its is of any interest.
Details of the device,
Contract device from O2 so probably vendor locked.
Was working fine but the past week or so there have been occasions where it wouldn't accept a correct pin, then would after about 5-6 attempts then be fine some time. I didn't pay it too much thought at the time as nothing seemed off and fingerprint was always fine but seems more relevant now.
I'm not enrolled for the beta.
I haven't tried to root or unlock the bootloader.
For the first time I've been pretty boring with a phone and haven't fiddled with a thing.
I don't think I've even had the dev options menu opened on it.
I refuse to believe its bricked itself for no apparent reason but google seems to be failing me or I must be looking for the wrong thing. There must be something I can do via fastboot surely given that it has got some form of communication?
If anyone has any further suggestions it would be much appreciated before I go down the return/replace route.
I assume you didn't have OEM Unlocking enabled before this happened. Without an unlocked bootloader, there is nothing you can do to fix it, because the bootloader will reject any of the necessary commands to reflash the device. If you're still under warranty, seek warranty repair; this is going to require replacing the mainboard, because no one has the necessary tools to perform a low level reflash.
If the bootloader was unlocked, fixing this would be fairly simple because you'd just have to reflash the boot image. But, as I described above, a locked bootloader rejects all the commands that would help in this situation, and there is no way to unlock the bootloader if OEM Unlocking was not enabled.
dch29 said:
Hi All,
Apologies if this has already been covered somewhere but I've been scouring the internet for most of the day and come up with nothing.
tldr: My Pixel 6 Pro has been running absolutely fine for 9 months, no issues what so ever through all the automatic updates, I powered it off this morning to apply a new screen protector went to turn it back on and its been stuck in fast boot since with every option that can be selected returning to the same screen. Not been fiddled with, no root nor boot loader unlock.
Simply turned it off put the screen protector on turned back on and it has been stuck in fast boot ever since with a list of things below I have tried;
Restarted, no change straight back to fastboot.
Recovery Mode, no luck same as 1.
Rescue mode and using googles update/repair tool, cannot connect result is the same as number 1.
Restart bootloader, no luck same as 1.
Flashed barcode setting on and off (i know), device state & NOS Production some times change see non error image.
Flashing via android flash tool, boot loader locked wont allow. 'error getting device locked state -1'
Using force options confirms bootloader needs unlocking.
Connected to fastboot.exe on pc.
fastboot devices, correctly recognises the device is connected.
fastboot set_active a, FAILED (remote: 'error getting device locked state -1') message.
fastboot set_active a --force, same as above.
fastboot set_active other, same as above
fastboot reboot --slot a, accepts command with slower restart than normal but reverts to b.
fastboot getvar all, works list in attachments if its is of any interest.
Details of the device,
Contract device from O2 so probably vendor locked.
Was working fine but the past week or so there have been occasions where it wouldn't accept a correct pin, then would after about 5-6 attempts then be fine some time. I didn't pay it too much thought at the time as nothing seemed off and fingerprint was always fine but seems more relevant now.
I'm not enrolled for the beta.
I haven't tried to root or unlock the bootloader.
For the first time I've been pretty boring with a phone and haven't fiddled with a thing.
I don't think I've even had the dev options menu opened on it.
I refuse to believe its bricked itself for no apparent reason but google seems to be failing me or I must be looking for the wrong thing. There must be something I can do via fastboot surely given that it has got some form of communication?
If anyone has any further suggestions it would be much appreciated before I go down the return/replace route.
Click to expand...
Click to collapse
Kind of sounds like a stuck hardware button, either power and volume that's makes the phone think you are holding down buttons during boot to get into bootloader
Can you press the power button to start the system? If not, try this (it may be useful, but it may get worse, please be cautious) Hold on power button and volume down at the same time for 45s, When you press 30 seconds, the screen should turn off and restart to this interface. Then do it again as above, when it restarts to the interface again, try to press the power button to enter the system.translate form Chinese(simplified)_Google
Juuuuune said:
Can you press the power button to start the system? If not, try this (it may be useful, but it may get worse, please be cautious) Hold on power button and volume down at the same time for 45s, When you press 30 seconds, the screen should turn off and restart to this interface. Then do it again as above, when it restarts to the interface again, try to press the power button to enter the system.translate form Chinese(simplified)_Google
Click to expand...
Click to collapse
Thanks but no change sadly, still completely booked.
Hi to all, yesterday I tried to root my phone following a guide here on XDA Developers (I don't remember which one). I have a Pixel 6 Pro and I tried to flash boot.img when the phone, after being restarted, starts to bootloop and then I try to turn it off. Then, the panic. The phone doesn't seem to be recognizable by ADB nor fastboot and the screen is permanently black. When I try to hold Power button and other combinations (while plugged to my PC) Windows emits some system sounds like "plugged" or "unplugged device" but I can't find my phone like recognizable.
Phone isn't hardbricked, but softbricked.
Re-flash Stock ROM.
xXx yYy said:
Phone isn't hardbricked, but softbricked.
Re-flash Stock ROM.
Click to expand...
Click to collapse
I can't interact with phone, I just see "Pixel ROM Recovery" on devices when I connect to my PC. I don't even know if it's in recovery, if it's on or off
You might be better off if this thread was moved to the Pixel 6 Pro forum -- I can move this if you request.
But determining if you can get into Fastboot/Bootloader Mode will determine whether this is soft-bricked or not; whether this is recoverable on your end or you'll have to bring it to Google/repair shop. At this point, the only way to get into that mode is through the button combinations -- I've seen some instances where user had to hold the button combination for 1-2 minutes before it popped up; and obviously the device will need to have sufficient battery charge...
simplepinoi177 said:
You might be better off if this thread was moved to the Pixel 6 Pro forum -- I can move this if you request.
But determining if you can get into Fastboot/Bootloader Mode will determine whether this is soft-bricked or not; whether this is recoverable on your end or you'll have to bring it to Google/repair shop. At this point, the only way to get into that mode is through the button combinations -- I've seen some instances where user had to hold the button combination for 1-2 minutes before it popped up; and obviously the device will need to have sufficient battery charge...
Click to expand...
Click to collapse
If you could move it to Pixel 6 Pro forum I'd be grateful, btw idk if I can reboot into bootloader. In fact I would like to know if I can. I tried to read this https://forum.xda-developers.com/t/...evices-with-deleted-bootloader-sboot.3573865/ but I can't understand many things. So if you know how to repair it, I would be very grateful
Chexet48 said:
If you could move it to Pixel 6 Pro forum I'd be grateful, btw idk if I can reboot into bootloader. In fact I would like to know if I can. I tried to read this https://forum.xda-developers.com/t/...evices-with-deleted-bootloader-sboot.3573865/ but I can't understand many things. So if you know how to repair it, I would be very grateful
Click to expand...
Click to collapse
First and foremost is seeing if you can get to Fastboot/Bootloader Mode; When your device is off and not connected to anything (at all, no cord connecting to PC or power plug or anything), hold the Power & Volume+Down buttons simultaneously for up to 2 minutes. If you cannot power on into this mode, you will not be able to flash your device's stock firmware to re-establish any system data that may have been corrupted. It is unlikely, but you may have other options if you can boot into Recovery Mode or somehow into the OS, but if you cannot get into Fastboot Mode, it is too unlikely that you would be able to boot into these. But if you are successful into loading Bootloader/Fastboot Mode...
There's two ways i would suggest you go about it...The first and easiest is to run the official Google Android Flash Tool -- You should be able to load up the latest factory firmware version for your device (Raven), and it should be able to flash the factory image onto your phone to get it working; BE SURE to check the "keep data" (or do not wipe; I can't recall off the top of my head) and to flash to both slots (just to be safe). The second way is to follow THIS GUIDE (as directed by roirraW "edor" ehT's Pixel 6 Pro guide who holds the defacto quintessential central guide in the Pixel 7 Pro forum in which is most up to date, but not catered to "raven") -- specifically you will find what is needed in the "Update and Root Factory Image" section; play close attention to the method using the "flash-all.bat" as that is the simplest and most straightforward way to go about it.. Please read everything and place close attention on being sure to go about it without "wiping" your device (removing the "-w" in the flash-all.bat file), else if you are able to recover your system, your data will not be there when coming back to it and everything would be factory reset.