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.

[Q] L3 can't boot on recovery

Aim: Flash CM9 ROM
Friend's L3 E400, bricked his phone and somehow managed to unbrick it and root it. No idea what kind of ROM he had on. It was GB though.
Got it on my hands today, tried to get into recovery by pressing Vol- + Home + Power. Phone got wiped (not exactly factory, but reset) and was asking for Google info as in starting it up for the first time.
So no access to recovery.
Rebooted to bootloader and flashed CWM recovery. Same thing happened, phone reset itself.
Downloaded the LG KDZ flasher, and the Greek Cosmote KDZ file and flashed it.
Tried to boot into recovery, still no luck.
Phone is no longer rooted. Tried to root using the usual script and i'm getting permission errors.
"adb reboot bootloader" : is working fine
"adb reboot recovery" : resetting phone
"adb reboot fastboot" : same as "adb reboot recovery"
If anyone has any tip for me I would be really greatful!
Tried a lot of things without any luck.
Tomorrow I'll have a discussion with my friend and elaborate a bit more on the issue.

1. Reinstal system
- Download latest system for you from http://lg-phone-firmware.com/index.php?id_mod=11
- Install normal by KDZ
2. Root phone
- Download attachment (maybe you should deactive antivirus for 10 minutes)
- Connect phone with USB Debbuging
- Open SuperOneClick
- Check "rageagainsthecage" in progam right side
- Click root
- After installation click "Yes" (root test), "OK" (su promp confirmation), and "Yes" or "Not" (donation)
- You have root
3. Install CWM
- Do that: http://forum.xda-developers.com/showthread.php?t=2405279
- To open CWM boot phone: Vol Up + Home + Power if not work use Link2SD or other app to "run in recovery mode".
4. Press "thanks" and dance for me!
- Regards!

On my LG L3 e400, it's volume down + home + power. And when the phone vibrate, I release the power button. I wait to be in recovery mode to release the others

leonarf said:
Volume down + home + power. And when the phone vibrate, I release the power button.
Click to expand...
Click to collapse
You should have over 1 MILION likes of that post! Thanks mate, that's works!
I wanna dance for you: *shaking ass*

We managed to root the phone with your way!
We are now at the point where we "install/update" the CWM from ROM manager...
{
"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"
}
Why does it show that i have 2 recoveries installed?
Clicking any of those 3 buttons gives me an error, that it couldn't connect to the cwm's server...
Being more descriptive:
1. Installed the KDZ.
2. Rooted the phone using SuperOneClick.
3. Installed Terminal Emulator and ROM Manager.
4. Tried to use the ROM Manager and got the "can't connect error"
5. Tried VolDown+Home+Power to boot into Recovery. Phone opens up but factory reset. (Terminal Emulator and ROM Manager not installed anymore, but phone is still rooted)
6. Tried the Terminal Emulator to installed the recovery and at "# dd if=/sdcard/cwmrecovery.img of=/dev/block/mmcblk0p17" i get "Cannot open for read. No such file or directory"
7. Tried to boot into bootloader and fastboot install the recovery zip into the recovery partition.. Seems to have worked fine but when booting into recovery phone factory resets again.
PROBLEM SOLVED BY REPEATING STEP 7!
Managed to get in the recovery after all, and therefore installed the CM9. All good! THANK YOU ALL

Cannot restore system, stuck on bootloop

Hey guys,
i recently bought a OP2 from Ebay which is bricked (Stuck on bootloop). The phone wasn't able to boot into Recovery. Only thing worked was Fastboot. I managed to get stock recovery to work using this Guide (Method 3):
https://forums.oneplus.net/threads/updated-28-06-2016-mega-unbrick-guide-for-a-hard-bricked-oneplus-2.347607/
Unfortunately it still stucks in a bootloop. I tryed flashing serveral Stock-ROM's. Does anyone know a solution to fix this?
ADB Sideload give me this output (everytime at around 94%)
{
"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'm kind of new to this.
Greedings
Kynie

Make sure to update the fastboot/bootloader to the newer 3.0/hydrogenos version as all newer ROMs require this to boot.

How can i do this? I have stock bootloader v. 1.0 installed and not able to flash via fastboot cause the phone is locked. Cannot unlock because i'm not able to turn the phone on.

Then just use the standard Qualcomm flash-mode to restore the phone to factory OxygenOS 3.0.2. The utility and 3.0.2 full OTA zip required can be found in this forum if you search.

Then just use the standard Qualcomm flash-mode to restore the phone to factory OxygenOS 3.0.2. The utility and 3.0.2 full OTA zip required can be found in this forum if you search.
Click to expand...
Click to collapse
Thanks for the information. The OTA zip file do I have already. Sadly I can't find such an utility you are talking about. The only thing I found was a chineese (or I think it's chineese) tool which I already tryed but not worked. This tool just brings the stock recovery v 1.0 to life.
Or do you mean a diffrent tool?

In a similar position to you. Phone was working fine (only received it today and tried to get CM13 on it)
My bootloader is unlocked, but phone will no longer boot up, or go into recovery.
I can get it into FastBoot, but it doesn't show up anymore in ADB devices. When in fastboot, the device shows as "Android Device, Marshall London Bootloader interface"
If I switch the phone off and check Device manager it just shows as unknown device and then windows gives me an error message that its not functioning properly.
I have tried to follow this guide https://forums.oneplus.net/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
but it won't allow me to update the device driver, even if I turn off signature for drivers.
The only thing I can get to load is Fastboot. I did at one point have a little penguin on the screen, but haven't replicated that again.
Can anyone help? I'm pulling out my hair

Are you sure you didn't just boot it up into fastboot-ish mode? To be able to flash using that tool you mustn't boot up the phone, make sure it's of and hold volume up when connecting the USB cable, this way the phone will enter chinese factory flash mode at which you can flash using the chinese tool. Also the drivers require you to disable driver signature in windows to install since it's not signed.

Got it working in the end. I just ran the application without bothering with the USB driver stuff and it detected the phone. Then flashed the stock rom and it's now booted.
Still can't get CM13 installed, as I get the error 7 in recovery and that's what got me in the mess!
Sent from my ONE A2003 using Tapatalk

I turned driver signature of and installed drivers succesfully. I run the chineese tool and it finishes succesfully but the phone is still in bootloop. This is frustrating...

Hello do you have find à solution ??

Xiaomi Redmi 2 2014811 bricked after updating SuperSu binary in recovery?

I'm not rly good with electronics etc, my phone came with root access permissions via Security MIUI app so I installed SuperSu to manage it easier (MIUI app reqiured to manually check each app to allow access), no custom ROM or anything installed, the way it happened was
1. updated supersu from google play
2. entered supersu app,it asked me to update su binary
3. I clicked yes through recovery
4. it rebooted and got bootlooped.
It's stuck at the "mi.com" screen when turning on, can't go into recovery, fastboot mode only shows an image of Miui mascot without any fastboot options. I've followed some tutorials online and got the thing below from minimal adb.
{
"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"
}

sufoc said:
I'm not rly good with electronics etc, my phone came with root access permissions via Security MIUI app so I installed SuperSu to manage it easier (MIUI app reqiured to manually check each app to allow access), no custom ROM or anything installed, the way it happened was
1. updated supersu from google play
2. entered supersu app,it asked me to update su binary
3. I clicked yes through recovery
4. it rebooted and got bootlooped.
It's stuck at the "mi.com" screen when turning on, can't go into recovery, fastboot mode only shows an image of Miui mascot without any fastboot options. I've followed some tutorials online and got the thing below from minimal adb.
Click to expand...
Click to collapse
Fastboot will show that android icon only.
No fastboot options will be available there.
Now you need to perform some steps to recover your device..
Note - Your data will be wiped. Also, remove memory card (if any).
Now let's start the process -:
Download MIUI Fastboot ROM file.
Here's the link..
1GB RAM model - http://update.miui.com/updates/v1/fullromdownload.php?d=wt88047_global&b=F&r=global&n=
2GB RAM model - http://update.miui.com/updates/v1/fullromdownload.php?d=wt88047_pro_global&b=F&r=global&n=
Also extract this file and put in C Drive.
Now turn your PC on..
And install latest Mi flash tool. http://api.bbs.miui.com/url/MiFlash
Turn your device off. By pulling battery. (Assuming that your device is in bootloop).
Go to fastboot mode (power + volume down)
Now turn your PC on.
Open Mi flash tool.
Connect your device.
Click on refresh button in flash tool.
Now, it will show some random numbers. (This is your device).
Now, select your ROM fastboot file which you downloaded and extracted.
After that, choose 'flash all' and click Flash..
It will take some time.
After that your device will be rebooted.
Voila! Your device is back to life!

edit: solved

edit: solved

