yashsingh1/xdaforums huggingface dataset:
[General Questions and Answers] sl93acko:
I want to install a custom rom on my Moto E3 power device. So here's what I have done till now

I have unlocked the bootloader.

Now I press the power button +vol up key to enter into boot options.

Then I go to fastboot mode and try flashing the twrp recovery using the following command

This however doesn't flash the existing out-of-the-box useless recovery.

So I tried again with

These just restart the phone without booting into recovery mode.

Anyway I can get the twrp recovery working on Moto E3 power?
[General Questions and Answers] scaryzombieBot34287:
Just barely joined XDA, and starting out in android development. I have an LG fortune with cricket wireless phone that Im interested in rooting for development purposes. Its not my primary phone so I'm not worried about losing data, mostly interested in tinkering with Android software. For some reason it refuses to stop at the Bootloader screen. In other words it just goes straight to booting up with the cricket welcome screen regardless of what method. I have tried rebooting with "adb reboot Bootloader"/"adb reboot fastboot" and also holding the volume button and power button method. None will work for whatever reason. I have it also on USB debugging and OEM unlock so not sure if there is another configuration I need do. Interested in any thoughts on this.

-Thanks
[General Questions and Answers] Deleted member 1890170:
To bring back phone to Normal mode you run

adb devices
adb reboot
[General Questions and Answers] scaryzombieBot34287:
Normal mode? Phone does not have issue rebooting. Phone will not halt at Bootloader screen regardless of steps I have tried.
[General Questions and Answers] Deleted member 1890170:
Sorry. I misread your initial post.
[Google Home] Texnolog74:
It's been a while since the initial release of the google home hub but no one knows how the firmware really get's flashed using the hidden micro usb port under the rubber bottom surface.

Well, it's very simple, it uses the Amlogic S905D2G chip ( similar to what cheap tv boxes have ) which means it can be simply flashed with a custom rom via the Amlogic Usb burning tool. In order for it to go into flashing mode you need to hold both volume up and down buttons then plugging the power cable whilst also having the micro usb cable is plugged into a computer.

As you can see the connection is successful meaning that this can truly be flashed but...

There is a small catch, google never reveals pre compiled firmware for these devices meaning you would have to compile it. There was recently an update from which there was a high possibility google was transitioning to a different OS called fuchsia while seamlessly leaving the same UI as the original OS was and hopefully still is android.

Once the drivers are installed, The google home hub can be seen as what is above. before driver install, your computer should've detected it as GX-CHIP

Hope this helps with future development on this little platform as I don't see much going on.

LINKS :

Amlogic USB burning tool - https://androiddatahost.com/qh5pm

Amlogic drivers - https://mega.nz/file/7TBhwSTC#AE_oDwohj7TnZZB0aLq8idcDKWlu-LX2x-FnXhERxhM
[Google Home] GuyInDogSuit:
{Mod edit: Quoted post removed}

Wrong thread?
[Google Home] CSX321:
Yeah, wrong section, but I don't see a way to delete it. Sorry about that.
[Google Home] Zastando:
{Mod edit: Quoted post removed}

Does this apply to other Google Home Speakers, more specifically to the LG WK7 ?
[Google Home] Oswald Boelcke:
I've removed your post that I recognised by accident. If you require any type of thread maintenance like the deletion of a post, simply use the report button and alert the moderators team. We're happy to assist.

Regards

