So I flashed cm10 mod on my amaze and had made a backup.somehow the cm10 didn't work as i thought it would so i restored to my previous rom(ics) then I tried to flash the speed butter 9.0 rom and then again i restored back to ICS.then lastly i flashed Aokp rom but it kept saying ""the process com.android.phone has stopped" so I restored it to my stock rom(ICS).When I rebooted,it got stuck at htc t mobile android screen. Please help
First off are you s-on or off? Also, what recovery are you using..
4EXT and S on.Apparently I have managed to save my device. What happened was that,I relocked the boot loader,downloaded the latest stock ruu and flashed it through the HTC amaze tool kit. All of the roms which I tried had problems,cm 10 would freeze a bit if I would swipe on the home screen,speed rom 9,wouldn't show me contacts when I would type a name and AOKP jelly bean rom kept giving me the "the process com.android.phone has stopped" error" . I don't think I will ever try flashing a custom rom now. But I wonder why it got stuck at boot screen when I restored the stock ICS rom in the end?. I thank you for your reply.
wahid beg said:
4EXT and S on.Apparently I have managed to save my device. What happened was that,I relocked the boot loader,downloaded the latest stock ruu and flashed it through the HTC amaze tool kit. All of the roms which I tried had problems,cm 10 would freeze a bit if I would swipe on the home screen,speed rom 9,wouldn't show me contacts when I would type a name and AOKP jelly bean rom kept giving me the "the process com.android.phone has stopped" error" . I don't think I will ever try flashing a custom rom now. But I wonder why it got stuck at boot screen when I restored the stock ICS rom in the end?. I thank you for your reply.
Click to expand...
Click to collapse
I think the problem was that when you flashed cm10 and aokp etc, 4ext flashed the cm kernel (obviously). But what 4ext is unable to do is restore a kernel (boot.img) when you are simply restoring a backup. Therefore you still had the cm kernel which isnt compatible with your stock rom you have backed up.
I think if you had just found a download for the stock ics kernel and flashed it you would have been fine. Or of course simply flashing the RUU will usually always fix anything too
Related
Hi, I am in need of help... I decided to give CM 10.1.3rc2 a try and after a day or so decided i wanted to go back. In order to flash CM 10 I had to use Flash GUI to flask the CM kernel. So when I decided to switch back to stock I again used Flash GUI to flash the kernel for the stock rom, and then flashed the rom, which appeared as part of the install process to again attempt to flash the kernel, and immediately went into boot loop. So I decided then to just try to restore my NAND backup. It appeared to restore fine, except I have no touchscreen functionality, so after it boots I can't do anything.
What went wrong here, and how do I fix it from here?
Truly appreciate any help I can get...
Thanks.
forgot to mention, I am S-on...
Click the link in my sig, and read the section about halfway down regarding the latest OTA update and the touch panel driver. You need to flash a 3.16 software version ROM, or a AOSP ROM with the newer 3.4 kernel.
Hi there,
I downloaded the latest MIUI ROM available in the Development sectionand installed when i was on ICS, but it only booted and the BOOT.iMG was not flashed by fastboot because the hboot version was not sufficient for the MIUI jelly bean ROM. My phone was rooted earlier and i was running Sense Revolution 5 but after it was degrading i decided on installing your ROM.
Now, after long hours I updated the stock version via the OTA so the hboot version has now increased. But the problem now I am facing is that after flashing your ROM [After doing a factory reset which consists of Wiping cache,data and dalvik cache] and flashing the boot.img separately is that my Desire X is booting into stock jelly bean ROM even though i have wiped everything. I have tried this thing like for 2-3 times and my bootloader shows UNLOCKED. The phone starts like it has come from factory. Also during 3rd time i noticed that I got a message that Xiaomi Framework has closed. There are some apps of MIUI installed like Weather and gallery etc out of which few work and few don't. I did not get any kind of errors while installing your ROM as well. I have verified the md5 as well but it is not working.
also when I boot into bootloader, i get a green message
SD CARD CHECKING
PM66diag.zip no or wrong image
something like that.
Could you guys please help me out for this one?
Regards,
Pranav
Blueelvis_RoXXX said:
Hi there,
I downloaded the latest MIUI ROM available in the Development sectionand installed when i was on ICS, but it only booted and the BOOT.iMG was not flashed by fastboot because the hboot version was not sufficient for the MIUI jelly bean ROM. My phone was rooted earlier and i was running Sense Revolution 5 but after it was degrading i decided on installing your ROM.
Now, after long hours I updated the stock version via the OTA so the hboot version has now increased. But the problem now I am facing is that after flashing your ROM [After doing a factory reset which consists of Wiping cache,data and dalvik cache] and flashing the boot.img separately is that my Desire X is booting into stock jelly bean ROM even though i have wiped everything. I have tried this thing like for 2-3 times and my bootloader shows UNLOCKED. The phone starts like it has come from factory. Also during 3rd time i noticed that I got a message that Xiaomi Framework has closed. There are some apps of MIUI installed like Weather and gallery etc out of which few work and few don't. I did not get any kind of errors while installing your ROM as well. I have verified the md5 as well but it is not working.
also when I boot into bootloader, i get a green message
SD CARD CHECKING
PM66diag.zip no or wrong image
something like that.
Could you guys please help me out for this one?
Regards,
Pranav
Click to expand...
Click to collapse
Install a recovery meant for the JB hboot
GtrCraft said:
Install a recovery meant for the JB hboot
Click to expand...
Click to collapse
Thanks a lot dude. I tried the beta recovery from TWRP and it got flashed finally
Thanks and sorry for being such a noob.
Ok so i previously flashed to both 4.2 and 4.3 JB roms, I then flashed to the newer kitkat cm11 rom and everything worked fine for about 3 days and all of a sudden google apps stopped accepting mobile data and only wifi would work. I then attempted to flash back to 4.3.1 and got the build prop error which is where i am now stuck. I have successfully got back to EH03 but anytime i follow the guide to flash to a JB rom i get the build prop error or if i remove that check from the zip it begins installing the rom and resets 3 seconds later to get stuck in bootloop only showing kernal and "Samsung CWM" screen. What am i missing here? thanks in advance.
I had this same problem. I just flashed the a 4.3 devil kernel from hhp's thread in the general section, rebooted to recovery, then flashed back to a 4.3 ROM.
Sent from my SCH-I500 using xda app-developers app
m3fletcher3 said:
Ok so i previously flashed to both 4.2 and 4.3 JB roms, I then flashed to the newer kitkat cm11 rom and everything worked fine for about 3 days and all of a sudden google apps stopped accepting mobile data and only wifi would work. I then attempted to flash back to 4.3.1 and got the build prop error which is where i am now stuck. I have successfully got back to EH03 but anytime i follow the guide to flash to a JB rom i get the build prop error or if i remove that check from the zip it begins installing the rom and resets 3 seconds later to get stuck in bootloop only showing kernal and "Samsung CWM" screen. What am i missing here? thanks in advance.
Click to expand...
Click to collapse
I always flash the sc3 rom before flashing a jb rom. Always works for me. If I don't flash, then I have problems depending on which jb rom i try to flash.
every rom i try and flash just gets stuck on the htc white screen the only one i have had work is a stock rom anyone help im on cwm based recovery v5.0.2.7 im s-on this is the only rom that works http://forum.xda-developers.com/showthread.php?t=2477549 and im a t mobile user and when i do get this one to work the wifi just says error
stuck white screen
5cruff said:
every rom i try and flash just gets stuck on the htc white screen the only one i have had work is a stock rom anyone help im on cwm based recovery v5.0.2.7 im s-on this is the only rom that works http://forum.xda-developers.com/showthread.php?t=2477549 and im a t mobile user and when i do get this one to work the wifi just says error
Click to expand...
Click to collapse
Use 4EXT recovery and enable the smart flash--your rom's boot images aren't flashing properly with s-on, and 4EXT works around that by pre-flashing the boot image. If you are using ICS based rom's, be sure to upgrade your phone to ICS FIRST, using the RUU.
You're doing well though--you're part way there.
I have installed custom rom cyanogenmod cm-11-20140806-NIGHTLY-n7100 and It works fine and after that I wished to go back to my stock rom which is Android Kitkat 4.4.4 , So I took a backup of my stock rom and moved to computer's hard disk
After I restored using clockworkmod recovery version 6.0.4.3 I restored my old stock rom .. but the problem is when i unlock from lock screen this message "unfortunately com.google.process.gapps has stopped working " keeps popping and I cannot get rid of it..
Now I again installed custom rom and I think the gapps version and stock rom android version is not syncing...please help me to recover my stock rom
mismatched versions maybe
Are you hard set on installing your recovery image?
You could download the correct stock firmware and gapps for your phone by searching google (i would link something to you but im new)
Take a look here: http://forum.xda-developers.com/showthread.php?t=1896696
---------- Post added at 06:17 AM ---------- Previous post was at 06:09 AM ----------
Sailor spinach said:
Are you hard set on installing your recovery image?
You could download the correct stock firmware and gapps for your phone by searching google (i would link something to you but im new)
Take a look here: http://forum.xda-developers.com/showthread.php?t=1896696
Click to expand...
Click to collapse
Scroll down to the first section and it will send you to sammobile to download your stock firmware.
At sammobile click Firmware, then to the right side and down a bit there is a "search device here" box. Enter n7100 and you should find when you need!
Hope this helps!!
vignesh1990 said:
I have installed custom rom cyanogenmod cm-11-20140806-NIGHTLY-n7100 and It works fine and after that I wished to go back to my stock rom which is Android Kitkat 4.4.4 , So I took a backup of my stock rom and moved to computer's hard disk
After I restored using clockworkmod recovery version 6.0.4.3 I restored my old stock rom .. but the problem is when i unlock from lock screen this message "unfortunately com.google.process.gapps has stopped working " keeps popping and I cannot get rid of it..
Now I again installed custom rom and I think the gapps version and stock rom android version is not syncing...please help me to recover my stock rom
Click to expand...
Click to collapse
Well, before flashing the stock ROM try going to the application manager and try clearing the cache and the data stored by the Google Play services app. and if that still doesn't helps you out then you can move forward with flashing the stock ROM over your device.
vignesh1990 said:
I have installed custom rom cyanogenmod cm-11-20140806-NIGHTLY-n7100 and It works fine and after that I wished to go back to my stock rom which is Android Kitkat 4.4.4 , So I took a backup of my stock rom and moved to computer's hard disk
After I restored using clockworkmod recovery version 6.0.4.3 I restored my old stock rom .. but the problem is when i unlock from lock screen this message "unfortunately com.google.process.gapps has stopped working " keeps popping and I cannot get rid of it..
Now I again installed custom rom and I think the gapps version and stock rom android version is not syncing...please help me to recover my stock rom
Click to expand...
Click to collapse
m facing the same issue no fix