yashsingh1/xdaforums huggingface dataset:
[Asus Transformer TF700] florck:
Thank you elfaure, but I'm not really sure understanding.

I had a fully functional CM10.0 on my tablet. Then I used CWM to flash the newer boot loader and reboot.

Once I was in the system, through parameter, i requested an update of CM to 10.1 nightly.

It rebooted my tablet, and then, entered the CWM, but with the error messages I printed above.

Now, if I try a hard stop (power + volume up) and then a cold boot (power + volume down) then it doens't propose me the options, but directly goes to CWM. And in CWM, I can't move up and down in the menu, neither with my volume keys nor my finger. The only I can do is use power to reboot and then it come again and again to that broken cwm... Please tell me I don't need to return the tablet...
[Asus Transformer TF700] elfaure:
Please take what I say here with a grain of salt as I have no experience with custom ROMs or custom recoveries. But your one saving grace I think would be if you left ADB enabled on your device and have already upgraded your SDK for privileged ADB connections [required for 4.2 only] (if not then you can still do this from the PC end).

If you can get into ADB then I would think you can fix it. If not, then I think you are bricked. From ADB you can push a new ROM or recovery.

http://xdaforums.com/showthread.php?t=1667929

http://blog.twimager.com
[Asus Transformer TF700] florck:
It seems I can't connect ADB as ClockWorkMod is running. But... I can't get anything else running...

I arrived to control with the physical keyboard the CWM, but can't do anything, since neither external nor internal sdcard is recognized...
[Asus Transformer TF700] _that:
At least with TWRP, a connection via adb shell is possible - either on Linux, or on Windows using the correct driver. I don't know about CWM though.
[Asus Transformer TF700] florck:
Unfortunately, i don't have twrp... I can't see the solution here... :crying:
[Asus Transformer TF700] _that:
Why doesn't adb work? Can you see any USB device on your computer?
[Asus Transformer TF700] florck:
Oh ! I got and ADB shell.

but when I "ls /dev/block", I only get

loop0

loop1

loop2

loop3

loop4

loop5

loop6

loop7

mmcblk0

mmcblk0p1

mmcblk0p3

platform

Am not I missing some mmcblk0pX?

What should I do ? How can I flash recovery if no mmcblk0p4?
[Asus Transformer TF700] _that:
This looks like a hard brick. But I have one more idea that you can try:

Download this file and unzip it: View attachment 1985914

Then push it to your device:

adb push bootit.ko /

and run insmod on it:

adb shell
insmod /bootit.ko

If you are very lucky, your tablet should instantly reboot into Android.
[Asus Transformer TF700] florck:
Thank you a lot, but i was not very lucky.

It rebooted to the cwm once again.

I wanted also to share that strange point : my adb device name is 0123456789ABCDEF ...

Other ideas ? Way to try flashing a full system?
[Asus Transformer TF700] _that:
The funny serial number is normal for the recovery.

Try the procedure again and hold down volume-left immediately after pressing "Enter" in adb shell on the insmod command. Maybe you can get to the bootloader menu. If not, I'll try to build another kernel module.
[Asus Transformer TF700] florck:
That's so kind of you...

even holding the button volume left didn't worked.

I will send to you my jabber through MP if you do aggree to get this easyer. I promise if this works to make the full summary here.
[Asus Transformer TF700] _that:
I don't use Jabber or Google Talk, but I have only one idea left anyway... try this module:

View attachment 1985941

Same procedure as above (unzip, adb push, insmod). It should reboot into the bootloader, from which you can use fastboot if it worked. If not, I declare your tablet finally bricked.
[Asus Transformer TF700] florck:
You're a genius, I can now fastboot and / or cold boot. When I cold boot I have my fully functional previous android. But unfortunately, with flashing with dd on block 4 the cwm, at reboot, i have exactly the same as before...

do you have a link to another bootloader ? or a way to directly flash something else ?

How can I deactivate once booted to android the fact that it boot first to bootloader?
[Asus Transformer TF700] _that:
That's good news - until today your situation was considered an unrecoverable hard brick.

I don't know - I would now flash TWRP 2.5 via fastboot, make a backup, wipe data, and reinstall a ROM.
[Asus Transformer TF700] florck:
Can I just be a very bad student? Can I request references to other pages and to the zip i should flash? I really fear doing another stupid action... :(
[Asus Transformer TF700] _that:
Get the TWRP blob and instructions for fastboot here: http://teamw.in/project/twrp2/105

Here's the official CM thread: http://xdaforums.com/showthread.php?t=1957660

and here is the place to ask questions about it: http://xdaforums.com/showthread.php?t=2249461
[Asus Transformer TF700] florck:
Hum... Unfortunately, this is not finished. When I flash through ADB or flashboot twrp, it changes nothing. I even tried a "fastboot boot" and got

C:\adb>fastboot boot recovery-jb-touch.img

creating boot image...

creating boot image - 7542784 bytes

downloading 'boot.img'...

OKAY [ 1.310s]

booting...

FAILED (remote: ()

finished. total time: 1.342s

I'm so frustrated...
[Asus Transformer TF700] florck:
Any other idea ? Something to flash in other blocks?
[Galaxy Tab 2 General] arunmcops:
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.2.2
TARGET_PRODUCT=aokp_p3110
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.5.0-17-generic-x86_64-with-LinuxMint-14-nadia
HOST_BUILD_TYPE=release
BUILD_ID=JDQ39
OUT_DIR=/home/arun/aokp/out
============================================
Checking build tools versions...
grep: /bltsville/gcbv/version.h: No such file or directory
ls: cannot access /bltsville/ticpu/lib/android/libbltsville_*.*.so: No such file or directory
build/core/base_rules.mk:130: *** device/samsung/p3100/power: MODULE.TARGET.SHARED_LIBRARIES.power.piranha already defined by device/samsung/omap4-common/libpower. Stop.

Contents of both files...

OMAP4-Common/libpower

LOCAL_PATH := $(call my-dir)

include $(CLEAR_VARS)

LOCAL_MODULE := power.$(TARGET_BOOTLOADER_BOARD_NAME)
LOCAL_MODULE_PATH := $(TARGET_OUT_SHARED_LIBRARIES)/hw
LOCAL_SRC_FILES := power.c
#LOCAL_SHARED_LIBRARIES := liblog
#LOCAL_MODULE_TAGS := optional

include $(BUILD_SHARED_LIBRARY)

P3100/power

LOCAL_PATH := $(call my-dir)

# HAL module implemenation stored in
# hw/<POWERS_HARDWARE_MODULE_ID>.<ro.hardware>.so
include $(CLEAR_VARS)

LOCAL_MODULE_PATH := $(TARGET_OUT_SHARED_LIBRARIES)/hw
LOCAL_SHARED_LIBRARIES := liblog libcutils
LOCAL_SRC_FILES := power_piranha.c
LOCAL_MODULE := power.piranha
LOCAL_MODULE_TAGS := optional
include $(BUILD_SHARED_LIBRARY)

Solution needed urgently please..
[Verizon Samsung Galaxy S 4] shabbypenguin:
Shabbypenguin and the OUDHS

presents to you

OUDHS Touch CWM-based Recovery 1.0.3.5

for your Verizon Samsung Galaxy S 4

Read this whole post before doing anything :)​

I use nandroid manager to edit/alter my nandroids made by this recovery, you can find the app here : https://play.google.com/store/apps/details?id=com.h3r3t1c.bkrestore&hl=en Enjoy

CWM Flashable - OUDHS CWM-based Recovery 1.0.3.5 (need to already have a recovery for this)

Loki flashable - OUDHS CWM-based Recovery 1.0.3.5

Loki Flashing Utility

Drivers

Directions

:

1) Download the above files

2) using a root file manager remove /system/etc/install-recovery.sh

3) extract the zip

4) use the following adb shell/terminal commands:

adb push recovery.lok /data/local/tmp/
adb push loki_flash /data/local/tmp/
adb shell
su
chmod 755 /data/local/tmp/loki_flash
/data/local/tmp/loki_flash recovery /data/local/tmp/recovery.lok

-------------------------------------------------------------------------------------------------------------------------------------------------

Congrats you now have CWM now.

