Related
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.
This rooting crap used to be easier man, I swear. I think I literally rooted my Evo through the web browser. Whatever...anyway, it just seemed a lot less riskier back then. I havent had an Android phone since then so I was happy to see my One S come in the mail. Right now though, I'm hoping I didn't waste my money. I'm gonna try to retrace my steps as explicitly as possible so someone can help me easier.
1. Unlocked the bootloader thru HTC Dev
2. Used this to root
3. Install recovery, TWRP.
4. Downloading CM10.2 ROM and Gapps to flash thru TWRP.
5. Cant mount sdCard. The mount screen in TWRP gives you 4 check box options, cant check 'mount sd'
5a. (Can boot phone as normal until now. Was on stock rooted rom with no problems but I hate sense and wanted to switch)
6. Wipe everything; data, cache, dalvik, sd.
7. Cant see SD Card at all now. No OS. Stuck on white HTC startup screen if I dont go to bootloader/recovery.
8. At this point I just tampered around with random solutions from threads I found on google, now I can see my SD card in TWRP file manager but its still not mountable (Even when I could check 'mount sd' windows doesnt see anything).
9. Tried relocking bootloader, running RUU, error code 155.
10. Right now, stuck with tampered unlocked bootloader, s-on, cant install rom because sd card wont mount and cant push ruu because it errors within 2 minutes. This was from last night, and I havent touched it today, and I wont touch it until someone who actually knows what they're doing can tell me whats up.
help
Hi,
I had a similar issue.. I followed a tutorial on YouTube and the guy forgot to mention that the ROM needs to be on the SD before rooting.
And my device was not reconised by my computer (win 7).
I messed around with a few recovery's.. turned out i was using a older version and after flashing about 3 recovery's my computer reconised my device when mounting SD card.
Hope this helps.
cfagan17 said:
This rooting crap used to be easier man, I swear. I think I literally rooted my Evo through the web browser. Whatever...anyway, it just seemed a lot less riskier back then. I havent had an Android phone since then so I was happy to see my One S come in the mail. Right now though, I'm hoping I didn't waste my money. I'm gonna try to retrace my steps as explicitly as possible so someone can help me easier.
1. Unlocked the bootloader thru HTC Dev
2. Used this to root
3. Install recovery, TWRP.
4. Downloading CM10.2 ROM and Gapps to flash thru TWRP.
5. Cant mount sdCard. The mount screen in TWRP gives you 4 check box options, cant check 'mount sd'
5a. (Can boot phone as normal until now. Was on stock rooted rom with no problems but I hate sense and wanted to switch)
6. Wipe everything; data, cache, dalvik, sd.
7. Cant see SD Card at all now. No OS. Stuck on white HTC startup screen if I dont go to bootloader/recovery.
8. At this point I just tampered around with random solutions from threads I found on google, now I can see my SD card in TWRP file manager but its still not mountable (Even when I could check 'mount sd' windows doesnt see anything).
9. Tried relocking bootloader, running RUU, error code 155.
10. Right now, stuck with tampered unlocked bootloader, s-on, cant install rom because sd card wont mount and cant push ruu because it errors within 2 minutes. This was from last night, and I havent touched it today, and I wont touch it until someone who actually knows what they're doing can tell me whats up.
Click to expand...
Click to collapse
Okay First I don't whether you have an S3 version (VilleC2) or an S4 version (Ville).
Understand this, when you format SD card using TWRP recovery, you can't mount it. It is because only the Stock HTC recovery is able to format the SD correctly.
What you ought to do now is:
1. Download stock HTC recovery for your phone version, S3 or S4.
2. flash the recovery through Fastboot using the command:
Code:
fastboot flash recovery recovery.img
3. Go to bootloader and select the option to erase Storage; if it's not there, then you will have to select Factory Reset, wiping your data and apps too.
Regards
Just use this - http://forum.xda-developers.com/showthread.php?t=2471151
It will almost do all things for you, Unlock Bootloader, Flash recovery, Root ...
And remember, if abd console says "error: device not found" or when downloading and fail install "HTC MTP drivers" don't worry, it happened to me too.
Remember, you need flashed Recovery, to be able to Gain Root. And Unlocked Bootloader to flash Recovery.
Now I am back to original stock ROM, rooted.
Windows still not recognizing SD card after mount. it gives option to mount internal_sd, but folder that sd is located is called 'sdcard'? I flashed stock recovery, clear storage, then factory reset, then root, then flash twrp.
Even when I put a custom ROM and gapps on the sd through stock ROM, it bootloops after flash. It's like HTC really doesnt want me to appreciate anything other than their crap stock firmware.
cfagan17 said:
Now I am back to original stock ROM, rooted.
Windows still not recognizing SD card after mount. it gives option to mount internal_sd, but folder that sd is located is called 'sdcard'? I flashed stock recovery, clear storage, then factory reset, then root, then flash twrp.
Even when I put a custom ROM and gapps on the sd through stock ROM, it bootloops after flash. It's like HTC really doesnt want me to appreciate anything other than their crap stock firmware.
Click to expand...
Click to collapse
Rooting the stock is not necessary flash a custom rom. Most roms that you flash are already rooted and root should be flashed in twrp if you just want a stock rooted rom
Flash the stock recovery, clear storage and factory reset. Then flash TWRP. If that doesn't boot for some reason you may need to flash the stock ruu.
If you chose to keep the stock firmware, you can download the superuser.apk from the playstore. When you run the app it will give you the option to reboot into TWRP to flash the root automatically.
mjsheldon4 said:
Rooting the stock is not necessary flash a custom rom. Most roms that you flash are already rooted and root should be flashed in twrp if you just want a stock rooted rom
Flash the stock recovery, clear storage and factory reset. Then flash TWRP. If that doesn't boot for some reason you may need to flash the stock ruu.
If you chose to keep the stock firmware, you can download the superuser.apk from the playstore. When you run the app it will give you the option to reboot into TWRP to flash the root automatically.
Click to expand...
Click to collapse
Even after clear storage, factory reset and TWRP flash I still cannot see the SD card in Windows or install a custom rom without white HTC bootloop. Only way I can mount the SD card is on the stock rom.
Also, Win says SD card is 10GB. Does everything else really use up 6GB?
cfagan17 said:
Even after clear storage, factory reset and TWRP flash I still cannot see the SD card in Windows or install a custom rom without white HTC bootloop. Only way I can mount the SD card is on the stock rom.
Also, Win says SD card is 10GB. Does everything else really use up 6GB?
Click to expand...
Click to collapse
What CID do you have. Have you matched the RUU with the your CID. If the CID's don't match it will give you and error and not flash. If you are SuperCID you can flash any RUU but with a stock CID you need the RUU that matches it.
mjsheldon4 said:
What CID do you have. Have you matched the RUU with the your CID. If the CID's don't match it will give you and error and not flash. If you are SuperCID you can flash any RUU but with a stock CID you need the RUU that matches it.
Click to expand...
Click to collapse
I already flashed RUU. I can't flash a custom ROM.
I don't see here. Are you s-off or on?
Sent from my CM 10.1 Motorola Xoom Wingray!
mjsheldon4 said:
I don't see here. Are you s-off or on?
Sent from my CM 10.1 Motorola Xoom Wingray!
Click to expand...
Click to collapse
On
/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
My old phone got lost so I am using my Infuse again. I decided to update it since it is still on the old version from when it first came out. I was trying forever to update through the kies software until I realized I rooted it and so this won't work. So then I found out there are roms for way better versions anyways. So I found the Cyanfox rom and I wanted to do that, but I needed to first upgrade to cm9 so I went and downloaded the cm9 file and got the clockworkrecovery, and I installed it.
Now my phone will not turn on, it sits as samsung screen. And if you try to go to recovery it is just a messed up screen with all different colors as if the screen was broken. So now my only option to bea ble to install anything on it is through odin. I can get to download mode fine.
But this damn odin software will not detect my phone for the life of me. It literally will not work. I don't understand. I have spent hours upon hours on this between the past few days. I just want to update my damn phone.
Now I have to leave for work in 30 minutes and my phone doesn't work. This is just great.
How did you install CWM?
Sent from my Asus MeMO Pad 8"
Well I tried clockworkmod through the rom manager app, but I was running the android recovery 3e and it said I needed a modified version of that to be able to install 3e. So I replaced the recovery file with the one I was given, and then I manually installed cwm by naming it update.zip and running it on the recovery
The only problem was that every time I wanted to use cwm, it would go back to android recovery 3e, and I would have to click install again to get it to go into cwm.
Either way, it doesn't work anymore and I just need the damn thing to connect to Odin so I can flash it back.
Are you using a desktop or laptop? If desktop, are you using the USB ports in the back? If laptop, have you tried different USB ports? Maybe try a different computer? I've heard that USB 3.0 doesn't play nicely with ODIN so it's good to find some 2.0 connections. What Windows version? I've heard that Win8 can cause problems. Could also try Heimdall instead of Odin.
Unless I think of anything else, is the cable in good working order (recent successful file transfer)?
Alright. I got things working somewhat. I had to use different drivers for each program for it to be able to detect it. I don't know, its annoying as hell, but it worked when I went back and forth between drivers.
Anyways, I got my device restored. But the whole point of this was that I was trying to get to the KitKat rom(Cyanfox). I am still quite a few steps away from that. I am actually further away than when I started,
This is what originally happened: I had my device rooted(from when I last used it, 1-2 years ago) and had the 3e recovery. So I found out I needed a modified 3e so I could install Clockworkmod. Got that, all was well, and the thing basically got bricked when I went to update to a new rom. It wasn't the kitkat rom, but a CM9 rom that I needed to go to first so that I could then update to kitkat.
Now I got it unbricked, and I updated it using kies. So now I am on gingerbread. So then I rooted it again. So now I have the 3e recovery again, the only problem is when I go to system/bin/ there is no file called recovery, and I can put one there but it does not affect the recovery, it still looks for signed files, meaning I cannot install Clockworkmod.
Not sure what to do...
Seems everyone follows this process (looks like you already did step one) now....
1. Either use Odin or Heimdall One-Click. Follow instruction on how to do it.
2. While phone running install sgs kernel flasher from Market/Google Play.
2a. Copy/transfer Synthesis GB Kernel to your Internal SD card.
2b. Start up sgs kernel flasher and choose it from your Internal SD card. Phone will auto-reboot after done flashing.
2c. Wait a bit while your phone convert to new partition format and activate lagfix. Your CWM recovery version should be 2.5.1.3
3. Reboot phone into CWM Recovery and DISABLE vodoo lagfix and /system lagfix. Reboot once done. Phone will convert partition to old format. If you don't turn the lagfix off the phone will hang at Samsung logo when you install new rom.
4. Prepare your flavor rom/gapp for installation by copying them to your Internal SD card.
4a. Go into CWM Recovery mode and install the rom. You will need to do this twice since the 1st time was just a warning about partition format being different.
4b. Reboot once done. You will need to REMOVE the battery to power down the booting process and put it back in.
4c. Go into the New CWM Recovery and install the rom again since the previous attempt only install the new CWM Recovery.
5. Install Gapp.
6. a. Wipe: Cache / Factory Reset <--- Probably don't need it since it's new install from stock unless you installed stuff. Just to be safe.
b. Wipe: Cache Partition
c. Wipe: Dalvik Cache
7. Reboot
Click to expand...
Click to collapse
I never tried step two myself, as I found a flashable download for ODIN that did this for me. But mine is a Rogers phone (not AT&T) so that would not work for you. Hope this helps.
Thanks you so much man. I know that is just copy/paste but I didn't see it, and it works. I was looking in Cyanfox thread, never looked at the Beanstalk thread.
Anyways I am in the process of doing this and it seems like it will work. Appreciate all your help!
Edit: Boom. Worked like a charm. Thanks so much. I am very happy now The funny thing is, half the reason I wanted this is cause everyone was group messaging, and I didn't have that capability anymore when I lost my phone(I was on such an old version). Again thanks so much.
Hi all, i tried to install Chainfire 3d (don't ask me why) in the procces a message camed "If this image don't dissapear in 2 minutes pull out battery" i waited like 10 minutes, and then i tried to reboot, and then the bootloop camed. I have an HTC One S [S4] with Android 4.2.2[Maximus HD 10], CWM Recovery and S-Off done. I need to mention that i've tried everything with that chace wipe and nothing happend. I would be very pleased if someone could help me.
Sorry for my bad english.
vLaDxB said:
Hi all, i tried to install Chainfire 3d (don't ask me why) in the procces a message camed "If this image don't dissapear in 2 minutes pull out battery" i waited like 10 minutes, and then i tried to reboot, and then the bootloop camed. I have an HTC One S [S4] with Android 4.2.2[Maximus HD 10], CWM Recovery and S-Off done. I need to mention that i've tried everything with that chace wipe and nothing happend. I would be very pleased if someone could help me.
Sorry for my bad english.
Click to expand...
Click to collapse
Re-install Maximus.
tivofool said:
Re-install Maximus.
Click to expand...
Click to collapse
Tried, CWM Recovery can't mount sd card, tried to fix that, not working, my windows 8.1 can't find my device.
vLaDxB said:
Tried, CWM Recovery can't mount sd card, tried to fix that, not working, my windows 8.1 can't find my device.
Click to expand...
Click to collapse
Is that CWM recovery a modified one that will work with the new firmware that you need for Maximus?
I don't keep up with all the new stuff, but the TWRP provided in the install of Maximus is special. If your CWM is "special" too, then ok.
Now the special TWRP provided with Maximus unfortunately doesn't move files from pc to the phone. I know that sucks.
If you knew all this and your sd card partition has really been corrupted then you will need to install stock recovery. Once that is installed you go into BOOTLOADER and select clear storage.
From there you will need to run an RUU to get back to stock. (so that you can move a ROM from pc to sd card ) then do the whole Maximus install all over again.
if you don't have an RUU that will work you can install the firmware http://forum.xda-developers.com/showthread.php?t=2322755
This will bring you back to the old 2.15 hboot and older partitions so you can install the 2.15 roms to get a working phone to do what you want.
Alternatively, you could learn what adb push is and that will allow you to move files from pc to your phone on the "special" recovery.
tivofool said:
Is that CWM recovery a modified one that will work with the new firmware that you need for Maximus?
I don't keep up with all the new stuff, but the TWRP provided in the install of Maximus is special. If your CWM is "special" too, then ok.
Now the special TWRP provided with Maximus unfortunately doesn't move files from pc to the phone. I know that sucks.
If you knew all this and your sd card partition has really been corrupted then you will need to install stock recovery. Once that is installed you go into BOOTLOADER and select clear storage.
From there you will need to run an RUU to get back to stock. (so that you can move a ROM from pc to sd card ) then do the whole Maximus install all over again.
if you don't have an RUU that will work you can install the firmware http://forum.xda-developers.com/showthread.php?t=2322755
This will bring you back to the old 2.15 hboot and older partitions so you can install the 2.15 roms to get a working phone to do what you want.
Alternatively, you could learn what adb push is and that will allow you to move files from pc to your phone on the "special" recovery.
Click to expand...
Click to collapse
It is not a special CWM i installed it because the TWRP sucked, now i am installing windows 7 because windows 8.1 couldn't find my phone, i will reply after the windows 7 is installed, thank you very much!