Database Users

[Q] How to install ClockworkMod Recovery

I'm currently running Prime! v1.3r2 and want to flash up to Prime! V1.4 but I am having some issues/ questions about CWM. The way I remembered, you just powered the device off, then held down vol down and power and it should boot into CWM. When I do this, it boots to a message that says "Press <VOL_UP> to execute or <VOL_DOWN> to cancel wiping data" with a glowing wipe data box at the center of the screen. I'm paranoid to do this and always press the vol down key. I know that I had to use CWM when rooting and flashing to Prime! v1.3r2, but it was super late at night and I was super tired and kind of zombied my way through it. Could someone please shed some light on what I am doing wrong?
Also, when using Rom Manager, when you go into Flash ClockworkMod Recovery, there are alot of devices listed, but no Asus Transformer so I apparently can't load it that way either. Do we use one from another device or are we currently not able to use Rom Manager?
Thanks to any who can help educate me!

Basicly you have to power off ur Transformer, hold down "Power" and "Vol-Down" at the same time and continue holding until some white letters appear on the left upper corner of your TF-display. From now on you have 5 seconds to release the two pressed buttons and press "Vol-Up".
If you want to start over again, u can follow this guide:
Rooting your TF101

Bavarianguy said:
Basicly you have to power off ur Transformer, hold down "Power" and "Vol-Down" at the same time and continue holding until some white letters appear on the left upper corner of your TF-display. From now on you have 5 seconds to release the two pressed buttons and press "Vol-Up".
If you want to start over again, u can follow this guide:
Rooting your TF101
Click to expand...
Click to collapse
Thank you so much! That worked great. Do you also know the answer to the second part of my question? Lastly, is it necessary to update ClokworkMod Recovery? Currently I have v3.0.2.8 on my TF. Thank you again

bds369 said:
Also, when using Rom Manager, when you go into Flash ClockworkMod Recovery, there are alot of devices listed, but no Asus Transformer so I apparently can't load it that way either. Do we use one from another device or are we currently not able to use Rom Manager?
Thanks to any who can help educate me!
Click to expand...
Click to collapse
ROM manager is not compatible with the TF yet.
ON Prime v1.4 you can flash the optional Power button recovery ad on

baseballfanz said:
ROM manager is not compatible with the TF yet.
ON Prime v1.4 you can flash the optional Power button recovery ad on
Click to expand...
Click to collapse
Thank you very much for the information! Hopefully ROM Manager will be updated for TF soon. Do you have a link for the the optional power button recover ad on?

