[Q] Sudden Bootlooping! Please HELP!!! - Motorola Photon Q 4G LTE

Hi, guys! Signed up just to ask this since everyone on here seems helpful. Long story short, my digitizer got damaged, so I replaced it today. First time doing something like that, but I was EXTREMELY careful and followed a repair guide on YouTube to the dot! Phone is currently (or possibly WAS) running CM11, Android 4.4 BEAUTIFULLY! No problems whatsoever before the damage occurred.
Got the piece replaced today, turned the phone on and it started bootlooping :crying: I don't know why it started, so I opened it up again, checked every single connection and they're all good. No damaged ribbon cables, nothing. Still looping....Flashed back to stock ICS with RSD 6.1.5, still looping....Reflashed CM11, still doin' it.
I cannot for the life of my figure out what's going on. I have CWM Recovery 6.0.1.2 on it right now and got an error log to show on the screen. Here's what it says, word for word:
CWM Based Recovery v6.0.1.2
ro.hardware=gcom
ro.revision=33456
ro.emmc=1
ini.svc.recovery=running
service.adb.root=1
init.svc.adbd=running
i: Checking for extendedcommand...
i: Skipping execution of extendedcommand. file not found...
i: Can't partition non-vfat: datamedia
i: Can't partition unsafe device: /dev/black/mmcblk1p1
i: Can't format unknown volume: /emmc
So, that's everything it says on the screen in the exact order, spacing and lettering. Does any of this mean anything to anybody? I don't know what to make of it....I'm not real into this kinda thing, other then being able to know how to flash new ROMS and root my phone. I would reflash the stock firmware, try and relock the bootloader and send it in for repair, but I know they'll know I was into it. If someone could PLEASE help me, I'd GREATLY appreciate it!

I didn't see you mention it...
Did you factory reset in recovery?

arrrghhh said:
I didn't see you mention it...
Did you factory reset in recovery?
Click to expand...
Click to collapse
Yes, a few times. Also did Dalvik
EDIT: I just found this, but I'm not sure if it's what I'm looking for: http://forum.xda-developers.com/showthread.php?t=2295643
I noticed it has emmc files in it. Could it help? They mention you need TWRP, but I can't use it. The touchscreen is still unresponsive.

StarlitSnowWolf said:
Yes, a few times. Also did Dalvik
Click to expand...
Click to collapse
Hm. You might have to RSD back to stock

arrrghhh said:
Hm. You might have to RSD back to stock
Click to expand...
Click to collapse
I mentioned in my first post I flashed stock ICS with RSD, but still no change

StarlitSnowWolf said:
I mentioned in my first post I flashed stock ICS with RSD, but still no change
Click to expand...
Click to collapse
Was the flash successful? Did you try JB? Do you have any logs? Does adb start up even?

arrrghhh said:
Was the flash successful? Did you try JB? Do you have any logs? Does adb start up even?
Click to expand...
Click to collapse
Flash seemed successful, currently downloading 4.1.2 stock ROM to flash, only log I know of is the one I described in first post, and I'm not sure what you mean by the ADB. Fastboot works

StarlitSnowWolf said:
Flash seemed successful, currently downloading 4.1.2 stock ROM to flash, only log I know of is the one I described in first post, and I'm not sure what you mean by the ADB. Fastboot works
Click to expand...
Click to collapse
When your phone is "bootlooping" see if the computer can "see" the phone - adb devices typically.

arrrghhh said:
When your phone is "bootlooping" see if the computer can "see" the phone - adb devices typically.
Click to expand...
Click to collapse
How would one do that? The computer makes it "ding" sound like it does when a device is connected to a USB port and RSD Lite will show it if it's in fastboot mode

StarlitSnowWolf said:
How would one do that? The computer makes it "ding" sound like it does when a device is connected to a USB port and RSD Lite will show it if it's in fastboot mode
Click to expand...
Click to collapse
Just like fastboot devices, adb devices from command prompt.

arrrghhh said:
Just like fastboot devices, adb devices from command prompt.
Click to expand...
Click to collapse
I'm pretty sure the ADB works. I'm able to flash recoveries with it and do the "fastboot devices" and it shows up

