Database Users

[Guide] Easiest way from root to stock :)

I have read many posts, and did many tries.........we all know that Froyo ver that is out, is not a official one. In order to get Official OTA update, our phones must be in complete factory stage. Unlocked boot-loader is not an issue. Trust me, i tried many different ways to "unroot" my N1. Following many "how to's" uproot your N, in order to get OTA (Froyo), all tries have failed. I was flashing original roms (ERD79), replaced recovery image, and then i GOT an OTA with 2.1-update1, no sweat! Then, when it tried to install, there was an error every time. I was able to install that (ER27) update manually, but it was NOT the thing i wanted to accomplish. I knew that i will be able to receive next OTA with ver 2.2 (Froyo), but i also knew that this update will NOT install either. The problem is a recovery image! After been running many different custom roms, i have decide to try again to go back to the state from the beginning, so i can be sure i can be able to install official Froyo, when it is out. I was afraid to do this, but i did it anyway.............and it was successful. I restored my Nexus to the original state (except boot-loader of course), and after i got back to ERD79, momentarily i got OTA with ver 2.1-1. But this time, it has installed with no problem!!! I am running it right now, waiting for next (2.2) OTA update.
Ok, here we go:
Just go there and grab Google OEM file (PASSIMG.zip). Put it on your SD card (root dir).
Then restart your phone into boot-loader (trackball+power button).
Once there, top power button again. It will look for passimg file as always. It will load the passimg file. Note the blue status bar at right-upper corner of your screen.
Then, it will check that file, and finally you will see "do you want to start update?"
Press Volume UP, for YES............and wait.
After phone reboots - you are done! Completely back to stock!
Then you can go to "menu-settings-about-system updates" and you should see that your phone is already downloading update 2.1-1.
That is it.
If for some reason you end up with android screen with triangle and exclamation mark, just press VOL up and Power, at the same time, you will get into recovery screen, and reboot your phone from there.
One more thing...........i did that in my own risk
{
"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"
}
So, please do not blame me, if something would happen to you Nexus (phone just exploded, or something....
)

Wow..can't get any simpler than that..thx for this.

Thanks. Very simple.

this effectively make it so that if you root your phone and void the warranty you can unroot and regain your warranty?

This might be totally unrelated, but I finally just rooted my phone a few hours ago, so I'm a noob. I created a nand backup of my factory install. Then I installed cyanogen and some apps, then did another nand backup and think I wiped my factory nand backup. I wanted to keep that. Is there anyway I can get my factory image back for future use? How do you save a new nand backup as a different file name so this won't happen? I don't see how to do this...thanks.
-------------------------------------
Sent via the XDA Tapatalk App

Wow... Much appreciated!

laughter95 said:
this effectively make it so that if you root your phone and void the warranty you can unroot and regain your warranty?
Click to expand...
Click to collapse
Nope. Even if you unroot your phone, your bootloader cannot be locked back again (if you unlocked it). Rooted or not, if your bootloader was unlocked, you always get that unlocked padlock image on your first screen when you turn on your phone. However, I read somewhere that someone has sent his phone back for warranty exchange, after he revert everything to factory stage (except bootloader of course) and they (HTC) accepted. I don’t know how that happened...maybe they (HTC) overlooked that first screen??

