Related
So I rooted, then put CM10.1 nightly and gapps on my sdcard, then went to flash, and I spaced out and accidentally formatted SDCARD when i know that I shouldnt have. crap.
i tried using the "sideload" feature but it wouldnt work on my adb-mac version, i also tried adb pushing ROM files to SDCARD, it says transfered but when i go to flash it says no files in SDCARD, I also tried pushing to SDCARD/0 but i get an error that it isnt a directory since it is formatted.
SOME ONE PLEASE give me instructions on what to do. Do I have to go back to stock or can I just get this to go straight to CM10.1? Id prefer straight to CM10.1 obviously.
crackmulah said:
So I rooted, then put CM10.1 nightly and gapps on my sdcard, then went to flash, and I spaced out and accidentally formatted SDCARD when i know that I shouldnt have. crap.
i tried using the "sideload" feature but it wouldnt work on my adb-mac version, i also tried adb pushing ROM files to SDCARD, it says transfered but when i go to flash it says no files in SDCARD, I also tried pushing to SDCARD/0 but i get an error that it isnt a directory since it is formatted.
SOME ONE PLEASE give me instructions on what to do. Do I have to go back to stock or can I just get this to go straight to CM10.1? Id prefer straight to CM10.1 obviously.
Click to expand...
Click to collapse
Push cwm via fastboot then reflash the rom
Fastboot flash recovery (your recovery)
Sent from my Nexus 4
Hindsight 20/20, but it never hurts to do an adb backup, it will b/u your sdcard as well.
For the future: http://forum.xda-developers.com/showthread.php?t=1420351
mark manning said:
Push cwm via fastboot then reflash the rom
Fastboot flash recovery (your recovery)
Sent from my Nexus 4
Click to expand...
Click to collapse
did this, but still same error, no files found in sd card. i did not think this would solve it but i tried anyway...
crackmulah said:
did this, but still same error, no files found in sd card. i did not think this would solve it but i tried anyway...
Click to expand...
Click to collapse
So you've successfully flashed a recovery img via fasboot? Did you also push a copy of the ROM zip back to your phone?
Boot to recovery and then adb push the ROM to the sd card.
Code:
adb push yourROMsName.zip /sdcard/
The above code assumes you've placed the rom zip in the adb or platform-tools folder on your PC.
Can't you just boot into fastboot, flash a recovery, boot into said recovery and mount the internal storage and drag and drop the files from your computer?
How did you format the SD card when the phone doesn't have one?
jakejm79 said:
Can't you just boot into fastboot, flash a recovery, boot into said recovery and mount the internal storage and drag and drop the files from your computer?
How did you format the SD card when the phone doesn't have one?
Click to expand...
Click to collapse
The internal storage is considered an SD card.
Sent from my Nexus 4
CMNein said:
So you've successfully flashed a recovery img via fasboot? Did you also push a copy of the ROM zip back to your phone?
Boot to recovery and then adb push the ROM to the sd card.
Code:
adb push yourROMsName.zip /sdcard/
The above code assumes you've placed the rom zip in the adb or platform-tools folder on your PC.
Click to expand...
Click to collapse
yes i did repush the rom file. this isnt working because i dont believe that flashing a recovery adds folder/partition information to the sdcard. maybe im wrong, but it didnt work.
crackmulah said:
yes i did repush the rom file. this isnt working because i dont believe that flashing a recovery adds folder/partition information to the sdcard. maybe im wrong, but it didnt work.
Click to expand...
Click to collapse
Are there any spaces in the ROM zips name?
CMNein said:
Are there any spaces in the ROM zips name?
Click to expand...
Click to collapse
lol no
I am currently using Wug's Nexus Toolkit to try to flash stock from softbrick mode...will let you know how it goes
EDIT:: This is giving me some trouble as I cant turn on USB DEBUGGING (because i have no OS installed) to install the drivers and such.....
PLEASE KEEP IDEAS ROLLIN...
crackmulah said:
lol no
I am currently using Wug's Nexus Toolkit to try to flash stock from softbrick mode...will let you know how it goes
EDIT:: This is giving me some trouble as I cant turn on USB DEBUGGING (because i have no OS installed) to install the drivers and such.....
PLEASE KEEP IDEAS ROLLIN...
Click to expand...
Click to collapse
Just go back to stock
Sent from my Nexus 4
mark manning said:
Just go back to stock
Sent from my Nexus 4
Click to expand...
Click to collapse
this is what im trying to do lol...having trouble tho. what is your recommended method?
crackmulah said:
this is what im trying to do lol...having trouble tho. what is your recommended method?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2010312
Sent from my Nexus 4
You could also try wugfresh's toolkit and selecting "Back to Stock" -> "Soft-bricked".
mark manning said:
http://forum.xda-developers.com/showthread.php?t=2010312
Sent from my Nexus 4
Click to expand...
Click to collapse
ya im gonna do that if this Wug's Toolkit wont do the trick...seems to be working now tho...in middle of flashing stock
crackmulah said:
ya im gonna do that if this Wug's Toolkit wont do the trick...seems to be working now tho...in middle of flashing stock
Click to expand...
Click to collapse
You should learn how to do this without tool kits. Those things while helpful are nothing more than a crutch
Sent from my Nexus 4
mark manning said:
The internal storage is considered an SD card.
Sent from my Nexus 4
Click to expand...
Click to collapse
Yeah but doesn't the Nexus 4 lump all the internal storage together, I know other devices like the OXL have like 6GB internal storage and then a 'simulated' mSD card of about 10GB, making 16GB total. But the Nexus 4 uses the whole 16GB (or 8GB) as internal storage.
mark manning said:
You should learn how to do this without tool kits. Those things while helpful are nothing more than a crutch
Sent from my Nexus 4
Click to expand...
Click to collapse
yes definitely agreed.
although ive always wanted to try one, and it worked! if this were to happen again (if i dont shoot myself) then i will be doing it manually.
Thanks so much to everyone for all the help! I am now running Official CM10.1 Nightly (newest) and running beautifully so far. This is my second N4 tho, so I will be using my 1st stock one for today since its already setup, have to go to work now and will setup my new CM10.1 N4 later, hopefully wont find any crazy bugs...
I had the same problem and after reading this thread I tried the Fastboot method first:
after I finished it didnt boot so I continue with the inst', then it booted but only with 8GB, so I continue with the inst' and from that stage it just didnt boot.
At the end I tried the root toolkit V1.6.2 and the phone back to life with stock rom and 16GB.
I'm back to stock now. But I've used the sideload successfully. After you get your phone restored, you'll probably want to do a full factory reset because some of your pushes have probably gone through and are now eating up space. You can't delete them that I know of unless you FULLY format.
ANYWAY
When I got sideload to work, I had to push it to /sdcard/0/, /sdcard0/, or something like that. Wish I could be more specific, but I don't want to change from stock to install cwm (the ROMS have too many bugs so far, and we might be getting 4.2.2)
The key is finding the right directory to push it to. Experiment with slashes, and it SHOULD work.
I was going to flash a rom using twrp. Before I got to flash it I wiped the internal storage. Now I have nothing on my tablet. Can I use the adb sideload feature in twrp to push a rom on the device? If so can you explain how? I'm new at this so I do think know the commands. Thank you for your help.
I'm in the same boat as you
Sort of in the same boat as you. Except I'm having trouble with ADB sideload and Fastboot. But for you to try and fix your issue go here: http://forum.xda-developers.com/showthread.php?t=2001868
That toolkit will allow you to flash either a Google stock ROM or a backup using fastboot. If that doesn't work then reply back to this thread.
I also did the same thing as you did, I was able to side load cyanogen mod on the nexus
Just go into recovery and then into adbsideload option,make sure device is connected to PC and adbfastboot drivers are installed,then while your recovery is in adbsideload mode, type in command by opening command prompt in platform tools in sdk 'adb sideload filename.zip'
Where filename is the name of the rom you downloaded,then the ROM will be pushed and twrp will flash it automatically
Make sure you reset the device(factory reset) from twrp first,otherwise ROM will not be flashed
Sent from my Nexus 7 using xda app-developers app
You can also use an OTG/memory stick. TWRP reads them just fine. I've also used an SD card & reader. Load your rom, kernel, gapps & connect. Then you can flash all right from your memory-source. I find it much more convenient.
Sent from my Nexus 10 using Tapatalk 2
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