I am really confused.
The last time I flashed my nike was almost a year ago, and now, since hardspl 1.22 I cant remember how to flash a new rom.
So, when I used spl 1.16, how I always do is the following: establish active sync connection, execute spl 1.16 on device, and then execute RUU.
So (by that time) I installed 1.22 and flashed an official ROM (no need of spl 1.16). But now, I'm trying flashing the same ROM (the lastest one, OEM PTG), establishing active sync and just executing RUU, but in the last step my device jumps to tri color boot (with USB information) and I get in my computer error in syncronizing.
Am I doing anything wrong?
I'm using Windows 7, wondering if that's problem (altought I can use Windows Mobile Device Center very well and with no problems).
Can you please help me?
Same problem here, might be a Win7 issue.
boa tarde Tiago, tive o mesmo problema aqui.
a solução foi a seguinte: despluga do usb, desliga o aparelho e liga com o botao da camera pressionado, vai entrar na tela tricolor, aí vc pluga e executa o customRUU.
pra mim funcionou.
qq coisa tamos aí.
Abraço.
1 - unplug from usb
2 - turn off the phone
3 - hold camera button and turn on the phone (will apear the three color screen)
4 - plug the usb cable again
5 - run customRUU
thanks
I am also using windows 7 and no problem.
I think need to install 1 more driver.
When connected on bootloader mode (three color) windows will ask for a driver.
Just let it search online. When it's done, then you can flash your phone.
Sorry for my bad english
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
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?
eu pisquei um arquivo img de um gsi na partição do super sistema, agora ele não liga. eu tentei piscar via qfil e smsdownload e até twrp , ele muda a rom mas o telefone ainda está preso no modo fastboot. Ele não entra no modo fastbootd ou modo de recuperação. para algo que eu possa fazer? há esperança?
adb reboot fastboot
leobraz said:
i flashesed an img file from a gsi in the super system partition ,now it doesn`t turn on . i`vetried flashing via qfil and smsdownload and even twrp , it changes the rom but the phone is still stuck in fastboot mode. It doesn`t go into fastbootd mode or recovery mode. to something i can do ? is there hope?
Click to expand...
Click to collapse
from original rom with the same version which is installed you can
fastboot --disable-verity flash vbmeta vbmeta.img
fastboot reboot fastboot
fastboot flash system system.img
* i guess you used only 2 img files, right?
when i give the fastboot reboot fastboot command it doesn`t go into fastbootd mode . as if fastbootd mode is corrupted
appears in cmd (error:it will read to boot into userspace fastboot ; one or more components mighit be unbootble
i guess you used only 2 img files, right?it was just one .
i`ve been trying to solve it for two months , i`ve tried all the methods i knew , now i`m out of ideas so i`m asking on the forum
Hi. Bootloader is unlocked and you can access fastboot mode? That's great news!
You can download a stable official firmware from realme website (preferably the same version that's currently installed on your device) and then flash the complete firmware to your device. If you don't want to lose your data then don't flash the userdata partition!
Good luck!
Sorry for my English
Maybe helps someone:
I want to talk about the successful flash Android 12 on TA-1041(Nokia 7)
Algorithm
1) Unlock the bootloader (full unlock)
2) Download TWRP https://forum.xda-developers.com/t/...eam-win-recovery-project-nokia-7-c1n.4146763/
3) flash the firmware from here https://forum.xda-developers.com/t/fastboot-unofficial-9-0-android-one-port-for-nokia-7.3980067/
4) Reboot into fastboot, boot from TWRP, format data, systems. Reboot to fastboot
5) download PixelExperience_Plus_arm64-ab-slim-12.1-20220825-UNOFFICIAL.img.xz from https://github.com/ponces/treble_build_pe/releases/tag/v415.1-plus . Extraxt xz
6) fastboot flash system PixelExperience_arm64-ab-slim-12.1-20220823-UNOFFICIAL.img.xz
Reboot .... cheers, 12 android, the battery perfectly, everything works.
Olá, você poderia me ajudar a realizar esta instalação?
Olá, você poderia me ajudar com esta instalação?