Related
I have currently installed RUU_Le2_UK_1.72.206.3_Radio_15.32.50.07U_2.07.51.22_2_Signed_LEO_Ship
everything works fine.
i have tried Dutty CDLC version 14 which worked fine but due to the messaging client being not compatible with smartwatchM i had to go back to stockrom
i previously HSPL so i could install custom radio (to make android work)
after going back to the stock rom i have since tried various other roms and i have the same problem each time
it installs and boots fine, after a restart it just seems to hang at first screen (does not display radio rom etc in bottom corner like normal just screen)
only way to get anything to work again is to once again install the stock rom via bootloader screen.
is the HSPL damaged? or have i missed something
thank you for you help
you are flashing 576 ram enabled roms, but your radio is still a 51 version so they won't boot.
enter bootloader, flash something like 2.08.50.x radio and your phone will boot. don't forget every time you flash back to that o2 rom it will reset the radio to a 51 version.
that makes so much sense, im just an idiot.
i shall attempt this now. thanks alot
easy to overlook.
it worked ... altho i have to go back due to me not being able to find a new rom that works with my mbw150 lol , 2 days just to revert back
anyways im very happy for the quick reply and help and not mocking me for being dumb. thanx again
Hey guys,
here is what is going on with my German Vodafone I9100
After using Sensation Rom for a few months, I finally decided to make the transition to Android 4.
The first rom I tried, was the Simplistic ICS by LegendK95
Installing from CWM worked like a charm, booting worked like a charm, but whatever I tried to do, the phone freezed in homescreen randomly after 5-30 seconds. Only a restart bring it back to work, only to make it freeze again after the mentionend time span.
Whatever I did (waiting in home screen, pulling down the statusbar, scrolling in app drawer) the phone always freezes.
After dozen of restarts, I installed the rom again, the problem stayed.
Then I decided to go to stock 4.0.3 (LP6). Installation via Odin worked like a charm. Booting worked like a charm, but the homescreen-freeze-problem got even worse.
I also tried to reinstall the stock LP6, but the phone now even froze in CWM mode, while data reset AND WHILE INSTALLING THE FW.
Now I got a soft brick in my hands.
So, I installed stock 2.3.3. via Odin. The phone now worked flawless again. No freezes, no no nothing. Just a working phone.
My final try was to install the latest CM9 build.
Guess what happend?
The legendary homescreen freeze. That nobody else appear to have. YAY
So, somehow my phone seems to be allergic to Android 4.
Can somebody please help me?
Regards
PS: Yes, I followed the instructions every firmware provided.
Honestly you want an honest answer. Stay clear of ICS leaks and yes that means even cm9. Reason being. Because of what they are. Leaks and nothing official. Not saying that they are not good but if you look at the original android development can you see any actual ICS roms? No. Why you asking? Because no kernel sources have been released and nothing is far from stable yet. Even cm9 builds codeworkx has on the thread title experimental. So my advice. Flash a Gingerbread custom rom slap on it the ICS by vertumus and your good to go till the official stuff get released.
Maybe before flashing ICS you should fully wipe your device to get rid of all previous ROM data from Gingerbread as they,I imagine,wont be very compatable.
Boot to recovery and go to "mounts and storage" and format System/Data/cache and then factory reset.Then flash the Rom via recovery(install zip).If its an Odin flash then reboot and flash via Odin.
Hi suarez,
thanx for your opinion. I read a lot of threads before updating and came to the conclusion that the current releases, even CM9 seem to be pretty stable.
Also I found no one having issues like that.
Hi cooza,
I did that.
Klammeraffe said:
Hi suarez,
thanx for your opinion. I read a lot of threads before updating and came to the conclusion that the current releases, even CM9 seem to be pretty stable.
Also I found no one having issues like that.
Hi cooza,
I did that.
Click to expand...
Click to collapse
No problem my friend. But I still stand by what I said though. For me to make the jump is a no go yet. Yes they might be stable but so far I still read problems regarding video forever, this is not working that does not work and that most issues will be solved once kernel source is available. Hence why still the experimental on cm9.thread.
Sent from my GT-I9100 using xda premium
Suarez7 said:
No problem my friend. But I still stand by what I said though. For me to make the jump is a no go yet. Yes they might be stable but so far I still read problems regarding video forever, this is not working that does not work and that most issues will be solved once kernel source is available. Hence why still the experimental on cm9.thread.
Sent from my GT-I9100 using xda premium
Click to expand...
Click to collapse
Yes, but if you're not that big into watching/recording videos on your SGS2, it's pretty freaking stable.
Installing the latest experimental build of CM9 is probably the best thing I've done to my SGS2 as of late. It's just so... Nice.
I cannot get rid of that problem.
I really need help on this.
Some new information:
I also tried to flash the leaked stock LP2. Same result.
This FW crashed on first start, when the Samsung Apps are installed.
Still some little success:
When flashing from stock BUGKJ2 straight to LegendK95's Simplistic ICS rom, I was able to get it to run, until I have to restart the phone.
But this was the only rom capable of doing so. Every other fw failed.
So, I now can have ICS on my phone but only until I restart the phone.
After reboot, the phone crashes again after some seconds.
Additionally the CWM Recovery doesnt work as long as I have a ICS rom on it.
It also occasionally crashes. Preferrably when I try to flash a new rom, leaving me a shiny brick
Here are the steps to get Simplistic ICS run until reboot:
1. Put the file on internal memory.
2. Go to recovery: wipe data/factoy reset, wipe cache, wipe dalvik, wipe battery, format system, format data, format cache
3. Flash from internal sd
4. Reboot
Klammeraffe said:
Some new information:
I also tried to flash the leaked stock LP2. Same result.
This FW crashed on first start, when the Samsung Apps are installed.
Still some little success:
When flashing from stock BUGKJ2 straight to LegendK95's Simplistic ICS rom, I was able to get it to run, until I have to restart the phone.
But this was the only rom capable of doing so. Every other fw failed.
So, I now can have ICS on my phone but only until I restart the phone.
After reboot, the phone crashes again after some seconds.
Additionally the CWM Recovery doesnt work as long as I have a ICS rom on it.
It also occasionally crashes. Preferrably when I try to flash a new rom, leaving me a shiny brick
Here are the steps to get Simplistic ICS run until reboot:
1. Put the file on internal memory.
2. Go to recovery: wipe data/factoy reset, wipe cache, wipe dalvik, wipe battery, format system, format data, format cache
3. Flash from internal sd
4. Reboot
Click to expand...
Click to collapse
Maybe the problem is the stock firmware you first flash.I searched for it but cant find it,is it carrier branded?..BUG sounds like it to me.Maybe you should fully wipe your phone (format System/Cache/Data) and first flash something like XWKL1 and then the ICS ROM.If the ICS ROM you are going to flash has a multi CSC package in it then it wont matter what F/W you flash first.
hello cooza,
i had to go back to stock 2.3.3 because my phone was a brick after flashing any ics rom.
i tried to flash simplistic ics and cm9 via cwm, i dont know if those contain multi_csc.
however, the leaked stock roms, lp2 and lp6 both contain multi_csc that i flashed via odin.
here are all the steps i tried:
fail 1: flashing from sensation rom 3 (2.3.6) to simplistic ics
fail 2: flashing from 2.3.3 to cm9/simplistic ics
fail 3: flashing from bricked ics to stock lp6
fail 4: flashing from 2.3.3. to 2.3.5. (latest official release via kies) to cm9/simplistic ics/stock lp6
fail 5: flashing from 2.3.3 to leaked stock lp6 inluding the pit-file provided
nevertheless, flashing from 2.3.5 to simplistic ics worked until restarting the phone. however, cwm was not working correctly then. so, surely i could have tried to let the phone on for forever, but as soon as i would want to flash a new firmware, i would have got a brick left, because cwm would crash during installation of the new one.
there must be some help out there
thanx for trying cooza. much appreciated.
You might have a damaged bootloader.Although its not needed you could try a JTag.A JTag is used to bring a hard bricked phone back to life.You dont have a hard bricked phone but what it also does is repairs any damage that the bootloader may have.Costs about 25 to 30 euros.As a last resort you could give it a go if your phone is going to give you constant reboot problems and not let you flash firmwares.It should also repair any repartition faults because it completely wipes the bootloader before repairing it.The phone will come back like the first day you got it.check the link below out and use it to find one close to you if you choose to do one.I had an i9000 done last September here in Spain and it came back perfect from a hard brick soo I know it works.I used the link below.
http://www.jtagbox.com/riff-jtag-bo...-bricked-phone-riff-box-owners-list/#comments
Seems like the very last option to me
Would a broken bootloader allow me to run 2.3.X flawless?
Question does Samsung stock firmware work .
As it seems all your problems are from using a buggy unreleased test rom not from using Samsung released firmware .
I would if it was my problem .
Clean Slate for those that balls up the firmware .Or need to return to service or decide if its hardware/firmware problem .
Backup data first if phone is working .
Boot CWM recovery
Mounts and Storage
Format cache data system sd card wiping everything on the phone .
Remove battery
Boot to download mode
Open Odin
Install correct Samsung stock firmware for your phone model .
Test phone works .
jje
hi JJ,
thanks for your post.
as i said, the phone is working fine on stock android 2.3.X as well as custom firmwares using 2.3.X.
However, all 4.0.X firmwares I tested, showed the same behaviour: crashing my phone in homescreen (or anywhere else after booting) AND in cwm after 10 to 30 seconds.
only simplistic ics custom rom worked fine until first reboot. then it crashed as well. everytime.
I tested 2 stock firmwares of samsung and 2 custom roms.
I also tested flashing 4.0.3 (CM9) on a friends SGS2 using the same procedure I used on my phone. It worked on first try and he`s now a happy android 4 user.
right now i`m running on CM7 but i wanna uprage to android 4.
edit:
up to this date there is no official released 4.0.3 rom for the sgs2 but how can it be that I have the only phone showing such a behaviour while everyone else has a 99% stable fw for the same phone using the same rom?
Mate,at least it works,thats the important thing.I can understand that its frustrating when the only Firmware/customROM you want doesnt work in your phone and only your phone but we are talking about BETA version ROMs.If there is something for some reason blocking the ICS ROM then it is possible that the JTag will clear it up as it wipes and repears the bootloader as I mentioned so any corrupt data will dissappear.Ive had a bricked phone done and it still works perfectly today but never a phone in your situation.Its possible but never having done so I cant guarantee it.If you want give it a go.You got nothing to loose except 20 or 30 bucks for your efforts.
I have exactly the same issue with a "german" Galaxy S2. I tried to install the {CWM}İCS REMİX ROM v8.4 ULTİMATE ONLİNE XXLP6 4.0.3 resurrection NO-WİPE
Version.
Followed ofcourse the installation instructions letter for letter. It doesn't go over the logo screen. ( And yes I am aware it takes several minutes for such an installation to finish)
I read in that thread of at least another 3-4 people with the same issue.
Going back to any 2.3.x works as usual.
If you take the time and read the various ICS posts one inescapable fact will arise .
ICS suffers from many varied problems with no two users reporting identical problems .
That is compounded by two factors one the boot loader and two as a beta test rom for some strange reason those with very little knowledge rush to install it .
But hey save money on the Samsung testing department just leak your Alphas and Betas .
For me i will play with a test rom for an hour or two but thats it i require a stable rom for daily use . It will need vast improvement for me to consider the final release of ICS for daily use .
jje
spytrek said:
I have exactly the same issue with a "german" Galaxy S2. I tried to install the {CWM}İCS REMİX ROM v8.4 ULTİMATE ONLİNE XXLP6 4.0.3 resurrection NO-WİPE
Version.
Followed ofcourse the installation instructions letter for letter. It doesn't go over the logo screen. ( And yes I am aware it takes several minutes for such an installation to finish)
I read in that thread of at least another 3-4 people with the same issue.
Going back to any 2.3.x works as usual.
Click to expand...
Click to collapse
GSMArena say that Samsung are launching ICS for the S2 in march
http://www.gsmarena.com/samsung_galaxy_s_ii_and_galaxy_note_to_get_ics_in_march-news-3752.php
with this I imagine that stable ICS custom ROMs are just around the corner so if you can wait a few months more you will be able to flash a stable safe ROM without any problems.Until then the BETA versions that are out at the moment are going to cause these types of things.
I had these same isues with KP8 on my s2. I fixed them by flashing LP6 directly over kp8 without wiping anything. I think it may have something to do with the phone drivers you have installed on your pc. They may be damaged and be producing some kind of error on the flashing proccess. I recomend that you hard reset to 2.3.x and reinstall kies on your pc. That should reinstall phone drivers too. And make sure kies is NoT running while using odin. Kies doesent like odin
Sent from my GT-I9100 using Tapatalk
I have patience As long as I fallback to a functional rom everyting is cool. As for the alpha-beta testing, I have nothing against it and I didn't complain about it. Till March I hope the S3 is out so I can pass my S2 to my better half ...
I bought a Rezound on ebay, pre-rooted/unlocked with the leaked ICS / Sense 3.6 ROM (besides that, pretty much bone-stock)
I decided I wanted to try out a different ROM and make sure I am familiar with the process before I try to do the S-OFF process....
Well, I found that the first thing I needed to do to upgrade to (insert ICS/Sense 4 Rom here) was to upgrade to the newest Firmware (3.11.605.22), and I am currently on 3.11.605.01 ... I followed their instructions closely to update the firmware ( re-lock , load new FW as PH98IMG.zip , flash it , unlock, etc)
Well, that didn't work for me, when I got to loading up hboot and it automatically updating the FW, it didn't do what the instructions said it would, it showed a dark blue bar near the top/right, waited for that to complete, then same thing but yellow, that completed and asked to reboot, but would only reboot to fastboot...
eventually I unlocked it again and it allowed me to return to my ROM (normal ICS/sense 3.6)
Sorry about this short story... lol ^
Basically I cannot for the life of me install any rom with success... I can't even restore the nandroid I made last night (before any of this) with success..
the CLOSEST thing to success I got was installing newts One XxX sense 4 rom, it booted, and will sit on the lock screen just fine, but when I try to unlock and go to settings to turn off animations (like instructed) it will freeze and reboot....
DO I need to install the newest FW???
OR what do I need to dooo?
Pls help! I am fairly familiar with android, as I had a D Inc before this, evervolv ICS etc etc....
Thanks alot anyone !
x70xchallengerx said:
I bought a Rezound on ebay, pre-rooted/unlocked with the leaked ICS / Sense 3.6 ROM (besides that, pretty much bone-stock)
I decided I wanted to try out a different ROM and make sure I am familiar with the process before I try to do the S-OFF process....
Well, I found that the first thing I needed to do to upgrade to (insert ICS/Sense 4 Rom here) was to upgrade to the newest Firmware (3.11.605.22), and I am currently on 3.11.605.01 ... I followed their instructions closely to update the firmware ( re-lock , load new FW as PH98IMG.zip , flash it , unlock, etc)
Well, that didn't work for me, when I got to loading up hboot and it automatically updating the FW, it didn't do what the instructions said it would, it showed a dark blue bar near the top/right, waited for that to complete, then same thing but yellow, that completed and asked to reboot, but would only reboot to fastboot...
eventually I unlocked it again and it allowed me to return to my ROM (normal ICS/sense 3.6)
Sorry about this short story... lol ^
Basically I cannot for the life of me install any rom with success... I can't even restore the nandroid I made last night (before any of this) with success..
the CLOSEST thing to success I got was installing newts One XxX sense 4 rom, it booted, and will sit on the lock screen just fine, but when I try to unlock and go to settings to turn off animations (like instructed) it will freeze and reboot....
DO I need to install the newest FW???
OR what do I need to dooo?
Pls help! I am fairly familiar with android, as I had a D Inc before this, evervolv ICS etc etc....
Thanks alot anyone !
Click to expand...
Click to collapse
If you want to go back to a GB rom you need to reflash the boot image that came with it. If you want a sense 4.0 to work you need to flash the old firmware patch. For the patch I have attached it. Flash it via recovery and your rebooting on a sense 4.0 rom/ new firmware rom should be gone. (don't forget to follow the OP for Newts rom about disabling animations btw) for the boot images look to the op of the rom you are running.
cstrife999 said:
If you want to go back to a GB rom you need to reflash the boot image that came with it. If you want a sense 4.0 to work you need to flash the old firmware patch. For the patch I have attached it. Flash it via recovery and your rebooting on a sense 4.0 rom/ new firmware rom should be gone. (don't forget to follow the OP for Newts rom about disabling animations btw) for the boot images look to the op of the rom you are running.
Click to expand...
Click to collapse
Ok thanks for the reply, I did install the "old firmware patch" included with Newts XxX Sense 4 ROM, and I can successfully get the ROM to boot, it doesn't operate very well, and only for a few minutes because it will freeze and reboot. It doesn't allow me to get to the settings, no matter how fast I try to get there, it ALWAYS freezes before I can access the setting :/ ...
x70xchallengerx said:
Ok thanks for the reply, I did install the "old firmware patch" included with Newts XxX Sense 4 ROM, and I can successfully get the ROM to boot, it doesn't operate very well, and only for a few minutes because it will freeze and reboot. It doesn't allow me to get to the settings, no matter how fast I try to get there, it ALWAYS freezes before I can access the setting :/ ...
Click to expand...
Click to collapse
Hmm.. wow I'm lost. I had the same issues before I installed the patch, but after I didn't and it went fine. I'm going to have to think about this one for awhile.
cstrife999 said:
Hmm.. wow I'm lost. I had the same issues before I installed the patch, but after I didn't and it went fine. I'm going to have to think about this one for awhile.
Click to expand...
Click to collapse
Okay after flashing the ^above^ patch, the rom seems to work now, it didn't freeze so I was able to turn off animations and now it works might fine
Do you know by chance any good kernels for an ICS/Sense 4 ROM?
the stock one was draining faster than it was charging (while plugged in lol)
So I tried out the 1.836 OC kernel and it seems to be working fine, but I am interested more in battery life than performance right now, coming from the DInc, this phone is buttery smooth and doesn't REALLY need OC just yet (for me anyway)
Thanks for the help by the way!
Hello,
I have a huge Problem:
Last weekend i installed HSPL on my European HTC Titan and flashed Dynamics V2.0.
This Rom was extremely buggy and wasn't booting again after I turned it of once.
Then I tried the second Rom, Eburon V2.1, which had the same Problems.
After that I installed the European Stock 7.8, which worked better but also stopped working after I installed the official Facebook App.
The next one I used was EB Edition V2.6, worked for a whole day but stopped working after I installed an App from the market. Now the phone isn't booting any more.
I have always installed the right radio, which was in the download file.
My question is:
Are those custom roms so buggy or am I the only person who cannot install any Rom?
How can I fix these problems?
When there is no solution to that I have to sell my HTC Titan and buy an Android Phone again, where custom roms are really working...
P-Froggy said:
Hello,
I have a huge Problem:
Last weekend i installed HSPL on my European HTC Titan and flashed Dynamics V2.0.
This Rom was extremely buggy and wasn't booting again after I turned it of once.
Then I tried the second Rom, Eburon V2.1, which had the same Problems.
After that I installed the European Stock 7.8, which worked better but also stopped working after I installed the official Facebook App.
The next one I used was EB Edition V2.6, worked for a whole day but stopped working after I installed an App from the market. Now the phone isn't booting any more.
I have always installed the right radio, which was in the download file.
My question is:
Are those custom roms so buggy or am I the only person who cannot install any Rom?
How can I fix these problems?
When there is no solution to that I have to sell my HTC Titan and buy an Android Phone again, where custom roms are really working...
Click to expand...
Click to collapse
The answer to your question is; no! I'm currently running Eburon 2.1 and it's running as good as Eburon 2.0 which I've posted runs as smooth as a baby's butt! I'm not familiar with the European Stock 7.8 and I'm curious as to whether it's a custom ROM and designed to run with HSPL. Microsoft's Facebook app has always been buggy; however, within the People Hub it runs there too and all you have to go is go up under your settings and accounts and put your username and password there and you're good to go. As for your phone not booting, I have no idea.
What you need to do is literally start over; if...if...you do not have HSPL; double check this up under your bootloader. Attempting to install all these different ROMs begs the question if you re-locked your phone. Start from knowing for a fact your device is HSPL and has the words "CottulaH" on the bootloader screen. If it does, proceed to flashing your ROM but make sure you have at least a 50% battery charge and the installation process isn't disrupted for any reason. It's a toss up here as to which ROM is the best but you can't go wrong with either the Dynamic 2.0 or Eburon 2.x series.
P-Froggy said:
Hello,
I have a huge Problem:
Last weekend i installed HSPL on my European HTC Titan and flashed Dynamics V2.0.
This Rom was extremely buggy and wasn't booting again after I turned it of once.
Then I tried the second Rom, Eburon V2.1, which had the same Problems.
After that I installed the European Stock 7.8, which worked better but also stopped working after I installed the official Facebook App.
The next one I used was EB Edition V2.6, worked for a whole day but stopped working after I installed an App from the market. Now the phone isn't booting any more.
I have always installed the right radio, which was in the download file.
My question is:
Are those custom roms so buggy or am I the only person who cannot install any Rom?
How can I fix these problems?
When there is no solution to that I have to sell my HTC Titan and buy an Android Phone again, where custom roms are really working...
Click to expand...
Click to collapse
Sounds to me like you are getting bad flashes? Most WP7 custom roms are very stable and perform well 99% of the time. Been using the Dynamics rom on one of my Titans for 2 months or so with no problems whatsoever. The official FB app is buggy...I don't even both installing it.
Now, I'm not here to bash Android, but I dabbled into cooking some Android roms a few years ago. IMHO custom roms on WP are about 10x's more stable than any Android rom I've come across.
Ok, thanks for your replies, but just don't use the official Facebook app isn't a solution.
Could it be a solution to wait ca. one hour after installing a rom and let the phone configure everthing (maybe the phone needs that time)?
Because I set up all my accounts and install the apps I need directly after the rom has booted. Maybe it works if I wait before doing that.
P-Froggy said:
I set up all my accounts and install the apps I need directly after the rom has booted. Maybe it works if I wait before doing that.
Click to expand...
Click to collapse
Definitely - not. This is not a reason of your issue. I would offer to repeat the procedure of HSPL-ing. All customs work at least not worse than the stock roms.
I guess you may have the hardware issue. To be 100% sure - try to flash older stock - like 2.05 (with 16 radio). If it also does not work for you - than - pass your phone to the workshop - it's hardware.
AndrewSh said:
Definitely - not. This is not a reason of your issue. I would offer to repeat the procedure of HSPL-ing. All customs work at least not worse than the stock roms.
I guess you may have the hardware issue. To be 100% sure - try to flash older stock - like 2.05 (with 16 radio). If it also does not work for you - than - pass your phone to the workshop - it's hardware.
Click to expand...
Click to collapse
I had that idea after flashing Deepshining V3: The readme says that you have to activate "Trust all applications" in Root Manager, I wanted to do that, but I got an error message "No root access. Be sure you have fully unlocked your rom".
This was very weird, because that's the app needed to permit other Apps root access.
Also, none of the 3 soft buttons worked.
I waited a couple of minutes and restarted the phone several times, and suddenly the soft buttons worked and Root manager had root access.
P-Froggy said:
I had that idea after flashing Deepshining V3: The readme says that you have to activate "Trust all applications" in Root Manager, I wanted to do that, but I got an error message "No root access. Be sure you have fully unlocked your rom".
This was very weird, because that's the app needed to permit other Apps root access.
Also, none of the 3 soft buttons worked.
I waited a couple of minutes and restarted the phone several times, and suddenly the soft buttons worked and Root manager had root access.
Click to expand...
Click to collapse
Looks like the phone is swapping or caching something for ages. Maybe it's a Storage card malfunctioning. So hopefully the fixing will be just card replacement.
Mhh, ok, so what should I tell HTC? I can't say that I wanted to install custom roms, but none of them is working, so the phone needs a card replacement xD.
I tried installing Dynamics V2.0 again, and it works until I try to install WhatsApp, then it ends up in bootloops.
But the original stock 7.5 Mango worked without any problems. If the storage card is damaged, the original rom would also not work.
P-Froggy said:
But the original stock 7.5 Mango worked without any problems.
Click to expand...
Click to collapse
Did you install stock Mango AFTER you had tried all possible customs and it worked w/o issues?
AndrewSh said:
Did you install stock Mango AFTER you had tried all possible customs and it worked w/o issues?
Click to expand...
Click to collapse
No, before flashing a custom Rom everything worked, and since I tried to install custom roms I have nothing but Problems...
P-Froggy said:
No, before flashing a custom Rom everything worked, and since I tried to install custom roms I have nothing but Problems...
Click to expand...
Click to collapse
So - once again - try to flash stock. If it works - the problem is installing HSPL. If it does not work properly - just send the phone to workshop. Maybe it's just bad coincidence - the card died when you had installed HSPL....
AndrewSh said:
So - once again - try to flash stock. If it works - the problem is installing HSPL. If it does not work properly - just send the phone to workshop. Maybe it's just bad coincidence - the card died when you had installed HSPL....
Click to expand...
Click to collapse
Maybe it works now.
I did the whole HSPL Flash Thing again and now I was able to install WhatsApp on Dynamics V2.0.
It's only a small Progress, but it is one.
I will try the Rom tommorrow and if it crashes again, I go back to Stock 7.5.
similar problem
my Problem is, that after installing the Dynamics Rom, the device is just showing the white bootscreen with the htc-logo on it.
I am still able to enter bootloader mode, but I don't see any advantage in it.
The device was Vodafone-branded.
I hope someone can help me.
Did you follow the instructions at this link http://forum.xda-developers.com/showthread.php?t=1684912 before flashing the Dynamics Rom?? If you didn't debrand and unlock with HSPL you get stuck or have the wrong radio rom installed.
malvo26 said:
Did you follow the instructions at this link http://forum.xda-developers.com/showthread.php?t=1684912 before flashing the Dynamics Rom?? If you didn't debrand and unlock with HSPL you get stuck or have the wrong radio rom installed.
Click to expand...
Click to collapse
I did. But I think I know what I was doing wrong. The step between finishing HSPL installation and Dynamics setup...should have I installed the phone first and done a Zune synchro? Cause I didn't -.-
Just install the radio rom that comes with the Dynamics rom. That should do it. You don't need a Zune synchro afterwards unless you want to copy pictures, music, videos back to your HTC.
I just rooted my phone (Samsung S6 Edge [SM-G925P] running Android 6.0.1) this Friday and I have a couple of questions about using the CyanogenMod ROM and installing Xposed. To note, I am pretty, pretty new (I literally just rooted 2 days ago.
So my question about CyanogenMod is will it run on my rooted Samsung and is it dedoxed? I already have TWRP and SuperSU flashed and installed on my phone.
And my question about Xposed is will it run on my phone, as well with CyanogenMod, TWRP and SuperSU? I tried installing it with the original ROM on my phone, but that provided to be disasterous since it soft-bricked my phone, but I heard that was because my ROM was deodexed.
Hi NovaViper ! It depends. Cyanogenmod and other ROMS can come in two flavors: odexed or deodexed. The one on the official Cyanogenmod Website is deodexed. If you go on Cyanogemod's official website they don't have a ROM for Samsung Galaxy S6 / Edge. Check it out: http://download.cyanogenmod.org/ Look at the left to see supported devices. Unfortunately, it's not there. Some Galaxy S6 / Edge models do support Cyanogenmod but as for your model the SM-G925P there is still no official support for CM ROM. Check this link out: http://forum.xda-developers.com/gal...development/cyanogenmod-13-galaxy-s6-t3269984 Just out of curiosity, why do you want to install CM on your device?
I want to try CM because I heard it offers full customization.. I really would like to customize the lockscreen and colors of the UI especially and because it is deodexed, so I can also add Xposed. I have another ROM atm called Mostly Stock (its based on ROM but its deodexed and have a few changes to the stock UI, BUT it still has the parts I hate about the stock ROM). I specifically want CM because I haven't found any other ROM that offers full customization, deodxed for Xposed, and most importantly, is not like the stock ROM.
Oh, also with CM, I tried to install it but it said my device isn't support.. I tried the one from the link
If you want a full stable ROM for Samsung Galaxy S6 Edge and XPosed on it I would recommend this ROM: http://forum.xda-developers.com/galaxy-s6-edge/development/rom-carhdrom-1-t3111519. My friend has it on his ROOTED S6 Edge and it offers even more customization's then Cyanogenmod plus you can install XPosed on it. Give it a try.
Thanks I already flashed it but I notice that it isn't responsive to touch. I can interact with the buttons but no response to touch whatsoever. Seems like there isn't a ROM that works with my SM-G925P, the edge that rom works with is a G925F
Hmm, I thought it would work on your model. Try this: http://androidfreeroms.com/renegade-android-m-6-0-1-aroma-rom-sprint-samsung-s6-g925p/
I got the rom flashed and running.. but i cant seem to restore my messages from the samsung backup.. i can only get them from Textra (which doesnt export them). Also, i cant receieve text messages either.
Well, I finally got my messages backed up but.. I notice something else now. I had installed Xposed, which ended up giving me a bootloop and I had to factory and data reset, and reflash my stock rom. then I installed TWRP and then Renegade, but the mobile data isn't working anymore. Its just black the black bars.. I can't even find the Mobile Data enable button anywhere. (It works on stock rom though). To point out, mobile data WAS working before I installed Xposed. Right now, I'm reflashing my stock rom and seeing if it works.
--UPDATE 1--
Yeah, the stock mobile data works.. although I do have a theory on what could be going on
Theory 1: It could be I have to install my ROMS a certain way, initally, I had stock ROM, then I added the "Mostly Stock ROM" THEN I added Rengeade when you suggested it to me
Theory 2: Possibily signal strength/proxies (I'm doing this at on my school's wifi)
Theory 3: Something that Xposed has modified and its still there
--UPDATE 2--
I did the first theory and it worked successfully BUT.. I did remember that I had installed SuperSU soon after flashing twrp (which came after i flashed the stock rom).. Now I'm trying to see if that made a difference.
--UPDATE 3--
Ok, so it seems that it is a certain install order (tried with both superSU installed first and without). But I'm worried now about installing Xposed.. as I'm now nervous that it may end up messing up my phone again (It took a while for me to figure out how to get it back working.. as it ended up bricking with continuous looping and even factory resetting/clearing data off didn't work. I had to flash the stock rom for it to work again)
Interesting. My friends all have the International version which is G925F. Yours is Sprint ? Or some other cell phone provider ?
If your model goes haywire with simple custom rom installations and other apps than I wouldn't risk installing XPosed BUT if you do then try to follow these instructions... they work for your model:
https://xtremetricks.net/install-xposed-framework-android-6-0-6-0-1-marshmallow/
My phone is Sprint and I downloaded Xposed from the Magitsk app and it worked without bricking my phone.. I wonder why it was acting up
Strange thing, I seems I HAVE to install the 'Mostly Stock ROM' BEFORE I add Renegade.. the mobile data works to not work at all without installing Mostly Stock first.. How any idea how to fix this?
Well, I tried installing Magisk and it bricked my phone once again.. I'm really confused with whats going on. I have a backup of the stock ROM from SamMobile. What I want to do now is completely clear off ALL data from all of the roms and just start over, is that even possible? Also, if I delete the system files, do I HAVE to install the Stock ROM first, or can I just add the custom ROM and it will add the OS?
Well normally for rooted phones, you only add the custom ROM and it will automatically add the OS. I have no idea why you having so much problem with it. Did you unluck the bootloader ??
Yeah.. (I think), I made sure OEM Unlock is enabled and USB debugging is on.. Not sure what could be causing such problems with my phone.. I honestly wish I knew
What method did you use to root your phone and unlock the bootloader ?
I used the systemless method (installed TWRP, then installed the latest SuperSU which used the systemless method by itself) and I think I did.. there was an option where I had to enable (it was called OEM Unlocking, it was preventing me from flashing)
And I forgot to ask another question.. should I (and if such thing is possible) wipe the system/ folder and then install the custom ROM onto my phone without having to add the stock one at all?
What I would do if I were in your shoes is I would unroot and re-lock your bootloader again... see this article for unrooting: http://howunroot.com/unroot-supersu/samsung/galaxy+s6+edge+sm-g925p/5.0/ Now... once you unroot your phone... I don't think re-locking your bootloader will have any effect... but you can try to relock your bootloader and bring it to the original state meaning factory... once there just follow these instructions step by step: http://www.ibtimes.co.uk/skipsoft-toolkit-galaxy-s6-edge-root-unlock-restore-flash-stock-firmware-drivers-more-1517879 Once you root it and unlock your bootloader again, and after your install TWRP, go into TWPR, wipe dalvik cache, wipe system, wipe everything ... and then instlal the custom ROM that I gave you in the link, and it should be working find without problems. Try that and get back to me and update me... if you have any questions then just post it here and I will help you as much as i can.
I don't think I unlocked the bootloader because I looked up the instructions to how to unlock the bootloader and I didn't do that.. all I did was enable OEM unlock, is that the same thing as unlocking the bootloader? If not, how do I unlock the bootloader?