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

Bricked A2017U

I'm not sure exactly what I did wrong, but in the process of trying to root my B15 A2017U, it ended up in a state of, I'm guessing, permanent EDL mode. The phone gives absolutely no response to any buttons or attempts to boot it (no vibration, no lights, just a black screen, whether I try to boot normally, boot to recovery, or boot to EDL), it does show up in device manager as Qualcomm HS-USB QDLoader 9008 (COM10), but adb won't recognise it, and it shows up in MiFlash but any attempt to flash anything results in "cannot receive hello packet", "try to reset status" and eventually "error:The write timed out."
I've been reading through a lot of threads here, but at this point I'm pretty much out of ideas, and I'd really like to have a phone for work in 6 hours. Can anyone help, please?
Not sure how useful it will be, but here's everything I can remember about what I've done just so there's something to go on. First, I tried a few days ago as detailed in this post, and put it aside after that post. Aside from not being able to get to recovery at that point, the phone was working perfectly. Today, seeing the new Axon7Toolkit, I decided to give it a try. I managed to unlock the bootloader and get into TWRP recovery (during the process, it asked me for a decryption password and I hit cancel). I've done a lot of reading and searching since then so I can't recall the exact steps I took after that, but I wiped the device (I didn't change the filesystem or anything) and got errors, and then after seeing the "your device can't be checked for corruption" message I searched and found that I need to mount system, so I did so (not in read-only), and wiped again, this time with no error messages. I can't remember if I did anything else in TWRP aside from looking through the options available. After that, I think what I did was "Flash TWRP and/or root" again in Axon7Toolkit, and I think something went wrong at that point. That's pretty much all I know.

Aspoehro said:
I'm not sure exactly what I did wrong, but in the process of trying to root my B15 A2017U, it ended up in a state of, I'm guessing, permanent EDL mode. The phone gives absolutely no response to any buttons or attempts to boot it (no vibration, no lights, just a black screen, whether I try to boot normally, boot to recovery, or boot to EDL), it does show up in device manager as Qualcomm HS-USB QDLoader 9008 (COM10), but adb won't recognise it, and it shows up in MiFlash but any attempt to flash anything results in "cannot receive hello packet", "try to reset status" and eventually "error:The write timed out."
I've been reading through a lot of threads here, but at this point I'm pretty much out of ideas, and I'd really like to have a phone for work in 6 hours. Can anyone help, please?
Not sure how useful it will be, but here's everything I can remember about what I've done just so there's something to go on. First, I tried a few days ago as detailed in this post, and put it aside after that post. Aside from not being able to get to recovery at that point, the phone was working perfectly. Today, seeing the new Axon7Toolkit, I decided to give it a try. I managed to unlock the bootloader and get into TWRP recovery (during the process, it asked me for a decryption password and I hit cancel). I've done a lot of reading and searching since then so I can't recall the exact steps I took after that, but I wiped the device (I didn't change the filesystem or anything) and got errors, and then after seeing the "your device can't be checked for corruption" message I searched and found that I need to mount system, so I did so (not in read-only), and wiped again, this time with no error messages. I can't remember if I did anything else in TWRP aside from looking through the options available. After that, I think what I did was "Flash TWRP and/or root" again in Axon7Toolkit, and I think something went wrong at that point. That's pretty much all I know.
Click to expand...
Click to collapse
I think you got the "cannot receive hello packet", because your bootloader is locked. Using this method https://forum.xda-developers.com/axon-7/development/axon7tool-flash-backup-boot-recovery-t3514254 to unlock it, then flash twrp, then firmware

The bootloader was unlocked (though it may have been unintentionally re-locked somehow?), and MiFlash works with a locked bootloader, so I don't think that's the issue. Axon7tool also doesn't help, because just like adb it can't find the device.
Now, trying again today, MiFlash is working for some reason. I haven't done anything differently, but I can flash whatever I want with MiFlash now. But it doesn't really make a difference, because the phone is still entirely unresponsive, I can't enter recovery or boot in any way. Any suggestions for what else to try?

