Database Develop

Please help!!! Phone stuck after installing image 1.6 during V4.2.1 Cyanoen installat

Okay i was installing V4.2.1 and after i installed the image 1.6 i turn on the phone and it shows me an imgae of like a black rectangle and an arrow. I try pressing Home + power but i still get the same thing.
Help please!

85Mario85 said:
Okay i was installing V4.2.1 and after i installed the image 1.6 i turn on the phone and it shows me an imgae of like a black rectangle and an arrow. I try pressing Home + power but i still get the same thing.
Help please!
Click to expand...
Click to collapse
Tell me what happens when you press home + power then alt + l when the screen comes up. .. and when that screen comes up does the g1 screen come up first? Cuz I think otherwise it might be a guaranteed brick :/

okay i gott itt to go to the menu. but i try to apply the v4.2.1 and it always aborts it =/

Try the Q&A forum next time.

I go to the menu. flash the 1.6 recovery image. Change Cyanogen to update. Try to flash it but it gets aborted

don't know about cy updates but it sounds like your may have a bad file. Have you installed this update before using the "same file"? if not you may try just redownloading the update.

really neeed helpp with this. Tried installing the v4.1.9999 and it still aborts

bummer. I'm not sure what all the prerequisites are for cy mods.. Hopefully someone else can jump in here to help ya :/

Think he may have aborted installation during the radio flash portion of the HTC archive.
From Cyanogen's OP:
cyanogen said:
7- Apply sdcard:choose zip *PICK dream_devphone_userdebug-ota-14721.zip* from the list
ALLOW IT TO INSTALL FIRST.....you will see the "unbox" image.........then it will automatically reboot HOLD HOME button while it reboots.
Click to expand...
Click to collapse
That's not exactly the way it went for me the 2X I've done this, so maybe this is what happened...IDK?
I've had to reboot manually (Home+back) out of recovery following phase 1 of the flash to initiate the start the Radio flash portion. This may confuse some as it's not listed as a step.
Just to be sure, place fresh copies of dream_devphone_userdebug-ota-14721.zip and cm4.2.1 in /sdcard prior to doing this. Use an external card reader if necessary.
1. Get into recovery
2. Wipe (optional but recommended, problems=include step 2)
3. Flash dream_devphone_userdebug-ota-14721.zip
4. If phone does not reboot automatically, reboot manually (Home+back) out of recovery and release buttons immediately
5. Let Radio flash (you see the image of the box with the arrow and the eprom chip)
6. Wait for screen to go completely black then hold "Home" button until it reboots back to recovery console.
7. Flash CM4.2.1
I noticed 4.2.1 took an unusually long time to load on initial boot, so be patient.
If this has nothing to do with your issue, sorry for wasting your time. Hopefully this helps somebody eventually.