StarlitSnowWolf said:
I'm pretty sure the ADB works. I'm able to flash recoveries with it and do the "fastboot devices" and it shows up
Click to expand...
Click to collapse
Then use adb to pull logs when you say the device is booting.......

So, how do I do that? I don't know how to pull logs during boot, or do I do it in fastboot mode?

Bump....I left it on the charger all night long and at some point, it booted into Android, but I wasn't able to do anything. Screen was on "Hands Free Activation" and said something about a failure ota_apn. No touch response whatsoever, so I powered it back off and it's boot looping again. Can someone PLEASE help me!?!? I posted a log for CWM when I had it installed, so does any of it mean anything!?

StarlitSnowWolf said:
So, how do I do that? I don't know how to pull logs during boot, or do I do it in fastboot mode?
Click to expand...
Click to collapse
adb logcat

So, when would I want to run that? In fastboot or while the phone is trying to boot?

StarlitSnowWolf said:
So, when would I want to run that? In fastboot or while the phone is trying to boot?
Click to expand...
Click to collapse
While the phone is trying to boot... I need a log from the bootloop failure.

arrrghhh said:
While the phone is trying to boot... I need a log from the bootloop failure.
Click to expand...
Click to collapse
I just got home from dropping it off at a repair shop. If I'd known about getting the log sooner, I would've.

Related

Error during rooting process

