Related
Hi xdadevelpers team unfortunately i have installed an unoficial rom for my device from this link http://forum.xda-developers.com/showthread.php?t=2069935 it works very good and no thing wrong with it but i have to send my phone to the Authorized agent here in egypt because of a problem at the sim card place in the phone so i need to get back to the official kernal which is ics is there any way to do this please help me
have you noticed, that this is the Razr HD section ?
And yes. MOAR fonts
Though you are indeed in the wrong forum, i'll help you out
There are 2 possibilities:
1. Your bootloader is unlocked:
Grab the appropriate Stock FW here: XT910 Stock Firmwares
And flash your phone according to this guide: http://www.andromods.com/tips-trick/how-to-restore-unroot-droid-razr-m-xt907-stock-original-firmware.html
Though the guide is for the xt907, it'll also work for xt910. As long as your BL is unlocked...
2. Your bootloader is locked and you're on safestrap:
Watch this
And above all: Next time post your question here: Droid RAZR Q&A
Xadro said:
Though you are indeed in the wrong forum, i'll help you out
There are 2 possibilities:
1. Your bootloader is unlocked:
Grab the appropriate Stock FW here: XT910 Stock Firmwares
And flash your phone according to this guide: http://www.andromods.com/tips-trick/how-to-restore-unroot-droid-razr-m-xt907-stock-original-firmware.html
Though the guide is for the xt907, it'll also work for xt910. As long as your BL is unlocked...
2. Your bootloader is locked and you're on safestrap:
Watch this
And above all: Next time post your question here: Droid RAZR Q&A
Click to expand...
Click to collapse
I'm so sorry that i did that mistake and i'm on my way to try your way thanks but also i have saved cid is it works and how to use it ?
mostafas60 said:
I'm so sorry that i did that mistake and i'm on my way to try your way thanks but also i have saved cid is it works and how to use it ?
Click to expand...
Click to collapse
What do you mean by saved cid? Is your phone carrier locked? Or what are you trying to say? You should pick a stock fw, which is at least your country/region better also from your carrier. It may also not be available at the site i mentioned.
If it is not available you could try and make a request. See the op of this thread
There is no such thing as an "unlocked bootloader" XT910 nor any other OMAP chipset Motorola device unless it is an engineering model with an NS bootloader.
There is no OEM unlock available for those devices and there never will be as the bootloader was never designed to be unlocked.
Motorola themselves have stated as much publicly.
This person has wiped their CID. partition in order to successfully flash a firmware from a different region onto his device.
He should seek advice in the proper forum fro those who have experience with this type of cross flashing issue.
It is precisely as a result of the locked bootloader status of these devices that these kinds of issues arise when users attempt to update their device with firmware not intended for their specific hardware or regional configuration.
Uh thanks for the heads up, wasn't aware of that. I assumed that motorola devices would be all similiar with this.
cellzealot said:
There is no such thing as an "unlocked bootloader" XT910 nor any other OMAP chipset Motorola device unless it is an engineering model with an NS bootloader.
There is no OEM unlock available for those devices and there never will be as the bootloader was never designed to be unlocked.
Motorola themselves have stated as much publicly.
This person has wiped their CID. partition in order to successfully flash a firmware from a different region onto his device.
He should seek advice in the proper forum fro those who have experience with this type of cross flashing issue.
It is precisely as a result of the locked bootloader status of these devices that these kinds of issues arise when users attempt to update their device with firmware not intended for their specific hardware or regional configuration.
Click to expand...
Click to collapse
Thanks a lot for your supply actually you did understood what happened with me
But now i faces problem i tried to get back to 2.3.6 and the phone stopped working totally and after two days of searching i found some way to get back to ics but it is opening only from Bp tools from the boot menu can you help me in that ?
mostafas60 said:
Thanks a lot for your supply actually you did understood what happened with me
But now i faces problem i tried to get back to 2.3.6 and the phone stopped working totally and after two days of searching i found some way to get back to ics but it is opening only from Bp tools from the boot menu can you help me in that ?
Click to expand...
Click to collapse
guys is there any one can answer me and how to solve this issue
http://forum.xda-developers.com/forumdisplay.php?f=1622
mostafas60 said:
guys is there any one can answer me and how to solve this issue
Click to expand...
Click to collapse
Probably if you go to the right forum man.
Sent from my PACMAN MATRIX HD MAXX
First of all sorry if my english is not clear, thanks in advance.
I bought a Z5 C6603 in a commercial store, I mean it doesn’t come from any cellular provider company. The first thing I thought when I get it was about rooting it and I did, and I did install TWRP too, but before doing these two things I unlocked the boot loader, in fact as I know if this device comes with the option of bootloader unlock: no, that means the rooting and custom recovery are not possible.
If that is true something happened because when I checked up the service menu after rooting and twrp this option tells me the bootloader unlocking is not allowed. My memory is failing because a have been working in several cell phones despite the fact I’m not an expert. I think in the process I install a kernel or a rom wich made the modification, could It be possible that this kernel change the value?
I have the ver. 32.2.A.0.224
I cannot be imagining being without the possibility of changing Roms
That is odd indeed. But since you've already unlocked your BL, what does it matter anyways what your phone tells you?
Introduction
This is the bootloader unlock from ZTE. It was provided to me in private email by a ZTE engineer.
Warning
This package is for the USA version of the Axon 7 Mini (tulip) running 7.1.1 b14 firmware. If you are running any other device or firmware version, it may not work.
Note
After some testing, it appears that the Axon 7 Mini is not locked in any way. In other words, apparently neither this package nor tuliptool's unlock are required to flash custom ROMs. The only apparent advantage to flashing this is to get access to fastboot, which provides a way to flash a custom boot and recovery (among other things).
Flashing Instructions
Place axon_mini_unlock.zip on the root of your sdcard.
Reboot into recovery.
Select "Apply update from SD card".
Select axon_mini_unlock.zip.
Usage Instructions
After the package is flashed, you may boot into the bootloader:
adb reboot bootloader
Once in the bootloader, you will see an on-screen menu. Additionally, you may access the typical fastboot commands:
fastboot oem device-info
fastboot oem unlock
fastboot flash ...
... etc ...
Download
axon_mini_unlock.zip
md5: ea8f1a21c8a46b3045d00f17a37fe359
So, after this is done, I can flash TWRP through fastboot and tuliptool is no longer necessary, correct?
Yes, that is correct.
JoeGatto said:
So, after this is done, I can flash TWRP through fastboot and tuliptool is no longer necessary, correct?
Click to expand...
Click to collapse
This package is for the USA version of the Axon 7 Mini (tulip) running 7.1.1 b14 firmware. If you are running any other device or firmware version, it may not work.
Click to expand...
Click to collapse
Is this something your contact mentioned or something that you believe based on your experience?
Any harm in trying it on verdandi/other versions without any risk of bricking?
After some testing, it appears that the Axon 7 Mini is not locked in any way. In other words, apparently neither this package nor tuliptool are required to flash custom ROMs. The only apparent advantage to flashing this is to get access to fastboot.
Click to expand...
Click to collapse
Any way to confirm this is also the case with other versions as well?
Thanks TDM.... you're going to have a lot of Canadians asking about verdandi as it is quite cheap here at the moment. Better get those questions out of the way early. The source is released, same kernel version as the U.S. one with some small differences with drivers (from what I can see) and I am sure that if people know that custom roms are possible on that version (not bootloader locked forever) it would be appreciated.
trpn111 said:
Is this something your contact mentioned or something that you believe based on your experience?
Any harm in trying it on verdandi/other versions without any risk of bricking?
Any way to confirm this is also the case with other versions as well?
Thanks TDM.... you're going to have a lot of Canadians asking about verdandi as it is quite cheap here at the moment. Better get those questions out of the way early. The source is released, same kernel version as the U.S. one with some small differences with drivers (from what I can see) and I am sure that if people know that custom roms are possible on that version (not bootloader locked forever) it would be appreciated.
Click to expand...
Click to collapse
Yeah...verdandi is stuck on Marshmellow. But since it has different hardware it could brick if this is tried.
The ZTE engineer is USA based, he is not on the China development team (read: probably a support engineer). He said: "I attached the unlock update zip package, please try it. It is based on B14 build."
Sorry, that's all I have to go by for "official" information.
I do not want to be responsible for anyone bricking their device, so I cannot claim that this bootloader will work with anything other than a tulip device running 7.1.1 b14.
If you want to try and report back, I'm sure others will appreciate it. But I can't be responsible for the results.
trpn111 said:
Is this something your contact mentioned or something that you believe based on your experience?
Any harm in trying it on verdandi/other versions without any risk of bricking?
Any way to confirm this is also the case with other versions as well?
Thanks TDM.... you're going to have a lot of Canadians asking about verdandi as it is quite cheap here at the moment. Better get those questions out of the way early. The source is released, same kernel version as the U.S. one with some small differences with drivers (from what I can see) and I am sure that if people know that custom roms are possible on that version (not bootloader locked forever) it would be appreciated.
Click to expand...
Click to collapse
Oh, and here is some more information to help you decide...
The volume key combo to enter EDL is handled by aboot (bootloader, eg. the thing we are flashing). This means even if you aren't currently able to use the key combo, you should be able to use it with the new aboot here. And if you can get to EDL, you can never really brick the device.
The volume key combo is detected very early in the aboot code. Like, first thing after basic platform init. So even if this isn't compatible with your device, it's likely we could restore the old aboot (assuming you back it up first, of course).
I'm convinced that the tulip is not locked based on my investigation today. So I have no idea if this aboot is properly signed. If your device is locked and this aboot is not signed properly, the lower boot loader won't load it. I'm not quite sure if that kicks you into EDL or not.
Not sure if that makes the decision easier or harder...
How did you come to the conclusion that tulip is not locked to begin with? If we don't need tuliptool or this aboot, how can I check verdandi if the device is the same 'locked but not really locked' state?
I will have a read about backing up aboot and see what I come up with concerning getting into edl.
So here's the deal...
I initially assumed the bootloader was locked because... well... it's supposed to be. So I found the place in aboot code where it checks the lock flag in the devinfo partition. I used the firehose to write unlocked to that flag. Then I built TWRP, flashed it and it booted. So I assumed everything was working just as I expected.
Today, I flashed the aboot with fastboot support and ran "fastboot oem device-info". It said that my device was locked. So I went to look and, sure enough, my devinfo partition flag was still set. Hmm, that's odd.
So I wrote locked back to the flag. TWRP still booted. Now things are looking pretty suspicious.
But maybe the new aboot doesn't even support locking? So I flashed the original b14 version of aboot and TWRP still booted.
That's pretty hard evidence that aboot is ignoring the lock flag. I don't know what they did -- whether they just removed the code that reads the lock flag or introduced a bug or what.
This does not necessarily mean that the lower layers are unlocked. That is, the lower boot loader may still required a properly signed aboot. I don't know, and I'm not ready to brick my device trying to find out.
trpn111 said:
How did you come to the conclusion that tulip is not locked to begin with? If we don't need tuliptool or this aboot, how can I check verdandi if the device is the same 'locked but not really locked' state?
I will have a read about backing up aboot and see what I come up with concerning getting into edl.
Click to expand...
Click to collapse
Hmm... Looks like this package incompatible with ZTE/P852A11/tulip.
Got error while trying to flash it by stock recovery. Error message says that it is for A12 version of tulip.
Ah, yes, you have the euro model. See the "calling all mini owners" thread, posts #76 and #77.
maestromony said:
Hmm... Looks like this package incompatible with ZTE/P852A11/tulip.
Got error while trying to flash it by stock recovery. Error message says that it is for A12 version of tulip.
Click to expand...
Click to collapse
i get a message saying "cant update from sd card?"
yeshivabachur said:
i get a message saying "cant update from sd card?"
Click to expand...
Click to collapse
Make sure battery level is at least 30% before applying any update. It's a standard protection feature.
JoeGatto said:
Make sure battery level is at least 30% before applying any update. It's a standard protection feature.
Click to expand...
Click to collapse
My battery was 80%+ mine still said can't update from sdcard
Aries2010 said:
My battery was 80%+ mine still said can't update from sdcard
Click to expand...
Click to collapse
Try turning on the OEM unlock setting in developer settings.
JoeGatto said:
Try turning on the OEM unlock setting in developer settings.
Click to expand...
Click to collapse
Thank you so much that worked I appreciate the it . Now I have one more question I have been searching for a way to root stock rom but I can't find any instructions on it. Could you walk me through it or post a link for me if possible? I have the USA mini 7 with B14 firmware
Aries2010 said:
Thank you so much that worked I appreciate the it . Now I have one more question I have been searching for a way to root stock rom but I can't find any instructions on it. Could you walk me through it or post a link for me if possible? I have the USA mini 7 with B14 firmware
Click to expand...
Click to collapse
Rooting the stock ROM will require that you remove verity, so that the OS won't refuse to boot once you've made any changes to the system partition. You'll need to use tuliptool to flash a new boot image, which you can find in this section of the forum. Then, you could either install TWRP through fastboot or using tuliptool.
JoeGatto said:
Rooting the stock ROM will require that you remove verity, so that the OS won't refuse to boot once you've made any changes to the system partition. You'll need to use tuliptool to flash a new boot image, which you can find in this section of the forum. Then, you could either install TWRP through fastboot or using tuliptool.
Click to expand...
Click to collapse
Thank you sir I appreciate it I shall try it tomorrow.
here's a stupid question.... I have only dealt with Samsung devices so, I have trouble understanding any other kind of process that is not Samsung. If a new update comes out while my device is bootloader unlocked can i update it? or will it brick my device?
The "standard" (not Samsung) method of updating via OTA is to ship:
1. Full images of any firmware partitions (rpm, tz, aboot, etc.)
2. Full image of boot.
3. A delta (patch) to system.
Also note that custom recoveries generally do not work with vendor OTA's.
This means that if you wish to apply an OTA, you must first have stock recovery and a completely pristine, unmodified system partition. The rest doesn't matter.
yeshivabachur said:
here's a stupid question.... I have only dealt with Samsung devices so, I have trouble understanding any other kind of process that is not Samsung. If a new update comes out while my device is bootloader unlocked can i update it? or will it brick my device?
Click to expand...
Click to collapse
Hi guys i want to share with you this methode to unlock bootloader on Oreo for Nokia 3 go to this thread and requests the files from @bigrammy
This is the thread link : https://forum.xda-developers.com/no...-t3708129/post76293046?nocache=1#post76293046
Don't forget to hit thank's to him and me 12 thanks is not enough ??
This methode work with So Flashtool ?
I'm going to make SPflashTool working. I have some issue
Riadh300 said:
Hi guys i want to share with you this methode to unlock bootloader on Oreo for Nokia 3 go to this thread and requests the files from @bigrammy
This is the thread link : https://forum.xda-developers.com/no...-t3708129/post76293046?nocache=1#post76293046
Don't forget to hit thank's to him and me 12 thanks is not enough ?
Click to expand...
Click to collapse
Thanks for your enthusiasm but my method does not Unlock the bootloader so you should change your thread title.
As I told you I will open a thread when the method is fully tested by a few advanced user's who are testing it now and you will be given full credit for all your help.
I do not want to risk anyone bricking their phones due to rushing. Many none advanced users bricked their sony c4 phones by Not following my instructions so I need this to be 100% clear and fully tested I hope you understand.
I understand you @bigrammy by flashing twrp bootloader will automatically unlocked !
Riadh300 said:
I understand you @bigrammy by flashing twrp bootloader will automatically unlocked !
Click to expand...
Click to collapse
If the bootloader was unlocked fully you would be able to use fastboot to flash the device but we cannot so the bootloader is still locked to all intense purposes.
The secure boot chain does appear to be broken so we can use SPFlashTool to flash and boot our TWRP recovery but the secure boot chain may still be working if you have never unlocked the bootloader before like on Android 7.x. This means TWRP may Not boot up for everyone. Like I said it needs to be fully tested.
bigrammy said:
If the bootloader was unlocked fully you would be able to use fastboot to flash the device but we cannot so the bootloader is still locked to all intense purposes.
The secure boot chain does appear to be broken so we can use SPFlashTool to flash and boot our TWRP recovery but the secure boot chain may still be working if you have never unlocked the bootloader before like on Android 7.x. This means TWRP may Not boot up for everyone. Like I said it needs to be fully tested.
Click to expand...
Click to collapse
Thanks for this informations ! ?
Riadh300 said:
I understand you @bigrammy by flashing twrp bootloader will automatically unlocked !
Click to expand...
Click to collapse
Actually, spflashtool bypasses the bootloader in this instance, so the bootloader is untouched and you still flash twrp
---------- Post added at 08:35 AM ---------- Previous post was at 08:02 AM ----------
bigrammy said:
I do not want to risk anyone bricking their phones due to rushing. Many none advanced users bricked their sony c4 phones by Not following my instructions so I need this to be 100% clear and fully tested I hope you understand.
Click to expand...
Click to collapse
Not to be pessimistic, but you do realise that even with all your precautions,people will still not read properly and will still brick their phones, no matter how many precautions you take. Even if you had an app that requires you to click one button to do everything,there are still people who will do it wrong. That said I think I know of one or 2 people in this Nokia 3 forum who were able to recover their phones using spflashtool AFTER the phone couldn't even be detected by their pc, even OST flashing was not possible .
Another thing is, all the Nokia 3 is last year's phone, I wonder how many experienced users will be buying the phone now, and experienced people are probably not the best way to get something 100% tested, because they know the right steps to take.
I think you should make your method public after you hear from SkaboXD
redweaver said:
Another thing is, all the Nokia 3 is last year's phone, I wonder how many experienced users will be buying the phone now, and experienced people are probably not the best way to get something 100% tested, because they know the right steps to take.
I think you should make your method public after you hear from SkaboXD
Click to expand...
Click to collapse
Sorry I replied to your PM before seeing this.
True there is no accounting for people but I don't want to get bogged down by noob's. If you and maybe SkaboXD would like to open a thread and manage it using the method then that would be fine by me as long as credit is give to Riadh300 the original tester and who informed me SPFlashTool still worked and myself of course.
Please read my PM about the bootloader condition as I recommend only previously unlocked devices try this for now until tested by Advanced user able to recover the device should anything go wrong (EFuse Blown).
bigrammy said:
Sorry I replied to your PM before seeing this.
True there is no accounting for people but I don't want to get bogged down by noob's. If you and maybe SkaboXD would like to open a thread and manage it using the method then that would be fine by me as long as credit is give to Riadh300 the original tester and who informed me SPFlashTool still worked and myself of course.
Please read my PM about the bootloader condition as I recommend only previously unlocked devices try this for now until tested by Advanced user able to recover the device should anything go wrong (EFuse Blown).
Click to expand...
Click to collapse
Alright I understand your point now. One thing I wonder though is: would someone on nougat who has never unlocked bootloader be able to flash ost?
Just checked my phone, oem unlocking was set to off so you're right, your method doesn't actually affect the bootloader.
I actually don't mind posting your method and giving you guys the credit, I just thought that you would want to be the one to do so.
Anyway I'll wait to hear @SkaboXD thoughts before I decide on whether to put up the post
redweaver said:
Alright I understand your point now. One thing I wonder though is: would someone on nougat who has never unlocked bootloader be able to flash ost?
Just checked my phone, oem unlocking was set to off so you're right, your method doesn't actually affect the bootloader.
I actually don't mind posting your method and giving you guys the credit, I just thought that you would want to be the one to do so.
Anyway I'll wait to hear @SkaboXD thoughts before I decide on whether to put up the post
Click to expand...
Click to collapse
Before on 7.0 I flashed a TWRP I was working on via SPFlashTool bootloader locked and ended up in a never ending recovery bootloop which none advanced users may find difficult to get out of now this may of been because I screwed up the TWRP or more likely because the bootloader was Locked.
I did not try any other TWRP's until I was bootloader Unlocked and I have not had the recovery bootloop since.
Not sure about OST as SPFlashTool is by far the best tool for MediaTek devices and recovery of said devices remember the SoC manufacturer knows best and I only ever see problems when the OEM's try to move away from it like Sony did.
Happy for you to take the lead I am too busy in other threads to worry about it
bigrammy said:
Before on 7.0 I flashed a TWRP I was working on via SPFlashTool bootloader locked and ended up in a never ending recovery bootloop which none advanced users may find difficult to get out of now this may of been because I screwed up the TWRP or more likely because the bootloader was Locked.
I did not try any other TWRP's until I was bootloader Unlocked and I have not had the recovery bootloop since.
Not sure about OST as SPFlashTool is by far the best tool for MediaTek devices and recovery of said devices remember the SoC manufacturer knows best and I only ever see problems when the OEM's try to move away from it like Sony did.
Happy for you to take the lead I am too busy in other threads to worry about it
Click to expand...
Click to collapse
So how did you get your phone back anyway?
redweaver said:
Alright I understand your point now. One thing I wonder though is: would someone on nougat who has never unlocked bootloader be able to flash ost?
Just checked my phone, oem unlocking was set to off so you're right, your method doesn't actually affect the bootloader.
I actually don't mind posting your method and giving you guys the credit, I just thought that you would want to be the one to do so.
Anyway I'll wait to hear @SkaboXD thoughts before I decide on whether to put up the post
Click to expand...
Click to collapse
I will lock bootloader and try this method of rooting. I think that is this the best method because it doesn't affect bootloader so you can have OTA updates. Just what is the root manager, SuperSU or Magisk?
I think that we could make a thread when this mehod is tested on both Nougat and Oreo with locked bootloader. As far as i read, Oreo is tested so only Nougat remains to test.
redweaver said:
So how did you get your phone back anyway?
Click to expand...
Click to collapse
:laugh: Sorry mate this is what I mean. I simply don't have the time to sit answering every single question as there is no short answers
I hope you understand.
SkaboXD said:
I will lock bootloader and try this method of rooting. I think that is this the best method because it doesn't affect bootloader so you can have OTA updates. Just what is the root manager, SuperSU or Magisk?
I think that we could make a thread when this mehod is tested on both Nougat and Oreo with locked bootloader. As far as i read, Oreo is tested so only Nougat remains to test.
Click to expand...
Click to collapse
OK, one thing though, before flashing the recovery you might want to do a backup of the stock recovery if you don't already have one. That's what I did, so after I got root, flashed back my stock recovery. Magisk is the root manager ,
---------- Post added at 12:17 PM ---------- Previous post was at 12:12 PM ----------
bigrammy said:
:laugh: Sorry mate this is what I mean. I simply don't have the time to sit answering every single question as there is no short answers
I hope you understand.
Click to expand...
Click to collapse
oh you mean you went through hoops to get your phone back? I thought you would say you got a stock recovery somewhere and flashed using spflashtool or used the ost method. I didn't actually expect you to outline the steps you used. BTW, first time I flashed twrp AFTER unlocking bootloader, I got stuck in a recovery bootloop too. I had to flash my phone with OST then retry the process again.
One other thing, I think OST is actually a propriety software that is supposed to work for lots of phones, at least I know that users of other non mediatek Nokia phones also use it to recover their phones (with the corresponding stock images of course)
SkaboXD said:
I will lock bootloader and try this method of rooting. I think that is this the best method because it doesn't affect bootloader so you can have OTA updates. Just what is the root manager, SuperSU or Magisk?
I think that we could make a thread when this mehod is tested on both Nougat and Oreo with locked bootloader. As far as i read, Oreo is tested so only Nougat remains to test.
Click to expand...
Click to collapse
Magisk hide allows you get OTA's see the Magisk thread and yes it will work on any android version.
@redweaver
I am glad you got out of the loop but your clearly a more advanced user hence why I ask you to test. :good:
The OST is very convoluted for use on MediaTek devices and is very unnecessary it also requires unnecessary FIH software to be installed on the phone to work properly.
They likely choose this method to work across different SoC's but it's not what MediaTek use SPFlashTool is MediaTeks own software.
EDIT: Sorry lost internet for a while then.
I continue: Good news is I do not think they will be able to remove SPFlashTool use as it's binary on device which lives on a none volatile area ram chip or radio chip and is loaded at the factory so I doubt it can be updated via a OTA. :fingers-crossed:
Sony actually replaced this and this is the only device I have been unable to recover and even Sony were replacing the boards of bricked devices but if they had left the Mediatek binary in there it would not of been a issue as SPFlashTool would of been able to recover them. :good:
guys, old thread, i know, different device, i know, but ive been in the dark and this is what most resembles my issue.
any hints would be appreciated, read all 2 pages, can you believe it? im a very average xda enthusiast.
worries out of the way, my sincere thanks beforehand follow.
issue
carrier doesnt get in the way
oem doesnt get in the way
oem unlock toggle, check, adb debugging, you and i know the drill, no driver/cable issues
cannot for the life of me unlock bootloader, this one would take the newer command, however i tried them all ive come accross to no avail
output encourages me to unlock first, howwever not a clue is given as to how to accomplish it. this isnt the flash a file type of unlocking, either, at least not oem provided. going nuts.
go ahead and feel free to issue "advanced" directions (meaning, like your voicemail, instead of "for voicemail configurations press 8" and just "configurations 8"
spreatrum, not mtk
x120c
came with oreo go, treble enabled per getprop
i dont know what else, please
hey you guys we owners of the 10.or G would really appropriate if ya started building custom roms for the 10.or G 32GB and 64GB.
The phone is really awsome and i think it would out out perform other phones in this catogory. please please please try and port Resurrection remix for this phone it would be crazy good.
thanks in advance if this happens
scottdroolboyswinden said:
hey you guys we owners of the 10.or G would really appropriate if ya started building custom roms for the 10.or G 32GB and 64GB.
The phone is really awsome and i think it would out out perform other phones in this catogory. please please please try and port Resurrection remix for this phone it would be crazy good.
thanks in advance if this happens
Click to expand...
Click to collapse
Can we plz get a custom rom for 10 or g as fast it can be ,plz i really beg before u all members.....
Can we get pie build for 10.or.g ... that'd be dope
Miui for 10 or G
I want miui 10 custom rom for my mobile please developer develop my os
10.or g
Hey guys I am the user of 10.or g it's an awesome phone just need a awesome custom ROM for it hope you guys help me for it
Bootloader issues
There is a great problem in unlocking bootloader....
Then only we can install custom rom...
Without unlocking there is no twrp/cwm recovery
if we dont have it we cant able to install it
you need to ask support team of tenor g by email...
I am always asking them but they are not giving us valuable reply
I was watching how to compile roms... But we will need a device source tree for compiling roms
Before that we neet to unlock bootloader
Can anyone try this command in fastboot mode and confirm if bootloader unlocks?
fastboot oem unlock
Make sure u have backed up your data because it will wipe data
I have my warranty for 6 months left? so can anyone without warranty test it out?
I will start development on it after i am confident enough on compiling roms and i get my new laptop?
Abhishek17599 said:
I was watching how to compile roms... But we will need a device source tree for compiling roms
Before that we neet to unlock bootloader
Can anyone try this command in fastboot mode and confirm if bootloader unlocks?
fastboot oem unlock
Make sure u have backed up your data because it will wipe data
I have my warranty for 6 months left so can anyone without warranty test it out?
I will start development on it after i am confident enough on compiling roms and i get my new laptop
Click to expand...
Click to collapse
Another way to install twrp if you have stock ROM , if yes then replace recovery.img in stock ROM with twrp recovery.img then full flash phone . Phone will unlock .
I am also try on another phone , but I have no stock ROM this phone .
deepakuklan said:
Another way to install twrp if you have stock ROM , if yes then replace recovery.img in stock ROM with twrp recovery.img then full flash phone . Phone will unlock .
I am also try on another phone , but I have no stock ROM this phone .
Click to expand...
Click to collapse
We can use generic twrp for snapdragon 625 devices , i havent actually tested it but have seen in a couple of guides
Abhishek17599 said:
We can use generic twrp for snapdragon 625 devices , i havent actually tested it but have seen in a couple of guides
Click to expand...
Click to collapse
You can download TRWP FROM https://androidfilehost.com/?fid=11050483647474829650
---------- Post added at 04:54 AM ---------- Previous post was at 04:29 AM ----------
Pls post anyone stock ROM for 10.or G
deepakuklan said:
Another way to install twrp if you have stock ROM , if yes then replace recovery.img in stock ROM with twrp recovery.img then full flash phone . Phone will unlock .
I am also try on another phone , but I have no stock ROM this phone .
Click to expand...
Click to collapse
Herehttps://firmwarefile.com/category/tenor
Maxz21 said:
Herehttps://firmwarefile.com/category/tenor
Click to expand...
Click to collapse
this is not stock rom .this is only update file
Abhishek17599 said:
I was watching how to compile roms... But we will need a device source tree for compiling roms
Before that we neet to unlock bootloader
Can anyone try this command in fastboot mode and confirm if bootloader unlocks?
fastboot oem unlock
Make sure u have backed up your data because it will wipe data
I have my warranty for 6 months left[emoji39] so can anyone without warranty test it out?
I will start development on it after i am confident enough on compiling roms and i get my new laptop[emoji41]
Click to expand...
Click to collapse
Yep, I'm sure someone could test it for you......that someone is YOU.
If you want it tested, test it yourself. You said your device is under warranty, that means if you brick it, you can get it replaced. If someone that does NOT have warranty bricks their device testing this for you, they will be stuck with a dead device and no way to get it replaced, whereas, YOU CAN IF IT GOES WRONG.
You're asking others to risk their device for your own convenience to protect your own device. That is is being spoiled, rude and inconsiderate.
Sent from my LGL84VL using Tapatalk
Droidriven said:
Yep, I'm sure someone could test it for you......that someone is YOU.
If you want it tested, test it yourself. You said your device is under warranty, that means if you brick it, you can get it replaced. If someone that does NOT have warranty bricks their device testing this for you, they will be stuck with a dead device and no way to get it replaced, whereas, YOU CAN IF IT GOES WRONG.
You're asking others to risk their device for your own convenience to protect your own device. That is is being spoiled, rude and inconsiderate.
Click to expand...
Click to collapse
Bro that command won't brick any device , plus have some common sense ... If anyone unlocks bootloader it's warrenty is voided
I'll try it myself if no one does and be the first one to respond then.... I garuntee you that... But after my warrenty period is over...
I haven't ordered anyone to do this ... Its upto that individual... There's no need to respond like that
Abhishek17599 said:
Bro that command won't brick any device , plus have some common sense ... If anyone unlocks bootloader it's warrenty is voided
I'll try it myself if no one does and be the first one to respond then.... I garuntee you that... But after my warrenty period is over... I have experience of unlocking bootloaders and using roms for 3-4 devices and 5 yrs
I know what should i post and what not... Be sensible ... Research before u say anything
Click to expand...
Click to collapse
Be sensible? I was being more sensible than you understand due to your un-awareness to certain things about android devices. You've unlocked the bootloader and used ROMs on 3-4 devices in the past 5 years, great, that gives you experience with the devices that you own. That doesn't mean much when it comes to other devices, though.
It wasn't so much a matter of whether it was a potential brick or not, it was the fact that you ask someone else to test instead of doing it yourself. Generally, using oem unlock command does not brick a device....but, you aren't exactly right. Running the oem unlock command CAN and HAS bricked devices, they are device specific scenarios though. I have an RCA tablet that is unrecoverable due to using fastboot to unlock bootloader and that was on 4.4, long before all the extra security measures implemented by manufacturers and carriers today ever came along. Bootloader unlocking these days can be much more tricky than it was on that old device. So, as you said, do your research. I wouldn't have said anything if I didn't already know.
Also, you are aware that even if you tried the command and it unlocked your bootloader, you could easily relock the bootloader, which wouldn't void your warranty unless the manufacturer/carrier was standing right there looking over your shoulder when you unlocked the bootloader?
Sent from my LGL84VL using Tapatalk
Droidriven said:
It wasn't so much a matter of whether it was a potential brick or not, it was the fact that you ask someone else to test instead of doing it yourself. Generally, using oem unlock command does not brick a device....but, you aren't exactly right. Running the oem unlock command CAN and HAS bricked devices, they are device specific scenarios though. I have an RCA tablet that is unrecoverable due to using fastboot to unlock bootloader. So, as you said, do your research. I wouldn't have said anything if I didn't already know.
Also, you are aware that even if you tried the command and it unlocked your bootloader, you could easily relock the bootloader, which wouldn't void your warranty unless the manufacturer/carrier was standing right there looking over your shoulder when you unlocked the bootloader?
Click to expand...
Click to collapse
fastboot oem unlock
It probably should work...
This is another device from this company running stock android ....
Also i have seen some guides online referring to same guide
I apologise for earlier rudeness ... But i meant to help up there .... there were people wanting to unlock bootloader and so i gave them a way of doing so.... But i should have framed my sentense in a better way...? I'll keep that in mind...
One thing i want to ask ..will the generic snapdragon 625 twrp work wiith this device?
Abhishek17599 said:
fastboot oem unlock
It probably should work...
This is another device from this company running stock android ....
Also i have seen some guides online referring to same guide
I apologise for earlier rudeness ... But i meant to help up there .... there were people wanting to unlock bootloader and so i gave them a way of doing so.... But i should have framed my sentense in a better way...[emoji39] I'll keep that in mind...
One thing i want to ask ..will the generic snapdragon 625 twrp work wiith this device?
Click to expand...
Click to collapse
My point was to be careful what you post when it comes to unlocking bootloader these days. Bootloader unlocking gets more tricky by the day with all the coding and security measures used by manufacturers and carriers as time goes on. They are getting better at creating roadblocks for people like us. As these measures evolve, more and more users are breaking devices due to encountering security measures on their device that they were unaware of.
Sent from my LGL84VL using Tapatalk
Droidriven said:
My point was to be careful what you post when it comes to unlocking bootloader these days. Bootloader unlocking gets more tricky by the day with all the coding and security measures used by manufacturers and carriers as time goes on. They are getting better at creating roadblocks for people like us. As these measures evolve, more and more users are breaking devices due to encountering security measures on their device that they were unaware of.
Click to expand...
Click to collapse
Yeah ... The likes of huawei haave totally hindered the development of potential devices
Well... Xiaomi is doing a great job in this front
https://www.stupdroid.com/2018/07/root-twrp-10or-G.html?m=1
This is one of the posts i went through and
https://androidfilehost.com/?fid=11050483647474829650
This is the recovery which is recommended and i have doubt for
Abhishek17599 said:
fastboot oem unlock
It probably should work...
This is another device from this company running stock android ....
Also i have seen some guides online referring to same guide
I apologise for earlier rudeness ... But i meant to help up there .... there were people wanting to unlock bootloader and so i gave them a way of doing so.... But i should have framed my sentense in a better way...[emoji39] I'll keep that in mind...
One thing i want to ask ..will the generic snapdragon 625 twrp work wiith this device?
Click to expand...
Click to collapse
I did a search for "generic TWRP for snapdragon 625".
I didn't find anything, all I found was mention of using treble.
I'm not sure there can even be such a thing as generic TWRP due to the way it has to be built specific to the hardware in the device.
Sent from my LGL84VL using Tapatalk
---------- Post added at 10:37 AM ---------- Previous post was at 10:36 AM ----------
Abhishek17599 said:
Yeah ... The likes of huawei haave totally hindered the development of potential devices
Well... Xiaomi is doing a great job in this front
https://www.stupdroid.com/2018/07/root-twrp-10or-G.html?m=1
This is one of the posts i went through and
https://androidfilehost.com/?fid=11050483647474829650
This is the recovery which is recommended and i have doubt for
Click to expand...
Click to collapse
I usually don't trust sources outside of XDA, you never know what you are going to get in those situations.
Sent from my LGL84VL using Tapatalk
---------- Post added at 10:51 AM ---------- Previous post was at 10:37 AM ----------
deepakuklan said:
Another way to install twrp if you have stock ROM , if yes then replace recovery.img in stock ROM with twrp recovery.img then full flash phone . Phone will unlock .
I am also try on another phone , but I have no stock ROM this phone .
Click to expand...
Click to collapse
Typically, a locked bootloader won't allow this to work, the locked bootloader will see that the TWRP.img is not your stock recovery and won't allow it to boot.
Sent from my LGL84VL using Tapatalk
First of all, you guys try to root this phone, I am trying with magisk patched Boot img.
Pls share your views on this, unless our device won't be developed.
Also I am trying to port twrp, wish me luck .!!✓