will the new sense roms ever work on our phones?? - HTC Pico (Explorer)

fist we were getting it... after build 3 of Derefas random reboots ?? is there any developer working to solve this issue.. some people are saying its sd classs problem.. i don't know what the problem is but please someone make it work

talhadabest said:
fist we were getting it... after build 3 of Derefas random reboots ?? is there any developer working to solve this issue.. some people are saying its sd classs problem.. i don't know what the problem is but please someone make it work
Click to expand...
Click to collapse
Its been already solved in build # 6..I haven't tested it but been on build #4 for a month..and there were no random reboots:silly::silly:
If you are still getting reboots...try changing your recovery and must follow the installation steps provided.. precisely..:fingers-crossed::fingers-crossed:

its also happening in build 6.. It boots after you pull the ring to unlock.. and we have tried every recovery there is to use on Explorer

talhadabest said:
its also happening in build 6.. It boots after you pull the ring to unlock.. and we have tried every recovery there is to use on Explorer
Click to expand...
Click to collapse
I flashed JaggyDzire v1.2 yesterday, I was also facing bootloops but usd95 helped me with exact steps and it installed flawlessly..:good:
Its not problem of ROM, its just the steps to be followed for flashing..
JaggyDzire is based on derefas sense 4 build #4..If you want to flash this rom..check this thread by me...
http://forum.xda-developers.com/showthread.php?t=2131690

