Related
On the sticky thread there is a link for cwm thread, however I'm not quite sure which filesystem to choose, I'm going to install through recovery, seems safer for me. I want to install cwm for 2 purposes, first I'm planning to backup my stock rom so that I can always flash it back if I need my warranty and second I'm planning to flash cm9 to my phone. I'm not quite sure what is the diffrence between rfs and ext4 is Currently I'm on 2.2.1 stock rom.
Actually I found the proper version of CWM to install here http://forum.xda-developers.com/showthread.php?t=1414173
But I can't apply it, when I enter recovery mode the options I have are:
reboot system now
apply sdcard:update.zip
wipe data/factory reset
wipe chace parition
Pheraps I should rename the zip file I downloaded to update.zip? I can't select any other zip from the sd card and if I press "apply sdcard:update.zip" it searches for update.zip and fails to find it.
Try to install final cwm 5.0.7
* I'm using now cwm 5.0.6
Sent from my GT-S5660 using Tapatalk 2
samgio said:
Try to install final cwm 5.0.7
* I'm using now cwm 5.0.6
Sent from my GT-S5660 using Tapatalk 2
Click to expand...
Click to collapse
But I can't seem to be able to install any cwm through recovery, as I just don't have this option, should I rename the package?
Can anyone help me please? :\
Eden3319 said:
Can anyone help me please? :\
Click to expand...
Click to collapse
''apply update from sdcard''
''apply update.zip''
something like that, and than select the cwm.
U have original recovery??!
If u have it do this steps:
Put the cwm file in (android) folder
1-go to recovery
2-apply update from sd card
3-go to android folder
4-chose the cwm file
5-flash it
6-wait while it finished
7-reboot your phone
I can't help more this is the all steps...it should works
Sent from my GT-S5660 using Tapatalk 2
This is the log I get when I click apply sdcard:update.zip:
-- Install from sdcard...
Finding update package...
Opening update package...
E:Can't open /sdcard/update.zip
(No such file or directory)
Installation aborted.
Because the name of the zip is just not update.zip.
1.first copy the zip to the root of sdcard
rename the zip to update.zip and install as instructed
Press thanks if i helped u
Sent from my GT-S5660 using xda app-developers app
I flashed it but I can't seem to be able to enter to recovery now, power+home buttons just keep me on the samsung logo (not the flashing one, the first one) my phone works but just can't enter to recovery. When I flashed it, it seemed to work, but I don't know why I can't enter
Mates you have to help me!!! I ordered an order to reboot into recovery from rom manager and my device doesn't start now, I know it was stupid but I'm not sure what to do now, I can get it to download mode and to the first samsung logo but not past it
Eden3319 said:
Mates you have to help me!!! I ordered an order to reboot into recovery from rom manager and my device doesn't start now, I know it was stupid but I'm not sure what to do now, I can get it to download mode and to the first samsung logo but not past it
Click to expand...
Click to collapse
First you have to root and format to ext4, before installing CWM.
Download mode, remove battery, insert battery, press power, home, volume down, at the same time.
movfan said:
First you have to root and format to ext4, before installing CWM.
Download mode, remove battery, insert battery, press power, home, volume down, at the same time.
Click to expand...
Click to collapse
I'm still getting into download mode, my problem is that whenever it boots now it trys to get into recovery mode and I don't have recovery mode because applying it didn't work :\ The normal os worked before I clicked that button in rom manager
After installing a rooted app, the app asked to reboot the phone in order to complete the driver installation, then after that the phone wont start up and stuck at the logo....:crying: In a panic I wipe data/factory reset and now I got a messege saying
This phone is LOCK state.
E:failed to mount/sdcard (No such file or directory)
There is no UPDATE.APP in /sdcard/dlead or /data/share/0/dload
Huawei SD card update fail.......
cust copying files....
copy cust file successed
FAIL
Please help
kabatinouguy said:
After installing a rooted app, the app asked to reboot the phone in order to complete the driver installation, then after that the phone wont start up and stuck at the logo....:crying: In a panic I wipe data/factory reset and now I got a messege saying
This phone is LOCK state.
E:failed to mount/sdcard (No such file or directory)
There is no UPDATE.APP in /sdcard/dlead or /data/share/0/dload
Huawei SD card update fail.......
cust copying files....
copy cust file successed
FAIL
Please help
Click to expand...
Click to collapse
looks like you have a soft-brick.
Download a Official-Rom, move the Update into the DLOAD-Folder,
go into the original Recovery and let it flash the file.
After this your phone should be starting normally.
kabatinouguy said:
After installing a rooted app, the app asked to reboot the phone in order to complete the driver installation, then after that the phone wont start up and stuck at the logo....:crying: In a panic I wipe data/factory reset and now I got a messege saying
This phone is LOCK state.
E:failed to mount/sdcard (No such file or directory)
There is no UPDATE.APP in /sdcard/dlead or /data/share/0/dload
Huawei SD card update fail.......
cust copying files....
copy cust file successed
FAIL
Please help
Click to expand...
Click to collapse
which app is that
nARDOs said:
which app is that
Click to expand...
Click to collapse
From what i can remember I think it SUPER USER
kabatinouguy said:
From what i can remember I think it SUPER USER
Click to expand...
Click to collapse
Which rooting methode did u use to root ur phone?
nARDOs said:
Which rooting methode did u use to root ur phone?
Click to expand...
Click to collapse
I use ROOT WIZARD method....
This happened to me yesterday as well, I was about to restore apps using TB but the phone frooze and then anything made it boot. I don't know how Exactly I solved it but all I did was:
1.- Flash TWRP v3.01
2.- Wipe all the phone, including system, data, cust and internal sd
3.- From within TWRP flashed STock boot and recovery for 118CN FW.
4.- Placed 118CN UPDATE.APP in external sd/dload
5.- from within TWRP still, rebooted the phone to recovery.
6.- The phone started to flash the update from external SD.
7.- It succeded to flash files but couldn't mount /sdcard so I repeated steps above once more
8.- from stock recovery wipe/factory reset
9.- Tried the update again and voila! Phone succeded and booted just fine... Now it's been running with no issues since 2 days
I was running 118CN FW and a test kernel with some "non tested" or unstable features which I think forced the phone to frooze and then the data corruption...
kabatinouguy said:
I use ROOT WIZARD method....
Click to expand...
Click to collapse
I used eROOT method with HiSuite.
Has never had issues.
Are u on B118cn ?
nARDOs said:
I used eROOT method with HiSuite.
Has never had issues.
Are u on B118cn ?
Click to expand...
Click to collapse
Oh no Im on old one, B116
kabatinouguy said:
Oh no Im on old one, B116
Click to expand...
Click to collapse
Why not move to B125.
less bugs.
Better battery life and smoother...
raolleel said:
looks like you have a soft-brick.
Download a Official-Rom, move the Update into the DLOAD-Folder,
go into the original Recovery and let it flash the file.
After this your phone should be starting normally.
Click to expand...
Click to collapse
Thanks mate my phone is working again........it took me a long time to figure out how to do flashing and everything because I am a beginner but after doing a lot of reading and watching utube I finally have some basic knowledge on unbricking a phone....Thanks again for your information it really helps me alot....
huawei p6
hi i did the same putting official firmware in d load and installed and i rebooted it wright?
---------- Post added at 11:09 AM ---------- Previous post was at 11:04 AM ----------
hi can anyone help my huawei p6 is stuck to the logo
This phone is LOCK state.
E:failed to mount/sdcard (No such file or directory)
There is no UPDATE.APP in /sdcard/dlead or /data/share/0/dload
Huawei SD card update fail.......
cust copying files....
copy cust file successed
FAIL
Please help
jimbo77 said:
This happened to me yesterday as well, I was about to restore apps using TB but the phone frooze and then anything made it boot. I don't know how Exactly I solved it but all I did was:
1.- Flash TWRP v3.01
2.- Wipe all the phone, including system, data, cust and internal sd
3.- From within TWRP flashed STock boot and recovery for 118CN FW.
4.- Placed 118CN UPDATE.APP in external sd/dload
5.- from within TWRP still, rebooted the phone to recovery.
6.- The phone started to flash the update from external SD.
7.- It succeded to flash files but couldn't mount /sdcard so I repeated steps above once more
8.- from stock recovery wipe/factory reset
9.- Tried the update again and voila! Phone succeded and booted just fine... Now it's been running with no issues since 2 days
I was running 118CN FW and a test kernel with some "non tested" or unstable features which I think forced the phone to frooze and then the data corruption...
Click to expand...
Click to collapse
how did you manage to flash the stock boot.img and recovery inside twrp???
huawei
hi thanks how do you flash with trwp? cause i am not that expert please cant use my phone
thanks
You must do it through adb.
ahhhh..
sry
but i can't even install a rom by using the adb sideload command..it fails because of "file_getprop: failed to stat "/system/build.prop": No such file or directory"
what can i do now?
tried to reload the B510..
should i try with a custom ROM?
blueIBI said:
ahhhh..
sry
but i can't even install a rom by using the adb sideload command..it fails because of "file_getprop: failed to stat "/system/build.prop": No such file or directory"
what can i do now?
tried to reload the B510..
should i try with a custom ROM?
Click to expand...
Click to collapse
Flash through adb stock recovery. Extract your sdcard, create on it dload folder using your PC/Laptop. In dload folder put the update.app of the ROM you want and insert back in the device the sdcard. Press volume up + volume down + power button until the HUAWEI logo appears, after that release all the buttons and the phone will start to update the firmware.
Thanks beyond..
Got it finally again..
But it was very tricky..
Had to usw the b507 by reyncla (thanks for sharing)..
I let this for now in my phone..
I tried the Method you mentioned..but i could not reach the phone by ADB directly (in twrp via ADB sideload it worked finally)..
Thanks for answering..maybe i switch sometime back to the b510 or to the official release (when it comes)..
Sent from my P6-U06 using XDA Free mobile app
blueIBI said:
Thanks beyond..
Got it finally again..
But it was very tricky..
Had to usw the b507 by reyncla (thanks for sharing)..
I let this for now in my phone..
I tried the Method you mentioned..but i could not reach the phone by ADB directly (in twrp via ADB sideload it worked finally)..
Thanks for answering..maybe i switch sometime back to the b510 or to the official release (when it comes)..
Sent from my P6-U06 using XDA Free mobile app
Click to expand...
Click to collapse
Great. Enjoy.
Hi,
Probably after select something wrong in TouchRecoveryInstaller-v1_01 i cant start my phone any more.
- PC don't recognize usb via cable
- sd card not detected (apply update from external storage) appears ../ (E:failed to mount /sdcard (No such file of directory).
- wipe data/factory rese - does not help.
- reboot system now - blocks on logo HUAWEI Ascend
Each expert suggestion and idea is welcome and thank you.
Hello,
I'm looking for help as I have exhausted all of my search on google and xda developers and the answer doesn't seem to be there. I'm afraid I might be unable to get out of this one.
I have a huawei ascend P6-U06 I bought it and it came with the international firmware, I had rooted it and flashed miui v5 into my phone, everything was fine but one thing, I was unable to use themer, so about 3 days ago I finally decided to flash omni rom.
I downloaded omni rom and installed CWM recovery and once into the system I selected the zip from my sd card and flashed it, only to find that the phone would not go pass the first screen (stuck in boot and could not be shutdown or anything)
Since I did not do a TWRP recovery (and I don't know how, I'm just a beginner) I was unable to do anything other than the "3 button method" so I looked and found that I could put the UPDATE.APP file on the dload folder and it should work, so I tried it and the UPDATE.APP firmware version is the B125, all good I think this was the Chinese version but it had English and other languages as well, but Chinese seemed to be the main one.
Anyways I had the phone back and it did an update, after the update everything was working fine, I deleted the dload file from the sd card, also I saw that the "system" or the phone itself created a dload file on the internal storage but then once I had themer on the phone I saw myself that I hated the emotion ui and in the first place that was the reason I had put miui into my phone, I still wanted to try omni rom and persistently I tried a second time.
Now this time since I already new that I could just do the dload thingy I thought (what could happen) so I tried again with CWM to flash the omni rom (the latest version) but it gave me an error saying something like the installation was aborted or something like that.
So I went back to having the phone stuck in boot, I put the B125 UPDATE.APP and created a dload folder on the sd card, but when doing the "3 button method" the system gave me an error, I tried downloading the B122 and the B132 and also the B510 but although I have put the UPDATE.APP on the dload folder it just doesn't do it's magic like it previously did.
Now I don't really have money to buy another phone, if I did I would just buy another one (I like the p7) but I don't so I need to fix this issue otherwise I don't have a phone.
Please help me, I'd appreciate if you can do your best explaining as I'm dumb in this matter, (just a beginner as said before) Also I'm attaching a picture of the error message being received when entering the system recovery through the "3 button method"
Thanks for all of your time, I DO appreciate your help and if you have any questions please just ask! I really need to fix this!
DanRioja said:
Hello,
I'm looking for help as I have exhausted all of my search on google and xda developers and the answer doesn't seem to be there. I'm afraid I might be unable to get out of this one.
I have a huawei ascend P6-U06 I bought it and it came with the international firmware, I had rooted it and flashed miui v5 into my phone, everything was fine but one thing, I was unable to use themer, so about 3 days ago I finally decided to flash omni rom.
I downloaded omni rom and installed CWM recovery and once into the system I selected the zip from my sd card and flashed it, only to find that the phone would not go pass the first screen (stuck in boot and could not be shutdown or anything)
Since I did not do a TWRP recovery (and I don't know how, I'm just a beginner) I was unable to do anything other than the "3 button method" so I looked and found that I could put the UPDATE.APP file on the dload folder and it should work, so I tried it and the UPDATE.APP firmware version is the B125, all good I think this was the Chinese version but it had English and other languages as well, but Chinese seemed to be the main one.
Anyways I had the phone back and it did an update, after the update everything was working fine, I deleted the dload file from the sd card, also I saw that the "system" or the phone itself created a dload file on the internal storage but then once I had themer on the phone I saw myself that I hated the emotion ui and in the first place that was the reason I had put miui into my phone, I still wanted to try omni rom and persistently I tried a second time.
Now this time since I already new that I could just do the dload thingy I thought (what could happen) so I tried again with CWM to flash the omni rom (the latest version) but it gave me an error saying something like the installation was aborted or something like that.
So I went back to having the phone stuck in boot, I put the B125 UPDATE.APP and created a dload folder on the sd card, but when doing the "3 button method" the system gave me an error, I tried downloading the B122 and the B132 and also the B510 but although I have put the UPDATE.APP on the dload folder it just doesn't do it's magic like it previously did.
Now I don't really have money to buy another phone, if I did I would just buy another one (I like the p7) but I don't so I need to fix this issue otherwise I don't have a phone.
Please help me, I'd appreciate if you can do your best explaining as I'm dumb in this matter, (just a beginner as said before) Also I'm attaching a picture of the error message being received when entering the system recovery through the "3 button method"
Thanks for all of your time, I DO appreciate your help and if you have any questions please just ask! I really need to fix this!
Click to expand...
Click to collapse
So first of all DON'T ever use CWM on our phone because its not really good to use! Always use TWRP.
Than second when you want to install a KK ROM like OMNI you have to update first via update.app to a KK firmware, then install TWRP and so on. This is all described in the first post in the OMNI thread.
Third and this is your problem now you have an modified build.prop in your ROM so the recovery will not update you have to push an stock unmodified build.prop via fastboot, that's the only method I think. How to push that with fastboot there you will find something on google.
Good luck
try this
DanRioja said:
Hello,
I'm looking for help as I have exhausted all of my search on google and xda developers and the answer doesn't seem to be there. I'm afraid I might be unable to get out of this one.
I have a huawei ascend P6-U06 I bought it and it came with the international firmware, I had rooted it and flashed miui v5 into my phone, everything was fine but one thing, I was unable to use themer, so about 3 days ago I finally decided to flash omni rom.
I downloaded omni rom and installed CWM recovery and once into the system I selected the zip from my sd card and flashed it, only to find that the phone would not go pass the first screen (stuck in boot and could not be shutdown or anything)
Since I did not do a TWRP recovery (and I don't know how, I'm just a beginner) I was unable to do anything other than the "3 button method" so I looked and found that I could put the UPDATE.APP file on the dload folder and it should work, so I tried it and the UPDATE.APP firmware version is the B125, all good I think this was the Chinese version but it had English and other languages as well, but Chinese seemed to be the main one.
Anyways I had the phone back and it did an update, after the update everything was working fine, I deleted the dload file from the sd card, also I saw that the "system" or the phone itself created a dload file on the internal storage but then once I had themer on the phone I saw myself that I hated the emotion ui and in the first place that was the reason I had put miui into my phone, I still wanted to try omni rom and persistently I tried a second time.
Now this time since I already new that I could just do the dload thingy I thought (what could happen) so I tried again with CWM to flash the omni rom (the latest version) but it gave me an error saying something like the installation was aborted or something like that.
So I went back to having the phone stuck in boot, I put the B125 UPDATE.APP and created a dload folder on the sd card, but when doing the "3 button method" the system gave me an error, I tried downloading the B122 and the B132 and also the B510 but although I have put the UPDATE.APP on the dload folder it just doesn't do it's magic like it previously did.
Now I don't really have money to buy another phone, if I did I would just buy another one (I like the p7) but I don't so I need to fix this issue otherwise I don't have a phone.
Please help me, I'd appreciate if you can do your best explaining as I'm dumb in this matter, (just a beginner as said before) Also I'm attaching a picture of the error message being received when entering the system recovery through the "3 button method"
Thanks for all of your time, I DO appreciate your help and if you have any questions please just ask! I really need to fix this!
Click to expand...
Click to collapse
hi there. try to boot with adb shell in fastboot mode.
if you have b111,125,132,118 etc you need twrp for jelly bean.
after that install twrp recovery and wipe system, data, cache, dalvik.
then reinstall stock recovery also via fastboot and then you can install update.app from dload.
if you want omni you have to update to official b510 because it repartitions your device, then flash omni via twrp.
don't use cwm again
adipaval said:
hi there. try to boot with adb shell in fastboot mode.
if you have b111,125,132,118 etc you need twrp for jelly bean.
after that install twrp recovery and wipe system, data, cache, dalvik.
then reinstall stock recovery also via fastboot and then you can install update.app from dload.
if you want omni you have to update to official b510 because it repartitions your device, then flash omni via twrp.
don't use cwm again
Click to expand...
Click to collapse
Hey thank you for the quick response, could you send me a link with the steps? as I said before I'm really just a beginner so I don't understand much, I mean I don't know what adb shell is, and how to enter the fastboot mode. I'd appreciate if you could help me with that!
Thanks
try this
sorry for the late response, i've been very busy.
you must have hisuite installed because you need the drivers.
so first you have to put your phone in download mode. you do this by starting your phone with vol down pressed. (it will remain on the ascend logo) and in windows you should see a quick removable device.
you need twrp recovery for jelly bean from here (the twrp2.6.x.x. IMG file ) http://forum.xda-developers.com/showthread.php?t=2534420
put the downloaded twrp2.6.3.3.img file in the folder which you'll extract from the attached zip of this post
in the fastboot folder shif+right click - start command windows here
type adb reboot bootloader - it will start the service then display error device not founde
type fastboot flash recovery "and the nameof the recovery ex. twrp2.6.3.3.img" - it should sai ok
safely remove device from windows and reboot your phone.
then you should be able to boot in twrp and clear system, data, cache, dalvik cache. this will let your phone without an operating system so either you install a custom jelly bean or put via twrp the stock recovery back (you cand find on the same page linked above) and then install stock jelly bean via dload folder.
P.S. from what I see in your screenshot, did you put an update.zip in hwouc folder on sdcard? hwouc is the folder where phone saves updates downloaded via ota then installs them from recovery.
are you sure you put update.APP in dload folder?
hope I helped
adipaval said:
sorry for the late response, i've been very busy.
you must have hisuite installed because you need the drivers.
so first you have to put your phone in download mode. you do this by starting your phone with vol down pressed. (it will remain on the ascend logo) and in windows you should see a quick removable device.
you need twrp recovery for jelly bean from here (the twrp2.6.x.x. IMG file ) http://forum.xda-developers.com/showthread.php?t=2534420
put the downloaded twrp2.6.3.3.img file in the folder which you'll extract from the attached zip of this post
in the fastboot folder shif+right click - start command windows here
type adb reboot bootloader - it will start the service then display error device not founde
type fastboot flash recovery "and the nameof the recovery ex. twrp2.6.3.3.img" - it should sai ok
safely remove device from windows and reboot your phone.
then you should be able to boot in twrp and clear system, data, cache, dalvik cache. this will let your phone without an operating system so either you install a custom jelly bean or put via twrp the stock recovery back (you cand find on the same page linked above) and then install stock jelly bean via dload folder.
P.S. from what I see in your screenshot, did you put an update.zip in hwouc folder on sdcard? hwouc is the folder where phone saves updates downloaded via ota then installs them from recovery.
are you sure you put update.APP in dload folder?
hope I helped
Click to expand...
Click to collapse
Hey, I was trying to follow the instructions, but somehow this is not working, I mean the hisuite is stock searching the drivers and once I type adb reboot bootloader it just says not found. but doesn't do anything.
As for the screenshot I found it online, it's the closest thing to the error presented, but I did put the UPDATE.APP on the dload folder
The error I get first it gives me some sort of error which disappears once the Android system recovery menu comes up. then the only thing I'm able to see says:
Checking Module MD5RSA.. OK
Checking Module CRC.... OK
Checking Module CURVER.... OK
Checking Module VERLIST....
Huawei SD card update fail.....
cust copying files...
copy cust files successed!
===================
FAIL
===================
EDIT: I'm updating the actual picture of the error received.
Not found as in command not found or what? Post print screen please
Sent from my HUAWEI P6-U06 using XDA Free mobile app
adipaval said:
Not found as in command not found or what? Post print screen please
Sent from my HUAWEI P6-U06 using XDA Free mobile app
Click to expand...
Click to collapse
Here's the screenshot!
Did you see that you wrote abd instead of adb?
Sent from my HUAWEI P6-U06 using XDA Free mobile app
adipaval said:
Did you see that you wrote abd instead of adb?
Sent from my HUAWEI P6-U06 using XDA Free mobile app
Click to expand...
Click to collapse
My bad, although with adb is still not working lol.
mine is working
DanRioja said:
My bad, although with adb is still not working lol.
Click to expand...
Click to collapse
i downloaded zip from before to be sure.
i see in my console that it runs as administrator, i think that's the reason why yours is not working.
adipaval said:
i downloaded zip from before to be sure.
i see in my console that it runs as administrator, i think that's the reason why yours is not working.
Click to expand...
Click to collapse
I have a question, could it have something to do with the drivers not being installed? I mean I installed the hi-suite but it never installed the drivers, so I'm wondering if that could be the reason, or could it be due to the phone not booting and not having TWRP?
DanRioja said:
I have a question, could it have something to do with the drivers not being installed? I mean I installed the hi-suite but it never installed the drivers, so I'm wondering if that could be the reason, or could it be due to the phone not booting and not having TWRP?
Click to expand...
Click to collapse
EDIT: I'm uploading the picture, I tried with administrator, still not working.
If it says device not found it means adb started but cannot find device.
It is ok because in download mode you cannot enable usb debugging so that adb sees it but if you type to flash the twrp.img it should work. At least on mine it did
Be sure you started phone in download mode by powering it on with vol down pressed. Press it longer just to be sure
Sent from my HUAWEI P6-U06 using XDA Free mobile app
adipaval said:
If it says device not found it means adb started but cannot find device.
It is ok because in download mode you cannot enable usb debugging so that adb sees it but if you type to flash the twrp.img it should work. At least on mine it did
Be sure you started phone in download mode by powering it on with vol down pressed. Press it longer just to be sure
Sent from my HUAWEI P6-U06 using XDA Free mobile app
Click to expand...
Click to collapse
Hmm it's weird, I tried to skip the first step " adb reboot bootloader" and went to the second step, this is what I got (check the picture)
.img
DanRioja said:
Hmm it's weird, I tried to skip the first step " adb reboot bootloader" and went to the second step, this is what I got (check the picture)
Click to expand...
Click to collapse
that's because you did not write .img
fastboot flash recovery twrp_2_6_3_3_recovery.img
DanRioja said:
Hmm it's weird, I tried to skip the first step " adb reboot bootloader" and went to the second step, this is what I got (check the picture)
Click to expand...
Click to collapse
Hello !
Please follow this steps from here !
Because adb not working, you can put your device in bootloader mode manually : press and keep at the same time for about 10~15 sec. power button and volume down , now your device are in bootloader mode and you can use "fastboot" command to flash stock/twrp recovery !
If your device was on Android JB you must use stock/twrp forAndroid JB, else if your device was on Android KitKat you must use stock/twrp for Android KitKat .
The next time when you want to flash something in your device please do your research more - because here on XDA you have almost all the answers to every question - sure, you need to spend some time to read - and not ultimately you can ask , if you are not 100% sure what to do
Good luck !
surdu_petru said:
Hello !
Please follow this steps from here !
Because adb not working, you can put your device in bootloader mode manually : press and keep at the same time for about 10~15 sec. power button and volume down , now your device are in bootloader mode and you can use "fastboot" command to flash stock/twrp recovery !
If your device was on Android JB you must use stock/twrp forAndroid JB, else if your device was on Android KitKat you must use stock/twrp for Android KitKat .
The next time when you want to flash something in your device please do your research more - because here on XDA you have almost all the answers to every question - sure, you need to spend some time to read - and not ultimately you can ask , if you are not 100% sure what to do
Good luck !
Click to expand...
Click to collapse
I'm going to give it a try. thanks!
I have an issue that I cannot for the life of me fix. Last night my wife’s phone received the OTA update and her phone would not restart after that. Total B.S. move on ASUS’s part not to pull that update knowing the issues people were having. But anyways, here’s the rundown. I can boot into bootloader mode but I cannot get into stock recovery. I can, through a certain method get into CWM recovery and I can see the external SD, but I get errors when I try to flash an update or another entire OS. I’ve tried to bypass signature verification also and still cannot get anything to install. ADB will not sideload because it does not find my device, but the method of getting into CWM recovery is done through ADB so I’m confused there. Never have I had such a tough time restoring a bricked device. Samsung, no problem. Huawei, no problem. This POS I’m about ready to throw in the pool and call it a day. Does anyone have any suggestions?
Try flashing CN version and dont forget to disable zip signature and format everything before flashing
Sent from my ASUS_Z00AD using Tapatalk
LiRi2000 said:
Try flashing CN version and dont forget to disable zip signature and format everything before flashing
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
The only way I can flash is through the CMW recovery and everything I try to flash says cant install this package over newer build. But there's nothing on the device as far as I can tell. Also says E: Error in /external_sd status 7
MikeyLee said:
The only way I can flash is through the CMW recovery and everything I try to flash says cant install this package over newer build. But there's nothing on the device as far as I can tell. Also says E: Error in /external_sd status 7
Click to expand...
Click to collapse
Open ROM archive with app (for example WinRAR),
navigate to META-INF\com\google\android
unpack updater-script
open unpacked updater-script with any text editor (I use Notepad++)
remove first line with "(!less_than_int..."
save file
put unpacked file back in archive overwriting it
put rom package on sdcard
flash it via recovery
btw, Updating IFWI takes a 10 or more minutes so wait and don't panic
I'll try that when I get home
MikeyLee said:
The only way I can flash is through the CMW recovery and everything I try to flash says cant install this package over newer build. But there's nothing on the device as far as I can tell. Also says E: Error in /external_sd status 7
Click to expand...
Click to collapse
Try and install twrp recovery through adb you can find how in the forum....if you can install it it will be much easier to flash a room.
Sent from my ASUS_Z00AD using Tapatalk
LiRi2000 said:
Try and install twrp recovery through adb you can find how in the forum....if you can install it it will be much easier to flash a room.
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
Nothing will flash through adb
meciu99 said:
Open ROM archive with app (for example WinRAR),
navigate to META-INF\com\google\android
unpack updater-script
open unpacked updater-script with any text editor (I use Notepad++)
remove first line with "(!less_than_int..."
save file
put unpacked file back in archive overwriting it
put rom package on sdcard
flash it via recovery
btw, Updating IFWI takes a 10 or more minutes so wait and don't panic
Click to expand...
Click to collapse
Still doesnt work. E: error in external sd blah blah blah, same as everything else.
@MikeyLee I had the same problem this morning, i spent a lot of time to fix this, i couldn't access the recovery, i tried to flash thetered recovery and do factory reset, flash again the rom, but nothing.
To fix the bootloop i just rebooted in fastboot mode, launced the adb from pc and format cache partition, thats all.
And the strange thing is that i didn't loose the data, Although I did the factory reset, that's mean maybe a corrupted cache partition that maked impossible to flash anything or do factory reset.
Sent from my ASUS_Z00AD using Tapatalk
Hank87 said:
@MikeyLee I had the same problem this morning, i spent a lot of time to fix this, i couldn't access the recovery, i tried to flash thetered recovery and do factory reset, flash again the rom, but nothing.
To fix the bootloop i just rebooted in fastboot mode, launced the adb from pc and format cache partition, thats all.
And the strange thing is that i didn't loose the data, Although I did the factory reset, that's mean maybe a corrupted cache partition that maked impossible to flash anything or do factory reset.
Sent from my ASUS_Z00AD using Tapatalk
Click to expand...
Click to collapse
I've wiped cache multiple times. What steps did you go through?
Use the adb fastboot, command "fastboot erase cache"
Sent from my ASUS_Z00AD using Tapatalk
You need the stock recovery as the same version of the firmware you're sideloading, flash the recovery through fastboot.
I was finally able to restore everything. Stock recovery, OS etc… Here’s what I did.
Using ADB and following the procedures here http://forum.xda-developers.com/zenfone2/help/how-to-upgrade-cn-version-to-ww-t3101556 and using fastboot, flashed the recovery.img, boot.img and droidboot.img in that order. That gave me stock recovery back. Then I sideloaded with ADB the latest FULL firmware from here https://www.asus.com/support/Download/39/1/0/13/Lk0Sg1Ulh0Ph49Hl/32/
It was the only version that did not error out in some form or another. Everything is back to normal.
Hello everyone!
My oneplus3 is actually running no OS and I'm having a boot loop.
I will try to explain what happened to me with the most details I can.
Before I ****ed everything up, I think I was running OxygenOS 3.28, not really sure about it but im 100% sure it was below 4.0, and it was rooted with TWRP 3.0.2 installed.
1) Today I had a pop up saying OxygenOS 4.0.2 was available (the official one that pops on the screen on boot) "Yay so coooool Nougat!"
1.1) I downloaded it, 1.4Go, then I pressed install
1.2) TWRP showed up, I didn't know what to do and that's where I ****ed up, I set my phone "factory new" in TWRP.
1.3) Phone restarted fresh new, I thought I had 4.0.2 but naaaaah would've been too easy so the official pop up showed again, I was still 3.28 I think.
1.4) Downloaded it once more, TWRP opened again, this time i was looking for the update i just downloaded in the "install" section. I browsed for quite a while and couldn't find it.
1.5) Master ****-up here: I tried to restore a backup. Then the bootloop happened. The black screen with "Oneplus" written in white. I was able to go back in TWRP by pressing power + volume down
1.6) Tried every kind of restore unsuccessfully, and tried ADB but it wouldn't load. Also TWRP said that I was running no OS when I wanted to turn off my phone for example.
2) I downloaded 4.0.2 from one plus website on my mac, and i flashed the official recovery instead of TWRP.
2.1) Transferred the update from my mac to my PC (seems important to me) and installed ADB & everything on both PC/O+3.
2.2) so adb worked in forceboot, i've been able to flash official recovery, tried once more to wipe & everything, but clearly I have no OS now, as TWRP said.
2.3) so i had the update in a folder (not a zip, probably due to the download being done from a mac), I made it a .ZIP with winrar, but "adb sideload update.zip" crashed at 0% everytime
2.4) looked at the archive then i noticed it was first a folder "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883" then inside it i had the content like "boot.img" & everything. So i zipped it again but without that first folder because I thought it was the problem, but it kept on crashing 0%.
2.5) restarted my PC, looked on several forums, but i couldn't find any fix. Now adb can't even open update.zip anymore, it fails even before 0%.. I tried naming it .zip.zip, keeping the name "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip", using a third party app to allow more RAM to the cmd app...
I've been trying hard for 4 hours but I still have a O+3 without any OS... My last idea is downloading "OnePlus3Oxygen_16_OTA_039_all_1701140133_03b794d8a8b44883.zip" from my PC so it downloads it directly .zip unlike on my mac...
I hope I said everything, sorry for the long post but i'm desperate.. thanks for your attention,
Valentin
Try this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
Let me know if it works.
EDIT: See FAQ #1, 2, 4, 12, 14 and 17.
dbabaev21 said:
Try this guide: https://forum.xda-developers.com/oneplus-3/how-to/guide-flashing-oos-v4-0-1-custom-rom-t3537757
Let me know if it works.
EDIT: See FAQ #1, 2, 4, 12, 14 and 17.
Click to expand...
Click to collapse
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Try to install the new official TWRP version i think it is 3.0.3-0 through fastboot. Boot up TWRP, wipe every partiton and copy the update.zip onto the phone. You can copy it by connecting it normaly via USB(like you would do in OOS) and install the zip file afterwards.
Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
install stock recovery and then try installing official OS. Or install modded twrp 3.0.2-1.28 and then try installing Freedom OS 2.3 via sideload or through internal storage.
Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
Stop fiddling with the ROM. Download the ROM afresh directly to your Windows PC/laptop. Check the md5. Then start experimenting with the other suggestions but don't again meddle with the ROM!
Sleazy_ said:
Thank you for answering! unfortunately i've already tried that and my problem occurs when i try to sideload the update from adb recovery... "couldn't load 'update.zip'"
I dont really know what to do now because I think my only option here is to load the OS through adb as I can't boot my phone to get the update zip inside a specified folder to load it from internal storage.
Click to expand...
Click to collapse
I read your post again and here are a few things:
* Don't update Stock OOS via "System updates" in Settings if you are rooted and have TWRP
* Back up your data before updating, wiping or doing something with your phone.
* For the ADB error, see the FAQ #17 in the guide I provided.
Now, try this:
Flash TWRP via fastboot > boot to TWRP > connect your phone to your PC and copy the full Stock OOS v4.0.2 OTA to your phone > reboot to fastboot and flash Stock Recovery.
It didn't touch the internal storage. So, try to install from internal storage when you are in Stock Recovery.
Let me know if it worked.