Hey everyone,
I am very new to the OP7TP, comming from an HTC U11 which is.. old and very different.
Anyhow on to my problem:
When I got my new device I decided to get rooted, and then chose to use reseruction rom.
Which was a pretty nice experience, but I also wanted to see what else was being released, and Havoc came along.
I flashed Havoc according to the instructions on telegram, using fastbootd..
But when I went to boot it just kept rebooting to Bootloader mode
I restored my device using MSM, and triedagain, with the same result
But now, for the real trouble: reseruction rom does the same!
When flashing it, it will just reboot to bootloader every time.
It seems I can't flash custom roms anymore?
The stock OOS rom seems to be fastbootd and MSM flashable and boots without issue.
Has anyone encountered this before? any advice on how to proceed?
I am using the European OP7TP HD1913 with latest stable OOS 10.0.9 HD01BA
Solution:
Well I do feel silly now..
I flashed Reseruction Remix using my Desktop
Flashed Havoc (and all other attempts) using my notebook
And even tho I installed, which I thought were the correct fastboot drivers, evidently they are not..
When I tried flashing Havoc using my desktop it worked instantly..
It was just fastboot.. no errors during flashing, wiping, erasing and such... but it did something wrong..
Giblet-dono said:
Hey everyone,
I am very new to the OP7TP, comming from an HTC U11 which is.. old and very different.
Anyhow on to my problem:
When I got my new device I decided to get rooted, and then chose to use reseruction rom.
Which was a pretty nice experience, but I also wanted to see what else was being released, and Havoc came along.
I flashed Havoc according to the instructions on telegram, using fastbootd..
But when I went to boot it just kept rebooting to Bootloader mode
I restored my device using MSM, and triedagain, with the same result
But now, for the real trouble: reseruction rom does the same!
When flashing it, it will just reboot to bootloader every time.
It seems I can't flash custom roms anymore?
The stock OOS rom seems to be fastbootd and MSM flashable and boots without issue.
Has anyone encountered this before? any advice on how to proceed?
I am using the European OP7TP HD1913 with latest stable OOS 10.0.9 HD01BA
Solution:
Well I do feel silly now..
I flashed Reseruction Remix using my Desktop
Flashed Havoc (and all other attempts) using my notebook
And even tho I installed, which I thought were the correct fastboot drivers, evidently they are not..
When I tried flashing Havoc using my desktop it worked instantly..
It was just fastboot.. no errors during flashing, wiping, erasing and such... but it did something wrong..
Click to expand...
Click to collapse
Everytime I flashed havok I had to wipe data after flashing the ROM when it was in boitloop I held all buttons. Then went to recovery and wiped data then it booted fine
Related
Hi,
I have quite a serious problem with my phone.
I used stable CM11 as my ROM lately, worked nice, seemed to be ok. Now, if I want to boot my phone, it suddenly crashes as soon as I want to enter unlock code. "Funny" thing is, performing a full backup via TWRP didn't help.
So I decided to wipe everything (even sdcard) and do everything from scratch, including flashing boot.img. After flashing the ROM zip, it's still the same.
After that, I flashed boot.img from AOSP 5.1 Unstable, installed this new, different ROM (which I had successfully tested on my device before) and STILL THE SAME?!
What's going on here? It sounds a bit like defective hardware, but I never experienced a crash when I was in Recovery mode, so that's quite unplausible.
My last idea is to flash stock ftf. Perhaps this will help...
Was running the unofficial lineage 14.1 rom, was getting frustrated with all the gps problems so I decided to try fulmics. Well cell service didn't work on fulmics, so I wanted to switch back and tough out the gps problems until lineage team got things fixed. Recovery seems to be working fine, but any rom I try to install simply endless reboots before every getting to the initial set up. I am at a loss, I am thinking I didn't have the new lg bootloader as I was told to have before trying to install fulmics. How the hell can I fix my phone? I always thought as long as recovery worked I would be fine, but that doesn't seem to be the case. Anyone help before I have to go out and buy a new phone tomorrow?
jamesvmccann said:
Was running the unofficial lineage 14.1 rom, was getting frustrated with all the gps problems so I decided to try fulmics. Well cell service didn't work on fulmics, so I wanted to switch back and tough out the gps problems until lineage team got things fixed. Recovery seems to be working fine, but any rom I try to install simply endless reboots before every getting to the initial set up. I am at a loss, I am thinking I didn't have the new lg bootloader as I was told to have before trying to install fulmics. How the hell can I fix my phone? I always thought as long as recovery worked I would be fine, but that doesn't seem to be the case. Anyone help before I have to go out and buy a new phone tomorrow?
Click to expand...
Click to collapse
PMd you.
I found a fix, I completely wiped everything and first flashed just the stock 7.0 lg bootloader, now everything is working fine. Thanks for the message though!
jamesvmccann said:
I found a fix, I completely wiped everything and first flashed just the stock 7.0 lg bootloader, now everything is working fine. Thanks for the message though!
Click to expand...
Click to collapse
No problem ?
Same Problem
I have the exact same problem. I flashed the LineageOS ROM, then flashed Fulmics ROM, then tried to go back to Lineage—and now every ROM just reboots endlessly, but I can boot into recovery and access TWRP just fine.
It looks like jamesvmccann found a fix, by "completely wiped everything and [then] flash[ing] just the stock 7.0 lg bootloader." I'm afraid I don't know where to download the stock 7.0 lg bootloader. This is a h830, so that may matter as well.
Any additional help would be greatly appreciated.
Managed to fix this problem myself
The stock h830 bootloader was linked in this forum post.
I booted into TWRP and flashed the stock bootloader. It has a different bootflash.
H850 keeps booting into Recovery
Hello everyone, I have a H850 and my phone does not want to boot into the OS. It keeps booting into Recovery mode. I tried flashing only the H850 bootloader and then installing a ROM, and it doesn't work. I've formatted everything except the SD card and still no joy. What else can I do to restore my H850?
Please Help!
KCKitsune said:
Hello everyone, I have a H850 and my phone does not want to boot into the OS. It keeps booting into Recovery mode. I tried flashing only the H850 bootloader and then installing a ROM, and it doesn't work. I've formatted everything except the SD card and still no joy. What else can I do to restore my H850?
Please Help!
Click to expand...
Click to collapse
I had same problem factory reset few times within twrp seem to work after a while. I take it your backup not working? If all else fails flash kdz in lgup
Sent from my LGE LG-H830 using XDA Labs
well after somehow breaking the miui stock cam when enabling the camera2apk, and being unable to fix it by replacing build.prop, i decided to restore the backup i made in twrp earlier.
restored backup: sticks at MI logo.
tried several times, cleared caches, wiped etc etc.. will not boot after restore.
so i downloaded the stock global rom, and flashed it in twrp: sticks at MI logo. will not boot
downloaded Ressurection Remix rom, flashed that.. works fine. but i want stock or as near as possible for now.
downloaded developer miui rom, flashed that in twrp: stuck at MI logo. will not boot.
tried stock stable rom again... same story, will not boot.
downloaded Miflash, and recommended TGZ archive of ROM. followed instructions and extracted to a folder and browsed to folder with Miflash. hit "refresh"
get error "length cannot be less than zero"
tried using the "mi recovery" method (renaming rom to "update.zip" and power/vol_up)
but for whatever reason, there is no "install update" option even present.
as you can see im having a very frustrating evening. i only wanted to enable the damn google camera.
flash it by edl mode
Sent from my [device_name] using XDA-Developers Legacy app
is there a decent guide for that anywhere? from what ive seen it still requires miflash to be working? which it, frankly, just isnt. but then, nothing is! dont think ive ever had an evening where so many things which are supposed to work all give problems together.
i mean, i could understand if the custom rom was problematic, but its the only thing that *did* work.
404 Not found
well i managed to get a stock rom installed by downloading an older version of miflash... that didnt give any errors and installed the global rom fine.
i would love to know what could be causing all my problems though. seems everthing ive tried should work.
the one that is bugging me more than anything now is that whenever i enable the camera2api, the miui stock camera stops working ( crash on hdr, panorarama mode) and stays broken even if i remove mod.
this should not happen it seems, since there are guides for enabling this and adding the pro features to the camera from higher models.
nobody seems to have an opinion on it, which is very strange considering the number of people who must have done the camera2 mod...
robinlawrie said:
...nobody seems to have an opinion on it, which is very strange considering the number of people who must have done the camera2 mod...
Click to expand...
Click to collapse
I dropped miui long ago, so it is difficult to comment. However, the problem would probably be found in the settings (and/or the drivers in the system). Reinstalling a stock system image and wiping /data (and formatting it, if necessary) should solve the problem. This is, of course, a drastic step - but I would be very surprised if the problem persisted after such a step.
you have to flash lazy flasher after every MIUI stock rom flashing to be able to boot the rom...
google it "lazy flasher'
Hello everyone,
i got a Redmi Note 3 pro for a friend some while ago, since i dont wanted to stick to MIUI, i just flashed ResurrectionRemix since this was the most used costum rom back then.
My friend now suddenly has the problem that his phone just bootloops all the time. So i tried upgrade the rom to a newer version but it just keept bootlooping.
I also already tried formating the data partition as well as the storage but nothing helped so far. I even tried a few different roms but no difference there either.
But the weired thing is that i found an really old full backup (1.5 years old, only system and data) of the rom he used before and when i flash that, it just works fine.
I really dont wanna go back to that old and buggy rom so is there something else i could do to fix this problem?
Have you tried flashing a newer firmware? IIRC there's a thread that includes links to all the past and latest firmwares for kenzo.
TomTheDragon87 said:
Hello everyone,
i got a Redmi Note 3 pro for a friend some while ago, since i dont wanted to stick to MIUI, i just flashed ResurrectionRemix since this was the most used costum rom back then.
My friend now suddenly has the problem that his phone just bootloops all the time. So i tried upgrade the rom to a newer version but it just keept bootlooping.
I also already tried formating the data partition as well as the storage but nothing helped so far. I even tried a few different roms but no difference there either.
But the weired thing is that i found an really old full backup (1.5 years old, only system and data) of the rom he used before and when i flash that, it just works fine.
I really dont wanna go back to that old and buggy rom so is there something else i could do to fix this problem?
Click to expand...
Click to collapse
If u unofficially unlocked bootloader
Then U need latest miui rom bootloader. First update to latest miui 10 fastboot rom using pc. then unlock and install twrp .
Then ur custom roms will boot.
If u have unlocked ur bootloader officially using miunlock tool. then just flash latest firmware which includes emmc. This will directly update ur bootloader. Then u can flash custom roms.
Hello, i flashed twrp it was working after the first run, when i rebooted and installed the decrypt 4.0 (v18) (which can be found here https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-unlock-bootloader-custom-t3839405) the touch stopped working, so i proceeded to download the miui global v10.3.7.0 from the official site and flash it with MiFlash, it did work, the phone booted as before but the touch was still not working, so i booted into the recovery mode which was the default one again as i cleared the data and wiped the data but the touch screen stills not working, everything was working fine before flashing the twrp...
please, help is required, idk what to do anymore, and there is almost no xiaomi assistance near
---------
update: lol, i think i was a bit desesperated, to everyone that gets into the same situation, i went going back trying every single MIUI build... the one that worked was V10.2.3.0 - Global, everything is fine now, time to do everything again and get anxiety, sorry.
try twrp 3.3.1 unofficial from
https://forum.xda-developers.com/showpost.php?p=80122987&postcount=305
also then flash vendor image https://mirror.akhilnarang.me/MIUI/beryllium/ (9.6.27 is the popular)
flash LINAGE OS
flash DFE Treble https://drive.google.com/file/d/1As6z5v7NEIfOk67jXHBX34cbnFZdEjy9/view ,
later install magisk 19.4
now try one by one all three version of Twisted kernels ( the developer maintains 3 versions based on touch drivers (nvt)
https://forum.xda-developers.com/poco-f1/development/kernel-twisted-kernel-v4-0-beryllium-t3902838
i am hopful you will fix it
zyhpex said:
Hello, i flashed twrp it was working after the first run, when i rebooted and installed the decrypt 4.0 (v18) (which can be found here https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-unlock-bootloader-custom-t3839405) the touch stopped working, so i proceeded to download the miui global v10.3.7.0 from the official site and flash it with MiFlash, it did work, the phone booted as before but the touch was still not working, so i booted into the recovery mode which was the default one again as i cleared the data and wiped the data but the touch screen stills not working, everything was working fine before flashing the twrp...
please, help is required, idk what to do anymore, and there is almost no xiaomi assistance near
---------
update: lol, i think i was a bit desesperated, to everyone that gets into the same situation, i went going back trying every single MIUI build... the one that worked was V10.2.3.0 - Global, everything is fine now, time to do everything again and get anxiety, sorry.
Click to expand...
Click to collapse
Worked for me! Thanks!
zyhpex said:
Hello, i flashed twrp it was working after the first run, when i rebooted and installed the decrypt 4.0 (v18) (which can be found here https://forum.xda-developers.com/poco-f1/how-to/xiaomi-poco-f1-unlock-bootloader-custom-t3839405) the touch stopped working, so i proceeded to download the miui global v10.3.7.0 from the official site and flash it with MiFlash, it did work, the phone booted as before but the touch was still not working, so i booted into the recovery mode which was the default one again as i cleared the data and wiped the data but the touch screen stills not working, everything was working fine before flashing the twrp...
please, help is required, idk what to do anymore, and there is almost no xiaomi assistance near
---------
update: lol, i think i was a bit desesperated, to everyone that gets into the same situation, i went going back trying every single MIUI build... the one that worked was V10.2.3.0 - Global, everything is fine now, time to do everything again and get anxiety, sorry.
Click to expand...
Click to collapse
I had an experience as bad as yours. After flashing the last miui.eu, I went to boot and the phone does not leave the boot right away. I tried to enter TWRP and the touch just didn't work. I ended up flashing the official TWRP, also none of the touch works. I started getting desperate and settling for formatting for ROM stock and losing my 2 year old data, because I went to fastboot and flashed stock 11.0.8.0 and guess what? the touch didn't work, even in stock, I started to go crazy. So I had the stupid idea of putting the stock and blocking the bootloader, I ended up ****ting even more because even after the flash and blocking the bootloader the touch was dead. I was already giving up and thinking about paying someone as access to EDL mode to restore the phone. I ended up seeing your post and had the idea of plugging a mouse into the cell phone's type c input, and believe me the mouse cursor worked. Then I managed to unlock the bootloader again and flashed the stock that you recommended, and voiala the touch went back to work. I ended up going back to miui.eu and I'm ready for new flashes. It seems that we like to suffer LoL. I think this topic should be fixed at the top in case anyone else falls into this insane problem.
Reflash firmware n try ones.. only firmware
dorfohm2 said:
Worked for me! Thanks!
Click to expand...
Click to collapse
Im having the same issue.What should I do??My touch was working totally well before flashing TWRP.
solved by plugging in a mous in TWRP and navigating the UI to restore my "full" backup of all partitions! if you have done a backup! cheers and thanks for the idea of the mous! not expected it to work in TWRP though!!!