Hi. My phone symphony W17 ( mt6572) is stuck on bootloop. I tried flashing stock rom using sp flash tool in format all + download mode. I tried clearing dalvik cache and data but no luck.
Firmware I flashed - https://www.mediafire.com/file/8csalmwtcxf0nme/Symphony_W17_V01.5_UP11.zip
SP flash tool version - 5.1516
Scatter - https://drive.google.com/file/d/12jhrdeM8bKjPU5Ej0KZVfEK4ZBg5DVzq/view?usp=sharing
Please help me
try fastboot format:ext4 userdata
aIecxs said:
try fastboot format:ext4 userdata
Click to expand...
Click to collapse
what to do after that ? should i try flashing phone again?
phone should boot again, or at least /data should be mountable. you can repeat for cache partition that is basically what factory reset does
aIecxs said:
phone should boot again, or at least /data should be mountable. you can repeat for cache partition that is basically what factory reset does
Click to expand...
Click to collapse
No. it cant get out of bootloop
I think its the end of my phone
you should figure out the reason for boot loop with adb logcat
for this you need to enable usb-debugging via modifying default.prop first.
check out this thread and come back with logcat
Bypass secure USB debugging prompt on phone with broken screen
aIecxs said:
you should figure out the reason for boot loop with adb logcat
for this you need to enable usb-debugging via modifying default.prop first.
check out this thread and come back with logcat
Bypass secure USB debugging prompt on phone with broken screen
Click to expand...
Click to collapse
I somehow flashed cwm recovery and connected my device to pc and i was trying to edit the default.prop and build.prop but i got these errors
Code:
E:\Downloads\platform-tools_r31.0.3-windows (1)\platform-tools>adb pull /data/property/persist.sys.usb.config
adb: error: remote object '/data/property/persist.sys.usb.config' does not exist
Code:
E:\Downloads\platform-tools_r31.0.3-windows (1)\platform-tools>adb pull /system/build.prop
adb: error: remote object '/system/build.prop' does not exist
.
Help
Code:
adb shell mount /system
adb pull /system/system/build.prop
or maybe
Code:
adb shell mount /system_root
adb pull /system_root/system/build.prop
aIecxs said:
Code:
adb shell mount /system
adb pull /system/system/build.prop
or maybe
Code:
adb shell mount /system_root
adb pull /system_root/system/build.prop
Click to expand...
Click to collapse
I have lost all hopes and i will save money for a new phone. Thanks for trying to help me
aIecxs said:
Code:
adb shell mount /system
adb pull /system/system/build.prop
or maybe
Code:
adb shell mount /system_root
adb pull /system_root/system/build.prop
Click to expand...
Click to collapse
Hey bro, after many days i flashed the same rom and it booted but im getting many errors such as apps crashing and also a wifi named "NVRAM WARNING ERR X10" is appearing. please help me. I somehow got into settings and enabled usb debuging
first you should recover NVRAM
How to use SN Write Tool to Write IMEI on MediaTek Devices
please capture logcat during boot for further debugging
Code:
adb logcat '*:W' -b all > logcat.txt
aIecxs said:
first you should recover NVRAM
How to use SN Write Tool to Write IMEI on MediaTek Devices
please capture logcat during boot for further debugging
Code:
adb logcat '*:W' -b all > logcat.txt
Click to expand...
Click to collapse
Im getting this error
Junaid433 said:
Hi. My phone symphony W17 ( mt6572) is stuck on bootloop. I tried flashing stock rom using sp flash tool in format all + download mode. I tried clearing dalvik cache and data but no luck.
Firmware I flashed - https://www.mediafire.com/file/8csalmwtcxf0nme/Symphony_W17_V01.5_UP11.zip
SP flash tool version - 5.1516
Scatter - https://drive.google.com/file/d/12jhrdeM8bKjPU5Ej0KZVfEK4ZBg5DVzq/view?usp=sharing
Please help me
Click to expand...
Click to collapse
Hi .
What did you use before installing Stoke ROM? For example, have you unlocked the phone bootloader or not?
Junaid433 said:
Hi. My phone symphony W17 ( mt6572) is stuck on bootloop. I tried flashing stock rom using sp flash tool in format all + download mode. I tried clearing dalvik cache and data but no luck.
Firmware I flashed - https://www.mediafire.com/file/8csalmwtcxf0nme/Symphony_W17_V01.5_UP11.zip
SP flash tool version - 5.1516
Scatter - https://drive.google.com/file/d/12jhrdeM8bKjPU5Ej0KZVfEK4ZBg5DVzq/view?usp=sharing
Please help HI again . perform a factory reset may solve this problem .
Click to expand...
Click to collapse
BYSOFT said:
Hi .
What did you use before installing Stoke ROM? For example, have you unlocked the phone bootloader or not?
Click to expand...
Click to collapse
bootloader is unlocked but sometime ago when i flashed this rom my phone was working fine and now when i flash this rom its stuck in bootloop. I found another rom for my phone and i flashed it and im getting errors like apps crashing and a wifi named nvram err x10
go to recovery mode and reset factory the phone may solve this problem .
BYSOFT said:
go to recovery mode and reset factory the phone and wipe the cache partition my solve this problem .
Click to expand...
Click to collapse
I even wiped data but no luck
@BYSOFT as mentioned in OP whole eMMC was erased by SP Flash Tool (format all + download)
important phone unique calibration data, bluetooth, mac address and IMEI are not included in stock ROM/firmware and must recovered manually (NVRAM and PERSIST partitions got lost forever)
aIecxs said:
@BYSOFT as mentioned in OP whole eMMC was erased by SP Flash Tool (format all + download)
important phone unique calibration data, bluetooth, mac address and IMEI are not included in stock ROM/firmware and must recovered manually (NVRAM and PERSIST partitions got lost forever)
Click to expand...
Click to collapse
Hi I flashed the rom , link is in the post and it booted and phone is working but its not detecting my sim cards help
Related
hi.my lenovo a396 has been lock and need gmail to open.i forgot the password.the phone usb debugging is off.i try to go to recovery mode,but it cant.it show nothing.it also show fastboot mode.i already try to wipe data via fastboot using android multitool,but it show failedunknown partition name).i also try to boot recovery,its say ok
but the screen show nothing.i also try to flash recovery,it also show failedunknown partition name).it is because corrupted data partition?or i not follow a proper step for
afattah18 said:
hi.my lenovo a396 has been lock and need gmail to open.i forgot the password.the phone usb debugging is off.i try to go to recovery mode,but it cant.it show nothing.it also show fastboot mode.i already try to wipe data via fastboot using android multitool,but it show failedunknown partition name).i also try to boot recovery,its say ok
but the screen show nothing.i also try to flash recovery,it also show failedunknown partition name).it is because corrupted data partition?or i not follow a proper step for
Click to expand...
Click to collapse
Go to fastboot mode and flash TWRP recovery.
Then open built in file manager of twrp and delete data/system/gesture.key or settings.db
Tyaginator said:
Go to fastboot mode and flash TWRP recovery.
Then open built in file manager of twrp and delete data/system/gesture.key or settings.db
Click to expand...
Click to collapse
i already try that.it also say failed (uknown partition name)..cannot flash anything.is it because emmc data partition corrupt?
afattah18 said:
i already try that.it also say failed (uknown partition name)..cannot flash anything.is it because emmc data partition corrupt?
Click to expand...
Click to collapse
Then try flashing your firmware
Tyaginator said:
Then try flashing your firmware
Click to expand...
Click to collapse
same case. failure partitions if flushing.
rusnanto21 said:
same case. failure partitions if flushing.
Click to expand...
Click to collapse
Is ur device listed in fastboot devices, and which command are you using to wipe a partition. And is there any bootloader lock in ur device.
Sent from a Device using an App!
Hi guys,
I have a rooted Device with CM and TWRP installed, but someting happenend using the device and my Moto G got stuck on startup logo and Recovery TWRP logo, with adb I have acess to adb shell but everything else like adb reboot bootloader etc doesn't seems to work, with adb shell I have realized that the TWRP wasn't running 'cause when I use the interface on shell I get this message
$twrp wipe cache
"TWRP does not appear to be running. Waiting for TWRP to start"
Is there any way to install a new recovery via adb shell or reinstall a new rom, factory reset or something like that to make my cellphone work again?
Thanks,
If you are okay to wipe internal storage, the following fastboot command will probably make TWRP load again:
fastboot erase userdata
fastboot flash recovery newrecovery.img - is a way to reflash recovery, however the above command may still be required.
The problem is that with fastboot the device is not recognized, only when I open the recovery mode...
The logo freezes but the device is reconigzed with adb devices...
gconsentini said:
The problem is that with fastboot the device is not recognized, only when I open the recovery mode...
The logo freezes but the device is reconigzed with adb devices...
Click to expand...
Click to collapse
What OS are you using? Maybe try the ADB commands:
adb shell
wipe data
lost101 said:
What OS are you using? Maybe try the ADB commands:
adb shell
wipe data
Click to expand...
Click to collapse
It's the latest CM
I'll try, but the last time I got this message.
"TWRP does not appear to be running. Waiting for TWRP to start . . .
Press CTRL + C to quit."
EDIT
using
adb shell
twrp wipe data
happened the same above
gconsentini said:
It's the latest CM
I'll try, but the last time I got this message.
"TWRP does not appear to be running. Waiting for TWRP to start . . .
Press CTRL + C to quit."
EDIT
using
adb shell
twrp wipe data
happened the same above
Click to expand...
Click to collapse
I meant what OS on PC are you using. Stop adding the phrase 'twrp' - type the command as I wrote it.
lost101 said:
I meant what OS on PC are you using. Stop adding the phrase 'twrp' - type the command as I wrote it.
Click to expand...
Click to collapse
Sorry, I'm using Windows 10, if I use only wipe data, the command wipe is not reconigzed.
Can you enter fastboot mode by holding vol down and powering phone on?
lost101 said:
Can you enter fastboot mode by holding vol down and powering phone on?
Click to expand...
Click to collapse
yes, but when I connect the phone usb and use fastboot devices
it has no devices on the list
gconsentini said:
yes, but when I connect the phone usb and use fastboot devices
it has no devices on the list
Click to expand...
Click to collapse
There are many threads on Win10 and usb driver issues. If you don't want to try to fix fastboot on Windows, you could boot into a Ubuntu Linux LiveCD and install fastboot there.
lost101 said:
There are many threads on Win10 and usb driver issues. If you don't want to try to fix fastboot on Windows, you could boot into a Ubuntu Linux LiveCD and install fastboot there.
Click to expand...
Click to collapse
Yes, I thought about that too =x
SOLVED
Guys the problem was that I've not installed the drivers before, after doing this, I just installed the stock rom from motorola.
Thanks
gconsentini said:
SOLVED
Guys the problem was that I've not installed the drivers before, after doing this, I just installed the stock rom from motorola.
Thanks
Click to expand...
Click to collapse
Hey i'm having the same issue, would you mind telling me how you re-flashed the Motorola rom, Thanks
thomasswan5547 said:
Hey i'm having the same issue, would you mind telling me how you re-flashed the Motorola rom, Thanks
Click to expand...
Click to collapse
Install the Minimal Fastboot & ADB package and the Motorola USB drivers, use the mfastboot package and install the stock ROM as per the instructions provided, but ignore the disassembly part, unless you have your phone does not respond to keypresses.
https://forum.xda-developers.com/showpost.php?p=71328823&postcount=915
Hey,
Hopefully you guys can give me some help with the problem ive been having,
My nexus 5 is stuck in bootloop, i can get into the bootloader and the lockstate is unlocked but no custom recovery is appearing like it used to. I tried flashing using ADB but my phone doesn't show up as a device on my pc.
i have tried to wipe the cache ect and it comes up with "E:failed to mount /cache (invalid argument)
I only really know the basics of this stuff (only ever used the basic stuff to root and flash my phone)
You must use fastboot commands while being into the bootloader, not adb.
mworley1991 said:
Hey,
Hopefully you guys can give me some help with the problem ive been having,
My nexus 5 is stuck in bootloop, i can get into the bootloader and the lockstate is unlocked but no custom recovery is appearing like it used to. I tried flashing using ADB but my phone doesn't show up as a device on my pc.
i have tried to wipe the cache ect and it comes up with "E:failed to mount /cache (invalid argument)
I only really know the basics of this stuff (only ever used the basic stuff to root and flash my phone)
Click to expand...
Click to collapse
Yeah, exactly what primokorn says...
Primokorn said:
You must use fastboot commands while being into the bootloader, not adb.
Click to expand...
Click to collapse
If you use the command "fastboot devices" and your phone with a code appears in the command prompt then there's no problem with your drivers.
Just reflash the factory image, you can use the automatic process if you run "flash all". You can also flash the images manually but if you go for that option make sure you don't forget to flash the cache image, that will fix your problem with mounting the cache partition.
ADB commands are used when the phone is booted into the ROM.
Flash the latest stock ROM from here to see if it solves the issue: https://developers.google.com/android/nexus/images
If the phone still bootloops, flash the userdata.img in fastboot. After flashing the userdata.img file in fastboot, boot directly into stock recovery using the power/volume buttons, perform a factory wipe, and reboot.
So I totally messed up my phone. When booting it, CM logo will take forever to disappear. Hopefully I can go to bootloader. I have installed latest version of TWRP. TWRP logo stays up for about 5 minutes then it loads the main menu.
It shows internal storage o mb. If I flash custom rom or firmware, it shows unable to mount /data, /persist, /cache. Even I couldn't unmount the partition through ADB Shell as it shows error "device or resource is busy". What is the solution for this? I badly want my phone back. Even I think I lost all my important data. Please help me to solve this. What could be the actual solution? And I am a noob. So if you instruct me with a solution, be descriptive. Thank you.
Can you get in fastboot mode? If so install the latest factory image.
rdmunn said:
Can you get in fastboot mode? If so install the latest factory image.
Click to expand...
Click to collapse
I tried but device will not mount /data. So flashing fails
hiren43 said:
I tried but device will not mount /data. So flashing fails
Click to expand...
Click to collapse
Try this fastboot command:
Code:
fastboot erase data
fastboot erase cache
Recently I installed a custom ROM that is meant to be installed on a Huawei P8, for my Huawei P8 lite as my new OS because I accidentally deleted my whole OS. When I plug my mobile phone to a power source it shows the Huawei logo, I cannot get it into fastboot/rescue mode. If I try the dload folder to sd-card method it will not do anything. Does anyone know what to do.
Flash the stock firmware. I'm 100% sure your problem would be solved.
munimjaffer said:
Flash the stock firmware. I'm 100% sure your problem would be solved.
Click to expand...
Click to collapse
How do I flash it without fastboot?
pim8181 said:
How do I flash it without fastboot?
Click to expand...
Click to collapse
What do u see when u try to enter fastboot?
munimjaffer said:
What do u see when u try to enter fastboot?
Click to expand...
Click to collapse
When I try to enter fastboot I just see the Huawei logo
pim8181 said:
When I try to enter fastboot I just see the Huawei logo
Click to expand...
Click to collapse
Ok can u enter into recovery mode?
munimjaffer said:
Ok can u enter into recovery mode?
Click to expand...
Click to collapse
Nope....
Your phone got hardbricked with flashing a wrong rom,hardbrick is really hard to unbrick,
i already have one phone that got hardbricked due to flashing a wrong rom,since now i can't find the solution to unbrick it,
hope you find the solution soon..
pim8181 said:
Nope....
Click to expand...
Click to collapse
Is the device recognized by PC? If not, what is device manager labeling the device as?
If it connects to PC and is recognized you can.........
Use adb to clear cache and dalvik/ART cache, then see if the device will boot to recovery or fastboot, if not then power the device off and remove the battery then reinsert the battery(if it has a removable battery). Then leave the device off and connect it to PC then open a adb terminal and type:
adb reboot bootloader (press enter, sometimes the deamon has to start, if nothing happens then type adb reboot bootloader a second time, some devices can be booted from a powered off state with adb)
If that doesn't work try typing:
adb reboot fastboot (press enter).
If none of that works to boot fastboot then try turning the device on, when it gets to the logo, connect the device to PC, open a adb terminal and type:
adb devices (press enter, if it returns a serial number the device is recognized)
Then type:
adb reboot bootloader (press enter and it may boot to fastboot)
Or type:
adb reboot fastboot (press enter)
Or type:
reboot fastboot (press enter)
If none of that gets you to fastboot and you can't boot it manually with the buttons then you're bricked, its not hardbricked though because it boots to logo so that means bootloader is at least there even if it is corrupted and whether anything else is there or works or not.
Whatever you flashed must have had some differences in partitions that flashed over your partitions in places that weren't correct for your device, its more than just the software not being for your device, it is structured completely different than your device.
You've got to get to fastboot someway to flash the stock firmware, that's the only thing I see being able to correct your partitions and put the .imgs in the places they are meant to go.
There is also the possibility that you can download your stock firmware, then extract the kernel(Zimage, its sometimes bundled with/called boot.img or recovery.img, depending on device and android version), the boot.img, the recovery.img and the system.img and then do some research on your device model number and find out which partition(mmcblk0) each of those imgs go in(I could tell you how to use adb to find the partitions but that wouldn't help if flashing the wrong things has screwed up their placements). Then, if adb is working with the device you can use the dd command to manually push the boot.img to its mmcblk0, the recovery.img to its mmcblk0 and the system.img to its mmcblk0.
I would start with dd-ing the recovery, then seeing if it will boot to recovery, if the recovery is a custom recovery and you have a nandroid backup or a correct ROM zip, try restoring or flashing. If it doesn't then dd the boot.img to its mmcblk0 and see if it boots to recovery, if not, dd the system.img to its mmcblk0, you can repeat this process with each of the .imgs in your stock firmware. Maybe if you can push enough to the device it will restore some functionality that will allow you to get booted to a state will allow you to completely reflash the device.
If the confused you then I might have confused myself typing it, lol.