I have spent about 10 hours sitting here, with over 200 tab open trying to find a solution to my problems but I could not find one. My last option is to post here and hope someone can help me out.
I recently bought the tf701t which came with Android 4.2.2. Everything worked fine. A few days ago, I got pushed an update to android 4.3 but it was .1.7 not .1.18 (the newest apparently). With that update, my problems came. When I light up the device by pressing the power button, the lock screen was unresponsive. I pressed my pin numbers in but there was no response and it was as if the touchscreen was broken. However, the home and back button were all working fine. I had to randomly keep pressing until it finally started becoming responsive. When I got in, the quick management window (the one you get by swiping down), kept popping up the moment i press the screen. Because of this, I couldnt do anything. I couldn't even turn off the tablet as the power off option was unable to be pressed by me (When i did press, the window came up again).
After a while, i managed to get around this by again randomly pressing stuff. I got really frustrated and decided maybe if I install a custom rom, this problem might be fixed.
I read around a bit and found that the CROMix rom required firmware 1.18, which I did not have. Because of this, i decided to try install 1.18. First i used the asus unlock tool. Next I tried booting into recovery but here I met my problem. I have guides telling me to first boot using power button + volume down key. This worked. It then told me to choose the RCK option and press the volume up key. This however, did not work. When I selected the RCK option, the android figure appeared lying down with a red triangle and exclamation mark over it.
Unsure of what to do in this situation, i read one of the guides on this forum which said simply place the 1.18 zip file (yes i unziped the zip file from the file i downloaded), in the root folder then reboot and it would automatically update. This didnt happen.
I then tried using the adb thing but it said no devices were connected even when my tf701t was connected to the PC. I guessed that I needed to be in the recovery mode that I could not get into, before it would work.
I then read around and they said I had to first get Rom manager + the CMR recovery thing but Rom Manager said it needed root access. In order to get root access, I needed to get into the recovery mode yet again.
So now I am stuck. Whenever I try the RCK option, the error pops up and I can't get any further.
WIll someone please help me? I have no idea what to do anymore except throw the tablet out.
zhuang281 said:
I have spent about 10 hours sitting here, with over 200 tab open trying to find a solution to my problems but I could not find one. My last option is to post here and hope someone can help me out.
I recently bought the tf701t which came with Android 4.2.2. Everything worked fine. A few days ago, I got pushed an update to android 4.3 but it was .1.7 not .1.18 (the newest apparently). With that update, my problems came. When I light up the device by pressing the power button, the lock screen was unresponsive. I pressed my pin numbers in but there was no response and it was as if the touchscreen was broken. However, the home and back button were all working fine. I had to randomly keep pressing until it finally started becoming responsive. When I got in, the quick management window (the one you get by swiping down), kept popping up the moment i press the screen. Because of this, I couldnt do anything. I couldn't even turn off the tablet as the power off option was unable to be pressed by me (When i did press, the window came up again).
After a while, i managed to get around this by again randomly pressing stuff. I got really frustrated and decided maybe if I install a custom rom, this problem might be fixed.
I read around a bit and found that the CROMix rom required firmware 1.18, which I did not have. Because of this, i decided to try install 1.18. First i used the asus unlock tool. Next I tried booting into recovery but here I met my problem. I have guides telling me to first boot using power button + volume down key. This worked. It then told me to choose the RCK option and press the volume up key. This however, did not work. When I selected the RCK option, the android figure appeared lying down with a red triangle and exclamation mark over it.
Unsure of what to do in this situation, i read one of the guides on this forum which said simply place the 1.18 zip file (yes i unziped the zip file from the file i downloaded), in the root folder then reboot and it would automatically update. This didnt happen.
I then tried using the adb thing but it said no devices were connected even when my tf701t was connected to the PC. I guessed that I needed to be in the recovery mode that I could not get into, before it would work.
I then read around and they said I had to first get Rom manager + the CMR recovery thing but Rom Manager said it needed root access. In order to get root access, I needed to get into the recovery mode yet again.
So now I am stuck. Whenever I try the RCK option, the error pops up and I can't get any further.
WIll someone please help me? I have no idea what to do anymore except throw the tablet out.
Click to expand...
Click to collapse
Did you try to put the update on the external sd card? Not sure if that would make a difference but i remember i used to put it there...
You could also flash a custom recovery and flash the update that way. You can find more info in this thread:
http://forum.xda-developers.com/showthread.php?t=2636093
You should safely be able to update your factory firmware first by putting it at /sdcard location.. Then just reboot. It automatic. I Thought there was also an update available in settings after that. Don't unlock til you are at 4.3.
To unlock with Asus unlock tool make sure Google 2 Step verification is disabled.
Then I used fastboot to flash CWM recovery from a computer. I think you flash with fastboot from the newly unlocked bootloader. Power + Vol DOWN.
After you have flash recovery then you can enter it. No scary man lying down.
YayYouFixedIt said:
You should safely be able to update your factory firmware first by putting it at /sdcard location.. Then just reboot. It automatic. I Thought there was also an update available in settings after that. Don't unlock til you are at 4.3.
Click to expand...
Click to collapse
I forgot to mention one thing at the start. I don't actually have on hand a external microSD card. Which I think might be why placing the zip file in the root of the internal storage did not work.
Should it work? Is there any way to get around it? I've been trying to use sideload with cwm (finally got cwm working), but it comes up with "failed to write data protocol fault no status"
EDIT: Through cwm, I chose "choose zip from /sdcard" then select the "0" file directory then i found my zip at the location. I selected it and confirmed install. However, it then comes up with "Error in data/media/0/(name of update here).zip status 6"
Thanks for the help so far but anyone have an idea about this?
Not sure. After googling I see this
http://forum.xda-developers.com/showthread.php?t=1535546
---------- Post added at 09:54 AM ---------- Previous post was at 09:45 AM ----------
You can put the zips anywhere when your recovery is installed.
Okay so I finally managed to get the custom rom installed and working. However, this did not fix my problem with the touchscreen. I think it is because it only changed the firmware but not the android version (still 4.3).
Is there any place I could find android 4.2.2 rom? This was the one the tablet was on before the update that screwed everything up. If I could downgrade to that version, it may work again.
Thanks
I gave up and just put on the android 4.3 ota from droidbasement. Now the tablet randomly restarts and is stick in reboot loop. It wont even allow me to boot into cwm recovery to delete the cache. But i accept that I now have a $600 piece of **** on my hands. Going to bed. Night.
Ya i dont like the whole void your warranty for "using it" idea. If it responds to fastboot you might be ok.
You should be able to download a 4.2.2 rom from Asus' website (.47 was the last build for 4.2.2). You can use fastboot to install it.
Alta1r said:
You should be able to download a 4.2.2 rom from Asus' website (.47 was the last build for 4.2.2). You can use fastboot to install it.
Click to expand...
Click to collapse
I tried that before but it stated "update aborted" immediately after i pressed confirm, in CWM.
But all that is in the past now. I am pretty sure that the tablet is hard bricked since it no longer even opens bootloader. I accidentally pressed the wipe data option and I read that irreversibly damages the tablet. When I hold pwr+vl down, nothing happens anymore, it keeps on its reboot loop.
Related
So I purchased a used G1 and I knew it has some software issues. I have no idea what version OS or anything is on this phone. Issue is it will not boot up into the OS. After researching (I am new to android) I have found what it can and what I cant get it to do. I can get into recovery mode no problem and after an ALT-L I see "Android System Recovery <2e>". The phone usually boots into this mode straight away, or I can hold home+power and it will enter the mode. Tried doing a "wipe data/factory reset" but nothing changes. If I reboot the phone and hold "back" I would expect it to enter Fastboot mode where I could do stuff. Instead I see the "rainbow screen" very briefly and then a message saying that if I want to restore factory setttings press send, otherwise hit any other key to cancel. No matter what I press nothing happens and I have to pull battery. I can only get into this mode every now and then. It seems pretty finicky about getting into it, and again no options when I do. Finally the camera+power to get into the bootloader does nothing. I can get the PC to see the phone when in recovery mode. It showed up as a mass storage device and i got that changed over to "Android Phone" by installing the SDK drivers.
Is there anything I can do on the recovery screen? That is the only thing that consistently works. I have tried a few update.zip files (various OTA updates I downloaded) but I either get a "No signature" error or it starts installing and then immediately get an "Installation aborted".
Any help to get this up and running would be appreciated. Hopefully its not just useless. For now an OEM 1.5 build is really all a i need. I can worry about updating/rooting later.
Download dream.nbh and format your sd card then place the dream onto ur sd card reboot holding home+cam button and let it do its magic that's how I fixed mine I'm sure if you go to the htc site you will find all the files u need just do a bit more research before trying this
Sent from my HTC Magic/Dream using XDA App
I mentioned in my original post that the camera+power button to enter bootloader mode does not do anything. I have already researched solutions, but it only seems I have access to the recovery mode screen. What can be done from there to assist with this issue (if anything)?
Download and flash the files from here http://developer.htc.com/adp.html (ota radio and system image) rename them update and flash them one at a time
Sent from my HTC Magic/Dream using XDA App
As for the no sig error just do some reasarch on adb shell and flash clockworkmod recovery from there its easy once u do some searching.....dw a couple of weeks ago I was you lol it'll pan out ok the people round here are really helpful
Sent from my HTC Magic/Dream using XDA App
Does this require adb? I have not been successful in making my pc get an adb connection. When in recovery mode the phones shows up on my pc and I got it to show up as android, but "adb devices" does not show anything listed. Everything referencing adb says it needs USB Debugging enabled, but I cant do that I cant get into the OS to enable. I dont seem to be able to enter fastboot mode either (see original post).
Download the radio and recovery image format sd card rename the ota radio update.zip boot into recovery and select apply update from sd card one you have that done delete the update.zip and then place the recovery image on sd card but rename update.zip and do the same....should work for ya
Sent from my HTC Magic/Dream using XDA App
When trying to update the radio files (tried all 3 versions on the download page) I get the "E: No signature (5 files)" error. Can I generate a valid signature for the files?
its worth a try lol if that dont work then i really dont know whats wrong lol
So far I have tried the following files:
The following pass verification and I get to the "Installing update..." but I then instantly get an "Installation Aborted". No other error message as to why:
signed-kila-CRC1-from-CRB43-FIX.7ca4a1d7.zip
signed-kila-DRC83-from-CRC1.c41b93c1.zip
signed-kila-ota-148830.de6a94ca.zip
signed-PLAT-RC33-from-RC30.zip
signed-RC30-from-RC29-fat.1582cace.zip
The following I get a "No Signature" error:
signed-dream_gfh-ota-147201.6d1386de.zip
ota-radio-2_22_19_26I.zip
ota-radio-1_22_12_29.zip
ota-radio-1_22_14_11.zip
I did a Wipe data and Cache before each update.zip attempt and this was using the "Android system recovery <2e>" screen.
Ideas? I will look and see if I can add a signature to the radio files.
dont spose u flashed the recovery with clockworkmod recovery 2.5.0.7
too short
I have not been successful flashing anything to the phone so far. All this was done via the "Android system recovery <2e>".
I signed the radio files myself, but they came out identical and same issues occurred. No idea what the "No signature" error is. Seems like a bunch of people get it on the forums, but no solutions. No idea why the good updates suddenly abort.
forum.xda-developers.com/showpost.php?p=4647751&postcount=1
Unfortunatly that seems to require fastboot, adp, or a rooted phone. I tried installing another SPL and I keep getting the "No Signature" error.
wow man your having a tough ass time lol ill keep researching for ya
i think your home button maybe stuck lol
far to short
You know thats not a bad idea. It does actually boot into recovery mode without holding the home button like you are meant to. Would holding home when powering on prevent the boot loader from starting if I hold the camera button?
on my g1 if i hold home power and cam buttons i get the bootloader/fastboot menu
So I ordered a new battery for it today too. The phone does not seem to work too long without being plugged in. Maybe that will help.
I also managed to capture some pictures of the screens I have, so maybe that will assist people with diagnosing the issue.
The first is the rainbow screen I get when holding back on a reboot. It flashes for 1 second or so and then displays the white screen with blue text. The last pic is the recovery menu I have access to.
It looks like this is a fully stock phone, no flashes. I am going to keep trying to get into that bootloader screen. Getting into the rainbow screen works once every 20 tries or so. Maybe the bootloader is similar. Hitting send on the white screen does nothing and requires a battery pull to reset phone.
how long can you stay in the coloured menu for ?????? also what happens if you stay there like what options do you get???
Hello! If you're reading this i hope you can help me, cause right now i have no idea what to do. First I'm going to tell my phone specs. I have a rooted, Moto X 2nd Edition XT1092, without any custom ROM installed, running Android Lollipop, with the option to upgrade to marshmallow and an unlocked bootloader. It uses the google launcher by default. I am pretty experienced with root as i have used rooted android phones for more than 4 years now (my first one was a Samsung Galaxy S2) and haven't had any problems until now. I had recently downloaded FaceNiff, one of the sniffing apps for android, and when i pressed start, it would automatically stop. I thought it was maybe a problem of the apps compatibility with my phone, but after researching for a long time, nothing came up so i decided to try another sniffing app. I moved on to DroidSniff, yet, I had the same problem, but this one wouldn't only stop, it would crash. I researched on this app too. Nothing. So I later downloaded one called DroidSheep, and when I started this one, I was lucky that an error was displayed, it was something about Position Independent Executables (PIE), it said "Only Position Independent Executables are supported" or something around those lines. So I decided to research PIE, and I found on the XDA Forums that you could fix this by changing the system/bin/linker file for a custom linker file, which a download link was provided for. I downloaded the file, changed it for the old linker file and tried the apps again. Apparently, I didn't have root access anymore! None of the root apps worked, I thought maybe I had to reboot my phone for my root to come back or for the custom linker to work. So i powered off my phone, turned it on, but instead of turning on, it would say the "Warning unlocked bootloader" thing, and then show a picture of and Android lying down with a caution sign, with the text "No Command" underneath. It's currently in this state, and the phone won't stop repeating this until it runs out of battery. The good thing is I can hold the power and volume down button to enter the fastboot menu, and i can then go into recovery. After this happened, I went to recovery and factory reset my phone, but it still didn't work, so I factory reset it again. It still charges, with a wall plug and with a computer. I think the computer recognises the phone, and I'm pretty sure I have USB Debugging enabled.
To sum this up, I changed the file system/bin/linker for a modified version of it and my phone won't boot up.
Custom linker file: http://forum.xda-developers.com/attachment.php?attachmentid=2821644&d=1403933203
Link to the website where it said you can change the linker files to fix the PIE problem: http://forum.xda-developers.com/goo...x-bypassing-pie-security-check-t2797731/page1
You are booting into recovery. I think when the android is laying down you hold power and press the volume up key. You will probably have to restore the backup of the file you changed (you did back it up right?).
If that doesn't work, you will most likely have to flash your system partition with the stock one and root again.
Red_81 said:
You are booting into recovery. I think when the android is laying down you hold power and press the volume up key. You will probably have to restore the backup of the file you changed (you did back it up right?).
If that doesn't work, you will most likely have to flash your system partition with the stock one and root again.
Click to expand...
Click to collapse
Ill try flashing the stock one, see if it works, thank you
First of all, I've looked around for answers, and I seem to find the same solution everywhere, which is OK. It just doesn't work for me.
Here's the drill. My Moto X was sitting in a drawer for a year or two. I took it out a while ago to update it and see how 5.1 worked on it. I put it back in the drawer as an emergency phone. Last weekend I took it out, to find that it's stuck in Fastboot. the up volume key scrolls, and down volume key does nothing (originally down scrolls, up chooses) and the power button reboots.
Long story short, I was able to get my computer to recognize my phone (tried for hours until I realized it was the cable, use the right cable and voila!) I unlocked the bootloader via Motorola, and after hours of trying was able to flash everything I thought was necessary (boot, recovery, motoboot, system, and so on). However, in every thread and video, the "fastboot reboot" command makes the phone reboot into the actual OS, whereas mine just keeps rebooting into fastboot, regardless of what I flash.
I don't notice anything off, so hence why I recur to everyone in here to give me some advice on what I could be doing wrong. I've downloaded stock roms so far. I get a partition error with .zip files so always have to flash the images individually.
Please let me know if I'm missing any details, and/or what other information I should provide.
Thank you!!
SantiagoEB24 said:
First of all, I've looked around for answers, and I seem to find the same solution everywhere, which is OK. It just doesn't work for me.
Here's the drill. My Moto X was sitting in a drawer for a year or two. I took it out a while ago to update it and see how 5.1 worked on it. I put it back in the drawer as an emergency phone. Last weekend I took it out, to find that it's stuck in Fastboot. the up volume key scrolls, and down volume key does nothing (originally down scrolls, up chooses) and the power button reboots.
Long story short, I was able to get my computer to recognize my phone (tried for hours until I realized it was the cable, use the right cable and voila!) I unlocked the bootloader via Motorola, and after hours of trying was able to flash everything I thought was necessary (boot, recovery, motoboot, system, and so on). However, in every thread and video, the "fastboot reboot" command makes the phone reboot into the actual OS, whereas mine just keeps rebooting into fastboot, regardless of what I flash.
I don't notice anything off, so hence why I recur to everyone in here to give me some advice on what I could be doing wrong. I've downloaded stock roms so far. I get a partition error with .zip files so always have to flash the images individually.
Please let me know if I'm missing any details, and/or what other information I should provide.
Thank you!!
Click to expand...
Click to collapse
Flash system.img and boot.img then flash twrp.img and boot into twrp and flash your stock ROM for your device
Hi guys,
I got a G5S+, which got stuck the other day.
It was booting, showing the blue Motorola screen but ended up with a lying down android with a red questionmark and saying 'no command'.
I read through a couple of threads and finally decided, I need to flash stock again.
I did not have switched on USB debugging and so on, as the phone was quite new to me.
I decided to run with that tutorial here:
https://forum.xda-developers.com/g5-plus/how-to/solution-to-flash-stock-romfactory-t3691396
Which seemed to be the right one.
Said so, booted into bootloader, installed the driver on my Win10 PC and ran through the steps.
I gut stuck on 'fastboot flash system system.img_sparsechunk.3' (15mins waiting..... after the steps before required about 12 Sec each) and needed to disconnect and connect the phone again.
Started with the same command and it worked.
Anyway when I got to the command 'fastboot flash system system.img_sparsechunk.5' I realized in the Potter Retail, there is no such file (neither there is 6 or 7).
I skipped the commands and continued.
When it came to rebooting the phone disconnected and thats it.
Since then I am not able to turn my phone back on.
Sometimes there seems to be a small notofication led showing up when trying to turn on the phone.
And you can hear the USB connect sound when I connect it to my computer.
Did anyone of you guys experience the same issue or has an idea what to do?
I have no idea what I shall so.
Best regards,
Matt
Which stock ROM did you flash? I'm hoping that following that guide, you flashed a stock ROM for sanders (i.e. the codename for Moto G5S Plus) and not for potter (codename for G5 Plus), which appear to be not compatible with each other.
Your original issue appears to be your device is booting into the stock recovery (which the start of is the 'no recovery' screen).
Do you know what model number or retail software channel, or the software build you had on your device before it failed? If so, we may be able to flash the correct sanders stock ROM to your device and get it going again. Another user appears to have gotten their device working when they incorrectly flashed the potter stock ROM and not sanders. https://forum.xda-developers.com/moto-g5s-plus/help/bricked-moto-g5s-plus-t3747064 Ideally you will want to flash the correct stock ROM for your device.
Oha damn you are right.
I am an idiot and tried to flash Potter to a G5S Plus.
Oh boy. I should not flash a cellphone after a long day at work.
I had the latest safety update installed and the latest release.
I am not sure though which software that used to be.
Unbelievable.....
Anyway, so my screen does not show anything anymore.
I guess the display driver dows not work or something like that.
The cellphone is still working I think, as the USB sound still appears.
Does anyone have an idea what to do if the screen stays black.
I still cannot believe it.....
Thanks though for your help!
EDIT: fastboot still reckognizes the phone. I guess this is good.
But the command 'fastboot oem fb_mode_set' runs into an error.
Edit2:
I skipped the first command and everything ran through (with some error messages though).
I hope it works now.
Device is currently rebooting and showing the blue motorola screen.
Lucky me.....
Okay, at least your device is booting now (ish)... I saw your other post and was wondering if you were able to boot from the bootloader.
1)Boot to fastboot (probably easiest by powering off your device, then hold down power and volume down keys until your device boots).
2)Once in the fastboot menu (with details about your device, like bootloader version), check that 'Start' is selected, and press the Power button to select. If 'Start' is not showing, use the volume keys to scroll through the options until 'Start' appears. Sometimes, this booting via fastboot bypasses an auto-boot to recovery mode.
Failing that, if you're on the 'no command' screen, then hold down the power button and tap the volume up key. Release both and it should let you into the recovery menu. Then, you can try to reboot to system.
Hi there,
I ran through all the steps you said.
But I ended up having the same issue. I always get back to the broken droid.
Is there a way to flash a completely new ROM to the device in its current condition?
I don't mind having a customrom, but I want to get it working again.
Thanks!
Matt
I solved my problem:
It was the SD card. I cannot believe it.
I got myself another G5S Plus and swapped everything:
Same issue.
So I removed the memory card and all good again.
I am quite sad though not having figured that out earlier, becoz all my data is lost now....
Thanks for your help though!
After months of deliberation I finally decided to root my Note 9. It was the first time I've ever tried rooting and it seems to have gone horribly wrong. To root the phone, I followed the guide in the video titled 'How to Root Galaxy Note 9! [EASIEST METHOD]' on youtube which has an instruction link in the description. As a new user here, the forum doesn't allow me to post links yet, so please just type the title on youtube and it'll come up as the first result.
What I did was:
- unlocking bootloader
- Flash AP file with TWRP version 3.4.0
- Wipe data
- Since I was worried about using a software from an unknown source, I then flashed the official magisk v20.4 instead of the 'N9-S9_root_for_oem_issue_devices_v3' file recommended in the video.
After doing so, the note 9 restarted and showed the error message "Verification Failed, Unable to restart your device. The Integrity verification has failed. You need to reset your device to factory default settings. This will erase all your data.". I allowed the phone to reset.
Following this, the phone restarted and showed exactly the same message of 'verification failed' and no amount of going through the rebooting process resolved the issue. I googled the issue and was advised to flash the phone with Odin by going into download mode. I then tried to go into download mode, but the phone will simply not go into it and tries to restart the normal way. I also tried to connect to my laptop to see if I can flash with odin but the phone was not recognised at all by the computer.
I then tried to reboot using the twrp key combo and this worked. I then decided to try flashing with the 'N9-S9_root_for_oem_issue_devices_v3' file in the tutorial. Yet, this led to the same issue as with the official magisk file.
Looking at some rooting tutorials, I see that some of them recommend flashing CSC, AP, BL and CP instead of just the AP in the tutorial I followed. I then thought that perhaps the issue is I need to install a ROM on the device. I therefore tried to load the lineage 17.1 ROM in the micro SD card and installed it (top left option on twrp 'install') as well as the magisk and disable_dm_verify_forceencrypt zip files.
In hindsight, this was a stupid move from me - I did so I was in full panic mode at that point and desperate for a solution.
After doing so, the phone rebooted and showed a booting animation of a single blue curved line stuck with a circle rolling from right to left on it.
I left it for a while, hoping that it meant the new ROM was booting. 30 min later it was still stuck on the animation!
I then tried to reboot the phone. Pressing power button did nothing. I then tried different combinations and eventually power + volume up + bixby allowed it to restart in TWRP mode.
As of now, the phone is still in TWRP mode. The phone is still not recognised by my laptop and will not enter download mode if I press volume down + bixby when restarting.
I am fully aware that I've screwed up the rooting process and feel awful about it. It was the first time I've ever tried rooting and I really hope it is only a 'soft brick' and that my phone can be saved. I would really appreciate if anyone here could advise what I can do to complete the root process correctly from here?
Many thanks,
Sam
Is there a "download" or "bootloader" option when you press the reboot button in TWRP? My Note9 is on stock, so I'm not 100% certain myself. However if there is, that should take you to Samsung's download screen. This way you can send yourself back to stock if you give up on rooting your device.
BTW, I do recommend following a note9 rooting guide on XDA (it's not too hard to find) over a youtube video, since YouTube videos can often be out of date or a little sketchy.