So i saw a new pixel experience rom was out and it asked me to update so i said yes, restarted and now the screen does not respond to touch (was fine before obv)
is there any way to fix this as i cant navigate round recovery screen or anything, i dont have access to a PC either ffs
ZEbbEDY said:
So i saw a new pixel experience rom was out and it asked me to update so i said yes, restarted and now the screen does not respond to touch (was fine before obv)
is there any way to fix this as i cant navigate round recovery screen or anything, i dont have access to a PC either ffs
Click to expand...
Click to collapse
You need a PC and you need adb/fastboot.
thanks for the reply, strange and a PITA this just happened, i recently replaced my cracked screen though it worked on he older rom do you think its related?
what adb commands do i need to do when i can get access to a PC?
ZEbbEDY said:
thanks for the reply, strange and a PITA this just happened, i recently replaced my cracked screen though it worked on he older rom do you think its related?
Click to expand...
Click to collapse
Probably. There are at least 3 different kinds of display panel for vince - td4310 fhdplus e7 (fine for all custom ROMs and recoveries); td4310 ebbg (problematic for custom ROMs and recoveries); Novitek nt36672 (problematic for custom ROMs and recoveries). If you changed your panel from the first one to one of the other two, then there will be problems.
ZEbbEDY said:
what adb commands do i need to do when i can get access to a PC?
Click to expand...
Click to collapse
Either flash a MIUI fastboot ROM, or flash a recovery that supports your display panel, and then use it to flash a ROM that supports your display panel.
How do you know whether a recovery supports your display panel? First try to hotboot it - "fastboot boot recovery.img" and then test the touchscreen when it boots. If the touchscreen works, then reboot to bootloader and flash that recovery ;
Code:
fastboot flash recovery recovery.img
fastboot boot recovery.img
After that, you have a working custom recovery to do whatever.
Related
So, I've stupidly let my son try and flash a custom rom on his generic chinese tablet (Cambridge Sciences StarPAD 9 SE) and he found a few very similar spec tablet roms on the internet which said they require TWRP to be installed before flashing. So he's installed that, rebooted into recovery but the TWRP doesn't fit the screen in terms of resolution size. Now, that's not the main problem. The main problem is that the touch screen doesn't work at all within TWRP so I can't select any of the options. Whenever I power off the device and power it back up, it reboots to TWRP and doesn't boot to the main ROM. He said that it did originally reboot to the ROM whenever he first installed the TWRP because he said that it was the only way of getting to the recovery. So I thought that I could just use ADB and just force a reboot from there but off course, there is no ADB device driver to be found on the internet.. well not that I can find anyway.
I'll attach a photo for you guys and hopefully someone can help me with this as I've spent the best part of 2 days trying to figure out a fix but am now stuck.
I'm now able to access the device by adb however I don't know what to do from there.
Any help?
Does anyone have any firmware for this device? I can't find anything on the internet at all. If I could get a firmware img then the device will be fixed.
The build number from the firmware is: fiber_evb-eng 4.1.1 master 20130530
the command is "adb reboot" AFAIK
Did he take a nandroid backup before flashing? It looks like a version of twrp that is not compatible with the tablet was installed. Not every device supports touch screen recovery mode. Can you use the volume rocker to navigate?
I can almost guarantee you won't find the firmware for a Chinese tablet. I've just been trying to help someone in a similar situation but the best we could manage was a ROM that had lots of glitches.
Edit how did he flash TWRP if it was incorrectly flashed ie: fastboot flash boot recovery.img instead of fastboot flash recovery recovery.img then that may produce a device that would boot straight into TWRP. I've heard of that happening on a nexus 7
Sent from my C5303 using xda app-developers app
Go here for a updated TWRP thread!
Hey guys I have twrp here however I need help from the community.
The Twrp i have compiled, i have not tested everything yet, so please do not try any function yet, If you want to test out functionality, I found that reflashing stock system.img, boot.img, and recovery.img will probably reverse some damages, however I dont want anyone to mess their watch up (unless you are really brave) also guys flashing this twrp renders android wear useless so please do not flash it, this is going to be a tethered recovery for now. Only fastboot boot this thing anyways, with this itll help advance custom roms.
I have compiled the latest kernel, and I want to see if there is differences in the boot.img's that i have, and the ones that everyone else is running.
The kernel was giving me loads of build errors, but recently i had it built but I cant get it to boot android wear. My theory is that the boot.img i have, has .67, and i compiled .87, and there is something weird there. Unless my fixes broke the kernel, I have no idea but this will hopefully shine light on my issue. I did try .67 multiple times but untar'ing it gives errors and building it doesnt boot it, .87 doesnt have tar issues so IDK
Thanks /u/hamagc! Hopefully ill have something happen within a week or so!
Make sure you have adb & fastboot: This installer is for windows, and it installed adb, fastboot, and drivers with a few key presses
Download twrp here: and place it in a folder of your choice.
force the watch to power down by holding the button or power down in settings, when the screen goes black, repress and hold the button and swipe the screen from the upper left down to the lower right and that should bring up the ASUS logo with CSC Fastboot Mode! on the screen
Plug your watch in your computer and wait a few seconds then type in the CMD fastboot boot recovery.img and you should have a recovery to make backups or to flash supersu if needed
links:
System.img:
https://www.dropbox.com/s/pq03vrapclz3684/system.img?dl=0
Boot.img:
https://www.dropbox.com/s/p16n60s0s7wdbhh/boot.img?dl=0
good luck!!
hamagc said:
so attempting this for you, i get to twrp and push the fastboot dd if=/dev/block/mmcblk0p28 of=/sdcard/system.img command and i am left with a <waiting for device>.
scratch that, put commands into adb instead of fastboot and it's working. will have something for you shortly!
Click to expand...
Click to collapse
I forgot one step, with twrp on the watch, type in
adb shell
and then try the dd commands
T10NAZ said:
I forgot one step, with twrp on the watch, type in
adb shell
and then try the dd commands
Click to expand...
Click to collapse
yep, exactly what i had to do lol.
many thanks to you two
T10NAZ said:
I forgot one step, with twrp on the watch, type in
adb shell
and then try the dd commands
Click to expand...
Click to collapse
Fastboot booted the recovery and it boots into twrp just fine nice work!
EDIT: just took a full system and data backup and rooted the device with supersu and all is working fine
noahvt said:
Fastboot booted the recovery and it boots into twrp just fine nice work!
EDIT: just took a full system and data backup and rooted the device with supersu and all is working fine
Click to expand...
Click to collapse
Im really excited to hear that this is all working a-ok!!
noahvt said:
Fastboot booted the recovery and it boots into twrp just fine nice work!
EDIT: just took a full system and data backup and rooted the device with supersu and all is working fine
Click to expand...
Click to collapse
I thought if you rooted you get screwed for any and all future OTA updates? I swear I've heard that for multiple Android Wear watches.
parkerlreed said:
I thought if you rooted you get screwed for any and all future OTA updates? I swear I've heard that for multiple Android Wear watches.
Click to expand...
Click to collapse
I took a full twrp backup before root so I doubt that I won't get any available updates when I restore that backup
parkerlreed said:
I thought if you rooted you get screwed for any and all future OTA updates? I swear I've heard that for multiple Android Wear watches.
Click to expand...
Click to collapse
yes, that is my understanding, but if you make backups of everything before you root, and reflash it when an ota drops, you should be alright. However if I can get everything in working order, we can keep up with ota's in flashable rom form.
we now have access to clean system and boot images too if twrp decides not to restore your backups for some reason
Sweet!
Holy crap guys, I have a source built kernel booted!
Im adding some more features and seeing how stable it runs, so far i hit 1 random reboot, but it looks like its holding strong
Hi.
I have a problem with my Oneplus X smartphone.
I can't find a similar problem anywhere on the forum.
I've used the MSMdownloadtool 2.0 to recover from a brick. Can go into fastboot and oxygen os recovery but no matter what firmware I try to flash the phone won't boot into anything.
After the oneplus logo it just goes to a black screen and the notification led turns on.
When it is connected to a PC it shows up a 4 separate removable devices.
The bootloader is locked. I can't unlock it because I can't access developer settings because I'm not able to boot into anything.
Does anyone know how to fix this?
Thank you.
s3r3tin said:
Hi.
I have a problem with my Oneplus X smartphone.
I can't find a similar problem anywhere on the forum.
I've used the MSMdownloadtool 2.0 to recover from a brick. Can go into fastboot and oxygen os recovery but no matter what firmware I try to flash the phone won't boot into anything.
After the oneplus logo it just goes to a black screen and the notification led turns on.
When it is connected to a PC it shows up a 4 separate removable devices.
The bootloader is locked. I can't unlock it because I can't access developer settings because I'm not able to boot into anything.
Does anyone know how to fix this?
Thank you.
Click to expand...
Click to collapse
If you have recovery side load may help.or try full unbrick method rather than mini.
Fap4k said:
If you have recovery side load may help.or try full unbrick method rather than mini.
Click to expand...
Click to collapse
i did try that. didn't help either.
I used this guide and worked for me.....
http://forum.xda-developers.com/oneplus-x/general/guide-mega-unbrick-guide-hard-bricked-t3272108
i did too... didn't work. the Oneplus tech team tried the same thing. Didn't work.
s3r3tin said:
i did too... didn't work. the Oneplus tech team tried the same thing. Didn't work.
Click to expand...
Click to collapse
Same problem here. My device is now in the RMA process and I'm still waiting for their answer if they will repair it on warranty.
They told me that I have voided the warranty because the phone is bricked.
hello, here the same problem.... tried a few TWRP recovery versions but can't access the internal Storage. After the try to flash the phone with the MSMdownloadtool 2.0 (original OP Recovery Flash-Tool) the Oneplus X even boot anymore. No idea what happens with the newest Generation OPX
Date of Manufacture was November 2016?! Perhaps, the problem is the newer OOS 3.xxx. With OOS2.xxx i had no problems to Flash CM13 to a few OPX
Oneplus_X_Flasher said:
hello, here the same problem.... tried a few TWRP recovery versions but can't access the internal Storage. After the try to flash the phone with the MSMdownloadtool 2.0 (original OP Recovery Flash-Tool) the Oneplus X even boot anymore. No idea what happens with the newest Generation OPX
Date of Manufacture was November 2016?! Perhaps, the problem is the newer OOS 3.xxx. With OOS2.xxx i had no problems to Flash CM13 to a few OPX
Click to expand...
Click to collapse
Sorry but with your pseudo, it's a kind of funny
"tried a few TWRP recovery versions but can't access the internal Storage. " what do you mean by that?
Explain what happen at start. OS version, BL state....
Kéno40 said:
Sorry but with your pseudo, it's a kind of funny
"tried a few TWRP recovery versions but can't access the internal Storage. " what do you mean by that?
Explain what happen at start. OS version, BL state....
Click to expand...
Click to collapse
my normal "pseudo" was not available, so i take this funny one XD
Bootloader unlocked, OS --> OOS 3.x. Smartphone had boot into OS.
Recovery cant access internal Storage (Stock Recovery & TWRP)
After the stupid idea using the Oneplus original recovery tool the Smartphone cant boot anymore into the OS.
Now the Bootloader ist locked, cant open him anymore. Stock Recovery & TWRP cant access internal Storage.
OOS 2.x doesn't Boot. Android boot animation doesn't show.
So the main problem was, i want to flash CM13 but cant access the internal Storage (unable to mount data, system etc) wipe, formating, erasing was also not possible. even Fastboot had no access.
After using the "mega unbrick Quide" from Oneplus with the MSNdownload tool @ Qualcomm back door the Smartphone is "bricked"....Fastboot, recovery etc all good, but can't boot the OS (OOS2.x) Bootloader is locked, internal Flash still locked :silly::crying:
Fastboot command are OK?
Whatt's the output of "fastboot devices" &
"fastboot oem device-info"
If you have the old OOS 2 recovery on it, fastboot reflash the OOS recovery then try OOS 2.2.3 full rom zip
Old stuff links here : http://forum.xda-developers.com/showpost.php?p=69170103&postcount=45
If still a problem, and you think the BL is already on the new version, try to fastboot reflash TWRP 3.0.2.1 official and then OOS 3.1.4 with it.
To transfer it, use the microSD card.
After Flashing over the Qualcomm back door, the bootloader ist locked. so fastboot says of course, Bootloader ist locked (Fastboot oem device-info) that means, i cant flash anything by sideload or fastboot codes... and when i try it over the Recovery Boot, recovery is not able to mount /Data /System /cache and so on. so i am not able to flash anything XD Neither cm nor stock oxygen in the version OOS2.x / OOS3.x. I try the old bootloader, the new Bootloader and the TWRP 2.8.x, TWRP 3.0.2.0, TWRP 3.0.2.1, TWRP 3.0.2.2 and the Stock Recovery from CM and OnePlus
I've never had this behavior of a mobile phone The Technical Support Team of ONEPLUS even cant help. very strange. Here someone with the same strange problem... http://forum.xda-developers.com/oneplus-x/help/twrp-access-internal-storage-t3513748
The only way to flash anything to the phone is over the Qaulcomm BackDoor. With the new Bootloader & Kernel of OOS3 the boot animation of OOS3 starts and the phone gets hot. but not boot into the OS. And i can't find anywhere the system.img of OOS3. in the Recovery Tool from OnePlus ist the system.img from OOS2 (I have exchanged single items from directory xxx.img)
sorry it is very difficult to explain this complex problem in english XD
IT from Oneplus tried to flash OnePlus_15_A.11_160420 but it still didn't work. Bootlader is locked so TWRP is not an option or is flashing anything trough fastboot. Only Qualcomm Msmdownload tool or qfil. I've tried the old bootlader, new boolader, h2os, ColorOS, Miui ... but the phone just won't boot into any OS. it stays on a black screen with a white led on and that is it.
if the Qualcomm driver mount you a few partition under Windows, you can flash the internal Storage with an clone of a running OPX. I found an guide how to write direct into the Flash with a PC
Unfortunately I'm from a small town in Croatia. Here I think no one even knows what a Oneplus mobile phone is not to mention owning one... so I am out of luck.
UPDATE: I will get my repaired OPX (or a new one, don't know yet) back tomorrow. They repaired/exchanged it, I had the same problem, black screen and white led. Perhaps my good was to remove the "tampered"-flag from fastboot oem device-info
When I told them I use linux and don't have access to a windows PC they didn't even try the remote-session and told me to send it to them right away.
s3r3tin said:
Unfortunately I'm from a small town in Croatia. Here I think no one even knows what a Oneplus mobile phone is not to mention owning one... so I am out of luck.
Click to expand...
Click to collapse
i have access to two working Oneplus X but the dead phone did not show the removable drive under Windows so i thing we have to send the dead phone back to OP and hope the can fix oder replace it
You should remove the "tampered"-flag before you send it to them. It's simple:
Use the MSMdownloadtool 2.0 to flash twrp (just swap the recovery.img in the MSM-folder). Then you can start the recovery, but I could not do any swipes (screen didn't react), so I couldn't get past the first screen asking if I wanted to mount system r/o. But adb shell was working.
This I used to use the guide at http://forum.xda-developers.com/oneplus-x/help/guide-unlock-bootloader-oneplus-x-using-t3362640
Use adb push/pull to get the file to your pc.
After dd-ing the modified partition back, I used MSMdownloadtool 2.0 to flash the latest original oneplusX-recovery you can download at their site.
I told the support I never rooted the device and was acting like a complete noob, said I had no idea what android version I was on and it seems they accepted it.
It's definitely a hardware problem. Touch isn't working either. The IT guy checked the oem info himself after the flash and after boot was uncussesful and asked me if the phone was rooted. My warranty is now voided. I have decided to sell my oneplus x for parts.
Its seems like EU community released two version of twrp. So people how are facing white screen problem probably have the 1st version (recovery-TWRP-3.4.0B). Go to google and search "recovery-TWRP-3.4.1B-0322-REDMI_K30-CN-wzsx150" . Download and flash it. Hope it will fix it and can go normally to recovery using power& volume + button.
NB. Unfortunately i cant give the recovery link due to forum rules.
Its working fine ,guys just follow the steps.
Poco X2 official twrp When will it come?
luffy1212 said:
Its seems like EU community released two version of twrp. So people how are facing white screen problem probably have the 1st version (recovery-TWRP-3.4.0B). Go to google and search "recovery-TWRP-3.4.1B-0322-REDMI_K30-CN-wzsx150" . Download and flash it. Hope it will fix it and can go normally to recovery using power& volume + button.
NB. Unfortunately i cant give the recovery link due to forum rules.
Click to expand...
Click to collapse
Wow , thank you soo much bro
Hi, does this special edition TWRP support setting a password or trigger the same password/pattern set in MIUI, inorder to enter TWRP and flash something or access the file manager? Or in another word, does it support the encryption (is it FBE?) set in MIUI?
I installed the TWRP recovery and flashed a custom ROM using it (HAVOC OS). Now, I'm trying to get into the custom recovery but whenever I do that, it gives me a prompt for a password and says that the data is encrypted. How do I fix this? I can't find any solution to this.
LiLbomberxo said:
I installed the TWRP recovery and flashed a custom ROM using it (HAVOC OS). Now, I'm trying to get into the custom recovery but whenever I do that, it gives me a prompt for a password and says that the data is encrypted. How do I fix this? I can't find any solution to this.
Click to expand...
Click to collapse
boot to your stock system...or usuall
y the password for user[0] is your pin/password that you used to unlock your screen with
before flashing or unlocking your bootloader..the option is to just remove it before you flash..if not just enter that password..or you'll have format the whole thing
it started with calyxOS then i tried Paranoid Andriod and now i am trying RiceDriod.
Specifically it happens trying to go into recovery mode to install updates via adb sideloading but it just takes me to the google screen then the "your devices bootloader is unlocked" warning.
I just flashed stock using andriod flash tools and it worked fine. not sure why it wont work for the others.
catcatjpg said:
it started with calyxOS then i tried Paranoid Andriod and now i am trying RiceDriod.
Specifically it happens trying to go into recovery mode to install updates via adb sideloading but it just takes me to the google screen then the "your devices bootloader is unlocked" warning.
I just flashed stock using andriod flash tools and it worked fine. not sure why it wont work for the others.
Click to expand...
Click to collapse
You have to flash a custom recovery so that you can flash custom ROMs.
Lineage OS has a up to date collection for device specific recoveries. However, you have to check the compatibility of them with the ROM you are intended to flash.
You should read the OP of that ROM more carefully regarding the compatibility issue.
aimsjahan said:
You have to flash a custom recovery so that you can flash custom ROMs.
Lineage OS has a up to date collection for device specific recoveries. However, you have to check the compatibility of them with the ROM you are intended to flash.
You should read the OP of that ROM more carefully regarding the compatibility issue.
Click to expand...
Click to collapse
I do flash the custom recovery so I can flash the ROM. I never had an issue before but now I do even though I have done everything correctly.
How do I clear cashe partition and dalvik cashe? The rest of the steps I have done but have not worked unfortunately. even with the different roms.
Do you have a visual of this? Pixel 6 does not have a physical home button when powered off haha. It would also help just for better understanding what to do
nothings working so far guess ill stick with graphene until i get a new phone or a solution pops up
catcatjpg said:
Do you have a visual of this? Pixel 6 does not have a physical home button when powered off haha. It would also help just for better understanding what to do
Click to expand...
Click to collapse
To manually boot recovery on a custom rom just hold power button down , keep holding it down and once your screen goes black hold volume down till you are in bootloader/fastboot mode, then use volume to select recovery and hit power. That should get you in recovery on custom roms. Or you can plug in to a PC with adb and enable USB debugging and dev options on device, disable screen lock and type: sudo adb devices (for Linux ) and when the box pops up on your phone check mark it really quick. Now your device can have commands sent to it. If on a custom rom from cli type: sudo adb reboot recovery or sudo adb reboot bootloader then use volume keys to go to recovery and power to select it.
The best way to get out of a bootloop is hold power and volume down until you are in bootloader/aka fastboot mode then execute the ./flash-all.sh script that's in factory image and let it flash and wipe your device. You can always sideload a rom again but the factory image script will get everything to normal. There are tons of videos on YouTube about flashing device's. Everything changed a few years ago when Google started making android A/B partition devices but if you check out YouTube just do a quick search for whatever it is and more than likely you'll find what you're looking for there. Lots of pixel 6 videos!!!
Please explain your "exact " installation technique step by step. The more details the better the answers you'll get. What rom are you installing and exact steps you are doing to get in a boot loop.. While there are some highly intelligent people here nobody can read minds. Every detail helps to get a solution that works. Must be specific.. For me I rarely have issues but i don't flash nearly as often as I used to but when I have had a loop I hold power and volume down then from bootloader screen plug up to PC and I flash factory image using the flash-all.sh script that comes in factory image. Check out YouTube for visuals. Lots of good videos there.
This will hopefully provide more information on my situation
Currently I am trying to install RiceDroid for the pixel 6.
How I am in stalling it is I extract the images from the payload bin using a guide. Get the vendor boot image. Flash it with 'fastboot flash vendor_boot 'path/to/vendor_boot.img' then I try to boot into recovery which doesn't work it loads into the the warning screen then to the Google boot up screen but I never get to the Andriod 'no command' screen I only get taken back to the warning screen then back to the boot screen again untill I manually boot into bootloader again (power button and volume down) and flash my stock firmware.
Other Roms are not working for me either and it started happening after I tried to flash calyxOS and that failed. Now I can't even flash lineageOS or Evolution X rom only web flashing with GrapheneOS and Android Flash Tool can successfully flash my device.
im not sure what i did but things are working again