People, I do not know what I did here at the time of installing a custom ROM and ended up giving a problem that says: patching system image unconditionally and now it happens with every ROM that I install (even those that worked before). I already installed ROM Stock but nothing works!
it's perfectly normal, chill
Related
I noticed that when using the last dev preview for my N7 2013, it keeps killing TWRP and putting back the stock recovery. Now the final release does this. If I flash TWRP again, it just gets overwritten after a normal boot then back to recovery.
Why? Is there a way to stop this? This is the first time I've dealt with this. Nothing else does this to me. I haven't found a clear answer yet to this while searching this site or others.
I solved this by flashing a custom kernel, in my case, ElementalX 3.02.
I downloaded the zip to the tablet, rebooted to fastboot, wrote the recovery, then booted into the recovery (just after flashing it, don't boot system), flashed custom kernel, and upon booting system it stopped overwriting the recovery partition with stock recovery.
It seems the stock kernel overwrites the recovery partition if it has been modified. Correct me if I'm wrong!
rguilamo said:
I solved this by flashing a custom kernel, in my case, ElementalX 3.02.
I downloaded the zip to the tablet, rebooted to fastboot, wrote the recovery, then booted into the recovery (just after flashing it, don't boot system), flashed custom kernel, and upon booting system it stopped overwriting the recovery partition with stock recovery.
It seems the stock kernel overwrites the recovery partition if it has been modified. Correct me if I'm wrong!
Click to expand...
Click to collapse
Well it is just 5.0 that does this.
Since I posted this there is a sane reason for them to do this - it might be the way they enforce the factory reset protection. It has to use their recovery to do so. Still annoying.
But thanks for a workaround, that it simply is the kernel, or boot image. That and I want root
You can try Chainfire's CF-AutoRoot, It modifies Boot.img so root is granted in boot time, I already had a custom kernel when I rooted, but you can try to root first and see if it stops auto-writing the stock recovery.
Here's the download link: http://download.chainfire.eu/347/CF-Root/CF-Auto-Root/CF-Auto-Root-flo-razor-nexus7.zip
Extract it, and run root-windows.bat (or the one suitable to your OS) while in fastboot.
Hello,
it looks like that I'm unable to install a custom rom on my GX8 (see details out device at the end of the post).
FRP disabled, bootloader unlocked (this is at least what the fastboot/bootloader screen is saying)
I'm able to flash twrp-3.1.1-0-rio.img to recovery
I can use twrp on recovery and it seems to be fully functional
When I use twrp in 'read-only' mode, I'm able to reboot the system (stock firmware)
But when I use twrp in modifing mode, booting the system (stock firmware) is no longer possible (even if I only wipe cache and/or dalvik). Restarting the device will always end in twrp/recovery.
Backup is possible. Restore backup succeeds, but booting the system (stock firmware) is not possible. Restarting the device will always end in twrp/recovery.
Nevertheless trying to install a custom rom from zip in twrp. This leads to the following error message:
"E3004: This package is for device: RIO-L01, hwRIO-L01, RIO-L02, hwRIO-L02, RIO-L03, hwRIO-L03, RIO-AL00, hwRiO-AL00, RIO-CL00, hwRIO-CL00, RIO-TL00, hwRIO-TL00; this device is rio.
Updater process ended with ERROR: 7"
Well, patch the custom rom in lines of http://www.lineageosdownloads.com/fix-error-7-lineage-os/, i.e. modifing the 'updater-script' in the zip. Now installing the custom rom zip in twrp is possible. Still unable to reboot system.
Installing gapps and/or chainfire supersu does not improve the situation.
Giving up back to stock rom in lines of https://forum.xda-developers.com/gx...tall-stock-rom-g8-t3370013/page2#post73008458 . This has (so far) worked for me to get back a working mobile phone.
Any suggestions, anyone?
Kind regards,
aanno
PS:
device:
Prod
HUAWEI RIO-L01
Serial
MUYDU16122xxxxxx
IMEI
867115027xxxxxx
Prod Id
2983xxxx
Unlock
9725092227xxxxxx
stock firmware used:
EMUI 4.0
Build
RIO-L01C432B340
Android
6.0.1
Kernel
3.10.49-g06216b3
Custom
CUSTC432D001
I've encountered the same exact problem when I flashed using twrp-3.1.1-0-rio.img. Had to force update to stock rom after it got stuck on bootloop.
Solved it when using the older TWRP 3.0.2-0 which you can get here:
https://forum.xda-developers.com/gx8/development/huawei-g8-gx8-t3324538
Hope it might help you too.
So i originally had a p2c...blabla
Ota updated to p2a4 or something like that. sf244 ROW
unlocked oem (waited 14days)
flashed twrp.
factory resetted+format system. + data partition is ext4
rom flashed successfully
gapps starts flashing but keeps stuck after just 1% of flashing.. always.
or twrp keeps freezing.
Does anyone have a solution?
Right now i'm back to Stock Rom+Magisk 13.3 .
sm00th4f3 said:
So i originally had a p2c...blabla
Ota updated to p2a4 or something like that. sf244 ROW
unlocked oem (waited 14days)
flashed twrp.
factory resetted+format system. + data partition is ext4
rom flashed successfully
gapps starts flashing but keeps stuck after just 1% of flashing.. always.
or twrp keeps freezing.
Does anyone have a solution?
Right now i'm back to Stock Rom+Magisk 13.3 .
Click to expand...
Click to collapse
If you have backup then Install your stock rom and its every components such as boot, recovery etc....
Or download the fastboot files from the p2 thread and flash it.
Then properly install twrp.
How can i properly install twrp?.. I mean, i think i always installed in correctly...otherwise magisk wouldn't work., right?. Because it does. I need your help. I even got Safetynet Pass and Root Apps like Root Explorer is working Fine.
Only the Flashing of Custom Roms etc fails for me... It's weird.
Okey. I just redid it like 5 Times. And i got a bit farther.. new boot animation shows up. But still blue led after it stops.
I FINALLY found the SolutioN!!! I used this https://androidfilehost.com/?fid=817550096634780916 and did the upgrades per ota. Then adb'd my twrp on my phone. And changed data to ext4. Rebooted. Activated usb debugging again. flashed twrp again(just to be sure), booted into twrp. Formatted system,data,cache,dalvik and then flashed my roms. SUCCESS <3
Hello guys.
I'm having trouble here with a friend's device.
the device simply reboots the twrp.
I already realized the flash of several rons, I also tried with the stock.
installs everything correctly, but at the time of doing the reenicialization in the system returns to twrp again.
I have already tested several versions of twrp and also did not succeed.
Has anyone ever had this problem? I'm finding it very strange, because I've been with rom for a long time and I've never had any problems like this.
What do you think it could be? and how can I resolve and re-restart correctly again?
Thank you in advance.
You flashed the stock ROM and you still have TWRP? Then something is wrong. Usually when that happens you did something wrong. So this is a good thing you are stuck in TWRP. Usually a factory reset will make it boot again. You can pull data off from TWRP before doing this (like pictures and such).
What exactly have you tried to flash (order too), and what version of TWRP are you using. The factory ROM may not have worked as well if you tried to flash the latest, without having the treble partition setup, or did not have a version of TWRP that keeps the vendor partition mounted.
We really need a few more details on what you tried to help.
If you just want to get it booting, I would try wiping everything in BluSpark's TWRP, and flash 5.1.5 OOS.
Hello, the names Braadliiah,
I am having excessive difficulty figuring out how to flash any Rom that is beyond Kitkat, even though they, supposedly are "designed" for an "SM-T217s". As I had success flashing Cyanogen mod[cm-12.1-20160706-UNOFFICIAL-lt02ltespr], which is not even for my model of tablet, which is bizarre due to the fact that other ROM's of the same model do not successfully flash. The most recent custom Rom I had attempted to install with no avail, was the Ressurection Remix[[ROM][8.1.0]ResurrectionRemix v6.2.1[Official]]. This ROM was linked into google, under "SM-T217s" compatibility, but for the model "It02ltespr".
The way that I flash these ROM's are through TWRP, namely, version "2.7.0.0". The TWRP dialogue within the flash window, usually says something like, "failed to zip" and "Zip error". The reason I have not done the flashing via ADB & Fastboot is because I have not done this successfully yet, and truth be told, I am not sure it is even possible given the TWRP can't do it? Also, I do not use Odin, because this will remove TWRP, and there is no guaranty that the ROM will work, and then, I will have to re-install Stock Firmware and TWRP. I lack any desire doing double the work, as I have already done a bit of that through trial and error recently.
So is there any method, via TWRP, ADB, or ODIN, which will in fact work? Should I install another version of say, Cyanogenmod, to be able to install this ROM? I am looking for experienced, tech savvy people, as I am a curious noob, who wants a ressurected tablet that can do all modern conveniences via wifi, and be my study tab. Furthermore, I would like, say, Magisk Manager to Install Modules, but can not do so, without a newer Kernel, that is Lolipop and forward. And again, Lolipop and forward do not seem to Install.
I shall be ever greatful for anybody's help. Thank you. :angel:
Update:
Today I experimented with ODIN some more. I had a small victory, because I happened to take the TWRP v.3.1 flash Image, and converted him into a TAR file, and luckily ODIN managed to successfully install this update. However, when it came to TWRP v.3.2, there became an error installing. TWRP still failed to instal zip files from the below ROMs. Furthermore, ODIN seemed to flash the boot images of Custom ROMs well, when converted to TAR files. Yet, when I booted the ROM, this device remained on the Boot screen.
My process by which I installed these ROMs, went like so:
First, extract zip, then convert to TAR via 7zip
Open ODIN, flash TAR in PDA, Boot down android
Boot to Download Mode again, in PDA flash TWRP v3.1 TAR, Boot down android
Boot to Custom recovery, and install proper Gapps
Boot on, and Stuck.
I did this three times, while starting off with a full wipe, to rule some things out. When I tried to fix context, it said Error1
The Roms I attempted to flash were, Cyanogenmod 12, which worked entirely; Cyanogenmod 13 which was stuck on Boot screen, tried twice; Lineage OS 15, which I tried three times, and was stuck on Boot screen.
Do I need to apply more than one file? for instance, CSC, Phone, and PDA? Because I was only flashing boot Image as a TAR file in PDA.