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 am having a problem with my Kindle Fire and am hoping for some guidance. My fire was running fine . it was rooted and had fff installed. I am using TWRP and a custom ROM. This is what I have:
Android: 4.2.2
CyanogenMOD version: 10.1-20130215-1442-otter-sgt7
Build number: cm_otter-userdebug 4.2.2 JDQ39
TWRP: 2.8.3.0
When booting it says: v1.4a. And press the power button for boot menu. I can go into recovery now, BUT.... If I go to flash a zip file nothing is listed. I have put many .zip files in /sdcard folder, but they are all missing from view in TWRP??
No matter were I put a .zip file I cannot find it in TWRP.
TWRP puts me into /sdcard but there are no files listed now. It must be in some other partition ?? Idk ?? Also when I am booted into the OS it is saying I don't have root but if I run root checker, it says I do.
Bottom line is I want to flash a new ROM but I can not find the zip file of the new ROM while in TWRP. It is also saying I am out of space but I know I am not.
What should I do ? It seems the partitions are may be messed up ? Again idk..... Please help !!!
Need more info??
Hi,
In still having this problem. Does anyone have any thoughts on what I could try ? I don't know much but it seems like it is reading off the wrong partition maybe ? I mean I put the .zips in the folder /sdcard but when I am in twrp the files are not there. Please help me ?
Thibor69 said:
I am having a problem with my Kindle Fire and am hoping for some guidance. My fire was running fine . it was rooted and had fff installed. I am using TWRP and a custom ROM. This is what I have:
Android: 4.2.2
CyanogenMOD version: 10.1-20130215-1442-otter-sgt7
Build number: cm_otter-userdebug 4.2.2 JDQ39
TWRP: 2.8.3.0
When booting it says: v1.4a. And press the power button for boot menu. I can go into recovery now, BUT.... If I go to flash a zip file nothing is listed. I have put many .zip files in /sdcard folder, but they are all missing from view in TWRP??
No matter were I put a .zip file I cannot find it in TWRP.
TWRP puts me into /sdcard but there are no files listed now. It must be in some other partition ?? Idk ?? Also when I am booted into the OS it is saying I don't have root but if I run root checker, it says I do.
Bottom line is I want to flash a new ROM but I can not find the zip file of the new ROM while in TWRP. It is also saying I am out of space but I know I am not.
What should I do ? It seems the partitions are may be messed up ? Again idk..... Please help !!!
Need more info??
Click to expand...
Click to collapse
Thibor69 said:
Hi,
In still having this problem. Does anyone have any thoughts on what I could try ? I don't know much but it seems like it is reading off the wrong partition maybe ? I mean I put the .zips in the folder /sdcard but when I am in twrp the files are not there. Please help me ?
Click to expand...
Click to collapse
Downgrade to twrp 2.7.1.0
[url="http://forum.xda-developers.com/showpost.php?p=54156780&postcount=5]"Flashing Twrp in FFF bootloader with fastboot.exe[/url]
Sent from my XT907 using Tapatalk
I have a Zenfone 2 (ZE551ML) with the latest WW firmware (2.20.40.97) which is obviously causing trouble with my phone. I want to revert back to the older firmware version (2.20.40.90 or even 2.20.40.63).
Is something like that possible on my phone? I've tried every resource that I could find online and nothing seems to work. It's not rooted - it's as is from the shop just with the latest update. I've tried sideloading but that obviously works only when updating firmware not downgrading. I've tried downloading recovery images and using fastboot to flash them but nothing happens.
So I ask again is it possible to downgrade stock firmware and if yes are there reliable tested instructions on how to do it?
Refer to http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596 and follow the steps of root method 1 (pre-rooted image) to flash boot, droidboot and recovery images for the firmware version you want to revert to. However, DON'T download and flash the pre-rooted system image. Instead download the full firmware zip from ASUS, rename it as MOFD_SDUPDATE and place it on your external SD card. Erase your data and then boot back into the bootloader and then recovery mode. It should then install the firmware from your SD card.
kanagawaben said:
Refer to http://forum.xda-developers.com/zenfone2/general/asus-zenfone-2-flashing-recovery-mode-t3096596 and follow the steps of root method 1 (pre-rooted image) to flash boot, droidboot and recovery images for the firmware version you want to revert to. However, DON'T download and flash the pre-rooted system image. Instead download the full firmware zip from ASUS, rename it as MOFD_SDUPDATE and place it on your external SD card. Erase your data and then boot back into the bootloader and then recovery mode. It should then install the firmware from your SD card.
Click to expand...
Click to collapse
Thanks for the info! However I need help with the last part. I have no problem following up to the part about sending fastboot flash commands but what exactly does "Erase your data" mean? After I send the fastboot commands I am still in the bootloader screen. Do I proceed perhaps to the recovery mode to wipe/erase the cache? I am also wondering is it enough to just put the MOFD_SDUPDATE file in the root of the SD card? And do I need an unlocked bootloader to perform all these actions?
I understand that these questions might seem a bit noobish to experienced Android hackers but my experience on that field is limited to just doing one "unofficial" upgrade of my Nexus 4 to Lollipop so I would be grateful for any help.
EDIT: It seems I managed to figure out the correct order of things however when I reboot to bootloader I get the following error.
Code:
E:file path:/sdcard/MOFD_SDUPDATE.zip
E:failed to map file
SD installation aborted.
EDIT 2: It was actually an error on my end. I had my Windows set in a way to display file extensions so I accidentally named the file MOFD_SDUPDATE instead of MOFD_SDUPDATE.zip. Renaming the file did the trick.
I had to make a separate post just to thank you kanagawaben. Thanks! You are a life saver :victory: I've managed to successfully revert my phone to stock 2.20.40.90.
The best part is it resolves an issue with the proximity sensor which was obviously introduced with 2.20.40.97 (http://forum.xda-developers.com/zenfone2/help/proximity-sensor-inconsistently-t3224700/)
SuperSU told me that my SU binary was out of date and so i tried to update it through TWRP like it recommended. Well that ended up failing in the middle of it (I don't have logs) and it seems like the backup I had is missing from my SD card. Whenever I load android it goes black screen, it'll show the back button and the status bar but none of that will be interactive. I can power it down but if i wait too long the buttons won't work. Anyways I was hoping someone had a backup for the a5_chl phone.
end360 said:
SuperSU told me that my SU binary was out of date and so i tried to update it through TWRP like it recommended. Well that ended up failing in the middle of it (I don't have logs) and it seems like the backup I had is missing from my SD card. Whenever I load android it goes black screen, it'll show the back button and the status bar but none of that will be interactive. I can power it down but if i wait too long the buttons won't work. Anyways I was hoping someone had a backup for the a5_chl phone.
Click to expand...
Click to collapse
Sorry your having problems. Why not just get the stock RUU file directly from HTC/downloads and flash back your stock recovery by running the RUU on your computer and before hitting start type %temp% into the search box and go to the RUU's running files and in one of the numbered files will be the rom.zip and within that file will be the recovery image. Copy that to your ADB/fastboot folder then flash it over your TWRP recovery but first I'd wipe the system and data in advanced wipe in TWRP to get your system partition clean( THIS WIPES THE WHOLE PHONE SO BE AWARE OF THAT AND MOVE FILES TO YOUR COMPUTER ACCORDINGLY OR BACK UP USING GOOGLE STOCK BACKUP IN SETTINGS IF YOU'RE NOT ALREADY FOR CONTACTS AND NUMBERS ETC). Then relock your bootloader with the stock recovery flashed back and run the RUU or put it in your ext SD and rename the file to OP9CIMG and reboot into your bootloader and it should automatically pick up the file and start flashing it. I have this same model phone and I keep my stock RUU that I got from HTC on my computer for just such a problem. I got a stock recovery zip from somewhere else but i can't remember where but it's also within the RUU itself. Try to find the link for you in a bit.
EDIT: here's a link to someone I know who had a whole tutorial for the a5_ul version of our phone on how to flash back a stock RUU from your computer or from within your ext SD card. Obviously the links with the files aren't valid for our phone but the steps are . Also has instructions for restoring using a TWRP backup but I wouldn't use someone else's TWRP backup if my hair was on fire. Especially since we have access to the pure stock RUU with our version why not take advantage of it. That's all I'm saying.
http://forum.xda-developers.com/desire-816/help/guide-how-to-flash-stock-recovery-ruu-t3308502
And here's the HTC RUU downloads link below
http://www.htc.com/us/support/rom-downloads.html
And lastly a link to a tutorial on extracting the stock recovery from the RUU .
http://androidforums.com/threads/guide-re-flash-stock-rom-ruu-after-bricking-a-rooted-device.565203/
Well not lastly I guess because here is a link to the stock recovery provided by FoxyDrew. Don't use the RUU link it's to kitkat but the recovery link below it is the same for lollipop as it's for the a5_chl
http://forum.xda-developers.com/desire-816/general/ruu-t2952058/post57019175#post57019175
thoctor said:
Sorry your having problems. Why not just get the stock RUU file directly from HTC/downloads and flash back your stock recovery by running the RUU on your computer and before hitting start type %temp% into the search box and go to the RUU's running files and in one of the numbered files will be the rom.zip and within that file will be the recovery image. Copy that to your ADB/fastboot folder then flash it over your TWRP recovery but first I'd wipe the system and data in advanced wipe in TWRP to get your system partition clean( THIS WIPES THE WHOLE PHONE SO BE AWARE OF THAT AND MOVE FILES TO YOUR COMPUTER ACCORDINGLY OR BACK UP USING GOOGLE STOCK BACKUP IN SETTINGS IF YOU'RE NOT ALREADY FOR CONTACTS AND NUMBERS ETC). Then relock your bootloader with the stock recovery flashed back and run the RUU or put it in your ext SD and rename the file to OP9CIMG and reboot into your bootloader and it should automatically pick up the file and start flashing it. I have this same model phone and I keep my stock RUU that I got from HTC on my computer for just such a problem. I got a stock recovery zip from somewhere else but i can't remember where but it's also within the RUU itself. Try to find the link for you in a bit.
EDIT: here's a link to someone I know who had a whole tutorial for the a5_ul version of our phone on how to flash back a stock RUU from your computer or from within your ext SD card. Obviously the links with the files aren't valid for our phone but the steps are . Also has instructions for restoring using a TWRP backup but I wouldn't use someone else's TWRP backup if my hair was on fire. Especially since we have access to the pure stock RUU with our version why not take advantage of it. That's all I'm saying.
http://forum.xda-developers.com/desire-816/help/guide-how-to-flash-stock-recovery-ruu-t3308502
And here's the HTC RUU downloads link below
http://www.htc.com/us/support/rom-downloads.html
And lastly a link to a tutorial on extracting the stock recovery from the RUU .
http://androidforums.com/threads/guide-re-flash-stock-rom-ruu-after-bricking-a-rooted-device.565203/
Well not lastly I guess because here is a link to the stock recovery provided by FoxyDrew. Don't use the RUU link it's to kitkat but the recovery link below it is the same for lollipop as it's for the a5_chl
http://forum.xda-developers.com/desire-816/general/ruu-t2952058/post57019175#post57019175
Click to expand...
Click to collapse
My thread has the KitKat and Lollipop RUU, which is the latest one from HTC, and should work fine for his issue
FoxyDrew said:
My thread has the KitKat and Lollipop RUU, which is the latest one from HTC, and should work fine for his issue
Click to expand...
Click to collapse
Cool. You're the man.
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.