Database Info

com.android.phone FC after installing stable CM7.1

Hi,
The release of the stable CM7.1 really encouraged me to finally S-OFF my phone and install it. I used Revolutionary 0.4pre4, and installed CWM 5.0.20. I wiped everything (data, system, cache, dalvik, you name it), and installed the CM7.1 update zip and right afterwards the new Google apps zip. Eventually, I used Fix Permissions, and rebooted.
I was quite happy, until I saw the com.android.phone FC message. It just showed the same message over and over. I updated my radio to the latest version, to no avail. I tried reformatting, re-wiping, reinstalling quite a few times, and I even tried 3 different sim cards. I finally decided to go back to RUU (kept S-OFF), and didn't get any FCs.
I'm really frustrated, since it is my first Android phone, and I really believe I tried everything already.
Thanks in advance.

I got no problem at all until now.

Another thing I've discovered is when I get these FCs, sometimes if I enable the bluetooth, the phone suddenly discovers the network and the FCs stop. That's just very odd, to me.
I really hope that's not a problem with my phone (especially since it does work properly with RUU).

foouser said:
Hi,
The release of the stable CM7.1 really encouraged me to finally S-OFF my phone and install it. I used Revolutionary 0.4pre4, and installed CWM 5.0.20. I wiped everything (data, system, cache, dalvik, you name it), and installed the CM7.1 update zip and right afterwards the new Google apps zip. Eventually, I used Fix Permissions, and rebooted.
I was quite happy, until I saw the com.android.phone FC message. It just showed the same message over and over. I updated my radio to the latest version, to no avail. I tried reformatting, re-wiping, reinstalling quite a few times, and I even tried 3 different sim cards. I finally decided to go back to RUU (kept S-OFF), and didn't get any FCs.
I'm really frustrated, since it is my first Android phone, and I really believe I tried everything already.
Thanks in advance.
Click to expand...
Click to collapse
Nothing has ever broken my phone quite as much as when I have done the 'fix permissions' thing. Totally screwed my phone and was FC city. I've never done it since, and never had any problems since. Try going back over your steps and leave out the fix permissions part!
I recently had a quick go with CM7 nightlies and had no issues. This included the last nightly before it became stable which was very close to the stable version.

wnp_79 said:
Nothing has ever broken my phone quite as much as when I have done the 'fix permissions' thing. Totally screwed my phone and was FC city. I've never done it since, and never had any problems since. Try going back over your steps and leave out the fix permissions part!
I recently had a quick go with CM7 nightlies and had no issues. This included the last nightly before it became stable which was very close to the stable version.
Click to expand...
Click to collapse
Tried doing the same process without fixing permissions, twice already, and I still get the same problem.

have you tried this?
http://forum.xda-developers.com/showpost.php?p=18309360&postcount=9

Helped with the market issue, but not yet with the com.android.phone FC...

