Ok, so i installed one of the custom ROMs available and started using it. However, it always reboots my Desire every time I use my app (sometimes it restarts itself when I'm trying to input simlock code after power up). So maybe (I thought) its a bad flash of the custom ROM. I did full wipe and re-flash it but still no luck.
So i decided to install a different custom ROM (full wipe again before installing) - and it still reboots itself! So now I'm thinking - maybe i did a bad root of my Desire?? What do you think? And should I just re-root again to solve this issue?
NOTE
ROM (before rooting): FroYo OTA (ASIA Region)
Radio: 5.09*
Rooting tool: Unrevoked 3.21
Goldcard?: Yes
Related
Hi there
I think I destroyed my CPU or something ... I used a custom kernel which does OC and UV and it worked without any glitches for about 8 hours.
Then it froze and now I cannot boot any rom.
If there is user data it boots to a frozen lockscreen.
If I do a factory reset it says that the Process system is not responding...
Anybody got an idea?
I just flashed the official SLCD RUU and now it works again ...
I can only run official ROMs
If I root and flash a new one, the same error persists!
anybody any idea?
I cannot really tell HTC to replace my phone, it works with their froyo version :S
but I don't like Sense and now I'm stuck using it ... hate that -.-
Well you rooted with an RC of unrevoked. Could as well have something to do with that. Have you tried custom sense roms? Just to see if they work. Else, i would try the downgrade-to-hboot-0.83-method.. just practice the screenless method with the screen turned on, i managed to do iy in one attempt (H)
Hi,
I (foolishly) tried to upgrade to Telstra Defy (build #JRDNEM_U3_2.26.0) to Pays-Rom ([ROM] Pays-ROM Defy v5.1 Froyo with Ginger feeling [3.4.3-11 based!]). I played with it briefly, couldn't get Clockwork Recovery (defy version) to run, and so wanted to go back to the original Telstra soft (from http://and-developers.com/sbf:defy)
I've used RSD Lite to restore that telstra soft before (from Chinese froyo) and it worked fine. However, when I do it now (after having used RSD to apply the 3.4.3-11 Motorola SBF from this thread ) then I get a blank screen - not even a Moto logo - when I try to boot (like this guy I think).
I reflashed back to the 3.4.3-11 Motorola SBF and the phone is booting happily again. However, I don't really want to be stuck on this - particularly since I can't actually get System Recovery (i.e. Clockwork Recovery) to go so can't seem to install Pays-Rom.
The magic question is: by upgrading to 3.4.3-11 from the Pays-Rom pack, have I removed my ability to go back to my original rom? If not, can anyone think what I may be doing wrong with my downgrade to kill the phone?
Cheers.
Was asking why system recovery was not working - answer was because I had failed to disable USB debugging. Oops. Main problem remains though.
If you flashed a full SBF, then you can't go back to 2.1. It's not bad as you think, since 2.2 in every country is about to be released. When this happens you will need only a nandroid backup...
Sent from my MB525 using Tapatalk
I have done a similar thing, flashed 3.4.2_155-002 and now cant downgrade back to the default Telstra rom. Not to concerned at the moment as I am using Color ROM from here, http://forum.xda-developers.com/showthread.php?t=1021742. It is based on this SBF, 3.4.2-155-2 deblur. Just follow the installation instructions and you should have no trouble. Very fast and deblurred. every thing works fine on my Defy, including clockwork recovery.
Only problem I may have is not being able to downgrade to stock if the phone has to go back to telstra for anything.
Hope this helps.
Cheers.
Hi,
I was recently trying to get CyanogenMod 7 on my Defy. This is what happened...
rooted with z4root
installed ClockworkMod bootloader (using System Recovery apk)
performed a full backup
ran the update.zip for CM7 (from here)
wiped user data + cache (didn't wipe before running update.zip, because I didn't read it properly!)
got stuck in a "M" logo loop
flashed the UK T-Mobile 2.21.1 SBF file (from here) with RSD Lite
ended up with a completely dead Defy! (as described here)
the only ROM i can get to boot at all is the UK Orange 2.3.3 (from here)
i rooted using this method (here)
i've reinstalled the ClockworkMod recovery (using the same System Recovery apk)
when it reboots to the recovery, I just get a black screen
Does anyone know any way of reverting back to the stock T-Mobile ROM (or, ideally, move to CyanogenMod 7?), or does it look like I'm stuck in the Orange ROM?
Any help would be appreciated!
Thanks!
xnoruk said:
Hi,
I was recently trying to get CyanogenMod 7 on my Defy. This is what happened...
rooted with z4root
installed ClockworkMod bootloader (using System Recovery apk)
performed a full backup
ran the update.zip for CM7 (from here)
wiped user data + cache (didn't wipe before running update.zip, because I didn't read it properly!)
got stuck in a "M" logo loop
flashed the UK T-Mobile 2.21.1 SBF file (from here) with RSD Lite
ended up with a completely dead Defy! (as described here)
the only ROM i can get to boot at all is the UK Orange 2.3.3 (from here)
i rooted using this method (here)
i've reinstalled the ClockworkMod recovery (using the same System Recovery apk)
when it reboots to the recovery, I just get a black screen
Does anyone know any way of reverting back to the stock T-Mobile ROM (or, ideally, move to CyanogenMod 7?), or does it look like I'm stuck in the Orange ROM?
Any help would be appreciated!
Thanks!
Click to expand...
Click to collapse
Even for me CM7 Beta 6 didn't worked... well but I am happy to be on Leaked Orange GB 2.3.3 with Blur..
It's definitely an improvement on the original ROM! It supports proxy over wifi (although I haven't tried it yet), although GPS + android Market don't work... but I suppose it's much better than having a bricked phone!
I'm also on the leaked 2.3.3 orange rom and everything seems to work great so far (using it for 1 week now).
I've had a problem with the market too in the beginning. The market needs a google account to work and I couldn't add this account to motoblur from the beginning, where you setup motoblur, so the market wouldn't work for me. I did a wipe data/factory reset, rebooted and this time I could add the google account. Not a single bug, FC, reboot or anything like that so far (ok 1 "bug" to be honest, the signal bars stay empty but the 2g, 3g and hdspa indicators work). I've also used gps navigation without problems and the camera too without the fixes in the forum, but you may want to try the fix from walther79 for gps (http://forum.xda-developers.com/showpost.php?p=14046494&postcount=388).
I haven't tried myself but they say it can be downgraded. If you carefully follow this guide (http://forum.xda-developers.com/showthread.php?t=1054447) and use the sbf mentioned in that post you should be able to install cyanogenmod 7 succesfully. Use this guide for flashing: http://forum.xda-developers.com/showthread.php?t=853674
If you want to wipe data and cache before flashing (suggested) you could use clockwork OR the standard recovery (http://www.hardreset.eu/motorola_defy_hard_reset_soft_reset_en.html). Though you should hold volume up + volume down after you see the droid instead of tapping the touchscreen. There is also a chance clockworkmod will work after you've done a wipe data/factory reset.
I just got an replacement evo with HBoot 6.16.1002 and i rooted it with s-off with revolutionary method. However no matter what rom I flash(CM7,evodeck,sense 3.5 roms), they all freeze up on me after initial setup of google accounts and etc... the only thing that works is the stock rom. Can someone please help?
Are you doing full wipes when flashing?
I do full wipes, i wipe everything except sdcard at least three times before flashing
the bad part is, i tried several roms and they all do the same thing. I even unrooted my phone then rooted again and im still having the same issues. The stock rooted rom works perfectly.
New to the world of Custom ROMs. A week ago I installed CM 13 which took great courage on my part and wanted to share my experience, issues and discuss possible solutions.
My phone had the latest lollipop on it. And McCafee locked. The steps that worked for me where
1) Did a factory reset and bumped into mccafee.
2) Tried download mode but kill switch was enabled.
3) Rebooted the phone to face mccafee, tried 123465 pin which worked.
4) Disengaged McCafee but not before transferring ownership to my email.
5) Tried rooting didnt work with any method.
6) Rolled back to d software version stock lollipop.
7) Rooted with PurpleDrake
8) Replaced with CM recovery didnt work.
9) Replaced with TWRP and rebooted directly to recovery
10) Installed CM and gapps mini. Worked fine. Voila!
Issues:
1) No Custom recovery sticks, whenever I flash with a custom recovery like TWRP or Clockwork. I have to reboot into recovery immediately or the custom recovery is replaced by stock. It happens on every second reboot.
My concern is here if I get stuck into bootloop and dont have a custom recovery I might not have any other option than the stock ROM which does a full reset. How can make TWRP stick forever?
2) After installation of Custom ROM there have been random reboots, I suspect there is something here with phone app or voice. So far the reboots have been when I try to call using fb messenger, appear.in and phone app itself.
Is there a guide that tells me how to track this down?
Can I install a newer Nightly and hope this get fixed?
How can I retain my apps and data when installing a newer nightly? since all guides ask to wipe everything :S
I have a backup of system and data partitions, can I use that with other ROMs.
What ROMs have a better chance of fixing this issue?
Coudnt find Stock M for D850. Why arent those available?
Should an Official ROM be more reliable than CM for this?
3) Bad signal reception so far. It may be a generic g3 issue.
Can I hope that this issue be fixed with a different ROM or updates from Cynogen?
Someone said you may have to flash the radio partition. My question is where can I get a brief understanding of what partitions there are in android and which are risky. Which ones can be replaced, backedup and replaced back.
4) Whenever the phone reboots, it gets stuck into bootloop unless I remove the SIM card. Then I power off and install SIM Card and reboot and it boots fine.
I am already tracking CM changelog for something important. Cant post urls as of now :S