yashsingh1/xdaforums huggingface dataset:
[Android Software/Hacking General [Developers Only]] LuneBear:
That's true bro. As for me I still trying more things unfortunately I ended bricking my phone got stuck into pantech logo. I did a mistake trying to reroot again but I was very close to do it manually super user was working I could mount the system rw again just I delete build.prop by accident and phone rebooted so I lost ability to boot back. I will get this mainboard of my phone for test purposes with Qualcomm tools QPSTand EFS Professional to try to resurrect it. I bough a new Flex mainboard for 49.99 on ebay kinda good deal for people no has warranty in their phones. Im waiting for it to test if all works well and if I am lucky it will come with 4.0.4 so I will install fast CWM to make things easy.

Something Interesting I found I could use busybox and runs it from /data/local/tmp and get full access of the /system using adb when phone got just half rooted like the error some user are experimenting when they use srsroot (•"Half-Success :-/ ... system partition is read-only, use local.prop trick. Reboot your device and use adb to see if it run as root" I could manually install root binaries and everything was lost when I unrooted the phone and make a factory restore. I discovered in my care several files got missed and corrupted my system like mkdir, chmod (to permanent give permission in files or directories) also mount files. For some reason those got lost from xbin and bin folder. The exploit SRSROOT uses (legolas) not work again because part of the root remains in system like "su binaries" parts from busybox and other stuff. Legolas exploit is not available after ya unroot your phone Im sure mostly because system change to RO before full unroot uninstall.

I have an idea but as I am not a dev maybe cant help much but I will write it anyway maybe someone with full knowledge of it can try it. My idea is to get somehow a fresh Jelly Bean update.zip and start to modify it. First from Recovery... why simple. Im sure is AT&T Fault The <3e> Recovery from JB got lot of restrictions like they removed the ability to flash update or flash from external sd card, No adb function in recovery you can use to use basic commands like push, remount, etc. Update from ADB just let ya use adb sideload that kinda sux cause ya cant do anything apart from update. The idea if to make a custom stock Jelly bean recovery with those options available also try to make an insecure kernel just in case to not get any unwanted restrictions. Second, the locked bootloader. As far as I know people can use fastboot in 4.0.4 just fine In Jelly Bean just remote not supported which mean locked. Somehow we need a custom bootloader like remove these restricitons OTA update installs in our phones. Then we can try to push the update via sideload from people no have CWM or with fastboot update as well from those with 4.0.4. If the update works even the radio will be updated and wifi error will get fixed and everyone will be happy. Just Theory based my researches and test. I cant wait to get my Flex board to test more stuffs. I hope this little info can help somehow.

Im just a rookie with big dreams :silly:
[Android Software/Hacking General [Developers Only]] reyradi:
Thanks for your efforts lunebear
[Android Software/Hacking General [Developers Only]] Enigmavision:
Hello

I've Pantech flex 4.0.4 rooted. As I live outside of USA, O'm not able to get OTA update. Could you tell me what should I do to get JB on my Flex, please?
[Android Software/Hacking General [Developers Only]] luismrosa:
i need help guys i get my pantech flex its brick it get stuck into the att logo it was running jb so i think reflash the jb ota update will fix it any ideas pls help
[Android Software/Hacking General [Developers Only]] randomphace:
is anyone working towards cm10 again?
[Android Software/Hacking General [Developers Only]] donavan01:
I am but I'm still learning how to ( lot of reading ). It may take a while though because I have a 6 week old daughter that is taking up a huge amount of my time. I am currently building my rig to do the port on ... still waiting on the drive cages to come in ... ordered them from ebay god knows when I will see them. If anyone is interested in building it I would suggest getting started by reading the Cyanogen wiki. Sorry about it take so long on my end things have just been crazy lately and I'm getting about 3 hours of sleep a night so there inst much time to develop.
[Android Software/Hacking General [Developers Only]] ajclai08:
I dont have a "Legolas" option in SRSroot on JB. Never attempted to root or unroot the device. Is there any other way to root the device in Jelly Bean?
[Android Software/Hacking General [Developers Only]] LuneBear:
Try the latest Framaroot http://xdaforums.com/showthread.php?t=2130276 download it from here. It has several exploits included. If you not attempted to root it before it means probably at&t patched the rom and it will not work. If this is the case there is nothing you can do for now. I'm still out cause my Flex board still no arrived from China reseller so don't have phone for test.
[Android Software/Hacking General [Developers Only]] ajclai08:
Looks like using the Gandalf exploit worked for me. That thread post did say that method was compatible with Qualcomm devices.
[Android Software/Hacking General [Developers Only]] mikiemc73:
Sweet, this worked, it fixed my "half root" issue.

Download Farmaroot...

Select unroot...

Press Gandalf...

Select SuperSU...

Press Gandalf...

Reboot...

Enjoy your newly rooted device.
[Android Software/Hacking General [Developers Only]] donavan01:
Do we as of yet have a method to go from a rooted 4.0.4 ROM with CWM that failed the update to a JB updated phone?
[Android Software/Hacking General [Developers Only]] mikiemc73:
Has anyone tried using farmaroot to un-root, then try the update?
[Android Software/Hacking General [Developers Only]] ovalracer:
This method also fixed my sudo root. Now rooted again.

Thanks everyone:svetius:
[Android Software/Hacking General [Developers Only]] mikiemc73:
Glad to help
[Android Software/Hacking General [Developers Only]] WonderWoofy:
Farmaroot works!

Though it has already been confirmed above, I just want to say that the Farmaroot/gandalf method worked for me as well.

Though the script posted in the original post did not work at all. I am an Arch Linux user running the 3.12rc2 kernel from Linus' git repo. In case you aren't familiar with Arch Linux, that means I am running incredibly bleeding edge software. In fact, a vast number of the packages provided by the official repos are git (or otherwise development) snapshots. So I'm not sure if the versions of packages might have had anything to do with it. But I tried running it as my regular user (in the adbuser group) as well as with root… and nothing.

Thank god I can use adaway with this phone!
[Android Software/Hacking General [Developers Only]] attn1:
Has anyone tried flashing the ABOOT from the ICS release back to a device flashed with JB? On the Burst, we were able to do that and restore our original bootloader properties. A similar process might be the solution. First guy to try that risks his phone, of course.

Something like (I can't test because my phone won't take the update):

Root

adb push aboot.img /data/local/tmp/

adb shell (root)

cd /data/local/tmp

dd if=aboot.img of=/dev/block/mmcblk0p5

I pulled and zipped the aboot from my ICS Pantech Flex phone.

md5sum /dev/block/platform/msm_sdcc.1/by-name/aboot

3af799fcb04331d5d0a00f0af2ebd229 /dev/block/platform/msm_sdcc.1/by-name/aboot

tells me the md5sum of the aboot partition

md5sum /dev/block/mmcblk0p5

3af799fcb04331d5d0a00f0af2ebd229 /dev/block/mmcblk0p5

tells me that is the aboot partition because the md5's match

md5sum aboot.img

3af799fcb04331d5d0a00f0af2ebd229 aboot.img

tells me the aboot I off pulled matches the partition aboot. It's a good image.

Here's my aboot and a copy of the md5 in a zip file: http://tau.shadowchild.nl/files/flex-aboot.zip

I have no idea how safe this is on Flex, but the same process worked on Burst. Good luck.
[Android Software/Hacking General [Developers Only]] donavan01:
Honestly I think it is actually and issue with Ubuntu more than Arch. When I was redoing Bin4ry's script I ran into a number of issues that should have just worked but didn't and required me to recode some paths in the longer version. If you are skilled with linux I would recommend using Bin4ry's script (one of the older versions). But I think that is even the hard way around things being that there are a number of new tools out there for rooting that weren't available when I originally rooted this little phone.
[Android Software/Hacking General [Developers Only]] WonderWoofy:
Yeah, I started to read through the script, and it all seemed pretty simple. But then I decided to see if there were others with the same problems, and found one of the posts above where someone found a successful solution with gandalf. So I decided to give that a go since it didn't sound terribly risky.

Thanks for leading me in the right direction though. I apperciate it.
[Android Software/Hacking General [Developers Only]] dnyanesh:
Is it just me or the option to move to SD card (External Storage) just vanished from the apps section in the settings?
[Android Software/Hacking General [Developers Only]] donavan01:
It has something to do with how ICS/JB uses storage space. My fiance has a less robust phone and she is always running into the wall when it comes to storage space becasue of the same issue luckily I haven't had that issue with this phone yet.
[Android Software/Hacking General [Developers Only]] dnyanesh:
I had moved a few apps to the external storage recently on the same phone (flex) and when I visited today, the option has simply vanished. I can't find it anywhere.

Also, I didn't install any system updates.
[Android Software/Hacking General [Developers Only]] attn1:
I was able to apply the 4.1 update and test this. It works. Fastboot is back. I was then able to extract and boot the stock JB boot image.

ICS boot images are not compatible. New recovery and custom boot images are needed, but they can be installed the same ways as before after flashing back the older aboot as described above.

For anyone not able to get the JB update.zip from the AT&T OTA, here it is, signed and ready to flash from stock recovery. Note: this will fail if there are missing pieces. You must be on stock ICS.

http://tau.shadowchild.nl/files/flex-jb-update.zip

Here are extracted stock JB aboot, boot and recovery images:

http://tau.shadowchild.nl/files/flex-4.1-stock-aboot-boot-recovery.zip
[Android Software/Hacking General [Developers Only]] mikey199:
Great job mate!
[Android Software/Hacking General [Developers Only]] dnyanesh:
Do I have to root the phone/install a recovery to flash this? or should I simply use the stock recovery to flash the update?

I am on Stock ICS 4.0.4.
[Android Software/Hacking General [Developers Only]] attn1:
You should be able to flash the ICS update from stock recovery using adb sideload.
[Android Software/Hacking General [Developers Only]] dnyanesh:
adb sideload? how do I do that?
[Android Software/Hacking General [Developers Only]] attn1:
Does stock ICS recovery not have that? Surely there is a way to flash update.zips with it.
[Android Software/Hacking General [Developers Only]] attn1:
Here's Clockworkmod for Flex v6.0.3.8 on AT&T OTA update to 4.1.2 Jellybean

md5 b82fd02e1681b6c5f74fd7cf7b3e570e http://tau.shadowchild.nl/files/cwm-flex-6.0.3.8.img (Built from CM10.2)

Install Process:

check md5

Get root (Use GANDALF)

adb push cwm-flex-6.0.3.8.img /data/local/tmp/

adb shell (root)

dd if=/data/local/tmp/cwm-flex-6.0.3.8.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery

sync

reboot recovery

I am not explaining further or supporting this, so please don't PM. If you don't understand, do something else so you don't brick.
[Android Software/Hacking General [Developers Only]] attn1:
Again, here's the aboot that allows "fastboot boot <bootimagename>"

Install Process:

check md5

Get Root (Use GANDALF)

adb push aboot.img /data/local/tmp/

adb shell (root)

cd /data/local/tmp

dd if=aboot.img of=/dev/block/mmcblk0p5

md5 3af799fcb04331d5d0a00f0af2ebd229 http://tau.shadowchild.nl/files/flex-aboot.zip

This works for me after the 4.1.2 OTA. No, I am not explaining further or supporting this, either - PLEASE stop the PMs.
[Android Software/Hacking General [Developers Only]] attn1:
For anyone not able to get the JB update.zip from the AT&T OTA, here it is, signed and ready to flash from stock recovery.

md5: 8b887735615bda7bc294353e59cce928 http://tau.shadowchild.nl/files/flex-jb-update.zip

Note: this will fail if there are missing pieces. YOU MUST BE ON

STOCK ICS

No support expressed, implied or bargained for. Please don't PM. I am a grouchy old man with no patience.
[Android Software/Hacking General [Developers Only]] donavan01:
OK so we can now get from ICS to JB and get Root and CWM for JB but do we have a way to flash stock rom and recovery back to a phone that has CWM and has been rooted? We really need those files or some way of flashing from ICS CWM to JB however that craziness might work.
[Android Software/Hacking General [Developers Only]] attn1:
Process to restore stock, unrooted ICS if you have working but modified ICS:

Make a CWM BACKUP of your current working ROM.

download flex-ics.zip

unzip the contents of flex-ics.zip

make a folder in your sdcard called FLEXICS under /clockworkmod/backup (where your backups should be)

unzip the contents of flex-ics.zip

copy the 4 files (boot.img nandroid.md5 recovery.img system.ext4.tar) to the FLEXICS directory on your sdcard

download flex-ics-stock-recovery.zip and copy that to the root directory of your sdcard

reboot to clockworkmod recovery

wipe data/factory reset

restore from FLEXICS

reboot and verify working stock ICS.

reboot to CWM and install zip flex-ics-stock-recovery.zip.

Congrats - you are on stock ICS.

Note: someone please mirror these files and repost them. I am not leaving them up for more than a couple of weeks.

As usual, follow it or not but don't bug me with PMs.
[Android Software/Hacking General [Developers Only]] reyradi:
[MENTION=2436164]attn1[/MENTION]

Ok man need little help here.

Im on JB using the zippermaster backup method, im rooted too, but have a lot of ramdoms reboots, i want to know if i can do a clean instalation flashing new recovery 6.3.8 and then flashing update.zip signed thanks for your help bro.
[Android Software/Hacking General [Developers Only]] attn1:
No you can't. The update.zip OTA is only for STOCK ICS, not hacked in JB.
[Android Software/Hacking General [Developers Only]] reyradi:
can i roll back to stock in my condition?
[Android Software/Hacking General [Developers Only]] attn1:
If you never flashed the OTA, yes. Instructions are above to go back to stock ICS with stock recovery. Don't forget to do a CWM backup before you begin.
[Android Software/Hacking General [Developers Only]] reyradi:
im on JB but i dont have CWM.
[Android Software/Hacking General [Developers Only]] donavan01:
OK folks Im going to try flashing to JB here after I get all the files downloaded. I need to know what the best/easiest way to get root on JB is. I am going to update the main page once I have a definite working path to JB and root there after. Let me know what you all find the easiest I have seen a number of things mentioned with varying results. Thanks
[Android Software/Hacking General [Developers Only]] donavan01:
If your on JB then you don't need to update ... the update gives you JB.
[Android Software/Hacking General [Developers Only]] reyradi:
Yes im on JB but with hack method and it's horrible a lot of bugs and ramdom reboots.
[Android Software/Hacking General [Developers Only]] attn1:
Hack method tells us nothing about how you got there. What baseband do you have? What hack method?
[Android Software/Hacking General [Developers Only]] attn1:
If you come see me in IRC I can help you. Then you can document, host and support. Homey don't play dat.
[Android Software/Hacking General [Developers Only]] reyradi:
Well i use backup method from cwm ics

Fotmatng data/cache etc....

Then full restore from zaappermaster file backup
[Android Software/Hacking General [Developers Only]] attn1:
Fail. just install ICS CWM, then follow the procedure to restore stock ICS and stock recovery here. From there, you can upgrade.
[Android Software/Hacking General [Developers Only]] reyradi:
How?? i cant use fastboot mode in JB is locked
[Android Software/Hacking General [Developers Only]] donavan01:
What channel/server can I find you on I have run into an issue and can't figure out how to over come it. I flashed the ROM back to stock ICS and tried to boot back into CWM but something went wrong somewhere in the restore process (im thinking it was the factory wipe part of things). It seemed to wipe out my recovery now I get the dead droid icon every time I try to boot into recovery. I tried to root and then re-install CWM from fastboot but for some reason fastboot just sits there looking for my phone. I can still boot the ROM so I'm not dead in the water. Problem is I'm now back to having a rooted ICS (needed it to delete that boot.p file in the systems folder) which I may or may not be able to get rid of and I don't have any sort of bootable recovery. Got any ideas I saw that you had posted instruction for flashing the CWM for JB using ADB I was wondering if there is a way to do the same with the ICS files from this thread http://xdaforums.com/showthread.php?t=2133857 or do I need new/different files because of the difference in method of install.
[Android Software/Hacking General [Developers Only]] attn1:
freenode #burstroot
[Android Software/Hacking General [Developers Only]] attn1:
fastboot boot is locked? So you flashed the whole OTA already? You can't go from JB back to stock ICS once you flash all of the OTA files.

Again, what baseband do you have? Look in about phone to find it. JB is JYUS06032013
[Android Software/Hacking General [Developers Only]] reyradi:
Yes that my baseband
[Android Software/Hacking General [Developers Only]] attn1:
Alright, then no going back to stock ICS for you.
[Android Software/Hacking General [Developers Only]] randomphace:
the problem ive had all along is when i try to update to jb the update fails. After following attn1s directions I am 100 percent stock. Unfortunately the update still fails at 31 percent.
[Android Software/Hacking General [Developers Only]] donavan01:
Same exact issue I am having was working with attn1 via IRC to get around this ... he was going to try to make a CWM version of the update hoping that maybe it would work instead.
[Android Software/Hacking General [Developers Only]] LuneBear:
Easiest way is with SRSroot or updates framaroot I posted before.
[Android Software/Hacking General [Developers Only]] solz6009:
Anyone have any idea how to make a jellybean softbriked phone back to.work.Cause it is stuck at pantech screen with jb kernal or recovery...so no.fastboot commands work.
[Android Software/Hacking General [Developers Only]] donavan01:
Im just guessing here but if you can get to any sort of recovery you may be able to push some working files over to the phone ADB. From there you might be able to get either your phone to boot or CWM installed or something ... Im not sure about the method that attn1 created for getting fastboot/CWM going on the JB phones and what it requires but it might be worth a shot looking into it.
[Android Software/Hacking General [Developers Only]] randomphace:
hopefully he does.
[Android Software/Hacking General [Developers Only]] donavan01:
He said he should have something tomorrow sometime, crossing my fingers
[Android Software/Hacking General [Developers Only]] attn1:
Flex Partition Info

Dev Start End Size FS Name
/dev/block/mmcblk0p1 524kB 67.6MB 67.1MB fat16 /dev/block/platform/msm_sdcc.1/by-name/modem
/dev/block/mmcblk0p2 67.6MB 69.2MB 1573kB /dev/block/platform/msm_sdcc.1/by-name/sbl1
/dev/block/mmcblk0p3 69.2MB 70.8MB 1573kB /dev/block/platform/msm_sdcc.1/by-name/sbl2
/dev/block/mmcblk0p4 70.8MB 72.4MB 1573kB /dev/block/platform/msm_sdcc.1/by-name/sbl3
/dev/block/mmcblk0p5 72.4MB 73.9MB 1573kB /dev/block/platform/msm_sdcc.1/by-name/aboot
/dev/block/mmcblk0p6 73.9MB 75.5MB 1573kB /dev/block/platform/msm_sdcc.1/by-name/rpm
/dev/block/mmcblk0p7 76.0MB 86.5MB 10.5MB /dev/block/platform/msm_sdcc.1/by-name/boot
/dev/block/mmcblk0p8 86.5MB 88.1MB 1573kB /dev/block/platform/msm_sdcc.1/by-name/tz
/dev/block/mmcblk0p9 88.1MB 88.6MB 524kB /dev/block/platform/msm_sdcc.1/by-name/pad
/dev/block/mmcblk0p10 88.6MB 92.8MB 4194kB /dev/block/platform/msm_sdcc.1/by-name/rawdata
/dev/block/mmcblk0p11 92.8MB 95.9MB 3146kB /dev/block/platform/msm_sdcc.1/by-name/modemst1
/dev/block/mmcblk0p12 95.9MB 99.1MB 3146kB /dev/block/platform/msm_sdcc.1/by-name/modemst2
/dev/block/mmcblk0p13 99.6MB 1148MB 1049MB ext4 /dev/block/platform/msm_sdcc.1/by-name/system
/dev/block/mmcblk0p14 1148MB 1149MB 1049kB /dev/block/platform/msm_sdcc.1/by-name/dummy
/dev/block/mmcblk0p15 1150MB 1158MB 8389kB ext4 /dev/block/platform/msm_sdcc.1/by-name/persist
/dev/block/mmcblk0p16 1159MB 1499MB 341MB ext4 /dev/block/platform/msm_sdcc.1/by-name/cache
/dev/block/mmcblk0p17 1499MB 1768MB 268MB /dev/block/platform/msm_sdcc.1/by-name/tombstones
/dev/block/mmcblk0p18 1768MB 1769MB 1049kB /dev/block/platform/msm_sdcc.1/by-name/misc
/dev/block/mmcblk0p19 1769MB 1780MB 10.5MB /dev/block/platform/msm_sdcc.1/by-name/recovery
/dev/block/mmcblk0p20 1780MB 1784MB 3146kB /dev/block/platform/msm_sdcc.1/by-name/fsg
/dev/block/mmcblk0p21 1784MB 1784MB 524kB /dev/block/platform/msm_sdcc.1/by-name/ssd
/dev/block/mmcblk0p22 1784MB 1805MB 21.0MB fat16 /dev/block/platform/msm_sdcc.1/by-name/log
/dev/block/mmcblk0p23 1805MB 1858MB 52.4MB /dev/block/platform/msm_sdcc.1/by-name/fota
/dev/block/mmcblk0p24 1858MB 7813MB 5955MB ext4 /dev/block/platform/msm_sdcc.1/by-name/userdata
/dev/block/mmcblk0p25 7813MB 7818MB 5226kB /dev/block/platform/msm_sdcc.1/by-name/grow
[Android Software/Hacking General [Developers Only]] attn1:
Procedure if you ARE NOT running baseband JYUS06032013 (ICS Basebands) :

boot ICS CWM

flash FLEX-JB-JYUS06032013-FIRMWARE.zip from CWM

format system in CWM (will NOT wipe data, but makes sure old rom does not flash back stock recovery)

restart start recovery/adb reboot recovery (JB CWM is installed - do not try to fastboot boot ICS CWM)

flash FLEX-JB-JYUS06032013-ROM.zip from CWM.

reboot

Procedure if you ARE running baseband JYUS06032013 (JB Baseband) :

get root (Instructions HERE - use GANDALF)

install CWM (Instructions HERE)

flash FLEX-JB-JYUS06032013-FIRMWARE.zip from CWM

format system in CWM (will NOT wipe data, but makes sure old rom does not flash back stock recovery)

reboot to CWM

flash FLEX-JB-JYUS06032013-ROM.zip from CWM.

reboot

This ROM is Pantech stock stock stock with no mods other than CWM installation protection and all stock permissions and symlinks carefully maintained and consistent with the product of a successful OTA. It runs well with nothing broken. You MUST be on JB firmware (below) to run it properly.

The firmware is also stock, with the exception of the open aboot allowing fastboot boot <bootimage>, and installation of JB CWM with nothing else added or changed.

You can let the new CWM root it if you like when you exit - it will prompt you.

Downloads:

md5: 1a0ca5f177bce2f4c428931616e0ecd1 FLEX-JB-JYUS06032013-FIRMWARE.zip

md5: 17c0e611ab6dfbca230571c1e40f3d14 FLEX-JB-JYUS06032013-ROM.zip

[B]GPL INFO[/B]
The kernel used in the ROM is the unaltered, stock rom
and boot image provided by the Pantech OTA.

The kernel used in CWM provided I built from unaltered
Pantech provided source code.

The source code for both kernels can be obtained on the
[URL="http://opensource.pantech.com/"]Pantech Open Source[/URL] website.
[Android Software/Hacking General [Developers Only]] mikey199:
Great job attn1. You are awesome bud. Wish we had a guy like you for the lenovo k900.

Sent from my

Non-chinese Lenovo K900.
[Android Software/Hacking General [Developers Only]] attn1:
get it done?