H3G firmware reboots after instaling any rom - Galaxy Note 3 Q&A, Help & Troubleshooting

Hi all. I'm not a newbie. I've been rooting phones since galaxy s2 and I think I'm pretty good in it. A friend of mine is using n9005 in UK that was locked on three uk and he asked me if I could root his device and make it look better with some note 7 ported rom. I asked him to unlock the phone with his network provider and he did it. After all he could put any carrier's sim card and use it. I managed to install philz cwm and latest supersu and all was good until I installed a rom. The phone started rebooting as soon as I put a sim card. Any sim card. I tried different roms and the phone behaved exactly the same. With no sim card the phone worked like a charm. Is there any way I can install a rom and make it work and behave like a phone. Before posting the thread I tried to find the solution myself checking throughout the internet but with no success. Any help would be more then welcome and appreciated.

I recommend using twrp as many newer roms require it for installation.

tomekostka said:
Hi all. I'm not a newbie. I've been rooting phones since galaxy s2 and I think I'm pretty good in it. A friend of mine is using n9005 in UK that was locked on three uk and he asked me if I could root his device and make it look better with some note 7 ported rom. I asked him to unlock the phone with his network provider and he did it. After all he could put any carrier's sim card and use it. I managed to install philz cwm and latest supersu and all was good until I installed a rom. The phone started rebooting as soon as I put a sim card. Any sim card. I tried different roms and the phone behaved exactly the same. With no sim card the phone worked like a charm. Is there any way I can install a rom and make it work and behave like a phone. Before posting the thread I tried to find the solution myself checking throughout the internet but with no success. Any help would be more then welcome and appreciated.
Click to expand...
Click to collapse
What's the version of your bootloader and modem ?
Did you tried to update them ?
What custom roms do you tried ?
audit13 said:
I recommend using twrp as many newer roms require it for installation.
Click to expand...
Click to collapse
Please check your information.

Check what information? Odin is used for stock ROM and twrp is often used for custom roms.

audit13 said:
Check what information? Odin is used for stock ROM and twrp is often used for custom roms.
Click to expand...
Click to collapse
The guy said he already flashed and used Philz recovery to try some custom roms.

Thanks for the clarification.
Philz and cwm have not been updated for a long time and all recent custom roms need twrp which is why I suggested using twrp.

audit13 said:
Thanks for the clarification.
Philz and cwm have not been updated for a long time and all recent custom roms need twrp which is why I suggested using twrp.
Click to expand...
Click to collapse
I have no doubt in your good will
I just wanted to say that TWRP is not mandatory for flashing new ROMs.
Even if he is old, Philz is perfectly capable of handling Aroma installers, while the latest available versions of TWRP can't, as you know.
The most recent roms use the same install scripts that date back to years.

Depending on the ROM, twrp is recommended by the developer and the op's problem may be related to using cwm as the recovery. I'm not saying cwm is the problem but the possibility exists.

Guys I didn't want to stir up a hornet's nest. I appreciate your both advises but I don't think that it's a problem with a sort of recovery. By the way I tried TWRP but the phone just seemed to not accept any other recovery then Philz. Like I mentioned earlier I successfully managed to root the device, what I didn't mention was that I managed even to install stock firmware different then H3G from Three UK via odin and while rooted, the phone was working just fine. But when I installed roms (darklord, aryamode and fake nougat ) the phone just went crazy after inserting a sim card. When looking for the solution on internet I found information about changing PIT file. So I found the PIT file proper for the UK area and tried it but I almost bricked the phone definitely. Fortunately I managed to bring it back to normal but like I mentioned it works with a sim card on stock rooted firmware.

You confirmed the model number in download mode?
Did you use Odin to install twrp?
I'm not sure why the phone would not accept twrp as it has been used on the n9005 by XDA members for a while.
Darklord and Arayamod can use Philz or twrp because they use aroma installers. Did you try a rom that doesn't use aroma?
If the pit file is for the phone and you are flashing it with the proper version of Odin and stock ROM, not sure why it would cause a near brick. What error message did you get in Odin?

Yes I confirmed the model and yes I used odin the latest version. Unfortunately I wasn't much interested with the message odin gave after I installed PIT fie but came as failed milliseconds after I pressed start button. I don't know maybe it wasn't 100% proper PIT file. But the most interested fact is that before installing roms the phone worked and behaved properly with different sim cards and didn't want to after. Right now I can't try other roms as I had to give the phone back but as soon I have it back I will try different roms without aroma and maybe I'll start from something lighter then ported roms, and then if I succeed maybe i'll be able to flash ported roms. I had the phone only for a couple of hours and I didn't have time to try other roms. I focused on n7 ported ones because that what a friend of mine wanted and I didn't take into account the fact that it might cause so many issues. But thanks for your help anyway.

Related

Software update help/call doesn't work

my galaxy s 4 is running 4.3 since the new update for 4.4.2 came out it tried to install itself but could not I cannot reset or update my phone for some reason I rooted my phone and also install safe strap none of the roms work with safe strap either I cannot install anything on my phone or update I also tried using odin to install the new update but no luck it says fail i unrooted my phone and tried to root it with odin but no luck. The reason I am trying to install a new software on it its because ever since the new update tried to install itself I think it messed with the calling function everytime i receive or send a call I cannot be hear or I cannot hear the other person all speakers work. When I had safestrap on I could do a factory reset and everything would work fine but then it would stop working again I dont think its speaker problems but if anyone can help me with my problem it would be great ><
I also voided my warrante when I tried to install stock firm ware 4.4.2 through odin it gave a binary count 1 and stuff and it said on the dowload mode warrante is void as well when i boot up my phone it says custom I dont know how to get rid of that either
trunks_ss2 said:
my galaxy s 4 is running 4.3 since the new update for 4.4.2 came out it tried to install itself but could not I cannot reset or update my phone for some reason I rooted my phone and also install safe strap none of the roms work with safe strap either I cannot install anything on my phone or update I also tried using odin to install the new update but no luck it says fail i unrooted my phone and tried to root it with odin but no luck. The reason I am trying to install a new software on it its because ever since the new update tried to install itself I think it messed with the calling function everytime i receive or send a call I cannot be hear or I cannot hear the other person all speakers work. When I had safestrap on I could do a factory reset and everything would work fine but then it would stop working again I dont think its speaker problems but if anyone can help me with my problem it would be great ><
I also voided my warrante when I tried to install stock firm ware 4.4.2 through odin it gave a binary count 1 and stuff and it said on the dowload mode warrante is void as well when i boot up my phone it says custom I dont know how to get rid of that either
Click to expand...
Click to collapse
There are custom roms designed to work with Safestrap.
If you want to use the stock rooted rom, you need to use the odin.
Sometime, if there is a conflict between the firmware/bootloader and your modem or between kernel and firmware, there could be problem not getting wifi or call did not work.
Please tell me about your phone.
1. model
2. Baseband
3. Kernel version
3, build number.
sway8966 said:
There are custom roms designed to work with Safestrap.
If you want to use the stock rooted rom, you need to use the odin.
Sometime, if there is a conflict between the firmware/bootloader and your modem or between kernel and firmware, there could be problem not getting wifi or call did not work.
Please tell me about your phone.
1. model
2. Baseband
3. Kernel version
3, build number.
Click to expand...
Click to collapse
model-----sgh 1337 ATT
bb-----1337ucuemk2
kernel------2.4.0-1921628
built #--------jss15j.i337ucumk2
thanks for replying ><
I tried using several different roms but they woulnt boot up with ss but none would boot up
trunks_ss2 said:
model-----sgh 1337 ATT
bb-----1337ucuemk2
kernel------2.4.0-1921628
built #--------jss15j.i337ucumk2
thanks for replying ><
I tried using several different roms but they woulnt boot up with ss but none would boot up
Click to expand...
Click to collapse
You are still on MK2 firmware/bootloader. There must be an error in your software that would prevent you from getting the OTA.
Since you are in MK2 the safestrap version you are using must be 3.71.
You are using the rooted rom so that you see the custom sign every time you boot. I am seeing that sign every time I boot my phone too.
Be patient and let's go step by step.
First try to install the stock MK2 files and see whether you phone works. All the files you need, all the instructions you need to follow, all the options that you can choose can be found here.
I would choose MK2 all in one. Flash it with Odin see the phone is working.
sway8966 said:
You are still on MK2 firmware/bootloader. There must be an error in your software that would prevent you from getting the OTA.
Since you are in MK2 the safestrap version you are using must be 3.71.
You are using the rooted rom so that you see the custom sign every time you boot. I am seeing that sign every time I boot my phone too.
Be patient and let's go step by step.
First try to install the stock MK2 files and see whether you phone works. All the files you need, all the instructions you need to follow, all the options that you can choose can be found here.
I would choose MK2 all in one. Flash it with Odin see the phone is working.
Click to expand...
Click to collapse
okay thank you so much!! i will try it and re post when iam done ><

