Database Users

[Q] Help I botched It!!!

Hi there i have a rotted kindle fire with burrito root.
I rooted it yesterday and everything was fine, then i turned it off and back on later it worked fine.
the next day it hangs on the boot logo (it is animated no triangle)
adb recognizes it yet i cant access adb root, remount etc Permission denied.
I cant install TWRP
What i wanted to do was go to the /sdcard directory and push the update.zip there. but i cant because it read-only. How do i change any of these? Ive read 6 other posts on possible fixes none of which work.

Have you tried pressing the power button for 20 seconds and then restarting it?

nope
Yes i did that does not help.
adb says it cannot be root in production builds. I looked up how to do it but its either vague or makes no sense or does not work. why is it a production buold? it didnt do that when i rooted my fire in the first place so why is it doing it now?

What i believed happened is that when i went to past the andoid market's vending.apk into the system/app folder it deleted all of the things in the folder and nothing worked not even the GUI. I hard reset and then i got stuck at the logo. Dont know if that would clarify anything

that clariefys a lot - if you messed up your /system this should help you:
http://forum.xda-developers.com/showthread.php?t=1414832
then you should be able to install twrp
hopefully ...

Thanks but that did not help. It isnt recognized in adb like that.

Can you get into recovery? When you boot it up do you see FireFireFire at all?

No it says KindeFire and its animated.

sorry but i think you'll need a factory cable to get in fastboot mode
you'r not the first one ...

I have a micro usb and it works to connect (well until i followed that link and followed the instructions )

melmantheman said:
No it says KindeFire and its animated.
Click to expand...
Click to collapse
Hi,
Did you have a look at this too:
http://forum.xda-developers.com/showthread.php?t=1356257
I had quite the same issue with mine ...Device was not recognizable at all on Windows (unknown drivers)
I used this guide and it just worked like a charm.
regards
mjay

melmantheman said:
I have a micro usb and it works to connect (well until i followed that link and followed the instructions )
Click to expand...
Click to collapse
i think you did'nt understand what a factory cable is
it's a special cable which forces the kf in fastboot mode
you can build or buy one
make a search for "factory cable" and you'll know ...

http://forum.xda-developers.com/showpost.php?p=21151545&postcount=118

HP slate 7 Extreme root tutorial plz!

Hey, I just bought a Hp slate 7 extreme and love it but i want to root my tablet. It was rooted using Vroot when my tab is 4.2.2. Now problem is someone or something has triggered the update to 4.3 and now i lost the root access. Tried using Vroot, onesuperclick and even the supertool by Tom but to no avail. There also towelroot but it make my tablet hanged and if i force close, it restarts the tab.
Also heard so much bad thing about 4.4.2 so i rather not up my os. Plz help me in my situation. I have check other threads and couldn't find a solution for this (at least for 4.3) would love a youtube video tutorial.
thank you

Sazz said:
Hey, I just bought a Hp slate 7 extreme and love it but i want to root my tablet. It was rooted using Vroot when my tab is 4.2.2. Now problem is someone or something has triggered the update to 4.3 and now i lost the root access. Tried using Vroot, onesuperclick and even the supertool by Tom but to no avail. There also towelroot but it make my tablet hanged and if i force close, it restarts the tab.
Also heard so much bad thing about 4.4.2 so i rather not up my os. Plz help me in my situation. I have check other threads and couldn't find a solution for this (at least for 4.3) would love a youtube video tutorial.
thank you
Click to expand...
Click to collapse
For starters this is the wrong Forum Thead to post in, it should be in the Q&A Forum.
Second you didn't use search as if you got here : http://forum.xda-developers.com/showthread.php?t=2541784 it will tell you with clear instructions on how to root the TegraTab.
Please insure that your threads are in the right place. I mean no disrespect but XDA have rules for a reason.

Ahh my bad, I'll try and be more careful. Now, I have read that link there already and it doesn't work. Also now my situation has worsen in that it got updated to 4.4.2.......I still tried all other methods, Vroot, towelroot, supertool etc . Tried to do the manual fastboot also doesn't work, impact or see no device so stuck over there. Has anyone found a way to root?

