Related
So, hey guys, i've used this site a lot in the past, but now i need some help / advice, so i've registered. The following isn't going to be pretty but i'll explain it as best as i can.... infact, i can paste the email i sent to Sony asking for advice, it was this morning, i don't know if they operate or care
Hello people at Sony, my stupid head appears to have bricked my Xperia Arc S Android phone, it was still under warranty until i decided to unlock the bootloader, then i was having trouble restoring it back to stock android, this resulted in me trying to lock the bootloader. But alas, nothing now happens except a lonely green light flashing every so often, if i hold down menu, a blue light appears, which is charming, but then it dissipates and im left lonely again. With just a bricked phone and little dignity.
What are my options, by rules, it's void of warranty, can it be fixed? Can i pay for it to be fixed? Will my Natwest Insurance cover it on the grounds of Accidental damage (My stupidity) and Breakdown due to electrical fault, that being, no electrical softwareness is been transitorized.
I decided to go custom due to the wait for the Xperia update for my phone, out of the 273 S-I variant versions of the Arc S, 246 have gotten the update, but not mine, months had gone by, day turned to night, night turned to day, and i got desperate, i decided to root... for the first time. (And now last)
What i did learn, apart from technology will rise up and defeat us all, is JellyBean works very well to some degree on this phone, HOWEVER, the lack of Flash player caused bad results when playing content, im not sure what piece of code on the JellyBean CM10/Paranoid Android release was rendering it, but if you can get past the lack of flash for this and render images in its mobile bravia engineness then it will work a treat, and i mean it, it really did run well, obviously it was customness, but i digress...
Can anything be done? I do so love my Arc S, and just so you know, if it can't be repaired and I have to change phones, it will still wear the brand logo... Sony Ericsson... and if its your newer phones, that lack Eric's Son, i shall scribe his name proudly across the top with a sharp implement with pride. (With the care of an Adult, or someone equally minded)
Thank you lovely people over at Sony.
Stuart Herrington
Click to expand...
Click to collapse
So, basically it doesnt boot, apart from it does vibrate with button holds and the LED flashes. I tried flashing it with flashtool and stock ROM, but flashtool came back saying it needed unknown sources and debugging mode activated, which makes me think, it could be salvagable and not bricked, however how can i change those settings if i can't get into the phone itself, is there a bypass?
On a side note, i can Hold Menu, plug the phone into my computer and it goes into blue light mode, i cant remember the term for this
but its what i was using for flashboot, you reckon i could flashboot out of this? I was trying so many different methods to try and custom rom my phone that everything got confusing, which was best to use etc, and on another note the phone never booted when i tried to relock it, so im unaware if it finished, it didnt boot at all, and this is the point im at now.
Fortunately i picked up a Xperia U for £135, second hand, actually cheaper than my Arc S second hand, crazy really, but you can see why with the size difference and a couple of small spec differences.
Any help would be appreciated. This isn't obviously the best situation but i'm wondering if anyone has encountered this stupid mistake i've cast upon myself XD
Thanks in advance.
Wait...
I've checked the fastboot status of my phone using Flashtools, and it says my phone needs to be rooted first... hmmm it was rooted, maybe it got undone with the bootloader thing, i guess i can try but i can't access the phone to debugg or allow unknown sources.
Hi Stu15,
The fact that you can boot holding down the menu button is good.
You can probably flash a custom kernel onto your phone this way using the following command.
Code:
fastboot flash boot boot.img
If you have a rom that you want to use, then it usually comes with a custom kernel (called boot.img most of the time) inside the rom's zip file.
Most custom kernels have CWM recovery built-in, and here's the trick to enter recovery -
After you turn on the phone, wait for the hardware keys to light up.
Just in case you miss this, the coloured led will light up purple at the same time
When this happens, press (and release) the "volume down" button once or twice.
Then you should see CWM recovery in a few seconds.
So what you do is copy the rom to your sd card (just plug the card into your computer to do this).
Then flash the custom kernel that came with the rom.
Then boot into CWM and flash the rom (you should clear the cache and the dalvik cache before flashing the rom).
If you don't have a preferred rom, then have a look at this thread - http://forum.xda-developers.com/showthread.php?t=1653188
It has lotd of helpful links, near the bottom of the 1st post are a few roms you can try.
I hope that you come right.
Take care,
Hotfingers
Thanks for the info, ive tried this and apparently my phone isnt rooted anymore, it must've locked itself why i tried to undo the rom install, my recovery wasnt working so i was left with little choice. I can try and root the phone but i dont think it will be possible without accessing debugging mode, which is in the phone.. doh
im going to try adb commands to try and work something, then insurance claim. woop :/ lol
[EDIT] IM BACK, im in lol, i managed to find the command to unlock the bootloader, so now im back into CWM, the problem is the recovery doesnt work, so im reinstalling the original package, go into the phone, usb debugging and unknown sources, then i will flash it with stock ROM, should work. best work, i dont know why i did this in the first place... guess i had to learn XD
stu15 said:
Thanks for the info, ive tried this and apparently my phone isnt rooted anymore, it must've locked itself why i tried to undo the rom install, my recovery wasnt working so i was left with little choice. I can try and root the phone but i dont think it will be possible without accessing debugging mode, which is in the phone.. doh
im going to try adb commands to try and work something, then insurance claim. woop :/ lol
[EDIT] IM BACK, im in lol, i managed to find the command to unlock the bootloader, so now im back into CWM, the problem is the recovery doesnt work, so im reinstalling the original package, go into the phone, usb debugging and unknown sources, then i will flash it with stock ROM, should work. best work, i dont know why i did this in the first place... guess i had to learn XD
Click to expand...
Click to collapse
cool, well done. :good:
Hello,
just some hours ago my Galaxy Nexus (SC-04D) rebooted while lying on the table next to me. After several sings of vibration I noticed that the phone doesn't boot completely.
When switching on the phone I get the turn-on-vibration, then the google letters are displayed. Most times the word "google" flickers from left to right over the screen (only the line where the word is supposed to be). Sometimes it boots further and I get the colored "X" displayed. This symbol starts flickering, too and if it went so far it reboots.
Here are two pictures I took from the phone failing to boot:
picpaste.com/img_0001_01-Rmm7kDYb.jpg
picpaste.com/img_0001-eoLqVoiM.jpg
The phone is running stock Android from Docomo. The phone is about 14 months old and has never been unlocked, rooted, modded, taken a bath, ... 'til now.
I tried starting with and without SIM-card, with and without charger attached and let it lie around for several minutes without battery between my tries.
Is there any chance to get my data from the phone or even get it fixed? Please give me a hint what I can do.
Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix. This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery
Thanks GPFboy for your fast response,
GPFboyJS said:
Well the Red exclamation mark means that there is a problem with the phone reading the build path. Since you have never rooted the phone, this would mean that the files got corrupt on the phone. With a non-rooted phone a Factory Reset is about the only solution, but is probably only a temporary fix.
Click to expand...
Click to collapse
As far as I understand a factory reset results in a complete loss of data on the phone, right? So without root/unlock there's no chance to get my data from the phone? That would be really bad.
GPFboyJS said:
This is most likely caused by too many apps on the phone and it just freaked out on something eventually.
Click to expand...
Click to collapse
What is "too many"? I think there are about 35 apps installed atm. By the moment the problem arose wifi and 3g-data,BT,GPS were disabled and just a minute before I took a look how late it was. So nothing special.
GPFboyJS said:
I think these options might work for you, however I cannot confirm since I have rooted my phone from day one and never looked back:
Power button + up volume= recovery
Click to expand...
Click to collapse
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?
BrainSD said:
The phone reaches fastboot mode, but when selecting recovery mode I get the google logo and after that the open android with the red exclamation mark. That doesn't look good, does it?
Click to expand...
Click to collapse
thats stock recovery.
is your bootloader already unlocked or no?
Zepius said:
is your bootloader already unlocked or no?
Click to expand...
Click to collapse
It's still locked.
you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.
Zepius said:
you might try and go into recovery,
then press (i think) power and vol up and try and see if you can wipe just cache.
Click to expand...
Click to collapse
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?
BrainSD said:
ok, I tried that several time now, but it didn't work. The only thing when I select recovery and press the power button is that I get the google logo and then the dead android + red exclamation sign, but this screen is scrambled and shows flickering pixels as shown in one of my pictures in the first post. So recovery mode seems not to work for me?
Is there a software or hardware problem with my device?
Click to expand...
Click to collapse
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app
mrgnex said:
You can try to unlock your boorloader and flash a custom recovery like cwm or twrp. Maybe that helps. You can always go back and re lock it.
Sent from my Galaxy Nexus using XDA Premium HD app
Click to expand...
Click to collapse
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Well if I was him I would be more worried about my expensive phone instead of data. Maybe a lesson for later to have a backup
Sent from my Galaxy Nexus using XDA Premium HD app
beekay201 said:
He wants to keep his data... which, at this point, seems rather impossible.
If fastboot doesn't solve it, i would try omapflash, OP. That "flickering" doesn't look good.
Click to expand...
Click to collapse
Yes exactly this is the point. Since I don't have a current data backup the first thing to try is getting my data from the phone. I already tried temporary loading the clockwork recovery through fastboot - with the galaxy nexus toolkit and by hand(sdk) - but it failed ("Bootloader locked").
What I'm wondering about is the fact that the phone seems to behave normally in odin and fastbood mode but going nuts the moment it's expected to boot. Besides the flickering google logo and the "matrix-modded" dead android it even ended up in a totally green screen one time.
At the moment I don't dare trying to unlock/flash the phone because of being afraid getting stuck and ending up with the phone being in some kind of undefined / totally broken state. Initially I was in hope of being able to rescue my data but now i will try my luck with docomo support first.
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
I will try to get through 1 to 4 of the guide first and see how far I get.
If this won't work I might try to unlock, recover and try to "undelete" what's possible. (http://forum.xda-developers.com/showthread.php?t=1994705)
Does this order make sense?
Btw, having a dead phone is bad, of course, even when I got it new for 2300Yen but loosing some pictures i really liked and having no phone atm currently hurts more. Especially when knowing that I was thinking of copying all photos to my computer only one day before when I pulled only some minor important ones from the phone I needed for work and planned to do a full backup and unlock this weekend when I get back my 'Milestone' currently lent to someone else.
Once again something I learned. Backup! Even you phone.
BrainSD said:
As far as I understood omapflash is primary used for recovering bricked phones not even starting to odin/fastboot mode. But thanks to your hint I found http://forum.xda-developers.com/showthread.php?t=2016628 "Unlock bootloader on GT-I9250 without wipe and without root" This might bring some chance for data access.
Click to expand...
Click to collapse
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.
It will unlock your bootloader, bypassing fastboot. Still, it's not for the faint hearted. I refered to omapflash because its a low level tool, it doesn't require the bootloader to be unlocked, and is able to restore the bootloader to working state, and I got there because you mentioned you see graphical glitches/flickering which may indicate bootloader partition failure and/or consequent corruption.
I think that's your best shot at trying to get your data back. After unlock, boot to fastboot and 'fastboot boot custom_recovery.img', and grab your stuff (if you can) from /data/.
beekay201 said:
!!!
It will work actually, I read/also replied to that thread! I had forgotten about it, sorry. I must say that if you had already read the stickies that matter, you'd already know about it.....
Click to expand...
Click to collapse
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems
BrainSD said:
Your hint was very helpful for me getting the right direction since I'm just starting to dig into all this stuff.
Unlocking went quite well. Writing back to the phone worked without a problem and after that it's shown as unlocked in fastboot mode.
It even started loading clockwork recovery with fastboot. But the initial cw recovery screen (their logo and the cw recovery footer) was already shown on a scattered screen (google logo + unlocked lock was fine). After that the usb port connected and disconnected several times, then the screen went blank.
May this be because of corrupted fs or defective hw?
From my understanding with omapflash one have raw access to the phones internal memory similar to with dd on Unix/Linux. So currently I'm trying to dump ("upload") the emmc from the phone - actually in smaller chunks since omapflash needs to allocate all the memory in advance for the upload and to prevent interruptions. This will take a while...
After that I want to try to 'cat' the parts together and mount the filesystem - might be possible to do this from linux since it seems to be ext4 filesystems
Click to expand...
Click to collapse
Great, so far so good.
Yeah, they're ext4 images, but sparse images i believe - link
So I tried using the wugfresh toolkit last nigh to root since from what I've read all the nexus devices use the same method to unlock the bootloader and such. This was likely a mistake. After figuring out I had to change the device to PtP I managed to get to the unlock bootloader screen on the device, at which point it became unresponsive. I turned it off completely, and at that point it wouldn't boot at all, it would just sit on the nexus logo forever. I also couldn't fastboot, holding down the power, volume up and volume down buttons seemed to do nothing. So I let it run down last night in hopes of starting on a fresh charge. Now the device doesn't seem to want to charge at all. I plugged it into both my computer and wall charger through the usual usb cable, and the screen isn't showing any indication of charging. All I saw was the notification light blinking in short bursts after initially plugging it in, and now not even that is happening.
Ideas?
Reboot to recovery and wipe dalvik, cache and system and reboot
Sent from my Nexus 7 using xda premium
Simer03 said:
Reboot to recovery and wipe dalvik, cache and system and reboot
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
If you wipe system, what exactly are you expecting to reboot into???
je
Simer03 said:
Reboot to recovery and wipe dalvik, cache and system and reboot
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
Exactly....I can't reboot into recovery because I can't fastboot into anything. I'm not sure how this helps.
destructobob said:
Exactly....I can't reboot into recovery because I can't fastboot into anything. I'm not sure how this helps.
Click to expand...
Click to collapse
A few points.
First, this is why I highly discourage 'toolkits', especially on Nexus devices. There simply is no reason to use them and many reasons not. It is much wiser to learn how to do things manually, as it makes troubleshooting problems much easier and is less likely to cause a problem. For example, to unlock the bootloader, you could have issued a single command to accomplish it.
Second, as I don't use toolkits, I can't say exactly how the one you used works, but it most likely automates that 'fastboot oem unlock' command, which IS the same for both N7 versions. If so, it shouldn't have caused you any issues.
Third, assuming all you did was attempt to unlock the bootloader - and not flash any custom stuff, root the device, etc. - you should not be running into this issue. If you did try something else, that could certainly explain some of the problems you have. There is certainly a possibility that your device is defective. It it truly won't charge or function at all, I would highly recommend you return it for a new one. If it's dead, there should be no reason why they won't take it back.
Next time, I would recommend doing things the old fashioned way .
phonic said:
A few points.
First, this is why I highly discourage 'toolkits', especially on Nexus devices. There simply is no reason to use them and many reasons not. It is much wiser to learn how to do things manually, as it makes troubleshooting problems much easier and is less likely to cause a problem. For example, to unlock the bootloader, you could have issued a single command to accomplish it.
Second, as I don't use toolkits, I can't say exactly how the one you used works, but it most likely automates that 'fastboot oem unlock' command, which IS the same for both N7 versions. If so, it shouldn't have caused you any issues.
Third, assuming all you did was attempt to unlock the bootloader - and not flash any custom stuff, root the device, etc. - you should not be running into this issue. If you did try something else, that could certainly explain some of the problems you have. There is certainly a possibility that your device is defective. It it truly won't charge or function at all, I would highly recommend you return it for a new one. If it's dead, there should be no reason why they won't take it back.
Next time, I would recommend doing things the old fashioned way .
Click to expand...
Click to collapse
It turns on, it's on at the moment actually. It's been sitting at the nexus logo for about ten minutes. And I still can't load into fastboot, holding down those three buttons does nothing. I'm not even sure why the device froze at the unlock screen. I'm trying to start up the old fashioned way right now, following this link http://forum.xda-developers.com/showthread.php?t=2379618
I've managed to make my way to the platform tools folder in a command line, but running the reboot bootloader command there does nothing. It simply says device not found. I don't think my computer is even seeing the n7 properly so it can't reboot it. I don't think its defective, but I don't know where to begin to fix this using the old fashioned way either....
phonic said:
A few points.
First, this is why I highly discourage 'toolkits', especially on Nexus devices. There simply is no reason to use them and many reasons not. It is much wiser to learn how to do things manually, as it makes troubleshooting problems much easier and is less likely to cause a problem. For example, to unlock the bootloader, you could have issued a single command to accomplish it.
Second, as I don't use toolkits, I can't say exactly how the one you used works, but it most likely automates that 'fastboot oem unlock' command, which IS the same for both N7 versions. If so, it shouldn't have caused you any issues.
Third, assuming all you did was attempt to unlock the bootloader - and not flash any custom stuff, root the device, etc. - you should not be running into this issue. If you did try something else, that could certainly explain some of the problems you have. There is certainly a possibility that your device is defective. It it truly won't charge or function at all, I would highly recommend you return it for a new one. If it's dead, there should be no reason why they won't take it back.
Next time, I would recommend doing things the old fashioned way .
Click to expand...
Click to collapse
I second all that's been said here. While toolkits can seem attractive, it's really quite simple, and much safer to do it manually once your take an hour to learn your way around the Android-SDK (way easier than it sounds, I promise).
I like toolkits, seriously, but they hardly ever work. I usually have to drop to a shell prompt and run the commands manually anyway.
Sent from Nexus 7 XHD using XDA Premium HD
destructobob said:
It turns on, it's on at the moment actually. It's been sitting at the nexus logo for about ten minutes. And I still can't load into fastboot, holding down those three buttons does nothing. I'm not even sure why the device froze at the unlock screen. I'm trying to start up the old fashioned way right now, following this link http://forum.xda-developers.com/showthread.php?t=2379618
I've managed to make my way to the platform tools folder in a command line, but running the reboot bootloader command there does nothing. It simply says device not found. I don't think my computer is even seeing the n7 properly so it can't reboot it. I don't think its defective, but I don't know where to begin to fix this using the old fashioned way either....
Click to expand...
Click to collapse
To get into bootloader mode, you hold down POWER+VOLDOWN - not all three buttons. Make sure you turn off your device first (hold down power until it shuts off), then hold down those two buttons.
If it gets to the nexus logo, that means your bootloader should be OK, which means you can probably recover.
The 'adb reboot bootloader' command will not work until the device is booted up, your turned on developer mode and USB debugging, and you allowed your computer to connect.
Assuming you can get into bootloader, look to see if you did successfully unlock it or not. If you didn't, try the 'fastboot oem unlock' command.
If you continue to be unable to boot normally, you will likely need to flash the system image. There is one floating around here (system.img). You can do this in the bootloader as well (fastboot flash system system.img).
hadisious said:
I second all that's been said here. While toolkits can seem attractive, it's really quite simple, and much safer to do it manually once your take an hour to learn your way around the Android-SDK (way easier than it sounds, I promise).
Click to expand...
Click to collapse
I understand that and have absolutely learned my lesson. What's confusing me at the moment is installing the drivers listed in the link I posted. All that's there is a zip file, no exe or anything which is what I'm used to for installers. I was able to reboot my nexus 7 into bootloader before with the toolkit, so I know I had the drivers installed properly at some point. The toolkit installed a universal ADB set which I'm thinking should work. I don't know what to do to get the device into bootloader to follow the instructions.
phonic said:
To get into bootloader mode, you hold down POWER+VOLDOWN - not all three buttons. Make sure you turn off your device first (hold down power until it shuts off), then hold down those two buttons.
If it gets to the nexus logo, that means your bootloader should be OK, which means you can probably recover.
The 'adb reboot bootloader' command will not work until the device is booted up, your turned on developer mode and USB debugging, and you allowed your computer to connect.
Assuming you can get into bootloader, look to see if you did successfully unlock it or not. If you didn't, try the 'fastboot oem unlock' command.
If you continue to be unable to boot normally, you will likely need to flash the system image. There is one floating around here (system.img). You can do this in the bootloader as well (fastboot flash system system.img).
Click to expand...
Click to collapse
So I'm able to get into the bootloader, but its not responding to the command line entries. My computer brings a popup anytime the nexus tries to do a regular boot, where it just sits at the logo. The popup explains that the device is unrecognized. I've uninstalled any devices that resemble the nexus in device manager, and have tried repeatedly to update the driver manually by pointing it to the usb driver folder within the sdk. Doing that simply says windows is unable to locate the correct driver. So I think my device is where it needs to be, I just can't connect to it from the command line at the moment.
First of all, what made you try the toolkit(effective as it is) on the new Nexus...? Couldn't you just sit down for a day or two enjoying stock experience(abominative as it is)...?
alicarbovader said:
First of all, what made you try the toolkit(effective as it is) on the new Nexus...? Couldn't you just sit down for a day or two enjoying stock experience(abominative as it is)...?
Click to expand...
Click to collapse
Unlocking the bootloader will always result in your device getting wiped.
So it makes sense that you do this first, this way you don't need to setup your device twice.
It also has nothing to do with stock vs custom. I have an unlocked bootloader, custom recovery and am rooted. But my device is still completely stock as far as the OS goes. The only thing I might change in the future is a custom kernel, as I am usually fine with things 'stock' from a user perspective on Nexus.
phonic said:
Unlocking the bootloader will always result in your device getting wiped.
So it makes sense that you do this first, this way you don't need to setup your device twice.
It also has nothing to do with stock vs custom. I have an unlocked bootloader, custom recovery and am rooted. But my device is still completely stock as far as the OS goes. The only thing I might change in the future is a custom kernel, as I am usually fine with things 'stock' from a user perspective on Nexus.
Click to expand...
Click to collapse
Honestly I had completely forgot that the initial unlocking does the factory reset. I got caught up in booting up the device and installing a few apps to try it out, to the point that I completely blanked on the reset haha.
I tried a bunch of different roms and verions on my gnexus and old N7, jumping between CM and PA mostly, and I got used to just having a backup ready and not worrying about a data wipe. I've mostly stuck with PA because the pie controls are fantastic on both devices and I've come to get used to the added screen space. I'm perfectly fine with the stock experience outside of pie controls, but I do love customizing my device and the custom roms allow for so much freedom in that regard.
destructobob said:
I understand that and have absolutely learned my lesson. What's confusing me at the moment is installing the drivers listed in the link I posted. All that's there is a zip file, no exe or anything which is what I'm used to for installers. I was able to reboot my nexus 7 into bootloader before with the toolkit, so I know I had the drivers installed properly at some point. The toolkit installed a universal ADB set which I'm thinking should work. I don't know what to do to get the device into bootloader to follow the instructions.
Click to expand...
Click to collapse
Okay... so its a zip file.... go to device manager and it should show you some android driver or nexus 7 or something.... right-click on that and choose update drivers... choose manual method and select the folder hat you unzipped...
then use fastboot to flash factory image...
Q: is factory image for nexus 4 2013 available
??
shengovind said:
Okay... so its a zip file.... go to device manager and it should show you some android driver or nexus 7 or something.... right-click on that and choose update drivers... choose manual method and select the folder hat you unzipped...
then use fastboot to flash factory image...
Q: is factory image for nexus 4 2013 available
??
Click to expand...
Click to collapse
I actually got it successfully up and running, unlocked and rooted and everything. The screen and dual speakers alone justify the price for sure, and the speed difference is noticeable. Riptide 2 seems to run alot smoother on this than my old N7. I'm also aware that in general a clean install runs better than something that's been used for a while, so perhaps that's part of my percieved performance gains. In any case I'm more than happy with my purchase, and am looking forward to getting my chromecast tomorrow!
destructobob said:
I actually got it successfully up and running, unlocked and rooted and everything. The screen and dual speakers alone justify the price for sure, and the speed difference is noticeable. Riptide 2 seems to run alot smoother on this than my old N7. I'm also aware that in general a clean install runs better than something that's been used for a while, so perhaps that's part of my percieved performance gains. In any case I'm more than happy with my purchase, and am looking forward to getting my chromecast tomorrow!
Click to expand...
Click to collapse
:good::good::good:
phonic said:
Unlocking the bootloader will always result in your device getting wiped.
So it makes sense that you do this first, this way you don't need to setup your device twice.
It also has nothing to do with stock vs custom. I have an unlocked bootloader, custom recovery and am rooted. But my device is still completely stock as far as the OS goes. The only thing I might change in the future is a custom kernel, as I am usually fine with things 'stock' from a user perspective on Nexus.
Click to expand...
Click to collapse
Yes but you should've waited for a suitable toolkit.
alicarbovader said:
Yes but you should've waited for a suitable toolkit.
Click to expand...
Click to collapse
Why would I wait for a toolkit?
This is a Nexus device. You don't need a toolkit. All you need is two brain cells and a willingness to learn. You can unlock, flash custom recovery and root in a matter of minutes with nothing other than the Android SDK. Toolkits cause more problems than they solve.
phonic said:
Why would I wait for a toolkit?
This is a Nexus device. You don't need a toolkit. All you need is two brain cells and a willingness to learn. You can unlock, flash custom recovery and root in a matter of minutes with nothing other than the Android SDK. Toolkits cause more problems than they solve.
Click to expand...
Click to collapse
ok, not a toolkit.. I give you that, but was the stock experience too intimidating...?
personally, i'd nuked htc sense when i got thoroughly bored with its great buttery ui. i like the aosp experience, rooted or not.
and i didn't know that we don:t need toolkits fpr nexus devices, cuz i've never happened to own one.
Hello I need a but of help my Nexus 7 is showing my nothing but the google logo and at the store earlier it showed the android with his chest up and a red triangle. it doesnt even show the moving colors after i turn it on it just sits and says google like a paper weight. i can turn it off and on but nothing more. the geek squad at best buy told me to ask for help here at Xda. last thing i was doing with it was opening deer hunter 2013 and next i go to see if it opened and it stuck on the google logo. can anyone help me fix my tablet? its not under store warranty only manufactures.
Well, sucks to be you.....just kidding...but that does suck. Now, on to more serious matters...
Do you have access to your bootloader? (hold the power button + the vol up button at the same time) If you do, you might want to look into rooting the tablet. Based on the content of your post, I am assuming that you haven't. There is plenty information about rooting the Nexus 7.2 tablet (and just about every other Android device). Simply Google "root Nexus 7 2013" and you will quickly find your answer.
Also, how much do you know about rooting and the sort? I want to know before I waste my time giving details about info that you are aware of.
aarsyl said:
Well, sucks to be you.....just kidding...but that does suck. Now, on to more serious matters...
Do you have access to your bootloader? (hold the power button + the vol up button at the same time) If you do, you might want to look into rooting the tablet. Based on the content of your post, I am assuming that you haven't. There is plenty information about rooting the Nexus 7.2 tablet (and just about every other Android device). Simply Google "root Nexus 7 2013" and you will quickly find your answer.
Also, how much do you know about rooting and the sort? I want to know before I waste my time giving details about info that you are aware of.
Click to expand...
Click to collapse
i dont know anything about rooting. i dont have access to the boot loader. i did a few days ago now it wont even show up, the guy and best buy tried to bring it up and its like it was showing a dead android or something chest open with a red triangle above it. he said someting about maybe have to flash a new or or something like that on to it, it wont show me anything just stays off or shows the google logo when its on
Sigh...that is the bootloader. Maybe...he could have booted into the stock recovery, which shows this or something similar for most devices. Please remember, they are reps...they may know about the software, but usually they speak from their experience or their perspective. I'm glad that he sent you here for a second opinion.
Hold the volume down button and power button to get into the bootloader. You should see some options at the top of the screen saying Start, Restart bootloader, Recovery Mode, Power Off. Not sure if those are the exact options, but it's pretty close.
Also, you need to look into rooting your device. You need to download some files first. You'll need adb, fastboot, and drivers for your Nexus.
And one last thing....what Computer OS do you use? The rooting process is slightly different for each one (Windows 7, 8/8.1, Mac OS, & Linux). If you are into computers, and you have Linux installed on a device, good for you. That is my preference when rooting, as Android is built from Linux, and naturally supported without the need for drivers.
I had similar problems when I first bought it. Going into recovery and resetting the tablet cured it. You will lost all your data BTW.
He's facing the loss of his entire tablet, so I'm sure that data loss isn't the biggest thing to worry about.
But yes, just about every solution involves a clean wipe of data.
_______________________________________
Phone: HTC EVO 4G LTE
Sense 5, S-Off
Tablet: ASUS Nexus 7.2
Rooted, Custom Rom & Kernel
_______________________________________
I'm stuck on the google logo too. I had my tablet plugged in over night and when I opened the cover this morning it woke up, but as soon I tried to access anything it rebooted and stuck.
I'm unlocked and have tried various thing. NRT doesn't recognize it as an ADB device so I don't think that will work. Fastboot works, but I keep getting "FAILED (remote: flash write failure)" when I try to use the factory flash all, or the instructions found here: http://forum.xda-developers.com/showthread.php?t=2381582
I can use fastboot to query the device and get it to return "flo" but it seems like the flash storage has failed.
if it's truly horked, can I use "fastboot oem lock" to relock it and attempt a warranty replacement?
sean67854 said:
I'm stuck on the google logo too. I had my tablet plugged in over night and when I opened the cover this morning it woke up, but as soon I tried to access anything it rebooted and stuck.
I'm unlocked and have tried various thing. NRT doesn't recognize it as an ADB device so I don't think that will work. Fastboot works, but I keep getting "FAILED (remote: flash write failure)" when I try to use the factory flash all, or the instructions found here: http://forum.xda-developers.com/showthread.php?t=2381582
I can use fastboot to query the device and get it to return "flo" but it seems like the flash storage has failed.
if it's truly horked, can I use "fastboot oem lock" to relock it and attempt a warranty replacement?
Click to expand...
Click to collapse
You can try Method 2 from this post: http://forum.xda-developers.com/showthread.php?t=2513701
I know it's for the N5, but I used this one for both my Galaxy Nexus, N5 and N7. Since they are all Nexuses (Nexi?), the same general procedures apply. I always prefer to do it all manually, step-by-step, which is why I went with Method 2 in the OP of that thread. Obviously, since this is the N7, just skip the radio flashing command. Everything else is the pretty much exactly the same. If this doesn't work in fastboot, then it's probably a hardware failure.
my phone was working normally and all of a sudden I came back to my room and it only displayed the galaxy a50 starting screen (the one before there is just "samsung" written).
Restarting it didn't help and it always gets stuck at the same display or restarts endlessly. Sometimes it makes it until the "samsung" display.
Firstly, I don't really know why it rebooted anyway and the problem started. There is a software update I should have been doing for quite some time, so maybe that got executed automatically (is that even possible?) and failed?
What I already tried:
Charging (100% charged)
Went into recovery mode and:
repaired apps (didn't help)
powered off and restarted after 20 minutes of being turned off (didn't help)
Run graphics/ locale test (didn't help, the graphics test said something about deleting so I got afraid and restarted it. Could I have lost some data because of that?)
click on mount/system (as far as I can tell nothing happened)
wiped cache partition (didn't help)
clicked reboot to bootloader (what does that do? There was written downloading but then I got scared and restarted the phone, could that have done some damage?)
Rebooted (nothing happened)
downloaded drphone, phone does not get recognized
As you might see, I'm a bit desperate and although being quite tech savvy I don't know that much about android.
What is most important to me is recovering/ not deleting the data on my phone (last backup is about one month old so not too bad but still very bad for me) so please suggest safe options first in that regard (if there are any).
Can I maybe just update the software via ADB without damaging my data?
Or use ODIN for that? Also heard something about TWRP. Don't really know how any of these three work exactly (but totally willing to learn how!)
Your help would mean the world to me
the deleting part in the graphics test is just texts it does nothing. i dunno if the usb debugging is enabled, but if it is get alternative boot partition (saved my pixel 4 like that). i used linageOS 20 recovery mode that got me to os i backed up my files and then reflashed.
KirinPixel said:
the deleting part in the graphics test is just texts it does nothing. i dunno if the usb debugging is enabled, but if it is get alternative boot partition (saved my pixel 4 like that). i used linageOS 20 recovery mode that got me to os i backed up my files and then reflashed.
Click to expand...
Click to collapse
Thanks very much for your reply! I found out quite a bit by now and it seems to me after intensely studying this thread https://forum.xda-developers.com/t/...ce-is-stuck-on-boot-loop.4536965/page-2#posts only reinstalling the software (most likely with ODIN) is the way to get back to the phone working properly. You don't know anything about that, maybe? I'm very afraid to do it wrong and wipe my data.
Can I just reinstall the already installed software version? Or should I go higher?
I restarted it once though and even put in my PIN but after the home screen appeared it fell back into the bootloop again.
I have no experiance with samsung odin. But what i say is you bring it to someone who does to back ya fils up. Then go play with flashing. Odin is far from the only way. Unfortunately i can not assist you on it because i never used it. Good luck!