Develop Bugs

[IDEA!]How-to get in bootloader without vol buttons

This is my idea!
Since we make android partition in the nand like system boot data etc i found a way to get in bootloader without working vol buttons!
only i need some one to work it out ofcourse
you need to have root and terminal and busybox and android on nand
well here is the plan!
why dont make a boot.img to flash over the old boot and the boot.img we flashed with android take us to bootloader
then we can flash CLK or windows mobile so we could use the phone fully!
if some one can work this out pls do it
with CLK we also need a CWR that use the home and start button to navigate in CWR

RDilus said:
This is my idea!
Since we make android partition in the nand like system boot data etc i found a way to get in bootloader without working vol buttons!
only i need some one to work it out ofcourse
you need to have root and terminal and busybox and android on nand
well here is the plan!
why dont make a boot.img to flash over the old boot and the boot.img we flashed with android take us to bootloader
then we can flash CLK or windows mobile so we could use the phone fully!
if some one can work this out pls do it
with CLK we also need a CWR that use the home and start button to navigate in CWR
Click to expand...
Click to collapse
use power menu , worked in clk version . long press power key /restart/bootloader

RDilus said:
This is my idea!
Since we make android partition in the nand like system boot data etc i found a way to get in bootloader without working vol buttons!
only i need some one to work it out ofcourse
you need to have root and terminal and busybox and android on nand
well here is the plan!
why dont make a boot.img to flash over the old boot and the boot.img we flashed with android take us to bootloader
then we can flash CLK or windows mobile so we could use the phone fully!
if some one can work this out pls do it
with CLK we also need a CWR that use the home and start button to navigate in CWR
Click to expand...
Click to collapse
Also when flashing the new boot.img you have to use the volume to navigate up or down.

I believe he is talking about booted android from the MAGLDR...

I have a great IDEA for YOU!!!
FIX YOUR VOLUME BUTTONS!!!
BUY ANOTHER FLEX RIBBON, SEND IT TO A TECHNICIAN, DO ANYTHING BUT ASK THIS KIND OF STUFF...
This is so stupid! PPL 'll start to ask for a new kernel, capable of 12mpx photos, full hd recording and 1 week battery duration... oh.. u don´t know what is a kernel?!

betuca said:
FIX YOUR VOLUME BUTTONS!!!
BUY ANOTHER FLEX RIBBON, SEND IT TO A TECHNICIAN, DO ANYTHING BUT ASK THIS KIND OF STUFF...
This is so stupid! PPL 'll start to ask for a new kernel, capable of 12mpx photos, full hd recording and 1 week battery duration... oh.. u don´t know what is a kernel?!
Click to expand...
Click to collapse
You deserve a ban, nothing else to add.

betuca said:
FIX YOUR VOLUME BUTTONS!!!
BUY ANOTHER FLEX RIBBON, SEND IT TO A TECHNICIAN, DO ANYTHING BUT ASK THIS KIND OF STUFF...
This is so stupid! PPL 'll start to ask for a new kernel, capable of 12mpx photos, full hd recording and 1 week battery duration... oh.. u don´t know what is a kernel?!
Click to expand...
Click to collapse
Seems like you got registered and made your very first post to down put someone else.
Since you did not read what XDA forum is all about. Let me re-iterate.
XDA forum is all about development.
And with it all comes members who had given many craxy ideas and HAVE actually created apps and done mods from those very craxy ideas.
Though the OP's suggestion is near impossible as it requires coding from the start and would be best achieved from the manufacturer side.
But did ANYONE imagine HD2 a 3 year old mobile running Android as smooth as default Android equiped phones.
AND you never know what else developers and HD2 put together is capable of.
SO you can take UR ideas and downputs elsewhere.

contactwajeeh said:
I believe he is talking about booted android from the MAGLDR...
Click to expand...
Click to collapse
i would agree with you but he states clearly cLk.

