I have downloaded the files and unzipped them. How do i flash? Where do I enter: fastboot -i 0x413c flash recovery recovery.img
fastboot -i 0x413c reboot?
Im a total noob!!!!
You can download this pdf to get an idea. It's a must read document.
http://forum.xda-developers.com/attachment.php?attachmentid=397078&d=1283901727
Look at the fastboot section.
Welcome to the forum.
used this tonight to get StreakMod + DJSteve 1.8.0 going on my Streak. First timer with Android and all, worked like a charm.
I was looking for a light 2.1 rom and found this one: http://forum.xda-developers.com/showthread.php?t=1038337 (Lite edition)
Being a beginner, i got a few questions.
Do i need my phone flashed to V20E using .kdz beforehand? My current is V20B + fastboot.
There is kernel img provided, but iam not sure how to use it.
Which clockwork recovery do i need? As i understand 2.1 roms can only be flashed with old recoveries, such as 2.5.x.x . My current version is 3.0.2.4.
Thanks.
Img files can be flashed via fastboot commands:
on your PC type:
fastboot devices (makes sure its recognized)
fastboot -w (wipes data, cache)
fastboot erase boot
fastboot erase system
fastboot flash system system.img
fastboot flash boot boot.img
fastboot reboot
You'll need the fastboot drivers to be installed of course
Tnx for fast reply.
But do i need V20E.kdz rom specifically and flash my phone with KDZ updater? I couldnt find working links for V20E.kdz, only A,B&C.
berins said:
Tnx for fast reply.
But do i need V20E.kdz rom specifically and flash my phone with KDZ updater? I couldnt find working links for V20E.kdz, only A,B&C.
Click to expand...
Click to collapse
nope thats not needed
as the tittle says... i am soft-bricked, stuck on google animation.. I did a install of the full android rom 1.4 from zulu99 and everything worked like a champ but i wanted to go back to stock for the kids and now i am stuck
I can access fastboot and recovery on the device and compute recognizes it also..
I downloaded the stock image for marsh 3.2.0 and i flashed all the required files:
fastboot flash staging blob
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
it reboots and goes to the google animation and it just stays there!!!(left it there for a day!!!) i also tried to flashing fastboot flash tegra210-foster-e-p2530-0930-e02-00.dtb and did not fix it..
also tried to flash 3.1.0 same steps and no go... i know my adb files are up to date... any ideas?
I was able to flash full android 1.4 from zulu again and works like a champ but i need stock for the kiddos.
try flashing twrp recovery from there wipe system and data partition then reboot into fastboot flash 3.2 again
i was stuck at the boot animation about a month ago after the 3.2 update.... see my post in this thread:
http://forum.xda-developers.com/shi...ion-screen-t3263143/post67564062#post67564062
please note: i used the 3.1 recovery image because the 3.2 image had not been released yet. have not tried it with the newer 3.2 image
also, if you follow my post and install the 3.1 image....be sure to flash the files in the order posted! some will flash quickly, but one or two took awhile to complete, so be patient and wait for each step to finish before moving on to the next.
yes, i saw ur post and how you solved it and i did try the same thing and it did not fix it.. it just gets me to the animation screen... i am gonna try to load twrp from fastboot, wipe.. then re install everything and once done, i will try to fastboot -w and see if that helps me...
foomanjackel said:
i was stuck at the boot animation about a month ago after the 3.2 update.... see my post in this thread:
http://forum.xda-developers.com/shi...ion-screen-t3263143/post67564062#post67564062
please note: i used the 3.1 recovery image because the 3.2 image had not been released yet. have not tried it with the newer 3.2 image
also, if you follow my post and install the 3.1 image....be sure to flash the files in the order posted! some will flash quickly, but one or two took awhile to complete, so be patient and wait for each step to finish before moving on to the next.
Click to expand...
Click to collapse
lalord69 said:
yes, i saw ur post and how you solved it and i did try the same thing and it did not fix it.. it just gets me to the animation screen... i am gonna try to load twrp from fastboot, wipe.. then re install everything and once done, i will try to fastboot -w and see if that helps me...
Click to expand...
Click to collapse
if you un pack the nvidia recovery image there is a scipt inside caled flashall.bat one of the steps run in there is a reboot to fastboot after you flash the boot.image
flash staging blob
fastboot flash boot boot.img
fastboot reboot
adb wait-for-device
adb reboot bootloader
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot reboot
echo Press any key to exit...
pause >nul
exit
Hi there,
sorry, if this was answered before, but I couldn't find the correct answer:
After trying to flash a custom ROM (CMOD) I'm stuck now at the Cyanogen Mod boot animation.
If pressing "Power" button for a while the phone reboots, but gives me again the same boot animation (after ZUK logo).
If pressing "Power" + "Volume +" + "Volume -" buttons for a while the phone reboots, but gives me again the same boot animation (after ZUK logo).
The phone is not recognized via USB on a computer.
Anybody has still an idea what I could do?
Many thanks in advance for hints
best regards
m
What are the steps you followed before you ended up in this situation? What rom were you previously on? Provide as much details as you can without being redundant.
KKaushal said:
What are the steps you followed before you ended up in this situation? What rom were you previously on? Provide as much details as you can without being redundant.
Click to expand...
Click to collapse
I was coming from latest stock. The attempt was to flash CM14.
1.) flash in the thread linked twrp
2.) flash CM14 and Nougat GAPPS micro
3.) reboot ok
4.) fingerprint didn't react, so went back to recovery and flashed both again, causing this loop
many thanks again for any help/hint
best regards
m
If the first time boot with the rom and gapps was okay, maybe you should try wiping /system, /data, /dalvik and /cache and reflash the rom again.. Since you were in stock cmos 12.1, I think it'll be better if you flash official cm13 first, and then jump to cm14 from there to minimize sensor issues such as with the fingerprint like you experienced.
meikelrix said:
any help/hint
Click to expand...
Click to collapse
Mate if you think you're done with everything and nothing seems to help, just search around here how to flash ZUI using QPST. That's the last resort which saves your device from the gravest issues.
However, let me know if you can or can't find that thread or anything else, I'll be happy to help. :good:
KKaushal said:
If the first time boot with the rom and gapps was okay, maybe you should try wiping /system, /data, /dalvik and /cache and reflash the rom again.. Since you were in stock cmos 12.1, I think it'll be better if you flash official cm13 first, and then jump to cm14 from there to minimize sensor issues such as with the fingerprint like you experienced.
Click to expand...
Click to collapse
thank you, but I did wiping and reflash => causing the loop
best regards
m
sahu.prashant said:
Mate if you think you're done with everything and nothing seems to help, just search around here how to flash ZUI using QPST. That's the last resort which saves your device from the gravest issues.
However, let me know if you can or can't find that thread or anything else, I'll be happy to help. :good:
Click to expand...
Click to collapse
many thanks for offering. Any chance to provide a link, in order to spare some time?
best regards
m
meikelrix said:
I did wiping and reflash => causing the loop
Click to expand...
Click to collapse
There are many reasons for a bootloop. Start from scratch once again. Flash stock cos12.1 (or restore if you have a backup), flash cm13 from there after you load twrp, go from cm13 to cm14. I think this should be the way to go to avoid sensor issues. Once in stock, you can go from there. Good luck.
http://forum.xda-developers.com/zuk-z1/development/how-to-flash-zuk-z1-zui-version-t3265741
This is the thread link right here explaining all the steps (although it's a little tricky to follow )
That was the good part....
The worst part is that the download links are dead
I'll try snooping around more and see if I can find anything else and you should try too since the thread will give you an idea what to look for.
If the search comes up empty, I'll upload the files tomorrow by all means
Fortunately found a link....
http://forum.xda-developers.com/showpost.php?p=64202059&postcount=14
sahu.prashant said:
http://forum.xda-developers.com/zuk-z1/development/how-to-flash-zuk-z1-zui-version-t3265741
This is the thread link right here explaining all the steps (although it's a little tricky to follow )
That was the good part....
The worst part is that the download links are dead
I'll try snooping around more and see if I can find anything else and you should try too since the thread will give you an idea what to look for.
If the search comes up empty, I'll upload the files tomorrow by all means
Fortunately found a link....
https://www.androidfilehost.com/?w=files&flid=40618
Click to expand...
Click to collapse
Heya
many thanks again for your much appreciated help!
I'll try to figure and provide the outcome...
best regards
m
KKaushal said:
There are many reasons for a bootloop. Start from scratch once again. Flash stock cos12.1 (or restore if you have a backup), flash cm13 from there after you load twrp, go from cm13 to cm14. I think this should be the way to go to avoid sensor issues. Once in stock, you can go from there. Good luck.
Click to expand...
Click to collapse
thank you, but I can't start from scratch, since the loop won't let me in
Happy to help and hopefully, outcome will be desirable.
meikelrix said:
thank you, but I can't start from scratch, since the loop won't let me in
Click to expand...
Click to collapse
Power button + volume up gets you into recovery mode.
(I think) Power button + volume down gets you into fastboot mode. Not sure about this one, you can search around for the key combo to get into specific modes. From fastboot mode, you can flash the stock cos 12.1 provided from the official support page of cyanogen. Make sure you download the zip compatible with fastboot mode. When you finally get to cos 12.1, you can install Twrp recovery (also available among the forum threads or from the official twrp website), then flash cm13, reboot to check if everything works and then finally move to cm14.
You can post here in case of problems/confusions in any step.
Alternately, in place of cos12.1, you can flash zui as suggested. Search in the 'help, q/a' section of zuk z1 in this forum. You can find the tutorial there. Good luck.
KKaushal said:
Power button + volume up gets you into recovery mode.
(I think) Power button + volume down gets you into fastboot mode. Not sure about this one, you can search around for the key combo to get into specific modes. From fastboot mode, you can flash the stock cos 12.1 provided from the official support page of cyanogen. Make sure you download the zip compatible with fastboot mode. When you finally get to cos 12.1, you can install Twrp recovery (also available among the forum threads or from the official twrp website), then flash cm13, reboot to check if everything works and then finally move to cm14.
You can post here in case of problems/confusions in any step.
Alternately, in place of cos12.1, you can flash zui as suggested. Search in the 'help, q/a' section of zuk z1 in this forum. You can find the tutorial there. Good luck.
Click to expand...
Click to collapse
Hi,
after draining the battery (and loading up a bit) I could get access to fastboot. From there I flashed latest twrp (3.0.2) and booted into twrp.
From twrp I wiped and then flashed latest Nuclear ROM & Gapps. After rebooting I'm still ending up in twrp, again?
PS: flashing the cos 12.1 via fastboot mode didn't work, due to below:
"
fastboot -i 0x2b4c update cm-12.1-YOG4PAS9IG-ham-signed-fastboot-b9cce4220b.zip
target reported max download size of 1610612736 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(14844,0xa3181000) malloc: *** mach_vm_map(size=1585467392) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1583882000 bytes
error: update package missing system.img
"
many thanks again for any help/hints
best regards
m
meikelrix said:
Hi,
after draining the battery (and loading up a bit) I could get access to fastboot. From there I flashed latest twrp (3.0.2) and booted into twrp.
From twrp I wiped and then flashed latest Nuclear ROM & Gapps. After rebooting I'm still ending up in twrp, again?
PS: flashing the cos 12.1 via fastboot mode didn't work, due to below:
"
fastboot -i 0x2b4c update cm-12.1-YOG4PAS9IG-ham-signed-fastboot-b9cce4220b.zip
target reported max download size of 1610612736 bytes
archive does not contain 'boot.sig'
archive does not contain 'recovery.sig'
fastboot(14844,0xa3181000) malloc: *** mach_vm_map(size=1585467392) failed (error code=3)
*** error: can't allocate region
*** set a breakpoint in malloc_error_break to debug
failed to allocate 1583882000 bytes
error: update package missing system.img
"
many thanks again for any help/hints
best regards
m
Click to expand...
Click to collapse
Extract cos zip files and flash separately
Enviado desde mi ZUK Z1 mediante Tapatalk
acuicultor said:
Extract cos zip files and flash separately
Enviado desde mi ZUK Z1 mediante Tapatalk
Click to expand...
Click to collapse
That was it. I did the following sequence:
fastboot -i 0x2b4c flash aboot emmc_appsboot.mbn
fastboot -i 0x2b4c flash modem NON-HLOS.bin
fastboot -i 0x2b4c flash rpm rpm.mbn
fastboot -i 0x2b4c flash sbl1 sbl1.mbn
fastboot -i 0x2b4c flash dbi sdi.mbn
fastboot -i 0x2b4c flash splash splash.img
fastboot -i 0x2b4c flash tz tz.mbn
fastboot -i 0x2b4c flash persist persist.img
reboot device
fastboot -i 0x2b4c flash system system.img
fastboot -i 0x2b4c flash boot boot.img
fastboot -i 0x2b4c flash recovery recovery.img
fastboot -i 0x2b4c flash cache cache.img
fastboot -i 0x2b4c flash userdata userdata.img
fastboot reboot
Then I was back to stock. After that I started from scratch to flash twrp, Nuclear and Gapps.
Many thanks to all that helped!
best regards
m
Kinda stuck on Sending system. Help?
Try this
https://forum.xda-developers.com/zuk-z1/help/boot-loop-cyanogen-logo-t3666056
moriyaprateek said:
Kinda stuck on Sending system. Help?
Click to expand...
Click to collapse
AFAIR, I followed https://stackoverflow.com/questions/34299245/fastboot-flash-system-img-error
=> "fastboot flash –S 256M system PATH_TO_SYSTEM.img" (the -S switch did the trick)
Even i am in the same situation how to fix it bro
meikelrix said:
Heya
many thanks again for your much appreciated help!
I'll try to figure and provide the outcome...
best regards
m
Click to expand...
Click to collapse
stuck with same situation plz need help
hi guys/girls
android TV shield 2015 16 GB model.
well it is long been while.. i gave up with 5.1 i want to more upgrades. but it was already old problem. i ignored it.
but i want to upgrade right now =/
i did installed via ADB
i remember i did type
fastboot flash system system.img
fastboot flash vendor vendor.img
fastboot -w
fastboot flash recovery recovery.img
fastboot reboot
any someone have idea how to fix those?
thx you
Any someone else have idea about this how to fixed? thank you a lot.
you didnt flash the blobs needed for it
Code:
fastboot flash staging blob
Adromir said:
you didnt flash the blobs needed for it
Code:
fastboot flash staging blob
Click to expand...
Click to collapse
what does flash staging blob? ya it seems i didn't add those
I assume that is the updated bootloader. Id flash it as first and then flash all the other things
Adromir said:
I assume that is the updated bootloader. Id flash it as first and then flash all the other things
Click to expand...
Click to collapse
tsorry late reply, thx you a lot. it works perfect now
Glad I could help