In a bit of a bind...
So I finally rooted my Transformer, using the windows method of doing that (using APX), and everything went well. However, it seems I now can't get into recovery mode. I use the Vol Down + power, followed by Vol Up, get the message that it is booting the recovery, but it just sits there spinning.
(Exact message is "Booting recovery kernel image)
I am thinking that said kernel image can't be located.
Sadly, I am now not able to boo the tablet in APX mode to try and fix it.
does anybody have any suggestion? I would like to install clockworkmod recovery, but at this point I am not too sure what to do.
Any help greatly appreciated!

Stuck on "Booting recovery kernel image"
Were you ever able to resolve this issue? I have exactly the same problem. I've tried flashing alternate recovery.img files, but still cannot get CWM to come up.
Thanks!
--Roger
azafred said:
So I finally rooted my Transformer, using the windows method of doing that (using APX), and everything went well. However, it seems I now can't get into recovery mode. I use the Vol Down + power, followed by Vol Up, get the message that it is booting the recovery, but it just sits there spinning.
(Exact message is "Booting recovery kernel image)
I am thinking that said kernel image can't be located.
Sadly, I am now not able to boo the tablet in APX mode to try and fix it.
does anybody have any suggestion? I would like to install clockworkmod recovery, but at this point I am not too sure what to do.
Any help greatly appreciated!
Click to expand...
Click to collapse
SOLVED: I finally got past this by using nvflash to rewrite all the partitions and install a new ROM. I used the instructions at
http://tabletroms.com/forums/transf...ment/976-nvflash-unbricking-forever-root.html
which is written for Prime 1.4. This is possibly overkill, because it rewrites ALL the partitions and you lose all data, but since my problem appeared to be related to something other than just the boot loader and/or the system partition, I decided to take the hit. I followed those instructions as is, and got a Prime 1.4 system with CWM working perfectly. Then I just grabbed the latest Prime build and patches and applied them from CWM.
This is a huge relief, as I've been fighting with this for quite awhile. I see that many people have had a similar problem, and on other Tegra based tablets as well. While I haven't tried it, I presume that from this point, I could go back and install stock again, rooted or unrooted, with the BRK's nice tool from http://forum.xda-developers.com/showthread.php?t=1185104
I hope this helps out someone else with a similar problem.
--Roger

HELP - Did I brick my new Nexus 4

I think I bricked my brand new Nexus 4 I was trying to follow the rooting directions here:
http://forum.xda-developers.com/showthread.php?t=1993331
I was using the Clokcworkmod and I was unable to see the super su folder in the sd connection. and i rebooted it anyways. Now after reboot the phone doesnt start up It just hangs at the X symbol at the startup.
As suggested, I also tried to reboot recovery, which also hangs
I'm super new to this, anybody, please help

I need 10 posts before I can post in the developer thread...so posting away

getsky said:
I need 10 posts before I can post in the developer thread...so posting away
Click to expand...
Click to collapse
Just start again, sometimes it messes up, but you generally just start again with flashing the clockworkmod. Make sure the download wasnt corrupted by doanloading everything again though, although ignore the bit about adb rboot bootloader, you need to start the phone manually by use power + volume-down key combination to get into bootloader when its powered off and continue from point 5.

Thanks, I will give that a try

Ya dun goofd
Sent from my Nexus 4 using Tapatalk 2

getsky said:
Thanks, I will give that a try
Click to expand...
Click to collapse
Relac, its actually pretty hard to completely bust these things. Dont quote me on that though lol

Don't freak out. I'm sure you're fine.
Unlocking the bootloader on my N10 caused me to hang at the X. Wiping data fixed it for me. Try the following:
1. Reboot into Fast Boot
2. Select Recovery using volume rocker. Hit power to select. You'll get the android mascot with the red exclamation point.
4. Press Power and Volume Up at the same time.
5. Choose to wipe all data. Confirm the selection.
6. Reboot.

TheBishopOfSoho said:
Just start again, sometimes it messes up, but you generally just start again with flashing the clockworkmod. Make sure the download wasnt corrupted by doanloading everything again though, although ignore the bit about adb rboot bootloader, you need to start the phone manually by use power + volume-down key combination to get into bootloader when its powered off and continue from point 5.
Click to expand...
Click to collapse
So I didn't originally flash the recovery image, just booted into it. So I tried that again, but there is nowhere to find the SU_BusyBox_Pack.zip. I tried the sideload method, but ADB can't find my device any more. It shows nothing when I do adb devices.
what else can I try ?

Were you able to try wiping data through the stock recovery?
Sent from my Nexus 10 using XDA Premium HD app

getsky said:
So I didn't originally flash the recovery image, just booted into it. So I tried that again, but there is nowhere to find the SU_BusyBox_Pack.zip. I tried the sideload method, but ADB can't find my device any more. It shows nothing when I do adb devices.
what else can I try ?
Click to expand...
Click to collapse
I got stuck after just booting into recovery as well and immediately exit. Just use the volume key and change it until you see recovery, without going into it, I just fastboot flash recovery recovery.img from pc, then factory reset.

nyijedi said:
Don't freak out. I'm sure you're fine.
Unlocking the bootloader on my N10 caused me to hang at the X. Wiping data fixed it for me. Try the following:
1. Reboot into Fast Boot
2. Select Recovery using volume rocker. Hit power to select. You'll get the android mascot with the red exclamation point.
4. Press Power and Volume Up at the same time.
5. Choose to wipe all data. Confirm the selection.
6. Reboot.
Click to expand...
Click to collapse
Yes that seemed to work. Thank you Thank you Thank you
I almost had a heart attack

getsky said:
Yes that seemed to work. Thank you Thank you Thank you
I almost had a heart attack
Click to expand...
Click to collapse
Ha. No problem, man. I'm glad it worked. I've been there before.

nyijedi said:
Unlocking the bootloader on my N10 caused me to hang at the X. Wiping data fixed it for me. Try the following:
1. Reboot into Fast Boot
2. Select Recovery using volume rocker. Hit power to select. You'll get the android mascot with the red exclamation point.
4. Press Power and Volume Up at the same time.
5. Choose to wipe all data. Confirm the selection.
6. Reboot.
Click to expand...
Click to collapse
hi,
first timer here. i tried to get root using clockword mod following http://forum.xda-developers.com/showthread.php?t=2019273, but failed and get android mascot with the red exclamation point. following the above till #4 : Press Power and Volume Up at the same time, didn't bring me anywhere but turn off the device.
what should i do to get root ?
thank you,

[Q] Bricked my nexus 10! [Solved]

Please I really need some help! I think I've totally killed my nexus 10
I can get to fast boot but cannot flash anything. As soon as I try and say flash TWRP I get "FASTBOOT STATUS - DATA005fe000".
I've tried using the stock firmware and using flash-all.bat but get the same issue. The erase commands work, but then command to flash the boot loader gets the same issue.
I'm hoping I'm going to get flamed for not searching, 'cause that means I've missed something, but I've tried to search to no avail.
PLEASE HELP!!!!

kipperfish said:
Please I really need some help! I think I've totally killed my nexus 10
I can get to fast boot but cannot flash anything. As soon as I try and say flash TWRP I get "FASTBOOT STATUS - DATA005fe000".
I've tried using the stock firmware and using flash-all.bat but get the same issue. The erase commands work, but then command to flash the boot loader gets the same issue.
I'm hoping I'm going to get flamed for not searching, 'cause that means I've missed something, but I've tried to search to no avail.
PLEASE HELP!!!!
Click to expand...
Click to collapse
How did you got to that "state"? You should try using WugFresh toolkit.

lKBZl said:
How did you got to that "state"? You should try using WugFresh toolkit.
Click to expand...
Click to collapse
That's how I got into this mess! I tried to unlock and then root my tablet.
It rebooted and wouldn't pass the nexus X logo.
Now I can't flash anything.

In the Nexus Root Toolkit it says that if all goes wrong try Odin.
I've downloaded a version (I'm familiar with it from my Galaxy S), and got the drivers working... does anyone know where I can download the tar files?

kipperfish said:
That's how I got into this mess! I tried to unlock and then root my tablet.
It rebooted and wouldn't pass the nexus X logo.
Now I can't flash anything.
Click to expand...
Click to collapse
Did you get a chance to do the first twrp factory data reset? If not you may be able to boot into recovery mode and try a manual factory reset..
If your tablet is on, power it off.
Press and hold Volume Up + Volume Down + Power until the device powers on. You should see an image of an Android lying on its back.
Press Volume Down twice, until the screen says "Recovery mode."
Press Power to restart into "Recovery mode." You should see an image of an Android with a Red triangle after a few minutes.
While holding down Power, tap Volume Up
Use the volume keys to scroll to "wipe data/factory reset" and press Power to select it
Scroll down to "Yes - erase all user data" and press Power to select it
for some reason with wugfresh the first twrp factory reset failed on 2 out of 3 tests. I had do just do the manual factory reset above and all was well. Good luck! :good:

midgetzombiekiller said:
Did you get a chance to do the first twrp factory data reset? If not you may be able to boot into recovery mode and try a manual factory reset..
If your tablet is on, power it off.
Press and hold Volume Up + Volume Down + Power until the device powers on. You should see an image of an Android lying on its back.
Press Volume Down twice, until the screen says "Recovery mode."
Press Power to restart into "Recovery mode." You should see an image of an Android with a Red triangle after a few minutes.
While holding down Power, tap Volume Up
Use the volume keys to scroll to "wipe data/factory reset" and press Power to select it
Scroll down to "Yes - erase all user data" and press Power to select it
for some reason with wugfresh the first twrp factory reset failed on 2 out of 3 tests. I had do just do the manual factory reset above and all was well. Good luck! :good:
Click to expand...
Click to collapse
+1, exactly what I was thinking, you have to do a wipe data after unlocking in some cases.

Press and hold Volume Up + Volume Down + Power until the device powers on. You should see an image of an Android lying on its back.
Click to expand...
Click to collapse
Yes
Press Volume Down twice, until the screen says "Recovery mode.
Click to expand...
Click to collapse
Yes
Press Power to restart into "Recovery mode." You should see an image of an Android with a Red triangle after a few minutes.
Click to expand...
Click to collapse
I just get a black screen
While holding down Power, tap Volume Up
Use the volume keys to scroll to "wipe data/factory reset" and press Power to select it
Scroll down to "Yes - erase all user data" and press Power to select it
Click to expand...
Click to collapse
By using 4.2.0 (rather than 4.2.2) and trying the flash stock and unroot option I can now install CWM or TWRP as a boot loader.
I installed CWM and did a factory reset, then retried the above. This got the data error when installing system and then when finished got a file veririfcation error in the fastboot status. When I reboot I just get the Google logo and the unlock at the bottom.

kipperfish said:
Yes
Yes
I just get a black screen
By using 4.2.0 (rather than 4.2.2) and trying the flash stock and unroot option I can now install CWM or TWRP as a boot loader.
I installed CWM and did a factory reset, then retried the above. This got the data error when installing system and then when finished got a file veririfcation error in the fastboot status. When I reboot I just get the Google logo and the unlock at the bottom.
Click to expand...
Click to collapse
Wow i haven't had my n10 long enough to help you much more. Sounds like you might have some corrupt files from wugrfresh download/install? Maybe download from another mirror and try again? good luck !!!! Keep me posted!

Re: [Q] Bricked my nexus 10!
Not to be rude or anything but toolkits are the devil when it comes to Nexus devices. They are so easy to root and ROM that anyone can do it. Toolkits encourage ignorance to what and how things are getting done.
For starters go Google the fastboot files for the Nexus 10. Google Fastboot.exe and add it to your system folder on windows if you are using such.
Extract the downloaded "manta....." File and then extract the zip file contained.
From here make sure you are in your boot loader and type "fastboot devices" ensure your serial shows.
Then one by one go into the extracted folder and erase then flash each partition EXCEPT the bootloader. Don't mess with that at this point. After flashing the recovery, system, boot and data files reboot into the recovery and perform a factory reset. It should boot from this point.
On Manta, you MUST do a factory reset after flashing the data partition or unlocking the device. For some reason it fails to boot without performing that step.
Sent from my Nexus 10 using Tapatalk HD

altimax98 said:
Not to be rude or anything but toolkits are the devil when it comes to Nexus devices. They are so easy to root and ROM that anyone can do it. Toolkits encourage ignorance to what and how things are getting done.
For starters go Google the fastboot files for the Nexus 10. Google Fastboot.exe and add it to your system folder on windows if you are using such.
Extract the downloaded "manta....." File and then extract the zip file contained.
From here make sure you are in your boot loader and type "fastboot devices" ensure your serial shows.
Then one by one go into the extracted folder and erase then flash each partition EXCEPT the bootloader. Don't mess with that at this point. After flashing the recovery, system, boot and data files reboot into the recovery and perform a factory reset. It should boot from this point.
On Manta, you MUST do a factory reset after flashing the data partition or unlocking the device. For some reason it fails to boot without performing that step.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Yeah after my experience with toolkits I have leaned that the google sdk fastboot is the best method and you also learn the fastboot/adb commands and what's actually happening step by step.

midgetzombiekiller said:
Wow i haven't had my n10 long enough to help you much more. Sounds like you might have some corrupt files from wugrfresh download/install? Maybe download from another mirror and try again? good luck !!!! Keep me posted!
Click to expand...
Click to collapse
Ok, given all the feedback, especially with regards to corrupt items, I dug out an old laptop and was still getting the same problems, re-downloaded the 4.2.2 image and tried again.... and was more patient this time, and voila! back up and running!
Thanks to everyone who replied, I would not have persevered without your comments.
Lessons learned:
1) On Manta, you MUST do a factory reset after flashing the data partition or unlocking the device. For some reason it fails to boot without performing that step.
2) For me the downloads seem to have been unreliable, try, re-try, cry, weep, try again, punch the desk until your knuckles bleed, try some more and eventually you'll get there!
3) Be VERY patient. I was less patient than my normal impatient self when I saw how super lightning fast the N10 is.
Thanks again to everyone.

kipperfish said:
Ok, given all the feedback, especially with regards to corrupt items, I dug out an old laptop and was still getting the same problems, re-downloaded the 4.2.2 image and tried again.... and was more patient this time, and voila! back up and running!
Thanks to everyone who replied, I would not have persevered without your comments.
Lessons learned:
1) On Manta, you MUST do a factory reset after flashing the data partition or unlocking the device. For some reason it fails to boot without performing that step.
2) For me the downloads seem to have been unreliable, try, re-try, cry, weep, try again, punch the desk until your knuckles bleed, try some more and eventually you'll get there!
3) Be VERY patient. I was less patient than my normal impatient self when I saw how super lightning fast the N10 is.
Thanks again to everyone.
Click to expand...
Click to collapse
Glad to hear it worked out. I found out that wipe step the hard way.
Use the MD5 to verify your downloads if you have any doubts, i personally haven't had any failures

Sweet!
Sent from my Nexus 10 using xda premium

[Q] Device bootloops after messed up partition

I once tried to use geno's partition resize, and after a reboot, it cannot boot into system anymore. Stuck at the huawei logo.
Since I'm quite familiar with linux, I tried this solution: http://forum.xda-developers.com/showthread.php?t=1971266
However, my linux installation didn't show any drives when it's in pink screen mode, so I'm pretty much stuck here.
In Windows 8 it did show two HUAWEI Technologies device (no drivers though) in pink screen mode.
I can't access recovery mode either, holding power + vol up only does normal boot for some strange reason. Anyone can help me out here?

