Develop Bugs

[9/9/12][Recovery]Clockworkmod v6.0.1.3

This is just a recovery I compiled from the latest available code from the CM10 source. It does not offer any major upgrade in function from ACL's latest cwm recovery, but is slightly aesthetically different.
Installation:
Download from link below, flash with fastboot
Code:
fastboot flash recovery recovery.img
Bugs:
recovery.log may show these errors:
Code:
failed to open /sys/class/android_usb/android0/state: No such file or directory
but it does not affect usb or mass storage afaik.
Download:
recovery_cwr_6.0.1.3.img - 3.36 MB 9912
Credits: Everyone involved in Android development.
Feel free to report any bugs and enjoy.

works great, but one question: what is the thing you are asked first time you click reboot system now and what should i have answered yes or no, cause i clicked no?

Ranomez said:
works great, but one question: what is the thing you are asked first time you click reboot system now and what should i have answered yes or no, cause i clicked no?
Click to expand...
Click to collapse
I have not seen that prompt before.. what did it say? If you don't know what it does, answering "no" is probably a good idea

jianC said:
I have not seen that prompt before.. what did it say? If you don't know what it does, answering "no" is probably a good idea
Click to expand...
Click to collapse
something about after reboot rom may flash stock recovery, do you want to disable recovery flash, thats the question i get

Ranomez said:
something about after reboot rom may flash stock recovery, do you want to disable recovery flash, thats the question i get
Click to expand...
Click to collapse
In that case, just choose "no".

sorry to revive this old thread, but i just realised this recovery has a big problem and wanted to warn anyone who may want to try it: most blckups made by it have md5 mismatch, i meant i got that error at 14 out of 15 backups created.
EDIT1: i had a look at the backup folder and as far as i can see some .img files are not generated (i think cache and recovery) and also the nandroid.md5 is not generated, but that is easy to fix by generating it by urself throu adb.

Battery loading Led not working
The Led is not working with this recovery while charging.
I guess the Battery is not loading, too.
Edit - This is only, when phone is off. -
Hope this can be fixed.
regards

Sorry about the bugs/lack of support but I do not have a Touch Pro 2 anymore.
The most help I can offer is uploading the device tree that I used to compile recovery in CM10 (and potentially compile a booting version of CM10 but that has never been accomplished due to kernel issues).
https://github.com/jianC/android_device_htc_rhodium

jianC said:
Sorry about the bugs/lack of support but I do not have a Touch Pro 2 anymore.
The most help I can offer is uploading the device tree that I used to compile recovery in CM10 (and potentially compile a booting version of CM10 but that has never been accomplished due to kernel issues).
http://ge.tt/1gVK1FS/v/0?c
Click to expand...
Click to collapse
If you would like to play with the 3.4.17 kernel for S&Gs, you can find it in this thread at the bottom of the first post.
Maybe some of the kernel issues will be fixed there? I can probably get the git for it if you would want it.

wizardknight said:
If you would like to play with the 3.4.17 kernel for S&Gs, you can find it in this thread at the bottom of the first post.
Maybe some of the kernel issues will be fixed there? I can probably get the git for it if you would want it.
Click to expand...
Click to collapse
Thanks for the links, but I do not have a rhod for testing anymore.. maybe someone adventurous could take a stab at it .

Android 4.3 OTA Security Update Boot Loop Issue and Solution

I hit a boot loop snag on my Galaxy Nexus GSM after installing the recent 4.3 OTA security update. I had no issues with the initial Android 4.3 release, but the security update did something that made my device hit a boot loop. I could restore from a Nandroid backup, but about once a day I would hit the boot loop snag again. After dealing with daily restores for a couple days I dug into it a bit and found that when the phone gets mired in a boot loop I can fix it by deleting two files.
The trick is you have to be using TWRP on the recovery partition because that will let you use a file manager to delete the two files. There may well be other solutions but that's been the easiest for me. The two files which need to be deleted are:
/data/system/locksettings.db
/data/system/locksettings.db-shm
If you use Google Wallet you'll see a similarly named file there "locksettings.db-wal" -- DO NOT DELETE THIS ONE, just the two above.
If this helps anyone please post so if it doesn't people won't waste their time -- THANKS!

Told my cousin she said that it worked like a charm! What do those two files actually do?
Sent from my Galaxy Nexus using Tapatalk 4