talhadabest said:
its also happening in build 6.. It boots after you pull the ring to unlock.. and we have tried every recovery there is to use on Explorer
Click to expand...
Click to collapse
I tried this way:
Currently on TWRP
Boot to Recovery
Mount System, Data, Cache, SD, SDExt(I'm ust Sd-ext with ext2 file system on class4 8GB)
Wipe Dalvik-cache
Wipe data/Factory reset
Wipe System
Mount sd, sd-ext, cache (This step is now not necessary as build#5, #6 mount themselves)
Then finally flash sense 4
Reboot n wait for it boot fully and then reboot after few mins.
This way I have had no random reboots except on build#4
Now on build6, its fluidic.

thanks bros.. I installed flyrom v2 this way and it was rebooting after 15 mins.. now I'm installing JaggyDzire v2 I hope it works

didn't work of me still rebooting

talhadabest said:
didn't work of me still rebooting
Click to expand...
Click to collapse
Which ROM?

JaggyDzire 1.2 and Build 5 and 6 of derefas.. flyrom v2 is rebooting less

talhadabest said:
JaggyDzire 1.2 and Build 5 and 6 of derefas.. flyrom v2 is rebooting less
Click to expand...
Click to collapse
Agreed... FlyROM v2 has not given me reboot since morning... Initially it gave reboots for about 20 mins... But now it running like butter..

....
i've been running flyrom v1 and haven't had much problems with it...gonna try build 6 by derefas soon

Related

Device rebooting and entering recovery!(SOLVED)

HI guys!I just installed [ROM][22 OCT 11] RCMix3d Runnymede S v3.1 [Runnymede XL sense 3.5 Android 2.3.5][OC Kernel 2GHz] on my desire s.I did a full wipe,i have a ext3 partition.After rebooting everything went fine,no problems.After i configured my google account and installed some apps,i rebooted the phone...........and now remains on HTC boot screen and after a few seconds it reboots and enters recovery mode........Is my desire BRICKED?I tried installing another ROM with no results....It always reboots and enters recovery mode.
P.S. I forgot to mention that the device is rooted,s off by revolutionary.Also i flashed a new radio.
format all partitions to ext4 and flash again
tnx for the fast reply but how i can format all partitions to ext4?
sorry for the noob question....
via recovery.use wipe and format option
I dont have that option.........maybe i need the 4ext recovery?i have clockworkmod
Costinutz32 said:
I dont have that option.........maybe i need the 4ext recovery?i m have clockworkmod
Click to expand...
Click to collapse
yes use 4ext is much much better
thank you!
I pressed thank you button but nothing happens??!!!??
your thanks meter remains untouched...
nah..dont worry about that.glad u resolved ur issue.
cheers.

cm-11-20140227-NIGHTLY-falcon --- Bootloop issue after OTA-Update

Hey guys,
today i have made a OTA-Update over the Cyanogenmod-Updater (CWM-Version: 6.0.4.6) from Version cm-11-20140220-NIGHTLY-falcon to cm-11-20140227-NIGHTLY-falcon and everything went fine.
But after the first reboot i have got a bootloop issue. The only thing you can do is, to wait about 4-5 minutes; then the system starts normally und you can enter your pin-code.
Another interesting thing was that after the update my "es file explorer" get warning -> something like missing file and was deinstalled by itself without asking me.
Now i installed the es file explorer again and get the same warning again.
Hope you can help me.
Did you try to wipe cache and dalvic cache in CWM?
Dizzyrul3z said:
Did you try to wipe cache and dalvic cache in CWM?
Click to expand...
Click to collapse
No. I just make a dirty flash over the Cyanogemod-Updater under Settings.
So, i have made now a wipe cache and dalvik cache in CWM but this does not solve the bootloop issue and the strange deinstallation of my apps.
Whenever i start the Phone with the power button it tooks about 5 minutes to enter my pin code.
After each system start one app is in random order deinstalled by itself. This time my es file explorer is ok but gmail was deinstalled.
I have had never such issues on the cm-11-20140220-NIGHTLY-falcon.
The cm-11-20140227-NIGHTLY-falcon seems to be buggy and should be removed from the official OTA-Update.
Volkan66 said:
So, i have made now a wipe cache and dalvik cache in CWM but this does not solve the bootloop issue and the strange deinstallation of my apps.
Whenever i start the Phone with the power button it tooks about 5 minutes to enter my pin code.
After each system start one app is in random order deinstalled by itself. This time my es file explorer is ok but gmail was deinstalled.
I have had never such issues on the cm-11-20140220-NIGHTLY-falcon.
The cm-11-20140227-NIGHTLY-falcon seems to be buggy and should be removed from the official OTA-Update.
Click to expand...
Click to collapse
Hi, I have the same situation as you. I flashed from 24th to 27th, everything was OK. After that I flashed pink kernel from 21th.
After that flashing I had over and over bootloops. Wipe/factory reset - nothing changes. I formated internal card fully and now I would like to flash I don't know stock or maybe still CM but I'm sure not 27th release.
Volkan66 said:
Hey guys,
today i have made a OTA-Update over the Cyanogenmod-Updater (CWM-Version: 6.0.4.6) from Version cm-11-20140220-NIGHTLY-falcon to cm-11-20140227-NIGHTLY-falcon and everything went fine.
But after the first reboot i have got a bootloop issue. The only thing you can do is, to wait about 4-5 minutes; then the system starts normally und you can enter your pin-code.
Another interesting thing was that after the update my "es file explorer" get warning -> something like missing file and was deinstalled by itself without asking me.
Now i installed the es file explorer again and get the same warning again.
Hope you can help me.
Click to expand...
Click to collapse
What recovery do you have installed?
january waower
kieranc said:
What recovery do you have installed?
Click to expand...
Click to collapse
I have installed ClockworkMod-Recovery (CWM): cwm-6.0.4.6
I don't have any problems with the recovery but with the Nightly Update from 27th February.
I can't understand how the cm-11-20140227-NIGHTLY-falcon can get official, when a lots of people have the same problem: bootloops.
=dgim= said:
Hi, I have the same situation as you. I flashed from 24th to 27th, everything was OK. After that I flashed pink kernel from 21th.
After that flashing I had over and over bootloops. Wipe/factory reset - nothing changes. I formated internal card fully and now I would like to flash I don't know stock or maybe still CM but I'm sure not 27th release.
Click to expand...
Click to collapse
I totally agree with you. I won't do a full format of the internal card. Just waiting for the next Nightly in the hope that dhacker improves this issue.
Do you have also problems with GMAIL. After each restart GMAIL is lost. I must install it each time new.
I had the same problem and haven't fixed it yet. I had CWM 6.0.4.5 installed when CM updater tried to install 0227 and I'm wondering if that could be the problem as dhacker29 recommended an update to the CWM he specified to avoid "accidental wiping of critical partitions."
I dunno, but so far it looks like I'm going to have to restore stock firmware and start from scratch....
kieranc said:
I had the same problem and haven't fixed it yet. I had CWM 6.0.4.5 installed when CM updater tried to install 0227 and I'm wondering if that could be the problem as dhacker29 recommended an update to the CWM he specified to avoid "accidental wiping of critical partitions."
I dunno, but so far it looks like I'm going to have to restore stock firmware and start from scratch....
Click to expand...
Click to collapse
So, I installed by mfastboot for now the newest stock rom 4.4.2 DE, updated to the latest release and rooted.
Maybe I'll flash also kernel to faux's release. Very strange issue. I flashed CM several times and today's issue was the first time.
=dgim= said:
Hi, I have the same situation as you. I flashed from 24th to 27th, everything was OK. After that I flashed pink kernel from 21th.
After that flashing I had over and over bootloops. Wipe/factory reset - nothing changes. I formated internal card fully and now I would like to flash I don't know stock or maybe still CM but I'm sure not 27th release.
Click to expand...
Click to collapse
I've just wiped /data/media ("sdcard") and have successfully installed and booted feb 27th build. Strange problem but that looks like the solution....
I was at the 0224 build and flawlessly updated to the 0227 build... no issue so far. i am using twrp...
Hey guys,
i have flashed the newest Nightly cm-11-20140228-NIGHTLY-falcon.zip today and everything was solved. No bootloops or lost of apps.
With pink kernel the system rocks. This is awesome. Thanks to dhacker29, pinkflozd, faux123, razrqcom-dev-team :good::good::good:
Im Using Since last two nightlys no Pink Kernel anymore. The battery life under Stock cm Rocks now. Bat i have Crap Sounds in Calls Since then..
Android-CM11
hydromän said:
Im Using Since last two nightlys no Pink Kernel anymore. The battery life under Stock cm Rocks now. Bat i have Crap Sounds in Calls Since then..
Android-CM11
Click to expand...
Click to collapse
I can confirm your sound problem.
I am using the nightly version 0228 and pink kernel 0228 and would recommend you to use the pink kernel because you will feel the boost in performance.
Yes the battery will drain a little bit more than on stock-cm but it is worth it. I can use my phone with pink kernel two days long without charging it.
So I will try Again Pink Kernel =).. I hope the Sound in Call Problem get fixed soon
Android-CM11
I Flashed last Pink Kernel, youre right, really smoother than stock cm Kernel :thumbup:
Android-CM11
hydromän said:
I Flashed last Pink Kernel, youre right, really smoother than stock cm Kernel :thumbup:
Android-CM11
Click to expand...
Click to collapse
Yeah this version of pink kernel is great. I hope this kernel will leave soon the beta-stadium and will get official.
0303-NIGHTLY sometimes still has the problem
Sent from my Moto G using xda app-developers app
tohigh said:
0303-NIGHTLY sometimes still has the problem
Sent from my Moto G using xda app-developers app
Click to expand...
Click to collapse
Please flash the TWRP 2.6.3.3 recovery first then flash the newest nightly cm-11-20140304-NIGHTLY-falcon.zip .
I am using 0303-NIGHTLY with TWRP 2.6.3.3 and don't have such issues like bootloop again.
But it is very important to flash the recovery first, then flash cm-11-20140304-NIGHTLY-falcon.zip with Cyanogenmod-Updater under settings.
If you do otherwise flash cm first you will encounter the same problem.

[Q] First boot taking forever .

Hi ,guys .
So my problem is the first boot (on my p3110 )takes an eternity , whatever I'm trying to flash it wouldn't succesfully have the first boot .
I've tried omni,slimkat and CM but nothing works .
Dumb I was ,in my blind tries, I've deleted my backups and now the only place i can flash is my microSD card.
Help please , I'm really stuck . :crying:
TheHelplessGuy said:
Hi ,guys .
So my problem is the first boot (on my p3110 )takes an eternity , whatever I'm trying to flash it wouldn't succesfully have the first boot .
I've tried omni,slimkat and CM but nothing works .
Dumb I was ,in my blind tries, I've deleted my backups and now the only place i can flash is my microSD card.
Help please , I'm really stuck . :crying:
Click to expand...
Click to collapse
The first boot always takes longer as it is setting up, but no longer than ~5 minutes.
Anyway... If you've waited and it is boot looping, try these steps:
Make sure your recovery is up to date.
Wipe system, data, cache, and dalvik cache.
Flash ROM, gapps, and any addons
Wipe cache and dalvik
Reboot. After first reboot is complete and on setup screen, wait 5 minutes and reboot into recovery.
Wipe cache and dalvik again. Reboot
This reboot could also take ~5 minutes, but the others shouldn't as long as you don't wipe cache and dalvik.
You should see an "Android is Upgrading" screen. After this is done, complete setup and you should be good to go.
Sent from my SGH-T989
The same
jrc2 said:
The first boot always takes longer as it is setting up, but no longer than ~5 minutes.
Anyway... If you've waited and it is boot looping, try these steps:
Make sure your recovery is up to date.
Wipe system, data, cache, and dalvik cache.
Flash ROM, gapps, and any addons
Wipe cache and dalvik
Reboot. After first reboot is complete and on setup screen, wait 5 minutes and reboot into recovery.
Wipe cache and dalvik again. Reboot
This reboot could also take ~5 minutes, but the others shouldn't as long as you don't wipe cache and dalvik.
You should see an "Android is Upgrading" screen. After this is done, complete setup and you should be good to go.
Sent from my SGH-T989
Click to expand...
Click to collapse
The same loading image .(You know ,when you first boot something it appears the custom flash's logo) . what can i do ?
TheHelplessGuy said:
The same loading image .(You know ,when you first boot something it appears the custom flash's logo) . what can i do ?
Click to expand...
Click to collapse
How long have you tried waiting? Which room door you flash on which device?
Sent from my SGH-T989
jrc2 said:
How long have you tried waiting? Which room door you flash on which device?
Sent from my SGH-T989
Click to expand...
Click to collapse
I've waited more than usual 5-10 mins ,even 6 hours ,but nothing, ,I'm curently trying to flash slimkat 4.4.4 but i've tried omni ,CM all kitkat .
What is your advice ?
TheHelplessGuy said:
I've waited more than usual 5-10 mins ,even 6 hours ,but nothing, ,I'm curently trying to flash slimkat 4.4.4 but i've tried omni ,CM all kitkat .
What is your advice ?
Click to expand...
Click to collapse
What version of unroofed TouchWiz were you running before rooting and flashing?
Sent from my SGH-T989
jrc2 said:
What version of unroofed TouchWiz were you running before rooting and flashing?
Sent from my SGH-T989
Click to expand...
Click to collapse
The one with Android 4.1 my guess is Nature UX
TheHelplessGuy said:
The one with Android 4.1 my guess is Nature UX
Click to expand...
Click to collapse
Then idk what the problem is. You were on jelly bean already so that isn't a problem.
Sent from my SGH-T989
jrc2 said:
Then idk what the problem is. You were on jelly bean already so that isn't a problem.
Sent from my SGH-T989
Click to expand...
Click to collapse
What do you suggest ?
TheHelplessGuy said:
What do you suggest ?
Click to expand...
Click to collapse
I don't know, sadly. Maybe someone else will know and we'll both learn something.
Sent from my SGH-T989
Back to stock rom for now, prepare (charge until full).
Re-root, then reboot to recovery to try again flashing the rom.
Always format /system, /cache, /data/media first when installing different roms. Good luck
150208 said:
Back to stock rom for now, prepare (charge until full).
Re-root, then reboot to recovery to try again flashing the rom.
Always format /system, /cache, /data/media first when installing different roms. Good luck
Click to expand...
Click to collapse
I did exactly as you said but nothing happened .
1. It's a problem that i install zips from my external storage ?
2.Do you know where i can find a nandroid backup to download ?
3.What do you suggest for my issue ?
TheHelplessGuy said:
I did exactly as you said but nothing happened .
1. It's a problem that i install zips from my external storage ?
2.Do you know where i can find a nandroid backup to download ?
3.What do you suggest for my issue ?
Click to expand...
Click to collapse
Stock rom is working fine? Is root working on stock?
Did you get any errors while flashing costom roms?
I remember a folk here got a same problem as you, and i think it's not resolved yet..
Maybe you and him have a "special" devices.
Don't worry, it's not a problem with your ext-sd because i use it all the time. and if it was ext-sd problem, you'll get an error while flashing.
I suggest messages devs in developement section, maybe they can figure out what is wrong.
And of course i think it's not safe to restore others nandroid backup, so don't mind find it.
God speed, wish I can help you more :angel:
150208 said:
Stock rom is working fine? Is root working on stock?
Did you get any errors while flashing costom roms?
I remember a folk here got a same problem as you, and i think it's not resolved yet..
Maybe you and him have a "special" devices.
Don't worry, it's not a problem with your ext-sd because i use it all the time. and if it was ext-sd problem, you'll get an error while flashing.
I suggest messages devs in developement section, maybe they can figure out what is wrong.
And of course i think it's not safe to restore others nandroid backup, so don't mind find it.
God speed, wish I can help you more :angel:
Click to expand...
Click to collapse
Sadly my stock rom is gone.
So yesterday when I've rerooted whit your link I've received two errors :
- SOKP and when I've flash it something like poped up : E:Cannot write to sd card clockworkmod recovery etc.
- CM 11 :
Root Access Possibly Lost Fix?
THIS CANNOT BE UNDONE
1. YES fix root (/system/xbin/su)
2. NO do not fix
TheHelplessGuy said:
Sadly my stock rom is gone.
So yesterday when I've rerooted whit your link I've received two errors :
- SOKP and when I've flash it something like poped up : E:Cannot write to sd card clockworkmod recovery etc.
- CM 11 :
Root Access Possibly Lost Fix?
THIS CANNOT BE UNDONE
1. YES fix root (/system/xbin/su)
2. NO do not fix
Click to expand...
Click to collapse
Like I said earlier, you should have flashing stock rom first to remove root via odin/hemidall.. you can find it at sammobile,com
then re-root with link i gave earlier again via odin/hemidall, and format in recovery like i said earlier. no wonder you still fail..
you should have philz touch recovery instead cwm if you succeed.
150208 said:
Like I said earlier, you should have flashing stock rom first to remove root via odin/hemidall.. you can find it at sammobile,com
then re-root with link i gave earlier again via odin/hemidall, and format in recovery like i said earlier. no wonder you still fail..
you should have philz touch recovery instead cwm if you succeed.
Click to expand...
Click to collapse
re-rooted as you said still the same loading screen , you can give me a link to the part of the forum where I can speak with developers as you said few comments ago

[Q] [HELP] Stuck at HTC Logo and Recovery

So, I haven't been using my pico recently..used it about 6 months ago and it has been unused ever since..
Today, I finally picked it up and tried to install MIUI V4. I updated TWRP to 2.7 and it was updated.. Deleted the previous rom and installed the MIUI zip.. When I restarted even the MIUI bootanimation did not show up, only the HTC Logo showed up, and the phone rebooted into recovery. .
So, is it bricked ? I tried installing CM9 but same problem..Any help will be appreciated
TAOprajjwal said:
So, I haven't been using my pico recently..used it about 6 months ago and it has been unused ever since..
Today, I finally picked it up and tried to install MIUI V4. I updated TWRP to 2.7 and it was updated.. Deleted the previous rom and installed the MIUI zip.. When I restarted even the MIUI bootanimation did not show up, only the HTC Logo showed up, and the phone rebooted into recovery. .
So, is it bricked ? I tried installing CM9 but same problem..Any help will be appreciated
Click to expand...
Click to collapse
did you 'Make a clean install' , when you flash different rom you have to Clean old one
In TWRP 2.7
Go to WIPE > Advanced Wipe > select :dalvik, cache , data ,system > swipe to clean >>>Than flash ur rom bro
XenoMorphv2 said:
did you 'Make a clean install' , when you flash different rom you have to Clean old one
In TWRP 2.7
Go to WIPE > Advanced Wipe > select :dalvik, cache , data ,system > swipe to clean >>>Than flash ur rom bro
Click to expand...
Click to collapse
Yup wiped everything including system and sd-ext partiton
TAOprajjwal said:
Yup wiped everything including system and sd-ext partiton
Click to expand...
Click to collapse
i dont know bro maybe you need to change recovery ? also can try nand recoveryies... again i dont know much but you can try to 'fastboot flash boot boot.img' method...
our forum slowly dies
TAOprajjwal said:
So, I haven't been using my pico recently..used it about 6 months ago and it has been unused ever since..
Today, I finally picked it up and tried to install MIUI V4. I updated TWRP to 2.7 and it was updated.. Deleted the previous rom and installed the MIUI zip.. When I restarted even the MIUI bootanimation did not show up, only the HTC Logo showed up, and the phone rebooted into recovery. .
So, is it bricked ? I tried installing CM9 but same problem..Any help will be appreciated
Click to expand...
Click to collapse
i think may b its a issue with twrp version... try twrp v2.6 or lower... i think it will work for sure...

Bootloop with every Android N Roms

After flashing android n rom my devices stuck in boot loop
This is not the case with single rom. I am getting boot loop for every android n roms.
I am currently using cyanogemmod 6.0.1.
please help if you have solution.
Dush4711 said:
After flashing android n rom my devices stuck in boot loop
This is not the case with single rom. I am getting boot loop for every android n roms.
I am currently using cyanogemmod 6.0.1.
please help if you have solution.
Click to expand...
Click to collapse
Make you are flashing it correctly.
Wait for at least 20 30 mins.
Reply so i can help you further.
Also mention the steps you did.
ethicalhacker365 said:
Make you are flashing it correctly.
Wait for at least 20 30 mins.
Reply so i can help you further.
Also mention the steps you did.
Click to expand...
Click to collapse
Steps:
Wipe dalvik cache,cache,data,system.
Installing zip.
Reboot to system.
After that phone stuck at boot logo and after some time I felt vibration but phone is not booting up.
I forgot to mention that this problem is with only android n ROMs and
All android m ROMs are working perfectly.
Thank you.
Dush4711 said:
Steps:
Wipe dalvik cache,cache,data,system.
Installing zip.
Reboot to system.
After that phone stuck at boot logo and after some time I felt vibration but phone is not booting up.
I forgot to mention that this problem is with only android n ROMs and
All android m ROMs are working perfectly.
Thank you.
Click to expand...
Click to collapse
I would recommend to follow the steps wisely exactly as i have written.
First copy the rom and gapps file to internal storage and remove sd card and sim cards.
I would recommend rr 5.8.0. It is the best custom ROM i know.
Factory reset.
Go to advanced wipe.
Select only davlik/art cache
I think that you select system and data that is the main cause of the problem.
Now install the rom.
Ike of helpful.
ethicalhacker365 said:
I would recommend to follow the steps wisely exactly as i have written.
First copy the rom and gapps file to internal storage and remove sd card and sim cards.
I would recommend rr 5.8.0. It is the best custom ROM i know.
Factory reset.
Go to advanced wipe.
Select only davlik/art cache
I think that you select system and data that is the main cause of the problem.
Now install the rom.
Ike of helpful.
Click to expand...
Click to collapse
Thanks
Will try after 2 days as I am currently out of town.
Reply you later
Please don't mind.
U are not doing it correctly.
Goto-twrp-wipedata-advanced-check(dalvik/art,Data & Internal Storage) dont check system.
After it Flash with any Custom Rom
Then Wipe-dalvik/art,Data & Internal Storage) uncheck system
Flash Gapps
Again Wipe-dalvik/art,data & internal storage)
Reboot to System
Wait Aleast (10-15)-For me After Flashing 6.0.1 Cyanogenmod from Official Website.
Finish(You have no problem of bootloop)
Hits thanks if you solve this way.
None of the solutions mentioned above worked for me...and the bootloop is only with Android N Roms only. Ihave also tried the official Lineage Os for Yu Yunique, it is also stucking in bootloop. All roms other than Android N (Marshmallow , lollipop ) are working fine.
dh.y said:
None of the solutions mentioned above worked for me...and the bootloop is only with Android N Roms only. Ihave also tried the official Lineage Os for Yu Yunique, it is also stucking in bootloop. All roms other than Android N (Marshmallow , lollipop ) are working fine.
Click to expand...
Click to collapse
Bro search on google Phantom Kernel jalebi. You will get 31st dec, 2016 build of phantom on android file host.
Install rom.
install gapps.
at last install phantom kernel.
rom will boot....
ankitdhimancr said:
Bro search on google Phantom Kernel jalebi. You will get 31st dec, 2016 build of phantom on android file host.
Install rom.
install gapps.
at last install phantom kernel.
rom will boot....
Click to expand...
Click to collapse
Yap it boots but problem is battery discharged within 1 hour
Yeah..phantom kernel will work but on other hand this kernel eats up battery and take to much time on charging usually 3-4 hours
Try censium kernel

Categories

Resources