Aspoehro said:
I'm not sure exactly what I did wrong, but in the process of trying to root my B15 A2017U, it ended up in a state of, I'm guessing, permanent EDL mode. The phone gives absolutely no response to any buttons or attempts to boot it (no vibration, no lights, just a black screen, whether I try to boot normally, boot to recovery, or boot to EDL), it does show up in device manager as Qualcomm HS-USB QDLoader 9008 (COM10), but adb won't recognise it, and it shows up in MiFlash but any attempt to flash anything results in "cannot receive hello packet", "try to reset status" and eventually "error:The write timed out."
I've been reading through a lot of threads here, but at this point I'm pretty much out of ideas, and I'd really like to have a phone for work in 6 hours. Can anyone help, please?
Not sure how useful it will be, but here's everything I can remember about what I've done just so there's something to go on. First, I tried a few days ago as detailed in this post, and put it aside after that post. Aside from not being able to get to recovery at that point, the phone was working perfectly. Today, seeing the new Axon7Toolkit, I decided to give it a try. I managed to unlock the bootloader and get into TWRP recovery (during the process, it asked me for a decryption password and I hit cancel). I've done a lot of reading and searching since then so I can't recall the exact steps I took after that, but I wiped the device (I didn't change the filesystem or anything) and got errors, and then after seeing the "your device can't be checked for corruption" message I searched and found that I need to mount system, so I did so (not in read-only), and wiped again, this time with no error messages. I can't remember if I did anything else in TWRP aside from looking through the options available. After that, I think what I did was "Flash TWRP and/or root" again in Axon7Toolkit, and I think something went wrong at that point. That's pretty much all I know.
Click to expand...
Click to collapse
Hi, I'm the dev for the toolkit and I think I know what the problem is. Can you go into C:\Axon7Development\Axon7Toolkit\twrp and see what the size of the image is? It may have been a bad download. Either that or there is issues with the latest version of SupersSU if you chose the root option.

bkores said:
Hi, I'm the dev for the toolkit and I think I know what the problem is. Can you go into C:\Axon7Development\Axon7Toolkit\twrp and see what the size of the image is? It may have been a bad download. Either that or there is issues with the latest version of SupersSU if you chose the root option.
Click to expand...
Click to collapse
twrp-3.1.0-0-ailsa_ii.img is 14.1 MB

Aspoehro said:
twrp-3.1.0-0-ailsa_ii.img is 14.1 MB
Click to expand...
Click to collapse
Ok so TWRP is definitely not the problem. Can you remember exactly when the problem happened, like after SuperSU was flashed since you mentioned using the Flash TWRP and root option?

I don't remember any specific details, but I'm fairly certain I didn't get to the point of flashing SuperSU. I think the most likely cause is me doing something wrong in TWRP (I was trying to follow vague guides mixed with scattered information throughout various threads), and when I did "Flash TWRP and/or root" after flashing TWRP, I think I got some error messages right away.
One problem I do remember is that the toolkit would sometimes say something like "device not found", but still try to continue whatever it was doing and move on to the next step as if there were no problems. Unfortunately I don't remember exactly when it did that, so I can't give any details on how you could reproduce it.

Hey, I had exactly the same problem. Are you saying miflash is now working (you get success at the end!) ? If so, I don't understand why it wouldn't boot afterwards.
If not, in my case, a computer reboot, switching to MiFlash Beta and switching com ports eventually allowed me to flash successfully B15 full package after 3 hours of cannot receive hello packet. You could always try full B13 (Chinese rom) or other similar packages to see if it makes a difference. You'll be able to revert afterwards.

Aspoehro said:
I don't remember any specific details, but I'm fairly certain I didn't get to the point of flashing SuperSU. I think the most likely cause is me doing something wrong in TWRP (I was trying to follow vague guides mixed with scattered information throughout various threads), and when I did "Flash TWRP and/or root" after flashing TWRP, I think I got some error messages right away.
One problem I do remember is that the toolkit would sometimes say something like "device not found", but still try to continue whatever it was doing and move on to the next step as if there were no problems. Unfortunately I don't remember exactly when it did that, so I can't give any details on how you could reproduce it.
Click to expand...
Click to collapse
So you're sure that your problem is not because of my toolkit? Regardless looks like now I have to fix the ADB check

Gnreux said:
Hey, I had exactly the same problem. Are you saying miflash is now working (you get success at the end!) ? If so, I don't understand why it wouldn't boot afterwards.
If not, in my case, a computer reboot, switching to MiFlash Beta and switching com ports eventually allowed me to flash successfully B15 full package after 3 hours of cannot receive hello packet. You could always try full B13 (Chinese rom) or other similar packages to see if it makes a difference. You'll be able to revert afterwards.
Click to expand...
Click to collapse
MiFlash does seem to be working, I don't get any errors and it says it flashed successfully. I tried flashing B15 full and fastboot unlock from here, neither allowed the phone to boot.
Any suggestions for specific files to try flashing?
bkores said:
So you're sure that your problem is not because of my toolkit? Regardless looks like now I have to fix the ADB check
Click to expand...
Click to collapse
I can't be sure since I don't know exactly what the problem is or how I caused it. All I really have are guesses at this point.