Vekhez said:
Told my cousin she said that it worked like a charm! What do those two files actually do?
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
To be honest -- I have no idea. I found this by pure trial and error after a totally non-related post pointed to the /data/system folder.
The files appear to get recreated when the phone reboots so it's probably generated from the system partition ultimately.
From what I know now, it appears as though SuperSU is causing this somehow. Is your cousin using SuperSU do you know?
There was a recent update to version 1.60 of SuperSU which was supposed to address this and I think it did for some users, perhaps Nexus 4 users only, but I definitely have this issue still even with the newest 1.65 version.
I've ended up created a Tasker script to delete the files on reboot because I was tired of having to repetitively reboot into TWRP and manually delete them. It works well but I'd much rather fix the underlying cause.

sansnil said:
To be honest -- I have no idea. I found this by pure trial and error after a totally non-related post pointed to the /data/system folder.
The files appear to get recreated when the phone reboots so it's probably generated from the system partition ultimately.
From what I know now, it appears as though SuperSU is causing this somehow. Is your cousin using SuperSU do you know?
There was a recent update to version 1.60 of SuperSU which was supposed to address this and I think it did for some users, perhaps Nexus 4 users only, but I definitely have this issue still even with the newest 1.65 version.
I've ended up created a Tasker script to delete the files on reboot because I was tired of having to repetitively reboot into TWRP and manually delete them. It works well but I'd much rather fix the underlying cause.
Click to expand...
Click to collapse
Yeah, they are using SuperSU...they are still on 1.5, I'll tell them to update.
Sent from my Galaxy Nexus using Tapatalk 4

Vekhez said:
Yeah, they are using SuperSU...they are still on 1.5, I'll tell them to update.
Sent from my Galaxy Nexus using Tapatalk 4
Click to expand...
Click to collapse
Thanks, Vekhez. Let me know if that hopefully fixes the problem for them. If it does it means I'm "special" not in a good way!

sansnil said:
Thanks, Vekhez. Let me know if that hopefully fixes the problem for them. If it does it means I'm "special" not in a good way!
Click to expand...
Click to collapse
Nope it didn't.. Same problem.
Sent from my Galaxy Nexus using Tapatalk 4

Vekhez said:
Nope it didn't.. Same problem.
Click to expand...
Click to collapse
Thanks for this. I'm sorry for your cousin but happy for me because that means it's not something unique or specific to my device.
This is helpful -- I'm going to post this over in the SuperSU thread and see if Chainfire will pick it up and look into it.
Stay tuned...

sansnil said:
Thanks for this. I'm sorry for your cousin but happy for me because that means it's not something unique or specific to my device.
This is helpful -- I'm going to post this over in the SuperSU thread and see if Chainfire will pick it up and look into it.
Stay tuned...
Click to expand...
Click to collapse
Ok, so it turns out this is actually being caused by the app "Delayed Lock" if you use a pattern lock. If you use a PIN/password lock it won't happen, but if you use a pattern lock with the current version of Delayed Lock on a Galaxy Nexus this boot loop issue will occur.
I've opened a bug with the Delayed Lock Dev so hopefully he'll find a way to fix it. In the meantime, choices are to either disabled/uninstall Delayed Lock (hate!) or switch to a PIN or password lock setting.

Hey guys,
I had the same problem and found out that it could be solved, without losing any data, by directly flashing the update.
Here's what I did: http://forum.xda-developers.com/showthread.php?t=2427613
Best of luck.

Porting LineageOS 14 to the d710

Disclaimer: I am not a ROM developer. I am a developer and Linux user, but I know next to nothing about creating Android ROMs. Whole other world to me.
I'm wondering if all three of us Epic 4G Touch users left might be able to get a working port of LineageOS 14 on our aging handsets.
The good news:
I just loaded the Official LineageOS 14 for i9100 20170419 nightly on my d710, and IT WORKS
...almost.
The bad news:
The ROM boots up, everything works and looks normal except for:
Wi-Fi - Settings app spins with message "Turning Wi-Fi on..."
Menu Button
Home Button
Now, I'm wondering if there is a way to fix these problems. I prefer on-screen navigation anyway, so that's probably an easy "fix." But Wi-Fi will probably be trickier. I assume it's kernel related, but I can't find any Nougat kernels for this device, so that will likely be the most difficult part.
Thoughts? Anyone else out there have any input or want to give this a crack?
Links:
https://wiki.lineageos.org/devices/i9100/build
https://wiki.lineageos.org/devices/i9100/install
https://web-beta.archive.org/web/20161224202958/https://wiki.cyanogenmod.org/w/Build_for_d710
https://web-beta.archive.org/web/20161224192644/https://wiki.cyanogenmod.org/w/Doc:_porting_intro
https://github.com/LineageOS/android_device_samsung_d710/tree/cm-12.0
https://github.com/LineageOS/androi...4.1/arch/arm/configs/lineageos_d710_defconfig
https://github.com/Lanchon/TWRP-Patcher-SGS2
https://github.com/Lanchon/REPIT
https://forum.xda-developers.com/ep.../rom-cyanogenmod-11-official-nightly-t2852074

Can you pm me your rom you used, i may be able to figure out how to get wifi to work, i dont have access to a computer right now but i can take a look at the rom you used when i get to one

svaethier said:
Can you pm me your rom you used, i may be able to figure out how to get wifi to work, i dont have access to a computer right now but i can take a look at the rom you used when i get to one
Click to expand...
Click to collapse
Link is in the OP. Here it is again: https://forum.xda-developers.com/galaxy-s2/general/rom-t3555834
Direct link to the download page: https://download.lineageos.org/i9100

How did you get past the 07 error then? Ive tried clearing everything from system to dalvik cache and nothing gets me to install the rom to look into the wifi issue properly

svaethier said:
How did you get past the 07 error then? Ive tried clearing everything from system to dalvik cache and nothing gets me to install the rom to look into the wifi issue properly
Click to expand...
Click to collapse
I don't know what you're talking about. I don't get an error.
The ROM flashes without modification. Make sure you have an up-to-date TWRP with the i9100 crossflash patch: https://github.com/Lanchon/TWRP-Patcher-SGS2

Ive tried flashing twrp onto my device using the guide that tells you how, even after editing the installer script to have the SPH-D710 line in it it aborts the installation

svaethier said:
Ive tried flashing twrp onto my device using the guide that tells you how, even after editing the installer script to have the SPH-D710 line in it it aborts the installation
Click to expand...
Click to collapse
I followed lots of advice from this thread: https://forum.xda-developers.com/epic-4g-touch/help/help-getting-stock-rooted-4-1-2-to-cm11-t3384832
I believe the method that finally worked for me was: Odin to EL29 rooted, Philz recovery, TWRP, CM11.
That's where I was before I tried the i9100 LOS 14.1 ROM.

I can get a twrp with a different rom then cm11 but that twrp doesnt have the img installation feature on it

svaethier said:
I can get a twrp with a different rom then cm11 but that twrp doesnt have the img installation feature on it
Click to expand...
Click to collapse
If you have root in CM11, you can use Flashify to flash the new TWRP .img file.

My E4GT still works, more than glad to throw my hand in the pot to make something happen. Haven't used the S2 in years so it's not updated, currently running an old build of CWM and a CM11 nightly with iso-rec support. If you could bring me up to speed on what I need to get from where I am to a newer recovery(TWRP preferred) and your ROM I'll start playing around with it. Last time I searched all of this to update left me more confused than anything with it being mixed up with the i9100 and i777 information as well.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
My E4GT still works, more than glad to throw my hand in the pot to make something happen. Haven't used the S2 in years so it's not updated, currently running an old build of CWM and a CM11 nightly with iso-rec support. If you could bring me up to speed on what I need to get from where I am to a newer recovery(TWRP preferred) and your ROM I'll start playing around with it. Last time I searched all of this to update left me more confused than anything with it being mixed up with the i9100 and i777 information as well.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
You should be able to flash the latest TWRP (for i9100) using Flashify. Beware that I have not been able to get TWRP to mount my external SD card, so any files you want to flash in TWRP need to be stored on internal memory. Everything else works perfectly. Mounting USB storage in TWRP works well, and that's how I've been able to get new files on the phone when I needed to.
After installing TWRP, make sure you run Lanchon's crossflash patch on it: https://github.com/Lanchon/TWRP-Patcher-SGS2
I used
Code:
lanchon-twrp-patcher-20160417-crossflash-d710.zip
to enable flashing d710 and i9100 ROMs.

flamadiddle said:
You should be able to flash the latest TWRP (for i9100) using Flashify. Beware that I have not been able to get TWRP to mount my external SD card, so any files you want to flash in TWRP need to be stored on internal memory. Everything else works perfectly. Mounting USB storage in TWRP works well, and that's how I've been able to get new files on the phone when I needed to.
After installing TWRP, make sure you run Lanchon's crossflash patch on it: https://github.com/Lanchon/TWRP-Patcher-SGS2
I used
Code:
lanchon-twrp-patcher-20160417-crossflash-d710.zip
to enable flashing d710 and i9100 ROMs.
Click to expand...
Click to collapse
Yeah, I took another look last night, the information available now clarifies things that seemed a mess back when I first looked into this.
Have you made any progress with your ROM? If the hardware keys are still not working it's because key mapping is different on i9100, also rotation is backwards or at least it was years back when I flashed a i9100 ROM on my D710. You can remap the hardware keys so that they function correctly. Other than that there should be no differences.
Sent from my SM-S903VL using Tapatalk

