after installing r2x2 recovery, it is impossible to read the memory partition, after reading it, it is impossible to run the magisk file to Root the device. And when trying to reboot the device, the device gets bricked and falls into the boot loop. ..please help me
Related
Hi everyone. I was trying to root my phone and install the philz_touch, I successfully did that and the booting finished the first time, then I flashed the philz_touch.tar file as well, then the recovery mode worked as well with the philz_touch UI etc. Then I wiped clean my data from the recovery mode so that I could install a new rom (cm-12.1-20150423-NIGHTLY-trltetmo), when I tried, the install game me an error (This package is for device: trltetmo; this device is trlte), and since then, the phone is stuck on the boot loop, any ideas how I can resolve this?
I have unlocked bootloader, flash modified boot.img and recovery but when I boot the device I get 'Your device is corrupt and may not work properly' I then get stuck on the google boot screen. When I go into TWRP recovery it cannot mount anything so I cannot even perform a factory reset.
Please help
did you make a back up?
I didn't unfortunately, I can get into recovery and as long as I leave it as 'Read-Only' it seems to mount everything. I think I need to get a stock image.
Resolved - used a Toolkit to go completely back to stock, kind of scared to try again now.
Follow directions and that won't happen again. Make sure you are on the correct version MDB08K BEFORE you start (you have the OTA), format not wipe in TWRP and you won't get caught in the boot loop.
Failing to do those two things will put you in a boot loop.
What toolkit did you use because i myself have this issue with my nexus 6p
Swatto86 said:
I have unlocked bootloader, flash modified boot.img and recovery but when I boot the device I get 'Your device is corrupt and may not work properly' I then get stuck on the google boot screen. When I go into TWRP recovery it cannot mount anything so I cannot even perform a factory reset.
Please help
Click to expand...
Click to collapse
That warning is normal, and should be ignored if you want unlocked bootloader, custom ROMs, etc.
Here TWRP couldn't mount because you forgot to decrypt after flashing the modified boot.img.
If you have further issues, let me know.
A quick advise - Avoid toolkits. They are handy and easy, but if something goes wrong, it will be hard to track down the cause. On the contrary, doing thing manually, will not only make it easy, but will also help you learn more about your Android, and how it works.
Hello,
First to get this out of the way i have searched the topic and there were several "solutions" none worked for me.
How it started, I downloaded the latest LieneageOS update as always, set the phone to do it's thing, came back and the phone was stucked on OP log, tried a little reboot, nothing.
No access to recovery or fastboot.
computer wouldn't recognize device even after installing drivers, this guide helped me a little https://forums.oneplus.com/threads/...ck-guide-for-a-hard-bricked-oneplus-2.347607/
found tools got fastboot back and original recovery.
via fastboot attempted to installed TWRP
fastboot flash recovery twrp****.img
and then tried to boot into recovery
fastboot boot twrp****.img
Not able to boot into twrp
after all that my phone still stucked on the boot OP logo
any help would be greatly appreciated.
Anyone has any idea, sorry I have been scouring and reading everywhere, but I can't find a solution.
Thank you
So i have been trying many things and finally getting somewhere. I apologize for the long post, but i have been trying so many things to get this device back to speed.
So flashing TWRP newer version for some reason is not letting me boot into recovery.
I have flashed twrp-2.8.7.0 and i am able to boot into recovery, however when trying to install the ROM (LineageOS 16) i get error E3004.
Searching the web i find that the correction is to that error is to update TWRP, thus i have tried flashing
twrp-3.2.1-0 and twrp-3.1.1-0 and once installed i am not able to boot into recovery again.
I flashed 2.8.7.0 and i was able to get in, thus from inside TWRP i did an image install of twrp-3.1.1-0 and rebooted, recovery won't load. I proceeded to repeat this until i get a result.
I flashed twrp-3.0.2-0 and be able to boot. However still not able to install LOS.
Once i tried flashing twrp-3.0.2-1, recovery won't load.
For sake of argument i flashed twrp-3.0.2-0 and attempted a image install for twrp-3.0.2-1, but the system still won't boot to recovery.
I have completely formatted the phone.
I hope someone could give me a little advice . Thank you.
Hi, I'm trying to root my Samsung j3 phone, and i cant figure out how to do it. it seems quite simple, but i cant get it to boot twrp. Ive copied the twrp image to the recovery partition using Hemidall and then held power+volume-up+home to boot into recovery mode but the phone just boots into the normal recovery mode. Ive never rooted a phone before so i don't know what really to do.
Dont let it boot into the system, the system overwrites the recovery. Make sure as soon as its done flashing twrp, you restart instantly into the recovery. I'd recommend turning off auto reboot.
Hello guys,
I broke my Suez - I need some help.
I went through all the pain of opening up and unbricking it with amonet-suez-v1.1.2.zip from https://forum.xda-developers.com/t/unlock-root-twrp-unbrick-fire-hd-10-2017-suez.3913639/.
Then I was in TWRP, I think 3.2.sth.
I tried to adb sideload the latest lineage for my device from this thread: https://forum.xda-developers.com/t/rom-testing-suez-lineage-16-0-05-july-2022.4232785/
The installation finished with a red error message like /data partition not found.
I restarted the tablet, which is now stuck in a lineage os bootloop.
I thought the problem might be not having the most recent TWRP. So I brought the tablet into hacked-fastboot, and flashed TWRP 3.6.1.2, from https://forum.xda-developers.com/t/rom-testing-suez-lineage-16-0-05-july-2022.4232785/, which succeeded.
Not I can not even access my recovery anymore. When I try to with volume and pwr, the screen stays black and the tablet resets, ending in the TWRP bootloop.
A) why is the lineage in a bootloop
B) What about the /data partition missing error
C) How to get my TWRP to work again?
I can redo the unbricking stuff, but I would lang in the exact same situation. Where should I try different stuff?
I could think of replacing the old TWRP of amonet-suez with the most recent version, and then do the unbrick procedure with shorting again.
Push. I need help.