Related
I received one of these the other day and began to tinker. Rooted with Gingerbreak v1.2, installed the full market, and busybox. All with no problems. I would like to change a few other things but with out having CWM to make a backup, I am a little cautious. When I go into the FWUpdate, it tells me there is an update. I tracked down the file on the web, downloaded it ( all 300 megs worth) and have been looking at it. If anyone would be interested it this file for development purposes I could upload it or provide the link of where to get it from.
Ive downloaded it. So far it fixes bugs. But you have to use root explorer to clear the unwanted apps
Sent from my LG-P500 using XDA App
Well I started dissecting the update. Found it is still 2.3.1, it uses fuse to manage the file system, and has an updated recovery. The file system layouts are a little different than what I normally see on my Incredible. It has separate mbr, uboot, kernel, env, system, ramdisk, ect... I would really like to change the density but with out having adb working or a custom recovery, if I use a value that is not compatible I am in a world of hurt.
Yeah its still the same. For nw i currently waiting for cm7 for viewpad 7e. Btw the viewpad 7e isnt big and limited people.
Sent from my LG-P500 using XDA App
Granted it is not a XOOM or a Galaxy Tab, but I don't think it should be it should be overlooked for development. I am not much of a programmer, but I do like to try. If a current developer could give some guidance as to how to build a custom recovery that would be beneficial.
Andy try power off the vp7e and then hold the power, volume
Up and down button. It resets my tablet.
Sent from my LG-P500 using XDA App
Yep, Power on with volume down boots into bootloader with a boot flag of 1 and volume up while power on also boots into recovery but with a boot flag of 2. Not sure what the difference is with the boot flag. I know that in both modes with usb pluged in, it is seen by my windows computer as a Viewpad 7e. Which is the same thing that is shown when I have usb debugging turned on with usb pluged in after a normal boot. I looked into the adb thing and I cant get adb to see it, even on my linux box. Kinda wierd the vendor id is 0bb0, Concord Camera Corp.
For now we have to wait for a custom recov and cm7 for our tablets
Sent from my LG-P500 using XDA App
My viewpad 7e keeps rebooting after rooting - please help
Hi Andyav.... I saw your post that you have downloaded the firmware for viewpad 7e. It may be my best chance to recover my viewpad 7e and have it working again.
My viewpad 7e started a reboot-loop after I rooted it with gingerbreak and ran the google market installation.
I need to restore the original firmware but I can't find it anywhere.
Please send me a link and allow me to download your copy of the firmware for the 7e. I would really appreciate if you could do this for me.
My email address is [email protected]
Hoping you would reply soon...
thanks,
Ariel(Reapjack)
Could you also sned me a link to the firmware. I received one yesterday, but its downloading the firmware at about 5% an hour for some reason! If I used this copy for firmware and put it on a micro sd and update the viewpad from that? Thanks in advance
My email is [email protected]
I pm the link to you for the update.
Reapjack - Not sure how you will install update. I would try to copy file to root of sd card and boot into recovery to see if it will install that way. If not rename it to update.zip to see if the recovery will work that way. Let us know know how it turns out and which way worked. Thanks.
I'm trying to download F70 VSAM_S_W_C_11282011.zip, but I have the same problem, the very slow download...
will you send me the firmware too?.
Thanks !
[email protected]
Update file ran but tablet keeps on rebooting..
Hi Andyav.. Thank you for the update file. The file ran as expected by putting it in the sdcard's root. The update went fine but my tablet still keeps on rebooting.
It seems that this update is overwriting only some files but not all. Maybe that part of the OS that was rooted earlier is not being overwritten. Would you know if there is a full update that will overwrite everyting?
Thank you again.... I appreciate the help so much!
Thanks Andyav !!!
I really appreciate your soon PM with the link.
I have problems with the spanish languaje, hope that this update fixt it.
I'll post the results.
Thanks again !
PAD
Reapjack - How did you apply the update. Through the recovery or through a normal boot? I know inside that update there is an updater-script for doing a full update, includes mbr, kernel, system...etc. I am not sure how to trigger it though. Maybe that’s what the boot flag is for in the recovery.
I did finally take the risk and adjust my density in the build.prop file. Tried a few different settings. Default is 180. I am currently running at 160 but did try 200 and 220. Looks good but the display is still not as clear as my phone (HTC Incredible running MIUI). I know the screens are not really comparable, but Viewsonic has been designing and building monitors for years and this is the best screen they could put in this tablet.
Also did some digging around on the internet about the host cable. Found a few here and there but I can be rather impatient at times, so I decided to make my own. Chopped off the end of an old Motorola house charger, shaved off al the plastic around the end, de-soldered the wires and one resistor from the small board. Then dismantled a usb cable I had made for my original Xbox, soldered the cable to the mini usb end, shorted pin 4 to pin 5, plugged her in with a keyboard attached and it worked, first try. I did notice that the host mode is not real reliable. After the initial test I could not get it recognize keyboard again. Checked all solder points, tested from usb female end to mini usb, all tested good. Several reboots with cable plugged in, nothing changed. I knows to go into host mode, I can see it switching when i run dmesg. But it just doesn't know what it attached to cable.
Andyav, i tot the lastest update is 20111125? I dont have the 28.... version for ota update.
Sent from my GT-I9000 using XDA App
hey andyav , try this website : www.viewsonic.com.au/kbase/article.php?id=492
Sent from my GT-I9000 using XDA App
After 12 hours of downloading, tried to upgrade from the internal application but after reboot, the process was canceled because it didn't find the .zip file on the sdcard. (error mounting sdcard)
Surely the problem was that the sdcard was not properly formatted.
Now,
the Recovery system shows 1.9 version and bootflag is only "1", regardless of the volume button I use to start (+ or -)
I formated the sdcard and tried to do a manual upgrade with the file downloaded directly from viewsonic: F70 VSAM_S_W_C_11282011.zip, but no luck, the recovery reported bad file.
Any help?
hellodzulz, will you tell me where did you dwonload the 20111125 update to try it
Thanks !
PAD
Over the last few days I have been trying to get the ready for custom roms when they become available. Digging around on the internet trying to find as much information as I could about the hardware. While digging around for devices that have custom roms and use the same processor line, I found some rather interesting information about the Galaxy S Unbrickable Mod. Basically it is a hardware mod that causes the phone to enter a Samsung download mode for flashing. Well I took the plunge and opened the case, found and verified the processor, broke out my multi-meter and went probing. Was able to locate the hardware that controls the boot sequence, preformed the mod and plugged it in to my linux box. Ran the Unbrickable Mod Mode Detector and it recognized it. HOLLY CRAP. I have to do a bit more research on utilizing this mod to our benefit but I an rather excited that this mod will work for us.
I've downloaded the file again and everything went ok.
May be the first download file was corrupted due to the slow transfer.
The errors that occurred when selecting Spanish language were resolved.
Anyway, there is an issue with bluetooth.
I can send files to other devices, but I cant receive with the VP7e, when I try to send some file, the VP7e don't show the popup window asking permission to receive file.
Is like it's denied by default.
Does somebody successfully tried to send/receive files with bluetooth ?
Thanks !
PAD
Hi again,
my problem is as followed,
Recently rooted my Galaxy N7000 and replaced firmware with IMilkas ICS Tablet version.
Now my problem is I want to get rid of it yet the USB is not recognized by my Windows computer.
I am unable to use Mobile Odin as it will crash instantly also unable to use Odin via PC due to my phone not being recognized.
So any help would be great !
______________________________________________________
FIXED
I downloaded via the app store an app called "Airdroid" which allows you to move files from your pc to your phone whilst both devices share the same Network!
Moved a new Rom onto my phone and rebooted it into Recovery mode
> Install Zip from SDcard located my main file and installed it.
applied the update the same way, after restarting ,it threw a bunch of random error messaged around so I used the app CWM which comes with the ROM
option : FLASH KERNEL
located same rom as before and installed it with CWM followed by a reboot I used the option Flash Update in CWM and updated Griskelo Rom .
SO thank god it worked no error messaged and my USB works again so Odin can get back to work
Most likely there is a much easier way but this is what I figured out myself and as this forum says before you sign up... You are a noob any ways !
lol
hope I helped somebody with this and hope someone else posts the easier way beneath this
Code:
**** DISCLAIMER ****
This post is an EXPERT-LEVEL Post.
I am NOT RESPONSIBLE for what you do to your device.
Please not that I am still working on a solution to this brick.
Hello XDA-Developers,
I recently got my hands on a Meizu M3 note and, of course, wanted the newest - nougat - firmware on it. It seems I accidently flashed a incompatible (or currupted) Update (flashed an A Firmware on a G version phone). Sadly it broke down and showed only vertical stripes on it's display.
Image here: https://ibb.co/cpGunm
After some hours research I found some information on how to reflash the M3 note via SP Flash Tool here and here. Since the first tutorial is for the M3 and M3s and the second tutorial is for the M model of the device (I've got the L model) there are some changes needed for it to somehow magically work.
I exchanged files provided (such as preloader.bin, lk.bin etc) with the matching ones from the latest Official Global Firmware from Meizu. Just extracted them out of the update.zip. (Don't forget to select the Authentication File!)
Image here: https://ibb.co/k3zYDR
Short flashing tutorial: make sure your device is turned off and disconneced then click "Download" and connect your device via USB. Don't worry if it now shows an error like "Download DA Failed", just dismiss the error and click "Download" again. It should flash the device now.
Sadly it is not possible to flash the boot.img provided in the latest official update.zip from Meizu (you'll get an security mismatch error). BUT the boot-verified.img provided by the chinese archive is flashable and is accepted by the device. The device is now in a bootloop, fastboot is accessible via holding Vol - and Power, but no recovery access via Vol+ and Power
The files seem to be repaired now but the display still shows these stripes - I think the firmware actually fried something on the display chipset. I bought a replacement screen and then will update this thread as soon as possible. If you have any Ideas of how to unbrick the device feel free to discuss.
Update 18.11.2017
Thanks to @ncristian !
I did as he suggested, downloaded and flashed the files from the russian forum here (if you do not speak russian and want to get straight to the point: Direct Download Link)
I still have the stripes on my screen but the device booted up successfully and got recognized again by my computer! While booting up I could see the stripes changing their color slightly as the bootanimation of flyme was playing. I guess I will have to replace the screen to make the display error go away... I will update this post as soon as I did so
Update 10.11.2018
Sadly I never actually exchanged the screen, I'm running a Pro 7 Plus as a daily driver now and I'm loving it
Update 19.05.2019
I have attached the boot-verified.img as someone requested it
I had the same problem and I solved thanks to this: https://4pda.ru/forum/index.php?showtopic=739028&st=24480#entry65580668 and Google Translate; I downloaded the .zip, installed drivers, launched the flash tool and flashed files contained in the folder L691H (Remember to install drivers and disable antivirus or it will not work). Then I downloaded FlyMe 6.1.0.0G, went into recovery with vol up + power, copied the update.zip into the device "Recovery" and flashed it; the only problem I had is that the phone charged but he didn't recognize the battery level; by reflashing the files contained in the 4pda .zip, the battery level went up (obviously, after leaving the phone charging for about an hour).
Someone please help my meizu m3 note bricked after flashing flyme 7.8 beta.
Rajdas26 said:
Someone please help my meizu m3 note bricked after flashing flyme 7.8 beta.
Click to expand...
Click to collapse
Try reflashing via the original recovery, that might be your easiest solution. If that doesn't work you might try your luck with something like SP flash tool
Hey. Uhmm i know it's an olld post but i'm hopeless now. I need the boot-verified img you have. i can't find it anywhere. can you send it to my gmail ?? [email protected]
shawn_mendes said:
Hey. Uhmm i know it's an olld post but i'm hopeless now. I need the boot-verified img you have. i can't find it anywhere. can you send it to my gmail ?? [email protected]
Click to expand...
Click to collapse
I have attached the file to the first post. Good thing I never delete anything :angel:
m3shat said:
I have attached the file to the first post. Good thing I never delete anything :angel:
Click to expand...
Click to collapse
First of all, thank you mate I successfully downloaded the boot verified. But still it didn't turned on. Just no power but recognized by the sp tool. I'm starting to think that downloaded again the wrong firmware. I also found out that their are two main board(or whatever is that). So this global firmware can be flashed in the both L and M series. I'm wondering what firmware you used to flash. Again, thank you in advance ^_^
l got same problem .. (because I'm not read careful )l tired to flash using many firmware or using boot verified .. i tired that for 2 Days.. So l give up.. take my device to profesional service . and solved. solved with Emmc repair ..
my device is L681H.
Hi guys,
Hope it's ok if I start this thread, I just wanted to give new users some feedback before/ after unlocking and flashing an India ROM on my sealed China ROM K20 Pro (8/256). It might be useful to some, or maybe even help others. Thanks a lot to Robbo.5000, Madsponge and Hursty UK (hope I got it right?) among others for their help and advice.
- [BUYING PROCESS] My trip with the K20 Pro started here: https://forum.xda-developers.com/k2...ice-to-buy-t3939616/post79918346#post79918346 (about 18 days to get it from China during high season, not too bad I guess). (FYI, the real Global version will come out in Europe in a few weeks but the 8/256 won't be available here.)
- [UNLOCKING PROCESS] I then started the "infamous" unlocking process which triggered the even more "infamous" unlocking wait time. Why did Xiaomi choose to do that? Pretty strange if you ask me. Why should you wait 5 days or more? Anyways, in my case it was almost 6 days. That part of the process went smoothly (I run a kinda old Windows 7 PC). I rebooted the phone and it was unlocked indeed. Then started the stressful process: flashing a +400 euros phone without knowing if it would actually work. Kinda reminded of the time when we "backuped" PS1 (PSX) games, haha.
- [FLASHING PROCESS] I used the official MiFlash tool, with the official India ROM (fastboot file, .TGZ extension). First problem : MiFlash couldn't install the drivers because a /log/ folder was missing, which I had to create manually (didn't see that mentioned on the forum, but might be my OS? Oh well). The rest was OK until I launched the flashing process and hit the "clean all" button (I carefully didn't choose the clean all and lock which would have bricked the phone).
>> Link to the official India ROM Fastboot .TGZ -> http://bigota.d.miui.com/V10.3.3.0....FKINXM_20190711.0000.00_9.0_in_a1c0a15dec.tgz
>> Link to the official MiFlash tool I used -> https://xiaomiflashtool.com/download/xiaomi-flash-tool-20181115
>> Use the official Xiaomi USB-C cable - do not try another USB cable
>> Important reminder: please change the default option in the flashing tool and DO NOT choose "clean all and lock". Change it to "clean all" only (you don't want to lock it as you might brick it - see posts below about this)
- [STRESSFUL REBOOT] The flashing process ran for about 10 minutes, said "error: Not catch checkpoint (\$fastboot -s .*lock)". Needless to say I was very stressed out at that point, especially with the not cool red message "error" on the right of the tool, in the column "result". I thought the phone was bricked...but no, it just rebooted normally with the India ROM on it. Honestly I don't know what happened, if it was normal or something but I didn't see anyone mentioning this.
Some feedback post flash: everything is fine, the phone seems even faster than on China ROM but it might be just an impression. I do not like the POCO launcher at all, when you're used for 4 years with the classic MIUI launcher it's honestly a pain, I like to see all installed apps on the home and next screens. I had an issue with my Mi Cloud backup (home screen): Mi Cloud said there was no backup even though I did one just before flashing. The rest of the sync process (except home screen - maybe because of POCO launcher?) was fine though: pics, notes, calls, messages, etc. Too bad we're missing NFC but it feels good to be back on "Global" (was coming from a Mi 8 Global phone). Oh yeah, missing the multiple shots option from the China ROM (where you can choose the "best" shot), but it will come to Global one day I guess.
- [MI CLOUD BACKUPS] I can confirm the Mi Cloud home screen backup issue described above is indeed because of the POCO launcher: my previous backups didn't have it (Mi 8 Global, K20 Pro China) and so Mi Cloud couldn't restore from those backups. I now have a POCO launcher backup (daily in Mi Cloud) and I can restore from those. So keep that in mind: if you come from non POCO you won't be able to restore home screen, but same thing if you move from POCO to a non POCO launcher. If you're not familiar with those backups, it's very practical (usually...) when you change phone because you just have to restore it and you'll have all your icons, apps and stuff like before.
[UPDATE] As you might know, a European Global version will be released in a few weeks, let's see if it has the POCO launcher or not.
Thanks again all for the help and let me know if you have more feedback.
Thank you for posting this - i am trying to get thru the steps too.
I too had Miflash tell me a file/folder was missing - after i created the /log folder it got past and said install was done (in chinese) and that log folder now has a txt matching what the window was searching for.
I tried pointing MiFlash to the folder with the ROM with a TGZ extension but it said 'couldn't find flash script'. After some reading apparently we have to extract it ? i did that ang got TAR - MiFlash still did not recognise and still gave me the same error message.
Any ideas?
Also, does it matter if Windows recognise the phone as a Phone? What's the USB connection type you set?
hippo2s said:
Thank you for posting this - i am trying to get thru the steps too.
I too had Miflash tell me a file/folder was missing - after i created the /log folder it got past and said install was done (in chinese) and that log folder now has a txt matching what the window was searching for.
I tried pointing MiFlash to the folder with the ROM with a TGZ extension but it said 'couldn't find flash script'. After some reading apparently we have to extract it ? i did that ang got TAR - MiFlash still did not recognise and still gave me the same error message.
Any ideas?
Also, does it matter if Windows recognise the phone as a Phone? What's the USB connection type you set?
Click to expand...
Click to collapse
You need to fully unpack the ROM. It requires unzipping twice. You now need to extract everything from the tar file. After extracting the tar file you should have a folder with all the ROM image files and some .bat files. Point the Mi Flash Tool to this folder.
The phone needs to be booted into fastboot mode. The PC should recognise the phone automatically if it has all the correct drivers installed.
ive been using the indian rom for like 2-3 weeks now, my question is, does it support auto updater trough the updater? or we need to install back trough the mi flash tool
i failed multiple times to flash the global india rom before(using winzip to extract). and I tried again extract the files using winrar and it succeed. i'ved been using it almost 2 weeks now. the issue that i am facing is i cant use earphone mic on discord and whatsapp call. the rest is fine. for the updates, i get it from system app updater in settings.
OK - Managed to get the image folder recognised - the file path was too long - so i renamed it and moved it closer to where the miflash .exe was.
Now MiFlash is not detecting my device - when plugging in phone windows comes up with a 'USB device not recognised' message as well.
In Device Manager it says Unknown USB device (Invalid Configuration Descriptor) - I looked for Xiaomi usb drivers but Windows say i already have the best driver installed...
Any ideas?
hippo2s said:
Thank you for posting this - i am trying to get thru the steps too.
I too had Miflash tell me a file/folder was missing - after i created the /log folder it got past and said install was done (in chinese) and that log folder now has a txt matching what the window was searching for.
I tried pointing MiFlash to the folder with the ROM with a TGZ extension but it said 'couldn't find flash script'. After some reading apparently we have to extract it ? i did that ang got TAR - MiFlash still did not recognise and still gave me the same error message.
Any ideas?
Also, does it matter if Windows recognise the phone as a Phone? What's the USB connection type you set?
Click to expand...
Click to collapse
I forgot to mention it, yes you do have to extract it (using WinRAR or similar) until you get an actual folder like Robbo.5000 said. I then renamed the rom's parent folder as "raphaelin" because another user mentioned we could have issues if the folder's name was too long.
About the USB connection i didnt change anything, i left it by default.
hippo2s said:
OK - Managed to get the image folder recognised - the file path was too long - so i renamed it and moved it closer to where the miflash .exe was.
Now MiFlash is not detecting my device - when plugging in phone windows comes up with a 'USB device not recognised' message as well.
In Device Manager it says Unknown USB device (Invalid Configuration Descriptor) - I looked for Xiaomi usb drivers but Windows say i already have the best driver installed...
Any ideas?
Click to expand...
Click to collapse
I'm guessing your phone is already in fastboot mode (with the little Mi cartoon guy)?
I installed ADB minimal, the MiFlash drivers but also ADB Lite drivers (mentioned in the big Madsponge thread where you can find the links). That might help.
In MiFlash when i hit Refresh it saw the phone as some ID like 1d23456 or something.
Just installed Qualcomm drivers - didn't help either...
set USB debugg mode - what was the USB connection type? if you remember - thanks in advance
piqiee said:
ive been using the indian rom for like 2-3 weeks now, my question is, does it support auto updater trough the updater? or we need to install back trough the mi flash tool
Click to expand...
Click to collapse
I dont think there is an update since 10.3.3.0 but i guess we'll find out with the next OTA update. I read somewhere an automatic update might lock the phone back (and brick it) so i disabled them for now, until we know more...
Of course Chinese OTA was fine on the China ROM.
hippo2s said:
Just installed Qualcomm drivers - didn't help either...
set USB debugg mode - what was the USB connection type? if you remember - thanks in advance
Click to expand...
Click to collapse
In fastboot mode you cant change it on the phone if i remember, and its set automatically in file transfer mode i think.
Yes I installed those drivers too. I might try a different laptop and usb cable tonight.
Thank you so far for your help.
FYI i used the USB cable shipped with the phone. As for the laptop, is its OS up to date? I installed the latest Windows update before the flashing process.
Hope its gonna work!
DontDamnMe said:
FYI i used the USB cable shipped with the phone. As for the laptop, is its OS up to date? I installed the latest Windows update before the flashing process.
Hope its gonna work!
Click to expand...
Click to collapse
I own the Indian variant, stock rom, bootloader unlocked and rooted. Widevine L1 is still present.
So, I am curious. When you flashed the Indian ROM, did your Widevine level changed from L3 to L1?
If you didn't check, if you don't mind, please install "DRM Info" from playstore and let me know!
I am trying to find whether the Widevine is implemented based on Stock ROM level or its just at device variant level. Thanks in advance!
theincognito said:
I own the Indian variant, stock rom, bootloader unlocked and rooted. Widevine L1 is still present.
So, I am curious. When you flashed the Indian ROM, did your Widevine level changed from L3 to L1?
If you didn't check, if you don't mind, please install "DRM Info" from playstore and let me know!
I am trying to find whether the Widevine is implemented based on Stock ROM level or its just at device variant level. Thanks in advance!
Click to expand...
Click to collapse
I just checked and it says I have L3. Honestly I don't really see a difference (if it's about Netflix HD or not), Netflix videos are still great quality.
DontDamnMe said:
I just checked and it says I have L3. Honestly I don't really see a difference (if it's about Netflix HD or not), Netflix videos are still great quality.
Click to expand...
Click to collapse
Thanks mate. Just one more thing. Could you play "Test Patterns" - S1:E1 video, zoomed out for 2 mins, in Netflix app?
It will initially show "960x540" (right top corner of the screen in zoomed out mode), but after 2 mins, does it change to "1280x720" or still stays at "960x540"??
Again, thanks in advance!
Ok it was the USB cable - device was detected on original USB cable.
Flashed - BUT i made a mistake and had it default to Clean all and Lock !!! ugh...
Flash went thru - but now i am in some thing called Redmi-Recovery 3.0. Red message say "This MIUI version can't be installed on this device."
I can still get into Fastboot and MiFlash can still detect the device - Upon trying to reflash again MiFlash gives error 'Erase Boot Error'
So i think i am F-ed....
Any advice, anyone?
I think its only "soft bricked". Another user had a similar issue and created a thread below. Experts here will be able to help you for sure. If its locked i believe you have to reinstall the China stock ROM.
About Netflix it stays on 960, so no HD i guess...
hippo2s said:
Ok it was the USB cable - device was detected on original USB cable.
Flashed - BUT i made a mistake and had it default to Clean all and Lock !!! ugh...
Flash went thru - but now i am in some thing called Redmi-Recovery 3.0. Red message say "This MIUI version can't be installed on this device."
I can still get into Fastboot and MiFlash can still detect the device - Upon trying to reflash again MiFlash gives error 'Erase Boot Error'
So i think i am F-ed....
Any advice, anyone?
Click to expand...
Click to collapse
Just download the china latest stock rom or china latest dev rom (recovery rom will be enough), no need of mi flash.
Then go to this link and follow the instructions. Since you can access the recovery, you are fine mate.
PS: Use the latest official Mi Assistant app from the MIUI site, not the one given in the link above. But the steps are the same.
Thanks guys I will try. Really worried that phone doesn’t shut down it keeps going into recovery (doesn’t power off) and charging doesn’t seem to work in all these conditions.
Will work quickly
---------- Post added at 12:15 PM ---------- Previous post was at 12:04 PM ----------
err... thats not the Mi PC Suite is it? when i google miphone assistant thats what comes up...
Err...not detecting my phone so the PC Suite can't find the device
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.