Develop Bugs

AT&T to JME boot/recovery fix

Sorry if this was already posted but I banged my head on the wall for a while before I figured a fix so may be it will be helpful to someone.
I tried to flash Roto-JME over brand new AT&T Tab. All went smooth but at boot up I saw AT&T start screen followed by black screen with vertical white line on the right. Then device would boot ok. I would get the same screen in recovery mode.
I also tried to flash JM6 but result was the same.
I figured that it must be something with SBL/PBL from AT&T not liking European Tab kernel (or other parts of firmware).
Long story short - I flashed JJ4 because it contains boot.bin and sbl.bin and they are not from infamous JMA/C/D etc signed firmwares. And voila - now I have regular Samsung logo and normal boot without lame white line.
After that I flashed JME and had no problem since.
The end result - my bootloaders are not signed:
SGT-BootloaderCheck v1.0 - Copyright (C) 2010 Chainfire
boot.bin: Unsigned
sbl.bin: Unsigned
zImage: SIGNED !
Assessment:
-- Bootloaders: Unprotected, can flash all bootloaders and kernels
-- Kernel: Signed, can be flashed on all bootloaders

thanks alexnoalex,
can anyone else confirm this work as mentioned, and safe?

quickk said:
thanks alexnoalex,
can anyone else confirm this work as mentioned, and safe?
Click to expand...
Click to collapse
I can confirm that this works, but, since we don't have stock bookloaders for at&t, its a one way trip. If you go back to the stock at&t firmware that I built, it will boot blank and you wont be able to see the stock recovery screens.
Its not perfectly safe in that if you fail to flash JJ4 bootloaders you can brick your tab. But once you have them, your tab becomes perfectly compatible with the euro firmware.

So why boot.bin and Sbl.bin pulled from AT&T stock using dd will not work?
Sent from my GT-P1000 using XDA App

alexnoalex said:
So why boot.bin and Sbl.bin pulled from AT&T stock using dd will not work?
Click to expand...
Click to collapse
I only know the results. Anyone who has flashed them back, either through Odin, Heimdall or dd has created a brick.

alexnoalex said:
Sorry if this was already posted but I banged my head on the wall for a while before I figured a fix so may be it will be helpful to someone.
I tried to flash Roto-JME over brand new AT&T Tab. All went smooth but at boot up I saw AT&T start screen followed by black screen with vertical white line on the right. Then device would boot ok. I would get the same screen in recovery mode.
I also tried to flash JM6 but result was the same.
I figured that it must be something with SBL/PBL from AT&T not liking European Tab kernel (or other parts of firmware).
Long story short - I flashed JJ4 because it contains boot.bin and sbl.bin and they are not from infamous JMA/C/D etc signed firmwares. And voila - now I have regular Samsung logo and normal boot without lame white line.
After that I flashed JME and had no problem since.
The end result - my bootloaders are not signed:
SGT-BootloaderCheck v1.0 - Copyright (C) 2010 Chainfire
boot.bin: Unsigned
sbl.bin: Unsigned
zImage: SIGNED !
Assessment:
-- Bootloaders: Unprotected, can flash all bootloaders and kernels
-- Kernel: Signed, can be flashed on all bootloaders
Click to expand...
Click to collapse
AlexnoAlex,
What was your procedure for loading JJ4 combining with Roto JME to fix the white line... Can you explain in details whether you had to do in odin (.pit, repartition, etc.)...
Also are you able to return to At&t Stock?

Jeepsdaddy said:
AlexnoAlex,
What was your procedure for loading JJ4 combining with Roto JME to fix the white line... Can you explain in details whether you had to do in odin (.pit, repartition, etc.)...
Also are you able to return to At&t Stock?
Click to expand...
Click to collapse
Not at the moment, so this is a one way ticket.
Attached are the jj4 bootloaders for you to flash using Odin, no pit file, use the PDA button.
Make sure your computer is working well, it sounds like it is. I would't flash bootloaders on a flaky system.
I really really hope you did a RotoBackup since earlier today. If not, please do it before flashing this file.
I only recommend this firmware for AT&T Tabs that have the screen problems.
I'm on irc if you need assistance.
server: irc.droid-life.com channel: #ModADroid-Galaxy-Tablet
View attachment jj4_bootloaders.zip

rotohammer said:
Not at the moment, so this is a one way ticket.
Attached are the jj4 bootloaders for you to flash using Odin, no pit file, use the PDA button.
Make sure your computer is working well, it sounds like it is. I would't flash bootloaders on a flaky system.
I really really hope you did a RotoBackup since earlier today. If not, please do it before flashing this file.
I only recommend this firmware for AT&T Tabs that have the screen problems.
I'm on irc if you need assistance.
server: irc.droid-life.com channel: #ModADroid-Galaxy-Tablet
View attachment 496999
Click to expand...
Click to collapse
Yes I did the RotoBackup per your instruction.
I'd prefer to wait until it is no longer a one way ticket. I need to be able to return to stock. The way I understand it now is that I can easily return to stock from my current state. Is that correct?

From Chat. To test with JME v4

Jeepsdaddy said:
From Chat. To test with JME v4
Click to expand...
Click to collapse
What are we testing with the swype?

Can we flash the .tar file to fix the black screen with the white line for at&t tabs, then use the bootloader fix .apk to unprotect our tab?
Or, what is the procedure to repair the black screen with white line?
This happens when you re partition a stock at&t tab, then flash Roto JME.

rangercaptain said:
Can we flash the .tar file to fix the black screen with the white line for at&t tabs, then use the bootloader fix .apk to unprotect our tab?
Or, what is the procedure to repair the black screen with white line?
This happens when you re partition a stock at&t tab, then flash Roto JME.
Click to expand...
Click to collapse
Just flash the JJ4 bootloaders, as they are unsigned. Then you are finished, theres no need for the patch.

Thank you Roto-Amigo. The jj4 bootloaders flashed though odin in the pda spot, now the at&t tab has the logo restored, the black screen and white line is gone.

Failed to update
Hi!
I tried this with the attached file, and had no success. As I'm quite unfamiliar with Odin, I will post an image of the failure but I lack debugging know-how with this tool. I'm willing to do whatever, but don't know what "whatever" is.
I appreciate any advice, especially with the information-gathering process. (Note: I did download again, from a different computer, with the same result.)
{
"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"
}

Everything in odin set up looks good except the fail. Are your pc drivers correct? Was your tab in download mode? Did you see if your current bootloader is protected by using chainfire's bootloader patch? Let me know what works.