Aspoehro said:
MiFlash does seem to be working, I don't get any errors and it says it flashed successfully. I tried flashing B15 full and fastboot unlock from here, neither allowed the phone to boot.
Any suggestions for specific files to try flashing?
Click to expand...
Click to collapse
I rebricked myself last night (lol), so I had to reflash full package, from the same link you posted, and here are some notes:
It seemed on first boot that it didn't work: usual three blinks of LED followed by a black screen
Second boot worked (and I now remember that the same thing had happened the first time I bricked my device), but Android asked me for a password even though I had formatted /data
From there, install TWRP via fastboot (and fastboot_unlock prior to that if bootloader is locked, it shouldn't be), format /data using TWRP, reboot, and you should have a working device
Hope it helps!

Gnreux said:
It seemed on first boot that it didn't work: usual three blinks of LED followed by a black screen
Click to expand...
Click to collapse
I don't even get that much, nothing I do gets any response from the phone at all. No LED when trying to boot (including EDL or recovery), no LED when charging, the only indication that the phone isn't perfectly dead is that it shows up in device manager and MiFlash.

You could try not flashing fastboot_unlock right away and booting first instead... This is the only thing we are doing differently, although I don't see how it could have an impact.
You could also try flashing this EDL package (B13) instead and flash your device specific bootstack afterwards.

Still no luck with anything I try to flash in MiFlash. But I tried reinstalling drivers with Zadig, and axon7tool is working this time. Trying to read gpt works fine, but if I try to read/write boot or recovery, I get "W: bad lba in partition entry 26" and "Cannot find partition boot"/"Cannot find partition recovery". I tried writing TWRP and a couple stock boot/recovery images despite the error, still no change.
Do those error messages give any new information that might be helpful?

Try miflash firmware from offical:
https://www.zteusa.com/axon-7#support

Not sure if this will help you but that miflash utility is a piece of ******** to work with I found.
When extracting the zip files there will usually be 2 folders in them, one is meta-something and the other one has the full name of the zip file, you have to select the full name one beside the meta folder not the parent folder.
Also Sometimes you need to hold all the buttons again and "restart" edl mode before the "hello packet" issues go away.

lipe123 said:
Not sure if this will help you but that miflash utility is a piece of ******** to work with I found.
When extracting the zip files there will usually be 2 folders in them, one is meta-something and the other one has the full name of the zip file, you have to select the full name one beside the meta folder not the parent folder.
Also Sometimes you need to hold all the buttons again and "restart" edl mode before the "hello packet" issues go away.
Click to expand...
Click to collapse
Thank you. This helped me. Why the *$*# can't the program just pick the zip file, or tell you which folder to pick? Until I found your post, I had no idea which folder to pick.
Thanks!!!
:victory:

Flapjack said:
Thank you. This helped me. Why the *$*# can't the program just pick the zip file, or tell you which folder to pick? Until I found your post, I had no idea which folder to pick.
Thanks!!!
:victory:
Click to expand...
Click to collapse
Glad it helped someone!

LG aristo 2 (K8 2018)

Since the majority of the hardware between the devices is gonna be almost exactly the same, I'mma give a shot at rooting it. Picking up tomorrow, so hopefully it goes well

I just got this phone. Let me know how what happens please.

tge101 said:
I just got this phone. Let me know how what happens please.
Click to expand...
Click to collapse
Yeah, I'll keep a heads up. I'm sitting in metro now tryna see what's going on, small argument. Their commercials in Philly don't mention that you need to switch carriers for the rebates.

I'll probably be getting one next week. Says it has 7.1.2 an it weighs less? Cool

attempt
Ok so I tried to root this and everything went well up ubtil I flashed Team win. When i try to open it, the program starts HOWEVER something is up with the touch screen. Im unable to click anything the only power button works. I tried flashing versions 3.0.0, 3.0.1, 3.0.2, 3.0.3. No luck! Is the problem they are old versions? Should i use 3.1.1 which was designed for Nougat supposedly?
Any advice this is my first attempt in to rooting android devices. Forgive me if any of my lingo is incorrect.

tribal1209 said:
Ok so I tried to root this and everything went well up ubtil I flashed Team win. When i try to open it, the program starts HOWEVER something is up with the touch screen. Im unable to click anything the only power button works. I tried flashing versions 3.0.0, 3.0.1, 3.0.2, 3.0.3. No luck! Is the problem they are old versions? Should i use 3.1.1 which was designed for Nougat supposedly?
Any advice this is my first attempt in to rooting android devices. Forgive me if any of my lingo is incorrect.
Click to expand...
Click to collapse
Are you trying to root the aristo or aristo 2?

Aristo 2. Sorry, kind of diving in head first with this whole process. If im doing something obviously wrong go easy on me lol.
---------- Post added at 11:26 PM ---------- Previous post was at 11:25 PM ----------
Aristo 2

Hmm and you flashed the twrp that was for the aristo right?

Well the TWRP files i used were on *How To* forums posts and youtube videos for the original LG Aristo. Everything was going fine but the touch screen while in TWRP does not work. Maybe there os a different version I can try? Do any of you guys have any ideas, my understanding though is that TWRP has to be created for a specific device once released. Is thats whats going wrong?

you unlocked the bootloader and flashed the aristo 1 recovery thats what you did so far right?

The aristo 1 recovery will not work at all.
The screens are of the same build, but different composition.
That's why I wanted to test this myself before posting further on the subject.
I can risk my phone, most of you cant.

I figured as much. Thanks for the info! Just got mine today. Glad the aristo's battery works in the aristo2 as i bought a couple batteries for it. I still do like the aristo though it feels a bit better in my hand.

Well luckily It seems i have not screwed up my phone. Have reset and wiped it multiple times which was annoying, but seems to be ok. It sucks because it looks like the touch screen alone is whats screwing me over. If only i had a way around it. Then again im sure you guys have a better idea of whats going on. Guess ill just be patient until more is posted on subject.

We need a new recovery for this anyway. Since the aristo 2 isn't gonna have multiple versions (besides the Korean base model the 2 is built after), we should be able to build just one recovery using the model number as it's target, we can make it borderline universal if a new version were to pop up.
I decided against going the metro route, buying mine in bulk. So I'll have one to smash when this is all over.

The TWRP method works the same as the Aristo, and the TWRP recovery IS compatible. However the touch screen does not function.. Is there a way to get it to work?

@ninjasinabag @teknoweanie @tribal1209 Hey guys, spent a few hours figuring out how to root. Pretty Simple
1) Enable Developer Options, USB Debugging & OEM Unlock
2) Reboot to Fastboot Mode (Using ADB via PC type: adb reboot bootloader)
3) Add root_boot.img into your adb folder
4) In ADB type: fastboot flash boot root_boot.img
5) After flash successful, type: fastboot reboot
6) Install Magisk Manager App

