Database Info

[Q] Semi-bricked tf300t

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.

Help! I did something to my phone!

Hello there, I have a htc one xl on At&t rooted... it has the hboot 1.14. Everything was fine until yesterday when I tried to flash AOKP. I used flash image gui to flash the boot.img then rebooted to TWRP and wiped rom, wiped everything, then installed the .zip for the boot.img I flashed... It would say android is upgrading and cycled through all the apps but stopped at starting apps... wouldnt go past it for 6 hours. I rebooted and tried to reflash the boot.img, but computer didnt recognize phone, and TWRP showed there was nothing on the sdcard

Juts mount your sd in recovery and drag a Rom over from your computer

J3susisl0rd7 said:
Hello there, I have a htc one xl on At&t rooted... it has the hboot 1.14. Everything was fine until yesterday when I tried to flash AOKP. I used flash image gui to flash the boot.img then rebooted to TWRP and wiped rom, wiped everything, then installed the .zip for the boot.img I flashed... It would say android is upgrading and cycled through all the apps but stopped at starting apps... wouldnt go past it for 6 hours. I rebooted and tried to reflash the boot.img, but computer didnt recognize phone, and TWRP showed there was nothing on the sdcard
Click to expand...
Click to collapse
Sounds like the initial problem was just a bad flash/download. It happens.
Try unplugging your phone, shutting down and restarting into bootloader, then hooking it up.

You flashed an incompatible kernel it sounds like.
Make sure you try flashing the kernel within the ROM
Sent from my One X using Tapatalk 2

Hello everyone! Thanks for the replies. Sorry for the rushed post earlier, was on the way out the door after trying for a while to figure something out. I'd love to send a rom to it, but TWRP shows that I have 0 mb available of storage, and the computer says I must format it to access files or something. I may have forgotten to mention- I think i flashed rohan kernel b6 improperly... used flash image gui then went to recovery and clicked it and hit install ... it hung at installing for a while, and upon reboot the starting apps problem happened, followed by no rom being on there, only being able to access TWRP, and ... well, above things. If I formatted it would I be able to put twrp and everything back on it necessary to make the thing function properly? Orr.... Thanks for any help!
God bless!
P.S. Forgot to add- Not sure why I thought I needed to try to "install" rohan kernel later on in TWRP lol
P.S.S I tried to mount sd card in twrp, nomatter how many times i try to select it it wont work

Yeah just format it and then it'll show up as a drive for you then you can send a rom to it.
Sent from my HTC One XL using xda premium

thejosh86 said:
Yeah just format it and then it'll show up as a drive for you then you can send a rom to it.
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
I'm sorry- I really don't understand what I'm going to lose if I format, like... apparently all my data is somewhere in the air now lol, but will I not lose any important things the phone needs to run? TWRP? Will the bootloader still be unlocked?
And, if above "issues" aren't "issues", then will the following steps be correct?
1. Send ROM to phone
2. Throw fastboot.exe and adb thing into a folder with the ROM/ boot.img
3. CMD prompt to flash
4. Magic
?
Thanks so much and sorry to be a pain here if this isn't that big of an issue! I was afraid I bricked the thing, but I was holding on to hope that I didn't since it seemed like a good thing that it would still boot to TWRP.
Also- not sure if this is an issue, I tried to hit adb sideload in TWRP just messing around with options, and it said it couldn't mount the SD card.... so.... yeah, is that an issue?

Whatever data you had on the sd card is gone anyway. You need to reformat to use it.
Formatting the sd card won't affect your /system files or recovery, which are stored on a different area, or cause you to lose root.

You guys are awesome. Thanks so much!
And, as you get a lot: Sorry... for being a noob. lol

[Q] Odin can't flash stock, boot hangs at logo

Good morning...
Right now, my phone (Galaxy S III on Verizon) will not boot past the "Galaxy S III" logo. Odin will not flash a stock Jelly Bean ROM from StockRoms.net. It gets stuck on the first .img, boot.img. I am downloading a new stock ROM right now and will try a full wipe.
Being silly and ambitious, I do not have a nandroid before it wouldn't boot. On Monday (two days ago) I rooted it. I flashed the VRALEC boot chain, rebooted, flashed ClockworkMod recovery, and installed the SuperSU bootloader and root patch through recovery. I rebooted, allowing CWM to disable the automatic re-flashing of the recovery. With my newly rooted phone, I jumped at trying to install Google Wallet. I went with the route of using Wallet Installer as found on the app store. And, being silly, I checked all three OS options (JB, ICS, and one other). After authorizing the superuser request, my phone almost immediately shut off. I think I made a nandroid through CWM after that, but not one that would run.
I thought it was going to be just build.prop having issues, so I went on a wild quest trying to find a working one online and get it on the device. I worked it into the updater script of my SuperSU patch. Nonetheless, nothing there fixed it. I've tried a bunch of things, including (get this) extracting the stock system.img.ext4 image, mounting it, tarring the device, creating an MD5 for it, and wrapping it up like a nandroid to "restore" with CWM.
I'm thinking I'm going to try and wipe the entire device, maybe leave /recovery, and flash a new I-535 ROM with Odin, see if that works. I don't know if it will. Any advice?
My flash counter is at about 5 after many attempts to get back to something that will boot, so warranty is not an option. Not that they've ever been a whole lot of help anyways.

