Hello all, I was asking if you can help me with an issue here.
While trying to root my Nord 2, I flashed the wrong boot.img version (A.10, while I was already update at the A.11), losing my WiFi and Bluetooth. So to recover them, I flashed the Full A.07 firmware and went back up to A.11 flashing the various OTAs. After flashing the A.07 firmware though, I've lost IMEI and Cellular functionality, and was never able to recover them.
I've done a backup of my nvram, nvdata, and nvcfg partitions before flashing, but restoring them didn't solve the issue.
I've use this guide for root: https://forum.xda-developers.com/t/root-tool-oneplus-nord-2-oxygen-11-3-dn2103_11_a-xx-eea.4332959/
And this guide to flash A.07 and OTAs: https://forum.xda-developers.com/t/oneplus-nord-2-oxygen-11-3-dn2103-eea-rom.4331695/
Does someone have any hints? Or should I send it back to Oneplus?
Raygen said:
Hello all, I was asking if you can help me with an issue here.
While trying to root my Nord 2, I flashed the wrong boot.img version (A.10, while I was already update at the A.11), losing my WiFi and Bluetooth. So to recover them, I flashed the Full A.07 firmware and went back up to A.11 flashing the various OTAs. After flashing the A.07 firmware though, I've lost IMEI and Cellular functionality, and was never able to recover them.
I've done a backup of my nvram, nvdata, and nvcfg partitions before flashing, but restoring them didn't solve the issue.
I've use this guide for root: https://forum.xda-developers.com/t/root-tool-oneplus-nord-2-oxygen-11-3-dn2103_11_a-xx-eea.4332959/
And this guide to flash A.07 and OTAs: https://forum.xda-developers.com/t/oneplus-nord-2-oxygen-11-3-dn2103-eea-rom.4331695/
Does someone have any hints? Or should I send it back to Oneplus?
Click to expand...
Click to collapse
You done the mess even I creted simple twrp and root method you choosed the patched boot.img way and This happened.
Try to restore your full backup of nandroid using twrp. Or fist install twrp and flash non patched boot images using twrp itself
pankspoo said:
You done the mess even I creted simple twrp and root method you choosed the patched boot.img way and This happened.
Try to restore your full backup of nandroid using twrp. Or fist install twrp and flash non patched boot images using twrp itself
Click to expand...
Click to collapse
Yeah I saw there was 2 different guides, I went with the newer one but it wasn't the right choice.
Already tried flashing a stock boot image, no change. Didn't do a Nandroid backup before hand, that's my bad.
Raygen said:
Yeah I saw there was 2 different guides, I went with the newer one but it wasn't the right choice.
Already tried flashing a stock boot image, no change. Didn't do a Nandroid backup before hand, that's my bad.
Click to expand...
Click to collapse
Try all boot images and test it
File folder on MEGA
mega.nz
Must work with anyone
sakarya1980 said:
Try all boot images and test it
File folder on MEGA
mega.nz
Must work with anyone
Click to expand...
Click to collapse
Those images are the first I've tried. I've then tried with the stock boot image linked in @pankspoo post, but with still no result. My guess is that flashing V.07 on top of V.11 rewrited some others partitions that should have not be touched
Well i am not happy to tell you, but if its true that partitions containing IMEI and WiFi connections got overwritten with nonsense information then the only thing that could save your phone is full nandroid backup which you do not have. And unfortunetly dont expect anyone else to provide it as that would mean that those 2 phones would have the same IMEI and MAC address.
I would suggest that you flash stock image, lock your bootloader and send it for RMA saying that you dont know what happened. You will have like 50/50 chance that they will just replace your motherboard without much of an investigation.
Raygen said:
Those images are the first I've tried. I've then tried with the stock boot image linked in @pankspoo post, but with still no result. My guess is that flashing V.07 on top of V.11 rewrited some others partitions that should have not be touched
Click to expand...
Click to collapse
If you have europe Version of nord2, flash Version v07, then update with otas to v09, v10, v11 with twrp
@Raygen did you get through with your imei repair? i have a similar issue.
BusterCZ said:
Well i am not happy to tell you, but if its true that partitions containing IMEI and WiFi connections got overwritten with nonsense information then the only thing that could save your phone is full nandroid backup which you do not have. And unfortunetly dont expect anyone else to provide it as that would mean that those 2 phones would have the same IMEI and MAC address.
I would suggest that you flash stock image, lock your bootloader and send it for RMA saying that you dont know what happened. You will have like 50/50 chance that they will just replace your motherboard without much of an investigation.
Click to expand...
Click to collapse
Yeah, I've already contacted OnePlus and I'm waiting for an RMA.
There's just a catch: I'm not able to re-lock the bootloader without getting the "boot image is corruptd" error. But I hope it's not an issue if I send it back all stock, with just the bootloader unlocked.
sakarya1980 said:
If you have europe Version of nord2, flash Version v07, then update with otas to v09, v10, v11 with twrp
Click to expand...
Click to collapse
Tried two times already, no change.
Keden said:
@Raygen did you get through with your imei repair? i have a similar issue.
Click to expand...
Click to collapse
Send it back to OnePlus sadly.
Raygen said:
Yeah, I've already contacted OnePlus and I'm waiting for an RMA.
There's just a catch: I'm not able to re-lock the bootloader without getting the "boot image is corruptd" error. But I hope it's not an issue if I send it back all stock, with just the bootloader unlocked.
Tried two times already, no change.
Send it back to OnePlus sadly.
Click to expand...
Click to collapse
Did any way you can flash stock. Firmware using sp flash tool of mediatek just like qualcoms MSM tool used for hardbricked devices
Raygen said:
Yeah, I've already contacted OnePlus and I'm waiting for an RMA.
There's just a catch: I'm not able to re-lock the bootloader without getting the "boot image is corruptd" error. But I hope it's not an issue if I send it back all stock, with just the bootloader unlocked.
Click to expand...
Click to collapse
Well my guess is that if they take a look at it and the bootloader will be unlocked they will send it back to you rejacted. Atleast that was my expirience once with my old Xiaomi phone. So probably try flashing original firmware using some kind of recovery utility such as Sp flash to help get rid of this message?
pankspoo said:
Did any way you can flash stock. Firmware using sp flash tool of mediatek just like qualcoms MSM tool used for hardbricked devices
Click to expand...
Click to collapse
BusterCZ said:
Well my guess is that if they take a look at it and the bootloader will be unlocked they will send it back to you rejacted. Atleast that was my expirience once with my old Xiaomi phone. So probably try flashing original firmware using some kind of recovery utility such as Sp flash to help get rid of this message?
Click to expand...
Click to collapse
I would like to use Sp flash but I don't know where I could find the files for the Nord 2 to use with it. Like the scatter file and the firmware in Raw format
Keden said:
@Raygen did you get through with your imei repair? i have a similar issue.
Click to expand...
Click to collapse
Might help ! Check,.
U need to get UMT dongle , Ultimate Multi tool software.
Related
hi,
i wanted to flash stock android (used an rom before) so i erase recovery system etc.. and when i want to flash the system img it says "
(bootloader) Device State : Locked
FAILED (remote: Can not flash any images while device state is locked!)
-.- what can i do ?
any solutions ?
thanks
Not much. Only thing you can do with a locked boot loader is flash OTA updates, and they don't have an OTA that will flash the full system. OTAs only update an existing system. You shouldn't have erased your system.
You need to return your N9 to HTC for a replacement.
Sent from my Nexus 9
enriquejones666 said:
Not much. Only thing you can do with a locked boot loader is flash OTA updates, and they don't have an OTA that will flash the full system. OTAs only update an existing system. You shouldn't have erased your system.
You need to return your N9 to HTC for a replacement.
Sent from my Nexus 9
Click to expand...
Click to collapse
hmm okey, so send it back to HTC (or amazon cause i buyed it there)
but it should be no problem cause its locked and therse no sign that it was/is rooted, right?
also i have buyed an insurance for 2 years so i think it should be okey... i hope so
So I'm in a similar pickle, with one huge difference: my bootloader is unlocked, and reflects such in the fastboot menu.
Long story short, I have no image of any kind on it at this point. All attempts with any interface to flash either 5.1.1 or 6 fail. When attempting to flash the system.img, I get the "too many links" error. I've not found a solution that works.
At this point, I have no recovery and no image. I can't successfully flash one either. Not sure what to do from here...
Sent from my LG-H810
disturbd1 said:
So I'm in a similar pickle, with one huge difference: my bootloader is unlocked, and reflects such in the fastboot menu.
Long story short, I have no image of any kind on it at this point. All attempts with any interface to flash either 5.1.1 or 6 fail. When attempting to flash the system.img, I get the "too many links" error. I've not found a solution that works.
At this point, I have no recovery and no image. I can't successfully flash one either. Not sure what to do from here...
Sent from my LG-H810
Click to expand...
Click to collapse
are you using the right fastboot commands? Eg. not something dumb like fastboot flash boot system.img. Also are you flashing your stuff in the correct order? Make sure to grab a good copy of whatever version of android you're trying to flash from here
tdct12 said:
are you using the right fastboot commands? Eg. not something dumb like fastboot flash boot system.img. Also are you flashing your stuff in the correct order? Make sure to grab a good copy of whatever version of android you're trying to flash from here
Click to expand...
Click to collapse
Thanks, I ended up getting it in a workable state last night. Ran a temporary recovery via Wug's toolkit, got TWRP installed, and went from there. I now have Marshmallow on it via AOSP, but I think the bootloader might still need updating.
Sent from my LG-H810
disturbd1 said:
Thanks, I ended up getting it in a workable state last night. Ran a temporary recovery via Wug's toolkit, got TWRP installed, and went from there. I now have Marshmallow on it via AOSP, but I think the bootloader might still need updating.
Sent from my LG-H810
Click to expand...
Click to collapse
Just download the newest build and fastboot flash bootloader bootloader.img :good:
oediv said:
hmm okey, so send it back to HTC (or amazon cause i buyed it there)
but it should be no problem cause its locked and therse no sign that it was/is rooted, right?
also i have buyed an insurance for 2 years so i think it should be okey... i hope so
Click to expand...
Click to collapse
Definitely send it back to Amazon. They are very good about taking returns. You can just say you tried to update the OS, and now the device doesn't boot (i.e. product is defective).
Sent from my Nexus 9
enriquejones666 said:
Definitely send it back to Amazon. They are very good about taking returns. You can just say you tried to update the OS, and now the device doesn't boot (i.e. product is defective).
Sent from my Nexus 9
Click to expand...
Click to collapse
2 people 1 idea
It's on the way, I said " want to update the OS and Made a factory reset before"
Have you tried flashing the factory images with fastboot? Pretty straight forward...
For future reference, how did you erase things with the bootloader locked?
EDIT: The problem is fixed, the problem was my dead SD card, as soon as I took it out and boot into TWRP the recovery has been working well. Thank you all for your help anyways.
What's going on guys, today I'm in need of some aid. Couple days ago I was trying to swap ROMs from PsyRom to FlyMeOS and when I tried to access TWRP recovery, it would get stuck on the TeamWin logo. I softbricked my phone by restoring the stock recovery and kernel (lol) and flashed the latest Fastboot ROM. Now I'm fine with MIUI8, and I flashed TRWP again (with Fastboot flash) but everytime I try to access TRWP it gives me that stuck logo or a black screen. I don't know what to do because I already tried with a rooted Dev ROM and flashify and even the TWRP Manager but I can't get anywhere. Do you know what I can do?
I've seen several TWRP versions for RN2.
Did you try with the official one?
https://dl.twrp.me/hermes/
gnazio said:
I've seen several TWRP versions for RN2.
Did you try with the official one?
https://dl.twrp.me/hermes/
Click to expand...
Click to collapse
Yes I did, and with the 2.8.7, and the other 3.0.x
Always the same result. Did Xiaomi lock the Redmi Note 2 bootloader?
kiko9895 said:
Yes I did, and with the 2.8.7, and the other 3.0.x
Always the same result. Did Xiaomi lock the Redmi Note 2 bootloader?
Click to expand...
Click to collapse
AFAIK the bootloader is not locked.
Otherwise I think that you can't even install TWRP.
I any case, I would try with an older fastboot ROM and with the official TWRP.
Have you tried this one: http://forum.xda-developers.com/redmi-note-2/general/twrp2-8-7-0-light-materialized-theme-t3308492
DarthJabba9 said:
Have you tried this one: http://forum.xda-developers.com/redmi-note-2/general/twrp2-8-7-0-light-materialized-theme-t3308492
Click to expand...
Click to collapse
Yes, it's the last one I tried, I used the one on the first link, with MIUI8 compatibility.
gnazio said:
AFAIK the bootloader is not locked.
Otherwise I think that you can't even install TWRP.
I any case, I would try with an older fastboot ROM and with the official TWRP.
Click to expand...
Click to collapse
I'm sorry but do you know where I can find an older one?
kiko9895 said:
Yes, it's the last one I tried, I used the one on the first link, with MIUI8 compatibility.
Click to expand...
Click to collapse
I am using this one: https://drive.google.com/file/d/0BwdRTuyj12_yVlJoMzJoeUJKLVE/view
I have no problem with it (MIUI8). To be honest, I don't think any of them should cause the problem that you are having. Trying to solve the problem without identifying the cause will probably prove unfruitful. How did you install the first one that you had problems with? Did it ever work at all? If so, when did it start malfunctioning?
DarthJabba9 said:
I am using this one: https://drive.google.com/file/d/0BwdRTuyj12_yVlJoMzJoeUJKLVE/view
I have no problem with it (MIUI8). To be honest, I don't think any of them should cause the problem that you are having. Trying to solve the problem without identifying the cause will probably prove unfruitful. How did you install the first one that you had problems with? Did it ever work at all? If so, when did it start malfunctioning?
Click to expand...
Click to collapse
Yes it used to work, I already tried a lot of ROMs, I had the one compatible with Android 6.0 which I flashed with TWRP itself (It worked since I flashed CM13 with it).
I don't really know when it started malfunctioning because the last time I made a backup was at least one month ago when I swapped to PsyRom (it was functioning well). But two days ago when I tried to access it to change to FlyMe it wouldn't work. Anyways I'm flashing a MIUI7 fastboot ROM to see if it works.
I'm sorry if I can't explain myself very well but I'm doing the best I can lol. Thank you for your help too.
Perhaps something messed up your file system or partitions. If all attempts don't work, then you might want to use the SP Flash Tool to flash a compatible ROM and working TWRP.
DarthJabba9 said:
Perhaps something messed up your file system or partitions. If all attempts don't work, then you might want to use the SP Flash Tool to flash a compatible ROM and working TWRP.
Click to expand...
Click to collapse
I just flashed MIUI 7 with SP Flash Tool. Gonna try and flash TWRP through fastboot and with update.zip method, see if anything works.
kiko9895 said:
I'm sorry but do you know where I can find an older one?
Click to expand...
Click to collapse
I should have a MIUI7 on my mega account, it should be the last 7 stable, saved just in case something was wrong with 8.
I can send you the link if you are still searching.
OK, I just noticed that you have solved yet.
Good, I hope that this time everything will be fine.
gnazio said:
I should have a MIUI7 on my mega account, it should be the last 7 stable, saved just in case something was wrong with 8.
I can send you the link if you are still searching.
OK, I just noticed that you have solved yet.
Good, I hope that this time everything will be fine.
Click to expand...
Click to collapse
Thank you very much for your kindness, I'm still trying tho ahah using WinDroid Toolkit now.
gnazio said:
I should have a MIUI7 on my mega account, it should be the last 7 stable, saved just in case something was wrong with 8.
I can send you the link if you are still searching.
OK, I just noticed that you have solved yet.
Good, I hope that this time everything will be fine.
Click to expand...
Click to collapse
Hello, after one month the issue is still not fixed, the recovery still hangs. Perhaps you could send me that fastboot rom you talked about please? Thank you.
I'm going to send you the link.
In the meanwhile...reading the thread again...what is "update.zip method"?
Are you try to install TWRP from Mi recovery?
This is not going to work anymore.
You should better stay with the last ROM and flash TWRP from fastboot.
This is the recovery image: https://dl.twrp.me/hermes/twrp-3.0.2-0-hermes.img
This is the guide: https://twrp.me/devices/xiaomiredminote2.html
Just start your RN2 into fastboot (vol down+power on), run fastboot flash recovery twrp.img and finally keep pressed vol up and send fastboot reboot and wait with the key pressed until it enter TWRP.
BTW:
in the official forum there should be a thread with link to all officially released ROMs for RN2.
kiko9895 said:
Hello, after one month the issue is still not fixed, the recovery still hangs. Perhaps you could send me that fastboot rom you talked about please? Thank you.
Click to expand...
Click to collapse
Here you should find every MIUI Global ROM released for RN2:
http://en.miui.com/forum.php?mod=viewthread&tid=394496
I just realized that the one I have is China version, used just to clean the phone from reseller ROM.
gnazio said:
I'm going to send you the link.
In the meanwhile...reading the thread again...what is "update.zip method"?
Are you try to install TWRP from Mi recovery?
This is not going to work anymore.
You should better stay with the last ROM and flash TWRP from fastboot.
This is the recovery image: https://dl.twrp.me/hermes/twrp-3.0.2-0-hermes.img
This is the guide: https://twrp.me/devices/xiaomiredminote2.html
Just start your RN2 into fastboot (vol down+power on), run fastboot flash recovery twrp.img and finally keep pressed vol up and send fastboot reboot and wait with the key pressed until it enter TWRP.
BTW:
in the official forum there should be a thread with link to all officially released ROMs for RN2.
Click to expand...
Click to collapse
The problem is I already tried the fastboot method as well, and the problem is always the same, stuck TWRP logo. Even if it was a partition problem, flashing the fastboot ROM should fix it, but it didn't. I tried the SP Flash Tools method too, and the flashing methods are successful, they all Flash TWRP, but when I try to access it it's stuck. I don't know why this is happening, it used to work.
@kiko9895 Sounds like you have screwed your partitions. You will need to load a full ROM using SP Tools to correct it as this is the only way to set the partitions back at their correct memory locations. Fastboot and Recovery rewrite the partitions by name not memory location so any fault in that will never be fixed. If you have flashed an Android 6.0 based ROM or something intended for another model phone, this will definitely be the case. Anyone flashing custom ROMs should first gather the skills and tools to recover from disasters - luckily, MTK based phones are virtually unbrickable!
As far as the "official" TWRP goes, it is not official and not a good version. It is just someone who has used the TWRP build server to knock out a random version. How does that make it "official"?
jajk said:
@kiko9895 Sounds like you have screwed your partitions. You will need to load a full ROM using SP Tools to correct it as this is the only way to set the partitions back at their correct memory locations. Fastboot and Recovery rewrite the partitions by name not memory location so any fault in that will never be fixed. If you have flashed an Android 6.0 based ROM or something intended for another model phone, this will definitely be the case. Anyone flashing custom ROMs should first gather the skills and tools to recover from disasters - luckily, MTK based phones are virtually unbrickable!
As far as the "official" TWRP goes, it is not official and not a good version. It is just someone who has used the TWRP build server to knock out a random version. How does that make it "official"?
Click to expand...
Click to collapse
Ahah I have the skills and the tools, I've been flashing ROMs for more than two years. This never happened before. If you read what I said before on this thread, you'll see that I already flashed a new ROM through SP Flash Tools. And yes I flashed a 6.0 rom before so that must be the problem, but since I already flashed a fastboot rom through SP Flash Tools I can't see where the problem is. The partitions should be fixed by now but that isn't the case.
@kiko9895 Sorry if it sounded like I was coming down hard on you. You should only need to flash a matching preloader, uboot, logo plus TWRP recovery using SP Flash Tools with the correct scatter file to get back into booting to TWRP. Any other problems can be sorted from there.
I will attach a known good scatter file because I know there are several floating around that will reverse one or two partitions on you (such as the RN3 version)
I'll try and keep this short and to the point. If you unlocked your bootloader and flashed TWRP and SuperSU, theirs a Good chance your phone will not return to stock and take OTA updates. Many of us have tried but for some reason the updates just fail.
Well we are lucky and someone captured and posted the 3 known updates and I'm going to show you how to flash them
New ~ All in One ~ update Instructions in Post 2
We now have a new way to do this, So the information below is just for information sake So bare with me while I get the Guide updated...
Other Files you may need
H1611.TWRP.New.img <<- This is the New Twrp by yuweng I Highly recommend everyone use this Version
minimal_adb_fastboot_v1.4.1_setup.exe
Huawei_Android_phone_drivers(1).rar
I have been working on this for some time and I now have an ALL in One Flash solution
This will allow you to flash a Single Rom to Update or Downgrade your firmware and Rom
As with any firmware update or downgrade I'm not responsible to what happens to your phone you do this at your own risk
(rest assured I have tested all these files and my phone is fine)
The Flash instructions are the same as any rom flash on this phone
Step one is to Boot to the bootloader and boot H1611.TWRP.New.img
fastboot boot H1611.TWRP.New.img
Swipe to allow modifications to System
then choose Mount and check system and cust
Select Storage Micro SDcard
Next is install and choose your Bxxx_Full_Update.zip
Swipe to flash
Reboot
That's really all their is too it, Just choose the File below that you want to update or downgrade too
Note: The phone always loads the AT&T logo and reboots the first time and then loads normally
First boot will take you to the setup screen if you formatted data
Another thing i noticed while test flashing these files is that the Data partition becomes Encrypted after the flash
This means before you can restore a data backup or flash a Rom like CleanRom (it includes data) you'll need to Format Data to UN-encrypt it
Also some roms may need to have SuperSU flashed after the Rom or the phone may not boot the first time after the upgrade.
AS Always make a complete backup of your phone before you start any flashing
Downloads
~New~ B180_Full_Update.zip
Note about B180 - If you have no wifi or the phone won't boot simply extract the boot.img from the rom and flash it with TWRP (Install Image) or fastboot (fastboot flash boot boot.img) also the AT&T Logo is missing for now but everything else works
Thanks To @madvane20 Download >> B170 Stock Full Update with Firmware
B160_Full_Update.v2.zip
B150_Full_Update.zip
I had to make B140 into 2 flashes but it works the same just copy both files to your phone and Flash A then B
B140_Full_Update.A.zip
B140_Full_Update.B.zip
B130_Full_Update.zip
Huge thanks to @madvane20 for helping with the partition layouts and testing and to @worstenbrood for the Huawei Update Extractor tool
Where do I start if I have B140 rooted on my XT? Maybe some numbers or section titles would help answer that. Thanks .
divineBliss said:
Where do I start if I have B140 rooted on my XT? Maybe some numbers or section titles would help answer that. Thanks .
Click to expand...
Click to collapse
You start at the 2nd half of the updated guide B140 to B150
the process is the same no matter what version your on
So I should start with B130 stock files even though I'm in B140 rooted right now?
clsA said:
You still start at the top and substitute the B150 files where their needed
the process is the same no matter what version your on
Click to expand...
Click to collapse
divineBliss said:
So I should start with B130 stock files even though I'm in B140 rooted right now?
Click to expand...
Click to collapse
... no you would start at returning your phone to Stock B140 and continue from their
flashing the B150 firmware then the B150 stock system and /cust
We have the B150 files and the guide is updated
If I can get back to B140 stock and take the B150 OTA, which files do you need?
clsA said:
The guide is not complete ... no you would start at returning your phone to Stock B140 and continue from their
flashing the B150 firmware then the B150 stock system and /cust
We don't have the B150 files yet so it's hard to complete the guide
Click to expand...
Click to collapse
divineBliss said:
If I can get back to B140 stock and take the B150 OTA, which files do you need?
Click to expand...
Click to collapse
is that a trick question ? if you could get back to stock and take the OTA this post wouldn't be necessary now would it ?
The whole point of the thread is that no one who rooted has been able to return to stock and take an OTA
Why bother updating? Isn't someone working in Lineage for this phone?
guest_2011 said:
Why bother updating? Isn't someone working in Lineage for this phone?
Click to expand...
Click to collapse
no one has posted any threads about it
you should still try and be on the latest security patch while you phone is stock
@RN_ReFlux Thank You ! for getting the B150 backup and /cust.img
guest_2011 said:
Why bother updating? Isn't someone working in Lineage for this phone?
Click to expand...
Click to collapse
Yes, someone is working on it but it is best to have your ROM up to date. You may not see a need for it but a lot of others see a need.
clsA said:
@RN_ReFlux any luck getting the B150 backup and /cust.img ?
Click to expand...
Click to collapse
Yes, I have them, am working on zipping some of the larger files, then will upload to drive or dropbox, since I don't have developer access to afh yet.
Only think I forgot to do was get the post-root backup in TWRP. If you need that, I've already asked my cousin to perform the backup, I'll ask her to zip and upload them to me.
RN_ReFlux said:
Yes, I have them, am working on zipping some of the larger files, then will upload to drive or dropbox, since I don't have developer access to afh yet.
Only think I forgot to do was get the post-root backup in TWRP. If you need that, I've already asked my cousin to perform the backup, I'll ask her to zip and upload them to me.
Click to expand...
Click to collapse
Thanks ... I'll post the files to my AFH account if you can share them through google or dropbox ..etc
If you request developer access, it doesn't take that long to get it ........ a few hour maybe if I recall correctly .
RN_ReFlux said:
Yes, I have them, am working on zipping some of the larger files, then will upload to drive or dropbox, since I don't have developer access to afh yet.
Only think I forgot to do was get the post-root backup in TWRP. If you need that, I've already asked my cousin to perform the backup, I'll ask her to zip and upload them to me.
Click to expand...
Click to collapse
divineBliss said:
If you request developer access, it doesn't take that long to get it ........ a few hour maybe if I recall correctly .
Click to expand...
Click to collapse
Requested it about 12 hours ago
Uploading to drive now.
Sent from my SM-T530 using Tapatalk
divineBliss said:
...
Click to expand...
Click to collapse
All the files are uploaded for your B140 to B150 update...
I'll be updating the guide soon.
The steps in a nutshell are
flash your stock B140 system/boot/recovery and stock b140 /cust
force flash the dload/update.app for b150 with the dialer code
boot TWRP restore stock B150 system and dd the B150 /cust
Flash SuperSU and Factory Reset (< optional)
reboot system and it boots to a clean B150
Click to expand...
Click to collapse
Guide is updated !
Has anyone been able to follow the OP to get up to B150 from either B140 or B130? Or even B130 to B140? Thanks!
clsA said:
All the files are uploaded for your B140 to B150 update...
I'll be updating the guide soon.
The steps in a nutshell are
Guide is updated !
Click to expand...
Click to collapse
divineBliss said:
Has anyone been able to follow the OP to get up to B150 from either B140 or B130? Or even B130 to B140? Thanks!
Click to expand...
Click to collapse
Yeah me
Sent from my Nexus 6P using Tapatalk
Be careful upgrading from B130 to B140. Went from stock non-rooted B130 to B140 using the SD card update method and hidden menu. While it went through the update process without reporting an error but after auto reboot it still showed the same version but lost WIFI functionality, mac address showed mostly 00s and can't restore full backup from TWRP without errors on /data, etc.
Anyone know if there are .img equivalent of 2017-01-26-H1611.B130.stock.complete to attempt restore from either fastboot flash or dd?
Hi everyone,
I've recently messed up terribly on the Canadian model of this phone. The model # is KII-L05 and the problem is that I'm stuck on the logo screen when booting.
I was unable to flash a custom ROM properly and have no backups. I have TWRP 3.1.1-0 installed and have tried flashing cm12.1, cm-13.0, lineage-13.0 and lineage-14.1 with the proper gapps to no success. I also tried eRecovery (with a lot of trouble getting to it using the Vol+/- because it loads TWRP 99% of the time) but it won't detect the dload/UPDATE.APP that I acquired from the Canadian Huawei support site nor will it update via wifi.
I've run out of ideas so I'd appreciate some assistance in finding a solution either getting back to stock ROM(firmware?) or a custom ROM that supports this model.
If there's already an answer posted, please pass along the link as I've come up with nothing searching and following most of what's been said before.
Thanks,
You just have an option to restore the backup if someone can share it.
shashank1320 said:
You just have an option to restore the backup if someone can share it.
Click to expand...
Click to collapse
I was hoping it wouldn't have to come to that...
For clarity, would that be using TWRP to restore the backup or using the eRecovery/UPDATE.APP method?
I'll try my luck in the file repository to see if anyone has it.
Dominic987 said:
I was hoping it wouldn't have to come to that...
For clarity, would that be using TWRP to restore the backup or using the eRecovery/UPDATE.APP method?
I'll try my luck in the file repository to see if anyone has it.
Click to expand...
Click to collapse
you should try both.
TWRP backup and dload method. any of them could work
Dominic987 said:
I was hoping it wouldn't have to come to that...
For clarity, would that be using TWRP to restore the backup or using the eRecovery/UPDATE.APP method?
I'll try my luck in the file repository to see if anyone has it.
Click to expand...
Click to collapse
Extract your update.app using a program like 7zip -- it should contain a boot.img file. Use the ADB method to manually flash the file.
While your at it, if there is a system.img file -- flash that as well.
bb709394 said:
Extract your update.app using a program like 7zip -- it should contain a boot.img file. Use the ADB method to manually flash the file.
While your at it, if there is a system.img file -- flash that as well.
Click to expand...
Click to collapse
It may not work and dload will be best option here.
Fastboot may not allow him anymore to flash anything
bb709394 said:
Extract your update.app using a program like 7zip -- it should contain a boot.img file. Use the ADB method to manually flash the file.
While your at it, if there is a system.img file -- flash that as well.
Click to expand...
Click to collapse
shashank1320 said:
It may not work and dload will be best option here.
Fastboot may not allow him anymore to flash anything
Click to expand...
Click to collapse
Your suggestions are noted.
I'll try my luck at waiting a while longer for someone with a backup until I go flashing more things.
Did you try flashing stock recovery then flashing via dload?
hassanjavaid8181 said:
Did you try flashing stock recovery then flashing via dload?
Click to expand...
Click to collapse
I mentioned in my original post that I have no backups. Unfortunately, that includes me not having stock recovery to start from scratch.
My current eRecovery doesn't recognize anything I put into dload nor does it update via wifi.
I'm currently outreaching to Huawei Canada (been more than a few days without a response) as well as friends/coworkers that may have the phone that can help with no success.
Dominic987 said:
I mentioned in my original post that I have no backups. Unfortunately, that includes me not having stock recovery to start from scratch.
My current eRecovery doesn't recognize anything I put into dload nor does it update via wifi.
I'm currently outreaching to Huawei Canada (been more than a few days without a response) as well as friends/coworkers that may have the phone that can help with no success.
Click to expand...
Click to collapse
do you have orignal firmware file for your phone?if not download it from huawei website acoording to you model number
hassanjavaid8181 said:
do you have orignal firmware file for your phone?if not download it from huawei website acoording to you model number
Click to expand...
Click to collapse
Dominic987 said:
... it won't detect the dload/UPDATE.APP that I acquired from the Canadian Huawei support site nor will it update via wifi. ...
Click to expand...
Click to collapse
No backups, that includes anywhere internal or external of the phone in question. Already tried the Huawei site and they have Marshmallow - I suspect I need anything older that's on Lollipop.
Dominic987 said:
No backups, that includes anywhere internal or external of the phone in question. Already tried the Huawei site and they have Marshmallow - I suspect I need anything older that's on Lollipop.
Click to expand...
Click to collapse
Unfortunately there are no official firmware yet for this mate. I tried looking for you but couldn't get any. Its just OTA and not full firmware that could help you with dload.
Dominic987 said:
No backups, that includes anywhere internal or external of the phone in question. Already tried the Huawei site and they have Marshmallow - I suspect I need anything older that's on Lollipop.
Click to expand...
Click to collapse
May be last option is to take it to Huawei service center they will fix it for you.
After unlocking the bootloader flashed magisk and data decrypt imei and baseband are lost can I restore it?before going to service center:crying:?
Download a global Stock ROM for your device and just run the flash all.bat file and let it run may take awhile and phone will be fresh again
HELP !!! I'm getting the same issue but don't care if i brick the phone.
No matter how many times i flash use different roms i still lose my IMEI/Baseband
I have an external SD card but it looks complicated to backup the EFS file to the SD card and then restore it to the phone but is that my only option ?
Doubtpablo said:
Download a global Stock ROM for your device and just run the flash all.bat file and let it run may take awhile and phone will be fresh again
HELP !!! I'm getting the same issue but don't care if i brick the phone.
No matter how many times i flash use different roms i still lose my IMEI/Baseband
I have an external SD card but it looks complicated to backup the EFS file to the SD card and then restore it to the phone but is that my only option ?
Click to expand...
Click to collapse
Don't disable forceencrypt, that's your problem.
Doubtpablo said:
Download a global Stock ROM for your device and just run the flash all.bat file and let it run may take awhile and phone will be fresh again
Click to expand...
Click to collapse
Already flash stock ROM, but my IMEI still null.
I flashed 10.2.8.0.
Please anyone, I'm stuck with my phone without my IMEI and Baseband
whothehellami said:
Already flash stock ROM, but my IMEI still null.
I flashed 10.2.8.0.
Please anyone, I'm stuck with my phone without my IMEI and Baseband
Click to expand...
Click to collapse
Did you flash a recovery rom or a fastboot rom? You should find flashing the fastboot rom restores everything correctly.
Robbo.5000 said:
Did you flash a recovery rom or a fastboot rom? You should find flashing the fastboot rom restores everything correctly.
Click to expand...
Click to collapse
I tried restoring the phone using a fastboot rom, but the baseband and IMEI errors still appear. Does anyone know about another solution or tool for this? I know both of my IMEI numbers, by the way.
Spikyman said:
I tried restoring the phone using a fastboot rom, but the baseband and IMEI errors still appear. Does anyone know about another solution or tool for this? I know both of my IMEI numbers, by the way.
Click to expand...
Click to collapse
Every time I got this problem I found that flashing a fastboot ROM fixed it. I never managed to find any other solution that actually worked. Googling the problem I did find some solutions, but I didn't try them all. I just gave up and kept stock ROM with Magisk, then debloated it as much as I could. All I can suggest is seeing what Google throws up and seeing if any solution works for you.
anyone found a fix yet?
I have the mistake of rooting my device and disabling the encrypt, Now I have unknown baseband and my imei is blank. What do i do now?
Anuvind98 said:
After unlocking the bootloader flashed magisk and data decrypt imei and baseband are lost can I restore it?before going to service center:crying:?
Click to expand...
Click to collapse
It happens to me only when i flash decrypt,if i try to flash another decrypt it doesn't work and data remains crypted.
It's not a big problem bit i would like to have a solution of this problem
still have this problem. any fix?
try this youtube