sethidheeraj06 said:
Fastboot will show that android icon only.
No fastboot options will be available there.
Now you need to perform some steps to recover your device..
Note - Your data will be wiped. Also, remove memory card (if any).
Now let's start the process -:
Download MIUI Fastboot ROM file.
Here's the link..
1GB RAM model - http://update.miui.com/updates/v1/fullromdownload.php?d=wt88047_global&b=F&r=global&n=
2GB RAM model - http://update.miui.com/updates/v1/fullromdownload.php?d=wt88047_pro_global&b=F&r=global&n=
Also extract this file and put in C Drive.
Now turn your PC on..
And install latest Mi flash tool. http://api.bbs.miui.com/url/MiFlash
Turn your device off. By pulling battery. (Assuming that your device is in bootloop).
Go to fastboot mode (power + volume down)
Now turn your PC on.
Open Mi flash tool.
Connect your device.
Click on refresh button in flash tool.
Now, it will show some random numbers. (This is your device).
Now, select your ROM fastboot file which you downloaded and extracted.
After that, choose 'flash all' and click Flash..
It will take some time.
After that your device will be rebooted.
Voila! Your device is back to life!
Click to expand...
Click to collapse
The fastboot rom is incorrect for my model (missmatching image and device error)

sufoc said:
The fastboot rom is incorrect for my model (missmatching image and device error)
Click to expand...
Click to collapse
Which device do you have..?
Kindly tell the model no. Such as 2014818.

sethidheeraj06 said:
Which device do you have..?
Kindly tell the model no. Such as 2014818.
Click to expand...
Click to collapse
It's the same as in the title, 2014811 TD-LTE

OxygenOS 12 to 11 : BRICKED, msm: "Param preload failed"

Hello,
I tried to make a fresh install of OxygenOS 11 from 12.
After many steps, I am stuck at the bootloader.
Restart and recovery not working, returning to the bootloader.
I can't have access to adb.
I can use fastboot, but can't "fastboot restart fastboot", it simply restart the phone and go to the bootloader.
I tried with MSM and it failed with "Param preload failed".
Can somebody help me ?
{
"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 was in a similar position today and fixed it by using the USB cable that came with the phone and I plugged it into a different USB port than the one I was using. I did, however, have a different error.

RyFax said:
Hello,
I tried to make a fresh install of OxygenOS 11 from 12.
O After many steps, I am stuck at the bootloader.
Restart and recovery not working, returning to the bootloader.
I can't have access to adb.
I can use fastboot, but can't "fastboot restart fastboot", it simply restart the phone and go to the bootloader.
I tried with MSM and it failed with "Param preload failed".
Can somebody help me ?
View attachment 5604615
Click to expand...
Click to collapse
I would try to boot a recovery, sideload an aosp rom and then try to msm, maybe flashing oos 11 firmware/partitions 1 by 1 using an extracted payload before even

RyFax said:
Hello,
I tried to make a fresh install of OxygenOS 11 from 12.
After many steps, I am stuck at the bootloader.
Restart and recovery not working, returning to the bootloader.
I can't have access to adb.
I can use fastboot, but can't "fastboot restart fastboot", it simply restart the phone and go to the bootloader.
I tried with MSM and it failed with "Param preload failed".
Can somebody help me ?
View attachment 5604615
Click to expand...
Click to collapse
Boot into twrp, then install OOS11 zip.
Some error message may occurred.
Just ignore it, reboot see if it can boot normally.
If not working, install OOS11 zip into both slot.

Change your USB cable and/or USB port. Your phone isn't bricked.

The param preload error occurs when u dont have proper drivers installed bro. Try reinstalling the drivers. Then install driver attached in this message. To install it follow the instructions below.
1. Download the attached file.
2. Extract it to desktop.
3. Connect ur oneplus phone to ur computer via usb cable.
4. Open device manager in a separate window.
5. Hold both volume keys and power key together for a while, when the computer recognises the phone in EDL mode, go to the device manager.
6. There will be an unknown device called QHS bulk.
7. Right Click and select update driver.
8. Select browse my computer for drivers.
9. Select browse and navigate to the extracted folder.
10. Select next and install.
After all the above process has been done, disconnect ur phone, restart the device and plug it again opening the msm tool and connect through EDL mode and flash ur phone. The param processing error will not come.
Kindly post ur questions next time in the Q&A page and read the instructions in the unbrick tool page of the forum before attempting to post questions bro.
[OP8PRO][OOS 11AA/BA/DA] Unbrick tool to restore your device to OxygenOS
Disclaimer: By attempting any of the processes listed in this thread you accept full responsibility for your actions. I will not be held responsible if your device stops working, catches fire, or turns into a hipster and claims to have been...
forum.xda-developers.com
The above link is for the unbrick tool page, here is the page with all the flashing tools and drivers.

Use the red OEM USB cable. I was getting the same error, and switching to the red OEM USB cable fixed it.