Guys, I get it. The atrix HD is an old phone and by making this thread I am digging up the past, but I've searched everywhere on this site and still don't have an answer. First of all before you read this, please note that I am very new to this flashing business and don't understand a lot of the tech lingo you guys use all over this forum. Excuse me for being stupid.
The problem I am having is that every time I try to reboot into cwm recovery, it takes me to a screen that I will include a screenshot of down below.
Before I started any of this, I rooted my phone using towelroot, unlocked my boatloader (I think) using motopocalypse's file.
I then downloaded CWM 6.0.4.4. Recovery for the Atrix HD . I then used the app Flashify (yes I know. I'm dumb) to backup my stuff such as my kernel and all that and then tried to install the .IMG file from my SD card. It downloaded and then asked me if I wanted to reboot. I clicked yes and then it went on this screen that said something about recovery failure and it gave me status code 0. I'll post the picture don't worry. I tried using the ROM manager app to install cwm but it did the exact same thing
Guys I know I'm not very good at this, but could someone please explain to me how to flash a custom recovery without a computer on the Atrix HD? And please include simple small steps, because I'm not the smartest at this crap. Also if you could not use so much tech lingo that would be greatly appreciated.
Thanks guys
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sinlesstitan said:
Guys, I get it. The atrix HD is an old phone and by making this thread I am digging up the past, but I've searched everywhere on this site and still don't have an answer. First of all before you read this, please note that I am very new to this flashing business and don't understand a lot of the tech lingo you guys use all over this forum. Excuse me for being stupid.
The problem I am having is that every time I try to reboot into cwm recovery, it takes me to a screen that I will include a screenshot of down below.
Click to expand...
Click to collapse
Hi
First of all, I can't see the screenshot that you posted for some reason. Could you upload it again?
Also, about your problem, if you already unlocked the bootloader, this is what you need to do:
First of all, make sure you have correctly installed the Motorola drivers. You can get them on the motorola site. You will need a computer to do this, preferably one with Windows on it.
Then, if everything is right with the drivers, turn off the phone. Then you need to press and mantain the volume-down button and then press and mantain the power button. Mantain both buttons pressed until you see a dark screen with some letters on it. Make sure it reads somewhere "Bootloader UNLOCKED". If it does, you are doing great.
Next, check the file that I uploaded. As you can see, it has your name on it and it's a .zip file. You will need to extract the content, preferably on a new folder on the root of your drive (Assuming you are using Windows, that would be C:/nameofthefolder/).
Next, you will need to open a console window. There are many ways to do it, but you can search for it on Windows. When you find the icon (a black one), right clic and use "Run as administrator". Then you need to navigate to the folder in which you saved the files. In the console, type "cd .." and press enter until you get to the root of the drive, then "cd nameofthefolder" to get there.
Now, to the good part. If your phone is still in fastboot mode (the black screen with white letters), you will type the following in the console and press enter: "fastboot flash recovery philz_touch_6.43.4-moto_msm8960.img" without the "". What this will do is send a flash command to your phone and it will flash the recovery indicated. It will show some message and then in about 4 seconds it will be done. And that's it. If it doesn't works or it says that it can't find "fastboot" or something, make sure you are in the right folder.
To enter the recovery, turn off the phone, press volume-up button and power button, mantain both until you see a purple screen with some options. That's the recovery. And from there, you can install a zip, a new ROM, and do some nice things, but be careful.
If you have any other inquiry, let me know.
mauchito said:
Hi
First of all, I can't see the screenshot that you posted for some reason. Could you upload it again?
Also, about your problem, if you already unlocked the bootloader, this is what you need to do:
First of all, make sure you have correctly installed the Motorola drivers. You can get them on the motorola site. You will need a computer to do this, preferably one with Windows on it.
Then, if everything is right with the drivers, turn off the phone. Then you need to press and mantain the volume-down button and then press and mantain the power button. Mantain both buttons pressed until you see a dark screen with some letters on it. Make sure it reads somewhere "Bootloader UNLOCKED". If it does, you are doing great.
Next, check the file that I uploaded. As you can see, it has your name on it and it's a .zip file. You will need to extract the content, preferably on a new folder on the root of your drive (Assuming you are using Windows, that would be C:/nameofthefolder/).
Next, you will need to open a console window. There are many ways to do it, but you can search for it on Windows. When you find the icon (a black one), right clic and use "Run as administrator". Then you need to navigate to the folder in which you saved the files. In the console, type "cd .." and press enter until you get to the root of the drive, then "cd nameofthefolder" to get there.
Now, to the good part. If your phone is still in fastboot mode (the black screen with white letters), you will type the following in the console and press enter: "fastboot flash recovery philz_touch_6.43.4-moto_msm8960.img" without the "". What this will do is send a flash command to your phone and it will flash the recovery indicated. It will show some message and then in about 4 seconds it will be done. And that's it. If it doesn't works or it says that it can't find "fastboot" or something, make sure you are in the right folder.
To enter the recovery, turn off the phone, press volume-up button and power button, mantain both until you see a purple screen with some options. That's the recovery. And from there, you can install a zip, a new ROM, and do some nice things, but be careful.
If you have any other inquiry, let me know.
Click to expand...
Click to collapse
Thanks for replying man it really means a lot. I will definitely try this later today and I'll let you know if I run into any problems. Also, I sent you a private message with a link to the picture on it, due to the fact I'm new here, xda developers won't let me post pictures on a thread yet.
Sinlesstitan said:
Thanks for replying man it really means a lot. I will definitely try this later today and I'll let you know if I run into any problems. Also, I sent you a private message with a link to the picture on it, due to the fact I'm new here, xda developers won't let me post pictures on a thread yet.
Click to expand...
Click to collapse
I just saw your screenshot. It looks like your bootloader is still locked. It must say "UNLOCKED" for you to install a custom recovery. There is a thread around here to do that, I honestly don't remember how to do it since I did it like 2 years ago, but search on this forum and you will find it. In case you can't unlock your bootloader, let me know and we'll see what we can do.
Look the image that I just uploaded. This is what you are looking for. This is how it should say. Note that it says "Device is UNLOCKED. Status Code: 3". Yours says "LOCKED".
Related
Kwongger's NVIDIA SHIELD All-In-One- Toolkit
An All-In-One Kit for our beloved Nvidia Shields.
Provides Unock, Recovery, Root, and Relock!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
SORRY NO DL...
THE TOOL IS DISCONTINUED!
CHANGELOG
...
And this is mine!
Videos will come in the future!
HAHA. I LOVE the disclaimer! "Unless your device starts shooting lasers. Then that's all me".
I seriously got a good laugh out of that!
red triangle in recovery
step 4 which should install super su gives a red triangle..Might want to try this on yours when you get one. thanks for trying..
brian13206 said:
step 4 which should install super su gives a red triangle..Might want to try this on yours when you get one. thanks for trying..
Click to expand...
Click to collapse
Make sure you're booted into android... All it does is adb push the supersu.zip And walk you through the rest.
to be fair
I realized I sounded a little snide.. that wasn't my intention... The red triangle goes away by itself once you unplug the cable.. not sure why but it isnt a brick. one thing I realized on the github solution is you have to put those rootmaster files in the file where you keep your adb files.. (it doesn't mention that) I should also mention that your 1 click did install a recovery as it was supposed to.. thanks again
brian13206 said:
I realized I sounded a little snide.. that wasn't my intention... The red triangle goes away by itself once you unplug the cable.. not sure why but it isnt a brick. one thing I realized on the github solution is you have to put those rootmaster files in the file where you keep your adb files.. (it doesn't mention that) I should also mention that your 1 click did install a recovery as it was supposed to.. thanks again
Click to expand...
Click to collapse
Did you try booted into android?
In the kit you start everything in android
It put the SuperSU zip in my download folder.
I saw that screen.. when I hit :"install" it went to red triangle...
brian13206 said:
I saw that screen.. when I hit :"install" it went to red triangle...
Click to expand...
Click to collapse
NO BOOTLOADER!!!
A post above confirmed that it is working!
If you still have issues, copy and paste the file and go from there
sigh...YES BOOTLOADER.. after I got red triangle I redid root with the github solution and all went well. I'm rooted all is well.. I wasn't trying to point fingers I just posted what happened to me. I'm sure no one will get the red triangle just me...Good luck in your endeavors
brian13206 said:
sigh...YES BOOTLOADER.. after I got red triangle I redid root with the github solution and all went well. I'm rooted all is well.. I wasn't trying to point fingers I just posted what happened to me. I'm sure no one will get the red triangle just me...Good luck in your endeavors
Click to expand...
Click to collapse
Dude. Really???????????
DO NOT START IN BOOTLOADER!!!!!
My method DOES NOT WORK THAT WAY.
Kwongger said:
Dude. Really???????????
DO NOT START IN BOOTLOADER!!!!!
My method DOES NOT WORK THAT WAY.
Click to expand...
Click to collapse
You're instructions CLEARLY say to be booted into Android...
wwjoshdew said:
You're instructions CLEARLY say to be booted into Android...
Click to expand...
Click to collapse
Thanks for the back up
I was getting kind of frustrated, I'll check his past posts... May be a sad attempt at a Troll.
wwjoshdew said:
It put the SuperSU zip in my download folder.
Click to expand...
Click to collapse
brian13206 said:
I saw that screen.. when I hit :"install" it went to red triangle...
Click to expand...
Click to collapse
I am guessing you are referring to the "Install" option in green text in wwjoshdew's 1st picture. Is that correct?
EDIT
Kwongger said:
Dude. Really???????????
DO NOT START IN BOOTLOADER!!!!!
My method DOES NOT WORK THAT WAY.
Click to expand...
Click to collapse
In reality it should not matter IF the Shield is already in bootloader mode or not. the only thing it does by already being in android is make it a little easier for people by not needing to enter bootloader mode by hand. There are alot of good reason to know how to do just that. as far a writing a batch script to automate the process there are options that can be used to check if the device is in fastboot or booted to android. I don't have them memorized, and don't have time to look them up right now.
chevyowner said:
I am guessing you are referring to the "Install" option in green text in wwjoshdew's 1st picture. Is that correct?
EDIT
In reality it should not matter IF the Shield is already in bootloader mode or not. the only thing it does by already being in android is make it a little easier for people by not needing to enter bootloader mode by hand. There are alot of good reason to know how to do just that. as far a writing a batch script to automate the process there are options that can be used to check if the device is in fastboot or booted to android. I don't have them memorized, and don't have time to look them up right now.
Click to expand...
Click to collapse
I adb push the file, so you have to be in Android.
Kwongger said:
I adb push the file, so you have to be in Android.
Click to expand...
Click to collapse
IF you are referring to the supersu.zip it does even need to be on the device to be installed. You can also use "adb push" in recovery, the catch here is if the device you push to is not mounted when pushing the file, the file will not be useable after it is mounted.
That is what the command "adb sideload" is for.
From the CWM main menu you go to install zip>install zip from sideload.
the command would be written in a batch file like this assuming the zip will be in the same folder as the batch script. "adb sideload supersu.zip"
If you are talking about the recovery is a better idea IMO to flash that from recovery.
chevyowner said:
IF you are referring to the supersu.zip it does even need to be on the device to be installed. You can also use "adb push" in recovery, the catch here is if the device you push to is not mounted when pushing the file, the file will not be useable after it is mounted.
That is what the command "adb sideload" is for.
From the CWM main menu you go to install zip>install zip from sideload.
the command would be written in a batch file like this assuming the zip will be in the same folder as the batch script. "adb sideload supersu.zip"
If you are talking about the recovery is a better idea IMO to flash that from recovery.
Click to expand...
Click to collapse
hmm... Never thought of that. I'll just stick with my method, IMO it is simpler and I have already plastered ALL OVER to start booted into android, thanks so much for the feedback!
If you have any other suggestions don't hesitate to let me know
hmmm never been accused of being a troll. i realize I should have never posted this. Just to be clear. I wasn't in bootloader when it happened.I was in android. I did step 4..(install su.) when it was finished I went into recovery to check and got the red triangle I stated that it reverted and restarted by itself and I just went and rooted via a different method.( github joshdew vid ) I tried to say that I didn't blame the Op or his 1 click... that I was posting just what happened to ME and that it probably wouldn't happen to anyone else. I even apologized if I was snide in my first post. I have had many smartphones and have never had an issue rooting. Shield was my only hiccup and I started all of this asking for help.
Let me know how the kit is working!!!
PM me any suggestions you have, for new features or for a new Supported device!!!!!!!!!!!
Thanks,
Kwongger
Dear Xda'ers,
I am really desperate on the situation and need your help.
I tried every solution to get into recovery mod including SFT and others available, no luck in getting there.
The rom is working, so no bricked phone situation, problem is gapps terminates itself making email and other functions unreachable.
So I want to switch to either the official rom or another one which is in the forum.
Phone is roooted by the way.
Any suggestions?
PS. As put in the title, this roms cook told me that he cannot help me.
---------- Post added at 11:33 PM ---------- Previous post was at 11:26 PM ----------
hasgerdas said:
Dear Xda'ers,
I am really desperate on the situation and need your help.
I tried every solution to get into recovery mod including SFT and others available, no luck in getting there.
The rom is working, so no bricked phone situation, problem is gapps terminates itself making email and other functions unreachable.
So I want to switch to either the official rom or another one which is in the forum.
Phone is roooted by the way.
Any suggestions?
PS. As put in the title, this roms cook told me that he cannot help me.
Click to expand...
Click to collapse
Hello.
If you just want to get into recovery mode, open terminal emulator.
Type
'su'
Allow it and type
'Reboot recovery'
Without '.
Works under cwm.
If this doesn't work.
Use smart flash tool.
(Quoted) ⬇
After flashing your phone should Boot into recovery.
Dont forget to do always a factory reset. If not -> bootloop
radkor said:
SmartFlash Tool completly erases device memory during flashing.
Phone will make Factory Reset at first boot after flashing!
You can upgrade and downgrade. You can downgrade from V20N too!
This also will remove phone lock if you forget unlock code or pattern. (phone lock, NOT simlock or network lock...)
This method doesn't need internet connection.
If you want to flash an LG P970H download correct ROM from link below.
With this solution you can unbrick LG Optimus Black P970.
It fixes bootloop, "ERROR LG Security Team", and BSOD - blue screen with green writings (untested).
Only requirement is ability to enter in to S/W Update mode and not broken hardware.
Tested on: Windows 7 Ultimate x86, x64 and Windows XP Pro SP3.
---------------------------------------------------------------------------------------------------------------
Downloads:
- SmartFlash Tool (mirror) [password: [email protected]]
- stock ROM V10A EEU XXX with .bin & .fls. [CRC MD5: d880b8834400575b5827bafbf29a745e] - DepositFiles, FileServe, WUpload.
Other bin/fls ROMs are HERE. (All these links are working again!)
You need to install LG Mobile drivers. They are located HERE. [CRC MD5: e4614071e72c0292d3a8238908b5c7ba]
1. Unpack SFT.rar that contains SmartFlash Tool program.
2. Unpack, preffered C: drive, firmware pack BIN_LGP970AT-00-V10a-EEU-XXX-MAY-09-2011_0.zip
Inside there will be 2 files: LGP970AT-00-V10a-EEU-XXX-MAY-09-2011+0_AP.bin i LGP970AT-00-V10a-EEU-XXX-MAY-09-2011+0_CP.fls.
3. Run B_SmartFlashTool_Extern.exe
4. Choose:
1) ROM copy D/L bookmark
2) in Select mode choose Normal mode
3) choose CP file: LGP970AT-00-V10a-EEU-XXX-MAY-09-2011+0_CP.fls
4) choose AP file: LGP970AT-00-V10a-EEU-XXX-MAY-09-2011+0_AP.bin
*) connect phone in S/W Update mode with battery in it (on the phone that is switched off, plug in USB cable WHILE HOLDING Vol+ button)
5) choose COM port.
6) choose LGE Mobile USB Serial Port in Communication Driver
7) click Start and wait till end.
It takes about 3 mins to flash.
After successfully flashing, phone will reboot and make Factory Reset.
And that's all!
Settings:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Flashing:
Finished:
Now your phone should be unbricked and working.
I will not take any responsibility if something goes wrong when you trying this solution. For me and many others it worked well.
Click to expand...
Click to collapse
Used ALL mentioned so far, brought it three different service centres, they couldn't manage to get into recovery as well
Any creative ideas?
hasgerdas said:
Used ALL mentioned so far, brought it three different service centres, they couldn't manage to get into recovery as well
Any creative ideas?
Click to expand...
Click to collapse
try this
washbeer said:
power up your phone, then press and hold vol down + home key and then also press and hold the power button until the phone restarts. then it should boot into recovery.
btw i made a small video tutorial
youtube.com/watch?v=Iu4O_zvrn6U
Click to expand...
Click to collapse
worked for me
ok it seems there is also an other way to enter recovery:
on switched off phone (and only then!) press and hold G-key + volume up and then press power key.
it should boot straight into recovery.
Cant you push recovery through adb/fastboot?
Sent from my HP 7 using XDA Premium HD app
Do you still have cwm and the custom ROM on your phone? If yes, simply download quickboot or rommanager from playstore and hit reboot recovery.
Sent from my LG-P760 using xda app-developers app
Hi guys,
Tried the two methods from DuffBoon and wash beer - no luck.
I think there is something wrong with gapps as it gives an error when I try to download smth from Google Play- so no option to load any new app.
I go into terminal emulator, input 'su' and have superuser rights, than punch 'reboot recovery', it reboots but no recovery at all.
My diagnosis is CWM and gapps is broken somewhat; SFT or another method is not working for that reason.
hasgerdas said:
Hi guys,
Tried the two methods from DuffBoon and wash beer - no luck.
I think there is something wrong with gapps as it gives an error when I try to download smth from Google Play- so no option to load any new app.
I go into terminal emulator, input 'su' and have superuser rights, than punch 'reboot recovery', it reboots but no recovery at all.
My diagnosis is CWM and gapps is broken somewhat; SFT or another method is not working for that reason.
Click to expand...
Click to collapse
But your system is still working? There is an adb flashable cwm recovery from redy06 somewhere here. Google:
Xda cwm touch redy06
And youll probably find it. You can flash it with the device on. There also is a reboot recovery script in the pack, so you can check if it works or not.
Sent from my LG-P760 using xda app-developers app
Thanks, seems interesting - I will try it and see whether it works or not (currently on Mac)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
This is my first walkthrough so I will do my best to do this properly. The Honor Note 8 does not have a forum yet, and this is the third thread for this phone. Hopefully we can get a forum up soon.
PLEASE NOTE THAT UNLOCKING BOOTLOADER WILL WIPE YOUR DEVICE AND POSSIBLY VOID YOUR WARRENTY!!!
I'M NOT RESPONSIBLE IF SOMETHING DOESN'T WORK.
Unlock Bootloader
Follow the steps here to begin the Bootloader Unlock process:
https://www.dc-unlocker.com/how-to-read-huawei-bootloader-unlock-code
1. a) Install the application
1. b) Follow the steps on the above page to put phone into "Manufacture Mode"
1. c) Under "Select Manufacturer", choose "Huawei Phones" and under "Select Model", choose the model of your phone
1. d) Click on "Buy Credits". You should end up being emailed a username and password, return to the Unlocker Client, and input those two
1. e) The Unlocker Client should return the bootloader unlock code
2. a) Enable Developer Options by clicking on the build number multiple times
2. b) Turn on USB Debugging
3. Prepare TWRP custom recovery before preceeding further. You can get it from here: https://drive.google.com/open?id=0B4xzs81XsmURVTRnUDJHdl9CQlE
3. Prepare and install ADB and Fastboot tools. I used this one http://forum.xda-developers.com/showthread.php?t=2588979
4. Go into the folder with your recovery and open a CMD (if you used system-wide ADB as linked above, otherwise place recovery in your ADB folder)
5. Put the phone into Bootloader mode with:
Code:
adb reboot bootloader
. This will take you to the bootloader mode (white screen with some small text)
6. Now type:
Code:
fastboot oem unlock <UNLOCK_CODE>
where
Code:
<UNLOCK_CODE>
is the bootloader code that the Unlocker Client gave you
Loading TWRP Custom Recovery
7. Your phone may reboot when the process is complete. We want to go back into Bootloader mode, so follow Step 5 again to go back to bootloader mode
8. Now type:
Code:
fastboot flash recovery <NAME_OF_YOUR_RECOVERY.img>
The recovery will flash over to your device. We want to reboot into the recovery mode.
9. Now type:
Code:
fastboot reboot
but just before you hit ENTER on that command, start holding VOLup and VOLdown at the same time (as explained below)
This phone has two recoveries on it, which is great since it makes it really hard to brick. In order to access custom recovery, you need to hold down both VOL buttons during boot process (from the very beginning) in order to access the custom recovery.
Once you have entered TWRP, you will most likely notice that it is in CHINESE. If you don't read chinese, follow the steps below to change to English UI in TWRP:
Change to English UI in TWRP
10. TWRP has two columns of 4 buttons, 8 buttons total. I have labeled the buttons as per their position as below:
1 2
3 4
5 6
7 8
11. Click button 6 to go to the Settings, then click on the "Globe" icon, then switch to english and click the button in the bottom right corner.
BACKUP!!
12. I highly recommend you now do a TWRP backup and place the backup on an External SD card (not the internal memory). This will save your ass if you mess anything up or it doesn't work for you. Do a full backup (select ALL of the options).
Installing Xposed
Grab the Installer APK here: http://forum.xda-developers.com/showthread.php?t=3034811
and the Framework zip here: http://dl-xda.xposed.info/framework/sdk23/arm64/
Put both files onto your SD card.
13. Boot into your rom, install the APK file (you may need to enable "unknown sources")
14. Then boot back into TWRP. Do this by restarting the phone, and just as the screen goes black, hold down both VOL buttons until you see text on the screen.
15. Install the framework, wipe cache/dalvik and reboot the phone
ROMs
There are several roms, all of which can be found here: http://forum.xda-developers.com/general/general/huawei-honor-note-8-roms-t3487575
I will try to update this post with instructions on how to install them once I have the process down properly.
Thanks to:
@benmeroff for his posting of all of those ROMs and his work on the original thread.
The link to the xposed installer is dead
jdantow said:
Installing Xposed
Grab the Installer APK here: http://forum.xda-developers.com/show....php?t=3034811
Click to expand...
Click to collapse
Just another small reminder this Xposed apk link is broken. Could I just download any Xposed apk or was this link for a specific version for the Note 8?
Thanks
remix435 said:
The link to the xposed installer is dead
Click to expand...
Click to collapse
Thank you! I updated the link, can you confirm it is working now from your end? Thanks so much!
The thread ID is 3034811 so if you take
Code:
http://forum.xda-developers.com/showthread.php
and add
Code:
?t=3034811
it should work for you
jlomein said:
Just another small reminder this Xposed apk link is broken. Could I just download any Xposed apk or was this link for a specific version for the Note 8?
Thanks
Click to expand...
Click to collapse
Thank you! I updated the link, can you confirm it is working now from your end? Thanks so much!
The thread ID is 3034811 so if you take
Code:
http://forum.xda-developers.com/showthread.php
and add
Code:
?t=3034811
it should work for you
Hopefully either a camera port or a camera hack can come about from developing. Anybody know about possible camera hack thats the only thing (IMO) this phone needs
jdantow said:
Thank you! I updated the link, can you confirm it is working now from your end? Thanks so much!
Click to expand...
Click to collapse
Thanks, downloaded Xposed 3.1.1 apk from that link now.
Cheers
hi
after i flashed trwp and did back up i stuck in bootloop
tried to flash kingvip rom - no luck. tried to recover from back up but stil in boot loop.
can anyone help me, please
Anyone happen to have the img for the modem? I believe mine may be corrupted.
hi i will my boodloader unlock my Note 8. The phone will not unlock. I have the ulock key. I hvae the Build Nummber B027.
Hi guys, a question...
The is no way I can install this drivers that are required... if I click the setup icons nothing happens at all, and if i try manually all i get is 4x "Android device" in the device manager, and locating drivers in the designated folders does not help, it still says "windows did not find the driver for your device...."
Anyone maybe had a similar problem/solution?
Thanksss
Bubreg said:
Hi guys, a question...
The is no way I can install this drivers that are required... if I click the setup icons nothing happens at all, and if i try manually all i get is 4x "Android device" in the device manager, and locating drivers in the designated folders does not help, it still says "windows did not find the driver for your device...."
Anyone maybe had a similar problem/solution?
Thanksss
Click to expand...
Click to collapse
Just google huawei drivers.... I had the same question but when i installed HiSuite the drivers was inside - it work fine, but it will always pop up when you connecting phone...
falc1 said:
Just google huawei drivers.... I had the same question but when i installed HiSuite the drivers was inside - it work fine, but it will always pop up when you connecting phone...
Click to expand...
Click to collapse
Thank you man, worked like a charm! I got the bootloader code... but since it's gonna wipe everything if I unlock it, I'm gonna wait until the next weekend most probably, too busy these days.
Hi guys,
i was able to unlock the bootloader but i can't flash the recovery and every time i try it display "remote: command not allowed".
Good morning.
I hope for Christmas to be a holder of Honor Note 8.
To unlock the bootloader you need to pay 4 euro through dc-unlocker.com program?
Thank you
m3sari0 said:
Hi guys,
i was able to unlock the bootloader but i can't flash the recovery and every time i try it display "remote: command not allowed".
Click to expand...
Click to collapse
Same thing happend to me
I relocked the bootloader then unlock it again and it works
player1990 said:
Same thing happend to me
I relocked the bootloader then unlock it again and it works
Click to expand...
Click to collapse
thanks man it worked.
TWRP - changing language
OP - thank you for this thread. Was able to follow the steps and get most of the things accomplished.
One thing that i am having trouble with is - changing the TWRP language from Chinese to English. In button #6, the globe icon is not even clickable. All others are, but that one is not. Any ideas? Thanks!
EDIT: I got it to work. It seems some icons in the corners of the screen can be a little hard or slow to respond... if you (a future reader) are having the same issue - try kind of mini swiping in circles over that icon and it will eventually respond.
Hi,
I requested the unlock code on the Huawei site but I get this error:
The Huawei ID used to apply for the unlock code has not been used on the device for more than 14 days.
How can I do?
Some might apply to me
MarkAndroid said:
Hi,
I requested the unlock code on the Huawei site but I get this error:
The Huawei ID used to apply for the unlock code has not been used on the device for more than 14 days.
How can I do?
Some might apply to me
Click to expand...
Click to collapse
You have to wait 14 days or pay for the credits on DC-unlocker app
Hi everyone, really sorry i have to create a new thread on this topic, i have checked and browsed about this about a billion and one times and nothing seem to work is why i thought maybe someone can help me with a more detailed solution. I updated my LG G4 H811 recently and the proximity sensor refused to work again and it fueled my quest to install a new ROM as i have always wanted to. SO i checked all the threads and they put in there to type some commands in the cmd and people said it worked for them but over the past few days I've been trying nothing has worked for me. the closes I've come is a Universal fastboot tool and the only thing that does was reboot my phone and every other command it just says waiting for the device and i have installed and uninstalled a lot of drivers adb and the LG driver itself but it doesn't just work. Whenever i right-clicked the folder to get CMD to open in th folder it opens the windows shell command rather and that doesn't work. Please can anyone help me, I need to install the TWRP recovery to install this new ROM. Thank you.
olufalujo said:
Hi everyone, really sorry i have to create a new thread on this topic, i have checked and browsed about this about a billion and one times and nothing seem to work is why i thought maybe someone can help me with a more detailed solution. I updated my LG G4 H811 recently and the proximity sensor refused to work again and it fueled my quest to install a new ROM as i have always wanted to. SO i checked all the threads and they put in there to type some commands in the cmd and people said it worked for them but over the past few days I've been trying nothing has worked for me. the closes I've come is a Universal fastboot tool and the only thing that does was reboot my phone and every other command it just says waiting for the device and i have installed and uninstalled a lot of drivers adb and the LG driver itself but it doesn't just work. Whenever i right-clicked the folder to get CMD to open in th folder it opens the windows shell command rather and that doesn't work. Please can anyone help me, I need to install the TWRP recovery to install this new ROM. Thank you.
Click to expand...
Click to collapse
Get yourself a blank DVD or a USB drive with 8GB or more space.
Use FWUL https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
It will have ADB working, fastboot working, etc. Then try following the guides (print it out, save it as a PDF, whatever you need to do to access it when doing the commands using FWUL.)
Possible solution
I was in a similar situation as you some days back. But found a way around.....
Heres how i got around it.
Step 1:
If your lg g4 h811 is on stock MM, connect your phone to your pc, pull down the notification menu from your status bar. You'll be prompted to select the usb connection mode. Select mtp.
Another pop up will come on, prompting you to install usb drives. Accept/select it.
Now, on your pc, the icon of your lg should appear like a cd rom. Double click and install the usb drivers.
I'll give you step 2: soon when i have my pc close by.
Cuz you might find the instructions confusing if i write it out of my memory.....
Okay... I'll appreciate. Thank you
Possible solution , step 2:
In step 1, i assumed that your g4 is set to allow usb debugging and oem unlock.
Now type "device manager " on your pc search bar.
Lunch the device manager. and plug your g4 via usb.
You should see "adb device interface/bridge" at the top of your device manager list(with a green icon i guess, lets call this DRIVER21) .
Now, go and execute the cmd command that reboots your phone. your phone enters fastboot mode. Execute the next code that displays "waiting for device".
Now go to your device manager window. You should see "adb device interface/bridge" at mid-way through your device manager list with a yellow exclamation sign , right click, select "Update driver sofware" > Browse my computer for driver software > let me pick from a list of device driver..........
A list of android adb device drivers/interfaces should appear. Now select/highlight DRIVER21 (described above) among d list, click next. At this point, it should display "installing driver software" after wich you'll get a success message.....
Go back to your cmd window.
The code that generated the "waiting for device " msg should have been executed.
You shouldn't have any problems with subsequent cmd codes thence.
Reply if you get stock anywhere.
I wrote most of this as far as i can remember. Cuz am not on stock MM anymore.
pizzaboy192 said:
Get yourself a blank DVD or a USB drive with 8GB or more space.
Use FWUL https://forum.xda-developers.com/an.../live-iso-adb-fastboot-driver-issues-t3526755
It will have ADB working, fastboot working, etc. Then try following the guides (print it out, save it as a PDF, whatever you need to do to access it when doing the commands using FWUL.)
Click to expand...
Click to collapse
You are a genius pizzaboy192 thank you so much. I've been able to flash the twrp and also a new rom.
Sophophiler said:
In step 1, i assumed that your g4 is set to allow usb debugging and oem unlock.
Now type "device manager " on your pc search bar.
Lunch the device manager. and plug your g4 via usb.
You should see "adb device interface/bridge" at the top of your device manager list(with a green icon i guess, lets call this DRIVER21) .
Now, go and execute the cmd command that reboots your phone. your phone enters fastboot mode. Execute the next code that displays "waiting for device".
Now go to your device manager window. You should see "adb device interface/bridge" at mid-way through your device manager list with a yellow exclamation sign , right click, select "Update driver sofware" > Browse my computer for driver software > let me pick from a list of device driver..........
A list of android adb device drivers/interfaces should appear. Now select/highlight DRIVER21 (described above) among d list, click next. At this point, it should display "installing driver software" after wich you'll get a success message.....
Go back to your cmd window.
The code that generated the "waiting for device " msg should have been executed.
You shouldn't have any problems with subsequent cmd codes thence.
Reply if you get stock anywhere.
I wrote most of this as far as i can remember. Cuz am not on stock MM anymore.
Click to expand...
Click to collapse
I just found out that it was your steps i used not the other guy's and i said thanks to him and not you...sorry about that...thank you so much Sophophiler..you are the bomb
olufalujo said:
I just found out that it was your steps i used not the other guy's and i said thanks to him and not you...sorry about that...thank you so much Sophophiler..you are the bomb
Click to expand...
Click to collapse
Olufalujo.......... Am glad i could be of help, everyone that tries to help deserve a "thanks".
Which Rom did you flash?? I am on H-rom Android 7.0 Nougat.
By: TecknoFreak .
Everything about the G4 is improved, especially the camera.
I want to test his other roms (stock roms). Cuz hotspot does not work on this rom.
So tell me wich rom you're on, and the experience thus far..........
Sophophiler said:
Olufalujo.......... Am glad i could be of help, everyone that tries to help deserve a "thanks".
Which Rom did you flash?? I am on H-rom Android 7.0 Nougat.
By: TecknoFreak .
Everything about the G4 is improved, especially the camera.
I want to test his other roms (stock roms). Cuz hotspot does not work on this rom.
So tell me wich rom you're on, and the experience thus far..........
Click to expand...
Click to collapse
I flashed Android Nougat Stock rom but the reason i flashed the rom still exist. auto brightness stopped working when i updated the MM to Android 6.0.1 Software version H81120x and a funny screen comes up during calls in place of the screen going black and coming on after the call.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
and proximity sensor still dont work, now it says no sensor detected
Sophophiler said:
Olufalujo.......... Am glad i could be of help, everyone that tries to help deserve a "thanks".
Which Rom did you flash?? I am on H-rom Android 7.0 Nougat.
By: TecknoFreak .
Everything about the G4 is improved, especially the camera.
I want to test his other roms (stock roms). Cuz hotspot does not work on this rom.
So tell me wich rom you're on, and the experience thus far..........
Click to expand...
Click to collapse
olufalujo said:
I flashed Android Nougat Stock rom but the reason i flashed the rom still exist. auto brightness stopped working when i updated the MM to Android 6.0.1 Software version H81120x and a funny screen comes up during calls in place of the screen going black and coming on after the call.
and proximity sensor still dont work, now it says no sensor detected
Click to expand...
Click to collapse
i've tried to attatch an image it's not sowing
Am no this rom.......... https://forum.xda-developers.com/tmobile-g4/development/rom-h-rom-g6-port-t3669066
Download and flash if you can live without hotspot until its fixed. Camera and battery life is improved, proximity sensor works.
Otherwise, download and install this rom.............. https://forum.xda-developers.com/tmobile-g4/development/rom-despacito-n-rom-v1-0-t3659805
I haven't test this rom, but i think its more stable (hotspot included) than the one am on.
Both are stock android Nougat 7.0.
Goodluck........
I wanted to remove root, tried following some guides and so I came upon trying to uninstall magisk. I was prompted with two choices, "Restore images" and "Complete Uninstall".
I tried out Restore images first and it said "stock backup does not exist" so I then proceeded to do a complete uninstall. I got stuck then in recovery mode bootloop.
I therefore tried to go to my recovery by turning off my phone first and now it's in this perpetual charging state, I removed the connector but it's still "charging". Forcing it to turn off by holding the power button doesn't work as well.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I was scared of root so I tried removing it since it was rooted when I got it, but now here I am :crying::crying::crying: please help.
Thank you very much.
Try power button + Volume down for up to 10 seconds.....should shutdown and reboot after a few seconds of shutdown
(Meaning, it will shutdown and appear to just be off.....but it will actually start to reboot after a few seconds of nothing.....so be prepared/ready to do the button mash to boot to recovery......it will vibrate once as it begins to boot again....
*****edit.....
Sorry I'm in the wrong thread (different phone), but its possible you need to press and hold power plus volume up/or volume down.
Best of luck
Sent from my [device_name] using XDA-Developers Legacy app
Thank you for the suggestion, but sadly for me it doesn't work. My phone doesn't shutdown at all and is just in this perpetual charging state even after holding the power button for 30 seconds.
Hanzor said:
I wanted to remove root, tried following some guides and so I came upon trying to uninstall magisk. I was prompted with two choices, "Restore images" and "Complete Uninstall".
I tried out Restore images first and it said "stock backup does not exist" so I then proceeded to do a complete uninstall. I got stuck then in recovery mode bootloop.
I therefore tried to go to my recovery by turning off my phone first and now it's in this perpetual charging state, I removed the connector but it's still "charging". Forcing it to turn off by holding the power button doesn't work as well.
I was scared of root so I tried removing it since it was rooted when I got it, but now here I am :crying::crying::crying: please help.
Thank you very much.
Click to expand...
Click to collapse
Which rom version are you on? You need to boot into fastboot mode abs flash the same stock boot img. I may well have it to hand in my cloud folder. Lemme know the version, hopefully all will be well again
reg66 said:
Which rom version are you on? You need to boot into fastboot mode abs flash the same stock boot img. I may well have it to hand in my cloud folder. Lemme know the version, hopefully all will be well again
Click to expand...
Click to collapse
Is the rom like the OS version? I'm not sure but I have this RAW file in my pc. My uncle said to leave it here just in case, it's called "WW_ZS660KL_16.0631.1910.35_M3.13.33.30". I also have this "root&bootstockww191035.zip" file so maybe the 191035 is my OS version? If I remember correctly he said the phone is chinese and he had to do stuff to make it english.
It's either that or Android 9.0.
Hanzor said:
Is the rom like the OS version? I'm not sure but I have this RAW file in my pc. My uncle said to leave it here just in case, it's called "WW_ZS660KL_16.0631.1910.35_M3.13.33.30". I also have this "root&bootstockww191035.zip" file so maybe the 191035 is my OS version? If I remember correctly he said the phone is chinese and he had to do stuff to make it english.
It's either that or Android 9.0.
Click to expand...
Click to collapse
Oh, you need to be quite sure as the boot img needs to match the rom. When it was rooted do you remember ever updating it? I should have 1910.35 boot img hopefully, I'll check in a mo
reg66 said:
Oh, you need to be quite sure as the boot img needs to match the rom. When it was rooted do you remember ever updating it? I should have 1910.35 boot img hopefully, I'll check in a mo
Click to expand...
Click to collapse
I've never gotten to update it, I see other people have android 10 and such but mine doesn't see the update so I just left it be. Should be the same as when I got it.
Hanzor said:
I've never gotten to update it, I see other people have android 10 and such but mine doesn't see the update so I just left it be. Should be the same as when I got it.
Click to expand...
Click to collapse
OK, I'll be in soon, will have a hunt :good:
---------- Post added at 10:57 AM ---------- Previous post was at 10:10 AM ----------
Hanzor said:
I've never gotten to update it, I see other people have android 10 and such but mine doesn't see the update so I just left it be. Should be the same as when I got it.
Click to expand...
Click to collapse
Here's the link for both root and stock boot img's 1910.35_root and stock_imgs
Are you ok with the process or do you need guidance?
reg66 said:
OK, I'll be in soon, will have a hunt :good:
---------- Post added at 10:57 AM ---------- Previous post was at 10:10 AM ----------
Here's the link for both root and stock boot img's 1910.35_root and stock_imgs
Are you ok with the process or do you need guidance?
Click to expand...
Click to collapse
I'm not very familiar with how it works, if it's okay I would be glad to be guided.
Hanzor said:
I'm not very familiar with how it works, if it's okay I would be glad to be guided.
Click to expand...
Click to collapse
That's no problem, but I've been awake now for 2 days straight. I really can't focus on anything right now. Maybe later tonight or tomorrow. Sorry dude
reg66 said:
That's no problem, but I've been awake now for 2 days straight. I really can't focus on anything right now. Maybe later tonight or tomorrow. Sorry dude
Click to expand...
Click to collapse
That's alright, I'm fine with later or tommorow as well. Rest well, and thanks!
reg66 said:
That's no problem, but I've been awake now for 2 days straight. I really can't focus on anything right now. Maybe later tonight or tomorrow. Sorry dude
Click to expand...
Click to collapse
Hey man, hope you got to rest well! Here with just a fair bit of inquiry.
So, today I've tried looking for guides on sideloading. Got my phone to bootloader as well by depleting the battery then charging it up to be able to boot into bootloader.
I got my phone then to fastboot using the adb method, my device was recognized in the adb devices command as well. The problem is, fastboot devices don't show up any results. I'm scared to worsen the problem so I didn't continue past this point.
I could see my device in the device manager as well.
Am I on the right track?
Hanzor said:
Hey man, hope you got to rest well! Here with just a fair bit of inquiry.
So, today I've tried looking for guides on sideloading. Got my phone to bootloader as well by depleting the battery then charging it up to be able to boot into bootloader.
I got my phone then to fastboot using the adb method, my device was recognized in the adb devices command as well. The problem is, fastboot devices don't show up any results. I'm scared to worsen the problem so I didn't continue past this point.
I could see my device in the device manager as well.
Am I on the right track?
Click to expand...
Click to collapse
Hey dude, so sorry for the late reply, so damn tired!! You may well now be aware of some of this etc but I'll post any way so it's all there...
1. Download and install Minimal ADB and Fastboot app (windows). Install it on your PC to root of C drive
2. Download the root&bootstockww191035.zip and extract it to the Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot) from here
3. Boot into fastboot mode ( from powered off, hold volume up then press and hold power button. Fastboot mode is the 1st screen you come across, the one with the options to Start, boot to recovery, etc...)
4. Still in fastboot mode, connect phone to pc using side port on phone.
5. Go to C:\Program Files (x86)\Minimal ADB and Fastboot and double click cmd-here.exe
6. Check your device is recognised in fastboot mode by the pc/laptop by typing 'fastboot devices' in cmd window. If it is recognised you will see a string of numbers and/or letters.
7. Type 'fastboot flash boot boot.img' in cmd window.
That's it, you should now have the correct boot img for your device flashed and hopefully it'll boot up again.
Good luck
reg66 said:
Hey dude, so sorry for the late reply, so damn tired!! You may well now be aware of some of this etc but I'll post any way so it's all there...
1. Download and install Minimal ADB and Fastboot app (windows). Install it on your PC to root of C drive
2. Download the root&bootstockww191035.zip and extract it to the Minimal ADB and Fastboot Folder (C:\Program Files (x86)\Minimal ADB and Fastboot) from here
3. Boot into fastboot mode ( from powered off, hold volume up then press and hold power button. Fastboot mode is the 1st screen you come across, the one with the options to Start, boot to recovery, etc...)
4. Still in fastboot mode, connect phone to pc using side port on phone.
5. Go to C:\Program Files (x86)\Minimal ADB and Fastboot and double click cmd-here.exe
6. Check your device is recognised in fastboot mode by the pc/laptop by typing 'fastboot devices' in cmd window. If it is recognised you will see a string of numbers and/or letters.
7. Type 'fastboot flash boot boot.img' in cmd window.
That's it, you should now have the correct boot img for your device flashed and hopefully it'll boot up again.
Good luck
Click to expand...
Click to collapse
Thanks for the time man, hopefully it does work.
Edit: IT WORKS!
Had a few hiccups which was fixed by disconnecting and reconnecting the cable after going into fastboot.
THANK YOU!
Seriously, THANK YOU!
Please have a good rest, and take care!
Hanzor said:
Thanks for the time man, hopefully it does work.
Edit: IT WORKS!
Had a few hiccups which was fixed by disconnecting and reconnecting the cable after going into fastboot.
THANK YOU!
Seriously, THANK YOU!
Please have a good rest, and take care!
Click to expand...
Click to collapse
Excellent. Glad it's all good again :good: