Database Info

Phone is Cycling between Bootloader Unlocked Screen and Motorola Sp

I just tried rooting my phone. The phone is cycling back and forth between the bootloader is unlocked screen and the Motorola splash screen.
To repeat some steps from a prior post.
My phone had QPR30.80-58-3 .
I downloaded that ROM and extracted the boot.img file.
I downloaded the latest Magisk Manager and installed it on my phone.
I ran through the patching process for boot.img.
I requested an unlock code from Motorola and unlocked the bootloader.
I flashed the patched boot image which patched partition b.
I flashed the patched boot image to partition a.
I rebooted which began the cycle.
I tried holding down the power button but it returns to the cycle.
I can get back to the bootloader with the Volume Down and Power buttons.
Any suggestions on what could get me back to a functioning phone, rooted or not rooted?

I would confirm the version of the boot image you flashed matches the version of the installed rom. You could also try to flash the unpatched / original boot.img to see if that gets you booting again.

dafunk60 said:
I would confirm the version of the boot image you flashed matches the version of the installed rom. You could also try to flash the unpatched / original boot.img to see if that gets you booting again.
Click to expand...
Click to collapse
I checked that the image I patched was from the QPR30.80-58-3 ROM which matched the level after the phone was updated.
I flashed that original boot image which flashed partition a and then rebooted. I did not flash partition b.
It first came up with the unlock warning screen. It sat on the Motorola splash screen for a noticeable amount of time followed by a yellow screen with a circle around the Motorola symbol. Finally it ended up on a blue Hello there screen with a yellow start button.
This screen was unresponsive. Eventually through various cyclings through all this I ended up on a screen that said Android could not boot and gave me an option of a factory reset. I did that but it did not help getting past the Hi there screen.
I went back and flashed the QPR30.80_58 image on both partitions a and b. This got me back to setting up the phone again. The phone is at QPR30.80_58. I am considering just rooting at this level.

So I tried patching the original QPR30.80_58 boot image. I did notice that it appeared the phone had automatically staged the QPRS30.80_58_3 update. I proceeded in (false) hopes that I could stop that.
It flashed the b partition. Ended up stuck in the bootloader unlock loop. I flashed the a partition but no change.
Previously I had ended up on a recovery screen automatically after some time. I could not force this to happen.
I tried flashing the original unpatched boot image but would end up on a non-functioning Hello there screen.
I tried adb recovery and adb shell but came back with device unauthorized.
I tried following some instructions on using fastboot erase userdata and fastboot erase cache. No change.
I finally found out that the Recovery menu was option off the bootloader screen. However, that came up with No command.
Lenovo Rescue did not want to recognize my XT2043-4 device.
I flashed the unpatched retail QPRS30.80_58_3 boot image to both a and b partitions. That got me back to a functioning phone. After getting through the login and setup steps I did find that it was at QPRS30.80_58_3.
Out of curiosity, I tried Lenovo Rescue again. I received a "Failed to match connected device. Reconnect device, then try again." which did not work.
Now I am at a loss.

DougPeterson said:
So I tried patching the original QPR30.80_58 boot image. I did notice that it appeared the phone had automatically staged the QPRS30.80_58_3 update. I proceeded in (false) hopes that I could stop that.
It flashed the b partition. Ended up stuck in the bootloader unlock loop. I flashed the a partition but no change.
Previously I had ended up on a recovery screen automatically after some time. I could not force this to happen.
I tried flashing the original unpatched boot image but would end up on a non-functioning Hello there screen.
I tried adb recovery and adb shell but came back with device unauthorized.
I tried following some instructions on using fastboot erase userdata and fastboot erase cache. No change.
I finally found out that the Recovery menu was option off the bootloader screen. However, that came up with No command.
Lenovo Rescue did not want to recognize my XT2043-4 device.
I flashed the unpatched retail QPRS30.80_58_3 boot image to both a and b partitions. That got me back to a functioning phone. After getting through the login and setup steps I did find that it was at QPRS30.80_58_3.
Out of curiosity, I tried Lenovo Rescue again. I received a "Failed to match connected device. Reconnect device, then try again." which did not work.
Now I am at a loss.
Click to expand...
Click to collapse
Happy to hear you have a working phone again! The lack of touchscreen response & the stuck at the hello screen issues are what others have reported when they used a boot image from a different version than on the phone. I suspect that something got confused between the version & slot somewhere along the way. As far as the Lenovo Rescue software not seeing the phone, it's communicating via ADB. If I recall correctly I needed to reauthorize the PC to connect via ADB after updating from 30.80-58 to 30.80-58-3. When I connect the phone via USB there's a popup on the phone asking to authorize the PC. Can you connect via ADB in the command line? If yes, you may want to reinstall the Lenovo software. If no, I would troubleshoot the ADB connection.
I originally rooted the 30.80-58 version. When 30.80-58-3 was released all I did was flash the unpatched boot.img, took the update OTA, let it reboot, then flash a patched boot.img from 30.80-58-3. All worked as expected, user data was intact.

