Please help phone not starting - Galaxy S I9000 Q&A, Help & Troubleshooting

PLEASE HELP....GT-I9000 Not Working..!
What i did?
I was using GB 2.3.6 XW_JW7
I rooted it with CF-Root-XX_OXA_JW4-v4.4-CWM3RFS via ODIN
I wanted to flash pa_galaxysmtd-1.9.2a-27JUL2012-202615 (PARANOID ANROID)
I went into recovery mode,
factory reset
wipe cache
wipe dalvik under advanced
i flashed pa_galaxysmtd-1.9.2a-27JUL2012-202615.zip but it restarted not completed and it stuck
I again went in recovery again tried to flash, that time could not found files,
I went to downoad mode
installed again GB 2.3.6 XW_JW7
It gave me pass
But when phone rebooted automatically it gave erros
E:copy_dbdata_media: Can't mount /dbdata your storage not prepared yet. please use UI menu for format and reboot actions..
Meida files copy failed
-- Deleting files...
E:failed to mount /dbdata (File Exists)
E:copy_dbdata_media: Can't mount /dbdata your storage not prepared yet. please use UI menu for format and reboot actions.
-- Updating filesystem..
E:failed to mount /dbdata (File Exists)
E:discard_filesystem_for_rfs:Can't mount /dbdata
-- Wiping cache...
Formating cache...
Cache wipe failed.
-- Appling Multi-CSC...
Installing Multi-CSC
Can't access to '/system/csc/ITV/system/'.
Successfully applied multi-CSC.
I tried flashing again stock rom, but not helped, it is only one PDA file.
Please Please let me know solution, So that i can atlast start phone with STock GB.

Looks like the stock ROM you tried to flash is missing dbdata.rfs. Get a stock ROM from here, they should contain all files (incl. dbdata.rfs). Alternatively you could search for a flashable dbdata.rfs to flash with Odin.

stbenz said:
Looks like the stock ROM you tried to flash is missing dbdata.rfs. Get a stock ROM from here, they should contain all files (incl. dbdata.rfs). Alternatively you could search for a flashable dbdata.rfs to flash with Odin.
Click to expand...
Click to collapse
http://snappybytes.blogspot.in/2012/04/how-to-fix-cant-mount-dbdata-error-sgs.html
Should i use this trick? and for flashing stock rom again, what i need? repartition tick?

stbenz said:
Looks like the stock ROM you tried to flash is missing dbdata.rfs. Get a stock ROM from here, they should contain all files (incl. dbdata.rfs). Alternatively you could search for a flashable dbdata.rfs to flash with Odin.
Click to expand...
Click to collapse
Thanks it worked. But I did not understand problem. Why this happened. Did I miss any step or used wrong files?
Sent from my GT-N7000 using xda app-developers app

jeet.chaudhari said:
Thanks it worked. But I did not understand problem. Why this happened. Did I miss any step or used wrong files?
Sent from my GT-N7000 using xda app-developers app
Click to expand...
Click to collapse
I don't know the exact settings you used, but I assume the following:
ICS ROMs have different partition layouts than GB ROMs. Therefore the initial flash of the ICS failed, as it probably needs a reboot after changing the partition layout. If you had flashed it again, it should have worked.
But what I'm pretty shure about is, that flashing ICS the first time, changed the partition layout. As a result you probably had to check "repartition" when flashing stock GB with Odin. But when you check "repartition" in Odin, the ROM you are flashing needs all ROM parts (including dbdata.rfs), because all partitions of the internal flash of the phone are cleared after repartition. If a part is missing, it can't mount the related partition, because the partition is still unintialized.
If you flash a GB ROM with missing parts and "repartition" unchecked over an already working GB ROM, Odin will only flash the parts of the ROM that are present and leave the rest untouched. Thats how flashing only a kernel works, it just flashes the kernel to the kernel partition and leaves the rest of the ROM untouched. Also thats how the fix you posted works. The dbdata.rfs.tar only contains dbdata.rfs, flashing it with "repartition" unchecked only overwrites the dbdata partition and leaving the rest (which you flashed earlier with the PDA file) untouched.

