So I recently installed arrow OS on my device and rooted it. Everything went fine except screen mirroring didn't work anymore, so I tried to fix it by adding just one line in the build.prop file (I don't remember what this was) and it got stuck in a boot loop. When I turn my phone on, it works for a minute, then freezes and shuts down. I got rid of the changes I made in build.prop but the problem still exists. Then I tried flashing arrow OS again, but that didn't work either. Please help.
I think you should try flashing the stock rom using official mi flash
Or EDL mode
It should work for most xiaomi devices
Related
Hello I am searching for help. The problem is that my galaxy s2 i9100 stopped working properly. It started like this maybe I took out the battery or something I don't remember and then I turned it on the phone wouldn't boot. I thought maybe my android operation system got bricked so I decided to re flash it but as I can remember the phone wouldn't go in to download mode but some how I managed to reflash the firmware but then phone booted it just froze and then I pressed lock button the phone screen would go black and reboot. After installing cyanogen mode 11 the phone would boot and it could be used again until pressed the lock button it would go black and reboot so I have been reading forums and found problems like boot loop corrupted mmc or something else corrupted and I don't know what the real problem is because the symptoms are like boot loop or corrupted mmc or soft brick. I have already tried other kernels other android versions clock work mode
migimantas said:
Hello I am searching for help. The problem is that my galaxy s2 i9100 stopped working properly. It started like this maybe I took out the battery or something I don't remember and then I turned it on the phone wouldn't boot. I thought maybe my android operation system got bricked so I decided to re flash it but as I can remember the phone wouldn't go in to download mode but some how I managed to reflash the firmware but then phone booted it just froze and then I pressed lock button the phone screen would go black and reboot. After installing cyanogen mode 11 the phone would boot and it could be used again until pressed the lock button it would go black and reboot so I have been reading forums and found problems like boot loop corrupted mmc or something else corrupted and I don't know what the real problem is because the symptoms are like boot loop or corrupted mmc or soft brick. I have already tried other kernels other android versions clock work mode
Click to expand...
Click to collapse
I have found that my emmc has the insane chip bug. The phone boots normally with cyanogen mode 11 but then it goes to sleep mode or I press the power button the screen goes black and the phone restarts. I have tried siyah kernel to try dual boot but then I flash siyah I cant get into recovery.
I think you should flash latest STOCK ROM with Odin, and then follow available custom rom instructions on xda...
Test if the stock rom will work for you, boot your phone etc... Try to use it a few days. If everything is OK, proceed with
further procedures...
twinsen.net said:
I think you should flash latest STOCK ROM with Odin, and then follow available custom rom instructions on xda...
Test if the stock rom will work for you, boot your phone etc... Try to use it a few days. If everything is OK, proceed with
further procedures...
Click to expand...
Click to collapse
I have already tried this but with the stock rom phone boots but at the section where I have to chose language I jus freezes stops working
So I think it is a hardware problem. Phone on stock rom shouldn't freeze on language selection. Something is wrong. If you are on warranty, let them fix it for you, if you are not, try to fix it in some phone repair point. I'm sure you can stop your attempts. It will not be better for now.
twinsen.net said:
So I think it is a hardware problem. Phone on stock rom shouldn't freeze on language selection. Something is wrong. If you are on warranty, let them fix it for you, if you are not, try to fix it in some phone repair point. I'm sure you can stop your attempts. It will not be better for now.
Click to expand...
Click to collapse
Take it straight away to the official service centre
(backstory) Hi, ive had an Asus TF300T, for about 3 years now, unlocked, rooted it pretty early on... cycled between cyanogenmod and omnirom quite a bit, without really any major issues. Until today, i was running Cyanogenmods latest nightly build (CM11 Nov 5 2014), it worked just as any other nightly does a few bugs here and there, but nothing major and i hadn't done any major flashing or modding to the device. On my home from university, I turned my tablet off. And when i got home i plugged in the charger, and just as always the tablet turned on, showed the stock Asus screen, then changed to the Android boot animation... the animation then suddenly froze, and the device went into a boot loop... continuously... I dont know whats weong with it... tried to do a factory reset, i tried reinstalling the ROM, tried installing omnirom, but that got stuck on the OmniRom animation...
Im running Asus build 10.6.1.27.5
I had TWRP v2.7.0.1 installed but have now no longer works
id really hope there is a solution for this!
Thanks!
Edit: I dont know why, but when i try using fastboot or adb, the device isnt recognized. It doesnt show up on device manager either. I dont know if its the cable cause i bought it new, it says its can sync data, or a faulty charge/sync port....
razr9622 said:
(backstory) the tablet turned on, showed the stock Asus screen, then changed to the Android boot animation... the animation then suddenly froze, and the device went into a boot loop... continuously... I dont know whats weong with it... tried to do a factory reset, i tried reinstalling the ROM, tried installing omnirom, but that got stuck on the OmniRom animation...
Im running Asus build 10.6.1.27.1 (I know that theres a newer version 10.6.1.27.5, but when i try to flash it, the recovery says error and fails)
I have TWRP v2.7.0.1 installed but have now no longer works
id really hope there is a solution for this!
Thanks!
Click to expand...
Click to collapse
^THIS!
I was just to open a similar thread, then i saw your post. I join your request for help!
A month ago i have done a favor to a friend by unlocking his tf300t and installing CM11 on it. A few days ago he comes to me with this problem. I've tried anything but still no success:
- restore a backup done before flashing CM11 --> restore ends correctly but the problem remains
- flash a rom (CM11 and OmniRom) --> flash ends correctly but the problem remains
- flash the stock firmware found on asus website (WW_epad-user-10.6.1.27.5.zip, the SKU is correct for my version) --> the flash process stuck (i had to force restart the tablet after almost 2 hours of "flashing")
Since the boot animation changes according to the rom, i suppose the flashing process works. But the problem remains: after a few seconds the animation freeze and the device restarts, in loop.
Informations on the system:
- build 10.6.1.27.5
- TWRP v2.7.0.1 (working!)
- adb works (i managed to set /data as rw and push the .zip file to flash)
- fastboot should work
Please help! I feel a bit responsible for bricking my friend's device
SOLVED!
Finally!
I had already tried this method, before requesting for help, but the first time didn't worked... I don't know why this evening the tablet decided to collaborate:
http://forum.xda-developers.com/showpost.php?p=44244313&postcount=12
That worked for me! :victory:
Hey everybody,
I just have a serious problem with my LG G4 H814. Yesterday I was just sitting there, using some Apps and suddenly the application ges frozen and after that the phone just more or less turned off. (So the screen gets black). I tired to replace battery and all this stuff but doesn't work.
Next thing to do for me was to boot into TWRP try to fix problem with wiping dalvik cache and/or restore by nandroid backup...
Problem beeing: I cant boot in Recovery Mode either! Just doesn't work... So I tried to boot in the Stock Recovery of LG to do a factory Reset, wasn't able to do that either!
So last try... reboot into Fastboot Mode (Download Mode) and try rebooting into recovery via adb comands...!
Problem beeing: can't get into Fastboot Mode!
I tried to connect Phone via Bootloader but deosn't work.
So now I'am at a point where I can't turn on my Phone! I mean it wont start up...The screen stays black, no Logo is showing up, no LED NOTHING!
The battery icon doesn't show up when I try to charge my phone...
So tell me: WHAT THE FVCK IS HAPPENING HERE? Do you have any idea on what to do except for bringing it to carrier?
I just want to get to my Data on phone...rest doesn't matter. I could set up everything again?
Device information:
LG G4 H814
TWRP
Xpsosed Framework running (v75 i think)
Modules were working just fine (before everything happened I did an reboot so that the modules are active!
lmfgpeace said:
Hey everybody,
I just have a serious problem with my LG G4 H814. Yesterday I was just sitting there, using some Apps and suddenly the application ges frozen and after that the phone just more or less turned off. (So the screen gets black). I tired to replace battery and all this stuff but doesn't work.
Next thing to do for me was to boot into TWRP try to fix problem with wiping dalvik cache and/or restore by nandroid backup...
Problem beeing: I cant boot in Recovery Mode either! Just doesn't work... So I tried to boot in the Stock Recovery of LG to do a factory Reset, wasn't able to do that either!
So last try... reboot into Fastboot Mode (Download Mode) and try rebooting into recovery via adb comands...!
Problem beeing: can't get into Fastboot Mode!
I tried to connect Phone via Bootloader but deosn't work.
So now I'am at a point where I can't turn on my Phone! I mean it wont start up...The screen stays black, no Logo is showing up, no LED NOTHING!
The battery icon doesn't show up when I try to charge my phone...
So tell me: WHAT THE FVCK IS HAPPENING HERE? Do you have any idea on what to do except for bringing it to carrier?
I just want to get to my Data on phone...rest doesn't matter. I could set up everything again?
Device information:
LG G4 H814
TWRP
Xpsosed Framework running (v75 i think)
Modules were working just fine (before everything happened I did an reboot so that the modules are active!
Click to expand...
Click to collapse
You might want to post in the G4 general or where the H814 model is specific (is that T-Mobile?) This forum is specific to the H810 ATT version.
Additionally, you can see the posts about TOT method for restoring your phone, however this will completely wipe your data.
warri said:
You might want to post in the G4 general or where the H814 model is specific (is that T-Mobile?) This forum is specific to the H810 ATT version.
Additionally, you can see the posts about TOT method for restoring your phone, however this will completely wipe your data.
Click to expand...
Click to collapse
I think H811 is T-Mobile.
Lg G4 H815 T mobile
Same here with my H815 from T mobile. After a forced update of a start up T mobile screen it stops working and gets in a boot loop. all key combinations don't work so can't start in safemode
my g4 h810 does not turn on. no download mode, no recovery, black screen but can be detected by PC when connected via USB. recognized qualcomm 9008 thing. drivers were successfully installed. Mobile feels lifeless except when connected to PC.
any ideas what's going on, does it mean that my phone is hard-bricked? how to resurrect it?
Hi, I've got an Honor 9 with unlocked bootloader and everything, today I was trying to change version of the Twrp because the one I had gave me some problems. So I decided for an older version ( "stf-twrp-zxz-0.2.img" found here), I flashed it and rebooted, but it freezed with the Teamwin logo and whatever combination of buttons I try to shut it down it keep booting in recovery, ending stuck in that situation. Thank you for your time.
P.S. If I connect the phone with a computer adb recognize the device and works fine, but I don't know how to handle it.
Please help me out as I messed my phone up real bad recently and I need to fix it as soon as I can as I have interviews right now and need to be updated with them.
So here's what I did:
I was using Pixel Experience ROM on Android 12, with OrangeFox recovery, it was working fine with no major issues.
I really wanted to try out Android 13 though it's still in Beta but I have heard good things about it, specially the one by Project Elixir.
But since I was already using Pixel Experience and loved the ROM so much, I decided to be on the safer side and look if they have a Android 13 ROM for my phone.
That's where the story began, I mistook the Redmi Note 7 forum (lavender) as Redmi Note 7 Pro forum, I forgot how they were two separate devices.
So I flashed the Redmi Note 7 recovery on my phone and it it didn't boot into recovery when I tried it to, then I downloaded the original (correct one) from OrangeFox's official site and flashed it after which the recovery works. But then as I tried installing the new ROM, my adb sideload kept getting stuck at "Starting ADB Sideload feature" and I couldn't make it work, so I flashed the new OS from my sdcard. It was all fine, I set it up and was loving the experience until I plugged it out of the charger. After a few minutes of plugging it out of the charger, it literally started rebooting and it restarts just in the middle of the boot animation. And when I manually power it on by pressing and holding the power button, it displays that It has no charge left.
I tried flashing quite a few other ROMs too, even Android 12 and 13 both, and at a point for some reason it also showed "system has been destroyed. press the power button to shut down" while booting into recovery but it went away once I re-flashed the recovery, and after no luck, I flashed MIUI but the same thing still persists.
I read in a few forums that it might be a battery issue which I too thought at first but the fact that it happened exactly after I flashed the wrong recovery bothers me. I thought installing the stock MIUI rom through fastboot would solve it by replacing every corrupted files and partitions but the issue seems to persist.
What might have been the issue and what can I do to fix it, and can flashing a wrong recovery cause this even if I have flashed the right one just after that?