********* solution in POST 2 *********
Ok, i have double trouble situation here. As the title says i'm in a:
- TWRP bootloop (flashing TWRP logo, interval is about 1 min) AND
- custom ROM bootloop (it's not on the Samsung logo, it's pass that point, it displays boot animation [choppy], vibrates and then repeats vibrating, here it enters a loop)
How did i get to bootloop both? Well, i had TWRP 3.0.2.0 and custom ROM installed in my phone.
It was booting into system and into recovery without any problem and was able to use my phone UNTIL i decided to experiment and flash custom kernel via TWRP. It flashed ok BUT THEN i got stuck into this double bootloop situation. Custom rom/custom kernel interference probably.
Only thing i can access now it's the download mode. So i tried to use ODIN and flash latest TWRP(3021) over existing one (3020) - DIDN"T WORK!
Here i found that i can flash CWM over TWRP recovery and use it to factory reset, format partitions and flash another ROM to revive my device. Is this safe?
I think that since it's bootlooping because of a custom kernel, flashing stock will resolve this issue. But how to do that?
Never been in this situation before and i don't know any of the possible solutions to fix it.
I don't mind about the data, just to revive it!
Is there a hope? Can you help me? Please?
!
********* SOLUTION *********
This method works for me, it doesn't mean it'll work for you. SO PROCEED AT YOUR OWN RISK. I'm not responsible for any kind of damage you cause to your device by following this tutorial! Read carefully!
---------------------------------------------------------------------------------------------------------------------
First of all, make sure your battery is charged over 50%. If not, charge it.
Check you USB cable, make sure it's in good condition.
If you're using laptop, plug it in.
---------------------------------------------------------------------------------------------------------------------
Download all the zips attached, or the one you need.
- Install samsung drivers extracted from archive 1,
- Reboot your PC/LAPTOP,
- Extract CWM_6.0.4.7_Non-Touch_GT-I9300.tar image from archive 2,
- Extract odin from archive 3 and run it as administrator,
- Boot your samsung device into DOWNLOAD mode, MENU+VOL_DOWN+POWER, then press VOL_DOWN again,
- Connect it with PC/LAPTOP using usb cable,
- odin should recognize it and turn green under ID:COM section,
- In odin, under AP browse for extracted CWM_6.0.4.7_Non-Touch_GT-I9300.tar image and select it,
- Click START,
- Wait for the phone to reboot,
Now, if your samsung can boot into system, leave it boot.
If you also have a system bootloop like i did, then interrupt it once samsung logo shows up by taking out the battery, leave it out for ten seconds then pop it back in and boot into recovery by pressing MENU+VOL_UP+POWER.
- Done!
---------------------------------------------------------------------------------------------------------------------
Firstly wipe cache/dalvik cache, format /system, /data, then you can download and flash any custom ROM!
---------------------------------------------------------------------------------------------------------------------
.
You don't have to thank me!
.
Related
Hi guys, really need your help!!!
Been using Custom ROMs since Omnia HD. Loved the work of cookers, never had problems, ODIN is just so easy.
Four days ago, tried to flash I9100 from Lite'ning v5 to 6.1. So, as recommended I wiped cach with CWM, and then done proper FORMAT.
Once I pressed it, format started but didn't finish - the phone restarted, and continued to restart - stuck with boot "S" animation - so can't boot into system.
Then, tried as suggested to install VANILA latest firmware - tried it - didn't work. Keeps freezing in the middle of the process in ODIN - or - it says FAILED. Now, i can't use CWM - if I press Volume UP +HOME+POWER, i get "Mobile phone with yellow Triangle with PC signs" - left to the right.
Updating to the VANILA software doesn't work, so as Lite'ning V6, or any other versions of it. Without CWM, i can't boot from SD Card to other cooked roms, so please, any ideas will be MUCH APPRECIATED !!!
morespama2k .at. yahoo
I have never tried this before myself, but I have seen some people recommend trying an emergency firmware recovery with kies. If someone else can chime in and correct me if I am wrong, please do so.
emergency firmware recovery with kies - will try now, and update status...
Solution doesn't work
SugarySnack said:
I have never tried this before myself, but I have seen some people recommend trying an emergency firmware recovery with kies. If someone else can chime in and correct me if I am wrong, please do so.
Click to expand...
Click to collapse
This solution doesn't work. Because, all that I can do is to log into DOWNLOAD MODE, once I connect the phone via USB to PC with Kies ON, then the Kies doesn't recognise the phone in this mode, so there is opportunity or possibility to do an emergency firmware recovery - if anybody knows anything abt this - please comment ....
morespama5k said:
This solution doesn't work. Because, all that I can do is to log into DOWNLOAD MODE, once I connect the phone via USB to PC with Kies ON, then the Kies doesn't recognise the phone in this mode, so there is opportunity or possibility to do an emergency firmware recovery - if anybody knows anything abt this - please comment ....
Click to expand...
Click to collapse
Put the phone in recovery mode with Volume UP +HOME+POWER (it won't be CWM because you tried to flash stock, it is samsung's recovery mode), "Mobile phone with yellow Triangle with PC signs" and try it.
Let me know how it goes.
just checking... when you flashed through odin, was kies turned off? Meaning not even in the background and it's (process) not present in task manager?
Because that's what happend to me when i tried to flash a kernel to my SGS2. odin failed too but good thing my phone wasn't bricked.
Anyways, I would recheck the custom rom you downloaded, it sounds like the file was incomplete, or damaged during download. Always check the MD5 checksum, or at least the filesize.
Some custom ROMs cannot rebuild a formatted userdata partition. Most custom kernels cannot do that, so doing a factory reset (wipe userdata partition, format data partition, etc) is not recommended.
FIX:
Boot into Clockwork Recovery
Format cache, format system, format boot, format userdata partitions
Boot into Download Mode
Use ODIN to flash to Stock ROM
Boot into Stock ROM
Flash Custom ROM (Lite'ning), DO NOT FORMAT USERDATA and DO NOT FACTORY RESET!!
Boot into Lite'ning
CM7 using codeworkx kernel (CM7 kernel), is the only custom rom that does not have a rebuild userdata partition problem.
for my i9100 i solved this problem
i have the same issue and i solved with my i9100:
unmount battery and leave it for 20 sec
push up vol and home and keep it then put the battery !!!!! put vol up and home still pushed
if ....if you entry in recovery mode wipe data and cache and .... voila...
sorry for my bad english...hope this will work for you guys !!!
Jig from ebaaaaay .
Sent from my GT-I9100 using xda premium
I Have a I9100 ,It Has android cod ,I tried by hard reset ,hard reset complate but cod stil present.then i flash it by odin3 ,flash complate then start up and friz.then i open its Batery and put it again then try to flash again .but its sleeping now. dont going to download mod.not powering on .have any solution guys ?????????
Hi All,
First off, thanks for taking the trouble read my post!
In the attempt to root my I9100G phone using Odin and GT-I9100G_LP7_ClockworkMod-Recovery_5.5.0.4.tar, I stupidly followed the wrong instructions at: http://forum.xda-developers.com/showthread.php?t=1679778
I didn't have ICS - only GB - so I was completely wrong. Whilst Odin said success, the phone now only boots into Recovery Mode.
1) I can't enter Download Mode - I've tried but the Download screen just blinks and then CWM-Based Recovery Mode reappears.
2) I have tried wiping the cache
3) I have tried wiping data/factory reset
4) If I try to plug in the USB cable whilst in Recovery Mode, Odin does not recognise/detect the phone
5) The only way for me to shut down the phone now is to pull the battery out
I have also tried following Phistachio's Guide on "Fix an unflashable or soft bricked I9100G" but since Odin does not detect the phone when I plug the USB cable, I can't get past Step 3.
I'm a noob so according to the XDA video, I hate myself for messing up! I would appreciate ANY help - as I'm such a noob, please try to speak to me like you would to a 5-year old.
Thanks
------------------------------
Dear All,
I'm happy to report that by the grace of Jesus Christ alone - after trying multiple times to quickly press the Volume Up key when the Downloading screen blinked, Odin suddenly detected the device - and I immediate proceeded to flash it with superatmos_I9100G_kernel_v3.2.tar
The phone has now started up and I'm in the process of restoring backups.
Thank you!!
Wrong thread mate. This is only for GT-I9100, there is another one for the G version. Better ask there
Sent from my GT-I9100 using xda app-developers app
so u can boot into recovery mode.. why not flash another kernel through recovery mode
1)just pull out your SD card and connect it to ur computer through any SD reader
2)download the .zip file of any custom kernel u like and the put ur SD back in ur phone and flash that kernel and install that zip file from your recovery then wipe cache and data and see what happens
Note : u can do that also with a whole rom ( cwm flashable )
Solved!
Dear All,
I'm happy to report that by the grace of Jesus Christ alone - after trying multiple times to quickly press the Volume Up key when the Downloading screen blinked, Odin suddenly detected the device - and I immediate proceeded to flash it with superatmos_I9100G_kernel_v3.2.tar
The phone has now started up and I'm in the process of restoring backups.
Thank you!!
Hi all,
I think I broke my Galaxy S (I9000). I hope you can help me somehow. Here is the history of things I already did/tried
- my phone was working and had cyanogenmod 9.1 installed
- I wanted to give my phone a little speedup and wiped the cache and dalvik cache partition (did this before and it worked before)
- after this, phone was in a boot loop (even the battery loading animation rebooted over and over)
- the download mode still worked, but no recovery menu appeared!
- as given on cyanogenmod homepage in the install guide I flashed ClockworkMod Recovery using heimdall
- after that, recovery worked again
- I copied the cm9.1 zipfile on my phone to flash it, wiped the whole phone (factory reset), but flashing fails at some asserts (even though I disabled asserts) that seem to check that the target device really is a Galaxy S (I9000) (unfortunatly, I do not have a screenshot and cannot provide one now)
- I also had a ClockworkMod backup I tried to recover, but it fails at restoring /system (unfortunatly, I do not have a screenshot and cannot provide one now)
- so I thought, maybe I can use a regular firmware and flash it with Odin3 (1.87) to make things working at least a little
- started odin, selected firmware and started, but Odin3 got hung at some early point, so I closed Odin after ~10 minutes (see screenshot odin.jpg)
- when I now start my phone, only two symbols appear which kind of signal a problem with a connection to a (PC-)host which I have never seen before (see screenshot startscreen.jpg)
I tried a lot, but now I am out of ideas. Can you help?
Robert
missing attachments
Missed the attachments. Here they are.
Robert
Turn off phone, remove usb cable from pc if it's connected, remove battery, wait around 10 seconds, while battery is still not in the phone press the button combination for download mode. While u still holding the button combination for download mode, force reinsert the battery. Now phone should go into download mode automatically. Connect cable to pc and phone and flash stock Rom via Odin. Good luck
Worked! Great! Phone is back in download mode. Unfortunatly my work pc does not detect the Samsung composite device so I have to wait until I am back home. I hope Odin is working then. As given, it did not when I last tried.
Can you tell me what kind of mode this is, when those two symbols appear?
Robert
It's not any mode, it just an indication that earlier download mode flashing via Odin failed or interrupted by user.
U probably need to kill Kies process via Windows task manager before flashing with Odin because it's known to interrupt Odin, make it hung at setup connection.
Hi,
brought my phone into download mode again and this time odin flashed succesful. However, Kies was never installed on this computer so I have no idea why it worked now.
After flashing the phone rebooted, but stated several errors. They are similar to those which appear on reflashing with the cm91 zip via recovery mode ( "unable to mount ... (file exists)" ). I have made a screenshot and attached it. You have an idea how to help?
I have tried both the 512 and the 803 pit file, same results.
Thanks,
Robert
Tried to re reboot after those errors, but the S-Animation of the stock rom during boot never ended.
Robert
I took another stock firmware, JVI, which contains also a CSC and PDA image. Flashing worked, phone booted, Works!
I will see how to come back to my cm91, but a great step forward .
Thanks,
Robert
Made it back to cm91 . Thank you for your support.
Here are the steps ...
- applied I9000XWJVI.zip with 512 pit and repartition (2.3.3 based german stock firmware)
- applied I9000XWJW6_I9000DBTJW2_DBT (2.3.6 based german stock firmware)
- applied cf-root-xx_oxa_jw4-v4.4-cwm3rfs.zip as this clockworkmod recovery is able to disable verifications before appling a zip
- applied cm91 zipfile
- restored my backup
Robert
Hello all,
First of all, as a disclaimer: I am a total noob in this area. I just got my Ulefone T1, and tried to root it by installing TWRP and then installing SuperSU using TWRP. When I first installed TWRP, it worked and I got into the TWRP recovery menu. However, as the phone had to be wiped, I couldn't install the SuperSU zip anymore. I did a normal reboot to transfer the SuperSU zip to my phone, but when I then tried to turn my phone off and access TWRP, it went to normal recovery mode of my phone. As I wanted to start fresh off again, I went to the settings of my phone and did a factory reset silly.
Now, it is stuck in a bootloop where I can literally do nothing. I cannot access factory mode or recovery mode, all it does is just endlessly boot and turn off. I have managed to turn it off completely, but that's all I can do. Also, the battery is not removable.
Does anyone with a little more knowledge have a suggestion for me? Thanks in advance!
As an update, I got a suggestion to fully drain the battery, but that does not work either. I have tried connecting it to my PC, which is not working, but that was acting weird before. I guess it's just not possible?
did you work this out ? i am stuck in bootloop too ??????
Daviesjosh95 said:
did you work this out ? i am stuck in bootloop too ??????
Click to expand...
Click to collapse
I have no idea what software is necessary to do it for your device but you can flash stock rom, if it uses sp tool or something then download stock rom, use sp tool to flash it. Should be OK after that. As I am not familiar with this device I can't give you any other advice other than flashing stock rom.
Any solutions to unbricking/boot looping?
Have anyone found any solutions to unbricking phone??
Mine also did bootlooping after unlocking bootloader.
I was able to flash successfully but screen fussy and unreadable and not able to touch. I am able to hear but lines are on screen.
I have same problem, please, anyone help, I think I used wrong twrp image
Ulefone T1 Bootloop solution 2019.
I was able to fix the bootloop of my ulefone t1, just flash it with sp flash tool by following this guide:
1. Download the Stock Firmware on your personal computer.
2. Install the USB MTK Drivers (skip if you have it already installed).
3. Download and Launch the Smart Phone Flash Tool (SP Flash Tool)
4. Click the Scatter-loading button to navigate to the stock Rom you just downloaded.
5. Select the Scatter File from the extracted Stock Firmware on your computer.
6. Select the Download Only in the SP flash tool option
7. Click the Download button to start the Formating process.
8. Connect your device via USB to the computer>> holding volume + and volume – button of your device at the same time or holding power button only so that the flashing process will starting working
9. Patiently wait for your device to be formatted.
10. After the formatting is done, a Big Green button will pop up on the SP Flash to show that.
11. Unplug your device and boot it up.
12. If you have a boot loop after booting your device, boot into recovery mode and do a factory reset.
13. Voila, you are all good.
Very important step 8 of the guide.
Hi Community,
I read some posts how to fix my Problem, but i cant go to a service Point.
So I was using the Evolution X for a long Time (Installed with TWRP 3.1.0).
And now i wanted to change to the Nusantara Project (Vanilla), I did a clean Flash, everything worked i could access the System.
Than i had problems installing Play Store, so i rebooted into Recovery via the System. But now im Stuck in the Loop.
Can i Somehow connect my Phone to the PC and Reset?
Can someone tell me if i Hard/soft bricked my phone ?
Just a little advice, would be really appreciated.
Thanks a lot
Go to TWRP, wipe system, cache, data and dalvik. Now flash nusantra and whichever GApps are recommended for it (if there are no recommendations then use OpenGApps, make sure the architecture is correct). Now wipe dalvik and restart. Sometimes, certain roms begin to bootloop if you boot into the rom first, then try to install gapps later.
If you still have issues, just reflash the stock rom.
I cant access the TWRP anymore, im just stuck on the Bootloader, no matter how i turn on The Phone (Volume Up + Power ON ), (Volume Down + Power), (All 3 Buttons)
Nothing works anymore i dont understand ....
Im searching the net but i cant go to fastboot or something else, its just keeps on rebooting ...
So it's bootlooping, but you cant access recovery?
When the screen turns off, press the key combo and it should go to recovery.
Your best bet is to take it to a service centre, but if that really isn't possible for you, then wait for its battery to drain completely, then when you plug in the charger, instead of turning the phone on, press the key combo to enter the recovery. From there, wipe and flash some other OS.
I've also heard that certain versions of TWRP don't support some roms, leading to a bootloop. In that case, you'll have to use orangefox recovery to flash the rom (orangefox is flashable via twrp)
Yes its Bootlooping.
When i turn it on, on the Left Corner "Recovery Mode" blinks for one second. Than the usual Text appears:
"Orange State
Your Device has been unlocked and cant be trusted
Your Device will boot in 5 Seconds".
So after a couple of seconds (around 10-20 sec)
It turns off and immediately on again. I Just can turn it OFF when i hold all 3 Buttons.
Than i try starting it with Volume up + Power / Volume down + Power, But i cant access Recovery or TWRP.
So i should wait til the battery gets low and try it again ?
Like i said, my custom Rom (Evolutionx) and TWRP just worked fine. I dont know man ...
Well since your bootloader is unlocked, try flashing the stock rom again. Look for a tutorial and follow it.
Hi I managed to unbrick my device with this guide, and im back on a stock rom
Unbrick
i ran following commands to get to my custom rom:
I run adb reboot bootloader,
add executed following commands.
(Pitch Black recovery 3.1)
- adb reboot bootloader
- fastboot flash recovery recovery.img
-fasboot reboot recovery
It just hang up and booted after a while into the normal system.
But im not able to get to the recovery menu ?
When I restart and hold Volume up + Power, i go in a loop and the phone keeps restarting over and over again.
what have i Fu**ed up ?
Do i need another recovery tool ?
sorry guys, i appreciate your help a lot tho !
EDIT: Is my bootloader unlocked ?
I can access via "adb reboot bootloader" the phone
and on the blackscreen on the phone it is written:
oppo verfiy pass
fastboot_unlock_verify ok
Update:
So i tried some Stuff and i got Red State. No Problem i Unbricked it once again and now im on Stock Android 10.
Now im Trying to enable the bootloader again.
I downloaded the In Depth Test_Realme_6.apk but i keep getting the Error that i should update the system.
So should i update the system ?
I cant find a CURRENT Tutorial to make this work, please help...
If you cant find a tutorial for your version, why not downgrade back to a previous one if possible.