Related
right ima cut to the chase
i used to use cyanogen mod 10 but wanted a official rom from sam mobile so i flashed via odin and cocked up my note 2 n7100
now i can get into recovery and download mode and i have flashed the same cm10 via tw recovery and it hangs on boot animation
i then wiped and flashed via recovery SSHD rom and it also hangs at boot animation so what do you guys think is wrong?
i need this fixed it cost way too much to just thow in the junk draw espcially since i cant work anymore.
thanks
-FatBoyNate
When you change your rom you need to wipe data from recovery.
FatBoyNate said:
right ima cut to the chase
i used to use cyanogen mod 10 but wanted a official rom from sam mobile so i flashed via odin and cocked up my note 2 n7100
now i can get into recovery and download mode and i have flashed the same cm10 via tw recovery and it hangs on boot animation
i then wiped and flashed via recovery SSHD rom and it also hangs at boot animation so what do you guys think is wrong?
i need this fixed it cost way too much to just thow in the junk draw espcially since i cant work anymore.
thanks
-FatBoyNate
Click to expand...
Click to collapse
Always flash custom rom through custom recoverys only (not from stock rom). Flash TWRP or CWR or Philz recovery first and then flash custom rom.
After flashing custom rom or stock rom, first wipe data and cache (as above said) before rebooting.
sent from my GT-N7100. Press thanks if I helped..
MBariya said:
Always flash custom rom through custom recoverys only (not from stock rom). Flash TWRP or CWR or Philz recovery first and then flash custom rom.
After flashing custom rom or stock rom, first wipe data and cache (as above said) before rebooting.
sent from my GT-N7100. Press thanks if I helped..
Click to expand...
Click to collapse
i have flashed a custom rom through a custom recovery, i've been flashing custom roms since the htc himalaya and never had a booting problem.
i think i snuffed the bootloader can anyone give a me a stock nandroid?
OR
guide me as how to get past the 2nd boot logo, i also flashed a core 2 kernel and that's when i think the damage was done, if it will fix this, where can i get the stock kernel?
[EDIT] atm it has SSHD ROM and The SSHD Kernel i get the samsung n7100 logo and then the boot animation but then it gets stuck.
FatBoyNate said:
i have flashed a custom rom through a custom recovery, i've been flashing custom roms since the htc himalaya and never had a booting problem.
i think i snuffed the bootloader can anyone give a me a stock nandroid?
OR
guide me as how to get past the 2nd boot logo, i also flashed a core 2 kernel and that's when i think the damage was done, if it will fix this, where can i get the stock kernel?
[EDIT] atm it has SSHD ROM and The SSHD Kernel i get the samsung n7100 logo and then the boot animation but then it gets stuck.
Click to expand...
Click to collapse
same has happened to me.
FatBoyNate said:
i have flashed a custom rom through a custom recovery, i've been flashing custom roms since the htc himalaya and never had a booting problem.
i think i snuffed the bootloader can anyone give a me a stock nandroid?
OR
guide me as how to get past the 2nd boot logo, i also flashed a core 2 kernel and that's when i think the damage was done, if it will fix this, where can i get the stock kernel?
[EDIT] atm it has SSHD ROM and The SSHD Kernel i get the samsung n7100 logo and then the boot animation but then it gets stuck.
Click to expand...
Click to collapse
ItzMar said:
same has happened to me.
Click to expand...
Click to collapse
get into recovery flash this file http://d-h.st/fWr u will loose evrything from internal memory, now after it reboot to recovery just flash your rom but dont reboot after installation.
first click fix permission
then wipe cache and dalvik atleast twice
then reboot!
it should load the rom fine, and i would suggest to stay with philz recovery and create a backup of efs and rom both the terminal way and through recovery too
shhbz said:
get into recovery flash this file http://d-h.st/fWr u will loose evrything from internal memory, now after it reboot to recovery just flash your rom but dont reboot after installation.
first click fix permission
then wipe cache and dalvik atleast twice
then reboot!
it should load the rom fine, and i would suggest to stay with philz recovery and create a backup of efs and rom both the terminal way and through recovery too
Click to expand...
Click to collapse
once i flashed it i gete:error opening 'data/dontpanic'
e:error I/O error
it didnt reboot. do i click reboot system after flashing your file?
ItzMar said:
once i flashed it i gete:error opening 'data/dontpanic'
e:error I/O error
it didnt reboot. do i click reboot system after flashing your file?
Click to expand...
Click to collapse
I hope u are rooted and have a custom recovery installed if yes then its a script to clean wipe the rom to start a fresh install better known as dirty flash so when u flash the zip it will wipe ur cache, dalvik, system on recover and will automatically reboot to recovery then u can proceed wth any custom rom u want the latest philz recovery is recommended.i am using my phn yo reply and already 4am morning here so be sure what you are doing , give complete info of ur phn status as wht u hv done till now if u have all as mentioned abv then u r good to go and flash, but in ur case the flash of the file was not successful so u can manually wipe all mentined above and procced as instructed.
Its an instruction for custom rom and recovery if u have stock then just wipe cache and dalvik and try booting up.
Off to sleep
If you are unsure of what u r doing then try to get hands on odin and flash stock rom ,as messing up to much may damage ur pit partition
shhbz said:
I hope u are rooted and have a custom recovery installed if yes then its a script to clean wipe the rom to start a fresh install better known as dirty flash so when u flash the zip it will wipe ur cache, dalvik, system on recover and will automatically reboot to recovery then u can proceed wth any custom rom u want the latest philz recovery is recommended.i am using my phn yo reply and already 4am morning here so be sure what you are doing , give complete info of ur phn status as wht u hv done till now if u have all as mentioned abv then u r good to go and flash, but in ur case the flash of the file was not successful so u can manually wipe all mentined above and procced as instructed.
Its an instruction for custom rom and recovery if u have stock then just wipe cache and dalvik and try booting up.
Off to sleep
If you are unsure of what u r doing then try to get hands on odin and flash stock rom ,as messing up to much may damage ur pit partition
Click to expand...
Click to collapse
:angel:Saviour!:angel:
Thank you so much. All is well now. :highfive:
Step to expose what happens to me:
after brick my oneplus 3 by flash a wrong zip I got back to the stock rom, but when I try to install twrp only stays 1 time. When I reboot the system and try again to enter TWRP it appears the stock recovery of oneplus. Any idea why this happens and how to fix it?
BlackDeath XVI said:
Step to expose what happens to me:
after brick my oneplus 3 by flash a wrong zip I got back to the stock rom, but when I try to install twrp only stays 1 time. When I reboot the system and try again to enter TWRP it appears the stock recovery of oneplus. Any idea why this happens and how to fix it?
Click to expand...
Click to collapse
Flash the recovery by adb. This should make it stick.
zelendel said:
Flash the recovery by adb. This should make it stick.
Click to expand...
Click to collapse
I flash it with adb 3 times and still stock when i reboot the phone
BlackDeath XVI said:
I flash it with adb 3 times and still stock when i reboot the phone
Click to expand...
Click to collapse
Immediately after flashing TWRP, without booting, flash SuperSu or Magisk and then boot to system.
tnsmani said:
Immediately after flashing TWRP, without booting, flash SuperSu or Magisk and then boot to system.
Click to expand...
Click to collapse
What is the diference for do twrp permanently installing magisk?? Ty very much for you help
BlackDeath XVI said:
What is the diference for do twrp permanently installing magisk?? Ty very much for you help
Click to expand...
Click to collapse
Your question is not very clear. If you are asking how TWRP stays permanent if Magisk is flashed, I think that since Magisk modifies the boot image, it prevents the ROM from overwriting TWRP with stock recovery.
tnsmani said:
Your question is not very clear. If you are asking how TWRP stays permanent if Magisk is flashed, I think that since Magisk modifies the boot image, it prevents the ROM from overwriting TWRP with stock recovery.
Click to expand...
Click to collapse
ty yes that my question jajaja
Is there any way to install twrp recovery and keep receiving OTAs on stock Pie ROM?
saedkebbeh said:
Is there any way to install twrp recovery and keep receiving OTAs on stock Pie ROM?
Click to expand...
Click to collapse
No.
marstonpear said:
No.
Click to expand...
Click to collapse
How to install OTAs after installing twrp?
You need to flash stock boot.img, as TWRP gets installed to the boot.img on your phone. But you need to do it on the right partition otherwise you won't get the updates. Also if you've tampered with system or any other partition of the device, you need to remove them. To get rid of all the steps, just flash the stock rom via MiFlash (you'll lose your data so take a backup).
marstonpear said:
You need to flash stock boot.img, as TWRP gets installed to the boot.img on your phone. But you need to do it on the right partition otherwise you won't get the updates. Also if you've tampered with system or any other partition of the device, you need to remove them. To get rid of all the steps, just flash the stock rom via MiFlash (you'll lose your data so take a backup).
Click to expand...
Click to collapse
You don't neccesary lose your data with MiFlash, just choose the option without relock/wipe.
thorin0815 said:
You don't neccesary lose your data with MiFlash, just choose the option without relock/wipe.
Click to expand...
Click to collapse
Don't forget to flash the same version!
marstonpear said:
Don't forget to flash the same version!
Click to expand...
Click to collapse
I need to know where to flash the twrp and where to flash stock boot.img when installing OTA
Yesterday I flashed patched boot img using the command: fastboot flash boot patched boot img, without choosing a partition
I made a guide for doing OTA with TWRP and Magisk. You should be able to follow it and just ignore the Magisk bits. The start covers restoring the boot partition.
https://forum.xda-developers.com/mi-a2-lite/how-to/10-0-4-0-to-10-0-7-0-ota-keeping-magisk-t3916863/
Note that I normally get a boot loop after installing TWRP and reinstall magisk as a fix. I'll assume you have your own way to install TWRP.
Hi there, i have problem with my pixel 2 xl, the first time i try to UBL it was successfully, and then i try to flash twrp, it successfully too, but i make a mistake here, i try to flash a custom rom but its not a custom rom file, but twrp.zip file and i flash it , and then i wipe the system, data, and i reboot to revocery but now getting freeze at the twrp screen, i cant connected to adb anymore, please help me, im sorry if i have a bad grammar
[email protected] said:
Hi there, i have problem with my pixel 2 xl, the first time i try to UBL it was successfully, and then i try to flash twrp, it successfully too, but i make a mistake here, i try to flash a custom rom but its not a custom rom file, but twrp.zip file and i flash it , and then i wipe the system, data, and i reboot to revocery but now getting freeze at the twrp screen, i cant connected to adb anymore, please help me, im sorry if i have a bad grammar
Click to expand...
Click to collapse
Can you get into fastboot mode? If so, does your pc recognize your device? And just a funny FYI...
UBL = Usama Bin Ladden
Badger50 said:
Can you get into fastboot mode? If so, does your pc recognize your device? And just a funny FYI...
UBL = Usama Bin Ladden
Click to expand...
Click to collapse
im stuk at Colt OS recovery, try to side load stock rom i get error signature verification failed, i try flash colt os rom and another custom rom but it stuck again at recovery, pls help me , any solution?
Hello
I have big problem.
After patching img over Magisk and flash this new patched img, can not start system / boot loop to POCO logo, or boot loop to MIUI logo - here system starting, but every restart and boot loop
Help please
Thanks
Hi!
Which boot-img did you patch and where did it come from?
How did you flash it?
So:
I received an update 12.5.8.0.RKHEUXM
After the update, I always have to root the phone again.
So I took boot.img from the original 12.5.8.0.RKHEUXM and patched it via Magisk.
I flashed the patched boot.img via ADB.
Well, after the restart, my phone will boot only after the MIUI logo and a bit of a melody, and the phone will restart again. This restart is performed about 4 times and remains/stops in fastboot mode,or it will return to TWRP after clearing dalvik and cache and restarting.
He does what he wants
I've had a problem with that before, but it was enough to delete Dalvik and the cache via temporary TWRP.
Then the system booted up normally, but now it doesn't work even after deleting Dalvik and the cache.
Here is a link to the thread where I solved it. Nobody actually advised me there, I just tried to clear dalvik and cache via TWRP and it was after the problem. Unfortunately, now the problem persists.
Poco F3 - Boot Loop to POCO logo / Please help
Hello. I have a big problem after updating the firmware. Poco F3 root over magisk. After updating from 12.5.6.0 RKHEUXM, I updated to 12.5.7.0 RKHEUXM. After the restart, both the phone and the system booted up. I patched the original boot.img...
forum.xda-developers.com
Thats what I did also with 12.5.8.0.RKHEUXM and everything is working fine.
Updated to 12.5.8.0 via the MIUI updater, but downloading the full rom, as the updater told me that the incremental update (~58MB) wouldn't work.
Then downloaded the the recovery file here: https://xiaomifirmwareupdater.com/miui/alioth/stable/V12.5.8.0.RKHEUXM/
Unzipped it and extracted the boot.img with payload-dumper-go on my Mac: https://github.com/ssut/payload-dumper-go
Patched the boot.img with Magisk on the phone.
Copied the patched_boot.img file back to the Mac.
Flashed the patched_boot.img from the mac with fastboot to both partitions:
Code:
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
Friend, I did exactly what you were writing, and unfortunately my system won't start
The only thing I did differently was to download the big rom 6gb update so I didn't have to extract boot.img. I didn't have to use a payload dumper.
Any other solution?
But I don't want to lose data and applications!
Did you try wiping data partition?
takichiman said:
Did you try wiping data partition?
Click to expand...
Click to collapse
Where should I do it?
But I don't want to lose data and applications!!!!!
I have bootloop to MIUI logo 4times - 5times and then stop in fastboot mode , It stops in fastboot mode and after pressing and holding the power button, the mobile starts only in fastboot mode, it no longer starts booting to the MIUI log
You can do it from recovery.
If you have twrp recovery you can backup your data before wiping.
But I'd only recommend backuping pictures(files) not the apps which you can reinstall.
takichiman said:
You can do it from recovery.
If you have twrp recovery you can backup your data before wiping.
But I'd only recommend backuping pictures(files) not the apps which you can reinstall.
Click to expand...
Click to collapse
You didn't give me much advice, my friend
I don't want to lose any data, or applications, pictures, just anything.
If it went after deleting the dalvik / cache last time, then why shouldn't it go now?
The system boots only to the miui logo, then the boot loop.
I don't understand why this is so.
And can't you somehow refresh the whole rom without losing data, applications and files?
Boot temp recovery, backup boot, patch backed boot and flash patched boot ... Just rename the boot backed image of twrp in boot.img, patch and flash ...
Try reflashing the official boot.img, you won't have root but at least you will be able to boot your phone. Also if you have TWRP why aren't just rooting your phone with the Magisk.zip instead of patching the boot.img yourself ?
Dark-Yox said:
Try reflashing the official boot.img, you won't have root but at least you will be able to boot your phone. Also if you have TWRP why aren't just rooting your phone with the Magisk.zip instead of patching the boot.img yourself ?
Click to expand...
Click to collapse
I tryed flashing official boot image, but still dont work.
Reboot back to recovery or booting only to miui logo and bootloop
Do you have module in magisk? Remove them ...
Frequently Asked Questions
The Magic Mask for Android
topjohnwu.github.io
snx413 said:
Do you have module in magisk? Remove them ...
Frequently Asked Questions
The Magic Mask for Android
topjohnwu.github.io
Click to expand...
Click to collapse
Yes, I have modules in Magisk.
How do I remove modules in Magisk if I don't get into the system — I don't boot
jkmaxfli said:
Yes, I have modules in Magisk.
How do I remove modules in Magisk if I don't get into the system — I don't boot
Click to expand...
Click to collapse
When you boot, you have access normally
snx413 said:
When you boot, you have access normally
Click to expand...
Click to collapse
And how do I remove them? instructions please
jkmaxfli said:
Yes, I have modules in Magisk.
How do I remove modules in Magisk if I don't get into the system — I don't boot
Click to expand...
Click to collapse
You can remove them in TWRP
jkmaxfli said:
I tryed flashing official boot image, but still dont work.
Reboot back to recovery or booting only to miui logo and bootloop
Click to expand...
Click to collapse
Dirty flash the whole ROM then
Adb shell
then
magisk --remove-modules
Dark-Yox said:
You can remove them in TWRP
Dirty flash the whole ROM then
Click to expand...
Click to collapse
How it dirty flash ?
I used it over TWRP recovery ROM zip file, and not work flashing