foouser said:
Helped with the market issue, but not yet with the com.android.phone FC...
Click to expand...
Click to collapse
Odd. Here is how I did mine, step-by-step. (Do a NANDroid backup before this, and copy it to your PC/Mac.)
1. Install latest 4EXTRecovery from here: http://forum.xda-developers.com/showthread.php?t=1130004
2. Use this to format all partitions to EXT4. (Not sure if you are using EXT3, not sure if it matters, just saying I'm on EXT4 formatting with no issues.)
3. Do the full wipe & manual format routine (including boot) again just in case!
4. Flashed CM7.
5. Flashed Gapps.
6. Flashed Tiamat kernel (1.1.4)
7. Reboot.
I'm used the same radio as in my sig but also doubt that matters. Not sure what else to suggest. Try downloading the ROM again, and compare the MD5 of your two downloads.

Wow, I believe I'm in some big trouble now. I decided to try and get my phone replaced in the store since I just recently bought it. I used this guide: http://forum.xda-developers.com/showpost.php?p=17481836&postcount=2 to get back to S-ON, but when I tried to flash back the RUU, I get a CUSTOMER ID ERROR and the flash fails.
I've tried two RUUs: RUU_Saga_HTC_Europe_1.47.401.4_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199410_signed
RUU_Saga_hTC_Asia_WWE_1.48.707.1_Radio_20.28I.30.085AU_3805.06.02.03_M_release_199476_signed
But they both end up the same way. I'm now stuck on the HBOOT screen with S-ON and a big purple security warning (I guess since CM7 is still on the /system partition).
Any help?

Try solution 2 of this guide http://forum.xda-developers.com/showthread.php?t=1284196
but replace the mmc....
With
mmcblk0p25
this will format your system partition,
maybe also data could be formatted by replacing mmc... with mmcblk0p26,
after that run the ruu again.
Swyped from my Desire S

Tectas said:
Try solution 2 of this guide http://forum.xda-developers.com/showthread.php?t=1284196
but replace the mmc....
With
mmcblk0p25
this will format your system partition,
maybe also data could be formatted by replacing mmc... with mmcblk0p26,
after that run the ruu again.
Swyped from my Desire S
Click to expand...
Click to collapse
I don't really have access to recovery (it just gets me back to fastboot), let alone Android, so I don't see how I can follow this guide (maybe I misunderstood)...

I have FC with Market. Everytime i try to acces it.

foouser said:
I don't really have access to recovery (it just gets me back to fastboot), let alone Android, so I don't see how I can follow this guide (maybe I misunderstood)...
Click to expand...
Click to collapse
Don't mind the recovery step, just do the commands within adb shell
Swyped from my Desire S

mihaibuda said:
I have FC with Market. Everytime i try to acces it.
Click to expand...
Click to collapse
Have you tried wiping cache and
dalvik cache?
I also had fc after an update, this solved it for me.
If you're using cyanogen, try changing the language to English us, this solved it for some users.
Swyped from my Desire S

Never mind, I actually created a goldcard in order to bypass the CUSTOMER ID error and flashed my phone back to original and S-ON. Thanks anyways.
Just as a note to everyone, you should really go about getting back to S-ON via this way: Flash any RUU, get the original HBOOT image from that RUU (you can find it in your temp folder while flashing the RUU), and then just downgrade the HBOOT using fastboot. Easier than going through ENG HBOOT, and allows you to avoid these kind of problems (CID errors).

The problem is that you restored "DIALER STORAGE" via titanium backup. Reflash ROM, and don't restore this. It'll work, FOR SURE.

foouser said:
Never mind, I actually created a goldcard in order to bypass the CUSTOMER ID error and flashed my phone back to original and S-ON. Thanks anyways.
Just as a note to everyone, you should really go about getting back to S-ON via this way: Flash any RUU, get the original HBOOT image from that RUU (you can find it in your temp folder while flashing the RUU), and then just downgrade the HBOOT using fastboot. Easier than going through ENG HBOOT, and allows you to avoid these kind of problems (CID errors).
Click to expand...
Click to collapse
Can you please post the thread that contains the Gold Card creation process (if there was one) so that I can add it to the INDEX.
As no doubt this will be useful to others...
ty

ben_pyett said:
Can you please post the thread that contains the Gold Card creation process (if there was one) so that I can add it to the INDEX.
As no doubt this will be useful to others...
ty
Click to expand...
Click to collapse
Sure, it's really the same process for all HTC phones and works even on the newest models (Sensation generation). Thanks a lot to EFI from AlphaRev who actually pointed me in the right direction.
I used this guide: http://theunlockr.com/2010/03/10/how-to-create-a-goldcard/
I'm using Windows 7 x64 and when I inserted the card after modifying it, Windows required me to format it (as opposed to what's written in the above guide), but it still worked. Also, since my phone was stuck on HBOOT I had to use another Android phone to get the SD's CID (I used a friend's SGS, and the SD slot to query is mmc2 on it).
shrome99 said:
The problem is that you restored "DIALER STORAGE" via titanium backup. Reflash ROM, and don't restore this. It'll work, FOR SURE.
Click to expand...
Click to collapse
Well, I actually didn't use Titanium Backup at all, so nope.

[Q] I think I have done something wrong.

Salutations,
I recently installed a ICS ROM from another site, was meant to be in beta but it crashed and wouldn't reboot unless I removed the battery everytime the screen went off. I thought I would wipe everything and just go back to the stock ROM for a while until all of the ICS builds have matured.
Sadly this wasn't the case, after wiping everything ( I wanted to clean the SD card etc as well ) the phone doesn't boot, remains stuck on HTC logo if it wants to go that far. The LED is flashing orange and I cannot get into HBOOT.
Any help would be greatly appreciated!

The flashing LED light means u got low battery, so I would suggest you charging it.
to get into recovery remove the battery, and then try again. When in recovery wipe cache and dalvik cache and try to reboot.
The screen-off problem I have no idea how to fix, try re-downloading, maybe u got a broken zip. Or just try another ROM.
Sent from my MIUI.us Sensation 4G using xda premium

Make sure you do "supercid" then go ahead and download and run the correct ruu and drivers for your version of sensation problem solved

mendes52309 said:
Make sure you do "supercid" then go ahead and download and run the correct ruu and drivers for your version of sensation problem solved
Click to expand...
Click to collapse
Thanks for the responses, I think I must have wiped the boot partition and messed up the ruu. Problem solved when I downloaded a new ROM on my Mac and moved it onto the SD card and installed it. Got quite worried that I might have soft bricked the device!

wifi error on every ROM

long story short, my phone was shipped with prerelease software. After rooting and flashing a customer recovery, my original nandroid was corrupted.
The only option for me now is custom ROMs, but unfortunately my wifi gives me an error on every single ROM available.
Anyone know of a quick fix?
The only thing i can think of that would solve the issue is to possible flash the stock US ROM once it's available, then hopefully that would fix my wifi issues and i'd be able to flash to any other ROM with no problem.
Alternatively - could someone please post a flashable ZIP of the stock ROM, or at least post a stock nandroid that i would be able to restore onto my phone to see if the wifi issue gets resolved.

Did flashing the stock img work
Sent from my PC36100 using Tapatalk 2

I have a fix for you. I'm releasing it tomorrow though.
I'm releasing a stock T-Mobile nandroid final firmware and newest software.
I'm also releasing a rooted version.
Sent from my HTC VLE_U using XDA

Full wipe on everything?
Sent from my Galaxy Nexus using Tapatalk 2

MikeyCriggz said:
Full wipe on everything?
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
Always
After doing a bit of reading, it seems as though some people have having similar issues. The exception is that theirs is doing this while stock, and updating their router firmware fixed the problem. My phone connected to my router perfectly fine while stock...the problem didn't occur until i flashed the first custom ROM.

Reviewers said:
I have a fix for you. I'm releasing it tomorrow though.
I'm releasing a stock T-Mobile nandroid final firmware and newest software.
I'm also releasing a rooted version.
Sent from my HTC VLE_U using XDA
Click to expand...
Click to collapse
Thanks, hoping this will solve the problem!

suhailtheboss said:
Always
After doing a bit of reading, it seems as though some people have having similar issues. The exception is that theirs is doing this while stock, and updating their router firmware fixed the problem. My phone connected to my router perfectly fine while stock...the problem didn't occur until i flashed the first custom ROM.
Click to expand...
Click to collapse
It's because all roms now are based on European firmware not T-Mobile firmware.
Tomorrow I'm uploading the first ever T-Mobile Rom and it'll fix everybodys problem.
Sent from my HTC VLE_U using XDA

suhailtheboss said:
Always
After doing a bit of reading, it seems as though some people have having similar issues. The exception is that theirs is doing this while stock, and updating their router firmware fixed the problem. My phone connected to my router perfectly fine while stock...the problem didn't occur until i flashed the first custom ROM.
Click to expand...
Click to collapse
Definitely sounds like a firmware or driver issue. Have you tried resetting your router or updating its firmware? Also, what kernel version are you running.
Sent from my Galaxy Nexus using Tapatalk 2

MikeyCriggz said:
Definitely sounds like a firmware or driver issue. Have you tried resetting your router or updating its firmware? Also, what kernel version are you running.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
tried connecting to a different router on update stock firmware and teh issue still exists.
I was hoping that with the stock TMO-US ROM the problem would be fixed, but unfortunately not.
Now i have really no idea. It's impossible for me to live without wifi on my phone for good.

suhailtheboss said:
tried connecting to a different router on update stock firmware and teh issue still exists.
I was hoping that with the stock TMO-US ROM the problem would be fixed, but unfortunately not.
Now i have really no idea. It's impossible for me to live without wifi on my phone for good.
Click to expand...
Click to collapse
Do this:
1. Delete /data/misc/wifi folder using a file browser.
2. Clear cache using recovery. Reboot. Wifi will regenerate its data.
3. Try wifi again.
Let me know if this works. It's a shot in the dark so I don't know if that's gonna work for you, since you already seem to have performed a fac reset.

nickmv said:
Do this:
1. Delete /data/misc/wifi folder using a file browser.
2. Clear cache using recovery. Reboot. Wifi will regenerate its data.
3. Try wifi again.
Let me know if this works. It's a shot in the dark so I don't know if that's gonna work for you, since you already seem to have performed a fac reset.
Click to expand...
Click to collapse
Thanks for the tip, unfortunately this didn't work either. I'm totally out of ideas at this point. Might just end up exchanging the phone and paying the out of warranty fee if they find out the boot loader was unlocked. Not really sure what's left for me to try.

