Hi, so i need some help regarding an issue i'm currently facing ( and have been facing for about a month now).
I'll give you the full story of my device and what i did:
First, when i got the phone. First thing i did was unlock bootloader and install custom recovery + rom (sultanXDA rom)
Then, when the android 7.1 ROMs started coming out, i installed one of those, worked great.
After a while i got bored, and decided to actually try the stock ROM, so i used a tool which took the phone back to 100% stock.
After this, i wanted to install a custom recovery so i could root and install xposed, i unlocked bootloader and tried installing THIS recovery.
It seems to install just fine via fastboot, but when try to go into the recovery, it tries to boot into it, then it just boots into the system instead. And after this, i have no recovery at all. I tried going back to stock again (which also got me the recovery back). But once again, when i try to install the recovery it doesnt work.
Anyone got any idea why this is?
Any help would be appreciated
Shpped said:
Hi, so i need some help regarding an issue i'm currently facing ( and have been facing for about a month now).
I'll give you the full story of my device and what i did:
First, when i got the phone. First thing i did was unlock bootloader and install custom recovery + rom (sultanXDA rom)
Then, when the android 7.1 ROMs started coming out, i installed one of those, worked great.
After a while i got bored, and decided to actually try the stock ROM, so i used a tool which took the phone back to 100% stock.
After this, i wanted to install a custom recovery so i could root and install xposed, i unlocked bootloader and tried installing THIS recovery.
It seems to install just fine via fastboot, but when try to go into the recovery, it tries to boot into it, then it just boots into the system instead. And after this, i have no recovery at all. I tried going back to stock again (which also got me the recovery back). But once again, when i try to install the recovery it doesnt work.
Anyone got any idea why this is?
Any help would be appreciated
Click to expand...
Click to collapse
That recovery is only for Oxygen OS 3.1.3 and ROMs based on it.
I take it you flashed Oxygen OS 2.x that's why it didn't boot.
Joshwin Aranha said:
That recovery is only for Oxygen OS 3.1.3 and ROMs based on it.
I take it you flashed Oxygen OS 2.x that's why it didn't boot.
Click to expand...
Click to collapse
Thanks for your reply
Unfortunately (see image below) i am on OOS 3.X
EDIT: sorry about the large image, i dont know how to make it smaller
{
"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"
}
Don't think anything wrong with that recovery but you could also try Sultans twrp or blu sparks V41 twrp.
Exodusche said:
Don't think anything wrong with that recovery but you could also try Sultans twrp or blu sparks V41 twrp.
Click to expand...
Click to collapse
I tried different Recoveries too, (i know i tried both Sultan and Blu Spark's Recoveries). I tried all i could find on Android Development page.
The issue does seem very weird, i dont know where i messed up in the process. It seems like when i try to install the new recovery, it does replace the old one but never boots.
Shpped said:
I tried different Recoveries too, (i know i tried both Sultan and Blu Spark's Recoveries). I tried all i could find on Android Development page.
The issue does seem very weird, i dont know where i messed up in the process. It seems like when i try to install the new recovery, it does replace the old one but never boots.
Click to expand...
Click to collapse
What recovery did you use to install 3.1.3? I think it has to be old stock recovery from 2.X.X or won't work. When I used the new stock recovery from 3.x.x had issues myself.
Exodusche said:
What recovery did you use to install 3.1.3? I think it has to be old stock recovery from 2.X.X or won't work. When I used the new stock recovery from 3.x.x had issues myself.
Click to expand...
Click to collapse
Thanks for your reply
I used the stock rom to install 3.1.3 from 2.x.x (don't remember exactly which version i was on). Anyways, the issue right now is the fact that i cannot install any custom recoveries.
Shpped said:
Thanks for your reply
I used the stock rom to install 3.1.3 from 2.x.x (don't remember exactly which version i was on). Anyways, the issue right now is the fact that i cannot install any custom recoveries.
Click to expand...
Click to collapse
What it tells after flashing in fastboot?
cva_kabil said:
What it tells after flashing in fastboot?
Click to expand...
Click to collapse
Hi, this is what it shows me on install. After installing when i try to go into the recovery it stays on the oneplus logo :/
Okay so this is weird.
After installing adb drivers on my work pc (im currently at work) and flashing, it for some reason works!
Thanks for all the help guys
For anyone facing the same issue: Try using a different pc with different adb and fastboot drivers, dont know why it worked for me, but it did!
Shpped said:
Okay so this is weird.
After installing adb drivers on my work pc (im currently at work) and flashing, it for some reason works!
Thanks for all the help guys
For anyone facing the same issue: Try using a different pc with different adb and fastboot drivers, dont know why it worked for me, but it did!
Click to expand...
Click to collapse
Glad it worked
Related
Hi all,
I purchased the Rom Manager, and flashed the new clockworkmod recovery, but like this I cannot acces my older nand backups.
I have a few, older backups, and maybe i will need them ! What can I do?
thx
legycsapo said:
Hi all,
I purchased the Rom Manager, and flashed the new clockworkmod recovery, but like this I cannot acces my older nand backups.
I have a few, older backups, and maybe i will need them ! What can I do?
thx
Click to expand...
Click to collapse
If you made your older backups with AmonRA recovery you won't be able to use them in CWM recovery. You will have to flash AmonRA to use them. That is pretty simple, thanks to ciaox who shared flashable recovery zips here.
borrow thread awhile,
just now i root my phone using gingerbreak 1.2
after root,then download rom manager free version from market
then i choose flash clockwork Mod recovery,and choose lg optimus one as my device
and wait it to load finish the bar
after finish,it shows this :
{
"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"
}
so now what should i do ??
XeactorZ said:
borrow thread awhile,
just now i root my phone using gingerbreak 1.2
after root,then download rom manager free version from market
then i choose flash clockwork Mod recovery,and choose lg optimus one as my device
and wait it to load finish the bar
after finish,it shows this :
so now what should i do ??
Click to expand...
Click to collapse
Are you sure you granted ROM Manager superuser privileges?
22VIN said:
Are you sure you granted ROM Manager superuser privileges?
Click to expand...
Click to collapse
just now don't have
so i root my phone again,and its work already
but after i flash clockworkMod recovery,and reboot into recovery
then i use the guide that u last time teach me at my thread
22VIN said:
1. root your phone
2. install a custom recovery (the easiest way is to install ROM Manager from Market and select "flash cwm recovery"
3. download a custom kernel (I'm using franco's) and copy it on your sdcard
4. boot into custom recovery: turn off your phone and then press vol down + home + power and release at lg logo
5. make a nand backup
6. wipe dalvik cache (in cwm recovery it's in advanced menu)
7. select install zip from sdcard, select your kernel from the sdcard and flash it.
8. start your phone and install setcpu; use max 729mhz
That's it
Click to expand...
Click to collapse
so after finish flash franco kernel
i choose reboot,then my phone stuck at LG logo
i wait very long,then unplug the battery and put it back
and turn on phone as usual,same also stuck at there
i do it a lot times
so i give up,and do a Nand restore,but its also stuck at LG logo ==
then the only way is i go emergency mode and use kdz updater to flash back
luckily my phone no problem
so now got other way to flash custom recovery instead using rom manager ??
because i google it quite a lot people also got the same case as me,stuck at LG logo after reboot ~
XeactorZ said:
so after finish flash franco kernel
i choose reboot,then my phone stuck at LG logo
i wait very long,then unplug the battery and put it back
and turn on phone as usual,same also stuck at there
i do it a lot times
so i give up,and do a Nand restore,but its also stuck at LG logo ==
then the only way is i go emergency mode and use kdz updater to flash back
luckily my phone no problem
so now got other way to flash custom recovery instead using rom manager ??
because i google it quite a lot people also got the same case as me,stuck at LG logo after reboot ~
Click to expand...
Click to collapse
Well I also got stuck at lg logo on some occasions when flashing kernels/themes, it happens. But I can't understand why you got stuck after restoring backup.
When did you make your backup? Did you make a backup before flashing stuff on your ROM?
And what do you mean by "got stuck"? Sometimes it takes longer to boot after you flash something. How much did you wait to consider that your phone is stuck?
To install a custom recovery the classic way check out step 3 here.
By the way, your problems aren't related to the recovery's installation. You're saying you rebooted into recovery, so the instalation of CWM with ROMmanager was succesful.
22VIN said:
Well I also got stuck at lg logo on some occasions when flashing kernels/themes, it happens. But I can't understand why you got stuck after restoring backup.
When did you make your backup? Did you make a backup before flashing stuff on your ROM?
And what do you mean by "got stuck"? Sometimes it takes longer to boot after you flash something. How much did you wait to consider that your phone is stuck?
To install a custom recovery the classic way check out step 3 here.
By the way, your problems aren't related to the recovery's installation. You're saying you rebooted into recovery, so the instalation of CWM with ROMmanager was succesful.
Click to expand...
Click to collapse
i also duno why after i restore from the nand backup that i do yesterday night still stuck at LG logo
the backup i make at yesterday night,which before flashing franco kernel
yes i got a backup before flashing franco kernel,and i no flash any ROM coz i wan use stock rom
erm,my phone stuck at LG logo more than 10minutes already,its too long than normal
i know sometime will take longer time,but sure won't over 10minute
so now i gonna try another method to flash custom recovery
thanks for ur link ~
After spending two whole days trying to flash my Galaxy S2 with MIUI 2.1.6 (also tried the latest Cyanogenmod and DarkyROM) and with nothing to show for it, it's time to ask for help.
My main goal is to install MIUI 2.1.6. The starting point is stock Gingerbread 2.3.5 (XXKI3). This is what I did:
- flashed stock 2.3.5 (XXKI3) via Odin
- rooted XXKI3 with CF-Root
- copied MIUI 2.1.6 on SD card (the zip file)
After that comes the part where I have to flash ClockworkMod Recovery and that's where the troubles start. My phone comes with 3e recovery which gives me the "failed to verify whole file signature" error after I try to flash CWM via the ROM Manager.
After browsing XDA forums, a lot of reading and trying both methods of overriding that bloody signature check (Untermensch's script method and Existenz's method of placing the Recovery file in /system/bin), none of them worked for me.
Untermensch's script method starts doing its thing but at one point it gives me an error message and suggests that my phone isn't rooted (which it definitely is, as I'm able to use Superuser, Root Explorer, AdBlock and every other root-only app).
Existenz's method of manually putting the Recovery file in /system/bin swaps the 3e recovery with CWM (orange letters, if I recall correctly), but after doing all the neccessary wipes and installing MIUI (or Cyanogenmod) from a zip file on my SD card, all I get is a boot loop. DarkyROM won't install at all, it simply gives me an error at the very beginning of the installation process.
At this moment I'm running stock Gingerbread 2.3.5, rooted by CF-Root and flashed with SpeedMod kernel. When I try to enter recovery, I'm getting CWM Recovery 5.0.2.3 (blue letters). However, if I try to wipe the phone and install MIUI from zip, all I get is another boot loop. And I'm back on 3e recovery.
Perhaps it's also worth mentioning my 3e recovery menu has no "reinstall packages" option which was mentioned in several threads on this forum that were vaguely related to my issue.
Anything I'm missing? Any ideas at all?
Thanks in advance and kind regards!
YouLaxy said:
My main goal is to install MIUI 2.1.6
Click to expand...
Click to collapse
Try the MIUI forums for support.
1) Flash CF-root
2) Copy the Miui zip into the sdcard
3) flash the Miui zip twice
4) reboot into CWM recovery
5) Flash the miui zip again
6) wipe cache/data
7) reboot into miui
oinkylicious said:
Try the MIUI forums for support.
Click to expand...
Click to collapse
The thing is, I'd ultimately like to be able to install any custom ROM, not just MIUI. So far none of them worked (MIUI, Cyanogenmod, DarkyROM), I'm guessing due to that nasty 3e recovery (nothing else comes to mind)
veyka said:
1) Flash CF-root
2) Copy the Miui zip into the sdcard
3) flash the Miui zip twice
4) reboot into CWM recovery
5) Flash the miui zip again
6) wipe cache/data
7) reboot into miui
Click to expand...
Click to collapse
I'll give that a go later today and post back the results. Cheers!
Nope, that didn't work. After flashing with MIUI twice via CWM and powering the phone off, I'm unable to enter recovery to flash MIUI for the third time, as the phone goes into boot loop.
Any other ideas, anyone? Thanks in advance!
Your not using rom manager are you?
Maybe its a bad miui download, where did you get the zip from?
Nope, I'm flashing the zip via CWM recovery, so after turning the phone off and doing the three-key thingy. I got the MIUI zip from MIUIAndroid.com and downloaded it three times, just to be sure there's not an issue with the zip.
YouLaxy said:
Nope, I'm flashing the zip via CWM recovery, so after turning the phone off and doing the three-key thingy. I got the MIUI zip from MIUIAndroid.com and downloaded it three times, just to be sure there's not an issue with the zip.
Click to expand...
Click to collapse
I have no clue then, it should work
Maybe you could try galnet miui?
Have you tried flashing other custom roms, eg hyperdroid or checkrom?
I did try to flash CyanogenMod (ended up with a boot loop, just like MIUI), as well as DarkyROM (got an error shorty after the start of the installation, can't remember what it was anymore). Seems my SGS2 simply isn't up for anything but stock ROMs. Bastard.
YouLaxy said:
I did try to flash CyanogenMod (ended up with a boot loop, just like MIUI), as well as DarkyROM (got an error shorty after the start of the installation, can't remember what it was anymore). Seems my SGS2 simply isn't up for anything but stock ROMs. Bastard.
Click to expand...
Click to collapse
CM7 does need doubleflashing, so when you go into CWM double flash the zip before wiping/rebooting.
And what was the error on the stock rom? Have you tried others.
Try this.
Its the resurrection edition of darkyrom. Its something to fall back on when other roms failI, it completely repartions your phone and should replace 3e with CWM and you'll have a nice darky custom rom
Make sure you follow the instruction to the letter
http://www.darkyrom.com/community/i...arkyrom-hd-v1-0-r5-resurrection-edition.6565/
veyka said:
CM7 does need doubleflashing, so when you go into CWM double flash the zip before wiping/rebooting.
And what was the error on the stock rom? Have you tried others.
Click to expand...
Click to collapse
Just tried to doubleflash CM7 and then do the wipe. Ended up in yet another boot loop (and unable to get into recovery). Then I restored the stock 2.3.5, rooted with CF-Root and tried to flash DarkyROM (via CWM recovery, of course). This is the message that it gives me:
{
"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"
}
So now I'm back on stock 2.3.5 once again. Blimey.
thteddieboii said:
Try this.
Its the resurrection edition of darkyrom. Its something to fall back on when other roms failI, it completely repartions your phone and should replace 3e with CWM and you'll have a nice darky custom rom
Make sure you follow the instruction to the letter
http://www.darkyrom.com/community/i...arkyrom-hd-v1-0-r5-resurrection-edition.6565/
Click to expand...
Click to collapse
I'll give it a go in a couple of minutes and post back with the results. Thanks for your input!
Wait you have an sgs 2? Well the darkyrom your trying to flash in your pic is for the galaxy one
This will seriously mess up your phone.. try the link.I posted should work
thteddieboii said:
Wait you have an sgs 2? Well the darkyrom your trying to flash in your pic is for the galaxy one
This will seriously mess up your phone.. try the link.I posted should work
Click to expand...
Click to collapse
Hahah, really? wow, hes lucky it didnt brick it, good old status 0 (oops should have noticed that, it means that the firmware isnt for this the phone you are trying to flash it on)
veyka said:
Hahah, really? wow, hes lucky it didnt brick it, good old status 0 (oops should have noticed that, it means that the firmware isnt for this the phone you are trying to flash it on)
Click to expand...
Click to collapse
Yeah I noticed cause it was darky 10.2.2 which I remember from my s1 days of flashing.. I was wondering why the 0 was there. Very lucky its not bricked
Let us.know how you go with the darkyrom HD resurrection.. darkyrom HD is for galaxy s 2 just in case you wanted to update in future and so you don't get confused
Feeling like a bit of a dumbass right about now. And just when I thought I tripple checked everything... Okay, that explains the DarkyROM issue, however still no clue what's wrong with MIUI and/or CM7. I'm sure I downloaded correct versions of those
I'm downloading the ROM from your link at this very moment, trying it shortly.
YouLaxy said:
Feeling like a bit of a dumbass right about now. And just when I thought I tripple checked everything... Okay, that explains the DarkyROM issue, however still no clue what's wrong with MIUI and/or CM7. I'm sure I downloaded correct versions of those
I'm downloading the ROM from your link at this very moment, trying it shortly.
Click to expand...
Click to collapse
All good. Its not hard to get mixed up. I remember how overwhelming it was when I first started learning to flash
Bit scary for a while til I learnt more and understood things better
Hmm I'm not to sure about the miui issue or cm7
Never used them, except for cm9 cause I like the aosp ICS..
Let us know how darkyrom HD goes for ya
Well, that worked. Had to flash twice to get it to work, though (got stuck on step #14 for 10 scary minutes and then just turned the phone off an reflashed)
I'll give DarkyROM a go. I do have one more question though. If I decide to try to flash MIUI once again, would it be enough to boot into CWM recovery and try to install it from zip (so, without doing anything to my DarkyROM installation) or do I have to go back to stock ROM for that?
Thanks a ton for your help guys, my SGS2 can run custom ROMs after all! Horray!
So I've successfully rooted my phone (S6 Edge G925F) using CF-Auto-Root and I've been using it for the past few days. Looking to install a custom ROM, but I can't get TWRP to work without getting "recovery is not seandroid enforcing". If I try to use it through the app, I get a bootloop. If I do it with SkipSoft Android Toolkit, it boots fine but I can't get into the recovery menu. Same error as above.
I feel like I'm missing something really simple here... But I can't quite put my finger on it. I feel like it has something to do with unlocking the bootloader, but I can't seem to find any guides on it. The one I did find had a dead link to a download, and 20+ minutes of searching for a replacement left me with nothing.
Losing my mind here...
ProdigyThirteen said:
So I've successfully rooted my phone (S6 Edge G925F) using CF-Auto-Root and I've been using it for the past few days. Looking to install a custom ROM, but I can't get TWRP to work without getting "recovery is not seandroid enforcing". If I try to use it through the app, I get a bootloop. If I do it with SkipSoft Android Toolkit, it boots fine but I can't get into the recovery menu. Same error as above.
I feel like I'm missing something really simple here... But I can't quite put my finger on it. I feel like it has something to do with unlocking the bootloader, but I can't seem to find any guides on it. The one I did find had a dead link to a download, and 20+ minutes of searching for a replacement left me with nothing.
Losing my mind here...
Click to expand...
Click to collapse
The "recovery is not seandroid enforcing" message can be just ignored.
There are 2 easy ways to get twrp to work.
Flash twrp through odin in AP.
https://dl.twrp.me/zerolte/
You need the .img.tar
Or
Download flashify
https://play.google.com/store/apps/details?id=com.cgollner.flashify
From flashify it gives you the option to download and flash twrp directly from the app.
callumbr1 said:
The "recovery is not seandroid enforcing" message can be just ignored.
Click to expand...
Click to collapse
Can't exactly ignore it, it's all I get when booting into the recovery menu after installing twrp.
ProdigyThirteen said:
Can't exactly ignore it, it's all I get when booting into the recovery menu after installing twrp.
Click to expand...
Click to collapse
Can the phone boot up?
Can you boot to recovery?
Flash a permissive kernel and the message will dissapear.. You can flash custom roms from flashify or flash fire also
callumbr1 said:
Can the phone boot up?
Can you boot to recovery?
Flash a permissive kernel and the message will dissapear.. You can flash custom roms from flashify or flash fire also
Click to expand...
Click to collapse
It boots into android, but not the recovery menu.
If I install through the twrp app, it won't even boot to android, it just gets stuck in a bootloop
ProdigyThirteen said:
It boots into android, but not the recovery menu.
If I install through the twrp app, it won't even boot to android, it just gets stuck in a bootloop
Click to expand...
Click to collapse
Try to install twrp through flashify!
callumbr1 said:
Try to install twrp through flashify!
Click to expand...
Click to collapse
I am, but I'm getting some error while trying to download it
{
"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"
}
ProdigyThirteen said:
I am, but I'm getting some error while trying to download it
Click to expand...
Click to collapse
What error?
callumbr1 said:
What error?
Click to expand...
Click to collapse
Added screenshot
I get the error on WiFi and 4g
ProdigyThirteen said:
Added screenshot
I get the error on WiFi and 4g
Click to expand...
Click to collapse
I cant see the screen shot? I would suggest start from scratch. Do a full wipe/ stock flash.
Flash twrp first then cf auto root.
Aaaand now I feel like a complete moron. Went to unroot my phone through SuperSU, it finished doing its thing, I rebooted my phone, and now I'm stuck in a bootloop. Every damn link I find to a stock ROM has a pathetic download speed, so I'm now having to wait 6 hours for something that may or may not work. Beginning to regret rooting my phone.
ProdigyThirteen said:
Aaaand now I feel like a complete moron. Went to unroot my phone through SuperSU, it finished doing its thing, I rebooted my phone, and now I'm stuck in a bootloop. Every damn link I find to a stock ROM has a pathetic download speed, so I'm now having to wait 6 hours for something that may or may not work. Beginning to regret rooting my phone.
Click to expand...
Click to collapse
Aslong as you have the correct stock firmware it should work. And if it works save the firmware somewhere safe. Then if you ever mess up again just needs a re flash.
Flashed stock ROM, phone working again. Tried to flash TWRP, but still getting recovery is not seandroid enforcing and nothing else.
ProdigyThirteen said:
Flashed stock ROM, phone working again. Tried to flash TWRP, but still getting recovery is not seandroid enforcing and nothing else.
Click to expand...
Click to collapse
Try to root first, then flash twrp. My note 4 did the same the other day after flashing stock ROM mm update. So I did full wipe, flashed cf auto root then twrp. Works fine
Hello, so I unlocked the bootloader and I installed a rom but when I want to configure it, the phone restarted and only lasts 10 seconds on and restarts back.
This problem happens with every android I want to install.
It isn't a hardware problem because I buy it few days ago
Agustinmds said:
Hello, so I unlocked the bootloader and I installed a rom but when I want to configure it, the phone restarted and only lasts 10 seconds on and restarts back.
This problem happens with every android I want to install.
It isn't a hardware problem because I buy it few days ago
Click to expand...
Click to collapse
Please give a detailed explanation, as of what you did, and what custom rom you flashes. Did tou flash the firmware ?
MyNameIsRage said:
Please give a detailed explanation, as of what you did, and what custom rom you flashes. Did tou flash the firmware ?
Click to expand...
Click to collapse
The phone went into bootloop because I was trying to install miui 9 with the "dualboot patcher" program and the phone did not start any operating system, I made a wipe and wanted to install another rom, but when I tried to install it, problems with bootloop started .
I tried with everything and I can not make it work, it's infinite bootloop, when I install the stock rom through miflash it installs successfully but when I start it restarts while loading android about two / three times and then loads android and after about ten seconds of having loaded it restarts and that's how it is always
Yes,I flash Miui, Resurrection Remix, Nitrogen Os, Lineage Os (13, 14.5), Paranoid Android, Slim and a few more, and I've tried many firmwares but nothing, I can not get it out of the bootloop.
Help pls
Agustinmds said:
The phone went into bootloop because I was trying to install miui 9 with the "dualboot patcher" program and the phone did not start any operating system, I made a wipe and wanted to install another rom, but when I tried to install it, problems with bootloop started .
I tried with everything and I can not make it work, it's infinite bootloop, when I install the stock rom through miflash it installs successfully but when I start it restarts while loading android about two / three times and then loads android and after about ten seconds of having loaded it restarts and that's how it is always
Yes,I flash Miui, Resurrection Remix, Nitrogen Os, Lineage Os (13, 14.5), Paranoid Android, Slim and a few more, and I've tried many firmwares but nothing, I can not get it out of the bootloop.
Help pls
Click to expand...
Click to collapse
I guess the problem is with the partitions which dual boot makes, please ask this on the official dual boot patcher thread, you will get a better answer there.
Agustinmds said:
The phone went into bootloop because I was trying to install miui 9 with the "dualboot patcher" program and the phone did not start any operating system, I made a wipe and wanted to install another rom, but when I tried to install it, problems with bootloop started .
I tried with everything and I can not make it work, it's infinite bootloop, when I install the stock rom through miflash it installs successfully but when I start it restarts while loading android about two / three times and then loads android and after about ten seconds of having loaded it restarts and that's how it is always
Yes,I flash Miui, Resurrection Remix, Nitrogen Os, Lineage Os (13, 14.5), Paranoid Android, Slim and a few more, and I've tried many firmwares but nothing, I can not get it out of the bootloop.
Help pls
Click to expand...
Click to collapse
Having some experience from dual booting with my previous device, I guess somehow you messed up your kernel and partitions. I would suggest to make a fresh start, meaning that you flash twrp recovery, boot into recovery and make a factory reset, and then flash a kernel image according to the rom that you want to install, then install the rom and try boot again. If you flash original miui rom make sure you flash lazyflasher or rom will not boot.
akisg said:
Having some experience from dual booting with my previous device, I guess somehow you messed up your kernel and partitions. I would suggest to make a fresh start, meaning that you flash twrp recovery, boot into recovery and make a factory reset, and then flash a kernel image according to the rom that you want to install, then install the rom and try boot again. If you flash original miui rom make sure you flash lazyflasher or rom will not boot.
Click to expand...
Click to collapse
Oh ok, i'll try it but I don't think this is going to work..
anyway thanks
No, it didn't worked, there are the logs, I don't know how to 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"
}
Agustinmds said:
No, it didn't worked, there are the logs, I don't know how to do
Click to expand...
Click to collapse
I can't see any error in the above screenshots. Is your device still not booting?
Try this: extract boot.img from rr rom and flash it through twrp by selecting install -> image -> boot.img -> and select boot
This should flash rr kernel in case your kernel is messed up and so rom can't boot. Reflash rom and see if that works.
akisg said:
I can't see any error in the above screenshots. Is your device still not booting?
Try this: extract boot.img from rr rom and flash it through twrp by selecting install -> image -> boot.img -> and select boot
This should flash rr kernel in case your kernel is messed up and so rom can't boot. Reflash rom and see if that works.
Click to expand...
Click to collapse
So I have to flash boot img and then flash the zip with the rom?
Agustinmds said:
So I have to flash boot img and then flash the zip with the rom?
Click to expand...
Click to collapse
Yes, try that in order to restore your rom's kernel and then flash rom as normal. Be sure to flash boot.img as "boot" and not recovery after selecting image
Damn it didn't work
I'm going to take a video with the error
Agustinmds said:
Damn it didn't work
I'm going to take a video with the error
Click to expand...
Click to collapse
You get an error while flashing or your device just can't boot?
Also, have you tried flashing any official miui rom?
akisg said:
You get an error while flashing or your device just can't boot?
Also, have you tried flashing any official miui rom?
Click to expand...
Click to collapse
I don't get any error, just when I turn on the phone it enters in an infinite bootloop.
Yes, I've tried with a lot of official roms and the same result.
https://www.youtube.com/watch?v=0xU4ABxlAyE
Agustinmds said:
I don't get any error, just when I turn on the phone it enters in an infinite bootloop.
Yes, I've tried with a lot of official roms and the same result.
https://www.youtube.com/watch?v=https://www.youtube.com/watch?v=0xU4ABxlAyE
Click to expand...
Click to collapse
have you tried flashing lazyflasher after flashing rom before rebooting?
akisg said:
have you tried flashing lazyflasher after flashing rom before rebooting?
Click to expand...
Click to collapse
Yes, but it does not work, I do not know what else to do, should I send it to a technical service or is there still hope?
Agustinmds said:
Yes, but it does not work, I do not know what else to do, should I send it to a technical service or is there still hope?
Click to expand...
Click to collapse
I just saw the video you uploaded. If this happens with any kernel/rom combination then i think your device might be faulty. Have you tried another kernel? Does the same happen with stock kernel and rom? Have you tried flashing stock rom from pc with mi flash tool?
Sent from my Redmi Note 4 using Tapatalk
akisg said:
I just saw the video you uploaded. If this happens with any kernel/rom combination then i think your device might be faulty. Have you tried another kernel? Does the same happen with stock kernel and rom? Have you tried flashing stock rom from pc with mi flash tool?
Sent from my Redmi Note 4 using Tapatalk
Click to expand...
Click to collapse
I tried everything and it's the same, I don't think that the phone is faulty because I bought it a few days ago and it worked well.
Agustinmds said:
I tried everything and it's the same, I don't think that the phone is faulty because I bought it a few days ago and it worked well.
Click to expand...
Click to collapse
Well maybe you should try another kernel compatible with this rom or another rom/kernel combination. Also, flashing baseband firmware might also help.
How I do that?
When I bought the tablet from the alixpress seller it had a shady version of MoKee on it and given I in general don't like Mokee very much I decided to reflash to other roms, but none of them had auto-rotate.
I've tried MoKee (flashing my own file), LineageOS, and am now running Carbon.
I'm wondering if I'm the only one with the problem - and if not, if anyone was able to figure out how to fix it?
Using the "Sensor Test" app it's as if there is no accelerometer/gyroscope within the device at all (No Input Data).
Software wise I'm at:
TWRP & CarbonROM (from here)
{
"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've reinstalled the MIUI China rom using the XiaomiFlashUtility, and that gave me back auto-rotate.
I've since installed XiaomiEU's TWRP & "Globalized" Rom, and auto-rotate persists.
I'm gonna try and install a custom AOSP/LOS -based rom now and see if that solved the issue, or if it's ROM-related.
Edit: After installing Carbon's TWRP (for treble support, it was the only 3.2.3 TWRP for Clover I could find) & LineageOS 16.0 ROM, auto-rotate is gone, and my bet's on the rom. I guess I'll go "back" to XiaomiEU's MIUI10, but it would be cool to know whether or now I'm the only one with the weird issue and whether or not there's a fix coming.
The only custom I tested is AICP-mordiford and I do not have a problem with auto-rotate .
^^
great rom, using it myself also, not a single problem
https://cloud.akane.blue/nextcloud/s/PbGugWPefp9fFNZ?path=/clover
Hi.
I'm in the same situation. The mi pad 4 worked flawless on the stockrom. With lineageos 15.1 and 16 it won't auto-rotate. I found no solution yet.
I just installed the Unofficial LineageOS 16.0. Auto rotate is turned off by default, but once I turned it on it worked as it did with the stock ROM.
Tomek0000 said:
The only custom I tested is AICP-mordiford and I do not have a problem with auto-rotate .
Click to expand...
Click to collapse
Update.
The autorotate stops too work after some time (long time). I using my automagic script/widget for this ocasion.
banesi said:
^^
great rom, using it myself also, not a single problem
Click to expand...
Click to collapse
----
Is its UI beautiful?Can I flash it directly with TWRP?
---------- Post added at 06:37 PM ---------- Previous post was at 06:30 PM ----------
Hello, may I have any questions about MoKee? Some people say that it is very stable, I want to know what are the disadvantages? Because I am trying to flash.
I tried flashing the china developer and stable stock roms via fastboot with 'clean all' and the problem of auto rotation persists. when I hold my tablet portrait the screen turns landscape, is there maybe a setting in the build.prop I can change to fix this?
Please help
yakie996 said:
I tried flashing the china developer and stable stock roms via fastboot with 'clean all' and the problem of auto rotation persists. when I hold my tablet portrait the screen turns landscape, is there maybe a setting in the build.prop I can change to fix this?
Click to expand...
Click to collapse
I have the same problem. Did you find a solution?
This problem I observed only in android 8 based custom roms . From the moment I tested some android 9 , I never had this problem .
Do not clear or format the Persistence folder
Do not clear or format the Persistence folder or you will lose - tada - autorotation. Plus you risk losing your IMEI.
If you have done this already then re-flash a stock ROM, confirm all is well, then put your ROM of choice back and in the process when using TWRP leave the persistence folder alone.
GregEden said:
Do not clear or format the Persistence folder or you will lose - tada - autorotation. Plus you risk losing your IMEI.
If you have done this already then re-flash a stock ROM, confirm all is well, then put your ROM of choice back and in the process when using TWRP leave the persistence folder alone.
Click to expand...
Click to collapse
Thanks for solution
Thanks for solution
Click to expand...
Click to collapse
Hi, did the solution work for you? I have the same problem, just reinstalled the official eu ROM, where auto rotate is working. Then back to a custom ROM, without deleting the "vendor" files ( I think that is what it is called on newer TWRP) an the auto rotating does not work.
I had a problem with autorotation, power off display during call, ... And all sensors. The subdirectory sensors disapered from persistant partition. When I restored persistant partition from backup all work again .
Install app to test sensors and check if it works.
The test app does not show any sensors unfortunately. I do not have a backup though, where can I get the files from?
You can unpack persistent partition file from the last official stock image. I am not sure if it is in the recovery version, but maybe only in fastboot version.
Extracting stock Boot, Recovery and Persist images
Talking here about how to extract the stock Boot, Recovery and Persist images, needed in case of e.g. bootloop upon flashing Magisk or TWRP, to reflash the stock image(s). Also, boot image is needed for patching from Magisk Manager (and flashing...
forum.xda-developers.com
If you will have it , install it.
Else you will can install full stock and repeat all steps.
Thanks for your answer. I can't find the persist.img for MI Pad 4 though, any idea where I could get it from? Instead I tried flashing an official ROM again, verified the rotation is working and then made a backup of the Persist partition in TWRP. Then I installed the Pixel Plus Rom again and restored persist from backup, but again the sensors are not working. Any idea what I made wrong? Or where can I get the persist.img from?
nalpo said:
Thanks for your answer. I can't find the persist.img for MI Pad 4 though, any idea where I could get it from? Instead I tried flashing an official ROM again, verified the rotation is working and then made a backup of the Persist partition in TWRP. Then I installed the Pixel Plus Rom again and restored persist from backup, but again the sensors are not working. Any idea what I made wrong? Or where can I get the persist.img from?
Click to expand...
Click to collapse
You should not need to restore the /persistence partition - just do not format it. It has had a name change in Android 11 i think it is now in Vendor. So do not clear or format /Vendor. Someone else can verify that. I am using the March release of Lineage with NikGapps and have no issues. Newer versions of Lineage have had many issues.
GregEden said:
You should not need to restore the /persistence partition - just do not format it. It has had a name change in Android 11 i think it is now in Vendor. So do not clear or format /Vendor. Someone else can verify that. I am using the March release of Lineage with NikGapps and have no issues. Newer versions of Lineage have had many issues.
Click to expand...
Click to collapse
Well that was interesting... So after your mention of LOS I installed the current version from xda after wiping Dalvrik/Cache/Data and System). Rotation now worked! But in LOS, my external DAC does not work so I tried isntalling Pixel Plus again, wiping the same stuff as before and now it suddenly worked! Strange why it didn't after installing the official ROM. Nevertheless it works now, thanks a lot