Your friendly neighbourhood watch
[Google Home] latino147:
I was hoping to find a way to flash the original firmware on the first gen hub, but there are no roms available anywhere? :(
[Google Home] bazzap_nz:
Mine has toasted itself - I suspect it got corrupted doing an update and Google can't help me. They say "It's dead Jim!". Has anyone found a valid ROM that I can flash it with and see if I can resuscitate it? TIA
[Google Home] Zastando:
I see that some of you guys are interested in fixing/modifying your device(s), me included.

So I wondered if you may be interested in creating a Github project to help us out eachother.

I definitely would!
[Google Home] keerttttt:
Maybe good to know that after the fuchsia upgrade everything has changed. Holding volume up while powering up gives fastboot mode. Volume down gives recovery mode but I don't know what that does.

I flashed a TWRP build over my recovery and now the recovery is broken... Stupid. Anyone wanna try to tinker with the recovery? Maybe try a port scan. Or try volume up or down while in recovery?
[Google Home] dv03:
Hello - I also have a bricked google nest hub. I removed the bottom. The micro usb socket is connected to the pc. A cdc device was found. more precisely two of them. I have loaded the armlogic driver, but the device is not recognized in the burning program. I would be very interested if someone could generate a recovery file to repair the device. thx martin
[Google Home] ThoughtFraud:
My Google Nest Hub bricked itself. I believe it happened when I powered it off while it was booting up.

I can hold 2 keys and get into Recovery mode, but I just get stuck on the "G" screen when trying to reset the device.

I too have a "CDC-Ethernet" device when I plug the micro USB (hidden underneath) into my computer.

I would love to be able to restore a standard ROM, or even a custom one.
[Google Home] Cr4z33:
I am trying to fastboot my 1st gen Nest Hub, but it looks like it doesn't.

What I do is to keep pressed VOL+ and then I power up the device.

Is that correct?

I desperately need to fastboot it because it looks like something f up the firmware (factory reset has the same behaviour) and it ends up with a white screen loop crash.
[Google Home] Electro_:
Does anyone have a Compiled version of the nest hub software?
[Google Home] MAIKELN80:
any news? I have a google nest hub wotn boot onlyG logo, any solution? factory reset dont resolve the problem
[Google Home] danico253:
did i find this link? It will be that it is the solution or it is fake http://gofirmware.com/content/google-nest-hub-custom-firmware
[Google Home] matteo94s:
do you also have the firmware? Can you download it from your nest hub?
[Google Home] Jaavilf:
Have you found any firmware? Since my Nest Hub entered a loop mode and stayed in recovery mode so I would like to reinstall the software

Has encontrado algun firmware? Ya que mi Nest Hub entro en un modo de loop y se quedo en modo recovery por lo cual me gustaria volver a instalar el software
[Google Home] deadman96385:
Thought I would drop this here, in theory it would be possible to expand the exploit to affect more models.

Breaking Secure Boot on Google Nest Hub (2nd Gen) to run Ubuntu

In this post, we attack the Nest Hub (2nd Gen), an always-connected smart home display from Google, in order to boot a custom OS. First, we explore both hardware and software attack surface in search of security vulnerabilities that could permit arbitrary code execution on the device. Then...

fredericb.info
[Google Home] Motorih90:
Hi! Help me find the original firmware ROM for google nest 2

I have a dummy version, but it can be reflashed via micro usb and usb flasher tool from first post
[Google Home] bloxycola:
I managed to reboot one in bootloader mode
[Google Home] bloxycola:
I have a question
[Google Home] zelitomas:
Maybe this would be helpful (maybe not) - I've noticed this article:

Bricked and Fixed - My Adventures with Google Nest Hub - HackMD

> # Bricked and Fixed - My Adventures with Google Nest Hub > ## Introduction The story began abo

hackmd.io

If you take a look one of the last screenshots, it seems that the author has made the dump of all the partitions of this device. It might be worth a try to contact her and politely ask whether she could make those images available.
[Google Home] mongobbongo:
Hi,

have tried and contact the person mentioned?

If so, i would highly appreciate if you could share it!

Thank you in advance
[Google Home] bloxycola:
You think we can port android to the nest since amolgic kernels are compatiable with each other
[Google Home] beckmx23:
Hello guys, so I followed the articles because the developers were not easy to reach, here are some pictures, in order to make an exploit we need to get access to the UBoot, I tried connecting to the UART and it does respond, however it looks like it is encrypted, I leave here a dump of the info it outputs in case someone identifies the encryption

UART output is on the txt file
[Google Home] nebster:
@beckmx23 Output like that is usually indicative of a wrong serial baud rate. Have you tried other baud rates?
[Google Home] beckmx23:
@nebster I tried from 9600 to 1000000, the all time famous 115200 didnt work
[Google Home] bobzer:
@beckmx23 did you try to change the parity ?

becuase indeed it look like a wrong serial parameters
[Google Home] beckmx:
I didnt change parity, I use the common 8bit one, any suggestion which can i try?
[Google Home] beckmx:
@bloxycola how did you reboot it in boot mode
[Google Home] bloxycola:
Holding volume up while plugging it in

There's bunch of modes btw
[Google Home] bobzer:
no idea but maybe try at least 115200 with and without parity
[Google Home] traviszech:
Normally if it isn't 8n1 then use 7e1 (7 bits even parity 1 stop bit)
[Google Home] bbs233:
The baud is 115200, it is confirmed 8n1, the pins are next to the USB port, my usb serial adapter requires XON and XOFF, but the pins are the 4th and 5th from the USB side

It seems the google home nest hub max is running Sherlock and the g12b newman custom google firmware for u-boot. according to the UART serial messages upon boot while holding vol buttons
[Google Home] bloxycola:
Can you help me dump the UTART files?
[Google Home] bloxycola:
Can someone help me boot Ubuntu on a Nest Hub 1st gen?
[Google Home] Alexeydt:
guys, hi! My frame hung on the “G” logo and I managed to connect it via the USB port and through this program. the program saw it. I thought it might be possible to reflash it, but I can’t find the firmware anywhere. Maybe someone knows or can help with this? Google Nest Hub 2nd Gen
[Google Home] bloxycola:
Try to boot ubuntu into it
[Google Home] Alexeydt:
this can only be done by following the instructions with githu b - fredericb? Using an additional DIY debug board? Can’t you just flash it using a micro-USB cable and a computer?
[Google Home] bloxycola:
Nope, you need a raspberry pi and the y cable.
[Google Home] davidhacker01:
Can someone please send me the image file

I got one that's a store demo

Nest hub max

It's sad to see it go in the garbage it's working properly
[Touch Diamond, MDA Compact IV General] Chuckle:
Heeeelpp !!! :eek:

I am going crazy over this problem : :mad:

I have had my HTC Diamond for less than two months and it has worked fine.

Two days ago it started misinterpreting my stylus' pointing on the screen.

It seem that the sensory-element in the screen has "moved"...

I have recalibrated the screen several times and it works for some 6 - 10 clicks.

Then the touch of the stylus is either not registered (if I try to reach something on top part of the screen) or I get results as if I was pointing between 0,1cm - 1,5 cm or more above og under (it varies) the actual contact point of the stylus (needless to say - I have given up using my fingertip).

I have tried with soft reset and have also tried the hard reset but to no avail.

It means that I can't use the phone for one thing and also, that most of the other functions are out of reach or very very hard to use because of the displacement.

Ozgur ? / Anybody ? :confused:

Chuckle
[Touch Diamond, MDA Compact IV General] mikey1963:
I have exactly the same problem on my wifes Diamond. Just havent got round to reporting it yet, thought i'd let her suffer a while first. ;)
[Touch Diamond, MDA Compact IV General] Chuckle:
Suffering

If it is acting up like mine, she must be crawling the walls by now and refusing any form of physical contact - just like the phone does ... :D :D

Mine is so bad now, that I can't call a number from my list or pick up the phone without 4 -5 tries at hitting the right spot let alone using any other function.

Against better knowledge I today updated the ROM with the new one from HTC - and it is quite evident, that is is a hardware thing.

I am handing in my complaints and the phone today.
[Touch Diamond, MDA Compact IV General] tepss:
I had the same problem on dutty's v2.2 rom yesterday. I reflashed a radio as i had problem with gps as well and it is good back again. Reflash your radio. If not flash radio and other rom. Usually HTC rom don't upgrade your radio!
[Touch Diamond, MDA Compact IV General] Diskun:
Same problem here, my diamond stated misinterpreting slightly the stylus, now it's all just messed up, wherever you click, it detects the pulsation at the upper left side of the screen. It doesn't pass the calibration phase either.

I did not try to reflash the radio, just reflashed the stock SPL and original Vodafone ROM for sending it to RMA. However they are telling me that the whole RMA-thing will take AT LEAST 2 weeks. Over 15 days without my phone. I need it, that's madness! They should give the users a new phone and send the other back to HTC for whatever they want to do with it!

I think it happened after I tried playing a bad-formatted WAV file and the phone crashed. Should I try the Radio thing?
[Samsung Galaxy M51 Questions & Answers] nextGaurav:
Can we install Viper4Android in our M51 device? Please share steps if possible, I would thank in advanced.
[Samsung Galaxy M51 Questions & Answers] Affangta:
No it doesn't work but there's a good alternative: JamesDSP. It's a magisk module so its easy to install. I've been using it for months without issues. Sound quality is on par with Viper4Android although the UI is not that streamlined.
[Samsung Galaxy M51 Questions & Answers] nextGaurav:
Thank you so much for answering. I have no idea when Viper mod will be available but can only wait.
[Samsung Galaxy M51 Questions & Answers] xn0live:
if u have root then viper working
[Samsung Galaxy M51 Questions & Answers] soulexit:
Viper works with Magisk, installing ainur audio first resolves problem.
[General Questions and Answers] Grendel25:
The default dictionary for my Galaxy Note 8 phone is Collins. But I'd prefer to use Merriam Webster, which is installed on my phone. Is it possible to change the default dictionary so that when I select a word and choose Dictionary from the popup menu, I get MW results instead? For example, I wanted to look up "polymath", but Collins gave me a definition for "playmate." There have been other words I've tried to look up in the past that Collins just had no clue about.
[Xiaomi Mi 11] koloure2211:
As the title says, can you flash the weekly rom over a installed stable rom?

Just don't want to have to setup the phone again......

Mi 11 (venus)

Thank you for your help 👍
[Xiaomi Mi 11] hewlett2008:
No, you have to format data first...
[Xiaomi Mi 11] koloure2211:
Thank you.
[Android Apps and Games] AngelofMe:
View attachment 5323493

Game: Cargo-Bot

Original Version: App Store

Android Version: XDA
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Ather:
Hello All, many of you just keep asking how to do that and this, you do not use search, so im making this Guide which will help you

Things You Should Know:

Things Which Will not work after Upgrading to WM5, WM 6 or WM 6.1 :

Htc Himalaya Backpack (read below)

STK will Not function

There is no SDHC Drivers for any Version of ROMS for HTC Himalaya Yet

To Have 30.53 MB of storage Go here

Upgrading:

Windows XP :

Requirements :

Windows XP :p

Microsoft ActiveSync 4.5

Minimum of 256 MB of RAM

and some patience

Windows Vista 32-Bit :

Requirements :

Any Version of Windows Vista 32-Bit

Windows Mobile Device Center (Latest Version)

and a little computer knowledge

Before starting: Your device needs to be connected to the PC, and in BOOTLOADER mode.

If MODS find this Helpful, Please Sticky This :)

