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.
Related
It all started with the plan to root the device Samsung Galaxy Note 3
I had rooted the device using Kingo Android root. This had gone successfully. Then I tried to install some apps which needs root access. I tried an app called EFS, I though I would back up EFS and NV_ *, When I clicked on backup NV_* (cant remember the whole name), thats when the problem started. It had been 2 days since I had been trying different things to recover the device.
I went into recovery mode and tried
Clear cache
Then Back up my data and did factory reset
Between boot loops I had the opportunity to uninstalled the EFS app
Then installed twrp and tried this blog http://forum.xda-developers.com/showthread.php?t=2471421
eventually, I thought of letting go of my data, so did the format of data
used ODIN to and flashed this ROM from this blog http://forum.xda-developers.com/showthread.php?t=2540822
Despite all these steps I cannot get it working.
Current phone behaviour
The phone keeps booting again, once the UI of the phone starts, I get a window of 1 min before the phone restarts again. I get a message saying "Process system isn't responding"
I am willing to try anything to get the device functional, if it means to build it from scratch. This is my first time venturing into this side of the world, I would be thankful if you can guide me with the steps to perform a build from scratch, or direct me to a blog where I can do this?
eagle909 said:
It all started with the plan to root the device Samsung Galaxy Note 3
I had rooted the device using Kingo Android root. This had gone successfully. Then I tried to install some apps which needs root access. I tried an app called EFS, I though I would back up EFS and NV_ *, When I clicked on backup NV_* (cant remember the whole name), thats when the problem started. It had been 2 days since I had been trying different things to recover the device.
I went into recovery mode and tried
Clear cache
Then Back up my data and did factory reset
Between boot loops I had the opportunity to uninstalled the EFS app
Then installed twrp and tried this blog http://forum.xda-developers.com/showthread.php?t=2471421
eventually, I thought of letting go of my data, so did the format of data
used ODIN to and flashed this ROM from this blog http://forum.xda-developers.com/showthread.php?t=2540822
Despite all these steps I cannot get it working.
Current phone behaviour
The phone keeps booting again, once the UI of the phone starts, I get a window of 1 min before the phone restarts again. I get a message saying "Process system isn't responding"
I am willing to try anything to get the device functional, if it means to build it from scratch. This is my first time venturing into this side of the world, I would be thankful if you can guide me with the steps to perform a build from scratch, or direct me to a blog where I can do this?
Click to expand...
Click to collapse
Flash THIS it'll fix your EFS issues and your bootloop -
Grab CWM/TWRP and flash via Odin
Run that zip from custom recovery
Job done
Stay away from EFS back up apps, they're notoriously unreliable and can brick your device
radicalisto said:
Flash THIS it'll fix your EFS issues and your bootloop -
Grab CWM/TWRP and flash via Odin
Run that zip from custom recovery
Job done
Stay away from EFS back up apps, they're notoriously unreliable and can brick your device
Click to expand...
Click to collapse
Sounds like a dumb question but How to I upload this zip file to my phone. Note3 does not come with external SD slot and I am not able to connect the phone through PC either by Kies or ADT, none of them are recognising?
Can I upload this zip file through ODIN? it only accepts .tar or .md5 files?
Any tips?
eagle909 said:
Sounds like a dumb question but How to I upload this zip file to my phone. Note3 does not come with external SD slot and I am not able to connect the phone through PC either by Kies or ADT, none of them are recognising?
Can I upload this zip file through ODIN? it only accepts .tar or .md5 files?
Any tips?
Click to expand...
Click to collapse
Ahh, you will need to find an ext SD card, then you'll have to transfer it across via your PC then insert into phone, boot into Recovery and flash it.
Not flashable via Odin atm I'm afraid
eagle909 said:
Sounds like a dumb question but How to I upload this zip file to my phone. Note3 does not come with external SD slot and I am not able to connect the phone through PC either by Kies or ADT, none of them are recognising?
Can I upload this zip file through ODIN? it only accepts .tar or .md5 files?
Any tips?
Click to expand...
Click to collapse
Yes it does comes with an ext SD card slot... Beside ur sim card slot. Put that file into it then put into ur phone. Boot into custom recovery and flash it.
Sent from my proudly temaseked +Yankied note 3.
Yeah SD Card slot is above the sim card slot, -- I read it wrong, thought you said -- "it doesn't come with an EXT SD Card"
radicalisto said:
Flash THIS it'll fix your EFS issues and your bootloop -
Grab CWM/TWRP and flash via Odin
Run that zip from custom recovery
Job done
Stay away from EFS back up apps, they're notoriously unreliable and can brick your device
Click to expand...
Click to collapse
radicalisto said:
Yeah SD Card slot is above the sim card slot, -- I read it wrong, thought you said -- "it doesn't come with an EXT SD Card"
Click to expand...
Click to collapse
I never knew there was a slot of SD card, else I would have backed up my data thanks!
But this solution didnt work for me. After the install of this script through twrp the phone behavior is unchanged.
Try flashing the stock rom for your phone. Then you can go back and root again....
99% of the time this will fix things...
eagle909 said:
I never knew there was a slot of SD card, else I would have backed up my data thanks!
But this solution didnt work for me. After the install of this script through twrp the phone behavior is unchanged.
Click to expand...
Click to collapse
The screenshot of the install. I suspect if there is something wrong with the install?
{
"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"
}
eagle909 said:
The screenshot of the install. I suspect if there is something wrong with the install?
sorry too big of the picture
Click to expand...
Click to collapse
ultramag69 said:
Try flashing the stock rom for your phone. Then you can go back and root again....
99% of the time this will fix things...
Click to expand...
Click to collapse
downloading this Rooted Stock ROMs for Note 3 SM-N9005
http://galaxynote3root.com/rooted-stock-roms/
That screenshot looks OK to me. The Mount error is standard in TWRP. Reboot your device and see.. or as posted re flash stock as it pretty much fixes everything
Sent from my SM-N9005 using XDA Premium 4 mobile app
eagle909 said:
downloading this Rooted Stock ROMs for Note 3 SM-N9005
http://galaxynote3root.com/rooted-stock-roms/
Click to expand...
Click to collapse
I have just flashed this ROM and reran the fix, but with out any luck?
The phone keeps rebooting
eagle909 said:
I have just flashed this ROM and reran the fix, but with out any luck?
The phone keeps rebooting
Click to expand...
Click to collapse
You haven't flashed a stock rom... That is rooted and so is no longer a stock rom. Go to Sammobile.com to get a pure stock rom...
Just a note for you, whether it says stock is solely reliant on it being NOT tampered with. Rooting a stock rom no longer makes it stock, it is just a description that means no tweaks were applied or bloatware removed...
Remember that the bootloader must match the stock rom. If you are trying to flash a lower version rom onto an MJ3 or higher bootloader you will get bootloops.
The same applies if you have updated to Kitkat rom.
If you haven't updated to 4.4.2, then you should check this[first post]
http://forum.xda-developers.com/showthread.php?t=2540822
But this will trip your Knox counter
Sent from my SM-N9005 using Tapatalk
I checkout this post and did exactly as described. but the phone rebooting doesnot stop. Also when the phone is turned on I am not able to open Phone option and under settings I am not able to launch status option under about device? Could my EFS is lost/corrupted?
Dahdoul said:
If you haven't updated to 4.4.2, then you should check this[first post]
http://forum.xda-developers.com/showthread.php?t=2540822
But this will trip your Knox counter
Sent from my SM-N9005 using Tapatalk
Click to expand...
Click to collapse
eagle909 said:
I checkout this post and did exactly as described. but the phone rebooting doesnot stop. Also when the phone is turned on I am not able to open Phone option and under settings I am not able to launch status option under about device? Could my EFS is lost/corrupted?
Click to expand...
Click to collapse
Use This It'll fix it. - You have to install a custom recovery via Odin then flash that fix and you'll be alright, you EFS is warped is all.
I had already tried that fix, but with no luck. I flashed that fix with a lot of combinations like with fresh install of stock rom, with rooted rom etc. No luck
radicalisto said:
Use This It'll fix it. - You have to install a custom recovery via Odin then flash that fix and you'll be alright, you EFS is warped is all.
Click to expand...
Click to collapse
eagle909 said:
I had already tried that fix, but with no luck. I flashed that fix with a lot of combinations like with fresh install of stock rom, with rooted rom etc. No luck
Click to expand...
Click to collapse
Is the phone bootlooping constantly ? and crashing after around 1minute?
rtanceF seize
radicalisto said:
Is the phone bootlooping constantly ? and crashing after around 1minute?
Click to expand...
Click to collapse
When you mean "install a custom recovery via Odin", you meant to install something like TWRP to install the zip using recovery mode?
The phone keeps booting again and again, once the UI of the phone starts, I get a window of 1 min before the phone restarts again. I get a message saying "Process system isn't responding" before the phone restarts.
I'll cut right to the chase, I've soft-bricked my Note 3 (sm-9005). I bought it off Newegg and received it Friday. I proceeded to use Chainfire's root, and then installed TWirp which worked without incident. My problem started after I installed X-Note. My system was unstable, had no sound and would make calls but not receive them. (I'm in USA, on AT&T network).
I know I should have made a backup but I didn't. (Im a Samsung fan, have owned the Note 1, Galaxy 3, and now the International Note 3). I went to sammobile and the started to realize I was in trouble. (I don't know the original CSC) It was not printed on the box, and on the back of the phone my info is the same as The guys in this thread: http://forum.xda-developers.com/showthread.php?t=2628435.
Long story short. I've tried multiple stock recoveries. Some are stuck in a bootloop (at the Samsung screen). Some will appear to work but have no sound, camera doesn't work, etc. I can still get iinto Download mode, can even reflash Twirp after screwing up. When I try other custom roms they either bootloop or half way work (no sound, crashes, etc.)
I know NewEgg won't take this phone back, and honestly since i'm still able to access it via odin I dont want to send it in IF someone here can help me get it back, and I'll pay someone $100.00 via PayPal if they can.
I have TeamViewer / Skype, or will get whatever you need to help me Via / video call, over the phone, etc.
It is 10:00am (CST) right now. I will be back here at 12:30pm (2.5 Hours) I hope someone is willing to help me with this issue. 2 days working with this and i'm at my end.
If anyone is willing to help please let me know I'll keep this page open and will be refreshing it often, in the mean time I'll keep searching forums.
Was it JB or KK when got it?
Maybe you're trying to run a KK rom when you have a JB bootloader still?
Is the knox tripped?
MystaMagoo said:
Was it JB or KK when got it?
Maybe you're trying to run a KK rom when you have a JB bootloader still?
Is the knox tripped?
Click to expand...
Click to collapse
Is on KK 4.2.2 Bootloader from Factory. I'm sure Knox was / is tripped because I had used ChainFire's root Friday night after getting the phone. Things went bad when I tried to flash X-Note yesterday.
I have reinstalled a Polish Rom (N9005XXUEND3_N9005XEOEND2_N9005XXUENC2_HOME), and it's booting up, but no sound at all, camera, etc. Also just checked, No modem, (IMEI or BaseBand) even though I flashed the above file thru Odin 3.7 [But WiFi, GPS works]
Edit #2: Downloading UK recovery firmware now.
Not that this will help, I do NOT remember anything about the country code, but /I can tell you the sticker on the back has some spanish on it, and when I started the welcome screen Friday I had to change the language from Spanish to English.
Heres a picture of the Sticker, sorry for the bad quality.
{
"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"
}
What do you mean by no modem / IMEI. If it doesn't show any IMEI number with Sim card inserted than it's probably due to corrupt EFS. Do you have a backup of EFS?
Envoyé de mon GT-N5120 en utilisant Tapatalk
LuMe96 said:
What do you mean by no modem / IMEI. If it doesn't show any IMEI number with Sim card inserted than it's probably due to corrupt EFS. Do you have a backup of EFS?
Envoyé de mon GT-N5120 en utilisant Tapatalk
Click to expand...
Click to collapse
No I didn't make an EFS backup When I had my Note 1 there was never any mention about EFS on any rom I flashed and they all worked without issue, but i'm having a heck of a time.
Right it's showing Unknown BaseBand / or Imei under system / about.
With the UK rom it seems stable / not crashing, wifi works and I can surf, but No Cellular service, or sound, or camera.
hello there, as far as i know , csc is just customer service code or something like that, just bloatware and other stuff loaded for a specified region, an example, my device is for UAE, csc is xsi or something like that, but whats installed on the device is the polish firmware and the device is functioning properly
from what you stated that you had no idea which firmware version was installed prior to flashing the custom rom,
the following steps (may) be helpful for you
search the forums for these separate files and flash them separately, start with the modem/baseband as this is more important than sound and camera at the current time being
modem:
http://www.4shared.com/file/4YUQQVkYce/REPACK_DXUENE3_MODEM.html (credit goes to @SERGiooooo and those who extracted to files)
to flash modem go into download mode on the device and in odin select CP and unselect autoreboot, then reboot manually again to download mode and repeat and select autoreboot this time (flash it twice)
then you need to search for a compatible or recommended bootloader for your rom and flash it
and finally do a standard wipe and reinstall a rom of your choice which is compatible with your device
please keep in mind that you should only flash roms which are made for your variant( n9005 rom for n9005 and n900 for n900 and so on)
also keep in mind that some roms from sammobile.com wont be compatible (eg: hong kong nf1 is not compatible with other n9005's because of the diffrent pit )
make sure your device is 32gb n9005 and re download the rom again
finally, may i suggest to try this rom (stock based de-odexed based on ne4 and all the extra files like bootloaders and modems are included separately) and hope it solves the sound and other issues as well
http://forum.xda-developers.com/showthread.php?t=2649176
apologies for the details, this is just a suggestion coz I had the same issue with the IMEI and baseband problem
and always always do backups
I flashed singapore (NE4) stock rom (supposed to be international) from sammobile. After that, when I tried to go back to older modem my imei would be unknown, sound was messed up, and dialer would take a long time to start, but after flashing singapore modem back my imei would be there again.
It looks like that samsung is trying to block flashing of older versions of anything... Try that singapore rom (which is almost the latest available, and should flash latest everything bl, pda, csc, phone) and see if it works.
ciribic said:
I flashed singapore (NE4) stock rom (supposed to be international) from sammobile. After that, when I tried to go back to older modem my imei would be unknown, sound was messed up, and dialer would take a long time to start, but after flashing singapore modem back my imei would be there again.
It looks like that samsung is trying to block flashing of older versions of anything... Try that singapore rom (which is almost the latest available, and should flash latest everything bl, pda, csc, phone) and see if it works.
Click to expand...
Click to collapse
Downloading Now. IF you are my savior give me your PayPal Address and you'll be $100 richer. Quck question, first time I flash using Odin, just put .tar in PDA then flash, right? If I need to just flash the modem back, how do I do that?
jb0nd38372 said:
Downloading Now. IF you are my savior give me your PayPal Address and you'll be $100 richer. Quck question, first time I flash using Odin, just put .tar in PDA then flash, right? If I need to just flash the modem back, how do I do that?
Click to expand...
Click to collapse
Yes ap/pda for the whole rom, cp for modem, bl for bootloader
Good luck
Bnjalal said:
Yes ap/pda for the whole rom, cp for modem, bl for bootloader
Good luck
Click to expand...
Click to collapse
Sent you A PM, you fixed it, Just need your PayPal address. Do you have any ideas why I can't flash other roms? X-Note got me in this mess, and from what I understand it's supposedly a great rom.
You fixed it!!!!
Bnjalal said:
Yes ap/pda for the whole rom, cp for modem, bl for bootloader
Good luck
Click to expand...
Click to collapse
PM Sent, your $100 is waiting.
Easy with the money and carefully with flashing.
Yes, put it in pda, make sure that only auto reboot and f.reset time are checked, nothing else. Modem is included in the rom. If you are flashing only modem you put it in phone field. The thing is I'm not sure You'll be able to go back to old modem after you flash this one (NE3), when I tried flashing my old modem it messed up things, and flashing whole older ROM would skip flashing modem because it would detect newer already there.
Put your phone in download mode (make sure that battery is at least 60%)
Start Odin and open tar file in pda, wait a minute or two till md5 is checked when it says it's checked an ok connect your phone. I'll assume you installed samsung drivers previously. Wait a few moments here because windows might install drivers (if you have never connected your phone while in dl mode). Now there shoud be device added in ID:COM field in Odin and it should be blue/green. now you can press start.
jb0nd38372 said:
PM Sent, your $100 is waiting.
Click to expand...
Click to collapse
Sir i believe that @ciribic is the one who suggested to download the ne4 singapore stock international rom and i replied instead of him on which selection to choose in odin please verify that as i dont want to take credit on other persons work
And please accept my apologies if I caused any confusion as i was only trying to help you through the process in any means possible
Sorry
Bnjalal said:
Sir i believe that @ciribic is the one who suggested to download the ne4 singapore stock international rom and i replied instead of him on which selection to choose in odin please verify that as i dont want to take credit on other persons work
And please accept my apologies if I caused any confusion as i was only trying to help you through the process in any means possible
Click to expand...
Click to collapse
ciribic said:
Easy with the money and carefully with flashing.
Click to expand...
Click to collapse
You both helped me. I am thankful to have it back up and working. I don't understand why on my Note 1 (AT&T locked), I was able to flash every rom on that forum with no issues; Every Rom on this forum gives me BAD issues, could I have got a bad phone or something? (It was new in box, ordered from Newegg.com), but could it be defective somehow?
@ciribic I sent you a PM,
OP allow me to clear any misunderstanding with fellow members and please give all credit to him as I did nothing
now back to your question , you probably flashed roms based on recent stock TW roms and those require you to be on recent bootloaders and modems, reason for this difference is that rom builders take into consideration that the user does not want to trip his KNOX flag and may use other methods to flash the rom without using custom recovories like TWRP/CWM (ex mobile odin, safestrap) so most custom roms come without modems and bootloaders and if you unzip the x-note rom you will see that there are no bootloaders and modems included if im not mistaken
Now to get rid of any OCD related to the your device whether its faulty or not, try flashing back x-note <after> you make a complete backup in TWRP(my personal favorite) and im 95% sure that you will not have these issues anymore
ciribic said:
I flashed singapore (NE4) stock rom (supposed to be international) from sammobile. After that, when I tried to go back to older modem my imei would be unknown, sound was messed up, and dialer would take a long time to start, but after flashing singapore modem back my imei would be there again.
It looks like that samsung is trying to block flashing of older versions of anything... Try that singapore rom (which is almost the latest available, and should flash latest everything bl, pda, csc, phone) and see if it works.
Click to expand...
Click to collapse
ciribic said:
Easy with the money and carefully with flashing.
Yes, put it in pda, make sure that only auto reboot and f.reset time are checked, nothing else. Modem is included in the rom. If you are flashing only modem you put it in phone field. The thing is I'm not sure You'll be able to go back to old modem after you flash this one (NE3), when I tried flashing my old modem it messed up things, and flashing whole older ROM would skip flashing modem because it would detect newer already there.
Put your phone in download mode (make sure that battery is at least 60%)
Start Odin and open tar file in pda, wait a minute or two till md5 is checked when it says it's checked an ok connect your phone. I'll assume you installed samsung drivers previously. Wait a few moments here because windows might install drivers (if you have never connected your phone while in dl mode). Now there shoud be device added in ID:COM field in Odin and it should be blue/green. now you can press start.
Click to expand...
Click to collapse
Bnjalal said:
@ciribic I sent you a PM,
OP allow me to clear any misunderstanding with fellow members and please give all credit to him as I did nothing
now back to your question , you probably flashed roms based on recent stock TW roms and those require you to be on recent bootloaders and modems, reason for this difference is that rom builders take into consideration that the user does not want to trip his KNOX flag and may use other methods to flash the rom without using custom recovories like TWRP/CWM (ex mobile odin, safestrap) so most custom roms come without modems and bootloaders and if you unzip the x-note rom you will see that there are no bootloaders and modems included if im not mistaken
Now to get rid of any OCD related to the your device whether its faulty or not, try flashing back x-note <after> you make a complete backup in TWRP(my personal favorite) and im 95% sure that you will not have these issues anymore
Click to expand...
Click to collapse
Making that Twirp Backup as I type this, got an SD card just for that purpose now. TBH, I could care less about warranty because it won't cover Water damage, drops, misuse and that's where 99% of my past problems have happened. Knox is annoying to no end, I just got through running System Uninstaller to pull all the knox libraries / apk's and modules out.
I think i'll just stick a better optimized / open kernel on it and launcher, and call it quits. I'm 42, after these past 2 days, I feel 82.
good decision and hope u enjoy your new phone :good:
Okay, so I've had this issue for a few months now where no matter what I tried, I could not update my Baseband. I tried everything I could think of - flashed the full stock Rom, used mobile ODIN, flashed twice, etc. but no matter what, the baseband would stick to the old one. I tried googling and looking around but the same tricks as above were posted again and again to no avail.
I eventually found the answer, it was a single post buried in a thread on here. As I keep seeing posts from other users with the same issue, I figured I'd write a quick guide so that hopefully those searching for the problem will find it.
So to reiterate - you've just updated to a new firmware (custom or otherwise) but your radio (aka baseband) has not changed. You then try to flash the radio directly but it still won't change. What gives?
Well to fix it, you're going to need the following:
Odin 3.07
Triangle Away (Thanks to Chainfire, as always)
A Method of rooting your device (I'm leaving this up to you as it's a warranty voiding experience and I presume you know how to do that by this point).
An official Samsung firmware containing the radio you want to update to
If you're currently on an AOSP based ROM, then I have bad news - you'll need to flash back to touchwiz to do this. Once you're done, you can flash back though.
Remember to make a backup of all your data, as you will be doing a lot of flashing here.
Note: You may be able to fix your stuck radio problem without flashing back to a completely stock firmware and cutting corners elsewhere, however I wanted this guide to be bulletproof, deviating slightly may produce different results. If all else fails, follow each step below exactly!
Remember: This guide is specifically for those of you who have tried other methods and are still stuck on an old baseband. If you're just looking how to flash your radio, there are easier and less involved methods that don't require any wiping - I strongly advise you to try those first.
Okay, by this point I'm going to assume you've done all your backups and are ready to start flashing.
Step 1: Reboot your phone into DOWNLOAD mode (aka Odin). To do this, hold down POWER, VOL-DOWN and HOME at the same time until you see the following screens:
{
"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"
}
Remember to let go of the above buttons and press "volume up" to continue.
Step 2: Open up Odin 3.07, click on the "PDA" button and select the stock firmware file you have downloaded (file should have a ".tar.md5" extension, if you downloaded a .zip file you'll need to extract it but DO NOT EXTRACT MORE THAN THIS, you want a single .tar.md5 file).
Step 3: With your phone connected to your PC running ODIN, click "start". This will take a few mins, so be patient.
Step 4: Root. Now your phone should be rebooting into some pretty awful stock Samsung firmware. Boo. However this is a necessary evil. Here you need to root your phone. CF-Auto-Root is my preferred method but this trips Knox so do what you feel is best.
Step 5: Install and run Triangle Away. Triangle Away requires a Stock samsung kernel, which is why you've just flashed a full Samsung firmware. Triangle away requires root, which is why you've just performed Step 4.
Step 6: Install the Stock Firmware. Again.
That's right, repeat steps 2 and 3 once more to flash that stock Samsung firmware all over again. Except this time, your system is reporting that it's "official" and TriangleAway has cleared some flags that were preventing the updated radio from installing. When your phone reboots, your radio should have updated.
You're done! From here, you can do whatever you like - flash another custom ROM (you're still rooted at this point), wipe and restore a backup you made earlier, switch to AOSP or whatever. Personally, I would go buy Chainfire a beer as TriangleAway is what makes this all possible.
Nice....it helped me :good:
Thanks :highfive:
neoKushan said:
Okay, so I've had this issue for a few months now where no matter what I tried, I could not update my Baseband. I tried everything I could think of - flashed the full stock Rom, used mobile ODIN, flashed twice, etc. but no matter what, the baseband would stick to the old one. I tried googling and looking around but the same tricks as above were posted again and again to no avail.
I eventually found the answer, it was a single post buried in a thread on here. As I keep seeing posts from other users with the same issue, I figured I'd write a quick guide so that hopefully those searching for the problem will find it.
So to reiterate - you've just updated to a new firmware (custom or otherwise) but your radio (aka baseband) has not changed. You then try to flash the radio directly but it still won't change. What gives?
Well to fix it, you're going to need the following:
Odin 3.07
Triangle Away (Thanks to Chainfire, as always)
A Method of rooting your device (I'm leaving this up to you as it's a warranty voiding experience and I presume you know how to do that by this point).
An official Samsung firmware containing the radio you want to update to
If you're currently on an AOSP based ROM, then I have bad news - you'll need to flash back to touchwiz to do this. Once you're done, you can flash back though.
Remember to make a backup of all your data, as you will be doing a lot of flashing here.
Note: You may be able to fix your stuck radio problem without flashing back to a completely stock firmware and cutting corners elsewhere, however I wanted this guide to be bulletproof, deviating slightly may produce different results. If all else fails, follow each step below exactly!
Okay, by this point I'm going to assume you've done all your backups and are ready to start flashing.
Step 1: Reboot your phone into DOWNLOAD mode (aka Odin). To do this, hold down POWER, VOL-DOWN and HOME at the same time until you see the following screens:
Remember to let go of the above buttons and press "volume up" to continue.
Step 2: Open up Odin 3.07, click on the "PDA" button and select the stock firmware file you have downloaded (file should have a ".tar.md5" extension, if you downloaded a .zip file you'll need to extract it but DO NOT EXTRACT MORE THAN THIS, you want a single .tar.md5 file).
Step 3: With your phone connected to your PC running ODIN, click "start". This will take a few mins, so be patient.
Step 4: Root. Now your phone should be rebooting into some pretty awful stock Samsung firmware. Boo. However this is a necessary evil. Here you need to root your phone. CF-Auto-Root is my preferred method but this trips Knox so do what you feel is best.
Step 5: Install and run Triangle Away. Triangle Away requires a Stock samsung kernel, which is why you've just flashed a full Samsung firmware. Triangle away requires root, which is why you've just performed Step 4.
Step 6: Install the Stock Firmware. Again.
That's right, repeat steps 2 and 3 once more to flash that stock Samsung firmware all over again. Except this time, your system is reporting that it's "official" and TriangleAway has cleared some flags that were preventing the updated radio from installing. When your phone reboots, your radio should have updated.
You're done! From here, you can do whatever you like - flash another custom ROM (you're still rooted at this point), wipe and restore a backup you made earlier, switch to AOSP or whatever. Personally, I would go buy Chainfire a beer as TriangleAway is what makes this all possible.
Click to expand...
Click to collapse
No need this，too complicated。
Only turn off the phone, then remove the battery ,
install it
and get into download model ,
Flash the radio.
that you can update the baseband
nforce4 said:
No need this，too complicated。
Only turn off the phone, then remove the battery ,
install it
and get into download model ,
Flash the radio.
that you can update the baseband
Click to expand...
Click to collapse
Thanks, but unfortunately that didn't work for me.
neoKushan said:
Thanks, but unfortunately that didn't work for me.
Click to expand...
Click to collapse
Turn off your phone manually. Leave it for 10 sec, dont need to remove battery, Put the modem on Phone, NOT PDA connect your phone and flash it. It is simple.
IzArsha said:
Turn off your phone manually. Leave it for 10 sec, dont need to remove battery, Put the modem on Phone, NOT PDA connect your phone and flash it. It is simple.
Click to expand...
Click to collapse
Believe me when I say that I tried that, I tried just about everything before it would finally stick. Removing battery, leaving it off for 10s+ (I did this numerous times as TriangleAway demands it due to the risk if bricking your phone and one time left it off/unplugged for a good 20mins to no avail). There was some kind of write protection in place, Mobile ODIN (yeah tried that as well) mentioned it when trying to flash the Radio - hence why TriangleAway is needed.
Before it got "Stuck", I had manually updated my Modem a few times without issue. I've had the Note 3 since launch and voided Knox within about 2 days of getting it - believe me, I've been there and done that
Nothing worked for me also until I tried this method...
Sent from my SM-N9005 using XDA Premium 4 mobile app
Here's what I don't like, and what I "Do" Like...
Like....
1) A post in the proper forum that seems to help a few people fix their issue when other methods didn't seem to work.
Dislike...
1) Somebody coming in touting their own method (which may or may not work for a particular user). This, believe it or not, only adds to confusion when a person looks for an answer. Now there are different methods in the same thread topic.
2) 2 pages of back and forth arguing as a result of the above ^^^
So, I'll delete all posts concerning this debate on procedures.
Folks, don't go poaching other users threads please. If they provide a solution that helps a few users, then that is GREAT!!! Not all normal solutions work for all users. Stick around long and you will discover this on your own one day.
Cleaned thread, please don't make me come back and do it again.
MD
Thanks Moscow. I apologise for what happened, I didn't mean to cause a fuss.
To show there's no hard feelings, I've updated the OP with a warning that this is specifically for those who are still stuck after trying out other methods. Hopefully that's enough to keep everyone happy.
neoKushan said:
Thanks Moscow. I apologise for what happened, I didn't mean to cause a fuss.
To show there's no hard feelings, I've updated the OP with a warning that this is specifically for those who are still stuck after trying out other methods. Hopefully that's enough to keep everyone happy.
Click to expand...
Click to collapse
Much better. I didn't mean to start an argument... But it happened somehow.
Good detailed guide however. See you around XDA.
I'm having Baseband: Unknown issue, and flashing different modems are not changing it.
Can this method help ?
thanks
MuhammadZeeshan7 said:
I'm having Baseband: Unknown issue, and flashing different modems are not changing it.
Can this method help ?
thanks
Click to expand...
Click to collapse
Hmm, I really don't know man. I've not seen that error before so I can't comment. Perhaps this can help?
neoKushan said:
Hmm, I really don't know man. I've not seen that error before so I can't comment. Perhaps this can help?
Click to expand...
Click to collapse
I've done almost every method, but not yours. BTW I don't have any other triangle icon except the yellow triangle at the start of Download mode.
MuhammadZeeshan7 said:
I'm having Baseband: Unknown issue, and flashing different modems are not changing it.
Can this method help ?
thanks
Click to expand...
Click to collapse
Unpack the tar file, and flash just the modem.bin into phone (not pda) in Odin.
not working on SM-N900w8
Didn't work on my note 3 sm-n900w8, modem still previous version :crying:
any other suggestion please?
jsecruzvalencia said:
Didn't work on my note 3 sm-n900w8, modem still previous version :crying:
any other suggestion please?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=53632129&postcount=1
In the first box.
Hi,
So I unlocked the bootloader, installed the official twrp 3.2.30 available on this thread. These are the things I did
1. Wipe>format data>Typed "Yes"
2. Swipe to factory reset
3. Flashed a GSI ROM (PE ROM) It didn't boot
4. Flashed "disable-encryption -RMX1801.zip" and booted again but same result
5. Flashed another GSI rom (AOSP EXTENDED) It showed up the logo but was loading forever
6. Tried another GSI rom but it doesn't even show logo basically same Realme bootloop
*** I did take a twrp backup BACKUP> SYSTEM, VENDOR, DATA,BOOT, RECOVERY, EFS" (Just in case) I don't remember whether I took this backup before "formatting data or after that.
Now,
1. I can restore TWRP back up but it doesn't boot same problem.
2. I tried installing 3 different gsi 9.0 roms but no result.
3. I download the stock realme 2 pro firmware but don't really know how to flash it with some type of pc recovery.
How do I get back to stock? Or be able to boot any rom which is available right now?? There are only GSI ROMs but no regular roms otherwise I could have flashed it.
Any help wold be appreciated.
UPDATE: THIS IS IMPORTANT (SOLUTION) So after fiddling with every other possible alternative, I solved this by simply installing the twrp by anabhi and main thing is "boot+magisk+patch.img" so after installing both of these, I again try restoring the twrp backup and simply installed flashed the "boot+magisk+pagth.img" after that it booted fine. So my guess was right that I needed a file something similar to "lazy flasher" for Xiaomi devices which I was missing. I tried flashing that official twrp along with "disable_encryption_RMX1801.IMG" in the same above process but it doesn't work.
So finally I booted back into Color OS and now I'm going to try and flash a gsi image and try again.
I would like to thank all of you guys who quickly replied and tried to help which is the best part I love about XDA. YOU GUYS ARE AWESOME and you inspire me to type and spend some good time typing and helping others as well. Cheers!!
bad news is that there is no official tool to flash stock rom yet but you can go to oppo service center and get it flashed stock rom for free.
Thetpcguy said:
Hi,
So I unlocked the bootloader, installed the official twrp 3.2.30 available on this thread. These are the things I did
1. Wipe>format data>Typed "Yes"
2. Swipe to factory reset
3. Flashed a GSI ROM (PE ROM) It didn't boot
4. Flashed "disable-encryption -RMX1801.zip" and booted again but same result
5. Flashed another GSI rom (AOSP EXTENDED) It showed up the logo but was loading forever
6. Tried another GSI rom but it doesn't even show logo basically same Realme bootloop
*** I did take a twrp backup BACKUP> SYSTEM, VENDOR, DATA,BOOT, RECOVERY, EFS" (Just in case) I don't remember whether I took this backup before "formatting data or after that.
Now,
1. I can restore TWRP back up but it doesn't boot same problem.
2. I tried installing 3 different gsi 9.0 roms but no result.
3. I download the stock realme 2 pro firmware but don't really know how to flash it with some type of pc recovery.
How do I get back to stock? Or be able to boot any rom which is available right now?? There are only GSI ROMs but no regular roms otherwise I could have flashed it.
Any help wold be appreciated.
Click to expand...
Click to collapse
maybe the same problem. https://forum.xda-developers.com/realme-2-pro/help/please-help-restore-t3893602 I got a good answer, even though I had never tried it because I went to the service center before getting an answer
Zaibuluk said:
maybe the same problem. https://forum.xda-developers.com/realme-2-pro/help/please-help-restore-t3893602 I got a good answer, even though I had never tried it because I went to the service center before getting an answer
Click to expand...
Click to collapse
Hi, Thanks a lot for your reply!!
Are you saying that the service centre guys can fix this? I mean flash stock rom? Because I unlocked bootloader and flashed twrp recovery. I formatted data and all. Do you think they have the tool to put stock rom again??
prince1995 said:
bad news is that there is no official tool to flash stock rom yet but you can go to oppo service center and get it flashed stock rom for free.
Click to expand...
Click to collapse
Hi, Thanks for the fast response. Do you really think they can put back stock rom? If they have such a tool to restore stock rom then why wouldn't they already release it to general public? I'm not really hopeful that they have such tool to actually put back the stock rom. I know they have lot of proprietary stuff but can you confirm this?
Zaibuluk said:
maybe the same problem. https://forum.xda-developers.com/realme-2-pro/help/please-help-restore-t3893602 I got a good answer, even though I had never tried it because I went to the service center before getting an answer
Click to expand...
Click to collapse
I forgot to ask, How many days or how much time did they take to flash stock rom? And Btw which region or place you are from if don't mind me asking?
Thetpcguy said:
I forgot to ask, How many days or how much time did they take to flash stock rom? And Btw which region or place you are from if don't mind me asking?
Click to expand...
Click to collapse
Your phone can be flashed with the Stock ROM at the service center. It would take a 1 day at the most, but, most definitely less than that if they have the OS at hand with them.
My suggestion would be that you could wait till the full Kernel Source is released and official ROMs are released for the RM2Pro and flash those ROMs. It's the safer alternative.
Thetpcguy said:
Hi, Thanks a lot for your reply!!
Are you saying that the service centre guys can fix this? I mean flash stock rom? Because I unlocked bootloader and flashed twrp recovery. I formatted data and all. Do you think they have the tool to put stock rom again??
Click to expand...
Click to collapse
Thetpcguy said:
Hi, Thanks for the fast response. Do you really think they can put back stock rom? If they have such a tool to restore stock rom then why wouldn't they already release it to general public? I'm not really hopeful that they have such tool to actually put back the stock rom. I know they have lot of proprietary stuff but can you confirm this?
Click to expand...
Click to collapse
Thetpcguy said:
I forgot to ask, How many days or how much time did they take to flash stock rom? And Btw which region or place you are from if don't mind me asking?
Click to expand...
Click to collapse
Your questions are quite meaningful there are 2 types of bricking hard brick & soft brick.
soft brick can be fixed by flashing some other roms or using official rom flasher.
hard brick can be fixed using a hardware called as JTAG which will be done by formatting the whole emmc storage as well as using some electrodes to reset the motherboard.
if you are having 4/6gb ram version then no problem but i doubt it for 8gb variant
but still as promised by realme bootloader unlocking rooting wont void your warranty it wont take more than 1-2 days to fix
so dont worry rush to nearest service center now:fingers-crossed:
if i was helpfull hit the thanks button please:good: btw i am from india, odisha, bhubaneswar
prince1995 said:
Your questions are quite meaningful there are 2 types of bricking hard brick & soft brick.
soft brick can be fixed by flashing some other roms or using official rom flasher.
hard brick can be fixed using a hardware called as JTAG which will be done by formatting the whole emmc storage as well as using some electrodes to reset the motherboard.
if you are having 4/6gb ram version then no problem but i doubt it for 8gb variant
but still as promised by realme bootloader unlocking rooting wont void your warranty it wont take more than 1-2 days to fix
so dont worry rush to nearest service center now:fingers-crossed:
if i was helpfull hit the thanks button please:good: btw i am from india, odisha, bhubaneswar
Click to expand...
Click to collapse
Hi, Thanks for the reply again.
I would like to correct one thing that rooting does void warranty. Realme only said that flashing custom roms/ unlocking bootloader is allowed under warranty but not rooting. BTW I didn't root it. I just unlocked, flashed twrp and tried flashing custom rom which didn't work so I ended up here.
Mine is 4gb/64 variant and it's a soft brick because the fastboot is working, twrp is also installed. The twrp restore or custom rom flashing is also going well without any errors but only unable to boot into system as it gets in the boot loop.
Yeah, the last resort would be to visit service centre but here the service is normally slow and most of them don't understand such things.
Anyway looking for a solution right here. I'm guessing that something is blocking the device from booting. I even saw bootlogo of GSI ROMs. I don't know it could be some encryption thing? or May be when I formatted the data, the vendor partition is wiped as well which is important for us to install GSI IMAGE.
But still why wouldn't the TWRP restore boot up properly??
Thetpcguy said:
Hi, Thanks for the fast response. Do you really think they can put back stock rom? If they have such a tool to restore stock rom then why wouldn't they already release it to general public? I'm not really hopeful that they have such tool to actually put back the stock rom. I know they have lot of proprietary stuff but can you confirm this?
Click to expand...
Click to collapse
actually I can flash it if I only know the Msmdownloadtool pass (the OFP extension is really new to me). I tried using Qfil and failed, when my cellphone was totally dead there wasn't even a logo for charging the battery when I tried it. which gave me hope, the detection of HS-USB QDLoader 9008 in Qfil. I am sure the service center can fix it because it is still detected by the computer, I said my cellphone suddenly died! finally they flashed again and in less than an hour. now twrp already installed magisk is installed just waiting for development :Hai:Hai
Thetpcguy said:
Hi, Thanks for the reply again.
I would like to correct one thing that rooting does void warranty. Realme only said that flashing custom roms/ unlocking bootloader is allowed under warranty but not rooting. BTW I didn't root it. I just unlocked, flashed twrp and tried flashing custom rom which didn't work so I ended up here.
Mine is 4gb/64 variant and it's a soft brick because the fastboot is working, twrp is also installed. The twrp restore or custom rom flashing is also going well without any errors but only unable to boot into system as it gets in the boot loop.
Yeah, the last resort would be to visit service centre but here the service is normally slow and most of them don't understand such things.
Anyway looking for a solution right here. I'm guessing that something is blocking the device from booting. I even saw bootlogo of GSI ROMs. I don't know it could be some encryption thing? or May be when I formatted the data, the vendor partition is wiped as well which is important for us to install GSI IMAGE.
But still why wouldn't the TWRP restore boot up properly??
Click to expand...
Click to collapse
I will look into this issue & comeup with something. mean while i think customer care is the best bet i hope they will reset it within a day.
i would suggest you try to wipe everything even internal storage put the rom on a sdcard/OTG & flash it from there.
the same kind issue arrised with my moto g(1st gen) this occurred because the device needed to be rooted already to flash some custom rom properly but mine wasn't hence i did get bootloop.
Stok recovery lazım
So, can you please give some time to this unbricking thing and provide a better solution with links. specially with that "boot+magisk+patch.img" part. It'd be really helpful. Thanks
Bro how can I fix this problem
Bro how can I fix this problem it's not booting it's give me a error the current image boot /recovery have been destroyed can not boot bro please help me
{
"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"
}
Please help
Bricked my realme 2 pro after flashing twrp.img and boot.img. After that I also tried r2x2 reacovery. But no effect. It stuck in logo. Please suggest any way
I unlocked the bootloader of my Rear 2 pro 4/64. And installed twrp but after the installation I'm stuck with a bootlppo. What can I do now pls help!!!?
I got the same problem before with my realme 2 rmx1809...the easiest way to flash stock rom is to flash stock recovery.img first and then flash ozip file from official realme website...to get the stock recovery.img is to decrypt and extract ozip file using the ozip decryptor that are available on github
Bootloop stuck please help asap!!
I was trying to install custom rom but I didn't took back up and wiped every thing on internal memory and also flashed stock recovery of realme 2 pro LOCKED the bootloader also I was hoping that I would be able to install stock rom by realme . But now am stuck at bootloop only realme logo appers
Basically I only have stock recovery on my phone and nothing else in the internal no OS installed bootloader is also locked so am not able to install twrp recovery to please help me install any rom .I am stucked due to lockdown no Service center is open. Please help asap??? I can't leave without my phone in this lockdown
Hello!
I bought an SM-N910G on ebay recently. The stock rom is a little bit slow and I would like to flash lineage or something else.
When i try to flash the latest version of twrp with odin it passes and shows the splash screen with the logo and version (all normal) but doesnt load and reboots to Android.
Does anyone have any ideas? ive tried most things that i found online but nothing works. the first available version on the twrp website does flash and work but wont flash latest lineage.
del32 said:
Hello!
I bought an SM-N910G on ebay recently. The stock rom is a little bit slow and I would like to flash lineage or something else.
When i try to flash the latest version of twrp with odin it passes and shows the splash screen with the logo and version (all normal) but doesnt load and reboots to Android.
Does anyone have any ideas? ive tried most things that i found online but nothing works. the first available version on the twrp website does flash and work but wont flash latest lineage.
Click to expand...
Click to collapse
Which bootloader is active?
So 3.6.2-9-0 doesn't start?
Tried flashing that .img using old TWRP as well or only .tar with Odin?
What did 3.1.0-0 say when flashing LOS fails?
bmwdroid said:
Which bootloader is active?
So 3.6.2-9-0 doesn't start?
Tried flashing that .img using old TWRP as well or only .tar with Odin?
What did 3.1.0-0 say when flashing LOS fails?
Click to expand...
Click to collapse
sorry i am not sure what you mean by which bootloader is active, is there a way to check this?
Nope, it just loads on the splash screen for a while then boots back to android
I have tried old twrp to flash and odin tar
It said an error about this rom is for *phone* you are using blank or something along those lines.
Afaik 3.5(?) is the only one that can install past oreo roms
del32 said:
sorry i am not sure what you mean by which bootloader is active,
is there a way to check this?
Click to expand...
Click to collapse
That's the one from the stock firmware you came from.
Should be the latest stock possible.
Did you check or can you tell?
del32 said:
Nope, it just loads on the splash screen for a while then boots back to android
I have tried old twrp to flash and odin tar
It said an error about this rom is for *phone* you are using blank or something along those lines.
Click to expand...
Click to collapse
Can you provide a screenshot?
del32 said:
Afaik 3.5(?) is the only one that can install past oreo roms
Click to expand...
Click to collapse
Well mine is on 3.6.1_9-0 and currently on Havoc 4.16 I got from the telegram group.
Has of course the battery drain problem (like all A11 custom versions for this device) when shut down.
With that TWRP I've installed A11 versions of LOS, crDroid and Havoc mulitple times.
bmwdroid said:
That's the one from the stock firmware you came from.
Should be the latest stock possible.
Did you check or can you tell?
Can you provide a screenshot?
Well mine is on 3.6.1_9-0 and currently on Havoc 4.16 I got from the telegram group.
Has of course the battery drain problem (like all A11 custom versions for this device) when shut down.
With that TWRP I've installed A11 versions of LOS, crDroid and Havoc mulitple times.
Click to expand...
Click to collapse
im using the latest 6.0.1 australia optus firmware (im australian and on optus)
there were bootloader files there available there for download but i dont think they worked for me. and also gave me no service in android
I am currently at school, so i will be able to provide a screenshot later
should i try a different stock firmware version/ different country carrier when i get home?
del32 said:
im using the latest 6.0.1 australia optus firmware (im australian and on optus)
Click to expand...
Click to collapse
So that should be ok.
del32 said:
...
should i try a different stock firmware version/ different country carrier when i get home?
Click to expand...
Click to collapse
No idea if that wil do any good or even harm your device.
I know that on some that works but idk about yours.
Perhaps it will help to start from scratch flashing the latest stock if available via samfirm_reborn_3.6.3 (gets it directly from Samsungs servers).
bmwdroid said:
So that should be ok.
No idea if that wil do any good or even harm your device.
I know that on some that works but idk about yours.
Perhaps it will help to start from scratch flashing the latest stock if available via samfirm_reborn_3.6.3 (gets it directly from Samsungs servers).
Click to expand...
Click to collapse
I'll try samfirm_reborn_3.6.3
currently installing the files it needs
{
"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"
}
@del32 which files?
Didn't need any additional ones on my W11 system.
SamFirm_Reborn itself starts directly without installation.
Took it from here:
GitHub - ivanmeler/SamFirm_Reborn
Contribute to ivanmeler/SamFirm_Reborn development by creating an account on GitHub.
github.com
bmwdroid said:
@del32 which files?
Didn't need any additional ones on my W11 system.
SamFirm_Reborn itself starts directly without installation.
Took it from here:
GitHub - ivanmeler/SamFirm_Reborn
Contribute to ivanmeler/SamFirm_Reborn development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
not sure what it needed but i just installed anyways and it all worked
used the same github link
also now in twrp, getting error 1 got a screenshot
del32 said:
not sure what it needed but i just installed anyways and it all worked
used the same github link
also now in twrp, getting error 1 got a screenshot
Click to expand...
Click to collapse
Well your device is trltedt so ROM should fit.
Which TWRP right now?
Did updaing it work?
You did "Format data" after wiping?
Tried with 2nd download of that ROM?
Tried crDroid or Havoc?
Once when I had flashing problems I changed filesystem of several partitions to and fro which helped.
If that all doesn't help I'ld start from scratch.
bmwdroid said:
Well your device is trltedt so ROM should fit.
Which TWRP right now?
Did updaing it work?
You did "Format data" after wiping?
Tried with 2nd download of that ROM?
Tried crDroid or Havoc?
Once when I had flashing problems I changed filesystem of several partitions to and fro which helped.
If that all doesn't help I'ld start from scratch.
Click to expand...
Click to collapse
I am using 3.1.0
I tried a later version and still didnt work, 3.2.2 does not even work!!!
Yes, format data after wiping.
I have tried to redownload
will try havoc right now
@bmwdroid
same issue with havoc, error one and your device is blank
not sure what happened with it
del32 said:
@bmwdroid
same issue with havoc, error one and your device is blank
not sure what happened with it
Click to expand...
Click to collapse
I suppose you definitely need a higher TWRP version but don't understand why you can't flash it.
What does TWRP say when you flash a higher version?
@del32 regarding higher TWRP.
As I understood you you're either flashing 3.5 or higher using Odin and it then TWRP doesn't start afterwards.
Correct?
What happens when you flash high TWRP...img using the older 3.1. TWRP and reboot after that into recovery from TWRP menu?
bmwdroid said:
@del32 regarding higher TWRP.
As I understood you you're either flashing 3.5 or higher using Odin and it then TWRP doesn't start afterwards.
Correct?
What happens when you flash high TWRP...img using the older 3.1. TWRP and reboot after that into recovery from TWRP menu?
Click to expand...
Click to collapse
I just got it to work!!! TWRP 3.5.2 and Havoc are running!!!
i was recording a video to show what i did and how it failed and it just worked
as long as i dont screw around with twrp i should be fine, thank you for your help.
if it wasnt for your response i was just going to give up and not bother.
Your browser is not able to display this video.
@del32 glad I could somewhat help.
May I quote from the film "Galaxy Quest":
Never give up, never surrender
Additional advices: I saw you rebooting after flashing but it's recommended to wipe Cache/Dalvik before the reboot.
It's useful to activate "advanced reboot" so that you can directly reboot to TWRP from the system without button combo.
When you want to get a higher TWRP you can flash it directly within the old one using a .img file.
Worked always for me so it should for you as well.
And you could mark the thread as solved so that others have no need to answer.
bmwdroid said:
@del32 glad I could somewhat help.
May I quote from the film "Galaxy Quest":
Never give up, never surrender
Additional advices: I saw you rebooting after flashing but it's recommended to wipe Cache/Dalvik before the reboot.
It's useful to activate "advanced reboot" so that you can directly reboot to TWRP from the system without button combo.
When you want to get a higher TWRP you can flash it directly within the old one using a .img file.
Worked always for me so it should for you as well.
And you could mark the thread as solved so that others have no need to answer.
Click to expand...
Click to collapse
Thank you very much, also ive never had issue with not wiping after flash but ill keep it in mind and try to remember for later on
I also had advanced reboot on but i didnt have an os on the phone at time of recording
once again, many thanks!!!!!!!
so excited to have Havoc on my phone
del32 said:
Thank you very much, also ive never had issue with not wiping after flash but ill keep it in mind and try to remember for later on
I also had advanced reboot on but i didnt have an os on the phone at time of recording
once again, many thanks!!!!!!!
so excited to have Havoc on my phone
Click to expand...
Click to collapse
Which Havoc version btw?
bmwdroid said:
Which Havoc version btw?
Click to expand...
Click to collapse
4.6, working nicely on android 11
faster than i thought it would be!
@del32 here you find much newer ones: