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.

Nexus 7 only boots into Fastboot Mode

Hello,
my Nexus 7 wasn't turned on since 3 weeks. Yesterday, I tried to boot it but it just shows the Google logo. The same with the Recovery. So I tried to install with N-Cry a Recovery, it shows that the installation was successfull, but it won't change everything. The same with the factory ROM, I tried it to install it via ADB, it shows that the installation was successfull, but it doesn't boot and still stucks in the Google-Screen. Know? What can I do? Is it a hardware problem? That would be terrible, because the gueranty ended august 2013.
Greetz!
Edit: If I try to Shut it down via fastboot, it shows Unrecoverable Bootloader Error.

DELETE

I am having an identical issue. I have experienced and resolved the battery issues before. This is not that. I've tried factory resets, toolkit stock flashes, toolkit OS updates, adb wipes and flashes. Everything always says successfully completed but it only boots to Google logo and occasionally freezes on the nexus logo.
Does anyone have more info on the N7's acutal boot process? I assume the Google logo is the POST. Is the Nexus logo provided by the bootloader, the kernel or after the OS starts running?
Is there a way to install a new bootloader?
Is there a win7 or Debian program program that will show in more detail every single line and process during the boot process?

Yea, there is a way, I've allready done it, but it doesn't boot anyway. With the Baseband Version sorry, but it's my fault, there cannot be a Baseband Version on my Grouper.
My Fastboot shows:
Product Name - grouper
Variant - grouper
HW Version: ER3
Baseband Version - N/A
Serial Number: 015XXXXXXXXXXX
Singing: Not defiened yet
LOCK STATE - UNLOCKED

fixed mine, conflicting driver issue and used pdanet versions instead of universal.

Thanks man. That could be work. I will try it later. Anybody another ideas?
Sent from my GT-I9300 using xda app-developers app

Push! Please, anybody any another ideas? The driver wasn't the problem, it doesn't turn on. I can do anything, flash with ADB, flash with different Toolkits...
PLEASE I need my tab...

PUSH! Please help. I tried it so much times, I deinstalled all drivers and install different drivers again... Please what could I do?

