Related
Hi, I bricked my Phone (I can get access to CWM v6.0.1.9) whilst changing the Build.Prop file (which I know I'm meant to be careful with) I rebooted my phone and after 10 minutes it was still siting on the "Google" screen. I can get into Bootloader and CWM 6.0.1.9 but cant get it to display on my Laptop (win7) as I can't turn on USB debugging..
Any help? I'm stuck right now! It wont show up on ADB or Nexus Toolkit (I found a thread elsewhere with some links but couldnt read them as I wasnt a member)
Fast boot, flash factory image
do this: http://forum.xda-developers.com/showthread.php?t=1626895
Or reflag custom ROM
I'm getting no response when typing in "Fastboot Devices" when I put "ADB Reboot bootloader" its saying "No device found"
If the device cant be seen Can I still flash?
to use fastboot you need to be in the bootloader, not recovery.
I've tried in the bootloader but nothing ever shows up? I havent seen anything pop-up on the bottom of my start bar.. Hmnn If I could get access to my USB/SDcard I could put a zip file to flash -_-
I'll see if I can get it to show up onn fastboot again
if nothing shows up, that means you dont have the fastboot drivers.
Exactly that's what I thought at first place. Forgive me if you find it way too basic but have you tried re-install fastboot drivers? (or even samsung usb drivers....u can also reflash your Gnex via Odin Mode...after all you've got nothing to lose)
I managed to get it working, It wasn't the drivers (I've been using them recently) It was the latest version of ADB/Fastboot I downloaded the latest version and its now flashing
If you can get into CWM like you say, just flash the ROM again. It should fix whatever changes you made to the build.prop file.
EDIT: Nevermind, I guess you got it working. For future reference, if you ever get to where you messed something up and you can still boot into CWM, a simple reflash of the ROM should fix it. Or always make a backup before you go messing with stuff that might ruin something.
...and as long as u can boot into bootloader, download, recovery mode device is usually nowhere near to brick
Ok so my 3 yo. son likes to play games on my GNex. I have not rooted or made ANY modifications whatsoever. He was in the middle of playing a game when it randomly reboots. He hands it to me on the google screen. It never boots. just sits. I have been from forum to forum. If i hold:
pwr + - volume i get the odin mode download screen. I have tried loading stock images through odin but it always gets to CDMA-Radio the very last step and hangs there forever (15+min.) battery pull.
pwr + + volume I get a black screen with a lock at the bottom. ( i have read that this means i have unlocked the bootloader but I have not, on purpose at least) battery pull
pwr + both volume i get a black screen. It kinda looks like the screen is on but just completely black. no fastboot mode. Battery pull.
the stock images i have found either do not work in odin or have broken links.
i am not sure if usb debugging is on like i said i usually dont mod phones. adb wont recognize. I just want a stock GNex back. Any tips tricks files or suggestions will be greatly appreciated and I have no problem donating to the cause
Also if i plug my phone into my pc and dont touch anything the battery symbol with the lightning bolt comes up. cant get rid of it unless battery pull. HELP!! :crying:
jsgraphicart said:
If you can get into CWM like you say, just flash the ROM again. It should fix whatever changes you made to the build.prop file.
EDIT: Nevermind, I guess you got it working. For future reference, if you ever get to where you messed something up and you can still boot into CWM, a simple reflash of the ROM should fix it. Or always make a backup before you go messing with stuff that might ruin something.
Click to expand...
Click to collapse
Good advice...
regal513 said:
Ok so my 3 yo. son likes to play games on my GNex. I have not rooted or made ANY modifications whatsoever. He was in the middle of playing a game when it randomly reboots. He hands it to me on the google screen. It never boots. just sits. I have been from forum to forum. If i hold:
pwr + - volume i get the odin mode download screen. I have tried loading stock images through odin but it always gets to CDMA-Radio the very last step and hangs there forever (15+min.) battery pull.
pwr + + volume I get a black screen with a lock at the bottom. ( i have read that this means i have unlocked the bootloader but I have not, on purpose at least) battery pull
pwr + both volume i get a black screen. It kinda looks like the screen is on but just completely black. no fastboot mode. Battery pull.
the stock images i have found either do not work in odin or have broken links.
i am not sure if usb debugging is on like i said i usually dont mod phones. adb wont recognize. I just want a stock GNex back. Any tips tricks files or suggestions will be greatly appreciated and I have no problem donating to the cause
Also if i plug my phone into my pc and dont touch anything the battery symbol with the lightning bolt comes up. cant get rid of it unless battery pull. HELP!! :crying:
Click to expand...
Click to collapse
If you want to flash img files via Odin you must first create tar or tar.md5 packages. Download and install cygwin. Once u opened cygwin navigate to your factory image folder where all your img files are. (it's a good idea to make a copy of your bootloader-xxx-img and radio-xxx.img and to rename them to simple bootloader.img and radio.img) and use the following commands:
Code:
tar -H ustar -c boot.img bootloader.img radio.img recovery.img system.img userdata.img > name-of-odin-flashable.tar
md5sum -t name-of-odin-flashable.tar >> name-of-odin-flashable.tar
mv name-of-odin-flashable.tar name-of-odin-flashable.tar.md5
flash this newly created package under "pda" , and do NOT check re-partition!
Please read forum rules before posting
Questions and help issues go in Q&A
Thread moved
Thank you for your cooperation
Friendly Neighborhood Moderator
So, I was using my Nexus during my class today and it was working great.
After class, I walked to my next class with the tablet in my hand, I did not drop it or anything, when I got to my next class the lock screen was unresponsive.
I was still able to take a screen shot, so the tablet wasn't frozen, but the touch screen was not working at all. All of the hardware buttons worked fine.
I let it sit for about 2 hours and the problem persisted.
I just did a soft reset, holding the power button down for 10 seconds, and it shutdown and rebooted, but its now stuck on the Google screen.
Anyone know what is wrong or how I can fix it?
Thank you
See this thread: http://forum.xda-developers.com/showthread.php?t=2381582
krazzyjman said:
So, I was using my Nexus during my class today and it was working great.
After class, I walked to my next class with the tablet in my hand, I did not drop it or anything, when I got to my next class the lock screen was unresponsive.
I was still able to take a screen shot, so the tablet wasn't frozen, but the touch screen was not working at all. All of the hardware buttons worked fine.
I let it sit for about 2 hours and the problem persisted.
I just did a soft reset, holding the power button down for 10 seconds, and it shutdown and rebooted, but its now stuck on the Google screen.
Anyone know what is wrong or how I can fix it?
Thank you
Click to expand...
Click to collapse
Return it.
You have a defective unit.
[email protected] said:
Return it.
You have a defective unit.
Click to expand...
Click to collapse
Another one of many. ASUS quality control FTW.
anjelika said:
See this thread: http://forum.xda-developers.com/showthread.php?t=2381582
Click to expand...
Click to collapse
This thread doesn't work for me since my nexus is in a bricked like state
hard reset ?
hard reset always works for me. 20 seconds
krazzyjman said:
This thread doesn't work for me since my nexus is in a bricked like state
Click to expand...
Click to collapse
Have you tried entering bootloader?
[Info] Guide to entering safe mode, bootloader, stock recovery
I really doubt you are in bricked mode or it wouldn't even show google. If it is stuck on google it is having trouble loading the OS.
Most likely you can go into fastboot mode and just flash your /system and it will begin working again with no loss of data.
sfhub said:
Have you tried entering bootloader?
[Info] Guide to entering safe mode, bootloader, stock recovery
I really doubt you are in bricked mode or it wouldn't even show google. If it is stuck on google it is having trouble loading the OS.
Most likely you can go into fastboot mode and just flash your /system and it will begin working again with no loss of data.
Click to expand...
Click to collapse
My problem is I can't turn the tablet off. When I hold the power button it just restarts.
Also I tried the hard reset and it does nothing. Just stays on the Google screen
Is your device rooted? If not that is just rediculous on asus's part
slamdunksaliby said:
Is your device rooted? If not that is just rediculous on asus's part
Click to expand...
Click to collapse
My device is not rooted at all.
I've had it for 2 days.
I have to say, I am very disappointed in all of these issues.
I would return it..I'm sorry to hear that I have had troubles myself with two devices so far
krazzyjman said:
My problem is I can't turn the tablet off. When I hold the power button it just restarts.
Also I tried the hard reset and it does nothing. Just stays on the Google screen
Click to expand...
Click to collapse
Did you specifically try to get into bootloader mode using the post I mentioned.
You need to Press Power+VolDown continuously until the bootloader menu comes up?
The fact that you are getting to the Google screen at all means your bootloader is still working so I find it hard to understand why you wouldn't be able to get into bootloader mode.
sfhub said:
Did you specifically try to get into bootloader mode using the post I mentioned.
You need to Press Power+VolDown continuously until the bootloader menu comes up?
The fact that you are getting to the Google screen at all means your bootloader is still working so I find it hard to understand why you wouldn't be able to get into bootloader mode.
Click to expand...
Click to collapse
It was not working, but my tablet just died and I was able to charge and get into the bootloader.
Now to see if it will work.
sfhub said:
Did you specifically try to get into bootloader mode using the post I mentioned.
You need to Press Power+VolDown continuously until the bootloader menu comes up?
The fact that you are getting to the Google screen at all means your bootloader is still working so I find it hard to understand why you wouldn't be able to get into bootloader mode.
Click to expand...
Click to collapse
What do I do once into the bootloader mode?
Start, restart bootloader, or recovery?
krazzyjman said:
What do I do once into the bootloader mode?
Start, restart bootloader, or recovery?
Click to expand...
Click to collapse
Well since you are getting stuck on Google, that means your ROM (/system) is not loading.
I would flash boot.img and system.img from the factory restore.
http://developers.google.com/android/nexus/images#razor
The restore is in .tar.gz format and within the tar there is a zip file. Within that zip file is boot.img and system.img. You need to extract those (ungzip, then untar, then unzip) and place them in your adb directory.
Boot your tablet into bootloader mode, connect the USB cable, make sure it is recognized as android bootloader interface.
Type
fastboot flash boot boot.img
fastboot flash system system.img
assuming no errors
fastboot reboot
If on the reboot you still get stuck, push and hold Power for 30-60 seconds and try again.
Fails a second time, something more serious is probably wrong.
If you get stuck on X instead of Google, that means something may be wrong with your user data. Try the 60 second reboot thing again. If it is still stuck on X, boot into recovery and do a wipe data factory reset. See previous post for how to get into recovery.
sfhub said:
Well since you are getting stuck on Google, that means your ROM (/system) is not loading.
I would flash boot.img and system.img from the factory restore.
http://developers.google.com/android/nexus/images#razor
The restore is in .tar.gz format and within the tar there is a zip file. Within that zip file is boot.img and system.img. You need to extract those (ungzip, then untar, then unzip) and place them in your adb directory.
Boot your tablet into bootloader mode, connect the USB cable, make sure it is recognized as android bootloader interface.
Type
fastboot flash boot boot.img
fastboot flash system system.img
assuming no errors
fastboot reboot
If on the reboot you still get stuck, push and hold Power for 30-60 seconds and try again.
Fails a second time, something more serious is probably wrong.
If you get stuck on X instead of Google, that means something may be wrong with your user data. Try the 60 second reboot thing again. If it is still stuck on X, boot into recovery and do a wipe data factory reset. See previous post for how to get into recovery.
Click to expand...
Click to collapse
Where am I typing in those lines?
And all the files I need are in the download link?
sfhub said:
Well since you are getting stuck on Google, that means your ROM (/system) is not loading.
I would flash boot.img and system.img from the factory restore.
http://developers.google.com/android/nexus/images#razor
The restore is in .tar.gz format and within the tar there is a zip file. Within that zip file is boot.img and system.img. You need to extract those (ungzip, then untar, then unzip) and place them in your adb directory.
Boot your tablet into bootloader mode, connect the USB cable, make sure it is recognized as android bootloader interface.
Type
fastboot flash boot boot.img
fastboot flash system system.img
assuming no errors
fastboot reboot
If on the reboot you still get stuck, push and hold Power for 30-60 seconds and try again.
Fails a second time, something more serious is probably wrong.
If you get stuck on X instead of Google, that means something may be wrong with your user data. Try the 60 second reboot thing again. If it is still stuck on X, boot into recovery and do a wipe data factory reset. See previous post for how to get into recovery.
Click to expand...
Click to collapse
I figured out where to type, but I have to unlock my bootloader?
I have no way to enable usb debugging since I cant tun on the device, right?
krazzyjman said:
I have no way to enable usb debugging since I cant tun on the device, right?
Click to expand...
Click to collapse
You don't need to enable USB debugging for fastboot mode.
You just need to press Power+VolDown until you get into the bootloader. That is fastboot mode. It will install Android Bootloader Interface (usb debugging does android debug bridge interface)
I actually didn't realize you weren't unlocked. If that is the case, the unlock process will erase your userdata, so you might as well just do the full factory restore.
First goto bootloader mode using Power+VolDown and connect USB, type
fastboot oem unlock
You'll see a question on the tablet screen, Press VolUp to go to yes and Power to select.
On the command prompt in windows, you should see it erase userdata and cache.
On the bootloader screen it should have "Start" highlighted (if not, use VolDown to cycle until you see "Start"). Press Power to accept. You should see Google, then it'll go into recovery and format userdata and cache. It'll then try to boot and since /system is having issues, you'll be stuck in Google again.
Go back into bootloader mode, hold Power+VolDown for a while until you see the bootloader screen.
Now grab the factory image as above, gunzip, untar, and you should have a folder razor-jss15j
Copy these files from your adb directory to the razor-jss15j directory
adb.exe
fastboot.exe
AdbWinApi.dll
AdbWinUsbApi.dll
In command prompt in the razor-jss15j directory, type
flash-all
It should output a bunch of stuff, essentially writing a factory image to your tablet.
When it is done, it'll reboot and hopefully you'll get the initial setup window.
I wrote this up from memory, so hopefully I didn't forget stuff. If something doesn't seem right just ask.
Thanks for all of your help.
It really means a lot you took the time to help me.
I'm going to Best Buy today and I am going to see if I can do an exchange.
If not, I will try this later.
Again, thank you
Hi guys, I have an issue with my Zenfone 2 (ZE551ML).
I flashed CyanogenMod 12.1 and everything was working fine. That is, until I decided I wanted to go back to stock ROM. That's when everything went wrong.
1) I went into recovery mode (using Power + Volume UP).
2) I wiped cache partition (probably my first mistake)
3) I restored to factory settings (possibly my second mistake)
4) After this I tried to flash the "recovery1.img" of the stock ROM I had.
5 ) That didn't work so I tried using ADB to flash different ".zip" files (all firmware downloaded from Asus website)
When that didn't work either, I abandoned and rebooted the phone. But it doesn't boot anymore.
It is stuck on the Asus screen and nothing happens.
Does anyone know if and how I can get out of this situation?
I must insist on the fact that I am only a novice. Until now I've only ever known iOS and have no knowledge whatsoever of how Android works.
I already posted my question here ("http://forum.xda-developers.com/general/xda-assist/possibly-softbricked-zenfone-2-t3248318") and was told I might want to try posting it here as well. I hope one of you can help me repair my mess !
Download one click root, the one with CWM recovery. Place the factory firmware on your external SD card. Run the one click batch file. Type ACCEPT, press enter, the type T4 for option 4, press enter. Let the phone boot into CWM recovery. Select the option to update from external SD, pick your file and wait about 5 mins. Back to stock you go. By the way, to get into fastboot press and hold volume up + power wait for vibration then quickly press volume down about 3 times you should be able to get to fast boot, the run the one click batch.
shawnchalfant said:
Download one click root, the one with CWM recovery. Place the factory firmware on your external SD card. Run the one click batch file. Type ACCEPT, press enter, the type T4 for option 4, press enter. Let the phone boot into CWM recovery. Select the option to update from external SD, pick your file and wait about 5 mins. Back to stock you go. By the way, to get into fastboot press and hold volume up + power wait for vibration then quickly press volume down about 3 times you should be able to get to fast boot, the run the one click batch.
Click to expand...
Click to collapse
Thanks for the reply. Do you have a link for the one click root with CWM Recovery ? Can't seem to find it... Also, when I connected my phone to the computer and opened oneclickroot (basic) it says my phone needs to have USB debugging activated (which it did).
I can't get into recovery mode anymore, the phone just loops back to fastboot with no error message.
You just need fast boot only. Look around the forum for the CWM root its here and esy to find.
shawnchalfant said:
You just need fast boot only. Look around the forum for the CWM root its here and esy to find.
Click to expand...
Click to collapse
Found it but it doesn't do anything. The device doesn't even appear when I type "adb devices" in cmd. Thanks for trying to help but I'll just send it somewhere it can be fixed. I must have deleted the whole OS and now the phone is just trying to reboot but there is nothing to reboot.
Boot into fastboot, Vol Up + Power, once it vibrates quickly press and hold volume down a few seconds. Fastboot should appear. Then run the batch file. Adb does not run in fastboot mode.
m3j said:
Found it but it doesn't do anything. The device doesn't even appear when I type "adb devices" in cmd. Thanks for trying to help but I'll just send it somewhere it can be fixed. I must have deleted the whole OS and now the phone is just trying to reboot but there is nothing to reboot.
Click to expand...
Click to collapse
there is still hope ... go for a lower version of recovery, boot (flash it in fastboot) and then keep the rom by keeping it in the external sd card renaming it to MOFDS_Update (i dont remember the name ). flashing should be done on its own...
search "Tutorial Upgrade / Downgrade / Unbrick Zenfone 2" in Asus ZenTalk. it helps for me
Thank you all for trying to help but I wasn't able to repair the phone.
I sent it back and by some miracle they accepted to give me my money back. Buying a new one now but I won't do anything stupid with it this time !
Hi all,
I installed TWRP on my Honor 7x, that went well.
Yesterday I decided to try to get Lineage working so:
- I installed EMUI 8, that went pretty smooth
- I installed Lineage OS 15.1. (without GApps)
- I flashed TWRP.
The issue I have now is that:
1) I can't install any APK in Lineage. Probably needs a factory reset/dalvik cache wipe.
2) I can't boot into TWRP. It stays stuck on the splash screen forever. This also means I can't install OpenGapps, SuperUser access (afaik), or anything else that requires root.
3) The bootloader is saying "FRP: Locked", which means I can't flash a new TWRP or a different ROM. When I try it fails with "command not allowed"
3) "fastboot oem unlock" fails saying I need to enable it in the developer options, but it's grayed out in the developer options because it's already unlocked.
4) I wanted to try the "dload" method but I can't find a good explanation on how to do it, and Huawei recently took all their downloads down, which means I can't find any UPDATE.app even if I knew how.
5) The other solution that *might* work is using "fastboot oem frp-unlock", but I need an unlock code for that (I assume the same one that you request for an OEM unlock from Huawei), and Huawei closed down the site that generated the codes.
So I'm stuck in a weird limbo where I can't move forward (install Gapps and use my phone as normal) nor backwards (go back to EMUI8).
Does anyone have any idea how I can fix this situation?
Shadowsalyer said:
Hi all,
I installed TWRP on my Honor 7x, that went well.
Yesterday I decided to try to get Lineage working so:
- I installed EMUI 8, that went pretty smooth
- I installed Lineage OS 15.1. (without GApps)
- I flashed TWRP.
The issue I have now is that:
1) I can't install any APK in Lineage. Probably needs a factory reset/dalvik cache wipe.
2) I can't boot into TWRP. It stays stuck on the splash screen forever. This also means I can't install OpenGapps, SuperUser access (afaik), or anything else that requires root.
3) The bootloader is saying "FRP: Locked", which means I can't flash a new TWRP or a different ROM. When I try it fails with "command not allowed"
3) "fastboot oem unlock" fails saying I need to enable it in the developer options, but it's grayed out in the developer options because it's already unlocked.
4) I wanted to try the "dload" method but I can't find a good explanation on how to do it, and Huawei recently took all their downloads down, which means I can't find any UPDATE.app even if I knew how.
5) The other solution that *might* work is using "fastboot oem frp-unlock", but I need an unlock code for that (I assume the same one that you request for an OEM unlock from Huawei), and Huawei closed down the site that generated the codes.
So I'm stuck in a weird limbo where I can't move forward (install Gapps and use my phone as normal) nor backwards (go back to EMUI8).
Does anyone have any idea how I can fix this situation?
Click to expand...
Click to collapse
small chance you enable root from developer options. (i think it will be adb only)
if so , maybe can use adb shell and "dd" to write recovery to correct partition.
problem is many of the available twrp do not boot on custom rom .
example code. (if you do wrong , it may be bad)
Code:
dd if=/ext_sdcard/twrp_Recovery_ramdisk.img of=/dev/block/mmcblk0p32
It seems like I'm allowed to use dd in ADB shell, but before I run it, what do you mean by " problem is many of the available twrp do not boot on custom rom . "? I thought recovery was independent of the ROM? And does it mean flashing twrp like that could brick my phone?
Shadowsalyer said:
It seems like I'm allowed to use dd in ADB shell, but before I run it, what do you mean by " problem is many of the available twrp do not boot on custom rom . "? I thought recovery was independent of the ROM? And does it mean flashing twrp like that could brick my phone?
Click to expand...
Click to collapse
Like what you have , twrp stuck on splash screen
I managed to unlock the FRP with DC-unlocker. Sucks that it costs money but it worked!
Now Im stuck in a TWRP boot loop though.
Shadowsalyer said:
I managed to unlock the FRP with DC-unlocker. Sucks that it costs money but it worked!
Now Im stuck in a TWRP boot loop though.
Click to expand...
Click to collapse
At this point you should have access to fastboot though, right? I'd try a different TWRP instead. Perhaps try this one: https://drive.google.com/file/d/1ZYo7Ndte3vlLcUSadD6jIgfBi1oxa0Pb/view?usp=drivesdk
Just to clarify, it gets stuck on TWRP splash screen. When I turn off the phone, it immediately boots up again into TWRP. I tried getting into fastboot mode with all kinds of combinations of button presses, but no luck. Not even Volume Up + USB cable works
smokinjoe2122 said:
At this point you should have access to fastboot though, right? I'd try a different TWRP instead. Perhaps try this one: https://drive.google.com/file/d/1ZYo7Ndte3vlLcUSadD6jIgfBi1oxa0Pb/view?usp=drivesdk
Click to expand...
Click to collapse
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
I have seen this happen before , solution was to wait for dead battery, or disassemble to unplug battery
---------- Post added at 04:51 PM ---------- Previous post was at 04:47 PM ----------
Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
This is because after the frp unlock, it needed to see a factory reset, and it usually needs to be done with stock recvery.
So will have to wait till battery is dead and and plug in usb while holding volume button. Should then load to fastboot. Where it is best to flash stock recovery to clear the recovery bootloop. The bootloop is do to the fact yo unlocked frp and now phone needs to wipe/data
Shadowsalyer said:
Sorry, only saw your answer after sending my other reply. In theory I should have access to fastboot mode. However, everytime I start up I get into TWRP, which doesn't work. I tried Volume up, volume down, both, with and without power button, with and without cable, and no dice.
Click to expand...
Click to collapse
it sucks this happened to yu but im glad i am not the only one that dc-unlocker deleted my fastboot after i unlocked the frp and i cant boot fastboot for nothing if you find a solution please contact me. my phone is doing the exact same thing booting straight too twrp no mater what combinations i use
dcraffam said:
it sucks this happened to yu but im glad i am not the only one that dc-unlocker deleted my fastboot after i unlocked the frp and i cant boot fastboot for nothing if you find a solution please contact me. my phone is doing the exact same thing booting straight too twrp no mater what combinations i use
Click to expand...
Click to collapse
i just took mine apart and discconected the battery and still no luck that program deleted my fastboot
Please can you tell me the process to install twrp I have the L24
I waited all the way till the battery drained, stuck in the USB, and it booted to ROM! Sadly it immediately shut off again because the battery is dead (even with keeping the USB in). I'm going to keep trying though.
I can't get into fastboot mode. I can get into the ROM by letting the battery drain completely on the TWRP splashscreen, and then sticking in the USB cable. However, no button combination or "adb reboot bootloader" or rebooting to bootloader from the ROM brings me to the bootloader. I wonder if it's still there. Any ideas?
Shadowsalyer said:
I can't get into fastboot mode. I can get into the ROM by letting the battery drain completely on the TWRP splashscreen, and then sticking in the USB cable. However, no button combination or "adb reboot bootloader" or rebooting to bootloader from the ROM brings me to the bootloader. I wonder if it's still there. Any ideas?
Click to expand...
Click to collapse
Seems to be a f-up situation either way.
You have adb DD available, found out before.
Don't know if maybe flashing stock recovery is good idea at this point.
I think fastboot.img can be flashed with DD too, but don't try till someone can confirm.
If flash stock recovery clears the loops, maybe best to do full-ota manual flashing.
I managed to get an UPDATE.APP file and extract fastboot.img from it, as well as all the other .img files. If someone can tell me what to flash and how (with dd), I think Im set.
Shadowsalyer said:
I managed to get an UPDATE.APP file and extract fastboot.img from it, as well as all the other .img files. If someone can tell me what to flash and how (with dd), I think Im set.
Click to expand...
Click to collapse
Fastboot.img is the large part the bootloader. If flashing it goes bad, might be dead phone after, just rember that.
Will add a list of partition names and command s for you soon.
here is a list of oreo partitions and there /dev/blk/** number
and here is an example of code to save images with dd assuming you put the images on your extrnal-sdcard in folder called oreo-images
Code:
dd if=/dev/block/mmcblk0p5 of=/mnt/ext_sdcard/oreo-images/fastboot.img
Do that save first and compare the md5 of the file from update.app to this file.
or just check the md5 before making the copy
Code:
adb shell md5sum /dev/block/mmcblk0p5
If you are conviced you need to flash the images, here is example of writing the image assuming files are in sdcard folder oreo-update-images
Code:
dd if=/mnt/ext_sdcard/oreoupdate-images/fastboot.img of=/dev/block/mmcblk0p5
As I have said, this might be bad advise , I have not done fastboot.img flashing before. But on other devices it is same as lk.img or uboot.img, There is danger in flashing it incorrectly. That is why my suggestion was to flash no-check-recovery and do manael update with "echo -update_package" commands.
Along with the statement that fastboot.img is similar to lk.img or uboot.img on other phones, Your fastboot cannot be gone. because phone boots.
but do let us know how it goes.
I agree it would be better to flash recovery if possible. I assume I need the NoCheck-Recovery image from this thread? https://forum.xda-developers.com/honor-7x/how-to/manual-update-to-oreo-beta-emui-8-bnd-t3767044
And what partition do I have to flash it to? I'm guessing either /dev/block/mmcblk0p28 (erecovery ramdisk) or /dev/block/mmcblk0p32 (recovery ramdisk)? I'm not sure what the difference is between erecovery and normal recovery.
(didn't flash fastboot yet, wanted to see if recovery was doable).
Shadowsalyer said:
I agree it would be better to flash recovery if possible. I assume I need the NoCheck-Recovery image from this thread? https://forum.xda-developers.com/honor-7x/how-to/manual-update-to-oreo-beta-emui-8-bnd-t3767044
And what partition do I have to flash it to? I'm guessing either /dev/block/mmcblk0p28 (erecovery ramdisk) or /dev/block/mmcblk0p32 (recovery ramdisk)? I'm not sure what the difference is between erecovery and normal recovery.
(didn't flash fastboot yet, wanted to see if recovery was doable).
Click to expand...
Click to collapse
To recovery_ramdisk. 32
What about check md5 of fastboot partition, that will be helpful to know if it did get wiped out.?
Hmm seems like I'm not allowed to use dd after all:
HWBND-H:/ $ dd if=/storage/7C96-7E17/BND-RECOVERY-NoCheck.img of=/dev/block/mmcblk0p32
dd: /dev/block/mmcblk0p32: Permission denied
And here I was thinking I was close to solving it...
Also can't run md5sum on the fastboot partition, since that needs root as well.
hey, i have a completely stock 9 pro, i was texting someone and sending them pictures from the night but while i was doing that the phone suddenly crashed to the lock screen over and over again. so i just hard rebooted it since it was completely unresponsive and just crashing on the lock screen and now it will not even boot up it just shows the oneplus log and a field to put in a password and after entering the password its looking to format the phone and probably factory reset the whole device i was hoping that there would be some way to use adb to get my photos back since i didnt get a chance to save or send them and it would be a real bummer if they were gone. not enough to pay 1000s of dollar but enough that i would spend time playing with adb to recover them. im very familiar with commandline and adb but i dont know of a way to get in without unlocking the bootloader first.... any help would be very much appreciated.
Can you manage to boot into fastboot and try some things there?
Setup platform tools (let me know if you do not have it setup) and then boot into fastboot. Connect your device to your computer and try out the following commands :
fastboot getvar current-slot
If this outputs something like :
current-slot: b
Then run the following command :
fastboot --set-active=a
otherwise, run the following command :
fastboot --set-active=b
After this is done, reboot your device by running :
fastboot reboot
Like the original poster above. my completely stock OP9P (with all official updates installed) is stuck in a bool loop in which it displays the 1+ logo for a fraction of a sec, then reboots. I believe this was the result of the phone being unlocked in my pocket and something happening. When I pulled the phone out of my pocket, there was a message about a corruption in the OS on the screen.
I am able to get it to boot to fastboot by holding the Vol +&- buttons during the boot cycle, but I don't know how to recover the OS.
Can anyone help guide me or point me at a thread with tools that I can try?
Thanks, in advance.
I never set bios or lockscreen passwords, or encrypt data drives. You are the one most likely to be locked out, sometimes through no fault of your own. People will steal these devices regardless if they're locked or not; physical security is the only type of security that works.
wjcrabtree said:
Like the original poster above. my completely stock OP9P (with all official updates installed) is stuck in a bool loop in which it displays the 1+ logo for a fraction of a sec, then reboots. I believe this was the result of the phone being unlocked in my pocket and something happening. When I pulled the phone out of my pocket, there was a message about a corruption in the OS on the screen.
I am able to get it to boot to fastboot by holding the Vol +&- buttons during the boot cycle, but I don't know how to recover the OS.
Can anyone help guide me or point me at a thread with tools that I can try?
Thanks, in advance.
Click to expand...
Click to collapse
When you enter the Bootloader (fastboot as you call it), and by navigating with the volume buttons, choose the "reboot to recovery" and confirm with the power button. This will reboot you to the recovery, and from there you can again use the Volume buttons to navigate and choose to wipe your data/phone.
This will format your internal storage, so your data is lost, but it will most likely help you with the issue you have. Another solution would be to use the MSM tools and "unbrick" the phone from EDL. Just by getting into recovery and formating your phone should do the trick, if not, MSM will fix it since it is the unbrick tool.
ekin_strops said:
When you enter the Bootloader (fastboot as you call it), and by navigating with the volume buttons, choose the "reboot to recovery" and confirm with the power button. This will reboot you to the recovery, and from there you can again use the Volume buttons to navigate and choose to wipe your data/phone.
This will format your internal storage, so your data is lost, but it will most likely help you with the issue you have. Another solution would be to use the MSM tools and "unbrick" the phone from EDL. Just by getting into recovery and formating your phone should do the trick, if not, MSM will fix it since it is the unbrick tool.
Click to expand...
Click to collapse
Thank you for the response. Sorry for the bad nomenclature. It's been a long time since I have used anything except stock. (Go all the way back to the custom ROMs on my Note 4)
I've tried that. Booting to recovery puts it right back into the boot loop.
It seems like there's a way to sideload the stock OS, but I can't find a cohesive, step-by-step guide that'll walk a N00B like me through.
wjcrabtree said:
Thank you for the response. Sorry for the bad nomenclature. It's been a long time since I have used anything except stock. (Go all the way back to the custom ROMs on my Note 4)
I've tried that. Booting to recovery puts it right back into the boot loop.
It seems like there's a way to sideload the stock OS, but I can't find a cohesive, step-by-step guide that'll walk a N00B like me through.
Click to expand...
Click to collapse
There is no way to sideload it with a locked bootloader. Your only way out now is the MSM tool.
Follow these two links:
https://forum.xda-developers.com/t/op9pro-repository-of-msm-unbrick-tools-tmo-eu-glo-in.4272549/
https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/
wjcrabtree said:
Thank you for the response. Sorry for the bad nomenclature. It's been a long time since I have used anything except stock. (Go all the way back to the custom ROMs on my Note 4)
I've tried that. Booting to recovery puts it right back into the boot loop.
It seems like there's a way to sideload the stock OS, but I can't find a cohesive, step-by-step guide that'll walk a N00B like me through.
Click to expand...
Click to collapse
You can't do a factory reset from there?
It's rare but a SEU can corrupt any part of the flash memory. It causes no physical damage but the altered memory cells will need reset.
I think the best way to recover is MSM tool for youre specific model phone.
My phone power off by it self after watching a video on a received link with whatsapp.
Nothing workt beside MSM. I factory reset, downgrade rom. flash-reflash rom's.
MSM wipe all in youre phone.
ekin_strops said:
There is no way to sideload it with a locked bootloader. Your only way out now is the MSM tool.
Follow these two links:
https://forum.xda-developers.com/t/op9pro-repository-of-msm-unbrick-tools-tmo-eu-glo-in.4272549/
https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/
Click to expand...
Click to collapse
Thank you so much!!
Sorry for the slow reply, but I haven't had time to deal with the problem because of work. I'll be looking into this today.
ekin_strops said:
There is no way to sideload it with a locked bootloader. Your only way out now is the MSM tool.
Follow these two links:
https://forum.xda-developers.com/t/op9pro-repository-of-msm-unbrick-tools-tmo-eu-glo-in.4272549/
https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/
Click to expand...
Click to collapse
Ho Lee Sheet! I finally got around to dedicating serious time to working on this.
I had to jack-around with it quite a bit to get Windows 11 to load the proper drivers so that the phone would be recognized, but: BOOM! BACK IN BUSINESS!
Thank you so much for the guidance.