Related
some guy successfully bricked his N1 as soon as he received it about 2 months ago. When this expensive brick reached my hand, he didn't even remember what he had done... and this brick had been through many many ppl for repair, so there is no way for me to know what exactly happened during the last 2 months...
Anyway, now it:
1. light doesn't turn on when charging(not sure yet whether it is actually charing)
2. trackball + power could gets it to fastboot screen, but none of the key is working then.
3. after single press of power button when powered off, red/green/blue/white color bar and 3 droids on the screen
so , now I cannot put it in fastboot nor recovery mode, stuck.
could there be anything I can do to rescue it?
ndep said:
2. trackball + power could gets it to fastboot screen, but none of the key is working then.
Click to expand...
Click to collapse
Verify this. Enter fastboot mode (connected to usb) and then try "fastboot devices" in a command prompt. It it reports a connected device then its definitely recoverable.
The only way that a N1 get bricked (software wise) is by upgrading a wrong radio, and unfortunetly the only way to recover it (now) is by sending it to Google/HTC
more explanation
thanks i did try that...fastboot devices could not detect anything,coz it just freezes at that screen and could not enter any mode using power and voldown button.
what puzzlrs me most is that screens with multicolor bars, how on earth does that happen?
britoso said:
Verify this. Enter fastboot mode (connected to usb) and then try "fastboot devices" in a command prompt. It it reports a connected device then its definitely recoverable.
Click to expand...
Click to collapse
update: the light turns orange now and then when charging, and it is actually charging no matter the light is on or not. ( using my own nexus to verify that )
Did you plugged it to your PC?
I knew a guy who bought a ''flashing device'' capable of formating any chipset over USB, so he could do a clean install of the Firmware again. Perhaps you could find one of these devices over ebay
britoso said:
Verify this. Enter fastboot mode (connected to usb) and then try "fastboot devices" in a command prompt. It it reports a connected device then its definitely recoverable.
Click to expand...
Click to collapse
That's assuming he has the android sdk installed with the correct drivers. We don't know if the op has.
@vegetaleb: the device you mentioned is somewhat mysterious... a search on ebay with "flash device" does not give me anything related, do you have a specific name?
@C.Slater: I do have them, coz I myself own a nexus too..
should be deleted, sorry
@vegetaleb: the device you mentioned is somewhat mysterious... a search on ebay with "flash device" does not give me anything related, do you have a specific name?
@C.Slater: I do have them, coz I myself own a nexus too..
edit: isn't there an option to delete this reply? I clicked the submit button twice,sorry.
does typing fastboot devices in the cmd prompt work for your non bricked nexus?
Sent from my Nexus One using the XDA mobile application powered by Tapatalk
Does holding power+trackball bring you to fastboot?
Yes=It's not bricked
No=Kiss it goodbye, it's bricked
Simple as that
TFJ4 said:
Does holding power+trackball bring you to fastboot?
Yes=It's not bricked
No=Kiss it goodbye, it's bricked
Simple as that
Click to expand...
Click to collapse
power+trackball will bring it to fastboot screen, note just the fastboot screen, it just freezes there. All the buttons does not work, and connecting to PC using a USB cable does not show "FASTBOOT USB".
However, it could enter HBOOT with power+voldown, I noticed it searches for passdiag.zip , passdiag.nbh, etc. Could I use this builtin function to flash it? which file in this post should I use?
http://android.modaco.com/content/g...-online-kitchen-optional-root-insecure-himem/
I tried to use the first one ( http://www.romraid.com/paul/nexusone/EPE76-update-nexusone-stock-images.zip ), rename to PASSDIAG.zip , but HBOOT is still complaining about "No Image"
Perhaps it's physically damaged!
It remembers me of my boss iphone that looked perfectly normal but couldn't get a FW installed because the power part has been damaged by water(power button couldn't work at all)
Try renaming it to passimg.zip and use hboot again.
speedyls91 said:
Try renaming it to passimg.zip and use hboot again.
Click to expand...
Click to collapse
tried PASSIMG.zip , still "No Image"...
You can send it to htc for repair but the downside would be that you would never know how to deal with this kind of problem yourself...
Continue the research and keep us posted ...
i maybe wrong but i think is it case-sensitive.....meaning PASSIMG.zip would fail but passimg.zip wouldn't.....Correct me if i'm wrong please....
Case sensitive
I'm pretty sure it is case sensitive. Used to be that way with other android and HTC devices. Can't imagine it's changed.
linux is case sensitive, for sure.
i say approach from the adb/fastboot route, using usb. first, ensure that you have all the correct drivers etc for adb use (the sdk, the usb drivers, and the device specific drivers).
try ur 'adb devices' command
if adb sees it, in normal mode, you should be okay. make sure the phone has 'usb debugging' turned on in settings
I flash a wrong kernel (A Nexus 7 kernel), and my nexus4 become brick. No matter what I did, it still no response. I can't boot to fastboot, even i can't turn it on. Please help....
connect to PC, only show a QHSUSB_DLOAD in Device Manager. But still can't turn it on. Please help, anything i can do to fix it??
Read through the ENTIRE other thread you posted in, all the info is there.
No idea how you accidently flash wrong a kernel for the wrong device.
Get into bootloader mode. (can you? Google on how to do it manually)
Or
Plug the phone in via usb if you had adb used on it and type adb reboot bootloader (hence if use toolkit you won't have this set up.)
Sent from my Nexus 4 using xda premium
These guys are way to eager to flash any and everything on there devices
yyz71 said:
These guys are way to eager to flash any and everything on there devices
Click to expand...
Click to collapse
It just seems impossible on finding kernel for other phones on a nexus 4 forum.
Oh what's this? A link to a flash able zip? Let's flash it without thinking.
Think before you flash op.... And dont use toolkits.
Sent from my Nexus 4 using xda premium
zephiK said:
It just seems impossible on finding kernel for other phones on a nexus 4 forum.
Oh what's this? A link to a flash able zip? Let's flash it without thinking.
Think before you flash op.... And dont use toolkits.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
So true:good:
I can't connect PC with adb. I connect PC can't show the charge icon in my phone. And PC can only identify the device as QHSUSB_DLOAD.
So, what can i do..?
yatyuk said:
I can't connect PC with adb. I connect PC can't show the charge icon in my phone. And PC can only identify the device as QHSUSB_DLOAD.
So, what can i do..?
Click to expand...
Click to collapse
Send that puppy back, & get a new one...
Sent from my HTC One X using xda premium
rayford85 said:
Send that puppy back, & get a new one...
Sent from my HTC One X using xda premium
Click to expand...
Click to collapse
I really dislike people recommending to send the phone back (RMA) to Google for a user's own (I'll be polite here) lack of awareness and understanding of what they are doing. This person should continue to look for solutions to get it working and if not.. well, to bad. Lesson learnt. Buy another Nexus 4.
Besides that fastboot should still be accessible. If OP can eventually get into fastboot then all will be well.
Go read read FAQ thread,will show yo proper way to get back to bootloader mood don't be lazy that won't help,agree getting to bootloader mode then fastboot proper n4 kernel.try it on other pc I'd you cannot in this pc,make sure you install the driver.
Read before you ask
Sent from my HTC One X using xda app-developers app
Zackconsole said:
Go read read FAQ thread,will show yo proper way to get back to bootloader mood don't be lazy that won't help,agree getting to bootloader mode then fastboot proper n4 kernel.try it on other pc I'd you cannot in this pc,make sure you install the driver.
Read before you ask
Sent from my HTC One X using xda app-developers app
Click to expand...
Click to collapse
Bro, i already read some thread... but still not work...i try any combine key with connection to PC, and only red LED appeared few sec and then off again. I think i had driver, because i can use toolkit, unlock and root via adb before. Or can u please give me the link which i need to read? I search about the "qhsusb_dload" problem. Some tell me can easy to fix it by using power+ Vol+/- with connection to PC. But i try many times, still not work... I know i can fix it, if i can enter bootloader. But now i can't turn my phone on.... any suggestion? Thank you.
yatyuk said:
Bro, i already read some thread... but still not work...i try any combine key with connection to PC, and only red LED appeared few sec and then off again. I think i had driver, because i can use toolkit, unlock and root via adb before. Or can u please give me the link which i need to read? I search about the "qhsusb_dload" problem. Some tell me can easy to fix it by using power+ Vol+/- with connection to PC. But i try many times, still not work... I know i can fix it, if i can enter bootloader. But now i can't turn my phone on.... any suggestion? Thank you.
Click to expand...
Click to collapse
Its actually appalling the lack of support users get on here, instead being on point and helping the man out all they get is criticized.
Anyways Back to topic: yatyuk your device isn't bricked it still has life. I had the exact same issue before when connecting to the PC I was also getting the "qhsusb_dload" driver alert.
Click on the Link and Follow the steps if you can get into Fastboot Mode. Check the Post #241 of mine.
LINK
Happy Recovery!
risktaker84 said:
Its actually appalling the lack of support users get on here, instead being on point and helping the man out all they get is criticized.
Anyways Back to topic: yatyuk your device isn't bricked it still has life. I had the exact same issue before when connecting to the PC I was also getting the "qhsusb_dload" driver alert.
Click on the Link and Follow the steps if you can get into Fastboot Mode. Check the Post #241 of mine.
LINK
Happy Recovery!
Click to expand...
Click to collapse
I read your post already bro!! Thanks for your help. But, i don't understand #241. How can I get into fastboot mode?
Is the first step "1) Once in Fastboot mode, through Nexus 4 Toolkit I flashed the Clock Work Recovery. " ?
Now I connect my phone to PC, then Power + Vol- for ~10sec, my phone will had red led for few second and then off again.
risktaker84 said:
Its actually appalling the lack of support users get on here, instead being on point and helping the man out all they get is criticized.
Anyways Back to topic: yatyuk your device isn't bricked it still has life. I had the exact same issue before when connecting to the PC I was also getting the "qhsusb_dload" driver alert.
Click on the Link and Follow the steps if you can get into Fastboot Mode. Check the Post #241 of mine.
LINK
Happy Recovery!
Click to expand...
Click to collapse
Bro, can you please teach me how to enter fastboot mode? I try using all combine key with connection to PC, but only red led appear for few second then off.
I like how all the people who manage to do something so idiotic to these phones band together and stick up for each other. There is no possible way to flash the wrong nexus kernel. any who, the solution has been posted plenty of times. Enter recovery then fast food.
Sent from my Nexus 4 using xda premium
yatyuk said:
Bro, can you please teach me how to enter fastboot mode? I try using all combine key with connection to PC, but only red led appear for few second then off.
Click to expand...
Click to collapse
To get into Fastboot:
-----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
So for all the people with Bricked devices all hope is not lost. Follow this procedure to get into Fastboot.
1) Press the Power button for more then 5 seconds to do a Hard Reset. This is where you screen is completely turned off.
2) Now take your LG manufactured USB connect it to the PC. Do not connect it to the phone just yet.
3) Holding the Vol Down and Power together and NOW connect your other end of the USB connector to the phone and then your phone should give you a slight vibration and you should see the Fastboot screen (Android lying on the back)
NOTE: Make sure as soon as you see then fastboot mode Let go of the Vol and Power Button right away!
------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Click to expand...
Click to collapse
risktaker84 said:
To get into Fastboot:
Click to expand...
Click to collapse
I try many times.....but still can't turn on...
My situation is
1) Press the Power button for more then 5 seconds to do a Hard Reset. This is where you screen is completely turned off.
--->My phone is always turned off, when i disconnect to PC....
2) Now take your LG manufactured USB connect it to the PC. Do not connect it to the phone just yet.
--->This step is ok
3) Holding the Vol Down and Power together and NOW connect your other end of the USB connector to the phone and then your phone should give you a slight vibration and you should see the Fastboot screen (Android lying on the back)
---> when i connect the usb, the phone immediately Red LED on and no vibration. LED on few second, my phone off again and remind no response
Is that mean no hope
yatyuk, use this thread for further inquiry LINK. I don't want to go back and forth in between different threads with the same issues.
Try this,
Did you ever get a Battery sign when you had it connected to the PC or AC for power?
Try this, I don't know if its gonna work or not but plug your phone in the wall receptacle for AC Charge and leave it for a while. On AC, the phone most likely, if completely dead, will stay idle but most likely jump back to Battery sign showing its charging or not.
When that happens, leave like that for a hour or two.
Let me know what happens. Good luck.
Click to expand...
Click to collapse
Thank you for your friendly help
I had read your post already, and i will keep on trying...
Hi,
I finally found the real method to boot our Amazfit watch into fastboot. It is difficult to success at any time, but you should be able to boot fastboot directly after some try.
Here is the procedure : (I've made a video : https://www.youtube.com/watch?v=ZlXoeq30vM0 )
When you try, I advice to put the watch in its charging base, the usb Cable connected to the base, but not on the PC.
Here are the steps to go in fastboot mode :
1) press the power button 2 seconds
2) release the button et repress it again without releasing it
3) when the screen of the watch switch off, plug the usb cable.
4) when the screen turn on, count from 1 to 4. At 4 release the power button. You are now in fastboot.
If it fails, try again. It is a little difficult.
Hope this helps.
kiralex
OMG!
edit:
how the hell do i get those files inside with only wastboot mode ... FFS
2nd edit: @Neuer_User, I have the pulled mmcblk0p7 on the storage, is there any possible way of pushing it back into the system via fastboot?
Guys, that is so great! And @kiralex1995 deserves highest thanks for his finding! We need to get a stickied post for this!!
@1immortal: I'll prepare instructions for you. You will need a modified boot image and then boot this. Then you can flash system from there!
Accidentally opened fastboot with a different method.
My device didn't show up under Windows 7, after I installed adb and fastboot drivers.
So with device connected to usb I typed adb kill-server, then adb start-server and adb wait-for-device then I switched it on and off... tadaa fastboot. See picture with command lines.
MyriaBoa said:
Accidentally opened fastboot with a different method.
My device didn't show up under Windows 7, after I installed adb and fastboot drivers.
So with device connected to usb I typed adb kill-server, then adb start-server and adb wait-for-device then I switched it on and off... tadaa fastboot. See picture with command lines.
Click to expand...
Click to collapse
Interesting. See if you can make it reproducable. That would be great!
---------- Post added at 08:39 PM ---------- Previous post was at 08:37 PM ----------
I wrote some unbricking instructions and a flash script to recover bricked watches with @kiralex1995 method of entering fastboot.
Hope, it helps recover the small number of watches known to be bricked through flashing.
https://forum.xda-developers.com/sm...tches/tutorial-unbrick-huami-amazfit-t3547300
Neuer_User said:
Guys, that is so great! And @kiralex1995 deserves highest thanks for his finding! We need to get a stickied post for this!!
@1immortal: I'll prepare instructions for you. You will need a modified boot image and then boot this. Then you can flash system from there!
Click to expand...
Click to collapse
You're welcome
@kiralex1995 , Thanks a Gazillion !!!
it worked and with @Neuer_User help, the watch came back to life !!!
My fastboot method was reproducable on a different machine on Windows 10 . Needed 2 attempts. Seems a question of timing. Right before it happens, the computer makes the notification sound for 'new usb device detected'.
MyriaBoa said:
My fastboot method was reproducable on a different machine on Windows 10 . Needed 2 attempts. Seems a question of timing. Right before it happens, the computer makes the notification sound for 'new usb device detected'.
Click to expand...
Click to collapse
maybe you need to explain a little bit more detailed? is the watch running and completely booted when you connect to usb and type those adb commands or is it switched off? when you turn it on, how fast do you turn it off? i didn't get it yet. please explain a bit more.
MyriaBoa said:
Accidentally opened fastboot with a different method.
My device didn't show up under Windows 7, after I installed adb and fastboot drivers.
So with device connected to usb I typed adb kill-server, then adb start-server and adb wait-for-device then I switched it on and off... tadaa fastboot. See picture with command lines.
Click to expand...
Click to collapse
It is interesting. Does it work with out th.e adb kill-server and adb start-server commands? I do not see, how they could be involved...
The adb wait-for-server might be the key. So, when the watch is started, there is some USB communication on-going. I'd love to do some testing on that. Will do that for sure, when I get the development watch
I' m not near my computer, so I can't do more tests now.
As I wrote in my first post, it wasn't my intention to open fastboot, when it accindentally happened for the first time.
The kill and start commands were given, because my Windows 7 machine pretended not to see the watch in adb (only as usb), and I thought, maybe it's detected, when I turn it on while adb is waiting for device and the usb notification 'kicks in'.
But nothing happened, so I pushed the button, to turn the watch off again.
To my surprise the result was fastboot.
I repeated the same steps today on my Windows 10 computer that always detects the watch in adb and it opened fastboot again.
Could you specify for which build or version you tried this? I (unfortunately) had the update to 1.3.5 and there seems to be no way to enter fastboot. It also is not recognised as an adb device
I have a amazfit pace but he is stucked on a update screen and when I try entring in fast boot mode he doesn´t enter and goes to update again and don´t conclude that. What can I do?
Did anybody managed to get Amazfit 2 (stratos) to fastboot using this method? thx...
EDIT: Yes, I can confirm it works! However it is really kind of tricky. Embrace yourselves!
Many thanks to you guys for finding this out, you are the best!
Thanks.
kiralex1995 said:
Hi,
I finally found the real method to boot our Amazfit watch into fastboot. It is difficult to success at any time, but you should be able to boot fastboot directly after some try.
Here is the procedure : (I've made a video : https://www.youtube.com/watch?v=ZlXoeq30vM0 )
When you try, I advice to put the watch in its charging base, the usb Cable connected to the base, but not on the PC.
Here are the steps to go in fastboot mode :
1) press the power button 2 seconds
2) release the button et repress it again without releasing it
3) when the screen of the watch switch off, plug the usb cable.
4) when the screen turn on, count from 1 to 4. At 4 release the power button. You are now in fastboot.
If it fails, try again. It is a little difficult.
Hope this helps.
kiralex
Click to expand...
Click to collapse
can confirm that this method (sort of) works for stratos as well.
i guess the important part is the 4 seconds after the light goes on. i have done it in like the 8th try.
i guess pulling the usb cable and reattaching it is not really required...
Hello my device is waiting for the logo, it is not opening.
endrancer said:
can confirm that this method (sort of) works for stratos as well.
i guess the important part is the 4 seconds after the light goes on. i have done it in like the 8th try.
i guess pulling the usb cable and reattaching it is not really required...
Click to expand...
Click to collapse
Hi all together,
yes I can confirm that plugging the cable is not neccessary. Went back to stock yesterday. Got into fastboot on first try.
I'm trying that on an actual Stratos watch way longer than 40 minutes - maybe you could help me: I have an "A1619"-model with firmware 2.3.5.0. Same for other Stratos users?
Unlike in the linked video, when I'm at step #4, the "A."-logo appears after about 2 seconds again, so if I release the power button after 4, it's already visible and bootup goes on as normal. Did you notice the same behavior with the "A."-logo before accessing fastboot?
E-lian said:
I'm trying that on an actual Stratos watch way longer than 40 minutes - maybe you could help me: I have an "A1619"-model with firmware 2.3.5.0. Same for other Stratos users?
Unlike in the linked video, when I'm at step #4, the "A."-logo appears after about 2 seconds again, so if I release the power button after 4, it's already visible and bootup goes on as normal. Did you notice the same behavior with the "A."-logo before accessing fastboot?
Click to expand...
Click to collapse
Hello
I've bricked my Pace and cannot enter fastboot.
When I try to enter fastboot I have the same behaviour on my Amazfit Pace. Have You managed some how to enter the fastboot without connection to the PC?
Hello, I turned on my phone this morning as usual however was instead presented into a Factory Test Mode, has happened for the first time. I then long pressed the power button but still no luck, after trying every combination possible I gave up. I charged the phone last night at 100% and turned it off as usual. (On stock rom, Oreo 8.0 not rooted or anything. - A2017GV1.3.0B03 ) Also, don't really want to disassemble or reset my phone. Any help would be much appreiated. Thanks!
owerevoke said:
Hello, I turned on my phone this morning as usual however was instead presented into a Factory Test Mode, has happened for the first time. I then long pressed the power button but still no luck, after trying every combination possible I gave up. I charged the phone last night at 100% and turned it off as usual. (On stock rom, Oreo 8.0 not rooted or anything. - A2017GV1.3.0B03 ) Also, don't really want to disassemble or reset my phone. Any help would be much appreiated. Thanks!
Click to expand...
Click to collapse
what is "long pressed"? You have to hold it for about a minute or so, did you?
If it doesn't work, FTM mode has ADB, so you should be able to hook it up to a PC and issue "adb reboot" from the terminal. If you end up in FTM again then your phone is just borked or something, you can attempt to fix it by using "adb reboot recovery" instead and reflash stuff
Choose an username... said:
what is "long pressed"? You have to hold it for about a minute or so, did you?
If it doesn't work, FTM mode has ADB, so you should be able to hook it up to a PC and issue "adb reboot" from the terminal. If you end up in FTM again then your phone is just borked or something, you can attempt to fix it by using "adb reboot recovery" instead and reflash stuff
Click to expand...
Click to collapse
Thanks, adb reboot solved it! Can't thank you enough!
Same case to me on OreoB03. Power button long pressed didn't respond. I used "minimal_adb_fastboot_1.4.1_portable" and command reboot.
svsavic said:
Same case to me on OreoB03. Power button long pressed didn't respond. I used "minimal_adb_fastboot_1.4.1_portable" and command reboot.
Click to expand...
Click to collapse
Same problem here.
But i do not know how to use ADB tool.
I dowloaded minimal adb fastboot tool and i have now 3 executable (adb, fastboot, MAF32) in a directory but I do not know how to use them in order to reboot my Axon 7.
I would appreciate a step by step guide, made for a very beginner.
Note also that I may not have already the device drivers on my computer.
Find cmd.exe in syistem32, run as administrator, drag adb.exe in cmd window. Write command adb reboot.
Impossible for me.
I am not even able to have the phone recognized since the drivers are not correctly installed and Zadig tools wont help.
I'm really stuck.
Would any Belgian Guys be able to help me having a computer with adb WinUSB drivers correctly installed so that we can reboot my phone with his PC with any adb tool ? Please PM me is so.
Phone is recognized as adb device (w/o driver). Just try this and write command adb reboot or reboot (i don't remember).
It is said that no devices is found.
?
Also had the same FTM problem and can confirm that power button did not work in stock Oreo.
If can't get adb reboot work, one simple way is to discharge the phone - USB type C connection is fully working in FTM mode (u can simply check that). Connect one or few (use simple usb spliter) USB devices (the best way is to connect devices, for example power bank, some bluetooth speaker, which actually suck energy etc.) to your phone in order to charge them and it will fully discharge the phone in a few hours. Then on phone turned off connect power charger, wait about 15-20 minutes to charge and turn on the phone as usual (using only power button for a few seconds).
Hello, i actually thought about this option of waiting for the battery to be discharged but did not dare to take the risk. I finally found someone that will "adb reboot" my phone tomorrow, fingers crossed.
Hi,
OK, let's hope that "adb reboot" option will succeed.
However, personally I see no risks in discharging the battery - when the phone discharges it just safely automatically turns off - no data loss, no need to reflash the ROM etc. I went through this route myself.
I think it could be another bigger risk to keep the screen on (not moving screen) for a longer time - possible burn in of screen etc. But not sure about this risk and don't want to frighten, maybe others have more knowledge on possible screen burn in issues. In my case after discharging the battery no burn in or other screen problems.
I ordered a OTG cable that should arrive tomorrow to discharge the phone if adb reboot does not work. Thank you for ur feedback.
Have you tried this tool to get to EDL and then you can use Miflash to flash back to stock https://forum.xda-developers.com/axon-7/how-to/salesmultidla2017-tool-to-unblick-dfu-t3854229
billjim24 said:
Have you tried this tool to get to EDL and then you can use Miflash to flash back to stock https://forum.xda-developers.com/axon-7/how-to/salesmultidla2017-tool-to-unblick-dfu-t3854229
Click to expand...
Click to collapse
that's not remotely useful to the situation
please read up before posting lmao
Mine Axon 7 did just that, couldn't turn it off in any way, also on b03 Oreo rom. So I let it discharge completely, and just did a normal power on, and it worked again.
I think that the Oreo Rom is in an awfully bad beta Rom rushed out from a sinking mobile company, that don't give a s... about their customers.
Will never buy ZTE again.
A friend could reboot mine with adb reboot. Problem solved.
I guess adb drivers did not worked well on m'y computer.
Next thing to do : downgrade to Nougat in order to get Daydream. What a shame.
Chinesur said:
A friend could reboot mine with adb reboot. Problem solved.
I guess adb drivers did not worked well on m'y computer.
Next thing to do : downgrade to Nougat in order to get Daydream. What a shame.
Click to expand...
Click to collapse
G B03 has daydream, hasn't it?
No, it doesn't have
Boot in FTM,open axon7toolkit,connect phone to laptop and follow instructions in axon7toolkit.It will reboot in edl and you can flash a firmware
My tab stopped working from on days to another. TWRP installed but I can't enter any mode! I can see it with ADB when I connect it to my Macbook.
I can enter the tab via shell (adb shell). Entering download mode is also not possible. The display then switches on and a second later off again - that's it!
ODIN also does not connect to it.
Don't know what happened to it. Now I try to get TWRP back to work and flash it again.
Any help here much appreciated!
Just suggests a totally flat battery to me.
ashyx said:
Just suggests a totally flat battery to me.
Click to expand...
Click to collapse
That's what I thought as well, but with ADB I see it connected and also can open a shell.
But I can't trigger recovery nor the download mode. ODIN also can't connect to it.
Absolutely clueless what to do.... ?
TGHH said:
That's what I thought as well, but with ADB I see it connected and also can open a shell.
But I can't trigger recovery nor the download mode. ODIN also can't connect to it.
Absolutely clueless what to do.... ?
Click to expand...
Click to collapse
So many times I've come across the same symptoms and almost always has been a flat battery.
Try a different charger and cable, leave it on charge for a few hours.
ashyx said:
So many times I've come across the same symptoms and almost always has been a flat battery.
Try a different charger and cable, leave it on charge for a few hours.
Click to expand...
Click to collapse
Thx, will charge it over the night and check again.
So I charged the tablet over night and it is still not booting. I guess the bootloader is corrupt or so.
Is it possible to fix it with ADB?