Database Info

-SOLVED- [Q] Trying to root, but can't boot into CWM...can anyone help?

I was using this guide http://forum.xda-developers.com/showthread.php?t=1078019 to unlock, install CWM, and then root. Unlocking was fine, installing that version of CWM seemed okay, but when I enter command "fastboot reboot", then hold down the volume - button after 3 seconds of the Moto logo showing, then pressing the volume + key, I get only 1 option....-->Android Recovery. I press the Volume + key, get "Entering Android Recovery Mode", and below that "Reading ODM Fuse 1", then the screen switches to an android with a yellow hazard sign in his tummy.
From that screen, if I press Volume + and power, I see:
Android system recovery <3e>
Use volume keys to highlight; power button to select.
reboot system now
apply update from USB drive
wipe data/factory reset
wipe cache partition
I don't get a choice to apply something from the microSD card I have installed with the WiFi_RootTool_3.1.zip I put on the card.
Has anyone had this happen? I can't ask in the development forum. I also just got the Xoom back from a repair, and it was wiped to stock, then I did the 3.1 update when I got it back this morning. Is the fuse thing something they may have done to block rooting?

Have you tried reformat your sd card?

becu4xda said:
Have you tried reformat your sd card?
Click to expand...
Click to collapse
I'll try that. But would that stop it from going into recovery?

becu4xda said:
Have you tried reformat your sd card?
Click to expand...
Click to collapse
I reformatted my sd card, but I still can't get CWM to work and boot into recovery. Same message-
-->Android Recovery
Entering Android Recovery Mode
Reading ODM fuse: 1
And that's it....no options to load the root zip from an SD card or anything. Is there a way to push root without using the SD card? Or is that ODM fuse thing making it impossible?

becu4xda said:
Have you tried reformat your sd card?
Click to expand...
Click to collapse
Nothing at all to do with CWM.
OP: Try flashing the recovery again. To get into recovery, type adb reboot recovery, or use an app such as Quick Boot.
Edit: You can't use CWM to root, you need to do that first.

siscim23 said:
Nothing at all to do with CWM.
OP: Try flashing the recovery again. To get into recovery, type adb reboot recovery, or use an app such as Quick Boot.
Edit: You can't use CWM to root, you need to do that first.
Click to expand...
Click to collapse
I have to root first? I'm not sure how to do it....can't find any other methods of rooting 3.1....everything on Google just points me to the same method, using the SD card that won't work cuz I can't boot into recovery. Ugh.

Hey jump hour PM me.

Hey guys,
I called JumpHour and we tried to troubleshoot this over the phone. We aren't able to get into the recovery because of error "reading odm fuse: 1". The OP is using Windows 7 64 BIT and has the SDK installed properly. He updated the sources and installed them so those are up to date. We also verified that USB debugging was enabled and that the correct files were in the tools section in the SDK folder.
We ran the commands:
adb reboot bootloader
fastboot-recovery ........ (we typed it in correctly accoriding the thread)
fastboot reboot
and we get that error message.
This was all initiated while the Xoom was powered on. JumpHour stated that he had to send his Xoom back to Moto because his Xoom got messed up during the re-locking process when he unrooted a one click root and re-locked.
We then went ahead and downloaded the recovery image again and replace the one in the tools folder. We ran the commands again and we were getting the same error.
Does anyone have any idea what is going on with this process? Are we missing something? Is something broken?

Get the official images. I am assuming you have a USA 3g or wifi model.
Follow the steps to return the device to stock. But do not issue the reclock bootloader command. There is no need to relock.
From there power up the device and turn on USB debugging.
Then adb reboot into recovery. That should bring you to the stock recovery.
If all goes well from here just do what ever else you where intending to do in the first place.
You most likely can just flash the stock recovery but I would just do a full flash back to official images minus relocking bootloader.
Sent from my Xoom using Tapatalk

Then let the ota update it to 3.1 and so on.
Sent from my Xoom using Tapatalk

What's the status JumpHour? Did you get it to work. I told you it may have been due to the images. Hopefully that fixes your issue. Take care dude.

gqstatus0685 said:
What's the status JumpHour? Did you get it to work. I told you it may have been due to the images. Hopefully that fixes your issue. Take care dude.
Click to expand...
Click to collapse
Hi, thanks for the response. I'm gonna try it now. I was up REALLY late last night, and just got up a little while ago. I'll definately respond after I try it out.