brad2192 said:
@[email protected]@tribal1209 Hey guys, spent a few hours figuring out how to root. Pretty Simple
1) Enable Developer Options, USB Debugging & OEM Unlock
2) Reboot to Fastboot Mode (Using ADB via PC type: adb reboot bootloader)
3) Add root_boot.img into your adb folder
4) In ADB type: fastboot flash boot root_boot.img
5) After flash successful, type: fastboot reboot
6) Install Magisk Manager App
Click to expand...
Click to collapse
Not to sound sceptical but is this the real deal?

spirithandler said:
Not to sound sceptical but is this the real deal?
Click to expand...
Click to collapse
Please someone let me know! I want this phone rooted (Its an awesome phone) but want some verification before I start flashing and downloading random files.

spirithandler said:
Not to sound sceptical but is this the real deal?
Click to expand...
Click to collapse
Yes, it is. What I did was use LG firmware extractor and extracted the boot image, then I proceeded to patch the boot image with magisk manager. Enabling OEM unlock allows me to flash the boot image with the newly-created custom one. Remember though, you should create a backup of your device because enabling OEM unlock will completely erase everything.

brad2192 said:
@ninjasinabag @teknoweanie @tribal1209 Hey guys, spent a few hours figuring out how to root. Pretty Simple
1) Enable Developer Options, USB Debugging & OEM Unlock
2) Reboot to Fastboot Mode (Using ADB via PC type: adb reboot bootloader)
3) Add root_boot.img into your adb folder
4) In ADB type: fastboot flash boot root_boot.img
5) After flash successful, type: fastboot reboot
6) Install Magisk Manager App
Click to expand...
Click to collapse
Supposedly the img you posted is simply a modified version of Magisk you posted. Someone please explain to me (Who is new to this whole process) why this supposed explanation does not involve any recovery program or requiring of wiping/clearing any cache or what have you?