muckelmaus Wrote :
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] muckelmaus:
Backpack problem

Things Which Will not work after Upgrading to WM5, WM 6 or WM 6.1 :

* Htc Himalaya Backpack

As I tested some ROMs with my himas. Only the CF-slot will not work, 'till someone will write a working driver for it.

There are no probs to use the backpack battery and the vga-video funktion, so far. Two out of three, thats not bad, I think.
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Ather:
thanks for the info, i havent tested it my self thats why i didnt knew, edited the First post with this info :)
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Tippex:
Im a noob

Hi I am a noob and followed this guide but it did nothing...

Basically I have a 02 XDA II - it is locked and I want to upgrade it to windows 6/6.1 - I have been reading through the forum for a couple of hours now covering the wiki for himalays and other things.

I followed the steps on this - but nothing has been upgraded. So I guess this isn't how to upgrade to wm6?

So frustrating cos I can't seem to find the instructions on how to do it.

I believe its a rom i need right?> how do i put it on?

Should I unlock the xda first? (havent worked that out yet) or upgrade to wm6 and then it will be unlocked anyway?

Please please help I have been reading loads and trying to not ask obvious thigns.
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Ather:
i donot know if its SIM locked or not...try givinf xda2unlock a try

second, to upgrade you need a ROM, there are MANY roms in this Himalaya WM6 Forum...many of them have detailed instructions :)

