Hallo everybody, greetings from germany.
I would need some support from you guys on a bootloop case for the sm-t700. I searched my ass off in google and xda but could not find a solution.
So now after hours of trying it myself I like to ask for help.
In the following I will describe what I have done to come to this point including everything I installed etc.
The stock rom was lollipop 5.0.2 and already installed.
- usb debug mode on
- flashed via odin v.3.10.7 supersu "cf-autoroot-twrp-t700.tar"
- forgot to install busybox and rootchecker for verifying root.
- backup of IMEI/EMFS (data is now on pc)
- in recovery backup of Boot.img
- wipe data/cache/dalwik/system in one go
- flashed "Euphoria-OS-1.1-klimtwifi-UNOFFICIAL-20150812.zip"
"open_gapps-arm-5.1-pico-20151013.zip"
"SkyHigh_SM-T700_kernel_TW-LL_v2.0.zip"
- rebooted and waited up to 15 - 20 min. Stopped waiting after that.
the regular samsung logo while booting shows up in intervalls from 5 to 10 minutes.
Next I wanted to do it better by installing busybox and cheking for root, because
I thought first that this could be the main cause for the bootloop.
- downloadmode
- flashed succesfully "T700XXU1BOE5_T700DBT1BOD1_HOME.tar.md5" via odin v.3.10.7 to get to stockrom again
- usb debug mode on
- downloadmode
- flashed via odin v.3.10.7 supersu "cf-autoroot-twrp-t700.tar"
- verifyied it with rootvalidator
- installed busybox
- deleted all knox stuff
- installed twrp app to get to v.2.8.7.0
- recoverymode
- backup of everything
- wipe data/cache/dalwik/system
- flashed "Euphoria-OS-1.1-klimtwifi-UNOFFICIAL-20150812.zip"
"open_gapps-arm-5.1-pico-20151013.zip"
"SkyHigh_SM-T700_kernel_TW-LL_v2.0.zip"
- rebooted and waited up to 15 - 20 min. Stopped waiting after that.
the regular samsung logo while booting shows up in intervalls again from 5 to 10 minutes.
Next I went into recovery and restored everything as before the flash of the customrom.
This happens in the same way with blisspop and liquidsmooth roms.
Hope anyone knows something.
Youve flashed an aosp rom , but attempting to boot with a stock based kernel.
Its never advisable to multi flash. Flash after each successful boot.
You need to flash the kernel provided in that thread or flash the whole rom again.
Also make sure your bootloader is up to date.
Tbh I'd wipe and start again.
ashyx said:
Youve flashed an aosp rom , but attempting to boot with a stock based kernel.
Its never advisable to multi flash. Flash after each successful boot.
Click to expand...
Click to collapse
By "multi flash" do you mean the install procedure in twrp that automates the installation procedure? (add zip)
And how am I able to flash after each successful boot if there is nothing to boot left after wipe?
ashyx said:
You need to flash the kernel provided in that thread or flash the whole rom again.
Click to expand...
Click to collapse
I thought this Kernel would be great. So you do not recommend me to use it?
I will look up the roms now and the kernel they use.
ashyx said:
Also make sure your bootloader is up to date.
Tbh I'd wipe and start again.
Click to expand...
Click to collapse
How do I do this or if already up to date where do I can look it up?
According to your post you flashed rom, gapps and kernel in one go.
Any one of those could have caused a bootloop or hang.
As for SkyHigh kernel, it is a great kernel but probably not suitable for an aosp rom as it's built from stock sources intended for stock roms.
Use the kernel provided.
To update the bootloader flash the latest firmware or pull it out and flash it separately.
Okay I will do the following now.
First find the appropiate Kernel if Skyhigh is a nogo. sadly.
Then flash in recovery at first the kernel of the rom. boot. recovery, flash the customrom + gapps. Right?
And before all that flash a new bootloader.
Further, is there a Kernel beside the one of the roms that you would recommend me?
Just wipe data and cache in recovery then flash just the rom. It probably already has the kernel.
Don't flash gapps just reboot after flashing the rom.
ashyx said:
Just wipe data and cache in recovery then flash just the rom. It probably already has the kernel.
Don't flash gapps just reboot after flashing the rom.
Click to expand...
Click to collapse
Okay worked well.
Left out the kernel because I could not find any custom ones.
Now I have euphoria on it and want to change between blisspop and liquidsmooth until I have the one I like most.
It is kinda hard to get the difference. I just know that euphoria and liquid are faster, smoother?
Thanks a lot without your input I would still be searching for an answer.
Happy day to you.
skyhigh and iron kernel are mean for touchwiz. Its not mean for cyanogen/aosp/aokp.
currently there is no one cook a custom kernel for cyanogen/aosp/aokp rom. so we stuck with the kernel that come with the rom.
Kernels :
https://www.androidfilehost.com/?w=files&flid=37193
Okay, did not know about this kernel.could you give me some info about the "deathly signed"?
My browser here is not loading the xda thread where I found people talking about it.
Related
Hello members,i have a problem . I bought a samsung galaxy tab 3 7.0 wifi (SM-T210) last week and i have rooted it + installed cwm and after i flash anything(custom lock screen or custom rom) the tablet gets soft bricked and the rom dont boot anymore,it enters automaticaly in cwm. So how can i fix it?
d0vada said:
Hello members,i have a problem . I bought a samsung galaxy tab 3 7.0 wifi (SM-T210) last week and i have rooted it + installed cwm and after i flash anything(custom lock screen or custom rom) the tablet gets soft bricked and the rom dont boot anymore,it enters automaticaly in cwm. So how can i fix it?
Click to expand...
Click to collapse
Which recovery Version you are flashed on your tab?
And which root.zip you are used?
Flash Stockrom and try it again.
bierma32 said:
Which recovery Version you are flashed on your tab?
And which root.zip you are used?
Flash Stockrom and try it again.
Click to expand...
Click to collapse
Im using the latest TWRP recovery 2.7.0.0 and for root i use a zip called universal root armeabi *smth like that*
I allready flashed the stockrom 3 times and i got the same result. also im using the T210XXANC2 firmware.
In CWM, wipe data and factory reset. Then go to Download mode, use Odin and flash your stock rom. That should do it.
paranoidmarvin42 said:
In CWM, wipe data and factory reset. Then go to Download mode, use Odin and flash your stock rom. That should do it.
Click to expand...
Click to collapse
i have rooted stock rom running with latest twrp but if i flash a custom rom it wont boot anymore, it gets softbricked but i dont know why.
d0vada said:
i have rooted stock rom running with latest twrp but if i flash a custom rom it wont boot anymore, it gets softbricked but i dont know why.
Click to expand...
Click to collapse
What ROM are you trying to flash? You must have missed a step. Make sure you read the instructions carefully before doing anything and use a custom rom for your device. Try again. I'm also new to Android and has softbricked my tab a couple of times now.
Go back to stock. Let your device boot completely. Install recovery again. Reboot again.
To make it easier, how about watching a video so you can see how it's done properly? It helped me a lot. http://forum.xda-developers.com/showthread.php?t=2459817
Good luck.
paranoidmarvin42 said:
What ROM are you trying to flash? You must have missed a step. Make sure you read the instructions carefully before doing anything and use a custom rom for your device. Try again. I'm also new to Android and has softbricked my tab a couple of times now.
Go back to stock. Let your device boot completely. Install recovery again. Reboot again.
To make it easier, how about watching a video so you can see how it's done properly? It helped me a lot. http://forum.xda-developers.com/showthread.php?t=2459817
Good luck.
Click to expand...
Click to collapse
I want to flash seal rom. also, thanks for the links, i will check them later.
d0vada said:
I want to flash seal rom. also, thanks for the links, i will check them later.
Click to expand...
Click to collapse
Plesse,dont use TWRP , i prefere CWM or PhilzTouch,why : alot of user are have postet probs when they used TWRP.
Also i prefere after rooting The Blackhawk Kernel.
bierma32 said:
Plesse,dont use TWRP , i prefere CWM or PhilzTouch,why : alot of user are have postet probs when they used TWRP.
Also i prefere after rooting The Blackhawk Kernel.
Click to expand...
Click to collapse
So i have flashed (again) the stock firmware from sammobile,i rooted it,installed cwm 6.0.4.7 and then i flashed SEAL rom v4 and its not working. Its like something that doesnt let custom rom boot on my tab. Sad part is that i cant provide a logcat because the android wont boot.
EDIT: Do i have to unlock the bootloader?
d0vada said:
So i have flashed (again) the stock firmware from sammobile,i rooted it,installed cwm 6.0.4.7 and then i flashed SEAL rom v4 and its not working. Its like something that doesnt let custom rom boot on my tab. Sad part is that i cant provide a logcat because the android wont boot.
EDIT: Do i have to unlock the bootloader?
Click to expand...
Click to collapse
Last Try,
Have you flashed The Blackhawk Kernel?
If not , Boot Into recovery, make a full wipe, flash seal ,Blackhawk Kernel ,full wipe again and reboot.
If this all not help ,post your prob at The Rom Thread.
bierma32 said:
Last Try,
Have you flashed The Blackhawk Kernel?
If not , Boot Into recovery, make a full wipe, flash seal ,Blackhawk Kernel ,full wipe again and reboot.
If this all not help ,post your prob at The Rom Thread.
Click to expand...
Click to collapse
I allready tried 3 roms(seal, 4.2.2 beta 2 and inspire) and all goes to the same result. Also, after installing the cwm i flash first the blackhawk kernel and android boots normally (stock rom with custom kernel) but custom rom with or without custom kernel wont boot.
I had similar problem try flashing seal v3.
I'm having a strange problem when I flash kernels (tried for Xcelerate and Beast kernels on both CM11, CM12.1), TWRP 2.8.6 gives the "e:Zip signature verification failed: 1" error message . The zip files for the kernels are perfectly fine - tested fine using archiver app and I don't face the same problem when flashing roms (MIUI/CM11/12/etc).
Turning zip verification off in TWRP allows the flashing process to complete normally but checking the kernel version under settings shows that it hasn't changed (still shows kratos/jsevi for CM11/12.1).
Any ideas?
barrack1 said:
I'm having a strange problem when I flash kernels (tried for Xcelerate and Beast kernels on both CM11, CM12.1), TWRP 2.8.6 gives the "e:Zip signature verification failed: 1" error message . The zip files for the kernels are perfectly fine - tested fine using archiver app and I don't face the same problem when flashing roms (MIUI/CM11/12/etc).
Turning zip verification off in TWRP allows the flashing process to complete normally but checking the kernel version under settings shows that it hasn't changed (still shows kratos/jsevi for CM11/12.1).
Any ideas?
Click to expand...
Click to collapse
FYI, i never ticked/marked the zip signature while flashing beast or xcelerate kernel, and all of them works fine with the rom.
after clean install, i reboot to rexovery and i flash the kernel and reboot, never wipe anything
presetz said:
FYI, i never ticked/marked the zip signature while flashing beast or xcelerate kernel, and all of them works fine with the rom.
after clean install, i reboot to rexovery and i flash the kernel and reboot, never wipe anything
Click to expand...
Click to collapse
I did a clean install several times with different rom-kernel combinations and I keep running into the same problem. I think its related my other problem of looping in recovery (twrp) after performing a factory reset in cm11/12.1.
barrack1 said:
I did a clean install several times with different rom-kernel combinations and I keep running into the same problem. I think its related my other problem of looping in recovery (twrp) after performing a factory reset in cm11/12.1.
Click to expand...
Click to collapse
did you flashed twrp recovery.img to boot option, instead of recovery option?
if that case, youll get looping to twrp, instead of system. IMO
presetz said:
did you flashed twrp recovery.img to boot option, instead of recovery option?
if that case, youll get looping to twrp, instead of system. IMO
Click to expand...
Click to collapse
I don't know what you mean there. I flashed twrp using fastboot.
I have no problems with using TWRP to flash customs roms multiple times (except for flashing kernels).
edit-
Steps I took to flash kernel-
- start twrp recovery and wipe everything except for external sdcard and usb otg
- flash rom cm11/12.1/etc
- wipe cache/dalvik
- reboot to system and check that everything is fine etc
- power off and start in twrp to flash kernel
- get error msg as stated in my OP
barrack1 said:
I don't know what you mean there. I flashed twrp using fastboot.
I have no problems with using TWRP to flash customs roms multiple times (except for flashing kernels).
edit-
Steps I took to flash kernel-
- start twrp recovery and wipe everything except for external sdcard and usb otg
- flash rom cm11/12.1/etc
- wipe cache/dalvik
- reboot to system and check that everything is fine etc
- power off and start in twrp to flash kernel
- get error msg as stated in my OP
Click to expand...
Click to collapse
sorry, just my experienced with twrp looping that i encountered once.
i dont know if it help, but i moved the kernel.zip in the internal storage before i flashed it.
edit: just curious, before you flashed kernel, had you double checked, if the zip verification was unmarked in twrp>setting ?
presetz said:
sorry, just my experienced with twrp looping that i encountered once.
i dont know if it help, but i moved the kernel.zip in the internal storage before i flashed it.
edit: just curious, before you flashed kernel, had you double checked, if the zip verification was unmarked in twrp>setting ?
Click to expand...
Click to collapse
I think so but I make sure zip verification is always toggled on in the install menu. There is no reason to turn it off since verification is very quick and doesn't cost anything.
But even when I turn it off, the kernel doesn't seem to have changed from what I see in the kernel version info under settings after I reboot the phone - as stated in the OP.
barrack1 said:
I think so but I make sure zip verification is always toggled on in the install menu. There is no reason to turn it off since verification is very quick and doesn't cost anything.
But even when I turn it off, the kernel doesn't seem to have changed from what I see in the kernel version info under settings after I reboot the phone - as stated in the OP.
Click to expand...
Click to collapse
okay, last i remembered,i once encountered no changed on kernel, but i saw some posting at xcelerate thread, that it had to flashed on top of stock boot.img, the file extracted from the rom.zip,
flashed the boot.img first then straight to flash the kernel.zip.
if you already tried that and still had the issued, then im wondering why too...
presetz said:
okay, last i remembered,i once encountered no changed on kernel, but i saw some posting at xcelerate thread, that it had to flashed on top of stock boot.img, the file extracted from the rom.zip,
flashed the boot.img first then straight to flash the kernel.zip.
if you already tried that and still had the issued, then im wondering why too...
Click to expand...
Click to collapse
Is the boot.img from CM11/12.1 or miui rom? From what I understand, the boot.img flash is only if the kernel is other than cm11/12.1 like Beast/Xcelerate/Carbon. Since I'm only on on CM11 or 12.1 on a clean flash without any other modifications theres no point in flashing boot.img (from CM11/12.1).
barrack1 said:
Is the boot.img from CM11/12.1 or miui rom? From what I understand, the boot.img flash is only if the kernel is other than cm11/12.1 like Beast/Xcelerate/Carbon. Since I'm only on on CM11 or 12.1 on a clean flash without any other modifications theres no point in flashing boot.img (from CM11/12.1).
Click to expand...
Click to collapse
yup, thats true, i have encountered that after clean install while still on cm12 and the procedure was worked for me.
presetz said:
yup, thats true, i have encountered that after clean install while still on cm12 and the procedure was worked for me.
Click to expand...
Click to collapse
Err what do you mean? Encountered what? Did you still have to flash boot.img from cm11/12.1 or miui?
barrack1 said:
Err what do you mean? Encountered what? Did you still have to flash boot.img from cm11/12.1 or miui?
Click to expand...
Click to collapse
sorry my mistaken, thought that my problem was the same with yours with no changed kernel after flashin custom kernel while back at cm12
and no, i didnt need to flashed boot.img first before custom kernel ever since cm12.1 clean install
Hi,
I have tried to install many custom roms but all get stuck on their own boot logos
eg
*Resurrection remix 5.6.5 marshmallow was stuck on its rr logo ( Tried installation with twrp 3.0, 2.4. 2.6 but still same thing)
*Cyanide 5.1 also gets stuck on its boot logo
Phone gets passes note 2 thing but gets stuck on respective roms logos i install
# Yes i Rooted phone before installation
# TWRP 3.0 installed
# Did clean installs (Formatted EVERYTHING and installed)(Read somewhere twrp cant format stock stuff properly, i dont know) Should i try different recovery? (Please suggest best to install RR Marshmallow)
# Presently I m on stock 4.4.2
# tried this too >> custom rom zip install >> SU Install >> Gapps >>restart (Did without SU install too but doesnt work that way too)
I got it SOLVED finally
HOW?
Yup sure i ll tell how
I followed the following steps
1. Flash stock rom ( I mean stock rom by odin, Not factory reset or anything (as that didnt work) and my baseband was also lost (showed 'Unknown'))
2. Didnt add anything to it (gmail account or any settings etc)
3. Booted it completely once again ( restarted after first boot)
4. got to Download mode
5. Rooted it using cf auto root ( for sgh-i317m as i m using same phone)
6. restarted
7. got to Download mode again
8. Flashed twrp 2.8.7.0 from Odin
9. restarted again
10. got to Recovery
11. Flashed Resurrection Marshmallow (I think 5.6.5)
12. Flashed SU manually after that
13. Flashed OpenGapps Mini 6.0
14. Wiped Dalvikcache / Cache
15. Reboot
16. Wait for about FIVE Mins and
VOILA....
Enjoying new Marshmallow
Hope this helps someone who is also stuck in my situation.
Thanks for all your help
are you sure that should work? you have i317 and as far as I know it differs from N7100 and N7105
I too am experiencing the same issue, I have an at&t SGH-i317
I tried latest TWRP as well as CWM and Philz recovery
I tried like 4 different ROM's some based off stock and some based of Cyanogen mods.
I even wiped cache and davlik cache after ROM install as suggested by some of the threads, I actually tried every combination I could think of and all ROM's get stuck on the boot logo splash screen.
Is there something I am missing or doing wrong, this is certainly the the first phone I tried this on.
yaro666 said:
are you sure that should work? you have i317 and as far as I know it differs from N7100 and N7105
Click to expand...
Click to collapse
I m not sure about it. Do they actually differ ? i317 and n7105 (My thoughts they are same, Actually ALL Canadian versions of note 2 are same)
xtacydima said:
I too am experiencing the same issue, I have an at&t SGH-i317
I tried latest TWRP as well as CWM and Philz recovery
I tried like 4 different ROM's some based off stock and some based of Cyanogen mods.
I even wiped cache and davlik cache after ROM install as suggested by some of the threads, I actually tried every combination I could think of and all ROM's get stuck on the boot logo splash screen.
Is there something I am missing or doing wrong, this is certainly the the first phone I tried this on.
Click to expand...
Click to collapse
Can this be because of stock kernel? Because i m still on stock kernel
And thats the only thing i didnt change, despite all other random changes in steps to follow to install custom rom.
First and foremost TWRP 3.0 might be your problem, Its buggy and doesnt work right some people couldnt install it and all others have had issues with flashing roms, I would downgrade twrp to 2.8.5 if I were you.
the only other thing I think you already said you did but when you wipe go to advanced wipe make sure system is checked so system, cache, delvik cache, and data...but I think mainly TWRP is probably your problem.
lsdhillon said:
Hi,
I have tried to install many custom roms but all get stuck on their own boot logos
eg
*Resurrection remix 5.6.5 marshmallow was stuck on its rr logo ( Tried installation with twrp 3.0, 2.4. 2.6 but still same thing)
*Cyanide 5.1 also gets stuck on its boot logo
Phone gets passes note 2 thing but gets stuck on respective roms logos i install
# Yes i Rooted phone before installation
# TWRP 3.0 installed
# Did clean installs (Formatted EVERYTHING and installed)(Read somewhere twrp cant format stock stuff properly, i dont know) Should i try different recovery? (Please suggest best to install RR Marshmallow)
# Presently I m on stock 4.4.2
# tried this too >> custom rom zip install >> SU Install >> Gapps >>restart (Did without SU install too but doesnt work that way too)
Click to expand...
Click to collapse
yaro666 said:
are you sure that should work? you have i317 and as far as I know it differs from N7100 and N7105
Click to expand...
Click to collapse
majicmazo said:
First and foremost TWRP 3.0 might be your problem, Its buggy and doesnt work right some people couldnt install it and all others have had issues with flashing roms, I would downgrade twrp to 2.8.5 if I were you.
the only other thing I think you already said you did but when you wipe go to advanced wipe make sure system is checked so system, cache, delvik cache, and data...but I think mainly TWRP is probably your problem.
Click to expand...
Click to collapse
I m gonna go to twrp 2.8.5. Hopefully it works. Will be back with results soon.
i get this error after installation (Using twrp 2.8.5.0 now)
"unmount of /system failed; no such volume"
Probably this is cause?
How to fix it?
and
I m using twrp for t0lte (i have SGH-i317m) I hope its all right with that.
lsdhillon said:
Can this be because of stock kernel? Because i m still on stock kernel
And thats the only thing i didnt change, despite all other random changes in steps to follow to install custom rom.
Click to expand...
Click to collapse
Actually yes I never updated the kernel, and now I am wondering if that is the reason why. Perhaps the latest ROM's need the latest kernel. Unfortunately, the links for that are down, if anyone can repost please.
[UPDATE]
I found the latest kernel and flashed it within Philz latest recovery and sure enough that did the trick, now I got two ROM's I tried and both booted fine. I guess that's the fix.
that's weird, I'm using stock kernel since the 1st day and never had boot problem. See if your emmc chip is sane or insane
xtacydima said:
Actually yes I never updated the kernel, and now I am wondering if that is the reason why. Perhaps the latest ROM's need the latest kernel. Unfortunately, the links for that are down, if anyone can repost please.
[UPDATE]
I found the latest kernel and flashed it within Philz latest recovery and sure enough that did the trick, now I got two ROM's I tried and both booted fine. I guess that's the fix.
Click to expand...
Click to collapse
Could you please guide me to stable risk-free custom kernel for my sgh-i317
yaro666 said:
that's weird, I'm using stock kernel since the 1st day and never had boot problem. See if your emmc chip is sane or insane
Click to expand...
Click to collapse
Stock kernel with latest 6.x ROM's? Only thing I can think of is your stock kernel was updated with an Android update, since this isn't my phone I din't know how on queue my family member who owns it was with updates. Everything is working fine now I just settled on a ROM after trying a few, so I think my emmc chip is fine.
---------- Post added at 03:20 PM ---------- Previous post was at 03:00 PM ----------
lsdhillon said:
Could you please guide me to stable risk-free custom kernel for my sgh-i317
Click to expand...
Click to collapse
Here is the kernel I downloaded (it's a zip so I flashed via Phil'z latest recovery)
http://d-h.st/JUm
Here is latest modem (same flashed via Philz)
http://d-h.st/WTp
xtacydima said:
Stock kernel with latest 6.x ROM's? Only thing I can think of is your stock kernel was updated with an Android update, since this isn't my phone I din't know how on queue my family member who owns it was with updates. Everything is working fine now I just settled on a ROM after trying a few, so I think my emmc chip is fine.
Click to expand...
Click to collapse
really stock kernel with MJ5 modem and old bootloader up until this year january, as I updated to RR 5.1.1 and then updated bl, modem to OC and flashed CM13
xtacydima said:
Stock kernel with latest 6.x ROM's? Only thing I can think of is your stock kernel was updated with an Android update, since this isn't my phone I din't know how on queue my family member who owns it was with updates. Everything is working fine now I just settled on a ROM after trying a few, so I think my emmc chip is fine.
---------- Post added at 03:20 PM ---------- Previous post was at 03:00 PM ----------
Here is the kernel I downloaded (it's a zip so I flashed via Phil'z latest recovery)
http://d-h.st/JUm
Here is latest modem (same flashed via Philz)
http://d-h.st/WTp
Click to expand...
Click to collapse
I flashed AGNI kernel but the results were still same. Now gonna flash http://d-h.st/JUm as xtacydima suggested(Thanks).
Hope it works.
Will be back with results soon.
Do i need to update modem? to install RR (Marshmallow)?
With http://d-h.st/JUm as xtacydima suggested
It doesnt pass note 2 logo
Just goes blank after note 2 logo, So i think it isnt supported.
i m on 4.4.2 stock now.
Another thing i note is that my baseband is "unknown".
Any suggestions?
I got it SOLVED finally
HOW?
Yup sure i ll tell how
I followed the following steps
1. Flash stock rom ( I mean stock rom by odin, Not factory reset or anything (as that didnt work) and my baseband was also lost (showed 'Unknown'))
2. Didnt add anything to it (gmail account or any settings etc)
3. Booted it completely once again ( restarted after first boot)
4. got to Download mode
5. Rooted it using cf auto root ( for sgh-i317m as i m using same phone)
6. restarted
7. got to Download mode again
8. Flashed twrp 2.8.7.0 from Odin
9. restarted again
10. got to Recovery
11. Flashed Resurrection Marshmallow (I think 5.6.5)
12. Flashed SU manually after that
13. Flashed OpenGapps Mini 6.0
14. Wiped Dalvikcache / Cache
15. Reboot
16. Wait for about FIVE Mins and
VOILA....
Enjoying new Marshmallow
Hope this helps someone who is also stuck in my situation.
Thanks for all your help
Not my work but it works now.
How to
Reboot in recovery
Wipe device
Flash Rom and kernel:
Download for rom:
Flash this after:
Reboot
Recommend using twrp 3.0.0.1
what about the hardware keys? do they work with moar rom and this kernel or do we need virtual hardware keys?
FingerBlastJ said:
what about the hardware keys? do they work with moar rom and this kernel or do we need virtual hardware keys?
Click to expand...
Click to collapse
Kernel fixes hardware issues
and if I'm on note 5 moar rom with patch.... no issue flashing right?
Sky-high made us a kernel? Sweet sadistic smiles, success! So happy. Anyone know if it'll work like the LP patch did for note roms, or does more need to happen first? Or do people just need to start trying and report back?
-edit-
Clicked the link and saw it was a note 5 Rom. What can I say, I was excited!
Blzfrost said:
Sky-high made us a kernel? Sweet sadistic smiles, success! So happy. Anyone know if it'll work like the LP patch did for note roms, or does more need to happen first? Or do people just need to start trying and report back?
-edit-
Clicked the link and saw it was a note 5 Rom. What can I say, I was excited!
Click to expand...
Click to collapse
Just flash Rom and kernel everything will work.
MonkeyAround said:
Just flash Rom and kernel everything will work.
Click to expand...
Click to collapse
Oh I'm setting everything up right now for the flash! I'm so excited. Once I realized you linked to a note 5 Rom most of my questions got answered. My favorite part, the kernel was posted on my bday.
i tried wiping and clearing cache then flashing the rom and the kernel. nothing actually happens to my phone. i end up on the same home screen and apps i had installed on moar 5.1.1 with note 5 patch.
any ideas why wiping my phone doesnt work on twrp 3.0.0.0?
FingerBlastJ said:
i tried wiping and clearing cache then flashing the rom and the kernel. nothing actually happens to my phone. i end up on the same home screen and apps i had installed on moar 5.1.1 with note 5 patch.
any ideas why wiping my phone doesnt work on twrp 3.0.0.0?
Click to expand...
Click to collapse
Update your TWRP.
https://dl.twrp.me/zenltespr/
yea I tried doing that with Odin and it would freeze mid way. I also tried flashing a twrp update zip file on twrp and that didn't work either.
you think I should flash with flash fire?
bricked my phone by trying to flash newer version of twrp with twrp manager
been trying to flash unbrick tar and pit file to get back up and running but its not working.
any help is much appreciated
fixed the brick by flashing new recovery in Odin, now on 3.0.2. still can't get the phone to wipe out install new rom and kernel
FingerBlastJ said:
fixed the brick by flashing new recovery in Odin, now on 3.0.2. still can't get the phone to wipe out install new rom and kernel
Click to expand...
Click to collapse
Have you checked for root with root checker? I have lost root access a few times in the past?
yea I just checked with root checker and I have root access.
I've never had this happen to me... weird
anything else you can think of?
FingerBlastJ said:
yea I just checked with root checker and I have root access.
I've never had this happen to me... weird
anything else you can think of?
Click to expand...
Click to collapse
Last thing I can think of is when opening TWRP the first time. It asks if you want to make the system 'read only'. Did you select No?
I never got that message when I flashed twrp 3.0.2 to unblock... how do I make it show up?
FingerBlastJ said:
I never got that message when I flashed twrp 3.0.2 to unblock... how do I make it show up?
Click to expand...
Click to collapse
Not sure. You can click mount and see what is mounted. I am not sure that will work. I am not sure exactly what you are trying to wipe, but mount the items you are attempting to wipe and make sure the read-only is unchecked.
Try this:
Check to see if oem is checked
Re-root via root tar/odin
twrp 3.0.0.1 from edge files post in general
Backup stock
Wipe
Flash Moar
Don't reboot
Flash skyhigh kernel
Flash xposed(don't have to)
Reboot
Allow it to boot loop a couple time (from sky kernel)
Give 5-10 minutes to boot
I just did it with no issues and I've personally had more luck with 3.0.0.1 than any of the others.
heres my issue...twrp doesnt do anything for me (all versions) whether i wipe or install
so i used flashfire to flash the rom and the kernel at once and it finally displayed aroma installer (wouldnt get that in twrp)
however, after it in stalled i got stuck on boot screen
the only fix for this was flashing unbrick aok3 tar file which brought me to stock
i put on twrp as a recovery again starting fresh unrooted and it still doesnt respond to any of my commands
i think i will try flash fire on stock one more time and see what happens since its the only thing that is responding
FingerBlastJ said:
heres my issue...twrp doesnt do anything for me (all versions) whether i wipe or install
so i used flashfire to flash the rom and the kernel at once and it finally displayed aroma installer (wouldnt get that in twrp)
however, after it in stalled i got stuck on boot screen
the only fix for this was flashing unbrick aok3 tar file which brought me to stock
i put on twrp as a recovery again starting fresh unrooted and it still doesnt respond to any of my commands
i think i will try flash fire on stock one more time and see what happens since its the only thing that is responding
Click to expand...
Click to collapse
Your on Lp bootloader that's your issue.
Download Marshmallow tar from the general post I made for rooting Bpg1.
Flash tar and follow post.
twrp. 3.0.x.x is more for marshmallow. You need to be on 6.0.1 not 5.1.1.
Don't use fireflash on this device.
Fireflash is more for phones with locked bootloaders like Verizon s4 on the of1 update.
Fireflash isn't really up to date with our phone and could easily brick your device.
Hello dear friends,
I had been using some custom roms for a while like lineage os, cm, resurrection etc.Then i wanted to change it to a 4.4 rom.Once i flashed a stock rom by odin.Then i tired to use Eclipse.I have been using it without a problem.But now i want to upgrade the phone again.
-And i tried to flash different roms but i have the same problem.It passes SAMSUNG screen and shows ROM's flash.But it stucks in there.It keeps moving but nothing more.The rom doesn't start the homescreen.I tried to factory reset, wipe cache and dalvik cache.But they also doesn't work at all.I wait about half and hour or 1 hour, Once i tried to let it work overnight even.But doesn't work.Now i try to flash Cosmic OS but the problem still exists.I have a Eclipse rom backup and i restore it and it works.I use TWRP recovery on the phone.
-So what the problem might be?How can i fix it?
I recommend flashing back to the latest stock ROM, factory reset, and start over with TWRP.
audit13 said:
I recommend flashing back to the latest stock ROM, factory reset, and start over with TWRP.
Click to expand...
Click to collapse
Thank you it worked.I just want to explain the steps to give some information for the others who got the same problem.
-Connect the phone to the pc and flash a stock rom by odin or heimdall in linux
-Then wait for the rom to start.
-Open stock recovery mod (not TWRP or CWM Recovery)
-Format all data
-Flash a custom recovery (I use TWRP)
-And flash the custom rom as instructions.
And it works for me.Thank you again.
stranger_88 said:
Thank you it worked.I just want to explain the steps to give some information for the others who got the same problem.
-Connect the phone to the pc and flash a stock rom by odin or heimdall in linux
-Then wait for the rom to start.
-Open stock recovery mod (not TWRP or CWM Recovery)
-Format all data
-Flash a custom recovery (I use TWRP)
-And flash the custom rom as instructions.
And it works for me.Thank you again.
Click to expand...
Click to collapse
Glad you got it working.
Thanks for posting your method.
same problem
i'm gettin the same problem...
in download mode there are few lines as follows:
odin mode
prduct name:gt-n7100
current binary:Custom
System Status:Custom
knox warranty void: 1
AP SWREV: A2
PLSSS HELP
ShubhamS156 said:
i'm gettin the same problem...
in download mode there are few lines as follows:
odin mode
prduct name:gt-n7100
current binary:Custom
System Status:Custom
knox warranty void: 1
AP SWREV: A2
PLSSS HELP
Click to expand...
Click to collapse
Which rom you are using to flash?
Is the rom exactly for your phone model? (For eg, N7100 rom cannot be used for N7105)
thomas140 said:
Which rom you are using to flash?
Is the rom exactly for your phone model? (For eg, N7100 rom cannot be used for N7105)
Click to expand...
Click to collapse
Yep ...it's for N7100 only.... DotOs 7.1.2 by Santosh
---------- Post added at 08:20 AM ---------- Previous post was at 08:16 AM ----------
stranger_88 said:
Hello dear friends,
I had been using some custom roms for a while like lineage os, cm, resurrection etc.Then i wanted to change it to a 4.4 rom.Once i flashed a stock rom by odin.Then i tired to use Eclipse.I have been using it without a problem.But now i want to upgrade the phone again.
-And i tried to flash different roms but i have the same problem.It passes SAMSUNG screen and shows ROM's flash.But it stucks in there.It keeps moving but nothing more.The rom doesn't start the homescreen.I tried to factory reset, wipe cache and dalvik cache.But they also doesn't work at all.I wait about half and hour or 1 hour, Once i tried to let it work overnight even.But doesn't work.Now i try to flash Cosmic OS but the problem still exists.I have a Eclipse rom backup and i restore it and it works.I use TWRP recovery on the phone.
-So what the problem might be?How can i fix it?
Click to expand...
Click to collapse
Stranger_88....try doing a complete advanced wipe using Twrp..and then install a rom
You said DotOS 7.1.2, it is custom rom and I think it needs to be install using TWRP. And also, need to perform wipe in TWRP before reboot. Otherwise, it will stuck at Samsung logo boot loop.
Solved
thomas140 said:
Which rom you are using to flash?
Is the rom exactly for your phone model? (For eg, N7100 rom cannot be used for N7105)
Click to expand...
Click to collapse
Dude I got it working. Use Heimdall in Linux , my phone was detected in Heimdall and I followed the simple instructions there and flashed a new rom.