Database Info

Atrix 2 Wont Boot into Fastboot mode

My sceen wont come back to life whenver it goes into standby. The phone is still one however. This started happening after the upate to version 2.3.6. I would like to try 2.3.5 again however my phone also wont go into fastboot mode " Vol up/down and power same time".
Whats wrong with my phone?

My A2 is sleeping/waking up easily on 2.3.6. Are you sure that you're holding the power button long enough to wake it up?
It's odd that your phone isn't booting into fastboot...
-First make sure you're completely powered down. First "shut down" then pull the battery.
-Hold the volume up+down buttons while reinserting the battery, then release them
-Hold the volume down buton, then hold the power button. Wait about 5 seconds then release both buttons.
-This should make you boot directly into fastboot.

My phone is acting up. I definitely can't get into fastboot mode. I tired the SuperCharged V5 rom and the same screen issue was present. I really wish I could get into fastboot so I could flash back to stock in hopes in hopes it fixes my issue.
Your intrustions are confusing. Most insturctions i read say hit volup and voldow along with power at the same time. This just boots the phone normally, im not sure exactly what your steps below are indicating...
Here is what I did.
1. Removed Battery for 10 seconds
2. While holding volup and voldown down, I inserted the battery and immediatley let go, proceeded by voldown and power. (Nothing happens at all)

I'm a n00b and dont know if this will help.
I had almost the same problem after updating to 2.3.6 with the first two Atrix 2. I was told by AT&T that the OS was corrupted during update. This was prior to me rooting phone.
I started having problems again when I went to Supercharge V5. What I had to do to get to fastboot was pull out the battery, reinsert battery and then hold down power button and up/down volumn at the same time for about 5 seconds.
This took me several trys before I could get fast boot.
I plugged phone to USB on computer and reinstalled 2.3.5 using RSDLite 5.6 and InLineFlash.
Again n00b and steps may not be exact but best I can recall. Good Luck.

No dice. What a shame!!! I just paid $300 for this phone off contract. I dont have the receipt as i bought it on Criagslist, however it was brand new "sealed box" and phone.
What a joke, I can't even boot into fastboot!!! Never ran into any issues like this before where I can't even try to reinstall fresh factory os.
Anyone else have any ideas? Please please help me!