85Mario85 said:
really neeed helpp with this. Tried installing the v4.1.9999 and it still aborts
Click to expand...
Click to collapse
There are 2 things you could do, use cyans file, and make sure you flash the HTC image first, as his update file is a partial update without the google experience (read apps)
This is taken from Cyans OP in his thread and edited for you, please follow the instructions properly.
Note: You need cyanogens recovery image 1.4 or better for this process, as it lets you chose files named other than update.zip
Install instructions for an HTC Dream/ADP1/G1:
1- Perform a Backup......nandroid, etc (ignore since i don't suppose you have anything to backup at this moment)
2- Download: http://developer.htc.com/adp.html#s3 Android 1.6 Recovery Image. This isn't the type of recovery image we know. It's HTCs version of an update.zip
3- Download cyanogens ROM. http://n0rp.chemlab.org/android/update-cm-4.2.1-signed.zip
4- Mount your phone and place BOTH 1.6 Image and cyanogens ROM on your SD Card.
5- Reboot into recovery mode *Home+Power*
6- WIPE!!!! This will allow google apps to function, correctly.
7- Apply sdcard:choose zip *PICK dream_devphone_userdebug-ota-14721.zip* from the list
ALLOW IT TO INSTALL FIRST.....you will see the "unbox" image.........then it will automatically reboot HOLD HOME button while it reboots.
(ITS VERY IMPORTANT THAT YOU HOLD THE HOME BUTTON, BECAUSE IF IT THE HTC ROM BOOTS, YOU WILL HAVE TO RE-ROOT YOUR PHONE)
8- Apply sdcard:choose zip *Pick cm-4.2.1-signed.zip* from the list.
9- Reboot!
OR
download daveid's full update from http://www.megaupload.com/?d=80FXE36J or http://www.mediafire.com/?dnljdtndwnv
and just flash normally.
Oh and to mount your sd card to transfer the rom images to it from your computer when in recovery (Alt-X), use this command (in recovery, on your phone)
echo /dev/block/mmcblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
Finally, as someone else mentioned, please post in the right section.

how did u get ur phone to go back to the menu because the same thing happened to me

Sorry for may bad english !
I have the same problem. After flash rom OTA 1.6 of HTC, now i lose the recovery cm-1.4.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
When boot in recovery, it look like before hack root, we can't update the other file, exception "update.zip".
When i type "su" in terminal, it return "permission denied".
-I tried to update another rom but i didn't run.
-I tried to flash another recovery by Fastboot but not success.
-I tried to flash another SPL but not success.
-The last hope, i tried to re-hack root by DREAIMG.nbh but not success too.

Okay I had the same problem and know how to fix it.
1. Download 1.5 Cupcake here
2. Copy the file to the root of your SD and name it Update.zip
3. Boot recovery and press Alt + S to install Cupcake
4. Now that you`ve got Cupcake download Flashrec here
5. Make sure that you allow installing non market programs on your phone.
6. Open Flashrec after installing it and click backup recovery!! VERY IMPORTANT, didn`t do it the first time and it didn`t work.
7. After backup is finished you download the recovery given by the program
8. When the download is complete you select flash recovery.
9. Reboot, and flash your Custom Firmware again.
IMPORTANT!: All of the 1 click rooting procedures are putting the Flashrec.apk file and a recovery image on the SD card, installing Flashrec and then using it to flash the new recovery image. You WILL NOT have internal root access after this procedure (it only allows us external root access from recovery)
10. I installed the full version of 4.2.1 which was linked on the previous page of this thread, and it installed the right radio, spl and hboot.
So everything is normal again, thank god. Ow after i installed the full version of 4.2.1 it didn`t work but i had the recovery back and root so i installed the oldskool 4.1.1.1 and it works.
Good luck and this took me 5 hours to find out!

Edj87 said:
Okay I had the same problem and know how to fix it.
1. Download 1.5 Cupcake here
2. Copy the file to the root of your SD and name it Update.zip
3. Boot recovery and press Alt + S to install Cupcake
Click to expand...
Click to collapse
After this step, i have this result:

Omg! Exact same thing happen to me!
Please fix this problems for us if possible

[RECOVERY][Huawei P7-L10] TWRP 2.8.7.0 touch recovery [2015-07-19]

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Compiled from latest Source's (Android 5.1.1) and build for Huawei P7-L10
Works on EMUI 3.0 - 4.4.2 and EMUI 3.1 - 5.1.1
Changelog TWRP 2.8.7.0
-Initial ground work for software drawn keyboard (_that)
-Fix handling of wiping internal storage on datamedia devices (xuefer)
-Allow DataManager to set and read values from the system properties (xuefer)
-Fix crash when taking screenshots on arm64 devices (xuefer)on Android 5.1.1
-Fix error message after an ORS script completes (Dees_Troy)
-Fix crashes / error when creating encrypted backups (_that, Dees_Troy)
-Add system read only option – more details below (Dees_Troy)
-Add resize2fs and GUI option to run resize2fs (Dees_Troy)
-Fix crash loop caused by empty lines in AOSP recovery command file (_that)
-Prevent duplicate page overlays such as multiple lock screens (mdmower)
Note: As always, be sure your custom theme is up to date (or remove your custom theme) before updating TWRP.
System read only option: Devices that ship with 5.0 and higher as their initial OS are using block level OTA updates. With this style of OTA update, the update script checks to see if the system partition has ever been mounted read/write. Further, the script also usually runs an SHA sum of the entire system partition to detect if any changes have been made. If any changes have been made, the OTA update will refuse to install. Since not all OEMs and devices have factory images available, we have created a new feature in TWRP that detects if the system partition has ever been mounted read/write. If not, you will be prompted asking if you want TWRP to mount system as read/write. If you choose not to allow TWRP to mount as read/write, TWRP won’t prompt to install SuperSU and TWRP won’t try to patch the stock ROM to prevent TWRP from being replaced by stock recovery. The goal of this option is to hopefully allow the user to make a raw system image backup that they can use to get back to a state where they can take OTA updates again.
resize2fs feature: On some devices like the Nexus 6, the factory images include a userdata image that is the proper size only for the 32GB units. If you flash the factory image to a 64GB Nexus 6, the data partition will appear as if it only has the free space of a 32GB device. Using the resize2fs option, TWRP can resize your data partition to take up the full space available. The resize2fs may also be useful to resize system partitions on devices where custom ROM system images don’t take up the full partition space. Lastly, resize2fs may be useful in some cases to reserve the proper space at the end of a data partition for a full disk encryption key, should your partition be formatted incorrectly for some reason.
This new version also marks our first set of full builds using our new jenkins build server. You can track the progress of builds at https://jenkins.twrp.me and we have taken additional steps to make it easier for device maintainers to step up and submit patches to our gerrit server at https://gerrit.twrp.me to help us keep devices up to date and working.
Bugs
- CPU Temp is not displayed
How to install
Unlocked bootloader is recommend!
Flash via fastboot
adb reboot-bootloader
fastboot flash recovery TWRP-2.8.7.0.img
fastboot reboot
Download
MEGA
Sourcecode
GitHub
BIG THX FOR HELP
@_that
@SHM
@yuweng
@surdu_petru
@acbka

Eagerly Waiting

andromodgod said:
Eagerly Waiting
Click to expand...
Click to collapse
yeah i have to fix one bug first before release ....
because twrp will backup the whole sdcard when you select the data partion for backup..
i think release will be tommorow . but beside that and the cpu temp all is working well

Download is now live :d

Congrats on your build :highfive:

It works very well, health in your hand.

Job Well Done i Must Say !!

As for devices that have <5.0, OTA still won't work and we must go back to Huawei recovery to apply OTA?

TimAnd said:
As for devices that have <5.0, OTA still won't work and we must go back to Huawei recovery to apply OTA?
Click to expand...
Click to collapse
it also works for EMUI 3.0 --> 4.4.2

Help, I can not flash any recovery, to start in bootloader says in red letters phone is unlocked and this error appears to me, with your probe you provided me with the TWRP and that other CWM (changing the carefully clear name) when I flash it by Forzo flashify installation and remains in the logo with the LED flashing red and green and to get him out of there original flashee by fastboot boot recovery and smoothly ...

Hi,
I have two issues:
After flashing this recovery, when I try to power off the phone, it reboots to recovery.
When I try to connect to my computer in debug mode, fastboot don't recognize the device (I try this to flash the stock recovery, I used TWRP to flash SuperSU)
I want to power off the phone when i need to do it...
Some help?
Thanks in advance, regards
Víctor

MisterVik said:
Hi,
I have two issues:
After flashing this recovery, when I try to power off the phone, it reboots to recovery.
When I try to connect to my computer in debug mode, fastboot don't recognize the device (I try this to flash the stock recovery, I used TWRP to flash SuperSU)
I want to power off the phone when i need to do it...
Some help?
Thanks in advance, regards
Víctor
Click to expand...
Click to collapse
Are you saying that while in TWRP when you select to power off it reboots the recovery?
And when you say debug mode, are you referring to while your system OS is booted up that you are attempting to use fastboot?
Sent from my C525c using Tapatalk

SHM said:
Are you saying that while in TWRP when you select to power off it reboots the recovery?
And when you say debug mode, are you referring to while your system OS is booted up that you are attempting to use fastboot?
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
Hi SHM,
Thanks for your reply.
First question: no, i'm saying that when i'm in Android and select from power menu to power off, it reboots to TWRP recovery.
Second question: no, i'm referring when my phone is in debug mode (adb mode) my computer doesn't recognize it (before flashing TWRP recovery, with stock recovery, it recognizes)
Thanks in advance, regards
Víctor

MisterVik said:
Hi SHM,
Thanks for your reply.
First question: no, i'm saying that when i'm in Android and select from power menu to power off, it reboots to TWRP recovery.
Second question: no, i'm referring when my phone is in debug mode (adb mode) my computer doesn't recognize it (before flashing TWRP recovery, with stock recovery, it recognizes)
Thanks in advance, regards
Víctor
Click to expand...
Click to collapse
This is very unusual behavior. In fact, this is the first time I have ever heard of this kind of behavior. Especially with the issue of powering off your device and instead it reboots your recovery.... Will have to brainstorm on my end.
Sent from my C525c using Tapatalk

@MisterVik are you currently using a mod for powering off, rebooting, etc, or is the power options seen on your device completely stock?
Sent from my C525c using Tapatalk

SHM said:
@MisterVik are you currently using a mod for powering off, rebooting, etc, or is the power options seen on your device completely stock?
Sent from my C525c using Tapatalk
Click to expand...
Click to collapse
@SHM
It happens while using the default stock power off menu, no mod installed (like xposed)
But, now and because your question, i remember a modify i did in build.prop. I check it right now.
Thanks, regards
Víctor
Edited: no mod installed

@SHM
Don't ask me how, but now, without any changes, when I select power off on power menu, phone goes off properly!
Still having the issue with the connection to the computer in ADB mode...
Thanks and regards
Edit: solved both, maybe yesterday isn't my day. Booted directly in fastbood mode, and then flashed stock recovery.

hello
i succesfully installed TWRP 2.8.7.0.img
also every other version i cant get it activated
i used my phone keys volule up & at same time powerbutton i always get in fastboot menu
WHAT DO I WRONG??

Can you get I to recovery using "adb reboot recovery"?

rodlane said:
Can you get I to recovery using "adb reboot recovery"?
Click to expand...
Click to collapse
Yes
Sent from my HUAWEI P7-L10 using XDA Free mobile app

[GUIDE] Root/Flash for Xiaomi Redmi 2

AnandMore's How-To Guide For Beginners
Xiaomi Redmi 2
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Intro:
This thread will serve as a location for basic how-to guides for the Xiaomi Redmi 2. I'm going to start off with a couple of the more obvious ones and go from there. If anyone has any suggestions for additions please feel free to let me know.
By attempting any of the processes listed this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches on fire, or turns into a hipster and claims to have been modified before it was cool.
Index:
Post #1 - Rooting your Redmi 2
Post #2 - Flashing Custom Recovery
Post #3 - Flashing Custom ROMs
Post #4 - Flashing Custom Kernels
Resources:
Everything you need for Xiaomi Redmi 2 is available in the below given thread -
[INDEX] Xiaomi Redmi 2

Rooting your Redmi 2:
This guide will root your device through Stock MI Recovery(Works with TWRP also), but this is not Native Root. A new app named SuperSU will be installed, which will give root Permission.
Note:
Rooting does not Void Warranty.
Caution:
This is a safe process, but I am not responsible for anything bad that happens to your phone.
In most cases this approach of rooting should not block OTA updates.
Steps to follow for rooting:
Download the Root.zip and Copy the file to the folder 'Internal storage' (root of internal storage).
(File at the end of thread)
Open the Updater app, Press the 3 dots at Right Top Corner, A menu will open. Tap on “Choose Update Package“ and select the Root.zip File.
Wait until device will reboot.
After reboot a new app SuperSu will be installed.
Open the app and Choose "Continue".
Choose "Normal", Don't Choose TWRP/CWM, device will go into Boot Loop.
Note - Don't Choose TWRP/CWM, it will brick your device.
After sucessful updation , press ok.
Your Phone has now Root Permission.
Open any app using Root permission and SuperSU will ask for Permission.
Enjoy your rooted Redmi 2.
Un Root The Device:
For Un Root , open the SuperSU app,tap on Settings, Choose Full Unroot.
Your Device is Un Rooted Sucessfully. The SuperSU app will be removed.

Flashing Custom Recovery:
From Mobile:
Install Flashify app from Playstore
Once installed, access the application through app drawer.
Allow root access now and get navigate to Flashify’s home screen.
First take a backup of your recovery in case something goes wrong. (RECOMMENDED)
Now tap on recovery image and by "Choose the file" menu locate the .img file you want to flash.
After successful flashing it will ask you to reboot your device.
Done! You have custom recovery on your phone.
From PC:
Enable USB debugging, go to settings>about phone and then tap on Android/MIUI version 5 times. Developer Options will be enabled. Now go back to settings>Developer options and enable USB debugging.
ADB and Fastboot Drivers installed on your PC. I can provide you the drivers but it would be a better option to install MiFlash to get all the necessary drivers and Miflash software with you for future use.
Install Miflash on your PC. Lets suppose we installed it in C:\Xiaomi folder.
You can see two folders, proceed to "adb' folder
Then proceed to "Google" folder.
Proceed to "Android" Folder.
We are at our destination.
Now Hold down "Shift" button on your computer keyboard and right click with mouse on an empty part of the window. You will see that in the menu that appears, you have an option - "open command window here". Click on that
To verify if ADB is working and installed correctly, type "adb version" in the command window that opened without the code. You should get the adb version which means its working fine.
Turn off your Phone. When its completely switched off, press and hold "Volume Down" and "Power" button together and then the phone will turn on in Fastboot mode.
Use the USB cable to connect Phone to PC.
Copy the Recovery.img in the Android folder where we are running the Command prompt. (C:\Xiaomi\adb\Google\Android in my case as i installed Mi flash in C:\Xiaomi folder)
Now go back to command promt and enter the following commands -
Code:
fastboot devices
Once you enter that command, you will get a non-empty name for the device meaning the device is connected. Proceed to enter the next command to flash recovery image -
Code:
fastboot flash recovery recovery.img
Once you enter this command, the recovery image will be flashed on your device. Once it is completed, enter the final command to reboot your phone -
Code:
fastboot reboot
Your phone will reboot.
You have have now completed flashing custom recovery replacing Stock Mi recovery on your Xiaomi Redmi 2.

Flashing custom ROMs:
Steps to Follow:
Download and transfer the custom ROM you wish to flash to your device’s storage.
Boot your device into TWRP recovery.
Select “Wipe” from TWRP main menu and do a “Swipe to Factory Reset” on the bottom of screen.
Note: This will factory reset your device. If your custom ROM doesn’t require a factory reset, then simply skip this step.
Go back to TWRP main menu, tap on “Install” and select the custom ROMs .zip file that you transferred to your device in Step 1.
After selecting the .zip file, do “Swipe to Confirm Flash” on the bottom of screen to begin the custom ROM installation process. This may take some time.
Once your ROM is successfully flashed, you’ll see “Wipe cache/dalvik” option, select it and then do “Swipe to wipe” on bottom of screen.
Once cache & dalvik wipe completes, hit the “Back” button on-screen and then select “Reboot System” button.
That’s all. Your device will now reboot with the custom ROM you just flashed. Since this will be the first reboot after flashing a new ROM, it might take some time to rebuild cache and finish boot, have patience.

Flashing Custom Kernels:
Steps to Follow:
Download and transfer the custom Kernel you wish to flash to your device’s storage.
Boot your device into TWRP recovery.
In the TWRP main menu, tap on “Install” and select the custom Kernel .zip file that you transferred to your device in Step 1.
After selecting the .zip file, do “Swipe to Confirm Flash” on the bottom of screen to begin the custom Kernel installation process. This may take some time.
Once flashing completes, hit the “Back” button on-screen and then select “Reboot System” button.
That’s all. Your device will now reboot with the custom Kernel you just flashed. Since this will be the first reboot after flashing a new Kernel, it might take some time to rebuild cache and finish boot, have patience.

For list of all available Roms visit this thread :
http://forum.xda-developers.com/redmi-2/how-to/available-custom-marshmallow-roms-redmi-t3278535
Click to expand...
Click to collapse
Better if you make lollipop ROMs thread too

Superb work bro thanks ...u

Isn't MIUI rooted out of the box already? [emoji52]

Stachura5 said:
Isn't MIUI rooted out of the box already? [emoji52]
Click to expand...
Click to collapse
Developer ROMs are. Global ROMs aren't.
Device comes with global ROM :3

noobpremium said:
Better if you make lollipop ROMs thread too
Click to expand...
Click to collapse
I made both lollipop and marshmallow roms in one thread. So you think i should make seperate one for lollipop.

Stachura5 said:
Isn't MIUI rooted out of the box already? [emoji52]
Click to expand...
Click to collapse
All roms(Beta,developer,stable) for Redmi 2 are not Pre rooted.

Added videos tutorials for better understanding.

Great info, thanks a lot!
I have a very basic, very likely extremely stupid question: I flashed an early CM12.1 build (using CWM afaik) and for unknown reasons, I cannot boot into recovery and don't have root. How can I re-gain root access from here?

my phone also rebooting. please help me. how to go to recovery?

srmohanrajan said:
my phone also rebooting. please help me. how to go to recovery?
Click to expand...
Click to collapse
1) Switch off the phone.
2) Press the Volume Down, Volume Up and the Power Button at the same time, about 2-3 seconds until the mi logo shows up.
3) Recovery mode menu will appear.

