I have flashed Revolver 4 by Gnufabio 4.0.0 Beta 1.3.1 recently and I've had no problems with it for the last 4 days. However, I locked the screen today and somehow my transformer turned off. When I try to turn it back on it shows a low battery logo for a second and shuts off. (it's fully charged) I can't access recovery and since my tranformer is a SBK2 model, I can't flash it again with Nvflash. Should I wait till the battery drain and attempt to get in recovery? What should I do? Am I screwed? Does anyone have this similar problem?
one
one
two
rticphreeze said:
one
Click to expand...
Click to collapse
two
I don't think you can flash a stock ROM through cwm.... Go back to stock(unroot) using nvflash/easy flash method and once you have a untooted tf101 go back to rooting if you like to....
Sent from my Transformer TF101 using xda app-developers app
Related
I have CWM installed so I could flash CM7 easily for each night build.
I am thinking to try out ICS. back to about 2 months ago, I could flash to ICS but the camera doens't work out well so I roll it back.
today, I see a lot of updates so I decide to give it a try again. I follow the instruction until "9.When welcome screen appears, DO NOT TOUCH ANYTHING, let sit for 10 mins." After I reboot, I don't see "welcome screen" I only see LG logo popup, then I see "LG Logo with waves" for 15 minutes and then nothing happens. I just wonder if I did anything wrong? thanks
I have ext 4
Would help if we knew what exactly you were flashing.
Sent from my LG-P999 using XDA
if your flash took only a couple of seconds.. then redo the flash until it takes more than 15 seconds. Your symptoms look like flash problem that is a known issue.
desynch- said:
Would help if we knew what exactly you were flashing.
Sent from my LG-P999 using XDA
Click to expand...
Click to collapse
Sounds like he flashed Genesis ICS rom by Mr.Apocolypse
Sent from my LG-P999 using xda premium
more info
sorry, I forget post more info.
I tried these two ROM:
1. HellFire ICS
2. Kang ICS
both have the same problem.
by the way, I did the backup before doing ICS. the first time roll back, it asked me to setup account like a new machine! so I did restore again. then second got fully restore. currently I am using CWM 3.0.1. I just wonder if this makes difference?
when I flash CM7, it took few minutes, but when I flash ICS, which is fast! only about 15 seconds. does this sound right?
thanks!
CWM 3? Update your CWM to the latest version (5.0.2.8 for normal CWM, or 5.8.1.3(?) for touch recovery). That might alleviate all your problems.
Yea I imagine you have an SD card just like the dude above me mentioned go with the newest cwm.Same way you flash 3
Sent from my LG-P999 using XDA
Since I updated to ICS the pad shuts down or reboots by itself and then it gets stuck on the Asus splash screen, it happens almost every day. Can anyone help me with a solution please??
Sent from my SAMSUNG-SGH-I727 using xda premium
Hi r3dp0is0n2012
I think its safe to safe that this is a ICS/Asus problem. I think in every forum about ics the same complain is there.
I had the same. My tf has nvflash capabilities, so after a week or reboots and hanging, I wiped every thing on my TF. Then put a nvlash version honeycomb back. Then installed cwmrecovery of gnufabio and also rooted the pad again. Then flashed/restored a good working revolver rom 3.11.1 cwm backup on my pad (was my own backup before updating) and all works correct again. Last week I updated/cwm-flashed my pad with revolver 4.0.0. rc1 (after just wiping cache and delvik) and its now rather stable. Only have reboot in 2 or 3 days. but real reboots, so no hanging in boot screen. But this means that ICS is still unstable. So, if you have problems and you know how to go back, or have a good backup, use that......or wait for a fix by Asus.
If you need help to go back, let us know all info of your TF pad? what kind, what serial etc etc....and maybe we can help....
nlheiz said:
Hi r3dp0is0n2012
I think its safe to safe that this is a ICS/Asus problem. I think in every forum about ics the same complain is there.
I had the same. My tf has nvflash capabilities, so after a week or reboots and hanging, I wiped every thing on my TF. Then put a nvlash version honeycomb back. Then installed cwmrecovery of gnufabio and also rooted the pad again. Then flashed/restored a good working revolver rom 3.11.1 cwm backup on my pad (was my own backup before updating) and all works correct again. Last week I updated/cwm-flashed my pad with revolver 4.0.0. rc1 (after just wiping cache and delvik) and its now rather stable. Only have reboot in 2 or 3 days. but real reboots, so no hanging in boot screen. But this means that ICS is still unstable. So, if you have problems and you know how to go back, or have a good backup, use that......or wait for a fix by Asus.
If you need help to go back, let us know all info of your TF pad? what kind, what serial etc etc....and maybe we can help....
Click to expand...
Click to collapse
Thank you for your response, very helpful by the way! I do want to go back and restore it. How can I do this?
Sent from my SAMSUNG-SGH-I727 using xda premium
Sorry was not around a computer yesterday.....
Impotant is to know what kind of TF you have and serial number.
I have a B50.....so I can use nvflash. What is your serial? do you have CWM installed, or can you check if you have a SBK1 or SBK2 TF. Do you have cwm installed, do you have nandroid backup of honeycomb etc etc.....I have some experience with downgrading, but not regarding the SBK2 TF's. Some say that if you download an older updater op asus (see some where in this q&a where you can download it) then unzip it on your sdcard, reboot and your TF will ask if you want to load this "newer" rom. This is also mentioned somewhere in this q&a. maybe that will help. But 1st of all, to be able to help in downgrade, we need your tech info of your TF.
serial number TF
CWM installed (see app of gnufabio)
nvflash possibitities
EDIT: more bad new about this reboot thing
http://forum.xda-developers.com/showthread.php?t=1569670
and see this last post in that thread,
http://forum.xda-developers.com/showpost.php?p=25375664&postcount=87
so, nvflash is your only option seem like.....I hope that you have a nvflash compatible TF (B60 and less and some B70....SBK1)
Hello,
Yep news are getting worst...
my serial number is C10 model TF101
I dont know if that helps.
r3dp0is0n2012 said:
Hello,
Yep news are getting worst...
my serial number is C10 model TF101
I dont know if that helps.
Click to expand...
Click to collapse
Have you tried wiping data?
no I haven't... you mean restoring to factory settings?
Do you have CWM installed on your TF?
I have a really bad problem, my gf and I recently both got the Verizon galaxy s3 from Amazon wireless. I happen to like mine. In a day I rooted, flashed Synergy and won't go back.
Now..my gf's galaxy is a different story. From day one,.Hers likes to shut off by itself or become unresponsive (with the blue light blinking in sleep mode. The only fix is to pull the battery and restart.
Here is what I've tried..
Browse the hell out of forums (mainly yours)
Changing stock settings.
Flashed a custom ROM to see possibly it's the stock rom was broken. Same issue
Used my battery to see if it was a bad battery.still didn't fix it
Flashed a different kernel to see if the kernel is to blame. No dice.
Wiped to stock using Odin. Nuh uh.
I'm pretty much out of options.
I'm thinking about sending it back.
Hers has Synergy on it atm. If no one has any options left, can I just Odin back to stock, lock the bootloader, and use triangle away?
Thanks
Sent from another Galaxy far, far away using xda premium
stanleyopar2000 said:
I have a really bad problem, my gf and I recently both got the Verizon galaxy s3 from Amazon wireless. I happen to like mine. In a day I rooted, flashed Synergy and won't go back.
Now..my gf's galaxy is a different story. From day one,.Hers likes to shut off by itself or become unresponsive (with the blue light blinking in sleep mode. The only fix is to pull the battery and restart.
Here is what I've tried..
Browse the hell out of forums (mainly yours)
Changing stock settings.
Flashed a custom ROM to see possibly it's the stock rom was broken. Same issue
Used my battery to see if it was a bad battery.still didn't fix it
Flashed a different kernel to see if the kernel is to blame. No dice.
Wiped to stock using Odin. Nuh uh.
I'm pretty much out of options.
I'm thinking about sending it back.
Hers has Synergy on it atm. If no one has any options left, can I just Odin back to stock, lock the bootloader, and use triangle away?
Thanks
Sent from another Galaxy far, far away using xda premium
Click to expand...
Click to collapse
What build was your Synergy ROM? I've had difficulties with any ROM after about 3/23 due to some problems with the whole 3.4 thing. I'm not familiar with the Synergy ROM (obviously I've heard of it, but I don't like the stock "feel") and the problems that I've encountered have been on AOKP and CM based ROMS. But you may want to try flashing an earlier build. I went back to a build of the ROM I use from 3/13 and the problems I had that were similar to the ones you described stopped.
I've been running synergy for months now, and with almost all of their different releases. I have never had random reboots like that though. If you are using r420, or pretty much any of the newer releases, make sure you are doing a full wipe and not restoring any app data. That's the only way to make sure it isn't the ROM causing it. If it's still a problem, use that manufacturer warranty
Sent from my SCH-I535 using xda app-developers app
SynergyROM is awesome agreed. I had similar problems at one point due to my voltage settings. Not all phones are created equal. Increased voltage and changed governor to 'on demand' because 'interactive x' had problems at the moment.
Some have just flashed a different kernel but imo ziggy is a genius and I will rock his kernel as long as he makes one.
The issue is one one of the builds ziggy and I think phones with rev4 couldn't handle the low volt
The blue light blinks or stays on for a bit like when booting.?
Clearly..... It your phone does it on a stock kernel,
I highly doubt the software is causing it.
It sounds like somewhere across the line you have a hardware issue.
Oh damn...hardware..that's what I suspected. Should I do the three steps (odin, re-lock , triangle away) and send it back to Amazon?..or sammy?
And will they know if I messed with it?
Sent from my SCH-I535 using xda premium
I'm having the exact same problem with the latest AOKP and CM10.1. I reverted back to an older version to see if this fixes the problem.
stanleyopar2000 said:
Oh damn...hardware..that's what I suspected. Should I do the three steps (odin, re-lock , triangle away) and send it back to Amazon?..or sammy?
And will they know if I messed with it?
Sent from my SCH-I535 using xda premium
Click to expand...
Click to collapse
triangle away first then odin, since you need root to use triangle away. re-lock not necessary if you flash a stock image.
reslor1 said:
triangle away first then odin, since you need root to use triangle away. re-lock not necessary if you flash a stock image.
Click to expand...
Click to collapse
+1. Also, Odin will not up your flash counter unless your flashing something that isn't stock......Odin as the last step will leave you at out of box stock.
Sent back the phone. Hope for the best
Sent from my SCH-I535 using xda premium
Amazon apologized and she got overnight a 32gb s3 for the same price as the 16. This new one has no sleep issues
Sent from my SCH-I535 using xda app-developers app
I have been running EOS4 on my TF101 for a while, and I decided to try the Kat kernal to see if it can improve performance. I flashed it through CWM right after I did a Nandroid backup. Now all of a sudden my battery won't charge. If the device is plugged in, the upper right indicator shows charging, but the lock screen and battery section of the settings page show not charging. And if I have the unit plugged in and running, it will lose charge. If I plug it in and shut it down, it will pick up maybe 30% overnight. I also tried a recovery through Nandroid backup, but it left the kernel and my problem stayed. I assume Nandroid backup doesn't effect the kernel. For the record, the kernel I used was Tim_KatKernel_103_JB4.2_Lidpatch. I have the most recent EOS4. I believe it's 114. Any help would be appreciated.
I can't believe there is not a single response to this issue. That does lead me to believe that this is not a common problem with the Kat kernel, and just maybe it's a coincidence that this occurred when I updated the kernel. Maybe I'm just having issues with the 5/15v charger. I have one on order and we'll see if that fixes it. I'm also curious if Nandroid backup is supposed to back up the kernel.
Sent from my Transformer TF101 using xda app-developers app
hambcastle said:
I can't believe there is not a single response to this issue. That does lead me to believe that this is not a common problem with the Kat kernel, and just maybe it's a coincidence that this occurred when I updated the kernel. Maybe I'm just having issues with the 5/15v charger. I have one on order and we'll see if that fixes it. I'm also curious if Nandroid backup is supposed to back up the kernel.
Sent from my Transformer TF101 using xda app-developers app
Click to expand...
Click to collapse
I believe the newer versions of cwm backup the custom kernel in the nandroid.
Sent from my SGH-T999 using Tapatalk 2
Let me start by saying that I am not new to flashing Roms on my devices, that being said I have never had an LG phone till now.
When I go in to Twrp and try to flash a new rom or even wipe it tells me it can't mount system. I've tried fixing permissions but nothing helped. I ended up having to use Nexus tool to restore phone to stock. (lost everything on phone)
I got the phone rooted and flashed carbon rom but decided that I wanted to flash a rom with 4.4.1 and same thing happened with phone not able to mount system. This time I was able to restore a Twrp backup I had and then flash the stock 4.4.1 rom available on this forum.
Is there something with this phone that is different then flashing on others? Can't seem to flash more then once without going back to stock? I have 2 nexus 7's 2012 & 2013 models and everything seems fine on these have flashed numerous Roms without a hitch.
I came from GS3 and have Asus prime, Motorola, HTC and just about every other manufacturers device in my house. Why is this one giving me so much issues.
Also battery won't charge past 77% now. Any ideas?
Sent from my Nexus 5 using XDA Premium 4 mobile app
nelomen said:
Let me start by saying that I am not new to flashing Roms on my devices, that being said I have never had an LG phone till now.
When I go in to Twrp and try to flash a new rom or even wipe it tells me it can't mount system. I've tried fixing permissions but nothing helped. I ended up having to use Nexus tool to restore phone to stock. (lost everything on phone)
I got the phone rooted and flashed carbon rom but decided that I wanted to flash a rom with 4.4.1 and same thing happened with phone not able to mount system. This time I was able to restore a Twrp backup I had and then flash the stock 4.4.1 rom available on this forum.
Is there something with this phone that is different then flashing on others? Can't seem to flash more then once without going back to stock? I have 2 nexus 7's 2012 & 2013 models and everything seems fine on these have flashed numerous Roms without a hitch.
I came from GS3 and have Asus prime, Motorola, HTC and just about every other manufacturers device in my house. Why is this one giving me so much issues.
Also battery won't charge past 77% now. Any ideas?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
the battery percentage should be an issure with your custom rom, for the mounting problem... are you using the latest version of twrp? - and maybe you could try cwm ( i recommend that always ) - also, no there isn't a difference in flashing things on an lg device, as log it's an nexus one
nelomen said:
Let me start by saying that I am not new to flashing Roms on my devices, that being said I have never had an LG phone till now.
When I go in to Twrp and try to flash a new rom or even wipe it tells me it can't mount system. I've tried fixing permissions but nothing helped. I ended up having to use Nexus tool to restore phone to stock. (lost everything on phone)
I got the phone rooted and flashed carbon rom but decided that I wanted to flash a rom with 4.4.1 and same thing happened with phone not able to mount system. This time I was able to restore a Twrp backup I had and then flash the stock 4.4.1 rom available on this forum.
Is there something with this phone that is different then flashing on others? Can't seem to flash more then once without going back to stock? I have 2 nexus 7's 2012 & 2013 models and everything seems fine on these have flashed numerous Roms without a hitch.
I came from GS3 and have Asus prime, Motorola, HTC and just about every other manufacturers device in my house. Why is this one giving me so much issues.
Also battery won't charge past 77% now. Any ideas?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I would try: fastboot flash cache cache.img. use cache.img from the 4.4 factory image.
golem95 said:
the battery percentage should be an issure with your custom rom, for the mounting problem... are you using the latest version of twrp? - and maybe you could try cwm ( i recommend that always ) - also, no there isn't a difference in flashing things on an lg device, as log it's an nexus one
Click to expand...
Click to collapse
Thanks for the response. The battery issue has resolved itself by running battery down to 0%and recharging.
I will give CWM a try. Maybe.
I've noticed that before I started flashing Roms I ran stock go 2 weeks and was consistently getting almost 5 hours of screen time. Coming for the GS3 I was amazed but since I've started using custom rooms I'm barely getting 3.
Going to test this out some before I do too much more flashing.
Sent from my Nexus 5 using XDA Premium 4 mobile app
I've used cataclysm rom with franko kernel and have gotten 24 hours with over 7 screen on
nelomen said:
Thanks for the response. The battery issue has resolved itself by running battery down to 0%and recharging.
I will give CWM a try. Maybe.
I've noticed that before I started flashing Roms I ran stock go 2 weeks and was consistently getting almost 5 hours of screen time. Coming for the GS3 I was amazed but since I've started using custom rooms I'm barely getting 3.
Going to test this out some before I do too much more flashing.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
wow, 5hrs i get barely 3h +/-
golem95 said:
wow, 5hrs i get barely 3h +/-
Click to expand...
Click to collapse
Check it out. That was on stock in the first couple of days of getting the phone. But once I started flashing Roms it has only been about 3. Going to try stock for another while see if I can reproduce the amazing battery life I first had.
Sent from my Nexus 5 using XDA Premium 4 mobile app
Maybe u must change ur cwm
Sent from my GT-S5360 using xda app-developers app
nelomen said:
Check it out. That was on stock in the first couple of days of getting the phone. But once I started flashing Roms it has only been about 3. Going to try stock for another while see if I can reproduce the amazing battery life I first had.
(not sure if pics attached but they are of my 5hrs screen time)
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Sent from my Nexus 5 using XDA Premium 4 mobile app
nelomen said:
Let me start by saying that I am not new to flashing Roms on my devices, that being said I have never had an LG phone till now.
When I go in to Twrp and try to flash a new rom or even wipe it tells me it can't mount system. I've tried fixing permissions but nothing helped. I ended up having to use Nexus tool to restore phone to stock. (lost everything on phone)
I got the phone rooted and flashed carbon rom but decided that I wanted to flash a rom with 4.4.1 and same thing happened with phone not able to mount system. This time I was able to restore a Twrp backup I had and then flash the stock 4.4.1 rom available on this forum.
Is there something with this phone that is different then flashing on others? Can't seem to flash more then once without going back to stock? I have 2 nexus 7's 2012 & 2013 models and everything seems fine on these have flashed numerous Roms without a hitch.
I came from GS3 and have Asus prime, Motorola, HTC and just about every other manufacturers device in my house. Why is this one giving me so much issues.
Also battery won't charge past 77% now. Any ideas?
Sent from my Nexus 5 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
When your in TWRP and your trying to flash a ROM try restarting recovery by pressing reboot then reboot recovery then flash the ROM
Sent from my Nexus 5 using Tapatalk
OptimusVDarwin said:
When your in TWRP and your trying to flash a ROM try restarting recovery by pressing reboot then reboot recovery then flash the ROM
Sent from my Nexus 5 using Tapatalk
Click to expand...
Click to collapse
Thanks, I've never tried that but am willing to give it a shot after I finish my testing of battery life on stock compared to custom roms.
For some reason I am getting about 2 hours more screen time with stock then with custom rom.
Sent from my Nexus 5 using XDA Premium 4 mobile app