Database Users

Redmi note 3g hard brick fix

i accidentally use the format all+download option in sp tools and flashed the bootloader. now whenever i try to do anything it gives me this error. pls help
-phone will not boot
-no charging led when plugged in
-phone is detected when i plug into pc
{
"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"
}

mysi said:
i accidentally use the format all+download option in sp tools and flashed the bootloader. now whenever i try to do anything it gives me this error. pls help
-phone will not boot
-no charging led when plugged in
-phone is detected when i plug into pc
View attachment 3551440
Click to expand...
Click to collapse
same as you. can anyone help?

scott4 said:
same as you. can anyone help?
Click to expand...
Click to collapse
just download a new recovery rom (the miui 7 ones) and flash it through spflash tools it worked for me:good:

mysi said:
just download a new recovery rom (the miui 7 ones) and flash it through spflash tools it worked for me:good:
Click to expand...
Click to collapse
can you give me the link to download that recovery rom? Thanks!
did you download the rom from below URL?
http://en.miui.com/thread-53193-1-1.html
What steps did you do in order to save your hard brick phone? Thanks!

scott4 said:
can you give me the link to download that recovery rom? Thanks!
did you download the rom from below URL?
What steps did you do in order to save your hard brick phone? Thanks!
Click to expand...
Click to collapse
terribly sorry to keep you waiting, but yes it is the miui 7 one in the link

mysi said:
terribly sorry to keep you waiting, but yes it is the miui 7 one in the link
Click to expand...
Click to collapse
Thanks for your reply. What steps did you do in order to save your phone? I want to follow step by step.

scott4 said:
Thanks for your reply. What steps did you do in order to save your phone? I want to follow step by step.
Click to expand...
Click to collapse
just follow the step exactly on this thread
http://en.miui.com/thread-64425-1-1.html
and make sure to use the miui 7 fastboot rom

Big Thanks..
mysi said:
just download a new recovery rom (the miui 7 ones) and flash it through spflash tools it worked for me:good:
Click to expand...
Click to collapse
Thanks bro, It works.. My phone was live again

hiii
i need ur help. My Redmi note 3g (Mediatek - Global rom) was stuck up at logo. When i tried flashing it using SP flash tool , i got error that "pmt changed for the rom it must be downloaded". Then i have seen some youtube videos and read forums . As per their instruction i have first forrmated using "Auto Format flash" and then did "Format all+ Download" . Now my phone is not starting.
No fastboot, no charging , No recoery mode. Only i am able to run same process again.
I am average user so dont know much about such process.. Can you guys plz help me what to do?

Hi
jalsa_100 said:
i need ur help. My Redmi note 3g (Mediatek - Global rom) was stuck up at logo. When i tried flashing it using SP flash tool , i got error that "pmt changed for the rom it must be downloaded". Then i have seen some youtube videos and read forums . As per their instruction i have first forrmated using "Auto Format flash" and then did "Format all+ Download" . Now my phone is not starting.
No fastboot, no charging , No recoery mode. Only i am able to run same process again.
I am average user so dont know much about such process.. Can you guys plz help me what to do?
Click to expand...
Click to collapse
Jalsa...i have the same problem as you. Was using the phone when all of a sudden the system files started crashing one by one. Showing "unfortunately android.xxxxx.xxx has stopped working....bla...bla...bla". Tried to reboot but stuck at mi logo. tried again, screen went blank, no mi logo. tried doing flash with download only option, successful but still phone blank upon boot up. tried format and download and phone totally dead. no charging nothing. Tried to flash again and each time successful but still cant turn phone on and no charging led. Hope someone can reply with a solution.

bump.. still no solution for this>?my phone bootloop because of many apps do not responding .. i try flash using sp flash tools and success but still cant get into system. it just stuck at MI logo .. and recovery mode also not changed after flash using sp flash tool. still twrp .. cache, data, system also cant mount if want flash rom using twrp .. it say no os installed if u want to reboot ur device via twrp. if anyone have solution plese share it. thanks

viviminmin said:
bump.. still no solution for this>?my phone bootloop because of many apps do not responding .. i try flash using sp flash tools and success but still cant get into system. it just stuck at MI logo .. and recovery mode also not changed after flash using sp flash tool. still twrp .. cache, data, system also cant mount if want flash rom using twrp .. it say no os installed if u want to reboot ur device via twrp. if anyone have solution plese share it. thanks
Click to expand...
Click to collapse
is there any solution for this ??? i got this problem as well

pengentau said:
is there any solution for this ??? i got this problem as well
Click to expand...
Click to collapse
searched almost 100 threads and even MI has no solution for it i guess coz once you format and download redmi note 3g through SP Flash phone is dead...Its realy strange MI is least interested in solving this bug and its approach is quite visible that they are only interested in launching new handsets and flash sales...Redmi note 3g is history so its users dont deserve any support...this is what am feeling for now

