I have this strange problem on my droid 3 (I just bought it with this problem).
Every time the screen goes off it reboots.It doesn't happen only when I'm on a JB based rom.I.e,with cm10.1 the Phone works perfectly!But I need Camera functionality,so I could not use it as daily driver!
I tried 6-7 roms gingerbread-based, the steeldroid 5.6(Ics based)and CM9.also stock rom (5.6.890, 5.7.906 and 5.8.25) reboot.
It's not wifi related (it reboots even with wifi off),it's not gsm related (it reboot even in airplane mode),it's not governor related(It reboot set in performance,hotplug,badass,ondemand,userspace...),it's not cpu related(it reboots even if I set Cpu to stay always to the max),it's not account related(it reboots even before setting the account),it's not deepsleep related(it reboots even if I disable deepsleep with wake lock app)
It doesn't reboot when I plug it in Pc but it reboots when it's plugged into the charger..
Help please..I'm going crazy!!
fabio536 said:
I have this strange problem on my droid 3 (I just bought it with this problem).
Every time the screen goes off it reboots.It doesn't happen only when I'm on a JB based rom.I.e,with cm10.1 the Phone works perfectly!But I need Camera functionality,so I could not use it as daily driver!
I tried 6-7 roms gingerbread-based, the steeldroid 5.6(Ics based)and CM9.also stock rom (5.6.890, 5.7.906 and 5.8.25) reboot.
It's not wifi related (it reboots even with wifi off),it's not gsm related (it reboot even in airplane mode),it's not governor related(It reboot set in performance,hotplug,badass,ondemand,userspace...),it's not cpu related(it reboots even if I set Cpu to stay always to the max),it's not account related(it reboots even before setting the account).
It doesn't reboot when I plug it in Pc but it reboots when it's plugged into the charger..
Help please..I'm going crazy!!
Click to expand...
Click to collapse
mmmm... looks like it's a storage/kernel problem, try this: unmount the memory card (if you have one) and see if it reboots, after that, connect it to the pc (i guess you did it in memory storage mode) and watch if it reboots, after this, change the usb mode (charge only, windows media, etc.) and for each one, look for a reboot. In the end, try to format both internal storage and memory card (if you have) via pc, BUT, do NOT use quick format, use the long one, and see if anything get better
P.S. after that, you could do an SBF just to be sure that you've restarted from zero!
Bye!
FrankieDedo said:
mmmm... looks like it's a storage/kernel problem, try this: unmount the memory card (if you have one) and see if it reboots, after that, connect it to the pc (i guess you did it in memory storage mode) and watch if it reboots, after this, change the usb mode (charge only, windows media, etc.) and for each one, look for a reboot. In the end, try to format both internal storage and memory card (if you have) via pc, BUT, do NOT use quick format, use the long one, and see if anything get better
P.S. after that, you could do an SBF just to be sure that you've restarted from zero!
Bye!
Click to expand...
Click to collapse
mm..to do that,I have to do it with the stock rom,isn't it?What's the best way to format internal storage from pc?
I will try,but I know that when it's connected to the pc,it never reboots!
Edit:
Formatted internal storage and removed memory card..then flashed .890...It'e still rebooting..Any chance to modify kernel?Or if there's any rom with different kernel,even if GB based..
P.S. Hey..another Italian user?
fabio536 said:
mm..to do that,I have to do it with the stock rom,isn't it?What's the best way to format internal storage from pc?
I will try,but I know that when it's connected to the pc,it never reboots!
Edit:
Formatted internal storage and removed memory card..then flashed .890...It'e still rebooting..Any chance to modify kernel?Or if there's any rom with different kernel,even if GB based..
P.S. Hey..another Italian user?
Click to expand...
Click to collapse
mmmm.... i don't think there is another kernel for D3, the only one is the kexec, but it is for ICS/JB... at this point i think it's something broken :/
P.S. Esatto rispondo in inglese almeno anche altri possono usufruire delle risposte (e poi non credo si possa parlare in altre lingue )
FrankieDedo said:
mmmm.... i don't think there is another kernel for D3, the only one is the kexec, but it is for ICS/JB... at this point i think it's something broken :/
P.S. Esatto rispondo in inglese almeno anche altri possono usufruire delle risposte (e poi non credo si possa parlare in altre lingue )
Click to expand...
Click to collapse
Bah..very strange behaviour..Next week I'll try an original new battery!Now I have 4 compatible batteries..I know this is not the problem,but I will try everything!
I don't think it's a hardware issue because with JB it works perfectly!
fabio536 said:
Bah..very strange behaviour..Next week I'll try an original new battery!Now I have 4 compatible batteries..I know this is not the problem,but I will try everything!
I don't think it's a hardware issue because with JB it works perfectly!
Click to expand...
Click to collapse
I don't know how to reflash kernel for D3, search somewhere on the forums, but at this point i think this is the problem... i thought this: try the CM9 build with functioning camera (it has the Gingerbread kernel) and see if reboots are still happening, the steel droid 5.6 should be fine, or look for an Hashcode build. If it reboots, then it's definitely a kernel problem, if it runs ok, then it's something related to roms, but i doubt it... This issue is pretty weird!
P.S. I know it's dumb, because you've probably done this with a freshly wiped phone, but could this be originated from an app? i had a problem with a wallpaper changer that freezed my phone on the lockscreen, maybe it's something like that
FrankieDedo said:
I don't know how to reflash kernel for D3, search somewhere on the forums, but at this point i think this is the problem... i thought this: try the CM9 build with functioning camera (it has the Gingerbread kernel) and see if reboots are still happening, the steel droid 5.6 should be fine, or look for an Hashcode build. If it reboots, then it's definitely a kernel problem, if it runs ok, then it's something related to roms, but i doubt it... This issue is pretty weird!
Click to expand...
Click to collapse
I tried Cm9 and steel droid 5.6,but they reboot..I'll look for a way to reflash kernel..
Could I flash the 5.5.959 sbf?It's the only original firmware I didn't try!
FrankieDedo said:
P.S. I know it's dumb, because you've probably done this with a freshly wiped phone, but could this be originated from an app? i had a problem with a wallpaper changer that freezed my phone on the lockscreen, maybe it's something like that
Click to expand...
Click to collapse
Definitely not..It reboots even in the setup wizard if I lock the screen..Before installing any app!!
fabio536 said:
I tried Cm9 and steel droid 5.6,but they reboot..I'll look for a way to reflash kernel..
Could I flash the 5.5.959 sbf?It's the only original firmware I didn't try!
Definitely not..It reboots even in the setup wizard if I lock the screen..Before installing any app!!
Click to expand...
Click to collapse
Ok, now i'm pretty sure that the problem is with the kernel, OR, with a kernel call to a device that doesn't work very well, maybe even the camera... did it works ok? this is the first thing that i'm thinking, because if i'm not wrong, the kexec kernel in the ICS/JB builds is not even calling the camera functions... but i'm pretty trivial now... i hope it's not something like a misplaced component (one of the flat cable connected to the motherboard) but in that case you could just grab a 1€ Torx T5 screwdriver on eBay and see if something is screwed (ha-ha ) hopefully you could do that all by pc and USB port, i'll search a guide to reflash kernel in the D3, and i'll post you the result
P.S. or maybe post a question to all the other guys here on xda that are surely better than me in those tech stuff
FrankieDedo said:
Ok, now i'm pretty sure that the problem is with the kernel, OR, with a kernel call to a device that doesn't work very well, maybe even the camera... did it works ok? this is the first thing that i'm thinking, because if i'm not wrong, the kexec kernel in the ICS/JB builds is not even calling the camera functions... but i'm pretty trivial now... i hope it's not something like a misplaced component (one of the flat cable connected to the motherboard) but in that case you could just grab a 1€ Torx T5 screwdriver on eBay and see if something is screwed (ha-ha ) hopefully you could do that all by pc and USB port, i'll search a guide to reflash kernel in the D3, and i'll post you the result
P.S. or maybe post a question to all the other guys here on xda that are surely better than me in those tech stuff
Click to expand...
Click to collapse
The camera was my first thought..Because every rom with full functioning camera reboots!But Camera works great!I have the screwdriver and I will take a look..but I hope is something software related and if we'll find out a way to reflash kernel it will be terrific!!
The question was for every xda-users!!!Thank you for the answers!
AFAIK the kernel is flashed as part of the rom package, try looking through the /etc folder, as I'm pretty sure it's there, but I can't remember what it's called. There are only 2 kernels for the D3 the stock gingerbread and hashcodes kexec kernel. I've moved on from this device, so I'm reaching into the depths of memory, but you can use moto-fastboot to push the boot.img of the stock kernel, you can get it from sbf.droid-developers.org. Just grab the firmware package for your particular model. I'm not sure if you can flash hashcodes kernel via the same method. I've honestly never flashed a kernel on this device, I've NEVER had the need. Best of luck.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Endoroid said:
AFAIK the kernel is flashed as part of the rom package, try looking through the /etc folder, as I'm pretty sure it's there, but I can't remember what it's called. There are only 2 kernels for the D3 the stock gingerbread and hashcodes kexec kernel. I've moved on from this device, so I'm reaching into the depths of memory, but you can use moto-fastboot to push the boot.img of the stock kernel, you can get it from sbf.droid-developers.org. Just grab the firmware package for your particular model. I'm not sure if you can flash hashcodes kernel via the same method. I've honestly never flashed a kernel on this device, I've NEVER had the need. Best of luck.
Sent from my Nexus 4 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
thank you for the help!
in hashcode's roms,the kernel is in /etc/kexec..but I have no idea how I could swap the kernel!!simply swapping Kexec folder between cm10.1(that give me no reboot) and Kexec cm9(that reboots)made Cm9 unbootable..
Original battery arrived..It did not solve my problem..
Related
I've been searching, and reading, and my eyes hurt. I normally don't like to post threads, but I'm left with no choice. If this topic has been covered, then I guess my searchin' skillz are stating to lack. Here is my delimna:
Rooted, Lagfix, enabled Side-loading, recently installed ClockworkMod, stock firmware. I ran a backup using ROM Manager/ClockworkMod. I was attempting to install the Mobile AP fix for WiFi Hotspotting from designgears. I downloaded the new kernel per instructions (Mobile AP ony). I first tried installing it using ROM Manager's boot option into Clockwork without renaming MobileAP.zip. Still received black screen when I open the Mobile AP settings that the new kernel was trying to fix. So I thought that the flash didn't work, so this time I renamed the kernel file to update.zip and did the standard method of flash using stock recovery mode.
Now the phone boots to the Galaxy S screen, then just a black screen. The bottom row buttons seem to be active, but nothing happens. Holding power....nothing. I have to pull the battery; however, I can boot into stock recovery.
Now here's the delimna. I can boot into recovery, but the update.zip file is NOT the one for ClockworkMod, its the modified kernel. Is there a way that I can browse the files on the phone so I can change the update.zip file? I want to put Clockwork's in place so I can restore using my backup made yesterday....It's not a huge order if I have to flashback to stock and lose everything as I usually do that everynow and again anyways (usually I'm prepared). I won't lose anything important that isn't already backed up except maybe some pictures....
BUT, I can't help but try. It's just me I like to break stuff and fix 'em. I want to try to run that backup I made. I have Odin, and I tried flashing the kernel back to stock (i had one hell of a time finding information on how to use it). As a matter of fact, I found instructions on HOW to use it, but I gave up trying to find useful information on how the program runs (like a user guide, what else can it do, that sort of thing....). I spent hours reading thread after thread........information overload I guess.
I figured someone might point me in the right direction. How can I browse/edit the contents of the phone while in Recovery or Download mode?
You could try letting the phone boot up, yes I know it's only a black screen, then plug in the usb to your PC and see if ADB works.
If so then just adb shell into it and work with command line.
I'm not sure if ADB would work in stock recovery mode but that's worth a shot too.
Excellent idea, but no luck. I can get the computer to recognize the phone in recovery mode, but ADB shows the device offline, and Windows Explorer shows 2 drives with the whole "insert disk into drive ..." message. Can't boot phone to enable "development mode", that might have something to do with it......unless I'm missing something?
swedishcancerboi said:
Excellent idea, but no luck. I can get the computer to recognize the phone in recovery mode, but ADB shows the device offline, and Windows Explorer shows 2 drives with the whole "insert disk into drive ..." message. Can't boot phone to enable "development mode", that might have something to do with it......unless I'm missing something?
Click to expand...
Click to collapse
Wasn't sure if that would work or not.
So, if you turn it on and just let it sit as long as a normal boot, then try adb does anything work?
I actually let it sit for ~15 minutes. computer doesn't even register the usb being plugged in. I'm going to give it another go or two, but in about an hour I'm going to have to call it quits and just flash it with Odin. Don't want to give up yet, but I am driving out of town later this afternoon and must have my phone for the trip. Maybe I'll break it again tomorrow and play with it over the weekend!
Let me know if you have any other ideas. I'll let you know when I give up.
While on that subject (watch someone tell me to move my post after this.....), maybe I'll experiment with a new ROM. Any recommendations? (without OC, device is fast enough). I haven't read much on the different flavors available at the moment (I think I read something about a 2.2 from I9000 or something?).
swedishcancerboi said:
While on that subject (watch someone tell me to move my post after this.....), maybe I'll experiment with a new ROM. Any recommendations? (without OC, device is fast enough). I haven't read much on the different flavors available at the moment (I think I read something about a 2.2 from I9000 or something?).
Click to expand...
Click to collapse
Hybrid from eugene is pretty fast especially if you add the voodoo kernel to it. Thats what I heard tho. Because when i tried it out it was pretty quick with out a lagfix and without autokiller. Only used it for 20 min tho as i couldn't get Titanium backup to work. I think the titanium problem is a hit or a miss.
well, I guess I'm going to have to load stock and wipe everything...oh well. Let's see how this goes. Then I'll start playing with ROMs this weekend. Thanks anyway!
swedishcancerboi said:
well, I guess I'm going to have to load stock and wipe everything...oh well. Let's see how this goes. Then I'll start playing with ROMs this weekend. Thanks anyway!
Click to expand...
Click to collapse
Well, if your going to do that take an extra 2 minutes and load Eugenes Hybrid R3 while your at it. It's extremely easy to do and in my opinion the fastest thing we can put on these phones right now.
Vibrant ROM? is that safe? I mean, I know they are all Galaxy S, but is the hardware really that identical?
I don't think eugenes captivate hybrid is actually a vibrant rom. I think he just borrowed some of the better parts.
Sent from my SAMSUNG-SGH-I897 using XDA App
Got it! I used the one click stock down loader to get the phone to boot. I then noticed that many of my files were still there, music, zips.....so I thought....maybe my backup is still there.
Instead of using my original root, I decided to try Unleash the Beast.applied it so I could load Rom Manager.i opened Rom manager and it showed my backup!
I tried restoring then without success (no update.zip) and had to flash clockwork (even though it showed it already loaded, guess it needed to be refreshed, makes sense since it is a fresh firmware), selected my restore and it ran like a charm.
I am just surprised. I thought the act of flashing the Rom would wipe everything. Apparently not if you never do the "master clear."
Thankfully I had just installed Rom Manager the day before and had a fresh backup. Looks liked I'm gonna have to start shelling out more beer money to the devs!
Now I can prepare to break it again and again. Let the fun begin!
Sent from my SAMSUNG-SGH-I897 using XDA App
Nice. Yeah, stuff you have stored on your "internal SD" is safe between flashes. Of course apps, contacts, etc get wiped, but that's an easy fix.
"the more you know," eh? Ha!
Sent from my SAMSUNG-SGH-I897 using XDA App
Hello everyone!
I know this issue has been discussed many times in many forums, but no-one can find a final solution to this problem.
I have a LG P990 bought in Portugal, and I installed CWM 5.0.2.8 with internal and external SD support.
My problem is everytime I want to flash something on my phone, I reboot into recovery mode, and when I enter CWM, my phone vibrates like a dildo. I tried several versions of CWM, and the problem persists.
You might say "you can always use Paul's version from Modaco"... yeah, I could. But since I use an external SD card, that is not a viable solution to my problem.
The strange thing is, this doesn't happen on all P990 devices...
I'm not sure about the vibration issue you're having...
but other CWMs should be able to access external SD as well. AFAIK, older versions of CWM couldn't access internal SD, but all could access external SD.
And for what it's worth, I use 5.0.2.7 and it can access both internal and external.
aragorn7 said:
I'm not sure about the vibration issue you're having...
but other CWMs should be able to access external SD as well. AFAIK, older versions of CWM couldn't access internal SD, but all could access external SD.
Click to expand...
Click to collapse
Right, Paul's @Modaco version (4.0.0.5) can only access one of them... If you don't have an external SD, CWM will mount the internal one, but if you have an external SD, CWM wouldn't recognize the internal.
That's the version I use, and the only one that won't make my phone vibrate like a dildo.
No matter how I install CWM, either using ROM Manager, or NVflash or whatever, the result is always the same... The phone vibrates...
I may be wrong, but it seems that temasek is the one who compiled the first p990-compatible CWM 5.0.2.8 back in January.
http://forum.cyanogenmod.com/topic/22319-cm7-discussion-of-nightlies/page__st__1720#entry289942
Is that the same one you are using? If not, try his. If yes, maybe you can ask him?
Or maybe Rusty
http://forum.xda-developers.com/showpost.php?p=27176594&postcount=695
I'll try temasek's version. I had the vibration problems with Rusty's compilation. I'll take a look and get back to you.
korgndm said:
I'll try temasek's version. I had the vibration problems with Rusty's compilation. I'll take a look and get back to you.
Click to expand...
Click to collapse
Tried temasek's version of CWM. Has the same vibrating issue... reverting back to Paul's version.
korgndm said:
Tried temasek's version of CWM. Has the same vibrating issue... reverting back to Paul's version.
Click to expand...
Click to collapse
Sorry to hear that. This is real strange.
You do have a p990 o2x and not a su660 o2x, right? The only thing else I can think of is the slight difference in hardware between phones...
Or one other thing we could try is looking at the command lines for Paul's cwm and compare to temasek/rusty's. Can you send me a link for paul's?
EDIT: Never mind. I found it. I'll let you know if I see anything....
I'm pretty sure it's a O2x, which goes by the name LG Maximo 2x.
Here's Paul's version of CWM:
http://www.modaco.com/topic/335479-29-jun-4005-clockworkmod-recovery-for-the-lg-optimus-2x/
sorry korgndm, but I dont' have any good news.
I had trouble unpacking the .img files. I tried to use bsdiff to see what might be different between the two cwms (apart from the internal/external support) but was not successful.
Logically, if it worked without vibration with paul's, then it's not hardware issue. it's just a matter of coding/compiling the recovery img properly. but now, it's beyond my abilities...
I also considered that it could be a baseband issue. I'm using V20Q with stock rom, and never used anything else.
I'm planning on flashing my phone today with another BB, maybe 20s or 21y, then installing CWM again using the bat files, not using ROM Manager, and see what happens.
ok. kindly report back with how it goes when you get a chance, because i remember reading somewhere that changing BB/RIL didn't help with this. But wish you better luck with your phone!
aragorn7 said:
ok. kindly report back with how it goes when you get a chance, because i remember reading somewhere that changing BB/RIL didn't help with this. But wish you better luck with your phone!
Click to expand...
Click to collapse
All hope is lost
No luck flashing with another BB, or another version of CWM. The "dildo sindrome" persists... S**T!
EDIT: Found a solution to the problem:
http://forum.xda-developers.com/showthread.php?t=1508824
Congrats on finding the solution! So your o2x is su660 after all?
Do you have four or three buttons in the bottom?
If it is three, you have a su660 and that's what I was asking before.
Sent from my LG-SU660 using xda premium
I definitely have four buttons on the bottom. I double checked the label under the battery and it says "LG P990 Made in Korea".
I DO have a small problem with this CWM version, though... It won't mount the internal storage, neither will it mount USB. In another words, it will only recognize my external SD (which, BTW, is a piece of crap!), and if I want to copy a file to it, I have to either boot the phone normally and use a file manager, or remove the SD card and pop it in my laptop.
Any suggestions?
Have you tried adb while in Recovery mode?
If you can connect that way, maybe you can manually mount through shell.
Sent from my LG-SU660 using xda premium
I must confess I'm new to this "world", and I really don't have many computing or programming skills, but I suppose you're talking about using a terminal / terminal emulator... If you could kindly explain the procedure, I would appreciate it.
Yes I was talking about using the terminal. I will have to look for the instructions, written by much smarter and more knowledgeable people than me.
In the mean time, this excellent post with guides may be helpful.
http://forum.xda-developers.com/showthread.php?t=1037751
And if usb connection doesnt work for whatever reason and all you want to do is copy files to the phone, perhaps this tip from xda TV might help too :
http://youtu.be/UI70UYug_zQ
The example in the video is with a Ubuntu machine, but you can follow the same steps for using PC with Putty and WinSCP.
Edit: link updated
Sent from my LG-SU660 using xda premium
aragorn7 said:
In the mean time, this excellent post with guides may be helpful.
http://forum.xda-developers.com/showthread.php?p=7546
Click to expand...
Click to collapse
"No thread specified. If you followed a valid link, please notify the administrator"
Sorry for the wrong link. It's updated.
And for guide on ADB, check this out:
http://www.xda-developers.com/android/adb-easy-tutorial/
Can someone advise me on whether it is possible to update to the new Rom without the use of a USB.
My g\f's phone doesn't have usb its bust for some reason.
Is there any other way to load the latest 5.0 cwm, the new bootloader and then install a zip from cwm.
Any help is much appreciated.
Sent from my LG-P990 using xda app-developers app
monkeyass said:
Can someone advise me on whether it is possible to update to the new Rom without the use of a USB.
My g\f's phone doesn't have usb its bust for some reason.
Is there any other way to load the latest 5.0 cwm, the new bootloader and then install a zip from cwm.
Any help is much appreciated.
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
1) You should clarify the title. Something like "How to update to v28E without USB". Imagine every thread like "LG P990 question", it's absurd.
2) You should tell us if you want the vlite or the full version of v28E.
3) CWM 5.0 is not the latest.
4) Yes, it is possible, put everything in the sd card =P.
Good luck.
Hello, apologies for that.
Thank you for the fast response.
I would like to install the full version, I am aware that you need to specifically partition the ad, but I can read grains thread for that.
Can I just confirm then, that if there is a zip for the new downloader, cwm and Rom in one zip.
That can be run from cwm?
Thank you
Sent from my LG-P990 using xda app-developers app
monkeyass said:
Hello, apologies for that.
Thank you for the fast response.
I would like to install the full version, I am aware that you need to specifically partition the ad, but I can read grains thread for that.
Can I just confirm then, that if there is a zip for the new downloader, cwm and Rom in one zip.
That can be run from cwm?
Thank you
Sent from my LG-P990 using xda app-developers app
Click to expand...
Click to collapse
First -- In case you want to go full metal on P990, that means repartitioning, new BB and full flash, you need to flash. There is no other way than using NVFlash, as described in lovely thread in development by Stephan G.
Reasons - reformatting is not easily done from within phone which runs on these partitions, same goes for reflashing recovery from within recovery.
Second -- not sure why without USB?
Third -- there is CWM-possible way by using TonypAndHarsh's vlite V28E rom, yet this goes without new BB and with possibility of no call audio issue.
So, to repeat my answer to your main point, no. There is no way to fully install new system/BB without USB connection and PC. You have to flash it.
Hello. I think you can instal the new ICS without your usb cable.
1. you need to instal rom manager from PlayStore and flash from here the CWM recovery. I recomend you to instal the version 5.2.0
2. Make a nandroid backup before you do something to your actual rom.
3. Use titanium backup to backup all your apps and settings.
4. Put ICS rom from here http://forum.xda-developers.com/showthread.php?t=1959545 in your sd card (i think you have at leat a card reader and on adapter to put your microsd card) and follow the isntruction from the download page.
Good luck!
Cool thank you will try tomorrow.
Ant
Sent from my LG-P990 using xda app-developers app
ergosum said:
1) You should clarify the title. Something like "How to update to v28E without USB". Imagine every thread like "LG P990 question", it's absurd.
2) You should tell us if you want the vlite or the full version of v28E.
3) CWM 5.0 is not the latest.
4) Yes, it is possible, put everything in the sd card =P.
Good luck.
Click to expand...
Click to collapse
I'm sorry but I disagree with you... I think that anyone that thinks about the title for 2 seconds can understand that if the guy is asking if it's possible to flash v28e without USB of course he means the "full" stock ICS leak, the one which requires you to redo your partitions and whatnot... the one that is only possible through nvflash, thus, it is not possible to update to v28e without USB.
Or, you could just reply... hey, it's not possible to flash "the real deal", but you can flash tonyp's "lite" version, which uses the old bootloader and a patched kernel (thus some bugs might come from that) and all you need to do is put the files in the sd card...
I don't know why you had to be so "blunt"...
LarsPT said:
I'm sorry but I disagree with you... I think that anyone that thinks about the title for 2 seconds can understand that if the guy is asking if it's possible to flash v28e without USB of course he means the "full" stock ICS leak, the one which requires you to redo your partitions and whatnot... the one that is only possible through nvflash, thus, it is not possible to update to v28e without USB.
Or, you could just reply... hey, it's not possible to flash "the real deal", but you can flash tonyp's "lite" version, which uses the old bootloader and a patched kernel (thus some bugs might come from that) and all you need to do is put the files in the sd card...
I don't know why you had to be so "blunt"...
Click to expand...
Click to collapse
Thank you for that information, I am currently trying to find out if there is a way to install the right version of CWM, then try to install the new bootloader from within CWM? I am not even sure if that is possible.
I think she is just going to have to get her phone sent back, the only problem is the o2x is discontinued, I doubt they will replace it or fix it. They will probably try and replace it, but only give her something that I wouldn't consider a good replacement. But we'll have to speak to her insurance company first.
I have seen these phones selling on ebay, they are about £100 from what I can gather, it depends what she wants to do. Could buy a new one and sell her one, just a shame really, i found another thread about the USB problem and they had to send it back and get it repaired, must be either a problem with the connection or the board, I would think the board as it charges fine, which is really weird.
Anyway, thank you for you help, i will keep searching to see what i can find.
monkeyass said:
Thank you for that information, I am currently trying to find out if there is a way to install the right version of CWM, then try to install the new bootloader from within CWM? I am not even sure if that is possible.
I think she is just going to have to get her phone sent back, the only problem is the o2x is discontinued, I doubt they will replace it or fix it. They will probably try and replace it, but only give her something that I wouldn't consider a good replacement. But we'll have to speak to her insurance company first.
I have seen these phones selling on ebay, they are about £100 from what I can gather, it depends what she wants to do. Could buy a new one and sell her one, just a shame really, i found another thread about the USB problem and they had to send it back and get it repaired, must be either a problem with the connection or the board, I would think the board as it charges fine, which is really weird.
Anyway, thank you for you help, i will keep searching to see what i can find.
Click to expand...
Click to collapse
Just cause you didnt mention it before, but are you running a hacked version of ICS right now on the phone? If you are, it could be a matter of the ADP drivers on your computer? If it was a stupid idea sry. It was just something that pop'd into my head
headshot21 said:
Just cause you didnt mention it before, but are you running a hacked version of ICS right now on the phone? If you are, it could be a matter of the ADP drivers on your computer? If it was a stupid idea sry. It was just something that pop'd into my head
Click to expand...
Click to collapse
Unfortunately not, it is running a version of gingerbread, can't remember which one.
monkeyass said:
Unfortunately not, it is running a version of gingerbread, can't remember which one.
Click to expand...
Click to collapse
I got a bug on my O2X USB as well, and I managed to solve it temporary, (the bug comes back after some time, but the process has worked for me everytime the bug comes back, I'm currently testing to try to identify the cause of the bug), it is kind of a long process but I could get back my usb sync, if you want I made a tutorial of what I exactly did, after this process you can install any stock or custom rom without any problem just make sure to follow the instructions as they are described
http://forum.xda-developers.com/showthread.php?t=1981359
ocr66 said:
I got a bug on my O2X USB as well, and I managed to solve it temporary, (the bug comes back after some time, but the process has worked for me everytime the bug comes back, I'm currently testing to try to identify the cause of the bug), it is kind of a long process but I could get back my usb sync, if you want I made a tutorial of what I exactly did, after this process you can install any stock or custom rom without any problem just make sure to follow the instructions as they are described
http://forum.xda-developers.com/showthread.php?t=1981359
Click to expand...
Click to collapse
Thank you, tried your fix but unfortunately didn't work, looks like it will have to be sent back.
thank you though
monkeyass said:
Thank you, tried your fix but unfortunately didn't work, looks like it will have to be sent back.
thank you though
Click to expand...
Click to collapse
Too bad to hear it didn't worked, do you mind if I ask, what exactly failed? I mean, it would be great to have some feedback of what you did and where you got stuck, so I might make some updates of the post, or upload another backup, or so
If you have any doubt about my post, I would be pleased to help you with that
thanks for giving it a try
cheers
Hi
I downloaded a stock Rom that had been modded.
So I could be sure that I would have cwm in case anything went wrong.
Rom loaded and was able to get into the secret menu.
I will say that under USB connection type there was misspelling where it said:
LG USB adnroid
Not sure if that would affect it.
I selected that item.
Then went to port.
Selected the different options in ordered and waited about 10 seconds on each turn, then pressed find any changes in device manager unplugged and plugged the USB.
Then tried in different orders but with not luck.
Took the battery out and tried holing the vol up down the plugging in USB but to no avail.
Then pressed power and vol down.
The phone tuned on and showed LG sign then switched off.
I tried pressing check any changes as the LG sign came on but nothing.
Then tried nvflash as the LG sign came on but nvflash showed no connection.
Very weird, definitely dead but still charges, doesn't make sense.
Oh well
Ordered an atrix with work and play kit for 68 quid, has a broken digitizer which will cost 20 pound, on average, off ebay.
Thanks for the help though.
May take the 2x apart when new phone comes and see if there's any physical damage on te board.
Sent from my LG-P990 using xda app-developers app
I realize this isn't the developer section and that there is a risk in flashing roms.
I had downloaded rom manager and for some reason went on to flashing cwm for the S3.
The camera stayed in a boot loop.
I reflashed a recovery image, twrp, and then went on to clearing cache and doing a data/factory rest (I may have lost the usb debugging in the midst?)
I reflashed a stock rom, all flashing process is fine, the camera boots, hardware keys wok, only problem is the touchscreen is unresponsive.
Any files I can provide to help solve this bad move on my part, or is it toast?
Thanks.
I've managed to hook up a mouse with OTG cable so I can at least do something with it, but I sure hope I can find a fix for this besides having to send it to samsung for repair.
Are there any files I can provide to see if anything looks out of place, build.prop maybe? I really don't know where to start with this.
morbs_gt said:
I've managed to hook up a mouse with OTG cable so I can at least do something with it, but I sure hope I can find a fix for this besides having to send it to samsung for repair.
Are there any files I can provide to see if anything looks out of place, build.prop maybe? I really don't know where to start with this.
Click to expand...
Click to collapse
Have you tried the toolkit here: http://forum.xda-developers.com/showthread.php?t=2099765
You could flash a stock recovery / ROM
I have used this guys toolkit on other devices and they are easy to use and are rock solid.
apprentice said:
Have you tried the toolkit here: http://forum.xda-developers.com/showthread.php?t=2099765
You could flash a stock recovery / ROM
I have used this guys toolkit on other devices and they are easy to use and are rock solid.
Click to expand...
Click to collapse
Yes, I have his toolkit as well. I've used it for my SGS before.
The thing is I may need to flash the original rom, which is from New Zealand. I found the file on sammobile, just the first download I think was corrupt as it would fail md5 checksum and odin wouldn't flash it. I just downloaded another copy of the NZ rom version and am currently trying that out.
Any other version of the original rom i tried, the touchscreen wouldn`t work. The camera is brand new so I`m hoping it`s just software related.
*edit: I just flashed the original rom with odin, touchscreen is still no working. I`ll try the toolit again and see what gives.
u think it might be a kernel issue ? try and reflash the kernel.
pileiba said:
u think it might be a kernel issue ? try and reflash the kernel.
Click to expand...
Click to collapse
I really don`t know what happened, besides the fact that I flashed a recovery that was clearly not meant for the galaxy camera, lesson learned.
I realized my 14 day return was still in effect, so I just returned it to the shop and got a new one. :S
morbs_gt said:
I really don`t know what happened, besides the fact that I flashed a recovery that was clearly not meant for the galaxy camera, lesson learned.
I realized my 14 day return was still in effect, so I just returned it to the shop and got a new one. :S
Click to expand...
Click to collapse
I made the same mistake! I have no 14 day return thing with my device.
PLEASE HELP!
Hi;
I had downloaded CWM rom manager and for some reason went on to flashing cwm for the S3.
Camera restarting and then touchscreen doesnt work. Buttons are working but touchscreen isn't.
Anybody help me?
Please..
I've managed to hook up a mouse with OTG cable too. I hope install new CWM SGC rom. But there is no rom in CWM.
I think we can install touchscreen driver, But where?
Hi
I found a little secret, how to enter the d3 (maybe d1 also) boot menu:
1 Power Off the Phone.
2 Press power, when the blue light appears, press Volume Up.
Presto!! The boot menu have:
Fastboot, Cwm, factory boot?, normal boot and power off.
On the Cwm you have to press Volume Up, to display the menues.
Also if you press Power+VolUp+VolDown at the same time for like 10 seconds( anytime) , the Phone power off.
I try to flash a root zip package, but the Phone instantanly reboots... And the su binary wasnt flashed, maybe it because the zip used busybox to mount the system.
Maybe tomorrow i will try to create another zip... (I Dont like the chinese app root method )
Enviado desde mi XT919 usando Tapatalk 4 Beta
Friend, you are on the wrong forum. This one is for Motorola Razr XT910, not for D3.
The D3 doesnt have a forum yet, is no droid 3, it razr d3 xt919.. @fredamsouze
Enviado desde mi XT919 usando Tapatalk 4 Beta
Really easy to get in boot menu, does anybody used restore option?
Enviado de meu GT-N8000 usando o Tapatalk 2
jlobodroid said:
Really easy to get in boot menu, does anybody used restore option?
Enviado de meu GT-N8000 usando o Tapatalk 2
Click to expand...
Click to collapse
@jlobodroid
The recovery it's the e3 recovery not CWM, so it can't flash regular zip, maybe just motorola signed zips.... There's another thread for building cwm for the mt6577 CPU:
http://forum.xda-developers.com/showthread.php?t=1825722
I have an xt919 cwm image, but can't use it, i try booting it via "fastboot boot boot.img" but the phone hangs,
This thread have been moved to the droid 3 forum, that's incorrect i think the RAZR forum is more apropitated, i encourage all RAZR D1 / D3 user, please write in the forums petition for us to get a forum for our devices....
http://forum.xda-developers.com/showthread.php?t=1660354
I bought a D3 too.
I'm with you for the the new forum. About the device, the only thing that is boring me is that looks like it doesn't have bluetooth HID support, regardless it have Android 4.1.2 . I have a Ípega gamepad and can't make it work.
I tried to mix around some files from another RAZRs but didn't get this working until now. A cwm would be very useful at the moment
Also usb gamepad don't work, i think usb otg is disabled.
Well.. I tried to mix some files from other roms to make the Bluetooth works without success until now. I need a custom recovery to make deeper research :/. I'll keep looking for that. Maybe a cwm for a spreadtrum device
@farenheith in this thread http://forum.xda-developers.com/showthread.php?t=1825722, you can find a recovery for xt919, but i was unable to boot it... maybe you have more time or lucky to get it working
I saw that one...
I read the interactions in the thread about this cwm, as the final result is that was unable to boot, I didn't even try. Also I need to flash a firmware first in my phone to make sure I can play hard with it . I still couldn't do that, I have the files but I couldn't take time with it yet.
But, at least with bluetooth, I think we need to change the service in the ROM, or insert a new one. I really don't know much about ROMs, I'm researching to see if I can get it to work in the D3... I thought the services was described in the init.rc, but I couldn't find this file in the phone, so...
farenheith said:
I saw that one...
I read the interactions in the thread about this cwm, as the final result is that was unable to boot, I didn't even try. Also I need to flash a firmware first in my phone to make sure I can play hard with it . I still couldn't do that, I have the files but I couldn't take time with it yet.
But, at least with bluetooth, I think we need to change the service in the ROM, or insert a new one. I really don't know much about ROMs, I'm researching to see if I can get it to work in the D3... I thought the services was described in the init.rc, but I couldn't find this file in the phone, so...
Click to expand...
Click to collapse
Take a look at this site, i havn't flashed any of this...
http://fwteam.grupoandroid.com/RAZR D3/XT919/
Here are flashing instrucctions, for the brave
http://www.droidevelopers.com/f274/14711-razr-d1-razr-d3-firmware-update-leaked.html
Dude, take a look in this app:
https://play.google.com/store/apps/details?id=com.mobileuncle.toolbox&hl=pt_BR
You have an option there to replace the stock recovery for many others ones.... I can't try it right now. First I need to make sure I'll be able to flash the firmware again if I screw up. I couldn't do this for a matter of time. Maybe I can in the end of week.
But, if you already tried to flash a firmware, if you know how to recover your stock recovery, then maybe you can take a look into it.
Gathering info... to activate some options, if possible, maybe we need a new kernel. Here we have a source for the kernel 3.4 for mtk, not for our device. If we need to reach this point, then this can be a start if we don't find anything more compatible
farenheith said:
Gathering info... to activate some options, if possible, maybe we need a new kernel. Here we have a source for the kernel 3.4 for mtk, not for our device. If we need to reach this point, then this can be a start if we don't find anything more compatible
Click to expand...
Click to collapse
Here're the Motorola sources
http://sourceforge.net/projects/razrd.motorola/files/?source=navbar
But somebody told me that this is only the kernel sources, we need also the modifications to android source, not sure if it included on the sourceforge site....If a have more spare time i will try but not sure when, i hope someone can start the proyect. But we need first some CWM, thats the starting point.
CosmicDan told me that generic chinese phones that use MTK6577 doesn't have fastboot, just flashmode. Using flashmode, you can flash even kernel in this case. As D3 it's a MTK6577 too, maybe we can bypass the fastboot using the flashmode? If you connect your phone turned off without any button combination to the USB, you'll see a missed driver. In theory it's the flashmode driver.
We have a chance that the limitation about hid devices using USB and bluetooth is from the Kernel. If we confirm this, we can try just to flash a patched Kernel and keep the same ROM. If we're able to flash the kernel this is a possible way.
Oh, about the CWM.
The app I told you before maybe can download some compatible CWM... It's just a matter of time to testing each one
I tried some stuff but didn't get anywhere...
Now trying to bring the phone back to life lol
farenheith said:
I tried some stuff but didn't get anywhere...
Now trying to bring the phone back to life lol
Click to expand...
Click to collapse
What did you try? I also have a bluetooth Ipega gamepad and the xt919 pairs it, but never connects to it.
If you manage to revive your phone please let us know how you did it. Im afraid to kill mine but i really want to start messing with it to find a solution to the bluetooth problem.
Btw, my carrier is TELCEL from Mexico.
LifeZero said:
What did you try? I also have a bluetooth Ipega gamepad and the xt919 pairs it, but never connects to it.
If you manage to revive your phone please let us know how you did it. Im afraid to kill mine but i really want to start messing with it to find a solution to the bluetooth problem.
Btw, my carrier is TELCEL from Mexico.
Click to expand...
Click to collapse
I handled it.
I used "RSD Connected 1.15.06 PROD" to flash the lastest firmware, the one that came with the phone. I followed this tutorial. Just in portuguese for a while... I'll translate it to english when I have some time.
The part of the "DeviceIdAllocationTool" was unnecessary on my notebook, so I did go straight to the RSD part.
Also... I could flash the firmware just in one of the USBs of my notebook.
Just bricked the phone again...
It's a pain to make this RSD work... idk why... I thought it was the usb port but now I doubt that
Edit: Done .
The problem was actually the USB of y notebook lol... I tried on my brother's PC and worked at first time.