Related
I know that there's probably tons of these, but here goes.
Last night, I tried installing 2.3.320, but ended up looping at the eye. I thought I had installed it wrong, so I tried to access bootstrap recovery to delete the data I hadn't cleared. I was surprised to only be able to access the stock bootloader, 30.04. Anyway, I decided to try using an SBF to restore, but I used the wrong one. Bootloader now loads with these messages, "Err:A5,70,70,00,1F" "MEM_MAP Blank" "Service Req'd".
I got my hands on the system only SBF for 2.3.320 that is floating around, but that still isn't fixing my problem.
Simply put, does anybody know of anything I can do now?
silversonic1 said:
I know that there's probably tons of these, but here goes.
Last night, I tried installing 2.3.320, but ended up looping at the eye. I thought I had installed it wrong, so I tried to access bootstrap recovery to delete the data I hadn't cleared. I was surprised to only be able to access the stock bootloader, 30.04. Anyway, I decided to try using an SBF to restore, but I used the wrong one. Bootloader now loads with these messages, "Err:A5,70,70,00,1F" "MEM_MAP Blank" "Service Req'd".
I got my hands on the system only SBF for 2.3.320 that is floating around, but that still isn't fixing my problem.
Simply put, does anybody know of anything I can do now?
Click to expand...
Click to collapse
Think you're boned. Shoulda read some of the thread at mydroid before taking this on. Most ppl are bricking, with it. You appear to fall into that category.
Go Back to TBH there maybe some help now.
But the 23.15 may also big the big bone.
ouch
This is awful. I'm a guide on another forum for androids and I'm telling people not to try the new update until there is a full sbf available. I'm so sorry. You are stuck..for now.
Well, Verizon's gonna let me swap, so I'll just have to wait until Tuesday and root the new phone.
I'm preparing to root my X and am trying to get a rescue plan in place prior to rooting. The one thing I can't find is a list of what SBF files can safely be used for a given bootloader revision. I posted this in a thread at another forum. Does what I'm asking for not make sense? Or am I completely missing something?
There should be some sort of sticky for SBF'ing the X. I realize that sbf links cannot be posted but it would sure be nice to know which files are needed to properly sbf a semi bricked phone, especially if using the wrong one will fully brick a phone.
What I've gleaned from this thread...
"No if you were stuck on the M that shows that you should already be updated, put your phone into flash mode and make sure (turn of your phone press the camera down volume and power button). It should say boot loader 30.04 if it shows 30.03 then dont use the link provided. If it is 30.04 go download the sbf from ncdubs link and run it using RSD 4.8 and that should be enough for the phone to get past the M logo. Dont it asap because you never know when that link will be dead. Man I was so scared yesterday because i thought my phone was bricked haha but that link that i found in another forum did the job."
"If you are on 2.3.20, use the 2.3.15 SBF.
If you are on 2.3.320, use the SBF's from TBH"
It would be nice to have a running list detailing which sbf file needs to be used for a given bootloader,
i.e. if bootloader is 30.03 use the 2.3.15 sbf or the x.x.xx sbf
if bootlader is 30.04 you can safely use the x.x.xx sbf
and so on.
Surely this won't be in violation of anyone's terms of service would it?
I'm not rooted yet but I'm trying to wade through multiple posts at multiple sites to put together a rescue package prior to rooting and can't find what I believe to be concise information anywhere.
Click to expand...
Click to collapse
http://www.mydroidworld.com/forums/...rikes-back-2-3-320-update-must-rooted-69.html
Post #682 - CZ from TBH is working on a way to restore soft bricked X's,and is making good headway!
bricked, verizon is overnighting one, should have a good clean one tomorrow.
SerialKilla said:
.....link deleted, as this forum won't allow me to post outside links..... yet...
Post #682 - CZ from TBH is working on a way to restore soft bricked X's,and is making good headway!
Click to expand...
Click to collapse
Thanks for the link, I'll be following the thread closely. Sorry to hear you're X is in a semi bricked state. At this point I'm quite wary of doing anything to the X but I believe I have a rescue in place. My phone shows to be 2.3.151 and I found VRZ_MB810_2.3.15_1FF_01.sbf so I believe I should be able to safely recover should I brick it. I rooted using Z4 and the bootstrap, then proceeded to freeze the bloat. I'll run like this until UD for the X comes out then depending on SBF requirement / availability will consider trying it out. UD2 is really sweet on the D1 and I've read it's even nicer on the X.
I must be in the minority because I kind of like blur. I did freeze all of the social networking stuff and installed gallery3d, I would continue to use the blur gallery if it synced with picasa.
edit: SerialKilla I see a new rescue sbf was released, did it work for you?
edthesped said:
Thanks for the link, I'll be following the thread closely. Sorry to hear you're X is in a semi bricked state. At this point I'm quite wary of doing anything to the X but I believe I have a rescue in place. My phone shows to be 2.3.151 and I found VRZ_MB810_2.3.15_1FF_01.sbf so I believe I should be able to safely recover should I brick it. I rooted using Z4 and the bootstrap, then proceeded to freeze the bloat. I'll run like this until UD for the X comes out then depending on SBF requirement / availability will consider trying it out. UD2 is really sweet on the D1 and I've read it's even nicer on the X.
I must be in the minority because I kind of like blur. I did freeze all of the social networking stuff and installed gallery3d, I would continue to use the blur gallery if it synced with picasa.
edit: SerialKilla I see a new rescue sbf was released, did it work for you?
Click to expand...
Click to collapse
I haven't seen the new .sbf yet...where did you see it? If it's just the sytem only fix, that won't work on mine - I need the full .sbf, or whatever it'll be that CZ and P3 are working on. P3 said to expect something in less than 36 hours, but I haven't seen anything as of yet. Too early yet I think - but I know they've had success in their progress, so fingers crossed!
SerialKilla said:
I haven't seen the new .sbf yet...where did you see it? If it's just the sytem only fix, that won't work on mine - I need the full .sbf, or whatever it'll be that CZ and P3 are working on. P3 said to expect something in less than 36 hours, but I haven't seen anything as of yet. Too early yet I think - but I know they've had success in their progress, so fingers crossed!
Click to expand...
Click to collapse
Sorry, it was the system only sbf, I d/l'ed it as a backup and judging by it's size it isn't a full system sbf. Hopefully you'll be rocking again by this time tomorrow.
***Updated: 04/09/2015
First, thank you BeansTown106 and ryanbg for previously sharing the information and technical expertise that has led to successful development of the "tool" that ultimately provides the means to recover a locked bootloader on the Note 4 Developer Device. Without your help and expertise this "tool" may never have been developed.
UDATE: 04/09/2015---There is now a step by step guide that will take you through a process that produces a flashable aboot recovery file for the Developer Edition bootloader if it becomes locked (by flashing retail firmware for instance). This backup MUST be done BEFORE your bootloader becomes corrupted and locked. It is strongly recommended that if you own a Developer Edition Note 4 that you take the time to make a backup of your aboot. This link will take you to a step by step process with links to the couple of files you will need.: http://forum.xda-developers.com/note-4-verizon/general/guide-vzw-note-4-backup-developer-t2962911. Thank you radionerd for the guide and again to BeansTown106 and ryanbg.
Most of us have heard or read about Developer Edition owners of the S4 or S5 that inadvertedly flashed a retail firmware or ROM that was not intended (safe) for the Developer Edition consequently turning their Developer Edition phone into a retail edition phone...locked bootloader. I want to emphasize that this method of recovering a Developer Edition bootloader has been tested and has recovered several Note 4 DE devices whose bootloaders were locked (purposely or inadvertently).
I always found it amazing that people flash ROMs for the wrong device. saw it a lot in Note 2 forums.
Can't believe people can be that careless...especially someone that goes so far as to buy a developer edition. Measure twice...cut once.
tfly212 said:
I always found it amazing that people flash ROMs for the wrong device. saw it a lot in Note 2 forums.
Can't believe people can be that careless...especially someone that goes so far as to buy a developer edition. Measure twice...cut once.
Click to expand...
Click to collapse
Yep, I don't understand either, but it happens.
jpcalhoun said:
Yep, I don't understand either, but it happens.
Click to expand...
Click to collapse
Yeah my Dev edition note 3 got ruined with running "nvbackup" so as a last resort i purposely flashed a retail rom hoping that would just make it work even though it would be locked...
This makes one start to wonder if we could then take a retail version and make it dev as well. If all the hardware is identical and the main difference is the unlocked bootloader..
Fastboot option is not available, but again, hardware being identical, this theoretically should be possible.
gatesjunior said:
This makes one start to wonder if we could then take a retail version and make it dev as well. If all the hardware is identical and the main difference is the unlocked bootloader..
Fastboot option is not available, but again, hardware being identical, this theoretically should be possible.
Click to expand...
Click to collapse
Ive tried to push a DE aboot to the retail Note 4. I can not get it to even write. Ive tried ODIN and ABD to push it. Any suggestions?
mrlaigle said:
Ive tried to push a DE aboot to the retail Note 4. I can not get it to even write. Ive tried ODIN and ABD to push it. Any suggestions?
Click to expand...
Click to collapse
Well, that's kind of my whole point I was being a little sarcastic. With a locked bootloader, lets just say Read-Only, you cannot really overwrite something RO that has already been loaded per say... You would have to be able to fastboot, from my experience, in order to be able to do that. Now if they are signing it, if we could somehow impersonate the key and resign with a newer version number that might work, because they probably have allowances for signed updates.
To me, that might be the only way of resolving this whole locked bootloader issue in general. They obviously have the ability to update them, so we need to figure out how to sign it somehow and or understand their conditions. Meaning, what if they are already planning the next planned bootloader version coming within the existing one. So in this case, if it doesn't match what is expected on the check it will fail along with the fact the signature is not correct.
mrlaigle said:
Ive tried to push a DE aboot to the retail Note 4. I can not get it to even write. Ive tried ODIN and ABD to push it. Any suggestions?
Click to expand...
Click to collapse
Have you tried it from the phone useing Terminal Emulator and the su command?
I could only copy aboot.bak via terminal emulator. I couldn't get through with CMD in windows 7. (I have only copied the file.)
It will not work... The tell tale sign is all of the capable devs of possibly accomplishing this moved on to Tmo or quit developing all together. Loosing Hashcode was a major blow to the dev community.
droidstyle said:
It will not work... The tell tale sign is all of the capable devs of possibly accomplishing this moved on to Tmo or quit developing all together. Loosing Hashcode was a major blow to the dev community.
Click to expand...
Click to collapse
Not all have given up yet ... I am still hard at it.. Ye of little faith..
If anyone wants to send me an image of their aboot for research purposes, it'd make my day
ryanbg said:
If anyone wants to send me an image of their aboot for research purposes, it'd make my day
Click to expand...
Click to collapse
PM sent
wy1d said:
PM sent
Click to expand...
Click to collapse
anyway i can one too/??
larrycjr said:
anyway i can one too/??
Click to expand...
Click to collapse
I'm not certain that p6 is the aboot. I'm thinking it may be p7. I've asked for verification in the other thread.
is there an odin file for the developer edition device? if so will someone direct me there??
larrycjr said:
is there an odin file for the developer edition device? if so will someone direct me there??
Click to expand...
Click to collapse
No there isn't. That is what we are all looking for. Samsung hasn't released one and I'm not sure how to make one from the retail version by replacing the aboot.
wy1d said:
No there isn't. That is what we are all looking for. Samsung hasn't released one and I'm not sure how to make one from the retail version by replacing the aboot.
Click to expand...
Click to collapse
Well, we could do a dd if, blah blah blah and back up the partition once rooted, but this is not really what we want, because we want a factory clean, fresh partition. Not a modified boot, root, recovery etc... Can you guys connect to Kies on the developer addition and do a firmware upgrade and reinitialization option on the tools menu. Because this, would in fact, call out and download the whole image for the phone where you could snag it before it started trying to commit it to the phone. That is essentially what I did to get the factory image for the retail phone.
gatesjunior said:
Well, we could do a dd if, blah blah blah and back up the partition once rooted, but this is not really what we want, because we want a factory clean, fresh partition. Not a modified boot, root, recovery etc... Can you guys connect to Kies on the developer addition and do a firmware upgrade and reinitialization option on the tools menu. Because this, would in fact, call out and download the whole image for the phone where you could snag it before it started trying to commit it to the phone. That is essentially what I did to get the factory image for the retail phone.
Click to expand...
Click to collapse
I've tried that. It says there is no image available for the phone. I've also gone to the Mosaic kiosks (Samsung inside Best Buy) and they use a different tool called Samsung Smart tool to reflash phones. They also do not have an image for the DE Note 4. I've also talked to Support and Advanced Tech at Samsung - both do not have the image. Finally I've talked to the Samsung repair depot and they also do not have the image. On a whim, I also got pretty high up in Verizon tech support asking them if they had an image. They do not support the DE device (as we know) and also didn't have an image.
wy1d said:
I've tried that. It says there is no image available for the phone. I've also gone to the Mosaic kiosks (Samsung inside Best Buy) and they use a different tool called Samsung Smart tool to reflash phones. They also do not have an image for the DE Note 4. I've also talked to Support and Advanced Tech at Samsung - both do not have the image. Finally I've talked to the Samsung repair depot and they also do not have the image. On a whim, I also got pretty high up in Verizon tech support asking them if they had an image. They do not support the DE device (as we know) and also didn't have an image.
Click to expand...
Click to collapse
Well....... I would say you covered all the bases... lol
In my trials and tribulations of unlocking and rooting my phone. I found myself in a bootloop. The dreaded blue M. After reading endless amount of info from the knowledge this site provides, but im still in pursuit of more knowledge. Being somewhat new to this and my excitement of receiving the phone. I thought I had read enough to start the journey of unlocking and rooting. Wrong. Always backup which I didn't do. I looked here and the MOTO site for instructions on how to.....Long story short I emailed MOTO for the firmware. Their firmware is North America US Retail XT1575 MPH24.49-18_18. The firmware I got here, now from every post ive read it is this one XT1575 MPH24.49-18-3. So leaves me with a couple questions that someone may oblige me with.
So which is the latest?
And if they are the same. I would like to use the MOTO one. But when I extract it, it shows one large unknown file at 2.11 gig. Should I add .img to the end to flash?
On their site it just shows fastboot commands to flash image.
Thanks in advance.
http://forum.xda-developers.com/moto-x-style/development/pure-firmware-tuff-wip-t3224833
That thread has all the stock firmwares listed, with the latest being MPH24.49-18-4, amongst a bunch of other info.
Edit: Unless Moto is withholding a later update, the latest version of the stock ROM is the May security update, which is in the above thread.
Ahh I see. So MPH24.49-18_18 original release. I was going by the last digits. And that's not the case. That's the link I used to pull image to recover my blunder. Last thing correct me if im wrong to install these updates you have to do a full reflash as in start from scratch? And if your bootloader unlocked and rooted it will not auto update ? thanks
As far as I am aware, as long as you have stock recovery, you can accept stock OTAs, even if you are rooted. Assuming you have anything you really need to keep, you can try flashing the stock ROM without deleting the system partition, and see if that works for you. Though, in doing that, you risk instability.
I've flashed almost all the stock builds. Sometimes wipe is not needed but usually it's best just to wipe and start fresh.
Questions go in q&a.
Hello, Ya all... hope you're doing fine.
I searched for days to find a serious guide to root moto c, xt1754, and wasnt successful. Now, am an older guy and I sure cant dive as deep as you do into that area Had me a fine Moto G and rooted it with XDA know how pretty good. Unfortunately this device got stolen a few weeks ago. Since am not a rich man and that I needed a new device, I got the Moto C. I can see for myself thats a pretty simple piece... but till am able to get a better Moto - I'd like to root XT1754 either. So, is anyone willing to help me? Could I use the files I once successful used for Moto E and G, logically updated?
Is Moto C another kind Moto E?
Hope I'd describe my case well enough for you. I also truly hope someone might have mercy with me and can let me know what I've to do.
Wish you all a Good Time at All.
Tyd27
In short, no, you cannot use the same files as on previous gen Moto's. The reason behind it... quite simple: they have absolutely nothing in common. This Moto C sports an MTK processor, to begin the long list of differences.
What you can try is this:
1. Unlock your bootloader. Either via Motorola Developer Website, or via fastboot oem unlock.
adb reboot bootloader
fastboot oem unlock
OR
fastboot oem unlock UNLOCK_CODE_FROM MOTOROLA
Once you're done with that, re-enable USB Debugging and OEM UNLOCK ( if you need to turn it back on ).
Then install the latest Magisk app from www.tiny.cc/latestmanager
At this stage, you will need your original boot image ( from here: https://www.needrom.com/download/moto-c-4g-xt1754-nrd90m-054-row-official-rom/). You will need to register there, and wait basically until forever for that firmware file to finish downloading. Open that up with 7zip and extract it. Find the file called boot-signed.img.
Patch it using Magisk.
move that patched_boot.img in your ADB directory.
adb reboot bootloader.
fastboot flash boot patched_boot.img
At this point, 2 options:
a. It will flash, in which case you will do fastboot reboot
b. it will not flash, in which case you will get an error ( boot image not signed etc)
If the first option occurs, you might get a "corrupt" error screen upon reboot. Follow the steps and let the phone do a factory reset. If it reboots properly, re-install Magisk and enjoy root.
if it does not want to reboot properly... you'll congratulate yourself on having the firmware handy
So, thanx alot for this answer. Am happy that someone took care now coz i really dont like unrooted devices. Well, the other side is am 58 now and not a professional at phones. Rooted a few motos with xda help and all went good. Unfortunately my last moto g got stolen and fir what reason ever else i chose to get moto c. Probably it was realky damn ****n stupid. Until i can afford another moto i going to try everything to root moto c. I'll read your reply now before i start doing it. Too bad that there is no way rooting it like moto g. Does it mean i wont have twrp neither?
Have a Good Day.
Tyd27
Definitely no TWRP on it, until someone with the knowledge will port it. That's just how it goes with MTK Devices and their closed source, I'm afraid.
Hi can u make a custom recovery for moto c xt1754
https://forum.xda-developers.com/android/development/recovery-twrp-3-1-1-0-moto-c-t3703184
What is the point of installing twrp and custom ROMs and magisk etc when we can't even remove this annoying Bootloader unlocked warning telling any would be thief to steal it. Im starting this here forum too see what we can do to change this. I have previously owned at ZTE Axon 7 4gb ram 64gb gold has a Snapdragon 820 in it. Your asking wtf does this have to with the op5t relax I'm getting to that. ZTE phone was amazing for awhile. Custom ROMs, kernels, recoveries etc. When you install custom ROM on unlocked bootloader you get the warning every time you boot up. A couple of devs or more I believe through XDA came up with a bootloader warning remover zip and custom splash images for the Axon 7 and it worked perfectly no more boot warning God I loved that. Now what I would like to do is to find away to modify that very script to work with the op5 and op5t. Basically the warnings are jpegs and the remover zip removes them from the bootloader and replaces it with the splash IMG or modified no splash IMG eliminating the warning completely. Wouldn't it be nice op5 and op5t users to flash custom ROMs and not have to worry about that annoying warning like forever. I will upload the ZTE post about the bootloader remover zip and splash images and see if some devs can't figure out how to modify that script. I know codeworx is one of the op5t maintainers who might be interested in this. I'll post again soon. Let me know who else is interested first thanks.
Interested... :good:
kirknado18 said:
What is the point of installing twrp and custom ROMs and magisk etc when we can't even remove this annoying Bootloader unlocked warning telling any would be thief to steal it. Im starting this here forum too see what we can do to change this. I have previously owned at ZTE Axon 7 4gb ram 64gb gold has a Snapdragon 820 in it. Your asking wtf does this have to with the op5t relax I'm getting to that. ZTE phone was amazing for awhile. Custom ROMs, kernels, recoveries etc. When you install custom ROM on unlocked bootloader you get the warning every time you boot up. A couple of devs or more I believe through XDA came up with a bootloader warning remover zip and custom splash images for the Axon 7 and it worked perfectly no more boot warning God I loved that. Now what I would like to do is to find away to modify that very script to work with the op5 and op5t. Basically the warnings are jpegs and the remover zip removes them from the bootloader and replaces it with the splash IMG or modified no splash IMG eliminating the warning completely. Wouldn't it be nice op5 and op5t users to flash custom ROMs and not have to worry about that annoying warning like forever. I will upload the ZTE post about the bootloader remover zip and splash images and see if some devs can't figure out how to modify that script. I know codeworx is one of the op5t maintainers who might be interested in this. I'll post again soon. Let me know who else is interested first thanks.
Click to expand...
Click to collapse
The more people with one plus 5t phones we can get interested in this project the better. It will force the developers to do something about it. So everyone interested please chime in with your thoughts on this. I loved it on the Axon 7 and the one plus 5t blows the axon away in ram and storage. Axon 7 still love the front firing speakers though lol. So please share your thoughts I'm trying to get as many oneplus 5and 5t users as I can. So show your love modders what do you think. You love custom ROMs like I do. You like to mess with your device to see what it can do. So do I but the bootloader warning has gots to go. If you'd like to check this out look up remove bootloader warning axon 2017g in chrome read up. I'll get the URL for this soon and it give you an idea of what I'm taking about thank
interested
I'm pretty sure a number of users would want this.. and I get it. It doesn't bother me that much though.
Personally, whenever that splash warning pops up, I just press the power button twice to pause then continue. This cuts the wait time for that warning and phone initiate the actual boot process right away and I'll be on my way.
Sent from my OnePlus 5T using XDA Labs
I'm also interested
This has been discussed before. The warning on the 5/5T isn't an image like it was on older devices. Since it's not an image, it's not a simple replace 'warning image' with another picture. You would need to modify the bootloader to ignore the verity check so the actual warning goes away.
I have seen one person get rid of the warning and that required him to build and sign all of his own packages. Essentially, he re-locked the bootloader and since all of his items were signed (properly) the device would continue to boot.
Edit: Found the post.
superatmel said:
You have to sign boot.img and recovery.img to remove the warning.
I have managed to eliminate it by signing those two images.
In my oneplus 5 and 5t I have twrp installed and with rom lineageos without warning.
Who wants to try to send me your boot and recovery and return it for you to try.
Remember that you have to close the bootloader whereby the phone will be wipe
Process:
fastboot oem unlock
unlock bootloader
You have to go back to fastboot mode
fastboot flash boot boot.img
fastboot recovery recovery_name.img
fastboot oem lock
Wuala
It can be done in any rom from firmware 5.1.5
Click to expand...
Click to collapse
kirknado18 said:
...
Click to expand...
Click to collapse
@kirknado18 THREAD CLOSED as a subject matter related thread already exists, to which the relevant posts from above have been copied: https://forum.xda-developers.com/oneplus-5t/help/remove-unlocked-bootloader-warning-t3841712
XDA Forum Rules (excerpt):
...
5. Create a thread topic or post a message only once, this includes external links & streaming media.
As a large forum, we don't need unnecessary clutter. You're free to edit your message as you like, so if you do not receive an answer, revisit your message and see if you can describe your problem better. Not everyone is online at the same time so it might take a while before you receive an answer.
You can bump your unanswered question once every 24 hours
Duplicate threads and posts will be removed
Always post in an existing thread if a topic already exists, before creating a new thread.
Use our search function to find the best forum for your device.
Links to an external source are only allowed if relevant to the topic in hand. A description must be included, no copy & pasting from the original source.
Self-promotion is forbidden, this includes blogs, social media and video channels etc. Random links will be removed.
...
Click to expand...
Click to collapse