Flash my T-Mobile Nandroid in recovery.

Reviewers said:
Flash my T-Mobile Nandroid in recovery.
Click to expand...
Click to collapse
I did within ten minutes of you posting it. Unfortunately it did not solve the problem. I thought that would be the fix...

One thing I didn't notice was a clear description of the problem. Please describe what your issue is. You say the wifi gives you an error. What does that mean?
Please describe everything in detail from start to finish, before trying to return it.

WiFi will turn on, display available networks, once a network is selected it will not connect and then says "error"
then after about ten seconds the phone will reboot, then reboot after it turns on. never-ending.
only way to have the phone work is to do a master reset, but the problem starts again when you attempt to.connect to WiFi.
also the phone will not stay off when stuck in the WiFi reboot loop. if i choose "power down" it will turn off, then turn back on within 10 seconds.

That sounds very very strange. Almost like a kernel error (unlikely since kernel is included w/ ROMs), a radio issue (more likely), or a hardware issue (most likely, in my opinion). If you've already done a full wipe and wiped /system and /sdcard to be sure, then it sounds like you've done your due diligence.
At this point you might want to go ahead and reflash the stock ROM (see Reviewer's post with a nandroid of the stock ROM), reflash the stock recovery, and relock the bootloader. Unless someone else can chime in here. Also, if you return it, there's no promises that they won't look for TAMPERED or anything in the bootloader, so beware. The important thing is to have the stock software and recovery loaded and it relocked. Then they can flash it in the store, and it'll probably fail, in which case they may replace it.

nickmv said:
That sounds very very strange. Almost like a kernel error (unlikely since kernel is included w/ ROMs), a radio issue (more likely), or a hardware issue (most likely, in my opinion). If you've already done a full wipe and wiped /system and /sdcard to be sure, then it sounds like you've done your due diligence.
At this point you might want to go ahead and reflash the stock ROM (see Reviewer's post with a nandroid of the stock ROM), reflash the stock recovery, and relock the bootloader. Unless someone else can chime in here. Also, if you return it, there's no promises that they won't look for TAMPERED or anything in the bootloader, so beware. The important thing is to have the stock software and recovery loaded and it relocked. Then they can flash it in the store, and it'll probably fail, in which case they may replace it.
Click to expand...
Click to collapse
Yeah i'm clueless. I've literally done absolutely EVERYTHING that i could imagine to fix the issue.
I actually work for T-Mo, we dont have any abilities to flash anything in store. Also exchanging the phone is a little bit more difficult for me, because the phone was not purchased through tmobile, it was given to me by HTC a week before launch.
Either way, I'm going to reload all the shipping stuff when i get home tonight then go ahead and try to process an exchange. Worst case scenario they will charge me ~100 bucks as an out of warranty fee. (due to having the *TAMPERED* logo on the bootloader scren. Although I'm fairly certain they don't check that, they shoudl only check for physical/liquid damage. I have processed many exchanges for rooted customers, who had manufacturer defects.

also another thing i just noticed, my baseband is: 0.15.31501S , but my friends retail version is 0.16.
any way for me to update this?

Early Adopters
I just got the One S myself and I'm a bit forlorn from the lack of available ROMS. Then again when I was in the Apple Ecosystem, there was no ROMS, just tweaks so different environment different timelines I guess.

Not sure if it can help in this case, but this solved my wifi error problem.
I had a "wifi error", my One S coudn't connect any AP.
The problem was a bad permision on the file /data/misc/wifi/wpa_supplicant.conf.
Logcat gave me that :
"Cannot set RW to /data/misc/wifi/wpa_supplicant.conf"
So, using Es Explorer (as root), i changed the chmod of this file to rw-rw-rw and wifi started to work again. (no reboot needed in my case).
Hope this help.

[Q] █ ELEGANCIA™ Rom Series █Sense 3.6|v3.7.6| problems.

Hello Elegancia dev team.
First and foremost, I want to say thanks for a very nice ROM.
After the last 3 or 4 updates a problem has occured. The phone has begun to turn off spontaneously. It is worst when there are approximately 50% power left. It lies on the table and turns off by itself. It also happens, when it is in my pocket. It takes me about 3 attempts to turn it on again. Sometimes I have to take out the battery and when I insert it again, the phone turns on rather quickly and problem has been solved for a couple of days. After 2 days I am back to square one.
I have tried both kernels ie 1.2 and 1.6 HTZ and it is the same problem.
I hope it is something that can be solved.
It's Sense 3.6, which has the problem.
Sorry it is not written in the right thread, but the dev. thread is locked for me.
Does anyone know what to do?
Regards Morten
htc Sensation

doc309 said:
Hello Elegancia dev team.
First and foremost, I want to say thanks for a very nice ROM.
After the last 3 or 4 updates a problem has occured. The phone has begun to turn off spontaneously. It is worst when there are approximately 50% power left. It lies on the table and turns off by itself. It also happens, when it is in my pocket. It takes me about 3 attempts to turn it on again. Sometimes I have to take out the battery and when I insert it again, the phone turns on rather quickly and problem has been solved for a couple of days. After 2 days I am back to square one.
I have tried both kernels ie 1.2 and 1.6 HTZ and it is the same problem.
I hope it is something that can be solved.
It's Sense 3.6, which has the problem.
Sorry it is not written in the right thread, but the dev. thread is locked for me.
Does anyone know what to do?
Regards Morten
htc Sensation
Click to expand...
Click to collapse
Tried only bricked kernel? Maybe you should try faux or sebastianFM. They're working both great
gesendet von meinem Htc Sensation Elegancia Phoenix 3.7.6 Anthrax Kernel

You could try a different ROM to see if that helps. If not, then it's mostly a hardware problem.

Hi Doc!
Did you update just by flashing the newest version over the last each and everytime?
If yes you should try to Superwipe your phone and start fresh without any added applications then those included with the ROM. Superwipe, install and let 10-15 mins for your phone to settle before rebooting and then start configuring your phone.
Do the basics first your email account, not more and let see if your phone will replicate this issue.
You can flash this Superwipe just before flashing a fresh version of Elegancia 3.7.6 Don't forget to verify the MD5 : 6a88266c3c6cb664d305a4e101c566ae
I will try to follow you in the resolution of your problem.

Try different roms with stock kernel. Sounds like hardware to me
Sent from my HTC Sensation 4G using XDA

Lucky Thirteen said:
Hi Doc!
Did you update just by flashing the newest version over the last each and everytime?
If yes you should try to Superwipe your phone and start fresh without any added applications then those included with the ROM. Superwipe, install and let 10-15 mins for your phone to settle before rebooting and then start configuring your phone.
Do the basics first your email account, not more and let see if your phone will replicate this issue.
Don't forget to verify the MD5 : 6a88266c3c6cb664d305a4e101c566ae
I will try to follow you in the resolution of your problem.
Click to expand...
Click to collapse
hi Lucky Thirteen
I have superwiped a couple of times, it remains the same.
I have followed the instructions everytime when flashing a new update. When the phone is updated I let it settle for 10-15 min before rebooting
I'm not sure how or where to check the DM5 no. Can you please tell my how and where?
Regards Morten

doc309 said:
Sorry it is not written in the right thread, but the dev. thread is locked for me.
Click to expand...
Click to collapse
Hi Doc!
Yes you need 10 messages before being able to post in the dev thread.
Which kernel did you tried with your ROM? Bricked? Faux123? SebastianFM? Did you try a stock ROM just to see if the problem is still the same? Have you done a data restoration with Titanium Backup? Or Nandroid? Did you try to install a previous ROM that you know your phone was running great with? Is your phone excessively hot? Or the battery?
What is a MD5 checksum?
A checksum MD5 is not aimed at guaranteeing the provenance of a file or a group of files. His interest is to allow the check on the integrity of recovered data.In fact, no one is sheltered by a disturbance or by a network problem have the effect the corruption of an archive in the course of downloading.
Click to expand...
Click to collapse
When you download a file generally the emitter give to users a MD5 hash like the one in my previous post. Now, to check the MD5 checksum you need a small program like this one . It's real easy and takes generally less than a minute to do, you paste the MD5 provided with the file you just downloaded in the appropriate box, then you Browse to the file you want to check, if the result is a perfect match, your file is not corrupted and good to use. It is valuable habit to take, it can save you to bricked your phone with a corrupted file.

Use this stock rom (rooted) to bring your phone back to life ....Than you can flash any other custom rom
Stock rom HERE
You do know how to flash pg58img ?
EDIT
On second thought, you should also format your SD....
so mate
1.Backup your documents...pic ...music.... on your pc
2.Go to recovery and FORMAT SD
3.Toggle USB...and transfer pg58img on sd
4.Open power menu----> reboot in bootloader
5.Follow the instruction on (phone) screen

If this is still happening after doing the great advice already given to you then you might have a corrupt file on your sd card so if you have another sd card insert it and try to do a clean flash and start from scratch. Do not restore your data (apps and system data) as you may have files that are causing these issues on your device.
When you load your apps back on only put back the apps you have to have on the device and run it for a while and see if the problem goes away, continue this until you have all the apps back on the device.
If you have flashed other ROMs and it is still happening and flashed other kernels but your device is still having these issues the next step is to clear your sd card and start with a completely clean device. If this doesn't fix the problem then you may have a problem with hardware possible the power button.
If you are going to clean (format) your sd card make sure to back-up your pics and vids then after you are done transfer the ROM you are going to flash back onto the sd card and flash away. Problems like these usually can be solved they just take time and energy.
If you need to flash the firmware like dublinz said then after it has flashed and it asked you to reboot take the sd card out put into your laptop and erase the " pg58img " then put the sd card back in and then reboot. If you forget to delete the " pg58img " then the device goes into a boot loop.
Good luck
drew

OP, after I flashed from 4.2 to 4.3 I was having the same issue. After a few charges it stopped doing it. I'm not sure if this will be the case for you but just thought you should know.

doc309 said:
Hello Elegancia dev team.
First and foremost, I want to say thanks for a very nice ROM.
After the last 3 or 4 updates a problem has occured. The phone has begun to turn off spontaneously. It is worst when there are approximately 50% power left. It lies on the table and turns off by itself. It also happens, when it is in my pocket. It takes me about 3 attempts to turn it on again. Sometimes I have to take out the battery and when I insert it again, the phone turns on rather quickly and problem has been solved for a couple of days. After 2 days I am back to square one.
I have tried both kernels ie 1.2 and 1.6 HTZ and it is the same problem.
I hope it is something that can be solved.
It's Sense 3.6, which has the problem.
Sorry it is not written in the right thread, but the dev. thread is locked for me.
Does anyone know what to do?
Regards Morten
htc Sensation
Click to expand...
Click to collapse
Had exactly the same issue ..... tried all possible solutions unsuccesfully. at the end i was forced to chenge rom (ordroid) and now everything is ok

[Q] Bricked xt925 - read-only eMMC ?

Hello,
Since yesterday my phone is crashing about 20-30 seconds after properly booting. I can unlock the phone with my lockscreen pattern, I land on my homescreen but process like Google Play Services goes like "x has stopped working".
On CWM I've erased /system and /data and then reflash a rom (Slimkat or CM), Erasing and flashing process on CWM seems to work as planned but when the phone reboot it's still on Slimkat with all my datas, like if nothing have been done in CWM.
So I've rebooted on the bootloader and tried a "fastboot -w", again the process seems to be ok on my pc but when the phone reboot it is still on this f**ked rom with all my datas, like if fastboot have done nothing.
I've tried to flash an up-to-date CWM, same thing again.
I think the eMMC chip are deeply corrupted, they say any writing on it is ok but in fact they are read-only, which may explain why all the process are crashing after the boot and why flashing seams ok but are useless.
What do you think XDA, andy idea about my problem ? Do you think it's an Hardware issue or what can I do to solve it ?

Why not flashing a stock firmware to go back to STOCK?

joel_sinbad said:
Why not flashing a stock firmware to go back to STOCK?
Click to expand...
Click to collapse
I've tried it with RSDLite but same thing again, everyhing seams ok in RSDLite, the 22 blocks are writed but at the reboot it's still the same Slimkat with my datas.

Ezekiel3 said:
I've tried it with RSDLite but same thing again, everyhing seams ok in RSDLite, the 22 blocks are writed but at the reboot it's still the same Slimkat with my datas.
Click to expand...
Click to collapse
if infact it has gone read only as has happened to some other users, there is no known fix. all known angles have been explored, even with input from a developer.
if you find a fix, post it, it may help others.
most likely, you will need a new phone.

I agree with bwen diord...aint never see anyone recover from that, least not yet.

cmh714 said:
I agree with bwen diord...aint never see anyone recover from that, least not yet.
Click to expand...
Click to collapse
I've just see it's possible to boot from the SD card in that case but I'm to lazy to try it.
Goodbye little RAZR HD, we have covered a lot of mileage together, it's time to leave. :angel:
Anyway thanks for the help XDA