Develop Bugs

phone restarts itself but I dont know why?

I use MCR r5 2.2. it works well. but when I turn on EDGE/3G, my phone reboot alltime. if I turn off EDGE/3G, it stops booting loop(tried 2 3 times to turn off edge/3g).
I tried another ROM 2.2, another Radio, but there's nothing changes, phone reboot itself. even more seriously,sometimes when I go to recovery mode, it still reboot itself here and freezing. I must pull out battery and try again.
information about my desire( rooted/ no lock fone):
baseband: 32.42.00.32U_5.09.00.08
kernel 2.6.32.15-g1fc4045
[email protected]#1
build number 2.06.832.1 cl207528 test-keys
MCR r5
when I flash new ROM: I wipe system/Factory reset, Wipe Cache, Wipe Dalvik( I dont know I wipe Dalvik correctly or not, because I can not see any information about successfully wipe Dalvik ), format ext, flash new ROM, new radio. is it correct?
i have tried radio 32.41.00.32U_5.08.00.04, 32.43.00.32U_5.09.00.20.
any advice for me? sorry my bad English

any help for me . should I try up kernel? My phone is still rebooting now

( Im so confused... I have tried to up ROM again and now it is freezing at HTC screen... what can I do now (.

Can't help you with a direct solution, but I do know that it's not needed to flash the radio every time you flash a ROM.
To end the bootloop I suggest you try it without the ext partition.

Rudolfje said:
Can't help you with a direct solution, but I do know that it's not needed to flash the radio every time you flash a ROM.
To end the bootloop I suggest you try it without the ext partition.
Click to expand...
Click to collapse
thanks for your advice... . i format my sd card with full FAT32( delete Ext2) and the phone boots again( now I use MCR 3.1 radio 4.06.00.02_2, not use froyo ). It went to home screen and looks fine. but sometime it reboots itself. I pulled out sd card and SIM but it still reboot sometimes.
sometimes loop booting, the phone vibrates 7 times quickly at HTC screen after that, it freezes. I must pull out the battery

any advice for me?
anybody see the phone go to recovery mode, but sometimes it reboot itself quickly 7 times( vibrate 7 times in 1 2 seconds) and freeze...
I see an "E:Can't open /cache/recovery/command" in recovery mode when I press + button? what is it?

put your microSD card into a PC using an adapter and run a chkdsk on it
start -> run or start -> search (on vista/7)
type in: CMD and press enter
then type in: CHKDSK X: /f /v /r (where X is the current drive letter assigned to your microSD)
If you're literate enough in linux, and you have an ext2/3 partition, you can also run e2fsck on that partition
from your favourite shell:
e2fsck /dev/sdX2 ( where X is the current device letter assigned )

bestofstrongman said:
any advice for me?
anybody see the phone go to recovery mode, but sometimes it reboot itself quickly 7 times( vibrate 7 times in 1 2 seconds) and freeze...
I see an "E:Can't open /cache/recovery/command" in recovery mode when I press + button? what is it?
Click to expand...
Click to collapse
Are you still able to get to the recovery and stay in the recovery? If so, in recovery go to the option format. Format youre sdcard, swap=0, ext2=512, remainder is fat32. Then upgrade the ext2==>ext3.
Go back to the mainscreen in the recovery and press usb-toggle. Then copy the rom from youre pc to youre sdcard. If done press trackball to disable usb-toggle.
It also might be that youre sdcard is corrupt as poster above me wrote
Then flash the rom and see what happens.

I am having the same issue. All new radio (for 2.2 froyo) will cause random reboot during 3G usage.
The easiest way to reproduce the problem is to keep browsing google map for a few minutes using 3G connection.
Flashing froyo custom rom with old radio (4.06.00.02) does not have this issue, but losing camcorder features...
Anyone idea for this?

sounds similar to my problem (for which i have a partial solution):
http://forum.xda-developers.com/showpost.php?p=7533671&postcount=220
Maybe one of the radio images updated something which shouldn't be updated?
I think this is a general software problem which is pushing the hardware to its limits however people seem to think it is purely a hardware issue.

I had the same issue. After trying everything to fix the problem fully bricked my phone to where it wouldn't even start. I personally its all hardw are.. got my phone replaced and now works fine... I spoke to my carrier and they did say some of the desires just have issues
If possible replace the device , if not I hope u guys eventually sort it out
Sent from my HTC Desire using XDA App

thank all for your attention.
I flashed my phone to MCR 3.1 with radio 4.06.00.02( of course wipe everything). it boot well, to home screen . but sometimes it still reboots itself( now it's on 2.1, not on froyo 2.2 any more)
in recovery mode still have: "E:Can't open /cache/recovery/command"
anybody meets the phone vibrates 7times( reboot) at HTC screen then freezing?

[Q] Stuck on bootscreen

Hey, My phone was working fine till yesterday. N when i tried to flash dk froyo .i had to change the kernel and i guess the bootscreen(htc logo) freezed because of that. I tried flashing hcdr and other kernels and even changed rom back to cm 7.But nothing seems to help.Only cwm is working on my phone. CAn someone help me please

btw its a wildfire

Your best bet Is to try run a ruu as that would reset the phone back to stock, bootloader and kernal, but depending on how you s-offed you may lose the ability to root.( untill you s-off again.) Good luck
sent from my steroid powered, cyanogenmod filled wrecking machine! using xda app.

Perform a full wipe (In CWM, Select "Data Wipe / Factory Reset", then, staying in CWM, go to Mounts and Storage, Select "Format /system". After this, flash a ROM (any) and check if it boots.

Tried. Its still not working. Can any1 post a nandroid backup file of any rom for wildfire. Please. I formatted my sd card too by mistake.

and while flashing a ruu. it always shows a error E:Failure at line 65 and something. Its different everytime

Connect your Wildfire to your PC, In CWM, Go to Mounts and Storage, and Select "Mount USB Storage". This will activate Mass Storage Mode and you can access your SDCard on your PC as normal. (I don't think anyone would upload a Nandroid backup of his own, it contains personal stuff like contacts and all. But, if someone does, good for you)

i mount usb storage n then do wat..? i tried flashing every rom possible. But its still not working. Is it the kernel's problem or what??

I am pretty certain performing a full wipe (Following options in CWM - 1: Data Wipe - Factory Reset, along with 2: Wipe Cache Partition, 3: Format /cache, 4: Format /system, 5: Format /data, 6: Wipe cache partition, 7: Wipe Dalvik Cache) in CWM and flashing a fresh ROM will fix your issue, UNLESS your phone is not bricked due to bad flash, but since you already claim that you have done that, I can't help you any further on this.
EDIT - Also one more thing - When you flash the kernel / ROM, do you get a confirmation message "Installation Complete"? What is your CWM version?

Yes i do.it says installation comple and its v3.0.0.6

Sense ROM's like DK will not work on CWM versions above 2.x.x.x. Anyway, since you tried CM7 already, One last suggestion in that case would be to try flashing the RUU via the bootloader.
Steps -
1: Download the RUU you want to install
2: Extract the rom.zip from the RUU. Procedure here
3: Once you have that rom.zip, Rename it to PC49IMG.zip
4: Transfer this to the root of your SDCard (i.e. - Not in any folders / sub-folders)
5: Restart device in HBoot Mode (Press Vol Down + Power simultaneously)
6: It will scan for the file, and ask to install. Follow On-Screen instructions.

Ill give it a try.

owe you big time man..Thanx a lot..

Return of the Jedi, Yoda is the man.
" once its gone,its GONE."

stuck at htc logo
cRo77y said:
Hey, My phone was working fine till yesterday. N when i tried to flash dk froyo .i had to change the kernel and i guess the bootscreen(htc logo) freezed because of that. I tried flashing hcdr and other kernels and even changed rom back to cm 7.But nothing seems to help.Only cwm is working on my phone. CAn someone help me please
Click to expand...
Click to collapse
search for syed zain ahmed on utube and see his video.. i cant post a link to the video coz i am new , after 10 post i will be able to post the link ... it helped me alot.. do try that method.

syed_786 said:
search for syed zain ahmed on utube and see his video.. i cant post a link to the video coz i am new , after 10 post i will be able to post the link ... it helped me alot.. do try that method.
Click to expand...
Click to collapse
Are you him by any chance?
Sent from my locked, tampered ville

wow, this is quite the thread revival, 2011 was ages ago....

help
Help?
or can anyone help me when I tried to install Custom MTD Partitions I'm stuck whit htc screen all to me erase what to do now when I want to install a new room again stuck please help I already tried all I do not have nor restore any deleted by mistake help

[Q] DINC won't clear user data, after using every trick I know

So, I recently acquired an Incredible, the second one I've owned. The first one I rooted, turned S-off and installed CM7 with zero difficulties, after that I rooted/flashed my Xperia Play CDMA with all the issues that accompany that device. (after the ease with which I modded my first DINC, the hoops through which I had to jump to unlock my bootloader blew my mind)
This DINC, though, refuses to clear user data. Even after multiple wipes via CWM, and multiple updates using the PB31IMG method, user data remains. Attmepts to preform a factory reset via HBOOT result in a balck screen with a red triangle and exclamation point.
I tried to install MIUI, thinking maybe a fresh rom would fix it, but it gets stuck at the room splash screen.
I've even tried recovering a clean CM7 install from my old incredible, but it gets stuck in a bootloop at the rom splash, same story trying to flash the .zip in recovery.
I've seen a few threads that deal with a few of these symptoms, but not the issue as a whole
Thanks in advance for any answers you guys have!
Cheers
I found a solution, finally. Admittedly, it was a bit drastic, but it worked, nonetheless.
I ended up disassembling both DIncs and putting the motherboard of the working device (with the smashed screen) into the device that was unable to format /data.
It was a bit touch and go for a bit, but my new DIY refubished phone is up and running.
Thanks for the help guys!

What error do you get? Can you upload the logs from /cache/ recovery after trying to wipe?
Sent from my Galaxy Nexus using Tapatalk 2

I'm still a bit of a noob, if you could point me towards some basic instructions on how to do that, I'll post a log when i get back to the house.
Last time I tried to logcat something in recovery, I nearly bricked my phone somehow.
Edit: It either gives me the red error triangle/exclamation point if i use HBOOT, or it gives me an error when trying to format the data partition on a recovery attempt.

mattdubuc said:
I'm still a bit of a noob, if you could point me towards some basic instructions on how to do that, I'll post a log when i get back to the house.
Last time I tried to logcat something in recovery, I nearly bricked my phone somehow.
Edit: It either gives me the red error triangle/exclamation point if i use HBOOT, or it gives me an error when trying to format the data partition on a recovery attempt.
Click to expand...
Click to collapse
Re-flash CWM recovery. The red triangle is a problem with recovery most likely. You can flash the latest CWM for the incredible from the app.
If that doesn't work then pull all the files from /cache/recovery location, use a file explorer app that can read it and copy it to the /sdcard location and upload it in a zip.

tiny4579 said:
Re-flash CWM recovery. The red triangle is a problem with recovery most likely. You can flash the latest CWM for the incredible from the app.
If that doesn't work then pull all the files from /cache/recovery location, use a file explorer app that can read it and copy it to the /sdcard location and upload it in a zip.
Click to expand...
Click to collapse
The red triangle happens when you try to do a factory reset from hboot wile on cwm recovery. If you really need to do a factory reset, you will need to flash to the stock recovery first. http://dinc.does-it.net/Recoveries/Stock_4.08.605.15/PB31IMG.zip Then if it works or even if not flash back to cwm recovery http://dinc.does-it.net/Recoveries/CWM_5.0.2.0/PB31IMG.zip.

The weird thing is, that even after flashing PBG31IMG via HBOOT I'm retaining all the previous user data. I've tried formatting the internal drive, using a few different versions of the image, even manual formatting of /data via CWM, which only gives me an error. the same error as when I tried to restore a nandroid from my functioning DINC.

tiny4579 said:
If that doesn't work then pull all the files from /cache/recovery location, use a file explorer app that can read it and copy it to the /sdcard location and upload it in a zip.
Click to expand...
Click to collapse
So do i just make a .zip file out of the contents of /cache/recovery or is there something more to it?

mattdubuc said:
So do i just make a .zip file out of the contents of /cache/recovery or is there something more to it?
Click to expand...
Click to collapse
That should be fine. Try to wipe data in cwm again just so it logs it.
Sent from my Galaxy Nexus using Tapatalk 2

I'm having the same issue, even after reflashing a rom or hard reset my system is as it was before, but most apps don't work. After turning on device instantly shows many errors such as error in com.android.phone etc... While trying factory reset in Recovery (5.0.2.0) the only error that logs is "no app2sd partition found. Skipping format of /sd-ext ". What can you advise? Please help, tomorrow I'm going to another country and in this moment working phone is very needed Device S-OFF Rooted HBoot 0.92

zslashy said:
I'm having the same issue, even after reflashing a rom or hard reset my system is as it was before, but most apps don't work. After turning on device instantly shows many errors such as error in com.android.phone etc... While trying factory reset in Recovery (5.0.2.0) the only error that logs is "no app2sd partition found. Skipping format of /sd-ext ". What can you advise? Please help, tomorrow I'm going to another country and in this moment working phone is very needed Device S-OFF Rooted HBoot 0.92
Click to expand...
Click to collapse
Same error if you flash stock GB sense and factory reset from recovery? You have the errors when booting and the apps are still there?
Sent from my Nexus 7 using Tapatalk 2

Thank you for reply, I solved reset issue by installing Amon Ra recovery. But the problem with apps still exists, it looks like system is restoring back up after reboot, I can do everything with system but after reboot it's like it was before with no changes made. Additionally, it seems that the problem is with emmc, just because when I delete EVERYTHING on it, after restart all files appear again!

I'm also getting an error when I try to manually format the data partition under >mounts and storage in CWM, I'm assuming that may be to blame for retained user data?
When I run show log after running only a manual /data format it displays:
6 black groups
32768 blocks per group. 32768 fragments per group
8112 inodes per group
superblock backups stored on blocks:
32768. 98304. 163840
The filesystem already has a journal,
tune2fs 1.41.6 (30-May-2009)
Setting current mount count to 1
Failure while running mke2fs
Error formatting /data!
mtd: succesfully wrote block at 0
I:Set boot command ""
I have no idea what that means really, or even if it's pertinent.

I had to remove the user info (owner data, phone number, etc) from my inc after canceling my contract with verizon. After about 25 different attempts to wipe it, I finally found something that worked (at least for me)
Tried running the RUU, could not reboot into HBOOT (version error)
Tried the RUU again, this time starting it after manually booting the phone to HBOOT. Got a little farther than before, but still errored out. Did not work. Disconnected phone, pulled battery, rebooted to HBOOT.
Factory reset in HBOOT got me stuck on the stock recovery screen. Battery pulled, could not boot.
Flashed CWM in HBOOT (by renaming to PB31IMG.zip), was able to get into CWM recovery.
Tried to flash the 2nd GB OTA in CWM, did not take. Every option I clicked in CWM gave me about 7 errors after sitting on the logo for a moment. Battery pull, reboot. Boots into CM9. >.<
Booted to my rom, saw about 300 force closes. Tried to reflash CWM from Rom Manager, got a bunch of force closes. Updated Rom Manager from market, reflashed CWM, and this time it worked.
Rebooted to CWM, wipe data/cache/dalvik, reboot.
This time I booted in CM9, but to the initial ICS set up (click next to begin, wireframe pic of Andy)
After skipping thru initial setup, I checked Settings>About Phone>Status. My phone number was removed, network is Unknown, and all my data was removed. Activation prompt appears on each boot.
Not sure if this will help, but worth a try. I think that the HBOOT factory reset is what cleared my data, and then I just needed to fix CWM so I could get back to a working ROM.

Yeah that's what I did in june except I just got service on mine but I would think that would help getting your data out forever. If that does not work I wouldn't know what to tell u besides grab a magnet. Lol
Sent from my Droid Incredible using xda premium

Galaxy GIO S5660 - Can't access csc

Hello,
I have a Galaxy Gio S5660 and I kinda soft bricked it. I've got it used, since my older phone got wrecked in work, so I bought this from a collegaue of mine - he gave it to me for almost free since I fixed his other phone. It had TWRP previously, and I think the internal memory was extended with Link2Sd. But SD card wasn't in the deal, also it had the original Android system on it.
I used ODIN to update Firmware, installed CWM and after that I tried to install CM 7 on it. I failed, since then I can only start in recovery mode and I'm kinda stuck with this problem of mine.
I'm not even sure that I am root, since when I want to run the Update.zip it gives back only error. I cannot wipe, and this is my major concern. When I want to use wipe data/format the phone sipmly freezes. At times I've got some hint like the screen changes to some colorful ant war but I left it to "work" on it for a whole night without results. I have tried to use the advanced options in CWM like mount /data - crash. Format /data crash...
No matter which Firmware I use with any "known to be working'" Rom I cannot move forward since I cannot format. When I udpate the firmware the original 3e recovery gives back an error message "cannot access csc" :S
I wasn't able to install any working root zip. Can anyone help me with this one?

Update
Still no luck, so looking forward to get some advice from tech wizzes

Bump, anyone please?
Show log from CWM:
ro.serialno=
ro.bootmode=unknown
ro.baseband=unknown
ro.carrier=unknown
ro.bootloader=unknown
ro.hardware=gt-s5660v
ro.revision=10
init.svc.recovery=running
init.svc.adbd=running

So, no one seems to be interested but I'm not giving up hope yet.
I'm trough this csc problem and I found the real source of all my problems, the only problem that I do not know how to get around it....
Got CWM up and running, I tried to wipe data, format data or wipe dalvik cache but the phone crashes, restarts itself.
After connecting with ADB shell I tried to use recovery --wipe_data without luck, as above the phone restarted.
Flashed back official ROM, used ADB again - no root permission. Installing CWM and rooting - no luck here from now on I cannot su in shell.
So far I know that I cannot use Fastboot to reflash the whole system, so is there any possible way to restore my corrupted /data?
I think if I could wipe data I could restore my system and such but currently I'm sitting here tearing out my hair.
Any help would be much apprectiated!

Stuck in bootloop, how to recover device ? (work suffering)

I am running Resurrection Remix on a rooted one+3t. I haven't updated the RoM past few months as I was busy with work. My phone used to keep reeboting randomly but that was the only issue it ever had.
Today while I was just browsing , randomly the phone rebooted and got stuck in bootloop screen where the Rom's logo keeps spinning. Also the top back side of the phone heats up a lot when on bootloop
I am able to access TWRP recovery, but since I have been disconnected from xda from a long time, I have completely forgotten what to do to get into the OS without loosing any data .
It is a working day for me and without my phone, its getting really difficult. I am sure it must be a simple fix, any help or pointers would be much appreciated .

Arjs said:
I am running Resurrection Remix on a rooted one+3t. I haven't updated the RoM past few months as I was busy with work. My phone used to keep reeboting randomly but that was the only issue it ever had.
Today while I was just browsing , randomly the phone rebooted and got stuck in bootloop screen where the Rom's logo keeps spinning. Also the top back side of the phone heats up a lot when on bootloop
I am able to access TWRP recovery, but since I have been disconnected from xda from a long time, I have completely forgotten what to do to get into the OS without loosing any data .
It is a working day for me and without my phone, its getting really difficult. I am sure it must be a simple fix, any help or pointers would be much appreciated .
Click to expand...
Click to collapse
Wipe Dalvik and Cache from TWRP and boot. If not successful, dirty flash your ROM. For any other methods, it is better that you are near your PC/Laptop.

tnsmani said:
Wipe Dalvik and Cache from TWRP and boot. If not successful, dirty flash your ROM. For any other methods, it is better that you are near your PC/Laptop.
Click to expand...
Click to collapse
Thanks for helping me out here.. appreciate it.
Tried wiping both dalvik and cache but it didnt work . I dont remember the version of RoM i had, I will try to find the zip of that version to dirty flash. Dirty flashing wont have issues with any of the apps I have installed which are using root ?
What other way is there to fix it ?? I have a pc available with me.
Also, while googling, I found this method on a very old post, will it work ?
The OnePlus One has had its share of bugs, but there has been one issue that effectively breaks the phone without the owner being even accidentally at fault. One minute you're swiping through the app drawer looking at the best way to kill time for a couple of minutes, the next you're hit with a spontaneous reboot and staring at a phone that boot loops indefinitely, leaving you with a bricked device.
The problem is suspected to stem from the "persist" partition getting corrupted during the reboot, even though CyanogenMod doesn't use this particular location. The damaged area doesn't get fixed like other partitions because a filesystem integrity check isn't ran. It's left corrupted, and even though the area isn't needed for the OS to run, the OnePlus One boot loops anyway.
After a helpful session with +Ricardo Cerqueira of +Cyanogen Inc., here's a fix. While your phone is booted to TWRP, run these commands on your computer:
adb shell
make_ext4fs /dev/block/mmcblk0p15
A similar fix appeared earlier on another XDA forum, but this single command is easier, runs faster, and doesn't require any downloads.
Here's the output of the command:
make_ext4fs /dev/block/mmcblk0p15
Creating filesystem with parameters:
Size: 33554432
Block size: 4096
Blocks per group: 32768
Inodes per group: 2048
Inode size: 256
Journal blocks: 1024
Label:
Blocks: 8192
Block groups: 1
Reserved block group size: 7
Created filesystem with 11/2048 inodes and 1166/8192 blocks
Click to expand...
Click to collapse

Arjs said:
Thanks for helping me out here.. appreciate it.
Tried wiping both dalvik and cache but it didnt work . I dont remember the version of RoM i had, I will try to find the zip of that version to dirty flash. Dirty flashing wont have issues with any of the apps I have installed which are using root ?
What other way is there to fix it ?? I have a pc available with me.
Also, while googling, I found this method on a very old post, will it work ?
Click to expand...
Click to collapse
Don't seek that far. Wipe system and all cache partitions and flash the zip you used, then flash Gapps and any other mods and the bootloop should be solved. If not then there is something corrupted on your data partition which means you will have to start over again on a fresh installation of a new rom. I do recommend trying out the latest ResurrectionRemix or any other rom, 99% of the issues are solved.

In situations like these, i usually clear cache, dalvik, and format System partition >> Re-flash rom>Gapps>SuperSu/Magisk >> Let it restart
Usually wiping system partition and installing the rom won't affect your data at all and you will restart with the same apps/settings you had.
If it still won't work, i'm afraid any of your app or any other corrupted file is not letting the phone boot and you might have to actually wipe data partition as well.

Puddi_Puddin said:
Don't seek that far. Wipe system and all cache partitions and flash the zip you used, then flash Gapps and any other mods and the bootloop should be solved. If not then there is something corrupted on your data partition which means you will have to start over again on a fresh installation of a new rom. I do recommend trying out the latest ResurrectionRemix or any other rom, 99% of the issues are solved.
Click to expand...
Click to collapse
abhibnl said:
In situations like these, i usually clear cache, dalvik, and format System partition >> Re-flash rom>Gapps>SuperSu/Magisk >> Let it restart
Usually wiping system partition and installing the rom won't affect your data at all and you will restart with the same apps/settings you had.
If it still won't work, i'm afraid any of your app or any other corrupted file is not letting the phone boot and you might have to actually wipe data partition as well.
Click to expand...
Click to collapse
I have 60+ tabs open in the chrome browser which I dont want to loose. I guess reisntalling gApps means I will loose them. Is there any other way ?
Code:
make_ext4fs /dev/block/mmcblk0p15
Running this command from twrp shell , it asks for size of partition and I dont know how to proceed.

Arjs said:
I have 60+ tabs open in the chrome browser which I dont want to loose. I guess reisntalling gApps means I will loose them. Is there any other way ?
Code:
make_ext4fs /dev/block/mmcblk0p15
Running this command from twrp shell , it asks for size of partition and I dont know how to proceed.
Click to expand...
Click to collapse
I do believe the tabs gets reset when you restart your phone. And no, i don't see a reason why flashing gapps would mess with chrome? Instead flash pico gapps from opengapps.

abhibnl said:
I do believe the tabs gets reset when you restart your phone. And no, i don't see a reason why flashing gapps would mess with chrome? Instead flash pico gapps from opengapps.
Click to expand...
Click to collapse
Tabs dont reset on restarting phone. Some tabs I had open from around 8 months ago.
I cannot flash gApps again as it will result in loosing chrome and all tabs.
Is there anyone who can suggest me some way to recover them ??
I will use bookmarks from now on but i need to be saved this one time please!