Dear friends, I am really despaired. My brand new does not work.
Yesterday I wanted to root the phone, and so unlocked the bootloader first ( phone was updated to mashmallow) . All was done ok and the boatlodear was freed. Then I flashed the twrp version 2.8.7.0 and was installed too. Then went to install the supsersu and did it, but when i restarted the phone is got stuck in the warning unlocked bootloader screen and does not intendted to boot, nothing.... .
I donwloaded 3 diverse roms, 2 custom and one official, I pushed to the phone through twrp and they go to the phone but when try to install I always get errors.
for example i get : could not detect filesystem for /dev/block/bootdevice/dy-name/system at system no such file or directory
mount failed to mound ( the above )
unmount of /system failed no such volume
script succeded result was ( 0.200000)
and even that for one of the roms I get succesfull nothing is installed and the phone bots only on fastboot, there is no operative system at all there, even that the internal storage seems ok because I can access to in via PC!
I tried also via abd to install and even that the phone does connect and show in the abd devices when I send a command in adb i get only the flushing of the help screeen of adb!!
Please anyone help, I just bought that phone one week ago!
Then you flashed an old version of TWRP. Use the updated version.
didn't you take backup before flashing SU ??
Related
Edit: All happy now, a change of pc solved the problem of not detecting the device!
Hi all! I have another challenge for you!
Right, I've got myself in a tizz with my Defy +. While updating between CM10.1 versions I found myself in a situation where I couldn't get past the boot animation. So I loaded the TWRP restore I had made prior to updating...
Except it wouldn't, instead it came up with 'Failed' each time I tried any of the TWRP backups I had created. So the next step was to wipe partitions and start flashing various ROMs until I found one what worked. Except they didn't work either. Eventually I thought the best idea would be to just turn the phone off and see where I was with booting.
So power on, boot logo, blue light, red light then... nothing. Just the boot logo static. Went into the custom bootloader to go into recovery again, nothing. Pressing Custom recovery simply loops back to the top bootloader screen.
Ok next step, flash .sbf and start from scratch. So into the Moto bootloader it is to plug in and flash except... it's no longer detected by my computer.
"Ok" I think, "We'll just flash files from the SD card after I use an external SD card reader.
Except now when I enter Moto recovery to flash the TWRP recovery I get:
-- Install /sdcard ...
Finding update package...
Opening update package...
Verifying update package...
E:failed to verify whole-file signature
E:signature verifiaion failed
Installation aborted
So to recap:
1) Tried to flash and update, failed
2) Tried to recover, recoveries wouldn't write (I think this is becaue I'd changed to EXT4 on /data and /cache and had forgotten to go back to EXT3 before trying to recover)
3) Tried to boot, epicly failed
4) Tried to flash .sbf, Defy+ won't appear in RSDLite 5.7 with latest driver
5) Tried to flash from SD card, sig verification failed
6) Googletastic for the last four days
Notes:
a) I CAN charge the Defy+ using the wall charger but I get '?' for the battery level indicator but...
b) In Cmod bootloader 2.1 (Which I can use a little) it shows the correct battery level
c) I /was/ getting some errors with not being able to mount /cache from the moto recovery but I've since used the cmod bootmenu 2.1 to set it back to ext3 and it's all happy now, those errors aren't appearing
d) Plugging in my Defy red lens I get W8 x64 detecting the correct portal drivers and such but when I go to moto bootloader this device also doesn't appear in RSDLite
e) Both devices prompt windows to install a Motorola Flash Interface driver in Device Manager when plugged in in moto bootloader mode and neither device appears in RSDLite despite the fact the program is running in Admin mode
f) Looking at the logs in bootloader, it appears that I might not have formatted anything from ext4 to 3, everything I select in the cmod bootmenu returns .E:Error in /system/... , (Result: Invalid arguement) , Done..
So at the moment I think I need to acheive one of the following:
1) Find a file that allows me to write any useful data to /system like a recovery or some of those bootmenu files that passes the signature verification
2) Find a way to troubleshoot RSDLite so I can actually flash .sbf and get out of this hellhole
Many regards!
Alexis
If your custom recovery is not working, then you cannot do anything other than flash an sbf(nothing except data and cache wipe can be done via stock recovery): this is due to the locked boot loader(recoveries cannot be simply flashed from the stock recovery as you're trying to do)
Sent from my MB526 using Tapatalk 2
Success (ish)!
Yes I swapped to a different machine and then upgraded the version of RSD Lite installed on it from 4.7 to 6.1.5
[URL="http://forum.gsmhosting.com/vbb/f166/rsdlite-6-0-mtk-patch20-rsd-lite-6-0-a-1545012/index2.html#post8988239"]http://forum.gsmhosting.com/vbb/f166/rsdlite-6-0-mtk-patch20-rsd-lite-6-0-a-1545012/index2.html#post8988239
And flashed the 'lower' of the two .sbf's from the links on this forum for the British variant. After a DEA1 error (Phone is dead, code corrupt and all the bad things) I managed to flash the file.
As of yet I've not managed to get out of the bootloop but I've not carried out the requisite steps as mentioned in the "So you think you've bricked your Defy/Defy+" thread.
Lessons learned:
1) Motorola drivers and RSD Lite are pennickety, you will probably need to mix them up in order to get them to behave properly
2) If all else fails, use a different computer
3) You will probably need to flash over and over, while making every effort to not muck them up. Be aware the efuse system only has limited uses before it's useless though...
My saga continues, from no USB support hopefully to a fully working device again
In the end switching PC then doing the factory reset from moto recovery let the phone boot, all standard but the dodgy USB stuff at the first post is what sent me away from the right track.
Hello,
Ok, here is the situation
I have a Zuk Z1 with last COS update 12.1 with locked bootloader, no root etc ... (I didn't touch anything).
Yesterday, it reboot by itself but I got bootloop (starting apps then again lenovo boot image ...)
I try to factory reset by using the recovery metohd, it's start normally (optimizing apps ...) but then reboot and again bootloop ...
So I try to sideload the official COS ROM from Cyanogen Support (cm-12.1-YOG4PAS9IG-ham-signed-d4fc2c5394.zip), but the sideload stuck at 47% and saying total xfer: 1.00x and the phone go back to recovery but still have boot loop ...
I try to boot in fastboot and use the All In One tool to flash official ROM but didn't work (Its say that the bootloader is lock)
I find without knowing this menu a debugging hardware tool test, and then I run the test, its say SD : Fail and in another I got SD : Fail and no sd fuse in dir
I saw many thread here and on google, and some say that we have to use qfil/qpst method, and find this which seems complete : http://www.androidbrick.com/lenovo-zuk-phones-qfil-roms-unbrick-guide/
But as I don't know if its hardware issue or soft brick ...
Could someone help me to recover my phone to COS or CM by using the right method ?
Thank you !
wackou said:
Hello,
Ok, here is the situation
I have a Zuk Z1 with last COS update 12.1 with locked bootloader, no root etc ... (I didn't touch anything).
Yesterday, it reboot by itself but I got bootloop (starting apps then again lenovo boot image ...)
I try to factory reset by using the recovery metohd, it's start normally (optimizing apps ...) but then reboot and again bootloop ...
So I try to sideload the official COS ROM from Cyanogen Support (cm-12.1-YOG4PAS9IG-ham-signed-d4fc2c5394.zip), but the sideload stuck at 47% and saying total xfer: 1.00x and the phone go back to recovery but still have boot loop ...
I try to boot in fastboot and use the All In One tool to flash official ROM but didn't work (Its say that the bootloader is lock)
I find without knowing this menu a debugging hardware tool test, and then I run the test, its say SD : Fail and in another I got SD : Fail and no sd fuse in dir
I saw many thread here and on google, and some say that we have to use qfil/qpst method, and find this which seems complete : http://www.androidbrick.com/lenovo-zuk-phones-qfil-roms-unbrick-guide/
But as I don't know if its hardware issue or soft brick ...
Could someone help me to recover my phone to COS or CM by using the right method ?
Thank you !
Click to expand...
Click to collapse
Go with qpst/qfil method to recover your phone
And did you tried changing the USB port or cable while side loading cos ROM .. Cause most of issues are solved by the changing USB port or cable.. So try this.. Or else qfil is the option
shubhambhise said:
Go with qpst/qfil method to recover your phone
And did you tried changing the USB port or cable while side loading cos ROM .. Cause most of issues are solved by the changing USB port or cable.. So try this.. Or else qfil is the option
Click to expand...
Click to collapse
Hello,
I got help on the telegram group, we try many thing, the result is that I can only get ZUI working, if flashing COS via QFIL, I get the same result, if I flash ZUI, unlock bootloader, flash TWRP, wipe everything, then sideload CM13, TWRP say that no os is installed and I get a bootloop at the bootloader ...
ZUI is good, but I get some error regarding notification.
If you have any other idea ?
wackou said:
Hello,
Ok, here is the situation
I have a Zuk Z1 with last COS update 12.1 with locked bootloader, no root etc ... (I didn't touch anything).
Yesterday, it reboot by itself but I got bootloop (starting apps then again lenovo boot image ...)
I try to factory reset by using the recovery metohd, it's start normally (optimizing apps ...) but then reboot and again bootloop ...
So I try to sideload the official COS ROM from Cyanogen Support (cm-12.1-YOG4PAS9IG-ham-signed-d4fc2c5394.zip), but the sideload stuck at 47% and saying total xfer: 1.00x and the phone go back to recovery but still have boot loop ...
I try to boot in fastboot and use the All In One tool to flash official ROM but didn't work (Its say that the bootloader is lock)
I find without knowing this menu a debugging hardware tool test, and then I run the test, its say SD : Fail and in another I got SD : Fail and no sd fuse in dir
I saw many thread here and on google, and some say that we have to use qfil/qpst method, and find this which seems complete : http://www.androidbrick.com/lenovo-zuk-phones-qfil-roms-unbrick-guide/
But as I don't know if its hardware issue or soft brick ...
Could someone help me to recover my phone to COS or CM by using the right method ?
Thank you !
Click to expand...
Click to collapse
Hope this will help you
Check this out
http://forum.xda-developers.com/zuk-z1/help/helpppp-t3505990
http://forum.xda-developers.com/zuk-z1/general/guide-how-to-unlock-root-install-twrp-t3394037
This will help you
Asus Zenfone Selfie ZD551KL
Hello, i have a big issue with my Asus zenfone selfie. It worked properly and a week ago just restart and cannot boot again, it is bricked in bootloop.
When i go to recovery it gives me asdf/recovery/last_log (bad descriptor) error, when i clear cache, wipe data/factory reset. It clear`s it and wipe the data but when i try to power its bootlooped again, somethimes start with the screen like brand new, enter Language, Keyboard and than when give me the step to add wi-fi network immediately freeze and restart after 2-3 second and again going to bootloop.
I cannot use my phone again can samoone help me ?
(My phone first is buyed CN model and i personally change it to WW firmware and update to latest WW without problem, worked almost 2 years)
Steps i try myself :
1. connect to adb via PC, when i try adb sideload ....exe it gives me asdf/recovery/last_log (bad descriptor)
2. Put the firmware to the SDcard, and apply update from SDcard from recovery, succesfully update but bootloop remains (reocvery confirmed that the firmware is updated to WW_21.40.0.2210 )
3. Try to connect to fastboot, i have adb installed, android usb drivers on windows (adb devices in apply update from adb worked and see the phone attacked) but in fastboot adb devices does not find the device. So i can`t go furthure (i find some kind of solution but it guides me true fastboot and i stuck in not getting my phone recognized)
Kamen911 said:
Asus Zenfone Selfie ZD551KL
Hello, i have a big issue with my Asus zenfone selfie. It worked properly and a week ago just restart and cannot boot again, it is bricked in bootloop.
When i go to recovery it gives me asdf/recovery/last_log (bad descriptor) error, when i clear cache, wipe data/factory reset. It clear`s it and wipe the data but when i try to power its bootlooped again, somethimes start with the screen like brand new, enter Language, Keyboard and than when give me the step to add wi-fi network immediately freeze and restart after 2-3 second and again going to bootloop.
I cannot use my phone again can samoone help me ?
(My phone first is buyed CN model and i personally change it to WW firmware and update to latest WW without problem, worked almost 2 years)
Steps i try myself :
1. connect to adb via PC, when i try adb sideload ....exe it gives me asdf/recovery/last_log (bad descriptor)
2. Put the firmware to the SDcard, and apply update from SDcard from recovery, succesfully update but bootloop remains (reocvery confirmed that the firmware is updated to WW_21.40.0.2210 )
3. Try to connect to fastboot, i have adb installed, android usb drivers on windows (adb devices in apply update from adb worked and see the phone attacked) but in fastboot adb devices does not find the device. So i can`t go furthure (i find some kind of solution but it guides me true fastboot and i stuck in not getting my phone recognized)
Click to expand...
Click to collapse
same problem. stuck on bootloop on stock recovery
https://www.youtube.com/watch?v=cDRsEsI0qBY
Have you guys tried this method, yet?
here's the backstory
i was trying to install HavocOS but failed multiple times.. always stuck in twrp after i installed GApps.. then i remember i tried to flash the HavocOS rom before the stock firmware.. then it shut off for a second and now i'm stuck in twrp with unable to mount /data and unable to mount storage error
and now here's the situation
1. i can't flash any rom/zip files (turn off for a second then back to twrp)
2. i can't transfer any file to internal (not detected on pc)
3. i can't mount data
4. i can't wipe internal
5. i can't wipe data
6. error unable to mount /data and unable to mount storage on everything
7. i can't get into fastboot
8. i'm stuck in twrp
anybody know how to fix it? :crying:
SagenKrieg said:
here's the backstory
i was trying to install HavocOS but failed multiple times.. always stuck in twrp after i installed GApps.. then i remember i tried to flash the HavocOS rom before the stock firmware.. then it shut off for a second and now i'm stuck in twrp with unable to mount /data and unable to mount storage error
and now here's the situation
1. i can't flash any rom/zip files (turn off for a second then back to twrp)
2. i can't transfer any file to internal (not detected on pc)
3. i can't mount data
4. i can't wipe internal
5. i can't wipe data
6. error unable to mount /data and unable to mount storage on everything
7. i can't get into fastboot
8. i'm stuck in twrp
anybody know how to fix it? :crying:
Click to expand...
Click to collapse
have you tried reboot to bootloader option under reboot in twrp
SagenKrieg said:
here's the backstory
i was trying to install HavocOS but failed multiple times.. always stuck in twrp after i installed GApps.. then i remember i tried to flash the HavocOS rom before the stock firmware.. then it shut off for a second and now i'm stuck in twrp with unable to mount /data and unable to mount storage error
and now here's the situation
1. i can't flash any rom/zip files (turn off for a second then back to twrp)
2. i can't transfer any file to internal (not detected on pc)
3. i can't mount data
4. i can't wipe internal
5. i can't wipe data
6. error unable to mount /data and unable to mount storage on everything
7. i can't get into fastboot
8. i'm stuck in twrp
anybody know how to fix it? :crying:
Click to expand...
Click to collapse
Flash stock rom via fastboot.
And try to reboot to bootloader from twrp it'll put you in fastboot mode.
SagenKrieg said:
here's the backstory
i was trying to install HavocOS but failed multiple times.. always stuck in twrp after i installed GApps.. then i remember i tried to flash the HavocOS rom before the stock firmware.. then it shut off for a second and now i'm stuck in twrp with unable to mount /data and unable to mount storage error
and now here's the situation
1. i can't flash any rom/zip files (turn off for a second then back to twrp)
2. i can't transfer any file to internal (not detected on pc)
3. i can't mount data
4. i can't wipe internal
5. i can't wipe data
6. error unable to mount /data and unable to mount storage on everything
7. i can't get into fastboot
8. i'm stuck in twrp
anybody know how to fix it? :crying:
Click to expand...
Click to collapse
1. install the drivers again https://androidfilehost.com/?fid=890278863836289045 hope now it may connect to pc
2. check that, to reboot to fastboot mode (i kno u said abv, but just do a try.) try to reboot fastboot mode from twrp
3. download https://androidfilehost.com/?fid=11410963190603882446
4. Open firmware folder and click on flashall_AFT.cmd & wait
5. i cant say itil work just giv a try
ajayravi1122 said:
1. install the drivers again https://androidfilehost.com/?fid=890278863836289045 hope now it may connect to pc
2. check that, to reboot to fastboot mode (i kno u said abv, but just do a try.) try to reboot fastboot mode from twrp
3. download https://androidfilehost.com/?fid=11410963190603882446
4. Open firmware folder and click on flashall_AFT.cmd & wait
5. i cant say itil work just giv a try
Click to expand...
Click to collapse
That's what I told the person to do in short he/she didn't respond.
He/she should update the thread whether he/she got it working by doing something or fixed it via service center. Others just try to help without knowing if it is needed or not.
First of all, i want to say i'm sorry to all of you.. especially for those who tried to help me by replying my thread. I'm sorry for being silent and not updating on you guys. I managed to figure it out the next day after i posted this thread before any of you replied and just kinda forget this thread- which is a bad thing to do. I'm sorry guys. I won't do that ever again.
With that out of the way, i'm going to answer all of your replies
ajmalhussainhy said:
have you tried reboot to bootloader option under reboot in twrp
Click to expand...
Click to collapse
I tried that, it didn't work. Either reboot to system or bootloader, it just went back to TWRP.. with the "Keep System Read Only?" thing.. acting like i just installed TWRP for the first time. Even when i chose to turn off the device, it came back to TWRP.
z1_nile said:
Flash stock rom via fastboot.
And try to reboot to bootloader from twrp it'll put you in fastboot mode.
Click to expand...
Click to collapse
As i specified in my first post, i can't get into fastboot. Totally stuck in TWRP.
ajayravi1122 said:
1. install the drivers again https://androidfilehost.com/?fid=890278863836289045 hope now it may connect to pc
2. check that, to reboot to fastboot mode (i kno u said abv, but just do a try.) try to reboot fastboot mode from twrp
3. download https://androidfilehost.com/?fid=11410963190603882446
4. Open firmware folder and click on flashall_AFT.cmd & wait
5. i cant say itil work just giv a try
Click to expand...
Click to collapse
Didn't try that one, because as i said i've figured it out the next morning.
z1_nile said:
That's what I told the person to do in short he/she didn't respond.
He/she should update the thread whether he/she got it working by doing something or fixed it via service center. Others just try to help without knowing if it is needed or not.
Click to expand...
Click to collapse
Again, sorry for that
Here's what i did to fix the issue :
1. After some more searching in the next morning (literally the next morning, few minutes before i gone to school), i stumbled to this thread post : https://forum.xda-developers.com/showthread.php?t=2522426
it says that if you "Put the phone under a strong light and longpress power and volume down, your phone will reboot in bootloader.".
So i tried that. I hold my phone right in front of my monitor, then hold the power and volume up to get into fastboot mode. And Voila, it worked. I get into fastboot without any problem whatsoever.
Somebody else also replied "Just hold the power and volume down for a long time and hold it in front of a bright light, something about the proximity sensor."
So.. yeah. Didn't really know how it worked out, but it worked. :silly:
2. After that, i just installed a different version of TWRP (This one specifically https://dl.wafuu.id/twrp/X00T/twrp-3.2.3-0-X00T-20181214.img which i got from someone in the telegram group) and just redo the HavocOS installing process. It went smooth, and i manage to boot the system without any problem.
Problem solved. Just like that. However, i think i know what was causing the issue.
When i was trying to install the GApps (before stuck in bootloop), i only managed to get to the part when i had to choose to either save my choices or not. After that it just went back to TWRP. I didn't know that it wasn't actually installed yet, because i thought it was installed already. Yep, that was my first time installing GApps and i actually never seen the entire installing process. The way i know that is when i installed it after the fix (after i installed a different TWRP) and then saw the "installing things" part. Silly me.
So i think that was the issue. It was because i used an older version of TWRP which i got from this thread https://forum.xda-developers.com/asus-zenfone-max-pro-m1/development/recovery-twrp-3-2-1-x-t3787134 . Maybe GApps didn't support that version. I knew it was an old version of TWRP. Why i was using that version and not the latest one? Because when i tried to install the latest one from this thread https://forum.xda-developers.com/as...ent/recovery-unofficial-twrp-3-2-3-0-t3888110 , it didn't work on my phone. It fails to detect my internal memory (0mb).
I think that's all i can say. Again, i'm sorry to all you guys for the late respond. Thank you for replying my thread and trying to help me. I hope this thread will eventually help someone who faced a similar problem to mine.
*Last but not least, Shout out to Dyruz from the telegram group who provided me the working TWRP and tried to help me as best as he can. I would've not fix the issue this because of him. Cheers!
Hi,
I initially had G935FXXS3ERHD_G935FXEO3ERG2_XEO installed and flashed Glamour ROM S9+ port some time ago, now i need to return it to stock but no luck...
Using latest odin i flashed:
G935FXXU3ERL3_G935FXEO3ERKF_XEO
and
G935FXXU3ERJE_G935FXEO3ERJF_XEO
(i need to remain on 3 bootloader)
after each flash i receive the NO COMMAND screen, and cannot boot into stock recovery... only way to boot the phone is to install TWRP... I have noticed when i plug the phone is it comes up as GALAXY S9+ so i am guessing it hasn't been wiped correctly (i did formats, factory resets, wipes many many times and no change)
i have no idea what else to try
Hi,
Using latest Odin I am trying to return to my phone to stock but cannot
I have tried 4 different firmware’s already (over 20 times) and each one will PASS the flash process, phone rests, installing system update (stops at around 30%) and during the blue screen the update stops, resets, receive Erasing message for a bit and then NO COMMAND and phone will simply not boot. (with some flashes the stock recovery is not even available, working or present)
... only way to boot the phone is to install TWRP... installing the NO VERITY file seems to help in booting…
I have noticed when i plug the phone is it comes up as another device name (from a previous ROM) so i am guessing it hasn't been wiped correctly (i did formats, factory resets, wipes many many times and no change)
Back in DOWLOAD MODE under system status = CUSTOM (after flashing stock firmware)
My guess is that the new firmware I flash simply wont stick, or is half installed, or could be something to do with encryptions,
Some of the logs I see include:
Failed to open recovery
Reboot recovery cause UNKNOWN
E: Failed setting up dirty target
Fail to mount /system as rw
i have no idea what else to try