Hey folks,
NOTE: SOLVED, update below
On my VTR-L09 Single Sim, I flashed TWRP to edit /vendor/etc/hosts and then flashed recovery again. I went a wrong path there and had to flash the original recovery in order to do a factory reset & wipe. My /data-Partition was broken during the process, too, because I was accidentally wiped it
After the fresh wipe, I started the phone again and after it loaded, configured it (without restoring from my backup) and after a couple of seconds my camera app disappeared from the home screen. Dafuq? Since then, I tried to recover it a couple of times.
I am now hoping that the B126-Update brings my camera app back when it arrives via OTA, but until then:
Does anyone have an Idea where my camera app went, and how I can get it back?
Obviously, I checked under the disabled apps.
Thanks for sharing your thoughts
I am on VTR-L09C432B123
UPDATE: I worked out a way of re-flashing an official update without funkyhuawei, check out https://forum.xda-developers.com/p10/development/dev-introducing-redlotus-source-huawei-t3601493
Did you try to install another camera app to see if the camera turn on? it's possible that the data folder of camera to be erased.
Lukx said:
Hey folks,
On my VTR-L09 Single Sim, I flashed TWRP to edit /vendor/etc/hosts and then flashed recovery again. I went a wrong path there and had to flash the original recovery in order to do a factory reset & wipe. My /data-Partition was broken during the process, too, because I was accidentally wiped it
After the fresh wipe, I started the phone again and after it loaded, configured it (without restoring from my backup) and after a couple of seconds my camera app disappeared from the home screen. Dafuq? Since then, I tried to recover it a couple of times.
I am now hoping that the B126-Update brings my camera app back when it arrives via OTA, but until then:
Does anyone have an Idea where my camera app went, and how I can get it back?
Obviously, I checked under the disabled apps.
Thanks for sharing your thoughts
I am on VTR-L09C432B123
Click to expand...
Click to collapse
Have you tried the HiSuite system restore option. I never used it. But if it works like the restore option from Samsung and Sony. You should restart your phone in recovery mode and the original firmware will be flashed?
Hey
thanks for your answers.
The hisuite does not support my model yet (argh).
OpenCamera works fine, whatsapp's camera feature as well....
The Gallery App is still there, by the way.
I'm having the same issue too after an unsuccessful root which required me to factory reset my P10. After factory rest the stock camera app is missing..
Could someone upload their stock camera backup file? It would be much appreciated.
I attached the HwCamera2 folder with apk, lib and oat folder from /system/priv-app.
I'm on VTR-L29C432B123.
Jannomag said:
I attached the HwCamera2 folder with apk, lib and oat folder from /system/priv-app.
I'm on VTR-L29C432B123.
Click to expand...
Click to collapse
Thanks for the file. May I know how do I get it installed?
I navigated through the same directory and found the same files as yours. I tried installing the apk file from both my own and yours but it says it is corrupted.
Thanks, @Jannomag. I have found that most other Huawei-Apps in that priv-app folder are also missing (except I am not entirely sad about many of those). I'll keep digging a bit.
*Update* I just found in my /etc/whitelistedapps.xml points to /vendor/etc/whitelistedapps.xml, which in turn does not exist.
could somebody with a working Camera app please check whether that file /vendor/etc/whitelistedapps.xml exists, and what is written in there?
This is just a straw I am holding on to, not a real trace or hint, though.
Lukx said:
Thanks, @Jannomag. I have found that most other Huawei-Apps in that priv-app folder are also missing (except I am not entirely sad about many of those). I'll keep digging a bit.
*Update* I just found in my /etc/whitelistedapps.xml points to /vendor/etc/whitelistedapps.xml, which in turn does not exist.
could somebody with a working Camera app please check whether that file /vendor/etc/whitelistedapps.xml exists, and what is written in there?
This is just a straw I am holding on to, not a real trace or hint, though.
Click to expand...
Click to collapse
Hy Lukx, i have exactly the same problem. Wanted to root my phone, but I couldnt see the zip file in twrp, so i wiped whole data and did formatting the whole phone. after reboot my camera app was gone, also the themes were disappeared. I tried installing the firmware for my huawei (from a russian site but I dont know if its the right firmware) but it stopped at 5%.
My Phones Build Number is: VTR-L09C432B113
Thanks
stilla98
Funny thing... I am suspecting that some version mismatch of the recovery or boot partition during the Wipe might be the cause, although I do not have any proof of that.
I am currently trying to write a free alternative to funkyhuawei, so we can flash the full firmware easily again. I think i won't be done with that before mid next week, though...
I am using the OpenCamera app in the meantime.
Lukx said:
Funny thing... I am suspecting that some version mismatch of the recovery or boot partition during the Wipe might be the cause, although I do not have any proof of that.
I am currently trying to write a free alternative to funkyhuawei, so we can flash the full firmware easily again. I think i won't be done with that before mid next week, though...
I am using the OpenCamera app in the meantime.
Click to expand...
Click to collapse
So you are telling me, that the funkyhuawei method works? I saw that my Version is supported. Should I try it?
Thanks
stilla98 said:
So you are telling me, that the funkyhuawei method works? I saw that my Version is supported. Should I try it?
Thanks
Click to expand...
Click to collapse
I didn't say that
But as FH reflashes your phone fully, it should do a full recovery. If you feel like investing money into that, why not try? Otherwise, I recommend you wait along with me for another week and see how far I get with my approach, which I promise to release for free...
Lukx said:
I didn't say that
But as FH reflashes your phone fully, it should do a full recovery. If you feel like investing money into that, why not try? Otherwise, I recommend you wait along with me for another week and see how far I get with my approach, which I promise to release for free...
Click to expand...
Click to collapse
Okay , i will wait for it. I will also install the opencamera app.. by the way, do you also have problems with the design? im having only one design and i cannot add more..
stilla98 said:
im having only one design and i cannot add more..
Click to expand...
Click to collapse
I never really use the theme feature, as I have found "my" favorite theme initially and it's now in the Huawei Backup I carry around through reflashes (highly recommended, it stores on SD card). But the "Designs" app seems to show me a couple of designs, yes. I don't want to try downloading them right now, though.
Lukx said:
I never really use the theme feature, as I have found "my" favorite theme initially and it's now in the Huawei Backup I carry around through reflashes (highly recommended, it stores on SD card). But the "Designs" app seems to show me a couple of designs, yes. I don't want to try downloading them right now, though.
Click to expand...
Click to collapse
okay, i hadnt a microsd card since yesterday, i also backed up my phone before wiping and formatting but there are still no themes, i will try installing them on sd card.. thank you for your help
just install via fastboot boot.img recovery.img cust.img system.img
i have same problem but i can fix it
Same problem
Lukx said:
Hey folks,
NOTE: SOLVED, update below
On my VTR-L09 Single Sim, I flashed TWRP to edit /vendor/etc/hosts and then flashed recovery again. I went a wrong path there and had to flash the original recovery in order to do a factory reset & wipe. My /data-Partition was broken during the process, too, because I was accidentally wiped it
After the fresh wipe, I started the phone again and after it loaded, configured it (without restoring from my backup) and after a couple of seconds my camera app disappeared from the home screen. Dafuq? Since then, I tried to recover it a couple of times.
I am now hoping that the B126-Update brings my camera app back when it arrives via OTA, but until then:
Does anyone have an Idea where my camera app went, and how I can get it back?
Obviously, I checked under the disabled apps.
Thanks for sharing your thoughts
I am on VTR-L09C432B123
UPDATE: I worked out a way of re-flashing an official update without funkyhuawei, check out https://forum.xda-developers.com/p10/development/dev-introducing-redlotus-source-huawei-t3601493
Click to expand...
Click to collapse
I have the same problem with my Huawei p10, don't have the camera apk but I can use with the open camera. did you fix the problem? Thank you
been there done that
Guy all you need is follow step on this link to restock rom and start unlock bootloader again
You can try to restore factory settings.
Related
So I received a notification to download the 5.1 update this morning on my rooted Nexus 6. I proceeded to click download and then install.
However, due to that I had TeamWin recovery installed the update failed on reboot. (didn't even try to install)
Now when I click on "Check for updates" in About in System Settings menu. It says that there are no new updates??? Even though it failed to install.
Does anyone know where the update is stored on the device before installation? Maybe i need to remove it before it will try and update again? (now that i have flashed stock recovery)
Any help would be very appreciated.
You need to unroot too.
Ota can be downloaded online.
d1wepn said:
So I received a notification to download the 5.1 update this morning on my rooted Nexus 6. I proceeded to click download and then install.
However, due to that I had TeamWin recovery installed the update failed on reboot. (didn't even try to install)
Now when I click on "Check for updates" in About in System Settings menu. It says that there are no new updates??? Even though it failed to install.
Does anyone know where the update is stored on the device before installation? Maybe i need to remove it before it will try and update again? (now that i have flashed stock recovery)
Any help would be very appreciated.
Click to expand...
Click to collapse
Once you remove root, try pulling your Sim and rebooting. Let the phone sit, without Sim, and see if update reappears.
rootSU said:
You need to unroot too.
Ota can be downloaded online.
Click to expand...
Click to collapse
I was hoping to use the factory OTA update method for a change. (Always manually update) But might just be easier.
Downloading OTA now. Thanks for the advice rootSU
Evolution_Freak said:
Once you remove root, try pulling your Sim and rebooting. Let the phone sit, without Sim, and see if update reappears.
Click to expand...
Click to collapse
Might give this a try first. Worth a shot. Cheers mate.
OTA update downloads to system/cache folder ... It may get deleted soon after you try installing and restart the phone. You need rooted phone and a file explorer like es file explorer for accessing system folder.
Sent from android one lollypop 5.1
---------- Post added at 12:47 AM ---------- Previous post was at 12:38 AM ----------
Check first whether you have it in your phone already. Rooted phone go to /cache folder you'll find something.Zip there.
Ok so i managed to get the phone to download the OTA again and attempted to install it again. This time with stock recovery.
Everything was looking good but it fails with "error" below the android logo.
Any ideas?
Sorry I can't help you. I don't want that AT&T 5.1 update. So I did what you did and hit install. It of course didn't. I use TWRP also. But the damn 5.1 update is back!
Tappin from my Nexus 6
Any reason you want the OTA? you can install the factory image from here and get the same result without mucking around...
https://developers.google.com/android/nexus/images
Gage_Hero said:
Any reason you want the OTA? you can install the factory image from here and get the same result without mucking around...
https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
You only need to flash the system.img file within the Google image using fastboot.
After that, boot into TWRP and reflash SuperSU, XPosed, and anything else you've flashed that resides in /system.
Wipe caches and reboot. Easy, and no app or data loss.
Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
um.. you are quite a bit late. this is an old thread, look at the dates. you responded to a question thats 6 month old.
liquidzoo said:
You only need to flash the system.img file within the Google image using fastboot.
After that, boot into TWRP and reflash SuperSU, XPosed, and anything else you've flashed that resides in /system.
Wipe caches and reboot. Easy, and no app or data loss.
Click to expand...
Click to collapse
Except, to be more complete, it might be a good idea to flash everything except data and boot - that is, in case changes are made to radio or anything else, but if changes are done to boot and are required for system or kernel and you don't put stock boot, you're kinda screwed (you'd need a different version of twrp in this case and it probably won't be out).
My point, there really is no complete way to know if flashing just system is enough to get all the security updates unless you look at what the update replaces. That's why I'm looking for the ota.zip
Rocky1988 said:
Except, to be more complete, it might be a good idea to flash everything except data and boot - that is, in case changes are made to radio or anything else, but if changes are done to boot and are required for system or kernel and you don't put stock boot, you're kinda screwed (you'd need a different version of twrp in this case and it probably won't be out).
My point, there really is no complete way to know if flashing just system is enough to get all the security updates unless you look at what the update replaces. That's why I'm looking for the ota.zip
Click to expand...
Click to collapse
And thankfully Google put version numbers to the other files so takes about 15 seconds to realise you only need to flash system. If a change was made to radio you can still flash in exactly the same way as the system and not lose data...
Amos91 said:
And thankfully Google put version numbers to the other files so takes about 15 seconds to realise you only need to flash system. If a change was made to radio you can still flash in exactly the same way as the system and not lose data...
Click to expand...
Click to collapse
How do you check version numbers for the other files? This may be what I'm after!
Rocky1988 said:
Using a stock image will wipe the device each time. The posters question is even more valid now since Google's doing security patches every month.
I have the same issue & I wasn't able to find the .zip in /cache
Click to expand...
Click to collapse
I'm unable to find the latest update in the /system folder (/system/cache doesn't exist on my device) or the /cache folder either.
/data/data/com.google.android.gms/app_download/update.zip
d1wepn said:
Ok so i managed to get the phone to download the OTA again and attempted to install it again. This time with stock recovery.
Everything was looking good but it fails with "error" below the android logo.
Any ideas?
Click to expand...
Click to collapse
Use Flashify to install OTA updates instead.
At last i found it
I have clock work recovery installed on my phone. It refuses to update my OTA factory software update, i searched for it and installed it manually. It was in /data/data/com.tinno.systemupdate/files/googleota/0/update.zip
Hi all,
I have a P7-L10 rooted with Lollipop 5.1.1 and EMUI 3.1.
I cut the magazine folder to my external sd card. After that when I unlock the device it doesn't display anymore these images. I put it back and still the same.
I found this, but the folder bounce in where the images exist seem to be ok. I removed the themes folder from system and placed it back again, but the theme application sees it in first and after I open it again it doesn't.
How can I have the magazine setting back?
ps I guess we can keep this thread for some custom magazines for future use.
koutzi said:
Hi all,
I have a P7-L10 rooted with Lollipop 5.1.1 and EMUI 3.1.
I cut the magazine folder to my external sd card. After that when I unlock the device it doesn't display anymore these images. I put it back and still the same.
I found this, but the folder bounce in where the images exist seem to be ok. I removed the themes folder from system and placed it back again, but the theme application sees it in first and after I open it again it doesn't.
How can I have the magazine setting back?
ps I guess we can keep this thread for some custom magazines for future use.
Click to expand...
Click to collapse
it happened to me too, try to use an other theme, and revert back to default magazine theme
First thing i did. It didnt work.
koutzi said:
First thing i did. It didnt work.
Click to expand...
Click to collapse
sorry then, it worked for me, be sure your cust version is still there
Thank you for your interest though.
I had the idea to flash the rom (local update) again, but i dont know whether it will erase the files existing already there or not. I'm not the user of this device and i dont want to risk on that.
no local update will not erase or replace your data, only a force update will solve this problem, but you will lose your data
Sir,
I have created a problem on my Huwaei EUI3 mobile phone and that is when ever I used to switch it on or awake it there was different picture on the screen. I have no idea whatI have done and I have several ways by going into the display geading of the phone and it it is still not responding can you help me.
Regards
Akbar Amanat
Hi everyone !
I rooted my Honor 5C a while ago and everything went smoothly. After installing Xposed, some modules and some nice root apps, I decided to take a step forward.
Lately, I heard of MicroG to replace Google Apps and Services. Since I'm actually and for quite some time trying to degooglise myself more and more, it catched my interest. Thus, according to several tutorials, I used Root App Deleter to uninstall GApps, in order to replace them with the MicroG framework. Then I reboot and... well my device was unable to pass the Honor screen. So I went to TWRP recovery menu and tried a factory reset, which changed nothing, so I went deeper in the wipe settings and wiped... pretty much everything yeah. This was quite a stupid thing to do, now I don't even have an OS installed on my phone...
And of course, I've been stupid enough to never did a nandroid backup. Feel free to yell or mock me, I know I really should have...
Anyway, at this point, it seems that the only available option to me would be to flash a stock rom to my device, but I can't find one for the EU version NEM-L51. Actually, I can't find any stock rom for Honor 5C on Huawei site, nor on the web. I did quite some research today and I swear I couldn't find anything, anywhere. And here I am.
Please guys, can someone help me ? I know I'm at fault for not taking my precautions before doing some risky stuff, and I guess it was going to happen to me one of these days, but I hope there is something I can do.
Thanks in advance for reading and eventually trying to help me if you can.
See ya !
google huawei firmware finder to get stock rom
jkccl9 said:
google huawei firmware finder to get stock rom
Click to expand...
Click to collapse
Thanks for answering. I installed that software on Windows, but by searching for "NEM-L51", I got a list of several models : NEM-L51C10B141, NEM-L51C432B130, NEM-L51C432B120, NEM-L51C10B121, NEM-L51C432B104 and NEM-L51C432B103. I have no idea which one I should try to download. Can you help me figuring that out ?
Again, thank you for your help.
Zarou said:
Thanks for answering. I installed that software on Windows, but by searching for "NEM-L51", I got a list of several models : NEM-L51C10B141, NEM-L51C432B130, NEM-L51C432B120, NEM-L51C10B121, NEM-L51C432B104 and NEM-L51C432B103. I have no idea which one I should try to download. Can you help me figuring that out ?
Again, thank you for your help.
Click to expand...
Click to collapse
do you remember which version was installed on the phone? that is what the different Bxxx stands for
jkccl9 said:
do you remember which version was installed on the phone? that is what the different Bxxx stands for
Click to expand...
Click to collapse
As I thought, but unfortunately, no, I don't. What should I do then ? Try them all ?
Zarou said:
As I thought, but unfortunately, no, I don't. What should I do then ? Try them all ?
Click to expand...
Click to collapse
i guess thats the only thing you can do unless someone else uploads a twrp backup that you can flash.
to start download honor multitool and huawei update extractor. use the unbrick option use lowest Bxxx number first until the phone boots. may have to wait a few minutes
or idk if you can use the 3 button flash method, considering you dont know which version you have installed previously.
jkccl9 said:
i guess thats the only thing you can do unless someone else uploads a twrp backup that you can flash.
to start download honor multitool and huawei update extractor. use the unbrick option use lowest Bxxx number first until the phone boots. may have to wait a few minutes
or idk if you can use the 3 button flash method, considering you dont know which version you have installed previously.
Click to expand...
Click to collapse
I don't know this tool, but after a quick research, it looks like Honor Multitool has been made for Honor 6 and 7 devices. Or am I wrong ? As for Huawei Update Extractor, isn't a tradition file extractor good enough for this ? I thought I could flash the ROM from the TWRP menu, but it's not going to be that easy, right ?
Anyway, links for B103 and B104 are dead. But why some zip are NEM-L51C432Bxxx and others NEM-L51C10Bxxx ? Are they from different devices ? Guess I can try them all regardless, things won't get any worse because of that, right ?
Oh, and some zip files are OTA and others are FULL, but assuming I don't have an OS installed, I guess I have to go for the FULL types, correct ?
Sorry for asking so many questions, I'm pretty unaware of what to do in these circumstances and I really hope I'll be able to get my phone working again...
Zarou said:
I don't know this tool, but after a quick research, it looks like Honor Multitool has been made for Honor 6 and 7 devices. Or am I wrong ? As for Huawei Update Extractor, isn't a tradition file extractor good enough for this ? I thought I could flash the ROM from the TWRP menu, but it's not going to be that easy, right ?
Anyway, links for B103 and B104 are dead. But why some zip are NEM-L51C432Bxxx and others NEM-L51C10Bxxx ? Are they from different devices ? Guess I can try them all regardless, things won't get any worse because of that, right ?
Oh, and some zip files are OTA and others are FULL, but assuming I don't have an OS installed, I guess I have to go for the FULL types, correct ?
Sorry for asking so many questions, I'm pretty unaware of what to do in these circumstances and I really hope I'll be able to get my phone working again...
Click to expand...
Click to collapse
the multitool should work for all as honor phones are similar, need huawei update extractor. google which version of the phone you have to see which Cxx you need. yes you need full
p.s you can also use this method https://forum.xda-developers.com/honor-7/help/to-destroyed-ur-h7-noob-friendly-t3554793
jkccl9 said:
the multitool should work for all as honor phones are similar, need huawei update extractor. google which version of the phone you have to see which Cxx you need. yes you need full
p.s you can also use this method https://forum.xda-developers.com/honor-7/help/to-destroyed-ur-h7-noob-friendly-t3554793
Click to expand...
Click to collapse
In the end, I ended trying the second method from there : http://www.gizmoadvices.com/install-stock-firmware-honor-5c-b102/ with a file I got from Huawei Firmware Finder. Basically, in case this can help someone, I extracted the archive content in the internal storage (my phone was plugged to my PC while in TWRP menu), then created a dload folder within which I cut/paste the update.app previously extracted. Then I powered off my device and rebooted it while pressing the volume up, down and power button as you also suggested. After the process completed and another reboot, the whole thing was apparently good to go. For now anyway, I receive phone calls and texts, and network is functioning as well.
Still, I noticed something strange. I downloaded the NEM-L51C10B141 build version, but in my phone info, I have the NEM-L51C432B141, which wasn't even in the list of the zip files from Huawei Firmware Finder. How comes ? Plus, I can't know for sure, but I think I hadn't this version since it is apparently the most recent one available. Is it possible that I have now a more recent build version than my phone had considering it didn't seem to want to update beforehand ? Also, what could be the fallout after that ?
Again, thank you. You've been a huge help, I wouldn't have made it without you. I'll be more careful next time.
Zarou said:
In the end, I ended trying the second method from there : http://www.gizmoadvices.com/install-stock-firmware-honor-5c-b102/ with a file I got from Huawei Firmware Finder. Basically, in case this can help someone, I extracted the archive content in the internal storage (my phone was plugged to my PC while in TWRP menu), then created a dload folder within which I cut/paste the update.app previously extracted. Then I powered off my device and rebooted it while pressing the volume up, down and power button as you also suggested. After the process completed and another reboot, the whole thing was apparently good to go. For now anyway, I receive phone calls and texts, and network is functioning as well.
Still, I noticed something strange. I downloaded the NEM-L51C10B141 build version, but in my phone info, I have the NEM-L51C432B141, which wasn't even in the list of the zip files from Huawei Firmware Finder. How comes ? Plus, I can't know for sure, but I think I hadn't this version since it is apparently the most recent one available. Is it possible that I have now a more recent build version than my phone had considering it didn't seem to want to update beforehand ? Also, what could be the fallout after that ?
Again, thank you. You've been a huge help, I wouldn't have made it without you. I'll be more careful next time.
Click to expand...
Click to collapse
not sure what happened to your build number... np thats the method i use to unbrick my phone done it like 20 times XD
jkccl9 said:
not sure what happened to your build number... np thats the method i use to unbrick my phone done it like 20 times XD
Click to expand...
Click to collapse
Well, I looked at the options and it's clearly not the version I had before, there are some differences here and there. Basically, the build number just refer to the latest security patches, is that it ? So if I have a more recent one, I guess it's just lucky me. Dunno why Huawei didn't propose me to update to it though... And I'm still on Android 6.0.
Sad thing is, this method apparently locked again my bootloader. I guess TWRP is gone too then... Long road ahead.
Thanks again for your help.
Zarou said:
Well, I looked at the options and it's clearly not the version I had before, there are some differences here and there. Basically, the build number just refer to the latest security patches, is that it ? So if I have a more recent one, I guess it's just lucky me. Dunno why Huawei didn't propose me to update to it though... And I'm still on Android 6.0.
Sad thing is, this method apparently locked again my bootloader. I guess TWRP is gone too then... Long road ahead.
Thanks again for your help.
Click to expand...
Click to collapse
no problem, hit the thanks button please!!!
jkccl9 said:
no problem, hit the thanks button please!!!
Click to expand...
Click to collapse
I did.
Can you confirm or infirm what I said about the build number ? Just to be sure.
Zarou said:
I did.
Can you confirm or infirm what I said about the build number ? Just to be sure.
Click to expand...
Click to collapse
i dont know what the Cxx is? the start will be the model and the end Bxx is version of firmware thats all i know :/ i just bought a new phone as my huawei is getting pretty old so havent really been keeping up with any of new stuff huawei do
jkccl9 said:
i dont know what the Cxx is? the start will be the model and the end Bxx is version of firmware thats all i know :/ i just bought a new phone as my huawei is getting pretty old so havent really been keeping up with any of new stuff huawei do
Click to expand...
Click to collapse
Okay, thanks anyway.
Hi guys, I am only a very junior user who randomly flash his phone but most of the time I want my phone to be stable for work. I have had the situation since the recent OTA available, suffered a lot, would like to seek any help or advice.
I have a L09C635B361, Japan version. I updated to Android 7 via OTA, then unlocked / rooted under the instructions in this forum, forgot which exact thread though. Never thought of flashing any customized rom so I haven't realized the update problem until the recent OTA update (from B361 to B382) released. I got the push, downloaded B382 OTA package, restart to TWRP, then the flash was failed in TWRP screen. Restart again, the system notified there was a recent update failure. Then I installed Firmware Finder, downloaded the 3 update zip files, restart back to TWRP, still failed installing. Please refer to the failure screenshot for detailed reson. I have no idea what it said and how I should do differently.
No other way to go, I backed up my system, then wiped my phone, reset to factory mode, but brand new system was very strange: only voice input, no keyboard, missing several key functions such as camera. So I have to restore to my previous system, everything worked well except I can't open "clock".
Right now I am looking at system notification of B382 all the time, but I can't figure out how to get it updated, I don't mind if there's a way enables me go back to stock rom, but it's really hard to find the stock firmware for C635......
Thanks, appreciate your help in advance.
Hey man, try follow this guide to debrand your phone (get onto C432). It will probably unroot you and get you back to stock firmware as well.
https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523
Might want to check around first though, I dont want you bricking your phone on my account.
Good luck
xMrTROLLIPOPx said:
Hey man, try follow this guide to debrand your phone (get onto C432). It will probably unroot you and get you back to stock firmware as well.
https://forum.xda-developers.com/p9/how-to/guide-debranding-to-c432-updating-to-t3551523
Might want to check around first though, I dont want you bricking your phone on my account.
Good luck
Click to expand...
Click to collapse
Thanks bro. I will try the entire process when I have a backup phone.
One more thing is when I first tried to wipe phone, failed for several times. Plus the TWRP flashing error, I have suspect that there's something wrong with my partition information or format error. Can anyone help me to eliminate the possibility by the screenshot please?
On the other hand, I found 3 zip files on Firmware for same version update. Which one should I flash? If I need to flash all of the 3, is there a sequence?
The screenshot for the 3 zip files.
oushouseki said:
The screenshot for the 3 zip files.
Click to expand...
Click to collapse
You flash those in the order they appear. Except the last one, don't flash that (I think). From what I know it's always been update.zip and then update_hw.zip.
I see you're going to flash hw_jp which is the Japanese cust, so ignore the advice above about debranding to c432 as that's essentially the same thing as what you are about to do with those files. (C432 is the European version, which is called update_hw_eu.zip)
Also the voice input only bug is well known. You need to rollback to marshmallow (I forget which firmware but there's a thread on it here somewhere) and then OTA back to nougat and it should fix it.
lostunsunghero said:
You flash those in the order they appear. Except the last one, don't flash that (I think). From what I know it's always been update.zip and then update_hw.zip.
I see you're going to flash hw_jp which is the Japanese cust, so ignore the advice above about debranding to c432 as that's essentially the same thing as what you are about to do with those files. (C432 is the European version, which is called update_hw_eu.zip)
Also the voice input only bug is well known. You need to rollback to marshmallow (I forget which firmware but there's a thread on it here somewhere) and then OTA back to nougat and it should fix it.
Click to expand...
Click to collapse
Well, it ended up with paying 20USD to some "pro"s on taobao.com to unbrick my P9...sigh...am I too old to do this :crying:
I thought I would just casually go through my installed apps and clean some up. I disabled the following...
1. Accessibility Suite
2. Gmail
3. Google TV
4. Google Music
5. Chroma
6. Razor Store
7. Logo+ (Uninstalled)
I then thought to myself that I would probably need the Accessibility Suite for apps that needed that as a permission to work. So I re-enabled it and it updated. I then rebooted and now the phone hangs at the Razor logo. I do have TWRP installed so I can get to that. I also have a complete backup from about a year ago using TWRP which I would like to use as my last resort. I am thinking that by disabling one of the above apps caused this issue. So, can I fastboot and re-enable them using adb? If so what is the command and the name for each app above? I am not an adb guru so the exact commands and names would help. Or if someone can think of another way to get my phone working besides a complete wipe I would greatly appreciate it! I am running MR1 stock with Magisk/art97. I do remember back in the day having a similar problem and I ended up re-flashing the ROM or something and it kept all my data but I think it just repaired the OS or something and that fixed a not booting issue. That was a long time ago so I cannot remember all the specifics but if that rings any bells for anyone as to another way I can approach this I am all ears. Thank you!
Logo+ - you uninstalled it. I dont think any others will prevent booting. If there is no logo, it will sit till it gets one. Reflash logo+ if at all possible. (I have a logo.img in my firmware, but different fone.
Pachacouti said:
Logo+ - you uninstalled it. I dont think any others will prevent booting. If there is no logo, it will sit till it gets one. Reflash logo+ if at all possible. (I have a logo.img in my firmware, but different fone.
Click to expand...
Click to collapse
Thanks for your reply. Logo+ is not a system app and shouldn't have anything to do with the Razor logo when booting up. Logo+ is a 3rd party app that allows to manipulate the colored logo on the back of the phone. For example when a notification comes in Logo+ can light up the colored logo on the back of the phone or make it flash. The app is from here. I've actually uninstalled and reinstalled Logo+ in the past when updating and such with no adverse effects. I can't imagine Logo+ would be the culprit here. What do you think?
I think only logo+ is capable of preventing boot, because your bootlooping. all other apps should NOT cause ANY bootloop, because they do not access anything previous to logo+, your first step in your problem.
Try this...
Logo+ if incorrect in any way will not show. This CAN cause bootloops. No other app you mention can. Perhaps your fone took a silent update, maybe it checked for the Logo+ and 'kicked' you for messing with it. Maybe google decided not to like it, so silently ordered your fone to delete the logo you installed leaving you with no logo+, and until you can see a logo+ your fone will stay there, so try my suggestion, seems your only choice. I have been flashing chips for years so can help, just go with my suggestion, reflash ONLY stock system.img/.bin using your stock flashing application, you'll be glad you did.
Pachacouti said:
I think only logo+ is capable of preventing boot, because your bootlooping. all other apps should NOT cause ANY bootloop, because they do not access anything previous to logo+, your first step in your problem.
Try this...
Logo+ if incorrect in any way will not show. This CAN cause bootloops. No other app you mention can. Perhaps your fone took a silent update, maybe it checked for the Logo+ and 'kicked' you for messing with it. Maybe google decided not to like it, so silently ordered your fone to delete the logo you installed leaving you with no logo+, and until you can see a logo+ your fone will stay there, so try my suggestion, seems your only choice. I have been flashing chips for years so can help, just go with my suggestion, reflash ONLY stock system.img/.bin using your stock flashing application, you'll be glad you did.
Click to expand...
Click to collapse
I will follow your instructions but I am needing some clarification please.
The app Logo+ never came with the stock OS or the Razor Phone 2. It is a separate app made by a 3rd party. So flashing the system.img will not bring back Logo+. So should I first attempt to flash the Logo+ app using TWRP?
If you want me to reflash the stock system.img, I don't believe I have that. How can I obtain this? And could you please provide me with the steps to reflash? Should I use TWRP or fastboot and use Windows adb?
So the Logo+ is only an app. Not a zip. So I don't believe I can flash that. Should I attempt to sideload it? Can I install an app on the phone when the phone cannot boot?
So logo+ IS your prob. Personally I would never use an app to do such work, I'd edit and flash it myself, but hey, you prob know this by now.
Go to (motorola?) Razor support, look for your firmware, it may help if you have phone plugged in while doing so in case they have a detector script to detect firmware for your fone.
Regardless, grab stock offered for your fone. This should also point you in the direction of the correct flashing frmware. once you have them, get back to me.
Or look at what I found using startpage/google:
Need help in flashing stock rom on Razer Phone 2 ! (Stuck in Bootloop)
Hello Everyone , I have ran into a very bad problem and would appreciate some help. I tried rooting my phone (Razer Phone 2 Atnt varient) with the following method...
forum.xda-developers.com
Take your pick, so many stock firmares online here:
Startpage Search Results
www.startpage.com
(I use startpage for these results)
Choose what you believe is for your fone, then read the XDA razor thread I linked to above, I will guide you once you have your files if you still need it, but read the razor thread first
Pachacouti said:
So logo+ IS your prob. Personally I would never use an app to do such work, I'd edit and flash it myself, but hey, you prob know this by now.
Go to (motorola?) Razor support, look for your firmware, it may help if you have phone plugged in while doing so in case they have a detector script to detect firmware for your fone.
Regardless, grab stock offered for your fone. This should also point you in the direction of the correct flashing frmware. once you have them, get back to me.
Or look at what I found using startpage/google:
Need help in flashing stock rom on Razer Phone 2 ! (Stuck in Bootloop)
Hello Everyone , I have ran into a very bad problem and would appreciate some help. I tried rooting my phone (Razer Phone 2 Atnt varient) with the following method...
forum.xda-developers.com
Take your pick, so many stock firmares online here:
Startpage Search Results
www.startpage.com
(I use startpage for these results)
Choose what you believe is for your fone, then read the XDA razor thread I linked to above, I will guide you once you have your files if you still need it, but read the razor thread first
Click to expand...
Click to collapse
The Razer Phone 2 is made by Razer https://www.razer.com/mobile. Motorola makes the Razr which can be confusing.
I don't know how to edit and flash the Logo+ app. Can you do this for me and I'll test? The app is located here https://github.com/CurtisMJ/LogoPlus/releases.
As I understand it as soon as I flash the stock rom it'll put me back to factory settings right? So I'll have to re-personlize my entire phone from scratch. I'd like to leave this as my last resort if possible. So if we can I'd like to flash the Logo+ if you can make that zip for me.
Hi, developer of Logo+ here
I think there's maybe some misunderstanding as to what the app does. It doesn't work on the bootloader splash in any way (this can actually cause failed boots). It's for controlling the RGB on the Razer logo on the back of the device. I named it "Logo+" to avoid any legal issues with caling it "Chroma" since thats a trademark of Razer. The app is entirely user space and is not active during boot. It modifies the lights via sysfs values (with root) that are entirely in RAM so they're cleared on boot.
You can typically just put the .apk in /data/app in recovery mode to install it. I think this may have changed slightly with newer android versions.
Ultimately I don't think Logo+ is needed for or can interfere with boot. I would suggest flashing the system image as suggested for a clean slate.
EDIT: You may end up having to use your last resort backup if you're not keen to loose *too* much data. Not booting is a difficult thing to troubleshoot because there's no feedback as to what went wrong on Android. If its a data thing and not a system thing that is. You could try fastboot flash each system image part to maybe fix any corruption
EDIT2: Take another backup before you do anything though. Titanium back can extract app data from TWRP backups so you can restore your user data at least
CurtisMJ said:
Hi, developer of Logo+ here
I think there's maybe some misunderstanding as to what the app does. It doesn't work on the bootloader splash in any way (this can actually cause failed boots). It's for controlling the RGB on the Razer logo on the back of the device. I named it "Logo+" to avoid any legal issues with caling it "Chroma" since thats a trademark of Razer. The app is entirely user space and is not active during boot. It modifies the lights via sysfs values (with root) that are entirely in RAM so they're cleared on boot.
You can typically just put the .apk in /data/app in recovery mode to install it. I think this may have changed slightly with newer android versions.
Ultimately I don't think Logo+ is needed for or can interfere with boot. I would suggest flashing the system image as suggested for a clean slate.
EDIT: You may end up having to use your last resort backup if you're not keen to loose *too* much data. Not booting is a difficult thing to troubleshoot because there's no feedback as to what went wrong on Android. If its a data thing and not a system thing that is. You could try fastboot flash each system image part to maybe fix any corruption
EDIT2: Take another backup before you do anything though. Titanium back can extract app data from TWRP backups so you can restore your user data at least
Click to expand...
Click to collapse
Thank you for taking the time to chime in here @CurtisMJ. I did end up gettijg it to boot now in partition a. I went into TWRP and switched to partition a and phone boots but no longer has root or magisk. I'm not sure how the partitions work but it looks like there are two that the Razer uses. A and b. And I guess I've been using b since the beginning and since b won't boot now I tried booting off partition a and the phone seems to work as it did. All apps and widgets are in the same place except magisk and phone isn't rooted. I could reflash the system image but the amount of time to re-personalize everything will be extensive. So I just wanted to make sure I did everything I could before that. I'll try copying the apk as suggested and see if that works.
Do you know if there is a way to enable system apps when they've been disabled like I did when phone won't boot? I am in partition a right now and booted and I reinstalled logo+ and saw that all the apps I disabled in OP are back to being enabled. So I am not sure if partition a and b share the same system and user data but everything is exactly what it looks like from partition b. So it is a good chance they share everything except magisk which I guess is flashed at the partition level. Just trying to make sense. Thanks for everyone's time.
So the A-B partition layout is a thing that was introduced by google for more reliable system updates. Effectively the phone has 2 copies of the OS, including system partition,kernel,vendor etc and the phone flip-flops between them on every update, updating the "other" partition to the one its running so if it fails it can boot to the still good one. So you effectively went a system update backwards, but using the same user data partition (or Magisk kept an old copy of the system around). System apps disabled status is stored in /data/system/users/0/package-restrictions.xml which can edited in TWRP with some effort. Magisk is likely flashed to kernel B so you're correct in that its a partition level thing.
CurtisMJ said:
So the A-B partition layout is a thing that was introduced by google for more reliable system updates. Effectively the phone has 2 copies of the OS, including system partition,kernel,vendor etc and the phone flip-flops between them on every update, updating the "other" partition to the one its running so if it fails it can boot to the still good one. So you effectively went a system update backwards, but using the same user data partition (or Magisk kept an old copy of the system around). System apps disabled status is stored in /data/system/users/0/package-restrictions.xml which can edited in TWRP with some effort. Magisk is likely flashed to kernel B so you're correct in that its a partition level thing.
Click to expand...
Click to collapse
Thank you so much for that explanation. That makes a lot of sense. My OS has been MR1 for a long time and OTA has been turned off so I guess there hasn't been any OS updates so there's been no reason to switch between partition a and b I guess. So I guess there's technically been a backup of my OS all this time with the double partition thing which is cool. And I guess I could magisk and root partition a. If I reflash the system image to partition b will that effect partition a?
I think he's talking bootloaders re: a/b partitioning, The point of A/B being if your using 'A' to boot, and you update, the updated BOOTLOADER is flashed to 'B' and when you reboot the f'n, 'B' becomes your main bootloader until next update where that update will use 'A' having been 'emptied' after the previous update sort of thing, I dont have a/b, but this is my understanding of the a/b partitioning,,,?
Opens up the options for dual booting fone with or without magisk, If I had a/b, i'd flash magisk to one and stock to the other...
Pachacouti said:
I think he's talking bootloaders re: a/b partitioning, The point of A/B being if your using 'A' to boot, and you update, the updated BOOTLOADER is flashed to 'B' and when you reboot the f'n, 'B' becomes your main bootloader until next update where that update will use 'A' having been 'emptied' after the previous update sort of thing, I dont have a/b, but this is my understanding of the a/b partitioning,,,?
Opens up the options for dual booting fone with or without magisk, If I had a/b, i'd flash magisk to one and stock to the other...
Click to expand...
Click to collapse
I was thinking the same. I believe I have the opportunity to stick with the working partition which is a, and magisk that. And then for the partition b I could put the official lineage OS on there. My only concern is if lineage had an update does it update both a and b partitions which I would lose my original OS then. I guess I'll have to research.
I think it's safe to assume that when an update takes place, upon reboot, whichever bootloader you WERE using, a OR b, is now empty... it's staring you in the face
Just remember what we agreed on. Once you magisk your current bootloader, make a backup of said bootloader, store it on main computer, because when you flash lineage, your magisk in your current slot will be wiped. Once you have installed Lineage, you will need to boot into fastboot to re-flash magisk, and then use fastboot boot a or b for dual booting until you get an app or sumat to choose in gui what you choose to boot into
What I am thinking I will do for the time being is stick with booting into partition a which is currently not rooted and I am fine with that. At least it works unlike partition b. This is my main phone, my only phone, and I need it to work right now so would rather not risk causing issues flashing stuff. I know enough about flashing to be dangerous.
Currently the official release of lineage for the Razer Phone 2 is still not stable yet according to the forum here. So camera still doesn't work and I need the camera to work. So I'll wait until the camera is fixed which hopefully will be soon.
You stated in your previous post "sumat to choose in gui what you choose to boot into" can you clarify? Are you saying there is a GUI that helps choose what to boot into? Currently I am using TWRP to select partition a or b to boot into. It takes about a minute to load into TWRP but I wouldn't be doing it often. I don't think I really have a use for dual booting.
I appreciate the help. As soon as I am ready to proceed I'll update this post and If you're still around I'll receive your assistance. Thank you for your time.