So I downloaded new kernels and CM10 for my newly rooted N4. I did a backup before flashing the kernel and didn't pay attention to the error message saying cache was not found or whatever. But the kernel flashed fine and it booted up, nothing out of the whack. When I went back to flash CM10 it said the MD5 sum didn't match so the flashing processes didn't finish. Since my backup was ****ed up and the MD5 didn't match I couldn't restore the system either. Device will boot and will go into fastboot and recovery. Currently using CWM. If I turn on the device normally it will stay on the GOOGLE screen and it will not go into the boot screen. What do?
Usually when it hangs on the google screen it is kernel related.
You can try booting into recovery, clearing cache and flashing the kernel.
If that doesn't work, re-flash the ROM with signature verification turned off. (in the update from .zip menu)
OR You can push a new rom with ADB to your sd card. adb push /sdcard/
El Daddy said:
Usually when it hangs on the google screen it is kernel related.
You can try booting into recovery, clearing cache and flashing the kernel.
If that doesn't work, re-flash the ROM with signature verification turned off. (in the update from .zip menu)
OR You can push a new rom with ADB to your sd card. adb push /sdcard/
Click to expand...
Click to collapse
The CM10 zip itself is bad. How can I get another one on the phone? Or can I flash the CM zip without the file being on the phone? Thanks
Also, the error message popped up when flashing the CM zip was set_perm: some changes failed
E: Error in /sdcard/0/cmblahblahc zip
(status 7)
installation aborted
Should I turn off the signature verification anyway?
I would just push a new cm ROM to your phone. Command is.
adb push nameofzip.zip /sdcard/
Then flash it.
Sent from my Nexus 4 using xda premium
El Daddy said:
I would just push a new cm ROM to your phone. Command is.
adb push nameofzip.zip /sdcard/
Then flash it.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
3 years of rooting and flashing stuff on 3 of my previous phones, there wasn't a time when I had to do this, or had to ask for help. Damn it.
Could you be a little more detailed in how do I go about doing so? As you can see my post count I am a bit of a noob Despite those 3 years. I just don't wanna mess up again, you know?
Thanks for everything dude
What screen should my phone be on? Just type that into the command prompt and it should work?
_thunderchild_ said:
What screen should my phone be on? Just type that into the command prompt and it should work?
Click to expand...
Click to collapse
Sorry I was out and about the past few hours.
You want to be in recovery. Custom recoveries allow you to use adb.
Rename the ROM something easy like CMrom.zip
Then put the CMrom.zip in the same location as adb on your computer.
Open the command window from that directory. (hold shift and right click; then choose open command window here)
Type the command: adb push CMrom.zip /sdcard/
It will push the file to the root of /sdcard/
Then you can flash it.
If that fails, use toolkit to download factory image and flash it through fastboot.
Oh man you guys saved my life. I cannot thank you guys enough. You won't believe how happy I was when I saw the bootscreen. Glad that was dealt with. Again thanks guys
Hey everyone I don't know if this is the right place to be posting this but I had the same problem as OP a few hours ago. I flashed LiquidROM and it got stuck on a boot loop. Needless to say, I panicked and used the adb push method since I decided to delete my AOKP ROM from my folder. Anyway, while panicking what I did was is before flashing, I backed up my entire SD card onto my laptop as ADB backup wasn't working and I pushed the entire folder using "adb push sdcard /sdcard/. Next thing I'm in recovery (CWM) and when I go through the flash from sdcard option, usually there were 3 options name 0/ and 2 others, however since I pushed the sdcard folder to /sdcard/ I get a 0/ at the top of the list which is where I would usually go but then underneath that I get all the folders I pushed! Is there any way to sort this out? I could attach pictures at some point for those of you who find it hard to picture what I'm describing Thanks in advance for any help!
Edit: just to add a couple of other things, my NANdroid had a checksum error so I cannot revert to stock without having to manually flash it which I cannot do at the moment due to a lack of WiFi, is there any way to sort this out? And the other thing was that for some reason sdcard cannot be unmounted at all in cwm, is it meant to be like that or am I missing something? Afaik its supposed to toggle.
Thanks again!
Sent from my Nexus 4 using xda app-developers app
Related
i stupidly changed from CWM recovery to TWRP and forgot to make a backup.
I went to install the Revolt rom so copied it to the memory and it installs fine but when i go to reboot it just sits on the "Google" boot screen with the unlocked padlock at the bottom and never gets anywhere.
Any ideas or advice on what i can do?
Does adb work?
Wipe cache?
If you would have read through the thread, you would have seen that the ROM doesn't boot past the Google logo. The ROM doesn't work.
Sent from my Nexus 4 using xda premium
But how can I get another ROM.zip onto the device since I can't get onto it (I can access TWRP) but how can I get the zip onto it?
nexus toolkit doesn't pick it up so no ADB. My other nexus gets picked up fine
Sent from my Nexus 4 using xda premium
Roshi69 said:
But how can I get another ROM.zip onto the device since I can't get onto it (I can access TWRP) but how can I get the zip onto it?
nexus toolkit doesn't pick it up so no ADB. My other nexus gets picked up fine
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Try configuring the drivers from here. Can you mount USB Storage? Does your computer recognize fastboot?
It picks up my other nexus that is working fine but with being stuck in a boot loop i dunno what to do. with my s3 i would have just put a new rom on the external SD
just got it into download mode :s and 2 new random devices have appeared. check the links below.
all i want to be able to do it put a new .zip on the device so i can get it going.
https://www.dropbox.com/s/jux2lvkn63fjq2q/IMG_20130118_181401.jpg
https://www.dropbox.com/s/nk7rozieurd7ofg/IMG_20130118_181407.jpg
Roshi69 said:
It picks up my other nexus that is working fine but with being stuck in a boot loop i dunno what to do. with my s3 i would have just put a new rom on the external SD
just got it into download mode :s and 2 new random devices have appeared. check the links below.
all i want to be able to do it put a new .zip on the device so i can get it going.
https://www.dropbox.com/s/jux2lvkn63fjq2q/IMG_20130118_181401.jpg
https://www.dropbox.com/s/nk7rozieurd7ofg/IMG_20130118_181407.jpg
Click to expand...
Click to collapse
Can you get into fastboot?
possibly. what commands do i have to try? i know fastboot did work for my last device so its configured and working ok
Roshi69 said:
i stupidly changed from CWM recovery to TWRP and forgot to make a backup.
I went to install the Revolt rom so copied it to the memory and it installs fine but when i go to reboot it just sits on the "Google" boot screen with the unlocked padlock at the bottom and never gets anywhere.
Any ideas or advice on what i can do?
Click to expand...
Click to collapse
This happened to me 2 times yesterday. I was flashing new kernel and roms and then I keep getting the Google logo for every new rom I tried. I fixed this problem by doing these steps..
I'm using TWRP so ..
-Wipe
-Cache / Dalvik cache / factory reset / system / format data / and internal storage (Make sure u wipe internal storage and format data! This will stop the Google logo loop. NOTE: U will lost everything if you do this step)
-Then I reboot into TWRP after the wipe
-I download nexus 4 toolkit v1.3 Toolkit dl link
-mount /system/ in TWRP
-Put the below stock rooted rom into put_files_to_push_here (it's inside installed path of the nexus 4 toolkit)
-Push This stock rooted rom using #13 option in nexus 4 toolkit
-It will ask if u using a custom rom or insecure image type yes
-It will ask u where to push ur file to.. just type /system/
-wait 2-3 mins to push. If everything goes well it should say "Finished xxx secs"
-Install the Stock rooted rom using TWRP
-reboot
Roshi69 said:
possibly. what commands do i have to try? i know fastboot did work for my last device so its configured and working ok
Click to expand...
Click to collapse
I think I was wrong. You can't push/flash a ROM through fastboot. Are you absolutely sure that you can't mount your SD card to your PC in TWRP recovery? I can't mount my SD using CWM but I can using TWRP.
enyceckk said:
This happened to me 2 times yesterday. I was flashing new kernel and roms and then I keep getting the Google logo for every new rom I tried. I fixed this problem by doing these steps..
I'm using TWRP so ..
-Wipe
-Cache / Dalvik cache / factory reset / system / format data / and internal storage (Make sure u wipe internal storage and format data! This will stop the Google logo loop. NOTE: U will lost everything if you do this step)
-Then I reboot into TWRP after the wipe
-I download nexus 4 toolkit v1.3 Toolkit dl link
-mount /system/ in TWRP
-Put the below stock rooted rom into put_files_to_push_here (it's inside installed path of the nexus 4 toolkit)
-Push This stock rooted rom using #13 option in nexus 4 toolkit
-It will ask if u using a custom rom or insecure image type yes
-wait 2-3 mins to push. If everything goes well it should say "Finished xxx secs"
-Install the Stock rooted rom using TWRP
-reboot
Click to expand...
Click to collapse
got it all sorted and going. when trying to push to device i get "error: device not found" what way should i connect the phone? whilst in recovery and i've checked "mount system"?
Thanks so much for the help guys much appreciated!
Roshi69 said:
got it all sorted and going. when trying to push to device i get "error: device not found" what way should i connect the phone? whilst in recovery and i've checked "mount system"?
Thanks so much for the help guys much appreciated!
Click to expand...
Click to collapse
Do u have adb driver installed on ur pc? If you do, it should show ur device near top left of toolkit. It should say " ADB mode List of devices attached" If you can see ur device with the serial number then everything should work fine.
You can install the driver using toolkit.. it's the #1 option
When pushing the file, u should be in TWRP (where u see install.. wipe etc..) and mount /system/ should have an X on it.
enyceckk said:
do u have adb driver installed on ur pc? If you do, it should show ur device near top left of toolkit. It should say " adb mode list of devices attached" if you can see ur device with the serial number then everything should work fine.
You can install the driver using toolkit.. It's the #1 option
when pushing the file, u should be in twrp (where u see install.. Wipe etc..) and mount /system/ should have an x on it.
Click to expand...
Click to collapse
it worked!!! Thank you so much!!!
Hi everyone,
So I have never ran across this issue before. I haven't had any problems with my device and yesterday I wanted to test out the new Jelly Bam update rom from their site. The rom would not boot pasted the "Google" spash screen so I rebooted in to recovery and did a full wipe and restored via backup to my previous rom just like normal. Well then I noticed that normally when I connect my phone to my computer I see my internal memory drive pop up which I am able to click on and then access my files, but this time when I accessed it I have a hand full or folders like 0, twrp, android, etc and I had to double click on o folder to access my memory with all my files. I thought that was weird so I went on about my day. Later I tried to do a fresh install of my current rom PACman but even after doing a fresh install the phone will not boot passed the Google spash screen, and now twrp doesn't even see my backup file because its being directed to this new partition with all the folders I was talking about. I even tried using the file manager in twrp to move the backup to that twrp folder but twrp doesn't even see it.
So as of right now I can get in to twrp but I can not boot my device pasted the google splash screen. I also can't access my memory through my pc since nexus does not allow it with twrp. What do I do? My thoughts are that something got screwed up with the partitions when I flashed the Jelly Bam rom so I will need to go back to stock, does that sound about right? I was thinking of following these instructions to go back to stock and then move on from there, any thoughts or alternatives? http://www.androidrootz.com/2012/12/how-to-unroot-nexus-4-to-stock-42-jelly.html
Thank you
Trying this method to return to stock: http://www.wugfresh.com/nrt/
If no one has any input I will assume I am following the right path.
I flashed factory images a couple weeks ago and in order for TWRP to see the nandroids I copied back to my phone I put them in the following path: /sdcard/TWRP/BACKUPS/stringofrandomnumbersandletters/
Are your TWRP backups in a similar location?
If you've decided to go back to stock, I'd suggest using the following guide by efrant... http://forum.xda-developers.com/showthread.php?p=34552123
Sent from my Nexus 4 using xda app-developers app
It is twrp fault. That recovery is crap to be honest.
Sent from my Nexus 4 using xda premium
It looks like twrp is now looking at my twrp folder in my sd card 1 not sd card 0 where I have had my backups and all my files. After trying again, I moved the TWRP backup to the sd card 1 twrp folder, twrp recognized it and I restored from backup....but when I reboot I am still stuck on the Google screen. Not sure what to do.
Underground_XI said:
It is twrp fault. That recovery is crap to be honest.
Sent from my Nexus 4 using xda premium
Click to expand...
Click to collapse
Since I can't move anything to my memory, any suggestions?
If you've got adb and the proper drivers installed on your PC you could try:
Code:
adb push ROM.zip /sdcard/ROM.zip
from the command prompt. Obviously use the name of the actual ROM.
Edit: ignore that, just read the post where you managed to restore! D'oh!
Have you tried clearing both caches?
The only issue is that my phone is not recognized as having debugging on when I use the Nexus Root Toolkit. Would it matter trying to push via adb? Also with your code, can you specify exactly what I should type. Mine shows C: \Users
synergeticink said:
The only issue is that my phone is not recognized as having debugging on when I use the Nexus Root Toolkit. Would it matter trying to push via adb? Also with your code, can you specify exactly what I should type. Mine shows C: \Users
Click to expand...
Click to collapse
If I were you I would not rely on a toolkit at this point. If you boot into recovery you can use adb commands to push the files from your computer to your phone.
Edit... Spec-Chum's suggestion of wiping caches is a good one. Have you tried that while booted into TWRP?
You could also try the following from within TWRP:
1. Factory reset
2. Wipe system
3. Restore nandroid backup
4. Wipe caches
5. Reboot
Sent from my Nexus 4 using xda app-developers app
chef_christoph said:
If I were you I would not rely on a toolkit at this point. If you boot into recovery you can use adb commands to push the files from your computer to your phone.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
And that's were I am stuck right now. I am not a pro at using adb commands, never used it till I got my nexus 4. Right now when I launch the cmd it shows "C:\Users\My User Name\Desktop>", not sure where to go next. I guess I am not sure what I should be pushing at this point either.
Oops...it seems I was editing my post at the same time you were responding to it...take a look at my previous response again
I'm fairly new around here but I can help with the adb commands if you need. Hang in there
Sent from my Nexus 4 using xda app-developers app
chef_christoph said:
If I were you I would not rely on a toolkit at this point. If you boot into recovery you can use adb commands to push the files from your computer to your phone.
Edit... Spec-Chum's suggestion of wiping caches is a good one. Have you tried that while booted into TWRP?
You could also try the following from within TWRP:
1. Factory reset
2. Wipe system
3. Restore nandroid backup
4. Wipe caches
5. Reboot
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yeah. I tried wiping cache/dalvik/system/factory reset and then both restoring from backup or flashing the latest PACman rom which is in my sd card. Right now I am reading the http://forum.xda-developers.com/showthread.php?t=2018179 guide to see if I can use adb to flash my rom or another recovery. Makes sense if its the recovery not letting me flash anything, but i'm not a dev. At least I am able to get in to recovery to begin with, good sign I guess.
If you can boot into bootloader and recovery there are many options to help get you up and running again. That guide by Jubakuba is really good but if wiping and restoring your backup from within TWRP didn't work I would highly suggest reading efrant's guide on returning to stock...I posted the link in an earlier reply.
Sent from my Nexus 4 using xda app-developers app
I was able to flash cwm using adb, now trying to do a fresh install
Nope, doing a fresh install didn't work. Now its time to restore to stock. ......
One problem:
"
5) Extract the files from within the .tgz file which you downloaded in step 3 using 7-zip, not WinZip or WinRAR or whatever.
6) Make sure you have extracted ALL the files (including extracting any files in any archives inside the .tgz file). You should have six (6) files ending with .img in the directory you created in step 1. The other files you extracted from the .tgz are not necessary;"
UPDATE; Got it, instructions were not clear.
synergeticink said:
UPDATE; Got it, instructions were not clear.
Click to expand...
Click to collapse
I was just checking how it appeared on my own computer before responding... I'm glad you got that part cleared up.
Sent from my Nexus 4 using xda app-developers app
chef_christoph said:
I was just checking how it appeared on my own computer before responding... I'm glad you got that part cleared up.
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Its weird adb will not work on the computer unless the files are in the platform-tools folder in androi sdk. trial and error, just finished flashing system....
should I do this command, I really don't want to lose my stuff:
10) Optional (NOT optional for n00bs) -- Flash the data partition: fastboot flash userdata userdata.img Note: this command will wipe your device (including /sdcard), EVEN if your bootloader is already unlocked. See note 2 below.
Well, I didn't and finished the process...did a reboot when I was done...now its on the Google screen...just waiting....I'm seeing a Nexus X splash screen!!!...
Update: Its taking a very long time, hopefully it works...going to give it another 10 mins
And we have BOOT... thank you everyone! Now I have to root this sucker!
Hi All
I am in the process of flashing Cyanogenmod 11 onto my TF300T however I am in a world of hurt. First I updated to the latest TWRP (2.6.3 -4.2). When i boot up into TWRP it is asking me for a password which I do not know. If I press Cancel i cannot see any contents of /sdcard. Also if I insert a microSD card, again cannot see any contents. TWRP is telling me there is no operating system installed and if i reboot it just comes straight back into TWRP.
I apologise if this question has already been asked but I just cant figure this one out.
What bootloader version do you have? What helped me was to reboot into the boot loader (using volume down+power, has three options RCK, cold-boot linux, Wipe data [dont ever ever ever wipe data]) and select cold-boot linux (the android guy in the middle) and it would boot back into my ROM. If you cant get in that way, you are going to have to use ADB on your computer and use the "adb reboot-fastboot" command. If you get in, back up your files, because you're at the event horizon of losing all your data. If your bootloader is 10.6.1.8 youre going to need to flash the latest asus stock firmware from their website.
Sent from my TF300T using XDA Premium 4 mobile app
Lyshco said:
Hi All
I am in the process of flashing Cyanogenmod 11 onto my TF300T however I am in a world of hurt. First I updated to the latest TWRP (2.6.3 -4.2). When i boot up into TWRP it is asking me for a password which I do not know. If I press Cancel i cannot see any contents of /sdcard. Also if I insert a microSD card, again cannot see any contents. TWRP is telling me there is no operating system installed and if i reboot it just comes straight back into TWRP.
I apologise if this question has already been asked but I just cant figure this one out.
Click to expand...
Click to collapse
u should back to twrp 2.5, or u should use scanno twrp.
Tunameltsalad said:
What bootloader version do you have? What helped me was to reboot into the boot loader (using volume down+power, has three options RCK, cold-boot linux, Wipe data [dont ever ever ever wipe data]) and select cold-boot linux (the android guy in the middle) and it would boot back into my ROM. If you cant get in that way, you are going to have to use ADB on your computer and use the "adb reboot-fastboot" command. If you get in, back up your files, because you're at the event horizon of losing all your data. If your bootloader is 10.6.1.8 youre going to need to flash the latest asus stock firmware from their website.
Sent from my TF300T using XDA Premium 4 mobile app
Click to expand...
Click to collapse
I am using bootloader 10.6.1.3. When I cold boot linux it just continually boots up into TWRP.
Whenever I try to run an ADB command i get "error: device not found". I have installed the android SDK, tried to install the USB drivers but no luck (possible windows 8 issue?).
It doesnt matter if I lose all data on it, i dont keep anything really important on it.
I have rolled back to 2.5.0 TWRP and it still asks me for a password.
I've switched over to my Mac now and have been able to push the CM-11 ROM into the sdcard directory. However when I attempt to flash it, it fails immediately with the log saying.
E:Unable to mount '/system'
E:Unable to mount '/cache'
Lyshco said:
I've switched over to my Mac now and have been able to push the CM-11 ROM into the sdcard directory. However when I attempt to flash it, it fails immediately with the log saying.
E:Unable to mount '/system'
E:Unable to mount '/cache'
Click to expand...
Click to collapse
I had something similar, tried many things but nothing worked so i ended up flashing stock ROM again with fastboot.
If you need help on how to do that just let me know.
rtfm
and more serious:
cm11=android4.4=new PITs(like with 4.1 to 4.2)
solution:
flash scsnnos twrp 2.6.3.0 from his omni thread and it works.
cheers
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
screeny added
Sent from my TF300T using XDA Premium 4 mobile app
Buster99 said:
rtfm
and more serious:
cm11=android4.4=new PITs(like with 4.1 to 4.2)
solution:
flash scsnnos twrp 2.6.3.0 from his omni thread and it works.
cheers
buster
Sent from my GT-I9505 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Ok this morning I have tried the following:
1. Flashed Scanno's TWRP from the OMNI thread using this command:
> fastboot -i 0x0B05 flash recovery recovery.img
2. Booted up into TWRP, again /sdcard is empty.
3. Pushed the OMNI ROM onto /sdcard using:
> adb push omni-4.4.2-20131218-tf300t-HOMEMADE.zip /sdcard/
4. Went to Install and selected the zip then it immediately fails saying:
Unable to mount '/system'
Am I missing something here? From above i see that i flash 'recovery'. Do I need to flash 'system' with fastboot?
no, but maybe your PITs are corrupt. do you still have an older nandroid backup you could try to restore first?
oh just read that twrp asks for password. is that still the case?
Sent from my GT-I9505 using XDA Premium 4 mobile app
Yep it's still asking me for a password.
What are PITs?
I'm not sure if I have a backup. When in TWRP if I go to restore it can't find any. It's like the whole tablet is wiped. Does this have something to do with not having the ability to mount anything?
Sent from my HTC_PN071 using Tapatalk
Ok, Buster99 I followed your instructions over at this thread and am now back up and running with stock.
http://forum.xda-developers.com/showpost.php?p=44244313&nocache=1&z=9056634965818376
For me to go to KitKat, can I just flash the OMNI ROM now?
EDIT: Nevermind, I am all back up and running, thanks so much for the help, i was getting a bit worried that I had bricked it!
HELP
So I just tried getting cm11 on my tf300t, i installed TWRP 2.5 and rooted my device, everything went well. I then did a factory reset and wiped cashe. I tried installing then cm11 zip file with no success. I get the message that it failed. And now im on a device with no ROM to boot into and no working ROM to flash on the device.
Since there is a SD card slot on the device, would it be possible to put another ROM on there and then flashing that?
Please help me!
ollemolle said:
So I just tried getting cm11 on my tf300t, i installed TWRP 2.5 and rooted my device, everything went well. I then did a factory reset and wiped cashe. I tried installing then cm11 zip file with no success. I get the message that it failed. And now im on a device with no ROM to boot into and no working ROM to flash on the device.
Since there is a SD card slot on the device, would it be possible to put another ROM on there and then flashing that?
Please help me!
Click to expand...
Click to collapse
in order to install CM11, you need a special TWRP modded for KK: http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7
You can copy a CM11 nightly and the TWRP onto a SD card and flash from there, or use fastboot.
cmendonc2 said:
in order to install CM11, you need a special TWRP modded for KK: http://forum.xda-developers.com/showpost.php?p=48508679&postcount=7
You can copy a CM11 nightly and the TWRP onto a SD card and flash from there, or use fastboot.
Click to expand...
Click to collapse
Hello, i have a similar problem, i wanted to install CM11 on my TF300T, i downloaded the latest version of TWRP from their site for the tablet, installed via Fastboot and everything seems to be ok, when i try to flash it (via CM OTA) it ask me for the password and it didn´t mount any data, but when i reboot the tablet it just keep loading twrp and i can't get to fastboot nor adb nor APX, so i have no idea on how to restore or boot back to the OS, or i just bricked the device?
thanks
josush said:
Hello, i have a similar problem, i wanted to install CM11 on my TF300T, i downloaded the latest version of TWRP from their site for the tablet, installed via Fastboot and everything seems to be ok, when i try to flash it (via CM OTA) it ask me for the password and it didn´t mount any data, but when i reboot the tablet it just keep loading twrp and i can't get to fastboot nor adb nor APX, so i have no idea on how to restore or boot back to the OS, or i just bricked the device?
thanks
Click to expand...
Click to collapse
What stock bootloader are you on?
cmendonc2 said:
What stock bootloader are you on?
Click to expand...
Click to collapse
i'm not really sure about the number but it was the latest one from ASUS, i was on the official 4.2.1 ROM when i moved to CM10 a few months ago
josush said:
i'm not really sure about the number but it was the latest one from ASUS, i was on the official 4.2.1 ROM when i moved to CM10 a few months ago
Click to expand...
Click to collapse
When you restart you tablet, and hold the vol down key while rebooting it will give you a bootloader number: 10.6.x.x.x
cmendonc2 said:
When you restart you tablet, and hold the vol down key while rebooting it will give you a bootloader number: 10.6.x.x.x
Click to expand...
Click to collapse
that's the point, it doesn't do anything, is like i'm not holding or pressing it, it just show the ASUS Logo screen and in the top left it says that the bootloader is unlocked as usual, i don't think is a wardware problem because it was working the last time it booted on Android
josush said:
that's the point, it doesn't do anything, is like i'm not holding or pressing it, it just show the ASUS Logo screen and in the top left it says that the bootloader is unlocked as usual, i don't think is a wardware problem because it was working the last time it booted on Android
Click to expand...
Click to collapse
Once it goes to recovery, adb will be accessible. Then follow Buster's recovery method.
Hey,
Last night I was thinking about reflashing my phone with a new ROM. I made a backup (it's on my computer now), transferred it to my computer. I installed the ROM files and put them into to clockwordmod folder thinking that they wouldn't be deleted if I deleted /data and /date/media (/sdcard) in the custom recovery under "mounts and storage menu."
I was wrong. It deleted the rom files and now I don't have anything to flash. If I try to reboot to system, it says "Android is upgrading - app 1 of 52" Once that is done, it gets stuck on "Android is upgrading - Loading Apps", or something like that.
What can I do? I heard I could ABD push but I have no idea what that is and how I can do it... Help!?
Any help? Please
Goto cmw and install your ROM via adb.
Under option install zip there will be a choice for flashing zip via adb. Just select that in cmw and connect your phone to laptop.
Now in laptop you should have adb files in a folder and paste your ROM in that adb folder.
Next do as it is written in cmw and it will be flashed
Sent from my Nexus 4 using xda app-developers app
suvasco said:
Hey,
Last night I was thinking about reflashing my phone with a new ROM. I made a backup (it's on my computer now), transferred it to my computer. I installed the ROM files and put them into to clockwordmod folder thinking that they wouldn't be deleted if I deleted /data and /date/media (/sdcard) in the custom recovery under "mounts and storage menu."
I was wrong. It deleted the rom files and now I don't have anything to flash. If I try to reboot to system, it says "Android is upgrading - app 1 of 52" Once that is done, it gets stuck on "Android is upgrading - Loading Apps", or something like that.
What can I do? I heard I could ABD push but I have no idea what that is and how I can do it... Help!?
Click to expand...
Click to collapse
You cant brick your phone as long as fastboot and recovery works.
boot into fastboot.
if your recovery is not working : reflash your recovery
Then boot into recovery and install rom via sideload;
From your pcadb sideload):
http://teamw.in/ADBSideload
Try wugfresh tool kit from here: http://www.wugfresh.com/nrt/
suvasco said:
Hey,
Last night I was thinking about reflashing my phone with a new ROM. I made a backup (it's on my computer now), transferred it to my computer. I installed the ROM files and put them into to clockwordmod folder thinking that they wouldn't be deleted if I deleted /data and /date/media (/sdcard) in the custom recovery under "mounts and storage menu."
I was wrong. It deleted the rom files and now I don't have anything to flash. If I try to reboot to system, it says "Android is upgrading - app 1 of 52" Once that is done, it gets stuck on "Android is upgrading - Loading Apps", or something like that.
What can I do? I heard I could ABD push but I have no idea what that is and how I can do it... Help!?
Click to expand...
Click to collapse
What can I do? I heard I could ABD push but I have no idea what that is and how I can do it... Help!? - What you can do is some leg work and look up how to ADB push instead of saying you dont know what that is. Now if you rooted your phone yourself at some point an ADB push was probably done. This is why most hate toolkits(if thats what was used) since it does not help you learn anything.
Search my friend but its like starting from scratch but if you have a working recovery still thats one less step...
adb push -> rom to phone
boot into recovery
flash rom
go on with life......:good:
playya said:
What can I do? I heard I could ABD push but I have no idea what that is and how I can do it... Help!? - What you can do is some leg work and look up how to ADB push instead of saying you dont know what that is. Now if you rooted your phone yourself at some point an ADB push was probably done. This is why most hate toolkits(if thats what was used) since it does not help you learn anything.
Search my friend but its like starting from scratch but if you have a working recovery still thats one less step...
adb push -> rom to phone
boot into recovery
flash rom
go on with life......:good:
Click to expand...
Click to collapse
That, or use adb push or sideload from recovery.
Sent from my Nexus 7 using Tapatalk
korockinout13 said:
That, or use adb push or sideload from recovery.
Sent from my Nexus 7 using Tapatalk
Click to expand...
Click to collapse
Yes... sorry I forgot to add sideload and if you not sure what that is please use Google
Edit; My bad I see instructions and website for sideloading were posted area in here
I wanted to do factory reset on my rooted nexus 4 , using CWM. It didn;t work (all files stayed) so I went to advanced and formated everything that was there. Now my phone doesn't start (the screen with "google" is on.
I can go to recovery or fastboot but in fastboot adb or anything can't see my device.
Is there anything I can do?
Yes, you wiped your os. Either adb push a rom zip onto your sdcard and flash in recovery or adb sideload a rom zip in recovery
Sent from my Nexus 5 using XDA Free mobile app
Should I sideload zip or tgz?
I tried zip, it says: installation aborted.
I tried tgz, it says e: can't open /tmp/update.zip (bad)
I also tried pushing, but installation aborted as well
If you're trying to get back to stock then flash individual partitions using fastboot.
This guide should help you out .
http://forum.xda-developers.com/nexus-4/general/how-to-how-to-flash-factory-image-t2010312
If you want to flash a custom ROM follow the steps in the previous post.
Doesn't work, like I said, adb can't see my nexus in bootloader.
Before I started doing anything I'd made a backup. Maybe I can restore it now somehow?
EDIT: @up, it worked, tkanks a lot
szajbuz said:
Doesn't work, like I said, adb can't see my nexus in bootloader.
Before I started doing anything I'd made a backup. Maybe I can restore it now somehow?
added: wait, smoething is happening
Click to expand...
Click to collapse
If your in the boot loader you need to use fastboot devices, not adb devices
Sent from my Nexus 5 using XDA Free mobile app
@up
yeah but I realized that after my previous post
If you are on bootloader you van use nexus foot toolkit for flash stock with bricked option