[Q] Nexus stucked on google logo - Nexus 7 (2013) Q&A

Hi I'm a new member so I hope this is the right section. My nexus 7 2013 is stucked at the google logo screen, I can enter in fastboot mode but not in recovery mode, if I try the device reboots and it stucks on google logo again. I've not usb debug activated. Can anyone help me?

Francesco Amato said:
Hi I'm a new member so I hope this is the right section. My nexus 7 2013 is stucked at the google logo screen, I can enter in fastboot mode but not in recovery mode, if I try the device reboots and it stucks on google logo again. I've not usb debug activated. Can anyone help me?
Click to expand...
Click to collapse
Hey, trust me, I feel your pain! I've been dealing with this issue for a week. I could get into the bootloader, but recovery wouldn't work and no matter what I flashed, I couldn't get past the google logo.
Today, I tried it again and it worked. I was able to get it to reinstall and boot.
Try this: http://forum.xda-developers.com/showthread.php?t=2381582
Just download the file there, boot your nexus into the bootloader, connect it to your computer, and click the "dead_nexus7" file.
That's what worked for me. I have no idea if it'll work for you because I tried the exact same thing probably a dozen times and it never worked until now..
Good luck!

nexusjas said:
Hey, trust me, I feel your pain! I've been dealing with this issue for a week. I could get into the bootloader, but recovery wouldn't work and no matter what I flashed, I couldn't get past the google logo.
Today, I tried it again and it worked. I was able to get it to reinstall and boot.
Try this: http://forum.xda-developers.com/showthread.php?t=2381582
Just download the file there, boot your nexus into the bootloader, connect it to your computer, and click the "dead_nexus7" file.
That's what worked for me. I have no idea if it'll work for you because I tried the exact same thing probably a dozen times and it never worked until now..
Good luck!
Click to expand...
Click to collapse
Sorry but I have to follow the guide or only your suggestion?

Francesco Amato said:
Sorry but I have to follow the guide or only your suggestion?
Click to expand...
Click to collapse
Follow the guide, but skip step 5 and do 6 instead. Since you can't get into your OS, you can't have debugging enabled, so step 5 won't work. Step 6 is for people who can only get into the bootloader.

nexusjas said:
Follow the guide, but skip step 5 and do 6 instead. Since you can't get into your OS, you can't have debugging enabled, so step 5 won't work. Step 6 is for people who can only get into the bootloader.
Click to expand...
Click to collapse
It doesn't work, when it sends bootloader it fails and says FAILED <remote:Bootloader is locked.> then it reboot into bootloader and says erasing 'system' but it doesn't do anything... :crying:
:

Francesco Amato said:
It doesn't work, when it sends bootloader it fails and says FAILED <remote:Bootloader is locked.> then it reboot into bootloader and says erasing 'system' but it doesn't do anything... :crying:
:
Click to expand...
Click to collapse
You have to unlock the bootloader.
Go to the folder and open a command prompt from there. Usually you can right click and say open command prompt. If that's not an option go to start > run and type cmd. Hit enter. Type "cd <path of folder>" -- mine, for example would be "cd C:\Desktop\Nexus7_2013_KTU84P_Restore" (no quotes) - then hit enter.
Then type: fastboot oem unlock
hit enter.
On your nexus, a screen will pop up. Use the volume key to navigate to the option that says you want to unlock it. Hit the power key once to select that option.
When it's done, go back into the bootloader and open the dead_nexus7 file on your computer.

nexusjas said:
You have to unlock the bootloader.
Go to the folder and open a command prompt from there. Usually you can right click and say open command prompt. If that's not an option go to start > run and type cmd. Hit enter. Type "cd <path of folder>" -- mine, for example would be "cd C:\Desktop\Nexus7_2013_KTU84P_Restore" (no quotes) - then hit enter.
Then type: fastboot oem unlock
hit enter.
On your nexus, a screen will pop up. Use the volume key to navigate to the option that says you want to unlock it. Hit the power key once to select that option.
When it's done, go back into the bootloader and open the dead_nexus7 file on your computer.
Click to expand...
Click to collapse
When I press the power button on yes the device stuckes and I can't do anything:crying:

This recently happened to me. I returned it to Asus and they replaced the main board. I've read elsewhere that this isn't terribly uncommon.
Sent from my Nexus 7 using Tapatalk

Related

[Q]Unlocking Bootloader Step 11-13

