Related
Hey everyone.
I know there's a couple other threads with this problem, but none of them included their last_kmsg files. It took a bunch of tries before I could stay booted up long enough to grab it, but I have one.
I'm getting a significant number of reboots on my EVO. Like almost unusable at times. It seems fairly random, although there's a slight suspicion is has something to do with the GPS. Maps has been a crash-cause before and the most recent bout last night was brought on by foursquare. (the annoying part is I had just used 4sq fine 30 minutes prior with no issues. Then, booted it up, refreshed locations and my phone was unusable for hours.)
I've done all the standard things. Fix permissions, wipe cache, wipe dalvik, wipe data/system, reinstall the latest CM7 build (update-cm-7.0.2.1-Supersonic-signed.zip), wipe cache, wipe dalvik. I entered my google account info but told it not to sync anything. It is now rebooting less than a minute after it starts up. I haven't installed any apps at all since this most recent wipe/reload of CM7. It reboots with and without the sd card installed.
I'm at a loss here and getting incredibly frustrated. Many replies say it's as easy to fix as wipe everything and re-do it. Obviously something abnormal is screwed up on my phone and I can't figure it out.
Here's the pastebin from this morning: pastebin.com/Ki7H8bH3 (Crap, I don't post here enough to be allowed to post links. Just add the http part to that.)
And then when I got awake enough, I did another complete wipe/reload. The rebooting is even worse now, it's taken me almost an hour to get to a point I can install es explorer to try and pull another file. And when I did, it was blank.
Any ideas?
Thanks!
1. Go to the link below and download the PC36IMG.zip file for amon RA v2.3 and place it on the root of your SD card.
http://forum.xda-developers.com/showthread.php?t=705026
2. Shutdown your device.
3. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install it. Follow the easy prompts to install. Installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. Go to the backup/restore menu and make a nandroid backup of your current setup.
4. Now go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card.
5. Go to the flash menu and flash the rom you desire to flash.
On many occasions, reflashing the recovery solved rebooting issues and hopefully, it will solve yours.
posting & replying via the XDA Premium app.
Hi dougjamal,
Thanks for the reply.
I've made some progress. Last night I had done a majority of what you suggested, with installing amon RA. I've also just formatted my entire sd card just to be sure.
I haven't tried wiping things other than cache and dalvik, so I'll try that.
My progress I mentioned is that I had CM7 up and running until I flashed a new kernel and gapps in there. So I guess I'll just stick with the stock CM7 kernel, try your extra wiping and see how that works.
Thanks!
grifta67 said:
Hi dougjamal,
Thanks for the reply.
I've made some progress. Last night I had done a majority of what you suggested, with installing amon RA. I've also just formatted my entire sd card just to be sure.
I haven't tried wiping things other than cache and dalvik, so I'll try that.
My progress I mentioned is that I had CM7 up and running until I flashed a new kernel and gapps in there. So I guess I'll just stick with the stock CM7 kernel, try your extra wiping and see how that works.
Thanks!
Click to expand...
Click to collapse
You're very welcome. Sorry for the delayed response. I was having a late lunch and then drove home. Anyway, keep us informed of your progress and enjoy the rest of your day.
posting & replying via the XDA Premium app.
No worried on any delay, just glad to have someone that took a read and time to reply!
Ugh, it's the randomness of this that has me so frustrated. I thought I had a good install again, I left it sit on the "touch the android" screen for a few minutes and it stayed on. Made it through the setup process ok. I allowed the setup to "auto-download" a handful of the google apps it asks if you want. Once they got to about 38%... boom, restart.
So I did another toooootal wipe and I'll manually install those apps one by one. We'll see...
dougjamal said:
1. Go to the link below and download the PC36IMG.zip file for amon RA v2.3 and place it on the root of your SD card.
http://forum.xda-developers.com/showthread.php?t=705026
2. Shutdown your device.
3. Simultaneously press the DOWN volume button and the power button until your device starts. There will be a short pause and then a few lines of text will scroll across the screen. Afterwards, the bootloader will automatically detect the PC36IMG.zip file and prompt you to install it. Follow the easy prompts to install. Installation will take less than 10 seconds to complete. Afterwards, reboot into your new recovery. Go to the backup/restore menu and make a nandroid backup of your current setup.
4. Now go to the wipe menu and wipe EVERYTHING in it EXCEPT the SD card.
5. Go to the flash menu and flash the rom you desire to flash.
On many occasions, reflashing the recovery solved rebooting issues and hopefully, it will solve yours.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Seems like this gets posted quite often, huh??? lol
Don't rule out a corrupt download. If you have the time, download both Salvage-Mod 1.2.1 and the gapps zip from http://www.salvage-mod.com/node/4. If you like CM7, you may like Salvage-Mod. It is pure gingerbread. If you decide to flash it, see whether or not you get bootloops with it.
posting & replying via the XDA Premium app.
HipKat said:
Seems like this gets posted quite often, huh??? lol
Click to expand...
Click to collapse
Indeed, my friend...lol...but it works.
posting & replying via the XDA Premium app.
HipKat said:
Seems like this gets posted quite often, huh??? lol
Click to expand...
Click to collapse
It does and it wish it was that easy. It's frustrating to read that others seem to have no issues at all yet when I follow those directions, which are everywhere, nothing seems to work.
dougjamal said:
Don't rule out a corrupt download. If you have the time, download both Salvage-Mod 1.2.1 and the gapps zip from http://www.salvage-mod.com/node/4. If you like CM7, you may like Salvage-Mod. It is pure gingerbread. If you decide to flash it, see whether or not you get bootloops with it.
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
I re-downloaded CM7 this morning thinking that might be the issue, but it hasn't seemed to help. I'll give a different rom a try probably, maybe there's something other than CM7 I'd be content with.
Whelp, I downloaded SalvageMod and their gapps. Wiped everything, installed salvage, installed gapps, rebooted.
I got through set-up, was ok for a couple minutes, then as I was going into my contacts to see if they had sync'd yet... reboot.
This makes me think this can't be a ROM issue.
Any other ideas?
Does the same thing happen when you run a stock (or close-to-stock) rom? Main reason I ask is that this might actually be some sort of hardware problem, but one of the best ways to test for that is to be running on stock software. I wouldn't necessarily suggest flashing an RUU to get to the latest official release, but there are stock rooted roms out there that you could try.
You probably went with CM specifically to get away from Sense and the default HTC stuff (that's most people's reasons anyway), but if you flash a stock rom and it's still rebooting like that then I'd say chances are REALLY good that it's hardware and that you'd have grounds for getting a replacement phone (just remember to unroot first.)
And if it stops randomly rebooting on you then you'll have at least narrowed things down a bit.
jesuspgt said:
Does the same thing happen when you run a stock (or close-to-stock) rom? Main reason I ask is that this might actually be some sort of hardware problem, but one of the best ways to test for that is to be running on stock software. I wouldn't necessarily suggest flashing an RUU to get to the latest official release, but there are stock rooted roms out there that you could try.
You probably went with CM specifically to get away from Sense and the default HTC stuff (that's most people's reasons anyway), but if you flash a stock rom and it's still rebooting like that then I'd say chances are REALLY good that it's hardware and that you'd have grounds for getting a replacement phone (just remember to unroot first.)
And if it stops randomly rebooting on you then you'll have at least narrowed things down a bit.
Click to expand...
Click to collapse
Hey jesuspgt,
I haven't tried that yet. I'll look around for a rooted stock ROM later and give that a shot.
My current status is back to uncertainty. At the moment, my evo has been sitting here fine, not rebooting, for the past hour or two. It's still the Salvage ROM I first installed (i.e. I haven't reinstalled it since it rebooted). Now I haven't really used it any, so it might go to hell as soon as I do that, but for now, it's on and only had that one (maybe two, I can't keep track...) initial reboot.
That's what makes it tricky to diagnose. I know using any custom ROM runs the risk of loosing stability and all ROMs probably produce a reboot here and there. Tough to tell if it's just a "comes with the territory" type of reboot or an actual problem.
Even though I'm sure there's some CM features I'll miss, maybe Salvage is my answer.
Thanks!
*sigh* Well I decided to try using some apps and guess what... reboot.
All I was doing was trying to play a game of Androminion, which is about as basic and not-tasking as possible, so I can't imagine that's what crashed things.
The only thing I can think of that you *may* need to do is reflash your hboot and/or your baseband, PRI & NV from within recovery. You can download it from the link below.
http://forum.xda-developers.com/showthread.php?t=715485
posting & replying via the XDA Premium app.
dougjamal said:
The only thing I can think of that you *may* need to do is reflash your hboot and/or your baseband, PRI & NV from within recovery. You can download it from the link below.
http://forum.xda-developers.com/showthread.php?t=715485
posting & replying via the XDA Premium app.
Click to expand...
Click to collapse
Excellent, I'm going to try that. My hboot is still 0.93!
Hey dougjamal,
Just wanted to drop an update. I know how annoying it is to help someone out and never hear how things ended up!
Who knows what combo helped, but I'm fairly stable now. After updating my hboot, I flashed to Sprint Lovers, did the ##GPSCLRX# trick and then flashed to the latest nightly of CM7 (63 I believe). Only one or two crashes and one bootloop since then.
Of course, as luck would have it, a new problem showed up in the form of a dead spot on my touch screen. Right about where the "Clear" button is for notifications, that entire strip across the phone won't respond to touch. I was hoping it was a nightly issue, but I switched to a different rom and the issue was still there. Looks like it's going in for a warranty claim after-all!
Thanks for all your help
-grifta67
Hi,
I ve been through all this forum and the rest of the internet, but I couldnt find the answer ... so hopefully you will help me.
I have Desire Z - about 3 months old.
I ve rooted the phone and flashed to cyanogenmod 7.1 stable. All the time Ive followed guides here or on cyanogen section/wiki. CM has been running stable for a month maybe until today.
This morning I couldnt make a call - so I rebooted phone.
After reboot phone gets to the home screen and automatically reboots itself after 5 seconds.
info from hboot
VISION PVT ENG S-OFF
HBOOT-0.84.2000 (PC1011000)
MICROP-0425
eMMC-boot
OS ver 1.34.707.3
CID 1111111111
Click to expand...
Click to collapse
Ive already tried:
Wipe cache / davik cache
Wipe battery status
Recover to CM - backup created right after first flash - successfully - problem remains
Recover to original ROM - successfully - problem remains
any ideas?
also - if you dont have any advice to fix this problem - Id like to ask you, if you could point me to the best way, how to unroot/(s-on) etc. phone and make it look like its like stocked one for the purpose of waranty. - i dont mind any data nor in phone nor on sdcard, everything I need is synced to gmail acc. Thank you
cyber-mythius said:
Hi,
I ve been through all this forum and the rest of the internet, but I couldnt find the answer ... so hopefully you will help me.
I have Desire Z - about 3 months old.
I ve rooted the phone and flashed to cyanogenmod 7.1 stable. All the time Ive followed guides here or on cyanogen section/wiki. CM has been running stable for a month maybe until today.
This morning I couldnt make a call - so I rebooted phone.
After reboot phone gets to the home screen and automatically reboots itself after 5 seconds.
info from hboot
Ive already tried:
Wipe cache / davik cache
Wipe battery status
Recover to CM - backup created right after first flash - successfully - problem remains
Recover to original ROM - successfully - problem remains
any ideas?
also - if you dont have any advice to fix this problem - Id like to ask you, if you could point me to the best way, how to unroot/(s-on) etc. phone and make it look like its like stocked one for the purpose of waranty. - i dont mind any data nor in phone nor on sdcard, everything I need is synced to gmail acc. Thank you
Click to expand...
Click to collapse
Pull /proc/last_kmsg and see what it says; should help you narrow it down.
Sent from my HTC Vision using XDA App
could you gimme hand how? - the only point where I can get in the phone is to bootloader / recovery.
so i cant run terminal from apps in phone.
+ could anyone help me how to charge up battery with my problem? I have about 20% on both batteries and I dont want to loose them during repair progress.
to the /proc/last_kmsg - i could not find anything like this on sd
cyber-mythius said:
+ could anyone help me how to charge up battery with my problem? I have about 20% on both batteries and I dont want to loose them during repair progress.
to the /proc/last_kmsg - i could not find anything like this on sd
Click to expand...
Click to collapse
Sorry, I just got to work. The last_kmsg is on your device, not the sdcard. If you have ADB set up you should be able to access it by connecting your phone to your computer
Sent from my HTC Vision using XDA App
I have everything installed on the other PC where Ill be on monday. Maybe Ill find some time to look through it tommorow.
Thank you now for pointing me somewhere - Ill add more info when I ll have it.
I had a similar problem after flashing new rom. My Desire Z was also rebooting after a few seconds.
I downloaded 1.34.707.3 firmware(used to downgrade Desire Z from gingerbread) from CM wiki, installed it through fastboot (step 8) , rooted my phone once again following the wiki and since then my phone is working without any problems.
Battery can be charged up while the phone is turned off.
well I flashed phone with the downgrading rom as you mentioned and it helped a little
- phone is running and not restarting after few seconds - but randomly after 5-60 seconds (so I am able to do at least something ))...
On monday I ll root that bi*ch again, pull there CM7 or some other ROM and post here actual status.
Thank you so far
Similar problem
Hi, I have the exact same problem with my Desire Z. I've attached the last_msg if someone could help me with that.. also, my sdcard is not partitioned so could that have anything to do with it? Thanks, hopefully I'll get an answer soon
Resurrecting a bit of an old thread here but I have just experienced these exact symptoms.
A friend gave me his old Desire-Z so of course I immediately set about rooting it and trying some ROMs.
As a start I went with the most recent Cyanogenmod which is 7.2 at this time. Everything was going smoothly and was just getting used to the phone and it's physical keyboard. My biggest worry was that the battery life wouldn't be good enough for me so I was running a test to see how long it would last. I am a very light phone user. With background wifi disabled, gps disabled and the phone set to 2G only it ran for 7days and 3 hours! No problems there even with a well used battery. When it eventually died I hit the power button to wake it and it started booting and then shutdown again as you would expect. However after I had fully charged it it booted no problems but then went into the boot loop described above. It boots successfully to the home screen but then after 10-15 seconds it reboots. Frustrating!
I tried some things:
Clear cache from CWM: No change
Factory reset from CWM: No change
Reflash CM7.2 from CWM: No change
Clear Dalvik Cache from CWM: No change
Clear Battery stats from CWM: No change. I was hopeful this might be the problem as the battery had been unusually flat, perhaps some flag had been set that caused the reboot.
I have now recovered by reflashing the exploitable original image, PC10IMG.zip, and then going back through the rooting process. I wouldn't want to have to do it again though.
Possible explainations for the behaviour: I was running a battery monitor app (GSam Battery Monitor) which runs continuously and has various power related functions. Though I would have thought anything that was doing would have been removed by factory reset or reflashing CM.
During the 7 days I was testing ROM manager prompted me to update it and then to update the version of CWM that I had. This is perhaps more likely as would have survived everything else I tried to recover until I reflashed the original recovery.
Hope that helps someone and if anyone has any insight on this I'd lobe to hear it.
Steve
Looks like I spoke too soon. First time I had to reboot the phone I got stuck in the reboot loop again.
Hmm, really confused now. No idea what can be causing this that isn't solved by reflashing CM7.2 but is by going back to the original rom?
Steve
the only thing, that helped me back then was to flash another ROM ... give it a try.
there is several other ROMs based on CM, I'm pretty sure, that you'll find one, that will suit you best.
Thanks for the reply I appreciate you taking the time.
It's very odd I can't think what might be causing this. I ran CM7.2 with zero issues for a week. Then first time I had to reboot it gets stuck in the loop.
Since I was away from home I could not get into recovery. I could get into HBoot (by holing Vol. Down + Power) but because I had a PC10IMG.zip file on my sdcard it would just go straight in to asking if I wanted to update from that with no way to select recovery. And of course I needed to have the sdcard in the phone to get an image from it!
So I have been running from the exploitable 2.2 Rom from the rooting procedure since. That can reboot no problems.
Today I tried a much more recent CM10.1 based rom - stuck in boot loop.
Then a tried the Rooted G2 stock ROM which is obviously much older. It booted correctly one time. Then I rebooted it (actually shutdown and then turned on, it doesn't have a reboot option) and now I'm stuck in the reboot loop.
I'm doing a factory reset and clearing the Dalvik cache after flashing each ROM.
I have also tried booting without the sdcard or SIM card, no change.
Something I have observed is that the phone will reboot once after flashing with every ROM, even the original ROM, but then either runs correctly or continuously reboots.
I can only think that possibly I have wrong phone model. I know that the previous owner bought this contract free so it may be some import. Perhaps it's actually a G2 and I'm using the wrong HBoot? I think that's unlikely as it would show an error during the rooting process.
Steve
I doubt you have the wrong hboot, it wouldn't even start if you did. I would do a complete wipe and format maybe change firmware as well. Backup SD and reformat that as well. If you have true radio soff (rooted via gfree) then you are safe to use one of the pc10img.zips I created here
http://forum.xda-developers.com/showthread.php?p=27796375 (see post 30)
Make sure to remove it from SD this time or at least change the name when done
This will give you new engineering hboot, updated 4ext recovery, .19 radio but all can be changed to whatever if you want.
After the flash reformat all in recovery and flash a new rom
Sent from my Nexus 7 using xda premium
Thanks for your input.
Updating the radio rom does seem tempting if potentially dangerous! The claimed power saving especially. I haven't ever used 4ext recovery but given how CWM seems to be failing me I might give it a try.
I don't wan to speak too soon here (but doing so anyway!) it looks like I may have corrected the problems by using SuperWipeG2+ from here: http://forum.xda-developers.com/showthread.php?t=1044992
After running that, which can easily be done from CWM, the phone booted first time with no reboots.
I'll update this if that did not fix it.
Steve
Yep spoke too soon!
However I have found a way to reliably recover but it's not straight forward.
Boot to recovery. Run SuperWipeG2+.
Attempt to boot the phone, boot fails as there is no ROM installed. This step seems important.
Boot to recovery. Install ROM from zip and Gapps from zip.
Reboot and phone will boot successfully and stay booted!
I then have to recover all my contacts and apps from Google which takes a further 20/25 mins.
Having done that I still cannot reboot the phone. If I reboot (or shutdown and power on) it is then stuck ion the boot loop and I have to do that all over again!
This means I cannot ever allow the phone to go flat.
Aaarrgh!
Any suggestions? It has been suggested that installing another ROM could fix this. Any specific ROM? Any idea why that would work?
I have found that the light sensor doesn't seem to be working and the suggested fix for that is to install a Sense based ROM and then switch back. I can't see how that could work either.
Steve
Yeah I've heard the sense ROM thing works, I don't see how but people seem to swear by it. I would suggest you change all your firmware, new hboot, new radio, new recovery and what not a new ROM. There are lots of good ROMs to choose from so I wouldn't know what to recommend for you, personally I almost always use gingerbread based ones
Sent from my Nexus 7 using xda premium
OK, here it goes.
I have a R800x CDMA Verizon Xperia Play
I had bootloader unlocked successfully by alejandrissimo.
I am rooted.
Today I decided to try the MIUI rom for CDMA.
It required custom kernel, and recommended Kieren's darkforest kernel.
I installed that kernel via fastboot with no problems.
Upon turning on phone, i get a page that says Sony, then I get ANDROID page.
Then it just stays on ANDROID. I can tell that it is not frozen because I can see the waving lines going across.
SO, I decided to just go back to stock kernel then try again.
BUT, I cannot get into fastboot!!
I hold search while connecting usb, and the led blinks blue once, then continues with boot.
I am at a loss.
I Can get into CWM.
Please Help!
Edit: I just noticed that after holding search then plugging in USB, the light blinks blue once. Then about 25 seconds later, the light turns solid blue for about 3 seconds. Then just to orange for charging. During this time, I can not get fastboot to recognize device, nor does my computer recognize any devices.
OK, first - don't panic! I had some issues myself with this, but it's easy to resolve.
First - if you want to return to stock, the easiest thing to do is to download flashtool from this link:http://androxyde.github.com/Flashtool/
And the FTF of the stock ROM from here: http://www.mediafire.com/?u70ci3bdzak3u9e
Follow the directions on the Flashtool website for how to flash back to stock. This will make your phone just like it came out of the box. It does not touch the SDCard.
Second - Make sure the kernel you flash in fastboot is the one intended for the ROM you want to install. Also make sure you copy the zip file of the rom you want to install onto your sdcard. Then enter into CWM and do the following:
- clear data
- clear cache
- clear Dalvik cache (under the advanced menu)
- clear Battery Stats (same menu as above)
Then use the menu "install zip from sd card" (or whatever it says ) find the zip file you copied onto you card and load it. Reboot when finished and you should be good to go. Please be aware some ROMS take a long time to boot up the first time around.
Good luck.
netizenmt said:
OK, first - don't panic! I had some issues myself with this, but it's easy to resolve.
First - if you want to return to stock, the easiest thing to do is to download flashtool from this link:http://androxyde.github.com/Flashtool/
And the FTF of the stock ROM from here: http://www.mediafire.com/?u70ci3bdzak3u9e
Follow the directions on the Flashtool website for how to flash back to stock. This will make your phone just like it came out of the box. It does not touch the SDCard.
Second - Make sure the kernel you flash in fastboot is the one intended for the ROM you want to install. Also make sure you copy the zip file of the rom you want to install onto your sdcard. Then enter into CWM and do the following:
- clear data
- clear cache
- clear Dalvik cache (under the advanced menu)
- clear Battery Stats (same menu as above)
Then use the menu "install zip from sd card" (or whatever it says ) find the zip file you copied onto you card and load it. Reboot when finished and you should be good to go. Please be aware some ROMS take a long time to boot up the first time around.
Good luck.
Click to expand...
Click to collapse
ok, small problem with that.
when I click to install flashtool, it tells me that it is not available for my region (Central USA).
I do have a nandroid and titanium backups made just before flashing.
Use this link - I forgot about their link blocking us. But use that site for instructions.
http://www.mediafire.com/?t2pxz1j7snieeos
Having just unlocked my bootloader this weekend as well, I don't know what to tell you there. But since you can get into CWM, reverting to stock is a good way to go. Then try flashing the firmware, etc again.
still stuck
netizenmt said:
Use this link - I forgot about their link blocking us. But use that site for instructions.
http://www.mediafire.com/?t2pxz1j7snieeos
Having just unlocked my bootloader this weekend as well, I don't know what to tell you there. But since you can get into CWM, reverting to stock is a good way to go. Then try flashing the firmware, etc again.
Click to expand...
Click to collapse
OK, thanks for your help, but I am still stuck.
I can not get the device to be recognized.
So, now I need an alternate method.
I will attach the kernel that I flashed, maybe I could flash a ROM that could be compatible.
I tried to flash MIUI v4 from near the end of the MIUI port for CDMA thread (pg 9, I think) , which paxchristos and a few others reported working fine for the R800x
I flashed the kernel that was listed to use in the same post.
But, when I tried to flash the ROM, CWM told me that it was not compatible with my device. It checked the ro.build.fingerprint and determined that it was not compatible.
Maybe another rom would work, and then I would be able to work on it from there
zeeky120 said:
OK, thanks for your help, but I am still stuck.
I can not get the device to be recognized.
So, now I need an alternate method.
I will attach the kernel that I flashed, maybe I could flash a ROM that could be compatible.
I tried to flash MIUI v4 from near the end of the MIUI port for CDMA thread (pg 9, I think) , which paxchristos and a few others reported working fine for the R800x
I flashed the kernel that was listed to use in the same post.
But, when I tried to flash the ROM, CWM told me that it was not compatible with my device. It checked the ro.build.fingerprint and determined that it was not compatible.
Maybe another rom would work, and then I would be able to work on it from there
Click to expand...
Click to collapse
Yeah, that seems to be the wrong boot.img. It should be called boot-v2.img.
EDIT: WOW - I just reread your post after posting mine and realized I pointed you to the same spot!
Try this ROM which is a version of CM9 that Chevyowner got working for our R800x. I know it works because I'm using it. http://www.mediafire.com/?1xnh54i6lvnnh73
It is the same one, i just renamed it because i thought kernels had to be boot.img to flash correctly. I will try that rom when i get home.
Sent from my T100 using XDA
zeeky120 said:
It is the same one, i just renamed it because i thought kernels had to be boot.img to flash correctly. I will try that rom when i get home.
Sent from my T100 using XDA
Click to expand...
Click to collapse
just an fyi, you can name kernels whatever you feel like (I'm not sure about spaces, I use linux, so I never have spaces in names anyways )
Sent from my R800x using Tapatalk
Flashing now
OK, I just downloaded and flashed the ROM about 3 minutes ago.
I cleared everything just like you told me to.
It installed with no errors.
You may be right about long boot times for first boot, otherwise I have a really bad kernel.
It has just sat on Sony screen for the past 10 minutes.
It hasn't even went on to the android page that I got before.
Hoping that it will Work.
Assuming that it doesn't, what would be my best next move?
Can I flash a kernel (Such as doom_lord's CDMA Kernel) via clockwork?
I think I saw a video about it for the Samsung fascinate, however I seem to recall something about needing an s2 file or something??
I will update as soon as I get something. (hopefully good news)
Update: It has been about 20 minutes now and still on Sony screen.
Now it has been 30, im starting to get worried. Should I plug in? Should I just let it be? Should I let it die? Should I battery pull?
Major Edit: I got impatient and just battery pulled. I then tried to get into CWM, but failed. THen I got a bright Idea, why not try fastboot with the new rom. IT WORKED. I WILL NOW TRY TO FLASH A NEW KERNEL AND SEE IF THAT HELPS.
it should not take 30 minutes to boot, only thing i can think of right now is to redownload kernel (boot-v2.img) and reflash that.
chevyowner said:
it should not take 30 minutes to boot, only thing i can think of right now is to redownload kernel (boot-v2.img) and reflash that.
Click to expand...
Click to collapse
is this your kernel, or someone else's? If it's yours/you have a working copy, could you post an md5 so the op can double check it?
Sent from my R800x using Tapatalk
nope not my kernel, and i doubt i have an original working copy as i added 2 lines so i could mount my sdext partition.
Finally!
OK, I am now back up and running.
I went through every kernel and rom for CDMA play, and got nowhere.
I ended up getting Doom's kernel to run. It worked, and booted to android... Then stayed at android.
Then I decided to flash my nandroid i made, and am now working on stock rom W/ DoomKernel.
The ROM seems to be lagging a lot.
Since everything is *working* now, what kernel/ROM combo can anyone verify working for the Play R800x CDMA.
I would really like CM9 or ICS based roms.
Thanks for your help getting me out of this mess!!
EDIT: Nothing seems to be working!! My touchscreen seems to be non responsive, no phyiscal keys except for the power key seem to be working with my original ROM now!!! Maybe somebody could attach a copy of the stock kernel for my device, so that I could start from scratch.
If you're using keiran (darkforest) cm9 kernel the md5sum for it should be: 74a5be2bf95322b8c45780d9daeda4fa
Sent from my R800x using Tapatalk
zeeky120 said:
Nothing seems to be working!! My touchscreen seems to be non responsive, no phyiscal keys except for the power key seem to be working with my original ROM now!!! Maybe somebody could attach a copy of the stock kernel for my device, so that I could start from scratch.
Click to expand...
Click to collapse
This site has some of the stock FTFs, just extract the kernel.sin from the R800x one http://www.xperiagamer.com/Stock-Roms/233-se-stock-firmware-for-root.html
kernel.sin: http://www.mediafire.com/?e29j13d9wpgdvoj
md5sum: 45116201967408d70895ef63c500ed1e
@zeeky120 - I'm sorry you're having so many problems. For me when everything seemed hosed, I started over by using Flashtool and flashing the ftf file I gave you links for. Then once it came back up as stock, I started again from scratch. Depending on what your goals are, you need to flash the proper kernel for that. Then get into CWM. Clear DATA, CACHE, DALVIK CACHE before you do anything else. Then load via zip file the rom you want to install, making sure it matches the kernel you loaded. And, whether necessary or not, I always wipe the big 3 again, just in case. (Call me paranoid, but it helps! )
Ok now up and running on stock everything working great just like out of box. The only thing I have done so far is to root. I want to do it right this time. I would like to flash cm9 based miui for r 800x. Could anyone provide detailed step by step instructions and links for download. Thanks in advance.
Sent from my R800x using xda premium
Closing Notes
This thread has reached its end, because my problem has been fully solved. Advice to future users, always clear the big three, and when in doubt: use flashtool to reboot the ftf. Right now I am up and running on CM9 (use the link in Chevy's signature to download. I can verify that it works great on CDMA. (faster download speeds than stock!!!) Thanks for everyone for all of their help, and I hope to be contributing to development in the near future.
All right this problem has now been solved! Thank goes to khamsakamal48 for posting the solution for the problem. The problem is solved by replacing the updater-script with the one that is used in the GSM version the of Rom. Then Using the latest 4ext recovery, wipe everything and install. Thank you to everyone that have participated in trying to get this solved. This might also work with other recoveries, but has not yet been confirmed.
Updater-Script: http://db.tt/sUfk5p8E
Latest 4ext recovery: http://db.tt/sP5o7HhJ
only thing i could think of is try a different recovery .I haven't had any trouble at all booting miui an i use cwm touch version.
Alright I'll have to give it a try. Was trying to avoid that but oh well. Thanks!
Sent from my Incredible 2
so I tried 4ext and clockwork recovery. Both have caused my phone to just boot right back into recovery. Wiped data and all.
kylesag21 said:
so I tried 4ext and clockwork recovery. Both have caused my phone to just boot right back into recovery. Wiped data and all.
Click to expand...
Click to collapse
Can you give us a little more background on your phone setup? Have you flashed roms successfully before or is this a first time? Are you s-off?
Sorry bout that. I am S-off and I am able to flash all of the other roms available. But when it comes to this one it just won't flash.
Sent from my Incredible 2 using Tapatalk 2
I have been having this same problem. I am going to try to go through everything I have done to see if I can get more info.
I had MIUI V4 (2.9.29 CDMA) running shortly after rooting this phone (maybe 1 week ago). I installed it from the latest TWRP, so that isn't our problem. I loved it and everything was great. I am unsure what radio I was on at the time, and I think that may be where my problems came in.
I successfully installed ViperINC 1.0.0 after doing a factory reset, wiping cache, dalvik from my WORKING MIUI V4. It booted and I played with it for a few hours, but wanted to go back to MIUI. At this point I was on the firmware from nitsuj17's thread. When I tried to factory reset and install MIUI clean again I started having the same trouble as OP. Since then I have tried every radio I could get my hands on, and may have even been a bit sloppy about what firmware I flashed (the only one I'm unsure of is CondemnedSoul's Return to stock as I am unsure what all it included other than radio and stock rom). After a lot of different attempts, I used CondemnedSoul's PG32IMG and went back to stock where I had everything working fine (for stock). I got an OTA update, but wasn't satisfied so I kept trying different radios from the pinned post on the Development thread (really only .0312 and .0320 as well as the first leaked firmware I linked from nitsuj17). So far nothing has worked to get me any further than the OP unless I just use a different rom. Had this rom never worked I would just talk to the developer, but as I had it working before and no idea what changed I'm at a loss.
I don't have enough posts to get something on the Development forum, but if anyone here can help, I'd really appreciate it.
I've been scouring these forums looking for someone who has made progress on this issue. I'm going to make a list here of posts by people having similar problems, if not the exact same. I have yet to see anyone successfully address them.
One of a few people on the MIUI V4 thread who have had the same issue. I had this rom running at one point, though, so I'm not sure what change caused it to stop. I definitely get further with the TWRP recovery (freezes on "android" splash screen) than the 4ext recovery (reboots to recovery).
I don't believe the JB issues are directly related, but similar problems.
Similar to the Jellybean issue above. More similar to my own situation since I also only started having trouble after flashing ViperINC, but I have formatted, wiped and reverted (even to S-ON and unroot Froyo) so much that I can't see how it would have changed anything that I have not removed. This thread has 3+ people with the same sort of issues. Last report one of them installed ViperINC with all defaults and let it run for a few minutes then wiped and re-installed CM10 with success. I may try this, only with MIUI. I have no idea what settings would be slipping through.
And the cdma miui is one of the only roms that boots for me. Running it now. I think Zelmo is right, there's something sticking around with that Aroma script. I've flashed aosp roms over sense roms and vice versa without even wiping and never had issues like these. I've basically wiped this thing with steel wool and always the same thing. It's gone atleast 15 mins with it's bootloop/freezing max cpu process. It ain't gonna boot! I was up until 2am last night ****ing with it. I'm done.
I'm nearly there. Had I never been able to run MIUI, I would probably have dumped it by now, but it's like an itch I can't reach at this point. There is just something there that I can't see or imagine that is hanging in through every wipe I can find. I just formatted my SD card and did a bunch of wipes (I know that has been tried) and I'm going to try VenomINC with all defaults like Zelmo88 had some success with. If I don't have any luck getting to MIUI from there I'll probably go back to my dinc or buy a new phone soon. This one was really an experiment anyway.
Will follow up if I can figure out anything else.
khamsakamal48 posted pretty detailed instructions here. I have confirmed that my install is going pretty fast, so I am betting that could be our issue. I am not sure what causes this or how to prevent it. I'm going to try and flash it a bunch of times here to see if I can get it to complete.
Edit: I tried 3-4 times with CDMA file and had no success making it take longer than 1-2 minutes. I then flashed the GSM file which I had been having the same trouble with and it succeeded! I am going to check my MD5s again on the CDMA file and give it another go.
Edit: I have tried now around 10 times with the file found here linked from khamsakamal48's thread on the development forum. MD5 matches, but I cannot find any method of flashing>wiping>reflashing>rewiping>crying>flashing>snoring which will make it take more than about a minute with the "install". I'm going to type out my log from 4ext so that I have something to do.
>format all partitions (except sdcard)
>wipe dalvik cache ;multiply the repetetive redundancy
>install from sdcard
>MIUI.us_vivow_v4_2.9.29.zip ;MD5 9f36b433635e50e0daf23768280c050f
;begin log
Finding update package...
Opening update package...
Installing update...
Formatting system...
do not formate system ;???
Installing system files... ;this bit may take 1minute
Creating system links...
Set permission...
Update Boot image...
Install from sdcard complete. ;and done in less than 2 minutes every time.
If someone could post a link to this on the Dev forum or something I would appreciate it. I don't feel like spamming 4 more posts just so I have that privilege.
stoicwood said:
khamsakamal48 posted pretty detailed instructions here. I have confirmed that my install is going pretty fast, so I am betting that could be our issue. I am not sure what causes this or how to prevent it. I'm going to try and flash it a bunch of times here to see if I can get it to complete.
Edit: I tried 3-4 times with CDMA file and had no success making it take longer than 1-2 minutes. I then flashed the GSM file which I had been having the same trouble with and it succeeded! I am going to check my MD5s again on the CDMA file and give it another go.
Edit: I have tried now around 10 times with the file found here linked from khamsakamal48's thread on the development forum. MD5 matches, but I cannot find any method of flashing>wiping>reflashing>rewiping>crying>flashing>snoring which will make it take more than about a minute with the "install". I'm going to type out my log from 4ext so that I have something to do.
>format all partitions (except sdcard)
>wipe dalvik cache ;multiply the repetetive redundancy
>install from sdcard
>MIUI.us_vivow_v4_2.9.29.zip ;MD5 9f36b433635e50e0daf23768280c050f
;begin log
Finding update package...
Opening update package...
Installing update...
Formatting system...
do not formate system ;???
Installing system files... ;this bit may take 1minute
Creating system links...
Set permission...
Update Boot image...
Install from sdcard complete. ;and done in less than 2 minutes every time.
If someone could post a link to this on the Dev forum or something I would appreciate it. I don't feel like spamming 4 more posts just so I have that privilege.
Click to expand...
Click to collapse
Your post is an exact match to what I've done. Even tried reverting to ext3 ( no luck, obviously). Well I've got the bug so now I'm not stopping until I figure this out. I'm running viper 1.0.1 so there might be a common element.
grunt9800 said:
Your post is an exact match to what I've done. Even tried reverting to ext3 ( no luck, obviously). Well I've got the bug so now I'm not stopping until I figure this out. I'm running viper 1.0.1 so there might be a common element.
Click to expand...
Click to collapse
I think most of us first noticed these problems around the time we flashed Viper, but I have nuked this thing so hard from so many different directions since the last time I ran Viper that I can't imagine anything surviving. Still, a little too coincidental.
Running the GSM version didn't last long, either. I played around with trying to get it to use my sim, but as soon as I changed some of my network settings it went into a bootloop tailspin and somewhere along the way corrupted my /system. That took a little work to get around, so now I'm back to aeroevan's CM10 which runs OK... other than what doesn't.
Try replacing the updater-script under meta-inf with one from my GSM version!!
Hope that helps!!
Edit: Replace the updater-script with this one- http://db.tt/sUfk5p8E & use this recovery which I downloaded just now- http://db.tt/sP5o7HhJ
All the best!!
Sent from my HTC Incredible 2 using xda app-developers app
[SOLVED]
khamsakamal48 said:
Try replacing the updater-script under meta-inf with one from my GSM version!!
Hope that helps!!
Edit: Replace the updater-script with this one- http://db.tt/sUfk5p8E & use this recovery which I downloaded just now- http://db.tt/sP5o7HhJ
All the best!!
Sent from my HTC Incredible 2 using xda app-developers app
Click to expand...
Click to collapse
Worked perfectly first try! Now running CDMA version without problem. I don't know why it works, but it works. Everyone thank khamsakamal48!
I'm not seeing a meta-inf folder. Is there another place it could be?
Sent from my vivow using xda premium
I believe it is in meta-inf>com>google>android
Updater-script should be located there.
Sent from my HTC Incredible 2 using Tapatalk 2
Nope, no meta-inf. Back to Google
Sent from my vivow using xda premium
Are you using 7zip to open up the zip file?
Sent from my HTC Incredible 2 using Tapatalk 2
I'm too embarrassed to tell you what I was trying got it now, thanks again
Sent from my vivow using xda premium
I have installed the rom of cfx_ace-4.2-BR11 & cfx_ace-4.2-SR1 and install all my apps, change my wallpaper and stuff, butt when I reboot my phone it resets to first installation (lose my wallpaper, my apps, and settings). Can someone help me with this? I really like this ROM.
I use a HTC Desire HD.
Did you a Fullwipe before flashing the ROM?
L3moon said:
Did you a Fullwipe before flashing the ROM?
Click to expand...
Click to collapse
Yes I did full wipe, dalvek & cache
Download again. Flash rom. Reboot. Wait a few minutes. Do your settings, reboot, flash gapps, reboot.
Technically, it doesn't really matter in what order you do it (I believe it so), some people swear by x or y method. In short, you should be able to flash the rom and gapps without needing to reboot in between and without loosing anything. It's odd that you are. After flashing both of those then download your apps, that is, if you use gapps.
Sent from a dream.
Tworan said:
Yes I did full wipe, dalvek & cache
Click to expand...
Click to collapse
Dalvik and cache is not a full wipe. A full wipe is system, data, and cache.
Yes i know, tried it still doesnt work. Installed another rom that One Works fine, going to try and reinstal the rom this weekend.
Sent from my HTC Desire HD using xda app-developers app
i wonder why when certain features are working on one release, some of those features can get problem in the next release?
what happened during the firmware/rom writing process?
yauchildchew said:
i wonder why when certain features are working on one release, some of those features can get problem in the next release?
what happened during the firmware/rom writing process?
Click to expand...
Click to collapse
Things just break sometimes. It's not as easy as it seems to make a ROM with so many features by oneself. If you're talking about GPS not working since SR1, that specific issue was because synergye's source code hosting site BitBucket merged some of his code together and messed things up, and he had to sort that out to get it fixed. That's what I remember reading. GPS and Bluetooth will be working in the next release.
@OP -
Something is messed up in your wiping/flashing process. No one else has the issues you described, save for the wallpaper resetting on restart sometimes. Like Teichopsia said, wipe properly and reflash ROM and gapps. You might think you're wiping correctly, but you might be doing it all wrong. There are many guides on what constitutes a full wipe. Report back here if it still occurs after full wiping and re-flashing properly.
Sent from my Desire HD using xda premium
First time trying anything like this on a smart phone. So tonight I did a "back to factory" restart to get the phone like it was when I opened it out of the box. Then I read about this ROM, and thought why not. So I rooted my phone, then installed the ROM. Everything went fairly smooth, and got the ROM working. My problem is I dont have a google play store app now, and I didnt sync anything, so I dont have any of my apps, nor do I have the ability to download them again. Any help with this?
@gregkneitas said:
First time trying anything like this on a smart phone. So tonight I did a "back to factory" restart to get the phone like it was when I opened it out of the box. Then I read about this ROM, and thought why not. So I rooted my phone, then installed the ROM. Everything went fairly smooth, and got the ROM working. My problem is I dont have a google play store app now, and I didnt sync anything, so I dont have any of my apps, nor do I have the ability to download them again. Any help with this?
Click to expand...
Click to collapse
Flash gapps. Linked in cfX OP.
I do have the gapps file downloaded. I just dont know how to get it on my phone and working. I used a ROM manager app for the ROM file.
From recovery, same way you flashed the ROM (except for the full wipe part; don't wipe.)
bananagranola said:
From recovery, same way you flashed the ROM (except for the full wipe part; don't wipe.)
Click to expand...
Click to collapse
Like I said, I didnt flash the ROM, I used a ROM manager app.I dont know how to get to the recovery screen. Could someone please help me out with a step by step. Keep in mind vol down + power doesnt put my phone into recovery
You need to use "adb reboot recovery" from your computer. There are several good adb guides; check the Ace Think Tank link in my signature. Then, depending on your recovery, find the option that says something like "install zip from sdcard." Use it, navigate to your gapps, and select it.
bananagranola said:
You need to use "adb reboot recovery" from your computer. There are several good adb guides; check the Ace Think Tank link in my signature. Then, depending on your recovery, find the option that says something like "install zip from sdcard." Use it, navigate to your gapps, and select it.
Click to expand...
Click to collapse
Figured it out, thanks!
Next question is I downloaded Gmail App, and it wont sync with my account. I login, and everything but it just sits at the screen saying "Waiting for sync, your email will appear shortly" I've waited well over 10mins and no sync. Ideas?
Have you set up your account in Settings? If you reboot between flashing the ROM and gapps you need to do that manually; it doesn't show a first boot thing.
bananagranola said:
Have you set up your account in Settings? If you reboot between flashing the ROM and gapps you need to do that manually; it doesn't show a first boot thing.
Click to expand...
Click to collapse
It appears I didnt. You solved the problem! Thanks a bunch. Sorry for all the questions.
Ok last question, will adobe flash player work with this ROM? If so how can I get it. I search the market and the app isnt there. And its not on my phone either
4.2 in general doesn't support flash. You could try searching for the apk and sideloading it. Make sure you enable installation from unknown sources in Settings - Security.
sashank said:
Things just break sometimes. It's not as easy as it seems to make a ROM with so many features by oneself. If you're talking about GPS not working since SR1, that specific issue was because synergye's source code hosting site BitBucket merged some of his code together and messed things up, and he had to sort that out to get it fixed. That's what I remember reading. GPS and Bluetooth will be working in the next release.
@OP -
Something is messed up in your wiping/flashing process. No one else has the issues you described, save for the wallpaper resetting on restart sometimes. Like Teichopsia said, wipe properly and reflash ROM and gapps. You might think you're wiping correctly, but you might be doing it all wrong. There are many guides on what constitutes a full wipe. Report back here if it still occurs after full wiping and re-flashing properly.
Sent from my Desire HD using xda premium
Click to expand...
Click to collapse
So, when fixing one thing, the process could probably break some working features.