Hey guys, I'm a new poster but have been reading these forums for a while, hope you can help me solve this huge problem I have..
So I was rooting my Motorola Razr I today, did the Bootloader unlock, everything great, started rooting, everything went nice until all of the sudden this happens:
remount succeded
error: protocol fault (no status)
error: device not found
error: device not found
error: device not found
error: device not found
Rebooting...
error: device not found
Flashing Secured Kernel back...
< waiting for device >
I waited a while to see if it would reconnect by itself, nothing happened, then I restarted the boot, got another "waiting to find device to reboot", but nothing..
Then I disconnected the phone and tried to restart it, but the only menus I can get to are the fastboot and the screen that says that the bootloader is unlocked..
Is there any way I could restore the system or restart the rooting process and get it all the way through?
Any help is appreciated.. Thanks!
P.S.: I have a screenshot of the whole root process window, just can't post it here because I'm a new user.. If anyone is willing to help I can send it to them via email or pm.. Thank you again!
EDIT: sorry, this might be the wrong subforum.. Mods feel free to move it where it belongs..
snowbirddd said:
Hey guys, I'm a new poster but have been reading these forums for a while, hope you can help me solve this huge problem I have..
So I was rooting my Motorola Razr I today, did the Bootloader unlock, everything great, started rooting, everything went nice until all of the sudden this happens:
remount succeded
error: protocol fault (no status)
error: device not found
error: device not found
error: device not found
error: device not found
Rebooting...
error: device not found
Flashing Secured Kernel back...
< waiting for device >
I waited a while to see if it would reconnect by itself, nothing happened, then I restarted the boot, got another "waiting to find device to reboot", but nothing..
Then I disconnected the phone and tried to restart it, but the only menus I can get to are the fastboot and the screen that says that the bootloader is unlocked..
Is there any way I could restore the system or restart the rooting process and get it all the way through?
Any help is appreciated.. Thanks!
P.S.: I have a screenshot of the whole root process window, just can't post it here because I'm a new user.. If anyone is willing to help I can send it to them via email or pm.. Thank you again!
EDIT: sorry, this might be the wrong subforum.. Mods feel free to move it where it belongs..
Click to expand...
Click to collapse
If you have an unlocked BL its really simple... flash CWM recovery. Then download SuperSU from chainfire's site and flash it with CWM and you have root.
As for the system, guess you have to flash with RSD a stock system and re-root.
Sent from my RAZR HD XT925
saloums7 said:
If you have an unlocked BL its really simple... flash CWM recovery. Then download SuperSU from chainfire's site and flash it with CWM and you have root.
As for the system, guess you have to flash with RSD a stock system and re-root.
Sent from my RAZR HD XT925
Click to expand...
Click to collapse
Sounds simple enough, thanks :good:
I actually brought the phone to a neighbor who probably knows more about this stuff than I do, sent him a link to this thread too, maybe he figures it out, if not i'll try what you said tomorrow..
Will keep you posted on how it plays out.. Thanks!
So my neighbour is saying he can't get anything to work, that possibly the phone is bricked :crying:
I'm gonna go by his place in a bit and try what saloums7 said, but if my neighbor is right and the phone IS bricked, is there any way to possibly unbrick it?
I'll be the ass. This is the wrong forum.
You are not your iPhone 5
#tylerdurden
SFG said:
I'll be the ass. This is the wrong forum.
You are not your iPhone 5
#tylerdurden
Click to expand...
Click to collapse
Lol yeah I just realised
snowbirddd said:
Sounds simple enough, thanks :good:
I actually brought the phone to a neighbor who probably knows more about this stuff than I do, sent him a link to this thread too, maybe he figures it out, if not i'll try what you said tomorrow..
Will keep you posted on how it plays out.. Thanks!
Click to expand...
Click to collapse
If you can't boot the phone try downloading the corresponding fastboot files from the firmware super thread and flash with RSD. Then flash CWM with fastboot commands (mfastboot works better for flashing recovery) and then from CWM you can install SuperSU and root.
Sent from my RAZR HD XT925
saloums7 said:
If you can't boot the phone try downloading the corresponding fastboot files from the firmware super thread and flash with RSD. Then flash CWM with fastboot commands (mfastboot works better for flashing recovery) and then from CWM you can install SuperSU and root.
Sent from my RAZR HD XT925
Click to expand...
Click to collapse
I can only find a firmware superthread for the XT925, but mine is an XT890, do they both use the same firmware? Meaning, can I use the XT925 firmware in mine? Thanks
EDIT: Nevermind, I found the firmware I need.. Gonna try to flash it now
EDIT 2: Excuse my noobness, but I think you might have misunderstood what I said.. I do have access to the fastboot menu.. When you say that I should flash the fastboot files, you mean only if I can't get into fastboot right? Or do I have to do it anyway? thanks
EDIT 3: Well I think I might be getting onto something now, I'm following the steps used in the "How to Update/unbrick" video of "TheRazrGuy".. I'll keep you guys posted
Ok so I downloaded the fastboot files for my phone but there is not a single file in there thats flashable through RSD, no xml file, nothing, only .img and .exe.. Did I download the wrong thing or can I flash these files too?
Oh shoot, now the RSD is stuck in "Please manually power up this phone" but when i press the power button the little green light lights up but the screen won't turn on at all... Can I still flash something through RSD if this happens? Meaning could I turn RSD off now and restart it and try to flash again or a different file?
snowbirddd said:
Oh shoot, now the RSD is stuck in "Please manually power up this phone" but when i press the power button the little green light lights up but the screen won't turn on at all... Can I still flash something through RSD if this happens? Meaning could I turn RSD off now and restart it and try to flash again or a different file?
Click to expand...
Click to collapse
I think you're better off asking in the RAZR I forums... they will be better equipped to help you...
Sent from my RAZR HD XT925

Partially Bricked Nexus 5

