Related
so when i install and update it start it up and it gets to the first time start wizard and it dont fully load. vibrates and restarts. its doing it with all android builds and cabs and i uograded the rom a couple of times so i dont think thats the reason. any ideas?
dkdontforget said:
so when i install and update it start it up and it gets to the first time start wizard and it dont fully load. vibrates and restarts. its doing it with all android builds and cabs and i uograded the rom a couple of times so i dont think thats the reason. any ideas?
Click to expand...
Click to collapse
Wipe your sd card and start over is usually will fix any weird bugs. Or as stated in the release thread by 100 different people, delete your data.img file, your cache folder, any old folders associated with the old android build. Usually old conflicting files are the culprit.
i delete all the android files but didnt work. will try formatting the sd card tho
ok. so i did task 29 updated my rom. formatted my sd card. downloaded and installed the newest build. and same problem. first boots it loads the top task bar give it a few seconds. vibrates and reboots.
I also had this problem and its super annoying
But I managed to fix it.
What u wanna do is not UPDATE with the MJG start up tool
Just select which Rhodium I have for keymapping and hit run android.
Try that cuhz that fixed mine.
Make sure u do what was mentioned onj the top post to clear the SD card and format it FAT32 LONG VERSION(uncheck quick format)
Keep us updated
-Koomz
Sent from my MSM using XDA App
Koomoo said:
I also had this problem and its super annoying
But I managed to fix it.
What u wanna do is not UPDATE with the MJG start up tool
Just select which Rhodium I have for keymapping and hit run android.
Try that cuhz that fixed mine.
Make sure u do what was mentioned onj the top post to clear the SD card and format it FAT32 LONG VERSION(uncheck quick format)
Keep us updated
-Koomz
Sent from my MSM using XDA App
Click to expand...
Click to collapse
im not sure i fully understand what you are saying. if i dont update it the first time i run it. it doesent boot. is there another method of updating?
Yeah don't update using the ultility. If what u mean it won't boot? Like it hangs during the linux boot up?
Sent from my MSM using XDA App
dkdontforget said:
im not sure i fully understand what you are saying. if i dont update it the first time i run it. it doesent boot. is there another method of updating?
Click to expand...
Click to collapse
You shouldn't need to run the update at all if its a new package that you're using. The zimage/modules update breaks the build currently. (Update in the works). You can still use it to update footfall and initrd.
Sent from my SAMSUNG-SGH-I897 using XDA App
Reefermattness said:
You shouldn't need to run the update at all if its a new package that you're using. The zimage/modules update breaks the build currently. (Update in the works). You can still use it to update footfall and initrd.
Sent from my SAMSUNG-SGH-I897 using XDA App
Click to expand...
Click to collapse
Hey reef don't know if your aware or not, but i think the reason is that when they use the update app, the modules aren't being extracted properly. i think that's whats causing the system to crash after it boots.
they should be like 876kb or around that and when they use the update app, they are like 6-8Mb in size.
devilcuban said:
Hey reef don't know if your aware or not, but i think the reason is that when they use the update app, the modules aren't being extracted properly. i think that's whats causing the system to crash after it boots.
they should be like 876kb or around that and when they use the update app, they are like 6-8Mb in size.
Click to expand...
Click to collapse
There will be a new tool soon and that this wont happen, one click update type thing where i control what does and doesnt get updated by an xml file per update.
Reefermattness said:
There will be a new tool soon and that this wont happen, one click update type thing where i control what does and doesnt get updated by an xml file per update.
Click to expand...
Click to collapse
Sweet lol
Koomoo said:
Yeah don't update using the ultility. If what u mean it won't boot? Like it hangs during the linux boot up?
Sent from my MSM using XDA App
Click to expand...
Click to collapse
well since i updated my rom. and formatted my card. i reinstall the cab. if i dont do the update it just has a thing pop up asking to launch a script file. am i only supposed to update certain files? because no update at all means no boot for me
Well theres your problem
The ROM
What ROM are you using?
My phone is stock and it works
Seems to me the ROM is your problem.
Koomoo said:
Well theres your problem
The ROM
What ROM are you using?
My phone is stock and it works
Seems to me the ROM is your problem.
Click to expand...
Click to collapse
im using energy
ok so i updated my rom. installed android and DID NOT update that. and it booted just fine. and i was playin around in it for a while. then out of nowhere i couldnt make calls. and i couldnt use data. but i could recieve calls and send/recieve txts. so i resetted and try to boot into android again. NOPE. i dont know what could of happened it wont exit out of winmo it just says haret version pre..... launch a script file. any ideas?
Just to reiterate, THIS DOES NOT WORK YET. This thread was created for interested devs who may want the appropriate files to get this going. As far as I know, this doesn't work on anything but the Korean Galaxy.
Ok, so recently the Korean variant of the Galaxy S got a Gingerbread update. (the SHW-M110S)
This phone HAS call recording, and is the best chance of getting call recording to work on Gingerbread.
However, just copying the appropriate files isn't enough. libaudiopolicy.so (the only file needed for recording, as the other 2 broke Fring in the Froyo version) puts the phone into a hard bootloop (doesn't get to boot animation). Phone.apk will force close.
That said, I'm on Darky's 10RC6, which I have previously got into a hard bootloop through a new framework-res.apk suitable for JVB (which it's based on). I encourage you to backup your files and copy these files yourself - if you're lucky, it might work!
I found it a chore to download the entire update tar, mount factoryfs.rfs and extract and deodex the apk and .so files myself, so I'm putting them here to hopefully attract interest in getting this to work.
Attached files are:
/system/app/Phone.apk
/system/app/Phone_util.apk
/system/lib/libaudiopolicy.so
/system/lib/libaudioflinger.so
/system/lib/libaudio.so
/system/framework/twframework-res.apk (required to decompile Phone.apk!!)
/system/framework/framework-res.apk (Also required to decompile Phone.apk!)
Phone.apk is deodexed (framework apks have no need to be), and because I have the ROM downloaded and mountable, I can attach any other files from the ROM that devs may need.
Phone_util.apk is completely unchanged from JVB, so I doubt it is needed for a successful port.
Good luck to all on getting this to work!
For those interested, the tar is:
SHW-M110S_Gingerbread_REV03_ALL_VD27-0629_CL164221_mid_user.tar
Google it if you want to dl yourself a copy.
P.S. Mods - I posted this in dev and not general because I extracted and deodexed the files myself, and there may be more dev exposure here - hoping this is alright. Move if appropriate.
Hope the devs here get this working
Oh, and if it works on CM7, that would be SO hot.
Thanks dude, Can you upload these files also ?
systemp\app\phone_util.apk
systemp\lib\libaudio.so
systemp\lib\libaudioflinger.so
Edit: SHW-M110S_Gingerbread_REV03_ALL_VD27-0629_CL164221_mid_user.tar was already on torrent, I had downloaded it. But I didn't know whether it has call recording or not. Are you sure about that?
sinancetinkaya said:
Thanks dude, Can you upload these files also ?
systemp\app\phone_util.apk
systemp\lib\libaudio.so
systemp\lib\libaudioflinger.so
Click to expand...
Click to collapse
Updated the original post with the files.
And I'm sure it has call recording. The Phone.apk has all the required xmls and images for recording, looking quite similar to the Froyo call recording Phone.apk.
i will test it i ve been waiting for this for a long time
I have package M110S-Gingerbread-HOME-IMAGE-REV03-VE03-0050-USER.tar.md5.
I don't know if it is right version, but it doesn't seem to help.
So far I tried just copying libaudiopolicy.so and Phone.apk, but it didn't work - actually after copying Phone.apk, it started to crash.
Files from this thread didn't work either (same crashing).
K4P1 said:
I have package M110S-Gingerbread-HOME-IMAGE-REV03-VE03-0050-USER.tar.md5.
I don't know if it is right version, but it doesn't seem to help.
So far I tried just copying libaudiopolicy.so and Phone.apk, but it didn't work - actually after copying Phone.apk, it started to crash.
Files from this thread didn't work either (same crashing).
Click to expand...
Click to collapse
Yeah, doesn't seem like it works on any non Korean Gingerbread roms at the moment then. Pity it's not just a darky thing.
montymintypie said:
Yeah, doesn't seem like it works on any non Korean Gingerbread roms at the moment then. Pity it's not just a darky thing.
Click to expand...
Click to collapse
Yep, they should do call recording available to all areas.
Here is some info about this ROM
http://www.phoneinside.co.kr/bbs/board.php?bo_table=about04&wr_id=814
K4P1 said:
I have package M110S-Gingerbread-HOME-IMAGE-REV03-VE03-0050-USER.tar.md5.
I don't know if it is right version, but it doesn't seem to help.
So far I tried just copying libaudiopolicy.so and Phone.apk, but it didn't work - actually after copying Phone.apk, it started to crash.
Files from this thread didn't work either (same crashing).
Click to expand...
Click to collapse
Edit: didn't work
sinancetinkaya said:
Can you try these files via cwm ?
Click to expand...
Click to collapse
Flashing first... Waiting if it boots.
Neither doesn't work. Phone doesn't even get to boot animation stage.
Ok, not working.
I can try other if needed (I just reflash rom again - it takes just a few minutes).
sinancetinkaya said:
Can you try these files via cwm ?
Click to expand...
Click to collapse
For me (Darky's 10RC6 which is based on JVB) both update files give me a hard bootloop (doesn't get past Galaxy S screen).
I noticed you changed the libaudio.so between the 2, what did you do to it?
K4P1 said:
Flashing first... Waiting if it boots.
Neither doesn't work. Phone doesn't even get to boot animation stage.
Ok, not working.
I can try other if needed (I just reflash rom again - it takes just a few minutes).
Click to expand...
Click to collapse
edit: didn't work
montymintypie said:
For me (Darky's 10RC6 which is based on JVB) both update files give me a hard bootloop (doesn't get past Galaxy S screen).
I noticed you changed the libaudio.so between the 2, what did you do to it?
Click to expand...
Click to collapse
It's the original file of froyo. The ginger one you provided is too small. I thought that can't be that much small.
sinancetinkaya said:
Last test, try these please
Click to expand...
Click to collapse
Nope, still boot loops before it gets to the boot animation. The file that's killing it is libaudiopolicy.so, replace nothing but that and it'll bootloop.
How do you decompile a .so file? A google search returns limited information on the topic.
I tried to flash with CWM2 (flashed speedmod k13E), I have changed the files in the update zip of http://forum.xda-developers.com/showthread.php?t=967297 and I used the restore update too... easier way to check it.
The results are that: The phone is even not booting, it's stuck on the I9000 screen and not going to the ROM boot...
I flashed back to original files... wait for good update zip.
orenzah said:
I tried to flash with CWM2 (flashed speedmod k13E), I have changed the files in the update zip of http://forum.xda-developers.com/showthread.php?t=967297 and I used the restore update too... easier way to check it.
The results are that: The phone is even not booting, it's stuck on the I9000 screen and not going to the ROM boot...
I flashed back to original files... wait for good update zip.
Click to expand...
Click to collapse
Same here,I tried with files in this thread and files from "M110S-Gingerbread-HOME-IMAGE-REV03-VE03-0050-USER" rom.
I'm going to flash just the 'lib' '.so' files and check the response of the device, if the device will response right... I'll go further and I'll change the apk's files of the phone, I'll merge the apk's of the i9000 GB with korean GB.
I hope it will be easy as it sound.
orenzah said:
I'm going to flash just the 'lib' '.so' files and check the response of the device, if the device will response right... I'll go further and I'll change the apk's files of the phone, I'll merge the apk's of the i9000 GB with korean GB.
I hope it will be easy as it sound.
Click to expand...
Click to collapse
waiting for a result
zenosteam said:
waiting for a result
Click to expand...
Click to collapse
ok, I flashed.
sadly the phone won't boot, I restored with the backup files, and than it's booted.
The 'lib' '.so' files having problems. I don't know which one of them.
That's means we need here a good developers for working on this.
I can't help anymore of that (I think), I'm just electronic guy not programmer.
orenzah said:
ok, I flashed.
sadly the phone won't boot, I restored with the backup files, and than it's booted.
The 'lib' '.so' files having problems. I don't know which one of them.
That's means we need here a good developers for working on this.
I can't help anymore of that (I think), I'm just electronic guy not programmer.
Click to expand...
Click to collapse
At least it is in libaudiopolicy.so, because try flashing it only and phone won't boot.
[Q] S3 device status detected as "modified" after JB update yesterday night.
First let me say that my Galaxy SIII was not rooted before the update. It's been running full stock rom.
I've done the Jelly Bean update yesterday night through Kies while my phone was connected to my computer.
Update was perfect until I tried the software update app to check if there was anything left to install.
At this moment, I had a message telling me that my phone was modified and updates will not work (I don't remember the exact message).
If I go to Settings, About device, Status... Device Status is "modified".
Again, I don't have anything on my phone to root my device.
So what I tried next... removing my microsd card (64GB Sandisk microSDXC) and reboot my phone. Now, Device status is "Normal".
Put it back again... reboot... and Device status is again "modified".
Format the card... reboot... Device status is Normal.
Put everything back (55GB of music only synched through iSyncr wifi with my Mac)... reboot... Device Status "modified".
So it really looks like that the thing that Samsung uses to detect the "modified" state of the phone is broken in some way because it's detecting my media files (mp3 and m4a) as some sort of modification to the phone... this is completely wrong!!
Am I the only one with this problem?
I will try this week to reduce the amount of music file to see if there is anything that broke the detection system... I will report later if I find anything.
By the way, I found a similar thread with a similar problem... but this thread did not offer any solution and it looks like to be close as I cannot add anything to it.
That's very weird because I was rooted using the method in my sig and my device status showed modified as well. I was able to install the update just fine.
Tony_YYZ said:
That's very weird because I was rooted using the method in my sig and my device status showed modified as well. I was able to install the update just fine.
Click to expand...
Click to collapse
I was also able to install the update... the status was "normal" before the update...
the issue I have now is it says "modified" even if I did not modify anything in my phone.
I did the test again this morning... I removed all the music file on my card... device status is back to normal.
It must be one of my music file that triggers this detection... if it's in fact the case, it means that there is a bug in the detection that Samung have implemented.
zadigre said:
I was also able to install the update... the status was "normal" before the update...
the issue I have now is it says "modified" even if I did not modify anything in my phone.
I did the test again this morning... I removed all the music file on my card... device status is back to normal.
It must be one of my music file that triggers this detection... if it's in fact the case, it means that there is a bug in the detection that Samung have implemented.
Click to expand...
Click to collapse
Yeah, that is very odd. I'd organize all your files on our SD Card into folders and move them to your PC. Then copy one folder at a time over to the SD card and see which one triggers the phone to show a Modified status. Then you can narrow it down from there.
Tony_YYZ said:
Yeah, that is very odd. I'd organize all your files on our SD Card into folders and move them to your PC. Then copy one folder at a time over to the SD card and see which one triggers the phone to show a Modified status. Then you can narrow it down from there.
Click to expand...
Click to collapse
this is exactly what I'm going to do... I will also try to logcat command through adb ... I might be able to find something in the log.
I will let everyone know as soon as I find the cause of this problem.
Yea mine was modified going into the ota update it updated fine then after when you checked software update it said it was modified and that updates were no longer available
Sent from my SGH-I747M using xda premium
thatsupnow said:
Yea mine was modified going into the ota update it updated fine then after when you checked software update it said it was modified and that updates were no longer available
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
This is so weird, after my OTA completed yesterday I tried to check for updates again and it just told me I was on the latest version. Now when I check it gives me the modified error.
Blargh. Ahh well, It's not like we're going to be seeing another update anytime soon, unless it's a patch.
Tony_YYZ said:
This is so weird, after my OTA completed yesterday I tried to check for updates again and it just told me I was on the latest version. Now when I check it gives me the modified error.
Blargh. Ahh well, It's not like we're going to be seeing another update anytime soon, unless it's a patch.
Click to expand...
Click to collapse
are you rooted after updating?
maybe you can do like what I've did (remove microsd card), reboot and see if you still have this "modified" status/message.
zadigre said:
are you rooted after updating?
maybe you can do like what I've did (remove microsd card), reboot and see if you still have this "modified" status/message.
Click to expand...
Click to collapse
I did restore root after updating. I'll have to temporarily remove root, restart and see what it says then. I'll try to do that later.
Tony_YYZ said:
I did restore root after updating. I'll have to temporarily remove root, restart and see what it says then. I'll try to do that later.
Click to expand...
Click to collapse
I suspect that they are checking not just the presence of "rooting" app in the system folder, but also other "rooting" files anywhere else on the phone... I'm sure they do this because just by removing my microsd card, even if the only files present were music and jpg file, the status went from modified to normal.
So a temp unroot might not necessarily fix this problem for you.
zadigre said:
I suspect that they are checking not just the presence of "rooting" app in the system folder, but also other "rooting" files anywhere else on the phone... I'm sure they do this because just by removing my microsd card, even if the only files present were music and jpg file, the status went from modified to normal.
So a temp unroot might not necessarily fix this problem for you.
Click to expand...
Click to collapse
Hmm, hopefully the answer surfaces from one of the devs soon.
I have ROOT but my Device Status is Normal
Sent from my SGH-I747M
yulet said:
I have ROOT but my Device Status is Normal
Sent from my SGH-I747M
Click to expand...
Click to collapse
which su binary are using (supersuser or supersu)?
I think that supersu has an option to hide the root availability... is this the one that you are using?
thatsupnow said:
Yea mine was modified going into the ota update it updated fine then after when you checked software update it said it was modified and that updates were no longer available
Sent from my SGH-I747M using xda premium
Click to expand...
Click to collapse
Sam here, as far as I can tell it wasn't as a result of the SD card. It was fine when I had stock unrooted Rogers ALH1, but it changed to modified when I flashed the root injected Rogers ALH1 for the no counter trip thread, and it was in ODIN too.
zadigre said:
which su binary are using (supersuser or supersu)?
I think that supersu has an option to hide the root availability... is this the one that you are using?
Click to expand...
Click to collapse
I'm also rooted on the JB update and status shows normal. I'm using supersu but can't find an option to hide. With rooted ics it always showed modified.
I wasn't sure if it was connected to the flash counter in some way since I'm not at 0 anymore but apparently that's not the case.
Sent from my SGH-I747M using xda app-developers app
acloaf said:
I'm also rooted on the JB update and status shows normal. I'm using supersu but can't find an option to hide. With rooted ics it always showed modified.
I wasn't sure if it was connected to the flash counter in some way since I'm not at 0 anymore but apparently that's not the case.
Sent from my SGH-I747M using xda app-developers app
Click to expand...
Click to collapse
It's all based upon files in /system ALSO flash counter.
Modified, meh.
Just if you DO NOT root and updated to JB 4.1 and it now shows modified...that's weird.
Yet most of the time when you flash to a rooted version and it says modified thats cause of /system files and flash counter.
caha2639 said:
It's all based upon files in /system ALSO flash counter.
Modified, meh.
Just if you DO NOT root and updated to JB 4.1 and it now shows modified...that's weird.
Yet most of the time when you flash to a rooted version and it says modified thats cause of /system files and flash counter.
Click to expand...
Click to collapse
My phone has a stock rom and flash counter is 0.
This morning, I had all my music files on my microsd card... Status was modified. I removed all files, reboot... Status normal. Yes this is weird.
Please read forum rules before posting
Questions go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
I have the same weird problem too. I bought my phone 4-5 days ago from a famous shop. It was totally new and unused, never rooted, never flashed anything, no simlock, no root required app installed AND no sdcard. These days it is mostly Modified, rarely it turns to Normal after restarting the device...
I don't know what was really going on... I removed one song, got the "Normal" status. I removed some other files, got "modified". ReAdd the first file that was removed, got the "Normal" status again.
What I've decided to do is put my memory card in my MacBook Pro. I got an error that the card wasn't readable. My MacBook is supposed to support SDXC standard with and extFAT formated card... so it looks like that my card had a problem. I decided to reformat the card with FAT32 even if SDXC card are supposed to be extFAT. I put the card back into my phone. I synched all music files.... and I got the "normal" status again. I modified my playing list in iTunes... I synched again... status stil shown as "normal".
So I don't know what was the problem exactly... I suppose that the file system on the card was damaged in some way... but I really do not know what caused this problem at first.
Anyway it works fine now... so this is the most important thing.
I have no Idea what i did to brick the phone but it wont get past the huawei splash screen. i am a complete noob at this so please dont explain everything clearly. i do not have any custom recovery installed (i have stock Android system recovery <3e>)
EDIT:
i have also downloaded the emotionUI UPDATE.APP and put it on the sd card but when i boot up this happens;
(i havent posted enough to allow me to send links and the attachment button is broken so just remove the spaces in the link and it will work
http s: //vimeo.com/121563634
i downloaded the firmware from some chinese place but im too lazy to check where but if it rly matters i can
mbdawg said:
I have no Idea what i did to brick the phone but it wont get past the huawei splash screen. i am a complete noob at this so please dont explain everything clearly. i do not have any custom recovery installed (i have stock Android system recovery <3e>)
EDIT:
i have also downloaded the emotionUI UPDATE.APP and put it on the sd card but when i boot up this happens;
(i havent posted enough to allow me to send links and the attachment button is broken so just remove the spaces in the link and it will work
http s: //vimeo.com/121563634
i downloaded the firmware from some chinese place but im too lazy to check where but if it rly matters i can
Click to expand...
Click to collapse
To me it looks like you made a bad update and now you need to reflash. Now if you know which firmware was the last working one on thw phone i can make a suggestion on what to put in the sd card to flash.
Sent from my SM-G850F
tileeq said:
To me it looks like you made a bad update and now you need to reflash. Now if you know which firmware was the last working one on thw phone i can make a suggestion on what to put in the sd card to flash.
Sent from my SM-G850F
Click to expand...
Click to collapse
sry for the late reply. i have fixed it (i just downloaded the firmware from huawei's website and it worked flawlessly DERP) thanks anyway
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