Hi,
I have had a TF101 for over a year. However it was used by someone else who upgraded it 0.17 and when it came to be me was unreliable and would often randomly reboot and then get stuck on the 'EEEpad' screen (before it says ASUS etc).
I am new to Android (been on webOS for a few years) so rooting etc is new ground for me, but I am pretty technical. Had lots of webOS patches and overclocking installed.
I 'upgraded' to 0.24 and then started reading as much as I can on this site after the reboots remained. I now realise I made two fundamental mistakes
1) Going to 0.24 at all seems to be a no-no from what I'v read.
2) I didn't do a clean restart before upgrading.
I'm not too worried about staying with stock but I do need the thing not to re-boot as often (15 times yesterday !!), so I am wondering.
1) Is 0.24 on a factory reset machine better for rebooting ? If so how do I get back to that state given that I have 0.24 already so can't reset and then re-install 0.24 (as I think I should have) ?
2) Is the only way to make it reliable to go for a customised ROM/Kernel/Bootloader etc ?
3) If (2) is true and I need a different ROM/kernel etc which is the most reliable ?
I know I need to do the downgrade, root, clockworkmod etc but can probably handle that from other threads.
Many thanks for anyone taking the time to respond.
1: A factory reset *May* help, but there's problems with official ICS anyway.. I haven't tried stock ICS and have no intention of trying it with all the horrid reports I read.
2: I would say this is your best option, put a ROM on, you won't regret it.
3: You will need to flash a ROM, boot it once, then wipe caches again and flash a kernel. As for kernel IMO your best choice is Guevor's kernel, (I'm using v20.6 and it's perfect.) As far as ROM I recommend ARHD or Revolver if you like stock look, and Megatron or AOKP if you like AOSP based roms. (its all preference here)
15 reboots in one day? Have you tried a factory reset yet? That sounds excessive.
But I have zero problems with ARHD 3.4 and Guevors kernel.
As the 2 previous posters suggest - I think a factory reset could possibly help.
If not then I would root, and install a custom ROM. I'm using Revolver and stock kernel with zero RR or SOD. I tried Guevor's kernel and it just didn't agree with my particular TF-101. I also tried ARHD and it worked great but I just prefer the aesthetics of Revolver. Good luck and I sure hope you get your reboot issues fixed soon.
Many thanks for the help, I will do a factory reset.
I suspect that won't work so will look in to rooting and custom roms etc.
I gather I need to downgrade ?
I know there are instructions out there so I will go and have a look at them in preperation !
Thanks again.
rege0039 said:
Many thanks for the help, I will do a factory reset.
I suspect that won't work so will look in to rooting and custom roms etc.
I gather I need to downgrade ?
I know there are instructions out there so I will go and have a look at them in preperation !
Thanks again.
Click to expand...
Click to collapse
As you have had the unit over a year --> old serial# --> it has to be nvflash-able. So you have an option for an easy one-step installation.
Erm, OK - now I am a bit lost !
I want a rooted machine, Clockwork mod and a chance to try custom roms and kernels.
I seem to be able to find instructions for one but not the others, some want to put back stock rom but I am don't want that.
Sorry to be thick, and maybe I'm looking in a panic and getting lost but is there some instructions to follow to take it from 0.24 to being rooted and able to load custom roms. If I get to Clockwork mod I know how to use that to flash etc as I had it on my touchpad before I want completely to Android.
nv-flasable - what does that mean ? Can I check my serial number to know I can do it ? Stickers seems to have come off so not sure I know serial
Sorry for sounding confused and not looking enough - I really have tried but can't seem to get instructions that go from where I am to where I need to be !!!
Thanks again.
NvFlash
NvFlash is a utility that older tabs (With Sbkv1) can use to easily flash a recovery on the system. ASUS has basically two passkeys for the TF101 to get into APX mode, Sbkv1, and Sbkv2. Sbkv1 is the passkey everyone has, and Sbkv2 is currently unknown/locked. What Sbk you have is based on the serial number of your tablet (you can look at the box if you still have it, or find the stickers, also when did you purchase the tab, if it was before July 2011 then you for sure have Sbkv1, if not it may be Sbkv2) If your serial number starts with B60 or below (B50 B40 etc...) it has Sbkv1, if it has B70 or higher, it has Sbkv2. Find out what Sbk you have (it should be version one) then download NvFlash from Rayman's thread. Search nvflash unbricking released in the development forum. Once you have that get an NvFlashable recovery (I recommend Rouge XM touch recovery 1.5, since it reads from internal and external memory, again search in development.) Boot your tablet into APX mode and connect to your computer (Turn off, hold Volume-UP and power.) Install the driver, then follow instructions from NvFlash thread to flash the new recovery. Once you have this, you can place a ROM on your tab (All roms are pre-rooted, no need to install superuser) boot into your new CWM recovery with Power + Volume-DOWN, then press Volume-Up after a few seconds. Wipe data/factory reset, wipe cache, wipe Dalvik-cache, install zip from... find your ROM.zip (don't extract it) and install! Then reboot and let it install, after booting once, you can go back into CWM recovery to install a kernel.zip that you also place on your tab (I recommend Guevor's kernel, make sure you wipe cache and dalvik-cache again.) Then you're all set!
Any other Q's?
Ok. I think I follow all that. Many, many thanks.
I will go to work tomorow and look for the box, but I'm pretty sure it was bought before July 2011.
Need to do something, sure it's cos I am now counting but today held the record at 29 reboots ! Four within 8 minutes at one point.
I think I will go Android Revolution and the kernel you mentioned.
Would be great to bo rooted as I have Titanium license as well.
Thanks again. webOS forums were always good, XDA proving so as well.
Nvflash was just released for Sbkv2, so just use NvFlash, it's easiest good luck!
Thanks for following this up with the latest news !
As far as I can see the wheelie setup is for LINUX only ?
I'm on Windows 7, I could set it up as a dual boot but am complete newbie at Linux !
It's not that bad to set up, just download virtualbox from Oracle, then an ubuntu.iso installation, and run it as a virtual machine within windows. Easier than dual boot. It isn't too hard to set up, essentially download and extract.
So ...
Good news is got it rooted, clockworkmod installed (using the Rogue version that was suggested) and then went installed Android Revolution latest version. Did all the required resets, dalvik and cache wipes etc.
Great I, thought, until ...
All day to day it has rebooted frequently even though I installed no other s/w - just what comes with Android Revolution. It seems to more frequent when the device has powered down after a period of inactivity.
Is it now time to start thinking this is a h/w problem ?
Will a different custom ROM be worth a go or would a different kernel help (which I haven't tried yet) ? If so I wasn't sure which version of the suggested kernel (Guevors) I should go for as there seemed to a lot of them.
Once again, thanks for any and all time. NVFlash was a revelation and really not that hard once I had the drivers installed.
Have now installed v21 of the kernel and got CPU tuner to change minimum cpu speed, wasn't sure about voltages.
Is there a recommended way to set cpu speed, governors and voltages ?
At the point of thinking this will never be stable again. Not even getting 30 minutes without a random reboot.
Try version 17c of guevor's if 21 is giving you issues, and any Cm9 based build will have overclock change built in. I don't use overclock apps, they give me problems. Make sure you SuperWipe, then try reinstalling ARHD (or a aosp/aokp/etc rom) flash either 20.1version6 guevor or 17c and don't overclock (default it overclocks a bit to 1200). See if it is finally stable, if not you might have borked hardware :/
It's charging at the moment, after I night of rebooting I presume.
I've got the SuperWipe zip so I will run that (which I didn't before but did do a reset, cache and dalvik wipe) and then put Revolution on after that.
I looked at Megatrons ROM as well - any comments on its reliability ?
I've not noticed it only does it when the device has been left for a few minutes. If I keep using it and don't let it sleep then things seems OK.
Megatron is really stable, I've found. I like aosp better too.
Those who experience rr or SoD can downgrade via nvflash to Any custom rom , prime 1.4 for example, and then upgrade by way of cwm to an ics aopk to make those problems disappear?
EDIT: megatron is very stable and have an awesome battery life. And the pop ups telling us there's a new update is great too
Sent from my Transformer TF101 using XDA Premium HD app
Hi,
Have been away with unreliable internet access but am now back.
I'm starting to think there must be a h/w problem as nothing seems to make the thing stop rebooting. The only pattern I can see is that if the device is being charged (either from the mains or by being plugged in to the keyboard) then it seems to stay up. Not sure if a certain battery level makes a difference.
I went through the whole SuperWipe clean and Revolution install, then put on the 17c kernel (At least I think I did About shows 2.6.39.4-g8fc25a9-dirty for the kernel, is that right ?) and am still have lots of reboots.
Tried Megatron with the same kernel and couldn't get wifi but still got a couple of reboots.
Any other suggestions ?
Or does anyone know a way of getting repairs done on this in the UK ?
You'll want to RMA to ASUS if nothing works :/
Related
Got S-OFF yesterday and used gribger break to root the phone and all was well.
Didn't install a custom rom ,but now this morning the phone won't reboot past splash screen and keeps rebooting at splash screen. Is it bricked?
Take the battery off, start the phone with vol - preseed and do a factory reset.
When I go into CWM and try the reset it goes through the motions but upon reboot its still the same problem
Don't go into CWM just do a normal factory reset, if it doesn't work i guess you could put a ROM on the SD and install....anyway your phone is not bricked.
Lol before i got S-off... so with s-on i modified a theme, and i got the phone into a boot-loop, the factory reset solved my problem
Thanks , when do factory reset it seems to tale me to CWM recovery by default? any way round this? .
Also your help is much appreciated
Don't know.... i'm almost as new to this as you are...
Put a stock RUU on your sd card and install it... or a custom one.
before it goes to CWM it seems to flash up an error msg .As far as i can make out it says PG88DIAG.zip no image
Morning, The fact that you can still get into CWM is good,
Is your phone recognised, when you plug in usb?
I suspect that you'll need to run an official Ruu (rom upgrade utility) which you run from the pc.
But first try the following
1) download wipe utility http://bitly.com/kpb0A2?r=bb
2) download custom rom http://bitly.com/jnV3em?r=bb
3) copy both files onto sd card, put card in phone
4) boot phone to CWM
5) use the "flash zip files from sd" option to flash both zips in order above, wipe and then rom
6) then reboot
Good luck
EDIT: don't understand the error message that you're getting haven't heard of that.......
does CWM appear to work though, and the wipe you tried from there worked? Our returned cheerfully and came to with the correct messages?
No When I plug it in to the PC HTC Sync isn't picking it up , going to try your other suggestion Ben
Yeah cwm does appear to work it has the status bar and all
Just d/l the rom now then will try that
Just starting to install the rom now .
Does this take some time ? as install bar does not seem to be moving?
ben_pyett and .sh4d0w. you are both stars and I thank you very much. Got that custom rom installed Ben and everything seems ok.Just need to set the phone up the way I like it again lol.
.sh4d0w. thank you for setting my mind at ease 2 months into a 24 month contract and waking up to what i thought was a bricked phone scared the living S*** out of me .
Panic over .
Hopefully I will be able to pass this info on to anyone that needs it in the future
No problem.. glad i could help.
I'm also on a 24 month contract (22 left ), but i just couldn't resist to s-off my phone and try a new rom
Same here even though I was more than happy with it .
Ben one more quick question then i'll leave you be. Do I need to keep the rom zip on the memory card after i have installed it ?
det66 said:
ben_pyett and .sh4d0w. you are both stars and I thank you very much. Got that custom rom installed Ben and everything seems ok.Just need to set the phone up the way I like it again lol.
.sh4d0w. thank you for setting my mind at ease 2 months into a 24 month contract and waking up to what i thought was a bricked phone scared the living S*** out of me .
Panic over .
Hopefully I will be able to pass this info on to anyone that needs it in the future
Click to expand...
Click to collapse
Very glad to be able help to a positive outcome and Very happy that you got it all sorted.
If you intend to stay on that ROM, (I like it) then I'd recommend that you also apply the following (which should all applied via flash from zip option from SD card)
UNITY V2=[SENSE 2.1][OC/UV][CIFS/TUN][SLQB][V(R)][2WCR] V2
later version of kernel that comes with the base rom (kernel updated since rom released)
4EXTRecovery v2.0.2 RC2
which is a re-worked version of CWM (improved, easier to use with more options ) - would recommend this as it currently has great support and is updated very regularly.
There is also the option to install the Engineering (ENG) HBOOT, which is an improved bootloader that gives you more options which are useful in advanced recovery situations. Although I don't know the implications of using it with AlphaRex but believe that there's a thread specifically about this which I'd suggest that you read.http://forum.xda-developers.com/showthread.php?t=1161158
[A] you don't need to leave the ZIPs on the SD card but they do no harm there, I find that it's useful to leave them there, I always leave the ROM that I'm running on on my card - in case I experience any problems.
There is also the option the flash new radio, but this is very much user, location and network specific so only do so if you're having problems.
You may need to re-calibrate you battery having moved to new the ROM see instructions on SAGA thread, see how battery usage is first.
The only bug that I know of in LBC ROM is the ADVANCED POWER MENU (which you get by long hold on power button)->RESTART-> HOT RESTART hangs the device requiring battery removal - so don't use it!
Thanks for the tip .do you know if this is overclocked by default and if so to what speed ?
det66 said:
Thanks for the tip .do you know if this is overclocked by default and if so to what speed ?
Click to expand...
Click to collapse
it has the ability to be Overclocked, but isn't out of the box, and in my opinion unless you're a gamer, probably it isn't needed, it will just burn more battery
do not install setCPU as this disables the O/C daemon
sleep: min 245MHz / max 368MHz / conservative
wake: min 245MHz / max 1017MHz / ondemand
- > everything can be changed with a text editor in /etc/virtuous_oc
If you intend to stay on this ROM then I suggest that you read the whole thread, so as not to ask questions that have been answered already
ROMS also due an update any time soon.
Read and understood and onceagain many thanks .Gonna read the thread calmly this morning
I have tried all of the ICS roms, and always gets stuck at the same spot. Wi-fi is turning on.
It worked on the Revolver 4, but I wanted to try another one. Did a super wipe, and bam. Nothing after that..
Any thing I might be able to try?
Nandroid restore, if that won't work nvflash?
you mean use NVflash to do the rom install vs the recovery?
I made a topic about this, check my post (not able to give you a link right now sorry)
I also need help with this. I am trying to come from CM9 cornerstone build back to revolver. I have done a couple restores and I still get no WIFI. Anybody have anymore info on this?
Have a look at this : http://forum.xda-developers.com/showthread.php?t=1530612
You can try this:
- Turn off wifi
- rename the file /data/misc/wifi/wpa_supplicant.conf to wpa_supplicant.old
- reboot
- try wifi again to see if it works
**note
This might cause the tablet to forget any previously saved networks.
I have tried Outpoxs' method in varies combinations with no success also I have tired your method a.mcdear and also with no success. Mine is still stuck on Turing WI-Fi on... The one thing with outpox method there might have been something I was doing wrong.
This is how I fixed my tablet after 15 hours of trying everything. I downloaded the ota rooted full version of ics and performed a full wipe then made sure it booted into that rom with wifi working then proceeded to flash my revolver backup with no problems. Hope that helps.
Similar WiFi issue - still stuck
I hate to bump an old thread, but I've recently hit what appears to be a related issue (WiFi stuck off), though perhaps there are some twists to my tale - and I'm still stuck.
I have an early TF101 (B50) and have had it rooted with stock ICS for awhile. Everything has been mostly fine, but I decided to give CM9 nightlies a try.
Here's where my issue differs from the others in this thread. With the CM9 nightly flashed, I was stuck at the boot animation (for hours - left it overnight with no progress). I restored my nandroid backup and now I had the "WiFi Turning on" issue that others here have experienced.
I've tried multiple other ROMS (latest of AOKP, Gummy, and Prime 1.6), with complete wipes, and in each case, I was stuck on the respective boot animation. This completely mystifies me, but it may not be related to the WiFi problem. After each iteration of failed ROM flashing, I can restore my nandroid backup (the rooted stock ICS) and everything works fine EXCEPT WiFi.
Following the suggestions in this thread I've tried flashing a new stock ROM (from http://forum.xda-developers.com/showthread.php?t=1514658) and while that doesn't stick at the boot animation, it also doesn't fix my WiFi. I also tried a.mcdear's suggestion in http://forum.xda-developers.com/showpost.php?p=23446585&postcount=7, but I did not have the file wpa_supplicant.conf in my /data/misc/wifi directory. The only file in there was an empty file called "status." Just for good measure, I tried renaming it, but no joy.
At this point, I'm out of ideas and have a severly crippled TF. I would appreciate any suggestions or ideas from the community.
TIA
--Roger
I've have a rooted TF101 B50 and most ROM's that I have tried seem to fail at this point as well. However, I did notice that when I flashed my first ROM (AOKP) it has the same stock kernel. So I tried another one. This time was Revolution 4. It seemed to work out just fine because I belive it has the stock kernel. Next I moved onto a CM10 Eruoskank ROM. It too had the problem of the AOKP ROM in that after I flashed it, the stock kernel was still present, presumably left over from the Revolution 4 ROM. I am now on Android Revolution HD 3.5.0 and it seems to work fine so I am sticking with it for the time being.
I beleive something in the flashing script of the ROM or the recovery program itself is not flashing the /boot partition properly. I am not a developer nor do I have an in depth knowledge of the inner workings of Android...but this is just a guess. I hope there is a way to flash just a kernel in the /boot partition from these individual ROMs. That would be nice.
If can access recovery then do a full wipe(system, cache and dalvik) and install the ROM again... that should do the trick... you might wanna try some other kernel also... there few kernels for ICS in the forum look for them and flash them via recovery...
Sent from my Transformer TF101 using xda app-developers app
It seems as thought someone else is on the same track as I am.
http://forum.xda-developers.com/showpost.php?p=29447134&postcount=8
rstry this:
take unit out of dock if you use one. restore via cwm if u can, to 3.01 firmware, honeycomb. wipe all cache, data, etc prior to flash.
DO NOT SIGN INTO GOOGLE ACCOUNT.
Turn tablet completely off following boot. Cold boot back on. Grab latest official firmware off Asus website, xx.27
Install via CWM, and again wipe ALL.
Boot into system again, and cold boot back on. Asus should prompt you with 300mB update now, which differs from the official .27,but had same filename...
I found this bug/glitch a few hours ago... Somehow downgrading to HC and back to stock triggers this unknown update...
See if you can reproduce please. I also saved the firmwares to sdcard external.
The various ROMs require a supporting kernel. I would try obtaining the correct kernel for the ROM you want and then flash them both at the same time from recovery.
Resolved - for me
From replies here and other research, it became clear to me that I should reflash my transformer back to stock (NVFLASH down to the metal). Every other ROM would show the stuck WiFi issue or (worse) would get into a boot loop.
This was something of a problem, because my volume up button was broken and I couldn't enter APX mode. I finally managed a workaround for that (see http://forum.xda-developers.com/showthread.php?t=1890236) and then used EasyFlasher to restore the Asus firmware. Now the WiFi works fine and all is well again.
So, as a last resort - scrub and start over.
Cheers!
--Roger
regregoryallen said:
I hate to bump an old thread, but I've recently hit what appears to be a related issue (WiFi stuck off), though perhaps there are some twists to my tale - and I'm still stuck.
I have an early TF101 (B50) and have had it rooted with stock ICS for awhile. Everything has been mostly fine, but I decided to give CM9 nightlies a try.
Here's where my issue differs from the others in this thread. With the CM9 nightly flashed, I was stuck at the boot animation (for hours - left it overnight with no progress). I restored my nandroid backup and now I had the "WiFi Turning on" issue that others here have experienced.
I've tried multiple other ROMS (latest of AOKP, Gummy, and Prime 1.6), with complete wipes, and in each case, I was stuck on the respective boot animation. This completely mystifies me, but it may not be related to the WiFi problem. After each iteration of failed ROM flashing, I can restore my nandroid backup (the rooted stock ICS) and everything works fine EXCEPT WiFi.
Following the suggestions in this thread I've tried flashing a new stock ROM (from http://forum.xda-developers.com/showthread.php?t=1514658) and while that doesn't stick at the boot animation, it also doesn't fix my WiFi. I also tried a.mcdear's suggestion in http://forum.xda-developers.com/showpost.php?p=23446585&postcount=7, but I did not have the file wpa_supplicant.conf in my /data/misc/wifi directory. The only file in there was an empty file called "status." Just for good measure, I tried renaming it, but no joy.
At this point, I'm out of ideas and have a severly crippled TF. I would appreciate any suggestions or ideas from the community.
TIA
--Roger
Click to expand...
Click to collapse
regregoryallen said:
I hate to bump an old thread, but I've recently hit what appears to be a related issue (WiFi stuck off), though perhaps there are some twists to my tale - and I'm still stuck.
I have an early TF101 (B50) and have had it rooted with stock ICS for awhile. Everything has been mostly fine, but I decided to give CM9 nightlies a try.
Here's where my issue differs from the others in this thread. With the CM9 nightly flashed, I was stuck at the boot animation (for hours - left it overnight with no progress). I restored my nandroid backup and now I had the "WiFi Turning on" issue that others here have experienced.
I've tried multiple other ROMS (latest of AOKP, Gummy, and Prime 1.6), with complete wipes, and in each case, I was stuck on the respective boot animation. This completely mystifies me, but it may not be related to the WiFi problem. After each iteration of failed ROM flashing, I can restore my nandroid backup (the rooted stock ICS) and everything works fine EXCEPT WiFi.
Following the suggestions in this thread I've tried flashing a new stock ROM (from http://forum.xda-developers.com/showthread.php?t=1514658) and while that doesn't stick at the boot animation, it also doesn't fix my WiFi. I also tried a.mcdear's suggestion in http://forum.xda-developers.com/showpost.php?p=23446585&postcount=7, but I did not have the file wpa_supplicant.conf in my /data/misc/wifi directory. The only file in there was an empty file called "status." Just for good measure, I tried renaming it, but no joy.
At this point, I'm out of ideas and have a severly crippled TF. I would appreciate any suggestions or ideas from the community.
TIA
--Roger
Click to expand...
Click to collapse
I also have the same issue. Bought the eee pad transformer with a cracked screen; touch screen did not work. I replaced it and everything works great! except for Wi-Fi =\ Any help would be greatly appreciated!
You should really start your own thread. That being said, first thing to try is to back up all your data and wipe it to factory using EasyFlasher. If the problem persists after a stock firmware flash, then it's likely a hardware issue. If it's resolved, then it was a rom/software issue.
regregoryallen said:
I hate to bump an old thread, but I've recently hit what appears to be a related issue (WiFi stuck off), though perhaps there are some twists to my tale - and I'm still stuck.
I have an early TF101 (B50) and have had it rooted with stock ICS for awhile. Everything has been mostly fine, but I decided to give CM9 nightlies a try.
Here's where my issue differs from the others in this thread. With the CM9 nightly flashed, I was stuck at the boot animation (for hours - left it overnight with no progress). I restored my nandroid backup and now I had the "WiFi Turning on" issue that others here have experienced.
I've tried multiple other ROMS (latest of AOKP, Gummy, and Prime 1.6), with complete wipes, and in each case, I was stuck on the respective boot animation. This completely mystifies me, but it may not be related to the WiFi problem. After each iteration of failed ROM flashing, I can restore my nandroid backup (the rooted stock ICS) and everything works fine EXCEPT WiFi.
Following the suggestions in this thread I've tried flashing a new stock ROM (from http://forum.xda-developers.com/showthread.php?t=1514658) and while that doesn't stick at the boot animation, it also doesn't fix my WiFi. I also tried a.mcdear's suggestion in http://forum.xda-developers.com/showpost.php?p=23446585&postcount=7, but I did not have the file wpa_supplicant.conf in my /data/misc/wifi directory. The only file in there was an empty file called "status." Just for good measure, I tried renaming it, but no joy.
At this point, I'm out of ideas and have a severly crippled TF. I would appreciate any suggestions or ideas from the community.
TIA
--Roger
Click to expand...
Click to collapse
Im 99% sure your problem is that you haven't got the right kernel for the rom your using, this is the usual outcome - wifi not working/ turning on. i don't think nandroid backs up the kernel so your basically restoring stock ICS rom with cm9s kernel. Try find the related kernel to rom your currently on. As for your rom failed flashing, you might be using a very old recovery try updating to the newest twrp recovery. Better yet join the dark side and move up to Jelly Bean, makes the tf101 a whole new device.
Hi everyone, I had a problem with my previous nexus s (I have since gotten a working replacement) and I was wondering where exactly I messed up so in the future I can avoid this
Here is what I did on my previous phone:
1. I flashed ics onto my device from the ota update package from androidcentral, it was 4.0.3. (This worked great and I had it on my phone for 2-3 months before I tried the next steps.)
2. I rooted my device successfully using the guide at nexusshacks.
3. I also flashed TWRP recovery (fastboot) and superuser using the above guide/links
4. When I would turn off my phone it would boot to a screen with a red triangle and an opened android bot. So what I would have to do is flash twrp recovery everytime I turned the phone on just to get it to work.
5. What I wanted to do was keep the stock rom but still have twrp recovery without it making me reflash it on every boot. So I clicked install and tried to flash the stock rom (update package from the link in step 1) with twrp recovery. It then turned off my phone and hard bricked it. I couldn't turn it on anymore and a new battery didn't fix it.
I was able to get a replacement now and I was just wondering at which step did I go wrong? I THINK that I should have wiped my cache before I tried to reflash the stock rom but maybe I'm way off base here. This is why I posted a question here so hopefully some of you guys can help.
I did think about posting in another thread, but I didn't wanna threadjack or anything... and his problem also seemed a bit different then mine. Also, sorry about not being able to provide the specific links it won't let me post them until I've posted 8 times.
I don't know for sure but team win recovery has been reported to corrupt the device's efs directory. I've even had problems myself using clockwork recovery. I've moved on to razor recovery and haven't looked back.
This is the most flash-friendly phone I've ever owned, and razor recovery rivals amon ra (which was awesome on my g1 and evo). I really think it may have just been the recovery you were using... Somebody correct me if i'm wrong.
Sent from my Nexus S 4G using Tapatalk
I had once corrupted one of the partition. I fixed to by flashing stock recovery and stock rom.
Use adam outler's unbrickable mod tool. It can be found in android development section.
Sent from my Nexus S using XDA
Thanks for the replies.
That's interesting about twrp... I didn't know that. Truth be told, the only reason I went for it over other ones like clockwork mod was because the UI looked pretty nice and easy to use. Also the guide I followed at nexusshacks used that, so I wanted to stay consistent with it.
jishnu7, it's a little late for that now however as I actually have already received a working replacement from my carrier, but in the future if something ever does go wrong (hopefully not) I will definitely check that out.
The main thing I'm wondering is if it messed up because I tried to reflash the stock rom essentially over top itself (was hoping that by doing that, it would stop making me reflash twrp on every reboot) or if it was because I didn't wipe the cache before the flash.
Also, what I really wanted to do with my phone was to keep the stock rom but be able to overclock my cpu/gpu. I was hoping I could set different overclocks for different things (I've heard of kernels where you can downclock your phone when the screens off and have it overclocked slightly while you're using it, that would be something I'd like to have). I figured to install those kernels I would have to root my phone, replace stock recovery and install superuser so that's why I tried to do that. Once again, I'm pretty new to all this stuff for my phone.
Sorry to bump this thread again, but I would really like to know how I could avoid what happened to me for the future. I think it's because I flashed the stock 4.0.3 rom over itself (was hoping that by doing that twrp recovery would stay on the phone after reboot).
What I would like to do is install something like CM9 or AOKP and use the Matr1x kernel so I could undervolt or overclock my phone.
I seriously dont get how u hard bricked your phone...
the reason you are thinking is you reflashed stock rom without wiping cache, as per my experiece its not at all the reason
now, whats my experience??
...I have some fault with my nexus device and I'm working on it,,and I did everything I could do...one of the thing out of those things was reflashing stock rom without wiping,and i did it quite a several times...my device never hard bricked,,however it was soft bricked for many times,,and i recovered from it
so reflasing a stock rom over stock rom, over ICS, over some themed custom rom,will not hard brick your device, you must be missing something none of your steps sounds suspecious
P.S:- pulling out battey while flashing something like this sounds suspecious, never tried though
I'm not sure what happened either to be quite honest with you. Since giving it another shot now with my new fresh phone I have had great success!
I did everything I wanted to do all in one go. Rooted it, install CWM touch, install AOKP (went with milestone 4 cuz I heard newest build 29 has some bugs) + gapps and installed matr1x kernel 18.5 bfs.
The only thing I did different from last time was installing CWM touch (instead of twrp) and flashed aokp this time (instead of reflashing 4.0.3 over itself).
I would just avoid step 2 at all cost.
The nexus s hacks dude is a tool.
Good morning,
While not a noob to rooting or flashing (currently active on Galaxy tab 2 boards) I appear to have made a noob mistake, and even though I searched and read stickies, etc - still made the mistake.
I rooted the Rogers Infuse 4G using this thread http://forum.xda-developers.com/showthread.php?t=1197248 and it worked without issue.
Decided to try the enable lag fix option - deleted the voodoo file on the sd card, and rebooted the phone. Phone got stuck on SAMSUNG screen (unfortunately - did not notice that the volume was off on the phone) and I did not hear the "voice" telling me what was going on - so rebooted the phone by holding the power button until it rebooted.
Spent a couple of hours after that re-reading, and since I was able to get into download mode - was able to reflash stock package through odin. When the phone did finally reboot (thankfully, as this is my daughter's daily driver) I noticed there was already a voodoo file on the sd card, with another file inside named "logs" Just in case, I deleted that file, and added a new one called "disable-lagfix" as per the original instructions.
Just to be sure - went back and ran the rooting procedure, and can confirm that we have root.
From there, I decided to flash the 100% working CWM Recovery file through Rom Manager - found the details on this thread http://forum.xda-developers.com/showthread.php?t=1107881 and can confirm that after rebooting into recovery - the phone has CWM Version 2.5.1.2
The phone is currently fully functional, no issues with network or wifi, playstore, etc - but would like to know if anyone can confirm that we are good to go should we decide to upgrade to a custom rom. I've done so much reading - that the recovery version confuses me ( red or blue, etc). I realize that some of the threads are back from early to mid 2011 - so not sure if they are still completely valid - so am asking before proceeding.
Phone settings are the following:
Kernal 2.6.35.7-I997RUXKG3-CL366622
Build GB.UXKG3
Baseband I997RUXKG3
Firmware 2.3.3
CWM 2.5.1.2
Currently have the voodoo/disable-lagfix file on the sd card
If anyone has gotten this far into the thread - and can offer up some feedback or recommendations - it would be appreciated
Thanks in advance,
Bill
I usually don't trust Rom manager, but if you are able to boot to recovery then I would say you are good.
If you want the red one (don't remember the version) you could flash a custom kernel with sgs kernel flasher (available on play store).
Infusion should work for you
andros11 said:
I usually don't trust Rom manager, but if you are able to boot to recovery then I would say you are good.
If you want the red one (don't remember the version) you could flash a custom kernel with sgs kernel flasher (available on play store).
Infusion should work for you
Click to expand...
Click to collapse
Thanks for the reply - appreciate your time
Guess it's time to turn that volume up, delete the voodoo folder, and cross my fingers....
Just to confirm - do I delete the voodoo folder itself, or the disable-lagfix folder inside the voodoo folder only ?
Again, thanks
:good:
What were you planning on flashing?
You can probably leave it there for now, and after you have flashed then you can dispose of the folder.
Sent from my Transformer using xda app-developers app
andros11 said:
What were you planning on flashing?
You can probably leave it there for now, and after you have flashed then you can dispose of the folder.
Sent from my Transformer using xda app-developers app
Click to expand...
Click to collapse
First off andros11 - thank you so much for your time in replying to my issue.
My daughter has been looking over the development site - and,
as it stands right now, she has her mind set on the Dark Night Rom by VortexJunior.
Here is the link, if it helps http://forum.xda-developers.com/showthread.php?t=1662280
The install instructions, while relatively simple - and similar to what I am used to doing - but no mention of lagfix
Installation: From Gingerbread
1. Download Zip
2. Wipe Data/Factory Reset
3. Wipe Cache Partition
4. Flash
5. Reboot into recovery(Advanced>Reboot recovery)
6. Flash again
7.BAMM!
Thanks again for your time and replies,
Regards
Once on ICS I don't think you have to mind about lag-fix..
Also, I suggest you just reboot instead of rebooting into recovery. That often causes recovery bootloops.
When you reboot, the phone will hang at the kernel splash screen (this is normal). Just take out the battery, place it back in and boot into recovert with 3-finger combo (vol +, vol - and power, and let go when samsung logo pops up)
My personal suggestion is that you move on to JB. It performs much better, and mostly all development is now there.
Perfect - thanks
Am running CM 10.1 on my tablet, and love it
Will have my daughter research JB ROMs instead.....
Happy Holidays to you and your family
Regards,
sent from my GT-P3113 using Tapatalk 2
Lag fix??
I am confused.. what exactly is the lagg fix? My GF has a JB (one of phablet ROMS) installed and all the JB ROMS I have installed on this phone (and I think all ROMS besides JB) have had lagg problems. So I would really like to know how to fix this phone.
About that lagfix...
If I remember correctly voodoo lag fix was originally designed for the Galaxy S to change the file system it ran at to something that made the phone feel more responsive and access recourses quicker. It was ported to other ROMs so if a ROM includes it then you're ok to use it but I don't think you can just apply it to any JB ROM. Plus after using a GB ROM with this lagfix for some time, any 4.0 and above ROM I have used after that has been a LOT quicker in comparison. So I would probably look into the way you JB roms were installed maybe do a data wipe/factory wipe in CWM and reinstall the ROM from the beginning. What ROMs are you using exactly?
My issue has been plaguing me for several weeks now. I just stared developing for Android, so I'm a bit of a noob (forgive any obvious mistakes that I have made, or do make)
I have an HTC EVO 3D that I got about 8 months ago. One of the first things I did after I got it was root the puppy and flash a custom Gingerbread ROM to it. That worked great as a development tool for a while, with no issues, whatsoever.
After some time, I updated my custom Gingerbread ROM to a custom ICS ROM, which again, worked fine, minus the minor inconvenience of it occasionally rebooting when I would hit the debug icon on my IDE (Eclipse). That would only happen every once and a while. However, one day last week, all it did, when I hit debug, was reboot. I figured that the ROM was bad in some way, and flashed a custom JellyBean ROM to it. Same issue. I flashed another JB ROM(CM 10), with the same issue. After that, I've done everything that I can think of to fix this issue. I've tried flashing everything that Clockwork would let me flash (Dalvik, cache, did a factory reset, etc) I tried reformatting the SD card, and even tried 3 new ones. I tried reflashing the ROM, I tried 3 other computers, and even re installed Windows on one of them! In my experimentation, I have discovered that it also reboots when I try to record video with the native JB camera (I say that because I installed another camera app from the Play Store, and that works fine).
I'm thinking maybe a memory leak? I honestly have no idea.
HTC EVO 3D
HBOOT 1.40
S-OFF
Thanks in advance
Next step is to use the Eclipse debugger and read the debug output once it crashes/reboots. The output from the debugger will provide more information about what happened so you can start narrowing the problem down more.
It's a memory or cpu problem (i guess) . Try the cpu a bit lower. I hope it will help you
If you have flashed your phone allot, and you have under clocked your CPU first, it may be a NAND issue. It has been a problem on my end with the HTC HD2 after like 1000+ flashes. You should be able to use a tool to check for bad NAND blocks, don't remember off the top of my head what it was called when I used it but that's something you could do. That is all (if) you have not tried to under-clock your CPU first and make sure the ROM is not bugging out like it sounds like it is.
Another way to test your NAND is to try a SD ROM that runs on your MicroSD card.