So i have researched over and over about unlocking bootloader, how to gain S-off, and rooting.I decided to unlock the bootloader. I struggled through some of it, as i tried on a mac first then switched to a Windows XP system. I finally got to step 12 on the unlocking process from the HTC website. After i type in fastboot flash unlocktoken Unlock_code.bin it says that my phone should ask me whether i want to actually unlock or abort the process(step13). Yet, my phone never does step 13? I have searched and searched and could not find any answers, i even tried calling HTC(NO help).
So, does anyone know of any way to fix this?
Thank you anyone who can help with my situation
SargentRudy said:
So i have researched over and over about unlocking bootloader, how to gain S-off, and rooting.I decided to unlock the bootloader. I struggled through some of it, as i tried on a mac first then switched to a Windows XP system. I finally got to step 12 on the unlocking process from the HTC website. After i type in fastboot flash unlocktoken Unlock_code.bin it says that my phone should ask me whether i want to actually unlock or abort the process(step13). Yet, my phone never does step 13? I have searched and searched and could not find any answers, i even tried calling HTC(NO help).
So, does anyone know of any way to fix this?
Thank you anyone who can help with my situation
Click to expand...
Click to collapse
did you place the bin file you got form your email into the folder where you have adb and all the other necessary files?
1. Download the .bin file from the attachment
2. Place the .bin file "as itself" in the folder where you kept the 3 files (fastboot.exe , adb.exe etc)
For eg. If it is in C:/Android place it there.
3. Now note two things before rebooting into recovery (a) ENABLE USB DEBUGGING (b) DISABLE FASTBOOT
4. Now power off
5. Press vol- and Power button
6. Wait until initial checking by HBOOT is over
7.Select Fastboot
8. Connect USB ( When USB is connected you can confirm it by the changing of heading "FASTBOOT" to "FASTBOOT USB" in red color in the phone )
9. In computer Run "cmd" and type in the command as such
You will see the notification in phone and acceppt it and that's it... It's Done Congratzz!!!
POlease do thank if this helped
krishnanms said:
1. Download the .bin file from the attachment
2. Place the .bin file "as itself" in the folder where you kept the 3 files (fastboot.exe , adb.exe etc)
For eg. If it is in C:/Android place it there.
3. Now note two things before rebooting into recovery (a) ENABLE USB DEBUGGING (b) DISABLE FASTBOOT
4. Now power off
5. Press vol- and Power button
6. Wait until initial checking by HBOOT is over
7.Select Fastboot
8. Connect USB ( When USB is connected you can confirm it by the changing of heading "FASTBOOT" to "FASTBOOT USB" in red color in the phone )
9. In computer Run "cmd" and type in the command as such
You will see the notification in phone and acceppt it and that's it... It's Done Congratzz!!!
POlease do thank if this helped
Click to expand...
Click to collapse
yes do that it will work for sure, but make sure you have done the first and second step
i just tried it on a newer computer that has windows 7, but when i get to step 12 and have to type fastboot flash unlocktoken Unlock_code.bin it just says < waiting for device > and nothing happens...i am on the bootloader screen (battery out, put back in, volume - and power button). What else could i try?
Ahh, i feel VERY stupid now. I hadn't realized i had to turn off fastboot. Thanks all for the help! This took me over a week to figure out i had to turn off fast boot -_-
but i finally got it to work thanks to you guys thanks for all the help !
But my question is can i turn on fastboot after i do all this? I hate taking about 2 minutes just for the phone to boot up.
Yes you can. But all custom roms do not have this feature.
SargentRudy said:
Ahh, i feel VERY stupid now. I hadn't realized i had to turn off fastboot. Thanks all for the help! This took me over a week to figure out i had to turn off fast boot -_-
but i finally got it to work thanks to you guys thanks for all the help !
But my question is can i turn on fastboot after i do all this? I hate taking about 2 minutes just for the phone to boot up.
Click to expand...
Click to collapse
yes, only for stock roms
Don't forget to thanks =D

[Q] Is there a way to remove 'fastboot'?

