Develop Bugs

[Q] Nexus 7 2013 Problems...

A couple days ago, I was browsing the internet, then my Nexus 7 2013 suddenly froze. I did a reboot, but it got stuck on the boot animation. So, since it wasn't booting back up, I tried to load from one of my old backups. I managed to get the back up to work, however I needed to download the 4.4.2 update OTA through TWRP. It never officially said it finished, but I restarted the tablet and it's been stuck on the Google screen. I've went to fastboot, but it wont let me into TWRP recovery since it only loads the Google screen. I've also tried this ( http://www.androidbeat.com/2013/11/flash-factory-image-nexus-device/#.U0o0z3nn_0x ) and it didn't work.
When I try to reset through WugFresh, I've flashed KRT16S 4.4 and KOT49H 4.4.2, and and I get
Code:
sending 'bootloader' (3911 KB)...
FAILED (command write failed (Invalid argument))
finished. total time: 0.001s
rebooting into bootloader...
FAILED (command write failed (Unknown error))
finished. total time: 0.638s
archive does not contain 'boot.sig'
error: out of memory
I've also tried a few other ways of restoring to factory settings but nothing has worked :crying:
Any help is much appreciated!

I deleted my OS on my nexus... Oops? what I did is I did a ADB Sideload custom rom but if you can't get into twrp you are screwed. Maybe send it to Asus or return it if it is under warranty and get a new one. Just remember don't listen to me, in just a child on a tablet at night trying to unpack full posting privileges.
Sent from my Nexus 7 using XDA Premium 4 mobile app

Any other suggestions..?

Couldn't you go into your bootloader, erase your recovery using ADB, and then flash it?
Sent from my SAMSUNG-SGH-I747 using Tapatalk

codemonkey98 said:
Couldn't you go into your bootloader, erase your recovery using ADB, and then flash it?
Sent from my SAMSUNG-SGH-I747 using Tapatalk
Click to expand...
Click to collapse
I don't think I've tried that yet. Do you have a link on how to do it? I'm not all that experienced...

PieceofSlice said:
I don't think I've tried that yet. Do you have a link on how to do it? I'm not all that experienced...
Click to expand...
Click to collapse
A tutorial can be found here. The tutorial guides you to get the Nexus 7 (2012) original files, please get the actual Nexus 7 (2013) files.

codemonkey98 said:
A tutorial can be found here. The tutorial guides you to get the Nexus 7 (2012) original files, please get the actual Nexus 7 (2013) files.
Click to expand...
Click to collapse
Alright, thanks I'll try this as soon as I get home. Though, when it says to type "fastboot flash bootloader bootloader-grouper-3.34.img" will I just be able to substitute the new 4.4.2 factory image stuff instead of the older? Also, does it matter that I can't set my Nexus into debugging mode?

PieceofSlice said:
Alright, thanks I'll try this as soon as I get home. Though, when it says to type "fastboot flash bootloader bootloader-grouper-3.34.img" will I just be able to substitute the new 4.4.2 factory image stuff instead of the older? Also, does it matter that I can't set my Nexus into debugging mode?
Click to expand...
Click to collapse
Yes you will need to replace by the "bootloader-grouper-3.34.img" by the name of the img in your device archive.
For my Razorg / deb (The LTE version) it will be :
Code:
fastboot flash bootloader bootloader-deb-04.02.img
and
Code:
fastboot -w update image-razorg-kot49h.zip
And for the Razor / flo (Wifi version) it will be :
Code:
fastboot flash bootloader bootloader-flo-flo-04.02.img
and
Code:
fastboot -w update image-razor-kot49h.zip
For reminder, factory images can be found there : https://developers.google.com/android/nexus/images?hl=FR#razor
Debugging mode / ADB is not nessesary until you write the bootloader in fastboot mode
But don't forget to install drivers, except if you already do this step
I hope i helped you.

PieceofSlice said:
Alright, thanks I'll try this as soon as I get home. Though, when it says to type "fastboot flash bootloader bootloader-grouper-3.34.img" will I just be able to substitute the new 4.4.2 factory image stuff instead of the older? Also, does it matter that I can't set my Nexus into debugging mode?
Click to expand...
Click to collapse
You mustn't flash grouper bootloader on flo/deb!
Only the bootloader that belongs to your firmware.
Yet I'm not sure if your USB driver is installed properly.
Are you 100% sure it is?

that link is great!...
Don't worry you are not screwed...just follow the link the person above posted about how to hard reset your nexus device. Since you have a 2013 nexus just make sure that you download the correct nexus image and make sure you flash the correct files and you will be fine. I have used that same tutorial on my nexus 7 2013 flo and deb to fix issues.
Trust me it will work...
-droidshadow

codemonkey98 said:
A tutorial can be found here. The tutorial guides you to get the Nexus 7 (2012) original files, please get the actual Nexus 7 (2013) files.
Click to expand...
Click to collapse
When following the tutorial, I type in "fastboot erase boot." However, when I do that it gives me this error...
Code:
C:\android-sdk\platform-tools>fastboot devices
04988e98 fastboot
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
I have the SDK installed correctly and everything in the correct spot, right?

PieceofSlice said:
When following the tutorial, I type in "fastboot erase boot." However, when I do that it gives me this error...
Code:
C:\android-sdk\platform-tools>fastboot devices
04988e98 fastboot
C:\android-sdk\platform-tools>fastboot erase boot
erasing 'boot'...
FAILED (command write failed (Invalid argument))
finished. total time: 0.017s
I have the SDK installed correctly and everything in the correct spot, right?
Click to expand...
Click to collapse
The files in folder look fine now
Did you update your SDK manager to the newest version? (Especially sources regarding API 18 and 19 are important). Move the firmware files elsewhere before, because by major updates whole platform-tools folder will be replaced.
Try to use different USB port on your PC. Once when you are in fastboot mode, does this command work?
Code:
fastboot reboot-bootloader
tetakpatalked from Nexus 7

Well, just my 2 cents... I read somewhere else on this forum from someone having the same issue that replacing the cable he used actually did the trick for him. You might try that. Won't hurt..

tetakpatak said:
The files in folder look fine now
Did you update your SDK manager to the newest version? (Especially sources regarding API 18 and 19 are important). Move the firmware files elsewhere before, because by major updates whole platform-tools folder will be replaced.
Try to use different USB port on your PC. Once when you are in fastboot mode, does this command work?
Code:
fastboot reboot-bootloader
tetakpatalked from Nexus 7
Click to expand...
Click to collapse
I haven't updated the SDK. So when I do, just be sure to move the image files and whatnot, and then put them back after the update, correct?
I'll be doing this later

PieceofSlice said:
I haven't updated the SDK. So when I do, just be sure to move the image files and whatnot, and then put them back after the update, correct?
I'll be doing this later
Click to expand...
Click to collapse
Yes just move your firmware files (bootloader and image.zip) out of the folder.
Updating is easy, double-click SDK manager application (you will see it as soon as you open SDK folder) and there you can choose what to update. You just need an internet connection.
tetakpatalked from Nexus 7

i am intrigued to see if this person was able to fix his tablet...
I think that all the suggestions above are very good ones. Making sure he has the most updated software...
Make sure he tries another usb cable or make sure you are using the stock usb cable.
And trying another usb port...
However from this fastboot devices output it did show that his device was connected which i don't think would happen with a default usb cable.
Okay so here is what i think may be causing the problem.
I think you need to unlock your bootloader before you can erase it. Try following this tutorial -> http://forum.xda-developers.com/showthread.php?t=1907796
You have to unlock it before you can erase the bootloader. So you need to do:
command 1: adb reboot-bootloader
command 2: fastboot oem unlock
then you can do:
command 3: fastboot erase boot
try that and see if that helps....
If that does not work then try flashing the new bootloader over the old one.
I hope this has been helpful.
Don't give up...
-droidshadow

LOL, good point @droidshadow!
Hey, @PieceofSlice, is your bootloader possibly still locked? Please make photo of the text in bootloader mode on bottom left and post screenshot of it.
tetakpatalked from Nexus 7

droidshadow said:
i am intrigued to see if this person was able to fix his tablet...
I think you need to unlock your bootloader before you can erase it. Try following this tutorial -> http://forum.xda-developers.com/showthread.php?t=1907796
You have to unlock it before you can erase the bootloader. So you need to do:
command 1: adb reboot-bootloader
command 2: fastboot oem unlock
then you can do:
command 3: fastboot erase boot
try that and see if that helps....
-droidshadow
Click to expand...
Click to collapse
I'm pretty sure my bootloader is unlocked, my tablet has the unlocked padlock at the Google screen. I'll take your advice and try a new cord too

droidshadow said:
i am intrigued to see if this person was able to fix his tablet...
You have to unlock it before you can erase the bootloader. So you need to do:
command 1: adb reboot-bootloader
command 2: fastboot oem unlock
then you can do:
command 3: fastboot erase boot
try that and see if that helps....
If that does not work then try flashing the new bootloader over the old one.
-droidshadow
Click to expand...
Click to collapse
So I actually tried to do this because, even though I updated the Android SDK, when I typed in "fastboot erase boot", it basically froze on "erasing bootloader." When I tried the first command, "adb reboot-bootloader", it said
Code:
C:\android-sdk\platform-tools>adb reboot-bootloader
error: device not found
So I take it I have a problem with ADB or something?

There are two generally different modes by using Android Debugging Bridge:
1. ADB (device booted in OS or recovery)
2. FASTBOOT (device in bootloader mode)
When I tried the first command, "adb reboot-bootloader", it said
Code:
C:\android-sdk\platform-tools>adb reboot-bootloader
error: device not found
So I take it I have a problem with ADB or something?
Click to expand...
Click to collapse
So, if you have tried this command above when your device was in bootloader mode, it was wrong command, as the command should have started with "fastboot...." instead of "adb..."
If the device was booted in OS, this command would have been correct and such response could have two reasons:
* USB debugging was not enabled
* drivers are not installed properly
After updating SDK manager, it is always highly recommended to check if the driver still works.
PieceofSlice said:
when I typed in "fastboot erase boot", it basically froze on "erasing bootloader."
Click to expand...
Click to collapse
Careful, mate, I hope you didn't try to erase your bootloader? That would have fatal results. Actually "boot" means kernel! As long as your bootloader is there = your tab will be fine.
By flashing a factory image the order of doing things is
* erase all (kernel, system, userdata etc)
* flash new bootloader
* reboot bootloader
* flashing whole factory image zip file
tetakpatalked from Nexus 7

[6039] Custom Recovery - TWRP - 2.8.7.0

Hello guys/girls,
I have built successfully a TWRP 2.8.7.0 recovery for Alcatel Idol 3 6039 4.7 inch (tested on 6039y). The recovery image can be downloaded from here:
Edit (30.09.2015): I think this will be the final version of the recovery. The date/time issue is fixed now and additionally small adjustments to the initialization process have been added.
twrp_recovery-2.8.7.0-idol347.img
md5sum: 175be787d67839d15beab7285279a72c
Please note that the latest OTA updates from the end of August and the start of September disable the fastboot commands which means that this recovery cannot be started as described below (if your device is already upgraded)!!! The device will return FAILED (remote: unknown command) when you try to boot the recovery.
If you find yourself in this situation but want root access please see this thread.
It can be tested as follows:
- enable the developer options
- allow the USB debugging
- reboot to bootloader:
Code:
adb reboot-bootloader
- start the recovery image with:
Code:
fastboot -i 0x1bbb boot twrp_recovery-2.8.7.0-idol3-6039y.img
Please do not forget first to make a backup of the system partition by selecting System Image from the Backup settings. The backup image will be needed in order to install future OTA updates if available, so please keep it in a safe place.

petrov.0 said:
Hello guys/girls,
I have built successfully a TWRP 2.8.7.0 recovery for Alcatel Idol 3 6039 4.7 inch (tested on 6039y). The recovery image can be downloaded from here:
twrp-2.8.7.0-idol3-6039y.img
It can be tested as follows:
- enable the developer options
- allow the USB debugging
- reboot to bootloader:
Code:
adb reboot-bootloader
- start the recovery image with:
Code:
fastboot -i 0x1bbb boot twrp_recovery-2.8.7.0-idol3-6039y.img
Please do not forget first to make a backup of the system partition by selecting System Image from the Backup settings. The backup image will be needed in order to install future OTA updates if available, so please keep it in a safe place.
Click to expand...
Click to collapse
Great job! A couple of the outstanding issues on the 6045 TWRP are that the date/time stamp of the backup is screwy because of a known bug with 64 bit chips and also the recovery identifies every model as a Y model (you can see in recovery.log) because the boot.img for a Y was used. Yours may also encounter one or both of these issues. I suggested in the other thread they consider building for each model using the individual boot.img but didn't get a reply.

famewolf said:
Great job! A couple of the outstanding issues on the 6045 TWRP are that the date/time stamp of the backup is screwy because of a known bug with 64 bit chips and also the recovery identifies every model as a Y model (you can see in recovery.log) because the boot.img for a Y was used. Yours may also encounter one or both of these issues. I suggested in the other thread they consider building for each model using the individual boot.img but didn't get a reply.
Click to expand...
Click to collapse
Yes, the date/time stamp is wrong. The device model however is not much . The ro.product.model is shown as idol347. It is a custom build after all.

I tried to use TWRP on my 6039Y and it's not working. Well to be more precise I don't know if your custom recovery works or not because I can't seem to get past the first step. Here's what happened
Code:
adb reboot-bootloader
So the device reboots, but doesn't get past the first screen (Alcatel OneTouch Powered by Android) even after a minute or so. Should I let it more time or is this the bootloader?
Then i try this
Code:
fastboot -i 0x1bbb devices
This seems to have no effect, the command seems to execute without any consequence and I'm able to type a new line in cmd
And if I try
Code:
fastboot -i 0x1bbb boot twrp_recovery-2.8.7.0-idol3-6039y.img
I get a <waiting for device> and I'm stuck on that line, having to Ctrl+C to stop the command and reboot the phone by holding power
Yes I know, I'm on Windows and it might be the drivers causing this. However I have installed the ADB drivers through SDK just fine. I would like to be able to install the drivers from the phone but the only options I see in the USB connection settings are MTP, PTP and Charging only. Any idea on how to get that CD-Rom option to appear?
Thanks for your help in advance

Rorshan said:
I tried to use TWRP on my 6039Y and it's not working. Well to be more precise I don't know if your custom recovery works or not because I can't seem to get past the first step. Here's what happened
Code:
adb reboot-bootloader
So the device reboots, but doesn't get past the first screen (Alcatel OneTouch Powered by Android) even after a minute or so. Should I let it more time or is this the bootloader?
Click to expand...
Click to collapse
This is OK it's in the bootloader.
Rorshan said:
Code:
fastboot -i 0x1bbb devices
This seems to have no effect, the command seems to execute without any consequence and I'm able to type a new line in cmd
And if I try
Code:
fastboot -i 0x1bbb boot twrp_recovery-2.8.7.0-idol3-6039y.img
I get a <waiting for device> and I'm stuck on that line, having to Ctrl+C to stop the command and reboot the phone by holding power
Click to expand...
Click to collapse
Looks like a driver issue. I use Linux no problems here no need of drivers too.
Rorshan said:
Yes I know, I'm on Windows and it might be the drivers causing this. However I have installed the ADB drivers through SDK just fine. I would like to be able to install the drivers from the phone but the only options I see in the USB connection settings are MTP, PTP and Charging only. Any idea on how to get that CD-Rom option to appear?
Thanks for your help in advance
Click to expand...
Click to collapse
Try with the drivers posted by @famewolf here or with these.
Meanwhile the first post has been updated with a new link. Please download the recovery again. There was a bug with the screenlock in the previous build. The screenlock is disabled in this one.

Alright I'll make sure to try that. Otherwise I guess I'll just try with Linux or Mac. Thanks
Sent from my 6039Y using Tapatalk

Rorshan said:
Alright I'll make sure to try that. Otherwise I guess I'll just try with Linux or Mac. Thanks
Sent from my 6039Y using Tapatalk
Click to expand...
Click to collapse
A quick check of the dirvers shared by @famewolf shows that they should work on windows with 6039y (at least to start the recovery). These are the vendor and the product IDs of 6039y from one of the INF files in the archive so the drivers should be compatible with the device when is in the bootloader (they match with those reported by the device).
Code:
USB\VID_1BBB&PID_D00D.DeviceDescRelease="Android Sooner Single ADB Interface"
I don't see however the IDs for the recovery mode:
Code:
[726530.487224] usb 1-4: New USB device found, idVendor=18d1, idProduct=4ee2
and the IDs from when the phone is connected as MTP device:
Code:
[726695.431624] usb 1-4: New USB device found, idVendor=1bbb, idProduct=af2b
but I hope everything to be OK. Good luck.

Why is this thread in Mi Note pro development section ? It's about idol 3 6039....

frankee207 said:
Why is this thread in Mi Note pro development section ? It's about idol 3 6039....
Click to expand...
Click to collapse
I asked the moderator to move it to the development section of Idol 3, but something went wrong. The moderator is informed about this. Now I'm waiting to be moved to the Idol 3 forum again.

petrov.0 said:
I asked the moderator to move it to the development section of Idol 3, but something went wrong. The moderator is informed about this. Now I'm waiting to be moved to the Idol 3 forum again.
Click to expand...
Click to collapse
Yeah I was thinking that's a bit strange! Got me excited thinking theres newer TWRP for Mi Note Pro xD

Cyanogen recovery
Here is a download link of the cyanogen recovery (built from the 12.1 branch). It's useless. But if someone wants to try it. The md5sum of the image is 3ff21bbf5ece48422f3135fa583eaa78

Should this work on 6039J?

Has not been tested on 6039J until now, but you can try it. Don't rush with backups wipes etc. (because the partition table can be different) just boot with it through fastboot. You can examine your partitions with the recovery from the repartitioning guide which contains gdisk (if your phone is not rooted yet). But this is only if this one works with your device. By the way what is the J version ? Dual sim ?

I'm trying to create a backup of the 6039S (North American 16GB, 1-SIM/1-SD model), and am having some issues with fastboot.
ADB is working flawlessly, and I can boot into the bootloader. As petrov.0 noted earlier in this thread there is no dedicated bootloader screen, just the onetouch splashscreen displays.
I can enter:
Code:
fastboot -i 0x1bbb devices
and the device shows up: "6346ce6d fastboot".
However, when I go to run any of the OEM commands, e.g.
Code:
fastboot -i 0x1bbb oem device-info
it shows:
...
FAILED (remote: unknown command)
finished. total time: 0.016s
Any ideas? By all appearances the alcatel driver seems to be working, but could this still be a driver issue?

Bradlee22 said:
I'm trying to create a backup of the 6039S (North American 16GB, 1-SIM/1-SD model), and am having some issues with fastboot.
ADB is working flawlessly, and I can boot into the bootloader. As petrov.0 noted earlier in this thread there is no dedicated bootloader screen, just the onetouch splashscreen displays.
I can enter:
Code:
fastboot -i 0x1bbb devices
and the device shows up: "6346ce6d fastboot".
However, when I go to run any of the OEM commands, e.g.
Code:
fastboot -i 0x1bbb oem device-info
it shows:
...
FAILED (remote: unknown command)
finished. total time: 0.016s
Any ideas? By all appearances the alcatel driver seems to be working, but could this still be a driver issue?
Click to expand...
Click to collapse
Probably this problem is not related to the driver. Something is different in your device. By the way can you boot this recovery ?

petrov.0 said:
Probably this problem is not related to the driver. Something is different in your device. By the way can you boot this recovery ?
Click to expand...
Click to collapse
No, I can't boot this TWRP recovery either. I get the same error message: FAILED (remote: unknown command).

I must admit that the internal sd card has not been mounted properly until now. I found the proper way however how to do it. The first post has been updated and now contains a link to the recovery which includes the corrections. The configuration files with which I do these recoveries, are also publicly available now and can be found here. Nothing special but ...

Bradlee22 said:
No, I can't boot this TWRP recovery either. I get the same error message: FAILED (remote: unknown command).
Click to expand...
Click to collapse
Any output from
Code:
fastboot -i 0x1bbb getvar secure
fastboot -i 0x1bbb getvar version-bootloader
fastboot -i 0x1bbb getvar all

petrov.0 said:
Any output from
Code:
fastboot -i 0x1bbb getvar secure
fastboot -i 0x1bbb getvar version-bootloader
fastboot -i 0x1bbb getvar all
Click to expand...
Click to collapse
Nothing useful from any of those.
Code:
fastboot -i 0x1bbb getvar secure
Output is:
secure:
finished. total time: 0.016s
Code:
fastboot -i 0x1bbb getvar version-bootloader
Output is:
version-bootloader:
finished. total time: -0.000s
Code:
fastboot -i 0x1bbb getvar all
Output is:
all:
finished. total time -0.000s
P.S. Thanks for your help. It's much appreciated!

Bradlee22 said:
Nothing useful from any of those.
Click to expand...
Click to collapse
remote: unknown command is a protocol error, as long as I understand the source. What is the host OS ? Windows ... which version ... did you try to start cmd.exe as administrator ? Which drivers you use ? On what port is your device connected (USB 2 or USB 3). Do you have access to a Linux box ? If you have try from there. I'm not sure how Windows handles the sharing of the USB ports with a virtual machine. You can try to start a distro in VirtualBox, which have option to expose a device connected on the host to the guest system and then to try fastboot from there.

Enter Bootloader Mode with Hardware Keys on H815 international

Hello,
on my h815 international I unlocked the bootloader and entered bootloader mode:
$ adb reboot bootloader
and booted TWRP:
[email protected]:~/Downloads$ fastboot boot twrp-3.0.2-1-h815.img
downloading 'boot.img'...
OKAY [ 0.831s]
booting...
OKAY [ 0.599s]
finished. total time: 1.431s
[email protected]:~/Downloads$
I was under the (wrong) impression that I installed TWRP and continued with the instructions for installing LineageOS, i.e. wiping System, Cache, and Data partitions.
After I realized that this removed the lineage os zip file, I rebooted (which was apparently a very bad idea).
Now matter how I boot the h815 always hangs at the initial LG logo (saying Bootloader state: bootloader unlocked! in the top left corner) -- except when I start with vol-down+Power this brings me in a setting which allows to reset to factory settings. But this does not bring the system in a bootable mode either.
Needless to say that adb and fastboot do not work and respond with
fastboot:
< waiting for device >
adb:
error: device not found
I think I need to enter bootloader mode with my LG G4 h815 with hardware keys (i.e. w/o adb reboot bootloader).
I tried the vol-up+power button method described here
http://www.android.gs/reboot-lg-g4-into-fastboot-mode/
without success.
Any idea on how to get into fastboot mode with hardware keys or recover the device is very welcome
Thanks
Rainer

If you have access to TWRP, boot into twrp and use "adb push" to get your lineage os zip from your computer...

onotor said:
If you have access to TWRP, boot into twrp and use "adb push" to get your lineage os zip from your computer...
Click to expand...
Click to collapse
Unfortunately, I do not have access to TWRP anymore, the boot process stops right after the LG logo.

rdorsch said:
Unfortunately, I do not have access to TWRP anymore, the boot process stops right after the LG logo.
Click to expand...
Click to collapse
Can you atleast flash a kdz ?

onotor said:
Can you atleast flash a kdz ?
Click to expand...
Click to collapse
For that I need the LG flash tool, it does not work with Linux, correct?

rdorsch said:
For that I need the LG flash tool, it does not work with Linux, correct?
Click to expand...
Click to collapse
You can use LGUP on windows

rdorsch said:
Hello,
on my h815 international I unlocked the bootloader and entered bootloader mode:
$ adb reboot bootloader
and booted TWRP:
[email protected]:~/Downloads$ fastboot boot twrp-3.0.2-1-h815.img
downloading 'boot.img'...
OKAY [ 0.831s]
booting...
OKAY [ 0.599s]
finished. total time: 1.431s
[email protected]:~/Downloads$
I was under the (wrong) impression that I installed TWRP and continued with the instructions for installing LineageOS, i.e. wiping System, Cache, and Data partitions.
After I realized that this removed the lineage os zip file, I rebooted (which was apparently a very bad idea).
Now matter how I boot the h815 always hangs at the initial LG logo (saying Bootloader state: bootloader unlocked! in the top left corner) -- except when I start with vol-down+Power this brings me in a setting which allows to reset to factory settings. But this does not bring the system in a bootable mode either.
Needless to say that adb and fastboot do not work and respond with
fastboot:
< waiting for device >
adb:
error: device not found
I think I need to enter bootloader mode with my LG G4 h815 with hardware keys (i.e. w/o adb reboot bootloader).
I tried the vol-up+power button method described here
http://www.android.gs/reboot-lg-g4-into-fastboot-mode/
without success.
Any idea on how to get into fastboot mode with hardware keys or recover the device is very welcome
Thanks
Rainer
Click to expand...
Click to collapse
Power off
Plugin usb cable.
Press volume up
You should see download mode
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Power off
Plugin usb cable.
Press volume up
You should see download mode
Click to expand...
Click to collapse
Indeed that makes a difference (I had to Press volume up and then plugin usb cable):
This brings me into a "firmware update" mode.
How do I continue from there, this does not seem to be the standard bootloader mode, at least
[email protected]:~$ fastboot boot ~/Downloads/twrp-3.0.2-1-h815.img
< waiting for device >
^C
[email protected]:~$
still does not reach the h815.

rdorsch said:
Indeed that makes a difference (I had to Press volume up and then plugin usb cable):
This brings me into a "firmware update" mode.
How do I continue from there, this does not seem to be the standard bootloader mode, at least
[email protected]:~$ fastboot boot ~/Downloads/twrp-3.0.2-1-h815.img
< waiting for device >
^C
[email protected]:~$
still does not reach the h815.
Click to expand...
Click to collapse
This mode is different. Use lgup to flash a kdz matching your device. You will loose root and all settings but it should bring back your g4 to live.
Guide:
https://forum.xda-developers.com/g4/general/guide-lg-g4-stock-firmware-to-stock-kdz-t3107848
.
Sent from my LG-H815 using XDA Labs

Hello, I cannot get into fastboot. I have tried by holding vol down and plugging in cable and with TWRP.
The result is:
Fastboot mode
Product name - msm8992_p1_spr_us
Varient - msm8992_p1_spr_us Toshiba 32gb
HW version - rev_10
Bootlader version -
Baseband version -
Carrier info - n/a
Serial number - ***********
Signing - production
Secure boot - disabled
Lock state - locked
[1110]
[1160] fastboot mode started
[1120] fastboot: processing commands
Any help would be greatly appreciated.

Help with root for Alldocube M5X Pro

I am in over my head once more and could use help from someone more experienced.
The problem?
I bought an Alldocube M5X Pro tablet for my kids. First thing I did was root it using Magisk. I found the stock ROM, extracted the boot.img file, patched it with magisk manager, unlocked the bootloader and then used the fastboot command to flash the modified boot.img. Smooth sailing, worked flawlessly, kids were happy. 2 kids, 1 tablet, the happiness didn't last too long. They both wanted to use the tablet all the time. So when I found a sales promotion for the same model tablet, I decided to buy one more. Tablet #2 arrives, also an Alldocube M5X Pro, model T1006, Kernel version 3.18.60, Android version 8.0.0, same as tablet #1. I go through the same steps, but when I try to flash the modified boot.img file on the new tablet, it tells me Remote: Flash WRITE failure.
Here's what I did, step by step:
1. I verified that the 2nd tablet had the same build number as the 1st tablet. It did: T1006_V1.01_20200504
2. I enabled USB debugging in developer options and set the OEM Unlock option to ON
3. I trusted the connected computer in order to use the adb commands
4. I rebooted to the bootloader and executed the command Fastboot OEM unlock
C:\adb>fastboot oem unlock
...
(bootloader) Start unlock flow
OKAY [ 7.825s]
finished. total time: 7.826s
Click to expand...
Click to collapse
5. I executed the command Fastboot Flash boot magisk_patched.img with the img file in the path from where I'm running the command
C:\adb>fastboot flash boot magisk_patched.img
target reported max download size of 134217728 bytes
sending 'boot' (10253 KB)...
OKAY [ 0.468s]
writing 'boot'...
FAILED (remote: flash write failure)
finished. total time: 0.633s
Click to expand...
Click to collapse
6. I've tried erasing the cache and user data partitions from the stock recovery and repeating step 5, but received the same error.
And that's where I'm stuck. The tablet can reboot from there, will detect tampering and proceed to run an erase command and starts with the Android Setup tutorial.
Just for the hell of it I tried flashing the stock ROM using the SP Flash tool for Mediatek devices, which works just fine. I then tried tried flashing an older build (0304) but still received the same error when trying to flash the boot.img
I also tried flashing a custom recovery as well as booting a recovery.img but in both cases the tablet ends up booting normally, I assume because the custom recovery isn't compatible with this device.
Everything I find online about flash write failure errors seems to indicate a defective emmc however most of those are specific to the Nexus 5 phone. The difference here seems to be that I can unlock the bootloader just fine, it stays unlocked as far as I can tell and I can overwrite with a new ROM, so I'm thinking the emmc is fine.
I'm just trying to puzzle this together from what I can find online, but I could really use the help of someone with more insight into the inner workings of Android.
Any help would be greatly appreciated.

After flashing 4 different ROMs, formatting the emmc completely and doing lord knows what else, it finally dawned on me that I could simply flash the patched boot image using the SP Flash tool instead of via Fastboot. It does wipe the data, and starts the Android setup wizard, but once that is completed, I was able to install Magisk Manager and download the missing files. The device rebooted after that and came back with systemless root.
Problem solved.

Redmi note 5 pro stuck in bootloop and cant access to recovery please help $$

I have a Redmi Note 5 Pro from last Saturday while uploading Instagram stories as usual, the phone decided to crash. So I turned it off and back on though got stuck with MI Logo and Bootloop. The device said it's unlocked but apparently seems not to.
I CANNOT go into recovery mode.
I CANNOT flash any recovery too.
I have connected the device to my laptop (Windows 10) through fastboot try to flash any recovery: OrangeFox, TWRP, no success.
I either run a powershell or run CMD as Admin
This is the error:
c:\adb fastboot flash recovery recovery.img
Sending 'recovery' (31161 KB) OKAY [ 0.669s]
Writing 'recovery' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
So I try this command: fastboot boot recovery.img
It loads the recovery either TWRP or OrangeFox but only the Logo nothing else.
It doesn't RUN any official MIUI recovery.
So, now I can use ADB commands.
The phone is seen connected to Windows 10 as USB but I guess not MTP mode but only as charging mode.
In the "Safely Remove Hardware" section I can see the device connected and its name as Redmi Note 5 Pro.
Of course I can't see the device in the Explorer and any folder as the OS hasn't loaded at all.
Now, though, I can run ADB commands, so I typed: run devices and it says it's in recovery mode, also with the number of the device.
Then with ADB SHELL LS command
I can see the folder tree
With Push and Pull commands, I can copy folders, but cannot access and copy the content of SDCARD and STORAGE.
I know those folders are protected even though my phone should be unlocked but apparently it is not then.
It's really ridiculous that there is no a way around this.
Why, if I am the owner the unlock process have to reset phone data?
It's so stupid! They should have developed a public/private key or a long key to unlock those folder by registering your phone with SN and IMEI number.
So surprised Google and any brand don't do that.
If I connect the device in fastboot mode, I have those details:
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.006s]
Finished. Total time: 0.006s
Is there a WAY with lower level commands or software to access to data with "write protected" inside the phone memory?
I would love to recover my Whatsapp folder and my DCIM folder with every files in those.
Or the only solution is to give the Device to experts and do the CHIP Off recovery data?
Will MiFlash with a MIUI rom with save user data option actually save my data and hence Whatsapp and DCIM folder and its content inside?
Please Help!
If anyone can HELP to successfully recover my data seriously I would be more than happy to give a compensation via PayPal cause I would truly appreciated the infinite effort and help!
Thanks in advance to anyone who can sponsor the cause!
I am so pissed as the phone should be under 2 years warranty but of course no brand would cover and help you through those issues!
Such A PITY!
Kind regard,
Michael

supermike23 said:
I have a Redmi Note 5 Pro from last Saturday while uploading Instagram stories as usual, the phone decided to crash. So I turned it off and back on though got stuck with MI Logo and Bootloop. The device said it's unlocked but apparently seems not to.
I CANNOT go into recovery mode.
I CANNOT flash any recovery too.
I have connected the device to my laptop (Windows 10) through fastboot try to flash any recovery: OrangeFox, TWRP, no success.
I either run a powershell or run CMD as Admin
This is the error:
c:\adb fastboot flash recovery recovery.img
Sending 'recovery' (31161 KB) OKAY [ 0.669s]
Writing 'recovery' FAILED (remote: 'Error flashing partition : Write Protected')
fastboot: error: Command failed
So I try this command: fastboot boot recovery.img
It loads the recovery either TWRP or OrangeFox but only the Logo nothing else.
It doesn't RUN any official MIUI recovery.
So, now I can use ADB commands.
The phone is seen connected to Windows 10 as USB but I guess not MTP mode but only as charging mode.
In the "Safely Remove Hardware" section I can see the device connected and its name as Redmi Note 5 Pro.
Of course I can't see the device in the Explorer and any folder as the OS hasn't loaded at all.
Now, though, I can run ADB commands, so I typed: run devices and it says it's in recovery mode, also with the number of the device.
Then with ADB SHELL LS command
I can see the folder tree
With Push and Pull commands, I can copy folders, but cannot access and copy the content of SDCARD and STORAGE.
I know those folders are protected even though my phone should be unlocked but apparently it is not then.
It's really ridiculous that there is no a way around this.
Why, if I am the owner the unlock process have to reset phone data?
It's so stupid! They should have developed a public/private key or a long key to unlock those folder by registering your phone with SN and IMEI number.
So surprised Google and any brand don't do that.
If I connect the device in fastboot mode, I have those details:
fastboot oem device-info
(bootloader) Verity mode: true
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
OKAY [ 0.006s]
Finished. Total time: 0.006s
Is there a WAY with lower level commands or software to access to data with "write protected" inside the phone memory?
I would love to recover my Whatsapp folder and my DCIM folder with every files in those.
Or the only solution is to give the Device to experts and do the CHIP Off recovery data?
Will MiFlash with a MIUI rom with save user data option actually save my data and hence Whatsapp and DCIM folder and its content inside?
Please Help!
If anyone can HELP to successfully recover my data seriously I would be more than happy to give a compensation via PayPal cause I would truly appreciated the infinite effort and help!
Thanks in advance to anyone who can sponsor the cause!
I am so pissed as the phone should be under 2 years warranty but of course no brand would cover and help you through those issues!
Such A PITY!
Kind regard,
Michael
Click to expand...
Click to collapse
Stop with same multiple threads!!!!
It's against XDA rules.
And I gave you and answer already in other thread, please check.

drnightshadow said:
Stop with same multiple threads!!!!
It's against XDA rules.
And I gave you and answer already in other thread, please check.
Click to expand...
Click to collapse
I haven't done any multiple threads sorry!
It was my first post, I realized later on someone post something similar to mine though not really the same issue.
I will check your answer.
Thanks.

Dear have you recovered your data ! I'm in the same problem pls help me