I never tried flashing a custom kernel before on my phone, but I downloaded Code Blue last night latest (615 I think) and I tried flashing it this morning. I have MultiROM installed with TWRP. When I rebooted my phone, MultiROM came up and I selected my internal 4.4.4 stock ROM. It then went to a black screen and stayed there for about 5 minutes until I rebooted the phone. Now I am currently sitting at a "Google" logo and the phone is completely stuck and won't move. I'm guessing the kernel wiped MultiROM or it wasn't compatible and now it's trying to boot something that is corrupted.
What's weird is, if I go into TWRP and go to MultiROM, it tells me it isn't installed.
Does anyone know how to fix this
I tried downloading MultiROM uninstaller tool and lo and behold, my data wont mount in TWRP on my laptop or desktop to put it on there :'(
Is there anyway to install the uninstaller without it on my internal
snappycg1996 said:
I tried downloading MultiROM uninstaller tool and lo and behold, my data wont mount in TWRP on my laptop or desktop to put it on there :'(
Is there anyway to install the uninstaller without it on my internal
Click to expand...
Click to collapse
Hello,
use wugs nexus toolkit, you can flash back to stock with this tool.
There ist a point named flash stock and unroot, there you must set the point by current status, bricked/bootloop.
Freddy Krüger said:
Hello,
use wugs nexus toolkit, you can flash back to stock with this tool.
There ist a point named flash stock and unroot, there you must set the point by current status, bricked/bootloop.
Click to expand...
Click to collapse
Thank you for the reply just to ensure, this will wipe everything right is there any way to save my data
I really don't know much about multitom.. But just use adb to pull your sdcard data then factory reset.
You could return to stock but please don't use toolkit as mentioned above. I'm really not sure why people insist on this being then answer.
2 links in my signature. 1 about why toolkits are not the answer. Another about guides and info threads. You can read about fastboot and adb. There and never think about pesky toolkits again.
Also no such thing as partially bricked. Its either bricked or not. This is not. Just a boot loop
do not use root toolkits. the reason you listed your phone as "partially bricked" is because you dont know better. a phone is either completely bricked or not. you do not learn how to do things using root toolkits. root tooolkits are not meant for noobs. what you want to do is flash the factory img via fastboot while you are in the bootloader.
Your phone isn't bricked at all, it can be easily fixed.
1) Downlaod 4.4.4 stock rom for nexus 5 on the offical site : https://developers.google.com/android/nexus/images
2) Unzip the folder and click the "flash all.bat" file inside the folder. This will install 4.4.4 on your nexus 5. (connect nexus 5 to your computer first)
3) You're done. (During the installation process from flash.all, all your data will be deleted).
So next time you get bricked, you can rely on that flashall bat but in the future, read the general info in the forums about how to use adb and fastboot without flashall.bat so you can unbrick your phone in minutes.
Link for all the general info you need to know : http://forum.xda-developers.com/goo...urce-guides-info-threads-linked-read-t2784527
EDIT: Nvm, others have already explained above
rootSU said:
I really don't know much about multitom.. But just use adb to pull your sdcard data then factory reset.
You could return to stock but please don't use toolkit as mentioned above. I'm really not sure why people insist on this being then answer.
2 links in my signature. 1 about why toolkits are not the answer. Another about guides and info threads. You can read about fastboot and adb. There and never think about pesky toolkits again.
Also no such thing as partially bricked. Its either bricked or not. This is not. Just a boot loop
Click to expand...
Click to collapse
How could I go about pulling the sdcard and resetting that would save data
I have no idea at all how to do those things, kind of in the dark without being able to mount anything. I just don't want to lose anything if it's possible, and if I wipe the phone, I have a feeling MultiROM will still be there. I'll check out the links
snappycg1996 said:
How could I go about pulling the sdcard and resetting that would save data
I have no idea at all how to do those things, kind of in the dark without being able to mount anything. I just don't want to lose anything if it's possible, and if I wipe the phone, I have a feeling MultiROM will still be there. I'll check out the links
Click to expand...
Click to collapse
Like I said, there's a guides and info link in my signature. If you click that and then read "adb and fastboot. What is it?" - all your answers are there..
rootSU said:
Like I said, there's a guides and info link in my signature. If you click that and then read "adb and fastboot. What is it?" - all your answers are there..
Click to expand...
Click to collapse
Thank you so much for your help, I really do appreciate it. however I installed abd and I went into TWRP and went to abd sideload and I typed in CMD "abd devices" and it don't show my phone, it shows "adb devices attached" but no serial numbers. Is there something I must do before it will show up
btw, I always typed abd wrong lol and it never showed up. I felt dumb when I realized it's actually adb.
EDIT fastboot works just fine showing serial numbers adb still nothing..
snappycg1996 said:
Thank you so much for your help, I really do appreciate it. however I installed abd and I went into TWRP and went to abd sideload and I typed in CMD "abd devices" and it don't show my phone, it shows "adb devices attached" but no serial numbers. Is there something I must do before it will show up
btw, I always typed abd wrong lol and it never showed up. I felt dumb when I realized it's actually adb.
Click to expand...
Click to collapse
No idea what happens when you enter adb sideload. That's not what you should be doing. Just test adb from the main menu of TWRP. If no devices, driver, USB issue.
rootSU said:
No idea what happens when you enter adb sideload. That's not what you should be doing. Just test adb from the main menu of TWRP. If no devices, driver, USB issue.
Click to expand...
Click to collapse
When I enter recovery on my laptop and desktop, it makes the "usb failed sound" the du du dun. Not sure if that is my problem. Is there anyway to fix the issue I think it isn't possible with fastboot to put stuff on any storage.
snappycg1996 said:
When I enter recovery on my laptop and desktop, it makes the "usb failed sound" the du du dun. Not sure if that is my problem. Is there anyway to fix the issue I think it isn't possible with fastboot to put stuff on any storage.
Click to expand...
Click to collapse
Fix the drivers
rootSU said:
Fix the drivers
Click to expand...
Click to collapse
I remember when I first got my phone I had driver issues. Could you please point me in the direction of proper driver updates there is indeed a yellow exclamation mark on my phone under device manager.
snappycg1996 said:
I remember when I first got my phone I had driver issues. Could you please point me in the direction of proper driver updates there is indeed a yellow exclamation mark on my phone under device manager.
Click to expand...
Click to collapse
Its all in my "adb and fastboot" thread. I thought you were reading it?
snappycg1996 said:
I remember when I first got my phone I had driver issues. Could you please point me in the direction of proper driver updates there is indeed a yellow exclamation mark on my phone under device manager.
Click to expand...
Click to collapse
My friend, Google is your friend.
You cannot rely on someone else holding your hand through this entire process or you won't learn. Learning is essential.
Google universal nexus drivers. Install them and boom.
Sent from my Nexus 5 using Tapatalk 2
jmtjr278 said:
My friend, Google is your friend.
You cannot rely on someone else holding your hand through this entire process or you won't learn. Learning is essential.
Google universal nexus drivers. Install them and boom.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
The universal naked driver is already linked in my thread that he was supposed to be reading
jmtjr278 said:
My friend, Google is your friend.
You cannot rely on someone else holding your hand through this entire process or you won't learn. Learning is essential.
Google universal nexus drivers. Install them and boom.
Sent from my Nexus 5 using Tapatalk 2
Click to expand...
Click to collapse
LOL. They're directly linked in rootSU's thread.
EDIT: rootSU beats me to it again. One day my friend, one day, I'll learn to type faster.
rootSU said:
Its all in my "adb and fastboot" thread. I thought you were reading it?
Click to expand...
Click to collapse
Maybe my phone is just done for. I download that driver and another one from a different thread and everytime I try to update it is says "nothing is found for your Nexus 5". If I'm in the bootloader it shows "Android Composite Device" with no yellow exclamation mark, however when I try to update there is just says everything is up to date. So I know the drivers work, but what I don't get is why it won't update.
theesotericone said:
LOL. They're directly linked in rootSU's thread.
EDIT: rootSU beats me to it again. One day my friend, one day, I'll learn to type faster.
Click to expand...
Click to collapse
Maybe one day you'll have as little to do on a Sunday as me and you'll beat me tonight

