Hey guys,
So, I tried to flash HKTW, but I'm new at this, and I believe I screwed something up. I installed Tenfar's CWM Recovery and flashed from that, using the CWM version of HKTW. I didn't wipe anything, and I didn't do a backup (and I cringe to write that -- I'll do better next time, I promise!). Now I can't boot into the OS -- I just hang on my the Motorola boot splash -- but I *can* get into recovery/fastboot/etc. I tried flashing stock 1.8.3 using fastboot, but I still can't boot. I have no doubt I've done at least one incredibly dumb thing here, and probably a whole collection of them. I'm at your mercy, guys. Can you help me out?
Related
Hi all,
So coming from a Samsung craptivate, Im having a little bit of trouble flashing CM 6.1.1 on my new N1
so far starting from stock I have
- Unlocked the bootloader
- used fastboot to flash the latest clockworkmod
now I am trying to boot into recovery to flash the CM zip on my SD and I keep getting to a screen with the android guy and an exclamation point, and have to do a battery pull to reboot, I have tried using adb and 3 button combo to get into clockwork,
so, what idiotic thing am I doing wrong?
You're booting in between installing the recovery and booting into recovery.
There are two files that restore the stock recovery upon a system boot (which is what you are seeing). If you go straight to recovery after flashing, the stock recovery won't be restored, then you can install a custom ROM.
The two files are missing from custom ROMs, so you won't have this problem again.
Typically, people remove these files once they have root access, but since you don't have root yet, that isn't an option...
Sent from my Nexus One using XDA App
thanks very much for your help, got it working
Reading the Wiki guides for installing recovery should have solved your question before you wrote it.
hi guys,
my find 5 was having some reboot issues (it was rebooting a few times per day) and that was a bit anoying. I was using an old original FW so i decided to update to a newer one. Heard good stuff about the Omni so i went for that, so i was using TWRP 2.4.1.0 (i think... i'm sure it was 2.4.x) and on the omni page they said we have to use TWRP 2.6 so i went for an update.
here, i think, i've created my problem. I used the new flashify app to install the TWRP but instead of choose recovery img i choosed to flash the boot and i guess i'd flashed the TWRP on the boot.
well anyaway, now i'd installed the TWRP 2.6.3.1 i manage to start the phone in fastboot and recovery all good here, i install every rom nice and easy over TWRP but the phone simply doesn't start, it gets stuck on Touchscreen Firmware Update please wait.... this happens ALWAYS with what version of TWRP or even if i install CWM...
my guess is that i'd messed up some partition or so i don't really know what but i'd tried to format every partition that TWRP let me and still getting the freackin Touchscreen Frim updt screen... so need some Pro help to help me undo the mistake i'd done...
thanks for everything
On the official Oppo forum's there's a guide on how to install the latest Omnirom. Under known issues it says:
5)After installing the TWRP recovery the Screen Touch firmware update goes on for more than 5-7 minutes, do a hard reboot and you would be fine,
Click to expand...
Click to collapse
I haven't tried it myself since I didn't get the problem when flashing Omni and Asylum, but it seems to be worth a shot.
In case you are looking for the topic, search for "How to Install OmniRom 4.4".
I have rooted and installed ricks rom using safestrap. Everything worked well until today. Long story short I tried using safestrap to install a new ricks rom. I get stuck on activation screen so I rebooted phone and messed around with safestrap. somehow my phone is now stuck on boot and I can only get into adroid recovery from the boot screen. I am stuck here and cant figure out what to do next? Is there a way to install a custom recovery from this point? any help would be appreciated.
Yes, you can flash another custom or stock recovery to rescue from this problem.. Try this, may this'll help you..
I tried that but it would not work. I finally used odin to flash the stock rom and got my phone back to normal again.
Hi, today i just played with file systems today and now i can't install any other roms excepting supermanrom. So i think i have a problem with file systems. Which file system does s7 edge using for default? Can any master help me? After im installing any rom it's stuck at bootloop
Which one should i use for example system and data file? ext4 or f2fs or any other?
Can you give us some more information?
if your stuck in boot loop? can you not boot into twrp?
Did you turn off OEM unlocking in developer options?
If you can load twrp? lots of info on returning to stock on here
just use search for installing to stock after bad flash.
Or other option would be flash another custom Rom.
Or are you saying you cant do any of the above?
If so what errors are you getting? it may help others that know more on
returning to stock.
I only flashed my first Rom to my S7E a few days ago after two bad flashing and had to have phone fixed in shop
to be honest I just did not read every thing and missed out apart and got stuck in boot loop.
but this time did the same but had twrp installed and just kept reading up on errors i was getting and in the end
i got it sorted.
May not of been much help but hope you get it sorted.
Good Luck
leggoman said:
Can you give us some more information?
if your stuck in boot loop? can you not boot into twrp?
Did you turn off OEM unlocking in developer options?
If you can load twrp? lots of info on returning to stock on here
just use search for installing to stock after bad flash.
Or other option would be flash another custom Rom.
Or are you saying you cant do any of the above?
If so what errors are you getting? it may help others that know more on
returning to stock.
I only flashed my first Rom to my S7E a few days ago after two bad flashing and had to have phone fixed in shop
to be honest I just did not read every thing and missed out apart and got stuck in boot loop.
but this time did the same but had twrp installed and just kept reading up on errors i was getting and in the end
i got it sorted.
May not of been much help but hope you get it sorted.
Good Luck
Click to expand...
Click to collapse
I can boot into twrp but i cant flash stock frimware with odin. It's giving FAIL error to me immidietly when im trying to do. And yes, OEM was open before
Now i flashed stock rom via odin, but when i install twrp again on my device it stucking at boot loop. Why?
Then i realized something that whatever i flash something via odin or something else, its stucking at bootloop
sdiown said:
Hi, today i just played with file systems today and now i can't install any other roms excepting supermanrom. So i think i have a problem with file systems. Which file system does s7 edge using for default? Can any master help me? After im installing any rom it's stuck at bootloop
Which one should i use for example system and data file? ext4 or f2fs or any other?
Click to expand...
Click to collapse
Format all with ext4 (in twrp). Especially the system. Because all touchwiz cusrom can only run on ext4. After all normal, you can just format to f2fs for data and cache
Hey, I'm new here when it comes to writing forum posts, so bare with me.
I've had this tablet for a few years now and I had flashed it with one of Magendanz roms (Nexus Stock) and I wanted to change to the LineageOS rom he had. I downloaded the .zip file and copied it to my sdcard and tried to get into TWRP to flash it. I did restart to recovery in the OS and once it restarted, it's been doing a boot loop ever since. I have tried using Odin to flash the rom that way, but for some reason it'll keep doing a boot loop after it's done flashing and restart. I can try going back to the stock firmware if it's a final option to get this tablet working again, but I would love to see if I can get LineageOS to work.
DengekiMatsuko said:
I did restart to recovery in the OS and once it restarted, it's been doing a boot loop ever since.
Click to expand...
Click to collapse
I had a similar issue once. It turned out that after flashing, not all the partitions mounted properly.
Are you still using TWRP? Boot to recovery, and go into "Mount". Make sure the system and other partitions are actually ticked. That solved the problem for me, and I was able to successfully boot to the system.
Hopefully your issue is that simple!
I managed to brick my Tab A 10.1 (2019) last year by dirty flashing ROMs I shouldn't have. I properly munted it, I couldn't even get into recovery. But I could still get into download mode with a USB cable plugged in to my laptop (it needed to be plugged in for download mode to come up). I flashed the stock ROM, which made it bootable again, which then allowed me to re-flash TWRP and then Magendanz' LOS18.1 ROM.
If you completely break your tablet, reflashing the latest stock ROM for your region is a great way to get back to a familiar starting point. You can then follow people's guides online to get where you want to be.