Droidriven said:
Yeah, I took another look last night, the information available now clarifies things that seemed a mess back when I first looked into this.
Have you made any progress with your ROM? If the hardware keys are still not working it's because key mapping is different on i9100, also rotation is backwards or at least it was years back when I flashed a i9100 ROM on my D710. You can remap the hardware keys so that they function correctly. Other than that there should be no differences.
Sent from my SM-S903VL using Tapatalk
Click to expand...
Click to collapse
I haven't done anything yet except try to load the unmodified i9100 ROM and report what works/doesn't. Really the only thing I need fixed is the Wifi, and I have no clue how to do that.

flamadiddle said:
I haven't done anything yet except try to load the unmodified i9100 ROM and report what works/doesn't. Really the only thing I need fixed is the Wifi, and I have no clue how to do that.
Click to expand...
Click to collapse
I'll reach out to some developer associates and see what I can find out about the WiFi.
Sent from my SM-S903VL using Tapatalk

I'm not a developer, but I have a D710 lying around and I am willing to do testing if you need me

I also have an Epic 4g touch that im willing to test stuff

So... I guess nothing ever happened with this ROM? I have a SCH - R760 from US Cellular that AFAIK is compatible with d710 roms. I would still be interested in running Nougat on my device - even though my eMMC seems to have issues at the moment.

chrismin13 said:
So... I guess nothing ever happened with this ROM? I have a SCH - R760 from US Cellular that AFAIK is compatible with d710 roms. I would still be interested in running Nougat on my device - even though my eMMC seems to have issues at the moment.
Click to expand...
Click to collapse
Never had any real interest, and I don't know enough to do it myself.

flamadiddle said:
Never had any real interest, and I don't know enough to do it myself.
Click to expand...
Click to collapse
Understood. So you said that the buttons didn't work and the wifi wasn't turning on. Were there any other major bugs that you noticed? I might try and make it work for our device, because why not!
Thanks for still responding after so many months!

chrismin13 said:
Understood. So you said that the buttons didn't work and the wifi wasn't turning on. Were there any other major bugs that you noticed? I might try and make a for for our device, because why not!
Thanks for still responding after so many months!
Click to expand...
Click to collapse
Those were the only two things I noticed. Bluetooth worked. I didn't see any apps crash (but I couldn't load new ones because no wifi). I didn't try cell service because I don't even have Sprint anymore, but I suspect that probably didn't work for the same reason wifi was killed.
Thanks for looking into this! I'm still interested if we can find a way to make it work. I just don't know much about creating ROMs. I'm not an Android dev.

[GUIDE] How to correct a wrong shown build number from settings menu

