Hello, I have a Samsung j2 phone (model j200g) and it shows me a black screen (in place of the Samsung logo) after the boot, and I want a solution from you, I will show you what I did after this problem occurred.
- When this problem occurred, I did not know what to do, so I had to flash it with its own file, and after the success of the flashing process, the same problem remained.
**I tried to flash it several times, but same problem, so I had to flash it with a custom ROM (lineage os 14.1).
-After failed attempts to flash, I installed the recovery module (twrp) and copied the custom rom file (lineage os 14.1) to the phone via otg, I flashed the custom and the installation succeeded. I turned on the phone and the “samsung galaxy j2” screen appeared, and then the custom ROM boot screen came, but here the boot (the circle that rotates for the custom ROM) remained as it was moving indefinitely. I left it for a whole day and it is still in this state.
I want you to solve this problem. I spent days looking for a solution to this problem.
I understand you have flashed full Samsung ROM/firmware BL AP CP CSC from Odin3, then installed TWRP and installed LineageOS on boot + system. In case you haven't already done, disable dm-verity with this zip
https://build.nethunter.com/android-tools/no-verity-opt-encrypt
don't forget to format Data (wipe - advanced - format - type 'yes')
aIecxs said:
I understand you have flashed full Samsung ROM/firmware BL AP CP CSC from Odin3, then installed TWRP and installed LineageOS on boot + system. In case you haven't already done, disable dm-verity with this zip
https://build.nethunter.com/android-tools/no-verity-opt-encrypt
don't forget to format Data (wipe - advanced - format - type 'yes')
Click to expand...
Click to collapse
thanks i will try, but the link not working
check your VPN, link is fine
aIecxs said:
I understand you have flashed full Samsung ROM/firmware BL AP CP CSC from Odin3, then installed TWRP and installed LineageOS on boot + system. In case you haven't already done, disable dm-verity with this zip
https://build.nethunter.com/android-tools/no-verity-opt-encrypt
don't forget to format Data (wipe - advanced - format - type 'yes')
Click to expand...
Click to collapse
i tried this but same problem
try with stock ROM no TWRP no modifications.
Related
Hi, I'm getting stuck at the black screen just before the boot animation (the one that says "samsung galaxy SIII gt-i9300"), after flashing custom rom via CWM. Maybe I'm a complete noob but I think something is wrong in my phone.
I had installed MIUI official before, then removed it to get warranty back and sent phone to samsung service to fix the my broken simcard compartment.
After getting my phone back, I tried to install MIUI again and got stuck.
The strange thing is how fast ROM is installed in CWM, less than 10 seconds...
No error message and says install is complete
have retried 7 times now, using this:
- Odin 3.04
- CF-Auto-Root (http://forum.xda-developers.com/showthread.php?t=1957273)
- CF-Root 6.4 - SuperSU+CWM5.5+CWMManager (http://forum.xda-developers.com/showthread.php?t=1695238)
- ClockworkMod Touch 6.0.3.2 (http://forum.xda-developers.com/showthread.php?t=1719744)
- ClockworkMod 6.0.3.6 - Touch and Non-Touch (http://forum.xda-developers.com/showthread.php?t=2200501)
ROMs:
- MIUI Official 3.8.16
- MIUI Official 3.7.12
- CyanogenMod 9.1.0 (stable)
what I do:
- boot to bootloader
- flash CF root with Odin (Auto reboot and F.reset Time are checked)
- reboot, then shutdown
- boot to bootloader
- flash CWM with Odin (Auto reboot and F.reset Time are checked) also tried to install with ROM manager
- reboot, then shutdown
- boot to recovery
- wipe data/ factory
- wipe cache
- wipe dalvik
- install zip from sdcard (internal) <-- strange thing here is how fast it is installed, less than 10 seconds...
- wipe data/ factory, cache, dalvik again
- reboot
- got stuck.
- flash samsung stock ROM I9300UBALE6_I9300ZTOALE7_ZTO (brazilian 4.0.4, phone was in that version when installed MIUI first time)
Don't know what to do now, please help!
Does it boot with stock roms?
Please DO NOT flash anything older than 4.1.2 stock...
If all zips opnly take 10 seconds, perhaps theyre getting corrupt on your memory. How are you getting the zips on your phone?
rootSU said:
Does it boot with stock roms?
Please DO NOT flash anything older than 4.1.2 stock...
If all zips opnly take 10 seconds, perhaps theyre getting corrupt on your memory. How are you getting the zips on your phone?
Click to expand...
Click to collapse
yes, it boot with stock rom.
I just copy/paste files from windows, always done that, but now that you say, md5 is diferent...
I'll check stock ROM and file copy.
Thanks!
It was the file copy messing with the zip...
used adb push and all OK now!
Thanks again!
Hi,
I recently unlocked my bootloader after a really long time. I then proceeded to flash twrp and then flashed superSU and rooted my phone. I took a backup of my rom and then proceeded to install RR 5.8.4. I was given a error 7. Tried this method (https://forum.xda-developers.com/showthread.php?t=2522762) but then it gave me a error 6. Would someone help me out ?
Thx.
1) flash latest global developer MIUI ROM via MiFlash to updated firmware and to reset things if they messed up (watch out if you lock your bootloader while flashing, choosing the wrong .bat file);
2) after flash TWRP via fastboot;
3) boot TWRP and "advanced wipe" ALL partitions (except MicroSD if you have a MicroSD inserted and you want to keep its data);
4) reboot to recovery and install the RR .zip file (and the gapps .zip file if you use it);
5) after you boot into RR, you can then reboot to TWRP and install Magisk .zip to get root and other nice things.
Can i factory reset my device instead of flashing developer rom as the developer rom is quite big, around 1.4gb?
shalom170401 said:
Can i factory reset my device instead of flashing developer rom as the developer rom is quite big, around 1.4gb?
Click to expand...
Click to collapse
If you've TWRP installed at the moment then try this :
Boot to TWRP
Take a nandroid backup (just incase)
Wipe > advanced wipe > swipe to confirm
Flash firmware if you're coming from marshmallow based MIUI
Flash ROM & Gapps
Reboot
If you still get errors, probably corrupted zip. Try Re-downloading the zip.
shalom170401 said:
Can i factory reset my device instead of flashing developer rom as the developer rom is quite big, around 1.4gb?
Click to expand...
Click to collapse
You can try. Remember that if you download the full MIUI ROM, you should follow this guide http://en.miui.com/a-234.html
You can also upgrade the firmware without downloading the full ROM, from here https://forum.xda-developers.com/re.../firmware-firmware-update-2017-08-04-t3651537
Will try soon and reply
Even after flashing the firmware, i get the same error 7
I have downloaded this rom (https://www.google.co.in/amp/s/foru...nt/rom-resurrectionremix-5-8-2-t3567023/amp/) and flashed twrp using this guide (http://en.miui.com/thread-536180-1-1.html)
Maybe this is a stupid question, but your phone has MediaTek chipset or Qualcomm chipset?
I'm pretty sure it is qualcomm as the cpu speed is 2.0ghz
Now, i get this error and status error 7.
What should i do?
Where you can format all partitions, you can fix them too.
It looks like your /data is using f2fs, you should fix it converting the partition in ext4 (in official TWRP it's not possible to use f2fs).
Check all partitions, not only /data, to be formatted as ext4
So, what r the steps i should follow?
And btw, is there any unofficial twrp which i could use?
Enter TWRP, choose Wipe > Advanced Wipe
Check the box for "data"
Tap "change or repair file system"
Tap "Change file system"
Tap "ext4"
Swipe the button
Repeat for other partitions
I don't know if there are unofficial TWRP that support f2fs. Probably they exists, but you should also check if the default RR kernel supports f2fs, else you have to flash a custom kernel that supports f2fs.
Just one important question. During this process, if something weird happens ( like i get my phone soft bricked) and i got a nandroid backup. Will i be able to flash it successfully using twrp?
Yes, changing file system is a pretty safe operation (except for the erasing of the data inside the partition, as a normal format).
Flashing the backup or a full fastboot image will reset things back.
But it already shows it as ext4
Oh mahn, it still doesn't resolved?
Flash official TWRP via fastboot mode, skip this step if your already on official TWRP
Boot to TWRP
Wipe
Flash cm14.1 mido firmware
Flash Rom
Flash Gapps
??
Reboot
Note that, you should try Re-downloading all the things, like Rom / Gapps
Dude, i am unable to flash the rom due to cant install this package error and status error 7 !
shalom170401 said:
Dude, i am unable to flash the rom due to cant install this package error and status error 7 !
Click to expand...
Click to collapse
Yeah man, that's what I'm saying, you should try installing cm14.1 firmware first, then Rom..
Even after flashing the firmware, i get the same errors
Hi
Got a GT-P5110.
- boots to stock recovery (or other recovery) insted to system
- buttons are not stuck
- Original GT-P5110ZWAXEO (from file in efs), on case, on box
- Can flash CWM, philz, twrp recovery, it will boot the recovery
- After installing any custom rom (lineageos13, cm10, cm12, cm13, omni etc) it will boot to the recovery
- Choosing reboot in the recovery will power off the device, not reboot
- flashing factory rom (P5110XXDNH2 and some other) with odin works, after reboot it shows "Installing system update..", the blue bar goes to about half, after it will show "Erasing..." and power off after a second. Power on again it will boot to facotry recovery, in this place wipe data will work, wipe cache will give error.
- wiping the partitions work with custom recovery, chcecked from shell, partitions are writable, no errors
- flashed new PITfile with repartitioning, still no change.
- if i install a custom ROM, the battery charge screen will come from the custom rom.
So i can not get any OS working on this tab. Any ideas?
The 4-file ROM for odin i only found for GT-P5100, should i try to flash it?
I found the bootloader for P5110, should i flash it?
Thx
So i found my problem.
It was the like here, i missed this thread before. The dock/charge connector was faulty (looks like new) and prevents the tab from booting.
https://forum.xda-developers.com/galaxy-tab-2/help/gt-p5100-boot-recovery-download-mode-t3246322
Plz anybody help this out...
I unlocked bootloader, then immediately flashed Pitchblack recovery, then booted into recovery.
Initially console shows decrypted FBE device with default password. But Encryption status : Encryped
So I went into wipe & Formatted Data inorder to get rid of encryption. Then I rebooted recovery & it shows Unable to decrypt FBE device.
[UPDATE] (24/12/20) : The console output Unable to decrypt FBE device was nothing but to tell us that incompatible operating system flashed.
I flashed global version roms which are the main cause for bootloops. I flashed stock rom, then immediately worked out of the box.
1. Format data after going into twrp *It will wipe you device*
2. If you don't want to install a custom rom just mod MIUI, remove your lock screen password or flash orange fox and if it asks for password just put your lock screen password.
3. Else if you want to install a custom rom
Open recovery
Wipe data cache davilk
Flash rom
Format data
Reboot.
LoadOP2 said:
1. Format data after going into twrp *It will wipe you device*
2. If you don't want to install a custom rom just mod MIUI, remove your lock screen password or flash orange fox and if it asks for password just put your lock screen password.
3. Else if you want to install a custom rom
Open recovery
Wipe data cache davilk
Flash rom
Format data
Reboot.
Click to expand...
Click to collapse
Thnx for reply. I've tried Orange fox too. When I format data, internal storage doesn't decrypt. Also when I flash custom roms, they flash, but I'm gonna stuck in bootloop.
My main problem is that I can't decrypt storage. Phone boots only when I'm on MIUI stock. Am I missing something ?
That is odd but still flash fastboot rom and then flash twrp , flash a rom of your choice then format data . Maybe it will help . Btw which rom are you installing.
LoadOP2 said:
That is odd but still flash fastboot rom and then flash twrp , flash a rom of your choice then format data . Maybe it will help . Btw which rom are you installing.
Click to expand...
Click to collapse
Thnx for the reply. I'm trying to have lineage 17.1 & resurrection remix official build. I think rom's not the issue here. I need to know one thing.
To exactly say my issue, I can do flashing. But when I do & then reboot, Internal storage doesn't show the size & mtp doesn't work too, with bootloop issues along together.
There is no official LineageOS for the device.
kalehrl said:
There is no official LineageOS for the device.
Click to expand...
Click to collapse
Oh, I've mistaken, I was about to say resurrection remix official build & lineage unofficial one. Btw what do you think my device is going up to ? How can I decrypt & use internal storage successfully? I can't use internal storage when I flash a rom. Bcaz internal storage renders useless because of encryption.
Which recovery are you using?
Try flashing magisk 20 or 21.
Flash twrp by marounfurio( I am sorry if I slaughtered the name) which is available on xda.
And format data.
It's midnight here and I am going to sleep I will help to tommorow morning.
LoadOP2 said:
Which recovery are you using?
Try flashing magisk 20 or 21.
Click to expand...
Click to collapse
Right now I'm on Pitchblack beta latest build.
I tried magisk on MIUI stock through patched boot method, it worked, but no apps able to access root. I checked all magisk settings...
I think encrypted data partition is the whole culprit here. How can I decrypt it ?
MPK99 said:
Right now I'm on Pitchblack beta latest build.
I tried magisk on MIUI stock through patched boot method, it worked, but no apps able to access root. I checked all magisk settings...
Click to expand...
Click to collapse
And what about flashing magisk in twrp.
MPK99 said:
Right now I'm on Pitchblack beta latest build.
I tried magisk on MIUI stock through patched boot method, it worked, but no apps able to access root. I checked all magisk settings...
I think encrypted data partition is the whole culprit here. How can I decrypt it ?
Click to expand...
Click to collapse
Formatting data normally decrypts it . I don't know why something like this is happening here.
Follow my guide again maybe? Give it a shot step by step.
LoadOP2 said:
Formatting data normally decrypts it . I don't know why something like this is happening here.
Follow my guide again maybe? Give it a shot step by step.
Click to expand...
Click to collapse
Yah, I'm feeling weird too. Normally there are 3 ways to remove decryption...I tried all those.
1. Formatting Data by typing "yes"
2. Formatting data partition from f2fs to ext4
3. Installing Decrypt script v2 zip immediately after flashing stock rom.
I tried everything I could. I know all sorts of common flashing things. I caz I always used to try so many roms on my previous redmi's, but this one is special case.
I'd suggest you use LineageOS recovery. That's how I removed decryption.
kalehrl said:
I'd suggest you use LineageOS recovery. That's how I removed decryption.
Click to expand...
Click to collapse
Sure. Encryption is the whole culprit for me to say exactly. I'm trying to decrypt & flash builds. I'll notify if it works. Nice to get help from you guys.
Try this.
How to decrypt rom/storage so you can easily switch roms without format
First I would thankx to @sakhatlonda for koutiliy.zip
Steps to download file
1. Download koutility.zip from below.
2. Documentation related to koutility
Read from below link (recommended)
Just a utility zip which can be flashed on every rom flash, to do some pre-defined tasks.
Can be used either to copy everything you place in sdcard/sudeep/system_root to respective dirs or to set config and use that to do predefined tasks
This is how it works:
Flash in recovery, every option has Note with it
Available Configs:
brbootdtbo - auto backup/restore boot & dtbo, will do backup if no backup present and will do restore if backup is there
bbootonly - always backup boot
bdtboonly - always backup dtbo
resbootdtbo - always restore boot & dtbo (brbootdtbo won't work if this is enabled)
enalways - encrypt always (edauto won't work if this is enabled)
dealways - decrypt always (enalways & edauto won't work if this is enabled)
edauto - auto change encryption state on each flash
avb - removes avb flags (if decrypted)
quota - removes quota flag (if decrypted)
keep - doesn't over-writes boot/dtbo backups
debloat - removes bloats
rebloat - restore removed bloats
patchD - same as flash but set in config
productsize - makes a product image from your currently flashed rom to sdcard/sudeep and adds 600mb to it. So you can flash gapps etc. without error. (PC needed to flash product.img)
Steps to decrypt rom/storage
1. Flash roms
2. Flash koutility.zip tested on aosp only
3. Format data (required only first time after flashing koutility)
4. Reboot to recovery
5. Flash gapps (optional)
6. Boot into system
Congratulations your storage/rom is decrypted , you can switch roms without format
Next time when you want to switch roms
Steps
1. Wipe data,caches and dalvik caches
2. Flash rom
3. Flash koutility.zip
4. Reboot to recovery
5. Flash gapps (optional)
6. Boot into system
Notes
Remember you need to config koutility.zip in recovery
How to config koutility for decryption
Volume down (set config) > yes
After that "No" till 5th option
Then "yes" for 6th option
Rest "No" till 15th option
Last "yes" to flash
@LoadOP2 Thanx for providing KoUtil & its read me.
But I think we shouldn't reboot to recovery immediately after formatting the data. Because the stock rom will start it's initial encryption process by then & I won't get decrypted storage. Isn't it ?
I think this is the case that's happening to me. I always reboot recovery after formatting data, my storage will encrypt again because of stock rom's existence.
Yes you have to reboot to recovery. Otherwise you won't be able to use data partition.
LoadOP2 said:
Yes you have to reboot to recovery. Otherwise you won't be able to use data partition.
Click to expand...
Click to collapse
Yes, you're correct, we should do that. But can you read my 1st post in this thread. This is about that specific problem. I'm rebooting recovery after formatting data, then recovery shows Unable to decrypt FBE device
Send your recovery logs after formatting data.
LoadOP2 said:
Send your recovery logs after formatting data.
Click to expand...
Click to collapse
That would help. I'll attach screenshots too. Currently I'm on stock & being busy. I'll do this by today night & post logs & screenshots.
Hi, I've recently repaired my mido with a new screen after a fall. After this I tried some custom roms. Initially I managed to install lineage 18.1. After I switched to dotOS. From this point on, the phone restarts a few seconds after the launcher appears. To fix this I used MiFlah to install latest MIUI, formatted data, wiped everything, tried TWRP and Orangefox, tried other custom roms with no changes. Now only stock MIUI11 works. Other custom roms (included lineage) gets the phone continuously rebooting. Could be an hardware problem? What am I doing wrong? It is the first time in ages I have problems flashing ROMS .-.
Thanks.
gabritb01 said:
Hi, I've recently repaired my mido with a new screen after a fall. After this I tried some custom roms. Initially I managed to install lineage 18.1. After I switched to dotOS. From this point on, the phone restarts a few seconds after the launcher appears. To fix this I used MiFlah to install latest MIUI, formatted data, wiped everything, tried TWRP and Orangefox, tried other custom roms with no changes. Now only stock MIUI11 works. Other custom roms (included lineage) gets the phone continuously rebooting. Could be an hardware problem? What am I doing wrong? It is the first time in ages I have problems flashing ROMS .-.
Thanks.
Click to expand...
Click to collapse
The vendor partition could have some code/ file that persists stock ui or system
and make sure your phone was rooted before flashing custom rom
and also via twrp flashing. from what Ive seen flash in twrp before flash custom rom( https://www.google.com/search?client=firefox-b-d&q=disable+encryption+treble ) then flash the "verity and encryption disabler ,theres another one to re enable encyption only " then flash custom rom
after flashing custom rom reboot poweroff(switch phone off via twrp)
reboot into twrp and flash whatever else you need
now reboot to system and your phone should work fine
Thanks, it worked!
I did:
Flash last miui with miflash
Flash recovery
Flash you suggested zip
Format data
Flash lineage 17.1 (android10)
WIpe system, data, cache, art cache
Flash any android 11 ROM
gabritb01 said:
Thanks, it worked!
I did:
Flash last miui with miflash
Flash recovery
Flash you suggested zip
Format data
Flash lineage 17.1 (android10)
WIpe system, data, cache, art cache
Flash any android 11 ROM
Click to expand...
Click to collapse
Holy **** how did you come up with this.
Either the zip with Magisk somehow fixed it or installing the android 10 rom somehow. Either way doesn't make sense
flairepathos.info said:
The vendor partition could have some code/ file that persists stock ui or system
and make sure your phone was rooted before flashing custom rom
and also via twrp flashing. from what Ive seen flash in twrp before flash custom rom( https://www.google.com/search?client=firefox-b-d&q=disable+encryption+treble ) then flash the "verity and encryption disabler ,theres another one to re enable encyption only " then flash custom rom
after flashing custom rom reboot poweroff(switch phone off via twrp)
reboot into twrp and flash whatever else you need
now reboot to system and your phone should work fine
Click to expand...
Click to collapse
Didn't work for me,
- did all the steps , exactly - flashed stock fastboot , then flashed Android 10 based rom crDroid + pico gapps. worked fine for 2 hours or so .
but interesting enough , phone freezes then shutdown without restarting , then i would go and trun it back on , but fingerprint not working now
heroboy107 said:
Didn't work for me,
- did all the steps , exactly - flashed stock fastboot , then flashed Android 10 based rom crDroid + pico gapps. worked fine for 2 hours or so .
but interesting enough , phone freezes then shutdown without restarting , then i would go and trun it back on , but fingerprint not working now
Click to expand...
Click to collapse
i think somewhere in the process the persist partition gets damaged .
heroboy107 said:
i think somewhere in the process the persist partition gets damaged .
Click to expand...
Click to collapse
so if you have magisk you can use a zip file to chmod 744 or 644 (it may be "chmod root 744" )the /persist partiton and thatll mean only true root has access
so 7 is read write execute 6 is read and write 4 is read only 5 is read execute i forgot which number was execute only 1 maybe?
so play with the permissions or look in the root folder for boot.p or permissions.sh then you can modify in there the permissions, it can cause bootloop , so always keep an original copy or youll hae to reflash(DISCLAIMER)
so you can pull the file using adb+root / or a root explorer
Copy it to phone then edit then copy to SDCARD
reboot to twrp then use shell/terminal "chmod 777" the partition where the file is / or read write everything
then copy the file and overwrite the original