Database Info

Why whis problem?

Why whis problem?
{
"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"
}

that is the stock recovery
what were you trying to do?

I'm arrived at step "LOCK STATE - UNLOCKED". When i go on to download " clockwork recovery" and "superuser" mount all on the USB storage, in Recovery i see this.
Look my picture, in background, you see error logo.

No I see the stock recovery logo and that you're trying to flash through the stock recovery.
Sent from my MattedBlues CM7 Google Nexus S!

My Nexus S is UNLOCKED, because i read it in the Bootloader Interface.
I tried to continue the guide right to the end, but when i selected the Recovery i saw this:

mr_magreb said:
I'm arrived at step "LOCK STATE - UNLOCKED". When i go on to download " clockwork recovery" and "superuser" mount all on the USB storage, in Recovery i see this.
Look my picture, in background, you see error logo.
Click to expand...
Click to collapse
After successfully unlocking the bootloader you need to install your custom recovery.
In "Fastboot" mode, (phone connected to computer via usb, phone on bootloader screen) your need to: assuming your working directory is sdk/tools...
at command prompt:
fastboot devices (make sure youo device is detected)
fastboot flash recovery "clockworkrecovery.img goes here" (no quotes)
reboot phone to recovery ( if you reboot back into android recovery will revert back to stock)
If followed the guide, maybe a few steps were missed.

Ok works!!!

Wpt500 wikipad rooted jb 4.2.2

Hi there, I've managed to root Wikipad on newest update
Works only on windows7 ( I used VMware ) unless you find a driver for windows8
1. Install driver in package
2. reboot PC
3. make sure you've got dev mode enabled with usb debugging on
4. read README.txt file
readme states:
1. power off device; RECOVERY : once off hold VOL+ and power for 5 s; pressing VOL- choose fastboot protocol pressing VOL+
2. run 'insecurebootflash.bat'
3. once rebooted go to fastboot protocol again
4. in Windows process manager kill adb and fastboot .exe
5. run 'cwmrecoveryflash.bat'
6. in developer's mode on device enable USB debugging and connect your Wikipad
10. run 'run.bat'
you're rooted
cortex69 via insecure boot made by myself
root method via motorchop (or something, can't remmeber exactly)
Click to expand...
Click to collapse
here's the link:
https://drive.google.com/file/d/0B54wdkjMEJKAVHZtaUhKVmliSDg/view
here's a proof
{
"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"
}
If anyone wants to use it or edit it go ahead. I have only built insecure boot.img
if you're not sure about you can try just to boot to boot.img
fastboot devices
fastboot boot boot.img
fastboot reboot
If anyone who has 4.1.1 installed and rooted Wikipad and is able to download but NOT INSTALL update firmware and pull it out, I am waiting for that someone. I will gladly take over the firmware and do my best to make it customizable and rooted. Might even take a look at kernel

ADB Not recognised

Hi Guys,
Hope you are all well!
I am having some issues with my hopefully-not-late Nexus 5 (hammerhead).
I originally wanted to flash AOSP 7.2.1 however during the process I ran into some troubles.
I flashed TWRP successfully, but TWRP does not start and reboots as it says it is not able to mount /data, etc... hence why the phone takes me to bootloader.
I have downloaded Minimal ADB and Fastboot from XDA, which works fine for fastboot, as it finds my device through "fastboot devices". However, adb does not recognise my Nexus 5, as it retrives an empty list of devices through "adb start-server" then "adb devices".
I have installed the latest drivers from the Google developers website, and I still get a yellow icon for both ADB drivers, i.e. Android ADB and Android Compounded ADB. Bootloader instead, works just fine as it recognises the devices when it is plugged in.
I am stuck trying to understand what I am doing wrong.
I had USB debuginng enabled before flashing TWRP and "lock state" is unlocked on recovery, as well as "secure boot" enabled.
I am using Windows 10.1 if it helps at all!
Thank you so much for your help in advance!
Quick update: I have noticed that when it boots into TWRP the device comes up for a couple of seconds, which means it is getting recognised but I cannot boot into TWRP. This is the error I get:
{
"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"
}

adb does not work in fastboot mode, only fastboot does. Is your data encrypted. Seems your /data partition is corrupted. You could use fastboot format data and see if it fixes it. Note that this will erase all data.

It may be best to use fastboot command to restore a stock rom, confirm everything is work, and start over.
You could also try using a different verizon of twrp.

Flash Idol 6045Y from Linux (phone bricked, not recognized by Eluga nor Mob Upgrade)

Hello,
From yesterday, I am experiencing infinite bootloop witth my idol 6045 Y. I did nothing special, it just began to reboot, and then bootloop.
The system does not succeed to launch : during the launch the screens flashes blue then the phone reboot again.
I can access bootloader mode and recovery (TWRP 3.0.0.1) wihtout any problems. Just the system won't boot. I tried to flash new rom and restore backup - won't work, the phone does not succeed to boot the system and reboot again and again. I don't know if it's a hardware issue or soft one.
I wanted to flash completely through Eluga Panasonic. I foud the downloas link on XDA Idol3, don't rememeber which thread exactly. After having installed it, this one does not recognize the phone, even when the drivers are properly installed.
The steps I follow : I plug the phone into PC in fastboot mode and click on "download" button on the Panasonic soft. Tried opening the soft before and plugging the phone after and vice-versa, does not change anything. Installed fastboot drivers, qualcomm drivers etc... driver in Panasonic soft, no changes.
The Eluga Software does not succeed to communicate with the phone. Now way. I tried all (3 differents computers, windows 10, windows 7, reinstalling drivers etc...)
On linux, I succeed to control the phone through adb or fastboot.
Anyway to reflash completely the phone with these commands ?
Any help grealty appreciated.
{
"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"
}

Shouldn't one use "download" mode rather than "fastboot" in this case ?
I'd try
sudo adb reboot edl
or the phone-off-press-both-volume-buttons-then-plug-usb combo

Support for OP8T: unbrick tool seems to not work, partions can't be mounted

I'm on OP8T, the current status is:
- I can access fastboot
- I can access orangefox recovery (so I could boot to EDL mode, but it seems to not work)
- I can use ADB from my computer
- I can't boot any OS
The problem: I have some partitions that seems corrupted because they aren't automatically mounted when I boot to recovery. I tried to clean data and flash crdroid rom but both operations have errors (all partitions have the error "the partition can't be mounted").
Other problem: Unbrick tool doesn't work, it seems to not recognize the device and not start the flashing. I followed the guide in the official thread https://forum.xda-developers.com/t/...l-to-restore-your-device-to-oxygenos.4180837/ but when I press volume buttons the smartphone doesn't go in EDL mode (because it's not recognized by the unbrick tool). It seems to not go in EDL mode even from recovery (using the "reboot to EDL").
Is there a way to flash stock oxygen os in order to "re-build partitions"?

Try putting your PC in test mode:
Press windows key (on keyboard) + x
This brings up a menu, click on powershell (administrative). Powershell is like a command prompt.
In powershell enter this command:
bcdedit /set testsigning on
Once it says successful, reboot your PC and then try MSM tool again.
Let me know how it goes.
{
"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 solved installing the driver manullay because the phone was recognized as QHUSB_BULK and not as QDLOADER 9008

Try also to look at this thread with proper driver installation.