Hi all,
Since i'm unable to start a thread in the android development forum I try here. Hopefully Arrrrgh won't get Arrrrgh'd at me for posting this..
I have a problem which I hopefully get support for. I have tried all Android roms for the touch pro2 which none will boot or get past the ACL bootlogo.
I've tried every imaginable way to get it working but all are resulting in a kernel panic. I tried the NAND versions and the SD versions but both options results in the same kernel panic.
First I thought it was the SD formatting problem but after trying 4 different sizes and brands I excluded this as a possible cause.
It seems after looking at it a bit more thoroughly I got a Vario V version of the TP2 - Rhodium 100 (please correct me if i'm wrong)
I'm able to pull logs i'm ready and willing to pass the logs for supporting this device. I've found a similar thread by Z!nk / Z1nk but he gave up on the device before the developers could get to it.
So hopefully there is a developer willing to add this version to the android roms.
Thanks for reading and hope to hear from anyone soon.
Cheers,
Alchedin
[edit] The device has security unlocked and is HSPL'd [/edit]
Alchedin said:
It seems after looking at it a bit more thoroughly I got a Vario V version of the TP2 - Rhodium 100 (please correct me if i'm wrong)
Click to expand...
Click to collapse
How can we correct you if you're wrong - you need to tell us what phone variant you have. There's a surefire way to know as well...
It's kind of the first question in the FAQ...
Either way, the fact that you can't boot either makes me think you have a clone. There was another fellow with a clone (perhaps the one you mentioned?) that was unable to boot XDAndroid because he didn't have the same hardware. If you run HaRET.exe with no startup.txt, what does it say?
Edit - Regardless, I would focus on one build and try to get that to work. FRX07.1 is probably the "simplest" from that perspective.
Edit2 - Also, you seem to indicate it's a kernel panic. Why no logs?
Dear Arrrghhh,
Thanks for replying.
Ok, looking at the faq it states my phone should be a Rhod100 (complete: NM8RHOD100) which seems, when googeling, to be some kind of T-Mobile version. At the moment i'm running a deepshining
I ran the rom without a startup.txt and it gave me the following message: Found machine Rhodium. Hope this is the info you needed?
Placed in the Rhodium100 startup.txt a started haret again, which resulted in a kernel panic.
Will keep you informed since I'm not at home.
Alchedin said:
Placed in the Rhodium100 startup.txt a started haret again, which resulted in a kernel panic.
Click to expand...
Click to collapse
Logs? How do you know it's a kernel panic? What kernels have you tried?
arrrghhh said:
Logs? How do you know it's a kernel panic? What kernels have you tried?
Click to expand...
Click to collapse
Hi Arrrghhh,
Attached are the adb logs, which I hope is the info you need. This is what I get when using FRX07.1 like you advised.
But I have three questions if i'm not too bold:
1. Did you advise this version because it's more thoroughly when it comes to finding a issue?
2. When looking at the logs, is there something wrong with sound or something?
3. I'm able to pull logs of NAND builds if you like? They seem to be more complete when it comes to information on boot.
Cheers,
Alchedin
Today I tried the GBX0C version of XDandroid and this is the first working android on my phone. Boot-animation started and it just worked! Still can't believe it.
Any idea how this rom differs from the FRX07.1?
Cheers
Alchedin said:
Today I tried the GBX0C version of XDandroid and this is the first working android on my phone. Boot-animation started and it just worked! Still can't believe it.
Any idea how this rom differs from the FRX07.1?
Cheers
Click to expand...
Click to collapse
Well there's a few things, besides the whole FroYo vs. Gingerbread. The acoustic code/routing is the 'main' one. Not sure what else off the top of my head, but there's changelogs in the GBX0C thread. There's not a huge difference since some of it was backported to FRX...
Either way, glad GBX is working.
Edit - the logs you posted from the FRX failures don't really give me much to go off of either, unfortunately.
arrrghhh said:
Well there's a few things, besides the whole FroYo vs. Gingerbread. The acoustic code/routing is the 'main' one. Not sure what else off the top of my head, but there's changelogs in the GBX0C thread. There's not a huge difference since some of it was backported to FRX...
Either way, glad GBX is working.
Edit - the logs you posted from the FRX failures don't really give me much to go off of either, unfortunately.
Click to expand...
Click to collapse
Today I tested different kernels using GBX0C and found out the following:
2.6.27.46(original GBX0C) - boots up
2.6.39.3 - boots up - Buttons / keyboard not functioning correctly
3.0.18 - boots up - buttons / keyboard not functioning correctly
3.3.8 - Not booting - Stuck on calibration (message: X & Y the same)
3.4.3 - Not booting - Stuck on calibration (message: X & Y the same)
Hope I did it right, replaced the zimage and module with every kernel switch. Also created a new data.img every time.
Cheers,
Alchedin
Alchedin said:
Today I tested different kernels using GBX0C and found out the following:
2.6.27.46(original GBX0C) - boots up
2.6.39.3 - boots up - Buttons / keyboard not functioning correctly
3.0.18 - boots up - buttons / keyboard not functioning correctly
3.3.8 - Not booting - Stuck on calibration (message: X & Y the same)
3.4.3 - Not booting - Stuck on calibration (message: X & Y the same)
Hope I did it right, replaced the zimage and module with every kernel switch. Also created a new data.img every time.
Cheers,
Alchedin
Click to expand...
Click to collapse
Sounds like for one reason or another, your device is different from all other RHOD's. There seems to be an infinite number of RHOD100 variants, and supporting all of them equally is impossible.
Unfortunately you're going to have to troubleshoot these issues. We don't have a lot of devs left, and without having the device in hand, it makes such development 1,000x harder. Good luck.
arrrghhh said:
Sounds like for one reason or another, your device is different from all other RHOD's. There seems to be an infinite number of RHOD100 variants, and supporting all of them equally is impossible.
Unfortunately you're going to have to troubleshoot these issues. We don't have a lot of devs left, and without having the device in hand, it makes such development 1,000x harder. Good luck.
Click to expand...
Click to collapse
If I supply you with the information you need through video, logs, dmesg, logcat etc. you can implement it correct? Too bad you're in the USA so shipping it will be costly.
Walter79 lives in Germany which country is next to where I live, maybe he can/is willing to extract the required info from the phone? I'm willing to go the extra mile if it helps the whole TP2 community.
Thanks a lot anyway :good:
Cheers,
Alchedin
Alchedin said:
Today I tested different kernels using GBX0C and found out the following:
2.6.27.46(original GBX0C) - boots up
2.6.39.3 - boots up - Buttons / keyboard not functioning correctly
3.0.18 - boots up - buttons / keyboard not functioning correctly
3.3.8 - Not booting - Stuck on calibration (message: X & Y the same)
3.4.3 - Not booting - Stuck on calibration (message: X & Y the same)
Hope I did it right, replaced the zimage and module with every kernel switch. Also created a new data.img every time.
Cheers,
Alchedin
Click to expand...
Click to collapse
Have you tried plugging a known working calibration file into the rom and using the kernels that are giving a calibration error?
Alchedin said:
If I supply you with the information you need through video, logs, dmesg, logcat etc. you can implement it correct? Too bad you're in the USA so shipping it will be costly.
Walter79 lives in Germany which country is next to where I live, maybe he can/is willing to extract the required info from the phone? I'm willing to go the extra mile if it helps the whole TP2 community.
Thanks a lot anyway :good:
Cheers,
Alchedin
Click to expand...
Click to collapse
I would not be a good candidate as I am far from a developer. As I stated previously, we don't really have any devs actively working on the project. walter79 just created the CM build, unfortunately he was not part of the original XDAndroid development team.
Again, your phone seems like it is a one-off, and development efforts for a one-off device are always difficult. I'd say you're going to have to pick up the effort yourself, or be happy with where the development is left at.
wizardknight said:
Have you tried plugging a known working calibration file into the rom and using the kernels that are giving a calibration error?
Click to expand...
Click to collapse
I used the same ts-calibration file that was created during the first boot of gbx0c. Like I stated earlier, I only replaced/removed the zimage, module and data.img file every time I switched kernel.
Should I also re-calibrate every time when switching kernels?
arrrghhh said:
I would not be a good candidate as I am far from a developer. As I stated previously, we don't really have any devs actively working on the project. walter79 just created the CM build, unfortunately he was not part of the original XDAndroid development team.
Again, your phone seems like it is a one-off, and development efforts for a one-off device are always difficult. I'd say you're going to have to pick up the effort yourself, or be happy with where the development is left at.
Click to expand...
Click to collapse
Many thanks for your interest and pointers arrrghhh, I will look into kernel stuff and such, maybe i'll get some of it working :fingers-crossed:
I have little to no development/linux/android skills but I can at least try to learn it.
Cheers
P.S: In a earlier stage playing around with NAND builds I managed to use the boot.img of the CM9-ICS_X1_testbuild1 in combination with the CM7.2 of walter79 and got it running in landscape mode, if this worked for me I can go from there.
Bit by bit i'm getting a hang of it.
Alchedin said:
Should I also re-calibrate every time when switching kernels?
Click to expand...
Click to collapse
No, as I state in all my threads about calibration - once you get a good calibration file, save 15,000 copies of it and re-use it constantly. There's no need to constantly recalibrate.
Ok here we go, sorry for the big read..
I hope I can be as precise as possible. This is about the NAND builds i've tested.
I installed ICS like in my last post again and made a CWM backup of the whole phone.
After this I did a new task29 and reflashed everything till I got back into CWM.
This time I installed the OMGB stable release with the kernelpatch + gapps.(seems the most advised build) Factory reset/data/cache/etc just to be sure.
Rebooted the device and let OMGB do it's thing, thus resulting in a kernel panic - can not sync issue. This is clearly a default message on this phone which I am in peace with. (log1)
Now for the fun part, I had this ICS testbuild backup up earlier and only did a restore of the boot part. Cleared the data/cache/etc again and rebooted.
This time it just boots fine into OMGB... (log2) previous attempts resulted in a landscape layout which i wasn't able to adjust myself, but this time I got the portrait mode correct! The only part which isn't working is the keyboard and hardware buttons.
Seems the "default" startup process is hanging in the part of the AudioFlinger? I compared the 2 logs but I can't see anything really which normally would result in a kernel panic.
Attached are the logs for the default OMGB boot (log1.txt) and the ICS modified boot + OMGB system (log2.txt)
Is this still different from any other Rhod100 or just a small adjustment? If this is really unknown I will break the phone to pieces and give up on it :silly:
I'll keep this config on the phone a bit longer since data and phone is working.
Thanks for reading
Cheers
-No sound
[Update]
Made a finding myself, the problem for my phone lies within the libhtc_acoustic.so removing this file made NAND boot up for the first time on this phone. Now looking for a compatible acoustic replacement which generates sound.
Going to try copying/pushing the file from FRX0.7 to NAND CM7.2 and see what it does. Including replacing my csv's from WinMo in the /system/etc folder.
[Update2]
Installed CM7.2 2.6.27 version today and used the FRX0.7 aucoustic.so, which resulted in a perfectly working android without sound...
now going after the csv's, which I hope gets me sound.
arrrghhh said:
[snip]...
Again, your phone seems like it is a one-off, and development efforts for a one-off device are always difficult. I'd say you're going to have to pick up the effort yourself, or be happy with where the development is left at.
Click to expand...
Click to collapse
I did a bit myself yesterday and today, the problem lies in the libhtc_acoustic.so, removing only this file made nand boot for me finally. See above post.
Alchedin said:
I did a bit myself yesterday and today, the problem lies in the libhtc_acoustic.so, removing only this file made nand boot for me finally. See above post.
Click to expand...
Click to collapse
Hrm, perhaps the new acoustic code jb started and detule 'finished' if you will isn't compatible with your device.
I don't know 'why'... on GBX0C did you copy the CSV's from your phone? I don't know how that build worked for you, because OMGB uses the same acoustic code.
arrrghhh said:
Hrm, perhaps the new acoustic code jb started and detule 'finished' if you will isn't compatible with your device.
I don't know 'why'... on GBX0C did you copy the CSV's from your phone? I don't know how that build worked for you, because OMGB uses the same acoustic code.
Click to expand...
Click to collapse
The interesting parts were the updates I posted. I did copy the csv's from the WinMo earlier, which were instructed by you (using total commander and such), but can't remember if it did produced sound.
But then...
I switched over to NAND CM7.2 by Walter79 and replaced the csv's in the CM7.2 zip file at location /system/etc (audioparatable.csv etc.)
Also I used the libhtc_acoustic.so from here
And ADB pushed the .so into the /system/lib folder.
When running logcat I see that the csv's are used and the audio routing is ok, but still didn't produce sound. Thought there were some other locations were the csv's are stored which I will also replace with mine. But didn't get to that yet.
Just tinkering with files really.. that's as far as I can go since I'm no developer.
What you mean by "perhaps the new acoustic code jb started and detule 'finished' if you will isn't compatible with your device" ?
Alchedin said:
What you mean by "perhaps the new acoustic code jb started and detule 'finished' if you will isn't compatible with your device" ?
Click to expand...
Click to collapse
I don't know how else to phrase that...
Although, I might have misread your statement. I thought you said you replaced a lib from FRX07.1 - which wouldn't boot for you. GBX0C did boot, so it seems the new acoustic code actually helps your phone.
So now I'm not sure what the deal is. I know OMGB uses the new acoustic, and I was under the impression that the CM ROM did as well. Did you try GBX0*? Basically the NAND version of GBX0C.
Related
Hello guys, want to have Froyo on your device? i've been testing and amzingly it run on Nike. Although there is a few bug just like the other android for Nike, but at least you can try the FROYO.
Here is what you need to do:
1a. If you haven't try Android before download attached andboot.zip, extract it to your SD card root.
1b. If you already have android build on your device, you can run copy androidinstall you've downloaded to andboot folder than do reinstall your android through haret. Remember to backup before doing anything.
2. Download androidinstall from the original thread Incubus26Jc's Super FroYo 2.2 [Deodexed] [RLS13] [8/18/10]
3. Backup! than, clear whatever "android" stuff you have from sdcard (I dont want it to get caught up in the install) especially your andboot folder
4. Extract contents of downloaded zip to temporary directory
5. Copy extracted /andboot folder to the ROOT of your SDCard
6. copy zimage to /andboot folder with this version (credit to mblaster) get in from http://84.23.71.227/kerneloftheday (i'm using zimage with vibration on my nike100 with zimageNike name) or you can use attached one - the newest from mblaster with audio fix (remember to extract the zip ).
7. overwrite default.txt with attached default.txt
8. Run HaRET, than hit “run” to launch android
9. Press and hold center of dpad after hitting "run" and follow the directions in the NoMoRootFs menu system
10. Install android system
11. Quit installer
12. Booting into Android
13. After you can see android logo wait about 15 minute
14. then shutdown and open up your phone again (should boot into winmo)
15. start haret and boot again to android
16. your android is ready to use
Working: Call, sms, ring, data (listed apn)
Not Working: Bluetooth, camera
Bug: Very difficult to receive call (maybe kernel problem???)
LEt us ask dzo (kernel inventor for vogue) to make update for Nike kernel to get all that stuff working
EDIT: thread author change it name, so i'll follow that too
UPDATE: I'm using dzo odex version from androidhtc
Very good post!
Whats wrong exactly with receiving calls?
I dont believe BT/Camera will work on any Android ROM for nike. This problem come from months since the first release, and never. So, or we buy a really android smartphone or we change for vogue
Installing RLS4 + Kernel with vibration 03 June.
EDIT: Now I understand. Receiving calls dont work, its like we have phone turned off. Data connections work (...) Its not fast and ADW Launcher crashs often (or we have to "wait" many times). 2.1 Much faster. Also, screen its very not aligned (sorry, dont know the right word). Many times if I want to press a widget I have to point to the another one on left (annoying using keyboard). Still the same issue with hardware button 1. Three times pressing this key, and my screen goes black. Sometimes, I have ADW Launcher, go to setting, go back, and then I have laucher PRO.
Its a cool ROM, but I think useless for now. Lets hope anyone can solve the problems.
Thank you.
yes, useless if our phone can't receive call, so we'll have to waiting for that, hope someone can solve it?
just contact dzo, he don't have time for maintaining a kernel for Nike. he want someone else to do that.
do you know someone who have some knowledge in C and a linux box to compile the kernel?
youngsien said:
yes, useless if our phone can't receive call, so we'll have to waiting for that, hope someone can solve it?
just contact dzo, he don't have time for maintaining a kernel for Nike. he want someone else to do that.
do you know someone who have some knowledge in C and a linux box to compile the kernel?
Click to expand...
Click to collapse
I know a lot of people, but no one with a nike. I know some C and linux, but I never programmed a kernel, however I can take a look. Where is the source code? Just found for vogue.
Maxxd01 said:
I know a lot of people, but no one with a nike. I know some C and linux, but I never programmed a kernel, however I can take a look. Where is the source code? Just found for vogue.
Click to expand...
Click to collapse
Check my kernel thread. You will find the diffs (basically text files that show changes in source) to the vogue kernel source on my download page.
yes, maxxxd01 please co-operate with mblaster, both of you is our hope for nike kernel. at least for now. thanks. keep up good work.
new zimage from mblaster works for audio, and no touch screen problems on mine, receiving call is also working for me using froyo - at least for now , still testing it -
here is what i did:
1. update newest kernel using mblaster kernel with audio bug free from new zimage from mblaster works for audio, and no touch screen problems on mine, receiving call is also working for me using froyo - at least for now , still testing it -
here is what i did:
1. update newest kernel using mblaster kernel with audio bug free from http://forum.xda-developers.com/showpost.php?p=7021840&postcount=3
2. using phone prioritizer from http://forum.xda-developers.com/showthread.php?t=558822
maybe you guyz can try it
OK, I know it is the third time I am posting this, but I don't want you to miss this...
Kernel service up again with audio patch included. Hope verything works now. Niki100 version is also patched now, touchscreen problems seem to be vibration related on niki100 (thats why there is a vibration free version especially for theat phone).
http://84.23.71.227/kerneloftheday/
PS: Let me know if everything is fine now.
looks like this newest build doesn't need any phone prioritizer anymore, it just ring as it should be, so no more receiving call lag.
youngsien said:
yes, maxxxd01 please co-operate with mblaster, both of you is our hope for nike kernel. at least for now. thanks. keep up good work.
Click to expand...
Click to collapse
I dont think I can help, mblaster works much faster
I'm confused, receiving calls problem solved. But, for kernel with or without vib?
I did not fix the call recieve bug, but I suspect it not to be in the kernel anyway. Android has a very greedy memory management, which tends to kill the phone app from time to time. On my G1 I have similar problems with some ROMs.
Perhaps it was just fixed in R5 of the ROM?
BTW: Any help is appreciated
Booting Froyo on my nike for the first time. Nice CM5 Bootanimation
wow, that mean receiving call problem is related to ROM, should thank dzo for that,
mblaster, yesterday i try to use newest kernel but it seems like sometimes it makes my touch screen not responding (i'm using zimage with vibration), then i revert back to zimage_audiotest, and still haven't find the same bug. anything wrong?
about the audio, it seems like a little larger, maybe can lower it a little thanks.
now yeah! I'm getting anxious, why now in an android niki100 (20 keys) is not just a toy is almost functional.
God bless you Mblaster, dzo you are almost there !!!!!
Vibration and camera are not so important for now, at least for me .. like the headphones because I walk a lot, but I will not ask more for it.
I think that Froio is more functional, but it seems late in the touch screen sometimes, or locking out of memory, not sure, but one question, where do I set the swap Froio? seems to me that with the eclair made work faster, Froio am running with EXT2.
Thanks!
Hey guys. I'm trying to use Android on my HTC Touch Dual.
It runs ok, and it is fast now using the froyo. But I got a problem that I don't understand...
I boot up on Android and I have sound. I then make a call and I can hear it well... I end that call and after that I can't get anymore sounds from the system... If I make a new call I can't hear anything from the other side...
Please help....
Could it be the radio version I'm using!?
Thanks.
I ask, the system did not contain Chinese, where I can download it?
abcorp said:
Hey guys. I'm trying to use Android on my HTC Touch Dual.
It runs ok, and it is fast now using the froyo. But I got a problem that I don't understand...
I boot up on Android and I have sound. I then make a call and I can hear it well... I end that call and after that I can't get anymore sounds from the system... If I make a new call I can't hear anything from the other side...
Please help....
Could it be the radio version I'm using!?
Thanks.
Click to expand...
Click to collapse
MAybe you can try to flash other version of radio. I'm using 1.65.28. you can get the link at insomnia thread
jiaorong said:
I ask, the system did not contain Chinese, where I can download it?
Click to expand...
Click to collapse
maybe you lack the input system and language only, i can run ucweb chinese version on mine, for input system try to search on web. sorry i can't help. thanks
youngsien said:
MAybe you can try to flash other version of radio. I'm using 1.65.28. you can get the link at insomnia thread
Click to expand...
Click to collapse
Thanks for the reply.
Sorry about asking this but I need to HardSPL my device to do that?
I saw a post saying this:
"Note: The USPL is not a "HardSPL" which means it gets overwritten when you flash a full ROM. You have to run the SSPL if you want to flash any ROM again.
The HardSPL is never overwritten which in case of flashing trouble is a great insurance. Should you want to flash another SPL or USPL you must run the SSPL."
Can I use the SSPL method instead? It seem's less dangerous...
I've never did this so sorry about the question.
Thanks man.
do you never flash custom ROM to your Nike?if you never flash you should read the tutorial in the sticky before doing anything further to prevent error on your nike. there are a lot of tutorial to doing that
Ok. Thanks a lot.
I already flash other devices but not this one... anyway I will read the tutorials.
EDIT: Thanks a lot youngsien. I already flashed the Radio you indicated and now I can make calls ok in android.
Xda Rulez!!
latest version video
http://www.youtube.com/watch?v=zlf5tEpyKGY
I seem to be having an issue with the proximity sensor on CM7 build 116. It was working perfectly. Suddenly, whenever in a call, the screen on my SGS2 would turn off as it was supposed to but then never turn on again. The only way to get the screen back on was to hard reboot the phone. I installed Z-DeviceTest and sure enough, the proximity sensor reads as constantly a distance of 0 (i.e. something covering the proximity sensor). If anyone knows a way to calibrate the proximity sensor or for a fix for this issue that would be GREATLY appreciated.
Thanks.
Update: Found a post somewhere that said the issue could be fixed by cleaning the screen really well. Took out the old microfibre cloth and voila, proximity sensor works again.
Hi all,
Anyone still got this build, esp 116..... As it appear to be the only one working on i9100 allegedly...
Thanks, Lister
rcfcyl said:
I seem to be having an issue with the proximity sensor on CM7 build 116. It was working perfectly. Suddenly, whenever in a call, the screen on my SGS2 would turn off as it was supposed to but then never turn on again. The only way to get the screen back on was to hard reboot the phone. I installed Z-DeviceTest and sure enough, the proximity sensor reads as constantly a distance of 0 (i.e. something covering the proximity sensor). If anyone knows a way to calibrate the proximity sensor or for a fix for this issue that would be GREATLY appreciated.
Thanks.
Update: Found a post somewhere that said the issue could be fixed by cleaning the screen really well. Took out the old microfibre cloth and voila, proximity sensor works again.
Click to expand...
Click to collapse
Lister Of Smeg said:
Hi all,
Anyone still got this build, esp 116..... As it appear to be the only one working on i9100 allegedly...
Thanks, Lister
Click to expand...
Click to collapse
What about the cm-7-20120722-NIGHTLY?
Hi @gsstudios,
You seem to be the most active person on here, thanks for coming to my support/rescue again...
Yeah, I've tried that one... I've tried that, and a couple of others from that page (all CM7.x releases) and after I've flashed them, they all just bootloop with the Samsung logo....
What's more annoying than it just not booting, is that it appears to remove any kind of recovery... As you can't get back into it, to flash anything else. And so have to enable Download mode and flash a kernel with Odin to be able to wipe and try / start summit else...
I've tried, 'the various solutions'
1) All the normal wipes
2) Flashing the rom twice
3) Returned the phone back to official stock PITs, it's even running stock (Android 4.1.2) OS at moment.
Just can't get it to boot....?? What's odd, I have actually had it running on this phone at some point... When it didn't belong to me. And that's the whole reason I purchased it off my friend, so I can go back to CM7, as well as keep upto date with all the Lollipop jazz...
Very odd, don't know what I did last time that made it work... As I just flashed it normally when the phone didn't belong to me... Didn't do anything fancy....
Also, is there a difference on CM's website between i9100 and galaxys2 listings...? (not that it helps, as one of the branches doesn't even have the files). Just seems odd to have 2x international versions... I can understand if it said i9100G or something, but they both seem the same... Perhaps I downloaded a different CM7 rom at the time...??
Thanks, Lister
gsstudios said:
What about the cm-7-20120722-NIGHTLY?
Click to expand...
Click to collapse
Lister Of Smeg said:
Hi @gsstudios,
You seem to be the most active person on here, thanks for coming to my support/rescue again...
Yeah, I've tried that one... I've tried that, and a couple of others from that page (all CM7.x releases) and after I've flashed them, they all just bootloop with the Samsung logo....
What's more annoying than it just not booting, is that it appears to remove any kind of recovery... As you can't get back into it, to flash anything else. And so have to enable Download mode and flash a kernel with Odin to be able to wipe and try / start summit else...
I've tried, 'the various solutions'
1) All the normal wipes
2) Flashing the rom twice
3) Returned the phone back to official stock PITs, it's even running stock (Android 4.1.2) OS at moment.
Just can't get it to boot....?? What's odd, I have actually had it running on this phone at some point... When it didn't belong to me. And that's the whole reason I purchased it off my friend, so I can go back to CM7, as well as keep upto date with all the Lollipop jazz...
Very odd, don't know what I did last time that made it work... As I just flashed it normally when the phone didn't belong to me... Didn't do anything fancy....
Also, is there a difference on CM's website between i9100 and galaxys2 listings...? (not that it helps, as one of the branches doesn't even have the files). Just seems odd to have 2x international versions... I can understand if it said i9100G or something, but they both seem the same... Perhaps I downloaded a different CM7 rom at the time...??
Thanks, Lister
Click to expand...
Click to collapse
Galaxys2 was the old name used for our device by cm. Now its i9100 which is the actual name for our phone. Galaxys2 has all of the old builds of cm, while i9100 has all of the newer builds. Other than that, its for the same device.
Sorry. I can't help you with the cm 7 build you are trying to find.
Hi @gsstudios,
Ah I see, I did wonder why there was 2x seperate branches for the same device... I could understand if one was for the HD or the LTE version, but I guess they already have their own variant name in CM already... Just thought it was odd to have 2x i9100 builds going on together.... lol
Anyway, regarding CM7.... I've finally managed to get it to work!!!! YIPPIE!!!!!!! Finally... Although I swear it wasn't as hard as this when the phone DIDN'T belong to me, and I did it as a test for my mate... But anyway, got it installed and loving it... It's nice to go back once in a while to where it all began (well, for me anyway.... My first device came with Android eClair, I think Android 2.1 or summit??) But CM7.x was my first custom OS ever installed on ZTE Blade.
It would seem all the CM7 builds that I can find, both on CM site, and other hosts are all BORKED (broken) and that they lack Boot info, hence the BootLoops... and that all their recoveries are broken, as not a single one would go back into recovery after flash, had to Odin it back to life with a PC. Not cool if ya gone out for the day... lol So basically I found some random GB kernel, and flashed that after CM7 + GApps + Recovery.... and thank the lord, it all boots again...
I'd just like to THANK YOU, for always consistently and continually coming to my support needs..... Your help/advice has been extremely helpful.... thanks
Lister
gsstudios said:
Galaxys2 was the old name used for our device by cm. Now its i9100 which is the actual name for our phone. Galaxys2 has all of the old builds of cm, while i9100 has all of the newer builds. Other than that, its for the same device.
Sorry. I can't help you with the cm 7 build you are trying to find.
Click to expand...
Click to collapse
Hello XDA! I have been a keen follower of this forum for long, but this is my first post, 'cause well... this is the first time I pretty stuck at something.
I have a Xperia Mini Pro (SK17i) and I have been using it for quite a while, around 2 years I presume. I have rooted and unlocked the bootloader by the end of the first year, and have been trying out several custom roms, until stopping at CM10.1 of LegacyXperia. (the amazing creation of Mike for our 2011-line of devices!) However, as of a month back, my touchscreen kinda broke - it wouldn't respond along with the capacitive buttons. I tried the methods mentioned in the general section, but no avail - it simply wouldn't work at all. There's a thin small strip that appears around the screen during pulling out the hardware keyboard, and I guess that somewhat suggests that the touchscreen is invalid by hardware means.
However, that's merely a background to the problem I'm facing. Recently, after the launch of CM11, I thought of giving it a swing, seeing how I have been an avid-fan of the pure look of CM. I tried flashing the kernel using flashtool and start the phone, but the only thing that takes place is just a vibration and a black screen. The screen remains black for like ever, until I pull out the battery. I tried flashing the kernel thrice, and the same problem persisted all through. I reverted back to the stock ICS then and it worked like a charm, and the same goes for FXP CM10 and the last CM10.1 I used... there's no problem whatsoever, save for the broken touchscreen.
Any suggestion one might give about my problem? Thanks a ton for reading out everything!
psychoticdemon said:
Hello XDA! I have been a keen follower of this forum for long, but this is my first post, 'cause well... this is the first time I pretty stuck at something.
I have a Xperia Mini Pro (SK17i) and I have been using it for quite a while, around 2 years I presume. I have rooted and unlocked the bootloader by the end of the first year, and have been trying out several custom roms, until stopping at CM10.1 of LegacyXperia. (the amazing creation of Mike for our 2011-line of devices!) However, as of a month back, my touchscreen kinda broke - it wouldn't respond along with the capacitive buttons. I tried the methods mentioned in the general section, but no avail - it simply wouldn't work at all. There's a thin small strip that appears around the screen during pulling out the hardware keyboard, and I guess that somewhat suggests that the touchscreen is invalid by hardware means.
However, that's merely a background to the problem I'm facing. Recently, after the launch of CM11, I thought of giving it a swing, seeing how I have been an avid-fan of the pure look of CM. I tried flashing the kernel using flashtool and start the phone, but the only thing that takes place is just a vibration and a black screen. The screen remains black for like ever, until I pull out the battery. I tried flashing the kernel thrice, and the same problem persisted all through. I reverted back to the stock ICS then and it worked like a charm, and the same goes for FXP CM10 and the last CM10.1 I used... there's no problem whatsoever, save for the broken touchscreen.
Any suggestion one might give about my problem? Thanks a ton for reading out everything!
Click to expand...
Click to collapse
The kernel is incompatible with your phone.
Care to explain a little more? I have flashed the kernel provided within the rom zip itself (as suggested time and time again), and I have double checked its for the correct device - i.e. mango.
psychoticdemon said:
Care to explain a little more? I have flashed the kernel provided within the rom zip itself (as suggested time and time again), and I have double checked its for the correct device - i.e. mango.
Click to expand...
Click to collapse
kernel is for mango??unofficial port right...can you provide the rom link once.....??
http://forum.xda-developers.com/showthread.php?t=2545367
This is the one - LegacyXperia CM11 by mikeioannina.
psychoticdemon said:
http://forum.xda-developers.com/showthread.php?t=2545367
This is the one - LegacyXperia CM11 by mikeioannina.
Click to expand...
Click to collapse
yeah i though so...was going through the post...did you try this..
1.1 (optional): If the device is not booting, reboot to bootloader again and run:
fastboot erase system
fastboot erase userdata
As the rom requires a new partition table and maybe system and userdata is conflicting...
Dark Wraith said:
yeah i though so...was going through the post...did you try this..
1.1 (optional): If the device is not booting, reboot to bootloader again and run:
fastboot erase system
fastboot erase userdata
As the rom requires a new partition table and maybe system and userdata is conflicting...
Click to expand...
Click to collapse
Thanks a lot for pointing it out, mate! Usually the roms I tried didn't require such a thing, but this might be it. I'll provide feedback if the steps works.
I tried the steps advised, but the problem seems to still persist to some extent. The capacitive lights are lit and the screen is lit as well (as could be understood from the viewing angles - it's brighter and powered up). Nothing seems to appear on the screen though - no boot logo or anything - and trying to enter recovery fails as well (through power + vol up shortcut). I have tried it twice already, kept the phone switched on for five minutes or so, but no avail. I had to pull battery out every time to shut down the device. Anyone have any other advice?
psychoticdemon said:
I tried the steps advised, but the problem seems to still persist to some extent. The capacitive lights are lit and the screen is lit as well (as could be understood from the viewing angles - it's brighter and powered up). Nothing seems to appear on the screen though - no boot logo or anything - and trying to enter recovery fails as well (through power + vol up shortcut). I have tried it twice already, kept the phone switched on for five minutes or so, but no avail. I had to pull battery out every time to shut down the device. Anyone have any other advice?
Click to expand...
Click to collapse
try this.....Have the stock ICS 4.1.B.0.587 full ftf flashed (doesn't matter if you have flashed it in the past or if you flash it before installing cm11.0, it will work both ways)
then see if device powers up...
once it does...go for the next steps........
Dark Wraith said:
try this.....Have the stock ICS 4.1.B.0.587 full ftf flashed (doesn't matter if you have flashed it in the past or if you flash it before installing cm11.0, it will work both ways)
then see if device powers up...
once it does...go for the next steps........
Click to expand...
Click to collapse
Thanks for the quick response, but I tried that too. Unfortunately, the problem still seems to persist.
psychoticdemon said:
Thanks for the quick response, but I tried that too. Unfortunately, the problem still seems to persist.
Click to expand...
Click to collapse
I wonder if its a hardware related issue...you said in your op that there is some problem with your screen and capacitive buttons...Got any friend with sk17i???? I had one before it was stolen......Every other rom apart from CM11 is working right..Is there any other Kitkat based ROM for sk17i..if its there you may try that out and see if you have the same problem...otherwise..wait for a kitkat based rom to come up and try before flashing this...Try one more time from scratch...flash stock ICS 4.1.B.0.587 full ftf..reboot....once its working...fastboot flash boot.img...then better to fastboot erase system and fastboot erase userdata and then before it boots enter recovery and wipe data cache everything...flash update.zip..wipe cache,data,dalvik cache again...and boot..if it doesnt boot up then there is no option but to wait..
Dark Wraith said:
I wonder if its a hardware related issue...you said in your op that there is some problem with your screen and capacitive buttons...Got any friend with sk17i???? I had one before it was stolen......Every other rom apart from CM11 is working right..Is there any other Kitkat based ROM for sk17i..if its there you may try that out and see if you have the same problem...otherwise..wait for a kitkat based rom to come up and try before flashing this...Try one more time from scratch...flash stock ICS 4.1.B.0.587 full ftf..reboot....once its working...fastboot flash boot.img...then better to fastboot erase system and fastboot erase userdata and then before it boots enter recovery and wipe data cache everything...flash update.zip..wipe cache,data,dalvik cache again...and boot..if it doesnt boot up then there is no option but to wait..
Click to expand...
Click to collapse
Exactly. That's the whole reason why I posed this thread - to know if it was a hardware related problem right off the bat, or there was really something that I was doing wrong. I'll rather leave this one open to see if anyone have any other opinion about the matter. I really want to see what Kitkat looks like seeing how it's not available for my current device. (Micromax A210)
Also, about trying out other 4.4 roms... I guess I can try that route. But seeing how this problem is induced by the kernel itself and every other rom out there is mainly based off the LX 3.4 kernel, I doubt if that will work. I'll try the option anyway and see if it works.
psychoticdemon said:
Exactly. That's the whole reason why I posed this thread - to know if it was a hardware related problem right off the bat, or there was really something that I was doing wrong. I'll rather leave this one open to see if anyone have any other opinion about the matter. I really want to see what Kitkat looks like seeing how it's not available for my current device. (Micromax A210)
Also, about trying out other 4.4 roms... I guess I can try that route. But seeing how this problem is induced by the kernel itself and every other rom out there is mainly based off the LX 3.4 kernel, I doubt if that will work. I'll try the option anyway and see if it works.
Click to expand...
Click to collapse
Yeah.....waiting for other roms wont work.....cz they are all based on 3.4.x kernel.......Umm can you check your baseband after flashing full ftf...baseband should be : 8x55A-AAABQOAZM-203028G-77..every other rom based on 3.4.x kernel works right???...btw if you want to see how it looks just download a kitkat launcher from playstore....
Yes, the baseband is .77 after flashing the ICS 4.1.0.B.587. I used 3.4.x kernel with CM10.1, but never really tried CM10.2 to that extent. Maybe I'll try downloading that and see if it works... or even the EOL CM10.1.
And sure, the launcher would give in the feel, but I want the full experience possible really.
Cheers, XDA colleagues
In first place, I want to apologize in advance for English mistakes, because I have only a basic knowledge in that language and I'm typing it all at the end of the night, here. So, I'm somewhat oblitered by the sleepless time I spent diagnosing and trying to fix some problems I had while flashing CM11 to my Xperia M device.
Well, due to some mistakes when installing GApps (I didn't want to be all-connected to Google), I have formated and reinstalled the system at least four times. Now, at the fourth time, I had everything more ou less setted up the way I wanted. Had some commonplace apps -- like WhatsApp -- installed, some UI features customized. At this point, I tought "Uff... Now it's all done".
However, it wasn't. Actually, I'm running into a bizarre problem with sleep mode, a few time after being locked. When my phone enters it, it won't exit. To make things a bit more clear: it dies, and in a way that's necessary remove battery and put it back on to turn it on again.
I'd check syslog and dmesg, but I don't know where are them at the Android filesystem (in fact, I haven't used *nix in a couple of years). So, I'm relying to my dear colleagues of these forums, if they have a clue on what's going on.
I'm using FXP330 ROM (http://forum.xda-developers.com/showthread.php?t=2584956).
Thank you very much!
Att.,
P. Pinheiro
Bumping it up.
system files are very delicate. what exactly did u modify because this means u re gonna need to reflash the whole rom
Ambychy said:
system files are very delicate. what exactly did u modify because this means u re gonna need to reflash the whole rom
Click to expand...
Click to collapse
Hi, Ambychy, thanks for the reply!
Yeah, it's actually what I ended up doing. Now it's working with no interruptions. Shame I'll need to reflash it because it had no GSM signal, and to make it work it's necessary reflash stock 4.3, and have 4.3 baseband flashed. So, for all effects, the subject of this thread were solved.
But it's what CyanogemMod about: it's a geek way and you'll run into some problems, but in the end everything got be working fine and in highly costumizable way.
Cheers
No problem mate we all gotta help each other
Hi.
I have a Nook Tablet (16gb version) with which I have a problem.
Once upon a time (couple summers ago), I decided to flash another touchscreen firmware through the Touchscreen Firmware Flasher app included in the KK version of LiquidSmooth, unofficial build for NT. I had just changed the glass part of the screen, so I was looking forward to using my tablet for months to come.
The problem is that the flasher app crapped out on me and force closed in the middle of the installation, leaving me without a usable touch driver. I have tried using SD-boot ROMs and I believe they have done nothing for me. I flashed many ROMs, including MIUI, stock and CM 10.1.3, with no result other than a successful boot. But still no touch input.
I talked to demetris about this (seemed like a good idea) and he gave me many tips. Essentially, all I have to do is run a script after placing a file in /system/etc/firmware and it should be fixed. Alas, this has not worked. I shall include a screenshot of the error.
I am now in possession of a Nook Tablet with a screen that will not respond to touch at all, but can boot standard CM 10.1.3, TWRP and CWM. I used the ADB included in TWRP for the procedure, and nothing. This is probably something that has to be done from within the system, so...
Is it possible to add a line in build.prop saying "ro.secure=0"? I read online that this will disable secure ADB (remove the need for RSA key approval) so that I may run the script?
UPDATE: I made a breakthrough. I am currently trying to put this script into a flashable zip. The part I still can't do by myself is the updater-script. It's mostly working but the recovery says the zip is bad. The exact thing is in the thumbnails below.
If anyone can use Edify (Recovery Script Language) and at least give me some tips, I'd be grateful. Thanks for checking!
TheAnonymusModUser said:
Hi.
I have a Nook Tablet (16gb version) with which I have a problem.
Once upon a time (couple summers ago), I decided to flash another touchscreen firmware through the Touchscreen Firmware Flasher app included in the KK version of LiquidSmooth, unofficial build for NT. I had just changed the glass part of the screen, so I was looking forward to using my tablet for months to come.
The problem is that the flasher app crapped out on me and force closed in the middle of the installation, leaving me without a usable touch driver. I have tried using SD-boot ROMs and I believe they have done nothing for me. I flashed many ROMs, including MIUI, stock and CM 10.1.3, with no result other than a successful boot. But still no touch input.
I talked to demetris about this (seemed like a good idea) and he gave me many tips. Essentially, all I have to do is run a script after placing a file in /system/etc/firmware and it should be fixed. Alas, this has not worked. I shall include a screenshot of the error.
I am now in possession of a Nook Tablet with a screen that will not respond to touch at all, but can boot standard CM 10.1.3, TWRP and CWM. I used the ADB included in TWRP for the procedure, and nothing. This is probably something that has to be done from within the system, so...
Is it possible to add a line in build.prop saying "ro.secure=0"? I read online that this will disable secure ADB (remove the need for RSA key approval) so that I may run the script?
Click to expand...
Click to collapse
Did you see this thread?
nmyshkin said:
Did you see this thread?
Click to expand...
Click to collapse
Yes, I did. I tried booting off an SD card and the screen still would not respond at all.