rangercaptain said:
Everything in odin set up looks good except the fail. Are your pc drivers correct? Was your tab in download mode? Did you see if your current bootloader is protected by using chainfire's bootloader patch? Let me know what works.
Click to expand...
Click to collapse
Sheesh, I had not been in download mode. In my (weak) defense, I had only done this once - and that's to apply JME4. I'll get better. The patch is applied and all looks well! Thanks for your indulgence, and for the prompt!
I knew the drivers were correct since nothing has changed on this PC (haven't used it) since applying JME4 to the Tab. I'll have a quick search for chainfire's bootloader patch.

rotohammer said:
Just flash the JJ4 bootloaders, as they are unsigned. Then you are finished, theres no need for the patch.
Click to expand...
Click to collapse
Hello rotohammer, sorry to bother you but I'm having a problem that I cannot seem to fix. Can you kindly see my post to see if you can help me? You seems like the one who knows the a lot about the AT&T Galaxy Tab. Thanks in advance for your help!
http://forum.xda-developers.com/showthread.php?p=11333386#post11333386

fixed me up!
rotohammer said:
Not at the moment, so this is a one way ticket.
Attached are the jj4 bootloaders for you to flash using Odin, no pit file, use the PDA button.
....
I only recommend this firmware for AT&T Tabs that have the screen problems.
View attachment 496999
Click to expand...
Click to collapse
totally fixed my blank screen booting! thanks!!
ATT Galaxy Tab, stock to Roto JME v1
Fixed Blank Boot w/Line w/jj4 bootloaders

hi guys,, i have tab that stuck at galaxy tab logo,, it cant access recovery mode but download mode is still ok.. ive tried many thinks including flashing pit and rotov4. but no luck. it always 'pass' but stuck at galaxy tab logo..
so my question is, can my tab ( arabic tab) be flashed with this jj4 so it can be normal again?..
thanks

[q] can i return to stock?

I just bought a Galaxy S3 from someone and it was already rooted. I am not able to add this phone to my Sprint account because of it. SO I looked up threads on returning the phone to stock and they all say if you have this new update you cannot go back to stock because of this knox warranty and warranty. When I loaded the boot screen thing it says warranty: 0. Or something like that.
So is there a way I can revert back to stock and UNroot my phone??

michaelemerica said:
I just bought a Galaxy S3 from someone and it was already rooted. I am not able to add this phone to my Sprint account because of it. SO I looked up threads on returning the phone to stock and they all say if you have this new update you cannot go back to stock because of this knox warranty and warranty. When I loaded the boot screen thing it says warranty: 0. Or something like that.
So is there a way I can revert back to stock and UNroot my phone??
Click to expand...
Click to collapse
The phone being rooted has nothing to do with activating the phone with Sprint.
If you mean by boot screen download/bootloader mode and you see warranty bit 0, sounds like you already have kitkat (with knox).
Go into settings\about phone and see what your android version is.
And yes you can go back to stock un-rooted.
Get back about your version of android and then you can go from there.

I have version 4.4.2.
The reason I believe this is the reason I cannot activate for Sprint is because I sold a rooted phone to a friend and they could not activate it. I got the phone and unrooted it back to stock and it was able to be put on their account.
But yeah, I think it will work after I am able to unroot it. I'm just nervous bc all of the threads I have found have a warning telling me not to use their method if I have that Knox Warranty in the bootscreen. They said it will hard brick. But most of those threads are from a few years ago. I guess because it's an older phone.
If you could find me a method to return it to stock / unroot I'd appreciate it so much.

That's a new one on me.

I've never heard of root being the cause of activation problems. As long as you are on a tw rom it should work. A quick search would have given you this though http://forum.xda-developers.com/showthread.php?t=2738533
[FULL RESTORE][TAR] Stock ND8 Odin FLASHABLE [4.4.2]

michaelemerica said:
If you could find me a method to return it to stock / unroot I'd appreciate it so much.
Click to expand...
Click to collapse
Ok,
First go download Holo Backup. Extract the folder in the zip file to your desktop:
Get it Here:
http://omegavesko.github.io/SimpleADBBackup/
It's a self contained ADB solution for backing up your apps etc. Instructions are on the web page. Pretty simple really. Make a backup(s) and store it in the Holo folder on your desktop.
Then as metalfan78 said, go and get DR CDMA's stock tar file. You will Odin that after you back up.
Get it Here:
http://forum.xda-developers.com/showthread.php?t=2738533
It will restore you completely to stock, un-rooted with stock recovery.
Then use Holo backup to restore.
Thats it.

Does Holo backup work good? I have only used titanium backup for the past 5 years.

Well, I use TiBu exclusively but I wanted to have an alternative incase something went wrong. So just before I finally moved to ND8 I gave it a try and it worked perfectly.

Nice, I'll have to give it a try sometime.

Just note, when you Odin the ND8 tar, it'll wipe your internal storage (not your microSD), so if you've saved any pictures or downloads to the internal storage, copy them to your SD and / or PC / cloud.
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Wicked X v6.5, Ktoonsez' latest kernel and the latest Philz Touch Recovery.

HEY GUYS IT WORKED!
I'm not sure if my phone had a custom rom on it from the previous owner or what. It's an almost brand new phone, no scratches or anything. But my last phone did this same thing only it was easier to find the file to un-root. I want to say it's a Samsung thing... but that could be false. My last phone was a Samsung Epic.
But anywayyy. You guys solved my problem 100% and I appreciate you guys taking the time to help me. XDA is the best. I come here for most everything.
THANK YOU.

michaelemerica said:
HEY GUYS IT WORKED!
But anywayyy. You guys solved my problem 100% and I appreciate you guys taking the time to help me. XDA is the best. I come here for most everything.
THANK YOU.
Click to expand...
Click to collapse
That's great.
Now for the sake of the masses, explain exactly what you did.

jhill110 said:
That's great.
Now for the sake of the masses, explain exactly what you did.
Click to expand...
Click to collapse
-----------
I bought a phone from a friend and called Sprint Customer Care to make sure it wasn't lost/stolen. It wasn't but they still weren't able to activate it because they said my device wasn't supported by Sprint and was not a Sprint device. (It definitely was. It had a Sprint model #, Said Sprint when I booted up, and said Sprint on the back of my phone)
I tinkered with my phone and realized it was Un-rooted by being able to go into Odin download mode. You can go into download mode by simultaneously pressing the power button, home button and volume down key. If it works you are rooted. There may be other ways to check, but that's how I did it.
I was having trouble un-rooting my phone because many threads I came across said I couldn't Un-root my device with their method if I had Knox Warranty on my phone. Their methods were for older android versions. (They said it will brick my device if I did it that way.)
You can figure this out by going into download mode by simultaneously pressing the power button, home button and volume down key. If your device says Knox Warranty or Warranty Bit on the screen then you have the update. SO USE THIS METHOD TO UNROOT / RETURN TO STOCK.
I asked XDA and they gave me this handy little website that allows you to un-root and return to stock with instructions. http://forum.xda-developers.com/showthread.php?t=2738533
***BEFORE YOU DO THIS BACKUP ALL YOUR DATA WITH HOLO BACKUP SO YOU DONT LOSE ANYTHING***
First go download Holo Backup. Extract the folder in the zip file to your desktop:
Get it Here:
http://omegavesko.github.io/SimpleADBBackup/
It's a self contained ADB solution for backing up your apps etc. Instructions are on the web page. Pretty simple really. Make a backup(s) and store it in the Holo folder on your desktop.
Click to expand...
Click to collapse
The only other problem I ran into while using this method is downloading the .tar.md5 file. The website wouldn't load the Captcha for me to enter to begin the download. So I looked around and the other one I found was downloading WAY too slow.
SO I found and used this one: http://www.androidfilehost.com/?fid=23487008491966461
It worked perfect.
Instructions:
1. Extract Download file
2. Put phone into download mode (power off, then power button + Volume Down + Home Button (website didn't mention holding the home button but you have to with the S3), then volume up when prompted)
3. Open Odin (right click > open as administrator)
4. Load File L710VPUCND8_L710SPRCND8_L710VPUCND8_HOME.tar.md5 into the PDA slot
5. Start flashing
6. Grab some popcorn because it will take a while
Click to expand...
Click to collapse
The only thing they forgot to mention and it left my phone stuck on the Samsung boot screen is you must go into Recovery Mode (power off, then Power button + Home + Volume up) and CLEAR THE CACHE.
Reboot your device
Once it boots up call Sprint or talk to a representative online to activate your device and they will walk you through it.
VOILA, YOU ARE GOOD TO GO.

Just so you know, you can get into download mode whether you're rooted or not, being rooted has nothing to do with being able to boot into download mode
http://i1076.photobucket.com/albums/w450/flastnoles11/tapatalk_1379735598798_zpsae07fa91.png

michaelemerica said:
The only thing they forgot to mention and it left my phone stuck on the Samsung boot screen is you must go into Recovery Mode (power off, then Power button + Home + Volume up) and CLEAR THE CACHE.
Click to expand...
Click to collapse
Glad you got it all sorted. I figured that's all you needed.
It doesn't always get stuck like that for everyone. That's a generally good way to fix that kind of problem any time it does happen, though.
Sent from my Sprint Samsung Galaxy SIII on TouchWiz 4.4.2 with Wicked X v6.5, Ktoonsez' latest kernel and the latest Philz Touch Recovery.

Will this work with 4.3 w/knox?
jhill110 said:
Ok,
First go download Holo Backup. Extract the folder in the zip file to your desktop:
Get it Here:
http://omegavesko.github.io/SimpleADBBackup/
It's a self contained ADB solution for backing up your apps etc. Instructions are on the web page. Pretty simple really. Make a backup(s) and store it in the Holo folder on your desktop.
Then as metalfan78 said, go and get DR CDMA's stock tar file. You will Odin that after you back up.
Get it Here:
http://forum.xda-developers.com/showthread.php?t=2738533
It will restore you completely to stock, un-rooted with stock recovery.
Then use Holo backup to restore.
Thats it.
Click to expand...
Click to collapse
Will this also work on Android version 4.3?
I have 4.3 with Knox and have rooted my phone and also have loaded Philz Touch 6 (CWM Base Version: V6.0.4.5).
I've attached a screen shot of my complete phone info. I would like to return to stock and upgrade to 4.4.
Thanks!
David
{
"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"
}

abqdavid said:
Will this also work on Android version 4.3?
I have 4.3 with Knox and have rooted my phone and also have loaded Philz Touch 6 (CWM Base Version: V6.0.4.5).
I've attached a screen shot of my complete phone info. I would like to return to stock and upgrade to 4.4.
Thanks!
David
Click to expand...
Click to collapse
Yes, it will work. The tar link is the 4.4 stock tar. Just backup using holo, or backup of your choice, flash the tar, then philz, reroot, profit
Sent from my SM-G900P using XDA Free mobile app

[ROM][C6903][14.5.A.0.270] Stock Pre-Rooted and Debloated

Here is the stock 14.5.A.0.270 (5.0.2) customized AU odexed, pre-rooted, highly debloated and bundled up with PRFCreator
BEFORE and 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"
}
ZIP ARCHIVE INCLUDES:
a) the rom itself (removed bunch of crapware)
b) SuperSU-2.49-BETA
c) Nuts Dual Recovery 2.8.15
d) DRM Function Restoration for UB
STEPS:
1) backup
2) wipe /system, /cache, /dalvik-cache
3) flash the main rom
4) flash google services removal.zip (optional)
5) boot up phone and go through setup
6) flash further debloat (optional)
DOWNLOADS:
Main
Google Services Removal
Further Debloat​

