Screen shows glitch logo then shows recovery manager and reboots doing the same thing i a loop
I flashed 2 other captivates the same exact way except this time i use CM7 whereas before i used a different rom
ISSUE SOLVED BY FLASHING STOCK ROM PACKAGE
Try
Code:
adb wait-for-device reboot recovery
That should get you out of the loop.
i just hooked up the phone and i got into download mode
so i guess i can flash another rom
xboxhaxorz said:
i just hooked up the phone and i got into download mode
so i guess i can flash another rom
Click to expand...
Click to collapse
That works too.
can i use any rom and just use the pda method then start?
xboxhaxorz said:
can i use any rom and just use the pda method then start?
Click to expand...
Click to collapse
As long as you repartition.
all the roms i have when i go to the directory do not show up, i guess because they are zip files, can i unzip a rom and rezip it to tar or is there a rom that is in tar file?
xboxhaxorz said:
all the roms i have when i go to the directory do not show up, i guess because they are zip files, can i unzip a rom and rezip it to tar or is there a rom that is in tar file?
Click to expand...
Click to collapse
No, you can't zip then tar. Most ROM's aren't tar, I don't know which would be.
ahh
cause i got another phone that is stuck in the at&t logo so i figured i could just reflash that too
guess i will get the sdk and try the method you mentioned
tkx
xboxhaxorz said:
ahh
cause i got another phone that is stuck in the at&t logo so i figured i could just reflash that too
guess i will get the sdk and try the method you mentioned
tkx
Click to expand...
Click to collapse
What OS is your computer?
Download a stock ROM, as they will repartition your phone for you....
windows 7 is my OS
I had the same problem when I switched from CM7 Nightly to CM7. 1 stable. The issue was the Glitch kernel. Try flashing the HL-DEV kernel after factory reset and wiping cache and dalvik cache. Then reflash CM7.
Sent from my SGH-I897 using XDA App
yea but i need to get into the system to do that
b-eock said:
Download a stock ROM, as they will repartition your phone for you....
Click to expand...
Click to collapse
solved just started over rerooting and installing another rom
Related
hey guys,
I flashed the "voodooChargeKernel4" tar file win Odin. Then I flashed the CWR recovery through Odin ( i know I ****ed up). It wouldnt boot and was stuck on the samsung screen. I pulled the battery and went back into Odin to reflash the voodoochargekernel again. Now it's stuck on a screen with a phone, a computer and orange triangle.
Well i got the same tar file to flash in Odin by switching USB ports, but now Im still stuck on the samsung screen
crap..i dont know what to do. I used the CWR recovery files from this thread on someone's recommendation: http://forum.xda-developers.com/showthread.php?t=1111486. Now the phone wont turn on at all except download mode and anything I flash says fail.
Odin is flaky you may need to try a different USB port.
If that does not work try to remove the device in device manager and unplugging the phone and plugging it back in to the computer,.
And flash the below package
http://forum.xda-developers.com/show....php?t=1116867
EE4 Stock.
uefcommad said:
Odin is flaky you may need to try a different USB port.
If that does not work try to remove the device in device manager and unplugging the phone and plugging it back in to the computer,.
And flash the below package
http://forum.xda-developers.com/show....php?t=1116867
EE4 Stock.
Click to expand...
Click to collapse
that link didn twork. Do you have another?
Breakthecycle2 said:
that link didn twork. Do you have another?
Click to expand...
Click to collapse
try this
http://forum.xda-developers.com/showthread.php?t=1116867
uefcommad said:
try this
http://forum.xda-developers.com/showthread.php?t=1116867
Click to expand...
Click to collapse
thank but that didnt work either. Its in an endless boot into recovery for some reason.
I had the problem, except mine wasn't going into recovery; it rebooted after every boot animation.
What worked for me was, using Odin, re-flashing the Kernel, unplug the phone, plug the phone in again, and then flashing Altered Beast, then turning the phone on. It didn't work if i tried them one at a time.
after u get the phone in download mde. re-install the battery and then flash via odin.
if your getting bootloop then try in recover to wipe data
uefcommad said:
if your getting bootloop then try in recover to wipe data
Click to expand...
Click to collapse
Yeah did that too. went rigth back into recovery. I just bought and did a **** move by bringing it back to best buy and got a new one.
Breakthecycle2 said:
Yeah did that too. went rigth back into recovery. I just bought and did a **** move by bringing it back to best buy and got a new one.
Click to expand...
Click to collapse
Well, mine's doing the same thing his was, but I'm not able to return mine to Best Buy. Any more ideas?
Grizzld said:
Well, mine's doing the same thing his was, but I'm not able to return mine to Best Buy. Any more ideas?
Click to expand...
Click to collapse
What did you flash exactly?
Breakthecycle2 said:
What did you flash exactly?
Click to expand...
Click to collapse
I flashed Stock Rooted ED1 (downgrade from ED2) from here:
http://forum.xda-developers.com/showthread.php?t=1085190
I'm currently waiting on this to be fixed:
http://rootzwiki.com/showthread.php?481-LEAK-STOCK-ED2-Droid-Charge-FULL-ODIN!
Grizzld said:
I flashed Stock Rooted ED1 (downgrade from ED2) from here:
http://forum.xda-developers.com/showthread.php?t=1085190
I'm currently waiting on this to be fixed:
http://rootzwiki.com/showthread.php?481-LEAK-STOCK-ED2-Droid-Charge-FULL-ODIN!
Click to expand...
Click to collapse
That may not work. I had that DL already.
have you tryed this package?
Stock EE4
http://forum.xda-developers.com/showthread.php?t=1116867
i am running it now
uefcommad said:
have you tryed this package?
Stock EE4
http://forum.xda-developers.com/showthread.php?t=1116867
i am running it now
Click to expand...
Click to collapse
Yup, did that too. That allowed my phone to actually boot, but then I got stuck in recovery.
HI..
My tab is stuck in BOOTLOOP..
I've already tried to reflash the cwm 10 and wipe cache several times.
and wipe data(which i cannot do, because it automatically reboot again)
i tried pressing the power button and volume down" and press continue..
now, my phone is in downloading process.. i have no idea what am i downloading now..
PLEASE HELP!!
THXX
This might help you: http://forum.xda-developers.com/showpost.php?p=30645468&postcount=1140
help
s4kura88 said:
HI..
My tab is stuck in BOOTLOOP..
I've already tried to reflash the cwm 10 and wipe cache several times.
and wipe data(which i cannot do, because it automatically reboot again)
i tried pressing the power button and volume down" and press continue..
now, my phone is in downloading process.. i have no idea what am i downloading now..
PLEASE HELP!!
THXX
Click to expand...
Click to collapse
same issue here, i did some mistakes like you did too... tried reflashing stock roms from sammobile from stock HC to ICS.. but no luck.. got my tab plus GT P6200 is now in bootloop.. saw someone fixed his bootloop by using odin thru using .pit file, csc, bootloader, pda and repartition checked... i wanted to try it but i cant find my tab's bootloader and csc files... if anyone knows where can i get those files, i badly needed your help too... thanks in advance...
Just make sure it's not just a corrupted data partition first before doing something as drastic as repartition.
re
rendler said:
Just make sure it's not just a corrupted data partition first before doing something as drastic as repartition.
Click to expand...
Click to collapse
how will i know if i got more problem than corrupted partition? any signs or can u site a lil more examples bout it sir?
zepoy said:
how will i know if i got more problem than corrupted partition? any signs or can u site a lil more examples bout it sir?
Click to expand...
Click to collapse
You'll know that it's more than a corrupted partition when running disk scan/fix (using e2fsck from an adb shell through recovery) and then afterwards flashing the rom again doesn't work.
zepoy said:
same issue here, i did some mistakes like you did too... tried reflashing stock roms from sammobile from stock HC to ICS.. but no luck.. got my tab plus GT P6200 is now in bootloop.. saw someone fixed his bootloop by using odin thru using .pit file, csc, bootloader, pda and repartition checked... i wanted to try it but i cant find my tab's bootloader and csc files... if anyone knows where can i get those files, i badly needed your help too... thanks in advance...
Click to expand...
Click to collapse
U know when u wipe data via stock recovery on ICS.....that will make ur device hardbrick..but if u wipe via CWM, then its safe..
Sent from my GT-P6200 using xda premium
Member90 said:
U know when u wipe data via stock recovery on ICS.....that will make ur device hardbrick..but if u wipe via CWM, then its safe..
Sent from my GT-P6200 using xda premium
Click to expand...
Click to collapse
i believe thats the biggest mistake i did when i try to flash cm10 on my device... i forgot to use cwm recovery when i wipe data/factory reset... from what i remembered i only use cwm when i flashed cm10... can anyone give me some advice to make things work again
rendler said:
This might help you: http://forum.xda-developers.com/showpost.php?p=30645468&postcount=1140
Click to expand...
Click to collapse
zepoy said:
same issue here, i did some mistakes like you did too... tried reflashing stock roms from sammobile from stock HC to ICS.. but no luck.. got my tab plus GT P6200 is now in bootloop.. saw someone fixed his bootloop by using odin thru using .pit file, csc, bootloader, pda and repartition checked... i wanted to try it but i cant find my tab's bootloader and csc files... if anyone knows where can i get those files, i badly needed your help too... thanks in advance...
Click to expand...
Click to collapse
rendler said:
Just make sure it's not just a corrupted data partition first before doing something as drastic as repartition.
Click to expand...
Click to collapse
i really don't understand about ADB..
i haven't installed all that stuff before..
how to know that it is just corrupted data partition??
Try Heimdall?
What method did you use? You tried flashing CWM 6.01.0 and then flashing CM 10? what version and what build? Maybe you want to flash another build in case it's just a problem in certain build?
I did mine using Heimdall, Give this a go
http://forum.xda-developers.com/showthread.php?t=1517934
for windows you can find the step here http://forum.xda-developers.com/showpost.php?p=29104577&postcount=29
Take a deep breath, read the instruction once again and then try, Good luck!
Unitedforlife said:
What method did you use? You tried flashing CWM 6.01.0 and then flashing CM 10? what version and what build? Maybe you want to flash another build in case it's just a problem in certain build?
I did mine using Heimdall, Give this a go
http://forum.xda-developers.com/showthread.php?t=1517934
for windows you can find the step here http://forum.xda-developers.com/showpost.php?p=29104577&postcount=29
Take a deep breath, read the instruction once again and then try, Good luck!
Click to expand...
Click to collapse
hmm
i use the CM 10 30Sept build using the CM Recovery (the one, that i press power and volume up button)
then i try wipe cache, install the CM10.. but it doesn't work..
yeah.. i thought if i reinstall maybe it will work ><
okay.. will try now thx a lot
s4kura88 said:
i really don't understand about ADB..
i haven't installed all that stuff before..
how to know that it is just corrupted data partition??
Click to expand...
Click to collapse
ADB (Android Debug Bridge) comes with the Android SDK. Basically you boot the device into CWM recovery then connect the device to a computer using a USB cable and run the command 'adb shell' which will then give you a shell prompt where you can send commands directly to be run on the device.
If you're getting reboots from trying to wipe certain partitions repeatedly from CWM then that's a pretty strong indication that you have a corrupted partition.
Unitedforlife said:
What method did you use? You tried flashing CWM 6.01.0 and then flashing CM 10? what version and what build? Maybe you want to flash another build in case it's just a problem in certain build?
I did mine using Heimdall, Give this a go
http://forum.xda-developers.com/showthread.php?t=1517934
for windows you can find the step here http://forum.xda-developers.com/showpost.php?p=29104577&postcount=29
Take a deep breath, read the instruction once again and then try, Good luck!
Click to expand...
Click to collapse
I've tried Heimdall..
but i got this
ERROR: Failed to access device. libusb error: -12
any suggestion?
rendler said:
ADB (Android Debug Bridge) comes with the Android SDK. Basically you boot the device into CWM recovery then connect the device to a computer using a USB cable and run the command 'adb shell' which will then give you a shell prompt where you can send commands directly to be run on the device.
If you're getting reboots from trying to wipe certain partitions repeatedly from CWM then that's a pretty strong indication that you have a corrupted partition.
Click to expand...
Click to collapse
I've tried this, but i'm really confused.. i've already installed adb and adb shell..
how to write this?
umount /cache
e2fsck -cy /dev/block/emmcblk0p7
e2fsck -cy /dev/block/emmcblk0p9
e2fsck -cy /dev/block/emmcblk0p10
do i need to put, ....\adb shell<umount /cache> or something?
thx a LOT!!:laugh::laugh:
What OS are you running? Windows? do make sure you follow the README and install the drivers to your computer.
4. Install the driver using zadig.exe as noted in the readme. BUT for me, P6200 usb driver is stated as Gadget Serial in the list. (not samsung usb composite)
Unitedforlife said:
What OS are you running? Windows? do make sure you follow the README and install the drivers to your computer.
4. Install the driver using zadig.exe as noted in the readme. BUT for me, P6200 usb driver is stated as Gadget Serial in the list. (not samsung usb composite)
Click to expand...
Click to collapse
i use windows..
yuppp.. i've already tried that..
the flash is working.. after finish flashing... it is bootloop again..
now, it appear samsung logo over and over again ><
never mind..
i tried wipe data and cache and it WORKS!!!
THX A LOTTTT!!!
zepoy said:
i believe thats the biggest mistake i did when i try to flash cm10 on my device... i forgot to use cwm recovery when i wipe data/factory reset... from what i remembered i only use cwm when i flashed cm10... can anyone give me some advice to make things work again
Click to expand...
Click to collapse
read this
http://forum.xda-developers.com/showthread.php?t=1517934
hope you find a solution.
---------- Post added at 10:18 PM ---------- Previous post was at 09:20 PM ----------
s4kura88 said:
i use windows..
yuppp.. i've already tried that..
the flash is working.. after finish flashing... it is bootloop again..
now, it appear samsung logo over and over again ><
never mind..
i tried wipe data and cache and it WORKS!!!
THX A LOTTTT!!!
Click to expand...
Click to collapse
great! sometimes simple re wipe and re flashing did the trick.
i made a mistake (i think) with flashing a cutom rom and now splash screen (name of device) is messed up
if someone has a idea on how to fix it, please let me know...
Thanks
DutchGlory said:
i made a mistake (i think) with flashing a cutom rom and now splash screen (name of device) is messed up
if someone has a idea on how to fix it, please let me know...
Thanks
Click to expand...
Click to collapse
You are more likely going to get help if you post in detail your issue, what exact model note you have, what custom rom and recovery you installed, what version of odin your using.
Give as much detail as you can............
RE: Repair Splash screen GT-N8000
kkretch said:
You are more likely going to get help if you post in detail your issue, what exact model note you have, what custom rom and recovery you installed, what version of odin your using.
Give as much detail as you can............
Click to expand...
Click to collapse
Well i have the GT-N8000 an i used ODIN 3.0.7 flashing ClockWorkMod Recovery here:
forum.xda-developers - show thread 2102677
after that i flashed CyanoGenMod ROM 10.2 Nightly ("cm-10.2-20131221-NIGHTLY-n8000.zip") Here
download.cyanogenmod.org device GT-N8000
I tried to restore splash sreen by flashing a stock ROM N8000XXCMF1_N8000PHNCMG1_PHN again... didden't work...
so any other thoughts are welcome...
The initial Samsung splash is in the kernel .
Suggest in recovery format data system cache and sdcard .
Boot to download mode flash stock rom via odin .
JJEgan said:
The initial Samsung splash is in the kernel .
Suggest in recovery format data system cache and sdcard .
Boot to download mode flash stock rom via odin .
Click to expand...
Click to collapse
So i need to look for separate kernel file. a stock rom doesn't have a kernel, only basic system files...
DutchGlory said:
So i need to look for separate kernel file. a stock rom doesn't have a kernel, only basic system files...
Click to expand...
Click to collapse
If a stock rom has no kernel in your view i suggest you read the faqs and guides before flashing anything ever again .
Kernel - This is always supplied with a ROM. It is the beating heart of Android. The ROM cannot function without the kernel. Since all ROMs include a kernel, if you're using a custom Kernel then flash a ROM, you will need to reflash the kernel again.
DutchGlory said:
Well i have the GT-N8000 an i used ODIN 3.0.7 flashing ClockWorkMod Recovery here:
forum.xda-developers - show thread 2102677
after that i flashed CyanoGenMod ROM 10.2 Nightly ("cm-10.2-20131221-NIGHTLY-n8000.zip") Here
download.cyanogenmod.org device GT-N8000
I tried to restore splash sreen by flashing a stock ROM N8000XXCMF1_N8000PHNCMG1_PHN again... didden't work...
so any other thoughts are welcome...
Click to expand...
Click to collapse
Can you please tell us exactly how you flashed the stock ROM
kkretch said:
Can you please tell us exactly how you flashed the stock ROM
Click to expand...
Click to collapse
with ODIN i usually dont have any problems with flashing roms. Not where exactly the splash screen is installed...
but with a rooted rom things can go bad. Normally when you flash a rom the splash screen stays unaffected.
For some reason it was damaged. so i need to find a way to repair it... not easy ....
DutchGlory said:
with ODIN i usually dont have any problems with flashing roms. Not where exactly the splash screen is installed...
but with a rooted rom things can go bad. Normally when you flash a rom the splash screen stays unaffected.
For some reason it was damaged. so i need to find a way to repair it... not easy ....
Click to expand...
Click to collapse
When you tried to flash to factory firmware did odin give you a message of pass or fail?
When you flashed to factory ROM did it actually install the factory firmware?
Have you have tried other versions of odin.......a copy of Odin3 v1.85 in attachment, if you want to try it.
kkretch said:
When you tried to flash to factory firmware did odin give you a message of pass or fail?
When you flashed to factory ROM did it actually install the factory firmware?
Have you have tried other versions of odin.......a copy of Odin3 v1.85 in attachment, if you want to try it.
Click to expand...
Click to collapse
i never had a problem with 3.0.7 i even tried "mobile ODIN"
DutchGlory said:
i never had a problem with 3.0.7 i even tried "mobile ODIN"
Click to expand...
Click to collapse
What actually happens when you say the spash screen is messed up?
Does the tablet actually start? Have you tried flashing another custom touch wiz based firmware like Revolution HD or even Omni rom?
I'm stuck in a boot loop after replacing my build.prop file, I replaced it with my own stock unedited one that I made a back up of with the one I edited with those RAM fixes. That did nothing and made my phone even slower so I used ES explorer and moved my stock file to the system folder and did an overwrite. Now my phone is stuck in a bootloop. I'm rooted not running a custom rom or recovery. Is there any way I can get this working without doing a factory reset? Yes I already tried wiping cache.
EDIT: DID A FACTORY RESET AND WIPED CACHE STILL STUCK IN BOOTLOOP.
st0j said:
I'm stuck in a boot loop after replacing my build.prop file, I replaced it with my own stock unedited one that I made a back up of with the one I edited with those RAM fixes. That did nothing and made my phone even slower so I used ES explorer and moved my stock file to the system folder and did an overwrite. Now my phone is stuck in a bootloop. I'm rooted not running a custom rom or recovery. Is there any way I can get this working without doing a factory reset? Yes I already tried wiping cache.
EDIT: DID A FACTORY RESET AND WIPED CACHE STILL STUCK IN BOOTLOOP.
Click to expand...
Click to collapse
always you have to do a nandroid backup for this case, but if you don't have the only way to fix this problem is flashing de stock firmware.
jah2110 said:
always you have to do a nandroid backup for this case, but if you don't have the only way to fix this problem is flashing de stock firmware.
Click to expand...
Click to collapse
How exactly do I go about doing this as I dont have a custom recovery or anything?
st0j said:
How exactly do I go about doing this as I dont have a custom recovery or anything?
Click to expand...
Click to collapse
only need to put the phone in download mode and flash the stock firmware with Odin.
jah2110 said:
only need to put the phone in download mode and flash the stock firmware with Odin.
Click to expand...
Click to collapse
Would you recommend the original stock firmware or using a custom ROM?
st0j said:
Would you recommend the original stock firmware or using a custom ROM?
Click to expand...
Click to collapse
first you have to get out of that situation, that mean you need a stock firm. Later read tutorials to install a custom rom, because if you have problems modification build.prop installing a custom rom is more harder. Download and install the stock firmware.
jah2110 said:
first you have to get out of that situation, that mean you need a stock firm. Later read tutorials to install a custom rom, because if you have problems modification build.prop installing a custom rom is more harder. Download and install the stock firmware.
Click to expand...
Click to collapse
Agreed. I'm still curious how I managed to put my phone into a bootloop by restoring my own build.prop file.
While using odin to flash firmware my usb connection kept cunning in and out for some reason I dont know why I even installed the updates. And it failed. Now I cant get rid of "An error has occured while updating the device software use emergency........" screen.... Now what.
st0j said:
While using odin to flash firmware my usb connection kept cunning in and out for some reason I dont know why I even installed the updates. And it failed. Now I cant get rid of "An error has occured while updating the device software use emergency........" screen.... Now what.
Click to expand...
Click to collapse
ttry to conect to kies and do a emergency restore.
here you have a video.
http://m.youtube.com/watch?v=UEnm5TU5KMw
I got back into download mode, and now it gives me an error saying it cant open serial(COM) port.
st0j said:
I got back into download mode, and now it gives me an error saying it cant open serial(COM) port.
Click to expand...
Click to collapse
Get into download mode, use odin to flash back the stock firmware.
jah2110 said:
ttry to conect to kies and do a emergency restore.
here you have a video.
http://m.youtube.com/watch?v=UEnm5TU5KMw
Click to expand...
Click to collapse
I got back into download mode, and now it gives me an error saying it cant open serial(COM) port.
Saafir said:
Did you make sure permissions was set correctly after the replacement? ALWAYS check them after moving crucial system files. build.prop should be set at rw-r-r (0644)
Click to expand...
Click to collapse
I got it to work, used another USB cable and odin finished installing it after 20 tries of USB fails.
What is the proper way to install the note rom on my galaxy j7t im having problems do i root my phone first or when i flash the rom will it root it since it has supersu on it i get stuck on the booting part the note 7 comes up but thats it it keeps flashing then it goes to a black screen and nothing happens please help me out if anyone can thanks :crying::crying::crying:
Ctrterrell said:
What is the proper way to install the note rom on my galaxy j7t im having problems do i root my phone first or when i flash the rom will it root it since it has supersu on it i get stuck on the booting part the note 7 comes up but thats it it keeps flashing then it goes to a black screen and nothing happens please help me out if anyone can thanks :crying::crying::crying:
Click to expand...
Click to collapse
Flash the rom in TWRP then before exiting TWRP flash Messi's permissive kernel. It takes about 10 minutes to boot and some features won't work (wifi, hot-spot, camera and VOLTE). Hope this helps.
Metabolic12 said:
Flash the rom in TWRP then before exiting TWRP flash Messi's permissive kernel. It takes about 10 minutes to boot and some features won't work (wifi, hot-spot, camera and VOLTE). Hope this helps.
Click to expand...
Click to collapse
Dang no WiFi so if I wanna install version 2 do you know if these features still won't work or would I even have to flash the kernel for the note rom version 2
Ctrterrell said:
Dang no WiFi so if I wanna install version 2 do you know if these features still won't work or would I even have to flash the kernel for the note rom version 2
Click to expand...
Click to collapse
I've gotten version 2 and 3 to boot on my J7, but the same issues showed in both releases. And yes you have to flash the kernel. Slight differences in the J700F/M/H and our T variant. This is why the Enigma Rom and CM13 (or any other kernel specific build) will never flash and boot without some internal tweaking.
Metabolic12 said:
I've gotten version 2 and 3 to boot on my J7, but the same issues showed in both releases. And yes you have to flash the kernel. Slight differences in the J700F/M/G and our T variant. This is why the Enigma Rom and CM13 (or any other kernel specific build) will never flash and boot without some internal tweaking.
Click to expand...
Click to collapse
OK thanks for your help ima try it now and see what happens and let you know
Ctrterrell said:
OK thanks for your help ima try it now and see what happens and let you know
Click to expand...
Click to collapse
Make a Nandroid before you flash it, just to be safe. If it works just hit the thanks button bro, good luck.
Metabolic12 said:
Make a Nandroid before you flash it, just to be safe. If it works just hit the thanks button bro, good luck.
Click to expand...
Click to collapse
Well I tried I installed the rom then tried to flash the kernel like how you said and it said fail
Ctrterrell said:
Well I tried I installed the rom then tried to flash the kernel like how you said and it said fail
Click to expand...
Click to collapse
Give me your step by step and I'll see if I can help you.
Well I wipe the data system and cache before I installed the rom then afterwards I installed it then I flashed the kernel and it said something bout permission was removed since it couldn't be installed but I will take a pic from my tablet real fast to show you what I was talking about
Metabolic12 said:
Give me your step by step and I'll see if I can help you.
Click to expand...
Click to collapse
This
I forgot to use Odin lol mybad
Ctrterrell said:
This
Click to expand...
Click to collapse
Try this. Take your external SD card and put it in your tablet. Go to Messi's thread for the max kernel in J7T development and download the boot.img not the boot.tar.md5. Finish the download then extract the zip in your external SD card. Put your SD card in your phone, boot into TWRP. Now mount system, cache, art/dalvik, data and internal storage (you may need to format data to access data) now wipe them. Don't wipe your external SD card, so make sure it's not mounted in TWRP. After the wipe mount your external SD, flash the rom, then flash boot.img and tick Boot not recovery before the flash. Reboot and wait. Let me know if it helped man.
---------- Post added at 08:39 PM ---------- Previous post was at 08:19 PM ----------
Ctrterrell said:
I forgot to use Odin lol mybad
Click to expand...
Click to collapse
If you download the boot.img you won't need Odin. But I prefer flashing tars personally, your choice. It should boot for you bro.
Hey thanks bro I finally got it I figured out what I was doing wrong I never flashed the boot img and is the wifi not working on V2
Ctrterrell said:
Hey thanks bro I finally got it I figured out what I was doing wrong I never flashed the boot img and is the wifi not working on V2
Click to expand...
Click to collapse
Glad you got it bro and no the Wi-Fi doesn't work on any of the 3 versions.
Yeah thanks for everu8amd what else roms have you tried and will I have to always flash that kernel when I try to install a roms on this phone or was that only for the note roms
Wi-Fi fix , you just need to get the files from the stock ROM in system,etc. And delete all the files in note 7 folder and put the ones you copy from the stock ROM in that same folder you just delete the Wi-Fi files out of
And Reboot I reboot to recovery and advance wipe click dalvic and cliche
mario1634 said:
Wi-Fi fix , you just need to get the files from the stock ROM in system,etc. And delete all the files in note 7 folder and put the ones you copy from the stock ROM in that same folder you just delete the Wi-Fi files out of
Click to expand...
Click to collapse
Ok ima give it a try In few and see what happens
Have anybody figure out a fix for the camera
mario1634 said:
Have anybody figure out a fix for the camera
Click to expand...
Click to collapse
That's what I was about to ask next I know I was still having problems even when I tried to send a pic it still Would reboot
I'm trying to figure it out now if I get it working I will tell you I get it to stop reboot ever time and now it just force close