Related
Following various threads here how to successfully unlocking and rooting their device, I've failed on so many levels.
At the moment I think my xoom is semi-bricked because its just stuck on the M screen. I've think I got the recovery screen working last night as I was able to go into recover mode but after updates through wifi I think it possibly stopped it.
So when i reboot and go into recovery mode, I get an exclamation mark over an android. I've tried rebooting and just got it to mount back on Fastboot but when I've tried to wipe it and reflesh it to (recovery-Tiamat-R4c-100611-1150-cwm.img) its not doing what its suppose to do and giving me "unknown partition, Failed to process command error (0x300003)
Any ideas what I need to do?
Btw, I can reboot, voldown and then volup to choose the 3 options but like I said I can't get into the recovery mode properly.
Schizophonic said:
Following various threads here how to successfully unlocking and rooting their device, I've failed on so many levels.
At the moment I think my xoom is semi-bricked because its just stuck on the M screen. I've think I got the recovery screen working last night as I was able to go into recover mode but after updates through wifi I think it possibly stopped it.
So when i reboot and go into recovery mode, I get an exclamation mark over an android. I've tried rebooting and just got it to mount back on Fastboot but when I've tried to wipe it and reflesh it to (recovery-Tiamat-R4c-100611-1150-cwm.img) its not doing what its suppose to do and giving me "unknown partition, Failed to process command error (0x300003)
Any ideas what I need to do?
Btw, I can reboot, voldown and then volup to choose the 3 options but like I said I can't get into the recovery mode properly.
Click to expand...
Click to collapse
Could I ask what steps in rooting you completed successfully and where exactly it went wrong?
Then, what exactly have you done to try to move forward?
Also, which guide did you use?
Don't worry, you're not bricked if you can get to fastboot.
okantomi said:
Could I ask what steps in rooting you completed successfully and where exactly it went wrong?
Then, what exactly have you done to try to move forward?
Also, which guide did you use?
Don't worry, you're not bricked if you can get to fastboot.
Click to expand...
Click to collapse
Last night I followed this videolinked in http://www.youtube.com/watch?v=OYc1lVWm7ks to Unlock OEM my device
I think that worked fine because it didn't throw up any hiccups.
I then followed this http://forum.xda-developers.com/showthread.php?t=1242241 to root it. It didn't have superuser so I downloaded it and installed it and then tried Terminal on the "SU" command. Said I did not have 'permissions'
This morning, I then followed this Youtbue link http://www.youtube.com/watch?v=ZsVpY0PDwtQ and after the first reboot of puting the new .img, it failed to reboot. Now I'm stuck on the M screen.
I think I managed to get my computer to pick up the device in adb fastboot because it responds to that. However when I type in adb devices it doesn't pick up anything...
Next after messing around I managed to flash it to the boot.img on this, http://forum.xda-developers.com/showthread.php?t=1049901
It flashed it ( I think) and worked without errors unlike the other flash I tried today, and its still stuck in M screen.
BTW, this is a UK Wifi Zoom.
Little update - I've downloaded and flash this boot: boot_3.1_insecure.zip from http://forum.xda-developers.com/showthread.php?t=1049901 and now boots up. However my Wifi has now disappeared. I'm in the process of doing a factory reset but will this work?
Still no avail - need to get this wifi working again soon. Think I've finally got access to superuser
Schizophonic said:
Little update - I've downloaded and flash this boot: boot_3.1_insecure.zip from http://forum.xda-developers.com/showthread.php?t=1049901 and now boots up. However my Wifi has now disappeared. I'm in the process of doing a factory reset but will this work?
Still no avail - need to get this wifi working again soon. Think I've finally got access to superuser
Click to expand...
Click to collapse
It sounds like you are on the right track. Hang in there, you'll make it!
Do you have access to an Ubuntu OS? when you connect an android device to a PC running Ubuntu it will mount the internal memory to the PC which makes it much easier to browse the partitions. Also, Go ahead and reflash the CWM recovery through Rom manager (if thats available to UK users) so that hopefully youll get a fresh recovery.img to work with. As far as ADB not noticing the xoom, you probably erased the adb drivers, and is the usb cord youre using 100% data transferable type? I about pulled my hair out a few times because adb wouldnt recognize my phone but realised I was using an older micro usb cable that only allowed electrical current for charging, not data transfer capable. You might also be able to find a clean nandroid backup file from a fellow UK xoom owner, that you trust, and see if they dont mind sending you their backed up boot-img and system-img. Just some guesses, but sounds like you got it pretty well figured out
Hello all, after a bit of self taught ADB and etc and understanding the mechanics how to successfully flash a Xoom, I managed to follow another guide from stratch (unlock oem, etc) and flashes it to the US stock 3.2.2 rom. It picked up wifi but couldn't connect for some reason - maybe different frequency?
Anyway since then I've installed one of the custom Roms here Team Tiamat Xoom Rom 2.2.2 and all is well now Got my Xoom back up and running with superaccess.
Thanks for all the info on this forum, great place for resource
Mind you, coming from a background with no experience with ADB, it was a bit mind boggling but I managed to get there in the end. Just a bit of feedback for those authors with the guides - maybe put a little subsection on the basics of how to get things prepared and up and running. This I think will help a lot of people who cannot sit for hours on end to trouble shoot something if it goes wrong. Most of the guides here are very useful and handy but at time I just kept saying to myself "wtf, what, where, huh?"
Schizophonic said:
Hello all, after a bit of self taught ADB and etc and understanding the mechanics how to successfully flash a Xoom, I managed to follow another guide from stratch (unlock oem, etc) and flashes it to the US stock 3.2.2 rom. It picked up wifi but couldn't connect for some reason - maybe different frequency?
Anyway since then I've installed one of the custom Roms here Team Tiamat Xoom Rom 2.2.2 and all is well now Got my Xoom back up and running with superaccess.
Thanks for all the info on this forum, great place for resource
Mind you, coming from a background with no experience with ADB, it was a bit mind boggling but I managed to get there in the end. Just a bit of feedback for those authors with the guides - maybe put a little subsection on the basics of how to get things prepared and up and running. This I think will help a lot of people who cannot sit for hours on end to trouble shoot something if it goes wrong. Most of the guides here are very useful and handy but at time I just kept saying to myself "wtf, what, where, huh?"
Click to expand...
Click to collapse
My guide, which is highlighted in the Xoom Heaven thread has a large section on setting up your adb files etc.
http://forum.xda-developers.com/showthread.php?t=1249798
Rooted 3.2 Xoom FAIL
Hi All,
Not the best way to join the boards but I am in deep....
I have a canadian wifi xoom on 3.2. I followed these instructions (How to root 3.2 on US WiFi & Verizon 3G XOOM! (Windows and Mac)) to root my xoom and was having issues with a wifi error.
I decided to use the Canadian boot.img file and when I rebooted the xoom got stuck on the moto logo and is no longer recognized by my computer.
I have tried resetting through the android recovery (I dont have anything 3rd party installed) but no luck. I am afraid that this thing is a total write off.
Any thoughts? Thanks
Blair
So like the genius that I am, I decided to mess with my Nexus S 4G. Right now, my PC will not detect my phone at all (won't show up at ALL, in my Device Manager or any toolkit that I've tried). Please note I had little experience and will probably look like a complete idiot, but bare with me.
So the steps I took were as followed (my phone came already unlocked)
1.) I first installed PDANet to get my computer to recognize my phone and install the right drivers
2.) After that, I flashed the latest, stable clockwork recovery mod
3.) Then, I downloaded the Hellybean ROM and installed it via clockwork recovery mod, with no problems
4.) I downloaded the Google Apps archive and dropped it onto my sdcard
5.) I then installed the google apps zip and then it all went down hill from then
Every time I turned on my phone, the nice Cyanogen mod logo popped up, and then once it was done booting up, it popped up with two error messages:
Code:
Unfortunately, the process com.google.process.gapps has stopped.
Unfortunately, SetUp wizard has stopped.
Both of these error messages will not stop popping up and my phone is currently useless at this stage.
So, I went back into fastboot mode, and tried to fix it with these steps:
1.) I downloaded the "Factory Image "sojua" for Nexus S (850MHz version, i9020a)" images, and followed the instructions on this thread
2.) Once I flashed the bootloader image, my PC no longer detected my phone. It won't show up on my device manages (not even as an unrecognized Android 1.0 phone)
I installed the bootloader image because it was apart of the tutorial on how to do a complete factory reset, I now know that was stupid and not necessary.
So, you can obviously see I didn't know what I was doing, and what I did was quite stupid and careless. So unless you have any suggestions or want to help me, please do not patronize me, I am already mad enough at myself.
With that said, I am unable to even flash anything to my phone anymore, and I don't know what I can do. I tried using Wug's Nexus Toolkit to try and install the drivers, but it won't detect anything. On top of that, I am not sure if I have even flashed the correct bootloader image. Any help or suggestions would be very much appreciated.
Carbon131 said:
So like the genius that I am, I decided to mess with my Nexus S 4G. Right now, my PC will not detect my phone at all (won't show up at ALL, in my Device Manager or any toolkit that I've tried). Please not I had little experience and will probably look like a complete idiot, but bare with me.
So the steps I took were as followed (my phone came already unlocked)
1.) I first installed PDANet to get my computer to recognize my phone and install the right drivers
2.) After that, I flashed the latest, stable clockwork recovery mod
3.) Then, I downloaded the Hellybean ROM and installed it via clockwork recovery mod, with no problems
4.) I downloaded the Google Apps archive and dropped it onto my sdcard
5.) I then installed the google apps zip and then it all went down hill from then
Every time I turned on my phone, the nice Cyanogen mod logo popped up, and then once it was done booting up, it popped up with two error messages:
Code:
Unfortunately, the process com.google.process.gapps has stopped.
Unfortunately, SetUp wizard has stopped.
Both of these error messages will not stop popping up and my phone is currently useless at this stage.
So, I went back into fastboot mode, and tried to fix it with these steps:
1.) I downloaded the "Factory Image "sojua" for Nexus S (850MHz version, i9020a)" images, and followed the instructions on this thread
2.) Once I flashed the bootloader image, my PC no longer detected my phone. It won't show up on my device manages (not even as an unrecognized Android 1.0 phone)
I installed the bootloader image because it was apart of the tutorial on how to do a complete factory reset, I now know that was stupid and not necessary.
So, you can obviously see I didn't know what I was doing, and what I did was quite stupid and careless. So unless you have any suggestions or want to help me, please do not patronage me, I am already mad enough at myself.
With that said, I am unable to even flash anything to my phone anymore, and I don't know what I can do. I tried using Wug's Nexus Toolkit to try and install the drivers, but it won't detect anything. On top of that, I am not sure if I have even flashed the correct bootloader image flashed. Any help or suggestions would be very much appreciated.
Click to expand...
Click to collapse
Good luck. Flashed a sojua stock ROM on a sojus phone, bootloader and all. I don't know if you'll ever be able to fix this. :|
polobunny said:
Good luck. Flashed a sojua stock ROM on a sojus phone, bootloader and all. I don't know if you'll ever be able to fix this. :|
Click to expand...
Click to collapse
Hopefully someone may know what to do.
Carbon131 said:
Hopefully someone may know what to do.
Click to expand...
Click to collapse
If you can put it into download mode you might be able to use Odin with a factory image to bring it back to life.
polobunny said:
If you can put it into download mode you might be able to use Odin with a factory image to bring it back to life.
Click to expand...
Click to collapse
Yeah I can't seem to do that.
Carbon131 said:
Yeah I can't seem to do that.
Click to expand...
Click to collapse
Make sure your cable is connected when you try to put your phone in download mode. Turn off the phone, then hold both volume + and -, and press power. Continue holding volume buttons until you see download mode.
Alright, I hate being that guy. You know, the one who posts the same question as 50 other people because he is too lazy to search. But in my defense, I have spent the last three days pouring over thread after thread and still can't find the answer, so please be patient and gimme a break!
So, I'm stuck in CWM 5.8.3.4 loop after flashing Katkiss and not knowing I couldn't use the "boot to recovery" option. I've got no access to my micro SD card and my x64 Win 7 won't recognize the TF101 so I can't put my own recover zip on. Cold boot goes to the screen that lets me boot Android or Wipe. If I pick Android, it hangs (for hours). I've wiped everything and reinstalled Katkiss, Revolver, Revolution, but I have the same problems.
Is there a thread that starts from the BEGINNING of the fix and sees it through? I've found dozens of threads that say, "Just input (code), flash, and you're done!", but I guess I'm not that far along. I've bricked Dinc/Dinc2, Razrs, etc., but never had trouble fixing them like this TF101.
I've got ADB, JDK, Ubuntu, etc. since I've tried numerous times. Also, I've had no luck with the one-touch fixes. I know I'm missing something easy, I just can't figure it out.
Thank you.
Incidentally, I've tried ***http://www.transformerforums.com/fo...ry-bootloop-fix-tested-my-c10-windows.html*** , but the SDK files come in a zip, not exe and none of the files execute/install in such a way that will let me input commands. I know I'm missing something because a soft brick isn't that big of a deal.
Huh. I don't know what happened, but it involved me cleaning the screen, accidentally pushing buttons, and rebooting, and now it works. No clue, but as long as I never shut it off again, I'm set!
You're gonna need to get the PC to recognise it to fix it I'd say
Easiest way would be using Easyflasher to get TWRP recovery installed, it sounds like you have stock recovery installed at the minute
http://forum.xda-developers.com/showthread.php?t=1688012
Few people have needed new cables to get the PC to recognise the TF again, might just be needing the correct drivers though which are also linked on that page
Basically install the drivers, put the TF into APX mode,
(Vol Up & Power from powered off state while plugged into the PC)
Then run Easyflasher as admin and choose to flash TWRP (CWM is probably the reason for the bootloop, it doesn't play nice with JB ROMs)
Once you have TWRP installed, flash whichever ROM you want from new recovery and you should be good to go
I appreciate the suggestion, but that isn't doing it. I have the tab booted up and recognized by Windows, but when I try to update to a different CWM or TWRP, nothing happens. I can reboot into CWM 5.8.3.4 all day, but it won't say anything about any different recoveries I've tried to install, though the recoveries appear to be installing correctly according to the dialog given on the tablet.
I've also tried running NVflash, but nothing happens (apx drivers installed). The BAT file briefly says USB not recognized and closes.
Further, I've tried Easyflasher / one click root+recovery and I just get messages saying "ADB server out of date. Killing." The tab still reboots, but upon rebooting, it gets stuck in CWM 5.8.3.4 unless I force cold boot.
I guess the best way to describe this is to say that no matter what I do with the tab or different recoveries, I can't get rid of CWM 5.8.3.4 and no matter what I do, it default boots into CWM.
It default boots into CWM.... I think that is the key here
I remember something about that from a while ago, having to hold Power & Volume Down to boot normally, as if the OS and Recovery partitions were reversed
Unfortunately I can't remember the solution atm, but if you head over to transformerforums.com or give frederuco a PM from here or over there, Im pretty sure I remember him having a solution some time back
I shot him a message. Thanks for the suggestion.
I swear all I did was root, install Katkiss, and reboot into recovery. Is this a common problem to have THIS much trouble with such a simple process? I know now that booting into recovery can cause a loop, but this seems like way too much.
It's having CWM as your recovery when you flash a JB ROM that causes the problems
CWM & JB = Problems
TWRP is the recovery to use once you get out of this mess, good luck
So I wanted to see how my phone would be in stock firmware / software for a while to use some streaming services flawlessly for a while. The problem is the guides to do so dont seem to be working with my Cyanogen Recovery.
When I try certain guides that recommend using Fastboot or Mfastboot , the device is not authorized or recognized outside of Apply update> ADB sideload. Im guessing its because i need to activate USB debugging. The problem is i already factory reset so the only thing in the phone right now is last weeks NGHTLY mod, and I cant open debugging options without settings freezing. So im technically locked out of USB debugging menu in the phone because it freezes.
I tried loading a few different Zips to see if the phone would take ANYTHING (follow a few guides) and none of them work. A white word saying "error" pops up. I remember one time one of the errors said "footer is wrong".
Anyone have any ideas or run across this situation before? Id be willing to start over with things i've already tried to give you detailed answers about any errors i run into but id appreciate the hand holding since Im generally lost when the guides stop working and I barely have any error messages to google off of.
TLR INFO
Phone: Moto g3 2gb ram 16gb storage (1540)
Cyangenod Recovery
I can get into bootloader
I can get into Cyanogenmod recovery but get a white text saying "error" when loading zips.
I can load the phone with last weeks NGHTLY mod but i cant access USB debugging because the phone seems to freeze when i access develoption options. Almost like its loading insanely slow.
I would suggest factory image here
http://forum.xda-developers.com/201...to-g-factory-firmware-images-t3169639/page160
However I've never used cm recovery.
You could try the more versatile TWRP recovery, and may have better luck with whatever you are trying to do
hossman said:
I would suggest factory image here
http://forum.xda-developers.com/201...to-g-factory-firmware-images-t3169639/page160
However I've never used cm recovery.
You could try the more versatile TWRP recovery, and may have better luck with whatever you are trying to do
Click to expand...
Click to collapse
yeah thats the problem. whenever i load one of these it just says error and stops. ill google how to load twrp recovery and see if i have better luck
edit: this is my issue mainly. i cant enable usb debugging so i cant do the CMD commands to install things like TWRP recovery. do you guys have any alternative to that? Im looking things up in google without much luck
edit: so this is as far as ive gotten since im forced to use this cyanogenmod recovery. no matter what i try to run i get "Verification error" and if i try to install Gapps i get "error 20" and i still cant access usb debugging because it freezes. Any idea on a fancy way to get around this verification issue? Guides suggest using a different recovery but it doesnt seem possible without the google play store or USB debugging.
yeah im not able to do anything without getting verification errors and without a different recovery i cant seem to disable it. hope someone has a direction to point me in.
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
recovery isnt used since its being updated itself.. duhh
go to bootloader and fastboot flash the firmware files
follow the tutorial above /\
HelpMeruth said:
http://forum.xda-developers.com/2015-moto-g/general/guide-fastboot-flashing-factory-t3187750
recovery isnt used since its being updated itself.. duhh
go to bootloader and fastboot flash the firmware files
follow the tutorial above /\
Click to expand...
Click to collapse
oh cracker jacks that did it. im so dumb. whats worse is sometimes i think about learning a programming language and then i see stuff like this and recognize absolutely none of it and just say "forget it.". thanks for the guidance man. if theres something i can do other thank hit the thanks button let me know, you guys are like the free clinic of the internet.
I am trying to resurrect my tf101. This is my starting point. Some time ago I installed cm10-20130929-NIGHTLY-tf101 into my tf101 using twrp. That installed fine but in the process something happened and I cannot boot into twrp I can now only boot into CM by holding the power button and volume up. I was not able to install gapps . Also I think my bootloader is corrupted because if I try to boot into it I just get a blank screen. I was able to install the Official TWRP App and can run it but it crashes every time "Unfortunately the app has stopped".
I am about ready to throw this laptop out because I have tried many options on this board and nothing worked. I can connect the tf101 to my computer and I can see it in device manager and I can open the laptop in file manager. I would even be willing to wipe the entire laptop and start from scratch but I don't know enough how to do this.
Any help or suggestions would be welcome.
Hi. First, I'll explain to you that for 10 years I had no contact with flashing phones. I didn't have any problems with the previous models. So I stopped somewhere at the level of the Samsung Galaxy S3-S4. Some time ago I decided that I would bring two Asus tf101s back to life and install a new KitKiss ROM on them. I set to work confidently. Turns out it's not that simple. I can do nothing. Some of the links have expired and the tips seem outdated. I can not upload a new recovery or even root the device. Strange things are happening. First of all, after turning on the device in recovery mode, after some time it goes into system boot and exits recovery. I've tried many ways and I don't understand any of it anymore. In the command line (CMD) it seems to see the device but does not want to respond to any commands, even to "adb reboot fastboot". I can do like this :
1. Ask for simple instructions for a "boy" and current links to the necessary files.
2. Look for someone who will perform a miracle and install the required Android for me.
Will someone help me?