Hi, i have this problem but worse is that the buttons of my tablet are not working. It seems i can not boot pass the fastboot whenever i try to reboot (using Wug's Toolkit). Please, does anybody here who can help?

Have you tried flashing back to stock with fastboot?
Sent from my SGH-I997 using XDA Premium 4 mobile app

yes, i have tried that but it still won't pass fastboot. i don't know what's happening. i even tried disconnecting the power/volume buttton cable and tried rebooting again to check if it was the one causing the problem but still it did the same thing.

akerocks said:
yes, i have tried that but it still won't pass fastboot. i don't know what's happening. i even tried disconnecting the power/volume buttton cable and tried rebooting again to check if it was the one causing the problem but still it did the same thing.
Click to expand...
Click to collapse
So, you downloaded the factory image from google and flashed via fastboot from the pc?
Sent from my SGH-I997 using XDA Premium 4 mobile app

yes, using wug's toolkit

akerocks said:
yes, using wug's toolkit
Click to expand...
Click to collapse
No, not wugs. Forget toolkits. First, go here and download the factory image.
https://dl.google.com/dl/android/aosp/nakasig-kot49h-factory-83d93b5f.tgz
Unzip into same folder on pc where you have fastboot binary.
Next, boot to fastboot. Plug N7 to the pc. Open pc directory where fastboot is. Open a command window. (Click on an empty section of the folder so no files are highlighted, hold shift key on keyboard and right click with mouse. Choose "open command window here" from the dropdown)
Type these commands.
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot flash bootloader bootloader-grouper-4.23.img
fastboot reboot-bootloader
sleep 10
fastboot -w update image-nakasi-kot49h.zip
Sent from my SGH-I997 using XDA Premium 4 mobile app

hi, thank you for the reply. i followed your steps but this is what i got...
{
"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"
}

akerocks said:
hi, thank you for the reply. i followed your steps but this is what i got...
Click to expand...
Click to collapse
The commands must correspond to the version you downloaded. Jkr16s....4.23...etc. Could you post a screenshot of the folder you have those files in? Ill see what the deal is
You unzipped the tar.gz, correct?
Sent from my SGH-I997 using XDA Premium 4 mobile app

akerocks said:
Click to expand...
Click to collapse
Here is the issue. When you downloaded the tar.gz file that the image-nakasi-kot49h.zip was in, ot also contains the bootloader and some files called .flash-all, .flash....etc. All thoes files need to be in this folder. The image cant be flashed without the bootloader being sucessfully flashed, and the -w command is not recognized withoit the .flash-all.... files. Unzip all the tar.gz contents into the folder and do it again. It will be fine.
Sent from my Nexus 7 using XDA Premium 4 mobile app

[PROBLEM] Bootloop persists after Wipe Factory/Data reset

What I did:
1- I rebooted my Nexus 10 in TWRP Recovery and I did all the Wipes... include the Full Data...
2- I downloaded the Android 4.4 Nexus 10 Factory Image
3- I use the Nexus 10 toolkit v1.3.0 to flash the Nexus 10 Android 4.4 factory Image
4- My Nexus 10 are in BootLoop...
5- I did FactoryData wipe, and reboot system now... but, My Nexus are in BootLoop...
6- I downloaded the Android 4.3 Nexus 10 FactoryImage, I use the toolkit again and to flash this...
7- My nexus 10 are in bootloop....
8- I reboot in TWRP again, and I did the FactoryData wipe... "ERROR: CANT MOUNT /DATA";
9- I reboot the system, and are in bootloop...
10- I did all the wipes again, flash the Android 4.4 Factory Image and my Nexus are in Bootloop...
How can I exorcise this demon from my nexus 10 to start normally the Android 4.4? The problem was the Full Data Wipe by TWRP?

felipepx said:
What I did:
1- I rebooted my Nexus 10 in TWRP Recovery and I did all the Wipes... include the Full Data...
2- I downloaded the Android 4.4 Nexus 10 Factory Image
3- I use the Nexus 10 toolkit v1.3.0 to flash the Nexus 10 Android 4.4 factory Image
4- My Nexus 10 are in BootLoop...
5- I did FactoryData wipe, and reboot system now... but, My Nexus are in BootLoop...
6- I downloaded the Android 4.3 Nexus 10 FactoryImage, I use the toolkit again and to flash this...
7- My nexus 10 are in bootloop....
8- I reboot in TWRP again, and I did the FactoryData wipe... "ERROR: CANT MOUNT /DATA";
9- I reboot the system, and are in bootloop...
10- I did all the wipes again, flash the Android 4.4 Factory Image and my Nexus are in Bootloop...
How can I exorcise this demon from my nexus 10 to start normally the Android 4.4? The problem was the Full Data Wipe by TWRP? :crying:
Click to expand...
Click to collapse
Toolkits = 99 Problems and then another 1... Stop using Toolkits... If I had a dime for every post I saw that someone needed help and "toolkit" was involved I'd be rich
Unzip the factory image..
The folder should look like this
{
"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"
}
Open a command prompt and navigate to the directory where you unzipped it
Make sure fastboot is in your path, if not copy it to the folder where you unzipped the factory image
Reboot to the bootloader
at the command prompt run flash-all
This will restore you to an un-rooted fresh 4.4

styckx said:
Toolkits = 99 Problems and then another 1... Stop using Toolkits... If I had a dime for every post I saw that someone needed help and "toolkit" was involved I'd be rich
Unzip the factory image..
The folder should look like this
Open a command prompt and navigate to the directory where you unzipped it
Make sure fastboot is in your path, if not copy it to the folder where you unzipped the factory image
Reboot to the bootloader
at the command prompt run flash-all
This will restore you to an un-rooted fresh 4.4
Click to expand...
Click to collapse
Thanks for you help. I have solved using the Stock Recovery, the Data/Factory reset generate a error, but the Wipe Cache solve this problem. Thanks.

felipepx said:
Thanks for you help. I have solved using the Stock Recovery, the Data/Factory reset generate a error, but the Wipe Cache solve this problem. Thanks.
Click to expand...
Click to collapse
how to use stock recovery?
i choose recovery mode, but i come to a page where an Android lying down with red ! sign.
what should i do next?

minjiet said:
how to use stock recovery?
i choose recovery mode, but i come to a page where an Android lying down with red ! sign.
what should i do next?
Click to expand...
Click to collapse
Press power button + Volume UP to open the StockRecovery options...

Update to 5.1.1 without loosing data

Hello together,
these were the steps to update to 5.1.1 (LMY47X) from 5.0.1 (LRX22C).
It was working for me - without loosing data.
Notes:
OTA didn't work cause of having custom recovery / root.
Maybe it was also in another thread here - but I didn't saw it
It work for me (WIFI-Version) - but might kill your device :crying:
from post #4: In case you using fastboot no very often - look here for more details: http://forum.xda-developers.com/showpost.php?p=60697487&postcount=26 - Thanks the.teejster
Steps
Make sure you have working fastboot on your PC
Download Factory Image and unzip it
Also unzip the included image-volantis-lmy47x.zip
Boot your Nexus 9 into fastboot (Shutdown device; Hold Vol-UP + Power on)
Flash bootloader & reboot
Code:
fastboot flash bootloader bootloader-flounder-3.44.1.0123.img
fastboot reboot-bootloader
Erase everthing but data partition
Code:
fastboot erase system
fastboot erase recovery
fastboot erase cache
fastboot erase boot
fastboot erase vendor
Flash the file (found in the unpacked image-volantis*zip)
Code:
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash cache cache.img
fastboot flash boot boot.img
fastboot flash vendor vendor.img
Reboot device
Optional: Root it again.
Download CF-Autoroot
Use the root-Scripts
Hope it helps and works for you.

One question. I am rooted and have twrp recovery. I this case : Why should we update recovery?

Alternatively, you could remove the "-w" flag from the flash-all.sh script and run it without losing data

A few key prerequisite items are missing in the OP..
I wrote up a similar "how to" over here :
http://forum.xda-developers.com/showpost.php?p=60697487&postcount=26

Hello,
I always upgraded android manually flashing while in fastboot.
Lastly i upgraded to 5.0.2 flawless, then yesterday i download 5.1.1 image and flashed as usual, to not lose data, bootloader/system/boot.
Now everytime i boot my tablet i get this error
{
"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"
}
And lot of apps force close (gmail opens, but when i try to open a mail fc, eurosport same, opens but when i reada news fc, and many other)while others works flawless.
I tried wiping everything, also userdata, but problem not solved.
What can i do?
I read here that someone when upgrade android also erase "vendor", it's the only thing i didnt do, but i never did it.
Please help, finally with 5.1.1 this device flies but now i can't use it!
Thanks.

What about Vendor and recovery ?
Please see my instructions linked about 2 posts up. Follow those exactly and you shouldn't lose any data and the upgrade should be fine.
Sayan1987 said:
Hello,
Lastly i upgraded to 5.0.2 flawless, then yesterday i download 5.1.1 image and flashed as usual, to not lose data, bootloader/system/boot.
Now everytime i boot my tablet i get this error
Click to expand...
Click to collapse

Sayan1987 said:
Hello,
I always upgraded android manually flashing while in fastboot.
Lastly i upgraded to 5.0.2 flawless, then yesterday i download 5.1.1 image and flashed as usual, to not lose data, bootloader/system/boot.
Now everytime i boot my tablet i get this error
And lot of apps force close (gmail opens, but when i try to open a mail fc, eurosport same, opens but when i reada news fc, and many other)while others works flawless.
I tried wiping everything, also userdata, but problem not solved.
What can i do?
I read here that someone when upgrade android also erase "vendor", it's the only thing i didnt do, but i never did it.
Please help, finally with 5.1.1 this device flies but now i can't use it!
Thanks.
Click to expand...
Click to collapse
try fastboot flash vendor vendor.img
For the fc you are experiencing, it is possibly due to the modified ART in 5.1.1 or you check if you have the latest Android Webview

I just thought I would throw this out here in case anyone needs or wants to know...
You do not need to flash the bootloader to upgrade from 5.0.2 to 5.1.1, I can not tell you if this will work coming from 5.0.1
Also after first boot and you flash twrp, you can boot to recovery then immediately reboot back to system. Twrp will install su for you. You'll just need to update the su apk in the market. No need to mess with any kind of su zip anymore.
That's all I have to add to an already great guide.

the.teejster said:
What about Vendor and recovery ?
Please see my instructions linked about 2 posts up. Follow those exactly and you shouldn't lose any data and the upgrade should be fine.
Click to expand...
Click to collapse
laill said:
try fastboot flash vendor vendor.img
For the fc you are experiencing, it is possibly due to the modified ART in 5.1.1 or you check if you have the latest Android Webview
Click to expand...
Click to collapse
Thanks guys flashing vendor fixed everything!!

All the forced closes, heat problems, May I ask are you really stock? No such problems here
Verstuurd vanaf mijn HIGHWAY SIGNS met Tapatalk

Axon 7 not able to install TWRP or lock bootloader

Hello all,
I need help with my Axon 7 (A2017G)
I upgraded my phone to Oreo 8.1 (AospExtended), played with it a bit, but decided to downgrade to 7.1.1 (stock) again.
After I did so, I noticed something different. Firstly when it boots up, this screen appears
{
"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"
}
It goes away after 5 seconds and boots or if I click the vol up or down button, it takes me to this screen
If I choose anything other than Recovery, the phone just boots up
If I choose Recovery, it takes me here
I cannot boot into recovery mode at all. I can't find out how to install TWRP recovery on here at all.
Also If i boot using power+vol down, this appears
Please advise how to install TWRP and lock the bootloader

Have you tried the Axon 7 tool by Djkuz?
It should be able to get you out of this, I'll find the link for you.

Khepralife said:
Hello all,
I need help with my Axon 7 (A2017G)
I upgraded my phone to Oreo 8.1 (AospExtended), played with it a bit, but decided to downgrade to 7.1.1 (stock) again.
After I did so, I noticed something different. Firstly when it boots up, this screen appears It goes away after 5 seconds and boots or if I click the vol up or down button, it takes me to this screen
If I choose anything other than Recovery, the phone just boots up
If I choose Recovery, it takes me here
I cannot boot into recovery mode at all. I can't find out how to install TWRP recovery on here at all.
Also If i boot using power+vol down, this appears
Please advise how to install TWRP and lock the bootloader
Click to expand...
Click to collapse
that is, like, 100% normal. you have stock recovery and that FTM mode just gives you adb. If you can't enter fastboot then you would have to install it via EDL.
But before doing that, why the heck would you want to lock the bootloader? Lol you can just hide the 5 sec screen and sell it (or return to zte, they never check), there's no difference at all
If you're gonna lock anyways, you have to install TWRP via EDL (use EDL Tool by djkuz) then install the "remove inscription" by raystef66 or follow the steps on his guide. Then you will get fastboot. After you do that, just reboot the phone. TWRP should be replaced with stock recovery again. Check if it was (power + vol+) and if you enter stock recovery then go to Fastboot (via "adb reboot bootloader") and do the command to lock
Of course you have to be FULLY stock (no magisk or whatever) or you'll brick your device

Axon 7 tool
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
There is an Axon 7 tool kit as well via another post here.
https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108

Syberclone said:
Have you tried the Axon 7 tool by Djkuz?
It should be able to get you out of this, I'll find the link for you.
Click to expand...
Click to collapse
Thank you

Choose an username... said:
that is, like, 100% normal. you have stock recovery and that FTM mode just gives you adb. If you can't enter fastboot then you would have to install it via EDL.
But before doing that, why the heck would you want to lock the bootloader? Lol you can just hide the 5 sec screen and sell it (or return to zte, they never check), there's no difference at all
If you're gonna lock anyways, you have to install TWRP via EDL (use EDL Tool by djkuz) then install the "remove inscription" by raystef66 or follow the steps on his guide. Then you will get fastboot. After you do that, just reboot the phone. TWRP should be replaced with stock recovery again. Check if it was (power + vol+) and if you enter stock recovery then go to Fastboot (via "adb reboot bootloader") and do the command to lock
Of course you have to be FULLY stock (no magisk or whatever) or you'll brick your device
Click to expand...
Click to collapse
Thank you