Database Develop

[Q] My TX screen upside down!!

I tried to fix it by flash the orginal TFT with flashtool but it's still can't not work...
{
"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"
}
Is the touch firamware problem?
Anybody know how can I fix it?
Thanks for help

Repair using pccompanion
Sent from my LT30p using xda premium

gregbradley said:
Repair using pccompanion
Sent from my LT30p using xda premium
Click to expand...
Click to collapse
When I use the PPC to repair it will appear
problem
"The phone include the software that can't modify and update"
detail:
"The update service of Sony is fail (error:2003)"
I tried to translate...hope my english is ok...
My phone has no root and locked...

skylovely2005 said:
When I use the PPC to repair it will appear
problem
"The phone include the software that can't modify and update"
detail:
"The update service of Sony is fail (error:2003)"
I tried to translate...hope my english is ok...
My phone has no root and locked...
Click to expand...
Click to collapse
goto phone and dial
*#*#7378423#*#* and goto service info / configuration and tell me what it says in the last line under "bootloader status"

gregbradley said:
goto phone and dial
*#*#7378423#*#* and goto service info / configuration and tell me what it says in the last line under "bootloader status"
Click to expand...
Click to collapse
It's look like this

You have unlocked your bootloader (Even though you say you haven't) that's why pccompanion wont work
Flash the relock ftf for your phone then repair using pccompanion. (Find the FTF file here)
Or find the correct ftf for your phone and flash it in flashtool.
PS (Can you tell me the link for the ftf you tried to flash, this problem normally happens when people flash a T ftf on a TX or vice versa)

gregbradley said:
You have unlocked your bootloader (Even though you say you haven't) that's why pccompanion wont work
Flash the relock ftf for your phone then repair using pccompanion. (Find the FTF file here)
Or find the correct ftf for your phone and flash it in flashtool.
PS (Can you tell me the link for the ftf you tried to flash, this problem normally happens when people flash a T ftf on a TX or vice versa)
Click to expand...
Click to collapse
My TFT is download in another forum...
and the name is "LT29i_9.1.B.1.67_1266-5825-R2I.ftf",
I don't know when do I unlocked my bootloader= =..
but I have download the relock ftf ,
let me try PPC =)
thanks you

You unlocked your bootloader when you went to the sony website and followed the instructions on how to unlock our bootloader.
Unless, you got the phone second hand then you must have done it, because they are not sold with unlocked bootloaders.
Let me know if it works when you have repaired with pccompanion

gregbradley said:
You unlocked your bootloader when you went to the sony website and followed the instructions on how to unlock our bootloader.
Unless, you got the phone second hand then you must have done it, because they are not sold with unlocked bootloaders.
Let me know if it works when you have repaired with pccompanion
Click to expand...
Click to collapse
It's still have same problem..
The screen still upside down ><
I have flash this rom this morning
http://forum.xda-developers.com/showthread.php?t=2407313
and try to use this patch
http://forum.xda-developers.com/showthread.php?t=2268401
then the screen is upside down...
I tried everything I can do and then no ussful =(

skylovely2005 said:
It's still have same problem..
The screen still upside down ><
Click to expand...
Click to collapse
goto phone and dial
*#*#7378432#*#* and goto service info / model info and tell me what it says there

gregbradley said:
goto phone and dial
*#*#7378432#*#* and goto service info / model info and tell me what it says there
Click to expand...
Click to collapse
I can't not get in to engineer mode= =...
Let me tried later...QQ

OK.
I suggest you redownload a TX FTF (Find one in the all in one thread) and flash it again in flashtool making sure you wipe everything.

gregbradley said:
OK.
I suggest you redownload a TX FTF (Find one in the all in one thread) and flash it again in flashtool making sure you wipe everything.
Click to expand...
Click to collapse
Model info:
LT29i

There was a problem after applying this patch. Helped only a replacement touchscreen. Flashing did not help.

nnmka said:
There was a problem after applying this patch. Helped only a replacement touchscreen. Flashing did not help.
Click to expand...
Click to collapse
How can I replace my [email protected]@?

In your case, it is better to contact the service center. I no recovery path did not help. Only replacement touchscreen.

nnmka said:
In your case, it is better to contact the service center. I no recovery path did not help. Only replacement touchscreen.
Click to expand...
Click to collapse
Oh no...
It's so sad...
So ti's a hardware's problem...
Thanks for your help ><

This is not a hardware problem and you have not flashed a "patch"
Find a TX FTF from the all in one thread and flash it. Make sure you exclude nothing and wipe everything.
Plus going to service centre is no good because you have voided your warrenty by unlocking the bootloader.

gregbradley said:
This is not a hardware problem and you have not flashed a "patch"
Find a TX FTF from the all in one thread and flash it. Make sure you exclude nothing and wipe everything.
Plus going to service centre is no good because you have voided your warrenty by unlocking the bootloader.
Click to expand...
Click to collapse
I don't flashed the patch anymore when I flashed the TX FTF,
I will try again with this one http://forum.xda-developers.com/showthread.php?p=39842542#post39842542
Thanks for your patient =)
Hope this time can resolve.
p.s If I unlock again they will know I have been unlocked my [email protected]@?

That should be fine,.
They know you have unlocked because
1) You gave them your IMEI number when you unlocked.
2) You have lost your DRM keys.
3) You have altered your TA partition.
Relocking your bootloader does not fix any of these things

