Question Guide to unroot, relock bootloader and to OTA updates - Google Pixel 6a

Hi,
Is there a guide to receive updates or sideload them while being rooted and unlocked??
Also how to unroot and relock bootloader??
Thanks

you should be able to get in system OTA's even while being rooted so long as you didn't modify /system in any way.
If you want to do that you need to first restore the stock boot.img, typically done by going to magisk -> restore images, for details refer to the guide for the pixel 6, check the automatic OTA section.
Though it might be easier and safer to sideload the OTA instead, you can find details for that in the same guide under the sideload OTA section.
As far as I understood it doesn't matter if you still have modules installed and a rooted boot.img when you sideload, but if you want to be super safe you could always just disable all modules and flash stock boot.img
After sideloading OTA you have to re-root, so keep a magisk patched boot.img ready to boot from.
unroot is just as easy as flashing stock boot.img or uninstalling through magisk.
I'm not exactly sure what the difference between the "uninstall" and "restore images" option is in magisk.
"restore images" is supposed to restore your stock boot.img if you previously rooted by doing "direct install" in magisk.
And I suppose uninstall does the same but also removes all of magisk instead of only unrooting?
Don't take my word for it, it's just a guess.
Relocking bootloader requires you to be 100% stock, and iirc that also requires you to wipe your device, but not sure about that one.
I'd recommend you use pixel flasher for that as it leave little room for error, typos and the like.
In essence you just download the latest factory image from google, flash everything including wiping data and relock bootloader after that.
That said, using Pixel flasher or android flash tool with the wipe options checked do the same for you without needing to type out commands and navigate your downloaded archives.
Is it necessary to flash to both slots?
I don't know, hopefully someone else can answer that one.

G5-User7080 said:
you should be able to get in system OTA's even while being rooted so long as you didn't modify /system in any way.
If you want to do that you need to first restore the stock boot.img, typically done by going to magisk -> restore images, for details refer to the guide for the pixel 6, check the automatic OTA section.
Though it might be easier and safer to sideload the OTA instead, you can find details for that in the same guide under the sideload OTA section.
As far as I understood it doesn't matter if you still have modules installed and a rooted boot.img when you sideload, but if you want to be super safe you could always just disable all modules and flash stock boot.img
After sideloading OTA you have to re-root, so keep a magisk patched boot.img ready to boot from.
unroot is just as easy as flashing stock boot.img or uninstalling through magisk.
I'm not exactly sure what the difference between the "uninstall" and "restore images" option is in magisk.
"restore images" is supposed to restore your stock boot.img if you previously rooted by doing "direct install" in magisk.
And I suppose uninstall does the same but also removes all of magisk instead of only unrooting?
Don't take my word for it, it's just a guess.
Relocking bootloader requires you to be 100% stock, and iirc that also requires you to wipe your device, but not sure about that one.
I'd recommend you use pixel flasher for that as it leave little room for error, typos and the like.
In essence you just download the latest factory image from google, flash everything including wiping data and relock bootloader after that.
That said, using Pixel flasher or android flash tool with the wipe options checked do the same for you without needing to type out commands and navigate your downloaded archives.
Is it necessary to flash to both slots?
I don't know, hopefully someone else can answer that one.
Click to expand...
Click to collapse
Thank you for your answer and your time, very much appreciated! I'll have a look at that guide. Thanks!

I don't know if anyone is getting this error in PixelFlasher...
Active code page: 850
Sending 'bootloader_b' (11574 KB) OKAY [ 0.261s]
Writing 'bootloader_b' (bootloader) Flashing pack version bluejay-1.2-9288097
(bootloader) flashing platform gs101
(bootloader) Validating partition ufs
(bootloader) Validating partition ufs
(bootloader) Validating partition partition:0
(bootloader) Validating partition partition:1
(bootloader) Validating partition partition:2
(bootloader) Validating partition partition:3
(bootloader) Validating partition bl1_b
(bootloader) Validating partition pbl_b
(bootloader) Validating partition bl2_b
(bootloader) Validating partition abl_b
(bootloader) Validating partition bl31_b
(bootloader) Validating partition tzsw_b
(bootloader) Validating partition gsa_b
(bootloader) Validating partition ldfw_b
FAILED (Status read failed (Too many links))
Finished. Total time: 2.662s

juv3nal said:
I don't know if anyone is getting this error in PixelFlasher...
Active code page: 850
Sending 'bootloader_b' (11574 KB) OKAY [ 0.261s]
Writing 'bootloader_b' (bootloader) Flashing pack version bluejay-1.2-9288097
(bootloader) flashing platform gs101
(bootloader) Validating partition ufs
(bootloader) Validating partition ufs
(bootloader) Validating partition partition:0
(bootloader) Validating partition partition:1
(bootloader) Validating partition partition:2
(bootloader) Validating partition partition:3
(bootloader) Validating partition bl1_b
(bootloader) Validating partition pbl_b
(bootloader) Validating partition bl2_b
(bootloader) Validating partition abl_b
(bootloader) Validating partition bl31_b
(bootloader) Validating partition tzsw_b
(bootloader) Validating partition gsa_b
(bootloader) Validating partition ldfw_b
FAILED (Status read failed (Too many links))
Finished. Total time: 2.662s
Click to expand...
Click to collapse
Best to go over to the Pixel Flasher thread and post your support.zip so the dev can take a look at it.

Related

[Solved] HTC Butterfly S-Off, Unlock, Bootloader & TWRP Recovery "Stuck in bootloop."

[Solved] HTC Butterfly S-Off, Unlock, Bootloader & TWRP Recovery "Stuck in bootloop."
PLEASE try to HELP or acknowlede!
Please forgive me for contacting you as such but I'm desparate right now.
Dear All,
I'm wound up in a bootloop. Please help at the earliest.
This is my current status and a little history.
1. I was flashed InsertCoin 3.0.6 on my x920d (originally HTC_038) a couple of days ago (and did a TWRP Backup after That),
2. Had unlocked my previous, old custom rom (thru HTCDev), S-Off (thru rumrunner) and
3. rooted by flashing 'UPDATE-SuperSU-v2.02' from recovery after flashing the ROM a couple of days earlier.
4. I had also flashed Kairi's firmware-kk (which is for HTC_061) as I had Super CID 11111111 by "fastboot oem writecid..." method, now I'm not able to do it anymore).
Anyway, there was some problem (wrongly presumed by me) with the htc backup/restore function, so I reflashed the IC3.0.6 rom a couple of times thru recovery(TWRP 2.7 by Kairi). And the device booted perfectly.
Stupidly, I happened to flash '[ROM] FireKatN4 Deodex V5 TW 4.4.4' through Kairi's recovery. Link of the ROM - http://forum.xda-developers.com/note...emely-t2916463.
Thish rom was for Samsung T Mobile Galaxy Note 4 N910T and it did not flashed properly; so I re-flashed IC3.0.6 thru recovery (if required I can perform this again) and it showed successful at the end.
Now since then whenever I reboot it get stuck in bootloop.
Since yesterday I have been trying various steps (repeated several times and not inchronological order):
- Unlocked the bootloader thru HTCDev once again.
- Flashing the firmware-kk thru oemRUU after changing the CID to 11111111 in the 'adroid-info file" of this firmware's zip. (it gave Remote90 error and after repeating fastboot flash zip firmware-kk.zip it flashed.
Although in between it said "signature checking, verified fail - Bypassing" and then continued on its own after that, successful at the end. However on my device the green bar moved only to 90% and remained there.)
- Rebooted into bootloader, tried flashing the same firmware with Error :
"C:\Fastboot>fastboot flash zip firmware-kk.zip
target reported max download size of 1514139648 bytes
sending 'zip' (19401 KB)...
OKAY [ 1.975s]
writing 'zip'...
FAILED (remote: not allowed)
finished. total time: 2.011s"
Now my status is:
Although I'm able to flash recovery img thru fastboot. I can do it from oem rebootRUU.
My Getvar all read as :
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 3A.32.306.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.04.709.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: xxxxxxx
(bootloader) imei: xxxxxxxxx
(bootloader) meid: 00000000000000
(bootloader) product: deluxe_ub1
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PL9911000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4196mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae8bbb39
(bootloader) hbootpreupdate: 11 - (As per Kairi's original Firmware-kk android-info file it is : 3, the CID is HTC_061)
(bootloader) gencheckpt: 0
all: Done!
Now
1. I,m S-Off, Relocked/Unlocked Bootloader (able to do this thru fastboot).
2. Can boot into bootloader & TWRP Recovery - Kairi's, but cannot boot the phone.
3. After flashed IC3.0.6 thru recover once again. when rebooting, get stuck in bootloop again.
Please try to help me out.
P.S. I have somescreenshots available of several steps, if required.
Hi Capt Vikram.
Try extracting the boot img and flash that. It has got me out of a few bootloops
Clarkie_955i said:
Try extracting the boot img and flash that. It has got me out of a few bootloops
Click to expand...
Click to collapse
Hi Clarkie,
Your help is appreciated.
I flashed the IC3.0.6 rom thru recovery successfull.
rebooted to bootloop.
Then I flashed the boot img from InsertCoin 3.0.6 from fastboot.
No luck Again stuck in bootloop.
Capt Vikram Sandhu said:
Hi Clarkie,
Your help is appreciated.
I flashed the IC3.0.6 rom thru recovery successfull.
rebooted to bootloop.
Then I flashed the boot img from InsertCoin 3.0.6 from fastboot.
No luck Again stuck in bootloop.
Click to expand...
Click to collapse
Did you flash the kk firmware twice? It will fail on the first go so flash again.
Clarkie_955i said:
Did you flash the kk firmware twice? It will fail on the first go so flash again.
Click to expand...
Click to collapse
Yes Clarkie,
I had flashed firmware-kk thru 'fastboot oem rebootRUU', then 'fastboot flash zip fimware-kk.zip'
It gave me th 90 error and I repeated the command and it went successful.
I'll do that again and update you with each step chronologically.
Thanks for your help in my desparate situation.
Here's what I repeated. Step - by -step
1. First of all got the getvar all details:
C:\Fastboot>fastboot getvar all
(bootloader) version: 0.5
(bootloader) version-bootloader: 1.57.0000
(bootloader) version-baseband: 3A.32.306.04
(bootloader) version-cpld: None
(bootloader) version-microp: None
(bootloader) version-main: 4.04.709.1
(bootloader) version-misc: PVT SHIP S-OFF
(bootloader) serialno: ------------------
(bootloader) imei: -----------------------
(bootloader) meid: 00000000000000
(bootloader) product: deluxe_ub1
(bootloader) platform: HBOOT-8064
(bootloader) modelid: PL9911000
(bootloader) cidnum: 11111111
(bootloader) battery-status: good
(bootloader) battery-voltage: 4195mV
(bootloader) partition-layout: Generic
(bootloader) security: off
(bootloader) build-mode: SHIP
(bootloader) boot-mode: FASTBOOT
(bootloader) commitno-bootloader: dirty-ae8bbb39
(bootloader) hbootpreupdate: 11
(bootloader) gencheckpt: 0
all: Done!
finished. total time: 0.089s
QUERY : Should I be concerned regarding
i. (bootloader) platform: HBOOT-8064
ii. (bootloader) hbootpreupdate: 11, because in Kairi's firmware zip the android-info reads
1) CID H_061 (I changed it to 11111111)
2) hbootpreupdate:3 (This I did not change)
2. Relocked the boot loader (after checking if I could unlock it again through the previous code.bin. I did this successfully but without Selecting 'Yes' option at the end of the process on my device)
C:\Fastboot>fastboot oem lock
...
(bootloader) Lock successfully...
(bootloader) mipi display off
(bootloader) mipi_dsi_cmds_tx_ext
(bootloader) pm8921_vreg_disable function, vreg_id = 1
(bootloader) pm8921_vreg_disable function, vreg_id = 38
(bootloader) TZ_HTC_SVC_DISABLE ret = -2228225 (0xFFDDFFFF)
(bootloader) [HTC]PS_HOLD resets device!
FAILED (status read failed (Too many links))
finished. total time: 1.246s
C:\Fastboot>fastboot flash unlocktoken Unlock_code.bin
< waiting for device >
target reported max download size of 1514139648 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.136s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.009s]
finished. total time: 0.148s
NOTE: Both the times device booted into bootloop.
3. Flashing Kairi's firmware-kk.zip through RUU
a. Rebooted in RUU
C:\Fastboot>fastboot oem rebootRUU
...
(bootloader) Start Verify: 0
OKAY [ 0.053s]
finished. total time: 0.055s
b. Flashed firmware-kk (remember the file CID changed to 11111111
C:\Fastboot>fastboot flash zip firmware-kk.zip
target reported max download size of 1514139648 bytes
sending 'zip' (19401 KB)...
OKAY [ 2.007s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[hboot] unzipping for pre-update check...
(bootloader) start image[hboot] flushing...
(bootloader) [RUU]WP,hboot,0
(bootloader) [RUU]WP,hboot,99
(bootloader) [RUU]WP,hboot,100
(bootloader) ...... Successful
FAILED (remote: 90 hboot pre-update! please flush image again immediately)
finished. total time: 3.490s
C:\Fastboot>
C:\Fastboot>fastboot flash zip firmware-kk.zip
target reported max download size of 1514139648 bytes
sending 'zip' (19401 KB)...
OKAY [ 2.016s]
writing 'zip'...
(bootloader) zip header checking...
(bootloader) zip info parsing...
(bootloader) checking model ID...
(bootloader) checking custom ID...
(bootloader) start image[sbl1-1] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-1,0
(bootloader) [RUU]UZ,sbl1-1,100
(bootloader) signature checking...
(bootloader) verified fail
(bootloader) ..... Bypassed
(bootloader) start image[sbl1-2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl1-2,0
(bootloader) [RUU]UZ,sbl1-2,100
(bootloader) signature checking...
(bootloader) [RUU]WP,sbl1-2,0
(bootloader) [RUU]WP,sbl1-2,100
(bootloader) ...... Successful
(bootloader) start image[sbl2] unzipping & flushing...
(bootloader) [RUU]UZ,sbl2,0
(bootloader) [RUU]UZ,sbl2,100
(bootloader) [RUU]WP,sbl2,0
(bootloader) [RUU]WP,sbl2,100
(bootloader) ...... Successful
(bootloader) start image[sbl3] unzipping & flushing...
(bootloader) [RUU]UZ,sbl3,0
(bootloader) [RUU]UZ,sbl3,100
(bootloader) [RUU]WP,sbl3,0
(bootloader) [RUU]WP,sbl3,100
(bootloader) ...... Successful
(bootloader) start image[radio] unzipping & flushing...
(bootloader) [RUU]UZ,radio,0
(bootloader) [RUU]UZ,radio,8
(bootloader) [RUU]UZ,radio,13
(bootloader) [RUU]UZ,radio,22
(bootloader) [RUU]UZ,radio,31
(bootloader) [RUU]UZ,radio,40
(bootloader) [RUU]UZ,radio,49
(bootloader) [RUU]UZ,radio,58
(bootloader) [RUU]UZ,radio,67
(bootloader) [RUU]UZ,radio,75
(bootloader) [RUU]UZ,radio,80
(bootloader) [RUU]UZ,radio,89
(bootloader) [RUU]UZ,radio,99
(bootloader) [RUU]UZ,radio,100
(bootloader) [RUU]WP,radio,0
(bootloader) [RUU]WP,radio,35
(bootloader) [RUU]WP,radio,71
(bootloader) [RUU]WP,radio,100
(bootloader) ...... Successful
(bootloader) start image[rcdata] unzipping & flushing...
(bootloader) [RUU]UZ,rcdata,0
(bootloader) [RUU]UZ,rcdata,42949671
(bootloader) [RUU]WP,rcdata,0
(bootloader) [RUU]WP,rcdata,42949671
(bootloader) ...... Successful
OKAY [ 10.628s]
finished. total time: 12.650s
Note: In the device the green bar did not reach the end. And did not reboot.
c. 'fastboot reboot bootloader' - command not recognized
d. 'fastboot reboot' - rebooted into bootloop
e. Manually booted the device into bootloader.
4. Getvar all - Same as previous.
5. Unlocked the bootloader.
C:\Fastboot>fastboot flash unlocktoken Unlock_code.bin
target reported max download size of 1514139648 bytes
sending 'unlocktoken' (0 KB)...
OKAY [ 0.136s]
writing 'unlocktoken'...
(bootloader) unlock token check successfully
OKAY [ 0.010s]
finished. total time: 0.149s
Note: The device automatically rebooted into bootloop yet again. Manually rebooted to bootloader it shows *** UNLOCKED ***
6. Re flashed Kairi's TWRP
C:\Fastboot>fastboot flash recovery TWRP-2-7-Kairi.img
target reported max download size of 1514139648 bytes
sending 'recovery' (10572 KB)...
OKAY [ 1.564s]
writing 'recovery'...
OKAY [ 0.977s]
finished. total time: 2.546s
7. Entered Recovery from the device. (To install Kairi's reset kernel) Did not wipe cache/dalvik after installation
Note: - 'adb reboot bootloader' did not work at recovery, thou
C:\Fastboot>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
FA34HPN00627 recovery
C:\Fastboot>adb reboot bootloader
8. Entered bootloader thru TWRP options on the device.
9. Flashed boot.img (extracted from InsertCoin 3.0.6 Zip). Did not erase cache after this.
C:\Fastboot>fastboot flash boot boot.img
target reported max download size of 1514139648 bytes
sending 'boot' (6500 KB)...
OKAY [ 0.926s]
writing 'boot'...
OKAY [ 0.747s]
finished. total time: 1.677s
10. Entered recovery to install InsertCoin Rom.
a. Selected - Perform a full wipe in the installer.
b. Deselected all the checkmarks (for HTC + Google)
c. Selected - 'Enable Cache - All times' in the end
d. Install. (Please refer the attached screen shots)
e. Reboot your Device now from the installer. (HOPE TO boot into android. Fingers crossed).
f. Again Bootloop.
g. Rebooted into bootloader
h. Fastboot the boot image once again erased cache after that.
C:\Fastboot>fastboot flash boot boot.img
target reported max download size of 1514139648 bytes
sending 'boot' (6500 KB)...
OKAY [ 0.926s]
writing 'boot'...
OKAY [ 0.745s]
finished. total time: 1.675s
C:\Fastboot>fastboot erase cache
******** Did you mean to fastboot format this partition?
erasing 'cache'...
OKAY [ 0.068s]
finished. total time: 0.070s
I. Still in bootloop.
Please help/advice.
Hi Vikram.
This could be the blind leading the blind. But I will help out as much as I can.
I had the same problem with IC boot looping and especially with my nandroid backups. See if you can download a different rom and get that on your sd card and flash that. You can try BOA Butterfly v8.0 that always booted up for me when IC wouldn't. I also found a stock nandroid x920d backup that worked. At least I had my device working until I had the time to sort out IC on my device.
Now a couple of your queries.
My cid 11111111
HBOOT 1.57
The green progress bar never reaches the end it always stays at about 90% and reboot bootloader command should be like this
"adb reboot-bootloader" without the quotes
Sorry Vikram all over the place tonight I just finished work. Hope this helps. Plus the best information I can give you as well is search this site. everything you need is on here with a little searching. Only been doing this since July and I also tried to flash every rom out there only to discover that they all don't work. Got myself out of a few bootloops.
Try what I mentioned above and see how you go with that.
Clarkie_955i said:
Hi Vikram.
This could be the blind leading the blind. But I will help out as much as I can.
I had the same problem with IC boot looping and especially with my nandroid backups. See if you can download a different rom and get that on your sd card and flash that. You can try BOA Butterfly v8.0 that always booted up for me when IC wouldn't. I also found a stock nandroid x920d backup that worked. At least I had my device working until I had the time to sort out IC on my device.
Now a couple of your queries.
My cid 11111111
HBOOT 1.57
The green progress bar never reaches the end it always stays at about 90% and reboot bootloader command should be like this
"adb reboot-bootloader" without the quotes
Sorry Vikram all over the place tonight I just finished work. Hope this helps. Plus the best information I can give you as well is search this site. everything you need is on here with a little searching. Only been doing this since July and I also tried to flash every rom out there only to discover that they all don't work. Got myself out of a few bootloops.
Try what I mentioned above and see how you go with that.
Click to expand...
Click to collapse
Thanks A TON Clarkie,
Your reply is very much appreciated. It seems like a ray of hope in a dark tunnel. Really grateful to you.
Now coming back to the matter at hand -
I had earlier tried to
1. Tried to flash 'NOS_m7_v3.0.0_dlxbu1' thru Recovery, was successful but when tried to boot, got stuck again in bootloop. Then again installed InserCoin.
Note - Maybe I did not perfom a wipe cache & definately did not flash the boot image thru fastboot after flashing the above rom.
Secondly I'm neither able to reboot from bootloader mode into recovery nor vice verca.
Thirdly, I cannot flash any zip from bootloader (but able to flash image files thru bootloader & install zip thru recovery); & no "fastboot reboot recovery" from bootloader mode and no "adb reboot bootloader"
from recovery (same with RUU "fastboot reboot bootloader", though in recovery & fastboot mode "adb/fastboot devices" show my device).
Fourthly, whenever I reboot into system/android I get Two bootscreens - 1. HTC Quietly Brilliant & the device gets disconnected and connected again and the second boot screen is HTC One.
Finally it stays at the HTC One screen for some time and suddenly there is some very slight variation in the brightness of the bootscreen, then the capacitive buttons (Back, Home & Recent app) lightens and it
reboots.
2. Tried to restore from TWRP Backup (when I was successfully running InserCoin for the first time) but again the bootloop. I also have one of NOS_m7_v3.0.0 (When I was S-On), that I've not tried yet as I'm afraid to get
back to S-On and bootloop at the same time..
3. Meanwhile, today a couple of hours ago, I came across this thread - http://forum.xda-developers.com/showthread.php?t=2208833, and
performed an advanced wipe thru recovery (wiping everythingh except external sd card). Wiped Dalvik Cache. TWRP Backup. Rebooted. (For a lovely change) Got stuck at boot screen -HTC Quitely Briliant.
(maybe no OS installed).
4. Manually went into bootloader and then recovery. Installed InsertCoin again. At the end it said no SuperSU. Swiped to install it. Reboot. Got stuck at Bootloop.
Please try to Suggest:
A. When to flash boot.img - before or after installing the rom.
B. Does restoring S-On state backup will effect my S-Off condition.
Thanx In Advance.
1 + 1 = 11
Will Definately try BOA's Rom meanwhile.
HI Clarkie,
Tried the download links at BOA's ROM thread in the forum. Doesen't work.
Can you provide me a link.
Ok Vikram.
From what I have done and read I have always done a factory reset thru recovery before flashing any rom. Also try re flashing TWRP same version. I also got stuck on HTC ONE screen and turned the device of at power button and back on and it booted up fine. I would keep your device at s.off and i flashed the boot img after the rom because the device would not boot. Sorry for the short replies I am not that quick on the keyboard.
Here is the link for boa
http://forum.xda-developers.com/showthread.php?t=2656094
Spare link 4 is still up.
Just keep going on it. It is a process of thinking what worked before and why it not working now.
Keep me posted
Clarkie_955i said:
Ok Vikram.
From what I have done and read I have always done a factory reset thru recovery before flashing any rom. Also try re flashing TWRP same version. I also got stuck on HTC ONE screen and turned the device of at power button and back on and it booted up fine. I would keep your device at s.off and i flashed the boot img after the rom because the device would not boot. Sorry for the short replies I am not that quick on the keyboard.
Here is the link for boa
http://forum.xda-developers.com/showthread.php?t=2656094
Spare link 4 is still up.
Just keep going on it. It is a process of thinking what worked before and why it not working now.
Keep me posted
Click to expand...
Click to collapse
Thanks Clarkie,
I'll give it a shot.
And let you know.
Capt Vikram Sandhu said:
Thanks Clarkie,
I'll give it a shot.
And let you know.
Click to expand...
Click to collapse
Check your commands you need one of these ---- between adb reboot-bootloader. That is what I was trying to say last night. Not sure if you got it.
Cheers
Clarkie_955i said:
Check your commands you need one of these ---- between adb reboot-bootloader. That is what I was trying to say last night. Not sure if you got it.
Cheers
Click to expand...
Click to collapse
Got it Sir,
Thanx.
P.S. Downloading the BOA Rom from the link. Will let you know what happens.
Capt Vikram Sandhu said:
Got it Sir,
Thanx.
P.S. Downloading the BOA Rom from the link. Will let you know what happens.
Click to expand...
Click to collapse
No worries.
Remember if it gets stuck on htc screen power off with power button and restart. See how you go.
Good Luck
Clarkie_955i said:
No worries.
Remember if it gets stuck on htc screen power off with power button and restart. See how you go.
Good Luck
Click to expand...
Click to collapse
Hi Clarkie,
Tried the following:
Installed TWRP 2.6.3
Factory reset from recovery.
Installed BOA V8.0 thru recovery (Couldn't understand the language of aroma installer, but went ahead both the times).
Device Rebooted into bootloop again.
Powered off with only the power button, but then it again restarted into bootloop.
Flashed the boot.img thru fastboot. Reboot. Again bootloop.
Went to Recovery. Wiped everythingh except Micro SDcard
Installed the rom thru recovery install zip
Aroma Installer Finished Screen -> from recovery reboot options went into fastboot. Flashed the boot.img.
Rebooted to System - Back to square 1 in bootloop.
Also during the bootloop pressing down the power button does not power off & restarts the device. But the screen goes off for a few seconds and automatically boots intp the bootloop.
FYI -
I'm using a partitioned sd card. with 1. FAT32, 2. ext4 & 3. Linux SWAP. And thru recovery file manager it showed sd-ext & superuser folders in the root. I'll give it a try on an unpartitioned card.
had successfully, flashed recovery-clockwork-touch-6.0.3.1-dlxub1 before flashing TWRP 2.6.3. But the CWMod recovery shows the following:
E:Can't mount /cache/recovery/log
E:Can't open /cache/recovery/log
E:Can't mount /cache/recovery/last_log
E:Can't open /cache/recovery/last_log
I tried adb reboot-bootloader but nothing happens.
Please try to suggest from here.
How can I check (from Bootloader/recovery) if my device is rooted/unrooted.
I mean when the splash screens stays on for more than a few minutes and not in boot loop hit the power button to off then back on. That has worked for me. I am not sure about your partitioned sd card. I just store things on mine.
Have a look at this. http://forum.xda-developers.com/showthread.php?t=2283896
I had the same similar errors a while ago but I cant remember how I fixed it. Well I do. I fixed one error at a time and lots of searching.
Clarkie_955i said:
I mean when the splash screens stays on for more than a few minutes and not in boot loop hit the power button to off then back on. That has worked for me. I am not sure about your partitioned sd card. I just store things on mine.
Have a look at this. http://forum.xda-developers.com/showthread.php?t=2283896
I had the same similar errors a while ago but I cant remember how I fixed it. Well I do. I fixed one error at a time and lots of searching.
Click to expand...
Click to collapse
I have done again the following steps as you said:
1. Started the Device.
2. First Splash screen came up - HTC quietly Briliant.
3. Second Splash Screen came up - HTC One.
4. Waited for one/two seconds and pressed continuosly on the power button.
5. Screen went totally black/maybe powered off.
6. Removed my finger from the Power button in order to press it back to power the device.
7. Before I can press it is back on the first splash screen pops up and the bootloop starts.
8. Even If I do not release the power button after the 5th step it automatically reboots & bootloop starts.
I did try this from the first bootscreen and also after complete power down from bootloader/recovery mode.
Meanwhile I'll search the link you gave.
I think that maybe I'm unrooted now because when i try thru recovery - advance - file manager, I cannot see any file in /system/bin/ (where there should have been a su file there.)
Thanks for your reply . will keep you posted.
Your replies mean a lot to me.
Hi Clarkie,
Re-read all of your posts and guidance.
Motivated by this and the links provided espaicially by you and reply from abhinav.tella I think I'm able to lock on the problem (perhaps).
Right now compiling it and will post with further details.
Kindly try to walk me thru it with your suggestions and guidance.
Thanx in advance.
Bits and Pieces
Hi Clarlie,
Thanks for your time & energy till date. You are kind enough to help out somebody very selflessly on your part. I'm motivated and have inculcated the same.
Anyway, I tried to understand the whole thing piece by piece. Also I have assimilated a few screenshots (I have many others if required.)
The following is only what I did & now think could be the cause.
First of all; I had successfully installed and was running InsertCoin a few days ago. See Step by Sep as per the numbered images attached with this and several within the next few following posts.
1
1. 1. Unlocked, rooted & running InserCoin, (but a Kernel & firmware based on 4.2 custom rom) --- 28-11-14 17-23hrs
1. 2. Achieved S-Off with XUNUS's (http://forum.xda-developers.com/htc-butterfly/help/qa-insertcoin-3-0-6-dlxub1-android-4-4-t2950052)help & updated to TWRP 2.7 Kairi's along with reste-kernel-ub1 again Kairi's, 29-11-14 19-32.
1. 3. bootloader after s-off before revone, 29-11-14 23-09.
1. 4. bootloader after removing TAMPERED thru revone, 30-11-14 00-02
Cont to next to post...
Capt Vikram Sandhu said:
Hi Clarlie,
Thanks for your time & energy till date. You are kind enough to help out somebody very selflessly on your part. I'm motivated and have inculcated the same.
Anyway, I tried to understand the whole thing piece by piece. Also I have assimilated a few screenshots (I have many others if required.)
The following is only what I did & now think could be the cause.
First of all; I had successfully installed and was running InsertCoin a few days ago. See Step by Sep as per the numbered images attached with this and several within the next few following posts.
1
1. 1. Unlocked, rooted & running InserCoin, (but a Kernel & firmware based on 4.2 custom rom) --- 28-11-14 17-23hrs
1. 2. Achieved S-Off with XUNUS's (http://forum.xda-developers.com/htc-butterfly/help/qa-insertcoin-3-0-6-dlxub1-android-4-4-t2950052)help & updated to TWRP 2.7 Kairi's along with reste-kernel-ub1 again Kairi's, 29-11-14 19-32.
1. 3. bootloader after s-off before revone, 29-11-14 23-09.
1. 4. bootloader after removing TAMPERED thru revone, 30-11-14 00-02
Cont to next to post...
Click to expand...
Click to collapse
Ok Vikram.
I found this for you. It is a very good write up with great detail. http://forum.xda-developers.com/showthread.php?t=2630214
Hope this gets you going.
---------- Post added at 07:37 AM ---------- Previous post was at 07:29 AM ----------
Clarkie_955i said:
Ok Vikram.
I found this for you. It is a very good write up with great detail. http://forum.xda-developers.com/showthread.php?t=2630214
Hope this gets you going.
Click to expand...
Click to collapse
You might want to change your cid. Thought you was supercid 11111111

[Q] Help to recovery Sensation after bad flash

Hello everyone.
I am hoping someone might be able to help me out.
I had been using the sensation for a while with the s-off bootloader with no problems.
Recently I tried to update it to see how it would work on the lolipop builds that are out.
I updated the recovery to 2.8.3.0 TWRP and tried to flash the rom.
It looked like it completeled normally but when I went to restart the phone it will only boot into the fastboot of the boot loader. I can not get it to boot into the rom or recovery.
I have tried to reflash the recovery using fastboot but get the following error:
FAILED (remote: image update error)
I used the command (fastboot flash recovery recovery.img) to try and flash a previous one that worked.
I can use fastboot to boot the recovery though and then it will load.
But when the recovery is loaded or by using the adb terminal I can not access any of the partitions.
It seems like the partition table is corrupted.
I have been trying to find a hboot to reflash but I also can not seem to use the command
fastboot OEM reboot RUU
That command gives me the following error
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) erase sector 130560 ~ 131071 (512)
(bootloader) emmc_erase(1852): sd_write_sector failed!
OKAY [ 0.081s]
finished. total time: 0.082s
Currently the phone is on Firmware 3.33
s-off
hboot 1.27.110
Does anyone know where I might be able to find the firmware / hboot to reflash to see if that fixes the partitions on the phone?
Or any other way to fix this?
I am finding it hard to try and dig up files that have working links for this device anymore.
If I am not mistaken, reflashing the firmware should be able to fix it though.
I think I might need to find the RUU and just reflash back to stock and am waiting on the download for that as we speak. Just dreading going through and rerooting the phone again.
The wire part was really tricky.
Any help would be greatly appreciated.
Thank you for your time to read this.
TheArtiszan said:
Hello everyone.
I am hoping someone might be able to help me out.
I had been using the sensation for a while with the s-off bootloader with no problems.
Recently I tried to update it to see how it would work on the lolipop builds that are out.
I updated the recovery to 2.8.3.0 TWRP and tried to flash the rom.
It looked like it completeled normally but when I went to restart the phone it will only boot into the fastboot of the boot loader. I can not get it to boot into the rom or recovery.
I have tried to reflash the recovery using fastboot but get the following error:
FAILED (remote: image update error)
I used the command (fastboot flash recovery recovery.img) to try and flash a previous one that worked.
I can use fastboot to boot the recovery though and then it will load.
But when the recovery is loaded or by using the adb terminal I can not access any of the partitions.
It seems like the partition table is corrupted.
I have been trying to find a hboot to reflash but I also can not seem to use the command
fastboot OEM reboot RUU
That command gives me the following error
...
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) [SD_HW_ERR] read data fail in CMD18
(bootloader) [SD_HW_ERR] SD: Read data fail..
(bootloader) [ERR] partition_read_emmc(732): error 2
(bootloader) Start Verify: 0
(bootloader) erase sector 130560 ~ 131071 (512)
(bootloader) emmc_erase(1852): sd_write_sector failed!
OKAY [ 0.081s]
finished. total time: 0.082s
Currently the phone is on Firmware 3.33
s-off
hboot 1.27.110
Does anyone know where I might be able to find the firmware / hboot to reflash to see if that fixes the partitions on the phone?
Or any other way to fix this?
I am finding it hard to try and dig up files that have working links for this device anymore.
If I am not mistaken, reflashing the firmware should be able to fix it though.
I think I might need to find the RUU and just reflash back to stock and am waiting on the download for that as we speak. Just dreading going through and rerooting the phone again.
The wire part was really tricky.
Any help would be greatly appreciated.
Thank you for your time to read this.
Click to expand...
Click to collapse
Okay so the only good news I can see is that if you can make the RUU run it will not s-on your phone so rooting will be easy but, if fastboot oem reboot RUU doesn't work then your in alot of trouble. When you download the RUU (any I'd one for the sensation of XE will do) run it and then extract the .zip (search on Google if you are unsure how to) when you have that extract everything and then move system.img data.img and anything rom related out of the folder. Your aiming to only have hboot related items and the android txt file in there. Zip it back up by highlighting all the files and make a zip file, not by zipping the folder. Rename the zip file to the device model number with img (i think its pg58img.zip) then pass it to your sdcard and then reboot to hboot.
If your hboot can "update" it will hopefully be able to restore/remake your damaged partition table but if that fails your options are really limited. A J-tag would be able to restore the devices partition tables forcefully but you would need a repair shop to do that.
Sent from my LG-D802 using Tapatalk
heavy_metal_man said:
A J-tag would be able to restore the devices partition tables forcefully but you would need a repair shop to do that.
Sent from my LG-D802 using Tapatalk
Click to expand...
Click to collapse
or if you know what to do about jtag method see here
http://forum.xda-developers.com/showthread.php?t=2775115
Yeah I think I'm toast then.
I tried grabbing the default Rom .zip and flash with boot loader and that failed.
Not sure if it needed to be on a gold card or not though.
TheArtiszan said:
Yeah I think I'm toast then.
I tried grabbing the default Rom .zip and flash with boot loader and that failed.
Not sure if it needed to be on a gold card or not though.
Click to expand...
Click to collapse
Shouldn't make a difference as you are s-off.
What happens if you issue the command. Fastboot getvar all
Does it work?
Sent from my LG-D802 using Tapatalk

Help please

Hi everyone, could you please help me i have a htc A9 and i face a bootloop . the phone hasn't the usb debugging on and it is S-on, i tried with fastboot to change the ruu but impossible always have failed in cmd prompt
Code:
(bootloader) kernel: lk
(bootloader) product: htc_hiaeuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 751200000
(bootloader) serialno: HT5ARBE06603
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: 352636071084888
(bootloader) version-main: 2.16.163.4
(bootloader) boot-mode: RUU
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PQ910000
(bootloader) cid: VODAP203
if someone has an idea i would appreciate coz i'm stuck
I tried to flash a rom using fastboot and i get this error message
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip 2PQ9IMG.zip
target reported max download size of 751200000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1029804250 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 278606042 is not a multiple of the block size 4096
sending sparse 'zip' (733590 KB)...
error: write_sparse_skip_chunk: don't care size 1029804250 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1029804250 is not a multiple of the block size 4096
OKAY [ 32.033s]
writing 'zip'...
(bootloader) HOSD CL#853511
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_h
(bootloader) RvMuM
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 22
(bootloader) [email protected]
FAILED (remote: 22 RU_HEADER_ERROR )
finished. total time: 57.319s
thanks for your help
kabelou said:
Hi everyone, could you please help me i have a htc A9 and i face a bootloop . the phone hasn't the usb debugging on and it is S-on, i tried with fastboot to change the ruu but impossible always have failed in cmd prompt
Code:
(bootloader) kernel: lk
(bootloader) product: htc_hiaeuhl
(bootloader) version: 1.0
(bootloader) max-download-size: 751200000
(bootloader) serialno: HT5ARBE06603
(bootloader) slot-count: 0
(bootloader) current-slot:
(bootloader) imei: 352636071084888
(bootloader) version-main: 2.16.163.4
(bootloader) boot-mode: RUU
(bootloader) version-baseband: [email protected]
(bootloader) version-bootloader: 1.0.0.0000
(bootloader) mid: 2PQ910000
(bootloader) cid: VODAP203
if someone has an idea i would appreciate coz i'm stuck
I tried to flash a rom using fastboot and i get this error message
Code:
C:\Program Files (x86)\Android\android-sdk\platform-tools>fastboot flash zip 2PQ9IMG.zip
target reported max download size of 751200000 bytes
Invalid sparse file format at header magi
error: write_sparse_skip_chunk: don't care size 1029804250 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 278606042 is not a multiple of the block size 4096
sending sparse 'zip' (733590 KB)...
error: write_sparse_skip_chunk: don't care size 1029804250 is not a multiple of the block size 4096
error: write_sparse_skip_chunk: don't care size 1029804250 is not a multiple of the block size 4096
OKAY [ 32.033s]
writing 'zip'...
(bootloader) HOSD CL#853511
(bootloader) ERR lzipv2_init : Cannot open file /dev/fastboot_download_h
(bootloader) RvMuM
(bootloader) ERR [SD_UPDATE_ERR] update_fb_ZIP_buf: can not find ZIP hea
(bootloader) der
(bootloader) ERR [SD_UPDATE_ERR] sddownload failed: 22
(bootloader) ERR Update zip file failed.
(bootloader) ERR ZIP ERROR, exit read zip loop
(bootloader) ERR ZIP signature checking failed...
(bootloader) Update zip file OK
(bootloader) ERR ZIP ERROR CODE, 22
(bootloader) [email protected]
FAILED (remote: 22 RU_HEADER_ERROR )
finished. total time: 57.319s
thanks for your help
Click to expand...
Click to collapse
What ruu version are you trying to flash?
Are you using htc_fastboot.exe or fastboot.exe?
alray said:
What ruu version are you trying to flash?
Are you using htc_fastboot.exe or fastboot.exe?
Click to expand...
Click to collapse
i tried a lot of ruu, an european ruu, vodaphone uk, etc
the htc_fastboot command doesn't work coz it's an old version, i tried to find the newest one but i didn't.
And the fastboot.exe it's the last version in android sdk manager and it's the only thing working...i cannot found ruu with cid vodap203....the phone is from france so if you can help me thanks
kabelou said:
i tried a lot of ruu, an european ruu, vodaphone uk, etc
the htc_fastboot command doesn't work coz it's an old version, i tried to find the newest one but i didn't.
And the fastboot.exe it's the last version in android sdk manager and it's the only thing working...i cannot found ruu with cid vodap203....the phone is from france so if you can help me thanks
Click to expand...
Click to collapse
You must use htc_fastboot.exe to flash RUU not fastboot.exe . The only ruu version that will work on your phone is 2.16.163.4 check on easy-firmware.com it's there
alray said:
You must use htc_fastboot.exe to flash RUU not fastboot.exe . The only ruu version that will work on your phone is 2.16.163.4 check on easy-firmware.com it's there
Click to expand...
Click to collapse
Hello Alray,
i tried to download the RUU you said but its not possible becaus i have to pay for it? do you have any access or are you able to download it ? if not no worries and thanks for help!!!.
Flahable zip
Would you like a flashable zip of the htc one a9 boostmobile/sprint stock rom with root?
anonymouseli said:
Would you like a flashable zip of the htc one a9 boostmobile/sprint stock rom with root?
Click to expand...
Click to collapse
Am glad that you asked this, I know that this is a different thread but I have been looking for a nougat flashable zip, am using HTC One A9 sprint version 1.10.651.1 hiaewhl S-OFF and boot loader unlocked, it's rooted with twrp 2.8.7.0 installed..I just want to grab this opportunity. I need to update my phone to nougat and return to stock.. I saw RUU.exe but I realized that you will flash firmware first before RUU.exe ,I didn't see RUU.zip for hiaewhl and I have not use RUU before..help me out.. I need any rom I can flash through custom recovery.. Is it safe for me to flash custom rom for hiaeul on my hiaewhl being S-OFF and bootloader unlocked? Pls your reply..
Sent from my 2PQ93 using XDA-Developers Legacy app
CAMERON1988 said:
Am glad that you asked this, I know that this is a different thread but I have been looking for a nougat flashable zip, am using HTC One A9 sprint version 1.10.651.1 hiaewhl S-OFF and boot loader unlocked, it's rooted with twrp 2.8.7.0 installed..I just want to grab this opportunity. I need to update my phone to nougat and return to stock.. I saw RUU.exe but I realized that you will flash firmware first before RUU.exe ,I didn't see RUU.zip for hiaewhl and I have not use RUU before..help me out.. I need any rom I can flash through custom recovery.. Is it safe for me to flash custom rom for hiaeul on my hiaewhl being S-OFF and bootloader unlocked? Pls your reply..
Sent from my 2PQ93 using XDA-Developers Legacy app
Click to expand...
Click to collapse
You should be alright ill upload it tomorrow
anonymouseli said:
You should be alright ill upload it tomorrow
Click to expand...
Click to collapse
I will be grateful
Sent from my 2PQ93 using XDA-Developers Legacy app
Stock Rom Rooted
CAMERON1988 said:
I will be grateful
Sent from my 2PQ93 using XDA-Developers Legacy app
Click to expand...
Click to collapse
Okay here is a link to download the rom becuase , i just finish uploading it and its around 4gbs or so.
https://anonfile.com/E1P1E7mdbb/TWRP_zip
Steps to recover
1) First thing you should do is extract the rom, DO NOT FLASH THE ZIP FILE !!! .
2)Delete any old twrp folders in your sd card or phone storage, dont worry it will not affect the recovery itself.
3))Put the twrp folder in your device or sd card, however you can transfer it, its better if its on an sd card(make sure the folder says twrp).
4)Turn off the device and reboot into recovery.
5)Afterwards format the entire phone (Dont use factorey reset, use format data)just make sure you dont delete anything from the sd card.
6) Next go into restore or backup whatever its called and restore the rom from your sdcard, it should automatically detect the folder and if it doesnt try choosing the folder manually.
7) reboot the phone and give it sometime and if doesn't boot up after 20 minutes delete the cache or factory reset.
8) let me know if you got any questions email: [email protected]
---------- Post added at 06:32 PM ---------- Previous post was at 06:30 PM ----------
anonymouseli said:
Okay here is a link to download the rom becuase , i just finish uploading it and its around 4gbs or so.
https://anonfile.com/E1P1E7mdbb/TWRP_zip
Steps to recover
1) First thing you should do is extract the rom, DO NOT FLASH THE ZIP FILE !!! .
2)Delete any old twrp folders in your sd card or phone storage, dont worry it will not affect the recovery itself.
3))Put the twrp folder in your device or sd card, however you can transfer it, its better if its on an sd card(make sure the folder says twrp).
4)Turn off the device and reboot into recovery.
5)Afterwards format the entire phone (Dont use factorey reset, use format data)just make sure you dont delete anything from the sd card.
6) Next go into restore or backup whatever its called and restore the rom from your sdcard, it should automatically detect the folder and if it doesnt try choosing the folder manually.
7) reboot the phone and give it sometime and if doesn't boot up after 20 minutes delete the cache or factory reset.
8) let me know if you got any questions email: [email protected]
Click to expand...
Click to collapse
w.
---------- Post added at 06:32 PM ---------- Previous post was at 06:32 PM ----------
anonymouseli said:
Okay here is a link to download the rom becuase , i just finish uploading it and its around 4gbs or so.
https://anonfile.com/E1P1E7mdbb/TWRP_zip
Steps to recover
1) First thing you should do is extract the rom, DO NOT FLASH THE ZIP FILE !!! .
2)Delete any old twrp folders in your sd card or phone storage, dont worry it will not affect the recovery itself.
3))Put the twrp folder in your device or sd card, however you can transfer it, its better if its on an sd card(make sure the folder says twrp).
4)Turn off the device and reboot into recovery.
5)Afterwards format the entire phone (Dont use factorey reset, use format data)just make sure you dont delete anything from the sd card.
6) Next go into restore or backup whatever its called and restore the rom from your sdcard, it should automatically detect the folder and if it doesnt try choosing the folder manually.
7) reboot the phone and give it sometime and if doesn't boot up after 20 minutes delete the cache or factory reset.
8) let me know if you got any questions email: [email protected]
Click to expand...
Click to collapse
w.
OK thanks a lot, I will download it when I subscribe to a data plan because there's no Wi-Fi here
Sent from my 2PQ93 using XDA-Developers Legacy app
I couldn't download the file as it is failing whenever it gets to 1.97Gb I have tried several times but still the same I have spent almost 7gb but couldn't still get it downloaded..I don't know whether the fault is from the link or not
Sent from my 2PQ93 using XDA-Developers Legacy app

