Related
Guys,
I need your urgent assistance .. I think I have bricked my phone and need assistance.. Basically I was running the Official ICS ROM which I got from XDA website it was the LQ2 kernel for the Galaxy Note.
Last night I custom flashed the Criskelo ICS v7 ROM but wasn't too happy and wanted to go back to stock ICS .. So I went into PC Odin and flashed the stock ICS Firmware.. upon booting I went into CWM (Volume up + home+power) did a factoy reset and cache, dalvik cache wipe.. Then reboot system.. The phone was stuck on the Samsung Galaxy Note screen .. So I tried to Flash the Stock ICS LQ2 rom again via PC Odin and now it just hangs almost at 90% at factoryfs.img?
Am I completely messed up or is there a way to resolve this please can you guys assist me in what I must do.. I don't know if this is a soft or super brick..
Many Thanks..
PS: I even did the PIT file thing and still no joy
you custom flashed??
what do u mean u custom flashed??
Get a rom with bootloader in it. Don t use repartition. Make sure you flash the bootloader.
Sounds like you wiped from a stock Samsung kernel, which is a big no no. The only way to fix this is to repartition your phone with a .pit file that has been designed not to use the the corrupted sectors of your internal storage. If you search hard enough, you'll find a thread about it. I successfully recovered a phone I bricked way back with the first LP1 ICS kernel. It does work! You'll lose some space though.
http://forum.xda-developers.com/showthread.php?t=1667886
And there's the thread I was talking about.
tibosee said:
Get a rom with bootloader in it. Don t use repartition. Make sure you flash the bootloader.
Click to expand...
Click to collapse
Can you send me a link with a rom which has this please?
Here i had the same problem when I tried to flash my first rom. Just tried to flash on another computer and guess what... Successfully done!
Sent from my GT-I9100 using Tapatalk 2
smalmagal said:
Sounds like you wiped from a stock Samsung kernel, which is a big no no. The only way to fix this is to repartition your phone with a .pit file that has been designed not to use the the corrupted sectors of your internal storage. If you search hard enough, you'll find a thread about it. I successfully recovered a phone I bricked way back with the first LP1 ICS kernel. It does work! You'll lose some space though.
http://forum.xda-developers.com/showthread.php?t=1667886
And there's the thread I was talking about.
Click to expand...
Click to collapse
Yes I factory reset a STOCK ICS ROM .. please can you assist in what I need to do.. Which PIT file and which ROM Shall I try to flash with.. please assist.. Many thanks..
Thanks for your help guys .. followed the german dudes tutorial and downloaded the .PIT file and managed to re flash stock ICS .. Now the only issue is my internal memory is showing 8.24 GB.. what happened to the other approx 8GB? I thought the Note was 16GB? Before windows used to show it as 11GB but now showing 8.24 GB is there a fix for this or is the bad or do I have to live with it.. ?
read the whole tut again it tells you why since you have to move partition tables.
Yes...it's a rather small deal anyway...there are 64gb SD card after all.
mkohman said:
Thanks for your help guys .. followed the german dudes tutorial and downloaded the .PIT file and managed to re flash stock ICS .. Now the only issue is my internal memory is showing 8.24 GB.. what happened to the other approx 8GB? I thought the Note was 16GB? Before windows used to show it as 11GB but now showing 8.24 GB is there a fix for this or is the bad or do I have to live with it.. ?
Click to expand...
Click to collapse
My advice is "live with it". Coz what the "German dudes" pit files do is avoid the "locked" sectors in your internal card. While you can try different pit files or try create new partitions via adb -- you probably wont gain much.
Or you could send it to Sammy for a warranty claim, after resetting the flash counter and then bricking it again via odin using the original pit file. Basically what you need to do is erase all evidence that u tampered with it. This is a risky option... (You can tell them phone got messed up in kies upgrade). This happened to me (on an almost new note, so i kinda did the same, except that i went a step further and deleted the boot-loader as well = hard brick. However i dont recommend it). And they replaced the phone.
I emphasize again this is risky -- and do more research before if you do this.
Problem as of now is since you've modified the pit -- and also the phone is working, you cant claim now.
nipuna said:
My advice is "live with it". Coz what the "German dudes" pit files do is avoid the "locked" sectors in your internal card. While you can try different pit files or try create new partitions via adb -- you probably wont gain much.
Or you could send it to Sammy for a warranty claim, after resetting the flash counter and then bricking it again via odin using the original pit file. Basically what you need to do is erase all evidence that u tampered with it. This is a risky option... (You can tell them phone got messed up in kies upgrade). This happened to me (on an almost new note, so i kinda did the same, except that i went a step further and deleted the boot-loader as well = hard brick. However i dont recommend it). And they replaced the phone.
I emphasize again this is risky -- and do more research before if you do this.
Problem as of now is since you've modified the pit -- and also the phone is working, you cant claim now.
Click to expand...
Click to collapse
Thanks for your assitance bro.. I will live with it. .I don't mind loosing 3 gb .. Already got 32GB SD card so no issue. Just happy its all back up and running really.. Big thanks to the German brother you the man
Its Forest1971 who first wrote this workaround and it was hg42 who rewrote the pit file and it was Dr null who proposed this way, Its all XDA members who helped you out of this brick. Not some German sites. Google throws up German results first
I am not harsh by anyway saying this. Just want to write it as it happened.
Was witnessing all the issues.
I am writing a guide for Noobies for bricks. Guess I get some help ....
prabhu1980 said:
Its Forest1971 who first wrote this workaround and it was hg42 who rewrote the pit file and it was Dr null who proposed this way, Its all XDA members who helped you out of this brick. Not some German sites. Google throws up German results first
I am not harsh by anyway saying this. Just want to write it as it happened.
Was witnessing all the issues.
I am writing a guide for Noobies for bricks. Guess I get some help ....
Click to expand...
Click to collapse
I actually followed his guide and repartioned manually and only lost about one Gbyte vs using the pit file and losing over 3 G bytes. Took a lot of trial and error though
Sent from my GT-N7000 using Tapatalk 2
RE:
mkohman said:
Guys,
I need your urgent assistance .. I think I have bricked my phone and need assistance.. Basically I was running the Official ICS ROM which I got from XDA website it was the LQ2 kernel for the Galaxy Note.
Last night I custom flashed the Criskelo ICS v7 ROM but wasn't too happy and wanted to go back to stock ICS .. So I went into PC Odin and flashed the stock ICS Firmware.. upon booting I went into CWM (Volume up + home+power) did a factoy reset and cache, dalvik cache wipe.. Then reboot system.. The phone was stuck on the Samsung Galaxy Note screen .. So I tried to Flash the Stock ICS LQ2 rom again via PC Odin and now it just hangs almost at 90% at factoryfs.img?
Am I completely messed up or is there a way to resolve this please can you guys assist me in what I must do.. I don't know if this is a soft or super brick..
Many Thanks..
PS: I even did the PIT file thing and still no joy
Click to expand...
Click to collapse
hi! i was in the same state as you! now, listen very carefully. Now, all you have to do is to use another PC and run ordin. Everything should work fine! My note was soft-bricked yesterday night and i had tried endless counts of tries just to get it up and running. Just earlier today,I saw someone who posted a comment in a similar forum and suggested that you should try a different PC it worked. AND IT worked for me now, just use this pit file that i had upload and download any (G-N7000)stock firmware that has (code.md5, modem.md5 and csc.md5). just place the pit file in ordin. ( do note you will lose 3gb of your internal memory) and click start hopefully it worked for you
-yours truly-
zairui from Singapore
can you contact entropy before sending your unit to samsung??
entropy is looking, if im not mistaken, for a purely stock bricked note... kindly pm him
zairui said:
hi! i was in the same state as you! now, listen very carefully. Now, all you have to do is to use another PC and run ordin. Everything should work fine! My note was soft-bricked yesterday night and i had tried endless counts of tries just to get it up and running. Just earlier today,I saw someone who posted a comment in a similar forum and suggested that you should try a different PC it worked. AND IT worked for me now, just use this pit file that i had upload and download any (G-N7000)stock firmware that has (code.md5, modem.md5 and csc.md5). just place the pit file in ordin. ( do note you will lose 3gb of your internal memory) and click start hopefully it worked for you
-yours truly-
zairui from Singapore
Click to expand...
Click to collapse
Not necessary to use the 3gb regain patch.
There's a 1gb or 2gb regain patch also. And it's enough.
WJ
Sent from xda-developers Galaxy N7000 ICS 4.0.4 LRK / CriskeloROM v.11.1 / Speedmod K3-12
---------- Post added at 11:34 PM ---------- Previous post was at 11:26 PM ----------
mkohman said:
Guys,
I need your urgent assistance .. I think I have bricked my phone and need assistance.. Basically I was running the Official ICS ROM which I got from XDA website it was the LQ2 kernel for the Galaxy Note.
Last night I custom flashed the Criskelo ICS v7 ROM but wasn't too happy and wanted to go back to stock ICS .. So I went into PC Odin and flashed the stock ICS Firmware.. upon booting I went into CWM (Volume up + home+power) did a factoy reset and cache, dalvik cache wipe.. Then reboot system.. The phone was stuck on the Samsung Galaxy Note screen .. So I tried to Flash the Stock ICS LQ2 rom again via PC Odin and now it just hangs almost at 90% at factoryfs.img?
Am I completely messed up or is there a way to resolve this please can you guys assist me in what I must do.. I don't know if this is a soft or super brick..
Many Thanks..
PS: I even did the PIT file thing and still no joy
Click to expand...
Click to collapse
Though so many ppl told u alrd, i just want to say, in any case, when u r in ICS alrd, it is totally prohibited to do factory reset through CWM with samsung ICS original kernel.
When u need to wipe or factory reset, make sure u r on a safe kernel like speedmod or notecore.
If u want to recover ur note, just use the pit file method. It works.
Make sure u use the correct patch of 16gb or 32gb, depends on ur note.
Always try from the smallest patch, so u won't loose so many storage.
Anyway, latest CriskeloROm with speedmod is the best for battery life nd performance.
WJ
Sent from xda-developers Galaxy N7000 ICS 4.0.4 LRK / CriskeloROM v.11.1 / Speedmod K3-12
I'm having the same issue now.
I did wipe data / factory reset with stock ICS kernel and I think, I bricked the Note.
I didn't know there were such issue.
I couldn't find a ROM with 3 files (code.md5, modem.md5 and csc.md5).
Please kindly guide me where to find such ROM.
i bricked mine last week and used the patched pit files to restore i went through a few pit files b4 i found one that worked i now have about 9 gb nand left but my phone works and has jb on it now
anubis1126 said:
i bricked mine last week and used the patched pit files to restore i went through a few pit files b4 i found one that worked i now have about 9 gb nand left but my phone works and has jb on it now
Click to expand...
Click to collapse
So we dont need 3 files ROM?
Hi all,
I think I have soft bricked my S4 i337m rogers Canadian variant.
I had rooted / unlocked the bootloader with motochopper successfully.
- I am using CWM
First thing I tried to do was backup the phone onto the external SD which would not work so I just went onto the next step.
I tried flashing a ROM onto the phone after doing phone restore and clearing cache. All installed correctly (apparently) and now when I boot up the phone the Samsung logo will appear for about 5 seconds then the phone will go black and try to boot up again.
The good:
- i have access the recovery mode still
The bad:
- no recovery made for the phone
- seems to be boot looping
As a side not I have tried installing a couple other ROMs which all result in the same issue.
Is there anything that can possibly be done?
I would happily put the stock ROM back on the phone.
All help would be greatly appreciated!
Rob.
9 times out of 10 a factory reset will get you out of a boot loop. Do that in recovery and reboot.
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Hi thanks for the reply. I have tried the factory reset and still does not fix the issue
Robby29 said:
Hi thanks for the reply. I have tried the factory reset and still does not fix the issue
Click to expand...
Click to collapse
If you are flashing a custom ROM that is not specifically for your phone, say a i9505 rom, you need to flash a Canadian kernel right after or you will bootloop. You also cannot flash any loki based roms either. As for the CWM backups, are you trying to back up to your external SD? If so, ensure the card is formatted fat32. To help get through your softbrick, just get into download mode and flash with odin
kiru said:
If you are flashing a custom ROM that is not specifically for your phone, say a i9505 rom, you need to flash a Canadian kernel right after or you will bootloop. You also cannot flash any loki based roms either. As for the CWM backups, are you trying to back up to your external SD? If so, ensure the card is formatted fat32. To help get through your softbrick, just get into download mode and flash with odin
Click to expand...
Click to collapse
Okay great I will try these. Does the kernel have to be specific to the ROM?
Robby29 said:
Okay great I will try these. Does the kernel have to be specific to the ROM?
Click to expand...
Click to collapse
The kernel is specific to your device. so you would use the i337M kernel.
So the procedure would be flash the rom of your choice, then before you boot flash YOUR i337M kernel, it will boot.
Good luck.
And make sure you do not flash a rom for the i9500 as you will hard brick
Also,
Make sure you choose the right i337m kernel. ie. a TouchWiz kernel for TW Roms and an AOSP kernel for CM10.1/AOSP Roms.
You should be able to:
remove your sdcard,
format it to fat32,
download the correct rom and kernel for you i337m to your freshly formatted sdcard,
put the card back into your phone,
boot into recovery,
install ROM zip from ext-sdcard,
install Kernel zip from ext-sdcard,
reboot.
phew....sounds like a lot of steps but not really I guess.
we good up in here....
Soft Brick S4
TheAxman said:
we good up in here....
Click to expand...
Click to collapse
Hello,
Greetings to you, I am sorry you have come to this point. I myself have bricked my phone just yesterday from flashing a bad ROM and not backing up my ROM properly. But I hope I can help you with some tips that i did to recover my phone fully. I apply some links to help you out but I recommend some patience lots of HW. ( Kies didn't work for me bugger =p.)
Unbrick S4 [Guide] -- http://forum.xda-developers.com/showthread.php?t=2265477&page=40
there is a user by the name of samersh72. you can request for a link to download your correct firmware it's best to get back to stock, ( don't forget to thank the user . )
this is someones video on youtube: http://www.youtube.com/watch?v=3a3qghhpDxg ( this helped me out as well)
I have these files/programs readied when I reverted back to stock
odin 1.3 ( i have odin 3.0 and didn't work for me reverting stock as it couldnt detect my tar.md5 file, but for some reason it worked for odin 1.3)
have your correct firmware ( I downloaded mine from http://www.sammobile.com, but for some reason I can't find yours, there is one on this site for sure just have the patience to look) make sure its for your correct carrier too.
im pretty sure you know how to do the DL mode, but just incase ill assume that you may or may not know, ill type this in anyway:
Get your S4 Download mode, [pressing up+power+home], (sometimes if i feel its not kicking in, just quick release then do it again)
open your odin 1.3, plug your phone in, tick auto-reboot, and F. reset time. PDA ticked, then find your correct firmware. hit start, then i hope from this something good will come out.
Best of wishes in your journey here in xda.
Cheers!
car154 said:
Hello,
Greetings to you, I am sorry you have come to this point. I myself have bricked my phone just yesterday from flashing a bad ROM and not backing up my ROM properly. But I hope I can help you with some tips that i did to recover my phone fully. I apply some links to help you out but I recommend some patience lots of HW. ( Kies didn't work for me bugger =p.)
Unbrick S4 [Guide] -- http://forum.xda-developers.com/showthread.php?t=2265477&page=40
there is a user by the name of samersh72. you can request for a link to download your correct firmware it's best to get back to stock, ( don't forget to thank the user . )
this is someones video on youtube: http://www.youtube.com/watch?v=3a3qghhpDxg ( this helped me out as well)
I have these files/programs readied when I reverted back to stock
odin 1.3 ( i have odin 3.0 and didn't work for me reverting stock as it couldnt detect my tar.md5 file, but for some reason it worked for odin 1.3)
have your correct firmware ( I downloaded mine from http://www.sammobile.com, but for some reason I can't find yours, there is one on this site for sure just have the patience to look) make sure its for your correct carrier too.
im pretty sure you know how to do the DL mode, but just incase ill assume that you may or may not know, ill type this in anyway:
Get your S4 Download mode, [pressing up+power+home], (sometimes if i feel its not kicking in, just quick release then do it again)
open your odin 1.3, plug your phone in, tick auto-reboot, and F. reset time. PDA ticked, then find your correct firmware. hit start, then i hope from this something good will come out.
Best of wishes in your journey here in xda.
Cheers!
Click to expand...
Click to collapse
Thanks for posting this. I hope many people read it. Anyone who flashes needs to know how to return to stock before they start flashing roms. You will need it someday!
Sent from my SAMSUNG-SGH-I727 using xda app-developers app
Hi, everyone I'm at a lost my S4 has been down for over a month now.
I've tried all the steps in the s4 bricked forums with no luck. I can't do the Kies recovery because it asks for a recovery code I don't have. (I bought the phone 2nd hand)
At this point I'm not even sure which stock rom I need to set the phone back to stock. I believe its a I337MVLUAMG1. I'm trying to run the phone on Aio.
When flashing from odin I usually get a failure. Seems like the Canadian S4 is prone to soft bricking searching the forums.
Currently I have Philz Advanced recovery installed. I'm stuck at Samsung Galaxy S4 logo
with
Kernel is not seandroid enforcing
Set Warranty bit: kernel
Any help of suggestions are gratefully appreciated.
Hey dude. No expert here, but it sounds like u have the new bootloader i.e. Knox. If ur going to do an odin flash to restore it, it's going to have to be at least MK6 firmware (I'm guessing this is the firmware u were on as NC1 just dropped and u said u'd been bricked for a month). Knox won't let u downgrade so if u've been flashing a 4.2 firmware then that's prolly why ur stuck at the boot screen. Good luck chief.
Oh, also, if u can boot into recovery, doing a factory reset and wiping /system couldn't hurt.
blankingblank said:
Hey dude. No expert here, but it sounds like u have the new bootloader i.e. Knox. If ur going to do an odin flash to restore it, it's going to have to be at least MK6 firmware (I'm guessing this is the firmware u were on as NC1 just dropped and u said u'd been bricked for a month). Knox won't let u downgrade so if u've been flashing a 4.2 firmware then that's prolly why ur stuck at the boot screen. Good luck chief.
Oh, also, if u can boot into recovery, doing a factory reset and wiping /system couldn't hurt.
Click to expand...
Click to collapse
Alright thank you thats a step in the right direction. I downloaded: I337MVLUFNC1_880525_REV06_user_low_ship_MULTI and tried flashing it. I'm getting odin failures. I can successful flash a recovery or modem. But flashing an entire ROM from odin fails every time. I'm not sure what stock ROMs will work with my phone. Its a Canadian i337m last time I was able to boot I was on MG1 i believe. I don't know if it matters. But I bricked my phone trying to undo the tmobile AWS work around (I swtiched to Aio).
crayak said:
Alright thank you thats a step in the right direction. I downloaded: I337MVLUFNC1_880525_REV06_user_low_ship_MULTI and tried flashing it. I'm getting odin failures. I can successful flash a recovery or modem. But flashing an entire ROM from odin fails every time. I'm not sure what stock ROMs will work with my phone. Its a Canadian i337m last time I was able to boot I was on MG1 i believe. I don't know if it matters. But I bricked my phone trying to undo the tmobile AWS work around (I swtiched to Aio).
Click to expand...
Click to collapse
U said u had the Knox msg come up when booting right? That means ur bootloader is 4.3 or higher regardless of what baseband ur on (modem). U can find a carrier specific version of the latest firmware at samsung-updates. Extract the tar.md5 and flash under AP in Odin 3.09 after unticking auto reboot and force reboot. If that fails u can try formatting all ur device partitions in recovery. Doubt that last part would help the odin flash stick but it's worth a shot. I use philz and u can format everything from /boot to /firmware_mdm. Like I said, dunno if that'll help but u could try it. Also, using kies on ur PC, u should make sure u have the latest drivers installed. Hope some of that helps
blankingblank said:
U said u had the Knox msg come up when booting right? That means ur bootloader is 4.3 or higher regardless of what baseband ur on (modem). U can find a carrier specific version of the latest firmware at samsung-updates. Extract the tar.md5 and flash under AP in Odin 3.09 after unticking auto reboot and force reboot. If that fails u can try formatting all ur device partitions in recovery. Doubt that last part would help the odin flash stick but it's worth a shot. I use philz and u can format everything from /boot to /firmware_mdm. Like I said, dunno if that'll help but u could try it. Also, using kies on ur PC, u should make sure u have the latest drivers installed. Hope some of that helps
Click to expand...
Click to collapse
Holly Vag thank you! I can now fully boot the phone. I installed Philz recovery and installed Vision X G4. WiFi is not working, and I haven't put my sim card in to see if it'll work with At&t/Aio yet.
Okay next step this is a Canadian Rogers i337m I think. Not sure how to confirm it. But assuming it is. What do I need to do to get wifi running. I see forums saying to install certain kernel and modems for the Canadian version. I'm not sure how to proceed considering I'm trying to use the phone on Aio/At&t, and suggestions?
Thank you, thank you. This is the farthest I've gotten I've been using a SGH-I437Z=Crapola.
crayak said:
Holly Vag thank you! I can now fully boot the phone. I installed Philz recovery and installed Vision X G4. WiFi is not working, and I haven't put my sim card in to see if it'll work with At&t/Aio yet.
Okay next step this is a Canadian Rogers i337m I think. Not sure how to confirm it. But assuming it is. What do I need to do to get wifi running. I see forums saying to install certain kernel and modems for the Canadian version. I'm not sure how to proceed considering I'm trying to use the phone on Aio/At&t, and suggestions?
Thank you, thank you. This is the farthest I've gotten I've been using a SGH-I437Z=Crapola.
Click to expand...
Click to collapse
Lol not sure anything I said helped. I think u must've wiped /firmware or /firmware_MDM right? I only meant to do that if u were going to flash a stock fw as it would replace those parts automatically. I think u lost ur non.hlos.bin file... Flashing a stock fw will bring it back. U can wipe everything again from philz if u want and try an Odin flash again using my instructions from the last post. Also, u want to flash a stock fw that uses the same base as the rom ur planning to flash, i.e. if u restore using a stock KitKat ROM (NC1), then ur gonna wanna make sure u flash a KitKat rom afterwards as the Knox BL won't let u downgrade.
As for which carrier fw to choose, the hardware is the same in all the Canadian variants, so any will work, although I think u were on a bell fw originally cuz of the MG1 suffix.
blankingblank said:
Lol not sure anything I said helped. I think u must've wiped /firmware or /firmware_MDM right? I only meant to do that if u were going to flash a stock fw as it would replace those parts automatically. I think u lost ur non.hlos.bin file... Flashing a stock fw will bring it back. U can wipe everything again from philz if u want and try an Odin flash again using my instructions from the last post. Also, u want to flash a stock fw that uses the same base as the rom ur planning to flash, i.e. if u restore using a stock KitKat ROM (NC1), then ur gonna wanna make sure u flash a KitKat rom afterwards as the Knox BL won't let u downgrade.
As for which carrier fw to choose, the hardware is the same in all the Canadian variants, so any will work, although I think u were on a bell fw originally cuz of the MG1 suffix.
Click to expand...
Click to collapse
You helped me quite a bit. Thank you. I reflashed Philz recovery with odin, then installed Vision X. I'm not sure what MDM or non.hlos.bin fiels are for. I don't want to use Odin with this phone. Searching the forums seems like this phone and odin don't get along when flashing a full ROM. I'd prefer to do all flashing using recovery. Now I just need to find the right stock zip.
crayak said:
You helped me quite a bit. Thank you. I reflashed Philz recovery with odin, then installed Vision X. I'm not sure what MDM or non.hlos.bin fiels are for. I don't want to use Odin with this phone. Searching the forums seems like this phone and odin don't get along when flashing a full ROM. I'd prefer to do all flashing using recovery. Now I just need to find the right stock zip.
Click to expand...
Click to collapse
No problem. Ya I guess the recovery zips could work just as well as the Odin tar.md5's would. I've just never used a recovery to flash a stock rom before.
Fwiw I have the same phone as u and have used Odin plenty, with positive results, although I've heard that peoples experiences with it vary a great deal. Having the right USB drivers installed on ur PC is key tho if u do use it.
Rom or Firmware?
crayak said:
Hi, everyone I'm at a lost my S4 has been down for over a month now.
I've tried all the steps in the s4 bricked forums with no luck. I can't do the Kies recovery because it asks for a recovery code I don't have. (I bought the phone 2nd hand)
At this point I'm not even sure which stock rom I need to set the phone back to stock. I believe its a I337MVLUAMG1. I'm trying to run the phone on Aio.
When flashing from odin I usually get a failure. Seems like the Canadian S4 is prone to soft bricking searching the forums.
Currently I have Philz Advanced recovery installed. I'm stuck at Samsung Galaxy S4 logo
with
Kernel is not seandroid enforcing
Set Warranty bit: kernel
Any help of suggestions are gratefully appreciated.
Click to expand...
Click to collapse
that have tried to install rom or firmware?
Pika71 said:
that have tried to install rom or firmware?
Click to expand...
Click to collapse
I have it booting into Maple Leaf now. Still trying to figure out if my performance issues are kernel, modem, or maybe its just KitKat?
My next phone is going to be a developer edition.
oh...
crayak said:
I have it booting into Maple Leaf now. Still trying to figure out if my performance issues are kernel, modem, or maybe its just KitKat?
My next phone is going to be a developer edition.
Click to expand...
Click to collapse
is the kit kat is very little battery
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.
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.