Database Users

[Q] [Fastboot] Can't flash Stock ROM

Hello there!
I have a Nexus 7 Device, I rooted it using a toolkit, everything was working great, then I messed up a little and I need to restore it using a Factory Image (a.k.a Stock ROM)...
The problem is, when I try to flash the .zip, it gives me the following 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"
}
According to some tutorials, you type the following commands to flash a ROM:
fastboot erase boot
fastboot erase cache
fastboot erase recovery
fastboot erase system
fastboot erase userdata
fastboot -w update ROM.zip
Click to expand...
Click to collapse
Because I'm afraid of something going wrong, I didn't erased any partition, so if for some reason the flashing procedure stops, I have the old data/partitions working because I didn't erased any, I just used the following command:
fastboot -w update ROM.zip
Click to expand...
Click to collapse
So, the questions are:
Do I need to erase the partitions first before trying to flash the Stock ROM?
Should I try flash each .img separately?
Additional Information:
Android is working, I'm able to boot with success.
Bootloader unlocked.
I didn't flashed any custom Bootloader/Recovery/ROM, everything is from Factory/Stock.
I have tested flashing the ROM under Windows and Linux (Ubuntu), it gives me the exact error.
The .zip I'm using isn't corrupted. (And it's directly from developers.google.com)
If flashing without erasing the partitions worked, I would erase them (To delete ALL data/trash) and flash it again...
P.S: First post!

I'm pretty sure the script erases those anyway... You could open it up and check though. Don't worry about the .sig files; that's normal. Check inside the .zip to make sure the system.img is actually in there. If it is, then extract it and try flashing it by itself.
In fact, if you just were trying to fix something you messed up, all you need is the system image anyway.
Sent from my Nexus 7 using Tapatalk HD

korockinout13 said:
I'm pretty sure the script erases those anyway... You could open it up and check though. Don't worry about the .sig files; that's normal. Check inside the .zip to make sure the system.img is actually in there. If it is, then extract it and try flashing it by itself.
In fact, if you just were trying to fix something you messed up, all you need is the system image anyway.
Sent from my Nexus 7 using Tapatalk HD
Click to expand...
Click to collapse
Hello!
Thanks for the answer, I tried to flash system.img and it worked, fastboot automatically erases the system partition.
I have now a clean system, thanks!
For other people with the same problem as me:
1 - Enter Fastboot Mode
2 - Extract system.img
3 - Run "fastboot flash system system.img"
4 - Enter Recovery Mode and do a "Factory Reset" (Optional, I guess)
5 - Enjoy!

Spenzert said:
fastboot automatically erases the system partition.
Click to expand...
Click to collapse
I wouldn't jump to that conclusion quite so readily.
It merely overwrote whatever contents were already there.
More or less the same result though, excepting some possibly inconsequential trash in the partition slack space.
cheers

bftb0 said:
I wouldn't jump to that conclusion quite so readily.
It merely overwrote whatever contents were already there.
More or less the same result though, excepting some possibly inconsequential trash in the partition slack space.
cheers
Click to expand...
Click to collapse
I believe fastboot really erased the partition, there's no "SuperSU" anymore and I have attached a screenshot of fastboot erasing the partition.
Cheers!

I wouldn't have believed it until I saw the picture... and now I believe! My bad!
I could swear I've done the same thing on other devices for a couple years now without the implicit erase happening. I wonder if it is a fastboot version difference.
If you don't mind me asking, what version of fastboot is that?

bftb0 said:
I wouldn't have believed it until I saw the picture... and now I believe! My bad!
I could swear I've done the same thing on other devices for a couple years now without the implicit erase happening. I wonder if it is a fastboot version difference.
If you don't mind me asking, what version of fastboot is that?
Click to expand...
Click to collapse
Android SDK Manager says "Rev. 16.0.1" (Platform-tools), maybe fastboot erased the partition first because I used "fastboot flash" instead of "fastboot update"...
A little off-topic:
I tried to root manually my Nexus and it's really easy, I might make an updated tutorial soon on how to root it manually
Have a good day!
Edit: I tried to flash TWRP (Recovery) and it didn't erased the partition first.

[help] Buying a bricked tf300

Hello guy,
I have the possiblity to buy a tf300 wich is bricked. And I would like to know if someone could tell me if it's fixable.
The guy says that he unlocked the bootloader, apparently it worked fine and the he flash a TWRP 2.6.3.0 then it went bad. He says the tablet is directly booting up into recovery (at least that's working) that TWRP says "Omb" whatever that means and that he doesn't see any files into recovery, only folders and subfolders (isn't supposed to be normal, I mean doesn't the recovery only display .zip files ??). He says volume down + power doesn't work, adb gives a " protocol failure" and fastboot is waiting for device (but I'm gessing it's normal since he can't boot into menu obviously fastboot is not working).
So what do you think is it fixable?
Thanks

the guy gave me 2 images of the recovery:
{
"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"
}

Apparently the password asked on the screenshots is here because the recovery can't mount the storage partitions. Clearly he flash the wrong recovery. He says that he can't get fastboot because he can't install driver (something I could figure out how to do ).
My last question is, will I get fastboot in this recovery, dispite the storage not mounting and the incompatibility?
if yes then I can do a "fastboot getvar all" to get bootloader version and flash the right recovery? What do you think??
thanks

ayziaa said:
Apparently the password asked on the screenshots is here because the recovery can't mount the storage partitions. Clearly he flash the wrong recovery. He says that he can't get fastboot because he can't install driver (something I could figure out how to do ).
My last question is, will I get fastboot in this recovery, dispite the storage not mounting and the incompatibility?
if yes then I can do a "fastboot getvar all" to get bootloader version and flash the right recovery? What do you think??
thanks
Click to expand...
Click to collapse
that has append to me couple of times( i think 3 -4 times actually) , if you are confident you can get fastboot and ADB working should be really easy to fix. but ull have to flash ASUS blob file then start over like if it was a new tablet

ayziaa said:
Apparently the password asked on the screenshots is here because the recovery can't mount the storage partitions. Clearly he flash the wrong recovery. He says that he can't get fastboot because he can't install driver (something I could figure out how to do ).
My last question is, will I get fastboot in this recovery, dispite the storage not mounting and the incompatibility?
if yes then I can do a "fastboot getvar all" to get bootloader version and flash the right recovery? What do you think??
thanks
Click to expand...
Click to collapse
Yeah I ran into that bug personally and I fixed is in less than 5 minutes with the right setup. Of course, it could be a different situation but there is the chance that it is easily fixable.

Sadly the guy allready sold it. Thank you guy for replying

help
Hi guys....
on my bad luck, looks like I did the same thing.... I had CMB Roms cmb4.4.2 with Philz CWM v6.0.4.5, as I did like this, I went to flash another rom. So, I put the TWRP 2.6 on sdcard with Cromi rom.... flash recovery, reboot and there it stock on recovery and state just like on pictures ...
I can go with ABD but not FASTBOOT... my sdcard is SYSTEM when I mount the system from twpr !!!!
can someone help me ?

srdjank said:
Hi guys....
on my bad luck, looks like I did the same thing.... I had CMB Roms cmb4.4.2 with Philz CWM v6.0.4.5, as I did like this, I went to flash another rom. So, I put the TWRP 2.6 on sdcard with Cromi rom.... flash recovery, reboot and there it stock on recovery and state just like on pictures ...
I can go with ABD but not FASTBOOT... my sdcard is SYSTEM when I mount the system from twpr !!!!
can someone help me ?
Click to expand...
Click to collapse
You put the wrong version of TWRP on your tablet probably? when you restart and it boots into TWRP, on the starting screen you should be able to use fastboot.
---------- Post added at 04:33 PM ---------- Previous post was at 04:31 PM ----------
When it happened to me, it was a bootloader and TWRP conflict: I flashed the jb version instead of the -42 Version. to fix it, I did fastboot reboot bootloader and then got back into android and flashed the correct one from Terminal Emulator. Or you could just flash it from there.

cmendonc2 said:
You put the wrong version of TWRP on your tablet probably? when you restart and it boots into TWRP, on the starting screen you should be able to use fastboot.
---------- Post added at 04:33 PM ---------- Previous post was at 04:31 PM ----------
When it happened to me, it was a bootloader and TWRP conflict: I flashed the jb version instead of the -42 Version. to fix it, I did fastboot reboot bootloader and then got back into android and flashed the correct one from Terminal Emulator. Or you could just flash it from there.
Click to expand...
Click to collapse
nope, I can't use it, if you meen on blue screen when twrp starts, when it boots is the same.... fastboot devices command and it just don't do anything, when twrp boots adb devices turn up : 0123456789ABCDEF recovery
I tryed meny things but I can get it to boot in bootloader with tree options....
when I type fastboot -i 0x0B05 flash c:\Android SDK\sdk\platform-tools\blob
just says <waiting for device> and stays that way.... tryed to reset tab with pin let it boot but nothing ...

srdjank said:
nope, I can't use it, if you meen on blue screen when twrp starts, when it boots is the same.... fastboot devices command and it just don't do anything, when twrp boots adb devices turn up : 0123456789ABCDEF recovery
I tryed meny things but I can get it to boot in bootloader with tree options....
when I type fastboot -i 0x0B05 flash c:\Android SDK\sdk\platform-tools\blob
just says <waiting for device> and stays that way.... tryed to reset tab with pin let it boot but nothing ...
Click to expand...
Click to collapse
What is your OS of your PC??

cmendonc2 said:
You put the wrong version of TWRP on your tablet probably? when you restart and it boots into TWRP, on the starting screen you should be able to use fastboot.
---------- Post added at 04:33 PM ---------- Previous post was at 04:31 PM ----------
When it happened to me, it was a bootloader and TWRP conflict: I flashed the jb version instead of the -42 Version. to fix it, I did fastboot reboot bootloader and then got back into android and flashed the correct one from Terminal Emulator. Or you could just flash it from there.
Click to expand...
Click to collapse
lj50036 said:
What is your OS of your PC??
Click to expand...
Click to collapse
HE's ALIVE ....
:fingers-crossed::fingers-crossed::fingers-crossed:
I''m on WIN7 64...... like I said I boot it up, all I needed is command : abd reboot-bootloader
that cat me in bootloader mode, with http://forum.xda-developers.com/showpost.php?p=44244313&nocache=1&z=9056634965818376
I boot it up on stock 4.2.1 JOP40D.ww_epad-10.6.1.8-20130225
sorry for trouble ...... thanks all for trying to help ....

[Q] Cant enter factory reset mode (devide turned off)

Got an LG G2 D802 which recently was stuck in fastboot only,no download mode not anything at all,
after many tries and errors i managed to boot to download mode and flash an apropriate version.
The thing is from that moment i cant seem to get in factory reset screen through Power Down + Power button as it used on the beginning i press the is im supposed and the phone just normaly boots,never get on factory reset or recovery,I can only enter the recovery via application from playstore called Reboot Recovery.
I can still factory reset from settings but i want to know why i cant enter with the other way and i think it a necessary function to have just in case.
How can i fix this in order to get in factory reset when the device is turned off?
How can i install twrp without autorec because this was the problem which bricked my phone?(download zip and install from current recovery?)which twrp do i need for the following device?
Any info on dorimanx kernel?
Android version 4.4.2
Build Number KOT49I.D80220h
kernel version 3.4.0
Model LG G2 D802

Did you use a kdz file or tot file?

scuzzo500 said:
Did you use a kdz file or tot file?
Click to expand...
Click to collapse
kdz file was it,should i reflash with a .tot file?
also my device was locked to tmobile uk and the got unlock via pin from the carrier,if i reflash it will need again to be unlocked?

watanabe32 said:
How can i fix this in order to get in factory reset when the device is turned off?
Click to expand...
Click to collapse
You're running 4.4.2 which is KitKat. KitKat Recovery is accessed by holding PWR + VOL DWN, then when the LG logo appears, switching to VOL DWN + VOL UP. You are trying the old method for Jellybean Recovery.
watanabe32 said:
How can I install TWRP without AutoRec?
Click to expand...
Click to collapse
BEFORE FOLLOWING THIS MAKE SURE YOU HAVE WORKING ADB DRIVERS INSTALLED AND CAN CONFIRM COMMUNICATION WITH YOUR PHONE VIA ADB COMMANDS!
You can install TWRP without autorec, which will result in keeping your KitKat bootloader. This method is also called BUMP. Follow my steps:
1. Download your KDZ from here. If you are already running Stock KitKat, no need.. just continue to step 2. I like to do everything from a clean/fresh installation that's all.
2. Root your stock KK with StumpROOT.
3. Download Bumped TWRP from here.
Extract the recovery.img file from the downloaded TWRP .rar archive.
4. Next we need your boot.img file currently on your phone. We can extract your boot.img to your sdcard by running the following command:
Code:
dd if=/dev/block/platform/msm_sdcc.1/by-name/boot of=/sdcard/boot.img
Once your boot.img is on your sdcard, move it to your computer via usb or adb, your choice.
5. Download Windows BUMP Tool.
6. Bump your boot.img file with the Windows BUMP Tool. This will result in a newly created bumped.img file. Delete your original boot.img and rename bumped.img to boot.img
7. Next we need to force your phone into fastboot mode (as much as that might scare you!), we can do that by running the following command via adb/shell.
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/boot
8. BEFORE WE GO ANY FURTHER, You should have 2 files on your computer: recovery.img, and your newly renamed boot.img (bumped with the Windows BUMP Tool). Next we need to reboot the phone in order to get into fastboot mode. So, REBOOT.
9. When your device reboots it will boot into fastboot as we nullified the boot partition. We now need to connect our device via adb and run the following commands,
Code:
fastboot flash boot boot.img
fastboot flash recovery recovery.img
These commands require your recovery.img and boot.img to be in the same folder as your fastboot.exe file.
(See the image below for an example)
{
"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"
}
Once successfully flashing your bumped recovery and bumped boot.img, run the following command:
Code:
fastboot reboot
.
That's it! You now installed TWRP without AutoRec, and kept your KitKat bootloader.
watanabe32 said:
Which TWRP do I need?
Click to expand...
Click to collapse
ALWAYS A BUMPED TWRP RECOVERY FROM HERE.
watanabe32 said:
Any info on dorimanx kernel?
Click to expand...
Click to collapse
Dorimanx Kernel works great with a KK Bootloader, BUT YOU NEED TO HAVE A BUMPED VERSION OF THE DORIMANX KERNEL. All versions of Dorimanx above 9.1 are BUMPED.

I'll try your steps when i go home,
i've got installed the minimal adb driver which i found in my search for fixi g the fastboot problem of g2 i think this will be enough right?
for the twrp recovery cant i install it via sideload?from the recovery that it has now which is not twrp/cwm,its something else i dont know what but it has wipe cache install from cache install fro sideload

watanabe32 said:
I'll try your steps when i go home,
i've got installed the minimal adb driver which i found in my search for fixi g the fastboot problem of g2 i think this will be enough right?
Click to expand...
Click to collapse
That should be okay. As long as you can use the fastboot command and fastboot.exe is present.
watanabe32 said:
for the twrp recovery cant i install it via sideload?from the recovery that it has now which is not twrp/cwm,its something else i dont know what but it has wipe cache install from cache install fro sideload
Click to expand...
Click to collapse
I have no idea, I've never used sideload before. I'm just giving you my solution to installing TWRP without AutoRec from the facts stated in your original post. We both have the D802 model and my methods above have worked flawlessly for me multiple times after reflashing a compatible KDZ. Good luck and take it slow.

Device is not detected when trying to flash TWRP

okay hello people.
here is my situation.
i was about to revert back to kitkat from ED300 CM12.1, and i suddenly wipe off and formatted my internal storage.
and now ofcourse i cant boot in and what i did was trying to reinstall TWRP through fastboot and minimal adb from PC.
*i tried to flash Lenovo_A6000_TWRP-3.0.2-0_x64-L_by_SevenMaxs
*i cant go into download mode (vol+,vol-,power) button.
so i went to fastboot mode (vol-,power) button until the 'powerkey long press can reboot phone' appear , and i plug in my phone to pc and when i type in command for -adb devices, no device appear.
figure out it was okay, i go ahead and proceed with - fastboot boot recovery.img command.
then it shows
FAILED (remote: dtb not found)
and im stuck there. idk what else to do, which guide to follow to bring my phone back to life.
i have did hours of searching but nothing works. really need a magic here.
thanks guys for ur time

rizarulaltiz said:
okay hello people.
here is my situation.
i was about to revert back to kitkat from ED300 CM12.1, and i suddenly wipe off and formatted my internal storage.
and now ofcourse i cant boot in and what i did was trying to reinstall TWRP through fastboot and minimal adb from PC.
*i tried to flash Lenovo_A6000_TWRP-3.0.2-0_x64-L_by_SevenMaxs
*i cant go into download mode (vol+,vol-,power) button.
so i went to fastboot mode (vol-,power) button until the 'powerkey long press can reboot phone' appear , and i plug in my phone to pc and when i type in command for -adb devices, no device appear.
figure out it was okay, i go ahead and proceed with - fastboot boot recovery.img command.
then it shows
FAILED (remote: dtb not found)
and im stuck there. idk what else to do, which guide to follow to bring my phone back to life.
i have did hours of searching but nothing works. really need a magic here.
thanks guys for ur time
Click to expand...
Click to collapse
BTW if "fastboot devices" not showing any devices then try to properly install fastboot on computer."fastboot boot twrp.img" is command for boot the twrp without flashing.
try "fastboot flash recovery twrp.img" .
p.s:-Try to flash different recovery file.It may be corrupted.

i-AM-BoReD said:
BTW if "fastboot devices" not showing any devices then try to properly install fastboot on computer."fastboot boot twrp.img" is command for boot the twrp without flashing.
try "fastboot flash recovery twrp.img" .
p.s:-Try to flash different recovery file.It may be corrupted.
Click to expand...
Click to collapse
did it as your advice,
{
"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"
}
then i reboot the phone, still cant manage to go into recovey. it stuck there at lenovo logo.
tried with different recovery image, still the same

rizarulaltiz said:
did it as your advice,
then i reboot the phone, still cant manage to go into recovey. it stuck there at lenovo logo.
tried with different recovery image, still the same
Click to expand...
Click to collapse
As i can see that it is saying device not found but flshing is succeeded.
Editlz try to install fastboot properly.Look here

i-AM-BoReD said:
As i can see that flashing is successful.For entering to recovery r u using button combo or command?
Click to expand...
Click to collapse
i use button combo.
vol+, vol-, power button

rizarulaltiz said:
i use button combo.
vol+, vol-, power button
Click to expand...
Click to collapse
Here is the possibilities:-
1)May be fastboot is not properly installed .I gave a link in the previous post for that. "device not found" that shouldn't be appear.
2)Try vol+ +power button
3)Try if stock recovery can be flashed by fastboot.Link.if can be then let me know.
4)If not then run this command in adb
Code:
adb shell
ls -al /dev/block/platform/dw_mmc/by-name
and give a screen shot.

