As this time-lapsed gif indicates, my phone is stuck in an endless boot logo - recovery loop.
I was on official Sammy 4.3 and decided to reboot to recovery when I encountered this. The recovery at that time was Philz 5.18.5 and I was incidentally rebooting to recovery to flash Philz 6.
The following has no effect:
1. Long press of power button (8 secs) for shutdown and reboot
2. Key combination for reboot to recovery
3. Pulling out the battery and then booting up the phone
4. Connecting the charger with the phone in off mode
I have been able to go in to Download mode which I suppose will enable me to use Odin, but I quite some time away from being able to do that. So any ideas anyone?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sounds like a partition is corrupt, if it won't boot to recovery then nothing else to try except odin.
Sent from my GT-I9300 using Tapatalk
t3chg33k said:
As this time-lapsed gif indicates, my phone is stuck in an endless boot logo - recovery loop.
I was on official Sammy 4.3 and decided to reboot to recovery when I encountered this. The recovery at that time was Philz 5.18.5 and I was incidentally rebooting to recovery to flash Philz 6.
The following has no effect:
1. Long press of power button (8 secs) for shutdown and reboot
2. Key combination for reboot to recovery
3. Pulling out the battery and then booting up the phone
4. Connecting the charger with the phone in off mode
I have been able to go in to Download mode which I suppose will enable me to use Odin, but I quite some time away from being able to do that. So any ideas anyone?
Click to expand...
Click to collapse
Maybe this is SDS, its time to send your SGS3 to Samsung for repair(getting new motherboard)..
Can u go into download mode or not(i did't understood what you said earlier), if you can go into download mode can you please tell what is there in Product Name. if its GT-I9300 and everything else is fine there than try to flash firmware from odin..
suyash1629 said:
Maybe this is SDS, its time to send your SGS3 to Samsung for repair(getting new motherboard)..
Can u go into download mode or not(i did't understood what you said earlier), if you can go into download mode can you please tell what is there in Product Name. if its GT-I9300 and everything else is fine there than try to flash firmware from odin..
Click to expand...
Click to collapse
From what I had read about SDS, the phone ends up being so very dead that it doesn't even show the boot logo. In my case, Download mode is the just about the only thing that I can currently enter in to; so I guess there is no other option now.
t3chg33k said:
From what I had read about SDS, the phone ends up being so very dead that it doesn't even show the boot logo. In my case, Download mode is the just about the only thing that I can currently enter in to; so I guess there is no other option now.
Click to expand...
Click to collapse
In case of SDS boot loop also occurs some times and also some users are able to get into download mode but they find that the product name is blank or something else, have you checked your Product Name, that should be GT-I9300..
i just had the very same problem, although with philz 6.0....
Fortunately in my case (and i can bet in yours too) in download mode the phone model was correctly reported as gt i9300 so it wasn't sds (phew) and i could get my phone running again.
these are the steps i followed:
1) put the phone in download mode
2) open odin and connect the phone to the pc
3) load under pda stock rom of my country
4) let odin do it's magic till it says "pass"
5) at this stage my phone got stuck at the samsuing logo so
6) Turned the phone off and boot in to stock recovery
7) Cleared cache and data/factory reset
8) tada phone up and running again
9) Flashed custom recovery and custom rom again (we will never learn, will we???)
Hope this helped.
amigaoneit said:
i just had the very same problem, although with philz 6.0....
Fortunately in my case (and i can bet in yours too) in download mode the phone model was correctly reported as gt i9300 so it wasn't sds (phew) and i could get my phone running again.
these are the steps i followed:
1) put the phone in download mode
2) open odin and connect the phone to the pc
3) load under pda stock rom of my country
4) let odin do it's magic till it says "pass"
5) at this stage my phone got stuck at the samsuing logo so
6) Turned the phone off and boot in to stock recovery
7) Cleared cache and data/factory reset
8) tada phone up and running again
9) Flashed custom recovery and custom rom again (we will never learn, will we???)
Hope this helped.
Click to expand...
Click to collapse
Yeah, Odin saved the day. A simple flash got the phone going again without the problems that you had with the phone getting stuck at the boot logo. But yeah, we never learn; immediately flashed Philz 6 and Temasek's CM11.
Related
I have tried everything on my wife's I9001 but I cannot get Odin to get past SetupConnection.
Here is a picture:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have tried:
Redownloading Odin 1.3 and 1.85 and also tried using Multi Downloader 4. (Which says that the .md5 file isn't supported).
Changing USB ports.
Using a Jig to boot Download mode.
Booting into Download mode normally.
Installing MobileODin except that I9001 is not supported.
Trying to flash a different rom other than 'I9001XXKQ1_I9001XXKPI_I9001DBTKP1_HOME.tar.md5'
Rebooting the computer over 9000 times.
Rebooting the phone over 9000 times.
Pulling the battery over 9000 times.
Reinstalling the drivers from Kies.
Turning USB Debugging mode off (was worth a try)
Using a different computer.
Reinstalling my OS (seriously, I had to do that anyway)
Leaving the phone plugged in for 30 minutes anyway just to see if it was working but not updating.
I am unable to boot into 'Recovery Mode' also the phone sh!ts itself and boots into 'RAM Dump' instead... where it requires a battery pull to reboot. So I can't even put the rom file on the internal memory and use recovery mode to flash it from there...
Basically nothing works at all. Odin 1.35 fails, Odin 1.85 fails, Multidownloader fails. I have tried rebooting, restart, and re-bloody everything I can. I have no idea why it won't get past setup connection. I've even tried using my second USB cable. It used to work fine, I used to be able to flash the phone fine.
Kies is NOT running in the background... there are no processes open or anything. I have googled and yahooed and everything to find a solution to this. NOTHING works..
Please help. I need to flash this dhfshfgdshgfshs phone as soon as possible. It's not working properly and it's really unstable..
If someone has any suggestions I am so willing to hear them..
Thanks a lot. - From a really frustrated dude
leijonasisu said:
I have tried everything on my wife's I9001 but I cannot get Odin to get past SetupConnection.
Click to expand...
Click to collapse
When you booted your phone, are you REALLY sure that you go into Download-mode?
When i was doing the same thing as you, i just enter Android Recovery (pressed Home+Vol Up+Power instead of pressing Home-Vol DOWN+Power)
Im not sure what buttons on your phone because im having a Note.
If you find this helpful, you could click Thanks
Thanks mate but I worked it all out. For some reason my I9001 wasn't being flashed in Odin properly like I explained. I accidentally screwed up my download mode. Sometimes I could get into Download mode by holding the corresponding keys. Volume Down + Home + Power. Sometimes the phone would just go black with a white dot at the top left corner.
Using a Jig I was able to boot into download mode without hassle. I then used Multi Flasher 4 to flash my phone seeing as no matter what Odin 1.85 and 1.3 would not work.
After that I did a factory reset so the phone was basically flashed twice. Everything seems to work well now. Before the factory reset the phone would just get into a boot loop.
Thanks anything. FeMod or whatever the clockworkmod for the I9001 is, wasn't working either. It would just go blank when I chose an option.
It's ok now. Thanks anyway but this can be closed.
Make sure Kies is not running. That was preventing me from connecting. :good:
Odin and xdadevelopers suck
Odin is buggy. Works on and off.
xda sucks because the owners of the site will have a single applicatoins dependencies spread across as many pages as possible in order to increase views and click through rates and sell ads to say, Bell Telecom perhaps?
F*n dicks at xda far as I'm concerned.
Wasting everyone's time and polluting the search results space.
Amen.
just do that
just enable usb debbuging
thanks
edwin_chenyh said:
Make sure Kies is not running. That was preventing me from connecting. :good:
Click to expand...
Click to collapse
Thank you alot bro. i was searching problem about half a year. you saved my life
I have the same issue with my Samsung Galaxy s2 (GT-i9100).
- Yes, Its really in download mode
- Have tried alot of diffrent versions of odin
My phone suddenly stopped working, can't start recovery and it doesnt boot at all.
The only thing I can do with it now is to enter download mode.
I might have flash something bad... dont really remember at all.
Had kies installed both the first version and klies3, all uninstalled now without any change...
THX
you're great, thank you very much bro : Iyi:: Iyi:: Iyi:
Hi i have n915f samsonge note edge after last update very restart or frizz when i work whit and go on downloading mode with out i press any key.i go recovery mode and wipes cach drive and restart on factory but Dissolving problem.when i want flash whit odin and turn on debugging mode not turn on my phone but when put cabe onit and hold power+Home +and volum key go on downloading mode.and detects with odin but when start stuck on setup connection.
Please help me.
Hey all,
I have unlocked my bootloader all went fine, then I flashed TWRP recovery but if I try to adb boot into recovery I get a screen with a little green android guy saying no command and if I do it manually I get the very same screen, what should I do? Should I try CWM or is this a bug I can fix?
Thanks k.. :good:
Please I am really stuck, I have tried flashing TRP a few times and even CWM to get root but anytime I boot to recovery I just get a green android guy with a red triangle coming out with a ! mark and under it saying No Command Please please help me out I have been reading and searching and cant get my moto e to boot into TWRP or CWM my bootl;oader is unlocked. All I am asking for is why am I getting this screen with the no command and what can I do to get into recovery so I can root my phone and flash a ROM.
:EDIT:
This is the Pic that comes up when I reboot into recovery only under the android guy it says no command
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Please someone, anyone help me i am really stuck on this and cant find a way out
RiceydDr0id said:
Please I am really stuck, I have tried flashing TRP a few times and even CWM to get root but anytime I boot to recovery I just get a green android guy with a red triangle coming out with a ! mark and under it saying No Command Please please help me out I have been reading and searching and cant get my moto e to boot into TWRP or CWM my bootl;oader is unlocked. All I am asking for is why am I getting this screen with the no command and what can I do to get into recovery so I can root my phone and flash a ROM.
:EDIT:
This is the Pic that comes up when I reboot into recovery only under the android guy it says no command
Please someone, anyone help me i am really stuck on this and cant find a way out
Click to expand...
Click to collapse
I thinl twrp not installed properly try cwm and install twrp over it
K I think I've done that already and keep getting the same screen... What's the latest cwm n twrp? I'll try some other methods of getting cwm on it.. Thank u for our reply I am getting stressed not getting into recovery to get root ughhh
Nope, still no joy getting the same screen... What is going wrong? Iv tried all d different methods on here followed them to a t but still can't boot to recovery. Plz help me out, I'm stressin big time!
after u flashed custom recovery...from fastboot.... don't reboot..... open recovery ..from fastboot(using volume buttons) just after flashing...... .. your custom recovery will be executed and it will stick ...
ps:- the green android screen with triangle..which is opening.....is stock recovery ......follow this method and your custom recovery will work
press thanks if i helped
OK I'll give it a try now, think I've tried that way already, I will flash TWRP again and try what you said.. I'll report back as soon as I've it setup. Thanks will be gave just for taking the time to try help work r not work u are trying to help... Thank u.
P.s How do u thank someone from the XDA App? :-?
Got it thanks gave 2 both ye guys r girls keep the help coming ikts appreciated!! I'll try flash now )
Lads I'm still getting no joy here :-/ iv used rookjunkies .bat super tool iv used other methods, nothing has worked. What am I doing wrong!?!?
RiceydDr0id said:
Lads I'm still getting no joy here :-/ iv used rookjunkies .bat super tool iv used other methods, nothing has worked. What am I doing wrong!?!?
Click to expand...
Click to collapse
have u done what i have told u to do ?
please explain your flashing process...
after flashing using fastboot DONT reboot..... go to recovery immediately
RiceydDr0id said:
Lads I'm still getting no joy here :-/ iv used rookjunkies .bat super tool iv used other methods, nothing has worked. What am I doing wrong!?!?
Click to expand...
Click to collapse
That's usually seen when you reboot to the Recovery menu. When you see that screen, press and hold Power, then press the Vol Up button at the same time. If you see the Recovery menu appear (it's in a small system font), use the volume buttons to highlight "reboot system now," and press Power to execute.
Failed to reboot into recovery mode from bootloader after flashing custom recovery
dchatterjee172 said:
after u flashed custom recovery...from fastboot.... don't reboot..... open recovery ..from fastboot(using volume buttons) just after flashing...... .. your custom recovery will be executed and it will stick ...
ps:- the green android screen with triangle..which is opening.....is stock recovery ......follow this method and your custom recovery will work
press thanks if i helped
Click to expand...
Click to collapse
Hi,
I tried your solution but unfortunately it's not working on my side.
I followed below steps,
1. Booted into fastboot mode.
2. Flashed custom recovery successfully. (tried both clockwork and twrp).
3. Tried to reboot into recovery mode by selecting option recovery from same screen of fastboot mode. phone flashes the as usual warning(bootloader unlocked) and gets turned off. Waited for 10 minutes but didn't reboot into recovery mode.
4. Pressed the power button and system reboots normally.
5. Again tried to reboot into recovery mode and facing the stock recovery not the custom one.
Any help?
Manish.android said:
Hi,
I tried your solution but unfortunately it's not working on my side.
I followed below steps,
1. Booted into fastboot mode.
2. Flashed custom recovery successfully. (tried both clockwork and twrp).
3. Tried to reboot into recovery mode by selecting option recovery from same screen of fastboot mode. phone flashes the as usual warning(bootloader unlocked) and gets turned off. Waited for 10 minutes but didn't reboot into recovery mode.
4. Pressed the power button and system reboots normally.
5. Again tried to reboot into recovery mode and facing the stock recovery not the custom one.
Any help?
Click to expand...
Click to collapse
I was also struggling a lot into getting twrp and cw loaded on to a Moto E. The problem was that I was pressing the Power button to activate the recovery menu and that will not activate the recovery option. You got to press the UP button instead of power. This is quite counter intuitive but described well in most posts, but as experts we assume up button is to go up the menu.
Sunish Issac
Hi Guys,
My Samsung Galaxy S2 SGH-I777 is soft bricked. It only goes into download mode when the usb cable is plugged and the (vol up down + power) buttons are pressed. When the cable is unplugged, it doesn't turn on. I've tried the following steps by creepyncrawly at last but couldn't get it to a working state.
1)Go to this post and download the Tar version of Siyah 2.6.14 Kernel. Flash it in the PDA slot without ticking Re-Partitioning. If you get a pass, it won't boot, so turn the phone off and then back to download mode and...
2) Flash the full stock Gingerbread distribution from the Download Repository, I777UCKH7 including the bootloaders and everything, in the PDA slot.
3) If you get a pass here, then the phone might boot, or you might have to boot into recovery first and perform a wipe data/factory reset. If you're able to boot the phone, then you are back in business, and can flash whatever firmware you want.
If it is not, then:
4) Download the SBL Bootloader from the Download Repository. Flash it as PDA in ODIN, without ticking Re-Partitioning.
5) Flash the Kernel, as in step 1.
6) Flash the full stock Gingerbread distribution, as in step 2.
Even before that I tried many other things from various forum posts.
Please help me to get this working again..
Thanks so much
Okay. The above are steps to overcome nand read-write corruption in the emmc memory. However, these steps should result in a working system installation under almost any circumstances. However, if there is emmc memory failure, not corruption but actual damaged memory, then it will be unrecoverable. Without additional information, it is impossible to say what the actual problem is.
So, since you say the above sequence fails, I need to know exact details of what happens when you follow the above instructions. I need a step by step description, what succeeds, what fails and in which step, and any text from the messages section of Odin. And anything else you can think to add that might be helpful.
Thanks so much for the reply.
The flashing process works fine, no error messages from odin or from the phone,
But
When it comes to the Android System Recovery Screen, I did the factory reset. After it reboots, load the Android System Recovery Screen again.
Then when I select the reboot option, phone reboots to the Android System Recovery Screen until the cable is plugged in, when it is removed, it doesn't reboot anymore.
In the Log there's a message that is suspicious, it says
"--Applying Multi-CSC...
Installing Multi-CSC
Can't access to /system/csc/ATT/system/
successfully applied multi-CSC"
And once i had something weird, when I flashed the secondary bootloader (step 4), phone seemed to load one step further than the samsung screen when onto the AT&T screen, but then suddenly it turned off and heard a few 'tik', 'tik' sounds.
Thanks so much for all the support, looking forward to an answer. Will upload some screens soon.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
You can safely ignore the message "Can't access to '/system/csc/ATT/system/'." This message is often present when the flash is fully successful, and at other times.
The telling message, however, is "Deleting Cryption Meta Data." This seems to indicate nand read/write corruption, and has been successfully repaired in at least a few cases that I am aware of, by using the above sequence.
So, I would suggest that you try going through the sequence again. It is a three step process, really.
1) Flash sbl.tar only using Odin. Tick F Reset Time, but untick Auto Reboot, so that the phone will not attempt to boot into system.
2) Flash the tar version of the Siyah 2.6.14 Kernel using Odin, having returned to download mode without trying to boot into system. Again tick F Reset Time, but untick Auto Reboot, so that the phone will not attempt to boot into system.
3) Finally, flash the stock Gingerbread SGH-I777UCKH7 tar using Odin, and this time tick Auto Reboot as well as F Reset Time.
If it doesn't boot into the system, you may still need to enter recovery and perform a wipe data/factory reset again.
Keep good notes about what happens each step along the way so that if it is not successful, we may get some clues.
Thanks so much for the help you're doing but unfortunately the results are the same as before
Same messages, for example "Deleting Cryption Meta Data" is always on top
Please give me another option.
BTW, I had to press Vol up + Vol down + Power button to get into download mode after the sbl is flashed because it wasn't restarting as per the option we set.
Also phone seemed to load one step further when I flashed the I777UCKH7 and the samsung screen went onto the AT&T screen, but then suddenly it turned off and heard a few 'tik', 'tik' sounds. weird !!!
Thanks so much
I don't have any additional "tricks up my sleeve."
It is possible that the emmc flash memory has become damaged, but this is far from conclusive. It is possible for the emmc flash memory to be damaged without the phone being completely hard bricked. In order to find out conclusively, you would need to send it to someone with equipment capable of testing the memory module.
From my observations of people who have posted about a problem similar to yours, including "deleting cryption meta data," there have been some cases where the phone was recovered, and some cases where it was not.
It is possible that it is a connection problem between the phone and the computer. I know of one case where a person kept trying to flash, and eventually the flash worked, but I don't remember if the problem he had was similar to your or not.
I also remember one case where a person got his phone going after using the pit file from the Download Repository, along with the Gingerbread tar. In that case, he had to flash the pit with the Gingerbread tar, and still wouldn't boot, but after flashing the Gingerbread tar again without the pit, it booted. Again, I don't remember is his problem was similar to yours.
Sorry I can't be of more help.
Thanks so much for trying to help me here. Anyways I'm trying to buy a new phone, I've been using this phone for 3.5 years and I think its time is up now. Thanks again ...
Please help me
Hope your phone can boot into fastboot mode.
Download and Flash the TeamSpain 15S recovery from here
Boot into fastboot mode. Turn the Phone off -> Power on using (Power button + Volume down). Connect to your PC and make sure Fastboot drivers are installed.
Pass this command fastboot flash recovery TWRP5.8TeaMSpaiNRevolution_15s.img assuming the recovery img file and fastboot are in the same directory.
Boot into recovery by pressing (Power + Volume Up) button combo. If you get Blue Led of Death, keep Power + Volume Up buttons pressed till phone boots into recovery.
Download TeamSpain Revolution 15s EUI ROM from here
In TWRP, Adb sideload the above rom.
Thank you I will try
Thank you I will try. please help me.
Can you tell me any detail.
Can you tell me any detail.
jakkapongjames said:
Can you tell me any detail.
Click to expand...
Click to collapse
What detail?
I change rom from model china x820 to indian x821. I try install TWRP but my devices just booted to a black screen with the blue led. I can try many method but doesn't work. it's show only quadcomm driver. what should i do?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi my le max 821 is also soft bricked can any one help please? It is going to fast boot mode, i have tried installing TWRP. It has shown that twrp has been installed, but when i tried to get into recovery it is showing a flashing blue screen and immediately the entire screen is going dark. Please some one guide me. Thanks in advance.
AJJU1972 said:
Hi my le max 821 is also soft bricked can any one help please? It is going to fast boot mode, i have tried installing TWRP. It has shown that twrp has been installed, but when i tried to get into recovery it is showing a flashing blue screen and immediately the entire screen is going dark. Please some one guide me. Thanks in advance.
Click to expand...
Click to collapse
You need to flash the correct recovery for 15s firmware. It is from TeamSpain.
Follow the instructions from this post. Click here.
sanke1 said:
You need to flash the correct recovery for 15s firmware. It is from TeamSpain.
Follow the instructions from this post. Click here.
Click to expand...
Click to collapse
Thanks Mr. Snake 1, will try this one and let u know the result.thanks again.
AJJU1972 said:
Thanks Mr. Snake 1, will try this one and let u know the result.thanks again.
Hi snake i tried this but no luck. But the good thing happened to me is, that after a long time i am able to get into the recovery. the "twrp" is working fine. I have downloaded the CM13 rom from your 'mega' link and adb sideloaded it, but it is not booting into the system, rather getting into boot loop again. The same blue screen is flashing and going dark, as earlier.
Can you please guide me, what am i doing wrong. I tried formating the system partition also(lost the stock rom also). Waiting for your respond. Thanks.
Click to expand...
Click to collapse
Hi snake i tried this but no luck. But the good thing happened to me is, that after a long time i am able to get into the recovery. the "twrp" is working fine. I have downloaded the CM13 rom from your 'mega' link and adb sideloaded it, but it is not booting into the system, rather getting into boot loop again. The same blue screen is flashing and going dark, as earlier.
Can you please guide me, what am i doing wrong. I tried formating the system partition also(lost the stock rom also). Waiting for your respond. Thanks.
AJJU1972 said:
Hi snake i tried this but no luck. But the good thing happened to me is, that after a long time i am able to get into the recovery. the "twrp" is working fine. I have downloaded the CM13 rom from your 'mega' link and adb sideloaded it, but it is not booting into the system, rather getting into boot loop again. The same blue screen is flashing and going dark, as earlier.
Can you please guide me, what am i doing wrong. I tried formating the system partition also(lost the stock rom also). Waiting for your respond. Thanks.
Click to expand...
Click to collapse
You have flashed 15s recovery and booted into CM ROM which is based on 14s or vice versa.
If you have flashed 15s recovery from TeamSpain, make sure that you flash CM ROM which is based on 15s or 16s only.
sanke1 said:
You have flashed 15s recovery and booted into CM ROM which is based on 14s or vice versa.
If you have flashed 15s recovery from TeamSpain, make sure that you flash CM ROM which is based on 15s or 16s only.
Click to expand...
Click to collapse
Thanks Mr. Snake1 finally i got my mobile working after a long time. Testing weather or not all the features are working. Post again with the results. Thanks a lot for your support.
Leeco le max 2 dead without system ...
good personal afternoon, I'm new here and I need help, I have a le Leeco max 2 and he came into loop after a atualizção for rom cuoco92, there installed TWRP the temspain downloaded the rom also the teamspain 15s and do the procedure by adb sideload and sometimes the protocol fail or lock in 47% already tried in every way to recover the device, tried to at OTG more this TWRP does not recognize the OTG cable, can anyone help me give me a light please, I'm the device locked to 1 month ...
A fix for hard brick you can find here http://www.letv.re/topic/1471-unbrick-le-max-2-qfil-rom/
Got the same problem but much worst.
I kind of have the same problem. But its different in its own way. The phone would turn off on its own. And soft brick for maybe 2-3 hours. And then unbrick it self. Meanwhile when u turn it on, you can feel the vibration of the device turn on, but no life on screen. When It does turn of it has the chance to turn on, show the "super powered by ecosystem" and then a blue square would cover the center of the screen. After that ur forced to turn it off again. And turn it back on hoping it won't brick again. When it does turn on normally, there is a chance it would just randomly power off and brick.(even if you are playing a game or browsing the web), I don't know if its hardware problem or software problem. (Btw iam typing this on a note pad so if the phone does brick, I don't have to type again.) It be great if you guys can help me out
Hey guys
I got really annoyed by not being able to delete photos in Google Images, so I decided to root and fix it.
Now, after having my data wiped in the process of opening the bootloader (had to register on LG dev, etc), I am stuck on the last step - I can't get into TWRP to flash supersu.
I flashed it with the fastboot flash recovery command, but then after doing fastboot reboot, and then using adb reboot recovery, I get into the stock recovery.
I found two fixes, none of which work:
1. after flashing TWRP, turn off, then use HW buttons to get into recovery. On the fifth try, I got to the "erase all data" screen, which allegedly should be ignored. So I ignored it, and it erased all my data again
2. use fastboot boot command to boot TWRP directly. Doesn't work, I get an "unknown command" error.
Any other ideas how can I proceed to rooting my V10 (H960A) would be much appreciated.
Are you sure that you are using the command right for flashing the TWRP?? That should be something like: fastboot flash recovery recovery.img
recovery.img --->twrp
Also you get information whether flashing the recovery was successfull or not. Read the output in the coomand window carefully. Maybe you can post a screenshot or at least the returned message.
Here's a screenshot after going through the process again:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hi,
flashing the recovery seems ok. Afterwards it seems vitally important that you switch off your phone, otherwise the recovery will be replaced by the stock revovery. Only after flashing SuperSu TWRP will be persistent.
Quote from the TWRP install instructions:
As on Marshmallow some fastboot commands are not working and LG is restoring recovery on every boot (so you cant use "adb reboot recovery" right now) you need to use one trick.
DO NOT REBOOT YOUR PHONE.
When still in fastboot from step 3 you need to turn off your phone completely. You can do that by holding power button or if that is not working take the battery out.
Now (put the battery in) and press POWER + VOL DOWN buttons. When you see LG logo release the POWER button (while still holding VOL DOWN) and press POWER button again. You should see a screen which is asking you if you want to factory reset your phone. Don't worry - if you made everything correctly it should not wipe your phone.
Use volume and power buttons to choose YES (twice) - and you should see a TWRP screen (after a while)
WARNING: IF YOU REBOOTED YOUR PHONE AFTER FLASHING RECOVERY THIS STEP WILL REALLY ERASE ALL DATA. You need to flash recovery again (step 3)
Click to expand...
Click to collapse
Also you tried to boot with the recovery image which is also not supported by LG.
I suggest you just flash TWRP again and do not try to reboot into recovery via fastboot command. Instead remove the battery right after flashing TWRP, wait a couple of seconds and put it in again. Then boot into recovery using the button combination decribed above.
I followed these steps three times with my phone (after updating the firmware) and it worked fine every time.
I tried it again and now I got through the whole rooting process.
Now I got stuck on the "Your device can't be checked for corruption" screen, which has been showing up on every boot since unlocking bootloader between the two animations, but now it's been there for a few minutes already.
Now what do I do?
****e, looks like I deleted my OS, while trying to wipe stuff in order to get through the boot freeze.
EDIT: I reinstalled stock ROM. Any ideas why it got stuck after rooting?
EDIT2: Installed the wrong ROM (some Tmobile branded version). Are there any custom ROMs for H960A running MM?
Hi,
no there are currently no Custom Roms for the H960A.
BTW: You will also get the "Your device can't be checked for corruption" screen with the correct ROM version. This is just a reminder popping up after bootloader unlock. After a couple of seconds the normal boot sequence will start.
I know, but the software version number now says H90110c
Also it's running 5.1.1. I can handle not having Nougat, but not back to 5.1 again...
I am searching for a way to get back my stock MM ROM, but there are apparently no ZIP or even kdz versions that work on the internet
Any help would be appreciated.
Yes, there are Android 6 kdz files for the H960A available, even in this forum:
http://forum.xda-developers.com/lg-v10/general/kdz-download-lollipop-kdz-10c-lg-servers-t3332348
Make sure you select the correct H960A version as there are two available: Europe and United Arab Emirates.
If the download does not work when you click on a link click it with the right mouse button select "copy link" (or similar, exact text depends on browser). Then open a new browser tab/windows and paste the link in the address field. Now the download should work.
You need to flash the kdz with LGUP.
In your case I would recommend the "REFURBISH" option in LGUP as it makes sure that the phone is completely wiped and reset.
As the refurbish option normally only allows tot-files to be selected you need to use a little trick. The below instructions are quoted from the LGUP thread (http://forum.xda-developers.com/g4/help/lgup-install-kdz-mm-lp-t3249803). Please look there if you need further information. You don't need to do the changes in the prop-file described at he beginning of the instructions. If you have not installed LGUP yet you'll find it in that thread as well.
TO DO A FULL WIPE AND INSTALL MM - Open the LGUP on your computer.
Select the option "update" (if not already selected).
FILE PATH: point it towards the MM KDZ file.
IMPORTANT!!!!!!! shut down LGUP!
Now open LGUP again - you will notice that the MM KDZ will still be showing in the FILE PATH section. Select REFURBISH and make sure BIN file is ticked. Press Start. Make cup of tea and be patient
Click to expand...
Click to collapse
Unfortunately, the downloads in that forum don't work, even after copy/pasting the link into Chrome, FF, even MSE...
I got two different kdz files from somewhere on the internet:
Europe H960A20a_00_0316
H960A10c_00_1224
None of them work. I got an error during the initialization phase saying the kdz file is incorrect.
Maybe it's because it says H90110c under version (as I said, I managed to install the wrong ROM after wiping everything)?
This is a nightmare. Please help