I tried to unlock my boot loader and something got screwed up, I have worked with the Nexus S,nexus one,droid incredible, so I get the failed to boot, then I get the 1-14 menu, RSD,fastboot,etc, what do I need too do get my phone back operating, it has the 4.5.91 GB stock and tried flashing the 2.3.4 pudding sbf gets at the very end of the flashing and fails during the flashing it shows the boot logo, then goes right back to the 1-14 menu any help would be great
Flashing pudding is only the first step in unlocking your your device. At this point you have two options.
A. Enter into rsd mode and flash 4.5.91 sbf (the one without pudding) to return to stock.
B. Enter into fastboot mode and finish unlocking your bootloader.
Sent from my MB860 using XDA App
to finish unlocking your bootloader, it's as simple as using the command 'fastboot oem unlock' in fastboot mode, just in case you didn't know that
Your almlsy there
Run that command ^^
great thanks guys I just did the fast boot oem unlock and it worked, something must have been jacked up with my laptop at home, I tried that several times at home, I hooked it up to my work computer and worked first time, thanks guys
Related
You're all going to have to forgive my idiocy, but I have a problem. I installed SM7 in my Atrix on an unlocked bootloader. I decided to go back to stock today and downloaded and flashed the SBF through RSLite. Reading now, you're not suppose to flash a previous sbf version if your bootloader is unlocked, but I didn't know that, at least that's what I'm assuming happenned. Now, the phone goes into a loop on the Motorola animation and does nothing. I can get into fastboot, recovery, RsLite mode and all of that, but the phone itself is in a loop. My questions is, what (If anything) can I do (eg. flash, fastboot etc) to go back and fix my problem? That battery already died once and I found a way to charge it so I can get back in those menus, but any tidbits would be majorly helpful.
madetoservehim said:
You're all going to have to forgive my idiocy, but I have a problem. I installed SM7 in my Atrix on an unlocked bootloader. I decided to go back to stock today and downloaded and flashed the SBF through RSLite. Reading now, you're not suppose to flash a previous sbf version if your bootloader is unlocked, but I didn't know that, at least that's what I'm assuming happenned. Now, the phone goes into a loop on the Motorola animation and does nothing. I can get into fastboot, recovery, RsLite mode and all of that, but the phone itself is in a loop. My questions is, what (If anything) can I do (eg. flash, fastboot etc) to go back and fix my problem? That battery already died once and I found a way to charge it so I can get back in those menus, but any tidbits would be majorly helpful.
Click to expand...
Click to collapse
If you can get into recovery, flash a fruitcake.
Make sure to data wipe & cache wipe beforehand.
Swiftks said:
If you can get into recovery, flash a fruitcake.
Make sure to data wipe & cache wipe beforehand.
Click to expand...
Click to collapse
I tried going into recovery mode; no dice. Droid error icon showed up. What's this I'm reading about flashing using fastboot? Can I download and flash a fastboot file so as to fix my phone?
Tried full wipe using fastboot? That pulled me out of boot loop once.
There are instructions and batch files to automate it somewhere in development forum.
if ur ATnT then screwed for very long time(till there is a fix)
if ur international/bell user (i am bell user and i messed up mine big time) then download the bootloader unlock SBF (IHOP_Bell) and flash it via rdslite and this will give u back the bootloader unlocked logo on ur boot screen.
if yes then ur lucky connect ur phone in fastboot mode and remove every **** out of it
fastboot erase boot
fastboot erase system
fastboot erase webtop
fastboot erase userdata
fastboot erase cache
then flash latest recovery via fastboot (do a search in forum ull find it)
boot into recovery and mount ur memory card as a usb mass storage device and copy the fruitcake or any other rom's zip file into it and flash it via recovery and u should be good to go.
since i am bell user i was able to flash back 2.2.2 french rom via SBF and RSD but after flashing cm7 i am not touching rsd or any sbf for that matter.
Press thanks if i helped you, and if i didnt then press it anyways
i would say do what swiftks says
flash a fruitcake use fastboot its your
only hope now also swiftks has guides
in his signature
Yer not hard bricked. You'll be fine. PM swift or myself if you can't figure it out.
Sent from my SAMSUNG-SGH-I777 using Tapatalk
Previously I have unlocked the bootloader using
Code:
fastboot oem unlock
and it worked just fine. Using
Code:
fastboot oem device-info
both the "tampered" and the "unlocked" bit were set to "True".
Recently, and I have no clue why (possibly a program I tried to use for work that ended up not working), both of these bits are now set to "False"
I cannot flash a new recovery using fastboot, though my original TWRP recovery is still there.
I can still adb sideload update my OS, have root access, etc.
Now running
Code:
fastboot oem unlock
reboots into TWRP recovery with no effect on the bootloader status
I have already tried a few things suggested around here to no avail.
The only thing I can think of to do now is to treat it as a hard brick and completely reset everything and install a stock ROM to start from scratch following something like this thread.
If I can avoid this that would be preferable...
I had the same issue. For some unknown reason my partitions were all messed up so I was getting "bootloader locked" every time, witch is basically what they call a hard brick.
I've used that recovery tool and did fresh start with the latest TWRP and a new ROM. All back on track! Working well since over a month now.
I know it's a pain doing a factory reset and all but I think it's the only thing you can do...
Hello sir,
Recently my internal storage got almost full ,it flashed repeated warnings that "some system functions may go wrong,please freeup some space".I just did not paid much attention to it and proceeded to download a file when my internal storage level was less than 100 mb and then suddenly my phone got switched off.when I tried to switch it on it got stuck in the middle with Android one logo .please help me to solve this problem as I don't to lose my data.
Hi Rakesh,
Is you issue get resolved?
I have also got warnings of internal storage full in my MI-A1 and after that my phone got switched off. I also tried to switched on and it got stuck at android one logo.
Please help me out if your issue get resolved?
Try booting in TWRP and using the file manager to delete some user data to make space.
barrack1 said:
Try booting in TWRP and using the file manager to delete some user data to make space.
Click to expand...
Click to collapse
Hi,
Could you please elaborate more as how to do that?
How to boot in TWRP and how to use file manager as i cannot access phone for file manager to delete some user data?
Note--i can't enable OEM unlocking and ADB debugging in Developer Options as cant access phone.
saurabhsh23 said:
Hi,
Could you please elaborate more as how to do that?
How to boot in TWRP and how to use file manager as i cannot access phone for file manager to delete some user data?
Note--i can't enable OEM unlocking and ADB debugging in Developer Options as cant access phone.
Click to expand...
Click to collapse
Can you use fastboot (volume down+power)? If you don't have Android SDK, then install Minimal ADB and Fastboot, open cmd in that directory and type "fastboot device" (or "fastboot devices"?) while phone is connected via USB in fastboot mode. If it displays your phone's serial number, then you can use fastboot. If it doesn't show you anything, then I think wiping your phone in recovery or performing a clean flash through Mi Flash is the only way. However, if you can use fastboot, then the next step would be booting into TWRP... but we'll get to that once you confirm if it's working or not.
manpildo said:
Can you use fastboot (volume down+power)? If you don't have Android SDK, then install Minimal ADB and Fastboot, open cmd in that directory and type "fastboot device" (or "fastboot devices"?) while phone is connected via USB in fastboot mode. If it displays your phone's serial number, then you can use fastboot. If it doesn't show you anything, then I think wiping your phone in recovery or performing a clean flash through Mi Flash is the only way. However, if you can use fastboot, then the next step would be booting into TWRP... but we'll get to that once you confirm if it's working or not.
Click to expand...
Click to collapse
Hi,
i have checked by typing command---fastboot reboot and my phone reboots and hangs at android one screen so that means i can use fastboot but strangely didnt see in fastboot devices but i found output for fastboot oem device-info where device unlocked shows false and other status.
If this is enough for using fastboot to boot into TWRP?
saurabhsh23 said:
Hi,
i have checked by typing command---fastboot reboot and my phone reboots and hangs at android one screen so that means i can use fastboot but strangely didnt see in fastboot devices but i found output for fastboot oem device-info where device unlocked shows false and other status.
If this is enough for using fastboot to boot into TWRP?
Click to expand...
Click to collapse
Actually bad news is that to boot into TWRP you need to unlock your bootloader first (fastboot oem unlock), but to do that I think you need to have enabled "OEM unlocking" in developer settings (though strangely I am unlocked, but for me this option is disabled). Try unlocking anyway. If it doesn't work, then I would follow this guide to clean flash official firmware with Mi Flash Tool. Be warned, you will lose all your data if you manage to unlock your device.
manpildo said:
Actually bad news is that to boot into TWRP you need to unlock your bootloader first (fastboot oem unlock), but to do that I think you need to have enabled "OEM unlocking" in developer settings (though strangely I am unlocked, but for me this option is disabled). Try unlocking anyway. If it doesn't work, then I would follow this guide to clean flash official firmware with Mi Flash Tool. Be warned, you will lose all your data if you manage to unlock your device.
Click to expand...
Click to collapse
Hi,
Is that mean i will still loose all data even if i unlock bootloader?
And i am unable to unlock bootloader by command. So only option i have now to do factoryreset/wipe data?
So after factory reset again i need to flash the ROM ? Because if again i need to flash ROM, i understand the prerequisite is Bootloader unlock which will create issue again.
Please suggest.
saurabhsh23 said:
Hi,
Is that mean i will still loose all data even if i unlock bootloader?
Click to expand...
Click to collapse
Yes, unlocking bootloader wipes data.
saurabhsh23 said:
Hi,
Is that mean i will still loose all data even if i unlock bootloader?
And i am unable to unlock bootloader by command. So only option i have now to do factoryreset/wipe data?
So after factory reset again i need to flash the ROM ? Because if again i need to flash ROM, i understand the prerequisite is Bootloader unlock which will create issue again.
Please suggest.
Click to expand...
Click to collapse
No, if you wipe your phone through recovery you won't need to flash anything. It just deletes all your stuff without touching the system.
Hi! SaurabhSh23!
Just gone through your post and i am stuck in the same situation of infinite android Logo appearing on screen. with only thing that can be done is FASTBOOT Mode, Tried ADB & Fastboot but OEM Bootloader is LOCKED and cannot be unlocked using cmd.
Did You find any solution to the problem without losing any personal DATA?? please Help me out i am having some precious personal data and I am very confused about how to get that back.
Regards,
Vaibhav, New Delhi. 9953749713
Any update here please?
vaibhav08 said:
Hi! SaurabhSh23!
Just gone through your post and i am stuck in the same situation of infinite android Logo appearing on screen. with only thing that can be done is FASTBOOT Mode, Tried ADB & Fastboot but OEM Bootloader is LOCKED and cannot be unlocked using cmd.
Did You find any solution to the problem without losing any personal DATA?? please Help me out i am having some precious personal data and I am very confused about how to get that back.
Regards,
Vaibhav, New Delhi. 9953749713
Click to expand...
Click to collapse
Guys pls help me i got stuck on boot logo i want to flash stock rom pls help me
I'm in the same boat. Unable to access developer options as phone won't boot and its stuck at the android one logo.
Fastboot oem unlock gives error Flashing Unlock is not allowed.
Is there anyway around this?
I'm still stuck with my Mi A2. I didn't enable OEM unlock or USB debugging and now i'm stuck on android one logo with only option is to boot into fast-boot mode. All commands and tools i try I get error stating unlock is not allowed in Lock State.
I bit the bullet and ordered an EDL cable so we'll see if i get anywhere with that. I've read that newer Xiaomi devices wont work with EDL cable and only option is to use the test point method....not sure how accurate that is but guess i'll find out whenever the cable gets here.
Face_11 said:
I'm still stuck with my Mi A2. I didn't enable OEM unlock or USB debugging and now i'm stuck on android one logo with only option is to boot into fast-boot mode. All commands and tools i try I get error stating unlock is not allowed in Lock State.
I bit the bullet and ordered an EDL cable so we'll see if i get anywhere with that. I've read that newer Xiaomi devices wont work with EDL cable and only option is to use the test point method....not sure how accurate that is but guess i'll find out whenever the cable gets here.
Click to expand...
Click to collapse
What if you type fastboot oem unlock?
https://forum.xda-developers.com/mi-a1/how-to/discussion-bypass-wipe-oem-unlock-t3804406 use this tutorial to avoid data loss during unlocking
jack_21 said:
What if you type fastboot oem unlock?
https://forum.xda-developers.com/mi-a1/how-to/discussion-bypass-wipe-oem-unlock-t3804406 use this tutorial to avoid data loss during unlocking
Click to expand...
Click to collapse
If i try and using Fastboot OEM Unlock i get the following:
C:\Tools\platform-tools>fastboot.exe oem unlock
FAILED (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.008s
Face_11 said:
If i try and using Fastboot OEM Unlock i get the following:
C:\Tools\platform-tools>fastboot.exe oem unlock
FAILED (remote: 'Flashing Unlock is not allowed
')
Finished. Total time: 0.008s
Click to expand...
Click to collapse
You can try fastboot oem edl
To put the phone in EDL mode without specific cable
However why not wipe data from the recovery?
Just use fastboot reboot recovery
jack_21 said:
You can try fastboot oem edl
To put the phone in EDL mode without specific cable
However why not wipe data from the recovery?
Just use fastboot reboot recovery
Click to expand...
Click to collapse
Thanks for the suggestions. I know when I ran fastboot oem edl previously I get message stating device already locked.
If i do fastboot reboot recovery i got an error ..i believe not allowed but will have to check later tonight.
Face_11 said:
Thanks for the suggestions. I know when I ran fastboot oem edl previously I get message stating device already locked.
If i do fastboot reboot recovery i got an error ..i believe not allowed but will have to check later tonight.
Click to expand...
Click to collapse
If you see a triangle, you are in recovery mode
You need to press a button combination to see options, Search on Google for that
Help, I'm in a real state. I was happy on US997 Fulmics, with root, etc, but decided to try Stock Oreo. I upgraded, didn't like the substratum issues, and restored my Nandroid backup. As others discovered, this means the fingerprint doesn't work. I googled, and saw "just factory reset", so I went into my settings and selected "Factory Reset". This took me to TWRP, because of course, but then when I rebooted system, it took me back to TWRP. After some hours of trying to fix this by flashing various ROMs, I came across the advice to try this command in TWRP Terminal:
dd if=/dev/zero of=/dev/block/platform/624000.ufshc/by-name/misc
dd if=/dev/zero of=/dev/block/platform/624000.ufshc/by-name/fota
Click to expand...
Click to collapse
(except I had to add "/soc" after /platform)
Now my bootloader is locked, and its bootloop directly to Fastboot, and type in "fastboot flash unlock unlock.bin" but it returns "FAILED (remote: oem unlock is not allowed)". I can get into Download mode, and I've tried loading two stock Nougat KDZ files, and it still just brings me to Fastboot, right around 80% in the upload process. I can hold volume and get to the recovery prompt, choose erase, I see a brief window of "Erasing" and then its back to Fastboot.
Please, any help is super appreciated!
I'm back trying to fix this after very little sleep, and am at least trying to ask the right questions.
Are there other Fastboot commands I could be using?
Could I have wiped the boot partition, and that's why it goes to Fastboot when it starts?
Is there a way to restore the boot partition using LGUP?
Are there other ways to unlock the bootloader now?
I see in red letters "Please check "Enable OEM unlock in Developer options" in Fastboot, but I can't get into Android to do that, is there anyway to do enable that from within Fastboot or Download?
Is there a KDZ I could flash that has it enabled?
I'm so upset about breaking this through my own idiocy, and really don't want to have to purchase a new phone right now, so I'm definitely willing to throw a few bucks to anyone who knows a sequence of steps to get me working again!
You need to put it in qc9008 mode and do with jtag box
If u can boot into fastboot mode then all hope is not lost. Try using the official LG bridge app for pc, idk if itll work with an unlocked bootloader device but its worth a try, in the app under the update phone tab there is an option "update error recovery" just connect your phone in fastboot mode, select that option, and follow the app instructions. It should atleast take u back to stock. where u can probably start fresh.
My OnePlus 8 Pro is stuck in a fastboot boot loop, can't even power the phone down at this point, fastboot just comes back up again. There is no ROM on the phone somehow (after attempting to downgrade from the beta program) The bootloader is also locked as well, and can't flash any fastboot images. I have attempted to use the MsmDownloadTool, but can't get out of fastboot to use it.
What can I do at this point?
UPDATE: After letting the phone sit and drain the battery completely, I was able to get it into EDL mode, and use the MSM tool, it flashed everything, but still no boot. Any suggestions?
Make sure that you are not connected to USB and select power off from the fastboot menu. You should be able to put it into EDL mode after that and connect back to USB so that you can use the msm tool.
rmiles7721 said:
Make sure that you are not connected to USB and select power off from the fastboot menu. You should be able to put it into EDL mode after that and connect back to USB so that you can use the msm tool.
Click to expand...
Click to collapse
Power off would immediately power back on and to fastboot. I let the phone die and was able to get it to go into EDL mode after, and was able to use the MSM tool, but still no boot.
Any suggestions?
Only time I have had that happen is when I still had the USB cable connected. If it let you use the msm tool and still no boot there may be something wrong with the phone and need an RMA.
Can you access fastboot from the command line? Try downloading the fastboot rom and flash it using the flash-all bat. I had an issue after doing an ota where it wouldn't boot anything but the bootloader. Had to manually change slots to B and then run flash-all and was good after that.
Sent from my ONEPLUS IN2023 using Tapatalk
rmiles7721 said:
Only time I have had that happen is when I still had the USB cable connected. If it let you use the msm tool and still no boot there may be something wrong with the phone and need an RMA.
Can you access fastboot from the command line? Try downloading the fastboot rom and flash it using the flash-all bat. I had an issue after doing an ota where it wouldn't boot anything but the bootloader. Had to manually change slots to B and then run flash-all and was good after that.
Sent from my ONEPLUS IN2023 using Tapatalk
Click to expand...
Click to collapse
Fastboot does boot, but it is locked so there is no flashing anything through that.
Recovery can now boot as well, but still no boot to OS.
hole896 said:
Fastboot does boot, but it is locked so there is no flashing anything through that.
Recovery can now boot as well, but still no boot to OS.
Click to expand...
Click to collapse
So unlock it?
c_86 said:
So unlock it?
Click to expand...
Click to collapse
"but it is locked so there is no flashing anything through that."
Cannot unlock as I can't boot into an OS to enable the unlock. Tried flashing through fastboot but gives error that it has to be unlocked. I have attempted unlocking it through fastboot but it gives an error that it can't be unlocked.
hole896 said:
"but it is locked so there is no flashing anything through that."
Cannot unlock as I can't boot into an OS to enable the unlock. Tried flashing through fastboot but gives error that it has to be unlocked. I have attempted unlocking it through fastboot but it gives an error that it can't be unlocked.
Click to expand...
Click to collapse
Rough. I was thinking since it didn't have a os loaded it would bypass that switch in dev options
c_86 said:
Rough. I was thinking since it didn't have a os loaded it would bypass that switch in dev options
Click to expand...
Click to collapse
Yep, already contacted OnePlus the other day and they are supposed to be setting up a remote session, but I haven't heard from them yet...