Hello people I actually Hardbricked my one plus two can't even say a hard brick but main problem is phone boots into the system but nothing is visible not even recovery is visible where as the boot logo and Fastboot mode page is visible... The current situation is :-
1. FASTBOOT ACCESSIBLE
2. BOOTLOADER LOCKED( can't unlock it because oem unlock is disabled)
3. Phone boots into system.. Internal storage is visible when connected to pc and can take screen shots using volume keys n viewed those screen shots from internal storage which shows that phone is currently on welcome page..
4. Phone vibrates when setting it to vibrate mode using volume keys
5.Tried qualcomm recovery tool n all 4 methods (except method 2 because link is broken) form @Naman Bhalla from one plus form mega guide but didn't work for me
6. Waiting for help
I would request developers or anyone how knows solution to please help me out...
Hi
Try this...
1. Reboot the phone to the bootloader (fastboot)
2. Connect phone to PC an run command
Code:
fastboot devices
to see if detected.
3. Run this command to wipe data/factory reset
Code:
fastboot -w
Hope it helped
Sent from my ONE A2005 using Tapatalk
Brandon Indar said:
Hi
Try this...
1. Reboot the phone to the bootloader (fastboot)
2. Connect phone to PC an run command
Code:
fastboot devices
to see if detected.
3. Run this command to wipe data/factory reset
Code:
fastboot -w
Hope it helped
Sent from my ONE A2005 using Tapatalk
Click to expand...
Click to collapse
Will try this n will get back to you.. ?
Brandon Indar said:
Hi
Try this...
1. Reboot the phone to the bootloader (fastboot)
2. Connect phone to PC an run command
Code:
fastboot devices
to see if detected.
3. Run this command to wipe data/factory reset
Code:
fastboot -w
Hope it helped
Sent from my ONE A2005 using Tapatalk
Click to expand...
Click to collapse
Didnt work for me ..m getting the error..
OK u say that u can boot into system but nothing is visible...if u boot into system an connect to pc, do u have access to adb?
Btw have u ever rooted or flash custom recovery like twrp before?
Sent from my ONE A2005 using Tapatalk
Brandon Indar said:
OK u say that u can boot into system but nothing is visible...if u boot into system an connect to pc, do u have access to adb?
Btw have u ever rooted or flash custom recovery like twrp before?
Click to expand...
Click to collapse
I haven't rooted it no custom recovery.. When typed adb devices it shows
List of adb devices
(blank)
I can access internal storage once connected with pc..
U can take screenshots an view it on ur pc?
If so u can try navigate to settings an enable OEM unlock by viewing the screenshots[emoji3]
Songs weird but that's only way since u hav no adb access[emoji13]
Sent from my ONE A2005 using Tapatalk
Brandon Indar said:
U can take screenshots an view it on ur pc?
If so u can try navigate to settings an enable OEM unlock by viewing the screenshots[emoji3]
Songs weird but that's only way since u hav no adb[emoji13]
Click to expand...
Click to collapse
Buddy since I tried to flash using qualcomm tools it flashed a new system ( with no display) so now it's currently on the welcome page n I can't go ahead.. I can't navigate using touch because screen is blank..
Just wanted to ask if I flash a rom with oem unlock enabled before hand then will I be able to unlock bootloader?
Have u tried this http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
There's not much u can do since u don't have adb access and ur bootloader is locked.
All I can say is to try different recovery packages an hope it work [emoji106]
Sent from my ONE A2005 using Tapatalk
Manish Salian said:
Just wanted to ask if I flash a rom with oem unlock enabled before hand then will I be able to unlock bootloader?
Click to expand...
Click to collapse
Yes...
But normally any rom u flash, u will still have to go in settings an enable it.
The only way u can flash rom is via the recovery tool. The recovery tool also installs twrp recovery. Since ur bootloader is locked it probably brick the recovery.
If u get a rom to boot successfully proceed in unlocking the bootloader.
Sent from my ONE A2005 using Tapatalk
Brandon Indar said:
Have u tried this http://forum.xda-developers.com/oneplus-2/general/oneplus-solution-hard-bricked-device-t3183449
Click to expand...
Click to collapse
I have tried this but same story.. It boots but display isn't visible.. ?
Manish Salian said:
I have tried this but same story.. It boots but display isn't visible.. ?
Click to expand...
Click to collapse
Well lastly try booting into fastboot then run the command " fastboot continue " and see if u can boot into recovery.
If not well u will have to replace the system.img and boot.img in the recovery tool with another rom.
Sent from my ONE A2005 using Tapatalk
Brandon Indar said:
Well lastly try booting into fastboot then run the command " fastboot continue " and see if u can boot into recovery.
If not well u will have to replace the system.img and boot.img in the recovery tool with another rom.
Click to expand...
Click to collapse
Yeah will try to replace system n boot.img with different roms.. Will let you know..
Check out this: http://android.stackexchange.com/questions/164052/no-os-installed-stock-recovery-oneplus-2
Sent from my ONE A2005 using Tapatalk
Brandon Indar said:
Check out this: http://android.stackexchange.com/questions/164052/no-os-installed-stock-recovery-oneplus-2
Click to expand...
Click to collapse
But buddy his bootloader is unlocked where as mine is locked :crying:
Did you wipe data partition? No one told you that before, so I'm curious. Do it from recovery (you didn't tell your recovery is dead, so...).
Had this issue, when I forgot to wipe data after switching roms.
turai said:
Did you wipe data partition? No one told you that before, so I'm curious. Do it from recovery (you didn't tell your recovery is dead, so...).
Had this issue, when I forgot to wipe data after switching roms.
Click to expand...
Click to collapse
Buddy when I boot into recovery nothing is visible but it vibrates if I use volume or power keys
Manish Salian said:
But buddy his bootloader is unlocked where as mine is locked :crying:
Click to expand...
Click to collapse
No download the zip and use the system.img from it in the link and replace it in the recovery tool...Ik fastboot is locked.
Here is direct link https://mega.nz/#!itR00ZaI!gJ6T0jgqfZaIF9NLlCzWj4LIGMMhCw8m8owFdeB_2B4
Sent from my ONE A2005 using Tapatalk
Brandon Indar said:
No download the zip and use the system.img from it in the link and replace it in the recovery tool...Ik fastboot is locked.
Click to expand...
Click to collapse
Okaay will try it n will let you know..
Manish Salian said:
Buddy when I boot into recovery nothing is visible but it vibrates if I use volume or power keys
Click to expand...
Click to collapse
If recovery does the same, this is a hardware issue.
I guess you are from India, so take your device to a service center. In case your warranty has expired, go for the 3T, replacing the mainboard does not worth the money.
Related
I just used toolkit to root new nexus clicked option 8 one click. Everything went fine it rebooted into Google and now its stuck. USB debugging is no longer active, how can I push a file to phone to get boot. Please help. Is there a free node channel for N4 discussion. Thanks.
Sent from my SGH-T959V using xda app-developers app
anoymonos said:
I just used toolkit to root new nexus clicked option 8 one click. Everything went fine it rebooted into Google and now its stuck. USB debugging is no longer active, how can I push a file to phone to get boot. Please help. Is there a free node channel for N4 discussion. Thanks.
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
Hold the power for about 10 seconds to turn it off, wait 10 seconds and press volume down and power button to get into the bootloader. If you have a windows pc try this link http://download.chainfire.eu/297/CF-Root/CF-Auto-Root/CF-Auto-Root-mako-occam-nexus4.zip to get root. Unzip the downloaded file and click root-windows. That should work.
----- CF-Auto-Root-mako-occam-nexus4 -----
Please make sure your device is in bootloader/fastboot mode before continuing.
***WARNING*** ALL YOUR DATA *MAY* BE WIPED ! ***WARNING***
We are going to run the "OEM UNLOCK" command on your device. If your device
was not previously unlocked, this will wipe all your data !
After the unlock, CF-Auto-Root will boot. You should see a big red Android
on your device's screen.
Press Ctrl+C followed by Y to cancel !
Press any key to continue . . .
The system cannot find the path specified.
The system cannot find the path specified.
It may take a minute or so for the red Android to appear. If it doesn't show up
at all, there may be a problem.
Press any key to continue . . .
gee2012 said:
Hold the power for about 10 seconds to turn it off, wait 10 seconds and press volume down and power button to get into the bootloader. If you have a windows pc try this link http://download.chainfire.eu/297/CF-Root/CF-Auto-Root/CF-Auto-Root-mako-occam-nexus4.zip to get root. Unzip the downloaded file and click root-windows. That should work.
Click to expand...
Click to collapse
any other suggestions
anoymonos said:
----- CF-Auto-Root-mako-occam-nexus4 -----
Please make sure your device is in bootloader/fastboot mode before continuing.
***WARNING*** ALL YOUR DATA *MAY* BE WIPED ! ***WARNING***
We are going to run the "OEM UNLOCK" command on your device. If your device
was not previously unlocked, this will wipe all your data !
After the unlock, CF-Auto-Root will boot. You should see a big red Android
on your device's screen.
Press Ctrl+C followed by Y to cancel !
Press any key to continue . . .
The system cannot find the path specified.
The system cannot find the path specified.
It may take a minute or so for the red Android to appear. If it doesn't show up
at all, there may be a problem.
Press any key to continue . . .
any other suggestions
Click to expand...
Click to collapse
That is what you are supposed to see, don`t worry about it and just press any button. If the bootloader is allreay unlocked you will not loose data. And don`t use Toolkits anymore
gee2012 said:
That is what you are supposed to see, don`t worry about it and just press any button. If the bootloader is allreay unlocked you will not loose data. And don`t use Toolkits anymore
Click to expand...
Click to collapse
ya but no red andriod appeared it just stayed in fastboot mode
anoymonos said:
ya but no red andriod appeared it just stayed in fastboot mode
Click to expand...
Click to collapse
Close CF Auto root, disconnect and reconnect usb and open CF Auto root again and try again.
If that doesn`t work flash TWRP recovery from here http://techerrata.com/file/twrp2/mako/openrecovery-twrp-2.5.0.0-mako.img in fastboot and flash this superSU zip http://download.chainfire.eu/331/SuperSU/UPDATE-SuperSU-v1.32.zip in recovery
I tried that and nada.I even try to flash factory img through fast boot and get error
Sent from my SGH-T959V using xda app-developers app
anoymonos said:
I tried that and nada.I even try to flash factory img through fast boot and get error
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
Do a data factory reset in recovery, wipe cache and reboot. And try rooting again after you enabled usb debugging.
anoymonos said:
I tried that and nada.I even try to flash factory img through fast boot and get error
Sent from my SGH-T959V using xda app-developers app
Click to expand...
Click to collapse
Might help to know what error and which img file (specifically), I would just pull down TWRP 2.5.0.0 (specifically for mako):
fastboot flash recovery name-of-recovery.img
Boot into recovery (wipe/format and flash up new rom, etc), or if you instead get an error note the specific error.
PS: If you have no rom/etc due to erasure, you can 'adb push' the zip files to /sdcard while in recovery.
C:\sdk>fastboot flash bootloader-mako-makoz10o.img
unknown partition 'bootloader-mako-makoz10o.img'
error: cannot determine image filename for 'bootloader-mako-makoz10o.img'
C:\sdk>
kbeezie said:
Might help to know what error and which img file (specifically), I would just pull down TWRP 2.5.0.0 (specifically for mako):
fastboot flash recovery name-of-recovery.img
Boot into recovery (wipe/format and flash up new rom, etc), or if you instead get an error note the specific error.
Click to expand...
Click to collapse
anoymonos said:
C:\sdk>fastboot flash bootloader-mako-makoz10o.img
unknown partition 'bootloader-mako-makoz10o.img'
error: cannot determine image filename for 'bootloader-mako-makoz10o.img'
C:\sdk>
Click to expand...
Click to collapse
First off, bootloader isn't a "recovery", second you're missing a parameter
fastboot [action] [partition] [file]
You were basically telling it to flash nothing onto a partition named bootloader-make-makoz10o.img which course doesn't exist.
anoymonos said:
C:\sdk>fastboot flash bootloader-mako-makoz10o.img
unknown partition 'bootloader-mako-makoz10o.img'
error: cannot determine image filename for 'bootloader-mako-makoz10o.img'
C:\sdk>
Click to expand...
Click to collapse
Dude why you are flasing a bootloader!
kbeezie said:
First off, bootloader isn't a "recovery", second you're missing a parameter
fastboot [action] [partition] [file]
You were basically telling it to flash nothing onto a partition named bootloader-make-makoz10o.img which course doesn't exist.
Click to expand...
Click to collapse
i have folled this link and am syuck at flashing bootloader.http://forums.androidcentral.com/ne...3923-guide-nexus-4-factory-image-restore.html
basically all i can access is fastboot
This is why you don't use a bootloader. Just do it the old fashion way.
You don't need to flash a bootloader. Just fastboot flash stock Google images and start over
https://developers.google.com/android/nexus/images#occam
Also please change the title, your phone isn't bricked. You just messed up due to taking a shortcut route aka toolkit.
zephiK said:
This is why you don't use a bootloader. Just do it the old fashion way.
You don't need to flash a bootloader. Just fastboot flash stock Google images and start over
https://developers.google.com/android/nexus/images#occam
Also please change the title, your phone isn't bricked. You just messed up due to taking a shortcut route aka toolkit.
Click to expand...
Click to collapse
thats the problem it wont let me flash anything through fastboot
anoymonos said:
thats the problem it wont let me flash anything through fastboot
Click to expand...
Click to collapse
Do a data factory reset/ wipe cache in recovery and reboot.
anoymonos said:
thats the problem it wont let me flash anything through fastboot
Click to expand...
Click to collapse
You have the proper drivers installed? http://forum.xda-developers.com/showthread.php?t=1996051
gee2012 said:
Do a data factory reset/ wipe cache in recovery and reboot.
Click to expand...
Click to collapse
i dont have a recovery everything got wiped
zephiK said:
You have the proper drivers installed? http://forum.xda-developers.com/showthread.php?t=1996051
Click to expand...
Click to collapse
yes proper drivers installed. Just unrooted and relocked old nexus 4 for return and then tried to root and unlock new one and it **** on me
It probably will if you use the proper syntax since you have to tell it which partition.
If you go and grab the TWRP 2.5.0.0 recovery image from their website for mako, you can use the following
fastboot flash recovery nameofrecovery.img
Making sure there are 4 parts as the word recovery is part of the command.
Sent from my Nexus 7 using XDA Premium HD app
---------- Post added at 11:47 AM ---------- Previous post was at 11:45 AM ----------
Thus why you download one and flash. It's nearly impossible to hard brick a Nexus. Just helps not to receive panic. Take a couple breaths and figure out the proper commands.
Sent from my Nexus 7 using XDA Premium HD app
Hi guys !
I need your help for trying to recover my information from my Nexus 4... (Thanks in advance)
First, my N4 is:
With the screen cracked, so, the bottom half of the screen is not responding to any touch
Locked with a lock pattern (and because of the damaged screen, I can't unlock the phone)
With stock Android
With USB debugging on
Not rooted
With no other modification whatsoever (No custom ROM or recovery mode, etc)
First I tried the obvious, I connected the N4 to my computer expecting a miracle; as the phone is locked, and I can't unlock it, ADB just didn't worked.
I also tried sending a .zip thought "adb sideload" (using the stock recovery mode) to delete the files where the lock pattern is, but an "signature verification error" occurred (because the phone is not rooted, I guess). I've tried to delete the files with "adb -d shell" but (obviously) as ADB is not working, a "device not found" error showed up.
So I guess the question here is... What are my options ? Is there any way I can recover my photos and files ?
Thanks in advance!
Try going into recovery and using adb from there. Turn off the phone then turn it boot into the bootloader using volume down and power. Use the volume rockers to scroll and highlight Recovery mode, then use power to select it. Once in recovery press and hold power, then volume up to enter the menu. Then try "adb devices", and if the phone is recognized you can use what you want.
chromium96 said:
Try going into recovery and using adb from there. Turn off the phone then turn it boot into the bootloader using volume down and power. Use the volume rockers to scroll and highlight Recovery mode, then use power to select it. Once in recovery press and hold power, then volume up to enter the menu. Then try "adb devices", and if the phone is recognized you can use what you want.
Click to expand...
Click to collapse
Hi chromium96 !
That didn't work.. :S
Any other idea ?
Thanks for replying !
Flash a custom recovery and boot into it... I think custom recoveries support adb.. If USB debugging is ON and proper drivers are installed on your PC, you can do 'adb pull' for the necessary files
Sent from my Nexus 4 using Tapatalk 4
badhri said:
Flash a custom recovery and boot into it... I think custom recoveries support adb.. If USB debugging is ON and proper drivers are installed on your PC, you can do 'adb pull' for the necessary files
Sent from my Nexus 4 using Tapatalk 4
Click to expand...
Click to collapse
Is that going to delete all my information ?
Thanks !
AlejandroFloresV said:
Is that going to delete all my information ?
Thanks !
Click to expand...
Click to collapse
To flash the recovery you will need to unlock your bootloader which is meant to wipe all your data. However if you flash the recovery right after unlocking the bootloader (no reboot in between) the data should not get wiped.
chromium96 said:
To flash the recovery you will need to unlock your bootloader which is meant to wipe all your data. However if you flash the recovery right after unlocking the bootloader (no reboot in between) the data should not get wiped.
Click to expand...
Click to collapse
I don't know if that's true...
Sent from my Nexus 7 using Tapatalk 4
korockinout13 said:
I don't know if that's true...
Sent from my Nexus 7 using Tapatalk 4
Click to expand...
Click to collapse
It is true. Ive done it successfully on several n4's and its even been talked about a couple times on xda: http://forum.xda-developers.com/showthread.php?t=2266928
Yes.. I have done that too.. It doesn't wipe the data.. Just flash cwm, right after the boot loader unlock..
Sent from my Nexus 4 using Tapatalk 4
Good evening,
I have trying to get my phone working for a few weeks now to no avail. I can access fastboot mode and it recognizes the device but I cannot access recovery mode. The phone is stuck on the logo screen, powered by Android. When I try to boot to recovery mode, it stays on the logo screen. Any advice? I am willing to try anything at this point.
Thank you!
Sent from my A0001 using Tapatalk
When you seeing the dead Android you push and hold power button and press volume+ additionally?
We actually do not have a recovery partition. You want to flash it to your current boot slot.
Do this:
fastboot getvar current-slot
this will return your <letter>
then do
fastboot flash boot_<letter> <filename>.img
You can continue forward.
good luck.
gflexstump said:
We actually do not have a recovery partition. You want to flash it to your current boot slot.
Do this:
fastboot getvar current-slot
this will return your <letter>
then do
fastboot flash boot_<letter> <filename>.img
You can continue forward.
good luck.
Click to expand...
Click to collapse
Thank you.
To clarify, I assume that the letter will be the partition, a or b. What do you refer to with filename? Is that the zip file with the image to flash? Apologies if the answers are obvious. Just learning over here. Thanks again.
Sent from my A0001 using Tapatalk
vergilbt said:
When you seeing the dead Android you push and hold power button and press volume+ additionally?
Click to expand...
Click to collapse
I never get to the screen with the Android. It never progresses past the logo screen when trying to boot into recovery mode from the bootloader menu. Any suggestions? Thank you
Sent from my A0001 using Tapatalk
When you determine the letter then flash boot.IMG I was on 8.1 aosip right after that you will see that the computer will see your file system then I flashed twrp and then either 8.1 beta or asoip.
gflexstump said:
When you determine the letter then flash boot.IMG I was on 8.1 aosip right after that you will see that the computer will see your file system then I flashed twrp and then either 8.1 beta or asoip.
Click to expand...
Click to collapse
I attempted to follow the instructions but it failed. Says "Flashing is not allowed in lock state" Any ideas? Thanks again
Sent from my A0001 using Tapatalk
trsargent said:
I attempted to follow the instructions but it failed. Says "Flashing is not allowed in lock state" Any ideas? Thanks again
Click to expand...
Click to collapse
Unlock first?
Sent from my PH-1 using XDA Labs
avd said:
Unlock first?
Sent from my PH-1 using XDA Labs
Click to expand...
Click to collapse
That may or may not be possible.
The first thing I do is fully unlock my bootloader.
For tother people I suggest enabling the OEM Unlock option.
That doesn't me you have to unlock, but it just might save you.
For the OP, did you select the option to OEM Unlock?
Recovering from a boot loop with a locked bootloader might be a challenge.
trsargent said:
Good evening,
I have trying to get my phone working for a few weeks now to no avail. I can access fastboot mode and it recognizes the device but I cannot access recovery mode. The phone is stuck on the logo screen, powered by Android. When I try to boot to recovery mode, it stays on the logo screen. Any advice? I am willing to try anything at this point.
Thank you!
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
I have the exact same problem, Stuck in boot logo in Recovery, can't flash it through the bootloader due to the phone is locked,
Any luck with your phone ?
I hope you found a way to go around it and will kindly share it with me,
Thank you
A.I.M said:
I have the exact same problem, Stuck in boot logo in Recovery, can't flash it through the bootloader due to the phone is locked,
Any luck with your phone ?
I hope you found a way to go around it and will kindly share it with me,
Thank you
Click to expand...
Click to collapse
Which screen?
trsargent said:
Good evening,
I have trying to get my phone working for a few weeks now to no avail. I can access fastboot mode and it recognizes the device but I cannot access recovery mode. The phone is stuck on the logo screen, powered by Android. When I try to boot to recovery mode, it stays on the logo screen. Any advice? I am willing to try anything at this point.
Thank you!
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
could you solve this problem?
Hey guys I need your help. My Xiaomi A1 got bootloop after I update OTA to Android 8.1.
I cannot unlockbootloader cause I did not turn on usb debugging before. I tried every ways but failed. Please help me
lightningjet said:
Hey guys I need your help. My Xiaomi A1 got bootloop after I update OTA to Android 8.1.
I cannot unlockbootloader cause I did not turn on usb debugging before. I tried every ways but failed. Please help me
Click to expand...
Click to collapse
This is where a/b partition does his magic.
If your update failed then phone will boot on the previous partition to make the update again
I think you can still change slot partition on fastboot with the right driver's installed and right command
Dead-neM said:
This is where a/b partition does his magic.
If your update failed then phone will boot on the previous partition to make the update again
I think you can still change slot partition on fastboot with the right driver's installed and right command
Click to expand...
Click to collapse
here is a guide if u dont know how to change partition:
download fastboot from here: https://forum.xda-developers.com/showthread.php?t=2317790
if u already have fastboot it might not work because its not the latest version but it is the latest version from this link
reboot to bootloader by holding power + volume down button while ur phone is shut down (to shut it down just hold power button)
open the cmd-here.exe file from the zip and type: fastboot devices, if it shows u a string then ur good, if no strings u need to download ur phone's driver and if more than one then unplug ur second phone from ur pc
then type: fastboot --set-active=b if that didnt fix it try --set-active=a and if that didnt fix it then u cant fix ur bootloop using partitions
Dead-neM said:
This is where a/b partition does his magic.
If your update failed then phone will boot on the previous partition to make the update again
I think you can still change slot partition on fastboot with the right driver's installed and right command
Click to expand...
Click to collapse
Thank you, sir. But could you show me how to do that please. Sorry I’m newbie for that.
YayJohn said:
here is a guide if u dont know how to change partition:
download fastboot from here: https://forum.xda-developers.com/showthread.php?t=2317790
if u already have fastboot it might not work because its not the latest version but it is the latest version from this link
reboot to bootloader by holding power + volume down button while ur phone is shut down (to shut it down just hold power button)
open the cmd-here.exe file from the zip and type: fastboot devices, if it shows u a string then ur good, if no strings u need to download ur phone's driver and if more than one then unplug ur second phone from ur pc
then type: fastboot --set-active=b if that didnt fix it try --set-active=a and if that didnt fix it then u cant fix ur bootloop using partitions
Click to expand...
Click to collapse
Thanks alot, I’ll try.
Sent from my iPhone using Tapatalk
YayJohn said:
here is a guide if u dont know how to change partition:
download fastboot from here: https://forum.xda-developers.com/showthread.php?t=2317790
if u already have fastboot it might not work because its not the latest version but it is the latest version from this link
reboot to bootloader by holding power + volume down button while ur phone is shut down (to shut it down just hold power button)
open the cmd-here.exe file from the zip and type: fastboot devices, if it shows u a string then ur good, if no strings u need to download ur phone's driver and if more than one then unplug ur second phone from ur pc
then type: fastboot --set-active=b if that didnt fix it try --set-active=a and if that didnt fix it then u cant fix ur bootloop using partitions
Click to expand...
Click to collapse
I did it. Thank you a thousand times you are my sunshine <3
lightningjet said:
I did it. Thank you a thousand times you are my sunshine <3
Click to expand...
Click to collapse
np press on thanks if it helped u
YayJohn said:
np press on thanks if it helped u
Click to expand...
Click to collapse
Yes sir. I got new problem. I cannot pass google account verified. My Granny he doesn’t remember his email and password. I need to do Bypass through abd but it requires USB debugging on.
Really sad that he didn’t turn on USB debugging before. Could you guys show me how to turn it on without go to Settings?
Sent from my iPhone using Tapatalk
just reflash stock rom via miflash and sign in with another account, or you can change password for the current account if there's any backup email/phone number provided
pooniaprashant said:
just reflash stock rom via miflash and sign in with another account, or you can change password for the current account if there's any backup email/phone number provided
Click to expand...
Click to collapse
Thank sir
Sent from my iPhone using Tapatalk
Mi a1 boot loop 8.0 Oreo to 8.1 OTA UPDATE SOLUTION
Hi friends 8.0 Oreo to OTA 8.1 try to update your phone boot loop I will give the solution ..turning on mobile in fastboot mode ..1) download pie beta fastboot ROM after platform tool download and extract AFTER ROM extract copy ROM files in platform tools after ..2turn to fastboot mode .3)open platform tool copy the ROM files after..4)DOUBELE CLIK..Flash ALL ...after wait 15minutes .black screen automatically open and running some commands don't worry and don't exit black screen still wait your phone reboot wait 15minutes after automatically reboot your phone in 8.0 Oreo ..5)CLIKING FLASH ALL ..AFTER black screen shows fail ..fail ..fail you will do not disconnect your phone wait your phone will be reboot automatically within 15 minutes .6) please note ..AFTER CLIICK FLASH ALL ..YOU WILL WAIT 15.MINUTES BUT COMAND AUTOMATICALLY OPENING ABD SHOWS FAIL don't worry about then .the process compleate take time 15to 20 minutes you will still wait after reboot automatically you will disconnect your mobile and enjoy
I got my 6P bootloader locked (ofcourse by accident) and now it has become a paperweight. is there any solution for this issue? I can boot into bootloader, but cannot flash anything. No recovery is installed and No OS is installed too...
Shabbirkt said:
I got my 6P bootloader locked (ofcourse by accident) and now it has become a paperweight. is there any solution for this issue? I can boot into bootloader, but cannot flash anything. No recovery is installed and No OS is installed too...
Click to expand...
Click to collapse
If the device can be seen by a computer, reflash the factory image. If not, no idea.
Dear friend if you have no OS installed and the Bootloader blocked the only thing you can try is using an OTG cable and a flash memory to download the latest version of the factory image but OTA and copy it to the flash memory and try to flash it from the stock recovery
felixpaz1992 said:
Dear friend if you have no OS installed and the Bootloader blocked the only thing you can try is using an OTG cable and a flash memory to download the latest version of the factory image but OTA and copy it to the flash memory and try to flash it from the stock recovery
Click to expand...
Click to collapse
i cannot do that. how can i access OTG ? booting into recovery reboots phone in endless loop of booting into Google written screen and Screen turns off...
Can you boot to bootloader? (With the device powered off, hold Volume Down + Power)
Then run
Code:
fastboot devices
If you see your mobile then you should be able to flash the factory ROM.
See section 10 in https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
ghost shell said:
Can you boot to bootloader? (With the device powered off, hold Volume Down + Power)
Then run
If you see your mobile then you should be able to flash the factory ROM.
See section 10 in https://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
Click to expand...
Click to collapse
yup... fastboot devices detects the phone...
but when i try to flash factory image it says cannot flash as bootloader is locked.
Shabbirkt said:
yup... fastboot devices detects the phone...
but when i try to flash factory image it says cannot flash as bootloader is locked.
Click to expand...
Click to collapse
Code:
fastboot flashing unlock
Note that it will delete all your data.
Please let me know if after that you're able to flash the factory image.
ghost shell said:
Note that it will delete all your data.
Please let me know if after that you're able to flash the factory image.
Click to expand...
Click to collapse
i tried that brother... it says 'oem unlock is not allowed'.
Shabbirkt said:
yup... fastboot devices detects the phone...
but when i try to flash factory image it says cannot flash as bootloader is locked.
Click to expand...
Click to collapse
Shabbirkt said:
i tried that brother... it says 'oem unlock is not allowed'.
Click to expand...
Click to collapse
I don't know if this will help you but
Code:
fastboot boot twrp.img
Maybe you're able to unlock it or flash from there?
ghost shell said:
I don't know if this will help you but
Maybe you're able to unlock it or flash from there?
Click to expand...
Click to collapse
i appreciate your effort brother...
but i already tried that and no luck...
Shabbirkt said:
yup... fastboot devices detects the phone...
but when i try to flash factory image it says cannot flash as bootloader is locked.
Click to expand...
Click to collapse
Shabbirkt said:
i appreciate your effort brother...
but i already tried that and no luck...
Click to expand...
Click to collapse
No worries. Normally I wouldn't dig into it... but who knows, next time could be me in the same spot.
If you can boot using twrp then you can get adb shell with root, right?
Code:
adb shell getprop | grep -i unlock
I'm getting
[ro.oem_unlock_supported]: [1]
[sys.oem_unlock_allowed]: [1]
Click to expand...
Click to collapse
I'm wondering if you set those props to 1 maybe you'll be able to flash images again.
Code:
adb -d shell setprop ro.oem_unlock_supported 1
adb -d shell setprop sys.oem_unlock_allowed 1
...
Spending way more time than I should lol...
If the above doesn't work check these
https://old.reddit.com/r/AndroidQue...astboot_oem_unlock_without_enable_oem_unlock/
https://gist.github.com/zhuowei/79b6fbcd9ba9f1726163
https://forum.xda-developers.com/nexus-6p/general/to-unlock-phone-twrp-flashed-t3334083
https://forum.xda-developers.com/android/software/frp-destroyer-flashable-zip-t3920067
Wait Brother...
My phone just mysteriously booted up... I dun know how this happend or what made it do so... And Thanks a lot for your assistance...
Another thing is my phone has booted into FRP lock, and i kinda dun know the Email associated with it. Is there any way to bypass it?
Shabbirkt said:
Wait Brother...
My phone just mysteriously booted up... I dun know how this happend or what made it do so... And Thanks a lot for your assistance...
Another thing is my phone has booted into FRP lock, and i kinda dun know the Email associated with it. Is there any way to bypass it?
Click to expand...
Click to collapse
How don't you know the email associated with it ?