[Q] I Really Screwed Up This Time....Major Screw Up - Xoom Q&A, Help & Troubleshooting

Well, I'm sure you've probably guessed by the tone of the title, I bricked my 3G Xoom MZ600. Don't really wanna get too much in depth on how I did so.​ But I will say this: I rooted my Xoom a few weeks back, and everything was cool. For some reason, tonight, I decided I wanted to revert back to stock. This way I could do all OTA updates, and get myself off of Honeycomb, and back to ICS, and then see what I wanted to do from then on. Well, my dumbass, DID NOT have my battery fully charged, and I had this wild ass idea that if I had my charging cable plugged in, everything would be ok as far as being able to flash all necessary *.img files to revert back to Stock. So I flash the first *.img file which was the boot.img This went completely fine, which led me to believe that continuing on would be fine as well....Not the case. I proceeded to flash the system.img file, and that's where things took a turn for the worse. For some reason the system.img file would not flash to my Xoom through ADB (kept saying FAILED). So what do I do? I panic. I try several ADB Commands thinking that the Xoom had come Unmounted from my PC. After trying different commands, and reading a few things, I was somehow able to get the Xoom to respond, but not in a good way. I apparently hit a button combo that reset my Xoom, and then all it would do is stay stuck on the Motorola M Dual Core Boot Screen. So then I panic again. I then press Volume Up + Power and then Volume Down + Power to get back into Fastboot protocol. I then try to flash the *.img files again, thinking surely it had been enough time on the charger, so I should be able to flash all files now. Not the case. I honestly can't remember what happened exactly next, but my Xoom started saying RSD MODE 3. At this point I stopped panicking and started completely tripping (I've heard of the elusive RSD MODE, Never actually saw it though, until now). I do some research (Google is my Best Friend), but hey, I'm a dumbass, and I start trying to boot into recovery and what not (didn't happen by the way). Got the Xoom to reboot again, back into fastboot protocol again, thinking to myself, I'll try flashing the files one more time. It's GOT to work this time. So I flash the boot.img, success! I try to flash the system.img, FAILED! So now I'm thinking, well maybe I don't necessarily need to flash the System.img file, and instead I just continue on flashing the other *.img files (recovery.img, and userdata.img). By the way, not sure if I made this clear, I'm a F**KING dumbass!) Well, I then get the files flashed, minus the system.img, I then for some reason, think it is acceptable to go ahead and Lock the F**KING BOOTLOADER(before having successfully flashed the system.img file. Yea, I know what you're ALL thinking (What the HELL is WRONG with YOU!?!?!?!) So, guess what happens next? Can you guess? My Xoom stays stuck on the Moto Dual Core Boot Logo Screen, I reset once more using Volume Up + Power, then try to go into Recovery, only to be told (In Red Letters):
Failed to boot LNX 0x0004
Starting RSD mode 2
OneWire: Charger is connected...
Battery Charge Level: 60%
Danny Xoom by DannyShane, on Flickr
So now I'm not really sure what the hell to do. I keep giggling a little bit to myself, but that could just be the liquor I'm now consuming because I am completely devastated that I could actually be so F**KING STUPID to go and do this to myself. I am at a total loss for words to be spoken out loud, for I feel as though a person as dumb as I should not be allowed to talk for a significant amount of time.​
ANY, and I MEAN ANY, HELP would be GREATLY APPRECIATED. I have been looking at random stuff about RSD Mode and so on, on Google since this has happened, which was about 25 minutes ago now (currently 2:08am Sunday April 14th 2013). All I have seen so far, are some posts, and other random things about Soldering a USB cable (which I have no idea how to do BTW) And a person with as little brain power as myself, definitely does not need to be screwing around with a Handheld Metal Melting Device, to "FIX" his electronics. Someone please Help! PLEASE HELP PLEASE HELP. I am going to go drown my sorrows in a bottle of rum. We'll see what tomorrow has in store for DannyShane and his beloved Stingray Xoom, See you tomorrow XDA.
For the love of all that is holy.....Please HELP!:crying::laugh::silly:

there ya go
1:Type "Fastboot oem unlock" and Enter: It will say "Waiting for device"
3: Immediately press'n hold "Vol- and power", when the Dual core logo appears. You will need to hold them down for 10-20 sec
2:Reset the Xoom (Power and Vol+)
4: After 10-20 sec you will see that the fastboot command gets through and you can unlock the xoom with fastboot oem unlock (MZ604 US)

As I know the only way to get out of this is with a "Factory Cable" or something, I never ran to RSD 2 to tell you what it is. I found this cable on ebay, not sure but looks it can work for you http://www.ebay.com/itm/150CM-5-ft-...014771?pt=PDA_Accessories&hash=item3a7b234f33

@Extremetempz, first let me say THANK YOU for such a quick response. I did have a question though, about the order of which you put the instructions:
1:Type "Fastboot oem unlock" and Enter: It will say "Waiting for device"
3: Immediately press'n hold "Vol- and power", when the Dual core logo appears. You will need to hold them down for 10-20 sec
2:Reset the Xoom (Power and Vol+)
4: After 10-20 sec you will see that the fastboot command gets through and you can unlock the xoom with fastboot oem unlock (MZ604 US)
The question I have is, am I supposed to do step 3 before step 2? Or was the step that is labeled as step 3 actually supposed to be labeled step 2? I just want to make sure I have it correct. Thanks again.

@XxLordsxX, hello again! Let me also say THANK YOU for such a quick response as well. I too have been looking at the Pre-Made Brick Fix Cables, because I honestly think I would end up screwing something else up by trying to make one myself. Not really sure that it is possible to do any more screwing up to my Beloved Xoom, but I'm sure I could find a way, ha.
Anyway once again thank you for the Shared Link, if I can't my Xoom to do anything based upon what Extremetempz explained how to do, then I will definitely bee looking at purchasing the Pre-Made Brick Fix Cable. I just hope it doesn't come down to that. Wish me luck.

DannyShane said:
@Extremetempz, first let me say THANK YOU for such a quick response. I did have a question though, about the order of which you put the instructions:
1:Type "Fastboot oem unlock" and Enter: It will say "Waiting for device"
3: Immediately press'n hold "Vol- and power", when the Dual core logo appears. You will need to hold them down for 10-20 sec
2:Reset the Xoom (Power and Vol+)
4: After 10-20 sec you will see that the fastboot command gets through and you can unlock the xoom with fastboot oem unlock (MZ604 US)
The question I have is, am I supposed to do step 3 before step 2? Or was the step that is labeled as step 3 actually supposed to be labeled step 2? I just want to make sure I have it correct. Thanks again.
Click to expand...
Click to collapse
yeah do the 3rd before second I've had this problem before

If you come to have the RSD Mode 3 problem again, you can check the FAQ (which points to my solution to solve it) or the link on my signature . RSD Mode 3 is quite a common things to happen, and to not cause further problems remember to download another system.img, because it's clear that yours is corrupted!

