Hello,
I've tried updating the Odys Genesis to the custom firmware cyanogenMod7 custom rom for odys genesis.
I think i did it the wrong way. I've searched for hours on the internet how to do it, and then i cam across a post that said i just needed to put it on the device and then android would pop up and say: "A new update is available" and i just would have to tap that. So, i did.
The device rebooted and started updating all kinds of stuff in a dos-like enviroment. But now it's only a black screen and saying ANDROID in white letters. I've kept it like that for an hour, and then i tried resetting it (behind the device, hard reset button). I see the Odys brand screen, but then it's back at the black screen with android on it again.
Is there any hope left? Can i do something to fix it?
I've tried searching for hours on the internet, and i came up with absolutly nothing. Any help would be greatly appreciated!
Thanks in advance!
I found out a little bit more:
- My problem is called a boot-loop. It seems like it anyway, i only see a tiny white text saying 'android'.
- I can't find anywhere on the internet if there's a recovery mode for the Odys Genesis.
- The device will turn on with any button-combination, except when i press menu+power or power+reset.
I have been looking at Odin, cause that should be a unbrick-program for android phones. But it seems you need specific firmware for your model. Can i just use the original firmware update from the website of the manufacturer?
Or am i just totally ****ed? Just a reaction alone would be appreciated !
Solution
And somebody can close this topic!
I'm extremely happy, cause by a little accident i discovered how i could flash back to the normal firmware.
For somebody who has the same problem, here my solution:
When the device is on the screen only saying android do the following:
- Press the hard reset button (on the back, the tiny hole) and the menu button at the same time.
- The android screen should now go away, and it should like the device is off (although it isn't).
- Plug in the usb cable and connect it to your pc.
- If you had your device previously plugged in to your pc before, the pc will falsly recognize it as 2 hdd's while there isn't any shown in this computer.
To fix that:
- Go to device manager (This computer (right click) -> properties -> device manager)
- Uninstall the falsly drivers, (so there is no driver anymore).
- Disconnect the usb cable and connect it again.
- Windows should now say (or say in device manager) that an unknown device is connected.
- Download the Pc Update Tool and original firmware from the manufacturer website: (can't post url's here, so google Odys Genesis and you will get there)
- At the driver installation window choose you would like to point where the drivers are.
- Choose the dir from the pc update tool, and choose the driver map according to your processor and windows.
- The device should now be installed as a RK2.... something device.
- Start the Pc Update Tool
- The first box below should be green, indicating it sees the device and is ready to flash.
- At the box image, choose the original image downloaded from Odys website.
- Click Upgrade.
All should work well now, the box (log) should keep you informed. It could take a little while.
When it's done, it will tell you in the window. The device should now restart and Boot recovery should start and the device, formatting everything, resetting again and then installing everything. It all could take some while, so be patient.
And that's it.... then everything is working again ! ~!
Please let me know where you downloaded the CM7 ROM from... can't get it from the link in other post
Thanks
sleuteltje said:
And somebody can close this topic!
I'm extremely happy, cause by a little accident i discovered how i could flash back to the normal firmware.
For somebody who has the same problem, here my solution:
When the device is on the screen only saying android do the following:
- Press the hard reset button (on the back, the tiny hole) and the menu button at the same time.
- The android screen should now go away, and it should like the device is off (although it isn't).
- Plug in the usb cable and connect it to your pc.
- If you had your device previously plugged in to your pc before, the pc will falsly recognize it as 2 hdd's while there isn't any shown in this computer.
To fix that:
- Go to device manager (This computer (right click) -> properties -> device manager)
- Uninstall the falsly drivers, (so there is no driver anymore).
- Disconnect the usb cable and connect it again.
- Windows should now say (or say in device manager) that an unknown device is connected.
- Download the Pc Update Tool and original firmware from the manufacturer website: (can't post url's here, so google Odys Genesis and you will get there)
- At the driver installation window choose you would like to point where the drivers are.
- Choose the dir from the pc update tool, and choose the driver map according to your processor and windows.
- The device should now be installed as a RK2.... something device.
- Start the Pc Update Tool
- The first box below should be green, indicating it sees the device and is ready to flash.
- At the box image, choose the original image downloaded from Odys website.
- Click Upgrade.
All should work well now, the box (log) should keep you informed. It could take a little while.
When it's done, it will tell you in the window. The device should now restart and Boot recovery should start and the device, formatting everything, resetting again and then installing everything. It all could take some while, so be patient.
And that's it.... then everything is working again ! ~!
Click to expand...
Click to collapse
I have the same issue, but I have a 64bit Win7 and it just won't work. Windows will not install the original drivers. Any other way to go around it?
I only need make a hard reset, any help??? I don't remember unlock code
I've tried to download original firmware but i can't find it.
I was following the exact step-by-step guide here:
http://forum.xda-developers.com/showthread.php?t=1196808
and after I flashed the kernel downgrade, unplugged USB, power up the phone and immediately plug in after the vibrate, I never got the message in the next step that says "Connected Device: X10", and the "Root" button on the flash tool never became available.
Now my phone is permanently stuck at the "Sony Ericsson" black screen, it won't even turn off. I checked device manager and there are 2 hardware without any drivers. one of them says "Modem Device on High Definition Audio Bus", and the other says "SM bus controller". Does this have anything to do with my problem?
I'm running Win XP SP3, I tried to let it automatically search for drivers but it didn't find anything. I went to:
http://forum.xda-developers.com/showthread.php?t=1193066
and downloaded those drivers, but have no idea how to use them. Tried to use device manager to look for drivers in the downloaded folder and it doesn't recognize anything.
What now? At this point I don't care if I can still root my x10 or not, I just want to fix it so I can use it again. I tried PC Companion but it won't even recognize my phone, keeps telling me to enable USB when I can't even get past the SE screen.
You should try flashing a new ftf firmware bundle, then try the steps again.
ok finally fixed... had to use a friend's computer who is running win7 and actually automatically installed the drivers. everything went as explained on the guide... I guess the guide is not win xp friendly then
Hi,
I have on my tf201 latest official firmware, 4.1.1 build-number: JRO03C.WW_epad-10.4.2.18-20121122.
As Asus doesn't provide any more updates for our device and mine is out of warranty I'm finally ready to move on to some custom roms.
My tablet is Rooted.
Now after a lot of reading I thought it would be wise to do a backup of everything and make my device unbrickable.
I started to follow the instructions on this site : matthill.eu/android/transformer-prime-tf201-jellybean-nvflash
At first I backed everything up with Titanium Backup and then I did a factory reinstall, so I would have a clean tablet to start.
Then I installed the unlocking tool and succesfully unlocked my device.
I restarted my tf201 with holding the volume button down to get the options to enter fastboot.
When I got to the selection menu, I press the volume button a few times to select the USB-icon.
Then I press the volume up button to enter fastboot, but nothing happens. It just freeze.
The only thing I can do is hold the power button until my tablet restarts.
Also, since i'm on JB I never could connect it on my pc anymore. It even doesn't show up as an unknown device.
So when I want to use ADB I have to use ADB Konnect (wireless ADB).
JNiels1980 said:
Hi,
I have on my tf201 latest official firmware, 4.1.1 build-number: JRO03C.WW_epad-10.4.2.18-20121122.
As Asus doesn't provide any more updates for our device and mine is out of warranty I'm finally ready to move on to some custom roms.
My tablet is Rooted.
Now after a lot of reading I thought it would be wise to do a backup of everything and make my device unbrickable.
I started to follow the instructions on this site : matthill.eu/android/transformer-prime-tf201-jellybean-nvflash
At first I backed everything up with Titanium Backup and then I did a factory reinstall, so I would have a clean tablet to start.
Then I installed the unlocking tool and succesfully unlocked my device.
I restarted my tf201 with holding the volume button down to get the options to enter fastboot.
When I got to the selection menu, I press the volume button a few times to select the USB-icon.
Then I press the volume up button to enter fastboot, but nothing happens. It just freeze.
The only thing I can do is hold the power button until my tablet restarts.
Also, since i'm on JB I never could connect it on my pc anymore. It even doesn't show up as an unknown device.
So when I want to use ADB I have to use ADB Konnect (wireless ADB).
Click to expand...
Click to collapse
When you press up on the USB icon and it freezes that it normal.. This is fastboot mode.
You now must access it over a PC after installing the naked drivers.. If it is not showing on your PC then either try a different PC or your cable is faulty.
Thanks for the quick reply.
I tried once more to enter fastboot. Same result.
But when I disconnected my usb cable to connect it to an other computer, suddenly I got this message on my tablet:
"Starting Fastboot USB download protocol"
This message didn't show up before.
I plugged the tablet back to my pc, but still no device detection in device manager, even when refreshing (So I can't install naked drivers, as it is not recognized).
My computer is a Windows 8.1 system.
I restarted my tablet again, (after disconnecting it from my pc) and followed the procedure to enter Fastboot again.
I waited for the message "Starting Fastboot ..." and then I connected the cable to my other pc (Windows 7 system)
Same result as on the Windows 8.1 machine, not recognized
You say it could be that my cable is broken. Maybe, but it's a strange coincidence that this happened when switching from ICS to JB.
I know JB for the tf201 is been out a long time, and I updated since I could. So over time, maybe my cable could be broken now. But I'm sure I had this problem (not recognizing) since then, because right after updating I wanted to do some things with ADB and so I found out I had this problem.
Hi everybody! First post here so please forgive me if I step over any bounds. I have a Verizon Samsung Galaxy S III (SCH-I535 is the model I believe?), OS version 4.1.2 and I'm having some problems rooting/unlocking it. My goal is to use it on the ATT&T network, which I've seen has mixed success when I researched it, but I'm currently rocking an iPhone 3GS so it doesn't get much worse. When I plug the phone into my computer (and I've tested it on a few now), it immediately begins charging, says it's connected as an installer, and by all accounts seems to be fine. On my computer though, a notification bubble pops up and says 'USB Device not recognized' (see pics). I've tried manually installing the drivers for the 'Unknown Device' in the Device Manager, uninstalling the Samsung drivers and installing a slightly older version, bending the tongue in the USB port slightly upwards, blowing in the port, connecting it as PTP and MTP (all solutions I found online), still to no avail. One thing I wanted to try but was unable to is plugging the phone in while it's in download mode. I can restart the phone into Download mode, but at the prompt I can only press the down arrow because the volume up button on the rocker is broken! None of the reboot apps on the Play Store would work for me. So, my question are:
1.) Are there any other solutions that might help me get my computer to recognize my phone so I can root/flash it?
2.) Is there any other way to enter recovery mode or bypass the prompt on an unrooted phone? Thanks a bunch for the help everyone!
P.S. I'm running Windows 7 SP1, and I recently rooted my friend's Note 2 successfully using the computer and cable so I don't think that's the problem.
Wrong forum, this is for the i9300 only.
Hi all, I will try to be as detailed as possible.
I have a MetroPCS LG MS323 which I bought as a second phone to use when I travel as my regular phone is CDMA and I wanted a GSM phone that I could use with a sim card. While on an overseas trip I paid a cellphone place to unlock the phone so I could use other carriers' sim card, it was working fine since then. However, as I don't use the phone on a regular basis it ended up sitting and the battery lost its charge. When I tried to charge it by usb, it started bootlooping (vibrate, LG logo, repeat). After that I pulled the battery and charged it using an external charger. The phone is not rooted. I tried the factory reset key combo, but it gets stuck on the screen which says factory reset processing........ endlessly. I tried to download kdz file and flash with LG flash tool but phone cannot get into download mode. When I press vol key and plug usb cable, it says LOADING.......... press volum up key until download mode starts But it gets stuck there and download mode never starts.
I downloaded adb and fastboot to a Windows 7 laptop, and LG drivers, but when I connect phone and open a terminal adb devices shows no phone connected.
I also downloaded Laf.img for this phone and Laf recovery tool for Windows but again I cannot seem to get computer to see the phone. If I try to use the tool it says "waiting for device"
One difficulty is to trying to plug phone to computer the right way.
Most of the threads say to have phone in battery charge mode with usb debugging enabled, but I can't select any settings if the phone is bricked.
If I just plug the phone to usb when it is turned off it shows a picture of battery but no sign of charging, and computer doesn't detect phone.
If I plug phone to usb first, then hold vol and power key the LG logo will go black and it vibrates, in that case sometimes the Windows laptop will see 2 folders, verinfo and image.
When I plug usb cable to Linux computer and phone is off, same thing just picture of battery but terminal only shows sda1 sda2 sda3 etc no sdb no sdc just like not detected.
If I hold vol down then plug usb it vibrates and stuck on LG logo.
I have also tried to plug usb, then press vol down and power until phone vibrates, then try to let go buttons before LG logo shows up. but it doesn't mount.
If I hold vol up and power, then plug usb. it vibrates and goes to LG logo.
Last night somehow I got it to mount on the linux computer but the file manager was going crazy opening multiple windows and a list of folders would show up for a second, disappear and reappear as if the system was trying to read the folders but having difficulty. Today I am not able to get it to mount.
I have downloaded a linux livecd with adb and fastboot, I haven't tried it yet because I am not sure the path to flash an img file from a different directory on the hard drive on the windows laptop.
I have downloaded aboot.img but don't know how I can flash it if I can't see the phone on any computers.
I have spent days searching for solutions but have not seen the exact same problem, other threads suggest things but often the symptoms are slightly different or with a different phone. So, first of all I need to know what kind of brick I have, because other solutions I have seen posted for completely black screen, or phone detected as qhsusb qualcomm etc. which seems like a different problem.
So the 2 main things are 1, to know which kind of brick because many of the solutions I see posted seem like a different problem.
second, what is the best way to plug to computer so I can see the phone?
I burned a live CD of FWUL and ran adb from linux, still says adb devices nothing shows up. usb cable is plugged in and phone is turned off. Am I doing this wrong? I held down power and vol down until phone vibrates and LG logo appears. adb devices - "list of devices attached" still has nothing showing.. I don't know why even in Linux I can't see any device attached. Also I tried with pressing vol up and power until phone vibrates.
ls /dev/sd* only shows sda sda1 sda2 etc
I have also looked at past threads about unlocking the L70 bootloader, but the bootloader.zip no longer links and the phone does not have busybox installed.
I tried to see it Windows Device Manager but it does not show up anywhere.
This probably won't help, but, when you're at this point, you'll try about anything.
Did you fully install the LG drivers on your PC? Obvious seeming question. I was doing an old Droid Bionic a couple months ago and didnt' switch the USB modes (charging, media, file transfer, whatever it had) to each mode before modding .
As a result, I bricked that Droid bad. It took me almost a week and a half to restore it. I'm not sure if LG drivers work the same way, though I've worked on plenty of them. I think I have an LG Leon still in the scrap heap as a result of trying to replace a cracked digitizer that was bonded to the LCD. If anyone needs parts for one, I've got em, cheap I think that's an MS345 if I recall.
equitube said:
This probably won't help, but, when you're at this point, you'll try about anything.
Did you fully install the LG drivers on your PC? Obvious seeming question. I was doing an old Droid Bionic a couple months ago and didnt' switch the USB modes (charging, media, file transfer, whatever it had) to each mode before modding .
As a result, I bricked that Droid bad. It took me almost a week and a half to restore it. I'm not sure if LG drivers work the same way, though I've worked on plenty of them. I think I have an LG Leon still in the scrap heap as a result of trying to replace a cracked digitizer that was bonded to the LCD. If anyone needs parts for one, I've got em, cheap I think that's an MS345 if I recall.
Click to expand...
Click to collapse
Thanks, yes I had installed latest LG drivers LGMobileDriver WHQL Ver 4.2.0 before trying to flash .kdz file.
A tiny bit of progress to report, after getting a perfect timing to release the power and vol down keys I was finally able to connect to Windows machine. while waiting for drivers to install it was detected as QHSUSB_BULK in device manager, after drivers loaded now it is listed as LGE AndroidNet USB Serial {port (COM4). However when I run adb I still cannot see an attached device. I will look at solutions for the specific type of brick problem which has now been identified.
fofopuka said:
Thanks, yes I had installed latest LG drivers LGMobileDriver WHQL Ver 4.2.0 before trying to flash .kdz file.
Click to expand...
Click to collapse
What I meant was after initially installing the drivers did you switch the USB mode on your LG to all possible settings? Some drivers (like Moto) install more functions only when first called. you'll know if you switch from say charging to MTP or RNDIS you'll see driver install reopen.
also when you first ran ADB and plugged in the phone you probably should have seen more drivers install.
Forgive me if I seem to insult your intelligence. I'm an IT pro w 30 yrs in tech and I didn't know about the multi driver USB functions.
Tom Sgt aka Rootjunky has a good video on this that i initially didn't watch figuring I'd been installing drivers forever. 5 more minutes of watching it would have saved near 40 hrs of work and research
and when r
equitube said:
What I meant was after initially installing the drivers did you switch the USB mode on your LG to all possible settings? Some drivers (like Moto) install more functions only when first called. you'll know if you switch from say charging to MTP or RNDIS you'll see driver install reopen.
also when you first ran ADB and plugged in the phone you probably should have seen more drivers install.
Forgive me if I seem to insult your intelligence. I'm an IT pro w 30 yrs in tech and I didn't know about the multi driver USB functions.
Tom Sgt aka Rootjunky has a good video on this that i initially didn't watch figuring I'd been installing drivers forever. 5 more minutes of watching it would have saved near 40 hrs of work and research
and when r
Click to expand...
Click to collapse
thanks, I found his video for the G2 and no, I have never seen that with the drivers before! good to know. You can't insult my intelligence because most of this is over my head and I'm just trying to follow stuff I found with Google on XDA......
I downloaded and installed the Qualcomm drivers to try and identify if I have the 9006 or 9008 variety brick. However now when I plug in the phone Windows waits to install drivers, then says successful, when I look in device manager now I can't find the phone. But I did notice on the taskbar now there appears an icon named "intel graphics media accelerator driver for mobile" perhaps that is the driver Windows assigned to it? Device manager does have Intel Graphics Media Accelerator under display adapters. The other weird thing is that now it shows the battery as charging, which it never did the other times I plugged it into usb.
fofopuka said:
thanks, I found his video for the G2 and no, I have never seen that with the drivers before! good to know. You can't insult my intelligence because most of this is over my head and I'm just trying to follow stuff I found with Google on XDA......
I downloaded and installed the Qualcomm drivers to try and identify if I have the 9006 or 9008 variety brick. However now when I plug in the phone Windows waits to install drivers, then says successful, when I look in device manager now I can't find the phone. But I did notice on the taskbar now there appears an icon named "intel graphics media accelerator driver for mobile" perhaps that is the driver Windows assigned to it? Device manager does have Intel Graphics Media Accelerator under display adapters. The other weird thing is that now it shows the battery as charging, which it never did the other times I plugged it into usb.
Click to expand...
Click to collapse
have you seen this thread.
https://forum.xda-developers.com/showthread.php?t=2773123
it has the firmware for your model links to drivers and the LG flash tool, (which is warned against newbies (what the hey, it can't get much worse, we were all newbies once, )
Can you boot into fastboot? if so, you could flash the firmware with that.
equitube said:
have you seen this thread.
https://forum.xda-developers.com/showthread.php?t=2773123
it has the firmware for your model links to drivers and the LG flash tool, (which is warned against newbies (what the hey, it can't get much worse, we were all newbies once, )
Can you boot into fastboot? if so, you could flash the firmware with that.
Click to expand...
Click to collapse
Hi, yes although those links no longer work I have found the drivers and flashtool elsewhere. If I try to run flashtool it cannot see the phone. I cannot get into fastboot, and download mode won't load. I cannot see the phone on any Linux machine. The most I can do it see the phone as E: Qualcomm MMC storage USB device in Device Manager, but no other details. Explorer can see 2 folders, image and verinfo. Is there anything I can do with these folders in Windows? adb and fastboot run from terminal still do not list any attached device. Windows did a search for drivers for QHSUSB_BULK, although in device manager it still says LGE AndroidNet USB Serial Port (COM5).
What I really want to do at this point is push aboot.img to the phone, but for some reason I can't access the phone with Linux or adb. maybe because it did not have usb debugging enabled before it bricked. So many of the threads I have seen require a working phone to implement the steps, is there any way to enable usb debugging when the phone doesn't work?
fofopuka said:
Hi, yes although those links no longer work I have found the drivers and flashtool elsewhere. If I try to run flashtool it cannot see the phone. I cannot get into fastboot, and download mode won't load. I cannot see the phone on any Linux machine. The most I can do it see the phone as E: Qualcomm MMC storage USB device in Device Manager, but no other details. Explorer can see 2 folders, image and verinfo. Is there anything I can do with these folders in Windows? adb and fastboot run from terminal still do not list any attached device. Windows did a search for drivers for QHSUSB_BULK, although in device manager it still says LGE AndroidNet USB Serial Port (COM5).
What I really want to do at this point is push aboot.img to the phone, but for some reason I can't access the phone with Linux or adb. maybe because it did not have usb debugging enabled before it bricked. So many of the threads I have seen require a working phone to implement the steps, is there any way to enable usb debugging when the phone doesn't work?
Click to expand...
Click to collapse
Of course, I had forgotten about that. In order to use fastboot, most flashing tools, you HAVE to have USB debugging on.
There are occasional ways around this, though they are few. I do seem to recall oding it on that LG Leon. OR it may have been a Moto e or G, let me look back at previous threads i've asked for help in.
(Hmm, perhaps taking notes, or just leaving a webcam running while I'm doing a new device might be valuable in the future, I think with remarkable hindsight.) :cyclops:
---------- Post added at 02:28 AM ---------- Previous post was at 02:26 AM ----------
And no, you can't do anything to Android files in Windows, except see them. they are generally a different file system
One of the difficulties is just plugging it to a PC. 9 out of 10 times it is not recognized and nothing happens. So far the only way that seems to occasionally work is to plug the usb cable to the Windows 7 laptop, hold vol down and power, release both as soon as it vibrates. Most of the time I can't get it timed exactly right, but if I'm lucky sometimes Windows will detect the usb connection by following these steps. If I try on a Linux machine nothing happens, phone stays invisible. The most I've gotten with Linux is to charge the battery, but will not mount.
It is just a stock phone, not rooted, no busybox, no developer options enabled.