Finally, I did it!
Okay, I fixed it finally. Reloaded the stock images, and it's now rooted with SD support. Yay! Only took 2 days!
Thanks for all your help guys.

Can reflashing with original images fix recovery mode mount problem?
Does any window is flashing to the original images can restore access to the sdcard IF the recovery mode in the official recovery mode (not CWM) says that you cannot mount the sdcard?

stuck on htc boot screen..

I have been searching for hours..and still couldn't find an asnwer..
at first when my phone was still alright I did a factory reset and after that
it stuck on a boot screen with android in the middle...for a long time
then I use vol down + power method to reset it and clean everything (like system,cache and boot) all of them...
now I stuck on the green htc boot screen
I tried to install rom and kernel but still won't work I wonder whats the problem now
any idea???
thanks

nias9527 said:
I have been searching for hours..and still couldn't find an asnwer..
at first when my phone was still alright I did a factory reset and after that
it stuck on a boot screen with android in the middle...for a long time
then I use vol down + power method to reset it and clean everything (like system,cache and boot) all of them...
now I stuck on the green htc boot screen
I tried to install rom and kernel but still won't work I wonder whats the problem now
any idea???
thanks
Click to expand...
Click to collapse
You haven't searched that bad, if not you would have come across this:
http://forum.xda-developers.com/showthread.php?t=1396229
Anyway, are you rooted? if you are rooted and did a factory reset then you don't have a Rom in your phone and that is why you are stuck on the splash screen. You even wiped everything, so probably erased usb debugging drivers from the device.
Well, you have these choices: 1) If you still can access your custom recovery (CWM or 4EXT) then you need to put a rom in your sdcard and flash it. You will have your phone back. You can even restore a nand backup and have your system as it was at that time.
2) If you are S-OFF, but can not access a custom recovery, then flash it again and follow option 1)
3) Use a PD98IMG.zip file to flash a RUU in hboot and you will get back. In the link I provided above, you have several links to those files.
In all cases, you will need an sdcard reader or someway to get the files to your sdcard.
Hope it helps....

thanks!!!!
problem solved

I'm having the same problem stuck on the android boot screen I can access recovery and tried to flash a few different roms but with the same results.

Fortis4Eva said:
I'm having the same problem stuck on the android boot screen I can access recovery and tried to flash a few different roms but with the same results.
Click to expand...
Click to collapse
Did you read the link that glevitan posted a couple posts above yours? Did you try what it says? Which option? What happened?