Flash mobile with volume down broke

Hello all,
After 5 hours searching and almost done, it seems like the phone won against me...
I have a friend who has his device under Android5, latest version, and need at least Android 6 to update his bank app, which required this update to work normally.
The worst part here, is that the device has the down volume button not working anymore (at all)
I wa a little rusty because I moved two years ago to iOS, but I have some memories with my old samsung and Nexus 6 flashing.
So here's what I've tried so far, I can forgot to mention some stuff because it's been a long work lol
So I have a 1GB SD Card and my indows 10 computer.
- I started to download and install all ADB and fastboot drivers.
- I've activated Debugged mod and OEM Unlock. I couldn't find if the bootloader is allowed for unlock or not, because the command didn't work. So I supposed that yes, it is. The device is the J3 SM-J320FN bought in France, new.
ADB work perfectly, but I didnt manage to get the device recognsied with the Fastboot mode. "ADB Devices" list the phone, but fastboot devices command does not show anything, it goes back to another line.
My friend didn't mentionned that he has installed a recovery. I don't know how, but the recovery is very basic. Here's a photo of the recovery screen. It appear when i press Vol+, home and power button, but I can't move anywehre because of the low volume button not working. Vol-, home and power doesn't work for the Download mode.
I finally managed to enter in download mode by using the command ADB REBOOT DOWNLOAD. With that, I honestly don't remember how I did it, but I think I've flashed a file which allow me to root the device from ODIN. With this, I've got confirmation of Root Checker app that the device is now rooted.
I've passed many hours to make some tests here and there, but nothing gave me a real result. Then I found two apps : ROM Manager and Flashfire.
ROM Manager : The app says that it doesn't find Superuser in System/bin/su. So it's like the device is not rooted. Nothing seems to work on the app too.
Flashfire : It seems like this app can do the job, but I can't finalize the process. So I've changed the year of the phone to 2013 to get the app running, I've tried a wipe, and here... Yahoooo ! A big Loading screen with many line codes, and then... nothing. My computer make the sound to say that it recognised the device, and a full blackscreen for 10mn. Exactly same process if I try to flash a ROM, or whatever action (even doing a backup).
I suppose it's because the app wasnt granted the root permissions. Not sure, because even if the phone seems to have the root status, I never get any pop up to ask if I allow to get the permission or not. I've tried to dwnload the APK for SuperSU app or something, and nothing seems to work.
So now, It looks like i'm close, but I also think that there is nothing more to do.
The device is powering on, with all its data, and seems rooted, but I can't do anything. It seems like the recovery is the only option to go trough the install.
So you guys, do you have any ideas of what can I do ?
I'd like to install LineageOS, but any ROM with Android 6.0 min. will be fine for me.
Also, pardon my english. I'm french lol
Thank you for your help..!

