{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hey guys! Paranoid Android is finally back!
Here I built a first release to share with you. The rom is based on AOSP sources, Paranoid code and Cyanogenmod stability fixes, plus other things hand-written for S6 good compatibility. Now stop talking and enjoy Paranoid!
Disclaimer:
I take no responsibility for lost data, broken devices or anything else you encountered
during/after flashing this ROM.
You are responsible for what you are using on your devices!
Do some research before doing anything and always make sure to have a backup!
Click to expand...
Click to collapse
NOTE: This ROM is based on AOSP. So make sure you follow exactly the steps I write to install.
Download:
Mod Edit
Link removed
Bugs:
some lags, camera starts 50% of times, frame drops here and there playing videos.
Steps:
flash 5.1.1 with odin (cause of bootloader)
flash paranoid (gapps not now, it won't boot!)
reboot
back to recovery
system and cache wipe
flash gapps
reboot
Credits:
Paranoid Android team
CyanogenMod team
Slim team (AOSP-CAF)
tdcfpp
Sources:
Exynos
And some personal fixes I'm still working on
XDA:DevDB Information
Paranoid Android, ROM for the Samsung Galaxy S6
Contributors
Tonylel
ROM OS Version: 6.0.x Marshmallow
Based On: AOSP
Version Information
Status: Beta
Created 2016-07-29
Last Updated 2016-07-29
hey man. I am willing to test this ROM, but you are telling us to flash android 5.1.1 to our phone? I mean, the title is saying that It is Android 6.0.1?
I am willing to test this rom too. But we have bootloader for android 6 and we cannot flash back to bootloader 5.1.1. How can we flash this Rom exactly? Which bootloader exatly do you mean??
Gesendet von meinem SM-G925F mit Tapatalk
alfo2004 said:
I am willing to test this rom too. But we have bootloader for android 6 and we cannot flash back to bootloader 5.1.1. How can we flash this Rom exactly? Which bootloader exatly do you mean??
Click to expand...
Click to collapse
Mr.pakkis said:
hey man. I am willing to test this ROM, but you are telling us to flash android 5.1.1 to our phone? I mean, the title is saying that It is Android 6.0.1?
Click to expand...
Click to collapse
You need to flash the stock Android 5.1.1 Rom with Odin because you cant flash the cm 13 Rom over an Android M bootloader (kernel not seandroid enforcing)
Tonylel said:
You need to flash the stock Android 5.1.1 Rom with Odin because you cant flash the cm 13 Rom over an Android M bootloader (kernel not seandroid enforcing)
Click to expand...
Click to collapse
Doesn't exactly make sense that it says Kernel not seandroid enforcing, when its a bootloader problem, and the fact that he is calling it a 6.0.1 ROM, when he asks us to DOWNgrade. I mean, what about all the 6.0.1 functions? Will we loose them? Like doze etc..
Woah, nice one, out of nowhere.
How did you get the camera partially working? Hopefully your hard work can help our progress with this device.
Any links for a SM-g925F 5.1.1 file?
holy ****. amazing
too bad i cant flash it cuz my chqrging port is broken..and odin dsnt recognize my phone anymore((
Tonylel said:
Steps:
flash 5.1.1 with odin (cause of bootloader)
flash paranoid (gapps not now, it won't boot!)
reboot
back to recovery
system and cache wipe
flash gapps
reboot
Click to expand...
Click to collapse
These steps make no sense. Why would you flash paranoid and later wipe the system to flash gapps.. ? When you wipe system the paranoid will be gone too.
Btw the install is taking ages..stuck at "patching system image unconditionally" for like an half hour..
I cant downgrade. Any help guys? it fails at the NAND write start...
Mr.pakkis said:
I cant downgrade. Any help guys? it fails at the NAND write start...
Click to expand...
Click to collapse
Just flash the 5.1.1 bootloader for 925f
In Odin flash it under BL
What about fingerprint?
Quintz said:
Just flash the 5.1.1 bootloader for 925f
In Odin flash it under BL
Click to expand...
Click to collapse
Its really hard to find a link. Do you have one?
Mr.pakkis said:
Its really hard to find a link. Do you have one?
Click to expand...
Click to collapse
I already gave you the link -.- => Click on the "925f"
Quintz said:
I already gave you the link -.- => Click on the "925f"
Click to expand...
Click to collapse
xD sorry, didnt see it. I tried, but when I try to use the choose the file, I get an error saying md5 error! Binary is invalid
What to do now...? Can I perhaps try to flash it under AP?
Edit; It doesnt work underneath AP.
Mr.pakkis said:
xD sorry, didnt see it. I tried, but when I try to use the choose the file, I get an error saying
What to do now...? Can I perhaps try to flash it under AP?
Edit; It doesnt work underneath AP.
Click to expand...
Click to collapse
Reason why you get the error is because you need the delete the .md5 extension from the name just to be .tar. Anyway dont risk it and flash the bootloader i post now.
1. Are you sure you have a 925F not 925I or something.
2.Try this bootloader: https://www.androidfilehost.com/?fid=24052804347786560
I wonder if you can install the rom because for my its busy installing for 30+ min.
Quintz said:
Reason why you get the error is because you need the delete the .md5 extension from the name just to be .tar. Anyway dont risk it and flash the bootloader i post now.
1. Are you sure you have a 925F not 925I or something.
2.Try this bootloader: https://www.androidfilehost.com/?fid=24052804347786560
I wonder if you can install the rom because for my its busy installing for 30+ min.
Click to expand...
Click to collapse
I am 100% positive I have a 925F. Used tons of ROMs, flashed kernels and generally changing stuff on my phone. After flashing the bootloader, should I boot into the recovery and install the ROM?
Not working
I have tried flashing this rom for like 5 times. Every time it get stuck on this:
"patching system image unconditionally"
What I did was:
- Install Lollipop
- Root
- TWRP Recovery
- Flash Rom
I will request you to please provide more detailed steps.
Well, I think that the developer should add support for the 6.0.1 bootloader...
---------- Post added at 07:28 PM ---------- Previous post was at 07:25 PM ----------
Also didnt work either. In the corner of the download side its written SW REV. CHECK FAIL. DEVICE: 3, BINARY: 2
Yes guys you can just flash bootloader 5.1.1 only. This allows aosp flash, it won't downgrade to 5.1.1, the flash will UPGRADE to 6.0.1 later.
For those who have some problem while flashing try perform a full wipe (system/cache/dalvik) and if still persist try change/update your recovery.
Right, I forgot: fingerprint not working because really no sources for that.
Related
Hi Everyone,I Have Deodexed & Zipaligned Z3's 4.4.4 23.0.A.2.105 Firmware
This Was Meant For The Single Sim Of Xperia™ Z3 With The Model Number D6603 Or D6653
Requirements
Unlocked Bootloader Currently
Rooted
CWM Recovery
After The Root Will Work On Locked Bootloader,You Can Also Flash This On Your Z3 With Locked Bootloader
You Will Need To Have A Rooted ROM With CWM Recovery
You Must Be On This Firmware (.105) To Flash It
Please Note That The Zip Only Contained System App,Framework & Priv-App
It Was Recommended To Flash This Zip On A Generic Firmware That Doesn't Contain Carrier Apps
The Odex File Will Be Deleted During The Installation & The Carrier App May Not Work Properly Because This Is Based On Generic Firmware
Installation:
1.Download The Zip & Move It To Your Phone
2.Boot Into CWM Recovery & Flash It
3.Clear Cache & Dalvik Cache
4.Done
Download:
Deodexed & Zipaligned 4.4.4 23.0.A.2.93 Firmware ( 520.3 MB )
Deodexed & Zipaligned 4.4.4 23.0.A.2.105 Firmware ( 524.8 MB )
Credits:
laguCool
RyokoN
Hit
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If I Helped You
@Ben Ling
would it be better if u could state which customization version u have de-odex from?
chunlianghere said:
@Ben Ling
would it be better if u could state which customization version u have de-odex from?
Click to expand...
Click to collapse
Generic UK
Btw there's is no any carrier apps in the zip & all Generic ROM have the same apk & jar files
It may be worthwhile to put that in the requirements it does not need an unlocked bootloader, only root and recovery. I know currently you cannot have either of these without an unlocked bootloader, but soon (Finger crossed) we will get root without having to unlock.
Greg
gregbradley said:
It may be worthwhile to put that in the requirements it does not need an unlocked bootloader, only root and recovery. I know currently you cannot have either of these without an unlocked bootloader, but soon (Finger crossed) we will get root without having to unlock.
Greg
Click to expand...
Click to collapse
yep I knew that but for now there is no way to root it on locked bootloader...
can you please get one for D6633
. .
Is it compatible with single SIM D6643 variant?!
Fatadxb said:
can you please get one for D6633
Click to expand...
Click to collapse
+1.
^^ a great opportunity to learn!! in the cross dev sony thread there is tool and instructions to convert ftf into deodexed flashable (I don't code but created these for Z Ultra) Ill go find the threads and post and you can easily make your own (ro save @Ben Ling doing exact same thing)
http://forum.xda-developers.com/showthread.php?t=2713329
[TOOL] Kamome tool for Windows - deodex tool for 4.4 KitKat
edit: sry, cannot find ftf conversion thread ~ from memory; unzip ftf, unpack system (the tricky bit, needs software), then kanome tool ~ will have to find proper instructions as this helps nobody lol
Sent from my D6653 using Tapatalk
Can this be installed with the TWRP recovery? Or do I need to have CWM recovery?
Im gonna open my bootlader and I am unsure on witch of the rooting alternatives I should use. Im used to TWRP from other phones, but I have also used CWM sometimes, aaaaaaah the choiches
Dirtyzecret said:
Can this be installed with the TWRP recovery? Or do I need to have CWM recovery?
Im gonna open my bootlader and I am unsure on witch of the rooting alternatives I should use. Im used to TWRP from other phones, but I have also used CWM sometimes, aaaaaaah the choiches
Click to expand...
Click to collapse
You can use the one you like
^^ if you use DoomLord cwm boot for root then flash AndroPlus kernel afterwards you actually end up with both cwm AND twrp (ftw)
Updated to .105
Hi,
I need help !! I own a D6603 Z3 model (with global generic firmware .93).
I unlocked the bootloader, then flash C.W.M recovery, then i flash this .105 de-odexed firmware, wipe cache and dalvik cache and finally, rebooting the phone.
But instead of the set up screen, i have a black screen with a blue line who shows up every 2 seconds at the bottom of the screen and i can't do anything !!
What am i missing ? I precise that i'm not a noob for flashing xperias phone.
P.S : I didn't make a backup before flashing cause i forgot, and flashtool doesn't works for Z3 yet so i can't flash any FTF Files.... :-/
flashtool works fine
gregou said:
Hi,
I need help !! I own a D6603 Z3 model (with global generic firmware .93).
I unlocked the bootloader, then flash C.W.M recovery, then i flash this .105 de-odexed firmware, wipe cache and dalvik cache and finally, rebooting the phone.
But instead of the set up screen, i have a black screen with a blue line who shows up every 2 seconds at the bottom of the screen and i can't do anything !!
What am i missing ? I precise that i'm not a noob for flashing xperias phone.
P.S : I didn't make a backup before flashing cause i forgot, and flashtool doesn't works for Z3 yet so i can't flash any FTF Files.... :-/
Click to expand...
Click to collapse
I guess you are not on .105 firmware to flash this.
I forgot to edit the OP as I just updated to .105 build,so there wrote that you must be on .93 firmware.
Actually you will need to be on the same firmware to flash it in case anything goes wrong.
For now you can only reflash firmware using flashtool.
Ben Ling said:
I guess you are not on .105 firmware to flash this.
I forgot to edit the OP as I just updated to .105 build,so there wrote that you must be on .93 firmware.
Actually you will need to be on the same firmware to flash it in case anything goes wrong.
For now you can only reflash firmware using flashtool.
Click to expand...
Click to collapse
Thanks a lot for your replies, i dowloaded the latest version of flashtool as i had an old version and i managed to get back to stock.
I unlocked again, rooted and that's good for me now, even if i'm still odexed.
Just hoping now that some devs will bring us some custom rom cause it's quite sad to own this amazing phone and have no custom rom to play with...
Thanks anyway for your work on this de-odexed rom !
totally agree
and stock is a blown up piece of ****
Alex3oe said:
totally agree
and stock is a blown up piece of ****
Click to expand...
Click to collapse
I'd rather be on Sony's stock firmware (which i like by the way) than Touchwizz rom !! But i like custom rom as i can modify whatever i want Also, something great would be to get some mods for camera (higher bitrate video for example) and mods for audio... Fingers crossed !
So I flashed latest firmware of lollipop thru ODIN lollipop everything went smooth, New Stock Lollipop rom flashed and everything was perfect......... Now the problem I rooted using cf autoroot that went well, Flashed Twrp, But when I try to restore any backup roms they bootloop...... Try to flash any new roms, Bootloop, So my question is ? Does the new bootloader new the stock kernel for this to work ? and once we flash this are we not able to flash any 4.4.2 roms since it won't have the 5.0 kernel ??
Hopefully I did something wrong ??? But who else that has flashed full firmware or bootloader been able to flash any other roms after ?????
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I am having the same problem, im not able to flash any ASOP roms (bootloops) but touchwiz i can flash without a problem.
idk if it has to do something with the bootloader or not. i also flashed the full stock .tar
eventheodds1 said:
I am having the same problem, im not able to flash any ASOP roms (bootloops) but touchwiz i can flash without a problem.
idk if it has to do something with the bootloader or not. i also flashed the full stock .tar
Click to expand...
Click to collapse
Is not even letting me flash touchwiz roms....... Which one have you tried that's worked for you ??? I keep getting stuck on bootloops with any 4.4.2 rom that I try I even tried Xtrelight or whatever the internation one and i can't get it to past the samsung logo.............. Just flashed the full firmware again and stock rom loads just fine...... How did you get root when you flashed 5.0 did you flash the old 4.4.2 cf autoroot ???
@gdmlaz i let the stock tar boot up than moved flash version of vision in the sdcard, used odin and flashed phliz. After doing so, wipe cache+data, than flashed vision. Read the instructions clearly or else you won't have mobile data! hope that helps!
[ROM]ViSiON-X US TMO[Android L 5.0][G900TUVU1DOB1][02-18-15]
eventheodds1 said:
@gdmlaz i let the stock tar boot up than moved flash version of vision in the sdcard, used odin and flashed phliz. After doing so, wipe cache+data, than flashed vision. Read the instructions clearly or else you won't have mobile data! hope that helps!
[ROM]ViSiON-X US TMO[Android L 5.0][G900TUVU1DOB1][02-18-15]
Click to expand...
Click to collapse
So you just flashed recovery before rooting ??? I'll try that this time, I usually root before try to flashing a recovery in the past it has not stuck around
gdmlaz said:
So you just flashed recovery before rooting ??? I'll try that this time, I usually root before try to flashing a recovery in the past it has not stuck around
Click to expand...
Click to collapse
yep, flashing phliz will trip your knox tho
eventheodds1 said:
yep, flashing phliz will trip your knox tho
Click to expand...
Click to collapse
My knox has been tripped for years lol
gdmlaz said:
My knox has been tripped for years lol
Click to expand...
Click to collapse
hahaha, i always flash recovery (via odin) than flash the rom, which most (if not all) coming with superSU and root access.
im just little ticked off I get stuck on bootloop for ASOP roms tho :l I'm not big fan of touchwiz.
eventheodds1 said:
hahaha, i always flash recovery (via odin) than flash the rom, which most (if not all) coming with superSU and root access.
im just little ticked off I get stuck on bootloop for ASOP roms tho :l I'm not big fan of touchwiz.
Click to expand...
Click to collapse
Still stuck on bootloops....... whenever I try to flash anything using ktoonz twrp Ugghhhh sooo annoying only thing I get to work is just stock rom when i fully flash the firmware file thru odin..... Going to try to restore an old 4.4.2 rom see if this even boots up..... I'm getting close to giving up
gdmlaz said:
Still stuck on bootloops....... whenever I try to flash anything using ktoonz twrp Ugghhhh sooo annoying only thing I get to work is just stock rom when i fully flash the firmware file thru odin
Click to expand...
Click to collapse
try using philz touchwiz, i dont think that would make a difference but it's worth a shot!
Also if you flashed the rom, vision, than it takes a good solid 10min!
eventheodds1 said:
try using philz touchwiz, i dont think that would make a difference but it's worth a shot!
Also if you flashed the rom, vision, than it takes a good solid 10min!
Click to expand...
Click to collapse
Yea I used vision before and used to work fine....... I been trying to flash regular 4.4.2 and none of them get past the samsung boot screen before it bootloops all over again..... Which philz version are you using I'm willing to try anything at this point lol
gdmlaz said:
Yea I used vision before and used to work fine....... I been trying to flash regular 4.4.2 and none of them get past the samsung boot screen before it bootloops all over again..... Which philz version are you using I'm willing to try anything at this point lol
Click to expand...
Click to collapse
try the 5.0 lollipop, seems like you already have 5.0 bootloader
eventheodds1 said:
try the 5.0 lollipop, seems like you already have 5.0 bootloader
Click to expand...
Click to collapse
Yea this is my problem the stupid 5.0 bootloader doesn't let me do anything for some reason............... Not even my backups load a soon as i try to restart my phone to load them phone goes into bootloop and nothing works...... I guess I'll just use the stock firmware file till somebody figures out what to do
I'm guessing it has to be with the Bootloader tied down to the stock tmobile 5.0 Kernel........... Since the only thing that loads up is the full firmware
If you guys are trying to revert back to previous version of kitkat coming from lollipop using custom recovery, it will fail. You will have to downgrade with pc odin to a previous kitkat full stock firmware and then reroot. You can not flash kitkat over lollipop, it will fail and bootloop. If you are trying to upgrade to tmo lollipop and then try to restore a asop lollipop rom, it will fail as well. Asop lollipop roms are based off international roms and will not play well with tmo lollipop.
galaxyuser88 said:
If you guys are trying to revert back to previous version of kitkat coming from lollipop using custom recovery, it will fail. You will have to downgrade with pc odin to a previous kitkat full stock firmware and then reroot. You can not flash kitkat over lollipop, it will fail and bootloop.
Click to expand...
Click to collapse
Well that sucks......... The most I got accomplished so far is flash stock firmware/flash twrp recovery/ root it.................. I will make a backup of this on twrp and try to flash another costum rom see if that works but last time I tried XtreStoLite Internation version 5.0 and still got me stuck on the same bootloop ??
galaxyuser88 said:
If you guys are trying to revert back to previous version of kitkat coming from lollipop using custom recovery, it will fail. You will have to downgrade with pc odin to a previous kitkat full stock firmware and then reroot. You can not flash kitkat over lollipop, it will fail and bootloop. If you are trying to upgrade to tmo lollipop and then try to restore a asop lollipop rom, it will fail as well. Asop lollipop roms are based off international roms and will not play well with tmo lollipop.
Click to expand...
Click to collapse
is there anything we can flash inorder to fix the bootloop? for example i flashed stock tar for kit-kat tar, to see if i could flash ASOP lollipop roms. i still get stuck on bootloop?
eventheodds1 said:
is there anything we can flash inorder to fix the bootloop? for example i flashed stock tar for kit-kat tar, to see if i could flash ASOP lollipop roms. i still get stuck on bootloop?
Click to expand...
Click to collapse
From what I remember in the past you weren't able to go back to an older firmware ??? Unless things have changed ?
I think issue we are having is a kernel issue....... Boot-loader is looking for stock 5.0 kernel and we don't have it when we flash any other rom
gdmlaz said:
From what I remember in the past you weren't able to go back to an older firmware ??? Unless things have changed ?
I think issue we are having is a kernel issue....... Boot-loader is looking for stock 5.0 kernel and we don't have it when we flash any other rom
Click to expand...
Click to collapse
you are right you can't go back firmware, i forgot :l so we just have to wait for someone to make flashable kernel that will make it work?
This is one reason why dev always say to wait before you take or do any update that drops from carriers. They will see if it is rootable or if it will lock you down.
Now some people dont care about being able to root or just cant wait for a dev to say it is ok. If you can not downgrade to a previous version using pc odin, then you are stuck untill on of the devs figures this out. Please be careful, search and read before taking any update.
eventheodds1 said:
you are right you can't go back firmware, i forgot :l so we just have to wait for someone to make flashable kernel that will make it work?
Click to expand...
Click to collapse
You can go back. I took the ota update to 5.0 and messed up trying to root so odin'd back to KitKat and then took the update again. I odin'd Phil's touch used that to flash the latest twrp from ktoonsez and then flashed root. Haven't tried flashing aosp yet.
Hi everybody,
I have flash G925FXXS4DPG2 Rom by Odin.
No problem but if i want downgrade in G925FXXS3DPF1 its fail at Sboot.bin flash.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Here is an exemple with 3DPDP but with 3DPF1 its the same...
So no more downgrade possible after Flash 4Dxxx Rom. Impossible to return in 3Dxxxx.
If i try to flash 4PDG2 again, no issue with Odin, flash succes... So its not Odin neighter cable or phone problem....
If i restore my Nandroid Backup to return on my Custom Rom base 3DPDP, unknow baseband, so no more IMEI, even if i flash 3Dxxxx Modem and BL.
Does someone have an idea ?
edzamber said:
Hi everybody,
I have flash G925FXXS4DPG2 Rom by Odin.
No problem but if i want downgrade in G925FXXS3DPF1 its fail at Sboot.bin flash.
Here is an exemple with 3DPDP but with 3DPF1 its the same...
So no more downgrade possible after Flash 4Dxxx Rom. Impossible to return in 3Dxxxx.
If i try to flash 4PDG2 again, no issue with Odin, flash succes... So its not Odin neighter cable or phone problem....
Does someone have an idea ?
Click to expand...
Click to collapse
azzzzzzz ! it's not possible the downgrade?!?!!? this is very strange ,,,,,,,,,,,,, i cant help you, sorry my friend ..
it seems a new android version like a new cake
edzamber said:
Hi everybody,
I have flash G925FXXS4DPG2 Rom by Odin.
No problem but if i want downgrade in G925FXXS3DPF1 its fail at Sboot.bin flash.
Here is an exemple with 3DPDP but with 3DPF1 its the same...
So no more downgrade possible after Flash 4Dxxx Rom. Impossible to return in 3Dxxxx.
If i try to flash 4PDG2 again, no issue with Odin, flash succes... So its not Odin neighter cable or phone problem....
Does someone have an idea ?
Click to expand...
Click to collapse
Samething happening on note 5 tmo new update N920TUVU3DPG1 we on same boat
Sent from my Samsung SM-N920T using XDA Labs
Carotix said:
azzzzzzz ! it's not possible the upgrade?!?!!? this is very strange ,,,,,,,,,,,,, i cant help you, sorry my friend ..
it seems a new android version like a new cake
Click to expand...
Click to collapse
I don't know but look, it seems that there is a secondary locked BL...
JonathanRAZ said:
Samething happening on note 5 tmo new update N920TUVU3DPG1 we on same boat
Sent from my Samsung SM-N920T using XDA Labs
Click to expand...
Click to collapse
Yes it seems to be the same problem...
edzamber said:
I don't know but look, it seems that there is a secondary locked BL...
Click to expand...
Click to collapse
Sent from my Samsung SM-N920T using XDA Labs
Hi all
Ok, some news :
As you can't downgrade, you can also restore a Nandroid Backup from TWRP to come back in older base, but you need new BL and Modem 4Dxxx to have baseband and imei. This is the only solution.
If you brick your phone, or need to come back on Official Samsung Firmware, as BL is blocked, only 4Dxxxx official Firmware can be flash by Odin
Here are my TWRP flashable zip and Odin tar for BL and Modem 4DPG2
Only for G925F
flashable TWRP Zip
http://www.mediafire.com/?06ylnww3q4s2s6c
Odin TAR Version
http://www.mediafire.com/?z79kna8k9x4zyv1
Only for G920F
flashable TWRP Zip
http://www.mediafire.com/?sb0bh7560q2626r
Odin TAR Version
http://www.mediafire.com/?87ts10pr0dcrmb6
@edzamber Can i change base secsettings2.apk ??? thx men
elkinguerrabarreto said:
@edzamber Can i change base secsettings2.apk ??? thx men
Click to expand...
Click to collapse
What do you mean ?
edzamber said:
What do you mean ?
Click to expand...
Click to collapse
I using s6 edge g925I. i have a settings2.apk modified but of a rom G925F, when change manually the file with root explore, show spaces, i think it is the rom base
elkinguerrabarreto said:
I using s6 edge g925I. i have a settings2.apk modified but of a rom G925F, when change manually the file with root explore, show spaces, i think it is the rom base
Click to expand...
Click to collapse
This is Off Topic, but i use a modified SecSettings2 from an another base and working fine...
edzamber said:
This is Off Topic, but i use a modified SecSettings2 from an another base and working fine...
Click to expand...
Click to collapse
OK, but what do I do to remove spaces with secsetting2 from G925F
elkinguerrabarreto said:
OK, but what do I do to remove spaces with secsetting2 from G925F
Click to expand...
Click to collapse
PM me with a screenshot please
edzamber said:
PM me with a screenshot please
Click to expand...
Click to collapse
View attachment 3816551
this is bug
elkinguerrabarreto said:
this is bug
Click to expand...
Click to collapse
By PM mate, this is Off Topic, nothing to do Here.
Thanks.
so...no chance to flash lollipop stock now )
i want it for 925i model
Sent from my SM-G925I using XDA-Developers mobile app
edzamber said:
Hi all
Ok, some news :
As you can't downgrade, you can also restore a Nandroid Backup from TWRP to come back in older base, but you need new BL and Modem 4Dxxx to have baseband and imei. This is the only solution.
If you brick your phone, or need to come back on Official Samsung Firmware, as BL is blocked, only 4Dxxxx official Firmware can be flash by Odin
Here are my TWRP flashable zip and Odin tar for BL and Modem 4DPG2
Only for G925F
flashable TWRP Zip
http://www.mediafire.com/?06ylnww3q4s2s6c
Odin TAR Version
http://www.mediafire.com/?z79kna8k9x4zyv1
Only for G920F
flashable TWRP Zip
http://www.mediafire.com/?sb0bh7560q2626r
Odin TAR Version
http://www.mediafire.com/?87ts10pr0dcrmb6
Click to expand...
Click to collapse
This worked perfectly for me. After 2 days of non-stop experiment nothing worked. This file did the work. I'm using G925F.
Thank you so much.
edzamber said:
Hi all
Ok, some news :
As you can't downgrade, you can also restore a Nandroid Backup from TWRP to come back in older base, but you need new BL and Modem 4Dxxx to have baseband and imei. This is the only solution.
If you brick your phone, or need to come back on Official Samsung Firmware, as BL is blocked, only 4Dxxxx official Firmware can be flash by Odin
Here are my TWRP flashable zip and Odin tar for BL and Modem 4DPG2
Only for G925F
flashable TWRP Zip
http://www.mediafire.com/?06ylnww3q4s2s6c
Odin TAR Version
http://www.mediafire.com/?z79kna8k9x4zyv1
Only for G920F
flashable TWRP Zip
http://www.mediafire.com/?sb0bh7560q2626r
Odin TAR Version
http://www.mediafire.com/?87ts10pr0dcrmb6
Click to expand...
Click to collapse
Which the steps are to continue? could a small guide make? I am in the g920fxxs4dpg2
DanyzoO said:
Which the steps are to continue? could a small guide make? I am in the g920fxxs4dpg2
Click to expand...
Click to collapse
That's all mate, just flash BL 4DPG2 for your model phone by Odin in AP
Then flash 4DPxxxx ROM by Odin.
If you need to restore a Custom Rom in 3Dxxx Rom, just restore it then flash BL 4DPG2 by TWRP Recovery.
Tutorial for replacing the original KERNEL with your PREFERED one in boot.img!
I did this image's tutorial for the users wich want to change the original kernel of the rom with his prefered kernel
You ned a pc runing with windows XP,7,8,10
Download the "Android Image Kitchen from here
and follow the instruction writed in image's
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Next image's are for help you to install the new "image-new.img"(boot.img) on the phone with TWRPrecovery
Atention!
MAKE FIRST A BACKUP before install the ROM and the NEW boot.img
Use only boot.img's for J5xxx/2015 for j5/2015 phones or boot.img's j510xx/2016 for j5/2016 phones
DONT edit/change the RAMDISK files without necesarry knowledge(DONT TOUCH IT!)
USE the SAME android version 5.1.1=>5.1.1 or 6.0.1=>6.0.1 for the boot.img's
DONT report bug's(if you find it) to the DEVELOPPER of the ROM(Will not be take in CONSIDERATION)
You will NOT BRIK te phone IF you RESPECT all the instruction and first 4 LINES from "ATENTION!"(IF you are not shure on your hand DONT DO IT!)
IF the changed file are NOT MATCH you will get a BOOTLOP! so you can try other files from other boot.img
ENJOY by your PREFFERED KERNEL
Thanks!
How to fix WIFI after the replacement!
After you change the Kernel, you can get the WIFI not working!
To fix that you need to have ROOT(SU rights) on the phone
and follow the image's and instruction writed it it
reserved
reserved
Q: How to boot stock 5.1.1 on new bootloader?
I know how to compile odin images, so i can flash stock 5.1.1 on 6 bootloader with odin.
MaDaLiNoSt said:
Q: How to boot stock 5.1.1 on new bootloader?
I know how to compile odin images, so i can flash stock 5.1.1 on 6 bootloader with odin.
Click to expand...
Click to collapse
So, you want to put stok rom 5.1.1 on 6.0.1 botloader!
first you must modify the boot.img replacing the "dtb"(5.1.1) file with the one from stok boot.img(6.0.1)
with ODIN can work or not becouse ODIN chech the version of each file before flashing, but you can try!
after you modify the boot.img, extract the system.img.ext4(5.1.1) file from stok rom.md5
put the new boot.img and the system.img.ext4 in a .tar archive and try to flash it with ODIN
you will have succes or can fail(becouse of ODIN)
also you can use the superRkitchen in linux to compile the rom to be flashed it with TWRP
that "dtb"(6.0.1) file will help you to pass the boot of a 5.1.1 rom on 6.0.1 botloader
that will work becouse i already did it with my ported roms
if you dont know hou to compile the rom with superRkitchen just tell me and i will guide you!
vaserbanix said:
so, you want to put stok rom 5.1.1 on 6.0.1 botloader!
First you must modify the boot.img replacing the "dtb"(5.1.1) file with the one from stok boot.img(6.0.1)
with odin can work or not becouse odin chech the version of each file before flashing, but you can try!
After you modify the boot.img, extract the system.img.ext4(5.1.1) file from stok rom.md5
put the new boot.img and the system.img.ext4 in a .tar archive and try to flash it with odin
you will have succes or can fail(becouse of odin)
also you can use the superrkitchen in linux to compile the rom to be flashed it with twrp
that "dtb"(6.0.1) file will help you to pass the boot of a 5.1.1 rom on 6.0.1 botloader
that will work becouse i already did it with my ported roms
if you dont know hou to compile the rom with superrkitchen just tell me and i will guide you!
Click to expand...
Click to collapse
oh my god ! I am so excited now.
I booted into 5.1.1 back :d:d:d:d:d:d
Edit: I leave it for 10 mins in boot animation... if not pass=bootloop
after 10 mins================Fail, why??
MaDaLiNoSt said:
oh my god ! I am so excited now.
I booted into 5.1.1 back :d:d:d:d:d:d
Click to expand...
Click to collapse
you are blocked in 6.0.1 botloader?
i understand you flashed the rom with success! i'm happy for you!
i beleve that process can be done and vice versa to flash a 6.0.1 rom on a 5.1.1 botloader(i didnt test it yet)
also it can be done with any custom rom BUT becouse we dont have here custom boot.img(6.0.1) except the one from Skies ROM by @BlackMesa123 or of @KingRaheel wich give up the project, the posibilities are limited for now, maybe in the near future
BUT(becouse all the time can be a BUT) can be tryed wiht the "dtb" file from stok rom's on custom rom's
Thanks!
MaDaLiNoSt said:
oh my god ! I am so excited now.
I booted into 5.1.1 back :d:d:d:d:d:d
Edit: I leave it for 10 mins in boot animation... if not pass=bootloop
after 10 mins================Fail, why??
Click to expand...
Click to collapse
do you have a backup of 5.1.1 stok rom?
if yes, restore the backup and then install the boot.img and reboot
or try the dtb file from King Raheel boot.img (6.0.1) or other custom (6.0.1) boot.img,
i worked with custom files not with stok, that can have some securities in it
vaserbanix said:
do you have a backup of 5.1.1 stok rom?
if yes, restore the backup and then install the boot.img and reboot
or try the dtb file from King Raheel boot.img (6.0.1) or other custom (6.0.1) boot.img,
i worked with custom files not with stok, that can have some securities in it
Click to expand...
Click to collapse
i tried even with DJ STEEVE :no luck
MaDaLiNoSt said:
i tried even with DJ STEEVE :no luck
Click to expand...
Click to collapse
on stok rom can be guilty the KNOX, CSC.
for me on custom rom work DJ Steve file
try my Slim Stok rom, is deKNOXed, deBloated, rooted etc, for FN
https://forum.xda-developers.com/galaxy-j5/development/romstock-modified-sm-j500fn-t3317737
ps. try to make a logcat
vaserbanix said:
you are blocked in 6.0.1 botloader?
i understand you flashed the rom with success! i'm happy for you!
i beleve that process can be done and vice versa to flash a 6.0.1 rom on a 5.1.1 botloader(i didnt test it yet)
also it can be done with any custom rom BUT becouse we dont have here custom boot.img(6.0.1) except the one from Skies ROM by @BlackMesa123 or of @KingRaheel wich give up the project, the posibilities are limited for now, maybe in the near future
BUT(becouse all the time can be a BUT) can be tryed wiht the "dtb" file from stok rom's on custom rom's
Thanks!
Click to expand...
Click to collapse
Actually my kernel in skies is djsteve one with ramdisk edit for boot note7 rom lol. Btw bro I don't understand the guide.. why replace the kernel binaries when you can just use the boot.img lol
This i did on custom rom, on stok rom can work just to replace all boot.img
on stok rom's the ramdisk can be the same or almost the same and rom can boot
but on custom every rom has his ramdisk wich not work on other
Thanks!
vaserbanix said:
This i did on custom rom, on stok rom can work just to replace all boot.img
on stok rom's the ramdisk can be the same or almost the same and rom can boot
but on custom every rom has his ramdisk wich not work on other
Thamks!
Click to expand...
Click to collapse
Oh I understand. btw edit ramdisk is pretty easy, just use winmerge then you see what services are missing etc
BlackMesa123 said:
Oh I understand. btw edit ramdisk is pretty easy, just use winmerge then you see what services are missing etc
Click to expand...
Click to collapse
Thanks! i use MELD 1.8.6.0 for that
but i wil chek the winmerge too
I THINK i restored old bootloader !, Now i am using old twrp because new one didnt work, and room booted !!!!!! OMGGGG SCREENSHOOTS ASAP !
MaDaLiNoSt said:
I THINK i restored old bootloader !, Now i am using old twrp because new one didnt work, and room booted !!!!!! OMGGGG SCREENSHOOTS ASAP !
Click to expand...
Click to collapse
i just instaled the 5.1.1 slimromFN on my F with 6.0.1 botloader
with the replacement mentioned and it booted
i get sim not working but can be from my phone wich are dual sim
i will try the slimF 5.1.1 rom now
everything is working and back to normal, i am using stock boot image !
I just restored old bootloader with custom odin image by me. Because i was locked on the new one
MaDaLiNoSt said:
everything is working and back to normal, i am using stock boot image !
I just restored old bootloader with custom odin image by me. Because i was locked on the new one
Click to expand...
Click to collapse
on my phone are on MM botloader
i never knew i can bypass samsung bootloader and replace with stock one.
Now i feel like a genius (pro) ))))))))
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
I have softbrick my poco f1 no recovery only fastboot mode and the old fastboot , I had mi flash the only stock rom which boots is miui 9 or miui 10 based on android 8.1 and when upgrade it goes to fastbboot but with new fastboot logo of xiaomi what should i do ?
Download mi fastboot flashtool and flash it back to stock simple.....
Sent from my CPH1951 using Tapatalk
stinka318 said:
Download mi fastboot flashtool and flash it back to stock simple.....
Sent from my CPH1951 using Tapatalk
Click to expand...
Click to collapse
I have made this option but i can only boot to miui 9 or 10 of android 8.1 and cant go custom rom android pie or upgrade to miui pie it goes back to fastboot
amrelhossieny48 said:
I have made this option but i can only boot to miui 9 or 10 of android 8.1 and cant go custom rom android pie or upgrade to miui pie it goes back to fastboot
Click to expand...
Click to collapse
How did you softbricked ur device?
Please take a look on my guides and find the guide "clean install official stock miui rom & relock bootloader". Follow exactly the steps there. You will find everything you need in my collection.
Retrial said:
How did you softbricked ur device?
Please take a look on my guides and find the guide "clean install official stock miui rom & relock bootloader". Follow exactly the steps there. You will find everything you need in my collection.
Click to expand...
Click to collapse
I decided to try the OOS McLaren edition (which I thought would be GSI) and flashed 'em on my Poco. Needless to say, it was a violet (rn7) specific rom which popped errors in my TWRP while flashing it and of course it didn't proceed
The thing is though, that after that I couldn't flash any rom ...
The only thing that works is flashing the original stock rom either in MIUI 9 or 10 of Android 8.1 Oreo (I have flashed MIUI 11 and 12 through fastboot and though showing successful I still get fastboot upon reboot) Even getting ota updates from stock 8.1 rom (the 11.0.5 which is Android 9) leads to the update screen, all good, but once it reboots I'm greeted with the fastboot logo again.
Retrial said:
How did you softbricked ur device?
Please take a look on my guides and find the guide "clean install official stock miui rom & relock bootloader". Follow exactly the steps there. You will find everything you need in my collection.
Click to expand...
Click to collapse
I decided to try the OOS McLaren edition (which I thought would be GSI) and flashed 'em on my Poco. Needless to say, it was a violet (rn7) specific rom which popped errors in my TWRP while flashing it and of course it didn't proceed
The thing is though, that after that I couldn't flash any rom ...
The only thing that works is flashing the original stock rom either in MIUI 9 or 10 of Android 8.1 Oreo (I have flashed MIUI 11 and 12 through fastboot and though showing successful I still get fastboot upon reboot) Even getting ota updates from stock 8.1 rom (the 11.0.5 which is Android 9) leads to the update screen, all good, but once it reboots I'm greeted with the fastboot logo again.
Try command line on a computer.....
Fastboot reboot bootloader....
Sent from my CPH1951 using Tapatalk
stinka318 said:
Try command line on a computer.....
Fastboot reboot bootloader....
Sent from my CPH1951 using Tapatalk
Click to expand...
Click to collapse
I have the same problem as well. Only boots from Oreo 8.1
Would love it if you expand this guide. For now it doesn't work even after using MiFlash to Miui 12 (Official).
bluextender said:
I have the same problem as well. Only boots from Oreo 8.1
Would love it if you expand this guide. For now it doesn't work even after using MiFlash to Miui 12 (Official).
Click to expand...
Click to collapse
Did you use the right version of rom there is two available one uses device recovery The other use fastboot flashtool......
stinka318 said:
Did you use the right version of rom there is two available one uses device recovery The other use fastboot flashtool......
Click to expand...
Click to collapse
Yes. The full name of the recovery rom is "beryllium_global_images_V12.0.2.0.QEJMIXM_20200925.0000.00_10.0_global". Extracted from the .tgz file.
I use Miflash to flash the "fastboot" which is the 2.6gb file. The recovery file is also the same filename except its 2gb and I use the MiAssistant program to flash it.
Please explain to me if I did something wrong or it's not the way, at this point I just dont want my Poco to run Android 8.1 forever
bluextender said:
Yes. The full name of the recovery rom is "beryllium_global_images_V12.0.2.0.QEJMIXM_20200925.0000.00_10.0_global". Extracted from the .tgz file.
I use Miflash to flash the "fastboot" which is the 2.6gb file. The recovery file is also the same filename except its 2gb and I use the MiAssistant program to flash it.
Please explain to me if I did something wrong or it's not the way, at this point I just dont want my Poco to run Android 8.1 forever
Click to expand...
Click to collapse
If you have a unlocked bootloader the follow this.....https://forum.xda-developers.com/t/unbrick-flashing-latest-stable-rom-using-fastboot-mode.3901152/
stinka318 said:
If you have a unlocked bootloader the follow this.....https://forum.xda-developers.com/t/unbrick-flashing-latest-stable-rom-using-fastboot-mode.3901152/
Click to expand...
Click to collapse
And this is how to do it with a locked bootloader......https://forum.xda-developers.com/t/pocophone-f1-flash-stock-rom-with-locked-bootloader-and-usb-debugging-off.4084949/
stinka318 said:
If you have a unlocked bootloader the follow this.....https://forum.xda-developers.com/t/unbrick-flashing-latest-stable-rom-using-fastboot-mode.3901152/
Click to expand...
Click to collapse
This is exactly what I did. I flashed Miui12 and it boots to Fastboot. So it doesn't work.
If I flash Miui9 it boots up to Miui9.
Yes I have an unlocked bootloader. Yes I even tried TWRP recovery and flash Miui 12 and it STILL doesnt work.
bluextender said:
This is exactly what I did. I flashed Miui12 and it boots to Fastboot. So it doesn't work.
If I flash Miui9 it boots up to Miui9.
Yes I have an unlocked bootloader. Yes I even tried TWRP recovery and flash Miui 12 and it STILL doesnt work.
Click to expand...
Click to collapse
Just maybe you have a what is known as a version of software that has locked you can't update try flashing early rom or different region.....
stinka318 said:
Just maybe you have a what is known as a version of software that has locked you can't update try flashing early rom or different region.....
Click to expand...
Click to collapse
...that's what I did. I cant flash any other version of Miui aside from Miui9 and 10 basically Android Oreo 8.1. Unless you can suggest me a MIUI rom to use?
I even downloaded and flashed the Miui 11.0.6.0 from the link you gave me. --> https://forum.xda-developers.com/t/unbrick-flashing-latest-stable-rom-using-fastboot-mode.3901152/. It doesn't work.
The MIUI that worked for me is beryllium_global_images_V9.6.18.0.OEJMIFD_20180824.0000.00_8.1_global.
bluextender said:
...that's what I did. I cant flash any other version of Miui aside from Miui9 and 10 basically Android Oreo 8.1. Unless you can suggest me a MIUI rom to use?
I even downloaded and flashed the Miui 11.0.6.0 from the link you gave me. --> https://forum.xda-developers.com/t/unbrick-flashing-latest-stable-rom-using-fastboot-mode.3901152/. It doesn't work.
The MIUI that worked for me is beryllium_global_images_V9.6.18.0.OEJMIFD_20180824.0000.00_8.1_global.
Click to expand...
Click to collapse
Maybe of interest......https://www.getdroidtips.com/xiaomi-poco-f1-stock-firmware/
stinka318 said:
Maybe of interest......https://www.getdroidtips.com/xiaomi-poco-f1-stock-firmware/
Click to expand...
Click to collapse
Which one do you think I should try? I dont have enough bandwidth to download all of them and try one by one.
bluextender said:
Which one do you think I should try? I dont have enough bandwidth to download all of them and try one by one.
Click to expand...
Click to collapse
Your choice if one doesn't work try another one it may take a while..... good luck
stinka318 said:
Your choice if one doesn't work try another one it may take a while..... good luck
Click to expand...
Click to collapse
Oh... ok. Well I'm open to other solutions...
I suppose I would have to take a chance with this. If with any luck those wild MIUI Android 10 roms will work. If not my F1 is forever stuck in Oreo 8.1 :')
How did you go get it off 8.1....
stinka318 said:
How did you go get it off 8.1....
Click to expand...
Click to collapse
At first my F1 was running Miui 12. I tried installing the Cyberpunk rom (One Plus) through twrp recovery cause I saw a Youtube video saying its for "all phones". It returned the Updating Error 7, pretty much the same story as the original poster here.
The only working rom for me right now is Miui 9/10 running Oreo 8.1. If I try flashing Miui 12 through the fastboot it will always show the rabbit fastboot logo. Even Miui 11 or any other rom.