Related
I'm new to this forum but have got solutions for many of my questions from here. I own a Motorola defy MB525 (SOC Camera), tried to fiddle around with it in order to install custom ROM's and eventually screwed up in the process .After my failed attempts, was able to somehow get a working Indian Motorola Froyo SBF and fix my phone, which was otherwise not booting, that was a small victory . In the meanwhile, had been to Motorola Service Center to replace my broken glass. Got that replaced, however I wondered if the service center could somehow update it with official Defy+ ROM and that's when I screwed up completely.
They updated it with official 2.3.6 Defy+ ROM and now my Camera module is dead , battery lasts hardly for 5-6 hrs on stand by :crying: , which would otherwise last for 2 days on foryo and my phone model shows MB526. I wouldn't worry about the camera right now, but I want my battery last for a day atleast
Is there a way I can go back to my original froyo ROM which I doubt would be possible
Can someone help me on this ? any patch that I could update for battery issues? anything at all !
Thanks in advance.
Have you tried flashing the original SBF with RSD Lite?
RSD Lite is an App used by Motorola to Flash Smartphones. It can revive mismatched Nandroid/Fixed SBFs, Black Screens, failed flashes etc.
Even though is really, really hard to completely brick a Defy, it is possible; a corrupted SBF, power failure on a critical part of the formatting, or some weird issues while creating partitions can lead to a Bricked Defy. If you can, always flash your Defy from a laptop so the power is not an issue, use good cables, and be sure the PC doesn’t go to sleep when is not being used.
Also, when flashing SBFs, is normally advised to put your SBF in your PC Root directory (C:/ ) or whatever it is in your PC and rename it to a short name like Defy.sbf, why? Because sometimes the Path name is just too long and RSD Lite throws errors not allowing the phone to be Flashed.
Click to expand...
Click to collapse
Refer to this thread for details.
snandakishore said:
Can someone help me on this ? any patch that I could update for battery issues? anything at all !
Thanks in advance.
Click to expand...
Click to collapse
Dont worry....you will get back everything...but first i guess you will have to downgrade your defy....
may be this link would help
http://forum.xda-developers.com/showthread.php?t=1825064
Hope it works for you....flash only the correct sbf (Froyo one) and everything will be fine....
itsnotmeatall said:
Have you tried flashing the original SBF with RSD Lite?
Refer to this thread for details.
Click to expand...
Click to collapse
Yes, I have tried the same Froyo SBF that I tried to flash before using RSD Lite, but it didn't succeed this time. Later I tried many Defy+ ROM's aswell, nothing worked ... put a lot of effort to do all that and got fed up. Went back to the service center and they re-flashed it with their Defy+ ROM using RSD Netconnect which is something they use to flash the ROM's. May be this works a bit differently. It worked this time... now I'm stuck with this ROM, which drains my battery like anything and rendered my camera dead.
Well...thanks anywazz will try the steps suggested by the other mate...
Ok Simple Steps to Recover & Get ur camera working
snandakishore said:
Yes, I have tried the same Froyo SBF that I tried to flash before using RSD Lite, but it didn't succeed this time. Later I tried many Defy+ ROM's aswell, nothing worked ... put a lot of effort to do all that and got fed up. Went back to the service center and they re-flashed it with their Defy+ ROM using RSD Netconnect which is something they use to flash the ROM's. May be this works a bit differently. It worked this time... now I'm stuck with this ROM, which drains my battery like anything and rendered my camera dead.
Well...thanks anywazz will try the steps suggested by the other mate...
Click to expand...
Click to collapse
Dude I went from the steps in which u are currently stuck.
My defy 525 was not booting hence i went to authorized service center, Vashi, Navi Mumbai & Engineer over there has flashed defy plus rom on my mb 525. My camera was dead for 2 months. Now you are on BL7. Talk enough here are the steps...
Step 1:- Root your Defy, link is as below for BL7 ROOTING..
http://forum.xda-developers.com/showthread.php?t=1595013
Step 2 :- Flash any 2nd Boot Defy Custom Rom ( Quarks (cm10) / Epsys (cm 9 & cm7 ) / Kayants( cm10)
By the way I use Epsy 2nd boot for CM7**( ONLY WIFI IS NOT WORKING OTHERWISE ITS STABLE ROM )
WWW.DEFY-CM.NET
Use 26112012 rom
Thats the only way to your defy to use with camera. ** Camera will work only on 2nd boot rom
In case additional help is required then let me know..
Happy to Help...
Avi Tandel, Navi Mumbai, India.
Didn't work for me
avi_tandel said:
Dude I went from the steps in which u are currently stuck.
My defy 525 was not booting hence i went to authorized service center, Vashi, Navi Mumbai & Engineer over there has flashed defy plus rom on my mb 525. My camera was dead for 2 months. Now you are on BL7. Talk enough here are the steps...
Step 1:- Root your Defy, link is as below for BL7 ROOTING..
http://forum.xda-developers.com/showthread.php?t=1595013
Step 2 :- Flash any 2nd Boot Defy Custom Rom ( Quarks (cm10) / Epsys (cm 9 & cm7 ) / Kayants( cm10)
By the way I use Epsy 2nd boot for CM7**( ONLY WIFI IS NOT WORKING OTHERWISE ITS STABLE ROM )
WWW.DEFY-CM.NET
Use 26112012 rom
Thats the only way to your defy to use with camera. ** Camera will work only on 2nd boot rom
In case additional help is required then let me know..
Happy to Help...
Avi Tandel, Navi Mumbai, India.
Click to expand...
Click to collapse
Bro, Thanks a lot I see a ray of hope again
...I was able to root my device, somehow I was unable to flash the first file mentioned on link you gave but was able to flash the second one,still I could see that the device was rooted inspite of that.
Now, please help me with detailed instructions on how to go about flashing the new ROM with some youtube Video references will also help. Also what about the battery life ? have you been able to get a decent battery life after flashing the new ROM ? and will I be able to flash ROM's meant for MB525 or should I choose only ones meant for MB526 ? If so, then will it still drain my battery bcoz it will contain a GB kernel ? Will my device ever be same again?
Also, you have mentioned that ur wifi isn't working on the ROM that you are running, is it specific to that ROM ?
Plz dnt mind, I have asked too many questions.. I'm not well versed with all this....still learning from my mistakes.
Solved !
snandakishore said:
Bro, Thanks a lot I see a ray of hope again
...I was able to root my device, somehow I was unable to flash the first file mentioned on link you gave but was able to flash the second one,still I could see that the device was rooted inspite of that.
Now, please help me with detailed instructions on how to go about flashing the new ROM with some youtube Video references will also help. Also what about the battery life ? have you been able to get a decent battery life after flashing the new ROM ? and will I be able to flash ROM's meant for MB525 or should I choose only ones meant for MB526 ? If so, then will it still drain my battery bcoz it will contain a GB kernel ? Will my device ever be same again?
Also, you have mentioned that ur wifi isn't working on the ROM that you are running, is it specific to that ROM ?
Plz dnt mind, I have asked too many questions.. I'm not well versed with all this....still learning from my mistakes.
Click to expand...
Click to collapse
This thread can be closed.. I was able to successfully port to CM10 2nd boot Quarx ROM.
Thanks a lot for all the support !! long live XDA
Hello,
I can buy Axon7 on Aliexpress for around 330USD. Currently I'm using OPO and it is running just fine. I've got a few questions to you guys:
1. Are custom ROMs stable ( no bugs, battery drains, camera and sound is working like on stock )?
2. How far is Stock ROM from AOSP (recents, QS, settings) ?
3. Would you switch if you had OPO ?
4. Are there any news of update to Android O being planned ?
Thanks for the replies!
If you want front facing speakers, yes. If you like the huge amount of roms available for bacon, stay with that. I was on the opo and if it was not for the speakers on the a7 I would switch back.
There are still enough roms available, just not like for op5. Roms are stable
FunkyRasta said:
Hello,
I can buy Axon7 on Aliexpress for around 330USD. Currently I'm using OPO and it is running just fine. I've got a few questions to you guys:
1. Are custom ROMs stable ( no bugs, battery drains, camera and sound is working like on stock )?
2. How far is Stock ROM from AOSP (recents, QS, settings) ?
3. Would you switch if you had OPO ?
4. Are there any news of update to Android O being planned ?
Thanks for the replies!
Click to expand...
Click to collapse
Most ROMs are somewhat stable, but all of them have a couple of bugs like mic broken until you turn on and off the loudspeaker (you can fix that with macrodroid). And the stock ROM works better than the custom ROMs no doubt. But I found out that (if you care more about MP3 music than FLAC lossless) V4A is better on custom ROMs than stock. and you can get more than 7 hours SOT on custom ROMs if done right (normally people get 5 on the stock ROM)
The stock ROM is totally different than AOSP. The stock launcher has no dock just like Apple stuff but it also comes with an alternative with dock. The icons are crappy though. If you install Lawnchair from XDA you get a launcher better than Pixel and stock icons for almost all of the apps. Recents is just like AOSP but with a Clear all button and a lock to avoid you closing the app by swiping or via the button. pretty handy!
Now, I had something weird happen to me: When I got my Moto G 2 I used the stock ROM for like 3 days and switched to customs. I never even thought about going back to stock for all the poor phone's life (like 1.5 years). now with this one, I try a couple of ROMs for a month or two, get bored and return to stock. Always happens. Many people say the same, that they started liking the stock ROM even though it strays from AOSP a lot. But it has its fair share of good things, like auto power-on some minutes before your alarm goes off, scheduled on and off, a Dolby Atmos QS tile... It's not bad because it doesn't look like AOSP. not at all.
Besides, MiFavor 5.0 was released for the Chinese and it looks very good!
The phone has hardware keys but the Chinese version hasn't, hence the on screen keys on the screenshot.
Update to O: No news yet, though if it comes, expect the first 2 or 3 builds to be riddled with bugs. ZTE's devs barely know how to use a keyboard. Up to B04 Nougat they broke the Play store then fixed it, broke exFAT for SD cards, then fixed it... People made petitions (basically spamming "We want Android O" on a petition thread on the German forums) but nobody said anything close to a confirmation.
Would I switch from a OnePlus One? 2K AMOLED screen, SD820, speakers better than Samsung's $800 phones come with, QC3.0, for 330 dollars? definitely
The screenshots I attached are from the Chinese MiFavor 5.0 because that's what I'm using right now. You can install it via TWRP if you want.
one thing though: If you can get an A2017U (US version) instead of an A2017 (Chinese Aliexpress version) you're gonna thank me. The U version has so much more development than the G or Chinese... Even people say that sound is better on it. It costs 330 dollars on the US too.
This phone is easy to brick, be REALLY careful and read everything twice before doing stuff or you can end up with a DFU brick which is the most hardcore brick of them all.
Choose an username... said:
Most ROMs are somewhat stable, but all of them have a couple of bugs like mic broken until you turn on and off the loudspeaker (you can fix that with macrodroid). And the stock ROM works better than the custom ROMs no doubt. But I found out that (if you care more about MP3 music than FLAC lossless) V4A is better on custom ROMs than stock. and you can get more than 7 hours SOT on custom ROMs if done right (normally people get 5 on the stock ROM)
The stock ROM is totally different than AOSP. The stock launcher has no dock just like Apple stuff but it also comes with an alternative with dock. The icons are crappy though. If you install Lawnchair from XDA you get a launcher better than Pixel and stock icons for almost all of the apps. Recents is just like AOSP but with a Clear all button and a lock to avoid you closing the app by swiping or via the button. pretty handy!
Now, I had something weird happen to me: When I got my Moto G 2 I used the stock ROM for like 3 days and switched to customs. I never even thought about going back to stock for all the poor phone's life (like 1.5 years). now with this one, I try a couple of ROMs for a month or two, get bored and return to stock. Always happens. Many people say the same, that they started liking the stock ROM even though it strays from AOSP a lot. But it has its fair share of good things, like auto power-on some minutes before your alarm goes off, scheduled on and off, a Dolby Atmos QS tile... It's not bad because it doesn't look like AOSP. not at all.
Besides, MiFavor 5.0 was released for the Chinese and it looks very good!
The phone has hardware keys but the Chinese version hasn't, hence the on screen keys on the screenshot.
Update to O: No news yet, though if it comes, expect the first 2 or 3 builds to be riddled with bugs. ZTE's devs barely know how to use a keyboard. Up to B04 Nougat they broke the Play store then fixed it, broke exFAT for SD cards, then fixed it... People made petitions (basically spamming "We want Android O" on a petition thread on the German forums) but nobody said anything close to a confirmation.
Would I switch from a OnePlus One? 2K AMOLED screen, SD820, speakers better than Samsung's $800 phones come with, QC3.0, for 330 dollars? definitely
The screenshots I attached are from the Chinese MiFavor 5.0 because that's what I'm using right now. You can install it via TWRP if you want.
one thing though: If you can get an A2017U (US version) instead of an A2017 (Chinese Aliexpress version) you're gonna thank me. The U version has so much more development than the G or Chinese... Even people say that sound is better on it. It costs 330 dollars on the US too.
This phone is easy to brick, be REALLY careful and read everything twice before doing stuff or you can end up with a DFU brick which is the most hardcore brick of them all.
Click to expand...
Click to collapse
Wow, that's why I love XDA, thank you for this very helpful reply !
So on official LOS for example microphone during call doesn't work until I toggle loudspeaker ? That's is... Weird . So even if you are running custom ROMs you are coming back to stock because of bugs and features :/
I noticed on videos that launcher and icons sucks. Can I just install nova launcher on stock and use it without any problem ?
About Chinese and American versions. The ROMs doesn't work on all version, the a2017, U and G ? I did some reading and I know there are different bootstacks and stuff but I though the custom ROMs are compatible with all regions.
Is this brick recoverable ? Is there a flashtool that will always rescue me ?
Thanks again !
Yes you can flash nova launcher. It is an app! There is a flashtool for flashing and recovering from soft/hard bricks. The phone just rocks...
FunkyRasta said:
Wow, that's why I love XDA, thank you for this very helpful reply !
So on official LOS for example microphone during call doesn't work until I toggle loudspeaker ? That's is... Weird . So even if you are running custom ROMs you are coming back to stock because of bugs and features :/
I noticed on videos that launcher and icons sucks. Can I just install nova launcher on stock and use it without any problem ?
About Chinese and American versions. The ROMs doesn't work on all version, the a2017, U and G ? I did some reading and I know there are different bootstacks and stuff but I though the custom ROMs are compatible with all regions.
Is this brick recoverable ? Is there a flashtool that will always rescue me ?
Thanks again !
Click to expand...
Click to collapse
It's more complicated than that.
First of all: The modes on this phone are (were):
-EDL (Looks like it's completely off, it's not. You can flash special folder packages with MiFlash when you are in this mode)
-Bootloader mode (Fastboot. On A2017G and U they got rid of it. You can get it back by flashing a zip through TWRP, but if you update the stock ROM officially you'll lose it and will have to flash it again)
-Recovery. You can use axon7toolkit to unlock and install this. One-click tool like the one on Nexus 6 thread.
After you flash the Universal bootloader (for custom ROMs), your TWRP will get overwritten with an older one. Just keep a 3.1.1-0 img file and flash it in this crappy TWRP with Install -> Install image
-FTM. Seems that you get ADB when you are in this mode. Handy when you brick it horribly (no recovery) and can't access EDL. You just issue adb reboot edl and you should get to edl.
And last: DFU mode. Be REALLY careful with EVERYTHING, for example if you flash a system zip and TWRP says that you have no system installed, restore a backup, DON'T reboot! I had a DFU brick once and the two ways to recover from a DFU brick (No EDL, no fastboot, no recovery, very rarely FTM) are to discharge the phone completely and try to get into FTM, or take the phone apart and do the 4th category brick repair manual. I did the latter
But as of now no brick is unrecoverable. With A2017G's and U's you get a pretty overkill warranty, and you can return it claiming that it stopped working all of a sudden for example.
About the launcher: yeah, you can install whatever you like. I use Lawnchair.
And the ROM's work on all 3 phones, but it's the kernels that don't. Kernels work on the G and U on custom ROMs, but there is only one kernel that works for the U on stock, and none for the G. On the G the camera breaks on stock when you use a custom kernel. That's why I recommend you to get a U even if it's a little bit more expensive.
Is there a tool that will always save you from a brick? well there are many, but they will help you like 90% of the time. axon7tool is used to flash stuff to recovery or boot from EDL (you can flash TWRP for ex.), axon7toolkit can do some basic fastboot stuff, and MiFlash is the most useful, cause you can flash a full system directly from EDL and leave your phone in a functional state.So if, say, your digitizer breaks and you are on a custom ROM (and have an A2017G or A2017U, which have warranty) you can simply flash a working system and send it to fix.
If ZTE finds out that the phone has been tampered with (unlocked, opened, etc) they will charge you $80 but they'll fix it. If the phone doesn't even boot and it's a G they'll change it free of charge because of European laws
one more thing: you'll hate the quick settings thingy on stock. Try MiFavor 5.0 if you decide to stay stock, it's a Chinese ROM but with a bunch of work it can get pretty nice. I sent you a couple of screenies there
RUNNERX said:
If you want front facing speakers, yes. If you like the huge amount of roms available for bacon, stay with that. I was on the opo and if it was not for the speakers on the a7 I would switch back.
Click to expand...
Click to collapse
I would go for it because the newer LTE modems are so much better than any of the SD820 especially how poor both the Axon 7 and OP3 signals are compared to the SD821 and SD835. It is night and day in terms of connectivity. Performance wise it's also worth it.
You don't need to flash Nova launcher, I am with the Stock rom and use Nova as it. Just install it and use it as default launcher.
Envoyé de mon ZTE A2017G en utilisant Tapatalk
I have moto g4 plus (2016) and want to install custom rom but I have some questions and without knowing about them i can't take the risk.so please answer sir.
1) There is 2 Twrp custom recovery one is 32 bit and second is 64 bit, so which is best ?
2) if I use 32 bit and flash 64 bit rom ,can it possible?
3) if No then if am use 64 bit Twrp and flash 32 bit rom accidentally ,can it will brick my device??
4) i am currently on stock rom android 7.0 , today most custom rom is based on 9.0 ,if I flash pie custom rom and after months i want revert back to stock or Oreo rom ,can i will do it? Because in some custom rom there is note that after flashing this rom you can not revert back lower version of rom.
5) where is rom take space if I flash it, means in ram ,internal storage???
Thanks in advance.i know this question is help for other noob:good:
keval3492 said:
I have moto g4 plus (2016) and want to install custom rom but I have some questions and without knowing about them i can't take the risk.so please answer sir.
1) There is 2 Twrp custom recovery one is 32 bit and second is 64 bit, so which is best ?
2) if I use 32 bit and flash 64 bit rom ,can it possible?
3) if No then if am use 64 bit Twrp and flash 32 bit rom accidentally ,can it will brick my device??
4) i am currently on stock rom android 7.0 , today most custom rom is based on 9.0 ,if I flash pie custom rom and after months i want revert back to stock or Oreo rom ,can i will do it? Because in some custom rom there is note that after flashing this rom you can not revert back lower version of rom.
5) where is rom take space if I flash it, means in ram ,internal storage???
Thanks in advance.i know this question is help for other noob:good:
Click to expand...
Click to collapse
64bit recoveries can handle 32bit roms too. Use a 64bit recovery and everything is fine.
You cannot downgrade your bootloader from stock Oreo to stock nougat(your current Rom). Custom roms won't flash bootloaders,only stock roms.
Your whole flash storage of your device is divided into several partitions like system, data, boot, recovery, internal storage. That's why you have to deal with less memory in your internal storage(10 out of 16 for example).
You cannot(yeah, but don't do it) modify the partition size cause it's used to met some requirements.
The rom will be flashed into system/data partition, not internal storage but also uses ram of course
Thanks man , but can you elaborate my question on if I flash today custom rom on pie base and that is rumor on moto g4 plus that oreo update will launch soon and I also wait for it.so can i get that update if I am on pie custom rom.sorry for your answer ,i not understand that .
keval3492 said:
Thanks man , but can you elaborate my question on if I flash today custom rom on pie base and that is rumor on moto g4 plus that oreo update will launch soon and I also wait for it.so can i get that update if I am on pie custom rom.sorry for your answer ,i not understand that .
Click to expand...
Click to collapse
Yes you can get official Oreo update if you are on Pie custom rom. You just need to go back to stock rom or flash the stock Oreo rom manually like the soak test.
Can you give me Twrp 64 bit link and also which custom rom do you prefer on gaming performance , battery performance and customisable wise? Thanks a lot...
keval3492 said:
Can you give me Twrp 64 bit link and also which custom rom do you prefer on gaming performance , battery performance and customisable wise? Thanks a lot...
Click to expand...
Click to collapse
Here's a link for the 64 bit TWRP https://forum.xda-developers.com/mo...recovery-twrp-3-2-1-unofficial-touch-t3722206 for flashing both 32 bit and 64 bit custom ROMs and TWRP flashables.
Of course, unlocking your bootloader and flashing a custom ROM via TWRP will unavoidably erase your device, so back up as necessary. Be also aware that flashing a custom ROM may necessitate flashing magisk as well, to get your device Google certified again.
As for a particular ROM, your best bet is to have a look at each custom ROM's page and particularly the first page and the last few pages. Both of those should give you information on how suitable the ROM is from other user's reports for your usage and also give you an idea how often the ROM is updated.
It is necessary for flashing magisk? Because magisk root my mobile and I don't want to do it right now.
keval3492 said:
It is necessary for flashing magisk? Because magisk root my mobile and I don't want to do it right now.
Click to expand...
Click to collapse
For some apps, like banking apps for example, these apps may not function properly if they detect an unlocked bootloader, or if your device does not pass Google Play Store certification. If you're wanting to flash a custom ROM or a TWRP flashable, then you may have to consider flashing magisk for magisk hide. Magisk hide helps to hide your unlocked bootloader status and thus may get your device certified to use these apps. Up to you - depends on if you use apps that won't work if they detect your device has an unlocked bootloader.
Thanks sir for get me guide .What is athens when I open xda moto g4 plus and what is kernel and how it is important ??
keval3492 said:
Thanks sir for get me guide .What is athens when I open xda moto g4 plus and what is kernel and how it is important ??
Click to expand...
Click to collapse
I'm guessing by Athens you mean athene? If so, athene is the device codename for the Moto G4/plus (2016). Custom ROMs and software designed for athene should work on our services, though please check the release dates of such software. That also means software built for another device codename may not work.
A kernel is part of the software communicating between the hardware and the software. Custom ROMs will come with one usually. If you choose to flash another kernel, ensure you flash the correct type of kernel - there are kernels for stock 7.0/6.0 (Motorola), 7.1 (custom) and kernels for custom 8.1/9.0 ROMs. These may not be cross compatible and as such if you flash the incorrect kernel to your device your device may fail to boot (buy then that's what TWRP backups are for). Due to the lack of source code for stock 8.1, I've not seen custom kernels built for the stock Motorola 8.1 stock ROM yet.
Thank you sir for guide me about athene and kernel ,so i choose custom rom only made for athene and kernel is also built in with custom rom.
I am on stock oreo on moto g4 plus ,it is same process in oreo for unlock bootloader??
keval3492 said:
I am on stock oreo on moto g4 plus ,it is same process in oreo for unlock bootloader??
Click to expand...
Click to collapse
Please search within the correct rom thread https://forum.xda-developers.com/mo...4-oreo-soak-test-update-t3871136/post78966322
I did not get proper answer from link you send ,please help for this..
keval3492 said:
I did not get proper answer from link you send ,please help for this..
Click to expand...
Click to collapse
Should be the same process to unlock your bootloader, provided your motherboard is the same and you've still got your IMEI and software channel.
Can you elaborate what you said about motherboard and IMEI ,i am getting that method is same as nought but after that line i don't understand.
keval3492 said:
Can you elaborate what you said about motherboard and IMEI ,i am getting that method is same as nought but after that line i don't understand.
Click to expand...
Click to collapse
When you unlock your bootloader, you need the unlock key. The unlock key is likely generated from and linked to your motherboard; if your motherboard had been changed, then you'd have to get a new unlock key.
If your IMEI is still present in your device and working, the unlock key should work. Some users with existing IMEI issues may not be able to unlock their bootloaders.
Basically, if your device is the same when you requested the unlock key, and everything is working okay, then unlocking should be the same as Nougat without any further steps. Back up, boot to fastboot and connect your device to your computer, then enter the unlock key command - with your key - on your computer in the minimal ADB terminal.
I changed my motherboard once and after that I unlock my bootloader also ,but I brick my device by installing 64 bit rom on 32 bit twrp version and after that I lock my bootloader and start as a fresh device till now.
Same key is still working for me as I want unlock my bootloader??
keval3492 said:
I changed my motherboard once and after that I unlock my bootloader also ,but I brick my device by installing 64 bit rom on 32 bit twrp version and after that I lock my bootloader and start as a fresh device till now.
Same key is still working for me as I want unlock my bootloader??
Click to expand...
Click to collapse
Should be - use the same key as you used to unlock your bootloader before (after you had your motherboard changed). Be aware you will not be able to re-lock your bootloader if you unlock your bootloader at the moment. We do not have the Oreo firmware to lock stock Oreo devices or devices previously updated to stock Oreo firmware.
Oreo firmware means coding in CMD ??
Want to find a fix to all custom ROM's bootlooping on my SM-J320FN (did not bootloop before)
[
or alternatevly, i was wondering if modifying a some samsung galaxy SM-J320[something] nougat rom, to work on SM-J320FN would be possible (it has only android5.1.1 (lollipop) stock rom as far as im aware and i have searched quite a lot).
]
The thing is, i have the SM-J320FN (twrp and rooted) and for a while i ran various custom roms (based on nougat) on it with no problems. But then about a year ago it bootlooped on resurrection remix (which i had ran with not many problems for 1/2year). Then every custom rom (i tried RR, DotOS, ViperOS and more) began to give me a bootloop, only flashing the stock rom booted.
I wiped and formated everything i could, tried same country stock rom that i had originally and a different country one (thinking maybe the custom roms were not happy with something inside the stock rom that it was flashed after, but logically it does not seem even possible, as before flashing the custom one, the old one is wiped), but custom rom's just did not boot anymore. I could not log the boot either because it had boot animation but nothing showed in adb, i guess it did not get so far that it could connect with adb.
I suspect this may be caused by my camera not working (some hardware part most likely got damaged), because i think wiping my phone completely and flashing stock rom with Odin should restore every software part on the phone thus it would have to be something with hardware that's causing custom roms to bootloop, how else could the problem persist (i obviously might be wrong).
I don't remember when exactly the camera stopped working but i know for a fact that i had a custom rom at the same time, and it did not bootloop (for some time at least) and im also curious why this has not ever stopped the stock rom from booting if it is the case.
So basically what i wish i could do are two things. Firstly find what makes the stock roms able to boot correctly opposed to the custom ones. And secondly implement this to a similar models higher version rom or a custom rom (Nougat). Come to think of this, it seems a useful step to look how did the people that made these Nougat based rom's for SM-J320FN modify the rom so that it could run on it, the source code is open after all.
Why i want to have a higher android version on my phone? Because my countrys corona close contact detection app supports only 6.0 or higher and my banking app recently notified me that they will soon end support for my android version too (this is the real pusher for me as i use it very frequently and there is not really an alternative). And it would be nice to have some other apps too, that not compatible with Lollipop.
And yes, i know, just buying a newer phone would solve all my problems But im a minimalistic (and without money) person. The fact that i own a phone that is still working (or fixable) stops me mentally from buying a new one. Also as one would guess, i like tinkering with this kind of stuff (i study CS currently) and building a rom myself for my phone sounds like a cool and challenging project, as i have not done anything like this before (maybe this will help me: [guide]how to build/modify roms for samsung devices [7.0/6.0.1/maybe more]).
Anyways, i kinda got carried away with this post. But for now im tired and have to sleep so i'll just post this and will come back later to read this over, fix some mistakes (not a native english speaker) and add things i maybe missed.
If anyone read this through, im impressed and if you have the knowledge/time to answer then i Thank You in advance!
i need help i tried to install re dreaux but my phone bootloop on touch wiz custom rom so how can i fix that
Hi, I have flashed custom roms many times on my old phone and also my nubia device. I have flashed android 9 custom roms many times and has worked flawlessly. But this time when i tried to flash the same zip which i had flashed many times, the system booted up, but no sensors were working. WiFi was not working, bluetooth, accelerometer, gyroscope and even flashlight. I kinda freaked out and reverted to the stock rom thinking something might have gone wrong in the custom rom zip. When I reverted, to my dissapointment, almost all sensors were still not working! I tried downgrading and upgrading twrp versions but still no luck. I researched about this and people say it might be due to a damaged persist partition. Hence, I tried to flash the persist.img of my stock rom and it still doesn't work. I noticed that there are persist.zip flashable files for mi devices which seems to work. Is there any similar persist.zip which I can flash on my nubia z11 mini s? Or is there any other solution?
Any help would be very much appreciated. Thank you.
Redmi note 7 pro gyroscope issue!