[Q] Where do I go from here? - Eee Pad Transformer Q&A, Help & Troubleshooting

I have a Transformer TF101 US and I have rooted it, I installed recovery, but whenever I try to install a ROM it just sits on the splash screen and loops forever. I was able to install a rooted stock ROM and I just left it at that, but the launcher crashes and I have to restart. It reboots randomly and I was having problems with the market not processing my requests. I had an old recovery so I thought that might be the problem so I installed roach's recovery 5.5.0.4 r2 and it installed but no change on the status of the ROM when I reflashed them. Now I can only access the internal SD card with the recovery but only have access to the external SD card due to the looping ROM. What's my next step?
The ROM I've been trying to install is the new CM9 nightly. I have tried to install other in the past but the looped too. Other people have had success with installing it. Why doesn't it work for me?
Thanks
-Munchi3s

If you need access to the internal SD, plug your TF into the computer and use 'adb push' to send the files you need to flash to it, or if you can get far enough into usb mode just drag and drop.
Also make SURE to 'wipe cache' when flashing anything, and factory wipe/wipe script if the Rom requests it.
You can also try flashing a custom kernel or a rom which includes one with fixes to help with reboots. Guevor's test kernels and the Tastymehics kernels are good for this.

Minor problem with that
Thanks for the reply, but that's what I tried first too. On windows ADB dosn't see my device in recovery mode and the drivers from ASUS wouldn't fix it. Next I tried ADB on my ubuntu machine and it shows something on the ADB devices but it says
??????????????? no permissions
If I try to push anyways it tells me there is a problem with permissions

Ok. You were right. Wiping the cache fixed up everything. The ROM booted normally and no other problems to date. Thanks for your help.
-Munchi3s

Related

[Q] TF101G bricked??? unable to restore backup!

Hey everybody!
I have some serious issues here.... Today I wanted to flash my TF101G (german version) from the HC to the ICS version of the Revolver Rom. Of course I made a backup as usual before getting to work. I also flashed to the newest version of CWM recovery, as recommended.
Unfortunately it seems that something went wrong.... During start-up the ASUS splashscreen appears but nothing else happens (bootloop?). At first I though that doesn't matter, because I could just restore the previous backup. But when I got into CWM recovery, I had to find out that this new fancy touch crap version is not able to access the external sd-card of my Transformer! So I'm not able to restore anything or install any ZIPs...
Next thing I tried was to flash either the ROM or the recovery (downgrade for sd-card access) via NVFlash. So I installed the driver, got into APX mode, but nothing happens. Well actually not nothing but instead, depending on which batchfiles I use, it either just kicks me out of APX mode (driver is not shown in the devicemanager anymore) or I get the error message "bla bla bla... command send failed (usb write failed)"
And now I ran out of ideas....
Can you still get into clockworkmod recovery touch? If you can try using the ADB from there to 'adb push rom.zip filepath/filepath' to get it onto your Internal SD and then reflash from there. I just use cwm 3.2, it's rock stable and never gives me issues, and after reading all of the issues with new versions and lack of ext SD support I refuse to update.
Darth Valda said:
Hey everybody!
I have some serious issues here.... Today I wanted to flash my TF101G (german version) from the HC to the ICS version of the Revolver Rom. Of course I made a backup as usual before getting to work. I also flashed to the newest version of CWM recovery, as recommended.
Unfortunately it seems that something went wrong.... During start-up the ASUS splashscreen appears but nothing else happens (bootloop?). At first I though that doesn't matter, because I could just restore the previous backup. But when I got into CWM recovery, I had to find out that this new fancy touch crap version is not able to access the external sd-card of my Transformer! So I'm not able to restore anything or install any ZIPs...
Next thing I tried was to flash either the ROM or the recovery (downgrade for sd-card access) via NVFlash. So I installed the driver, got into APX mode, but nothing happens. Well actually not nothing but instead, depending on which batchfiles I use, it either just kicks me out of APX mode (driver is not shown in the devicemanager anymore) or I get the error message "bla bla bla... command send failed (usb write failed)"
And now I ran out of ideas....
Click to expand...
Click to collapse
You 101G is NOT nvflash compatible. You don't have SBK v1.
The only thing you can try is ADB push the necessary files to the internal sd storage.
I couldn't connect my device via ADB before, but after trying a few things it works now.....
But ADB really gave me a hard time! In the beginning I pushed some testfiles. First they were pushed but somehow they did not appear in specific folders on the sd-card in CWM. Others just gave me the message "protocol error".
After restarting the deamon and remounting the sd-card I was finally able to push an older version of CWM and the ROM file. Then I just wanted to restore my old backup via CWM, but I ended up hanging at the ASUS splashscreen again. Only reflashing the ROM itself solved it in the end.
THX
Darth Valda said:
I couldn't connect my device via ADB before, but after trying a few things it works now.....
But ADB really gave me a hard time! In the beginning I pushed some testfiles. First they were pushed but somehow they did not appear in specific folders on the sd-card in CWM. Others just gave me the message "protocol error".
After restarting the deamon and remounting the sd-card I was finally able to push an older version of CWM and the ROM file. Then I just wanted to restore my old backup via CWM, but I ended up hanging at the ASUS splashscreen again. Only reflashing the ROM itself solved it in the end.
THX
Click to expand...
Click to collapse
Good to hear you got it working. Just a little FYI for the future.
Nandroid restore does not restore the kernel so next time just flash the ROM before or after the nandroid restore. That should put the correct kernel in place for it to boot up.
Did you try reflashing an earlier kernel? Those backups haven't been designed to store/restore kernel data (for us anyway). I think I had a similar experience, back when I was trying early AOSP ICS.
Hey! Thanks for the heads up, everybody!
I always thought that the nandroid backup restores everything (e.g. ROM, settings, base, kernel, etc.). That explains why the restore after the screwed up update to ICS didn't work anymore and why I got stucked in a bootloop again.
So even that seems not to be the last line of defense if you brick your device....