it wont be any harm if you upgrade first...try giving it a shot and tell me

Ather
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Tippex:
I have also performed 'Unlock Wiz/Himalaya' but all I get is 'The phone seems unlocked already' - but it is not unlocked - any advice with this also?
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Ather:
try to upgrade the rom simply, if u get stuck, we all are here :D
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Tippex:
I am struggling through trying to work out how to unlock my sim and then flash WM6 onto my 02 XDA ii which therefore is a himalya - says PH10b in model no.

Anyway Im following one of the guides (http://wiki.xda-developers.com/index...0for newbies) and it says I have to establish whether it is a G3 or G4 or else Ill brick it and probably throw myself out of my window.

So I performed a soft reset and got the following information in red letters when I do it.

R 1.10.00

G 1337. 18

1.60.00WWE

I just don't know if it is a G3 or G4 and can't afford to brick this phone - so please could someone help me so I know which intructions to follow?

I will send best reply a stick of rock from Blackpool (famous for rock - its like sugary concerete).
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Tippex:
Sorry to be unclear - it is sim locked - it has horrible 02 logos all over it.

Bastards.

Anyway it is sim locked and wm 2003 i think.

Im not clear about how to install a rom - i did update the drivers putting it in boot and then updating driver from what i downloaded - which I think was to resolve and issue with vista/xp as i am using vista.

Right now im trying to work out G3/G4 because i found what seemed to be a good instrucitonal post
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Ather:
lol, the xda2 doesent has g3 or G4 :p ... so flash away
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Tippex:
So how do i unlock it and then install WM6?

Is there a step by step guide?
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Tippex:
It is sim locked and i want to unlock it and install wm6
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] jadephyre:
the Branding has nothing to do with the Simlock, my Himalaya is from O2 too, and all it had was Branding, no simlock.