stuck in bootloader device not recognized in adb

I was attempting to flash a factory image, and now am stuck in bootloader. I've attempted to flash the image via fastboot, but the terminal command gets stuck at waiting for device. I suspect something else is going on that is keeping me from communicating properly with the phone from the terminal commands but cant figure it out. I uninstalled and reinstalled adb/fastboot on my computer. When in terminal I am unable to find my device listed with adb devices command. This I think is the issue. How to do I get that to work?
Secure Boot is enabled Lock state is unlocked.
working with a mac
Also tried my wife's mac but nothing.
geekrd1 said:
I was attempting to flash a factory image, and now am stuck in bootloader. I've attempted to flash the image via fastboot, but the terminal command gets stuck at waiting for device. I suspect something else is going on that is keeping me from communicating properly with the phone from the terminal commands but cant figure it out. I uninstalled and reinstalled adb/fastboot on my computer. When in terminal I am unable to find my device listed with adb devices command. This I think is the issue. How to do I get that to work?
Secure Boot is enabled Lock state is unlocked.
working with a mac
Also tried my wife's mac but nothing.
Click to expand...
Click to collapse
ADB works in recovery. Fastboot works in bootloader. Macs shouldn't need any drivers as far as I remember.
Enter bootloader and type:
fastboot devices
With an s on the end
fastboot devices
rootSU said:
With an s on the end
fastboot devices
Click to expand...
Click to collapse
Yep that. Thanks man I haven't had my coffee yet.
no luck.
I get an error "could not get pipe properties"
I am at a loss since I can't get the phone to even be recognized by the computer. I just tried to reboot to recovery, and it shows me the twrp splash screen but then goes right to the opening google text with the unlocked padlock screen. Same as if I just try to boot the phone. I did have twrp flashed, but wanted a fresh start so I tried flashing in bootloader and got stuck.
geekrd1 said:
no luck.
I get an error "could not get pipe properties"
I am at a loss since I can't get the phone to even be recognized by the computer. I just tried to reboot to recovery, and it shows me the twrp splash screen but then goes right to the opening google text with the unlocked padlock screen. Same as if I just try to boot the phone. I did have twrp flashed, but wanted a fresh start so I tried flashing in bootloader and got stuck.
Click to expand...
Click to collapse
I'm gonna assume your on TWRP 2.8.2.0 It's a known issue that some are having with it. Try plugging your phone into your comp before you boot to recovery and see if it stays in revovery. Also try a different usb cable and a different port on the comp to try and solve the pipe error.
theesotericone said:
I'm gonna assume your on TWRP 2.8.2.0 It's a known issue that some are having with it. Try plugging your phone into your comp before you boot to recovery and see if it stays in revovery. Also try a different usb cable and a different port on the comp to try and solve the pipe error.
Click to expand...
Click to collapse
I've done all of those attempts. booting without being plugged in, booting while being plugged in, Trying 3 different cables.... still nothing.
geekrd1 said:
I've done all of those attempts. booting without being plugged in, booting while being plugged in, Trying 3 different cables.... still nothing.
Click to expand...
Click to collapse
Well I'm not a Mac guy but I found this that may or may not help:
http://forum.xda-developers.com/showthread.php?t=1129942
theesotericone said:
Well I'm not a Mac guy but I found this that may or may not help:
http://forum.xda-developers.com/showthread.php?t=1129942
Click to expand...
Click to collapse
Thanks, I think that helped. At least I've got the phone working now
theesotericone said:
Yep that. Thanks man I haven't had my coffee yet.
Click to expand...
Click to collapse
Hope you've had a chance to have your coffee by now. I've been sucking mine down all day while trying to fix the problem :good:

Please halp! Phone possibly bricked

flashed a rom earlier today, and magisk wasnt passing the safteynet check for some reason, so i flashed Huawei-Prop-Fix-v1.1_2017082601.zip and now my phone wont boot at all. nothing even comes up on screen. it just keeps vibrating and resetting with a black screen and lit backlight. idk what to do, kinda freaking out ! please someone halp :'( :crying::crying::crying::crying::crying:
--UPDATE-- SOMEHOW I GOT IT IN FASTBOOT MODE, PLEZ SOMEONE TELL ME WHAT I CAN DO
if you in fastboot.. install TWRP via ADB.. download and flash stock firmware back..
think the chinese version is safest, then just rebrand device and load new firmware
none24 said:
flashed a rom earlier today, and magisk wasnt passing the safteynet check for some reason, so i flashed Huawei-Prop-Fix-v1.1_2017082601.zip and now my phone wont boot at all. nothing even comes up on screen. it just keeps vibrating and resetting with a black screen and lit backlight. idk what to do, kinda freaking out ! please someone halp :'( :crying::crying::crying::crying::crying:
--UPDATE-- SOMEHOW I GOT IT IN FASTBOOT MODE, PLEZ SOMEONE TELL ME WHAT I CAN DO
Click to expand...
Click to collapse
If you can get into fastboot follow this post https://forum.xda-developers.com/mate-9/how-to/hacking-customizing-managing-huawei-t3589996. Take your time and read it carefully then follow the steps.
vijer said:
If you can get into fastboot follow this post https://forum.xda-developers.com/mate-9/how-to/hacking-customizing-managing-huawei-t3589996. Take your time and read it carefully then follow the steps.
Click to expand...
Click to collapse
follow which instructions? and im in fastboot mode but my screen is still black
redhotneo said:
if you in fastboot.. install TWRP via ADB.. download and flash stock firmware back..
think the chinese version is safest, then just rebrand device and load new firmware
Click to expand...
Click to collapse
im in fastboot but my screen is still black. i can install twrp but when i reboot i cant get to it. the phone stays black screened and keeps rebooting
none24 said:
follow which instructions? and im in fastboot mode but my screen is still black
Click to expand...
Click to collapse
The link I provided has a lot of information about flashing stock firmware. At this point you probably want a short answer but it would be best if you read the whole post. That way you will have more knowledge about what you are doing.
You need the firmware for your device.
You need TWRP
You need to know how to use ADB
I could try to explain all of this here but it is already explained in the post I linked to. So try reading it carefully, and then ask questions about the parts you don't understand.
vijer said:
The link I provided has a lot of information about flashing stock firmware. At this point you probably want a short answer but it would be best if you read the whole post. That way you will have more knowledge about what you are doing.
You need the firmware for your device.
You need TWRP
You need to know how to use ADB
I could try to explain all of this here but it is already explained in the post I linked to. So try reading it carefully, and then ask questions about the parts you don't understand.
Click to expand...
Click to collapse
no lol a short answer is the last thing i need right now, i need details. its not that i dont understand it, my screen is black so i cannot see anything <---- thats the main issue.
I cant access ADB i can only get into fastboot because again my screen isnt showing anything at all. no bootlogo no nothing. i cant get into twrp only fastboot. i know how to use those things but if i cant get into recovery then what else can i do? my only available access is fastboot
none24 said:
no lol a short answer is the last thing i need right now, i need details. its not that i dont understand it, my screen is black so i cannot see anything <---- thats the main issue.
I cant access ADB i can only get into fastboot because again my screen isnt showing anything at all. no bootlogo no nothing. i cant get into twrp only fastboot. i know how to use those things but if i cant get into recovery then what else can i do? my only available access is fastboot
Click to expand...
Click to collapse
I guess I'm confused, if you can get to fastboot you should be able to issue ADB commands.
vijer said:
I guess I'm confused, if you can get to fastboot you should be able to issue ADB commands.
Click to expand...
Click to collapse
adb commands arent available in fastboot.. its only fastboot commands. adb is only available when the phone is booted into the OS
none24 said:
adb commands arent available in fastboot.. its only fastboot commands. adb is only available when the phone is booted into the OS
Click to expand...
Click to collapse
Well in theory you should be able to issue ADB commands in fastboot. But if you can't, then try using Huawei's Hisuite to recover the phone.
vijer said:
Well in theory you should be able to issue ADB commands in fastboot. But if you can't, then try using Huawei's Hisuite to recover the phone.
Click to expand...
Click to collapse
in theory yes, but sadly it doesnt work like that. ive tried. also HiSuite says its not compatible and the compatibility list only has 2 devices that i think are tablets.
guess its time to return to samsung i loved this phone, but note8 here i come.... its been real guys o/
none24 said:
in theory yes, but sadly it doesnt work like that. ive tried. also HiSuite says its not compatible and the compatibility list only has 2 devices that i think are tablets.
guess its time to return to samsung i loved this phone, but note8 here i come.... its been real guys o/
Click to expand...
Click to collapse
return for warranty.. they will sort out... maybe ur screen is dead or hardware issue..
also get the phone in off state.. think its volume up + power...
then hold down both volume buttons + power and wait for boot.. should take you to recovery screen.. if your screen is active then u have some hope
vijer said:
Well in theory you should be able to issue ADB commands in fastboot. But if you can't, then try using Huawei's Hisuite to recover the phone.
Click to expand...
Click to collapse
in fastboot mode you can only issue fastboot commands.
adb commands are used in recovery/booted system.
@none24 let the phone stay on until it dies then plug in usb and see if it boots after that.

