Related
I have compiled this guide from the other one posted on this forum, the discussion therein, and my own knowledge. If you have any suggestions on making it better or to correct any mistakes I may have made please let me know.
This guide is intended for Windows and includes detailed instructions. It will cover the steps necessary to root, flash the new recovery image, create a full backup. This will work with software versions 1.29.651.1 and 1.56.651.2 (aka Android 1.5). If you have updated to 2.1 please following this guide here. I am not responsible for any damage done to your phone using this guide. Root at your own risk.
I have put to together a video on YouTube for you to follow along as well. The version numbers of certain files are now outdated in the video so change file names as necessary.
If you own a non-Sprint Hero, you will need to do some extra steps. Follow the guide in the How to Root Non-Sprint CDMA Hero thread.
Step 1: Download the Android SDK from http://developer.android.com/sdk/index.html The Windows file is called android-sdk_r06-windows.zip. Extract the files to your C: drive so that you now have the folder C:\android-sdk-windows
Step 2: Download the asroot2 exploit file from http://forum.xda-developers.com/attachment.php?attachmentid=244212&d=1257621154 Extract asroot2.zip to C:\android-sdk-windows\tools folder.
Step 3: Download the Hero recovery image from http://forum.xda-developers.com/showpost.php?p=4898505&postcount=1g Place this file in C:\android-sdk-windows\tools as well.
Step 4: Make sure USB Debugging is off by going to Settings>Applications>Development. Now connect the phone to your PC via USB cable.
Step 5: Mount your sdcard; Browse to the HTC Sync folder and install HTC Sync on your pc. After it is done installing unmount the sdcard then enable your USB debugging.
Step 6: Open a command prompt by clicking the Start button and typing cmd into the search box and pressing enter or found under All Programs>Accessories.
Step 7: You will now enter a series of commands which I will place inside code boxes to indicate the entire command. You may copy and then paste them into the command prompt window by right clicking. Only enter one command at a time.
1:
Code:
cd C:\android-sdk-windows\tools
2:
Code:
adb devices
If you've been following this guide you will see your phone's serial number. If you get "device not found" error, you either need to make sure you the drivers were properly installed or make sure you enable USB debugging AFTER you connect the USB cable. Continue on once you get the proper phone serial output.
3:
Code:
adb push asroot2 /data/local/
4:
Code:
adb shell
5:
Code:
chmod 0755 /data/local/asroot2
6:
Code:
/data/local/asroot2 /system/bin/sh
You should see an output that says:
$ /data/local/asroot2 /system/bin/sh
[+] Using newer pope_inode_info layout
Opening: /proc/857/fd/3
SUCCESS: Enjoy the shell.
#Now for a few last commands.
7:
Code:
mount -o remount,rw -t yaffs2 /dev/block/mtdblock3 /system
8:
Code:
cd /system/bin
9:
Code:
cat sh > su
10:
Code:
chmod 4755 su
You are now officially rooted. A few more steps and you will have flashed the recovery image.
11:
Code:
exit
12:
Code:
exit
13:
Code:
adb push recovery-RA-heroc-v1.6.2.img /sdcard
Pushing is equivalent of copy the file to the root of your sdcard. By the time you finished reading this it should be done. You'll know its done because the ouput will say something like transferred X bytes in X secs.
14:
Code:
adb shell reboot
This will cause the phone to restart automatically. Wait till it is fully booted to continue.
15:
Code:
adb shell
16:
Code:
su
17:
Code:
cd /sdcard/
18:
Code:
flash_image recovery recovery-RA-heroc-v1.6.2.img
FLASHING TO THE RECOVERY TAKES SEVERAL SECONDS-- BE PATIENT. ENTER THE NEXT COMMAND ONLY AFTER THE COMMAND PROMPT RETURNS TO THE # (ROOT SYMBOL).
19:
Code:
reboot recovery
Step 8: This is the last command; you may now close the cmd prompt. This will cause your phone to boot into recovery mode; it should take no longer than 30 secs. The third option on the list is "- Backup/Restore"; select it. Now, select the first option "- Nand backup". The phone will prompt you to press HOME to confirm which is want you want to do. The backup will begin. You will see the screen say, "Performing backup : .........." When done, the bottom of the screen will say "Backup complete!" and you will be given the menu options again. Go back to the main menu and select reboot system. Rebooting your phone after installing the new recovery image may take several minutes.
Step 9: Once your phone is fully booted, mount the sdcard. You will see a folder called "nandroid"; I highly recommend you copy this to your pc in case you lose your sdcard data or reformat it. Your phone is rooted, 100% backed up, and ready to install a custom rom if you wish!
wow dude,
instructions worked great on Win7
i was able to download the missing usb_drivers by running SDK Setup in C:\android-sdk-windows, and selecting the usb driver from the available packages. I was unable to download the index for the SDK Setup program until I enabled "force http://" in the settings menu.
had to copy over asroot again after i ran SDK Setup (that program deleted it from the directory)
your instructions worked like a charm. total time spent rooting this thing after finding your post: 18 minutes.
(you might want to add a line there in the "mount and copy over the zip file step" to backup the nandroid folder from your SDCard to your comp just as a backup of your stock phone image)
anyway.. cheers!
izanagi said:
wow dude,
i'm about to follow these instructions. thank's for the precise list!
(btw, about to try it on Win7.. may have to change some folder pathing but we'll see)
okay.. typo on the first command in parentheses, and I'm missing the usb_drivers folder (do you have it / can sent it to me) so am unable to install the device in win7.
Click to expand...
Click to collapse
Heh, thanks for the misspell heads up. I did my rooting from Win7 pc; it automatically installed correct drivers for me. To check go to the Control Panel>View devices and printers. You see one device named "Android Phone". Otherwise as far as Ive heard installing HTC Sync installs proper drivers.
izanagi said:
*** edit had to copy over asroot again after i ran SDK Setup (that program deleted it from the directory)
**** edit: all done.. your instructions worked like a charm. total time spent rooting this thing after finding your post: 18 minutes.
(you might want to add a line there in the "mount and copy over the zip file step" to backup the nandroid folder from your SDCard to your comp just as a backup of your stock phone image)
anyway.. cheers!
Click to expand...
Click to collapse
Thank you for taking the time help make my guide better. I'm very glad to know there are little to no hiccups.
When I do step 5, instead of:
5. "/data/local/asroot2 /system/bin/sh"
You should see an output that says:
$ /data/local/asroot2 /system/bin/sh
[+] Using newer pope_inode_info layout
Opening: /proc/857/fd/3
SUCCESS: Enjoy the shell.
#
I get:
[1] Killed /data/local/asroot2 /system/bin/sh
Any suggestions? Should I just be quiet until there is an Eris specific way to do this?
When I do step 5, instead of:
5. "/data/local/asroot2 /system/bin/sh"
You should see an output that says:
$ /data/local/asroot2 /system/bin/sh
[+] Using newer pope_inode_info layout
Opening: /proc/857/fd/3
SUCCESS: Enjoy the shell.
#
I get:
[1] Killed /data/local/asroot2 /system/bin/sh
Any suggestions? Should I just be quiet until there is an Eris specific way to do this?
detox702 said:
When I do step 5, instead of:
5. "/data/local/asroot2 /system/bin/sh"
You should see an output that says:
$ /data/local/asroot2 /system/bin/sh
[+] Using newer pope_inode_info layout
Opening: /proc/857/fd/3
SUCCESS: Enjoy the shell.
#
I get:
[1] Killed /data/local/asroot2 /system/bin/sh
Any suggestions? Should I just be quiet until there is an Eris specific way to do this?
Click to expand...
Click to collapse
This guide is for the CDMA Hero not the Eris!
When I go to apply the rom I get an white screen with skateboarding androids on the bottom and the prompt to erase data yes/no. I press the home key and the Hero reboots without asking to "Apply sdcard:choose zip". This is done from the boot menu. Does the rom load automatically? Did I do something wrong? I got root with no problem. A tip; to make it easier and to avoid spelling mistakes copy and paste the rooting commands from the instructions. Made it go faster too. Thanks in advance.
Never mind. I held down Home and Power at
the same time instead of Home THEN power! ARRGH! Loading up now as I type. Sorry.
ELIMINATED said:
When I go to apply the rom I get an white screen with skateboarding androids on the bottom and the prompt to erase data yes/no.
I press the home key and the Hero reboots without asking to "Apply sdcard:choose zip".This is done from the boot menu.
Does the rom load automatically? Did I do something wrong? I got root with no problem.
A tip; to make it easier and to avoid spelling mistakes copy and paste the rooting commands from the instructions. Made it go faster too. Thanks in advance.
Click to expand...
Click to collapse
yuck... break up your sentences, that's alot of crap to throw on someone all at once... and the bold doesn't help it any.
check to see if you have the custom recovery installed....
-turn off phone
-hold vol down + power
-should search for some stuff then give three options
-press "home" to enter recovery image
do you see "!" and a phone.... does it just hang or do you see a green/yellow menu?
At the end of his post he says he figured it out. He wasn't holding down home key
None of this is working for me at all... I'm not sure what I'm doing wrong, but every time I enter ANY of the commands into the prompt all I get is "cannot find the path specified".
For reference, i have done everything in this guide to the letter, everything is downloaded, unzipped to the correct location, USB drivers installed, etc etc. Not sure what's wrong.
EDIT: I figured it out.. user error, awesome. Worked great, thanks for this!
awesomeindeed said:
None of this is working for me at all... I'm not sure what I'm doing wrong, but every time I enter ANY of the commands into the prompt all I get is "cannot find the path specified".
For reference, i have done everything in this guide to the letter, everything is downloaded, unzipped to the correct location, USB drivers installed, etc etc. Not sure what's wrong.
EDIT: I figured it out.. user error, awesome. Worked great, thanks for this!
Click to expand...
Click to collapse
"cd C:\android-sdk-windows\tools" is actually "cd C:\android-sdk_r3-windows\tools"
is that where you are stuck?
thank you TS. I've been lurking xda for a couple years now when i had the mogul and tp. First time on an android device. Thank you for your time in helping me.
someone buy this man a drink!!!
Invaluable piece of work right here, helped me get it done in no time at all....real clear concise and very helpful....REQUEST THIS BE A STICKY!!!!!
fenske09 said:
"cd C:\android-sdk-windows\tools" is actually "cd C:\android-sdk_r3-windows\tools"
is that where you are stuck?
Click to expand...
Click to collapse
That was the name of the zip file not the extracted folder.
Please help, I followed all of your instructions, I received no errors however I can't boot the recovery image. I checked and it is in the sd card, but every time it just hangs at the HTC logo
I downloaded a terminal emulator and typed su and it gave me # so I assuming I am rooted?!
newtodroid said:
Please help, I followed all of your instructions, I received no errors however I can't boot the recovery image. I checked and it is in the sd card, but every time it just hangs at the HTC logo
I downloaded a terminal emulator and typed su and it gave me # so I assuming I am rooted?!
Click to expand...
Click to collapse
Redownload the recovery image and reflash it. The one you're using probably became corrupt during DL or something.
theresthatguy said:
Redownload the recovery image and reflash it. The one you're using probably became corrupt during DL or something.
Click to expand...
Click to collapse
also make sure you have the heroc version there's a hero and heroC, i messed that up once and had similar results
new ROM
So i loaded the custom ROM, and i followed all the istructions as listed on this guide. When i rebooted my phone, a bunch of my apps started Force Closing on startup.
did i miss something, or do something wrong?
if i reinstall them on the new ROM will they work right?
thanks for any insight
kristaps said:
So i loaded the custom ROM, and i followed all the istructions as listed on this guide. When i rebooted my phone, a bunch of my apps started Force Closing on startup.
did i miss something, or do something wrong?
if i reinstall them on the new ROM will they work right?
thanks for any insight
Click to expand...
Click to collapse
you converted your sd card to fat32,ext2,swap and now the apps are looking for the program on your sd card,
turn off your phone
take out sd card
turn on phone
uninstall app
turn off phone
put in sd card
turn on phone
reinstall app
this should fix you
Ok, So I saw ClockworkMod released a recovery 5.5.0.4 for the Asus Transformer TF101 and decided to try it out(Dumb move on my part I admit). Anyways, now it continually boots into Recovery and will not boot into the AndroidOS at all. I've attempted NVFlash only to find out I have a B80 with a Locked Bootloader, thus I cannot use NVFlash. I've also tried reflashing Roach's Recovery as well as Rogue Recovery to no avail it does not seem to work. I'm pretty much as my whit's end here and was wondering if anyone had any possibility of fixing this or do I have a new paperweight?
Any and all Ideas are welcome I've tried looking through various other forums along with searching widely for some form of a fix but yeah...
Thanks
Same thing just happened to me yesterday. I have tried everything. I have a B90 and i cant get out of CWM Recovery. CWM also won't see my micro sd card.
Any help will be greatly appreciated!
Hi guys!
Just about the same thing happened to me yesterday.
I was getting tired of ICS-reboots and instability, so i rooted my TF101, installed RomManager and flashed CWM 5.5.0.4.
When CWM couldn't see my MicroSD I ended up putting the zips on internal memory and flashed both a full wipe script and Android Revolution HD 3.0.1. This worked fine.
However - when I reboot my Transformer, it always reboots into CWM instead of booting normally. To get it to reboot normally, I do the following:
- Power on and then hold [Vol Down] until there is small white print at the top of the screen
- Wait about 5 seconds
- Press [Vol Up] to perform a "cold boot", which basically boots your Transformer normally
I too would like to know how to stop the default CWM-boot.
Hope this helps!
Regards,
Christian
I am having the exact same problem. Flashed clockworkmod through rom manager, installed he latest android revolution, now it won't boot past clockwork mod. Help?
Nice! Installing now. Will report back. Thanks!
How are you getting on ? I also have this problem :-(
Hi again!
Last night I stayed up late trying to fix this - and guess what...it worked!
It took some searching on XDA and Google to find the solution.
Everything you need to flash a working recovery is in the first post of this thread: http://forum.xda-developers.com/showthread.php?t=1530337
I flashed the following recovery: "CWM-based Recovery v5.5.0.4 roach-tf101-r2" (http://forum.xda-developers.com/showthread.php?t=1213723)
At first the command "adb shell" wouldn't work in Windows command prompt. Found out that the Asus adb-drivers were not installed correctly, so I had to update the drivers manually in Windows (downloaded them from Asus' support-site).
I didn't have to push the recovery to the internal memory, as it was already there from my previous attempts.
Fire away if you have any questions!
Edit: And by the way - afterwards I was able to flash Krakd 1.5.2, which I'm running now. ICS can wait for now - I need it to more stable...
Regards,
Christian
Thanks Christian!
chrizz29 said:
Hi again!
Last night I stayed up late trying to fix this - and guess what...it worked!
Click to expand...
Click to collapse
Thank you for the tip! I'll give it a try- I encountered the exact same issue with CWM, plus an extra present... Wifi will not turn on. Still scratching my head over that one, but it's an issue for another thread.
WiFi Not turning on..
codebluechris said:
Thank you for the tip! I'll give it a try- I encountered the exact same issue with CWM, plus an extra present... Wifi will not turn on. Still scratching my head over that one, but it's an issue for another thread.
Click to expand...
Click to collapse
I had the same issue when restoring form a nandroid backup.
The way I fixed it was by doing the following
***DO A FULL WIPE***
--Flashed Rom--first
--wiped data--second
--Advanced restore/restore data only--
--reboot-- done
Wifi working Again.
Hope the helps..
However still Haaving problems with clockwork mod rebooting tried the above post and nothing .....
I got the same problem after play around with ROMManager, following is how to fix it.
Credit goes to here: http://blog.vegeby.nu/post/20159305108/transformer-always-booting-recovery-solution
As Christian mentioned in post #3, press Vol- with Power to boot into Android normally, then do following in either adb or Terminal app:
Step 0:
Code:
su
(to switch to root mode, the prompt should change to #)
Step 1:
Code:
cat /dev/block/mmcblk0p3
this will print something like following
==========
boot-recovery
x......#4r8$)#*0
==========
(5 to 10 lines garbage text except first line)
Make sure the first line is "boot-recovery", if not, DO NOT CONTINUE.
Step 2:
Then, run following command carefully, make sure it is correct:
Code:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
it should say some thing like 5 bytes write
Step 3: (Optional, you can reboot now, if you are curious, run this step to see/verify the changes we just did)
Then run the cat cmd again:
Code:
cat /dev/block/mmcblk0p3
this will print something like following
==============
boot
recovery
x......#4r8$)#*0
===============
(same garbage text except first line now is only "boot")
Now, a normal reboot should boot to Android by default.
Again, do this at your own risk, if you are not comfortable do this, maybe you can try flash other ROM (like Post #7) see if they overwrite above partition.
Cheers,
xordos
Edit: if the cat cmd cause many garbage chars and even corrupt the display, please try following command to only display first 2 lines:
Code:
cat /dev/block/mmcblk0p3 | head -2
xordos said:
I got the same problem after play around with ROMManager, following is how to fix it.
Credit goes to here: http://blog.vegeby.nu/post/20159305108/transformer-always-booting-recovery-solution
As Christian mentioned in post #3, press Vol- with Power to boot into Android normally, then do following in either adb or Terminal app:
Step 0:
Code:
su
(to switch to root mode, the prompt should change to #)
Step 1:
Code:
cat /dev/block/mmcblk0p3
this will print something like following
==========
boot-recovery
x......#4r8$)#*0
==========
(5 to 10 lines garbage text except first line)
Make sure the first line is "boot-recovery", if not, DO NOT CONTINUE.
Step 2:
Then, run following command carefully, make sure it is correct:
Code:
echo boot | dd of=/dev/block/mmcblk0p3 bs=1 seek=0
it should say some thing like 5 bytes write
Step 3: (Optional, you can reboot now, if you are curious, run this step to see/verify the changes we just did)
Then run the cat cmd again:
Code:
cat /dev/block/mmcblk0p3
this will print something like following
==============
boot
recovery
x......#4r8$)#*0
===============
(same garbage text except first line now is only "boot")
Now, a normal reboot should boot to Android by default.
Again, do this at your own risk, if you are not comfortable do this, maybe you can try flash other ROM (like Post #7) see if they overwrite above partition.
Cheers,
xordos
Click to expand...
Click to collapse
Worked fine for me, thanks!
Still Stuck
I tried the above, no change. Every reboot goes to recovery.
One thing I noticed, when it boots to recovery it always claims to be 5.5.0.4 even though RomManager claims I'm on 5.8.2.1. I tried rolling to 5.8.2.0 and back, even to 5.5.0.4 and back to 5.8.2.1. but every boot goes to recovery and claims to be 5.5.0.4.
Nomadadon said:
I tried the above, no change. Every reboot goes to recovery.
One thing I noticed, when it boots to recovery it always claims to be 5.5.0.4 even though RomManager claims I'm on 5.8.2.1. I tried rolling to 5.8.2.0 and back, even to 5.5.0.4 and back to 5.8.2.1. but every boot goes to recovery and claims to be 5.5.0.4.
Click to expand...
Click to collapse
Have you tried step 3 to verified the result? the first line changed or not?
Asus TF101 problem
I did the cat of the block device and it throws many pages of binary data. I am pretty sure I saw the boot-recovery go by but it crashed my connectbot.
Nomadadon said:
I did the cat of the block device and it throws many pages of binary data. I am pretty sure I saw the boot-recovery go by but it crashed my connectbot.
Click to expand...
Click to collapse
Oh, i see, can you try following command then:
cat /dev/block/mmcblk0p3 | head -2
(I updated my original post too)
If you still see "boot-recovery" in first line, then it means the "dd" cmd is not successful, please make sure you are root (step 0, su is doing this) when you run the dd. Or you can run command "id" and double check.
TF101
Same think couple pages of binary goes blowing by. If I do head -1 I get "boot-recovery" then write:Broken pipe.
---------- Post added at 03:08 AM ---------- Previous post was at 03:02 AM ----------
I just redid the echo | dd part. hte Head -2 showed boot and boot-recovery as it should. I rebooted and booted into recovery 5.4.0.4 again. After the reboot the "boot" is missing from the block head output.
That part concerns me also, according to rom manager I'm on 5.8.something but every time I boot into recovery I'm in the same 5.4.0.4. it's like I have 2 recoveries chained or something.
Nomadadon said:
Same think couple pages of binary goes blowing by. If I do head -1 I get "boot-recovery" then write:Broken pipe.
---------- Post added at 03:08 AM ---------- Previous post was at 03:02 AM ----------
I just redid the echo | dd part. hte Head -2 showed boot and boot-recovery as it should. I rebooted and booted into recovery 5.4.0.4 again. After the reboot the "boot" is missing from the block head output.
That part concerns me also, according to rom manager I'm on 5.8.something but every time I boot into recovery I'm in the same 5.4.0.4. it's like I have 2 recoveries chained or something.
Click to expand...
Click to collapse
OK, yeah, then your setup is weird, looks like some boot code overwrite that block and set it back to boot-recovery. Maybe you can try clean it up by flashing some ROM and/or cwm again?
TF101
I've tried 3 different roms (on Kang right now). Just this morning I went to latest cm9 (no wifi :<) and back to Kang. Same behavior.
xordos,
thank you very much. finally got it fixed after seeing this!
TF101
Is it possible to rebuild/recreate /dev/block/mmcblk0p3 ?
Robert
Since the link about rooting the TF101 in the reference thread is broken, I would like to ask what is the cleanest way to root the TF101. I'm coming from a stock B80* device at the latest OTA update.
I'm working under Linux. I want to root my device, install a custom ROM and Ubuntu as well (for the last part I think this guide http://forum.xda-developers.com/showthread.php?t=1537566 is the one to follow).
So now I need a pointer to the "reference" rooting guide (I've done a bit of search but apart from 1-click tools to be used under Win platforms I couldn't tell what is the latest "manual" procedure.
Another question: I read on the XDA wiki that to install Ubuntu on SBK2 devices Wheelie is needed in order to access the nvflash mode, but in the XDA guide I linked above Wheelie isn't mentioned at all. What am I missing?
What is the "cleanest" way to go through this?
Thank you in advance.
Under Linux, I think the easiest is to use Wolf's method 3 from here: http://forum.xda-developers.com/showthread.php?t=1622628
You will need the adb executable for Linux. I am not sure if it is included, or if you have to get it from the Android SDK tools here: http://dl.google.com/android/android-sdk_r21.1-linux.tgz
You will need a recovery blob saved on the internal memory of your TF101. I would use TWRP recovery, download the TWRP recovery blob here: http://techerrata.com/file/twrp2/tf101/openrecovery-twrp-2.3.2.3-tf101.blob I would rename this to recovery.blob and save it in the /sdcard/ for easy reference.
Also, save this copy of SuperSU that can be flashed through recovery in the /sdcard/: http://forum.xda-developers.com/attachment.php?attachmentid=1210576&d=1342793670
Next, connect your TF101 to your Linux machine via the charger cable. Go to Settings - Developer Options and enable USB Debugging.
Open a terminal window where you can execute adb and type the following:
Code:
adb devices
It should show one device connected. If so, proceed. If not, you will want to wait for a Linux guru to come along and assist.
Next, execute the following commands:
Code:
[B]adb shell[/B]
[email protected]# [B]mv /data/local/tmp /data/local/tmp.bak[/B]
[email protected]#[B] ln -s /dev/block/mmcblk0p4 /data/local/tmp[/B]
[email protected]#[B] exit[/B]
[B]adb reboot[/B]
Once you see the Asus loading screen, you should be able to use ADB again. If you want to wait until it is fully booted, that is fine.
Execute the following:
Code:
[B]adb shell[/B]
[email protected]# [B]dd if=/sdcard/recovery.blob of=/dev/block/mmcblk0p4[/B]
8860+1 records in
8860+1 records out
4536396 bytes transferred in 1.718 secs (2640509 bytes/sec)
[email protected]# [B]exit[/B]
[B]adb reboot[/B]
Note, the numbers for records in and out will vary, but as long as it completes it should be fine.
Upon reboot you should see a progress indicator on the bottom of the Asus screen. This is when it updates the recovery to the custom one you dd'd.
After it boots, you can then boot to recovery by holding the VOL DOWN and POWER button on the tablet (not the keyboard dock) for about 12-15 seconds. When you see the white text, release both and tap VOL UP before the white text disappears.
You should boot to the custom recovery (if you get a dead android, you still have stock recovery)
Once in custom recovery, tap Install and choose the SuperSU flashable located in the /sdcard/. Once that completes, you are rooted.
As far as installing Linux on a SBK2, I am not sure on that one. I have been reluctant to mess with Linux on my TF101.
Here I am, the procedure worked flawlessly. Thank you
Awesome!
Hello,
I have nerve-breaking issue with CWM Recovery wich loads up every time i turn on my tablet. So if i wish to restart or to go to CWM i have to hold volume down button to get to bootloader and then select Android to get back to CWM.
So my first question is how do i resolve this problem with constant booting into CWM Recovery? so it would go to recovery only when i select reboot to recovery option in CWM
My next issue is that i have tried to install Ubuntu Touch for TF101 (from ubuntu touch wiki). And in installation guide it says you have to download cm-10.1-20130404-UNOFFICIAL-tf101.zip, and then quantal-preinstalled-phablet-armhf.zip. The fist zip i got successfully but the second link did not exist, so i checked their repository and found similar zip named saucy-preinstalled-phablet-armhf.zip (i tought it's a newer version) well, then i made data wipe and installed both as stated in guide, i also deleted cache and now when i try to boot my tablet i get to blue spinning CWM logo and it stays there for eternity.
So my second question is how to put some other rom on SD card so i can install another rom? or what i have to do to make Ubuntu Touch work?
My third thing that i noticed (for me it seems wrong) is that with every data wipe it makes new 0/ folder and it keeps everything before wipe in it. I made couple of data wipes and now my data structure looks something like this:
Code:
0/
0/
0/
0/
ASUS/
Alarms/
Albums/
AndroZip/
...other folders (apps and data from stock rom)
Alarms/
Android/
Autodesk/
DCIM/
...other folders (probably from first wipe)
Alarms/
Android/
DCIM/
Downloads/
...other folders (probably from second or third wipe)
legacy/
obb/
obb/
So my third question is if this is the correct data structure because it seems wrong for me? And how to resolve that issue?
My un-educated guess is that all three problems are connected, but my android experience and knowdlege is far to small to have a clue how to begin resolving this twisted problem.
I did some researching and as far it goes with second question i think i have soft-bricked tablet (maybe there is still hope?). So i would like to make it back to original rom or 4.2 jelly bean as i had till now without CWM Recovery issue, if possible of course
(Using ClockworkMod Recovery v5.8.3.4 now, and i think at beginning there was ROM Manager used, i bought used tablet)
Please help, thx
The issues are somewhat intertwined, and run back to using CWM 5.8.X.X
The first thing you MUST do is stop the CWM bootloop or you will not be able to install any other ROM or recovery.
If you can boot to a ROM, run a terminal window with SU permissions. If you cannot boot to a ROM, you will need to run from an ADB Shell from a computer when booted to recovery:
Code:
echo boot | dd of/dev/block/mmcblk0p3 bs=1 seek=0
Then reboot normally and your bootloop to CWM should be fixed.
Next, I HIGHLY HIGHLY recommend upgrading to TWRP 2.3.2.3 or higher. The /0/0/0/0 issue has to do with the new directory structure of Android 4.2 for multi-users. CWM 5.8.X.X cannot handle multi-users properly.
TWRP 2.3.2.3 can be updated using the GooManager app (tap the menu key in the top right and choose Install OpenRecovery Script).
IMO, TWRP is far superior to CWM as it has a file manager and terminal emulator.
I am running SidneyK's TWRP 2.6.3.0. He has a zip that can be flashed from CWM to update, however you have to have the boot loop issue resolved or it will not flash.
Ok, as you said i cannot boot to ROM so i tried with ADB Shell but it says
error: device not found
I have device connected on keyboard dock and cable from dock to pc
Any advices how to reslove that issue? Am i missing some drivers?
In device manager i can see that there is a Transformer device with yellow exclamation. I tried to install drivers from asus webpage but it wont install.
Should i get copy of live linux and try from there?
EDIT:
I got the connection working with ADB Shell but i got this response from code you provided
Code:
~ # echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
5+0 records in
5+0 records out
5 bytes (5B) copied, 0.006079 seconds, 822B/s
Ok now i'm not getting to recovery after restart, but now my tablet is constantly restarting... after Asus eee image there is few secodnds of black screen and then it restarts itself.
Could this be due to my Ubuntu Thouch installation attempt?
Or how can i remove CWM Recovery and install TWRP whitout working ROM on tablet?
boonz said:
Maybe i should type?
Code:
echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
Click to expand...
Click to collapse
Damn, yeah, it should be ...of=dev/block/...
D'OH!
I made few more edits on previous post as i was trying diffrent things. So currently i'm at this position:
Code:
~ # echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
5+0 records in
5+0 records out
5 bytes (5B) copied, 0.006079 seconds, 822B/s
Ok now i'm not getting to recovery after restart, but now my tablet is constantly restarting... after Asus eee logo there is few secodnds of black screen and then it restarts itself.
Could this be due to my Ubuntu Thouch installation attempt or should i push some basic ROM from asus webpage to tablet and replace it with Ubuntu Touch in order to proceed with your instructions?
Or how can i remove CWM Recovery and install TWRP whitout working ROM on tablet?
Thx
boonz said:
I made few more edits on previous post as i was trying diffrent things. So currently i'm at this position:
Code:
~ # echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
echo boot | dd of=dev/block/mmcblk0p3 bs=1 seek=0
5+0 records in
5+0 records out
5 bytes (5B) copied, 0.006079 seconds, 822B/s
Ok now i'm not getting to recovery after restart, but now my tablet is constantly restarting... after Asus eee logo there is few secodnds of black screen and then it restarts itself.
Could this be due to my Ubuntu Thouch installation attempt or should i push some basic ROM from asus webpage to tablet and replace it with Ubuntu Touch in order to proceed with your instructions?
Or how can i remove CWM Recovery and install TWRP whitout working ROM on tablet?
Thx
Click to expand...
Click to collapse
There are a few ways.
You can use ADB to push the TWRP.zip from sidneyk's thread in the dev section, install that from the internal storage.
If you have a TF101 (non 3G) you can use one of my repacked EasyFlasher in APX mode to push TWRP: http://forum.xda-developers.com/showpost.php?p=43986513
Another option is to use the .blob file (extracted from the zip) and use adb to install when in CWM recovery.
Push the blob file to the /sdcard/ (called twrp.blob for this example)
Use adb shell and execute:
Code:
dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4
Then reboot normally (you need to see the progress indicator complete before rebooting to recovery). What I do is just hold the power button for 10 seconds, once the progress bar completes and it flashes black, hold VOL DOWN until you see the RCK message then tap VOL UP to boot to recovery. With any luck you will see TWRP.
Now i downloaded TWRP 2.6 for TF101 from teamw.in page and i got that twrp.blob file.
Then i executed adb push and it says it successfully copied file
But when i check in adb shell it says i cannot go or look into sdcard.
Am i missing some sort of permissions? or would live linux still be better option and using it with su might help?
Or is it ok and i should just run dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4?
Code:
C:\Program Files\Android\sdk\platform-tools>adb push C:\Users\BoonZ\Downloads\twrp.blob sdcard
1322 KB/s (4984908 bytes in 3.682s)
C:\Program Files\Android\sdk\platform-tools>adb shell
~ # cd sdcard
cd sdcard
/sbin/sh: cd: can't cd to sdcard
boonz said:
Now i downloaded TWRP 2.6 for TF101 from teamw.in page and i got that twrp.blob file.
Then i executed adb push and it says it successfully copied file
But when i check in adb shell it says i cannot go or look into sdcard.
Am i missing some sort of permissions? or would live linux still be better option and using it with su might help?
Or is it ok and i should just run dd if=/sdcard/twrp.blob of=/dev/block/mmcblk0p4?
Code:
C:\Program Files\Android\sdk\platform-tools>adb push C:\Users\BoonZ\Downloads\twrp.blob sdcard
1322 KB/s (4984908 bytes in 3.682s)
C:\Program Files\Android\sdk\platform-tools>adb shell
~ # cd sdcard
cd sdcard
/sbin/sh: cd: can't cd to sdcard
Click to expand...
Click to collapse
Try doing cd /sdcard/
If that does not work, you can also just push the twrp.blob to the / directory and push it from there too.
frederuco said:
Try doing cd /sdcard/
If that does not work, you can also just push the twrp.blob to the / directory and push it from there too.
Click to expand...
Click to collapse
Ok superb, i have TWRP it says v2.3.2.3
How do i perform something like format or delete everything (so there will be no 0/0/0/ folders or whatsoever) and make my tablet usefull again. I would like to run jellybean again because i'm pretty used to it and delete that Ubunto Touch mess i made. Maybe little help here, so i don't mess anything up?
Thx
Go to the Wipe section.
Wipe the system, davlik and also the cache.
Choose the FORMAT DATA option to completely wipe the /data/ partition (this deletes everything in the /data/media/ aka /sdcard/ directory)
Then I would reboot back to recovery (suggested after a format data) and then install your ROM, applicable GAPPS and kernel if necessary.
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.