Related
Hi all, I was on AKOP's milestone ROM before trying to flash their newest one. I did not do anything to the kernel or anything by the way.
I'm using ClockworkMod Recovery v6.0.2.7 and I rebooted into recovery and flashed super dark side wipe and then JB-MR1 and then gapps.
I went through the entire start up process with inputting your information and then finally I got into the actual home screen. I clicked around to see how the UI looked and then decided to reboot through the menu.
It was in the rebooting animation icon for at least 30 min before I decided to pull the battery. I want to wipe and start again but my cwm recovery isn't installing anything.
EDIT: The phone still works as I can boot into the phone and use it. I'm trying to reboot now: power button hold>reboot, but its taking ages still...need help on this reboot thanks
Any help here?
EDIT 2: Pretty much phone is "functional" but any method of trying to reboot or reboot into recovery fails
Thanks all!
Check the Md5 hash to make sure it is a good download.
Otherwise it sounds like it is CWM that can be causing issues.
Which version of gapps are you flashing?
8Fishes said:
Check the Md5 hash to make sure it is a good download.
Otherwise it sounds like it is CWM that can be causing issues.
Which version of gapps are you flashing?
Click to expand...
Click to collapse
Checked the Md5 with an app and it matches up perfectly with akop's main website.
I'm running 6.0.2.8 cwm. Is it even possible that its cwm? I used the same version to flash AKOPs new ROM.
and im flashing gapps-jb-20121212-signed.zip
Does it have anything to do with my kernel?
You aren't supposed to use super wipe with cwm 6. That is probably your problem.
meekrawb said:
You aren't supposed to use super wipe with cwm 6. That is probably your problem.
Click to expand...
Click to collapse
Thanks so much for pinpointing the problem! Is there a fix to this?
And is this the recommended method of flashing? (Taken from http://forum.xda-developers.com/showthread.php?t=1926754):
1. Wipe factory data/reset
2. Wipe cache
3. Go into mounts and storage
4. Format /system
5. Format /data
6. Format /cache
7. Enter advanced
8. Wipe dalvik
9. Flash ROM then gapps
10. Reboot and let the ROM settle for 5-10 minutes if flashing TW ROMs, this step is unnecessary for AOSP based ROMs.
11. (Optional) if flashing a new radio flash AFTER the ROM has been initially booted for the first time. No wipes are necessary when flashing a new radio but it HAS to be flashed after the ROM is loaded and settled in. Flashing a radio first and then a ROM has caused issues like the phone not even recognizing there is a network for it. ( phone remains in emergency mode )
Edit:
Pretty sure my phone is bricked now... in a continuous boot up loop... BUT i can still access recovery
Ostyrion said:
Thanks so much for pinpointing the problem! Is there a fix to this?
Edit:
Pretty sure my phone is bricked now... in a continuous boot up loop... BUT i can still access recovery
Click to expand...
Click to collapse
Yes, those are the proper flashing instructions for CWM6.
It sounds like you have a soft brick. I think your best bet is to Odin back to stock. Have a look here:
http://forum.xda-developers.com/showthread.php?t=1858435
Good luck.
meekrawb said:
Yes, those are the proper flashing instructions for CWM6.
It sounds like you have a soft brick. I think your best bet is to Odin back to stock. Have a look here:
http://forum.xda-developers.com/showthread.php?t=1858435
Good luck.
Click to expand...
Click to collapse
You sir are a saving grace!
I'll try this at once!!
I have 2 questions though.
1. in regard to kernels. Do i need to do anything (aka change my kernel?) Or is the stock kernel suitable for 4.2.1?
2. If i cant boot into my phone to get to my SD card, how do i download and put files onto my phone?
Ostyrion said:
You sir are a saving grace!
I'll try this at once!!
I have 2 questions though.
1. in regard to kernels. Do i need to do anything (aka change my kernel?) Or is the stock kernel suitable for 4.2.1?
2. If i cant boot into my phone to get to my SD card, how do i download and put files onto my phone?
Click to expand...
Click to collapse
Stock kernel is just fine.
Odin will flash the stock OS to your phone from the computer. Make sure to read the Odin directions a few times before trying it because it could hard brick if something goes wrong.
meekrawb said:
Stock kernel is just fine.
Odin will flash the stock OS to your phone from the computer. Make sure to read the Odin directions a few times before trying it because it could hard brick if something goes wrong.
Click to expand...
Click to collapse
I'm trying to read through the thread you gave me but its kinda cluttered and its hard finding exactly where to start...pointers?
From the first post of that thread you will need
1. The prerequisites
-Odin
-Drivers
-Kies(dunno if this is mandatory but I guess it couldn't hurt.)
2. T-Mobile t989 uvlhi stock ROM(Odin)
You will need some type of zip software to extract the files from this.
3. Follow the steps under Installation - Odin installation(skip step 1)
After you get the stock ROM running you can install custom recovery and then flash your custom ROMs.
meekrawb said:
From the first post of that thread you will need
1. The prerequisites
-Odin
-Drivers
-Kies(dunno if this is mandatory but I guess it couldn't hurt.)
2. T-Mobile t989 uvlhi stock ROM(Odin)
You will need some type of zip software to extract the files from this.
3. Follow the steps under Installation - Odin installation(skip step 1)
After you get the stock ROM running you can install custom recovery and then flash your custom ROMs.
Click to expand...
Click to collapse
IT WORKS!!!! I LOVE YOU!! THANK YOU SO SO SO SO SO MUCH!!
THANK YOU THANK YOU THANK YOU!!
So now that I'm back on stock ROM, is my phone still rooted? Or do i need to reroot?
Edit: Downloaded a root checker. Looks like I need to reroot. Thank you again SOOOOO much!!!
Ostyrion said:
IT WORKS!!!! I LOVE YOU!! THANK YOU SO SO SO SO SO MUCH!!
THANK YOU THANK YOU THANK YOU!!
So now that I'm back on stock ROM, is my phone still rooted? Or do i need to reroot?
Click to expand...
Click to collapse
You are welcome. You are now unrooted so you have to download the recovery of your choice to the internal SD card and flash it from the stock recovery. After you reboot back into recovery you can flash a ROM and you will be rooted.
meekrawb said:
You are welcome. You are now unrooted so you have to download the recovery of your choice to the internal SD card and flash it from the stock recovery. After you reboot back into recovery you can flash a ROM and you will be rooted.
Click to expand...
Click to collapse
So in essence, once i have cwm/twrp on my phone, i have "root"?
Just to check:
1. download cwm recovery
2. via usb put onto phone.
3. reboot into recovery
4. flash cwm
5. restart phone
6. copy AOKP ROM onto phone
7. reboot into recovery
8. flash AOKP ROM?
Again, i cant thank you enough!
Ostyrion said:
So in essence, once i have cwm/twrp on my phone, i have "root"?
Just to check:
1. download cwm recovery
2. via usb put onto phone.
3. reboot into recovery
4. flash cwm
5. restart phone
6. copy AOKP ROM onto phone
7. reboot into recovery
8. flash AOKP ROM?
Again, i cant thank you enough!
Click to expand...
Click to collapse
That should do it. You won't be rooted until you install a custom ROM though(they come already rooted).
meekrawb said:
That should do it. You won't be rooted until you install a custom ROM though(they come already rooted).
Click to expand...
Click to collapse
Apparently stock recovery doesn't allow to install via internal SD card so I need odin to flash cwm dont i?
What boxes do i need checked besides the PDA checkbox?
Ostyrion said:
Apparently stock recovery doesn't allow to install via internal SD card so I need odin to flash cwm dont i?
What boxes do i need checked besides the PDA checkbox?
Click to expand...
Click to collapse
If you download the flashable zip from the first post here:
http://forum.xda-developers.com/showthread.php?p=30497342
you should be able to flash it from stock recovery. If it doesn't work I will have to look up how to install it with Odin.
meekrawb said:
If you download the flashable zip from the first post here:
http://forum.xda-developers.com/showthread.php?p=30497342
you should be able to flash it from stock recovery. If it doesn't work I will have to look up how to install it with Odin.
Click to expand...
Click to collapse
I actually got cwm 5.0.2.7 on my phone through odin. I just need root now to upgrade it to the most recent version.
I've been seeing busybox paired with superuser.
Do i need busybox? Or can i just flash superuser through cwm recovery 5.0.2.7?
Ostyrion said:
I actually got cwm 5.0.2.7 on my phone through odin. I just need root now to upgrade it to the most recent version.
I've been seeing busybox paired with superuser.
Do i need busybox? Or can i just flash superuser through cwm recovery 5.0.2.7?
Click to expand...
Click to collapse
Why do you need root? You should be able to just flash the newer cwm zip.
Here is a superuser zip that I used successfully on my t989:
meekrawb said:
Here is a superuser zip that I used successfully on my t989:
Click to expand...
Click to collapse
Thanks for the file!
I downloaded cwm from this site:
http://www.clockworkmod.com/rommanager
but it comes as an img file...and I dont seem to be able to flash that from recovery
so, i flashed the kitkat bootloader from odin, then flashed the zip from philz touch recovery. the kernel splash screen stayed on for a long time, then the screen went out, and it loaded to the kernel splash, then to recovery. then i realized i hadnt wiped, so i flashed the kitkat stock rom through odin, installed philz touch recovery, did a full wipe, then installed the zip, and the same thing happened. being a new member with less than 10 posts i cant post on the official thread, so... whats the deal? what could the problem be?
EDIT: my bad everyone. i found a misleading link to philz, the newest version in that thread was not the newest version.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/n5110/philz_touch_6.41.6-n5110.tar.md5 use this. if you have the same problem
tooandrew said:
so, i flashed the kitkat bootloader from odin, then flashed the zip from philz touch recovery. the kernel splash screen stayed on for a long time, then the screen went out, and it loaded to the kernel splash, then to recovery. then i realized i hadnt wiped, so i flashed the kitkat stock rom through odin, installed philz touch recovery, did a full wipe, then installed the zip, and the same thing happened. being a new member with less than 10 posts i cant post on the official thread, so... whats the deal? what could the problem be?
Click to expand...
Click to collapse
in aroma choose the stock kernel option. I had the same bootloop problem ....it kept going into recovery.
After choosing the stock kernel everything was smooth.
off course pls confirm that you are using the correct ROM version
for 5100 version is 1.2
1.3 is only for 5110
I didn't see any kernel options let me make a nandroid and run it again. and yeah I have the 5110. Thanks
hey, i reinstalled it, there were no kernel options, but i left the bootanimation option on stock samsung, and i had been using the XAR region, so i tried btu this time, because thats what the stock rom i have installed is. still crashes to recovery
EDIT: and after restoring my nandroid, i get to the rom splash screen, and it just loops there.
I have the same problem...Where is the Stock KK that u can flash thru Odin ???
ronny71 said:
I have the same problem...Where is the Stock KK that u can flash thru Odin ???
Click to expand...
Click to collapse
Here is the link to Stock KK:
http://www.sammobile.com/firmwares/3/?download=29611
Also download Odin v3.09 from the same link.
Then follow these instructions:
1) Unzip the Download zip file, you will get N5110XXDNE1_N5110OXADNE1_HOME.tar.md5
2) Put the tablet in Download mode
3) Install N5110XXDNE1_N5110OXADNE1_HOME.tar.md5 using "PA" option of ODIN.
4) It will take a while, let it finish.
5) If that works, reboot back to download mode
6) Install latest Philz recovery, using ODIN's PA option.
7) Reboot into recovery, and install any custom ROMS.
Note: This will trip your KNOX counter
pvsgh said:
Here is the link to Stock KK:
http://www.sammobile.com/firmwares/3/?download=29611
Also download Odin v3.09 from the same link.
Then follow these instructions:
1) Unzip the Download zip file, you will get N5110XXDNE1_N5110OXADNE1_HOME.tar.md5
2) Put the tablet in Download mode
3) Install N5110XXDNE1_N5110OXADNE1_HOME.tar.md5 using "PA" option of ODIN.
4) It will take a while, let it finish.
5) If that works, reboot back to download mode
6) Install latest Philz recovery, using ODIN's PA option.
7) Reboot into recovery, and install any custom ROMS.
Note: This will trip your KNOX counter
Click to expand...
Click to collapse
thats the thing.... i flashed it, i have stock rooted kitkat running fine, i have philz recovery running fine, but when i try to flash the custom kitkat rom, i wipe, flash the zip, the aroma installer boots i choose a few options, the aroma installer completes, then i reboot and it just crashes to recovery, no matter how many times i try, how many factory resets i do, anything. knox is tripped, but i can't run the rom. i had the 4.2.2 custom touchwiz from the same developer running fine, but then i decided i had to have kitkat, and.... nothing. it simply won't run.
if it matters, i am already running the same stock rom you linked to, 4.4.2 btu
EDIT: just for the record, i am not new to this in general, only this particular device - my sprint galaxy s3 is running carbon rom, my galaxy gear is running null rom, i flashed N3BULA on my dad's verizon galaxy note two, and ive already decided on a rom for the note 3 i am getting at the end of july.
this is just my first time encountering this problem, all assistance with this matter is greatly appreciated.
tooandrew said:
thats the thing.... i flashed it, i have stock rooted kitkat running fine, i have philz recovery running fine, but when i try to flash the custom kitkat rom, i wipe, flash the zip, the aroma installer boots i choose a few options, the aroma installer completes, then i reboot and it just crashes to recovery, no matter how many times i try, how many factory resets i do, anything. knox is tripped, but i can't run the rom. i had the 4.2.2 custom touchwiz from the same developer running fine, but then i decided i had to have kitkat, and.... nothing. it simply won't run.
if it matters, i am already running the same stock rom you linked to, 4.4.2 btu
EDIT: just for the record, i am not new to this in general, only this particular device - my sprint galaxy s3 is running carbon rom, my galaxy gear is running null rom, i flashed N3BULA on my dad's verizon galaxy note two, and ive already decided on a rom for the note 3 i am getting at the end of july.
this is just my first time encountering this problem, all assistance with this matter is greatly appreciated.
Click to expand...
Click to collapse
Ok, so first try to validate the MD5 of the file that you are installing.
if you are installing "CivZ-FlexNote8.0_KK-Rev1.3-N5110_signed.zip" then the MD5 should match as below:
b8abeb1ec9535ef526d02ef402788359
Validate the MD5 in PC as well as Tablet. Sometime you get a good download on PC, but when you copy it to Phone/tablet file might not get copied properly.
Second option you can try to install another 4.4.2 based ROM:
http://forum.xda-developers.com/showthread.php?t=2763274
Again validate the MD5 before installing.
pvsgh said:
Ok, so first try to validate the MD5 of the file that you are installing.
if you are installing "CivZ-FlexNote8.0_KK-Rev1.3-N5110_signed.zip" then the MD5 should match as below:
b8abeb1ec9535ef526d02ef402788359
Validate the MD5 in PC as well as Tablet. Sometime you get a good download on PC, but when you copy it to Phone/tablet file might not get copied properly.
Second option you can try to install another 4.4.2 based ROM:
http://forum.xda-developers.com/showthread.php?t=2763274
Again validate the MD5 before installing.
Click to expand...
Click to collapse
Md5 matches. I'm going to download am earlier update and dirty flash, see if that helps
Hey, those who were having problems, you probably got the wrong recovery. i had two versions of philz on my computer, and i flashed philz 5 instead of philz 6.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/n5110/philz_touch_6.41.6-n5110.tar.md5
the other guy who was boot looping, that is the link to the recovery you should use. everything will be fine with that one
tooandrew said:
Hey, those who were having problems, you probably got the wrong recovery. i had two versions of philz on my computer, and i flashed philz 5 instead of philz 6.
http://goo.im/devs/philz_touch/CWM_Advanced_Edition/n5110/philz_touch_6.41.6-n5110.tar.md5
the other guy who was boot looping, that is the link to the recovery you should use. everything will be fine with that one
Click to expand...
Click to collapse
Thanx my man...u hit it right on the head...Wrong Recovery...I hope everyone who has this problem reads ur post...Thanx again Buddy...:good::good:
So I have to admit I am pretty overwhelmed but the amount of information. So I wanted to find out from the community what do I do now.
My RAZR my is rooted, boot loader unlocked and on stock KK 4.4.2. I have no idea how to get the customer recovery on my phone the forrest ways as I have seen it many different ways. SO how it it I get TWRP on my device now. Once I do, is that how I install a rom? Will that wipe the stock one?
Easiest way to flash TWRP is through an app called "Flashify," which is found on the Google Play store. Download the correct version (TWRP 2.7.1.0 works well on the KK build) in ZIP format. Save to your phone. Open Flashify, backup your current recovery, and choose the new TWRP to flash. Reboot and see the new recovery.
In the new recovery, perform a full backup, throw it on your computer for safe keeping. There are a select few ROMs that work on the 3.4 kernel that the KK build uses, so if you would like to be opened to all the other ROMs, find the 98.30.1 update and flash it using your favorite method. After you flash back to the update, reinstall TWRP if it is gone, and then have fun.
To flash a ROM, just throw the ZIP file on your phone for your ROM, boot into TWRP and choose to install, and select the file(s) to flash. This does wipe the stock one. Perform a nandroid backup to save it.
xKroniK13x said:
Easiest way to flash TWRP is through an app called "Flashify," which is found on the Google Play store. Download the correct version (TWRP 2.7.1.0 works well on the KK build) in ZIP format. Save to your phone. Open Flashify, backup your current recovery, and choose the new TWRP to flash. Reboot and see the new recovery.
In the new recovery, perform a full backup, throw it on your computer for safe keeping. There are a select few ROMs that work on the 3.4 kernel that the KK build uses, so if you would like to be opened to all the other ROMs, find the 98.30.1 update and flash it using your favorite method. After you flash back to the update, reinstall TWRP if it is gone, and then have fun.
To flash a ROM, just throw the ZIP file on your phone for your ROM, boot into TWRP and choose to install, and select the file(s) to flash. This does wipe the stock one. Perform a nandroid backup to save it.
Click to expand...
Click to collapse
Thanks for this, it makes things much clearer. I noticed in the flashify app that you can flash bot rims. DO I have to do that too? or is it just the recovery that I need to worry about?
nxion said:
Thanks for this, it makes things much clearer. I noticed in the flashify app that you can flash bot rims. DO I have to do that too? or is it just the recovery that I need to worry about?
Click to expand...
Click to collapse
I'm not sure what you're saying, but recovery is the important thing. Just flash ROMs through recovery. Read directions for each ROM before you do so as well. Most require wiping the System partition at the least, but it's best to do a factory reset (via TWRP) before an install. Backup your data with Titanium.
xKroniK13x said:
I'm not sure what you're saying, but recovery is the important thing. Just flash ROMs through recovery. Read directions for each ROM before you do so as well. Most require wiping the System partition at the least, but it's best to do a factory reset (via TWRP) before an install. Backup your data with Titanium.
Click to expand...
Click to collapse
Sorry, I was trying to say in Flasify, there is the option to flash a boot and recovery image. I was asking if I had to do both.
nxion said:
Sorry, I was trying to say in Flasify, there is the option to flash a boot and recovery image. I was asking if I had to do both.
Click to expand...
Click to collapse
Boot image, I believe, is just the logo your phone displays when you first turn it on (think: red M, or after you unlock, the bootloader warning). Just the recovery is the important part.
xKroniK13x said:
Boot image, I believe, is just the logo your phone displays when you first turn it on (think: red M, or after you unlock, the bootloader warning). Just the recovery is the important part.
Click to expand...
Click to collapse
Boot image is linux kernel, do not try to touch it.
Klen2 said:
Boot image is linux kernel, do not try to touch it.
Click to expand...
Click to collapse
Good to know lol. Thank you.
I am on 4.1.2
Ive used all 3 available custom recoveries, 4 if you include the other TWRP
Every recovery with every zip, all md5 checked, say unable to open zip
Am I doing something wrong?
shaunjohn said:
I am on 4.1.2
Ive used all 3 available custom recoveries, 4 if you include the other TWRP
Every recovery with every zip, all md5 checked, say unable to open zip
Am I doing something wrong?
Click to expand...
Click to collapse
What are you trying to flash?
And which recovery VERSION are you using?
Model aand name of rom
Which model do you have?? and what is the rom's name?
210r
ive tried
philz recpvery
cwm
twrp 2/7 and 2/8
ive tried
cm11
rocket
swat(name may be wrong)
kids
Reflash the 4.4.2 firmare from odin all over again and install TWRP (2.8.0.0) the flash rom in recovery
A friendly reminder - please keep all question threads in the Q&A board. Android dev is only for posting releases, not questions.
Thanks!
Same Result
ruzell said:
Reflash the 4.4.2 firmare from odin all over again and install TWRP (2.8.0.0) the flash rom in recovery
Click to expand...
Click to collapse
same result, error opening zip file
Did you ever figure this out? I"m having the same issue.
Can't flash a ROM on Tab 3 7.0 t210r
I am rooted, first thing I did after purchase.
Am currently running 4.1.2, build jzo54k.t210rueamk1
I have flashed PhilZ Touch 6, 6.44.9, ClockworkMod 6.0.4.9 from here:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/lt02wifi/
I have tried to flash the following ROMs:
Stockrom Series Ultimate Edition
http://forum.xda-developers.com/showthread.php?t=2489395
RocketTab v3.1
http://forum.xda-developers.com/showthread.php?t=2507772
Flash fails with:
Installation aborted (bad), can't open <path to zip file><name of zip>
This happens after a factory reset, wipe data, cache.
I have a Samsung S3 that I have rooted, and then flashed many times. Before that I had an HTC EVO. I am not new to the process, but apparently I am missing something here.
Got any suggestions?
Which Odin Version you are used to install The Recovery? Try an other Version.
Is your Rom on The micro Sdcard ? If you use Philz so is The max capacity 32 GB, if you use TWRP so is max 64 GB supported.
starmaha said:
I am rooted, first thing I did after purchase.
Am currently running 4.1.2, build jzo54k.t210rueamk1
I have flashed PhilZ Touch 6, 6.44.9, ClockworkMod 6.0.4.9 from here:
https://goo.im/devs/philz_touch/CWM_Advanced_Edition/lt02wifi/
I have tried to flash the following ROMs:
Stockrom Series Ultimate Edition
http://forum.xda-developers.com/showthread.php?t=2489395
RocketTab v3.1
http://forum.xda-developers.com/showthread.php?t=2507772
Flash fails with:
Installation aborted (bad), can't open <path to zip file><name of zip>
This happens after a factory reset, wipe data, cache.
I have a Samsung S3 that I have rooted, and then flashed many times. Before that I had an HTC EVO. I am not new to the process, but apparently I am missing something here.
Got any suggestions?
Click to expand...
Click to collapse
bierma32 said:
Which Odin Version you are used to install The Recovery? Try an other Version.
Is your Rom on The micro Sdcard ? If you use Philz so is The max capacity 32 GB, if you use TWRP so is max 64 GB supported.
Click to expand...
Click to collapse
I didn't use Odin to flash the recovery. Downloaded the zip and flashed via recovery.
I have tried with the ROM on the external and internal SD. Same results.
32GB SD.
starmaha said:
I didn't use Odin to flash the recovery. Downloaded the zip and flashed via recovery.
I have tried with the ROM on the external and internal SD. Same results.
32GB SD.
Click to expand...
Click to collapse
u
How do you rooted your Tab?
With Stockrecovery you can not flash a Rom or Recovery.
Flash Philz or TWRP With Odin, reboot to The New flashen Recovery , than you can install a Rom.
All information for The right steps you will find at dev Sektion.
bierma32 said:
u
How do you rooted your Tab?
With Stockrecovery you can not flash a Rom or Recovery.
Flash Philz or TWRP With Odin, reboot to The New flashen Recovery , than you can install a Rom.
All information for The right steps you will find at dev Sektion.
Click to expand...
Click to collapse
To clarify, when I initially rooted, I used Odin to flash recovery and root.
starmaha said:
To clarify, when I initially rooted, I used Odin to flash recovery and root.
Click to expand...
Click to collapse
At first we are turn us i The circle,but now we can come to your prob.
Flash a Rom and make a picture and post that here. So we can See The error message and your Recovery.
starmaha said:
To clarify, when I initially rooted, I used Odin to flash recovery and root.
Click to expand...
Click to collapse
Sounds like the rom download is bad. Check the md5 of the rom before trying to install.
Kind of success. I downloaded the same version of PhilZ, for Odin, on my laptop.
I put the tablet in download mode and flashed the recovery with Odin.
I downloaded the ROM again (http://forum.xda-developers.com/gal...m-stockrom-kitkat-version-16-08-2014-t2849742). This is one I had tried before. This time to my laptop and copied it to the tablet. The other times, I had downloaded the ROM directly onto the tablet.
While it was in the process of flashing, there were some video anomolies.
I rebooted the tablet into recovery and flashed the ROM. It hung on SAMSUNG for a very long time after the flash and reboot. I powered it off and rebooted. It booted completely this time, but not without some issues. The first thing was when the message pops up that Android is optimizing apps. That bar was all screwy looking, snowy. (see attached image)
Once I got to the lock screen and entered the pin, the screen "fractured", pieces shifted around, and the tablet locked up. I wish I had taken a picture of it. Never seen anything like it.
I had not done a data wipe yet. I did a data wipe, rebooted, entered the pin, tablet locked up again.
I then was going to restore the backup I made before the flashing. It wouldn't restore because of an MD5 mismatch. I had restored this backup previously with no problem.
I restored an older backup and then spent a couple of hours getting everything back to the level of the now broken backup.
Flash nolekat and all went fine.
I've had problems as well. I normally flash via a recovery. At times I'll have an md5 mismatch or it just doesn't work; I've even backed up a working ROM only to find out I can't restore the same backup. Seems like a hit or miss with me
I tried flashing NoleKat and it failed on me too.
[/COLOR]
bierma32 said:
At one of your post you write after flashing you must put in the Pin?
So you have make not a clean install or factory reset, you done a wipe cache and wipe dalvik.
You must do a clean install if you come from different Roms or Version.
Click to expand...
Click to collapse
Please post a picture from your Recovery with the error message.
Yeah, im impatient. Anyone know of a way to do this? I'd be happy to try a port if anyone could point me on the right direction.
you should be able to just flash the released T805 MM zip from samsung onto a T800. all you should see is a no LTE sign as in circle with line through it once it boots to desktop. im not 100% sure though so i take no responsibility for a bricked device.
Don't they have different CPUs, Exynos and Snapdragon? So really not as simple as just flashing it.
Sent from my SM-N910F using Tapatalk
oops !!
The 805 and 800 both use same exynos CPU . It's the 807 variant that had the SD.
Regardless of CPU the file manifest won't pass hash check, there's no way to flash the 805 ROM on the 800 without unpacking and moding it.
texaspledge said:
Yeah, im impatient. Anyone know of a way to do this? I'd be happy to try a port if anyone could point me on the right direction.
Click to expand...
Click to collapse
Odin flashable.
Make a full backup with TWRP then wipe dalvik cache.
Extract tar archive from zip and flash with ODIN in AP slot.
Contains only boot, recovery, cache and modified system image.
Usually takes around 10 mins to boot. If it hangs for much longer or boot loops it may be necessary to wipe data.
MM_SM-T800_T805OXA1CPH6_REPACK
.
ashyx said:
Odin flashable.
Make a full backup with TWRP then wipe dalvik cache.
Extract tar archive from zip and flash with ODIN in AP slot.
Contains only boot, recovery, cache and modified system image.
Usually takes around 10 mins to boot. If it hangs for much longer or boot loops it may be necessary to wipe data.
MM_SM-T800_T805OXA1CPH6_REPACK
.
Click to expand...
Click to collapse
You are awesome sir! I will let you all know how it goes.
ashyx said:
Odin flashable.
Make a full backup with TWRP then wipe dalvik cache.
Extract tar archive from zip and flash with ODIN in AP slot.
Contains only boot, recovery, cache and modified system image.
Usually takes around 10 mins to boot. If it hangs for much longer or boot loops it may be necessary to wipe data.
MM_SM-T800_T805OXA1CPH6_REPACK
.
Click to expand...
Click to collapse
Unfortunately doesn't seem to be working. Reboots to recovery saying:
System/bin/e2fsck failed with status 255
Format_volume: e2fsck fail : dev/block/platform/dw_mmc.0/by-name/cache
texaspledge said:
Unfortunately doesn't seem to be working. Reboots to recovery saying:
System/bin/e2fsck failed with status 255
Format_volume: e2fsck fail : dev/block/platform/dw_mmc.0/by-name/cache
Click to expand...
Click to collapse
Are you trying to install it with twrp?
Not sure what your doing but you wouldn't get that error with odin.
ashyx said:
Are you trying to install it with twrp?
Not sure what your doing but you wouldn't get that error with odin.
Click to expand...
Click to collapse
I installed with ODIN but first time it rebooted, it applied system update and then went into recovery with those errors messages.
Just reboot. It's only trying to wipe the cache partition.
Did the system.img install ok?
ashyx said:
Just reboot. It's only trying to wipe the cache partition.
Did the system.img install ok?
Click to expand...
Click to collapse
Multiple reboots don't help. Doesn't even get to samsung splash screen. Now that I tried again, after ODIN, it reboots and the tab shows the android updating icon and it gets about 1/3rd of the way through and spits me back to recovery. I don't think it is applying the system.img.
texaspledge said:
Multiple reboots don't help. Doesn't even get to samsung splash screen. Now that I tried again, after ODIN, it reboots and the tab shows the android updating icon and it gets about 1/3rd of the way through and spits me back to recovery. I don't think it is applying the system.img.
Click to expand...
Click to collapse
Does odin flash all 4 images OK? Are running the latest LL bootloader BOL1?
The other way to flash is to extract the images from the tar archive and use the system image flashing feature in TWRP.
same problem, Odin flash everything without an error, but when the tab restarts it fail on applying update and enter in the stock samsung recovery with the the error:
System/bin/e2fsck failed with status 255
Format_volume: e2fsck fail : dev/block/platform/dw_mmc.0/by-name/cache
i'm trying to update from the stock lollipop, and I have the last bootloader
RoIlingThunder said:
same problem, Odin flash everything without an error, but when the tab restarts it fail on applying update and enter in the stock samsung recovery with the the error:
System/bin/e2fsck failed with status 255
Format_volume: e2fsck fail : dev/block/platform/dw_mmc.0/by-name/cache
i'm trying to update from the stock lollipop, and I have the last bootloader
Click to expand...
Click to collapse
Wipe cache in recovery and reboot. It could be the install script in cache is looking for something that's not there.
As I've said above flashing boot and system with twrp should suffice.
While your there check to see if the system.img got installed by using twrp file manager to look for the required folders and files.
Make sure system is mounted first.
Just tried flashing in TWRP. Started with ODIN of latest French LP and then flashed TWRP. Then flashed system and boot. No go. It just stalls at initial 'by android' splash and sits there.
Thanks for the effort but I guess I'll need to wait for official.
Should also say that in TWRP system and boot flashed with no errors.
texaspledge said:
Just tried flashing in TWRP. Started with ODIN of latest French LP and then flashed TWRP. Then flashed system and boot. No go. It just stalls at initial 'by android' splash and sits there.
Thanks for the effort but I guess I'll need to wait for official.
Click to expand...
Click to collapse
After some investigation it seems the issue is incorrect permissions as I have been able to recreate the error. I have also managed to hopefully fix the issue.
The download below is a TWRP flashable zip with permissions set correctly this time. This is tested and working just fine.
INSTALL:
Copy the zip below to your sdcard.
There shouldn't be any need to wipe data, but wipe system and cache first in TWRP then install the zip below.
Be patient it will take at least 10 mins for first boot. If it takes much longer you may need to wipe DATA.
SM-T800_T805OXA1CPH6_MM
.
ashyx said:
After some investigation it seems the issue is incorrect permissions as I have been able to recreate the error. I have also managed to hopefully fix the issue.
The download below is a TWRP flashable zip with permissions set correctly this time. This is tested and working just fine.
INSTALL:
Copy the zip below to your sdcard.
There shouldn't be any need to wipe data, but wipe system and cache first in TWRP then install the zip below.
Be patient it will take at least 10 mins for first boot. If it takes much longer you may need to wipe DATA.
SM-T800_T805OXA1CPH6_MM
.
Click to expand...
Click to collapse
Downloading now ?