Database Users

[Q] please help with my nexus....

I went to flash cyanogenmod 10.1.
backed up rom via clockwork.
wiped data, flashed new rom.
flashed gapps.
I think i flashed the wrong gapps
upon boot I get "setup wizard has stopped" as well as one regarding gapps.
this prevents me from using the rom. I can access the calender and clock that is all. not the settings or reboot menu.
I can access the built in storage via windows, shows up as a nexus 7.
Ok, not a big deal, I will boot into recovery via the bootloader.
That no longer works. Sits at a google screen forever
Ok, I will use fastboot via the bootloader....
That no longer works. As soon as a usb cable touches the nexus either power or pc it freezes the bootloader requires a reboot.
windows rejects the usb and states is malfunctioned and unrecognised (though it works fine in the rom)
fastboot doesn't see the device.
I've tried:
three usb cables.
windows safe mode.
different ports
uninstall/install drivers.
nexus tool kit (doesnt recognise device)
wiggling the cable as suggested
anybody got an idea how I can either get the bootloader not to freeze when using a usb cable or how to boot into some kind of recovery (which was there!!!!!)
please? :fingers-crossed:

Something seems a little off here.
Was it a gapps package for some other device? Hard to see why flashing something to /system would produce the result you got, as the (gapps) edify script would at most specify a mount of "system", not a /dev/block/ device name.
Does adb work (with the ROM booted)? If so, can you get a root shell or install .apks?
The fact that the ROM boots suggests that the bootloader is working correctly enough to load and execute the LNX (boot) image. That means that in principle you could flash (using the "dd" command) a recovery image to the boot partition from a root-privileged command line (either an adb session or a terminal emulator). Performing a regular (power button) restart would boot you into a recovery session.
Obviously, this hinges on you getting a command line somehow with your reduced-functionality ROM limping along as it is. It's not obvious to me how you will make that happen though.
I am not at all confident that this will fix the bootloader <--> USB issue without somehow reflashing the bootloader without using fastboot!. The only way this has been observed for the N7 has been with the OTA process and a stock recovery - the OTA puts an image (**note - important!** this OTA bootloader image is slightly different from the bootloader image in the factory/fastboot ROMs) into the USP partition and some magic occurs on the next boot.
Well, anyway there's some ideas. Would you mind identifying the "wrong" gapps that you used? For the life of me I can't see how it caused the symptoms you are observing...
good luck

Hi. Many thanks.
Ok.....
Gapps. I downloaded the appropriate package via the link on the Rom page. However, I flashed a jellybean package I'd downloaded for my one x. I may be naive in thinking that Gapps is Gapps no?
I deduced it was that having googled the setup wizard problem and seeing that others had had it.
Bootloader.
Again. Ive googled around and can see many have the freezing bootloader with usb issue. Some say its the cable. Some say its the pc. But it does it with the charger as well. Again this is an issue for some. not sure what to do! Works fine until the cable goes in.
Recovery.
Again I know its an issue booting recovery from bootloader. I've read you need the usb in to a pc to make it happen. Obviously that's a no go for me
Adb.
Never really used it. Used fastboot many times. I assumed you need to be able to access the developer options and activate debugging etc within the Rom to allow it to work? I can not do that. Its around 10% funtional. I can place a reminder on the calender but that's about it! No way to system settings.
Sorry if thats teaching you to suck eggs. You obviously know your stuff, just wanted to make it clear.
Ta.
Sent from my HTC One X+ using xda app-developers app

