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?
Related
TL;DWR: I want to go back to absolute zero and revert my phone to factory. I'm new to android and just followed a youtube video guide to root and unlock boot loader and now don't know how to go back.
Hey guys, I am completely new to android and have been with iPhone for about 7 years so please forgive me for my questions as they are elementary in comparison with the topics that are typically discussed on here.
I decided to switch it up and try an M8 cause the build quality and screen really excited me so I sold my iPhone and made the switch. I was in absolute love for about a week while on stock. Just learning android and all it's small quirks was fun for me.
but now, I have the phone up for sale, I'm amazed at how convoluted it is just to return to stock after rooting and roming. I spent 6 hours last night with a phone that wouldn't boot and just hang at the opening htc one opening boot animation.
I installed TWRP, unlocked the boot loader and used Hassoon2000's all in one toolkit to root as well. I used this video posted on the toolkit thread on here to help guide me.: https://www.youtube.com/watch?v=Krw6H4gQ6g0&feature=youtu.be
I followed the video to a tee with some stops on my side cause what he said in the video didn't always happen on my end, so I would unplug my phone and plug it back in and continue where I left off until the whole process worked. It's at the very end when he used twrp to reboot back into his "normal phone" that my phone just hung on the HTC boot animation.
I have all neccasary drivers and software installed to run this the toolkit and still received the "error: no device found" from time to time when using the kit. so you can imagine all the hair I pulled out coming from jailbreaking an iPhone with one click to trying just to root my device to disable ads and not can't even use my phone.
after some digging to find what I thought what supposedly a stock rom/img/Whateverthenameis for my phone, I breathed a sigh of relief and flashed it using tarp adb side load option and it finally booted up. I now however don't have working Wi-Fi and some apps that came preinstalled on my phone are missing. I don't like and just feel like it's a buggy mess.
long story short, I just want to go back to absolute zero. all the way stock; I don't even care about keeping any root or unlock. It would be nice so I can adblock but I don't care about it if it will stop me from going back to zero.
Here are all the tools I used to ruin my android experience aka the tools I mentioned above:
Toolkit (thread): http://forum.xda-developers.com/showthread.php?t=2699065
rom/img/whateveritscalled that i used to get back into a buggy phone: http://www.androidfiles.org/?developer=M8&folder=StockRoms
video guide I used: https://www.youtube.com/watch?v=Krw6H4gQ6g0&feature=youtu.be
I ran all this on a Windows 7 64-bit desktop machine.
Did you flash the Shipped RUU?
orangekid said:
Did you flash the Shipped RUU?
Click to expand...
Click to collapse
I barely understood how to flash the rom I found to get my phone back on but how do I flash an ruu and where do i get it?
orangekid said:
Did you flash the Shipped RUU?
Click to expand...
Click to collapse
I would also love to know how to do this, I desperately need help
I think there was a shipped RUU for the M8 that could be used to go full stock, I'll see if I can find it.
RUU = Rom Update Utility, which was named that back in the old WinMo days. This would just be a file that you either flash thru SD via fastboot or thru your computer.
orangekid said:
I think there was a shipped RUU for the M8 that could be used to go full stock, I'll see if I can find it.
RUU = Rom Update Utility, which was named that back in the old WinMo days. This would just be a file that you either flash thru SD via fastboot or thru your computer.
Click to expand...
Click to collapse
If you could find that it would be most appreciated
I just looked and couldn't find one. Would this be the only way to revert to stock from either a bad flash, boot loop or just plain want to be stock again. I want to root but I'm just not confident enough to use the toolkit without any handups. At least if I knew how to get back to stock I wouldnt worry as much.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Word around was that there has been no RUU released for our device yet. There is a stock rooted TWRP recovery image on the Android Development forum but that's probably the closest you will get. I'm not sure if a straight up factory reset would do it or not, but you would need to flash the stock recovery as well. Overall a pretty drawn out process, especially if you are unfamiliar with adb and fastboot. You might have to wait for a RUU
Sent from my HTC One_M8
TheEmpyre said:
Word around was that there has been no RUU released for our device yet. There is a stock rooted TWRP recovery image on the Android Development forum but that's probably the closest you will get. I'm not sure if a straight up factory reset would do it or not, but you would need to flash the stock recovery as well. Overall a pretty drawn out process, especially if you are unfamiliar with adb and fastboot. You might have to wait for a RUU
Sent from my HTC One_M8
Click to expand...
Click to collapse
What would happen if I clicked att software update in settings? would it do something or no? Would it crash the whole phone?
TheEmpyre said:
Word around was that there has been no RUU released for our device yet. There is a stock rooted TWRP recovery image on the Android Development forum but that's probably the closest you will get. I'm not sure if a straight up factory reset would do it or not, but you would need to flash the stock recovery as well. Overall a pretty drawn out process, especially if you are unfamiliar with adb and fastboot. You might have to wait for a RUU
Sent from my HTC One_M8
Click to expand...
Click to collapse
I thought I saw a leaked RUU floating around that did the job..
RACEnSK8 said:
What would happen if I clicked att software update in settings? would it do something or no? Would it crash the whole phone?
Click to expand...
Click to collapse
It probably would not find one, but if it did nothing good would happen, it won't successfully take an OTA with a custom ROM, recovery, etc..
Non-rooted nand backup,which can be used to go back to stock
http://forum.xda-developers.com/showpost.php?p=51953376&postcount=352
Wonders_Never_Cease said:
Non-rooted nand backup,which can be used to go back to stock
http://forum.xda-developers.com/showpost.php?p=51953376&postcount=352
Click to expand...
Click to collapse
I think I need to find someone to help me, because I never had to deal with rooted devices before. So i wouldn't even know what to do with the files you posted
RACEnSK8 said:
I think I need to find someone to help me, because I never had to deal with rooted devices before. So i wouldn't even know what to do with the files you posted
Click to expand...
Click to collapse
It's pretty simple actually.
If you are using TWRP recovery, just place this in that folder on your SD card, boot into recovery, and hit "restore"
it will restore a stock ROM on your device.
Use the recovery version he mentions though.
orangekid said:
It's pretty simple actually.
If you are using TWRP recovery, just place this in that folder on your SD card, boot into recovery, and hit "restore"
it will restore a stock ROM on your device.
Use the recovery version he mentions though.
Click to expand...
Click to collapse
How do I figure out what recovery i have
RACEnSK8 said:
How do I figure out what recovery i have
Click to expand...
Click to collapse
reboot the phone into recovery (your power menu might have the option) and it will give you the version.
You can also access it from fastboot, or adb (typy adb reboot recovery)
RACEnSK8 said:
I think I need to find someone to help me, because I never had to deal with rooted devices before. So i wouldn't even know what to do with the files you posted
Click to expand...
Click to collapse
Yea, android phones are a complete different world then that of iPhones. I was in your shoes a yr after the ip4 release. I didn't jump right in...I didn't flash or root my 1st phone for months. To be fair, not all android phones have difficult root/restore methods...most I've used were 1 click, same goes for jb programs. The only thing I can think of that iPhone had a slight edge was if you bricked from a bad app or jb...DFU and restore thru iTunes but then you worry about restoring to the new firmware...waiting for the next exploit and praying its not tethered. If iPhone is your thing...great but don't bounce from android after your 1st set back...it happens to all of us.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
orangekid said:
reboot the phone into recovery (your power menu might have the option) and it will give you the version.
You can also access it from fastboot, or adb (typy adb reboot recovery)
Click to expand...
Click to collapse
I went into recovery and it says PhilZ Touch 6.25.5
Clockworkmod v6.0.4.7
nash2000 said:
Yea, android phones are a complete different world then that of iPhones. I was in your shoes a yr after the ip4 release. I didn't jump right in...I didn't flash or root my 1st phone for months. To be fair, not all android phones have difficult root/restore methods...most I've used were 1 click, same goes for jb programs. The only thing I can think of that iPhone had a slight edge was if you bricked from a bad app or jb...DFU and restore thru iTunes but then you worry about restoring to the new firmware...waiting for the next exploit and praying its not tethered. If iPhone is your thing...great but don't bounce from android after your 1st set back...it happens to all of us.
Sent from my HTC One_M8 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Yeah, luckily I went from WinMo to iOS, so I went from "if you flash one wrong file you're bricked" to "I cannot brick this device if I try"
coming back to Android was like the WinMo days.
Depends what you have too, my daily is a Nexus 5, pretty easy to do anything on it. Samsung are really easy too, you just Odin a factory tar no matter where you are for the most part.
But HTC is the difficult one, all these tokens and issues and hboot versions and patches etc...
You get used to it though, and then it doesn't seem so daunting...
In this case, these are things OP needs to know if he is going to mess with any Android phones, basic things like recovery and basic ADB / fastboot commands etc...
RACEnSK8 said:
I went into recovery and it says PhilZ Touch 6.25.5
Clockworkmod v6.0.4.7
Click to expand...
Click to collapse
Ok,
You need to flash TWRP:
http://forum.xda-developers.com/showthread.php?t=2695709
orangekid said:
Ok,
You need to flash TWRP:
http://forum.xda-developers.com/showthread.php?t=2695709
Click to expand...
Click to collapse
So how do I do that?
Sorry for being such a noob, but I just want my wifi to work lol
This evening i've made a factory reset of my nexus 9 and now i can't get past the first update because when it reboots it gives me the "error" that was giving when trying to update using the OTA. When i reboot it, it still tells me to update the device.
I have an unlocked bootloader so i think i should be able to flash the updated official rom from the bootloader but i don't know how and all the guides i've found told me to "select" things that i couldn't find.
I am stuck at the first update so i don't have the usb dabugging enabled but i still can load things using the usb.
Should i send it back? (The device was rooted but i think the factory reset should have removed it)
Please help me i'm desperate! (and sorry for my bad english)
Aleschio said:
This evening i've made a factory reset of my nexus 9 and now i can't get past the first update because when it reboots it gives me the "error" that was giving when trying to update using the OTA. When i reboot it, it still tells me to update the device.
I have an unlocked bootloader so i think i should be able to flash the updated official rom from the bootloader but i don't know how and all the guides i've found told me to "select" things that i couldn't find.
I am stuck at the first update so i don't have the usb dabugging enabled but i still can load things using the usb.
Should i send it back? (The device was rooted but i think the factory reset should have removed it)
Please help me i'm desperate! (and sorry for my bad english)
Click to expand...
Click to collapse
Try flashing the factory image. This is for the n5 but will work for the n9. Look at method 2. Use the correct bootloader and radio names for the n9, they'll be different than the examples given. Also in method 2 there is one command that is different for the n9. Instead of fastboot flash userdata userdata.img use fastboot flash vendor vendor.img. Google nexus factory image for the factory image for the n9
http://forum.xda-developers.com/showthread.php?p=47156064
Sent from my Nexus 9 using XDA Free mobile app
jd1639 said:
Try flashing the factory image. This is for the n5 but will work for the n9. Look at method 2. Use the correct bootloader and radio names for the n9, they'll be different than the examples given. Also in method 2 there is one command that is different for the n9. Instead of fastboot flash userdata userdata.img use fastboot flash vendor vendor.img. Google nexus factory image for the factory image for the n9
http://forum.xda-developers.com/showthread.php?p=47156064
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for the fast reply!
It worked! Thanks a lot for you help! You saved my file
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 tried to update my oneplus x to a new version of resurrection remix (the android 7.1 version) by flashing through twrp. Long story short I tried to update the recovery twrp and also update my bootloader but it all went to **** and now my phone is bricked. If I try and boot the phone into either the OS or into recovery I get a boot loop where the oneplus logo appears, the phone vibrates then reboots. I can get into fastboot but when I try and flash either a rom or recovery it tells me I can't because my 'device is not unlocked'. I know my bootloader was unlocked previously but am thinking that by trying to install a new rom it has re-lock or something and I'm not sure if this means my phone is now a paper weight..
Any help would be greatly appreciated!
edit: This problem is fixed. However twrp won't flash/boot correctly now..
Follow this to the letter: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
I did basically the same thing you did and flashed a rom that was compatible with the old bootloader only and it "locked" my bootloader which made the recovery and ROM useless. It took me a few hours to get the device to actually be recognized correctly by the computer and program but it worked. You may also need to google since I remember needing to download basically the same program but from a different site.
Tanner1294 said:
Follow this to the letter: http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
I did basically the same thing you did and flashed a rom that was compatible with the old bootloader only and it "locked" my bootloader which made the recovery and ROM useless. It took me a few hours to get the device to actually be recognized correctly by the computer and program but it worked. You may also need to google since I remember needing to download basically the same program but from a different site.
Click to expand...
Click to collapse
Thanks for the reply! I think I may have come across this but wasn't sure if I'd get myself into more trouble since my fastboot is working (it says it's for devices who have nothing). Rekcon it's still my best option?
Edit:
I tried it and worked perfectly. Thanks heaps!
lilfellabob said:
Thanks for the reply! I think I may have come across this but wasn't sure if I'd get myself into more trouble since my fastboot is working (it says it's for devices who have nothing). Rekcon it's still my best option?
Edit:
I tried it and worked perfectly. Thanks heaps!
Click to expand...
Click to collapse
You're welcome! Like I said I was in the same situation. It kept rebooting and when I got into fastboot my heart sank when it said "Device is locked"
So I now have recovery working as well as fastboot (unlocked this time). But I cannot for the life of me get twrp to work correctly. One version out of like 5 I've tried works but won't flash any roms; I read that could be from a bad version.. All others seem to flash from fastboot but when I try to boot I get the dtb not found error. I don't understand why I cant get it to work, this should be the easy part
lilfellabob said:
So I now have recovery working as well as fastboot (unlocked this time). But I cannot for the life of me get twrp to work correctly. One version out of like 5 I've tried works but won't flash any roms; I read that could be from a bad version.. All others seem to flash from fastboot but when I try to boot I get the dtb not found error. I don't understand why I cant get it to work, this should be the easy part
Click to expand...
Click to collapse
dtb not found error means its not compatiable with your bootloader. Did you try official twrp ? And you ever updated to new bootloader?
update your bootloader first, http://forum.xda-developers.com/onep...t3478917/page1
saurabh40629 said:
dtb not found error means its not compatiable with your bootloader. Did you try official twrp ? And you ever updated to new bootloader?
update your bootloader first, http://forum.xda-developers.com/onep...t3478917/page1
Click to expand...
Click to collapse
I'll give it a shot. I am using official twrp yeah - just seems weird because even the old one that used to work fine isn't working. That link doesn't work is this one ok?
http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Thanks for the help
lilfellabob said:
I'll give it a shot. I am using official twrp yeah - just seems weird because even the old one that used to work fine isn't working. That link doesn't work is this one ok?
http://forum.xda-developers.com/oneplus-x/general/guide-update-bootloader-firmware-to-t3478917
Thanks for the help
Click to expand...
Click to collapse
Yeah... This is the link.
All working, everyones help is much appreciated! <3 thanks
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.