If Impactor does not find your device fastboot mode, try another USB port. If that doesn't work, try another computer if possible.
Also, make sure that you are running Impactor as administrator by right-clicking the application and pressing "Run as administrator".

Edit: this is a different device

I did try other computers and still no avail, even with admin access. Also HP slate 7 extreme is basically a Tegra note 7 not different device. Just few minor changes. If only the fastboot work, i probably be rooted by now. Is there a way to back 4.2.2? like put the recovery 4.2.2 in sd and recover from the loader? would it brick my device? Also i found out about towelroot modstring, is there a specific modstring for hp 7 extreme? would like to try it.
thank you

Sazz said:
I did try other computers and still no avail, even with admin access. Also HP slate 7 extreme is basically a Tegra note 7 not different device. Just few minor changes. If only the fastboot work, i probably be rooted by now. Is there a way to back 4.2.2? like put the recovery 4.2.2 in sd and recover from the loader? would it brick my device? Also i found out about towelroot modstring, is there a specific modstring for hp 7 extreme? would like to try it.
thank you
Click to expand...
Click to collapse
In this case unlock bootloader
Flash TWRP and check if it works, if so flash supersu

Hey shaky, thank you for replying. he boot loader is still lock. When device off , I press power n vol up to get into this menu which has fastboot protocol, selected it but nothing happens, then check for driver in impactor, no device detected. So can't use Tom's supertool to unlock bootloader. Also did the command prompt, say fastboot not recognize internal or external etc....
There also a recovery kernel, which leads to a recovery menu that can open zip files, think I can do just flash twrp ?
Thanks

Sazz said:
Hey shaky, thank you for replying. he boot loader is still lock. When device off , I press power n vol up to get into this menu which has fastboot protocol, selected it but nothing happens, then check for driver in impactor, no device detected. So can't use Tom's supertool to unlock bootloader. Also did the command prompt, say fastboot not recognize internal or external etc....
There also a recovery kernel, which leads to a recovery menu that can open zip files, think I can do just flash twrp ?
Thanks
Click to expand...
Click to collapse
Install the drivers when the menu shows up, don't select anything at all.

Sazz said:
Hey shaky, thank you for replying. he boot loader is still lock. When device off , I press power n vol up to get into this menu which has fastboot protocol, selected it but nothing happens, then check for driver in impactor, no device detected. So can't use Tom's supertool to unlock bootloader. Also did the command prompt, say fastboot not recognize internal or external etc....
There also a recovery kernel, which leads to a recovery menu that can open zip files, think I can do just flash twrp ?
Thanks
Click to expand...
Click to collapse
Install fastboot drivers then go to your boot loader menu and type
Fastboot flash recovery twrplocation.IMG, this will flash twrp then boot into twrp (recoverykernel) install SuperSU

Thanks for replying. I did all that was suggested and nothing has changed. Problem is that impactor won't detect my device and won't install driver.
Took these pics to show what i'm seeing (left to right)
1) First pic is when tab is off, I power and vol up to get that menu,
2) Second pic impactor can't detect anything.
3) Third pic is if i select Recovery Kernel, a No command show, did power and Vol up to get this recovery menu

What does the Device Manager show? For instance, when the tablet is in the recovery menu, can you see an unidentified device?
EDIT: What operating system are you running? Are you an administrator? Are you running Impactor as administrator?

In recovery mode, nothing shows up in device manager
In normal tab mode, it show android phone with subset android composite adb interface. Also there a ? MTP

anyone?

Update! : I exchange my tab, now its 4.2.2 and just rooted it with vroot. Voila surprise that towelroot and impactor still not working....
now that its rooted, is there a way to install cmw/twrp? tried the supertool but no luck with impactor so can't fastboot command.
can i just put cmw or twrp in sd and flash it from the android revocery menu?
thanks

Bump....could use some expertise help here
Thank you

From the sound of it you are rooted but not unlocked. So, flashing Roms and things will not work until you do that.
However if I am wrong and you have unlocked the boot loader, go right ahead and flash some ROMs.