I want to remove 'fastboot' from my device, because every time I try to enter 'Download mode' it goes into 'fastboot mode'.
ErikBoonstra said:
I want to remove 'fastboot' from my device, because every time I try to enter 'Download mode' it goes into 'fastboot mode'.
Click to expand...
Click to collapse
Would a full reset/flash of OEM solve the problem? Seems doubtful it is a hardware issue, providing all of the buttons work normally at all other times..
Ask @rodrigofd, he seems to have had a great hands-on with removing fastboot
You cannot remove fastboot. Fastboot is a fundamental part of android.
What you want to do is to stop your G3 from botting into fastboot instead of download mode, to do this you have to do the reverse of what you did to enable fastboot mode in the first place.
To enable fastboot on the G3 you have to remove the LAF partition (download mode), so to get download mode back you have to restore the LAF partition. There are plenty of threads on xda explaining this process, just go to any of the fastboot threads, or any of the roms threads where a tethered rom is required.
I already found a way to fix it, still using fastboot mode. But I was able to flash trough LG Flash Tool 2014. I didn't have to delete my partitions or so what. If someone is interested in a tutorial send a reply here or a PM and I will make one!
ErikBoonstra said:
I already found a way to fix it, still using fastboot mode. But I was able to flash trough LG Flash Tool 2014. I didn't have to delete my partitions or so what. If someone is interested in a tutorial send a reply here or a PM and I will make one!
Click to expand...
Click to collapse
I sent you a PM!
ErikBoonstra said:
I want to remove 'fastboot' from my device, because every time I try to enter 'Download mode' it goes into 'fastboot mode'.
Click to expand...
Click to collapse
This method is temporary. If you want to put your device in DOWNLOAD mode from cmd, this method is for you. Seach over google for Send_Command.exe file. Once you got this file, Go to directory where you have this file. Hold shift key & right click, in context menu, click on "open command window here". Then Type this command "Send_Command \\.\Port#" e.g. "Send_Command \\.\COM6" (You can find port number from device manager). If command executed successfully, you'll see a msg something like "ENTER, LEAVE". cmd cursor is blinking next to # symbol. Just type ENTER. Your device will rebooted to DOWNLOAD mode. I'll use this method because my device volume up key is not functioning properly. I hope this helps.
adnanahmed008 said:
This method is temporary. If you want to put your device in DOWNLOAD mode from cmd, this method is for you. Seach over google for Send_Command.exe file. Once you got this file, Go to directory where you have this file. Hold shift key & right click, in context menu, click on "open command window here". Then Type this command "Send_Command \.\Port#" e.g. "Send_Command \.\COM6" (You can find port number from device manager). If command executed successfully, you'll see a msg something like "ENTER, LEAVE". cmd cursor is blinking next to # symbol. Just type ENTER. Your device will rebooted to DOWNLOAD mode. I'll use this method because my device volume up key is not functioning properly. I hope this helps.
Click to expand...
Click to collapse
Hi! Thanks for reply, if i reinstall the original kdz file im using right now, will i solve this fastboot problem?
Pistacho123Lol said:
Hi! Thanks for reply, if i reinstall the original kdz file im using right now, will i solve this fastboot problem?
Click to expand...
Click to collapse
I have F460L recently. It get bricked. When i turn it on, it goes to fastboot mode. I didn't find necessary files for F460 variants to debrick. So, i take my device to local market, there's a guy, he fixed my device. After that, my device is working. Device get back its DOWNLOAD mode (fastboot gone). So you try flashing stock firmware. I hope, this works for you.
Also, check whether your device goes to DOWNLOAD mode or not. If DOWNLOAD mode working, then its beautiful. Otherwise, your partitions are corrupted. You then flash *.imgs or *.bin files from fastboot mode (You can find thread on XDA about that). Before doing anything, search a lot. Write down any steps, you are going to do. Because, if you are not clear, then this will create more problem.

phone is dead. only access to fastboot

