Related
I have been able to get into CWM Recovery v5.8.0.2 but there are no system files or any files on the phone, i can load new ROM's on the SD Card but every time i install it, it comes back with installation aborted, i have tried multiple different ROM's, any suggestion will be greatly appreciated. The phone does not boot any further
Are you sure youre not flashing a Nexus S 4G rom on a Nexus S. Or the opposite?
I am sure, i downloaded all the correct ROM's from CWM and am sure i have a Nexus S not 4G, it was rooted before and worked fine, i tried getting it back to stock and when it booted, it stopped on the boot ROM, from there i went through the procedure on loading CWM recovery and finally got back into recovery mode but from there i cannot flash anything and as mentioned, there are no file whatsoever on the phone, it is as if it was wiped clean.
Have you accidentally flashed a NS4G recovery by any chance? Try reflashing your recovery.
Also, any other errors listed?
I flashed using the CWM v5.8.0.2-touch on the Nexus S category, so am sure and triple checked and redid the flash a couple of times, its as if the new flash does not find any files to flash and i cannot see any files on the phone, there is only the update.zip file on there
Jpienaar2012 said:
I flashed using the CWM v5.8.0.2-touch on the Nexus S category, so am sure and triple checked and redid the flash a couple of times, its as if the new flash does not find any files to flash and i cannot see any files on the phone, there is only the update.zip file on there
Click to expand...
Click to collapse
try a different recovery, or the non touch cwm recovery.
I loaded v5.0.2.0 from CWM and still the same, it changes CWM but cannot load any new ROM's
Jpienaar2012 said:
I loaded v5.0.2.0 from CWM and still the same, it changes CWM but cannot load any new ROM's
Click to expand...
Click to collapse
dont load from there, flash a new recovery via fastboot.
I only downloaded the recovery file from CWM but loaded it through fastboot, but still the same result
Jpienaar2012 said:
I only downloaded the recovery file from CWM but loaded it through fastboot, but still the same result
Click to expand...
Click to collapse
download from somewhere else and try.
any suggestions on where else i could get it from?
Download stock fastboot.imgs for your specific device. Flash them all = stock and start over
i have also downloaded from nexushacks.com and same result
Sorry, but where can i get the stock files from?
Search Google. Go to official Google site with them. Can't recall the exact URL but it will come up. There is a thread on these forums as well with the links to factory images and instructions if you need them.
PSA. Stay away from nexusshacks. That guy is a tool.
Thanks, will have a look on what i can find
Ihave tried stock and various developers and still no luck, i tried fast boot update from terminal and get
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Any suggestions
Jpienaar2012 said:
Ihave tried stock and various developers and still no luck, i tried fast boot update from terminal and get
archive does not contain 'android-info.txt'
archive does not contain 'android-product.txt'
error: update package has no android-info.txt or android-product.txt
Any suggestions
Click to expand...
Click to collapse
Did you grab your image from here and follow the instructions to start the script?
https://developers.google.com/android/nexus/images
Thanks, this worked and my phone is back to normal again. Don't trust what other people say on the web cause most of the time they give you crap.
I have ran into a problem and came here for help. I was on Android 5.1.1 and I wanted to try omni and a slimsaber build of omni so I tried to flash with 2.8.7.0 and could not get it to boot, tried for days. So I wanted to try the recommended recovery, 2.8.6.0 and tried through fastboot, flashify and toolkits. And I am unable to change recovery. Fastboot flash results in a loop to the OnePlus Android logo but flashing 2.8.7.0 is a quick fix for that but it's the only recovery I can flash. I have never seen a phone not take a fastboot partiton flash. I have flashed back to stock.. Flashed OOS you name it I tried it. I know others have had this issue but never seen a fix posted. Anyone?
I have a .zip that can be flashed on TWRP v2.8.7.0, so as to get TWRP v2.8.6.0
I'll upload it if you want me to. Thank me later!
~noob (you gotta start from somewhere)
Download the img and when are you on the twrp, change zip to img and will appear the img and it will be possible apply it. Its really simple.
evertking said:
I have ran into a problem and came here for help. I was on Android 5.1.1 and I wanted to try omni and a slimsaber build of omni so I tried to flash with 2.8.7.0 and could not get it to boot, tried for days. So I wanted to try the recommended recovery, 2.8.6.0 and tried through fastboot, flashify and toolkits. And I am unable to change recovery. Fastboot flash results in a loop to the OnePlus Android logo but flashing 2.8.7.0 is a quick fix for that but it's the only recovery I can flash. I have never seen a phone not take a fastboot partiton flash. I have flashed back to stock.. Flashed OOS you name it I tried it. I know others have had this issue but never seen a fix posted. Anyone?
Click to expand...
Click to collapse
To change TWRP version, to upgrade or downgrade, you just have to download the Flashify app from PlayStore and let it do the job in about 10 seconds, without any issue :good:
Did anything work? I'm stuck with the same problem, except on 3.0.2.0 and downgrading out of the question I can't even make any other recovery work!!!
On the OnePlus One, was trying to flash Jgcaap's MM build.
There is no downgrading or upgrading like matters. You can flash any version of twrp via twrp, FIRST GO TO YOUR TWRP AND FLASH 2.8.6 OR 3.0.2 . BOTH HAS FLASH ANY ROMS WITHOUT PROBLEMS.
drmuruga said:
There is no downgrading or upgrading like matters. You can flash any version of twrp via twrp, FIRST GO TO YOUR TWRP AND FLASH 2.8.6 OR 3.0.2 . BOTH HAS FLASH ANY ROMS WITHOUT PROBLEMS.
Click to expand...
Click to collapse
I already tried. -.- Wouldn't ask if I didn't run out of options.
The flash doesn't work, instead my recovery disappears and I reboot to system directly. Facing problems gives you experience, man :| Not a n00b here.
I found a typical kinda work around by trying this and that. Gonna create another thread to ask, now.
Hey everyone, so I have from what I researched here is a "soft" bricked phone as my recovery mode (TWRP) and download mode works fine but no boot.
First let me say this is the Canadian version of the Note 5 SM-N920W8. I posted here because there is no forum for that version everything seems to be the same and posted under 920T version.
HISTORY OF THE PHONE:
It was a while ago that I rooted but let me describe to the best of my memory how my note 5 ended up in the state that it is in. So stock was lollipop 5.1.1. I flashed the skyhigh kernel which gave root access but had random reeboot issues which led me to flashing TWRP recovery so I could flash boot.img as an image file which did take away the random reeboot problem and removed that red error on startup "kernel is not SEANDROID enforcing". Life was good at this point! Everything worked great woth no issues. I greenified everything and underclocked the cpu with system tuner and used system app removed to manually all the bloatware as I didnt want to start using custom roms I stuck with the stock firmware. Part of the reason that I didnt want to use custom roms is because I started reading up on xposed framework, so I decided to flash it and give it a try. I read the xposed framework thread followed the download link to my version downloaded it and flashed with TWRP. Immediately after this was a bootloop.
TROUBLESHOOTING:
Unfortunately I had no backup in TWRP.. In a panic before researching I started flashing other kernels like arters kernel and I think space x whcih can be used on some note 5s.. which brought back that SEANDROID error message in the bootloop. I flashed the skyhigh kernel but flashing the boot.img didn't get rid of that error message again.
A friend of mine at work recommended that I just wipe everything and flash the stock firmware from sammobile.com with odin since I still have recovery mode then just re root. So I went into TWRP and wiped EVERYTHING. I think there was 4 or 5 boxes in twrp data wipe but I selected all the boxes. Now the phone doesn't even get the Samsung logo on boot or anything but download mode works so I flashed twrp again which loads up. I downloaded my version of the Samsung firmware which was about 1.6gb from sammobile.com. I open odin load the file that I extracted. A tar.md5 file which took longer than normal to load into the AP but I didn't change any settings or anything. Should I have? Because after I hit start it failed. I retried at least 3 times. Does this firmware contain all the AP CP and all the other boxes or do I need to find those separately? Should I just try a custom rom?
Im not sure what to do here I have a completely blank phone but twrp and download mode works so it recoverable right?
I read up on adb sideloader but didn't get too far.. is that worth trying for recovery in this case?
I also read a few threads on here for other samsung versions where they say to flash a PIT file with odin but they all say that it only works specifically for that phone and I couldn't find one for this version of the note 5.
I know the #1 rule here is to research before posting and Ive really made my best attempt to research on here and Google over the last few days but I really need my phone back. Any help is greatly appreciated.
re: phone won't boot
bloewen4 said:
Hey everyone, so I have from what I researched here is a "soft" bricked phone as my recovery mode (TWRP) and download mode works fine but no boot.
First let me say this is the Canadian version of the Note 5 SM-N920W8. I posted here because there is no forum for that version everything seems to be the same and posted under 920T version.
HISTORY OF THE PHONE:
It was a while ago that I rooted but let me describe to the best of my memory how my note 5 ended up in the state that it is in. So stock was lollipop 5.1.1. I flashed the skyhigh kernel which gave root access but had random reeboot issues which led me to flashing TWRP recovery so I could flash boot.img as an image file which did take away the random reeboot problem and removed that red error on startup "kernel is not SEANDROID enforcing". Life was good at this point! Everything worked great woth no issues. I greenified everything and underclocked the cpu with system tuner and used system app removed to manually all the bloatware as I didnt want to start using custom roms I stuck with the stock firmware. Part of the reason that I didnt want to use custom roms is because I started reading up on xposed framework, so I decided to flash it and give it a try. I read the xposed framework thread followed the download link to my version downloaded it and flashed with TWRP. Immediately after this was a bootloop.
TROUBLESHOOTING:
Unfortunately I had no backup in TWRP.. In a panic before researching I started flashing other kernels like arters kernel and I think space x whcih can be used on some note 5s.. which brought back that SEANDROID error message in the bootloop. I flashed the skyhigh kernel but flashing the boot.img didn't get rid of that error message again.
A friend of mine at work recommended that I just wipe everything and flash the stock firmware from sammobile.com with odin since I still have recovery mode then just re root. So I went into TWRP and wiped EVERYTHING. I think there was 4 or 5 boxes in twrp data wipe but I selected all the boxes. Now the phone doesn't even get the Samsung logo on boot or anything but download mode works so I flashed twrp again which loads up. I downloaded my version of the Samsung firmware which was about 1.6gb from sammobile.com. I open odin load the file that I extracted. A tar.md5 file which took longer than normal to load into the AP but I didn't change any settings or anything. Should I have? Because after I hit start it failed. I retried at least 3 times. Does this firmware contain all the AP CP and all the other boxes or do I need to find those separately? Should I just try a custom rom?
Im not sure what to do here I have a completely blank phone but twrp and download mode works so it recoverable right?
I read up on adb sideloader but didn't get too far.. is that worth trying for recovery in this case?
I also read a few threads on here for other samsung versions where they say to flash a PIT file with odin but they all say that it only works specifically for that phone and I couldn't find one for this version of the note 5.
I know the #1 rule here is to research before posting and Ive really made my best attempt to research on here and Google over the last few days but I really need my phone back. Any help is greatly appreciated.
Click to expand...
Click to collapse
If you have either a custom or stock rom installed or the official Samsung firmware installed
then it should be an easy fix, you must have flashed a incompatible kernel or perhaps you
deleted the kerned. (the phone will not boot without a kernel)
You need to find a compatible kernel and flash it using twrp recovery.
Here is a link you may want to try, it's for kernels for the Note 5 only:
http://forum.xda-developers.com/tmobile-galaxy-note5/orig-development
It might even be better if you were to Odin flash a fresh copy of your Note 5 specific
firmware using download mode, that's the surest way to get your phone working again.
Give it a try...
Good luck,
Have a great day!
Good luck!
Hi thanks for the reply! I did try that already unless flashing a stock firmware is different than putting it in AP as I flashed the kernel. Do I need to select some different optioms in odin since I data wiped everything and need all the necessary files to boot the phone? Oh and I did put the skyhigh kernel back on.
A friend of mine at work recommended that I just wipe everything and flash the stock firmware from sammobile.com with odin since I still have recovery mode then just re root. So I went into TWRP and wiped EVERYTHING. I think there was 4 or 5 boxes in twrp data wipe but I selected all the boxes. Now the phone doesn't even get the Samsung logo on boot or anything but download mode works so I flashed twrp again which loads up. I downloaded my version of the Samsung firmware which was about 1.6gb from sammobile.com. I open odin load the file that I extracted. A tar.md5 file which took longer than normal to load into the AP but I didn't change any settings or anything. Should I have? Because after I hit start it failed. I retried at least 3 times. Does this firmware contain all the AP CP and all the other boxes or do I need to find those separately? Should I just try a custom rom?
Click to expand...
Click to collapse
Unfortunately I had no backup in TWRP.. In a panic before researching I started flashing other kernels like arters kernel and I think space x whcih can be used on some note 5s.. which brought back that SEANDROID error message in the bootloop. I flashed the skyhigh kernel but flashing the boot.img didn't get rid of that error message again
Click to expand...
Click to collapse
re: not sure what you mean
bloewen4 said:
Hi thanks for the reply! I did try that already unless flashing a stock firmware is different than putting it in AP as I flashed the kernel. Do I need to select some different optioms in odin since I data wiped everything and need all the necessary files to boot the phone? Oh and I did put the skyhigh kernel back on.
Click to expand...
Click to collapse
Your best bet is to download the official Note 5 N920T odin flash firmware,
unzip it so you will end up with a TAR.MD5 file.
Then do a full wipe including system, data, cache, dalvik and last but not least
a factory reset in twrp recovery.
Once you do that your phone will be working properly again, flashing a kernel
or flashing firmware is the same process in odin. Use the AP slot.
And now I know what messed up your phone... it was as I posted before either
flashing the wrong kernel or the kernel got deleted who knows how.
That's all I can tell you except if you want the link to the official Samsung
N920T firmware here it is:
http://forum.xda-developers.com/tmo...t/rom-android-6-0-marshmallow-note-5-t3250812
The link also guides you thru the odin flashing process and other important things.
Good luck!
re: not sure what you mean
Quote:
Originally Posted by bloewen4
Hi thanks for the reply! I did try that already unless flashing a stock firmware is different than putting it in AP as I flashed the kernel. Do I need to select some different optioms in odin since I data wiped everything and need all the necessary files to boot the phone? Oh and I did put the skyhigh kernel back on.
Click to expand...
Click to collapse
I was researching some methods of flashing firmware to a completely wiped phone and read somewhere that there is a method to download all the files individually and put them into all the other sections in odin but I guess these tar.md5 files are a package of everything and one file is enough for a completely wiped phone? If all I need to k ow is to download that firmware unzip and flash in AP then awesome So longlong as they both have the same effect.
Your best bet is to download the official Note 5 N920T odin flash firmware,
unzip it so you will end up with a TAR.MD5 file.
Then do a full wipe including system, data, cache, dalvik and last but not least
a factory reset in twrp recovery.
Once you do that your phone will be working properly again, flashing a kernel
Click to expand...
Click to collapse
Just to clarify the order of this; first download that firmware via that link. 2nd wipe everything in twrp except for recovery so I can go back into twrp and factory reset in twrp? This alone will boot my phone before flashing the firmware? Or do I need to factory reset in twrp then flash that firmware in odin to get a boot? And is this custom firmware do I need to root again after I get boot?
Thanks for the link to that firmware going to be trying this right after work
bloewen4 said:
re: not sure what you mean
Quote:
Originally Posted by bloewen4
Hi thanks for the reply! I did try that already unless flashing a stock firmware is different than putting it in AP as I flashed the kernel. Do I need to select some different optioms in odin since I data wiped everything and need all the necessary files to boot the phone? Oh and I did put the skyhigh kernel back on.
I was researching some methods of flashing firmware to a completely wiped phone and read somewhere that there is a method to download all the files individually and put them into all the other sections in odin but I guess these tar.md5 files are a package of everything and one file is enough for a completely wiped phone? If all I need to k ow is to download that firmware unzip and flash in AP then awesome So longlong as they both have the same effect.
Your best bet is to download the official Note 5 N920T odin flash firmware,
unzip it so you will end up with a TAR.MD5 file.
Then do a full wipe including system, data, cache, dalvik and last but not least
a factory reset in twrp recovery.
Once you do that your phone will be working properly again, flashing a kernel
Just to clarify the order of this; first download that firmware via that link. 2nd wipe everything in twrp except for recovery so I can go back into twrp and factory reset in twrp? This alone will boot my phone before flashing the firmware? Or do I need to factory reset in twrp then flash that firmware in odin to get a boot? And is this custom firmware do I need to root again after I get boot?
Thanks for the link to that firmware going to be trying this right after work
Click to expand...
Click to collapse
Wait. You have a W8 variant. Odin won't flash a T variant on your W8 device, I don't believe. You need to download your carrier specific, hopefully 6.0.1 version, of the firmware for your specific carrier version, and flash that in the latest 3.10.7 version of odin.
---------- Post added at 09:21 PM ---------- Previous post was at 09:08 PM ----------
bloewen4 said:
re: not sure what you mean
Quote:
Originally Posted by bloewen4
Hi thanks for the reply! I did try that already unless flashing a stock firmware is different than putting it in AP as I flashed the kernel. Do I need to select some different optioms in odin since I data wiped everything and need all the necessary files to boot the phone? Oh and I did put the skyhigh kernel back on.
I was researching some methods of flashing firmware to a completely wiped phone and read somewhere that there is a method to download all the files individually and put them into all the other sections in odin but I guess these tar.md5 files are a package of everything and one file is enough for a completely wiped phone? If all I need to k ow is to download that firmware unzip and flash in AP then awesome So longlong as they both have the same effect.
Your best bet is to download the official Note 5 N920T odin flash firmware,
unzip it so you will end up with a TAR.MD5 file.
Then do a full wipe including system, data, cache, dalvik and last but not least
a factory reset in twrp recovery.
Once you do that your phone will be working properly again, flashing a kernel
Just to clarify the order of this; first download that firmware via that link. 2nd wipe everything in twrp except for recovery so I can go back into twrp and factory reset in twrp? This alone will boot my phone before flashing the firmware? Or do I need to factory reset in twrp then flash that firmware in odin to get a boot? And is this custom firmware do I need to root again after I get boot?
Thanks for the link to that firmware going to be trying this right after work
Click to expand...
Click to collapse
What carrier are you on? Go to sammobile and find out exactly what firmware is the latest for your variant on your carrier, for us T variants it's dpd1, but yours will be different, and sammobile is slow so if you can find a mirror somewhere for the stock firmware do that, download it...should be a tar.md5....if you get an error loading it you can often remove the .md5 from the extension...now first reboot recovery and you only need to wipe art/dalvik cache, system, data, cache, and if you want to internal storage but I normally don't...if you wipe efs and everything else you'll be sorry because only thing that will restore it is a full factory odin firmware flash...which is exactly what we're doing...so wipe those partitions then reboot download mode....launch odin and load your downloaded image into the AP slot. Make sure it's at least 3.10.7 version of Odin...when you connect the usb after rebooting to download mode you should see a green/blue box with COM:x (where x is a com port number on your pc) and it should say added...now flash it and wait until it finishes, it'll reboot maybe even a couple times, but it'll eventually make it to the setup screen- from here you can continue stock or flash twrp in odin then recovery flash a rooted kernel for stock rooted or continue with a custom rom, there's a fix in the note 5 gen section for making t/w8 devices work with call audio on intl roms and there's some stock Deodexed stuff at this point and certainly tekhd's mm rom...so from there the choices are yours...but your device is fine you just NEED to flash the correct stock firmware for your variant and use the latest version of odin with a factory usb cable and latest usb drivers from Samsung on your pc when you do it...you'll find links to all this stuff in most of the guides that are abundantly available...
Wait. You have a W8 variant. Odin won't flash a T variant on your W8 device, I don't believe. You need to download your carrier specific, hopefully 6.0.1 version, of the firmware for your specific carrier version, and flash that in the latest 3.10.7 version of odin.
Click to expand...
Click to collapse
I realize I have a W8 and hes providing the firmware for a T. I rooted with a kernel that was for a T version and everything worked fine. I researched rooting note 5 SM-N920W8 and they said do everything the same for the T version because theyre basically identical and isnt much info on the w8 version. So far Ive had no issues flashing everything designed for the T version on my W8. Actually Ive only tried flashing stock w8 firmware from.sammobile.com and got a fail in odin so now Ill try the version MisterJunkie provided me with for the T version unless considering all this you think I should still try a different firmware all together for the W8?
Misterjunky said:
Your best bet is to download the official Note 5 N920T odin flash firmware,
unzip it so you will end up with a TAR.MD5 file.
Then do a full wipe including system, data, cache, dalvik and last but not least
a factory reset in twrp recovery.
Once you do that your phone will be working properly again, flashing a kernel
or flashing firmware is the same process in odin. Use the AP slot.
And now I know what messed up your phone... it was as I posted before either
flashing the wrong kernel or the kernel got deleted who knows how.
That's all I can tell you except if you want the link to the official Samsung
N920T firmware here it is:
http://forum.xda-developers.com/tmo...t/rom-android-6-0-marshmallow-note-5-t3250812
The link also guides you thru the odin flashing process and other important things.
Good luck!
Click to expand...
Click to collapse
Bud, that's not the official tmo pd1 firmware, and I'm not sure if the leaked (alright it would likely run) would be the best here...plus he scares me when he says he cleared EVERYTHING cuz I'm thinking back to exactly how much twrp will wipe, but it's a lot so I fear he's going to need some partitions restored that are only going to come from a full pit file mapping...I don't believe official pd1 would flash in odin, nor would I recommend doing so- I would locate the most recently official firmware to ensure all partitions are restored, then if he doesn't have official mm support he can look into the leak, but if he had official for his variant and carrier that's his best bet to ensure 100% fix and give him a solid foundation to start from if he wants to root, rom, mod, etc
Not to discount your advice, I'd just hate to see him in a worse place than he is...which he's not even bricked YET...but he's starts screwing with wiping efs or messaging with csc stuff from different variants and he could back himself into a corner...
What carrier are you on? Go to sammobile and find out exactly what firmware is the latest for your variant on your carrier, for us T variants it's dpd1, but yours will be different, and sammobile is slow so if you can find a mirror somewhere for the stock firmware do that, download it...should be a tar.md5....if you get an error loading it you can often remove the .md5 from the extension...now first reboot recovery and you only need to wipe art/dalvik cache, system, data, cache, and if you want to internal storage but I normally don't...if you wipe efs and everything else you'll be sorry because only thing that will restore it is a full factory odin firmware flash...which is exactly what we're doing...so wipe those partitions then reboot download mode....launch odin and load your downloaded image into the AP slot. Make sure it's at least 3.10.7 version of Odin...when you connect the usb after rebooting to download mode you should see a green/blue box with COM:x (where x is a com port number on your pc) and it should say added...now flash it and wait until it finishes, it'll reboot maybe even a couple times, but it'll eventually make it to the setup screen- from here you can continue stock or flash twrp in odin then recovery flash a rooted kernel for stock rooted or continue with a custom rom, there's a fix in the note 5 gen section for making t/w8 devices work with call audio on intl roms and there's some stock Deodexed stuff at this point and certainly tekhd's mm rom...so from there the choices are yours...but your device is fine you just NEED to flash the correct stock firmware for your variant and use the latest version of odin with a factory usb cable and latest usb drivers from Samsung on your pc when you do it...you'll find links to all this stuff in most of the guides that are abundantly available...
Click to expand...
Click to collapse
My carrier is Rogers. I did goto sammobile.com already and downloaded and flashed what I thought was the current stock firmware for my 920w8, but I flashed without wiping all data as previously stated. Maybe doing this will allow my firmware to flash? Will try when Im home from work. Will also post the link from sammobile.com for the exact firmware I download just to verify ots the right one.
Yeah I literally wiped everything I checked all the boxes and I remember having to manually type y e s to proceed so yeah pretty serious wipe lol.
I have the latest version of odin 3.10.7 and tried installing drivers on my pc said theyre already installed.
When I connect my phone to usb in download mode it says com:4
I thought also that just flashing the stock firmware would be the solution since I get download mode and twrp I just have a blank phone but as I said I did get the stock firmware from sammobile.com and try but it failed. Maybe I grabbed the wrong one but it looked pretty straightforward. Maybe with MM coming out Wednesday for rogers note 5 Im downloading the wrong version.
Im worried like you wrote earlier that I deleted too much with twrp if I needing mapping partitions and PIT files I will need some serious help that stuff is beyond me.
Go to sammobile and find out exactly what firmware is the latest for your variant on your carrier, for us T variants it's dpd1, but yours will be different, and sammobile is slow so if you can find a mirror somewhere for the stock firmware do that, download it...should be a tar.md5....if you get an error loading it you can often remove the .md5 from the extension...now first reboot recovery and you only need to wipe art/dalvik cache, system, data, cache, and if you want to internal storage but I normally don't...if you wipe efs and everything else you'll be sorry because only thing that will restore it is a full factory odin firmware flash...which is exactly what we're doing...so wipe those partitions then reboot download mode....launch odin and load your downloaded image into the AP slot. Make sure it's at least 3.10.7 version of Odin...when you connect the usb after rebooting to download mode you should see a green/blue box with COM:x (where x is a com port number on your pc) and it should say added...now flash it and wait until it finishes, it'll reboot maybe even a couple times, but it'll eventually make it to the setup screen- from here you can continue stock or flash twrp in odin then recovery flash a rooted kernel for stock rooted or continue with a custom rom
Click to expand...
Click to collapse
Goodmorning, as I mentioned I would try this right after work. Heres what I did.. I verified that I had the 3.10.7 version of odin which I do, checked drivers on pc which I have. I re downloaded the firmware from here http://www.sammobile.com/firmwares/database/SM-N920W8/ Its was the Canadian Rogers version 5.1.1 near the bottom as mm isnt out for rogers yet.. Oh and I checked my cable ot connected another device to my PC.. so after all this I went into twrp wiped everything you mentioned. After that I was looking for the factory reset option in twrp but couldn't find anywhere only restore which I have no rom backups made. Do I need this step?
Went into download mode pressed vol up.. opened odin 3.10.7. I did notice a change after wiping. Its now says com:6 instead of com:4 if that means anything.. I loaded the firmware into AP it took a while to load but it did without errors. Flashed and failed If you need I can copy the error message from odin in here tonight.
Do you think I need to remap partitions as you said earlier? Getting PIT files? Im lost here... appreciate any help
Still with a blank phone, any ideas?
Or if anyone could direct me to another thread that might be useful for re mapping partitions?
Have you tried flashing twrp again in Odin?
I hit too many buttons before when wiping. It even erased my recovery.
Once I had recovery again I could Odin flash the official firmware.
Could try Philz recovery as well.
Sent from my SM-N920T using XDA-Developers mobile app
Yeah I did try that heres the link where I got the firmware and yeah twrp is on there.
Goodmorning, as I mentioned I would try this right after work. Heres what I did.. I verified that I had the 3.10.7 version of odin which I do, checked drivers on pc which I have. I re downloaded the firmware from here http://www.sammobile.com/firmwares/database/SM-N920W8/ Its was the Canadian Rogers version 5.1.1 near the bottom as mm isnt out for rogers yet.. Oh and I checked my cable ot connected another device to my PC.. so after all this I went into twrp wiped everything you mentioned. After that I was looking for the factory reset option in twrp but couldn't find anywhere only restore which I have no rom backups made. Do I need this step?
Went into download mode pressed vol up.. opened odin 3.10.7. I did notice a change after wiping. Its now says com:6 instead of com:4 if that means anything.. I loaded the firmware into AP it took a while to load but it did without errors. Flashed and failed If you need I can copy the error message from odin in here tonight.
Click to expand...
Click to collapse
bloewen4 said:
Yeah I did try that heres the link where I got the firmware and yeah twrp is on there.
Click to expand...
Click to collapse
Since you have twrp on the phone.. Tap to create a backup even if there's no system on it so that you can at least make it create the folder.. Try using adb to push a ROM and kernel to the phone so you can use twrp to flash it. If you can get into the phones storage using Windows then just drop a ROM and kernel for your device in the folder and then use twrp to flash.
By the way.. Use the SkyHigh kernel.
Follow the directions to a T!!
http://forum.xda-developers.com/note5/orig-development/kernel-skyhigh-tw-6-0-1-kernel-t3321646
If you can get into the phones storage using Windows then just drop a ROM and kernel for your device in the folder and then use twrp to flash.
Click to expand...
Click to collapse
I did try immediately to connect with Windows to my phone so I could try flashing stock firmware with twrp but its currently not allowing me access to view storage on Windows though it does connect with odin saying com:6.
Since you have twrp on the phone.. Tap to create a backup even if there's no system on it so that you can at least make it create the folder..
Click to expand...
Click to collapse
I will do this as soon as I am home from work. Will this perhaps allow access with Windows and/or adb sideloader?
Try using adb to push a ROM and kernel to the phone so you can use twrp to flash it.
Click to expand...
Click to collapse
I will be researching how to do this. Have you any threads to learn adb? So basically this will allow me to put ROMS or other files into the internal memory?
By the way.. Use the SkyHigh kernel.
Follow the directions to a T!!
http://forum.xda-developers.com/note...ernel-t3321646
Click to expand...
Click to collapse
Is this the right kernel for SM-N920W8?
* SAME kernel for ALL supported variant !!
** If other party cannot hear voice when on speaker phone ** Then read Post #636
SM-N920 C / CD / G / i [ v3.2 ]
SM-N9200_HK [ v3.2 ]
Click to expand...
Click to collapse
Also Marshmellow isnt out officially for SM-N920W8 so Ill need a kernel for lollipop 5.1.1 unless you suggest to wait for marshmellow then try a mm kernel?
Thanks for helping!
How about this adb sideloader does anyone think that will work to load the firmware? If so any good threads to guode me?
What did you end up doing? I have a similar problem except no recovery mode, just download mode for Odin.
bloewen4 said:
Goodmorning, as I mentioned I would try this right after work. Heres what I did.. I verified that I had the 3.10.7 version of odin which I do, checked drivers on pc which I have. I re downloaded the firmware from here http://www.sammobile.com/firmwares/database/SM-N920W8/ Its was the Canadian Rogers version 5.1.1 near the bottom as mm isnt out for rogers yet.. Oh and I checked my cable ot connected another device to my PC.. so after all this I went into twrp wiped everything you mentioned. After that I was looking for the factory reset option in twrp but couldn't find anywhere only restore which I have no rom backups made. Do I need this step?
Went into download mode pressed vol up.. opened odin 3.10.7. I did notice a change after wiping. Its now says com:6 instead of com:4 if that means anything.. I loaded the firmware into AP it took a while to load but it did without errors. Flashed and failed If you need I can copy the error message from odin in here tonight.
Do you think I need to remap partitions as you said earlier? Getting PIT files? Im lost here... appreciate any help
Click to expand...
Click to collapse
Where did you get your firmware from?
Why oh why did I bother reading through this entire thread, with intentions to help OP. Lol I didnt realize the date till the last post.
Hello guys,
I installed cm-13 successfully and it was operating fine until yesterday. Today I tried to install a theme or something and it hung. So i just felt like doing a factory reset and I did it through my cwm recovery. But before that i made a backup, then i did the reset, then i did the restore...ever since then i havent been able to open the OS...it gets stuck on the samsung GALAXY Tab2 10.1 screen. I can however access the cwm recovery. I did infact try to unzip the cm-13 that i had previously used, and it doesnt work...
Please help guys!
I am pretty new to this and i feel like i cant figure out what to do next.
Is there a way to maybe restart the whole process, like get rid of the cm-13 that is already installed and redo the whole thing again?
Kindly help guys, i was really enjoying the cm experience and i messed it up :/
killermara said:
Is there a way to maybe restart the whole process, like get rid of the cm-13 that is already installed and redo the whole thing again?
Kindly help guys, i was really enjoying the cm experience and i messed it up :/
Click to expand...
Click to collapse
you did a backup before factory reset, then you restored the same data after reset. this hardly changed anything. the reason it didn't boot, is that The problem lies at the system partition, you should wipe system partition, data partition as well and flash the same cm-13 zip again along with gapps, if you had.
now let the system start. it should boot up with a clean installation. you can then try to advance restore and chose only data partition.
later just switch to twrp recovery by Android-Andi
HELP!
billysam said:
you did a backup before factory reset, then you restored the same data after reset. this hardly changed anything. the reason it didn't boot, is that The problem lies at the system partition, you should wipe system partition, data partition as well and flash the same cm-13 zip again along with gapps, if you had.
now let the system start. it should boot up with a clean installation. you can then try to advance restore and chose only data partition.
later just switch to twrp recovery by Android-Andi
Click to expand...
Click to collapse
Hello, actually I did exactly that, i wiped system partition and all of that...then i did try with cwm, and it didnt work, what is happening is that i select the option to flash the ROM, then the screen goes blank for a second and comes back to the home screen of the cwm recovery. So basically i selected the zip and nothing happened! I then tried flashing using twrp and the problem now was that there was the "no md5 file found" message and the installation would not stop, it would go on for too long, like some sort of loop. I then switched back to cwm and tried again and it still doesnt seem to work...kindly advice on what to do next
killermara said:
Hello, actually I did exactly that, i wiped system partition and all of that...then i did try with cwm, and it didnt work, what is happening is that i select the option to flash the ROM, then the screen goes blank for a second and comes back to the home screen of the cwm recovery. So basically i selected the zip and nothing happened! I then tried flashing using twrp and the problem now was that there was the "no md5 file found" message and the installation would not stop, it would go on for too long, like some sort of loop. I then switched back to cwm and tried again and it still doesnt seem to work...kindly advice on what to do next
Click to expand...
Click to collapse
first thing check if you have updated to last official stock jellybean rom prior to cm13 upgrade.
this thread will help you to update your bootloader to jb from ics. if you have a jb bootloader already. you can skip this.
forum.xda-developers.com/showthread.php?t=2642005
next thing you should get twrp 3.0.2.8
https://www.androidfilehost.com/?w=files&flid=48848&sort_by=date&sort_dir=DESC
after wiping, restart recovery, then flash the Rom zip
it takes time with the new CM13 builds to complete installation. some earlier twrp recoveries had issues(3.0.0.1 and 0.2, not sure right now, try latest only). cwm is not supported and twrp is the only preferred recovery by the Rom developers to flash the newer roms.
remember p5100 tab is called espresso3g now, since development has been unified. you need files marked as espresso3g for your p5100.
I don't which files are you using, development has changed so confirm the files that you're using are for unified builds and not device specific.
billysam said:
first thing check if you have updated to last official stock jellybean rom prior to cm13 upgrade.
this thread will help you to update your bootloader to jb from ics. if you have a jb bootloader already. you can skip this.
forum.xda-developers.com/showthread.php?t=2642005
next thing you should get twrp 3.0.2.8
https://www.androidfilehost.com/?w=files&flid=48848&sort_by=date&sort_dir=DESC
after wiping, restart recovery, then flash the Rom zip
it takes time with the new CM13 builds to complete installation. some earlier twrp recoveries had issues(3.0.0.1 and 0.2, not sure right now, try latest only). cwm is not supported and twrp is the only preferred recovery by the Rom developers to flash the newer roms.
remember p5100 tab is called espresso3g now, since development has been unified. you need files marked as espresso3g for your p5100.
I don't which files are you using, development has changed so confirm the files that you're using are for unified builds and not device specific.
Click to expand...
Click to collapse
I followed all the steps that you suggested, and the thread suggested.
I installed custom recovery, then I updated the bootloader.
Then i flashed the new twrp, which is alot more easier to operated compared to the cwm .
then i wiped , restarted recovery, then flashed the rom,
the exact same thing that was previously happening with the cwm happened : I tapped on the rom, then a blank screen appeared and it went back to the main menu of the twrp...
The ROM i am using is: cm-13.0-20160220-1347-UNOFFICIAL-p5100.zip
i also tried using the ROM i got from get.cm : cm-11-20160822-NIGHTLY-p5100.zip
Okay so i played a slow mo video to see what the screen says before it goes back to the welcome screen:
Updating partition details. . .
. . . done
Full SElinux support is present.
MTP Enabled
Then after this pops up, it goes back to the main menu of the twrp.
What if i just reinstall the stock OS then do the whole process of getting cyanogenmod again from rooting onwards?
Kindly assist!!
killermara said:
I followed all the steps that you suggested, and the thread suggested.
I installed custom recovery, then I updated the bootloader.
Then i flashed the new twrp, which is alot more easier to operated compared to the cwm .
then i wiped , restarted recovery, then flashed the rom,
the exact same thing that was previously happening with the cwm happened : I tapped on the rom, then a blank screen appeared and it went back to the main menu of the twrp...
The ROM i am using is: cm-13.0-20160220-1347-UNOFFICIAL-p5100.zip
i also tried using the ROM i got from get.cm : cm-11-20160822-NIGHTLY-p5100.zip
Okay so i played a slow mo video to see what the screen says before it goes back to the welcome screen:
Updating partition details. . .
. . . done
Full SElinux support is present.
MTP Enabled
Then after this pops up, it goes back to the main menu of the twrp.
What if i just reinstall the stock OS then do the whole process of getting cyanogenmod again from rooting onwards?
Kindly assist!!
Click to expand...
Click to collapse
OKAY! So i have had some progress in the situation i got myself into! Now i just changed the sd card and tried to flash the ROM, so it didnt successfully flash, it says:
Zip file is corrupt!
Error installing zip file ..*the directory of the ROM*
This doesnt make sense though because i used the exact same ROM earlier and it worked, i used it for a whole day and it was fine...
killermara said:
OKAY! So i have had some progress in the situation i got myself into! Now i just changed the sd card and tried to flash the ROM, so it didnt successfully flash, it says:
Zip file is corrupt!
Error installing zip file ..*the directory of the ROM*
This doesnt make sense though because i used the exact same ROM earlier and it worked, i used it for a whole day and it was fine...
Click to expand...
Click to collapse
do what @billysam said.
dont use device specific stuff. the latest twrp will only work with unified builds. for your device you need espresso3g builds.
you will find the latest roms on android-andis github site http://andi34.github.io/index.html
killermara said:
OKAY! So i have had some progress in the situation i got myself into! Now i just changed the sd card and tried to flash the ROM, so it didnt successfully flash, it says:
Zip file is corrupt!
Error installing zip file ..*the directory of the ROM*
This doesnt make sense though because i used the exact same ROM earlier and it worked, i used it for a whole day and it was fine...
Click to expand...
Click to collapse
you're using device specific Rom build, cm13.0 unofficial p5100, the latest twrp recovery you have, is a unfied espresso3g one.
latest roms, are build upon espresso3g for p5100,p3100 and espressowifi for p5110,p5113 p3113.
use latest cm13 rom zip, marked espresso3g.
there are device specific roms and recovery, which developers have stopped working on, your issue is because of this. get unified recovery and rom.
billysam said:
you're using device specific Rom build, cm13.0 unofficial p5100, the latest twrp recovery you have, is a unfied espresso3g one.
latest roms, are build upon espresso3g for p5100,p3100 and espressowifi for p5110,p5113 p3113.
use latest cm13 rom zip, marked espresso3g.
there are device specific roms and recovery, which developers have stopped working on, your issue is because of this. get unified recovery and rom.
Click to expand...
Click to collapse
Yea i thought so too, thats why i downloaded the cm-13.0-20161117-NIGHTLY-espresso3g.zip, then i wiped and tried to flash this rom, this also gave me the same error,
i also noticed that before the lines
Zip file is corrupt
there was:
Checking for MD5 file. . .
Skipping MD5 check: no MD5 file found.
killermara said:
Yea i thought so too, thats why i downloaded the cm-13.0-20161117-NIGHTLY-espresso3g.zip, then i wiped and tried to flash this rom, this also gave me the same error,
i also noticed that before the lines
Zip file is corrupt
there was:
Checking for MD5 file. . .
Skipping MD5 check: no MD5 file found.
Click to expand...
Click to collapse
maybe the zip got corrupted, checked your pc with anti-virus? are you downloading the zip file from androidfilehost of android-andi? or some other source? checked your sd card as well?
Hello guys,
I have a p5113 tablet that i have been having trouble with. I have tried flashing like 5 different roms and they all boot loop. I think its because I am using an old recovery (Device Specific TWRP 3.0.0-0) the problem is only the old recoveries are working for me. When i flash the latest common TWRP (3.0.3-0) Wiping gets stuck at updating partition details, it wont install any roms it stays at "detected filesystem ext4", and if I try to reset the tablet through TWRP menu it wont do anything. When I use the old recoveries it flashes and wipes fine. When i flash stock rom through odin, the system works fine. I have tried different versions of the latest twrp but to no avail. Thank you in advance for your help.
EDIT: I finally have a custom rom working on this tablet, it is Dhollmen stock 4.2.2 with GT-P5110_PhilZ-Touch-Recovery_6.59.2. recovery, device specific TWRP 3.0.0-0 would give me error 7. Im very happy but I would like to get Marshmallow on this tablet if anyone can help with that.
Install the 3.0.3-0 common TWRP, then try to format data (Wipe ->Format Data-> type yes). Reboot recovery once and then perform a wipe of all partitions (Wipe->Advanced Wipe-> select everything). If you get stuck at "updating partition details..." just wait. It could take as long as five minutes some times to get unstuck.
This is the link for the thread of Slim6, the mm rom I recommend by Andi:
https://forum.xda-developers.com/galaxy-tab-2/galaxy-tab-2-unified/rom-slim6-t3414798/page1
And this is an aosp mm rom also by Andi, try it if above fails
http://builds.unlegacy-android.org/aosp-6.0
Flash both with TWRP 3.0.3-0
If problems continue, post the recovery log (you can find it after reboot at /cache/recovery/ )
landetta said:
Hello guys,
I have a p5113 tablet that i have been having trouble with. I have tried flashing like 5 different roms and they all boot loop. I think its because I am using an old recovery (Device Specific TWRP 3.0.0-0) the problem is only the old recoveries are working for me. When i flash the latest common TWRP (3.0.3-0) Wiping gets stuck at updating partition details, it wont install any roms it stays at "detected filesystem ext4", and if I try to reset the tablet through TWRP menu it wont do anything. When I use the old recoveries it flashes and wipes fine. When i flash stock rom through odin, the system works fine. I have tried different versions of the latest twrp but to no avail. Thank you in advance for your help.
EDIT: I finally have a custom rom working on this tablet, it is Dhollmen stock 4.2.2 with GT-P5110_PhilZ-Touch-Recovery_6.59.2. recovery, device specific TWRP 3.0.0-0 would give me error 7. Im very happy but I would like to get Marshmallow on this tablet if anyone can help with that.
Click to expand...
Click to collapse
have you used the twrp on the http://andi34.github.io/ website? and roms compiled before 3/22/16 dont flash with common twrp when I updated twrp I had downloaded the zip and went into twrp to flash it I havent used a pc at all to install twrp and root . so I just put the zip on my sd card and it updated it did you update twrp with odin?
Thank you for your reply,
Yes I used the recoveries from Android Andi, and yes I have installed recoveries in zip form through recovery and Odin. Unfortunately neither have worked. I did use the latest recoveries when I tried to install the newer roms but it just gets stuck, I can't even make nandroid backups it also gets stuck with the newer recoveries.
Edit:
@ john99ap Sorry i just got home, I tried what you said but it just got stuck at both wipes, I waited 10 mins but a no-go. I found the logs, I couldn't paste them in here because it exceeded character length so I put it in pastebin. I didn't know which log to use so I am giving you the ones that I think are more relevant
Log:
pastebin/gpWgBEm7
Last_log:
pastebin/12uLYgwS
Last_log.10
pastebin/asePpLBa
Thank you guys again for your help!
landetta said:
Log:
pastebin/gpWgBEm7
Last_log:
pastebin/12uLYgwS
Last_log.10
pastebin/asePpLBa
Thank you guys again for your help!
Click to expand...
Click to collapse
I can't find anything in these logs
I need the log in which you try to install the zip file.
Try this:
-Install TWRP 3.0.3-0 (if it's not already there)
-Reboot and delete all recovery logs you can find
-Install the zip without doing anything else before or after so that the log is as clean as possible
-Post any log you find
PS: you could upload logs in your reply by hitting the button with a stapler on the bottom left corner
Thanks for your reply, sorry about the old logs, here are the new ones like you requested. Hopefully you find something in these new ones. Thanks again for all your help BTW I don't have any staples in my advanced reply so I had to use Pastebin again sorry. I think its because of my low post count.
pastebin/UcntGLTZ
pastebin/Fq8V7WUf
PS: Not even the reboot button works on 3.0.3-0.
Sorry but I can't find anything in these logs either. Maybe it's my fault since I 'm not an expert
At your first post you said device specific twrp gives you error 7. This is caused by a safety check in which your recovery checks if your device is compatible with the rom. In your case, it must be a mistake of the recovery (I had the same issue with my p3110 device specific twrp). So you could just remove the safety check.
Here's how to do it:
- Go to the zip you want to install and find the file /META-INF/com/google/android/updater-script
-Edit it with a text editor and remove the first line (it begins with asserts and ends at the first semicolon)
-Install the zip
Good luck!
john99ap said:
Sorry but I can't find anything in these logs either. Maybe it's my fault since I 'm not an expert
At your first post you said device specific twrp gives you error 7. This is caused by a safety check in which your recovery checks if your device is compatible with the rom. In your case, it must be a mistake of the recovery (I had the same issue with my p3110 device specific twrp). So you could just remove the safety check.
Here's how to do it:
- Go to the zip you want to install and find the file /META-INF/com/google/android/updater-script
-Edit it with a text editor and remove the first line (it begins with asserts and ends at the first semicolon)
-Install the zip
Good luck!
Click to expand...
Click to collapse
Awe thanks anyways dude, I really appreciate you trying. One last thing, on Andi's website he say that device specific 3.0.0-0 recovery should work to flash the latest roms. If anyone can confirm this maybe I can get the new roms working on it. Thanks again for all your help john99ap :good: