Hi, I'm writing from Argentina, I read the post to install ICs in my X10A, install X10_2.2.25_MIUIV4-MILAD407-FXP129.ftf and then not boot the phone anymore, it stays on the screen "sony ericsson"
superuser had installed and installed debug options
Can you help me please?, try to flash it but it did not work with older firmwares newer, other files ftf with Flashtool.
The problem begans after try to install this firmware: http://forum.xda-developers.com/showthread.php?t=1792045&page=6
While booting x10 flash mode FlashTool recognizes the phone, but when trying to flash it gives multiple errors
flashsystem.X10FlashException: ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
at flashsystem.X10flash.uploadImage(X10flash.java:225)
at flashsystem.X10flash.sendLoader(X10flash.java:233)
at flashsystem.X10flash.flashDevice(X10flash.java:344)
at gui.FlasherGUI$45.run(FlasherGUI.java:1092)
at foxtrot.AbstractWorkerThread$1.run(AbstractWorkerThread.java:40)
at java.security.AccessController.doPrivileged(Native Method)
at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:36)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:199)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:182)
at java.lang.Thread.run(Unknown Source)
java.io.IOException: Read error :31 : Uno de los dispositivos conectados al sistema no funciona.
at win32lib.JKernel32.readBytes(JKernel32.java:57)
at flashsystem.io.USBFlashWin32.windowsReadS1Reply(USBFlashWin32.java:51)
at flashsystem.io.USBFlash.readS1Reply(USBFlash.java:45)
at flashsystem.X10flash.openDevice(X10flash.java:432)
at flashsystem.X10flash.openDevice(X10flash.java:372)
at gui.FlasherGUI$45.run(FlasherGUI.java:1091)
at foxtrot.AbstractWorkerThread$1.run(AbstractWorkerThread.java:40)
at java.security.AccessController.doPrivileged(Native Method)
at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:36)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:199)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:182)
at java.lang.Thread.run(Unknown Source)
java.lang.NullPointerException
at flashsystem.X10flash.processHeader(X10flash.java:187)
at flashsystem.X10flash.uploadImage(X10flash.java:203)
at flashsystem.X10flash.sendLoader(X10flash.java:233)
at flashsystem.X10flash.flashDevice(X10flash.java:344)
at gui.FlasherGUI$45.run(FlasherGUI.java:1092)
at foxtrot.AbstractWorkerThread$1.run(AbstractWorkerThread.java:40)
at java.security.AccessController.doPrivileged(Native Method)
at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:36)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:199)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:182)
at java.lang.Thread.run(Unknown Source)
flashsystem.X10FlashException
at flashsystem.X10flash.uploadImage(X10flash.java:225)
at flashsystem.X10flash.sendLoader(X10flash.java:233)
at flashsystem.X10flash.flashDevice(X10flash.java:344)
at gui.FlasherGUI$45.run(FlasherGUI.java:1092)
at foxtrot.AbstractWorkerThread$1.run(AbstractWorkerThread.java:40)
at java.security.AccessController.doPrivileged(Native Method)
at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:36)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:199)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:182)
at java.lang.Thread.run(Unknown Source)
padevoto said:
Hi, I'm writing from Argentina, I read the post to install ICs in my X10A, install X10_2.2.25_MIUIV4-MILAD407-FXP129.ftf and then not boot the phone anymore, it stays on the screen "sony ericsson"
superuser had installed and installed debug options
Can you help me please?, try to flash it but it did not work with older firmwares newer, other files ftf with Flashtool.
The problem begans after try to install this firmware: http://forum.xda-developers.com/showthread.php?t=1792045&page=6
While booting x10 flash mode FlashTool recognizes the phone, but when trying to flash it gives multiple errors
flashsystem.X10FlashException: ERR_SEVERITY="MAJOR";ERR_CLASS="SECURITY_CLASS";ERR_DYNAMIC="SIN header verification failed"
at flashsystem.X10flash.uploadImage(X10flash.java:225)
at flashsystem.X10flash.sendLoader(X10flash.java:233)
at flashsystem.X10flash.flashDevice(X10flash.java:344)
at gui.FlasherGUI$45.run(FlasherGUI.java:1092)
at foxtrot.AbstractWorkerThread$1.run(AbstractWorkerThread.java:40)
at java.security.AccessController.doPrivileged(Native Method)
at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:36)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:199)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:182)
at java.lang.Thread.run(Unknown Source)
java.io.IOException: Read error :31 : Uno de los dispositivos conectados al sistema no funciona.
at win32lib.JKernel32.readBytes(JKernel32.java:57)
at flashsystem.io.USBFlashWin32.windowsReadS1Reply(USBFlashWin32.java:51)
at flashsystem.io.USBFlash.readS1Reply(USBFlash.java:45)
at flashsystem.X10flash.openDevice(X10flash.java:432)
at flashsystem.X10flash.openDevice(X10flash.java:372)
at gui.FlasherGUI$45.run(FlasherGUI.java:1091)
at foxtrot.AbstractWorkerThread$1.run(AbstractWorkerThread.java:40)
at java.security.AccessController.doPrivileged(Native Method)
at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:36)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:199)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:182)
at java.lang.Thread.run(Unknown Source)
java.lang.NullPointerException
at flashsystem.X10flash.processHeader(X10flash.java:187)
at flashsystem.X10flash.uploadImage(X10flash.java:203)
at flashsystem.X10flash.sendLoader(X10flash.java:233)
at flashsystem.X10flash.flashDevice(X10flash.java:344)
at gui.FlasherGUI$45.run(FlasherGUI.java:1092)
at foxtrot.AbstractWorkerThread$1.run(AbstractWorkerThread.java:40)
at java.security.AccessController.doPrivileged(Native Method)
at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:36)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:199)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:182)
at java.lang.Thread.run(Unknown Source)
flashsystem.X10FlashException
at flashsystem.X10flash.uploadImage(X10flash.java:225)
at flashsystem.X10flash.sendLoader(X10flash.java:233)
at flashsystem.X10flash.flashDevice(X10flash.java:344)
at gui.FlasherGUI$45.run(FlasherGUI.java:1092)
at foxtrot.AbstractWorkerThread$1.run(AbstractWorkerThread.java:40)
at java.security.AccessController.doPrivileged(Native Method)
at foxtrot.AbstractWorkerThread.runTask(AbstractWorkerThread.java:36)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:199)
at foxtrot.workers.SingleWorkerThread.run(SingleWorkerThread.java:182)
at java.lang.Thread.run(Unknown Source)
Click to expand...
Click to collapse
Your problem is that your bootloader is still locked. To flash a custom kernel, you need to unlock your bootloader (instructions can be found in this thread http://forum.xda-developers.com/showthread.php?t=1254087), then flash the kernel and finally the ICS rom.
You should probably flash the stock 2.3.3 firmware from flashtool to get your phone working again properly first (looks like there's only 2.1 for the X10a in this thread http://forum.xda-developers.com/showthread.php?t=920746), then unlock bootloader, then flash custom kernel, and finally the custom rom.
You might want to be careful about what you flash, though, because I'm not sure if these methods do work for X10a. Someone else might be able to confirm this for you
Panzerfaust101 said:
Your problem is that your bootloader is still locked. To flash a custom kernel, you need to unlock your bootloader (instructions can be found in this thread http://forum.xda-developers.com/showthread.php?t=1254087), then flash the kernel and finally the ICS rom.
You should probably flash the stock 2.3.3 firmware from flashtool to get your phone working again properly first (looks like there's only 2.1 for the X10a in this thread http://forum.xda-developers.com/showthread.php?t=920746), then unlock bootloader, then flash custom kernel, and finally the custom rom.
You might want to be careful about what you flash, though, because I'm not sure if these methods do work for X10a. Someone else might be able to confirm this for you
Click to expand...
Click to collapse
everything works same for x10a or x10i
as for 2.3.3 stock roms you can find link in my signature. just grab the global generic one.
Resolved
THeLogiC said:
everything works same for x10a or x10i
as for 2.3.3 stock roms you can find link in my signature. just grab the global generic one.
Click to expand...
Click to collapse
very good news!, the original problem was to use a kernel bug and not have released the bootloader.
I had to work hard to discover that something as simple as flashing the phone went wrong for any problems with drivers, REMOVE EVERYTHING!, jellyfish, 1stool, flashtools, drivers, and companion seus!, REGCLEAN run,
reboot, install went back to FlashTool, i use Sony Ericsson X10i_2.1.A.435_GLOBAL GENERIC 1232-9897 firmware, reboot, root with Super OneClik, install superuser, busybox, make sure everything works well, reboot again and run qsd8250_semc.cmd and.....
I am everything perfect!
After this install the kernel and MILAD47 rom and everything works perfect!
Thanks a lot!!!
muy buenas noticias!!, el problema original del fallo fue usar un kernel y no tener liberado el bootloader.
tuve que trabajar bastante hasta descubrir que algo tan sencillo como flashear el celular salia mal por algun problema con los drivers, DESINSTALE TODO!!, medusa, 1stool, flashtools, drivers, seus y companion!!,
ejecute REGCLEAN, reinicie, volvi a instalar Flashtool, baje Sony Ericsson X10i_2.1.A.435_GLOBAL-GGL GENERIC 1232-9897, inicie, rootee con Super OneClik, instale superuser, busybox, verifique que todo funciona bien, reinicie ejecute qsd8250_semc.cmd y quedo todo perfecto!!
luego de esto instale el kernel y rom de MILAD47 y todo funciona perfecto!
Related
Last night I had a lot of users private messages asking me to create the International Streak Gingerbread Rom starting from DjSteve and Fards 2.4 version...
Personally, I don't think that it's better then my previous "2.1", but.....:
Here's to you my 2.4 Dell Streak INTERNATIONAL....
I rebuilt DjSteve "GS2.4beta3" zip with all the translated apk : Contacts, contacts provider, Phone, Gallery3D, Calendar, Framework-res, Systemui and settings, plus I added "23portrait", ADW, 190 dpi default....and the same tweaks of my SD2.3 rev 2.1....
14-10-11 : REV.A - Removed Dell Keyboard, Dell Stage - ADDED default Italian language, 3G Watchdog, Dolphin HD, Battery calibration, Cxxxxxt Live, not call log, ES gestore file, Real Calc, Tunein radio, changed default ringtone and notification sound, added Market ver.2.x.x and removed "Market updater", added IC Music, added IC sounds and ringtones, added Gallery3D INT by default, Optimized build.prop with 3g improve settings and other memory tweaks and.....ADDED customizable "loop tweaks" (thanks to "eoghan2t7"), that works so fine with Streak !
VERY IMPORTANT : I DON'T WANT DONATION FOR THIS WORK, IF YOU WANT TO MAKE A DONATION, GIVE IT TO "EAST FRIEND" OF FARDS...
Download link (REV.A) with MD5 857b95e7713cb804f064f92f21328faa :
https://docs.google.com/leaf?id=0BzRB5vMumafCMWQ4ZDRhMmQtOWNjMi00MTI0LTlmNWItYWZjZWFlYzgzNDUx&hl=it
INSTALLATION INSTRUCTIONS :
1- scaricare il file zip (download zip rom file)
2- scaricare il file amss da qui (download amss file from here) :
amss:
http://mirror2.strea...m/beta/amss.mbn
ATTENZIONE (WARNING) :
FLASHARE SOLAMENTE IL FILE AMSS.MBN, HO AVUTO ESPERIENZA PERSONALE, PROVATA PER 4 VOLTE DI SEGUITO, CHE FLASHANDO ANCHE IL FILE DSP1 COME DICE DJSTEVE NEL THREAD DI MODACO, PUO' CAUSARE UN "SOFT BRICK" DELLO STREAK, CON CONSEGUENTE NECESSITA' DI RIPRISTINO CON QDLTOOL. (FLASH AMSS.MBN ONLY, I EXPERIENCED FLASHING ALSO DSP1 MAY CAUSE "SOFT BRICK", WITH THE NEEDING OF QDLTOOL)
3- entrare in streakmod recovery (0.3.2.7+) (run streakmod recovery 0.3.2.7+)
4- eseguire un nandroid backup dell'attuale rom (make a nandroid backup)
5- flashare il file zip (flash the zip file)
6- reboot
7- entrare in fastboot mode (go to fastboot mode)
8- flashare amss e dsp1 (punto 2) con fastboot (non chiedere come perchè qui su XDA si incazzano facilmente.. ) p.s. : questo passo può essere evitato da chi lo ha già fatto in precedenza (flash amss ONLY with fastboot, don't ask how because XDA moderators get angry easily..). p.s. : (not necessary if you have already flashed these files)
9- comando reboot di fastboot (make a fastboot reboot)
10- entrare di nuovo SUBITO in recovery fermandosi al menu' con le 4 scelte, scegliere la prima (FACTORY RESET) (keep attention, press vol+ and vol- keys as soon as you see logo DELL, then choose option 1 FACTORY RESET)
11- avviare lo Streak, scegliere preferibilmente ADW come scelta predefinita di launcher, l'altro l'ho messo per "sicurezza" (boot the system, choose preferably ADW, the other one is there only for security reasons)
12- la ROM è di default in ITALIANO, per cambiare la lingua basta andare nelle impostazioni - (Rom is default in ITALIAN, if you want to change language, go to settings)
13- NON ESEGUIRE ASSOLUTAMENTE RESTORE DI APPLICAZIONI O IMPOSTAZIONI DA TITANIUM O ALTRE UTILITY SIMILI, INSTALLARE LE PROPRIE APP PREFERITE SOLO DAL MARKET (DON'T USE TITANIUM BACKUP OR OTHER BACKUP APPLICATIONS TO RESTORE PREVIOUS APPLICATION OR SETTINGS, INSTALL YOUR OWNS ONLY FROM MARKET)
14- Enjoy Gingerbread in Italiano o nella tua lingua (enjoy Gingerbread in Italian or in your language)
15- MOST IMPORTANT : Press Thanks Button (MOST IMPORTANT : Press Thanks Button ...)
VERY IMPORTANT NOTES :
16- Ho aggiunto uno script nella directory "system\etc\init.d", che permette di velocizzare notevolmente i tempi di risposta con le app più utilizzate dalla Rom (ad esempio il Launcher). Di default ho inserito solamente le apk di utilizzo "scontato", è possibile però personalizzare la lista delle app a proprio piacimento editando il suddetto file, sostituendo o aggiungendo fra le "" i nomi dei servizi delle app che vogliamo andare ad inserire. Lo script da editare con "root explorer" si chiama "97personalize_tweak". I nomi dei servizi li trovate nella directory "data\data". Lo script può essere editato tranquillamente dopo avere reinstallato la rom e tutte le vostre applicazioni. Per maggiori info vedi http://forum.xda-developers.com/showthread.php?t=1205744(I added a script in "system\etc\init.d" directory, it's able to speed up response times with the most used app of the Rom (eg the Launcher). By default I inserted only the "obvious" apks, but you can customize the list of the app to your liking by editing this file, replacing or adding in to the "" the names of the services of the app that you want to insert. The script to be edited with "root explorer" is called "97personalize_tweak". You can find the name of the services in "data\data" directory. Script can be edited easily after you have reinstalled the ROM and all your applications. For more info see http://forum.xda-developers.com/showthread.php?t=1205744 )
17- Consiglio di modificare la scelta delle animazioni da visualizzare in "nessuna animazione" da impostazioni\display\animazione, sembra che influisca positivamente su alcuni impuntamenti che, anche se raramente, mi dicono che a volte capitano....(verify that "display animation settings" is on "no windows animation are shown")
18- Per cambiare il "Timezone", cambiare prima la lingua della ROM in inglese (UK), successivamente cambiare il proprio fuso orario, infine reimpostare la lingua desiderata ..(To change "Timezone", please change first language to "English/UK", then set your "timezone", then rechange language with your favorite)
19- Dopo qualche minuto di uso, Superuser notificherà un aggiornamento, eseguirlo quanto prima. Se ciò non succedesse, fare l'aggiornamento direttamente dal market(After few minutes of use, Superuser will notify an update, please do it as soon as possible. If this does not happen, do the update directly from the market )
POINT "10" MOST IMPORTANT, DO A FACTORY RESET
POINT "10" MOST IMPORTANT, DO A FACTORY RESET
POINT "10" MOST IMPORTANT, DO A FACTORY RESET
POINT "10" MOST IMPORTANT, DO A FACTORY RESET
POINT "10" MOST IMPORTANT, DO A FACTORY RESET
POINT "10" MOST IMPORTANT, DO A FACTORY RESET
POINT "10" MOST IMPORTANT, DO A FACTORY RESET
Thanks to "DjSteve" and "fards" who creating the rom
Thanks to "them east friend" (who build the kernel??)
Thanks to "_n0p_ " for some files I used from his NEXUS S sharing
Thanks to "nibras_reeza" for his tweaks
Great! Thank you for that!!!!
installed last night.
first.. GPS failed... then factory reset again.
And back to normal again.
excellent jobs Thanks
great work from all of you. i really appreciate. the streak is a wonderful device.
a friend like to buy it, since i get a very very cheap galaxy s2 from amazon i will sell him my streak.
my decision is because i think that if it happens it will take alot of time to get CM7/8 on the streak. i am hungry for ICS and i believe the S2 get it soon.
so have a good time and keep on. maybe i can get a used streak later to play around again.
Thanks for another release. good to see that there are active devs on the streak.
I was just about to try your REV.A release but seems like the link to amss file isnt working....
Do i need to flash amss through fastboot if I currently have DJ Steve's 2.4?
cheers
satanix said:
Thanks for another release. good to see that there are active devs on the streak.
I was just about to try your REV.A release but seems like the link to amss file isnt working....
Do i need to flash amss through fastboot if I currently have DJ Steve's 2.4?
cheers
Click to expand...
Click to collapse
No, with 2.4 amss you don't need..
Have u seen I renamed Rev.A in "MaxicetDroid1.0" ? It's the same...
Thanks for your renewed trust ..
market application problems
Maxicet
Rom is very good. I am using with spanish localization.
Everything is fine except market. It froozen whe install an application. I have made several times the installation process (following all the steps...)
beginner said:
Maxicet
Rom is very good. I am using with spanish localization.
Everything is fine except market. It froozen whe install an application. I have made several times the installation process (following all the steps...)
Click to expand...
Click to collapse
It's easy to resolve, but since you installed several times this rom, it's better that you install my "MaxicetDroid1.0", without the need to flash amss.mbn.
Flash the zip file of rom only, then do a factory reset...
maxicet said:
It's easy to resolve, but since you installed several times this rom, it's better that you install my "MaxicetDroid1.0", without the need to flash amss.mbn.
Flash the zip file of rom only, then do a factory reset...
Click to expand...
Click to collapse
It works after some reset, YES, NOW MARKET WORKS FINE
Great job.thank you ,
can you help me with arabic
i try with arabic_script
its working bout it give me error
Dear Maxcicet,
Could you please renew link amss
Oops! Internet Explorer could not find mirror2.strea...m
ak1978 said:
Dear Maxcicet,
Could you please renew link amss
Oops! Internet Explorer could not find mirror2.strea...m
Click to expand...
Click to collapse
Send me a request with your gmail address
maxicet said:
Send me a request with your gmail address
Click to expand...
Click to collapse
Have just sent to your box. Thanks so much.
hellp for arabic my friends
Constant Rebooting
Hi, all. After upgrading my Streak, it is rebooting several times a day, with no apparent consistency. Is anyone else seeing this? Any ideas?
jleznek said:
Hi, all. After upgrading my Streak, it is rebooting several times a day, with no apparent consistency. Is anyone else seeing this? Any ideas?
Click to expand...
Click to collapse
Try to flash my "maxicetdroid1.0" then factory reset..
Update to the new streakdroid version, please.
crexa said:
Update to the new streakdroid version, please.
Click to expand...
Click to collapse
More attention, please ... : http://forum.xda-developers.com/showthread.php?t=1304727
Thank you. Expected the threads to be updates, not new threads, so haven't searched. Will take this mistake into account.
this firmware is very good.
But I can not ask balance. Could any one tell me to fix this?
Help, I've installed with rom manager the wrong version of clock recovery, then I turned off my phone and it's dead
Recovery and download mode doesn't work..!! Odin can see it if I presso volume +, then Menu smartkey (first on left) and power botton but I can't flash Roms because odin hold on setup connection... How can I solve..? if odin can see the phone there must be a solution..!
Help please..
-------------------
Ho installato da rom manager la recovery e selezionato un modello sbagliato.. Poi ho spento il cel e non c'è verso di rianimarlo
Odin lo riconosce se premo tasto volume su + tasto funzioni + tasto accensione ma non va a buon fine il flash (si blocca su configurazione connessione)..
Recovery e download mode sono ko e nemmeno la ricarica USB funziona.. Cosa posso fare..? Ho provato a comprare su ebay un USB modificato per mandarlo in download mode.. Speriamo bene...
Ma possibile che se odin lo vede non posso farci nulla..?
Se lo mando in assistenza c'e speranza non se ne accorgano e la cosa passi in garanzia..?
Sent from my i9000 using Tapatalk
ribelle85 said:
Help, I've installed with rom manager the wrong version of clock recovery, then I turned off my phone and it's dead
Recovery and download mode doesn't work..!! Odin can see it if I presso volume +, then Menu smartkey (first on left) and power botton but I can't flash Roms because odin hold on setup connection... How can I solve..? if odin can see the phone there must be a solution..!
Help please..
-------------------
Ho installato da rom manager la recovery e selezionato un modello sbagliato.. Poi ho spento il cel e non c'è verso di rianimarlo
Odin lo riconosce se premo tasto volume su + tasto funzioni + tasto accensione ma non va a buon fine il flash (si blocca su configurazione connessione)..
Recovery e download mode sono ko e nemmeno la ricarica USB funziona.. Cosa posso fare..? Ho provato a comprare su ebay un USB modificato per mandarlo in download mode.. Speriamo bene...
Ma possibile che se odin lo vede non posso farci nulla..?
Se lo mando in assistenza c'e speranza non se ne accorgano e la cosa passi in garanzia..?
Sent from my i9000 using Tapatalk
Click to expand...
Click to collapse
the right download mode, the one you have to use with Odin is obtained by pressing Vol - / OK button /the bigger one at the center) / Power
try to use it after starting Odin to see if it recognized by it. Use Odin 4.2.8 with Europa 1.0.ops and ClockworkMod-Galaxy5-v0.5.tar file, no other one: for my personal experience, others ClockworkMod recovery versions (0.6, for example) don't work.. they just freeze on recovery.img download process!!
hope this could help you solving the problem, let me know!
- - - - - - - - - - - - -
Il Download mode che va usato con Odin si ottiene premendo Vol - / Tasto OK centrale / Power
usa questa sequenza con Odin 4.2.8, Europa 1.0.ops e come recovery solo e soltanto la ClockworkMod-Galaxy5-v0.5.tar, per la mia esperienza le successive versione della recovery non vanno: si bloccano durante il processo di sownlaod del recovery.img file (ma non succede nulla di irreparabile, basta riavviare e si può usare la versione precedente senza problemi)!!
spero che questo ti possa aiutare a risolvere il tuo problema, fammi sapere..
brainvision said:
the right download mode, the one you have to use with Odin is obtained by pressing Vol - / OK button /the bigger one at the center) / Power
try to use it after starting Odin to see if it recognized by it. Use Odin 4.2.8 with Europa 1.0.ops and ClockworkMod-Galaxy5-v0.5.tar file, no other one: for my personal experience, others ClockworkMod recovery versions (0.6, for example) don't work.. they just freeze on recovery.img download process!!
hope this could help you solving the problem, let me know!
- - - - - - - - - - - - -
Il Download mode che va usato con Odin si ottiene premendo Vol - / Tasto OK centrale / Power
usa questa sequenza con Odin 4.2.8, Europa 1.0.ops e come recovery solo e soltanto la ClockworkMod-Galaxy5-v0.5.tar, per la mia esperienza le successive versione della recovery non vanno: si bloccano durante il processo di sownlaod del recovery.img file (ma non succede nulla di irreparabile, basta riavviare e si può usare la versione precedente senza problemi)!!
spero che questo ti possa aiutare a risolvere il tuo problema, fammi sapere..
Click to expand...
Click to collapse
The download mode sequence doesn't work.. The display doesn't turn on..
Only with option key odin can see the phone
Sent from my i9000 using Tapatalk
WTF..
adb recognize it? did you try
Code:
adb reboot
or
Code:
adb recovery reboot
Searching the web I found a reply to a question very near yours (a user flash trough Odin but it use APBOOT for another phone):
Immettendo un file diverso su Odin hai scalibrato le linee di flash del dispositivo e di conseguenza alcune sue funzionalitá di utilizzo. Probabilmente a causa di ció la sequenza per entrare in dowload mode non va a buon fine. Consigliabile inviarlo in assistenza per capire se il problema puó essere risolto o meno tramite un intervento mirato al tuo caso........Il flash di qualunque Rom é un'operazione delicatissima e tante possono essere le cause che contribuiscono a poter rendere inutilizzabile il prodotto in questione.
Click to expand...
Click to collapse
Finally I found that, maybe you just read it.. http://forum.xda-developers.com/showpost.php?p=18795160&postcount=4
Tks mate tomorrow I'll try and let you know
Sent from my i9000 using Tapatalk
Can You tell Us which version did You pick?
brainvision said:
WTF..
adb recognize it? did you try
Code:
adb reboot
or
Code:
adb recovery reboot
Searching the web I found a reply to a question very near yours (a user flash trough Odin but it use APBOOT for another phone):
Finally I found that, maybe you just read it.. http://forum.xda-developers.com/showpost.php?p=18795160&postcount=4
Click to expand...
Click to collapse
In the control panel I see this:
http://dl.dropbox.com/u/23080338/pannellocontrollo.JPG
but when I launch the adb devices command the system doesn't recognize the device:
http://dl.dropbox.com/u/23080338/comando.JPG
Why???
ribelle85 said:
In the control panel I see this:
http://dl.dropbox.com/u/23080338/pannellocontrollo.JPG
but when I launch the adb devices command the system doesn't recognize the device:
http://dl.dropbox.com/u/23080338/comando.JPG
Why???
Click to expand...
Click to collapse
I think you have the same identical problem I run into when i installed the Android SDK (first time I did that by the zip archive): before all that, my laptop was able to recognized and connect to the Corby without problems.. I was able to use Odin and flash both CWM both stocks rom..
My troubles started when i decided to install the Android SDK: I installed the Java JDK, first of all, then i downloaded the zip version of the Android SDK: I unzipped into a folder and started the SDK Manager letting it install the 6 or 7 default packages it required..
After that I was not able anymore to successfully flash anything with Odin! I think that the problem is the USB Google driver, indeed!!
I try to uninstall the driver by unpicking it into the SDK Manager but it's still there.. and if I try to manually uninstall it by the Control Panel, at the next reboot it installs itself again and again!!
Just to be sure I install the Android SDK into an VirtualBox emulated machine but this time I don't install the USB driver and Odin stills work!!
So, I don't know what you can do into your PC to solve that, actually.. I'm still studying the problem but I usually don't use Windows so I quite forget it.. now I can run Odin into my Slackware, so..
What I can suggest you is to try with another PC or laptop, for now..
EDIT: I forget to say: obviously the question mark into your first screenshot means that the driver doesn't work properly.
Last thing: the right driver is not the one you shot, but is called Samsung USB or something like that and you must find it among the USB devices (when the phone is connected, naturally. If you don't have it: did you install Kies or the USB Samsung drivers? But I'm sure yes)!!
brainvision said:
I think you have the same identical problem I run into when i installed the Android SDK (first time I did that by the zip archive): before all that, my laptop was able to recognized and connect to the Corby without problems.. I was able to use Odin and flash both CWM both stocks rom..
My troubles started when i decided to install the Android SDK: I installed the Java JDK, first of all, then i downloaded the zip version of the Android SDK: I unzipped into a folder and started the SDK Manager letting it install the 6 or 7 default packages it required..
After that I was not able anymore to successfully flash anything with Odin! I think that the problem is the USB Google driver, indeed!!
I try to uninstall the driver by unpicking it into the SDK Manager but it's still there.. and if I try to manually uninstall it by the Control Panel, at the next reboot it installs itself again and again!!
Just to be sure I install the Android SDK into an VirtualBox emulated machine but this time I don't install the USB driver and Odin stills work!!
So, I don't know what you can do into your PC to solve that, actually.. I'm still studying the problem but I usually don't use Windows so I quite forget it.. now I can run Odin into my Slackware, so..
What I can suggest you is to try with another PC or laptop, for now..
EDIT: I forget to say: obviously the question mark into your first screenshot means that the driver doesn't work properly.
Last thing: the right driver is not the one you shot, but is called Samsung USB or something like that and you must find it among the USB devices (when the phone is connected, naturally. If you don't have it: did you install Kies or the USB Samsung drivers? But I'm sure yes)!!
Click to expand...
Click to collapse
Yes in that pc Kies is installed.. tomorrow i'll try in another one and let you know!!! Thanks for everything
Inviato dal mio GT-I9000 usando Tapatalk
on another pc I installed kies and press the option, power and volume down botton; it's now recognised ad a modem :
http://dl.dropbox.com/u/23080338/Immagine.JPG
but when I try ADB devices it appears this:
http://dl.dropbox.com/u/23080338/Immagine (1).jpg
(it doesn't recognize an adb device...)
http://dl.dropbox.com/u/23080338/Immagine3.JPG
this are the files in adb folder (I downloaded a zip version)
http://dl.dropbox.com/u/23080338/Immagine2.JPG
what's wrong??? help
ribelle85 said:
on another pc I installed kies and press the option, power and volume down botton; it's now recognised ad a modem :
http://dl.dropbox.com/u/23080338/Immagine.JPG
but when I try ADB devices it appears this:
http://dl.dropbox.com/u/23080338/Immagine (1).jpg
(it doesn't recognize an adb device...)
http://dl.dropbox.com/u/23080338/Immagine3.JPG
this are the files in adb folder (I downloaded a zip version)
http://dl.dropbox.com/u/23080338/Immagine2.JPG
what's wrong??? help
Click to expand...
Click to collapse
did you do all that with the phone ON or in Dload mode, that is the only state of the phone you are allowed to, isn't it?
brainvision said:
did you do all that with the phone ON or in Dload mode, that is the only state of the phone you are allowed to, isn't it?
Click to expand...
Click to collapse
I can't access to download mode..! I only can press the option,on and volume up to go in a special mode..
Sent from my i9000 using Tapatalk
ribelle85 said:
I can't access to download mode..! I only can press the option,on and volume up to go in a special mode..
Sent from my i9000 using Tapatalk
Click to expand...
Click to collapse
Yes I know.. It's called Emergency DLoad mode, if I well remember..
so did you try that with the phone putted in Emergency DLoad mode??
brainvision said:
Yes I know.. It's called Emergency DLoad mode, if I well remember..
so did you try that with the phone putted in Emergency DLoad mode??
Click to expand...
Click to collapse
Yes and the result is the one of the screenshots
Inviato dal mio GT-I9000 usando Tapatalk
bootloop samsung i5500
good morning head see I have a serious problem and would like to know if I can help smooth yo I got to free my samsung i5500 with the method that I show below:
and the super decompress a folder called oneclick ADB is copied to the root directory ie C:
2 - Within SuperOneClick files windows open a console (Start> Run> cmd) and
cd wrote .. twice and then, cd adb, then enter the following
-adb shell
- su
- cd /
- mount -o remount,rw -t rootfs rootfs /
- mkdir /efs
- mount -o nosuid,ro,nodev -t vfat /dev/block/stl5 /efs
- cat /efs/mits/perso.txt
anotamos el codigo de 8 digitos
- umount /efs
3 - Place the chip from another company and enter the lock code we had written down and ready.
actually showed me on screen release the eight digits. the question is that when you turn off the cel to place another sincard and stays lit in a boot loop that is constantly cycles on and off and not pass the screen that says SAMSUNG.
I'm trying to repair the cell with this method and after discovering that I have to keep precionada turn the MENU + HOME + POWER on screen I get "emergency Dload Mode (ARM9 mode), run the odin and detects the device performed all steps you mentioned and well but after hours in performance of odin never goes out of this line "
<1> setup connection ... ".
then it would ask if I'm missing some file or am I doing wrong. I have the Samsung i5500 cell movistar Venezuela
Hello everyone! Today I downloaded and installed in Rom manager a recovery different from my model (stupid), turned off the phone and now will not start, nor the downloading mode... is there any solution? In other forums told me that there is no solution, is this right?
Sorry, my english is too bad...
I forgot to say that does not show the symbol of the battery when charging, either the PC or power...
You found any solution...???
Samsung repaired my phone for free!!!
So happy
Inviato dal mio Nexus S usando Tapatalk
ribelle85 said:
Samsung repaired my phone for free!!!
So happy
Inviato dal mio Nexus S usando Tapatalk
Click to expand...
Click to collapse
che para******
meno male.. ora starai più attento, questo è certo!
did you find any solution????
Enviado desde mi GT-S5830L usando Tapatalk
brainvision said:
che para******
meno male.. ora starai più attento, questo è certo!
Click to expand...
Click to collapse
Sure! Comunque ho smanettato a palla sul galaxy e non ho mai brickato!!! E' stata sfortuna grazie ancora
Inviato dal mio Nexus S usando Tapatalk
voila se quil me marque quand je demare en recovery
"Failed to boot 2.
Starting RSD Mode"
Et... rien. Lors que je maintiens volume bas (ou haut d'ailleurs) et POWER, je n'ai pas accès au fastboot, il ne se passe rien, j'ai juste ces deux lignes d'affichées et je ne peux rien faire. merci de maider :crying::crying::crying:
English please.
Sent from that Atrix.
here is that he is me when I mark smith in recovery
"Failed to boot 2.
Starting RSD Mode "
And .. nothing. I maintain that at low volume (high or elsewhere) and POWER, I do not have access to fastboot it nothing happens, I just posted these two lines and I can not do anything. thank you for maider:crying::crying:
I had the same problem, there is a precise step by step fix for the failed to boot 2 error, i got this after using romracer to install cwm recovery = problem.
It even tells you what to do if rsd reaches 100% but doesnt say success or fail.
Unfortunately I'm currently at work and have a wedding reception to go afterwards.
But i will try and find it if no one else can.
There is a fix, but I forgot where, will try and find.
( il ya une solution, mais j'ai oublié où, vais essayer de trouver) :thumbup:
Google translate is my friend.
Sent from my Atrix
Motorola Atrix (MokeeOS v1.10.436)
Nexus 7 (Vanilla root flavour)
I had the same problem when I first tried to unlock the bootloader
http://forum.xda-developers.com/showthread.php?t=1302423
follow this exactly,follow the proper recovery method in the link, don't use any app at this stage to make the recovery, follow the method exactly as mentioned in the link, look carefully at step 9 if you have this problem with RSD and follow exactly,and yes it is in English.
This helped me with my failed to boot 2, this should fix your problem and...... use windows to follow the instructions (sign of cross with my fingers :cyclops: )
[Q&A] [TUTORIAL] MediaTek MT65xx Firmware Porting Thread | Guidelines | The Easy Way
Q&A for [TUTORIAL] MediaTek MT65xx Firmware Porting Thread | Guidelines | The Easy Way
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [TUTORIAL] MediaTek MT65xx Firmware Porting Thread | Guidelines | The Easy Way. If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
where to download the MTKBootimg.zip...
where to download the MTKBootimg.zip...
Luqmancili said:
where to download the MTKBootimg.zip...
Click to expand...
Click to collapse
Here you, bud!
http://d-h.st/30d
Can we port cm 12 to mediatek using this guide???
How to fix black screen camera? I have try ur method, its not working.
MTK6572a
Olá, preciso da ajuda, se conheçe o aparelho TLX S5i mini, ROM MTK6572a, O aparelho "não ativa o WIFI" fui tentar fazer um backup usando o MTK Tool e Rom HDC S5 A3LGT-i9600 MT6572, depois de alguns segundos surgiu um aviso (brom error s_ft_enable_dram_fail (4032)) e se insisto (Brom error s_ft_enable_dram_fail (1013)).
Depois disso o aparelho não liga mais.
Descobri que é porque a Rom que tentei usar é Compatível com o aparelho, procurei em todos os Sites que achei de Rons de aparelhos Clones e não encontrei a ROM "MTK6572a" indicada no aparelho só MTK6572.
Mais inf. Android 4.3.3 - Dual Core , 1.2GHz, Dual SIM - Mini Sim e SIM, Câmera 5MP.
Agradeço desde já.
Inglês
Hello, I need help, you know the TLX S5i mini device, ROM MTK6572a, The system "does not activate the WIFI" I was trying to make a backup using the MTK Tool and Rom HDC-S5 A3LGT i9600 MT6572, after a few seconds when a warning (brom error s_ft_enable_dram_fail (4032)) and insist (Brom error s_ft_enable_dram_fail (1013)).
After that the power does not turn over.
I have found it because the Rom I tried to use is compatible with the device, I tried on all sites I found sets of Rons Clones and found the ROM "MTK6572a" indicated on the appliance only MTK6572.
...More inf. TLX - Android 4.3.3 - ROM MTK6572a - Dual Core, 1.2GHz, Dual SIM - Mini Yes and YES, 5MP Camera.
Telefone não liga mais.
Phone does not turn over. no start.
hussain525 said:
Can we port cm 12 to mediatek using this guide???
Click to expand...
Click to collapse
No bro! Not possible
heryandp said:
How to fix black screen camera? I have try ur method, its not working.
Click to expand...
Click to collapse
Added init.rc code? Tell me your Device hardware
SergioMasc said:
Olá, preciso da ajuda, se conheçe o aparelho TLX S5i mini, ROM MTK6572a, O aparelho "não ativa o WIFI" fui tentar fazer um backup usando o MTK Tool e Rom HDC S5 A3LGT-i9600 MT6572, depois de alguns segundos surgiu um aviso (brom error s_ft_enable_dram_fail (4032)) e se insisto (Brom error s_ft_enable_dram_fail (1013)).
Depois disso o aparelho não liga mais.
Descobri que é porque a Rom que tentei usar é Compatível com o aparelho, procurei em todos os Sites que achei de Rons de aparelhos Clones e não encontrei a ROM "MTK6572a" indicada no aparelho só MTK6572.
Mais inf. Android 4.3.3 - Dual Core , 1.2GHz, Dual SIM - Mini Sim e SIM, Câmera 5MP.
Agradeço desde já.
Inglês
Hello, I need help, you know the TLX S5i mini device, ROM MTK6572a, The system "does not activate the WIFI" I was trying to make a backup using the MTK Tool and Rom HDC-S5 A3LGT i9600 MT6572, after a few seconds when a warning (brom error s_ft_enable_dram_fail (4032)) and insist (Brom error s_ft_enable_dram_fail (1013)).
After that the power does not turn over.
I have found it because the Rom I tried to use is compatible with the device, I tried on all sites I found sets of Rons Clones and found the ROM "MTK6572a" indicated on the appliance only MTK6572.
...More inf. TLX - Android 4.3.3 - ROM MTK6572a - Dual Core, 1.2GHz, Dual SIM - Mini Yes and YES, 5MP Camera.
Telefone não liga mais.
Phone does not turn over. no start.
Click to expand...
Click to collapse
Replaced libbluetooth**.so ?
Nice contribution, thank you!
Can I port ROM of different android version using this method?
I have Base ROM which is Android 4.1.2 and chipset of my device is MT6577,
I have port ROM which is Android 4.4.2 , port ROM is also for MT6577 Chipset,
will this method work for porting 4.4.2 to my device?
Thanks in adv.
Dhruv Suthar said:
I have Base ROM which is Android 4.1.2 and chipset of my device is MT6577,
I have port ROM which is Android 4.4.2 , port ROM is also for MT6577 Chipset,
will this method work for porting 4.4.2 to my device?
Thanks in adv.
Click to expand...
Click to collapse
You should port 4.2.2 of Amoi to your device because Kitkat ain't easy if you don't have same preloader.
Problem
Thanks for your guide
I have ported many roms but a lot of roms have the same bug is Dialer not responding(no sound incall) and the phone stuck... i get this bug when incalling
How to fix this
Stuck at mount
Thank you for your guide.
I am looking to port a Stock XOLO A500 Club(MTK6572) to XOLO A500S IPS(MTK6572W) and completely new to porting roms, infact this will be my first port. Please bear with me.
i have managed complete all your steps but stuck at the very last step of mounts and generating updater scripts, i have flashable stock roms for both. My Problems:
1. Could not generate updater-script for stock of both i tried using android kitchen, it did generate update-script but was nowhere close to the updater-script, i understand they both are different, but couldnt find one to use, please point me in the right direction.
2. Could you elaborate the last step if possible as the other files in meta-inf are also missing.
The over all idea is to update A500IPS to kitkat(next step) as the company has release kitkat update for A500 club and both devices have almost identical config.
Thanks again.
pavanbane said:
Thank you for your guide.
I am looking to port a Stock XOLO A500 Club(MTK6572) to XOLO A500S IPS(MTK6572W) and completely new to porting roms, infact this will be my first port. Please bear with me.
i have managed complete all your steps but stuck at the very last step of mounts and generating updater scripts, i have flashable stock roms for both. My Problems:
1. Could not generate updater-script for stock of both i tried using android kitchen, it did generate update-script but was nowhere close to the updater-script, i understand they both are different, but couldnt find one to use, please point me in the right direction.
2. Could you elaborate the last step if possible as the other files in meta-inf are also missing.
The over all idea is to update A500IPS to kitkat(next step) as the company has release kitkat update for A500 club and both devices have almost identical config.
Thanks again.
Click to expand...
Click to collapse
Update Managed to boot most this look ok, yet to test, but couple problems:
1 - Wifi doesnt work
2 - I Ported to a stock rom, so lost recovery as well as root, could you guide me to get rooted(framaroot wont work) and recovery as well
3. - Can you confirm if i can port Kitkat now, devices are near identical, i read you have a pre-loader and kernel issues, could i please help
Help!!!!
I manage to do the required methods but after compressing and flashing the phone is stuck at boot logo...
i tried the port boot image and it boots up but the screen is almost white or close to dead pixel but i can see the bootanimation the setup wizard but touchscreen wont work..
What should i do should i modify my stock boot image?
if yes how can i modify it?
Thnx
Stuck at boot logo
Thank you for the wonderful thread. Sir, i ported a vionicl rom to my device Htc desire 816g, and after flashing i get a booploop
plz helpp
Port Lollipop 5.1 to Lollipop 5.0 device, both MT6582 device.
Is it possible to port Lollipop 5.1 ROM to 5.0 device, both being MT6582 device?
If yes please guide me. this is my first attempt.
How do you compare preloader version on mtk devices?
mt6592
can i use for mt6592 chipset device?
Request
Hi I've ported MIUI6 based on this guide. So, I request you to post a guide regarding Cross Platform chipset porting like mt6592 to 6582, mt6582 to 6572..
Lord_Flaya said:
How do you compare preloader version on mtk devices?
Click to expand...
Click to collapse
Noone that knows yet?
hi everyon
Perform BLU unlock in Device connected in fastboot mode
The following error message appears
ERROR-Cannot invoke "String.split(String)" because the return value of "java.util.Properties.getProperty(String)" is null
How to solve this?
Mobile: xperia xz1 (SOV36) Japanese version Android9.0
Please see the link below
[IMG="https://i.imgur.com/bIuj3Gj.jpg"]
Thank you
use " command prompt " to unlock your bootloader
TEK023 said:
use " command prompt " to unlock your bootloader
Click to expand...
Click to collapse
Please help. I'm always fail when I try to unlock bl
Hi I have the sam problem
ERROR-Cannot invoke "String.split(String)" because the return value of "java.util.Properties.getProperty(String)" is null
unlocked was by fastboot lock is not possible by fastboot
Same problem here
Tried command prompt
Tried a different PC
8 hours of trying later and I'm ready to smash the phone to pieces with a hammer
Same problem here. What firmware and fastboot version are you on?
Mine is 53.1.A.3.85 and 30.0.5
@TEK023 Tried both Flashtool and fastboot, without success.
Fastboot fails with errormessage:
Bash:
sudo fastboot oem unlock 0x463xxxxx
FAILED (remote: 'Command did not succeed')
fastboot: error: Command failed
Same problem here!
is the developer options
under oem unlocking bootloader enabled?
not all phones allow oem unlocking bootloader. only some phones allow it.
you can't do nothing about it. no hack. from I know.
some carrier phones don't even allow usb debugging and no developer options .
same problem with xz2 compact.
Although
bootloader unlock allowed: yes
Oem unlock: On
Fixed by turning off lock the bootloader in dev options. Stupid Me!
Guys, I have a problem with my Sony Xperia XA2 Ultra H4213 that dropped software, so when I make a flash tool for new software can not respond to do that, also because of unlocking bootloader is not activated, I used all things also command prompt. I also try to unlock the bootloader to make new software can't respond also, can you help me, guys? please how to fix that thing?
jossefzizo said:
Pessoal, estou com um problema com meu Sony Xperia XA2 Ultra H4213 que derrubou software, então quando faço uma ferramenta flash para software novo não consigo responder a fazer isso, também porque o desbloqueio do bootloader não está ativado, usei todas as coisas também prompt de comando . Também tento desbloquear o bootloader para fazer com que novos softwares não respondam também, podem me ajudar, pessoal? por favor, como consertar isso?
Click to expand...
Click to collapse
managet tu unlock?