I was trying to update nightly build ( 21st March released) of lineage os for ZUK Z1. But now it is only starting in TWRP recovery mode. What to do now? Please help me.
I have attached a screenshot of the error which I am getting while installing any build of lineage os.
{
"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"
}
imcoder said:
I was trying to update nightly build ( 21st March released) of lineage os for ZUK Z1. But now it is only starting in TWRP recovery mode. What to do now? Please help me.
Click to expand...
Click to collapse
https://androidforums.com/threads/twrp-bootloop-fix-after-update-ota.922585/
Just go on this link and follow the steps given. There are two commands there, just type those commands in terminal of TWRP.. When your phone will boot properly first flash the latest TWRP 3.1.0, you will find it in original Android development section. Then only install the OTA. With TWRP 3.1.0 the OTA is installed automatically and there is no bootloop. All works fine....
---------- Post added at 01:38 PM ---------- Previous post was at 01:34 PM ----------
Incase if you are getting error 7 while installing official lineage OS then follow this
1. Download unofficial los 14.1 by orderkrieger
2. Clean install it...
3. Download official los 14.1
4. Clean install it...
There should be no error 7 while installing official los if you follow this.
I also faced the same issue and followed the above steps and it worked for me... Thanks for your help...!!!!
Hi
Hi what about the latest nightly 28march one how is it shall i download and install it oy
Here's the solution: https://www.youtube.com/watch?v=vSWC5MAB5cE
I found a similar issue by ZUK2 : https://forum.xda-developers.com/showpost.php?p=72298526&postcount=14
I used it on my ZUK1, but update the path according my filesystem...
This worked for me:
1. Boot to TRWP Recovery (power off, power on with volume up +volume down)
2. "Mount" -> mount "System" then back to main screen
3. "Advanced' -> "Terminal"
Type the following command:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Then run it...
4. go back to main menu, then "Reboot" -> "Power off"
5. Switch on, and then should work normally...
Mammuth1 said:
I found a similar issue by ZUK2 : https://forum.xda-developers.com/showpost.php?p=72298526&postcount=14
I used it on my ZUK1, but update the path according my filesystem...
This worked for me:
1. Boot to TRWP Recovery (power off, power on with volume up +volume down)
2. "Mount" -> mount "System" then back to main screen
3. "Advanced' -> "Terminal"
Type the following command:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Then run it...
4. go back to main menu, then "Reboot" -> "Power off"
5. Switch on, and then should work normally...
Click to expand...
Click to collapse
Worked like a charm. You saved my life with this one. I have no admin rights on my work PC so troubleshooting is difficult and I would be a dead man with no phone today. Many thanks!
tanmeshn said:
https://androidforums.com/threads/twrp-bootloop-fix-after-update-ota.922585/
Just go on this link and follow the steps given. There are two commands there, just type those commands in terminal of TWRP.. When your phone will boot properly first flash the latest TWRP 3.1.0, you will find it in original Android development section. Then only install the OTA. With TWRP 3.1.0 the OTA is installed automatically and there is no bootloop.
Click to expand...
Click to collapse
I cannot find a version 3.1 I used twrp-3.0.2-0-Z1, which is the latest from https://twrp.me/devices/zukz1.html and with this version the bug exists.
lg-optimus said:
I cannot find a version 3.1 I used twrp-3.0.2-0-Z1, which is the latest from https://twrp.me/devices/zukz1.html and with this version the bug exists.
Click to expand...
Click to collapse
https://forum.xda-developers.com/devdb/project/dl/?id=23595&task=get
Can I flash the new version 3.1 with the old version 3.0? Thanks!
lg-optimus said:
Can I flash the new version 3.1 with the old version 3.0? Thanks!
Click to expand...
Click to collapse
Yes,. You can flash twrp 3.1 over 3.0.2
Thanks, for unknown reasons I do not have any problems with 3 installations, so I am waiting to flash the newer verison.
tanmeshn said:
Yes,. You can flash twrp 3.1 over 3.0.2
Click to expand...
Click to collapse
I was unsure, what to use then, recovery or boot, what should I have used.
I decided to use fastboot
Code:
# /install/androidins/platform-tools/fastboot flash recovery /install/androidins/zuk_install/twrp-3.1.0-0-ham.img
target reported max download size of 1610612736 bytes
sending 'recovery' (10866 KB)...
OKAY [ 0.376s]
writing 'recovery'...
OKAY [ 0.150s]
finished. total time: 0.525s
# /install/androidins/platform-tools/fastboot reboot
rebooting...
Not working
Mammuth1 said:
I found a similar issue by ZUK2 : https://forum.xda-developers.com/showpost.php?p=72298526&postcount=14
I used it on my ZUK1, but update the path according my filesystem...
This worked for me:
1. Boot to TRWP Recovery (power off, power on with volume up +volume down)
2. "Mount" -> mount "System" then back to main screen
3. "Advanced' -> "Terminal"
Type the following command:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Then run it...
4. go back to main menu, then "Reboot" -> "Power off"
5. Switch on, and then should work normally...
Click to expand...
Click to collapse
It says
Code:
dd: can't open '/dev/block/platform/msm_sdcc.1/by-name/misc' : No such file or directory
Once take a look at my files in dev/block/platform/ folder in this video
its saying there is no directory named dd
its saying there is no directory named dd
Mammuth1 said:
I found a similar issue by ZUK2 : https://forum.xda-developers.com/showpost.php?p=72298526&postcount=14
I used it on my ZUK1, but update the path according my filesystem...
This worked for me:
1. Boot to TRWP Recovery (power off, power on with volume up +volume down)
2. "Mount" -> mount "System" then back to main screen
3. "Advanced' -> "Terminal"
Type the following command:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Then run it...
4. go back to main menu, then "Reboot" -> "Power off"
5. Switch on, and then should work normally...
Click to expand...
Click to collapse
Hi, thanks for your help, Why this happend?
I installed last lineageos nightly, gapps, all ok, but when I perform a factory reset from the options menu (of android) this happen, and only works performing this solution.
help anyone, stuck rebooting into recovery all the time, my phone is lenovo k3 note it happened after i tried factory reset on new installed rom.
getting error dd: can't open '/dev/block/platform/msm_sdcc.1/by-name/misc' : No such file or directory ... how can i fix that?
Moto G4 Plus
I have same issue in my Moto g4 plus......Does it reset every data present in the Phone ?
QUOTE=Mammuth1;74320886]I found a similar issue by ZUK2 : https://forum.xda-developers.com/showpost.php?p=72298526&postcount=14
I used it on my ZUK1, but update the path according my filesystem...
This worked for me:
1. Boot to TRWP Recovery (power off, power on with volume up +volume down)
2. "Mount" -> mount "System" then back to main screen
3. "Advanced' -> "Terminal"
Type the following command:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Then run it...
4. go back to main menu, then "Reboot" -> "Power off"
5. Switch on, and then should work normally... [/QUOTE]
---------- Post added at 02:49 AM ---------- Previous post was at 02:38 AM ----------
Does it reset my phone data ??
Mammuth1 said:
I found a similar issue by ZUK2 : https://forum.xda-developers.com/showpost.php?p=72298526&postcount=14
I used it on my ZUK1, but update the path according my filesystem...
This worked for me:
1. Boot to TRWP Recovery (power off, power on with volume up +volume down)
2. "Mount" -> mount "System" then back to main screen
3. "Advanced' -> "Terminal"
Type the following command:
Code:
dd if=/dev/zero of=/dev/block/platform/msm_sdcc.1/by-name/misc
Then run it...
4. go back to main menu, then "Reboot" -> "Power off"
5. Switch on, and then should work normally...
Click to expand...
Click to collapse
Related
Update
Flash this to have working combo
[HOW-TO] Enable Three Button Combo [RECOVERY]
Since our phone doesnt have any button combination go enter the recovery we have to use workarounds
Other methods:
ADB method
If you are running on non rooted ROM
1. Download and install Android SDK
2. Connect the phone to the PC via USB
3. Press Win key+ r and type cmd
4. Type adb reboot recovery
5. Done. Phone should reboot into recovery
Terminal method
If running rooted ROM
1.Download and install
Terminal Emulator app ( https://play.google.com/store/apps/details?id=jackpal.androidterm )
2. Open the app
3. Type su
4. Accept SuperUser permission
5. Type reboot recovery
6. Press enter
7. Done. Phone should reboot into recovery
App method
Requires root
1. Download and install this app: https://play.google.com/store/apps/details?id=com.siriusapplications.quickboot
2. Open the app
3. Click recovery
4. It should reboot
This guide may be updated once the cwm comes out!
Thank you for this!
ppero196 said:
Since our phone doesnt have any button combination go enter the recovery we have to use workarounds.
ADB method
If you are running on non rooted ROM
1. Download and install Android SDK
2. Connect the phone to the PC via USB
3. Press Win key+ r and type cmd
4. Type adb reboot reccocery
5. Done. Phone should reboot into recovery
Terminal method
If running rooted ROM
1.Download and install
Terminal Emulator app ( https://play.google.com/store/apps/details?id=jackpal.androidterm )
2. Open the app
3. Type su
4. Accept SuperUser permission
5. Type reboot recovery
6. Press enter
7. Done. Phone should reboot into recovery
This guide may be updated once the cwm comes out!
Click to expand...
Click to collapse
And one more way, if you have rooted your phone, you can install an app like quick boot and use it for booting into recovery.
Пратено со Tapatalk 2 од мојот SGSIII mini
vonuzu said:
And one more way, if you have rooted your phone, you can install an app like quick boot and use it for booting into recovery.
Пратено со Tapatalk 2 од мојот SGSIII mini
Click to expand...
Click to collapse
Added
Sent from my GT-I8190 using xda app-developers app
I dont understand how to do it with adb
Sent from my GT-I8190 using xda app-developers app
Sn0w0nS said:
I dont understand how to do it with adb
Sent from my GT-I8190 using xda app-developers app
Click to expand...
Click to collapse
Hi, I`m not ppero196 but how it works. Download this rar and extract on your PC. I always take the path to C:\Android\ . Then activate USB-Debugging on your device and connect your device to the PC. Open the cmd on your windows machine and type:
For download mode:
Code:
cd\
cd Android
adb reboot download
or for the recovery mode:
Code:
cd\
cd Android
adb reboot recovery
Have fun by the trying.
@ ppero196:
You write in the first post that:
Type adb reboot reccocery
Click to expand...
Click to collapse
Can you please fixed the command for reboot recovery? Thanks in advance.
Regards leather.face
Thx it worked.
Sent from my GT-I8190 using xda app-developers app
leather.face said:
Hi, I`m not ppero196 but how it works. Download this rar and extract on your PC. I always take the path to C:\Android\ . Then activate USB-Debugging on your device and connect your device to the PC. Open the cmd on your windows machine and type:
For download mode:
Code:
cd\
cd Android
adb reboot download
or for the recovery mode:
Code:
cd\
cd Android
adb reboot recovery
Have fun by the trying.
@ ppero196:
You write in the first post that:
Can you please fixed the command for reboot recovery? Thanks in advance.
Regards leather.face
Click to expand...
Click to collapse
All fixed
Sent from my GT-I8190 using xda app-developers app
No button combination?
Hello guys,
I can boot into recovery, pressing, up, home and power for a long time. The "Samsung Galaxy S3 Mini"-logo comes two times, and I press the three buttons all the time, until an "Android" comes. Than I am in Recovery mode. I haven't flashed or rooted my phone now, but is it not easier root and flash it via cutsom recovery mode?
Sorry for my bad English :/ If you habe some questions about my phone ask
What firmware are you running ??
It is the Original Samsung 4.1.1.
Can you post screenshot of "Settings->About device" page? Because on some devices (maybe from first batch) key combination just does not work.
Here is the Screenshot. I hope it helps.
{
"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"
}
Thanks :good:
This is a great guide! In theory you can also do this:
- backup your lfs partition (/dev/block/mmcblk0p19) with adb+dd when the phone has booted normally, backup that file
- backup your lfs partition (/dev/block/mmcblk0p19) with adb+dd inside CWM, have the file on your PC as well
Now you can reflash the partition with Odin/Heimdall and have the phone boot into either mode. The reason is because this partition contains params.blk which itself contains the boot mode (along other important parameters). It is always a good idea to have a backup of this partition, as well as other partitions (notably efs = mmcblk0p11 and modemfs = mmcblk0p12).
xd.bx said:
This is a great guide! In theory you can also do this:
- backup your lfs partition (/dev/block/mmcblk0p19) with adb+dd when the phone has booted normally, backup that file
- backup your lfs partition (/dev/block/mmcblk0p19) with adb+dd inside CWM, have the file on your PC as well
Now you can reflash the partition with Odin/Heimdall and have the phone boot into either mode. The reason is because this partition contains params.blk which itself contains the boot mode (along other important parameters). It is always a good idea to have a backup of this partition, as well as other partitions (notably efs = mmcblk0p11 and modemfs = mmcblk0p12).
Click to expand...
Click to collapse
Yeah.
But some user may find it too complicated.
I may add this in the future
Sent from my GT-I8190 using xda app-developers app
Just want to confirm the same
tux95 said:
Hello guys,
I can boot into recovery, pressing, up, home and power for a long time. The "Samsung Galaxy S3 Mini"-logo comes two times, and I press the three buttons all the time, until an "Android" comes. Than I am in Recovery mode. I haven't flashed or rooted my phone now, but is it not easier root and flash it via cutsom recovery mode?
Click to expand...
Click to collapse
Pictures attached
Thanks for this guide very helpfull
didinn1, what firmware version was preinstalled on your phone when you bought it ?
b_henry said:
didinn1, what firmware version was preinstalled on your phone when you bought it ?
Click to expand...
Click to collapse
b_henry it was 4.1.1
TWRP for flo has been released! http://forum.xda-developers.com/showthread.php?t=2380100
{
"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"
}
Root
1.) Download TWRP http://www.teamw.in/project/twrp2/193
2.) Download SuperSu for 4.3 here BUT SAVE ON DEVICE: https://plus.google.com/113517319477420052449/posts/GjbpgDdF6Fq
3.) Reboot to bootloader with either turning device on and holding POWER + VOL DOWN or under "About Tablet" > Tap "Build Number" 7 times > Back out > "Developer Options" > Check USB Debugging. Then in CMD Prompt/Terminal, type "adb reboot bootloader" without quotes
4.) In CMD prompt/Terminal type fastboot boot openrecovery-twrp-2.6.0.0-flo.img
5.) Click Backup - Backup boot, recovery, system and data
6.) Install > Download > UPDATE-SuperSU-v1.43.zip
7.) Reboot system
OPTIONAL
8.) Go back to bootloader after root and fully flash recovery with fastboot flash recovery openrecovery-twrp-2.6.0.0-flo.img
Or alternatively via ADB,
1.) Download TWRP http://www.teamw.in/project/twrp2/193
2.) Download SuperSu for 4.3 here: https://plus.google.com/113517319477420052449/posts/GjbpgDdF6Fq
3.) Reboot to bootloader with either turning device on and holding POWER + VOL DOWN or under "About Tablet" > Tap "Build Number" 7 times > Back out > "Developer Options" > Check USB Debugging. Then in CMD Prompt/Terminal, type "adb reboot bootloader" without quotes
4.) In CMD prompt/Terminal type fastboot boot openrecovery-twrp-2.6.0.0-flo.img
5.) Click Backup - Backup boot, recovery, system and data
6.) Advanced > ADB Sideload > Wipe both caches > Swipe to start ADB
7.) On desktop in cmd prompt > adb sideload /blah/blah/blah/UPDATE-SuperSU-v.1.43.zip
8.) Reboot system
OPTIONAL
9.) Go back to bootloader after root and fully flash recovery with fastboot flash recovery openrecovery-twrp-2.6.0.0-flo.img
It's actually much easier than doing all that.
1) Download Chainfires latest root and copy to SD card
2) Download TWRP
3) With tablet on, all drivers installed and Android SDK, and tablet plugged into PC... "ADB reboot bootloader"
4) rename the recovery you downloaded from TWRP to "recovery.img" and make sure you've copied it to your ADB folder
5) Type "fastboot flash recovery recovery.img" minus the quotes
6) use volume and power keys to select "recovery"
7) Once in TWRP flash SuperSU/UPDATE-SuperSU-v1.43.zip
8) when you reboot Superuser will be updated automatically by the Play Store
Nice tut btw!
ATGAdmin said:
-snip
Click to expand...
Click to collapse
That's the same thing just with renaming mate. I also prefer not to flash recovery fully until factory images are out, hence why I ask to backup first.
Nburnes said:
That's the same thing just with renaming mate. I also prefer not to flash recovery fully until factory images are out, hence why I ask to backup first.
Click to expand...
Click to collapse
yeah and minus the sideload...whatever floats your boat.
Thanks for posting it!
ATGAdmin said:
It's actually much easier than doing all that.
1) Download Chainfires latest root and copy to SD card
2) Download TWRP
3) With tablet on, all drivers installed and Android SDK, and tablet plugged into PC... "ADB reboot bootloader"
4) rename the recovery you downloaded from TWRP to "recovery.img" and make sure you've copied it to your ADB folder
5) Type fastboot flash recovery recovery.img
6) use volume and power keys to select "recovery"
7) Once in TWRP flash SuperSU/UPDATE-SuperSU-v1.43.zip
8) when you reboot Superuser will be updated automatically by the Play Store
Nice tut btw!
Click to expand...
Click to collapse
worked perfectly for mine, way easier and thanks!
Hope to see a video on this soon, I like to watch it being done as I do it!
Sent from my Nexus 7 using Tapatalk HD
Hell yes. Got my tablet today...unlocked, rooted, and have TWRP installed by dinner time.
Nburnes, thank you for your contribution. Any, and all help is appreciated. However, ATG's instructions are a little clearer, and easier. I have had my new Nexus for less then 12 hours, and it is already unlocked, and rooted. Yee-Haw! :good: Now bring on those ROMs!
Thanks, guys.
Thank you so much!
Rooted now and was able to get OTG to recognize 2 flashdrives simultaneously.
Thanks for the instructions ATGAdmin. Successfully unlocked, installed TWRP, and rooted in a matter of minutes!
Nburnes said:
TWRP for flo has been released! http://forum.xda-developers.com/showthread.php?t=2380100
Root
1.) Download TWRP http://www.teamw.in/project/twrp2/193
2.) Download SuperSu for 4.3 here BUT SAVE ON DEVICE: https://plus.google.com/+Chainfire/posts/Jkuu84odnx6
3.) fastboot boot recovery openrecovery-twrp-2.6.0.0-flo.img
4.) Click Backup - Backup boot, recovery, system and data
5.) Install > Download > UPDATE-SuperSU-v1.43.zip
6.) Reboot system
OPTIONAL
7.) Go back to bootloader after root and fully flash recovery with fastboot flash recovery openrecovery-twrp-2.6.0.0-flo.img
Or alternatively via ADB,
1.) Download TWRP http://www.teamw.in/project/twrp2/193
2.) Download SuperSu for 4.3 here: https://plus.google.com/+Chainfire/posts/Jkuu84odnx6
3.) fastboot boot recovery openrecovery-twrp-2.6.0.0-flo.img
4.) Click Backup - Backup boot, recovery, system and data
5.) Advanced > ADB Sideload > Wipe both caches > Swipe to start ADB
6.) On desktop in cmd prompt > adb sideload /blah/blah/blah/UPDATE-SuperSU-v.1.43.zip
7.) Reboot system
OPTIONAL
8.) Go back to bootloader after root and fully flash recovery with fastboot flash recovery openrecovery-twrp-2.6.0.0-flo.img
Click to expand...
Click to collapse
ATGAdmin said:
It's actually much easier than doing all that.
1) Download Chainfires latest root and copy to SD card
2) Download TWRP
3) With tablet on, all drivers installed and Android SDK, and tablet plugged into PC... "ADB reboot bootloader"
4) rename the recovery you downloaded from TWRP to "recovery.img" and make sure you've copied it to your ADB folder
5) Type fastboot flash recovery recovery.img
6) use volume and power keys to select "recovery"
7) Once in TWRP flash SuperSU/UPDATE-SuperSU-v1.43.zip
8) when you reboot Superuser will be updated automatically by the Play Store
Nice tut btw!
Click to expand...
Click to collapse
either way, anyone will appreciate the step by step procedure, so thanks to you both!
Got it rooted and working great thanks, let me use titanium backup now
Sent from my Nexus 7 using xda app-developers app
bring on the custom roms!!!!
Thanks guys everything worked flawlessly and tb worked great
Sent from my Nexus 7 using Tapatalk 2
got it, stupid filename crap, needed to add .img to the .img
dems86 said:
got it, stupid filename crap, needed to add .img to the .img
Click to expand...
Click to collapse
D'oh!
Mine is still giving me the error saying "error: cannot load 'recovery.img': No Error"
Nevermind I'm an idiot! I didn't put the recovery file in the right area!
adb devices
does not show anything, are there specific drivers for the nexus 7 2013, if so where would I locate them, cannot seem to find anything yet via simple searches('nexus 7 2013 driver", "nexus 7 driver", "adb nexus 7 2013", etc...)
anyone got a simple solution to connect adb to the nexus 7 2013?
Did & done! Thanks!
Sent from my Nexus 7²
Thanks a million!
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.
You may be have got attracted to those new roms out there on the internet and would have probably bricked your device.Or maybe did some modding and in worst case somehow your phone bootlooped.
so please follow the guide for unbricking or solving bootloop issues:
CAUTION:
[1] FIRST OF ALL, I AM NOT RESPONSIBLE FOR ANY DAMAGE TO YOUR DEVICE.
[2] NEVER UNPLUG THE USB CABLE WHILE FLASHING IS IN PROGRESS.IT MIGHT PERMANENTLY BRICK UR DEVICE..
ONLY FOR ZENFONE 5,A501CG/00CG
download the required files:
[1] kitkat firmware: for zenfone5(a501cg/00cg only other zf5 users download appropriate firmware from asus support page): http://dlcdnet.asus.com/pub/ASUS/ZenFone/A500CG/UL-ASUS_T00F-WW-2.21.40.44-user.zip
[2] adb/fastboot files: from here
[3] device drivers:if you do not have device drivers download and install pc link on pc from asus website,it will automatically install device drivers on your pc.(download from: http://liveupdate01.asus.com/pub/ASUS/LiveUpdate/Release/ZenFone/APP/LinkRim/PCLinkSetup.exe)
IF U R BRICKED PROCEED FROM STEP 2 ELSE FOR BOOTLOOP START FROM STEP 1:
step 1] try booting into recovery and perform a factory rest and wipe cache if this solves the bootloop(in most cases it should).if it still bootloops then follow the following tutorial
step 2]extract the fastboot files on the desktop and paste the firmware(it will be in .zip)in the fastboot folder
step 3]after copying the firmware also extract and copy the recovery.img and fastboot.img file from the firmware into the fastboot folder. (don't remove original firmware zip)
now your fastbootfolder should contain fastboot files+recovery.img+fastboot.img+firmware you dowloaded(compressed in .zip)
step4]boot into the fastboot by switching off the phone and powering it on by power+vol up key until asus logo comes up
if u r returning from some other rom u need to relock the bootloader so scroll some below to see how to relockbootloader.
step5]once you booted to fastboot ,open command promt in fastboot folder (downloaded earlier) by pressing right click+shift in any blank space on folder screen and selecting open command promt here.
in cmd write:
step6]
Code:
fastboot flash fastboot fastboot.img
step7] fastboot reboot-bootloader
wait until reboot is complete then write
step8]
Code:
fastboot flash recovery recovery.img
fastboot reboot-bootloader
step9] now we will be erasing data and cache for a clean flashing
Code:
fastboot clear data
fastboot clear cache
both of them take time and screen may turn off to save power so don't panic
next use volume keys to navigate to recovery and select it using power key .once your phone boots up showing android with belly open symbol press and hold volume up+volume down until recovery menu appears.if that does not open recovery try this:
hold volume down button, click and release vol up button,,,then finally release vol down button.
i admit it brothers,,it is sometimes really difficult to boot into recovery...but keep trying,,it is a bit difficult but is fruitful
if it doesnt appears it may be due to unssucceful flashing, unplug usb cable,force switch off phone by holding power button for few seconds.now again boot in bootloader by power button and vol up key and repeat from :step[8]
once in recovery select apply update from adb
step10] write on cmd
Code:
adb sideload <downloaded firmware name>.zip
for convenience you can rename firmware to kk.zip or any thing you like so command will be adb sideload kk.zip(it may take 15 to 20 mins)
step 11]once thats done select wipe data and cache in recovery and at last select reboot from recovery menu(dont skip this else you may face freezing on welcome screen itself)
hopefully you will boot into homescreen and be patient first bootup may take upto 20 mins.
[UPDATE] HOW TO RELOCK BOOTLOADER{only for zenfone 5 other device users pls google the procedure}
(USE THIS ONLY IF U R RETURNING FROM ANY CUSTOM ROM ITS NOT NEEDED FOR BOOTLOOPING PROBLEM)
hi guys i know u will be needing to relock the bootloader while returning to stock rom..
so what u have do is use the following steps before flashing fastboot.img that is before STEP [5] mentioned above
[1] download this file (its a zip file extract it using password zenfone-five.blogspot.com)...(link=https://drive.google.com/file/d/0B0o7qWuG7vvVRE9CV0hJWGRJS2c/view?usp=sharing)
[2]follow the on screen instructions
after the bootloader is locked carry on the steps from step[5]
PLEASE NOTE---THE UNLOCKING/LOCKING TOOL PROVIDED ABOVE IS NIETHER WRITTEN NOR OWNED BY ME...ALL CREDIT GOES TO ITS RESPECTIVE DEVELOPERS
this method can be used for:
1]unbricking
2]returning to stock rom
3]bootloop issues
IF YOU ARE NOT ABLE TO BOOT INTO FASTBOOT(maybe stuck on usb logo)--see this: http://www.asus.com/zentalk/forum.php?mod=viewthread&tid=33800 it is written by asus guys and will help you
thanks
if you face any issue please ask in comments...........
sources and credits===== www.windroidica.in
SCREENSHOTS DISCRIPTION:
pic 1] sideloading in progress
pic 2] the screen you will get when u will perform step [10] ( ignore the error "can't open /tmp/update-script.log")
pic 3]sideloading in progress (ignore the error: "please upgrade to newest 4.3 first")
pic 4] sideloading complete
NOT HITTING THANKS WILL LEAD TO A ZOMBIE APOCLYPSE(JUST KIDDING) ........dont forget to hit thanks!!!!
{
"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"
}
Kitkat link isn't working. Can I download it from another site? (Yes, it is a beginner problem )
DogeLordTR said:
Kitkat link isn't working. Can I download it from another site? (Yes, it is a beginner problem )
Click to expand...
Click to collapse
I wonder why it isn't working..... Yes u can download it from other sources. I will update the link as soon as possible...
update= download link working now...i omitted a "/" symbol and that gave the error
reserved----
AWESOME
Thanks for solution dude! You rock!
DogeLordTR said:
Thanks for solution dude! You rock!
Click to expand...
Click to collapse
Thanks bro... Ask for help anytime
hi, i have follow all the step, but until adb sideload <filename>.zip, it say at command prompt "error: device not found"
Now the phone stuck at asus logo.. :crying::cryinglease help......
zldjian said:
hi, i have follow all the step, but until adb sideload <filename>.zip, it say at command prompt "error: device not found"
Now the phone stuck at asus logo.. :crying::cryinglease help......
Click to expand...
Click to collapse
already solved the problem by using the method on this thread..
http://forum.xda-developers.com/zenfone-5/help/config-factory-partition-backup-t3316469
zldjian said:
already solved the problem by using the method on this thread..
http://forum.xda-developers.com/zenfone-5/help/config-factory-partition-backup-t3316469
Click to expand...
Click to collapse
great you have your problem solved,the error you were facing due to wrong drivers.
Cant boot recovery mode..
I am not able to boot into recovery mode..
rsunilkumar92 said:
I am not able to boot into recovery mode..
Click to expand...
Click to collapse
provide me more details. is it after flashing recovery.img? what is opening instead of recovery?
[email protected] said:
provide me more details. is it after flashing recovery.img? what is opening instead of recovery?
Click to expand...
Click to collapse
when i select recovery in bootloader, device will restart and stuck with the very frst logo.... "ASUS & Android Logo"
rsunilkumar92 said:
when i select recovery in bootloader, device will restart and stuck with the very frst logo.... "ASUS & Android Logo"
Click to expand...
Click to collapse
whats the current installed recovery?
[email protected] said:
whats the current installed recovery?
Click to expand...
Click to collapse
i tried TWRP ond also stock recovery
rsunilkumar92 said:
i tried TWRP ond also stock recovery
Click to expand...
Click to collapse
then try a guide on the forums by the name "de-brick with ruined partitions" i dont remember correctly but you'll find it easily
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