As far as I know...this thread is total BS.
You CANT revert to a previous version of Android going through the bootloader's update.
You MUST pick up a stock (I did with a stock Froyo's) Nandroid backup and restore it from Amon's recovery. You'll lose root and your recovery will revert to stock anyway.

justclimb said:
As far as I know...this thread is total BS.
You CANT revert to a previous version of Android going through the bootloader's update.
You MUST pick up a stock (I did with a stock Froyo's) Nandroid backup and restore it from Amon's recovery. You'll lose root and your recovery will revert to stock anyway.
Click to expand...
Click to collapse
HA ha ha! You did NOT understand what i wrote! Read it again....and what if one does NOT have a Nan backup at all??
" You MUST pick up a stock (I did with a stock Froyo's) Nandroid backup and restore it from Amon's recovery. " <= that's total BS!!

Would this work on the AT&T N1?

RogerPodacter said:
This might be totally unrelated, but I finally just rooted my phone a few hours ago, so I'm a noob. I created a nand backup of my factory install. Then I installed cyanogen and some apps, then did another nand backup and think I wiped my factory nand backup. I wanted to keep that. Is there anyway I can get my factory image back for future use? How do you save a new nand backup as a different file name so this won't happen? I don't see how to do this...thanks.
Click to expand...
Click to collapse
Creating multiple nand backups doesn't overwrite the previous one. It creates a new folder each time, with the timestamp as the folder name. Unless you specifically went into your sd card and deleted the folder containing the first nand backup, it's still there If you click Restore in Recovery, you'll be given a list of all the backups you created.
And you can always go back to the factory image using the ROM here: http://forum.xda-developers.com/showthread.php?t=614850

This might be totally unrelated, but I finally just rooted my phone a few hours ago, so I'm a noob. I created a nand backup of my factory install. Th
Click to expand...
Click to collapse
Creating multiple nand backups doesn't overwrite the previous one. It creates a new folder each time, with the timestamp as the folder name. Unless you specifically went into your sd card and deleted the folder containing the first nand backup, it's still there If you click Restore in Recovery, you'll be given a list of all the backups you created.
And you can always go back to the factory image using the ROM here: http://forum.xda-developers.com/showthread.php?t=614850
Click to expand...
Click to collapse
Awesome good to know. But when I went into restore I only saw one file. But maybe I just needed to click into that and would have seen 2 restore files.

RogerPodacter said:
Awesome good to know. But when I went into restore I only saw one file. But maybe I just needed to click into that and would have seen 2 restore files.
Click to expand...
Click to collapse
Yeah, it should be something like "HTP123990" which is your device number. Click once more and it'll show all the backups for that device.
Or just browse your SD card to the nandroid folder with a file manager like Linda:

wow thanks! it's so easy to use..and works!
i had so many problems with the froyo 2.2..though i really LOVE the speed and the new interface...but afterwards decided to switch back to 2.1 wait for official OTA...
thanks op!

shouldnt the name of this thread be "from FROYO to stock" not "from ROOT to stock"? because this has nothing to do with root, its just going from froyo back to shipping rom.

http://forum.xda-developers.com/showthread.php?t=686593

Well coming from a rooted MoDaCo rom, I performed the steps and am now running the stock ROM and just been informed that there is an update available. Update is installing now and it works great.
Now I have my stock OS back while still rooted, and getting updates.
I just recently got my Nexus one a few days before Froyo hit. I've been sporting Froyo while traveling and getting barely any coverage. So this is a good test.
I'm on Fringe coverage now. With Froyo and its radio, I kept getting network disconnects. Flashing back to stock+update = 2/3 bars of EDGE.
Finally!

RogerPodacter said:
shouldnt the name of this thread be "from FROYO to stock" not "from ROOT to stock"? because this has nothing to do with root, its just going from froyo back to shipping rom.
Click to expand...
Click to collapse
It's the fastest way to reload stock recovery/image/radio altogether.

Not true. I can confirm the method in this thread.
justclimb said:
As far as I know...this thread is total BS.
You CANT revert to a previous version of Android going through the bootloader's update.
You MUST pick up a stock (I did with a stock Froyo's) Nandroid backup and restore it from Amon's recovery. You'll lose root and your recovery will revert to stock anyway.
Click to expand...
Click to collapse

If i use mybackup pro to backup apps and data, how do I restore that stuff once I'm unrooted? Do you have to redownload mybackup pro? Sorry if this is obvious to some, I'm new to android and really want to be able to get the OTA update. Basically I'm wondering how the people that have used this method got all their info and apps back, Thanks.

[GUIDE] How to Install Cyanogenmod 7.1 from Stock 2.1

The procedure is quite simple.
Step 1.
Download the following tools:
Cyanogen Mod 7.1 for Xperia X8 (code named Shakira)
FlashTool
FXP030 kernel (2.6.29)
Step 2.
Step 2.1
Follow the guide located here to unlock your bootloader, do this before continuing with the rest of this guide it is important to have your stock firmware rooted for this step.
Step 2.2
Unzip flashtool to its own folder e.g. /Flashtool/.
Unzip FXP030 kernel to the Flashtool/firmwares/ folder - the directory should look like this:
{
"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"
}
Step 3.
Step 3.1
Open Flashtool and click on the 'Flash' button, select the FXP firmware from the list on the left hand side and click OK.
Step 3.2
Follow the on screen instructions.
Step 4.
Copy the update-cm-7.1.0-X8-signed.zip to the root of your MicroSD Card as shown below. (Please note that you can do this using a MicroSD Card reader OR your USB cable.
If you do not have a card reader then switch your phone on after flashing the FXP kernel and when you see the FreeXperia logo, repeatedly press the Back button until CWM loads. Once CWM has loaded scroll down to the Mounts and Storage menu. Once on the mounts and Storage menu scoll down to mount USB Storage and copy the update-cm-7.1.0-X8-signed.zip file to the root of the SD card.
Step 5.
Load CWM via the method described in Step 4 and select 'Install Zip from SD card.' then select 'Choose Zip from sdcard' and select the update-cm-7.1.0-X8-signed.zip that you copied over to the root of the SDCard in the previous step, Select the yes option using the volume buttons and let CWM work its witchcraft.
Step 6.
Go back to the main menu of CWM and select 'wipe data/factory reset'.
Next from the main menu of CWM select 'wipe cache partition'.
Finally from the main menu of CWM select 'Advanced' and 'wipe dalvik cache.
Optional
If you want the google apps installed you can download them here. To install them perform Step 4 through to Step 5 and instead of copying 'update-cm-7.1.0-X8-signed.zip' to the root of your sdcard, copy gapps-gb-20110613-signed.zip instead. All instructions in Step 4 and Step 5 that state you should use 'update-cm-7.1.0-X8-signed.zip' should use the file 'gapps-gb-20110613-signed.zip' instead.
Notes:
I'm having issues with the networking with this custom firmware, specifically the network (3G or WiFi) seems to 'drop' after any amount of small usage. If I use a Browser or the Market place for a short amount of time, they simply end up unable to load any pages whilst android reports that wifi/3g signal strengths are full. I tested the connectivity using ping commands from terminal and pings are succesfull. I'm unsure where the issue lies. I suspect however the issue is in the FXP Kernel, some people have reported using FXP 028 Kernel resolves the issues but I've been unable to find them.
Anyway I hope this helps people who are confused as to how to install this.
Credits:
Thanks to Paschalis for correcting an error in my wording.
Thanks go to dbts25 for pointing out mistakes and un-neccessary steps in the guide, sincethen the guide has been edited to be easier to follow and less convoluted.
Thanks go to rav3n_pl for the revised bootloader bundled with the kernel.

Vanilla is the AOSP, Android Open Source Project..
You mean stock, right?
Btw this kernel has wifi issues?
Tried many kernels, and wifi wont open with none of them..

Paschalis said:
Vanilla is the AOSP, Android Open Source Project..
You mean stock, right?
Btw this kernel has wifi issues?
Tried many kernels, and wifi wont open with none of them..
Click to expand...
Click to collapse
Ah Yes, I mean stock. It's 2:34am... That's my excuse haha, between university and sleep deprivation the mistakes keep mounting hehe. Thanks for pointing that out anyways.
And yes, it seems this kernel has issues with data connectivity, and call volume as well for some odd reason. It boggles the mind as to why it's been labelled 'stable'. Stable usually means it's solid and won't fall over and die, plus data connectivity on an android handset is really a critical feature, if it is buggy the custom firmware should not be labelled as stable.

It really need custom kernel?

Hehe.. Same university thing here, only difference here its 4:40, and got lesson at 8:30..
On my other phone, CM is beta and not Official yet, and its working perfectly, except 2 special features they didnt port yet, from stock rom..
If you find the 28 kernel, post it, until they release the 31!
Thanks!

EL_BELLACO said:
It really need custom kernel?
Click to expand...
Click to collapse
Yes, if you don't use a custom firmware it will get stuck in a boot loop and be unable to boot.
Paschalis said:
Hehe.. Same university thing here, only difference here its 4:40, and got lesson at 8:30..
On my other phone, CM is beta and not Official yet, and its working perfectly, except 2 special features they didnt port yet, from stock rom..
If you find the 28 kernel, post it, until they release the 31!
Thanks!
Click to expand...
Click to collapse
If I come across it I will, I'll edit my guide to feature it as a work around for connectivity issues for people in the meantime, if it works correctly.
I've got to admit though, issues aside - it is amazing what the open source community is capable of creating. CM 7.1 looks absolutely fantastic, I love the boot animation.

I have tried FXP028, FXP030 and the one that is included with the CM7.1 release, i'm having network problems with all of them.

termin8tor said:
.
Step 5.
Turn your phone on and repeatedly press the back button until you are displayed with the CWM menu. On this menu select 'install zip from sdcard' and then choose the 'choose zip from sdcard' select the cyanogenmod file you downloaded and let it do its thing.
Click to expand...
Click to collapse
In step 5 you forgot one thing:
Flash Google Apps. You can find it here: http://cmw.22aaf3.com/gapps/gapps-gb-20110613-signed.zip
Step 2 is unnecessary, because CWM Recovery is built-in FXP Kernel so you don't need to install it.

poisike said:
I have tried FXP028, FXP030 and the one that is included with the CM7.1 release, i'm having network problems with all of them.
Click to expand...
Click to collapse
Can you please share the FXP028 kernel?

has any of you tried the dx kernel yet? with cynanogen mod 7.1

No workie. Rom+kernel need match.
An I wrote it that way:
http://forum.xda-developers.com/showpost.php?p=18364335&postcount=1879

dbts25 said:
In step 5 you forgot one thing:
Flash Google Apps. You can find it here: http://cmw.22aaf3.com/gapps/gapps-gb-20110613-signed.zip
Step 2 is unnecessary, because CWM Recovery is built-in FXP Kernel so you don't need to install it.
Click to expand...
Click to collapse
I've edited the guide to eliminate that pointless step in the original guide version, thankyou for pointing it out!
Additionally the google apps step has been added to the end of the tutorial.
tonks22 said:
has any of you tried the dx kernel yet? with cynanogen mod 7.1
Click to expand...
Click to collapse
Unfortunately the rom will not boot with the DX kernel, I tried it myself and it gets stuck in a boot loop.
rav3n_pl said:
No workie. Rom+kernel need match.
An I wrote it that way:
http://forum.xda-developers.com/showpost.php?p=18364335&postcount=1879
Click to expand...
Click to collapse
I have included the correct kernel for the official cyanogenmod 7.1 rom and slipstreamed your edited loader into the kernel package for peoples convenience. Thanks for linking me to your post!
Hope this helps people!

It seems that this Rom and kernel [cm7] doesn't work.When i flash the kernel my SD is not recognized.And if i uninstall the kernel and try to flash the rom...i get a biiiiigg eror

i hope that they will also make a ROM that is compatible with stock kernel so that it will be easy to install... im having second thought of unlocking my bootloader because of this:
Before I start I must emphasise the fact that meddling with the bootloader is highly dangerous and will result in a hard brick if you don't follow proper instructions. Then, you will have to go and repair your phone by sending it to SE . I am not responsible if your phone dies on you because you didn't follow instructions or you screwed up somehow. I must also mention that this will probably void your warranty (rooting already probably voided it though) and that there is NO WAY to relock bootloader as of now.
Click to expand...
Click to collapse
i know they can make one because they are great programmer...

if you have bought your phone unlocked, things are pretty simple..
That tutorial, should be writtenmore clearly/easy..
Cos in fact its not too dificult..
Sent from my MB860 using XDA App

Paschalis said:
if you have bought your phone unlocked, things are pretty simple..
That tutorial, should be writtenmore clearly/easy..
Cos in fact its not too dificult..
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
yes i bought my phone from SE and its already unlocked... i think i'll try it when this ROM will be released as a completely working ginger without bugs...
i find this http://forum.xda-developers.com/showthread.php?t=1254225
as very informative but confusing tutorial... is there any other short and simple tutorial here??

mikel_0004 said:
yes i bought my phone from SE and its already unlocked... i think i'll try it when this ROM will be released as a completely working ginger without bugs...
i find this http://forum.xda-developers.com/showthread.php?t=1254225
as very informative but confusing tutorial... is there any other short and simple tutorial here??
Click to expand...
Click to collapse
There:
http://forum.xda-developers.com/showpost.php?p=17656148&postcount=1

Can it be installed WITHOUT unlocking the bootloader?
Thanks

thu001 said:
Can it be installed WITHOUT unlocking the bootloader?
Click to expand...
Click to collapse
I`m not 100% sure that cm71 rom will work on stock kernel...
When I flashed it under installed CM7 it stuck on bootanimation. Mybe full wipe? Not tried.

Hello
I installed on my Xperia X8 CM7.1 (I had version 2.1 of Android root), but it does not work the WiFi network and the 3G connection is disconnected, it did not work properly Market (having installed the GAPPS). My question, is there any way to get back to my terminal to android 2.1? I did a Back up of my system, but in trying to restore from CWM mistake I make, I guess it is for the kernel.

Marshmallow 6.0 on a SM-J320FN?

is this possible? i can't seem to find anywhere to download/flash the OS? but i am new to this, so maybe lookingp in the wrong places.
any help gratefully received!

secretmachines said:
is this possible? i can't seem to find anywhere to download/flash the OS? but i am new to this, so maybe lookingp in the wrong places.
any help gratefully received!
Click to expand...
Click to collapse
Ok, It seems like you need help!
So J320FN isn't getting Marshmallow, but there are what we call in XDA and anywhere else, Custom ROMS!
Now this practically optimizes your device for better performance, along with a newer version of Android!
When you searched for your device (SM-J320FN) you probably found LineageOS.
LineageOS is a Custom ROM for a big variety of devices.
Now for the J320FN we have LineageOS 13.0 (Marshmallow) and LineageOS 14.1 (Nougat), while have LineageOS 15 (Oreo) in the works thanks to our crew including the Main dev, djeman.
Now to flash Custom ROMS you need a recovery which you flash via Odin.
Then copy the ROM zip to the SD or Device storage.
Boot into recovery by holding VOL. UP+POWER+HOME at boot.
Wipe Dalvik Cache, Cache, Data, Internal Storage (If you put ROM on SD) and System.
Then Flash the ROM with Gapps (Google Apps, Such as Play store...)
Wait and Reboot

Diamond26 said:
Ok, It seems like you need help!
So J320FN isn't getting Marshmallow, but there are what we call in XDA and anywhere else, Custom ROMS!
Now this practically optimizes your device for better performance, along with a newer version of Android!
When you searched for your device (SM-J320FN) you probably found LineageOS.
LineageOS is a Custom ROM for a big variety of devices.
Now for the J320FN we have LineageOS 13.0 (Marshmallow) and LineageOS 14.1 (Nougat), while have LineageOS 15 (Oreo) in the works thanks to our crew including the Main dev, djeman.
Now to flash Custom ROMS you need a recovery which you flash via Odin.
Then copy the ROM zip to the SD or Device storage.
Boot into recovery by holding VOL. UP+POWER+HOME at boot.
Wipe Dalvik Cache, Cache, Data, Internal Storage (If you put ROM on SD) and System.
Then Flash the ROM with Gapps (Google Apps, Such as Play store...)
Wait and Reboot
Click to expand...
Click to collapse
thanks so much @Diamond26!
i'd played around with a couple of installations with no joy... but in the process have installed Odin, so am aware of that.
my main reason for wanting to do this, is to be able to access adaptable storage. 8gb device space is a joke! I've installed maybe 2 or 3 apps, but apps can't be updated as it's already out of space (even though 400mb is available)! totally unusable!
i'll try this out... i may be back

secretmachines said:
thanks so much @Diamond26!
i'd played around with a couple of installations with no joy... but in the process have installed Odin, so am aware of that.
my main reason for wanting to do this, is to be able to access adaptable storage. 8gb device space is a joke! I've installed maybe 2 or 3 apps, but apps can't be updated as it's already out of space (even though 400mb is available)! totally unusable!
i'll try this out... i may be back
Click to expand...
Click to collapse
My Pleasure :fingers-crossed:

so i think the developer setting was turned off and i started to get the FRP lock problem.
i managed to use Odin to reinstall Android, but it is now stuck in bootloop.
i've installed Kies3 and Smart Switch, but neither recognise the handset (not compatible), so i can't reinstall firmware, etc.
i'm kinda stuck... help!

secretmachines said:
thanks so much @Diamond26!
i'd played around with a couple of installations with no joy... but in the process have installed Odin, so am aware of that.
my main reason for wanting to do this, is to be able to access adaptable storage. 8gb device space is a joke! I've installed maybe 2 or 3 apps, but apps can't be updated as it's already out of space (even though 400mb is available)! totally unusable!
i'll try this out... i may be back
Click to expand...
Click to collapse
Im currently on a J320FN with a stock 5.1 rom (manually updated via sammobile) but have instead done the following :
1. Got a good Android kitchen (A bash/shell program that makes creating roms easy as could be) I woukd suggest SuperR's Kitchen due to it being the most updated one. On XDA portal?
2. Downloaded the firmware i want from sammobile.
3. Debloated the rom (option in the kitchen to remove unwanted apps from system/app or system/priv-app) making space.
4. Added Supersu (again the kitchen walks you through all the options for rooting the rom).
5. Added my own apps to run as system (such as adaway or nova launcher to replace TouchWiz)
6. Created the rom and flashed the zip.
Now im on partitioning the system block in order to save 2gb of space i dont need since the new system is 780mb from 1.9gb..
Both ways are good and safe / stable if you are careful, it's just that one provides updates and sources and build threads (LOS) , the other is a great and fun way to learn more about android and rom building plus you get to have it 100% YOUR WAY.. With building your own rom using the kitchen you can even go as far as editing the settings apk to rearrange the options or add ur own... And many more thing to discover...
Good luck no matter what you choose to take from this wonderful community!
Peace

secretmachines said:
thanks so much @Diamond26!
i'd played around with a couple of installations with no joy... but in the process have installed Odin, so am aware of that.
my main reason for wanting to do this, is to be able to access adaptable storage. 8gb device space is a joke! I've installed maybe 2 or 3 apps, but apps can't be updated as it's already out of space (even though 400mb is available)! totally unusable!
i'll try this out... i may be back
Click to expand...
Click to collapse
I tried it for the same reason and it turned out to be a mistake. The rom I tried (Lineage 13) is full of display bugs. Now I lost my original firmware and probably voided the warranty. Your best bet is just to move your apps to the SD card instead

idklol123 said:
I tried it for the same reason and it turned out to be a mistake. The rom I tried (Lineage 13) is full of display bugs. Now I lost my original firmware and probably voided the warranty. Your best bet is just to move your apps to the SD card instead
Click to expand...
Click to collapse
Your warranty is void, im sure Lineage OS has the appropriate notice about this..
Yiu could seek help about your issue, perhaps there is something along the lines that you missed.. Wiping dalvik and or cache and re trying it could help..You should always do a nandroid backup using twrp or cwm recovery or even Titanium Backup / My Backup Pro. It is something that you should practice since you're messing with any type of software and hard-flashing firmware.
Again, consider a stock rom with root and xposed module, a partitioned system block and deodexed apks..
You can get firmware releases for your country and carrier from sammobile.com anfd flash it via odin. That should give you OTA updates and stock stability...
Peace

Kaiyum said:
Im currently on a J320FN with a stock 5.1 rom (manually updated via sammobile) but have instead done the following :
1. Got a good Android kitchen (A bash/shell program that makes creating roms easy as could be) I woukd suggest SuperR's Kitchen due to it being the most updated one. On XDA portal
2. Downloaded the firmware i want from sammobile.
3. Debloated the rom (option in the kitchen to remove unwanted apps from system/app or system/priv-app) making space.
4. Added Supersu (again the kitchen walks you through all the options for rooting the rom).
5. Added my own apps to run as system (such as adaway or nova launcher to replace TouchWiz)
6. Created the rom and flashed the zip.
Now im on partitioning the system block in order to save 2gb of space i dont need since the new system is 780mb from 1.9gb..
Both ways are good and safe / stable if you are careful, it's just that one provides updates and sources and build threads (LOS) , the other is a great and fun way to learn more about android and rom building plus you get to have it 100% YOUR WAY.. With building your own rom using the kitchen you can even go as far as editing the settings apk to rearrange the options or add ur own... And many more thing to discover...
Good luck no matter what you choose to take from this wonderful community!
Peace
Click to expand...
Click to collapse
This is the best thing i heard so far!
I was looking for this. I like the UI of Samsung, and it was stable and fast for me for daily usage. Had some bad experiences with LOS and RR so i was thinking of re-flashing stock, then rooting and then removing system apps. The only issue i have is too little free space. Is the effect same if i do that compared to your method? Can you tell me what happened to your little experiment? How much free space do you have?
Can i flash your modified rom and get it to work on my phone?

hi everyone, sorry to ask again, i seem to be going round in circles! can anyone advise the next step?
- i installed lineageOS ok, but must have accidentally turned off OEM Unlock, so am now getting "Blocked by FRP Lock
- i reinstalled a version of original firmware, but that is getting stuck in bootloop
- i've tried reinstalling original firmware downloaded from sammobile, with Odin, but that fails
- i've installed Kies and Smart Switch on my PC, but both say the handset is not supported, so I can't install firmware that way
what should i try next?

djaneski said:
This is the best thing i heard so far!
I was looking for this. I like the UI of Samsung, and it was stable and fast for me for daily usage. Had some bad experiences with LOS and RR so i was thinking of re-flashing stock, then rooting and then removing system apps. The only issue i have is too little free space. Is the effect same if i do that compared to your method? Can you tell me what happened to your little experiment? How much free space do you have?
Can i flash your modified rom and get it to work on my phone?
Click to expand...
Click to collapse
Im sorry im replying so late,given your post i take it you need some help...I wont go big here and tell you i can fix exactly what you want,however i have managed to get it all working besides repartitioning the mmcblk0!
Im out of town during weekends for work but i can possibly have a rom ready for you by Monday night (GMT+2).
I will still recommend you download SuperR's Kitchen (if possible the donate version)and start cooking your own rom,the kitchen provides 100% j3xnlte and j3 variants!
You WILL need to download the firmware i will point you to for the modem but its for better use also,you can run the stock for a while and then flash (mine or your own) the debloated/deknoxed/lighter version.
About the space,i have attached a SS from my Smart Manager..I have magisksu,magisk-xposed,iYTBP,gapps pico + photos,swiftkey replacing Sammy Keyboard and nova launcher replacing TW..FFox,Yahoo Mail,TiBu,Lucky Patcher and Facebook / Messenger...Some i have placed as system apps and others preinstalled as user apps (such as Busybox and Telsa Unread or Adaway that don't work correctly when placed in /system/app)..
Still i have Airdroid moving files locally and have at least 600mb of romzips being moved all the time while flashing....
That 5.1Gigas you see are 100% usable for me because i can swap system and data apps to my liking...also trust me,if you have relationship issues with googke,debloated roms come down to 1/3 of original size...
Let me know what i can help with,have a blasting weekend!
Peace
{
"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"
}
Sent from the depths of outer space using highly potent telepathically altering mushrooms.
---------- Post added at 09:45 PM ---------- Previous post was at 09:31 PM ----------
secretmachines said:
hi everyone, sorry to ask again, i seem to be going round in circles! can anyone advise the next step?
- i installed lineageOS ok, but must have accidentally turned off OEM Unlock, so am now getting "Blocked by FRP Lock
- i reinstalled a version of original firmware, but that is getting stuck in bootloop
- i've tried reinstalling original firmware downloaded from sammobile, with Odin, but that fails
- i've installed Kies and Smart Switch on my PC, but both say the handset is not supported, so I can't install firmware that way
what should i try next?
Click to expand...
Click to collapse
Download TWRP if im not mistaken by djeman and flash that through odin!That passes just make sure to UNTICK auto reboot so you can reboot to recovery after removing battery(or just ignore the unticking if ure d
fast enough to hold vol up + home + pwr while the flash resets)
Wipe system,dalvik,cache,data and reboot...
Sent from the depths of outer space using highly potent telepathically altering mushrooms.

My gf got this phone for Christmas, it's 2017 why are (many) retailers selling a phone that is still on Android 5.1?..

Galaxy S4 Play Edition (GT-I9505G) and Lineage OS 15.1

Hello folks,
I have Galaxy S4, Play Edition, GT-I9505G, currently running SlimROM 7.1.2 build 1.17 (dated 20180115) and baseband version I9505GUEUDNL3.
Last stock I had on this phone was Android 5.0. If there was any OTA after that, I didn't install it.
(Sam Mobile does not list this device, hence no way of knowing firmwares, but https://forum.xda-developers.com/wiki/Samsung_Galaxy_S_4/GT-I9505G lists mine as the last firmware.)
I have been trying to install Lineage 15/Oreo ROMs and with every ROM I am getting Error 7, which is supposedly Recovery error but every time I have used the recovery recommended by the ROM administrator. So its definitely not a recovery issue in my case.
I was wondering, those with same device, managed to install Oreo ROM, what is your baseband version? Most likely, this is the culprit, but to be sure, I would like to know at least one person with same device and different baseband version that managed to install Oreo ROM.
This page (https://forum.xda-developers.com/galaxy-s4/i9505g-develop/odin-images-i9505g-t3271624) list a lot of stock ROMs. Mine is half way through. Hence, I would like to see someone with newer baseband running Oreo ROM.
Many thanks in advance.

Did you check the updater script to ensure the phone's model # is included?

audit13 said:
Did you check the updater script to ensure the phone's model # is included?
Click to expand...
Click to collapse
Yes. All the ROMs I tried were for I-9505 of which I-9505G is a variant. I also removed that part of the script, just in case, but the same error occurred.

fuzzychicken said:
Yes. All the ROMs I tried were for I-9505 of which I-9505G is a variant. I also removed that part of the script, just in case, but the same error occurred.
Click to expand...
Click to collapse
Maybe you need to add the gt-i9505g to the list rather than removing it.

audit13 said:
Maybe you need to add the gt-i9505g to the list rather than removing it.
Click to expand...
Click to collapse
It was already there, so the ROMs were compatible but I removed just in case, thought if it is not working with the model number in it, maybe I can try without it, as recommended on some other blog posts on the web.

I guess the only other thing would be to try different versions of TWRP.

audit13 said:
I guess the only other thing would be to try different versions of TWRP.
Click to expand...
Click to collapse
I am sorry, thats what I said in the OP. I have tried every possible version of TWRP that was recommended for those ROMs and the error keep showing up. That indicates that its not recovery that is causing the problem.

Only thing left I can think of would be to flash the latest stock ROM, factory wipe, flash twrp, then wipe, and then flash the custom ROM.

audit13 said:
Only thing left I can think of would be to flash the latest stock ROM, factory wipe, flash twrp, then wipe, and then flash the custom ROM.
Click to expand...
Click to collapse
That is what I am thinking but I am not too sure which is the latest stock ROM.
https://forum.xda-developers.com/galaxy-s4/i9505g-develop/odin-images-i9505g-t3271624 On this page, there are loads of stocks. Mine is half way through. Its I9505GUEUDNL3_FULL. Assuming that the list goes down as newer stocks, esp looking at the last 3 alpha-numerics, should I be flashing I9505GUEUDPF1_FULL?
If I flash, I9505GUEUDPF1_FULL will it write new bootloader and baseband? If yes, do I have to go through whole unlock bootloader thing? or just flash twrp via Odin and go ahead with newer ROM? This is the most sticky part as I don't remember how I did it in the past. I just don't touch something I am not very clear understanding on, but this time I would like to update to Oreo, primarily for security purpose and the cash is tight so if I brick this, I wouldn't be very happy to buy another device. Hence trying to dot all i's and cross all t's.
Thanks for all help in advance.

Flashing a stock ROM with Odin will update the bootloader and modem.
The bootloader is not locked and has never been locked on the gt-i9505.

audit13 said:
Flashing a stock ROM with Odin will update the bootloader and modem.
The bootloader is not locked and has never been locked on the gt-i9505.
Click to expand...
Click to collapse
Thank you.
Let me put it in steps, pls correct me if I am wrong.
1. Flash I9505GUEUDPF1_FULL using Odin. Once rebooted, confirm if newer baseband is present. Check if the calls and data works.
2. Flash TWRP recovery using Odin (it will revert to stock recovery, right?) If not, alls good as it is.
3. Install ROM of choice.
There is no data on the phone, I reflashed SlimROM after all attempts of Oreo failed.
Anything tricky stuff in between?
Thanks in advance.

To prevent the stock recovery from overwriting twrp, uncheck everything in Odin except for reset time, flash twrp, when you see the word "reset" in the status window, remove the usb cable from phone, remove the battery, replace the battery, boot into twrp.

audit13 said:
To prevent the stock recovery from overwriting twrp, uncheck everything in Odin except for reset time, flash twrp, when you see the word "reset" in the status window, remove the usb cable from phone, remove the battery, replace the battery, boot into twrp.
Click to expand...
Click to collapse
I am very sorry to be a PITA, mate, but I really need help here.
As per the suggestions, I tried flashing various images. In every image I flashed, the calling and wifi worked but cell data didn't work in any of those versions. Still I tried flashing Oreo with them but the error persisted. So probably, its something beyond I can do it with my little knowledge.
So finally, to give up I tried going to back to where I was before all this, to baseband version, I9505GUEUDNL3. I flashed NL3 image linked in the post https://forum.xda-developers.com/galaxy-s4/i9505g-develop/odin-images-i9505g-t3271624 through Odin. While the OS shown in about phone is 5.0, the baseband version is stuck at OJ1, where the data does not work.
Any idea how I can go back to NL3 where data worked flawlessly?
Many thanks in advance.
Edit: I flashed NL3 modem from https://forum.xda-developers.com/showthread.php?t=2452034 but still the issue persists. I have nandroid backups from the very first time when I flashed another ROM. If I use that to restore, will it restore all the issues?

The bootloader and modem should be flashed in tandem to maintain compatibility with each other. Data may not be working due to a mismatch.
Flash the latest stock ROM from sammobile.com, updato.com, or samsung-firmware.org.

audit13 said:
The bootloader and modem should be flashed in tandem to maintain compatibility with each other. Data may not be working due to a mismatch.
Flash the latest stock ROM from sammobile.com, updato.com, or samsung-firmware.org.
Click to expand...
Click to collapse
Thank you.
Can you pls take a look at this thread? https://forum.xda-developers.com/galaxy-s4/i9505g-develop/odin-images-i9505g-t3271624 Supposedly, these are factory images. I tried these images and my best guess is, they have right bootloader and modem. None of the sites you suggested carry stock images for GT-I9505G (Play Edition). They have GT-I9505 though.
What I tried so far.
- Flashed images linked above. Didn't work
(at one point, I even got OTA, when I was on OE1 baseband, it updated to OJ1. So in theory, in this OTA, it should fix this mismatch bootloader and modem, right?) When things didn't change after this update. I tried to flash NL3 image.
- Flashed NL3 image which I had. The baseband remained at OJ1. This was odd to me. So flashed NL3 modem. The issue persisted.
- I had taken nandroid backup before I started flashing custom ROMs. I tried to restore that back up through a custom recovery, TWRP. No help.
Screenshot of that backup, if it tells you anything
{
"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 EFS Backups, but I don't quite remember how I took that backup.
Screenshot attached. Any idea if this can be used to restore everything in one shot. I don't know if EFS contains bootloader as well.
You mentioned I should flash stock ROM. Assuming that ROM images linked on the XDA thread above are untouched, shouldn't that fix the issue? If not, is there any possibility one can find bootloader images (if such thing exists) because modem images are available in another thread. One can pick and choose a combination to flash. I am just speculating. I have no idea if such a thing can be done.
Thank you so much. Really appreciate you sticking around to share the ideas.
P.S. - Is there any option where you can delete both bootloader and modem just before flashing the stock ROM via Odin or TWRP?

There is no need to deal with the EFS at this moment as long as the phone is showing the correct IMEI and MAC address.
Yes, those look like factory images and you should try the latest ROM which is PF1. It's possible that the phone was running a newer bootloader than the one found in the NL3 ROM. Some boot loaders cannot be downgraded.
You cannot delete the bootloader from the phone. Without a bootloader, the phone would function. It's similar to the BIOS of a PC.

It is not TWRP that's the problem - it's the size of your system / user partitions on the 9505g.
@side said he would have a fix in version 4 OptLos for this.
His solution is not something I will be implementing in Resurrection Remix however.

audit13 said:
There is no need to deal with the EFS at this moment as long as the phone is showing the correct IMEI and MAC address.
Yes, those look like factory images and you should try the latest ROM which is PF1. It's possible that the phone was running a newer bootloader than the one found in the NL3 ROM. Some boot loaders cannot be downgraded.
You cannot delete the bootloader from the phone. Without a bootloader, the phone would function. It's similar to the BIOS of a PC.
Click to expand...
Click to collapse
So I flashed PF1 stock ROM, both bootloaders and modems are PF1. Made sure over the full day yesterday, there is no update and the problem persists. Can't flash Oreo and no cell phone data. Now, my interest in Oreo has pretty much died and only hoping to find a tweak to fix cell phone data. Fixed APN, made a factory reset just to be sure that its not the issue, tried SIM card in the different phone and other SIM in my phone that its not the SIM or the network thats the cause. So far I have not managed to find out what made the phone lose cell phone data.
Buff99 said:
It is not TWRP that's the problem - it's the size of your system / user partitions on the 9505g.
@side said he would have a fix in version 4 OptLos for this.
His solution is not something I will be implementing in Resurrection Remix however.
Click to expand...
Click to collapse
Dang man, your comment came a little late after I managed to fcuk up my phone very well trying to install Oreo. It will be great if you folks can make this comment in OP of the respective ROMs so that next I9505G user won't mess it up royally the way I did. If I remember correctly, I read both the threads start to the end and I didn't find any comment on this issue of I9505G.
Thanks both of you for chiming in and trying to help. If there is any idea to fix the loss of cell phone data, that will be of great help.

Finally Android pie

I followed this guy's post so I'm just going to link his directions over here
https://forum.xda-developers.com/honor-view-10/development/rom-aosp-pie-t3829466/page3
Got this to boot on my phone, finally.
I have an Honor 7x.
I removed the assert line and uploaded the file here
https://drive.google.com/file/d/1Wth0N14bKM1WM2VGXdJN91fPBXzdnsCQ/view?usp=drivesdk
1. Go back to stock using hurupdater, this is a must. I tried coming from a different ROM, and it bootlooped and nothing would stop the bootloop.
2. Factory reset in stock recovery
3. Flash back twrp in fastboot, I used this one https://drive.google.com/open?id=18u...QgwleMIOjsZd7S
4. Flash the rom and bitgapps in one go
5. Factory reset in twrp, format data, and also factory reset in stock recovery
6. It will bootloop you to erecovery, just tap "Reboot" again, and it will boot to the ROM.
7. Enjoy Android P on your phone
This is running pretty damn good for it not to be for our device no bugs as of yet

bugs
dcraffam said:
I followed this guy's post so I'm just going to link his directions over here credits to @crayonicle
https://forum.xda-developers.com/honor-view-10/development/rom-aosp-pie-t3829466/page3
Got this to boot on my phone, finally.
I have an Honor 7x.
I removed the assert line and uploaded the file here https://drive.google.com/drive/folde...fY?usp=sharing
1. Go back to stock using hurupdater, this is a must. I tried coming from a different ROM, and it bootlooped and nothing would stop the bootloop.
2. Factory reset in stock recovery
3. Flash back twrp in fastboot, I used this one https://drive.google.com/open?id=18u...QgwleMIOjsZd7S
4. Flash the rom and bitgapps in one go
5. Factory reset in twrp, format data, and also factory reset in stock recovery
6. It will bootloop you to erecovery, just tap "Reboot" again, and it will boot to the ROM.
7. Enjoy Android P on your phone
This is running pretty damn good for it not to be for our device no bugs as of yet
Click to expand...
Click to collapse
There are following bugs on honor 7x:
1. Hotspot not working.
2. Usb connecetion to pc is charge only can use to transfer files.
Also the camera has too much noice.
there maybe more but these are all that I finded.

itsnikhilkadyan said:
There are following bugs on honor 7x:
1. Hotspot not working.
2. Usb connecetion to pc is charge only can use to transfer files.
Also the camera has too much noice.
there maybe more but these are all that I finded.
Click to expand...
Click to collapse
USB does work you have to enable under developer settings also and the pie nav bar works enable it in gesture

camera
dcraffam said:
I followed this guy's post so I'm just going to link his directions over here credits to @crayonicle
https://forum.xda-developers.com/honor-view-10/development/rom-aosp-pie-t3829466/page3
Got this to boot on my phone, finally.
I have an Honor 7x.
I removed the assert line and uploaded the file here https://drive.google.com/drive/folde...fY?usp=sharing
1. Go back to stock using hurupdater, this is a must. I tried coming from a different ROM, and it bootlooped and nothing would stop the bootloop.
2. Factory reset in stock recovery
3. Flash back twrp in fastboot, I used this one https://drive.google.com/open?id=18u...QgwleMIOjsZd7S
4. Flash the rom and bitgapps in one go
5. Factory reset in twrp, format data, and also factory reset in stock recovery
6. It will bootloop you to erecovery, just tap "Reboot" again, and it will boot to the ROM.
7. Enjoy Android P on your phone
This is running pretty damn good for it not to be for our device no bugs as of yet
Click to expand...
Click to collapse
Is the Camera functional?

zagingi said:
Is the Camera functional?
Click to expand...
Click to collapse
it is very functional, if you mean by the stock aosp cam.

i saw a video on youtube like 5 days ago ... i hesitated posting because i couldn't verify if it's really the 7x or not but it appeared that he was running pie
Great news

How does honor view 10 roms runs in Honor 7x?

dcraffam said:
I followed this guy's post so I'm just going to link his directions over here credits to @crayonicle
https://forum.xda-developers.com/honor-view-10/development/rom-aosp-pie-t3829466/page3
Got this to boot on my phone, finally.
I have an Honor 7x.
I removed the assert line and uploaded the file here https://drive.google.com/drive/folde...fY?usp=sharing
1. Go back to stock using hurupdater, this is a must. I tried coming from a different ROM, and it bootlooped and nothing would stop the bootloop.
2. Factory reset in stock recovery
3. Flash back twrp in fastboot, I used this one https://drive.google.com/open?id=18u...QgwleMIOjsZd7S
4. Flash the rom and bitgapps in one go
5. Factory reset in twrp, format data, and also factory reset in stock recovery
6. It will bootloop you to erecovery, just tap "Reboot" again, and it will boot to the ROM.
7. Enjoy Android P on your phone
This is running pretty damn good for it not to be for our device no bugs as of yet
Click to expand...
Click to collapse
VOLTE working ?

karti16 said:
How does honor view 10 roms runs in Honor 7x?
Click to expand...
Click to collapse
I don't know but I'm using like a secondary and honestly it's the best rom I used I think so far I really like the havoc os because I play mc5 and to me that one ran the game the best but this honor view 9 pie is running exceptionally well and it plays the game great I can't wait for pie to be optimized for the honor because it's gonna be perfect

I need to unlock bootloader. Got any working gcam? Honor 7x camera is showing unrealistic colour.

is VoLTE working ?

can not install always saying error 7 and that the Rom is not for my device...

Hi new to this phone and flashed rros from the openkirin site using just fastboot so have a couple questions about installing this ROM. First question is the link to the recovery isn't even for a honor 7x but guessing that doesn't matter anymore on a treble enabled phone and do you flash it to the ramdisk? Then after you do get it flashed do you install the ROM as a zip or do you extract it to install as a image? Thanks for the help guys kinda crazy thinking you will have twrp and stock recovery on a phone

dcraffam said:
I followed this guy's post so I'm just going to link his directions over here credits to @crayonicle
https://forum.xda-developers.com/honor-view-10/development/rom-aosp-pie-t3829466/page3
Got this to boot on my phone, finally.
I have an Honor 7x.
I removed the assert line and uploaded the file here https://drive.google.com/drive/folde...fY?usp=sharing
1. Go back to stock using hurupdater, this is a must. I tried coming from a different ROM, and it bootlooped and nothing would stop the bootloop.
2. Factory reset in stock recovery
3. Flash back twrp in fastboot, I used this one https://drive.google.com/open?id=18u...QgwleMIOjsZd7S
4. Flash the rom and bitgapps in one go
5. Factory reset in twrp, format data, and also factory reset in stock recovery
6. It will bootloop you to erecovery, just tap "Reboot" again, and it will boot to the ROM.
7. Enjoy Android P on your phone
This is running pretty damn good for it not to be for our device no bugs as of yet
Click to expand...
Click to collapse
the 2 drive links you posted are broke, they are being broken with "..." "drive.google.com/drive/folde...fY?usp=sharing" "drive.google.com/open?id=18u...QgwleMIOjsZd7S"

please use the quote function...
{
"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"
}

Wrong place to ask this question
MOD EDIT

darkmage1991 said:
the 2 drive links you posted are broke, they are being broken with "..." "drive.google.com/drive/folde...fY?usp=sharing" "drive.google.com/open?id=18u...QgwleMIOjsZd7S"
Click to expand...
Click to collapse
I'll reupload now it's this guy @crayonicle being wierd ASF like how many more times you want me to @crayonicle you damn @crayonicle

BigDiqSeitz said:
can not install always saying error 7 and that the Rom is not for my device...
Click to expand...
Click to collapse
I reuploaded the one with that check remove should flash through now

dcraffam said:
I'll reupload now it's this guy @crayonicle being wierd ASF like how many more times you want me to @crayonicle you damn @crayonicle
Click to expand...
Click to collapse
hahahaha you just want more number counts in your thanks meter so you can be "cool"
please delete your spams, it's getting annoying, i am the one who originally posted it, what right do you have to come and take it for your own?

crayonicle said:
hahahaha you just want more number counts in your thanks meter so you can be "cool"
please delete your spams, it's getting annoying, i am the one who originally posted it, what right do you have to come and take it for your own?
Click to expand...
Click to collapse
Really. So like ........
.