Hi all
I'm starting to suspect that the partition my recovery uses as temp storage is full.
It gets stuck in the flashing process, I just tried side-loading with adb and it is now stuck, and has been for 1 hour.
Latest message from ADB says:
Code:
serving: cm-13.0-20151221-NIGHTLY-m8.zip (~47%)
Latest message from my recovery (latest stable CM)
Code:
Finding update package...
I have S-ON, but haven't had any problems flashing updates to cm so far
Any ideas?
I have the same problem on Sony Xperia M. It stops at 47% on cmd terminal, but on the phone it continues however I'm on bootloop now and couldn't get help anywhere.
joaobot said:
I have the same problem on Sony Xperia M. It stops at 47% on cmd terminal, but on the phone it continues however I'm on bootloop now and couldn't get help anywhere.
Click to expand...
Click to collapse
Sideload is very finicky. I've seen it fail and cause a lot of problems, where simply flashing from other means works just fine.
If you have a USB card reader and a MicroSD card, just put the ROM on the MicroSD card, insert into phone, and flash it from there (using custom recovery).
Otherwise, try to adb push the ROM to the phone's storage. Then flash in your custom recovery.
I don't have any specific experience with your phone, so that is probably all I can help.
redpoint73 said:
Sideload is very finicky. I've seen it fail and cause a lot of problems, where simply flashing from other means works just fine.
If you have a USB card reader and a MicroSD card, just put the ROM on the MicroSD card, insert into phone, and flash it from there (using custom recovery).
Otherwise, try to adb push the ROM to the phone's storage. Then flash in your custom recovery.
I don't have any specific experience with your phone, so that is probably all I can help.
Click to expand...
Click to collapse
Just to update, ADB push wouldn't work, ADB devices printout show device connected on sideload mode only.
So I tryed again untill it worked.
Thanks!
Related
Hi all,
I've been googling this for some hours now but haven't found anything i could solve my problem with: I was rooting my mt3gs and after applying the radio update, i probably did something wrong, as now my phone does not recognize the SD card except when it reads ESPRIMG.zip. I'm not able to apply update.zip from sdcard and i realised that /dev/block/mmc* files are not present.
I read that i could try and do
fastboot -c board_sapphire.disable_sdcard=0 boot recovery.img
but i don't have any recovery image.
I also tried mounting /dev/block/mtdblock4 (cache) as the sdcard to see if i could make it read a new update.zip, but the pc does not recognize the phone. In fact, when i plug it to USB adb does not recognize it anymore. I also tried going into fastboot by rebooting the phone to see if i could reflash it from there, but adb doesn't recognize it as well. The strange thing is that when i plug the cable the phone just reboots itself.
Any ideas?
Thank you so much!
Hello. I need your help. I have the LG E980 with 4.4.2. I was trying to set this up as a spare phone but for some reason could not get an email program to work with my companies "Notes Traveler" program. I'm able to achieve syncing with my S4 active though. I oulled the email APK off of the S4 active and that resolved the problem temporarily. I read up and found out that the CM11 ROM would resolve this issue. Anyway, I installed a recovery program and did a nanodroid back up only to realize that my EXT_SD card was not being recognized. Si I did a factory reset now I get a boot error and can only get to the recovery program.
It will not recognize my external SD card and I'm afraid that possibly I corrupted the boot image or recovery? Any suggestions how to get out of this boot? Is there a way I can drag a Update.Zip to the internal SD card and it will completely over write boot and all files?
mikelets456 said:
Hello. I need your help. I have the LG E980 with 4.4.2. I was trying to set this up as a spare phone but for some reason could not get an email program to work with my companies "Notes Traveler" program. I'm able to achieve syncing with my S4 active though. I oulled the email APK off of the S4 active and that resolved the problem temporarily. I read up and found out that the CM11 ROM would resolve this issue. Anyway, I installed a recovery program and did a nanodroid back up only to realize that my EXT_SD card was not being recognized. Si I did a factory reset now I get a boot error and can only get to the recovery program.
It will not recognize my external SD card and I'm afraid that possibly I corrupted the boot image or recovery? Any suggestions how to get out of this boot? Is there a way I can drag a Update.Zip to the internal SD card and it will completely over write boot and all files?
Click to expand...
Click to collapse
This Fix solved my boot only to recovery bug, but if your cwm is not reading your external, you could try sideloading it through adb if your cwm version has that. Copy the fix to your adb folder, connect your phone to pc, select install zip through sideload in the recovery, open adb, type adb sideload fix.zip or if nothing works just use lgflashtool and kdz back to stock.
spirallingspiral said:
This Fix solved my boot only to recovery bug, but if your cwm is not reading your external, you could try sideloading it through adb if your cwm version has that. Copy the fix to your adb folder, connect your phone to pc, select install zip through sideload in the recovery, open adb, type adb sideload fix.zip or if nothing works just use lgflashtool and kdz back to stock.
Click to expand...
Click to collapse
Thanks for your reply. I'm not good at all with ADB would you mind telling me exactly what to type (spacing, etc)? I've tried ADB before and must have been entering the wrong sequence or spacing. On my S4 I simply used ODIN and loaded a Deodexed version.
mikelets456 said:
Thanks for your reply. I'm not good at all with ADB would you mind telling me exactly what to type (spacing, etc)? I've tried ADB before and must have been entering the wrong sequence or spacing. On my S4 I simply used ODIN and loaded a Deodexed version.
Click to expand...
Click to collapse
Click install zip by sideload on cwm, copy the zip i linked before to the your adb folder,. Open Adb, and type "adb devices" to see if your device is detected. If it isnt. click here and download the naked drivers. If your device is detected, type "adb sideload filename.zip" . Just copy the filename and paste it after "adb sideload" in the command prompt, which is "adb sideload Zero_Misc_fix_factory_data_reset_recovery.zip"
spirallingspiral said:
Click install zip by sideload on cwm, copy the zip i linked before to the your adb folder,. Open Adb, and type "adb devices" to see if your device is detected. If it isnt. click here and download the naked drivers. If your device is detected, type "adb sideload filename.zip" . Just copy the filename and paste it after "adb sideload" in the command prompt, which is "adb sideload Zero_Misc_fix_factory_data_reset_recovery.zip"
Click to expand...
Click to collapse
Worked like a charm...thank you very much!
EDIT: however mr SD card is not being shown. When I boot up it says SD card installed, but it's not showing up anywhere. Any suggestions?
mikelets456 said:
Worked like a charm...thank you very much!
EDIT: however mr SD card is not being shown. When I boot up it says SD card installed, but it's not showing up anywhere. Any suggestions?
Click to expand...
Click to collapse
Glad it worked The sd card is not getting detected atall or just recovery? if its just recovery, some recoveries wont see the sd card, you can just flash another recovery to fix that. If its not being detected once it boots up too then i have no clue what the problem is. Try flashing another rom and see if it detects it.
spirallingspiral said:
Glad it worked The sd card is not getting detected atall or just recovery? if its just recovery, some recoveries wont see the sd card, you can just flash another recovery to fix that. If its not being detected once it boots up too then i have no clue what the problem is. Try flashing another rom and see if it detects it.
Click to expand...
Click to collapse
In recovery it shows "external sd card" then when I tried to flash it says " can't mount sd card". Also, I've tried my 64 gb card that's in my samsung and that does not work either. When it boots up it says "sd card inserted".
How do I flash another recovery or go back to stock recovery? I think something is corrupted in recovery because when I did a factory reset again to clear things up I got the boot error and had to do the process all over that you posted.
This is the recovery i always use, its philz touch. You can flash it the same way u flashed the fix, copy the zip to adb folder and sideloading it using adb sideload filename.zip. I cant guarantee that everything will work but if everything goes downhill, you will have to kdz back to stock using the steps from here . If the sd card isnt getting detected after boot too, i really have no idea what the issue is.
spirallingspiral said:
This is the recovery i always use, its philz touch. You can flash it the same way u flashed the fix, copy the zip to adb folder and sideloading it using adb sideload filename.zip. I cant guarantee that everything will work but if everything goes downhill, you will have to kdz back to stock using the steps from here . If the sd card isnt getting detected after boot too, i really have no idea what the issue is.
Click to expand...
Click to collapse
Flashed "TOT" file and all is good. I believe the bootloader is either locked or was corrupted somehow. Thanks again
Hello,
Few days before I was able to install TWRP to my p6. But now i want to revert to stock recovery. But now problem is when I am trying to run the process, the command prompt shows error device not found!
I have installed adb, i have phone drivers installed. Phone is detected on PCHiSuite too.
It even reboots when i put the command: fastboot reboot!
just very confused to think what would be the problem! please help..
thanks!
start the connection with: adb reboot bootloader
blueIBI said:
start the connection with: adb reboot bootloader
Click to expand...
Click to collapse
It doesn't work. Shall put up the screenshots soon! I even tried ADB over wireless just to check if there is some problem with USB drivers. But it says device not found.
is unrooting needed?
My phone was rooted. Do I have to unroot before installing the stock recovery?
I repeated the procedure of installing ADB and fastboot drivers and I then followed the procedure installing the stock recovery!
now the thing is the phone is stuck permanently on huawei logo...?
Please help me out!!!
attempt 2:
when i try to force reboot, it shows failed to update and shows the stock recovery!
it shows an option to install from external memory
and also wipe/factory reset
for the same now I have put a folder dload/update.app in the external memory card.
will a factory reset will help or should I opt to install from external memory??
Current status:
I read somewhere on the same forum to delete the dload folder and create new and paste update.app.
I did that, a little bit of phone charging and then force upgrade. This time it worked!!
It was nice to see my p6 back in life!!
but one problem still exists.
When I go to mobile networks options, a dialog box appears ""unfortunately process com.android.phone has stopped"
Any solution for that??? the sad part is I cannot check the option of "Roaming Data".. I cant use net when roaming coz of that..
sal3011 said:
My phone was rooted. Do I have to unroot before installing the stock recovery?
I repeated the procedure of installing ADB and fastboot drivers and I then followed the procedure installing the stock recovery!
now the thing is the phone is stuck permanently on huawei logo...?
Please help me out!!!
Current status:
when i try to force reboot, it shows failed to update and shows the stock recovery!
it shows an option to install from external memory
and also wipe/factory reset
for the same now I have put a folder dload/update.app in the external memory card.
will a factory reset will help or should I opt to install from external memory??
Click to expand...
Click to collapse
Which cimmand does show up the result 'device not found'? If its adb devices then it shouldnt be stuck on huawei ascend logo because thats bootloader/fasboot mode in which case you should use fastbood commands, like fastboot devices. If that turns up a device with some random numbers/letters then you are good to go for flashing stock recovery.
Sent from my SM-G850F
tileeq said:
Which cimmand does show up the result 'device not found'? If its adb devices then it shouldnt be stuck on huawei ascend logo because thats bootloader/fasboot mode in which case you should use fastbood commands, like fastboot devices. If that turns up a device with some random numbers/letters then you are good to go for flashing stock recovery.
Sent from my SM-G850F
Click to expand...
Click to collapse
Hello,
What you say is right, I just realized this after too much of fiddling with my phone...! but now its enough! not doing anything until a stable international firmware is released!
the command I used was adb reboot bootloader.
Well, later I was able to resolve the issue. Just repeating the procedure (i.e installing adb and fastboot and then following the procedure in cmd prompt helped me flash to stock recovery)
Seeing the stock recovery installed was a relief.
When the USB update didnt work for the first time
>>I deleted the dload folder and created again and then pasted the UPDATE.APP.
>>force update
This worked for me...!
I everyone,
I need your help, I tried to install a new rom (AICP : this one) , and somehow forgot to do a backup.
When I boot I only get the swirling logo, never get to fully load.
The phone is not bricked, I can still access the bootloader / fastboot and my recovery, so I could simply flash another rom... but I can't figure how to get the zip file on the /sdcard.
I can't use adb sideload or push, I have HTC sync and android sdk installed, I have no problem to use fastboot commands, so I guess I don't have any driver problem, but adb devices never shows my phone (Tried while off, booted on bootloader, on fastboot, and on recovery, never shows up when I try adb devices)
On windows I get a driver error when plugging my phone while in recovery, but I don't find how to install it.
So... is there a way to mount the /sdcard/ as an external drive in windows or ubuntu ? Or do you have a workaround for adb ?
Thanks a lot !
Vincent
Hi all,
It seems I come back a n00b every few years.
I rooted my Zenfone 2 to remove some clutter and guess what I did today? I updated. Didn't know that would brick my phone but well here I am.
I followed these steps:
http://www.asus-zenfone.com/2015/06/how-to-update-ota-without-bootloop-on-rooted-zenfone2.html
Only to find that it wouldn't boot.
Went into recovery and tried to factory reset... went on for more than 15 minutes (I didn't want to stop the process....). I then had to hard reset then boot into recovery and tried to wipe cache which yielded nothing...
BTW, I think the failed wipe and reset messed up permissions as fastboot yields an error (even though the "flash recovery" bit seems to work).
I tried installing TWRP and it only boots back into fastboot. Reinstall the recovery from the link above and I can go back into recovery but can't seem to use any of the functions.
Any ideas?
p.s. I did do a few searches. Can't find anything specific about
I also tried using the adb sideload to sideload official firmware but it yields "error: device not found" and then goes back into regular recovery...
adramelch said:
I also tried using the adb sideload to sideload official firmware but it yields "error: device not found" and then goes back into regular recovery...
Click to expand...
Click to collapse
Have you installed all your drivers correctly?
In TWRP, have you gone into advanced and selected ADB Sideload? I've also had issues with sideloading, I think it's a TWRP issue though.
Here's what you can try:
Boot into TWRP and make sure the phone is detected on the PC.
open up adb
type: adb devices
hit enter
your device should be listed
type: adb push -p rom.zip /sdcard0/
-for push, it's just the command to push files to your phone. Alternatively, pull is for taking files from your phone (in the event you can't boot up and need a certain file)
-for -p, it just means show progress, so in CMD you'll see a percentage sign which is always a good thing to know
-for rom.zip you type in the location of the file
-for /sdcard0/ you can leave that, as that is the send destination and should land right in your main folder.
And once the file is transferred over, install through TWRP.
Wipe Dalvik/Cache.
Reboot system.
Profit.
If all this doesn't work, try a microsd card with the file on it.
EDIT: I just realized you meant you meant stock recovery. In that case...it should still allow you to adb sideload, but I'm not sure. As long as you can still use ADB, you can follow my instructions above.
adb push yields "error: closed"
adb sideload says it needs adb 1.0.32 to do operation...
Try using microSD, download the latest firmware on asus website, then rename the zip to MOFD_UPDATE.zip and copy it to your microSD then go to recovery mode and it'll install the update. it took sometime be patient
badaboomBURP said:
Try using microSD, download the latest firmware on asus website, then rename the zip to MOFD_UPDATE.zip and copy it to your microSD then go to recovery mode and it'll install the update. it took sometime be patient
Click to expand...
Click to collapse
Recovery doeasn't have option "Update from zip" but this time, the adb sideload command worked for some reason...
adramelch said:
Recovery doeasn't have option "Update from zip" but this time, the adb sideload command worked for some reason...
Click to expand...
Click to collapse
in my experience, it automatically install the zip if i go to recovery
Update: Sideload worked and I've been back to stock since. Didn't want to flash because I was ok with stock but didn't want the clutter. Will find another stable firmware if need be.
Thanks again for the help!