Hi,
I was attempting to install Cyanogen ROM last night and (long story short) ran into a few problems.
I am now in a position where I can boot (but not flash) a recovery image via fastboot. My SD card appears to be corrupt since I can't format it via the recovery menu, and the adb process is confusing me.
I have two basic questions:
1. Can I format the SD card without an SD card reader in my laptop?
2. Can I send a new ROM to the SD card via adb/fastboot?
I believe the answer to both is "yes", but I am having seemingly random issues... for example I cannot restore my Nandroid backup via fastboot (either manually or via GUI); the same goes for a "stock" Nandroid backup I downloaded.
At the moment my phone hangs on the UK Vodafone screen and nothing else (other than fastboot via vol. down+power), and I really need to get it working ASAP.
Thanks for your help.
This is development not Q&A. Post in right forum next time.
Reported
Start asking your questions in the right sub-forum (Q&A) (Theme) or even in (General), or simply search.......Final result will be a ban for you up too 3 days.
Thanks
Thread Trashed!!
Related
Everyone,
I've written this a bunch of times but and putting it in
it's own thread so folks can read and use it.
Memory and Storage:
/sdcard -- internal memory of the tablet
/sdcard2 -- microSD card in the external slot
/usbdisk -- USB key slot
Stock Recovery Info:
Main method: Put your recovery folder and update.zip on /sdcard, turn off the tablet, the press power and volume + to initiate standard recovery.
Second method: Put your recovery folder and update.zip on a microSD card. Edit the command file in the recovery folder with Notepad to change the location from /sdcard to /sdcard2 and save it with the name "command" (NO
.txt or other file extension). Then boot recovery with power/volume + and the OS will use the sdcard (assuming you don't have a live recovery/update.zip file in /sdcard).
Third method: If you can boot recovery to CWM but can't get your ROM to work, go in recovery to the mount menu and go down to the mount USB memory option and choose it. Then plug your connector cable from the miniUSB port to your PC. When you plug into your PC an Explorer window should open and you should have a drive letter representing the G-Tablet (it's G: on mine) on your menu. You now can select that letter and you have access to your tablet memory (/sdcard). I've even had a time or two when not a single file showed!!! I added update.zip and recovery and loaded
a ROM!
The tablet boot process apparently checks /SDCARD. If it doesn't find a recovery file there it does the same check if you have a miniSD external card installed. The large USB slot is not useable for booting or recovery so far as I have determined or read.
I hope this helps you.
Rev
EDIT: I didn't put one fact in here about recovery that everyone should know. When you run a recovery operation, the system deletes the command file so you can't accidentally do it again. If you have to run a recovery or
attempt to load something again, make sure you have a command file in the recovery folder with the correct command in it!!! Sorry I omitted this first time around.
Placeholder
Placeholder
Hope everybody who needs this has seen it. I won't kick it up again.
Rev
Can you also add information about partitioning of /sdcard and why would one need it?
Is there another "hidden" flash memory available for firmware or all mods and custom ROMs go into /sdcard only?
Thanks so much, I thought I'm dead cuz I wiped out everything.
This may have been asked before, but how does one perform a full data wipe w/o using CWM? Thanks.
HackaMathecian said:
This may have been asked before, but how does one perform a full data wipe w/o using CWM? Thanks.
Click to expand...
Click to collapse
You need to use nvflash (nvidia tegra SoC flashing utility). There are alot of posts about it. Do be carefull if you go this route, as even though you will not damage your tablet, it may be difficult to put it back to a bootable state if you don't do it properly.
thanks!
thanks great. simple and to the point. should help people that get confused. thanks again!
Vlad_z,
It has been my experience that when somebody gets boot loops, it often involves a
partition problem. Also, sometimes the G-Tablet does flaky things. I have one I
just shut down. Restarted it with boot looping and had to rebuild.
The three locations listed above are the three memory places you can store stuff
unless you find software that custom sets up something else.
Rev
Os Money:
http://forum.xda-developers.com/showthread.php?t=861950
This thread completely explains the NVFlash process.
Rev
That's kind of odd, my removable sd card ended up with the label ex-sd. Doesn't seem to be messing anything up though.
sixtofive,
I've never seen or heard of that with the stock ROM. Are you running a different ROM?
Some of them do change the directories.
Rev
So simply put, we should copy and backup the recovery folder and update.zip in /sdcard (or tablet storage) and when things get f'ed up, we move the recovery folder and update.zip back into the /sdcard?
Maybe it's just me, but I looked into the recovery that was already in the tablet and there's nothing in it; is that normal? If not, can anyone provide the back up recovery folder and update.zip just in case?
sam,
Recovery is simply a folder which holds a file named "command" in it. Command is a file
that has the command line in it with the command and parameters to "recover" or "load" files onto your G-Tablet.
Sometimes when your tablet gets messed up, you can still use recovery and are lucky. But sometimes the recovery partition gets damaged and then you have to look
for other ways to get in and fix things.
http://forum.xda-developers.com/showthread.php?t=1010943
Many of us keep telling people there is a lot to learn here -- and Android doesn't have
all the stuff built into it Windows does. Nor is Android known for it's great documentation!
If everyone would read all the stickies at the start of the forums, it would provide
probably 80% of everything they need to know.
Rev
If OP also put links to stock ROMs, that would be great
interesting...even though I don't have a microSD card in mine /sdcard2 seems to be a valid directory within "root explorer"
what partition and memory structure should I be seeing on my brand new g-tablet? any suggestion on "mount" and "df" output?
Question, which is the best method or quicker to backup before attempting other rom installs?
Deleting CWM
How would one delete CWM so that the tablet can be returned?
Got my gtablet last evening. Seems there is a lot to learn.
thanks butchconner...
Thanks all the people who are contributing at xda. You are doing a wonderful job. In fact I bought this device because of you ( I think Viewsonic owes you guys a lot. At least they avoided a big loss because of you. )
Two questions:
1) Is it recommended to flash back to stock before changing roms?
2) Is there a link to the stock Rom files that I am missing?
Thanks
So please be gentle, I'm over my head (explains the noob). I rooted and installed rom manager, titanium, busybox, all of the necessary apps. I backed up before I started then installed cyanogenmod 7 from SD card. When I ran I learned I needed to flash the radio i used the one you guys posted here http://forum.xda-developers.com/showthread.php?t=1049542 . It rebooted but was stuck in bootloop. I rebooted into recovery (power and vol down) goes straight into "sd checking" then "no image or wrong image" then asks me if i want to start update. Says:
parsing...[SD zip]
[1] mdm9k
[2] radio_u2
Do you want to start update
Either way it asks to reboot, then goes back into a bootloop
Is this fixable????
Others will have better answers (I'm not a TB user) but I can tell you that if it's turning on, it's not bricked, so I'd chill and figure out how to get that file off the card (don't update twice). Good luck!
Thanks...
That's a good sign then... When I unmounted the SD card it let me get into recovery. But that obviously does me no good when the problem lies ON the SD card
The easiest way to do this would be to try and mount your SD card if it gives you the option. Remove the Ingram file from SD and go from there. Or you can take the SD card out of your phone power back on into recovery and try that then battle pull let your phone reboot delete the file and you should be good to go. I had the problem in the past and that's what I did and it worked like a charm.
Sent from my PG86100 using Tapatalk
battle pull??
Stupid f'n noob... asking a question I SHOULD know the answer to but "Battle pull"? Not sure what file i need to delete or where to delete it from.. Need to speak to me in monosyllabic phrases
Ok I've been trying for two days now to fix a friends nook and can't get anywhere. I know it was rooted before and he tried to go back to stock and in the process formatted everything including boot so it will only boot from a cwr sdcard. When it does boot i am unable to install anything from the card because it will not mount the card. I have attempted everything i can find with adb, adam outlers ubuntu recovery, and different cards of different sizes and different cwr files. I have no clue what to do now. all i can do is either boot to cwr sdcard of boot.img sdcard to the "n" screen but then i have no dab access.
What can I do?
Please Help
Update: I've got it repartitioned and booting on it owns now but only to the "n" screen with no sd card installed. The only thing I'm am having a problem with is getting the system.img file dd'd onto the sd card because it keeps giving me a protocol error. Have tried a few different things but either get "no more room left on device" or protocol error. I also don't have the serial number for the device either. by the way it's a nook color.
Please use the Q&A Forum for questions &
Read the Forum Rules Ref Posting
Thanks ✟
Moving to Q&A
Hello all, as the title says, I'm new, both to the site and android rooting in general.
I used the latest sunshine to s-off, although now i read that that wasn't necessary. What I'm trying to do is get rid of the bloatware on my phone and gain a little more control over the device itself. It is a verizon phone on the tmobile network and things like verizon vm and the verizon cloud apps and such are really just taking up space.
So the question is, now that I have s-off'd the device, where do I go next? I managed to get TWRP on there, but I just don't know where to go from there. Yes, I searched the site, Yes I searched Google, and yes, I prayed to the Skating Droid of Legend.
Any advice would be great. All of the information i have found on my own is about 2 years old.
If you already S-OFF'd it, and even got twrp going, I recommend the only thing left to do is downloading a ROM from the Android Development section (in ZIP format), saving it to your phone's internal memory or external sd card, then flashing it via twrp. That way you will have a rooted, pre-de-bloated phone. In my case, the ROM I liked best and that worked fine for me was S-ROM-JW-5.2.5 (doanloaded from this thread http://forum.xda-developers.com/ver...ment/romthe-worlds-100-m9-1-32-401-8-t3065304).
I personally selected "Global" during the flashing options, as I do not use Verizon network (I live in Brazil currently). But even so, you can change to/from Global and Verizon (and something else) in the Android settings after you are already set up.
To flash, first place the ZIP file in your phone (do not unzip it). Either internal storage or external sd-card. Then turn the phone off, unplug it (make sure you have plenty of battery like 40% or more just to be safe). Then turn the phone back on booting into twrp (power + down vol, then select Recovery, then Power). Then select "Flash ZIP" and navigate to your ROM ZIP file select it and follow the prompts. Choose "full wipe" when prompted (this will only wipe internal storage system files and apps and such and not your external sd card). After flashing finishes, just let the phone reboot (you can select Reboot while still in the twrp recovery mode).
Do not panic during first boot, it takes several minutes in the HTC logo (like some 5 or 10 minutes) until Android itself shows up and starts building itself into your phone and booting up properly.
Please proceed carefully and just to be safe, before flashing the ROM, make a full BACKUP (theres the Backup utility inside twrp) and save the backup to your external sd card or PC. That way you can recover using that backup if needed (but you should be ok).
gamekill said:
If you already S-OFF'd it, and even got twrp going, I recommend the only thing left to do is downloading a ROM from the Android Development section (in ZIP format), saving it to your phone's internal memory or external sd card, then flashing it via twrp. That way you will have a rooted, pre-de-bloated phone. In my case, the ROM I liked best and that worked fine for me was S-ROM-JW-5.2.5 (doanloaded from this thread http://forum.xda-developers.com/ver...ment/romthe-worlds-100-m9-1-32-401-8-t3065304).
I personally selected "Global" during the flashing options, as I do not use Verizon network (I live in Brazil currently). But even so, you can change to/from Global and Verizon (and something else) in the Android settings after you are already set up.
To flash, first place the ZIP file in your phone (do not unzip it). Either internal storage or external sd-card. Then turn the phone off, unplug it (make sure you have plenty of battery like 40% or more just to be safe). Then turn the phone back on booting into twrp (power + down vol, then select Recovery, then Power). Then select "Flash ZIP" and navigate to your ROM ZIP file select it and follow the prompts. Choose "full wipe" when prompted (this will only wipe internal storage system files and apps and such and not your external sd card). After flashing finishes, just let the phone reboot (you can select Reboot while still in the twrp recovery mode).
Do not panic during first boot, it takes several minutes in the HTC logo (like some 5 or 10 minutes) until Android itself shows up and starts building itself into your phone and booting up properly.
Please proceed carefully and just to be safe, before flashing the ROM, make a full BACKUP (theres the Backup utility inside twrp) and save the backup to your external sd card or PC. That way you can recover using that backup if needed (but you should be ok).
Click to expand...
Click to collapse
That's extremely helpful, thank you very much.
It turns out that Verizon is much better in my area than T-Mobile, so I wont be removing all the stuff I originally wanted to, however anything that gives me more options and power should I choose to wield it, is a welcome addition.
Thanks again.
Hello All. I’ve run into an issue with my new Moto G4+. I rooted the phone a couple of weeks ago and all was well with that. I downloaded the AOKP rom last Friday and was going to flash it over the weekend. To my surprise, TWRP does no see my external SD card so I can’t do a backup. The internal storage does not have enough space to backup. I have the 16gb model. I can see/use the SD card with no problem when the phone is running. I’ve searched the forums for a solution, but the only thing I’ve found is to format the SD card as internal storage. However, folks seem to be really, really divided on this solution. I really want to flash AOKP, but I need to do a Nandroid backup first. I tried doing an on-line backup with the TWRP app, but it doesn’t provide me with an MD5 for verification. Any help with getting TWRP in recovery mode to see the SD card would be greatly appreciated. TWRP file manager and terminal allow me to see the card (sdcard1 is its name in TWRP recovery), but it does not show up for "select storage" or "mount" options.
Thanks.
Hi there,
Please read the Sticky threads for XDA Assist. Our purpose here is to guide new members to the correct section for their issues. As a Senior Member, you should be able to use the search features provided to you to find the correct section to post your question.
Thanks for understanding.
Thread closed.
Razvan
Forum Moderator