I have more than 10 posts but apparently I still don't have permission to post in this ROM thread: http://forum.xda-developers.com/showthread.php?t=1199304 You know what is even weirder? I've posted in a ROM thread before and I cannot reply anymore: http://forum.xda-developers.com/showthread.php?p=15892100#post15892100 Don't ask me how that works. Anyhow....
Installed G2xTreme 1.1.1v2 with clockworkmod recovery 5.0.2.0. Wiped data/factory, cache, dalvik, battery stats before installing. No recovery/backup was done.
Main problem: All vibration is gone, in all modes silent/non-silent even though vibration is set to always, haptic feedback too. I think I had this issue with one other ROM but not on others. Doesn't seem to be a consistent issue.
From what I understand from the g2xtreme thread .. after flashing I guess you have to reboot to recovery and do a clear data/factory reset again... then reboot ..
Related
Well first off I do believe there are 2 different reboot problems. One related to radio/sig and a new one. Im very crazy about wiping everything before flashing roms. I would boot into cwr and wip data/factory reset, cache, dalvik, then go into mounts and storage and format /system and /sdcard. now i would have basically nothing on my phone or sd card.... i would then mount as usb storage from cwr and add the rom i wanted to flash. I would flash it and have 0 probs until the GB roms. Ive found that after wiping the SD card it would boot and after the setup process it would get non stop reboots every time it would get a data or voice sig. to fix it i had to wipe just data cache and dalvik and then reflash the rom and then everything was cool (besides maybe a reboot during setup but thats semi normal) ive gone a day now with 0 reboots on my phone. before that i tested and i can replicate this every time ive even tested it on my co workers phone. I dont know why this happens and im hoping some1 can test it by doing what i did in cwr and confirm that they also get reboots after this.
again the steps are:
Boot into CWR
Wipe data/factory reset
Wipe cache
Wipe dalvik
go into mounts and storage and format /system /sdcard
mount as usb and add in GB bamf beta 4 (since thats what i did my tests with)
reboot do the setup and see if you get reboots
report back here
p.s. please dont flame or ask silly questions kinda wana just keep it to people who have tested and have feed back
p.s.s. to fix the reboots just re wipe data cache dalvik and reflash rom
please some1 test it if you can confirm then im gong to test it on stock froyo roms etc
Hi
I installed CM 7 stable version in my Galaxy s GT9000 mtd last week and until when i captured a video it was working fine and i took my phone to make a call after 5minutes and by the time it was rebooting automatically. I thought its normal but it got bootlooped.i got shocked and luckily it worked fine after i switched off the phone by pressing power button for 30 seconds and switching it on again......
and when i googled about this i saw in most of the forums regarding this problem and learnt that i should wipe the dalvik cache too which i never did during the installation of CM7 (Its not mentioned in the wiki)
I am afraid that it might happen again in future...my question is if i redo the installation again by the following procedure is there any chance that it might not boot loop again???
1.wipe cache
2.wipe data/factory reset
3.Navigate to Advanced-->wipe Dalvik cache
4.Navigate to mounts and storage---> format /system
5.Install the ZIP
Please i need some experts help on this.....(thanks in advance)
can anyone help me on this plzzzzzzzzzzzzzzzzzzzzz
Yeah..flash the custom ROM again..n wipe everything before
version: v8.5
wiped data/factory reset
wiped cache
wiped battery statistics
installed v9 using CWM 5(install zip from SDCARD).
result: bootloop
what gives?
My suggestion would be to try and Flash it all the way from kpe->kpq-> Miui .
This should not be happening based on what you have done so far. That is why the extreme measure of starting over.
If it still does not boot. We might be looking at something entirely different than screwed flashing.
cYbOrG5 said:
version: v8.5
wiped data/factory reset
wiped cache
wiped battery statistics
installed v9 using CWM 5(install zip from SDCARD).
result: bootloop
what gives?
Click to expand...
Click to collapse
same prob for me.
follow the above post method.
cYbOrG5 said:
version: v8.5
wiped data/factory reset
wiped cache
wiped battery statistics
installed v9 using CWM 5(install zip from SDCARD).
result: bootloop
what gives?
Click to expand...
Click to collapse
I install so: flash to KPE---KPQ---Root---Flash with CWM Miui V9. and good
even i had this problem...flash your i9003 with kpq and do factory reset/wipe cache...after rooting process is done using cf root...install miui and clear cache/factory reset
another suggestion may be only good for those not quite in bootloop:
when I flashed to v9, all of a sudden the phone had difficulty "waking up" for an alarm or incoming call. the home button wasn't enough, so I had to press the power button instead. things were weird like that, even when set to oc, etc., until I re-flashed vurrut v3 kernel. things have been normal after that. I didn't factory reset, just wiped caches before flashing v9 so I don't know why it worked that way for me.
is it possible that someone stuck in bootloop may be able to recover without starting over by doing this? for the next person that bootloops, try flashing vurrut v3 from recovery and wipe caches again, then try starting the phone and see if you still have bootloop.
May it helps...
Clean flash of xxkpe then xxkpq.....cf root for xxkpq.......nt ny kernal.....go to recovery...factory reset....cache clear....clear dalvik cache...battery stats....format system...flash v9......repeat procedure not flashing...nd dnt format the system again...reboot...keep still for 10 min....ur done
I found that" ddkp3" as bottom package will be more power, than other bottom package power, I tried[SIZE="<font><font class="">6</font></font>"][/SIZE]
Hi All,
I have the Telstra HTC One XL, and have just recently attempted to install CM10 ROM - however have run into some problems that I would appreciate some advice to rectify. I had recently updated to Jelly Bean OTA.
I followed the guide on these forums - http://forum.xda-developers.com/showthread.php?t=1859478
I Successfully unlocked bootloader by following the steps at HTCdev.com
I Successfully installed TWRP Custom Recovery
I Downloaded CM10 as per - http://forum.xda-developers.com/showthread.php?t=1790032. I transferred this as well as Google Apps onto my phones storage.
When attempting to install CM10, I created the Nandroid backup as recommended, and proceeded to wipe the mentioned items using TWRP (a guide I saw said to wipe everything). This is when my Nandroid back-up got wiped. TWRP gives you the option to wipe cache, delvik cache, factory reset, system, external storage, internal storage and format data. I did alll of these, and this was my mistake I believe? I proceeded to try and install CM10 and gapps from internal storage (I had to re load these back on after I wiped everything), and the install of CM10 displayed as successful.
Upon rebooting to system, the HTC screen comes up first and then goes to the CM10 animation. The phone then stays on this animation (rotating circle) for up to 10-15 minutes.
I have read thread after thread with people experiencing similar issues, and have tried rectifying my problem with various versions of roms and different guides out there. I can still boot into recovery (TWRP) mode via bootloader, and this means I can still mount my phone's storage onto my PC and have access to the storage directory. As I have deleted the Nandroid backup though, and because the ROM's won't install, I am stuck in no man's land.
There must surely be a way to have a ROM installed (even if its back to stock Telstra) from the position I am in, it would be greatly appreciated if someone may be able to point me in the right direction.
Thanks,
Robbie
maybe yall need to "fastboot flash boot boot.img" now
robbie.d said:
TWRP gives you the option to wipe cache, delvik cache, factory reset, system, external storage, internal storage and format data. I did alll of these, and this was my mistake I believe?
Click to expand...
Click to collapse
Why do people keep doing this??? Just because TWRP gives you all those options, doesn't mean you should use them.
Sometimes, people will say to do a "full wipe" when flashing a ROM. But that term is a bit misleading. Factory reset (from TWRP, never from hboot), wipe Dalvik and wipe cache is all that is technically required when flashing a new ROM. Some people like to wipe more "just in case". But if you aren't completely confidant in what you are doing, keep in simple and don't make it more complicated than it needs to be.
I don't know if wiping everything is the cause of your woes, but it certainly didn't help, and caused you to do some extra steps.
Flash boot.img via fastboot as previously suggested. Otherwise, just try to re-download and flash the files agin. Its seems that some people are having troubles booting after flashing CM10 (even after doing the correct wipes and flashing boot.img). Doesn't seem to be much rhyme or reason, but just flashing again has fixed the problem for at least one person.
Thanks so much, such a simple fix! That has me booted up into CM10.
I have installed cm-10-20130107-NIGHTLY-evita and cm-10.0.0-evita , however with both of these versions, my touch screen is not working once it boots up. I can function with the volume up/down, and with the power buttons, but cannot get past my SIM card lock screen.
I noticed this thread http://forum.xda-developers.com/showthread.php?t=2083314 (no solution yet)...
Does anyone have a solution to this issue that seems a common one?
Alternatively, more than happy to get an alternative ROM on my phone in the interim...Can someone recommend me a ROM?
Again, I really appreciate the quick response to my problem, very happy my phone is in operation!
Details first:
Oneplus One 64GB
Have never changed the kernel (so, stock? I think?)
TWRP 3.0.2.0
LineageOS 14.1 - "nightly" (weekly?) 2017-05-01
Phone is (was) encrypted
I'm not quite sure what to make of this:
Yesterday my phone wouldn't turn the screen on. I had received a notification, the notification light was flashing, and I had just used it, but double-tapping the screen or pressing the power button wouldn't turn the screen on. I wasn't overly worried, I've encountered bugs like this before, so I held the power button to restart the phone.
The OS wouldn't move past the boot animation.
The phone very happily booted into the recovery though.
Here's what I've attempted so far, in this order:
Wipe cache & dalvik cache.
Wipe cache, dalvik cache, and data.
Wipe cache, dalvik cache, data, and internal storage.
Restore nandroid backup
Fresh install of OS and Gapps
Fresh install of recovery in fastboot and then #5
Fresh install of a different OS (SlimRom 7.1.2 Beta 2017-04-21) and Gapps
Nothing is getting me back into Android, but as you can read, fastboot and recovery load up with no worries.
Does anyone have any idea as to what might be wrong? I'm about to load a new kernel on and see if that does anything, but I'm not holding my breath.
Any help would be greatly appreciated, thank you.
NoSyt15 said:
Details first:
Oneplus One 64GB
Have never changed the kernel (so, stock? I think?)
TWRP 3.0.2.0
LineageOS 14.1 - "nightly" (weekly?) 2017-05-01
Phone is (was) encrypted
I'm not quite sure what to make of this:
Yesterday my phone wouldn't turn the screen on. I had received a notification, the notification light was flashing, and I had just used it, but double-tapping the screen or pressing the power button wouldn't turn the screen on. I wasn't overly worried, I've encountered bugs like this before, so I held the power button to restart the phone.
The OS wouldn't move past the boot animation.
The phone very happily booted into the recovery though.
Here's what I've attempted so far, in this order:
Wipe cache & dalvik cache.
Wipe cache, dalvik cache, and data.
Wipe cache, dalvik cache, data, and internal storage.
Restore nandroid backup
Fresh install of OS and Gapps
Fresh install of recovery in fastboot and then #5
Fresh install of a different OS (SlimRom 7.1.2 Beta 2017-04-21) and Gapps
Nothing is getting me back into Android, but as you can read, fastboot and recovery load up with no worries.
Does anyone have any idea as to what might be wrong? I'm about to load a new kernel on and see if that does anything, but I'm not holding my breath.
Any help would be greatly appreciated, thank you.
Click to expand...
Click to collapse
Did you tried flashing stock Cyanogen Os through fastboot?
Mr.Ak said:
Did you tried flashing stock Cyanogen Os through fastboot?
Click to expand...
Click to collapse
No, but I tried flashing a different OS, so I wouldn't think that would work? Especially considering Cyanogen is gone and not supporting anymore.
Either way, I worked it out in the end!
I thought I'd tried everything, but turns out I hadn't: I didn't try formatting the phone. Doing so "removed" the previous encryption, which meant that with a fresh flash I could boot again. After that I restored my backup, re-encrypted, and I'm good to go!
So it must've been something wrong with the decryption/boot process(?)
Anyway, thanks for your help!