the story goes like this, I flash TWRP 2.2.0 did a nandroid and deleted all the necessary partitions to install the new rom, I put the rom in the SD card, TWRP is not mounting the sd card wich happens to work flawlessly in my phone, and pc, now i cant access the internal storage nor the sdcard, Please I dont know what to do anymore i cant get my cpuid because my tablet does not have an os so i cant select usb debugging, i cant access my internal storage either from the pc, im using skrilax-oz bootloader v7, the computer only recognizes the tablet in fastboot, how can i put a recovery in it via the bootloader in fastboot if posible.
If your PC will recognize Fastboot (you should have it listed in Device manager when you go to fastboot with Skirlaz Bootloader), then the easiest thing would be to get the proper recovery .img file. I suggest EZTerry Public revovery, or CWM. Most recent versions of both. Your choice. You can find CWM recovery image at tegraowners, or get the Public Recovery from the XDA Dev forum.
Boot your tab to fastboot.
Make sure the xxxxxxxxrecovery.img file is in the same folder as your Android/Android-sdk/Platform-tools folder. (has to be in the same folder as fastboot.exe)
Then open a Command window in that folder
Type fastboot flash recovery xxxxxxxrecovery.img
Then hit enter
Remember, where xxxxxxxrecovery,img is the name of the recovery image.
This should hook you up.
TWRP has some issues,
MD
cubanghost said:
the story goes like this, I flash TWRP 2.2.0 did a nandroid and deleted all the necessary partitions to install the new rom, I put the rom in the SD card, TWRP is not mounting the sd card wich happens to work flawlessly in my phone, and pc, now i cant access the internal storage nor the sdcard, Please I dont know what to do anymore i cant get my cpuid because my tablet does not have an os so i cant select usb debugging, i cant access my internal storage either from the pc, im using skrilax-oz bootloader v7, the computer only recognizes the tablet in fastboot, how can i put a recovery in it via the bootloader in fastboot if posible.
Click to expand...
Click to collapse
Can you still go into recovery by power+volume down? If yes, then go back into trwp recovery and do the following. Mount option >click mount sd card and using external sd. Once you have those options clicked, go back to install option. There you will be able to access your external sd card. I think the best recovery to use now is thor 1.7.3.
Good luck,
Sent from my A500 using Tapatalk 2
10507 said:
Can you still go into recovery by power+volume down? If yes, then go back into trwp recovery and do the following. Mount option >click mount sd card and using external sd. Once you have those options clicked, go back to install option. There you will be able to access your external sd card. I think the best recovery to use now is thor 1.7.3.
Good luck,
Sent from my A500 using Tapatalk 2
Click to expand...
Click to collapse
it wont mount, that is why im having such a big issue trying to install a new recovery or flash the rom in the external sd card.
Ok, you have 2 different threads going. In this thread, you didn't mention anything about formatting your internal storage. This is why XDA has a rule about posting the same thing in multiple forums. Chances are you say something in one, and not the other. And what you will get is sometimes not good info, or even worse, no response.
Dees-troy and I have posted possible solutions. Problem is, other people get confused when they see it.
That little bit of missing info between the multiple posts can mean a big thing.
I will let it slide this time. Next time, I will delete one or the other.
MD
cubanghost said:
it wont mount, that is why im having such a big issue trying to install a new recovery or flash the rom in the external sd card.
Click to expand...
Click to collapse
Did you fastboot a new recovery image like I directed?
MD
Moscow Desire said:
If your PC will recognize Fastboot (you should have it listed in Device manager when you go to fastboot with Skirlaz Bootloader), then the easiest thing would be to get the proper recovery .img file. I suggest EZTerry Public revovery, or CWM. Most recent versions of both. Your choice. You can find CWM recovery image at tegraowners, or get the Public Recovery from the XDA Dev forum.
Boot your tab to fastboot.
Make sure the xxxxxxxxrecovery.img file is in the same folder as your Android/Android-sdk/Platform-tools folder. (has to be in the same folder as fastboot.exe)
Then open a Command window in that folder
Type fastboot flash recovery xxxxxxxrecovery.img
Then hit enter
Remember, where xxxxxxxrecovery,img is the name of the recovery image.
This should hook you up.
TWRP has some issues,
MD
Click to expand...
Click to collapse
Thank you, thank you thankyou, you have no idea the headhache you have saved me, I'm very greatfull for your help, it work like a charm, no more TWRP recovery for me.
cubanghost said:
Thank you, thank you thankyou, you have no idea the headhache you have saved me, I'm very greatfull for your help, it work like a charm, no more TWRP recovery for me.
Click to expand...
Click to collapse
Hey, don't forget the THANKS Button
MD
cubanghost said:
Thank you, thank you thankyou, you have no idea the headhache you have saved me, I'm very greatfull for your help, it work like a charm, no more TWRP recovery for me.
Click to expand...
Click to collapse
TWRP is a good recovery. And it works for most. As with most recovery systems, it will have times when things don't work correctly. Call it a "hic-cup". And the only thing to do, is totally install something else. Works most of the time.
Dees Troy is a darn good Dev. And we're grateful to have him around. In this case, you had to do something radical to shock the system. Works every time
Also, throw a Thanks to Skirlax_CZ for the bootloader and the fastboot capability. If you didn't have that, your "stuff would be hanging in the breeze" about now.
MD
Moscow Desire said:
TWRP is a good recovery. And it works for most. As with most recovery systems, it will have times when things don't work correctly. Call it a "hic-cup". And the only thing to do, is totally install something else. Works most of the time.
Dees Troy is a darn good Dev. And we're grateful to have him around. In this case, you had to do something radical to shock the system. Works every time
Also, throw a Thanks to Skirlax_CZ for the bootloader and the fastboot capability. If you didn't have that, your "stuff would be hanging in the breeze" about now.
MD[/QUOTE
most defenatly im greatful for Skirlax and his boot loader it totaly saved me. and TWRP i use it on my skyrocket and works very well, thus why i flash it with out looking for the thread.
Click to expand...
Click to collapse
Related
As a disclaimer, I have already searched and found some people with the same issue. What I haven't found is someone that arrived at this problem in the same way I did. I am scared ****less of bricking my phone (and hope I haven't already). So at this point, I am looking for some help to figure out my best course of action.
I recently updated to JF1.5 using his updater app, and everything worked. Today when I received my new SDcard, I started the process to get apps on my SD following this tutorial: http://forum.xda-developers.com/showthread.php?t=512743
I got as far as partitioning my card using the Apps2SD application as described, doing everything the tutorial says. I began the partition on my phone, and let it sit.....and sit, and sit. It sat frozen on the partitioning screen (the one with the slider to select the size) for almost an hour before i pulled the battery. I selected 1444mb for the ext2 after reading that it was not a good idea to go higher than 1500mb.
Now, as stated the phone boots to the G1 splash and goes nowhere. I am however still able to boot in recovery mode using Home+Power. Interestingly, it says at the top:
"Android system recovery utility
Build: JFv1.42"
Not sure if this means that 1.5 didn't install correctly or what, but that's what it says.
I have no idea what to do at this point, and am scared to go on without some candid advice. Sorry for the noobishness of my description - if there is anything else needed to give accurate advice please let me know. Also thanks in advance for any help I can get!
Same thing happened to me, you have to reflash. I tried using that method and it never worked for me, although I already had the partition. So reflash jf 1.51 and you are golden. BTW that text you see in recovery is the recovery image version, until you switch to another it will say that.
meoshe said:
Same thing happened to me, you have to reflash. I tried using that method and it never worked for me, although I already had the partition. So reflash jf 1.51 and you are golden. BTW that text you see in recovery is the recovery image version, until you switch to another it will say that.
Click to expand...
Click to collapse
Thanks for the response. I'll have to find a way to get that image onto my SD card. I just bought a 16BG card and that was the card I was using when I ran into this problem.....oh wait a sec....
I'm assuming that the JF1.51 update.zip will still be on my old 1GB card from when I updated to JF1.51 via his updater app last week? If so then my life will be a lot easier, and I'll just swap back to that card, boot up in Recovery, flash from update.zip, and that should be it?
Just want to make sure before I put that old card back in and try to flash....
try wiping before you update? Also to mount your SDcard (if you need to) press alt-x in recovery (or in adb shell) and type
Code:
echo /dev/blockl/mmdblk0 > /sys/devices/platform/usb_mass_storage/lun0/file
x2 that's what i had to do since my computer stopped reading sd cards.
Wipe then update.
I'd also recommend using CMv3.4 because the apps2sd is automated. It runs a2sd by itself
And with Cyanogen Recovery v1.2 you can move apps to sd card
First off, just want to thank everyone for the help. I successfully reflashed with jf1.51, but now I can't seem to sign in. I'm on the welcome screen, skipped the tutorial, entered my Gmail account and it sits for awhile trying to contact the server and then says there's a problem with the service or my sim card.
I know my sim card is provisioned for data, so not sure what's happening here...any ideas?
EDIT: Forgot I had to enter the Rogers APN settings, trying that now (Duhhh)
Abolfazl said:
Wipe then update.
I'd also recommend using CMv3.4 because the apps2sd is automated. It runs a2sd by itself
And with Cyanogen Recovery v1.2 you can move apps to sd card
Click to expand...
Click to collapse
I'm interested in this Cyanogen stuff, but no idea where to start. Any good tutorials? I was following this scene for awhile but kinda lost touch a few months ago - turns out there's been lots of developments.
t3mp3st said:
First off, just want to thank everyone for the help. I successfully reflashed with jf1.51, but now I can't seem to sign in. I'm on the welcome screen, skipped the tutorial, entered my Gmail account and it sits for awhile trying to contact the server and then says there's a problem with the service or my sim card.
I know my sim card is provisioned for data, so not sure what's happening here...any ideas?
EDIT: Forgot I had to enter the Rogers APN settings, trying that now (Duhhh)
I'm interested in this Cyanogen stuff, but no idea where to start. Any good tutorials? I was following this scene for awhile but kinda lost touch a few months ago - turns out there's been lots of developments.
Click to expand...
Click to collapse
It is pretty cut and dry. Cyanogen's Mod unleashes the G1 to its max. Apps2sd is automated and is working before you can even turn your phone on.
CMv3.4
CM Recovery v1.2
Abolfazl said:
It is pretty cut and dry. Cyanogen's Mod unleashes the G1 to its max. Apps2sd is automated and is working before you can even turn your phone on.
CMv3.4
CM Recovery v1.2
Click to expand...
Click to collapse
Cool, I guess I'll try it out now before trying to restore everything. I don't see a tutorial for it though, or am I to just follow the previous "How to root" tutorial and just use his image as the update.zip?
t3mp3st said:
Cool, I guess I'll try it out now before trying to restore everything. I don't see a tutorial for it though, or am I to just follow the previous "How to root" tutorial and just use his image as the update.zip?
Click to expand...
Click to collapse
no no no! just rename CM3.4 to update.zip, enter recovery (Home+power) wipe (alt+w) and flash (alt+s) after it says installation successful, reboot (Home+back)
you might also want to download his recovery image 1.2 like suggested in the posts above me
place the recovery image on your sdcard, do not rename it and do
Code:
flash_image recovery /sdcard/cm-recovery-1.2.img
alritewhadeva said:
no no no! just rename CM3.4 to update.zip, enter recovery (Home+power) wipe (alt+w) and flash (alt+s) after it says installation successful, reboot (Home+back)
you might also want to download his recovery image 1.2 like suggested in the posts above me
place the recovery image on your sdcard, do not rename it and do
Code:
flash_image recovery /sdcard/cm-recovery-1.2.img
Click to expand...
Click to collapse
Thanks a lot, going to try that now with my 16GB card. And just to be clear (last questions in this thread, I PROMISE!), I should flash with CM3.4 and THEN install the recovery image, or vice versa?
Also, with CM3.4, will I have to go through to steps again to try to partition my card (which is where i ran into the problem from post #1), or is there some automatic process built into his super-de-duper ROM?
Thanks again to all for the speedy responses!!
t3mp3st said:
Thanks a lot, going to try that now with my 16GB card. And just to be clear (last questions in this thread, I PROMISE!), I should flash with CM3.4 and THEN install the recovery image, or vice versa?
Also, with CM3.4, will I have to go through to steps again to try to partition my card (which is where i ran into the problem from post #1), or is there some automatic process built into his super-de-duper ROM?
Thanks again to all for the speedy responses!!
Click to expand...
Click to collapse
Don't worry asking questions is good as long as they are intelligent. You should flash CM3.4 and then the recovery image, as that is what i did. However, i don't think it really matters. To be safe, flash CM3.4 and then the recovery image.
And to your question pertaining to partitioning your SDcard, you can try MarcusMaximus' Apps2SD2 app which formats the card for you here
Unzip it to your sdcard and install it using ASTRO file manager or some other file manager.
If you have adb working,
Code:
adb install AppstoSD2.apk
if you have other questions you can always contact me on AIM- roflzbrianxdd
alritewhadeva said:
Don't worry asking questions is good as long as they are intelligent. You should flash CM3.4 and then the recovery image, as that is what i did. However, i don't think it really matters. To be safe, flash CM3.4 and then the recovery image.
And to your question pertaining to partitioning your SDcard, you can try MarcusMaximus' Apps2SD2 app which formats the card for you here
Unzip it to your sdcard and install it using ASTRO file manager or some other file manager.
If you have adb working,
Code:
adb install AppstoSD2.apk
if you have other questions you can always contact me on AIM- roflzbrianxdd
Click to expand...
Click to collapse
Thanks a ton, I'll get to this right after i finish this delicious sub! I'll also add you so I can IM if i have any more questions..
t3mp3st said:
Thanks a ton, I'll get to this right after i finish this delicious sub! I'll also add you so I can IM if i have any more questions..
Click to expand...
Click to collapse
Cool, Best of Luck with the flashing
alritewhadeva said:
no no no! just rename CM3.4 to update.zip, enter recovery (Home+power) wipe (alt+w) and flash (alt+s) after it says installation successful, reboot (Home+back)
you might also want to download his recovery image 1.2 like suggested in the posts above me
place the recovery image on your sdcard, do not rename it and do
Code:
flash_image recovery /sdcard/cm-recovery-1.2.img
Click to expand...
Click to collapse
Alright...I successfully partitioned my card, flashed with CM 3.4, but now when I try this instruction to install the new recovery, i get this error msg in Terminal:
error writing recovery: Permission denied
Any ideas?
You have to enter su before the code..
Code:
su
then
Code:
flash_image recovery /sdcard/cm-recovery-1.2.img
meoshe said:
You have to enter su before the code..
Code:
su
then
Code:
flash_image recovery /sdcard/cm-recovery-1.2.img
Click to expand...
Click to collapse
I did not enter the su, I will try that now thanks. In the mean time I also performed this step:
13. My /system/sd is read only and/or didn't upgrade to ext3!
Your filesystem is probably corrupt. Boot into recovery and open a console. Run "mount /system" then "/system/bin/e2fsck /dev/block/mmcblk0p2" and fix your filesystem. Reboot.
from: http://forum.xda-developers.com/showthread.php?t=518851
So I hope that didn't hurt anything...ill try with the su now. Thanks!
edit: out of curiosity, what does the "su" stand for? I feel if I know this it may help me to remember to enter it before any commands.
edit #2: does it stand for "Super User" to allow super user permissions? I gathered this after entering SU prompted me to allow superuser access
New recovery.img successfully installed! Thanks again to everyone that helped me with this.
I know I can transfer apps to SD easily from recovery now, but is there also a similar way to do it from the phone (or do they install to the SDcard by default now?)
Hey T3MP3ST... how did it go with upgrade to cm3.4
I had the same problem as you mentioned start of the post....
(stuck at g1, after partition).
this cm3.4 sounds like the solution for me to have apps2sd..
as it is in the ROM automatically, if i understood correctly.
dynamisoz said:
Hey T3MP3ST... how did it go with upgrade to cm3.4
I had the same problem as you mentioned start of the post....
(stuck at g1, after partition).
this cm3.4 sounds like the solution for me to have apps2sd..
as it is in the ROM automatically, if i understood correctly.
Click to expand...
Click to collapse
Hey there, with the help from everyone in this thread, along with the partitioning instructions using Ubuntu (if you still need to partition your card) from tubaking182 found here: http://forum.xda-developers.com/showthread.php?t=523648, It was great.
I just finished flashing with that ROM and then installing CM's recovery image (which is AWESOME...trackball selection, Apps2SD in one click)
I HIGHLY recommend it. If you have any problems, I'm sure you'll find most of the answers in this thread. If not, try PMing one of the helpful respondents, or I may be of SOME help with some minor questions or assurances.
Hi, i'm new here so i can't post in the development section.
I have a xoom wi-fi only US version and things have gone terribly wrong. I had unlocked bootloader + Android 3.2 rooted and i was trying to install a theme by using the clockwork mod recovery, but after I did it just kept replaying the boot animation and would not actually start. I freaked out and used clockwork recovery to format user data, cache, /system and the like. Now i can't get off the Motorola screen and i was wondering if there is a way to reinstall (the latest rooted version of) android on my device. Someone please help me, and if you can can you walk me through it. Any help would be greatly appreciated!!
have you tried downloading another version, put it on your SD card and flash it from CWM recovery?
This forum may be able to help you as well...
http://forum.xda-developers.com/showthread.php?t=1209341
i suggest u to flash a new rom instead.
Ok, I have the latest rooted version of android here on my PC.
How exactly do I get it installed onto my xoom? I am aware that you can use adb but can you please go over the exact procedure? (i got it here http://forum.xda-developers.com/showthread.php?t=1242524) Thanks that would be very helpful. I just want my device back
How do u do that using ADB? Please help!
Neardood1 said:
How do u do that using ADB? Please help!
Click to expand...
Click to collapse
ok first off just relax and you posted this in the right section... General or Q&A is where you post questions not Development so you are ok. Now on to your issue, download another rooted rom preferably Tiamat from here. Follow instructions on how to flash the file and that should get you back up and running. Now no need to ask for specifics and wait for it since all OP's in Development will instruct you on what to do.
Also did you make a backup, if you did it would be easier to just flash that. Hope it helps and dont panic. Next time make a backup before flashing themes. Oh yea if you still have the original rom you were running on your sd card just flash that again. If you still have an issue after flashing then do a factory reset wipe in CWM and try and reboot.
So basically your gonna try and flash a rom to see what happens... Any rom you have...
Ok, so i've copied it onto the micro SD card from my phone, there's a lot of other crap in there but I've just put it on into root (not in any folders). Now, how exactly do i install it because the thread just says to "install rom". i'm in clockwork recovery now, what do i select to get it to install?
I have ClocworkMod Recovery v4.0.0.4, and there doesn't seem to be an external sd card option, just the /sdcard directory from within android. Does this mean that I have to find a way to flash the rom into that directory using fastboot or something? If so, pleese just tell me how.
Neardood1 said:
I have ClocworkMod Recovery v4.0.0.4, and there doesn't seem to be an external sd card option, just the /sdcard directory from within android. Does this mean that I have to find a way to flash the rom into that directory using fastboot or something? If so, pleese just tell me how.
Click to expand...
Click to collapse
My friend this is why I told you to follow OPs instruction. How did you flash your last rom or get rooted in the first place. This procedure is no different, relax and read the options in clockwork and it with will all come to you. You are installing/flashing a rom so it would be install from zip. Since I may not be on here to help you when your ready this is why I stress reading the intructions. They will give your answers
?,
Sent from my Xoom using xda premium
You're still not helping me, and neither is the other posts; their not specific enough. just tell me how to flash a rom to my /sdcard directory so i can use it in clockwork mod. What commands from my PC do i enter to transfer the .zip???
Hooray!!!
Yay! I've managed to fix my xoom by flashing a stock android 3.0 rom to it. Thank you to everyone involved who took the time to help me, although none of your advice was relevant to the way i fixed it.
For the sake of anyone who was in the same predicamant as me, the steps I took to fix it were:
1) Go to this http://developer.motorola.com/products/software/ link and download the US release (122 mb, down the bottom of first table)
2) Unzip it and extract the contents (should be a set of .img files) to your android-sdk/tools folder
3) Put your xoom into fastboot mode (power on and during the motorola logo repeatedly press volume down until the menu appears in top left of screen, press volume down until you see fastboot, then press volume up, will show starting fastboot protocols)
4) Open a command window in your /tools directory (select tools folder and shift+right click and choose it from the menu that appears in windows)
5) Type the following: fastboot flash boot boot.img
fastboot flash system system.img
fastboot flash recovery recovery.img
fastboot flash userdata userdata.img
fastboot erase cache
6) Once that is done, type fastboot reboot or hold power+volume up (reboots device). you are now done and it should boot into android
IF ANYONE FOUND THIS HELPFUL, PLEASE SAY SO!
Didn't think bricking was possible but I can't seem to get out of CWM. I was running the honeycomb revolver rom and decided to download ota rootkeeper and then revolver parts. After downloading those apps, revolver parts asked to reboot into recovery to flash the updated zip. Did that and I've been stuck in CWM ever since. I even tried factory resetting. It does the reset but then stays at CWM screen. Won't let me boot out of it. Does anyone know what I should do? I can't even power down the device so basically it's sitting at the CWM screen all the time. Ughhhh. Any help would be greatly appreciated.
Sent from my PG86100 using Tapatalk
if you have cwm 5504 , take a look here:
http://forum.xda-developers.com/showthread.php?t=1530337
I am on CWM 5504 but can't seem to access your link. (at least not via Tapatalk app) will take a look later thanks.
Sent from my PG86100 using Tapatalk
ok , its a cwm 5504 known problem , easy solution , dont worry
the thread is : Troubleshooting/Solved] ClockworkMod recovery 5.5.0.4 from Koush
Have you tried cold booting into the OS? Power it on using volume down and power button. As soon as you see the white text just release both buttons and it should attempt a cold boot into the OS. This would let you know if you're still able to access the OS or not.
The above referenced post has all the info you'll need to fix your problem. It'll just be easier to fix if you still have access to the OS.
jinwu57 said:
Didn't think bricking was possible but I can't seem to get out of CWM. I was running the honeycomb revolver rom and decided to download ota rootkeeper and then revolver parts. After downloading those apps, revolver parts asked to reboot into recovery to flash the updated zip. Did that and I've been stuck in CWM ever since. I even tried factory resetting. It does the reset but then stays at CWM screen. Won't let me boot out of it. Does anyone know what I should do? I can't even power down the device so basically it's sitting at the CWM screen all the time. Ughhhh. Any help would be greatly appreciated.
Sent from my PG86100 using Tapatalk
Click to expand...
Click to collapse
Yeah...just go back to Rogue CWM. If all you do is flash Roms like most here on xda ...its all you need. Plus it got external SD mode.
SiNJiN76 said:
Yeah...just go back to Rogue CWM. If all you do is flash Roms like most here on xda ...its all you need. Plus it got external SD mode.
Click to expand...
Click to collapse
All i do is flash roms and don't really understand all the elements of ADB. What is Rogue CWM? From what I read, it seems like I have to use ADB to push either a new rom or a new version of CWM to my device?
jinwu57 said:
All i do is flash roms and don't really understand all the elements of ADB. What is Rogue CWM? From what I read, it seems like I have to use ADB to push either a new rom or a new version of CWM to my device?
Click to expand...
Click to collapse
Team Rouge CWM is a different version of CWM. It's a version that will read from both the internal sd as well as the external micro sd card.
Under normal circumstance you can simply flash a different version of recovery but if you're in a recovery bootloop because of the Koush's CWM 5.5.0.4 version. You'll have to follow partio's link to solve the problems.
Now if you can cold boot into the OS, you can move all the necessary files there without the need of ADB. (Just hook TF up to PC and drag/drop files to internal sd.
If you can't get out of CWM recovery you'll need ADB to push the files to to internal sd.
jinwu57 said:
All i do is flash roms and don't really understand all the elements of ADB. What is Rogue CWM? From what I read, it seems like I have to use ADB to push either a new rom or a new version of CWM to my device?
Click to expand...
Click to collapse
Rogue cwm is just a modified version of cwm. It gets rid of the 100 no options to confirm a flash....and has flash from external SD.
Good luck in getting out of the 5.5.0.4...
I tried cold booting...no go. I guess I'll have to try the ADB method. Thanks for the understanding of recoveries. I have a co worker who is going to try and help me with ADB since i've never used it.
*How will my PC know that I've plugged my tf in, if Im stuck in the recovery mode?(i guess this is probably ADB basics =/)
This is a good thread for setting up ADB.
http://forum.xda-developers.com/showthread.php?t=1071584
ADB required USB debugging to be turn on.
Not sure how one would go about turning that on if you can't get into settings.
IIRC you should be able to get into adb through recovery. I'll have to boot into recovery to remember the way, but I am fairly certain it is possible. Maybe through Advanced->Mounts and Storage?
I FINALLY DID IT!! Cold boot way!!
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.
Rooted and installed twerp 2.6 wiped download files to copy over and flash, but will not mount internal storage tried 2 different systems. stays stuck at updating partion details.
raven.warsong said:
Rooted and installed twerp 2.6 wiped download files to copy over and flash, but will not mount internal storage tried 2 different systems. stays stuck at updating partion details.
Click to expand...
Click to collapse
Do you have adb + the drivers installed? If not, do so now and then adb push the files to the phone. adb will work even if you're in recovery. Should be plenty of write ups on the forum about how to install and set up the required stuff.
is been a long time since I pushed files useing adb Im sure it will come back to me. Should I change to clockworks to avoid this in the future? Why is it not mounting
raven.warsong said:
is been a long time since I pushed files useing adb Im sure it will come back to me. Should I change to clockworks to avoid this in the future? Why is it not mounting
Click to expand...
Click to collapse
It can't be on the Nexus 4. If you don't have the files on your phone it's your only option at this point.
Edit: CWM vs TWRP wouldn't make a difference in this case.
CMNein said:
It can't be on the Nexus 4. If you don't have the files on your phone it's your only option at this point.
Edit: CWM vs TWRP wouldn't make a difference in this case.
Click to expand...
Click to collapse
I pushed the files over and im going to flash now. so i guess the nexus 4 dose not support usb mode so I will all ways need to push with adb? I gess thats the part I still dont understand. I like being able to mount it as a drive in recovery is this supported? if not great. If it is how to I trouble shoot it?
raven.warsong said:
I pushed the files over and im going to flash now. so i guess the nexus 4 dose not support usb mode so I will all ways need to push with adb? I gess thats the part I still dont understand. I like being able to mount it as a drive in recovery is this supported? if not great. If it is how to I trouble shoot it?
Click to expand...
Click to collapse
You cant mount it as USB storage in recovery mode. I normally download the new ROM I want to flash before going into recovery so that I don't have to use adb to push it.
chromium96 said:
You cant mount it as USB storage in recovery mode. I normally download the new ROM I want to flash before going into recovery so that I don't have to use adb to push it.
Click to expand...
Click to collapse
ok thanks I will reflash recovery or start there as long as I know it can be done thats all that matters.