[email protected] said:
i would agree with you but he states clearly cLk.
Click to expand...
Click to collapse
I can see that but what he says is, he is currently using MAGLDR and wanted to convert to CLK....

white-energy said:
You deserve a ban, nothing else to add.
Click to expand...
Click to collapse
I agree !!

contactwajeeh said:
I can see that but what he says is, he is currently using MAGLDR and wanted to convert to CLK....
Click to expand...
Click to collapse
well almost right
i wanna kick it in bootloader to install CLK so a patch in the boot.img that will kick is direcly in the bootloader instead of android

white-energy said:
You deserve a ban, nothing else to add.
Click to expand...
Click to collapse
+1 to that

[9/9/12][Recovery]Clockworkmod v6.0.1.3

This is just a recovery I compiled from the latest available code from the CM10 source. It does not offer any major upgrade in function from ACL's latest cwm recovery, but is slightly aesthetically different.
Installation:
Download from link below, flash with fastboot
Code:
fastboot flash recovery recovery.img
Bugs:
recovery.log may show these errors:
Code:
failed to open /sys/class/android_usb/android0/state: No such file or directory
but it does not affect usb or mass storage afaik.
Download:
recovery_cwr_6.0.1.3.img - 3.36 MB 9912
Credits: Everyone involved in Android development.
Feel free to report any bugs and enjoy.

works great, but one question: what is the thing you are asked first time you click reboot system now and what should i have answered yes or no, cause i clicked no?

Ranomez said:
works great, but one question: what is the thing you are asked first time you click reboot system now and what should i have answered yes or no, cause i clicked no?
Click to expand...
Click to collapse
I have not seen that prompt before.. what did it say? If you don't know what it does, answering "no" is probably a good idea

jianC said:
I have not seen that prompt before.. what did it say? If you don't know what it does, answering "no" is probably a good idea
Click to expand...
Click to collapse
something about after reboot rom may flash stock recovery, do you want to disable recovery flash, thats the question i get

Ranomez said:
something about after reboot rom may flash stock recovery, do you want to disable recovery flash, thats the question i get
Click to expand...
Click to collapse
In that case, just choose "no".

sorry to revive this old thread, but i just realised this recovery has a big problem and wanted to warn anyone who may want to try it: most blckups made by it have md5 mismatch, i meant i got that error at 14 out of 15 backups created.
EDIT1: i had a look at the backup folder and as far as i can see some .img files are not generated (i think cache and recovery) and also the nandroid.md5 is not generated, but that is easy to fix by generating it by urself throu adb.

Battery loading Led not working
The Led is not working with this recovery while charging.
I guess the Battery is not loading, too.
Edit - This is only, when phone is off. -
Hope this can be fixed.
regards

Sorry about the bugs/lack of support but I do not have a Touch Pro 2 anymore.
The most help I can offer is uploading the device tree that I used to compile recovery in CM10 (and potentially compile a booting version of CM10 but that has never been accomplished due to kernel issues).
https://github.com/jianC/android_device_htc_rhodium

jianC said:
Sorry about the bugs/lack of support but I do not have a Touch Pro 2 anymore.
The most help I can offer is uploading the device tree that I used to compile recovery in CM10 (and potentially compile a booting version of CM10 but that has never been accomplished due to kernel issues).
http://ge.tt/1gVK1FS/v/0?c
Click to expand...
Click to collapse
If you would like to play with the 3.4.17 kernel for S&Gs, you can find it in this thread at the bottom of the first post.
Maybe some of the kernel issues will be fixed there? I can probably get the git for it if you would want it.

wizardknight said:
If you would like to play with the 3.4.17 kernel for S&Gs, you can find it in this thread at the bottom of the first post.
Maybe some of the kernel issues will be fixed there? I can probably get the git for it if you would want it.
Click to expand...
Click to collapse
Thanks for the links, but I do not have a rhod for testing anymore.. maybe someone adventurous could take a stab at it .

[Q] Unresponsive screen after flashing ROM/Kernel

Hello All,
First time post and as an offering, I will say 'thanks' to anyone that responds in a positive manner to my post (trying to win some friends) :laugh:
Here's my issue, I have an Arc S LT18i.
Unlocked bootloader and rooted.
Whenever I flash anything custom the touch screen fails to respond, i've flashed LupusV7, slim bean 3.1 and 3.2 (with arc fusion 3.6 and 4.5) and Super Jelly Bean. All seemingly start without any issues and the physical buttons work no problem. BUT the screen refuses to work in anyway at all!!
I have made sure I wiped the system, cache and delvak (sp?)
Any help greatly appreciated, I am a NOOB but underneath it all I'm just trying to make the most of this wonderful Arc S...
Anything you want to know, please ask away...
Please help.
Namaste
Ricky:fingers-crossed:

Try doing a clean install
- Flash stock ICS .587 ftf
- Flash Kernel
- Wipe data,cache & dalvik
- Install ROM
sent via XPERIA™

Same thing!!
msc3169 said:
Try doing a clean install
- Flash stock ICS .587 ftf
- Flash Kernel
- Wipe data,cache & dalvik
- Install ROM
sent via XPERIA™
Click to expand...
Click to collapse
Hello and thank you for the reply...
I flashed stock ICS .587 (world india) from this site talk.sonymobile.com/thread/35239
Does that count as stock ICS .587?
And then followed the rest of the instructions, the exact same thing happens... buttons work but the touch screen does not!?
Any other ideas please? Or does anyone else have a suggestion?
Thank you very much for taking the time to reply to me.
Ricky

ricky7D said:
Hello and thank you for the reply...
I flashed stock ICS .587 (world india) from this site talk.sonymobile.com/thread/35239
Does that count as stock ICS .587?
And then followed the rest of the instructions, the exact same thing happens... buttons work but the touch screen does not!?
Any other ideas please? Or does anyone else have a suggestion?
Thank you very much for taking the time to reply to me.
Ricky
Click to expand...
Click to collapse
Are you using compatible ROM and Kernel?
僕のLT18iから送られてきた

compatible ROM and Kernel
popthosegaskets said:
Are you using compatible ROM and Kernel?
僕のLT18iから送られてきた
Click to expand...
Click to collapse
Hello, thanks for the reply...
According to the Slim Bean page, I can use ANY kernel with that rom. But also, if I just have the Lupusv7 Kernel on there, the touch screen doesn't work within that, so not a ROM/Kernel conflict I belive.
I've also tried other Kernel/ROM combinations, same thing keeps on happening. Touchscreen works 100% with a SE restore, stock ROM.
Any other ideas please??

ricky7D said:
Hello, thanks for the reply...
According to the Slim Bean page, I can use ANY kernel with that rom. But also, if I just have the Lupusv7 Kernel on there, the touch screen doesn't work within that, so not a ROM/Kernel conflict I belive.
I've also tried other Kernel/ROM combinations, same thing keeps on happening. Touchscreen works 100% with a SE restore, stock ROM.
Any other ideas please??
Click to expand...
Click to collapse
It's best to use the recommended kernel as stated on the ROM thread. Try another kernel and see how things go.
僕のLT18iから送られてきた

You sure you installed device-specific patch / chose correct phone in AROMA?

Kernel or ROM issue?
popthosegaskets said:
It's best to use the recommended kernel as stated on the ROM thread. Try another kernel and see how things go.
僕のLT18iから送られてきた
Click to expand...
Click to collapse
Hello,
As previously mentioned, the reccomended kernel is Lupusv7, When i flash this Kernel into recovery mode, all looks well but as it has a touch screen interface this still doesn't work!
I'm presuming that it cannot be a conflict as it's happen before I instll the new ROM etc... the touch screen doesn't even work within the GUI of the Lupusv7 kernel.
I can get multiple ROMS to load with different kernels but so far, none have booted with the touch screen working!!
I am very much a noob but have read loads of articles on how this should be done, unless i'm missing something very obvious which isn't stated then I dont see anyone else having this issue.
Any clues people? :good:
Thanks, Ricky