Did you flash kitkat ROM after this or before this fuss?
If Yes, then you need to flash TWRP for kitkat firmware.

https://drive.google.com/file/d/0B8_p5nNeW71VRFZnc3cwb2hLR28/view?usp=sharing
download the above recovery and download flashify from playstore . Flash the recovery that you downloaded from above link with flashify and reboot and in the next step you will be in the recovery

Try this
http://forum.xda-developers.com/len...lenovo-a6000-plus-stuck-booting-logo-t3437378
LP/MM TWRP 2.8.7.7 https://drive.google.com/file/d/0B3yAzE4FH2e7RkNQbUk2b0g1T0E/view?usp=drivesdk
KK TWRP 2.8.6.1 https://drive.google.com/file/d/0B3yAzE4FH2e7RU5helVWd0dBUGM/view?usp=drivesdk

i-AM-BoReD said:
Here is the possibilities:-
1)May be fastboot is not properly installed .I gave a link in the previous post for that. "device not found" that shouldn't be appear.
2)Try vol+ +power button
3)Try if stock recovery can be flashed by fastboot.Link.if can be then let me know.
4)If not then run this command in adb
Code:
adb shell
ls -al /dev/block/platform/dw_mmc/by-name
and give a screen shot.
Click to expand...
Click to collapse
1.fastboot is properly installed
2.still nothing
3. tried this and it worked. i can boot into recovery now.
now i should flash the stock rom right?

