Related
Hi there,
I need some help from you guys.
I was flashing my phone through Odin and ticked NAND ERASE ALL option.
Now, no matter what I do, I'm stuck at bootloop.
I can enter at download mode, also recovery mode. My phone is recognized by Odin.
So, what I've tried to solve it:
1. Flashed Original Samsung (4.4.2 India I9192DDUCNG2) through ODIN (I can flash with success, but still stuck at bootloop)
2. Flashed Original Samsung (4.4.2 Russia i9192XXUCNG2) through ODIN (bootloop)
3. Flashed Philz Touch Recovery, wipe everything and then Flashed a Custom ROM (still bootloop)
5. Repeated 1. with PIT file (still bootloop)
I don't know what to do...
I'm desperate!
Can anyone help me?
Regards.
Finally I solved it...
After trying several methods, I was almost giving up but suddenly I got it working again...
What I did:
1. Downloaded i9192 PIT file from http://forum.xda-developers.com/showpost.php?p=53003227&postcount=4 (maybe not needed)
2. Flashed Original Samsung i9192XXUCNG2 (4.4.2 russia) through ODIN 3.10 with PIT file (re-partition checked)
3. After flash process, I got bootloop again
3.1. (just in case) I removed the battery for 5 minutes, but I think it was not necessary
4. I went to stock recovery [get some errors regarding /data mount with invalid argument]
5. Selected 'wipe cache partition'
6. Selected 'wipe data/factory reset'
7. Reboot and voilà!
Thanks to ismael0301 for the initial help!
Regards.
Dude, did you try do a wipe/data and cache? That solve all!
ismael0301 said:
Dude, did you try do a wipe/data and cache? That solve all!
Click to expand...
Click to collapse
Yes, I tried (as I said at step 3)...
It didn't work!
s0cks said:
Yes, I tried (as I said at step 3)...
It didn't work!
Click to expand...
Click to collapse
Well try to wipe but with the stock recovery or you already try that?
ismael0301 said:
Well try to wipe but with the stock recovery or you already try that?
Click to expand...
Click to collapse
I already tried it, didn't work also...
It seems that I can't mount /sdcard (internal storage)...
I think it is related to a partition problem...
Is there any difference between a PIT file from 4.2.2 and from 4.4.2?
I tried this solution for my phone that it also has bootloop, what everytime that my phone tries to boot, it gets stuck at the boot animation, it does not load completed, it gets stuck and restarts, vibrates one time then restart, the vibrates again and it does this cycle everytime.
errusdan said:
I tried this solution for my phone that it also has bootloop, what everytime that my phone tries to boot, it gets stuck at the boot animation, it does not load completed, it gets stuck and restarts, vibrates one time then restart, the vibrates again and it does this cycle everytime.
Click to expand...
Click to collapse
Are you able to enter at DOWNLOAD MODE? If yes, try to reflash via ODIN an original (untouched) ROM...
If after reflesh it does not work, try to enter at recovery mode and then make a wipe data/factory reset...
I have a s4 mini i9192 phone with 4.4.2 latest updated version and I want to root the phone but unfortunately I even can't go to download or recovery mode.thank u please help me
Salve io ho un s4 mini duos i9192,non riesco ad installare la rom(si riavvia continuamente) poichè credo che non sia abilitato il debug usb;
ovviamente non accendendosi non posso abilitarlo dalle impostazioni;
l'unica cosa che riesco a fare è metterlo in modalità download provando a installare più di un firmware e non riuscendo nemmeno a farlo partire in recovery mode. sono riuscito con i driver attraverso adb. Sicuramente non sono praticissimo ma spero mi possiate aiutare cmq, Grazie , Francesco
Hi I have a s4 mini duos i9192, can not install the rom (continually reboots) because I believe it is not enabled USB debugging;
obviously not coming on I can not enable the settings;
the only thing I can do is put it into download mode trying to install more than one firmware and failing even to get it started in recovery mode.
I managed with drivers via adb. Surely I am not very practical, but I hope you can help me anyway, Thank you, Francesco
pabbuccio said:
Salve io ho un s4 mini duos i9192,non riesco ad installare la rom(si riavvia continuamente) poichè credo che non sia abilitato il debug usb;
ovviamente non accendendosi non posso abilitarlo dalle impostazioni;
l'unica cosa che riesco a fare è metterlo in modalità download provando a installare più di un firmware e non riuscendo nemmeno a farlo partire in recovery mode. sono riuscito con i driver attraverso adb. Sicuramente non sono praticissimo ma spero mi possiate aiutare cmq, Grazie , Francesco
Hi I have a s4 mini duos i9192, can not install the rom (continually reboots) because I believe it is not enabled USB debugging;
obviously not coming on I can not enable the settings;
the only thing I can do is put it into download mode trying to install more than one firmware and failing even to get it started in recovery mode.
I managed with drivers via adb. Surely I am not very practical, but I hope you can help me anyway, Thank you, Francesco
Click to expand...
Click to collapse
You don't need debugging on to flash a ROM with Odin or recovery. Make sure you are using up to date version of Odin for our phone. What message does Odin give? But I wouldn't be surprised if it's hardware
Hello all !
(First, sorry if I don't make myself clear enough, I'm french..)
Today I updated the Paranoid Android rom from the OTAParanoidandroid app, and when it said it was rebooting, the screen went off in a weird way.
I rebooted it and it was stuck on the boot animation (with the colourful spheres) for like an hour. I gave up, pressed the power + Volume up button, and went into recovery.
I tried updating it from here, but I've got the same problem, the boot animation takes ages !
So I cancelled it again, and I tried to wipe the cache and the dalvik's one.
When I rebooted it, it said it was updating android apps, but when it came to '"starting apps.." it remained stuck for 10mn..
After That, I managed to have it working with my PC, I reflashed the G apps and the Rom.
But Maps "stopped working" everytime
I tried a previous version of gapps, deleting the cache... Still nothing !
Salut !
Il y a un problème avec la beta 2 de paranoid, le module GPS semble ne pas être inclus... En attendant que ça soit corrigé, je pense qu'il vaut mieux retourner sur la beta1 :/
nhibel said:
Salut !
Il y a un problème avec la beta 2 de paranoid, le module GPS semble ne pas être inclus... En attendant que ça soit corrigé, je pense qu'il vaut mieux retourner sur la beta1 :/
Click to expand...
Click to collapse
Hello !
Finalement j'ai fait un wipe complet et réinstallé la beta 2 et les gapps 4.4.4... Mais le gps fonctionne très bien pour moi
Known issue in Beta 2
http://forum.xda-developers.com/showpost.php?p=55707753&postcount=3691
In Beta 1 GPS is working but there are Problems with the camera (taking 10 seconds to Start, also for Flashlight)
Targunitoth said:
Known issue in Beta 2
http://forum.xda-developers.com/showpost.php?p=55707753&postcount=3691
In Beta 1 GPS is working but there are Problems with the camera (taking 10 seconds to Start, also for Flashlight)
Click to expand...
Click to collapse
Hey, thanks for your answer.
IDK why, but the GPS is working on my BETA2.. Is this bad ?
of course it is good if it is working
Are you sure you are on Beta 2 and not getting your possition over WLAN?
Did you do a clean install of Beta 2 or first with Beta 1 and then Update?
Is your Problem
But Maps "stopped working" everytime
Click to expand...
Click to collapse
solved in the meantime?
If not, try to format /system (CARE YOU LOSE DATA) and then flash GAPPS again
http://forum.xda-developers.com/showthread.php?t=2397942
I prefer MICRO MODULAR PACKAGE or PICO MODULAR PACKAGE
Edit: Maybe only format /system could not be enought:
http://android.stackexchange.com/questions/65762/how-do-i-remove-gapps-from-cyanogenmod
(This is also for other Roms then Cyanogenmod)
Yep that's exactly what I did and the initial problem is solved
The thing was that the "system wipe" option was not in the initial tab of my recovery, I had to look around a bit (at first I was only factory reseting it, I don't really remember, but it wasn't exactly a system wipe, maybe formating the data..?)
Anyway after that everything worked fine !
IDK anything about WLAN..? But my gps is working, and I successfuly flashed BETA2 (even paraonoidandroidOTA says I'm up to date..)
So, I don't really understand why is it working ?
i need help
sKY'HER said:
Yep that's exactly what I did and the initial problem is solved
The thing was that the "system wipe" option was not in the initial tab of my recovery, I had to look around a bit (at first I was only factory reseting it, I don't really remember, but it wasn't exactly a system wipe, maybe formating the data..?)
Anyway after that everything worked fine !
IDK anything about WLAN..? But my gps is working, and I successfuly flashed BETA2 (even paraonoidandroidOTA says I'm up to date..)
So, I don't really understand why is it working ?
Click to expand...
Click to collapse
ur lucky D:
stuck at sony boot logo during first boot after installing paranoid android 4.6 beta
just installed pa 4.6 beta3 ,gapps, almost 15minutes still cellphones stuck at sony logo.
i have unlocked boot loader, rooted,installed cwm recovery i am little but worried please help me
impradeepy said:
just installed pa 4.6 beta3 ,gapps, almost 15minutes still cellphones stuck at sony logo.
i have unlocked boot loader, rooted,installed cwm recovery i am little but worried please help me
Click to expand...
Click to collapse
First boot always tooks a bit longer, but 15 min is too long i suppose...
Make a new clean flash...
wiping all data + cache + dalvik cache
Cheers mate all working after 30mins i used fastboot mode and reboot into recovery and repeated all steps once again using it from past 2hours no fc,no random reboots, gps,wireless working,screenshot fixed all good thanks paranoid android
Sent from my Xperia S using XDA Free mobile app
I have a similar issue. I tried to udpate via Paranoid OTA app from beta 3 to beta 4 (same issues on b2 => b3) and then I press install and reboot. My phone stucks at the rebooting... animation.
After Hardreset (Power + Upper-Volume button) is restarts and flashes the new rom.
Today again after clean flashing beta 4 once again stuck at Sony logo I think boot loader is not getting boot.IMG itself and after hard reset its boot up also not able to enter into cwm recovery m using dual boot Ubuntu with windows 8.1 and due to drivers issues m not able to flash the kernel img before flashing the ROM please help me
Sent from my Xperia S using XDA Free mobile app
impradeepy said:
Today again after clean flashing beta 4 once again stuck at Sony logo I think boot loader is not getting boot.IMG itself and after hard reset its boot up also not able to enter into cwm recovery m using dual boot Ubuntu with windows 8.1 and due to drivers issues m not able to flash the kernel img before flashing the ROM please help me
Sent from my Xperia S using XDA Free mobile app
Click to expand...
Click to collapse
There are more people having this problem, including me
After the new Update (BETA-4) no boot into CWM is posible
There are two suggestions:
If you can boot normaly, you can install TWRP
the second suggestion is to flash boot.img with fastboot
If you got bootloop you have to try the second one...
What problems do you have with your drivers?
There are a lot of guides how to install drivers while using Windows 8.1
stuck at sony boot logo
Targunitoth said:
There are more people having this problem, including me
After the new Update (BETA-4) no boot into CWM is posible
There are two suggestions:
If you can boot normaly, you can install TWRP
the second suggestion is to flash boot.img with fastboot
If you got bootloop you have to try the second one...
What problems do you have with your drivers?
There are a lot of guides how to install drivers while using Windows 8.1
Click to expand...
Click to collapse
after hard reset i can boot normaly...but if i reboot or shutdown then again i have to do hard reset i will install twrp now,,, i want to flash boot.img using fastboot my problem is whenever i try to connect in fastboot using windows then blue light changes into yellow means no proper connectivity with usb i do not have android sdk atm.
2. on ubuntu i can enter into fastboot blue light stable but only android tools 4.2.2 available in the repository so when ever i type fastboot reboot-bootloader then stuck on waiting device do not why this happening on linux help me
impradeepy said:
after hard reset i can boot normaly...but if i reboot or shutdown then again i have to do hard reset i will install twrp now,,, i want to flash boot.img using fastboot my problem is whenever i try to connect in fastboot using windows then blue light changes into yellow means no proper connectivity with usb i do not have android sdk atm.
2. on ubuntu i can enter into fastboot blue light stable but only android tools 4.2.2 available in the repository so when ever i type fastboot reboot-bootloader then stuck on waiting device do not why this happening on linux help me
Click to expand...
Click to collapse
You just need this one/two commands:
fastboot flash boot boot.img [ENTER]
fastboot reboot [ENTER] (optional)
take the boot.img from BETA-3
Targunitoth said:
You just need this one/two commands:
fastboot flash boot boot.img [ENTER]
fastboot reboot [ENTER] (optional)
take the boot.img from BETA-3
Click to expand...
Click to collapse
finaly i installed flashtool on ubuntu flashed boot.img saved on my hdd(extracted from pa 4.6beta4), then again clean install of rom but same error after every reboot still i have to do hard reset searching on google
impradeepy said:
finaly i installed flashtool on ubuntu flashed boot.img saved on my hdd(extracted from pa 4.6beta4), then again clean install of rom but same error after every reboot still i have to do hard reset searching on google
Click to expand...
Click to collapse
You Mean still no recovery?
The Problem is, that the CWM in PA 4.6 BETA-4 is broken.
You should extract the boot.img from BETA-3
Targunitoth said:
You Mean still no recovery?
The Problem is, that the CWM in PA 4.6 BETA-4 is broken.
You should extract the boot.img from BETA-3
Click to expand...
Click to collapse
i flashed boot.img from beta3 only one time reboot into recovery then again same problem hard reset then i can enter into using vol+ key if not then normal boot
impradeepy said:
i flashed boot.img from beta3 only one time reboot into recovery then again same problem hard reset then i can enter into using vol+ key if not then normal boot
Click to expand...
Click to collapse
Hmm, thats wired, after a clean flash boot you shouldn't get bootloop... did you wait long enough? First boot always takes a few Minutes...
You should flash boot.img from beta3,
do a clean installation of beta4
and flash boot.img from beta3 again
if you still got problems you should flash boot.img from beta3 and then install some other ROM...
Edit: to get right of your battery draining problem, you could install Pico Gapps: http://forum.xda-developers.com/showthread.php?t=2397942 without google search
Hi,
SM-P600 without ROM, without recovery, Kies and Odin doesn't work.
How can I reflash stock ROM or CM12 rom ?
Device : SM-P600 (with samsung rom stock 4.4!?)
I root my tablet with odin and teamwin 2.8.0.0 (PDA field + tar file)
the root flash should success.
I restart in recovery and install custom rom CM12 + Gapp
the tablet restart and stay to CM12 loading during all the night.
I come back into recevery mode
I try to wipe cache/dalvik => unable to mount cache/dalvik
I try to wipe cache => unable to mount cache
I try to wipe system => unable to mount system
I install Kies on my computer and try to restore the official rom with it.
The download of the rom is ok and Kies try to send the rom to the table a transfer is running during 15min (progress bar into computer windows, but no progress bar into tablet).
After that a second transfer progress bar into computer stay to 0% during 1 hour. I unplug my tablet.
Now I have got a table without recovery. I have access to download mode.
But I cannot transfer stock rom (PDA field) with Odin.
Thx for your help.
Staying at your disposal
I can flash recovery mod (TeamWin) with Odin.
But I cannot send Kies tar file by Odin.
I am downloading old stock rom (*tar) to transfer by Odin 3.09
How can I convert a CM12 zip file in tar file to tranfer it (I haven't SD card)
You could use a USB OTG cable (micro USB plug on one end and a socket like the USB ones on a computer on the other), one of these:
http://m.ebay.com.au/itm/301542874539?nav=SEARCH
And use it to plug a USB stick with the zip file on it into your tablet. You would have to mount it in twrp before flashing the zip.
They are a very useful cable to have, if your screen breaks and touch doesn't work you can use it to plug a mouse into the android device and use that for things like backing up your data before repair or disposal.
Hi I fixed the problem,
Re-Flash TWRP (many time) en try to install an unofficial KitKat version (information were write into NAND) but this version bootloop.
I wipe cache, cache/dalvik, Data, System (some eror were display in red, mount error)
I install the unofficial CM12, then the Android invite was displayed :victory:
I setup the unoficial CM12.
Reboot in recovery mode to install gapp
@Nameless One, thx for your help. In TWRP, the mount doesn't work in my case !? (It works with my Galaxy S4)
Appology for my poor English
Hi Dribounet
Dribounet said:
Hi I fixed the problem,
Re-Flash TWRP (many time) en try to install an unofficial KitKat version (information were write into NAND) but this version bootloop.
I wipe cache, cache/dalvik, Data, System (some eror were display in red, mount error)
I install the unofficial CM12, then the Android invite was displayed :victory:
I setup the unoficial CM12.
Reboot in recovery mode to install gapp
@Nameless One, thx for your help. In TWRP, the mount doesn't work in my case !? (It works with my Galaxy S4)
Appology for my poor English
Click to expand...
Click to collapse
Hi Dribounet
I have similar issue with my SM-P600.
I have tried 10 official roms , official and custom recoveries also , without success. I am absolutely sure that I am not following correctly the procedure using Odin and its version or combination of this plus wrong official ROM and so on.
Also have tried to use PIT file because I think something goes wrong with the partitions but not success again,
Would you advice with your steps you follow in order to succeed installing custom recovery.
Can I install only the recovery without ROM and how I can run in it ( button combinations)
For now I am just able to run in Download mode and with one official ROM to run the process to the middle- then goes in error with Odin and when reboot the device it shows message "Firmware upgrade encountered an issue ..... "
Thanks in advance for all answers
p600 bricked
kafencetu said:
Hi Dribounet
I have similar issue with my SM-P600.
I have tried 10 official roms , official and custom recoveries also , without success. I am absolutely sure that I am not following correctly the procedure using Odin and its version or combination of this plus wrong official ROM and so on.
Also have tried to use PIT file because I think something goes wrong with the partitions but not success again,
Would you advice with your steps you follow in order to succeed installing custom recovery.
Can I install only the recovery without ROM and how I can run in it ( button combinations)
For now I am just able to run in Download mode and with one official ROM to run the process to the middle- then goes in error with Odin and when reboot the device it shows message "Firmware upgrade encountered an issue ..... "
Thanks in advance for all answers
Click to expand...
Click to collapse
I have the same problem! There is download mode only - NO recovery, NO rom! ((
I have tried to flash original rom from sammobile via Odin. No results.
Who can help???
uno mas said:
I have the same problem! ((
Who can help???
Click to expand...
Click to collapse
Still do not have the answer and solution.I have start thinking that this is hardware issue. But when i have got it intially from the service it was able to boot in a stock bootloader and I have done something wrong with Odin and since then not able event to go in stock or custom bootloader.
Sent from my LG-D855 using Tapatalk
kafencetu said:
Still do not have the answer and solution.I have start thinking that this is hardware issue. But when i have got it intially from the service it was able to boot in a stock bootloader and I have done something wrong with Odin and since then not able event to go in stock or custom bootloader.
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
In other words - should I go to the service?
uno mas said:
In other words - should I go to the service?
Click to expand...
Click to collapse
If you did not do something with it that makes the warranty not valid it is advisable to send it to service, unfortunatelly I have rooted it and they refused to accept it
Sent from my LG-D855 using Tapatalk
kafencetu said:
If you did not do something with it that makes the warranty not valid it is advisable to send it to service, unfortunatelly I have rooted it and they refused to accept it
Sent from my LG-D855 using Tapatalk
Click to expand...
Click to collapse
SOLVED!!!
http://forum.xda-developers.com/showthread.php?t=2719750
http://forum.xda-developers.com/galaxy-note-10-2014/help/pit-stock-pit-file-thread-t2989266
uno mas said:
I have rooted also. No the warranty. But it doesn't matter if you have a bricked. ((
The Odin starts writing but no finish.
Click to expand...
Click to collapse
yep this is the case , Odin start process of writing and then suddenly - error - in the middle of the procedure.
I have tried to install only custom bootloader - pass successfully ,but then I am not able to go in bootloader mode ( I am trying with Volume down + Power , do not know is that correct - do you have an idea? )
uno mas said:
SOLVED!!!
http://forum.xda-developers.com/showthread.php?t=2719750
http://forum.xda-developers.com/galaxy-note-10-2014/help/pit-stock-pit-file-thread-t2989266
Click to expand...
Click to collapse
Hello uno mas
would you advice what tools you have used and also what order you have follow.
First update PIT and then installed the ROM or other
Thanks in advance for time and efforts!
Guys, my cell phone has version 8.0 stock. Unlocked and installed TWRP (3.2.1.0 and 3.2.1 64bit), it turns out that if I install the Magisk or SuperSu, or even I make any change in the system how to install the Gapps, the system does not start, it is on the screen of the bootloader warning unlocked.
From what I read in the topics would be simple, is it because it is version 8.0? Could someone help me do the root? Just for the record, the phone is not blicker, I reinstalled the stock ROM and blockaded the bootloader again. It is worth informing also that even unlocked and with TWRP installed, however without any changes, the system goes through the warning message of the bootloader unlocked and starts normally.
Just backup system and boot partitions with TWRP to SD card, wipe everything, make format, reboot recovery.
Restore your backup, flash Magisk 16 and f2fs module.
Enjoy your rooted phone
davidsonsjesus said:
Guys, my cell phone has version 8.0 stock. Unlocked and installed TWRP (3.2.1.0 and 3.2.1 64bit), it turns out that if I install the Magisk or SuperSu, or even I make any change in the system how to install the Gapps, the system does not start, it is on the screen of the bootloader warning unlocked.
From what I read in the topics would be simple, is it because it is version 8.0? Could someone help me do the root? Just for the record, the phone is not blicker, I reinstalled the stock ROM and blockaded the bootloader again. It is worth informing also that even unlocked and with TWRP installed, however without any changes, the system goes through the warning message of the bootloader unlocked and starts normally.
Click to expand...
Click to collapse
St.Noigel said:
Just backup system and boot partitions with TWRP to SD card, wipe everything, make format, reboot recovery.
Restore your backup, flash Magisk 16 and f2fs module.
Enjoy your rooted phone
Click to expand...
Click to collapse
In my case, to root stock 8.0, no need to wipe or format anything.
Just backup system and boot partitions with TWRP, and then restore them back to your z2p before flash Magisk.zip. So, no need flash f2fs module, too.
Works like a charm for me.
davidsonsjesus said:
Guys, my cell phone has version 8.0 stock. Unlocked and installed TWRP (3.2.1.0 and 3.2.1 64bit), it turns out that if I install the Magisk or SuperSu, or even I make any change in the system how to install the Gapps, the system does not start, it is on the screen of the bootloader warning unlocked.
From what I read in the topics would be simple, is it because it is version 8.0? Could someone help me do the root? Just for the record, the phone is not blicker, I reinstalled the stock ROM and blockaded the bootloader again. It is worth informing also that even unlocked and with TWRP installed, however without any changes, the system goes through the warning message of the bootloader unlocked and starts normally.
Click to expand...
Click to collapse
NO need wipe anything...
Try it before all:
1: Start Recovery (TWRP)
2: Enter in ADVANCED > TERMINAL
3: Run commands:
echo KEEPVERITY=true>>/data/.magisk
echo KEEPFORCEENCRYPT=true>>/data/.magisk
4: Flash Magisk zip
5: Reboot.
Fabio Feher said:
NO need wipe anything...
Try it before all:
1: Start Recovery (TWRP)
2: Enter in ADVANCED > TERMINAL
3: Run commands:
echo KEEPVERITY=true>>/data/.magisk
echo KEEPFORCEENCRYPT=true>>/data/.magisk
4: Flash Magisk zip
5: Reboot.
Click to expand...
Click to collapse
Not tested by me. But look most simple :fingers-crossed::laugh:
Tkx:fingers-crossed:
Fabio Feher said:
NO need wipe anything...
Try it before all:
1: Start Recovery (TWRP)
2: Enter in ADVANCED > TERMINAL
3: Run commands:
echo KEEPVERITY=true>>/data/.magisk
echo KEEPFORCEENCRYPT=true>>/data/.magisk
4: Flash Magisk zip
5: Reboot.
Click to expand...
Click to collapse
BR:
Muito bom, funcionou perfeitamente aqui!
Me diga: para instalar o xposed, como faço? Só abrir o TWRP e flash o .ZIP? Ou algum desses comandos?
US:
Very good, worked perfectly here!
Tell me: to install xposed, how do I? Just open TWRP and flash the .ZIP? Or any of these commands?
RafaelFUN said:
BR:
Muito bom, funcionou perfeitamente aqui!
Me diga: para instalar o xposed, como faço? Só abrir o TWRP e flash o .ZIP? Ou algum desses comandos?
US:
Very good, worked perfectly here!
Tell me: to install xposed, how do I? Just open TWRP and flash the .ZIP? Or any of these commands?
Click to expand...
Click to collapse
Only flash.
davidsonsjesus said:
Only flash.
Click to expand...
Click to collapse
BR:
Após fazer o root, reinicio o dispositivo, entro no TWRP, flash o .ZIP do framework, reinicio o dispositivo, instalo o xposed installer, só que o app fala que o framework não esta instalado. Como posso fazer?
US:
After doing the root, reboot the device, I go into TWRP, flash the .ZIP of the framework, reboot the device, install the xposed installer, but the app says that the framework is not installed. How can I do it?
RafaelFUN said:
After doing the root, reboot the device, I go into TWRP, flash the .ZIP of the framework, reboot the device, install the xposed installer, but the app says that the framework is not installed. How can I do it?
Click to expand...
Click to collapse
Install the zip from the forum xposed not from the forum Magisk
Mark2014 said:
In my case, to root stock 8.0, no need to wipe or format anything.
Just backup system and boot partitions with TWRP, and then restore them back to your z2p before flash Magisk.zip. So, no need flash f2fs module, too.
Works like a charm for me.
Click to expand...
Click to collapse
Over which 8.0 security patch update you've performed this method? (BTW, recommended by @Junior Passos as well) did you have Xposed flashed and working?...
Sent from my Moto Z2 Play using XDA Labs
The Analog Kid said:
Over which 8.0 security patch update you've performed this method? (BTW, recommended by @Junior Passos as well) did you have Xposed flashed and working?...
Sent from my Moto Z2 Play using XDA Labs
Click to expand...
Click to collapse
i'm no longer use stock anymore.
Mark2014 said:
i'm no longer use stock anymore.
Click to expand...
Click to collapse
Ok... But I was hoping for you to share your stock days experience. Would you, please? If possible?... It still can be helpful.
Sent from my Moto Z2 Play using XDA Labs
The Analog Kid said:
Ok... But I was hoping for you to share your stock days experience. Would you, please? If possible?... It still can be helpful.
Sent from my Moto Z2 Play using XDA Labs
Click to expand...
Click to collapse
I was stayed in stock rom very short time.
Because FireHoundOS is better than stock much.
CLOSED
CLOSED
CLOSED
dl link = e404
kischon said:
dl link = e404
Click to expand...
Click to collapse
thx for reporting, fixed
Good morning !
thanks for sharing and working for our Samsung
sm-g973F/DS
I tried to install the kernel and the rom but I am in a situation where the phone does not react anymore when I want to boot it normall
I can only access in download or twrp mode
The classic start does not react
I tried flashing the official Samsung rom via odin, and tried to install the BLASTUI rom several times but nothing works
I proceeded like this on
twrp (latest version) and vbmeta via odin
I deleted the data, and the custom rom that I had
then I flashed the multidisiabler then the bl and finally the rom
but then impossible to start it normally
the phone does not react and remains black
what should i do please?
@Blast752 can you please consider update your installation instructions using my one below.
I think it's more clear & easy to understand because it took me long time to understand your one.
you could make some changes to it.
I think it will help because lot people seem to get bootloop. maybe they dont follow the right steps
0. Unlock bootloader
Fastboot. long press vol up. unlock (wipe phone)
Reboot connect internet to remove RMM (vaultkeeper) & enable oem unlock again
1. TWRP: Fastboot: Odin Flash TWRP .tar latest from corsicanu (AP) + Avbmeta .tar (CP)
(disable auto reboot)
https://twrp.me/samsung/samsunggalaxys10e.html
https://downloads.corsicanu.ro/samsung/vbmeta-27.10.2020/
After flash finish. Press vol up + bixby + power to force boot straight in TWRP
2. TWRP: Wipe Format data + flash multidisabler zip (to disable encryption/security)
https://forum.xda-developers.com/ga...ynos/g97xf-multi-disabler-encryption-t3919714
3. Install latest bootloader (corsicanu): in Fastboot Odin .tar (BL) or TWRP zip
https://github.com/corsicanu/9820-bootloaders_and_modems
Is bootloader flash necessary now? or before TWRP?
4. Flash BlastUI Rom ZIP in twrp
5. (optional) safetynet fix + thundertweaks app
fatjoez said:
@Blast752 pouvez-vous envisager de mettre à jour vos instructions d'installation en utilisant celles ci-dessous.
Je pense que c'est plus clair et plus facile à comprendre car il m'a fallu beaucoup de temps pour comprendre le vôtre.
vous pouvez y apporter quelques modifications.
Je pense que cela aidera parce que beaucoup de gens semblent avoir le bootloop. peut-être qu'ils ne suivent pas les bonnes étapes
0. Déverrouiller le chargeur de démarrage
Démarrage rapide. appuyez longuement sur le volume vers le haut. déverrouiller (effacer le téléphone)
Redémarrez, connectez-vous à Internet pour supprimer RMM (vaultkeeper) et réactivez le déverrouillage OEM
1. TWRP : Fastboot : Odin Flash TWRP .tar le plus récent de corsicanu (AP) + Avbmeta .tar (CP)
(désactiver le redémarrage automatique)
https://twrp.me/samsung/samsunggalaxys10e.html
https://downloads.corsicanu.ro/samsung/vbmeta-27.10.2020/
Après la finition flash. Appuyez sur vol up + bixby + power pour forcer le démarrage directement dans TWRP
2. TWRP : Wipe Format data + flash multidisabler zip (pour désactiver le cryptage/la sécurité)
https://forum.xda-developers.com/ga...ynos/g97xf-multi-disabler-encryption-t3919714
3. Installez le dernier bootloader (corsicanu) : dans Fastboot Odin .tar (BL) ou TWRP zip
https://github.com/corsicanu/9820-bootloaders_and_modems
Le flash du chargeur de démarrage est-il nécessaire maintenant ? ou avant TWRP ?
4. Flash BlastUI Rom ZIP en twrp
5. (facultatif) correctif du filet de sécurité + application Thundertweaks
Click to expand...
Click to collapse
I followed scrupulously step by step exactly but it does not give me anything. Still inactive and black screen with the possibility of flashing twrp and accessing download mode, but that's it.
I don't know what's wrong ..
is it because I own the G973F / DS?
normally with odin I can catch up with this and flash the Samsung firmware and start over but I am stuck with a black screen that does not react if we want to turn it on normally
FabienGege said:
Good morning !
thanks for sharing and working for our Samsung
sm-g973F/DS
I tried to install the kernel and the rom but I am in a situation where the phone does not react anymore when I want to boot it normall
I can only access in download or twrp mode
The classic start does not react
I tried flashing the official Samsung rom via odin, and tried to install the BLASTUI rom several times but nothing works
I proceeded like this on
twrp (latest version) and vbmeta via odin
I deleted the data, and the custom rom that I had
then I flashed the multidisiabler then the bl and finally the rom
but then impossible to start it normally
the phone does not react and remains black
what should i do please?
Click to expand...
Click to collapse
yeah bro latest magisk canary problem, tomorrow i will upload a version with downgraded magisk (v23 stable)
fatjoez said:
@Blast752 can you please consider update your installation instructions using my one below.
I think it's more clear & easy to understand because it took me long time to understand your one.
you could make some changes to it.
I think it will help because lot people seem to get bootloop. maybe they dont follow the right steps
0. Unlock bootloader
Fastboot. long press vol up. unlock (wipe phone)
Reboot connect internet to remove RMM (vaultkeeper) & enable oem unlock again
1. TWRP: Fastboot: Odin Flash TWRP .tar latest from corsicanu (AP) + Avbmeta .tar (CP)
(disable auto reboot)
https://twrp.me/samsung/samsunggalaxys10e.html
https://downloads.corsicanu.ro/samsung/vbmeta-27.10.2020/
After flash finish. Press vol up + bixby + power to force boot straight in TWRP
2. TWRP: Wipe Format data + flash multidisabler zip (to disable encryption/security)
https://forum.xda-developers.com/ga...ynos/g97xf-multi-disabler-encryption-t3919714
3. Install latest bootloader (corsicanu): in Fastboot Odin .tar (BL) or TWRP zip
https://github.com/corsicanu/9820-bootloaders_and_modems
Is bootloader flash necessary now? or before TWRP?
4. Flash BlastUI Rom ZIP in twrp
5. (optional) safetynet fix + thundertweaks app
Click to expand...
Click to collapse
ok bro thanks
FabienGege said:
I followed scrupulously step by step exactly but it does not give me anything. Still inactive and black screen with the possibility of flashing twrp and accessing download mode, but that's it.
I don't know what's wrong ..
is it because I own the G973F / DS?
normally with odin I can catch up with this and flash the Samsung firmware and start over but I am stuck with a black screen that does not react if we want to turn it on normally
Click to expand...
Click to collapse
change kernel or use stock one, latest magisk canary versions gives problems with samsung atm
Blast752 said:
ouais bro dernier problème magisk canary, demain je téléchargerai une version avec magisk rétrogradé (v23 stable)
Click to expand...
Click to collapse
Will it be a zip flashed via twrp?
In your opinion why this blocked with my Samsung (SM-G973F / DS).
THANKS SO MUCH FOR SHARING YOUR KNOWLEDGE!
Blast752 said:
changer le noyau ou utiliser un stock, les dernières versions de magisk peuvent résoudre des problèmes avec samsung atm
Click to expand...
Click to collapse
I will go through the process by changing the kernel several times.
staying of course with the g973 kernels.
I'll keep you informed .
thank you for your speed
FabienGege said:
I will go through the process by changing the kernel several times.
staying of course with the g973 kernels.
I'll keep you informed .
thank you for your speed
Click to expand...
Click to collapse
Did you change kernel? Problem fixed?
If it fix please share instructions & link kernel used
fatjoez said:
Did you change kernel? Problem fixed?
If it fix please share instructions & link kernel used
Click to expand...
Click to collapse
Hello .
I tried several different kernels in g973F ..... some wont flash others yes, but that didn't fix the problem.
I still now have access to the loading screen when the phone is off, but I still can't turn it on.
only download mode and i can flash twrp to access it but that's it.
I succeeded !! My phone works after several days of hard work !!!
I am very happy!
I followed fatjoez's links for vmbeta and multidisiabler and it worked!
Many thanks for the links !!
resolu .
FabienGege said:
J'ai réussi !! Mon téléphone fonctionne après plusieurs jours de travail acharné !!!
Je suis très heureux!
J'ai suivi les liens de fatjoez pour vmbeta et multidisiabler et ça a marché !
Merci beaucoup pour les liens !!
résolu.
Click to expand...
Click to collapse
The rom and excellent but the phone restarts itself
FabienGege said:
I succeeded !! My phone works after several days of hard work !!!
I am very happy!
I followed fatjoez's links for vmbeta and multidisiabler and it worked!
Many thanks for the links !!
resolu .
Click to expand...
Click to collapse
great
can you please post the exact instructions for how you fix it so other people can recover too?
which steps did you follow & which buttons pressed ~~
Start in download mode via the volume button - and bixby while plugging it into my pc.
I flashed the last twrp and the Vmbeta with Fat Joez links (disable reboot on Odin)
Then volume - bixby and power then once the screen is off volume + bixby and power at the same time.
On twrp Factory data reset.
Flashed multidisiabler to twrp, reboot to twrp.
Then flash the rom, wipe data and reboot the system