Hi can anyone help as I cant find a guide anywhere. I want to remove Remix OS from my Pixel C. Lately ive had issues with start up times and feel that due to lack of updates the whole thing is a little bit dated. I cant seem to find a guide anywhere and dont want to brick the tablet. Would really appriciate any help and direction
Just flash a factory image from Google via fastboot
Related
Hi
got the SMT 320 (8.4) and forgot my lockscreen password as I was in such a hurry...
Wifi is not on. Have tried to switch it on via adb but no success. Comes up as "unauthorised"...
Device is unlocked rooted and runs cyanogenmod rom 10 (I think)
Can anyone tell me what to do? Have looked around for hours but cannot find right advice
Can I just go to TWRP and do a factory reset?
I am a real stupid newbee so would really appreciate steps and links if there are...
would be extremely grateful!
found this excellent advice https://www.youtube.com/watch?v=BJZMxPxUXOo
but my device appears as "unauthorised" ...
Hey guys,
sorry if my english isn't right but I am so tired so now and so frustrated that I don't know what I could do.
The story is simple: I have a android head unit, running allwinner t3 (aka R40) with stock rom and stock recovery.
So far, there isn't any custom recovery available (I would like to create/compile CWM but CWM-Builder have some 502 Bad Gateways...) and the only way to root on 4.4.2 is with 360Root (On 6.0.1 for the newer Models only with Kingroot).
So far not bad but it takes a lot of patience sometimes and sometimes you can try over 1 week every day many hours and it still don't work!
So where do I need help? I want to add Root/SuperSU/... manually but I have many limitation.
First one is that I can only modify the system.img without any chmod and else (Maybe because I am using windows? Maybe because the Firmware has to be flashed while the Head Unit is powered off aka "Dead flash")
Secondly, ADB is not working, to be honest, the head unit act only as a receiver! It accepts any devices like Keyboard, UMTS/WCDMA Stick, USB Stick, ... but MTP fom HeadUnit or ADB, ... don't work. The only way for ADB is ADB over Wifi but I don't know whether it's good or bad. I saw that the USB is plugged into a slot which seems to be bend out, maybe they plugged it in wrong? I don't know how I can test that but I heard that connecting two devices with wrong polarity will break at least one of them!
Thirdly is, that I can't notice a difference between a rooted stock rom and a unrooted stock rom.
According to WinMerge, the rooted ROM have two new files (/etc/install-recovery.sh and /bin/su) but that's it!
If I transfer those files to my custom ROM with the same rooting app, it wont recognize them! I can try and try until I die.
And last, maybe worst, I can't just update something over. Every change outside the Android OS is mainly done by flashing the whole firmware! They changed that policy a little bit after Android 6.0.1 but this Android have the worst stability, worst GPS Modules and completely bricked Bluetooth! Also the stock recovery on 4.4.2 is useless, touch isn't working and the touch-buttons are also not working. I also tried to use a usb keyboard but also useless. Only the 6.0.1 stock recovery recognizes the touch screen and the touch-buttons but as I said, the Android 6 is terribly made...
I know what it sound like a noob and I didn't provided much information but I want to know whether someone can help me or want to help me... maybe someone say that I have to provide information xyz so yeah, feel free to ask
Best regards
Pascal
At what point did you install the ADB device drivers (kinda important) for your device, so that when you plugged it into anything, the thing could register you were plugging in the HeadUnit......
Hi guys n Gals How you all doing? Staying safe i hope!! Im posting this incase it is of any use to anyone who happens to stumble upon an old tablet as i did, But is absolutely bamboozled with what to do next.
Well then i had been looking for help on this issue with regard to Kindle Jem and done my fair share of reading before signing up here.
I am right out of the wrapper and wet behind the ears with Kindles and the like(1st time rooting anything at all) however i managed to install TWRP 2.8.6.0 on su rooted kindle using the bin4ry method.
I followed step by step a tutorial on Youtube named " KindleFireHD89 to pure android"
1. At first i was getting read/load errors:
when attempting to flash cm10.1 cm11/12 through adb sideload i was getting the error message "unable to read cm 11/12" or "unable to load cm11/12" each time i try to flash the rom.
So I done some research on XDA and found a thread to do with the \LARGEADDRESS issue , so downloaded the program to use more than 2GB ram for the flash process, all to no avail. (THIS WAS ABSOLUTELY NO USE AT ALL)
I soon figured i was copying and pasting the commands for flash/fastboot wrong ( i was forgetting to add .img to the name of the image files i was pasting into the command prompt to flash lol)
2. I done a bit of reading around and saw that most , if not all the files were severely obsolete (like the Jem) so i searched around and first upgraded to TWRP 3.0.0.2 from 2.8.6.0 which i feel made a big difference if not just for a smoother gui alone.
3. As my determination and curiosity got the better of me i began replacing the roms also , flashing newer ones each time in this order:
cm 10.1 (success)
cm 11(success)
cm 12.1 (success)
And finally onto Lineage OS 14.1 along with GApps 7.1 Pico where i remain , however i am unable to fix the bluetooth issue as i dont know the commands/ paths or method to alter the LTE file replacement. (any help with this would be great guys or girls (i know Ladye made a fix i think) i just dont know how to go about editing these files.
I got into the menu brand new , though weirdly it wasnt by the volume up button, it was by turning on/off about 5 times and then holding the POWER button in and finally the TWRP Recovery screen would popup.
### edited### i know this is an old kiindle hence why there is no replies .....
####23rd May 2020 EDITED YET AGAIN ##### So i wondered whether there was a recent newish kinda Rom for the JEM after managing to flash (with great difficulty and beginners syndrome) custom rom in TWRP 3.0.0.2.
As i said earlier this was a kindle that was found and when i got it in out the rain and dried off with the hairdrier treatment , was amazed it still worked. So i figured it was a tough mofo and deserved to live outwith the bin since he made it this far.
Anyway when i checked it out the firehd 8.9 was blacklisted ((((Which i am assuming will mean i at least dont need to worry about disabling OTA updates??????))))
So bottom line and after all the fuss above trying to root etc i got 14.1 lineage os without the bluetooth but ill figure that out soon.
For anyone out there this post may help if you can be bothered to read through it haha.
###Last but not least I would like to thank all the guys n gals who make these mods possible and xda themselves for not binning these old posts for noobs like myself . Respect people . thanks again man ###
Sop i used Mega unbrick on my 5T, and i can not , for the life of me, get anything installed on in other then the 7.1.1 androidf that mega installed by defauly. I've rooted, twrp, tried sideloading, . Kid of at a lost after trying multiple things for hours today. any step by step, or suggestioons would be appreciated. Sorry for the spelling. tired and frustrated. And it doesnt see any OTAs either. I just dont get it.
Hello everyone. I am stuck in a bit of a draining situation. and I really hope that some of you, may be able to help.
I have 3 kids with each their phone, all of them have been registered to Googles Family Link service. Recently the account that managed them all got suspended for being hijacked and therefor it broke their terms, and now 4 accounts are locked. Google will not help me, to release the accounts the kids have, so they can use their phones again. So I tried following a guide on bypassing the log in prompt after a factory reset on this specific device. It happily activated the tap talk function, but when I try to open Google Assistant, nothing happens. I've tried looking it the settings of Tap Talk to find any clues, but to no avail.
I have searched for different variations of the same procedure on Youtube and Google and I can't seem to get further than described..
I then decided to try unlocking the bootloader or re-flashing the stock firmware, hoping to wipe the existing system completely. The re-flashing part, well. I found the Asus Zenfone Flash tool, but I am not too sure what to do. The guide seemed a bit confusing to me, so I tried the Bootloader, since I used to flash and root all my phones back when HTC was big. I have installed Quallcomms drivers, Asus-android_USB drivers, generic Android Usb drivers and restarted the pc to make sure that was done right.
The phone however is another problem. I haven't been able to enable usb-debugging thanks to Family Link preventing access to Dev-mode, before I did the Factory reset. I can read the phone's name on the ADB update option, when I boot it to stock recovery. But any commands, makes it hang with "waiting for any device", which, from what I understand, is a driver related issue. So I have updated the drivers as each guide has descibed.
My plan was to install the latest Lineage Rom, so I have the most recent files for that.
So now I ask you. I have downloaded Rom files, Gapps, 2 types of recovery img files, but for now, I am stuck and sad and I need a Yoda in this matter. The entire situation is probably solved with a simple click or command that I am not aware of.
If you need any further info I will do my best to help. My kindest and biggest thanks to anyone that provide some help.
Kind regards
Johnny