Ok I have a massive problem here. Last night I decided to use the 1 click universal root app to root my phone and flash it to get CM.
I downloaded the app did the root, downloaded clockworkmod then did a clockworkmod recovery. After that finished i was given a pre-root option to backup my phone and wipe data/storage.
I only chose back up my phone. My nexus one then rebooted and proceeded to backup my phone then it went to install CM 6 RC2.. After this had finished it then rebooted and went to the multicoloured animation where the colours ceom from the left and right..
Here it would continuously loop and never do anythign else. With this I pulled the battery and loaded into recovery where I was in ClockworkMod. I then proceeded to use the recovery and as it was doing the recovery it just froze and the progress bar nor any words would come up.
From here I pulled the battery again did a soft/hard reset but it would hang on the loading animation again. I then did a wipe data/clean option and now it just hangs on the X logo.
On my sdcard I still have the clockworkmod folder with the backup, nandroid, system and all the other files as well. Vodafone Australia have no stock of the Nexus One at all and won't be getting anymore in since it's a finished product
I barely have any cash for a new phone and need to know asap what to do to fix this problem! If anyone can help!
When you installed Cyanogen CM6 did you install the proper baseband also or you just didn't write it down for us? If you had 2.2 on the phone before you rooted the baseband is ok for CM6.
Did you try hooking your phone with USB and try if ADB interface works? If your computer sees the phone via fastboot?
IF fastboot works, you could always restore your stock recovery and install a stock FRF91. (And then try again with CM6, this time installing the proper baseband AND WIPING like you should when installing CM6!!)
When installing custom ROMs always read the install instructions whole first then install.
http://forum.cyanogenmod.com/topic/...y-crap-its-full-of-awesome-v600-rc2-07252010/
I need some help with something. I am trying to restore a backup of one of my ROMs that I created a backup of with CW and I am getting this message after Restoring system "Error while formatting /system!" So now if I reboot it gets stuck at the White screen with the HTC.
Does anyone know what this is all about? Why would I get a formatting system error? If I am stuck how do I get back to original state?
I just tried a test with a different back up and same result.
Finally! Someone with the same issue as me!
It sucks.
Even tried flashing the shipped RUU and rooting/S-OFF from scratch. No dice.
Happens with any version of CWM I use.
ProTekk what are you doing now with the phone? Has anyone else given you an explanation? Have you tried to go original out of the box state?
Just reflashed the custom RUU and re-rooted.
Not ideal, but it keeps S-OFF and gives me a working phone.
Grab the RUU file, rename it to PG05IMG.zip, and place on the root of your sd card. UNPLUG the phone and turn it off. Restart the phone UNPLUGGED while holding the volume down toggle. It will flash the RUU to your phone and return it to stock, unrooted, S-On.
Reroot using the instructions from the team.
Been there, done that, got the t-shirt...
This happened to me today too... i reflashed the last ruu file in the rooting directions, reran the last few lines of code and went from there. Then after having superuser installed, and rom manager installed, i verified root and then rebooted into clockwork and installed my old backup. No big issues. Just sucks i had to go through that again.
This happened to me when i tried getting rid of that new virus rom. Not that it was bad, just didnt like the 'flavor'. So i went into cwr cleared data then tried to install my previous backup. That's where it all went to hell.
/\\/\\orlince
Just wanted to let you know I was successful is just flashing a .zip of any ol rom that you can find on the site, I used Lightning v1.2 to flash CWM and then rebooted into recovery and recovered from one of my backups. Hope this helps!
-Justin
I unlocked my bootloader and then tried to flash CWM, but after rebooting it goes back to stock recovery.
Creating a backup via CWM worked fine though, but somehow it won' flash over stock recovery
Anyone else having this problem ?
ma_moto said:
I unlocked my bootloader and then tried to flash CWM, but after rebooting it goes back to stock recovery.
Creating a backup via CWM worked fine though, but somehow it won' flash over stock recovery
Anyone else having this problem ?
Click to expand...
Click to collapse
Yes it happened to me too. There was an option that I could select just before rebooting to prevent this, but it didn't work. I was on stock kk4.4.2 at that time, after installing cm11 nightly, the recovery partition was ok after the reboot. When I later restored the kk4.4.2 to see if it is possible, I had to flash the recovery partition again in order to restore cm11.
enaon said:
Yes it happened to me too. There was an option that I could select just before rebooting to prevent this, but it didn't work. I was on stock kk4.4.2 at that time, after installing cm11 nightly, the recovery partition was ok after the reboot. When I later restored the kk4.4.2 to see if it is possible, I had to flash the recovery partition again in order to restore cm11.
Click to expand...
Click to collapse
So you just flashed CM11, even though it booted back into stock recovery ?
ma_moto said:
So you just flashed CM11, even though it booted back into stock recovery ?
Click to expand...
Click to collapse
Yes eventually Idid. Just like you, I made a backup while at cwm. After the reboot, the recovery partition was gone, and the fallen robot was shown when I selected it. I powered the motog off, did the volume down-power combination, reconnected the usb cable and entered the 'fastboot flash recovery xxxxxx.img' . After a sec or so I pressed vol down , then vol up, and I was back in revovery. Did a test to verify that the backed up kk4.4.2 worked, it did, did it all over again, and flashed cm11. This time, the question about persisting on reboot was not asked, and the revovery persisted.
Ps
I am trying to reach 10 posts in order to report a bug in the developers forum, so if it sounds like I am pulling your leg, I am not.
enaon said:
Yes eventually Idid. Just like you, I made a backup while at cwm. After the reboot, the recovery partition was gone, and the fallen robot was shown when I selected it. I powered the motog off, did the volume down-power combination, reconnected the usb cable and entered the 'fastboot flash recovery xxxxxx.img' . After a sec or so I pressed vol down , then vol up, and I was back in revovery. Did a test to verify that the backed up kk4.4.2 worked, it did, did it all over again, and flashed cm11. This time, the question about persisting on reboot was not asked, and the revovery persisted.
Ps
I am trying to reach 10 posts in order to report a bug in the developers forum, so if it sounds like I am pulling your leg, I am not.
Click to expand...
Click to collapse
I did pretty much the same thing right now and just flashed CM11 and it's working. I did delete personal and system files before via CWM but somehow some pictures i took were still there after CM11 installed I'm also still running stock recovery
Everythings seems to work fine but still...strange
ma_moto said:
I did pretty much the same thing right now just flashed CM11 and it's working. I did delete personal and system files before via CWM but somehow some pictures i took were still there after CM11 installed I'm also still running stock recovery
Everythings seems to work fine but still...strange
Click to expand...
Click to collapse
Yes I did a factory reset or something like that while on cwm just before restoring. Allways do that for a cleaner install. Since you see your photos, I guess you didn't do that part corectly.
If I where you, I whould do it once more, making sure you are flashing 'CWM 6.0.4.7 Swipe Recovery for 4.4 bootloader: CWM-swipe-6.0.4.7-falcon.img' from the thead of dhacker29.
Also make sure you flash the latest nightly directly from cyanogen. This compination will give you a persistant cwm and a 'official' dhacker29 cyanogen rom.
Only problem I have is with audio on csipclient, and the embeded one, but I will eventually reach 10 posts
enaon said:
Yes I did a factory reset or something like that while on cwm just before restoring. Allways do that for a cleaner install. Since you see your photos, I guess you didn't do that part corectly.
If I where you, I whould do it once more, making sure you are flashing 'CWM 6.0.4.7 Swipe Recovery for 4.4 bootloader: CWM-swipe-6.0.4.7-falcon.img' from the thead of dhacker29.
Also make sure you flash the latest nightly directly from cyanogen. This compination will give you a persistant cwm and a 'official' dhacker29 cyanogen rom.
Only problem I have is with audio on csipclient, and the embeded one, but I will eventually reach 10 posts
Click to expand...
Click to collapse
I used CWM directly from their site, maybe that's why it isn't working probably.
You're right i should do a clean reflash, but I'm getting sick of constantly reinstalling and configuring everything
Hello! I've been running the CM13 nightly from Dec 26.
Today i downloaded the Dec 30 nightly.
I had the phone in airplane mode when I rebooted into TWRP to flash the nightly along with the xposed v78 sdk23.
After rebooting my simcard wasn't detected anymore.
It clearly is a software problem, and rebooting or wiping cache/dalvik didn't solve my problem.
I hope you can help me
Same boat. No SIM
No SIM card detected here as well after the 123015 update. I am not using the custom kernel nor was I in airplane mode when I flashed.
Tried rebooting a couple times. Removed SIM card and replaced. Couldn't get it to recognize.
Same problem here with the 123015 update. Reverting to old roms did not work.
just use search ...
you probably use twrp 2.8.6.1 or greater, so new modem firmware in 30/12 nightly is not updated correctly, if you use cm, use cm recovery too or twrp 2.8.6.0! and update rom again
reflash old firmware and it will be back.
its a combination of bad luck and bad flash on the recovery you are using.
use twrp 2.8.7.6.0.
That one is not prone to bad flashes of firmware
no need to restore efs cause the bad flash can be corrected
Sent from my A0001 using Tapatalk
Startlinger said:
reflash old firmware and it will be back.
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Where do I find the 'old firmware'
deleted
just back to 29/12 nightly, flash correct recovery and again flash 30/12
I'm also having this issue, but it happened under different circumstances:
I was using the last CM12.1 nightly (2015-11-21).
On a previous occasion I had clean-flashed the CM13 nightly (2015-12-10), however it was freezing and crashing quite a lot so I decided to wait a bit, and restored my CM12.1 build (after making a nandroid back-up of my CM13 build).
Yesterday (2015-12-30) I thought I'd see how the CM13 builds were going, so restored my CM13 backup... This is when my phone refused to recognise my sim card. On top of this, it would randomly reboot for no apparent reason. I updated to the latest CM13 nightly (2015-12-30) but these problems weren't fixed.
I then decided to restore my CM12.1 build (which was backed up right before I attempted any of this), however the problems remained. It wouldn't recognise my sim card and would reboot at random.
Since then I have wiped cache + dalvik, cache + dalvik + data, cache + dalvik + system + data + internal memory, done a fresh install, and still the problems persist.
After reading the above posts I'm going to try and roll back my TWRP to 2.8.6.0, but needless to say it's been a very frustrating experience!
If anyone can see anything I'm doing amazingly wrong, please let me know.
twrp-2.8.6.0
NoSyt15 said:
I'm also having this issue, but it happened under different circumstances:
I was using the last CM12.1 nightly (2015-11-21).
On a previous occasion I had clean-flashed the CM13 nightly (2015-12-10), however it was freezing and crashing quite a lot so I decided to wait a bit, and restored my CM12.1 build (after making a nandroid back-up of my CM13 build).
Yesterday (2015-12-30) I thought I'd see how the CM13 builds were going, so restored my CM13 backup... This is when my phone refused to recognise my sim card. On top of this, it would randomly reboot for no apparent reason. I updated to the latest CM13 nightly (2015-12-30) but these problems weren't fixed.
I then decided to restore my CM12.1 build (which was backed up right before I attempted any of this), however the problems remained. It wouldn't recognise my sim card and would reboot at random.
Since then I have wiped cache + dalvik, cache + dalvik + data, cache + dalvik + system + data + internal memory, done a fresh install, and still the problems persist.
After reading the above posts I'm going to try and roll back my TWRP to 2.8.6.0, but needless to say it's been a very frustrating experience!
If anyone can see anything I'm doing amazingly wrong, please let me know.
Click to expand...
Click to collapse
in your case your efs may have gotton corrupt, next to a bad flash. Do if flashing old firmware doesnt fix it, restore the backup of efs if you made one to make more confusing you may need a special twrp version to have made the backup on in first place. to make more confusing.
Try this first,official twrp doesnt backup the firmware, so chance is highest you are running cm13firmware and cm12 rom. flash and reboot on recovery official 2.8.6.0, clean and repair system, data, cache. Flash old cm13 and let it boot. Note you should have no(maybe just 2) lines which state after "Writing radio image...")"already up to date
All functioning then score! Proceed with latest nightly
All not functioning efs restore should help. Never made one, follow above and flash back the cm12 rom you have. Same case with firmware updating and booting
Sent from my A0001 using Tapatalk
fronzinator said:
Hello! I've been running the CM13 nightly from Dec 26.
Today i downloaded the Dec 30 nightly.
I had the phone in airplane mode when I rebooted into TWRP to flash the nightly along with the xposed v78 sdk23.
After rebooting my simcard wasn't detected anymore.
It clearly is a software problem, and rebooting or wiping cache/dalvik didn't solve my problem.
I hope you can help me
Click to expand...
Click to collapse
Use 2.8.6.0 of twrp to update modem
Startlinger said:
in your case your efs may have gotton corrupt, next to a bad flash. Do if flashing old firmware doesnt fix it, restore the backup of efs if you made one to make more confusing you may need a special twrp version to have made the backup on in first place. to make more confusing.
Try this first,official twrp doesnt backup the firmware, so chance is highest you are running cm13firmware and cm12 rom. flash and reboot on recovery official 2.8.6.0, clean and repair system, data, cache. Flash old cm13 and let it boot. Note you should have no(maybe just 2) lines which state after "Writing radio image...")"already up to date
All functioning then score! Proceed with latest nightly
All not functioning efs restore should help. Never made one, follow above and flash back the cm12 rom you have. Same case with firmware updating and booting
Click to expand...
Click to collapse
I restored my twrp to 2.8.6.0 (after wiping the entire phone previously... urgh), and then flashed the latest nightly. Everything worked again!
I ended up going back to my CM12.1 backup as the TrueCaller CM app keeps crashing in CM13. I could just keep the stock dialer, but I have grown accustomed to knowing who's calling me!
Thanks for your help all!
I get this issue as well.
IVIatty said:
I get this issue as well.
Click to expand...
Click to collapse
ok, thanks for informing us.
bastard79 said:
ok, thanks for informing us.
Click to expand...
Click to collapse
Thank your for thanking him for informing us
Sent from my A0001 using Tapatalk
Hi, I'm stuck. I have tried flashing the twrp-2.8.6.0-bacon.img recovery image file I got from dl.twrp.me. The file matches the MD5 I got from the TWRP website (f69fa503419644851822d883c2388bb8), and I don't see any errors when I do a fastboot flash recovery twrp-2.8.6.0-bacon.img command.
However, when I have tried to boot back into Recovery Mode, my phone just ends up booting into Normal Mode (until my phone gets hung). Doing a fastboot boot twrp-2.8.6.0-bacon.img command didn't get me into Recovery Mode, either. If I go back and do a fastboot flash recovery twrp-2.8.7.0-bacon.img, I can boot back into the 2.8.7.0 TWRP Recovery Mode, but that won't let me get my modem back.
Can anybody help (maybe with a different copy of the twrp-2.8.6.0-bacon.img recovery image)?
Thanks.
¿GJ?
Startlinger said:
use twrp 2.8.7.6.0.
Click to expand...
Click to collapse
Hi, Startlinger - Do you mean 2.8.6.0? That's a little confusing ...
¿GotJazz? said:
Hi, I'm stuck. I have tried flashing the twrp-2.8.6.0-bacon.img recovery image file I got from dl.twrp.me. The file matches the MD5 I got from the TWRP website (f69fa503419644851822d883c2388bb8), and I don't see any errors when I do a fastboot flash recovery twrp-2.8.6.0-bacon.img command.
However, when I have tried to boot back into Recovery Mode, my phone just ends up booting into Normal Mode (until my phone gets hung). Doing a fastboot boot twrp-2.8.6.0-bacon.img command didn't get me into Recovery Mode, either. If I go back and do a fastboot flash recovery twrp-2.8.7.0-bacon.img, I can boot back into the 2.8.7.0 TWRP Recovery Mode, but that won't let me get my modem back.
Can anybody help (maybe with a different copy of the twrp-2.8.6.0-bacon.img recovery image)?
Thanks.
¿GJ?
Hi, Startlinger - Do you mean 2.8.6.0? That's a little confusing ...
Click to expand...
Click to collapse
Download again via different browser, double check filesize of what you downloaded. It was a bad download sir
You can download on your phone also, same check download size. From twrp where when flashing you can select img. Then select recovery, reboot recovery and your on the one that works
Sent from my A0001 using Tapatalk
Startlinger said:
Download again via different browser, double check filesize of what you downloaded. It was a bad download sir
You can download on your phone also, same check download size. From twrp where when flashing you can select img. Then select recovery, reboot recovery and your on the one that works
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Hi, @Startlinger - I've downloaded twrp-2.8.6.0-bacon.img with three different browsers (Chrome, MS IE, and Firefox). All three images acted the same way: They all matched the MD5 posted on TWRP, and they were all unbootable (either by flashing, or with a fastboot boot twrp-2.8.6.0-bacon.img command). I couldn't download the image to the phone via the internet, because I can't get an internet connection on my OPO anymore - probably because the modem is corrupted. I did copying one of the computer-downloaded 2.8.6.0 images to the phone, and tried flashing the image through TWRP 2.8.7.0, but the results were exactly the same ... it wouldn't boot into Recovery Mode after that.
Is the f69fa503419644851822d883c2388bb8 MD5 value correct? (I suspect it is)
One thing I've noticed is that I can't just power-off my phone anymore when 2.8.6.0 is loaded. If I try to power off, it comes back up in Normal Mode. This may be related to the corrupted 2.8.6.0 Recovery Mode.
Update: I've also noticed something else - I tried doing a fastboot boot twrp-image-file with other versions of TWRP (2.84.1 and 2.8.5.1). None of these boot into Recovery Mode - just the 2.8.7.0 image works.
Is there something else I need to recover on my phone (if it's even possible)? Is there any other way I can reinstall a workable Lollipop 5.0.2 Modem Image onto the phone?
well, thats a first gotjazz.
I would recommend 2.8.7.05 from here https://www.androidfilehost.com/?fid=24269982087010524
if same results, perhaps best to download latest fastboot rom from cyanogen. Then fastboot your way back to a complete stock situation. Before doing so wipe everything in 2.8.7.0, and repair all partitions that allow repairing.
when fastbooting everything take care in using the 64 if you got 64 gb
After let it boot, check if you can get reception. If that works, fastboot flash recovery of 2.8.6.0. or 2.8.7.05 and go back to whatever rom you want
Sent from my A0001 using Tapatalk
Long story short I was running latest nightly of cm13, I decided to flash to cm14 to try nougat. I had backups, during the process I pulled an idiot and wiped everything dalvik, system,data,internal storage,cache . So now I have no backups, I can still get into TWRP and attempt to flash Roms but I've tried countless ones and same outcome, TWRP just restarts half a second after it tries to flash, I've even tried the stock rom with no luck.it starts and gets to MTP enabled installing "name of rom" and then reboots . I've been using a tablet to install the Roms onto an sdcard and then using the sdcard to flash, I'm hoping it's an sdcard issue and I'm waiting to get the laptop to try and put the Roms on internal phone storage and try. I'm hoping I won't have to go back to unroofed stock using kdz tot. If anyone knows what's wrong please help.
Well I tried flashing to stock and can't get into download mode, computer won't recognize phone. So I decided to try updating Twrp flashed the image, rebooted and now I'm stuck on [11050] fast boot mode started. Nothing gets me out of that.