AROMA?
Someguyfromhell said:
You sure you installed device-specific patch / chose correct phone in AROMA?
Click to expand...
Click to collapse
Hello Someguyfromhell,
I haven't used AROMA, the guides i've been reading haven't mentioned this!?
This is the process I went through:
flashed stock ICS ROM
flashed kernel
wipe data/cache/davlik
flashed rom
rebooted, ROM loads up and the touch screen doesn't work.
Any help you can give me on AROMA, links etc?
I'm looking right now, but a 'leg up' would be great.
Thanks for the reply.
Ricky

here what to do
- Make sure you had installed Official 4.0.4 ftf pack
- When flashing official ftf pack remember to exclude / tick these things:
1. simlock.ta (Exclude TA)
2. Kernel.sin (Exclude kernel)
3. FOTA (Exclude FOTA)
After flash successful, power on your phone and let it start completely
- Now you can start to install any ROM
1.Flash the Recommended Kernel: Vengeance , KTG Anzu , RUSH
2. Place ROM on SD card
3. Power off the phone and boot into CWM
3. Backup and restore > choose Backup
4. Wipe Data/Factory Reset
5. Mounts and storage > Format /system
6. Advanced > Wipe battery stats
7. Install zip from SD card > Choose the rom
8. if rom uses aroma Follow on screen instructions on AROMA, remember to choose "Unlocked bootloader" and also the correct kernel modules and of course the correct phone model
9. After complete installation tick "Reboot" and let the phone restart
10. Give the phone a good full charge, and enjoy ur phone !
11.THE MOST IMPORTANT THING PRESS THANKS if I helped

ricky7D said:
Hello Someguyfromhell,
I haven't used AROMA, the guides i've been reading haven't mentioned this!?
This is the process I went through:
flashed stock ICS ROM
flashed kernel
wipe data/cache/davlik
flashed rom
rebooted, ROM loads up and the touch screen doesn't work.
Any help you can give me on AROMA, links etc?
I'm looking right now, but a 'leg up' would be great.
Thanks for the reply.
Ricky
Click to expand...
Click to collapse
Then did you install the device-specific patch?

ok man, you've got the same problem like me
First thing, all roms that make your touch screen doesn't work will based on cm (e.g. cm10, slim, any jb).
and ALL STOCK roms will get no problem.
There's lot of people here got this problem and still has no clue why this problem occure to ours, so sad story.
Someone says that the touch screen firmware sould be updated to the lastest version, but i don't know how.
One solution that i found is, remove the battery to turn off then turn it on to reboot again and again. If you lucky enough, the touch screen will work like a miracle!
and the success rate is also <50% ( based on my experience only)

AROMOA guide?
Someguyfromhell said:
Then did you install the device-specific patch?
Click to expand...
Click to collapse
on all the ROM guides, I have never seen a part where it says i should install a device specific patch, do you have a link to where these may be?
Or even a ROM with guide where it says this? I'm very happy to follow that to get this working. I have no preference to CM10, Slim Bean, Racing Bean etc... as of yet i've not been able to use any of them.
Thanks for the continued response.
Ricky

THANK YOU
eakav said:
ok man, you've got the same problem like me
First thing, all roms that make your touch screen doesn't work will based on cm (e.g. cm10, slim, any jb).
and ALL STOCK roms will get no problem.
There's lot of people here got this problem and still has no clue why this problem occure to ours, so sad story.
Someone says that the touch screen firmware sould be updated to the lastest version, but i don't know how.
One solution that i found is, remove the battery to turn off then turn it on to reboot again and again. If you lucky enough, the touch screen will work like a miracle!
and the success rate is also <50% ( based on my experience only)
Click to expand...
Click to collapse
Ah ha... sounds like you have the same problem as me!
Did you manage to get any JB ROM working? If so, which one, just so I can try that also...
Does anyone else have an idea on how to update the touch screen firmware?
Really appreciate the feedback, thank you one and all!!
Ricky