Alerion13 said:
Hello all,
After 5 hours searching and almost done, it seems like the phone won against me...
I have a friend who has his device under Android5, latest version, and need at least Android 6 to update his bank app, which required this update to work normally.
The worst part here, is that the device has the down volume button not working anymore (at all)
I wa a little rusty because I moved two years ago to iOS, but I have some memories with my old samsung and Nexus 6 flashing.
So here's what I've tried so far, I can forgot to mention some stuff because it's been a long work lol
So I have a 1GB SD Card and my indows 10 computer.
- I started to download and install all ADB and fastboot drivers.
- I've activated Debugged mod and OEM Unlock. I couldn't find if the bootloader is allowed for unlock or not, because the command didn't work. So I supposed that yes, it is. The device is the J3 SM-J320FN bought in France, new.
ADB work perfectly, but I didnt manage to get the device recognsied with the Fastboot mode. "ADB Devices" list the phone, but fastboot devices command does not show anything, it goes back to another line.
My friend didn't mentionned that he has installed a recovery. I don't know how, but the recovery is very basic. Here's a photo of the recovery screen. It appear when i press Vol+, home and power button, but I can't move anywehre because of the low volume button not working. Vol-, home and power doesn't work for the Download mode.
I finally managed to enter in download mode by using the command ADB REBOOT DOWNLOAD. With that, I honestly don't remember how I did it, but I think I've flashed a file which allow me to root the device from ODIN. With this, I've got confirmation of Root Checker app that the device is now rooted.
I've passed many hours to make some tests here and there, but nothing gave me a real result. Then I found two apps : ROM Manager and Flashfire.
ROM Manager : The app says that it doesn't find Superuser in System/bin/su. So it's like the device is not rooted. Nothing seems to work on the app too.
Flashfire : It seems like this app can do the job, but I can't finalize the process. So I've changed the year of the phone to 2013 to get the app running, I've tried a wipe, and here... Yahoooo ! A big Loading screen with many line codes, and then... nothing. My computer make the sound to say that it recognised the device, and a full blackscreen for 10mn. Exactly same process if I try to flash a ROM, or whatever action (even doing a backup).
I suppose it's because the app wasnt granted the root permissions. Not sure, because even if the phone seems to have the root status, I never get any pop up to ask if I allow to get the permission or not. I've tried to dwnload the APK for SuperSU app or something, and nothing seems to work.
So now, It looks like i'm close, but I also think that there is nothing more to do.
The device is powering on, with all its data, and seems rooted, but I can't do anything. It seems like the recovery is the only option to go trough the install.
So you guys, do you have any ideas of what can I do ?
I'd like to install LineageOS, but any ROM with Android 6.0 min. will be fine for me.
Also, pardon my english. I'm french lol
Thank you for your help..!
Click to expand...
Click to collapse
So why not just install Marshmallow with Odin?
After that install TWRP the same way?

Is it possible ?
I though that only installing custom rom will allow the phone to go beyond 5.1. Because the phone can’t find any update on OTA.
So if I download the correct file, flashing it should work ?
Thanks for the answer

Alerion13 said:
Is it possible ?
I though that only installing custom rom will allow the phone to go beyond 5.1. Because the phone can’t find any update on OTA.
So if I download the correct file, flashing it should work ?
Thanks for the answer
Click to expand...
Click to collapse
I assumed the J320 had received the MM update. However it seems not.
In that case custom is the only way. For that you will need to install twrp with Odin.

Exactly what I though yesterday. I will call him to see what can I do.
So the latest versions of TWRP are compatible with the touch screen, and then the volume down button isn’t required to process ? After the recovery installed, I will be able to find the zip of the custom rom and install it right ?
Thank you again

Alerion13 said:
Exactly what I though yesterday. I will call him to see what can I do.
So the latest versions of TWRP are compatible with the touch screen, and then the volume down button isn’t required to process ? After the recovery installed, I will be able to find the zip of the custom rom and install it right ?
Thank you again
Click to expand...
Click to collapse
Twrp is touch driven so no need for hard keys.
The only issue is that you need to reboot immediately into recovery mode after flashing twrp.
As down isn't working you will need to leave auto reboot enabled and catch it at the right moment to boot to recovery as it reboots.

Excellent. I will try that and will let you know. Thank you

Trying to install TWRP and Lineage . . . vbmeta is in the way

