Today I tried to flash the CyanogenMod 9 Nightly 06-30-12, coming from Build 35 of AOKP and after factory resetting and clearing Dalvik I went to install the zip and while flashing it I got a build-prop related error!
All of my NANDROIDS gave me a data error when flashing and now I am pretty f'd! I /really/ need to fix this ASAP but have no idea how.
-Samsung Galaxy Tab 10.1 Wifi-
-CWM 4-
On a second note, does anywhere know where I can get my screen replaced for cheap? I dropped my tab a few months back and the screen got MAJOR cracked, though it still does technically work (I still use the screen, it works but it's cracked is all...) and after calling Samsung and waiting for over 1 and a half hours they told me they wanted $150 to fix it, which if I recall is about half of what I payed for it anyway...
To be honest, I'd be lying if I said I was happy with Samsung over all.
I mean, bad customer support, the proprietary connection cable, and lack of official updates (along with the ugly TouchWiz that I'm not sure /who/ likes ) don't make me that happy...
Anyway, can anyone help me please?
Thanks in advance!
Update your recovery: http://droidbasement.com/db-blog/?p=2655
If you have a GT-P7510 (p4wifi), in this post are flashable zips (with your current recovery) of CWM and TWRP, in case you prefer this method: http://forum.xda-developers.com/showpost.php?p=28051448&postcount=29
After that, flash your ROM like always.
Yeah, thanks, were it so easy. I fired up ODIN multiple times, no matter what, unsuccessful. Like always, my computer would not recognize my tablet. Yes, I have the bloody Samsung drivers, yes I've tried reinstalling them (several times in the last few months), yes I've tried using different USB ports! And what? Nothing. Nothing at all. For the last few months I have not been able to transfer movies/music to my tablet via file transfer and I can't even get the stupid odin download thing to work. To be honest, I really am pissed off with this broken pile of trash. Would trade it in for a similar tablet any time.
Did you try any of the flashable zips for a new recovery?
About the USB, it sounds like a different problem, but for the file transfers, are you sure you have MTP selected? (answer #5 --> http://forum.xda-developers.com/showthread.php?t=1642009 )
If you haven't tried it yet, you could use a different computer, another OS (some Linux distro and check that adb works), change the USB cable.
I can't use a flashable zip since I can't copy files onto the tablet >.>
Also, yes, for file transfers I /do/ have MTP selected always and it doesn't work eitherway.
Essentially, I am stuck with a $300+ ugly and broken thing that I can only use as a paperweight for the huge mess I call my desk. Yay.
>Rage sidenote; Samsung, go take the money I payed for **** and shove it.
And I guess you don't have your old ROM (AOKP build 35) in your tab.
Try with adb (in recovery), but if you can't get a working USB connection (using other computers or OS), maybe there's something physically wrong with your tablet.
No, I don't. I'm stupid enough to delete the ROM zip after flashing it to save space on the tablet...
How do I do this ADB thing? I've heard of it before alot but never used it or looked into it...
Read this: for windows -> http://forum.xda-developers.com/showthread.php?t=1387527 , for Ubuntu -> http://forum.xda-developers.com/showthread.php?t=921169
After everything is installed, boot your tablet into recovery and try running in your command line application (CMD for windows):
adb devices
If it shows that a device (and ID number and the actual state, e.g. recovery) is connected, your golden!
If you have another android device, try it too, to be sure that is working.
To transfer a file the command is
adb push /path/to/file /path/in/tablet
In windows I guess is something like this:
adb push C:\path\to\file /path/in/tablet
so I'd do something like
adb push C:\ADB\CWM-5.5.0.4-p4wifi.zip mnt/sdcard/ ?
Im dling the ADB files right now
adb push C:\ADB\CWM-5.5.0.4-p4wifi.zip /mnt/sdcard/
You need the slash at the star and end of the path of the tablet.
While installing PdaNet it failed, said it couldnt connect through to the device or w/e
Also,I don't recall having ADB on when I had the tablet. I might've but I don't think I kept debugging on for the general time...
This is so frustrating >.>
I'm not sure about that error in PdaNet, I can help you with adb but I don't use Windows, so there's things I can't test.
If you didn't select ADB debugging in your ROM it doesn't matter, you're doing this from recovery.
BTW, do you have other android device?
adb seems to be working and copying, but I can't find the file in Recovery while doing choose a zip to apply!
Yes, I have an LG Optimus V on Virgin Mobile running tdm's AMAZING Quattrimus Alpha 10 on Ice Cream Sandwich/ Android 4.0.4
this is what I get
C:\Users\Mikoyan Gurevich\Desktop\LG Drivers>adb devices
List of devices attached
43C800340009517 recovery
C:\Users\Mikoyan Gurevich\Desktop\LG Drivers>adb push C:\CWM-5.5.0.4-p4wifi.zip
43C800340009517\sdcard\download
1328 KB/s (4147569 bytes in 3.048s)
C:\Users\Mikoyan Gurevich\Desktop\LG Drivers>
If you connect your phone and execute
adb devices
What's the output?
If you do the same with your tablet, what's the output?
with the tablet it's
C:\Users\Mikoyan Gurevich\Desktop\LG Drivers>adb devices
List of devices attached
43C800340009517 recovery
with my phone it doesn't wanna show up in Recovery or not.... Hmm.
Well, it shows fine, then you should be able to transfer the files
First, in your recovery, go through the steps to install some zip file, but just go as far as selecting the directory, then go back
Now in your PC try running something like this, change your path in windows:
adb push C:\CWM-5.5.0.4-p4wifi.zip /sdcard/
The in your recovery, select install and should show there. The thing is that most likely the sdcard wasn't mounted in your tab
Edit, to mount your sdcard in recovery do: mounts and storage > mount /sdcard > Go back
The do the transfer in your PC.
Hmm
While I was holding it to my gut, pushing the end of the cable into my stomach (It was the only way to get it to be recognized) I fooled around and went into download mode, hoping that on the contrary I could do that, turn it off, and when I went back into Recovery it would be there when it finally said the cable WAS connected and then I rushed to open Odin and wrote it through, and it frickin' wrote CWM v5 right on and it worked, I'll be damned!
Maple, I can not thank you enough for helping me with this, I am in great debt.
You're welcome, I'm glad it worked. Knowing how to use adb is really useful. And now you know that something is wrong with your cable.
Or in the connector pins or w/e of the tablet... The cable works fine for charging though....
You are my savior, bro.
Related
I have messed up my tablet, my tablet is rooted i went and replaced couple of the system apps by using root explorer and that completely made my system go crazy so i then did a system reset and now i keep getting unfortunately, setup wizard had stopped and i cant go anywhere from there. my boot loader is not unlocked. is there any way to reinstall the stock ROM like from adb or something. please any help is appreciated. I have also tried to reset the rom by holding down power and vol down and wipe data from there, and still the same thing. when i plug it in the computer i am still able to see the transformer so i can transfer files to and from the transformer i just cant get it passed the welcome screen.
spencerj2001 said:
I have messed up my tablet, my tablet is rooted i went and replaced couple of the system apps by using root explorer and that completely made my system go crazy so i then did a system reset and now i keep getting unfortunately, setup wizard had stopped and i cant go anywhere from there. my boot loader is not unlocked. is there any way to reinstall the stock ROM like from adb or something. please any help is appreciated. I have also tried to reset the rom by holding down power and vol down and wipe data from there, and still the same thing. when i plug it in the computer i am still able to see the transformer so i can transfer files to and from the transformer i just cant get it passed the welcome screen.
Click to expand...
Click to collapse
Does adb on your computer see your device, since it's not fully booted?
Connect your tablet with USB cable.
On your PC, in the same folder as your adb files, open a command prompt in that location (shift+right click).
Type "adb devices" and see if yours come up as connected.
I doubt it will though, sounds like how I bricked my first prime, when I pushed a deodexed framework to it.
Might also want to try looking in the Dev section, under the how to unbrick your device thread, and see if you can attempt to revert to a different firmware via installing a blob file, but if you can't access your internal or external SD cards, to read/write the blob file (b/c your device won't fully boot) you may be SOL.
Next time unlock the boot loader first an make a nandroid backup, before messing w/ system files, that way you can easily restore. If your still in your 30 day window of purchase, you might consider a quick return/swap... would be the eaisest thing to do.
Sent from my CM7 Atrix 4G
no adb does not see my device but i can access the internal sd card
Swiftks said:
Does adb on your computer see your device, since it's not fully booted?
Connect your tablet with USB cable.
On your PC, in the same folder as your adb files, open a command prompt in that location (shift+right click).
Type "adb devices" and see if yours come up as connected.
I doubt it will though, sounds like how I bricked my first prime, when I pushed a deodexed framework to it.
Might also want to try looking in the Dev section, under the how to unbrick your device thread, and see if you can attempt to revert to a different firmware via installing a blob file, but if you can't access your internal or external SD cards, to read/write the blob file (b/c your device won't fully boot) you may be SOL.
Next time unlock the boot loader first an make a nandroid backup, before messing w/ system files, that way you can easily restore. If your still in your 30 day window of purchase, you might consider a quick return/swap... would be the eaisest thing to do.
Sent from my CM7 Atrix 4G
Click to expand...
Click to collapse
spencerj2001 said:
no adb does not see my device but i can access the internal sd card
Click to expand...
Click to collapse
If you can access the internal card, its weird that adb can't see your device... oh well... try reverting to a earlier/different firmware via a blob. See thread in dev section.
Sent from my CM7 Atrix 4G
i did exactly the same mistake: i uninstalled some system apps (the asus preinstalled apps, with titanium) without unlocking the bootloader, and after a wipe from the stock recovery i'm not able to go beyond setup configuration, it always stops. but i can see and use internal and external memory from my computer. did you find a solution?
Welp, after spending over 26 honest-to-God hours researching a "cure" for this, I am still without a solution. I hope a kind soul will be able to guide me to the light, because I have been unable to find it on my own.
I am going to try to be as through as possible, if for nothing else than doing a mental checklist to see if I missed some obvious step along the journey. Also, maybe a keen observer will be able to spot what I'm doing wrong.
So,
My Asus Prime is bricked. I'm stuck on scenario 3 (according to this post:http://forum.xda-developers.com/showthread.php?t=1514088&)
In chronological order, here's what happened:
1. I'm running Virtuous Prime 1.0
2. I flash ClockworkMod Recovery Touch v5.8.1.8
3. I rebooted into recovery and wiped data/factory reset, cache, dalvik cache
4. I performed a backup of my old ROM
5. I flashed a new ROM, then hit 'reboot system now'
6. I'm stuck at the Asus logo screen; Android won't boot.
I am able to access recovery and activate Fastboot mode; definitely scenario 3.
Then, also in chronological order:
1. I restarted the tablet, pressed the up volume key and accessed the other menu with 3 options
2. I hit the 'wipe data' option
3. Try to boot Android
4. Still stuck at the 3 option screen
From what I read, this situation is likely the result of clockworkMod Recovery flashing a bad kernel. Supposedly, it can fixed by flashing a 'good' kernel via fastboot, which requires both a "stock kernel" and a more recent clockwork mod recovery image.
I downloaded the SDK package and downloaded pretty much everything, including the USB drivers. I downloaded a stock kernel called stock_9.4.2.21_kernel-signed and a CWM recovery image and placed them inside the "tools" folder.
I opened a command window and while having the tablet plugged in, typed 'adb devices'. I get 'List of devices attached' but then a blank space.
Here's what happened next:
1. I re-plugged in the tablet in Recovery mode to my AMD X64 Windows 7 PC and got an "USB device not recognized" message.
2. I went to Device Manager and under "Universal serial bus controllers" I see a yellow triangle mark besides an "unknown device" option.
3. Right click on "unknown device" and try to update the drivers manually using the Universal_Naked_Driver_Beta_0.6.1
4. When I select the folder in which the drivers are located Windows gives me a message of "the best driver software for your device is already installed". Back to step 3.
5. I try "let me pick from a list of device drivers on my computer" and hit "have disk option"
6. Upon choosing the android_apxusb file inside the universal naked drivers folder, I get the following error: "the folder you specified doesn't contain a compatible software driver for your device (...) make sure it is designed to work with Windows for x64-based systems."
7. Try again this time choosing file android_apxusb; same error.
I heard that some Windows 7 x64 users are having issues installing drivers; that may be my case too. I, however, don't have access to any other Window or Macs or Linux PCs in my house. Still, if this is the issue, then I might try redoing things in a different PC at a friend's house or something.
Bottom line? I think I know what to do, but I can't install the universal naked (nor the official Asus Prime) drivers. What now? Is there an easy fix for Brick scenario 3?
I have read God knows how many discussions on the subject, but I haven't been able to find a solution to my issue. I got no support from Freenode #asus-transformer; some ops were even downright rude. Any help is greatly appreciated.
For what is worth, I'll be donating $50 to whoever is able to help me navigate through this issue and get my tablet back and running.
Thanks again for reading this far.
TL;DR: I bricked my Prime and I'm stuck in scenario 3. I will donate $50 dollars to whoever can help me unbrick it.
Hey,
try to get a Live CD like Ubuntu.
Get the Linux files from the ViperMOD thread. It includes the "adb" executable.
Try to get ADB running there.
Go to the freenode IRC Channel "#asus-transformer" on Freenode (http://webchat.freenode.net/?channels=asus-transformer) and ask for help like described in the unbrick thread!
Greetz
Edit: No need for donate!
hanzo001 said:
3. I rebooted into recovery and wiped data/factory reset, cache, dalvik cache
4. I performed a backup of my old ROM
Click to expand...
Click to collapse
In that order? So you backed up an empty rom?
You don't mention; do you have valid nandroid backup? Can you restore it?
Do you have a rom zip on your device? What happens if you wipe and re-flash?
I would suggest a couple of options.
I notice that you have not once (according to what you have written) formatted /System if you still have a good ROM on your memory card that is flashable I would format all partitions in recovery /System, /Cache, /Staging and /Data then reflash the ROM.
You could also try an advanced restore and flash only the boot image from your nandroid.
Also, I have to agree with chrischdi, there is no need for a bounty for this. Your problem is one of the reasons we are all here in the first place.
Thanks for your answer; I'll answer yours
djmcnz said:
In that order? So you backed up an empty rom?
You don't mention; do you have valid nandroid backup? Can you restore it?
Do you have a rom zip on your device? What happens if you wipe and re-flash?
Click to expand...
Click to collapse
1. Yes, in that order; I backed an empty ROM
2. No, I don't have a valid nandroid backup (go figure; just this single freaking time I forgot to backup before wiping data/cache/dalvik cache)
3. No other ROM on my device. I had a new ROM when I performed the flashing, but when I got to the point where I hit "deleate data" in the 3-option menu, I lost everything on the SD card
4. When I wipe and reflash I'm stuck on the same loop. Maybe flashing a 'good' ROM will fix it; the issue is, my PC doesn't know what I'm plugging in when I connect the tablet to it.
Thank you for your support
Thank you, I'll try a Live CD. I'm downloading now even as we speak.
When that's finished, I'll grab the Linux files.
I guess that sorts of confirms my hypothesis that my main issue is with Windows... *sigh* WINDOWS!
I tried getting help from freenode's #asus-transformer in the past, but... lets say that on the overall my experience could have been better. I'll try again later tonight, where hopefully I'll be able to talk to RaYmAn, a volunteer in the original Diamonback post who is offering supports to users in my specific situation.
By the way, thanks for pointing me with a clickable link to the IRC chat; I've never used IRC before in my life, and getting it to work, dumb as it may sound, took me quite to figure out. Thank you again for your help and support!
chrischdi said:
try to get a Live CD like Ubuntu.
Get the Linux files from the ViperMOD thread. It includes the "adb" executable.
Try to get ADB running there.
Click to expand...
Click to collapse
Thank you for your answer. It is really nice to have a helpful person around; Like I mentioned in my op, my experience on freenodes' #asus-transformer chat was a bit... discouraging. I figured most would want some form of payment for their time, but here you both are, proving that there is kindness in this world.
I'll address your comments:
1. I did wipe /System; after NOTHING I tried on recovery worked, I did manual wiping of everything, trying to boot each time; similar results.
2. I do not have a good ROM on the memory card. Before doing the 'wipe data' from the 3-option menu, re-flashing a good ROM did no good nevertheless. From here is where I started suspecting that it was the fault of CWM not flashing a proper kernel.
3. I tried the advanced restore as well, an like in #1, I tried rebooting each time, just to make sure it would work. But it didn't.
Thank you again for your support. It feels great to know there's someone backing you up out of the goodness of their heart.
Right now I'll try to redo my steps from a Live CD Linux environment; hopefully that'll work. Freaking Windows...
Doktaphex said:
I would suggest a couple of options.
I notice that you have not once (according to what you have written) formatted /System if you still have a good ROM on your memory card that is flashable I would format all partitions in recovery /System, /Cache, /Staging and /Data then reflash the ROM.
You could also try an advanced restore and flash only the boot image from your nandroid.
Also, I have to agree with chrischdi, there is no need for a bounty for this. Your problem is one of the reasons we are all here in the first place.
Click to expand...
Click to collapse
Thank for your support, guys
I just wanted to shout out a big thanks to the great people who have offered me suggestions regarding this issue. I'll re-do my steps this time from inside the Live CD version of Ubuntu later tonight, and I will update.
Best regards,
me
hanzo001 said:
I just wanted to shout out a big thanks to the great people who have offered me suggestions regarding this issue. I'll re-do my steps this time from inside the Live CD version of Ubuntu later tonight, and I will update.
Best regards,
me
Click to expand...
Click to collapse
Hope it works out for the best, life is better with a little Nix in it.
What if you load a rom like aokp onto an external SD then flash that? That flashes everything you would need. Then if you want to back to virtuous you could restore the stock boot img. Im tired and I'm probably not understanding the issue correctly so forgive me if that is indeed the case.
Sent from my MB870 using xda premium
CadenH said:
What if you load a rom like aokp onto an external SD then flash that? That flashes everything you would need. Then if you want to back to virtuous you could restore the stock boot img. Im tired and I'm probably not understanding the issue correctly so forgive me if that is indeed the case.
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
You cannot use an external SDcard with any version of CWM for the Prime.
CadenH said:
What if you load a rom like aokp onto an external SD then flash that? That flashes everything you would need. Then if you want to back to virtuous you could restore the stock boot img. Im tired and I'm probably not understanding the issue correctly so forgive me if that is indeed the case.
Sent from my MB870 using xda premium
Click to expand...
Click to collapse
Thanks for the thought. I tried that too; for some reason, ClockworkMod Recovery won't read the SD card at all!
Linux
[Update]
In general, this could be going better.
I finally got Ubuntu.
I plugged in the tablet while (the tablet is) on recovery mode, and nothing happens.
I was expecting a pop-up menu, or a notification somewhere acknowledging that I connected a device to the PC, but nothing. I'm just going to assume that Linux somehow knows.
I then downloaded the Android SDK for Linux, unziped, and there's no executable file inside. I'm supposed to download the rest of the file via the terminal, apparently, but this one doesn't work like its Windows counterpart either, so I have no clue what to do now.
Jesus...
Bottom line: I'm in Linux, I downloaded the Android SDK, the universal naked drivers and a stock kernel. Now what?
Try to get ADB running in the recovery mode.
In the files of ViperMOD are the executables. Just open up a console / shell and go to the directory via the "cd" command.
Then in the ViperMOD directory execute "sudo ./adb shell" to try the adb connection.
If the adb connection is ok, mount the sdcard via Recovery Menu and then push a file / rom to the sdcard.
For example with the command:
"sudo ./adb push /media/rom.zip /sdcard/"
(I don't know if this are the correct paths.)
Greetz
Thank you, Chris.
While on the terminal, I'm inside the viperMOD folder. Whenever I try execute "sudo ./adb shell" I get this: "sudo ./adb: order not found"
The tablet is plugged in, and in recovery mode.
I haven't installed Java nor the Android SDK because I haven't figured out a way to do it --why can't Linux be double-click action-oriented? *sigh* Anyway, does not having those things installed have something to do with the answer I'm getting from the Terminal?
If so, how in the world do I install them?
I'm never using Touch Recovery again, my word.
Thanks in advance.
Hey,
are you sure that there is "order not found?"
Try the command "ls" to see what files are available. If there is one, called "adb" you are in the right directory. If there is no "adb" then you have to move to the right directory.
Maybe you could try a "chmod +x adb" first and then execute "sudo adb shell" or such if you are in the right directory.
This is going to sound like a stupid question and sorry if it does. but you can access clockwork still right? what happens when you try to flash back your backup? This is important because I had an error sort of like yours that no one could solve here want to make sure its what happened to me. When i tried to restore the original rom it would get to the part where it was restoring data partition and then error on me reading file or something like that. If thats what you see i know the answer. or at least how i fixed mine.
push a rom
Read NIlsonf post about how to adb push a rom to cwm, you get a stock rooted rom
And adb push the blob file, then run the dd command, unmount staging mount data.
This is what fixed mine, and it looks like it fixed nilsonf's also.
Was this ever resolved? I have the same issue and it looks like I've been through many of the same steps as you've gone through. If you were able to do anything to fix it, please let me know.
I would even up the reward to $100.
Just thinking
Why dont you get someone elses CWM backup and adb push it to the device and restore it from that?
Wifi and OTA updates were working fine before I rooted my kids' Nabi 2. I never tried an OTA update until after I rooted them, which doesn't work (I tried 2.1 since it said it was available). I followed the directions at http://forum.xda-developers.com/showthread.php?t=2041224 and it worked great to restore to stock 1.9.12, but wifi doesn't work now (mine could have been 1.9.37 originally). I tried the "wifi fix" mentioned, but there are still no wifi networks displayed like there were earlier today. I do not have a micro SD card to install the updates from, as mentioned in the replies. If I were to buy one, can I just put the OTA updates from http://forum.xda-developers.com/wiki/Fuhu_nabi_2 on it, and install from it somehow?
I tried to copy fuhu_nabi2_138139_1937_ota.zip to the device and install through the recovery kernel, but got an "assert failed" error. Any ideas as to what can be done to at least update this to 1.9.37, or maybe do a "stock install" of 1.9.37 instead of 1.9.12 so I have a better chance of wifi working? Please be specific as to what I need to try and in what order...some of the tools I tried seem to be inconsistent in results (Nabi Lab was latest I used). I am comfortable using what t499user has to go back to 1.9.12, I just wish I could use the same method to go to something newer...
I had the wifi problem this past spring. I backed up all my apps and data then flashed back to stock with NabiLab. Re-rooted and all was fine again.
You should also be able to use TWRP to flash back to stock. See TWRP thread http://forum.xda-developers.com/showthread.php?t=2074501
Some more info that may help http://forum.xda-developers.com/showthread.php?t=2248495
This experience is only my second time with TWRP and updating the Nabi. I've previously tried reverting to the backup in the "stockunrooted" folder, which is where I think the original was. I now recall that this had been updated to 2.0 using OTA before it was rooted.
Using TWRP, I tried reverting back to stockunrooted just now. Wifi works again, but OTA still does not (2.1 downloaded and seemed to install quicker, but upon reboot all I saw was "an error installing" message and it went directly to TWRP (where I just rebooted and it went to the Nabi screen). I am not sure what else to try. There is also an "oem" folder available for restore in TWRP, but that is the one created using t499user's process to go to 1.9.12. I initially used t499user's tutorial because I thought maybe something was wrong with the stockunrooted backup.
I have a few questions. Is updating TWRP to the latest version important? If yes, how do I do that (I've seen http://forum.xda-developers.com/showthread.php?t=2074501 before, but still not sure how to download/install 2.6.1.0)? If this has been reverted to "stock" and OTA updates still don't work, how do I apply them manually (from http://forum.xda-developers.com/wiki/Fuhu_nabi_2)?
I just noticed that the "stockunrooted" backup has things that aren't stock. Internal Storage has an Android folder with com.google.apps subfolders, etc. I am back to the original problem, and that is going to "stock" (something other than 1.9.12).
Cool, I figured out how to install 205to210.zip (TWRP 2.3.3.0)...For anyone interested, I copied the zip to Nabi/Internal Storage/TWRP, booted while holding +, pressed - to 'recovery kernel,' pressed + to choose it, then chose install. There is one more update I tried (2127stock.zip), but I get a flash error and it did not install. Considering (so far) I cannot get back to "stock unrooted" and use OTA updates, does anyone know how I can install this?
Wait...maybe there isn't another update. http://forum.xda-developers.com/wiki/Fuhu_nabi_2 has "Update 2.0.5 to 2.1.27" as the latest. I think it is working OK. Back to my original question(s), what is the process to install an updated version of TWRP and a "stock version" of something other than 1.9.12? Just trying to get the whole process understood...If I can simply use t499user's tutorial with different images, that would be rad to the max.
brentford said:
Wait...maybe there isn't another update. http://forum.xda-developers.com/wiki/Fuhu_nabi_2 has "Update 2.0.5 to 2.1.27" as the latest. I think it is working OK. Back to my original question(s), what is the process to install an updated version of TWRP and a "stock version" of something other than 1.9.12? Just trying to get the whole process understood...If I can simply use t499user's tutorial with different images, that would be rad to the max.
Click to expand...
Click to collapse
Yes its probably wise to update to TWRP 2.6.1.0. Get the file
Download
Follow "Method 3" here
http://forum.xda-developers.com/showthread.php?t=2074501&highlight=nabi
As for getting a stock image. You were using the zips here http://forum.xda-developers.com/wiki/Fuhu_nabi_2
You dont "Install" those zips. You need to extract the contents. boot.win, system.win, etc. and put them in the TWRP folder.(TWRP/BACKUPS/XXXXXX/folder)
Make a folder called 2127 put the filed in there. Then "Restore in TWRP. Then you should have a stock system. Same goes for 1937stock.zip 205stock.zip
If you have questions ask away.
Thank you all! I think I am getting it. Since I am reading (and had first hand experience) that Google Play isn't working very well with 2.1.27, I will go back to 2.05. That should keep the kids happy. I will let you know if I have more questions.
Oops...I broke something. I have two Nabis. I accidentally restored one using the device ID path of the other. I used "adb push c:\nabi\fuhu_nabi2_v1912_system.ext4.win /sdcard/TWRP/BACKUPS/015d2bc264340217/oem/system.ext4.win" for both. The incorrect one booted, but I noticed that the apps aren't the same. I tried to use TWRP again, but it is not recognized by cmd "adb devices" and I get "error: device not found" when trying "adb reboot-bootloader." I also tried whatever restore option there was in the settings, but it is the same result...Any options?
brentford said:
Oops...I broke something. I have two Nabis. I accidentally restored one using the device ID path of the other. I used "adb push c:\nabi\fuhu_nabi2_v1912_system.ext4.win /sdcard/TWRP/BACKUPS/015d2bc264340217/oem/system.ext4.win" for both. The incorrect one booted, but I noticed that the apps aren't the same. I tried to use TWRP again, but it is not recognized by cmd "adb devices" and I get "error: device not found" when trying "adb reboot-bootloader." I also tried whatever restore option there was in the settings, but it is the same result...Any options?
Click to expand...
Click to collapse
Google play won't work with 2.1.27 unless you delete some apps from /system/vendor/apps before installing gapps
As long as you have the bootloader(with the 4 options boot normal, fastboot, recovery kernel, forced recovery) and working USB port there are always options.
So is ADB not working in TWRP or in Android or both? It's probably best to copy boot.emmc.win, data.ext4.win and restore those too since you have done so much stuff. Boot contains you kernel, and data the apps. You will be back to a stock tablet with no game saves or anything so make sure you got off the tablet what you needed
I don't see a /system/vendor folder using TWRP file manager now...is that only when 2.1 is installed? How much do I need to remove, and are there any known problems with gapps in this case?
I fixed whatever problems I had. (Yes, I still have the bootloader.)
I am not that familiar with this, but let me explain what I have done. As before, I was using ADB/fastboot instructions from http://forum.xda-developers.com/showthread.php?t=2041224 (Windows 7). Both tablets' Internal Storage were recognized by Windows, but only the other one (with correct device ID 015d2bc264340217) was recognized when using ADB. That is how I was updating between Nabi 2 versions before.
Tablet 1:
C:\adb>adb devices
List of devices attached
015d2bc264340217 device
Tablet 2 (normally 015d24a7f41c1c15):
C:\adb>adb devices
List of devices attached
At one point, both devices started an endless loop when booting (shows the "Please wait while Nabi initializes" message for a split second and boots again). It may have been something with the way I installed the OTA updates, but I figured that it had to be something wrong with System so I wiped absolutely everything from within TWRP and I followed t499user's instructions for Windows cmd line (for going back to 1.9.12). Everything is good now, but I don't want to upgrade to 2.1 if gapps has any problems...
brentford said:
I don't see a /system/vendor folder using TWRP file manager now...is that only when 2.1 is installed? How much do I need to remove, and are there any known problems with gapps in this case?
I fixed whatever problems I had. (Yes, I still have the bootloader.)
I am not that familiar with this, but let me explain what I have done. As before, I was using ADB/fastboot instructions from http://forum.xda-developers.com/showthread.php?t=2041224 (Windows 7). Both tablets' Internal Storage were recognized by Windows, but only the other one (with correct device ID 015d2bc264340217) was recognized when using ADB. That is how I was updating between Nabi 2 versions before.
Tablet 1:
C:\adb>adb devices
List of devices attached
015d2bc264340217 device
Tablet 2 (normally 015d24a7f41c1c15):
C:\adb>adb devices
List of devices attached
At one point, both devices started an endless loop when booting (shows the "Please wait while Nabi initializes" message for a split second and boots again). It may have been something with the way I installed the OTA updates, but I figured that it had to be something wrong with System so I wiped absolutely everything from within TWRP and I followed t499user's instructions for Windows cmd line (for going back to 1.9.12). Everything is good now, but I don't want to upgrade to 2.1 if gapps has any problems...
Click to expand...
Click to collapse
Before browsing with TWRP file manager you need to go to the "Mount" tab, put an X in system. Then go to file manager.
Probably have to remove around ~50MB, maybe a bit less. Lots of people choose Wings, but obviously Wings is something some kids love. Really depends on the user.
When you flash stock, it often reset USB debugging to off in Android settings, if you flashed data too.
USB debugging is still on. Do you know anything about whether or not gapps has any problems with rooted Nabi 2.1? You have been a great help!
I didn't realize what would happen until it broke, but what I tried to do was remove apk files prior to upgrading to 2.1. I have copies of them on Internal Storage and locally, but I don't see a way to copy them back to /system/vendor/app using TWRP (tried mounting everything except external storage, which isn't selectable; internal storage isn't selectable, located to the right). Is there a way to do it, or do I have to go back to 1.9.12 and start over?
brentford said:
I didn't realize what would happen until it broke, but what I tried to do was remove apk files prior to upgrading to 2.1. I have copies of them on Internal Storage and locally, but I don't see a way to copy them back to /system/vendor/app using TWRP (tried mounting everything except external storage, which isn't selectable; internal storage isn't selectable, located to the right). Is there a way to do it, or do I have to go back to 1.9.12 and start over?
Click to expand...
Click to collapse
The only problem gapps has is there isn't enough room for it with a stock 2.1. You have to remove something.
Mount everything in TWRP. Go to file manager. /data/media is internal storage. You will find your files. Copy them back to /system/vendor/apps. Might have to set permissions.
Thanks! I copied from Windows using adb, but I got the same asset error (two of the files no longer had their original icon, it was default Android icon). That might have been the permissions issue you mentioned. In the future, how do I change the permissions, and what should they be set to? After this, I am done messing with it. Thank you for everything!
brentford said:
Thanks! I copied from Windows using adb, but I got the same asset error (two of the files no longer had their original icon, it was default Android icon). That might have been the permissions issue you mentioned. In the future, how do I change the permissions, and what should they be set to? After this, I am done messing with it. Thank you for everything!
Click to expand...
Click to collapse
You might be out of space again depending on what you copied back and why the icons are blank. Check with
adb shell df (in Android)
Look at system and see how much space you have free.
Or it could be permissions. You can use a file manager in Android such as ES File Explorer or Astro. You need to go to the setting in the app and enable whatever option they have to browse and remount "system" as read/write that will require root and should prompt you to accept. Then you can browse to the directory. You could also use TWRP File manager the same as when you copied files. There is a permissions tab.
I think the permission you want is 0644(for TWRP), or wr-r--r--(for ES). Same thing just different nomenclature.
Similar issue as OP
Hi guys, I have done pretty much the same thing as the OP. The wireless will not turn on or find any networks. I have tried reverse tethering, but have lost root and pretty much any other way to get internet to the nabi 2, so I can update from version 1.9.12. The big problem is I cannot use TWRP because when I boot into recovery and try to get there I get the dead green android guy with the exclamation point error and it hangs there until a hard restart. Any ideas on how to fix this. Is there a way to push an update through the SD card? Any ideas and suggestions would be greatly appreciated. I have already spent more time than I would have liked trying to fix this.
Dead android is stock recovery. You need to reflash TWRP.
Also to get out of the stock recovery just press vol + and - together. Should be am option to reboot. No need to hard power off.
aicjofs said:
Dead android is stock recovery. You need to reflash TWRP.
Also to get out of the stock recovery just press vol + and - together. Should be am option to reboot. No need to hard power off.
Click to expand...
Click to collapse
Well I swear I have tired this, but decided to give it another go and it worked! Got TWRP up and running then ran NabiLab to return to stock 1.9.37. Wireless is working and updating to 2.1 and then will give root a shot and GApps. Thanks for getting back on track!
Hi guys, I have the Rock Jaw Vi phone which by all sense and purpose seems to be a clone of the HTC One. It's Quad Core with 2 mega pixel camera on the front and 8 mega pixel on the back. The case and all outward appearances are that of the HTC, the phone info screen displays the following ...
Model Number = RJViJGTL32SM
Andoid version 4.2.1
Baseband version = moly.wr8.w1248.md.wg.mp.v6.p8,2013/08/12 15:55
Kernel version 3.4.5 [email protected] #1 Mon Aug 19 16:54:14 CST 2013
Build Number = 0502H026_20130819
I can get into the boot options screen by doing the On/Volume Down press but the menu's are all in Chinese and just seem to go through self diagnostics and tests. I can drag n drop file from Mac OSx but none of the apps I have found so far will communicate with the phone via USB. I am trying to get root so i can do a full back-up and then to try and put HTC Android 4.3 on it.
Do you guys have any idea on how I can achieve this or to get the phone to display it's boot options in English ?
I am pretty much clueless and stuck, any advice, tips, hacks etc would be really appreciated
I did follow a link at one stage on the web that went to SRSroot but their tool was windows only
Hmmm More messing with the phone has revealed power on with volume up depressed gets me to some very small text menu with the options;
Boot Normal
Fastboot
Boot(UART)
Boot UART is all the test screens that I was getting in Chinese but now they are touch screen buttons and labeled in english ao that's good to know.
Using fastboot-mac from HTCRootOne tries to talk to it but comes back with error: could not clear input pipe; result -536854449, is this something that's platform specific, ie it's not a true HTC so the version of fastboot-mac is no good and needing a non specific version ?
Ok that error is generated to the oem get_identifier_token...
If i do a fastboot-mac devices i get the reply "mt6589_phone_720pv2 fastboot" ...
I'm getting there slowly
Done some more digging with the phone attached to the Mac here and checking my systems profile I see that the phone is listed under usb connections as seen in the screen grab, still referring the as a HTC. Getting a new usb cable delivered to see if the phones usb cable provided is for charging only. If anyone here has any other suggestions I would be all ears or eyes as the case might be
Done more grubbing around and have found it to be a HDC One, HTC One clone .... Now to go see if any are rooted on here
Can anyone help me
Well i am pretty much stuck here so if anyone is reading this and wants to offer some help and advice I could do with it
I have looked around on the phone and can't see any bin or system folders even with show hidden i can't find them.
adb wont give me a remote shell, it complains that there is no bin/bash
when i try and do an adb backup i get 0 byte files grrrrr!!
I still need to find a way of getting root
This phone is a tricky beast for a learner - lol
Install some file explorer that allows you to browse from the top folder (/). I'm pretty sure you'll find at least /system there.
gbl08ma said:
Install some file explorer that allows you to browse from the top folder (/). I'm pretty sure you'll find at least /system there.
Click to expand...
Click to collapse
Thanks Gbl08ma - I have have it opened in Mac osx finder with show all files hidden or otherwise - The phone shows as two "No Name" devices and get mounted immediately on connection ....
I used sideload to push a package file over using adb and then went back to use Finder, and I can't see the file anywhere - hidden partition perhaps ? Can you do that with Android ?
Even the Android SDK file transfer app wont see the phone when it's connected, I am all very confused - lol
Thanks for the reply - Wonder if i can use disk utility to so some probing and at least get an ISO image file incase I goof things real bad - lol
TpwUK
tpwuk01 said:
Thanks Gbl08ma - I have have it opened in Mac osx finder with show all files hidden or otherwise - The phone shows as two "No Name" devices and get mounted immediately on connection ....
I used sideload to push a package file over using adb and then went back to use Finder, and I can't see the file anywhere - hidden partition perhaps ? Can you do that with Android ?
Even the Android SDK file transfer app wont see the phone when it's connected, I am all very confused - lol
Thanks for the reply - Wonder if i can use disk utility to so some probing and at least get an ISO image file incase I goof things real bad - lol
TpwUK
Click to expand...
Click to collapse
/ does not get mounted over USB so you won't see /bin, /system, /data or anything other than the SD card and the internal FAT32 "user" partition when entering USB transfer mode.
You must do it on the device. And for adb to work, USB debugging must be enabled in the settings.
gbl08ma said:
/ does not get mounted over USB so you won't see /bin, /system, /data or anything other than the SD card and the internal FAT32 "user" partition when entering USB transfer mode.
You must do it on the device. And for adb to work, USB debugging must be enabled in the settings.
Click to expand...
Click to collapse
I already had the phone in usb debug mode. Had to set the phone to use usb as MTP and not mass storage device connection type. Now it allows me to get in to the blighter with adb, fastboot still errors with pipes. That method allows me to get adb shell running and i can get android file transfer .... back to the reading part again
Thanks for the information gbl08ma - if i can find a way to back-up the rom i will share it somewhere
Hmm yummy - lots of interesting things in there .... Forgive my ignorance again please, but if i can create an update.zip file from the shell on the device that compresses all files from \ and all subdirs would that be the same thing as a safe ROM backup ? i wanna be safe before i attempt to root the phone as someone on here has a lower spec version of this phone and says it's a partial brick now.
TpwUK
Rooted
This phone is easily rooted with the motochopper
http://forum.xda-developers.com/showthread.php?p=40747604
Now should I push my luck further and go for the ROM - lol
TpwUK
I believe i own the same mobile
@tpwuk01
I also asked the same here; http://forum.xda-developers.com/showthread.php?t=2180425&page=92
but i was only able to root using frama root app, and it worked like a charm, but thats the only thing i could achieve, dont know but it seems theres no official thread of developement going on for any cloned device, mine runs the MOLY.WR8.W1248.MD.WG.MP.V6.P8 2013/08/12 15:55 Baseband.
After root i just installed some root apps, ads blockers, cant get any recovery to work, (Playing safe actually not to brick this now, since no support yet) but would have appreciated trying out kitkat on it, using antutu to view up specs, its impressive, i got to find out our 13MP camera at the back can do a great job than it currently is we only need to figure out how to change the image compression, the one i stumbled upon online was the blast, the 13MP was great also the flash light was tweaked to be 50X its current brightness, our 1GB application space was increased to 3.5GB, GPS and the rest was also modded to work really great.
Would like to hear any new updates you stumble upon bro.
Still a nice and featured packed device.
Howdy folks,
Yesterday, I was the proud owner of a sleek little TCT.Alcatel OneTouch A554C, formally know as a Virgin Mobile Venture running Android version 2.3.5.
It was successfully and surprisingly easy to root by utilizing 2 cool little apps, Ministro and Poot-Debug.
After root, I subsequently downloaded some root tools (eg., Titanium Backup Pro, Superuser Elite, System App Uninstaller).
That was last week.
Yesterday, I got a bit cocky. I needed to clear up some internal memory so I used "System App Uninstaller" to uninstall a few apps. If I remember correctly, the apps were as follows: Google Maps, Google Maps Street View, Calculator, Digital Clock, Setup Wizard, Android Live Wallpaper, Live Wallpaper Picker, Magic Smoke Wallpaper, Music Visualization Wallpaper, and the TouchPal Keyboard French and Spanish Language Packs.
So far so good, right? However, I believe I may have snarfed-up when I uninstalled the Setup Wizard. But I'll get to that in a minute.
Now with Titanium Backup, I moved some apps to the sd card. Included was the stock launcher, Smart Launcher Pro, SPB Shell, AVG Anti-Virus, and Superuser Elite. Then I rebooted through Titanium Backup and I haven't viewed any pornographic material since!
After reboot, the phone got stuck on the final boot animation frame. I panicked, pulled the battery, booted into recovery then rebooted a 2nd time.
This time it booted to the pull-down lock screen. I unlocked and seen:
"Sorry! The application com.android.setup wizard has stopped unexpectedly. Please try again." Along with a "Force Close" option. I forced closed and the screen went black with the exception of the status bar. The phone is still on but otherwise...nada.
When I press the power button, same thing happens: pull-down lock screen, screen goes black. Or sometimes, it will turn on and boot loop.
Major panic time!!! I booted into recovery again and performed a factory reset to no avail.
Another clue to note: I can connect & access the sd card via usb to desktop.
Also, I did have the good sense to backup all apps, system and user, through ES File Explorer and stored them both on sd card and in the cloud via Yandex Disk prior to this bricking fiasco. Now, what do I do with them? I now realize it was possibly a mistake moving all 3 launchers to the sd card. How do I get the stock launcher back to the phone?
Or, should I:
1- Attempt a base rom reinstall or
2- Attempt a custom rom install or
3- Use it solely as a time piece/mass storage device or
4- Throw it very hard and very ******* far away from me!?
I realize this is an obscure little cheap phone but it's the only one I have. Any valid feedback would be greatly appreciated.
You can go to the Play Store on any browser and choose a launcher to install. Or if you have USB Debugging on, you can side load an launcher apk. Or if you install a custom recovery, you can install another rom or sideload an apk there. Or you can flash the original firmware via SP Flash Tool.
Lots of options and none of them need to be throwing it against the wall.
es0tericcha0s said:
You can go to the Play Store on any browser and choose a launcher to install. Or if you have USB Debugging on, you can side load an launcher apk. Or if you install a custom recovery, you can install another rom or sideload an apk there. Or you can flash the original firmware via SP Flash Tool.
Lots of options and none of them need to be throwing it against the wall.
Click to expand...
Click to collapse
Hmmm...Ok, thanks. Dig your username, by the way.
First thing is, install from play store would be possible if I had data service or if I was able to enable wi-fi. I only have calling & texting service on this phone and as for wi-fi, I can't enable it due to the problem of not being able to access the settings menu. All I have when it does boot, and it only fully boots when it is connected to a PC, is the pull-down lockscreen displaying time, date, status bar and the original wallpaper. Pull it down and the screen goes black with status bar still displayed along with time & battery level.
Secondly, USB debugging was enabled prior to all of this but I panicked & performed a factory reset. Don't think it's still on.
And lastly, is installing either a custom recovery, (which, to be frank, I'm just not that savvy) another rom or flashing original firmware even possible without a PC? Because I only have access to a PC without administrative privileges so therefore...no installing exe's without a password. Maybe this program lab will allow me, quite possibly not.
Hell, would I even still have root after a reset/data wipe?
Thanks, anyway, Esoteric Chaos
Off subject: The Joker was an Agent of Chaos. Loved Heath Ledger as The Joker.
Silver Rivers said:
Hmmm...Ok, thanks. Dig your username, by the way.
First thing is, install from play store would be possible if I had data service or if I was able to enable wi-fi. I only have calling & texting service on this phone and as for wi-fi, I can't enable it due to the problem of not being able to access the settings menu. All I have when it does boot, and it only fully boots when it is connected to a PC, is the pull-down lockscreen displaying time, date, status bar and the original wallpaper. Pull it down and the screen goes black with status bar still displayed along with time & battery level.
Secondly, USB debugging was enabled prior to all of this but I panicked & performed a factory reset. Don't think it's still on.
And lastly, is installing either a custom recovery, (which, to be frank, I'm just not that savvy) another rom or flashing original firmware even possible without a PC? Because I only have access to a PC without administrative privileges so therefore...no installing exe's without a password. Maybe this program lab will allow me, quite possibly not.
Hell, would I even still have root after a reset/data wipe?
Thanks, anyway, Esoteric Chaos
Off subject: The Joker was an Agent of Chaos. Loved Heath Ledger as The Joker.
Click to expand...
Click to collapse
You can go to ANY browser - even on the PC and log into your account and hit Install and it will send the command to your phone to install it. Pretty nifty. But you did say you factory reset, so that isn't actually going to work. Sorry.
The rest of the stuff would require a PC, though I don't think admin rights are needed, so there's that...
If you don't have your phone logged into Google or USB Debugging enabled, you're kind of stuck without a PC.
es0tericcha0s said:
You can go to ANY browser - even on the PC and log into your account and hit Install and it will send the command to your phone to install it. Pretty nifty. But you did say you factory reset, so that isn't actually going to work. Sorry.
The rest of the stuff would require a PC, though I don't think admin rights are needed, so there's that...
If you don't have your phone logged into Google or USB Debugging enabled, you're kind of stuck without a PC.
Click to expand...
Click to collapse
Well, on these PCs it certainly does. I thought I was on track yesterday and tried to install a copy of Odin that I found. Can't install without a frigging admin pass.
Someone else just suggested I try a stock rom flash. Might as well, right? Happen to know where I could find a good reliable copy? That also happens to be free?
Not sure why you were trying to use Odin for a non Samsung phone...?
The stock rom flash would only be possible via PC or if you had a custom recovery installed.
Here's what you would need to do for the Virgin Mobile Venture:
Download CWM: http://www.sendspace.com/file/4gt04i
Download adb/fastboot: http://forum.xda-developers.com/showthread.php?t=2317790
Download rom: http://goo.im/devs/LeslieAnn/Venture/Stock_Venture.zip - Put on SD card.
Drivers: http://pdanet.co/bin/PdaNetA4150.exe (this program is for USB tethering and installs the adb drivers for your phone as well as many others)
The CWM img will need to be in the folder you unzipped for adb/fastboot. You'll need to boot to fastboot mode by powering on with while holding Volume Up.
Open a terminal prompt and change directories to your adb/fastboot folder. Then run this command:
fastboot flash recovery nameofrecovery.img - fill in the nameofrecovery with whatever the CWM file name is.
(if this doesn't work - make sure that your PC is reading the phone correctly by using the command: fastboot devices . If you don't get anything back, make sure you check the Device Manager for errors. If you have them, try reinstalling the drivers and rebooting the PC)
Then pop the battery out and then reboot to recovery via powering on while holding volume down. Once there, you should be able to do a factory reset and then install the stock rom zip. The volume keys should scroll through selections and the Enter key for accept, or Power if that doesn't work. Not really sure about this particular phone.)
Actually, you might just be able to use adb to install a launcher apk once you have CWM installed. Might be a little easier.
launcher apk must be in adb folder then while in CWM:
adb install nameoflauncher.apk
Note: You can rename zips and apks to be easier to type the commands.
es0tericcha0s said:
Not sure why you were trying to use Odin for a non Samsung phone...?
Click to expand...
Click to collapse
Yeah, me either. I was all over the place yesterday grasping at anything. So Odin is only for Samsungs, huh? Guess I can delete the exe file from my sd.
Right then. I'm about to proceed with your advice. Cross your fingers and toes.
Thanks mate!
The CWM img will need to be in the folder you unzipped for adb/fastboot.
Click to expand...
Click to collapse
and
launcher apk must be in adb folder then while in CWM
Click to expand...
Click to collapse
Wait, what? Please excuse my ignorance, but am I missing something. ADB didn't come in a zip. It's an installer. I think you may have to dumb this down a bit more, mate.
Silver Rivers said:
and
Wait, what? Please excuse my ignorance, but am I missing something. ADB didn't come in a zip. It's an installer. I think you may have to dumb this down a bit more, mate.
Click to expand...
Click to collapse
Sorry, I meant in the folder that it extracts the files too.
es0tericcha0s said:
Sorry, I meant in the folder that it extracts the files too.
Click to expand...
Click to collapse
Right, got it.
Silver Rivers said:
Right, got it.
Click to expand...
Click to collapse
If you can't run the exe file, then let me know, and I'll just upload a zip / folder with the necessary files. You do not need admin access to run the adb commands.
es0tericcha0s said:
If you can't run the exe file, then let me know, and I'll just upload a zip / folder with the necessary files. You do not need admin access to run the adb commands.
Click to expand...
Click to collapse
That would be really cool, actually. But check this out:
I talked someone into allowing me to utilize his laptop. I installed ADB, moved the Launcher APK to the folder suggested, ran the commands but the command prompter responded with "waiting for device" and progressed no further. Could it be a driver issue? I was under the impression that if the PC recognizes your device (which it did) then a new driver install was not necessary.
Dude was real cool about it even though I ran his battery down quite significantly and didn't even accomplish anything.
So, if I had the ADB files then I could just copy them to...say the PC desktop and run the command prompter from there? If so, then yes please upload and I'll just try it that route rather than rely on someone's personal PC. Know what i mean?
I do appreciate all of this. I'm getting quite the education here. If you ever get married, let me know and I'll come and dance as my favor to you.:good:
Peace...I'll return tomorrow.
What mode were you in when trying to install? The laptop had the most up to date drivers? You checked the Device Manager to make sure there was no yellow exclamation mark next to the phone? It's not unheard of for the PC to recognize in one mode, but not load the correct drivers in another, as there are different drivers for the phone depending on if it is booted, in recovery, or download mode or whatever they call it for that phone. Just make sure to get the PDAnet drivers installed and reboot. That should do the trick.
Everything else you should need will be in here:
https://dl.dropboxusercontent.com/u/9903887/adbfastboot.zip
es0tericcha0s said:
What mode were you in when trying to install? The laptop had the most up to date drivers? You checked the Device Manager to make sure there was no yellow exclamation mark next to the phone? It's not unheard of for the PC to recognize in one mode, but not load the correct drivers in another, as there are different drivers for the phone depending on if it is booted, in recovery, or download mode or whatever they call it for that phone. Just make sure to get the PDAnet drivers installed and reboot. That should do the trick.
Everything else you should need will be in here:
https://dl.dropboxusercontent.com/u/9903887/adbfastboot.zip
Click to expand...
Click to collapse
I was in Recovery and I was also attempting to install the just the Launcher versus the entire ROM. And I was also feeling a tad bit rushed, cause dude was right there informing me of his battery status. "Well, it's down to 30%." Then 2 mins later.."Ok, looks like it just fell to 25%."
Haha...so yeah, with him pressuring me, I spaced on checking the device manager. This desktop that I'm on today seems to be cool. Just checked the manager & it informs me that my device is 'working properly'.
Off to give it another bloody joust, mate. Wish me luck...
Can you fully explain how to do this
es0tericcha0s said:
Not sure why you were trying to use Odin for a non Samsung phone...?
The stock rom flash would only be possible via PC or if you had a custom recovery installed.
Here's what you would need to do for the Virgin Mobile Venture:
Download CWM: http://www.sendspace.com/file/4gt04i
Download adb/fastboot: http://forum.xda-developers.com/showthread.php?t=2317790
Download rom: http://goo.im/devs/LeslieAnn/Venture/Stock_Venture.zip - Put on SD card.
Drivers: http://pdanet.co/bin/PdaNetA4150.exe (this program is for USB tethering and installs the adb drivers for your phone as well as many others)
The CWM img will need to be in the folder you unzipped for adb/fastboot. You'll need to boot to fastboot mode by powering on with while holding Volume Up.
Open a terminal prompt and change directories to your adb/fastboot folder. Then run this command:
fastboot flash recovery nameofrecovery.img - fill in the nameofrecovery with whatever the CWM file name is.
(if this doesn't work - make sure that your PC is reading the phone correctly by using the command: fastboot devices . If you don't get anything back, make sure you check the Device Manager for errors. If you have them, try reinstalling the drivers and rebooting the PC)
Then pop the battery out and then reboot to recovery via powering on while holding volume down. Once there, you should be able to do a factory reset and then install the stock rom zip. The volume keys should scroll through selections and the Enter key for accept, or Power if that doesn't work. Not really sure about this particular phone.)
Actually, you might just be able to use adb to install a launcher apk once you have CWM installed. Might be a little easier.
launcher apk must be in adb folder then while in CWM:
adb install nameoflauncher.apk
Note: You can rename zips and apks to be easier to type the commands.
Click to expand...
Click to collapse
I have a old ass iMac desktop that has not been used in 5plus years at all and I'm a mother of 3 with no clue how to do any of this if you can dumb it down for me that would be very help full as well I have no clue where to download any of the needed files please help. My email is [email protected]
Thank you