A friend of mine as the same phone as me, the Huawei Ascend P6, and when she said hers was broken I said I would take a look. I have played around with flashing Android Roms etcetera, but I am totally stuck with this problem.
The problem is as follows: when booting the phone it shows the Huawei Ascend logo (as it should) for a couple of seconds, but then instead of the Huawei animation it shows the name "android" and gets stuck there (see attachment).
After some researching I put the UPDATE.APP file from the Huawei website in the dload folder on the root of the SD-card and tried rebooting. I tried a several times, but nothing happened.
Next I successfully booted in recovery mode but even when starting recovery the screen shows errors (see attachment):
Code:
E:failed to mount /cache (Invalid argument)
E:failed to mount /cache (Invalid argument)
ensure_path_mounted Failed
E:failed to mount /cache (Invalid argument
Installing a ZIP file, wipe cache and wipe data give even more errors.
So I thought I would try flashing through ADB/fastboot, and used the HuaweiUpdateExtractor tool to get the images. I can get manually in fastboot mode, but when I try to flash an image get the error
Code:
FAILED (remote: flash failure, ErrNo:2)
I tried using different files, USB ports, cables, linux and windows but nothing seems to help. Has anyone an idea what to do next?
it would help much to know what fw is / was flashed as last..
this android screen means to me that it should be a chinese / non international version..
if you enter fastboot mode and connect your phone to the pc make sure your pc recognizes the phone (for checking: fastboot devices - it should show you many "????")..if so try to install twrp (there are many threads about it)..then you might be able to install (through twrp) a repack of b513 or another version (but it has to be a repack)..
after that (and hopefully successful) you can try (use search) to change to an official fw again..
just my suggestion
hope you get a solution..
blueIBI said:
it would help much to know what fw is / was flashed as last..
this android screen means to me that it should be a chinese / non international version..
if you enter fastboot mode and connect your phone to the pc make sure your pc recognizes the phone (for checking: fastboot devices - it should show you many "????")..if so try to install twrp (there are many threads about it)..then you might be able to install (through twrp) a repack of b513 or another version (but it has to be a repack)..
after that (and hopefully successful) you can try (use search) to change to an official fw again..
just my suggestion
hope you get a solution..
Click to expand...
Click to collapse
Since I can not boot and it's not my own phone I have no clue what the version is
Luckily my PC recognizes the phone in fastboot (indeed with a weird name with a lot of ?), but I am not able to flash twrp because every time I try I get a FAILED response... Maybe the file I have is wrong. Could you point me to a thread about falshing twrp?
here is a guide for unlocking bootloader: http://forum.xda-developers.com/showthread.php?p=50724517
here is a twrp for JB roms: http://forum.xda-developers.com/showthread.php?p=47633501
here for KK roms: http://forum.xda-developers.com/showthread.php?p=51718302
maybe you need to unlock your bootloader at first
changes not working
Thanks for the links! I am able to flash an image, but for some reason my changes won't stick. When I boot in fastboot it says it is locked and I am able to unlock it, but everytime I reboot it is locked again. The same happens with twrp, I am able to flash the image but for some reason when I boot back into recovery nothing has changed.
My fastboot commands and output:
Code:
C:\Android>fastboot oem get-bootinfo
...
(bootloader) locked
OKAY [ 1.952s]
finished. total time: 1.952s
C:\Android>fastboot oem unlock UUUUUUUUUUUUUUUU
...
OKAY [ 0.012s]
finished. total time: 0.012s
C:\Android>fastboot oem get-bootinfo
...
(bootloader) unlocked
OKAY [ 0.001s]
finished. total time: 0.001s
C:\Android>fastboot flash recovery twrp_2_6_3_3_recovery.img
sending 'recovery' (8690 KB)...
OKAY [ 0.259s]
writing 'recovery'...
OKAY [ 0.390s]
finished. total time: 0.650s
Any idea?
hm..
in this case no..
i'm sorry..your friend should bring it to the service..that's the best advice for now..
blueIBI said:
hm..
in this case no..
i'm sorry..your friend should bring it to the service..that's the best advice for now..
Click to expand...
Click to collapse
That's what I was afraid of..
I think the unlock code doesn't work correctly on this phone for some reason, but I don't think I'll be able to get an unlock code specific for my device from Huawei, without serial number and such which I can't get since the phone doesn't boot.
I hope there is some warranty left...
Results
If anyone is interested (perhaps in the future), the phone was sent for repairs and is working again. They probably replaced the motherboard, but luckily it all fell under the warranty.
Thanks to blueIBI for trying to help!!
Related
Hello everyone, I made a mistake (I am a big noob) and I don't know how to fix it.
I wanted to have fresh phone (real factory reset) to back-up and start over, so in recovery mode (interim one from paul) I wiped data, cache partition and I also formated cache,data, sdcard and system.
Now, I am stuck on htc quietly brilliant screen, I have access to hboot, recovery etc. I have been looking for a solution for 2 days without succes, I am sad.
Can someone help please ? thanks guys.
You wiped the system so there is no android on there!
Eirher download a new Rom and flash or relock bootloader and use ruu
Sent from my HTC One X using xda premium
Thanks sir, I'll try.
sotirios said:
Thanks sir, what can I do ? Which part I did wrong ? thanks again
Click to expand...
Click to collapse
The part you did wrong: It's true that you wipe (dalvik) cache and data before flashing a custom rom. That will perform a factory reset. Wiping system means deleting android itself, as stated before. That's what you did wrong.
Now, we can't know why you wanted to start all over again, but assuming you already flashed a custom recovery, you wanted to install a custom rom. Just go ahaed and do so, your problem will be fixed.
thanks, but I can't because this custom recovery doesn't allow me to mount usb and i have no rom on my sd card
sotirios said:
thanks, but I can't because this custom recovery doesn't allow me to mount usb and i have no rom on my sd card
Click to expand...
Click to collapse
That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push path/to/custom/rom /sdcard
or for linux/mac:
sudo ./adb push path/to/custom/rom /sdcard
This will copy the file to the root of your sdcard, so you can flash it. Good luck!
P.S. there's a thanks button, too
dobbi10k said:
That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push pfad/zu/einer/custom/rom /sdcard
or for linux/mac:
sudo ./adb push pfad/zu/einer/custom/rom /sdcard
This will copy the file to the root of your sdcard, so you can flash it. Good luck!
P.S. there's a thanks button, too
Click to expand...
Click to collapse
That wont work as ADB does not work on any of the custom recoveries at the moment. Im stuck in the same situtation at the mo and as phone is branded cant get the RUU to reflash so just playing the waiting game until either ADB/USB mount available in recovery or S-Off available.
See my thread in development thread
http://forum.xda-developers.com/showthread.php?t=1599748
Sent from my HTC One X using XDA
Hi lee james, thanks, I followed your thread but I don't know how to install ruu after relocking my bootloader, can you help me please ? thx again.
"Eirher download a new Rom and flash"
I can't flash, my ssd is wiped too and i can't mount usb with this custom recovery
"That's not actually a problem. I assume you aleady have the android SDK set up, if you don't, please use the search function or google. try the following command while in the platform-tools folder:
adb push pfad/zu/einer/custom/rom /sdcard"
It doesn't work, it doesn't find my device, even with the adb devices command
sotirios said:
Hi lee james, thanks, I followed your thread but I don't know how to install ruu after relocking my bootloader, can you help me please ? thx again.
Click to expand...
Click to collapse
Go to development thread then shipped ruu ans download specific to ur phone. Follow and Job done
Sent from my HTC One X using XDA
Same problem here! I unfortunatly erase everything from my one x and i can't restore anything!! How can i solve it?? My device is unlocked but stay in s-on mode! Why? From fastboot i can't flash anything! Help!!
Hello folks, problem solved by following leejames instructions :
flash stock recovery
relock bootloader
use ruu
I'm so happy. Thanks.
Mee too!! Thanks a lot!! I'm very very very very very very very very very very very very very very happy!!
1 flash stock recovery
2 relock bootloader
3 use ruu
It works fine!!
I do exactly the same thing , but half way through the RUU process it gives me an error saying i need the correct RUU. anyone can help ?
All you have to do is grab an RUU, run it. now on your pc search for %temp%in there locate ROM.zip. Extract the boot.img and system.img. and push them thru fastboot
Code:
fastboot flash boot boot_signed.img
Code:
fastboot flash system system.img
Code:
adb reboot
i did that , but i get this error:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
I used the latest RUU uploaded 3 days ago in the filefactory folder.
mahdibassam said:
i did that , but i get this error:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
I used the latest RUU uploaded 3 days ago in the filefactory folder.
Click to expand...
Click to collapse
Is your bootloader unlocked?
When I do it with an unlocked bootloader the error changes to this:
C:\ADB>fastboot flash boot boot_signed.img
sending 'boot' (4278 KB)...
OKAY [ 0.741s]
writing 'boot'...
FAILED (remote: not allowed)
finished. total time: 0.942s
C:\ADB>fastboot flash system system.img
sending 'system' (979509 KB)...
FAILED (remote: (00000008))
finished. total time: 0.001s
Nobody can help me?!! ((
Hello
i have some problems with my HTC One X. Until 2 hours ago it worked perfectly and without problems. i didn't flash anything in the last few weeks, but theres ARHD (ICS) installed. But then suddenly it had a freeze, so i had to restart it with pressing the powerbutton for 10 seconds. Since then, it doesn't boot anymore and also i can't access the Recovery, i get a blackscreen if i try, But i come into the Bootloader, Fastboot is possible but doesn't work...
I tried to reflash the Boot.img, but there was an error: erasing cache FAILED (remote: 19000008)
I also tried to reflash the CWM Recovery but there was another error:
5.8.4.0-endeavoru.img
sending 'recovery' (5742 KB)...
OKAY [ 0.904s]
writing 'recovery'...
(bootloader) Format partition SOS done
FAILED (remote: (00030000))
finished. total time: 1.150s
So can anybody help me? All that I want is access to my virtual SD Card for saving my data, and can anybody tell me how and if I can "repair" my One X? And sorry for the bad english, i'm no native speaker...
you can try this, http://forum.xda-developers.com/showthread.php?t=1609190
Thanks, but it didn't help. When i tried to flash the images in fastboot almost the same errors as before occured...i absolutely dont know what to to now, i think i even can't relock the bootloader, flash the stock recovery and a RUU
Achsoistdas19 said:
Thanks, but it didn't help. When i tried to flash the images in fastboot almost the same errors as before occured...i absolutely dont know what to to now, i think i even can't relock the bootloader, flash the stock recovery and a RUU
Click to expand...
Click to collapse
what the error mate?
Hm, i don't really know. There are these Error-Codes, mostly "remote: 19000008" or "remote: 00000004" also with a 5 at the end, and it says "remote: not allowed" sometimes.
Hello,
i have big problem wiht my D855. I'm trying to install recovery on my device via fastboot, because flashify method failed resulting in lack of recovery on my phone... When i enter "the place where recovery should be" boot certification error shows up and the only way to get rid of it is to re-insert the battery. Unfortunatelly fastboot is not working somehow. Command where it stuck while flashing says:
Code:
C:\adb\fastboot flash recovery reco.img
target reported max download size of 214743648 bytes
sending 'recovery' (15382 KB)...
OKAY [ 0.557s]
writing 'recovery'...
device:
Code:
[132740] fastboot: flash:recovery
Ive been already waiting about 40 minutes for this process to continue but of course nothing happened. After removing USB cable it says:
Code:
FAILED (status read failed (Too many links))
finished. total time: 649.362s
Other commands also do not work, they crash almost the same way but with sh.. i called "three dot bug"
Code:
C:\Users\Dom\Desktop\2>fastboot flashing unlock
...
It even dont reboot after typing:
Code:
C:\Users\Dom\Desktop\2>fastboot reboot-bootloader
rebooting into bootloader...
I have tried different cables, USB ports, different PC. I have lates LG drivers installed. What can I do. My OS is running but has many issues like not working wifi, crashing camera or random reboots (on new battery), so I cant use this phone anymore. It is impossible to revert it back to factory because recovery, which is used for this process is not working, so do fastboot...
Please help, I'm not android expert (and poor english user).
Cheers
Flash the latest TWRP onto it, it should let you boot. I had this problem a few days ago on a samsung tablet. I used odin on that. But you are going to have to match up the TWRP version and the android version you are running.
If you get TWRP working you wont have any problems, you can fix everything from there. Flash fulmics, unroot, what ever you want. Wipe the whole device ect. Make your goal trying to get TWRP on it.
Well, the problem is that I'm trying to flash TWRP now, it is the "reco.img" file, because I was trying to resolve the recovery instalation problem by changing name of file, which could be a problem somehow.
I found adb method to flash recovery:
Code:
adb shell
su
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/recovery
dd if=/sdcard/yourrecovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery
Will it work? ADB is working fine, I already tried similar method when removing and reinstalling laf.
Hi, i installed the latest LG G5 Update (lineage-14.1-20170822-nightly-h850-signed), the first regular reboot was fine.
The second reboot has "bricked" my phone.
Please check the attached Picture from the phone.
Anyon a idea how to get back the phone to "life"??? :crying:
Thank you in advance for any assistance
MoPhat
This advise comes "as is" and with no warranty and I will not be responsible for any damages of any kind.
That's a soft brick (I wouldn't even call it a brick) and should be easy to resolve.
Did you erase data and system before flashing the ZIP file? You should always do this before flashing a new OS or did you just flash over your original LG5's OS without erasing those partitions?
Try re-downloading lineage-14.1-20170822-nightly-h850-signed and run a crc32 check on both zip files (the one you downloaded originally and the one you downloaded the second time) to see if the crc32 values match. If they don't, that would explain why you ended up in this situation (assuming you flashed the file the correct way). If you are on Windows, you can download a utility called "hashmyfiles" by NirSoft to get the crc32 along with other checksum values. If you are on linux, you can use the "crc32 lineage-14.1-20170822-nightly-h850-signed.zip" command to see the crc32 value and if values do not match, try downloading it again and do the check one more time until the values match. You can also click on the "sha256" and "sha1" links below the link you downloaded the file from and then using "hashmyfiles" you can compare the values whether they match.
Anyway, the way I personally would go with this one is try to enter Recovery mode, erase system, data (and probably boot but not necessary as the OS zip file will over write it anyway) and try again. If your recovery asks you to install root / SuperUser, you should select "No" and use LOS's official SuperUser add-ons if that's what you are after.
Thank you marco-v
I can't check the crc from the file because i have updated the latest Version with the build in update function...
I have tryed to boot in the recovery menu by pressing the power und volume down button, realising when i see the lg logo an pressing again both to (normaly) enter the recovery mode. it appears the same message
http://androidflagship.com/20275-boot-lg-g5-recovery-mode
the only menu that Comes are the "factory data reset" menu, but this makes no difference...
any further ideas?
marco-v said:
This advise comes "as is" and with no warranty and I will not be responsible for any damages of any kind.
That's a soft brick (I wouldn't even call it a brick) and should be easy to resolve.
Did you erase data and system before flashing the ZIP file? You should always do this before flashing a new OS or did you just flash over your original LG5's OS without erasing those partitions?
Try re-downloading lineage-14.1-20170822-nightly-h850-signed and run a crc32 check on both zip files (the one you downloaded originally and the one you downloaded the second time) to see if the crc32 values match. If they don't, that would explain why you ended up in this situation (assuming you flashed the file the correct way). If you are on Windows, you can download a utility called "hashmyfiles" by NirSoft to get the crc32 along with other checksum values. If you are on linux, you can use the "crc32 lineage-14.1-20170822-nightly-h850-signed.zip" command to see the crc32 value and if values do not match, try downloading it again and do the check one more time until the values match. You can also click on the "sha256" and "sha1" links below the link you downloaded the file from and then using "hashmyfiles" you can compare the values whether they match.
Anyway, the way I personally would go with this one is try to enter Recovery mode, erase system, data (and probably boot but not necessary as the OS zip file will over write it anyway) and try again. If your recovery asks you to install root / SuperUser, you should select "No" and use LOS's official SuperUser add-ons if that's what you are after.
Click to expand...
Click to collapse
So it looks like your Recovery mode is messed up too? Not sure how that might have happened unless you instructed LOS to "Update Recovery" .
Have you tried to see if you are able to enter fastboot mode and reflash your custom recovery image again and try to enter Recovery mode again? The one I use on my device (Oppo Find 7) is a TWRP image and I find it very reliable.
You can see if you can boot to Recovery by running the following command from fastboot mode (assuming you have a TWRP image)
fastboot boot twrp-x.x.x-x-h850.img
Replace x.x.x.x with the version of the file.
Tryed, result is:
Code:
C:\Temp\root_H850>fastboot boot twrp-3.1.1-0-h850.img
downloading 'boot.img'...
OKAY [ 0.430s]
booting...
FAILED (remote: unknown command)
finished. total time: 0.451s
With "adb.exe devices" are the phone not listed
Ok, my device is locked!?!?
Code:
C:\Temp\root_H850>fastboot flash recovery twrp-3.1.1-0-h850.img
target reported max download size of 536870912 bytes
sending 'recovery' (19076 KB)...
OKAY [ 0.428s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.456s
So i have tryed to unlock the device again with the unlock key i get:
Code:
C:\Temp\root_H850>fastboot flash unlock unlock.bin
target reported max download size of 536870912 bytes
sending 'unlock' (1 KB)...
OKAY [ 0.037s]
writing 'unlock'...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.059s
How can i disable the " Enable OEM unlock" in the developer Settings without a gui???
Ok, fastboot works, that's good but it looks like your bootloader is locked again.
FAILED (remote: oem unlock is not allowed)
Click to expand...
Click to collapse
Try following these instructions: https://forum.xda-developers.com/lg-g5/development/recovery-team-win-recovery-project-lg-g5-t3363047 and see if you can get TWRP running and if you do, you can try flashing LOS again but format data + system (you will lose all data) and if you are not careful, you might lose data on internal storage + external storage so read carefully what's displayed on the screen before going ahead.
Also: http://developer.lge.com/resource/mobile/RetrieveBootloader.dev?categoryTypeCode=ANRS and this will show you how to unlock your bootloader.
---------- Post added at 01:42 PM ---------- Previous post was at 01:41 PM ----------
I just read your post, you can try:
fastboot oem unlock
and see if it works. May be it will because it was unlocked already once but can't tell for sure.
Sorry, nothing has worked.
I will try set "upgrade error" back in the lg update tool to flash the original firmware, but i need a SERIAL or the IMEI number, how can i find this out?
Normally, IMEI numbers are located right under the battery on phones that come with removable back covers and batteries. Yours however slides out, it might be somewhere there or perhaps you can check the box / packaging. So the following command didn't work?
fastboot oem unlock
What's the error you got? The official bootloader instructions on LG's website should have worked as it supports your model. To me the only issue you seem to be having is a restricted booloader and once you unlock it, everything should be fine. This is why you can't boot into TWRP using the boot command.
Not worked, the result is:
Code:
C:\Temp\root_H850>fastboot oem unlock
...
FAILED (remote: unknown command)
finished. total time: 0.025s
I see, thx, if the LG official unlock instructions did not or no longer work followed by the instructions here https://forum.xda-developers.com/lg-g5/development/recovery-team-win-recovery-project-lg-g5-t3363047, I am out of ideas. Perhaps someone else can help and provide further hints.
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Just a shot in the dark but have you enabled oem unlocking in developer options?
Xceeder said:
Just a shot in the dark but have you enabled oem unlocking in developer options?
Click to expand...
Click to collapse
no unfortunately not , thats the problem
amans90 said:
no unfortunately not , thats the problem
Click to expand...
Click to collapse
Okay well I hope you can get your phone sorted now , if I've helped then please leave a thumbs up on my post I really appreciate it...
amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Hi i have the same problem like you did you solve it ?
Dsn Fouad said:
Hi i have the same problem like you did you solve it ?
Click to expand...
Click to collapse
see below.
Xceeder said:
Just a shot in the dark but have you enabled oem unlocking in developer options?
Click to expand...
Click to collapse
Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Sent from my ONEPLUS A3003 using Tapatalk
n1kos said:
Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Click to expand...
Click to collapse
I dont know i flashed the lastest os and the old with sideload but it stuck on 45%
n1kos said:
Have you tried to flash any full Rom from stock recovery? Doesn't need unlocked bootloader as long as its the official OnePlus software.
Click to expand...
Click to collapse
Here
Dsn Fouad said:
Here
Click to expand...
Click to collapse
You are trying to flash TWRP with a locked bootloader and it obviously fails. Download the full official ROM from OnePlus site and the corresponding recovery also. First flash the recovery and reboot to bootloader and then flash the OS and reboot. If you are successful, you can enable Developer Options and from there OEM unlock and USB debugging. Thereafter you can try TWRP, Magisk and other ROMs.
Hmm, I thought he said he can enter bootloader and recovery. If so, reboot the phone in stock recovery and flash full Rom from local update.
Sent from my ONEPLUS A3003 using Tapatalk
tnsmani said:
You are trying to flash TWRP with a locked bootloader and it obviously fails. Download the full official ROM from OnePlus site and the corresponding recovery also. First flash the recovery and reboot to bootloader and then flash the OS and reboot. If you are successful, you can enable Developer Options and from there OEM unlock and USB debugging. Thereafter you can try TWRP, Magisk and other ROMs.
Click to expand...
Click to collapse
You mean flash twrp in fastboot and stock rom in recovery adb sideload i tried all of that i downloaded the lastest stock and lastest twrp it fails it's okay thanks for everything im just going to sell it, it's completely bricked because of that oem and usb debugging locked small things can be dangerous.
Dsn Fouad said:
You mean flash twrp in fastboot and stock rom in recovery adb sideload i tried all of that i downloaded the lastest stock and lastest twrp it fails it's okay thanks for everything im just going to sell it, it's completely bricked because of that oem and usb debugging locked small things can be dangerous.
Click to expand...
Click to collapse
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb and boot.
tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
Oh i see now where can i find the lastest recovery and by how i need to flash it, in adb sideload (recovery.img) or fastboot flash recovery (oneplus recovery.img)?
tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
I tried again but failed with official oneplus 3 recovery
Dsn Fouad said:
I tried again but failed with official oneplus 3 recovery
Click to expand...
Click to collapse
Here
Dsn Fouad said:
I tried again but failed with official oneplus 3 recovery
Click to expand...
Click to collapse
Here
tnsmani said:
NO.
So that is where you are committing a mistake. You have not been reading the posts carefully.
All of us are asking you to download the STOCK recovery compatible with the version of the stock ROM chosen by you and to FLASH THE STOCK RECOVERY FIRST, NOT TWRP.
Because TWRP can't be flashed with a locked bootloader whereas the stock recovery can be flashed from bootloader. Then go for the ROM, sideload it using adb from bootloader and boot.
Click to expand...
Click to collapse
...
amans90 said:
Hallo,
this is my problem: i dont have working system. When i turn on my device i only see one Plus logo. I have access to fastbot and recovery mode.
The things i have already tried:
https://forums.oneplus.net/threads/guide-mega-unbrick-guide-for-a-hard-bricked-oneplus-3.452634/
I have aleready executed method 1 and 2 ( without How to Prevent Data Wipe in Method 2) and everything is working properly until I perform Step 14, when I try to flash via adb sideload latest OXYGEN OS it always stops after 47%. (Installation failed).
I have also tried fastboot method:
PS C:\adb> fastboot devices
755549d1 fastboot
PS C:\adb> fastboot oem unlock
...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.000s
PS C:\adb> fastboot flash recovery recovery.img
target reported max download size of 536870912 bytes
sending 'recovery' (22605 KB)...
OKAY [ 0.625s]
writing 'recovery'...
FAILED (remote: Partition flashing is not allowed)
finished. total time: 0.641s
now i really dont know what to do . just hope that someone can really help me.
https://forum.xda-developers.com/oneplus-3/help/unlock-bootlader-t3411550
after some search i found this post, and the user seems to had the same problem that i have.
Click to expand...
Click to collapse
Make sure you are using the latest version of adb and fastboot, had some trouble myself with this:
https://developer.android.com/studio/releases/platform-tools
jeffrey268 said:
Make sure you are using the latest version of adb and fastboot, had some trouble myself with this:
https://developer.android.com/studio/releases/platform-tools
Click to expand...
Click to collapse
Nah it will still fail, all because of that oem and device state locked, lol i buy a new phone used it 1 month i was having a update available i updated it and then boom 370€ gone just like that, it took me 4 month to got it, i just want to kill people now im very depressed right now god bless people like you thanks for your help.