Related
Hi Folks,
I'm kinda stuck here. Spent the lst 2 hours googling for a possible solution but no luck.
I've tried to OEM Unlock my OP2 to flash TWRP. When I typed fastboot oem unlock in cmd command, my phone started to reboot itself every 1 second.
I've installing the corect drivers using SDK Tools.
Please help as I'm not sure what else I can do.
Did you ticked under dev options allow oem unlock? Try to flash latest stock rom and then unlock.
acmerw said:
Did you ticked under dev options allow oem unlock? Try to flash latest stock rom and then unlock.
Click to expand...
Click to collapse
I did turn on OEM Unlock as well as USB Debugging. I've tried to unlock the bootloader using the app on this thread as well as via cmd command. In both scenarios the phone goes into continuos reboot cycle (every 1 sec). I'm able to boot into fastboot (it says Fastboot on the screen) by pressing and holding the power+volume up button.
I've tried flashing twrp or stock room with no success. Every time i try to flash something it says:
C:\Android>fastboot flash recovery twrp.img
< waiting for device >
target reported max download size of 536870912 bytes
sending 'recovery' (28144 KB)...
OKAY [ 0.808s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 0.836s
C:\Android>
Any advise would be greatly appreciated!
Got it working again by using the following commands while in fastboot mode:
"fastboot continue"
Thanks to below thread.
http://forum.xda-developers.com/oneplus-2/help/boot-locked-bootloader-installing-twrp-t3229828
I'm having issues with my recovery after flashing the OOS 3.0 to the phone. My phone is working but when i boot into recovery, it stays on the page saying 1+ powered by android. Anyone else have this issue, or any ways to fix it.
I also tried re-flashing twrp, but i get "FAILED (Remote: dtb not found)" when i try to boot the recovery image.
FireForged said:
I'm having issues with my recovery after flashing the OOS 3.0 to the phone. My phone is working but when i boot into recovery, it stays on the page saying 1+ powered by android. Anyone else have this issue, or any ways to fix it.
I also tried re-flashing twrp, but i get "FAILED (Remote: dtb not found)" when i try to boot the recovery image.
Click to expand...
Click to collapse
u need modified twrp, here is the link: https://www.androidfilehost.com/?fid=24459283995297945
flo071 said:
u need modified twrp, here is the link: https://www.androidfilehost.com/?fid=24459283995297945
Click to expand...
Click to collapse
After using this twrp, and flashed with cmd: fastboot boot recovery.img, I return in twrp-recovery.
So I restart (with disable and/or not disable to change the recovery). But after that I am in the same situation. It is possible to flash the same twrp for another time but that is not what we want
This even doesn't work when I restart to recovery.
Is there another possible solution?
Thanks in advance.
retaliator said:
After using this twrp, and flashed with cmd: fastboot boot recovery.img, I return in twrp-recovery.
So I restart (with disable and/or not disable to change the recovery). But after that I am in the same situation. It is possible to flash the same twrp for another time but that is not what we want
This even doesn't work when I restart to recovery.
Is there another possible solution?
Thanks in advance.
Click to expand...
Click to collapse
i disabled reflashing the original recovery...whats is asked when you reboot in system...
for me this worked....
Thanks for answering me.
I did also disabling reflashing new recovery when reboot in system.
When reboot in recovery the 1+ logo apearred and nothing happens.
I have the same issue - I can get fastboot and flash recoveries, but the OP2 never gets beyond the boot screen. tried flashing different recoveries, no joy.
---------- Post added at 09:43 PM ---------- Previous post was at 09:02 PM ----------
update - got it working.
steps:
flashed recovery.img in this post.
booted into twrp
flashed oldmodem5.1.1 zip I had on my phone
rebooted into recovery
flashed twrp3.0.2.img
flashed new+modem.zip
flashed exdodus nightly
boom, back in business
you can keep that OOS rubbish
my phone also not going past the 1+ logo screen
as told i downloaded the recovery.img from above
restart my device in fastboot
C:\Users\imran\Downloads>fastboot oem unlock
...
OKAY [ 0.005s]
finished. total time: 0.006s
after this command my device again started n struck at that logo i restart again in fastmode to check
C:\Users\imran\Downloads>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.073s]
finished. total time: 0.074s
please help
Hello, i've the solution
Download the FirstAid :
http://forum.xda-developers.com/devdb/project/dl/?id=16684
- Unzip files
- Boot your phone in Fastboot
- Go to Firstaid_v_2_0 -> Firstaid -> then lunch ' firstaid'
Thanks for the reply..
i run the file but still no use
F:\Firstaid>fastboot oem unlock
...
OKAY [ 0.016s]
finished. total time: 0.016s
F:\Firstaid>fastboot oem device-info
...
(bootloader) Device tampered: true
(bootloader) Device unlocked: false
(bootloader) Device is_verified: false
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
(bootloader) console_locked: 1
(bootloader) exec_console_unconsole: 0
OKAY [ 0.078s]
finished. total time: 0.078s
F:\Firstaid>fastboot flash recovery TWRP.img
target reported max download size of 536870912 bytes
sending 'recovery' (28144 KB)...
OKAY [ 1.047s]
writing 'recovery'...
FAILED (remote: device is locked. Cannot flash images)
finished. total time: 1.063s
NOTE:if i enter command "fastboot continue" my device is getting started...
Try this, I think you bootloader is still locked
fastboot -i 0x2A70 oem unlock-go
Or follow this guide
http://forum.xda-developers.com/oneplus-2/general/guide-make-oneplus-2-adb-devices-t3218332
Sent from my ONE A2003 using Tapatalk
I had this problem and got the recovery working again with the modified version from above. Where did you get this? and what modification was needed? This is very strange. I never had that kind of a problem.
I flashed my phone back from OxygenOS 3 beta to OxygenOS 2.2.1 to get a working phone again and will now try to revert to the normal recovery again. From there I hope to get twrp 3.0.2.0 and cyanogenmod 13 to work.
UPDATE: normal twrp 3.0.2.0 works again. So my steps to recover from a brick with no accessable recovery to a working phone were:
1. flash modified recovery
2. boot into recovery
3. flash latest stable stock rom
4. flash latest stock twrp
Thanks a lot dude it worked for me
Keep up the good work guys.
What I did to get a working recovery:
1. flash modified recovery from first post in this thread with flashing recovery from pc
2. boot into recovery
3. flash latest stable stock rom
4. flash in recovery the latest recovery from first post
5. flash beta version Oxygen3
6. flash again twrp in recovery
7. flash superuser
8. disable replace recovery
All is well done.
Thanks for helping me mates!
I found out that it is enough when you:
1. copy modified recovery from first post in this thread to your phone
2. flash modified recovery from your pc to your phone
3. boot in recovery
4. flash the recovery you copied to your phone in installed recovery
5. restart with disable replace recovery
Thats enough to do the trick.
I am sorry to reply to an old post but I am unsure if other people are still having issues with this like I was. Here is some info from https://twrp.me/devices/oneplustwo.html :
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
---------- Post added at 07:19 AM ---------- Previous post was at 07:18 AM ----------
I am sorry to reply to an old post but I am unsure if other people are still having issues with this like I was. Here is some info from https://twrp.me/devices/oneplustwo.html :
"Note many devices will replace your custom recovery automatically during first boot. To prevent this, use Google to find the proper key combo to enter recovery. After typing fastboot reboot, hold the key combo and boot to TWRP. Once TWRP is booted, TWRP will patch the stock ROM to prevent the stock ROM from replacing TWRP. If you don't follow this step, you will have to repeat the install."
I will update my unbricking process with every attempt
Attempt 1:
Tried to flash grossoshop fastboot rom 17s by manually erasing boot, system, userdata, cache and recovery. Phone doesn't wake up with any. Still responds to ADB and Fastboot commands with no errors
If browsed through adb, system partition only shows two directories lib and lib64
Attempt 2:
Trying to manually flash mbn files present in the official 20s rom of x720. QPST is not recognizing my phone. I have to somehow put the phone into 9008 mode rather than 9025 mode (which is diagnostic)
There are no QPST compatible files around for Le Pro 3. Guess I finally put my 240$ to the trashcan....
Attempt 3:
I tried to flash the mbn, elf and bin files to their corresponding partitions via fastboot, everything went okay with the flashing. Then I flashed the boot.img, stock recovery and splash..... Went okay.
Rebooted my phone into recovery and its still dead. I can only see ADB interface in device manager and device is recognized correctly in adb.
If I power off my phone by pressing both volume buttons + power and then just insert USB cable, I end up in QDLoader 9008 mode. There is still hope if LeEco ever releases service rom for Le Pro 3 just like it released earlier for Le1, Le2, Le Max 2 etc. Leeco.re has all the firmwares except Le Pro 3.
Flagship my ass, LeEco ripped us off with its amazing chinese U-turn yet again. There is no hope in unbricking the phone unless I get QFill factory service rom meant to be compatible with QPST flasher.
Attempt 4:
Finally found the unbrick service rom which is to be flashed with FlashOne program but turns out the file is incomplete.
Ref Thread: http://www.leeco.re/topic/1906-helpx720-bricked/#comment-33155
I charged my x720 last night (just 10 hrs ago), drove to office with battery last known at 87% just 30 minutes ago.
I took it out of my pocket, sent a couple of text msgs, put it on my office table. Now all of a sudden phone is black, no display, no sign of life except short two vibrations everytime I try to turn it on. I have no idea what has just happened. Still got 6 hrs to stay at office then to home where I might try to charge/put phone to PC and check....
I literally have no idea what just happened.
I'm on CM13 by Team Superluminal and never had any problems like this in the past....
I'll update what was the problem once I get home and thoroughly check my phone :/
Click to expand...
Click to collapse
leave power button and vol down pressed for some time........ it's not the normal waiting time....... just leave it pressed until you get into download mode......
it happened to me with a past custom rom.......... your boot-loader may be locked again......
TURBO
TURBO2012 said:
leave power button and vol down pressed for some time........ it's not the normal waiting time....... just leave it pressed until you get into download mode......
it happened to me with a past custom rom.......... your boot-loader may be locked again......
TURBO
Click to expand...
Click to collapse
Phone vibrates very momentarily after about 10 seconds of holding power button and then vibrates like that every 10 seconds if I keep power button pressed.
I connected it to my Computer and it shows up as QUSB_BULK in device manager. Looks like my device is bricked until LeEco releases QFIL files for Le Pro3. I already have installed Qualcomm QDLoader 9008 drivers.
I am leaving this phone on charger overnight and will check if Battery really was depleted this fast in-case phone lives up. Otherwise its a sad story until LeEco releases QFIL files.
Update # 2
I managed to connect my phone stable with Computer without any stupid black rebooting.
I'm able to see my device in ADB under recovery, and ADB under composite interface and even I can issue ADB Reboot Bootloader command to take it to fastboot.
If I just flash TWRP, it flashes successfully but stays black. Even if I boot recovery image, it reboots into composite interface instead.
Next stop: Grossoshop fastboot rom. Im downloading it right now from https://mega.nz/#!VEM1QIYL!HwT9hk7-GA6KZBTRMv0IQ9kleYaG-el63UF21S6P0us
I REALLY REALLY REALLY HOPE IT WORKS. Phone died on me while on nearly full battery so if it stayed on during whole day it still would have half the juice left to be flashed in fastboot. I don't know if the phone is recharging on adapter or not.
Code:
D:\ADB>adb devices
List of devices attached
50a2127e recovery
D:\ADB>adb reboot bootloader
D:\ADB>adb devices
List of devices attached
D:\ADB>fastboot devices
50a2127e fastboot
D:\ADB>fastboot flash recovery lepro3_twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (47052 KB)...
OKAY [ 1.313s]
writing 'recovery'...
OKAY [ 0.328s]
finished. total time: 1.641s
D:\ADB>fastboot boot lepro3_twrp.img
downloading 'boot.img'...
OKAY [ 1.331s]
booting...
OKAY [ 0.344s]
finished. total time: 1.675s
D:\ADB>adb reboot -p
D:\ADB>adb devices
List of devices attached
50a2127e device
D:\ADB>adb reboot recovery
D:\ADB>adb reboot bootloader
D:\ADB>fastboot devices
50a2127e fastboot
D:\ADB>fastboot oem device-info
...
(bootloader) Device product name: [le_zl1_whole_netcom]
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.078s]
finished. total time: 0.078s
D:\ADB>
Update # 3 Phone is still in coma after flashing Grossoshop 17s rom via fastboot
Incomplete log since the batch file window can't be maximized or scrolled
Code:
*****
**********************************************************************
***** FLASH SYSTEM *****
**********************************************************************
target reported max download size of 536870912 bytes
erasing 'system'...
OKAY [ 0.000s]
sending sparse 'system' (487311 KB)...
OKAY [ 14.516s]
writing 'system'...
OKAY [ 9.544s]
sending sparse 'system' (518775 KB)...
OKAY [ 14.934s]
writing 'system'...
OKAY [ 7.324s]
sending sparse 'system' (524287 KB)...
OKAY [ 15.657s]
writing 'system'...
OKAY [ 5.031s]
sending sparse 'system' (524284 KB)...
OKAY [ 15.755s]
writing 'system'...
OKAY [ 4.486s]
sending sparse 'system' (500922 KB)...
OKAY [ 15.109s]
writing 'system'...
OKAY [ 7.818s]
sending sparse 'system' (484095 KB)...
OKAY [ 14.501s]
writing 'system'...
OKAY [ 89.072s]
finished. total time: 213.780s
**********************************************************************
***** FLASH KERNEL *****
**********************************************************************
target reported max download size of 536870912 bytes
sending 'boot' (35764 KB)...
OKAY [ 1.016s]
writing 'boot'...
OKAY [ 0.234s]
finished. total time: 1.266s
**********************************************************************
***** FLASH TWRP *****
**********************************************************************
target reported max download size of 536870912 bytes
sending 'recovery' (48272 KB)...
OKAY [ 1.344s]
writing 'recovery'...
OKAY [ 0.344s]
finished. total time: 1.687s
**********************************************************************
***** REBOOT RECOVERY *****
**********************************************************************
-- If process was OKAY.....
-- Press any Key to start Recovery then.....
1. Wipe DATA, CACHE and DALVIK CACHE for new rom installation.....
2. Wipe CACHE and DALVIK CACHE if you are updating BB72 rom.....
3. Restart at the end of the process.....
-- First boot takes long.....
D:\ADB\GSLEPRO3\18S>
Update # 4:
Phone is still dead, only recognizeable through ADB, Fastboot, QDLoader 9008. Screen never comes alive, only the vibrator gives the sign of life if not for the device Manager.
I managed to flash the mbn, elf and bin files to corresponding parittions with no errors, then I flashed official boot.img, splash.img and stock recovery but upon reboot, phone is still dead.
Dang it man. I in the same boat. I can get to the fastboot and that is it. If i try to boot recovery it flashes the recovery screen and then goes back... im so dumb for even trying to unlock and flash a rom on this thing...
Same here - qdload 9008 mode and no qfil compatible rom pack from LeEco. Relying blindly on them releasing the files sometime in the future seems like a lost cause to me.
coolmaster121 said:
Dang it man. I in the same boat. I can get to the fastboot and that is it. If i try to boot recovery it flashes the recovery screen and then goes back... im so dumb for even trying to unlock and flash a rom on this thing...
Click to expand...
Click to collapse
I am out and have OmniRom installed atm. Thank your XDA!
In case this helps you guys fix it:
https://forum.xda-developers.com/showpost.php?p=71704244&postcount=595
coolmaster121 said:
I am out and have OmniRom installed atm. Thank your XDA!
In case this helps you guys fix it:
https://forum.xda-developers.com/showpost.php?p=71704244&postcount=595
Click to expand...
Click to collapse
Your case was different. At least ur phone showed signs of life by momentarily showing u the recovery screen. My phone doesn't live up at all not even. LED notification light or screen. Just fastboot or ADB or QDLoader.....
Had a similar effect yet from different reason. I dropped my phone in salty water (I thought it would survive as it did in fresh water for a minute LoL) and it won't turn off but just in a boot loop to Recovery.
Then the screen died, won't turn on at all, phone vibrates once or twice every restart infinitely. The battery drained out and I put the phone in a bucket of rice for a day and voila it turned on again. I was able to relock the bootloader and sent it back for repair (with fingers crossed hoping they won't dismantle the phone and find water traces inside =D). They replaced it with new one and so I am happy camper again. =D
Joms_US said:
Had a similar effect yet from different reason. I dropped my phone in salty water (I thought it would survive as it did in fresh water for a minute LoL) and it won't turn off but just in a boot loop to Recovery.
Then the screen died, won't turn on at all, phone vibrates once or twice every restart infinitely. The battery drained out and I put the phone in a bucket of rice for a day and voila it turned on again. I was able to relock the bootloader and sent it back for repair (with fingers crossed hoping they won't dismantle the phone and find water traces inside =D). They replaced it with new one and so I am happy camper again. =D
Click to expand...
Click to collapse
I just happened to buy the phone and get it shipped to wrong country where Leeco support doesn't exist neigther the country supports such repair correspondance. Customs here will charge me around 150$ when I will recieve my phone after repair, moreover my Leeco warranty isnt covered because I didnt buy from their official store (rather a chinese store through a friend and get it shipped to me). So Im left out in the dark waiting for the on-shelf recovery measures.
Man, sucks when we break it this much, huh? I just tried to remove the encryption (was asking for password) after having gotten encrypted from flashing TARS 21s on my 727. Now I can fastboot and see recovery but I can't push any files because adb says it's "unauthorized".... I can't authorise because I have no OS!!! No files either obviously, I just wiped the storage entirely to remove that encryption. Anybody have any ideas on this one? Going to have use a Walmart burner for a little while until I can get a usb-c OTG drive. That's the only thing I can think of since I CAN enter recovery/fastboot flash things
benjmiester said:
Man, sucks when we break it this much, huh? I just tried to remove the encryption (was asking for password) after having gotten encrypted from flashing TARS 21s on my 727. Now I can fastboot and see recovery but I can't push any files because adb says it's "unauthorized".... I can't authorise because I have no OS!!! No files either obviously, I just wiped the storage entirely to remove that encryption. Anybody have any ideas on this one? Going to have use a Walmart burner for a little while until I can get a usb-c OTG drive. That's the only thing I can think of since I CAN enter recovery/fastboot flash things
Click to expand...
Click to collapse
Do you have twrp installed? And an OTG?
benjmiester said:
Man, sucks when we break it this much, huh? I just tried to remove the encryption (was asking for password) after having gotten encrypted from flashing TARS 21s on my 727. Now I can fastboot and see recovery but I can't push any files because adb says it's "unauthorized".... I can't authorise because I have no OS!!! No files either obviously, I just wiped the storage entirely to remove that encryption. Anybody have any ideas on this one? Going to have use a Walmart burner for a little while until I can get a usb-c OTG drive. That's the only thing I can think of since I CAN enter recovery/fastboot flash things
Click to expand...
Click to collapse
You can try "adb sideload" in twrp usually it bypasses "unauthorized" status and flashes away directly.
ivangotoy said:
You can try "adb sideload" in twrp usually it bypasses "unauthorized" status and flashes away directly.
Click to expand...
Click to collapse
That actually did the trick, thanks! I'd be really screwed without TWRP booting.
We, in the qh-usb boat, are rly screwed right now
benjmiester said:
That actually did the trick, thanks! I'd be really screwed without TWRP booting.
Click to expand...
Click to collapse
I am screwed. Can yu explain how this adb sideload worked?
zman123 said:
I am screwed. Can yu explain how this adb sideload worked?
Click to expand...
Click to collapse
Sorry I didn't see this earlier. I was lucky in that my phone would still work in fastboot mode with my computer even though adb push would not so I couldn't push files to flash.
If you can get to twrp, or fastboot (volume DOWN + power, hold until it boots to fastboot screen) then you can open fastboot command window on PC, type fastboot devices and make sure it shows a device is attached and recognized. If so, flash twrp with command fastboot flash boot twrp.zip (or whatever you name it). Once in twrp, you can go to sideload option, have to toggle it on in twrp and it will say ready (waiting to accept zip over adb). Then have rom zip and gapps zip in adb/fastboot folder on pc.
Use command adb sideload rom.zip then same for gapps.zip. It will show progress on the phone if working.
benjmiester said:
Sorry I didn't see this earlier. I was lucky in that my phone would still work in fastboot mode with my computer even though adb push would not so I couldn't push files to flash.
If you can get to twrp, or fastboot (volume DOWN + power, hold until it boots to fastboot screen) then you can open fastboot command window on PC, type fastboot devices and make sure it shows a device is attached and recognized. If so, flash twrp with command fastboot flash boot twrp.zip (or whatever you name it). Once in twrp, you can go to sideload option, have to toggle it on in twrp and it will say ready (waiting to accept zip over adb). Then have rom zip and gapps zip in adb/fastboot folder on pc.
Use command adb sideload rom.zip then same for gapps.zip. It will show progress on the phone if working.
Click to expand...
Click to collapse
Thank you! I was finally able to get sideload to work. I was using Darkobas recovery and that caused issues. Flashing normal TWRP worked. I was able to get back to stock via recovery so know I am trying to fix the prolem that started this mess... Google play store wont work on cellular..... most annoying problem in the world!
Hi so I want to revert back to factory image, however I keep on getting "file not found" or "target didn't report max-download-size" error. I already installed the drivers, unlock the bootloader and when I check fastboot devices, the phone shows up.
Any help would be greatly appreciated.
Ive had similar performance within the bootloader menu. Some things to check on your pc verify that the phone is showing up in device manager as essential phone fastboot. You may need to restart the pc or change usb port to get it to properly communicate.
You should also be able to revert to the factory image through the normal recovery; instead of attempting to install twrp to flash the stock image (sounds like what you might be trying to do your post is a little unclear) you can always just run the normal essential recovery partition and then use adb sideload from there to restore the factory image.
From essential's website
https://www.essential.com/developer/beta-builds
Your device is now in Recovery mode. An Android logo with red exclamation mark should appear on screen.
Hold the Power button, then press the Volume-Up button one time. When the menu appears, select Apply update from ADB.
Run the following command: adb devices. Then check that your device shows up with “sideload” next to its name
Run the following command: adb sideload ota_file.zip where ota_file.zip is the name of the file you downloaded and verified
Once the update finishes, select Reboot system now to reboot your phone
I tried this and it seems to work great but if I select slot b it will not boot properly. Has anyone else tried this?
I don't believe that the Essential bath file flashes both slots. I had to use the BTS file to fix my phone.
Halp
Zargone said:
I tried this and it seems to work great but if I select slot b it will not boot properly. Has anyone else tried this?
I don't believe that the Essential bath file flashes both slots. I had to use the BTS file to fix my phone.
Click to expand...
Click to collapse
Did you manage to successfully flash the stock image? If yes, would you kindly provide the steps that you performed? Im trying to get back to Oreo from Android P Beta so that I can have my unit replaced
I just got one of these phones as payment for some consulting. I booted into fastboot mode and checked fastboot devices before agreeing on the deal and I see the device listed. I get home and start to unlock bootloader etc...only to continue getting this error...
FAILED (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.005s
This was a simple process on my Huawei. WHats going on here does anyone know?
lolifer said:
I just got one of these phones as payment for some consulting. I booted into fastboot mode and checked fastboot devices before agreeing on the deal and I see the device listed. I get home and start to unlock bootloader etc...only to continue getting this error...
FAILED (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.005s
This was a simple process on my Huawei. WHats going on here does anyone know?
Click to expand...
Click to collapse
Have you enabled oem unlock in developer options?
I cannot boot into android to check. I literally got this phone a couple hours ago. Is there anyway to enable it via fastboot?
The guy that I got it from told me it was stuck on boot logo. I simply hooked it up to laptop, installed adb/fastboot, and drivers and booted to fastboot and ran fastboot devices which gave me the serial #. So i figured I would be able to restore it no matter as long as fastboot could see the device.
lolifer said:
I cannot boot into android to check. I literally got this phone a couple hours ago. Is there anyway to enable it via fastboot?
The guy that I got it from told me it was stuck on boot logo. I simply hooked it up to laptop, installed adb/fastboot, and drivers and booted to fastboot and ran fastboot devices which gave me the serial #. So i figured I would be able to restore it no matter as long as fastboot could see the device.
Click to expand...
Click to collapse
There is no way to unlock bootloader if you can't enable oem unlock option in developer menu.
You can try to boot to recovery and do a factory reset,or try switching slots a/b and see if you can boot ur phone.
gm007 said:
There is no way to unlock bootloader if you can't enable oem unlock option in developer menu.
You can try to boot to recovery and do a factory reset,or try switching slots a/b and see if you can boot ur phone.
Click to expand...
Click to collapse
i already did those options. each time FB fails to write because of locked state. I cannot access recovery. I tried to> fastboot boot boot.img and this is what I get:
platform-tools_r28.0.1-windows\platform-tools>fastboot boot boot.img
Downloading 'boot.img' OKAY [ 0.935s]
booting FAILED (remote: 'unknown command')
Finished. Total time: 0.962s
EDIT**** Just specified a USB device using fastboot -s. Looks like the partitions were created but just couldnt wipe userdata. What is SuperBlocks backup?
C:\Users\Leebo\Downloads\platform-tools_r28.0.1-windows\platform-tools>fastboot -s PM1LHMD762601033 -w
mke2fs 1.44.3 (10-July-2018)
Creating filesystem with 26768215 4k blocks and 6692864 inodes
Filesystem UUID: 672d99c8-c617-11e8-8c24-45c467b7c233
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
Erasing 'userdata' FAILED (remote: 'Erase is not allowed in Lock State')
Finished. Total time: 1.068s
lolifer said:
i already did those options. each time FB fails to write because of locked state. I cannot access recovery. I tried to> fastboot boot boot.img and this is what I get:
platform-tools_r28.0.1-windows\platform-tools>fastboot boot boot.img
Downloading 'boot.img' OKAY [ 0.935s]
booting FAILED (remote: 'unknown command')
Finished. Total time: 0.962s
EDIT**** Just specified a USB device using fastboot -s. Looks like the partitions were created but just couldnt wipe userdata. What is SuperBlocks backup?
C:\Users\Leebo\Downloads\platform-tools_r28.0.1-windows\platform-tools>fastboot -s PM1LHMD762601033 -w
mke2fs 1.44.3 (10-July-2018)
Creating filesystem with 26768215 4k blocks and 6692864 inodes
Filesystem UUID: 672d99c8-c617-11e8-8c24-45c467b7c233
Superblock backups stored on blocks:
32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,
4096000, 7962624, 11239424, 20480000, 23887872
Allocating group tables: done
Writing inode tables: done
Creating journal (131072 blocks): done
Writing superblocks and filesystem accounting information: done
Erasing 'userdata' FAILED (remote: 'Erase is not allowed in Lock State')
Finished. Total time: 1.068s
Click to expand...
Click to collapse
You will need to side load the OTA.
You cannot flash.
tech_head said:
You will need to side load the OTA.
You cannot flash.
Click to expand...
Click to collapse
But I cannot get adb to work, only fastboot. I install essentials ADB, download Essential drivers. Am I missing something? In Device Manager while in fastboot it says Essential Fastboot Phone.
Im starting to think the original owner must have had twrp and installed OTA update without going back to stock recovery. If I were to assume this the case, what would be the next step to recover?
tech_head said:
You will need to side load the OTA.
You cannot flash.
Click to expand...
Click to collapse
How do I go about sideloading from fastboot?
Don't know. My phone is rooted and bl unlocked
lolifer said:
How do I go about sideloading from fastboot?
Click to expand...
Click to collapse
Pretty sure you cannot sideload with fastboot. Anything flashing related in the bootloader with fastboot requires an unlocked bootloader. If twrp was previously installed than he would unlocked the bootloader at some point. What happens when you boot to recovery from the bootloader? Or the hardware buttons?
galakanokis said:
Pretty sure you cannot sideload with fastboot. Anything flashing related in the bootloader with fastboot requires an unlocked bootloader. If twrp was previously installed than he would unlocked the bootloader at some point. What happens when you boot to recovery from the bootloader? Or the hardware buttons?
Click to expand...
Click to collapse
when I boot into recovery the phone simply restarts and gets stuck on the boot screen "powered by Android" screen. What do you mean the hardware buttons? VOL UP+POwer?
lolifer said:
when I boot into recovery the phone simply restarts and gets stuck on the boot screen "powered by Android" screen. What do you mean the hardware buttons? VOL UP+POwer?
Click to expand...
Click to collapse
Yeah, was just curious about what you were seeing in recovery. If your bootloader is locked and you have somehow lost recovery I am not to sure what else you can do. You said you switched slots and still were unable to boot to recovery?
lolifer said:
when I boot into recovery the phone simply restarts and gets stuck on the boot screen "powered by Android" screen. What do you mean the hardware buttons? VOL UP+POwer?
Click to expand...
Click to collapse
Ok...
Let's try this thing...
Grab the fastboot images from the Essential website...
Download and unzip it...
Try flashing boot to it's partition...
Theory- signed by the OEM?
Once you can get to recovery... You can use ADB
rignfool said:
Ok...
Let's try this thing...
Grab the fastboot images from the Essential website...
Download and unzip it...
Try flashing boot to it's partition...
Theory- signed by the OEM?
Once you can get to recovery... You can use ADB
Click to expand...
Click to collapse
...downloading images for PIE now.
EDIT**Here is the fastboot result..
C:\Users\Administrator\Downloads\PH1-Images-PPR1.180610.091\PH1-Images-PPR1.180610.091>fastboot flash boot boot.img
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'boot_b' (20769 KB)...
OKAY [ 0.830s]
writing 'boot_b'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.845s
lolifer said:
...downloading images for PIE now.
EDIT**Here is the fastboot result..
C:\Users\Administrator\Downloads\PH1-Images-PPR1.180610.091\PH1-Images-PPR1.180610.091>fastboot flash boot boot.img
< waiting for any device >
target reported max download size of 536870912 bytes
sending 'boot_b' (20769 KB)...
OKAY [ 0.830s]
writing 'boot_b'...
FAILED (remote: Flashing is not allowed in Lock State)
finished. total time: 0.845s
Click to expand...
Click to collapse
Damn...
I woulda thought for sure you could flash signed image...
just fired up miraclebox and did a read info under the qualcomm section and this was my result.
Starting..
Waiting for Phone...
Phone Found..
version:0.5
unlocked:no
off-mode-charge:1
charger-screen-enabled:1
battery-soc-ok:yes
battery-voltage:3721
version-baseband:2.0.c4-M1.2
version-bootloader:mata-4452425
variant:
partition-type:userdata:ext4
partition-size:userdata: 0x1987357000
partition-type:system_b:ext4
partition-size:system_b: 0x100000000
has-slot:nvdef:yes
has-slot:dsp:yes
has-slot:vendor:yes
has-slot:devcfg:yes
has-slot:cmnlib64:yes
has-slot:cmnlib:yes
has-slot:boot:yes
has-slot:keymaster:yes
has-slot:abl:yes
has-slot:mdtp:yes
has-slot:mdtpsecapp:yes
has-slot:bluetooth:yes
has-slot:modem:yes
has-slotmic:yes
has-slot:hyp:yes
has-slot:tz:yes
has-slot:rpm:yes
has-slot:xbl:yes
has-slot:system:yes
current-slot:_b
slot-retry-count:_b:0
slot-unbootable:_b:no
slot-successful:_b:no
slot-retry-count:_a:0
slot-unbootable:_a:yes
slot-successful:_a:no
slot-count:2
slot-suffixes:_a,_b,
secure:yes
serialnoM1LHMD762601033
product:Mata
max-download-size:0x20000000
kernel:uefi
all:
0.011s
>>Process Done...
Folks,
I have a ZF2L aka ZE551KL which is currently in a bootloop. Why that happened I have no idea as I have not dinked with the stock rom or for that matter even unlocked the bootloader.
A little bit of history, over the weekend, I had plugged in my phone to charge it and then when it completed charging I unplugged it and then tried to reboot it. That was the last time I had it working. After the reboot the phone has been in a bootloop ever since.
In order to try to recover from the above, I started reading a bit on what to do and I came across the postings that mentioned the bootloader has to be dropped to the Lollipop level so that it can be unlocked and then the recovery can be upgraded to Marshmallow. While trying to get all of that done, I have ended up here.
I "think" I have unlocked the bootloader using the command
echo -ne "\x01" | dd obs=1 count=1 seek=16 of=/dev/block/bootdevice/by-name/devinfo
I ran the above command directly on the phone via the terminal in TWRP. I booted into TWRP using the following fastboot command
fastboot boot twrp-3.2.3-0-Z00T.img
Running the fastboot command, fastboot oem device-info gives me the following output
C:\Users\home\android\platform-tools\images>fastboot oem device-info
(bootloader) Device unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Display panel:
OKAY [ 0.016s]
Finished. Total time: 0.016s
However when I try to flash a new recovery TWRP-3.2.3-0-Z00T I get the following error
C:\Users\home\android\platform-tools\images>fastboot flash recovery twrp-3.2.3-0-Z00T.img
Sending 'recovery' (29856 KB) OKAY [ 1.342s]
Writing 'recovery' FAILED (remote: 'Permission denied, phone is protected')
Finished. Total time: 1.388s
I'm a little lost on what's going on. The device-info tells me the bootloader is unlocked, however it appears that something else is still locked which is not allowing the recovery to get flashed.
The stock recovery I was on before this all started was asus/WW_Z00T/ASUS_Z00T/6.0.1/MMB29P/WW_user_21.40.1220.2181_20170805. The recovery I currently have is LRX22G.WW_user_1.16.40.763_20151201
Any pointers on what I could do to get this resolved would be helpful?
hi if ur bootloader is unlocked, u an do a fresh flash of all d partitions as sometimes things get messed up on its own.
download firmware from https://drive.google.com/file/d/0B43Ue6xY9MmdN0UzWVRFcno4N0U/view and extract, then run flashall.cmd (in fastboot mode i.e. pwr and vol up)
u should finish without any hiccups. u will lose twrp though
tried on mine it woks. but google frp may be active so keep ur email n pass handy. m not responsible for any damages though ...