rizarulaltiz said:
1.fastboot is properly installed
2.still nothing
3. tried this and it worked. i can boot into recovery now.
now i should flash the stock rom right?
Click to expand...
Click to collapse
Then ur device is good to go.I found a recovery flashble stock rom in help or guide thread few days ago.Search it.
Also if there is recovey flashable T.W.R.P available somewhere u can flash it also.
Edit:-Here is a zip file of T.W.R.P.But version is 3.0.0.1.Don know if it can be flaahed by Stock recovery or not.Give it a try.If succeeded then no need to flash whole stock rom.You know that already.

i-AM-BoReD said:
Then ur device is good to go.I found a recovery flashble stock rom in help or guide thread few days ago.Search it.
Also if there is recovey flashable T.W.R.P available somewhere u can flash it also.
Edit:-Here is a zip file of T.W.R.P.But version is 3.0.0.1.Don know if it can be flaahed by Stock recovery or not.Give it a try.If succeeded then no need to flash whole stock rom.You know that already.
Click to expand...
Click to collapse
after i manage to flash stock recovery, i flash TWRP-2.8.6.1_A6000. then i boot into TWRP and format my internal storage, then continue flashing back ED 300's CM12.1.
and my device is back onlinee! Thanks brother for the help!!!

rizarulaltiz said:
1.fastboot is properly installed
2.still nothing
3. tried this and it worked. i can boot into recovery now.
now i should flash the stock rom right?
Click to expand...
Click to collapse
I am facing the same problem of adb device not listed , please share how it worked for you

TWRP bootloop after installing LineageOS

Installed LineageOS 14.1 (it didn't install first time so I formated data and it worked), then I launched it, and it said LineageOS has an update, tried to install it and this happened... I'm stuck in TWRP. Tried to reinstall lineageOS again the same way, but I'm still stuck in this TWRP. Please help
TWRP version 3.0.2-0
SOLVED: can't post links, so find a video in youtube named "When Your Android Keep Booting Into TWRP Recovery" and write down those 2 commands

Watch this, it'll help!
https://www.youtube.com/watch?v=vSWC5MAB5cE

Fantastic... Thanks

detalikota said:
Installed LineageOS 14.1 (it didn't install first time so I formated data and it worked), then I launched it, and it said LineageOS has an update, tried to install it and this happened... I'm stuck in TWRP. Tried to reinstall lineageOS again the same way, but I'm still stuck in this TWRP. Please help
TWRP version 3.0.2-0
SOLVED: can't post links, so find a video in youtube named "When Your Android Keep Booting Into TWRP Recovery" and write down those 2 commands
Click to expand...
Click to collapse
Connect your ZUK Z1 device to your computer via USB and run this command as root: adb shell dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc count=1 bs=32
You can also go to the TWRP terminal and run: dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc count=1 bs=32
This solves your problem.
Thank you

Here's the solution: https://www.youtube.com/watch?v=vSWC5MAB5cE

bhattyash32 said:
Here's the solution:
Click to expand...
Click to collapse
Plz give me the link fo tool kit zuk z1 windows 7

jay9167 said:
Plz give me the link fo tool kit zuk z1 windows 7
Click to expand...
Click to collapse
You will find it on xda in general section

srk2521 said:
Connect your ZUK Z1 device to your computer via USB and run this command as root: adb shell dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc count=1 bs=32
You can also go to the TWRP terminal and run: dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc count=1 bs=32
This solves your problem.
Thank you
Click to expand...
Click to collapse
ZUK Z1- i got struck into boot loop after restoring from TWRP, That worked for me ! the TWRP terminal command !!!

Zuk Z1 Stuck/Reboot in Recovery
Try this this solved my problem may be it'll help you also
Search on you tube "phone reboots in twrp recovery"

srk2521 said:
Connect your ZUK Z1 device to your computer via USB and run this command as root: adb shell dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc count=1 bs=32
You can also go to the TWRP terminal and run: dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc count=1 bs=32
This solves your problem.
Thank you
Click to expand...
Click to collapse
Worked perfectly via TWRP Terminal. Thanks!

detalikota said:
Installed LineageOS 14.1 (it didn't install first time so I formated data and it worked), then I launched it, and it said LineageOS has an update, tried to install it and this happened... I'm stuck in TWRP. Tried to reinstall lineageOS again the same way, but I'm still stuck in this TWRP. Please help
TWRP version 3.0.2-0
SOLVED: can't post links, so find a video in youtube named "When Your Android Keep Booting Into TWRP Recovery" and write down those 2 commands
Click to expand...
Click to collapse
This will fix it without losing any data. (NO FACTORY RESET NEEDED)
Go to TWRP recovery terminal commands, and enter the following:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
PRESS ENTER
THEN TYPE
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
THEN PRESS ENTER
REBOOT
This should boot up your phone without any changes.

srk2521 said:
Connect your ZUK Z1 device to your computer via USB and run this command as root: adb shell dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc count=1 bs=32
You can also go to the TWRP terminal and run: dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc count=1 bs=32
This solves your problem.
Thank you
Click to expand...
Click to collapse
This saved me bro.... Thanks!

This also saved my dad's z1 ham. Any idea the cause? We just installed the latest OTA 8222017 of LOS 14.1.

This problem is only for the 3.0.2 version for Mako devices. For safer side update to 3.1 version of TWRP.

jay9167 said:
Plz give me the link fo tool kit zuk z1 windows 7
Click to expand...
Click to collapse
It seems that the account of this youtube channel is terminated ,it shows error like this

Any idea to fix this permanently? every update from LineageOS results to this? The official version of TWRP is only 3.0.2-0

detalikota said:
Installed LineageOS 14.1 (it didn't install first time so I formated data and it worked), then I launched it, and it said LineageOS has an update, tried to install it and this happened... I'm stuck in TWRP. Tried to reinstall lineageOS again the same way, but I'm still stuck in this TWRP. Please help
TWRP version 3.0.2-0
SOLVED: can't post links, so find a video in youtube named "When Your Android Keep Booting Into TWRP Recovery" and write down those 2 commands
Click to expand...
Click to collapse
You cant update LineageOS through TWRP 3.0.x update to TWRP 3.1.x.. For some reaosn it is not able to run the update script and hence tries to run it on every boot...
One simle solution to this is boot it in bootloader and flast TWRP 3.1.x

Hi
I'm having this issue. I tried everything. the dd commands, upgrading/downgrading twrp, with no results. Can anyone help, me please, I'm getting so nbervous with this.
Thanks

joanrc said:
Hi
I'm having this issue. I tried everything. the dd commands, upgrading/downgrading twrp, with no results. Can anyone help, me please, I'm getting so nbervous with this.
Thanks
Click to expand...
Click to collapse
Which twrp version do you have/want to install? 3.1 or later is recommended.

strongst said:
Which twrp version do you have/want to install? 3.1 or later is recommended.
Click to expand...
Click to collapse
Hi, now I have 3.0.2, but I also tried with 3.1 with the same result
Edit: I have already update again to 3.1 and tried the dd commands, they show me always the same messge of : "No space left on device"
{
"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.exe shell dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/fota
dd: writing '/dev/block/platform/msm_sdcc.1/by-name/fota': No space left on device
2908593+0 records in
2908592+0 records out
1489199104 bytes (1.4GB) copied, 17.564732 seconds, 80.9MB/s
C:\ZUK Z1\platform-tools-latest-windows>adb.exe shell dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
dd: writing '/dev/block/platform/msm_sdcc.1/by-name/misc': No space left on device
2049+0 records in
2048+0 records out
1048576 bytes (1.0MB) copied, 0.302512 seconds, 3.3MB/s
Click to expand...
Click to collapse