A few months ago i broke the screen on my N7. I put it in a drawer until I could order a new screen. Yesterday I decided to play with it a bit after finding the tool permitting use with a broken screen.
I could not get my computer or any other i tried to recognize the tablet while in Android. However, if I was in fastboot or recovery I could communicate with the device via ADB. I attributed the connections issues to not having USB Debugging enabled and not being able to unlock the screen. I proceeded to try and modify the build.prop via ADB until I came across some misinformation and mistakenly deleted the build.prop.
I need some help getting the tablet to a state where I can control it via the Android broken screen tool avaipable here on XDA.
Do you have an unlocked bootloader mate?
I believe so. It's been a while since I tinkered with the tablet, but I usually root and unlock all my devices. This Nexus 7 is running Cyanogenmod.
jconnell said:
I believe so. It's been a while since I tinkered with the tablet, but I usually root and unlock all my devices. This Nexus 7 is running Cyanogenmod.
Click to expand...
Click to collapse
Do you have a custom recovery or not? If you do, you can just dirty flash your ROM again
I do. It's running TWRP. Could you tell me more about a dirty flash?
Get the the tablet into the bootloader, flash just the system.img of whatever ROM is installed using fastboot, done.
Would it be possible to enable debugging and disable the lock screen in the system image before flashing? If not, possible to do it after?
Related
Hi,
I own a Nexus One with CyanogenMod 7 RC1. I've rooted my phone without unlocking my bootloader (with super1click) using ClockworkMod as the Recovery console. The "wonk" was starting to drive me crazy.
Yesterday, for some "strage" reason (probably a bubble to the head!!) I decided to Flash the stock Rom to my phone (I wanted to try the official release of Gingerbread). My mistake was doing it through Rom Manager.
It sorta "semi" briked my nexus.
When I do a normal boot, I see the android X loading, then, the screen goes blank. I know something's going on on the device because my trackball is flashing white. I even get heptic feedback from the four bottom buttons. But the screen is always black!
When I boot into the bootloader menu (power+down) and try going into the Recovery console, my screen is also all black! There again, something must be going on because my computer detect the attached device, but unfortunately, I can't ADB (device not found!!)
Finally, when I boot into the bootloader menu (power+down) and I enable Fastboot USB, I cant "flash" anything onto the device (I get an error at the signature verification). This is probably due to the fact that my bootloader is still locked (I guess).
Here are my questions:
1- Is it a lost cause? Is my nexus forever in this semi bricked state?
2- Is my only option to solve the issue is unlocking the bootloader?
3- Will that work?
I would like (if possible) not to unlock the bootloader but if that's my only option, I'll do it without any issues.
If I unlock the bootloader, what then? Do I "fastboot flash recovery" a working recovery image and then, from the recovery console reflash any good rom?
Thanks for reading this long post and for helping me out!
Have you decided which ROM you want to use yet? When you have found one, extract the contents of the .zip and flash the contents using fastboot. Obviously you'll need to unlock the Bootloader first but what's the point of having that ability if you're not going to use it?
Lot's of info in the WIKI.
Hi Thanks for the reply!
I'll probably go back with CyanogenMod 6.1.1 (Stable release).
So you're telling me that I have no other choice and I'll need to unlock the bootloader?
What If I decide to flash the Stock ROM? I'll still need to unlock it right?
Thanks
From your original post it doesn't sound like there's any other option. Consider it a blessing in disguise though. Fastboot is a terrific feature to have as it makes flashing safe and easy.
THIS would be a good ROM to start with if you want to try out the stock Gingerbread experience.
I have been trying to root my incredible 2 ver 2.3.4 and managed to get it unlocked so I could change carriers. However, in the process of trying to also root the phone using adb I seem to have flashed improperly somehow and corrupted the recovery image instead of replacing it. Maybe I got hold of a corrupt TWC_recovery image and that is the problem. I was trying to flash TWC and it claimed to work but upon trying to reboot into recovery it simply sits at the white HTC screen and stalls.
When I use the cable and ADB to tryi and flash clockwork instead of TWC it apparently is not communicating with the phone. I used adb devices and the list is empty.
Incidentally the phone still boots up good and works fine as a phone but recovery mode using the phone menu is also history. Is there anyway to fix this. It seems like a catch 22 and I am stumped. At any rate, not being able to flash eithere using the phone itself or adb and the laptop has me stymied. Anyone have any ideas. I want to root also and it seems I have to get back to 2.3.3 in order to do that.
My experience is limited. I have successfully rooted my Hero (previous phone) and my Toshiba Thrive in the past though. All went well with them.
Any and all help will be greatly appreciated with proper thanks.
bushpilot444 said:
I have been trying to root my incredible 2 ver 2.3.4 and managed to get it unlocked so I could change carriers. However, in the process of trying to also root the phone using adb I seem to have flashed improperly somehow and corrupted the recovery image instead of replacing it. Maybe I got hold of a corrupt TWC_recovery image and that is the problem. I was trying to flash TWC and it claimed to work but upon trying to reboot into recovery it simply sits at the white HTC screen and stalls.
When I use the cable and ADB to tryi and flash clockwork instead of TWC it apparently is not communicating with the phone. I used adb devices and the list is empty.
Incidentally the phone still boots up good and works fine as a phone but recovery mode using the phone menu is also history. Is there anyway to fix this. It seems like a catch 22 and I am stumped. At any rate, not being able to flash eithere using the phone itself or adb and the laptop has me stymied. Anyone have any ideas. I want to root also and it seems I have to get back to 2.3.3 in order to do that.
My experience is limited. I have successfully rooted my Hero (previous phone) and my Toshiba Thrive in the past though. All went well with them.
Any and all help will be greatly appreciated with proper thanks.
Click to expand...
Click to collapse
download a recovery then rename it to recovery.img then boot your phone to fastboot and connect it to pc put the recovery into your fastboot folder then run this command
fastboot flash recovery recovery.img
this should fix your recovery NOTE ADB commands doesn't work until your phone boots up completely hence recovery is always flashed using fastboot commands
Or better yet, install rom manager and click install recovery
Sent from my ADR6350 using Tapatalk
An error occurred while flashing your recovery
weldawadyathink said:
Or better yet, install rom manager and click install recovery
Sent from my ADR6350 using Tapatalk
Click to expand...
Click to collapse
When I try to install clockworkMod Recovery via Rom Mgr it downloads ok and then as it tries to install it dies with the error 'An error occurred while flashing your recovery.'
As I said earlier, when I try using the pc and cable it stalls on 'waiting' because it can't communicate with the phone.
The phone no longer goes into USB Boot like it did earlier..... it did though prior to the corruption.
Any other ideas? Thanks for the help.
Soft Bricked Help?
First of all, my inc2 is unlocked but is NOT rooted.
It has hboot-0.98.0000
radio-1.09.01.0312
rMMC-boot
July 18 2011, 12:39:36
Ver 2.3.4
I tried each of the methods in the earlier posts in the thread and neither worked for me. In the process, I have screwed something and now my phone will not boot into normal phone mode either.
Somehow I have corrupted something that is preventing my flashing a new recovery. Since it is not rooted, I am not sure what I can adb flash and what I can't. I have tried flashing both Clockwork recovery and TWP and although adb reports success the phone will not go into recovery. It simply displays stuck on the white screen with the HTC logo. I also tried flashing by zipping up a rom and clockwork recovery and renaming the zip PG32IMG.zip, loading it onto the sdcard, and loading it at bootup of hboot. It shows loading, then I select reboot bootloader, then try loading recovery and the same thing. Stuck on the HTC white screen. Now, the phone will not boot into normal phone mode either but just sticks on the white screen. I am wondering..... do I need to do a wipe or anything else prior to flashing the recovery? Maybe partition is bad. I don't know the procedure for any of that. I appreciate any help I can get.
Use revolutionary if its unlocked already it'll flash su n cwm
Sent from my ADR6350 using xda app-developers app
Anyone I can mail this phone to that will fix it and root it for $$?
chillybean said:
Use revolutionary if its unlocked already it'll flash su n cwm
Sent from my ADR6350 using xda app-developers app
Click to expand...
Click to collapse
I have tried that but it won't work because my phone is has hboot-0.98.0000 and when I follow the exact described procedure to change back to 97 it fails.
Is there some guru that fixes these for a living I can send the phone to? Anyone know? :crying:
What carrier are you planning to switch to? On the GSM side, you will most likely get no faster than 2G or 2.5G / Edge speed on data, depending on the radio band used by your provider. It is reliable & dependable for voice and/or WiFi calling with excellent battery life.
SInce you've tried to fixed it a number of ways with limited luck, you should consider flashing one of the factory/VZW's RUU file to restore it back to stock condition, unrooted - then, start the process over. The tacoroot method is what I've used last year to fixed one that appeared to be 100% brick.
PM me if you have trouble locating and want to use the RUU files as I believed that are no longer on the server - see what I can come up with from offline storage.
Letitride said:
What carrier are you planning to switch to? On the GSM side, you will most likely get no faster than 2G or 2.5G / Edge speed on data, depending on the radio band used by your provider. It is reliable & dependable for voice and/or WiFi calling with excellent battery life.
SInce you've tried to fixed it a number of ways with limited luck, you should consider flashing one of the factory/VZW's RUU file to restore it back to stock condition, unrooted - then, start the process over. The tacoroot method is what I've used last year to fixed one that appeared to be 100% brick.
PM me if you have trouble locating and want to use the RUU files as I believed that are no longer on the server - see what I can come up with from offline storage.
Click to expand...
Click to collapse
I have droid Incredible 2 by verizone. I got it unlocked and S-OFF to use custom rom.
During the process, SD card is not detecting any more. Also, USB debugging is not functioning. Therefore, I cannot use any custom ROM now.
I have flashed Chinese 3.07.1401.3 as S710D. Because any of original Vrizone rom are not loading. The current situation is that all functions
are working except which are related to SD CARD, like photo/video, music, software download etc.
USB HOST CONTROLLER shown that S3C usb driver is missing. Please help.
farooq4u said:
I have droid Incredible 2 by verizone. I got it unlocked and S-OFF to use custom rom.
During the process, SD card is not detecting any more. Also, USB debugging is not functioning. Therefore, I cannot use any custom ROM now.
I have flashed Chinese 3.07.1401.3 as S710D. Because any of original Vrizone rom are not loading. The current situation is that all functions
are working except which are related to SD CARD, like photo/video, music, software download etc.
USB HOST CONTROLLER shown that S3C usb driver is missing. Please help.
Click to expand...
Click to collapse
Can you confirm that you can boot into your bootloader - what are the statistics?
S-OFF ??
HBOOT-
Radio-
eMMC-boot
Apr 1 2001, 18:34:30 (or something similiar)
You are most likely missing the correct HTC drivers or have corrupted ones installed. Uninstall & clean it off your PC first, reboot & start over (or, use/borrow another computer to do this - look into the Control Panel ...)
Unless you are planning or using the DI2 on a Chinese carrier that support CDMA and/or GSM, you could run into issues - and, getting it to reset & work properly back on CDMA with VZW could be problematic too.
As for the SD card read error, have you checked its usability on the PC or another device directly, do you have another mSD card to check & verify that the slot ont the device isn't broken/damaged/dirty, etc. ?? Format it on a PC to FAT32 and copy a dummy file, re-insert to DI2 and see what happened ...
Hi everyone,
I really need help since i found no solutions to my problem.
I wiped all my data with TWRP and even my OS. I have nothing installed and when i try to boot the Nexus it just goes in a bootloop. I can't flash anything from TWRP and when i try to copy a ROM to my Nexus via my PC, the PC just doesn't recognize the Nexus, thus i can't see the internal storage. Flashing stock doesn't work ever because of unrecognized device. What should I do ? is there any solutions to my issue ?
Thank you for reading.
Nexuuss17 said:
Hi everyone,
I really need help since i found no solutions to my problem.
I wiped all my data with TWRP and even my OS. I have nothing installed and when i try to boot the Nexus it just goes in a bootloop. I can't flash anything from TWRP and when i try to copy a ROM to my Nexus via my PC, the PC just doesn't recognize the Nexus, thus i can't see the internal storage. Flashing stock doesn't work ever because of unrecognized device. What should I do ? is there any solutions to my issue ?
Thank you for reading.
Click to expand...
Click to collapse
I got the same issue. Since I couldn't find a solution anywhere, I replaced the device yesterday. I tried everything you have. No solution. The display on mine was partially damaged. Don't know if that was related to the issue or not.
I just did what you did moments ago (deleting OS by accident) and I have no way of installing a new ROM on there since the computer stopped recognizing my nexus 7 after rooting it for a few hours a few months back..
MiKaiiEL said:
I just did what you did moments ago (deleting OS by accident) and I have no way of installing a new ROM on there since the computer stopped recognizing my nexus 7 after rooting it for a few hours a few months back..
Click to expand...
Click to collapse
Here is a new tip!
A few moments ago I found a workaround that fixed the problem, at least for me!
First, I charged the tablet up to 8%;
then, I booted into bootloader mode.
By the way, my bootloader was unlocked.
Becuase I had no OS installed, nor a custom recovery, I had little hope that the computer would recognize my device.
HOWEVER, when I used an identical cable (one that came with a different Nexus 7 2013,
The program "Nexus Root Toolkit" recognized the tablet, automatically flashed the stock firmware!
To ANYONE who has had this problem, TRY MAKING THESE SMALL CHANGES.
Boot into TWRP and start the adb sideload. Simply run adb sideload 'file name' from the ROM directory on your pc. Either that or flash stock with fastboot.
Make sure you have installed adb drivers properly otherwise your device wont be found. I have several problems with MTP from recovery, so use the sideload function.
My phone bootloops into teamwin logo with no commands, it's not recognize by my PC even though it was before I flash new vendor and a custom rom. it will allow me to go into fastboot.
It happens to me now, but with stock 7.1.1 (beta program).
rodrigo82 said:
It happens to me now, but with stock 7.1.1 (beta program).
Click to expand...
Click to collapse
How did you fix it? I am a Mac-user and Nexus Root Toolkit is not available for me
yychun1217 said:
How did you fix it? I am a Mac-user and Nexus Root Toolkit is not available for me
Click to expand...
Click to collapse
I googled it and I discovered that there's no fix.
It's a hardware problem, specifically on emmc controller.
End of story: I bought a Samsung J5 Metal and I still missing my dearest N5X.
And my N5X only works on bootloader.
I'm having a similar issue my phone froze and was bootlooping. I was able to access recovery and recover files from the SD. However Im now having a hard turning on the phone and when I do, I can get it into bootloader/ recovery but computer won't recognize it. So I can't lock the bootloader and unroot to send it in for repair. I'm probably going to send I'm the phone as is and hope it gets fixed. It's crazy that it just froze while I was using YouTube and started bootlooping. Now using my Nexus5
Sent from my Nexus 5
Hello everyone, so as the title suggests I have an a520f device that suddenly got frp locked after a reboot, and I'm guessing it was because I disabled and re-enabled developer options and forgot to turn on OEM unlocking again. anyway the thing is I tried using Tenorshare 4ukey but it didn't detect my device and same thing with Odin when I tried to flash a stock rom. I tried every possible fix (using a different cable a different usb port a dfferent pc etcc..) and none of them worked until I decided to take the phone to a local workshop and they told me that the data transfer port was broken and honestly they asked for more than what the whole device is worth to replace it. So I was wondering if there is a way to install a stock rom without a pc or/and rooting (directly from an sd card using recovery mode maybe)? any help would be greatly appreciated! and sorry about the long read I just tried to include any detail that might be helpful.
astralsabbat said:
Hello everyone, so as the title suggests I have an a520f device that suddenly got frp locked after a reboot, and I'm guessing it was because I disabled and re-enabled developer options and forgot to turn on OEM unlocking again. anyway the thing is I tried using Tenorshare 4ukey but it didn't detect my device and same thing with Odin when I tried to flash a stock rom. I tried every possible fix (using a different cable a different usb port a dfferent pc etcc..) and none of them worked until I decided to take the phone to a local workshop and they told me that the data transfer port was broken and honestly they asked for more than what the whole device is worth to replace it. So I was wondering if there is a way to install a stock rom without a pc or/and rooting (directly from an sd card using recovery mode maybe)? any help would be greatly appreciated! and sorry about the long read I just tried to include any detail that might be helpful.
Click to expand...
Click to collapse
twrp recovery flashed on phone or not?
matkali said:
twrp recovery flashed on phone or not?
Click to expand...
Click to collapse
unfortunately not, Is there a way to flash it without Magisk or PC?
In know a rooter app "kingroot" [ I don't recommend for security reasons], which could be root your phone online!
If you can get root access!
you can use twrp flasher apps to flash your recovery!
Can't you just bypass frp?