-------------------------------------------------------------------------------------------------------------------------------------------------

Keep in mind as of 1.0.3.4 it auto loki's kernels for ya, so its even easier to customize your device :) read more here - http://xdaforums.com/showthread.php?p=41803523#post41803523

Source for jfltevzw​

Credits:

Members of the Official Unloved Devices Hit Squad (OUDHS)

for being the best we can for those whom need us

garwynn

for helping with setting up jflte-common stuff

howtomen & RehpotsirhC

for helping test 1.0.3.4's autoloki on teh jflteatt

bhp090808 & an21281 & MR H3LLMAN

for helping test
[Verizon Samsung Galaxy S 4] shabbypenguin:
:eek:
[Verizon Samsung Galaxy S 4] iTechWNC:
So this will work on my s4 verizion correct?
[Verizon Samsung Galaxy S 4] p-slim:
after the install completed i still can't get to cwm recovery. i completed odin, the recovery installed after odin, now im still getting the stock recovery screen
[Verizon Samsung Galaxy S 4] shabbypenguin:
once teh bootloader is unlocked :)

im terribly confused, you installed this recovery? on your verizon sgs4? did you read steps 10 and on?
[Verizon Samsung Galaxy S 4] p-slim:
i did but i read it backwards. i thought i had to let it install. damn im so angry with myself
[Verizon Samsung Galaxy S 4] iTechWNC:
Thanks im a noob once again I have been out of the android seen for two years
[Verizon Samsung Galaxy S 4] slackwaresupport:
already have OUDHS installed. ;)
[Verizon Samsung Galaxy S 4] BladeRunner:
Without an unlocked bootloader? I am confused....

---------- Post added at 10:56 AM ---------- Previous post was at 10:28 AM ----------

Without an unlocked bootloader? Or do you know something we don't?:confused:
[Verizon Samsung Galaxy S 4] p-slim:
So was I, smh
[Verizon Samsung Galaxy S 4] slackwaresupport:
was a tester for Dan. ;)
[Verizon Samsung Galaxy S 4] shabbypenguin:
updated op, enjoy guys :)
[Verizon Samsung Galaxy S 4] slackwaresupport:
nice.. loki was way more easier. ;)
[Verizon Samsung Galaxy S 4] BladeRunner:
install-recovery.sh doesn't seem to be present in /system/etc for me. Any other locations it might be in?
[Verizon Samsung Galaxy S 4] shabbypenguin:
if its not there, then you are good :)

updated op with a bigger text recovery, and zipped up the files to prevent corruptions when downloading :)

have recovery already? just use teh cwm flashable in recovery and youll be set :D
[Verizon Samsung Galaxy S 4] ChrisK15:
Edit: Nevermind, it didn't work the first time but I tried it again and it booted into recovery. Thanks for the hack!

I followed the instructions and it said it successfully flashed the recovery, but when I tried to boot into it, it said it was booting recovery but didn't actually go anywhere. The screen blacked out for a second then rebooted normally. Any ideas? I'm not running the stock kernel, but the one used in one of the other root methods. Do I need to have stock kernel for this to work?
[Verizon Samsung Galaxy S 4] justreboot:
getting Loki aboot version does not match device (plus my adb keeps timing out for some reason and flipping back to usb mode)...
[Verizon Samsung Galaxy S 4] BladeRunner:
I got the same error

I am rooted with the MK kernel, if that matters
[Verizon Samsung Galaxy S 4] BeansTown106:
Good news I guess.. even though in no way this is an unlocked bootloader but it will do the trick for now, any chance b of making twrp cuz cwm sucks lol :P
[Verizon Samsung Galaxy S 4] shabbypenguin:
should be fixed now, sorry

no intentions to port twrp, others will do that id rather port my teams recovery.

if you only guess that this is good news then you shouldnt really be using it
[Verizon Samsung Galaxy S 4] jgrimberg1979:
I am still getting the aboot error.. I think the files and the commands are the exact same as they were earlier. What do you mean by it should be fixed now?
[Verizon Samsung Galaxy S 4] shabbypenguin:
i dont understand, i used the aboot provided by invisiblek, followed teh same steps and att users are working fine...
[Verizon Samsung Galaxy S 4] justreboot:
sorry still getting the error... just as an fyi to make sure i have this right...