Sounds like you can still enter recovery. If so adb push a custom ROM to your phone to flash.
Sent from my SCH-I535 using Tapatalk 2

What I have done in the past when flashing a completely stock unrooted ROM through Odin is remove the battery, replace it, boot to stock recovery, and do a factory reset plus wipe cache! This will make my phone boot every time, because flashing a stock makes it boot loop!
Sent from my SCH-I535 using xda app-developers app

joaquinla1 said:
What I have done in the past when flashing a completely stock unrooted ROM through Odin is remove the battery, replace it, boot to stock recovery, and do a factory reset plus wipe cache! This will make my phone boot every time, because flashing a stock makes it boot loop!
Click to expand...
Click to collapse
My phone has CWM recovery on it, but I don't see any reason CWM's factory reset and cache wipe would be any different. I'll give it a shot.
mentose457 said:
Sounds like you can still enter recovery. If so adb push a custom ROM to your phone to flash.
Click to expand...
Click to collapse
I may try this if I can't upload one through Odin after a complete wipe, like above. Also, I've only used adb push to upload individual files. How would I use it to push a ROM?
Thanks for all your help. The ROM I'm going to try and flash now is the official stock from stockroms.net. I can't post the link as I'm new but it's I535BLK_nowipe.zip. I'll keep this updated.

sworld said:
I may try this if I can't upload one through Odin after a complete wipe, like above. Also, I've only used adb push to upload individual files. How would I use it to push a ROM?
Click to expand...
Click to collapse
When you download a ROM, say Beans 11, it will be a zip file. Push that single file to the internal storage. Do not unzip it. Then boot into recovery and flash the zip.
Sent from my SCH-I535 using Tapatalk 2

mentose457 said:
When you download a ROM, say Beans 11, it will be a zip file. Push that single file to the internal storage. Do not unzip it. Then boot into recovery and flash the zip.
Click to expand...
Click to collapse
That makes more sense.
UPDATE: I "factory reset" the data partition and formatted /system and /cache through ClockworkMod. Turned it off, flashed VRALEC through Odin, rebooted, flashed the stock ROM, and then CWM. I'm restoring my nandroid of /data right now, and I'm awaiting an OTA firmware update to bring it up to the latest VZW JB. Then I'll root.. finally.

The thing with Odin is that after you reset you have to do a factory reset through stock recovery to finish the process. Otherwise you will get stuck in a boot loop like you did.
Sent from my GeeEssThree

z06mike said:
The thing with Odin is that after you reset you have to do a factory reset through stock recovery to finish the process. Otherwise you will get stuck in a boot loop like you did.
Sent from my GeeEssThree
Click to expand...
Click to collapse
Really? I've only odined once on the s3 and didn't have to wipe. On the fascinate and an older version of Odin after the flash before it booted it would automatically wipe.
Sent from my SCH-I535 using Tapatalk 2

Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator

So, the phone is functioning now. Of course, I am running a slightly older version and once I connect to a solid Wi-Fi network I'll request the newest update again.
However, I did already try to download the software update from Verizon, and it seemed to work fine. It rebooted into recovery and CWM seemed to handle it okay, although it claimed the signature was bad. It installed though, rebooted, and updated some app databases. And then, it said the update failed with "Code 401."
Right now I'm not too worried. Hopefully I can apply the update properly soon. It is worth noting that simply using CWM "advanced restore" on only the /data partition, without exactly matching the ROM build, has seemed to leave it hanging at the "4G LTE" logo.
Thanks for all of your help!

The phone will not install a Verizon update with a custom recovery installed.

tx926 all messed up

I need help trying to get back to the way it was. the bootloader is unlock, the phone will boot but here is the trouble 1. it will not do a factory reset, 2. the wireless is disabled, 3. no google apps are installed. I have used teamwin to format everything and do a install but it just updates the already installed programs. I have tried carbon and all the vers. of cm10. I also tried fastboot to install the img files. I used fastboot to format the phone all of this doesn't help. I been trying for 3 days to get back and I am getting nowhere. I need help bad.
ramon45

Did you flash the correct gapps?
Sent from my PACMAN MATRIX HD MAXX

deeje00 said:
Did you flash the correct gapps?
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
I installed gapps-jb-20130301-signed. It will install some of the apps but they don't work. I also tried DroidHD Utility 2.0 Deluxe and this doesn't help either. I also tried DroidHD Utility 2.0 Deluxe this didn't help either. I thik I need something to format the whole phone???? I can format bthe cashe, data and system in in teamwin but the phone will boot back into the os

Have you tried a different recovery - like cwm? It may make a difference.

Well cm 10 is based on 4.1 and those are 4.2 gapps I believe.
Sent from my PACMAN MATRIX HD MAXX

deeje00 said:
Well cm 10 is based on 4.1 and those are 4.2 gapps I believe.
Sent from my PACMAN MATRIX HD MAXX
Click to expand...
Click to collapse
I have tried all the helps but nothing works. Would a restore from another tx926 help any??? If so could someone post it for me, thanks