stbenz said:
I don't know the exact settings you used, but I assume the following:
ICS ROMs have different partition layouts than GB ROMs. Therefore the initial flash of the ICS failed, as it probably needs a reboot after changing the partition layout. If you had flashed it again, it should have worked.
But what I'm pretty shure about is, that flashing ICS the first time, changed the partition layout. As a result you probably had to check "repartition" when flashing stock GB with Odin. But when you check "repartition" in Odin, the ROM you are flashing needs all ROM parts (including dbdata.rfs), because all partitions of the internal flash of the phone are cleared after repartition. If a part is missing, it can't mount the related partition, because the partition is still unintialized.
If you flash a GB ROM with missing parts and "repartition" unchecked over an already working GB ROM, Odin will only flash the parts of the ROM that are present and leave the rest untouched. Thats how flashing only a kernel works, it just flashes the kernel to the kernel partition and leaves the rest of the ROM untouched. Also thats how the fix you posted works. The dbdata.rfs.tar only contains dbdata.rfs, flashing it with "repartition" unchecked only overwrites the dbdata partition and leaving the rest (which you flashed earlier with the PDA file) untouched.
Click to expand...
Click to collapse
Yes. I assume its all right but I didn't tried ICS. I was jumping from stock GB to JB ROM. So what you will now suggest me to flash JB PA ROM on currently working stock GB ROM?
Sent from my GT-N7000 using xda app-developers app

The things I wrote about ICS also apply to JB.
I don't know, how to install JB PA, but the install instructions should be in the thread where you got the ROM from. If flashing fails, you should ask there, as it may be a known problem and the people there would probably be more of a help than me, as I never flashed JB PA.

2.3.6GB fw.root after installation, the kernel semaphore cwm, then save the sd.kartu,, clearing the ultimate script for kernel instal script, factory data reset wipe, wipe Dalvik cache and rom and installed the ICS sd.karty.
it is better to have clean sd.kartu before the flash rom ICS or JB.

stbenz said:
Looks like the stock ROM you tried to flash is missing dbdata.rfs. Get a stock ROM from here, they should contain all files (incl. dbdata.rfs). Alternatively you could search for a flashable dbdata.rfs to flash with Odin.
Click to expand...
Click to collapse
Thanks, this worked for me. I downloaded the latest firmware and that set my phone straight.

Galaxy TAB GT-P1000L - Solved
I was facing the same issue with my Galaxy TAB GT-P1000L, where it was on loop in the Samsung Logo screen. Please note that after flashing the dbdata, you must flash the Stock ROM again

Related

Damn, My phone wont install stock rom!