its a Xiaomi's game plan
ok, so did anyone get any results ??? i dont think so as the same happened with lakhs of people say around 1,78,000 people, even i tried everything from drivers to SP Flash Tools, to Fastboot ROM, and yes it did gave that green tick mark as well, but when you boot you are struck at Mi Logo everytime, its basically a bug generated and distributed by Mi itself through its updates to get rid of old phones and to compel buyers to buy a news phone, i am still researching on this matter and if its true then i will sue xiaomi in the court of law for damages and rectification, further if its true i will seek ban from the government on xiaomi from doing business in india

Nitin1976 said:
ok, so did anyone get any results ??? i dont think so as the same happened with lakhs of people say around 1,78,000 people, even i tried everything from drivers to SP Flash Tools, to Fastboot ROM, and yes it did gave that green tick mark as well, but when you boot you are struck at Mi Logo everytime, its basically a bug generated and distributed by Mi itself through its updates to get rid of old phones and to compel buyers to buy a news phone, i am still researching on this matter and if its true then i will sue xiaomi in the court of law for damages and rectification, further if its true i will seek ban from the government on xiaomi from doing business in india
Click to expand...
Click to collapse
My dad's phone (Redmi Note 3G) stuck in bootloop after a call and suddenly rebooted itself, and this happened few days ago..
At first I tried flashing ROM in TWRP recovery, no luck to get the ROM flashed in due to "unable to mount /data", and same to system and cache.
And then I tried using SP Flash tool to flash the ROM to the device, the flashing process was successful, but the phone still stuck in bootloop (stuck at Mi logo). Still no luck..
And I accidentally selected Format All + Download during few times attempts, now the phone ends up dead, I can't boot it up. No more Mi logo, charging LED doesn't turn on. It's dead.

mysi said:
i accidentally use the format all+download option in sp tools and flashed the bootloader. now whenever i try to do anything it gives me this error. pls help
-phone will not boot
-no charging led when plugged in
-phone is detected when i plug into pc
View attachment 3551440
Click to expand...
Click to collapse
You can download stock rom in a .tar format from the xda forum. Use SP tools to flash the same on your phone.
That should solve the issue. I did it for my phone. it works

Will this work for bricked Redmi Note 3G GSM Indian version,with below symptoms ?
-phone will not boot
-no charging led when plugged in
-phone is detected when i plug into pc