ricky7D said:
Ah ha... sounds like you have the same problem as me!
Did you manage to get any JB ROM working? If so, which one, just so I can try that also...
Ricky
Click to expand...
Click to collapse
This solution is the one that i think it can move some files which related to touch screen.
http://forum.xda-developers.com/showpost.php?p=34593771&postcount=23
But sorry, it still get sometimes for the touch screen didn't response :crying:
However, as i mentioned above; you can get ALL jb rom working :fingers-crossed:
But depends on your luck. Just turn it off when the touch screen didn't response, then turn it on again (and again) untill it work.
I hoped that the new linux kernel will solve this...

No touch
eakav said:
This solution is the one that i think it can move some files which related to touch screen.
http://forum.xda-developers.com/showpost.php?p=34593771&postcount=23
But sorry, it still get sometimes for the touch screen didn't response :crying:
However, as i mentioned above; you can get ALL jb rom working :fingers-crossed:
But depends on your luck. Just turn it off when the touch screen didn't response, then turn it on again (and again) untill it work.
I hoped that the new linux kernel will solve this...
Click to expand...
Click to collapse
I have same issue have tried many stock based roms and kernels no problem but any CM based rom I have no touchscreen.
You can reboot and about 1 in 5 times it will work
Maybe it only affects certain versions of the phone. I even tried re-locking bootloader and doing official sony update then tried CM again I tried 7.1,9 and 10
same problem.

Here's where I am...
UPDATE:
So, here is where I am. Using advice from previous replies I have managed to install Xperia Ultimate HD and this is working off of the Lupus kernel without any issues. I'm still unable to get ANY Jelly Bean roms working...
Maybe my device will just not work on JB :crying:
Any other tips or tricks are greatly appreciated, would love to get JB working on here my beloved Arc S.
Ricky :good:

Any news here?
I have the same issue over here with a colleagues LT18i

I have same problem, touch screen doesn't work on many different kernels... only work on stock kernel

Any news about this problem?

[RECOVERY] TWRP 2.5 - i9505 Ex#2

Hello again, I bring to you, TeamWin Recovery Project or commonly known as TWRP (2.5) for your beloved i9505 (S4). I decided to build this as a number of users (including myself) are not much fans of CWM. This gives you the ability to flash your favourite custom ROMs, Kernels, Mods. I have pushed the TWRP Device Tree to my Github, for all of you curious people. Thankyou to 'as i9000' for giving me the stock recovery. Note: This thread will be moved to the i9505 section once its created. If you Encounter any issues with this recovery, report them to this thread with a recovery.log. You can get it by, adb pull /tmp/recovery.log
This has not been tested by me and is still experimental. I hold no responsibility
for any problems caused. YOU! Are trying this at your own risk. Don't blame me that I wasted your $700.
Put a scare in you didn't I?
I have provided the stock recovery if you encounter any issues, you can always flash back. It is Odin flashable.
Downloads:
TWRP (2.5) Experimental #Offi: Download (tech TeamWin)
Stock Recovery: http://d-h.st/LqC
Changelog:
Code:
[I][U]Experimental #2[/U][/I]
Attempted boot fix
Board MSM890 added to list
system.prop updated
Temporarily removed some twrp flags
[I][U]Experimental #1[/U][/I]
Public release

Does NOT work, tested this just now!
when you try to boot in recovery, phone is restarted automatically, recovery cannot be reached, so i went back to stock recovery

karoolus said:
Does NOT work, tested this just now!
when you try to boot in recovery, phone is restarted automatically, recovery cannot be reached, so i went back to stock recovery
Click to expand...
Click to collapse
Thankyou for reporting. Building new version now. one that will hopefully boot in recovery. (skipped some changes i thought werent necessary)
EDIT: i9505 user, who is willing to test. PM ME