Hi,
I was on darkys rom, I installed honeycomb theme on it.. which had some issues and my phone was in constant reboot loop after that. I couldnt go to recovery or anything. only the download mode was working.
So I flashed DDJP6 it gave me following error its giving me same error even if I flash using DDJPY or any other stock rom.
after I flash my rom this is what i get on 1st boot when it goes to recovery, please help.
============
Update media. please wait E:Cant mount /dev/block/st110
(Invalid argument)
E:copy_dbdata_media:cant mount db data:
your storage is not prepaired yet. please use UI menu for format and reboot actions.
copy default media content failed.
Flash a 2.1 version with repartition on! (maybe 2 times if first time don't work)
Then flash a 2.2 or 2.2.1 version without repartition on...
PS: Everytime before flashing with odin put off the battery once first!
Good luck!
Sent from my GT-I9000 using XDA App
Did u have lagfix on with darkys rom when u flashed with stock rom?
Sent from my GT-I9000 using XDA App
Now do a wipe and if problem still not fixd flash a full rom with 3 file and pit
Hannibal226 said:
Flash a 2.1 version with repartition on! (maybe 2 times if first time don't work)
Then flash a 2.2 or 2.2.1 version without repartition on...
PS: Everytime before flashing with odin put off the battery once first!
Good luck!
Sent from my GT-I9000 using XDA App
Click to expand...
Click to collapse
I think the point is not 2.2/ 2.2.1 .. The OP needs an odin flash with separated csc, modem and pda files plus a corresponding pit file plus repartition ticked.
I believe that this error happens after a odin flash with repartition ticked AND there s only 1 pda file (without the modem and csc things).
(is there a way to post in the android development without having to post > 10times @ other subforums ...? -_-)
m2677086 said:
I think the point is not 2.2/ 2.2.1 .. The OP needs an odin flash with separated csc, modem and pda files plus a corresponding pit file plus repartition ticked.
I believe that this error happens after a odin flash with repartition ticked AND there s only 1 pda file (without the modem and csc things).
(is there a way to post in the android development without having to post > 10times @ other subforums ...? -_-)
Click to expand...
Click to collapse
I don't understand your prob because the 2.1 versions i think "all" are 3 sepereated files, so that what I said!
Sent from my GT-I9000 using XDA App
I don't understand your prob because the 2.1 versions i think "all" are 3 sepereated files, so that what I said
Not true .
jje

[Q] Superuser not working anymore. What should I do?

Hi, I have SGS 1 with stock ROM JPJV6 (arabic)
I flashed the following Chainfire kernel:
CF-Root-XW_NEE_JVH-v3.2-CWM3RFS.tar
Everything was working well, super user, tweaks and the ext4 tool. However, when I tried to convert to ext4 I got the following error message when converting /system:
Not enough space.. Rolling back!
Restoring files...
Rolling back failed! | PANIC!
The other partitions where converted with no problem.
However, when the phone rebooted, super user is not working anymore, also tweaks and ext4 tools are not recognizing the kernel.
I tried flashing the same kernel again but the problem remained.
I tried flashing CF-Root-XX_OXA_JVO-v3.2-CWM3RFS and also the problem remained.
My question is:
1) How can I know the current partition (RFS or exts)?
2) Is it safe to flash the stock JPJV6 ROM to fix all that stuff and return to original firmware without root or ext4?
3) If it is safe, should I select "repartition" in ODIN?
Thanks in advance
necromancerfinal said:
Hi, I have SGS 1 with stock ROM JPJV6 (arabic)
I flashed the following Chainfire kernel:
CF-Root-XW_NEE_JVH-v3.2-CWM3RFS.tar
Everything was working well, super user, tweaks and the ext4 tool. However, when I tried to convert to ext4 I got the following error message when converting /system:
Not enough space.. Rolling back!
Restoring files...
Rolling back failed! | PANIC!
The other partitions where converted with no problem.
However, when the phone rebooted, super user is not working anymore, also tweaks and ext4 tools are not recognizing the kernel.
I tried flashing the same kernel again but the problem remained.
I tried flashing CF-Root-XX_OXA_JVO-v3.2-CWM3RFS and also the problem remained.
My question is:
1) How can I know the current partition (RFS or exts)?
2) Is it safe to flash the stock JPJV6 ROM to fix all that stuff and return to original firmware without root or ext4?
3) If it is safe, should I select "repartition" in ODIN?
Thanks in advance
Click to expand...
Click to collapse
dont panic!
yes, just flash back a stock rom with odin with repartition
it will change back to stock RFS
Thanks for replying
I'll try that and tell you what happened...
Try to install a new superuser.apk
chebon. said:
dont panic!
yes, just flash back a stock rom with odin with repartition
it will change back to stock RFS
Click to expand...
Click to collapse
agree with chebon...
The most stable method

[Q] Bootloop after going from CM7.1 > Telstra stock 2.3

Hi all,
I want to flash my phone back to Telstra (Aust) stock prior to selling it. I am currently running CM7.1 and I downloaded the Telstra gingerbread ROM from here and I then flashed the rom in odin with 512 Pit and Re-partition ticked. After the rom was flashed, the phone rebooted into recovery mode but then says "failed to mount /dbdata". Several other errors occur as well.
e:copy_dbdata.media: Can't mount /dbdata, your storage is not prepared yet.
I think this may be because there is a different file system etc in CM7, but I was under the impression that repartitioning when flashing a rom would take care of this?
Any help would be appreciated.
Rupert
edit: spelling
I worked it out - when going from CM7 I needed to flash a 3 file firmware with re-partitioning instead of a 1 file firmware. All good now!

[Q] EFS Mounting Problem