Making process the problem now is the Wi-Fi is grayed out. Unit is rooted and running Jelly bean 4.2.2 with the correct gapps. Please help

I had a ton of problems with my phone when I first got it. I was using twrp but when I fastbooted and started over with cwm (oudhs version) everything went much better. Idk why but that was my experience. So I suggest trying to switch recoveries like someone else suggested.

DroidAddict101 said:
I had a ton of problems with my phone when I first got it. I was using twrp but when I fastbooted and started over with cwm (oudhs version) everything went much better. Idk why but that was my experience. So I suggest trying to switch recoveries like someone else suggested.
Click to expand...
Click to collapse
I am unable to flash the cwm recovery or twrp also a new kernel. It takes a long time to get pasted the screen "bootloader is unlocked". Again the wifi and blue tooth are not working. the wifi when going to the advanced menu shows that region code is Europe. Changed to USA closed and reopen and it is back to Europe. Is the bootloader causing all this???? ow can I see what is in the bootloader and edit it?
Have I got everyone stumped on this problem?

ramon45 said:
I need help trying to get back to the way it was. the bootloader is unlock, the phone will boot but here is the trouble 1. it will not do a factory reset, 2. the wireless is disabled, 3. no google apps are installed. I have used teamwin to format everything and do a install but it just updates the already installed programs. I have tried carbon and all the vers. of cm10. I also tried fastboot to install the img files. I used fastboot to format the phone all of this doesn't help. I been trying for 3 days to get back and I am getting nowhere. I need help bad.
ramon45
Click to expand...
Click to collapse
use this tool from here http://forum.xda-developers.com/showthread.php?t=1970267
i got the same problem before

I downloaded the Droid Razr HD utility and flashed #1. How when the phone boots I get a black screen right after the bootloader. I can only get into fastboot from the menu. I can no longer get into recovery.

ramon45 said:
I downloaded the Droid Razr HD utility and flashed #1. How when the phone boots I get a black screen right after the bootloader. I can only get into fastboot from the menu. I can no longer get into recovery.
Click to expand...
Click to collapse
I got it. Phone is working great. Thanks for the help.
ramon45

[Q] Mixed up in my Photon Q CM Install

Installed CWM but installed the 4.1 update for Photon Q instead of the one here: wiki.cyanogenmod.org/w/Install_CM_for_moto_msm8960 which is the recovery-clockwork-6.0.4.4-xt926.img
Rooted.
Unlocked.
Wiped data
Tried to install CM11 anyway, it failed, already wiped so then tried to restore. Backup failed on /system...
Where do I go from here? How can I install the correct 6.4 CWM over the one on there now through adb?
I was stuck at the bootloader unlocked screen for a while, but now I was able to get to fastboot.
Any help?
I successfully installed CM11 on my Atrix HD.

Conotocarius said:
Installed CWM but installed the 4.1 update for Photon Q instead of the one here: wiki.cyanogenmod.org/w/Install_CM_for_moto_msm8960 which is the recovery-clockwork-6.0.4.4-xt926.img
Rooted.
Unlocked.
Wiped data
Tried to install CM11 anyway, it failed, already wiped so then tried to restore. Backup failed on /system...
Where do I go from here? How can I install the correct 6.4 CWM over the one on there now through adb?
I was stuck at the bootloader unlocked screen for a while, but now I was able to get to fastboot.
Any help?
I successfully installed CM11 on my Atrix HD.
Click to expand...
Click to collapse
You don't want to install that version. The newest one you can install right now is CWM 6.0.1.3
Go here for that=> http://clockworkmod.com/rommanager
Go back into FASTBOOT, and go into your command prompt and type: fastboot flash recovery recovery-clockwork-6.0.1.3-asanti.img
Turn the phone off, hold Volume UP+Power Button until it boots back into recovery. Hope that helps

Fixed. and installed CM11.
I was able to get to fastboot and from there I flashed the correct CWM by typing fastboot flash recovery recoveryname.img
With the recovery-clockwork-6.0.4.4-xt926.img on my Photon Q, I was then able to successfully go ahead and install CM11, gapps, and backup the phone.
Thanks for the wonderful resources here!

I should mention that CM11 being unified for these Motorola devices has been great. Getting practice on my Atrix HD prepared me for the Photon Q. I used all the same tools and should have used the same .zips... I got screwed up when I tried to install what CWM had listed default.
I don't know if I mentioned it before, I am installing the unified moto_msm8960 version.
Lesson here that is echoed throughout other posts: You cannot install CM11 with CWM Recover less than 6.0.4!

Conotocarius said:
I should mention that CM11 being unified for these Motorola devices has been great. Getting practice on my Atrix HD prepared me for the Photon Q. I used all the same tools and should have used the same .zips... I got screwed up when I tried to install what CWM had listed default.
I don't know if I mentioned it before, I am installing the unified moto_msm8960 version.
Lesson here that is echoed throughout other posts: You cannot install CM11 with CWM Recover less than 6.0.4!
Click to expand...
Click to collapse
Good deal, you got it to work