Maybe a noob question: Flashing your ROM means I will have my DRM functions restored?

Papanik said:
Maybe a noob question: Flashing your ROM means I will have my DRM functions restored?
Click to expand...
Click to collapse
I'm interested in this as well. Does flashing your rom restore BIONZ processing, making all the steps in the linked thread un-necesarry?
Also, anyway to check if BIONZ is working or not?

Papanik said:
Maybe a noob question: Flashing your ROM means I will have my DRM functions restored?
Click to expand...
Click to collapse
zgomot said:
I'm interested in this as well. Does flashing your rom restore BIONZ processing, making all the steps in the linked thread un-necesarry?
Also, anyway to check if BIONZ is working or not?
Click to expand...
Click to collapse
I'm currently on a locked bootloader so I can't verify if it'll work without having to flash an ftf with TA beforehand. Best thing to do is try it yourself.
If x-reality is working, bionz is working.

I flashed this ROM and my Z1 does not boot at all. When i press the power button, it vibrates once and that's all.
I flashed a stock rom, re-installed recovery and created a pre-rooted zip based on the SG customized firmware. The result was the same. Black screen, no sign of activity.
Does anyone have any idea what could be wrong here?
My device is a C6903 and worked just fine with the pre-rooted .242
Thanks!

facing problems...
After i do google and further debloat... dun even have app store to install my apps. I also unable to add my google account at Settings > Accounts...
Its great to have a RAM free rom... but what the point of having so much ram when there's nothing else u can do with the phone. I did try installing Google Play Store apk but it just simply crashes...
Please dun be offended as I still feel this ROM is a well done rom, I might just missed out something.

kedirakevo said:
After i do google and further debloat... dun even have app store to install my apps. I also unable to add my google account at Settings > Accounts...
Click to expand...
Click to collapse
The google debloat is only optional. If you don't flash it, you'll get to keep the play store.
I personally don't use the play store and download my apps from apkmirror or evozi

Okay, can share more what does further debloat do? I can do that without google debloat right?

