Related
followed a tutorial (Cnncted's youtube clip - How to root the ASUS ZenFone 2 ) to root
Accidentally (very stupid) pressed the update option when an OTA update showed up yesterday (Jul 8 2015), and after that the phone won't start properly - stopped at in search of incredible...
No luck with trying to boot into recovery mode (power + volume up). It just vibrates once and the screen is black. Trying to flash recovery image with ADB and flashtool etc, but the MTP usb connection failed. If I connect it to the PC using the USB cable and then press the power button to turn it on (stuck in that ..."incredible" screen), device manager shows the Z200AD name with a yellow exclamation mark beside, and Asus ZenUI software will automatically start. But it's not really recognized by the PC.
So...if you have any suggestions for me to try, please let me know and that would be greatly appreciated!
Harry
p.s. This is a US version, so the it's the WW sku?
Same problem here. I have a rooted 551ML and on July 6th I received an OTA update. I installed it and I'm stuck in boot loop. I have hundreds of family pictures in the internal memory.
The good news is that I have access to boot loader and recovery.
I could not find any custom recovery for Zenfone 2. They are not out yet, right? Is there any way to copy the internal memory of the phone (that doesnt load the OS) to the SD card? Or to paste a file img.boot taken from a downloaded official rom and copy it over the corrupted one on the phone's memory?
If you can access the bootloader, you can do this:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
Btw, there is a custom recovery out there (TWRP, check the Development section), but you will need an unlocked bootloader to use it in your state (I think).
US version is the WW SKU btw. Hope this helps.
joel.maxuel said:
If you can access the bootloader, you can do this:
http://forum.xda-developers.com/zenfone2/general/guide-to-apply-ota-bootloop-rooted-zf2-t3127835
Btw, there is a custom recovery out there (TWRP, check the Development section), but you will need an unlocked bootloader to use it in your state (I think).
US version is the WW SKU btw. Hope this helps.
Click to expand...
Click to collapse
Joel, thanks a lot! I will give it a try.
fingers and toes crossed...
I faced this problem too. All I did was to flash the boot.img of my version using fastboot,
Then I flashed the firmware, without factory reset I started the phone.
I was continiously getting an error "com.android.process has stopped". Ignoring that, I just backed up my whole data. Did a factory reset. Updated
Boom!! Everything was normal... I hope this helps
Just a quick update - followed the method in the link that Joel referred to, and everything worked beautifully. I did get two error messages like “the contact stopped working..." “The process android.process.acore has stopped working.” I fixed this problem by clearing the data/cache from the "contact" app, and that did the trick without a factory reset etc.
I unrooted the device using SuperSU. The fastboot screen, however, still shows a random serial number 0123456789ABCDEF. Is there a way to revert it back to the real one? I do see the real one from settings - about - status.
xxmmx said:
Joel, thanks a lot! I will give it a try.
fingers and toes crossed...
Click to expand...
Click to collapse
xxmmx said:
Just a quick update - followed the method in the link that Joel referred to, and everything worked beautifully. I did get two error messages like “the contact stopped working..." “The process android.process.acore has stopped working.” I fixed this problem by clearing the data/cache from the "contact" app, and that did the trick without a factory reset etc.
I unrooted the device using SuperSU. The fastboot screen, however, still shows a random serial number 0123456789ABCDEF. Is there a way to revert it back to the real one? I do see the real one from settings - about - status.
Click to expand...
Click to collapse
Isn't everyone serial number the same? mine is.
This is something that I am not sure of. Yours has been rooted as well?
I would like to know what the fastboot screen looks like before rooting.
GGL-Daz said:
Isn't everyone serial number the same? mine is.
Click to expand...
Click to collapse
xxmmx said:
This is something that I am not sure of. Yours has been rooted as well?
I would like to know what the fastboot screen looks like before rooting.
Click to expand...
Click to collapse
Pretty sure rooting didn't affect my fastboot screen at all.
actually i rooted my zenfone 2 and there was an OTA and i tried to install it without un-rooting my phone. the phone would not turn on and it gets stuck in the boot animation.
the phone wasn't detected by the ADB in my pc so i thought of installing some custom recovery, thought that could help.
i tried installing TWRP but i did not unlock the bootloader and now i am not able to enter in recovery mode either, everytime i try to get in the recovery modethe phone restarts and goes to fastboot mode.
please help.
dip_anker said:
actually i rooted my zenfone 2 and there was an OTA and i tried to install it without un-rooting my phone. the phone would not turn on and it gets stuck in the boot animation.
the phone wasn't detected by the ADB in my pc so i thought of installing some custom recovery, thought that could help.
i tried installing TWRP but i did not unlock the bootloader and now i am not able to enter in recovery mode either, everytime i try to get in the recovery modethe phone restarts and goes to fastboot mode.
please help.
Click to expand...
Click to collapse
I was having a similar issue where adb wouldn't recognize my phone but fastboot was detecting it. What I ended up doing was grabbing the latest stock firmware zip from asus, transferring it to my external sd card via adapter and renamed it to MOFD_SDUPDATE.zip. Then go into fastboot (restart with volume up key) and proceed to recovery. It should automatically update your system from there. The only bummer is having to re-configure everything.
5ifty1 said:
I was having a similar issue where adb wouldn't recognize my phone but fastboot was detecting it. What I ended up doing was grabbing the latest stock firmware zip from asus, transferring it to my external sd card via adapter and renamed it to MOFD_SDUPDATE.zip. Then go into fastboot (restart with volume up key) and proceed to recovery. It should automatically update your system from there. The only bummer is having to re-configure everything.
Click to expand...
Click to collapse
i tried it with prerooted as well as the stock rom, it did not work for me. isn't there any way to flash CM12.1 using the fastboot ?
I have no idea how to root or anything like that, I bought this oneplus 3 and had a update a week later.. so when I did the software update it took me into teamwin recovery mode and now I don't know how to get back into my phone please help....
Did you buy the phone second hand or did you try to flash TWRP yourself? It shouldn't have TWRP installed by default.
Regardless, you can use TWRP to flash the latest update.
Given that you have TWRP, I'm assuming that you have an unlocked bootloader. Did you notice a warning pop up everytime you reboot your phone before? It should say something along the lines of "your device has been unlocked and can't be trusted". If not, you'll have to unlock it (it wipes your phone in the process).
If the bootloader is unlocked, you can simply download and flash the latest zip for OOS 4.0.3 in TWRP. This will update you phone and replace TWRP with the stock recovery (so you don't run into this problem again in the future when installing an OTA). If you don't intend to modify your phone in any way, then this is all you need to do, your phone should be functional.
There are plenty of threads with detailed guides on how to do all of this.
I'm also stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off.
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditiontally'
- Another zip flashes, but gets stuck at the end, no reboot option (manually but that's not the way)
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please
sndr1384 said:
I'm also stuck on TWRP after stupidly downloading the latest OTA and I don't know what to do!
Phone won't boot normal, just goes off.
Situation:
- Bootloader, Fastboot and TWRP wil load.
- Device seen by windows
- Zip install in TWRP gets stuck at 'patching zip unconditiontally'
- Another zip flashes, but gets stuck at the end, no reboot option (manually but that's not the way)
Can someone please point me in the right direction? I don't care if I lose data, just want my phone back!
not helping:
Saying i'm a dipsh-t I know, I know, I will do better in the future, for now, help a brother out please
Click to expand...
Click to collapse
Simple, check the OnePlus D/L sites for this one http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img and flash it by TWRP or fastboot to RECOVERY. Boot once with the official Recovery and all ist fine again.
This is issue of using a faulty twrp so for that when ur phone us booting up go to fastboot and flash twrp 3.0.4-1 and everything will work
emuandco said:
Simple, check the OnePlus D/L sites for this one http://oxygenos.oneplus.net.s3.amazonaws.com/recovery_op3.img and flash it by TWRP or fastboot to RECOVERY. Boot once with the official Recovery and all ist fine again.
Click to expand...
Click to collapse
Similar Problem here:
just wanted to flash latest OOS 4.0.3, so I flashed back stock recovery with flashify and rebooted into recovery mode to flash the already downloaded OOS 4.0.3. zip. That's when it began to go poop! After rebooting it just went dark with no Chance to power it on again! No dice with power button, Volume up/down + power button, nothing! Not even the LED's are blinking when plugged in. So this one seems to be basically dead!
I got it once booting again after randomly pushing the buttons (after x minutes!?), but everytime I reboot the phone it just shuts off without beeing able to power it on again. At the Moment it's dead!
Any ideas what might happened? If I get it on again, should I immediately reset it to factory Settings?
I am kinda lost here! Any help/ideas would be much appreciated!
Flashify? Never used it and never trusted apps which flash stuff on a running system. Use fastboot and reflash the recovery partition. Link to recovery is in my former post.
fastboot flash recovery PATHTOIMGFILE
Thank you for your advice! Still a lot to learn! Got it up again, will try as you suggested!
It appeared that my stock recovery file was corrupted , but all is fine again! Thank you very much!
Mannycolon85 said:
I have no idea how to root or anything like that, I bought this oneplus 3 and had a update a week later.. so when I did the software update it took me into teamwin recovery mode and now I don't know how to get back into my phone please help....
Click to expand...
Click to collapse
I may have been the person you traded with to get the OnePlus 3, but I took the phone back and after 5 hours I got it up and running.
The phone would boot to TWRP, but even after wiping the entire system and dragging a ROM zip to the internal storage, reinstalling did nothing. It just kept booting back to recovery.
The solution entailed the following.
Download stock recovery IMG. Flashed through TWRP. Rebooted recovery and now was back to stock recovery.
Download the official OxygenOS ROM zip from the OnePlus website and changed the name to update.zip
Next I downloaded Android studio for access to ADB. I had never used ADB before, but I knew this was needed to push a file to the phone.
Needless to say, ADB kept freezing my computer when I would type in the commands to side load.
I deleted Android studio and installed a minimal ADB/Fastboot I found online. I opened my command prompt, typed the command for sideloading, and immediately got my installation starting. It took about 10 minutes to fully install. When it was finished, I rebooted and had a fully functioning OnePlus 3
Sent from my ONEPLUS A3000 using Tapatalk
Hey boss., after flashing open beta 12, the phone started hanging now and then. I tried to contact oneplus forums and they asked me to send the log files. Since they took too long to respond, I went to oneplus service centre. They flashed my phone with old oxygen os and the phone didn't start. It went into bootloop
Then I asked them, they said motherboard is corrupted. I left the place and I requested online customer support from oneplus. They too flshed and concluded the same. Can I know whether flashing/sideloading openbeta created this issue? If so, can you provide me support to avail the warranty on the phone? or recover it via any other method or process?
Please respond as soon as possible. My communication with the world has become limited after this issue. I hope there is some sort of support.
Also note that, the phone can boot into fastboot mode, but bootloader is locked. It can boot into recovery. I tried wiping everything, but the phone is not rebooting.
When I start the phone, it stucks in the boot logo and after a while, the screen becomes blank and a white color notification LED is glowing.
Kindly help me.
i had the same issue last week after updating to 13..and i tried to flash the black theme..it went black..i had nothing....it was like it was bricked... here's how after many failed attempt's..i had to clean out all files including backups.wipe data i had to wipe system i had to clean out all previous files.from TWRP recovery.then i had to download the latest software release then put the zip file in my phone storage not in the download file ..then i had to flash stock recovery.then install the new system..and i made the mistake of trying to use some of my app backups like for one estrong file ..all of them were corrupt.so start fresh.
You might try this unbricking method:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Though your device isn't hard-bricked, this would reset your device to the absolute factory settings (watch out, your data will be erased) on an older OxygenOS version.
I would recommend the 2nd Method, as it restores all partitions to factory settings.
I might also know where your issue came from:
Though you can flash the Open Beta (or any other ZIP from OnePlus) through the Stock Recovery, OnePlus states that you need to be on an unlocked bootloader for not bricking your device.
TimSchumi said:
You might try this unbricking method:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
Though your device isn't hard-bricked, this would reset your device to the absolute factory settings (watch out, your data will be erased) on an older OxygenOS version.
I would recommend the 2nd Method, as it restores all partitions to factory settings.
I might also know where your issue came from:
Though you can flash the Open Beta (or any other ZIP from OnePlus) through the Stock Recovery, OnePlus states that you need to be on an unlocked bootloader for not bricking your device.
Click to expand...
Click to collapse
It worked, but no network connection or wifi connection!
Is there a way to bring them back?
SivaMaxwell said:
It worked, but no network connection or wifi connection!
Is there a way to bring them back?
Click to expand...
Click to collapse
You might try to unlock your bootloader (There are giudes to do this) and flash a OxygenOS package from oneplus.net through the stock recovery, to ensure the firmware is OK (Do a factory reset from recovery!). I don't know if the Unbrick Tool only restores corrupted partitions or all. It might have installed the wrong system over your previously installed firmware if only corrupted partitions are restored. Keep the bootloader unlocked to be on the safe side (After some time you will be able to just ignore the boot message and you have better access to fastboot and recovery)!
Also, GG to OnePlus for (fake) Motherboard corruption!
About warranty:
Warranty should be ok as long as you won't do hardware modifications (I think).
Bootloader unlocking is definitely safe
TimSchumi said:
You might try to unlock your bootloader (There are giudes to do this) and flash a OxygenOS package from oneplus.net through the stock recovery, to ensure the firmware is OK (Do a factory reset from recovery!). I don't know if the Unbrick Tool only restores corrupted partitions or all. It might have installed the wrong system over your previously installed firmware if only corrupted partitions are restored. Keep the bootloader unlocked to be on the safe side (After some time you will be able to just ignore the boot message and you have better access to fastboot and recovery)!
Also, GG to OnePlus for (fake) Motherboard corruption!
About warranty:
Warranty should be ok as long as you won't do hardware modifications (I think).
Bootloader unlocking is definitely safe
Click to expand...
Click to collapse
I tried to update to recent oxygen os. Then the original proble started again.
It is not booting up, again..
SivaMaxwell said:
I tried to update to recent oxygen os. Then the original proble started again.
It is not booting up, again..
Click to expand...
Click to collapse
No, reflash the OxygenOS package of the same Version that is installed by the Unbrick Tool (If you can still get itfrom oneplus.net) and then check if Network does work. Also, check your IMEI.
I think you might have a corrupted EFS partition. That's y you don't have a working network. Check whether your device show a IMEI under about phone.
m4manusraj said:
I think you might have a corrupted EFS partition. That's y you don't have a working network. Check whether your device show a IMEI under about phone.
Click to expand...
Click to collapse
EFS doesn't have an effect on WiFi.
That's why I think that it is a firmware issue
I think, I have solved it guys. I'll let you know once completely under control
So, Thank you very much for your support. With this little support from you and my previous Foresightedness helped me restore the phone.
So just in case if any one else faces the same or similar problem, this is the process:
STEP0: If there is any partition corrupted, the device don't boot properly. And, The customer care/ sevice centre guys state it as motherboard problem. Donot Panic. Always take TWRP backup whenever you change your ROM. This Backup helps you to restore whenever you're in trouble. In this particular case, ESF backup is required. So, take a complete backup (everything) in TWRP, it saves your ass.. keep the backup in your PC or any safe Storage (the complete TWRP Folder which is in Internal Memory) before flashing any custom ROM.
Step1: Follow method2 in this guide: https://forums.oneplus.net/threads/g...plus-3.452634/
Step2: if everything is alright, its done. Otherwise, The device boots up with some missing features and details. At this time, you have to unlock the bootloader. See The forum to know how to do it. Basic searching can give you the method.
If you can transfer the TWRP folder from PC to Phone, it's good. But the phone boots itself because of missing firmware. Even Bluetooth couldn;'t be used.
In my particular case, I couldnot copy from PC to mobile or viceversa. So, you cannot copy back your TWRP folder in this situation.
So, Unlock bootloader. Then reboot to system (without doing anything)
Step3: Reboot to bootloader and flash TWRP 3-0.2 version only. otherwise device will be encrypted.
Step4: download Ressurection Remix ROM version : ResurrectionRemix-M-v5.7.4-20161113-PUBLIC-ex-oneplus3 or you can experiment with any other custom ROM but only android 6 (*Marshmallow). Also make sure that you have universal adb drivers. install them if not (search in the forums.)
Step5: goto TWRP recovery, in this, goto wipe option. Drag the swipe to wipe button here. (normal wipe).
Step6: Now, in advanced options, select adb sideload option and select the two wipes in the next menu. Start ADB sideload in the TWRP.
Step7: Now, Start the adb sideloading the custom ROM from your PC. You donot Require Gapps for transferring a file. So donot flash Gapps.
Step8: After the sideload is complete, reboot into system. Now you can transfer files between phone and PC. Now, Copy the Complete TWRP folder into the internal memory. A pop-up asks for merging the folders. Allow the merging, even if you have another TWRP backup there. They don't overlap.
Step9: Now, Boot into TWRP and restore completely. The phone boots up properly, this time. Everything works as expected. every mysterious problem is solved. Now you will get update request if you are on previous version of OOS.
Last but not Least: Please do not use any app recovery tools. they may cause issues while following the above steps
Thank to every XDA member, helping us save the time and money we spend at service center.
m4manusraj said:
I think you might have a corrupted EFS partition. That's y you don't have a working network. Check whether your device show a IMEI under about phone.
Click to expand...
Click to collapse
TimSchumi said:
EFS doesn't have an effect on WiFi.
That's why I think that it is a firmware issue
Click to expand...
Click to collapse
Yes, boss. The EFS is corrupted. But, thanks to TWRP, it also has the option to backup EFS, modem. SO, I used my old backup from Jan2017 to restore it back.
But, TO place TWRP back in phone, the original OOS3.1.2, even after reflashing didn't support. I thought for a while and flashed the All loved RR (MM) . THen, it gave me the scope to t/f the folder to internal memory.
Now, I restored the EFS , Modem, sytem with data. and hell yea!! the phone is back to life.
Complete Backup, Atleast once for 3 months saves your ass..
I am glad it helped. That's the power of Xda.
My OP3 is stuck on the boot animation only while booting up Oxygen OS. At first I thought it was bricked but as I proceeded I found out that it isn't and i'm able to boot other OS on it. I've had Resurrection Remix which I had no problems flashing whatsoever. But I'm having this problem with Oxygen OS. Has anyone experienced this? What do I do? Please help.
Hello guys,
my Oneplus 3 is hard bricked, I tried the methods in the Mega Unbrick guide, my device already gets shown as Qualcomm 9008 ... in Device Manager, so I started the MSM DownloadTool and it flashed anything without errors. But when the phone reboots I get a black screen and the white led is on.
I can't even boot to stock recovery (Volume down + power doesn't work and rebooting to recovery through fastboot doesn't work, too....) my bootloader is locked and all attempts to unlock the bootloader are failing with the error "remote: oem unlock is not allowed"
So at the moment I'm stuck in fastboot and nothing else works -.-
Can someone please help me?
The unbrick tool has an old firmware, can I replace the files with files from a newer firmware?
Thanks!
Have you tried the exact steps from Method 2? Maybe unzip it? If that doesn't work which is highly unlikely then there is not much you can do.
Puddi_Puddin said:
Have you tried the exact steps from Method 2? Maybe unzip it? If that doesn't work which is highly unlikely then there is not much you can do.
Click to expand...
Click to collapse
Yeah I tried it as I said, the MSM DownloadTool showed me Completed and the phone tried to boot up after that.
I'm now contacting the OP Customer Support, I've read a few times that they have other files to unbrick the phone with the MSM Tool.
min-dfreak said:
Yeah I tried it as I said, the MSM DownloadTool showed me Completed and the phone tried to boot up after that.
I'm now contacting the OP Customer Support, I've read a few times that they have other files to unbrick the phone with the MSM Tool.
Click to expand...
Click to collapse
Ye thats the only thing you can currently do... May i ask what you have done how did it get bricked?
I just updated AICP ota and after flashing the update my phone didn't boot up. The screen went black immediately.
So I thought that it is maybe a Problem with the ROM and I tried to go back to stock.
Flashed the stock recovery and locked the bootloader, but I couldn't boot to the stock recovery.
There it started...
Switch off the phone, connect usb ,open unbrick tool full ( method 2),Press vol up,down and power buttons same time ,tool will recognize phone then start , you must unbrick now.
NEVER LOCK YOUR PHONE.
drmuruga said:
Switch off the phone, connect usb ,open unbrick tool full ( method 2),Press vol up,down and power buttons same time ,tool will recognize phone then start , you must unbrick now.
NEVER LOCK YOUR PHONE.
Click to expand...
Click to collapse
Please read, I already did that.
The tool completed it successfully, but still black screen after a reboot.
Only the LED is flashing white.
I already contacted the support, they will do it remotely tomorrow.
min-dfreak said:
Please read, I already did that.
The tool completed it successfully, but still black screen after a reboot.
Only the LED is flashing white.
I already contacted the support, they will do it remotely tomorrow.
Click to expand...
Click to collapse
Never but never lock your bootloader...
If recovery, boot or system partition is modified. There's no harm in re locking otherwise..
Hi guy i have a big problem i buy a one plus 3 i was using it 1 month and there was a update i don't remember what it was oreo or nougat when the update downloaded i install it and the i got a bootloop 2 hours didn't boot and my device is not rooted and didn't enable developer option i tried to install stock rom by adb and fastboot with sideload it load but it stuck on 50% then it say failed tried to install recovery in fastboot i installed drive oneplus 3 ect but can't flash it i think because i have oem locked i trien to unlocked it says failed 00.6s ect and i don't have guarantee i have dash and cable charger i can charge it and go to fastboot and recovery but when i boot my phone normally i show logo one plus then the two red bullet who move then it power off
Dsn Fouad said:
Hi guy i have a big problem i buy a one plus 3 i was using it 1 month and there was a update i don't remember what it was oreo or nougat when the update downloaded i install it and the i got a bootloop 2 hours didn't boot and my device is not rooted and didn't enable developer option i tried to install stock rom by adb and fastboot with sideload it load but it stuck on 50% then it say failed tried to install recovery in fastboot i installed drive oneplus 3 ect but can't flash it i think because i have oem locked i trien to unlocked it says failed 00.6s ect and i don't have guarantee i have dash and cable charger i can charge it and go to fastboot and recovery but when i boot my phone normally i show logo one plus then the two red bullet who move then it power off
Click to expand...
Click to collapse
I'm assuming your device is OnePlus3 and not 3T
Okay. Firstly give a try to Oneplus3 openbeta Nougat special edition.
Oneplus3 : http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Method 1 : specific recovery for open beta24 available in Oneplus downloads
https://downloads.oneplus.com
Find legacy roms and find openbeta 24
Method 2: latest TWRP
If your bootloader is locked this isn't gonna work. But if it is still in unlocked .
Download TWRP for Oneplus3 from official TWRP site
Flash the recovery you choose using fast boot.
Now using asn command, try to flash the special edition.
Mostly this solves your issue. It helped me.
Let me know whether you face any issues.
Note: in this method you may lose every data you have on the phone. It boots up (if at all ? ) with fresh firmware and fresh storage (sometimes)
SivaMaxwell said:
I'm assuming your device is OnePlus3 and not 3T
Okay. Firstly give a try to Oneplus3 openbeta Nougat special edition.
Oneplus3 : http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Method 1 : specific recovery for open beta24 available in Oneplus downloads
https://downloads.oneplus.com
Find legacy roms and find openbeta 24
Method 2: latest TWRP
If your bootloader is locked this isn't gonna work. But if it is still in unlocked .
Download TWRP for Oneplus3 from official TWRP site
Flash the recovery you choose using fast boot.
Now using asn command, try to flash the special edition.
Mostly this solves your issue. It helped me.
Let me know whether you face any issues.
Note: in this method you may lose every data you have on the phone. It boots up (if at all ? ) with fresh firmware and fresh storage (sometimes)
Click to expand...
Click to collapse
Yeah i have oneplus 3 my bootloader is locked can't flash anything im going to try method 1
By the way why beta 24 why not lastest update ? And whene i download it do you want me to flash it with sideload like #adb sideload openbeta24.zip ?
Dsn Fouad said:
Yeah i have oneplus 3 my bootloader is locked can't flash anything im going to try method 1
By the way why beta 24 why not lastest update ? And whene i download it do you want me to flash it with sideload like #adb sideload openbeta24.zip ?
Click to expand...
Click to collapse
The file I gave link to is a special edition by Oneplus for Openbeta-Nougat. You can go to Nougat from any rom.
Rom: http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Specific recovery should be downloaded from Oneplus website.
You can sideload using adb or store internal storage and flash.
I tried with latest TWRP recently and it worked.
Note that all your data gets wiped if you use oneplus-recovey and asn sideload
SivaMaxwell said:
The file I gave link to is a special edition by Oneplus for Openbeta-Nougat. You can go to Nougat from any rom.
Rom: http://downloadmirror.co/Wa9/O2N_OBT_15801_OXYGEN_SIGN_wipe.zip
Specific recovery should be downloaded from Oneplus website.
You can sideload using adb or store internal storage and flash.
I tried with latest TWRP recently and it worked.
Note that all your data gets wiped if you use oneplus-recovey and asn sideload
Click to expand...
Click to collapse
The problem is i dont have store internal storage and when i try to flash anything it say oem locked not allowed and when i flash a rom with adb sideload jfjd.zip it stuck on 60% will it be complete if i use your beta ?
Dsn Fouad said:
The problem is i dont have store internal storage and when i try to flash anything it say oem locked not allowed and when i flash a rom with adb sideload jfjd.zip it stuck on 60% will it be complete if i use your beta ?
Click to expand...
Click to collapse
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery
SivaMaxwell said:
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery
Click to expand...
Click to collapse
Thanks i will download and give it a try
SivaMaxwell said:
Yes, it won't stick at 60% with this beta. I'm not the owner. It was provided on Oneplus forums. Try that one and tell me the result. It is a signed zip. So it will work on official Oneplus-recovery
Click to expand...
Click to collapse
Before that i downloaded msm download tool 3.0.8 i tested it and it boot but it say enter pin password i dont know what is the pin i didn't use a pin before it was working
Dsn Fouad said:
Before that i downloaded msm download tool 3.0.8 i tested it and it boot but it say enter pin password i dont know what is the pin i didn't use a pin before it was working
Click to expand...
Click to collapse
Simply reboot to recovery and say yes to wipe every data.
Note1:
all your internal data is wiped in the method I suggested. I can recall there is a method to recover data only if bootloader is unlocked. If your bootloader is locked there is no other way.
Note2: your data will be formatted to f2fs file system. If you want to flash any custom ROM, YOU SHOULD CHECK COMPATIBILITY WITH F2FS in that ROM forums.
It's better to always have EXT4 file system. You can change this file system with TWRP
SivaMaxwell said:
Simply reboot to recovery and say yes to wipe every data.
Note1:
all your internal data is wiped in the method I suggested. I can recall there is a method to recover data only if bootloader is unlocked. If your bootloader is locked there is no other way.
Note2: your data will be formatted to f2fs file system. If you want to flash any custom ROM, YOU SHOULD CHECK COMPATIBILITY WITH F2FS in that ROM forums.
It's better to always have EXT4 file system. You can change this file system with TWRP
Click to expand...
Click to collapse
Bootloader is locked i tryed to flash the 24 beta yoi give me but it stuck on 47 and say failed im just going to sell it
Dsn Fouad said:
Bootloader is locked i tryed to flash the 24 beta yoi give me but it stuck on 47 and say failed im just going to sell it
Click to expand...
Click to collapse
Even if the bootloader is locked, you can boot into the current rom and unlock simply by going to advanved options.
It is a very simple process.
HONOR 7X ( indian variant )
Phone is in a boot loop.
It shows Honor Logo and then the Error screen with the following message :
ERROR MODE
Attention!
Please update system again
Error!
Func NO : 15 (bl31 image)
Error NO : 1 (security verify failed!)
I tried to manually update to Oreo and was successful.
But VoLTE was not working properly.
So, i decided to roll back to EMUI 5.0 (Nougat) and got stuck in Boot Loop.
Initially both twrp and fastboot was working.
I tried to flash Stock recovery for oreo using fastboot.
But it didn't work.
At that point i lost both twrp and stock recovery.
It went into ERROR mode with different error codes saying "No Recovery Image" and "Load Failed"
I tried to Erase recovery and re-flash it.
I tried erasing System and flashing the system.img for oreo which was extracted from UPDATE.APP
I tried Multi tools.
I tried dload method.
Nothing worked. Same error mode.
Then i finally tried flashing the stock recovery again and relocked the oem.
Now, I can't even get into Fastboot.
It just displays the ERROR Screen.
I tried draining the battery to 0% and restarting it.
I tried all button combinations.
No luck.
Nothing works.
Now, i have a bricked phone with no recovery and no fastboot.
And i don't know whether they will accept this in the service center.
Is there someone who could really help me get my phone back?
rahulrk.2303 said:
HONOR 7X ( indian variant )
Phone is in a boot loop.
It shows Honor Logo and then the Error screen with the following message :
ERROR MODE
Attention!
Please update system again
Error!
Func NO : 15 (bl31 image)
Error NO : 1 (security verify failed!)
I tried to manually update to Oreo and was successful.
But VoLTE was not working properly.
So, i decided to roll back to EMUI 5.0 (Nougat) and got stuck in Boot Loop.
Initially both twrp and fastboot was working.
I tried to flash Stock recovery for oreo using fastboot.
But it didn't work.
At that point i lost both twrp and stock recovery.
It went into ERROR mode with different error codes saying "No Recovery Image" and "Load Failed"
I tried to Erase recovery and re-flash it.
I tried erasing System and flashing the system.img for oreo which was extracted from UPDATE.APP
I tried Multi tools.
I tried dload method.
Nothing worked. Same error mode.
Then i finally tried flashing the stock recovery again and relocked the oem.
Now, I can't even get into Fastboot.
It just displays the ERROR Screen.
I tried draining the battery to 0% and restarting it.
I tried all button combinations.
No luck.
Nothing works.
Now, i have a bricked phone with no recovery and no fastboot.
And i don't know whether they will accept this in the service center.
Is there someone who could really help me get my phone back?
Click to expand...
Click to collapse
I was gonna do a roll back too. Maybe I need to re exam your problem first.
Like why did you flash the Oreo system image after you rolled back?
Sorry, but I don't know of any steps forward for you, but can you tell the steps you did in the "Roll-back" and try to be detailed.
Please take a full back up before you roll back.
mrmazak said:
I was gonna do a roll back too. Maybe I need to re exam your problem first.
Like why did you flash the Oreo system image after you rolled back?
Sorry, but I don't know of any steps forward for you, but can you tell the steps you did in the "Roll-back" and try to be detailed.
Click to expand...
Click to collapse
I didn't succeed rolling back. I flashed the system.img and stock recovery of emui 5.0. But it got me the error.
Maybe the system partitions of emui 8.0 and 5.0 are different.
For example, The recovery partition has changed to recovery_ramdisk in emui 8.0.
Then, I tried flashing system.img and recovery of emui 8.0.
I got stuck in a bootloop.
But fastboot was accessible.
I tried flashing twrp for 8.0 by openkirin. It didn't work too.
Then i thought maybe i should flash the stock recovery and relock the oem and i did it.
Now i ended up with a locked bootloader, no recovery. Just the error message and the bootloop.
Somebody please help.
rahulrk.2303 said:
I didn't succeed rolling back. I flashed the system.img and stock recovery of emui 5.0. But it got me the error.
Maybe the system partitions of emui 8.0 and 5.0 are different.
For example, The recovery partition has changed to recovery_ramdisk in emui 8.0.
Then, I tried flashing system.img and recovery of emui 8.0.
I got stuck in a bootloop.
But fastboot was accessible.
I tried flashing twrp for 8.0 by openkirin. It didn't work too.
Then i thought maybe i should flash the stock recovery and relock the oem and i did it.
Now i ended up with a locked bootloader, no recovery. Just the error message and the bootloop.
Somebody please help.
Click to expand...
Click to collapse
OK, yes there is different partition table for oreo, so more that those partitions was needed.
one thing you might be able to try, is a manuael update.
put the oreo update.zip in the root of sd card. put card in phone, and hold both volume buttons together with power button.
mrmazak said:
OK, yes there is different partition table for oreo, so more that those partitions was needed.
one thing you might be able to try, is a manuael update.
put the oreo update.zip in the root of sd card. put card in phone, and hold both volume buttons together with power button.
Click to expand...
Click to collapse
I've already tried the dload method. But holding both volume buttons + power button didn't work. It loads into the error mode screen again. Maybe I'll copy the update.zip into the root of SD card and try again. But i think the phone won't boot into software update mode.
Is it hard bricked or soft bricked?
Should i try taking it to the service center?
People
Dont try to roll back from Oreo to Nougat on update ZIPs...
Partitions changed on Oreo System. The available update to Oreo it must read the previous partitions and configure the new partitions.
If you try to do it AFTER installing the update, the installation will get error cause can't read the Nougat partitions.
rahulrk.2303
With the phone powered off, press Vol Down key and insert the USB cable.
What happens?
RSGI said:
People
Dont try to roll back from Oreo to Nougat on update ZIPs...
Partitions changed on Oreo System. The available update to Oreo it must read the previous partitions and configure the new partitions.
If you try to do it AFTER installing the update, the installation will get error cause can't read the Nougat partitions.
rahulrk.2303
With the phone powered off, press Vol Down key and insert the USB cable.
What happens?
Click to expand...
Click to collapse
Nothing. It vibrates. Honor logo. Again the same error screen. I know it's supposed to go into fastboot mode. But unfortunately, it doesn't.
rahulrk.2303 said:
Nothing. It vibrates. Honor logo. Again the same error screen. I know it's supposed to go into fastboot mode. But unfortunately, it doesn't.
Click to expand...
Click to collapse
There is Oreo downgrade proceedure on Chinese huiwei club website. But your device needs full firmware package available.
There is full downgrade packages for al00 al10 and tl10.
rahulrk.2303 said:
Nothing. It vibrates. Honor logo. Again the same error screen. I know it's supposed to go into fastboot mode. But unfortunately, it doesn't.
Click to expand...
Click to collapse
Man... The FASTBOOT partiton is also screwed up...
The only change you got, other take the phone to the Huawei Service Center, is the dload method.
But for that you'lll need full packages.
mrmazak
Can you share a link to those packages?
RSGI said:
Man... The FASTBOOT partiton is also screwed up...
The only change you got, other take the phone to the Huawei Service Center, is the dload method.
But for that you'lll need full packages.
mrmazak
Can you share a link to those packages?
Click to expand...
Click to collapse
I have downloaded updateL22.zip for oreo and tried the dload method. It didn't work. It still boots to the same error mode. Is this condition hard brick or soft brick? I don't think there is a problem with the motherboard because the screen is turning on and it's in a bootloop. But i can't access recovery or fastboot. I'm confused. Maybe it's a software issue. But there is no way i could access the phone in order to flash something. I'm planning to take it to the service center and act innocent. Any suggestions? Will they find out that i unlocked or rooted and messed with the partitions. Is there any chance they could fix it?
RSGI said:
Man... The FASTBOOT partiton is also screwed up...
The only change you got, other take the phone to the Huawei Service Center, is the dload method.
But for that you'lll need full packages.
mrmazak
Can you share a link to those packages?
Click to expand...
Click to collapse
the three marked as full
b192
dated 3-28
http://pro-teammt.ru/firmware-database/?firmware_model=bnd-&firmware_page=0
mrmazak said:
the three marked as full
b192
dated 3-28
http://pro-teammt.ru/firmware-database/?firmware_model=bnd-&firmware_page=0
Click to expand...
Click to collapse
That's the one i tried.
The BNDAL10 one.
rahulrk.2303 said:
I have downloaded updateL22.zip for oreo and tried the dload method. It didn't work. It still boots to the same error mode. Is this condition hard brick or soft brick? I don't think there is a problem with the motherboard because the screen is turning on and it's in a bootloop. But i can't access recovery or fastboot. I'm confused. Maybe it's a software issue. But there is no way i could access the phone in order to flash something. I'm planning to take it to the service center and act innocent. Any suggestions? Will they find out that i unlocked or rooted and messed with the partitions. Is there any chance they could fix it?
Click to expand...
Click to collapse
If you take it to the service center, it wont matter how you play it...
The phone just dont get that way unless, somehow, the warranty was voided...
The less you say, the less you will pay for they to fix it... I believe that over those Service Centers they can fix almost everythng.
That package is not a full package! you need a Full Package
mrmazak said:
the three marked as full
b192
dated 3-28
http://pro-teammt.ru/firmware-database/?firmware_model=bnd-&firmware_page=0
Click to expand...
Click to collapse
Here´s a noob question:
What update.zip should i download?
1 - The one in the filelist section
2 - The one at the update section
Please, dont tell me that they're the same....
RSGI said:
If you take it to the service center, it wont matter how you play it...
The phone just dont get that way unless, somehow, the warranty was voided...
The less you say, the less you will pay for they to fix it... I believe that over those Service Centers they can fix almost everythng.
That package is not a full package! you need a Full Package
Click to expand...
Click to collapse
Is there nothing more i could do?
And what do you think the problem is?
Software issue or Hardware?
rahulrk.2303 said:
Is there nothing more i could do?
And what do you think the problem is?
Software issue or Hardware?
Click to expand...
Click to collapse
How the phone end up this way?
What were you trying to do?
How the heck you screw Fastboot? just kidding
If were trying to update, flash something to the device, its most likely a software issue.
If the phone fell down, bumped into something... well this increases the change that some hardware may by screwed also...
RSGI said:
If you take it to the service center, it wont matter how you play it...
The phone just dont get that way unless, somehow, the warranty was voided...
The less you say, the less you will pay for they to fix it... I believe that over those Service Centers they can fix almost everythng.
That package is not a full package! you need a Full Package
Here´s a noob question:
What update.zip should i download?
1 - The one in the filelist section
2 - The one at the update section
Please, dont tell me that they're the same....
Click to expand...
Click to collapse
but i think the update.zip listed in file list is same , don't really know.
all three are needed for full package.
RSGI said:
How the phone end up this way?
What were you trying to do?
How the heck you screw Fastboot? just kidding
If were trying to update, flash something to the device, its most likely a software issue.
If the phone fell down, bumped into something... well this increases the change that some hardware may by screwed also...
Click to expand...
Click to collapse
I flashed Oreo update successfully.
I wanted to Rollback.
I flashed system and recovery of nougat and locked the oem.
The problem is that we can't rollback from oreo to nougat because of different partitions.
I realized that only after locking the oem.
And now there's nothing i could do.
Btw, this is only due to flashing. So, i hope it's not a Motherboard problem.
The cost of flashing Software from service center is very less, even if my warranty is void.
rahulrk.2303 said:
I flashed Oreo update successfully.
I wanted to Rollback.
I flashed system and recovery of nougat and locked the oem.
**The problem is that we can't rollback from oreo to nougat because of different partitions.
Click to expand...
Click to collapse
???Well to be true you did not flash a roll-back(did you?) you only replaced system and recovery. The true roll-back "update.zip" should do more than that.???
I realized that only after locking the oem.
And now there's nothing i could do.
Btw, this is only due to flashing. So, i hope it's not a Motherboard problem.
The cost of flashing Software from service center is very less, even if my warranty is void.
Click to expand...
Click to collapse
mrmazak said:
???Well to be true you did not flash a roll-back(did you) you only replaced system and recovery. The true roll-back "update.zip" should do more than that.???
Click to expand...
Click to collapse
Tbh, i did everything one by one because nothing seems working.
I've tried every single method, trust me.