Hi! I have a problem installing GSI... I always get a bootloop and I don't know how to make it work... I tried so many things and, if you succeded I would like to receive a backup file of the partitions: Vendor, Boot, and System.
P.S: English isn't my first language so there could be grammatical errors..
Related
Hi people,
I hope I'm in the correct thread. On my SGS II (i9100) I managed to install the TWRP 3.0.2.1 (latest version i found in this forum).
So I can boot to Upload mode and Recovery without any problems.
For the installation i wiped "dalvik", "cache", "system" and "data".
For repartioning I used Heimdall-Suite and set the system to 1GB, data to 6GB and Preload to 512MB. (Was using CM12.1 previously with 1GB-system, 6GB-data and only 45MB preload)
Then started the install of the latest nightly build as of 2016-10-29.
After that I installed OpenGapps 6.0 pico also as of 2016-10-29.
After the installation i checked the contents with the linux-terminal within TWRP (great feature).
At the end I rebooted the phone.
The white Sasmung logo and text appears. Then the blue CyanogenMod logo appears and the white circle behind it keeps pulsating (boot animation)
But the phone is stuck in this situation. It never finished booting. Due to the fact, that i have no logs during this process (maybe this can be archived somehow?) I don't know where to start searching for the problem.
Thats the point where I think you can give me a hint.
In other threads I read about clearing dalvik again solved some problems. Other took out the battery for at least 5 mins.
Of course I tried all of this, and to install an other kernel (kernel-Lanchon-20160406-cm-13.0-i9100) which is IsoRec capable. Tried another nightly of CM13. But nothing helped me. The phone still is not booting.
Previously I have had CM12.1 on the device. There I only got the system to boot with Kernel_Dorimanx-V11.0b006-[16-07]-[28-07]-LP-SGII-GSSTUDIOS-TRIM-signed. All others also stuck in the boot animation loop.
Maybe this is a hint to my problem, unfortunatelly I don't know.
I really will appreciate your help in this situation.
Thanks in advance
CptAmerica
BTW.lease don't bother me for my english I'm from Austria and not used to write in english. But i hope i can point out my problem.
Solution for this Problem
Hi @ll,
due to the fact that I also posted this problem in the CM13.1 development thread I got good advises and the final solution for solving this problem.
Because I think other people might also have this problem I'd like to post the procedure how to solve the hanging boot loop issue.
Prerequisite:
For my luck I had a running Download Mode and a Running Recovery Mode
TWRP 3.0.2.1 installed on the phone.
Additional Information:
I was running CM12.1 on my phone with the kernel: Kernel_Dorimanx-V11.0b006-[16-07]-[28-07]-LP-SGII-GSSTUDIOS-TRIM-signed
This was the only kernel who managed to boot my phone with CM12.1. Maybe at this stage I already had my issue with the phone but the kernel bypassed it somehow.
Because also under CM12.1 no other kernel managed to boot the phone.
Procedure which caused the problem:
Due to the fact, the phone only bootet with the DorimanX Kerlen i thought why not updating to CM13.1 and get rid of the boot problem.
First I downloaded TWRP 3.0.2.1 and CM13.1 to the /sdcard01 partition.
I bootet in the DorimanX Recovery which was based on the CMR.
Whith this help I installed the new TWRP 3.0.2.1 which worked fine.
Rebooted to TWRP 3.0.2.1 and wiped /system, /data, /dalvik-cache /cache.
After that installed CM13.1 and OpenGapps Pico for Marshmellow.
Rebooted the device and here we are-> Hanging in the boot animation
I thought due to the fact that I used a partioning with only 43MB for the preload area once I installed CM12.1 this might kepping CM13.1 from booting.
Procedure which solved the problem:
After reading and trying a lot on the phone @the.gangster posted me a help to solve the problem.
I started a repartioning with the Heimdall-Suite with I9100_1GB-System_6GB-Data_512MB-Preload.pit which worked fine (I was thinking)
Then re-installed CM13.1 and again got stuck in the boot animation.
With the info from @the.gangster he told me, that most of the people which repartioning their device forgett to reformat the preload partition which keeps Android from booting.
So i started into TWRP 3.0.2.1 and selected "Advance"->"Terminal" which is a really cool feature, because you are in a full linux-terminal on your phone.
The preload partition is /dev/block/mmcblk0p12 (aka /dev/block/platform/dw_mmc/by-name/HIDDEN)
I fired of the following command:
Code:
mke2fs -t ext4 /dev/block/mmcblk0p12
which advices the phone to set up the ext4 filesystem on the given path, which later is mounted by the OS as preload area.
After that back to the main screen and then Reboot->System.
Now my phone took about 8-10 Minutes to start and I was back in Android with CyanogenMod 13.1 and a working phone!! :laugh::good::laugh:
I hope this might help you out there, if you have the same problem.
If you like to read the original thread this is the links: http://forum.xda-developers.com/galaxy-s2/development-derivatives/rom-cyanogenmod-13-t3223808/page629
Thanks for the hint as i gave up cm13 for Dirty Unicorns (which is great btw) for the same reason.
I repartitioned ny phone and get rid of the preload partition as I thought I didn't need it on cm13.
Now i know that first i need it and also need to reformat it...
But why?
Sent from my GT-I9100 using Tapatalk
Namoi said:
Thanks for the hint as i gave up cm13 for Dirty Unicorns (which is great btw) for the same reason.
I repartitioned ny phone and get rid of the preload partition as I thought I didn't need it on cm13.
Now i know that first i need it and also need to reformat it...
But why?
Sent from my GT-I9100 using Tapatalk
Click to expand...
Click to collapse
Hi @Namoi,
unfortunatelly I'm not a Android developer. So I'm not able to tell you the meaning of the preload partition. But @the.gangster - which helped me a lot in my case - seems to know whats this area is about.
Maybe he gets an info due to my mention of his name in this post, so maybe he will follow up and answer your question.
Bye
KaeptnAmerica said:
Hi @Namoi,
unfortunatelly I'm not a Android developer. So I'm not able to tell you the meaning of the preload partition. But @the.gangster - which helped me a lot in my case - seems to know whats this area is about.
Maybe he gets an info due to my mention of his name in this post, so maybe he will follow up and answer your question.
Bye
Click to expand...
Click to collapse
How, I know what this partition is : it was introduced by Samsung to allow the installation of Jelly Bean as the standard partition was too small to accomodate all the bloat ware they put in. So it shouldn't be used by other no Samsung based Rom. As I said, on Dirty Unicorns I removed it (well made it 0MB) and I have no issue, but as you pointed for CM 13 it seems it is needed... Why, I have no clue at all...
Yes, the partition was actively used on stock Samy-ROMs to incorporate all the Samsung addons.
And even if it is not being actively used by any non-Samsung stock ROM, at least the CM-ROMs I've seen on the Galaxy S2, still kind of checked the partition's presence or filesystem if present.
I never explored the exact reason, but I do know, if the preload partition is there but does not contain a filesystem (is not formatted), which is the case if a PIT-file changed the starting sector, it is very likely that the CM ROM will hang upon booting up. This might be kernel-related as - if I remember correctly - e.g. some DorimanX kernels didn't show that problem on the same ROMs. But the latter *do* use the preload partition for supporting dualboot.
I am not a friend of removing partitions completely anyway. Rather minimize them to e.g. 8MB. That will at least provide the space needed to put a filesystem on it.
That's also the method used by this great tool.
But for those who still use PIT-files, as @KaeptnAmerica did and who run into the problem, I created a modified TWRP-Recovery (IsoRec!) now, that provides the option to format the preload partition.
Hope it helps. @KaeptnAmerica: as you see, quoting worked
P.S.: By the way: reading the title of this thread just wanted to point out, that the issue of CM not booting when preload is not containing a filesystem is not related to what IsoRec-Recovery is installed or if there is one installed at all. This would also happen with no additional IsoRec-recovery is installed.
Hello
I have a problem with my phone. I really need encryption as my phone is used for political activities. I was using CRdroid then Mokee and then Resurrection Remix with encryption. The problem being that i cannot use the recovery to update or whatever as TWRP cannot decrypt data. So each time i want to update i have to format everything and start from the sratch...
I heard that with TWRP 3.1.1 and Lineage OS it could work. I could not format through TWRP (format was not working - impossible to mount partition) so i used fastboot format userdata and installed LOS afterwards. I then tried to encrypt but it doesn't work. It shows an android logo green on black (the one you see while encrypting) for 1 or 2 seconds and then it boots the phone without any encryption. Strange enough i can even do it without setting a password/pin/code/scheme which was not possible before (it always asked to create one before). Strange enough i thought it was a LOS problem so i tried to reinstall RR or CRdroid but it does the same !
Here is a logcat in case any of you could help, that would be so nice !
https://pastebin.com/t50Wn3S4
thanks a lot !!
Ben
First of all, I am not familiar with english, so the contents can be awkward.
Please understand.
When I'm done optimizing, I do a backup with TWRP.
In this process, I erase cache and dalvik-cache and back up.
Recovery from these backup files was normal for other models.
(LG, Samsung, etc.....)
However, RN2 has a bug that forces all applications to shut down after booting.
The same symptoms occur in both Android 5.0/5.1 roms(cm12.1, RR, Mokee, AOSP....). (I didn't test it on the MIUI)
I tried different versions of the TWRP, but the results were the same.
Of course, the reset and reinstallation process has been numerous.
I have no idea what the problem is.
Please share your knowledge.
try using xtreme reborn custom rom
Okay. I am tired of constantly bricking and reinstalling my stock rom onto my Cubot. If not for Titanium Backup i would be so frustrated. So i have decided to ask for help with flashing the Phhusson ROM.
The problem i have is that i do not know the proper steps to install the ROM.
I have unlocked bootloader, installed TWRP, cleared cache, data, vendor, dalvik and installed system.img and magisk for root, but no luck.
I keep getting NO OS installed.
Anyone who successfully installed a CUSTOM ROM for their Cubot X18 Plus please give a tutorial here. Preferably a video tutorial. :good:
Also, if you have any pointers for restoring base band (i have tried flashing stock, copying emmc to root, having driver issues with magic box) i would love help on that but you can private message me if you wanna help (ill pay if you want to be paid, but not much)
You don have to whipe vendor because this is the base folder of the phone its like the kernel but in treble.
You habe to search a pre tested rom on cubot x18 pluss Like AOSP 9.0 from PHHUSSON on GitHub
i wish you good luck, im going to install it to in my cubot, and sorry for my english because im Chilean.
kene200 said:
Okay. I am tired of constantly bricking and reinstalling my stock rom onto my Cubot. If not for Titanium Backup i would be so frustrated. So i have decided to ask for help with flashing the Phhusson ROM.
The problem i have is that i do not know the proper steps to install the ROM.
I have unlocked bootloader, installed TWRP, cleared cache, data, vendor, dalvik and installed system.img and magisk for root, but no luck.
I keep getting NO OS installed.
Anyone who successfully installed a CUSTOM ROM for their Cubot X18 Plus please give a tutorial here. Preferably a video tutorial. :good:
Also, if you have any pointers for restoring base band (i have tried flashing stock, copying emmc to root, having driver issues with magic box) i would love help on that but you can private message me if you wanna help (ill pay if you want to be paid, but not much)
Click to expand...
Click to collapse
Hi, I was able to useflash phh GSI (works just great btw). This is how I ended up doing it:
1. Flash TWRP.
2. In TWRP you'll see errors due to the encryption of the partitions. To resolve this you have to format the userdata partition either with fastboot either with TWRP
3. After fixing the encryption problems in TWRP mount and transfer Magisk to the phone and flash it using TWRP.
4. Transfer the GSI image (A only) and flash it using TWRP. At this stage you could flash it with fastboot as well if you reboot to the bootloader, but don't boot into the system yet. As I said before I used PHH AOSP 9 GSI image.
5. Wipe using TWRP and reboot to system.
The first time I tried to flash it I used the stock recovery wipe function which wipes out the IMEI and stuff, this forced me to reinstall stock rom to set the IMEI with the MTK engineering tools and restart the whole process.
Today i wanted to upgrade from Nitrogen OS android 9 to PixelExperience android 10 and it didn't work at all...
At first i wiped:
Dalivik / ART Cache
cache
system
Data
And now I just don't know what to do, because after flashing PixelExperience, I got the message: "No OS installed! Are you sure you wish to reboot?".
After that I flashed disable force encryption and rebooted anyway just to see the fastboot screen.
Then i wiped everything again and tried flashing my old ROM without any success (error 7) after that message,
I wiped everything once more and flashed vendor-firmware (it was an old version the name of the file is: "fw_beryllium_miui_POCOF1Global_V10.3.7.0.PEJMIX")
and it still didn't work...
Now I searched online for any solutions and just downloaded a new firmware (filename: beryllium-9.4.1-9.0-vendor-firmware.zip) flashed it,
and after trying to install any of the above mentioned ROM's i got the same results.
I'm kind of desperate right now and don't know what to do. I though that i could maybe format my phone,
I saved all my important files on my PC so that isn't really a problem.
Please help me! (Please let me know if you need to know more info, I hope I didn't forget anything)
xueru said:
Today i wanted to upgrade from Nitrogen OS android 9 to PixelExperience android 10 and it didn't work at all...
At first i wiped:
Dalivik / ART Cache
cache
system
Data
And now I just don't know what to do, because after flashing PixelExperience, I got the message: "No OS installed! Are you sure you wish to reboot?".
After that I flashed disable force encryption and rebooted anyway just to see the fastboot screen.
Then i wiped everything again and tried flashing my old ROM without any success (error 7) after that message,
I wiped everything once more and flashed vendor-firmware (it was an old version the name of the file is: "fw_beryllium_miui_POCOF1Global_V10.3.7.0.PEJMIX")
and it still didn't work...
Now I searched online for any solutions and just downloaded a new firmware (filename: beryllium-9.4.1-9.0-vendor-firmware.zip) flashed it,
and after trying to install any of the above mentioned ROM's i got the same results.
I'm kind of desperate right now and don't know what to do. I though that i could maybe format my phone,
I saved all my important files on my PC so that isn't really a problem.
Please help me! (Please let me know if you need to know more info, I hope I didn't forget anything)
Click to expand...
Click to collapse
I found a old backup, that i made in twrp and after loading that, i was able to flash stuff again, sorry if i inconvenienced anyone
Same happened with me when i flashed PE 10 from PE 9 PIE..
So i flashed Letest Miui 11 (pie) via fastboot then
Installed PE 10 via twrp..
so this is the fix.