Hi. I was toolin' along doing real well on CleanRom 4.5 for several days. Starting yesterday, the phone would randomly reboot itself to the HTC screen. I figured I had a bad app or something. Today, I went to open an app (Draw Something) and the phone froze for a bit. Then it rebooted, and now I cant get it booted back up. I usually never make it past the HTC screen. Got into recovery once but it rebooted in the middle of clearing the cache.
Any advice?
Welp, just made it through cache and dalvik and rebooted in the middle of factory reset. I wonder if I'm doing more harm than good.
Got it recovered and wiped fully, but it still keeps rebooting. Starting to feel like a hardware issue.
hcricket said:
Got it recovered and wiped fully, but it still keeps rebooting. Starting to feel like a hardware issue.
Click to expand...
Click to collapse
Wipe system than factory reset ....than flash a new Rom if u can without it rebooting :crying:
omario8484 said:
Wipe system than factory reset ....than flash a new Rom if u can without it rebooting :crying:
Click to expand...
Click to collapse
Thank you for the reply. I have the battery recharging in recovery right now (which I am thrilled it is doing, lol). What does it do when you wipe /system? Clear off the OS? Would you move a new ROM over to SD card first?
hcricket said:
Thank you for the reply. I have the battery recharging in recovery right now (which I am thrilled it is doing, lol). What does it do when you wipe /system? Clear off the OS? Would you move a new ROM over to SD card first?
Click to expand...
Click to collapse
So when u go into wipe menu in twrp it will show options : cache dalvic cache and external never press external unless u know what you're doing!
So do u have any Rom backups if so try restoring that and if not dl like clean Rom final version 5 and mount it sd in recovery and move that over and for the sake of itright now when your gunna install a new Rom in the wipe menu just choose factory reset ...your using twrp recovery right?
omario8484 said:
So when u go into wipe menu in twrp it will show options : cache dalvic cache and external never press external unless u know what you're doing!
So do u have any Rom backups if so try restoring that and if not dl like clean Rom final version 5 and mount it sd in recovery and move that over and for the sake of itright now when your gunna install a new Rom in the wipe menu just choose factory reset ...your using twrp recovery right?
Click to expand...
Click to collapse
Thank you. I wiped everything, including /system and put CleanROm final 5 on it. Everything looked beautiful but I got to the setup screens and rebooted. I'm back in recovery and charging now. Oddly, it has stopped rebooting from recovery. The only other thing I can think of is a bad sim card? Can that make a phone go crazy?
hcricket said:
Thank you. I wiped everything, including /system and put CleanROm final 5 on it. Everything looked beautiful but I got to the setup screens and rebooted. I'm back in recovery and charging now. Oddly, it has stopped rebooting from recovery. The only other thing I can think of is a bad sim card? Can that make a phone go crazy?
Click to expand...
Click to collapse
What's your battery at?
Removed the SIM card and it froze while booting, with lots of graphical tearing. *sigh*
hcricket said:
Removed the SIM card and it froze while booting, with lots of graphical tearing. *sigh*
Click to expand...
Click to collapse
Keep that simmy in there..now what's your battery ....when does it reboot ...when trying to get into aroma installer?
---------- Post added at 09:28 PM ---------- Previous post was at 09:25 PM ----------
Worst case scenario you can relock the bootloader and run an RUU. But I think u can get out of this without having to do that
I replaced the SIM. Battery at 90% now, was 44% when I started. Fortunately, it is charging from TWRP.
It reboots all over the place - from fastboot, from recovery, from the boot.img, from the lock screen. I made it all the way to Android setup at one point and it rebooted. It most often just gets to the HTC screen and hangs - it reboots the least from recovery, just once in a great while.
hcricket said:
I replaced the SIM. Battery at 90% now, was 44% when I started. Fortunately, it is charging from TWRP.
It reboots all over the place - from fastboot, from recovery, from the boot.img, from the lock screen. I made it all the way to Android setup at one point and it rebooted. It most often just gets to the HTC screen and hangs - it reboots the least from recovery, just once in a great while.
Click to expand...
Click to collapse
Dam so it's actually booting up and your getting to the rom... Umm what'd you do to your phone did u install something bad that's laying around on your sd or idk ! This is weird
omario8484 said:
Dam so it's actually booting up and your getting to the rom... Umm what'd you do to your phone did u install something bad that's laying around on your sd or idk ! This is weird
Click to expand...
Click to collapse
Oy. Add reboot during aroma installer to that list. I just tried to flash again but no go.
hcricket said:
Oy. Add reboot during aroma installer to that list. I just tried to flash again but no go.
Click to expand...
Click to collapse
Hold down your power button until your screen turns black and than see if it's still rebooting
Still no go. Thank you for your help - I've got it to 98% battery, powered it down, and I'm going to the bar, hah hah.
try flashing CM10 instead of a Sense rom. Aroma can cause freezes and reboots on its own. I would also be scared to run the RUU also since your phone freezes randomly. whats was your stock version?
It doesn't sound like you do, but if you installed a custom kernel that is overclocked then it could be that your device can't handle the higher CPU frequency. CleanROM 5 final I don't think has a custom kernel though. It could also be a bad CPU or memory hardware.
denversc said:
It doesn't sound like you do, but if you installed a custom kernel that is overclocked then it could be that your device can't handle the higher CPU frequency. CleanROM 5 final I don't think has a custom kernel though. It could also be a bad CPU or memory hardware.
Click to expand...
Click to collapse
I have had this happen. Viper has stock kernel listed in post 4 I would try flashing that.
Sent from my HTC One X using xda premium
kleeman7 said:
I have had this happen. Viper has stock kernel listed in post 4 I would try flashing that.
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I told him to flash a rom that doesn't use aroma. He is getting freezes all the time. TWRP used to freeze up on me all the time after the 2.20 ruu until twrp 2.2.2.0 was released. Phone still has trouble getting into recovery from the bootloader though. He should install CM10 or codefirex without using a custom kernel. Maybe run "fastboot erase cache" in bootloader then wipe cache,dalvik,factory reset,system,external in recovery then flash CM10 or codefirex and gapps. keep it plain until you find issues you can attribute to the rom or to the phone. i have had very few issues with latest builds of jb aosp roms besides some battery stuff.
Well, although I had fully charged it and then powered down, now that I am ready to work on it this AM, it wont start at all. I'm thinking she's gone, captain.
Thank you everyone for the replies.
Related
Salutations,
I recently installed a ICS ROM from another site, was meant to be in beta but it crashed and wouldn't reboot unless I removed the battery everytime the screen went off. I thought I would wipe everything and just go back to the stock ROM for a while until all of the ICS builds have matured.
Sadly this wasn't the case, after wiping everything ( I wanted to clean the SD card etc as well ) the phone doesn't boot, remains stuck on HTC logo if it wants to go that far. The LED is flashing orange and I cannot get into HBOOT.
Any help would be greatly appreciated!
The flashing LED light means u got low battery, so I would suggest you charging it.
to get into recovery remove the battery, and then try again. When in recovery wipe cache and dalvik cache and try to reboot.
The screen-off problem I have no idea how to fix, try re-downloading, maybe u got a broken zip. Or just try another ROM.
Sent from my MIUI.us Sensation 4G using xda premium
Make sure you do "supercid" then go ahead and download and run the correct ruu and drivers for your version of sensation problem solved
mendes52309 said:
Make sure you do "supercid" then go ahead and download and run the correct ruu and drivers for your version of sensation problem solved
Click to expand...
Click to collapse
Thanks for the responses, I think I must have wiped the boot partition and messed up the ruu. Problem solved when I downloaded a new ROM on my Mac and moved it onto the SD card and installed it. Got quite worried that I might have soft bricked the device!
Ok went to install coredroid on my inspire and ive installed roms before with no problem. I did a full wipe and started the install and now it is stuck on the screen say. ( Formatting partions,,, Mounting partitions,,,, Cleaning cache & Dalvik Cache & old data,,,,, writing shared systems) been like this for at least 30 min now wth can i do..
drewg0407 said:
Ok went to install coredroid on my inspire and ive installed roms before with no problem. I did a full wipe and started the install and now it is stuck on the screen say. ( Formatting partions,,, Mounting partitions,,,, Cleaning cache & Dalvik Cache & old data,,,,, writing shared systems) been like this for at least 30 min now wth can i do..
Click to expand...
Click to collapse
Maybe a bad download.....try to get the rom file again and flash it. I installed CoreDroid V9.3 yesterday no problem at all.....
Check the MD5sum before going through. Make sure that you flashed the multidevice rom and not the Sensation....
drewg0407 said:
Ok went to install coredroid on my inspire and ive installed roms before with no problem. I did a full wipe and started the install and now it is stuck on the screen say. ( Formatting partions,,, Mounting partitions,,,, Cleaning cache & Dalvik Cache & old data,,,,, writing shared systems) been like this for at least 30 min now wth can i do..
Click to expand...
Click to collapse
dont flash from any kind of rom manager software, only do it from recovery (in case you werent)
drewg0407 said:
Ok went to install coredroid on my inspire and ive installed roms before with no problem. I did a full wipe and started the install and now it is stuck on the screen say. ( Formatting partions,,, Mounting partitions,,,, Cleaning cache & Dalvik Cache & old data,,,,, writing shared systems) been like this for at least 30 min now wth can i do..
Click to expand...
Click to collapse
I love Coredroid ROM it is an awesome ROM. I flashed the new one Coredroid 9 and absolutely hatedv it had nothing but issues with it. I'd stick with Coredroid 8.1. Best thing would be remove battery remove SD Card and use and adapter place Coredroid ROM zip on root of SD as well as FULL WIPE 1.5 zip on root of SD. Then enter recovery thru hboot with holding volume down and power button at same time then flash full wipe then flash Coredroid. Should do the job.
I dont know about the Coredroid 9 multi device deal i had issues with it and completely hated it. Though I do love Coredroid but I will stay with Coredroid 8.1cause it works flawless for me. Thou now Im addicted to Absolution (lol)
Good Luck
RE
Ive already done a full wipe can i still take battery out and sd and dowload 8.1 and still put it on my phone i just scared since i did full wipe i wont be able to get back into recovery
drewg0407 said:
Ive already done a full wipe can i still take battery out and sd and dowload 8.1 and still put it on my phone i just scared since i did full wipe i wont be able to get back into recovery
Click to expand...
Click to collapse
Yeah, you can do that. Full wiping shouldn't delete recovery, you should still be able to get into recovery via HBOOT and then from there you can mount your sd card, put 8.1 on there and flash as normal. This is assuming that you haven't done anything already to screw up your recovery..
RE:
all ive done is full wipe and tried installing man i thought i bricked my damn phone i started getting scared my wife is in basic training for the army and this is my only way to talk to her
drewg0407 said:
all ive done is full wipe and tried installing man i thought i bricked my damn phone i started getting scared my wife is in basic training for the army and this is my only way to talk to her
Click to expand...
Click to collapse
My good sir, take a breath and relax...okay good! Alright, the good news is that 90% of the people who think they bricked their phone initially, don't actually have a bricked phone. I don't want to build your hopes up and say you aren't there but let's not say its bricked until it really is!
Let's start from scratch...can you get into HBOOT (holding the vol. down and power). If you can get into HBOOT, all is not lost. Once in HBOOT, you can hit the power button and it will scan for a PD98IMG.zip, hopefully you don't have one on there. After its done scanning you should be able to use the vol. rocker to select recovery. Enter recovery and follow my previous instructions. If you cannot get into recovery, there are some RUUs in the "PD98IMG.zip" form in the stock ROM thread that you can put on your SDcard and flash through HBOOT that will get you into a working ROM and you can reinstall a recovery and get back to flashing as normal.
thx
Ok thanks to all who replied got into bootloader through cmd prompts but im installing rom now ill let yall know how it goes
everything good thank you
Then click the Thanks button of those that helped you. They deserve it.
Good job not hard to fix many issues. We just have to take a deep breath and calm down. Ifs when people freak out that they start doing stupid things to their phones making matters worse. Nothing that a quick search won't cure.
Sent from my Inspire 4G using xda premium
I was running CM10, downloaded the nightly released on 1/13.
Installed it, it rebooted, then got stuck looping again. I couldn't get it to do anything. Eventually my boot screen would go away, it would go to a blank black screen. I could see backlight, but I had absolutely nothing.
I managed to get into my bootloader, could get into recovery as well. I'm using TWRP.
I couldn't get it to do anything at all.
I eventually wiped my SD card, reformatted it, downloaded AOKP, flashed the ROM. It's started, got to the AOKP Loading screen, which it is now looping. I can't get it to do anything. I'm lost and frustrated as can be.
Any fresh ideas from anyone?
If the screen is on, its not bricked. Not knowing what to do is not a brick.
Did you factory reset, wipe data and wipe cache (all from TWRP, do not factory reset from hboot, whatever you do) before flashing?
If on hboot 1.14 or higher, did you flash boot.img via fastboot?
I restarted the entire process. I actually ended up having to do it a few times. No change in the process.
Wipe SD card. Factory Rest. Removed OS through recovery. Flashed boot. Flashed ROM. I just kept getting looping boot screens.
On another attempt it worked just fine. No change in the way I did things. I'm unsure of what the difference was or why, but its working, for now. I may end up getting a different phone instead of my Onex to see if things run smoother on my process. I have an old captivate I may try to use as a trial/error experiment.
Sent from my One X using xda app-developers app
i factory reset from hboot is there anything i can do? had the same issue with cm10
mfc1288 said:
Wipe SD card. Factory Rest. Removed OS through recovery. Flashed boot. Flashed ROM. I just kept getting looping boot screens.
Click to expand...
Click to collapse
Why do people keep wiping their SD card when flashing? I understand there are some people that do it deliberately because they like to make a "fresh" start. But it seems that the majority of people doing it are n00bs that for some reason think its "required" when flashing a new ROM, which it is not. Factory reset, wipe Dalvik, wipe cache. Nothing else "needs" to be wiped when flashing.
Remember on most devices the SD is removable, and doesn't really have much of anything to do with the flashing process, aside from the fact that you put the new ROM zip file on there (and backups go there). Its like saying you "have to" format your external hard drive every time you want to change or upgrade your PC operating system.
mfc1288 said:
I have an old captivate I may try to use as a trial/error experiment.
Click to expand...
Click to collapse
Completely different hardware, so I'm not sure what you would trying to accomplish with that experiment. I think you just had some bad luck, and bad flashes just happen occasionally. I've flashed many different ROMs on the One X, and have never had issues booting up.
CM10 seems to be giving more headaches than other ROMs, so that may have something to do with it. Not to insult that ROM or its devs. But when things change nightly, there can be glitches. And it just seems there are a lot more complaints about not being able to boot after flashing CM10 than other ROMs (despite having correctly flashed boot.img and wiped). Or maybe the number of people posting this issue is just a testament to how popular CM10 is?
---------- Post added at 10:03 AM ---------- Previous post was at 10:01 AM ----------
sinzish said:
i factory reset from hboot is there anything i can do?
Click to expand...
Click to collapse
This has been discussed on many threads already. Plug the phone to a PC, and it should show up as new hardware. Select it, and choose the option to format FAT32. After that, you should be able to mount as a USB drive.
I installed the latest Cromi which went well for a week or two until the tablet started shutting off about 10 seconds after the home screen loaded. I[m pretty sure it has nothing to do with the ROM, but I still want to go back to stock and flash it all over again. How do I go back to complete stock if I had TWRP?
ocstew said:
I installed the latest Cromi which went well for a week or two until the tablet started shutting off about 10 seconds after the home screen loaded. I[m pretty sure it has nothing to do with the ROM, but I still want to go back to stock and flash it all over again. How do I go back to complete stock if I had TWRP?
Click to expand...
Click to collapse
Download the latest stock firmware from asus, extract it once then flash it with twrp. But this could be unnecessary. You might wanna try flash _thats kernel and see if it shows any difference.
ocstew said:
I installed the latest Cromi which went well for a week or two until the tablet started shutting off about 10 seconds after the home screen loaded. I[m pretty sure it has nothing to do with the ROM, but I still want to go back to stock and flash it all over again. How do I go back to complete stock if I had TWRP?
Click to expand...
Click to collapse
You maybe selected your sleep mode with a 15 second in your system setting. You can go to your system setting and select display. Your sleep mode will pop up and pick a different time for your sleep mode..
JoinTheRealms said:
Download the latest stock firmware from asus, extract it once then flash it with twrp. But this could be unnecessary. You might wanna try flash _thats kernel and see if it shows any difference.
Click to expand...
Click to collapse
I tried flashing the stock kernel that came with the Chromi install but the same thing continued to happen. I also overclocked the CPU to 1.7 Ghz using the Hunds kernel, resulting in the tablet crashing. I did this multiple times. Is it possible that my hardware is damaged?
LetMeKnow said:
You maybe selected your sleep mode with a 15 second in your system setting. You can go to your system setting and select display. Your sleep mode will pop up and pick a different time for your sleep mode..
Click to expand...
Click to collapse
I don't think so, I'm actively touching the screen and then the tablet will be unresponsive and shut down.
ocstew said:
I tried flashing the stock kernel that came with the Chromi install but the same thing continued to happen. I also overclocked the CPU to 1.7 Ghz using the Hunds kernel, resulting in the tablet crashing. I did this multiple times. Is it possible that my hardware is damaged?
I don't think so, I'm actively touching the screen and then the tablet will be unresponsive and shut down.
Click to expand...
Click to collapse
Sorry, misread your post..
Edit:
Did you do a clean install? Hund's kernel has a thermal throttle which reduces the CPU speed if it reaches a certain temperature that I believed.
It is more likely a software problem.
ocstew said:
I tried flashing the stock kernel that came with the Chromi install but the same thing continued to happen. I also overclocked the CPU to 1.7 Ghz using the Hunds kernel, resulting in the tablet crashing. I did this multiple times. Is it possible that my hardware is damaged?
Click to expand...
Click to collapse
Very unlikely, Is it possible during the cromix install you selected the option to undervolt? this could be the cause of the instabilities, More likely you have installed a root app thats failing during loading and bringing the system down. is the reboots consistently 10 after reaching the homescrren or the times vary?
Best option is to wipe and reflash cromix (or stock, but stock requires reflashing twrp with fastboot) with nothing but the default options and see if the issue persists
---------- Post added at 05:21 PM ---------- Previous post was at 05:12 PM ----------
LetMeKnow said:
Sorry, misread your post..
Edit:
Did you do a clean install? Hund's kernel has a thermal throttle which reduces the CPU speed if it reaches a certain temperature that I believed.
It is more likely a software problem.
Click to expand...
Click to collapse
Hmm this shouldn't be the issue. Hunds may have modified the default thermal throttling settings (from memory its high 70c) but it even should be safe up til low 80c (if your tablets running that hot you should really think about hoping out of the volcano your currently in )
Im far from a kernel expert but off the top of my head if the issue was kernel related it would be because once android init processes are finished a flag is passed allowing the kernel to scale to higher frequencies, at this point it might be crashing because at those high frequencies the tablet isn't allowing enough voltage to stay stable.
LetMeKnow said:
Sorry, misread your post..
Edit:
Did you do a clean install? Hund's kernel has a thermal throttle which reduces the CPU speed if it reaches a certain temperature that I believed.
It is more likely a software problem.
Click to expand...
Click to collapse
That's what I'm trying to do but it isn't working. I'm not sure how to use TWRP to reset my system back to its original state. I press factory reset, but it completes incredibly quickly, signalling that nothing is actually being reset. How do I revert my system back to stock, erasing all the data on my tablet?
JoinTheRealms said:
Very unlikely, Is it possible during the cromix install you selected the option to undervolt? this could be the cause of the instabilities, More likely you have installed a root app thats failing during loading and bringing the system down. is the reboots consistently 10 after reaching the homescrren or the times vary?
Best option is to wipe and reflash cromix (or stock, but stock requires reflashing twrp with fastboot) with nothing but the default options and see if the issue persists
---------- Post added at 05:21 PM ---------- Previous post was at 05:12 PM ----------
Hmm this shouldn't be the issue. Hunds may have modified the default thermal throttling settings (from memory its high 70c) but it even should be safe up til low 80c (if your tablets running that hot you should really think about hoping out of the volcano your currently in )
Im far from a kernel expert but off the top of my head if the issue was kernel related it would be because once android init processes are finished a flag is passed allowing the kernel to scale to higher frequencies, at this point it might be crashing because at those high frequencies the tablet isn't allowing enough voltage to stay stable.
Click to expand...
Click to collapse
No I didn't select that option. I suspect you're right. It always happens within a certain time interval, which is why I'm trying to completely erase everything on my tablet and start from stock. I flashed this ROM: http://forum.xda-developers.com/showthread.php?t=2223918
....And now it's been on "android is upgrading - starting apps" for 5 minutes now
ocstew said:
That's what I'm trying to do but it isn't working. I'm not sure how to use TWRP to reset my system back to its original state. I press factory reset, but it completes incredibly quickly, signalling that nothing is actually being reset. How do I revert my system back to stock, erasing all the data on my tablet?
It always happens within a certain time interval.
Click to expand...
Click to collapse
Use the method i just posted to get back to stock, twrp's factory reset doesn't do that, it wipes /system and cache partitions to remove android completely.
JoinTheRealms said:
Very unlikely, Is it possible during the cromix install you selected the option to undervolt? this could be the cause of the instabilities, More likely you have installed a root app thats failing during loading and bringing the system down. is the reboots consistently 10 after reaching the homescrren or the times vary?
Best option is to wipe and reflash cromix (or stock, but stock requires reflashing twrp with fastboot) with nothing but the default options and see if the issue persists
---------- Post added at 05:21 PM ---------- Previous post was at 05:12 PM ----------
Hmm this shouldn't be the issue. Hunds may have modified the default thermal throttling settings (from memory its high 70c) but it even should be safe up til low 80c (if your tablets running that hot you should really think about hoping out of the volcano your currently in )
Im far from a kernel expert but off the top of my head if the issue was kernel related it would be because once android init processes are finished a flag is passed allowing the kernel to scale to higher frequencies, at this point it might be crashing because at those high frequencies the tablet isn't allowing enough voltage to stay stable.
Click to expand...
Click to collapse
Thanks for the information. I am using the balance mode most of the time and it is max out around 51C. I think that I have a better luck than some people so far without any problem with Cromi X and Hund. About the throttle information on Hund's kerneI, I just want to mess around with it. I think that Hund sets it at level 0 onTegra_table0...
JoinTheRealms said:
Use the method i just posted to get back to stock, twrp's factory reset doesn't do that, it wipes /system and cache partitions to remove android completely.
Click to expand...
Click to collapse
I've been trying to find the stock firmware but the Asus website only has some manuals: http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+Transformer+Pad+Infinity+TF700T&p=28&s=1
Can you link me? And when you say "flash" do you mean press Install in TWRP and select a zip, etc?
ocstew said:
I've been trying to find the stock firmware but the Asus website only has some manuals: http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+Transformer+Pad+Infinity+TF700T&p=28&s=1
Can you link me? And when you say "flash" do you mean press Install in TWRP and select a zip, etc?
Click to expand...
Click to collapse
http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+Transformer+Pad+Infinity+TF700T&p=28&s=1
Im assuming your in the US if so make sure you use the US version. Yes where people here might say "flash" they mean install. Flash is the terminology of writing data to ROM memory
ocstew said:
That's what I'm trying to do but it isn't working. I'm not sure how to use TWRP to reset my system back to its original state. I press factory reset, but it completes incredibly quickly, signalling that nothing is actually being reset. How do I revert my system back to stock, erasing all the data on my tablet?
No I didn't select that option. I suspect you're right. It always happens within a certain time interval, which is why I'm trying to completely erase everything on my tablet and start from stock. I flashed this ROM: http://forum.xda-developers.com/showthread.php?t=2223918
....And now it's been on "android is upgrading - starting apps" for 5 minutes now
Click to expand...
Click to collapse
If you want to reset, you need to boot into the TWRP and select Wipe, then Advance Wipe. In Advance wipe, you need to check Dalvik, Cache, and Data to do a factory reset. I hope that helps.
Edit:
Do you have an external SD in your device?
LetMeKnow said:
If you want to reset, you need to boot into the TWRP and select Wipe, then Advance Wipe. In Advance wipe, you need to check Dalvik, Cache, and Data to do a factory reset. I hope that helps.
Edit:
Do you have an external SD in your device?
Click to expand...
Click to collapse
Yes I do. I think I did something stupid though, I flashed the ROM in the link using my external sdcard. It all worked fine until it stayed on "Starting Apps" for 5 minutes, at which I used the hardware reset buttons. My tablet cannot go beyond the spinning circle thingy and TWRP seems to have disappeared. My ignorance of Android is astounding haha :laugh:
I selected the "wipe" option when you hold down power and volume down. And it seems to have booted into the original start up screen, yay!
ocstew said:
I've been trying to find the stock firmware but the Asus website only has some manuals: http://support.asus.com/Download.aspx?SLanguage=en&m=ASUS+Transformer+Pad+Infinity+TF700T&p=28&s=1
Can you link me? And when you say "flash" do you mean press Install in TWRP and select a zip, etc?
Click to expand...
Click to collapse
I see absolutely no reason why you should flash the stock firmware. You'll just loose TWRP and root and have to start all over again.
Try this:
Put the your CROMI-X zip on a microSD.
Boot into TWRP and choose Wipe > Advanced > Format Data. This will erase your entire data partiton, so make sure everything is backed up.
Flash CROMI-X from the microSD. The Aroma installer will format your system partition before installing the new rom, wiping cache and Dalvik is the default selection as well.
Choose the stock kernel or _that's kernel for stability.
Oh, btw, what bootloader/recovery are you on? If you're not on 10.6.1.14.8 and TWRP 2.5/2.6, flash the package from the OP first, boot back into system, then proceed as described.
Sent from my DROID4 using Tapatalk 2
---------- Post added at 11:29 PM ---------- Previous post was at 11:25 PM ----------
ocstew said:
Yes I do. I think I did something stupid though, I flashed the ROM in the link using my external sdcard. It all worked fine until it stayed on "Starting Apps" for 5 minutes, at which I used the hardware reset buttons. My tablet cannot go beyond the spinning circle thingy and TWRP seems to have disappeared. My ignorance of Android is astounding haha :laugh:
I selected the "wipe" option when you hold down power and volume down. And it seems to have booted into the original start up screen, yay!
Click to expand...
Click to collapse
Jeez! Just saw this! You chose Wipe Data from the bootloader menu?? Consider yourself lucky that you're not hard bricked! Slow down! Don't do anything else before you're sure what you're doing!
Sent from my DROID4 using Tapatalk 2
What are the repercussions of wipe data? Everything seems to have reverted to normal and my tablet is running properly now. Thanks for the caution.
My build number has the string: 10.6.1.14.4-20130329
ocstew said:
What are the repercussions of wipe data? Everything seems to have reverted to normal and my tablet is running properly now. Thanks for the caution.
My build number has the string: 10.6.1.14.4-20130329
Click to expand...
Click to collapse
I am glad that you got your tab working again.. :good: What berndblb said is correct. People have had brick their devices using Wipe from the bootlloader if their bootloader and custom recovery are not compatible. The good practice is not using it because when the bootloader is not working, you can do anything unless you can update the bootloader binary.
ocstew said:
What are the repercussions of wipe data? Everything seems to have reverted to normal and my tablet is running properly now. Thanks for the caution.
My build number has the string: 10.6.1.14.4-20130329
Click to expand...
Click to collapse
Guys don't get paranoid about the Wipe Data option . That option caused bricks only when the users used a custom recovery which wasn't compatible with the device's bootloader. Using Wipe Data when no custom recovery is actually the only easy way to do a Factory Reset (especially for people on stock firmware and locked bootloader) and personally it also helped me repair a corrupted partition, so my advice is to read first and flash after.
Pretoriano80 said:
Guys don't get paranoid about the Wipe Data option . That option caused bricks only when the users used a custom recovery which wasn't compatible with the device's bootloader. Using Wipe Data when no custom recovery is actually the only easy way to do a Factory Reset (especially for people on stock firmware and locked bootloader) and personally it also helped me repair a corrupted partition, so my advice is to read first and flash after.
Click to expand...
Click to collapse
Best advice yet never be hasty when flashing stuffs. By the way im confused at how that would cause a soft brick? im not sure how or why it would affect fastboot access
JoinTheRealms said:
Best advice yet never be hasty when flashing stuffs. By the way im confused at how that would cause a soft brick? im not sure how or why it would affect fastboot access
Click to expand...
Click to collapse
AFAIK an incompatibility between a custom recovery and the bootloader was only causing a bootloop to recovery and also some corrupted partition, but the bootloader was ok. The bad part was that the user couldn't reach the fastboot mode anymore because the device always restarted to recovery (so no bootloader menu when pressing Volume Down + Power) but about two months ago _that managed to find a way to kick the device out of the recovery bootloop and once you did it you can recover the device just fine.
Pretoriano80 said:
AFAIK an incompatibility between a custom recovery and the bootloader was only causing a bootloop to recovery and also some corrupted partition, but the bootloader was ok. The bad part was that the user couldn't reach the fastboot mode anymore because the device always restarted to recovery (so no bootloader menu when pressing Volume Down + Power) but about two months ago _that managed to find a way to kick the device out of the recovery bootloop and once you did it you can recover the device just fine.
Click to expand...
Click to collapse
Note that this unbricking method *requires* a working rooted Android image, which the user whom I helped luckily still had. In other cases it is still a hard brick (because the recovery cannot access the eMMC so it is impossible to remove the reboot-to-recovery command or flash anything), so I recommend never using "wipe data" from the bootloader menu, or "install update" from within Android with a custom recovery.
i've been using CWM recovery and CM nightlies. they've been just fine. today i restored a two day old backup, as i didn't care for the current nightly.
now the phone black screens after the samsung splash.
i've tried:
factory reset
wipe dalvick/cache
restoring other backups
flashing other nightlies
and the phone will boot for the first time, but if i select 'reboot' or 'power down' on the next boot it's only a samsung splash, then black screen (no cm splash, no response from buttons input), and will not boot again.
what's the problem ?
ohgood said:
i've been using CWM recovery and CM nightlies. they've been just fine. today i restored a two day old backup, as i didn't care for the current nightly.
now the phone black screens after the samsung splash.
i've tried:
factory reset
wipe dalvick/cache
restoring other backups
flashing other nightlies
and the phone will boot for the first time, but if i select 'reboot' or 'power down' on the next boot it's only a samsung splash, then black screen (no cm splash, no response from buttons input), and will not boot again.
what's the problem ?
Click to expand...
Click to collapse
Happens once in a while when you flash over a back up.
Try making a clean flash.
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
Somcom3X said:
Happens once in a while when you flash over a back up.
Try making a clean flash.
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
Click to expand...
Click to collapse
i've done that. right now, i've wiped everything, and then flashed a nightly, and it will not reboot !
it will only boot the -one- time directly after flashing a new rom. any reboot attempts after that means it freezes, or fails, with a black screen directly after the samsung splash.
what have i missed ?
ohgood said:
i've done that. right now, i've wiped everything, and then flashed a nightly, and it will not reboot !
it will only boot the -one- time directly after flashing a new rom. any reboot attempts after that means it freezes, or fails, with a black screen directly after the samsung splash.
what have i missed ?
Click to expand...
Click to collapse
Try installing Samsung firmware via Odin. Root it and try again. Wouldn't hurt to try.
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
Somcom3X said:
Try installing Samsung firmware via Odin. Root it and try again. Wouldn't hurt to try.
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
Click to expand...
Click to collapse
could you point me to a specific samsung firmware, or is there only one ?
ohgood said:
could you point me to a specific samsung firmware, or is there only one ?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?p=24660137
Make sure repartition is always unchecked in Odin
Sent from my Carbonized SAMSUNG-SGH-T769 using Tapatalk Pro
ohgood said:
could you point me to a specific samsung firmware, or is there only one ?
Click to expand...
Click to collapse
Check out this post from the brick fix thread.
http://forum.xda-developers.com/showpost.php?p=44626072&postcount=117
The full fix thread
http://forum.xda-developers.com/showthread.php?t=1591601
Sniped lol
i've wiped everything. flashed back to stock via odin, rooted, just like always.
i've even wiped in between.
after the FIRST clean boot, there is no rebooting. all it does is continue to hang after the samsung splash. no cyanogenmod, no stock rom, no nothing, nothing will boot the SECOND TIME.
i really don't understand this.
i'm using CWM recovery 5.5.0.4, cm-nightly 10-05, and it just don't think it's going to work properly again. it's a real shame, cause i really like the size, weight, and speed of this phone. but if it won't boot, i can't use it.
if anyone has any tips, i'll try them. at this point i really don't mind destroying it, and it might make me feel better to do so.
i meant to add, it doesn't matter if i use a backup, flash a fresh new rom, or use stock. the first boot works fine, but all boots after that wether from powering down or selecting 'reboot' fail.
maybe this part will help -
if i wipe the phone completely, it will boot. let's call this boot 1.
i can setup the phone, or change nothing in settings, doesn't appear to matter, and choose 'power down' or 'reboot'. let's call this reboot 1.
the next time i power on the phone, black screen. no CM splash, nothing. i guess we'll call this hang 1 ?
ideas ?
ohgood said:
i've wiped everything. flashed back to stock via odin, rooted, just like always.
i've even wiped in between.
after the FIRST clean boot, there is no rebooting. all it does is continue to hang after the samsung splash. no cyanogenmod, no stock rom, no nothing, nothing will boot the SECOND TIME.
i really don't understand this.
i'm using CWM recovery 5.5.0.4, cm-nightly 10-05, and it just don't think it's going to work properly again. it's a real shame, cause i really like the size, weight, and speed of this phone. but if it won't boot, i can't use it.
if anyone has any tips, i'll try them. at this point i really don't mind destroying it, and it might make me feel better to do so.
.
i meant to add, it doesn't matter if i use a backup, flash a fresh new rom, or use stock. the first boot works fine, but all boots after that wether from powering down or selecting 'reboot' fail.
Click to expand...
Click to collapse
The October nightlies are cm10.2 right? Your using the old recovery, that's the issue. And there are newer nightlies.
New recoveries
http://forum.xda-developers.com/showthread.php?t=2475802
Cm thread
http://forum.xda-developers.com/showthread.php?t=2459198
Romman0 said:
The October nightlies are cm10.2 right? Your using the old recovery, that's the issue. And there are newer nightlies.
New recoveries
http://forum.xda-developers.com/showthread.php?t=2475802
Cm thread
http://forum.xda-developers.com/showthread.php?t=2459198
Click to expand...
Click to collapse
yes, they're fairly recent nightlies. i skipped back to the 10-5 nightly as i thought that might ahve been part of the problem. since you're pointing to my recovery being an older version, i'll update it. thanks for the clue stick !
Romman0 said:
The October nightlies are cm10.2 right? Your using the old recovery, that's the issue. And there are newer nightlies.
New recoveries
http://forum.xda-developers.com/showthread.php?t=2475802
Cm thread
http://forum.xda-developers.com/showthread.php?t=2459198
Click to expand...
Click to collapse
hey thank you for that. i've removed the old cwm recovery, flashed new, lots of other flashes, and it finally works again. now to dig up a non-corrupted backup and hopefully be back to working.
thanks button was used
well, after all of that i'm going to roll with cm-10.0, cwm 6.xomething, so i can have a working compass on oruxmaps.
i won't be updating until 10.x begins to support compass functions again.
see yall then !
ohgood said:
well, after all of that i'm going to roll with cm-10.0, cwm 6.xomething, so i can have a working compass on oruxmaps.
i won't be updating until 10.x begins to support compass functions again.
see yall then !
Click to expand...
Click to collapse
Make sure you use the latest cm10 nightly, as the old stable one is a lot less "stable" than the name suggests, and is lacking features
Romman0 said:
Make sure you use the latest cm10 nightly, as the old stable one is a lot less "stable" than the name suggests, and is lacking features
Click to expand...
Click to collapse
thanks for the tip !
i finally got all the corrupted files (or whatever was causing problems) rm'd from both the phone and sdcard.
as of yesterday i had CM-10.o + CWM 6.0.3.8 and gapps 2012-8 (i think) working nicely on the phone. backed up a nandroid of all of it two times, and restored them to make sure restores were working. yes, everything fine.
as of today, i have CM-10.2 (latest nightly) + CMW 6.0.3.8 and gapps (current) working nicely on the phone. backed CURRENT up nandroid on sdcard, and restored a few times to make sure. yes, working fine.
seems it was
A) corrupted files/filessystems
and/or
B) too old a clockworkmod recovery
C) unstable CM version( s )
but now all is fine. thanks to all that helped !