[Q][A700] Need help, i guess i bricked my A700 :-(

Hello XDA community !
LAst week I bought my Acer A700, but after a few days a dead pixel appeared...
So I was on my way to send back my toy, when I saw that CMWR was available.
"Nice ! I can do a factory reset so my toy will be clean to be sent back !"
But the factory reset didn't work... It was stuck at "Formatting /data" for a while...
So I rebooted the A700, and now it's stuck at the ACER logo... I only have access to recovery...
Any ideas ?
Thanks a lot :good:

Since you have recovery try and do data wipe, then wipe cache then davlik cache, then reboot.
If you have recovery you can install a ROM by renaming it update.zip and using CWM.

Itchiee said:
Since you have recovery try and do data wipe, then wipe cache then davlik cache, then reboot.
If you have recovery you can install a ROM by renaming it update.zip and using CWM.
Click to expand...
Click to collapse
I already tried this, when I want to install a update.zip, it stucks at "installing update".
When I want to wipe a partition, it stucks at "formating /xxx" and nothing happens...
I wanted to flash stock bootloader with Nvflash, but I can't find APX drivers for ACER A700

Can you install the update.zip without the use of CWM (By pressing the powerbutton with the vol down)?
Also, where is your update.zip located?
Edit:
I guess it could do no harm if you'd hook up your device to the PC and enter the following commands:
adb reboot bootloader
fastboot erase cache
Click to expand...
Click to collapse

TomONeill said:
Can you install the update.zip without the use of CWM (By pressing the powerbutton with the vol down)?
Also, where is your update.zip located?
Edit:
I guess it could do no harm if you'd hook up your device to the PC and enter the following commands:
Click to expand...
Click to collapse
_ update.zip putted on a extrenal SD card doesn't work, it's skipped and CWM is launched.
_ the "adb reboot bootloader" puts the A700 in "APX" mode... and the "fastboot erase cache" is stuck at "waiting for device"...
Thanks for trying to help !!!

May this be a relevant solution??
http://androidforums.com/esteem-all...w-get-out-clockworkmod-recovery-bootloop.html
Edit:
I don't think the device checks for update.zip on the sdcard. Maybe there is a way to move the file to the internal. (adb mount sdcard adb push /sdcard/update.zip update.zip ?

Yeah,
The current CWM seems to corrupt the Data partition (amongst other things). Seems to be a going thing lately. Remember, these are new tabs, and new root & recovery methods, so there are going to be some bricked tabs before things get sorted out. This happens in "ALL" development, and everybody knows the risks involved.
I had the same issue. Couldn't reboot into fastboot, as it seems the OS has to be running?
This is why Skirlax_CZ built the bootloader for the 500/501, so you could boot it into fastboot mode, bypassing the OS. Unfortunately, the stock 70x OEM bootloader doesn't seem to allow this.
Best bet if you can't find the "exact" version rom the tab was shipped with, is to try renaming some full roms to update.zip, copy to sd, reboot (vol + and PWR, and see if it will install and boot. At the worst, it will install a stock bootloader and recovery.
Also, holding PWR, Vol - (I believe) and toggling the rotation lock should wipe User Data.
At the very worse, turn it into Acer Service, suck it up and pay the repair bill.
They will just install the correct service rom and give it back to you.
MD

Touns said:
Hello XDA community !
LAst week I bought my Acer A700, but after a few days a dead pixel appeared...
So I was on my way to send back my toy, when I saw that CMWR was available.
"Nice ! I can do a factory reset so my toy will be clean to be sent back !"
But the factory reset didn't work... It was stuck at "Formatting /data" for a while...
So I rebooted the A700, and now it's stuck at the ACER logo... I only have access to recovery...
Any ideas ?
Thanks a lot :good:
Click to expand...
Click to collapse
your situation is just same as mine,seeming bricked after using fatory rest or wiping from cwm,I think it's the problem of the damn cwm.as i know from now there are several devices got bricked,all because of the goddamn cwm.as we know factory rest is the same as recovery wiping,i use the under the official recovery,everything wen fine,but after wiping via cwm from the forum,it appeared the problem.
i tried a lot of method,just as u mentioned,to flash *.img
but i found a curious thing,after dumping series of *.img from a well-mailfuntioning device i can use fastboot to flash "userdata" which the loaction is mmcblk010 or /dev/block/platform/sdhci-tegra.3/by-name/UDA,but after flashing,i can't erase userdata block in fastboot.then i reflashing the data.img to userdata block,then in cwm,i can mount /data,but it's still not able to wipe or format it.then i've found a data.img and flashing the userdata and reboot.then i enter the system,and it forced me to do a factory reset,of course as before,it's not mailfunctioning because of the cwm or the block itself damaged..
but i can enter adb,and i found that i can see the /data and the filesystem in it.then i use mount to modify it,for i can delete or modify the files in /data,and it appears normally.i delete everything in /data.then i want to try to reboot to see if it's working,but after rebooting,the device stuck at acer logo,then i reboot into the cwm,it can't be mounted again.it seems that i can flash the userdata but i can't format or wipe or modify...
and i tried to reflash the bootloader from a well-mailfunctioning deivece,not working,either.
then i go for searching the situation in google,i found there are a lot of similar problems of the tegra device,and the solution is nvflash...
i don't know if there are a block saving the information of partitions just like the PIT file of my galaxy s2,seems we should wait for nvflash?or the method to flashing PIT partitions file?
i installed the nvflash driver by modifying the usb id,but i can't do anything from nvflash,it's not matching.

I had the same problem after I upgraded to JB with CWM recovery 6.0.14 and I tried to root it. But it stuck in acer logo. Then I went to recovery mode, but it couldn't mount sdcard or external card, too.
In my case, I solved it by these steps:
1. Try to go to fastboot mode by press vol (-) + power. After it vibrate, release power, and then play lock button. Then tablet will go to fastboot mode. http://forum.xda-developers.com/showthread.php?t=1861092
2. Download these boot and recovery images: https://www.box.com/s/3321wf8gg4at639nfn06
3. Try to flash these boot and recovery images to table:
fastboot flash boot boot.img​
fastboot flash recovery recovery.img​
And then, reboot tablet:
fastboot reboot​
WOW, my tablet works again.
:victory:

kwaiding said:
I had the same problem after I upgraded to JB with CWM recovery 6.0.14 and I tried to root it. But it stuck in acer logo. Then I went to recovery mode, but it couldn't mount sdcard or external card, too.
In my case, I solved it by these steps:
1. Try to go to fastboot mode by press vol (-) + power. After it vibrate, release power, and then play lock button. Then tablet will go to fastboot mode. http://forum.xda-developers.com/showthread.php?t=1861092
2. Download these boot and recovery images: https://www.box.com/s/3321wf8gg4at639nfn06
3. Try to flash these boot and recovery images to table:
fastboot flash boot boot.img​
fastboot flash recovery recovery.img​
And then, reboot tablet:
fastboot reboot​
WOW, my tablet works again.
:victory:
Click to expand...
Click to collapse
Unfortunately, although somewhat similar, this is not the same situation as the OP had.
The first CWM originally posted a few months ago, was posted by a user who used the totally wrong partition tables, and also, didn't own the tab so it was never tested (after the fact). Basically, it damaged the chipset which required a motherboard replacement. Not to mention a specifically nasty Data_Cap bug in the CWM kernel. No image flashing via fastboot (and probably NVFlash) would repair the damage. The result was several bricked tabs till the CWM was removed. (mine included)
Also note, that the current root procedure is by the same person. Although there is an alternative.
What you had, was simple data corruption on one of the Dev Blocks. This is why you were able to fastboot an image.
Corrupting a partition can happen at any time. Whether rooted, stock, or custom rom. So it's always nice to have ADB to pull your partition images. Just in case.
MD

[Q] Bricked Nexus 5

Hello
I followed this guide http://forum.xda-developers.com/show....php?t=2507905 to root my new Nexus 5 and flashed this rom http://forum.xda-developers.com/show....php?t=2528265 onto it, when I tried to boot it up it got stuck in the boot animation so I rebooted into recovery and wiped the data, cache partition and the dalvik cache and tried to boot it up and encountered the same problem so I went to reboot and it wont boot back up not even to the bootloader and when I plug it into my pc its unrecognized and wont even show charging animations
Did I brick my new phone?

Smragnol said:
Hello
I followed this guide http://forum.xda-developers.com/show....php?t=2507905 to root my new Nexus 5 and flashed this rom http://forum.xda-developers.com/show....php?t=2528265 onto it, when I tried to boot it up it got stuck in the boot animation so I rebooted into recovery and wiped the data, cache partition and the dalvik cache and tried to boot it up and encountered the same problem so I went to reboot and it wont boot back up not even to the bootloader and when I plug it into my pc its unrecognized and wont even show charging animations
Did I brick my new phone?
Click to expand...
Click to collapse
Press and hold volume up then connect usb cable, what the result?

bitdomo said:
Press and hold volume up then connect usb cable, what the result?
Click to expand...
Click to collapse
same as above, nothin.

Smragnol said:
same as above, nothin.
Click to expand...
Click to collapse
Then it is bricked , but I don't really understand how could fromating data, cache and dalvik cache destroy the bootloader . There must be something wrong those recoveries, because you are not the only one

Did you ever check the md5 of the rom you flashed? It could have been a corrupted download

does your bootloader work? hold the vol up/down and power on boot. if u can get to the bootloader u can save it with wugs nexus tool.

malibu_23 said:
does your bootloader work? hold the vol up/down and power on boot. if u can get to the bootloader u can save it with wugs nexus tool.
Click to expand...
Click to collapse
If you can get into bootloader you can save it without a tool kit.

Do this if u can't go into recovery
http://forum.xda-developers.com/showthread.php?t=2513937
But if u are able to go into recover, just flash any other rom, make sure you before flashing u do a factory data reset, and after finished wipe cache/dalvik always so u dont go into bootloops.

Through some miracle I was able to get to the bootloader (sat there and held the vol and power buttons for like 3 minutes while my pc dinged and donged as it disconnected and reconnected) but I'm unsure of what to do now. Should I keep trying to load a custom rom on it or just go back to stock? and either or how am I going to get the rom on the internal storage as its still not being recognized by my pc (but I do have fast boot access)

Smragnol said:
Through some miracle I was able to get to the bootloader (sat there and held the vol and power buttons for like 3 minutes while my pc dinged and donged as it disconnected and reconnected) but I'm unsure of what to do now. Should I keep trying to load a custom rom on it or just go back to stock? and either or how am I going to get the rom on the internal storage as its still not being recognized by my pc (but I do have fast boot access)
Click to expand...
Click to collapse
I'd flash the factor image with fastboot and start all over

Do this if u can't go into recovery
http://forum.xda-developers.com/showthread.php?t=2513937
But if u are able to go into recover, just flash any other rom, make sure you before flashing u do a factory data reset, and after finished wipe cache/dalvik always so u dont go into bootloops.

Stay away from tool kits. You got enough problems on your hand

Alright so I got the stock os flashed on there and booted up and everything is looking goood, thanks guys for all your help I'll be sure to come back if I have any more problems

Smragnol said:
Alright so I got the stock os flashed on there and booted up and everything is looking goood, thanks guys for all your help I'll be sure to come back if I have any more problems
Click to expand...
Click to collapse
Glad to hear you're back up and running. Google md5 checksum and make sure the roms you download are good. I think that was your problem

Done this to my Nexus 7.. something went wrong when flashing the Rom and ended up somehow cocking up my drivers aswell.. Weird one.
Glad to hear your back up and running buddy.

stuck in loop, possibly a different kind of loop

I was trying to fix my girlfriends nexus 5 that was doing the restart loop after an update. Everything seemed to go fine. Unlocked the bootloader, etc. Flashed the newest rom (6.0.1 (MMB29S) ce1d670f61061c3902f3997510ea55d7 6bfcdfa4f4840898e5d76fa044f5e6a0f71343bf) and then something obviously went wrong (not quite sure, dont think i touched anything) and it's now stuck in a different kind of loop that only loops while it's plugged in. Ive uploaded a video to youtube, but since im a new user i cant actually link it properly yet. Hopefully this wont annoy any mods, I promise it's not spam. youtube . be / yNSoiTPnGZw
Is there any way to get it to stay on for more than a couple seconds to retry the flashing?
Any help is appreciated.

atomkrieg said:
I was trying to fix my girlfriends nexus 5 that was doing the restart loop after an update. Everything seemed to go fine. Unlocked the bootloader, etc. Flashed the newest rom (6.0.1 (MMB29S) ce1d670f61061c3902f3997510ea55d7 6bfcdfa4f4840898e5d76fa044f5e6a0f71343bf) and then something obviously went wrong (not quite sure, dont think i touched anything) and it's now stuck in a different kind of loop that only loops while it's plugged in. Ive uploaded a video to youtube, but since im a new user i cant actually link it properly yet. Hopefully this wont annoy any mods, I promise it's not spam. youtube . be / yNSoiTPnGZw
Is there any way to get it to stay on for more than a couple seconds to retry the flashing?
Any help is appreciated.
Click to expand...
Click to collapse
What was your flashing procedure, did u is a toolkit or do it manually, can u get it into bootloader or recovery? What files did u is for update and where did u get them?
Sent from my XT1526 using Tapatalk

soupysoup said:
What was your flashing procedure, did u is a toolkit or do it manually, can u get it into bootloader or recovery? What files did u is for update and where did u get them?
Sent from my XT1526 using Tapatalk
Click to expand...
Click to collapse
First i followed the guide here on xda to unlock the bootloader(guide-nexus-5-how-to-unlock-bootloader-t2507905), installed twrp, which went fine. Then i realized that i couldnt (or didnt realize how to via command line) to copy the stock rom and install it via twrp, so then i followed this guide here on xda (tutorial-how-to-flash-factory-image-t2513701) with the factory img (6.01 hammerhead), got to this point in the guide: ★After everything finished, select "Recovery" using the volume buttons. then it stalled out,turned off and now just cycles on and offf through the google logo with the lock picture or if i hold down the volume button it will go into the bootloader briefly then restart, rinse repeat.

atomkrieg said:
First i followed the guide here on xda to unlock the bootloader(guide-nexus-5-how-to-unlock-bootloader-t2507905), installed twrp, which went fine. Then i realized that i couldnt (or didnt realize how to via command line) to copy the stock rom and install it via twrp, so then i followed this guide here on xda (tutorial-how-to-flash-factory-image-t2513701) with the factory img (6.01 hammerhead), got to this point in the guide: ★After everything finished, select "Recovery" using the volume buttons. then it stalled out,turned off and now just cycles on and offf through the google logo with the lock picture or if i hold down the volume button it will go into the bootloader briefly then restart, rinse repeat.
Click to expand...
Click to collapse
Have u tried messing with the power button, there are a lot of issues on the nexus 5 with the power button causing loops, simply from getting stuck, try playing with the power button a little and see of that helps, it might just need to be replaced
Wait, did u flash the factory img with twrp, or did u flash it using fastboot?
Sent from my XT1526 using Tapatalk

soupysoup said:
Have u tried messing with the power button, there are a lot of issues on the nexus 5 with the power button causing loops, simply from getting stuck, try playing with the power button a little and see of that helps, it might just need to be replaced
Wait, did u flash the factory img with twrp, or did u flash it using fastboot?
Sent from my XT1526 using Tapatalk
Click to expand...
Click to collapse
in the end fastboot, since i coulndt see how i could copy the img over to install via twrp
im pretty sure the button is fine, since it was cycling from the ota update install, then was working fine unlocking the bootloader, but after the flash, it crapped the bed.

Different problem
I had a problem where the google logo keeps on booting up with a slight vibration.This started to happen when my was dropped.I initially thought that was a software issue and thought of installing new ROM's but eventually my device was not detected :crying:
So i took it to repair shop near my house and they said it would cost 2500
I did some google research and found the reason was due to the power button being stucked during the fall.I got that repaired and my device is good to go

siddhu007 said:
I had a problem where the google logo keeps on booting up with a slight vibration.This started to happen when my was dropped.I initially thought that was a software issue and thought of installing new ROM's but eventually my device was not detected :crying:
So i took it to repair shop near my house and they said it would cost 2500
I did some google research and found the reason was due to the power button being stucked during the fall.I got that repaired and my device is good to go
Click to expand...
Click to collapse
ok, took it into a shop, got the power button fixed. It must have been on the way out because literally one minute it worked and the second it didnt. now i think ive got it narrowed down. it's saying it's unable to mount /persist. ive tried the various fixes:
e2fsck/dev/block/platform/msm_sdcc.1/by-name/persist
and
make_ext4fs/dev/block/platform/msm_sdcc.1/by-name/persist
but all i get is a not found error. not sure what to do from here on.

success!! i ended up stumbling on a bit how to restore the persist partition i didnt try. got a custom rom installs and everything works. thanks to everyone who tried to help!!

stuck in bootloop while flashing cataclysm rom
i tried to flash cataclysm rom in my n5..i unlock bootloader, flash custom recovery using TWRP and flash cataclysm rom following the instructions in this thread http://forum.xda-developers.com/goo...s-5-how-to-unlock-bootloader-t2507905...after that it was stuck in bootloop...i tried to open recovery but it wont open anymore it will only go back to loop....how can open the recovery? is it safe to flash CWM recovery?..tnx in advance..

When it was stuck in the loop, I had to hold vol up and down with the power button (wait a few secs until it was completely off) then reboot holding down + power till it opened the bootloader. if that doesnt work, try reflashing the bootloader via fastboot. I only found out i couldnt mount the persist partition by looking at the terminal window in twrp after trying to install a rom which kept it in the boot loop. I then used the cmd: make_ext4fs /dev/block/platform/msm_sdcc.1/by-name/persist to rebuild it.

jpau11 said:
i tried to flash cataclysm rom in my n5..i unlock bootloader, flash custom recovery using TWRP and flash cataclysm rom following the instructions in this thread http://forum.xda-developers.com/goo...s-5-how-to-unlock-bootloader-t2507905...after that it was stuck in bootloop...i tried to open recovery but it wont open anymore it will only go back to loop....how can open the recovery? is it safe to flash CWM recovery?..tnx in advance..
Click to expand...
Click to collapse
After flashing TWRP, use the volume and power button to select recovery. Once in TWRP, wipe cache, data, reboot.

audit13 said:
After flashing TWRP, use the volume and power button to select recovery. Once in TWRP, wipe cache, data, reboot.
Click to expand...
Click to collapse
problems solved!!i flashed TWRP again and it it already to the recovery so i reflashed the cataclysm rom and it worked...my n5 is now working..tnx guys!

jpau11 said:
problems solved!!i flashed TWRP again and it it already to the recovery so i reflashed the cataclysm rom and it worked...my n5 is now working..tnx guys!
Click to expand...
Click to collapse
Great to hear it. Congratulations:good: