After talking to customer service and having them be completely useless, I've realized I probably need to reflash the device.
Couple of questions:
Does the bootloader need to be unlocked to reflash this device? If so, how would I do it?
Also, how exactly would I go about reflashing this device?
Related
About a week ago I received notification to update to ICS. After downloading the file and the phone upgrading it get locked into a boot loop, then after about 14 hours it finally escapes form the loop and starts up only to have the SIM not get recognized, I tried restoring to factory default but it didn't work... I then sent the phone to Bell to get repaired but now they are asking for $200 to fix the phone as apparently the bootloader was unlocked and voided warranty.
As you can guess I'm saying "screw you" to that and trying to fix myself... I'm not experienced with android and when I originally upgraded I didn't back up my original software so i have nothing to restore... So basically right now I am wondering what I should do... the phone is being returned to me not repaired and I want to fix this but don't have the knowledge how to... I'm not dumb when it comes to unlocking phones as I used to unlock old Nokia's and jailbreak iPhones but I have no idea when it comes to Androids.
I'm guessing I will need to try and find an official ROM for this but Bell canada isn't the most open with their OEM software so I was wondering if anyone could help in this area by providing a ROM I could use... secondly I guess I will need to S-off my device in order to install the software?
I have searched the forum to find somethings that may be relevant to what I'm trying to do... but I'm getting confused as to what i should do (The curse of being a Noob)
Any info would be great... thanks
Read through this thread: http://forum.xda-developers.com/showthread.php?t=1668259
Quick summary: you have to be totally stock (relocked bootloader, unrooted, S-ON) to run the update to ICS via Bell.
Thanks... will give it a look through and see if I can recover this way.
Hello, i have a retail xt1097, its already updated to marshmallow, dont really need to be root forever but i need at least temporal root to do some one-time minor changes, such as install my desired launcher as system, led for battery, hostfile and such.
The problem is i dont want to unlock the bootloader untill warranty expires (still 7 months of warranty) so the question is if any app/exploit, can temp root this device, under MM.
*Tryed searching and i found kingoroot does the trick but im not sure if it will work on MM, i cant mess up bricking phones now because im not be able to repair them since weather its hot, people overload powerlines and electricity drops all the time and makes my pc suddently power off.
Any advice? Thanks guys
As far as I know root isn't possible with locked bootloader.
There has been quite a bit of discussion (I think most of what I read was on other forums) about Motorola's warranty policy for unlocked bootloaders: it seems that from what people have experienced they will still honor the warranty if it is strictly a hardware problem. I bought my phone used but with over a year of Moto Care remaining, which the original owner transferred to me. He (the original owner) had already unlocked the bootloader, but the Moto Care is still shown as active and valid on my account, even though I don't even have stock rom anymore. Just to be safe I would definitely (if possible) re-flash stock rom prior to making any warranty claim.
Hmm makes sense, then can i unlock BL, root, do my things, then unroot, flash stock recovery and relock? is that posible? does it need a custom kernel too? im ok with the stock rom just need few one-time tweaks...
Unless you really use Moto Voice a lot I would just install the newly released CM14.1, and if you ever need warranty work try to reflash stock beforehand. Otherwise, flash twrp, root, etc.... That is covered in the general section, probably linked to some of the stickies at the top of the page. I'm not sure if it will work for you to make system modifications and then try to relock bootloader. I think part of relocking the bootloader includes flashing the stock rom, which would undo any changes you have made.
Hi! When I got my R1 HD, I wanted to get Lineage OS and TWRP. I tried everything including:
adb "fastboot oem unlock",
SP Flash Tool, and
DirtyCow R1-HD Tool,
yet I found no luck. Does anybody know how to get an unlocked bootloader and TWRP on an R1 HD v21? Thanks!:good:
P.S:
My "Custom build version" is:
BLU_R0011UU_V21_GENERIC. Also, this is not the Amazon Prime variant, however I got this from Amazon (for example: I get no ads).
Sorry to tell you, but version 21 of the ROM cannot be bootloader unlocked or rooted. The more recent updates have secured the phone so that none of the previous methods you mention work anymore. The phone is no longer being manufactured and Blu does not provide a process for unlocking the bootloader as some other companies, like Motorola, do. So even though you paid more to get the no ad version, you can't root it. 8-( This was only possible in the earlier versions of both the amaon and non-amazon models.
yaconsult said:
Sorry to tell you, but version 21 of the ROM cannot be bootloader unlocked or rooted. The more recent updates have secured the phone so that none of the previous methods you mention work anymore. The phone is no longer being manufactured and Blu does not provide a process for unlocking the bootloader as some other companies, like Motorola, do. So even though you paid more to get the no ad version, you can't root it. 8-( This was only possible in the earlier versions of both the amazon and non-amazon models.
Click to expand...
Click to collapse
So, can I revert back to an earlier version of the ROM where it is possible to unlock the bootloader?
PastThePixels said:
So, can I revert back to an earlier version of the ROM where it is possible to unlock the bootloader?
Click to expand...
Click to collapse
no, the signed updates are incremental so, the checksum verification will pervent flashing old version
OK.... What's the best thing to do now?
I found this option in my updater that says "Local updates". Maybe this can help?
PastThePixels said:
OK.... What's the best thing to do now?
I found this option in my updater that says "Local updates". Maybe this can help?
Click to expand...
Click to collapse
No, sorry - there is no known way to root or flash modified software after the phone has been upgraded with factory software. You can't go back. And, even if you could, it wouldn't help - it still couldn't be rooted or flash a modified ROM. Blu does not offer to unlock bootloaders the way some companies, like Motorola, do. Your phone is stuck with what you have now.
The best thing to do now? Enjoy your cheap android phone with great performance for the price!
yaconsult said:
No, sorry - there is no known way to root or flash modified software after the phone has been upgraded with factory software. You can't go back. And, even if you could, it wouldn't help - it still couldn't be rooted or flash a modified ROM. Blu does not offer to unlock bootloaders the way some companies, like Motorola, do. Your phone is stuck with what you have now.
The best thing to do now? Enjoy your cheap android phone with great performance for the price!
Click to expand...
Click to collapse
Well, is there at least a way to skin the phone (ex: change bootanimation, remove bloatware (Yes, there is still bloatware apps, and I'm talking REMOVE the apps, no uninstall for user only), remove the Adups spyware) so that it is just like stock Android?
PastThePixels said:
Well, is there at least a way to skin the phone (ex: change bootanimation, remove bloatware (Yes, there is still bloatware apps, and I'm talking REMOVE the apps, no uninstall for user only), remove the Adups spyware) so that it is just like stock Android?
Click to expand...
Click to collapse
No - all those things require root, which you can't get. Only the phones that were shipped with earlier versions of the ROM and hadn't been updated over-the-air could be unlocked and rooted.
Related. I have an 8GB phone; Custom build:
BLU_R0010UU_V8.7_GENERIC 05-08-2017
I've been trying to install TWRP (and then Lineage) but I'm having zero luck with SPFlash. I've tried on a couple of computers and followed the directions step by step. Am I missing something here?
Thanks,
Edit: yep, saw in another thread anything above 8.1.
Imma email Blu and see if they'll loosen the restrictions if they're stopping development. Can't hurt at this point.
I need to send in my Xperia 10 dual sim for repair (probably need new battery), it's still on warranty.
Now I had lineageOS on it, and hoped to resolve the battery charging problems by re-flashing the original firmware. I don't have a Winodws computer, so I used XperiFirm and Newflasher on Linux to do that. Everything looks original now, But of course I still have the "your device can't be checked for corruption" effin message popping up, and I don't know if the retailer will service my phone for free if they can see I had the bootloader unlocked.
Now I read that re-locking the bootlaoder will
1) also reset the whole thing to factory settings, delete all data.
2) break the camera?
1.) Is not a problem, they want you to do that before service anyways, and I backed everything up.
2.) Is a problem, because they might yet deduce that I unlocked the bootloader, or give me some other trouble.
However I also saw it hinted in this forum that re-locking the bootloader should be fine if it is done on the original firmware, which would be the case.
...=> If I re -lock, do you think I'll be safe sending it back, regarding signs of the BL being previously unlocked?
A friend of mine has a Redmi note 9 (merlin), his device recently got into a bootloop, and he can't really use it anymore. He's not a technical person, so he hasn't unlocked the bootloader or messed with it in any sort of way..
My first question is, how did the device get into the bootloop? Is it due to a hardware defect, or did the software just randomly get corrupted?
My second question is, how will i reflash the stock ROM? I know that in order to fix this, I'll need to flash the stock ROM to the device, but the bootloader is locked, so how can I do this? Does Xiaomi have a tool to reflash stock even with a locked bootloader? Or do I need to flash it as an update via an sdcard or something? Does fastboot work on xiaomi devices with a locked bootloader? If so, should I flash the image using fastboot? How would I go about doing that?
I'm quite experienced with Custom ROMs and Recoveries, but I've never had to reflash a stock rom before, so I'm a total newbie to this. If anyone here could help me out, then my friend and I would both greatly appreciate it!
PhotonIce said:
A friend of mine has a Redmi note 9 (merlin), his device recently got into a bootloop, and he can't really use it anymore. He's not a technical person, so he hasn't unlocked the bootloader or messed with it in any sort of way..
My first question is, how did the device get into the bootloop? Is it due to a hardware defect, or did the software just randomly get corrupted?
My second question is, how will i reflash the stock ROM? I know that in order to fix this, I'll need to flash the stock ROM to the device, but the bootloader is locked, so how can I do this? Does Xiaomi have a tool to reflash stock even with a locked bootloader? Or do I need to flash it as an update via an sdcard or something? Does fastboot work on xiaomi devices with a locked bootloader? If so, should I flash the image using fastboot? How would I go about doing that?
I'm quite experienced with Custom ROMs and Recoveries, but I've never had to reflash a stock rom before, so I'm a total newbie to this. If anyone here could help me out, then my friend and I would both greatly appreciate it!
Click to expand...
Click to collapse
You can flash safely using fastboot, even with locked bootloader.
Official MIUI has signed images, so them will be flashed without issues.
If you can't enter in fastboot, the spflashtool is the only solution.
Good luck.
Ah, its VD171. You know a lot about this device, do you know why it began to bootloop in the first place?
Only who caused that knows.
Alright, apparently I misread his message. He says that the phone is stuck on the Redmi screen, not the MIUI screen. Doesn't this mean that it's stuck on the bootloader, as its not reaching the MIUI screen, so it must not be bootlooping. He says he took it to a repair shop, and they claim that it is a ram/motherboard fault. I doubt that this is likely, could anyone help me with this matter?
I can think of three posibilities:
1. It is stuck on the MIUI screen, but he is calling that the Redmi screen.
2. He HAS messed up his device himself, probably wiped the OS, and now is stuck on a loop at the Redmi screen.
3. It is actually a fault in the phone.