kedirakevo said:
Okay, can share more what does further debloat do?
Click to expand...
Click to collapse
Further debloat removes some of the bloat that I forgot to remove from the main rom itself and also the setup wizards. So make sure to use it only after booting your device and going through the setup.
I can do that without google debloat right?
Click to expand...
Click to collapse
Yes.

I've tried flashing this twice and have ended up softbricking twice. I think the issue may be because of the wiping of system, which I have honestly never had to do before, so I'll try once again, and if it doesn't work I guess I'll just find something else.
EDIT: Yep, nothing I do seems to really be working, probably just getting bad downloads on my end though.

compatible with c6902?
Is this compatible with xperia z1 ,c6902?

Zerousen said:
I've tried flashing this twice and have ended up softbricking twice.
Click to expand...
Click to collapse
Do you have a c6903 and on latest kitkat(.108) or .242?
ravishmahur said:
Is this compatible with xperia z1 ,c6902?
Click to expand...
Click to collapse
Nope.

How to flash Xposed in this rom please? Thanks

Ahki767 said:
Here is the stock 14.5.A.0.270 (5.0.2) customized AU odexed, pre-rooted, highly debloated and bundled up with PRFCreator
edited
Click to expand...
Click to collapse
Flashed without issues coming from CM12.1 (the terrible, terrible photo-quality and some in-call sound issues recently always make me return to stock). I just took care to follow instructions and flash a pre-rooted .2.4.2 rom prior to flashing this.
The rom feels really really smooth, it's lovely so far.
edit: One issue thus far is some incompatibility on the Play Store, for instance Galaxy On Fire - Alliances. I can download it on any rom (CM/stock) except this one. Anyway to fix this?
edit2: Are dpi values changed for the launcher? I've tried a couple of xposed modules but I can't seem to get rid of that empty edge. The grid size is weird... it's like 4x4 but really crowded, with nasty-looking empty margins.
I tried a couple of apps to change dpi values to default, but they wouldn't read current dpi and no new values could be applied. Maybe this is linked to the Play Store incompatibilities.

How must I install it? Always I installed it (from official .242 and .270 too with RockZ1 Kernel) I had many bugs on this ROM, please help me

HELP
dyonissos said:
I flashed this ROM and my Z1 does not boot at all. When i press the power button, it vibrates once and that's all.
I flashed a stock rom, re-installed recovery and created a pre-rooted zip based on the SG customized firmware. The result was the same. Black screen, no sign of activity.
Does anyone have any idea what could be wrong here?
My device is a C6903 and worked just fine with the pre-rooted .242
Thanks!
Click to expand...
Click to collapse
Please help, I'v also got the same problems. I follow everything, but now my phone can not turn on anymore, can not charge. Everytime I press power button, it only vibrate once, but still off. Please help me.
I do the steps from Kitkat and using latest DUAL RECOVERY TWRP.
Thank you in advance

busukusu said:
Please help, I'v also got the same problems. I follow everything, but now my phone can not turn on anymore, can not charge. Everytime I press power button, it only vibrate once, but still off. Please help me.
I do the steps from Kitkat and using latest DUAL RECOVERY TWRP.
Thank you in advance
Click to expand...
Click to collapse
I fond the solutions for my problems. I test Fastboot at It work. When Power Off, press Volume Up and connect the USB Cable, then I can detect my phone with command: fastboot devices
After that, using Flashtools and install any FTF source with Kitkat 108, then flash it using Flashtools at computer PC. Prepare downloaded FTF files about 1 GB size at the same computer drive, then run Flashtools and then connect Press Volume Down and connect with USB cable, after that Flashtools display will show that my phone detected / connected, and continue with flashing FTF files, the process about 10 minutes less, and after finish flashing, disconnect USB cable, press Power button and YES it work again.
After that I have to install again with TWRP and install any Stock preroot firmware.

dyonissos said:
I flashed this ROM and my Z1 does not boot at all. When i press the power button, it vibrates once and that's all.
I flashed a stock rom, re-installed recovery and created a pre-rooted zip based on the SG customized firmware. The result was the same. Black screen, no sign of activity.
Does anyone have any idea what could be wrong here?
My device is a C6903 and worked just fine with the pre-rooted .242
Thanks!
Click to expand...
Click to collapse
I had the exact same problem. Ended up going back to my nandroid backup.
I am on locked bootloader. Not sure if that is the problem.

@Ahki767 could you please post md5 of the package? I am trying to make sure my download is not corrupt.

zgomot said:
edit: One issue thus far is some incompatibility on the Play Store, for instance Galaxy On Fire - Alliances. I can download it on any rom (CM/stock) except this one. Anyway to fix this?
edit2: Are dpi values changed for the launcher? I've tried a couple of xposed modules but I can't seem to get rid of that empty edge. The grid size is weird... it's like 4x4 but really crowded, with nasty-looking empty margins.
Click to expand...
Click to collapse
if you're still on this rom, you can change the dpi in /system/build.prop look for lcd_density and change it to 480 (original value). only thing i can think of for incompatibility is maybe an out of date play services
squashbuff said:
@Ahki767 could you please post md5 of the package? I am trying to make sure my download is not corrupt.
Click to expand...
Click to collapse
md5 check: 0406a4743310ee19209cfedcf0c728c9
make sure you're flashing at least from latest kit kat or lollipop

