Hi,
So I upgraded from cm7.2 to 10 on my defy green lens. After a long and difficult upgrade, almost everything works - except any functionality of the usb port...
I'll jump right into the real deal: without usb connectivity, I cannot try to flash other SBFs to fix it! I can enter the bootloader screen just fine (says 09.10 on top, I believe that the last SBF I flashed was 3.4.2_179-002 , as recommended, before I rooted it, 2ndinit, and sucessfuly installed cm10) and the phone recognizes when I plug in a usb cable to it. but the computer always shows up a "usb device not recognized" error, and I tried on two machines, winxp/win7, and several different usb cables. I read some threads about crashing drivers between rsdlite and different tools motorola made; I never installed any of that junk but just to be on the safe side I removed all drivers and started fresh. still no go.
______________(That's the problem, now I'm just going to give more information about it)______________
The phone does not charge off a computer nor from a wall charger, with an assortment of different usb ports, cables and chargers. when connected to a computer (whether the phone is on or off) a "usb device not recognized" message comes up, on both windows xp/7 (different machines.) Seldom, when connected to wall charger, I can get the battery icon to show charging for about a second, (after a restart and plugging in to the pc briefly beforehand.) If I'm so lucky to make that happen, either it goes off in about one second, or it will change statues from charging to not charging several times very rapidly and then stay on not charging.
If the phone is off and I connect it, the white led sometimes come on, and then the phone comes on- presumably to go into battery charging screen, but instead it boots up normally. (this may be the correct behavior with this rom. idk.)
If you care for more information, let me elaborate about what I mean by "After a long and difficult upgrade":
I previously upgraded to cm10 (30/7/2012) CM10-20120730-NIGHTLY-mb525.zip,
but downgraded shortly after, back to 7.2. (I decided to wait for something a bit more functional)
Back then both the upgrade/downgrade went fine. This time I got into a bootloop (or stuck on bootscreen) after updating to 26/03/2013 God's version (oops I meant Quarx's version.)
Trying to use my nandroid backup for 7.2 I got a md5 mismatch and even after generating a new md5 file I couldn't restore /data.
Moving on. using CWM I tried installing some kernels (kernel-froyo-222-179.zip, and same thing but signed,),
then a fixed sbf (not full) 3.4.2_177-Fixed.NORDIC_DEBLUR.sbf,
and a very crappy sbf JRDNEM_U3_2.26.0_BLUR_P3_SIGN_SIGNED_USAJRDNEMARAB1B5TEL02A.0R_USAJORDANTELSTRA_P033_A017_M008_HWp3_Service1FF.sbf
** this one almost gave me a heart attack, after successful flash defy black screened with no LED indications. I was able to work my way into the bootloader and flash another SBF with rsdlite, without any indications from the device. lucky me.
Then I flashed the sbf I mentioned above and that's how I eventually got into cm10.
I can't even downgrade to stable cm7.2. Tried flashing a fresh install through CWM (wiping everything before and after, of course) and ended up stuck on boot screen. I don't know if it has anything to do with CG numbers or what, but I really can't figure out why CM7.2 wouldn't boot on the same SBF CM10 is booting fine right now.
I can't also share the SD card through CWM. (-> device not recognized)
I'm losing my marbles over here. Been working on it for two whole days and can't think of anything else I can try out... If I flashed the wrong rom using CWM I might get locked out because bootloader won't be any help!
:crying: cry for help... thanks :fingers-crossed:
Have you tried installing adb and the motorola drivers so you can try to communicate with the device?
Thanks for your word zero gravity!
Well, I thought that since "usb device not recognized", and since it shows up as unknown device under device manager (currently it disappears and reappears every 3 seconds, but I think this is a new behavior) I automatically assumed that I couldn't get proper communication with it! I guess I got to do some reading about adb commands any help with it would greatly be appreciated (No worries though I know how to google )
http://forum.xda-developers.com/showthread.php?t=1241935
Here's a simple guide for adb. Hopefully you can get some sort of communication to flash your stock sbf and start over again.
So, even though I have the drivers installed (Motorola_End_User_Driver_Installation_4.9.0_32bit.msi_.zip, and also installed MotorolaDeviceManager_2.3.9.exe,) Android SDK Tools installed, then I tried adb devices - nothing comes on.
by enabling ADB over network I can adb connect to the phone through wifi and go into shell. but I can't see how I can debug the buggy usb interface with network access.
Also tried starting the adb service through recovery - no go, won't show up.
(I plugged in a different Android phone (an Xperia), installed the drivers and had it running on adb usb in no time. So I'm doing it right.)
Any thoughts? are there commands to specifically listen and figure out what's coming from the usb port?
any other leads anyone may have? I'm listening!
Cheers, Shawn
The port must have suffered hardware damage. Examine the port for obvious conductivity hindrance. If not I'm afraid you'll have to get it repaired
As for cm7.2 after flashing just format to ext3 from boot menu(before this wipe dalvik cache), and after a reboot wipe data from stock recovery for good measure
Sent from my MB526 using xda premium
Well, thekguy seems to be on the right track.. I can fiddle around with the usb plug and get it to charge, So the problem seems to be mostly physical - if not completely.
I still can't get it to connect properly to the computer, but go figure which usb signal is dropping off. might be power, might be data.
After spraying it several times with contact cleaner the port is good enough for steady charge. No change about how it doesn't connect to a computer.
I feel like a dumbass, cus I already gutted the phone up a couple of days ago to try tracing conductivity paths through the port. the usb port is cast in plastic that is not removable from the pcb. There's no access to the USB pins, excepting four conducting points through the plastic right next to the port, but they are all connected to ground - they probably belong to a bracket that's holding the plastic to the pcb.
anyhow I did all that (I got closeup pictures if anyone's interested) but I wasn't able to check conductivity, and I didn't try fiddling with it after that. bah!
___________________________
Still wondering about one thing! The bootloader is locked, so that means it was never-ever changed since the phone was manufactured, correct? So no effect of writing different SBFs on the bootloader, correct? (minding the Efuse and CG numbers)
if so, than can I conclude only by that information (and that I cannot connect the phone to the computer anymore with bootloader) that there must be hardware/physical damage? I've just completely eliminated the software factor out of the equation. haven't I?
Did I miss anything? let me know.
P/S, I'm going to stick with this phone as it is. I can work around never having usb data connection.
Cheers
Can you try installing Linux and see if the you can mount /system or even /sdcard on Linux from bootmenu? Bootmenu mount only works in Linux. I've tried it in Ubuntu 10.10
Its worth a try, if Linux doesn't see it then it must be a hardware issue and would need a Motherboard replacement.
Use ubuntu live disk to make things easy and not mess your Windoze
Sent from my MB526 using xda premium
You're right, sbf flashing cannot break usb functionality. I'm not very well versed in mobile hardware but I think the port can be replaced, though I don't know how. It may be possible that a local mobile store could fix it.
Trying Linux is a good idea, though it may not work out from the looks of it(the phone)
Sent from my MB526 using xda premium
If anyone is reading this, I had some bad batteries and a usb port that is having physical problems. I'm flashing it with contact cleaner spray every now and again and it helps. I can get a usb connection to the computer and charge it with a bit of luck and while I keep it stationary.
A couple of weeks ago my N4 decided that it didn't want connect to my computer. I tried windows xp, 7, and osx. I tried 5 different usb cables that worked with other android phones just fine. I tried all usb ports on said computers. I've uninstalled and re-installed all drivers, using all the known methods. Then I noticed that I was getting terrible battery life. Like 5% gone in 20 minutes with all radios turned off and leaving it in my pocket. I was on the latest verison of PA with the latest verion of franco.kernel and I've had no previous problems with my phone.
So I thought maybe I did something to it like a bad flash, so i downloaded a stock 4.2.2 zip and flashed it (with gapps). The problem persisted. So I proceeded to wipe the phone in cwm in an act of desperation, and lo and behole I was then stuck with the same problem as before, but this time with no working os to boot to, and no way of connecting it to fastboot or adb in order to put any files on the sdcard/ flash it back to stock. I am, however, still able to boot into cwm and the bootloader. Then, thinking it might be a problem with the usb daughter board as whenever I tried to plug my phone into a computer it gave me this:"windows has stopped this device because it has reported problems. (code 43)", I ordered a replacement. Replacement came, I swapped them out, and absolutely nothing has changed. I tried uninstalling/deleting drivers and re-installing them just to make sure, but same results as before. Also, the N4 DOES charge when plugged into a power source like normal.
So the way I see it, I can either keep trying to replace parts, or one of you wonderful people know some crazy fix to my problem. If not, then I could go the other way, and attempt to brick the N4 even further in order to get it replaced (I.e. it's not possible to see whether or not it's unlocked/has a custom recovery). Also, I can enter "download mode" by holding down the volume buttons and connecting a usb cable, but windows still doesn't recognize the device.
I never thought I'd have to go as far as create a thread pleading for help, but after a lot of Google searching I still cannot find someone with the same problem.
I will explain:
I am trying to use fastboot, which I (don't think) I've any problems with in the past.
I can issue commands in normal use via adb from my PC fine.
I can adb reboot bootloader ok, and can get into the bootloader any other way just fine.
I can use the volume keys to navigate the options in the bootloader just fine.
The problem comes with I connect the USB to my PC whilst in fastboot.
Windows fails to recognise the device, and says it may have malfunctioned.
It won't allow me to reinstall the drivers successfully it seems, and seems to have a problem with the USB Host Controller too.
Fastboot immediately freezes, and I'm unable to even navigate using the volume keys, let alone issue commands from my PC.
My question then is twofold:
1. Is there likely to be a problem with the USB port on my device, or some sort of bootloader corruption?
2. Is it possible to return to stock Android without using fastboot?
Finally, I would like to stress that I've seen plenty of similar looking threads, but it seemed that the posters of those threads merely had problems getting in to the bootloader or recovery.
I haven't got that problem, the problem only arises when a USB is connected to the PC, the tablet becomes unresponsive only in bootloader mode.
If anyone has any advice to offer at all, I'd greatly appreciate it.
Additionally, if the problem is solved, I will post a detailed set of instructions in case anybody else should encounter a similar problem in the future.
__________________________________________________________
Update for anyone who happens to read this in the future:
[This guide](http://forums.androidcentral.com/ne...3923-guide-nexus-4-factory-image-restore.html) has a useful FAQ at the bottom which helped a little.
I think I managed to determine the problem was likely a duff usb connection, either on my Nexus or on my computer.
I was able to just about hobble through by keeping the cable in the same place.
In case it wasn't just this, this is what I did:
1. Flashed TWRP recovery from their app.
Went into bootloader and failed to do anything
2. Flashed CWM recovery.
Managed to be recognised in fastboot.
I still had problems with my Nexus 'malfunctioning' -- possible the USB.
I updated the drivers using the ones from [this thread](http://forum.xda-developers.com/showthread.php?t=2588979).
3. Flashed a new bootloader image immediately (there were rumours that a dodgy version had been released accidentally). [This](http://www.androidfilehost.com/?fid=23060877489996594) is the one I used.
Then I managed to get the stock ROM flashed, and the bootloader locked up again.
Fastboot freezes whenever USB plugged in
I'm having a problem with this step...
1. When booting to fastboot with any sort of USB plugged in, your buttons on the side may not respond. In this case, pull the cable and hold down power + Vol Down until it reboots. The buttons should now respond and you can plug USB back in if you wish.
the problem is that whenever the USB cable is plugged in, the buttons don't navigate through the options.
however, whenever the usb is NOT plugged in (and rebooted bootloader) the button work just fine.
I don't have a recovery currently installed.
The issue is not with drivers on the computer,
happens while usb plugged in both windows and linux or simply just plugged into a wall outlet to charge and with different USB cables.
I need to load fastboot but i'm having this issue. Is the device bricked without hope?
any help would be appreciated.
Nexus 7 2012 Model (grouper)
Boatloader version 3.34
Hi all, i have a my sad story and a little of hope to get help from you.
Firstly i have bought LG G2 D800 at ebay, seller warn me that it is rooted, but due to android devices is new to me, i have no pay attention to it.
After couple days of using I received and notice to update software for my device from AT&T manufacturer and without hesitation it was accepted.
To my surprise but not for the rest advanced android users i got boot loop with LG logo and after heavy digging of internet i have found the way to fix it.
The instruction is this
My fail to this instruction was that i had downloaded sbl1.img, aboot.img, rpm.img, tz.img with 9Kb size with same crap code inside for each file and drop them to my D800 using ubuntu. When i pool out data cable the screen goes down and nothing else. Ubuntu is not recognize partitions anymore. Then after all it i realize what was happen.
Current situation is:
Due to i'me new to unix systems i'm not see any activity that ubuntu is detect my phone or anything that can tell that its not dead at all while i plugin data cable.
As for the windows when i plugin data cable its recognize in Device Manager my D800 as 'Unknown device' under USB section.
When i hold for awhile power button without cable and then release it and then hold volume up when plugin cable then windows recognize it as QHSUSB_BULK under Other Devices or under Ports (COM & LPT). No any disk mounting appears as when it was during boot loop problem.
Display, leds, speakers of the phone does not do anything, not even black screen, looks like it has power off.
This post is last hope to bring the phone alive. I assume if there is any chance to fix it to get back and place correct files to my device.
I also assume if there any android or else code to place to usb flash drive to use it with OTG cable. I sow a video where samsunge galaxy was used with some device (i assume it was usb flash drive with some code inside) and dead phone screen appears with android logo...
My phone is LG G2 32Gb black with installed KitKat 4.4.2
Please help me. I will be very gratefully for any help.
Thank a lot.
magnus-deth said:
I also assume if there any android or else code to place to usb flash drive to use it with OTG cable. I sow a video where samsunge galaxy was used with some device (i assume it was usb flash drive with some code inside) and dead phone screen appears with android logo...
Click to expand...
Click to collapse
It seems it was an usb jig, if so is it works only for samsung?
Does the story about usb flash drive with an Android OS installed on it+OTG is fantastic for dead phone in my case?
Yesterday i flashed my Jiayu S3 to lolipop (i tought) and i just bricked my phone!
After reboot it was just dead.. when i plug into pc with USB i hear the connect sound and after 2 seconds the disconnect sound. This keeps on going until i pull the USB plug. When i look in DeviceManager i see it refresh after every sound, but nothing pops up (unknown device or whatever). I deletet all usb drivers with usbdeview, restart pc but still no changes.
I tried with or without battery, but without it does nothing at all.. i tried holding Vol+ or - or both or with power button, but nothing.
Read some threads about unbrick and install correct usb driver for jiayu s3, but all the options they came with does not work on my device!
I'm a little despered now and don't know what to do.. i get the feeling that my 2 weeks old phone is dead? :'(
My pc has windows 7
Did the flash with SP Flashtool 5.1516
Did not untick preload in flashtool, i guess i got the wrong preload or something??
Please help!
No one..? :crying:
Lowrida said:
Yesterday i flashed my Jiayu S3 to lolipop (i tought) and i just bricked my phone!
After reboot it was just dead.. when i plug into pc with USB i hear the connect sound and after 2 seconds the disconnect sound. This keeps on going until i pull the USB plug. When i look in DeviceManager i see it refresh after every sound, but nothing pops up (unknown device or whatever). I deletet all usb drivers with usbdeview, restart pc but still no changes.
I tried with or without battery, but without it does nothing at all.. i tried holding Vol+ or - or both or with power button, but nothing.
Read some threads about unbrick and install correct usb driver for jiayu s3, but all the options they came with does not work on my device!
I'm a little despered now and don't know what to do.. i get the feeling that my 2 weeks old phone is dead? :'(
My pc has windows 7
Did the flash with SP Flashtool 5.1516
Did not untick preload in flashtool, i guess i got the wrong preload or something??
Please help!
Click to expand...
Click to collapse
so you cannot boot into recovery or fastboot either?
Lowrida said:
Yesterday i flashed my Jiayu S3 to lolipop (i tought) and i just bricked my phone!
After reboot it was just dead.. when i plug into pc with USB i hear the connect sound and after 2 seconds the disconnect sound. This keeps on going until i pull the USB plug. When i look in DeviceManager i see it refresh after every sound, but nothing pops up (unknown device or whatever). I deletet all usb drivers with usbdeview, restart pc but still no changes.
I tried with or without battery, but without it does nothing at all.. i tried holding Vol+ or - or both or with power button, but nothing.
Read some threads about unbrick and install correct usb driver for jiayu s3, but all the options they came with does not work on my device!
I'm a little despered now and don't know what to do.. i get the feeling that my 2 weeks old phone is dead? :'(
My pc has windows 7
Did the flash with SP Flashtool 5.1516
Did not untick preload in flashtool, i guess i got the wrong preload or something??
Please help!
Click to expand...
Click to collapse
Just flash it again, but this time with "Firmware upgrade " in SP Flashtool instead of "Download". Change from KK to LL needs reepartitioning, so firmware upgrade.
The reason why you don´t "see" the S3 any longer on the pc is, that the USB storage mode from KK, which is driverless for windows, don´t work right now on LL.
Once flashed to LL you will need to install a driver, for windows to connect to the S3.
@ Dior DNA:
No i can't. Phone does nothing with the buttons. Only diference if i hold Vol - then time from connect sound and disconnect sound is a little longer.. about 10 seconds. But still nothing happens.
@1testi:
Flashtools can't see my phone. I tried it a hundred times. With battery, without battery, with Vol - and with Vol +.
When i connect the USB cable i hear the connect sound and after 2 a 3 seconds i hear disconnect sound. This goes on and on until i pull the USB cable out. In devicemanager i see a refresh going on, but nothing pops up.
I'm realy despered on what to do now?
Lowrida said:
@1testi:
Flashtools can't see my phone. I tried it a hundred times. With battery, without battery, with Vol - and with Vol +.
When i connect the USB cable i hear the connect sound and after 2 a 3 seconds i hear disconnect sound. This goes on and on until i pull the USB cable out. In devicemanager i see a refresh going on, but nothing pops up.
I'm realy despered on what to do now?
Click to expand...
Click to collapse
Why the SP Flashtool isn´t working any longer? You didn´t deinstalled the driver, did you? Just try to flash again with "Firmware Upgrade".
I don´t know a way to reinstall the driver in windows without the preloader. The only thing you can do, as far as i know, is to use a linux
pc to flash again. Linux don´t need a driver for SPF, only some rules.
Lowrida said:
@ Dior DNA:
No i can't. Phone does nothing with the buttons. Only diference if i hold Vol - then time from connect sound and disconnect sound is a little longer.. about 10 seconds. But still nothing happens.
(
Click to expand...
Click to collapse
Booting into recovery or flashtool I meant regardless of pc and/or spflashtool.
If I recall correctly:
hold volup and power boots recovery
hold voldn and power boots flashtool
If you can boot recovery then which one is it? Maybe you can restore something or manually flash preloader bin from there.
After the flash i reboot and then the connect and disconnect sound appears. So i tried differend things, but could not connect. I wanted to flash again, but flashtool did not reconice the phone and nothing in DeviceManager. That's why i thought to remove the driver and try to re-install it. But that did not help..
Holding Vol - or + button with power button or both Vol buttons with power button does nothing.. i tried to hold all combinations at least 30 seconds, but nothing at all.
I have no Linux pc or any knowhow to make a Linux pc.. or a pc to install Linux on..
One last thing you can try: remove the battery, wait a little, insert the battery again. Hold vol+ key, keep holding it and press power
button, while still holding the vol+. If you don´t see anything happening then you bricked the phone.
You will need help from a professional or at least from someone with a linux machine, sorry.
I'll try that.
You have any idea what could have caused the brick?
As i wrote above, moving from KK to LL with wrong parameter "Download" in SPF.
....and a not working recovery.
You should try this method :
darmowyinternet.net/forum/temat-poradnik-jak-uruchomic-uceglony-telefon-po-wgraniu-zlego-romu-test-point_383
unfortunately you have to translate before
Ok i tried that site with google translate and i could a little make up what they are saying.
But that is a very drastically operation, and i would like to give it some other tries before dismantling my phone.
So i googled and googled.. came here: http://forum.xda-developers.com/showthread.php?t=889128
Had enough electronics lying around from my former 27mc hobby, so searched for the right resistors,
cut up a micro usb cable and give it a try... well.. nothing! Tried for about an hour and gave up.
Then i googled on Unbrick Jigs, but for what i read they are only for Samsung phones, so i gues the trick
with the resistors were also?
So googling again... came here: http://forum.xda-developers.com/showthread.php?t=2454004
Reading the tread and the comments, someone mentioned a download for "Mediatek Driver Auto Installer".
Downloaded that and installed the drivers. Plugged in my phone and... whoohoo!! Something is happening! :silly:
My devicemanager saw an "Alcatel single RNDIS interface". I unplugged and plugged my phone a few times to
be sure it was my phone. Sooo... one step further! :good:
Then i googled on this device.. came up with all sorts of network devices, not helpfull. Then googled on Jiayu with
this device. Came up with this tread: https://www.china-devices.com/topic...vcomm-drivers-onto-your-pc-win-7vistaxp-only/
It's a tread about bricked Jiayu G3 devices, but i thought, 'What the heck, lets give it a try!'.
I downloaded the "MTK Megapack - All Tools Here!" and unpacked. Wend back to device manager and manually updated the driver
of the Alcatel device. Show all devices - browse - wend to Megapack map and there were MTK drivers for the 65xx device.
And yess.. when i plug in my phone there's the device: " MTK USB Port (COM7) "
SP Flashtools sees my phone again! :good:
Tried to flash a stock preloader, but got an error: "BROM ERROR : S_FT_ENABLE_DRAM_FAIL (4032) – [EMI] Enable DRAM failed!"
But for now that's a problem for tomorrow.. it's almost 2:30 and i have to got some sleep!
(sorry for the misspellings or telling things not clear, i'm tired and english is not my main language)
Grats!
You can google the error. This leds you in the right direction.
It's alive!!!!!! :laugh::silly::victory:
Because the kitkat stockrom i downloaded gave me the same error over and over i searched for something else.
So i downloaded TF Extreme lolipop 5.1 this morning and give it a try. And all went well. I pulled the usb plug and
pushed power button.. only vibration but nothing. Then pulled the battery and after few seconds put it back in
and try power again. Only 1 vibration.. then tried Vol + and - combinations but nothing. (dammn!)
Then plug the usb in and i saw the battery icon.. it was total empty! (because of a week trying).
So now it's charging and i hope it starts, can't wait!!
Thanx all for the effort in helping me out! :good:
Edit: Ok, so i could not wait and hit power! It shows green screen with Jiayu S3 logo and text "New Load". So i guess it's prepairing for first startup!
my s3 basic is not charging when on.. also when connected to pc thru usb, ipc shows device malfunctioning ,and there is no indication on phone..I try to connect to sp flash tool also no success..same error"usb device not recognized pops up every 2s.everything else is fine..Any method to upgrade to 5.1 now on official kk
Kinda need help, happened something similar
It happened something similar to me.
I flashed the whole ROM, bootloader included, I was very sure that my model, Jiayu S3 3GB ROM + 32GB RAM, was the correct, but still bricked my phone.
There's no problem at all when I plug it into my PC, I installed the lastest MTK drivers on windows 10, having to disable the signature enforcement.
The problem comes when I start flashing. I only mark the bootloader, then I press "Download" (on the lastest version of SP Flash Tools), and plug the phone, with the battery in it (I've tried without battery, pressing all possible combinations and does nothing), when I plug it in with the battery and pressing no buttons, the driver is detected as MTK USB Port. That's a good thing I guess. But It does not pass from the red bar, and gives me the known error "Enable DRAM Failed".
I've tried to google any possible solutions, reinstalling other version of the MTK drivers, on different versions of Windows, with other versions of official ROMs, and the result is always the same.
The only thing that's left to try is flashing it with an Ubuntu machine, which is something I do not expertise to be honest, but I'm gonna gather some info and try to do it.
However, if someone has any idea of what I might be doing wrong (excluding the part when I flashed the bootloader, I'll never do it again), I would be really grateful for any kind of help.
Thank you!
Kiei said:
It happened something similar to me.
I flashed the whole ROM, bootloader included, I was very sure that my model, Jiayu S3 3GB ROM + 32GB RAM, was the correct, but still bricked my phone.
There's no problem at all when I plug it into my PC, I installed the lastest MTK drivers on windows 10, having to disable the signature enforcement.
The problem comes when I start flashing. I only mark the bootloader, then I press "Download" (on the lastest version of SP Flash Tools), and plug the phone, with the battery in it (I've tried without battery, pressing all possible combinations and does nothing), when I plug it in with the battery and pressing no buttons, the driver is detected as MTK USB Port. That's a good thing I guess. But It does not pass from the red bar, and gives me the known error "Enable DRAM Failed".
I've tried to google any possible solutions, reinstalling other version of the MTK drivers, on different versions of Windows, with other versions of official ROMs, and the result is always the same.
The only thing that's left to try is flashing it with an Ubuntu machine, which is something I do not expertise to be honest, but I'm gonna gather some info and try to do it.
However, if someone has any idea of what I might be doing wrong (excluding the part when I flashed the bootloader, I'll never do it again), I would be really grateful for any kind of help.
Thank you!
Click to expand...
Click to collapse
Oeps it might be the same problem with the 32GB version as I have.
See http://forum.xda-developers.com/showpost.php?p=68036678&postcount=295
I am waiting for a stock ROM backup.
I have learned to never flash the original preloader again.
xtyphoon said:
Oeps it might be the same problem with the 32GB version as I have.
See http://forum.xda-developers.com/showpost.php?p=68036678&postcount=295
I am waiting for a stock ROM backup.
I have learned to never flash the original preloader again.
Click to expand...
Click to collapse
You're right, with the 32GB rom version (which is still unavaliable for public use) it worked! I still got it here, so anyone feel free to ask me the link too.
Thanks to xtyphoon and Dior DNA and everyone who made this possible, if you ever come to Girona city, I'll buy you a drink ;D
Kiei said:
[...]if you ever come to Girona city[...]
Click to expand...
Click to collapse
I was around there few weeks ago