Hi all!
Ive got two CAT S62 Pro.
I understand there isnt a lot of help out there for these models.
One is a repaired phone, the other is brand new which will not boot past FastBoot.
I have tried MultiTools and a few other tools and the phone just reboots back to Fast boot.
Seeing as I have a good working S62, is it possible to transfer the ROM etc? This new phone has never booted furthur and selecting off/start/bootloader/recovery mode, it always restarts to fast boot.
Any help massively appreciated!
In what mode an Android device boots has NOTHING to do with installed ROM. It's a flag set within device's bootloader's settings what this controls.
Try if you can get into edl mode.
[GUIDE][TOOL] Reboot to EDL mode from FASTBOOT! No More "Test Point Method"! [kenzo]
[GUIDE][TOOL] Reboot to EDL mode from FASTBOOT! No More "Test Point Method"! [kenzo] Reboot to EDL mode from FASTBOOT! No more Test Point Method needed ;) Technical Details: Redmi Note 3 support rebooting to EDL in Android Bootloader aboot...
forum.xda-developers.com
Then you might use some tools there.
GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :) - GitHub - bkerler/edl: Inofficial Qualcomm Firehose / Sahara / Streaming / Diag Tools :)
github.com
Create rawprogram0.xml from FFU file and extract partition as raw file
I was searching for the "ffutoraw.exe" file referenced in the "rawprogram0.xml" file from the Xiaomi Mi4 Windows Mobile 10 ROM when I discovered a small tool which can also do the work. Here is the eMMC DL tool v2.15 from Qualcomm. This tool is...
forum.xda-developers.com
Hi guys,
Unfortunately the fastboot edl has the same result
I get the CAT splashscreen, then immediately fastboot screen.
Ive had a look through the next two links, but im struggling a bit outside of my knowledge!
Sorry I wasnt aware where the ROM starts and stops, I thought having a duplicate phone may help some how.
Any help appreciated
MC_Bobizzle said:
I thought having a duplicate phone may help some how.
Click to expand...
Click to collapse
Flashing programs tend to know how to change modes.
Might work. Have to know a lot though I don't.
Both those linked ones has a command reset which sounded promising...
If it's new...
Warranty Repairs | Cat phones
Warranty Repairs Limited Warranty Statement We pride ourselves on the robustness of our durable devices and as a commitment to all our valued customers, we offer a 24 months warranty from the date of purchase on all devices that meet the conditions of the Warranty Statement. For all accessories...
www.catphones.com
is there a TWRP for the CAT62 ?
Related
How to make oppo a57 be fastboot mode.
I want to install twrp and will be in root.
I've tried to hold volume + power button but become booting to window screen again..
what is oppo a57 no feature fastboot mode?
And what version twrp for oppo a57?
Please help me
thanks
"volume+" and "power" mostly running recovery/twrp mode.
Try "volume-" and "power" for fastboot mode.
Developer option is running? OEM unlock?
Load TWRP please. I wanna try too. Thanks.
volume - and power to recovery mode default oppo..
volume + and power oppo loggo appears and than booted to start again..
i have done it all before..
butstill can not get into fastboot mode..
i have not instaled twrp..
i want to fastboot mode to install twrp..
the problem is oppo a57 can not get into fastboot mode..
unlike oppo f1 i already successfully install twrp and root..
please help me
thanx for the answer
How about ADB?
USB-debagging, OEM unlock on phone, then use terminal.
"ADB reboot bootloader" - isn't work?
I'll try some things too, then return to home after work.
i have done and nothing happened,when running adb command "adb reboot bootloader" phone restart and returne to home screen not to fastboot mode.
i try to do this repeatedly until finally i ask to this forum..
help me
thanx for the answer
can someone help me?
Hello Dear, I have been trying the same with My Oppo A57, but still nothing works, I hope, we find out a way to enter fasboot mode. Thanks
Oppo A57 makes me dizzy:crying:
Fastboot access has been disabled on Oppo A57
Hey guys,
I've been looking into this situation and as far as I can tell, fastboot is disabled/unavailable on new Oppo devices unless we can find a workaround.
Fastboot was disabled by Oppo to help secure ColorOS but was previously available by flashing 'project spectrum'. Based on this report by Ausdroid it appears that they have either cancelled or temporarily suspended development of project spectrum now as well: http://ausdroid.net/2017/03/16/oppo-project-spectrum-killed-off-hiatus-notice/
A potential option I have found was a flashable zip file (magictricks.zip) that was created to enable fastboot on the Oppo F1 but I have not yet attempted to flash it as it wasn't made specifically for the A57 so it could possibly brick it.
https://forum.xda-developers.com/oppo-f1/development/boot-loader-unlock-twrp-related-t3397013/page1
I have emailed the creator of magictricks.zip asking if there's potential that it could work but I have yet to receive a response.
If someone has an A57 and is feeling brave, flashing it might possibly work as the F1 had fastboot disabled for the same reason. I am not responsible for your bricked device if you attempt this though.
Here's hoping some senior devs start helping us out with this because this phone has the potential to be an awesome well spec'd budget device with a custom rom installed.
Here's hoping.
I am waiting for news from the maker of magictrick.zip..:good:
thank
I tried .
Magictricks get rejected by A57 recovery.
As any other not genuine oppo firmware.
I tried adb reboot edl command and it works.
Blank screen phone is recognized as COM port in Windows.
That could be way to upload custom boot image.
martinr1 said:
I tried .
Magictricks get rejected by A57 recovery.
As any other not genuine oppo firmware.
I tried adb reboot edl command and it works.
Blank screen phone is recognized as COM port in Windows.
That could be way to upload custom boot image.
Click to expand...
Click to collapse
Interestingly I only found this out the other day as well.
Turns out if you put: *#801# in the dialer it gives you access to a diagnostics menu which let's you activate a bunch of Qualcomm diag ports.
Problem is I'm a rookie when it comes to QPST. I was able to use one of the included programs to backup a copy of my non-volatile memory but I'm not sure if I did it correctly or if that information is even useful? It's only 917KB.
Now would be a great time for an experienced developer to chime in. If you know ways to use QPST to back up I can do it and send you the files you need.
You need to modify emmc_appsboot.mbn to enable fastboot, then flash to phone with built in recovery or harder way with QPST tool.
Magictrics contains also emmc_appsboot.mbn but for different phone.
Original firmware is available on oppo website. It is 1.7GB size, quite a bloat. It contains emmc_appsboot.mbn
If you look inside that file with text editor you can see fastboot commands etc.
It is implemented but disabled.
martinr1 said:
You need to modify emmc_appsboot.mbn to enable fastboot, then flash to phone with built in recovery or harder way with QPST tool.
Magictrics contains also emmc_appsboot.mbn but for different phone.
Original firmware is available on oppo website. It is 1.7GB size, quite a bloat. It contains emmc_appsboot.mbn
If you look inside that file with text editor you can see fastboot commands etc.
It is implemented but disabled.
Click to expand...
Click to collapse
Thanks for the info, now I'm headed in the right direction. You sound like you know your stuff a lot more than me tbh.
See the potential problem I could see with the stock recovery is that I'm assuming it would have some kind of signature verification to ensure that the update.zip is legitimate.
I'm in the process of fixing my computer atm so I can't use it to look at the file right now.
When I open emmc_appsboot.mbn with a generic editor it's gibberish. Do I need to use notepad++ or is it just encrypted or a compressed format?
I reckon I could work out how to decrypt the emmc_appsboot.mbn but repackaging it into a working flashable file makes me nervous..
I hate this phone in its current state though so I guess I've got nothing to lose if I brick it haha. Wish me luck.
So I've done some digging and realised it's a binary file. Looks like I've got a steep learning curve ahead of me trying to wrap my head around editing these binary files. ?
This should be fun.
Good continue waiting then
Yes, it is binary file, but with text editor you can find understandable text inside gibberish.
Better results can be seen with dissassembler.
More info:
newandroidbook.
com
/Articles/aboot.html
So what next?
is there a solution?
I hope to find the best solution ..
thanks
It seems there might be a solution in China.
bbs.7to.cn/thread-315780-1-1.html
I got my A57 to custom recovery and root.
http://bbs.7to.cn/thread-315939-1-1.html
Hoping for help here. In trying to root this phone, having successfully unlocked bootloader, I am trying to flash back to stock firmware (as rooting went less than well!)
Couldn;t get the MSM download tool to work, so thought I would try the fastboot zip file extraction method!
The only Oxygen OS I can find that has the flash all .bat file is
10.5.5-GLOBAL-NordOxygen_14_OTA_007_all_2008180221_c45e1d5febd1f-FASTBOOT
Which results in looking like its working within cmd with all fastboot instruction seemingly writing to phone. But upon reboot, it just goes back to the qualcomm crashdump screen....!!
Grateful for any help inc getting the MSM download tool working.
Many thanks all
> 10.5.5-GLOBAL-NordOxygen_14_OTA_007_all_2008180221_c45e1d5febd1f-FASTBOOT
It this from Oneplus Nord ? That cannot work on N10 of course.
Qualcomm EDL mode should always work and is your best way to recover the phone.
andreas__ said:
> 10.5.5-GLOBAL-NordOxygen_14_OTA_007_all_2008180221_c45e1d5febd1f-FASTBOOT
It this from Oneplus Nord ? That cannot work on N10 of course.
Qualcomm EDL mode should always work and is your best way to recover the phone.
Click to expand...
Click to collapse
But whats does Qualcomm EDL mode actually look like? A blank screen? Can't find an explanation as to what the screen shows on Qualcomm EDL mode
TheDon13 said:
But whats does Qualcomm EDL mode actually look like? A blank screen? Can't find an explanation as to what the screen shows on Qualcomm EDL mode
Click to expand...
Click to collapse
yes it is a black screen! You know that is in EDL mode when you look into the "Device Manager" in Windows. Further explanation on how to use the tool is in the respective thread https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4204445/.
andreas__ said:
yes it is a black screen! You know that is in EDL mode when you look into the "Device Manager" in Windows. Further explanation on how to use the tool is in the respective thread https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4204445/.
Click to expand...
Click to collapse
Nowhere does it say EDL mode is simply a blank (as if phone off!) screen btw.....
I always press start on msm tool first then either adb reboot edl or make sure phone is off then hold volume buttons
I'll cut to the chase, I have a Nokia 1.3 and it is in edl mode (9008) due to bad flashing, the story is as follows. I tried to flash using the fastboot command and I had everything ready, the ROM, minimal AND fastboot, etc, and it occurred to me when I didn't know how to flash the partitions .. download the file "flash-all.bat" from the internet and at the end I ran it .. and so I left the device in the state I am in, rather in (900E) then I managed to change or go to Qualcomm 9008 mode. I would like to know if there is a way to get the phone back or not, thank you.
Hi, I am using a oneplus 7t pro mclaren edition. I have soft-bricked the device. I tried to change the filesystem in twrp to f2fs when i was in stock rom (I know it was a stupid mistake). Now the boot and recovery partitions are destroyed. I can boot to actual fastboot mode. Tried to use payload dumper but whenever it tries to boot fastbootd it says
fastboot: error: Failed to boot into userspace fastboot; one or more components might be unbootable.
Tried erase everything I got the following error using "fastboot -w"
Erasing 'userdata' OKAY [ 0.229s]
/home/abhijith/Documents/op7t/output/make_f2fs failed with status 1
fastboot: error: Cannot generate image for userdata
I have heard of MSM unbrick tool but as far as i know it only works in windows , before installing VM with windows , I want to know if there is any other way i can recover my device. I have a11 fastboot rom and a12 stock rom. Please help
I have exactly the same problem, same errors etc. if I find any solution I'll post it here. Can't use my phone until then I guess. It all happened after my phone was bricked after trying to install TWRP (previously used LineageOS Recovery).
I followed this guide which resulted in the same errors as for you: https://forum.xda-developers.com/t/...ock-fastboot-roms-for-oneplus-7t-pro.3991189/
Okay, I managed to unbrick my phone, but you won't like the (probably only) solution:
- You NEED Windows (7-10) for this, as the tools are only available on this platform, sadly
- There is this one Indian Guy that will save you:
- Includes how to install all drivers and how to get your phone into COM Mode
- This uses the MSM tool. For 1+ 7T Pro, get it here: https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4002909/
- This is going to STOCK RESET you phone 100%, meaning that your bootloader will be locked etc.
- If you get into any Chinese menu after the phone reboots, you can use Google Lens for translation
I can't believe this worked because it just feels so hacky, but trust me, it's a good last resort as you can always put your phone into COM Mode, regardless of how hard you messed up the system [citation needed].
For me even in device manager qualcomm device itself is not showing :0
abhijiths362 said:
For me even in device manager qualcomm device itself is not showing :0
Click to expand...
Click to collapse
Follow the video. When all drivers are installed and you hold both volume buttons while the device is off, it will show up as a COM/serial device for a few seconds before booting.
Important: Only connect the cable while already pressing the buttons or it won't work.
I was able to get to edl mode and msm tool was detecting but now i am facing sahara communication error i dont have official cable so maybe that might be the reason will try that also
@Colin_T Thanks for the help. I was able to install stock rom to my oneplus 7t pro. I really want to install pixel experience, in the instructions it is saying flash oos 12 firmware. But in the official website i am only seeing 11. What to do?
Hello
I tried to flash a custom rom on my Nord N10 --> [ROM][UNOFFICIAL] LineageOS 18.1 [OnePlus Nord N10/billie] <--
At 47%, the flash stopped. I tried it a several times but always with the same result.
I did a factory reset in twrp, since then all was gone from internal storage.
And now I'm unable to flash ANY rom on the device.
I tried a lot of ways: flashing stock rom with stock recovery, flashing different custom roms in twrp and other recoveries, Msmtool, extracting payload.bin and flash all the images in fastboot (I followed the commands at the bottom of this page), ... but I haven't got the result I wanted.
I even got into "Qualcom crash dump mode". That's when I tried to use the MsmDownloadTool but it wouldn't recognize any COM port.
I can transfer .zip files to the internal storage when using twrp, but flashing always fails (see attached file).
Sideloading in PE or Lineage recovery works, but flashing fails (2nd attached file).
Overview:
Positives:
bootloader is unlocked
fastboot is accessible
fastboot commands are working so I'm able to flash by fastboot command
recovery is accessible and different versions can be flashed
internal storage is accessible and copying files is possible (though, folders like Android, DCIM, downloads, etc... are all gone)
Negatives
Msmtool doesn't recognize the COM ports
some images (like vendor.img) can't be flashed in fastboot when extracted from the rom by using Payload Dumper
error shown in twrp (file attached)
neither can a rom be flashed in PE recovery or Lineage recovery
Anyone able and wanting to help or provide a link to a tutorial? I don't care which rom is installed, I just want to get the phone working again and at this point I fail to see what I'm doing wrong.
Kind regards
Its been a while since I used the N10, but I can at least help with the MSM tool: note that the MSM tool uses what is called EDL mode, which is basically a hardware (ROM) backed loader. If the phone isn't physically damaged, EDL should work no matter what you did to the partitions. It is lower level than the bootloader lock, so that shouldn't matter.
(Disclaimer: each EDL mode phone uses a signed loader, which can restrict what memory is read or written to... so technically, you could brick the phone and not be able to get it back if the loader won't let you write to a particular block. That said, I've never seen OnePlus phones unrecoverable, and if you can get the bootloader and fastboot back, you can then write to anything from FB that the partition table lets you, although that is subject to unlocking the bootloader at that point. It's why I'm probably OnePlus for life unless they do something stupid.)
Anyway, you have to get the phone in EDL mode. Off the top of my head, power it off, hold both volume keys down, then insert the USB cable. You will have a ** SHORT ** time period- like 5 sec - where the USB port will be identified as a Qualcomm 9008 (or whatever) and the MSM tool will see it. Have the tool running, and put your mouse over the "start" button, so you hit it in the window.
To be clear, EDL mode is NOT the same as crashdump mode, and any other mode than EDL will NOT be recognized by the MSM tool as valid.
Hope that helps!
I'll look into it and give it a try. Thanks!
SomeRandomGuy said:
Its been a while since I used the N10, but I can at least help with the MSM tool: note that the MSM tool uses what is called EDL mode, which is basically a hardware (ROM) backed loader. If the phone isn't physically damaged, EDL should work no matter what you did to the partitions. It is lower level than the bootloader lock, so that shouldn't matter.
(Disclaimer: each EDL mode phone uses a signed loader, which can restrict what memory is read or written to... so technically, you could brick the phone and not be able to get it back if the loader won't let you write to a particular block. That said, I've never seen OnePlus phones unrecoverable, and if you can get the bootloader and fastboot back, you can then write to anything from FB that the partition table lets you, although that is subject to unlocking the bootloader at that point. It's why I'm probably OnePlus for life unless they do something stupid.)
Anyway, you have to get the phone in EDL mode. Off the top of my head, power it off, hold both volume keys down, then insert the USB cable. You will have a ** SHORT ** time period- like 5 sec - where the USB port will be identified as a Qualcomm 9008 (or whatever) and the MSM tool will see it. Have the tool running, and put your mouse over the "start" button, so you hit it in the window.
To be clear, EDL mode is NOT the same as crashdump mode, and any other mode than EDL will NOT be recognized by the MSM tool as valid.
Hope that helps!
Click to expand...
Click to collapse
Couldn't get into EDL mode (I tried EVERYTHING). I updated/repaired the Qualcomm drivers, re-flashed another version of twrp and was able to flash this rom in twrp after I copied the rom to the sd card. It worked, the N10 is back alive again.