/I had the touch recovery on there and cyanogenmod 10 I think.. worked fine for a year.
Then I wanted to format and start over, so I did a wipe of everything and now anything I try to flash gives me an error, I can still get into the touch recovery but every rom I've tried won't install, keeps saying error.
I'd like to just throw a rom on it and be done, or go back to stock.
Also, when I try to reboot from the touch flash program it tells me its not rooted and would I like to root it now, swipe to confirm or just exit to deny.
Try to rsdlite/sbf to 100% stock
Sent from my dlx using Tapatalk 4
do what? what does that even mean?
thanks
I hope you have your ROM on your sdcard, if so then "Format Data". You'll lose everything on your internal memory but it should solve your ROM errors, considering your ROM isn't the issue to begin with. Especially if you are trying to go from 4.3 back to 4.2. If it's on your internal storage, then you'll need to do alot more searching on how to use adb and fastboot or hope someone is willing to find it for you and post a link.
You might also what to mention what ROMS / version you are trying to install and what version Xoom you have. If you are trying to install the latest EOS Roms they don't work.
And just as every post mentions before flashing something new... do a Nand backup (backup in recovery).
As for your root issues, it's known for 4.3 and has been mentioned many times on these forums. Do some searches about it here or simply go back to 4.2.
The Xoom is pretty hard to brick.
Domunus said:
I hope you have your ROM on your sdcard, if so then "Format Data". You'll lose everything on your internal memory but it should solve your ROM errors, considering your ROM isn't the issue to begin with. Especially if you are trying to go from 4.3 back to 4.2. If it's on your internal storage, then you'll need to do alot more searching on how to use adb and fastboot or hope someone is willing to find it for you and post a link.
You might also what to mention what ROMS / version you are trying to install and what version Xoom you have. If you are trying to install the latest EOS Roms they don't work.
And just as every post mentions before flashing something new... do a Nand backup (backup in recovery).
As for your root issues, it's known for 4.3 and has been mentioned many times on these forums. Do some searches about it here or simply go back to 4.2.
The Xoom is pretty hard to brick.
Click to expand...
Click to collapse
I have nothing on my SD card or Internal Memory, its completely empty!
Every rom I try to flash gives me an error, I tried a few now and it won't work.
I'm at a loss of what to do
I have Twrp recovery ver 2.5.0.0
I tried to flash later version recoveries but I just get an error
what are trying to flash recovery with? should be using fastboot. with an unlocked bootloader, you, quite literally, CANNOT brick the device
also, ignore the idiot who talked about rsd. that would be beyond stupid.
because you can still get into recovery, you can use adb to sideload the ROM.
adb sideload /path/to/ROM.zip
Sent from my Nexus 5
notbrodie said:
what are trying to flash recovery with? should be using fastboot. with an unlocked bootloader, you, quite literally, CANNOT brick the device
also, ignore the idiot who talked about rsd. that would be beyond stupid.
because you can still get into recovery, you can use adb to sideload the ROM.
adb sideload /path/to/ROM.zip
Sent from my Nexus 5
Click to expand...
Click to collapse
Yes I can get into recovery. Where can I read up on how to use adb again?
I'd love to try that.
THANKS
just download the android SDK and pull adb and fastboot executables ( should be in android-tools). as I use Ubuntu, I don't use the SDK any more.
once you have the adb file, if you place it in the same directory as the ROM, you would just need to 1) open command line 2) CD to directory where the files are 3) in Xoom recovery, go to advanced > sideload 4) on computer, type adb sideload ROM.zip
this is will flash the ROM over. do the same thing for gapps. then reboot Xoom
Sent from my Nexus 5
Yea, problem is, what you're saying, makes no sense to me.
I downloaded android SDK installed the 500 meg program.. Now what
also, it seems I cannot get my computer to recognize my xoom.. I downloaded the drivers and all,comes up unknown usb device.
This just really BLOWS!
I went ahead and did some quick searches for you in google. Hope this helps you, if not, do more searches for ADB Sideload xoom rom. If you don't understand something during one of the steps, google it. BTW, you need to update your TWRP if you plan to mess with 4.3.
If you need a visual guide, go to youtube and type in adb sideload. Good luck.
This is a bit old, but it's simplified and may help you setup ADB.
http://www.xoomforums.com/forum/motorola-xoom-hacking-guides/1838-setting-up-adb-windows-7-64-bit-other-windows-platforms.html
This guide may also help you, it's for HTC but obviously change anything HTC related to Xoom. It shows you how to sideload with every detail.
http://forum.xda-developers.com/showthread.php?t=2317985
ok.. does it matter that no matter what I try no computer can recognize my xoom.. Always says unknown device.. I downloaded moto's drivers and everything.
While in recovery and going to mount it still never recognizes my xoom..
Tried in 2 computers, same results
Related
Hi everyone... I've tried searching and seen references to this kind of thing, but no download links or guides...
So I've got my Nexus S (bootloader unlocked, rooted, stock 2.3.4 until attempting the following, I have no Sim card in this phone), and I tried to flash 2.3.6, and while the update appeared to run just fine, the wifi won't turn on, just gives "error". So I attempted several things, reflashing the update, flashing the 4.04 update (which was the original point), etc, but they all give the following; installation aborted, assert failed, error in xxx.zip, "status 7".
Anyways... I'm a bit at a loss, I've never had this problem, or any problems flashing ROMs on other phones or updates. It seems no update.zip, or any .zip, will install. Back in my captivate days, there was a very handy program called Odin, and it had a master clear functionality that brought you back to the stockest of stock. Ideally... is there a tool like this for the Nexus S? I don't care about whether or not it re-locks the bootloader, I can unlock it again in just a couple minutes... but I need help.
I've read guides about "return to stock" but they all involve flashing a .zip. I need a way to push past that, and get back to 2.3.4, or alternatively, a way to completely reinstall 2.3.6.
I know an Odin exists for the Nexus S, but is there a way to use that to reset to stock?
Thank you so much anyone who can help...
Do you see an android and exclamation mark as you enter recovery? This means you have stock recovery and you cannot flash anything that hasn't been signed by google here. Stock is flashed on each boot on a stock ROM, you need to rename/delete /system/etc/install-recovery.sh to stop this.
If you don't have stock recovery, update to the latest CWM (touch or not is irrelevant) and try again. It's recommended to do a full wipe (data/factory reset, format /system and optionally format /boot) when doing a major ROM change (ie, CM to non-CM, GB to ICS, etc), and failure to do so could leave you with some interesting problems like that wifi issue.
And as always, make sure you backup properly before flashing -anything-.
edit to answer more questions: Odin is available for the Nexus S but near-useless. Fastboot can do just as much, and there are official fastboot images released by google to bring you back to a pure stock state. You'll just need an unlocked bootloader to do that, though you can relock straight afterward with no repercussions.
Harbb said:
Do you see an android and exclamation mark as you enter recovery? This means you have stock recovery and you cannot flash anything that hasn't been signed by google here. Stock is flashed on each boot on a stock ROM, you need to rename/delete /system/etc/install-recovery.sh to stop this.
If you don't have stock recovery, update to the latest CWM (touch or not is irrelevant) and try again. It's recommended to do a full wipe (data/factory reset, format /system and optionally format /boot) when doing a major ROM change (ie, CM to non-CM, GB to ICS, etc), and failure to do so could leave you with some interesting problems like that wifi issue.
Click to expand...
Click to collapse
Heh, yeah I guess I should have wiped previous to running this upgrade. I guess I was hoping data would preserve, because theoretically it should have been just like the Google OTA.
And I have CWM... I'm not sure if it is the latest version, but the phone can't get any data connectivity so I can't update it.
Harbb said:
edit to answer more questions: Odin is available for the Nexus S but near-useless. Fastboot can do just as much, and there are official fastboot images released by google to bring you back to a pure stock state. You'll just need an unlocked bootloader to do that, though you can relock straight afterward with no repercussions.
Click to expand...
Click to collapse
Ok, so fastboot is my solution. I've used that to unlock my bootloader, but little else (on a Mac, because terminal is super easy to use, but I've got PC access too). I've found the Google fastboot images, do you (or anyone reading this) know of a good fastboot image flashing guide?
Dareoth said:
Heh, yeah I guess I should have wiped previous to running this upgrade. I guess I was hoping data would preserve, because theoretically it should have been just like the Google OTA.
Click to expand...
Click to collapse
Some people supposedly had troubles with the ICS update and keeping all data as-is, though i've not experienced it myself, but it is definitely possible and with such a big update, if it's in your power to start fresh it is always the best option. It was more of a general statement, not directed at your situation - something to keep in mind
Dareoth said:
And I have CWM... I'm not sure if it is the latest version, but the phone can't get any data connectivity so I can't update it.
Click to expand...
Click to collapse
You can flash the latest CWM through fastboot from your PC or Mac, you can grab the latest file from here. Name it whatever you like and put it in a known folder (preferrably current folder) and : fastboot flash recovery recovery.img
Dareoth said:
Ok, so fastboot is my solution. I've used that to unlock my bootloader, but little else (on a Mac, because terminal is super easy to use, but I've got PC access too). I've found the Google fastboot images, do you (or anyone reading this) know of a good fastboot image flashing guide?
Click to expand...
Click to collapse
Of course i do
Great, I'm all set now. Thanks so much.
(Also for linking to that ref guide again, I had read it three times, but I didn't get how to use it until I went in going, I just need the fastboot commands, which is all that guide gives.)
Your welcome mate. All you need for that is setting up the android SDK or essentially downloading platform-tools seperately. There are guides all over the place describing how to do this for Windows, Mac and Linux as it is no different from getting oem unlock to work, they're just mostly disguised as rooting guides.
Once you do it the first time it's quite simple, but it can definitely be confusing before that
I'll preface this by saying the following:
I know there are a lot of brick guides out there, and most are relatively easy to get out of. I've worked myself into a bit of a pickle, though.
It started when I noticed that there was an update available through the CM updater. I figured, what the hell, I'm running a nightly and this is likely to be a stable release, so I went ahead and downloaded it. I got home and checked the get.cm page, and sure enough, a new, stable build had recently been released. Being the diligent soul that I am, I made sure to do a full backup before I installed the .zip. Everything worked out just fine, the backup went swell, the update finished without problems, and then I rebooted my device.
All I see is the Asus splash screen. It just stays there. So I think, no big deal, it just didn't work out like I wanted, I'll go format my data (which I didn't do the first time around, in hopes that everything would carry over) and install again. The same thing happens. I haven't started panicking yet, since I still have 3 backups (1 older Jellybean, and one much older ICS). None of them work. I wipe everything that I can think might help. Data, system, cache, dalvik, you name it. Nothing was working, and I was starting to freak out. Then I decided to try to get some action through fastboot, hoping that I could push a .zip that wasn't the CM10 update that had started everything. In my search for a push command, I thought it would be a good idea to try a wipe from fastboot. This wiped everything. Not only the system, boot, etc. partitions, but also my personal partition that had all of my data. This in itself isn't a big problem, but it also left the partitions unformatted. Now I have a device that is devoid of data and can't do anything but get into CWM and fastboot.
What the hell can I do? Am I doomed? Is there no way to get out of the hole I've dug myself into?
tl;dr failed update, things got really real, really fast.
Specs before the initial update
ROM: CM10 nightly, Jellybean 4.1.x
CWM: 5.5.0.4
Kernel Version (?): 9.4.3.30-20120604 (I'm not sure with this, it says something about "android carhu-user" before it)
same thing just happened to me. Im going to download another version of CM and try that. It might just be that.
DerangedLoofah said:
same thing just happened to me. Im going to download another version of CM and try that. It might just be that.
Click to expand...
Click to collapse
That's the thing, though, I have no idea how I'm supposed to get it to my device now...
http://forum.xda-developers.com/showthread.php?t=1989076
Have you tried this? I was just thinking about it because I can't reflash my recovery and thought this may be the way to start over.
OK I downloaded the us jb update and extracted to my external SD card and flashed it in recovery after wipes. Everything is good now.
Edit: flash recovery in fast boot.
Sent from my SCH-I535 using Tapatalk 2
Glad you got it!
nitsuj79 said:
Glad you got it!
Click to expand...
Click to collapse
DerangedLoofah managed to get it, but I still haven't had any luck.
DerangedLoofah said:
OK I downloaded the us jb update and extracted to my external SD card and flashed it in recovery after wipes. Everything is good now.
Edit: flash recovery in fast boot.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
How did you flash it in fastboot? I can't figure out how to get to something that's on the external SD card. What were the exact commands you used?
1. Download any software from this topic http://forum.xda-developers.com/show....php?t=1697227
2. Unpack it one so you have a zip without UpdateLauncher
3. Rename the zip to EP201_768_SDUPDATE.zip
4. Put on a sdcard into the root (the sdcard should be clean, no other files)
5. Boot you tablet to RCK (Volume down + power, then volume up)
6. Let the magic begin!!! Take some minutes.
Attention! JB user pleas choose a JB ROM, don't flash ICS ROM on JB bootloader.
You tried this method with no love? I was able to flash stock pretty easily doing this.
nitsuj79 said:
1. Download any software from this topic http://forum.xda-developers.com/show....php?t=1697227
2. Unpack it one so you have a zip without UpdateLauncher
3. Rename the zip to EP201_768_SDUPDATE.zip
4. Put on a sdcard into the root (the sdcard should be clean, no other files)
5. Boot you tablet to RCK (Volume down + power, then volume up)
6. Let the magic begin!!! Take some minutes.
Attention! JB user pleas choose a JB ROM, don't flash ICS ROM on JB bootloader.
You tried this method with no love? I was able to flash stock pretty easily doing this.
Click to expand...
Click to collapse
Does that work with CWM? I don't have the stock bootloader on it.
This works only if you didn't flash custom recovery, it is the best method for locked devices. But you can still flash any stock ROM from CWM (but I suggest to use TWRP, you can install it from external sd). And you can push the ROM to internal memory via adb. I think you can install stock ROM via fastboot too, I am not sure, but the command fastboot update should help.
I managed to get it working again. If you can get to fastboot, push a bootloader that supports an external SD cards (like TWRP) and then from that install one of the official ASUS firmwares. From there, you have to root again, but it's better than having a device that won't boot at all.
Hey guys new here. I've done a fair amount of searching and cant really find anything that describes my problem. Trying to root my AT&T HOX and failed to put CM10 on the drive before unlocking. Now I have TWRP up right now but when I go to mount and then mount USB storage my PC says that this drive needs to be formatted to work correctly. Honestly not sure what I should do here I tried using HASOON2000's all in one kit but couldn't find the data folder for it. So I started following Cursed4Eva's video tutorial. I have already went to HTC Dev and unlocked it. When I'm in the bootloader menu it says "unlocked" "tampered". Basically Im kinda stuck right now as to what I can do to get CM10 on the one x's drive. Sorry for the super noob questions. Thanks in advance!
Okay so I formatted my drive. I'm able to get into TWRP and Bootloader screen, I get stuck in an infinite loop of the HTC screen with a disclaimer on it if I try to turn my phone on normally. Not sure where to go from here. Do I need to put CM10 in a specific folder and then "install" it from TWRP? Really sorry for the newb questions but I thought that I could handle this and apparently I cant.
Inside of TWRP, there should be a Mount menu button that will allow you to mount your phone to your computer. Simply drop the ROM zip anywhere in that directory, unmount the phone, and choose the Install option on TWRP. Select the ROM zip file and see what happens. If you get errors of "unable to mount drive" or the like, you may have to reflash the factory RUU and start over. Did that my first time trying to flash, it's a little sucky.
You can also do this from the fast boot bootloader menu with adp push.
Well I forgot upload boot.img can I just do that right now and "install" it? Will it just install CM10 and I should be good from there? Not sure what the adb push is. I have a folder with the documents, boot.img, adb, adbwinapi.dll, and fastboot.
Okay update I got CWM-SuperSU-v0.96.zip installed so I have root access. I also have TWRP installed. I dont think that I have a Kernal on my phone or if it is then its not working correctly. In my bootloader screen it says **tampared** and **unlocked**
I might need to reflash the factory RUU (I assume Factory ROM?) and try again I guess.
You should just be able to select the entire zip and install that through TWRP. I've been told that if your hboot version is 1.14, you might have to fastboot the boot.img separately. The ROM/Kernel set I used both took care of that for me via Aroma installer, but it's something to keep in mind.
Well Im far to newb for this so I will try to put my phone back to RUU and try again another day! After doing more research I found some people say that TWRP 2.3 doesnt work for the AT&T 2.20 and that you have to use 2.2 TWRP. Can anyone confirm this? Also learned quite a bit from this failed attempt. Please tell me if Im correct, Need to unlock the phone with HTCDev, upload the boot.img via fastboot, install TWRP, mount the "sdcard" flash the rest of the rom? Does this sound correct?
I'm on 2.2 using twrp 2.3.1.0. From what I've read, different roms tend to recommend different recovery apps/versions.
As for the ordering of the install process, I would install the recovery first thing after rooting because you'll need that to flash superuser. A lot of installers will actually use superuser during the installation, so you'll want to make sure that's squared away first.
Sent from my HTC One X using xda app-developers app
So you just load the rom after you have your phone unlocked and the recovery app (TWRP) and SuperSU installed?
I really appreciate the help! Thank you!
Sounds like you got it, hope everything goes well. Good luck!
Sent from my HTC One X using xda app-developers app
So can anyone help me out here please. I have been looking online for hours now but cant seem to find a clear concise guide on what I need to do.
I am stuck in a bootloop on my TF300T, I am on the JB update.
I have unlocked my bootloader and installed TWRP with the intention of putting a cyanogen OS on my device. I tried installing CM9 through RCK and it ended up saying that the install failed for some reason, since this point I have been stuck in a bootloop. I have tried all of the different reset options on RCK with no luck at all. Stupidly I never made any kind of backup prior to this.
Basically, what I am looking for is an idiots guide to getting out of the bootloop, ideally ending up with CM9 installed but I will be quite happy with stock JB on the device. Please dont just link me to other threads or tell me to use the earch function as I have been doing this but I am unable to resolve the issue. Thanks in advance
so your Tf300 was on JB.
That said you flashed a Rom for the ICS Bootloader on a JB bootloader. Bad move.
Search for adb pusher here on XDA. Use it to push a JB Rom to your internal space.
Go in Recovery and flash the JB Rom with TWRP.
Ok I will try this and see what happens. Thanks
Sent from my HTC One X using xda app-developers app
So I have tried using Quick ADB Pusher but it is not able to recognise the device. I have entered Fastboot mode on the TF300T and connected it to the PC. Selected the CM10.1 ROM and chosen the file destination.
But ADB Pusher is not recognising the device so it wont let me copy the file accross
Nekrom4n said:
So I have tried using Quick ADB Pusher but it is not able to recognise the device. I have entered Fastboot mode on the TF300T and connected it to the PC. Selected the CM10.1 ROM and chosen the file destination.
But ADB Pusher is not recognising the device so it wont let me copy the file accross
Click to expand...
Click to collapse
UPDATE: I have managed to install CM10.1 but there are no icons apart from settings and camera. Assuming this is because it is a nightly build, trying to flash stock WW now to see if it will work
so it seems that no rom will install through cwm. stock just stops at bootscreen an CM only displays limited icons.
Does anyone have a link to a stable CM for JB?
was rooted on lollipop, tried to update to 2.2 but i think i installed the wifi version (i am an lte owner) tried to put the aosp rom on since i needed to wipe and start fresh anyways. Now i am on the aosp rom which changed my recovery the recovery that loads doesnt mount the sd card (and doesnt see the internal storage). I figure if i can just get back to another recovery i should be able to get back on track.
Scoobydumb said:
was rooted on lollipop, tried to update to 2.2 but i think i installed the wifi version (i am an lte owner) tried to put the aosp rom on since i needed to wipe and start fresh anyways. Now i am on the aosp rom which changed my recovery the recovery that loads doesnt mount the sd card (and doesnt see the internal storage). I figure if i can just get back to another recovery i should be able to get back on track.
Click to expand...
Click to collapse
Are you rooted? if so, with flashify, flash another custom recovery. I'd recommend TWRP 2.8.5.0. Its here, http://forum.xda-developers.com/shield-tablet/development/wip-twrp-2-8-0-1-unofficial-t2877117/ and its on the latest posts as zip attachment (you need to extract the zip, because it contains an *.img).
If not, (I have not tried this because I haven't got the need to do it)
you can flash TWRP 2.8.5.0 via fastboot, but you need to unlock the bootloader.
problem is i dont have gapps installed so unable to use flashify. When i try to use adb to install them i get error closed
then waiting for device.
tablet is showing in device manager as google galaxy nexus adb interface
so i believe drivers are installed correctly.
Scoobydumb said:
problem is i dont have gapps installed so unable to use flashify. When i try to use adb to install them i get error closed
then waiting for device.
tablet is showing in device manager as google galaxy nexus adb interface
so i believe drivers are installed correctly.
Click to expand...
Click to collapse
You could do the second solution. But I have never done it, so I cant help you with that, just with what I theoretically know.