[Q] My Xperia V got bricked...

Let me tell you what happened.
I tried to relock my Xperia V (unlocked BL) with latest version of flashtool (v.0.9.16.1) and it seemed successful.
After I unplugged the cable and rebooted my phone (It had a normally working stock FW of 9.2.A.1.120), it stucked right after the SONY logo for some minutes and powered off automatically
And now every time I try to power it on, it does actually the same thing:
1. shows the SONY logo
2. shows 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"
}
and stays for about 5-10 minutes.
3. becomes blank screen and does not try to boot again.
As it could be set to Fastboot Mode and Flash Mode, I also tried to solve it but of no use. Here are my attempts:
1. Using PC Companion or SONY Update Service to repair both results in failure
2. Using Flashtool to flash FTFs gets following error messages
ERROR - ERR_SEVERITY="MAJOR";ERR_CODE="0026";ERR_DYNAMIC="08 : TA flush failed";
3. Also tried to re-unlock the relocked BL...
On the first time of trying after a reboot, the fastboot.exe says: FAILED (remote: oem unlock failed!)
and on the following attempts it keeps telling me: FAILED (remote: Phone is already unlocked!)
(but actually it's still locked)
Now I could neither flash anything into it, nor unlock the BL...
Totally confused about this situation. Would relocking BL brick a phone? Is there any solution to this?
Thank you!

char.c said:
2. Using Flashtool to flash FTFs gets following error messages
ERROR - ERR_SEVERITY="MAJOR";ERR_CODE="0026";ERR_DYNAMIC="08 : TA flush failed";
Click to expand...
Click to collapse
Open up Flashtool, select the FTF you want to flash and check TA inside the "Exclude" box.
Then try to flash...

istux said:
Open up Flashtool, select the FTF you want to flash and check TA inside the "Exclude" box.
Then try to flash...
Click to expand...
Click to collapse
Thank you for replying.
But I've already tried that... same error after flashed loader.sin. I couldn't avoid loader.sin (excluded everything and wiped no data at all, there's still loader.sin left, which leads to the same failure)

char.c said:
Thank you for replying.
But I've already tried that... same error after flashed loader.sin. I couldn't avoid loader.sin (excluded everything and wiped no data at all, there's still loader.sin left, which leads to the same failure)
Click to expand...
Click to collapse
You said you tried to re-lock again, but have you tried to re-unlock again and flash?
I guess the way you relocked just messed up something... all those errors are about a wrong kernel usually...
Anyway your phone is not hard-bricked, but just soft-bricked... and this problem seems to be new here

istux said:
You said you tried to re-lock again, but have you tried to re-unlock again and flash?
I guess the way you relocked just messed up something... all those errors are about a wrong kernel usually...
Anyway your phone is not hard-bricked, but just soft-bricked... and this problem seems to be new here
Click to expand...
Click to collapse
Yes, tried to re-unlock, but failed......:crying:
char.c said:
3. Also tried to re-unlock the relocked BL...
On the first time of trying after a reboot, the fastboot.exe says: FAILED (remote: oem unlock failed!)
and on the following attempts it keeps telling me: FAILED (remote: Phone is already unlocked!)
(but actually it's still locked)
Click to expand...
Click to collapse

istux said:
You said you tried to re-lock again, but have you tried to re-unlock again and flash?
I guess the way you relocked just messed up something... all those errors are about a wrong kernel usually...
Anyway your phone is not hard-bricked, but just soft-bricked... and this problem seems to be new here
Click to expand...
Click to collapse
I just followed a guide about using Flashtool to relock BL...
And other people who also used Flashtool to relock their phones did not face the same problem... That's why I'm totally confused. I cannot figure out what went wrong during the relock process.

char.c said:
I just followed a guide about using Flashtool to relock BL...
And other people who also used Flashtool to relock their phones did not face the same problem... That's why I'm totally confused. I cannot figure out what went wrong during the relock process.
Click to expand...
Click to collapse
The best way to relock is restoring a TA backup, that has to be done before unlocking the first time.
If you didn't backup TA, then you lost your DRM keys forever.
So you relocked using Flashtool. Right?
What guide did you follow? Give me the link, please.
I hope you didn't flash BLRelock for X10

istux said:
The best way to relock is restoring a TA backup, that has to be done before unlocking the first time.
If you didn't backup TA, then you lost your DRM keys forever.
So you relocked using Flashtool. Right?
What guide did you follow? Give me the link, please.
I hope you didn't flash BLRelock for X10
Click to expand...
Click to collapse
I didn't know anything about TA backup when I unlocked my phone.
So I'm not able to relock like that.
Here's the guide I followed. I didn't flashed that X10 relock TFT.
http://forum.xda-developers.com/showthread.php?p=45653511#post45653511

char.c said:
I didn't know anything about TA backup when I unlocked my phone.
So I'm not able to relock like that.
Here's the guide I followed. I didn't flashed that X10 relock TFT.
http://forum.xda-developers.com/showthread.php?p=45653511#post45653511
Click to expand...
Click to collapse
I know you didn't make a TA backup.
With your next xperia device, remember to do it
The guide you followed is right and comes from a very reliable developer.
According to all steps you did, I think you have nothing more to try... you did all what has to be done in this case.
Try to download another FTF, maybe yours is corrupted. But I don't think so actually (because also SONY Update Service repair didn't work).
I mean, your device behaviour is weird and no-sense.
Something is broken if you can't work with kernel partition.
Maybe your motherboard is fried
When we play with an unlocked bootloader, this can happen sometimes.
The problem is that your warranty is lost if sony repair center realizes that it was unlocked.
Sorry if I can't help you out further. :crying:
Good luck anyways

istux said:
I know you didn't make a TA backup.
With your next xperia device, remember to do it
The guide you followed is right and comes from a very reliable developer.
According to all steps you did, I think you have nothing more to try... you did all what has to be done in this case.
Try to download another FTF, maybe yours is corrupted. But I don't think so actually (because also SONY Update Service repair didn't work).
I mean, your device behaviour is weird and no-sense.
Something is broken if you can't work with kernel piartition.
Maybe your motherboard is fried
When we play with an unlocked bootloader, this can happen sometimes.
The problem is that your warranty is lost if sony repair center realizes that it was unlocked.
Sorry if I can't help you out further. :crying:
Good luck anyways
Click to expand...
Click to collapse
Well, thanks anyway.
Having tried for over 10 hrs to repair it and failed, I'll send it to repair tomorrow. Hope the fee won't be too high
At least no higher than a new phone

Can you plz tell me if I doing the right steps?

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.

Have boot and recovery stock. Need CWM port help

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...

X50 RMX2144 Bootloader access

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.