Related
While I'm thinking about it, I wanted to ask a question. I had to revert back to the stock ROM, and went to re-add root and Safestrap 2.10. All went well with the install, but when I went to enable the Safe System, and I rebooted, the phone did the POST (Motorola symbol), got to the SafeStrap splash, then the screen went blank. None of the keys would do anything, and the only way I could make anything happen, was to pull the battery. I had to go back into Safestrap, and disable it again. Anyone else experience this?
-Roger
cpnbnanamn said:
While I'm thinking about it, I wanted to ask a question. I had to revert back to the stock ROM, and went to re-add root and Safestrap 2.10. All went well with the install, but when I went to enable the Safe System, and I rebooted, the phone did the POST (Motorola symbol), got to the SafeStrap splash, then the screen went blank. None of the keys would do anything, and the only way I could make anything happen, was to pull the battery. I had to go back into Safestrap, and disable it again. Anyone else experience this?
-Roger
Click to expand...
Click to collapse
Did you flash something in safe mode before rebooting?
Sent from my XT860 using xda premium
Endoroid said:
Did you flash something in safe mode before rebooting?
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
No, just enabled it, allowed it to do it's backup, then rebooted. Thought for sure I was going to have to reload SBF again.
-Roger
cpnbnanamn said:
No, just enabled it, allowed it to do it's backup, then rebooted. Thought for sure I was going to have to reload SBF again.
-Roger
Click to expand...
Click to collapse
The first time you enable safe mode you need to flash a rom. You tried to boot... Nothing, thus the black screen
Sent from my XT860 using xda premium
Endoroid said:
The first time you enable safe mode you need to flash a rom. You tried to boot... Nothing, thus the black screen
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
Ahh.. that makes sense. Do we have any idea when a more stable ROM is coming out for the D3?
cpnbnanamn said:
Ahh.. that makes sense. Do we have any idea when a more stable ROM is coming out for the D3?
Click to expand...
Click to collapse
All gb roms are stable. It's just ics that has issues, however the kexec cm9 currently in alpha will be stable, likely in the next few weeks
Sent from my XT860 using xda premium
Endoroid said:
All gb roms are stable. It's just ics that has issues, however the kexec cm9 currently in alpha will be stable, likely in the next few weeks
Sent from my XT860 using xda premium
Click to expand...
Click to collapse
The kexec ICS from 8/6 is surprising stable for me. I've been running it for nearly a week and while I've had some reboots and a couple of freezes that required a battery pull, it's run better than I expected.
I have had the problem with leaving bluetooth on and answering a call without a headset - no audio until BT turned off.
Also, as advertised, no camera. Another note, the car dock USB audio doesn't work.
I've even scripted a mount to keep the Play Music directory on the external SD card and mass storage mount on the computer works better than stock with the mount in place. Internal sd doesn't mount though.
Sent from my XT862 using Tapatalk 2
Hey hey hey....
i hav an captivate from at&t and its works perfectly fith the "stocks" firmwares, like 2.3.3, 2.3.4, 2.3.5, but when i flash something like CM10 or X-bean, salty etc, half times screen fault,
what can i do? i really want ics, or JB, i hate GB and froyo ....
Thanks!
joshua3001 said:
Hey hey hey....
i hav an captivate from at&t and its works perfectly fith the "stocks" firmwares, like 2.3.3, 2.3.4, 2.3.5, but when i flash something like CM10 or X-bean, salty etc, half times screen fault,
what can i do? i really want ics, or JB, i hate GB and froyo ....
Thanks!
Click to expand...
Click to collapse
We need more info.. What's your flashing process? Do you have gb bootloaders?
What exactly is the problem with the screen? Touch doesn't work? It flickers?
Sent from my SGH-I897 using xda app-developers app
First of all, forgive my English, im from Costa Rica
Right now, I have Gingerbread 2.3.5, baseband i897uckk4 with GB bootloaders, rooted with I897UCKF1-AutoRoot-DesignGears and CornKernel_UCKK4_v706 (sorry if I do not give good information, but I'm new at this ...), I can install any firmware 2.3.5 and down, but when I try to install a custom firmware, half of the screen fails to respond and other times if not, try many custom firmwares like: X-Bean 3.0, Cyanogenmod 10,9,7 stables, nightlies, AOKP, AOSP, MIUI (by flashing in CWM), and none served me perfectly, and I really want to at least have ICS, and if you could, JB, something I noticed is that whenever I installed a custom firmware, my baseband changed to "I9000UGKG3" when normally with stock firmware, was "I897UCKK4"
I hope it can fix it , thanks to everyone at XDA,
Greetings from Costa Rica,
BWolf56 said:
We need more info.. What's your flashing process? Do you have gb bootloaders?
What exactly is the problem with the screen? Touch doesn't work? It flickers?
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
First of all, forgive my English, im from Costa Rica
Right now, I have Gingerbread 2.3.5, baseband i897uckk4 with GB bootloaders, rooted with I897UCKF1-AutoRoot-DesignGears and CornKernel_UCKK4_v706 (sorry if I do not give good information, but I'm new at this ...), I can install any firmware 2.3.5 and down, but when I try to install a custom firmware, half of the screen fails to respond and other times if not, try many custom firmwares like: X-Bean 3.0, Cyanogenmod 10,9,7 stables, nightlies, AOKP, AOSP, MIUI (by flashing in CWM), and none served me perfectly, and I really want to at least have ICS, and if you could, JB, something I noticed is that whenever I installed a custom firmware, my baseband changed to "I9000UGKG3" when normally with stock firmware, was "I897UCKK4"
I hope it can fix it , thanks to everyone at XDA,
Greetings from Costa Rica,
joshua3001 said:
First of all, forgive my English, im from Costa Rica
Right now, I have Gingerbread 2.3.5, baseband i897uckk4 with GB bootloaders, rooted with I897UCKF1-AutoRoot-DesignGears and CornKernel_UCKK4_v706 (sorry if I do not give good information, but I'm new at this ...), I can install any firmware 2.3.5 and down, but when I try to install a custom firmware, half of the screen fails to respond and other times if not, try many custom firmwares like: X-Bean 3.0, Cyanogenmod 10,9,7 stables, nightlies, AOKP, AOSP, MIUI (by flashing in CWM), and none served me perfectly, and I really want to at least have ICS, and if you could, JB, something I noticed is that whenever I installed a custom firmware, my baseband changed to "I9000UGKG3" when normally with stock firmware, was "I897UCKK4"
I hope it can fix it , thanks to everyone at XDA,
Greetings from Costa Rica,
Click to expand...
Click to collapse
The I9000UKG3 is your modem(baseband), not your ROM (firmware), so don't worry about that. As long as you have signal, you're fine.
Before flashing a Jb ROM, do you factory reset, clear cache/dalvik? Is the screen problem right at the start? Do you restore your apps?
Do you have the I9000 bootloaders or the I897 bootloaders?
Hoy do i now what bootloaders i have ?
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
joshua3001 said:
Hoy do i now what bootloaders i have ?
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
When you boot your phone, do you see I897 or I9000?
Now do i now what bootloaders do i have?
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
BWolf56 said:
When you boot your phone, do you see I897 or I9000?
Click to expand...
Click to collapse
It says at&t and a 3g animation and then galaxy s animation
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
joshua3001 said:
It says at&t and a 3g animation and then galaxy s animation
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
Isn't there a black screen before the white AT&T screen? It would say SGH-I897 or SGH-I9000
BWolf56 said:
Isn't there a black screen before the white AT&T screen? It would say SGH-I897 or SGH-I9000
Click to expand...
Click to collapse
No wolf, it just boot directly to the white at&t logo
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
joshua3001 said:
No wolf, it just boot directly to the white at&t logo
Sent from my SAMSUNG-SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
Ok, We'll start from the beginning then, You can get in download mode right?
Grab Odin KK4 without bootloaders, Corn kernel with Odin 1.85 and put the ROM (and Gapps) you wanna flash in the root of your internal SD. Flash KK4, boot up and make sure everything is fine. Once that's done, get back in download and flash Corn kernel.
From there, you can flash the ROM and the Gapps that go with it.
I believe you went through those steps already but hopefully we can find what's wrong by re-trying/reproducing the problem. Oh and don't restore any apps before trying it.
If that doesn't work, I'm thinking you might have the wrong Gapps or wrong bootloaders but first time I hear of a screen that doesn't work on JB but does on GB.
EDIT:
I just went through the thread to see that you already have KK4 and Corn on your phone. You don't need DesignGear to root, you can go in Corn's recovery to root your phone. Now, after re-reading, you said that sometimes it's iresponsive, what exactly do you mean by that? it takes a while to register your touch? locks up and you get no response for a few seconds?
Usually that's from lack of free ram. So a app sucking it all up. Have you tried JB (with the right Gapps) without restoring your apps?
PS.: You shouldn't restore your app with TiBu coming from GB, you can restore their data but should fresh download the apps from the market.
BWolf56 said:
Ok, We'll start from the beginning then, You can get in download mode right?
Grab Odin KK4 without bootloaders, Corn kernel with Odin 1.85 and put the ROM (and Gapps) you wanna flash in the root of your internal SD. Flash KK4, boot up and make sure everything is fine. Once that's done, get back in download and flash Corn kernel.
From there, you can flash the ROM and the Gapps that go with it.
I believe you went through those steps already but hopefully we can find what's wrong by re-trying/reproducing the problem. Oh and don't restore any apps before trying it.
If that doesn't work, I'm thinking you might have the wrong Gapps or wrong bootloaders but first time I hear of a screen that doesn't work on JB but does on GB.
EDIT:
I just went through the thread to see that you already have KK4 and Corn on your phone. You don't need DesignGear to root, you can go in Corn's recovery to root your phone. Now, after re-reading, you said that sometimes it's iresponsive, what exactly do you mean by that? it takes a while to register your touch? locks up and you get no response for a few seconds?
Usually that's from lack of free ram. So a app sucking it all up. Have you tried JB (with the right Gapps) without restoring your apps?
PS.: You shouldn't restore your app with TiBu coming from GB, you can restore their data but should fresh download the apps from the market.
Click to expand...
Click to collapse
All right, im gonna flash aokp_captivatemtd_jb_milestone-1.zip with gapps-jb-20121011-signed.zip, so, Turn off phone, enter cwm, wipe data/factory reset, wipe cache partition, wipe dalvik cache, flash aokp, flash gapps, fix permission and thats it right?
EDIT: I dont want to restore apps, i just want jb or ics, without that screen fail, the problem is that when i touch, it doesnt respond at all, but then 5 min later its works and then fail again, but just with the left side of the sceern....
joshua3001 said:
All right, im gonna flash aokp_captivatemtd_jb_milestone-1.zip with gapps-jb-20121011-signed.zip, so, Turn off phone, enter cwm, wipe data/factory reset, wipe cache partition, wipe dalvik cache, flash aokp, flash gapps, fix permission and thats it right?
EDIT: I dont want to restore apps, i just want jb or ics, without that screen fail, the problem is that when i touch, it doesnt respond at all, but then 5 min later its works and then fail again, but just with the left side of the sceern....
Click to expand...
Click to collapse
Sounds good. Quite often you don't need to fix permission, I never had to do it.
If screen fails again, I'm starting to think it might be a hardware issue.
Sent from my SGH-I897 using xda app-developers app
BWolf56 said:
Ok, We'll start from the beginning then, You can get in download mode right?
Grab Odin KK4 without bootloaders, Corn kernel with Odin 1.85 and put the ROM (and Gapps) you wanna flash in the root of your internal SD. Flash KK4, boot up and make sure everything is fine. Once that's done, get back in download and flash Corn kernel.
From there, you can flash the ROM and the Gapps that go with it.
I believe you went through those steps already but hopefully we can find what's wrong by re-trying/reproducing the problem. Oh and don't restore any apps before trying it.
If that doesn't work, I'm thinking you might have the wrong Gapps or wrong bootloaders but first time I hear of a screen that doesn't work on JB but does on GB.
EDIT:
I just went through the thread to see that you already have KK4 and Corn on your phone. You don't need DesignGear to root, you can go in Corn's recovery to root your phone. Now, after re-reading, you said that sometimes it's iresponsive, what exactly do you mean by that? it takes a while to register your touch? locks up and you get no response for a few seconds?
Usually that's from lack of free ram. So a app sucking it all up. Have you tried JB (with the right Gapps) without restoring your apps?
PS.: You shouldn't restore your app with TiBu coming from GB, you can restore their data but should fresh download the apps from the market.
Click to expand...
Click to collapse
BWolf56 said:
Sounds good. Quite often you don't need to fix permission, I never had to do it.
If screen fails again, I'm starting to think it might be a hardware issue.
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
All right, i just flash the rom an gapps with this process...: wipe data/factory reset, wipe cache, dalvik, flash rom, gapps, and thats it....i will tell you how it goes...
Edit, im not gonna instal or update any app, just let it like that and see what happend....so now the boot process is, at&t white logo. the pink horse of aokp (XD), and thats it, no i897 or i9000 bootloaders, and when you say ¨it may be a hardware issue¨ what did you mean with that?
joshua3001 said:
All right, i just flash the rom an gapps with this process...: wipe data/factory reset, wipe cache, dalvik, flash rom, gapps, and thats it....i will tell you how it goes...
Edit, im not gonna instal or update any app, just let it like that and see what happend....so now the boot process is, at&t white logo. the pink horse of aokp (XD), and thats it, no i897 or i9000 bootloaders, and when you say ¨it may be a hardware issue¨ what did you mean with that?
Click to expand...
Click to collapse
Usually when you boot the phone, it shows SGH-897 but it doesn't matter, I could be wrong.
As for the hardware issue, just like some Sleep of Death (SoD) issue, it's something that a software can't fix, it's something broken within the phone (hardware). I don't know if it's the case here but it's always a possibility, especially if the phone was dropped before, the screen connector might need to be pushed back into place.
BWolf56 said:
Usually when you boot the phone, it shows SGH-897 but it doesn't matter, I could be wrong.
As for the hardware issue, just like some Sleep of Death (SoD) issue, it's something that a software can't fix, it's something broken within the phone (hardware). I don't know if it's the case here but it's always a possibility, especially if the phone was dropped before, the screen connector might need to be pushed back into place.
Click to expand...
Click to collapse
But why when I have the stock firmware that doesn't happend?
Sent from my SGH-I897 using xda app-developers app
BWolf56 said:
Usually when you boot the phone, it shows SGH-897 but it doesn't matter, I could be wrong.
As for the hardware issue, just like some Sleep of Death (SoD) issue, it's something that a software can't fix, it's something broken within the phone (hardware). I don't know if it's the case here but it's always a possibility, especially if the phone was dropped before, the screen connector might need to be pushed back into place.
Click to expand...
Click to collapse
Oh, and also, can I download I897 bootloader? and if I could, is gonna make any change?
Sent from my SGH-I897 using xda app-developers app
joshua3001 said:
Oh, and also, can I download I897 bootloader? and if I could, is gonna make any change?
Sent from my SGH-I897 using xda app-developers app
Click to expand...
Click to collapse
You can get Odin KK4 with bootloaders. There's a risk of bricking your phone when you flash bootloaders though. There are needed to be on ROMs that are GB and up but I think you already have them.
As for the hardware thing, like I mentioned before, it could be like SoDs, where the phone will randomly shut off when you're using a ISC/JB ROM.
BWolf56 said:
You can get Odin KK4 with bootloaders. There's a risk of bricking your phone when you flash bootloaders though. There are needed to be on ROMs that are GB and up but I think you already have them.
As for the hardware thing, like I mentioned before, it could be like SoDs, where the phone will randomly shut off when you're using a ISC/JB ROM.
Click to expand...
Click to collapse
Hi wolf,
First of all let me thank you for all the help you gave me, let me tell you that if it was a hardware problem, then, as here in the office sometimes bring several of these phones, i change it for one XD and now it Works , im runnign aokp 4.1.2 Milestone 1 .... now, if not too much trouble, as last favor I say, you know if JB 4.2.1 roms for the captivate that are for everyday use?
really, really thank you......
Hello,
I have gotten the stock ICS rom from samfirmware.com, Installed using ODIN and it all went green.
However, after restart the touch screen is not working !
I have tried the following:
1. First the Default (XXX) ICS rom
2. Second, the Actual ATT ICS rom
3. Flashed CWM and it is working
4. Then tried AOKP unofficial rom, not starting
No luck so far, any help is much appreciated please.
The touch screen was working after step 3?
Sent from my SAMSUNG-SGH-I727 using xda premium
wamaOnline said:
Hello,
I have gotten the stock ICS rom from samfirmware.com, Installed using ODIN and it all went green.
However, after restart the touch screen is not working !
I have tried the following:
1. First the Default (XXX) ICS rom
2. Second, the Actual ATT ICS rom
3. Flashed CWM and it is working
4. Then tried AOKP unofficial rom, not starting
No luck so far, any help is much appreciated please.
Click to expand...
Click to collapse
Do you know what rom you flashed from Sam mobile?
Sent from my SAMSUNG-SGH-I957
jd1639 said:
Do you know what rom you flashed from Sam mobile?
Sent from my SAMSUNG-SGH-I957
Click to expand...
Click to collapse
First was this one sammobile (dot) com /firmware/?page=3&model=SGH-I957&pcode=XXX&os=1&type=3#firmware[/url]
Then when it didn't work, tried this one
sammobile (dot) com /firmware/?page=3&model=SGH-I957&pcode=ATT&os=1&type=3#firmware
Sorry for the strange URL format, but seems as anew member I don't get to add URLs yet
orlandoxpolice said:
The touch screen was working after step 3?
Sent from my SAMSUNG-SGH-I727 using xda premium
Click to expand...
Click to collapse
Sorry, I meant the cwm recovery was flashed correctly and functioning
Btwi tried the fix permissions suggestion from the similar thread but no luck
What version of odin did you use? The roms look ok. If you didn't use ver 1.85 download that and re flash the Rom.
Sent from my SAMSUNG-SGH-I957
jd1639 said:
What version of odin did you use? The roms look ok. If you didn't use ver 1.85 download that and re flash the Rom.
Sent from my SAMSUNG-SGH-I957
Click to expand...
Click to collapse
It is the Odin version I have used,
One more note now, am not sure if that is normal if not.but after the latest flash ( preceded by a data wipe and format ) I can now see zip file I have placed on sdcard but can't access them for flashing and/or ad new zip files from pc
In cwm do a factory reset, wipe and format system and data and then boot. I'm hoping that will solve the problem.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
In cwm do a factory reset, wipe and format system and data and then boot. I'm hoping that will solve the problem.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
Tried,booted, "SAMASUNG"screen only ( as expected sicne i formatted the system ), then re-flushed the ATT ICS and same output
Am trying to get a new ROM flashed, but when the device powers up [ without me going through the wizard ], i can't write anything to SD from my PC.
Any info around here about flashing CM or AOKP using ODIN for this I957 ?
Not with Odin that I'm aware of. All are zip files and would go thru cwm. If you get only to the Samsung logo, my experience has been a factory reset usually gets you past that and if that doesn't work flashing the stock rom with Odin does. And I'd flash the honeycomb rom and bring it back to they way I bought it, then upgrade to ics
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
Not with Odin that I'm aware of. All are zip files and would go thru cwm. If you get only to the Samsung logo, my experience has been a factory reset usually gets you past that and if that doesn't work flashing the stock rom with Odin does. And I'd flash the honeycomb rom and bring it back to they way I bought it, then upgrade to ics
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
Tried the honeycomb step, still same problem
As for Booting to samsung screen .. i did format /system as suggested, so there will be no system to boot to i think
I'm at a loss, you've tried everything that has gotten me beyond the boot screen.
Anyone else have any ideas?
Sent from my SGH-I727
wamaOnline said:
Tried the honeycomb step, still same problem
As for Booting to samsung screen .. i did format /system as suggested, so there will be no system to boot to i think
Click to expand...
Click to collapse
I should mention something that has gotten me worried, i flashed a TWRP recovery to check if the touch would work there, but it didn't.
Not sure if i should be worried about HW now, or try another TWRP for instance? Or perhaps TWRP shares another flawed tab wide configuration with the Android image ?
It's not twrp, I use it on my tab and it Works fine. If you were the only one who has this problem I'd say hardware for sure. But at least one other person has the same problem after updating to ics. It seems like there something with the firmware interfacing with the touch screen.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
jd1639 said:
It's not twrp, I use it on my tab and it Works fine. If you were the only one who has this problem I'd say hardware for sure. But at least one other person has the same problem after updating to ics. It seems like there something with the firmware interfacing with the touch screen.
Sent from my SAMSUNG-SGH-I957 using xda app-developers app
Click to expand...
Click to collapse
Then why is it still borked when reverting to hc?
Sent from my SAMSUNG-SGH-I727 using xda premium
Good question. One of the guys couldn't get the touch screen to work in twrp either. It sounds like a hardware issue but to have a few guys have the same problem after installing ics? I don't know? Something's doing it which I can't figure out
jd1639 said:
Good question. One of the guys couldn't get the touch screen to work in twrp either. It sounds like a hardware issue but to have a few guys have the same problem after installing ics? I don't know? Something's doing it which I can't figure out
Click to expand...
Click to collapse
yea i dont get how a rom flash could cause a hardware issue
orlandoxpolice said:
yea i dont get how a rom flash could cause a hardware issue
Click to expand...
Click to collapse
Think the other colleague did say he found someone elsewhere who resolved the problem by reverting to an older backup he had, which gives me hope that this is no hw issue
And this was my first time to flash any ROM without a backup first, thought a stock update would be fine !!
Can I use adb for instance to verify if it was a hardware issue,if so then any help is appreciated
wamaOnline said:
Think the other colleague did say he found someone elsewhere who resolved the problem by reverting to an older backup he had, which gives me hope that this is no hw issue
And this was my first time to flash any ROM without a backup first, thought a stock update would be fine !!
Can I use adb for instance to verify if it was a hardware issue,if so then any help is appreciated
Click to expand...
Click to collapse
Got it Reassembled and cleaned it and it worked
same prob, touchscreen not responding
wamaOnline said:
Got it Reassembled and cleaned it and it worked
Click to expand...
Click to collapse
I'm having this issue of the touchscreen not responding on my s2 now
You say you got it reassembled? What did you have to do to repair it
any help greatly appreciated
I have JB 4.1.2 and cwm 9.1 flashed
after reboot screen comes on but won't respond to touch, I can only access download and recobvery screens
I also have the phone not showing on computer when usb attached but am loading rom etc to ext sd card first and installing them from cwm
Got the maintenance center to disassemble it, clean the pins and reconnect the screen and then it worked
Sent from my LT26ii using xda app-developers app
I was simply curious and discovered that this RAZR HD ROM works (almost perfectly!) on my AHD running ICS. I assume this should fully work for JB, because it's made for that kernel. So if you're on JB, please try it and let us know.
>> Use Safestrap SLOT-1 to flash Epinter's rom: http://www.linuxmobile.org/razrhd/cm10
If your WIFI won't turn on, replace the drivers with the correct files from here: http://forum.xda-developers.com/showthread.php?t=2107662
Developers/Coders: How do we get the sensors working on ICS?? I've tried like mad to replace with stock-ics drivers, but I really don't know what I'm doing
Enjoy the pull-down toggles & customizable soft-keys!!
[edit: attached my screenshots; everything seems to work on ICS except the sensors & gps]
no go on JB 4.1.1, stuck in boot animation for 10mins twice.
progrockguy said:
I was simply curious and discovered that this RAZR HD ROM works (almost perfectly!) on my AHD running ICS. I assume this should fully work for JB, because it's made for that kernel. So if you're on JB, please try it and let us know.
Click to expand...
Click to collapse
What do you mean by almost perfectly... what was and was not working? Im still running on ICS and would love to get cm10 on my device.
JB 4.1.1 it boots for me but I get Encryption Unsuccessful. No go.
Sent from my MB886 using xda app-developers app
I can get the JB rom to boot, but i get a message about phone not successfully encrypted and requires a reset, wiping data now to see if it will work.
(installing to rom slot using safestrap)
coldfear00 said:
no go on JB 4.1.1, stuck in boot animation for 10mins twice.
Click to expand...
Click to collapse
Can you try deleting slot1 from Boot Options and creating a new one from scratch, wipe, then re-flash (and cross your fingers).
EcHoFiiVe said:
JB 4.1.1 it boots for me but I get Encryption Unsuccessful. No go.
Click to expand...
Click to collapse
Oneofonex1 said:
I can get the JB rom to boot, but i get a message about phone not successfully encrypted and requires a reset, wiping data now to see if it will work.
Click to expand...
Click to collapse
Is this the error message you guys are talking about? Also are you flashing to a freshly wiped (cache, dalvik, sys, factory data) slot or over an existing rom (i.e. dirty and not recommended)?
forum.xda-developers.com/showthread.php?t=1580902
If that's the bug then there is a fix for it, but I didn't encounter that at all on ics.
Clean flash. I have already seen that guide but we don't have partitioning in SS.
Sent from my MB886 using xda app-developers app
Damn this encryption bug. I did not see that coming due to simply being on JB.
I saw another thread say that removing the microsd and rebooting a couple of times might get you past the error message. This isn't ideal and reinserting would probably bring it back, but if it works we could then determine if all the sensors work on JB.
Nothing works on my side either I tried reboots w/o SD and tried booting off another ROM and then installing no-go
Sent from my MB886 using xda app-developers app
progrockguy said:
Is this the error message you guys are talking about? Also are you flashing to a freshly wiped (cache, dalvik, sys, factory data) slot or over an existing rom (i.e. dirty and not recommended)?
forum.xda-developers.com/showthread.php?t=1580902
If that's the bug then there is a fix for it, but I didn't encounter that at all on ics.
Click to expand...
Click to collapse
yes, exact error message but, will the fix from work on our phones (i'm a bit skeptical and cant be the 1st to jump and find out).
Oneofonex1 said:
yes, exact error message but, will the fix from work on our phones (i'm a bit skeptical and cant be the 1st to jump and find out).
Click to expand...
Click to collapse
Yeah that solution seems impractical. I think a simpler solution would be to work around the internal "sdcard." I'd remove anything that involves mounting/reading that area (/data/media) and see if it boots up then. I took a look at Batakang's init files and I noticed that his omit the /storage lines that this CM10 includes.
But my first priorities are these two cpa exams on the 14th and 28th. I've been wasting too much time on this new phone :/
progrockguy said:
Yeah that solution seems impractical. I think a simpler solution would be to work around the internal "sdcard." I'd remove anything that involves mounting/reading that area (/data/media) and see if it boots up then. I took a look at Batakang's init files and I noticed that his omit the /storage lines that this CM10 includes.
But my first priorities are these two cpa exams on the 14th and 28th. I've been wasting too much time on this new phone :/
Click to expand...
Click to collapse
tried removing everything (except twrp folder and safestrap) from external sd, still get encryption error. I appreciate your time, i hope your exams go well. good luck
Just a question how is everything going so far guys? Keep up the good work
ATRIX HD running BATAKANG 1.10
This ROM won't boot because were using SS and not CWM or TWRP
Sent from my MB886 using xda app-developers app
What if we use whirley eyes bootmanager like the atrix 2
Sent from my MB886 using xda app-developers app
EcHoFiiVe said:
This ROM won't boot because were using SS and not CWM or TWRP
Click to expand...
Click to collapse
This boots up just fine. The ROM creator himself says it can be flashed with Safestrap: http://forum.xda-developers.com/showthread.php?t=1993888
The issue is getting past the "Encryption Unsuccessful" message for those on JB. From what I've read it's because the internal sdcard cannot fully read. (Maybe a factory reset & SD wipe via stock would help by erasing any encrypted data?)
progrockguy said:
This boots up just fine. The ROM creator himself says it can be flashed with Safestrap: http://forum.xda-developers.com/showthread.php?t=1993888
The issue is getting past the "Encryption Unsuccessful" message for those on JB. From what I've read it's because the internal sdcard cannot fully read. (Maybe a factory reset & SD wipe via stock would help by erasing any encrypted data?)
Click to expand...
Click to collapse
No. Its because we use a bootstrap recovery. I don't think its SS compatible because the Encryption Unsuccessful error only happens because of the incompatibility.
Sent from my MB886 using xda app-developers app
Hi.
Am using Motorola Milestone (A853) running on Cyanogenmod 7.
Am having a telephony problem since few days and my mobile frequently is having this error and asking for a reboot. Error image is attached below.
I have installed Vulnerable recovery, Open recovery (2nd boot).
When I had this problem, I reinstalled open recovery, wiped dalvic cache, external partition cache but still am getting this error.
Please help me to fix this.
Thank you.
Sent from my Milestone using xda app-developers app
Most of the time it is caused by having the 2.1 BPSW (baseband processor software) instead of the 2.2
I recommend flashing these two files (bpsw and devtree) just to be sure.
Good luck.
I have applied the updates you mentioned. Will check if my mobile if i gives or not the error again. Will post if it is fixed.
Thank you.
Sent from my Milestone using xda app-developers app
Erovia said:
Most of the time it is caused by having the 2.1 BPSW (baseband processor software) instead of the 2.2
I recommend flashing these two files (bpsw and devtree) just to be sure.
Good luck.
Click to expand...
Click to collapse
After flashing those files i didn't had problems for two days. But am again getting the same error. How do I solve it??
Sent from my Milestone using xda app-developers app
Sorry, but I don't have any more information regarding this problem.
( I know this problem occured even with the stock roms, but they rebooted the phone immediately and all unsaved data lost. )
Erovia said:
Sorry, but I don't have any more information regarding this problem.
( I know this problem occured even with the stock roms, but they rebooted the phone immediately and all unsaved data lost. )
Click to expand...
Click to collapse
I think you have installed CM 9.1 in your Milestone!
Can you please give me a feedback about the performance and usage of milestone on CM 9.1!
Thank you
It works great. I'm not saying it is as speedy as on a newer phone, but most of the time its okay. If it slows down, I just restart the phone and the problem is solved.
I recommend you to try it out for yourself. I also recommend to change the stock launcher.
Erovia said:
It works great. I'm not saying it is as speedy as on a newer phone, but most of the time its okay. If it slows down, I just restart the phone and the problem is solved.
I recommend you to try it out for yourself. I also recommend to change the stock launcher.
Click to expand...
Click to collapse
Ya sure I will try once. Thank you for the feedback!