spftbricked Telus S4

So a few days ago i downloaded a rom for my Telus SGH-i337m which gave me apps and the features from the S5. I installed it and all that, but then it failed. So i tried to use my back up but it was corrupted as well. So I thought i can go online and find a stock image, i found many, but then I think i installed the image for a GT505 by accident. This gave me my software back but then i could't use my wifi or my data. So i found a proper SGH-i337m rom and installed it, my wifi came back but my data didnt. I thought it was because of the wrong modem, so i installed a few different modems and nothing worked. But today when i downloaded a different modem and installed it using odin mobile pro. It was installing and it rebooted, but then it got stuck there with the ODIN logo. I removed the battery and turned the phone on but not it says "Firmware upgrade encountered an issue..... please connect to kies". I tried connecting to kies but couldn't.
if someone could provide me with fully stock firmware and modem with easy instructions i would appreciate it, I'm so cheesed of my phone not working now
Did you have a custom recovery installed? Have you tried to go into recovery? Vol up home power. Make sure Samsung drivers are installed on your computer. Save a rom on your computer that you know works and place it on the sd card of your phone. Install rom. Try a stock rom version. Maple leaf by ib4stid would be a good one.
I just reread. Sorry I don't think my suggestion will help. Good luck.
Sent from Canadian i337m using Tapatalk
unsaddledhalo said:
if someone could provide me with fully stock firmware and modem with easy instructions i would appreciate it, I'm so cheesed of my phone not working now
Click to expand...
Click to collapse
http://www.sammobile.com/
~wolverine~ said:
http://www.sammobile.com/
Click to expand...
Click to collapse
I tried from here but still havent been able to succefully download any firmware
unsaddledhalo said:
I tried from here but still havent been able to succefully download any firmware
Click to expand...
Click to collapse
what do you mean? you need to create an account to be able to download. hope u got it sorted or by now
If you can give smoe more information about if you have a custom recovery installed (which one), can you connect to PC and move files to the external sd card, which modem you have installed and does the phone boot at all?
The procedure should be, root... download rom, ensuring it is for the i337m and not the i337 (2 different models) install custom recovery (I like TWRP (shouold be version 2.6 or lower.. some suggest 2.5 see mapleleaf rom OP..... others use Philz recovery... I don't have any experience with that).... install rom... let it boot up and run for a few minutes... then if you dont have the proper modem install the NC1 modem found on this forum...(I never flash the nonhalos file) I like to use Odin PC rather than moblie Odin... make sure you take off auto reboot as the flash takes longer than Odin allows before rebooting... You may need to enter your APN settings in settings... wrong APN's will result in no data...
As for roms, I would start with Maple leaf and see what you think... If you need to go back to stock, sam mobile roms are all Bell so you will see some Bell software (not to worry) and you will need to enter your APN's... then you can install a custom rom... again can't stress enough to choose one that is for i337m
The other thing you want to watch is bootloader versions.... once you go up in versions.. you can't go back...
Thanks for the help! I don't know how that I forgot the fact that I have a TelusS4 with a Wind sim in it, and cuz I formatted the phone and crashed the software, the bandwidths went to the stock Telus ones. But then I used a software and now I can use my wind sim on my phone!
Btw what are the best roms out there that look completely stock but provide tons of new features?
Sent from my SGH-I337M using XDA Premium 4 mobile app
unsaddledhalo said:
Thanks for the help! I don't know how that I forgot the fact that I have a TelusS4 with a Wind sim in it, and cuz I formatted the phone and crashed the software, the bandwidths went to the stock Telus ones. But then I used a software and now I can use my wind sim on my phone!
Btw what are the best roms out there that look completely stock but provide tons of new features?
Sent from my SGH-I337M using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Stock roms, I use Mapleleaf, I have also tried Google Play edition by Danvh but went back to maple leaf. I take it you are now back to stock and rooted, before you flash a rom, make sure you do a backup of your current stock rom so you have a easy way to go back. Make sure you back up your imei files also... might come in handy some day... I did both a full backup plus a seperate back up og just the iemi file... like i said before.... if you entend on going backwards from 4.4.3 or 4.4.2 to anything else do not change your bootloader... before you flash a rom make sure it will not change your bootloader... if it is going to i suggest you unzip the rom, remove the bootloader file and rezip then flash... it is up to you though... there is no going backwards on bootloaders......

Flashing a Note3, asking for help...

First, I have installed a ROM on my phone before and I followed very specific instructions. I am a developer in the land of microsoft so I recognize I am very much a newbie here.
Now, on to what I have now and what I want to do.
1. I have a Note 3. The SM-N9005. The baseband version is: N900W8.... suffice to say it is a canadian phone. If the rest of the baseband numbers are important I will post them, just ask.
2. I want to install the Alliance ROM, it seems to have what I am looking for.
3. When I rooted and ROMed my phone years ago I used the following thread: http://forum.xda-developers.com/show....php?t=2614772
4. Currently my phone is running a Jedi ROM from the vintage of that thread. However I must have made a mistake back then because the Hotspot feature does not work. Making the hotspot feature work again is my primary reason for undertaking this operation. The 4G works, I can use the Internet on the phone just fine. The wireless works I can connect to a wireless signal and use the internet that way (I confirmed this was working with mobile data off). The hotspot will allow a connection from a device (such as my laptop), but no data passes between the 4G connection and the connected computer.(yes, I turned on Mobile Data On) I have tried this using different computers connected to the hotspot to confirm it is the fault of the Note3.
Back when I did this flashing thing before I had to be careful to get the right CSC file and modem file and a few other steps. I had to specify the correct CSC file in addition to the rom I wanted to flash.
With that background, my questions are below (if you need any more info to point me in the right direction, just ask):
One last note... I will be performing any and all instructions from a macbook pro Mid 2012 with no other devices on the usb host controller running a near virgin copy of windows 7.
-----------------------------------------------------------
Do I need to worry about CSC files, modem files and so on to Flash to Alliance ROM and still have everything work? I ran across a thread that said that some ROMs have all the CSC files in them, but I cannot find any direct information (or I missed it) about the Alliance ROM with regards to CSC files and the like.
I thought I had TWRP installed, but when I boot to recovery the top two lines read
line1: Android system recovery <3e>
line2: KOT49H.N9005XXUENB4
Is this TWRP? Should I download the latest TWRP for my device and flash it using the AP button from Odin 3.10? If there is a different technique I should use, I will try it.
The instructions say that if I am not installing from stock 4.4.2 or stock 5.0 that I should install stock first, then install the alliance rom. I visited the sammobile website and there are no ROMs for the USA or Canada there... am I missing something or should I just use the UK ROM from that website? I guess I am not sure how to identify the correct ROM for Canada.
I did load the Alliance ROM 8.2 onto my SD card and attempted to use the option apply update from external storage and it failed. Nothing happened at all and the phone eventually rebooted and the ROM never installed.
Thanks in advance for any help you can provide me on this endeavour. I am largely looking for resources that I have not been able to find up until now. I am okay with help such as Read This Post! and so on.
If the phone is an n9005, not sure how the baseband can be n900w8 as the n9005 was never sold by Canadian carriers as far as I know.
Here's a link to the stock n900w8 firmware: http://www.sammobile.com/firmwares/database/SM-N900W8/
wizengamot said:
Thanks in advance for any help you can provide me on this endeavour. I am largely looking for resources that I have not been able to find up until now. I am okay with help such as Read This Post! and so on.
Click to expand...
Click to collapse
First of all, you should detect what device you own. You can install this APP and add some screenshots for avoid problems and give us more info about your device (IMEI not necessary).
We will try to detect if you own a clone, a SM-N9005 or SM-N900W8.
Additional Info as requested
Here are the screenshots that were requested. Thanks for your help. Yes, I will and continue to use the thanks button as well.
wizengamot said:
Here are the screenshots that were requested. Thanks for your help. Yes, I will and continue to use the thanks button as well.
Click to expand...
Click to collapse
I think you should flash the stock rom first via ODIN. Coz your baseband don't fit with your bootloader and your PDA either.
PS: You can use MEGA mirror as well :highfive:
I have the stock ROM from SamMobile. I am set to flash the phone. I have everything set but I searched the forum as a final check to make sure I am doing the right things and I found a post that says I need a PIT file. I can find a PIT file for HLTE verizon phones but I do not know if that PIT file works with the image I downloaded from sammobile. Of course I am connecting the dots from the info program I ran where is says on the general tab that the phone is of type hlte.
When I click on PIT in Odin it says this function is for engineers only. As a programmer myself I would put a message like that for a function I don't want people using needlessly but it does give me pause to ask about it. As they say Flash in Haste...Cry at Leisure..
Many thanks to you all. I have installed the stock ROM and it works. I can make phone calls, wifi works, 4g works, and hotspot works.. YAYA... Now, I would do the alliance rom but I can honestly say I am not sure I want to mess with it. I want the phone call recording feature but that is all I want...It would be the only reason to do the alliance rom. And it appears as though that rom is not done the same way as the stock rom as there is no md5 file.
anyhow.. thanks again to all who helped. I have thanked each post as well. If you have some tips based on my above info, I would be very grateful.
There are quite a lot of call recording apps which work well as far as I know, ACR being one of the example.
Only tar or tar.md5 files are flashed in Odin. Any non-stock ROMs are flashed using a custom recovery.
You can flash a custom recovery to your phone using Odin in the PDA/AP box from here: https://twrp.me/Devices/ Just use the latest tar file.
Once you have a custom recovery on the phone, you can create a backup of your existing ROM, then flash a custom ROM.

Flashing custom COJ5 firmware to 910C

Good day everyone.
Got a strange problem trying to upgrade my Note 4 (910C) to eRobot 11 (11.1) based on the latest COJ5 base.
After flashing device just does not start up - the black screen with "Galaxy Note 4" hangs and nothing goin on. Bootloops sometimes
I tried eRobot and another custom ROM based on COJ5 - the same result.
COI4 based ROM works fine.
Being flashed via ODIN the COJ5 based ROM works fine.
I have latest TWRP recovery, COJ5 bootloader and already have tried flashing service 4-file ROM.
If anyone got any information that can help - please welcome!
Thanks!
kurkovda said:
Good day everyone.
Got a strange problem trying to upgrade my Note 4 (910C) to eRobot 11 (11.1) based on the latest COJ5 base.
After flashing device just does not start up - the black screen with "Galaxy Note 4" hangs and nothing goin on. Bootloops sometimes
I tried eRobot and another custom ROM based on COJ5 - the same result.
COI4 based ROM works fine.
Being flashed via ODIN the COJ5 based ROM works fine.
I have latest TWRP recovery, COJ5 bootloader and already have tried flashing service 4-file ROM.
If anyone got any information that can help - please welcome!
Thanks!
Click to expand...
Click to collapse
Try flashing a kernel after flashing COJ5 ROM. Clear cache/davlik cache also
http://forum.xda-developers.com/note-4/development/n910c-spacex-kernel-v0-1-auto-root-t3192875
http://forum.xda-developers.com/note-4/development/kernel-suemax-kernel-lite-v1-0-t3221865
dicksteele said:
Try flashing a kernel after flashing COJ5 ROM. Clear cache/davlik cache also
Click to expand...
Click to collapse
Done.
I even tried flashing bootloader via ODIN after flashing ROM.
Got bootloop on Sixperience v5 and erobot 11.1.
kurkovda said:
Done.
I even tried flashing bootloader via ODIN after flashing ROM.
Got bootloop on Sixperience v5 and erobot 11.1.
Click to expand...
Click to collapse
ODIN Flash this
http://forum.xda-developers.com/note-4/development/rom-note-4-mod-t3244665
It should boot up fine. Blow past all the setup.
Boot into Download Mode, ODIN flash TWRP.
https://dl.twrp.me/treltexx/twrp-2.8.7.0-treltexx.img.tar
Boot into recovery then try flashing Six or e-Robot
I have the same phone and I've done this more time that I can count (TODAY !!)
dicksteele said:
ODIN Flash this
http://forum.xda-developers.com/note-4/development/rom-note-4-mod-t3244665
It should boot up fine. Blow past all the setup.
Boot into Download Mode, ODIN flash TWRP.
https://dl.twrp.me/treltexx/twrp-2.8.7.0-treltexx.img.tar
Boot into recovery then try flashing Six or e-Robot
I have the same phone and I've done this more time that I can count (TODAY !!)
Click to expand...
Click to collapse
Done already.
As I've rote - being flashed via ODIN the COJ5 based rom works fine
After flashing this ROM via ODIN I've tried flashing recovery, then geting root by installing prerooted krernel, then flashing custom ROM.
You've missed the point with flashing prerooted kernel, does this matter?
kurkovda said:
Done already.
As I've rote - being flashed via ODIN the COJ5 based rom works fine
After flashing this ROM via ODIN I've tried flashing recovery, then geting root by installing prerooted krernel, then flashing custom ROM.
You've missed the point with flashing prerooted kernel, does this matter?
Click to expand...
Click to collapse
Depends which ROM, and if it has a kernel in install. Looking through most of them, it is included.
How long are you waiting for it to boot? At the Samsung Logo depending on kernel it could take up to 5-10 minutes.
If it's stuck at first Galaxy Note 4 screen, usually that's kernel. My experience anyways. And I've flashed every 5.1.1 ROM here. Multiple times for many of them.
dicksteele said:
Depends which ROM, and if it has a kernel in install. Looking through most of them, it is included.
How long are you waiting for it to boot? At the Samsung Logo depending on kernel it could take up to 5-10 minutes.
If it's stuck at first Galaxy Note 4 screen, usually that's kernel. My experience anyways. And I've flashed every 5.1.1 ROM here. Multiple times for many of them.
Click to expand...
Click to collapse
It stucks on Galaxy Note 4 screen and bootloops sometimes.
ROMs eRobot and sixperience I've flashed has kernels inside, eRobot even has four via Arome, and I've tried each of them
Well, will try your method, thanks a lot for help, will write down about the results!
kurkovda said:
It stucks on Galaxy Note 4 screen and bootloops sometimes.
ROMs eRobot and sixperience I've flashed has kernels inside, eRobot even has four via Arome, and I've tried each of them
Well, will try your method, thanks a lot for help, will write down about the results!
Click to expand...
Click to collapse
Switch off the phone and remove the battery.Wait 2 minutes then re-insert the battery.Then flash the boot loader via odin.
kakkooran said:
Switch off the phone and remove the battery.Wait 2 minutes then re-insert the battery.Then flash the boot loader via odin.
Click to expand...
Click to collapse
Will be able to try this out later this evening, thanks!
kurkovda said:
Will be able to try this out later this evening, thanks!
Click to expand...
Click to collapse
I'm not sure what that will accomplish. The bootloader gets flashed during the stock ROM install I posted.
That's the sboot.bin file that gets flashed in ODIN not the boot.img that is the kernel with TWRP. Big difference.
Try to enter download mode by shutting off mobile (remove battery if it wont work) and enter downloade mode with 3 finger combo.
I had observed sometimes that flashing with odin by entering downloadmode from software will cause problems....
Maybe this will help...
Greetings
HalloSpencer said:
Try to enter download mode by shutting off mobile (remove battery if it wont work) and enter downloade mode with 3 finger combo.
I had observed sometimes that flashing with odin by entering downloadmode from software will cause problems....
Maybe this will help...
Greetings
Click to expand...
Click to collapse
I'm not sure you are speaking about MY problem
Flashing by ODIN causes no problem, they start after flashing ane custom COJ5 ROM via TWRP.
And I use "hardware" method every time I need to get to ODIN mode
Just wanted to make clear that you flashed COJ5 bootloader using "hardware method".... I actualy cant remeber were I read that flashing otherwise can cause problems (without odin failure)....
And yes I was speaking about your problem
dicksteele said:
ODIN Flash this
http://forum.xda-developers.com/note-4/development/rom-note-4-mod-t3244665
It should boot up fine. Blow past all the setup.
Boot into Download Mode, ODIN flash TWRP.
https://dl.twrp.me/treltexx/twrp-2.8.7.0-treltexx.img.tar
Boot into recovery then try flashing Six or e-Robot
I have the same phone and I've done this more time that I can count (TODAY !!)
Click to expand...
Click to collapse
As for me this is wiered but that worked obviously 0_o
The phone is booting up now.
But could you please explain what was wrong with this ROMs, or with my phone, or with me?) And - will I need to repeat all this shaman dances to flash any other ROM?
Anyway, I owe you, thanks a lot!
Does anyone knows what makes N910C COJ5 refuses the downgrade? In theory, the downloading mode that ODIN uses should be controlled by the bootloader, correct? The code in the downloading mode is the one responsible for not allowing downgrades. Why can't we just flash a different bootloader that allows us to downgrade or did samsung created some mechanism to protect the current some parts from COJ5 bootloader from being replaced (I noticed I can flash different bootloaders, but the issue with downgrading persists). If we could completely replace the booloader, this would provide answers for this thread and at least 5 other threads diving in the same issue.
amidsal said:
Does anyone knows what makes N910C COJ5 refuses the downgrade? In theory, the downloading mode that ODIN uses should be controlled by the bootloader, correct? The code in the downloading mode is the one responsible for not allowing downgrades. Why can't we just flash a different bootloader that allows us to downgrade or did samsung created some mechanism to protect the current some parts from COJ5 bootloader from being replaced (I noticed I can flash different bootloaders, but the issue with downgrading persists). If we could completely replace the booloader, this would provide answers for this thread and at least 5 other threads diving in the same issue.
Click to expand...
Click to collapse
They did
amidsal said:
Does anyone knows what makes N910C COJ5 refuses the downgrade? In theory, the downloading mode that ODIN uses should be controlled by the bootloader, correct? The code in the downloading mode is the one responsible for not allowing downgrades. Why can't we just flash a different bootloader that allows us to downgrade or did samsung created some mechanism to protect the current some parts from COJ5 bootloader from being replaced (I noticed I can flash different bootloaders, but the issue with downgrading persists). If we could completely replace the booloader, this would provide answers for this thread and at least 5 other threads diving in the same issue.
Click to expand...
Click to collapse
The bootloader was not the issue in this thread. It was flashing ROMs.
Samsung obviously realized we had way to much freedom our phones and has tightened down the sboot.bin (COJ5 bootloader file)
You will notice in your ODIN flashes when trying to downgrade, that's the file it barfs on.
Which surprises me, that why I bought the 910C to get away from the locked down crap from ATT.
---------- Post added at 01:27 PM ---------- Previous post was at 01:21 PM ----------
kurkovda said:
As for me this is wiered but that worked obviously 0_o
The phone is booting up now.
But could you please explain what was wrong with this ROMs, or with my phone, or with me?) And - will I need to repeat all this shaman dances to flash any other ROM?
Anyway, I owe you, thanks a lot!
Click to expand...
Click to collapse
Good deal. Booting up on a Custom ROM?
I usually flash back to stock every now and then. Never hurts.
I'm running SIMPLROM5c. Running pretty good. I've tried them all. I usually run them a couple of days and see how I like it.
All of the ROMs have their own personality. Just find one that fits yours. I'm finding a stock one like SIMPLROM will probably be my daily one, but I have backups of the others to change whenever my mood changes.
The N5 and S6 features are cool, but I bought a Note 4 because it's a Note 4. If I wanted a Note5 or S6 I would have gotten one.
Now the S7 MAY make me change my mind. we'll see.
kurkovda said:
They did
Click to expand...
Click to collapse
And even if we have the device rooted, we can't overwrite the bootloader because of it is not possible interfere with the environment external to hypervisor (like the bootloader, kernel, etc.) unless someone finds a loophole, right? In this situation, wouldn't it be possible to overwrite the booloader completely if we could access the internal sd card and mounting it in a regular linux environment (similarly to the way people used to extract the xbox 360 using a probe). Could it be possible?
dicksteele said:
Good deal. Booting up on a Custom ROM?
I usually flash back to stock every now and then. Never hurts.
I'm running SIMPLROM5c. Running pretty good. I've tried them all. I usually run them a couple of days and see how I like it.
All of the ROMs have their own personality. Just find one that fits yours. I'm finding a stock one like SIMPLROM will probably be my daily one, but I have backups of the others to change whenever my mood changes.
The N5 and S6 features are cool, but I bought a Note 4 because it's a Note 4. If I wanted a Note5 or S6 I would have gotten one.
Now the S7 MAY make me change my mind. we'll see.
Click to expand...
Click to collapse
Yep, the ROM has booted up and works
I'm a kind of newbe for Note4 and now just want to find out who is who But I've stucked being unable to flash the new base ROM, and unfortunately on my native forum there are just a very few rommakers, and no one could give me some info about this issue.
Now I'll test sixperience, and if it's not as good as I hope will try something else
kurkovda said:
Yep, the ROM has booted up and works
I'm a kind of newbe for Note4 and now just want to find out who is who But I've stucked being unable to flash the new base ROM, and unfortunately on my native forum there are just a very few rommakers, and no one could give me some info about this issue.
Now I'll test sixperience, and if it's not as good as I hope will try something else
Click to expand...
Click to collapse
All the ROMs work great, and there's great support. It all depends on what you looking for in a ROM.
I think there's a little too much expectation from people that think jamming (porting) features from other phones (N5 and S6) is supposed to work perfectly on a Note 4.
A lot of work goes into trying to make it work. But if they want the features that are on that phone to work perfectly, buy that phone.
---------- Post added at 02:00 PM ---------- Previous post was at 01:56 PM ----------
amidsal said:
And even if we have the device rooted, we can't overwrite the bootloader because of it is not possible interfere with the environment external to hypervisor (like the bootloader, kernel, etc.) unless someone finds a loophole, right? In this situation, wouldn't it be possible to overwrite the booloader completely if we could access the internal sd card and mounting it in a regular linux environment (similarly to the way people used to extract the xbox 360 using a probe). Could it be possible?
Click to expand...
Click to collapse
I have read someone suggesting doing a NAND ERASE ALL in ODIN during the firmware flash. That should wipe the hell out of everything.
I'm waiting to hear back if he's done that on the OJ5 bootloader.
I've had my phone from a month, I'm not willing to take that chance yet.