I bricked my phone

I accidentally erased the phones system from fox recovery. (dont ask how im dum) Its bricked now and is in a boot loop of some sort. It cant communicate with my pc which ik works with it as i used this pc to root it in the first place. Any help is appreciated. Its not overly important as its my old phone that i was messing around on.
If adb doesn't work, try to use filemanager to add files to your internal storage. Usually this should always work, as the device would be detected as MTP.
possiblyLopsided said:
I accidentally erased the phones system from fox recovery. (dont ask how im dum) Its bricked now and is in a boot loop of some sort. It cant communicate with my pc which ik works with it as i used this pc to root it in the first place. Any help is appreciated. Its not overly important as its my old phone that i was messing around on.
Click to expand...
Click to collapse
Is there anything preventing you from booting into OrangeFox, and flashing your ROM again?
DarthJabba9 said:
Is there anything preventing you from booting into OrangeFox, and flashing your ROM again?
Click to expand...
Click to collapse
I tried to boot to recovery but it just turns the screen on (nothing is displayed) and starts to "boot" after a bit it stops and retries until it dies. anytime I try to hold buttons to go to recovery or fast boot it just restarts its "boot" process. i cant get it to connect to my pc either. it doesn't show up in the USB tool or device manager.
posiblyLopsided said:
I tried to boot to recovery but it just turns the screen on (nothing is displayed) and starts to "boot" after a bit it stops and retries until it dies. anytime I try to hold buttons to go to recovery or fast boot it just restarts its "boot" process. i cant get it to connect to my pc either. it doesn't show up in the USB tool or device manager.
Click to expand...
Click to collapse
Simply erasing the "system" should not cause any of these problems that you are describing. The system partition is totally isolated from the recovery partition, the bootloader, and every other partition. You might want to expand on what precisely you erased, and how exactly you erased it.
DarthJabba9 said:
Simply erasing the "system" should not cause any of these problems that you are describing. The system partition is totally isolated from the recovery partition, the bootloader, and every other partition. You might want to expand on what precisely you erased, and how exactly you erased it.
Click to expand...
Click to collapse
that's an excellent question and I'm not entirely for sure. i rly was not thinking at all when i was doing this but basically i was trying to factory reset and somehow got into recovery mode. i think I went to wipe and erased everything. i am not for sure tho. like said I was rly not thinking at all when I was doing this.
Thank you so much for helping me with my stupidity.
posiblyLopsided said:
that's an excellent question and I'm not entirely for sure. i rly was not thinking at all when i was doing this but basically i was trying to factory reset and somehow got into recovery mode. i think I went to wipe and erased everything. i am not for sure tho. like said I was rly not thinking at all when I was doing this.
Thank you so much for helping me with my stupidity.
Click to expand...
Click to collapse
None of this should affect the boot loader. So you should boot into fastboot mode, flash the recovery image, boot into it, and then go on from there.
Full details of what to do are available here: https://wiki.orangefox.tech/en/guides/installing_orangefox ("Via fastboot, and the recovery")
I have tried. i cant even get into fastboot. i will try again.
DarthJabba9 said:
None of this should affect the boot loader. So you should boot into fastboot mode, flash the recovery image, boot into it, and then go on from there.
Full details of what to do are available here: https://wiki.orangefox.tech/en/guides/installing_orangefox ("Via fastboot, and the recovery")
Click to expand...
Click to collapse
ok. i got my phone to talk with my pc. i was able to maybe boot into fastboot. im not for sure because the screen is still black but the computer saw it as a usb device. the only problem is that it says the usb device is is not working and is malfunctioning. i think that its because i dont have the right drivers. however i need yo connect my phone properly to install the right drivers which i cant do. maybe i am doing this wrong. im trying to use the xiaomi suite. i tried manually installing but windows says the best drivers are already installed.
Edit: Great news. i got it to go to fastboot. i had a faulty cable. its working now. im getting orange fox rn.
posiblyLopsided said:
...Edit: Great news. i got it to go to fastboot. i had a faulty cable. its working now. im getting orange fox rn.
Click to expand...
Click to collapse
Excellent.
PS: no harm in hitting the "thanks" button ...
thanks for your help. i got it to work and i have miui flashed and running. again thank u for raking ur time to help with my stupidity.
posiblyLopsided said:
thanks for your help. i got it to work and i have miui flashed and running. again thank u for raking ur time to help with my stupidity.
Click to expand...
Click to collapse
:good:

Categories

Resources