I found off another thread that our HP S7E running kitkat can be rooted with towelroot v1. It's a one-click root method. Just download the apk, install and run it, and the tablet will be rooted! Just take note to install supersu from the play store

Root 4.4.2 HP Slate 7 Extreme
See my tutorial here: http://forum.xda-developers.com/nvidia-tegra-note-7/help/root-4-4-2-hp-slate-7-extreme-t2850893

HP Slate 7 Beats Special Edition
Hello new to this thread. Wanted to ask if this root method would work on the HP slate 7 beats special edition, the beats special edition looks very similar to the HP slate 7 extreme, and also the Nvidia Tegar note 7.

[Q] Screen cracked and unresponsive but display still visible. Need help getting data

Hi guys,
I recently dropped my Nexus 4 on the floor today and the screen cracked. As a result, the screen is completely unresponsive now but I am able to see its display when I press the power button. Could you guys help me/point me in the right direction regarding how to get the data I have on the phone (music, photos etc.) please.
My Nexus is unrooted/stock version. I tried connected it to my laptop via USB, but all it does it charge. I think I might have the USB debugging option enabled (as I remember enabling it before sometime ago). I'm running the latest firmware (5.0.1 I believe). Also the bootloader is locked.
Any help would be much appreciated.
Thanks
EDIT: I should note that I have a Password (PIN) for the lock screen.
I installed android sdk and tried to enter commands, but it didn't work. When I typed in 'adb devices', no serial came up (I checked sdk manager for the google usb driver, and it says it's installed). Also, when I tried typing in anything i.e. 'adb shell' it said error no devices found. I was attempting to follow a guide to set up adb for any other steps required to get my data from the internal storage. Bear in mind, I don't have much knowledge on these tools, all I'm doing is following any guides. Please can you help me how to get my photos or the contents of the sdcard.

The pin is not letting you boot into the os and that's why adb isn't working. Can you get into the bootloader? If so boot into twrp then try adb
fastboot boot twrp.img. Where twrp.img is the full file name.
Sent from my Nexus 9 using XDA Free mobile app

jd1639 said:
The pin is not letting you boot into the os and that's why adb isn't working. Can you get into the bootloader? If so boot into twrp then try adb
fastboot boot twrp.img. Where twrp.img is the full file name.
Sent from my Nexus 9 using XDA Free mobile app
Click to expand...
Click to collapse
Thanks for responding. I can enter the bootloader (if that's the Volume Down + power button menu). Quick google search shows that twrp is for customer recovery. Bear in mind that I haven't unlocked the bootloader or installed anything like recoveries before (it is basically a stock N4). Would I need to install it? If so, please could you direct me to a tutorial or guide me step-by-step on what to do as I don't have too many ideas on what to do to get the data from the phone.
Just to clarify: My N4 is completely stock, Bootloader is locked (says 'LOCK STATE - locked' in bootloader menu) and it is unrooted. I remember having the USB debugging option enabled the last time I was in the dev menu on the phone.

oracle93 said:
Thanks for responding. I can enter the bootloader (if that's the Volume Down + power button menu). Quick google search shows that twrp is for customer recovery. Bear in mind that I haven't unlocked the bootloader or installed anything like recoveries before (it is basically a stock N4). Would I need to install it? If so, please could you direct me to a tutorial or guide me step-by-step on what to do as I don't have too many ideas on what to do to get the data from the phone.
Just to clarify: My N4 is completely stock, Bootloader is locked (says 'LOCK STATE - locked' in bootloader menu) and it is unrooted. I remember having the USB debugging option enabled the last time I was in the dev menu on the phone.
Click to expand...
Click to collapse
We'll you've got a problem. You'll have to unlock the bootloader to run fastboot commands and that'll completely wipe your device. And with the pin and an unresponsive screen you can't get into the os. There really isn't anything you're going to be able to do to save your files. Sorry about that.
Edit, just one more thought, are you still on 4.4.4? If so there may be a hope. Shoot, you'll need to boot into the os though. So my idea isn't going to work.

jd1639 said:
We'll you've got a problem. You'll have to unlock the bootloader to run fastboot commands and that'll completely wipe your device. And with the pin and an unresponsive screen you can't get into the os. There really isn't anything you're going to be able to do to save your files. Sorry about that.
Edit, just one more thought, are you still on 4.4.4? If so there may be a hope. Shoot, you'll need to boot into the os though. So my idea isn't going to work.
Click to expand...
Click to collapse
Ah that was what I feared ... I'm running the latest firmware (5.0.1). I wouldn't really care about the phone if it weren't for a few images (should have had it backed up!).
Now I need to decide whether or not to change the screen etc. for £35 or just look in the market for a new phone. If I did buy a new screen/digitiser/frame thing, would these be suitable (where I won't need to use heat guns or glue and stuff)?
ebay (dot) co.uk/itm/LCD-Screen-Display-Touch-Digitizer-for-LG-E960-Google-Nexus-4-Frame-Replacement-/331224787829?pt=UK_Replacement_Parts_Tools&hash=item4d1e892b75
OR
ebay (dot) co.uk/itm/For-LG-E960-Google-Nexus-4-LCD-Display-Digitizer-Touch-Screen-Frame-in-Black-/331227949021?pt=UK_Replacement_Parts_Tools&hash=item4d1eb967dd
Also, if I did change it using the above, would dissembling the phone and reassembling it cause my data to be lost?
Thank you for your help
Edit: I managed to save about 80 photos which were probably in the default images folder in the SD card using AndroidLost. I'm guessing the other images which were in other folders i.e. WhatsApp Images etc. aren't recoverable using the site

AT&t Huawei Ascend XT H1611 Rooting Help.

I have unlocked the bootloader but I can not figure out how to root this thing at all. Has anyone had any success? I would like TWRP and SuperU.

this device is new yet. give it time

Tmobilefan906 said:
this device is new yet. give it time
Click to expand...
Click to collapse
Yeah I didn't realize how new this was whenever I posted it.

TWRP and root instructions available now in post 1 of
https://forum.xda-developers.com/android/general/huawei-ascend-xt-h1611-t3507933/
dabadguycr said:
I have unlocked the bootloader but I can not figure out how to root this thing at all. Has anyone had any success? I would like TWRP and SuperU.
Click to expand...
Click to collapse

divineBliss said:
TWRP and root instructions available now in post 1 of
https://forum.xda-developers.com/android/general/huawei-ascend-xt-h1611-t3507933/
Click to expand...
Click to collapse
You've already been helping me before you posted this.

People reading this thread might not realize we have root now. It's for their benefit .
dabadguycr said:
You've already been helping me before you posted this.
Click to expand...
Click to collapse

divineBliss said:
People reading this thread might not realize we have root now. It's for their benefit .
Click to expand...
Click to collapse
Good Point, I know my thread shows up first on Bing whenever I search for my phone and rooting help.

I have another XT and followed all instructions fine but no SuperSU when checking the phone. I tried flashing it twice (the one from the OP in main thread) and nothing. Am I missing a step?
I had installed fine on the first phone. this new one is 100% stock, unlocked bootloader, installed TWRP successfully but no supersu and root checker confirms no root.

Is it B140 or what? If you are missing a step, only you can check that.
powerserge1 said:
I have another XT and followed all instructions fine but no SuperSU when checking the phone. I tried flashing it twice (the one from the OP in main thread) and nothing. Am I missing a step?
I had installed fine on the first phone. this new one is 100% stock, unlocked bootloader, installed TWRP successfully but no supersu and root checker confirms no root.
Click to expand...
Click to collapse

divineBliss said:
Is it B140 or what? If you are missing a step, only you can check that.
Click to expand...
Click to collapse
Fixed

Can someone check the EMUI Huawei website for the unlock bootloader? Is it still working for requesting code? It keeps loop me back to the EMUI 5.0 page

sweetboy02125 said:
Can someone check the EMUI Huawei website for the unlock bootloader? Is it still working for requesting code? It keeps loop me back to the EMUI 5.0 page
Click to expand...
Click to collapse
Ya same. I got angry since I spent hours trying to find it so I just paid $4 and had DC-Unlocker unlock my bootloader.

sweetboy02125 said:
Can someone check the EMUI Huawei website for the unlock bootloader? Is it still working for requesting code? It keeps loop me back to the EMUI 5.0 page
Click to expand...
Click to collapse
webosFTW said:
Ya same. I got angry since I spent hours trying to find it so I just paid $4 and had DC-Unlocker unlock my bootloader.
Click to expand...
Click to collapse
If you follow this guide there should be no issue. The rootmygalaxy link should be pretty straightforward at unlocking the bootloader. The guide should be stickied in the OP.
https://forum.xda-developers.com/showpost.php?p=70515102&postcount=649

powerserge1 said:
If you follow this guide there should be no issue. The rootmygalaxy link should be pretty straightforward at unlocking the bootloader. The guide should be stickied in the OP.
https://forum.xda-developers.com/showpost.php?p=70515102&postcount=649
Click to expand...
Click to collapse
The issue is that https://emui.huawei.com/en/plugin.php?id=unlock that page hasnt worked for days. Keep redirecting me to the main page.

webosFTW said:
The issue is that https://emui.huawei.com/en/plugin.php?id=unlock that page hasnt worked for days. Keep redirecting me to the main page.
Click to expand...
Click to collapse
Yes use a different browser. Not working with chrome but working with edge. Go to the same link, it will bring you to EMUI 5.0 page, towards the top click on "download" then on the following page under the search bar click on "unlock bootloader" and it will bring you to the unlocking page. Just confirmed working. Updating the guide and will make a new post for root and twrp
Updated guide: https://forum.xda-developers.com/android/development/huawei-ascend-xt-h1611-feb27-2017-t3564389

Unlocked the boot loader, now adb/fastboot-15 Second won't work
Hello guys!
I used the 15 Second minimal adb/fastboot package from this site to unlock the boot loader. All seemed to go well, a screen message said success or something like that. It's been over 2 weeks since I had to put the phone down and take care of some other business. Now, after turning the phone off and then back on again when I am ready when I type in "fastboot devices" in the elevated cmd window in the adb directory the only message that comes back is "waiting on the device." Or the equivalent. I have tried what I could find from searching with Google to no avail. I am pretty sure that I am using the same cord, laptop, and everything that worked when I unlocked the boot loader. So, I am at a loss.
My goal originally was to use madvane20's slim downed version of b180 just to get it working again as my almost 2 years old P10 was stolen. I have no money in my budget for a new phone until Feb. 2020. I last talked with him in a series of PM's ending around May of last year, when a reply stated he had to get back to work on the last part of it. I have since seen a post referencing that it was ready in a package that after I had successfully unlocked the boot loader, it would root and install everything. This would have made me a happy guy... but I also noticed a custom ROM is now to be had based on Android 7. In order to get my Bank App's updated version of it's Mobile App to work, I have to install Android v 7 or higher. That's the main app that needs v 7 or better that I use daily. Several times...
But, now when I power up the phone, the first message is, "Your device has been unlocked and cannot be trusted... Press the Power Key now to reboot. Or the device will automatically reboot in 5 seconds." Which it does, the first time walking me through the Set-Up process, now it just boots into Huawei's EMUI 4.1. But, I cannot get adb to find the phone to follow the remainder of the instructions in the guide, "AT&T Huawei Ascend XT H1611 Feb27, 2017 update all things Root and TWRP (guide)"
Nor, can I get into the Recovery mode using the Vol Down/Power Keys.
So, where have I gone wrong or what is my next step? Since the phone can not be found and I can not get into Recovery using the proper keys what do I need to do and how do I do it?
I want to:
Root the phone.
Install the custom ROM I mentioned.
Or, Install an upgrade, if possible, to Android v 7... But,
can not get the phone recognized to get into a Recovery mode (is that right?) to push TWRP to it as well as the other files
it needs and to do whatever the Guides tell me to do.
Specs on the phone:
Model: H1611
Build: H1611C07B180
EMUI v: 4.1
Android v: 6.0.1
Security Patch level: September 1, 2017
Baseband v: 20234
Kernal v: 3.10.49-g03b627c
Sorry for the long post, but I thought it might answer some questions that came to mind before replying back.
Thanks in advance. I'm not here often, but when I am I am always relieved to get out of some jam I have gotten myself into!
mike0921

mike0921,
What happens if the phone is in normal mode and you type "adb devices" from the PC adb directory command prompt?

divineBliss said:
mike0921,
What happens if the phone is in normal mode and you type "adb devices" from the PC adb directory command prompt?
Click to expand...
Click to collapse
I just now found a new(er) USB cable for the phone. I also uninstalled the H1611 under Portable Devices in the Device Manager and rebooted the laptop. Where before, under Events the message was ".... needs further installation..." it now showed a successful install.
At the "adb devices" command, nothing happened, no response. I went and found the directions and explanations for the use of the top 30 commands. It told me to reboot the bootloader. A screen on the phone had me confirm the RSA command. Afterwhich the Fastoot&Recovery Mode screen with the little green Android guy with the message Phone Unlocked, FRP Unlock messages.
I went back to the elevated cmd window and at the adb directory command prompt entered "fastboot devices" and Voila! There were some letters and numbers, five or six spaces and the word "fastboot."
So, am I good to go with the rest of the steps in the guide from here? A question, about him saying to flash the Superuser zip file using TWRP. Is that suppose to already be on my SD card to flash it or can I flash it from my laptop without having to touch the phone or current USB cable? It seems stable but I am a bit gunshy and don't have much faith left in the old equipment I am having to use. A very old, refurbished HP Elitebook 8460P which is running really wonky, a not too new USB cable, the last of five I dug up and have used and finally works but is a bit loose, and Windows 10 1903 etc., which has disappeared all kinds of things I am having to run down) Can I use the "push" command to move the zip file to the SD card? And is that a fastboot function or an adb function? I seem to have read somewhere along the way to this point here that "push" is what I want to do, but powerserge1's Step 7 states to flash it using TWRP. I just want to check. And should questions from here on out be placed in his 184-page thread? I still haven't managed to read the whole thing, it seems to go off in so many other directions that I don't think I need to travel down. But, I will follow your advice.
I want to say a hearty thanks for your help. I was stuck, confused and frustrated at getting no results from Googling and reading for hours and getting nowhere it seemed. And I think I am good to go now.
Thoughts? Suggestions?
Just to be clear, The SuperSU zip file is currently on my laptop in the adb directory. Not on the phone.

mike0921 said:
I just now found a new(er) USB cable for the phone. I also uninstalled the H1611 under Portable Devices in the Device Manager and rebooted the laptop. Where before, under Events the message was ".... needs further installation..." it now showed a successful install.
At the "adb devices" command, nothing happened, no response. I went and found the directions and explanations for the use of the top 30 commands. It told me to reboot the bootloader. A screen on the phone had me confirm the RSA command. Afterwhich the Fastoot&Recovery Mode screen with the little green Android guy with the message Phone Unlocked, FRP Unlock messages.
I went back to the elevated cmd window and at the adb directory command prompt entered "fastboot devices" and Voila! There were some letters and numbers, five or six spaces and the word "fastboot."
So, am I good to go with the rest of the steps in the guide from here? A question, about him saying to flash the Superuser zip file using TWRP. Is that suppose to already be on my SD card to flash it or can I flash it from my laptop without having to touch the phone or current USB cable? It seems stable but I am a bit gunshy and don't have much faith left in the old equipment I am having to use. A very old, refurbished HP Elitebook 8460P which is running really wonky, a not too new USB cable, the last of five I dug up and have used and finally works but is a bit loose, and Windows 10 1903 etc., which has disappeared all kinds of things I am having to run down) Can I use the "push" command to move the zip file to the SD card? And is that a fastboot function or an adb function? I seem to have read somewhere along the way to this point here that "push" is what I want to do, but powerserge1's Step 7 states to flash it using TWRP. I just want to check. And should questions from here on out be placed in his 184-page thread? I still haven't managed to read the whole thing, it seems to go off in so many other directions that I don't think I need to travel down. But, I will follow your advice.
I want to say a hearty thanks for your help. I was stuck, confused and frustrated at getting no results from Googling and reading for hours and getting nowhere it seemed. And I think I am good to go now.
Thoughts? Suggestions?
Just to be clear, The SuperSU zip file is currently on my laptop in the adb directory. Not on the phone.
Click to expand...
Click to collapse
And after backing up in TRWP, I just checked the SD card's contents for the backup and saw the SuperSU zip file neatly placed on it as well. Just to be clear!??!
Okay, I somehow screwed this up I think. I was a little distracted by a friend dropping by. After telling her to give me a minute, I looked back at the phone after following Step 6:
Step 6: Confirm phone goes to FASTBOOT & RESCUE mode.
a) fastboot devices (to make sure your device is recognized)
b) fastboot boot TWRP.img (boots TWRP.img from Step 3)
c) The phone will boot into TWRP. Always select Keep Read Only from the first screen every time you go into TWRP.
Peek around a bit if you want to, then use TWRP to backup your stock recovery to external micro SD.
d) Reboot bootloader from inside TWRP to flash this custom recovery image (no adb command this time, you are rebooting to the bootloader from TWRP, you will see this option under "reboot" in TWRP).
e) fastboot flash recovery TWRP.img (now flashes TWRP recovery to the phone)
I then went to Step 7:
Step 7: After phone reboots, get into TWRP recovery repeating Step 6, a and b or hold the power button and volume up button from power-off state, then release when you see Huawei logo.
But now, the phone isn't being recognized again. And when I shut it off, hold Volume Up and Power buttons, I get a screen that asks if I want to: Reboot system now; Wipe data/factory reset; Wipe cache partition. Not the Recovery Screen with the options I got used to seeing in little green characters.
I tried the Reboot system now option and I'm back into the Huawei EMUI with everything appearing unchanged. Powered off, did the Vol Up + Power buttons and am back with the screen offering the three options I mentioned above. And the phone not being recognized after the "Devices" command.
Can you clarify my confusion? What am I doing wrong? Or not doing?
Thanks.
mike
---------- Post added at 06:47 PM ---------- Previous post was at 05:53 PM ----------
mike0921 said:
I just now found a new(er) USB cable for the phone. I also uninstalled the H1611 under Portable Devices in the Device Manager and rebooted the laptop. Where before, under Events the message was ".... needs further installation..." it now showed a successful install.
At the "adb devices" command, nothing happened, no response. I went and found the directions and explanations for the use of the top 30 commands. It told me to reboot the bootloader. A screen on the phone had me confirm the RSA command. Afterwhich the Fastoot&Recovery Mode screen with the little green Android guy with the message Phone Unlocked, FRP Unlock messages.
I went back to the elevated cmd window and at the adb directory command prompt entered "fastboot devices" and Voila! There were some letters and numbers, five or six spaces and the word "fastboot."
So, am I good to go with the rest of the steps in the guide from here? A question, about him saying to flash the Superuser zip file using TWRP. Is that suppose to already be on my SD card to flash it or can I flash it from my laptop without having to touch the phone or current USB cable? It seems stable but I am a bit gunshy and don't have much faith left in the old equipment I am having to use. A very old, refurbished HP Elitebook 8460P which is running really wonky, a not too new USB cable, the last of five I dug up and have used and finally works but is a bit loose, and Windows 10 1903 etc., which has disappeared all kinds of things I am having to run down) Can I use the "push" command to move the zip file to the SD card? And is that a fastboot function or an adb function? I seem to have read somewhere along the way to this point here that "push" is what I want to do, but powerserge1's Step 7 states to flash it using TWRP. I just want to check. And should questions from here on out be placed in his 184-page thread? I still haven't managed to read the whole thing, it seems to go off in so many other directions that I don't think I need to travel down. But, I will follow your advice.
I want to say a hearty thanks for your help. I was stuck, confused and frustrated at getting no results from Googling and reading for hours and getting nowhere it seemed. And I think I am good to go now.
Thoughts? Suggestions?
Just to be clear, The SuperSU zip file is currently on my laptop in the adb directory. Not on the phone.
Click to expand...
Click to collapse
And after backing up in TRWP, I just checked the SD card's contents for the backup and saw the SuperSU zip file neatly placed on it as well. Just to be clear!??!
Okay, I somehow screwed this up I think. I was a little distracted by a friend dropping by. After telling her to give me a minute, I looked back at the phone after following Step 6:
Step 6: Confirm phone goes to FASTBOOT & RESCUE mode.
a) fastboot devices (to make sure your device is recognized)
b) fastboot boot TWRP.img (boots TWRP.img from Step 3)
c) The phone will boot into TWRP. Always select Keep Read Only from the first screen every time you go into TWRP.
Peek around a bit if you want to, then use TWRP to backup your stock recovery to external micro SD.
d) Reboot bootloader from inside TWRP to flash this custom recovery image (no adb command this time, you are rebooting to the bootloader from TWRP, you will see this option under "reboot" in TWRP).
e) fastboot flash recovery TWRP.img (now flashes TWRP recovery to the phone)
I then went to Step 7:
Step 7: After phone reboots, get into TWRP recovery repeating Step 6, a and b or hold the power button and volume up button from power-off state, then release when you see Huawei logo.
But now, the phone isn't being recognized again. And when I shut it off, hold Volume Up and Power buttons, I get a screen that asks if I want to: Reboot system now; Wipe data/factory reset; Wipe cache partition. Not the Recovery Screen with the options I got used to seeing in little green characters.
I tried the Reboot system now option and I'm back into the Huawei EMUI with everything appearing unchanged. Powered off, did the Vol Up + Power buttons and am back with the screen offering the three options I mentioned above. And the phone not being recognized after the "Devices" command.
Can you clarify my confusion? What am I doing wrong? Or not doing?
Thanks.
mike

