Database Users

Might buy boot-looping Xoom, questions

Hello,
So I bought my Xoom over the weekend when I never heard back from a Craigslister about a Xoom they have that is bootlooping.
Finally got back to me today and I am looking to fix it, and make a little profit.
Guy explained he knows it can get into Fastboot and mentioned RSD lite so I know he has done some research but ultimately he said he is not good at computers and cannot fix it.
My question is what do I need to consider? If I can access hboot ( from power off wait til see M and hit Vol - right?) I should be good to go is my understanding. Is there any way to run a diagnostic and see if there is hardware issues going on?
What would you do I guess lol
He said I could tinker with it first. I am familiar with ADB and rooting / custom roms on Android but have only had my Xoom for about 3 days.
Thanks

If you can definitely get into fastboot, you can recover it; simple as that. Whether there are hardware issues is another matter.

MoreGone said:
Hello,
So I bought my Xoom over the weekend when I never heard back from a Craigslister about a Xoom they have that is bootlooping.
Finally got back to me today and I am looking to fix it, and make a little profit.
Guy explained he knows it can get into Fastboot and mentioned RSD lite so I know he has done some research but ultimately he said he is not good at computers and cannot fix it.
My question is what do I need to consider? If I can access hboot ( from power off wait til see M and hit Vol - right?) I should be good to go is my understanding. Is there any way to run a diagnostic and see if there is hardware issues going on?
What would you do I guess lol
He said I could tinker with it first. I am familiar with ADB and rooting / custom roms on Android but have only had my Xoom for about 3 days.
Thanks
Click to expand...
Click to collapse
The question is, how much are you willing to pay if you can't fix it, then if you can you will be happy, if not you should stay happy.
Bootloop can be software but they can easily be hardware too so better be safe than sorry

take a laptop with you and do "fastboot devices' on the spot.
If the computer can see it then it can be wiped clean and fixed

It's $300 and it wouldn't kill me, obviously wouldn't be ideal but not the end of the world either.

ydaraishy said:
If you can definitely get into fastboot, you can recover it; simple as that. Whether there are hardware issues is another matter.
Click to expand...
Click to collapse
That's what everyone told me when mine went into a boot loop. I was able to flash the new images in fastboot, but it never came out of the boot loop.

P00r said:
The question is, how much are you willing to pay if you can't fix it, then if you can you will be happy, if not you should stay happy.
Bootloop can be software but they can easily be hardware too so better be safe than sorry
Click to expand...
Click to collapse
At what point would I be able to run that command? When powering up, at the M etc?

Zargon335 said:
That's what everyone told me when mine went into a boot loop. I was able to flash the new images in fastboot, but it never came out of the boot loop.
Click to expand...
Click to collapse
Stock images?

Zargon335 said:
That's what everyone told me when mine went into a boot loop. I was able to flash the new images in fastboot, but it never came out of the boot loop.
Click to expand...
Click to collapse
That's certainly a concern

ydaraishy said:
Stock images?
Click to expand...
Click to collapse
Yes.
10chars

@OP
If seller knows about Fastboot & RSD Lite, he's probably on this forum. Might even be in this thread.
HEY SELLER just let me figure this out and I'll buy it right off ya, OK?

If you CAN get out of it that certainly a very good price. Most cases I think I have seen have been recoverable. Maybe ask the seller how he got into this situation in the first place, might give you a better understanding of how to fix it.

Need HELP to unbrick Nexus 4!

Sent from my Nexus 7 using Tapatalk 2
My N4 is from PlayStore USA, and I live outside of US. A few days ago I did a stupid mistake and flashed a wrong bootloader (please don't ask why - the embarrassment still hurts! ). The N4 is now totally dead - cannot be turned on, and won't boot no matter which sets of buttons I hold down.
I have been searching the net for solutions but have not found any simple enough (for me) solution. I read of several similar cases and the solution has been to send back to Google/LG. As I live outside of US, this isn't much of an option. I have also read about use of Gtag to unbrick devices but this is beyond my capability and this service is also not available in my country. Sending the N4 to my local LG service centre for repairs (there's no International warranty) is a last resort but I am not sure whether they have tbe tools and knowhow to unbrick my N4. They may not even want to get involved!
So I am writing in this forum to ask for help. Any advice will be appreciated. Thanks in advance.

Why the hell would you even flash the bootloader manually?
Anyway, there was a thread recently about Qualcomm's debugging mode. However, you'll need the appropriate drivers and most likely other software for it to work.
I don't know if anyone actually got it working, though

I dont know why I did it too - just following wrong instructions ; out of sheer stupidity!
Sent from my Nexus 7 using Tapatalk 2

download the quacomm usb high speed drivers and install them you might have to do have disk to install them in device manager. then doqnload the QPST qualcomm tool. this will allow you to flash phone images and other files here. It should pick your phone up in download state. Only problem now is that the Qualcomm tool only allows hex image files to be flashed. this is where i was stuck

Thanks for the qualcomm suggestion. I will look through it when I return to my home country in a week`s time. But from what you have described, the procedure seems too complex for me. I am also following the other `bricked Nexus 4` thread in this section which I was not aware of till yesterday. All indications are that my bricked Nexus 4 will be a total loss - LG in my country has told me that they will not touch my unit until Nexus 4 is officially launched in my country (that could be a couple of months away), and returning the unit back to Google USA will be extremely difficult, complex and cumbersome as I just learned that the unit has to be returned by the original purchaser from USA (I bought the N4 from a 3rd party in my country). Its an expensive mistake and I can only blame myself for the stupid mistake I made.

Thats how far i got with my bricked nexus thing was there was no images in hex to flash. the only thing i can think of is that you coulld try acking up a phone in QPST and the flash to bricked one. but you would need to enter the *# code to change usb on working phone to diagnostics

chwads2k8 said:
Thats how far i got with my bricked nexus thing was there was no images in hex to flash. the only thing i can think of is that you coulld try acking up a phone in QPST and the flash to bricked one. but you would need to enter the *# code to change usb on working phone to diagnostics
Click to expand...
Click to collapse
Not that simple. If you want, read this thread for some good info: http://forum.xda-developers.com/showthread.php?t=1914359

What where you trying to flash?

Anyone tried succesfully?

What i can do to unbrick my nexus7?

Hi.
I Was on stock 4.3.
I unlocked bootloader and rooted it via nexus 7 toolkit v.5.0
Then via TWRP i tryed to flash aosp 4.4 and it gave me "error 7"...
So i tryed to go back to stock, but i didnt made a backup, i tryed to flash factory image but nothing happend.
What should i do?
On another toolkit, what it finish image download, it show: missmatch, flash canceled.

If you can boot into bootloader mode, you can flash a factory image with fastboot.
If you cannot, your N7 is a goner.

By older brother tryed to fix it... and he locked the bootloader...
How i can unlock the bootloader now?

larpowiec said:
By older brother tryed to fix it... and he locked the bootloader...
How i can unlock the bootloader now?
Click to expand...
Click to collapse
fastboot oem unlock
Rgrds,
Ged.

If he was able to lock it, that means your bootloader is working fine and you can access your N7 with fastboot, whick means you can recover it by fastboot flashing a stock image.

Is there anyway whatsoever to maybe make use of the apx mode to unbrick it while fastboot is inaccessible????
Sent from my GT-S5570 using xda app-developers app

nobody_nowhere said:
Is there anyway whatsoever to maybe make use of the apx mode to unbrick it while fastboot is inaccessible????
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Hi, nobody_nowhere...
I received your PM regarding the thread located here... if your Nexus 7 has gone into an unstoppable CWM bootloop, as happened to @Jagutherrschaften 's Nexus 7, then other than the suggestions I made at the time, I'm afraid I have nothing else to add... other than to try to break out of the bootloop, by repeatedly pressing the VOL DOWN + POWER ON keypress sequence. Theoretically (and as I can confirm, having had similar issues myself), this should break out of any bootloop, and boot you directly into the bootloader... from which you can run fastboot commands.
I very much doubt APX is going to help here... unless you have previously generated your own unique Nexus 7 'wheelie blobs' using the flatline procedure. These 'blobs' are generated on a per-device basis, and are NOT transferable from one Nexus 7 to another.
And even if you did have such 'blobs' (which are primarily used to resurrect a dead bootloader), I have a suspicion they wouldn't be of much use to you... given your bootloader is actually intact (if it wasn't, your device would be completely dead - nothing would happen... at all... not even bootloop).
Sorry I can't shed any light on your problem, or suggest anything that might resolve it.
Rgrds,
Ged.

I thank you for replying so quickly. And honestly, I guess that's it for my nexus then . : crying:
Sent from my GT-S5570 using xda app-developers app
---------- Post added at 11:53 PM ---------- Previous post was at 11:42 PM ----------
Well, another question. Is there perhaps a point trying to claim warranty?
And about APX mode, how do I get my nexus out of it?
Sent from my GT-S5570 using xda app-developers app

nobody_nowhere said:
I thank you for replying so quickly. And honestly, I guess that's it for my nexus then . : crying:
Sent from my GT-S5570 using xda app-developers app
---------- Post added at 11:53 PM ---------- Previous post was at 11:42 PM ----------
Well, another question. Is there perhaps a point trying to claim warranty?
And about APX mode, how do I get my nexus out of it?
Sent from my GT-S5570 using xda app-developers app
Click to expand...
Click to collapse
Hi again, nobody_nowhere...
Well, there's certainly no harm in trying to claim warranty... you have nothing to loose.
Certainly, some here on XDA, and on other forums have succeeded. The question really is whether or not you have a hardware fault or a software fault. I'm inclined to think it's probably hardware related... in which case you should certainly be covered by warranty.
The whole business of flashing custom ROMs/kernels and any consequential screwups that might occur is a bit of a grey area when it comes to claiming warrenty... fortunately I've never (at least so far) been in that position.
With regard to getting out of APX mode... a long press on the power button should do it, as detailed here.
If you can't get out of APX mode, then your bootloader is almost certainly dead... as APX mode is the natural state the Nexus 7 defaults to in the absence of a working bootloader... with the expectation that somebody with the neccessary technical expertise and software ('wheelie blob's' generated by the flatline procedure, for example), will nvFlash a new one.
Rgrds,
Ged.

GedBlake said:
Hi again, nobody_nowhere...
Well, there's certainly no harm in trying to claim warranty... you have nothing to loose.
Certainly, some here on XDA, and on other forums have succeeded. The question really is whether or not you have a hardware fault or a software fault. I'm inclined to think it's probably hardware related... in which case you should certainly be covered by warranty.
The whole business of flashing custom ROMs/kernels and any consequential screwups that might occur is a bit of a grey area when it comes to claiming warrenty... fortunately I've never (at least so far) been in that position.
With regard to getting out of APX mode... a long press on the power button should do it, as detailed here.
If you can't get out of APX mode, then your bootloader is almost certainly dead... as APX mode is the natural state the Nexus 7 defaults to in the absence of a working bootloader... with the expectation that somebody with the neccessary technical expertise and software ('wheelie blob's' generated by the flatline procedure, for example), will nvFlash a new one.
Rgrds,
Ged.
Click to expand...
Click to collapse
Right. So if I do claim warranty, how do I go about it? I don't mean the contacting htem and stuff. But what do I say to them to ensure maximum chance of getting the warranty?
I mean, I have voided the warranty by installing custom software on my Nexus. But is there any way I could actually logically persuade them to give me warranty? Or is it just luck? Hoping you get a not-so-smart technician to verify it is suitable for warranty?
And by the way, thanks for your informative reply

[Q] Cannot Unlock Bootloader, Bricked Tablet

Hey Guys,
Hoping someone can help here, I have followed various tutorials I have found on the internet to try and restore my Nexus 7 back to its factory state after it one day decided to never get past the white Google logo.
Inevitably I ended up on this tutorial as the only one where I seemed to get any kind of a link and response with the tablet: blog.laptopmagDOTCOM/how-to-hard-reset-a-bricked-nexus-7-with-your-pc
basically it got as far as trying to Unlock the Bootloader, but it fails to do so. I do get the popup on the tablet asking if I want to unlock it but nothing happens, it remains locked after I click Yes. My command line saying that it Failed.
All other tutorials seem to assume you can access the OS and enable debug mode but of course I cannot. I cannot even do a Factory Reset, every options eventually leading me to a white Google logo.
I also cannot get into recovery mode, im just stuck on the screen with the green android and the option to Start, Recovery mode etc all just lead to the Google logo.
The impression I have gotten from not being able to unlock the bootloader is that there must be a hardware failure? could anyone suggest some black magic I might be able to do to fix it? I realise at some point I should cut my losses. I had also wondered if it was worth buying a new motherboard/logic board?
Would appreciate any help.
Cheers,
Matt.

Have you tried this tools:
http://forum.xda-developers.com/showthread.php?t=1766475
or
http://forum.xda-developers.com/showthread.php?t=1809195
Both are magic tools for nexus 7, please read any explanation carefully!
It may help you :good:

ju1da said:
Have you tried this tools:
http://forum.xda-developers.com/showthread.php?t=1766475
or
http://forum.xda-developers.com/showthread.php?t=1809195
Both are magic tools for nexus 7, please read any explanation carefully!
It may help you :good:
Click to expand...
Click to collapse
Wow.....
Please stop spamming the toolkits.
The op has indicated that there is a hardware issue because the bootloader unlock isn't working.. A stupid toolkit isn't going to fix that. You should are promoting people to use their damn brains and doing it the right way, but laziness prevails, eh?
To the op, sorry but it sounds like you have a corrupt emmc. If the unlock process fails to commit, that's a bad sign.
Sent from my Nexus 5

Also to the op, USB debugging has nothing to do with the bootloader or recovery, only a booted os. Can you boot to recovery from the bootloader?
Sent from my Nexus 5

Received device 2 hrs ago. Now stuck with "Error 7" trying to flash CM13 via TWRP

Received device 2 hrs ago. Now stuck with "Error 7" trying to flash CM13 via TWRP
Received device 2 hrs ago. Now stuck with "Error 7" trying to flash CM13 via TWRP
Yeah well, the topic says all. Took the latest image from CM13 but it just won´t flash. Any ideas? So keen on starting with my new device...

688attacksub said:
Received device 2 hrs ago. Now stuck with "Error 7" trying to flash CM13 via TWRP
Yeah well, the topic says all. Took the latest image from CM13 but it just won´t flash. Any ideas? So keen on starting with my new device...
Click to expand...
Click to collapse
Flash the latest bootloader, radio, and vendor. And then go on flashing the ROM.

Any chance to get a quick hint HOW?! I´m rather unexperienced, sorry.

We can see that. lol

688attacksub said:
Any chance to get a quick hint HOW?! I´m rather unexperienced, sorry.
Click to expand...
Click to collapse
http://bfy.tw/4vLn

Just unrooted and unlocked it using the tool kit. Maybe I´ll have another try some other time. For time being I had enough thrill. Thx and n8 boys.

No offense to you but you should have done some reading on how to modify your phone instead of jumping to a toolkit to do all the work for you. Check out Heisenberg's guide in the general section.

688attacksub said:
Received device 2 hrs ago. Now stuck with "Error 7" trying to flash CM13 via TWRP
Yeah well, the topic says all. Took the latest image from CM13 but it just won´t flash. Any ideas? So keen on starting with my new device...
Click to expand...
Click to collapse
Read my guide. Read it again. Then read it again. Then read it some more. Ditch the toolkit. You'll be much better off knowing how to do things for yourself. You really shouldn't be modifying your phone if you don't know what you're doing, you're gonna end up bricking it.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928

Heisenberg said:
Read my guide. Read it again. Then read it again. Then read it some more. Ditch the toolkit. You'll be much better off knowing how to do things for yourself. You really shouldn't be modifying your phone if you don't know what you're doing, you're gonna end up bricking it.
http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
I do like the post you put together. But to say ditch the toolkit means some developer that put together the toolkit isn't getting support. I would agree that you should know what you're doing and how to recover a phone before using a toolkit, and probably should try to do the entire process without the toolkit, but once you got it down, no reason not to use the toolkit.

dbroer91884 said:
I do like the post you put together. But to say ditch the toolkit means some developer that put together the toolkit isn't getting support. I would agree that you should know what you're doing and how to recover a phone before using a toolkit, and probably should try to do the entire process without the toolkit, but once you got it down, no reason not to use the toolkit.
Click to expand...
Click to collapse
I can think of one reason not to use a toolkit: they're known to cause problems. There are threads in virtually every Q&A section that can attest to this.

Heisenberg said:
I can think of one reason not to use a toolkit: they're known to cause problems. There are threads in virtually every Q&A section that can attest to this.
Click to expand...
Click to collapse
I took time to learn how to to everything manually but I still have loads of experiences with tool kits nexus 5 and 7 even previous 6ps that are faulty and have never had a problem with them they simply provide more convenience
Sent from my Nexus 6P using Tapatalk

mystertom101 said:
I took time to learn how to to everything manually but I still have loads of experiences with tool kits nexus 5 and 7 even previous 6ps that are faulty and have never had a problem with them they simply provide more convenience
Sent from my Nexus 6P using Tapatalk
Click to expand...
Click to collapse
I didn't say they cause problems for everyone, if they did they wouldn't be on the site. Anyway, the entire point I was making here, which seemed to be completely lost on some people, is that a beginner shouldn't be using a toolkit, they should be gaining the knowledge that's required (by reading and doing things manually) when you're modifying your phone.

Heisenberg said:
I didn't say they cause problems for everyone, if they did they wouldn't be on the site. Anyway, the entire point I was making here, which seemed to be completely lost on some people, is that a beginner shouldn't be using a toolkit, they should be gaining the knowledge that's required (by reading and doing things manually) when you're modifying your phone.
Click to expand...
Click to collapse
This. Heisenberg is not saying toolkits are useless. The main theme he's trying to employ here is that new users should not be relying on toolkits instead of taking the time to learn the basics of Fastboot before diving into the world of root and mods. When the toolkit fails, Fastboot will rescue you. If you don't know how to use Fastboot, avoidable threads such as this are constantly generated.