I've been trying for the last few days to root and install Lineage on a brand new S6 lite tablet. I've downloaded Lineage, Odin, stock rom, ADB/platform tools, Ls4 tool, the 7 whatever it is extraction tool. I've unlocked the bootloader (I can recite every option under developer options). I've installed Magisk hoping that it might help if I rooted the dumb thing (spoiler alert: it rooted, it didn't help). I've tried to install it using ADB (before reading that Samsungs don't play nice with it ). I tried to side load it with an SD card; tablet liked the card, poo poo'd the files on it. I've used ODIN in every way shape and form, it always says "Yay! You Pass!" then my tablet reboots saying "Boo! You Lose!". I then reinstall the stock ROM, try something else, reinstall stock ROM, try this solution, reinstall stock ROM. The latest and greatest hurdle: when trying to install TWRP I get the error message VBMETA Error verifying image, not signed (3), verification disabled bit is set. I found info on that here, downloaded vbmeta from my stock ROM, tried to use a blank vbmeta, even went overboard and did something with the PIT function in Odin (saw it in the internet, it HAS to be correct, right?). Nothing nothing nothing.
I've rooted and installed custom ROM on Samsung tablets in the past, but this is ridiculous. It would take me a LONG time to give all the details of everything I've tried, if needed I can. At this point it's the principal of the matter . . . I am going to make this happen one way or another, and any advice someone might have would be appreciated.
About me!
Samsung Galaxy Tab S6 tablet LITE, SM-P610, running Android 11, UI 3.1, WIFI only.

vstarjewel said:
I've been trying for the last few days to root and install Lineage on a brand new S6 lite tablet. I've downloaded Lineage, Odin, stock rom, ADB/platform tools, Ls4 tool, the 7 whatever it is extraction tool. I've unlocked the bootloader (I can recite every option under developer options). I've installed Magisk hoping that it might help if I rooted the dumb thing (spoiler alert: it rooted, it didn't help). I've tried to install it using ADB (before reading that Samsungs don't play nice with it ). I tried to side load it with an SD card; tablet liked the card, poo poo'd the files on it. I've used ODIN in every way shape and form, it always says "Yay! You Pass!" then my tablet reboots saying "Boo! You Lose!". I then reinstall the stock ROM, try something else, reinstall stock ROM, try this solution, reinstall stock ROM. The latest and greatest hurdle: when trying to install TWRP I get the error message VBMETA Error verifying image, not signed (3), verification disabled bit is set. I found info on that here, downloaded vbmeta from my stock ROM, tried to use a blank vbmeta, even went overboard and did something with the PIT function in Odin (saw it in the internet, it HAS to be correct, right?). Nothing nothing nothing.
I've rooted and installed custom ROM on Samsung tablets in the past, but this is ridiculous. It would take me a LONG time to give all the details of everything I've tried, if needed I can. At this point it's the principal of the matter . . . I am going to make this happen one way or another, and any advice someone might have would be appreciated.
About me!
Samsung Galaxy Tab S6 tablet LITE, SM-P610, running Android 11, UI 3.1, WIFI only.
Click to expand...
Click to collapse
Stumbled upon the answer to get Lineage OS and recovery installed . . . AND IT FREAKIN WORKED! Happy Dance!!!!!

vstarjewel said:
Stumbled upon the answer to get Lineage OS and recovery installed . . . AND IT FREAKIN WORKED! Happy Dance!!!!!
Click to expand...
Click to collapse
How did you fix? Just for a reader's curiosity sake.

Real_fakename said:
How did you fix? Just for a reader's curiosity sake.
Click to expand...
Click to collapse
I believe he used LineageOS Recovery instead of TWRP (since the latter has been abandoned by the developer due to too many problems getting it working properly).

MJPollard said:
I believe he used LineageOS Recovery instead of TWRP (since the latter has been abandoned by the developer due to too many problems getting it working properly).
Click to expand...
Click to collapse
What he said . . . still my hero!!!! Not sure if it matters or not, but I ended up using Heimdall/ADB to install Lineage. More key strokes but it worked the first time I tried it. Thumbs up for it

I'm hanging installing the recovery, see: https://forum.xda-developers.com/t/...s-on-galaxy-tab-s6-lite.4417629/post-86603873
How to reboot into recovery after flashing? I always land into Stock ROM

I mistakenly thought that Heimdell could get you right into recovery mode, but upon reading the instructions I sent you it says you need to boot into recovery manually . . . I apologize for the wrong info. I can say that I found that if you don't move them fingers FAST from the reboot mode to recovery mode buttons, you will keep getting plopped back to the stock ROM. Like the SECOND the screen goes dark you switch over to the power and volume up buttons, AND DO NOT LET GO! I do remember having a bit of a pause when booting into the Lineage recovery, and I thought I would have to start over when the recovery screen came up. I did a triple take, couldn't believe I got it to work.

vstarjewel said:
I mistakenly thought that Heimdell could get you right into recovery mode, but upon reading the instructions I sent you it says you need to boot into recovery manually . . . I apologize for the wrong info. I can say that I found that if you don't move them fingers FAST from the reboot mode to recovery mode buttons, you will keep getting plopped back to the stock ROM. Like the SECOND the screen goes dark you switch over to the power and volume up buttons, AND DO NOT LET GO! I do remember having a bit of a pause when booting into the Lineage recovery, and I thought I would have to start over when the recovery screen came up. I did a triple take, couldn't believe I got it to work.
Click to expand...
Click to collapse
Did your S6 happen to show "KG STATE: Checking" constantly? After 2 hours, even though the console shows that there was success, the device itself appears to constantly be downloading, as per the instructions. But even after 2 hours, there is no notification on the tablet that shows the download is complete.