1. I have Root

2. I am assuming (as part of the root process) that the original kernel sb put back (which it is on my phone)

3. We need to flash Loki prior to flashing any recovery (either by SD Card, or ADB)...
[Verizon Samsung Galaxy S 4] shabbypenguin:
the recovery gets patched with loki, i give it to you guys and use the loki tool to flash it. something isnt right and idk what is going on.
[Verizon Samsung Galaxy S 4] BusyPooping:
adding this on now... thanks!
[Verizon Samsung Galaxy S 4] BladeRunner:
I used a recovery_loki.img from another thread and it completed without the error, I still don't have a custom recovery though, just the stock android recovery. I think my install recovery.sh is hiding somewhere and I can't find it
[Verizon Samsung Galaxy S 4] shabbypenguin:
loki has a bug, looking into it. for those that dont wish to wiat you can dd it on. i only suggets that for advanced adb users :)
[Verizon Samsung Galaxy S 4] BeansTown106:
it is good news, i guess i should refraise that.. the whole thing was being suggested there was gonna be an unlocked bootloader. and lets face it this isnt unlocked non of the utilitys like mobile odin etc are gonna work with this. not being ungrateful but just stating the obvious truth.. it was advertised that it was gonna be alot different than it is, unlike u i guess i have had the verizon s3, and the verizon note 2 and have seen them both be actually unlocked.
[Verizon Samsung Galaxy S 4] shabbypenguin:
who said this wasnt gunna work with mobile odin? mobile odion doesnt use the download mode protocol, so it will still work just fine, just the images need to be loki'd up. it was never advertised as being an unlock. in fact if memory serves me right dan has only mentioned it being bypassed leading up to today.

and both of those relied on leaked files, there was none for this, just pure awesomness from dan

edit: turns out teh loki flash utilityu works fine on prerelease'd kernel, not MDK. will update as i know more :)
[Verizon Samsung Galaxy S 4] joshw0000:
Wholly $h!t. I just got this phone yesterday. You guys are moving fast! I know what I'm doing tonight. Thanks!

Sent from my SCH-I545 using Xparent Green Tapatalk 2
[Verizon Samsung Galaxy S 4] mikeyinid:
Glad to see a workaround but I'm sure there will be a legit bootloader unlock sooner than later. Shabby do you have the VZW S4?
[Verizon Samsung Galaxy S 4] northmendo:
[MENTION=2614663]shabbypenguin[/MENTION] Can you confirm that you first need to root using this method before applying this workaround.
[Verizon Samsung Galaxy S 4] shabbypenguin:
seems pretty legit to me, other people have recovery, some att people even have cm10 booting...

yes you need root
[Verizon Samsung Galaxy S 4] CZ Eddie:
Awesome, doing a backup of my TouchWiz right now in your recovery on my AT&T Galaxy S4.

:good:

THANKS!
[Verizon Samsung Galaxy S 4] mikeyinid:
A legit workaround. Not an unlock. S3/Note 2 have an unlocked bootloader. Do you think the S4 wont be unlocked?
[Verizon Samsung Galaxy S 4] shabbypenguin:
the s3 had a leak so they got lucky. the note 2 they had time to study the s3 and if memory serves me correctly used almost teh same security so they worked around it. teh s4 was a whole new ball game and unless sextape leaks out another bootloader that is insecured i dont believe so.

although from my understanding he isnt exactly on great terms iwth xda atm :P
[Verizon Samsung Galaxy S 4] mikeyinid:
Too bad we couldn't just use the tmobile S4 bl. Its unlocked oob. Stupid Verizon
[Verizon Samsung Galaxy S 4] prerunnerseth:
Waiting for aboot error fix with stock kernel. don't really want to run the prerelease kernel.
[Verizon Samsung Galaxy S 4] budwizer:
Possibly the Verizon S4 Developer Edition will help the cause?

http://www.samsung.com/us/mobile/cell-phones/SCH-I545ZKDVZW
[Verizon Samsung Galaxy S 4] joshw0000:
Fyi - you can flash TWRP from GooManager with root on stock kernel.