Yesterday i was upgrading my phone from B368 to B369, and wronging by impatience, i decided to shut down while my phone was apparently blocked on the NAG screen (your phone has been unlocked and can't be trusted screen at startup); in truth, it wasn't blocked but it was just applying updates during reboot and he was tooking some more time than usual... The result? My model number changed from BLN-L21 to generic_a15, and so apps like camera was keeping crashing and became not usable.
After had restored a TWRP backup made before updating, and so on B368 build, i ended up with BLN-L21C432B369 as build number, but without having the latest security patch and latest improvements. In poor words, the B369 build was shown even if i was on B368 at all, and so system update wasn't detecting any other updates since that i was apparently on the latest build.
[DISCLAIMER: don't point your finger on me if you end up with your phone exploding, emitting toxic spores or radiations, please. I'm just putting this simple guide here as a way to possibly solve your issue, but i can't know if it'll works on EVERY different model, variant or kind of issue; in mine case it worked like a charm, but BE CAREFUL. I'm not responsable for anything]
What i did for fix this issue was very, very simple, much simpler than what i thought to face; i just started combing here and there in the various root folders thanks to a root explorer (i used MiX, for example) containing the various local.prop and build.prop files scattered around the system folders, until i found the right one to tweak with. The path to follow is very simple: you just need to browse to
Code:
root/version/special cust/BLN-L21/hw/eu/prop/local.prop
(note that the path will obviously change if you own a BLN-L22, a BLL-L22, ecc. but the road will be always the same - you'll find other folders name after special cust, BLL-L22 other than BLN-L21, china instead of eu for example, but often it's always straight to the last folder that finally contains the local.prop file)
and once there, with the help of a text editor, correct all the errors that you'll find mismatching with your actual build number. The voices that i had to correct are circled in orange in the picture that i attached here below, (note: the picture shows voices already fixed) and there was four of them to adjust;
Code:
ro.build.display.id=BLN-L21C432[B][COLOR="Red"]B369[/COLOR][/B]
ro.build.version.incremental=C432[B][COLOR="red"]B369[/COLOR][/B]
ro.build.description=BLN-L21 -user 7.0 HONORBLN-L21 C432[B][COLOR="red"]B369[/COLOR][/B] release-keys
ro.build.fingerprint=HONOR/BLN-L21/HWBLN-H:7.0/HONORBLN-L21/C432[B][COLOR="red"]B369[/COLOR][/B]:user/release-keys
since that in this case i was on B368 other than B369, as shown by phone info in settings menu, i just tried to modify that number with an 8 instead of a 9, gave the phone a reboot and... It's done!
**Method Update!**
 @BakedOnSomeSour pointed out a way to definitely correct the build number, permanently and safer than my method!
To do this, flash the version.img matching your firmware build, an image that you can extract from the UPDATE.APP of each update.zip package through TWRP (flash the file as image of course, by selecting the dedicated option in TWRP menu). In this way, the build number will be definitely fixed!
Thanks to BakedOnSomeSour for finding a faster and more efficient method.​
Be aware, and backup before doing this or everything you're dubious about.
Cheers

nice one buddy and a detailed one...Thanks for sharing with us. as usual, great effort.

shashank1320 said:
nice one buddy and a detailed one...Thanks for sharing with us. as usual, great effort.
Click to expand...
Click to collapse
Thanks mate. I discovered how to do by myself while trying to get rid of this error, and so i thought to share with others who could face this in future.

nice one D
just curious, can we use the same trick to revert the model number when it's changed to generic_a15

sreekantt said:
nice one D
just curious, can we use the same trick to revert the model number when it's changed to generic_a15
Click to expand...
Click to collapse
Nice question dude, i was just asking myself the same. Maybe, modifying eventual errors in the same file, or alternatively in the one in root/version/etc/component_version.txt (here there is a file with only one string with the general model; mine shows "Version-BLN-L21-432000 5.0.0.1(N.17110801)" obviously, but if it should show something relative to generic_a15, modifying it could do the trick) it could be possible to easily fix this issue. I'd like to test it by myself, but at the moment I'd like to avoid to mess up my phone again also since that I'm busy with other stuff anyway I'll finally test this sooner, and eventually I'll update the guide.

RedSkull23 said:
Nice question dude, i was just asking myself the same. Maybe, modifying eventual errors in the same file, or alternatively in the one in root/version/etc/component_version.txt (here there is a file with only one string with the general model; mine shows "Version-BLN-L21-432000 5.0.0.1(N.17110801)" obviously, but if it should show something relative to generic_a15, modifying it could do the trick) it could be possible to easily fix this issue. I'd like to test it by myself, but at the moment I'd like to avoid to mess up my phone again also since that I'm busy with other stuff anyway I'll finally test this sooner, and eventually I'll update the guide.
Click to expand...
Click to collapse
yeah same with me - don't wanna delay other things as of now... :highfive:

I would like to switch my build number so i can receive an OTA since it is currently messed up. Every time i change the build number i get an update available. But in order to install i have to remove root and TWRP. When i remove those the build goes back to original and my phone cant find an update because it says im on the lastest build. Why does it switch back when i remove twrp and root? Im assuimg it may have something to do with the boot image?

BakedOnSomeSour said:
I would like to switch my build number so i can receive an OTA since it is currently messed up. Every time i change the build number i get an update available. But in order to install i have to remove root and TWRP. When i remove those the build goes back to original and my phone cant find an update because it says im on the lastest build. Why does it switch back when i remove twrp and root? Im assuimg it may have something to do with the boot image?
Click to expand...
Click to collapse
Yes, i assume that too... Maybe when the root is removed and the original boot.img is restored, the error is restored too. You could maybe solve that by flashing the boot.img of the build just before the one you'd like to update to (but be aware and take a backup before, in case something happens. Once i flashed a boot.img of a previous build instead of the one that i had to flash, and at phone startup, my code to unlock wasn't anymore recognized, so i had to restore a backup)

RedSkull23 said:
Yes, i assume that too... Maybe when the root is removed and the original boot.img is restored, the error is restored too. You could maybe solve that by flashing the boot.img of the build just before the one you'd like to update to (but be aware and take a backup before, in case something happens. Once i flashed a boot.img of a previous build instead of the one that i had to flash, and at phone startup, my code to unlock wasn't anymore recognized, so i had to restore a backup)
Click to expand...
Click to collapse
Flashing a boot.img is having no effect on the build number. The strange thing is im on b366 but my phone wont accept that firmware with the dload method. It only accepts firmware much lower. I just need that build number to change without root but no amount of flashing does anything. Ive had a ton of android phones and they've never been as unpredictable as this one.
Edit: Flashing a version.img and vendor.img see to do it.

