Related
I've searched but apparently it seems like most of the answers have been deleted or redacted.
My problem...
I was just given a Yoga Tab 2 from my sister who has given up on trying to fix it.
The tab was on 5.01 and rooted when she got a system update. She ran the update but now the tablet freezes during/after the boot animation.
It will go into fastboot but is not recognized by ADB.
She tried to install the original Lollipop firmware through recovery but ended up getting a system 7 error.
This is exactly what I see when in the bootloader screen
FASTBOOT MODE
PRODUCT_NAME - YT2
VARIANT - YOGA Tab1
HW_VERSION -
BOOTLOADER VERSION - unknown
IFWI VERSION - Blade_21.x64.0005.R00.1504101447 FFD8_X64_R_
SERIAL NUMBER - BaytrailD454B***
SIGNING - ?
SECURE_BOOT - ?
E: No valid installer medium found
I know nothing about Lenovo and how they do things but I know that with HTC you have to go back to 100% locked and stock before you can install an OTA. If you do try the OTA usually just won't install but unfortunately this thing seems to be at least soft bricked.
Is there a way for me to maybe roll back? I've read about people going back to KK in order to get the LP OTA but all links to the KK firmware are gone.
Thanks a lot, I appreciate any help I can get...
BTW, She is under warranty but of course she was rooted and is worried that repair will cost her almost as much as she paid for the Tab when they realize and void her warranty.
If its the same as the 1050f try these files.
http://tinyurl.com/zmmaww5
http://tinyurl.com/zgt7sjo do not bother about the warning with this one, its something to do with its size, just download it.
corasman said:
If its the same as the 1050f try these files.
http://tinyurl.com/zmmaww5
http://tinyurl.com/zgt7sjo do not bother about the warning with this one, its something to do with its size, just download it.
Click to expand...
Click to collapse
Thank you. I used the Restore KitKat Bios you posted along with an 830F specific KitKat firmware from the Russian Lenove site. Worked fine after editing the flash.xml file to allow for a larger system.img file.
The tablet is now back from the dead. Unfortunately it gets the 5.0 update but fails in the Lenovo Recovery when trying to flash the OTA. It gets to 100%, stays like that for a bit and then a blue X saying flash failed. After that I'm back to a black screen and have to reflash the kitkat firmware to get up and running again.
I have no idea why the OTA flash constantly fails but I guess I have to do a bit more research and hope I can get her up to date.
Did you set the country code , without setting it updates fail.
Look at this advice from ionioni to me about setting the code
http://forum.xda-developers.com/thinkpad-tablet/general/set-country-code-t3308024
corasman said:
Did you set the country code , without setting it updates fail.
Look at this advice from ionioni to me about setting the code
http://forum.xda-developers.com/thinkpad-tablet/general/set-country-code-t3308024
Click to expand...
Click to collapse
Outstanding!!! I entered the code in contacts and it gave me a menu of different countries to choose from. I Chose US and she rebooted, went into recovery, ran a bit and rebooted into another fresh install which looked completely different. We're talking different wallpaper, and different apps. After that it successfully installed 4 or 5 OTAs and as far as I can tell it is now completely up to date!
Android Version is 5.01
Build is S100250-160119
Kernel Version is 3.10.20-x86_64byt-g9f7fad7
Security patch is dated 2016-02-01
I'll wait a few days before I root and install Xposed just to be 100% certain it's up to date.
Of course my sister will probably ask for it back now.
Either way, THANK YOU VERY MUCH corasman!!! Your help has been invaluable!
I am so pleased it worked for you, ionioni helped me so much and now I am trying to do the same for others.
Hi guys,
I've been searching all over the show but can't seem to find leaked Nougat firmware for my device :/ it's a C183 released in New Zealand. Anyone know if there was actually firmware leaked for the C183 region?
cheers
gymfreak7855 said:
Hi guys,
I've been searching all over the show but can't seem to find leaked Nougat firmware for my device :/ it's a C183 released in New Zealand. Anyone know if there was actually firmware leaked for the C183 region?
cheers
Click to expand...
Click to collapse
I purchased the 2 degrees stock firmware for NXT-L09_C183B130_Firmware_New Zealand_Brightstar NZ Limited_Andriod 6.0_EMUI 4.0_05013NLM
Link is here https://drive.google.com/file/d/0B3pCekrpvWeaNk5meFMtR1dadms/view?usp=sharing
I have that version, I updated to B330 and my cust get broke (C900), but the system with EMUI 4.1 works fine, I tried to update to nougat but the system does not allow with C605 and C432. Maybe with other version work the update.
Yeah I also purchased through 2degrees. Unfortunately it seems firmware for this region hasn't been released still... I was expecting an update back in Feb. Frustrating.
Iv'e still seen nothing
I remember when I was using the Mate2, there were countless debates if/when LL5 was going to be released.
Huawei stated by the first half of 2015. It was released I think it was JUNE 30TH...the "last" day of the first
half of 2015.
If that holds true this time, then they announced Nougat 7 for the Mate 8, "by the end of the 1st quarter of 2017"
would mean...by March 31st. Just something to think about.
Personally, I'm holding off. I can wait. I use a BT headset for the phone, and use it A LOT. The past 4 phones I've
had, I've never used it by holding the phone to my ear, only through the headset. I've seen scattered reports of
issues (not just the Huawei phones), of glitches with bluetooth on nougat.
Marshmellow for me, on the mate8 is VERY stable, so it's a choice. If you gotta have the latest/greatest, there are
sources you can find to download it, but, if you want stable, you might want to wait a while.
p51d007 said:
I remember when I was using the Mate2, there were countless debates if/when LL5 was going to be released.
Huawei stated by the first half of 2015. It was released I think it was JUNE 30TH...the "last" day of the first
half of 2015.
If that holds true this time, then they announced Nougat 7 for the Mate 8, "by the end of the 1st quarter of 2017"
would mean...by March 31st. Just something to think about.
Personally, I'm holding off. I can wait. I use a BT headset for the phone, and use it A LOT. The past 4 phones I've
had, I've never used it by holding the phone to my ear, only through the headset. I've seen scattered reports of
issues (not just the Huawei phones), of glitches with bluetooth on nougat.
Marshmellow for me, on the mate8 is VERY stable, so it's a choice. If you gotta have the latest/greatest, there are
sources you can find to download it, but, if you want stable, you might want to wait a while.
Click to expand...
Click to collapse
Nope still no sign of c183 nougart firmware and now it's may. I am beginning to believe that Huawei are not going to release firmware for this region. It may be potentially due to the poor sales of the device in the region. Who knows. I have not been able to find a single other firmware variant that will flash to the phone. It's disappointing that we've been let down like this with it being a flagship device.
Does anyone have the backup of the cust for this region firmware? I will Rollback my update from 330 (Where I lost my cust), and I will try to change the region, Does anyone tried to change the region to get updates?
mmc00 said:
Does anyone have the backup of the cust for this region firmware? I will Rollback my update from 330 (Where I lost my cust), and I will try to change the region, Does anyone tried to change the region to get updates?
Click to expand...
Click to collapse
Here is Cust Backup .tar.gz
https://drive.google.com/open?id=0B3pCekrpvWeaUzNHTWkxOUs1LWs
Here is Cust Backup .img
https://drive.google.com/open?id=0B3pCekrpvWeaN0dLaEhKVy1yN3ce
these were taken from partition backup manager a few months ago ...these are from NZ L09-C183B150 EMUI 4.0
I have managed to upgrade to Nougat EMUI 5 using firmware finder without root or unlocking boot loader....following L29-636 Starting from file from B180 I didn't change cust but after first update it changed to L29 636 and has had no problems at all
The B585 is smooth and I have had no issues with batter drain or restarts at all...very happy with this after 3 weeks no problems at all.
The only issue was that after B330 which updated successfully, I did discover that my bootloader did get unlocked so I used DC Unlocker to re lock again which cost me 6 credits....now unrooted and bootloader locked.
image1
https://drive.google.com/open?id=0B3pCekrpvWeaeS1PYUg2dFVNRHM
image2
https://drive.google.com/open?id=0B3pCekrpvWeaWUhnWWZDZ0hEVG8
I want to upgrade my Mate 8 too. Are you able to provide the steps you took to upgrade to N?
What information do you need regarding my device?
Model: HUAWEI NXT-09
Build: NXT-L09C183B130
EMUI version: EMUI 4.0
Android version: 6.0
Hardware version: NEXT_L09_VN2
Bootloader: NXT-C900B180_FASTBOOT
Kernel: NXT-C900B191_BOOT
AP version: NXT-C900B130_SYSTEM
Parameter: CVersion:C183 DVersion001
P-00.00.000 G-16.00.004 E-40.01.000
brockles said:
I want to upgrade my Mate 8 too. Are you able to provide the steps you took to upgrade to N?
What information do you need regarding my device?
Model: HUAWEI NXT-09
Build: NXT-L09C183B130
EMUI version: EMUI 4.0
Android version: 6.0
Hardware version: NEXT_L09_VN2
Bootloader: NXT-C900B180_FASTBOOT
Kernel: NXT-C900B191_BOOT
AP version: NXT-C900B130_SYSTEM
Parameter: CVersion:C183 DVersion001
P-00.00.000 G-16.00.004 E-40.01.000
Click to expand...
Click to collapse
This is not for the faint hearted , You need to make sure you have backups of oem.info and cust for for the NZ model.
Also have the NZ firmware update app if needed, here on my google drive....unzip and place extracted update.app onto your SDCARD in dload folder
https://drive.google.com/file/d/0B3pCekrpvWeaNk5meFMtR1dadms/view?usp=sharing
Using HCU Client read phone info take a a screen shot with repair UMTS with of your serial number, imei number, & sub imei, WIFI & bluetooth MAC vendor etc...store this on your PC because you may need these settings if you lose modem settings after unbricking from DC Phoenix
I then would recommend that you have DC Phoenix on stand by and bookmark this link
https://forum.xda-developers.com/mate-8/help/nxt-c900b180-to-nxt-l29c432b330-easily-t3611500 even though its for 432 it will still get you unbricked if it all goes sour.
Now....just to clarify I was on stock firmware L09C185B130 same as your model (shared from link above)with locked bootloader and no root make sure you have developer mode enabled and OEM unlock enabled.
If any of the above is confusing then I would recommend that you go no further.
1st Install Firmware finder and and Firmware finder proxy. enable proxy port in wifi settings ie localhost port 8080
2nd Open FF go to settings and enable USE PROXY TO INSTALL disable SHOW PACKAGES FROM CURRENT REGION
3rd Open go back to FF start and type in NXT-L09636 and click search go to the first and lowest firmware which is B170 download and then install via proxy thru normal update it will show up in Phone settings system update if it doesn't then go back into FF settings and tell it to use proxy to install and then push system update to detect.
This should install without any hitches but you will notice now your firmware will be c900b170
goto FF again and choose the next firmware which is 180 then 193 then 211 etc etc when you get to 330 you will have to trial and error which file will work, I started with the largest full OTA but I dont remember in the end which one worked I think I had 3 or 4 goes if it fails it will stop at 15% and then stop you will have to force reboot thru holding power key but it should boot to normal and then just try another firmware of the same number.
when you get to b330 you should find you have changed to L29636B330 but you will now have unlocked bootloader? not sure why? anyway....keep trial and error updates until you get to B585
Hope it works good luck
Mickie.C said:
This is not for the faint hearted , You need to make sure you have backups of oem.info and cust for for the NZ model.
Also have the NZ firmware update app if needed, here on my google drive....unzip and place extracted update.app onto your SDCARD in dload folder
https://drive.google.com/file/d/0B3pCekrpvWeaNk5meFMtR1dadms/view?usp=sharing
Using HCU Client read phone info take a a screen shot with repair UMTS with of your serial number, imei number, & sub imei, WIFI & bluetooth MAC vendor etc...store this on your PC because you may need these settings if you lose modem settings after unbricking from DC Phoenix
I then would recommend that you have DC Phoenix on stand by and bookmark this link
https://forum.xda-developers.com/mate-8/help/nxt-c900b180-to-nxt-l29c432b330-easily-t3611500 even though its for 432 it will still get you unbricked if it all goes sour.
Now....just to clarify I was on stock firmware L09C185B130 same as your model (shared from link above)with locked bootloader and no root make sure you have developer mode enabled and OEM unlock enabled.
If any of the above is confusing then I would recommend that you go no further.
1st Install Firmware finder and and Firmware finder proxy. enable proxy port in wifi settings ie localhost port 8080
2nd Open FF go to settings and enable USE PROXY TO INSTALL disable SHOW PACKAGES FROM CURRENT REGION
3rd Open go back to FF start and type in NXT-L09636 and click search go to the first and lowest firmware which is B170 download and then install via proxy thru normal update it will show up in Phone settings system update if it doesn't then go back into FF settings and tell it to use proxy to install and then push system update to detect.
This should install without any hitches but you will notice now your firmware will be c900b170
goto FF again and choose the next firmware which is 180 then 193 then 211 etc etc when you get to 330 you will have to trial and error which file will work, I started with the largest full OTA but I dont remember in the end which one worked I think I had 3 or 4 goes if it fails it will stop at 15% and then stop you will have to force reboot thru holding power key but it should boot to normal and then just try another firmware of the same number.
when you get to b330 you should find you have changed to L29636B330 but you will now have unlocked bootloader? not sure why? anyway....keep trial and error updates until you get to B585
Hope it works good luck
Click to expand...
Click to collapse
When you converted your L09 to L29 did u get dual sim menu in Settings?
I want to crossflash my L09C432 to L29C432 so i can use dual sim function.
It works on Mate 9 and P10 singel sim when crossflash.
Just want to check if it is the same on Mate 8?
Sent from my LON-L29 using XDA Labs
I change the region and the model to L29C636, thanks to Mickie's helps, my steps:
1. I install the B330, wich a get from the Firmware official thread, and I used the 3 button method.
2. With SRK Tool, unlok the bootloader and get root .
3. Again with SKR Tool, change the region, (Change oeminfo and custom bin) to Asia (C636) and model (L29).
4. Donwload and Install the L29C636B330 (3 button method), I have to make a Factory Reset, with this firmware I lost the root and get locked the bootloader.
5. When I start normally, automatically get the update by OTA to L29C636B563.
mmc00 said:
I change the region and the model to L29C636, thanks to Mickie's helps, my steps:
1. I install the B330, wich a get from the Firmware official thread, and I used the 3 button method.
2. With SRK Tool, unlok the bootloader and get root .
3. Again with SKR Tool, change the region, (Change oeminfo and custom bin) to Asia (C636) and model (L29).
4. Donwload and Install the L29C636B330 (3 button method), I have to make a Factory Reset, with this firmware I lost the root and get locked the bootloader.
5. When I start normally, automatically get the update by OTA to L29C636B563.
Click to expand...
Click to collapse
Did u get dual sim settings when u crossflashed? Did u have L09 before crossflash?
Sent from my LON-L29 using XDA Labs
First excuse me for opening an other thread like this, i think i have read all other threats regarding my problem, but none have the same situation
My Huawei M3 Wifi (BTV-W09) seems semi bricked after installation of Nougat Update.
The Installation (Force Install with dload) gave me an error and also while boot i got the error message: "Your device has failed verification and may not work properly."
I have the option to press "Powerbutton" and the device will boot up. I checked the Version and it showed android 7 + EMUI 5. The only problem was that almost every system app was missing, like keyboard, calendar etc. (playstore was there)
So i tried to do the rollback with:
HUAWEI MediaPad M3 8 Rollback Package%28BTV-W09 %2CC900B300%2C EMUI5.0%2BAndroid7.0 rollback to EMUI4.1%2BAndroid 6.0%29
The Installtion (force update) gets stuck at 5% and after like 3-5 minutes the tablet will boot up showing the same boot error that can be skipped with pressing powerbutton. I checked sytem and it still showed "android 7 + EMUI 5" but built : BTV-W09C900B300
I think this is the one i "need" to be able to install the "HUAWEI MediaPad M3 8 Firmware %28BTV-W09 %2CC100B006%2C EMUI4.1%2BAndroid 6.0%29"
Problem is regardless which "update.app" i try to force install will get stuck at 5% and give me same error. I have ADB/Fastboot installed and tried some different things like flashing/unbricking it with "Huawei Multitool" where you can extract like boot.img or recovery.img and try to flash it.
Also getting an error. I can access eRecovery witout problems, the option to fix it by itself by wifi doesn`t work. I can´t access "normal" recovery and i think there is the problem (may got bricked while flashing Nougat?) I think its recovery problem, cause when i boot it up to the "half-installed" Android and go into setting "hard-reset" option i know it would boot up intoi recovery and would erease everything, while bootup it shows error "reset failed".
In fastbootmode i see bootloader: unlocked FRM: unlocked
I tried to install TWRP recovery with adb but get error: adb remote command not allowed
I downloaded like 15 different Android Versions 6+7 Emui 4.1+5 to try with force update but none worked, may i have to flash special version of recovery first?
I just want a normal version of android 6 or 7 i dont mind but at the moment with half working 7 "without" systemapps its a hardtime.
I hope someone can help me.
This isnt my first android device and im not a total noob i unlocked bootloader and flashed kernels on many other phones but with the W-09 where i did nothing special i dont get why "recovery got broken"
Thanks in advance
You haven't read other threads too well: more times people reported that the bootloader got locked after an update still declaring itself unlocked!
Second thing you have not found: the Nougat update consist of 2 packages and the second must be installed from TWRP.
nicolap8 said:
You haven't read other threads too well: more times people reported that the bootloader got locked after an update still declaring itself unlocked!
Second thing you have not found: the Nougat update consist of 2 packages and the second must be installed from TWRP.
Click to expand...
Click to collapse
thanks for your anwser, i read that so i also tried unlocking it "again" and it quotet it is also unlocked in adb. I also know that there are 2 packages. That you need TWRP i didnt know thanks so i am a bit smater now. I think i ll try "relock" and unlock it again might be the right way, thanks for the tip.
kivi90 said:
I think i ll try "relock" and unlock it again might be the right way, thanks for the tip.
Click to expand...
Click to collapse
This is nonsense. Unlock, install the right TWRP then install the second zip package.
nicolap8 said:
This is nonsense. Unlock, install the right TWRP then install the second zip package.
Click to expand...
Click to collapse
i cant unlock cause i dont have the code, on the huawei page i try do make an account and get the code by providing the necessary information.
I just uploaded a picture, i choose "before EMUI5" cause this is the only option i can choose "tablets". --> i choose "tablet wifi" , enter product model "BTV-W09" then the serialnumber i can see in setting: 28D6R17316XXXXXX but then i have the problem to input product id, it say i can get it through "Dialer" app (which i dont have in wifi model ) or the calculator. Problem is in my damaged installation there is no huawei calc, other calcs from store dont work (read that problem in other threats) I tried many apps from appstore to get a product ID but huawei site keeps saying wrong product ID =/
With the program DC Unlocker i am able to see a MEID i dont know if its the right one, i tried my luck with the Product ID Generator from Huawei but it doenst work. (device not supported)
It's very strange that it says bootloader unlocked if you have never unlocked...
And was very stupid to try to installl a beta release without before unlocking and taking a backup.
Exhange your device for a Nokia 3110!
nicolap8 said:
It's very strange that it says bootloader unlocked if you have never unlocked...
And was very stupid to try to installl a beta release without before unlocking and taking a backup.
Exhange your device for a Nokia 3110!
Click to expand...
Click to collapse
yeah at this device i never touched bootloader, i didnt think it would become such a big deal , i didnt want unlocked bootloader or other recovery just newest android. Never had any problems with the "force update function" to come back to stock. I tried DC Unlocker but cant get further cause device need to get into manufature mode (thorugh dialer or calculator which i both dont have) i hope maybe i find one more way.
Did you ever find a fix
Did you ever find a way to fix this. I'm in the same situation. I even did a VPN on my router to give me a Hong Kong address for erecovery and that still didn't work. I have the exact same product. Like you I tried to various attempts to download a new recovery, but nothing works. Nice hardware, but some of the worst software/firmware I have ever dealt with since starting with the first release of Android on the HTC Hero.
kivi90 said:
yeah at this device i never touched bootloader, i didnt think it would become such a big deal , i didnt want unlocked bootloader or other recovery just newest android. Never had any problems with the "force update function" to come back to stock. I tried DC Unlocker but cant get further cause device need to get into manufature mode (thorugh dialer or calculator which i both dont have) i hope maybe i find one more way.
Click to expand...
Click to collapse
I had mostly the same problem. I rolled back to 4.1 using the rollback and the actual 4.1 update.app. I think that puts you on C100 if I remember right. Tablet I have is C128 (USA) but no problem for this step. Get the Product ID from the calculator. Allow OEM unlock in the settings, then unlock it using the unlock code. Email yourself the unlock code because who knows if their website will even be functional next time. Alternatively you can extract the stock calculator from the update_data_usa.zip or whatever and try to use DC with 5.0. That second update zip does not install properly via the dload method, so a bunch of stock apps don't get installed. You can kind of hack it and flash it via TWRP but I didn't do it that way.
Or...you can use firmware finder to force an OTA from 4.1 right up to 5.0 (350), then take that last partial OTA to 351 after as well. The way to do that is via DNS in firmware finder. Find the Full OTA in firmware finder you want, send it to the updater by changing your DNS the way it tells you to, and when it does the OTA, everything will be properly installed basically the official way. Good as new. Flash TWRP to recovery2 and replace the erecovery. Keep the stock recovery as is. Install magisk. Golden.
---------- Post added at 03:36 AM ---------- Previous post was at 03:26 AM ----------
kivi90 said:
So i tried to do the rollback with:
HUAWEI MediaPad M3 8 Rollback Package%28BTV-W09 %2CC900B300%2C EMUI5.0%2BAndroid7.0 rollback to EMUI4.1%2BAndroid 6.0%29
The Installtion (force update) gets stuck at 5% and after like 3-5 minutes the tablet will boot up showing the same boot error that can be skipped with pressing powerbutton. I checked sytem and it still showed "android 7 + EMUI 5" but built : BTV-W09C900B300
I think this is the one i "need" to be able to install the "HUAWEI MediaPad M3 8 Firmware %28BTV-W09 %2CC100B006%2C EMUI4.1%2BAndroid 6.0%29"
Problem is regardless which "update.app" i try to force install will get stuck at 5% and give me same error.
Click to expand...
Click to collapse
Also, as far as the rollback, you need to do the first one (the C900 which is just a compatibility fix to allow rollback, previously used by beta testers I believe). Then you need to do the second one, the C100. If it is getting stuck, try downloading it again and be sure you don't have anything else in the /dload directory on either internal or the sd card. I had one on both at one point so maybe that happened to you. The C900 should be very quick but the C100 will slowly progress after 5% all the way around in several minutes.
When you get to updating back to 5.0, you can choose whichever region you want as long as it is a full OTA. C128 is USA and that's what I bought so that's what I picked. That gets you back in the right OTA update channel after that.
Hi guys,
I started as a novice and have learnt the hard way.
Has anyone tried rollback to EMUI 4.1 EU version on a US device (W09) and are there any problems I should be aware of?
I have had the exact same problem shared in this thread and have gone through the pain of finding a solution. My last resort is to rollback to 4.1 and restart the whole process.
@deV14nt: you suggested that when updating back to EMUI 5.0, I can choose the region even if my EMUI4.1 is EU version. How does this work?
Thanks in advance for your help.
Hi all,
I'm on WAS-LX1AC432B184 and i can't update via OTA because "no update" and I think there's update as a friend of mine has the same phone but different build numbers as i needed to unlock my dual sim capability.
When i bought my phone i could only use 1 sim then i changed it to a dual sim. Can this be the reason why i can't get updates? The guy that did the dual sim conversion told me that i will be able to get updates as normal but i don't at all.
Please help me get the latest update so that i can enjoy the new Android – 8.0 Oreo
Hey there, by looking at your build number, you've got a 3GB RAM variant (LX1 instead of LX1A) Dual SIM (even build number) P10 lite on the global cust (C432).
The strange thing is the build number, stuck at 184 when Nougat arrived at B209/210 (Oreo is at B360/361).
Maybe you did some kind of modification (root, bad EMUI flash in the past) to the system so you can't receive official Huawei updates via OTA?
Have you tried clicking on the top right in System Update > Download latest full package?
Just some guesses here…
Probably, the you're huawei p10 lite dual is a branded? Usualy these models is the very slow for porting major release.
zYoshi said:
Hey there, by looking at your build number, you've got a 3GB RAM variant (LX1 instead of LX1A) Dual SIM (even build number) P10 lite on the global cust (C432).
The strange thing is the build number, stuck at 184 when Nougat arrived at B209/210 (Oreo is at B360/361).
Maybe you did some kind of modification (root, bad EMUI flash in the past) to the system so you can't receive official Huawei updates via OTA?
Have you tried clicking on the top right in System Update > Download latest full package?
Just some guesses here…
Click to expand...
Click to collapse
Hi zYoshi,
the download latest full package is greyed out... i have done a dual sim conversion in the past not sure if it was done correctly but i got it done... is there anyway i can fix this?
I want to get new updates for my phone to be honest.
sham_1 said:
Hi zYoshi,
the download latest full package is greyed out... i have done a dual sim conversion in the past not sure if it was done correctly but i got it done... is there anyway i can fix this?
I want to get new updates for my phone to be honest.
Click to expand...
Click to collapse
Hi sham_1
I sent you a guide wrote quickly in DM (for anyone who might need it, I left it here).
One quick question, now you have an even build number, right? That means that you are on a Dual-SIM firmware.
I suggest you to follow these steps and maybe wait some weeks because I did something similar too while Oreo was hitting Huawei's servers, but I received it only a month later, when the IMEI finally matched my firmware (the IMEI has to be approved in order to receive updates, suggest to "check firmware availability" on Firmware Finder).
"Hey,
I'm not so experienced in Huawei modding, but I managed to debrand my device from C55 to C432, so maybe it's worth a shot.
•
Anyways, try this:
- Download Firmware Finder from Play Store
- open it and click on WAS-LX1C432
- search for builds like B210 (must be an even number and not an Oreo B361, otherwise you can brick your device) choose a FullOTA
- click on update via proxy/DNS, follow the steps on screen
•
The important thing here is to know if the phone grants you into updating with that build, then failing in erecovery (detecting an error, no brick) so that you can reboot with not updated firmware and do a standard System Update from the settings, that update will contain the same build that you've got installed, but it will be used to basically overwrite everything without losing any data, even thought I suggest you to do a backup.
•
Before doing any of the steps I gave you, could you please describe me what you did, what method did you follow?
•
In this post, I am giving steps that worked for me when I had a corrupted firmware, but your problem may be different from this.
Check also the HWOTA method (to solve the same problem but with the warranty void, I suggest to use it only if the above method doesn't work), search "HWOTA P10 lite" on Google for more info.
•
Hope this helps
-zYoshi"
1. Thanks to @FP_XDA and GSMZambia for the great directions found here
2. The other stuff and ideas:
The above method does put the U firmware on your phone. I had trouble getting it to connect to the network. I did try different combinations of files in the AP tar; CP; and CSC, but it would either not connect after a factory data reset or loop with the message about my SIM has changed, please restart.
I tried just flashing the following combinations through flashfire, but maybe this is a Sprint SIM issue and it works on other SIM cards; however, I have Sprint.
The U firmware seemed to work fine on the software. Including boot.img in flashfire would take away the eng_boot and root. I just had trouble connecting to the Sprint network.
Do you need to use the v5 combo file and flash a certain CP/CSC before going through the rooting steps? The U firmware CSC file is different in size, so is it a partition (PIT) issue since that will write the cache.img.ext4 file and those vary in size from stock to the U? Is there a certain order to flash in flashfire to get it to work properly?
Anyway, I downloaded several U CSC firmwares (XAA, XAS, SPR (last two are sprint)), but ran into some network issue every time. The operating system seemed stable, but the lack of connection and some random entries under settings make it so close, but yet so far.
I don't mind the Sprint firmware, but can you unlock additional LTE bands if you use the stock sprint firmware on another carrier?
Thanks for any help!
Here is more info about the Settings submenu options:
Here is some more detailed info:
The submenus under settings give me options like K twophoneservice; T roaming; Giga LTE. I think it is CSC related as those carriers are Korean based. I think this may be my issue along with a few others I've seen on reddit. Just wondering why it says that though. I used the G930U version, so not sure why this would appear.
Any help or suggestions?
Thanks
Bootloop
Did you get Oreo working while running on v5? Have followed steps in that video but the phone always gets stuck in a boot loop. I extracted the latest Oreo files from the AP file and every seems to flash right but gets stuck in a boot loop after flashfire reboots. Have tried multiple times with same result. Would rather not upgrade to v6 but was trying to get Oreo working.
Aggiedude said:
Did you get Oreo working while running on v5? Have followed steps in that video but the phone always gets stuck in a boot loop. I extracted the latest Oreo files from the AP file and every seems to flash right but gets stuck in a boot loop after flashfire reboots. Have tried multiple times with same result. Would rather not upgrade to v6 but was trying to get Oreo working.
Click to expand...
Click to collapse
I didn't try Oreo, but I didn't have any success getting Nougat to work. It would install and run fine, but I never got it to connect to a network. I tried flashing different imgs and making zip files with additional files to add to the system and same result. I do have additional LTE bands unlocked (12,13,17), but since I still have sprint, I have no way to test it.
I assume that everything would work normal except for VoLTE, but I think you could add that with root.
lvpre said:
I didn't try Oreo, but I didn't have any success getting Nougat to work. It would install and run fine, but I never got it to connect to a network. I tried flashing different imgs and making zip files with additional files to add to the system and same result. I do have additional LTE bands unlocked (12,13,17), but since I still have sprint, I have no way to test it.
I assume that everything would work normal except for VoLTE, but I think you could add that with root.
Click to expand...
Click to collapse
You have to follow the other guide on here about disabling packages. The only problem: you can't disable packages anymore with the apps from the play store. Samsung stopped that. There are system level applications that are blocking you from connecting to sprints network after flashing eng_boot. My guess is you flashed eng_boot, phone booted, then shutdown and reboot, now no network connection? This happens with the binary 4 version as well. I have been on nougat rooted using U firmware for a good while. I once had to re-install everything and when I went to disable the apps, I couldn't. There is a way to disable them via ADB but its not easy and requires patience. But once those packages are disabled, you will have a perfectly running phone with root.
Here are the packages:
XMayhem2099 said:
7. Disable the following packages via bk or adhell
Chameleon
Sprint OMADM
Sprint OMADM Phone Interface
MDMApp
SecurityLogAgent
Security Policy Updates
Security Storage
Click to expand...
Click to collapse
I came here looking to see if the same eng_boot works on Oreo. Guess I will just have to go ahead and try it myself
elesbb said:
You have to follow the other guide on here about disabling packages. The only problem: you can't disable packages anymore with the apps from the play store. Samsung stopped that. There are system level applications that are blocking you from connecting to sprints network after flashing eng_boot. My guess is you flashed eng_boot, phone booted, then shutdown and reboot, now no network connection? This happens with the binary 4 version as well. I have been on nougat rooted using U firmware for a good while. I once had to re-install everything and when I went to disable the apps, I couldn't. There is a way to disable them via ADB but its not easy and requires patience. But once those packages are disabled, you will have a perfectly running phone with root.
Here are the packages:
I came here looking to see if the same eng_boot works on Oreo. Guess I will just have to go ahead and try it myself
Click to expand...
Click to collapse
The version used by GSMZambia includes a boot.img file, which removes the eng_boot and root after a factory reset. It sounds like you are actually still b4 for everything. This version is for people on b5/6 and want to install the U firmware. However, you are correct about disabling those packages when rooting on the U firmware. You lose root and eng_boot by flashing the stock boot.img in flashfire. The point is to have the U firmware without root on a b5/6 Sprint S7/Edge.
Maybe it would work if you flash the eng_boot again and disable, but then you are stuck on the eng_boot. Plus it messes with Knox, so I'm not sure if something like SABS or Adhell would even work.
lvpre said:
The version used by GSMZambia includes a boot.img file, which removes the eng_boot and root after a factory reset. It sounds like you are actually still b4 for everything. This version is for people on b5/6 and want to install the U firmware. However, you are correct about disabling those packages when rooting on the U firmware. You lose root and eng_boot by flashing the stock boot.img in flashfire. The point is to have the U firmware without root on a b5/6 Sprint S7/Edge.
Maybe it would work if you flash the eng_boot again and disable, but then you are stuck on the eng_boot. Plus it messes with Knox, so I'm not sure if something like SABS or Adhell would even work.
Click to expand...
Click to collapse
But from what I read in the original post is that BEFORE using flashfire to flash the original boot.img, you are running the eng_boot.img. Is this correct? Btw, flashfire NEEDS root. So you ARE rooted at some point. Therefore, this is why you are being kicked from the network. Thus, disabling those packages will prevent that. But SABS and Adhell no longer work, at least I couldn't get them to. I even paid for the one and used it once. So I'm a bit annoyed with that. But yes, I am still on binary 4 for the BL. It was a requirement when purchasing my phone on Craigslist xD
But, what you are after may not be feasible. This is what you want: 100% U firmware on Sprint Binary > 4 WITHOUT eng_boot?
I always thought the whole point of being on U firmware was for root access though. But anyhow, once you get the U firmware flashed, which BL version is on the device? Is this an exploit that allows for older Binary to be flashed?
I'm intrigued by this method for other reasons. I would really REALLY love for a custom boot.img to be allowed but you can't. If this method is a way to block checking of BL, AP, etc hash checks, then the similar method should be possible for a custom recovery and custom kernel. I miss my kernel.
elesbb said:
But from what I read in the original post is that BEFORE using flashfire to flash the original boot.img, you are running the eng_boot.img. Is this correct? Btw, flashfire NEEDS root. So you ARE rooted at some point. Therefore, this is why you are being kicked from the network. Thus, disabling those packages will prevent that. But SABS and Adhell no longer work, at least I couldn't get them to. I even paid for the one and used it once. So I'm a bit annoyed with that. But yes, I am still on binary 4 for the BL. It was a requirement when purchasing my phone on Craigslist xD.
Click to expand...
Click to collapse
AdHell 3 still works on Nougat at least. You have to get the newer version because Samsung changed their SDK keys program. I'm not on Oreo, so I'm not sure if it will work. But if you are rooted, you have better options. If you need the new version of AdHell3, I'll post a link.
But, what you are after may not be feasible. This is what you want: 100% U firmware on Sprint Binary > 4 WITHOUT eng_boot?
Click to expand...
Click to collapse
Basically, when you finish. You'll have the U firmware on the phone, but the BL with still be 5/6. So some things like Knox, System Updates, etc..won't work because of the conflict and will say the phone has been compromised. Also, the phone doesn't bootloop because of those items you need to disable, because you did it before using flashfire.
It works fine after applying the changes after rooting, but it is after the flashfire flash and factory reset that doesn't. Modem you can flash, but the CSC files mostly get erased because parts of them are install to the system with the rom. When you check, the phone has no CSC setup available. Which is why it probably displays Korean carrier settings since that is the default with CSC files present.
I always thought the whole point of being on U firmware was for root access though. But anyhow, once you get the U firmware flashed, which BL version is on the device? Is this an exploit that allows for older Binary to be flashed? .
Click to expand...
Click to collapse
The original point of U firmware was to get rid of carrier bloatware and the ability to use most carriers easily with most addons (VoLTE) available.
I'm intrigued by this method for other reasons. I would really REALLY love for a custom boot.img to be allowed but you can't. If this method is a way to block checking of BL, AP, etc hash checks, then the similar method should be possible for a custom recovery and custom kernel. I miss my kernel.
Click to expand...
Click to collapse
So in conclusion, you have the U4 firmware running on a Sprint S7 with b5/6 installed without root. Since the phone runs fine with the U firmware, something is causing connection issues to Sprint. I assume he is in Africa (Zambia) and by using a GSM only sim card, it will work.
Unless you want to upgrade to b5/6 and try it, that's probably the only true way to test it. Plus, who wants to be on b4 anyway?
lvpre said:
AdHell 3 still works on Nougat at least. You have to get the newer version because Samsung changed their SDK keys program. I'm not on Oreo, so I'm not sure if it will work. But if you are rooted, you have better options. If you need the new version of AdHell3, I'll post a link.
Click to expand...
Click to collapse
Yeah I am currently rooted with the U firmware BL4. I want to upgrade to Oreo, hoping for performance improvements, better battery, etc. But I guess since the Oreo U firmware is still BL4, I can just downgrade if I can't get root back.
Basically, when you finish. You'll have the U firmware on the phone, but the BL with still be 5/6. So some things like Knox, System Updates, etc..won't work because of the conflict and will say the phone has been compromised. Also, the phone doesn't bootloop because of those items you need to disable, because you did it before using flashfire.
Click to expand...
Click to collapse
I never mentioned a bootloop? Is this about something else? The point I am trying to address is the loss of Sprint connectivity after flashing eng boot. This is because of the packages that need to be disabled.
It works fine after applying the changes after rooting, but it is after the flashfire flash and factory reset that doesn't. Modem you can flash, but the CSC files mostly get erased because parts of them are install to the system with the rom. When you check, the phone has no CSC setup available. Which is why it probably displays Korean carrier settings since that is the default with CSC files present.
Click to expand...
Click to collapse
So you flash everything, eng boot, and are currently rooted. You then flash the provided file via flash fire, factory reset, and now you no longer are able to connect to Sprint network? When you say "can't connect to Sprint network", are you referring to data or to Sprint network entirely? If you go under your "about phone" section, what does your IMEI and phone number display? Don't actually type it here, but it should be something comprehensible. It shouldn't say "unknown" or a bunch of zeros, etc. [/quote]
The original point of U firmware was to get rid of carrier bloatware and the ability to use most carriers easily with most addons (VoLTE) available.
Click to expand...
Click to collapse
True..
So in conclusion, you have the U4 firmware running on a Sprint S7 with b5/6 installed without root. Since the phone runs fine with the U firmware, something is causing connection issues to Sprint. I assume he is in Africa (Zambia) and by using a GSM only sim card, it will work.
Unless you want to upgrade to b5/6 and try it, that's probably the only true way to test it. Plus, who wants to be on b4 anyway?
Click to expand...
Click to collapse
I do. A lot of people want to be back to BL4. There is NO difference in the newer bootloaders EXCEPT a special "key" type of thing that prevents downgrading. That is the only thing different. This is why the U firmware is still on BL4 despite having an Oreo update. Sprint changes the BL version just so people like us have extra hurdles to overcome when we want something different. Its very stupid tbh.
But, I would like to help you guys out, however, I AM NOT upgrading to the BL5/6. Noway nohow.
It actually shows a crossed out circle for the signal strength in the status bar. I'm pretty sure I tried it by flashing just the system and system with boot, which removes the root. Even entering apn info had slight issues.
I was hoping someone with more knowledge and a b5\6 phone would give this a whirl. If you get bored, maybe it would be like you flashing the U firmware with b2.
My wife's phone is still b4, so at least one of us didn't get the Sprint screw.
lvpre said:
It actually shows a crossed out circle for the signal strength in the status bar. I'm pretty sure I tried it by flashing just the system and system with boot, which removes the root. Even entering apn info had slight issues.
I was hoping someone with more knowledge and a b5\6 phone would give this a whirl. If you get bored, maybe it would be like you flashing the U firmware with b2.
My wife's phone is still b4, so at least one of us didn't get the Sprint screw.
Click to expand...
Click to collapse
Hmm. That's weird. What does your about phone section say for IMEI and phone number? Everything good? I wonder if something is affecting the PRL. Try updating that via settings menu before you flash the firmware and factory reset. The CSC shouldn't really affect that part. I have changed mine multiple times to just eff around and see what/if anything changed. Its more for the phone to know what menu options are available and such. For instance, call recording shows up when its not a US branded carrier.
Sadly I will never flash the newer BL. But I will definitely keep trying via the thread and if you would like to discord or something similar I would be down. School starts in about 2 weeks so I'm basically free till then
sim boot loop
I have the same issue. I can install the g930u Nougat firmware on my BLv5 Sprint phone (you seem to need BLv6 for Oreo), however, the phone will not connect to the sprint network. I flashed the cache.img file and it does the same thing. It forces you to reboot to finish setup then errors out on the blue sim card screen in recovery. I removed the AutoPreconfig app through adb shell to bypass the forced reboot and tried to just select Sprint as the network under connection settings where you can search for available carriers. That too failed...it just sat there for a while then said that it couldn't connect and shows the emergency calls only as the network up top and low signal bars.
Aggiedude said:
I have the same issue. I can install the g930u Nougat firmware on my BLv5 Sprint phone (you seem to need BLv6 for Oreo), however, the phone will not connect to the sprint network. I flashed the cache.img file and it does the same thing. It forces you to reboot to finish setup then errors out on the blue sim card screen in recovery. I removed the AutoPreconfig app through adb shell to bypass the forced reboot and tried to just select Sprint as the network under connection settings where you can search for available carriers. That too failed...it just sat there for a while then said that it couldn't connect and shows the emergency calls only as the network up top and low signal bars.
Click to expand...
Click to collapse
Thanks for posting this!!! I'm glad that I wasn't the only having this issue. I tried it again using a different method and still got the SIM boot loop. This method probably works great if you have anything other than Sprint or Sprint MVNO, but something is conflicting like it does during a typical root of the G930P. Anyway, hopefully, someone else will be able to figure this out.