Related
I wanna know if you can help me, ...
I was on sprint gtab stock rom DJ30 which updated to EA24 and EB28. Data service worked very well. Then I flashed voodoo CWM in order to install Honeycomb rom. Then install the rom via CWM. The installation was indeed finished, but it stucked in samsung logo boot. I turned off device and boot in cwm mode. Sure, it was HC rom's CWM. But it couldnt mount system, Seems the convertion to ext4 didnt work. Worse thing it couldnt mount sdcard either. So I couldnt reinstall the rom. I also couldnt reboot, so i had to long press the power button.
Stop trying installing HC rom on my device, i decided to revert back to stock rom (DJ30>EA24). But it was weird, i cant revert to stock rom with modem.bin inside the package. It always stuck in modem.bin when flashed with odin. But, when i use the package with no modem, it can flashed succesfully. I had flashed that stock rom (with modem.bin) million times without fail, but now always fail.
Yeah, my gtab is running but without modem.bin so no signal and i cant use data services. Like wifi only tab.
Many ways i've tried:
- I've tried flashed DJ30 with no modem first. Okay, it is successful. But when flash with EA24 (with modem) it stuck on modem.bin.
- I've tried flashed DJ30 with modem.bin. And it also stucked on modem.bin. Trying flashed EA24 without modem.bin, it is succesful.
- Try using heimdall. Progress 100% but it wont reboot. But when i retry n uncheck modem. Flashing work flawlesly.
- Try using odin modem only flash. Progress bar is full but it wont reboot.
- Try flashing via CWM, but still no luck.
Weird, huh. Seems my gtab cannot use modem.bin anymore.
Any clue? Thanks before ...
I'd appreciate if you can help me flashing modem.bin to my device. Or it end up with wifi only tab.
EDIT: even OTA update, stuck on "verifying modem ... updating modem ..."
I would like to bump this as I am having the same issues also. I am flashing my Sprint Galaxy Tab to EA24, and it is held up at modem.bin.
I posted a question on this, and am hoping that someone helps us.
Thanks in advance,
Claud
try re-partition and flash pit by using odin,i suffered the same issue with my vzw tab
depending on which file you're using to restore. You need to use the .tar.md5 file from the EA24 flasher and rename it to just .tar, then flash with Odin. I've flashed this several times and it gets past modem.bin just fine. If you are using the 2 files 1 with modem (Epic 4g modem) and 1 without modem you're not using the right files. I ran into the same issue with the with/without modem files. Here's a link to the EA24 flasher and the .tar.md5 file you need to go back to stock.
http://www.multiupload.com/LXQKGX5RHL
Bumping this to avoid making a new thread.
I've done many reverts back to stock from different ROMs, but this past time coming from BTL or HC (Sprint Tab btw) I'm also getting hung up on modem.bin. Never had a problem here before, so not sure what's going on.
I didn't use a pit and only had reboot checked and it worked fine.
I've never included pit. I've just always put SPH-P100.EA24.SECURE.REV07-FULL_CL871413.tar in the PDA slot and let it go through. And tried checking re-partition, but it does not go through that way.
Maniken50 said:
I've never included pit. I've just always put SPH-P100.EA24.SECURE.REV07-FULL_CL871413.tar in the PDA slot and let it go through. And tried checking re-partition, but it does not go through that way.
Click to expand...
Click to collapse
Pretty sure if you try to re-partition, you have to have the correct pit file for it to know the right places to recreate the partition table. If you're just flashing back to stock, there's no need for the pit file.
pvtjoker42 said:
Pretty sure if you try to re-partition, you have to have the correct pit file for it to know the right places to recreate the partition table. If you're just flashing back to stock, there's no need for the pit file.
Click to expand...
Click to collapse
That's what I thought and never had a need for it. Guess I do now. Think it would even work?
Maniken50 said:
That's what I thought and never had a need for it. Guess I do now. Think it would even work?
Click to expand...
Click to collapse
I've never had to repartition a device, but i've read about it working for people to bring them back from boot looping etc. If somehow the partition table gets corrupted etc. If you're already soft bricked, there's no harm in trying.
Having the same issue, trying to go from Rooted GB to BTL then back to GB or EA24
Hi,
I am having the same issues, does anyone have the .PIT file available by any chance, all of the packcages that I have downloaded for the sprint tab seem to not have any pit included...
ezitec said:
Hi,
I am having the same issues, does anyone have the .PIT file available by any chance, all of the packcages that I have downloaded for the sprint tab seem to not have any pit included...
Click to expand...
Click to collapse
http://www.mediafire.com/?jb40cs460rf8aq7
Try that one.
I have the same problem with a Verizon Galaxy Tab. The archive modem.bin lock in 100% via Heimdall. Someone conseguiui solve this problem?
mbanton said:
I have the same problem with a Verizon Galaxy Tab. The archive modem.bin lock in 100% via Heimdall. Someone conseguiui solve this problem?
Click to expand...
Click to collapse
You need to look at one of the stock VZW threads and find the files you need there, as the sprint modem will make things worse for you. Not sure if the pit files are the same or not between the sprint and VZW tabs..
pvtjoker42 said:
You need to look at one of the stock VZW threads and find the files you need there, as the sprint modem will make things worse for you. Not sure if the pit files are the same or not between the sprint and VZW tabs..
Click to expand...
Click to collapse
I have the correct files for the tab for Verizon. I have the original files Following: Sbl.bin boot.bin cache.rfs dbdata.rfs efs.rfs factoryfs.rfs ldb.db modem.bin param.lfs param.rfs pit.pit zImage
But my problem is how to record using that pit. What other files should I use a recording that will restore the partition table?
I fear that a problem occurs with even higher tab.
I am having this issue as well, and I'm also coming from HC and on Sprint. I have no trouble flashing any kernel/rom of my choosing EXCEPT for the modem.
At this point, I'm just trying to reflash it back to stock. I've got the Sprint EA24 files, including the pit (tried with and without) but it refuses to flash the modem. If I omit the modem, it flashes perfectly fine and I'm left with a bone stock tab with no modem.
Is there anyone here who went to HC and then managed to go back? As stated by others, I've gone back to stock before without issue. The HC build seems to be what caused this problem
I ran spacemoose's HC port for a day or 2 and then went back to stock until the official GB came out. I've had no issues flashing the whole EA24, or any other updates.. with and without the modem..
Hmmmm. Maybe different hardware revisions? You have any suggestions? I'm completely out of ideas and it's of little use to me without 3G.
I just did a flash back to complete stock (including modem) 2 days ago, and it didn't hesitate once while flashing everything with Heimdall. Only thing I can say is keep trying.
At this point, I've attempted to flash it no less than a dozen times and still can't get the modem to flash. I'm completely baffled as to why it won't accept it.
Tried everything I could with Odin and phone still stuck in a start loop.
I was downgrading from checkROM to official firmware ZSLA2 with CWM (I wanted to keep ROOT, so I selected "Keep CF-Root kernel") due to stability issues, after restarting the phone got into the start loop.
I flashed with Odin official ZSLA2 with the same result (looped start). I flashed XXKKA (again looped start). During the flashing process, Odin says the flashing was successful. By the way, both ROMS are tar.md5 files.
I tried to remove the battery for over 30 minutes and charge it for 2 hours, tried re-partition in Odin (it's my understanding that with a stock rom, it creates a clean installation), but Odin fails to start the process.
What else can I do?
I am sorry if this has previously asked, but I've been searching for over 2 hours and nothing similar came. Somebody mentioned to use a PIT file in addition, but the other person who got his phone soft bricked didn't solve the problem either. As downloading a ROM is time consuming and I've got many problems with upload sites in china (cannot access to most of them), I would thank any help in regards this issue.
Sounds like your kernel isn't talking properly to your ROM.
A fresh start is your best bet. Flash a stock rom and kernel from Odin and reroot it with CF-Root.
What files are you putting into Odin? There should be a total of 4.
I'd also avoid the use of a .pit file. I haven't even seen the mention of one in all my time on the Note forum. I really don't think Samsung uses them the way they used to. (I used to have to flash one all the time when testing roms on the original galaxy tab.)
I am using official ROM N7000ZSLA2_N7000ZSLA2_N7000XLA4_HOME.tar.md5 into PDA and also tried ROM N7000XXKKA_N7000XEUKK3_N7000XXKK5_HOME.tar.md5, which I used successfully in the past to make root into my phone.
Does it really make a difference to flash 4 separate files instead of a full pack? Where can I find an official ROM with pda radio and kernel separated? Just untar the ROM?
btyork said:
I'd also avoid the use of a .pit file. I haven't even seen the mention of one in all my time on the Note forum. I really don't think Samsung uses them the way they used to. (I used to have to flash one all the time when testing roms on the original galaxy tab.)
Click to expand...
Click to collapse
Oh, they do come into the Note; I flashed the Beta ICS, and one of the things they mention is to use the PIT file for the 16GB version, instead of the 32GB that comes with the leaked ROM. Unfortunately I deleted that ROM, and donwloading it is painfully slow and also wouldn't necessarily solve my problem as I couldn't even make a phone call.
True - the .pit file can change the size of the partition data... But that's not your problem. If the .pit file was the problem - you'd boot, but have 0 storage space (or something else wonky pertaining to your disk size.)
Open the tar up and make sure it has all the files in it. Should be 5.
I've attached a screenshot of the 5 file names. Make sure they are all in the .tar you are flashing.
Even i had similar problem after flashing Stock ROM using Odin (PC). Only thing i did is just rebooted in recovery and Wipe/factory Reset and Wipe cache. everything went fine.
btyork said:
True - the .pit file can change the size of the partition data... But that's not your problem. If the .pit file was the problem - you'd boot, but have 0 storage space (or something else wonky pertaining to your disk size.)
Open the tar up and make sure it has all the files in it. Should be 5.
I've attached a screenshot of the 5 file names. Make sure they are all in the .tar you are flashing.
Click to expand...
Click to collapse
This are the files I am flashing:
Sorry, I am new user and still cannot post screen captures. I do have more than the 5 files.
In XXKKA I have:
Boot
Cache
Factoryfs
Hidden
Modem
param.lfs
Sbl
zImage
In ZSLA2:
Cache
Factoryfs
Hidden
Modem
zImage
btyork said:
Even i had similar problem after flashing Stock ROM using Odin (PC). Only thing i did is just rebooted in recovery and Wipe/factory Reset and Wipe cache. everything went fine.
Click to expand...
Click to collapse
I can only enter into Download mode, not recovery mode.
Odin is full wipe, right? What the hell am I doing wrong?
N7000xxla1_n7000oxala1_oxa
http://hotfile.com/dl/141060546/b0c7420/N7000XXLA1_N7000OXALA1_OXA.rar.html
download this firmware, it's gonna take awhile but worth a try..
try flashing this rom using PC odin.
pit: Q1_20110914_16GB.pit
pda: CODE_N7000XXLA1_CL868264_REV02_user_low_ship.tar.md5
phone: MODEM_N7000XXLA1_REV_05_CL1093393.tar.md5
csc: GT-N7000-MULTI-CSC-OXALA1.tar.md5
check re-partition, auto reboot, F. reset time.
let me know if it works!
Han
choihan06 said:
download this firmware, it's gonna take awhile but worth a try..
try flashing this rom using PC odin.
pit: Q1_20110914_16GB.pit
pda: CODE_N7000XXLA1_CL868264_REV02_user_low_ship.tar.md5
phone: MODEM_N7000XXLA1_REV_05_CL1093393.tar.md5
csc: GT-N7000-MULTI-CSC-OXALA1.tar.md5
check re-partition, auto reboot, F. reset time.
let me know if it works!
Han
Click to expand...
Click to collapse
Well, I finally managed to get my phone back. I was getting a lot of corrupted ROMS. I couldn't download your ROM as well; I managed to install the Beta ICS 4.0.3 which comes with a PIT for repartition, as I think the problem was that my booting partition was screwed.
Problem now is: that rom screws the phone and the keyboard, but at least I have my phone back.
Thank you
mrfan said:
Well, I finally managed to get my phone back. I was getting a lot of corrupted ROMS. I couldn't download your ROM as well; I managed to install the Beta ICS 4.0.3 which comes with a PIT for repartition, as I think the problem was that my booting partition was screwed.
Problem now is: that rom screws the phone and the keyboard, but at least I have my phone back.
Thank you
Click to expand...
Click to collapse
I have just recently dowloaded and installed the rom without problem. What do you mean by corrupted rom?
Sent from my GT-N7000 using xda premium
I too bricked my phone but after reading this guide (ABD wouldn't recognise my device so I couldn't follow it) I understood the partitions had become messed up.
I read somewhere about the PIT files.
I ODINed the ABYSS Kernal and PIT (Q1_20110914_16GB-patched) for my 16gb n7000 ticked the repartition box. It booted into CWM recovery and I used the restore and bingo.
Fix The problem
I had the same problem, the device got into start loop. JUST DO A FULL WIPE..! and the device should start normally. I worked for me.... :good:
Sent from my GT-N7000 using xda premium[/QUOTE]
Hello XDA members and devs. I have stumbled upon an issue that seems to be close to un-fixable. I have the SM-N910T obviously. I am on DOK2, every rom Touch Wiz and Cyanogenmod flashed correctly a couple of months ago. Now the only things I can flash are DOK2 stock firmware via ODIN, and then I can successfully flash TWRP 2.8.7.0, the only ROM I can flash is Maximum Overdrive 4.0.1 +(all upper updates.) I got a hold of Max OD dev and he said it's because of the 3 mount lines he added to the top of his updater-script. So I added those lines to updater-scripts of other roms and none worked. Some other roms have many other mount points and important lines of code in the updater-script that should not be removed or edited. I want to go back to Cyanogenmod, and others either 12.1 nightlies, or the new CM Remix 13.0 which worked before all the others stopped working at the same time.
Yes I also tried this.
Quote:
Originally Posted by sudoBacon
I tried before. Doesnt work onlky DOK2 or maximum ods 4.0.1 + no other roms
After you flash D0K2 firmware - Use the stock Recovery and Factory Reset - That will get you out of the bootloop - Just remember that your internal storage will be wiped!
I also get the same issue after attempting to downgrade which always fails. Used to be able to downgrade and upgrade firmware's as well, now I cant. I got the dev of Max OD rom to pull a DOK2 pit file even flashing that does not fix my issue. I also posted on Reddit, so I will copy and paste this post.
Reddit Post.
I have a T-Mobile Note 4 was working fine for a long time flashed many ROM's multiple times over and over again never had a problem until I flashed DOK2 I assume. With ODIN. I did flash to stock from COD6 to DOK2 can't seem to downgrade back to COD6 with ODIN get error cant downgrade note 4 SW REV CHECK FAIL : [aboot]Fused2 > Binary 1 [1] eMMC write fail : ABOOT , that appears on Download mode. Then every time I install TWRP I try to install a ROM from OTG usb or ext sd and nothing flashes, rom files work used them before. I can only seem to install DOK2 and can't downgrade or flash other roms. I need help so I can flash other roms. Yes I tried flash stock DOK2 and boot stock recovery then clearing cache and factory reset, to downgrade to COD6 still failing and can't install other roms. every time i try to flash version lower then DOK2 using odin get this error ; SW REV CHECK FAIL : [aboot]Fused2 > Binary 1 [1] eMMC write fail : ABOOT
At one point I installed CWM trlltexx or something like that through TWRP, and did format and all of that. But after that went back to stock flashed TWRP 2.8.7.0 because couldn't flash roms with CWM because the roms thought I was on trltexx. Formatted all partitions with CWM. Anyways tried to get back to Cyanogenmod and or Tekxodus and other roms all fail. Minus Maximum Overdrives 4.0.1.
The first 3 lines that Overdrive mentioned that must make my roms flash able are.
HTML:
run_program("/sbin/busybox", "mount", "/system");
run_program("/sbin/busybox", "mount", "/cache");
run_program("/sbin/busybox", "mount", "/data");
Anyways please contact me on Google+ Hangouts or respond here if you know how to fix my issue also have Skype but PM me for that info. Add Bacon Seeds first and last name to Google + Hangouts that G+ Hangouts email is [email protected] . I am experienced in compiling roms extracting, de compiling as well. Life on my Note 4 without some Cyanogenmod had been technologically heartbreaking. I like flashing multiple roms and swapping back and forth. Now I cant even test others stuck on Max OD which is a good and awesome rom but sometimes get tired of Touch Wiz.
I would install the ROM you can, then dirty flash an aosp ROM, then try to flash the ROM you want.
therealjwkware said:
I would install the ROM you can, then dirty flash an aosp ROM, then try to flash the ROM you want.
Click to expand...
Click to collapse
I'll give this a shot but I seriously doubt this will work if other methods didn't.
sudoBacon said:
I'll give this a shot but I seriously doubt this will work if other methods didn't.
Click to expand...
Click to collapse
Use Kies to recover your phone. It should be able to fit any issues with partitions etc.
Odd how using the PIT file does not fix this issue. It's literally setting up your phone's partition table all over again and it isn't working. Also, on DOK2's bootloader, it is impossible to rollback bootloader. I tried going from DOK2 -> ANIH (Kitkat original) and it didn't work. You can still run older ROMs, just not the older bootloader. That's why you're getting the 'Binary 2 > Fused 1' message.
-
By the way, you should be using ODIN3.10.7. It is the latest version. Load up the full stock DOK2 firmware (I suggest downloading using SamFirm -- make sure to check Binary Nature for a full firmware), follow this guide:
http://forum.xda-developers.com/showthread.php?t=2610757
They used a PIT and Stock to fully wipe, with the exception in this case being that this is 5.1.1 and not 4.4.4
ShrekOpher said:
Use Kies to recover your phone. It should be able to fit any issues with partitions etc.
Click to expand...
Click to collapse
I tried that and now after doing factory reset in the stock firmware I can not even flash Maximum OD only DOK2 via odin.
sudoBacon said:
I tried that and now after doing factory reset in the stock firmware I can not even flash Maximum OD only DOK2 via odin.
Click to expand...
Click to collapse
do you have a working DOK2 stock firmware running on your phone. Once you upgrade to DOK2 you can only flash ROMs based on 5.1.1 or ROMs that include a kernel. If you want to flash a ROM based on 5.0.1 you will need to flash either the Emotion Kernel or the Beast mode kernel as well before you reboot the device.
If you have Stock TW firmware running and you have TWRP installed your phone should be fixed. As long as you use compatible ROMs with it.
ShrekOpher said:
do you have a working DOK2 stock firmware running on your phone. Once you upgrade to DOK2 you can only flash ROMs based on 5.1.1 or ROMs that include a kernel. If you want to flash a ROM based on 5.0.1 you will need to flash either the Emotion Kernel or the Beast mode kernel as well before you reboot the device.
If you have Stock TW firmware running and you have TWRP installed your phone should be fixed. As long as you use compatible ROMs with it.
Click to expand...
Click to collapse
Still didn't work.
Edit : Now i cant seem to install any rom nor Max OD. only DOK2 via odin. TWRP log says
E:Mount: Unable to find partition for path /sdcard
E:UnMount: Unable to find partition for path /sdcard
E:Mount: Unable to find partition for path /sdcard
sudoBacon said:
Still didn't work.
Edit : Now i cant seem to install any rom nor Max OD. only DOK2 via odin. TWRP log says
E:Mount: Unable to find partition for path /sdcard
E:UnMount: Unable to find partition for path /sdcard
E:Mount: Unable to find partition for path /sdcard
Click to expand...
Click to collapse
Looks like you corrupted your partitions. You might need to flash the pit file to fix it. I think there is a thread related to that somewhere.
Request thread closed, resolved!
Steps taken not in any order.
Find a legit us TRLTE pit file. Message me for the TRLTE pit file or I'll make a separate thread for it.
Flash DOK2 stock firmware + proper pit file and have re-partition checked, along with flash BL and EFS clear.
Format ext SD card.
Downloaded the roms onto the formatted SD card.
Flash the latest TWRP recovery
Wipe all not including system x3 times.
Go to Wipe and then Format, check system format system type Yes
Go to install select your ROM.
Then select your GApps and custom kernel whatever else you want.
You might have to do the stock flashing and wiping and formatting several times before this works along with the re-partitioning.
Note a legit TRLTETMO pit file can be found : http://www.sammobile.com/forum/showthread.php?t=29568
The legit pit file name for TRLTETMO should be labeled: TRLTE_USA_TMO.pit
sudoBacon said:
Request thread closed, resolved!
Steps taken not in any order.
Find a legit us TRLTE pit file. Message me for the TRLTE pit file or I'll make a separate thread for it.
Flash DOK2 stock firmware + proper pit file and have re-partition checked, along with flash BL and EFS clear.
Format ext SD card.
Downloaded the roms onto the formatted SD card.
Flash the latest TWRP recovery
Wipe all not including system x3 times.
Go to Wipe and then Format, check system format system type Yes
Go to install select your ROM.
Then select your GApps and custom kernel whatever else you want.
You might have to do the stock flashing and wiping and formatting several times before this works along with the re-partitioning.
Note a legit TRLTETMO pit file can be found : http://www.sammobile.com/forum/showthread.php?t=29568
The legit pit file name for TRLTETMO should be labeled: TRLTE_USA_TMO.pit
Click to expand...
Click to collapse
Congrats!
Hey bacon. I'm glad you figured it out. But in was wondering if you think me doing the pit file would work for my situation. Currently my phone is on a loop every time I flash dok2. And twrp will not flash any huge files. I can get kernels too flash but not roms. Any insight would be greatly appreciated. I can't even get the firmware too boot up. Thanks in advance
Jamonguyen said:
Hey bacon. I'm glad you figured it out. But in was wondering if you think me doing the pit file would work for my situation. Currently my phone is on a loop every time I flash dok2. And twrp will not flash any huge files. I can get kernels too flash but not roms. Any insight would be greatly appreciated. I can't even get the firmware too boot up. Thanks in advance
Click to expand...
Click to collapse
https://www.androidfilehost.com/?fid=24369303960684492
Here's a pit for the N910T, grabbed from the latest DOK2.
eduardog131 said:
https://www.androidfilehost.com/?fid=24369303960684492
Here's a pit for the N910T, grabbed from the latest DOK2.
Click to expand...
Click to collapse
I'm trying to get stock to boot without success. I would really appreciate any help.
Longshark said:
I'm trying to get stock to boot without success. I would really appreciate any help.
Click to expand...
Click to collapse
Have you flashed the full ODIN package? Try erasing NAND and Re-Partition (with .pit in ODIN package)
I will usually just go about it that way when I go to stock to start off fresh.
eduardog131 said:
Have you flashed the full ODIN package? Try erasing NAND and Re-Partition (with .pit in ODIN package)
I will usually just go about it that way when I go to stock to start off fresh.
Click to expand...
Click to collapse
So I'm flashing the full ODIN package. PDA for stock, PIT from the link you posted, Checked boxes are Auto Reboot. Re-Partition, F. Reset Time and NAND Erase All. This is with ODIN 3.07.
What do I do when it finishes?
---------- Post added at 10:45 PM ---------- Previous post was at 10:43 PM ----------
eduardog131 said:
Have you flashed the full ODIN package? Try erasing NAND and Re-Partition (with .pit in ODIN package)
I will usually just go about it that way when I go to stock to start off fresh.
Click to expand...
Click to collapse
It's done but boot looping with RECOVERY BOOTING... screen. Do I flash TWRP now? I have 2.8.7. Is that sufficient?
Thanks
Longshark said:
So I'm flashing the full ODIN package. PDA for stock, PIT from the link you posted, Checked boxes are Auto Reboot. Re-Partition, F. Reset Time and NAND Erase All. This is with ODIN 3.07.
What do I do when it finishes?
---------- Post added at 10:45 PM ---------- Previous post was at 10:43 PM ----------
It's done but boot looping with RECOVERY BOOTING... screen. Do I flash TWRP now? I have 2.8.7. Is that sufficient?
Thanks
Click to expand...
Click to collapse
It shouldn't be bootlooping, in fact it has to reboot into recovery right after ODIN flashes the stock package, it needs to erase + verify / flash CSC contents. It should pretty much boot up into stock. If you really want to flash TWRP (to flash a custom ROM), flash it. Right after you flash it, make sure you take the battery out and you reboot into recovery manually. Stock system prevents recovery from being overwritten.
eduardog131 said:
It shouldn't be bootlooping, in fact it has to reboot into recovery right after ODIN flashes the stock package, it needs to erase + verify / flash CSC contents. It should pretty much boot up into stock. If you really want to flash TWRP (to flash a custom ROM), flash it. Right after you flash it, make sure you take the battery out and you reboot into recovery manually. Stock system prevents recovery from being overwritten.
Click to expand...
Click to collapse
Sorry I'm fairly new to this. So it did boot into custom recovery. I just want the phone back to stock without TWRP or any bells or whistles.
Its on the stock recovery interface. Should I wipe data/factory reset? Or reboot system now?
Longshark said:
Sorry I'm fairly new to this. So it did boot into custom recovery. I just want the phone back to stock without TWRP or any bells or whistles.
Its on the stock recovery interface. Should I wipe data/factory reset? Or reboot system now?
Click to expand...
Click to collapse
Once it's done with verification of CSC, just reboot system. It should take a few minutes to set itself up, then will throw you into the setup wizard. Once you're there you're good to go.
eduardog131 said:
It shouldn't be bootlooping, in fact it has to reboot into recovery right after ODIN flashes the stock package, it needs to erase + verify / flash CSC contents. It should pretty much boot up into stock. If you really want to flash TWRP (to flash a custom ROM), flash it. Right after you flash it, make sure you take the battery out and you reboot into recovery manually. Stock system prevents recovery from being overwritten.
Click to expand...
Click to collapse
Also does it matter the dm-verity verification failed is showing at the bottom?
Ok so I have a note 4 that was not working properly as it would boot into Odin mode when I tried to turn it on. That being said, it sometimes would boot normally or not turn on at all. So my solution was to root it and install a custom rom (like cyanogen mod). So I got odin and the twrp file and the custom kernel and followed the steps necessary: flash twrp, flash the kernel, flash super su, etc. But the problem is that Odin says "no pit binary". So I google it and found out that I could repartition it using a stock ROM and the correct pit file. I did that and it failed as well. So I turn to keis and do the firmware and initialization thingy, that ends up failing too. So I go back to odin and try to flash stock firmware but it fails after " writing NAND " thingy or it fails saying "cannot open specified file" or "no pit file ". What can I do.[emoji27]
beelito19 said:
Ok so I have a note 4 that was not working properly as it would boot into Odin mode when I tried to turn it on. That being said, it sometimes would boot normally or not turn on at all. So my solution was to root it and install a custom rom (like cyanogen mod). So I got odin and the twrp file and the custom kernel and followed the steps necessary: flash twrp, flash the kernel, flash super su, etc. But the problem is that Odin says "no pit binary". So I google it and found out that I could repartition it using a stock ROM and the correct pit file. I did that and it failed as well. So I turn to keis and do the firmware and initialization thingy, that ends up failing too. So I go back to odin and try to flash stock firmware but it fails after " writing NAND " thingy or it fails saying "cannot open specified file" or "no pit file ". What can I do.[emoji27]
Click to expand...
Click to collapse
Hey bud. Are you trying to flash a pit file and firmware or just firmware. And is it a N910T and if so on what build of firmware..? Send a screenshot of download mode...and also try to rename the extracted firmware file from .md5 to .tar and try to flash
Its a N910T and its on 5.1.1, i read on another XDA thread that to repartition something you need stock firmware (which I have a 5.1.1 one) and the right pit file (I have the N910T one) and that in odin put the extracted firmware file and on pit put the pit file. I did that and it failed. And how would I rename the file ... Would I just rename it on the file explorer on windows?
noob4598 said:
Hey bud. Are you trying to flash a pit file and firmware or just firmware. And is it a N910T and if so on what build of firmware..? Send a screenshot of download mode...and also try to rename the extracted firmware file from .md5 to .tar and try to flash
Click to expand...
Click to collapse
First it was a pit file and firmware, but now I'm trying to unbrick it by flashing just firmware on odin since keis doesn't seem to help. And yes it is an N910T, dont know the exact build but it is 5.1.1 ( would flashing a different 5.1.1(for the n910t) build matter or not, since its still 5.1.1 ?)
Yea if your on dok2 you can't go back to anything under that. It will fail every time. What firmware build u got
noob4598 said:
Yea if your on dok2 you can't go back to anything under that. It will fail every time. What firmware build u got
Click to expand...
Click to collapse
I dont know... The latest one ( the update for stage fright was the last update I had installed on there. Since it's soft bricked ( the connect to kies message) I can't tell what the exact build was... I just know its a 5.1.1 build.)
Hi everyone,
So I have a I9305, the factory ROM is not booting, but I do have the Samsung flashtool working, and I also have TWRP installed.
I am trying to flash the factory ROM back to the phone before I install Lineage OS.
I have tried using Odin3 to flash this, but it keep asking for the pit file, when I allow Odin to find the pit file, it then reboots the phone, after this Odin no longer sees the phone until I restart the app, thus loosing the pit file. :-S (I am running this on Linux)
So my question is, how can I flash the factory ROM back to the phone?
Any help appreciated
I managed to find a pit file online, but still cant get Jodin to flash the ROM. What is the best way to flash this factory ROM, can it even be done?
If it cant, then what can I do to get this phone up and running again.
I have read through many articles online stating how this should be done for this phone, but the methods do not work.