[Q] Is it bricked

I tried to go back to a stock rom and unroot my device by using the steps on the forum. What i have now is the unit comes on the asus logo shows but when it tries to boot up the screen is just black nothing happens. If i try to use an sd card with any thing on it doesn't read it. None of the files from the card show up in the menu. if have cleared the cache tried using the backup image that was on the device when i got it but still nothing. If you can help I would be grateful. I'm a noob to this rooting stuff. The only reason i brought it rooted was because of the price, I could not pass it up but after not getting some of the apps that i wanted to work if assume a rooted device is not for me.
jflynn0 said:
I tried to go back to a stock rom and unroot my device by using the steps on the forum. What i have now is the unit comes on the asus logo shows but when it tries to boot up the screen is just black nothing happens. If i try to use an sd card with any thing on it doesn't read it. None of the files from the card show up in the menu. if have cleared the cache tried using the backup image that was on the device when i got it but still nothing. If you can help I would be grateful. I'm a noob to this rooting stuff. The only reason i brought it rooted was because of the price, I could not pass it up but after not getting some of the apps that i wanted to work if assume a rooted device is not for me.
Click to expand...
Click to collapse
What instructions did you follow? Is the bootloader unlocked and can you boot into it? Does adb work? Need more info if we're going to help you.
It is rooted with
aokp-tf300t-build-38.
Android ver 4.0.4.
Kernel 2.6.39.4 g2bf1397-dirty.
Build IMM761.
bootloader unlocked
I was looking around in cwm menu before I tried to install the stock asus rom. Just going thru the menu's looking trying to familiarize myself with cwm. I went to backup and restore menu and there was Zip there. I hit to power button instead of the volume and it starting restoring the device. After that i have not been able to get it to do anything after the asus screen. But I can get into the menu of cwm. When i tried following the adb, i go into cmd on my computer and change directory it tells me the device is not ready. I tried putting a zip on a sd card but I cant get it to show on the device to install.
Try a factory reset in CWM, see if that helps.
tried the wipe data/factory reset several times with no luck. It goes through the process but still does not boot to any thing after asus logo.
jflynn0 said:
tried the wipe data/factory reset several times with no luck. It goes through the process but still does not boot to any thing after asus logo.
Click to expand...
Click to collapse
Can you flash a different ROM, maybe the stock one?
Had the same problem. Tried to flash stock from Twrp recovery.
Wipe do a factory reset, wipe system and than flash the aokp rom again.
Then reboot and when you are back in System you can put the rom you like on your internal SD.
Back to Recovery and flash the new rom.
I got adb working and it come up in devices list. How do i flash the aokp rom on the device. I'm learning this as i go along, after this i might get the hang of this . I cant seem to push files using adb either my directory is wrong. I unzip it into a folder (C:\romfolder\aokp_tf201_build-38.zip/sdcard) and all that comes up scrolling page of commands and help for adb when i push
this is the zip i dwl could not find built 38 for tf300 so i got tf201
http://aokp.co/index.php/releases/_/build-38-r24 also how do i make it an image to flash or can i download and image
jflynn0 said:
this is the zip i dwl could not find built 38 for tf300 so i got tf201
http://aokp.co/index.php/releases/_/build-38-r24 also how do i make it an image to flash or can i download and image
Click to expand...
Click to collapse
Do not flash a 201 rom or image. Thats for the prime. Never flash roms designed for another device no matter how similar they are.
ok I downloaded this on
http://goo.im/devs/termleech/tf300t/aokp_tf300t_unofficial_20120617_2100_build-39.zip
have to go to bed but when i get up this afternoon will try to get it o go to device.
How am I suppose to get it to the device if the sd card does not show up on file list in cwm?
Can you still use ADB? You can always push the files with that.
how do i use adb to push the file on to the device itself. because i can add it to the sdcard by just putting in on there and then placing sdcard in device but the menu as far as install zip from sdcard never shows any zips that are on the card itself. Only thing that shows up are list of directories that look like a standard list from cwm. Also if you choose any of directories from that list it returns no file found. If I choose apply update on sdcard no matter how many time i have called the file update.zip says "no such file or directory install aborted". Or how do i push and image to the restore section of the device and where do i find an image at?
well still no luck. I think I will give it a few more days and if I still cant get it guess will go to best buy and buy another on. Any thoughts on Toshiba excite?
Try this i posted a tutorial on how to fix this http://forum.xda-developers.com/showthread.php?t=1738825 hope it helps

