Database Info

Aquaris X5 cyanogen brick during root?

Hey,
I was trying to install CM on a BQ Aquaris X5 Cyanogen with the CM Instructions
but some how I failed :crying::crying::crying:
The Phone is rebooting every time first the TWP logo appears, then some red error messages appear and then the BQ logo appears
now everything returns.
It is not possible to power down the phone
If the Vol up and the Power button is hold for some time the FASTBOOT MODE starts.
Vol Down and Power has no function
What can I do to safe my Phone?

solved...

MaLuFi said:
solved...
Click to expand...
Click to collapse
Hey, I will get a X5 cyanogen edition in some days and I have a question : Where did you get instructions to move to CM?
Thanks

There is a german forum: http://www.android-hilfe.de/forum/bq-aquaris-x5-forum.2542/
Sent from my Aquaris X5 using XDA-Developers mobile app

oficial...
https://wiki.cyanogenmod.org/w/Paella_Info

How to get out of a boot loop
mousse04 said:
Hey, I will get a X5 cyanogen edition in some days and I have a question : Where did you get instructions to move to CM?
Thanks
Click to expand...
Click to collapse
I had that same problem last week, and I managed to resolve it.
My mistake had been to omit that reboot after unlocking the boot loader, so I got into that same boot loop with booting to recovery (TWRP) -> TWRP throwing errors -> TWRP causing a reboot -> rebooting into recovery again -> same error -> reboot -> etc. etc.
Here is what you can do (at least it worked for me); thanks also to the helpful people in the TWRP IRC channel on freenode:
Power the phone down during a boot loop:
It is not necessary to wait until the battery is completely drained by
rebooting hundreds of times.
There is a small time slot where the phone should accept "adb" commands during rebooting. So there is a chance to submit an "adb" command if you just send it over and over again. It may take some reboots to catch that time slot, but if you do it often enough, it should succeed at some time.
This worked nicely for me:
Make sure the latest Android SDK is installed (which includes the "adb" command).
Connect the phone to the PC with via USB.
While the boot loop is in progress, open a shell window on the PC (using
Linux in my case) and enter this command:
sudo adb shell reboot -p
(without "sudo" for Windows users - did not try that)
Repeat the command over and over again.
Use [Cursor Up] to repeat it from the command line history.
Do this until the phone's LED lights up and it shows a large battery logo on the display to indicate that it is powered off and charging.
! This might take many repeated attempts, don't lose your patience !
Disconnect the phone from USB.
Reboot into fastboot mode.
If TWRP is installed, this is [Power]+[Vol+].
If the stock recovery is still active, this is [Power]+[Vol-].
Break a boot loop that keeps booting into TWRP recovery
Make sure the latest Android SDK is installed (which includes the "adb" command).
Connect the phone to the PC with via USB.
While the boot loop is in progress, open a shell window on the PC (using
Linux in my case) and enter this command:
sudo adb shell rm "/cache/recovery/*"
(Without "sudo" for Windows users - did not try that)
Repeat the command over and over again.
Use [Cursor Up] to repeat it from the command line history.
Do this until the boot loop stops, i.e. you see the TWRP screen, and it does not keep booting any more.
! This might take many repeated attempts, don't lose your patience !
Reformat the /data partition under TWRP's "Advanced" options.
Just trying to wipe will fail at this time.
Reboot into recovery once more (TWRP -> Reboot -> Recovery).
Wipe (TWRP -> Wipe; the normal wipe which wipes data, cache, and dalvik).
Reboot the phone to system (TWRP -> Reboot -> system).
--
Stefan Hundhammer (shundhammer / HuHa)

How to save my media files from a bootlooping OnePlus One?

Hi,
I am totally lost and need help to get my personal data (images, videos most important) back from my bootlooping phone.
I browsed the privacy guard settings and disabled some boot and caller rights for google services and google play (with the intention to prevent it from looking up for updates constantly and drain my battery).
Then it restarted itself as I plugged it in for charge and is bootlopping since.
I have no root, the latest official CM update and a the build in Cyanogen recovery, since it came out of nowhere no usb bugging enabled (I believe).
When I try to enter the phone via ABD sideload from the CM Recovery "pull" my folders it says error:closed. adb backup wont work either.
It tells me: adb: unable to connect for backup: closed
This whole topic is kind a new for me - I never was in that situation and for now all I want is my images and videos back from my phone at least. I will try any method to save them.
I hope some can help me - I don´t know what to do anymore

This should theoretically work.
Flash TWRP by fastboot, then boot into this newly installed TWRP, then connect the device to your PC, as TWRP natively supports MTP, your Internal & External SD (If any) should be visible and you can copy your data over.

Thank you so much for this hint!
I will try that.
So I Just change my recoverer with this method right? This is possible without root and usb debugging?

Joshwin Aranha said:
This should theoretically work.
FlashTWRP] by fastboot, then boot into this newly installed TWRP, then connect the device to your PC, as TWRP natively supports MTP, your Internal & External SD (If any) should be visible and you can copy your data over.
Click to expand...
Click to collapse
It says:
writing recovery
FAILED (remote: Device not unlocked cannot flash or erase)
Is this game over?

Sore6 said:
It says:
writing recovery
FAILED (remote: Device not unlocked cannot flash or erase)
Is this game over?
Click to expand...
Click to collapse
Well no, it means your device has a locked bootloader, and you'll have to unlock it, the problem there is unlocking bootloader formats the device. Not always, but there's a good chance that you might lose your data, still thought give this a try,
fastboot devices (to confirm that your One is detected by the PC)
fastboot oem unlock (to unlock the device)
fastboot flash recovery recovery.img (to flash the recovery)
if this succeeds, disconnect the device and manually boot in to recovery, not to system, this is important because system will overwrite the TWRP with CYNGN recovery, so boot into recovery and try connecting your device to PC, see if MTP works.
PS - sorry for the late reply, i slept the whole sunday
EDIT - Wait, did you say that USB debugging is disabled ? then i think it might not work, give it a shot anyway tho.

Joshwin Aranha said:
Well no, it means your device has a locked bootloader, and you'll have to unlock it, the problem there is unlocking bootloader formats the device. Not always, but there's a good chance that you might lose your data, still thought give this a try,
fastboot devices (to confirm that your One is detected by the PC)
fastboot oem unlock (to unlock the device)
fastboot flash recovery recovery.img (to flash the recovery)
if this succeeds, disconnect the device and manually boot in to recovery, not to system, this is important because system will overwrite the TWRP with CYNGN recovery, so boot into recovery and try connecting your device to PC, see if MTP works.
PS - sorry for the late reply, i slept the whole sunday
EDIT - Wait, did you say that USB debugging is disabled ? then i think it might not work, give it a shot anyway tho.
Click to expand...
Click to collapse
Thanks for your help here - I guess I can´t win here with all my preconditions :/
One last question is:
Is there any method to wipe or flash the phone with a higher chance of keeping data even if little?

Try booting a recovery.img instead of flashing it.
Get the latest TWRP, copy the img file to the fastboot folder, enter fastboot mode and type fastboot boot twrp_file.img. It might work even with a locked bootloader.

Sore6 said:
Thanks for your help here - I guess I can´t win here with all my preconditions :/
One last question is:
Is there any method to wipe or flash the phone with a higher chance of keeping data even if little?
Click to expand...
Click to collapse
I was just about to say to try booting into the recovery, follow @nitrobg's instructions, get the recovery and instead of flashing the recovery, just try booting into it, command is
fastboot boot recovery.img
Hope it helps you, the pain of losing precious data isn't unknown to the best of us
EDIT - What caused the bootloop ? Who knows, maybe we manage to fix that

EDIT - What caused the bootloop ? Who knows, maybe we manage to fix that
Click to expand...
Click to collapse
I disabled some google play and google services from booting via the official cm privacy settings
Reason was to disable the battery drain by play when searching constantly for GOOGLE android updates...
Needed to disable that in cm12 back then and it helped.

nitrobg said:
Try booting a recovery.img instead of flashing it.
Get the latest TWRP, copy the img file to the fastboot folder, enter fastboot mode and type fastboot boot twrp_file.img. It might work even with a locked bootloader.
Click to expand...
Click to collapse
I will try that! Thank you.
I get back here with the result.

nitrobg said:
Try booting a recovery.img instead of flashing it.
Get the latest TWRP, copy the img file to the fastboot folder, enter fastboot mode and type fastboot boot twrp_file.img. It might work even with a locked bootloader.
Click to expand...
Click to collapse
Unfortunately it gives me this in the commandline:
booting...
FAILED (remote: Device not unlocked cannot boot)
finished. total time: 0.430s

That's unfortunate.
Do you have adb access to your phone in the CM recovery? If you do, try removing/renaming com.google.android.gms from both system and data partitions. You might have to play around trying to get root or to remount the partitions but it could work.

nitrobg said:
That's unfortunate.
Do you have adb access to your phone in the CM recovery? If you do, try removing/renaming com.google.android.gms from both system and data partitions. You might have to play around trying to get root or to remount the partitions but it could work.
Click to expand...
Click to collapse
Sadly no - all adb commands end in "error:closed"

Try this:
Power Down the OnePlus One
Hold the Power Button Until Android Starts to Boot Up
As Soon as Android Starts Booting Up, Let Go of the Power Button
Then Immediately Start Holding Both the Volume Up and Volume Down Buttons
Continue Holding Both Volume Buttons Until Android is Fully Booted
If you did everything correctly, Android *should* boot up just fine and show "Safe mode" on the lower left corner of the screen.

nitrobg said:
Try this:
Power Down the OnePlus One
Hold the Power Button Until Android Starts to Boot Up
As Soon as Android Starts Booting Up, Let Go of the Power Button
Then Immediately Start Holding Both the Volume Up and Volume Down Buttons
Continue Holding Both Volume Buttons Until Android is Fully Booted
If you did everything correctly, Android *should* boot up just fine and show "Safe mode" on the lower left corner of the screen.
Click to expand...
Click to collapse
Didnt work because as far as i know one has to be in the android ui - hold pwer off key and then hold the restart menu item and then the volume buttons + power buttons code should work.
Thanks anyway - i wiped it now.
it works but all data is gone

Not really, you hold volume buttons while the OS is booting and it should force a safe mode boot with all apps disabled.
Well, too bad now. It could've worked.

nitrobg said:
Not really, you hold volume buttons while the OS is booting and it should force a safe mode boot with all apps disabled.
Well, too bad now. It could've worked.
Click to expand...
Click to collapse
Honestly - I held it for 4 Minutes. There was a Vibrate Signal everytime it wanted to boot up into android but it didnt. Then it kept the cynogenmod loader til the next little vibration. It was a loop with no entry to android GUI

It's sad that you had to lose your data
Anyway, Take a lesson from this, weekly nandroid backups
(That's what I do)

Joshwin Aranha said:
It's sad that you had to lose your data
Anyway, Take a lesson from this, weekly nandroid backups
(That's what I do)
Click to expand...
Click to collapse
Thanks man - jeah I took care of such case beforehand now and rooted, bought titaniuam backup and enabled usb debugging instantly...
Also I am now using TWRP.
Lesson learned.
Thanks to you all for helping me!
I am really thankful for your effort.
Kind regards

Some kind thanks on my replies maybe ?
Haha, anyway. Take care.

Stupid me, tried Auto Root CF for Pixel and now it is bootlooping badly, No ADB

Okay, so I had been out of the flashing game for a while now, and recently got a Pixel 128Gb after using my trusty Nexus 6P, and I attempted to do Fastboot boot-to-root.img, which now has me stuck in a weird bootloop issue.
It boots, gives me the stupid can't be checked for corruption ****, gets to the white Google Screen, then there is a weird visual glitch, a blue line appears near the bottom of the screen, then the phone immediately reboots and does it all over again after doing a ramdump.
I can't even get into recovery to manually flash the stock image, as soon as I try to select RECOVERY it jumps to the boot screen where it tells me again that it cant be checked for corruption, and then starts the bootloop all over again.
ADB cant recognize it for whatever reason either. So now I'm probably not your average ****ed, I'm advanced ****ed.
Any body have any ideas?

boot-to-root is for Android O, you have to follow this guide

I had this same exact problem and I was able to fix it by reflashing the factory image. You said adb cannot recognize your device. But what about fastboot? If you reboot into the bootloader, connect to your PC, and execute "fastboot devices", does your device show? Download the latest factory image here. Extract it and execute flash-all.bat. Let me know if this helps.

You don't understand. When you attempt to reboot and go into recovery the manual way, the moment you select Recovery, the phone reboots and attempts to boot up, fails, performs write to ext4 ramdump, then loops over and over. ADB won't work because it wiped with the fastboot oem unlock which wiped the device, meaning no developer mode, which means no usb debugging.
Doesn't matter. Google is sending me a new one.
:/

jdkzombie said:
You don't understand. When you attempt to reboot and go into recovery the manual way, the moment you select Recovery, the phone reboots and attempts to boot up, fails, performs write to ext4 ramdump, then loops over and over. ADB won't work because it wiped with the fastboot oem unlock which wiped the device, meaning no developer mode, which means no usb debugging.
Doesn't matter. Google is sending me a new one.
:/
Click to expand...
Click to collapse
Fastboot and recovery are two different things. If you hold volume down + power it'll show you the bootloader screen (fastboot), this is where you'd usually select recovery. But if you stay on that screen, you can flash images to your phone. To fix your bootloop, download the boot.img from the stock ROM and use these commands in fastboot:
fastboot flash --slot _a boot boot.img
fastboot flash --slot _b boot boot.img
Then reboot normally.

falsh factory image inside the bootloader, don't need to go to recovery.

Step by Step
Thanks to previous experience with hacking devices (Android, Sony, etc.), patience and only allowing myself to freak out for a few seconds. A couple Google searches lead me to reflashing my Google Pixel 128GB and not sending it back to OEM.
So for the less patient I will break down the steps to do stop the bootlooping.
DON'T PANIC
Either hold down power until your phone turns completely off or wait for the bootlooping to do it for you. It usually only loops a few times before powering down.
Hold Power + Volume Down until it boots into the Fastboot mode.
[This is the screen that says you Phone Stats (serial #, cpu, ram, etc.) and has an Android picture on it laying down.]
Connect your Phone to your computer using a USB 3.0 port.
[My PC wouldn't recognize my phone at all when connected to USB 2.0]
Download from Full Factory Image from Google. { https://developers.google.com/android/images }
[Mine was "7.1.2 (N2G47O, May 2017)" for my Project Fi 128GB Pixel, but make sure you get the one for your phone]
Navigate to where your SDK/Fastboot folder is on your PC
[Unless you moved it, it is usually "C:\Users\USERNAME\AppData\Local\Android\Sdk" by default.]
Unzip the Contents of your Full Factory Image zip file to this location in it's own directory (for cleanliness).
Open a Command Prompt with a Right-Click "Run as Administrator" and navigate you your new zip file's directory.
["\platform-tools\sailfish-n2g47o" or whatever version of the Full Factory Image you used was.]
Type in "flash-all.bat" and wait for your phone to finish its installation. Your phone will restart itself into Fastboot Mode many times during this process.
Once it is finished, you phone should boot into its normal "First Boot Sequence" like you just started it up for the very first time.
At this point you can try flashing something else or use a different technique to update your recovery mode or ROM.
Good Luck.

Problem with B partition!

My OP7Pro (1917) apparently has a problem with the B partition. When I attempt to flash B partition with LOS17 and TWRP. It all flashes properly, but then when I attempt to boot the phone, the LOS boot animation starts but it's very slow and the phone just hangs at that point and will not boot past that point. So I power down and reboot the recovery and suddenly it cannot read storage, only the system partition. What causes this?
When I try to get back to partition A with: fastboot --set_active=_a
the response from fastboot is: fastboot: unknown option -- set_active=_a
I tried: fastboot --set-active=a , Same result.

Scotsman828 said:
My OP7Pro (1917) apparently has a problem with the B partition. When I attempt to flash B partition with LOS17 and TWRP. It all flashes properly, but then when I attempt to boot the phone, the LOS boot animation starts but it's very slow and the phone just hangs at that point and will not boot past that point. So I power down and reboot the recovery and suddenly it cannot read storage, only the system partition. What causes this?
When I try to get back to partition A with: fastboot --set_active=_a
the response from fastboot is: fastboot: unknown option -- set_active=_a
I tried: fastboot --set-active=a , Same result.
Click to expand...
Click to collapse
Hate it when that happens. This happened to me with stock OOS.... Had to format,data then reflash zip on both slots

Scotsman828 said:
My OP7Pro (1917) apparently has a problem with the B partition. When I attempt to flash B partition with LOS17 and TWRP. It all flashes properly, but then when I attempt to boot the phone, the LOS boot animation starts but it's very slow and the phone just hangs at that point and will not boot past that point. So I power down and reboot the recovery and suddenly it cannot read storage, only the system partition. What causes this?
When I try to get back to partition A with: fastboot --set_active=_a
the response from fastboot is: fastboot: unknown option -- set_active=_a
I tried: fastboot --set-active=a , Same result.
Click to expand...
Click to collapse
That's usually because your data partition is still encrypted and the incoming rom can't read it. You need to go back to the other rom you are running and remove the pin or pattern you have locked the phone with. Then go back into LOS and it should be able to read the data partition.
Might not be a good idea to run 2 different roms together though without using a recovery or system built to do that.

Turns out it's force encryption causing it. I finally managed to get LOS17 on both A/B slots with the DATA wiped. Then somehow lost rotation and other sensors. Managed to get that back by flashing the PERSIST partition with a file I found on XDA. Now everything is working great and my phone is de-googled. Only took me 2 days of pulling my hair out.

Please help. Bootloop stuck for no reason. Xiaomi mi 9 lite. Need to prevent data loss.

Hello.
Stock Xiaomi mi 9 lite, global rom
My phone started to lag hard so I decided to reboot.
Reboot took ages, stuck on MI logo, finally phone rebooted into recovery (5.0)
Reboot option makes phone try to boot (about 3-5minutes) and goes back into recovery.
Adb doesn't connect with recovery and device so no shell etc.
Connect to MiAssitant option allows side load connection via adb.
I can adb reboot bootloader to get into fastboot.
All those options do not allow for data recovery or bootloop fix without loss.
Phone is stock ROM, stock recovery, not unlocked.
I'm out of options. I need to save the data. Contacts etc.
Thanks for any help.

the only way I can image is read userdata partition off device, run fsck on linux, and restore partition image from EDL mode.
https://github.com/bkerler/edl
prog_ufs_firehose_sdm710_ddr.elf

I know what you have to do, give me some time to write k , kinda busta now
Nerfpl said:
Hello.
Stock Xiaomi mi 9 lite, global rom
My phone started to lag hard so I decided to reboot.
Reboot took ages, stuck on MI logo, finally phone rebooted into recovery (5.0)
Reboot option makes phone try to boot (about 3-5minutes) and goes back into recovery.
Adb doesn't connect with recovery and device so no shell etc.
Connect to MiAssitant option allows side load connection via adb.
I can adb reboot bootloader to get into fastboot.
All those options do not allow for data recovery or bootloop fix without loss.
Phone is stock ROM, stock recovery, not unlocked.
I'm out of options. I need to save the data. Contacts etc.
Thanks for any help.
Click to expand...
Click to collapse

try the loader first. you need to find a way to enter EDL mode. this is done either by deep flash cable or via modified fastboot.
[GUIDE][TOOL] Reboot to EDL mode from FASTBOOT! No More "Test Point Method"! [kenzo]
[GUIDE][TOOL] Reboot to EDL mode from FASTBOOT! No More "Test Point Method"! [kenzo] Reboot to EDL mode from FASTBOOT! No more Test Point Method needed ;) Technical Details: Redmi Note 3 support rebooting to EDL in Android Bootloader aboot...
forum.xda-developers.com
EDL tool works best on linux. you can copy re_livedvdV4.iso to pendrive with rufus.ie and boot from BIOS F11 or F12 key.
download the loader, open Terminal with ctrl + alt + T and try to print partition tables while phone is connected in EDL mode. note there is a timeout.
Code:
edl printgpt --memory=ufs --loader=path/to/prog_ufs_firehose_sdm710_ddr.elf
if the loader works you can dump userdata partition off device.
(open your windows drive in explorer first)
Code:
cd /media/ubuntu/<your windows drive UUID>/Users/<user>/Desktop
edl r userdata userdata.img --memory=ufs --loader=path/to/prog_ufs_firehose_sdm710_ddr.elf
Now you can try to fix possible errors on dump file. this won't change anything on phone. then try to mount.
Code:
sudo apt install f2fs-tools
sudo fsck userdata.img
sudo mkdir /media/ubuntu/data
sudo mount -vo loop,ro,noexec,norecovery userdata.img /media/ubuntu/data
sudo ls -la /media/ubuntu/data
(you should see encrypted files)

I didn't had deep flash cable or modified fastboot so after searching and trying every option (even asked ChatGPT, great source btw) i wiped everything using MiUnlock (phone was registered for unlocking).
It worked without problems in fastboot mode.
Next i installed twrp and installed Xiaomi eu ROM.
Lucky turned out phone had google sync on so many stuff was not lost.
(No i'v read it was about modified fastboot file, my bad. Thanks for great answer anyway)