So I have been running Slimbean 4.3 beta for the past couple days, it's been running pretty smooth except that when I accidentally let the battery die when it boots up the first time after a charge it locks up at boot at "Android is upgrading" and so I have decided to flash a couple custom kernels to see if it will help solve this problem. Although I heard mike is working on a solution for this? Hopefully haha..anyways. This is the first rom I have tried flashing a different kernel on this device. Anyways the first kernel I tried flashing was jriors Torch and it seemed to have booted up fine after the reboot from recovery but the boot animation was orange and after a while it locks up with a grey bar over it, with "Android is upgrading:" written on it in pink. I then proceeded to recovery clean wiped reflashed slimbean and tried flashing the one that came out last night I think...aznrice's evita boosted7 and I got the same result. So then I decided to try carbon and both kernels worked perfectly with it. So is this just a Slimbean problem? or am I missing something? I'm S-off, Hboot 2.14, TWRP 2.6.3
Sorry for the bulky post first time poster long,long,long time reader haha
Thanks
Those kernels aren't compatible with Slimbean, there currently aren't any custom kernels that are compatible with it.
Sent from my Evita
Related
Hi all I decided to try and run a custom ics build a couple days ago everything went smoothly, I got the lastest AOKP build running with tastymeh kernel. Well tonight I disabled the boot animations and it seems as though I'm stuck bootlooping into the latest cwm(touch). I've tried reflashing the rom/kernal/wipe dalvik/etc to no avail. And my Nandroid backup isn't showing up to make matters worse. I can't even power down my device it just keeps bootlooping. I was wander what the best method to return to complete stock rom? Thanks everyone
Brand New said:
Hi all I decided to try and run a custom ics build a couple days ago everything went smoothly, I got the lastest AOKP build running with tastymeh kernel. Well tonight I disabled the boot animations and it seems as though I'm stuck bootlooping into the latest cwm(touch). I've tried reflashing the rom/kernal/wipe dalvik/etc to no avail. And my Nandroid backup isn't showing up to make matters worse. I can't even power down my device it just keeps bootlooping. I was wander what the best method to return to complete stock rom? Thanks everyone
Click to expand...
Click to collapse
Go here for instructions on how to fix
http://forum.xda-developers.com/showthread.php?t=1530337
Okay.. So I own a sprint htc evo 4g lte, the other day I was bored and unlocked it(Still S-On). I flashed an upgraded stock mod that was supposed to have a few more options and what not and that worked great. I wanted something different and I heard that AOiKP was a good rom to try so the next day I flashed that. After flashing it got stuck on the boot animation, I read that it could be the rom so I downloaded Komodo rom for S-On. This is where my problems started, After installing Komodo I got AOKP to work but this was after fighting the looping bootups and clearing my caches in the recovery to magically get it to work. I tried installing CM10 with a Full Wipe and it seems that Komodo is still there. CM10 eventually booted by doing the same process as before but it was not a fun thing to do and I have to do it again if I reboot. I just now installed team venoms viper rom and it looked like it was going to work but then started doing a boot loop all the way from power off to the end of the boot animation. ANY HELP WOULD BE AMAZING! Thank you!!
AND sorry I'm such a noob
First of all, thanks for all the hard work you guys do.
I have a problem with my tf101 running a Cyanomod. I tried searching on the forum, but there are so many keywords i don't even know how to input a proper query, so sorry if the problem has already been covered.
My tf101 was working just fine, i mounted a new rom (a nightly based on Jelly Bean 4.1.2), everything was nice and smooth, until one day i forgot to plug the charger to my tablet. The battery ran down to 0%, the first time it ever happened. Since then, everytime i try to power my tablet it gets stuck on the cyanogenmod rotating logo. I have to force reboot it several times before it starts working again, even if the battery id completely charged.
The first time it happened i tried wiping all data as well as the cache, i also tried reinstalling the rom but the only thing that seemed to work was reverting to a stable rom and then installing the nightly. Until the battery accident, everything was perfect.
Why is this happening? Is there a way to fix it?
You have said:
Code:
i also tried reinstalling the rom but the only thing that seemed to work was reverting to a stable rom and then installing the nightly.
So does you tablet boot into Android or not?
Because you have TF101 not G or Slider, you can NVflash the tablet to stock and try everything from beginning (root, custom recovery...).
Link to NVflash method
Sincerely,
Žiga
ZigaG said:
You have said:
Code:
i also tried reinstalling the rom but the only thing that seemed to work was reverting to a stable rom and then installing the nightly.
So does you tablet boot into Android or not?
Because you have TF101 not G or Slider, you can NVflash the tablet to stock and try everything from beginning (root, custom recovery...).
Link to NVflash method
Sincerely,
Žiga
Click to expand...
Click to collapse
Yeah it does, but only after countless attempts. If i do nothing and let it go, it gets stuck on the cyanogen logo forever.
I will try your solution and let you know, thanks.
Which recovery are you using ?
TWRP is the one to use, CWM has issues
I've been using CM10.1 on this phone pretty much since it's been available and updating nightlies about once a week usually. Typically I use Ktoonsez kernel and also update this regularly. Also I am on the MF1 firmware. So, I'm pretty comfortable with the update process and have done it many times.
The other day I attempted to update to CM10.1 7/8 nightly while also installing a kernel I've never tried before called 'Sultan-kernel-Venturi-r5-USA'. Also completing the update process I rebooted and the phone would not move past the CM loading animation splash screen. After about 10 minutes of this I pulled the battery and rebooted, hoping it was just a hiccup but the same thing happened. After dirty installing various CM10.1 nightly and release versions with various combos of no custom kernel and the KT kernel but nothing would fix the boot issue.
I then attempted to wipe and ended up eventually wiping everything on the phone except the external SD card. Still, I could not get the phone to move past the CM splash screen. I then tried a few other AOSP ROMs with the same issue presenting.
Eventually I installed a TW based ROM and was able to get the phone to boot and and able to at least use my phone now. I've tried a couple time since to do a nandroid backup then try installing CM10.1 again and still nothing changes. I can restore the backup and the TW ROM works fine again.
Any ideas on what could have happened to cause this or anything else I can try to get AOSP ROMs working on my phone again?
I would say Odin back to 4.0.4 stock, do the OTA's, reroot with the one click root in the developer section, and it should work.
Sent from my SCH-I535 using xda app-developers app
I did get this figured out. Somehow my EFS partition was wiped. TW based ROMs would actually boot but displayed a 'Factory Mode' warning on startup. AOSP ROMs would not finish booting at all. After restoring EFS from backup everything started working again.
Okay so i have TWRP 3.0.2.0 modded for multirom and multirom installed on my phone and it was working okay for a long time now all of a sudden my phone randomly reboots and ALL 7 roms in mutli rom boot loop when you try to boot them. so i erased all of them and reflashed the rom, the second i flash anything other than the rom, kernel,mods, stupid files, literally ANYTHING but the rom it bootloops again and it never did this before all of these files worked together before, so i rewrote the twrp and mutlirom and all, figuring maybe that would help, it did not. so i thought okay, fine i will do an RUU and go to stock. it says the firmware is mismatched? so because of S-ON i cant restore to stock now. ( same one ive been using to RUU it for over a year anytime necessary )
literally everything i try i just end up with Bootloops. if i flash ONLY the rom it boots fine but the kernels tend to kill the battery really bad so i usually flashed a custom one and i just dont understand how the same kernel and files ive been using for like the last 8 month now are bootlooping every time. i tried looking for new roms too, nothing works. i also tried plain stock TWRP and no mutlirom, same results, bootloops if anything more than the plain rom is flashed.
also my battery seems to be dying like a rock now, unplugged it and within like 10 min i had lost 18%
universelove said:
Okay so i have TWRP 3.0.2.0 modded for multirom and multirom installed on my phone and it was working okay for a long time now all of a sudden my phone randomly reboots and ALL 7 roms in mutli rom boot loop when you try to boot them. so i erased all of them and reflashed the rom, the second i flash anything other than the rom, kernel,mods, stupid files, literally ANYTHING but the rom it bootloops again and it never did this before all of these files worked together before, so i rewrote the twrp and mutlirom and all, figuring maybe that would help, it did not. so i thought okay, fine i will do an RUU and go to stock. it says the firmware is mismatched? so because of S-ON i cant restore to stock now. ( same one ive been using to RUU it for over a year anytime necessary )
literally everything i try i just end up with Bootloops. if i flash ONLY the rom it boots fine but the kernels tend to kill the battery really bad so i usually flashed a custom one and i just dont understand how the same kernel and files ive been using for like the last 8 month now are bootlooping every time. i tried looking for new roms too, nothing works. i also tried plain stock TWRP and no mutlirom, same results, bootloops if anything more than the plain rom is flashed.
also my battery seems to be dying like a rock now, unplugged it and within like 10 min i had lost 18%
Click to expand...
Click to collapse
Try a different twrp version worked for me awhile ago when I had it
Thank you for the suggestion but as it says above i have tried that. this phone will not let me restore or use anything without google play now so im probably just going to get rid of it or smash it because ive been trying for weeks and NOTHING works.
only android 7+ roms boot, cant RUU, no home button menus, notifications or anything work without google installed so my phone has some weird new firmware on it and is forcing me to use the most up to date android/google play or it just wont work at all.
Update: charger port just quit working, probably burned up from getting so hot with all the battery over use, phone is officially dead now.