BakedOnSomeSour said:
Flashing a boot.img is having no effect on the build number. The strange thing is im on b366 but my phone wont accept that firmware with the dload method. It only accepts firmware much lower. I just need that build number to change without root but no amount of flashing does anything. Ive had a ton of android phones and they've never been as unpredictable as this one.
Edit: Flashing a version.img and vendor.img see to do it.
Click to expand...
Click to collapse
Reading that i was worrying, since that I'm about to update to B369 again after that Magisk V15.0 ****ed up my build.prop and other stuff too, and i thought the boot.img could fix that... But I'm glad you solved it. Both of them are needed so, or only one it's ok? By the way yeah, i can say that Huawei and their cosmos of firmware builds, different for every variant, is way too complicated. A project like Project Treble is what they need.

RedSkull23 said:
Reading that i was worrying, since that I'm about to update to B369 again after that Magisk V15.0 ****ed up my build.prop and other stuff too, and i thought the boot.img could fix that... But I'm glad you solved it. Both of them are needed so, or only one it's ok? By the way yeah, i can say that Huawei and their cosmos of firmware builds, different for every variant, is way too complicated. A project like Project Treble is what they need.
Click to expand...
Click to collapse
Well after flashing them the phone booted but I was unable to get into developer settings. It just kept crashing. It did change the build number though even after flashing to stock recovery without root. I flashed both through twrp. Maybe that was the problem. Maybe you can just try flashing version.img and let us know if it helped. I would try it without vendor.img first.

BakedOnSomeSour said:
Well after flashing them the phone booted but I was unable to get into developer settings. It just kept crashing. It did change the build number though even after flashing to stock recovery without root. I flashed both through twrp. Maybe that was the problem. Maybe you can just try flashing version.img and let us know if it helped. I would try it without vendor.img first.
Click to expand...
Click to collapse
I can extract the version.img of B368, but once i have it it's possible to flash it through fastboot/TWRP, or i have to follow another path, like typing somethin' by adb like "dd if=/sdcard/version.img of=/dev/block/mmcblck..." ?

RedSkull23 said:
I can extract the version.img of B368, but once i have it it's possible to flash it through fastboot/TWRP, or i have to follow another path, like typing somethin' by adb like "dd if=/sdcard/version.img of=/dev/block/mmcblck..." ?
Click to expand...
Click to collapse
try fastboot first. So "fastboot flash version VERSION.img". If that doesn't work flash it in TWRP.
After its flashed try removing root and flash a stock recovery and see if the build number stays.

BakedOnSomeSour said:
try fastboot first. So "fastboot flash version VERSION.img". If that doesn't work flash it in TWRP.
After its flashed try removing root and flash a stock recovery and see if the build number stays.
Click to expand...
Click to collapse
Yeah got that, thanks. I'll write here a feedback as i'll be able to do this

@BakedOnSomeSour okay i bring nice notices, here's what i did.
I tried first to flash the BLN-L21_data_hw_eu package from official firmware around 700MB by TWRP, but after some bloat apps installed that i always remove as i update, it failed with error 7 (if i don't remember bad). So i restored a backup made just before flashing it, to avoid issues of any kind.
Then i tried to flash version.img by fastboot, but it failed with error command not allowed.
Finally, i simply flashed the version.img through TWRP, then i completely removed Magisk, i flashed by fastboot the stock boot and recovery images as i do when i make an update, and... It worked. After booting to OS, my build number remained correct. It stopped from turning back to B369 after a reboot (even if I'm on B368 at all), solving the issue that i was facing. Thanks for the tip, I'll add it to the guide if you'd like to be credited

RedSkull23 said:
@BakedOnSomeSour
Then i tried to flash version.img by fastboot, but it failed with error command not allowed.
Click to expand...
Click to collapse
New mess with Huawei every day. They keep stopping us and we keep trying them

RedSkull23 said:
@BakedOnSomeSour okay i bring nice notices, here's what i did.
I tried first to flash the BLN-L21_data_hw_eu package from official firmware around 700MB by TWRP, but after some bloat apps installed that i always remove as i update, it failed with error 7 (if i don't remember bad). So i restored a backup made just before flashing it, to avoid issues of any kind.
Then i tried to flash version.img by fastboot, but it failed with error command not allowed.
Finally, i simply flashed the version.img through TWRP, then i completely removed Magisk, i flashed by fastboot the stock boot and recovery images as i do when i make an update, and... It worked. After booting to OS, my build number remained correct. It stopped from turning back to B369 after a reboot (even if I'm on B368 at all), solving the issue that i was facing. Thanks for the tip, I'll add it to the guide if you'd like to be credited
Click to expand...
Click to collapse
Im glad it all worked out :victory: Sure if you want to give me credit. Im just glad i could help

shashank1320 said:
New mess with Huawei every day. They keep stopping us and we keep trying them
Click to expand...
Click to collapse
What a bore is this, man?! :laugh: never admitting a loose against them!
BakedOnSomeSour said:
Im glad it all worked out :victory: Sure if you want to give me credit. Im just glad i could help
Click to expand...
Click to collapse
Of course, you deserve that :highfive: thanks for the idea, even faster than my workaround (and maintains properties overall)

RedSkull23 said:
What a bore is this, man?! :laugh: never admitting a loose against them!
Of course, you deserve that :highfive: thanks for the idea, even faster than my workaround (and maintains properties overall)
Click to expand...
Click to collapse
Never
Happy new year brother. Hope we continue to grow in year ahead with more mess and fixes with Huawei phones :silly:

shashank1320 said:
Never
Happy new year brother. Hope we continue to grow in year ahead with more mess and fixes with Huawei phones :silly:
Click to expand...
Click to collapse
Thanks pal, wish you the same i can say that until I'll have an Honor device, that will be almost at day order

Samsung j2 Prime (sm-g532m) - how do I get LineageOS on this device?

I'm not completely brand new to flashing with custom roms, but I sometimes go 2-3 years running stock, so when I do come back I have forgotten everything and it feels like starting over.
So far I have achieved the following:
1 - backed up device
2 - reset device back to stock
3 - flashed stock image using Heimdall
Unfortunately after all that I am not sure if I have made any progress. It just took my phone back to factory settings.. My storage is full, my SDCard is empty and I can't push a file to the sdcard because I don't know how to reference the right path.
I tried flashing a TWRP recovery.img file to the recovery partition, and it indicated success. But when I boot into recovery it looks exactly like it did before. I get no TWRP gui interface. The TWRP app has no official build for this device, so is unusable. I also tried installing Magisk but got errors and just uninstalled it.
Frankly I don't know what to do yet. I'm not sure the device is officially 'rooted' or not. I'm not sure what to do next. Do I flash an Enigma Android 6 image? Do I have to do that before I can update to Android 9?

dixonge said:
I'm not completely brand new to flashing with custom roms,.........
Click to expand...
Click to collapse
I don't have this device but, your best bet is to take a look at the following TWRP thread that's specific to your device and variants. Don't be afraid to ask for some member guidance as well.
https://forum.xda-developers.com/showthread.php?t=3616589
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Commodore VIC-20.

Ibuprophen said:
I don't have this device but, your best bet is to take a look at the following TWRP thread that's specific to your device and variants. Don't be afraid to ask for some member guidance as well.
https://forum.xda-developers.com/showthread.php?t=3616589
Good Luck!
~~~~~~~~~~~~~~~
UNLESS asked to do so, PLEASE don't PM me regarding support. Sent using The ClaRetoX Forum App on my Commodore VIC-20.
Click to expand...
Click to collapse
Yes, that's where I got my twrp recovery.img file from. I'll go back through those steps and ask in the thread if I have further issues. Thanks.

Typically there is a reboot into system after flashing twrp. Some stock ROM replace twrp with stock recovery in that case.
Known workarounds:
Flash twrp to boot partition also
Remove battery after flashing twrp
Use windows Odin and unchecked reboot
Do some key tricks to force recovery during reboot.
Once twrp booted, it normally does tricks to not get overwritten.

Asgard holds your answer
dixonge said:
I'm not completely brand new to flashing with custom roms, but I sometimes go 2-3 years running stock, so when I do come back I have forgotten everything and it feels like starting over.
So far I have achieved the following:
1 - backed up device
2 - reset device back to stock
3 - flashed stock image using Heimdall
Unfortunately after all that I am not sure if I have made any progress. It just took my phone back to factory settings.. My storage is full, my SDCard is empty and I can't push a file to the sdcard because I don't know how to reference the right path.
I tried flashing a TWRP recovery.img file to the recovery partition, and it indicated success. But when I boot into recovery it looks exactly like it did before. I get no TWRP gui interface. The TWRP app has no official build for this device, so is unusable. I also tried installing Magisk but got errors and just uninstalled it.
Frankly I don't know what to do yet. I'm not sure the device is officially 'rooted' or not. I'm not sure what to do next. Do I flash an Enigma Android 6 image? Do I have to do that before I can update to Android 9?
Click to expand...
Click to collapse
OK, bad jokes about Nordic deities aside. Try using ODIN rather than Heimdall to flash TWRP. In ODIN, make sure the automatic reboot on exit feature is turned OFF. After exiting ODIN, MANUALLY reboot the thing into recovery mode using whatever multiple button combination is required, and you "should" find it starting up TWRP for you. ASSUMING that is so, then power off the device and re-start it. it "should" now be working correctly, meaning with whatever ROM you have in place and TWRP as the recovery. And if THAT worked, you can flash SU using TWRP if you are not already rooted and you are good to go. Good Luck.

I now have managed to finally get TWRP flashed. It worked this time. Could not begin to tell you what I did differently...
I managed to flash the custom ROM and am now dealing with two remaining issues - a password I am being asked for that I never set, and getting the right version of opengapps flashed.

nezlek said:
OK, bad jokes about Nordic deities aside. Try using ODIN rather than Heimdall to flash TWRP. In ODIN, make sure the automatic reboot on exit feature is turned OFF. After exiting ODIN, MANUALLY reboot the thing into recovery mode using whatever multiple button combination is required, and you "should" find it starting up TWRP for you. ASSUMING that is so, then power off the device and re-start it. it "should" now be working correctly, meaning with whatever ROM you have in place and TWRP as the recovery. And if THAT worked, you can flash SU using TWRP if you are not already rooted and you are good to go. Good Luck.
Click to expand...
Click to collapse
FYI - the only version of Odin I could find for Linux is a glitchy Java version. All the tutorials say to put things in the 'AP Slot' - and I can clearly see that in screenshots. But my version didn't have an AP slot. The graphics were misaligned and I finally gave up. I did manage to flash a ROM using ADB sideload. So there's that.

ODIN for Linux ....
dixonge said:
FYI - the only version of Odin I could find for Linux is a glitchy Java version. All the tutorials say to put things in the 'AP Slot' - and I can clearly see that in screenshots. But my version didn't have an AP slot. The graphics were misaligned and I finally gave up. I did manage to flash a ROM using ADB sideload. So there's that.
Click to expand...
Click to collapse
Yeah, Odin can be more than a little bit "glitchy" on Linux boxes. Surprised you found one that worked at all, to be totally candid. I suggest to folks that they just beg, borrow, or steal 15 minutes on a Windows box and do it the easy way. Yes, I know "windows" is a very long "four letter word" in many circles, but sometimes you just bite the bullet and take the path of least resistance. The IMPORTANT question is: is your problem solved ??

nezlek said:
Yeah, Odin can be more than a little bit "glitchy" on Linux boxes. Surprised you found one that worked at all, to be totally candid. I suggest to folks that they just beg, borrow, or steal 15 minutes on a Windows box and do it the easy way. Yes, I know "windows" is a very long "four letter word" in many circles, but sometimes you just bite the bullet and take the path of least resistance. The IMPORTANT question is: is your problem solved ??
Click to expand...
Click to collapse
Good question. Do I have LineageOS on my device? Yes.
Is it a usable version? Uh, no. My device is now reporting to be a Galaxy J7 and the WiFi is useless. This was from an Enigma ROM. So at least I have managed to figure out how to flash the device and TWRP recovery is working. Now to find a better ROM.
I guess the question I have now is this: *IS THERE* an actual, working Android 9 PIE ROM for the J2 Prime (Grand Prime+) model?

dixonge said:
Good question. Do I have LineageOS on my device? Yes.
Is it a usable version? Uh, no. My device is now reporting to be a Galaxy J7 and the WiFi is useless. This was from an Enigma ROM. So at least I have managed to figure out how to flash the device and TWRP recovery is working. Now to find a better ROM.
I guess the question I have now is this: *IS THERE* an actual, working Android 9 PIE ROM for the J2 Prime (Grand Prime+) model?
Click to expand...
Click to collapse
Hui. Quick search in XDA shows: there is probably no aosp based ROM for your device. So you flashed a ROM for a different device? You should learn a bit about model names and codenames. And be glad to not have bricked your phone.

kurtn said:
Hui. Quick search in XDA shows: there is probably no aosp based ROM for your device. So you flashed a ROM for a different device? You should learn a bit about model names and codenames. And be glad to not have bricked your phone.
Click to expand...
Click to collapse
Well, it's from here on XDA, and it was advertised as being ported for my model specifically. Just surprised to see the other model info in 'About' - I agree that Pie seems to be non-existent for this phone. What about Oreo? So far every single article I find on the 'net is just click-bait.

Sometimes it is better to stay on stock ROM. With twrp you can install magisk or xposed or nanodroid.