[ROM] d2att LineageOS Unofficial 14.1 WhenICanlies

Hit the thanks button and Enjoy. Any problems let me and others here know. Dirty flash the updates NOT the initial flash of this rom but the updates to it. As of 9-3-18 i will be switching to Ubuntu 18.04 Bionic Beaver, that being said i do not know if i will have to change anything or do anything different to keep pushing these updates out but i will most definitely try to keep them coming.
Data and SIM fixed
Rom Zip = flash this https://www.androidfilehost.com/?fid=673956719939835046, Gapps, and SuperSU
after the rom has booted up install root browser and navigate to the the ROM zip, extract build.prop in system folder and replace the one in your new root/system folder with it and reboot your phone.
Update
4-17-18
https://www.androidfilehost.com/?fid=746010030569969556 replace build.prop in root/system with the one in the ROM zips system/build.prop after boot then reboot
4-24-18
https://www.androidfilehost.com/?fid=673956719939836755
its got root built in but, If you are updating and already had supersu then you will have to flash the supersu zip anyways or it will say the binary is occupied. If you are not updating all you need is to install the supersu.apk . Data and SIM is working. After the rom boots up and you have root and a root browser replace the phones system/build.prop with the one in this zips system/build.prop and reboot. follow this process if there are any future updates.
5-2-2018
https://www.androidfilehost.com/?fid=818222786056028458
No special directions root is not built in
5-13-18
https://www.androidfilehost.com/?fid=890278863836285207
No special directions root is not built in
5-20-18
https://www.androidfilehost.com/?fid=746163614322265526
5-31-18
https://www.androidfilehost.com/?fid=890278863836288847
7-28-18
https://www.androidfilehost.com/?fid=5862345805528060531
9-3-18
https://www.androidfilehost.com/?fid=1322778262903997130
10-07-18
https://www.androidfilehost.com/?fid=1322778262904022217
10-10-18
https://www.androidfilehost.com/?fid=1322778262904024839
12-7-18
https://www.androidfilehost.com/?fid=11410963190603868410
12-15-18
https://www.androidfilehost.com/?fid=11410963190603875897
2-24-19
https://www.androidfilehost.com/?fid=1395089523397901058
3-24-19
https://www.androidfilehost.com/?fid=1395089523397924748
5-6-19
http://download1486.mediafire.com/5...73/lineage-14.1-20190507-UNOFFICIAL-d2att.zip
Temporary link due to problems with AFH
I Have Added the OTA-Updater App (More details in the last pages of this thread)
8-7-19
https://www.androidfilehost.com/?fid=6006931924117931911
ditched ota updater
10-11-19
https://www.androidfilehost.com/?fid=1899786940962606099
recommend clean flash (built with different computer and proprietary blobs pulled directly from stock nj2 device plus some from an early build of this rom),
not built with su or ota updater (I experienced issues with ota updater because of download link problems) ,
also I do not have anything to do with the security patches, they are released to the source when they are ready. The patch level to this build is Sept. 5.
My apologies for the lapse in updates, and responses.
setprop persist.lineage.nofool true in terminal emulator with root privs (type su first grant permission then setprop persist.lineage.nofool true) gets rid of persistant notification
Bluetooth dialtone when playing music fix
Settings > Battery > tap in 3-dot menu at top right tap on Battery optimisation. To show all apps and services here, select the ‘All apps’ options under the dropdown. Tap on both of the Bluetooth services and change them to Don't optimise.

First of all, thank you for taking on this task as this is a nice device to this day.
Installed to test with the following results in regards to sim card / mobile data.
Upon setup, no sim card detected and no baseband or imei. Restarting with same results and certain obvious settings greyed out. I think your endeveor is most positive. Again, thank you...

N/A

Joker1716 said:
You have a ROM where the sim works try this https://forum.xda-developers.com/galaxy-note-3/help/solution-lineage-os-sim-t3640689 page 1 of the thread if you want I do not have a sim at all or I would
Click to expand...
Click to collapse
Sim still not working after doing this.

DerPuGNa said:
Sim still not working after doing this.
Click to expand...
Click to collapse
Did you mess with any settings under cellular networks? And there is a sim status option in the about phone/status? I don't have a sim or service so I can't help in that area

DerPuGNa said:
Sim still not working after doing this.
Click to expand...
Click to collapse
Samsung phone info and test apk in play store

DerPuGNa said:
Sim still not working after doing this.
Click to expand...
Click to collapse
I noticed the I was on nj1 and the rom is for nj2 so I flashed this it may fix it it may not but it's the modem and bootloader for nj2
https://androidfilehost.com/?fid=24052804347797347

Chuckles5150 said:
First of all, thank you for taking on this task as this is a nice device to this day.
Installed to test with the following results in regards to sim card / mobile data.
Upon setup, no sim card detected and no baseband or imei. Restarting with same results and certain obvious settings greyed out. I think your endeveor is most positive. Again, thank you...
Click to expand...
Click to collapse
https://androidfilehost.com/?fid=24052804347797347 bootloader and modem for nj2 flashable zip the rom is made around nj2 so you may need to flash this to get data just a suggestion