phone is dead
when plug in for charging it shows charging logo then restart and restart again. loop
second when i try to go in recovery , again it restart never go to recovery.
i can only access fastboot option.
i never try to root or unlock bootloader.
my phone is locked.
arixeon said:
phone is dead
when plug in for charging it shows charging logo then restart and restart again. loop
second when i try to go in recovery , again it restart never go to recovery.
i can only access fastboot option.
i never try to root or unlock bootloader.
my phone is locked.
Click to expand...
Click to collapse
i had the same problem please some one answer
arixeon said:
phone is dead
when plug in for charging it shows charging logo then restart and restart again. loop
second when i try to go in recovery , again it restart never go to recovery.
i can only access fastboot option.
i never try to root or unlock bootloader.
my phone is locked.
Click to expand...
Click to collapse
1. What phone model? What version of firmware 5.0.2 or 6.0.1?
Yes, same this with me. 6.0. I tried reset, but reset is not working. So I unlocked device , installed twrp, but twrp sometimes starts and only for few seconds. Mostly phone is either stuck in logo, or just shuts down after boot vibration. No luck in recovery. My phone crashed suddenly and got into this situation.
gSingh05 said:
Yes, same this with me. 6.0. I tried reset, but reset is not working. So I unlocked device , installed twrp, but twrp sometimes starts and only for few seconds. Mostly phone is either stuck in logo, or just shuts down after boot vibration. No luck in recovery. My phone crashed suddenly and got into this situation.
Click to expand...
Click to collapse
you unlocked your device after it was dead or before
because mine 820 is locked and i cant do anything
arixeon said:
you unlocked your device after it was dead or before
because mine 820 is locked and i cant do anything
Click to expand...
Click to collapse
After it was dead. I got into fastboot. And from linux , using tutorial from HTC unlocked the device.
gSingh05 said:
After it was dead. I got into fastboot. And from linux , using tutorial from HTC unlocked the device.
Click to expand...
Click to collapse
please share the link or method to unlock bootloader while phone is dead. in current situation im unable to write or update the firmware .
arixeon said:
please share the link or method to unlock bootloader while phone is dead. in current situation im unable to write or update the firmware .
Click to expand...
Click to collapse
http://www.htcdev.com/bootloader
You have to register.
For Windows: Install HTC drivers, HTC Sync Manager(optional), fastboot, adb.
For linux: Install android-tools
Put phone into Hboot -> Fastboot.
Connect to PC and from cmd/terminal you have to execute commands as told by HTC site.
> fastboot oem get_identifier_token
This will give you a string , copy paste from '<<Identifier Token start>>' to '<<Token End>>' , only this column, no prefix.
Paste this into website. There will be text box while following steps.
You will get a file in email attachment. It will be something like this 'Unlock_code.bin'
And also the link to further steps will be provided.
> fastboot flash unlocktoken Unlock_code.bin
You will get option on phone screen. 'Yes' 'No'. Use volume button and select Yes.
and its done.
It hardly takes a minute
gSingh05 said:
http://www.htcdev.com/bootloader
You have to register.
For Windows: Install HTC drivers, HTC Sync Manager(optional), fastboot, adb.
For linux: Install android-tools
Put phone into Hboot -> Fastboot.
Connect to PC and from cmd/terminal you have to execute commands as told by HTC site.
> fastboot oem get_identifier_token
This will give you a string , copy paste from '<<Identifier Token start>>' to '<<Token End>>' , only this column, no prefix.
Paste this into website. There will be text box while following steps.
You will get a file in email attachment. It will be something like this 'Unlock_code.bin'
And also the link to further steps will be provided.
> fastboot flash unlocktoken Unlock_code.bin
You will get option on phone screen. 'Yes' 'No'. Use volume button and select Yes.
and its done.
It hardly takes a minute
Click to expand...
Click to collapse
thanks
now i unlocked the bootloader abd installed recovery but unable to enter in the recovery.. it shows that entering recovery and then restart loop .
arixeon said:
thanks
now i unlocked the bootloader abd installed recovery but unable to enter in the recovery.. it shows that entering recovery and then restart loop .
Click to expand...
Click to collapse
Yes it happens sometimes.
Make sure the recovery step was complete. For win: The .exe cmd should exit on clicking enter or automatic, till then don't remove the phone.
Try some combinations:
- turn phone OFF from Hboot then start recovery
- if screen shows 'entering recovery' let it be , wait for reboot or shutdown
- try alternative options of 'reset' and 'recovery' both will get you to twrp
- remove sdcard then try
- check charging
- don't try if overheating, let the phone be in normal temperature.
I had similar problem, but trying combos started twrp.
The mistake I did was to wipe everything. Don't do that, try to wipe cache, the first default option provided by twrp and start phone. (no sdcard/sim)
I was able to install Tomal's Discovery ROM but after some time phone again rebooted and stuck in loop.
For any restore/flash use internal memory. SDcard failed to work for me ( i tried many different sdcards).

XT1676 - Stuck in Unlocked Bootloader, after Wipe Cache(?!)

