i got a very strange problem in my htc one x
everything was working fine and suddenly my phone was getting very hot (sometimes battery get hot sometimes cpu)
i was on slimkat rom
i thought re flashing will help as wiping dalvik cache didnt help.
i reflashed the same rom as a new one but the phone was still getting hot and was shutting down
i tried different kernel but same problem
then i tried aicp rom on slimkat's boot.img and without gapps it was working fine but without radio
then i thought it might be the gapps that is causing the problem but as soon as i flashed boot.img of aicp and booted up the same shutting down problem came
so i downgraded my recovery and tried to install viperx rom but in aroma as soon as installation goes ahead after formatting the phone reboots itself without completing installation.
so the conclusion is it is working fine with boot.img of non supported rom(as radio stays off)
so please someone help me what should i do ??????
spark2331995 said:
i got a very strange problem in my htc one x
everything was working fine and suddenly my phone was getting very hot (sometimes battery get hot sometimes cpu)
i was on slimkat rom
i thought re flashing will help as wiping dalvik cache didnt help.
i reflashed the same rom as a new one but the phone was still getting hot and was shutting down
i tried different kernel but same problem
then i tried aicp rom on slimkat's boot.img and without gapps it was working fine but without radio
then i thought it might be the gapps that is causing the problem but as soon as i flashed boot.img of aicp and booted up the same shutting down problem came
so i downgraded my recovery and tried to install viperx rom but in aroma as soon as installation goes ahead after formatting the phone reboots itself without completing installation.
so the conclusion is it is working fine with boot.img of non supported rom(as radio stays off)
so please someone help me what should i do ??????
Click to expand...
Click to collapse
Wipe everything in recovery except sd card and when you install viperx choice without wipe and don't forget to flash the boot.img from viperx rom
Thant said:
Wipe everything in recovery except sd card and when you install viperx choice without wipe and don't forget to flash the boot.img from viperx rom
Click to expand...
Click to collapse
i have philz recovery ...
i do clean to install new rom
wipe data factory reset
wipe cache
wipe dalvik cache
and by wipe everythingdo you to wipe the things under mounts and storage?
rca,rfs,devlog,data,boot???
i installed slimkat latest version with the boot.img provided in it and booted it up without flashing gapps its working fine but as soon as i install gapps and boot it up , after the optimizing app popup it shows shutting down
i have tried 2 gapps slimkat latest gapps and pico modular pa gapps
spark2331995 said:
i have philz recovery ...
i do clean to install new rom
wipe data factory reset
wipe cache
wipe dalvik cache
and by wipe everythingdo you to wipe the things under mounts and storage?
rca,rfs,devlog,data,boot???
i installed slimkat latest version with the boot.img provided in it and booted it up without flashing gapps its working fine but as soon as i install gapps and boot it up , after the optimizing app popup it shows shutting down
i have tried 2 gapps slimkat latest gapps and pico modular pa gapps
Click to expand...
Click to collapse
i downgraded my recovery to philz v5
successfully installed viperx
but it stays on htc boot screen(htc quietly brilliant screen) and before even starts it goes black(switch off).
update-
i did wipe data/factory reset and rebooted the phone it eventually started but for 2-3 seconds at the one time setup screen and again it showed htc screen and got powered off
spark2331995 said:
i downgraded my recovery to philz v5
successfully installed viperx
but it stays on htc boot screen(htc quietly brilliant screen) and before even starts it goes black(switch off).
update-
i did wipe data/factory reset and rebooted the phone it eventually started but for 2-3 seconds at the one time setup screen and again it showed htc screen and got powered off
Click to expand...
Click to collapse
Deleted
spark2331995 said:
i downgraded my recovery to philz v5
successfully installed viperx
but it stays on htc boot screen(htc quietly brilliant screen) and before even starts it goes black(switch off).
update-
i did wipe data/factory reset and rebooted the phone it eventually started but for 2-3 seconds at the one time setup screen and again it showed htc screen and got powered off
Click to expand...
Click to collapse
Try with phone connected to outlet charger and see if boot maybe faulty battery
khairulez said:
Flash boot.img via fastboot.
Click to expand...
Click to collapse
i have done that
Thant said:
Try with phone connected to outlet charger and see if boot maybe faulty battery
Click to expand...
Click to collapse
i had a backup of viperx 4.1.1 from previous month i restored it and rebooted the device first try had same problem
in second reboot with device connected to charger it booted up but wifi was not turning on and battery temp was around 37 c and cpu temp was 65 c which came down in some time to 45-47.
i have also tried that but no use and also phone works fine without gapps installed on aicp or slimkat rom
i have tried 2 gapps both not helping
i think maybe something in boot sector got corrupted?
i guess the problem exist when gapps is installed and wifi is on as i got to get the device on in only 2 conditons when gapps was not installed and wifi on and when wifi off and gapps installed
spark2331995 said:
i have done that
i have also tried that but no use and also phone works fine without gapps installed on aicp or slimkat rom
i have tried 2 gapps both not helping
i think maybe something in boot sector got corrupted?
Click to expand...
Click to collapse
On viperX rom you don't have gapps and you have this problem, or you make something wrong.
1. Flash the boot.img from rom archive
2. Install the rom via recovery TWRP 2.7.1 and after this install the gapps for the rom
3. reboot device
Wich SlimKat you try and with wich gapps post a link here
ARE YOUR bootloader IS UNLOCKED????
Thant said:
On viperX rom you don't have gapps and you have this problem, or you make something wrong.
1. Flash the boot.img from rom archive
2. Install the rom via recovery TWRP 2.7.1 and after this install the gapps for the rom
3. reboot device
Wich SlimKat you try and with wich gapps post a link here
ARE YOUR bootloader IS UNLOCKED????
Click to expand...
Click to collapse
yes bootloader is unlocked and i am using latest slimkat v8.0.4 from teemo and also i have tried v7.6 but same problem
and i have used slimkat latest mini gappsand pa pico modular gapps(24 mb)
spark2331995 said:
yes bootloader is unlocked and i am using latest slimkat v8.0.4 from teemo and also i have tried v7.6 but same problem
and i have used slimkat latest mini gappsand pa pico modular gapps(24 mb)
Click to expand...
Click to collapse
Now download this SLIMKAT 7.9 and this GAPPS and format system and data and dalvik and cache
First you must flash boot.img from rom archive second restart go in recovery install the rom and then gapps restart and report
Thant said:
Now download this SLIMKAT 7.9 and this GAPPS and format system and data and dalvik and cache
First you must flash boot.img from rom archive second restart go in recovery install the rom and then gapps restart and report
Click to expand...
Click to collapse
same problem no luck :'(
spark2331995 said:
same problem no luck :'(
Click to expand...
Click to collapse
And when you flash SlimKat and gapps are your recovery is TWRP.2.7.1 or you use Philz 5
Thant said:
And when you flash SlimKat and gapps are your recovery is TWRP.2.7.1 or you use Philz 5
Click to expand...
Click to collapse
philz 6
spark2331995 said:
philz 6
Click to expand...
Click to collapse
OK now we will try something else
OK now to be clear if you dont install gapps SlimKat work perfect but if you install gapps craches. Now please try install ARHD or Maximus take the boot.img from Maximus,zip paste it in your fastboot folder flash it then go to recovery and flash maximus.zip then restart the phone and report.
And please flash philz 5.15.9 when you flashing the MaximusHD
Don't install anythig else
i got a new data about my problem
i somehow managed to run slimkat with gapps and found out that at the time of boot and for 5 min the battery temperature is above 65c but it comes down to 45-50c and when connected to a charger it goes more down to 27-35c
i take it that is same in all roms for me so it may be that some service is spiking the battery temperature high at boot as without gapps the phone works just fine?
spark2331995 said:
i got a new data about my problem
i somehow managed to run slimkat with gapps and found out that at the time of boot and for 5 min the battery temperature is above 65c but it comes down to 45-50c and when connected to a charger it goes more down to 27-35c
i take it that is same in all roms for me so it may be that some service is spiking the battery temperature high at boot as without gapps the phone works just fine?
Click to expand...
Click to collapse
This is normal when you the phone boot to be hot for CPU and battery
Related
Hi,
I am on CM 10.2 nightly. Everytime I try to install an different ROM on CWM 6.0.27, eg. Android Revolution 22.0, the installation procedure goes fine. During Aroma installer I choose to wipe user data partition and so on. Then after reboot my phone stucks on "samsung galaxy note gt-n7100" screen. Afterwards I have to go back into recovery and have to recover my rom so the phone will boot again. Really strange. Any suggestions why my phone is behaving this way?
Regards, heinzelrumpel
heinzelrumpel said:
Hi,
I am on CM 10.2 nightly. Everytime I try to install an different ROM on CWM 6.0.27, eg. Android Revolution 22.0, the installation procedure goes fine. During Aroma installaer I choose to wipe user data partition and so on. Then after reboot my phone stucks on "samsung galaxy note gt-n7100" screen. Afterwards I have to go back into recovrey and have to recover my rom so the phone will boot again. Really strange. Any suggestions why my phone is beahving this way?
Regards, heinzelrumpel
Click to expand...
Click to collapse
Change the recovery, often Philz 5.15 works best with Aroma installer.
Androidwizzard said:
Change the recovery, often Philz 5.15 works best with Aroma installer.
Click to expand...
Click to collapse
Unfortunately this does not do the trick Still stuck after reboot.
I can't tell you why its happening, but what I've done in the past to get around the issue is to flash a stock rom with Odin, then flash a new recovery before going to another custom rom. If you worry about the Knox warranty bit being set you'll have to find an old 4.1 image somewhere to flash. Since I'm past warranty I don't care anymore.
Good luck!
Wipe data cache dalvik format system etc nstall the new rom reboot and after go again to recovery and factory reset it.
Sent from my GT-N7100 using Tapatalk
I just installed Phantom rom (wiped everything) but it's stuck on the Samsung logo, can't boot into recovery or download mode
:crying:
already waited like 10+ minutes still nothing
update : I got into recovery mode
can't I install phantom rom into a mj5 bootloader?
sinoka56 said:
I just installed Phantom rom (wiped everything) but it's stuck on the Samsung logo, can't boot into recovery or download mode
:crying:
already waited like 10+ minutes still nothing
update : I got into recovery mode
can't I install phantom rom into a mj5 bootloader?
Click to expand...
Click to collapse
Mj5 is fine for flashing any 4.3 or 4.4.2 rom just click on my signature and look for how to wipe your phone via philz follow those steps and flash phantom rom if still gives you issue then flash latest twrp you'll find the links for it in my signature as well and steps how to wipe via twrp good luck
Sent from my GT-N7100 using Tapatalk
I installed TWRP recovery but when I factory reset / wipe data, dalvik, data, system it doesn't format the system
You can try another recovery through odin, if it fails flash stock rom through odin. Make sure you flash one which is as least as new bootloader. Then start from square one.
Witch version of TWRP do you use ?
To do full wipe I use Zoot Wipe script, but be careful it remove everything :
http://forum.xda-developers.com/showthread.php?t=2121347
Hey guys. I have a problem installing any AOSP based roms after upgrading to stock KK.
Here's what i did previously:
1. Upgrade KK using flashtool CSE method
2. Root using towelroot (tried using framaroot before but it was failed)
3. unlock bootloader using freegee, mako unlock and install TWRP
4. flash twrp multirom
5. made a nandroid backup
6. wipe data, cache, etc
7. install carbon rom, pa gapps
8. reboot
now my device stuck on boot animation. i've waited for an hour, nothing happened.. I've tried carbon, omni, CM, 4.4.4 and 4.4.2 version, all failed. However, i was able to install artmod without problem.
i wonder what went wrong? is it something to do with partition? can anyone help me please?
Thanks.
grunch21 said:
Hey guys. I have a problem installing any AOSP based roms after upgrading to stock KK.
Here's what i did previously:
1. Upgrade KK using flashtool CSE method
2. Root using towelroot (tried using framaroot before but it was failed)
3. unlock bootloader using freegee, mako unlock and install TWRP
4. flash twrp multirom
5. made a nandroid backup
6. wipe data, cache, etc
7. install carbon rom, pa gapps
8. reboot
now my device stuck on boot animation. i've waited for an hour, nothing happened.. I've tried carbon, omni, CM, 4.4.4 and 4.4.2 version, all failed. However, i was able to install artmod without problem.
i wonder what went wrong? is it something to do with partition? can anyone help me please?
Thanks.
Click to expand...
Click to collapse
Boot into Recovery > Factory Reset > Wipe Cache > Wipe Dalvik > Flash Rom > Flash Gapps > Reboot System
erkasmoter said:
Boot into Recovery > Factory Reset > Wipe Cache > Wipe Dalvik > Flash Rom > Flash Gapps > Reboot System
Click to expand...
Click to collapse
Well, i think i know the standard procedure, having flashed roms countless times before. But thanks anyway.
Just an update, i tried to flash gproj rom. It was successfully installed, but i got no data and wifi working. So probably it's modem problem. Hopefully someone can help me here..
Just try with a different recovery, like Philz touch.
nlooooo said:
Just try with a different recovery, like Philz touch.
Click to expand...
Click to collapse
I've tried that too. Phillz's, CWM, all don't work. Still stuck on boot ani.
grunch21 said:
I've tried that too. Phillz's, CWM, all don't work. Still stuck on boot ani.
Click to expand...
Click to collapse
That happens to me too
In my case, GPROJ works fine but GEEB get stuck at the logo only. Maybe you are only using GEEB ROM, or vice versa.
For example SLIM LP v0.6 uses GPROJ and v0.7 uses GEEB. v0.6 works fine for me and v0.7 doesn't work. Same with BLISSPOP v3.4(gproj) and v4(geeb).
I wonder if there's a way to use GEEB.
I have a E970.
So i recently installed TWRP version 3.0.0-0 and i wan to get out of it but when i reboot it it jus goes back to TWRP instead of booting into my device if you know how to fix it please help
It seems that you have uninstalled your rom.
how did you flash twrp and what's your rom?
darknessd31 said:
It seems that you have uninstalled your rom.
how did you flash twrp and what's your rom?
Click to expand...
Click to collapse
I Used Flasify to get TWRP and i was trying to get Cyanegen Mod
did you wipe anything?
flash with Odin your samsung firmware stock.
if you want cm13 download it from their website
put it in your memory
go to twrp (it is better to install it again with odin )
wipe system,cache,data
install cm13 and gapps
have fun
**becareful you should download your device specefic rom
darknessd31 said:
if you want cm13 download it from their website
put it in your memory
go to twrp (it is better to install it again with odin )
wipe system,cache,data
install cm13 and gapps
have fun
**becareful you should download your device specefic rom
Click to expand...
Click to collapse
I reinstalled the rom so every thing is fine
darknessd31 said:
did you wipe anything?
Click to expand...
Click to collapse
No But i reflashed the rom and everything in fine now
I'm having issues with LineageOS based roms. Basically, ever since 4.1.0 was released, I haven't been able to boot anything other than OxygenOS.
The first time I flashed the 4.1.0 firmware, my OnePlus 3 bricked. I then used the unbrick tool to fix it. I then tried again, by flashing the 4.1.0 firmware, then flashing the latest LineageOS "lineage-14.1-20170316-nightly-oneplus3-signed.zip". Upon reboot, the phone stays stuck at the lineageos boot animation. I can't get any logcats (adb logcat doesn't seem to work).
Things I've tried so far:
- Using TWRP 3.0.4-1
- Using TWRP 3.1.0-0
- Dirty flash
- Clean flash
- Data as both f2fs and ext4, neither works
- Tried using TWRP's "Fix Contents"
- Tried using TWRP's filesystem repair, no problems with the filesystem
I'm at a loss, no idea what to do. I really want to get back to LineageOS, but ever since that original brick, the phone hasn't been able to boot anything other than the stock ROM.
do you try download again that rom?
i had some problems with AICP, flashing last firmware+modem was solved
you can try using other base, like 4.02, or freedomOS OB12
just ideas, I don't know what's the problem :/
bro i flashed the 316 build on oos 4.1 firmware and modem no issue here all works fine still using it with blue spark kernal you must have done something wrong
vasu1312 said:
bro i flashed the 316 build on oos 4.1 firmware and modem no issue here all works fine still using it with blue spark kernal you must have done something wrong
Click to expand...
Click to collapse
I don't think I screwed up anything. I had flashed multiple roms before. (LineageOS, ResurrectionRemix, AICP, FreedomOS...)
All of them worked, up until recently. When the 4.1.0 update came out, LineageOS Roms stopped booting. OxygenOS ROMS still work fine though. Flashing the OB12 firmware doesn't help.
This is the first time this has happened, I have no idea why its happening.
Do you flash SuperSU, without SuperSU mine boots fine. Without i m stuck in boot
Tried flashing SuperSU, but nothing has changed. Android still won't boot up if it is a LineageOS based ROM
go to stock recovery (oxygen os stock one)
then flash 4.1.0 with that recovery
then boot
now replace the recovery with twrp 3.1.0
once done dont boot the rom n go to recovery and flash su
now boot rom
now again go to twrp n wipe system, data, cache, dalvik
and then flash lineage lastest build.. it will work
if not lemme know i will help you further
indroider said:
go to stock recovery (oxygen os stock one)
then flash 4.1.0 with that recovery
then boot
now replace the recovery with twrp 3.1.0
once done dont boot the rom n go to recovery and flash su
now boot rom
now again go to twrp n wipe system, data, cache, dalvik
and then flash lineage lastest build.. it will work
if not lemme know i will help you further
Click to expand...
Click to collapse
Just did it. It didn't work, the phone gets stuck in the LineageOS Boot screen
Now, not even Android 6.0 ROMS will boot. I think some partitions are corrupted, but I'm unable to wipe them in fastboot mode.
Edit: So, finally, after 3 days, I was able to get in contact with OnePlus. OnePlus fixed the problem with the Qualcomm Tools, not entirely sure what they did, but it fixed the problem. I'm finally able to boot LineageOS!!!!
AquaBytez said:
Just did it. It didn't work, the phone gets stuck in the LineageOS Boot screen
Click to expand...
Click to collapse
how much time do you wait because first boot does take 5 or more minutes
indroider said:
how much time do you wait because first boot does take 5 or more minutes
Click to expand...
Click to collapse
OnePlus said that the persist partition had been corrupted. So they re-flashed it and the phone started booting custom ROMS again. I guess the ROMS weren't booting because they got stuck waiting on the sensors. (To be completely honest, I never noticed that the sensors were broken. Since the only one I frequently use is the Gyroscope and that one was working fine)
AquaBytez said:
OnePlus said that the persist partition had been corrupted. So they re-flashed it and the phone started booting custom ROMS again. I guess the ROMS weren't booting because they got stuck waiting on the sensors. (To be completely honest, I never noticed that the sensors were broken. Since the only one I frequently use is the Gyroscope and that one was working fine)
Click to expand...
Click to collapse
perfect... that is what i was trying ro instruct you reflasing the stock but somehow ,,, it was not able to be done throught stock oxygen recovery... from ur end
nevertheless happy ur device is working fine now