I needed nj2 for my sim to work with carbon, so that makes sense. I'll flash this later.

Joker1716 said:
https://androidfilehost.com/?fid=24052804347797347 bootloader and modem for nj2 flashable zip the rom is made around nj2 so you may need to flash this to get data just a suggestion
Click to expand...
Click to collapse
Yeah thanks, been running NJ2 for a long time. I'll look into some things soon.

Has anyone tried the settings/system profiles/default/settings I noticed that the default configuration is not setup so either turning system profiles off or configuring them accordingly may help. You may have to configure them then reboot. I wish I could help more but I can not being as I don't have a sim. I only use wifi on this phone.

Joker1716 said:
Did you mess with any settings under cellular networks? And there is a sim status option in the about phone/status? I don't have a sim or service so I can't help in that area
Click to expand...
Click to collapse
I didn't mess anything about sim or related to sim.
Joker1716 said:
I noticed the I was on nj1 and the rom is for nj2 so I flashed this it may fix it it may not but it's the modem and bootloader for nj2
https://androidfilehost.com/?fid=24052804347797347
Click to expand...
Click to collapse
I've flash this and still nothing. If you look closely into the settings, I've manage to have a signal because I revert back to OCT N OS. Because I need to copy the lib-sec.ro from the working ROM and paste it to the Linage OS.
{
"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"
}
Joker1716 said:
Has anyone tried the settings/system profiles/default/settings I noticed that the default configuration is not setup so either turning system profiles off or configuring them accordingly may help. You may have to configure them then reboot. I wish I could help more but I can not being as I don't have a sim. I only use wifi on this phone.
Click to expand...
Click to collapse
Disabled this setting and still nothing. Tried everything you've said. Replace the Lib-sec.ro, flash the NJ2 modem. still nothing. I've notice that baseband and IMEI is unknown at the Linage OS.

*#*#4636#*#* is a testing menu.

I have contacted lineage about the sim and data problem to see if they know what the deal is now its a waiting game. The other variants I have built for (d2spr,d2tmo) have no issues as of yet hopefully there will be a solution soon.

Joker1716 said:
*#*#4636#*#* is a testing menu.
Click to expand...
Click to collapse
Unknown IMEI as i said.

DerPuGNa said:
Unknown IMEI as i said.
Click to expand...
Click to collapse
Got it to recognise the baseband and imei its a small process I will get the file uploaded and directions posted shortly

DerPuGNa said:
Unknown IMEI as i said.
Click to expand...
Click to collapse
I have been up for days trying to figure out this problem. I believe I have found the solution, as i do not have a SIM i cant fully test but i did get the Rom to recognize the efs information. This is the process:
Rom Zip = flash this https://www.androidfilehost.com/?fid=673956719939835046, Gapps, and SuperSU
after the rom has booted up install root browser and navigate to the the ROM zip, extract build.prop in system folder and replace the one in your new root/system folder with it and reboot your phone.
I did all that and included a screenshot in the previous post
please let me know how it worked for you you may still need to disable system profiles and work with the settings after the sim is recognized

Joker1716 said:
I have been up for days trying to figure out this problem. I believe I have found the solution, as i do not have a SIM i cant fully test but i did get the Rom to recognize the efs information. This is the process:
First install the Rom from the first post in the thread 4-13-18
Second install the GAPPS and SuperSU
Third install root browser navigate to root/system/build.prop and copy it onto your sdcard
Fourth dirty flash this Rom Zip = https://www.androidfilehost.com/?fid=962187416754475323 or this if sim still isnt recognized https://www.androidfilehost.com/?fid=673956719939835046 and SuperSU
Fifth after the rom has booted up open root browser navigate to the place where you copied the build.prop to and replace the one in your new root/system with it and reboot your phone. If sim still is not recognized flash the second links ROM zip and continue with the instructions.
I did all that and included a screenshot in the previous post
please let me know how it worked for you you may still need to disable system profiles and work with the settings after the sim is recognized
Click to expand...
Click to collapse
"Rom from the first post in the thread 4-13-18" where is it?
instead of installing the rom and copy the build.prop, can I just copy and past the build.prop from the zip? i think that will save a lot of time?

DerPuGNa said:
"Rom from the first post in the thread 4-13-18" where is it?
instead of installing the rom and copy the build.prop, can I just copy and past the build.prop from the zip? i think that will save a lot of time?
Click to expand...
Click to collapse
The first post in this thread the ROM link dated 4-12-18 my bad and yes you can

Joker1716 said:
The first post in this thread the ROM link dated 4-12-18 my bad and yes you can
Click to expand...
Click to collapse
You could just install one of the ROMs in the solution post and extract the build.prop from the zip and paste it in the root/system folder it would save a lot of time but I wanted to be thorough

OTA failure problem.