Sorry for the delay. What's the latest status with attempts to root the phone?

Help with adb/recovery/root for Silverstrong Android 9

Hello!
I've recently got a Silverstrong Android 9 Head Unit: https://www.aliexpress.com/item/32822937592.html?spm=a2g0s.9042311.0.0.328e4c4dWZb7Fi
Can someone help me on how to get adb access or a custom recovery (mainly for rooting purpose)?
I have to mention that I've tried connecting a notebook with adb via and USB cable (male USB type A to USB type A), but it seems nothing happens. I can tell that the unit's USB ports are working for USB sticks.
I have also tried some combination implying the reset hole present on the front, but I couldn't make it work.
Any help is appreciated! Thanks!
Edit: I have to mention that the unit packs a MediaTek MT8321M if it matters.

Just an update: I have followed the instructions provided here for rooting: https://forum.xda-developers.com/showpost.php?p=76725981&postcount=740 . Everything went well until I tried to reboot the device. Now it is stuck in a bootloop (it passes the kernel bootlogo but it is stuck on Android bootlogo) and I really need to access its recovery. It would be my only hope to try to unbrick it. Unfortunately the only physical switch of the unit is just a reset hole on the front which will cut the power right away (tried multiple pressing combinations, none worked). I really need to enter recovery mode and I am pretty desperate, so any advice is welcome. Thanks!

I couldn't make it boot into recovery mode, but it did boot when I placed on a usb stick a file named "ZQ_MTK1B_UPDATE_HeXinDa_EN_8003_08152051.zip" and then it started to flash it automatically. After the flash completed, the unit recovered from bootloop, but now it seems there is no sound and no radio. I posted all of this just in case somebody ever will have to deal with same kind of trouble. It seems the unit is actually branded as alps ZQ8003 and I will ask the seller for some firmware/more technical info.

Hi, I have the same problem. Did you make it?