I was running stock 2.3.4 and successfully unlocked my bootloader using steps 1-5 of this thread and then tried rooting it using the simple Modaco method mentioned at the top of the same thread. It was late and I wasnt paying attention that it was for 2.3.2..
I got everything in terminal to say that it flashed correctly but when I unplug my phone I am stuck at the Google splash screen. After a battery pull I can boot into fastboot and choose recovery but then I am greeted with the android out of the box followed by a triangle ..I am assuming I have lost/ corrupted my recovery. Can anyone guide me out of this mess? Mac instructions would be greatly appreciated.
FIXED: Flashed the appropriate ROM from this thread
Edit1: Since I can access CWM from Fastboot can I just mount USB, transfer a ROM or nandroid and flash it?
Edit: Fastboot Menu Info:
HW Ver: Rev 11
Bootloader Ver: i9020xxka3
Baseband Ver: i9020xxd1
Lock State: Unlocked
Did u try pushing up and the power to access the recovery menu
Sent from my Nexus S 4G
Yes after a battery pull I can push vol + and power...which brings me to Fastboot mode not recovery...
Now an update.. I tried starting all over again using Kenvan19s thread I can now select recovery from the fastboot menu and enter CWM v 3.0.0.5 but again if I reboot I am stuck at the Google splash screen
Nvmd
Sent from my Nexus S 4G using Tapatalk
I am trying to flash back to 2.3.5 from SCv5 with update1. I did apply the 2.3.6 -> 2.3.5 files as it was stopping at 4/20 prev to this... (It also said 2.3.6 in system info)
Yes it is connected to one of the back USB main ports & the phone is charged to 100%.
I am able to start flashing and it makes it to 14/15 flash system "system.img" but it then stops at:
Failed flashing process. 15/20 flash boot "boot.img: -> Phone returned FAIL. ; phone connected
hmm ok, never mind restarted the program again and poof it went, sorry for the trouble. It was a corrupt extraction I think, because once I reopened the program and let it re-extract all was good...
Flashing always gets me scared when the word FAIL comes up, anyway thanks for the quick reply lol
Wait, 14 out of 15? It should say 14/18.
How did you get the fxz? Did you download it from my dropbox? If you did then I think that the reason it's only doing 15 steps is because it's using the fast xml file I created.
If you just used replace.zip to replace files then I'm not sure why it'd only be 15 steps...
ANYWAYS, first unzip the fxz. Instead of directing RSD Lite to the .zip fxz, direct it to the .xml file located inside of the folder that you unzipped. If there are 2 .xml files use the one with the longer name.
Also it's possible that the fxz managed to get corrupted as you downloaded it. Use this utility to get an md5sum of the file.
EDIT lol OK, took too long to post. Glad you got it worked out.
Stuck on Flash Failure
A2 stuck on Flash failure screen with low battery. Later on nothing but a white led light comes on!!!! Please help this is my business phone!!
Your battery is low I guess
Use McGyver method.
And flash it with RSD (2.3.5 if you havent updated) or modified 2.3.5 as written in noob thread
I read that earlier and don't have any extra cable/charger wire around. I was on Supercharge V5 and was getting the power button menu with reboot and then it was stuck on the boot loop. RSD flashed with extra replace attachment and got to step 18 reboot and came up with GC and SP errors. Now the screen says Flash Failure and battery low in Fastbot mode and when hookup to USB on PC white light comes on!!! I need this phone...
See if you can power off then get to the menu with the fastboot option and select boot normally. Once it tries to reboot pull the battery and plug it into your charger and see if it will start trying to take a charge. If not then you will have to find a way to charge it
Try to do this:
Download this file and this file
Unzip the first file (InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.zip)
Unzip the second file (replace.zip)
Copy all files from second file (cdt.bin, device_tree.bin, InlineFlashing_edison_5.5.175.16_cfc_p3_APBP_CID285.xml, lbl) and replace in the first file folder
Flash with RSD
I think so that this will work because the SCv5 was based in the 2.3.6.
Try and tell us what happened!
I'm sorry by my english!
can't flash
i'm trying to flash my atrix 2.3.6, i downloaded the FZX, i replaced the files for 2.3.6, downloaded the usb driver and then procceded to flash it with RSD lite 5.6 and it showed me this error on the status: "Failed flashing process. Failed flashing process. 3/18 flash mbmloader "mbmloader.bin" -> Phone returned FAIL.; phone connected".
Also, in the device properties it shows me this:
ESN:
Technology: N/A
Software Version: N/A
Flex Version: N/A
DRM Version: N/A
Can anybody help me please?
cal8 said:
i'm trying to flash my atrix 2.3.6, i downloaded the FZX, i replaced the files for 2.3.6, downloaded the usb driver and then procceded to flash it with RSD lite 5.6 and it showed me this error on the status: "Failed flashing process. Failed flashing process. 3/18 flash mbmloader "mbmloader.bin" -> Phone returned FAIL.; phone connected".
Also, in the device properties it shows me this:
ESN:
Technology: N/A
Software Version: N/A
Flex Version: N/A
DRM Version: N/A
Can anybody help me please?
Click to expand...
Click to collapse
Even I have the exact same error someone please help us out
I tried to flash to Indian Firmware first through rsd lite it stopped in step 7 then i tried to flash it with att firmware it is stopping at step 3
I am having same exact problem it stops at 3 when trying to flash back i have to keep cmd the boot.img to get it to work.
Hi, I tried applying the latest OTA however I screwed up and now both boot and recovery partition seem to be corrupt. Any help unbricking would be most welcome.
Here is what happened in detail: I followed the guide describing how to update for root users. However I originally rooted my tablet by flashing a patched boot image, so the update script failed on the following line:
Code:
assert(apply_patch_check("EMMC:/dev/block/platform/sdhci-tegra.3/by-name/LNX:4065536:e6a4be41aac750d525128c5981d9a225fe277eac:4065536:b89e110ce7e23a241778b37340993eea7d8c1a36"));
I now believe this checked whether the original boot was in place. So I foolishly removed in the same way the guide describes removing the line containing "ro.product.name". Unfortunately it seems that the update will not reflash the boot partition but rather patch it which seems to have failed.
When booting the tablet I get the error
Code:
Boot verified failed ...
When booting recovery (holding down vol down during power up) I get:
Code:
Erasing Cache before SD update....
SD update cmd: recovery
--update_package=SDCARD:update.zip
Booting recovery kernel image
Recovery verified failed ...
I would really appreciate it if someone could provide me with a valid boot.img and a way of flashing it.
Update:
I partially solved the problem by going into fastboot mode by holding power down and switching screen lock on and off while powering up. This allowed me to perform OEM unlock again which booted the tablet. I believe I still do not have the prober boot.img and checking for system update gives the following error message:
Code:
System update is not allowed on your device. Please call service center for help. Thanks.
This is the current tablet status:
Code:
Android version: 4.0.4
Kernel version: 2.6.39.4+
Image version: Acer_AV043_A700_RV23RC05_WW_GEN1
Build number: Acer_AV043_A700_1.061.00_WW_GEN1
U should enter the fastboot in this way: Hold on volume- (two dots) and Poweron and then toggle the rotation switch on and off a few times.
My A510 was bricked last month, i have no idea either.
u'd better send it to Service. Good luck!
I decided to upgrade my firmware without flashing the stock recovery back (I'm using the CWM 6 one). So i delete the 1st line and the assert(apply_patch_check("EMMC:/dev/block/platform/sdhci-tegra.3/by-name/.. from the script to allow the update.
So everything went fine and I prevented the update to flash a new recovery in CWM and after the reboot I had the "Boot verified failed" message.
So it just meansthe CWM recovery is not recognized and we are not allowed to use it. So I just went to fastboot mode and unlocked the bootloader.
Now my fully working A700 is updated
Hi
I postponed upgrade as much as I can but looks like that is time do it
I found this procedure made by SCFirefighter:
I updated my code base too, without a single hiccup. Here is what I did:
----------------------------------------VERIZON XT926 ONLY----------------------------------------
-----PREPARATION
Download cm-11-20140701-NIGHTLY-moto_msm8960.zip from http://download.cyanogenmod.org/?device=moto_msm8960
Download Android 4.4.2 / Blur_Version.183.46.10.XT926.Verizon.en.US from http://sbf.droid-developers.org/phone.php?device=5
Download Google Apps 20140606 from http://wiki.cyanogenmod.org/w/Google_Apps
Download RSD Lite 6.1.6 from https://bitly.com/bundles/johnlgalt/2
Download CWM6049-RAZR-HD_M-KITKAT.img from http://forum.xda-developers.com/show....php?t=2747535
-----Before-state:
CWM 6.0.4.9
Baseband VANQUISH_BP_100730.151.64.17P
Kernel: 3.0.101
-----Update steps:
1) Make sure your phone battery is sufficiently charged. Mine was at above 80%
2) Boot into fastboot mode. Current loader version: 10.9B(*) (sha-1e9f557, 2013-09-26 12:31:42)
3) Start RSD Lite, select your image, and start flashing (This takes 6-7 minutes)
4) Watch phone boot with new Motorola dual core boot logo. Windows discovered a new USB device, and initialized the XT926 driver again. Windows indicated MTP USB Device failed. (don't panic). 3 other ‘new’ USB devices are installed, and the “Setup Wizard” appeared 4 minutes into this first time boot sequence. “Please wait while we prepare your phone for first time use”. Boot finishes within 5 minutes, and I am now at the Welcome screen to pick my language.
5) Skip all restore and Google Account setup dialog boxes until you exit the Setup Wizard
6) New kernel and device info:
System Version 183.46.10.XT926.Verizon.en.US
Baseband: VANQUISH_BP_100731.020.64.21P
Kernel: 3.4.42
Build number: KDA20.62-10.1
Build date: Fri May 2 02:41:20 PDT 2014
7) Close RSD lite if still open.
8) Boot into fastboot bootloader again. Verify new version: 10.9B(*) (sha-61146a2, 2014-05-02 03:15:48)
9) Flash new KK recovery from your PC: fastboot flash recovery CWM6049-RAZR-HD_M-KITKAT.img
10) Reboot into your new recovery
11) Format /system and /data
12) Install CM zip, followed by gapps zip. I did it in the same session. No reboots in between.
13) Reboot your phone from your recovery screen, and watch it boot up into CM.
14) Verify phone details:
Kernel: 3.4.96
Build number: KTU84P
Build date: Tue Jul 1 05:03:23 PDT 2014
15) Profit!
Click to expand...
Click to collapse
Is that correct? Do I have to edit any lines in xml file?
In the case that kkbl doesn't work for me as I wish, can I go back to jbbl? I read that is possible if I skip gpt and tz flash.
Hello,
I have a Moto G5 XT1676 with Android 7.0 stock firmware.
I rooted the phone with Magisk and installed TWRP but I never backed up my recovery.img partition. Now I want to flash a stock recovery partition so I can apply an ota update and in case I want to sell on the phone I want to be able to take twrp off and unroot. I don't want to flash an entire firmware.. Can someone help me in choosing the correct stock recovery.img for my phone?
Here are details of the firmware currently on my phone:
Baseband version: M8937_22.29.02.56.01R CEDRIC_EMEADSDS_CUST
Kernel Version: 3.18.31-perf-g4a0c859
Wed May 2 06:29:31 CDT 2018
Build Number: NPPS25.137-93-12
Blur Version: Blur_Version.25.321.18.cedric.retail.en.US
RETGB
Here are the details of another stock firmware I downloaded.
SW Display Build ID: NPP25.137-93
SW Version: cedric-user 7.0 NPP25.137-93 12 release-keysM8937_22.29.02.56R
Build Date: Wed Nov 22 03:19:24 CST 2017
Blur Version: Blur_Version.25.281.12.cedric.retail.en.US
You see the two firmware are almost identical but I don't have enough experience to know if it would be safe to take the recovery.img out of the second one and use it in the first?
<<update>>
I tried booting into bootloader then..
# fastboot boot recovery.img
... to test the recovery .img file from another firmware but I got a picture of an Android lying down with red above him and his lid open and the words "No Command".
I think that # fastboot boot is disabled on Android OS these days.
Any help much appreciated !!
Flex
FlexMcMurphy said:
...
<<update>>
I tried booting into bootloader then..
# fastboot boot recovery.img
... to test the recovery .img file from another firmware but I got a picture of an Android lying down with red above him and his lid open and the words "No Command".
I think that # fastboot boot is disabled on Android OS these days.
Any help much appreciated !!
Flex
Click to expand...
Click to collapse
The no command screen is looking for hardware button command to boot into recovery. That is typical. My experience is pies and hold the power button then press and release volume up.
I was mostly asking for help with choosing a compatible recovery.img file for my phone..
But thank you for that advice about how to get past the "No Command" screen which was very helpful.
Flex