I flashed the recovery for SM 9005 (new kernel) with Odin 3,09 (Chose AP, this = PDA, right?). While flashing it started bootlooping, and for just a few seconds it showed the lockscreen then bootlooped again.
I have root and recovery, but everytime i start the phone it bootloops a couple of times before it fully starts the phone. Basically the phone works just fine, it just struggles to boot.
EDIT: Crap, I tried to install Xposed Framework, but KNOX seemed to block it, rebooted, now its just bootlooping, somtimes it briefly shows the logon screen, but never fully boots.
EDIT 2: Flashed a remove Xposed.zip, it stil bootloops (A LOT) ,but eventually it starts up properly?
EDIT 3: Tried to wipe cache and dalvik, no luck. Tried to reflash recovery, both including the regular kernel, and the old kernel, no luck.
This is the Odin log:
<ID:0/006> Added!!
<ID:1/007> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:1/007> Odin v.3 engine (ID:7)..
<ID:0/006> File analysis..
<ID:1/007> File analysis..
<ID:1/007> SetupConnection..
<ID:0/006> SetupConnection..
<ID:1/007> Initialzation..
<ID:1/007> Get PIT for mapping..
<ID:1/007> Firmware update start..
<ID:1/007> SingleDownload.
<ID:1/007> recovery.img
<ID:1/007> NAND Write Start!!
<ID:1/007> RQT_CLOSE !!
<ID:1/007> RES OK !!
<ID:1/007> Remain Port .... 1
<OSM> All threads completed. (succeed 1 / failed 1)
<ID:0/006> Added!!
As you can see I got suceed 1/failed 1, any tips? Would a data wipe fix the bootlooping?
midnightzen said:
I flashed the recovery for SM 9005 (new kernel) with Odin 3,09 (Chose AP, this = PDA, right?). While flashing it started bootlooping, and for just a few seconds it showed the lockscreen then bootlooped again.
I have root and recovery, but everytime i start the phone it bootloops a couple of times before it fully starts the phone. Basically the phone works just fine, it just struggles to boot.
EDIT: Crap, I tried to install Xposed Framework, but KNOX seemed to block it, rebooted, now its just bootlooping, somtimes it briefly shows the logon screen, but never fully boots.
EDIT 2: Flashed a remove Xposed.zip, it stil bootloops (A LOT) ,but eventually it starts up properly?
EDIT 3: Tried to wipe cache and dalvik, no luck. Tried to reflash recovery, both including the regular kernel, and the old kernel, no luck.
This is the Odin log:
<ID:0/006> Added!!
<ID:1/007> Added!!
<ID:0/006> Odin v.3 engine (ID:6)..
<ID:1/007> Odin v.3 engine (ID:7)..
<ID:0/006> File analysis..
<ID:1/007> File analysis..
<ID:1/007> SetupConnection..
<ID:0/006> SetupConnection..
<ID:1/007> Initialzation..
<ID:1/007> Get PIT for mapping..
<ID:1/007> Firmware update start..
<ID:1/007> SingleDownload.
<ID:1/007> recovery.img
<ID:1/007> NAND Write Start!!
<ID:1/007> RQT_CLOSE !!
<ID:1/007> RES OK !!
<ID:1/007> Remain Port .... 1
<OSM> All threads completed. (succeed 1 / failed 1)
<ID:0/006> Added!!
As you can see I got suceed 1/failed 1, any tips? Would a data wipe fix the bootlooping?
Click to expand...
Click to collapse
Don't add more wood into the fire.
Flash stock and try again.
nicholaschum said:
Don't add more wood into the fire.
Flash stock and try again.
Click to expand...
Click to collapse
now its worse its on a bootloop and when i try to reboot into recovery it doesnt. i think my phone is bricked fck
Check md5 and flash again stock. Maybe dl last one NF4 or NG1
Related
Hi
I tried to re-partition my Samsung S3 mini with a custom pit file with Odin v3.07. This is Odin output, looks ok:
<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> 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> RQT_CLOSE !!
<ID:0/003> RES OK !!
<ID:0/003> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
Click to expand...
Click to collapse
I'd like to remove the recovery partition and resize following system partition instead. The download menu on the device prints a red warning "Custom pit file", which I ignore.
After rebooting the device, I can't see any change, the recovery image still boots and the red flag in the download mode disappeared.
Why does it not work, I tried already different checkbox combinations on Odin.
Regards
Edit:
The problem was, that I tried to repartition the device without flashing the images. Instead of Odin, Heimdall throws an error.
Long story shot.
Flashed KK Bootloader, success, flashed x-note 8, phone was in a boot loop.
Waited over 10mins, so definately boot loop and not a slow boot.
tried everything, so decided to flash the stock KK via odin to see where that gets me.
Everything in Odin is setup correct, though when I added all the files to flash the stock rom I get.
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Set PIT file..
<ID:0/005> DO NOT TURN OFF TARGET!!
<ID:0/005> FAIL!
<ID:0/005>
<ID:0/005> Re-Partition operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
????
However I can flash the bootloader on its on and CWM, now when I try and flash a KK rom (Sweet, xnote etc...) I am now stuck at the Note 3 screen before the boot animation.
Any ideas on what I can try?
Thanks!
Everything is working now via the method found in this thread
http://forum.xda-developers.com/showthread.php?t=2616103
I do have a HK note.
I am trying to use CF Auto-Root for my GS-4 i9500. I power up my phone in "download mode" but as soon as i do it already says 'Downloading... Do not turn on target!!'. I waited for a while (watched a tv show so probably 40-45 min) and nothing changed. The upper left says; Odin mode, ..., Write Protection: Enabled, eMMC BURST MODE enabled. I turn it off and back on in download mode (still says 'Downloading...'), load up the binary, connect the phone to my comp (odin says 'Added!!' and recognizes the COM port it is connected to), and click start. About half the time i get:
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Removed!!
<ID:0/004> Get PIT for mapping..
<ID:0/004> There is no PIT partition.
<OSM> All threads completed. (succeed 0 / failed 1)
I have tried 4 different USB ports and 3 different cables. I can simply click restart in odin and try again when i get this error
The other half i get:
<ID:0/005> Added!!
<ID:0/005> Odin v.3 engine (ID:5)..
<ID:0/005> File analysis..
<ID:0/005> SetupConnection..
<ID:0/005> Initialzation..
<ID:0/005> Get PIT for mapping..
<ID:0/005> Firmware update start..
<ID:0/005> recovery.img
<ID:0/005> NAND Write Start!!
<ID:0/005> FAIL! (Auth)
<OSM> All threads completed. (succeed 0 / failed 1)
in the upper left on my phone I get, in red; start [224, 1440], secure magicode check fail : recovery. This requires me to reboot the phone for another attempt. I have clicked the PIT button in odin and there are no files there.
I have found some similar threads for the first failure but they all seem to require re-partitioning and re-make (?) the PIT file which is apparently "extremely risky". As for the second failure, I found several threads with a similar failure but they were regarding going back to stock and seemed to be caused by a bad recovery image?? On the up side my phone will still boot into factory software just fine, but I would really like to figure out what I'm f-ing up.
What am I doing wrong?
Thanks in advance for any help
If I were you, I would look for a custom recovery and flash this. I use Philz Touch Recovery, you can root it from it and it works perfect.
Links here: http://d-h.st/users/philz_touch/?fld_id=16644#files
flash it in Odin using AP.
Hi,
Hope someone can help me. I'm having problems rooting my Note 4 N910F. Initially I tried CF's autoroot but my phone went into a loop with the message "CF Auto Root, Set Warranty bit : recovery" message appearing in the top left. I could not get it out of this, so then tried to install TWRP recovery. This seemed to be successful as the phone rebooted and i was able to use my phone again. See Odin log :
<ID:0/004> Added!!
<ID:0/004> Odin v.3 engine (ID:4)..
<ID:0/004> File analysis..
<ID:0/004> SetupConnection..
<ID:0/004> Initialzation..
<ID:0/004> Get PIT for mapping..
<ID:0/004> Firmware update start..
<ID:0/004> recovery.img
<ID:0/004> NAND Write Start!!
<ID:0/004> RQT_CLOSE !!
<ID:0/004> RES OK !!
<ID:0/004> Removed!!
<ID:0/004> Completed..
<OSM> All threads completed. (succeed 1 / failed 0)
However when I tried to get into TWRP it simply boots into the stock android recovery. When i try to do a OTA update now I get the message " The operating system on your device has been modified...."
Thanks
Paul
Ok Think I've worked this out for myself. Think with CF autoroot I needed a special file that was posted by a Tony on here for my version of the N910F. Tried the TWRP again with Odin and did not do an automatic reboot this time. Pulled the battery and booted into recovery and have TWRP. Seems my phone was automatically replacing TWRP with stock recovery.
Hope this helps somebody else out!
Hey guys,
i gut some serious problems with my Galaxy S4 (GT-I9505)
I was running Cyanogen Mod 12.1 with CWM Recovery. After trying to update to CM13 and the appropriate Gapps i noticed some problems installing gapps with CWM. After searching the internet i decided to try it with TWRP instead of CWM. So i used the App Rashr Flash Tool to Flash the latest TWRP Recovery.
After flashing TWRP i rebooted the device and got stuck at the Samsung welcome screen. In the right upper corner is displayed the following:
RECOVERY BOOTING. . . .
RECOVERY IS NOT SEANDROID ENFORCING
Set Warranty Bit : recovery
Unfortunatelly the phone does not load the recovery or start the OS. The only option i recognized is to enter the download mode by pushing Home + Vol.Down + PWR.
So i tried to use Odin to reinstall TWRP correctly over download mode and this is what Odin puts out.
<ID:0/006> Added!!
<ID:0/006> Odin engine v(ID:3.1100)..
<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> recovery.img
<ID:0/006> NAND Write Start!!
<ID:0/006> Complete(Write) operation failed.
<OSM> All threads completed. (succeed 0 / failed 1)
<ID:0/006> Removed!!
<ID:0/006> Added!!
When i now restart the phone i got following message on the screen:
Firmware upgrade encountered an issue. Please select recovery mode in Kies & try again
After installing Kies it says that my device is not supportet...
So no i have no idea what else i can do to get my phone running again...
Does anyone has an idea?
Best Regards and thanks
Did you try flashing the latest stock ROM from sammobile.com?
Maybe use Odin to flash the latest version of TWRP to see if you can enter recovery?
The solution is easy. Use a different usb port / different usb cable.
Well a different USB-Port got me one step further.
It seems that odin flashed the recovery successfully:
<ID:0/007> Added!!
<ID:0/007> Odin engine v(ID:3.1100)..
<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> recovery.img
<ID:0/007> NAND Write Start!!
<ID:0/007> RQT_CLOSE !!
<ID:0/007> RES OK !!
<ID:0/007> Removed!!
<ID:0/007> Remain Port .... 0
<OSM> All threads completed. (succeed 1 / failed 0)
After that my phone booted back into my current android / cm OS
Unfortunatelly, if i try to reboot directly into the recovery, i get stuck in the samsung welcome screen again. Means i can not access the recovery...
Use a different recovery thats my advice, i have a same issue as you maybe someone could help me, i open a new thread there also
Try this: unchecked everything except f.reset time in Odin before flashing TWRP, connect phone, flash TWRP, when you see the word "RESET" in the status windows, remove USB cable, remove battery, replace battery, use button combination to boot into recovery. When the phone powers up, let the power button go but keep holding home and volume up.
somehow i fixed it...
i re-re-reflashed twrp and suddenly everything went fine.
Thanks for your help and real quick responses!
great forum!