Well, it's not so bad.
Yesterday I bought this phone and applied the October update. Then I flashed TWRP by @mohancm (I wasn't sure about that but I did it anyway). And then I flashed Magisk. But because I couldn't get Xposed to work, I tried to remove Magisk (unsuccessfully it seems) and flash SuperSU. I played around by switching from slot B to A. I am not sure exactly what I did.
The end result is that the phone won't boot when I turn it on. (I think I might still have TWRP installed, but I am not sure.) I tried flashing stock boot.img via fastboot, but I get get an error (I think it's something to do with the partition table). I can't flash using MiFlash because it says I don't have the permission. (I've had bad experiences with MiFlash before.)
However, I am able to boot the phone manually. When I boot to bootloader I can just boot stock boot.img (flashing doesn't work like I said), and then the system boots properly and I'm rooted.
Any ideas what I can do now to fix the issue. I just need to try to avoid random reboots and I can use my phone just fine, but is there a way to fix it? Should I just wait for the November update? Any hope of getting a ROM that I can flash using TWRP?
Edit: I'm dumb. Of course you can flash an image via TWRP. I flashed the stock image via TWRP and now the phone boots properly. Problem solved.
Hey everyone I just flashed the stock ROM on my device and just after that I got the update, when I clicked onto update my device just got moved to TWRP and didn't flashed the update too and finally the main issue is that my device just stuck in the TWRP. When I turn on my device It directly loads to the TWRP, I need to go to bootloader menu and then hit start to turn on my device.
Could anyone tell me how to solve this issue??
Sanjay parsi said:
Hey everyone I just flashed the stock ROM on my device and just after that I got the update, when I clicked onto update my device just got moved to TWRP and didn't flashed the update too and finally the main issue is that my device just stuck in the TWRP. When I turn on my device It directly loads to the TWRP, I need to go to bootloader menu and then hit start to turn on my device.
Could anyone tell me how to solve this issue??
Click to expand...
Click to collapse
Can't auto process 'stock' OTA updates with custom recovery. Must use stock recovery plus meet several other prerequisites that are difficult to satisfy on a rooted/modded device. Best option is to restore the nandroid you made before updating. What, no backup?? Reinstall stock image and hope for the best.
Hi,
as the title says, my phone is not booting anymore, after I transplanted the motherboard from a frame with a broken screen into a new frame (from china).
Abbreviations used:
RR => Resurrection Remix 5.8.5
CWM => ClockWorkMod Recovery 6.0.4.6-kitkat
TWRP => TeamWinRecoveryProject 3.2.1-1
I was using RR from the Rock Stable Setup on it before and it worked beautifully.
What happened:
I performed the mainboard-transplantation according to the iFixit guide
I held the power button to boot the phone:
It vibrated
It showed this screen for a couple of seconds
It vibrated
Back to step 1
And that until I removed power.
Then I tried to boot into recovery mode by holding the key combination on boot:
Same as above, but with this bootscreen
Then I tried to boot into download mode by holding the key combination on boot:
The warning to confirm download mode poped up and I got to see this screen.
I connected it to my PC and opened odin 3.09 and it recognized the device.
I tried to get adb and fastboot to see the device, but nothing worked. (In the old frame and before I broke the screen, it would be recognized at this stage)
I flashed TWRP with odin, odin showed the green "PASS!", but booting to recovery still failed.
I proceeded to flash a stock ROM, which had worked when I had issues with RR.
It worked, I went through the Android 5 setup process, enabled debug and connected adb.
adb saw the phone.
I rebooted to recovery and stock recovery booted correctly.
Sideloading anything with adb failed due to signature verification.
I then went back to download mode and flashed CWM successfully.
It now boots into recovery, but whenever I try to flash anything with CWM, it fails showing this screen
Or something similar (the photo comes from flashing RR 5.8.5)
I have both linux and windows properly setup and used both with adb, fastboot and odin (only windows)/heimdal (only linux).
I checked drivers and usb cables.
I opened the phone back up and checked all connections.
But I can't get any version of RR, CyanogenMod or LineageOS on there.
I've searched the internet, but people that have these kinds of problems after replacing parts of their phones, seem to only have driver issues or skipped steps in the manuals of custom ROM installations.
If you have any idea on what I could try or what I'm doing wrong or not doing, please leave an answer.
I'll keep this post updated below here:
(no updates, yet)
Thanks so much in advance
Simon
Your picture shows stock recovery not CWM .
Try flashing TWRP recovery through Odin .
I did flash TWRP and afterwards there was no recovery anymore.
When I flash CWM, I get the recovery shown in the photo.
The stock recovery has a black background and no touch controls for me.
What you saw must have been CWM.
Update: I can flash twrp-2.8.7.0-hlte-4.4.img.tar and it works. It's the only image that works, but I still can't boot into or flash any custom OS.
The only working OS I have at the moment is a stock android 5.0, which is not all that useful...
If anyone has an idea, why I can't or how I can find out what is causing it, please say so.
I can flash twrp-2.8.7.0-hlte-4.4.img.tar and it works. It's the only image that works, but I still can't boot into or flash any custom OS. )
What do you mean by ANY ??
Well, exactly that.
Regardless of what zip I flash, I end up with a bootloop.
If I flash a recovery zip, the recovery bootloops, but the OS still boots.
If I flash a custom ROM, I can still boot into recovery fine, but booting normally results in a bootloop.
The only way to get software onto my phone has been via odin and only an old CWM, Philz Touch, TWRP (Version 2.8.7.0 and below) and STOCK Android (Versions 4.3, 4.4.2, 5).
Anything else I have tried so far did not result in an error, but I couldn't boot into it either.
If you have ideas for software I can try flashing, please tell. I really have no idea how to get the damn thing to work again...
What happens when you flash correct stock rom via Odin ??
I mean that I can boot into it after flashing it via Odin.
But its terribly slow and bloated compared to ROMs like ResurectionRemix, so I don't want to use it.
AnyTimeTraveler said:
I mean that I can boot into it after flashing it via Odin.
But its terribly slow and bloated compared to ROMs like ResurectionRemix, so I don't want to use it.
Click to expand...
Click to collapse
In that case phone is OK .
Usual is that user is failing to follow instructions .
Not sure what you mean by fastboot on a N9005 .sounds like not a N9005 .
Personally with TWRP 2.8.70 i would be flashing something like .
https://forum.xda-developers.com/galaxy-note-3/development/rom-magma-nx-rom-t3508672
as its correct TWRP .
I am able to follow instructions.
Thank you very much.
I followed exactly the same procedure that has worked many times when switching between custom ROMs.
Also, the phone has a perfectly working version of Ressurection Remix installed at the time my frame broke and it did get stuck in the same bootloop after replacing the frame, even thogh the software was exactly the same.
I am looking for help analyzing the boot process and some way of capturing the kernel log when booting to determine where the error occures that traps the phone in a bootloop.
AnyTimeTraveler said:
I am able to follow instructions.
Thank you very much.
I followed exactly the same procedure that has worked many times when switching between custom ROMs.
Also, the phone has a perfectly working version of Ressurection Remix installed at the time my frame broke and it did get stuck in the same bootloop after replacing the frame, even thogh the software was exactly the same.
I am looking for help analyzing the boot process and some way of capturing the kernel log when booting to determine where the error occures that traps the phone in a bootloop.
Click to expand...
Click to collapse
Dear Mate..
Have you solved your problem? I have same problem after transplating N900 frame.
Sorry, I gave up, since I dearly needed a working phone and bought a OnePlus 3 cheaply from ebay second hand. It's been working like a charm and I threw the note into my museum after I softbricked it for the n-th time and couldn't get it out of a bootloop that didn't leave me time to go into Fastboot.
Sorry friend, but I can't help with this.
after reading a lot of similar threads, seems like the hardware is the cause of us not able to update to higher versions of twrp(& custom roms)
It's been a while since I unlocked my mobile's bootloader, following the steps of a you tube video specifically from the Tecnocat channel. Everything was going well until I thought I did not have any system because whenever I started it it went straight to recovery. Install roms and the same. Until I decided to go directly to the bootloader and start it from there. Of surprise it worked, there was no problem with the system. Everything works fine, but every time I turn off the phone and turn it on it starts in recovery and I have to boot it in fasboot mode and from there start the system. It's tedious, and for example I can not do restarts. I already reprimand the recovery from different sources, and I can not find a solution. Please help
Similar issue
I'm having a similar issue except mine started after mistakenly installing a OTA update (Sept. I think) on a xt1687. Rooted (magisk) with TWRP recovery on stock ROM. Every time I boot it goes into recovery mode, and the only way to get into the phone is through TWRP Reboot > Bootloader, then Start.
I tried flashing the latest stock ROM I could find, but still have the same issue. Only now I'm getting nagged with Install System Update New Version NPNS25.137-93-18. I know better now to follow the OTA update guides, but how do I get the phone back to the way it was before the update? Any help is greatly appreciated. Thanks in advance!
"Can't load android system. Your data may be corrupt." Urgent help required please.
My phone was running smoothly until I decided to disable Chrome app on android. System froze and rebooted to the above message.
Running Android 9.0 March Security Patch Stock Root tissot.
I downloaded the stock boot image, booted twrp and flashed it. Everything passed but I am still getting the error!
Any help would be highly appreciated! Will reply A.S.A.P.
Thank you!
What about flashing stock rom with miflash or edl mode?
The only solution is to reflash the stock rom nothing else
Flashing January stock rom via fastboot with miflash worked.
Would anyone hazard a guess as to why this happened? Is chrome an app that should not be disabled since its perhaps integrated in system function?
Boot to fastboot, get a twrp recovery compatible with A1, boot that recovery, in twrp go to reboot, change slot .
If you`re on A then reboot to B.
Then reboot to system.
x3malex said:
Flashing January stock rom via fastboot with miflash worked.
Would anyone hazard a guess as to why this happened? Is chrome an app that should not be disabled since its perhaps integrated in system function?
Click to expand...
Click to collapse
If I remember correctly, the stock ROM uses Chrome as the default WebView implementation (instead of Android System WebView). So, disabling it may cause issues.