not that I don't appreciate your effort in building it,
but won't the TWRP team create an official thread for the S4?

PLUG313 said:
not that I don't appreciate your effort in building it,
but won't the TWRP team create an official thread for the S4?
Click to expand...
Click to collapse
Maybe they will, maybe they wont. who knows
-----------------------------------------------------------------------------------------
Experimental #2 Online. Should fix recovery issues

Do you plan on making a recovery for the at&t s4?

fix-this! said:
Do you plan on making a recovery for the at&t s4?
Click to expand...
Click to collapse
Send me the stock recovery. and download this on your phone: https://play.google.com/store/apps/details?id=com.cls.partition&hl=en and send me the info

tested exp2, didn't work either.. i can't use ADB on work pc (driver restrictions etc) and i can't take the device home with me, so i can't take logs, sorry..

karoolus said:
tested exp2, didn't work either.. i can't use ADB on work pc (driver restrictions etc) and i can't take the device home with me, so i can't take logs, sorry..
Click to expand...
Click to collapse
Then it'll take a long time to fix the boot to recovery..

karoolus said:
tested exp2, didn't work either.. i can't use ADB on work pc (driver restrictions etc) and i can't take the device home with me, so i can't take logs, sorry..
Click to expand...
Click to collapse
Can you please test the CWM recovery and let us know if it works?
http://forum.xda-developers.com/showthread.php?p=40383354

karoolus said:
tested exp2, didn't work either.. i can't use ADB on work pc (driver restrictions etc) and i can't take the device home with me, so i can't take logs, sorry..
Click to expand...
Click to collapse
Try this, I doubt it will work at all. But get some filemanager that can browse ~/ directories. if it says root not available or something, deny it and check if you can continue. If yes, open the recovery.log and send me its contents.

Can anyone try this please??
I dont know if it will work but give a try.
Thank's

Doesn't boot in Recovery.

Can no one provide a recovery.log? that is the only thing needed to fix these issues

emwno said:
Can no one provide a recovery.log? that is the only thing needed to fix these issues
Click to expand...
Click to collapse
I would like to, but since i installed chainfires root my phone doesnt boot anymore... Waiting for a stock ODIN rom for the GT-I9505...
Then i can send it to you...

adb doesn't work here atm. If I get it to run, I'll send you the Log-File.

Unfortunately I had flashed chainfire's root before attempting this. I flashed exp2 and every time I attempted to boot recovery it would just kick me back to the battery charging screen (plugged in).
I booted back to the OS but it didn't have that log...
adb pull /tmp/recovery.log
remote object '/tmp/recovery.log' does not exist
Should I not boot back to the OS to get that file?

adb is working now here. But I have the same problem like Harry.
remote object '/tmp/recovery.log' does not exist

ausdim said:
Can anyone try this please??
I dont know if it will work but give a try.
Thank's
Click to expand...
Click to collapse
I tried this but it didn't work. Same thing as all the others.

harrybozack said:
I tried this but it didn't work. Same thing as all the others.
Click to expand...
Click to collapse
Boot into recovery. Then into system and try these:
Code:
adb pull /cache/recovery/last_log
Code:
adb pull /cache/recovery/log

restart all the time

i have a cayogenmod rom stable 10.1.3 and after i play a little on the phone its restart....someone can help me plz?

please help me.....
i dont know what to do please help me fix it:crying:

try another ROM.
You have given so little information, how can you expect people to give good direction based on your minimal explanation?
Seriously, try another ROM or another kernel or reflash current ROM after wiping. Good luck.