Some informations at first:
XT1676 Moto G5, Fine Gold, 16GB
(TYPE M2675/ FCC ID: <known>/ SEQ#: <known>)
2017-10-30
Problem: Stuck in unlocked Bootloader
Hi all,
i am stuck on bootloader and cant get out.
On my PC I have "Minimal ADB and Fastboot"(v. 1.4.2.) installed and after i open a command prompt(admin) and type
- "fastboot devices" my phone is listed as <NR> fastboot
so that works as the only positive thing i can say
- "adb reboot", *daemon not running. starting it now on port 5037*
*daemon started successfully*
error: no devices/ emulators found
- "adb reconnect", error: no devices/ emulators found
i am not into the adb commands at all, i am a dummy and i would be so glad if someone could lead me out of my problem.
Maybe a word how i got into there:
1) i installed the minimal adb and fastboot(v1.4.2.)
2) i unlocked the bootloader by doing that over the Motorola UNLOCK Bootloader site
3) then i rooted & Flash Twrp Recovery (twrp-3.1.1-0-cedric)
with "fastboot flash recovery twrp-3.1.1-0-cedric.img"
4) first time entered into twrp recovery and i did the following:
A) a factory wipe-> reboot back to recovery mode->
B) install no-verity-opt-encrypt-5.1-> reboot and let system start before i turn off phone and enter bootloader(vol down+start) again
C) after entering recovery mode again, i install Magisk-v11.6 -> reboot->
D) now everything seemed to work, the system started properly rooted.
E) but then i decided to flash once again the Magisk-v11.6 followed by wipe data/ factory reset cause i wanted to completly do the flashing all over.
(dont ask me why i did it.. i could explain and tell you my intention but well it happened anyway and brought me to where i am stuck now)
but that was on this move not all yet: i also wipe dalvik cache
so after wipedalvik/ cache , since that moment i couldnt access to my SD Card anymore as it simply didnt show up anymore.
after a restart i was my first time in an endless bootloop of that Screen with "Erasing"(, the letters sourrounded by a spectral colored circle)
i had to disconnect the phone from power . also i tried to remove the battery for a day. but it would only get me back into that bootloop and only get me out by removing the battery...
i dont know anymore what happened then when the phone now got stuck in the bootloader instead of the bootloop. But yea, now i am stuck here, appreciating any help :highfive:
more infromation from my bootloader screen:
AP Fastboot Flash Mode(secure)
BLB8.12 (<known>, 2017-04-19 11:00:47)
Baseband <known>
Product/ Variant: cedric XT1676 16GB P5
Serial Number: <known>
CPU: MSM8937
eMMC: <known>
DRAM: <known>
Console [NULL]: null
Tools Mode Config: DISABLED
Battery OK
flashing_unlocked
Software status: Official
Connect USB Data Cable
- When pressing <Start>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone drops back to Bootloader
when pressing <RESTART BOOTLOADER>
it restarts to BOOTLOADER
- When pressing <Start Recovery>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
after 10 seconds another screen poops up:
"Erasing", the letters sourrounded by a spectral colored circle for 3 seconds,
bevor the Phone just drops back to Bootloader
(talking about Erasing ..)
- When pressing <POWER OFF>
Power Off works
- When pressing <FACTORY RESET>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <BARCODES>
Barcodes are shown
- When pressing <BP TOOLS>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <QCOM>
Your device has been unlocked and can't be trusted.
to learn more, visit:
motorola,com/ unlockbootloader
ID: bad key
Your device will boot in 5 seconds.
->
bevor the Phone just drops back to Bootloader
- When pressing <BOOTLOADER LOGS>
Display shows:
AP Fastboot Flash Mode(secure)
Fastboot Reason: UTAG "bootmode" configured as fastboot
When connecting an USC- cable
Transfer Mode: USB Connected
...shows up but i cant get any adb commands to work tho ofc i am a dummy at it...
oh my, i just helped myself by reading my first poste here on the forum from 2016.
i made it now to start twrp by downloading the twrp_cedric_3.1.1-0 once again putting the recovery in my adb folder and type
<fastboot flash recovery twrp.img>
followed by <fastboot reboot-bootloader>
i am curious if i can get going now and if my SD card will be read and if i can get a new flash going...
now back in twrp i go first again to wipe/ factory reset.
now going to reboot, and reboot back into recovery. only gets me back to bootloader from where i can enter twrp manually now(but there is already an indication of the problem i have?)
also before the reboot, it doesnt ask me to install the twrp app anymore where i usually choose "do not install".
now i go to install the <no-verity-opt-encrypt-5.1>, flashing it successfully as it says at the end of the process but there is also some error message in the log before the ...done:
Failed to mount '/data' (invalid argument)
now i thought i should be able to boot the system again but i only get back into the bootloader...
can someone help me how to proceed correctly?
did i miss something to flash?
Techcri said:
now back in twrp i go first again to wipe/ factory reset.
now going to reboot, and reboot back into recovery. only gets me back to bootloader from where i can enter twrp manually now(but there is already an indication of the problem i have?)
also before the reboot, it doesnt ask me to install the twrp app anymore where i usually choose "do not install".
now i go to install the <no-verity-opt-encrypt-5.1>, flashing it successfully as it says at the end of the process but there is also some error message in the log before the ...done:
Failed to mount '/data' (invalid argument)
now i thought i should be able to boot the system again but i only get back into the bootloader...
can someone help me how to proceed correctly?
did i miss something to flash?
Click to expand...
Click to collapse
For failed mount data goto wipe & select format data (option on the right)
Reboot to recovery
For always going into recovery either you don't have a rom installed or read the faq section on my twrp thread as the answer is there
First of all thanks TheFixItMan, that you are behind it and your thread looks really cool and i will immediatly read and try to understand it!
For now i am stuck in the following:
TheFixItMan said:
For failed mount data goto wipe & select format data (option on the right)
Reboot to recoverye
Click to expand...
Click to collapse
i went to "wipe" & "select format data"
the process shows successfully and "...done" but in the log there is a line of red letter:
<Red Letter>"Failed to unmount '/data' ( Device or resource busy)"
<White Letter> You may need to reboot recovery to be able to use / data again.
i went back and to reboot and recovery.
but recovery wouldnt be booted but i get back to the bootloader(maybe that is still an indication of the problem i have here?)
manually entered recovery i did the select format data again but <red letter> line remains.
TheFixItMan said:
For always going into recovery either you don't have a rom installed or read the faq section on my twrp thread as the answer is there
Click to expand...
Click to collapse
i will parallel read your thread now, thx for being behind it solving the questions! :good:
Techcri said:
First of all thanks TheFixItMan, that you are behind it and your thread looks really cool and i will immediatly read and try to understand it!
For now i am stuck in the following:
i went to "wipe" & "select format data"
the process shows successfully and "...done" but in the log there is a line of red letter:
<Red Letter>"Failed to unmount '/data' ( Device or resource busy)"
<White Letter> You may need to reboot recovery to be able to use / data again.
i went back and to reboot and recovery.
but recovery wouldnt be booted but i get back to the bootloader(maybe that is still an indication of the problem i have here?)
manually entered recovery i did the select format data again but <red letter> line remains.
i will parallel read your thread now, thx for being behind it solving the questions! :good:
Click to expand...
Click to collapse
You have to select recovery from the bootloader menu to enter recovery
You can also type in a terminal window whilst phone connected to pc in fastboot
fastboot erase userdata
This will erase all internal data (the same as format data in twrp)
Important Notes For Stock Rom Users
When you first start TWRP it will ask you to swipe to allow modifications - If you do this your stock rom will no longer boot unless you disable dm-verity.
This can be done either by flashing a disable dm-verity zip or by flashing SuperSu zip which will disable it for you
Click to expand...
Click to collapse
ok, stock rom didnt boot so i flashed the "no-verity-opt-encrypt-5.1" .zip
and voila, i could boot the stock again finally! yipie!
but three things i noticed:
1) the boot progress is suspicous / wrong/ stuck at a moment:
"hello" and "moto" i still see and before the letters of moto start spinning around, the screen freezes for like 2-3 seconds and the next ting i see is the red mouth and cameleon and so on
2) i tried to test camera real quick and it says camera is busy
camera unable to start. if this repeats please power off your phone and restart.
(i did already 5 restarts now and still same problem)
anyway, i wanted to install a ROM now, something like Cyanogenmod.
in this context i wonder what the Magisk-v11.6 does? Does it just give superuser permission and is it always required?
3) system only gives me option to Power Off System(no reboot possible)
and that power off and turn on always gets me first into bootloader tho i dont press vol down+start
Edit:
ok, i have here 3 issues still but it goes offtopic already. i throw a thanks first of all at TheFixItMan and then i think thread cna be closed.
I will soon try to install a ROM, like LineageOS 15.1 , and hope that my previous 3 issues will be solved in the process. . .
Techcri said:
ok, stock rom didnt boot so i flashed the "no-verity-opt-encrypt-5.1" .zip
and voila, i could boot the stock again finally! yipie!
anyway, i wanted to install a ROM now, something like Cyanogenmod.
in this context i wonder what the Magisk-v11.6 does? Does it just give superuser permission and is it always required?
Click to expand...
Click to collapse
Cyanogenmod is now lineageos
Use the latest version of magisk to root (see official magisk thread on xda)
You can run modules to mod phone without tripping integrity or dm-verity which if false will stop apps that check if you are rooted from working
Magisk hide can hide apps from detecting you are rooted on a per app selected basis
3) system only gives me option to Power Off System(no reboot possible)
and that power off and turn on always gets me first into bootloader tho i dont press vol down+start
Click to expand...
Click to collapse
Phone should power off normally
If it can't be started normally without going in bootloader and selecting normal startup see my faqs in twrp thread & follow guide to wiping the misc partition
Note if flashing lineageos 15.1 you will require the 64bit version of TWRP available on the lineageos thread - I did not compile this & don't support it
It also doesn't support encryption as far as I know so if you are encrypted you will need to format data & remove it else the rom will get stuck at the decryption screen
TheFixItMan said:
Phone should power off normally
Click to expand...
Click to collapse
it can be powered off normally as long as its not connected per usb (power or pc)
If it can't be started normally without going in bootloader and selecting normal startup see my faqs in twrp thread & follow guide to wiping the misc partition
Click to expand...
Click to collapse
that was not exactly the problem. my problem is that either i press restart system from system or from recovery, i first get a stop at the bootloader. from there i can just toggle to START and confirm. then my system boots. its just that i first need to confirm in bootloader the Start, always!
at this point i tried now anyways from your Official TWRP For Moto G5 Cedric- Thread |||||| your solution from your faq. But yea, it obviously doesnt fit my problem cause putting the lines in cmd prompt gave me that result and boot still does a stop at bootloader.. before i can start system or recovery..
So yea, after the first codeline didnt trigger for an unknown reason for me...
i hadnt the courage to even try the second more relevant codeline!
Note if flashing lineageos 15.1 you will require the 64bit version of TWRP available on the lineageos thread - I did not compile this & don't support it
It also doesn't support encryption as far as I know so if you are encrypted you will need to format data & remove it else the rom will get stuck at the decryption screen
Click to expand...
Click to collapse
btw, Thx a lot for the information, i appreciate it! i choose LineageOs 15.1 and it runs now. atm i am reading myself into magisk. Also big thanks for your tipp looking up the official thread.
Techcri said:
it can be powered off normally as long as its not connected per usb (power or pc)
that was not exactly the problem. my problem is that either i press restart system from system or from recovery, i first get a stop at the bootloader. from there i can just toggle to START and confirm. then my system boots. its just that i first need to confirm in bootloader the Start, always!
at this point i tried now anyways from your Official TWRP For Moto G5 Cedric- Thread |||||| your solution from your faq. But yea, it obviously doesnt fit my problem cause putting the lines in cmd prompt gave me that result and boot still does a stop at bootloader.. before i can start system or recovery..
So yea, after the first codeline didnt trigger for an unknown reason for me...
i hadnt the courage to even try the second more relevant codeline!
btw, Thx a lot for the information, i appreciate it! i choose LineageOs 15.1 and it runs now. atm i am reading myself into magisk. Also big thanks for your tipp looking up the official thread.
Click to expand...
Click to collapse
That error means your phone is not connected to your pc
Make sure you have enabled adb debugging in phones dev settings before booting into recovery
If you type
adb devices
It will list all devices attached
Once your device is listed the commands will work
TheFixItMan said:
That error means your phone is not connected to your pc
Make sure you have enabled adb debugging in phones dev settings before booting into recovery
If you type
adb devices
It will list all devices attached
Once your device is listed the commands will work
Click to expand...
Click to collapse
and you think that your commands fromyour solution here helps me with my issue that i can start straight to everywhere i want? Cause atm I just always have to go over the bootloader -"stop". From there i have then to manually "START" in order to start system (now: LineageOS 15.1:victory or where i have to manually toggle down to "RECOVERY MODE" and start TWRP.
Well, i would give it a try, but yea dunno what i am doing wrong here atm. i just realized that the command "adb devices" never worked for me yet, cause i got in conflict with the command fastboot adb devices which effectivly works for me. Cause before i installed lineageOS 15.1 i had to flash the twrp cedric 3.2.1-0 x64. i did that over the adb command prompt:
Code:
fastboot flash recovery twrp.img
and in that process i even let my phone restart to bootloader with
Code:
fastboot reboot bootloader
.
now i went to tab build nummer 7 times-> dev options "on" -> android debugging enabled.
when i go to bootloader now or to recovery, and connect my device, for a strange reason in command prompt "adb devices" shows that:
... i dont know why the cmd "adb devices" doesnt show my device. maybe there is a twrp setting i need to change?
Techcri said:
and you think that your commands fromyour solution here helps me with my issue that i can start straight to everywhere i want? Cause atm I just always have to go over the bootloader -"stop". From there i have then to manually "START" in order to start system (now: LineageOS 15.1:victory or where i have to manually toggle down to "RECOVERY MODE" and start TWRP.
Well, i would give it a try, but yea dunno what i am doing wrong here atm. i just realized that the command "adb devices" never worked for me yet, cause i got in conflict with the command fastboot adb devices which effectivly works for me. Cause before i installed lineageOS 15.1 i had to flash the twrp cedric 3.2.1-0 x64. i did that over the adb command prompt:
Code:
fastboot flash recovery twrp.img
and in that process i even let my phone restart to bootloader with
Code:
fastboot reboot bootloader
.
now i went to tab build nummer 7 times-> dev options "on" -> android debugging enabled.
when i go to bootloader now or to recovery, and connect my device, for a strange reason in command prompt "adb devices" shows that:
... i dont know why the cmd "adb devices" doesnt show my device. maybe there is a twrp setting i need to change?
Click to expand...
Click to collapse
Does it display a device when the phone is fully booted
If yes than the recovery you are using doesn't support adb (my official recovery does)
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)
Hello, thx for your support.
I linked the wrong picture. This Screeny shows the related cmd (when dev enabled, booted to recovery, connected via usb to pc and typed adb devices).
Does it display a device when the phone is fully booted. If yes than the recovery you are using doesn't support adb (my official recovery does)
Click to expand...
Click to collapse
it shows the same like linked above and when in recovery mode
so no , the 64bit version of twrp cedric 3.2.1-0 prolly isnt the problem.
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)
Click to expand...
Click to collapse
ok i will try that. and the command prompt i have to open from the directoryy<platform tools folder> then right?
would you deinstall minimal ADB and fastboot before installing full android sdk?
TheFixItMan said:
If no I recommend downloading the full android sdk and using the adb that comes with that (you will find it in the platform tools folder where you installed it)
Click to expand...
Click to collapse
still my phone isnt found
- sdk tools installed
- dev enabled
- adb debugging enabled
- command prompt opened at "...\android-sdk\platform-tools"
either in recovery nor in booted system nor in bootloader "adb devices" finds my phone
so the problem with the "bootstop" (have always to manually press "START" at bootloader) persists..
oh wait... i am not connected as admin! is it possible to open an admin command promp:silly:t?
so i am am reading here atm how to open command prompt in specific folder(platform-tools)
but wife is waiting for dinner so i better do that first..
Techcri said:
still my phone isnt found
- sdk tools installed
- dev enabled
- adb debugging enabled
- command prompt opened at "...\android-sdk\platform-tools"
either in recovery nor in booted system nor in bootloader "adb devices" finds my phone
so the problem with the "bootstop" (have always to manually press "START" at bootloader) persists..
oh wait... i am not connected as admin! is it possible to open an admin command promp:silly:t?
so i am am reading here atm how to open command prompt in specific folder(platform-tools)
but wife is waiting for dinner so i better do that first..
Click to expand...
Click to collapse
On windows 7 - hold shift then right click a white empty space of the window where adb is & select open command prompt here
Windows 7 or 10 - search for cmd then right click on cmd and select run as administrator then navigate using cd commands to adb location or copy & paste location (if any spaces in path then put the entire path in quotation marks)
On windows 7 - hold shift then right click a white empty space of the window where adb is & select open command prompt here
Click to expand...
Click to collapse
yes i did that before as non admin
Windows 7 or 10 - search for cmd then right click on cmd and select run as administrator then navigate using cd commands to adb location or copy & paste location (if any spaces in path then put the entire path in quotation marks)
Click to expand...
Click to collapse
i use win7 and cd'ing to the path was almost getting annoying
as screenshot shows, it still doesnt work
in my desperation i deinstalled now all adb drivers(minimal+ sdk)
ran a ccleaner and cleaned registry and reinstalled minimal adb again (btw, there was a new version by now out, 1.4.3)
so the episodes still goes on and i could figure out some new details
because i bought the same phone again for a relative who needed a phone..
in the process of setting it up correctly( thankfully xda is around ) i enabled dev options and the adb debugging
here is the result for the new phone
that shows now that executing as admin or standard user wasnt the problem. i just did it as standard user..
then i thought "hey cool, wait, i connect now my own G5 and see if i can get the phones' Nr displayed there and make sure my phone can communicate with my pc over adb( dunno if the sentence just made sense- greetz from a dummy)"
what happened is shown in this screenshot .. same picture as before! :crying:
(dont get irritated by the screeny because i used the same command prompt for
first, the new phone and
second, my "old" phone which doesnt boot properly, if you look at the command and the result
i am lost!
is it possible to reinstall a bootloader? or how come my phone doesnt communicate with the pc anymore?
and how come that effects the booting process so that i always get this "stop" at the bootloader although i pressed for a restart?
can i do any more tests that indicates what problem i have here?

Fastboot mode Not taking any commands

Hi everyone, I am in a real pickle. I can boot into fastboot mode but when I do so I am not able to flash any recovery img or infact any operations on it only " fastboot devices " gives a positive response, else everything just stucks in command line. So my next step was to use the realme Flash tool. in that too when I click on available devices it shows my phone but after that it just quits the fastboot mode and the phone asks me to press any key to reboot.
Guys please help me if there is any way around it as i have tried everything. Can we reset the bootloader itself using some tool if yes then please let me know
Thanks in advance
katti205 said:
Hi everyone, I am in a real pickle. I can boot into fastboot mode but when I do so I am not able to flash any recovery img or infact any operations on it only " fastboot devices " gives a positive response, else everything just stucks in command line. So my next step was to use the realme Flash tool. in that too when I click on available devices it shows my phone but after that it just quits the fastboot mode and the phone asks me to press any key to reboot.
Guys please help me if there is any way around it as i have tried everything. Can we reset the bootloader itself using some tool if yes then please let me know
Thanks in advance
Click to expand...
Click to collapse
This happened twice with me.
Once, my device driver wasn't properly installed.
Second time I didn't gave cmd permission to access my phone.
Was there a pop up on your phone where it asks you something like "do you want this pc to control your phone"?
use diffrent port

Categories

Resources