olly2097 said:
Recovery.
Again I know its an issue booting recovery from bootloader. I've read you need the usb in to a pc to make it happen. Obviously that's a no go for me
Click to expand...
Click to collapse
A normally functioning tablet does NOT require you to be plugged in to a PC in order to boot the recovery from the bootloader menu. Maybe you are saying something else here, but I trust you've tried starting the recovery without anything plugged in at all.
Unless you can get the recovery working, the only hope you have is somehow levering up what you have available to gain a privileged thread of execution. Obviously that's going to be pretty challenging.
good luck - you're going to need it.
PS: could you provide a URL to the *wrong* One X gapps download? I think the gapps bundle ships with system libraries - I want to peek at those libs to see if there are any hardcoded block device paths that might explain the queerness you observed. (I can't imagine why this would be the case, but...)

bftb0 said:
A normally functioning tablet does NOT require you to be plugged in to a PC in order to boot the recovery from the bootloader menu. Maybe you are saying something else here, but I trust you've tried starting the recovery without anything plugged in at all.
Unless you can get the recovery working, the only hope you have is somehow levering up what you have available to gain a privileged thread of execution. Obviously that's going to be pretty challenging.
good luck - you're going to need it.
PS: could you provide a URL to the *wrong* One X gapps download? I think the gapps bundle ships with system libraries - I want to peek at those libs to see if there are any hardcoded block device paths that might explain the queerness you observed. (I can't imagine why this would be the case, but...)
Click to expand...
Click to collapse
yeah, tried both ways.
The gapps I downloaded was a while ago. I've deleted it. was for 4.1.1
anyway. I....
Booted to bootloader, selected recovery, pressed power and rammed in the usb cable at the same time.
recovery
now running rom fine after flashing TW recovery via toolkit and mounting to pc.
I cant explain it. it took forever. but thank you

After 10 hours of failing finally side loaded lollipop

I've been trying to sideload the lollipop ota since yesterday and after 10 hours of failing, I've finally got it running. The problems I got during the period including adb driver errors, recovery errors, and my USB ports problem.
Here are some tips for the other if facing a lot of problem sideloading the lollipop ota zip.
-Use Windows if possible. I tried using Ubuntu but adb won't work correctly. Even sometimes it works, fastboot fails. Use Windows and install the drivers needed namely Google USB Driver. It can be found on Android official website.
-Plug your device directly to the motherboard. Etc. back USB port. My desktop defective front USB ports caused me the most time as Windows/Ubuntu won't work correctly with them. Windows shows USB malfunction.
-Custom recoveries won't work. I tried twrp and cwm. They won't work. They show incompatible build fingerprint/user release keys. Flash stock recovery. I tried wugfresh but can't figure out how to use it so I have it up and flash with adb in Windows. Of course you need to install the drivers properly.
-If adb/fastboot can't detect device in os/bootloader/sideload/recovery/whatever mode, most probably drivers aren't installed correctly. Google the problem and you'll find solutions to it. It's out there and you can find it.
-Check the index thread in the general forum for useful tools/image/utilities
-Sideloading is quite easy if you have drivers installed correctly assuming you have no hardware problems (defective USB port)
Those are most of the problems I faced when trying to sideload ota. Hope this helps those who are facing same problem as me.

ImjuzCY said:
I've been trying to sideload the lollipop ota since yesterday and after 10 hours of failing, I've finally got it running. The problems I got during the period including adb driver errors, recovery errors, and my USB ports problem.
Here are some tips for the other if facing a lot of problem sideloading the lollipop ota zip.
-Use Windows if possible. I tried using Ubuntu but adb won't work correctly. Even sometimes it works, fastboot fails. Use Windows and install the drivers needed namely Google USB Driver. It can be found on Android official website.
-Plug your device directly to the motherboard. Etc. back USB port. My desktop defective front USB ports caused me the most time as Windows/Ubuntu won't work correctly with them. Windows shows USB malfunction.
-Custom recoveries won't work. I tried twrp and cwm. They won't work. They show incompatible build fingerprint/user release keys. Flash stock recovery. I tried wugfresh but can't figure out how to use it so I have it up and flash with adb in Windows. Of course you need to install the drivers properly.
-If adb/fastboot can't detect device in os/bootloader/sideload/recovery/whatever mode, most probably drivers aren't installed correctly. Google the problem and you'll find solutions to it. It's out there and you can find it.
-Check the index thread in the general forum for useful tools/image/utilities
-Sideloading is quite easy if you have drivers installed correctly assuming you have no hardware problems (defective USB port)
Those are most of the problems I faced when trying to sideload ota. Hope this helps those who are facing same problem as me.
Click to expand...
Click to collapse
Sounds like you need you need to save what every data you can if you can through recovery to maybe an OTG adapter.. Then go ahead and Completely WIPE your Nexus. Follow the instructions and download the Android Lolipop LRX31P image, and all the other files needed to properly root your device.. Flash to Stock+Unroot, then once finished reboot and put in your email and settings, download all your backed up apps.. Then once finished, then go back to the Nexus Toolkit by Wugsfresh, and use the tool to root the device, it will put your device into Booloader/Fastboot, and let it do its thing.. Make sure you have USB debugging selected..
If you have a custom kernel on your current rom, it will not sideload.. if you made any changes, if its rooted it will not OTA.. You need to flash to Stock Android 5.0 and go through the motions.... I was on Carbon Rom 4.4.4, and went through the paces, and gave me no issue.. It just takes about 5 or so mins at first boot.. So if it seems to hang.. don't worry.. Just let it do its thing, put in your email info and there you go.. The tool is dummy proof.. even if you soft brick the device, you can use the Advanced Utilities while manually booting into Fastboot/Bootloader mode..
Edit: also make sure you have the correct ADB drivers.. The took kit has those drivers, just follow the instructions, and you should have ADB, or you can flash manually through fast boot if you select your device as soft bricked.. I had the same problem when I first tried to side load an OTA..
Good luck

Zaphodspeaks said:
Sounds like you need you need to save what every data you can if you can through recovery to maybe an OTG adapter.. Then go ahead and Completely WIPE your Nexus. Follow the instructions and download the Android Lolipop LRX31P image, and all the other files needed to properly root your device.. Flash to Stock+Unroot, then once finished reboot and put in your email and settings, download all your backed up apps.. Then once finished, then go back to the Nexus Toolkit by Wugsfresh, and use the tool to root the device, it will put your device into Booloader/Fastboot, and let it do its thing.. Make sure you have USB debugging selected..
If you have a custom kernel on your current rom, it will not sideload.. if you made any changes, if its rooted it will not OTA.. You need to flash to Stock Android 5.0 and go through the motions.... I was on Carbon Rom 4.4.4, and went through the paces, and gave me no issue.. It just takes about 5 or so mins at first boot.. So if it seems to hang.. don't worry.. Just let it do its thing, put in your email info and there you go.. The tool is dummy proof.. even if you soft brick the device, you can use the Advanced Utilities while manually booting into Fastboot/Bootloader mode..
Edit: also make sure you have the correct ADB drivers.. The took kit has those drivers, just follow the instructions, and you should have ADB, or you can flash manually through fast boot if you select your device as soft bricked.. I had the same problem when I first tried to side load an OTA..
Good luck
Click to expand...
Click to collapse
Oops you misunderstood my post. I've done sideloading 5.0 and its running now before i post this thread. This thread i created is meant to give help to those who need it. Everythings running good for me right now. I successfully flashed stock recovery through adb and after that sideloading ran smoothly. Those problem written above is those problems i faced during it and now i already solved the problem and 5.0 is already running without full wipe. Thanks anyway

ImjuzCY said:
Oops you misunderstood my post. I've done sideloading 5.0 and its running now before i post this thread. This thread i created is meant to give help to those who need it. Everythings running good for me right now. I successfully flashed stock recovery through adb and after that sideloading ran smoothly. Those problem written above is those problems i faced during it and now i already solved the problem and 5.0 is already running without full wipe. Thanks anyway
Click to expand...
Click to collapse
Because of how Lolipop handles file location, I recommend doing a complete factory reset/wipe..
But if its working for you.. Thats alright.. But Android 5.0 handles the SDcard Location in a different area.. Something to do with the multiple profile ability I believe.

Zaphodspeaks said:
Because of how Lolipop handles file location, I recommend doing a complete factory reset/wipe..
But if its working for you.. Thats alright.. But Android 5.0 handles the SDcard Location in a different area.. Something to do with the multiple profile ability I believe.
Click to expand...
Click to collapse
You mean internal storage? I dont think nexus devices have an external microsd slot. Thanks for the suggestion anyway. I will do a factory reset if problems starts to bug me.

ImjuzCY said:
You mean internal storage? I dont think nexus devices have an external microsd slot. Thanks for the suggestion anyway. I will do a factory reset if problems starts to bug me.
Click to expand...
Click to collapse
Yes internal storage.. and yes a factory reset would correct that problem..
That just defeats the whole sideload thing, where you could just do a Titanium backup first, restore Data only when needed. Just install the factory image, and restore the Titanium back up... not the app, but the Data becaus the app will crash.. Its the easiest way to save your settings in your Launcher and your apps..
Its too much trouble to sideload when your rooted, with a custom Kernel.... you wasted 10 hours, when it could of taken less than 10 mins

Zaphodspeaks said:
Yes internal storage.. and yes a factory reset would correct that problem..
That just defeats the whole sideload thing, where you could just do a Titanium backup first, restore Data only when needed. Just install the factory image, and restore the Titanium back up... not the app, but the Data becaus the app will crash.. Its the easiest way to save your settings in your Launcher and your apps..
Its too much trouble to sideload when your rooted, with a custom Kernel.... you wasted 10 hours, when it could of taken less than 10 mins
Click to expand...
Click to collapse
Luckily i was using stock kernel. Ive disabled root beforehand and the problems i faced was all on the pc side. Evrything should be easy if my pc doesnt show so much problems. And i like to take challenges so i chose to sideload haha

DJI PHANTOM 4 PRO + Custom Rom

Not sure if anyone here does drones, but there is a requirement for a custom rom for the DJI GL300E remote controller.
DJI has a drone remote controller with a built in screen called the GL300E which runs a bastardised form of Android 5.1 that has no google play store or google play services.
So we cant use third party apps that rely on those services.
How feasible would it be to engineer a custom rom that has these components installed?
I realise this is a bit of a long shot and not many folk round here will be terribly interested or know what I'm on about but I thought i'd give it a go!

I thought only me that need this .... It has been depressing hours of adb shell methods with no luck ... I think reasonable price for everyone who made the custom ROM is welcome

Up ...

Up

st10+ rooted
dorbot said:
Not sure if anyone here does drones, but there is a requirement for a custom rom for the DJI GL300E remote controller.
DJI has a drone remote controller with a built in screen called the GL300E which runs a bastardised form of Android 5.1 that has no google play store or google play services.
So we cant use third party apps that rely on those services.
How feasible would it be to engineer a custom rom that has these components installed?
I realise this is a bit of a long shot and not many folk round here will be terribly interested or know what I'm on about but I thought i'd give it a go!
Click to expand...
Click to collapse
.. I used kingroot to root the st10+ A custom rom is what im after as well just havent figured what some of the apps are for on it and there use the radios are restricted by cpu and memory to start with but at lest with it rooted there is a open door ....I will pay 100 paypal or give a nice drone 55+mph 32min fly time brushless motors for help completing the same and i can send all the files and info device is rooted now
/youtu.be/EHSIvJBIheg[/url]

https://www.youtube.com/watch?v=c-T61GKSRvk
this guy roots the controller and gets google play store working. Now you have to register your device with google as a custom Rom user.
I used deviceID.apk to find out the number google wants.

Hmm, dunno what I did but I have a soft bricked Pro Plus controller GL300E.
The DJI logo comes up but just stays stuck there. The ADB bridge from My PC still works though.
Anyone got a nandroid backup or a stock image?
Help!
lol.

I unbricked it using iroot PC software, however that seems to have installed loads of stealth adware which makes the RC unusable as a remote controller.
Also......
I was Using the Official TWRP app to experiment with a different recovery for RK3288 devices but it didnt work.
I made a backup of the stock recovery and then i made a backup of boot aswell because it seemed like a good idea. Unfortunately the filenames were hidden behind the flash now button and I think the second backup overwrote the first so I have lost my backup original recovery.img.
Could someone with a rooted GL300e take a backup of their recovery using the Official TWRP app or similar and post it somewhere so I can download it and replace the stock recovery so I can then flash the stock firmware bin file you get from DJI.
https://forum.dji.com/thread-108560-1-1.html
At the moment when I try to flash the stock firmware bin files doing a local install from the SD card, when it reboots to complete the process nothing happens, it just reboots. There is no little green android on its back with a blue progress bar, because there is no recovery installed so the process never begins. I'm getting tired of naked ladies all over the screen when I'm trying to fly my drone..... (joke)

Someone gave me a copy of the stock recovery so its all fixed.
I flashed an older firmware using the sd card and it allows me to set FCC (0.4 Watt) and boost (1.5 Watt) TX power from R/C and A/C by using the .DJI.configs hack.

dorbot said:
Someone gave me a copy of the stock recovery so its all fixed.
I flashed an older firmware using the sd card and it allows me to set FCC (0.4 Watt) and boost (1.5 Watt) TX power from R/C and A/C by using the .DJI.configs hack.
Click to expand...
Click to collapse
i try this using v.1.1.1.1 ended up with GoApp loading failure ... the one that worked was the v.1.2.0.0 and the update screen shows everytime I turn it on ... now my right stick become less responsive sometimes no response ... what am I missing

I want phantom 4 pro plus android stock firmware
I want phantom 4 pro plus android stock firmware

dorbot said:
Someone gave me a copy of the stock recovery so its all fixed.
I flashed an older firmware using the sd card and it allows me to set FCC (0.4 Watt) and boost (1.5 Watt) TX power from R/C and A/C by using the .DJI.configs hack.
Click to expand...
Click to collapse
how do i do this. i'm on stock where do i get the older firmware

please delete

Please delete

jphilpot7 said:
I have a android head unit that is running 8.1 (8227L_8腾实UI02-国外_v67_20181203.zip firmware). I wasn't able to get firmware for my device, so I had to use one that was close to the same (8227L_8腾实UI04-国外_v44_20190523.zip). Well it has been working fine for a while now without any issues, only thing was I I could not unlock the boot loader anymore, buttons wouldn't work. So yesterday I received the original firmware that the device came with that was actually older then the firmware I found that worked. Once i flashed the update, it caused the resolution to be all jacked up where I can only see half the screen and artifacts on the screen. does that sound like the DPI is jacked in the build.prop and I need to figure out away to wipe /system? I attempted to put back the newer firmware 8227L_8腾实UI04-国外_v44_20190523.zip and it also has jacked up resolution.
So usb debugging does not work, so I have a terminal emulator that I was luckly able to get installed. I can su and gain root, then reboot into recovery for fastboot.
i attempted to wipe the system partition from fastboot or adb without success. any help would be appreciated.
Click to expand...
Click to collapse
Maybe if you get a screen mirroring tool installed you can work better? I was thinking of vysor but you said usb debugging is not working. But there is an idea.
Regarding the display no idea.
Sent from my ONEPLUS A3003 using Tapatalk

dpi
I am going to try to get dpi changed with adb shell wm density 190. Also going to try to get my keyboard to work in recovery, that way I can do a real wipe of data/system and then flash firmware again. So far I have been unable to find any working commands with adb/fastboot to wipe system.

Hi
Do you still have copies off the same firmware as am having trouble with not been able to play CDs or read usb devices . Thankyou

Setting up Lineage with a broken display

Hi, I'm trying to run Android on my Switch, but the LCD is broken. The digitizer works fine, but everything beyond the far right side of the screen is unintelligible. Lineage itself works fine docked, but to install OpenGApps and/or Magisk I need TWRP. Unfortunately for me, TWRP doesn't display anything on the second screen, it's completely blank.
First, I tried installing Magisk manually. I made sense of the install script as best as I could, but the Magisk app says it's not installed. I tried TWRP ADB, but I've gathered from the guide thread that USB doesn't work. Then I tried enabling root with ADB and connecting over the network, but I can't get it to authenticate. I couldn't find the adb_keys file, so I created it at (the main partition with the most space? It's unnamed)/adb/adb_keys and have set the permissions to 0644 and owner to 0:0 with no luck. I revoked keys in settings and nothing happened, so this might actually be the wrong place. I've done quite a bit of Google-ing over the last few hours, and nothing I can find applies here.
I'm not quite sure where to go from here, I would greatly appreciate any ideas. Thanks!

Have you another switch?
Reflash Linage on your SD card put it in the other switch install your stuff over twrp press reboot it comes black screen. Shutdown the switch put the SD card in your switch an it works.
Can you access twrp over your pc whit adb?
Try it when the switch is docket.
https://forum.xda-developers.com/umi-z/how-to/guide-twrp-adb-shell-t3601881

evil_santa said:
Have you another switch?
Reflash Linage on your SD card put it in the other switch install your stuff over twrp press reboot it comes black screen. Shutdown the switch put the SD card in your switch an it works.
Can you access twrp over your pc whit adb?
Try it when the switch is docket.
https://forum.xda-developers.com/umi-z/how-to/guide-twrp-adb-shell-t3601881
Click to expand...
Click to collapse
No, no other Switch. What do you mean try when it's docked?

put your switch in the dock while twrp is running. connect the USB port of your dock to your PC and try to connect via twrp. if you don't have a connection cable, try an Android smartphone.

evil_santa said:
put your switch in the dock while twrp is running. connect the USB port of your dock to your PC and try to connect via twrp. if you don't have a connection cable, try an Android smartphone.
Click to expand...
Click to collapse
That's not quite how USB works. I can't run adb from my phone anyways, it isn't rooted.
EDIT: I'm not quite sure I understood you. Did you mean plug the dock into the computer via USB-C? If so, I've just tried that and it didn't work.

I have managed to get ADB working! ADB with root is working fine, but I don't know how I can install Magisk and/or OpenGApps from here.

Ethan Weegee said:
EDIT: I'm not quite sure I understood you. Did you mean plug the dock into the computer via USB-C? If so, I've just tried that and it didn't work.
Click to expand...
Click to collapse
Yes the switch can't speak by the usb C port whit Your computer but when the switch docket he can speak by the dock's usb port.
The reason is that the switches Otg doesn't work.
If that doesn't work for you then I can make you a finished image of what Open Gapps and magisk has already installed.

evil_santa said:
Yes the switch can't speak by the usb C port whit Your computer but when the switch docket he can speak by the dock's usb port.
The reason is that the switches Otg doesn't work.
If that doesn't work for you then I can make you a finished image of what Open Gapps and magisk has already installed.
Click to expand...
Click to collapse
The Switch dock doesn't work without power, I just tested. There wouldn't be a way to connect it via USB.
I would very much appreciate it if you could make an image I can use, though! As long as it isn't a bother!

Ok what image size do you need for your SD card? Do you need an Emunand partition for atmosphere?
But it will take a while.

evil_santa said:
Ok what image size do you need for your SD card? Do you need an Emunand partition for atmosphere?
But it will take a while.
Click to expand...
Click to collapse
My card is 128 GB and I don't need an emunand partition. I can organize the partitions after I write them with gparted, no? It shouldn't really matter.

Yes you can if you know how to do it. If I have the time, I'll make you a finished image.

Do you can boot into hekate?
can you activate root on another way? You can try Flashify, its like a "live System recovery".
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=de
If you will setup android on another switch, you can boot it on your switch, but you wlan and bt dont work.
Maybe it is possible to flash gapps and co, without booting the main system (what will install mac and co. for wireless connections). So you just have to normal boot and all is fine
We have Multiboot pre-build Images:
https://psxtools.de/forum/index.php...c-android-linux-und/&postID=805881#post805881 (Google translator will help you)

Soulreaver1993 said:
Do you can boot into hekate?
can you activate root on another way? You can try Flashify, its like a "live System recovery".
https://play.google.com/store/apps/details?id=com.cgollner.flashify&hl=de
If you will setup android on another switch, you can boot it on your switch, but you wlan and bt dont work.
Maybe it is possible to flash gapps and co, without booting the main system (what will install mac and co. for wireless connections). So you just have to normal boot and all is fine
We have Multiboot pre-build Images:
https://psxtools.de/forum/index.php...c-android-linux-und/&postID=805881#post805881 (Google translator will help you)
Click to expand...
Click to collapse
I can boot Hekate and use it without the GUI, conveniently it displays text on the right side of the screen which is somewhat usable.
Doesn't Flashify require root access? I only have root access over ADB at the moment, Magisk is not installed. I don't have another Switch to install Magisk or OpenGApps. I checked the link, but it doesn't seem like those are any different at first glance? Correct me if I'm wrong.

Yes, flashify needs root.
Maybe you can try kingroot to get root and then flash magisk and Co. Via flashify.

Soulreaver1993 said:
Yes, flashify needs root.
Maybe you can try kingroot to get root and then flash magisk and Co. Via flashify.
Click to expand...
Click to collapse
Google gives me rather sketchy domains. Can you link this?

I have managed to gain root through Lineage! I found extra addons that LineageOS provides (specifically this one) and manually copied the system items to the system partition, taking care to set permissions right. After that, going into developer settings and checking the root setting now provides an 'Apps' option which is exactly what I'm looking for.
However, I couldn't install OpenGApps. Flashify claimed the flash completed successfully yet nothing new appeared after a reboot, and the OpenGApps app rebooted the Switch instantly when trying to install.

Hmm, cool way to get root.
But sorry IT doesnt Work.
The First Boot after gapps need much time, how Long do you wait?

Soulreaver1993 said:
Hmm, cool way to get root.
But sorry IT doesnt Work.
The First Boot after gapps need much time, how Long do you wait?
Click to expand...
Click to collapse
As long as it took to boot. It didn't take any longer than normal, though.

@Ethan Weegee
I made a pre made image please test and report if it works.
https://drive.google.com/file/d/1_xeNiOairi0KsCIt6EgJxd3bndl3L9mj/view?usp=sharing

evil_santa said:
@Ethan Weegee
I made a pre made image please test and report if it works.
https://drive.google.com/file/d/1_xeNiOairi0KsCIt6EgJxd3bndl3L9mj/view?usp=sharing
Click to expand...
Click to collapse
I'm so sorry I couldn't get back to you sooner! I've been distracted. I've since bought an RCM jig and learned of Hekate autoboot, so that's less painful.
I just tried to boot that image, and it 'Failed to mount SD!'. I can no longer read anything more than the first line though. I'll hopefully be getting my screen replaced soon, so I can finally figure this out.