I need help with Rom and kernels - AT&T Samsung Galaxy Note I717

I would like to flash the new Rom that is rooted and teamed in the development section. My question is how? Im a noob and have no clue. I used odin to root, but had to do a system restore because my phone was acting very slow. (laggy and only 1800 on benchmarks. Now its at 2700.) it also says i need to use a new kernel. I would like to use the overclocked one but don't know how to do anything. Please give me detailed step by steps. Think you
Sent from my SAMSUNG-SGH-I717 using Tapatalk

There is step by step directions in each one of the posts. But the simple version is download Odin 1.85 and put your phone into download mode then connect odin and the phone should show up as a COM port. After that put the kernel in the pda section and hit start. That flashes the kernel and you are done.

Orange_furball said:
I would like to flash the new Rom that is rooted and teamed in the development section. My question is how? Im a noob and have no clue. I used odin to root, but had to do a system restore because my phone was acting very slow. (laggy and only 1800 on benchmarks. Now its at 2700.) it also says i need to use a new kernel. I would like to use the overclocked one but don't know how to do anything. Please give me detailed step by steps. Think you
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Click to expand...
Click to collapse
not to sound like a jerk or rude , my best advice to you is instead of asking for someone to tell you step by step, is to read the threads for the modifications you want to do in your phone, and re read the steps, when I first started in the flashing game back in the winmo days I would print out pages from here with the guides and steps the devs would post so I could sit in front of the pc and have the info right in
front of me without having the need to open and close the browser while trying to use the pc for flashing. I also made friends so I could just pm someone if I had any issues/questions, keeping me from having the need for posting and making too many questions on the threads , thus helping me avoid the famous "use the search button" comment.
Good luck and have fun!!

roloracer said:
not to sound like a jerk or rude , my best advice to you is instead of asking for someone to tell you step by step, is to read the threads for the modifications you want to do in your phone, and re read the steps, when I first started in the flashing game back in the winmo days I would print out pages from here with the guides and steps the devs would post so I could sit in front of the pc and have the info right in
front of me without having the need to open and close the browser while trying to use the pc for flashing. I also made friends so I could just pm someone if I had any issues/questions, keeping me from having the need for posting and making too many questions on the threads , thus helping me avoid the famous "use the search button" comment.
Good luck and have fun!!
Click to expand...
Click to collapse
I read them about ten times each. I just want to know what i should do if there is anything special to do.
So do i flash the overclocked kernel first or the Rom?
Oh, and you don't sound like a jerk. Im just very nervous and don't want to brick this and have to go back to my 3gs...
Sent from my SAMSUNG-SGH-I717 using Tapatalk

Orange_furball said:
I read them about ten times each. I just want to know what i should do if there is anything special to do.
So do i flash the overclocked kernel first or the Rom?
Oh, and you don't sound like a jerk. Im just very nervous and don't want to brick this and have to go back to my 3gs...
Sent from my SAMSUNG-SGH-I717 using Tapatalk
Click to expand...
Click to collapse
if you're going all the way I would suggest flashing clockworkmod recovery thru odin, doing a nandroid backup, then flash the rom, then flash the kernel, most roms already have a kernel included, but not in the case of twopumpchump's rom, as he states his don't have the kernel, so you flash the kernel afterwards, I'm sure in the future when they start to have more roms and kernel choices the devs will probably add their kernel of choice for their rom/build, therefore if you decide to use a different kernel in that situation you flash the desired kernel after the rom so if the rom has one it won't replace the one you want, you understand? meaning you always flash the kernel after the rom.

roloracer said:
if you're going all the way I would suggest flashing clockworkmod recovery thru odin, doing a nandroid backup, then flash the rom, then flash the kernel, most roms already have a kernel included, but not in the case of twopumpchump's rom, as he states his don't have the kernel, so you flash the kernel afterwards, I'm sure in the future when they start to have more roms and kernel choices the devs will probably add their kernel of choice for their rom/build, therefore if you decide to use a different kernel in that situation you flash the desired kernel after the rom so if the rom has one it won't replace the one you want, you understand? meaning you always flash the kernel after the rom.
Click to expand...
Click to collapse
Ok thanks.
I'm trying to do a clockworkMod recovery, but the galaxy note isn't listed.... What do i do?
Now im not sure if you can answer this, but what do i do with this? Its from Da_G's kernel guide
"You will need modified libraries to take full advantage of this kernel as they override speeds at times, you can find these here.
You'll have to push them over adb for now after flashing the kernel, when CWM is up I will make a CWM zip for it.
From the directory with adb and the three .so files:
Code:
adb remount
adb push libhardware_legacy.so /system/lib/
adb push librpc.so /system/lib/
adb push libandroid_runtime.so /system/lib/
adb shell chmod 0644 /system/lib/libhardware_legacy.so
adb shell chmod 0644 /system/lib/librpc.so
adb shell chmod 0644 /system/lib/libandroid_runtime.so
adb reboot
Souce code available at: https://github.com/dagnarf/sgh-i717-dagkernel"
thanks!

Orange_furball said:
Ok thanks.
I'm trying to do a clockworkMod recovery, but the galaxy note isn't listed.... What do i do?
Now im not sure if you can answer this, but what do i do with this? Its from Da_G's kernel guide
"You will need modified libraries to take full advantage of this kernel as they override speeds at times, you can find these here.
You'll have to push them over adb for now after flashing the kernel, when CWM is up I will make a CWM zip for it.
From the directory with adb and the three .so files:
Code:
adb remount
adb push libhardware_legacy.so /system/lib/
adb push librpc.so /system/lib/
adb push libandroid_runtime.so /system/lib/
adb shell chmod 0644 /system/lib/libhardware_legacy.so
adb shell chmod 0644 /system/lib/librpc.so
adb shell chmod 0644 /system/lib/libandroid_runtime.so
adb reboot
Souce code available at: https://github.com/dagnarf/sgh-i717-dagkernel"
thanks!
Click to expand...
Click to collapse
this is for the use of adb(android debug bridge) and you need android sdk/jdk installed on pc to have commands for android thru command prompt.
if you want to install cwm from androiduser00110001 all you need is odin in your pc and the rest is this.
Follow these instructions:
You will need Odin to flash recovery. Check the threads on how to use and where to download it from.
Download recovery HERE
Start Odin
Click on PDA
Browse to file odin_n1717_cwm_recovery_a1.tar
Make sure your phone is in download mode so Odin can flash
Flash file
Let phone reboot
Boot into recovery - Either use adb reboot recovery or power down phone, press volume up, volume down and power at same time to boot into recovery
Once in recovery, select power down phone
Let phone power down and then power it back up
Phone should reboot into OS fine, if not go into recovery and try again.
That is one bug so far. Mostly everything else works. If you get stuck in a CWR boot loop than just flash stock recovery that can be found HERE.

roloracer said:
this is for the use of adb(android debug bridge) and you need android sdk/jdk installed on pc to have commands for android thru command prompt.
if you want to install cwm from androiduser00110001 all you need is odin in your pc and the rest is this.
Follow these instructions:
You will need Odin to flash recovery. Check the threads on how to use and where to download it from.
Download recovery HERE
Start Odin
Click on PDA
Browse to file odin_n1717_cwm_recovery_a1.tar
Make sure your phone is in download mode so Odin can flash
Flash file
Let phone reboot
Boot into recovery - Either use adb reboot recovery or power down phone, press volume up, volume down and power at same time to boot into recovery
Once in recovery, select power down phone
Let phone power down and then power it back up
Phone should reboot into OS fine, if not go into recovery and try again.
That is one bug so far. Mostly everything else works. If you get stuck in a CWR boot loop than just flash stock recovery that can be found HERE.
Click to expand...
Click to collapse
Well, i couldnt get clockworkmod to work, but i went along with everything else (except the nandroid backup) My flash counter is at 11 now.... but i have a new rom! thanks again!

Orange_furball said:
Well, i couldnt get clockworkmod to work, but i went along with everything else (except the nandroid backup) My flash counter is at 11 now.... but i have a new rom! thanks again!
Click to expand...
Click to collapse
you're welcome, glad you got it done.

Eric-1987 said:
There is step by step directions in each one of the posts. But the simple version is download Odin 1.85 and put your phone into download mode then connect odin and the phone should show up as a COM port. After that put the kernel in the pda section and hit start. That flashes the kernel and you are done.
Click to expand...
Click to collapse
go to the saurom thread all ur answers r there DAGs oc kernel

JB calhoun said:
go to the saurom thread all ur answers r there DAGs oc kernel
Click to expand...
Click to collapse
Been solved a long while ago! Thanks tho!
Sent from my SAMSUNG-SGH-I717 using Tapatalk 2

Related

CWM Not working

I installed Rom Manager and then downloaded the recovery for Samsung galaxy s2. When hit reboot into recovery. I am unable to perform any operations in CWM. I had to connect the phone via usb and issue a "adb reboot" command to get back.
How do we make cwm work.
http://forum.xda-developers.com/showpost.php?p=18160002&postcount=26
ptulluri said:
I installed Rom Manager and then downloaded the recovery for Samsung galaxy s2. When hit reboot into recovery. I am unable to perform any operations in CWM. I had to connect the phone via usb and issue a "adb reboot" command to get back.
How do we make cwm work.
Click to expand...
Click to collapse
Also must people are having issues flashing in cwm after using ROM manager. If you try installing from cwm and get verification error you needed to flash again then kernel and don't use ROM manager
Flashed CWM and nothing is happening
I flashed CWM Recovery 5.0.2.3 using the instructions here http://forum.xda-developers.com/showthread.php?t=1285823. However, when i go into CWM and select something the only thing that happens is the logo for CWM shows up with a black screen. When I push the power button again it will go back to the list.I am using the stock rom and it hasn't even been rooted yet. When I try to root using super one click, it gets stuck at step #5. Please Advise.
NDN
Dont use Rom Manager. It is known to have issues with the S2
I use CWM Manager and have no problems.....
noobdeeznutz said:
I flashed CWM Recovery 5.0.2.3 using the instructions here http://forum.xda-developers.com/showthread.php?t=1285823. However, when i go into CWM and select something the only thing that happens is the logo for CWM shows up with a black screen. When I push the power button again it will go back to the list.I am using the stock rom and it hasn't even been rooted yet. When I try to root using super one click, it gets stuck at step #5. Please Advise.
NDN
Click to expand...
Click to collapse
The key mapping is different. I had the same issue. Try the home key to select in place of the power button and the back key for back
Also if not rooted I do not think CWM will work...
Use this by Entropy512 it is flawless.
http://forum.xda-developers.com/showthread.php?t=1286432
SNadler said:
The key mapping is different. I had the same issue. Try the home key to select in place of the power button and the back key for back
That was it... THANKS!!!
Click to expand...
Click to collapse
SNadler said:
Also if not rooted I do not think CWM will work...
Click to expand...
Click to collapse
Root is having access to root account in os. It has nothing to do with cwm since cwm is loaded before the os loads.
They are irrelevant
Sent from my SAMSUNG-SGH-I777
Pirateghost said:
Root is having access to root account in os. It has nothing to do with cwm since cwm is loaded before the os loads.
They are irrelevant
Sent from my SAMSUNG-SGH-I777
Click to expand...
Click to collapse
In addition, all of our CWM-enabled kernels are "insecure" kernels - They give root at all times to ADB sessions, this is why SuperOneClick works after flashing them.
But only ADB sessions get root, so you use the "rooted" ADB shell to root the system partition. After that you've got perma-root until you nuke su and Superuser.apk from /system
Entropy512 said:
In addition, all of our CWM-enabled kernels are "insecure" kernels - They give root at all times to ADB sessions, this is why SuperOneClick works after flashing them.
But only ADB sessions get root, so you use the "rooted" ADB shell to root the system partition. After that you've got perma-root until you nuke su and Superuser.apk from /system
Click to expand...
Click to collapse
I think I am confused again?
When I flash a kernel, I have root. I have never used super one click. Just flashed your kernel. I thought that is what gave me root? Are you saying I still do not have root for /system files? Or does your kernel push su and superuser when it is flashed?
SNadler said:
I think I am confused again?
When I flash a kernel, I have root. I have never used super one click. Just flashed your kernel. I thought that is what gave me root? Are you saying I still do not have root for /system files? Or does your kernel push su and superuser when it is flashed?
Click to expand...
Click to collapse
Mine does, codeworkx's doesn't.
Setting a kernel to be insecure is a lot easier and takes less time than putting in a robust root-inject script.
SNadler said:
I think I am confused again?
When I flash a kernel, I have root. I have never used super one click. Just flashed your kernel. I thought that is what gave me root? Are you saying I still do not have root for /system files? Or does your kernel push su and superuser when it is flashed?
Click to expand...
Click to collapse
Entropy512 said:
Mine does, codeworkx's doesn't.
Setting a kernel to be insecure is a lot easier and takes less time than putting in a robust root-inject script.
Click to expand...
Click to collapse
Entropy512: Does this mean that codeworkx's kernel must be flashed with SuperOneClick in order to have complete root (to /system)... but with your kernels we don't need to flash SuperOneClick? If so, in order to unroot (without SuperOneClick) I suspect one would have to flash the non-root stock kernel? Thx
DoctorQMM said:
Entropy512: Does this mean that codeworkx's kernel must be flashed with SuperOneClick in order to have complete root (to /system)... but with your kernels we don't need to flash SuperOneClick? If so, in order to unroot (without SuperOneClick) I suspect one would have to flash the non-root stock kernel? Thx
Click to expand...
Click to collapse
Yes. (Unless you flash an su package with CWM instead of SuperOneClick)
Really, all SuperOneClick is doing are the following commands, assuming you've got a proper su binary and Superuser.apk:
Code:
adb remount
adb push su /system/xbin/su
adb shell chmod 6755 /system/xbin/su
adb push Superuser.apk /system/app/Superuser.apk
adb shell chmod 644 /system/app/Superuser.apk
Entropy512 said:
Yes. (Unless you flash an su package with CWM instead of SuperOneClick)
Really, all SuperOneClick is doing are the following commands, assuming you've got a proper su binary and Superuser.apk:
Code:
adb remount
adb push su /system/xbin/su
adb shell chmod 6755 /system/xbin/su
adb push Superuser.apk /system/app/Superuser.apk
adb shell chmod 644 /system/app/Superuser.apk
Click to expand...
Click to collapse
I understand (I think) that chmod 644 is to set the permission but what is chmod 6755?
SNadler said:
Dont use Rom Manager. It is known to have issues with the S2
I use CWM Manager and have no problems.....
Click to expand...
Click to collapse
I have downloaded CWM Manager and I have tried to install it but it has failed. Is there a different type of process to doing this other than opening it through root explorer?
what are you trying to do? just use the 3 button combo or extended power option to boot into recovery and flash away?
Ok, I am having a huge issue with trying to flash a custom rom. I will try to explain this the best way I can. I have had the same problem as above when trying to use CWM in recovery. Here is what I did:
- I unrooted my phone
- flash CWM with "SGH-I777_ClockworkMod-Recovery_5.0.2.3.tar"
- then it boots into CMW recovery and I can't do jack. When I try to select anything I just get a blank screen with the clock workz logo. If I hit the volume up and down buttons again the list of options comes back, but I will be stuck with the same situation if I try to select any options.
I was able to successfully root my phone in another instance using galaxys2root.com's method, however when I tried to use cwm I also ran into the same problem. I have yet to be able to use anything in cwm recovery. Please help me. I have flashed my phone multiple times and probably bricked it also. Luckily i haven't done any damage yet, but i would like to be able to flash roms. I am still kinda new to flashing roms, but i was able to flash my old infuse like a champ without any of these problems.
ducksauce88 said:
Ok, I am having a huge issue with trying to flash a custom rom. I will try to explain this the best way I can. I have had the same problem as above when trying to use CWM in recovery. Here is what I did:
- I unrooted my phone
- flash CWM with "SGH-I777_ClockworkMod-Recovery_5.0.2.3.tar"
- then it boots into CMW recovery and I can't do jack. When I try to select anything I just get a blank screen with the clock workz logo. If I hit the volume up and down buttons again the list of options comes back, but I will be stuck with the same situation if I try to select any options.
I was able to successfully root my phone in another instance using galaxys2root.com's method, however when I tried to use cwm I also ran into the same problem. I have yet to be able to use anything in cwm recovery. Please help me. I have flashed my phone multiple times and probably bricked it also. Luckily i haven't done any damage yet, but i would like to be able to flash roms. I am still kinda new to flashing roms, but i was able to flash my old infuse like a champ without any of these problems.
Click to expand...
Click to collapse
Use the home soft key to select stuff in CWR, not the power button.
Sent from my SGH-I777 using XDA App
i didnt read all of the posts until after i posted. thanks for not slashing me. so it looks like i use the home button to select then the back button still goes back. got it.
On a side not, I do not remember reading about that within the posts for rooting and flashing clockworkz. I tend to skip over things when reading, but I think someone should put that in big fat red letters "USE HOME BUTTON TO SELECT".