Hi Friends,
Trying to flash Redmi Note 3G (India) with SP Flash Tools and Global Rom V7.5.2.0 KHDMIDE (MIUI 7.5) but getting this error .
BROM ERROR : S_DA_NAND_BAD_BLOCK (0xBE5)
[HINT]:
Please suggest for the same.
Thank You........!!!!
---------- Post added at 01:30 PM ---------- Previous post was at 01:05 PM ----------
brom error : S_da_nand_bad_block (0xbe5)
[hint said:
:
Click to expand...
Click to collapse
after changing the usb cable brom error is solve and a big green tick will appear when flashing is finish.
Then reboot the phone but screen is still blank no power on ........... ??
Please suggest and help ...............!!!!
Thank you.

vishulove said:
Hi Friends,
Trying to flash Redmi Note 3G (India) with SP Flash Tools and Global Rom V7.5.2.0 KHDMIDE (MIUI 7.5) but getting this error .
BROM ERROR : S_DA_NAND_BAD_BLOCK (0xBE5)
[HINT]:
Please suggest for the same.
Thank You........!!!!
---------- Post added at 01:30 PM ---------- Previous post was at 01:05 PM ----------
after changing the usb cable brom error is solve and a big green tick will appear when flashing is finish.
Then reboot the phone but screen is still blank no power on ........... ??
Please suggest and help ...............!!!!
Thank you.
Click to expand...
Click to collapse
same here bro...

mysi said:
just follow the step exactly on this thread
http://en.miui.com/thread-64425-1-1.html
and make sure to use the miui 7 fastboot rom
Click to expand...
Click to collapse
not working for me

Mi 5s (X unlocking bootloader X) and root

Hi guys,
It turned out this script can't really unlock the bootloader. Although I didn't see it, my phone must have come with an unlocked bootloader.
I did another test on the same script but for Redmi 4X and the result was the same - can't unlock the bootloader.
So the moderators can delete this topic as it now serves no purpose. There are other topics for flashing TWRP and rooting the phone.
I am sorry for misleading you guys...
Here's how to install TWRP and SuperSu.
I'm not responsible if you brick your phone or lose data. I did a test on mine and all worked fine.
Info found here - (https://www.gizdev.com/root-xiaomi-mi-5s-unlock-bootloader/).
What you need:
1. Mi Flash Tool - Link(or just the ADB driver - Link)
2. Flasher ToolKit for Mi 5s - Link.
3. USB Debugging enabled in Developer Options
Install the Mi Flash Tool or the ADB drivers. Windows might tell you the drivers cannot be verified. Click on Yes to continue with the installation.
Unzip the Flasher ToolKit files to a folder on your computer.
Start with FLASHER TOOLKIT Capricorn.bat.
{
"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"
}
Hit Enter and this is what you'll see:
First you need to unlock the bootloader, so click on 3. Bootloader Utility. - This only really checks if the bootloader is locked or not. Nothing else.
The program will inform that hitting Enter will restart the phone in Bootloader mode.
Once there the unlocking will begin and you'll see this:
Now the phone will restart.
Once it boots up Android, you can continue with the next step - installing TWRP. Now it's a good time to transfer the SuperSu zip file to your phone. In Downloads for example.
Select the first option - Flash ZCX-TWRP 3.0.2.X for Mi 5s.
The image will be transferred and the phone will be restarted in Recovery mode. It might take a while to load TWRP for the first time, be patient.
Now that you're in TWRP, click on Install, select the SuperSU zip file. Once flashed, go back to Reboot, System.
If something fails:
-The ADB drivers didn't work for me so I installed Mi Flash and unplugged/plugged the phone in the USB.
Check in Device Manager if the ADB drivers are loaded for your Mi 5s. If you don't see anything saying ADB, unplug the phone and plug it back in the USB. Or try another USB port. Or try uninstalling the current drivers and reconnect the phone again.
-If you've closed the Flasher ToolKit and you try to start it again, but nothing happens, open Task Manager and kill/end task the adb.exe *32 process.
- If your phone restarts in Recovery, but all you see is the TWRP logo for minutes, give it about 10 minutes. If nothing changes, restart the phone by pressing and holding the power button. Have you unlocked the bootloader first?
It might have been a good idea to take a camera and shoot every step of the process, but I was testing it to confirm it's working. Hence most of the screenshots are from the web.
Anyway, that's what I can think of right now. If I'm missing something or you can't get it to work, let me know.

yes do it plz

Yes, it's a great ideea. Do it pls.

it will be a good start to have a guide here, you should give all the ways you know, including the first step to unlock by contacting xiaomi, however if you find a guide for a certain section you can link to it (or copy it and add a link so it won't be broken) .
It would also be nice to have a guide for major roms, with some optional steps that not all are aware of, like switching to f2fp

Should be ready now. The good thing is that you don't need to contact Xiaomi to unlock the bootloader.

ok so i did everything you told me
but i fail
first i press the 3 and everything was ok my device is unlocked no problem and its restart automatic
next i go to fast boot... and when i press 1 its show me twrp is install
but after that noting happens ... i press vol up and power its go to mi recovery
my phone is on fast boot i check that with cmd
dont know way
eny idea what to do
eny other method ? can i install with mi flash tool ?
im so confuse

Did you see the TWRP logo when the recovery was supposedly installed? Repeat again the TWRP installation and let's see what will happen.

unicastbg said:
Did you see the TWRP logo when the recovery was supposedly installed? Repeat again the TWRP installation and let's see what will happen.
Click to expand...
Click to collapse
no noting show up ? eny other method ?

frozenline said:
no noting show up ? eny other method ?
Click to expand...
Click to collapse
I'd say the recovery image is not getting transferred to your phone. Do you see a confirmation that the img file was sent over? It usually states how much time it took to transfer over.

unicastbg said:
I'd say the recovery image is not getting transferred to your phone. Do you see a confirmation that the img file was sent over? It usually states how much time it took to transfer over.
Click to expand...
Click to collapse
yes exactly its not transferring
---------- Post added at 03:34 PM ---------- Previous post was at 03:01 PM ----------
ok i did it problem was the adb i install naked adb driver its on know...ok so how i install custom rom? its like my other phones but something new in mounting it seed read only ? i had to change that or something? witch to wipe?

When starting TWRP the very first screen asks if you want to mount the partitions in read only mode or full access. And a check box to never show this again. Have you seen that? If not, try to update TWRP to 3.1.x.x, don't remember the exact version, you can find it here, in the Mi 5s section of the forums.
If you get that working, installing a new OS is pretty easy - go to Install, select the ZIP file with the new OS and follow the instructions. You might want to wipe cache and dalvik to avoid force closures after that.
Usually instructions on how to install a specific OS version are found in that OS's forum section.

i all ready do that bye rename and replace the new twrp in the flash kit folder everything is don... what is the best rom right now to install?

That's really up to your preference. I'm on global developer 7.5.25. Some use LOS.

i tried your guide, but i cant unlock bootloader. After i select option 3, the phone restarts and the bunny appears but after that i only receive the message attached.
Can somebody tell me what i do wrong?

What's your current MIUI version?

I'm on 8.2.1.0 and on computer i have Windows 10. I enabled usb debugging and type on add device account
Trimis de pe al meu MI 5s folosind Tapatalk

To be honest I'm not really sure why it doesn't work for you. The phone restarts, so you have the adb drivers.
Here's a little something that deserves a shot - the very first post - http://en.miui.com/forum.php?mod=viewthread&tid=525726&extra=page=1&page=2&mobile=2
I'd love to hear back from you if that worked or not.

i make a request to xiaomi to unlock bootloader and they aproved it in 6 hours, so i will try with mi unlock tool when i get home today. i keep you informed. thx

In managed to unlock with official metod.
Trimis de pe al meu MI 5s folosind Tapatalk

I've taken a look at the code in the script and this method WILL NOT unlock your bootloader. This is only useful for flashing TWRP and rooting a phone, if your phone IS ALREADY UNLOCKED. The third picture provided in the original post is incorrect and that will not be printed on the screen. The script does not attempt
Code:
fastboot oem unlock-go
at any point.
You will probably have to go through the official unlock process.

Repair Hard Bricked Phone [x52x-SD]

(i hope no one will have issue or will any mess if i am posting this again. I tried to search and did not find any post related to bricked LE 2 phone)
Dear All!
Before start make sure your phone is hard bricked( red indication light while connecting to data cable and no preview)
Here is the GUIDE:-
1. Download the following must things 1st.
FLASHONE
SPARSE INDIA VARIENT
QPST drivers
2. Copy/Move all these files on Desktop.
3. Extract FLASHONE and run MAIN.exe
4. Keep pressed Vol Up (+) and Vol Down (-) together and connect the phone by USB cable to the computer.
5. You will see that the computer will install drivers for "RELINK HS-USB QDLoader 9008".
6. Once you've opened the flashtool you'll see "Flash Type". Here select "Qualcomm - flash dead phone".
{
"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"
}
7. Select your phone - "COM ..." from "Select device" - Computer will detect it automatically by pressing REFRESH button.
8. Select File "s2_india_sparse_images.zip" from the folder where it is saved
9. Press "Flash" in the lower part of the window[​IMG]
10. Once completed, disconnect the phone and power it up by long pressing power button.
11. initially you will get 9Gb disk space to get full space back Go to Settings –Backup & reset then Restore factory settings or wipe using recovery to get
You will be reverted to "EUI 5.6.013S" x526 version of the phone.[​IMG]
Update it to latest version of EUI
Happy unbricking....
What if Flashing failed?
If you get an error like this, just put your phone into EDL mode again by pressing both volume buttons and power buttons (hear the USB unplug and plugged sound), then click the flash button again, choose “not to unzip” the rom file this time because it’s already done.

Great. Thanks!

Josesanchez0117 said:
Great. Thanks!
Click to expand...
Click to collapse
Welcome

Always getting error. No matter how many times I try

Sampath521 said:
Always getting error. No matter how many times I try
Click to expand...
Click to collapse
Change your CABLE + Use another Port...

The second link is dead, which renders this entire process impossible. Nice job
---------- Post added at 08:10 PM ---------- Previous post was at 07:56 PM ----------
Also, when you hold down the volume buttons and plug the pone in, no drivers are installed. So that's that. Have you actually gotten this to work? If so, why didn't you post the drivers for the phone to connect?

emkorial said:
The second link is dead, which renders this entire process impossible. Nice job
---------- Post added at 08:10 PM ---------- Previous post was at 07:56 PM ----------
Also, when you hold down the volume buttons and plug the pone in, no drivers are installed. So that's that. Have you actually gotten this to work? If so, why didn't you post the drivers for the phone to connect?
Click to expand...
Click to collapse
Dear , link is working fine i have checked it twice.
and install QPST. All you need is to connect the phone with PC once its connected you can bring your phone alive. :fingers-crossed:
I have checked it before posting and this software is rocking.:victory:

I did get the process working eventually, thank you. The drivers you linked did not work, but I found some that did. I think depending on your PC setup you may need to hunt around
It's worth nothing that while this will restore a bricked phone, it won't be very stable. The phone will force reboot at least once after starting up. Also, as I found out, you cannot update EMUI from this (13S) to the latest stock 21S. The stock recovery will not work.
What I did was use the steps at https://forum.xda-developers.com/le-2/development/le-s3-factory-image-5-8-020s-directly-t3527790 to use the Chinese TWRP to flash stock 20s, then from there downloaded the official stock 21S from https://www.skyneel.com/leeco-le-s3-eui-5-8-021s and the 20S stock recovery works to update to 21S stock.

emkorial said:
I did get the process working eventually, thank you. The drivers you linked did not work, but I found some that did. I think depending on your PC setup you may need to hunt around
It's worth nothing that while this will restore a bricked phone, it won't be very stable. The phone will force reboot at least once after starting up. Also, as I found out, you cannot update EMUI from this (13S) to the latest stock 21S. The stock recovery will not work.
What I did was use the steps at https://forum.xda-developers.com/le-2/development/le-s3-factory-image-5-8-020s-directly-t3527790 to use the Chinese TWRP to flash stock 20s, then from there downloaded the official stock 21S from https://www.skyneel.com/leeco-le-s3-eui-5-8-021s and the 20S stock recovery works to update to 21S stock.
Click to expand...
Click to collapse
Yes it specially happened on devices which were rooted.

Leeco Le x522 said:
Yes it specially happened on devices which were rooted.
Click to expand...
Click to collapse
I wasn't rooted, it was just unstable out of the box. And you cannot flash from 13s to any ROM higher than 20s
If there was a QFIL file for a ROM later than 13s we could use that but I could no find one online anywhere

emkorial said:
I wasn't rooted, it was just unstable out of the box. And you cannot flash from 13s to any ROM higher than 20s
If there was a QFIL file for a ROM later than 13s we could use that but I could no find one online anywhere
Click to expand...
Click to collapse
file provided in my link is of 14s ROM. after flashing that you can update only with TWRP.

Leeco Le x522 said:
file provided in my link is of 14s ROM. after flashing that you can update only with TWRP.
Click to expand...
Click to collapse
I thought it was 13S. Either way, you can go from 13S -> 20S via TWRP, then 20S -> 21S via stock recovery

emkorial said:
I thought it was 13S. Either way, you can go from 13S -> 20S via TWRP, then 20S -> 21S via stock recovery
Click to expand...
Click to collapse
No
All the way only TWRP
13S >>>DIRECT>>>21S

Leeco Le x522 said:
No
All the way only TWRP
13S >>>DIRECT>>>21S
Click to expand...
Click to collapse
You can't. There is no TWRP flashable 21s ROM. It fails with an ERROR 7. 21S will only work via the stock recovery and unfortunately there is no English copy of the stock updater online to download. Just a zillion copies of TWRP which is quite useless.

Solved

emkorial said:
You can't. There is no TWRP flashable 21s ROM. It fails with an ERROR 7. 21S will only work via the stock recovery and unfortunately there is no English copy of the stock updater online to download. Just a zillion copies of TWRP which is quite useless.
Click to expand...
Click to collapse
To avoid error 7
restart to boot loader than
boot to CHINESE RECOVERY

Leeco Le x522 said:
To avoid error 7
restart to boot loader than
boot to CHINESE RECOVERY
Click to expand...
Click to collapse
I cant do that, since there is no download for the x522 US recovery, so I can't go back.

I am using 64 GB model of le 2 x526 . Can it work with this

emkorial said:
I cant do that, since there is no download for the x522 US recovery, so I can't go back.
Click to expand...
Click to collapse
friend. Double check in threa on XDA codework the developer has prepared the recovery made by him which is a great developer for all devices. look in the thread of the lineageos14 to the first page and search. you find the fastboot flash and recovery.img file with ADB. otherwise follow the fastboot throughout the ROM. OK buddy?
Inviato dal mio LEX720 utilizzando Tapatalk

vagish said:
I am using 64 GB model of le 2 x526 . Can it work with this
Click to expand...
Click to collapse
yes without any issue

Apply update from sdcard FAILED : Rooted Crosscall Trekker M1 on BOOTLOOP

Hi there ! Hope you're doing all right
I had a lot of issues recently with my phone : Crosscall Trekker M1
It all begin when I started to remove entirely Google from the phone.
I rooted it and took the liberty to delete all that mention google.
I unfortunately delete a system file and that how my problems began.
(I called couple of times the Technique Assistance from Crosscall's Website but they weren't able to help me and I had the same story with the SAV --> the after selling's services. I gave up about asking them help and I decided to solve the issue by my own.)
So for now the phone start on bootloop, (I cannot use the OS anymore) so I can launch it in Recovery mod only.
After days of researchs I found the original stock rom for the Trekker M1 !!
On the recovery : After I wiped data and cache of course :
I tried to install the Rom with the option : "Apply update from sd card" but it didn't worked.
So I tried to install differents Custom Recovery like CWM and even renamed them update.zip but I had the exact same issue:
"E : failed to verify whole-file signature
E : signature verification failed
Installation aborted."
I also wanted to try Odin but apparently Crosscall's phones doesn't have a recuperation mod (I dream that someone got me wrong on this :crying: )
I've got a few clues about all this :
I guess the Debugging USB Mod isn't enable anymore on the phone
Maybe the versions of ClockWorkMod weren't compatible at all with my phone.
All I know is that the phone is rooted;
The recovery's version is : "Android system recovery <3e> LMY47V release-keys"
So know you know everything
Does someone think, he or she can help me with this ?
Thank you for your attention !

Brazyxs said:
Hi there ! Hope you're doing all right
I had a lot of issues recently with my phone : Crosscall Trekker M1
It all begin when I started to remove entirely Google from the phone.
I rooted it and took the liberty to delete all that mention google.
I unfortunately delete a system file and that how my problems began.
(I called couple of times the Technique Assistance from Crosscall's Website but they weren't able to help me and I had the same story with the SAV --> the after selling's services. I gave up about asking them help and I decided to solve the issue by my own.)
So for now the phone start on bootloop, (I cannot use the OS anymore) so I can launch it in Recovery mod only.
After days of researchs I found the original stock rom for the Trekker M1 !!
On the recovery : After I wiped data and cache of course :
I tried to install the Rom with the option : "Apply update from sd card" but it didn't worked.
So I tried to install differents Custom Recovery like CWM and even renamed them update.zip but I had the exact same issue:
"E : failed to verify whole-file signature
E : signature verification failed
Installation aborted."
I also wanted to try Odin but apparently Crosscall's phones doesn't have a recuperation mod (I dream that someone got me wrong on this :crying: )
I've got a few clues about all this :
I guess the Debugging USB Mod isn't enable anymore on the phone
Maybe the versions of ClockWorkMod weren't compatible at all with my phone.
All I know is that the phone is rooted;
The recovery's version is : "Android system recovery <3e> LMY47V release-keys"
So know you know everything
Does someone think, he or she can help me with this ?
Thank you for your attention !
Click to expand...
Click to collapse
Hello,
Can you capture files included in update.zip?

-Hope- said:
Hello,
Can you capture files included in update.zip?
Click to expand...
Click to collapse
By uptade.zip do you think about the Rom or the Custom Recovery ?
And yes I can

Brazyxs said:
By uptade.zip do you think about the Rom or the Custom Recovery ?
And yes I can
Click to expand...
Click to collapse
Can u copy the stock ROM name before renaming it to update.zip and yeah I meant the update.zip

-Hope- said:
Can u copy the stock ROM name before renaming it to update.zip and yeah I meant the update.zip
Click to expand...
Click to collapse
Here's the name of the stock rom :
LU652R(HS-L635)_L1185.6.02.00.EU00_MultiDownload_201601292005_user.tar.gz
To correct what I said first : I didn't renamed the Rom in fact, I did it only with the CWM file who was actually in zip format
(Sorry about that)
I couldn't even try to install the Rom because the Recovery doesn't recognize it

Brazyxs said:
Here's the name of the stock rom :
LU652R(HS-L635)_L1185.6.02.00.EU00_MultiDownload_201601292005_user.tar.gz
To correct what I said first : I didn't renamed the Rom in fact, I did it only with the CWM file who was actually in zip format
(Sorry about that)
I couldn't even try to install the Rom because the Recovery doesn't recognize it
Click to expand...
Click to collapse
Can u provide me with a pic of the tar.gz file (the files inside it)

-Hope- said:
Can u provide me with a pic of the tar.gz file (the files inside it)
Click to expand...
Click to collapse
Here's 4 captures of the tar.gz opened with Winzip
{
"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"
}
View attachment 4279786
View attachment 4279787
View attachment 4279788

Brazyxs said:
Here's 4 captures of the tar.gz opened with Winzip
View attachment 4279785
View attachment 4279786
View attachment 4279787
View attachment 4279788
Click to expand...
Click to collapse
Sorry for late reply however these files aren't falshable through recovery
they are flashed through QFIL
there are files called prog_emmc_firehose,rawprogram.xml, and patch.xml which is used to flash through qfil

-Hope- said:
Sorry for late reply however these files aren't falshable through recovery
they are flashed through QFIL
there are files called prog_emmc_firehose,rawprogram.xml, and patch.xml which is used to flash through qfil
Click to expand...
Click to collapse
Thank you very much ! I will check about QFIL by myself. For now I'm happy that someone care about my issues
I tell you if there is something new !

-Hope- said:
Sorry for late reply however these files aren't falshable through recovery
they are flashed through QFIL
there are files called prog_emmc_firehose,rawprogram.xml, and patch.xml which is used to flash through qfil
Click to expand...
Click to collapse
So it appear that the Crosscall M1 got an emergency mode. I can launch it by pressing Vol + and Vol - when I'm plugging the phone to a computer by USB.
At this moment a message show up :
"Authority indentification not found !"
"Long press power key to continue ..."
and if I do it :
No update file in TFcard!
X
Update failed!
Long press power key to power off.
If I start the phone on Emergency Mode with QFIL working (what I need to do) nothing happen.
I still have the message No Port Available on the top of QFIL.
So I'm wondering,
Do you think I can fix in some ways that problem of unrecognized device ?
or
Is there a way that I can install the Rom by choosing to install it as an update with the Emergency Mode. The Rom files would be the update that i put before in a "TFcard" in some format ?

Brazyxs said:
So it appear that the Crosscall M1 got an emergency mode. I can launch it by pressing Vol + and Vol - when I'm plugging the phone to a computer by USB.
At this moment a message show up :
"Authority indentification not found !"
"Long press power key to continue ..."
and if I do it :
No update file in TFcard!
X
Update failed!
Long press power key to power off.
If I start the phone on Emergency Mode with QFIL working (what I need to do) nothing happen.
I still have the message No Port Available on the top of QFIL.
So I'm wondering,
Do you think I can fix in some ways that problem of unrecognized device ?
or
Is there a way that I can install the Rom by choosing to install it as an update with the Emergency Mode. The Rom files would be the update that i put before in a "TFcard" in some format ?
Click to expand...
Click to collapse
Can you try to run it as an admin then choose the right com and try again ?

-Hope- said:
Can you try to run it as an admin then choose the right com and try again ?
Click to expand...
Click to collapse
I tried to run QFIL as an admin but it doesn't make a difference. The thing is that my device isn't recognize at all by my computer.
I sorry but what do you mean what "choose the right com" ?

Brazyxs said:
I tried to run QFIL as an admin but it doesn't make a difference. The thing is that my device isn't recognize at all by my computer.
I sorry but what do you mean what "choose the right com" ?
Click to expand...
Click to collapse
Did you install the qcom drivers

-Hope- said:
Did you install the qcom drivers ?
Click to expand...
Click to collapse
Hi, Here's the list of all the drivers I installed :
Qualcomm_USB_Driver_V1.0
MTK_USB_All_V1.0.8
ADBDriverInstaller
I also installed :
Android-sdk
Java SE Development Kit

After a lot of research my device still isn't showing on QFIL.
But for a time he showed up on "ADB Driver installer". I plugged the phone by USB and started it with a special combinaison (almost like the Emergency Mode's combinaison) that I'm still trying to remember.
There is also another a new thing. If I start my device that I plug before by USB and only with the power button :
My computer recognize it and the Driver Software Installation try to install MTP USB Device.
The operation failed everytime but for now I'm happy that the device is recognize.

Brazyxs said:
After a lot of research my device still isn't showing on QFIL.
But for a time he showed up on "ADB Driver installer". I plugged the phone by USB and started it with a special combinaison (almost like the Emergency Mode's combinaison) that I'm still trying to remember.
There is also another a new thing. If I start my device that I plug before by USB and only with the power button :
My computer recognize it and the Driver Software Installation try to install MTP USB Device.
The operation failed everytime but for now I'm happy that the device is recognize.
View attachment 4284734
Click to expand...
Click to collapse
Just reread the post, try to do a factory reset

-Hope- said:
Just reread the post, try to do a factory reset
Click to expand...
Click to collapse
The factory reset isn't working (and I just tried one more time), that is why I need to flash my rom.

Brazyxs said:
The factory reset isn't working (and I just tried one more time), that is why I need to flash my rom.
Click to expand...
Click to collapse
wait you said that adb works, if you can find the file system from an exact phone uploaded or you know that its common you can push it using adb if you are rooted

-Hope- said:
wait you said that adb works, if you can find the file system from an exact phone uploaded or you know that its common you can push it using adb if you are rooted
Click to expand...
Click to collapse
Yes I did said that, adb worked for a time.
I'm not sure to understand what you mean by "the file system" and "push it " with adb
The thing I'm sure of is that I'm rooted :good:
I'll continue my researchs.

[GUIDE] OnePlus 8 5G ..TMobile..(IN2017) bootloader unlock instant

Disclaimer
While I will assist with any issues resulting from this guide, I disclaim all responsibility and cannot be held accountable for any consequences caused by the use or misuse of this tool or process. This method also will wipe your phone, so please back up your data. I also will disclaim any understanding as to why exactly this works, since this method was developed by someone else, I am just listing the instructions on how to use it. With that being said, understand your personal limits and read this entire guide before starting.
Thanks to the attributed users at the end of this post, to find this method we are waiting for years...
METHOD 1:
Part 1: Requirements:
• To follow this guide you will need
A Windows PC
• Latest MsmDownloadTool for Oneplus IN2017 - Link
• Latest version of platform-tools - Link
• The bootloader unlock.ops file - Link
Plug your phone into your PC using a USB 2.0 port (this is important, USB 3.0 has given me a lot of issues and just doesn’t seem to work all the time) and ensure USB debugging is enabled.
Extract the downloaded platform-tools zip and open the platform-tools folder in a command prompt, and Run adb devices and makes sure your device appears in the list.
Next, extract the instantnoodlet_15_O.16_201001.zip and open up the MsmDownloadTool V4.0.exe inside the instantnoodlet_15_O.16_201001 folder.
When the application opens, select “Others” under the User type dropdown and hit next. Leave this window and the platform-tools command prompt open.
Part II: Entering Qualcomm EDL mode and installing correct QDLoader Driver
Part III: Flash Stock Firmware
In this section, we will flash the stock IN2017 Android 10 firmware.
Click the “Start” button in Msmtool. This will flash the stock firmware, wiping your data. Make sure you have backed your data up at this point. It will take a few minutes, usually ~300 seconds. Once it completes, it will reboot into factory default android 10.
Close MsmDownloadertool and once you are back to android, unplug your phone and power it off.
Part IV: Unlock the bootloader
In this section, we will flash the unlockable firmware and unlock the device for good.
1. Inside the directory with MsmDownloaderTool V4.0.exe, there should be a file called “instantnoodlet_15_O.16_201001.ops”. Remove it from the directory, either by deleting it or moving it to another folder. Then take the unlock.ops file downloaded earlier, and drag it into the directory and rename it to instantnoodlet_15_O.16_201001.ops . It should be in the same folder as MsmDownloaderTool.
2. Reopen MsmDownloaderTool V4.0.exe and like before, select “Others” in the drop down, and click next. Leave the window open.
3. Hold in the Volume up and down buttons, then plug your phone back in. Keep holding the buttons until your phone connects to your PC as "Qualcomm HS-USB QDLoader 9008", like before. Check device manager to ensure that it’s connected correctly as a COM port. If it boots to android, power it off and try again.
4. Return to MsmDownloaderTool. Make sure the phone is still displayed in the list under the associated COM Port.
5. Click start. The flashing should take about 15 seconds, and when complete, your phone should restart. It will display a message at boot saying “<!> The device is corrupt..” Do not panic, this is normal.
6. Unplug your phone and hold Volume Up, Volume Down and Power until the device reboots and let go once it shows the OnePlus Logo and “Fastboot Mode”. You should arrive at a screen that has “Start” in big green letters at the top, and “Fastboot mode” below it, with the very last item saying “Device state - Locked” in red text.
Plug your phone back into your computer.
7. Return to your command prompt window open in platform-tools, and run fastboot devices and ensure your device is in the list.
8. Finally, run the command "fastboot flashing unlock", it should prompt you to confirm unlocking the bootloader. Once complete, it should reboot into Android.
9. Shut the phone off again, and then Hold Volume Up, Volume Down, and Power and let go when the OnePlus logo and “Fastboot mode” shows up on screen. If the final item in the list says “Device State - Unlocked”, Congrats! You have successfully unlocked your bootloader. You can follow your custom OS’s installation guide from here.
If you want to flash back to stock firmware again (relock bootloader), you have to first flash this file (stock.ops) and then flash the bundled stock firmware. It will give a mismatch error if you do not.

So this is essentially the same as the IN2019 guide, just with the IN2017? Sounds neat.

Did anyone tried on Oneplus 8 IN 2017, Is it working

MohmmadUzairKhan said:
Did anyone tried on Oneplus 8 IN 2017, Is it working
Click to expand...
Click to collapse
Yes...i converted mine IN2017 without token..also using dual sims now

badshah99 said:
Yes...i converted mine IN2017 without token..also using dual sims now
Click to expand...
Click to collapse
you converted that ROM into which rom ?
did you follow this method?
Which files you flash? share those files link in PM or here

Share that file link which you flashed in local update? to convert dual sim

First flash tmobile msm 15.O.16_201001
Then global EU fastboot rom 10.5.9
Then ota update

badshah99 said:
First flash tmobile msm 15.O.16_201001
Then global EU fastboot rom 10.5.9
Then ota update
Click to expand...
Click to collapse
OTA update which rom?
EU or any other zip file?
your are using dual sim in which rom? OOS 11
share that file link which you used in OTA upgarde

15.I.40 downgrade OTA

badshah99 said:
15.I.40 downgrade OTA
Click to expand...
Click to collapse
File link?

MohmmadUzairKhan said:
File link?
Click to expand...
Click to collapse
[OnePlus 8][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com

Dude good job

Now make a new guide on XDA to convert method to dual sim.

MohmmadUzairKhan said:
File link?
Click to expand...
Click to collapse
MohmmadUzairKhan said:
Now make a new guide on XDA to convert method to dual sim.
Click to expand...
Click to collapse
Its already there..also given on youtube

badshah99 said:
Its already there..also given on youtube,
Click to expand...
Click to collapse
,....

Does dual sim work on OOS 12 or OOS 13 beta?

finally! Good job man! Will try it asap. Hope dual sim functioning
edit2: works, I went to the T mobile rom and check allow oem unlock first and then msmdownload the unlock.ops
{
"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"
}
edit1:not working yet...trying to figure it out

dlhxr said:
finally! Good job man! Will try it asap. Hope dual sim functioning
edit2: works, I went to the T mobile rom and check allow oem unlock first and then msmdownload the unlock.ops
View attachment 5755213
edit1:not working yet...trying to figure it out
View attachment 5755203
Click to expand...
Click to collapse
flash again tmobile msm and try again..it will work

dlhxr said:
finally! Good job man! Will try it asap. Hope dual sim functioning
edit2: works, I went to the T mobile rom and check allow oem unlock first and then msmdownload the unlock.ops
View attachment 5755213
edit1:not working yet...trying to figure it out
View attachment 5755203
Click to expand...
Click to collapse
First Enable OEM Unlocking in developer options.

badshah99 said:
flash again tmobile msm and try again..it will work
Click to expand...
Click to collapse
yes. it works after I check allow oem unlocking before flashing the unlock.ops.
and dual sim works on oxygen 11, confirmed using my op 8 pro sim tray.
I see to prevent breaking the dual sim functionality, I have to use custom rom with magisk dual sim patch. But I see the custom roms are now based on oos 12. Can I flash oos 12 first and then to custom rom? will it break dual sim function?