ansarips said:
I once tried to use geno's partition resize, and after a reboot, it cannot boot into system anymore. Stuck at the huawei logo.
Since I'm quite familiar with linux, I tried this solution: http://forum.xda-developers.com/showthread.php?t=1971266
However, my linux installation didn't show any drives when it's in pink screen mode, so I'm pretty much stuck here.
In Windows 8 it did show two HUAWEI Technologies device (no drivers though) in pink screen mode.
I can't access recovery mode either, holding power + vol up only does normal boot for some strange reason. Anyone can help me out here?
Click to expand...
Click to collapse
try put official GB dload file on sd card, then put sd card in phone press power up+power down+power...
maybe it'll help you.

I tried that too, and it still bootloops. Not much luck.

Go to recovery and wipe everything. Then, reboot recovery, and then try partitioning again.

I can't get into recovery by pressing power + vol up. It just does normal boot (which bootloops).
If there would be any other way to get into recovery (such as via ADB or update.app) would be highly appreciated.

ansarips said:
I can't get into recovery by pressing power + vol up. It just does normal boot (which bootloops).
If there would be any other way to get into recovery (such as via ADB or update.app) would be highly appreciated.
Click to expand...
Click to collapse
Yes, you can boot into recovery via adb:
Code:
adb reboot recovery
But, you cannot use that until your phone is booted up.
If that doesn't work, you can follow these instructions to hard reset your phone:
http://www.hard-reset.com/huawei-u8800-ideos-x5-hard-reset.html
Good Luck.

I can't get it to do the hard reset either. It just boots normally, aside from the bootloop.
I believe I need to fix the partition first before I try to reinstall stock. I hear that stock doesn't work with custom partitions. Which is why I'd prefer to at least get some access to the device via USB in order to fix it.
Ah well. It's a failing device anyway. Even before the brick the camera doesn't work anymore, regardless of which ROM I choose. Maybe it's time to move on for me.

ansarips said:
I can't get it to do the hard reset either. It just boots normally, aside from the bootloop.
I believe I need to fix the partition first before I try to reinstall stock. I hear that stock doesn't work with custom partitions. Which is why I'd prefer to at least get some access to the device via USB in order to fix it.
Ah well. It's a failing device anyway. Even before the brick the camera doesn't work anymore, regardless of which ROM I choose. Maybe it's time to move on for me.
Click to expand...
Click to collapse
I have found someone who has solved this problem.
Go to this link. In the first post, the OP has shared the solution with us.
Try it, and Good Luck!

rqmok said:
I have found someone who has solved this problem.
Go to this link. In the first post, the OP has shared the solution with us.
Try it, and Good Luck!
Click to expand...
Click to collapse
Well, I tried this too (in fact I stated it in the first post) but pink screen mode isn't showing any device (I typed in "dmesg" in the Linux Terminal, none is found).
I appreciate your help, though. If I can solve the detection problem, I should be able to recover my phone using this method. I'd be happy to share some logs if it helps.