Additional Details...
When i do the reccomended steps it basically sits at a dark black screen, then eventually like 10 seconds later you can see the baclight kick in (black screen turns lights grey, it sits there for about 8 secons then boots into the Supercharged V5 splash screen. Issue is, superCharged wont actually boot, just does boot loop, and I can't get into Fastboot.
Is there any other option for me or Im I out $300?
Thanks in advance.

Thats exactly what mine was doing with Supercharged V5 it stuck in that loop when I unpluged it form charger.
It took me over 5 attempts of pulling out the battery reinserting it and holding down power button and up/down volumn.
I also had RSDLite open and INLineFlash place in the File Box ready to go.
I was about to give up and get ready to buy another Atrix 2 when I was able to get fast boot.
It did take me almost half a day to get it running. I do think however that their maybe some files missing because it doesnt run to the level it did before Supercharged V 5 was installed.
Not that their is anything wrong with V5, but being new at all this I more than likely messed something up.
I hear what your saying I would hate to have to buy another phone. Good Luck.

Thanks for trying to help but I think Im SOL. I have tried this process like 100 times and still can't get into fastboot. Im so upset right now, this was just after my Xperia Arc was stolen, then i have to buy this $300 phone and 1 day later its bricked.... ugh.... FML!

ej_424 said:
When i do the reccomended steps it basically sits at a dark black screen, then eventually like 10 seconds later you can see the baclight kick in (black screen turns lights grey, it sits there for about 8 secons then boots into the Supercharged V5 splash screen. Issue is, superCharged wont actually boot, just does boot loop, and I can't get into Fastboot.
Click to expand...
Click to collapse
It sounds like it's probably not activating the screen at the boot menu... but the boot menu might be coming up and timing out to a normal bootup like usual.
You might be able to still get to fastboot.
Basically boot up into the "dark black screen" before the 10 second timeout...
Then press VolumeDown twice, and VolumeUp once to hopefully select AP Fastboot from the invisible menu.

You seem to be somewhat right!!! I did this and a drive stareted to install when i plugged it onto my computer. However when i load up RSD lite, I see "fastboot EDISON s" under moble on far left, port type is listed as USB.
When I hit start after loading the xml file with teh "replace" zip overwriten the 2.3.6 files for a 2.3.5 restore i get "Failed flasing process. 1/18.
Any further ideas? Seems we are moving in the right direction!

Im definitely in fastboot, just can't flash back to stock as I get an error. Any thoughts? I was running stock 2.3.6 rooted, then went to Supercharged V5 Update 2 but never booted succesfully. Now Im in fastboot but can't flash back to factory.
I apprecaite all the help and I feel we are getting closer.

You might go through the manual moto-fastboot method of flashing... this seems like a good start.
RSD lite is typically doing the flashing steps through fastboot in the background for you. You might be able to get a better idea of what the error is if you use moto-fastboot.
Gotta get some sleep, good luck

Im desperately looking for some help. The method posted above seems to be the same using RSD lite. As soon as i try to flash it fails, I dont even get to step 1. Is there logging that RDS does to help me out.
Since I can get into fastboot and RDS lite detects it, do you think its possible to recover my phone?

RSD Lite Log Messages
I was able to find the logs messages within RSD Lite:
Here is what I see (Fails right away)
02/22/12 10:39:52 New Log Started For Software Download.
02/22/12 10:40:04 The FlashLog key is turned off.
02/22/12 10:40:06 Multi upgrade started for 1 phones
02/22/12 10:40:06 [Device ID: 0] 1/18 flash mbm "allow-mbmloader-flashing-mbm.bin"
02/22/12 10:40:06 ERROR: 1/18 flash mbm "allow-mbmloader-flashing-mbm.bin" -> Phone returned FAIL. - on device ID 0.
02/22/12 10:40:06 [Device ID: 0] 1/18 flash mbm "allow-mbmloader-flashing-mbm.bin" -> Phone returned FAIL.
02/22/12 10:40:06 ERROR: Failed flashing process. - on device ID 0.
02/22/12 10:40:06 Multi upgrade finished.
02/22/12 10:42:39 00000a4c Phone.cpp 468 0 ERROR Generic failure when sending command.
02/22/12 10:42:39 00000a4c Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
02/22/12 10:42:39 00000a4c Phone.cpp 468 0 ERROR Generic failure when sending command.
02/22/12 10:42:39 00000a4c Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
02/22/12 10:42:39 00000a4c Phone.cpp 468 0 ERROR Generic failure when sending command.
02/22/12 10:42:39 00000a4c Phone.cpp 1700 0 ERROR GetTechnology failed: ERROR.
02/22/12 10:42:39 00000a4c Phone.cpp 468 0 ERROR Generic failure when sending command.
02/22/12 10:42:39 00000a4c Phone.cpp 1768 0 ERROR GetSoftwareVersion failed: SendTC failed: ERROR.
02/22/12 10:42:39 00000a4c Phone.cpp 468 0 ERROR Generic failure when sending command.
02/22/12 10:42:39 00000a4c Phone.cpp 1926 0 ERROR GetSoftwareFlexVersion failed: ReadSeemElement failed: ERROR.
02/22/12 10:42:39 00000a4c Phone.cpp 468 0 ERROR Generic failure when sending command.
02/22/12 10:42:39 00000a4c Phone.cpp 1896 0 ERROR GetBootVerFlashMode failed: SendTC failed: ERROR.
02/22/12 10:42:39 00000a4c Phone.cpp 468 0 ERROR Generic failure when sending command.
02/22/12 10:42:39 00000a4c Phone.cpp 1815 0 ERROR GetDRMVersion failed: SendTC failed: ERROR.
02/22/12 10:43:15 --------------------------------------------------------
Any ideas?

ej_424 said:
Any ideas?
Click to expand...
Click to collapse
Hmm no idea... Are you using windows 7? There have been reports of problems with people using vista...
I would still try going through the steps in moto-fastboot. If you look at the InlineFlashing .xml document, you can see the steps in order.
To replicate rsdlite, you'd just copy moto-fastboot into the same directory, then run these from a command line there...
moto-fastboot <operation> <partition> <filename>
ie: from the beginning of the steps...
moto-fastboot flash mbm allow-mbmloader-flashing-mbm.bin
moto-fastboot reboot-bootloader
moto-fastboot flash mbmloader mbmloader.bin
moto-fastboot flash mbm mbm.bin
moto-fastboot reboot-bootloader
Click to expand...
Click to collapse
etc...

Flashing TWRP on Ulefone Power doesn't work

Hello.
I have tried flashing the recovery partition on my Ulefone Power in 2 ways.
Boot to ROM.
Go to options -> “About phone”, click the compilation number several times to become a developer.
Enable OEM unlock.
Boot to fastboot.
“fastboot devices” in admin CMD shows my phone.
“fastboot flashing unlock”; pressed volume up to agree; successful
“fastboot flash recovery image.img”; successful
After that, when I reboot my phone to recovery or even ROM it goes into a loop of booting. I see Ulefone logo for several seconds, then it disappears for another few and the cycle is repeated.
I've also tried to flash it from the official Ulefone tutorial. But when it comes to connecting my device I get an error:
Code:
PMT changed for the ROM; it must be downloaded
From what I read, I first have to format the whole partition, flash TWRP and only then flash ROM from TWRP. So that's what I did.
Reinstalled ROM just in case.
Used SP_Flash_Tool_Win_v5.1620 to format the partitions with option "Format whole flash without bootloader". Successful.
Used SP_Flash_Tool_Win_v5.1620 to flash TWRP choosing its scatter file. Successful.
After that, I can boot neither to recovery nor to ROM. In order for the phone to work I have to flash the ROM again with SP_Flash_Tool_Win_v5.1620.
Oh, and I tried 3 different .img files for TWRP, 2 of which I downloaded from the official tutorial and one TWRP 3.0.2-1 from NeedRom.com.
Any idea what I'm doing wrong? I can live with flashing TWRP with either of these 2 methods.

I have also tried to root my phone with apps KingRoot and KingoRoot to install something like Flashify and flash recovery from ROM. But these apps failed to root my phone.
And finally, I've tried booting the recovery from fastboot with:
Code:
fastboot boot recovery.img
...but I got the following error:
Code:
C:\Users\mrjigsaw\Desktop\Smartphone\ulefone Power_Android 6.0_20160517>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.799s]
booting...
FAILED (remote: invalid kernel address: not lie in memory)
finished. total time: 0.820s
Fortunately this error appears on whole 2 pages in Google...
Any ideas what to do next? I'm stuck.

hey. Just received my Ulefone Power today as well.
Tried various TWRP for the Power from here: http://www.needrom.com/category/ulefone/power-ulefone/
but neither did work.
Since i don't own a windows machine i also tried to simply boot the recovery via fast boot but i get the same error message.
Hope someone is willing to help us
EDIT:
from the scatter file: - partition_index: SYS9
partition_name: recovery
file_name: recovery.img
is_download: true
type: NORMAL_ROM
linear_start_addr: 0x2d80000
physical_start_addr: 0x2d80000
partition_size: 0x1000000
region: EMMC_USER
storage: HW_STORAGE_EMMC
boundary_check: true
is_reserved: false
operation_type: UPDATE
reserve: 0x00
so maybe
Code:
fastboot -b 0x2d80000 boot recovery.img
? Will try later in the evening
Cheers

nope... i just hope i don't need all the windows madness to do it...

I managed to finally flash TWRP. I solved it by... using different image...
Please note that I used 4 images before finally 5th worked, so it wasn't such an obvious solution.
I couldn't find the link in my history but after some googling I think this was the image I used:
aplush.xyz/2016/05/ulefone-power-twrp-3-download.html
Please try this one and if it doesn't work, try another one from Aplush (I'm sure that I downloaded it from Aplush).
Good luck!

was successful as well last night using this recovery:
http://www.needrom.com/download/twrp-3-0-0-5/comment-page-3/#comment-273477
however i could not fastboot boot it, so i dived into the cold and flashed it hoping for the best

mrjigsaw said:
I have also tried to root my phone with apps KingRoot and KingoRoot to install something like Flashify and flash recovery from ROM. But these apps failed to root my phone.
And finally, I've tried booting the recovery from fastboot with:
Code:
fastboot boot recovery.img
...but I got the following error:
Code:
C:\Users\mrjigsaw\Desktop\Smartphone\ulefone Power_Android 6.0_20160517>fastboot boot recovery.img
downloading 'boot.img'...
OKAY [ 0.799s]
booting...
FAILED (remote: invalid kernel address: not lie in memory)
finished. total time: 0.820s
Fortunately this error appears on whole 2 pages in Google...
Any ideas what to do next? I'm stuck.
Click to expand...
Click to collapse
did you get it fixed?

c2305 flashing problem with setool

Hello Guys ,
c2305 flashing problem with setool
Code:
SIGNED MODE (USING SERVER)
CFG:101000000000
PLEASE ATTACH TURNED OFF PHONE NOW
PRESS AND HOLD "BACK" OR "VOLUME DOWN" BUTTON ...
RUNNING S1_BOOT VER "2.14.J.2.16"
ACTIVE_COMP_AID : 0001
HWCONF_AID : 0001
LOADER_AID : 0001
BOOT_AID : 0001
[ llcomm: 00080000,00080000 ]
DEVICE ID: 7759D23E3F1B2BD5
FLASH ID: "0090/014A0086"
LOADER VERSION: MT6589_12
writing "C:\Users\Ramsat\Downloads\Compressed\16_0_B_2_16.FSP_Pelican_WORLD_i_1277_6019_S1_SW_LIVE_BB35_PID1_0002_MMC.R2A\sys ...
Processing package
system-sign_S1-SW-LIVE-BB35-PID1-0002-MMC.sin
ERROR: "Archive is damaged. Open failed - Native error: 00048"
Break
Elapsed: 9 seconds