Hi,
I'm a newbee around here and I would really appreciate if someone could help me on this.
My GT-I9070 was fully functional till yesterday. I've been running CM10.2. Yesterday I tried to change the Kernal to Co-Core 8.2. I deeply regret doing that because I didn't had enough knowledge on how to change kernals. What I did was copied the Co-Core zip file to sdcard and applied it via CWM. After that, my phone restarted and it was stuck on the CM boot screen. I got mad and flashed the phone to stock 4.1.2 using ODIN. Then the setup wizard showed up and it kept on crashing giving me toasts, "gapps not working" and "setup wizard has unfortunately stopped".
I then went to stock recovery mode and the log said,
E:failed to mount /efs (No such file or directory)
E:failed to mount efs (Invalid argument)
Applying Multi CSC..
E:failed to mount /efs (Invalid argument)
E:multi_csc:Can't mount /efs Multi csc applied failed
I searched on n number of threads here in XDA about this problem and read in one thread that IMEI could've corrupted.
Then using ODIN, I flashed my mob to stock GB 2.3.6 with DDLD4 baseband. Then everything worked perfect. Phone booted up and was working perfect. But then I tried to update the phone to 4.1.2 via KIES, the KIES said "This phone can't be upgraded".
I again flashed 4.1.2 using ODIN, again it said gapps and setup wizard unfortunately stopped. I tried installing CM10.1, CM10.2, MIUI but in all cases, it got stuck on the bootscreen of each ROM. I flashed back to stock GB again and phone is working perfect now. When I go to "about phone", IMEI is showing with no error. It is the same IMEI which the phone had when it was bought. But when I go into recovery mode, it still says "/efs can't be mount". What could be the possible reason for this? How I can I fix this? Is there anyway for me to install the CM ROM again and successfully keep it up and running?
arjunkdas said:
Hi,
I'm a newbee around here and I would really appreciate if someone could help me on this.
My GT-I9070 was fully functional till yesterday. I've been running CM10.2. Yesterday I tried to change the Kernal to Co-Core 8.2. I deeply regret doing that because I didn't had enough knowledge on how to change kernals. What I did was copied the Co-Core zip file to sdcard and applied it via CWM. After that, my phone restarted and it was stuck on the CM boot screen. I got mad and flashed the phone to stock 4.1.2 using ODIN. Then the setup wizard showed up and it kept on crashing giving me toasts, "gapps not working" and "setup wizard has unfortunately stopped".
I then went to stock recovery mode and the log said,
E:failed to mount /efs (No such file or directory)
E:failed to mount efs (Invalid argument)
Applying Multi CSC..
E:failed to mount /efs (Invalid argument)
E:multi_csc:Can't mount /efs Multi csc applied failed
I searched on n number of threads here in XDA about this problem and read in one thread that IMEI could've corrupted.
Then using ODIN, I flashed my mob to stock GB 2.3.6 with DDLD4 baseband. Then everything worked perfect. Phone booted up and was working perfect. But then I tried to update the phone to 4.1.2 via KIES, the KIES said "This phone can't be upgraded".
I again flashed 4.1.2 using ODIN, again it said gapps and setup wizard unfortunately stopped. I tried installing CM10.1, CM10.2, MIUI but in all cases, it got stuck on the bootscreen of each ROM. I flashed back to stock GB again and phone is working perfect now. When I go to "about phone", IMEI is showing with no error. It is the same IMEI which the phone had when it was bought. But when I go into recovery mode, it still says "/efs can't be mount". What could be the possible reason for this? How I can I fix this? Is there anyway for me to install the CM ROM again and successfully keep it up and running?
Click to expand...
Click to collapse
Hi, did you try to flash other firmware?
Flash a new one and try to wipe data/factory reset.
YES, I DID
eduds said:
Hi, did you try to flash other firmware?
Flash a new one and try to wipe data/factory reset.
Click to expand...
Click to collapse
Yes, I mentioned, I tried to flash, CM10.1, CM 10.2 and MIUI also..I also did factory reset and wipe cache. But all of em was stuck on the bootscreen of the respective firmwares. :crying:
arjunkdas said:
Yes, I mentioned, I tried to flash, CM10.1, CM 10.2 and MIUI also..I also did factory reset and wipe cache. But all of em was stuck on the bootscreen of the respective firmwares. :crying:
Click to expand...
Click to collapse
No, I'm talking about original firmwares, not custom ROMs.
DDXL1 and DDLD4
eduds said:
No, I'm talking about original firmwares, not custom ROMs.
Click to expand...
Click to collapse
I flashed both of these baseband versions of GB..and DDULP8 baseband of JB..you want me to try flash more baseband versions?
did u solve it ?
arjunkdas
Click to expand...
Click to collapse
NO
amr diab said:
did u solve it ?
Click to expand...
Click to collapse
Not yet..I've been using GB for the past two months. Tried almost everything that I could find in xda. I'm afraid to go to Samsung SVC because I doubt they won't give me warranty for this problem. Do you have any solution?
arjunkdas said:
Not yet..I've been using GB for the past two months. Tried almost everything that I could find in xda. I'm afraid to go to Samsung SVC because I doubt they won't give me warranty for this problem. Do you have any solution?
Click to expand...
Click to collapse
i have the same problem
and i'm on GB too
i'm still searching every where
check this
http://forum.xda-developers.com/showthread.php?t=2506256&page=2
i will try and if it is solved i will tell u
amr diab said:
i have the same problem
and i'm on GB too
i'm still searching every where
check this
http://forum.xda-developers.com/showthread.php?t=2506256&page=2
i will try and if it is solved i will tell u
Click to expand...
Click to collapse
Ok man! I'm also on it!
arjunkdas said:
Hi,
I'm a newbee around here and I would really appreciate if someone could help me on this.
My GT-I9070 was fully functional till yesterday. I've been running CM10.2. Yesterday I tried to change the Kernal to Co-Core 8.2. I deeply regret doing that because I didn't had enough knowledge on how to change kernals. What I did was copied the Co-Core zip file to sdcard and applied it via CWM. After that, my phone restarted and it was stuck on the CM boot screen. I got mad and flashed the phone to stock 4.1.2 using ODIN. Then the setup wizard showed up and it kept on crashing giving me toasts, "gapps not working" and "setup wizard has unfortunately stopped".
I then went to stock recovery mode and the log said,
E:failed to mount /efs (No such file or directory)
E:failed to mount efs (Invalid argument)
Applying Multi CSC..
E:failed to mount /efs (Invalid argument)
E:multi_csc:Can't mount /efs Multi csc applied failed
I searched on n number of threads here in XDA about this problem and read in one thread that IMEI could've corrupted.
Then using ODIN, I flashed my mob to stock GB 2.3.6 with DDLD4 baseband. Then everything worked perfect. Phone booted up and was working perfect. But then I tried to update the phone to 4.1.2 via KIES, the KIES said "This phone can't be upgraded".
I again flashed 4.1.2 using ODIN, again it said gapps and setup wizard unfortunately stopped. I tried installing CM10.1, CM10.2, MIUI but in all cases, it got stuck on the bootscreen of each ROM. I flashed back to stock GB again and phone is working perfect now. When I go to "about phone", IMEI is showing with no error. It is the same IMEI which the phone had when it was bought. But when I go into recovery mode, it still says "/efs can't be mount". What could be the possible reason for this? How I can I fix this? Is there anyway for me to install the CM ROM again and successfully keep it up and running?
Click to expand...
Click to collapse
i got that problem too. you should flash your .pit file and check repartition in odin.
this solved my problem.
Patlcs said:
i got that problem too. you should flash your .pit file and check repartition in odin.
this solved my problem.
Click to expand...
Click to collapse
Are you saying I have to flash pit file alone? Or do a full flash of GB with repartition checked?
While flashing JB, I didn't used any pit file. Just used the .tar file which was selected under PDA of ODIN.
Any idea if checking repartition while flashing JB would work?
I'm currently running GB 2.3.6 baseband version DXLD1. And I've got 2 pit files one for 8GB which I got from the DXLD1 package I downloaded and one 16 GB which I downloaded separately.
arjunkdas said:
Are you saying I have to flash pit file alone? Or do a full flash of GB with repartition checked?
While flashing JB, I didn't used any pit file. Just used the .tar file which was selected under PDA of ODIN.
Any idea if checking repartition while flashing JB would work?
I'm currently running GB 2.3.6 baseband version DXLD1. And I've got 2 pit files one for 8GB which I got from the DXLD1 package I downloaded and one 16 GB which I downloaded separately.
Click to expand...
Click to collapse
No... you should flash pit file with the .tar.md5 file.
repartition will work on either GB or JB.
if you have the 8gb version you should use the 8gb .pit file and use the 16 gb .pit file if you have the 16gb version.
http://forum.xda-developers.com/showthread.php?t=2353293
check this man
it is worked for me !!!!!!!!!!!!!!
NO Backup EFS
amr diab said:
http://forum.xda-developers.com/showthread.php?t=2353293
check this man
it is worked for me !!!!!!!!!!!!!!
Click to expand...
Click to collapse
solution in that thread says you need to have an EFS backup. And I dont have it. And in next post, that guy said his restored IMEI is corrupted. Did u checked yours??!
Doubts
Patlcs said:
No... you should flash pit file with the .tar.md5 file.
repartition will work on either GB or JB.
if you have the 8gb version you should use the 8gb .pit file and use the 16 gb .pit file if you have the 16gb version.
Click to expand...
Click to collapse
My phone is the 16 GB version. I'm having some weird doubts. I beg your pardon if I'm asking noob questions but I need to know them.
Ok, so here's how I flashed JB 4.1.2
In the JB package I downloaded, ther was only .tar file and nothing else. The baseband version is DDULP8. So everytime I flashed JB, I did with .tar file alone and no pit file.
Now, whenever I flashed back to GB 2.3.6, I flashed by selecting three files in the DXLD1 download package. PDA file, CSC file and an 8GB pit file. I flashed with these files at the first place and the phone boots up, works well. But the internal storage is shown as 3.91 GB. To solve this, I downloaded a separate 16GB pit file and flashed the phone by just selecting the 16GB pit file. After I rebooted my phone, it shows 11.1 GB internal storage.
My doubt is, do I need to select the 16GB pit file and check repartition while flashing JB 4.1.2?
Or just check repartition and flash with .tar file alone?!
Didn't solved
Patlcs said:
i got that problem too. you should flash your .pit file and check repartition in odin.
this solved my problem.
Click to expand...
Click to collapse
tried it..didnt solve the problem!
arjunkdas said:
solution in that thread says you need to have an EFS backup. And I dont have it. And in next post, that guy said his restored IMEI is corrupted. Did u checked yours??!
Click to expand...
Click to collapse
i didn't have any backup and the imei is ok
just try it from 1-10
1) If you are with a Gingerbread rom, first have to migrate to a Jelly Bean
2) Now that you're with Jelly Bean, download the CWM Temporary, extract the files to a folder of your choice and move to your memory card.
3) Unplug the device and plug it into recovery mode
volume p / up + home + power
4) Select using the volume button the option "Apply update from external storage" and press the power
5) It will open a list with several folders and files, now navigate to the "CWM.zip" and press power again
6) It started to install and the phone screen goes all hazy, wait 5 seconds, press HOME and wait about 3 seconds will open the CWM version in "Touch"
7) Select "Wipe Cache"
8) Now select "advanced", then select "fix permissions"
9) Select "reboot system", a counter appears never ending, this time take out the battery and restart the device in recovery mode
10) The error message should no longer appear, now just install the Stock ROM Jelly Bean desired.
amr diab said:
i didn't have any backup and the imei is ok
just try it from 1-10
1) If you are with a Gingerbread rom, first have to migrate to a Jelly Bean
2) Now that you're with Jelly Bean, download the CWM Temporary, extract the files to a folder of your choice and move to your memory card.
3) Unplug the device and plug it into recovery mode
volume p / up + home + power
4) Select using the volume button the option "Apply update from external storage" and press the power
5) It will open a list with several folders and files, now navigate to the "CWM.zip" and press power again
6) It started to install and the phone screen goes all hazy, wait 5 seconds, press HOME and wait about 3 seconds will open the CWM version in "Touch"
7) Select "Wipe Cache"
8) Now select "advanced", then select "fix permissions"
9) Select "reboot system", a counter appears never ending, this time take out the battery and restart the device in recovery mode
10) The error message should no longer appear, now just install the Stock ROM Jelly Bean desired.
Click to expand...
Click to collapse
Tried! Still getting steup wizard stopped message!
arjunkdas said:
tried it..didnt solve the problem!
Click to expand...
Click to collapse
try to flash .pit file alone
Patlcs said:
try to flash .pit file alone
Click to expand...
Click to collapse
tried that too!

[REQ-DEV HELP] Experienced user and flasher stuck on DOK2 mounting partitions problem

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?

Categories

Resources