Moto G 2014 XT1033 - Boot Loop

Hi, I am new here and I wanted some assistnce to get my old Moto G working. Its stuck in boot loop. When I power it on, it is looping on the Moto screen. I tried flashing it seeing some old threads here and was getting remote failure. I also tried custom recovery but it was failing. I can see Motorola AD Interface on the PC and I have installed all drivers as well. Whatever i try just fails with the same message. "FAILED (remote failure)"
I also a saw thread which talked about the PC to show QLoader9008 in device manager but that also doesnt show in my device manager. I can just see Motorola ADB Interface.
Anything we can do to fix it. I'd really want it to get back to life if its possible.
Thank You for the help in advance.
Images tried
Motorola_Moto_G_XT1033_Falcon_ASIA_DS_5.1_LPBS23.13-56-2_CID7_CFC1
XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml by jame
Motorola_Moto_G_XT1033_FALCON_TIMBR_DS_5.1_LPBS23.13-56-2_CID12_5.1
Tools used
RSDLite 6.2.4
mfastboot-v2
Fastboot
Log Sample
F:\DownloadsFolder\Motorola_Moto_G_XT1033_Falcon_ASIA_DS_5.1_LPBS23.13-56-2_CID7_CFC1\Motorola_Moto_G_XT1033_Falcon_ASIA_DS_5.1_LPBS23.13-56-2_CID7_CFC\Firmware>fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 9.950s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 15.225s
If
maau1985 said:
Hi, I am new here and I wanted some assistnce to get my old Moto G working. Its stuck in boot loop. When I power it on, it is looping on the Moto screen. I tried flashing it seeing some old threads here and was getting remote failure. I also tried custom recovery but it was failing. I can see Motorola AD Interface on the PC and I have installed all drivers as well. Whatever i try just fails with the same message. "FAILED (remote failure)"
I also a saw thread which talked about the PC to show QLoader9008 in device manager but that also doesnt show in my device manager. I can just see Motorola ADB Interface.
Anything we can do to fix it. I'd really want it to get back to life if its possible.
Thank You for the help in advance.
Images tried
Motorola_Moto_G_XT1033_Falcon_ASIA_DS_5.1_LPBS23.13-56-2_CID7_CFC1
XT1033_FALCON_ASIA_DS_5.1_LPB23.13-56_cid7_CFC.xml by jame
Motorola_Moto_G_XT1033_FALCON_TIMBR_DS_5.1_LPBS23.13-56-2_CID12_5.1
Tools used
RSDLite 6.2.4
mfastboot-v2
Fastboot
Log Sample
F:\DownloadsFolder\Motorola_Moto_G_XT1033_Falcon_ASIA_DS_5.1_LPBS23.13-56-2_CID7_CFC1\Motorola_Moto_G_XT1033_Falcon_ASIA_DS_5.1_LPBS23.13-56-2_CID7_CFC\Firmware>fastboot flash partition gpt.bin
(bootloader) slot-count: not found
(bootloader) slot-suffixes: not found
(bootloader) slot-suffixes: not found
(bootloader) has-slotartition: not found
target reported max download size of 536870912 bytes
sending 'partition' (32 KB)...
OKAY [ 9.950s]
writing 'partition'...
(bootloader) This may take a few seconds, if a
(bootloader) different partition table is being
(bootloader) flashed since we need to backup
(bootloader) and restore a few partitions
(bootloader) Flashing primary GPT image...
(bootloader) Failed to write primary GPT.
(bootloader) Failed to program partition table
FAILED (remote failure)
finished. total time: 15.225s
Click to expand...
Click to collapse
If you have not already, first you need to unlock your bootlloader before flashing anything.

