Related
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.
Before i begin the actual topic, i feel like i need to share a story. a long, complicated story.
I feel like i can't go willy-nilly flashing things anymore. the USB cable (which btw is OEM) from my fassy is starting to go bad. odin recognizes it 1 out of 3 times, and every time i try to go back to stock, the operation fails half-way through. every other cable i've tried worked just fine, and i reinstalled samsung drivers four times. i believe i also had to reinstall windows at one point (not because of odin, i think something else broke/died) and that didn't help either. so, basically, if i flash a ROM, it has to be like perfect until i can borrow a cable.
a few nights ago, after deciding cm10.1 was too RAM-hungry for daily usage, i borrowed a cable and restored back to stock EH03 firmware. and let's face it, EH03 isn't the best thing ever, but it's usable. but i may go to jelly bean again because touchwiz is bad for your health
after discovering devil kernel (and getting some confirmation from udev that you need devil to properly get by on cm10.1), i have some questions about it:
1. from where should i download and flash it: DerTeufel's site or hhp's dev-host?
2. should i bother with Voodoo Color on jellybean?
3. at what RAM setting does it break 720p recording (as stated on DT's site)?
4. what other features should i know about that could possibly break everything?
by the way, i'm not really a n00b to android. i have a broken nook tablet and an lg vortex that went in the pool
skepticmisfit said:
Before i begin the actual topic, i feel like i need to share a story. a long, complicated story.
I feel like i can't go willy-nilly flashing things anymore. the USB cable (which btw is OEM) from my fassy is starting to go bad. odin recognizes it 1 out of 3 times, and every time i try to go back to stock, the operation fails half-way through. every other cable i've tried worked just fine, and i reinstalled samsung drivers four times. i believe i also had to reinstall windows at one point (not because of odin, i think something else broke/died) and that didn't help either. so, basically, if i flash a ROM, it has to be like perfect until i can borrow a cable.
a few nights ago, after deciding cm10.1 was too RAM-hungry for daily usage, i borrowed a cable and restored back to stock EH03 firmware. and let's face it, EH03 isn't the best thing ever, but it's usable. but i may go to jelly bean again because touchwiz is bad for your health
after discovering devil kernel (and getting some confirmation from udev that you need devil to properly get by on cm10.1), i have some questions about it:
1. from where should i download and flash it: DerTeufel's site or hhp's dev-host?
2. should i bother with Voodoo Color on jellybean?
3. at what RAM setting does it break 720p recording (as stated on DT's site)?
4. what other features should i know about that could possibly break everything?
by the way, i'm not really a n00b to android. i have a broken nook tablet and an lg vortex that went in the pool
Click to expand...
Click to collapse
You do not need devil to get on 1.cm10.1 cm has a built in kernel. 2.Voodoo kernel color is available for 4.2.2.
3.The max mem setting.
HOPE I HELPED
Sent from my SCH-I500 using Tapatalk 2
@skepticmisfit
1. from where should i download and flash it: DerTeufel's site or hhp's dev-host?
DT site does not have kernels for current 4.2.2 ROMs...
My kernel thread does
http://forum.xda-developers.com/showthread.php?t=2149067
2. should i bother with Voodoo Color on jellybean?
Don't see need for it but i have run this setting before and it looks great
From inside your galaxy s settings menu, (different ROMs put this in diff places)
View attachment 2167214
View attachment 2167220
3. at what RAM setting does it break 720p recording (as stated on DT's site)?
The 402 setting, but there is a patch if you search - hugemem patch - or - 720p video
-
http://forum.xda-developers.com/showthread.php?t=1815849
4. what other features should i know about that could possibly break everything?
Read my whole kernel thread post #1
Tons of info/tips
Also read the pages of the ROMs , it's the only way to learn.
...
Give a man a fish, and you feed him for a day; show him how to catch fish, and you feed him for a lifetime.
...
...
Hey guys,
I just got a few questions with this,
Will i lose my apps, theme and such when installing only a ROOT?
Also what do you guys prefer as ROOT method goes, Chainfire and Odin?
I've seen a ROOT BAT program a while ago that realy did everything for you, i just can't remember the name at the moment...
With that i would also like to ask what happens if i update my device? Will i still be able to update it when Samsung pushes a new update ?
Would i need a custom flash recovery? I used to have a phone wich i did it on, But as this is more of my expensiver phone i aint looking to realy risk it. and due all my apps info etc, has well over 150 apps.
Thanks everybody
Bump,
Sorry if nagging but i'm kinda in a rush, if anyone could help me a little?
I basicly know how you most likely root and stuff, just wanna be sure about a few things and what program/apk is best to get into the S3 at 4.3 firmware
Dr.Luigi said:
Hey guys,
I just got a few questions with this,
Will i lose my apps, theme and such when installing only a ROOT?
Click to expand...
Click to collapse
You might lose data.
Few things can be saved, because you have an official (so unrooted) device.
Also what do you guys prefer as ROOT method goes, Chainfire and Odin?
Click to expand...
Click to collapse
Odin is needed, Chainfire root is the most famous method.
I've seen a ROOT BAT program a while ago that realy did everything for you, i just can't remember the name at the moment...
Click to expand...
Click to collapse
Personally I did root with an automatized software, called Unlock Flash.
The better one is Framaroot, but I don't know how it works.
With that i would also like to ask what happens if i update my device? Will i still be able to update it when Samsung pushes a new update ?
Click to expand...
Click to collapse
You'll lost Samsung warranty (no more assistance support, excluded mine and use for software problems [emoji6]), update check and the access to some proprietary apps (You shouldn't be able to download/update from Galaxy Apps).
Normally when you root the device, a CWM custom recovery is included, otherwise you can simply flash via Odin the excellent Philz Recovery, so you'll be able to flash a new Samsung-based rom (ARHD, ArchiPort, Omega, Imperium... aborting the limited stock) or try the greatful AOSP roms (CyanogenMod, Omnirom, PacRom, etc.).
Also custom kernels (BOEFFLA, Googy Max, ArchiKernel and some others, I prevent to cite you outdated ones) and mods (everything!).
Would i need a custom flash recovery? I used to have a phone wich i did it on, But as this is more of my expensiver phone i aint looking to realy risk it. and due all my apps info etc, has well over 150 apps.
Thanks everybody
Click to expand...
Click to collapse
Highly recommended, as I said you need this to install a new rom and any other zip file.
For the rest... I haven't understood you.
Can you explain better last things?
Simone98RC said:
You might lose data.
Few things can be saved, because you have an official (so unrooted) device.
Odin is needed, Chainfire root is the most famous method.
Personally I did root with an automatized software, called Unlock Flash.
The better one is Framaroot, but I don't know how it works.
You'll lost Samsung warranty (no more assistance support, excluded mine and use for software problems [emoji6]), update check and the access to some proprietary apps (You shouldn't be able to download/update from Galaxy Apps).
Normally when you root the device, a CWM custom recovery is included, otherwise you can simply flash via Odin the excellent Philz Recovery, so you'll be able to flash a new Samsung-based rom (ARHD, ArchiPort, Omega, Imperium... aborting the limited stock) or try the greatful AOSP roms (CyanogenMod, Omnirom, PacRom, etc.).
Also custom kernels (BOEFFLA, Googy Max, ArchiKernel and some others, I prevent to cite you outdated ones) and mods (everything!).
Highly recommended, as I said you need this to install a new rom and any other zip file.
For the rest... I haven't understood you.
Can you explain better last things?
Click to expand...
Click to collapse
Well i would only be intrested in ROOT if i can keep all of my files, apps, widgets and such,
I would have done a new ROM if i wouldnt have had so many apps, it would take hours if not days to get everything back as it used to be would be a rather pain in the ***.
Thanks for your help!
Been a while when i unlocked my old device and rommed it undervoltaged it etc etc.
Dr.Luigi said:
Well i would only be intrested in ROOT if i can keep all of my files, apps, widgets and such,
I would have done a new ROM if i wouldnt have had so many apps, it would take hours if not days to get everything back as it used to be would be a rather pain in the ***.
Thanks for your help!
Been a while when i unlocked my old device and rommed it undervoltaged it etc etc.
Click to expand...
Click to collapse
My same problem: too many apps to be restored.
With MyBackupsPRO, the only working without root permissions, you can only keep some settings, contacts, SMS and MMS, then all your apps and games... but without any relative data.
Because as I said you're on an unrooted/official system.
I think you are using an external SD for documents and multimedia files, when you run the first start of your custom rom (highly recommend for the updates, instead the limited stock), be sure that the "Restore data from Google" option is checked.
A discrete help for you, better than nothing.
You have to think that when you did root, backups will be complete, via the greatful Titanium Backup or via recovery with Nandroid backup (my words should be useless if you already have experience with an old device).
Good hacking
As Samsung-based roms I suggest you Android Revolution HD 4.3 or ArchiPort to get the new and officially unsupported 4.4 system.
Pro:
-Compatibility with other Samsung devices;
-Much better camera stabilization than AOSP roms.
Con:
-Touchwiz is heavy for RAM memory and CPU performance;
-Many AOSP functions are completely removed or altered.
As AOSP rom I suggest you CyanogenMod 11, the M builds to have a more stable system, the nightlies for daily updates and less (but always enough) stability.
Pro:
-Latest updates daily/monthly available;
-Many features, AOSP and Cyanogen specific;
-Fully configurable, launcher can be completely replaced, at opposite of Samsung-based roms;
-Greater performance than Samsung-based roms.
Con:
-Some little bug;
-Poor compatibility with Samsung devices and proprietary apps.
As custom kernel, no better one than BOEFFLA: obviously OC and UV support, then lots of functions such "Touch to Wake", a great audio engine, zRAM support, a rich choice of governors and schedulers... it's available for Samsung and many AOSP roms.
Simone98RC said:
My same problem: too many apps to be restored.
With MyBackupsPRO, the only working without root permissions, you can only keep some settings, contacts, SMS and MMS, then all your apps and games... but without any relative data.
Because as I said you're on an unrooted/official system.
I think you are using an external SD for documents and multimedia files, when you run the first start of your custom rom (highly recommend for the updates, instead the limited stock), be sure that the "Restore data from Google" option is checked.
A discrete help for you, better than nothing.
You have to think that when you did root, backups will be complete, via the greatful Titanium Backup or via recovery with Nandroid backup (my words should be useless if you already have experience with an old device).
Good hacking
As Samsung-based roms I suggest you Android Revolution HD 4.3 or ArchiPort to get the new and officially unsupported 4.4 system.
Pro:
-Compatibility with other Samsung devices;
-Much better camera stabilization than AOSP roms.
Con:
-Touchwiz is heavy for RAM memory and CPU performance;
-Many AOSP functions are completely removed or altered.
As AOSP rom I suggest you CyanogenMod 11, the M builds to have a more stable system, the nightlies for daily updates and less (but always enough) stability.
Pro:
-Latest updates daily/monthly available;
-Many features, AOSP and Cyanogen specific;
-Fully configurable, launcher can be completely replaced, at opposite of Samsung-based roms;
-Greater performance than Samsung-based roms.
Con:
-Some little bug;
-Poor compatibility with Samsung devices and proprietary apps.
As custom kernel, no better one than BOEFFLA: obviously OC and UV support, then lots of functions such "Touch to Wake", a great audio engine, zRAM support, a rich choice of governors and schedulers... it's available for Samsung and many AOSP roms.
Click to expand...
Click to collapse
Thanks for the great help,
I aint realy sure yet realy,
But isnt there a way you can simple backup almost everything with the PC?
I thought that was faster, then root it and get those back up on the phone with the PC?
Youve made me thinking realy as my phone was getting slower, Samsung OS isnt that great quiet slow indeed,
I might just drop a few games i dont play realy, so i can get my faster phone back as it used to be.
I used to love tweaking my phone realy, till it broke due rain, was a quiet cheap phone 150e or so.
Do you mind giving your SKYPE or Steam? so i could ask you there, Its been 2 years when i did this, some are kinda floating around in my head but i just cant remember it all anymore.
http://forum.xda-developers.com/gal...msung-galaxy-s3-unified-toolkit-v8-0-t1979290
This is what i meant, Its simple and all in 1, just aint sure if its still up to date?
Via ADT Development Tool, you can do the "adb backup" command, but I think it will include the bootloader, so you'll restore the official and unrooted device state.
But I'm not sure, I never used to backup via PC.
Games are almost innocue, except for notification services who consume a bit of resources.
Can you tell me the heavier apps you're using?
According to your words, having too many apps you're not very satisfied about your performance... or I'm wrong?
Simone98RC said:
Via ADT Development Tool, you can do the "adb backup" command, but I think it will include the bootloader, so you'll restore the official and unrooted device state.
But I'm not sure, I never used to backup via PC.
Games are almost innocue, except for notification services who consume a bit of resources.
Can you tell me the heavier apps you're using?
According to your words, having too many apps you're not very satisfied about your performance... or I'm wrong?
Click to expand...
Click to collapse
Ye it used to be quiet a bit faster, Might be Samsung OS i forgot the name of the OS but anyhow, wizard or something,
Oh well, i will just do it i guess and i will see on the road what apps i need, the rest clearly seems that i dont need em if i never use em.
I'm guessing that the best would be Clockwork recovery and the SUroot? together with cyanogen ROM and buffalo.
As apps goes its basicly my home screen wich has quiet some widgets and such, all diffrent apps, in some folders like 100 apps etc.
Dr.Luigi said:
Ye it used to be quiet a bit faster, Might be Samsung OS i forgot the name of the OS but anyhow, wizard or something,
Oh well, i will just do it i guess and i will see on the road what apps i need, the rest clearly seems that i dont need em if i never use em.
I'm guessing that the best would be Clockwork recovery and the SUroot? together with cyanogen ROM and buffalo.
As apps goes its basicly my home screen wich has quiet some widgets and such, all diffrent apps, in some folders like 100 apps etc.
Click to expand...
Click to collapse
SuperSU is included in CF-Root and so is the most known, but Superuser (from Clockworkmod, the other Superuser is obsolete!) is a great open source alternative.
The best recovery is Philz, always based on CWM, but with extra and TWRP functions.
CyanogenMod yes, is the better choicr and also the easiest choice for root newbies.
Ps Buffalo is a kernel? If it's true, try BOEFFLA, is considered absolutely the best.
Simone98RC said:
SuperSU is included in CF-Root and so is the most known, but Superuser (from Clockworkmod, the other Superuser is obsolete!) is a great open source alternative.
The best recovery is Philz, always based on CWM, but with extra and TWRP functions.
CyanogenMod yes, is the better choicr and also the easiest choice for root newbies.
Ps Buffalo is a kernel? If it's true, try BOEFFLA, is considered absolutely the best.
Click to expand...
Click to collapse
Well i meant boeffla of course, Well i cant get it to work, What are the keys to get into TWRP recovery?
As in download mode it tells me its custom, but i cant get into it..
tryed quiet a few combis already
Dr.Luigi said:
Well i meant boeffla of course, Well i cant get it to work, What are the keys to get into TWRP recovery?
As in download mode it tells me its custom, but i cant get into it..
tryed quiet a few combis already
Click to expand...
Click to collapse
Edit:
Tryed again, i cant reboot if i did it would get the old recovery back, so in a push method it worked,
Now SuperSU, i might get a ROM but aint sure yet, Do kernels work on the stock rom aswell?
Dr.Luigi said:
Edit:
Tryed again, i cant reboot if i did it would get the old recovery back, so in a push method it worked,
Now SuperSU, i might get a ROM but aint sure yet, Do kernels work on the stock rom aswell?
Click to expand...
Click to collapse
Yes, BOEFFLA works also on stock rom (make sure to flash the correct zip file)... but I haven't understood your problem: can't reboot, old recovery back... what?
Simone98RC said:
Yes, BOEFFLA works also on stock rom (make sure to flash the correct zip file)... but I haven't understood your problem: can't reboot, old recovery back... what?
Click to expand...
Click to collapse
Ye nevermind that,
The problem is when i flashed my recovery, that when i reboot it switched automaticly back to the orginal stock recovery,
Only way to repair this was to not reboot, but goto the Philz recovery directly and reinstall the recovery program,
Also rooted it now,
So i can simple install Boefflo on my S3 international, With stock rom and ROOT, philz recovery?
If so that would be sweet ^^
As it should be more sufficient as far as battery goes, and a small overclock to like 1.6Ghz is reasonable ive heard,
1.8 is to high if i can believe those on some forums.
Since the last stable release you can overclock up to 1704 Mhz... and no more 1.5 Ghz step, I don't know the reason.
As I said, BOEFFLA works almost on every rom, but you habe to flash a different zip file for Samsung and AOSP roms.
Why can't you get a custom recovery? Are you sure to flash them reproducing properly the reported Odin guide (what to check in app, where to write file, etc.)?
It's a strange problem, rom "might" be cause by replacing the new recovery with the stock one, I think, but I'm not absolutely sure.
Simone98RC said:
Since the last stable release you can overclock up to 1704 Mhz... and no more 1.5 Ghz step, I don't know the reason.
As I said, BOEFFLA works almost on every rom, but you habe to flash a different zip file for Samsung and AOSP roms.
Why can't you get a custom recovery? Are you sure to flash them reproducing properly the reported Odin guide (what to check in app, where to write file, etc.)?
It's a strange problem, rom "might" be cause by replacing the new recovery with the stock one, I think, but I'm not absolutely sure.
Click to expand...
Click to collapse
Well like i said i've fixed that,
The standard way to flash doesnt work, As once i get booted in Samsung ROM, It fixes it, So you have to goto your Recovery immeaditly when youve flashed it, and flash it again in the custom recovery, and then it does work.
Well i will see, aint sure yet if i will do it the kernel and romming.
Thanks for the help
Dr.Luigi said:
Well like i said i've fixed that,
The standard way to flash doesnt work, As once i get booted in Samsung ROM, It fixes it, So you have to goto your Recovery immeaditly when youve flashed it, and flash it again in the custom recovery, and then it does work.
Well i will see, aint sure yet if i will do it the kernel and romming.
Thanks for the help
Click to expand...
Click to collapse
Here is also a great kernel. Check this out http://forum.xda-developers.com/gal...04-googy-max2-kernel-2-3-1-cm-camera-t2517875
I flashed Iced Bean 4.0 on my xperia sk17i and i think my touch screen died because of it, That rom has aroma installer and there was no my device on that list so i chose xperia pro. Installation was successful but touch screen didnt work. I reverted to stock using flashtools and it still doesnt work. Is there any way to fix this problem? i really need to try something so pleas suggest.
Just to be clear i'm not blaming on anybody, it is total my fault. I'm fully aware of risk installing custom roms so pleas help in any way you can
Thanks in advance
Have you tried to flashing a new kernel which was made for the phone? As far as I know drivers areusually stored within it in Linux / Unix systems so it might apply here for the touch screen as well.
i tried using command fastboot flash boot boot.img and generally did not work. I have unlocked bootloader. I had hard time finding guide to do that for my phone. I did revert to stock using flashtools and ftf file.
When you say fastboot didn't work, do you mean it could not connect to the phone? Where you in fastboot mode when you tried it?
I recently put the 4.4.4 AOPK rom (Link) on my phone and had trouble getting into fastboot to flash the required kernel, I think I solved that by using the flashtool.
If flashing the stock kernel doesn't fix the issue, perhaps using a custom one, which works with ICS, will help?
You can find some here: http://forum.xda-developers.com/showpost.php?p=47407355&postcount=3
-edit-
does this thread help you? [TUT] Fix broken touchscreen problem of xperia mini pro (SK17i,SK17a)
Fastboot worked fine, but any custom kernel after successful flashing didn’t work. I have installed managed to install xperialegacy cm11 it has custom kernel and it didnt fix touch screen. I will try the link you posted. On the side note i bought another sk17 today, yes i love this phone LOL xD
Yess, million times thank you . I made it using this tutorial
here is what you have to do for fix your Bricked touchscreen.
What you need for that is any custom rom with an aroma installer.
1. Flash suitable firmware with Flashtool ( i flashed .587 Because i used Zellycream rom V4 )
2. Then Install any ics Kernel that you like (I installed messa hybrid kernel v4.3 )
3: Then install Any rom that has Aroma installer in it and does support your device, via Cwm recovery (I installed Zellycream V4)
3. While installing the rom choose ST17i in Aroma instead of SK17i
4. Reboot after installation is completed.
5. Wait until phone is On homescree.Nopw touchscreen should work but h/w keyboard not
5. Reboot again into CWM install "keymap_for_pro_XXXX.zip
Link here For Keymap Mini pro
6. Reboot phone again.. Now keyboard and touchscreen should be working. Also options for h/w keyboard should appear now.
Good luck,
It did worked for me hopefully its also going to work for you.
Notice : At first your Touch might not responce how it was before, but give it a time it will work fine after some hours or day or it might never work like before.Mine touch screen worked normally after 8 hours of installing the rom with this method.
Click to expand...
Click to collapse
Now i have questions. Can for some reason touchscreen die again? and also which rom do you recommend for good battery and camera? i like stock but i find it tedious to root and remove all the unwanted apps only to free up a couple of MB and potential screw something
Update: I see that i need to flash a zip which fixes tochscreen. when installing new rom. Is this hardware or software problem?
It would surprise me if the screen died again from the same issue, as the harmful code should have been overwritten by the fix.
I am not a developer though, just a normal user with some basic linux knowledge.
I'd suggest trying out Real ICS. I think I ran it before I got my new phone (I just recently started using the Mini Pro again) and can't remember having any complaints back then.
Other than that you could just go through the rom list. There are some which claim to be focusing on performance, I haven't tried them myself though.
I currently use AOKP kitkat (with some modifications, see this post) but I cannot yet if I'll stick with it. Maybe gonna try out this one http://forum.xda-developers.com/showthread.php?t=2277199 next.
I think im going to stick to the stock for the now. Camera is the best there
I tried swapping motherboard from working sk17i to mine. MB is on stock 2.3 and bt is locked. To my surprises it did not work. Phone boot fine but touch screen does not work. I though this is a software problem, but i guess touch screen device has some controllers or something that were affected too.
Bucov said:
I tried swapping motherboard from working sk17i to mine. MB is on stock 2.3 and bt is locked. To my surprises it did not work. Phone boot fine but touch screen does not work. I though this is a software problem, but i guess touch screen device has some controllers or something that were affected too.
Click to expand...
Click to collapse
I'm confused. Didn't you solve the issue already?
If the damage is permanent, then maybe the touchscreen got damaged by using the wrong rom?
If you really want to have two working phones, you could get a replacent display from ebay. They start at around 30€ these days.
HI, All
I have had Nord 2 three months now. First Nord 2 was in service 3 times. So I got new device. Now this new has been two times at service. I have rooted both with TWRP (denniz) and Magisk of course.
I was wondering if TWRP is causing all the problems or is it just that Nord 2 does not like to be rooted.
And now I am thinking not to root but root has its benefits, so I guess I'll root but which method, TWRP or not.
Have you had problems after rooting? If you have, have you used TWRP and Magisk or just Magisk, no TWRP??
It would be nice if you would share your comments.
Thank you
My experience: if sent in for service, all they do is re-flash stock rom. This is where the problems start! I've been talking with an experienced guy from "The Phone Lab" in The Netherlands, which is the contractor for OnePlus repairs in my country.
Thing is, if your phone got messed up, THINGS REMAIN IN THE MEMORY after re-flashing stock. The ONLY thing that works to get a flawless CLEAN system (once even a TWRP-folder survived, but espacially the partition for your fingerprint etc. tempts to stay currupted in a way leading to several strange behaviours).
So to get a clean system, the "repaircompany" should:
- flash stock rom
- boot into STOCK recovery
- fully wipe
- flash stock rom again
NOW your device will work as stock WITHOUT strange behaviour. Mine has been stock flashed 5 times. I know what I am talking about. Every time different errors, which stopped / got eliminated after wiping inbetween.
The problem is, if you send your device to an OnePlus contractor or OnePlus servicepoint, they will not do this, since even THEY are not aware. Because after a stock flash the phone INTENTS to work normally. Strange behaviour sometimes even starts after set-up.
It's the most frustrating phone I ever had.
exis_tenz said:
My experience: if sent in for service, all they do is re-flash stock rom. This is where the problems start! I've been talking with an experienced guy from "The Phone Lab" in The Netherlands, which is the contractor for OnePlus repairs in my country.
Thing is, if your phone got messed up, THINGS REMAIN IN THE MEMORY after re-flashing stock. The ONLY thing that works to get a flawless CLEAN system (once even a TWRP-folder survived, but espacially the partition for your fingerprint etc. tempts to stay currupted in a way leading to several strange behaviours).
So to get a clean system, the "repaircompany" should:
- flash stock rom
- boot into STOCK recovery
- fully wipe
- flash stock rom again
NOW your device will work as stock WITHOUT strange behaviour. Mine has been stock flashed 5 times. I know what I am talking about. Every time different errors, which stopped / got eliminated after wiping inbetween.
The problem is, if you send your device to an OnePlus contractor or OnePlus servicepoint, they will not do this, since even THEY are not aware. Because after a stock flash the phone INTENTS to work normally. Strange behaviour sometimes even starts after set-up.
It's the most frustrating phone I ever had.
Click to expand...
Click to collapse
Hi and thank you for reply.
That was new to me but explains a lot. But also I remined that my 1st Nord2 got new motherboard (IMEI and S/N was different) and now my new Nord2 has new motherboard. So after replacing motherboard it should be as totally new. But still with 1st device I end up problems. I have not rooted my new Nord 2 because my intention was to find out if it is TWRP which is causing problems or is it the device - hardware vs OS after root rocess regardless TWRP or not.
Basically is Nord 2 working as "normal" devices after rooting or not.
To tell you the truth, I am fed up with this phone too
Hi jis251: we can shake hands. After the 4th (!) stockrom-flash by a OnePlus-servicecenter and still having strange behaviour (for example I was not able to set a fingerprint, the device-motor just kept shaking when I tried), they "decided" that my motherboard was broken. It was switched under warrantee and after that I messed up something and then a "regular" stock-flash didn't work either. You DO need to flash stock (@servicepoint or by yourself), then REBOOT into STOCK recovery, WIPE EVERYTHING, and flash stock again (with OnePlus-tool only they have).
The problem is that OnePlus (and their servicecenters) are NOT aware of this (and probably don't care). But once rooted with strange behaviour this is a must.
For now, fingers crossed, everything seems to work. I have TWRP 3.6 (Denniz) installed, Magisk 24.1, several modules (AFWall Boot AntiLeak, BuiltIn BusyBox, F-Droid privileged Extension, Magisk Bootloop Protector -not sure if this does anything, not tested-, Shamiko, Universal SafetyNet Fix and Zygisk LSPosed.
Also in LSPosed I have 4 modules activated: AFWall+, Disable FLAG_Seure, XPrivacyLua and GravityBox [R].
This setup works and passes SafetyNet without problem. Banking Apps work. The only thing I cannot get to work (keeps detecting root) is my Cupra App (for my car - same as Volkswagen App) as posted here: Cupra
The setup on my OnePlus 7 pro (A10) and Nord 2 5G (A11) - both stock roms - is the same. Both pass banking apps but the Volkswagen/Cupra app they do not. I can live with that as long as that is the only exception. It sucks, but privacy above all ;-)
after a week no broblem with my rooted nord 2 (twrp+ magisk canary) all working as well!
exis_tenz said:
My experience: if sent in for service, all they do is re-flash stock rom. This is where the problems start! I've been talking with an experienced guy from "The Phone Lab" in The Netherlands, which is the contractor for OnePlus repairs in my country.
Thing is, if your phone got messed up, THINGS REMAIN IN THE MEMORY after re-flashing stock. The ONLY thing that works to get a flawless CLEAN system (once even a TWRP-folder survived, but espacially the partition for your fingerprint etc. tempts to stay currupted in a way leading to several strange behaviours).
So to get a clean system, the "repaircompany" should:
- flash stock rom
- boot into STOCK recovery
- fully wipe
- flash stock rom again
NOW your device will work as stock WITHOUT strange behaviour. Mine has been stock flashed 5 times. I know what I am talking about. Every time different errors, which stopped / got eliminated after wiping inbetween.
The problem is, if you send your device to an OnePlus contractor or OnePlus servicepoint, they will not do this, since even THEY are not aware. Because after a stock flash the phone INTENTS to work normally. Strange behaviour sometimes even starts after set-up.
It's the most frustrating phone I ever had.
Click to expand...
Click to collapse
No way. I had my phone serviced at the same place and now I don't get OTA updates anymore and have to install them manually. My Bluetooth is also working less reliably. I had my suspicions but thanks for confirming it.
You DO need to flash stock (@servicepoint or by yourself), then REBOOT into STOCK recovery, WIPE EVERYTHING, and flash stock again (with OnePlus-tool only they have).
Click to expand...
Click to collapse
Just to be clear: is it possible to do by myself? Or is their tool required in this step? But yeah I was really hoping flashing would be as straight forward as with my previous OnePlus phones
Kenaestic said:
No way. I had my phone serviced at the same place and now I don't get OTA updates anymore and have to install them manually. My Bluetooth is also working less reliably. I had my suspicions but thanks for confirming it.
Just to be clear: is it possible to do by myself? Or is their tool required in this step? But yeah I was really hoping flashing would be as straight forward as with my previous OnePlus phones
Click to expand...
Click to collapse
Hi Kenaestic, so you are from The Netherlands as am I? Honestly, I don't know if you can do it yourself. Maybe with the tool from (I mean Pankspoo) you can put back all the partitions etc., get to some kind of "stock-state" and be able to wipe everything in stock recovery. But I am just not sure.
I am kind of "ready" with this phone. I am on version 17 (stock A11) and once rooted I decided to not take anymore OTA's. The phone is just way too unreliable. And it IS my daily driver for work, so I can't risk it. It freaks me out that I can't "normally" flash back a stock rom, an d I am too unexpierenced for ASB, commands, etc. I'm an user, not a programmer.
I got 5 (!) reflashes from The Phone Laband a new mainboard. Once, I got suspicious when a TWRP-folder was STILL THERE after a stock-re-flash. From that moment on, and all the problems with fingerprint and PIN-locks, that something just survives that factory flash (I always managed to mess things up by rooting).
Now the damn thing works (and really I still like it). I came from the OP7pro, but this device is just so much lighter and better in the hand (not top-heavy). It's snappy, it's fast. But in the meantime I will start working on my OnePlus 7 pro to get E/OS running and finally my goal is to de-google. Once that works, the OP Nord 2 will be sold and the OP7 pro will be my back-up phone.
The Nord 2 is good and I love it, but software is a failure. Never a MediaTek-device for me again.
exis_tenz said:
Hi Kenaestic, so you are from The Netherlands as am I? Honestly, I don't know if you can do it yourself. Maybe with the tool from (I mean Pankspoo) you can put back all the partitions etc., get to some kind of "stock-state" and be able to wipe everything in stock recovery. But I am just not sure.
I am kind of "ready" with this phone. I am on version 17 (stock A11) and once rooted I decided to not take anymore OTA's. The phone is just way too unreliable. And it IS my daily driver for work, so I can't risk it. It freaks me out that I can't "normally" flash back a stock rom, an d I am too unexpierenced for ASB, commands, etc. I'm an user, not a programmer.
I got 5 (!) reflashes from The Phone Laband a new mainboard. Once, I got suspicious when a TWRP-folder was STILL THERE after a stock-re-flash. From that moment on, and all the problems with fingerprint and PIN-locks, that something just survives that factory flash (I always managed to mess things up by rooting).
Now the damn thing works (and really I still like it). I came from the OP7pro, but this device is just so much lighter and better in the hand (not top-heavy). It's snappy, it's fast. But in the meantime I will start working on my OnePlus 7 pro to get E/OS running and finally my goal is to de-google. Once that works, the OP Nord 2 will be sold and the OP7 pro will be my back-up phone.
The Nord 2 is good and I love it, but software is a failure. Never a MediaTek-device for me again.
Click to expand...
Click to collapse
Haha ja zeker So this is something I have noticed as well. I'm in the same boat as you. I'm not a programmer and I come from a device where flashing was way easier. But for some reason this phone has persistent data on it that can not be reset or wiped. Maybe it was intended as a security measure. When you flash TWRP you probably noticed you can not boot into it without a commandline on your computer. Otherwise it will completely ignore the volume down + power combination and go straight to booting the OS. So I'm guessing OnePlus made it harder to tamper with the recovery. But for rooting it's only confusing, gives me headaches but most importantly; when you accidentally remove the ADB server authentication you're screwed because there is no recovery to boot into. I'm really hoping the miracle workers in the modding community find a way to work around these things. Because I first just thought it's kinda janky because they used a few work arounds to get TWRP running as fast as possible when the phone came out. But now I just don't know anymore. Anyway, I have an appointment with ThePhoneLab tomorrow and I'll report back if it did anything. Cheers.
exis_tenz said:
My experience: if sent in for service, all they do is re-flash stock rom. This is where the problems start! I've been talking with an experienced guy from "The Phone Lab" in The Netherlands, which is the contractor for OnePlus repairs in my country.
Thing is, if your phone got messed up, THINGS REMAIN IN THE MEMORY after re-flashing stock. The ONLY thing that works to get a flawless CLEAN system (once even a TWRP-folder survived, but espacially the partition for your fingerprint etc. tempts to stay currupted in a way leading to several strange behaviours).
So to get a clean system, the "repaircompany" should:
- flash stock rom
- boot into STOCK recovery
- fully wipe
- flash stock rom again
NOW your device will work as stock WITHOUT strange behaviour. Mine has been stock flashed 5 times. I know what I am talking about. Every time different errors, which stopped / got eliminated after wiping inbetween.
The problem is, if you send your device to an OnePlus contractor or OnePlus servicepoint, they will not do this, since even THEY are not aware. Because after a stock flash the phone INTENTS to work normally. Strange behaviour sometimes even starts after set-up.
It's the most frustrating phone I ever had.
Click to expand...
Click to collapse
I agree to some point... When it comes to rooting and updating when rooted this Phone is a p.i.a. If kept stock it is not to bad... But you want root for a reason. I think it is because of the mediatek processor. But I am struggling with it too. I am on A16, with TWRP, not rooted. I want to go back to stock (locked bootloader), but I am having a hard time to understand how to do it. I would appreciate a step by step guide.... The ones on XDA so-far haven't helped me any further...
Ik zit dus in hetzelfde schuitje... (sorry for the Dutch) really curious if "The Phone lab" can fix it
The Phone Lab can only re-flash stock (not repair). You'll loose all data.