My Lenovo Vibe K5 Plus (3GB RAM) has OTA update problem.
I'm attaching some Screenshots.
Its not rooted or modified in any way.
{
"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"
}
Phone will reboot normally and show "OTA Update failed".
My question is can I update it to latest build by using Lenovo Update Assistant or should I go in order to avoid bricking?
Can I flash the latest build using "Lenovo Smart Assistant" or QFIL?
Will it create any problem like bricking?
Please help.

Your problem is quite classic, the way to solve it is quite simple, but you'll have to lose your data anyway.
The first way is to check if in your internal storage you have a "/0/carrier" folder. If it's the case, you should flash the file <your_country>.ota.zip (via "apply update from sdcard", if it's not accessible, you should copy this file on your external SD card). It will take some time but then you should download and update your phone
In my latest experience, you can try to use Lenovo tools, but I did not succeed to flash my phone this way (never found the right model)
Personnally, when I want to get back to "updatable stock", I usually do this :
Flash a stock ROM via QFIL, but not the last version (I'm on K5 Plus 2GB, and I flash S042)
Just after success, I reboot to booloader via "Power + Vol -"
Using my PC, I reboot to a TWRP recovery, without flashing it, and without changing the readonly filesystem (via TWRP you can access both internal and external storage) : fastboot boot <path to twrp img file>
Here I flash the /0/carrier/<my_country>.ota.zip
Then I reboot and my ROM is installed, and updatable without the carrier problem
Tell me if you need further explanations.

@adinechin thankyou so much for replying.
I don't need my data because I've already backed up everything.
Can I downgrade to a lower build? For example I have build S051 currently installed, so can I go back to S042 with QFIL without any problems?
Is there any other method which doesn't need TWRP because I'm very much afraid of going custom at this moment, because of my lack of knowledge?
I don't have anything in 0 folder. Its empty even after downloading OTA update.

Apocalypse0 said:
@adinechin thankyou so much for replying.
I don't need my data because I've already backed up everything.
Can I downgrade to a lower build? For example I have build S051 currently installed, so can I go back to S042 with QFIL without any problems?
Is there any other method which doesn't need TWRP because I'm very much afraid of going custom at this moment, because of my lack of knowledge?
Click to expand...
Click to collapse
Did you check if you have your ota.zip file ? If you can find it, you only have to flash it and that's it
Sent from my Lenovo K5 Plus using XDA Labs

adinechin said:
Did you check if you have your ota.zip file ? If you can find it, you only have to flash it and that's it
Sent from my Lenovo K5 Plus using XDA Labs
Click to expand...
Click to collapse
No, that's what the irritation. After downloading OTA completely, I don't get anything in my 0 folder. That folder is completely empty. No OTA.zip or any other files completely empty.

Apocalypse0 said:
No, that's what the irritation. After downloading OTA completely, I don't get anything in my 0 folder. That folder is completely empty. No OTA.zip or any other files completely empty.
Click to expand...
Click to collapse
Ok so you can flash any ROM with QFIL, and if you are not comfortable with TWRP, you can try removing your sdcard after flashing ROM, reboot to recovery and flash the OTA.zip.file.
Be aware that flashing with QFIL will also wipe your internal storage.
Sent from my Lenovo K5 Plus using XDA Labs

@adinechin thank you. I have updated to latest version.
Thankyou so much.
I have few questions.
1. Why we can't flash latest version directly from QFIL?
2. My phone gets shut down automatically if not in use. Is it something hardware related because it was fallen down once and I'm getting this annoying problem even after updating to newer build? Earlier I was thinking it is something software related but now I think its hardware problem. Do you have any idea to share on this?
It gets shut down only after not in use. If I use it for hours it works correctly but as soon I lock the screen it gets switched off and only after removing and reinserting the battery it will on again. No matter how long you press Power button it won't get on. Even recovery combination won't work until I remove and reinsert the battery.
Thanks a ton for helping me.

Apocalypse0 said:
@adinechin thank you. I have updated to latest version.
Thankyou so much.
Click to expand...
Click to collapse
Glad I helped you
Apocalypse0 said:
1. Why we can't flash latest version directly from QFIL?
Click to expand...
Click to collapse
You can, but I personally prefer to update via the phone to be sure all is back to normal stock
Apocalypse0 said:
2. My phone gets shut down automatically if not in use.
Click to expand...
Click to collapse
I have no idea on this subject, but with what you describe, it seems more likely to me that the phone is "stuck" than "off". I know it can happen some times if an app takes much memory, especially when you just installed the ROM, it takes some time to stabilize. Have you tried to wait a little when it was stuck like that and unlock it a bit later ? Another remark, instead of removing battery (which can be very annoying), try holding Power Vol+ and Vol- during around 10 seconds : you should reboot to download mode (black glowing screen like with QFIL), and then do it again, you should reboot your phone.

It was happening even on older build. Yes I waited and tried everything (key combinations) but nothing worked. That's why I feel its a hardware problem because of the fall the device took. No problem if I keep using it, no hanging problems or other things, but as soon I lock the screen it just gets switched off Very irritating.
Anyway, you've helped me a lot and I really appreciate the way you've kept everything simple because these things go really above my head.
Thanks again.