Thanks goes to both
First, I wanna say Thanks to both of y'all
Now, to update y'all: Unfortunately XxLordxX the cable that you spoke of was not really an option for me, simply because, A.) I can't wait for the whole shipping time and such. B.) I don't have the $$$ to buy one if that was an option for me either. C.) I know that there has to be an easier/alternative way to go about fixing a completely Bricked Xoom. So as much as I do thank you for the input, these were not really feasible options for me seeing as how I use my Xoom on a constant daily basis, and I needed it back up and running immediately
And Extremetempz, I want to thank you for your input as well, because even though I couldn't get your method to actually do anything for me, it did get me to rethink my situation, take a deep breath, sit down, and start going back through everything I have learned, and everything I have taught myself about my Xoom, ADB, Fastboot, Android, and Patience. I would have to say that patience was the big factor in all of this. After trying your method with no success, unfortunately , I tried a few other things, button combos and what not. Unfortunately at this point the Xoom was completely unresponsive when it came to having it connected to my PC through USB. I kept getting a blank list of attached devices in ADB/Fastboot. I know it would seem that this would have to be a case of Drivers not being installed on my PC, but this was not the case. So after moving the folder that ADB/Fastboot was installed to around I was finally able to get my Xoom to register through Command Prompt(ADB/Fastboot). I wasn't ever able to get it to give me anything other than blank list of devices. So I took a shot in the dark, and decided to try and flash the *.img files......And so it worked!!!! Success! And I didn't even have to download any new *.img files. Because despite what XxLordxX recommended (about me needing to re-download the *.img files) they were actually all working files, and Ta-Da!!! I now have my Xoom back to Stock, and fully OTA'd and back on ICS (@ the moment ). We'll see how long it takes me to get something else going on it.
Once again, I wanna thank the both of you for helping me as much as y'all tried to. I will be keeping XDA posted on any new news that may happen in my Android Journey.
Thank you, and goodbye.

Related

Phone is borked?

Hi guys,
My girlfriend somehow has borked her phone.
From what she's explained, she used Task 29 to wipe her phone, or something to that degree, and then tried to flash a GSM ROM to it. However she in on Sprint, so I assume it's a CDMA phone.
As of right now, the phone appears off. If you hold the power down, nothing. If you take the battery out, put it back in, and hold Vol Down it'll boot into the bootloader (I believe that's what it is, the colorful background thing) however the bootloader soon goes away and back to the black screen.
Sometimes the phone will randomly boot up to the HTC logo, and then back to blackness.
Does anyone have any idea what she's supposed to do at this point? Or what I should do to get a ROM on there? I have 0 experience with Windows Mobile roms, so I don't know what happened or what to do next. Guidance of what happened and what to do next would be appreciated so I can solve this issue and understand the situation past 'is it borked'
Thanks everyone
EDIT UPDATE: I figured it out. Her battery was dead lol however USB charging wouldn't work. I happen to have an external charger hah so I saved the day. I was now able to boot into the bootloader, have it stay there, and put a ROM on there. Easy Peasy.

[Q] Help? GTab won't boot

So I just got my Gtab. Literally, pulled it out of a box and plugged it in. I get the 3 birds, then I get the GTablet screen, and it just hangs there. It won't progress past that point. I haven't installed anything, haven't plugged anything in other than the AC adapter, this is quite literally right out of the box. Anyone have any advice for me? Should I return it for another one, or do I just need to be patient?
It does take a while the first time around.
Have you tried holding the power button down and power cycling it again?
That may do the trick
Did try this, it still seems to be taking forever. I'll just leave it be for a bit, I guess and come back to it. Just wanted to make sure mine wasn't defective. I'm not used to devices taking forever to boot.
Please define "forever" 10 mins? 1 Hr?
So far, it has been about 30 minutes on the gtablet screen. I tried restarting once at ~10 minutes, shortly after I posted this thread.
If you just purchased it, take it back and exchange it if you can without paying any extra.
If you don't want to return it or can't, you can try to recover with apx mode and an nvflash. Follow the instructions in the following link carefully, read it all twice to be sure you understand it. It works well for nearly all who use it. If it fails the first time, re-download all files and try again.
http://forum.xda-developers.com/showthread.php?t=861950
Also the first post in the following link to flash clockwork recovery when you flash bekit's stock images (Allows you to re-partition the sdcard, which can help fix this or any number of other issues, without having to boot into the OS)
http://forum.xda-developers.com/archive/index.php/t-932157.html
I would exchange it if it were mine.
I may be returning it. It isn't booting, and now that I think about it, I can do quite a bit more with the $400 if I put it towards something else. I was really looking forward to having a new tablet, so I'm gonna try to get it to work a few more times first.
Edit: Returned. The new one works fine.

Xoom won't boot up...