After flashing original ROM, phone went into bootloop. Hard reset doesn't work.

My friend got an old phone from his dad, who had an old custom ROM installed on it, and asked me to return it to the original software.
I used ODIN 3.09 and installed the appropriate ROM which I downloaded from Sammobile.
The phone went into a bootloop, so I wiped the cache and when that didn't work, I wiped all data. After that the phone booted into the Welcome screen and my friend started to configure it. In the middle of the process, the phone rebooted, and now it loads into the Welcome screen, but reboots after a few seconds.
After that I've tried reflashing the software and doing multiple resets, to no avail. Any ideas?
Please let me know of any Ideas. I am very ashamed of damaging my friend's phone.
PS: I should say, I put a bootloader into ODIN the first time I flashed the software because some tutorial recommended it and I haven't seen that requierement in any other tutorial since. Might this be the cause? How could I test that?
What model what firmware what bootloader ??
JJEgan said:
What model what firmware what bootloader ??
Click to expand...
Click to collapse
The phone is a Note 3 N900 UB, the firmware I installed was N900UBSEBQB5, and to be honest, I can't quite tell what the bootloader is, the file I downloaded is just called "bootloader".
the file I downloaded is just called "bootloader
My guess is that's the fault as bootloaders are named same as firmwares
Example >>> BL_N9005ZSUGPJ2
Could be a bootloader for anything .because some tutorial recommended
Have you taken a chance to reflashing the official firmware with ordin , that would be helpful all the time.
After that you should make sure your phone work fine on the official rom .
Then update your Recovery to a third party Rec,like CWM or TWRP .
Next step,flashing an original rom.
larrycn said:
Have you taken a chance to reflashing the official firmware with ordin , that would be helpful all the time.
After that you should make sure your phone work fine on the official rom .
Then update your Recovery to a third party Rec,like CWM or TWRP .
Next step,flashing an original rom.
Click to expand...
Click to collapse
Thats wrong .

Categories

Resources