Sent from my SCH-I545 using Xparent Green Tapatalk 2
[Verizon Samsung Galaxy S 4] yyhd:
yes, i can confirm this as i did it too.
[Verizon Samsung Galaxy S 4] GraffitiKnight:
When I tried to flash it I got an error when I rebooted about an insecure recovery and couldn't boot. Had to restore the stock recovery and when reinstall OUDHS.

EDIT: Nevermind it looks like they released an update. It wasn't working on openrecovery-twrp-2.5.0.1-jfltevzw.
[Verizon Samsung Galaxy S 4] joshw0000:
They updated it. I downloaded from GooManager and made a backup in TWRP without any problems.

Sent from my SCH-I545 using Xparent Green Tapatalk 2
[Verizon Samsung Galaxy S 4] mikeyinid:
Lol. I was looking at this along the same lines as 2nd init for locked motos. Way off.
[Verizon Samsung Galaxy S 4] Paulb787:
ok so we can or cant install this now?
[Verizon Samsung Galaxy S 4] nweaver11:
When I follow the script, all goes well until the 5th & 6th lines. A second line, exactly the same comes up after I hit enter each time. If I try to enter recovery, I get a pad lock that says custom recovery but then the phone just boots up. Did I do something out of order? Yes, I am rooted from the method in this forum using Odin.
[Verizon Samsung Galaxy S 4] northmendo:
I keep getting an aboot mismatch. I am trying to make my own with loki but the binary won't work on mac. Installing a linux vm now.
[Verizon Samsung Galaxy S 4] shabbypenguin:
just got back guys, im updating teh file, loki_flash had an update to make it work while i was gone, so everything will be working :)
[Verizon Samsung Galaxy S 4] nweaver11:
Should I redownload the files before trying again?
[Verizon Samsung Galaxy S 4] northmendo:
Are you guys that this has worded for still running the pre- release kernel? This is what I get.

[+] loki_flash v1.1

[-] Loki aboot version does not match device.
[Verizon Samsung Galaxy S 4] shabbypenguin:
yea

when did you download this stuff?
[Verizon Samsung Galaxy S 4] nweaver11:
When we rooted we were not supposed to go back to the regular kernel?
[Verizon Samsung Galaxy S 4] northmendo:
I first downloaded it here. I download the updated loki_flash from djrbliss's github. I'll try the old kernel.

---------- Post added at 03:54 AM ---------- Previous post was at 03:48 AM ----------

Both root threads say to flash back after rooting to avoid a mismatch.
[Verizon Samsung Galaxy S 4] nweaver11:
Thanks. Just wanted to make sure.

Sent from my SCH-I545
[Verizon Samsung Galaxy S 4] abarthle:
Ok I'm slightly confused and just want to be sure about something.

We're to download all the files except the one that says (need to already have a recovery for this) by it?

What's with the post underneath the instructions saying we can't flash this yet?

I've just rooted my phone using the guide by openyoureyes, if I follow the instructions on this guide it will get me CWM correct?

On my old phone I had to boot into CWM, how would that process work on the S4?

Thanks,
[Verizon Samsung Galaxy S 4] Paulb787:
Dumb question maybe?

Which zip do u flash if u have twrp already? the 1st or second from the top?

Also? are we flashing in odin or twrp?
[Verizon Samsung Galaxy S 4] shabbypenguin:
you need loki_flash, the loki flashable recovery. if you need the drivers they are provided :). i posted this before the unlock came out, ill edit in a min. yes once you have root you should be able to use this to get recovery :).

with thte device off press and hold vol up and press the power button, when you see the blue text in the top left corner

the first one, its teh cwm/twrp flashable :)
[Verizon Samsung Galaxy S 4] nweaver11:
Not sure what I am doing wrong. I am still having the same issue.

When booting into CWR, do I have to press anything besides Vol Up + Home?

---------- Post added at 05:50 PM ---------- Previous post was at 05:45 PM ----------

Same error as above. I just downloaded the files.
[Verizon Samsung Galaxy S 4] das7982:
I can confirm this works. Don't follow the instructions in this thread. Use goo manager and install twrp. Stupid easy :thumbup:
[Verizon Samsung Galaxy S 4] nweaver11:
Wow...you were right. That was crazy easy
[Verizon Samsung Galaxy S 4] abarthle:
Yeah why do we even need this method if the touch method with twrp works and boom we have recovery.
[Verizon Samsung Galaxy S 4] shabbypenguin:
i have testers in irc for att, no one for vzw so im kind of flying blind. its one of the reasons why they have 1.0.3.4 which auto loki's kernels so no need for devs to worry about it.
[Verizon Samsung Galaxy S 4] thejondude:
Well I for one would love to have cwr i hate twrp :) Heard your working a on version that will auto loki any rom/kernel ....which would be awesome :)
[Verizon Samsung Galaxy S 4] abarthle:
I apologize, I appreciate your work and everything, I didn't mean to sound ungrateful. I was genuinely confused and wasn't sure if one method was better than the other.
[Verizon Samsung Galaxy S 4] nweaver11:
I prefer CWR and hope you get it fixed but having TWRP is better than nothing. That's all I was saying. This is my first time using TWRP, so it would be nice to go back to what I know and prefer.
[Verizon Samsung Galaxy S 4] twiz0r:
wow look @ op....

smh...
[Verizon Samsung Galaxy S 4] rvrugg90:
Can someone post link to twrp file we should use? Thxxx
[Verizon Samsung Galaxy S 4] brizey:
There is a TWRP thread.
[Verizon Samsung Galaxy S 4] mikeyinid:
it's finest...
[Verizon Samsung Galaxy S 4] shabbypenguin:
1.0.3.4 is posted, recovery flashable is teh only option since many people had issues with using the loki utility and the recovery.

flash the zip in the OP in cwm/twrp and youll be greeted with oudhs recovery on your next recovery bootup. the currently only known bug is aroma is messed up due to the way touch is handled in oudhs.
[Verizon Samsung Galaxy S 4] lortay78:
I use don't use cwm, but I'm very grateful for options, and cwm allowed an awful lot of development and growth for our community. I have a lot of respect for all the developers and teams out there who share this goodness with people like me who don't have the skills they do.

I won't be using this mod, but I'm grateful for the thread. I'm also grateful after several new phones now, that I'm finally able to be patient and let things play out a bit so I can educate myself before I make a mistake and break something.
[Verizon Samsung Galaxy S 4] Pickleweasel:
The link is brokeded :'(
[Verizon Samsung Galaxy S 4] shabbypenguin:
apologies, its up now :)
[Verizon Samsung Galaxy S 4] mikeyinid:
Thank you shabby.
[Verizon Samsung Galaxy S 4] BeansTown106:
is there anyway to fix ur aroma issue? only reason i ask is because i know most roms are gonna use aroma. while they have in the past. and id rather not have to tell people they cant user this recovery to use said rom etc. because of aroma issues with recovery
[Verizon Samsung Galaxy S 4] shabbypenguin:
its because the way i handle touch is via gestures. aroma apparently isnt a fan of it. i havent tried myself as ive never made a rom with aroma
[Verizon Samsung Galaxy S 4] BeansTown106:
aight ill have to give it a flash and see what u mean. dont feel bad aroma dont work with any recoverys right now.. well at least the touch part of aroma doesnt.. :( just made my rom and only way u can select stuff is with volume and power button.. its the same way on the note8 and the htc one so i guess aroma needs to be updated..
[Verizon Samsung Galaxy S 4] kingramon0:
Works great!

I'm not a big fan of the gesturing stuff. Is there any way to turn that off?
[Verizon Samsung Galaxy S 4] XfrostX:
Hold volume up + home + power until phone vibrates. let go of power button but hold volume up + home until you see recovery screen.

Should add that to the 1st post, I couldnt boot into the recovery without ^^. Not the same as the s3.
[Verizon Samsung Galaxy S 4] shabbypenguin:
i have teh correct way to get into recovery :)

i press and hold vol up while it boots up and it works great :)
[Verizon Samsung Galaxy S 4] tkacer:
Seems this recovery doesn't recognize my Samsung 64gb sd card (can't mount / save backups). Do I need to reformat fat32?