Related
I have a problem unlike others, i m caught in a bootloop while flashing 2.3.6 from ICS Build 9 using odin, i had nothing better to do, serves me right, I can't go to recovery bcos my stupid ph is one of those that do not have the 3 button recovery.
After odin pass when i remove the usb it goes into installation but it says:
E: copy_dbdata_media:can't mount/dbdata. your storage not prepared.Please use menu for format and rebot actions.(I dun ve that option)
E:failed to mount/dbdata file exist
deleting file failed
updating failed
cache wipe failed
Applying multi csc. Installing multicsc
Can't access
Successfully applied multi csc
But the on reboot it goes into Samsung and bootanimation over n over
Any help appreciated Thanks!!
I ve also tried flashing other stock roms but the it does not reboot instead showing the connection between ph and pc sign. Thanks again
I thought everyone checked if 3 button recovery was working before taking a walk in the dark valley of flashaholics.
Tapatalked - There's a Thanks button somewhere
Why didn't you flash something to enable the 3 button recovery before flashing anything else? Flashing without the 3 button recovery is just asking for a huge headache and even a brick. Now you may have to resort to making/buying a USB JIG to get into download mode.
ndmuni said:
I have a problem unlike others, i m caught in a bootloop while flashing 2.3.6 from ICS Build 9 using odin, i had nothing better to do, serves me right, I can't go to recovery bcos my stupid ph is one of those that do not have the 3 button recovery.
After odin pass when i remove the usb it goes into installation but it says:
E: copy_dbdata_media:can't mount/dbdata. your storage not prepared.Please use menu for format and rebot actions.(I dun ve that option)
E:failed to mount/dbdata file exist
deleting file failed
updating failed
cache wipe failed
Applying multi csc. Installing multicsc
Can't access
Successfully applied multi csc
But the on reboot it goes into Samsung and bootanimation over n over
Any help appreciated Thanks!!
I ve also tried flashing other stock roms but the it does not reboot instead showing the connection between ph and pc sign. Thanks again
Click to expand...
Click to collapse
You need a 3 files ODIN rom , and before flashing make so you have PIT and repartitions , your problem is a minor problem ( because you don't repart the partitions, that's why it's bootlooping
adslee said:
Why didn't you flash something to enable the 3 button recovery before flashing anything else? Flashing without the 3 button recovery is just asking for a huge headache and even a brick. Now you may have to resort to making/buying a USB JIG to get into download mode.
Click to expand...
Click to collapse
After kies update i was able to go into download mode so that was why i was'nt too worried, my mistake was deleting the file of build 9 in the internal sd b4 i flashed the .6 otherwise when odin finished my phone was in recovery mode i could ve just install zip fr sd again. The problem that the state my ph is in i could not get anything into the sd not even fr pc. Only chance is tru odin, i suppose now i ve to look for firmware that i flash with repartition to wipe the files and data fr internal sd maybe that might do it.
ndmuni said:
After kies update i was able to go into download mode so that was why i was'nt too worried, my mistake was deleting the file of build 9 in the internal sd b4 i flashed the .6 otherwise when odin finished my phone was in recovery mode i could ve just install zip fr sd again. The problem that the state my ph is in i could not get anything into the sd not even fr pc. Only chance is tru odin, i suppose now i ve to look for firmware that i flash with repartition to wipe the files and data fr internal sd maybe that might do it.
Click to expand...
Click to collapse
Ah ok, I thought you couldn't get into download mode, but it's always good to have recovery mode since I always found CWM pretty important
Mawdo said:
You need a 3 files ODIN rom , and before flashing make so you have PIT and repartitions , your problem is a minor problem ( because you don't repart the partitions, that's why it's bootlooping
Click to expand...
Click to collapse
This is exactly what i m doing now, downloading couple but i m not too sure cos i ve not use odin on 3 files, fr what i read its just putting the pit file in pit and tar file in pda what is the other? if i extract n c than i'll kn if what i downloaded has 3 files.
ndmuni said:
This is exactly what i m doing now, downloading couple but i m not too sure cos i ve not use odin on 3 files, fr what i read its just putting the pit file in pit and tar file in pda what is the other? if i extract n c than i'll kn if what i downloaded has 3 files.
Click to expand...
Click to collapse
When I messed my partition, I had to use ODIN. You will need four files:
1. PIT file
2. PDA
3. CSC
4. PHONE
ndmuni said:
This is exactly what i m doing now, downloading couple but i m not too sure cos i ve not use odin on 3 files, fr what i read its just putting the pit file in pit and tar file in pda what is the other? if i extract n c than i'll kn if what i downloaded has 3 files.
Click to expand...
Click to collapse
Pit file goes to PIT, CODE file goes to PDA, MODEM file goes to PHONE, and CSC goes to CSC, and make sure Re-partition is checked
Thanks to Ramad for his stockfirmware download and all you for yr assists, my SGS is up and running, going to bed now will be rooting it when i wake up Cheers!!!!
My phone is stuck on firmware on "upgrade encountered an issue. Please select recovery mode in Kies and try again."
I tried Kies 3 and it doesn't recognise the phone. I tried different firmwares the invalid .4ext error and says the file too big 475000 < 512000 something among those lines. I read that I will need to re-partition the memory with .PIT file for the note 4, which is no where to be found on google. I hope someone will be kind enough to extract the .PIT file from their phone and post it here.
Cheers,
Mus
Me too
madinho said:
My phone is stuck on firmware on "upgrade encountered an issue. Please select recovery mode in Kies and try again."
I tried Kies 3 and it doesn't recognise the phone. I tried different firmwares the invalid .4ext error and says the file too big 475000 < 512000 something among those lines. I read that I will need to re-partition the memory with .PIT file for the note 4, which is no where to be found on google. I hope someone will be kind enough to extract the .PIT file from their phone and post it here.
Cheers,
Mus
Click to expand...
Click to collapse
Me too i have this problem please gays share pit file for N910F thanks to all
Assadesign_sy said:
Me too i have this problem please gays share pit file for N910F thanks to all
Click to expand...
Click to collapse
I had the same problem. All i did was use Odin to put TWRP on my phone and it booted back up.
N910F
I tried many way nothing happen i cant use odin fail in everything i try to flash with rom or recovery. and now phone keep restarting and i cant wipe data?? anything i add or delete after restart go back like before like nothing happen?????
Guys I tried flash latest Sweden and have same problem size too big and ext4 failed,then I flash Philz recovery and voila phone booted everything its ok!!!
If you download a stock Samsung ROM, remove the .md5 from the end of it, and then extract the archive, you should find the PIT file in there.
I've not had to do it myself, because I'm using an S4 at the moment and was able to get a PIT file download on its own. So I can't verify 100% that it will be there, but I read it in a thread somewhere that it is.
Give it a try..
same problem
i hv same problem. but after instaling all samsung recovery.tar via odin it stuck on start up showing "android is not seandroid recovery."
i hv tried dfrnt stock firmware to flash via odin but all fails. need help?????????????
let me start by saying I've read almost all your threads only reason im actually bothering is because I'm really feeling like smashing my phone to bits .... that's how frustrating this has been. my phone was rooted and custom ROM till about 4 weeks ago, when Tmobile told me the IMEI on my phone was reported as stolen ... i grabbed my box as my phone i have since it was new and compared the IMEI ... to my surprise IMEI on box and on Phone chasis was not same as the one inside phone .... my phone was unblocked by a local unblocking service here in PR so i went to them and surely they took my phone and lent me another one while it was getting fixed ... "IMEI" was being changed again and it wasn't the one on the box either ... the gave me lame excuse about my IMEI .... they kept my note 3 for a week almost 2 after i got it back my note 3 said it was rooted but i couldn't use any apps for rooted phones as it would say i didn't have root access ... as i no longer trust these people i went on and tried fixing the issue myself ... and here's the thing i have tried absolutely everything cf auto root tar from download mode and even thru odin all versions of odin and using the sm-n900w8 cf auto root and the right roms "different one's to see if it was the rom's or the phone" i am about to give up i simply cannot root my phone so that i can install a modified rom ... thought of contacting you guys ... as my last resort ... i am so sorry to bother i know you guys are very busy ... but if you guys cant help i will have to settle for just a regular note 3 and that sucks... i have picture of absolutely everything i have tried and the outcome and the errors i have gotten and all in pics if needed...
Please pardon me for asking for a little help i really thought i could done this i guess i am not as savvy as i have thought...
Thanx in advanced Emilio Pinella
Does the IMEI on the box match the IMEI on the label attached to the battery compartment?
Have you tried using Odin to get back to a completely stock ROM, flash TWRP, and flash supersu from TWRP?
Ok here we go ...
Yes IMEI on box and phone chasis are same ... the different one is when you press *#06# ...
Secondly i have tried usin odin but absolutely all the files i downloaded are in .zip and odin does not recognize any of them i tried to convert from zip to .tar but it crashes odin thats why i have tried it from recovery mode ... even CF auto flash for sm-n900w8 doesnt work odin does recognize phone so it isnt a driver issue ... maybe if i had apropiate files in right format i could try flashing from odin ... but i dont and i cant find the files in .tar which is what odin recognizes ... as i said i have really tried almost everything ... i have been wondering can it be possible these people lock my phone in a way i could not do anything? ... will wait for your replay ... my phone sucks @The Moment i havent downloaded anything as i am factory resseting everytime i try a new method ... just fyi i do activate devops and usb debug after each wipe ...
Use 7zip or WinRAR to extract the zip from sammobile.com. Once unzipped, it should give you a tar. md5 file.
hello again...
well i was certain of my answer but before i started writing i had doubts so i went and open all the files i have for flashing with odin ... and yes none of my .zip files have any .tar files in them , i have no clue why they are zip files if they are intended for use with odin ... so i went to sammobile.com and yes i had downloaded the 3 files pertaining to my cel phone and tried flashing the stock rom but none of them worked ... some just werent recognized and some gave me whole file signature error or signature failed error ...
i have Tesla-hlte-5.1.1.High_Voltage.2.1-Release-20150824 and its a zip and has no .tar, inside also have cm-12.1-20150423-UNOFFICIAL-temasek-hlte-V10.4 and also no .tar inside and its in .zip format, also have X-Note_Build_15_ND5_Public and yes its a zip and no tar inside...
SM-N900W8-4.4.2-(KOT49H.N900W8UBUCNI1) is my original ROM and it does not have .tar inside ....
something they all do have in common is they have an img file inside that cannot be open ...
and i downloaded files for twrp but jajaja also in zip and no tar inside , just an image file wich is not recognized by odin and not recognized by recovery mode either as i have tried putting all these files in my sd card and have tried doing from recovery ending with results of .... whole file signature failed and signature failed error and also wrong footer error i have pic of all this ... would you want me to send them to you i wouldnt mind... btw thx for your time i really apreciate it.
If the files came from sammobile.com, they are defnintely tar. md5 files.
How many times are you unzipping the file from sammobile.com? The original file from sammobile.com should only be unzipped once.
Well after last replay i went and downloaded all 4 available files for my note 3 from the one dating at 2013 to the one with 5.0 lolli i will do this again tonight and will post the results ... i am certain they will be the same as last time but can you please remind me of steps to take using odin and which odin should i use as i have a few versions .
Once again thx for your time .
I like Odin 3.07 which is what I always use.
If you use Odin 3.07, put the phone into download mode, open Odin 3.07, place the tar.md5 file in the PDA box, uncheck everything except f.reset time, connect phone to computer, flash, when you see the word "RESET" in the status window, remove USB cable, remove battery, replace battery, use button to boot into recovery, perform a factory reset, wipe cache, reboot.
Ok
I will do this from home as soon as i get there and i will post results any specific one you would want me to start with?
Start with a rom that matches the bootloader currently on the phone.
Ok
Hmmm is bootloader the number after model example UBUCNC1?
Yeah just checked and bootloader would be for my current 4.4.2 N900W8UBUCNC1 .... Also says that latest firmware is one of the firmware i downloaded the one containing lolli 5.0
So you downloaded the cnc1 from sammobile.com and there is no tar.md5 file after unzipping?
Just got home
I got home im unzipping and i will let you know in about 2 minytes if there are tar.md5 inside what i downloaded ...
Ok so far so good
All have .tar.md5 in them so i will try flashing with same rom version i have 4.4.2 to see if then i can root and flash a cutom rom ... tell you in a few minutes how it went... wish me luck.
ok finished
i finally got to flaSH WITH odin and now my phone is 5.0 lolli ... can you guide me on how to flash root with odin as cf auto root does not work i took picture of what it did when i tried to auto root tell me where to send it .... or can you tell me where or who might have tesla 5.1.1 high voltage rom or X-note in .tar.md5 format ...
once again thanks for your time and understanding all i need now is to be able to root it so that i may install custom rom after i actually find them in .tar.md5 format.
Find twrp here
http://forum.xda-developers.com/showthread.php?t=2494245
Get the latest 2.8.7 or any 2.x.x 4.4 .tar.
Then get SuperSu flashable. You can google that.
Flash twrp with odin.
Flash SuperSU.zip with twrp.
It's rooted.
If you want to flash a custom rom just flash the rom of your choice in twrp. No need to root first.
Sent from my SM-G925F
Root is not required if you want to install a custom ROM, just install a custom recovery. I recommend flashing TWRP.
Find TWRP for your device from here (make sure you download the tar version of TWRP): http://teamw.in/Devices/
Supersu 2.46 is here: https://download.chainfire.eu/696/SuperSU Download and save Supersu to either the internal or external memory. If you put supersu on an external memory card, power off the phone and put the card into the phone.
Boot the phone into download mode.
Open Odin and uncheck everything except f.reset time.
Click on PDA/AP button and put TWRP into the box.
Connect the phone and flash TWRP in Odin.
When you see the word "RESET" in the status window, remove the USB cable, remove battery, replace battery, boot into recovery, flash Supersu, and reboot.
Ok will do now and tell you if anything ... but i read somewhere this version of android is unflashable ... but i will try what you are saying .
Which version of Android is not flashable?
Ok i gotta say if it wasnt for you i would still be stuck ... fortunetly i am riding 5.0 lolli and my phone is now officially rooted all i need to do is get tesla's 5.1.1 high voltage on it and i will be good ... so basically just need tesla in .tar.md5 to be good ... all thx to you .
Where can i download it or now that i have twrp as my recovery can you guide me thru on that? ... thx again.
When I restore by Odin my N910H 5.1.1
my Note 4 is hanging SW REV CHECK FAIL DEVICE 2 BINARY 1
Please help!
khongchinhxac said:
When I restore by Odin my N910H 5.1.1
my Note 4 is hanging SW REV CHECK FAIL DEVICE 2 BINARY 1
Please help!
Click to expand...
Click to collapse
pharhaps you have tried to restore downgrade version. plz try to the latest software version.
khongchinhxac said:
When I restore by Odin my N910H 5.1.1
my Note 4 is hanging SW REV CHECK FAIL DEVICE 2 BINARY 1
Please help!
Click to expand...
Click to collapse
i have the same problem...please!!! help me!!!
Probably you've had an OTA (over the air, wifi) update. You should flash latest firmware for your device. Samsung locked the bootloader, it's not possible to install an older firm anymore (until someone finds how).
any solution to fix this problem ?
Any solution to this?
Looking for a solution!!!!
Nixdax said:
Looking for a solution!!!!
Click to expand...
Click to collapse
I fixed my phone by downloading stock 5.1.1, unpacked with 7zip, deleted modem.bin and sboot.bin from the extracted contents, packed the contents again as tar using 7zip and flashed via ODIN.
Looking for an answer as well. Same situation after I wiped cache. Phone is on the fritz. Ive been up for the past 6 hours trying to fix it. Im trying to save my files on my phone in the case I need to wipe everything.
theplagueisback said:
I fixed my phone by downloading stock 5.1.1, unpacked with 7zip, deleted modem.bin and sboot.bin from the extracted contents, packed the contents again as tar using 7zip and flashed via ODIN.
Click to expand...
Click to collapse
do you mean aboot.bin? and when you packed the contents, did you just zip them? then just the extension to .tar? or did you change it to .tar, THEN zip it?
Figured it out on my own. Flashed CF autoroot. Then flashed 5.1.1 which is the most up to date firmware. Im not sure if the issue was because I was doing 5.1.0 and didnt realize that was the most UTD version, or if CF to 5.1.1 was the trigger. Either way, it worked.
I tried this but also failed, then I read somewhere else that I need to remove cm.bin and sboot.bin.
I did and it flashed OK, but phone is stuck in bootloop and wont go to recovery mote form e to reset.
I am presently searching for a way to get it out of bootloop
dannyogolo said:
I tried this but also failed, then I read somewhere else that I need to remove cm.bin and sboot.bin.
I did and it flashed OK, but phone is stuck in bootloop and wont go to recovery mote form e to reset.
I am presently searching for a way to get it out of bootloop
Click to expand...
Click to collapse
try rename firmware file from .md5 to .tar and extract it using 7-Zip, delete or move sboot.bin and modem.bin then make a new 7-Zip archive with .tar extension and install it regulary by Odin
Thanks.
But like I wrote, I have been able to flash, but phone is in bootloop now
use the sboot and modem files from the LATEST update..just swap em out
Hey,
I wanted to root my Galaxy S4 i9505 using CF-auto root. I cheked the version of my s4 i9505 which was i9505xxuhoj2, then go to https://desktop.firmware.mobi/ find my device model and exact same build (i9505xxuhoj2). I generated cf auto root file, boot phone in bootloader mode, unzip file and used odin (which was in that zip file too) to flash this generated file (using AP). Odin gives me FAIL and I cant boot my phone normally because of error during start (firmware upgrade encountered an issue please select recovery mode in kies).
So I flashed stock firmware (using Odin) with another build. This time i9505xxupqg1. Everything went well my S4 was running normally. So i decided repeated the procedure. Go to https://desktop.firmware.mobi/ and genereate cf auto file (this time for build i9505xxupqg1). I flashed the cf auto root file using odin and again it gives me FAIL.
Below screen of that FAIL:
https://imgur.com/a/SujjD
Can anyone help me with this?
Why this is happening ?
Cheers
Flash back to stock, flash twrp, flash supersu from twrp.
Thanks for reply.
I did this earlier what you said and everything was OK.
I had TWRP and Root using SU.
The problem isnt rooting itself.
The point is i wanted to tested rooting with CF-AutoRoot method.
And I'm wondering what am I doing wrong.
I did everyting correctly (exact same device model and build version) and ODIN gives me FAIL like i said above.
If Odin is failing, try a different version of Odin, a different USB cable, and different USB port.
I got the same problem with a Sprint Note Edge that I tried to root the same way. I'm currently downloading the stock firmware from sammobile.com to flash a stock ROM.
Thomass30 said:
Hey,
I wanted to root my Galaxy S4 i9505 using CF-auto root. I cheked the version of my s4 i9505 which was i9505xxuhoj2, then go to https://desktop.firmware.mobi/ find my device model and exact same build (i9505xxuhoj2). I generated cf auto root file, boot phone in bootloader mode, unzip file and used odin (which was in that zip file too) to flash this generated file (using AP). Odin gives me FAIL and I cant boot my phone normally because of error during start (firmware upgrade encountered an issue please select recovery mode in kies).
So I flashed stock firmware (using Odin) with another build. This time i9505xxupqg1. Everything went well my S4 was running normally. So i decided repeated the procedure. Go to https://desktop.firmware.mobi/ and genereate cf auto file (this time for build i9505xxupqg1). I flashed the cf auto root file using odin and again it gives me FAIL.
Below screen of that FAIL:
https://imgur.com/a/SujjD
Can anyone help me with this?
Why this is happening ?
Cheers
Click to expand...
Click to collapse
Hello
You do not need to generate a CF-AutoRoute, just google and download the original CF-AutoRoute.zip which roots ALL versions of the device, the baseband does not matter.
Ensure debugging is enabled
Place device into recovery (download)
Add device to Odin
Unzip the file, add the .md5 file to Odin and flash, job done.