tweeny80 said:
try another ROM.
You have given so little information, how can you expect people to give good direction based on your minimal explanation?
Seriously, try another ROM or another kernel or reflash current ROM after wiping. Good luck.
Click to expand...
Click to collapse
what information i need to write? sorry that im asking alot but I'm really upset about it....and i tried now to flash the CM11 on my phone and same problem...maybe it is because my modem? or somthing else i don't know what to do...
ohhh and one more thing when i charge my phone it is'nt restart it is stuck on the image when the device is off.
please tell me what info' i need to write so someone can help me?
sorry for my bad english^^

Ynot12 said:
what information i need to write? sorry that im asking alot but I'm really upset about it....and i tried now to flash the CM11 on my phone and same problem...maybe it is because my modem? or somthing else i don't know what to do...
ohhh and one more thing when i charge my phone it is'nt restart it is stuck on the image when the device is off.
please tell me what info' i need to write so someone can help me?
sorry for my bad english^^
Click to expand...
Click to collapse
*)you have to write your steps of flashing.... and :
*)Which ROM you came from before CM 10?
*)Did you do full wipe?
*)After which things you do and your device started to restart all the time?
More details, and more ppl can help you.

antique_sonic said:
*)you have to write your steps of flashing.... and :
*)Which ROM you came from before CM 10?
*)Did you do full wipe?
*)After which things you do and your device started to restart all the time?
More details, and more ppl can help you.
Click to expand...
Click to collapse
ok first:i flashed cm10.1.3 from stock rom 4.1.2 and this morning i flashed cm11 from 10.1.3.
yes i did full wipe (data/factory reset,dalvik,cashe,and format/preload) i have the last version of CWM (6.0.4.3)
i had problem with IMEI (0049) and i fixed it with flashing this tow modems-Modem DDEMG2 and modem_XXDME4.
i had binary count of 6 and i bought traingle away and now its 0.
and when my device go to restart It's not often at the same time, but when i plug my charger it go offline and doesnt restart its stuck untill i take the battery off and then click the power botuum till next time it go to restart.
Edit: I think I found out what the problem is but I do not know how to fix it. The device does restart every time it is not taking advantage of the battery - I mean that when I put the device near me or charge it. it goes restart again but when it is charging is not turned on. Someone who knows how to handle it?
Second Edit: I've done in the System of the developer when the handset is charging the screen does not turn off. When the device does not enter sleep mode so it does not restarts.
Why is this happening? How do I fix this?

someone please help me....
please someone help me im sooo upset.....:crying::crying::crying:
someone must know what should i do

Ynot12 said:
please someone help me im sooo upset.....:crying::crying::crying:
someone must know what should i do
Click to expand...
Click to collapse
After your device restarts itself, go to ADB terminal then do this
Code:
$ su
# cat /proc/last_kmsg > /sdcard/last_kmsg.txt
post your last_kmsg.txt in your internal storage here (as an attached file)

[email protected] said:
After your device restarts itself, go to ADB terminal then do this
Code:
$ su
# cat /proc/last_kmsg > /sdcard/last_kmsg.txt
post your last_kmsg.txt in your internal storage here (as an attached file)
Click to expand...
Click to collapse
what it is should do? and how i go to ADB terminal? oh and one more question-if i will change my karnel it will help me?

Ynot12 said:
what it is should do? and how i go to ADB terminal? oh and one more question-if i will change my karnel it will help me?
Click to expand...
Click to collapse
It will likely tell us why your device is restarting.
If you don't know how to get in to the adb, forget it.

[email protected] said:
It will likely tell us why your device is restarting.
If you don't know how to get in to the adb, forget it.
Click to expand...
Click to collapse
I think i did it...i have a file in my device with the name "logcat.txt" and its something like 380kb and when i open this i see a long text..
This is it? Please help me

Ynot12 said:
I think i did it...i have a file in my device with the name "logcat.txt" and its something like 380kb and when i open this i see a long text..
This is it? Please help me
Click to expand...
Click to collapse
No it's not.
kmsg = Kernel Messages, useful for kernel panics, restarts etc (your case)
Last_kmsg = the previous kmsg that contains the error caused kernel to panic.
search for how to install adb in this forum. I can't tell you the whole story from the beginning.

[email protected] said:
No it's not.
kmsg = Kernel Messages, useful for kernel panics, restarts etc (your case)
Last_kmsg = the previous kmsg that contains the error caused kernel to panic.
search for how to install adb in this forum. I can't tell you the whole story from the beginning.
Click to expand...
Click to collapse
Ok i will check it.
Do u have email or something that we can chat?
Sent from my GT-N7100 using xda app-developers app

Ynot12 said:
Ok i will check it.
Do u have email or something that we can chat?
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
I'd like to keep this conversation here because I might not be your savior
I just had the same symptoms few days ago. My Note2 was rebooting by itself with no reason.
I checked last_kmsg, it turned out EXT4-fs error http://pastebin.com/r3UNm9AS
I was using 4.3 rom with knox-free bootloader and wifi patch.
This combination, somehow was causing this error, kernel was entering panic mode due to the mount options used in fstab.
I went back to 4.1.2 with stock bootloader, everything is fine since then.

[email protected] said:
I'd like to keep this conversation here because I might not be your savior
I just had the same symptoms few days ago. My Note2 was rebooting by itself with no reason.
I checked last_kmsg, it turned out EXT4-fs error http://pastebin.com/r3UNm9AS
I was using 4.3 rom with knox-free bootloader and wifi patch.
This combination, somehow was causing this error, kernel was entering panic mode due to the mount options used in fstab.
I went back to 4.1.2 with stock bootloader, everything is fine since then.
Click to expand...
Click to collapse
So maybe should i change my kernel?
Sent from my GT-N7100 using xda app-developers app

[email protected] said:
I'd like to keep this conversation here because I might not be your savior
I just had the same symptoms few days ago. My Note2 was rebooting by itself with no reason.
I checked last_kmsg, it turned out EXT4-fs error http://pastebin.com/r3UNm9AS
I was using 4.3 rom with knox-free bootloader and wifi patch.
This combination, somehow was causing this error, kernel was entering panic mode due to the mount options used in fstab.
I went back to 4.1.2 with stock bootloader, everything is fine since then.
Click to expand...
Click to collapse
View attachment last_kmsg.txt
i hope this is it....

Ynot12 said:
View attachment 2527101
i hope this is it....
Click to expand...
Click to collapse
Yes it is. But we need this to be taken at the first boot after your device restarts by itself.
BTW looks like you have "failed to power up wifi chip" errors
I suggest you to use stock kernel and see if there such errors still exist.

[email protected] said:
Yes it is. But we need this to be taken at the first boot after your device restarts by itself.
BTW looks like you have "failed to power up wifi chip" errors
I suggest you to use stock kernel and see if there such errors still exist.
Click to expand...
Click to collapse
I use now a stock rom with stock kernel and to get my network connection fix I used this video https://www.youtube.com/watch?v=i7K6RDVRBhs&feature=youtube_gdata_player
Please someone help me because after I used this video installations I get the imei fixed but my phones reboot all the time
Sent from my GT-N7100 using xda app-developers app

Please someone help me im begging for helppp
Sent from my GT-N7100 using xda app-developers app

Ynot12 said:
Please someone help me im begging for helppp
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
All the files given on that video link belong to S3, I don't know if they are same to Note2(despite the video title).
I would never flash those files because I'm convinced.
Firstly I would search in this forum for the people who has the same error.
I would read their attempts and results.
I would find proper files that are for my phone model. Etc, mine is n7100, so I should never flash the files for n7105!!! I would use %100 stock files to avoid errors.
I would check everything twice, then flash.
But you look like you do the opposite. You do flash first, then think
Find a stock firmware that is exactly for your model and for your country from here http://forum.xda-developers.com/showpost.php?p=31987995&postcount=9
Then enter to recovery and do a factory reset, cache wipe.