Database Users

please help fast

{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
updated my n7 3g to 4.2.2 and now when i chose to unlock bootloader (with 4.2.1 chosen) it stops on waiting for adb mode when i write no.If i go to fastboot and write yes pertty much same,nothing changes...I got drivers and debugging on

help

Seems like adb is not working, most likely because of the new 4.2.2 security for adb debugging. I pulled my hair out for 3 hours the other night trying to get it to work. I had to uninstall the drivers, reboot, test, rinse repeat. I was using Wug's toolkit, it details everything pretty good.

Activate developer mode, enable adb, plug in your device, send an adb command (like adb devices). It will send back adb offline. Now look at your phone. You should see a screen about allowing adb from your computer. Allow it. Now once or twice, this prompt did not appear for me. I simply had to unplug and replug the device, then it appeared. Once it is allowed, test it by doing the old adb reboot bootloader and once there fastboot oem unlock and there you go!
Or you can continue with your tool kit at that point, up to you !!

Hi, FatalaS...
I'm not familiar with WugFresh's toolkit... or indeed any other toolkits... I'm more of a fastboot man.
I also generally don't tend to use adb much, except when I'm performing a full backup (via adb pull) to my laptop (which is infrequent, as it seems to take forever - a LOT of stuff to be backed up!).
I use fastboot primarily... for flashing custom recoveries and new kernels/boot.img's.
I do this by copying my chosen recovery.img file (currently TWRP, renamed as recovery.img) or a boot.img file (currently franco's, renamed as boot.img), into the same folder on my laptop, where I keep my fastboot and adb executables.
I shutdown my Nexus 7, and reboot into FASTBOOT/BOOTLOADER mode by pressing and HOLDING the VOL DOWN button, and whilst HOLDING, press the POWER-ON BUTTON.
Having connected my Nexus 7 to my laptop, I then check I have a valid FASTBOOT connection (via a command prompt window, open on the folder I alluded to above), with...
Code:
fastboot devices
This should report a serial number along the lines of something like this...
Code:
015d2424b1xxxxx fastboot
...and then... (and this is directly pertinent to your original question)...
Code:
fastboot oem unlock
...will unlock the bootloader - YOU DON'T NEED ADB FOR THIS - JUST ENSURE YOUR TABLET IS IN FASTBOOT MODE AND RUN THIS COMMAND.
I did this several months ago on my Nexus 7, and once done, it never needs to be repeated... unless you relock the bootloader at some point, with the surprisingly original syntax...
Code:
fastboot oem lock
------------
Having done this (unlocked the bootloader), you can then fastboot flash custom recoveries (like TWRP or CWM) with...
Code:
fastboot flash recovery <your chosen recovery.img>
...or flash CERTAIN (but not all) custom kernels, with...
Code:
fastboot flash boot <your chosen boot.img>
Some kernels consist of more than just a simple boot.img (such as franco's)... some put various files in various parts of /system and thus need to be flashed via your chosen custom recovery, in much the same way custom ROMs are flashed.
-----------
Hope this somewhat lengthy post helps...
Rgrds,
Ged.

You can't unlock 4.2.2 Android with 4.2.1 Toolkit the Android version MUST MATCH.
http://www.youtube.com/watch?v=GnHFtFTp-cc
Listen to this video CAREFULLY + read the Toolkit thread slowly and you will find your solution.

HELP!!! My nexus 4 is broken and failed to flash any img

I've tried to use the Wug's Nexus Root Toolkit (v1.7.9) and used the option of Flash stock + Unroot,
I've entered the bootloader mode to flash but I got this............ :crying:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
my nexus wont flash the img whatever I try to flash by the toolkit
please help

hey, did you unlock the bootloader 1st?

opssemnik said:
hey, did you unlock the bootloader 1st?
Click to expand...
Click to collapse
yes I did, my bootloader has already been unlocked

Flash factory image manually then, I don't trust in any program except my head
1. Download factory image
2. Download adb and fastboot
3. Extract factory image (all the files) in the adb/fastboot folder
4. Go into bootloader mode and connect it to the pc
5. Open a command window in the adb/fastboot folder
6. Type
Code:
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase recovery
fastboot erase boot
7. Go to the adb/fastboot folder and select flash-all.bat file, and let it flash
It works absolutely always!!!

luiseteyo said:
Flash factory image manually then, I don't trust in any program except my head
1. Download factory image
2. Download adb and fastboot
3. Extract factory image (all the files) in the adb/fastboot folder
4. Go into bootloader mode and connect it to the pc
5. Open a command window in the adb/fastboot folder
6. Type
Code:
fastboot erase system
fastboot erase userdata
fastboot erase cache
fastboot erase recovery
fastboot erase boot
7. Go to the adb/fastboot folder and select flash-all.bat file, and let it flash
It works absolutely always!!!
Click to expand...
Click to collapse
I've no idea how to open a command window in the adb/fastboot folder :silly:
and what should be the folder name of the adb/fastboot folder?

John_Yiu said:
I've no idea how to open a command window in the adb/fastboot folder :silly:
and what should be the folder name of the adb/fastboot folder?
Click to expand...
Click to collapse
Are u using windows?

i suggest you go to this thread as you don't know how to use adb and fastboot http://forum.xda-developers.com/announcement.php?a=2018179
Sent from my Nexus 4 using XDA Premium 4 mobile app

shift + righ click on the folder and select open cmd prompt

problems solved! my phone is back, thanks all

Can't unlock bootloader zuk z1

[SOLVE]
Hi, I have a Zuk Z1 with ZUI 2.5.330 installed. So, I want to try some custom ROMs for fun, but ZUI version haven't an OEM unlock option, only have an usb debugging option. I already install adb and fastboot tools for Android, and I can reboot to bootloader through command adb reboot bootloader, but when I type fastboot devices nothing appears. When fastboot is active, in the ZUK z1 appears a black screen with the linux penguin and a status that say locked. So, if someone can give me a solution I would appreciated.
Thanks.

zsbq82 said:
Hi, I have a Zuk Z1 with ZUI 2.5.330 installed. So, I want to try some custom ROMs for fun, but ZUI version haven't an OEM unlock option, only have an usb debugging option. I already install adb and fastboot tools for Android, and I can reboot to bootloader through command adb reboot bootloader, but when I type fastboot devices nothing appears. When fastboot is active, in the ZUK z1 appears a black screen with the linux penguin and a status that say locked. So, if someone can give me a solution I would appreciated.
Thanks.
Click to expand...
Click to collapse
Check your PC, drivers, Firewall, cable etc. That are most common problems you'll find

zsbq82 said:
Hi, I have a Zuk Z1 with ZUI 2.5.330 installed. So, I want to try some custom ROMs for fun, but ZUI version haven't an OEM unlock option, only have an usb debugging option. I already install adb and fastboot tools for Android, and I can reboot to bootloader through command adb reboot bootloader, but when I type fastboot devices nothing appears. When fastboot is active, in the ZUK z1 appears a black screen with the linux penguin and a status that say locked. So, if someone can give me a solution I would appreciated.
Thanks.
Click to expand...
Click to collapse
Hi, do you find any way to solve problem? My is similar, just flash ZUI over 7.1.2 and boolader is locked....

strongst said:
Check your PC, drivers, Firewall, cable etc. That are most common problems you'll find
Click to expand...
Click to collapse
Hi, it happens the same thing. I've change the USB cable and I also try it with allinone tool, but the state of the oem does not change. If someone have another way, I'll give it a chance.
Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I think this might be useful-
http://developer.zuk.com/bootloader

zsbq82 said:
Hi, it happens the same thing. I've change the USB cable and I also try it with allinone tool, but the state of the oem does not change. If someone have another way, I'll give it a chance.
Thanks.
Click to expand...
Click to collapse
Please post a log of your commands you typed so we can check this.

strongst said:
Please post a log of your commands you typed so we can check this.
Click to expand...
Click to collapse
1- adb devices ( returns my device ZUK z1).
2- adb reboot bootloader ( enters un fastboot Mode).
3- sudo fastboot devices ( same that in first step).
4- sudo fastboot oem unlock-go ( print three dots and in this step I get stuck).
That's all,
Thanks.

zsbq82 said:
1- adb devices ( returns my device ZUK z1).
2- adb reboot bootloader ( enters un fastboot Mode).
3- sudo fastboot devices ( same that in first step).
4- sudo fastboot oem unlock-go ( print three dots and in this step I get stuck).
That's all,
Thanks.
Click to expand...
Click to collapse
Sorry, but I that's not a log file. Please upload /link /screenshot whatever... The full commands and output you enter on your PC.

[SOLVE]
strongst said:
Sorry, but I that's not a log file. Please upload /link /screenshot whatever... The full commands and output you enter on your PC.
Click to expand...
Click to collapse
Well, there is no need: I already solve it. For same future issues you must go to http://developer.zuk.com/bootloader and ZUK team will send you an unlockerbootloader image. They explain with detail all the process to follow.
Thanks for the support.

Hi, could you please you used email address that they answered you?
Because i already have such problem and with some email address sent serial number to them, but unfortunately i did not receive any image or reaction, if i send for you my serial number could you give it for me?

unlock site doesn't seem to work anymore

[Claimed] New method of installing Magisk without ROOT on H872

Can someone assure me will this method work on our device(H872) if we unlocked our bootloader and do accordingly what written here? Or it will damage(hardbrick) our device? He said in a comment that this method will only work on H870, H872 & US997 model, which indicating all unlockable G6s.
Original thread title: [GUIDE][ROOT] Install Magisk without Root and Recovery
Original thread link: https://forum.xda-developers.com/lg-g6/how-to/guide-insatll-magisk-root-recovery-t3900475
K3V1991 said:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
​
NFO:
This Method does not need Root or Custom Recovery
You must have a Stock Boot Image Dump and you also have to be able to flash the patched Boot Image via Fastboot Mode
Requirements:
1. ADB and Fastboot on your PC (for example Minimal ADB and Fastboot) [Thread]
2. Stock boot.img of your Device (extract File from Factory Image)
3. Magisk Manager [Thread]
4. Internet connection
5. Bootloader unlocked [Thread]
6. Developer Options > USB Debugging [Thread]
Patching the Stock boot.img:
1. Copy the Stock boot.img to your Phone's internal Storage
2. Install Magisk Manager
3. Launch Magisk Manager App
4. If prompted to install Magisk select "No Thanks"
5. Press Install > Install > Patch Boot Image File and select your Stock boot.img
6. Magisk Manager should begin downloading the Magisk.zip file used for patching
7. Once download is complete Magisk Manager will automatically patch the Boot File
Flashing the patched boot.img:
1. Install Minimal ADB and Fastboot
2. Connect the Phone to the PC via USB Cord
3. Copy the patched_boot.img from your Phone's internal Storage to C:\Program Files (x86)\Minimal ADB and Fastboot\
4. Unlock the Bootloader
5. Enable USB Debugging
6. Open Minimal ADB and Fastboot
7. Boot into Fastboot Mode, type:
Code:
adb reboot bootloader
7. Flash the patched_boot.img
Code:
fastboot devices
fastboot flash boot patched_boot.img
fastboot reboot
8. Open Magisk Manager and verify Root
9. Enjoy
___
Click to expand...
Click to collapse

Go ahead and try it
If the H872 had the flash command, then you wouldn't need to go through that bullsh#t, you could just flash TWRP to recovery...
-- Brian

This does not work on H872 period.
I tried just for the hack of it, you will get
writing 'boot'...
FAILED (remote: unknown command)

Installing lineage OS - stuck on start screen, would very much appreciate assistance

I've been following this guide with the aim of installing lineageos on a 6T I just bought: https://lineageosroms.com/fajita/#installation.
I downloaded the following files in advance:
copy-partitions-20200903_1329.zip
lineage-18.1-20211230-nightly-fajita-signed.zip
lineage-18.1-20211230-recovery-fajita.img
I have followed all the steps up to and including steps 6 of part 'Temporarily booting a custom recovery using fastboot'. The last part that appeared to run successfully was step 5 e.g.: fastboot flash boot lineage-18.1-20211230-recovery-fajita.img
Here is the output of the commands run on the host (serial number redacted):
adb reboot bootloader
➜ fastboot devices
******* fastboot
➜ fastboot oem unlock
OKAY [ 0.036s]
Finished. Total time: 0.036s
➜ adb reboot bootloader
➜ fastboot devices
******** fastboot
➜ fastboot flash lineage-18.1-20211230-recovery-fajita.img
unknown partition 'lineage-18.1-20211230-recovery-fajita.img'
fastboot: error: cannot determine image filename for 'lineage-18.1-20211230-recovery-fajita.img'
➜ fastboot flash boot lineage-18.1-20211230-recovery-fajita.img
Sending 'boot_a' (65536 KB) OKAY [ 1.543s]
Writing 'boot_a' OKAY [ 0.332s]
Finished. Total time: 1.973s
➜ fastboot devices
******** fastboot. ### This is where I just see the message about the OEM being unlocked and integrity.
➜ adb sideload copy-partitions-20200903_1329.zip ## I ran this even though I just saw the integrity message in the hope it would then enable me to select 'Apply Update'.
adb: sideload connection failed: no devices/emulators found
adb: trying pre-KitKat sideload method...
adb: pre-KitKat sideload connection failed: no devices/emulators found
➜ fastboot devices
******** fastboot
NB I once accidentally wrote fastboot flash lineage-18.1-20211230-recovery-fajita.img instead of fastboot flash boot lineage-18.1-20211230-recovery-fajita.img (i.e. I missed off the 'boot'). However, as I got the immediate error "fastboot: error: cannot determine image filename for 'lineage-18.1-20211230-recovery-fajita.img'" I suppose it was a no-op and hopefully didn't do any harm.
The problem is that when I then booted into the phone with volume down and power (step 6) I just got a screen with a message about the OEM being unlocked and phone integrity.
I powered the phone off after waiting a while with volume up and power. Then powered on. Same message. Since then I've tried powering off and on with both volume up and volume down and power. I get into a mode where I can select start, restart boot loader, recovery mode and power off.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
As I understood I'm trying to get into 'recovery mode' I selected that, but that just restarts the phone. I think that just took me back to the integrity message and at that point I ran the command adb sideload copy-partitions-20200903_1329.zip in the hope it would bring up the option to apply the update. However, now whenever I restart the phone I don't see the integrity message, just the 'options' menu (please see 'start' option above). I don't see the OEM unlocked/integrity message any more regardless of how I start the phone.
I have now tried basically all the options including restart the bootloader. All lead back to the same screen. When I have the phone connected to my mac via usb, I can still at least see it with fastboot devices:
fastboot devices
******** fastboot
As the guide I'm following doesn't show what you ought to see at each step I'm not sure what should have happened on step 6 when booting into recovery mode (this is my first flash) but as the guide says
'On the device, select “Apply Update”, then “Apply from ADB” to begin sideload.' I'm guessing it should at least have booted into a UI different to the one I'm seeing.
Is there anything I can do now? Should I try flashing another recovery image? Re running anything? Is it 'bricked'?
Really appreciate any guidance.

PS one thing I've noticed is that the instructions of 6T (https://lineageosroms.com/fajita/#installation) say we should run
fastboot flash boot <recovery_filename>.img
whereas the instructions for earlier and later models of the one plus (and other brands) say to run
fastboot flash recovery <recovery_filename>.img
Of course this might be correct, but does anyone know if this is a mistake in the instructions - i.e. should it have been 'recovery' not 'boot' for the 6/6T?
---- EDIT -----
Having looked up some documentation on fastboot (which say the structure of the command is basically fastboot flash <partition> <filename>) and then read around a bit on partitions on Android phones, I'm getting the impression android phones pretty much always have a recovery partition, which would make me think that the 'boot' command is indeed wrong. That said, I've got next to no experience with this so it's hard to be sure that the command isn't correct for some reason I'm not aware of, that only pertains to a few generations of phones.
Anyone?
--- EDIT 2 ----
The maintainers of the wiki.lineageos.org have confirmed to me that the line fastboot flash boot <recovery_filename>.img is written as intended. So still at square one.
Any ideas, anyone?

FWIW I got there. In case it helps anyone to know any of the sordid details, first I flashed back the stock ROM using this thread. Worked pretty much as described albeit I had to unzip the images folder and move the bat file into it so it found the images (first had to get hold of a windows machine).
Once I had it installed again I took an android update on the device. I think it highly likely that this was the cause of the original issue reported above - following the lineageOS wiki would probably have worked from that point, but I never found out as I decided I wanted TWRP anyway and used that as my custom recovery instead. That said, I now realise I could just as well have only installed TWRP after flashing lineage, as flashing LineageOS wiped TWRP.
BTW, I really can't fathom why I either didn't clock or ignored the message about making sure you're on the latest 11 firmware (in a red box!) at the top of the lineageOS install wiki. I don't remember seeing it but perhaps I just thought it would be fine as it was a 'fresh' phone (that had probably lying in a box for a year or so). Anyway, lesson learned.
Had to scramble over some other issues, involving booting a temp 'test' TWRP from crdroid first before flashing the official one, described around this page. I also had an odd 'no system' message in TWRP after wiping the existing system (following these instructions to check which bits to wipe when using TWRP before flashing a custom ROM). Anyone reading might want to check those instructions by asking on a lineageos forum if it makes sense to wipe 'system' on TWRP before flashing the lineage ROM - as I got a message after flashing lineage (in TWRP, before rebooting) that there was no 'system'. However it rebooted (with an error re corrupt user data that I was able to fix just by allowing lineage to wipe the user data again), so it's hard to see how that report of there being no system can have been strictly accurate.
But. I. got. there.

PS now I remember why I didn't see the warning to update the firmware. I was (unknowingly) viewing a repost (on lineageosroms) rather than the original wiki (on wiki.lineageos.org). Beware

i have the same thing but on a newer phone, my pc cant see it so im stuck here for now