I'm currently using E-Plus as my Provider, and i did not have to circumvent any simlock before flashing WM6.1 onto the Device.

Also, if it DID have a Simlock, it has probably worn off by now, since the Device is already older than 2 years...
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Tippex:
I have managed to unlock the sim now thanks to the wonderful people here but still have no clue how to install wm6?
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Ather:
congrats :) , just download any ROM and enjoy flashing it
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Tippex:
do i just download a wm6 file and put it onto my pda and then execute it? double click it? is it that simple?
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Tippex:
Can u spefically tell me how to implement a rom?

i assume i download it but then what?

I am thinking I'll just brick it - then spend months on here asking for help... Id rather just ask beforehand and find out how to do it.
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] jadephyre:
it's exactly like ather said, you downloaded the ROM, now you can flash it to your XDA.

Just do it like it says in the Readme and you should have no Problems whatsoever :)
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] bobsys:
Strange

I had an old Qtek 2020 and flashed it successfully to WM6.1 No problems exept...... the phne does not conect to the correct provider. The SIM is for the Belgian BASE provider whereas it connects always to ORANGE. When I put the SIM in my new Diamond or in my very old Nokia phne it connects to BASE as intended. I reflashed to the original Qtek WM 2003 SE and same thing. Reflashed again to WM6.1 ans still it only wants to connect to ORANGE ??? What am I overlooking?

BTW if I donload the list of providers there isno BASE provider. If I download the list on my Diamond it appears whithout any problem.
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Ather:
it could be because of the Network Manager has old settings, try setting it up manually
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] bobsys:
Well, I downloaded Nertwork Wizzard and ran it. That configured my GPRS data connection automatically for BASE. So far so good, but ..... when I use the PHONE.... it still connects to ORANGE for voice. At least now the data connection goes to BASE. Really myisterious to me. I really wonder what algorithme a phone follows to select the GSM network to use.
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] Ather:
hmm, try selecting the Phone Network Manually, and see if that helps
[MDA II, XDA II, 2060 Windows Mobile 6 Upgrading] kinderenh:
There is nothing on the phone that directs you to a network, all data for network selection is on the SIM. This could just be a translation issue; your phone receives an operator id and translates it to an operator name. The translation table may reside on your phone but can also reside on your SIM. Maybe BASE is not in your Windows ROM, although I rather expect it to be in your Radio ROM. You might want to consider upgrading the radio ROM. It is recommended to use version 1.17 for the Hima.

Otherwise, if you live near the border, it might be that your Hima tries to roam on a Orange cell that is stronger than a BASE cell. You can recognize this by the triangle that appears next to the connection icon. Data traffic is always routed to a APN, also when roaming. In that case, you could roam on Orange but still use GPRS on the BASE APN.

Try selecting the network manually and see if BASE pops up, if not, it is only a translation error of the network name.