Related
Hi,
I bought a bricked Galaxy Note 10.1 GT-N8000 and managed to flash stock firmware and booted correctly except for a strange Watermark on screen which showed device specs. Then I tried flashing German Kitkat version thru ODIN which failed, now the device is stuck on Galaxy Note 10.1 screen even though I have tried flashing ODIN many times and it has shown PASS but doesn't go beyond that. It can't even go get into recovery (only can get to ODIN mode). Please help me as i can't go beyond that even though i have searched a lot google, no one seems to have gotten any solution.
34 views but no suggestion!!! It seems mighty developers never bought this phone to suggest something. It's strange ODIN can flash and shows success (firmware or any recovery) but nothing seems to install and make it boot. Pl someone got some idea?
usman3206 said:
34 views but no suggestion!!! It seems mighty developers never bought this phone to suggest something. It's strange ODIN can flash and shows success (firmware or any recovery) but nothing seems to install and make it boot. Pl someone got some idea?
Click to expand...
Click to collapse
Have you tried flashing a custom rom?.
Just realised you said it wouldn't go into recovery.
Try flashing from another pc
Which version of ODIN are you using?.
No haven't tried custom ROM but probably this device was never rooted but can give that a try. Yes it won't go into recovery at all. I will give try from another PC. I have tried ODIN v. 1.85 and v3.09.
usman3206 said:
No haven't tried custom ROM but probably this device was never rooted but can give that a try. Yes it won't go into recovery at all. I will give try from another PC. I have tried ODIN v. 1.85 and v3.09.
Click to expand...
Click to collapse
I think it might be a driver issue with your pc if it won't work with v1.85.
Trying reinstalling the Samsung drivers on your pc.
I flashed stock firmware before with the same PC and it worked and I have tried to use same ODIN and same stock firmware which worked before. Even now ODIN says PASS, infact there is no failure at all but device itself is stuck on "Samsung Galaxy Note 10.1" splash screen. I have tried restarting PC, using different USB ports but ODIN always says PASS without problem but device condition is same. I think may be i should change firmware/ stock recovery even though previously the same worked. I am at a loss, don't know what to do?
P.S: Edit: as i was writing these comments I thought of trying out same german kitkat version which earlier broke my device and this time it succeeded and at least device has come out of that splash screen though it is still stuck samsung animation screen. so i will try more and will update. any suggestions are welcome. thanks
ok, now it's possible to get into stock recovery at least, although it shows "E:failed to mount /efs (Invalid argument)" and " Applied the CSC-code : unknown". What to do now? kindly advise
Finally managed to ODIN a stock firmware to work correctly and device is able to boot but show "Broadband: Unknown". Thanks for your help
usman3206 said:
Finally managed to ODIN a stock firmware to work correctly and device is able to boot but show "Broadband: Unknown". Thanks for your help
Click to expand...
Click to collapse
Can you check your IMEI if its available in setting/device? If its not your EFS is missing or corrupt.
yes, IMEI is Unknown! that means EFS is corrupt! I know the IMEI, I have the box, how can i restore it?
usman3206 said:
yes, IMEI is Unknown! that means EFS is corrupt! I know the IMEI, I have the box, how can i restore it?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2111485
Thanks a lot for the link. I will go through it deeply and try it out and will come back.
Just some food for thought! Since i bought this device bricked and never knew which firmware it came with and tried different firmwares randomly until i found one that could work only with "Factory Mode". My question;
1. Could it be that I flashed a wrong firmware causing this thing to go Factory Mode?
2. Or must it be corrupt EFS folder?
I am asking because now i rooted my device, it is showing one EFS folder and when i tried to flash Philz recovery over TWRP it gave me error that " This package is for 'c).p4noterf.n8000.GT-N8000' devices; this is a 'p4notewifi'.
E:Unable to mount '/efs'.
Any suggestions? Please
I think this efs folder is generated automatically by the android when it can't find one because when i checked it was an empty folder, nothing inside. so may the issue is of broken efs system folder. Can't create my own IMEI since i have the box and IMEI is written on it.
Does this device use SIM to make calls or just for data download? Couldn't figure out! Is there a simple way to get rid of the "Factory Mode"? may be i don't need all that SIM functionality after all but certainly want to get rid of that "Factory Mode".
Can I try this one
http://forum.xda-developers.com/showpost.php?p=39523753&postcount=4
Any suggestions, kindly do suggest if i should do whatever is described in the above post or the ones suggested before written below
http://forum.xda-developers.com/showthread.php?t=2111485
Please advise which method should i try. Awaiting eagerly for input
Is it possible to use following tool to repair EFS?
http://forum.xda-developers.com/gal...ol-updated-09-06-14-efs-professional-t1308546
Please suggest me something if someone out there know something?
Finally fixed it by using the thread shown above but i have a fake IMEI but factory mode is no longer there and everything is working normally. Is it possible to change IMEI to my own by using methods i have seen on net including youtube? please advise
usman3206 said:
I flashed stock firmware before with the same PC and it worked and I have tried to use same ODIN and same stock firmware which worked before. Even now ODIN says PASS, infact there is no failure at all but device itself is stuck on "Samsung Galaxy Note 10.1" splash screen. I have tried restarting PC, using different USB ports but ODIN always says PASS without problem but device condition is same. I think may be i should change firmware/ stock recovery even though previously the same worked. I am at a loss, don't know what to do?
P.S: Edit: as i was writing these comments I thought of trying out same german kitkat version which earlier broke my device and this time it succeeded and at least device has come out of that splash screen though it is still stuck samsung animation screen. so i will try more and will update. any suggestions are welcome. thanks
Click to expand...
Click to collapse
Hi there.
The Note is a tablet 10.1 wifi version?
Is that I have exactly the same problem as you and I do not know what to do to get my tablet.
Could you give me the link of the rom with which you solved the problem? Thank you
spider1371 said:
Hi there.
The Note is a tablet 10.1 wifi version?
Is that I have exactly the same problem as you and I do not know what to do to get my tablet.
Could you give me the link of the rom with which you solved the problem? Thank you
Click to expand...
Click to collapse
Mine is wifi+3G version, its called GT-N8000. Mine was bricked before and I flashed it using ODIN (its available everywhere almost) and stock firmware (you need to use the one installed on it from factory, you can find download link from sammobile site but be careful download the one that is specific for you model no.). Then describe your problem may be i can help you.
this is the second time i've soft bricked my phone in the past 6 days and if this is fixable i will probably consider researching for weeks at a time before trying anything new..
anyway, the first time i soft bricked my phone last week, my s6 was rooted (via chainfire, G920IDVU1AOC6) but i decided to unroot so i could update software. after unrooting with SuperSU, i attempted to update by using smart switch and then something went wrong with that process (my firmware was at G920IDVU1AOC4) which i then fixed by flashing G920IDVU1BOE3 (latest stock firmware) WITHOUT the hidden.img
backstory out of the way, i wanted to flash TWRP so i could install xposed installer. i used the same chainfire firmware that worked the week prior (above) and so now my phone is soft bricked
things i've tried:
- flashing recovery of AOC4 - i can get back into recovery mode with the older firmware
- flashing AOC4 stock firmware with AND without the hidden.img
- flashing the BOE3 stock firmware with AND without the hidden.img
i'm still able to get into download mode and stock recovery and i've already tried wiping cache and factory reset but nothing works.
i continue to get FAILED on odin
if anyone is able to bring my phone back from purgatory for the second time it would be greatly appreciated.
thanks in advanced, mojo.
Ok, I soft bricked my s6 too :/ its fine now so dont worry, actually, I read somewhere the problem of failing is in Odin, and you need to flash the stock recovery and then recocery.img you extracted from it in a way odin can read, im from my phone now so I will try to search it out, hope I will find. Dont worry dude your s6 is alive.
Ok i found it, http://forum.xda-developers.com/galaxy-s6/help/solved-stuck-download-mode-failed-odin-t3104736 , I burned stock and then the file he supplied,worked like a charm.
JusTeN_ said:
Ok, I soft bricked my s6 too :/ its fine now so dont worry, actually, I read somewhere the problem of failing is in Odin, and you need to flash the stock recovery and then recocery.img you extracted from it in a way odin can read, im from my phone now so I will try to search it out, hope I will find. Dont worry dude your s6 is alive.
Ok i found it, http://forum.xda-developers.com/galaxy-s6/help/solved-stuck-download-mode-failed-odin-t3104736 , I burned stock and then the file he supplied,worked like a charm.
Click to expand...
Click to collapse
thank you so much for your reply and reassurance! i'll try this out right now and update on the results
UPDATE: i tried flashing stock and then the my-recovery.img.tar and i could get into recovery but i was stuck in boot loop.
is there something i'm doing that's incorrect?
Saafir said:
Did you remove the cable, boot download mode, then reconnect and let the driver install screen complete on your PC? Sorry if its a bit redundant but I had made this mistake before.
Click to expand...
Click to collapse
yes i have reconnected each time but thanks anyway!
JusTeN_ said:
Ok, I soft bricked my s6 too :/ its fine now so dont worry, actually, I read somewhere the problem of failing is in Odin, and you need to flash the stock recovery and then recocery.img you extracted from it in a way odin can read, im from my phone now so I will try to search it out, hope I will find. Dont worry dude your s6 is alive.
Ok i found it, http://forum.xda-developers.com/galaxy-s6/help/solved-stuck-download-mode-failed-odin-t3104736 , I burned stock and then the file he supplied,worked like a charm.
Click to expand...
Click to collapse
I FIXED IT.
i'm not exactly sure of the steps i took, as i had to keep waiting for my Unified Android Toolkit to create the tars but essentially what i did was i flashed;
- stock BOE3 WITHOUT hidden.img
- TWRP recovery (was able to boot into twrp and when i looked through some settings (reboot) it said i had no OS installed for some reason
- from this info i tried flashing the AOC4 older firmware WITHOUT hidden.img then it worked.
do you think it is worth attempting the smart switch thing mentioned in that link you posted?
i wouldn't want to run into this problem again..
my lord.. so SOMEHOW i managed to get myself into this for THE THIRD TIME..
once i got it fixed, just a few hours ago, everything was fine and i was then able to flash CF root again.
but once i tried to install TWRP (it worked before i fixed the second time) odin FAILED again and i'm back to square one.
i'm unsure how to properly fix it and the steps i took before aren't working now and i can't even flash any recoveries (whether its AOC4, BOE3 or TWRP)
can anyone suggest anything else please?? i'm in panic mode again lol
this is definitely the last time i try to do any type of configuration with this device.
Do you have recovery now? Maybe burn some custom rom? ..
JusTeN_ said:
Do you have recovery now? Maybe burn some custom rom? ..
Click to expand...
Click to collapse
now i can't flash the twrp .. it won't work. this suck so much!
UPDATE (final update, hopefully ): fixed it AGAIN.
after going through this hellish nightmare for the 3rd time and reading countless threads, i've discovered that the FAILs on odin may be occurring due to the corruption of the firmware file.
so if anyone goes through my problem, CREATE A COPY of the desired firmware before flashing with odin!
thanks justen for your patience and attempts to help me!
I tried to root my SM-G930F with current firmware G930FXXU1DQB3_G930FDBT1DQA8_DBT with this CF Autoroot file: https://download.chainfire.eu/929/CF-Root/CF-Auto-Root/CF-Auto-Root-herolte-heroltexx-smg930f.zip The latest one is based on NRD90M.G930FXXU1DQD7 and I am not sure if this is a problem.
During flashing the phone rebooted once showing "Kernel is not seandroid enforcing", then after some seconds another reboot. I waited nearly one hour with the phone beeing stuck in the samsung logo. When I shutdown and boot up the same happens. When in Recovery mode it shows first some failed "update" but I can get in the menu, download mode also working.
Now I am pretty lost about what I can do next. Of course my data is prio1 so I was searching for a way how to recover the phone and keep my data. Prio 2 is I still want root.
I have searched the whole day and I found the following options:
1. Flashing the whole Stock Rom: As I have read this should fix the bootloop problem, but since it's a 5-part ROM it will most likely also wipe my data - I really absolutely want to avoid this if possible!
I also read in some cases you don't have to check "Re-partition" if you don't use another CSC (this would be the case). So I was wondering if I could flash stock without re-partition and erasing user data.
2. Flashing only boot.img and/or recovery.img: Chainfire writes "If it still doesn't do anything after 5 minutes, something has gone wrong, and you should probably reflash your stock boot.img and recovery.img." Funnily he doesn't provide any guide -.- I don't know if this is trivial (I have only some basic knowledge on the whole Android flashing) but I was searching like crazy for any tutorial how to do this. My idea was that in this way only the recovery and boot are restored and user data is untouched- correct? So the only guides I found going in this direction are those mentioned here: https://forum.xda-developers.com/showpost.php?p=67648452&postcount=2
Now as these are rather old I am even not sure if they still count for Android 7.0 as I don't want make even more damage. Therefore my question - is this a possibility to convert the IMG to TAR and flash them ? Are both needed or just one, is the order important etc.. ? Maybe someone has a more specific guide.
3. Flashing TRWP: I have not read much about this yet because I wanted to stick to the simple Autoroot method and also don't make things more complicated. But I was wondering if in this way the bootloop could also be fixed and my original goal of rooting also could be achieved?
4. Trying CF Autoroot with earlier version: I searched for any archive of the CF Autoroot images. Maybe I could get the phone back to work with an image based on my version. Problem is it seems Chainfire does not keep the older versions and I didn't find any in other places. Anyone got such version for the DQB3? It would be worth an easy try..
5..... any other possiblity ?
General question for the future: Does anyone know why the rooting went wrong? What was my mistake? I striclty followed the guide, have activated OEM and USB Debugging, started Odin as Admin etc. Is it a version mismatch issue ?
I am really thankful for any advise! In the past I flashed my SGS2 and SGS5 and never had any issues as I always followed the guides and was very careful. Can't understand why there is no warning for this particular case ..
Michael
Flash stock again using ODIN (do not change any settings) and use HOME_CSC instead of CSC and you will not lose any data
HOME_CSC = No Wipe
CSC = Wipe
Then follow the TWRP / SuperSU thread to get root
I flashed as you proposed and the phone is back to normal without any data lost
Thank You so much *detection*, You saved me a lot of trouble!
For anyone else having the same problem I used this guide (it's for the S7 edge but process is the same).
I will report back if I managed to root with TWRP and how to do it.
BR
Michael
:good:
I've got the same problem (stuck at logo after Auto-root). Do you know any working solution to root S7 Edge without loosing the data?
wojtas44 said:
I've got the same problem (stuck at logo after Auto-root). Do you know any working solution to root S7 Edge without loosing the date?
Click to expand...
Click to collapse
Ask in the Edge forums
https://forum.xda-developers.com/s7-edge
Here is what I did so far to get here.
First I followed the guide to root my phone, and to be honest, all was perfect. I had to restore stock rom cause my first few tries failed. But seems I flashed a rom for a different provider. It worked anyway, but I don't have my sim card in that phone, it's temporarily in another device.
I had a little issue in settings, where battery was coming up two times in the list. That bugged me, I wanted to restore the rom and see if a full restore would take care of this issue, but somehow, after I installed twrp and rooted my phone, I can no longer flash anything stock with odin, it fails.
If I try to flash the AP tar.md5 file, it fails when it gets to system. And then after rebooting, I see this message:
"An error has occurred while updating the device software. Use the emergency recovery function in the Smart Switch PC Software"
I tried installing smart switch and kies, and both software doesn't detect my device in download mode or twrp (obviously)...
So to get rid of the emergency message, I flashed twrp again with odin, and been successful. If I tried to flash the AP image again, or CSC, it fails. And then I get the message back.
After flashing twrp, I'm stuck in a boot loop. Would need to restore system I think, but cannot seem to be able to do it with Odin.
Any possible way to recover my device?
Update: Turns out I must have made a mistake with the firmware I thought I had flashed, versus the one I was trying to flash and was failing. I downloaded the latest october firmware and it's currently flashing in odin!
This not be posted in development !
mchlbenner said:
This not be posted in development !
Click to expand...
Click to collapse
Sorry about that, I thought it was related to the topic. Obviously, you saw that I do not have a thousand posts around here, a wise thing to do would have been to suggest me where should I have posted this, and how can I move my thread around? Do I wait for a mod to move it himself?
pleclair said:
Here is what I did so far to get here.
First I followed the guide to root my phone, and to be honest, all was perfect. I had to restore stock rom cause my first few tries failed. But seems I flashed a rom for a different provider. It worked anyway, but I don't have my sim card in that phone, it's temporarily in another device.
I had a little issue in settings, where battery was coming up two times in the list. That bugged me, I wanted to restore the rom and see if a full restore would take care of this issue, but somehow, after I installed twrp and rooted my phone, I can no longer flash anything stock with odin, it fails.
If I try to flash the AP tar.md5 file, it fails when it gets to system. And then after rebooting, I see this message:
"An error has occurred while updating the device software. Use the emergency recovery function in the Smart Switch PC Software"
I tried installing smart switch and kies, and both software doesn't detect my device in download mode or twrp (obviously)...
So to get rid of the emergency message, I flashed twrp again with odin, and been successful. If I tried to flash the AP image again, or CSC, it fails. And then I get the message back.
After flashing twrp, I'm stuck in a boot loop. Would need to restore system I think, but cannot seem to be able to do it with Odin.
Any possible way to recover my device?
Click to expand...
Click to collapse
You forgot to flash all of them
BL, AP, CP, CSC
pleclair said:
Sorry about that, I thought it was related to the topic. Obviously, you saw that I do not have a thousand posts around here, a wise thing to do would have been to suggest me where should I have posted this, and how can I move my thread around? Do I wait for a mod to move it himself?
Click to expand...
Click to collapse
Just because you have a lot of post you don't post question in development section.
587.saboor said:
You forgot to flash all of them
BL, AP, CP, CSC
Click to expand...
Click to collapse
I did flashed all of them. But it always fails. No matter if I select only BL, AP, CP, CSC... or all of them. Almost seems like twrp is preventing write or something else does.
It fails after a few seconds in the process. Is there any kind of log generated by odin? If so, where can I find it? I don't see much information beside that it fails.
OEM unlock checked in dev options?
USB debuging checked? these were always the go to mischecks...
back when I had the galaxy a5 2017 520W canada unit I flashed a european rom to see if FM radio was going to work. it Worked, but I had the simular issue with battery showing up twice AND I ended up tripping knox while doing it. phone seemed to work fine other then that issue and the radio worked as well.
Flashed it back to 520W stock... later sold the phone... no issues. perhaps it was different with nougat
supertac said:
OEM unlock checked in dev options?
USB debuging checked? these were always the go to mischecks...
back when I had the galaxy a5 2017 520W canada unit I flashed a european rom to see if FM radio was going to work. it Worked, but I had the simular issue with battery showing up twice AND I ended up tripping knox while doing it. phone seemed to work fine other then that issue and the radio worked as well.
Flashed it back to 520W stock... later sold the phone... no issues. perhaps it was different with nougat
Click to expand...
Click to collapse
Yeah, I have those two checked. For some reasons, I was tired that night, and was actually trying to flash 7.1.1 firmware, while having already upgraded to 8.0. So I believe this operation wasn't getting thru because of that. I was tired, and picked the wrong folder, and flashed 7.1.1. Well, I was trying to flash, but it kept failing, but had a tiny bit done, enough to screw this up like this.
When I picked the right folder, 8.0, then it worked.
As for tripping knox, you probably tripped it while flashing twrp. I believe it trips it, haven't heard of a way to do it.
pleclair said:
Yeah, I have those two checked. For some reasons, I was tired that night, and was actually trying to flash 7.1.1 firmware, while having already upgraded to 8.0. So I believe this operation wasn't getting thru because of that. I was tired, and picked the wrong folder, and flashed 7.1.1. Well, I was trying to flash, but it kept failing, but had a tiny bit done, enough to screw this up like this.
When I picked the right folder, 8.0, then it worked.
As for tripping knox, you probably tripped it while flashing twrp. I believe it trips it, haven't heard of a way to do it.
Click to expand...
Click to collapse
nope. NEVER flashed twrp once on the A5- the european firmware tripped it on the 520W
desperately trying to un brick my note 5. I've been trying for weeks now to recover my phone after a rooting mishap had caused loss of imei and baseband. in the process of attempting to repair that issue I have managed to completely soft brick the damn thing. I have been to the deepest corners of google in search of this specific 4 file repair download and can not find anything that is free. I've even signed up for accounts on gsm flash and the like only to be disappointed that signing up wasn't enough to get the files I need... if anyone has a link or the files themselves I would be very thankful for there help. to be clear I can not flash standard stock rom through Odin. the process completes and the phone boots but than erases at 32 percent and will only boot to recovery with dm verity error or download mode. I've tried a few different official stock roms. I've tried flashing the one file home.tar as well as un packing and flashing boot, system, modem, cache neither of which have worked. I can't find a hidden image file to remove before flashing so unless I'm missing something im out of ideas.. the repair. firmware seems to be my last hope... also to hell out anyone trying to assist. I flashed a. efs file when trying to restore imei and that in turn re enabled frp lock.. so I believe both frp lock and oem lock are enabled. so any combination file or modified at all is out of the question... I believe it's repair or nothing. there are a few free 4 file repair downloads out there but they aren't the same number im not sure if there are any compatible enough that I could flash one of them and they work? so if any one knows of other models compatible. with the SM-N920TUVU4EQJ3 let me know so I can try to get this mess sorted out. I apologize if this has been asked somewhere els or if I'm in the wrong forum. but this seemed the most suited for my case. thank you to anyone who may be able to help
anybody?
is anyone able to help me out?
thatspideyguy said:
desperately trying to un brick my note 5. I've been trying for weeks now to recover my phone after a rooting mishap had caused loss of imei and baseband. in the process of attempting to repair that issue I have managed to completely soft brick the damn thing. I have been to the deepest corners of google in search of this specific 4 file repair download and can not find anything that is free. I've even signed up for accounts on gsm flash and the like only to be disappointed that signing up wasn't enough to get the files I need... if anyone has a link or the files themselves I would be very thankful for there help. to be clear I can not flash standard stock rom through Odin. the process completes and the phone boots but than erases at 32 percent and will only boot to recovery with dm verity error or download mode. I've tried a few different official stock roms. I've tried flashing the one file home.tar as well as un packing and flashing boot, system, modem, cache neither of which have worked. I can't find a hidden image file to remove before flashing so unless I'm missing something im out of ideas.. the repair. firmware seems to be my last hope... also to hell out anyone trying to assist. I flashed a. efs file when trying to restore imei and that in turn re enabled frp lock.. so I believe both frp lock and oem lock are enabled. so any combination file or modified at all is out of the question... I believe it's repair or nothing. there are a few free 4 file repair downloads out there but they aren't the same number im not sure if there are any compatible enough that I could flash one of them and they work? so if any one knows of other models compatible. with the SM-N920TUVU4EQJ3 let me know so I can try to get this mess sorted out. I apologize if this has been asked somewhere els or if I'm in the wrong forum. but this seemed the most suited for my case. thank you to anyone who may be able to help
Click to expand...
Click to collapse
thatspideyguy said:
is anyone able to help me out?
Click to expand...
Click to collapse
Hi I had the same issue with my note 5 SM-N920T I managed to fix it by downloading a pre rooted with SU rom from xda I also had the twrp custom bootloader installed first for some reason my pc still picked up my phone and I was still able to upload the rom to the twrp location on the device. having done that I was the able to copy the zip file over to my device and flash it.
When I had the rom installed I was then able to download the original android rom (android 5 in my case) from sam mobile they also had the most up-to-date android 7 rom as well for the device then it was just a case of using android repair to un root the bootloader and install the original android bootloader this was also on sam mobile.
Then make sure the phone has a full battery as flash the stock firmware as you would normally with odin and have the latest Samsung drivers installed on yore system or it will fail.
After the flash has taken place the first boot will take some time my note 5 took around 45 min's and then when fully back up and running I had to spend a good 2 hours reinstalling and updating all my software and OTA updates.