Fr3ak23 said:
Great info, thanks a lot!
I have a very basic, very likely extremely stupid question: I flashed an early CM12.1 build (using CWM afaik) and for unknown reasons, I cannot boot into recovery and don't have root. How can I re-gain root access from here?
Click to expand...
Click to collapse
Follow the same steps to boot into recovery and flash SuperSU v2.4.6 zip via recovery
(And remember you are responsible if anything happens to the device)

omg, I am so stupid. I tried vol up + power, vol down + power and all possible combinations including the home button, but never vol up + vol down + power button. Thank you!

Fr3ak23 said:
omg, I am so stupid. I tried vol up + power, vol down + power and all possible combinations including the home button, but never vol up + vol down + power button. Thank you!
Click to expand...
Click to collapse
No problem bro !
✌

Great !

New CM 12.1 is awesome, finally the camera works
I am curious on why I keep on losing root access. I never had that issue with any other phones and custom ROMs.

[GUIDE][EUI][Coolpad Cool 1][TWRP/Root] Easy TWRP/Root Using QFIL for EUI

Today I will be making some short and easy guide to easily flash TWRP on your Coolpad Cool 1 from your stock EUI. It will be easier to flash any custom ROM if you manage to get TWRP installed on your device.
Preparation :
1. Get Developer Option on your Coolpad Cool 1. You can do this by going to Setting>About phone and search for Build Number. Tap on it for 6-7 times until it tells you that you are now a developer.
2. Go into Developer Option and enable USB Debugging and OEM Unlocking.
3. Download all the necessary ADB Drivers, Qualcomm QLoader Drivers, Coolpad Assistant software, Magisk, EUI Recovery Coolpad Cool 1 and QPST/QFIL. (You can just google this, I have limited internet, so don't be counting too much on me to upload this)
Instruction :
1. Power off your phone.
2. Open QFIL software
3. Press Power + Volume Up + Volume Down button simultaneously and connect your phone to PC. This is to connect your phone into EDL (Emergency Download Mode).
4. Make sure your phone has been detected as "Qualcomm HS-USB QDloader xxxx (COMx)" in QFIL
5. At "Select Build Type", select "Flat Build"
6. At "Select Programmer" browse to your downloaded recovery folder path and select "prog_emmc_firehose_652.mbn" inside the folder. Don't worry, it will only show you this one file only anyways, so just click it.
7. At "Select Flat Build" , you can load your recovery files by using the "Load XML" button. Select "rawprogram0.xml" in the first popup and "patch0.xml" at the second popup. Again, it will only show you this one file in the popup box so you can't miss it anyways.
8. After all is set, click the download button and wait for it to finish flashing.
9. After the process finished, boot into your recovery directly by pressing Power button + Volume Up.
10. Flash your preferred rooting package. I use Magisk v16 and it's working fine with EUI.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

Thanks mate. Is 5here any custom rom for it ?

bouyhy01 said:
Thanks mate. Is 5here any custom rom for it ?
Click to expand...
Click to collapse
You can try this : https://forum.xda-developers.com/android/development/rom-jui-rom-vr12-cuoco92-t3780509#post76380258

can i use this method to leere le 3?

itsmeyukiedcqii said:
can i use this method to leere le 3?
Click to expand...
Click to collapse
I don't have that device but you can always try and let us all know.

Aplication cant download any files. Allways exit downloading

Τhe device model is R116 (not c103 or C106) Any tool that works with this model?? Qfil, Miflash, Coolpad download assistant didn't do the job. And ADB commands cant see it either.

Does this require formatting data?

Maybe yes i dont know.

Can we just do fastboot oem unlock and flash twrp?

Case closed. Recycle bin gave the solution.

Hi my device is showing as an "Unknown Device". I have installed all the drivers which are available accross the web. Please suggest me...

Anas Rahman said:
Can we just do fastboot oem unlock and flash twrp?
Click to expand...
Click to collapse
No you can't. I hope we can. I tried it and it doesn't work. Our device just don't recognize adb command.

I have a problem when i try to install recovery via QFIL ..... please help me???
Code:
Download Fail:Sahara Fail:QSaharaServerFail:Processfail

tanks for you
vulturext said:
Today I will be making some short and easy guide to easily flash TWRP on your Coolpad Cool 1 from your stock EUI. It will be easier to flash any custom ROM if you manage to get TWRP installed on your device.
Preparation :
1. Get Developer Option on your Coolpad Cool 1. You can do this by going to Setting>About phone and search for Build Number. Tap on it for 6-7 times until it tells you that you are now a developer.
2. Go into Developer Option and enable USB Debugging and OEM Unlocking.
3. Download all the necessary ADB Drivers, Qualcomm QLoader Drivers, Coolpad Assistant software, Magisk, EUI Recovery Coolpad Cool 1 and QPST/QFIL. (You can just google this, I have limited internet, so don't be counting too much on me to upload this)
Instruction :
1. Power off your phone.
2. Open QFIL software
3. Press Power + Volume Up + Volume Down button simultaneously and connect your phone to PC. This is to connect your phone into EDL (Emergency Download Mode).
4. Make sure your phone has been detected as "Qualcomm HS-USB QDloader xxxx (COMx)" in QFIL
5. At "Select Build Type", select "Flat Build"
6. At "Select Programmer" browse to your downloaded recovery folder path and select "prog_emmc_firehose_652.mbn" inside the folder. Don't worry, it will only show you this one file only anyways, so just click it.
7. At "Select Flat Build" , you can load your recovery files by using the "Load XML" button. Select "rawprogram0.xml" in the first popup and "patch0.xml" at the second popup. Again, it will only show you this one file in the popup box so you can't miss it anyways.
8. After all is set, click the download button and wait for it to finish flashing.
9. After the process finished, boot into your recovery directly by pressing Power button + Volume Up.
10. Flash your preferred rooting package. I use Magisk v16 and it's working fine with EUI.
Click to expand...
Click to collapse
Request for these files
boot1.bin
boot2.bin
main.bin (user data main.bin)
Please

ghasem.hf said:
Request for these files
boot1.bin
boot2.bin
main.bin (user data main.bin)
Please
Click to expand...
Click to collapse
Nobody help
I am waiting

Quote:
Originally Posted by vulturext
Today I will be making some short and easy guide to easily flash TWRP on your Coolpad Cool 1 from your stock EUI. It will be easier to flash any custom ROM if you manage to get TWRP installed on your device.
Preparation :
1. Get Developer Option on your Coolpad Cool 1. You can do this by going to Setting>About phone and search for Build Number. Tap on it for 6-7 times until it tells you that you are now a developer.
2. Go into Developer Option and enable USB Debugging and OEM Unlocking.
3. Download all the necessary ADB Drivers, Qualcomm QLoader Drivers, Coolpad Assistant software, Magisk, EUI Recovery Coolpad Cool 1 and QPST/QFIL. (You can just google this, I have limited internet, so don't be counting too much on me to upload this)
Instruction :
1. Power off your phone.
2. Open QFIL software
3. Press Power + Volume Up + Volume Down button simultaneously and connect your phone to PC. This is to connect your phone into EDL (Emergency Download Mode).
4. Make sure your phone has been detected as "Qualcomm HS-USB QDloader xxxx (COMx)" in QFIL
5. At "Select Build Type", select "Flat Build"
6. At "Select Programmer" browse to your downloaded recovery folder path and select "prog_emmc_firehose_652.mbn" inside the folder. Don't worry, it will only show you this one file only anyways, so just click it.
7. At "Select Flat Build" , you can load your recovery files by using the "Load XML" button. Select "rawprogram0.xml" in the first popup and "patch0.xml" at the second popup. Again, it will only show you this one file in the popup box so you can't miss it anyways.
8. After all is set, click the download button and wait for it to finish flashing.
9. After the process finished, boot into your recovery directly by pressing Power button + Volume Up.
10. Flash your preferred rooting package. I use Magisk v16 and it's working fine with EUI.
Click to expand...
Click to collapse
After doing that,
when I enter in recovery mode, it just show 2 options:
Update system
or
Clear data
What should I do

twrp internal storage 0mb coolpad c103 how to fix?
Hello,
I did all the procedures. But it can't install SuperSU. And it shows internal storage 0 mb. Then I rebooted the phone. And I rebooted the phone again in recovery mode but this time it gives me just two options format or update. Can someone please tell me how to solve this issue? Please.
Thank you.

cunhaandre said:
Hello,
I did all the procedures. But it can't install SuperSU. And it shows internal storage 0 mb. Then I rebooted the phone. And I rebooted the phone again in recovery mode but this time it gives me just two options format or update. Can someone please tell me how to solve this issue? Please.
Thank you.
Click to expand...
Click to collapse
Why not try magisk?
I'm not sure but your internal is 0mb because TWRP isn't able to decrypt your data partition. I don't use this phone but I have the same problem with my phone, what I did is that I flashed a zip which unencrypts the data and then formatted my internal storage it works fine after that
You can Try backing up your data and formatting your internal storage after flashing magisk

Anas Rahman said:
Why not try magisk?
I'm not sure but your internal is 0mb because TWRP isn't able to decrypt your data partition. I don't use this phone but I have the same problem with my phone, what I did is that I flashed a zip which unencrypts the data and then formatted my internal storage it works fine after that
You can Try backing up your data and formatting your internal storage after flashing magisk
Click to expand...
Click to collapse
Hello,
thank you for your reply, I already solved the issue. I did all the things again, and then I formated internal storage and become normal, then I transferred the ROM via mtp and flashed it. All is fine now.
Thank you

General [GUIDE][UNBRICK] Realme 8 Unbrick/Upgrade/Downgrade [RMX3085]

Hello everyone! So after the new MediaTek DAA and SLA protection bypasses you can find GitHub repo of here , using the bypass we are able to use SPFlash Tool, here is a guide how you can do it! This guide is for RMX3085 (Realme 8) ONLY. DON'T DO ANY OF THESE IF YOU HAVE SOMETHING ELSE!
ALWAYS USE DOWNLOAD ONLY MODE OF SP FLASH TOOL.
DON'T TOUCH ANYTHING RELATED TO FORMAT ON SP FLASH TOOL! (IT'S WRITTEN EVERYWHERE, YOU WILL LOSE YOUR IMEIS IF YOU USE FORMAT ALL + DOWNLOAD. YOU ARE SAFE IF YOU USE DOWNLOAD ONLY.)
Requirements:
PC or Laptop
Internet connection
Realme 8
USB cable
Windows Method
Requirements:
Bypass Tools Pack - (DRIVER AND BYPASS FILES)
SP Flash Tool
Decrypted OFP (OPPO FIRMWARE PACKAGE) :
Indian
A.22 (Indian) - GDrive
A.24 (Indian) - GDrive
A.26 (Indian) - Gdrive
C.05 (Indian) - GDrive
C.09 (Indian) - GDrive
C.11 (Indian) - GDrive
Global
A.22 (Global) - GDrive
A.24 (Global) - GDrive
A.26 (Global) - GDrive
Install Python from Windows Store
libusb-win32 - Having Issues? Use this.
Get usbdk installer (.msi) from here and install it
Steps:
1) Extract the zip
2) Go to driver folder, find the .inf file right click and press install.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
3) Download this file and install it, after installing power off phone and connect to pc while holding Vol+- (don't leave the buttons after connecting) . You might need this driver as well if it's not detected.
4) Press next, connect your device to PC while holding Vol+- buttons (your device needs to be powered off, and don't leave the buttons) and you will see the mtkdriver down below. Install it.
5) Choose MediaTek USB Port and install it.
6) Then run the brom.bat under Bypass folder.
7) Now power off the phone and connect the phone while holding volume + and - (Don't leave the buttons until the bypass is done)
8) After the above step Go into Flash Tool folder and open the SPFlash tool go to Options>Option
9) Click on Connections and select UART and set Baud Rate to 921600
10) After that choose scatter file and also if not set, set your download-agent. You don't need to select auth file as authorization is disabled. Once you do it, it should look like this. ALWAYS MAKE SURE DOWNLOAD ONLY MODE IS SELECTED! DON'T SELECT OTHER MODES!
Select all the Partitions except opporeserve2 and cdt_engineering. otherwise you will get errors.
*11) If you want to flash super.img partition also then download this scatter.txt file and replace it with the another scatter file which is present in the decrypted firmware folder. After that select it again in sp flash tool.
Again Make SURE "Download Only" is selected. Don't select ANYTHING ELSE! You will lose your IMEIs, Serial Numbers, Capability of Hardware Attestation etc. if you choose "Format data + Download" make SURE you selected "Download Only".
Now, you can start downloading with the button and after that a checkmark will appear. You can reboot your phone and use it like before now! All your userdata will (inevitably) be cleared!
After flashing it should look like this. Download has been complete. Enjoy!
"Congrats Now your Realme 8 is Unbricked "
Credits :
https://github.com/bkerler/ for decryptor and for creating the tool.
If you face any issues write them down below...

Some people having this problem so I want to add one more thing to the guide. If you are not having any issues related to boot then don't follow these steps.
After waiting more then 10 minutes, if it doesn't boot up/bootloop. Or shows DM-Verity corrupt error then do this.
1) Try boot into stock recovery by pressing volume up + power button after that when your screen flashes quickly unpress buttons.
2) Now press volume down + power button, by pressing these you will boot into stock recovery.
3) Go to format option and do a full format.
4) Your phone will definitely boot up after that.

Hi
I would like to ask how you obtained the system for realme 8 in the latest version.
Can you download somehow from your device?

HowWof said:
Hi
I would like to ask how you obtained the system for realme 8 in the latest version.
Can you download somehow from your device?
Click to expand...
Click to collapse
From realme offical site

Could you send a link because there is no information on the Polish realme site

HowWof said:
Could you send a link because there is no information on the Polish realme site
Click to expand...
Click to collapse
Realme 8 Firmware (RMX3085) - Realme Firmware
Realme 8 Firmware RMX3085 Official Flash File (Stock ROM). flash your phone using realme flashtool or MSM Download tool.
realmefirmware.com

if "Brick" occured in rooting process - then can recovery be done without data loss :
Prerequisite: firmware version on the body must the same as downloaded "Decrypted OFP" (as example both is A.22 )
HowTo:
at step of SPFlashing (currently that is 10-th)
- check ONLY next partitions in SPFlash to restore :
PRELOADER RECOVERY VBMETA LK LK2 BOOT
... and NO any of other
(as thats only are touched by currently described rooting processes)

after recovery exist on every boot:
"dm-verify corrupted..."
how to get out of this message?
Reset with clearing data not helps ...

DaLiV said:
after recovery exist on every boot:
"dm-verify corrupted..."
how to get out of this message?
Reset with clearing data not helps ...
Click to expand...
Click to collapse
Wait for 10mins if it didn't boot then.
Format with mtk client
python mtk e metadata,userdata,md_udc

that boots ... BUT
on every boot thet alerts about "corruption"
ok cleared partitions with python...
still the same alert ...

DaLiV said:
that boots ... BUT
on every boot thet alerts about "corruption"
ok cleared partitions with python...
still the same alert ...
Click to expand...
Click to collapse
Try booting into stock recovery and format from there

Ok. format from recovery menu solves ...
now that boots normally =
- no alert
-no boot allowing by pressing key required
good behaviour to see when boot subsystem altered, as at every boot alerted and required to press longer power button to confirm/allow starting ...
interesting, that is something new on mine (device versions) or overall ...

I have it anyway. have you solved it yet? Do I understand correctly?

after doing the insstruction, mine bootlooping and enters recovery mode

XCentrialG said:
after doing the insstruction, mine bootlooping and enters recovery mode
Click to expand...
Click to collapse
Maybe you missed some step. Can u explain ur problem briefly. What u did and what happened.

niki.rsb said:
I have it anyway. have you solved it yet? Do I understand correctly?
Click to expand...
Click to collapse
I Think that is not so solvable /possible if someone decode debug and finds /... but that is quite acceptable for rooting /if you don't want to make illegal spionage and so on/ ... also as if your device will be rooted by someone - you will see alert of changes on boot ... that is good ...
if you are rooted - you must be alerted .
but if you will going to stock rom and have protection - then flashing "stock" (surely without 3 partitions that IMEI-and-so-on-related ) and then format from recovery menu helps return to "factory" operation

Tony Stark said:
Maybe you missed some step. Can u explain ur problem briefly. What u did and what happened.
Click to expand...
Click to collapse
just a casual day to update my firmware, reboot and my phone refused to boot anymore, and then i came here, following all the steps very carefully (i read every steps twice so i dont make any mistake), and no luck.

XCentrialG said:
just a casual day to update my firmware, reboot and my phone refused to boot anymore, and then i came here, following all the steps very carefully (i read every steps twice so i dont make any mistake), and no luck.
Click to expand...
Click to collapse
There should be some mistake in your process. Because this guide is working and tested by many people.

Does global firmware have realme dialer instead of google dialer?
Can I flash Global firmware my indian device?

on your firmware package, it does not flashes super.img by default. Because in scatter file
- partition_index: SYS48
partition_name: super
file_name: super.img
is_download: false
changing false to true helps fixing destroyed super partition