Ok, lets start from the beginning,
I needed to fix the gps lock on my htc one, so I read that flashing back from cm11 to a sense based rom would fix this, so I flash Viper one in cwm, everything seemed good, until it didn't boot, only booted into bootloader, reflashed a recovery image in fastboot and restored my cm11 backup, so I think everything all good now. But now, I don't have a radio apparently, and my one doesn't recognize the internal sd card in the OS (I can see it in CWM) Help!
Related
i recently flashed froyo to eMMC after rebooting the right way it no longer boots with out a flash card. i can boot off the flash card but no matter what i have tried everything from reinstalling the image to booting back to stock it will not boot on its own. im sure some were in the forum some one has asked but i could not find the answer any help would be great.
Thanks
hopefully this is where this goes. >_> if not, please guide me to where i need to be.
OK. so what is going on:
-right now i am using a STOCK version of 2.2.1 FRG83D, that i rooted with superoneclick.
-i used rom manager to flash RA recovery, because somehow i can't flash roms with clockwork anymore. errors out every time, regardless of version
-i can flash new custom roms using RA, etc etc, but cannot flash roms and restore to old backups
-if i try to USE a custom installed rom, no matter which it is (i have tried a few gingerbread, nxsense, and some 2.2.1 roms), they will ALWAYS reboot after using them for a few seconds, regardless of what i am doing (setting up, using market, or just letting it sit and do nothing)
what i have done before this happened:
-i was using nxsense perfectly fine. great rom, ran great.
-updated rom manager, and clockwork recovery
-tried to flash a new boot animation, but noticed that the new clockwork won't install older .zips that use assert-scripts(?)
-tried to downgrade clockwork, and it randomly restarted the phone during the downgrade
-wanted to try gingerbread, so i flashed the new(er) hboot 0.35.0017 even though i think i had it already, and installed the rom succesfully.
-the rom wouldn't let me download from the market, as it restarted when i tried to download anything.
-i thought the problem was with the new hboot, so i went through a tutorial to revert it back to 0.33.0012 and went back to eclair, so i updated up to frg83d (and obviously got the 0.35.0017 hboot back through updating) and rooted.
the rom i am using now (stock with root) runs fine. haven't really found any real problems.
i just have NO clue why i can't use custom roms. i would absolutely LOVE if someone could help me on this.
I also had similar problem two days ago. I upgraded my clockworkmod recovery to 3.0.0.5 and tried to flash MM CM7 v14. All the problem began. I cannot restore any custom roms except the stock froyo and MM CM7 restarts like crazy whenever I try to install any apps from the market. After that, I also tried RA recovery. No luck. Luckily, I finally find out that the latest recovery messes up my ext3 partition. So, I backup and format my SD card, recreate ext3 partition, restore the SD card, downgrade clockworkmod to 2.5.1.4, wipe everything, fix permission and install MM CM7. It finally works. Hope this help.
PS: as long as I downgrade the clockworkmod, I can restore any custom roms.
Never flash now you will brick it soon
Sent from my Nexus One using XDA App
Latest ClockworkMod was known to have some problem, perhaps.
Use Amon_Ra's, if you want to be sure, and wipe everything (data & dalvik-cache) when going from ROM to ROM. Use Titanium Backup for restoring the apps.
ricky9237 said:
I also had similar problem two days ago. I upgraded my clockworkmod recovery to 3.0.0.5 and tried to flash MM CM7 v14. All the problem began. I cannot restore any custom roms except the stock froyo and MM CM7 restarts like crazy whenever I try to install any apps from the market. After that, I also tried RA recovery. No luck. Luckily, I finally find out that the latest recovery messes up my ext3 partition. So, I backup and format my SD card, recreate ext3 partition, restore the SD card, downgrade clockworkmod to 2.5.1.4, wipe everything, fix permission and install MM CM7. It finally works. Hope this help.
PS: as long as I downgrade the clockworkmod, I can restore any custom roms.
Click to expand...
Click to collapse
omfg thank you so much!!! <3 worked like a charm
kevvibot said:
omfg thank you so much!!! <3 worked like a charm
Click to expand...
Click to collapse
You're welcome. Glad to know my experience can help solving yours too.
Definitely a problem with Clockwork 3.0.0.5! I just went through madness trying to figure out WTF was up as well. The only fix was to completely format and re-partition my card then use RA instead of CW, works great now and I don't know if I will use CW again! What a pain...kinda regret having paid for ROM Manager now after this latest fiasco.
Hi,
I flashed my GT-i9000 (Firmware was Gingerbread BUJVY) using CF Root (CF-Root-XW_NEE_JVH-v3.2-CWM3RFS.tar) through ODIN.
All worked fine and I was able to boot into Recovery using the regular Volume Up+Home+Power.
I then proceeded to flash CM10 nightly (23/9/12) (from my external Micro SD card) by wiping data, wiping cache and wiping Dalvik Cache.
I then navigated to the zip file for CM10 and run it. It started ok then qiuckly the phone rebooted and rebooted into a newer version of CWM (6.0.1.4).
From here I cannot do anything at all!! It won't recognise my Micro SD now to even run the installation again
I'm hoping someone may be able to help, I would really appreciate it!
TIA!
zim_zimmer said:
It started ok then qiuckly the phone rebooted and rebooted into a newer version of CWM (6.0.1.4). From here I cannot do anything at all!! It won't recognise my Micro SD now to even run the installation again
Click to expand...
Click to collapse
Do you know what version is your Firmware? is it 2.3.3 or 2.3.6?, IF its 2.3.3 your boot loader needs to be updated to 2.3.6 for you use , If its already 2.3.6, than you should be able to use CWM recovery to reinstall the CM 10 from your SD card. (But by doing this you may lose your IMEI as you should do a progressive upgrade , like from GB 2.3.6>ICS CM9>JB) or flash a semaphore JB kernel
Easiest way out would be for you to use a JVU ROM to recover, safe your EFS, than proceed to CM 9 and than to CM 10...
you can get a rescue kit or JVU+CFRoot from My Android Collections and or a solution from My Android Solutions
Hi there,
I was on Gingerbread 2.3.6 before I ran the above.
I have gotten a bit further than the above. I managed to mount the phone as a USB whilst in CWM and put the CM10 zip file on the actual phone memory. I then wiped data/cache/dalvik and rerun the install. It installed but didn’t reboot itself, so I rebooted manually and then the Cyanogenmod logo started up and it booted into CM10. Looked ok apart from the Home Button didn’t work!!
Do you think I should still run the above??
Rooting this phone and flashing ROMS is more difficult than my Galaxy S3!!
Cheers
zim_zimmer said:
Looked ok apart from the Home Button didn’t work!!
Do you think I should still run the above??
Click to expand...
Click to collapse
Since you are already on CM 10, you need to solve your home button problem, try doing a wipe in recovery, if fails, flash again the CM 10
Hmmm, it didn’t work.
What I’ve done since though is try to flash another ROM.
I’ve flashed the ‘xBean’ ROM with success, however, I did encounter the exact same problem when flashing the ROM as mentioned above
I wiped data/cache/dalvik and run the install for xBean. It stopped after the first install attempt and rebooted itself, however it just brought me back to the CWM screen (although this time different from the CM CWM).
So I wiped data/cache/dalvik, then run the install again. This time it went through the full install but again (like with CM) it didn’t rebooted automatically. I manually rebooted and then the xBean logo came up and booted in.
This time the home button is working, and pretty much everything else is too by the looks of it. So far so good!
I guess my question would be, why does the ‘ghost installs’ keep happening???
Ok so i had 5.02 rooted kitkat. Obviously unlocked bootloader. It says 3. And twrp 2.8something...
For the previous months every time i rebooted the phone it took like 10 minutes to boot for some reason. But it worked. It was laggy these days so i thought i will wipe everything and install CM12.1.
So i downloaded the rom and gapps. Then i wiped delvik, cache, system, internal memory and data. I also did format data.
I dont really understand, obviously, how android works. So i had the zips on external card and pressed install on from twrp menu. Then wiped cache and delvik cache. Tried to reboot and says 'Warning no OS found'. I say okay and then it says that it wants to root. I say ok again.
Now the PROBLEM is that it does nothing. It justs stucks on motorola boot logo for too much time. I am not sure if this is because i already had a problem with booting taking too much time or because of what i have wiped. I also tried updating bootloader again. Not sure if this changed anything
Long story short, how do i continue now? Is there a way to really delete everything i have done on the phone, then install fresh twrp and then CM12.1? And how do i fix the booting taking too much time problem...
Any help will be valueable. I just dont get how things work because nowadays there are too many things, kernels, roms, bootloaders, recoveries etc... Can i just flash the CM rom from my computer via usb? I tried something like that by ?sideload? only to get a problem about requiring 1.0.32 version. I tried to download new SDK but again i have 1.0.31 version of adb...
Thanks!
P.S. Yes, i am totally lost. But i have desire to understand...
NUKE1989 said:
Ok so i had 5.02 rooted kitkat. Obviously unlocked bootloader. It says 3. And twrp 2.8something...
For the previous months every time i rebooted the phone it took like 10 minutes to boot for some reason. But it worked. It was laggy these days so i thought i will wipe everything and install CM12.1.
So i downloaded the rom and gapps. Then i wiped delvik, cache, system, internal memory and data. I also did format data.
I dont really understand, obviously, how android works. So i had the zips on external card and pressed install on from twrp menu. Then wiped cache and delvik cache. Tried to reboot and says 'Warning no OS found'. I say okay and then it says that it wants to root. I say ok again.
Now the PROBLEM is that it does nothing. It justs stucks on motorola boot logo for too much time. I am not sure if this is because i already had a problem with booting taking too much time or because of what i have wiped. I also tried updating bootloader again. Not sure if this changed anything
Long story short, how do i continue now? Is there a way to really delete everything i have done on the phone, then install fresh twrp and then CM12.1? And how do i fix the booting taking too much time problem...
Any help will be valueable. I just dont get how things work because nowadays there are too many things, kernels, roms, bootloaders, recoveries etc... Can i just flash the CM rom from my computer via usb? I tried something like that by ?sideload? only to get a problem about requiring 1.0.32 version. I tried to download new SDK but again i have 1.0.31 version of adb...
Thanks!
P.S. Yes, i am totally lost. But i have desire to understand...
Click to expand...
Click to collapse
http://forum.xda-developers.com/moto-g-2014/general/restore-to-stock-t2873657 try to restore to stock
I am trying to do this but i dont have some files like boot.img or logo.bin etc.... Where can i download those? There is a link about mfastboot is not working. I am using linux btw so i guess the fastboot i already have is okay
EDIT: Ok i am obviously stupid. The files are on the zip ROM. Okay i am doing this. Now the question i have is, cant i install CM12.1 using fastboot like this ROM?
Okay and it worked. It booted stock rom and this time it booted in a minute or two (considering it was the first time booting i think its awesome).
Now i have to try CM rom. At least i know how to return the phone back if anything happens. Thank you very very much!
NUKE1989 said:
Okay and it worked. It booted stock rom and this time it booted in a minute or two (considering it was the first time booting i think its awesome).
Now i have to try CM rom. At least i know how to return the phone back if anything happens. Thank you very very much!
Click to expand...
Click to collapse
Glad to help
now just copy the rom you want to install and the gapps, install the latest TWRP, wipe: Cache, Dalvik Cache, Data and System and just flash the zips
Many thanks I managed to install CM12.1. Thought i think i failed to flash most of gapps for some reason i dont really care.
I only have one severe bug. 3G is not working for some reason. So i dont have gsm internet except the slow one...
hey guys,
i got a problem with my m7. yesterday i flashed the current gpe firmware for the m7 (that one without stock recovery & boot img). i read in the lineage thread that the rom benefits from it in terms of battery endurance, so wanted to give it a try.
the firmware flash process was done without any problems. i entered the recovery (twrp 3.0.0-2) and i wiped everything except usb-otg. twrp showed me that every partition was wiped successfully. i plugged in my usb cable to copy the lineage rom and gapps on the phone, but then i noticed that it somehow didnt work. i checked the internal storage of my phone and noticed that all the files i "successfully" wiped before still were there.
i flashed back to the firmware i had before (7.19.401.51 without modifications etc.) because i hoped it would give me access to the internal storage but unfortunately the problem remained the same.
now i cant copy anything on the phone to flash some new roms and stuff and i cant use it because theres no rom installed.
guys please help me if you can i really appreciate it! (sry for any mistakes im not a native english speaker)
Maybe flash latest version of twrp might help you? https://dl.twrp.me/m7univ/
hey mate,
somehow i managed to bring my phone back to life. i dont know if it has anything to do with the newest twrp but im very happy that it works. thank you for your help!