Hi everybody,
I own a N7 2013 LTE (deb) with Android 5.1.1 installed (build: LMY48P). This morning I've tried to turn on my device and it remains stuck on Google logo.
The device correctly goes into Fastboot mode but from here I cant do anything:
Start: see the Google logo and stuck
Restart bootloader: correctly reopen the bootloader
Recovery mode: see the Google logo and stuck
Power off: correctly power off
These are the informations showed in the Fastboot screen:
FASTBOOT MODE
Product Name: deb
Variant: deb 32G
HW version: rev_e
BOOTLOADER VERSION: FLO-004.05
BASEBAND VERSION: DEB-Z00_2.44.0_0213
CARRIER INFO: None
SIGNING: yes
SECURE BOOT: enabled
LOCK STATE: locked
I've downloaded Nexus Root Toolkit v2.05 by WugFresh and the device is correctly seen from my windows pc and from NRT (I've succesfully installed USB drivers).
From NRT I've tried to "Flash Stock + Unroot" but I cant flash because the bootloader is locked; so I've tried to unlock the bootloader from NRT, the N7 correctly show the "Unlock bootloader?" screen, I move to "YES" with the volume keys but when I push the power button to confirm, nothing happens and the tablet continues to show that screen (I've waited about 30mins and nothing happens).
I dont care about user data and my photos and videos; I'd like to have my tablet working.
Some questions:
1) is there a way to launch a stock recovery or a TWRP recovery from NRT so I can wipe all data and have my tablet back working?
2) is there a way to see from NRT le log? I'd like to see some more specific error details when I try to unlock bootloader and it fails.
3) do you have some advices? thanks in advance
Thanks guys
Related
Guys hello,
yesterday i tried to unlock bootloader & gain root access for the first time. But i had some problems after unlocked bootloader. until that point everything was great. but when i was trying to build a "custom recovery" via HTC One X all in One Kit V2.5, maybe i did something wrong. at the moment, my phone can not complete a factory reset. stays HTC logo on a white screen until the charge is off. when i reboot my device, my device is in "airplane mode" and i can not close it. i can not use Wifi, or telephone signal. and i do not know what the problem is...
when i enter fastboot screen, i get a message:
"failed to open USB master mode
loading PJ46IMG.zip image
failed to open USB master mode
please plug off USB"
and then i see the menu items (FASTBOOT, RECOVERY...)
when i try to fastboot "clockworkmod.img (i downloaded it in the forum)", on the cmd screen, i get "error: can not load Recoveries/CWM.img". maybe the problem is here. i deleted something. and i do not know what that is...
on my fastboot screen, i see this:
"*** UNLOCKED ***
ENDEAVORU PVT SHIP S-ON RL
HBOOT-1.72.0000
CPLD-None
MICROP-None
RADIO-5.1204.163V2.31
eMMC-bootmode: disabled
CPU-bootmode: disabled
HW Secure Boot: enabled
MODEM PATH: OFF
Jun 21 2013, 18:24:41 "
and my CID No is : TMOB101.
and one more thing...
when i select RECOVERY via power button, i do not get a menu! i see a telephone icon and over that there is a red triangle and a ! sign inside that triangle. if i do not do anything, telephone reboots after a while. but on that screen if i press, "power + vol up (not vol down)", i get a small menu:
"Android system recovery <3e>
Reboot system now
Apply update from external storage
wipe data/factory reset
wipe cache partition
apply update from cache
Apply update from internal storage"
i do not see other menu items that other people see...
and while this menu is active, i get a message as :
"starting cw install
Enable host mode
Disable host mode"
when i press, pow + vol up button again, host mode becomes again enable... and after that telephone reboots...
but everything is again the same... no signal, no wifi, can not turn off Airplane mode... Please help me...
i am very very new on this rom/root thing. so can you please tell me in details? will i be able to use this phone again?
memoally said:
Guys hello,
yesterday i tried to unlock bootloader & gain root access for the first time. But i had some problems after unlocked bootloader. until that point everything was great. but when i was trying to build a "custom recovery" via HTC One X all in One Kit V2.5, maybe i did something wrong. at the moment, my phone can not complete a factory reset. stays HTC logo on a white screen until the charge is off. when i reboot my device, my device is in "airplane mode" and i can not close it. i can not use Wifi, or telephone signal. and i do not know what the problem is...
when i enter fastboot screen, i get a message:
"failed to open USB master mode
loading PJ46IMG.zip image
failed to open USB master mode
please plug off USB"
and then i see the menu items (FASTBOOT, RECOVERY...)
when i try to fastboot "clockworkmod.img (i downloaded it in the forum)", on the cmd screen, i get "error: can not load Recoveries/CWM.img". maybe the problem is here. i deleted something. and i do not know what that is...
when i press, pow + vol up button again, host mode becomes again enable... and after that telephone reboots...
but everything is again the same... no signal, no wifi, can not turn off Airplane mode... Please help me...
i am very very new on this rom/root thing. so can you please tell me in details? will i be able to use this phone again?
Click to expand...
Click to collapse
first go in bootloader and then connect to a computer you will not see this massage and you will be able to flash recovery and then rom and flash boot.img
Thant said:
first go in bootloader and then connect to a computer you will not see this massage and you will be able to flash recovery and then rom and flash boot.img
Click to expand...
Click to collapse
thank you very much. now, i did it. and i installed Android revolution HD 33.1. and all is okay.
hi guys,
tragedy started like that: today i decided to give miui another shot. downloaded latest miui developer rom to sd card of my galaxy nexus, rebooted into recovery and flashed miui zip and tiny kernel afterwards. stupid me i forgot to wipe cache before installing the new rom. hit reboot in cwm, which kindly told me that the new rom could make recovery unusable. here i accidentally selected the obvious wrong choice, which said "dont fix problem" or sth like that. dont know if recovery is gone now... after reboot miui was trying to boot without success (mi logo shown until you turn the phone off). so i went to fastboot by pressing volume down (my volume up is broken!). fastboot acts pretty dead: cant scroll through options by pressing volume down, cant do "normal" start by pressing power, absolute no reaction of the phone. also the phone is not recognized when connecting to pc via usb (tried the samsung original driver). phone is recognized when miui is trying to boot, but i cant send any commands via fastboot.
im thankful for any advice that lets me install a new recovery/boot into recovery/make it boot again!
fastboot mode details:
product name - tuna
variant - maguro 16gb
bootloader version - primemd04
baseband version - i9250xxlj1
carrier info - none
serial number - irrelevant
signing - production
lock state - unlocked
anyone?
Hello and thanks for reading!
I just got my hands on this Nexus 7, and it was working correctly for two days, but three days ago, i didn't use it that day and i think it discharged. Well, after that, it won't go pass the Google logo and it was restarting over and over...bootlooping. I tried going to the bootloader and then to the recovery to perform a factory reset, but when i selected the recovery, it went back to bootlooping.
Since i CAN access the bootloader and can get the fastboot device recognized on my computer (Windows) using the command "fastboot devices", i thought i was saved and tried flashing the stock 6.0.1 image via fastboot. That didn't work well. Everything flashed well except the System. When it tried to flash the system, i got the following error: "FAILED (remote: Unknown chunk type)". There is little information on the internet about that error. On one site, someone said that he was getting that error and sent the tablet to Asus for repair and when he got it back, they had flashed 4.4.1 on it, so i tried flashing 4.4.1 and to my surprise, when i flashed System, it said "Okey" instead of FAILED, again, i thought i was saved, but when i tried to boot the table, there is no bootloop but it just stays on the Google logo and won't go pass it. No bootloop, just stays there showing the Google logo. I let it sit there for about 20 mins, but nothing happened.
Here is the info it displays on the Bootloader:
PRODUCT NAME - flo
VARIANT - flo_16g
HW_VERSION - rev_e
BOOTLOADER VERSION - FLO-04.02
CARRIER INFO - None
SERIAL NUMBER - 08feeecf
SIGNING - yes
SECURE BOOT - enabled
LOCK STATE - unlocked
Is there something im missing? Any suggestions? I would like to fix this tablet.
Bump.
Hi Folks
I just got the Media Pad M2 8.0 and I want to check if the bootloader is locked or not
because there is no dialer installed I can't use the code I found in other forums
is there another way to find out?
hingerl said:
Hi Folks
I just got the Media Pad M2 8.0 and I want to check if the bootloader is locked or not
because there is no dialer installed I can't use the code I found in other forums
is there another way to find out?
Click to expand...
Click to collapse
Yes, there should be. You need to enter fastboot mode on the phone - i.e you need to get into the bootloader screen. The bootloader screen (usually called fastboot mode) will tell you if the bootloader and FRP are locked or unlocked - If it is locked, you should see "PHONE Locked" and "FRP Lock" in green, otherwise it should say "PHONE Unlocked" and "FRP Unlock" in red if the phone has been properly unlocked.
You can enter fastboot mode by either using ADB ("adb reboot bootloader", first make sure to enable developer options first as detailed in the Rooting guide, and then enabled USB debugging), or by first shutting down the phone and then powering it up while holding down the VOLDN (Volume Down) key. Of the two methods, I'd recommend the ADB method because the hardware keys method is usually hit-or-miss for me - sometimes it takes me to the bootloader, sometimes it boots normally into the ROM.
If you're on Windows and need the ADB and fastboot binaries, you can install the "15-second ADB installer" found in this thread.
Thanks, that worked, took me a while to figure everything out...
and it appears that my device is unlocked...
Hey there
As soon as my realme x gets into fastboot mode it jumps out again
Things I tried jet:
- Power + Volume Up (Down is recovery) -> Did not even enter
- adb reboot bootloader -> Enter Fastboot, jumps out suddently (win10 & ubuntu18.04) same, same with phone {after command} attached or not, simultan fastboot <waiting for device> dont works neither
- deep test app -> Message. :"not supported"
Developer Option is on, OEM on, Debugin on, adb works
My Phone:
Realme RMX1901
ColorOS 6.0
Android 9
Version: RMX1909_11_A.17_53f4cfd4
Baseband: Q_V1_P14,Q_V1_P14
Kerne: 4.9.112
Android Security Patch: August 5, 2019
Tried
if anyone has any hint or solution would be great.
_3raymon said:
Hey there
As soon as my realme x gets into fastboot mode it jumps out again
Things I tried jet:
- Power + Volume Up (Down is recovery) -> Did not even enter
- adb reboot bootloader -> Enter Fastboot, jumps out suddently (win10 & ubuntu18.04) same, same with phone {after command} attached or not, simultan fastboot <waiting for device> dont works neither
- deep test app -> Message. :"not supported"
Developer Option is on, OEM on, Debugin on, adb works
My Phone:
Realme RMX1901
ColorOS 6.0
Android 9
Version: RMX1909_11_A.17_53f4cfd4
Baseband: Q_V1_P14,Q_V1_P14
Kerne: 4.9.112
Android Security Patch: August 5, 2019
Tried
if anyone has any hint or solution would be great.
Click to expand...
Click to collapse
Use this app and this tutorial
_3raymon said:
Hey there
As soon as my realme x gets into fastboot mode it jumps out again
Things I tried jet:
- Power + Volume Up (Down is recovery) -> Did not even enter
- adb reboot bootloader -> Enter Fastboot, jumps out suddently (win10 & ubuntu18.04) same, same with phone {after command} attached or not, simultan fastboot <waiting for device> dont works neither
- deep test app -> Message. :"not supported"
Developer Option is on, OEM on, Debugin on, adb works
My Phone:
Realme RMX1901
ColorOS 6.0
Android 9
Version: RMX1909_11_A.17_53f4cfd4
Baseband: Q_V1_P14,Q_V1_P14
Kerne: 4.9.112
Android Security Patch: August 5, 2019
Tried
if anyone has any hint or solution would be great.
Click to expand...
Click to collapse
Do you get any solution for this? I'm also getting this problem.
vjykumar449 said:
Do you get any solution for this? I'm also getting this problem.[/QUOTE
unfortunately not jet. I kinda give up on this one. Can't do nothing without fastboot..
Click to expand...
Click to collapse
_3raymon said:
vjykumar449 said:
Do you get any solution for this? I'm also getting this problem.[/QUOTE
unfortunately not jet. I kinda give up on this one. Can't do nothing without fastboot..
Click to expand...
Click to collapse
May be some problem from Realme's end. I searched this on google, got some videos for sony mobiles, sony provides some 15digit code to unlock bootloader, without this code, same failed error occurs. In case of Realme, they provide the application. I tried with exit the depth test, then re-applied but no luck. Still got the same error.
I also tried with other windows PCs.
Click to expand...
Click to collapse
Bootloader Unlocked
I have successfully unlocked my Realme X's bootloader. The problem is with the PC or cable. I changed both.
Try on another PC with new or other cables.
Maybe:
Tried on Intel i5 PC -->> Not worked. (mine and friend's PC)
Tried on Intel i3 -->> Worked (got other friend's PC)
May this will help you too.
if anyone has any hint or solution?
mandar91 said:
if anyone has any hint or solution?
Click to expand...
Click to collapse
Try USB 2.0 and make sure to use orginal cable (or try another cable)
it''s not booting in fastboot mode i mean it boots but immediately boots into system it won't stay there
vjykumar449 said:
I have successfully unlocked my Realme X's bootloader. The problem is with the PC or cable. I changed both.
Try on another PC with new or other cables.
Maybe:
Tried on Intel i5 PC -->> Not worked. (mine and friend's PC)
Tried on Intel i3 -->> Worked (got other friend's PC)
May this will help you too.
Click to expand...
Click to collapse
you using depth test apk or via adb to enter fastboot?
i got this problem. not enter fastboot, just reboot normally after showing chinese words (via apk)
Help
when flashing an updated rom I forgot to flash vbmeta and magisk-fix.
And now I can't go into fastboot mode, can someone help me ...?
Thanks!
in the new update both fastboot and recovery an on the same scree power+volume down so once on the selection screen connect the device and check if the android driver is installed if not use a driver updater tool like driver booster to install the drive and check again