[INFO][GUIDE]Rooting on linux (and mac)

There appear to be two main options for rooting Samsung devices on linux and mac.
Option 1: (un-tested) root.zip (recovery)
This method roots your stock 2.3 rom from in recovery (stock or CWM)
1. Copy Root.zip to your sdcard.
2. Turn your phone off
3. Boot your phone into recovery mode. (Hold HOME+POWER buttons. When the screen turns on let go of POWER but keep holding HOME. After you enter recovery mode, let go of HOME.)
4. Select “apply update from sdcard”
5. Find and select Root.zip
6. When it’s done installing, select “reboot system now”
7. Go to apps and look for 'superuser'. If you see it, your phone is rooted.
Option 2: (un-tested) flash CWM from stock recovery:
This gives you the freedom of a custom recovery, flashed on the device from stock recovery
1. Download recovery-clockwork-5.0.2.6-galaxyace-fix.zip
2. Put recovery-clockwork-5.0.2.6-galaxyace-fix.zip on your sdcard
3. Boot into current stock (default) recovery (zip also compatible with CWM recovery)(Hold HOME+POWER buttons. When the screen turns on let go of POWER but keep holding HOME. After you enter recovery mode, let go of HOME.)
4. Go to "apply update from sdcard"
5. Select "recovery-clockwork-5.0.2.6-galaxyace-fix.zip"
6. When it finishes, power off and boot back into recovery mode to check it has installed (it should say "ClockworkMod Recovery v5.0.2.6" somewhere)
Option 3 (un-confirmed): use Heimdall.
An open source, cross-platform, alternative to Odin.
Heimdall is officially supported on the Galaxy S (and S variants including Galaxy Tab)
It allows you to do pretty much anything Odin can do (interact with download mode), and so you can flash a root kernel to gain root and CWM recovery.
Although supposedly untested on the Galaxy Ace, heimdall should be able to flash the usual root precedure (rooting kernel with CWM).
It would be great if someone could verify heimdall works for the Galaxy Ace
Option 4: (un-tested) root your ROM using the zergRush exploit (from the Revolutionary team).
zergRush rooting scripts: Linux, Mac, Windows
For the zergRush exploit scripts, you only root your firmware, so CWM will need to be installed manually afterwards if you want it.
Now that you have root, you should be able to (optionally) flash CWM from an app or over adb using flash_image) (DO YOU NEED ROOT IF THIS IS DONE IN RECOVERY(STOCK)?)
Apps that can flash CWM include:
* CWM Manager
* Flash image GUI
_DO NOT USE_ ROM Manager (reported unstable)
To flash using ADB and flash_image, download flash_image and an CWM recovery img then run:
Code:
cd directory-containing-files/
adb remount
adb push flash_image /system/bin/flash_image
adb shell chmod 0755 /system/bin/flash_image
adb push recovery.img /sdcard/
adb shell
flash_image recovery /sdcard/Recovery.img
rm /sdcard/recovery.img
reboot recovery
Or from the phone's terminal (if BusyBox is installed):
first put recovery.img & flash_image onto /sdcard/
Code:
cd directory-containing-files/
su
mount -o remount,rw -t yaffs2 /dev/block/mtdblock4 /system
mv /sdcard/flash_image /system/bin/flash_image
chmod 0755 /system/bin/flash_image
flash_image recovery /sdcard/Recovery.img
rm /sdcard/recovery.img
reboot recovery
DISCLAIMER: I do not personally own a Samsung phone, and have not yet tested these methods (although I am interested to hear how well they work,and will do my best to update the post). I am however planning to root a friends Galaxy Ace and possibly also an Galaxy S2, so will be testing some of these soon (I'm not sure I should try the untested heimdall on a friends Ace though)
This seems almost utterly pointless, prove me wrong?
Bofu said:
This seems almost utterly pointless, prove me wrong?
Click to expand...
Click to collapse
+1... I don't understand the point.. Why take a longer way when the shorter way is faster, efficient and trustworthy...
ace_viknesh said:
Why take a longer way when the shorter way is faster, efficient and trustworthy...
Click to expand...
Click to collapse
Sorry, which way is this shorter more trustworthy way?
The point of this is listing the methods I believe to be compatible with linux (and by extension mac)
I am new to Samsung phones and do not possess one myself, but understand that using Odin is restricted to Windows.
I will be flashing CWM Recovery to a Galxacy Ace soon and will try methods that have been tested (friend's phone)
If you know of other methods or if one of the listed methods does not work, I will update the post
Also if anyone can confirm heimdall to work with the Ace this would be the first time on xda (searching I've found only people saying it may work) the Ace is not on its supported list, however as it uses the same protocol (right?) it should work?
If however the mods believe this post to be useless or irrelevant, they are welcome to move it to the appropriate location
Point 1- Hopefully useful for Linux and Mac users.
Point 2- If on Windows its much easier and takes very less time..
Also u told about ROM Manager (reported unstable),... Dude leave unstable it bricks our phone... mAking it unusable...
Best way to root is to put the upd.zip in rooting section and flashing in recovery... Can thr be any other way better than that?
Bofu said:
This seems almost utterly pointless, prove me wrong?
Click to expand...
Click to collapse
I use OS X exclusively and this was a very useful post, and at least well written and clear. Most guides blindly assume we all use Windows, not everyone does!!!
For context, owning OS X I originally used the upd1.zip method, flashed via original recovery and it worked, which I suppose is the fastest method you don't cover.
I certainly didn't know about heimdall, great to see an open-source cross platform alternative to odin! Don't need to use it just yet, though testing will be invaluable for future use...
So thanks to the OP for writing clearly about alternative options.
But instaling CWM isn't rooting, you can have CWM without root.
Wysłane z mojego GT-S5830 za pomocą Tapatalk
actually speaking in case of SGA you don't need a PC to root or to anything except heavy logcat
What restrictions using odin on windows are you referring to?
Restriction: it doesn't work if you're not using Windows is the restriction... ;-)
dragonnn said:
But instaling CWM isn't rooting, you can have CWM without root.
Click to expand...
Click to collapse
Thanks, I wasn't sure of this as on my Desire I had to unlock the bootloader (s-off it) due to security features (and this was closely related to the rooting process). I use the term rooting as it seems the most generic, if anyone suggests a better word I will gladly consider changing the title
Prashanthme said:
Also u told about ROM Manager (reported unstable),... Dude leave unstable it bricks our phone... mAking it unusable...
Click to expand...
Click to collapse
I've updated the post advising against using ROM Manager, thanks
Prashanthme said:
Best way to root is to put the upd.zip in rooting section and flashing in recovery... Can thr be any other way better than that?
Click to expand...
Click to collapse
Thank you for this, I will get some details and update the post shortly to include this
Edit: I added the root.zip method
btw, I may rework the post to reflect whether current ROM will be rooted, recovery installed, or both and then list methods for each outcome.
matts95 said:
Thanks, I wasn't sure of this as on my Desire I had to unlock the bootloader (s-off it) due to security features (and this was closely related to the rooting process). I use the term rooting as it seems the most generic, if anyone suggests a better word I will gladly consider changing the title
I've updated the post advising against using ROM Manager, thanks
Thank you for this, I will get some details and update the post shortly to include this
Edit: I added the root.zip method
btw, I may rework the post to reflect whether current ROM will be rooted, recovery installed, or both and then list methods for each outcome.
Click to expand...
Click to collapse
Anyone tested Heimdall yet?

[Q] LG G2 D802 EE UK bootloop

I'm sorry if this isn't the right place.
I rooted my LG G2 D802 around 2 months ago, and completely forgot about it.
I got the Kitkat update about 5 hours ago, and stupidly downloaded it.
The phone got stuck in a team win bootloop and again, in a bit of a panic I wiped the phone (not thinking of just restoring my back up from when i rooted the device)
after that didn't solve anything, i reverted to google. I found a guide on here for my exact problem http://forum.xda-developers.com/showthread.php?t=2451696
I read it carefully and proceeded to follow this by the letter. I think I messed up though, with the 'ADB' thing, the last i remembered about it was using it to root the device, so I followed to guide but using the root folder i had used. now I'm no longer in a team win bootloop, I'm not in a LG splash screen boot loop, I can just about manage to get into recovery and get back to team win, but can't get into download mode.
I really wasn't looking to replace this device until the LG G3 got released, and don't really have the money to spare - so i'm really hoping this is fixable.
a note is, to root the device i followed a guide, and the TWRP (I'm not actually sure) I think i just went with it and managed it so i'm not very good when it comes to the terms, and stuff like that, any help would be greatly appreciated!
I can use a Win7 laptop to do whatever is needed, it is an EE LG G2 D802, UK, 16GB black.
I don't have insurance, I kept pushing myself to wait to do anything like this until I had insurance, but at 2 in the morning, nothing to do, ready to root - It's hard to resist.
(I do have the USB drivers on my laptop)
Sounds like you are in this boat now:
http://forum.xda-developers.com/showthread.php?t=2582142
That should do the trick since it's exactly what's happened to you and the same phone. The update might be different though as that is important to know. Just use the files from whichever the last official update you had was from.
es0tericcha0s said:
Sounds like you are in this boat now:
http://forum.xda-developers.com/showthread.php?t=2582142
That should do the trick since it's exactly what's happened to you and the same phone. The update might be different though as that is important to know. Just use the files from whichever the last official update you had was from.
Click to expand...
Click to collapse
I dont think thats the same problem as mine, i have no error, my screen doesnt go off, it just stays on lg splash screen with multicoloured led flashing, cant turn it off only restart it, i dont have linux & i can get into recovery with a few attempts. Is there anythjng that can be done or is my phone ****ed? Thanks
I have just had another read through, mainly the comments and that guide seems to get you to the point where you can get into recovery and enter those commands in the guide on my opening post - i can get into recovery and i did both fixes, the one using adb if using the adb in the root folder on my laptop i used to root the device is okay, and then again using the terminal emulator in recovery, after neither worked (actually, the terminal emulator one got me from a TWRP bootloop into an lg splash screen bootloop, after reading into thr comment to about page 7 there was an additional line to the terminal emulator method changing only the /fota to /misc which did nothing for my device. The fix there simply changed the type of bootloop i am in
yoalphadied said:
I dont think thats the same problem as mine, i have no error, my screen doesnt go off, it just stays on lg splash screen with multicoloured led flashing, cant turn it off only restart it, i dont have linux & i can get into recovery with a few attempts. Is there anythjng that can be done or is my phone ****ed? Thanks
Click to expand...
Click to collapse
Oh ok. Well, if you can still get into recovery, then you should be able to push another rom to the phone's storage via adb. But your phone definitely isn't screwed. It's pretty hard to totally mess these things up to the point of no return.
es0tericcha0s said:
Oh ok. Well, if you can still get into recovery, then you should be able to push another rom to the phone's storage via adb. But your phone definitely isn't screwed. It's pretty hard to totally mess these things up to the point of no return.
Click to expand...
Click to collapse
Im glad to hear it, got to the point of looking at a new ouone even though i wanted to keep this one until the g3 was on the shelves.
I hate to say, but how would i do this? I only know the very basics, and is the adb used to root fine to do it with? I didnt even know i had flashed TWRP correctly, think i used an app, flashify or something? Any help would be massively appreciated
yoalphadied said:
Im glad to hear it, got to the point of looking at a new ouone even though i wanted to keep this one until the g3 was on the shelves.
I hate to say, but how would i do this? I only know the very basics, and is the adb used to root fine to do it with? I didnt even know i had flashed TWRP correctly, think i used an app, flashify or something? Any help would be massively appreciated
Click to expand...
Click to collapse
So, boot to recovery and plug it in. Your PC SHOULD load the right drivers if you have already installed them. You can verify by going to your Device Mananger and making sure there are no warning signs next to your phone in the list.
If you need the drivers: https://mega.co.nz/#!rU0RkSaK!JzUCoZ5emWOsc_Tw6h8a3JZtRNT1-JvGvc8EC_u9rnI
adb and fastboot files: https://mega.co.nz/#!SJ8ijCKY!UKpr4ufVyPq4DVL2i90RI9CD7TX5AETPHrcqMQdpG5w
Download the rom you need and move it to the folder where the adb and fastboot stuff installs to. Should be C / Program Files (86) / adb
Once there and the drivers are loaded correctly, use the CMD shortcut from the adb set up and do this:
adb devices
If you get are response of some random string of letters + numbers, it's all good.
adb push nameofrom.zip /sdcard/
and then wait. It will take some time as these are large files. Not uncommon for it to take many minutes to 10 or more.
es0tericcha0s said:
So, boot to recovery and plug it in. Your PC SHOULD load the right drivers if you have already installed them. You can verify by going to your Device Mananger and making sure there are no warning signs next to your phone in the list.
If you need the drivers: link
adb and fastboot files: link
Download the rom you need and move it to the folder where the adb and fastboot stuff installs to. Should be C / Program Files (86) / adb
Once there and the drivers are loaded correctly, use the CMD shortcut from the adb set up and do this:
adb devices
If you get are response of some random string of letters + numbers, it's all good.
adb push nameofrom.zip /sdcard/
and then wait. It will take some time as these are large files. Not uncommon for it to take many minutes to 10 or more.
Click to expand...
Click to collapse
Just making sure I understand correctly, the 'rom' i need ks the stock rom, right? Im not looking to root again as the whole reason i rooted was because it was everywhere that ee werent releasing the kitkat update for the g2, since they have now i dont need root anymore.
Ill try this fix later on and tell you if it worked! Thanks
es0tericcha0s said:
So, boot to recovery and plug it in. Your PC SHOULD load the right drivers if you have already installed them. You can verify by going to your Device Mananger and making sure there are no warning signs next to your phone in the list.
If you need the drivers: link
adb and fastboot files: link
Download the rom you need and move it to the folder where the adb and fastboot stuff installs to. Should be C / Program Files (86) / adb
Once there and the drivers are loaded correctly, use the CMD shortcut from the adb set up and do this:
adb devices
If you get are response of some random string of letters + numbers, it's all good.
adb push nameofrom.zip /sdcard/
and then wait. It will take some time as these are large files. Not uncommon for it to take many minutes to 10 or more.
Click to expand...
Click to collapse
Okay, I can't seem to find the LG G2's stock rom anywhere, also the adb push nameofrom.zip /sdcard/ is that the exact command?
I found the stock firmware, but nothing for EE, just o2 and so on.
I also can't seem to get the drivers to work, I have an 'unidentified device' connected to the computer, I have tried to download from the link you gave me, and another place but neither work, once it searches for drivers again after download it just says drivers not found
saying that after trying 'adb devices' i got a random string of letters and numbers, roughly 21 characters long followed by recovery on the same line
yoalphadied said:
Okay, I can't seem to find the LG G2's stock rom anywhere, also the adb push nameofrom.zip /sdcard/ is that the exact command?
I found the stock firmware, but nothing for EE, just o2 and so on.
I also can't seem to get the drivers to work, I have an 'unidentified device' connected to the computer, I have tried to download from the link you gave me, and another place but neither work, once it searches for drivers again after download it just says drivers not found
saying that after trying 'adb devices' i got a random string of letters and numbers, roughly 21 characters long followed by recovery on the same line
Click to expand...
Click to collapse
Hmm if adb devices returned that, that means adb is working which means at least part of the drivers loaded correctly. I would grab the files from here:
http://forum.xda-developers.com/showthread.php?t=2736854
And then adb push the files to the /sdcard/. You want the Philz recovery, and the rom. You can grab the root and the kernel if you want to be rooted and the kernel might make a difference in battery life and performance. Whether that is a positive or negative influence, I've no clue. The poster seemed to like it, and he would know better than I. So you just want to download the files needed and put them in the same folder where you have your adb files. Then for each one you want to use:
adb push
then
nameoffile.zip - where you fill in the name of file with whatever (you can rename the files - but not extensions - to be easier, ie recovery.zip, rom.zip)
then /sdcard/
Full command of pushing the rom to the internal storage, assuming you renamed it to rom.zip would be:
adb push rom.zip /sdcard/
This will take awhile. Probably a good 10 minutes.
After you get it transferred over, then install the recovery zip in your current recovery and then reboot to recovery again so you will be in the new Philz. Then do a factory reset and install the rom zip.
es0tericcha0s said:
Hmm if adb devices returned that, that means adb is working which means at least part of the drivers loaded correctly. I would grab the files from here:
And then adb push the files to the /sdcard/. You want the Philz recovery, and the rom. You can grab the root and the kernel if you want to be rooted and the kernel might make a difference in battery life and performance. Whether that is a positive or negative influence, I've no clue. The poster seemed to like it, and he would know better than I. So you just want to download the files needed and put them in the same folder where you have your adb files. Then for each one you want to use:
adb push
then
nameoffile.zip - where you fill in the name of file with whatever (you can rename the files - but not extensions - to be easier, ie recovery.zip, rom.zip)
then /sdcard/
Full command of pushing the rom to the internal storage, assuming you renamed it to rom.zip would be:
adb push rom.zip /sdcard/
This will take awhile. Probably a good 10 minutes.
After you get it transferred over, then install the recovery zip in your current recovery and then reboot to recovery again so you will be in the new Philz. Then do a factory reset and install the rom zip.
Click to expand...
Click to collapse
Which of those files should I download.
as I understand it, once downloaded and in the file with the ADB.
adb devices (to make sure it is connected)
then
adb push recovery.zip /sdcard/ (saying recovery if I rename the file, and pushing the recovery is first?)
then straight after do I push the rom, after rebooting the device, or push them both - reboot the device then install the rom from the recovery?
the first file is Open Euro D80220D.zip - this is the rom, right? and since it is .ZIP do I extract it to the folder where the ADB is or keep it as .zip to push it?
sorry, I'm really new to all this stuff and starting to regret rooting in the first place.
yoalphadied said:
Which of those files should I download.
as I understand it, once downloaded and in the file with the ADB.
adb devices (to make sure it is connected)
then
adb push recovery.zip /sdcard/ (saying recovery if I rename the file, and pushing the recovery is first?)
then straight after do I push the rom, after rebooting the device, or push them both - reboot the device then install the rom from the recovery?
the first file is Open Euro D80220D.zip - this is the rom, right? and since it is .ZIP do I extract it to the folder where the ADB is or keep it as .zip to push it?
sorry, I'm really new to all this stuff and starting to regret rooting in the first place.
Click to expand...
Click to collapse
Download the rom and the recovery. It's up to you about the SU zip and kernel.
Push both.
Install recovery zip then the reboot recovery (adb reboot recovery or via the settings in recovery itself)
Factory reset then install rom (yes, Open Euro.zip is the rom)
Install kernel and SU now if you want - wipe caches if you do then reboot
es0tericcha0s said:
Download the rom and the recovery. It's up to you about the SU zip and kernel.
Push both.
Install recovery zip then the reboot recovery (adb reboot recovery or via the settings in recovery itself)
Factory reset then install rom (yes, Open Euro.zip is the rom)
Install kernel and SU now if you want - wipe caches if you do then reboot
Click to expand...
Click to collapse
Okay, I just tried pushing the rom, the line entered, i got no return so far but it won't allow me to type anything else in the CMD, i'm guessing its because it's pushing the file?
es0tericcha0s said:
Download the rom and the recovery. It's up to you about the SU zip and kernel.
Push both.
Install recovery zip then the reboot recovery (adb reboot recovery or via the settings in recovery itself)
Factory reset then install rom (yes, Open Euro.zip is the rom)
Install kernel and SU now if you want - wipe caches if you do then reboot
Click to expand...
Click to collapse
The recovery is working fine, but after factory resetting, and then trying to install the rom.zip it tries to open it
then e: cant open /data/media/rom.zip
(bad)
installation aborted
es0tericcha0s said:
Download the rom and the recovery. It's up to you about the SU zip and kernel.
Push both.
Install recovery zip then the reboot recovery (adb reboot recovery or via the settings in recovery itself)
Factory reset then install rom (yes, Open Euro.zip is the rom)
Install kernel and SU now if you want - wipe caches if you do then reboot
Click to expand...
Click to collapse
I didn't actually check to see if i got any errors during the push, so i tried pushing again with a different name rommy.zip and got this error
cannot read 'rommy.zip' : input/output error
3583 KB/s <1372848128 bytes in 374.008s>
yoalphadied said:
I didn't actually check to see if i got any errors during the push, so i tried pushing again with a different name rommy.zip and got this error
cannot read 'rommy.zip' : input/output error
3583 KB/s <1372848128 bytes in 374.008s>
Click to expand...
Click to collapse
Are you trying to sideload it? This is different than pushing the file. You don't need to sideload it. Just plug it in and adb push the files you need to the /sdcard/. And are you trying to install it with Philz?
es0tericcha0s said:
Are you trying to sideload it? This is different than pushing the file. You don't need to sideload it. Just plug it in and adb push the files you need to the /sdcard/. And are you trying to install it with Philz?
Click to expand...
Click to collapse
After realising that the push hadnt completed properly, I redownloaded the file, and then pushed it - now it has got past where it had the error and is at 'installing KitKat 4.4.2 ROM
Thanks for your help, greatly appreciated.
What are the benefits of using the Kernal you mentioned earlier?
maybe everything isn't as clear cut as it seemed, after the ROM installed correctly it asked me to reboot now, so I did and now I'm back stuck on the LG splash screen.
Maybe the rom is the wrong one for my phone? It's an LG G2 16gb D802 UK on EE.
yoalphadied said:
After realising that the push hadnt completed properly, I redownloaded the file, and then pushed it - now it has got past where it had the error and is at 'installing KitKat 4.4.2 ROM
Thanks for your help, greatly appreciated.
What are the benefits of using the Kernal you mentioned earlier?
maybe everything isn't as clear cut as it seemed, after the ROM installed correctly it asked me to reboot now, so I did and now I'm back stuck on the LG splash screen.
Maybe the rom is the wrong one for my phone? It's an LG G2 16gb D802 UK on EE.
Click to expand...
Click to collapse
Ohhh I think that one might be for the 32 GB one. Sorry. *edit*
You can try this one: http://forum.xda-developers.com/showthread.php?t=2681205
es0tericcha0s said:
Ohhh I think that one might be for the 32 GB one. Sorry. *edit*
You can try this one: http://forum.xda-developers.com/showthread.php?t=2681205
Click to expand...
Click to collapse
Should i try installing the kernal? See if that works? As it does say in comments that the 1st works for 16 &32
*EDIT*
install Kernal & supersu doesn't resolve the issue, going to try the new rom you posted now
yoalphadied said:
Should i try installing the kernal? See if that works? As it does say in comments that the 1st works for 16 &32
Click to expand...
Click to collapse
That's what I would do. Won't make it worse. Might help. If not, it's only a few more minutes altogether to try. Just make sure to wipe cache and dalvik cache.
es0tericcha0s said:
Ohhh I think that one might be for the 32 GB one. Sorry. *edit*
You can try this one: http://forum.xda-developers.com/showthread.php?t=2681205
Click to expand...
Click to collapse
Okay, I came across another problem.
with the several versions of the same ROM at /sdcard/ my memory was running low, so i formatted it - then it wouldn't let me push anything to it, anyway i sorted that (can't remember how) and then installed the Kernal and superuser, which didn't seem to sort anything, but I did a little digging and mounted all the directories on Philz.
Then after I restarted the phone, whilst trying to get into recovery I heard the 'LG' splash screen animation noise. and then the phone loaded up the country setting - and then I got an error which made the screen unresponsive, I tried reloading to get yet another error, similar but not the same.
I booted into recovery, did a factory reset and again rebooted the phone and now it works, with the Knock Code! thank you so much you have saved my phone..
Is there anything I can do to say thank you properly, you've just saved me over £250

[Q&A] [ROM + KERNEL] Tari's ASUS PadFone 2 (r150301)

Q&A for [ROM + KERNEL] Tari's ASUS PadFone 2 (r150301)
Some developers prefer that questions remain separate from their main development thread to help keep things organized. Placing your question within this thread will increase its chances of being answered by a member of the community or by the developer.
Before posting, please use the forum search and read through the discussion thread for [ROM + KERNEL] Tari's ASUS PadFone 2 (r150301). If you can't find an answer, post it here, being sure to give as much information as possible (firmware version, steps to reproduce, logcat if available) so that you can get help.
Thanks for understanding and for helping to keep XDA neat and tidy!
Hello Tari! I have Running your awesome ROM on my Padfone2, and i find it a very smooth and cool ROM! Thank You, for your Work in it!
I have a Question, - There is a Custom Lollipop ROM on XDA for Padfone S/X! Do you think that work on Padfone2? And the Nexus4 is almost the same hardware as Padfone2, is it possible that a Nexus4 Custom Lollipop ROM works on Padfone2?
Many, Thanks to you for your Work, Time and Engagement!
roselanguste said:
Hello Tari! I have Running your awesome ROM on my Padfone2, and i find it a very smooth and cool ROM! Thank You, for your Work in it!
I have a Question, - There is a Custom Lollipop ROM on XDA for Padfone S/X! Do you think that work on Padfone2? And the Nexus4 is almost the same hardware as Padfone2, is it possible that a Nexus4 Custom Lollipop ROM works on Padfone2?
Many, Thanks to you for your Work, Time and Engagement!
Click to expand...
Click to collapse
Thanks for the kind words roselanguste, I am glad you are satisfied with the ROM.
As for the Lollipop, porting it onto the Padfone2 would be lot of work. There are too many ASUS-specific details that would have to be changed, plus for the kernel to work we would need updated hardware modules and firmware. As far as I am concerned, KitKat is the last stop for our device.
can you give me step by step how to flash cwm after unlocking the phone (using ansarijavid method for unlock)?
kinda new for this stuff
running 8.1 64 bit
does this rom fix weird colour contrast after put the phone into sleep?
azurisu said:
can you give me step by step how to flash cwm after unlocking the phone (using ansarijavid method for unlock)?
Click to expand...
Click to collapse
Create a folder, download the needed files into it and open a terminal from there
Make sure the tools are present: sudo apt-get install android-tools-adb android-tools-fastboot
Enable USB Debugging on the phone
Boot into fastboot mode (Power, Volume up)
Install the CWM recovery: sudo fastboot -i 0x0b05 flash recovery cwm.img
Note: The above is for Linux - no extras are needed, you just plug in your phone and go. Windows users should probably need some drivers, enable ADB, and change the "sudo + COMMAND" parts.
azurisu said:
does this rom fix weird colour contrast after put the phone into sleep?
Click to expand...
Click to collapse
I have not had any contrast troubles, so I really can't tell. The kernel is the latest PF2 can handle, and the firmware is also up-to-date. There should be no issues.
tari01 said:
Create a folder, download the needed files into it and open a terminal from there
Make sure the tools are present: sudo apt-get install android-tools-adb android-tools-fastboot
Enable USB Debugging on the phone
Boot into fastboot mode (Power, Volume up)
Install the CWM recovery: sudo fastboot -i 0x0b05 flash recovery cwm.img
Note: The above is for Linux - no extras are needed, you just plug in your phone and go. Windows users should probably need some drivers, enable ADB, and change the "sudo + COMMAND" parts.
I have not had any contrast troubles, so I really can't tell. The kernel is the latest PF2 can handle, and the firmware is also up-to-date. There should be no issues.
Click to expand...
Click to collapse
weird,, i've been experiencing some weird colour issue since kitkat for PF2 released, and still happened on newest fw (11.4.8.23)
locking then unlocking the screen always trigger this, need to restart my device to get it back to normal
something like this..
padfoneclub.com/pl/forum/forum_viewtopic.php?15485
so i thought using custom rom will solve my issue haha
--------
reversiblity
tari01 said:
Create a folder, download the needed files into it and open a terminal from there
Make sure the tools are present: sudo apt-get install android-tools-adb android-tools-fastboot
Enable USB Debugging on the phone
Boot into fastboot mode (Power, Volume up)
Install the CWM recovery: sudo fastboot -i 0x0b05 flash recovery cwm.img
Note: The above is for Linux - no extras are needed, you just plug in your phone and go. Windows users should probably need some drivers, enable ADB, and change the "sudo + COMMAND" parts.
I have not had any contrast troubles, so I really can't tell. The kernel is the latest PF2 can handle, and the firmware is also up-to-date. There should be no issues.
Click to expand...
Click to collapse
i'm a completely noob about linux so my only question is : is the procedure reversible? my only fear is about this " sudo fastboot -i 0x0b05 flash recovery cwm.img" , if i type wrong a value what's going to happen? Brick or simply a failrure in the procedure?
Thanks in advance
Zollolo19 said:
i'm a completely noob about linux so my only question is : is the procedure reversible? my only fear is about this " sudo fastboot -i 0x0b05 flash recovery cwm.img" , if i type wrong a value what's going to happen? Brick or simply a failrure in the procedure?
Thanks in advance
Click to expand...
Click to collapse
This command is fairly safe. It simply means: "use fastboot to write the cwm.img image to an ASUS device (0x0b05 is your PadFone)". If you feel paranoid you can search for a Stock Recovery image. You can always flash that file instead of cwm.img to get your device back to factory state. Bricking is harder than you think. The bottom line: always read the instructions carefully, make sure you have EXACTLY what is required, and go slowly step-by-step. If you are unsure, or there is an error, do not try to fix it by yourself - go to the forums and tell the people about it, someone will surely help you out.
tari01 said:
This command is fairly safe. It simply means: "use fastboot to write the cwm.img image to an ASUS device (0x0b05 is your PadFone)". If you feel paranoid you can search for a Stock Recovery image. You can always flash that file instead of cwm.img to get your device back to factory state. Bricking is harder than you think. The bottom line: always read the instructions carefully, make sure you have EXACTLY what is required, and go slowly step-by-step. If you are unsure, or there is an error, do not try to fix it by yourself - go to the forums and tell the people about it, someone will surely help you out.
Click to expand...
Click to collapse
Thank you for the professional and specially quick answer I'm going to try the procedure tomorrow
i have to leave "A68_signed_030415_031241.zip" zipped?
Thanks
Zollolo19 said:
i have to leave "A68_signed_030415_031241.zip" zipped?
Thanks
Click to expand...
Click to collapse
Yes. ROMs are always packaged in a ZIP - you just send it to your CWM (sideload seems to be the fastest).
it's going automatically in recovery mode? Because i don't know how to enter in it and there're tons of procedure throughout the web.
i'm referring to this point : 3. Boot into recovery mode.
I thought that power + bottom up volume was for the recovery mode, indeed is for the fastboot mode.
Thanks for your courtesy
ULTRA LOL: i forgot to try power + volume down when i wrote this post, sorry xD
Zollolo19 said:
it's going automatically in recovery mode? Because i don't know how to enter in it and there're tons of procedure throughout the web.
i'm referring to this point : 3. Boot into recovery mode.
I thought that power + bottom up volume was for the recovery mode, indeed is for the fastboot mode.
Thanks for your courtesy
ULTRA LOL: i forgot to try power + volume down when i wrote this post, sorry xD
Click to expand...
Click to collapse
So it seems you have got it right, but just for future reference:
Power + Volume Up = fastboot/csc
Power + Volume Down = recovery
It goes for most Android devices, ASUS especially.
i'm blocked at point 9... it says "cannot read sideload".. i've tried solutions found online like rename folder, or use adb push but in this it says "acces: blocked"..
help please :crying:
news: when i tried the normal boot of the padfone it returned to original conditions, it's like new eek: . factory mode returned like new, too
Now how i can use the other procedure (without sideload) ? i have to put simply the file in the root?
Zollolo19 said:
i'm blocked at point 9... it says "cannot read sideload".. i've tried solutions found online like rename folder, or use adb push but in this it says "acces: blocked"..
help please :crying:
news: when i tried the normal boot of the padfone it returned to original conditions, it's like new eek: . factory mode returned like new, too
Now how i can use the other procedure (without sideload) ? i have to put simply the file in the root?
Click to expand...
Click to collapse
I see no reason why sideload or push shouldn't work. When you enter CWM recovery you select the sideload option and then send your ROM from the PC. On Debian and derivatives (Ubuntu, Mint, etc.) adb/fastboot tools are in system locations, so you need to run the commands with "sudo" to elevate your privileges.
Here are the detailed steps:
Boot into fastboot mode (Power, Volume up)
Install the CWM recovery: sudo fastboot -i 0x0b05 flash recovery cwm.img
Boot into recovery mode (Power, Volume down)
Select "wipe data/factory reset"
Select "install zip from sideload"
Send the ROM to the phone: sudo adb sideload ROMNAME.zip
Wait until it says it's done, then select "reboot"
When CWM asks "ROM may flash stock rocovery on boot. Fix?" Choose "No"
When CWM asks "ROM access possibly lost. Fix?" Choose "No"
Alternatively, you could simply plug in your phone, copy the ROM to the root folder (/sdcard) using nautilus/nemo or any other file manager you're using, then go to CWM and select "Install zip from SD card", then browse for it.
As for your phone looking like a fresh one, it's because you still have the stock ROM and it has been reset to factory settings. This should not bother you at all.
I tried everything with ubuntu but nothing... so i put the rom in the root and flashed by sd card. Everything seems to be ok now DDD I'm trying your rom like now.
Thanks a lot
Hey im happy to see a nice Rom for my womens padfone 2! The only Problem is the i have a Invalidit kernel.. And no boot for me) = i can only boot with Superboot trick. I need help to repair this phone.. please help me.
locce said:
Hey im happy to see a nice Rom for my womens padfone 2! The only Problem is the i have a Invalidit kernel.. And no boot for me) = i can only boot with Superboot trick. I need help to repair this phone.. please help me.
Click to expand...
Click to collapse
I think we need to know a little bit more about your problem to see if there is help:
- How did you get an invalid kernel?
- Is the device unlocked/do you have custom recovery on it?
Im New in the asus sector...okay I have root with towelroot and forget to unlock the bootloader!!! The not normal booting and Invalid kernel Problem is coming from twrp flash.
locce said:
Im New in the asus sector...okay I have root with towelroot and forget to unlock the bootloader!!! The not normal booting and Invalid kernel Problem is coming from twrp flash.
Click to expand...
Click to collapse
Unlocking the bootloader is always the first step. You can fix things, though. First, remove towelroot, and any other rooting mechanisms you may have - you do not need them, custom roms are pre-rooted.
If you are running a 4.1 or 4.2 ROM follow the points from this post
If you have KitKat, it is a bit more complicated, see this post
WARNING: If your device has been serviced (specifically the motherboard replaced), you will not be able to unlock it!

Recovery mode without hardware keys

Is there a possibility to go into the recovery mode without using hardware keys or apps in a ROM?
Situation:
Download mode with odin works.
Power button destroyed.
Volume up + Home button brings no effect.
If it starts, it boots to ROM-Splash and seems to stuck in a bootloop.
Flashed Custom ROMs and Stock ROM, 1 and 3 parted - no success.
Is there a way to force the I9100 to boot into the recovery without Apps, Android or hardware keys?
In best, out of download mode with odin, like "odin force reboot"-tar file.
You can use adb. I think there is command like fastboot reboot recovery or something like thah
Sent from my iPad using Tapatalk
MatNEWBIE said:
You can use adb. I think there is command like fastboot reboot recovery or something like thah
Sent from my iPad using Tapatalk
Click to expand...
Click to collapse
Thanks für your replay.
adb oder fastboot reboot recovery does not work - impossible to get a connection to device.
Isn't it possible to write a tar file and flash it via Odin that lets the device start into recovery next time?
I was never doing so. I don't use Odin too often, to get learn more I'm trying to do staff using adb... Hmmmm..... Were you trying to just flash stock kernel? Or kernel with philz? (Btw have you seen somewhere unsecured kernel with twrp same as stock? Share link if you had plx)
For this tar file... I think it's quite possible so search further.
P.S. I'm quite sure that I read that you can get out of such brick with adb but I forget how...
Sent from my iPad using Tapatalk
MatNEWBIE said:
Were you trying to just flash stock kernel?
Click to expand...
Click to collapse
No, always flashed 1 or 3 parted stuck ROM.
You think about formatting internal SD with pit-file and flash stock kernel from 3-parted stock ROM?
I don't remember where I could find it.
Would be a try, I think, whether it boots only into recovery after flashing.
I remember once, I flashed a kernel with CWM and that happend.
But never again.
Or kernel with philz?
Click to expand...
Click to collapse
Yes, no chance.
Only boots Stock ROM and bootloops.
I can't get into recovery, thats the problem.
(Btw have you seen somewhere unsecured kernel with twrp same as stock? Share link if you had plx)
Click to expand...
Click to collapse
not yet. If so, I'll link (try this first: http://www.cyanogenmod-forum.de/Thread-DOWNLOAD-TWRP-Downloadlinks)
For this tar file... I think it's quite possible so search further.
P.S. I'm quite sure that I read that you can get out of such brick with adb but I forget how...
Click to expand...
Click to collapse
I hope so.
ADB: I can't a a connection to the device, that's the problem. Else I could use adb reboot recovery to get into recovery and flash a new ROM, wiping, etc.
But I can't geht into recovery.
I really need such a script.
It is possible to create odin-friendly tar-files, but I don't know what to put in so it boots into recovery afterwards.

Categories

Resources