dafunk60 said:
Happy to hear you have a working phone again! The lack of touchscreen response & the stuck at the hello screen issues are what others have reported when they used a boot image from a different version than on the phone. I suspect that something got confused between the version & slot somewhere along the way. As far as the Lenovo Rescue software not seeing the phone, it's communicating via ADB. If I recall correctly I needed to reauthorize the PC to connect via ADB after updating from 30.80-58 to 30.80-58-3. When I connect the phone via USB there's a popup on the phone asking to authorize the PC. Can you connect via ADB in the command line? If yes, you may want to reinstall the Lenovo software. If no, I would troubleshoot the ADB connection.
I originally rooted the 30.80-58 version. When 30.80-58-3 was released all I did was flash the unpatched boot.img, took the update OTA, let it reboot, then flash a patched boot.img from 30.80-58-3. All worked as expected, user data was intact.
Click to expand...
Click to collapse
I double checked that I had USB debugging set, given I have reset a couple of times. I revoked all USB access and reinstalled the Rescue app. I still get the Failed to match connected devices error.
fastboot device will list the phone.
adb devices or adb devices -l does not list anything and adb shell says no devices/emulators found.
If I try to get into recovery mode I get a No command screen. I have been trying to take notes on what I did but there have been gaps in all the fiddling. I may have only flashed one partition the last time I tried putting back a stock boot image.
For USB drivers I downloaded the latest from Motorola. Was that sufficient for this?

DougPeterson said:
I double checked that I had USB debugging set, given I have reset a couple of times. I revoked all USB access and reinstalled the Rescue app. I still get the Failed to match connected devices error.
fastboot device will list the phone.
adb devices or adb devices -l does not list anything and adb shell says no devices/emulators found.
If I try to get into recovery mode I get a No command screen. I have been trying to take notes on what I did but there have been gaps in all the fiddling. I may have only flashed one partition the last time I tried putting back a stock boot image.
For USB drivers I downloaded the latest from Motorola. Was that sufficient for this?
Click to expand...
Click to collapse
If you want to get into recovery, boot into the bootloader than do
Code:
fastboot reboot fastboot
That'll boot you into fastbootd which has an option to go to the real recovery

DougPeterson said:
I double checked that I had USB debugging set, given I have reset a couple of times. I revoked all USB access and reinstalled the Rescue app. I still get the Failed to match connected devices error.
fastboot device will list the phone.
adb devices or adb devices -l does not list anything and adb shell says no devices/emulators found.
If I try to get into recovery mode I get a No command screen. I have been trying to take notes on what I did but there have been gaps in all the fiddling. I may have only flashed one partition the last time I tried putting back a stock boot image.
For USB drivers I downloaded the latest from Motorola. Was that sufficient for this?
Click to expand...
Click to collapse
If adb isn't showing any devices connected that would explain why the rescue software cannot find your phone. Perhaps you don't have the correct driver installed. Windows Device Manager shows the phone as a Motorola ADB Device on my PC.
View attachment 5061327
Another possibility is that you have multiple versions of adb on your PC. Older versions won't work but the adb.exe in "C:\Program Files (x86)\Rescue and Smart Assistant" works for sure. With your phone booted into android & unlocked, plug it into your PC. Do you see the "USB debugging connected" on the phone? If you don't I would re-check that USB debugging is enabled. If you do see the debugging notification, on your PC, open a command prompt and navigate to "C:\Program Files (x86)\Rescue and Smart Assistant". Run
Code:
adb devices
Does adb find your phone?

Badly f*d Op7Pro. Need help to revert to stock

Hi,
First of all, yes, I have checked the other threads that talk about reverting to stock and I am still stuck.
So I installed Kang OS which is Android 11, and now I want to revert to stock. I have tried downloading multiple different versions of the fastboot ROM from the page https://androidfilehost.com/?w=files&flid=294300 and run the flash all batch file and every time I am either getting stuck in a boot loop or getting the Verity Crash Dump Screen. I have managed to reach the fastboot screen, and I am waiting on the fastboot screen, for someone to show me some way.
Thanks in Advance.

If you used a pin then your storage is encrypted and the rom you are trying to flash can't use it, that's why you're most likely stuck at boot.
I ran into the same issue and posted about it in the same thread. I think we will need a new version of TWRP as 3.4.0-0 would not accept my pin which had not changed.
To fix your issue, sadly, you'll need to wipe your storage:
Boot the phone into fastboot mode
Attach your USB cable to the phone/PC
Download and unzip the file I've attached (ADB/Fastboot)
Launch an elevated command window in the folder you extracted the attached zip to
Try the command fastboot devices and ensure that it reports the device correctly, if not then you need to install the latest OnePlus drivers
Type the following in the command window : fastboot -w (This will wipe the storage)
Try your rom again (TWRP should remain as the recovery if you had flashed it already, if not then copy the latest TWRP img file to the same folder as the ADB/Fastboot tools, use fastboot and type boot twrpfilename.img this will make the phone boot into TWRP recovery, you can then copy over the TWRP zip and flash it to recovery using the booted version of TWRP)
Once you've done the above you shouldn't really need to use the fastboot scripts as the latest rom should just flash from TWRP.

Get msm download tool for guacamole which is the codename of the op7p. I know the shorts with the global version I am unsure if this works with T-Mobile or others?

MSM is a bit of a severe fix when they've already confirmed they can still get fastboot, MSM is for completely bricked phones that can't access anything. Wiping the storage and going to fastboot will allow them to just flash recovery then flash the stock rom. Way easier.

Boot into twrp. Then format data. Phone will boot then.

I-Life s500 spark 5 help unbrick my phone (backed-up) create a .pac file

hello , i bricked my phone last week ,luckily me i have a backup of almost everything, but the problem is i don't know how to restore my backup i'm stuck on a boot-loop and my twrp is not working either (recovery partition got corrupted somehow) please read and guide me
first backup method using partitions backup (from play store work with root) :-
i backed-up every partition i have :-
boot.img miscdata.img wcnmodem.img wfixnv2.img
cache.img prodnv.img wcnruntimenv1.img wmodem.img
fbootlogo.img recovery.img wcnruntimenv2.img wruntimenv1.img
logo.img wcnfixnv1.img wdsp.img wruntimenv2.img
misc.img wcnfixnv2.img wfixnv1.img
(i unchecked system)
Second backup method using adb and backup.zip found in this thread (https://forum.hovatek.com/thread-854-page-8.html)
i got the exact same files as above
my device is a spreadtrum device "SP7731GEA_HD_scx35_sp7731gea_hd_5.1_I-life-S500-FS20160427_S500"
its called "I-Life s500 spark 5" not the "I-Life itel s500"
android 5.1
i'm using spd research tool, i want to make a .pac file to unbrick my device using the above files here's the problem
i realized that i don't have fdl1.bin and fdl2.bin i got them from older build android 4.4.2 from here (https://naijarom.com/life-itell-s500) confirmed working by flashing that rom it works put white screen (display issues not same gpu ...etc)
step 1 ok
step 2 :-
i don't have the following :-
u-boot.bin
u-boot-spl-16k.bin Is there a way to generate those from boot.img? i could use from lower build android 4.4.2 and maybe port it somehow
nvitem.bin which is equivalent to wfixnv1.img & wfixnv2.img
nvitem_wcn.bin equivalent to wcnfixnv1.img & wcnfixnv1.img
first they are spilted , Second not same format should be .bin how to do this??
for system.img i have a full twrp backup for spd tool to read it should be in .img format so i did the following:-
extracted using tar -xf -f system.ext4.win
repacked with dd if="extracted folder" of="new system.img"
now the command "file system.img" shows
system.img: Linux rev 1.0 ext4 filesystem data, UUID=57f8f4bc-abf4-655f-bf67-946fc0f9f25b (extents) (large files)
for the rest of the files i got them and in the right format (checked through "file" command comparing to a extracted .pac file)
please help me find a way to may problem thanks hovatek team for your hard work
NOTE: please don't point me to the firmware file i already found it and its not free and all forums are dead i did alot of research work if anyone interested see the links ALL ARE PAID AND DEAD FOURMS
I Life S500 Flash File Frp Lock Hang Logo Lcd Fix Firmware Stock-Rom
I LIFE S500 SPD ANDROID 5.1 FLASH FILE FRP LOCK DEAD PHONE RECOVERY HANG ON LOGO LCD WHITE PROBLEM SOLVED 1000% TESTED FIRMWARE !!RIPON MOBILE ZONE!! WELCOME TO Thanks For Visite My Site. And Here All King Off Exclusive Any Gsm Support, Firmware Tools Etc. And All Firmware Customer Care And Cm2...
www.gsmriponbd.com
I LIFE S500 Flash File Spd7731 5.1 Stock-Rom Lcd /Dead & Hang Logo Fix Firmware 100% Tested - Ok Firmware
I LIFE S500 SPD7731 5.1 UPDATE WHITE LCD FIX CAMERA, LOGO, SOLVED DONE FLASH FILE **OK FIRMWARE**
www.okfirmware.com
http://maqsoodmobilesoftware.blogspot.com/2018/01/i-life-s500-sp7731-pac-flash.html --file deleted
ILIFE S500 SPD SC7731GEA 5.1 CM2 READED FAC FILE FIRMWARE 100% TESTED BY MIM TELECOM
symphony.bangladesh.sony.x-bo.we.amra.without.password.mi. .sports.kingstar.flash.file.walton.maximus.wiko.fly.okapia.winstar.winmax.lava.discoveri
mimtelecomjatrabari.blogspot.com
I-life S500 Flash File}Firmware SP7731 5.1 Stock Rom - KaremaFirmware Flashfile
SP7731GEA_HD_scx35_sp7731gea_hd_5.1_I-life-S500-FS20160427_S500 I-LIFE S500 SP7731 FLASH FILE 5.1 FIRMWARE 100% i-life S500 Firmware Flash File SP7731 5.1 Stock Rom I-LIFE S500 FLASH FILE SP7731 5.1 FIRMWARE 100%TESTED Model Name : S500 Model Brand : S500 Model Device: scx35_sp7731gea_hd...
karemafirmwareflashfile.com

please guide me if i posted in the wrong forum thanks

Hint: Add I-Life s500 spark 5 to this thread's title thus mainly owners of such a device get addressed.

your phone has fastboot?

ineedroot69 said:
your phone has fastboot?
Click to expand...
Click to collapse
of course it has and i used it alot in the past, I boot from twrp or adb into bootloader (fastboot), Since recovery isnt working i cant boot into fastboot

tqw said:
of course it has and i used it alot in the past, I boot from twrp or adb into bootloader (fastboot), Since recovery isnt working i cant boot into fastboot
Click to expand...
Click to collapse
As executable's name fastboot implies it deals with device's bootloader.
BTW: You boot phone into its bootloader by means of ADB
Code:
adb devices
adb reboot fastboot <- or: adb reboot bootloader

Thank you for this update. i will looking into it.

jwoegerbauer said:
As executable's name fastboot implies it deals with device's bootloader.
BTW: You boot phone into its bootloader by means of ADB
Code:
adb devices
adb reboot fastboot <- or: adb reboot bootloader
Click to expand...
Click to collapse
i know the adb command , i wish it was that easy my device is in a bootloop so i can't access it from adb, so all ways to boot in fastboot are closed ;(

arnoldfewic said:
Thank you for this update. i will looking into it.
Click to expand...
Click to collapse
what update?

restore .img you backup via fastboot flash

tqw said:
i know the adb command , i wish it was that easy my device is in a bootloop so i can't access it from adb, so all ways to boot in fastboot are closed ;(
Click to expand...
Click to collapse
My understanding of a bootloop is that phone turns on and off again or stuck at the device logo or one can't get past the logo screen. No matter how it appears, at this time device's bootloader is running and on device-side it has started both the ADB and the Fastboot daemons - only Android OS can't get started for whatever reasons.

jwoegerbauer said:
My understanding of a bootloop is that phone turns on and off again or stuck at the device logo or one can't get past the logo screen. No matter how it appears, at this time device's bootloader is running and on device-side it has started both the ADB and the Fastboot daemons - only Android OS can't get started for whatever reasons.
Click to expand...
Click to collapse
woah i'm suprise that you are actually helping other instead of being passive aggressive that nice

jwoegerbauer said:
My understanding of a bootloop is that phone turns on and off again or stuck at the device logo or one can't get past the logo screen. No matter how it appears, at this time device's bootloader is running and on device-side it has started both the ADB and the Fastboot daemons - only Android OS can't get started for whatever reasons.
Click to expand...
Click to collapse
adb doesn't work untill android boot animation starts , thats for my phone idk about others , my device reaches the boot animation and reboot i tried many times adb isn't working , anyway i found the firmware on needrom but i need premium account i posted for help i'm currently waiting .......

Difficulty copying ROM - TWRP sees encrypted data only

I unlocked the phone via Xiaomi then patched the boot with magisk. Now I can confirm phone is rooted, flashed twrp twrp-3.6.2_9-0-tucana onto the phone. Phone boots into recover and twrp works but looking for rom to load only shows encrypted files.
Don't think Xiaomi supports side loading, keep getting error no permissions (user in plugdev group; are your udev rules wrong?) and I have killed server and restarted and done $ sudo usermod -aG plugdev $LOGNAME.
So I'm stuck with a phone that boots stock or loads twrp but I can't access files. How do I copy a rom over?
Note I read one comment that twrp should ask to unlock same as stock rom (screen pattern) but twrp is NOT asking for this.

Hi, i had the same problem and fixed by booting the same recovery image from fastboot with command:
Code:
fastboot boot recovery.img
The prompt for the pin appears magically.

Could Someone Upload Pixel 4A's Persist Image (Bootloop fixed :) but...)

Hello Dear Comunity.
I erased the Persist file by entering:
Code:
fastboot erase persist
But when i try to boot the device, it loops 3 times by from Google logo (freezes at this) to black screen and finishes it's loop by going to fastboot screen and says "No valid slot to boot ".
I also tried to fix the issue by trying Flash Android's website; but it seems due to it does not have the Persist Image in firmware, it still shows same error.
Therefore, i must flash the Persist Image.
If someone send the Persist Image of Pixel 4A, i will be able to fix the device.
This is the code, how you will copy your Pixel 4A's Persist Image on Adb Shell:
Code:
dd if=/dev/block/by-name/persist of=/sdcard/persist.img
For your assistance, thank you.

Update:
I fixed the bootloop issue by enabling Disable Vbmeta Verification and DM-Verity and device booted succesfully
However, there are no any sounds and sensors does not work; probably due to Persist Image missing.
Just one more step i must do in order to run device properly; flash the Persist.
Waiting for someone to send the Persist Image, thank you.

Xda-KFJ74 said:
Update:
I fixed the bootloop issue bt enabling Disable Vbmeta Verification and DM-Verity and device booted succesfully
However, there are no any sounds and sensors does not work; probably due to Persist Image missing.
Just one more step i must do in order to run device properly; flash the Persist.
Waiting for someone to send the Persist Image, thank you.
Click to expand...
Click to collapse
Which FW version?

AlexKarimov said:
Which FW version?
Click to expand...
Click to collapse
This could be fine:
13.0.0 (TQ3A.230605.011, Jun 2023
Or, it does not matter
you can send whatever you have and i can flash firmware that matches on your; unless your firmware is un-global.
Thank you Dear...

Hope this helps...
persist - Download - 4shared - Mojo King
Download persist at 4shared free online storage service
www.4shared.com