The reason i am here is to ask for help. I have driven myself crazy in solving this complicated problem i have.
Ok
i own a moto g4 xt1624 and though about rooting it for all the reasons why people root.
Got the bootloader code unlocked the bootloader and installed twrp recovery file.
Went ahead and followed all the steps to install Lineage os 14.1 steps from their offical site.
Done all Flashed the file and the device is stuck on a screen now Saying :
Your device has been unlocked and can't be trusted.
ID:bad key
Tried every forum on here the device doesn't seem to connect to pc . No showing up in device manager also
Installed all moto usb and qualcomm 9008 drivers .
The device just doesn't enter into fastboot mode no matter what i do
Pls. suggest something .
Found the solution try and go to download mode in your phone by pressing the both volume keys simultaneously and then connect the usb already connected to pc to the phone and you will boot normally onto twrp recovery or any recovery you might have installed
Related
Hi, I've just recently switched over from iphone to android so I'm still new to the whole system. Anyway I've been trying to root my phone for the past 2 days to no avail so I'm at my wits end here. Before I start my phone is from korea which I don't know if whether or not impacts its ability to be rooted, I've done all the basics like enable USB debugging from dev mode, install samsung usb drivers, open ODIN in admin mode and allow MTP to computer. My Device details are below:
>Baseband version : G906SKSU1CPF1
>KERNEL : 3.10.40-8533426
>BUILD NUMBER : MMB29M.G906SKSU1CPF3
So anyway I first tried flashing using CF autoroot for sm-G906S with odin which while it said it was passed and was successful on pc it would be stuck on the samsung logo with a message at the top left that said :
>Recovery booting
>Recovery is not seandroid enforcing
>set warranty bit recovery
So then I tried flashing TWRP custom recovery and putting Super user zip in the internal storage which although got my phone back to working order still wouldnt let me root as the process required me to go to recovery mode from the fastboot mode after it was done flashing (I tried both with and without autoreboot), however once the flashing was done on fastboot I couldn't get to recovery mode no matter how long I held the Vol up/power/home button combination and when i tried it after rebooting it would show normal recovery mode hence there was no way to install the Super User. (Also attempted this with phils recovery)
I then tried to do the TWRP method using adb with command prompt however it would get stuck saying waiting for device when i tried to flash and needless to say kingroot also failed.
At this point as far I've gone through all the methods I could find for my particular device. Would greatly appreciate any insight or advice regarding this problem.
Thanks
start reading from here http://forum.xda-developers.com/gal...ner-thread-t2807639/post68725608#post68725608
Hello people.
So i got a custom recovery (TeamWin project) for my Samsung Galaxy A5 2016 [A510F] and disabled OEM Unlock on purpose, because i thought it wouldn't show the red line up in the bootscreen.
After trying to reboot, it wouldn't reboot, and i can't go into Recovery mode. I can't install any custom firmware too, because i've got the OEM Unlock set to "off"
Can someone please help, i can't find a topic similiar to my case, where i've bricked my phone and have no idea what to do.
Also fastboot doesn't recognize my device even though the right drivers are installed.
Have you tried Download mode ( vol - home button and power button) ?
Viesuliss said:
Hello people.
So i got a custom recovery (TeamWin project) for my Samsung Galaxy A5 2016 [A510F] and disabled OEM Unlock on purpose, because i thought it wouldn't show the red line up in the bootscreen.
After trying to reboot, it wouldn't reboot, and i can't go into Recovery mode. I can't install any custom firmware too, because i've got the OEM Unlock set to "off"
Can someone please help, i can't find a topic similiar to my case, where i've bricked my phone and have no idea what to do.
Also fastboot doesn't recognize my device even though the right drivers are installed.
Click to expand...
Click to collapse
Just download official firmware and flash with odin. (Make sure not to downgrade os version. )
go to downloadmode, be sure drivers are installed, COM must be green,flash firmware with odin "only PDA", return into bootlader after reboot, flash twrp, boot into recovery mode done
Same thing happened to me.
Don't search for any file, the solution is very simple: download Samsung Smart Switch (only Windows, Mac version didnt work for me).
On menu click "Others" then "Emergency software recovery". Write A510F and then your phone Serial Number. Wait 30/60 mins ?
Sent from my SM-A510F using XDA-Developers Legacy app
I was trying to install custom rom and my device got bricked, now its stuck in boot logo. I am trying to install a rom but tried with qfil/qspt but device is not getting detected. Once I was able to install qualcomm hs-qd loader 9008(com 3) but it was not working so I removed it and now I am unable to install it again.
I tried to enter the recovery mode by flashing TWRP recovery, My device was prerooted and already i had install TWRP but a device was brick I was unable to access it. After flashing TWRP, I got the Mount screen of teamwin but touch is not working.its saying unmodified system partition detected. but after that I am unable to got to next step to install a rom in my device as qualcomm hs-qd loader 9008 not getting installed. Please guide me, I am new in all this,need expert help. thank you
@amitpandey, have a look AT THIS.
Still not detecting by my pc. Also unable to disable driver signature as in my laptop no option of troubleshooting option available in advance startup menu.
Hi everyone,
For some stupid reason a reset the file system i now I'm stuck in the LG logo.
1. I can enter in download mode - in Device manager the PC recognized as LGE AndroidNet USB Serial Port (41)
2. I can enter in recovery mode (Cyanogenmod recovery, which is very based) - in Device manager the PC recognized as Android ADB Interface
So far, so good. BUT. I'tried to flash the phone with LG FlashTool 2014 and i'm stuck at 2%. Ok, i was tried the fix with FixedDownloadcmode.bat, but when nothing is uploading on the phone (which by ADB is recognized as sideload when i'm in recovery mode and apply the ADB connection). I tried to push by ADB but nothing is uploading - error: protocol.......
LGUP recognized my phone as unknown, so this method is not working now.
Via ADB i can't send even TWRP recovery, which is so much flexible than cyanogenmod recovery.
I will be thankful for any help from your side.
Thank you in advance!
https://forum.xda-developers.com/lg-g2/general/alternative-fix-lg-flashtool-stuck-2-t3605753
Same happened to me. Try this if you can reach your storage
https://forum.xda-developers.com/showthread.php?t=2663369
https://www.youtube.com/watch?v=Lg693AYgoTo
ATT 4.4.2 KitKat:
https://mega.nz/#!n0RTUYZD!MVntiPxuyW...
ATT 4.2.2 JellyBean:
https://mega.nz/#!e5RERS4L!FjZyopcvwM...
T-Mobile 4.2.2 JellyBean:
https://mega.nz/#!qsRSBDwD!KKCETp41O1...
Modified DLL file if nothing else works:
https://mega.nz/#!f5xTGKrC!ifBCOAnK4j...
I had a very similar problem with it getting stuck at the logo after pushing supersu to the phone. I followed Supersport every single step of the way in his video. I think his links are the only valid ones online now, so just download them and reflash your phone. If your G2 is anything like mine, drivers will never appear to be installed correctly and it never restarts, only shuts down.
His method is:
1) Download and install LG drivers on PC
2) Download and install the flash tool and patch it
3) Download and load the .tot and .dll files into the flash tool
4) Enter download mode on G2 by holding volume up while connecting USB
5) Switch G2 Com port to 41 in device manager
6) Once Flash tool shows that all ports are ready, power down G2 and disconnect
7) Hold volume up and reconnect to get back into download mode
8) LG Flash tool starts flashing
9) Complete
Note: If your G2 was screwed up as bad as mine, it'll say failed but all the main system files will load to the device before it restarts and it'll even shut itself off while doing it's installation on first reboot. Mine somehow was still revived from this state with his method.
I forgot to add this but couldn't edit my post for some reason.
For D800:
Master archive of 5 files needed to do this:
https://www.androidfilehost.com/?fid=95747613655047114
So I'm quite a noob when it comes to flashing/recoveries/bootloaders and things like that, and that's most likely the reason why I got myself into this situation. Anyways my axon 7 (which I bought in China a year ago) was running fine yesterday, just a little bit slow. I had installed TWRP on it, and flashed the US rom along with SuperSU root. However last night was when things all went wrong.
I tried to flash the xposed installer from twrp which caused me to not get stuck on the AXON boot screen when I tried to restart.
Seeing that my phone was now softbricked, I thought since my phone was already running so slow, maybe I should take this opportunity to install lineage os and at the same time unbrick my phone. Win win right?
But when I tried to flash lineage os, I got the red error 7 message and problems with mounting /system. I went into the zip and changed the updated script and tried reflashing the new lineage os zip. That didn't worked and I still got error 7 messages.
So I this point I was quite desperate to get my phone back so I tried to reinstall the stock axon 7 rom which didn't work as I ended up with unable to mount /system errors.
I tried to reinstall twrp but my pc wouldn't recognize my phone while it was in fastboot mode.
I tried this tutorial IGNORETHISTEXTCASUEICANTPOSTLINKSYETJUSTCOPYTHELINKTHATCOMESAFTERhttps://m.youtube.com/watch?v=T-7neHzSIvc but got stuck on the step where I needed to reformat my data partition as exfat (the progress bar just kept going). After waiting 3 hours for it to format, I thought it was frozen or something because the guy in the video was able to format it instantly.
So I force restarted my axon 7 and now I'm here:
1. Most of the time when I restart my phone, it gets stuck on the zte logo
2. occasionally it gives me the option menu (with power off, fastboot, recover, etc.)
3. If try to use fastboot, my pc won't recognize my phone
4. If I use recovery, I get stuck on the teamwin screen, but my computer seems to recognize my phones presence, in the fastboot command prompt the "adb devices" command displays my phone as "10109dd offline", if I run any other command such as reinstalling TWRP, the command gets stuck at "waiting for device"
5. Obviously can't boot into android cause my whole system partition is wiped
Anyways that's the state I'm currently in (all because I wanted to install xposed installer ) and I would appreciate any suggestions!
Make sure all your phone drivers and adb are up to date.
Also try the Zadig drivers these might help too.
In Windows device manager it should show as,
Qualcomm HS-USB QDLoader 9008"
If you get stuck you can always try using an Edl package.
I have and Edl help page here>
https://forum.xda-developers.com/axon-7/help/bad-flash-help-page-axon-7-t3839700
Syberclone said:
Make sure all your phone drivers and adb are up to date.
Also try the Zadig drivers these might help too.
In Windows device manager it should show as,
Qualcomm HS-USB QDLoader 9008"
If you get stuck you can always try using an Edl package.
I have and Edl help page here>
https://forum.xda-developers.com/axon-7/help/bad-flash-help-page-axon-7-t3839700
Click to expand...
Click to collapse
Holy moly, you saved my life Syberclone! I was able to flash back my rom through EDL mode and my A7 is saved! :angel: Thanks a million!:good: