i took my note 3 back to 4.4.2 and got the root on it and pulled and unpacked the boot and recovery img with carliv kitchen (http://forum.xda-developers.com/and...wm-based-recovery-t2973804/page8#post68550781)
I am following that guide. This is my first go at building a recovery and, hopefully, eventually a rom.
Just testing my feet before i jump into working on my note 4 and note 5. *im a samsung guy... all samung are belong to me... lol*
im stuck at the part where he is talking about building the fstab and init.rc.
not sure if this needs to be custom or not. I just want to create a stock rom with CWM recovery. Thats all. Can i just unpack the the stock recovery and boot and shove the CWM custom stuff in and repack it?
thanks for the help
Since the n900a has a locked bootloader, would cwm or twrp be possible?
don't really know if its locked... since i pulled the boot and recovery and it its flashable via odin....
I am having more issues with the basics of building here. not really the full application of the build.
if the boot loader was locked the why was i able to downgrade it? it was running 5.0 now on 4.4.2 and rooted.
don't know if others were not able to do the same but... really just need help understanding the next steps in building the custom recovery.
Even though the bootloader is locked, it may allow a downgrade to 4.4.2 from 5.0. Downgrading the bootloader doesn't automatically mean TWRP or CWM can be flashed to the phone.
People whose phone have a locked bootloader are using safestrap to flash the 900a.
audit13 said:
Even though the bootloader is locked, it may allow a downgrade to 4.4.2 from 5.0. Downgrading the bootloader doesn't automatically mean TWRP or CWM can be flashed to the phone.
People whose phone have a locked bootloader are using safestrap to flash the 900a.
Click to expand...
Click to collapse
well if it helps... i have a unlocked symbol and the word custom that show on the screen when it boots up.
This is kinda irregardless. I can emulate the test... that isn't an issue. I want to work on the basics of building... so my question isn't about the boot loader being locked or not.
I have the Boot.img and the Recovery.img on my local machine, unpacked with carliv kitchen. i just need to know what i need to copy over or what needs to be completely customized by hand. I am really new to the process of creating a custom recovery.
I'll worry about the flashing to device later.
It's my understanding that TWRP and CWM cannot be flashed to a phone with a locked bootloader which is why there is no TWRP build for this particular Note 3.
I wish you luck in your endeavour as I am sure a lot of users will be happy with something other than safestrap.
audit13 said:
It's my understanding that TWRP and CWM cannot be flashed to a phone with a locked bootloader which is why there is no TWRP build for this particular Note 3.
I wish you luck in your endeavour as I am sure a lot of users will be happy with something other than safestrap.
Click to expand...
Click to collapse
you keep talking about the boot loader but never even mention my question. my question has nothing to do with the boot loader or flashing the device.
I am asking about building. not the bootloader... this question is indifferent to even the phone i am on.
I am stuck on the instructions. I am just trying to figure out all the stuff that would need to be copied to the build device tree recovery/root. This should be standard in all phones or devices... I need to know what it is that makes the CWM recovery custom. are there files i need to replace with the original files. my original post has the link in the guide i am following. so if anyone can help answer that question i would appreciate it.
but thank you for the luck... it looks like i need it just to get somebody to answer some basic building questions.
I mention the bootloader because that seems to have been a stumbling block for users that want to use twrp to flash ROMs.
I will be the first to admit that I don't know anything about building twrp.
I will bow out now and leave you to your task.
Thanks for replying to my posts.
Building cwm I can't help you with. But cwm for note 3 att is useless. You can't flash it. Who uses cwm these days? Twrp isn't a preference it's the only real option anymore other than adb and fast boot.
Sent from my DROID Turbo using XDA-Developers mobile app
Some pics. But is not the point of my question. Please read the question.
Ok... this is going to seem like a noob question.... How can i prove that my bootloader is unlocked.
What would i need to do to prove or disprove it. Is there a log or something. This is literally my first go. Show me why it can't be flashed. I am not seeing the answer to this in any of the instructions.
You can't just say something is locked and that be the end of it. How is it locked. I can get into boot loader.
besides. This is solely to help me learn the basics of building a custom recovery. I have another device I want to work on but thats the device i don't want to brick. I am using this as a testing device to learn. I only want to learn to create the thing... i already know how to install the custom stuff... and to answer the question of who uses it... well... obviously.. me... when I am working on an old device learning the basics and building for android 4.4.2...
I am still working on this.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Even though the bootloader is locked, this does not prevent a user from entering download or recovery mode.
To verify the bootloader version on your phone, you can install and run the Samsung Info App from the Play store.
audit13 said:
Even though the bootloader is locked, this does not prevent a user from entering download or recovery mode.
To verify the bootloader version on your phone, you can install and run the Samsung Info App from the Play store.
Click to expand...
Click to collapse
I got that installed. I am not sure what i am looking for. bootloader version?
Also, if the bootloader isn't unlocked... what does the picture i posted with the unlocked lock with the word custom beneath it mean?
I believe that, starting with a stock 4.3 ROM, the bootloader was locked. Maybe your phone is running an older ROM before AT&T locked the bootloader?
It looks like your bootloader may be unlocked but I'm not 100% sure as I don't have the n900a, I have an n900w8.
A sure fire way to see if the bootloader is locked would be to flash a stock LP ROM to the phone and then try to flash non-officlal software; however, I don't recommend doing this as it may hard brick the phone.
As far as I know, no one has claimed the XDA bounty for unlocking the AT&T Note 3 and S4 bootloader.
http://forum.xda-developers.com/showthread.php?t=2708609
Notice here that there is no mention of TWRP or CWM: http://forum.xda-developers.com/showthread.php?t=2710972
Well. I sent the OP on that post a message as the thread is locked. since july i think?
I think the thread was locked because safestrap is a viable recovery for the n900a.
I believe there is a version of TWRP for the n900a but it can only be installed on a phone without a locked bootloader.
well i sent the OP and the perosn who locked the thread... Ironically... the guy that locked the bootloader lives about 30 minutes from me...
I wish that more people would see this thread... or perhaps someone could just help me out with the building part... I have figured out most of it.... im just having a hard time understanding some of the small concepts.. what files need to be changed and what files need to be left alone.
therealtaynak said:
well i sent the OP and the perosn who locked the thread... Ironically... the guy that locked the bootloader lives about 30 minutes from me...
I wish that more people would see this thread... or perhaps someone could just help me out with the building part... I have figured out most of it.... im just having a hard time understanding some of the small concepts.. what files need to be changed and what files need to be left alone.
Click to expand...
Click to collapse
Yep that phone still has a locked bootloader
Ok... My question was about building anyway... i don't really care about flashing it... I am only using it because i am trying to learn the building process...
Related
Gentlemen,
I brought a brand new, unlocked ATT MotoX to a friend out of the country, only to find out that the ATT version only has 4 languages compiled into it (ridicolous).
I've done some research and it seems like flashing the VZW ROM on the phone should do the trick (right?).
I've put the phone in fastboot and selected "recovery". After seeing the little Android image with "no command", I held the volume up button for about 6 seconds, followed by a tap of the power button (while still holding the volume button). It gave me the selection screen.
I picked "apply update from sdcard" and selected the "VZW_XT1060_4.4.2-KXA20.16-1.25.2_CFC_1FF.xml.zip" file I downloaded from here.
Here's the result:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Guys, my friend's English is not good. He needs the OS to be in his native language.
I am leaving town soon and would like to get the issue resolved and return the phone to him with all the languages, and able to work with non-US SIM Cards. Can you point me in the right direction? It will help us save time, since it's running fast.
Thanks in advance!
You can't flash AT&T phones with VZW firmware directly. You need to "port" the VZW firmware to the other model.
Sent from my Moto X
imnuts said:
You can't flash AT&T phones with VZW firmware directly. You need to "port" the VZW firmware to the other model.
Click to expand...
Click to collapse
Thanks man.
I am reading threads that explain porting, but it seems like a steep learning curve, at least for the limited time I have at my disposal before departure.
I'll continue reading and try to figure this out. I am following this guide. I will report back if I encounter any issues.
In the mean time, if someone knows of a pre-ported VZW ROM that would work in my case - or - of a better guide to follow, please let me know, it would be immensely appreciated.
Cheers!
Ok, 1st issue: I extracted the Zip archives of both ROMs (ATT stock and VZW). Inside the archives is a few ".img", ".bin" files, one ".mbn" and one ".xml" file. I assume the directories and files mentioned in the guide are in the system.img file (1.1GB), correct? Should I extract it and work on those, or is there a better way?
IlChengis said:
Gentlemen,
I brought a brand new, unlocked ATT MotoX to a friend out of the country, only to find out that the ATT version only has 4 languages compiled into it (ridicolous).
I've done some research and it seems like flashing the VZW ROM on the phone should do the trick (right?).!
Click to expand...
Click to collapse
Fist question... Is the ATT XT1058 you have SIM Unlocked or Bootloader unlocked?
SIM unlocking allows you to use the SIM from another carrier in your phone.. i.e. use a T-Mobile sim in an ATT branded X. That process does require you to have a different carrier's sim so the phone will prompt you to enter the unlock code. SIM unlock codes are available from many places around the web. It has no impact on rooting.
Bootloader unlocking allows you to flash a custom recovery, 3rd party roms, etc. By virtue of being able to flash a custom recovery you can easily root your phone. When it comes to the ATT XT1058 there is only only one place you can get a bootloader unlock code.. the Chinese Middleman (not as reliable as it once was, there is a BIG thread discussing it already).
If you are NOT bootloader unlocked, you will not be able to flash anything but the ATT XT1058 rom on that phone, no matter what you try. You will not be able to fully root and can not disable write protection once you have 4.4.2 on the phone.
As for adding languages, I thought there was another way, but I also thought that needed root and write protection disabled too.
---------- Post added at 03:15 PM ---------- Previous post was at 03:10 PM ----------
IlChengis said:
I am reading threads that explain porting, but it seems like a steep learning curve, at least for the limited time I have at my disposal before departure.
I'll continue reading and try to figure this out. I am following this guide. I will report back if I encounter any issues.
Click to expand...
Click to collapse
And you'll need an unlocked bootloader to flash the ported rom you make if you follow those instructions.. (since it says you're ready to flash via CWM... and you can't flash CWM, TWRP or other custom recovery to the phone unless the bootloader is unlocked)
Edit: this is the other thread for adding languages.. basically its suggesting flashing the VZW ROM and then your modem files for your device -> http://forum.xda-developers.com/moto-x/moto-x-qa/how-to-add-languages-to-moto-x-t2437807 which again needs unlocked bootloader.
Hey bud, thanks for taking the time to help me out and explain.
KidJoe said:
Fist question... Is the ATT XT1058 you have SIM Unlocked or Bootloader unlocked?
Click to expand...
Click to collapse
I'm not entirely sure, but I'd venture to say that it's SIM Unlocked.
Is there a quick way to tell for sure?
If it turns out being bootloader LOCKED, we're pretty much screwed then, right?
Thanks again man.
IlChengis said:
Hey bud, thanks for taking the time to help me out and explain.
I'm not entirely sure, but I'd venture to say that it's SIM Unlocked.
Is there a quick way to tell for sure?
Click to expand...
Click to collapse
Boot the phone into Fastboot/Bootloader mode (see -> http://mark.cdmaforums.com/MotoX-BootloaderMode.htm ) The status code will be there.
If you have an ATT XT1058, they are shipped Bootloader locked, and the only way to unlock them is to use the Chinese web site or Middeman selling the codes. So unless you bought the phone USED from someone who already did this, its bootloader is locked.
IlChengis said:
If it turns out being bootloader LOCKED, we're pretty much screwed then, right?
Click to expand...
Click to collapse
Pretty much, unless you don't mind voiding your phone's warranty, and then depending on the age of the phone, see the Chinese Middlman thread to buy a BOOTLOADER unlock code..
I've not tried to add languages to my phone, so I can't help you to do it. Just that based on the quick searches I've done, the results have always needed the phone's bootloader unlocked.
Hi,
How are you?
I want to do "back to rom stock" + re-lock the bl.
Before the procedure I want to be sure that I'm doing the right steps - so, can you please approve that?
1. Downloading the recent "shamu" image (6.0.1 (MOB30W) and Extract directly to Platform-tools folder these:
- shamu-XXXXX.tgz
- shamu-XXXXX.tar
2. Open the CMD from Platform-tools folder and start typing 1 by 1:
- fastboot flash system system.img
- fastboot flash boot boot.img
- fastboot flash recovery recovery.img
- fastboot flash cache cache.img
- fastboot flash userdata userdata.img
- fastboot reboot
Is this process completely bring the N6 back to Google rom stock + re-lock the bootloader?
Thanks for your time & help!
http://forum.xda-developers.com/nexus-6/general/guide-flash-factory-images-nexus-6shamu-t2954008
And don't lock you bootloader, or at least leave it unlockable, unless you want to sell it. Google can brick it with an OTA.
Hi @istperson
1) You guess it correctly - I do want to sell it.
(It would be better just to relock and thats it?)
Why would Google's OTA will brick it while it exactly back to stock without root?
2) Can you plz review my 1st message here to tell me if everything is correct?
3) For some reasson (maybe Win10 upgrade) the drivers are not working anymore('fastboot devices' dose not showing anything)
Setting the driver is one of those things that could make me crazy...:cyclops:
Is there a tool that just do everthing by itself? (i'm not talking about flash tools that guides you).
Thanks a lot!
shabydog said:
Hi @istperson
1) You guess it correctly - I do want to sell it.
(It would be better just to relock and thats it?)
Why would Google's OTA will brick it while it exactly back to stock without root?
2) Can you plz review my 1st message here to tell me if everything is correct?
3) For some reasson (maybe Win10 upgrade) the drivers are not working anymore('fastboot devices' dose not showing anything)
Setting the driver is one of those things that could make me crazy...:cyclops:
Is there a tool that just do everthing by itself? (i'm not talking about flash tools that guides you).
Thanks a lot!
Click to expand...
Click to collapse
No, your steps are not correct. Follow the steps in the link that was provided in post 2.
Any tool would still have to have the drivers properly setup and adb working. The nexus is one of the easiest devices to restore to stock. But there is no magic wand.
shabydog said:
Why would Google's OTA will brick it while it exactly back to stock without root?
Click to expand...
Click to collapse
If you want to lock it, then leave it as a last step when everything else worked. And the phone is completely back to stock, and booted up okay, and everything.
And Google made a couple of ugly mistakes in OTA-s, and the phones bootlooped. And yes they were not rooted, they were completely stock, because otherwise the OTA wouldn't have installed.
@ktmom
I posted this AFTER I MADE A RESEARCH all over...So please believe me that I need help (maybe bc's it's harder for me with much of information).
Please try to do your best to help me here bc's I been lost (and I know a bit or more in this)
Thanks.
@istperson
So, if i completely proceed with the all the necessary commands it will also relock the BL.
Do you think that it's better to NOT relock it (but if these commands doing that...)?
Thanks!
shabydog said:
@istperson
So, if i completely proceed with the all the necessary commands it will also relock the BL.
Do you think that it's better to NOT relock it (but if these commands doing that...)?
Thanks!
Click to expand...
Click to collapse
The bootloader is locked with the "fastboot oem lock" command.
If you're selling it then put it back to the original factory state. Without WiFi and sim card it will not receive updates. So let the new owner decide it he or she will unlock it or not.
Just don't lock it before you checked it boots.
Sent to another responce below
The updated replay bellow (found a method of "flash-all" script)
Hope to get an answer to this...
1) Found this (attached iamge), think it solve my question, right?
2) Drivers: I made a test - booted the n6 to BL and typed from the folder of the platform-tools: adb devices which gave me combination of numbers+letters ending with 'device'.
Guess that mean that the drivers are setted?
3) Heard something about that it's NOT recommanded to flash the rom stock bc's if the user doing an OTA it will brick the device?
So it better not proceed the 'fastboot oem lock'?
Anyone knows about it?
Thank you!
adb works in normally booted phone and in recovery. In bootloader mode you use fastboot.
Stock images won't brick your device, but an OTA might. Don't use OTAs, flash manually the updates. But you said you want to sell the phone, then flash stock, lock it, and sell it.
istperson said:
adb works in normally booted phone and in recovery. In bootloader mode you use fastboot.
Stock images won't brick your device, but an OTA might. Don't use OTAs, flash manually the updates. But you said you want to sell the phone, then flash stock, lock it, and sell it.
Click to expand...
Click to collapse
I followed by this tut )just without the last stage of unlocking bootloader:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You do realize that if you followed the directions in post #2 given to you 6 days ago, you would have been done? I'm certainly not going to rehash here what's been perfectly described in that thread.
Hi,
Eventually I used the Nexus Toolkit and Flashed +Unroot sucssesfuly.
Can you plz reminde me - I did not got that: Should I leave the BL unlocked to avoid BRICK or opposite?
Thanks!
You want to keep it or sell it? If you want to sell it then lock it.
Hello guys!
So..today i tried to unlock my G6 Plus' bootloader and ended up doing so but i got an error when booting the phone with the following "Device has loaded a different operating system" and then i tried to flash the Stock Firmware and succeded in doing so, but the error was still there.
After this i locked the bootloader again but still the error is there and In the End i tried to flash the Stock Firmware again but the bootloader was locked and i ended up bricking the phone.
Now i tried everything the whole day to make it work again but no success at all.
PS: OEM Unlock is unticked so i cant unlock the bootloader...basically i cant flash anything on my G6 Plus.
Can you please help me guys in getting my phone working again? I tried like everyting but with OEM Unlock unticked and Bootloader Locked i can't really get it working.
Thank you in advance!
Dan.
Thank you in advance guys! Hope you can help me!
Can you still boot in the bootloader?
Thomas Hunter said:
Can you still boot in the bootloader?
Click to expand...
Click to collapse
Yes, bootloader is working fine.
Just Recovery isnt working, it goes in but wont load menu.
You're not hard bricked if bootloader works. Unlock bootloader and try flashing stock firmware again. I've run in to this issue a few times. Nothing to worry about in the end.
Sent from my moto g(6) plus using Tapatalk
Xplorer4x4 said:
You're not hard bricked if bootloader works. Unlock bootloader and try flashing stock firmware again. I've run in to this issue a few times. Nothing to worry about in the end.
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
OEM unlock is unticked so... I cant really unlock the bootloader..
The switch itself does nothing. Unlock the bootloader and flash stock. When it is locked you are unable to modify system partition.
Sent from my moto g(6) plus using Tapatalk
Xplorer4x4 said:
The switch itself does nothing. Unlock the bootloader and flash stock. When it is locked you are unable to modify system partition.
Sent from my moto g(6) plus using Tapatalk
Click to expand...
Click to collapse
I tried to unlock it but i always got an error, something like "go to Settings and activate OEM Unlock" or something like this..
Could you provide a image
Thomas Hunter said:
Could you provide a image
Click to expand...
Click to collapse
Sure!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
TrueGodFlow said:
Hello guys!
So..today i tried to unlock my G6 Plus' bootloader and ended up doing so but i got an error when booting the phone with the following "Device has loaded a different operating system" and then i tried to flash the Stock Firmware and succeded in doing so, but the error was still there.
After this i locked the bootloader again but still the error is there and In the End i tried to flash the Stock Firmware again but the bootloader was locked and i ended up bricking the phone.
Now i tried everything the whole day to make it work again but no success at all.
PS: OEM Unlock is unticked so i cant unlock the bootloader...basically i cant flash anything on my G6 Plus.
Can you please help me guys in getting my phone working again? I tried like everyting but with OEM Unlock unticked and Bootloader Locked i can't really get it working.
Thank you in advance!
Dan.
Thank you in advance guys! Hope you can help me!
Click to expand...
Click to collapse
Hi, Dan...
I really do wish I had some good news to impart, but sadly I suspect your Moto G6 Plus is probably not recoverable.
The OEM Unlocking setting in Developer Options is part of Googles Factory Reset Protection scheme. Ostensibly, it's designed to prevent lost or stolen devices from being reflashed back to stock and dishonest individuals then claiming the device as their own.
I ran afoul of this myself, four years ago, with my (then) new Nexus 9 tablet which originally shipped with Android 5, Lollipop and it was the first device I'd owned that required OEM Unlocking to be enabled in Developer Options before the bootloader could be unlocked.
I won't bore you with the details here, but if you have a mind to, you can read about my thwarted endeavours to resurrect my Nexus 9 here...
https://forum.xda-developers.com/nexus-9/help/warning-locking-bootloader-disabling-t2951312
Fortunately, my Nexus 9 was still new, and I had a no-quibble warranty that I'd paid extra for, so I was able to get it replaced at the store from which I'd bought it.
-----------------------------------------
Around 2015 a solution (of sorts) was eventually found for this problem, for both the Nexus 6 phone and the Nexus 9 tablet, however it required a very specific set of criteria for it to work.
The OEM Unlocking setting in Developer Options flips a binary state flag, from either ON (Enabled) or OFF (Disabled) and it's stored in a special Persistent (PST) partition, which doesn't get touched when factory resetting the device, when receiving OTA updates or when reflashing it. As the name suggests, it 'persists'.
So it required somebody to create a dump image file of the PST partition with the OEM Unlocking flag already set to ENABLED on their device. This dump image file would be created by using a <dd, if, of> command in a terminal shell.
The person whose device was semi-bricked, would download this dump image file of the PST partition, and flash it to their device using a similar <dd, if, of> shell command, via ADB in TWRP Custom Recovery. This would overwrite their PST partition, where the OEM Unlocking flag is NOT enabled...
...with a version where it IS enabled, and consequently fastboot flash commands would then work.
*****
It required root on both devices, and TWRP custom recovery to be already flashed on the semi-bricked device, since ADB shell commands can not be run in the normal stock recovery.
You can read about the technical details here...
https://forum.xda-developers.com/nexus-6/help/info-nexus-6-nexus-9-enable-oem-unlock-t3113539
-----------------------------------------
Theoretically, the method detailed above could perhaps be adapted for the Moto G6 Plus ~ you'd just need to find somebody with an already rooted Moto G6 Plus prepared to create a dump image file of their PST partition, with the OEM Unlocking setting enabled, and your G6 Plus would also need to be able to boot into TWRP to run the necessary ADB shell command to flash it.
And which is impossible, since (due to your locked bootloader) you can't either remotely boot TWRP from a laptop using fastboot boot twrp.img or flash it directly using fastboot flash recovery twrp.img
As I say, I wish I had better news for you.
-----------------------------------------
I hope all of the above makes sense; it is a little technical.
If I have any ideas that may be helpful, I'll post them here. But as it stands right now, and knowing what I know about this topic, I'm not optimistic there is a solution to your problem.
Ged.
The only other thing I can think of that may or may not work is a blankflash. Search the forums for it.
Sent from my moto g(6) plus using Tapatalk
You don't need to unlock oem as I got the same problem a year ago with my moto g5 plus so basically what I did was keep trying to flash a different fimware and eventually it worked with installed a firmware with oem locked.
Hi
I'm looking for a method to access bootloader on the RMX2144 model (European version I think).
The in-depth app does not work, the model is not supported by the application.
I tried to run adb reboot bootloader but the phone reboot, show a message during half a second and then restart.
Can someone help me ?
Thanks in advance
EDIT : Here is the displayed message
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
In english :
Has entered Fastboot
Long press the power button for 6~10 seconds or reload the battery to exit
useless
xam666 said:
Hi
I'm looking for a method to access bootloader on the RMX2144 model (European version I think).
The in-depth app does not work, the model is not supported by the application.
I tried to run adb reboot bootloader but the phone reboot, show a message during half a second and then restart.
Can someone help me ?
Thanks in advance
EDIT : Here is the displayed message
In english :
Has entered Fastboot
Long press the power button for 6~10 seconds or reload the battery to exit
Click to expand...
Click to collapse
Im having the same problem here with my rmx2025 (China model) Im really sad i cant install custom roms on this phone
ROM_gamer987 said:
Im having the same problem here with my rmx2025 (China model) Im really sad i cant install custom roms on this phone
Click to expand...
Click to collapse
Mine is RMX2025 as well. If you can unlock bootloader, please share the method. Thanks in advance.
siamese007 said:
Mine is RMX2025 as well. If you can unlock bootloader, please share the method. Thanks in advance.
Click to expand...
Click to collapse
Sadly i don't think there is a method method for this phone, i asked in the Chinese forums and I'm waiting for a response
ROM_gamer987 said:
Sadly i don't think there is a method method for this phone, i asked in the Chinese forums and I'm waiting for a response
Click to expand...
Click to collapse
Thank you for your quick reply. I will wait for your future solution hopefully.
I did everything about unlock bootloader from Chinese post but the depth test apk said my phone is not supported! what the....
siamese007 said:
Thank you for your quick reply. I will wait for your future solution hopefully.
I did everything about unlock bootloader from Chinese post but the depth test apk said my phone is not supported! what the....
Click to expand...
Click to collapse
yea same for me, its very weird lets just hope someone finds something, I have managed to go on QDL (QUALCOMM usb flash mode) I think with the right tools twrp could be installed from there without even unlocking the bootloader, for now we just have to wait
ROM_gamer987 said:
yea same for me, its very weird lets just hope someone finds something, I have managed to go on QDL (QUALCOMM usb flash mode) I think with the right tools twrp could be installed from there without even unlocking the bootloader, for now we just have to wait
Click to expand...
Click to collapse
I am not sure if installing TWRP without unlocking bootloader will be useable for installing Custom ROMs or GSI ROMs. Without unlocking bootloader, installing these Custom ROMs may brick the phone. :crying::crying::crying:
Well I will keep looking for the solution for this also. Thanks for the update. :highfive:
ROM_gamer987 said:
yea same for me, its very weird lets just hope someone finds something, I have managed to go on QDL (QUALCOMM usb flash mode) I think with the right tools twrp could be installed from there without even unlocking the bootloader, for now we just have to wait
Click to expand...
Click to collapse
Hello Bro,
There is a link here on XDA that explains how to unlock bootloader.
I just sold my phone so I don't have one to try. Please try this if this works on your RMX2025. If the app works on your model, then I will order the new X50 5G to unlock bootloader.
By the way, have you heard any updates from Chinese post for the problem unlocking bootloader?
I am looking for a solution to unlock bootloader on RMX2025.
:highfive:
The problems of unlocking the bootloader come because they are rmx2025?
The RMX2144 can be unlocked with the realme apk? He has problems? Is there a bootlop?
The only solution would be to access the recovery and install a rom for otg?
Thanks friends
totmakina said:
The problems of unlocking the bootloader come because they are rmx2025?
The RMX2144 can be unlocked with the realme apk? He has problems? Is there a bootlop?
The only solution would be to access the recovery and install a rom for otg?
Thanks friends
Click to expand...
Click to collapse
My RMX2025 was not supported by the deep testing app for no reason. I have no RMX2144 but my best guess is this model is good to go with the deep testing app.
If you wanna install custom ROMs or GSI, unlocking bootloader is very necessary from my experiences so far. I have never been able to flash Android phones with no unlock bootloader once.
I would not recommend to flash custom ROMs via ADB, this may cause the phone to brick. And while your phone is not unlocked bootloader, unbricking it will be nighmare and hardcore. :crying::crying:
Unlocking boot is essential in order to install twrp or custom roms.
If the smartphone fails and brick, I think it could be restored through an otg installation from recovery stock.
I will risk unlocking the boot with the realme tool on the RMX 2144. If there is success I will comment on it
Thanks!
totmakina said:
Unlocking boot is essential in order to install twrp or custom roms.
If the smartphone fails and brick, I think it could be restored through an otg installation from recovery stock.
I will risk unlocking the boot with the realme tool on the RMX 2144. If there is success I will comment on it
Thanks!
Click to expand...
Click to collapse
Hello Pal,
Any updates for unlocking bootloader for RMX2144? Now I have RMX2144. The phone is great except there is no custom ROMs yet. So sad. :crying::crying:
Edit: If we can unlocking bootloader, we can flash GSIs which are close to specific custom ROMs.
Hi. Friend. Unable to unlock bootloader with the tool. I understand that Realme no longer grants this option. Return the mobile and buy the POCO X3. Tomorrow I will have the permission to open the boot and be able to flash TWRP. Besides, POCO already has custom roms. I intend to install Q LeOs in the bit and not depend on Google services
totmakina said:
Hi. Friend. Unable to unlock bootloader with the tool. I understand that Realme no longer grants this option. Return the mobile and buy the POCO X3. Tomorrow I will have the permission to open the boot and be able to flash TWRP. Besides, POCO already has custom roms. I intend to install Q LeOs in the bit and not depend on Google services
Click to expand...
Click to collapse
Hi friend. Thanks a lot for your updates.
I will probably do the same. :good: For me, I don't mind if there is no Custom ROMs for this phone. As long as I can unlock bootloader I will be able to flash GSI. Xiaomi phones will be my replacement as well.
By the way, RMX2051 can unlocked but there is no Custom ROMs for this phone anyways. :crying:
Laters,
No good news yet so I guess we won't get any custom roms for this unit. To bad for a good phone otherwise but the lack of root/custom rom make me wanna cry, why doesn't realme help the community out. Think I will try to make a refund and get a xiaomi 10 lite or a poco instead.
Hi!
As you may know Honor is pretty restricted in modding.
I AM NOT RESPONSIBLE FOR ERRORS/BRICKED DEVICES'
THIS JUST GIVES AN IDEA ON WHAT TO DO AND IF YOU SHOULD BUY( I don't recommend for modding)
EDIT: IT SEEMS LIKE WE CANT UNLOCK THE BL
There are no recoveries yet
So we need boot.img to root with magisk
But Honor/Other websites does not provide firmware
So we need to dump firmware(which I have not done yet) to get boot.img using mtk client or unlocktool (idk if unlocktool is legit)
Then patch boot.img and flash
#YetAnotherPerson said:
Hi!
As you may know Honor is pretty restricted in modding.
I AM NOT RESPONSIBLE FOR ERRORS/BRICKED DEVICES'
THIS JUST GIVES AN IDEA ON WHAT TO DO AND IF YOU SHOULD BUY( I don't recommend for modding)
There are no recoveries yet
So we need boot.img to root with magisk
But Honor/Other websites does not provide firmware
So we need to dump firmware(which I have not done yet) to get boot.img using mtk client or unlocktool (idk if unlocktool is legit)
Then patch boot.img and flash
Click to expand...
Click to collapse
Hi! Thanks for requesting this page!
For anyone considering buying this phone, just like OP said, DON'T buy if you want to MOD it in any way!
Also, if anyone has any information on this phone, like the firmware, exploits, etc. PLEASE share it since this device is not even that known in XDA.
Sad update, I backed up my Linux computer to install windows and use many apps to retrieve stock firmware for rooting and when device gets bricked, but no success, and I installed Linux again. I did not dual boot because of storage issues
Our hope is not fully lost.
We could flash a rooted GSI.
But I just don't want to risk it as there is no way to return back to the stock firmware if something goes wrong or some features don't work(that's sometimes how GSI's are
#YetAnotherPerson said:
Our hope is not fully lost.
We could flash a rooted GSI.
But I just don't want to risk it as there is no way to return back to the stock firmware if something goes wrong or some features don't work(that's sometimes how GSI's are
Click to expand...
Click to collapse
But wouldn't we need to at least unlock the bootloader to flash anything?
JoeBro19 said:
But wouldn't we need to at least unlock the bootloader to flash anything
Click to expand...
Click to collapse
There is a bootloader unlock option in settings, developer options
#YetAnotherPerson said:
There is a bootloader unlock option in settings, developer options
Click to expand...
Click to collapse
That's only an option to allow the device to be unlocked, but it doesn't unlock it per se. That's done in fastboot mode or similar where you enter a code to unlock it, but Huawei/Honor stopped giving those codes years ago, that's why it's so difficult to do anything to these phones...
JoeBro19 said:
That's only an option to allow the device to be unlocked, but it doesn't unlock it per se. That's done in fastboot mode or similar where you enter a code to unlock it, but Huawei/Honor stopped giving those codes years ago, that's why it's so difficult to do anything to these phones...
Click to expand...
Click to collapse
Hi!
Do you know any way to check if the bootloader is unlocked other than the phone and fastboot method(those don't work for me). I think I did unlock the bootloader, here is what I did:
1. I typed "fastboot flashing unlock"
2. THAT BRICKED MY PHONE
3. I booted into recovery and did a factory reset
4. Did my usual setup again
5. I just went into settings(developer options) and the OEM unlock toggle was enabled without me touching it!
#YetAnotherPerson said:
Hi!
Do you know any way to check if the bootloader is unlocked other than the phone and fastboot method(those don't work for me). I think I did unlock the bootloader, here is what I did:
1. I typed "fastboot flashing unlock"
2. THAT BRICKED MY PHONE
3. I booted into recovery and did a factory reset
4. Did my usual setup again
5. I just went into settings(developer options) and the OEM unlock toggle was enabled without me touching it!
Click to expand...
Click to collapse
You can check by entering fastboot/bootloader mode and it'll say if the phone (bootloader) is locked or unlocked.
You can enter the bootloader by using adb and entering "adb reboot bootloader" and after you get restarted into the bootloader it'll tell you the status on the bottom of the screen.
I have that OEM unlock toggled on and as it still says "Phone Locked" in the bootloader, just as I said that toggling that option doesn't actually unlock it.
JoeBro19 said:
You can check by entering fastboot/bootloader mode and it'll say if the phone (bootloader) is locked or unlocked.
You can enter the bootloader by using adb and entering "adb reboot bootloader" and after you get restarted into the bootloader it'll tell you the status on the bottom of the screen.
I have that OEM unlock toggled on and as it still says "Phone Locked" in the bootloader, just as I said that toggling that option doesn't actually unlock it.
Click to expand...
Click to collapse
Thanks!
While I did not make any progress, atleast I found out I wasted my time "unlocking" the BL and still nothing happened. Just to confirm that the phone locked thing does change when BL in unlocked, I checked a yt video on someone flashing a GSI on an older honor device and it does say "phone unlocked" for them.
Let me explain a bit more on what happened on the BL unlock attempt:
1.I did fastboot flashing unlock in adb which should unlock the BL
2.It put me in a menu which had an option to unlock the bootloader and it did say it will void warranty
3. Then it said it was a sucess and then went into another menu asking what to do next (fastboot mode,reboot,and something else) but it glitched and clicking hw buttons did nothing so I rebooted and the device was in a bootloop so I had to reset the device using the recovery
4. In fastboot mode, it still says phone locked
In short: There is a bug preventing BL unlock. I am not sure if Honor devices still need a code to unlock the BL since you said they stopped providing them
#YetAnotherPerson said:
Thanks!
While I did not make any progress, atleast I found out I wasted my time "unlocking" the BL and still nothing happened. Just to confirm that the phone locked thing does change when BL in unlocked, I checked a yt video on someone flashing a GSI on an older honor device and it does say "phone unlocked" for them.
Let me explain a bit more on what happened on the BL unlock attempt:
1.I did fastboot flashing unlock in adb which should unlock the BL
2.It put me in a menu which had an option to unlock the bootloader and it did say it will void warranty
3. Then it said it was a sucess and then went into another menu asking what to do next (fastboot mode,reboot,and something else) but it glitched and clicking hw buttons did nothing so I rebooted and the device was in a bootloop so I had to reset the device using the recovery
4. In fastboot mode, it still says phone locked
In short: There is a bug preventing BL unlock. I am not sure if Honor devices still need a code to unlock the BL since you said they stopped providing them
Click to expand...
Click to collapse
Being an Honor device, it most likely needs a code to unlock it. So I doubt we'll be able to do anything with this phone.
I could try and do a backup before trying what you did to see if it was a just a bug on your phone or if in fact it can't be done at all, which honestly is the most probable case.
I'll try later and let you know if anything happens.
JoeBro19 said:
Being an Honor device, it most likely needs a code to unlock it. So I doubt we'll be able to do anything with this phone.
I could try and do a backup before trying what you did to see if it was a just a bug on your phone or if in fact it can't be done at all, which honestly is the most probable case.
I'll try later and let you know if anything happens.
Click to expand...
Click to collapse
Ok, but
JoeBro19 said:
Being an Honor device, it most likely needs a code to unlock it. So I doubt we'll be able to do anything with this phone.
I could try and do a backup before trying what you did to see if it was a just a bug on your phone or if in fact it can't be done at all, which honestly is the most probable case.
I'll try later and let you know if anything happens.
Click to expand...
Click to collapse
Ok, but I'll give another warning: It's risky and may brick your device like mine and a factory reset from the recovery may be required. I am not respondible if something happens.
I did contact honor customer support but no reply yet
#YetAnotherPerson said:
Ok, but
Ok, but I'll give another warning: It's risky and may brick your device like mine and a factory reset from the recovery may be required. I am not respondible if something happens.
I did contact honor customer support but no reply yet
Click to expand...
Click to collapse
I doubt they'll anything other than "we don't provide those codes anymore"
And yeah I decided to try it anyway and it happened exactly the same as your case. I had to factory reset it to exit the boot loop. Fortunately, I did a backup just before trying it so I was able to restore it and not lose anything; but yeah, things seem to have come to a standstill.
JoeBro19 said:
I doubt they'll anything other than "we don't provide those codes anymore"
And yeah I decided to try it anyway and it happened exactly the same as your case. I had to factory reset it to exit the boot loop. Fortunately, I did a backup just before trying it so I was able to restore it and not lose anything; but yeah, things seem to have come to a standstill.
Click to expand...
Click to collapse
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
#YetAnotherPerson said:
View attachment 5902653
Click to expand...
Click to collapse
Just as I thought.... damn this companies...
So, unless some miracle happens and someone discovers an exploit on the processor or something that allows us to decipher the unlock code, there is absolutely nothing than we can do...
You can only unlock the bootloader on the new Honor at the Honor office. But this is only possible if the Honor employee is your friend.
volkodav1975 said:
You can only unlock the bootloader on the new Honor at the Honor office. The workers there have such smartphones, I have a friend among such workers and he made a request for me in a friendly way. I think that you will not see such a photo anywhere else. Alas, as long as it's useless, I need a custom one Recovery, But I don't know where to get it.
Click to expand...
Click to collapse
Well that's... disappointing... can't believe we have to even consider that. In my case, we don't have those centers, so I'm definitely screwed... good job Honor...