Develop Bugs

[Q]Desire Z keeps rebooting after few seconds on home screen

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

TWRP Won't load ROM

I have a Kindle Fire that I have already rooted and was running Reloaded, and decided to make a switch to something that was still supported / developed.
Originally, I had CWM and all was well, I installed a ROM without giving it too much thought, and it didn't work - further investigation revealed that I would need to utilize TWRP in order to get the thing back up and running.
"OK", I says to myself, "TWRP it is then."
But... After installing TWRP and reinstalling FireFireFire (it disappeared somewhere along the way, don't ask - I haven't a clue) I am unable to install any ROM's on the device.
Basically, it boots to TWRP, I wipe everything, cache, dalvik and system, then choose the zip I want to install.
So far, so good...
But only, it's not good. Not good at 'tall - It starts to install, then just stops and three buttons pop up on the bottom (Wipe Dalvik; Home; Reboot System).
Now, just for the record - I'm no Android genius, but I think I know enough to get around pretty well; so I start doing some research, poking about in the forums here and elsewhere looking for a little bit of enlightenment, you know - that one little nugget of info that sets off the "AHA!" in the back of your head and you just know that everything is gonna be just hunky dory.
Long story short - I've yet to experience the AHA! moment, nothing is hunky dory and my sleep pattern is in danger of being seriously disrupted...
Any little flash of insight that anyone here can provide would be appreciated...
P.S. Oh, and yeah - in my smug, over-confident first attempt, I neglected to make a backup, so I can't even roll back to the previous image. I propose that you add a smiley guy with a dunce hat for the gallery, just for asshats like me.

Nevermind.
My AHA moment came about a minute after typing the question - I changed the permissions on the system folder to 755, wiped everything again and started over.
Joy.
My sleep pattern will not be disrupted.

To be honest, I would never have thought of that xD

Please Explain
mdwbeex said:
My AHA moment came about a minute after typing the question - I changed the permissions on the system folder to 755, wiped everything again and started over.
Joy.
My sleep pattern will not be disrupted.
Click to expand...
Click to collapse
I'm having the exact same issue as you. Please elaborate on how you fixed it by changing the permissions? I've tried the other fixes found in the forums (like downgrading my TWRP version) but nothing is working. Thanks for the help.

[Tutorial] Installing Wildchild and getting it working on VM WFS CDMA

I'm not entirely sure where this topic would go, but I have figured out how to get wildchild 2.0 and 3.3 up and running on the VM WFS. It might work for other CDMA Wildfires, but I'm not sure. I figured it out after reading a post by 'threefootsmurf' who said he got it working. I'm just making a tutorial on how to install it and get it running fully without problems, since I had a few problems, and to show that we have a great rom for CDMA phones. Oh and these steps are pretty straightforward, but I left out things like backing up everything since you should be in the habit of it already.
1. Download the wildchild file. Either 3.3 or 2.0, I have found that the odex version for 2.0 and the deodex for 3.3 tend to work better than the other..
2. Download the 'Hensemod' VM patch.
3. Put them on the root of you micro sd.
4. Boot to recovery and factory reset and wipe dalvik
5. Flash the wildchild ROM.
6. Boot the phone and go through everything, you will probably get error messages and the phone may shut off and power back on, but your main goal is to get to the home screen after doing the google setup and everything.
7. Reboot back into recovery and do a factory reset and dalvik wipe again.
8. Flash the hensemod VM Patch. (You may need to reflash the rom again and then the VM patch in one go here, it all depends)
9. Boot the phone and go through the google set up and everything again, and the phone should be in working order.
Those were the exact steps I used. I tested multiple ways to do it, some gave me bootloops, some stayed on the HTC splash screen, and some kept rebooting the phone. I like the wildchild ROM and this tut will open up the wonderful rom for VM and possibly all other CDMA users. I hope this helped you guys.
Wildchild 3.3: http://forum.xda-developers.com/showthread.php?t=1842771
Wildchild 2.0: http://forum.xda-developers.com/showthread.php?t=1652973
Hensmod: http://forum.xda-developers.com/showthread.php?t=1434497

thanks for the shout out.
yeah not sure why exactly but i usually need to flash the keyboard add-on to get any keyboard function. and the flashing of the rom on official CWM for marvelc seems to have its issues like deodexed don't like to load right or boot loops. after i switched to the unofficial CWM touch recovery for our phones not an issue at all loading after flash. and i usually flash it all at one time. if anyone has the same CWM as me, to do a data/cache reset select it then press vol up 5 times and you are on yes even though you can not see the option, press power and let it finish its wipe. definitely a great fast rom. found some new tricks i wasn't to test so might go back up to 3.3 soon for the extra speed boosts, only thing holding me back is i don't want to spend a whole night restoring my apps backups again lol.
love experimenting with this little thing though even if i am slightly noob to droid

I advise you to post tutorials like this in the General section

