Related
Dear All
I'm a new android user, I just get a new A50 from Australia and try to root it. It's successful with z4root and I try to install Thai font to system. Unfortuantely I did wrong by deleting font folder in the system, therefore I can't run the system again. When I power on, it still have only garmin asus android logo and can't use it again. Does anyone please let me know how to restore or resolve this problem, or I have to throw it away? Thank you in advance.
Cheers!
Winext
Android 1.6 or the new 2.1 Eclair update?
It's a new Eclair 2.1 update, is there any solution?
Connect it to your computer via USB cable.
Using ADB, try this:
ADB REBOOT RECOVERY.
If it works, a yellow triangle appears with the green android guy.
Hit the HOME button. A menu appears. Use volume up/down to move through the options. Tap power to select it I beleive.
Reset/wipe to factory is one of the options.
If you need it, ADB is found in the Android SDK.
If that doesn't work, try calling in to Garmin for support.
Sent from my Garminfone using XDA App
Dear Spazmogen
Thank you for your suggestion, but I'm really new with ANDROID.
I downloaded ANDROID SDK and try to install but it dodn't work.
I use Win 7 64bit, do I need another software to run this command.
If possible, please let me know some previous post that already teach for beginner.
Thank you in advance.
Cheers!
Winext
ADB is a command line tool. But you will have to get Android SDK installed on the computer 1st.
Read the instructions for installing the SDK here: http://developer.android.com/sdk/index.html
ADB commands: HERE.
Interesting. I got into the recovery screen using the Quick Boot app,used the home button to show the menu. The arrows and volume buttons move, but can't actually do anything. Probably related to missing files that are reported in the data/cache/recovery folder.
https://www.garminasus.com/en_US/support/eclair/006-B1130-00.update
official 2.1 update came out today for USA GARMINFONES. Not the A50 Nuvifones elsewhere in the world...
Is the update different from the leaked one?
Sent from my Garminfone using XDA App
I am waiting for an answer to that question myself. I have no plans to change from the leaked version Garmin posted in mid-November.
Sent from my Garminfone using XDA App
Apparently someone did a bit comparison and said they matched. Plus, I tried and it told me it was the same version. On the plus side, I messed up my recovery partition and recovered it using the backups I made of each partition after I loaded 2.1 (dump_image). I made img backups and tar backups of all the files in 1.6 (I am anal about backing up). Good thing because 2.1 doesn't come with flash_image.
I can get into fastboot and the driver loads and stuff, but I get no devices listed when I do fastboot devices command. Next stop is Ubuntu
I know it works,just need to know how to get to it. Btw,I tried both the Garmin fastboot and adb drivers as well as adding the device hardware id's into the android drivers and neither worked.
I also need to find out if there is a similar enough kernel that I can use to get a fully functional recovery mode. I did find out that you can use adb just fine in the stock one and it loads a serial driver as well.
any possible way I could get that backup you made? I apparently didnt save my backup to the pc. And currrently I messed up permissions on my Garmin trying to get recovery working. I cant run the update or anything.
I've just stumbled across this forum post from google, I too am need of fixing my phone. All that is faulty is that the recovery mode has been overwritten with an incorrect one. Is it possible to extract the recovery image and reflash it from the optus supplied Android 2.1 006-B1130-00.update file?
Or is there a way of just getting say Rom Manager to work some magic for me?
Yes, it is possible... would be easier if someone could just use dump_image on a phone that has a working recovery mode and root access. I can provide the dump app and instructions.
Where can I get the Optus update, and are you positive recovery works on it? Does it also have working fastboot?
And to the other poster, which partition do you need? Btw, Rom manager has a permission fix mode. I can get you a tar file if it is the system partition or your choice of img or tar for the others.
And to everyone, after updating to 2.1, do a master clear because a lot of 1.6 apps are left over... duplicates.
Also, odexing all apps speeds it up a lot, with the caveat that you have to re-run the odex.sh file (found somewhere here and modified by me to be more thorough) after every app update or you will get force closes.
Oh I just reflashed the update again, and I got my recover menu back!
I'm not sure if i need any help anymore, but thanks for your offer of help merwin.
By working, do you mean that you can get to it with a hardware key combination and can actually select items?
first of all ,i 'm sorry for my english .my a50 is dead too.i also delet font folder and i use the adb command 'adb reboot recovery'.but the error is device not found. and my pohone can not boot .it stop at the android guy . how can i setup the device..Q.......Q......help me ..pls
garmin-asus a50
i have this garmin asus a50 was running 2.1 after installing a few apps.
tried to reboot and now is stuck on android screen.
tried hard reset stuck on android screen with wipe userdata on top
please help!
garmin-asus a50 dead
yoyoset
i think i have the same problem please let me know of any progress
thank you
I went through the [GUIDE] Rooting the 10.1 Tab, but I cannot get into fastboot.
I went through pershoots advice of uninstalling and reinstalling the drivers. I used the driver he has posted in the thread when I reinstalled.
Win7 cannot find the fastboot driver though. (Image attached)
*ADB works fine
*LE GoogleIO SGT with 3.1
Thanks to anyone who has some advice for me!
PS-- I'm too noob here to post in the dev forum.
same problem here annoying as f**
Hi, I facing the same problem here. Do you guys solve the problem? Please give me advice. Thank you
Same problem here. adb working fine on the tablet but not fastboot. I have tried Linux, osx, and win7 none work. Fastboot works fine on my nexus 1 with all of these platforms.
Sent from my GT-P7510 using XDA Premium App
Hi I just use mac os to done it, cause my windows 7 cant find the driver
my tab had just alive.. i cant post the link here cause i m newcomer..
jamn224 said:
I went through the [GUIDE] Rooting the 10.1 Tab, but I cannot get into fastboot.
I went through pershoots advice of uninstalling and reinstalling the drivers. I used the driver he has posted in the thread when I reinstalled.
Win7 cannot find the fastboot driver though. (Image attached)
*ADB works fine
*LE GoogleIO SGT with 3.1
Thanks to anyone who has some advice for me!
PS-- I'm too noob here to post in the dev forum.
Click to expand...
Click to collapse
I had similar problems and managed to finally use fastboot.
You have to choose drivers manually.
Read this post on how to choose drivers in order to get fastboot working
http://forum.xda-developers.com/showthread.php?t=1176292
Still no luck
I have had this problem for months, I have tried everything on this thread and on at least 10 to 20 other threads acrost the internet. I really need some help getting fastboot to work with my Galaxy Tab 10.1 Google I/O LE. Could this problem be from it being a I/O LE? Its so different than the shipping retail product, maybe these guides are for the retail 10.1? I would really appreciate any help!
Thanks
Josh
flacojo32,
As having just purchased an i/o edition used, i know what you mean about the differences, but i was able to root through fastboot on mine.. i just had to figure it out myself.
try this page, i wrote my steps that were successful for getting fastboot to load recovery:
http://forum.xda-developers.com/showthread.php?t=1429344
you may need to purge other drivers. i don't know exactly what protocol or method the fastboot is using for communication, but it may be based off the windows networking stack. i'd also suggest disabling any firewalls if it continues to fail.
flacojo32 said:
I have had this problem for months, I have tried everything on this thread and on at least 10 to 20 other threads acrost the internet. I really need some help getting fastboot to work with my Galaxy Tab 10.1 Google I/O LE. Could this problem be from it being a I/O LE? Its so different than the shipping retail product, maybe these guides are for the retail 10.1? I would really appreciate any help!
Thanks
Josh
Click to expand...
Click to collapse
The problem is using the right drivers. Going from memory here but in genersl go to your android-sdk folder and run sdk manager, select 3rd party and make sure to select usb drivers. After installing that go to device manager connect hte tab and you should see android device. if it has an exclamation point click on it and select update driver then select let me choose (not the browse for driver) - youn can then browse a list of devices and select samsung device. Once you do that the drivers are installed. you should be able to do fastboot.
A quick test is with the tab connected to the pc open a commamd editor type 'fastboot devices' and it should show a number
Sent from my GT-P7510 using Tapatalk
Thanks all for you help, but still no luck. I have rooted and or installed many of custom roms but just can't crack this one. I have all the right drivers for my other nexus devices to root them but this samsung galaxy tab 10.1 Google I/O just does not do fastboot right. It goes into fastboot but I don't know if its actually pushing the information to the computer. When I look under the Device Manager it show up as an ADB device, not fastboot. Also ADB works fine so the issue is with the tablet and how the fastboot is accomplished. Is there any other way to get a custom rom on this without fasboot? I have tried to use Odin and ADB to push a recovery but when I ADB reboot devices it just boots back up. That is after I have pushed a recovery file to the tablet. Im hopelessly deadlocked, I thought the LE I/O tab was to be open in every way for devs. but I can't seem to crack this beautiful device. Thanks for everyones help!
Josh
---------- Post added at 07:23 AM ---------- Previous post was at 07:21 AM ----------
Heck and I even used a mac that does not require drivers to try it, still it would not connect in fastboot mode. It did not even pull it up when I fastboot devices, just like on the windows machine.
Josh
flacojo32 said:
Thanks all for you help, but still no luck. I have rooted and or installed many of custom roms but just can't crack this one. I have all the right drivers for my other nexus devices to root them but this samsung galaxy tab 10.1 Google I/O just does not do fastboot right. It goes into fastboot but I don't know if its actually pushing the information to the computer. When I look under the Device Manager it show up as an ADB device, not fastboot. Also ADB works fine so the issue is with the tablet and how the fastboot is accomplished. Is there any other way to get a custom rom on this without fasboot? I have tried to use Odin and ADB to push a recovery but when I ADB reboot devices it just boots back up. That is after I have pushed a recovery file to the tablet. Im hopelessly deadlocked, I thought the LE I/O tab was to be open in every way for devs. but I can't seem to crack this beautiful device. Thanks for everyones help!
Josh
---------- Post added at 07:23 AM ---------- Previous post was at 07:21 AM ----------
Heck and I even used a mac that does not require drivers to try it, still it would not connect in fastboot mode. It did not even pull it up when I fastboot devices, just like on the windows machine.
Josh
Click to expand...
Click to collapse
Sorry for dumb Qs but wanted to make sure we are all on the same page.
So i take it you dont get a response when you connect via fastboot and type fastboot devices
You said you can use adb to push recovery did you try booting up from cold with the power and volume keys combo to enter recovery mode?
Sent from my GT-P7510 using Tapatalk
Right no response from the device or the PC when I type fastboot devices either on a Mac or PC. The problem lies that there is no button combination to boot the Google I/O LE Galaxy Tab into recovery, the only two options the Power + volume down button boot provides are the Fastboot(USB symbol) and the Android dude shoveling stuff(ODIN) choices. I can push recovery all day using ADB but there is no way for me to boot into recovery on the Limited Edition Tab. This is even after I try to reboot into recovery using ADB (ADB recovery or something like that) all that does is to boot me to the two choices Fastboot(USB symbol) and ODIN(android dude shoveling). I have pretty much tried everything. I appreciate all the help you are providing!
Josh
Any ideas? I can't be the only one with this problem.
flacojo32 said:
Any ideas? I can't be the only one with this problem.
Click to expand...
Click to collapse
It sounds like you do not have recovery. And since fastboot does not seem to work then it is likely yoi have the wrong drivers. Can you confirm you were able to push the recovery via adb?
Did you install the google drivers as described a couple of posts before ie using android sdk
Sent from my GT-P7510 using Tapatalk
animatechnica, I thank you for all of your help. But I return triumphant. I have found it to be a driver issue. I was trying to use a newer version of PDANet for Android (version 3.02) which did not include the correct drivers for the Galaxy Tab 10.1 LE. So I downloaded the version 2.15 of PDANet and bam fastboot started working like a charm. So I appreciate all the help from you animatechnica and also shane86 for his words of wisdom too. But overall tonight was a good night the Tide rolled, got my ICS update on my Transformer Prime and got fastboot to work and installed Galaxy Task 10.x on my Galaxy Tab 10.1 Google I/O LE. Im off to geek it up. Thanks all.
sweet and i will take note of how you solved it for future reference
flacojo32 said:
animatechnica, I thank you for all of your help. But I return triumphant. I have found it to be a driver issue. I was trying to use a newer version of PDANet for Android (version 3.02) which did not include the correct drivers for the Galaxy Tab 10.1 LE. So I downloaded the version 2.15 of PDANet and bam fastboot started working like a charm. So I appreciate all the help from you animatechnica and also shane86 for his words of wisdom too. But overall tonight was a good night the Tide rolled, got my ICS update on my Transformer Prime and got fastboot to work and installed Galaxy Task 10.x on my Galaxy Tab 10.1 Google I/O LE. Im off to geek it up. Thanks all.
Click to expand...
Click to collapse
I am trying to use 'adb' from the android dev kit but I cannot see the devices, i.e. 'adb devices' doesn't report any devices. It appeared to be working earlier this evening but not any more. I was going to push a rom file to my rooted phone but obviously since I no longer see the device I am stuck. I rooted yesterday and installed the maximus rom but my phone went into a loop of restarting. Unfortunately I didn't backup before I rooted and installed Maximus rom.
Can anybody offer any help? I am using Mac OSX.
Desperate since phone is now effectively redundant
adiemask said:
I am trying to use 'adb' from the android dev kit but I cannot see the devices, i.e. 'adb devices' doesn't report any devices. It appeared to be working earlier this evening but not any more. I was going to push a rom file to my rooted phone but obviously since I no longer see the device I am stuck. I rooted yesterday and installed the maximus rom but my phone went into a loop of restarting. Unfortunately I didn't backup before I rooted and installed Maximus rom.
Can anybody offer any help? I am using Mac OSX.
Desperate since phone is now effectively redundant
Click to expand...
Click to collapse
try this: http://forum.xda-developers.com/showthread.php?t=1706918
if it didnt help u just reply and we´re gonna look whats next to unbrick ur phone
Hi
Thanks for your reply, I have hit the 'Thanks' button
I read the posting you referenced but it doesn't really offer a solution to my problem.
As described earlier I rooted my phone and flashed a Rom (Maximus) succesfully but on turning the phone on after installing the new Rom I got into a cycle of the phone rebooting without actually getting past the lock screen. My thoughts at that stage were to re flash using stock rom but on running fastboot and plugging into my Mac OSX machine via USB, the phone doesn't show up in 'devices' on the Mac. I have also tried 'adb devices' form within Android Dev Tools and although 'adb' runs fine no device is reported. Of course without devices being avaialble to 'adb' then I cannot reflash!
I have also tried from within a bootcamp installation of 'Windows XP' installed on the mac with the same results, this with 'HTC Sync' installed and therefore providing the USB Drivers required within Windows.
I have tried logging into fastboot using 'power' and 'Down Volume' at various stages of the boot process on the phone but have never seen the phone within devices.
Clearly prior to installation of the Rom (Maximus) I could see devices at both the Finder window on the Mac and from adb devices.
Any help or insight you could provide would be very gratefully received
Ok ok ok dont worry
I had to read a bit and found quit much german threads where they flash back the stock rom
as is suggested u cant flash it with odin...
the only solution i woul suggest is that u have to find a computer running windows
there its very easy to restore the stock with the methods u described earlier in the thread...
hope u get done let me know what happend
=)
The question remains; how can I flash anything be it a hacked rom or an official rom when I cant see the 'device' in both windows and mac osx?
I think what I am looking for is a reason why the phone isn't seen when plugging in via USB. Once it is seen as a 'device' I will be able to flash anything via 'adb'.
Thank you for your continued interest and assistance
ok so u know how the get it back but ur phone is not really recognized by ur computer
but i found a method using the bootloader
the problem is that the instructions are in german
but i think if u google a bit u may find it
Don't know if I misunderstood what you said..but to get into recovery, you hold volume down and the power button when the phone is turned off. Not during the boot process.
Yes you can do it with bootloader (power+volume down)
Sent from my HTC Salsa C510e using xda premium
moksha098 said:
Yes you can do it with bootloader (power+volume down)
Sent from my HTC Salsa C510e using xda premium
Click to expand...
Click to collapse
Yes, I know that. He said he attempted to do that DURING the boot process. I was stating that he had to do it while the phone was powered down.
Guys, I can get into recovery no problem. The issue is that my phone doesn't show up in devices on the mac finder window and hence when I run 'ADB Devices' from the mac when the phone is plugged into the mac with USB no device is found and so no serial number is reported in my terminal window on the mac. If I can get to see the device with 'ADB' I can push the rom and recover the phone. At the moment the phone is bricked.
Thanks guys for your continued assistance.
adiemask said:
Guys, I can get into recovery no problem. The issue is that my phone doesn't show up in devices on the mac finder window and hence when I run 'ADB Devices' from the mac when the phone is plugged into the mac with USB no device is found and so no serial number is reported in my terminal window on the mac. If I can get to see the device with 'ADB' I can push the rom and recover the phone. At the moment the phone is bricked.
Thanks guys for your continued assistance.
Click to expand...
Click to collapse
But if this doenst work why dont u try the method with the recovery mode or the bootloader i suggested
Hello,
First off, I've gone through the forums and I have looked up other posts and despite everything I cannot figure out how to get my nexus 7 tablet to be recognized by the computer (I tried and after two days of searching for answers I decided to make a post). I like to include this information so people don't assume that I post without browsing or haven't tried anything yet.
The thing that I am having troubles with is that I have a nexus 7 tablet that is softbricked, I have already gone through a lot of ways to fix that problem (I found the best solution is this:http://forum.xda-developers.com/showthread.php?t=1809195). However, the issue is is that I cannot get my computer to recognize the nexus tablet to flash it and restore it back to factory settings.
I have installed and updated the device drivers on my computer, but still I have had no such luck. I found that ADB doesn't recognize the device whilst in the Bootloader, but still will not recognize the device in recovery mode. If anyone has any tips, or suggestions that might work PLEASE let me know, at this point I'm getting desperate and any/all help would be greatly appreciated!
Thank you!
NecroGi said:
Hello,
First off, I've gone through the forums and I have looked up other posts and despite everything I cannot figure out how to get my nexus 7 tablet to be recognized by the computer (I tried and after two days of searching for answers I decided to make a post). I like to include this information so people don't assume that I post without browsing or haven't tried anything yet.
The thing that I am having troubles with is that I have a nexus 7 tablet that is softbricked, I have already gone through a lot of ways to fix that problem (I found the best solution is this:http://forum.xda-developers.com/showthread.php?t=1809195). However, the issue is is that I cannot get my computer to recognize the nexus tablet to flash it and restore it back to factory settings.
I have installed and updated the device drivers on my computer, but still I have had no such luck. I found that ADB doesn't recognize the device whilst in the Bootloader, but still will not recognize the device in recovery mode. If anyone has any tips, or suggestions that might work PLEASE let me know, at this point I'm getting desperate and any/all help would be greatly appreciated!
Thank you!
Click to expand...
Click to collapse
adb is not designed to be usable in bootloader mode. You need fastboot for that. If you have the fastboot.exe program in the same folder as your adb stuff, try this:
fastboot devices
If it reads, then all you need to do is fastboot flash the various .img files back to the tablet. There are tool kits that do this for you, but I prefer doing it manually as there are less chances of things messing up and if they do, you're more likely to know at what step which could be useful for further troubleshooting if need be. It is important to download the correct img files due to differences between the generations and wifi / data enabled ones. There is a flash-all script that you can find in the download of the factory images, which might make it easier, but you can just manually flash the separate files as sometimes you don't need to bother with them all (like the bootloader) though if the script works, then it'll be fine and might make it easier if you are not familiar with the commands.
If you don't have fastboot at all, just grab it from here: http://forum.xda-developers.com/showthread.php?t=2317790
Nexus img files: https://developers.google.com/android/nexus/images
Hit me up on Hangouts if you need more direction.
NecroGi said:
Hello,
First off, I've gone through the forums and I have looked up other posts and despite everything I cannot figure out how to get my nexus 7 tablet to be recognized by the computer (I tried and after two days of searching for answers I decided to make a post). I like to include this information so people don't assume that I post without browsing or haven't tried anything yet.
The thing that I am having troubles with is that I have a nexus 7 tablet that is softbricked, I have already gone through a lot of ways to fix that problem (I found the best solution is this:http://forum.xda-developers.com/showthread.php?t=1809195). However, the issue is is that I cannot get my computer to recognize the nexus tablet to flash it and restore it back to factory settings.
I have installed and updated the device drivers on my computer, but still I have had no such luck. I found that ADB doesn't recognize the device whilst in the Bootloader, but still will not recognize the device in recovery mode. If anyone has any tips, or suggestions that might work PLEASE let me know, at this point I'm getting desperate and any/all help would be greatly appreciated!
Thank you!
Click to expand...
Click to collapse
You won't get adb in bootloader mode.
You have to use the fastboot command.
Please tell the OS on your computer.
Use the tool in my signature as an environment.
Download 7zip, and install that.
Then go here and download the proper image for your device.
It would either be "Factory Images "nakasi" for Nexus 7 (Wi-Fi)" or "Factory Images "nakasig" for Nexus 7 (Mobile)".
Grab the 4.4.2 version.
Extract the downloaded file with 7zip into the "Work" folder in the tool form my signature.
Then extract that "nakasig-kot49h-factory-83d93b5f.tar" file with 7zip.
Then go into the folder that came out of that, and extract the "image-nakasig-kot49h.zip" into the Work folder.
And enter the following commands while in bootloader.
Code:
fastboot oem unlock
fastboot erase userdata
fastboot erase system
fastboot erase recovery
fastboot erase cache
cd nakasig-kot49h
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
Make SURE you grab the correct image for your device. Wifi or Mobile.
I also assume that you know the .img files should be in the Work folder before you type thse commands into my tool.
Hey guys, first of all thank you for the speedy replies and steps I should follow.
Right now I'm using OSX but for the tablet I'm using a virtual Win7 machine to try and get this damn tablet to be recognized by the computer. The process is being delayed a little bit because my micro USB cords are being temperamental, meaning that the tablet has no juice, and when I mess with it (using the power + volume buttons to boot to bootloader/recover) the cord comes unplugged. I know automatically you guys are going to pinpoint this as the source of the issue (mainly because I would too), but it works fine if just laid flat and stays connected. It just has zero charge so when it disconnects/reconnects I literally have to power it back up, just need to wait for it to have some charge before I tinker with it more.
I will post updates after it charges.
Although I already thanked you guys, thanks again for speedy reply. It's much appreciated.
NecroGi said:
Hey guys, first of all thank you for the speedy replies and steps I should follow.
Right now I'm using OSX but for the tablet I'm using a virtual Win7 machine to try and get this damn tablet to be recognized by the computer. The process is being delayed a little bit because my micro USB cords are being temperamental, meaning that the tablet has no juice, and when I mess with it (using the power + volume buttons to boot to bootloader/recover) the cord comes unplugged. I know automatically you guys are going to pinpoint this as the source of the issue (mainly because I would too), but it works fine if just laid flat and stays connected. It just has zero charge so when it disconnects/reconnects I literally have to power it back up, just need to wait for it to have some charge before I tinker with it more.
I will post updates after it charges.
Although I already thanked you guys, thanks again for speedy reply. It's much appreciated.
Click to expand...
Click to collapse
I suggest to STOP!!!
If you are trying to restore the device and the cable disconnects in the middle of it, it might not be recoverable. That would be one of the few ways to really damage the tablet as they are pretty difficult to hard brick. Don't half ass it with stuff like this. A good cable is not THAT much and will certainly be cheaper than a new tablet or getting it to a point where you might have to send it somewhere for service.
I'm not familiar with Macs, but if you are more so, then this might be better than using a Virtual set up:
https://code.google.com/p/adb-fastboot-install/
es0tericcha0s said:
I suggest to STOP!!!
If you are trying to restore the device and the cable disconnects in the middle of it, it might not be recoverable. That would be one of the few ways to really damage the tablet as they are pretty difficult to hard brick. Don't half ass it with stuff like this. A good cable is not THAT much and will certainly be cheaper than a new tablet or getting it to a point where you might have to send it somewhere for service.
I'm not familiar with Macs, but if you are more so, then this might be better than using a Virtual set up:
Click to expand...
Click to collapse
It's actually working fine now (in the sense that the computer can now read it). The Virtual Machine also works just as good, but for some reason the toolkit I'm using won't properly return the tablet to the stock image using the SkipSoft Android ToolKit, so I'm going to have to try and find another way.
Thanks for your guys' help.
Hello my dear fellow community of XDA
I’m asking you for help, I found myself in a tough situation because I damaged system in tablet Nexus 9. Bootloader was already unlocked in my device when I bought it. I assume that the system was original. I didn’t notice any modifications. I damaged this system by uploading a file in a fastboot mode connected by ADB. This file is for rooting. I used this guide on the YouTube:
After doing everything step by step in this guide and switching my device on there was a sign of launching - vibration. The next thing I saw was white Google logo and after that the animation of loading appeared. It was loading without any success.
Before uploading the root file I also tried to upload TWRP file via ADB but it didn’t make any difference. After uploading TWRP files system launched properly, there is no new app in the app list and no combination of buttons such as power + volume that launches TWRP. Please tell me if I’m doing something wrong…
I tried to fix this bootloop by cleaning files via Hboot - factory reset but it didn’t change anything. I was searching for guides that would help me solve my problem but I couldn’t find anything useful. Each of them was old. They were from 2014 or 2015.
I would like to have a working tablet with TWRP, root and other unofficial system (you can give me some suggestions, I was thinking about Android 9). I don’t know where to start or what should I do first. Fix bootloop or upload TWRP ? What is correct order ? How to upload TWRP eligibly ? I rooted devices only several times so please excuse me, I am not a professional. I know that guide on YouTube mentioned before was for Android „L” not „N”.
Summary:
> Tablet Nexus 9 OP82100 WiFi version 32GB
> I use PC with Windows 10
> After connecting the tablet to the PC via USB cable in fastboot mode the tablet is visible in ADB console on the list of devices.
I hope that each information I gave you is clear enough. This is my first post on this forum. I hope somebody will find some minutes for reading this post. I’m counting on you. Thank you in advance for any help.
Ok, I honestly didn't read everything, but if you have and can access fastboot, flash TWRP, transfer a ROM to the internal memory, wipe data (not storage) and flash your ROM.
Try getting Wug's Nexus Root Toolkit, it's a graphical UI for adb and fastboot, might be a little friendlier for you.