Related
Rooted my Transform and went in to the superuser APK.... I'm disappointed that it has very limited content vs. my buddies HTC EVO. I'm new to Androids, but anyone know if there would be a way to port the superuser APK from the HTC EVO to the Samsung Transfrom, or is it even Feasible?
Can you go into more detail on how you rooted your Samsung Transform. I have tried SuperOneClick but the root never sticks. I would lose superuser randomly.
I just rooted with Super One Click, now, i dont know what to do with it lol. It sticks with me though.
No need for a superuser port. Just download from the market after rooting
via skeeterslint sdx:
Heres is a one click recovery installer for people that don't want to do it by hand.
http://www.mediafire.com/?jl21knp1d0lbf17
This is a still beta but working version of SDX Recovery version 3.1.1.
Things known to work.
Backups and restores.
Clearing dalvik cache.
Clearing cache partition.
Flashing kernel zImages.
Flashing zip files.
Adb works in recovery.
Also mounting the sdcard to your computer works.
Anything else in the options is still in need of testing I am not responsible if your phone gets bricked.
THIS MAY BRICK ALL PHONE MODS YOU DO AT YOUR OWN RISK!
OK now that thats out of the way heres the files needed.
1. http://www.mediafire.com/?862j3wlzftenwef This is the recovery image.
2. http://www.mediafire.com/?67an7lkm9qtmf5b until there is a custom recovery you will need this program to flash recovery. Its called flash_image.
3. http://www.mediafire.com/?5dcv3r14sjvsfdq rage.bin temporary exploit to get root.
4. You will also need the Android SDK so you have a working adb to be able to push files over to your phone.
If you are flashing this from a phone running my rooted kernel you can skip steps 4 and 7 and just su over to a root prompt.
OK these are the steps to install this recovery.
1. Make sure adb is installed and working there are how to's on the forum to get this setup or just use google.
2 adb push recovery.bin /data/local/tmp to move the kernel to the phone.
3 adb push flash_image /data/local/tmp to move flash_image onto the phone.
4 adb push rage.bin /data/local/tmp to move rage.bin onto the phone.
5. Run adb shell to get to a shell prompt on the phone.
6. Run chmod 755 on flash_image and rage.bin chmod 755 rage.bin chmod 755 flash_image.
7. Run ./rage.bin and let it go run through untill it exits you out of adb.
8. adb shell you should now have a root shell on the phone.
9. Run ./flash_image recovery recovery.bin to install the kernel.
Once its installed to get into recovery use Volume down Camera and power to get into recovery.
Volume up and down scroll through the option.
Menu should be the enter key.
Back button is back.
Search key is delete.
You will need to create the directorys on your sdcard that recovery needs to flash zip files make backup and flash kernel and recovery from.
Create directory called sdx on the root of the sdcard and inside it create 3 folders zips update and backup.
At this time it seems that factory restore is not working correctly and anyone else can confirm please let me know.
And for better recovery via vampirefo on sdx:
his is my first recovery, I made the change to the first screen to show that this is a transform recovery rather than a moment recovery. Also I got console to work in recovery, it wont rotate but works just fine.
http://www.4shared.com/file/bBTlN7UZ/recoveryrfs.html
You can flash this via swupdate, or if you already have skeeters recovery installed, just extract recovery.tar to /sdcard/sdx/updates
boot to recovery
Scroll down to
Backup, Restore, Flash
Scroll down to
Flash Recovery
After flash is complete
press back button
Under Reboot options choose Reboot to Recovery to see new recovery
HII GUYS THIS THREAD IS ALL ABOUT LG P690:-
FIRST
/////////////////////////////ROOTING:-/////////////////////////////
Code:
http://forum.xda-developers.com/showthread.php?p=21348926
2)Custom Recovery for LG Optimus Net - Clockwork 5.0.2.7
DOWNLOAD ALL THESE FILES:-REQUIREMENTSFLASH_IMAGE
RECOVERY IMAGE
ADB RUNNING
http://developer.android.com/sdk/index.html
The Recovery can be installed as follow:
•Download recovery.img from the link attachment
•IMPORTANT: Check MD5SUM - This is to ensure that during the download / copy the file is not corrupted
•Copy recovery.img to the SD
•download Flash_image, unzip and copy it to SD
Now you must install the recovery through ADB (the commands must be entered one by one in the shell, waiting a couple of seconds between one and another.
Code:
$ adb shell
# su
# mount -o remount,rw -t yaffs2 /dev/block/mtdblock1 /system
# cat /sdcard/flash_image> /system/bin/flash_image
# chmod 755 /system/bin/flash_image
# mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.bak
# mount -o remount,ro -t yaffs2 /dev/block/mtdblock1 /system
# flash_image recovery /sdcard/recovery.img
# reboot recovery
Note: the command
Code:
mv /system/etc/install-recovery.sh /system/etc/install-recovery.sh.
WILL GIVE YOU SOME ERROR IGNORE IT
If all goes well, the menu with a cheerful hat ClockworkMod background confirms that the boot recovery occurred in CW.
Also ignore the error below: "E: bad boot message" is not a real error.
The recovery functionality is simple:
- The volume keys to scroll
- The back button to go back
- The power button to select a menu item.
If you have problems, you can select Advanced / Error Reporting. This will generate a log into SD (recovery.log). You can use it to understand the problem.
/////////////////////////////
[HOWTO] Flash original firmware on P690
http://forum.xda-developers.com/showthread.php?t=1483192
[HOWTO] Flash DOWNLOAD firmware on P690
http://forum.xda-developers.com/showthread.php?t=1483180
/////////////////////////////
///////////////////////////////
[ROM] DarDroidXD_0.3 [LGP690]
http://forum.xda-developers.com/showthread.php?t=1483206
//////////////////////////////
This guide works 100% , just used it now waiting for custom recovery to download.
Majestic36 said:
This guide works 100% , just used it now waiting for custom recovery to download.
Click to expand...
Click to collapse
Doesnt work for me, recovery just freezes at the LG screen
Need to understand what is recovery and custom installation
May I know what is Custom Recovery for LG Optimus Net - Clockwork 5.0.2.7 and what it do?
and what is installing cyanogenmod 7.0 is it a custom rom and is it better then stock rom?
Hi guys,
I have problem. I rooted my LG P690 and installed CWM bootloader. During installing custom ROM my phone bricked and rebooted after LG initial picture. I was able to enter only RECOVERY MODE by pressing PWR+BACKARROW+VOL_UP. But that was all, I couldn't also repair phone through HDZ_FW_UPD.exe , because problem with USB drivers. I tried everything, but without success. But I was able to connect to phone via ADB commands, downloaded update.zip, added it near fastboot.exe file, run fastboot and install that update.zip. I removed SD card to other phone, connected, uploaded some CyanogenMod 9 and moved SD card back to LG P690. Now I was able to enter BOOTLOADER (BUT I DON'T REMEMBER COMBINATION OF BUTTONS DURING SWITCHING PHONE !!!), and installed CyanogenMod9. Everything looks OK, but after rebbot and entering new Android OS my touch screen isn't working. I don't know why, but I think that problem is in that CyanogenMod9 version - it doesn't recognize touching screen. It reacts to pressing Vol UP/DOWN buttons (setting volume), pressing BACK button or long pressing PWR button. But that's all. I can turn off the phone by remobing battery. When it's ON and I connect it via USB, I cannot use ADB.exe or FASTBOOT.exe commands because PC donesn't recognise device
So now the question - how to enter bootloader during power ON sequence? I tried all combinations:
- pressing and holding PWR+VOL UP
- PWR+VOL DOWN
- quick pressing of VOL UP
- quick pressing VOL DOWN
- pressing PWR+BACK+VOL UP
- pressing.....and so on and so on
I don't know why I cannot access bootloader becasue before I did it without any problem....Can you please write me detailed "butto n sequence" for entering bootloader on LG P690 Optimus Net? Or am I LOL?
Thank you very much
Rado
SOLVED -> entering bootloader works with pressing HOME+VOL_DOWN+PWR_ON
Do it at your risk!
Hi,everybody.
I had successfully ported CWM recovery&Bootmenu 2ndinit for spice,which allows us to use custom rom.
Now,you have two ways to use CWM recovery.One is entering CWM recovery through bootmenu,the another way is entering CWM recovery through stock recovery(Fake flash update zip).
Method 1:Through bootmenu
First of all,you need to root your spice.And then install bootmenu.
Download the bootmenu.tar file(attached).And push it into /sdcard/
Turn on usb debugging on your phone. And use the following commands in adb:
Code:
C:/> adb shell
$ su
# mount -o remount,rw /dev/block/mtdblock1 /system
# mkdir /system/bootmenu
# cd /system/bootmenu
# busybox tar -xf /sdcard/bootmenu.tar
# rm /system/bin/charge_only_mode
# busybox ln -s /system/bootmenu/binary/bootmenu /system/bin/charge_only_mode
# sync
# mount -o remount,ro /dev/block/mtdblock1 /system
# exit
The bootmenu will be installed.
Restart your device once.
Using Boot Menu:
Turn your phone off.
Press the Power Button.
After 1-10 seconds, the red led on your phone will light up for just 3 seconds (Still while the Motorola logo is being displayed).
Exactly when the led lights up, press the volume down button.
You will see the BootMenu, use the Volume Button to navigate up and down, and the power button to select an item.
Then you can select enter CWM recovery.(Someone say CWM's backup&restore cannot work,you can use method 2 for it)
Method 2:Through stock recovery(Fake flash zip)
I found that we can use CWM recovery with stock recovery leak(Fake flash update zip,like OpenRecovery),but this leak is only existed in SESGC_U3_10.10.0_RT firmware.
I have dumped this recovery(Attached file:recovery.img).And flash it by fastboot.It works well with SESLA_U3_01.72.0 firmware.
And then to flash a fake update.zip(Attached file:update.zip) from the root of your sdcard,you will enter CWM recovery!
By the way,if you want to port CM7 for spice,you need to use 2ndinit for your froyo/gingerbread,because it has locked bootloader.
I have compiled CM7 for it,and it can boot up but stuck in white screen after CM bootanimation.If you want to continue my work,you can checkout my github.
Thanks to:
CyanogenMod
koush
...
sorry for my poor English.
With the first method i can't make a nandroid backup, i'll try it with the second!
Nand backup question
GentryLamp said:
Do it at your risk!
Hi,everybody.
I had successfully ported CWM recovery&Bootmenu 2ndinit for spice,which allows us to use custom rom.
Now,you have two ways to use CWM recovery.One is entering CWM recovery through bootmenu,the another way is entering CWM recovery through stock recovery(Fake flash update zip).
Method 1:Through bootmenu
First of all,you need to root your spice.And then install bootmenu.
Download the bootmenu.tar file(attached).And push it into /sdcard/
Turn on usb debugging on your phone. And use the following commands in adb:
Code:
C:/> adb shell
$ su
# mount -o remount,rw /dev/block/mtdblock1 /system
# mkdir /system/bootmenu
# cd /system/bootmenu
# busybox tar -xf /sdcard/bootmenu.tar
# rm /system/bin/charge_only_mode
# busybox ln -s /system/bootmenu/binary/bootmenu /system/bin/charge_only_mode
# sync
# mount -o remount,ro /dev/block/mtdblock1 /system
# exit
The bootmenu will be installed.
Restart your device once.
Using Boot Menu:
Turn your phone off.
Press the Power Button.
After 1-10 seconds, the red led on your phone will light up for just 3 seconds (Still while the Motorola logo is being displayed).
Exactly when the led lights up, press the volume down button.
You will see the BootMenu, use the Volume Button to navigate up and down, and the power button to select an item.
Then you can select enter CWM recovery.(Someone say CWM's backup&restore cannot work,you can use method 2 for it)
Method 2:Through stock recovery(Fake flash zip)
I found that we can use CWM recovery with stock recovery leak(Fake flash update zip,like OpenRecovery),but this leak is only existed in SESGC_U3_10.10.0_RT firmware.
I have dumped this recovery(Attached file:recovery.img).And flash it by fastboot.It works well with SESLA_U3_01.72.0 firmware.
And then to flash a fake update.zip(Attached file:update.zip) from the root of your sdcard,you will enter CWM recovery!
By the way,if you want to port CM7 for spice,you need to use 2ndinit for your froyo/gingerbread,because it has locked bootloader.
I have compiled CM7 for it,and it can boot up but stuck in white screen after CM bootanimation.If you want to continue my work,you can checkout my github(["github . com/gentrylamp").
Thanks to:
CyanogenMod
koush
...
sorry for my poor English.
Click to expand...
Click to collapse
Hello!
Mr GentryLamp, congratulations done, I do not see many people who understand Android programming interested in XT300, you're the man!
I performed all the procedures above, installed bootmenu (but renamed the "charge_only_mode" as "charge_only_mode.bin" the backup purposes), I installed the old recovery with flash_image (command "flash_image recovery path_of_recovery _.img") and put the update.zip on the root of SD.
I can not perform with nand backup recovery from bootmenu (advance notice, and obviously non-functional), and the second way does not work (the leakage update.zip).
When trying to nand backup the nand, the device is the screen backuping ("SD memory free... Backup system...") For about an hour, and then the screen goes white, and end.
You know how I could accomplish this nand backup? You got on your device? Do you know any script that I can use for it?
If you need more information, or something that I test on my device, I place myself at your disposal.
Sorry my english too, Google Translate help much Brazilians.
Hug.
Regisboliver said:
Hello!
Mr GentryLamp, congratulations done, I do not see many people who understand Android programming interested in XT300, you're the man!
I performed all the procedures above, installed bootmenu (but renamed the "charge_only_mode" as "charge_only_mode.bin" the backup purposes), I installed the old recovery with flash_image (command "flash_image recovery path_of_recovery _.img") and put the update.zip on the root of SD.
I can not perform with nand backup recovery from bootmenu (advance notice, and obviously non-functional), and the second way does not work (the leakage update.zip).
When trying to nand backup the nand, the device is the screen backuping ("SD memory free... Backup system...") For about an hour, and then the screen goes white, and end.
You know how I could accomplish this nand backup? You got on your device? Do you know any script that I can use for it?
If you need more information, or something that I test on my device, I place myself at your disposal.
Sorry my english too, Google Translate help much Brazilians.
Hug.
Click to expand...
Click to collapse
I haven't confirmed whether NAND backup will work in bootmenu,but it works well in fake update.zip way.
If your firmware version is SESLA_U3_01.72.0,you need to boot the phone into fastboot mode(bule screen,pressing Vol-up&Vol-down while the phone boots up),and using fastboot to flash recovery.img.
BTW:Some firmware(such as SESGC_U3_10.10.0_RT) do not allow fastboot.You can see some warnings in fastboot bule screen.
More questions...sorry
GentryLamp said:
I haven't confirmed whether NAND backup will work in bootmenu,but it works well in fake update.zip way.
If your firmware version is SESLA_U3_01.72.0,you need to boot the phone into fastboot mode(bule screen,pressing Vol-up&Vol-down while the phone boots up),and using fastboot to flash recovery.img.
BTW:Some firmware(such as SESGC_U3_10.10.0_RT) do not allow fastboot.You can see some warnings in fastboot bule screen.
Click to expand...
Click to collapse
Thanks for reply man o/
My firmware is SESLA_U3_01.72.0, nand backup really not work on first method, and in the second method, also not .
I followed a guide like this: [ht tp:// forum . xda-developers . com/showthread.php?t=918275]. I believe the command is flash_image the same effectiveness as the fastboot, because I could run the CWM_recovery from the update.zip (you said that this gap is only SESGC_U3_10.10.0_RT recovery firmware, and I do not use - no clue of what it is, just know mine, and Chinese MONSTER).
But I saw now that you've lost your XT300 and therefore believe that there is no possibility to test or you do something for it. But anyway, I am grateful and even my disposal device testing, if desired.
Taking advantage ... would be able to put an 'if' that is, the low volume was not pressed, he continued with the 'charge_only_mode', so that the battery could be charged with the device off? I would also like to know if you know if it is possible to make a nand backup from a script, with the connected device, and if you have some kind of script ...
Excuse me for asking so many questions to you is that I know someone who knows and is as interested as you.
Thank you!
Hug.
i had the same problem with NAND backup using method 2
Regisboliver said:
the low volume was not pressed, he continued with the 'charge_only_mode', so that the battery could be charged with the device off?.
Click to expand...
Click to collapse
The phone will not enter charge only mode when you install bootmenu.
In method 2,NAND Backup&Restore works well when I use spice,I'm sorry that it doesn't work with some phone.
GentryLamp said:
The phone will not enter charge only mode when you install bootmenu.
In method 2,NAND Backup&Restore works well when I use spice,I'm sorry that it doesn't work with some phone.
Click to expand...
Click to collapse
I understand that only with bootmenu the device not charge without boot but, my question was would like to know if one can apply this procedure to boot: power button pressed > magenta led light and Motorola logo > {(before bootanimation and bootinstructions) volume down button pressed while red led light? "yes? -> bootmenu" | "no? -> execute the real charge_only_mode binary", execute charge_only_mode.bkp for example, in my case, since renamed the original charge_only_mode for subsequent restoration of boot } > boot. Understand my question? :s
But if there is, I made two scripts, one for installation and uninstallation of another bootmenu (if someone wants I can post), but if you do not give to run the above algorithm, I use the update.zip CWM_recovery the same, so I can recharge my device is switched off, while I find I try to do a custom for 2ndinit.
Mr GentryLamp, you said above, in the opening thread, it has ported a CM7 for XT300 and it crashed after the Motorola logo. I some time ago, I replaced the file libGLES_android.so (in the folder / system / lib / egl), trying to enable the GPU, I fear there is not even in the chipset of XT300 and while on the Motorola logo, the screen was white, blinking. You keep intact the lib folder? Forgive me if I did wrong or very noob question, because I have no expertise in ROM switches, ports, CM, etc...
Regarding the nand backup, searched about it here, to see if I can find at least one script for it, because then I can become more peaceful to test changes more dangerous, not bothering with RDS, SBF ...
Thanks again bro!
Is there a way to port to other Motorola devices? I have a DROID x that I need to try this on because it is stuck in safe mode. How did you port this to flash in stock recovery?
Sent from my DROID4 using Tapatalk 2
Great job, but I think this work is not useful because we don't have a custom Rom for this phone and the stock Rom sucks, I have this xt300 from my carrier iusacell Mexico, and is so slow and to f**king buggy, if is thera a chance to have a good froyo or gingerbread stable Rom will be perfect this phone have some potential but is too capable by the Motorola software
I hope we can some time get a good Rom for this great and cheap phone
hello all,
this recovery is not ported by me, xda's senior member fun_ have ported this to many devices, and we using the one which is compatible with paladin, many many thanks to him, a link to original thread is here
requirements:-
1. a rooted phone, you can root your tab here
2. cwm recovery image which you can get here
steps:-
1. open file manager which can have root access
2. go to system and rename recovery.cpio.img to recovery.cpio.img.bak
3. put downloaded recovery in /sdcard
4. open terminal emulator
5. type su
6. type "inand_flash_image recovery /mnt/sdcard/recovery.cpio.img" (if you have put it in flash then replace sdcard with flash)
7. then boot into recovery by holding menu and power button together or by typing "reboot recovery" in terminal emulator
how to control recovery:-
# power button is used to select options
# menu button will take you up
# home button will get you down when pressed
some notes you should keep in mind:-
1. back button do not work in recovery
2. never try the key test option else you will get stuck
3. backup do not work for boot, xboot, mbr areas
4. do not flash any rom available for paladin, basic etc. devices (or you will have a hard bricked tablet)
a simple step to enable on-screen back button
as soon as you booted into recovery, press menu then home then again menu, a message will appear saying enabled ( can be done in every screen)
Cwm
Nt able to rename recovery.cpio.img to recovery.cpio.img from andro zip, es file explorer,terminal . . ? Any solution?
in terminal type
Code:
su
mv /system/recovery.cpio.img /system/recovery.cpio.img.bak
dheeraj (dhlalit11) said:
in terminal type
Code:
su
mv /system/recovery.cpio.img /system/recovery.cpio.img.bak
Click to expand...
Click to collapse
failed - read only file system . . . ? . . Any other way to rename this file
pbhasin21 said:
failed - read only file system . . . ? . . Any other way to rename this file
Click to expand...
Click to collapse
tab is not rooted root it first
http://forum.xda-developers.com/showthread.php?p=29100664
dude i followed ur steps, used root explorer to rename to bak, and then tried, i get kcrc32 file size not same. and then when i boot to recovery the whole screen goes berzerk with curtain falls and doesn't do anything. i renamed the bak file into normal and flashed it and got the old recovery.. could you tell me what im doing wrong? used your recovery.cpio.img 3.5mb file in my sdcard... doesnt work..
rooted karbonn smart tab
kcrc32 not same is normal
did the terminal flash the recovery 2 times
like:-
kcrc32 not same
then a hex address
flashing from /mnt/sdcard
kcrc32 not same
then a hex address
flashing from /mnt/sdcard
if you get something like above then it is flashed properly
dheeraj (dhlalit11) said:
kcrc32 not same is normal
did the terminal flash the recovery 2 times
like:-
kcrc32 not same
then a hex address
flashing from /mnt/sdcard
kcrc32 not same
then a hex address
flashing from /mnt/sdcard
if you get something like above then it is flashed properly
Click to expand...
Click to collapse
yup i got it twice, kcrc32 not same.
then i entered reboot recovery. thats when the screen goes all curtainfall like a crash, and recovery doesn't load. i had to use the reset pin and power button to turn on the tab again.. perhaps the img is not compatible with my tab?
btw mine is Karbonn Smart Tablet 2.
http://ncarry.nimbuzz.com/karbonn/product.php?product_id=2212
but when i purchased, it came with android 4.0 ics. everything else is same as in that page..
it is different
and I think that's why recovery is not booting
any suggestions mate? perhaps another ainol tab is similar to karbonn st2?
What if there is no "recovery.cpio.img" file in the system folder? This is after having root permissions...nothing has been done otherwise. I do not have a recovery file to rename and am unsure if it should still go in the system folder or not. It doesn't even have a file extension (I had to transfer it to my laptop just to check, and there's no .img or .zip...nothing.)
Also I keep getting the following message in terminal emulator when attempting to run the command:
sh: inand_flash_image: not found. The image file is in the /mnt/sdcard/Download folder. The full instance is:
[email protected]:/ $ su
[email protected]:/ # inand_flash_image recovery /mnt/sdcard/Download/recovery.cpio.img
sh: inand_flash_image: not found
127|[email protected]:/ # inand_flash_image
sh: inand_flash_image: not found
Any help?
Pantech Discover P9090 (Magnus) Root & Modification Guide
This thread is intended as an updated version of the original Ultimate Pantech Discover/Magnus/P9090 Rooting & Modding Thread thread. I created this thread to bring the latest knowledge and tutorials to the top. If you are interested in the evolution of Discover rooting and modding pour yourself a cup of coffee, tea, or ??? and review the posts in that thread and when you are ready to modify your Discover come back here.
Available Mods
Root access
ClockworkMod Recovery
TWRP Recovery
Restore unlocked bootloader for Jellybean devices
CWM flashable ROM/partition updates
Warning/Disclaimer
The tutorials posted in this thread at the time of this writing have been tested and should do what they claim to do without causing harm to your phone, however, if for any reason things go awry when doing any kind of update or modification to your phone the authors of these tutorials or thread posts are not responsible. There is always a chance that modifying your phone can cause damage or a loss of features. Proceed at your own risk. I suggest you read the procedure you intend to implement thoroughly and if necessary ask questions before you proceed. Also, installing mods may make it so you cannot receive or install updates from Pantech/AT&T.
Modification Procedure Order
Determine if your device is running Ice Cream Sandwich (ICS) or Jellybean (JB)
Open the Settings app and tap on "About phone"
If the "Android version" is 4.0.4 you are running ICS, if it is 4.1.2 you are running JB
Set up and ensure you have ADB access to the phone
For now you will have to find an ADB installation tutorial elsewhere
Root your device
Follow the tutorial here.
Jellybean (JB) users should revert back to the unlocked (ICS) bootloader to increase the chance of brick recovery
Follow the tutorial here.
Install ClockworkMod Recovery or TWRP
Follow the tutorial here (CWM) or here (TWRP).
(Optional) Install custom ROM(s)
Follow the tutorial here.
Useful links
Pantech Discover Specs
Ultimate Pantech Discover/Magnus/P9090 Rooting & Modding Thread - Not all content is still relevant but a great read
PantechDevTeam Github - The original Pantech devs (a ton of awesome work here)
PantechDiscover Github - Put together by @Unjustified Dev with contributions from @mifl and myself
Pantech Discover Jellybean Kernel Source
Pantech Discover ICS Kernel Source
Thanks to everyone who helped test and provide feedback for these advancements. A big thanks to @Unjustified Dev & @mifl for their continued development help and porting TWRP (Unjustified Dev) and to @ShotSkydiver for creating the original Pantech Discover mod thread.
Root
Rooting the Pantech Discover P9090
WARNING: Please review the Warning/Disclaimer in the original post before following this procedure!
Click "CLICK TO SHOW CONTENT" to proceed.
Users running ICS
Download recovery-magnus.img, su, and SuperSU_1.65.apk and move them to a directory of your choosing hereafter known as <install-directory>
Boot the phone in fastboot (bootloader) mode by holding down both volume buttons and the power button, once the menu appears use the volume buttons to select "fastboot", then hit the power button
Attach your phone to your computer
Open a cmd window (Windows) or terminal/shell (unix flavors) and type the following command (hit enter after each):
Code:
cd <install-directory>
Now boot to the magnus recovery by typing:
Code:
fastboot boot recovery-magnus.img
The phone should be booted to CWM, now type:
Code:
adb push su /sdcard/
adb push SuperSU_1.65.apk /sdcard/
adb shell
You should now be in an adb terminal on the phone, type the following:
Code:
mount /dev/block/mmcblk0p14 /system
cd /sdcard
cp SuperSU_1.65.apk /system/app/
cp su /system/xbin/
chmod 4755 /system/xbin/su
exit
If all goes well you should be back in your computer's terminal, reboot the phone with
Code:
adb reboot
Enjoy!
Users running Jellybean
Download and install the Framaroot app (version 1.6.1 or later) from here.
Install and open the app
Select "Gandalf"
Reboot the phone for good measure
Enjoy!
Bootloader
Reverting to the Unlocked (ICS) Bootloader from the JB Bootloader
WARNING: Please review the Warning/Disclaimer in the original post before following this procedure!
Click "CLICK TO SHOW CONTENT" to proceed.
Context: The Jelly Bean update for the Pantech Discover flashes a locked bootloader over the unlocked Ice Cream Sandwich bootloader. The result is that you can no longer use fastboot to flash images or boot to external bootloaders. If you are on ICS this tutorial does not apply.
You can test to see if you have the locked bootloader by booting into fastboot (power off device, power on devices holding both volume keys, select fastboot), connect the device to your PC, and run the following command from a command terminal.
Code:
fastboot boot recovery-magnus.img
NOTE: If you don't already have the magnus recovery image download it from here.
If your output looks like the message below you have the locked bootloader and this guide applies to you.
Code:
downloading 'boot.img'...
OKAY [ 0.538s]
booting...
FAILED (remote: Not Support !!)
finished. total time: 0.543s
Procedure: If you have the locked bootloader, you would prefer not be locked, and you are willing to take the risk you can follow the procedure below.
Prerequisites
Phone must be rooted
ADB access
Download the ICS bootloader image (aboot.img) from here.
Connect your phone to your PC and from a command window in the download directory type:
Code:
adb push aboot.img /sdcard/
adb shell
If you are connected to your device at this point type:
Code:
su
cd /sdcard
md5sum aboot.img
The output should be:
Code:
7f55c5ab321cf20e595b841371f45cda aboot.img
The MD5 checksum should be the hex number above (beginning in 7f and ending in cda). If it does match download it again and make sure the checksum matches before proceeding. If no matter what you do you can't get a match then don't proceed.
If you are here then you have the ICS bootloader and it's ready to be flashed, before we do this you should check the checksum for the bootloader partition with the command:
Code:
md5sum /dev/block/mmcblk0p5
output:
Code:
8b6fa6881c7f155858243e94490d0a29 /dev/block/mmcblk0p5
If you are on JB the checksum should match mine.
Now you are ready to flash the ICS image. If you are feeling confident and risk adverse run the command below:
Code:
dd if=aboot.img of=/dev/block/mmcblk0p5
You should get the output:
Code:
5120+0 records in
5120+0 records out
2621440 bytes transferred in 0.458 secs (5723668 bytes/sec)
Don't be concerned if the transfer time is not precise.
Now confirm that our checksum is updated to the new image:
Code:
md5sum /dev/block/mmcblk0p5
Code:
7f55c5ab321cf20e595b841371f45cda /dev/block/mmcblk0p5
If not follow the bail out procedure outlined after this procedure, otherwise get back to your PC command window with:
Code:
exit
exit
Reboot into the ICS bootloader with:
Code:
adb reboot bootloader
Once you are in fastboot verify it worked with:
Code:
fastboot boot recovery-magnus.img
You should be rewarded with the following output:
Code:
downloading 'boot.img'...
OKAY [ 0.544s]
booting...
OKAY [ 0.020s]
finished. total time: 0.565s
You are done!!!!!
Invalid checksum: If the checksum you show does not match the checksum above you can reflash the JB bootloader and if all goes well you will be back where you started.
Download the JB bootloader (jb-aboot.img) from here.
Follow the procedure above to push the bootloader to the device and validate that the checksum matches the original JB checksum you copied on step above.
Flash the JB bootloader as per the guide above replacing aboot.img with jb-aboot.img.
If you have problems I strongly suggest you refrain from rebooting your phone and ask for help.
CWM
Installing ClockworkMod 6.0.2.8 on your Pantech Discover
WARNING: Please review the Warning/Disclaimer in the original post before following this procedure!
Click "CLICK TO SHOW CONTENT" to proceed.
Prerequisites
You must have adb and fastboot installed and working on your computer. There are literally hundreds of tutorials on this so I won't go into it here.
Your phone must be rooted
Optional but recommended
If you are on Jellybean and you haven't already done so I recommend reverting to the unlocked (ICS) booloader. An unlocked bootloader will increase the ability to restore a "brick" substantially.
Ready, set, go!
Option 1 (Do this if you have the unlocked ICS bootloader this is much faster)
Download update_magnus_clockworkmod-6.0.2.8.zip and recovery-magnus.img and move them to a directory of your choosing hereafter known as <install-directory>
Turn off the phone, copy update_magnus_clockworkmod-6.0.2.8.zip to a micro sdcard and install it in the phone
Boot the phone in fastboot (bootloader) mode by holding down both volume buttons and power, once the menu appears use the volume keys to select fastboot, then hit power
Attach your phone to your computer
Open a cmd window (Windows) or terminal/shell (unix flavors) and type the following command (hit enter after each):
Code:
cd <install-directory>
Now boot to the magnus recovery by typing:
Code:
fastboot boot recovery-magnus.img
The phone should be booted to CWM, now select the menu options:
install zip from sdcard > choose zip from external sdcard
Select update_magnus_clockworkmod-6.0.2.8.zip then hit power and confirm by choosing
Yes - Install update_magnus_clockworkmod-6.0.2.8.zip
Once the install is finished choose
Go Back > reboot system now
Enjoy!
Option 2 (Do this if you have the locked Jellybean bootloader and do not wish to revert it):
Attach your phone to your computer and make sure it is booted to Android
Download recovery-magnus.img and move it to a directory of your choosing hereafter known as <install-directory>
Open a cmd window (Windows) or terminal/shell (unix flavors) and type the following command (hit enter after each):
Code:
cd <install-directory>
adb push recovery-magnus.img /sdcard/
adb shell
In the adb terminal type:
Code:
cd /sdcard
ls
Verify that the recovery-magnus.img file is there and if so type:
Code:
su
mount -o rw,remount /system
dd if=recovery-magnus.img of=/dev/block/mmcblk0p20
You should see output indicating that the image was flashed (I'll try to update this with the exact text). If you get an error don't continue and when you reboot to Android the original recovery should be restored. Otherwise type:
Code:
mv /system/recovery_from_boot.p /system/recovery_from_boot.p.bak
exit
exit
You should be back in your computers terminal, type:
Code:
adb reboot recovery
You should be in CWM 6.0.2.8 after a minute or so. The first time you reboot CWM will ask if you want to prevent recovery from being overwritten, go ahead and say yes.
You can use the backup feature to backup your ROM.
What works
Backup/restore from sdcard and external sdcard (including advanced restore)
Delete backup (sdcard and external sdcard)
Choose default backup method
Install zip from sdcard (external)
Wipe cache
Wipe dalvik-cache
Wipe data/factory reset
Mounts - mounting and unmounting partitions
Key test
Show log
Fix permissions (I ran this and it completed and the phone boots but I haven't done exhaustive testing so I don't recommend it, shouldn't need this feature at this point)
What hasn't been tested yet
Install zip from sideload
Format partitions (not recommended)
Partition external sdcard
Report error
Bugs
Backups do not reflect the correct date (common issue that can be resolved eventually)
ROM
Flashing a Custom ROM
WARNING: If you downloaded the ROM that was originally linked to in this guide (magnus-jb-4.1.2-cwm-unlocked_bootloader-rooted-all_partitions.zip) please do not flash it!! While this has worked on most phones the original IMEI on a couple of phones was wiped out.
WARNING 2 (Untested fix uploaded on 11/29, see below) : A couple of users have reported that this update failed on their phones but they were able to restore from a nandroid backup. If you still want to try this ROM please backup your current ROM in CWM first! If you try this please let me know if this works or does not work on your phone and which Android version you were on prior to flashing it. Thanks!
UPDATE 11/29/2013 Newly uploaded file will most likely fix the issues mentioned in warning 2 above, however, I still strongly encourage that you do a backup in CWM before flashing. Please respond with the results indicating which version of Android you flashed this over.
Click "CLICK TO SHOW CONTENT" to proceed.
This guide covers the procedure to flash a specific, JB ROM as discussed below, however, the basic procedure can be used to flash different ROMs as they become available.
Features
Jellybean 4.1.2 stock (other than noted below)
Rooted with /system/xbin/su
SuperSU installed as a system app
Magnus CWM recovery
ICS unlocked bootloader (aboot)
This update is intended to install the unlocked bootloader for all users; provide a restore point going forward; and serve as a basis for future ROMs and enhancements.
This update does not flash the cache or data partitions so your installed apps and data will remain.
WARNING: Please review the Warning/Disclaimer in the original post before following this procedure!
NOTE FOR ICS USERS: The AT&T/Pantech OTA JB Update (from ICS) provides patches to several partitions that are not patched as part of this update. If you are able to run the OTA update I recommend it, if not and you don’t mind having a “hybrid” ROM go for it at your own risk.
Since this flashes the bootloader I strongly recommend checking the MD5 Checksum as per the guide below before executing the update. Make sure the device has enough power, and don't unplug, wiggle, or otherwise mess with the device until the update is complete.
Prerequisites
Magnus CWM installed per the guide above (see OP)
Jellbean or ICS (see notes above before flashing over ICS)
ADB installed and functional
Make sure the battery level of the device is adequate
Flash from the internal sdcard
Download the update from here.
Boot into CWM recovery by holding down the volume up button and power button
Do a CWM nandroid backup
Select "mounts and storage > mount /sdcard > +++++Go Back+++++"
Select "wipe cache partition"
Select "advanced > wipe dalvik cache > +++++Go Back+++++"
OPTIONAL: Select "wipe data/factory reset". WARNING: This will remove your personal apps and data!
Once the download from step 1 is complete, plug the phone into your computer, open a command window, navigate to the download directory, and push the update to the sdcard with:
Code:
adb push magnus-jb-4.1.2-cwm-unlocked_bootloader-rooted2.zip /sdcard/
Check the md5 checksum to ensure you don't have a corrupt download (IMPORTANT!)
Code:
adb shell
cd /sdcard
md5sum magnus-jb-4.1.2-cwm-unlocked_bootloader-rooted2.zip
Should result in:
Code:
3dca0555f81cef97e304c17515c807fa magnus-jb-4.1.2-cwm-unlocked_bootloader-rooted2.zip
If not, download the update and try again. Do not proceed if your checksum doesn't match!
Exit adb shell:
Code:
exit
On the phone, select "install zip from sdcard > choose zip from sdcard", select the update file, and confirm
Wait patiently and do not unplug the device or disrupt the process!
When the update is finished select "+++++Go Back+++++" followed by "reboot system now", if you are prompted to "Fix root" select "Yes" to prevent it from warning again
Wait patiently while it boots, configures the apps, compiles & caches, and connects to your carrier. This can take a few minutes.
Enjoy!
Nice guide. Can't wait till this phone comes if I'm not mistaken cogency sent it again
Sent from my SCH-I535 using Tapatalk
Unjustified Dev said:
Nice guide. Can't wait till this phone comes if I'm not mistaken cogency sent it again
Sent from my SCH-I535 using Tapatalk
Click to expand...
Click to collapse
Thanks! I have been pretty swamped at work so I haven't been able to pull your kernel updates but I am anxious to get back to it. I am glad you have a phone on the way.
Great detailed guide, that provides easy to follow instructions.....nice work, again.
CM11.0
gj23 said:
Great detailed guide, that provides easy to follow instructions.....nice work, again.
Click to expand...
Click to collapse
I predict that on 2 months we will get CM11.0 (kitkat) for the p9090
eeter said:
I predict that on 2 months we will get CM11.0 (kitkat) for the p9090
Click to expand...
Click to collapse
I predict less than one month when my Discover comes in
Sent from my SCH-I535 using Tapatalk
I saw in the Original Thread that Updating to Jellybean on an ICS device doesn't work and he made it work by restoring a nandroid backup and then flashing the rom via CWM.
Any other way to directly upgrade to Jelly bean by flashing the zip via CWM directly without using nandroid backup?
Thanks.
vijayr2002 said:
I saw in the Original Thread that Updating to Jellybean on an ICS device doesn't work and he made it work by restoring a nandroid backup and then flashing the rom via CWM.
Any other way to directly upgrade to Jelly bean by flashing the zip via CWM directly without using nandroid backup?
Thanks.
Click to expand...
Click to collapse
If you are talking about the post below I think you misunderstood. Flashing Jellybean using the guide on the first page of this thread worked for him. He was outlining the history of what he has done on the device and nothing worked other than the magnus-jb-4.1.2-cwm-unlocked_bootloader-rooted.zip update.
If you are on ICS and you have CWM installed the guide in post #5 will get you on Jellybean with all of the goodies.
osopol4r said:
Confirmed working....
> ICS Unable to Update
> Updated to JB with nandroid provided here
> JB nandroid missing browser apk
> Restored from to and from previous ICS
> Installed zip from sd card magnus-jb-4.1.2-cwm-unlocked_bootloader-rooted.zip
> Phone booted correctly, so far so good
I'll report back any issued (if any)
Thanks!!!
Click to expand...
Click to collapse
New subforum in "DevsNest Developments" dedicated to Pantech P9090:
http://www.devsnest.com/forumdisplay.php?fid=142
We hope you include some content in it.
Greetings.
sandnap said:
If you are talking about the post below I think you misunderstood. Flashing Jellybean using the guide on the first page of this thread worked for him. He was outlining the history of what he has done on the device and nothing worked other than the magnus-jb-4.1.2-cwm-unlocked_bootloader-rooted.zip update.
If you are on ICS and you have CWM installed the guide in post #5 will get you on Jellybean with all of the goodies.
Click to expand...
Click to collapse
Great! I somehow misunderstood it. I will update after i install. Thank you for your time spent in contributing for Pantech Discover. Kudos!
vijayr2002 said:
Great! I somehow misunderstood it. I will update after i install. Thank you for your time spent in contributing for Pantech Discover. Kudos!
Click to expand...
Click to collapse
If u install the JB 4.1.2 from here that's rooted and CWM you won't need to update as u will be on Jellybean.
was having wifi issues and bluetooth issues and was ics/jb mix . everything flashed fine and updated fine. will post back after further testing but all seems to be working and volume seems a bit better now.
greg97526 said:
was having wifi issues and bluetooth issues and was ics/jb mix . everything flashed fine and updated fine. will post back after further testing but all seems to be working and volume seems a bit better now.
Click to expand...
Click to collapse
Glad to hear it! I have been waiting to hear from you. I am interested to know if this improves your wifi/bluetooth issues.
sandnap said:
Glad to hear it! I have been waiting to hear from you. I am interested to know if this improves your wifi/bluetooth issues.
Click to expand...
Click to collapse
Blue tooth works flawlessly. Still a bit lagging on wifi. Maybe I need to remove the files we added that didn't match up with what you had or did this update erase all of that?
greg97526 said:
Blue tooth works flawlessly. Still a bit lagging on wifi. Maybe I need to remove the files we added that didn't match up with what you had or did this update erase all of that?
Click to expand...
Click to collapse
This update completely wipes /system then copies over all of the stock Jellybean files so there are no remnants of our hand-crafted /system left. The update also flashes all of the Jellybean partitions that were patched as part of the OTA update so your device should now be consistent with those of everyone who has executed this update with the exception of your /data and /sdcard. You could try backing up your applications and doing a factory reset in CWM.
How about that!
Hi there!
I don't know if you remember me from the old post but...
I just realized my IMEI changed, I used to have my pantech discover unlocked (network unlock) and I believe after flashing the Jelly Bean update file some how relocked itself plus the IMEI also changed. I purchased the unlock code and I just compared the IMEI and it is not the same, plus the phone is now network locked.
I'll try my original nandroid backup and see what happens.