I got your back buddy
ansarips said:
Well, I tried this too (in fact I stated it in the first post) but pink screen mode isn't showing any device (I typed in "dmesg" in the Linux Terminal, none is found).
I appreciate your help, though. If I can solve the detection problem, I should be able to recover my phone using this method. I'd be happy to share some logs if it helps.
Click to expand...
Click to collapse
Hey, this is my first post well here it goes
Step 1 :- Format the sd card and put dload folder in it ( you'll get it from the official rom zip file)
Step 2 :- press and hold vol+ & vol- and then power button, it'll start upgrading
Step 3 :- now here is the tricky part!!! i was stuck here too and gone half mad well, let it reboot it will format cache etc and then bootloops, now turn off the device and then turn on pressing vol+ and power button, or u can try by pressing home, vol+ and power button, u'll b in recovery mode i.e in official rom builtin i guess.
Step 4 :- once in recovery, select reset factory default and clear partition cache, and then reboot!!!! Voila u will b able to finally boot successfully...
Now listen very carefully, u got only one chance here, cause if u reboot ur device again then bootloops will start again so in the first go, root the device by superoneclick and then install recovery i guess u knw all that and then u will be able to return to stock rom by flashing... once u've installed CWM then u r good to go bootloop wont effect ya SORRY FOR MY BAD ENGLISH THOUGH

[Q] Please help guys

I have installed 4.2.2 on nexus 7. As I had skipped account login at welcome screen, i could not login the account. I altered the apk of login. After factory reset my device has hanged on setup on welcome screen. I tried installing custom rom through stock bootloader but the bootloader says installation failed. How do I solve thia problem guys???

subin.nexus7 said:
don't know the exact steps, but i got it out of the APX mode and into the bootloader.
1. Tablet plugged into computer.
2. Held Volume Down + Volume Up + Power (simultatenously) for three seconds
3. And then released all, and pressed Power again.
4. Tablet booted into bootloader.
I thought that unlocking the bootloader ALWAYS voided the warranty, but in anycase I flashed reflashed ALL stock and locked the bootloader. Will be sending it to ASUS now. Thanks again!
EDIT:
So I wanted to verify that it was a CPU problem, and I downloaded StabilityTest again and ran the CPU load test. It crashed within two minutes, and went into AXP mode again. To get it out of AXP mode, the correct instructions:
1. Plug in the usb into computer
2. Hold Volume Down + Volume Up + Power simultaneously for like 15 seconds
3. The bootloader should show up.
4. If it doesn't, unplug the usb cable, and plug it back in and then repeat the these procedures.
Click to expand...
Click to collapse
Very helpful! I don't have a problem but I've read about others stuck in APX mode. This should be pinned if it works for those stuck in APX. Maybe you should change the thread title to something about APX solution so it draws some attention.

kieso said:
Very helpful! I don't have a problem but I've read about others stuck in APX mode. This should be pinned if it works for those stuck in APX. Maybe you should change the thread title to something about APX solution so it draws some attention.
Click to expand...
Click to collapse
Well... being stuck in APX doesn't necessarily mean your hardbricked. (Corrupt or erased bootloader).
But being hardbricked DOES mean your device will default to APX mode.
To use a mathematical metaphor, one is a SUBSET of the other.
-------
bftb0 has posted an exhaustive list of Nexus 7 button press combos here...
http://forum.xda-developers.com/showthread.php?t=2133986
... which includes how to pro-actively get into APX mode... although until somebody figures how to nvFlash the N7, APX is sort of redundant.
Rgrds,
Ged.

Delete

subin.nexus7 said:
I have installed 4.2.2 on nexus 7. As I had skipped account login at welcome screen, i could not login the account. I altered the apk of login. After factory reset my device has hanged on setup on welcome screen. I tried installing custom rom through stock bootloader but the bootloader says installation failed. How do I solve thia problem guys???
Click to expand...
Click to collapse
I'm sort of confused about the relationship between your edited post and what (apparently ?) kieso quoted, but I'll throw out a few suggestions:
1) AFAIK, there is no way to flash a dev ROM using fastboot (only the boot image of a dev ROM can be flashed this way). You said "bootloader", not "custom recovery" ... so that implies using fastboot. If that is not the case, then your use of terminology is not correct. (It's a computer - reporting details correctly is incredibly important).
2) If you bypass the WiFi login, an account can be added at any time later using the settings menu or simply by launching the Google Play (market) app - there is no need to "alter the apk of login", whatever that means.
3) I would recommend at this point that you start completely over by flashing a factory ROM using fastboot - see the sticky thread about returning to stock using fastboot. If you already have the 4.18 bootloader installed, I recommend you avoid like the plague any operation involving flashing the bootloader.
4) It should be obvious from the trouble that you got yourself into that you should learn what nandroid backups are and that you START USING THEM. The first thing you do after rooting is "make a backup", not "flash a ROM"
good luck