So, I was using fastboot to flash some recoveries for testing (EOS, rogue, cwm) and suddenly my xoom doesn't want to turn on (last command I issued was fastboot reboot and it never turned back on).
I have it plugged in and the charging light shows its charging. It was at around 80% battery so I don't think that's the issue.
Any help please? Any way to force a power on?
Try power button and volume up together...
Sent from my MZ601 using Tapatalk 2
Yeah, I've tried.
Tried just about everything at this point. Probably going to send it in for repair today.
Just keep trying hopefully u get it working again....i had same problem, i mean i couldnt powered it up and thought it was bricked, but after a 30mins and couple of tries more got it up again. Did full wipe of all data and since than enjoy fresh and clean JB xoom
Same problem!!!
I had the same problem testerday and till can't fix it. Please help. I was doing the reffered here http://forum.xda-developers.com/archive/index.php/t-995108.html and the problem appeared after step10 (Type "./fastboot reboot" (wait for reboot)), but it not reboot!!!! I just can see the motorola image from the beginning and that's it.
Please, HELP US!!!!
Nah, my xoom is a bit over a year old and its been heavily used. Not saying I throw it around or anything but I imagined it would have some sort of hardware malfunction eventually.
Just to be clear, I'm not even getting a splash screen or anything. No display at all and from what I can tell, no response from pushing buttons.

Will not finish booting up (pretty sure its NOT the pwr button)

ok so im working on a nexus 5. i was already all too aware of the potential power button issue so that was the 1st thing i checked out, ive cleaned it twice now and made dbl damn sure i can feel it both click in and click out when being pressed.
on top of that i can boot into twrp both temp boot and flashing recovery for it. it does not cut off when in twrp (as i imagine it would if it were the power button being stuck)
previously i could not boot into twrp or flash anything at all so i ordered and installed a breand new battery.. now i can flash twrp via fastboot (progress right?)
however when it is powered off, on teh charger it shows the battery full with lightening bolt, then that fades and is replaced with a hollow battery being filled, then goes black and starts over... leading me to believe its not taking any charge in..
ive tried stock 7.1.1, stock 7.0.1, stock 6.0.1, cyanogenmod 14 and even ran the NRT by Wugs... i have wiped everything, i formatted data and made sure the partition was correct pre-flashing by running NRT to return stock values n such, i have also tried different approachs to flashing. fastboot flash system, adb sideload, twrp install zip and NRT...
with my small (yet excessive) experience so far with android im led to believe this is being caused by some sort of conflict inside the system memory, it almost has a rythym to when it cuts off, like when it hits block such n such it goes "OUCH DAMMIT" and retreats for safety (powering off)
you'll have to forgive me for starting a new thread, the only info i can find pertains to the power button which i am fairly confident it is NOT, and after hours of searching tonight alone im really not for diffing thru every thread, i did however do a quick search prior to posting....
Where did you get the battery? Tried different USB cables and chargers? The phone boots and runs properly on stock?
I had a similar problem. I talked to LG customer support and they were aware of this issue and suggested that the whole logic board needs to be replaced. Apparently this is common with LG devices.
A workaround that worked for me is to turn off the phone for 1 day (let it cool down), clean flash whatever rom you like, then flash ElementalX kernel with the CPU under-clocked to minimum.
I have tried various ports and cords, battery from a top seller on ebay (checked reviews prior) and I cannot boot into stock Android either... During my extensive tweaking of the device last night I relocked the bootloader while returning to complete stock... After doing such I later tried some thing I saw suggested on the forums, removal of the power button.. so I desoldered it.. didn't change anything so it's def not the button... However now I cannot click the screen to confirm unlocking the BL again so I'm close to boned as far as flashing options ATM... Lol fail...
If it is a motherboard problem, and it sounds like it is, the cheapest solution may be to buy a used Nexus 5 with smashed screen and working motherboard. Swapping the motherboards is quite simple.
That's probably gonna happen, I don't see many other viable options .... It's not my phone so imma be putting money into someone else's to save face. U don't get a broke device back from me
Thanks guys