threefootsmurf said:
thanks for the shout out.
yeah not sure why exactly but i usually need to flash the keyboard add-on to get any keyboard function. and the flashing of the rom on official CWM for marvelc seems to have its issues like deodexed don't like to load right or boot loops. after i switched to the unofficial CWM touch recovery for our phones not an issue at all loading after flash. and i usually flash it all at one time. if anyone has the same CWM as me, to do a data/cache reset select it then press vol up 5 times and you are on yes even though you can not see the option, press power and let it finish its wipe. definitely a great fast rom. found some new tricks i wasn't to test so might go back up to 3.3 soon for the extra speed boosts, only thing holding me back is i don't want to spend a whole night restoring my apps backups again lol.
love experimenting with this little thing though even if i am slightly noob to droid
Click to expand...
Click to collapse
I know what you mean I'm a pretty big noob at this stuff too, but it's fun thinking I have some kind of involvement in something. I'm using WC 2.0 right now since I can't get 3.3 to load on the odexed version with wifi and data working. I gotta edit my post. I got the deodexed version running, but it's got bugs, like FB wont work, and a few apps wont work right either, and of course no A2SD support... Lame. And I tried flashing all at the same time. But i'd get bootloops with 2.0. So I had to do it the way I described. Not sure if it's my phone my recovery or what. But yeah....

THANKS

This should be stickied for marvelc.
Thank's wc running great on marvelc.
Sent from my HTC_A510c using xda app-developers app

I just flashed WildChild 3.3 to my VMUSA Wildfire S last night. Here is my experience so far:
Definitely install WC and the VM patch right on top of each other in one shot
Skip the keyboard tutorial in the setup
If you get to the wifi setup and yours isn't listed, you need to wipe/reset/clear dalvik and install both files again or you're gonna have a bad time
I've got video playback problems. Videos I record playback with horizontal matrix green crap, and videos in the YouTube app give me audio only
Opinion: There are a few things I don't like about WildChild which are causing me to abandon it after 24 hours. The video issue is unacceptable, and a bunch of strange app choices make this not much better than the crap apps that come with HTC/VM Sense to begin with. Stock browser is absent in favor of Dolphin, no Google Talk app, no default Calendar, required use of Startup Manager (Free) which I feel is pretty useless to me, and a whole list of other apps (like a dozen) I am too lazy to deal with. I realize what I am looking for is a barebones setup, and I'm going to look for it starting now.

Thanks for this post. I've been running Wildchild 2.0 for a few months now. The video issue mentioned above comes & goes with certain app installations - oddly enough a reinstall of the youtube app usually clears it up on my WFS.

[Q] Problem with A100

Hey! I'd like to start off that I'm new to this forum but I do have a problem with my A100 though.
After getting my Galaxy Note 2, I decided to give my old A100 some new life by rooting it and installing the Jellytime ROM. I'd like to thank the creators of the ROM (pio_masaski & others) because it was the fresh look I wanted on the tablet, however, something happened. Recently, my parents wanted to use the tablet a lot more, so I offered to just give them my tablet but only after undoing everything else I did to it. So on my way to undo everything, I had the stock recovery at hand and the full stock rom at hand on an SD card. I wiped everything and installed the stock recovery, and since it was successful, I proceeded with the stock rom (update.zip) but my tablet was hung up after it installed it. When I say this, I mean it was stuck on the Android loading screen (and it wouldn't stop flashing and looping). So I tried again, wiping one more timing but it produced the same result.
I did look around and I have reason to believe that I just bricked my tablet, maybe because of the flash controller but I'm not sure. If anyone could drop by and tell me what they think of this, it would be awesome. Also, if you have a way of undoing it if possible?
-Thanks in advance!

xdtnguyenx said:
Hey! I'd like to start off that I'm new to this forum but I do have a problem with my A100 though.
After getting my Galaxy Note 2, I decided to give my old A100 some new life by rooting it and installing the Jellytime ROM. I'd like to thank the creators of the ROM (pio_masaski & others) because it was the fresh look I wanted on the tablet, however, something happened. Recently, my parents wanted to use the tablet a lot more, so I offered to just give them my tablet but only after undoing everything else I did to it. So on my way to undo everything, I had the stock recovery at hand and the full stock rom at hand on an SD card. I wiped everything and installed the stock recovery, and since it was successful, I proceeded with the stock rom (update.zip) but my tablet was hung up after it installed it. When I say this, I mean it was stuck on the Android loading screen (and it wouldn't stop flashing and looping). So I tried again, wiping one more timing but it produced the same result.
I did look around and I have reason to believe that I just bricked my tablet, maybe because of the flash controller but I'm not sure. If anyone could drop by and tell me what they think of this, it would be awesome. Also, if you have a way of undoing it if possible?
-Thanks in advance!
Click to expand...
Click to collapse
Its likely bricked, but I would try to flash the update.zip again, power on holding the volume closest to the power button, hold power until it vibrates then let go, it should pick it up and try to flash again, let us know any messages, like failed to mount errors, if any, that show up.
Tapatalked from my GNex - JBSourcery 4.5.6

[Q] Possible gapps issue on PA3.1x (8th of March 2013)

Hi,
First, thank you very much for your work on this. It is leaps and bounds above the performance of the stock rom, with a very nice extra layer of options and functionalities.
I do have a couple of questions:
1) Installing gapps* takes a long, long time. On my phone it took 1h30m for the initial install. Is this expected?
2) When I rebooted my phone after gapps were installed it took a very long time to boot up. (don't know precisely how long, it ran out of battery halfway the second reboor yesterday!) This, as well as point 1 above makes me think that perhaps I should I reflash?
Many thanks!!!
Sidenote: To anyone installing this ROM, there is no progress bar. I found that flashing this ROM also took a while, although nowhere near over one hour!
* I've used all the files in the first post on the rom's thread - Rom, Kernel & 20130301-signed gapps . As for unlocking it, I used the All in one tool kit.