Thanq so much.But still some clarification needed
Now What do I do? My nexus 7 can't pass through at welcome screen saying saying unfortunately setup wizard has stopped. and in recovery{i have no custom recovery, I use bootloader 4.18} i cant flash any rom. I just want to start device any how.. any way.. Is there any way??

subin.nexus7 said:
Now What do I do? My nexus 7 can't pass through at welcome screen saying saying unfortunately setup wizard has stopped. and in recovery{i have no custom recovery, I use bootloader 4.18} i cant flash any rom. I just want to start device any how.. any way.. Is there any way??
Click to expand...
Click to collapse
I guess I am having trouble understanding the sum total of information you have provided - I guess you have omitted some information or mis-stated something. No custom recovery sort of implies a full stock device, but yet you previously mentioned modifying/changing an .apk in /system... normally that would be possible only with a rooted ROM or a custom recovery to do that.
If your tablet is 100% stock, a factory reset of the tablet should allow you to boot once again - at the cost of deleting everything you put on the device, including all files you put on the (pseudo-) SD card.
If that is the case:
- press and hold power+vol-down until the bootloader screen shows up
- use vol-up/vol-down to select "start recovery" and press the power button
- an android lying on it's back should show up; this is the stock recovery splash screen, so
- press power+vol-up simultaneously for about one second - the stock recovery menu should show up
- select factory reset (with vol-up/vol-down) and press the power button.
good luck

bftb0 said:
I guess I am having trouble understanding the sum total of information you have provided - I guess you have omitted some information or mis-stated something. No custom recovery sort of implies a full stock device, but yet you previously mentioned modifying/changing an .apk in /system... normally that would be possible only with a rooted ROM or a custom recovery to do that.
If your tablet is 100% stock, a factory reset of the tablet should allow you to boot once again - at the cost of deleting everything you put on the device, including all files you put on the (pseudo-) SD card.
If that is the case:
- press and hold power+vol-down until the bootloader screen shows up
- use vol-up/vol-down to select "start recovery" and press the power button
- an android lying on it's back should show up; this is the stock recovery splash screen, so
- press power+vol-up simultaneously for about one second - the stock recovery menu should show up
- select factory reset (with vol-up/vol-down) and press the power button.
good luck
Click to expand...
Click to collapse
when you say at the cost of deleting everything, does this include deleting everything in the bootloader because thats what I did when I used the command "fastboot erase bootloader"