Question System gone to void after i ran this command at recovery.

I have Lineage18.1 unofficial installed in slot a,without thinking too much I flashed Evolution X 7 following the guide inside the post.Later I flash magisk for root to restore, but restore failed so I wonder if lineage could boot atfer flashed.Cause I found Evolution was installed in slot b .I thouht so maybe slot a still work?Of course not,it just stuck at the wobbling logo.Luckily noting important in it because it is not my main phone.
So I factory reset at Lineage recovery ,it boot successfully. Next, I tried to root again but failed and wasted lot of time .I decided to give and had a look at slot b,somehow I ran "fastboot set_active other" at recovery of Lineage then tap boot.As a result ,my phone show me a screen of red warning said novalid operating system could be found.And the bootloader became more simpler than before.
Most of fastboot commands don't work now.Like switch slot,falsh boot img etc.I don't know what happened exactly.Is there any way to fix it without send back to seller?Here are some info.Please tell me if any other information should be post.
(bootloader) current-slot: b
(bootloader) running-bl-slot: unknown/unknown
(bootloader) running-boot-lun: 2
(bootloader) slot-count: 1
(bootloader) slot-successful:_a: unknown
(bootloader) slot-successful:_b: unknown
(bootloader) slot-unbootable:_a: unknown
(bootloader) slot-unbootable:_b: unknown
(bootloader) slot-retry-count:_a: unknown
(bootloader) slot-retry-count:_b: unknown
(bootloader) logical-block-size: 0x1000
(bootloader) erase-block-size: 0x1000
Click to expand...
Click to collapse
Warning: skip copying boot image avb footer (boot partition size: 0, boot image size: 100663296).
Sending 'boot' (98304 KB) OKAY [ 2.288s]
Writing 'boot' (bootloader) Invalid partition name boot
FAILED (remote: '')
fastboot: error: Command failed
Click to expand...
Click to collapse
Slot b does not exist. supported slots are:
a
Click to expand...
Click to collapse
Just fixed it by flash stock firmware.

Categories

Resources