So here are my issues.
I used CF-auto root to install custom ROMS. Roms like Hybrid just got stuck in a bootloop, regardless of how many times I wiped everything. CM works almost fine. However, it randomly reboots. No timing, app, battery, usage, or other patterns I can see. It just randomly reboots itself.
I downloaded the BOB7 and tried to Odin back, but it just fails everytime.
Log on the phone says
UDC START
SW REC CHECK FAIL: [aboot]Fused 2 > binary 1
[1]eMMC write fail: ABOOT
Odin reports:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I either need to fix CM so it quits randomly rebooting, or go back to stock. I'm not too picky as to which option, so I'll take whatever I can get.
James.Q.Campbell said:
So here are my issues.
I used CF-auto root to install custom ROMS. Roms like Hybrid just got stuck in a bootloop, regardless of how many times I wiped everything. CM works almost fine. However, it randomly reboots. No timing, app, battery, usage, or other patterns I can see. It just randomly reboots itself.
I downloaded the BOB7 and tried to Odin back, but it just fails everytime.
Log on the phone says
UDC START
SW REC CHECK FAIL: [aboot]Fused 2 > binary 1
[1]eMMC write fail: ABOOT
Odin reports:
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I either need to fix CM so it quits randomly rebooting, or go back to stock. I'm not too picky as to which option, so I'll take whatever I can get.
Click to expand...
Click to collapse
Use your backup and try to fix CM
xxSTARBUCKSxx said:
Use your backup and try to fix CM
Click to expand...
Click to collapse
Yeah, accidentally deleted backup. Kicked myself plenty for it. I've wiped and reinstalled CM half a dozen times now with no luck. 3x factory reset, cache, dalvik, data and system wiped 3, 4 or even 5 times.
Still reboots randomly.
James.Q.Campbell said:
Yeah, accidentally deleted backup. Kicked myself plenty for it. I've wiped and reinstalled CM half a dozen times now with no luck. 3x factory reset, cache, dalvik, data and system wiped 3, 4 or even 5 times.
Still reboots randomly.
Click to expand...
Click to collapse
Ever thought of trying Noterized? it will flash through Odin, give that a test drive.
xxSTARBUCKSxx said:
Ever thought of trying Noterized? it will flash through Odin, give that a test drive.
Click to expand...
Click to collapse
I downloaded it, but have no idea how to flash it through Odin. Help?
James.Q.Campbell said:
I downloaded it, but have no idea how to flash it through Odin. Help?
Click to expand...
Click to collapse
When you click on PDA (AP) , does it not show up in the folder you downloaded it to/desktop when trying to select said file?
Try downloading cwm in odin
James.Q.Campbell said:
I downloaded it, but have no idea how to flash it through Odin. Help?
Click to expand...
Click to collapse
You don't flash it via Odin. Install thr latest TWRP through Odin then boot into recovery make a backup first then factory reset and wipe system and you should be able to install Noterized.
Sent from my SM-N910P using Tapatalk
---------- Post added at 06:56 PM ---------- Previous post was at 06:55 PM ----------
Kayotick said:
You don't flash it via Odin. Install thr latest TWRP through Odin then boot into recovery make a backup first then factory reset and wipe system and you should be able to install Noterized.
Sent from my SM-N910P using Tapatalk
Click to expand...
Click to collapse
Sounds like the only thing that will work for you is CM or Noterized both flashable via TWRP.
Sent from my SM-N910P using Tapatalk
Sorry for the misinformation, i thought Noterized worked via Odin after taking the OE1 update.
Related
So, I've recently wanted to use a custom ROM for my phone, and I have done this before, but there's a bunch of changes I guess. I thought that "unified s3" meant that the ATT variants and others (including my i747m) would be compatible, so I tried to flash "Liquid Smooth v3.0" ROM but it didn't work with TWRP. So I got CWM and restored my phone (also my restore file by accident) so my phone was totally wiped, but I could flash the ROM. The problem occurs here, the phone WILL NOT boot, it is stuck at the "Samsung Galaxy S III" splash and won't go past it. I cannot delete the cache or anything without the phone restarting itself. I tried to flash a modem with Odin but get an error also.
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> modem.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I've been searching the forums for a way to fix my i747m but I cannot find anything. Any solutions or is my phone dead. Also I can get into both recovery and download screen. I cannot flash a stock ROM because another error pops up. And when I go into download mode and flash, the "QUALCOMM SECUREBOOT: ENABLE" turns into "SECURE CHECK FAIL : aboot"
Tonamon said:
So, I've recently wanted to use a custom ROM for my phone, and I have done this before, but there's a bunch of changes I guess. I thought that "unified s3" meant that the ATT variants and others (including my i747m) would be compatible, so I tried to flash "Liquid Smooth v3.0" ROM but it didn't work with TWRP. So I got CWM and restored my phone (also my restore file by accident) so my phone was totally wiped, but I could flash the ROM. The problem occurs here, the phone WILL NOT boot, it is stuck at the "Samsung Galaxy S III" splash and won't go past it. I cannot delete the cache or anything without the phone restarting itself. I tried to flash a modem with Odin but get an error also.
<ID:0/003> Added!!
<ID:0/003> Odin v.3 engine (ID:3)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> modem.bin
<ID:0/003> NAND Write Start!!
<ID:0/003> Transmission Complete..
<ID:0/003> Now Writing.. Please wait about 2 minutes
<ID:0/003> Receive Response from boot-loader
<ID:0/003> FAIL!
<OSM> All threads completed. (succeed 0 / failed 1)
I've been searching the forums for a way to fix my i747m but I cannot find anything. Any solutions or is my phone dead. Also I can get into both recovery and download screen. I cannot flash a stock ROM because another error pops up. And when I go into download mode and flash, the "QUALCOMM SECUREBOOT: ENABLE" turns into "SECURE CHECK FAIL : aboot"
Click to expand...
Click to collapse
Since you can get into both download and recovery modes, there is plenty of hope and your phone is far from dead. Odin probably failed because you were trying to flash incompatible firmware or one that involved a bootloader downgrade attempt. You may be able to recover by re-flashing the correct firmware from (custom) recovery. You need to provide more information including what stock were you on before going custom and what stock you are now trying to revert to. When flashing stock firmware, however, you need to be sure you are working with the right ones. In spite of the near similarity in the names, firmware for the i747U... (AT&T) is different from the Canadian versions (i747M...) and you should be careful to pick only the ones specific to your phone model. You probably were on a 4.3 bootloader so your safest bet now may be to search for and download the i747M 4.3 stock rom, bootloader/modem and kernel zips and reflash these via recovery. If you are on TWRP, you may also do an advance wipe to remove all existing firmware before flashing new ones.
I've been searching the forums for 3 hours and it's gotten me nowhere.
I am trying to unroot my Note 4. Here are system specs and what I've tried:
Device Model: SM-N910P
PAC version: LP Beta-1 Nightly
Android Version: 5.0.2
Baseband version: N910PVPU2BOE1
I have tried to unroot with BOB7 using both Odin 3.07 and 3.09. Both times I get the error message on ODIN:
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> NAND Write Start!!
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL! (Auth)
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/003> Removed!!
<ID:0/003> Added!!
<ID:0/003> Removed!!
And on the phone:
sw rev check fail : [aboot]fused 2 > binary 1
[1] eMMC write fail: ABOOT
I have tried rerooting then using Odin to the same result. I am currently downloading ANIE to try that.
I have also tried swearing loudly, promised to throw virgins into a volcano to whatever deity will listen, promised my phone sexual favors and/or savage beatings, and I've consumed some whiskey.
What am I doing wrong?
U have to use a oe1 tar file and use odin you cant oding back to bob7 now that u have oe1 once u odin backto stock oel then you will be root less be careful that tar with most likely wipe internal info make sure u do a backup
Sent from my SM-N910P using Tapatalk
That's all I was missing?
OK, thanks!
Now where do I get an oe1?
JQuinnC said:
That's all I was missing?
OK, thanks!
Now where do I get an oe1?
Click to expand...
Click to collapse
The latest is OJ6. You can find it here :
http://forum.xda-developers.com/showthread.php?t=3250864
JQuinnC said:
That's all I was missing?
OK, thanks!
Now where do I get an oe1?
Click to expand...
Click to collapse
Use OJ6 tar (latest☺). You'll find it in Sprint Note 4 general forum.
Backup what you want to keep, wipe everything but extSdCard. Delete the Android folder on extSdCard. Power down and pull battery for at least 30 seconds before going to download mode. Use latest Odin with defaults, let it boot and run the setup wizard.
Sent from my SM-N910P using Tapatalk
So my Sprint Note 4 running the latest 5.1.1 stock rooted was charging today and when I took it off the charger and hit the home button it froze on the black/off screen.
I rebooted and it went directly to Odin/DL mode... tried to re-flash the same firmware with no luck, tried to flash the unroot/stock firmware with no luck.
Tried to use Kies for emergency recovery but it didn't recognize my phone.
Tried Odin once more and immediately got:
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I can't even get into recovery.
I've had not one issue with this phone since I unboxed it so this is kinda crazy.
If anyone knows of a fix please let me know, I need this phone to work.
Thank you.
broad_st_bully said:
So my Sprint Note 4 running the latest 5.1.1 stock rooted was charging today and when I took it off the charger and hit the home button it froze on the black/off screen.
I rebooted and it went directly to Odin/DL mode... tried to re-flash the same firmware with no luck, tried to flash the unroot/stock firmware with no luck.
Tried to use Kies for emergency recovery but it didn't recognize my phone.
Tried Odin once more and immediately got:
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/006> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:0/006> File analysis..
<ID:0/006> SetupConnection..
<ID:0/006> Initialzation..
<ID:0/006> Get PIT for mapping..
<ID:0/006> Firmware update start..
<ID:0/006> SingleDownload.
<ID:0/006> aboot.mbn
<ID:0/006> NAND Write Start!!
<ID:0/006> sbl1.mbn
<ID:0/006> rpm.mbn
<ID:0/006> FAIL! (Auth)
<ID:0/006>
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
I can't even get into recovery.
I've had not one issue with this phone since I unboxed it so this is kinda crazy.
If anyone knows of a fix please let me know, I need this phone to work.
Thank you.
Click to expand...
Click to collapse
Did you had TWRP 3.0 installed?
Sent from my SM-N920P using JellyBombed Tapatalk 2
GhostAssassin said:
Did you had TWRP 3.0 installed?
Sent from my SM-N920P using JellyBombed Tapatalk 2
Click to expand...
Click to collapse
just installed TWRP3.0, saw my '/system' was unchecked, hopefully that the fix right there...
broad_st_bully said:
just installed TWRP3.0, saw my '/system' was unchecked, hopefully that the fix right there...
Click to expand...
Click to collapse
Try installing an older version
Like TWRP 2.8
Afew days ago i try to install TWRP 3.0
And i ran into the same issue you have rebooted my phone and it jump into download mode,
To fix the problem i odin TWRP 2.8 and problem solve...
Sent from my SM-N920P using JellyBombed Tapatalk 2
GhostAssassin said:
Try installing an older version
Like TWRP 2.8
Afew days ago i try to install TWRP 3.0
And i ran into the same issue you have rebooted my phone and it jump into download mode,
To fix the problem i odin TWRP 2.8 and problem solve...
Sent from my SM-N920P using JellyBombed Tapatalk 2
Click to expand...
Click to collapse
I factory reset, installed a previous backup now I cant get it to boot...trying to get into Odin mode
Mods please close this thread.
Hello!
Here is the full N910AUCS2EQF1 Odin manual update to 6.0.1 for everyone to enjoy. You can flash from any current version you have now it doesn't matter whether you are on 4.4.4, 5.1.1 or 6.0.1.
https://www.androidfilehost.com/?fid=745425885120746376
If for whatever reason you want to downgrade or don't like this build, you can safely downgrade to any of the below versions without any issues. After you flash a lower android version using Odin, phone might get stuck on AT&T logo. If that happens, all you need to do is boot into recovery and do a factory wipe/reset and phone will boot right up after that. Make sure you backup your data when upgrading or downgrading firmware so you don't loose any information..
N910AUCS2EQE1 (6.0.1) - https://www.androidfilehost.com/?fid=745425885120742009
N910AUCS2EPK4 (6.0.1) - https://www.androidfilehost.com/?fid=673368273298964563
N910AUCU2EPH5 (6.0.1) - https://www.androidfilehost.com/?fid=24651430732238073
N910AUCU2DOI2 (5.1.1) - https://www.androidfilehost.com/?fid=24438995911970946
Thanks. Will give it a try later.
Great job!
Does the Odin update wipe the phone?
Thanks for sharing this. I'm a few updates behind, so I presume this will be faster than installing multiple OTAs to get up to date.
Can someone recommend a safe download location for Odin? Some of the sites that come up in Google look a little shady. Thanks.
erm, which files go where? i get an error no matter where i put any file.
hello guys, anybody know how to backup full data if the phone dont have root ??
Flashing the firmware from Odin keeps failing.
<ID:0/003> Added!!
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Set PIT file..
<ID:0/003> DO NOT TURN OFF TARGET!!
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> aboot.mbn
<ID:0/003> sbl1.mbn
<ID:0/003> rpm.mbn
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
It's happened this way 3 times thus far. I'm assuming it's an issue with the BL? I don't know...Could be very wrong. But it keeps failing.
help
Phone gets stuck at the logo even after full wipe
D3ATHSTALK3R said:
Phone gets stuck at the logo even after full wipe
Click to expand...
Click to collapse
for how long?
toutanje said:
Hello!
Here is the full N910AUCS2EQF1 Odin manual update to 6.0.1 for everyone to enjoy. You can flash from any current version you have now it doesn't matter whether you are on 4.4.4, 5.1.1 or 6.0.1.
If for whatever reason you want to downgrade or don't like this build, you can safely downgrade to any of the below versions without any issues. After you flash a lower android version using Odin, phone might get stuck on AT&T logo. If that happens, all you need to do is boot into recovery and do a factory wipe/reset and phone will boot right up after that. Make sure you backup your data when upgrading or downgrading firmware so you don't loose any information..
Click to expand...
Click to collapse
Tried this repeatedly now. fails every time. cant get past system. tried different cables, different usb ports. fails every time. every 3rd boot gets me an mmc_read_failed. I am on QF1 already, and was trying to correct a corrupted over the air install. anyone able to help?
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1203)..
<ID:0/007> File analysis..
<ID:0/007> SetupConnection..
<ID:0/007> Initialzation..
<ID:0/007> Get PIT for mapping..
<ID:0/007> Firmware update start..
<ID:0/007> SingleDownload.
<ID:0/007> boot.img
<ID:0/007> recovery.img
<ID:0/007> system.img.ext4
<ID:0/007> FAIL! (Write)
<ID:0/007>
<ID:0/007> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Click to expand...
Click to collapse
Hello all, anyone successfully used this to upgrade their phone... from the above, it looks like not the case... thanks!
ridgemagnet said:
Hello all, anyone successfully used this to upgrade their phone... from the above, it looks like not the case... thanks!
Click to expand...
Click to collapse
Yea, it worked perfectly fine for me.
Thx, where is N910AUCS2EQG1?
Gxzn said:
Yea, it worked perfectly fine for me.
Click to expand...
Click to collapse
which file did you use?
Thanks. I use this to updgrade an old phone that still had the Marshmallow beta on it.
Can someone repost the download link for N910AUCS2EQF1 I tried downloading it I've been getting really slow speeds and it stops during the download
no matter what mine just fails every time. Is there anything we can do?
F3AR420 said:
no matter what mine just fails every time. Is there anything we can do?
Click to expand...
Click to collapse
Are you still having trouble with this?
Did anyone successfully rooted sm-n910a with 6.0.1 ? if so, how?
Worked for me.
Loaded AP files first then the other 3 files after all at once.
Upgraded to 6.01 from 5.01 . I was surprised at how easy the process was as I have no knowledge on this subject.
Hi guys, bit of a noob here...I messed up my kids tablet.
It was running NoleKat 2.X, previous to that was running stock 4.4.2.
In an effort to get tablet back to stock to clear up some bootloop issues - used odin to flash stock 4.1.2 it worked no problem except Samsung update to 4.4.2 would no longer work...
so I break out odin again and grab what I think is the right stock 4.4.2 Rom from sammobile....try to flash it, it fails and now tablet only boots straight into recovery <3e>.
I tried wipes from recovery they all fail due to some make_extf4fs failed on dev block.
adb sideload will crash when ROM transfer gets to about 70%.
tablet will not take any other ADB commands
Smart switch and Kies will not reconize tablet say its unsupported - works fine on another tablet.
I can get it into odin mode but odin will fail no matter what I try and flash...works fine to flash second tablet I have.
Any suggestions or do I need a new tablet.
Plaz
I think what happened is due to the bootloader...it was different on JB, so the KK rom won't boot on it without the KK bootloader. Did you try to flash @gr8nole TWRP? If you can get it to flash, you may be able to recover it.
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
I think what happened is due to the bootloader...it was different on JB, so the KK rom won't boot on it without the KK bootloader. Did you try to flash @gr8nole TWRP? If you can get it to flash, you may be able to recover it.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Let me try that using odin - if its a bootloader issue should I not be able to flash JB stock then? should I try it if TWRP is a no go?
Thanks
Plazomat
plazomat said:
Let me try that using odin - if its a bootloader issue should I not be able to flash JB stock then? should I try it if TWRP is a no go?
Thanks
Plazomat
Click to expand...
Click to collapse
I would. Also, it's possible that your download became corrupted, might try redownloading stock from SamMobile again. I think we can probably get it going, though. There is still hope. Lol
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
I would. Also, it's possible that your download became corrupted, might try redownloading stock from SamMobile again. I think we can probably get it going, though. There is still hope. Lol
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
So when I flash twrp 2.8.0 it , the progress bar goes all the way green then fails after a few seconds here is the oding log...
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> recovery.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Thanks for any help RealWelder...
Plaz
And when I try to flash a jelly bean stock rom it fails almost instantly....and log is as such..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Plaz
plazomat said:
And when I try to flash a jelly bean stock rom it fails almost instantly....and log is as such..
<OSM> Enter CS for MD5..
<OSM> Check MD5.. Do not unplug the cable..
<OSM> Please wait..
<OSM> Checking MD5 finished Sucessfully..
<OSM> Leave CS..
<ID:0/003> Odin engine v(ID:3.1203)..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> SingleDownload.
<ID:0/003> boot.img
<ID:0/003> FAIL!
<ID:0/003>
<ID:0/003> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
Plaz
Click to expand...
Click to collapse
One more thing I should add - not sure if it makes any difference but I never get the android picture just before I get into odin mode....I need to time it, waiting for the backlight to come up, release home/power/volume down, then tap volume up and I get the odin mode text information only - never a picture.
Odin will only attempt to flash once from a fresh entry into recovery - once it fails...if I just try again it won't get past getting PIT table and pukes that PIT is missing or something like that - I will see if I can post that log as well..
PLAZ
plazomat said:
One more thing I should add - not sure if it makes any difference but I never get the android picture just before I get into odin mode....I need to time it, waiting for the backlight to come up, release home/power/volume down, then tap volume up and I get the odin mode text information only - never a picture.
Odin will only attempt to flash once from a fresh entry into recovery - once it fails...if I just try again it won't get past getting PIT table and pukes that PIT is missing or something like that - I will see if I can post that log as well..
PLAZ
Click to expand...
Click to collapse
Hi i have the same problem can u help me pls?
Making some progress i think....I found rootjunky's link to odin 3.07 and at least it does not "fail" right away.
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> PBL.bin
<ID:0/003> param.lfs
<ID:0/003> loke_2nd.bin
<ID:0/003> loke_pxa988.bin
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> radio.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Problem is no matter what stock rom or custom recovery i flash - tablet always always always reboots to samsung ( I think) recovery....
Plaz
plazomat said:
Making some progress i think....I found rootjunky's link to odin 3.07 and at least it does not "fail" right away.
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> recovery.img
<ID:0/003> PBL.bin
<ID:0/003> param.lfs
<ID:0/003> loke_2nd.bin
<ID:0/003> loke_pxa988.bin
<ID:0/003> system.img
<ID:0/003> cache.img
<ID:0/003> hidden.img
<ID:0/003> radio.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Problem is no matter what stock rom or custom recovery i flash - tablet always always always reboots to recovery....
Plaz
Click to expand...
Click to collapse
I use Odin 3.04, if that helps. In the past I've bricked mine a number of times and have always managed to fix it. Once I encountered a similar situation, where basically the system partition was shrunk from 1.4gb to 1.2gb and Odin would fail everything because of it. I was lucky enough to still have TWRP, so I used it to flash my rom's flashable zip and that fixed it. I think we need to get back to total stock 4.2.2 and then reupgrade to 4.4.2. Or we need to get TWRP to flash... Can you open up a terminal shell anywhere and get root? If so we could manually flash TWRP.
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
I use Odin 3.04, if that helps. In the past I've bricked mine a number of times and have always managed to fix it. Once I encountered a similar situation, where basically the system partition was shrunk from 1.4gb to 1.2gb and Odin would fail everything because of it. I was lucky enough to still have TWRP, so I used it to flash my rom's flashable zip and that fixed it. I think we need to get back to total stock 4.2.2 and then reupgrade to 4.4.2. Or we need to get TWRP to flash... Can you open up a terminal shell anywhere and get root? If so we could manually flash TWRP.
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
I can try using Odin 3.04 see if that helps at all...
I have tried using ABD commands from my PC in powershelll and a CMD window, but the only time it responds to anything is when I put it into ADB sideload mode from the "recovery".
I will try to flash a stock 4.2.2 with Odin 3.04 and report back.
Is there anyway to Odin Flash your ROM?
Thanks for help Real Welder
Plaz
plazomat said:
I can try using Odin 3.04 see if that helps at all...
I have tried using ABD commands from my PC in powershelll and a CMD window, but the only time it responds to anything is when I put it into ADB sideload mode from the "recovery".
I will try to flash a stock 4.2.2 with Odin 3.04 and report back.
Is there anyway to Odin Flash your ROM?
Thanks for help Real Welder
Plaz
Click to expand...
Click to collapse
I tried to do an Odin flashable before and it passed and everything, but once the ROM booted up it wouldn't connect to the pc anymore via mtp. I could try to upload one and if it boots up we can flash TWRP and then my ROM and everything will work correctly. The main thing is just getting out of the loop. Report back on the 4.2 flash, meanwhile I'll try to get an Odin flashable for you to try.
Here is my ROM in Odin format. Hope it helps!
https://drive.google.com/file/d/1g6sM4l--bYqIGrzeUu0aMEEc0vBmQwga/view?usp=drivesdk
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
I tried to do an Odin flashable before and it passed and everything, but once the ROM booted up it wouldn't connect to the pc anymore via mtp. I could try to upload one and if it boots up we can flash TWRP and then my ROM and everything will work correctly. The main thing is just getting out of the loop. Report back on the 4.2 flash, meanwhile I'll try to get an Odin flashable for you to try.
Here is my ROM in Odin format. Hope it helps!
https://drive.google.com/file/d/1g6sM4l--bYqIGrzeUu0aMEEc0vBmQwga/view?usp=drivesdk
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Thanks RealWelder you are awesome to still be supporting these old beaters - gonna try this in the morning when I get some time....
Plaz
Did either of you have any luck?
Sent from my KYOCERA-C6745 using Tapatalk
RealWelder said:
Did either of you have any luck?
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Sorry Real - I haven't got a chance to try it - life got in the way...been itching to get this moving again...plan is to attempt it later today..
I read that the kernel may have to be flashed with something like the blackhawk kernel...because this tab was once upgraded to 4.4.2 and I went back to a 4.1.2 stock rom...any opinons on if I should bother with that first? or at all?
Thanks so much for the help.
Plaz
plazomat said:
Sorry Real - I haven't got a chance to try it - life got in the way...been itching to get this moving again...plan is to attempt it later today..
I read that the kernel may have to be flashed with something like the blackhawk kernel...because this tab was once upgraded to 4.4.2 and I went back to a 4.1.2 stock rom...any opinons on if I should bother with that first? or at all?
Thanks so much for the help.
Plaz
Click to expand...
Click to collapse
Couple things to keep in mind here:
If the full 4.4.2 firmware was flashed to the device at any point, then the bootloader was updated. The 4.4.2 bootloader needs to have the stock 4.4.2 recovery or one of the custom recoveries that has the "recovery bootloop" fix. The most recent TWRP will work.
The 4.4.2 bootloader looks for a signal that the recovery session is complete before it will boot into the OS properly. Older 4.1.2 recoveries do not provide this "recovery complete" signal, so it gets stuck in the recovery bootloop.
This may or may not be useful in your case as I admit that I didn't read this whole thread.
gr8nole said:
Couple things to keep in mind here:
If the full 4.4.2 firmware was flashed to the device at any point, then the bootloader was updated. The 4.4.2 bootloader needs to have the stock 4.4.2 recovery or one of the custom recoveries that has the "recovery bootloop" fix. The most recent TWRP will work.
The 4.4.2 bootloader looks for a signal that the recovery session is complete before it will boot into the OS properly. Older 4.1.2 recoveries do not provide this "recovery complete" signal, so it gets stuck in the recovery bootloop.
This may or may not be useful in your case as I admit that I didn't read this whole thread.
Click to expand...
Click to collapse
Thanks gr8nole - tried flashing the 3.0.0 TWRP still no joy - keeps booting into stock (ithink) recovery. I pulled it from your file repo on Android file host.
I say I think cause the font is so big and the display is in landscape mode.
Plaz
RealWelder said:
Did either of you have any luck?
Sent from my KYOCERA-C6745 using Tapatalk
Click to expand...
Click to collapse
Gave it a go with your ROM...still recovery boot loop as suggested by gr8nole.
Here is log..
<ID:0/003> File analysis..
<ID:0/003> SetupConnection..
<ID:0/003> Initialzation..
<ID:0/003> Get PIT for mapping..
<ID:0/003> Firmware update start..
<ID:0/003> boot.img
<ID:0/003> NAND Write Start!!
<ID:0/003> system.img
<ID:0/003> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Removed!!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Thanks again
Plaz
Hi Gents, still messing with this when I have time and no joy...
Can't get a custom recovery to stick, odin flashes file but when device reboots just goes back to stock recovery...
Any clues.
Plaz