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.
Related
hi i need help plz after rooting i don spl . the device now on g1 logo i try meny things home+power - cmera+power ..... nothing
First of all, you've officially murdered the English language. The only way I sort of understood what you were saying was by copy and pasting your post to Google Translate.
Secondly, I still can't understand it. So you rooted but didn't flash an SPL but flashed the radio, and now your stuck at G1 logo? Hmmm, I could only presume you've successfully entered Bricksville (Population: Noobs*Infinite).
Try pulling out the battery and boot into Recovery (Home + Power) Mode, FastBoot (Back + Power) Mode, or Bootloader (Volume Down/Camera + Power) Mode.
Or plug in USB adapter into device and setup ADB. After you've successfully setup ADB, get back to me so I can give you the commands and needed nbh files to pull you out of your predicament.
I mean, after change recovery img I done spl but the device freeze on G1 logo and it doesnt respond . what you mean setup ADB ???????
dude you are basically f'ed. you didnt update your radio did you. you just flashed a spl. welcome to BRICKSVILLE. population...YOU. and countless others who probably didnt READ AND RE READ THE ENTIRE POST AND READ WHILE YOU ARE DOING THESE PROCEDURES. these CAN AND WILL BRICK YOUR PHONE IF YOU DO NOT KNOW WHAT YOU ARE DOING.
It's quite amazing that the population of "Bricksville" continues to grow. There is plenty of literature out there about rooting your device but it still seems to elude some. Just awesome. And how true.. Noobs*Infinite... I lol'd.
nolimit78 said:
It's quite amazing that the population of "Bricksville" continues to grow. There is plenty of literature out there about rooting your device but it still seems to elude some. Just awesome. And how true.. Noobs*Infinite... I lol'd.
Click to expand...
Click to collapse
Very true, it's impossible to brick unless you have trouble reading that means you need to go back to elementary.
Ace42 said:
Very true, it's impossible to brick unless you have trouble reading that means you need to go back to elementary.
Click to expand...
Click to collapse
+1. This is true.
Meh, it's probably just a troll.
Lol these posts are quite funny
bricksville... I'll keep that in mind... lol
I think I asked for help, not a silly jokes
majed2001 said:
I think I asked for help, not a silly jokes
Click to expand...
Click to collapse
you got help. the jokes were for our amusement. its not our fault you bricked your phone, we are allowed to "chuckle" when other people mess up, because we know that we are smart enought to keep our very expensive phones up and running.
So I've apparently, effectively bricked my phone. Under bootloader it is listed as S-OFF. Is there any way I can return my evo in and stay under warranty?
Note: I can not reach recovery.
What happens when you rename a recovery to PC36IMG.zip and try to update via bootloader?
I go into a boot loop no matter what i do, no matter what I flash. I have flashed 10+ PC36IMGs with everything from bootloaders to recoveries, to every img that can be on the phone... there is a thread still on the first page if you want to look at that.
Anyways, it doesn't look like I'm going to be able to fix it, so this is more about what options are available to me in getting a new phone, if you having any suggestions though on what I can do to fix mine, please be my guest and comment on my thread below, I'm still trying to fix it!
Just report the phone lost or stolen and pay $100 deductible.
Sent from my PC36100 using XDA App
I would try one last time to flash Amon's recovery.
Download this: http://forum.xda-developers.com/attachment.php?attachmentid=483320&d=1294435056
Rename it to "PC36IMG.zip"
put it on the root of your sd card via a card reader if you have one or someone elses phone.
then update via bootloader.
Other than that I'm out of ideas. The good news is I'm not as savvy as 95% people on here, which means someone much smarter than me might know the answer. Good luck.
Hmm, yeah I may just have to pay the 100 then... but is that an insurance thing or a warranty thing? I don't have insurance
Do you think Sprint will even check for the S-ON?
thanamesjames said:
Hmm, yeah I may just have to pay the 100 then... but is that an insurance thing or a warranty thing? I don't have insurance
Do you think Sprint will even check for the S-ON?
Click to expand...
Click to collapse
i dont think its a warranty thing its insurance and i think your screwed
What happens when you put a pc36img.zip file on the root of your SD card and start up in bootloader?
I appreciate the people trying to help me... but honestly i've flashed a ridiculous amount of PC36IMGs. Both boot.img and recovery.img and then much more. This is more about, is there anyway I can return it to sprint and get another under warranty. Sounds like i'm out of luck.
So you cleared all the caches?
thanamesjames said:
I appreciate the people trying to help me... but honestly i've flashed a ridiculous amount of PC36IMGs. Both boot.img and recovery.img and then much more. This is more about, is there anyway I can return it to sprint and get another under warranty. Sounds like i'm out of luck.
Click to expand...
Click to collapse
What did you do that caused this issue? Or what were you trying to do? Also what hboot version do you have?
I've done "clear storage" I don't see a place to clear anything other than that in hboot.
thanamesjames said:
I appreciate the people trying to help me... but honestly i've flashed a ridiculous amount of PC36IMGs. Both boot.img and recovery.img and then much more. This is more about, is there anyway I can return it to sprint and get another under warranty. Sounds like i'm out of luck.
Click to expand...
Click to collapse
Pretty much. If you haven't tried yet, try re-rooting via toast's method.
http://forum.xda-developers.com/showthread.php?t=690762
Try going through the whole process. If successful make sure you have a nice stock ROM like the current Sprint Lovers ROM to flash.
Unfortunately my phone isn't getting listed as a device under adb, and thats part of the toast tutorial I have tried his eng-PC36IMG.zip, and it didn't work
woah woah woah....
take your phone to wal-mart and slide it over the demagnetizer at the register a couple times.
THAN take it in.
_MetalHead_ said:
What did you do that caused this issue? Or what were you trying to do? Also what hboot version do you have?
Click to expand...
Click to collapse
I had nightlies of CM7 they would reboot fairly often, but I just figured they were unstable. Out of nowhere it rebooted, and lost all my texts, and desynced my google account. I decided to switch to CM6. When i switched to CM6, soon after it rebooted out of nowhere, and then staid in an endless loop and never came out. I currently have hboot .76, for more fastboot commands.
Try this PC36IMG.zip. If it doesn't work the first time then try it again. If it doesn't work the second time, then I would say you're SOL. I know you said you've tried a bunch but they aren't all the same. It's the sprintlover's full update ROM.
_MetalHead_ said:
Try this PC36IMG.zip. If it doesn't work the first time then try it again. If it doesn't work the second time, then I would say you're SOL. I know you said you've tried a bunch but they aren't all the same. It's the sprintlover's full update ROM.
Click to expand...
Click to collapse
Is it from here? http://forum.xda-developers.com/showthread.php?t=830153
If so I've tried it
thanamesjames said:
Is it from here? http://forum.xda-developers.com/showthread.php?t=830153
If so I've tried it
Click to expand...
Click to collapse
Yep :/ I don't know what to tell you then man, sorry.
I guess I'm going to Sprint and playing stupid!
Has anyone done this successfully?
It sucks because as soon as I started having these problems, all the experts would be frustrated and say "*sigh* you're not bricked, you can get into bootloader" and so I was so sure it was fixable... but apparently not. Every time I mention it I have a thousand people yell at me "FLASH PC36IMG!!" Anyways thanks for the help!
like a week ago i came to the help thread because my nexus 4 got bricked while flashing THE CORRECT bootloader , and tomorrow im gonna send it in to get jtagged by the guy/guys at mobiletechvideos .
( http://mobiletechvideos.mybigcommerce.com/lg-nexus-4-jtag-brick-repair/ )
i heard they/he is really legit and that my phone should end up fixed , now im really worried that i should just leave my phone on stock and not tamper with it so i dont run into this problem again , but i REALLY REALLY REALLY like cyanogenmod 10.1
should i just give up on tampering with my phone for the sake of my money (low family income , i got the nexus 4 for income tax otherwise impossible) or is it really not a big deal and should i just flash cyanogenmod 10.1 ?
im not looking for a definite answer i just want some advice or opinions , thanks :good:
EDIT: btw i havnt purchased the repair yet either lol im waiting for my mom to get payed tomorrow then im gonna purchase the repair and ship in the phone to them/him on monday
Here http://forum.xda-developers.com/showthread.php?t=2147194 you can download the particular bootloader and/or radio in CWM format for the latest 4.2.2 rom.If you still are on 4.2.1 i suggest to flash the whole 4.2.2 image in fastboot from here https://developers.google.com/android/nexus/images#occam first. Then root and after that flash CM10.1.
gee2012 said:
Here http://forum.xda-developers.com/showthread.php?t=2147194 you can download the particular bootloader and/or radio in CWM format for the latest 4.2.2 rom.If you still are on 4.2.1 i suggest to flash the whole 4.2.2 image in fastboot from here https://developers.google.com/android/nexus/images#occam first. Then root and after that flash CM10.1.
Click to expand...
Click to collapse
My phone isn't repaired yet, I was just wondering if cyanogenmod is worth tampering with my phone. Just wanted to hear some opinions, because I decided to stay stock so I don't brick my nexus again but I really like cyanogenmod 10.1
EDIT:thanks for the bootloader link though I'll add that to my reference bookmarks
I think what gee2012 is trying to tell you is that your phone is probably not "bricked". If you can get into fastboot you can fix it yourself. If you have the money (which from the OP looks like you don't) then go ahead and send it to someone else to fix. If you want to save some cash start reading and once you learn how, do it yourself. That (extensive reading) should have been your first step before you flashed the first time.
Why were you flashing just the bootloader? My personal take on updating core components of the phone is to wait for a factory image and flash that in its entirety using Google's scripts and then restore a backup/flash a new ROM based on the new build. This way you know everything on the phone matches and you'll get the best out of it
Just flashing cm won't brick your phone it doesn't overwrite anything that can brick it
Sent from my Nexus 4 using xda app-developers app
grubbster said:
I think what gee2012 is trying to tell you is that your phone is probably not "bricked". If you can get into fastboot you can fix it yourself. If you have the money (which from the OP looks like you don't) then go ahead and send it to someone else to fix. If you want to save some cash start reading and once you learn how, do it yourself. That (extensive reading) should have been your first step before you flashed the first time.
Click to expand...
Click to collapse
ohhh no no no TRUST ME my phone is bricked , it like flashed a corrupted bootloader or something and it never came back on , just black screen , vol down and power (which is to go into fastboot) didnt do anything , plugging in a charger didnt do anything , the phone was just completely dead
SneakyGuyDavid said:
ohhh no no no TRUST ME my phone is bricked , it like flashed a corrupted bootloader or something and it never came back on , just black screen , vol down and power (which is to go into fastboot) didnt do anything , plugging in a charger didnt do anything , the phone was just completely dead
Click to expand...
Click to collapse
Well that can happen if you have no idea what you`re doing. Good luck.
Hi everybody, I enjoyed my stock N4 for almost a year and today several apps started to crash suddenly, after that the device rebooted itself and never got out of the bootloop. I immediatly booted into recovery and tried to wipe the cache memory and perform a factory reset but I cannot do either of the two, the error I get is something like "can't mount cache partition".
What should I do? How did this happen?!? I really need my phone back asap.
Thanks everybody!
Flash the stock images.
Chromium_ said:
Flash the stock images.
Click to expand...
Click to collapse
Ok I will but...How can this happen? A fully stock phone who never had a problem suddenly corrupts it's partitions?! (This is my understanding of the situation, correct me if I am wrong)
Thanks again for the link
Update: unlocking the bootloader works but when I reboot it appears to be locked again.
flashing the bootloader img file fails.
chikosneff said:
Update: unlocking the bootloader works but when I reboot it appears to be locked again.
flashing the bootloader img file fails.
Click to expand...
Click to collapse
sounds like your storage itself fails. thats the same issue that happens when the storage goes bad.
simms22 said:
sounds like your storage itself fails. thats the same issue that happens when the storage goes bad.
Click to expand...
Click to collapse
Thanks for helping, yes it looks like..so I can throw away my phone or there's something more I can try?
It feels so weird because it's one of the few phones I always kept stock, never fell, never had a single problem. Damn.
chikosneff said:
Thanks for helping, yes it looks like..so I can throw away my phone or there's something more I can try?
It feels so weird because it's one of the few phones I always kept stock, never fell, never had a single problem. Damn.
Click to expand...
Click to collapse
You could give this a try, but I really doubt it'll do much. I guess its worth a shot though.
chikosneff said:
Ok I will but...How can this happen? A fully stock phone who never had a problem suddenly corrupts it's partitions?! (This is my understanding of the situation, correct me if I am wrong)
Thanks again for the link
Click to expand...
Click to collapse
chikosneff said:
Update: unlocking the bootloader works but when I reboot it appears to be locked again.
flashing the bootloader img file fails.
Click to expand...
Click to collapse
Tried to Toolkit yet ? http://forum.xda-developers.com/showthread.php?t=1766475
Why did it happen? A phone is basically a mini computer, same as when you have to reload a computer OS sometimes,(failing hardware, bad app???)
Timboe73 said:
Tried to Toolkit yet ? http://forum.xda-developers.com/showthread.php?t=1766475
Why did it happen? A phone is basically a mini computer, same as when you have to reload a computer OS sometimes,(failing hardware, bad app???)
Click to expand...
Click to collapse
I'll give it a shot thanks, but I am afraid that the fastboot flash error is pretty clear :crying:
I get the phone being a computer, and I am totally ready to reload an OS...but I am not so ready to see the storage fails so suddenly leaving me with no phone, especially because this phone has received more care than any other phone I ever had..
Timboe73 said:
Tried to Toolkit yet ? http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
If its failing when he does it manually via fastboot commands, its very unlikely that using a toolkit will change anything. A toolkit simply runs the same fastboot commands behind a GUI.
Switched to windows to give the toolkit a try, then I will follow the unbrick procedure...I still cannot believe that this phone is lost without even having experienced the fun to mess it up with my own hands
chikosneff said:
Switched to windows to give the toolkit a try, then I will follow the unbrick procedure...I still cannot believe that this phone is lost without even having experienced the fun to mess it up with my own hands
Click to expand...
Click to collapse
As expected: toolkit not working. Since the bootloader " relocks" itself after rebooting the toolkit is unable to flash it afterwards.
Will try to contact google support but I am currently living in Europe I don't think it will be easy to get help.
Any other help is greatly appreciated. Thanks everybody.
1. if its within the warrenty period, this is something that would be covered.
2. its fixable. it can be professionally repaired, or you can try to do it yourself with the right parts.
but you will lose whatever you had in your storage, if you havent already.
another case reported :/
i think some batches of nexus 4 contains emmc brick bugs
just see this thread, more then 5 or 6 have been reported here.
http://forum.xda-developers.com/showthread.php?t=2259334
so after reading that thread i **** my self, because if this occured to my nexus i will have no warranty no google claims no nothing because i live in Pakistan.
So i ran emmc check app on my phone to check what it shows.
my emmc check shows i have "NO, Sane chip"
this means i am safe? if it give me "Yes, Insane chip" then i,m not safe according the my theory.
EMMC check app also shows the chip type, my chip type is "016g92"
googling this chip type i came across no specific results, one from S3 sudden death thread discussion. one person reports he have the 016g92 type and it is a safe chip according to other folks.
and one person having a galaxy s3 bricked his emmcs chip and claim the warranty. after the phone returns his chip type change to 016g92
http://smartphone.usofttech.com/t85915.html
so they change the emmc chip to 016g92.
can i surely assume that my nexus is safe from this serious hardware defect?
also any one here run the emmc chip and do give there chips type here, as i want to confirm if i,m safe or not. if not i,m going to sale my phone here. because the lose will be unbearable for me if the brick did occured
---------- Post added at 11:48 AM ---------- Previous post was at 11:37 AM ----------
simms22 said:
1. if its within the warrenty period, this is something that would be covered.
2. its fixable. it can be professionally repaired, or you can try to do it yourself with the right parts.
but you will lose whatever you had in your storage, if you havent already.
Click to expand...
Click to collapse
Dear Sir do advice me
simms22 said:
1. if its within the warrenty period, this is something that would be covered.
2. its fixable. it can be professionally repaired, or you can try to do it yourself with the right parts.
but you will lose whatever you had in your storage, if you havent already.
Click to expand...
Click to collapse
I still have 2 weeks of warranty left but I'll be in Europe till next year..I will try to ask the warranty service if I can send it in at my own expense.
Damn a worldwide warranty service doesn't look so useless now as it looked when I bought it :laugh:
PHONE BACK FROM THE DEAD!!!
So I got in touch with google's customer care to arrange the RMA and just to show them that my phone was impossible to recover I jumped ahead and told 'em: ok let's do a factory reset together so that I can show you what's the problem....
Fastboot>recovery>>data wipe....COMPLETED!
I cannot understand why did it work, I tried to wipe it at least ten times yesterday.
So now I have my N4 back working. What's your opinion on what happened? Do you feel like the problem is going to show up again soon? Is there anything I should do now that it's working? I just did a factory reset, not the cache wipe.
Just FYI: RMA from oversea is a pain in the ass, you have to ship the phone back to somebody in the U.S. and THEN ask for the RMA.
I wish I had your luck, mine did the same thing about 2 weeks ago. Couldn't get it to factory reset either. Mounting issue. My RMA came in yesterday. I'm enjoying the new phone though. It's even got the little nubs on the back. Mine original was a creaky 1st or 2nd batch one, I think. I will miss all the memories, pics, and data on my old one though.
SefEXE said:
I wish I had your luck, mine did the same thing about 2 weeks ago. Couldn't get it to factory reset either. Mounting issue. My RMA came in yesterday. I'm enjoying the new phone though. It's even got the little nubs on the back. Mine original was a creaky 1st or 2nd batch one, I think. I will miss all the memories, pics, and data on my old one though.
Click to expand...
Click to collapse
Since I feel this problem is hardware related I do not feel completely safe and I believe you were the lucky one getting the RMA
I had no choice, I should have sent the phone back to the US and then ask for the RMA...big pain in the ass
:fingers-crossed: let's hope this thing holds
Is there a procedure out there to run LOS with a locked bootloader?
You can't
koftheworld said:
Is there a procedure out there to run LOS with a locked bootloader?
Click to expand...
Click to collapse
No and don't try. You can get back to stock and relock with MiFlash though, so even if your screen breaks or somesuch you should be able to fix it
Choose an username... said:
No and don't try. You can get back to stock and relock with MiFlash though, so even if your screen breaks or somesuch you should be able to fix it
Click to expand...
Click to collapse
Thanks. I've done do on other phones, but I wanted to make sure here. I tried before I posted and got a boot loop. I didn't try flashing the stock recovery before hand, but I'm guessing it would be a bust as well. Thank you again for your answer.
koftheworld said:
Thanks. I've done do on other phones, but I wanted to make sure here. I tried before I posted and got a boot loop. I didn't try flashing the stock recovery before hand, but I'm guessing it would be a bust as well. Thank you again for your answer.
Click to expand...
Click to collapse
Did you recover from that? A lot of people did that and had to return it to ZTE. They change A2017Gs for free if it doesn't show the unlocked bl screen though (a.k.a if ir's blackscreened). just say it's not your fault
Choose an username... said:
Did you recover from that? A lot of people did that and had to return it to ZTE. They change A2017Gs for free if it doesn't show the unlocked bl screen though (a.k.a if ir's blackscreened). just say it's not your fault
Click to expand...
Click to collapse
Yeah it was pretty easy. I booted into that fix all recovery mode and installed a stock image through the mi recovery program. This is my first time with a ZTE phone, but have been with Moto since the og. Screwing with phones and recovering from bricks is part of the experience.
koftheworld said:
Yeah it was pretty easy. I booted into that fix all recovery mode and installed a stock image through the mi recovery program. This is my first time with a ZTE phone, but have been with Moto since the og. Screwing with phones and recovering from bricks is part of the experience.
Click to expand...
Click to collapse
Oh yeah, but on Motorolas (and some Samsungs, and some other oems) you have anti-bricking measures in place. I had a moto g2, damn near unbrickable. but here you don't have that, and you can DFU brick the phone. Look up the '4th category brick repair manual' and tell me if you still want to screw with the phone...
I got there, had to do the whole process. I even broke a couple of legs of the USB/vibrator module but everything works anyways (seems that the connector has 2 legs for each wire - i broke 2 unrelated) and touched something else while shorting the testpad for the 50th time -sparks flied and all- but it's working just as well as before. It's not impossible to recover from a brick but before doing anything (stupid or not) read everything there is to read about that. Don't do things that you could do on other phones...
Choose an username... said:
Oh yeah, but on Motorolas (and some Samsungs, and some other oems) you have anti-bricking measures in place. I had a moto g2, damn near unbrickable. but here you don't have that, and you can DFU brick the phone. Look up the '4th category brick repair manual' and tell me if you still want to screw with the phone...
I got there, had to do the whole process. I even broke a couple of legs of the USB/vibrator module but everything works anyways (seems that the connector has 2 legs for each wire - i broke 2 unrelated) and touched something else while shorting the testpad for the 50th time -sparks flied and all- but it's working just as well as before. It's not impossible to recover from a brick but before doing anything (stupid or not) read everything there is to read about that. Don't do things that you could do on other phones...
Click to expand...
Click to collapse
Well understood. I'm back unlocked on Los and staying that way. Thanks again.