Hi, I need help, I have Xperia x8 (ROOT I have done) and try to load the ROM, but when I download this file Cm7.1.0 FXP030 with the kernel and run flashtool flashtool and click on the flash and connect phone instructions and passes it starts kernelchilku loader and starts it running the green bar is the construction paper and then starts the flash was successful, and then that i turn on debugging and unknown sources on the phone but nothing has changed and unknown sources and tuning my patches. But I tried that when I disconnect in the middle of flashing the phone to me also writes that the flash was completed successfully and yet could be because the phone was connected. So success to me even though I reported it myself sabotaging and when I let it run as it completes successfully, but they's no flash did not take place.
Read instructions carefully.
When FT says "flash complete" then "disconnect ... turn debugging" it means that flashing IS complete.
Disconnect, boot phone to recovery, install zip rom, full wipe and reboot.
Do backups first ;]
this helped me ....
If Unzip the downloaded zip
Go to the META-INF \ com \ Google \ android \
replaced with the updater-script updater-script found in the updater-script.zip
RE-ZIP folder (I had a META-INF, system and boot.img)
Related
Hello,
Problem - Device keep on rebooting showing Mi logo (every 2 sec), Does not boot into system
What I did?
exteneded system partition to 1.2 gb - success
flash Marshmellow custom rom - success
misinstalled system ui of theme - system ui stopped
reinstalled clean rom from custom recovery - success
then it does not boot into system - keep on rebooting at mi logo (every 2 sec)
tried fastboot rom - failed (remote size too large)
rebooted into recovery
flash stock partition via adb - success
fastboot flash (with flash all) - success (says miflash - operation compeleted successfully)
Still it does boot into system - keep on rebooting at mi logo (every 2 sec)
Help?
if you can access recovery now then go to recovery and take a backup of current rom. The wipe everything except internal storage and then restore the backup.
maybe it'll fix it because thats what happened to me too after flashing the MM custom rom. Every time i was rebooting the phone kept bootlooping at Mi Logo.
Hmm i ll try but i have to install twrp from adb for backup.
Cwm backup not promising.
You think there ll be problem in hardwere?
No problem in hardware.
and yes do it twrp only. never try cwm.
the thing is i am not able to enter into recovery mode at all.
No recovery and fastboot accessible.
Then connect it to PC and tell me what name the device manager shows for the device.
fastboot is accessible.
i've flashed fastboot rom from miui. successfully completed. but it won't boot.
yesterday it booted into system so i was charging the phone, as soon as i removed charger it went the same boot looping.
now,
clicking flash_all_except_storage from fastboot command
it shows one line in every process - 'target reported max size 80909989 '
process goes on and success.
but does not boot into system. same bootloop.
one strange thing is,
when i connect to pc, - just by pressing vol down button i'm entering to fastboot. (even without holding power button)
does this mean there's something wrong with power button which causing cont. reboot? i mean it cont. forcing system to on and off? :s
Nothing is wrong with the hardware. In this situation the phone boots into fastboot by pressing vol when plugged in.
You didn't answer my question. What does it show in device manager on PC.
sorry for late reply , net connection loss
device manager
1st one is android booloader interface
other devices - bluetooth peripheral devices
Did you use miflash tool to flash fastboot rom
yes,
flashed successfully says miflash.
While flashing using miflash did you select all files in advanced menu properly.
Like all the bat, mbn and xml files.
i didnt try all the file separatly.
trying now.
Then go to advance and choose all the respective files properly.
1st one - flash_all_except_storage.xml
2nd one - nvflash_all.bat (leave it as it is)
3rd one - MPRG8974.mbn
4th one - 8974_msimage.mbn
5th one - rawprogram0.xml
6th one - patch0.xml
i found
flash_all.bat
could not find nvboot script
flash programmer
boot image
could not find kernelflinger image
could not find UFS provision image
RAW xml file
patch xml file
should i go with files?
Which MiFlash tool are you using.
I used the 2014.05.09.0 version
Try this one.
And extract the fastboot ROM twice till you get the images folder inside the "cancro_images_V7.0.****" folder. There you'll fill all the files.
Then in miflash click browse and select that images folder.
And in advanced options select the respective files which are there outside the images folder.
2015.10.28 version
i ll leave the navboot as it is.
giving it a try.
appreciate your help brother.
If it doesn't work then try my version.
It has proper names of files. To avoid confusion.
And all files are there in fastboot ROM except nvboot
i checked on miui
no halos.bin
tz.bin
these all files?
p.s.
operation completed successfully but same boot loop.
trying your version now.
hi,
my micromax a1 was runnning marshmallow 6.0.1 when during a security patch update installation got stuck and failed to boot again. now just booting into "dead android with exclamation mark". upon pressing power button and volume up and going into recovery(Android stock recovery) menu , cant wipe partition or data as it throws error "E: failed to mount/ cache" errors..
upon trying to install with any SD card also throws same error.
then i tried to install through ADB, while connecting to PC , PC not detecting mobile in recovery mode but detecting in bootloader mode. with fastboot flash command (for installing TWRP/CWM) in bootloader mode, error coming as "sending recovery failed(unknown status code)" .
Kindly help...
same happened to me yesterday . do you find any solution ??
Hi there !
STEP 1: DOWNLOAD the FLASH TOOL from this this link :LINK TO DOWNLOAD FILE
It is almost 30 MB in Size. And EXTRACT / UNZIP it to Desktop ( OR SOMEWHERE ) of your computer.
STEP 2: DOWNLOAD LOLLIPOP FLASH FILE
DOWNLOAD LINK FOR LOLLIPOP: HERE
After downloading this flash file EXTRACT / UNZIP it to Desktop ( OR SOMEWHERE ) on your computer.
STEP 3: NOW INSTALL DRIVERS:
YOU NEED TO BE ON WINDOWS 7 TO INSTALL DRIVERS (WINDOWS 8 DOESN'T SUPPORT THIS DRIVER / PHONE IS NOT DETECTED)
DOWNLOAD DRIVERS from this link : HERE
EXTRACT AND INSTALL THE DRIVERS : Next next next and finish If you see an security warning ( a red coloured pop up ) choose INSTALL IT ANYWAY
IT IS RECOMMENDED YOU TO RESTART YOUR PC.
STEP 4:
Now we have Extrated /unziped 2 files. One is FLASHTOOLS and other is FLASH FILE and Extracted it or unziped it to Desktop or Somewhere.
One of it having the name SP_Flash_Tool_exe_windows_v5.1424.00 or open both folders then one of it having the flashing tool. OPEN THE FOLDER NAMED SP_Flash_Tool_exe_windows_v5.1424.00
it contains an application named fashtool.exe OPEN IT
NOW THE APPLICATION IS ASKING FOR SCATTER LOADING FILE
its a txt file which is on the extracted flash file folder
BROWSE it by clicking Button named Scatter Loading
click OPEN
STEP 5:
HERE IN THE DROPDOWN BOX, IT SAYS DOWNLOAD ONLY, CLICK ON IT AND SELECT FIRMWARE UPDATE ONLY.
IF YOU SELECT FORMAT + DOWNLOAD, THEN YOU WILL LOOSE IMEI NUMBER.
NOW CLICK DOWNLOAD BUTTON ( GREEN ARROWED BUTTON NAMED DOWNLOAD )
IN CASE YOU LOOSE IMEI NUMBER, THEN REFER HERE
STEP 6:
Now SWITCH OFF your PHONE and REMOVE BATTERY
STEP 7:
CONNECT your PC via USB CABLE
wait for the driver Detection.
THE FLASHING PROCESS WILL START AUTOMATICALLY you can See the progress in progress bar which is on bottom of flashing tool Application.
WHEN IT IS FINISHED DISCONNECT USB AND RESTART YOUR PHONE.
NOW YOU WILL GET LOLLIPOP UPDATE IMMEDIATELY.
NOW REFER HERE TO ROOT MARSHMALLOW
HIT THANKS IF HELPED
if link do not work here properly then just google 'canvas a1 stuck on startup' ... and follow link in associated with xda
Device is dead
My phone is neither switching on, nor charging.
I flashed the stock ROM due to some problem with the rooted device through SP Flash tools. It completed successfully, but the device is not switching on or charging.
KIndly help
Hello,
I've got an X526 phone that overnight lost its signal.
I tried the different solutions found on the forum.
- Erase Modem
fastboot erase modemst1
fastboot erase modemst2
- Installation of the Indian 21s rom stock then flash of the bootloader+modem 21s and 19s file.
- Attempt to install CUOCO ROM but it is impossible because it is for the X527 "s2"and not the X526 "s2_ww".
Do you have any other suggestions? or other way to install CUOCO ROM?
Thanks
there is a way to skip the device model verification. But Roms are specifically made to use the particular hardware in the device. The rom may not install and you might get other errors while installing if the rom is not compatible with the device, or you will struck in bootloop or you may experience UI crashes. If you are okay with that, follow this
Prerequisites: Download and install notepad++ on your pc
Download compatible Rom
Extract it with winrar or 7zip
Browse to "Rom/META-INF\com\google\android" and locate this file "updater-script"
Open that file with "Notepad++"
put "#" before this line: assert(getprop("ro.product.device") i.e., #assert(getprop("ro.product.device")
and do the same for lines start with "getprop("ro.product.device")" # getprop("ro.product.device")
........it must be first 2 or three lines depending on the model......
save it and close notepad++
navigate to the parent folder (which contains all files like "meta INF and install" folders and other files)
right click and click "add to archive" and save it as "Zip file"
Copy & flash through TWRP
you wont get Error 7 but you might get other errors while installing if the rom is not compatible with the device
Good Luck
My smartphone was running on Android 9 pie. I am saying "was running" beacuse i am in a trouble now... I flashed a custom recovery(TWRP) and I installed a custom rom (LingeaOS) without wipping storage... from that time TWRP shows that "No os installed" .. It restart again and again but without starting android..Whenever I tried to restore my backuped stock rom It shows an error message"Failed to mount /system".. then I flashed another custom recovery(CWM).. And now it restart again and again I've tried to rebboot it in custom recovery mood but I 've failed... Is my Smartphone is bricked?? Is there any way to solve this problem??
This is how to fix it
Naim178 said:
My smartphone was running on Android 9 pie. I am saying "was running" beacuse i am in a trouble now... I flashed a custom recovery(TWRP) and I installed a custom rom (LingeaOS) without wipping storage... from that time TWRP shows that "No os installed" .. It restart again and again but without starting android..Whenever I tried to restore my backuped stock rom It shows an error message"Failed to mount /system".. then I flashed another custom recovery(CWM).. And now it restart again and again I've tried to rebboot it in custom recovery mood but I 've failed... Is my Smartphone is bricked?? Is there any way to solve this problem??
Click to expand...
Click to collapse
Yes, this is called a soft brick.
You can solve the problem by doing the following:
-Your bootloader should be unlocked, and I think you've already unlocked it since you were trying to flash a custom ROM.
-You need to have a STOCK ROM of your exact phone model, this is different from TWRP backup, search google for your phone model's stock rom and download.
-You should have Fastboot and ADB installed on your pc.
-boot to fastboot mode (volume up+power, then navigate to fastboot mode).
-connect your phone to pc with USB cable
-open the folder where you have downloaded the minimal adb and fastboot, and open cmd window there with right lick or click cmd-here.exe
-now type fastboot devices, and there should be an alphanumeric code. This means your device is connected. If it is not showing up, try downloading 'minimal adb and fastboot tool' and clicking cmd-here.exe.
-In the stock rom file, there will be a file called 'firmware', and inside it there should be these files: 'system.img' 'recovery.img' 'cache.img' 'userdata.img' 'boot.img'
-Copy all 5 of these, then go to the folder where you have adb and fastboot, go inside that folder( to the place where you have all the adb and fastboot files like adbWinApi.dll). Now paste the 5 files here.
-open cmd window again, and type the following:
1) fastboot erase boot
2) fastboot flash boot boot.img
3)fastboot erase system
4)fastboot flash system system.img
5)fastboot erase recovery
6)fastboot flash recovery recovery.img
7)fastboot erase cache
8)fastboot flash cache cache.img
9)fastboot erase userdata (this may be called data, if fastboot shows an error message, type data instead)
10)fastboot flash userdata userdata.img
and you are done, this should enable you to restore your phone.
If you are unable to access your bootloader, try flashing your stock ROM with SP Flash tool (if you have a mediatek device). You have to have your stock ROM downloaded on your pc. Connect phone to pc via usb, open SP Flash tool, select your firmware file in the topmost box, and in the box beneath that, select the file ending in scatter.txt from your firmware file. Uncheck 'preloader' if it shows up on your screen, then click 'download'. Do not disconnect your phone during the process. When it is finished, there will be a green tick, and you should be able to restart your device.
Hello, I chose "reboot in recovery" on Pixel UI Plus A11 ROM and now ended up with bootloop on "Redmi" logo.
If I press power+down, the screen turns off and MediaTek USB Port appears in Windows Device Manager for a moment and then disappears and "Redmi" logo shows up again.
If I press Up+Down+Power at the same time, the screen turns off, after around 30 seconds the phone vibrates once and then screen is still blank. At this time, "MediaTek USB Port" device keeps reconnecting in Device Manager. I can't turn off the phone with these 3 buttons. Should I disassemble the phone and disconnect the battery?
How can I repair my phone? Please help.
Hello. I had a similar issue that I tried to solve, that happened after I flashed a recovery image. It took me several hours to figure out how to fix it, but after some search, I can provide a good solution for this issue.
First, you going to need some things. For this procedure you will need the SP Flash Tool (I suggest downloading and installing MiFlashPro if you want to mess with modifications, because it installs all the tools you may need), VD171's MTK bypass tool and a fastboot MIUI ROM for your device (you can choose your preferred version here). I also suggest using the 7zip file manager, because it will be needed as well (for example, you have to extract the fastboot images from the .tar.tgz file).
After getting the files and installing the programs I mentioned above, you should follow the instructions from the MTK bypass tool thread I linked and run the batch file. In case that you get any error from the Python script and it doesn't actually run, you can try installing VSCode/VSCodium, open the main.py file, click on "Run and Debug" (you may have to install a Python debugger first) and then click on the "Run and Debug" button and it should work just fine. Connect your device while it still works, it will be detected by the script. Don't disconnect your device.
If you got the "Protection disabled" output from the MTK bypass tool, you're ready to flash the ROM. Extract the fastboot ROM files (if you haven't already extracted them) and launch the SP Flash Tool. Go to Options>Option>Connections and choose UART, the COM port that appears in the choices and choose "921600" as the baud rate. For the Download Agent, click on "Choose" and use the "DA_6765_6785_6768_6873_6885_6853.bin" file. For the Scatter-loading file, go to "Choose", go to the directory you extracted the files of the fastboot ROM > images > "MT6768_Android_scatter.txt" (or similar). Then, a list of image files will appear. Check all of them. You don't need an authentication file.
Then choose "Download Only" from the dropdown options and click on Download. If you get a warning after seeing the bottom bar loading, change the dropdown from "Download Only" to "Firmware Upgrade" and click on download. Then you have to wait for a few minutes. After that, your device will be able to boot properly. The only downside is that it locks the device and you have to unlock it again.
That's how I fixed my device. I hope my instructions to be useful to you.
getimiskon said:
Hello. I had a similar issue that I tried to solve, that happened after I flashed a recovery image. It took me several hours to figure out how to fix it, but after some search, I can provide a good solution for this issue.
First, you going to need some things. For this procedure you will need the SP Flash Tool (I suggest downloading and installing MiFlashPro if you want to mess with modifications, because it installs all the tools you may need), VD171's MTK bypass tool and a fastboot MIUI ROM for your device (you can choose your preferred version here). I also suggest using the 7zip file manager, because it will be needed as well (for example, you have to extract the fastboot images from the .tar.tgz file).
After getting the files and installing the programs I mentioned above, you should follow the instructions from the MTK bypass tool thread I linked and run the batch file. In case that you get any error from the Python script and it doesn't actually run, you can try installing VSCode/VSCodium, open the main.py file, click on "Run and Debug" (you may have to install a Python debugger first) and then click on the "Run and Debug" button and it should work just fine. Connect your device while it still works, it will be detected by the script. Don't disconnect your device.
If you got the "Protection disabled" output from the MTK bypass tool, you're ready to flash the ROM. Extract the fastboot ROM files (if you haven't already extracted them) and launch the SP Flash Tool. Go to Options>Option>Connections and choose UART, the COM port that appears in the choices and choose "921600" as the baud rate. For the Download Agent, click on "Choose" and use the "DA_6765_6785_6768_6873_6885_6853.bin" file. For the Scatter-loading file, go to "Choose", go to the directory you extracted the files of the fastboot ROM > images > "MT6768_Android_scatter.txt" (or similar). Then, a list of image files will appear. Check all of them. You don't need an authentication file.
Then choose "Download Only" from the dropdown options and click on Download. If you get a warning after seeing the bottom bar loading, change the dropdown from "Download Only" to "Firmware Upgrade" and click on download. Then you have to wait for a few minutes. After that, your device will be able to boot properly. The only downside is that it locks the device and you have to unlock it again.
That's how I fixed my device. I hope my instructions to be useful to you.
Click to expand...
Click to collapse
my phone not recognized as mediatek usb port any solution??