Related
Okeydokey. I installed a custom ROM ( VillainRom3.0 ) last night, and it has messed up a few things :/. Most apps randomly blank out and crash instantly - wifi doesn't work, phone freezes.
I'm rather new, and most of this stuff does confuse me; anyone able to post simple step by step of how to get a suitable kernal for VillainRom3.0 ?
EDIT: It also removed CWM and Superuser from the App menu :/
MegaJoshh- said:
Okeydokey. I installed a custom ROM ( VillainRom3.0 ) last night, and it has messed up a few things :/. Most apps randomly blank out and crash instantly - wifi doesn't work, phone freezes.
I'm rather new, and most of this stuff does confuse me; anyone able to post simple step by step of how to get a suitable kernal for VillainRom3.0 ?
EDIT: It also removed CWM and Superuser from the App menu :/
Click to expand...
Click to collapse
I was running villain rom with the standard chainfire kernel that most start with and that was stable - I must say though I wasn't too impressed with it - recently installed Westcrip's Resurrection ICS remix and boy am I happy I did! - if you want villain though just search for a compatible rom using the last letters from your baseband version - that normally does the trick! Good luck
I've found an old backup laying around, and got to installing that, so VillainRom is no longer on their. I'm back to a rooted firmware and that's it.
BUT: Now my computer ( nor any other ) recognises when It's pluggedin via USB :/.
I have this issue flashing some newer roms lately, not sure what it is.
To get back to a stock rom/rooted rom use the methods listed under the dev section of your phone that are the initial root direction using odin or something similar.
clarity1 said:
I have this issue flashing some newer roms lately, not sure what it is.
To get back to a stock rom/rooted rom use the methods listed under the dev section of your phone that are the initial root direction using odin or something similar.
Click to expand...
Click to collapse
Cheers, I ended up getting a working firmware on it, but I still have certain issues that are ****ting me >_>
Hey guys !
I haven't used my DHD for a while but last weekend a friend lost his phone and asked me to borrow my good ol DHD.
So I thought I would update it to CM11 but there seems to be an issue with it.
I made a clean install of CM11 M10 Rom with PA gapps Pico
I had troubles booting but finally worked after a while. Managed to install some apps and gave the phone to my friend.
I told me today that the phone wouldn't stop rebooting to the HTC screen but wouldn't fully boot.
I'm not so much familiar with what's going on with the DHD since I haven't used it for almost 2 years.
I've search the thread of the rom but couldn't really find anything.
If anyone has an idea on what might but the problem, it would be great to know so my friend can have a working phone.
Cheers !
Arnohsgti9300 said:
Hey guys !
I haven't used my DHD for a while but last weekend a friend lost his phone and asked me to borrow my good ol DHD.
So I thought I would update it to CM11 but there seems to be an issue with it.
I made a clean install of CM11 M10 Rom with PA gapps Pico
I had troubles booting but finally worked after a while. Managed to install some apps and gave the phone to my friend.
I told me today that the phone wouldn't stop rebooting to the HTC screen but wouldn't fully boot.
I'm not so much familiar with what's going on with the DHD since I haven't used it for almost 2 years.
I've search the thread of the rom but couldn't really find anything.
If anyone has an idea on what might but the problem, it would be great to know so my friend can have a working phone.
Cheers !
Click to expand...
Click to collapse
If S-ON than it's obvious. If not than out of my league. Probably update recovery or radio could possibly sort out your problem.
Though can you please share Hboot image of your device.
No, as far as I know it's s-off. I updated recovery before flashing. Don't know about radio. And I don't know how to share Hboot either...
up
Hi everyone,
i had the " stupid idea " to update my oppo find 7a to official coloros 2.0 KK !
I didn't like it so much and then i decided to go back to Dirty Unicorn BUT once done that i could not get any NETWORK working!
Following some other user suggestion i went back to 1.2.4 (they say booloader is unlocked) but still couldn't have network working!
SO far the only way to have my network back is to load COLOROS 2.0 KK..
can anyone please tell me how can i have my network BACK on any other rom than coloros 2.0??
thank you so much!
simika said:
Hi everyone,
i had the " stupid idea " to update my oppo find 7a to official coloros 2.0 KK !
I didn't like it so much and then i decided to go back to Dirty Unicorn BUT once done that i could not get any NETWORK working!
Following some other user suggestion i went back to 1.2.4 (they say booloader is unlocked) but still couldn't have network working!
SO far the only way to have my network back is to load COLOROS 2.0 KK..
can anyone please tell me how can i have my network BACK on any other rom than coloros 2.0??
thank you so much!
Click to expand...
Click to collapse
SOLUTION
FINALLY!!!!!!!!!!!
FIRST i had to find the OLD (1.2.3 ) oppo recovery (link: http://d-h.st/pfR )
i INSTALLED it from fastboot
than always in fastboot i did FASTBOOT OEM UNLOCK
then i boot into recovery.. installed Oppo coloros 1.2.4 ( seems to have bootloader unlocked )
now ive 1.2.4 and i'm gonna install back dirty unicorn.. probably will work !!!!!!!!
YES I CONFIRM.. it works..
so for all of those having problems with color os 2.0 kk and decide to go back to other ROM(and having issues on calling ) just do as i did ..
i hope it helps others
simika said:
SOLUTION
FINALLY!!!!!!!!!!!
FIRST i had to find the OLD (1.2.3 ) oppo recovery (link: http://d-h.st/pfR )
i INSTALLED it from fastboot
than always in fastboot i did FASTBOOT OEM UNLOCK
then i boot into recovery.. installed Oppo coloros 1.2.4 ( seems to have bootloader unlocked )
now ive 1.2.4 and i'm gonna install back dirty unicorn.. probably will work !!!!!!!!
YES I CONFIRM.. it works..
so for all of those having problems with color os 2.0 kk and decide to go back to other ROM(and having issues on calling ) just do as i did ..
i hope it helps others
Click to expand...
Click to collapse
@simika
Glad you got it working again.
I have a friend who bought his Find 7a x9007 second hand with no mobile connectivity. It has ColorOS 2.0.1i installed and I was wondering if the situation is similar to yours. I will try to fix it tonight but I have one question. At which point did you get your connectivity back? After installing ColorOS 1.2.4 or after installing Dirty Unicorns?
The easiest guaranteed way to get connectivity and custom rom support back up and running after an official KitKat update is to restore the phone to ColorOS 1.2.5 using the Sahara package from here: http://d3bzg7dsosz4ht.cloudfront.net/OTA/Find7/FIND7WX_12_A.09_140810.tgz
After restoring the phone via Sahara it will be fully reset and you can do whatever you want from there.
MrColdbird said:
The easiest guaranteed way to get connectivity and custom rom support back up and running after an official KitKat update is to restore the phone to ColorOS 1.2.5 using the Sahara package from here: http://d3bzg7dsosz4ht.cloudfront.net/OTA/Find7/FIND7WX_12_A.09_140810.tgz
After restoring the phone via Sahara it will be fully reset and you can do whatever you want from there.
Click to expand...
Click to collapse
Thanks. Downloading now. However, I need to ask two more things. Is this Sahara package international or chinese version? I'm asking bcs I'm going the flash it to a chinese model (x9007). Finally, is it OK to flash it with "TWRP mod for ColorOS" or do I need ColorOS recovery?
Edit:
I've got the file but it's not a flashable zip. How do I flash it? Google search gave me no results!
Edit2:
I found the instructions. Now I only need confirmation that it will work on the x9007. Any feedback will be much appreciated.
Edit3:
I got too impatient and used the tool anyway. It worked like charm. I saw the progress bars while flashing all partitions and in the end it got green. I rebooted the phone and it had gone back to ColorOS 1.2.5i but, guess what, I still had no GSM/3G signal. Then I thought, hey, this tool flashed an international version, so I probably need a Chinese baseband. So I used modded TWRP and flashed modem pack 1.2.5 by zixuan. Rebooted and to my great disappointment, I still had no signal!!! So, I decided to go one step further. I installed a genuine Chinese ROM (v1.2.0) and after rebooting, I still had no signal!!!
I'm about to tell my friend to sell his phone for parts, unless you, gurus, have any further suggestions...
we
dreccon said:
Thanks. Downloading now. However, I need to ask two more things. Is this Sahara package international or chinese version? I'm asking bcs I'm going the flash it to a chinese model (x9007). Finally, is it OK to flash it with "TWRP mod for ColorOS" or do I need ColorOS recovery?
Edit:
I've got the file but it's not a flashable zip. How do I flash it? Google search gave me no results!
Edit2:
I found the instructions. Now I only need confirmation that it will work on the x9007. Any feedback will be much appreciated.
Edit3:
I got too impatient and used the tool anyway. It worked like charm. I saw the progress bars while flashing all partitions and in the end it got green. I rebooted the phone and it had gone back to ColorOS 1.2.5i but, guess what, I still had no GSM/3G signal. Then I thought, hey, this tool flashed an international version, so I probably need a Chinese baseband. So I used modded TWRP and flashed modem pack 1.2.5 by zixuan. Rebooted and to my great disappointment, I still had no signal!!! So, I decided to go one step further. I installed a genuine Chinese ROM (v1.2.0) and after rebooting, I still had no signal!!!
I'm about to tell my friend to sell his phone for parts, unless you, gurus, have any further suggestions...
Click to expand...
Click to collapse
i too have this connectivity issue that even sahara package could not fix. i do sometimes get signal using 2.0.x roms or 5.0.x roms but i cant call or send sms, in phone status it shows mobile network unknown
wish there was a fix for this
thirdzcee said:
we
i too have this connectivity issue that even sahara package could not fix. i do sometimes get signal using 2.0.x roms or 5.0.x roms but i cant call or send sms, in phone status it shows mobile network unknown
wish there was a fix for this
Click to expand...
Click to collapse
Well, in my case, it seems that someone had tampered with the antenna RF cable. As soon as I replaced it, the phone worked normally and I had no problem installing and using Nameless Lollipop over a Chinese baseband. My friend is happy with his phone now!
dreccon said:
Well, in my case, it seems that someone had tampered with the antenna RF cable. As soon as I replaced it, the phone worked normally and I had no problem installing and using Nameless Lollipop over a Chinese baseband. My friend is happy with his phone now!
Click to expand...
Click to collapse
weird, after many attempts i finally gave up, but to my surprise when i woke up one moring my phone just had reception now, was able to call and text and have data and i dont have a clue what happened, the last thing i did was not flash sahara packacge, but flash 2.0.3beta then downgrade to 1.2.3 then flash 1..2.7i but i didnt get any signal back until that morning.. weird but im happy i got signal back and now happily running CoS 2.0.7
Hello, i hope there is someone that can help me with this problem i have.
I rooted and used cm12 sometime in the begining og 2015, then i unified the phone and used another rom(dont remember what), but it crashed sometime last summer and went black.
And after i have had it i started reading and found some posts and figured out i could try to get life in it befor cristhmas, and i found this: community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra=&page=1[/url]
And i found a computer with win 7 on, and i got the phone back to life, but the rom stopped at language or region settings at installing.
and the i tried using nameless-recovery-twrp-2.8.7.0-find7-20151220 and the rom will start up, but i dont have wifi, radio or IMEI.
And i found someone that gave me oneplus.qcn this file, but i cant get my phone in to diagnostic mode, becouse the code *#801# is not working on my phone(Only *#06# is working).
I have tried different roms and recovery, but onlu namless rom is working in that way that i can start a rom (color os 1.4i up to 1,8i) over 1.8 will not start.
So i would be wery happy if there is someone that can help me fix it..
And i apologies for my English, but hopfully it is possible to understand.
Kindly regard
Johan
JPSimon said:
Hello, i hope there is someone that can help me with this problem i have.
I rooted and used cm12 sometime in the begining og 2015, then i unified the phone and used another rom(dont remember what), but it crashed sometime last summer and went black.
And after i have had it i started reading and found some posts and figured out i could try to get life in it befor cristhmas, and i found this: community.oppo.com/en/forum.php?mod=viewthread&tid=23067&extra=&page=1[/url]
And i found a computer with win 7 on, and i got the phone back to life, but the rom stopped at language or region settings at installing.
and the i tried using nameless-recovery-twrp-2.8.7.0-find7-20151220 and the rom will start up, but i dont have wifi, radio or IMEI.
And i found someone that gave me oneplus.qcn this file, but i cant get my phone in to diagnostic mode, becouse the code *#801# is not working on my phone(Only *#06# is working).
I have tried different roms and recovery, but onlu namless rom is working in that way that i can start a rom (color os 1.4i up to 1,8i) over 1.8 will not start.
So i would be wery happy if there is someone that can help me fix it..
And i apologies for my English, but hopfully it is possible to understand.
Kindly regard
Johan
Click to expand...
Click to collapse
Hey there! Sad to hear that you have bricked your phone and lost your imei.
Im no expert, but have you retry the method provided in oppoforums? I suggest that you retry it once more.
Have tried
DingleBell said:
Hey there! Sad to hear that you have bricked your phone and lost your imei.
Im no expert, but have you retry the method provided in oppoforums? I suggest that you retry it once more.
Click to expand...
Click to collapse
Yes, i have tried it several times, and i only get to the same point every time.
JPSimon said:
Yes, i have tried it several times, and i only get to the same point every time.
Click to expand...
Click to collapse
Have you tried reverting back to stock ColorOS rom? Try to flash stock ColorOS 2.0.8i or ColorOS 2.1.5i to your phone. Usually when things go bad, people usually revert back to stock coloros rom and that fixed their problems as it fixed mine before this.
DingleBell said:
Have you tried reverting back to stock ColorOS rom? Try to flash stock ColorOS 2.0.8i or ColorOS 2.1.5i to your phone. Usually when things go bad, people usually revert back to stock coloros rom and that fixed their problems as it fixed mine before this.
Click to expand...
Click to collapse
The phone will only start up when i use colosos 1.4 up to 1.8, when i use higher or lower it will not start up..
And i can not use color recovery, only with nameless-recovery-twrp-2.8.7.0-find7-20151220..
Hi, recently I got this a32 from a friend because my phone is broken, but there's a problem. Some time ago she updated this phone from android 11 to 12 and the touchscreen completely stopped working, i got the phone yesterday hoping to fix this problem but i updated to android 13 (oneui 5.1) and it still doesnt work, i tried do downgrade to android 11 but its impossible and for last i tried to install twrp and then a gsi (following a guide here on the forum), i noticed that in twrp the touchscreen does actually work but after installing lineage os 20 it didn't again, is there any hope for this phone?
persifele said:
Hi, recently I got this a32 from a friend because my phone is broken, but there's a problem. Some time ago she updated this phone from android 11 to 12 and the touchscreen completely stopped working, i got the phone yesterday hoping to fix this problem but i updated to android 13 (oneui 5.1) and it still doesnt work, i tried do downgrade to android 11 but its impossible and for last i tried to install twrp and then a gsi (following a guide here on the forum), i noticed that in twrp the touchscreen does actually work but after installing lineage os 20 it didn't again, is there any hope for this phone?
Click to expand...
Click to collapse
Did you contacted the assistance? Seems a bad driver or kernel problem.
zSyntex said:
Did you contacted the assistance? Seems a bad driver or kernel problem.
Click to expand...
Click to collapse
no because i dont know how much it would cost and the phone isnt mine either so if possible i dont want to spend money
persifele said:
no because i dont know how much it would cost and the phone isnt mine either so if possible i dont want to spend money
Click to expand...
Click to collapse
We couldn't provide support for the hardware, mostly because you said that you've tried to reset the device and flash the stock ROM again.
If this doesn't fix the hardware issue, the assistance is the only way.
Probably a failure batch etc.
to be completely honest i flashed the stock rom by a backup i did before flashing lineage os, so if there's a guide on how to flash one ui 5.1 in order to have a clean installation it would be rlly helpful
persifele said:
to be completely honest i flashed the stock rom by a backup i did before flashing lineage os, so if there's a guide on how to flash one ui 5.1 in order to have a clean installation it would be rlly helpful
Click to expand...
Click to collapse
Simply download the latest firmware from SamLoader (Bifrost) and use Odin in order to flash it.
Tell me if you couldn't flash
I tried installing the latest firmware with odin, everything went fine but nothing, touch still doesn't work, i think tomorrow i'll take it to someone to fix it.
persifele said:
Hi, recently I got this a32 from a friend because my phone is broken, but there's a problem. Some time ago she updated this phone from android 11 to 12 and the touchscreen completely stopped working, i got the phone yesterday hoping to fix this problem but i updated to android 13 (oneui 5.1) and it still doesnt work, i tried do downgrade to android 11 but its impossible and for last i tried to install twrp and then a gsi (following a guide here on the forum), i noticed that in twrp the touchscreen does actually work but after installing lineage os 20 it didn't again, is there any hope for this phone?
Click to expand...
Click to collapse
what model of a32 is it? SM-A325F or??
One ui 5.1 firmware cannot be downgraded. I currently daily drive crdroid from nazim on one ui 5.1 firmware. my touch has never had issues. May be a hardware issue. Maybe a custom kernel would solve it. I built one for A325F that works on one ui 5.1 firmware. Give it a try from here. Its permissive btw. Just flash it in twrp. Although take a backup of boot before flashing incase something goes wrong
Captain_cookie_200 said:
what model of a32 is it? SM-A325F or??
One ui 5.1 firmware cannot be downgraded. I currently daily drive crdroid from nazim on one ui 5.1 firmware. my touch has never had issues. May be a hardware issue. Maybe a custom kernel would solve it. I built one for A325F that works on one ui 5.1 firmware. Give it a try from here. Its permissive btw. Just flash it in twrp. Although take a backup of boot before flashing incase something goes wrong
Click to expand...
Click to collapse
Hi, I tried to flash from twrp but it just gives me a series of "unable to unlock /dev/block/mmcblk0p14" and so on, btw yes its a A325F.
persifele said:
Hi, I tried to flash from twrp but it just gives me a series of "unable to unlock /dev/block/mmcblk0p14" and so on, btw yes its a A325F.
Click to expand...
Click to collapse
its fine. those are normal. if the flash suceeds at last that is all that matters
Captain_cookie_200 said:
its fine. those are normal. if the flash suceeds at last that is all that matters
Click to expand...
Click to collapse
The problem is that after flashing it goes in a bootloop where it says that "this phone's bootloader is unlocked, press power button" i do it and it starts the galaxy logo with above the writing "the software you are using isnt official, you may have problems with security and features" and it gets stuck there, rn i flashed the original firmware with odin and the phone is working but touch still isn't.
EDIT: i forgot to add that when i flashed with odin everything was going fine until the phone's screen went from green to red, i've never seen this so idk if i should be worried or not (phone is still running normally).
persifele said:
The problem is that after flashing it goes in a bootloop where it says that "this phone's bootloader is unlocked, press power button" i do it and it starts the galaxy logo with above the writing "the software you are using isnt official, you may have problems with security and features" and it gets stuck there, rn i flashed the original firmware with odin and the phone is working but touch still isn't.
EDIT: i forgot to add that when i flashed with odin everything was going fine until the phone's screen went from green to red, i've never seen this so idk if i should be worried or not (phone is still running normally).
Click to expand...
Click to collapse
oh weird . you are using one ui 5.1 right? whats the firmware name or version. Also those things def look like hardware issue. you should get it checked.
Captain_cookie_200 said:
oh weird . you are using one ui 5.1 right? whats the firmware name or version. Also those things def look like hardware issue. you should get it checked.
Click to expand...
Click to collapse
yes i'm on android 13 one ui 5.1, the firmware is A325FXXU3DWB8_A325FOXM3DWB8_ITV. I got it checked and they said that it cant be fixed because i cant downgrade from android 13 to another one, i could try installing crdroid like you and if you could send me a guide it would be amazing, thanks again.
persifele said:
yes i'm on android 13 one ui 5.1, the firmware is A325FXXU3DWB8_A325FOXM3DWB8_ITV. I got it checked and they said that it cant be fixed because i cant downgrade from android 13 to another one, i could try installing crdroid like you and if you could send me a guide it would be amazing, thanks again.
Click to expand...
Click to collapse
Just flash twrp for this thing from here. Follow steps on that thread to decrypt your storage and stuff. Then download crdroid gsi. Extract it. flash img file to system partition in twrp. Afterwards wipe dalvik, cache, internal storage
(internal storage is not necessary). You should be able to boot into twrp sucessfully.
I also have some workarounds and the stuff i use for my daily driving in this thread here.
If you need any further help i'll be here to assist.
Captain_cookie_200 said:
Just flash twrp for this thing from here. Follow steps on that thread to decrypt your storage and stuff. Then download crdroid gsi. Extract it. flash img file to system partition in twrp. Afterwards wipe dalvik, cache, internal storage
(internal storage is not necessary). You should be able to boot into twrp sucessfully.
I also have some workarounds and the stuff i use for my daily driving in this thread here.
If you need any further help i'll be here to assist.
Click to expand...
Click to collapse
Oh um i am sorry looks like thread doesnt contain instructions to that. I'll write em here myself
When you boot into twrp after flashing go to advanced and go to terminal
type
multidisabler
run it two times. Then go to format. Then press format data and type yes. Once its done reboot back into twrp again. Then flash crdroid as i said in my post above. and format the things i said. you should be able to boot into crdroid normally.
Captain_cookie_200 said:
Oh um i am sorry looks like thread doesnt contain instructions to that. I'll write em here myself
When you boot into twrp after flashing go to advanced and go to terminal
type
multidisabler
run it two times. Then go to format. Then press format data and type yes. Once its done reboot back into twrp again. Then flash crdroid as i said in my post above. and format the things i said. you should be able to boot into crdroid normally.
Click to expand...
Click to collapse
I followed everything you said, flashed crdroid but nothing, touch still doesnt work if not for when im twrp, i tried to flash kernel again and it still didn't so i don't know what to do anymore.
persifele said:
I followed everything you said, flashed crdroid but nothing, touch still doesnt work if not for when im twrp, i tried to flash kernel again and it still didn't so i don't know what to do anymore.
Click to expand...
Click to collapse
So uh looks like you have no options left. I just want to make sure. could you list the exact methods you used to flash the fw. Along with where u got the fw from? Lets see if the fw itself is broken or something.
Also this is very unrelated and time wasting. but you could try download one ui 5 firmware. Then extract super.img from ap. unsparse it and extract vendor.img and flash it to vendor partition using twrp. Then decrypt by typing
multidisabler twice in terminal as said in my previous post. Check if maybe an older version one ui 5 firmware has this issue fixed. one ui 5's kernel boots so one ui 5 vendor should work on 5.1 as well. It may not work but worth a try. you could also try doing this with android 12 firmware if that fixes it. if you do not have a linux machine availible i'll do it for you and upload the files for both firmwares here. Otherwise if its a hardware issue get your phone replaced or try getting the screen replaced. if still nothing happens ig switching to a new phone would be the only optiion.
So, to flash the firmware I used odin, the fw was from sammobile.
For trying to extract super.img and so on idk how to actually do it so if you could explain it would be really helpful. Btw trying to flash android 12 firmware is impossible because samsung made it so,
thank you again for the help.
persifele said:
So, to flash the firmware I used odin, the fw was from sammobile.
For trying to extract super.img and so on idk how to actually do it so if you could explain it would be really helpful. Btw trying to flash android 12 firmware is impossible because samsung made it so,
thank you again for the help.
Click to expand...
Click to collapse
i use samfw mostly for my firmwares. anyways. You need a linux machine nearby. ubuntu or arch. any distro based on them would work.
first you need to unsparse the super.img
for that we use
simg2img super.img super-raw.img
then we can use lpunpack or mount it to get our vendor.
we flash it using twrp and then we run multidisabler twice like we did when we first flashed gsi.
As you said above if you could do it for me it'd be awesome because i don't have a pc with linux rn.