Stuck in "nothing" (not bootloop) cannot enter into recovery or fastboot

Dear all,
On my redmi 6, I was on android 8.1 (10.3.6.0 cereus precisely) and I prepared myself to try android 9
I had exactly this recovery recovery-TWRP-3.3.0-0423-REDMI6-CN-wzsx150.img and I did the necessary (backup everything) to be ready for the worse
Don't ask me why but I +/- remembered that recovery was tricky with android pie and I stupdly decided to flash the latest recovery I found on TWRP: twrp-3.5.1_9-0-cereus.img
Just after the flash I said reboot to recovery but: I'm in a "bootloop" not the one people have when booting in android, it's before!
Whatever the power or vol+ / vol- combination, long press power etc. , the screen is black it vibrates every 5 sec and I cannot enter neither recovery (i can understand...) NOR fastboot!
First time it happened to me to be stuck at this level. I do not know what to do, I tried desperate physical manipulations and crawl the internet meanwhile, but I do not see any trick, only solution is for an android bootloop, but not "early phone boot" (the 1 second before recovery or fastboot)
Can someone save me?
Hi, you've got your phone hard bricked, which means, that it coould be fixed, but it takes a lot of time to find a solution or you'll spend days trying to fix it, but its just gonna be a waste of time.
You can try methods that other people did, and maybe you'll get lucky, and unbrick your phone.
Other fix, is that you're gonna take your phone to an authoried Xiaomi store and hope for the best.
There are 10s of threads on hard bricks on Redmi 6 (for example: removing your battery for a couple of minues and putting it back, using SP flash (but you must have an authorized Xiaomi account, ...)).
If none of my solutions worked, I suggest buying a new phone. Redmi 6 is old and unstable after all (it didnt get MIUI 12 because of "performace issues"), so I guess thats the best you can do.
Im not really an expert for this kinda stuff.
I hope this will help you, but Im not saying that I could solve the brick.
Hi Sucharek,
I put the phone to the back of a drawer one week ago, because the vibrations every 30s where annoying. This afternoon I just "found" it again, likely out of power (no screen no vibration), and I charged it. Hopefully, it rebooted, not too far, as expected, but at least in fastboot mode and I was able to flash the TWRP and everything was fine!
With much more time and tools, I could have maybe follow one of your advice like removing battery, but I saw your replay 'too" late.
Strange and funny thing, I couln'd pass the pattern at the system lock screen. I can't forget it: it's the same I use on many phones. As this remdi was rooted, it was a piece of cake to remove the lock
So, in this story, I learnt that the fastboot is not a kind of secure sanctuary where you can go that easily...
edwin_r said:
Hi Sucharek,
I put the phone to the back of a drawer one week ago, because the vibrations every 30s where annoying. This afternoon I just "found" it again, likely out of power (no screen no vibration), and I charged it. Hopefully, it rebooted, not too far, as expected, but at least in fastboot mode and I was able to flash the TWRP and everything was fine!
With much more time and tools, I could have maybe follow one of your advice like removing battery, but I saw your replay 'too" late.
Strange and funny thing, I couln'd pass the pattern at the system lock screen. I can't forget it: it's the same I use on many phones. As this remdi was rooted, it was a piece of cake to remove the lock
So, in this story, I learnt that the fastboot is not a kind of secure sanctuary where you can go that easily...
Click to expand...
Click to collapse
Hi Edwin, Im glad to hear that your phone is back and running
For any of you other people that have this problem, I would recommend removing and replugging the battery, but remmember, there are more solutions you can find on XDA, that could fix the hard brick.
Also, for those of you that are willing to wait days, weeks, or even months and dont have the tools to open your phone and removing and replugging the battery, I would recommend checking out other solutions or just buying a new phone. Like I said before, Redmi 6 is old and unstable and theres a high change that you might get a hard brick, so if you want to install a custom ROM or a custom recovery, think twice before you do it and always have a backup phone.
I wish you all the best in solving your hard brick

Categories

Resources