Bootloop, no ADB, no APX

Hello friends,
So I wanted to switch my TF101 to Cyanogenmod this weekend. I've been using Revolver, but with other devices on CM, I wanted some consistency in the experience among my devices.
I started by updating my Clockworkmod Recovery version. Flashing the latest 6.0.1.3 version caused problems with Install Zip from Sdcard, for some reason. So I downgraded to the 5.8.3.4 Touch version. Now Recovery works, but I cannot utilize adb reboot-recovery (it reboots system), Reboot System Now from CWM (it reboots recovery), or manually power off to reboot system (it reboots recovery). I can manually reboot back to system by Power+Vol Down and letting it cold boot, but this is less than ideal.
Here's my big problem. I went ahead with trying to flash CM anyways. I booted into the recovery, with the CM zip on my sdcard partition. I wiped cache and data, flashed the sdcard, and then tricked my tablet into cold booting (sigh). Then I waited. CM's logo spun around, and around, and around...and did this for the better part of an hour.
So I tried flashing it again. Same problem. I would have tried flashing back to Revolver, but apparently the new CWM looks for my internal partition rather than my microSD card, and that's where Revolver is stored. Bad luck there.
I went hunting for some unbricking tools. I got the tablet into APX mode once, and got my computer to recognize that something was there. But by the time I'd installed the drivers, Windows wouldn't recognize that anything was connected. So I can't use any APX tools.
tl;dr: Here's my problem:
Bootlooping ROM
Recovery Access (CWM Touch 5.8.3.4)
No ADB access
No APX access
jordanjay29 said:
Hello friends,
So I wanted to switch my TF101 to Cyanogenmod this weekend. I've been using Revolver, but with other devices on CM, I wanted some consistency in the experience among my devices.
I started by updating my Clockworkmod Recovery version. Flashing the latest 6.0.1.3 version caused problems with Install Zip from Sdcard, for some reason. So I downgraded to the 5.8.3.4 Touch version. Now Recovery works, but I cannot utilize adb reboot-recovery (it reboots system), Reboot System Now from CWM (it reboots recovery), or manually power off to reboot system (it reboots recovery). I can manually reboot back to system by Power+Vol Down and letting it cold boot, but this is less than ideal.
Here's my big problem. I went ahead with trying to flash CM anyways. I booted into the recovery, with the CM zip on my sdcard partition. I wiped cache and data, flashed the sdcard, and then tricked my tablet into cold booting (sigh). Then I waited. CM's logo spun around, and around, and around...and did this for the better part of an hour.
So I tried flashing it again. Same problem. I would have tried flashing back to Revolver, but apparently the new CWM looks for my internal partition rather than my microSD card, and that's where Revolver is stored. Bad luck there.
I went hunting for some unbricking tools. I got the tablet into APX mode once, and got my computer to recognize that something was there. But by the time I'd installed the drivers, Windows wouldn't recognize that anything was connected. So I can't use any APX tools.
tl;dr: Here's my problem:
Bootlooping ROM
Recovery Access (CWM Touch 5.8.3.4)
No ADB access
No APX access
Click to expand...
Click to collapse
Reconnect tablet into APX mode, if u have installed all drivers laptop should recognize your tablet in APX mode... once in apex, use easy flash
Sent from my Transformer using xda app-developers app
You didn't read, clearly.
No worries, I got this unbricked by following this guide: http://www.transformerforums.com/fo...overy-bootloop-fix-tested-my-c10-windows.html

Here's How I Bricked My TF300T

Hello Forum! I've come here for a little help! Here's My Story.
After running Cyanogen 10.1 Nightlies on 4.2.2 for quite some time, I decided to do a factory reset because my TF300T seemed to be running a little slugish. I DID NOT back it up (mistake #1), DID NOT have USB Debugging on (mistake #2), and, while CWM was wiping /data, I shut off the tablet (STRIKE THREE). Prior to my bonehead move, I had everything else squared away. The unit was fully functional. Now, I'm stuck in this infernal boot loop on the ASUS screen.
I can reboot into recovery, so CWM is not compromised. I have tried to push a new ZIP of the ROM via ADB (unsuccessful, thinking the drivers are nerfed) and through CWM (also unsuccessful).
If anyone has any ideas, please feel free to comment.
P.S. Please don't kill me Mods, I'll be good after this
Update:
After looking through the forums more I tried all of these:
Installed the Universal Naked Driver (Sorta Worked)
Reflashed the system blob from the most recent CyanogenMod Nightly (Says it wrote, I doubt it did)
Went into CWM, tried to Sideload the CM zip (Didn't work)
Then, I took my external SD, placed the CM zip onto it, rebooted the tablet w/ the SD in it, booted into CWM, TRIED a full system wipe (couldn't mount /data), and reflashed the ROM. That worked! ... sorta. Upon "successful install", I had CWM reboot the TF300T. It came to the ASUS Screen w/ a progress bar (went from 1% to 100% within a second). However, after that, it went back to the bootloop ASUS screen
I feel like I'm close on this one, any tips?
Kazman101 said:
Update:
After looking through the forums more I tried all of these:
Installed the Universal Naked Driver (Sorta Worked)
Reflashed the system blob from the most recent CyanogenMod Nightly (Says it wrote, I doubt it did)
Went into CWM, tried to Sideload the CM zip (Didn't work)
Then, I took my external SD, placed the CM zip onto it, rebooted the tablet w/ the SD in it, booted into CWM, TRIED a full system wipe (couldn't mount /data), and reflashed the ROM. That worked! ... sorta. Upon "successful install", I had CWM reboot the TF300T. It came to the ASUS Screen w/ a progress bar (went from 1% to 100% within a second). However, after that, it went back to the bootloop ASUS screen
I feel like I'm close on this one, any tips?
Click to expand...
Click to collapse
I would try to install TWRP recovery since CWM is sometimes a bit flaky, I would use TWRP 2.3.3.0 since I believe is the most stable but you can install the latest one 2.4.4.0, then flash the blob file via fastboot (instructions are at the twrp site) and repeat the same process as you did with CWM, wipe everything and then flash CM.zip from external SD and see if it works that way. If that does not work, try reflashing the stock system blob from Asus this time using fastboot and that will put you completely stock and then you can start over.
hope it helps.
Erik
ricco333 said:
I would try to install TWRP recovery since CWM is sometimes a bit flaky, I would use TWRP 2.3.3.0 since I believe is the most stable but you can install the latest one 2.4.4.0, then flash the blob file via fastboot (instructions are at the twrp site) and repeat the same process as you did with CWM, wipe everything and then flash CM.zip from external SD and see if it works that way. If that does not work, try reflashing the stock system blob from Asus this time using fastboot and that will put you completely stock and then you can start over.
hope it helps.
Erik
Click to expand...
Click to collapse
It Unbricked!
Step 1: Flashed TWRP 2.4.4.0 blob file to overwrite CWM (Check)
Step 2: Factory Reset and Wipe Entire Device (CHECK!?!?!)
Step 3: Flash CM.zip!?!?! (Not So Check ... PLAN B!)
Downloaded Chinese Stock system blob (don't ask, I know it was stupid, but go with me here)
Flashed the system blob (after 3 minutes ... SUCCESS!)
No more boot loop and back to stock ... now to root it again to get my sweet CyanogenMod back ...
Thank you Erik, your help was much appreciated!

[Q] Only fastboot accessible to flash / restore my TF700

Hello,
My TF700 was on a CleanRom (2.3 i think), for a while, i decided to update.
- I installed the latest CWM (via fastboot) and flashed a Cyanogen 10.2 "stable", but my tablet freezed very quickly after successful boot, i tried some reboots and get same problem.
- I tried to install a stock ODEX root ROM, the tablet freezed at asus logo
- I flashed TWRP instead of CWM, it doesn't helped
- I tried wipe data and cache with TWRP, then my data was not accessible anymore and TWRP was unable to re-create it
- I searched on forums and found on this one that flash a boot.blob file can solve the problem
- It doesn't and now CWM and TWRP refuse to work ....
So i post here before getting my tablet completely brick.
At this point, i get access to fastboot / abd, CWM load but don't work (reboot when trying to do something), TWRP don't load.
Any suggestion to get back to a Stock ODEX rooted rom ?
Excuse my english ...
Asphodele said:
Hello,
My TF700 was on a CleanRom (2.3 i think), for a while, i decided to update.
- I installed the latest CWM (via fastboot) and flashed a Cyanogen 10.2 "stable", but my tablet freezed very quickly after successful boot, i tried some reboots and get same problem.
- I tried to install a stock ODEX root ROM, the tablet freezed at asus logo
- I flashed TWRP instead of CWM, it doesn't helped
- I tried wipe data and cache with TWRP, then my data was not accessible anymore and TWRP was unable to re-create it
- I searched on forums and found on this one that flash a boot.blob file can solve the problem
- It doesn't and now CWM and TWRP refuse to work ....
So i post here before getting my tablet completely brick.
At this point, i get access to fastboot / abd, CWM load but don't work (reboot when trying to do something), TWRP don't load.
Any suggestion to get back to a Stock ODEX rooted rom ?
Excuse my english ...
Click to expand...
Click to collapse
Hey Your in the right place
Shoot me an email, we can review your issues and if we find a solution we can post back here to help
XDA users with there issues....
My email is everywhere talke a look around
Thx Josh
Asphodele said:
Hello,
My TF700 was on a CleanRom (2.3 i think), for a while, i decided to update.
- I installed the latest CWM (via fastboot) and flashed a Cyanogen 10.2 "stable", but my tablet freezed very quickly after successful boot, i tried some reboots and get same problem.
- I tried to install a stock ODEX root ROM, the tablet freezed at asus logo
- I flashed TWRP instead of CWM, it doesn't helped
- I tried wipe data and cache with TWRP, then my data was not accessible anymore and TWRP was unable to re-create it
- I searched on forums and found on this one that flash a boot.blob file can solve the problem
- It doesn't and now CWM and TWRP refuse to work ....
So i post here before getting my tablet completely brick.
At this point, i get access to fastboot / abd, CWM load but don't work (reboot when trying to do something), TWRP don't load.
Any suggestion to get back to a Stock ODEX rooted rom ?
Excuse my english ...
Click to expand...
Click to collapse
Sounds like you are on an old bootloader. Flash the stock rom from asus by unzipping the zip you download from their website and placing in the root folder of your micro sd and then go into rck from the bootloader menu (power + volume down whilst booting)
Or you could just flash it from recovery....
lj50036 helped me to flash a new bootloader, recovery, rom and nvflash to make it unbrickable
Not just helped he spent many times to explain me how it works and what he did.
He is very nice and this was a pleasure to talk with him, i'm happy that there's still person like that on this planet
see you !
Asphodele said:
lj50036 helped me to flash a new bootloader, recovery, rom and nvflash to make it unbrickable
Not just helped he spent many times to explain me how it works and what he did.
He is very nice and this was a pleasure to talk with him, i'm happy that there's still person like that on this planet
see you !
Click to expand...
Click to collapse
I buy a tf700 with cm 11 a few days ago i am really interessted on how this steps works. I really want to make it unbrickeable, But i dont really understand how it works. I can not enter in fastboot. at least i got cwm interface when rebooting with adb into recovery.
Can u explain how you did it?
It invovles flashing a modified bootloader and the flatline recovery and then using Wheelie to generate your nvflash blobs.
Step-by-step instructions (which you need to follow to the letter) are here:
https://www.androidroot.mobi/pages/guides/tegra3-guide-nvflash-jellybean/
Stuck in boot loop, fastboot and recovery accessible
Hello,
I'm having a similar issue and I need help! Initially my tablet was rooted with Cromi-X 5.4. Then I decided to try Crombi-KK.
Here is what happened:
- Updated TWRP recovery
- Did a full wipe as recommended
- Flashing got stuck at the Crombi-KK loading sign
- Tried to reflash but TWRP wasn't detecting data partition anymore
- Instead installed the other recommended recovery CWMR.
- Flashed Crombi-KK, it worked. Played around with it for a few days, it was wonderful, fast and responsive.
- Battery died out and when I turned it back on I got a UIDs system inconsistent error.
- I found online many recommendations to reflash so I tried to do that
- Since then I'm stuck in a boot loop. I see the initial "bios" Asus logo then it restarts over and over.
- I am able to access bootloader and recovery
I've tried reflashing the asus stock blob. I've tried wiping the data through CWMR but it starts working and then it restarts. I don't know what to do anymore, so if anyone can help me, I would really appreciate it!
Thanks
Which recovery and bootloader version do you have now?
A (for KK) outdated bootloader seems the most likely culprit.
You can try save the recovery log when you flash or grab a logcat of the bootloop, but probably it'll only tell you that the recovery cannot mount /data.
Determine that you are on the correct bootloader, if not update it. If you're lucky the tablet will start right up. If it doesn't, formatting /data is the only way I know to get it back. Not just wiping - formatting it. You will loose everything on internal SD, so I hope you have a nandroid you can restore from later.
If you use TWRP 2.7+ be aware that formatting can take more than an hour. Let it finish!
For good measure, download CROMBi-KK again, check the md5 and then flash that file.
I'm on 10.6.1.14.10 bootloader which I think is the latest one
I have 6.0.4.7 CWMR
I'm trying to format data completely but when i do it in CWMR it starts and then the tablet reboots on it's own after a couple of minutes.
How can I retrieve the logs, I never had to do it before.
Thanks for your help
Mhh, getting a little more complicated.
Your BL is ok...
What do you see in CWM when you go into Mounts and Storage? What is mounted?
The recovery logs are under Advanced > show logs.
I'm at work now but from what I remember the only thing mounted was the cache. I'll double check tonight. Do you think there's any hope or I have a brand new paper weight?
yasyas said:
I'm at work now but from what I remember the only thing mounted was the cache. I'll double check tonight. Do you think there's any hope or I have a brand new paper weight?
Click to expand...
Click to collapse
Can you fastboot flash twrp?
It's much much better than CWM, has its own terminal and will be easier to offer the correct format command.
sbdags said:
Can you fastboot flash twrp?
It's much much better than CWM, has its own terminal and will be easier to offer the correct format command.
Click to expand...
Click to collapse
So I flashed TWRP and when I go in mount/storage everything is selected except for system. Should I do a format data from the wipe menu before flashing crombi-kk again?
yasyas said:
So I flashed TWRP and when I go in mount/storage everything is selected except for system. Should I do a format data from the wipe menu before flashing crombi-kk again?
Click to expand...
Click to collapse
To be in the safe side, yes, that is what I would do. TWTRP 2.7.+ takes a long time to format and it may seem the process got stuck. Give it at least 90 minutes to finish.
Then reflash CROMBi
I'm back up and running !!!
This time installing TWRP, everything was mounted (maybe my previous flash before CWMR wasn't good), did a format data, waited until it was done, flashed latest Crombi-KK and going through setup now. Hopefully won't have the same UID issue on next shutdown. I didn't enable fsync or journaling so hopefully it won't happen again.
Thanks both of you for your help!
Good deal! Happy for you!
Rooting google pixel zl

Categories

Resources