Question Stock recovery error: SamMobile firmware footer is wrong; signature verification failed

Samsung recovery
Code:
samsung a12zh/a12
10/QP1A.190711.020/A125FZHU1AYC3
user/release/keys
Install /sdcard/A12/stock/A125FXXU1AUC3_A125FOLM1AUC3_XSA.zip ...
Finding update package ...
Opening update package ...
Verifying update package ...
E: Footer is wrong
Update pkacage verification took 0.1s (result 1).
E: Signature verification failed
E: Error 21
Install from SD card completed with status 2.
Installation aborted. #1
PNG and TGY were also failed like is, but if reflashing stock ROM using Heimdall, which partitions are to be flashed accoring to the PIT on my A12? And which partitions should never be touched?
Even with successful flashes using Heimdall, it still always reports to me SW REV check failed
Now my device is still being boot-looped, and on either YouTube or online text tutorials nothing is about solving the boot loops for my A12
And have also retried to flash my own builds of TWRP instead, https://sourceforge.net/p/twrp-samsung-a12/code/ci/master/tree/out/target/product/a12, however also unfortunately somewhy,
Code:
Heimdall mode (High speed)
Product name: SM-A125F
...
Warranty void: 0x1 (0x500)
RP SWREV: B1 NS1 K1 S1
...
SW REV check fail: [recovery] Fused 1 > Binary 2
SW REV check fail: [boot]Fused 1 > Binary 0

Me again.. Ive obtained the same problem and solved it just reflashing my whole firmware with Odin u_u

I’ve just flashed the full firmware.
The SW REV check failures were fixed, but my device is still being boot looped
What to do next?

My A12 has MTK chipsets (according to my CPU-Z), hence also their ‘‘secure’’ boot locks, now going to unlock it by their SPFlashTool

speedmetal444 said:
Me again.. Ive obtained the same problem and solved it just reflashing my whole firmware with Odin u_u
Click to expand...
Click to collapse
Heimdall flashes are always by PIT partitions; PIT means partitioning informative tables
Odin flashes, on the other hand, are instead more by tar packages, namely BL, AP, CP, and CSC
* BL = BootLoaders; AP = Android PDA’s i.e. systems with also recoveries; CP = Core PDA’s i.e. modems; CSC = Country support codes or Consumer software customizations

I’m still being boot looped due to sth in unknown errors named PDP
Code:
Android recovery
samsung/a12nsxx/a12
11/RP1A.200720.012/A125FXXU1BUE3
...
Supported API: 3
# MANUAL MODE v1.0.0#
No commands specified
-- Wiping data ...
Formatting /data ...
E: [PDP] lstat /c___/pdp_b__: 0 - No PDP scenario
Formatting /cache ...
Formatting /metadata ...
Formatting /keydata ...
Formatting /keyrefuge ...
Data wipe complete.

hd_scania said:
Samsung recovery
Code:
samsung a12zh/a12
10/QP1A.190711.020/A125FZHU1AYC3
user/release/keys
Install /sdcard/A12/stock/A125FXXU1AUC3_A125FOLM1AUC3_XSA.zip ...
Finding update package ...
Opening update package ...
Verifying update package ...
E: Footer is wrong
Update pkacage verification took 0.1s (result 1).
E: Signature verification failed
E: Error 21
Install from SD card completed with status 2.
Installation aborted. #1
PNG and TGY were also failed like is, but if reflashing stock ROM using Heimdall, which partitions are to be flashed accoring to the PIT on my A12? And which partitions should never be touched?
Even with successful flashes using Heimdall, it still always reports to me SW REV check failed
Now my device is still being boot-looped, and on either YouTube or online text tutorials nothing is about solving the boot loops for my A12
And have also retried to flash my own builds of TWRP instead, https://sourceforge.net/p/twrp-samsung-a12/code/ci/master/tree/out/target/product/a12, however also unfortunately somewhy,
Code:
Heimdall mode (High speed)
Product name: SM-A125F
...
Warranty void: 0x1 (0x500)
RP SWREV: B1 NS1 K1 S1
...
SW REV check fail: [recovery] Fused 1 > Binary 2
SW REV check fail: [boot]Fused 1 > Binary 0
Click to expand...
Click to collapse
The error at the last is probably because the firmware you are trying to flash has older bootloader than what it is currently and it looks like you cannot downgrade bootloader.

I

Problem with Nokia Lumia 630 flashing

How can I flash my Nokia Lumia 630?
I tried on WPInternals, but it says:
Flash failed! Error 0x1106: Security header validation failed
I also tried THOR2, which also failed. It says:
Initiating FFU flash operation
WinUSB in use.
isDeviceInNcsdMode
isDeviceInNcsdMode is false
Device mode 6 Uefi mode
[THOR2_flash_state] Pre-programming operations
Disable timeouts
Detecting UEFI responder
Lumia UEFI Application did not respond to version info query
Device is not in Lumia UEFI mode
Device mode get failed, mode is 6
Connection lost, trying to re-connect
Rebooting to the normal mode...
Rebooting from the WP/MMOS failed.
Operation took about 16.00 seconds.
THOR2_ERROR_TO_COMMUNICATE_WITH_DEVICE
THOR2 1.8.2.18 exited with error code 84102 (0x14886)
Can someone help me?

I'm also having issues unbricking my Nokia 630 (RM-979),
It's completely bricked. Nothing shows on the screen. Completely black.
It is detected on Windows Device Manager as QDLoader 9008 (COM7), but I'm not being able to flash it.
I have tried:
- Windows Phone Internals
- Windows Device Recovery Tool
- NaviFirm
- Thor
Result from thor:
> thor2 -mode ffureader -ffufile "C:\rm-914\XXX.ffu" -dump_gpt -filedir C:\dump
THOR2 1.8.2.18
Built for Windows @ 13:36:46 Jun 16 2015
Thor2 is running on Windows of version 6.2
thor2 -mode ffureader -ffufile C:\rm-914\XXX.ffu -dump_gpt -filedir C:\dump
Process started Wed Dec 29 17:13:00 2021
Logging to file C:\Users\Angelo\AppData\Local\Temp\thor2_win_20211229171300_ThreadId-13244.log
Debugging enabled for ffureader
Initiating do FFUReader operations
Version of FfuReader is 2015061501
Parsing FFU... Please wait...
Failed to parse FFU file. Header size: 0x00000000, Payload size: 0x0000000000000000, Chunk size: 0x00000000, Header offset: 0x00000000, Payload offset: 0x0000000000000000
File open failed
THOR2_ERROR_FFUREAD_CORRUPTED_FFU
THOR2 1.8.2.18 exited with error code 84204 (0x148EC)
Any ideas?

Angelo Marzolla said:
I'm also having issues unbricking my Nokia 630 (RM-979),
It's completely bricked. Nothing shows on the screen. Completely black.
It is detected on Windows Device Manager as QDLoader 9008 (COM7), but I'm not being able to flash it.
I have tried:
- Windows Phone Internals...
Click to expand...
Click to collapse
I don't have bricked Nokia, but did you format the whole phone storage when Windows said it's broken? Because it can be the reason why your phone is bricked.