Related
Hi,
Last night i was playing with my N4 (with some root applications) and an app asked for a reboot. I just pressed yes so that the phone will reboot (I have done this earlier without any issues). Suddenly the device doesn't boot up. My N4 is stuck at a black screen. While trying to boot up, the Google logo appears and then a black screen. It doesn't advance to the 'X' logo. I'm running on stock, rooted phone (used N4 toolkit by Wugfresh to root).
I'm able to boot into recovery although. I tried all the possible means, wiped cache, dalvik cache, did a factory reset, backed up the system and tried to restore the same. Nothing happened.
Then i tried the "Back to Stock" option in the N4 toolkit and chose the option "Soft-brick/Bootloop" to recover my N4. These are what happened:
Downloaded the 4.2.2 image from Google servers and tried to flash in the device with prior instruction from the toolkit. Everything went fine until the flashing process. In the last step the CMD window opens up saying it is unrooting and flashing stock and immediately it'll bring up a complete message saying the flashing is complete and to wait until the device boots up. But nothing happens again.
I tried the automatic flashing and on the downloading window it saying download failed and hash checks failed meaning its not downloading.
I searched all the possible threads in a day to find a similar problem but in vain. I'm not a noob but i'm too lazy . But i would do anything to bring my N4 back to life. Anyone please show me a direction.
In short:
Status: Soft-Bricked (guess so), black screen after Google logo
Version: Stock 4.2.2 (rooted+busybox+supersu+twrp)
Able to boot to recovering: Yes, bootable to recovery and bootloader.
Tried Nexus toolkit recovery: Yes but in vain.
Gave up: No and never, I'm searching and searching for answers and I'm worried if I'll end up in a hard brick. :crying:
Guys, please help.
Thank You!
Aghil
I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?
ameinild said:
I'm just taking a wild guess here - I'm not responsible if anything bad happens, and you might want to wait to someone else seconds my suggestion in any case (although I can't imagine things getting worse as long as you flash N4 stuff). But have you tried flashing a new boot.img/reset kernel from recovery or via fastboot/toolkit?
Click to expand...
Click to collapse
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
aghilvr said:
Err...nope I haven't tried any and will wait until someone seconds you. Meanwhile I have wiped off the ROM through the option in recovery. Still will I be able to do what you said? Also if could direct me to a "how-to" thread would be great. Just that I don't wanna mess up again.
Click to expand...
Click to collapse
No, my suggestion would require that the ROM is still on the phone, so you should restore your ROM prior to my suggestion. And I'm by no means an expert (therefore the disclaimer), but I *think* that since it's a bootup problem, it could be solved by flashing a new boot.img (which is essentially flashing a new kernel to the system).
But yeah, let's see if others think this might help, haven't researched it, is at work right now. Just throwing in a suggestion, that's all...
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
I *think* (again, I'm totally not sure about this, as I haven't tried it) that you can sideload a ROM via zip file from recovery, but since I haven't tried it I'm not sure - can anybody confirm???
EDIT: Chromium's suggestion is better, by pushing the ROM.zip to the device and flashing from recovery (check md5 first, just in case).
aghilvr said:
Also, is there a way to transfer a ROM to N4 through fastboot? So that I can install the ROM through TWRP.
Click to expand...
Click to collapse
Yes there is. Your nexus is not bricked and this is why you shouldnt use toolkits to do things. This is honestly an extremely easy and simple fix. Use adb to push a rom onto the n4.
Code:
adb push \path\to\rom.zip /sdcard
Boot into recovery, do a full wipe, and flash the rom.
You said you downloaded the Google images.
Just boot your phone into the bootloader and run the flashall.bat that is in the Google image folder.
Note this will probably fully wipe you're phone in the process
Sent from my Nexus 4 using xda app-developers app
try this it may help u this toolkit is damn easy to use :
http://forum.xda-developers.com/showthread.php?t=1995688
Okay, thanks guys. I'm on it. Will let you know when I'm done.
That same thing happened to me once. I had to extract the google file and look for the 4 img files(bootloader, system, userdata, recovery) and flash them with toolkit manually and it fixed it, but it erased everything on my sd
I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?
aghilvr said:
I tried to load the file "occam-jdq39-factory-345dc199.tar" into my phone using the ADB sideload feature in the toolkit. I don't have the SDK installed hence I depended the tool again. But now the tool only loads .zip file and not .tar as the one that i downloaded. Am I doing it right?
Click to expand...
Click to collapse
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.
chromium96 said:
K if you have a custom recovery installed, there isnt much you need to do to fix the issue.
First setup adb/fastboot by reading this
Then boot the phone into recovery, and plug it into the computer. Open a new command prompt window and use adb like this:
Code:
adb push \path\to\rom.zip /sdcard
Then you can unplug the phone. From recovery go to the install menu, find the rom that you just pushed, and flash it.
Click to expand...
Click to collapse
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images
aghilvr said:
Okay, installing the SDK. And the command saying "rom.zip", the file that I have is like "rom.tar". Does it matter? I downloaded the rom from here https://developers.google.com/android/nexus/images
Click to expand...
Click to collapse
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.
chromium96 said:
No the tar wont work through recovery. You should download a rom from here or here.
If you want to flash the stock rom through recovery you can download it here.
Click to expand...
Click to collapse
Oh that's why it didn't work all the time
Thanks chromium :fingers-crossed:
Hey thanks guys, my device is back to normal. Chromium a special thanks for you for helping me out. See you guys with my next problem/queris!
hello everyone..
In serious need of help here and hope someone can help..
Due to the massive battery drain issue I have been having, I tried to flash the original stock rom on my nexus 7 and
things have gone downhill really bad..
in the past, I flashed using this guide (http://forum.xda-developers.com/showthread.php?t=1907796)
without any problems but last night.. I encountered errors when trying to flash the bootloader
and radio IMG files.. neeedless to say when it comes to flashing the rom in, it came out with errors and my nexus remain OS-less
the errors when trying to flash the bootloader and radio are
"failed (command write failed (Invalid Argument))"
can anyone help me?
p.s :- if anyone can even suggest me a easier way to flash custom roms in and so forth, your suggestion will be most welcomed..
also, I did try wug's rootkit plus the nexus 7 toolkit or something, both came out errors too when too do any flashing in relating to
the bootloader or system.. thanks
Why were you trying to flash the bootloader? Were you trying to update to 4.18?
Username invalid said:
Why were you trying to flash the bootloader? Were you trying to update to 4.18?
Click to expand...
Click to collapse
actually, my bootloader boots fine, it shows tilapia 4.18.
so does this mean I dont have to flash it?
if I dont have to flash the bootloader, do I have to flash the radio?
sorry, kind of a noob in these things..
Anyway, is it normal for the bootloader flash attempt to fail?
hamiksu said:
Anyway, is it normal for the bootloader flash attempt to fail?
Click to expand...
Click to collapse
No, it's not normal for it to fail.
You really don't need to flash either unless one of them is screwed up or you are upgrading to a newer version. Bootloader flashes are risky anyway. To avoid flashing them, you can either remove code from the updater script or remove them from the factory image files entirely.
korockinout13 said:
No, it's not normal for it to fail.
You really don't need to flash either unless one of them is screwed up or you are upgrading to a newer version. Bootloader flashes are risky anyway. To avoid flashing them, you can either remove code from the updater script or remove them from the factory image files entirely.
Click to expand...
Click to collapse
hmm, ok..
then I will go back home and do the system flashing and try and post out the errors it stated there..
really hope to get my nexus back on line...
This is what I get when I tried to flash the image
Hope someone can guide me on what to do next.
hamiksu said:
This is what I get when I tried to flash the image
Hope someone can guide me on what to do next.
Click to expand...
Click to collapse
Try to unlock your bootloader before flashing image with the command:
fastboot oem unlock
ameinild said:
Try to unlock your bootloader before flashing image with the command:
fastboot oem unlock
Click to expand...
Click to collapse
it says my bootloader is already unlocked
hamiksu said:
it says my bootloader is already unlocked
Click to expand...
Click to collapse
Then it sounds like something happened to your system partition that should not have happened.
Are you sure the system image you're trying to flash is valid, do the md5 sums match?
How about flashing another system image?
Or flash a custom recovery, and install a new ROM from there?
ameinild said:
Try to unlock your bootloader before flashing image with the command:
fastboot oem unlock
Click to expand...
Click to collapse
ameinild said:
Then it sounds like something happened to your system partition that should not have happened. Sorry, can't help you there...
Click to expand...
Click to collapse
meaning my system partition is screwed?
anyone knows how to go around this problem?
p.s :- anyway ameinild, thanks for trying to help
hamiksu said:
p.s :- anyway ameinild, thanks for trying to help
Click to expand...
Click to collapse
I edited my post with some more suggestions to try first
ameinild said:
I edited my post with some more suggestions to try first
Click to expand...
Click to collapse
yup, the image i tried a few.. even tried stock rom image.
tried both nexus 7 toolkit
as well as wugs nexus root tool kit.
they all seem to encounter problems when trying to "push" the rom images in or something.
is there a way to like format the entire thing and install from scratch>?
hamiksu said:
is there a way to like format the entire thing and install from scratch>?
Click to expand...
Click to collapse
Sorry, I can't really find anything for the N7... Hope someone else can chime in.
ameinild said:
Sorry, I can't really find anything for the N7... Hope someone else can chime in.
Click to expand...
Click to collapse
Yea, I hope someone will pop in and be my guardian angel too..
Thanks again, Ameinild
tried to flash stock rom using wug's rootkit..
this is what happens...
hamiksu said:
tried to flash stock rom using wug's rootkit..
this is what happens...
Click to expand...
Click to collapse
As a rule, don't do anything with a toolkit that you don't know how to do yourself with the relevant fastboot or ADB commands. It has a nasty tendency of leaving you in a lurch.
I noticed that your last run of Wug's toolkit did claim to successfully flash your recovery. Have you been able to access it from the fastboot menu on the device? If so, that's a major step forward.
Perhaps most importantly (based on your mentioning of tilapia earlier), are you 100% certain that you are trying to flash the factory image for your model of the Nexus 7?
Rirere said:
As a rule, don't do anything with a toolkit that you don't know how to do yourself with the relevant fastboot or ADB commands. It has a nasty tendency of leaving you in a lurch.
I noticed that your last run of Wug's toolkit did claim to successfully flash your recovery. Have you been able to access it from the fastboot menu on the device? If so, that's a major step forward.
Perhaps most importantly (based on your mentioning of tilapia earlier), are you 100% certain that you are trying to flash the factory image for your model of the Nexus 7?
Click to expand...
Click to collapse
Yes, I am absolutely sure it is the image for my nexus 7.. which is 3g/wifi model, not just wifi only..
image file is downloaded using wug's rootkit too..
file name = nakasig-jdq39-factory-0798439d.tgz
as the snapshot shows.. it keeps showing failed when "sending system"
please tell me you have an idea on why it keeps failing there...
*crosses fingers*
p.s :- after that (numerous) wug's toolkit attempt to flash back stock rom, I tried booting to recovery and it shows the android on its back with a red exclamation mark on its open body chasis
I'm assuming you haven't tried this yet, if you have tried this just ignore.
1 - Download - http://techerrata.com/file/twrp2/grouper/openrecovery-twrp-2.6.0.0-grouper.img
2 - fastboot flash recovery openrecovery-twrp-2.6.0.0-grouper.img
If flashes fine:
Power off Nexus, Hold Volume down and Power on, keep holding power down until you get to recovery.
Then:
Either - Get a USB OTG and put a ROM on a USB Stick, go to "install" - "Use external storage" find the rom and flash it.
or
Plug in to PC whilst in recovery, - Mount Storage - Now the Nexus should pop up on PC, Drag ROM to Nexus. Unmount and then try to flash.
Let me know how you get on with this.
Regards.
hamiksu said:
Yes, I am absolutely sure it is the image for my nexus 7.. which is 3g/wifi model, not just wifi only..
image file is downloaded using wug's rootkit too..
file name = nakasig-jdq39-factory-0798439d.tgz
as the snapshot shows.. it keeps showing failed when "sending system"
please tell me you have an idea on why it keeps failing there...
*crosses fingers*
p.s :- after that (numerous) wug's toolkit attempt to flash back stock rom, I tried booting to recovery and it shows the android on its back with a red exclamation mark on its open body chasis
Click to expand...
Click to collapse
That's because you have stock recovery installed now and it's unable to verify that your device is in working order, hence the red mark. Find TWRP for your device, download the .img and try to flash it with fastboot flash recovery <path-to-recovery.img>. Since you can at least get into a recovery, it's possible you'll be able to use onboard recovery tools to see what state your internal partitions are in.
Until there's a little more info available, there's nothing I can say that's not pure conjecture.
my moto x play is stuck in boot loop m not able to downgrade it on 5.1 and cant upgrade to 6.0(because there is no 6.0 stock file on air still)
my question is is there any way to enable usb debugging and allow oem unlock via fast boot cmds.?
because if there is a way to unlock boot lodear to i can install twrp recovery.
please help me
http://lmgtfy.com/?q=fastboot+allow+usb+debugging
http://android.stackexchange.com/qu...ndroid-if-forgotten-pattern-for-screen-unlock
Nico3d3 said:
http://lmgtfy.com/?q=fastboot+allow+usb+debugging
http://android.stackexchange.com/qu...ndroid-if-forgotten-pattern-for-screen-unlock
Click to expand...
Click to collapse
unfortunately not working for me.
http://android.stackexchange.com/qu...ndroid-if-forgotten-pattern-for-screen-unlock
If the instructions are too technical for you and you can't figure out how to make it happen, following the tutorial, then I'm afraid I'll have a hard-time helping you unless I have the phone in my hand. Unfortunately, hacking phone is a process where we learn from our mistakes. I had a few times where I almost bricked my then new to me Samsung Galaxy SIII, but then I searched the Internet trying and trying again until I understood how do to thing to get it back to work.
Maybe, try to flash TWRP temporarily, you should at least give it a shot:
fastboot boot TWRP-lux-2.8.7-r4.img
Click to expand...
Click to collapse
I'm pretty sure it will work even if your bootloader is locked because it just install it temporarily. You execute the flashboot command, then you navigate the option on the phone until you see the option "Reboot recovery". It will reboot in TWRP recovery, then you could use the interface to install this recovery backup of Marshmallow. Instructions on how to install the recovery backup in TWRP, are here.
Nico3d3 said:
http://android.stackexchange.com/qu...ndroid-if-forgotten-pattern-for-screen-unlock
If the instructions are too technical for you and you can't figure out how to make it happen, following the tutorial, then I'm afraid I'll have a hard-time helping you unless I have the phone in my hand. Unfortunately, hacking phone is a process where we learn from our mistakes. I had a few times where I almost bricked my then new to me Samsung Galaxy SIII, but then I searched the Internet trying and trying again until I understood how do to thing to get it back to work.
Maybe, try to flash TWRP temporarily, you should at least give it a shot:
I'm pretty sure it will work even if your bootloader is locked because it just install it temporarily. You execute the flashboot command, then you navigate the option on the phone until you see the option "Reboot recovery". It will reboot in TWRP recovery, then you could use the interface to install this recovery backup of Marshmallow. Instructions on how to install the recovery backup in TWRP, are here.
Click to expand...
Click to collapse
brother another think is that when m on recovery mode and click on apply update from sdcard its shows (Internal and external memory cannot be mounted)
i think my sdcard storege is corrupted m not able to right any thing. and i had already tried that twrp recovey Method witch is not work for me may be tha resasion is corrupte memory.
here is the result
I really want to know why people flash soak tests without unlocking the bootloader? Do they really know what they are doing?
treibstoff said:
I really want to know why people flash soak tests without unlocking the bootloader? Do they really know what they are doing?
Click to expand...
Click to collapse
m also asking same qustion to me
ok do you have any idea when the stock firmware will be on air..?
anujanuj said:
m also asking same qustion to me
ok do you have any idea when the stock firmware will be on air..?
Click to expand...
Click to collapse
No unfortunetly not... You have to wait ...
anujanuj said:
m also asking same qustion to me
ok do you have any idea when the stock firmware will be on air..?
Click to expand...
Click to collapse
Try these commands only
fastboot erase cache
fastboot erase userdata
fastboot reboot
effingbadluck said:
Try these commands only
fastboot erase cache
fastboot erase userdata
fastboot reboot
Click to expand...
Click to collapse
already did via manual via recovery mode
any way to format my phone memory not clear data i mean format full drive may be then i can flash 5.1 again
anujanuj said:
already did via manual via recovery mode
any way to format my phone memory not clear data i mean format full drive may be then i can flash 5.1 again
Click to expand...
Click to collapse
Do it this time using fastboot commands.It's worth a try
anujanuj said:
already did via manual via recovery mode
any way to format my phone memory not clear data i mean format full drive may be then i can flash 5.1 again
Click to expand...
Click to collapse
Hi anuj if you are using indian moto x play then try to flash this one. It will help you
http://www.filefactory.com/file/6jg...23.118-32_cid7_subsidy-DEFAULT_CFC_v2.xml.zip
umair deshmukh said:
Hi anuj if you are using indian moto x play then try to flash this one. It will help you
http://www.filefactory.com/file/6jg...23.118-32_cid7_subsidy-DEFAULT_CFC_v2.xml.zip
Click to expand...
Click to collapse
der umair can i have the alternative link of this because file fectory didnt provide resume links
and
still i had tried these roms
1. X_Play_Retail_India_XT1562_LPD23.118-10_CFC.xml
2.XT1562_LUX_RETASIA_DS_5.1.1_LPD23.118-12_cid7_subsidy-DEFAULT_CFC.xml.zip
3.XT1563_LUX_RETLA_DS_5.1.1_LPD23.118-6.1_cid12_subsidy-DEFAULT_CFC.xml
4.Blur_Version.24.11.18.lux_retasia_ds.retasiaall.en.03 (this is ota)
umair deshmukh said:
Hi anuj if you are using indian moto x play then try to flash this one. It will help you
http://www.filefactory.com/file/6jg...23.118-32_cid7_subsidy-DEFAULT_CFC_v2.xml.zip
Click to expand...
Click to collapse
i think this is the alternative
https://mega.nz/#!3dAR3AZZ!UvQco3Bf_BqSEeMfwEMjZUm8quYV31lu5gYoj4PKs3E
anujanuj said:
der umair can i have the alternative link of this because file fectory didnt provide resume links
and
still i had tried these roms
1. X_Play_Retail_India_XT1562_LPD23.118-10_CFC.xml
2.XT1562_LUX_RETASIA_DS_5.1.1_LPD23.118-12_cid7_subsidy-DEFAULT_CFC.xml.zip
3.XT1563_LUX_RETLA_DS_5.1.1_LPD23.118-6.1_cid12_subsidy-DEFAULT_CFC.xml
4.Blur_Version.24.11.18.lux_retasia_ds.retasiaall.en.03 (this is ota)
Click to expand...
Click to collapse
Dude try this one http://www.filefactory.com/file/4ar...LPD23.118-22_cid7_subsidy-DEFAULT_CFC.xml.zip mine problem was solved i hop it will solve your problem also
And sorry i don't have an alternative link..
umair deshmukh said:
Dude try this one http://www.filefactory.com/file/4ar...LPD23.118-22_cid7_subsidy-DEFAULT_CFC.xml.zip mine problem was solved i hop it will solve your problem also
And sorry i don't have an alternative link..
Click to expand...
Click to collapse
tried these roms nothing happened
Nico3d3 said:
http://lmgtfy.com/?q=fastboot+allow+usb+debugging
http://android.stackexchange.com/qu...ndroid-if-forgotten-pattern-for-screen-unlock
Click to expand...
Click to collapse
can you give me the link or tell me how to allow oem unlock via fastboot....?
treibstoff said:
I really want to know why people flash soak tests without unlocking the bootloader? Do they really know what they are doing?
Click to expand...
Click to collapse
Nico3d3 said:
http://lmgtfy.com/?q=fastboot+allow+usb+debugging
http://android.stackexchange.com/qu...ndroid-if-forgotten-pattern-for-screen-unlock
Click to expand...
Click to collapse
hello frnds here is the updated 6.0 file uploaded if i will flash this file so my phone can be start..?
http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1
this is stock 6.0 firmware file
anujanuj said:
hello frnds here is the updated 6.0 file uploaded if i will flash this file so my phone can be start..?
http://www.filefactory.com/folder/dd05c058d3ff8dbe/?sort=created&order=DESC&show=100&page=1
this is stock 6.0 firmware file
Click to expand...
Click to collapse
your problem solved or not?
How could I flash recovery without pc? I have twrp at the moment and i want the CWM. Im on 6.0 Emui 4.1
staska_lt said:
How could I flash recovery without pc? I have twrp at the moment and i want the CWM. Im on 6.0 Emui 4.1
Click to expand...
Click to collapse
Try with the Flashify app.
GaT7 said:
Try with the Flashify app.
Click to expand...
Click to collapse
I tried and i got black screen
Flash it via TWRP then? TWRP supports flashing .img too if you need to. :|
3. Post using a clear and descriptive subject and message.
You're most likely to receive a helpful answer to your question, if you use a short subject title that describes your problem and a message that explains in detail, what your problem is and what you've done to try solving it.
Click to expand...
Click to collapse
Source (Forum rules): http://forum.xda-developers.com/announcement.php?a=81
Just sayin bro...
And btw some things just dont work well without a PC. Even though it might be possible to work around it you might just wanna do this on a computer with these commands in adb:
Code:
adb reboot bootloader
and
Code:
fastboot flash recovery recovery.img
and then reboot
PCSE said:
Source (Forum rules): http://forum.xda-developers.com/announcement.php?a=81
Just sayin bro...
And btw some things just dont work well without a PC. Even though it might be possible to work around it you might just wanna do this on a computer with these commands in adb:
and
and then reboot
Click to expand...
Click to collapse
I tried to flash via twrp. It said that the install was succesful, but when i tried to go to recovery i got black screen
Why would you want cwm? TWRP is way better. Oh and your recovery is gone. You can be lucky that you didn't brick your phone. Next time, use TWRP instead and ONLY if you have the ability to restore everything with a PC. ONLY make such hard modifications to your phone if you have a PC nearby
Confirm that you're fully rooted using something like Root Checker
GaT7 said:
Confirm that you're fully rooted using something like Root Checker
Click to expand...
Click to collapse
Im sure im fully rooted
Ok, I suspect something may be wrong with your root or TWRP or ROM, which may be the reason for the odd problems.
So do check & confirm root anyway, & also tell us the versions of your TWRP & ROM (latter in Settings > About phone > Build number).
GaT7 said:
Ok, I suspect something may be wrong with your root or TWRP or ROM, which may be the reason for the odd problems.
So do check & confirm root anyway, & also tell us the versions of your TWRP & ROM (latter in Settings > About phone > Build number).
Click to expand...
Click to collapse
Im on sakoban's rom. B564
hello,
so i was installing cm13 while installing i wiped entire partition(data,including system)
now i can only boot into recovery , i installed cm13, cm-12.1-YOG4PAS9IG-ham-signed-d4fc2c5394 , after installing if i reboot it will again go to reovery only wont boot into phone..
please help
thank you
ancilary said:
i installed cm13, cm-12.1-YOG4PAS9IG-ham-signed-d4fc2c5394 , after installing ..
Click to expand...
Click to collapse
That's doesn't make sense, can you explain what it means? Which recovery, which rom was installed and was working? You wipes system and data, ok. What did you do then?
strongst said:
That's doesn't make sense, can you explain what it means? Which recovery, which rom was installed and was working? You wipes system and data, ok. What did you do then?
Click to expand...
Click to collapse
hi , thanks for reply
i was using nought rom 7.0 & TEAMWIN recovery
i performed wipe ( data , cache , system , internal storage)
then installed cm13
it booted only to recovery , after that i tried flashing different rom , no use everytime it goes only to recovery..
What's with your other request? http://forum.xda-developers.com/zuk-z1/help/how-to-make-device-stock-t3515921
You need cm13 or stock rom? It's annoying to open several threads..
strongst said:
What's with your other request? http://forum.xda-developers.com/zuk-z1/help/how-to-make-device-stock-t3515921
You need cm13 or stock rom? It's annoying to open several threads..
Click to expand...
Click to collapse
that was different but i tried this and now im stuck here
ancilary said:
that was different but i tried this and now im stuck here
Click to expand...
Click to collapse
And what you need is a running cm13 now?
strongst said:
And what you need is a running cm13 now?
Click to expand...
Click to collapse
ya running cm or any other rom is fine..
ancilary said:
ya running cm or any other rom is fine..
Click to expand...
Click to collapse
seems you don't know what you need cm isn't the same as cos, the difference is huge.
For cos12.1 stock rom you can get it here http://forum.xda-developers.com/zuk-z1/help/how-to-make-device-stock-t3515921/post70007487
Flash it with all in one tool, it's the easiest way.
Cm13 you can flash it though twrp.
strongst said:
seems you don't know what you need cm isn't the same as cos, the difference is huge.
For cos12.1 stock rom you can get it here http://forum.xda-developers.com/zuk-z1/help/how-to-make-device-stock-t3515921/post70007487
Flash it with all in one tool, it's the easiest way.
Cm13 you can flash it though twrp.
Click to expand...
Click to collapse
i flashed cm-12.1-YOG4PAS3AJ-ham-signed.zip with twrp still i get booted to recovery only
ancilary said:
i flashed cm-12.1-YOG4PAS3AJ-ham-signed.zip with twrp still i get booted to recovery only
Click to expand...
Click to collapse
You didn't understand or read my post... You need to flash stock firmware with fastboot. I didn't wrote flash it with twrp.
Use the all in one tool. It's called so, because you can do all with it. Like downloading stock rom and flash it :good:
strongst said:
You didn't understand or read my post... You need to flash stock firmware with fastboot. I didn't wrote flash it with twrp.
Use the all in one tool. It's called so, because you can do all with it. Like downloading stock rom and flash it :good:
Click to expand...
Click to collapse
i tried flashing stock recovery using All in one tool but now its not booting to recovery only
ancilary said:
i tried flashing stock recovery using All in one tool but now its not booting to recovery only
Click to expand...
Click to collapse
Sorry mate, why you do that? It said to flash stock rom with all in one tool, not stock recovery
strongst said:
Sorry mate, why you do that? It said to flash stock rom with all in one tool, not stock recovery
Click to expand...
Click to collapse
i read it as recovery my bad...
now i cannot boot into recovery/fastboot.
powers on rarely too just shows zuk logo and goes off
ancilary said:
i read it as recovery my bad...
now i cannot boot into recovery/fastboot.
powers on rarely too just shows zuk logo and goes off
Click to expand...
Click to collapse
Use all in one tool to boot into bootloader. Read carefully or your next step is qfil method
Here's a good guide in case you're don't get it through aoi tool: http://forum.xda-developers.com/zuk-z1/general/qpst-method-how-to-unbrick-to-stock-t3506833
But better to check again if you can flash stock cos rom with tool
strongst said:
Use all in one tool to boot into bootloader. Read carefully or your next step is qfil method
Here's a good guide in case you're don't get it through aoi tool: http://forum.xda-developers.com/zuk-z1/general/qpst-method-how-to-unbrick-to-stock-t3506833
But better to check again if you can flash stock cos rom with tool
Click to expand...
Click to collapse
Nothing is happening in phone , no respone for any button press . its wont turn on also now
ancilary said:
Nothing is happening in phone , no respone for any button press . its wont turn on also now
Click to expand...
Click to collapse
Can you charge it?