• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root [OUDHS] Clockworkmod Recovery 1.0.3.4

Shabby, i was messing with set cpu when rooted and i not knowingly clicked set on boot so now im in a boot loop. I wish i would installed the recovery but i didnt even check if there was one. i cant acces adb either alls it says when im in the command prompt is error device not found. The found new hardware brings up MPT and thats all. Is there any other solution????
:confused:
 
metrohackz said:
Shabby, i was messing with set cpu when rooted and i not knowingly clicked set on boot so now im in a boot loop. I wish i would installed the recovery but i didnt even check if there was one. i cant acces adb either alls it says when im in the command prompt is error device not found. The found new hardware brings up MPT and thats all. Is there any other solution????
:confused:
Click to expand...

you dindt install oudhs recovery? but you still have stock? boot into it using the vol keys and power and do a factory reset. its the only way to clear that data out im afraid :/
 
Shabbypenguin said:
you dindt install oudhs recovery? but you still have stock? boot into it using the vol keys and power and do a factory reset. its the only way to clear that data out im afraid :/
Click to expand...

i did that and im still looping i get stuck on metro screen and when i go to perform adb process it finds no devices but there is a found new hardware .indicator saying MPT could this driver help during adb.
 
metrohackz said:
i did that and im still looping i get stuck on metro screen and when i go to perform adb process it finds no devices but there is a found new hardware .indicator saying MPT could this driver help during adb.
Click to expand...

no mtp is for file transfer. if a factory reset didnt fix you then you did something more than just mess with setcpu's settings.
 
hmmm i did uninstall bloatware and shit i coulda did something there....... is there any way i could use my friends premia and use the recovery u made to make a backup and fix it or am i screwed
 
metrohackz said:
hmmm i did uninstall bloatware and shit i coulda did something there....... is there any way i could use my friends premia and use the recovery u made to make a backup and fix it or am i screwed
Click to expand...
i thought you didnt have cwm installed?
rdrain1994 said:
I cant get the new link to work Shabby. The box always goes away in the middle of running the script.
Click to expand...

whats teh last thing it says?
 
It says trying to see if your device is connected then two more lines come up after that starting with good news but then the rest I can't see it's too fast when it goes away
 
Windows XP Professional

Script runs, but at the point where it verifies root, I get this error message

Code: 
| not expected at this time

. Also if you open up run.bat in notepad, CRLF are not there... Curious.
Ubuntu Linux 12.04.2 KDE (Kubuntu)

Script gets further along than the windows script, but there is a typo in ./run-linux.sh, adb-linux is the binary it looks for. ./adb.linux is the name of the actual binary.

ADB reports that
Code: 
 --o is not a valid prefix
/data//....blah blah Unknown ID
Reboots into stock recovery at the end.
 
Hey shabby good work, but its not working for me, I'm on Windows 8 64-bit. I did a factory reset rerooted the device using your motochopper file and it worked like a charm. I updated SU via Play Store, and installed Busybox via play store. then tried to run your OUDHS-Recovery-Installer-Premia-4G-1.0.3.4-1 recovery script and it fails. All I can make out before the cmd window closes is good news...

Now to install it manually can I use your adb binary with command prompt and use the following commands:

push "recovery.img /data/local/tmp/recovery.img"
shell "su -c 'busybox dd if=/data/local/tmp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery'"
shell "su -c mount -o remount,rw system /system"
shell "su -c rm /data/local/tmp/recovery.img"

or is there an easier way?


EDIT:
I used the commands listed above and then used adb.exe reboot recovery, and I booted directly into your CWM. I'm backing up now...Thanks alot Shabby and the crew at OUDHS
 
If you would like to see the final output of the script, open a command prompt and elevate it. What I see is a pipe character then an error message I will be looking into this in case it has not already been addressed.

Manual install is the way to go right now I guesss..
 
Tried the new script and it keeps saying my phone isn't rooted like 5 times then at the end it says i need to extract the whole zip before the tool can be used
 
I removed the root check and it works fine. In recovery now. Thanks anway shab :)

I wouldn't recommend a newbie do that...if you're not rooted IDK what will happen.
 
This is my run.bat


DON'T DO THIS UNLESS YOU HAVE DOWNLOADED ROOT CHECKER AND SURE THAT YOUR DEVICE IS ROOTED. I DON'T KNOW WHAT COULD HAPPEN (PROBABLY JUST A PERMISSION DENIED)


Its a temp fix


I'm running Superuser and BusyBox on there as well with updated binaries.


Code: 
@echo off cd "%~dp0"
IF NOT EXIST recovery.img goto :Missing


echo 
[*] OUDHS Recovery Install Script
echo 
[*] Premia 4G
echo 
[*] by Shabbypenguin
echo 
[*]
echo 
[*] Press enter...
pause
adb kill-server
adb start-server
goto :Loop


:Loop
echo 
[*] Trying to check if your device is connected.
@ping 127.0.0.1 -n 4 -w 1000 > nul
set /A i=i+1
IF %i%==5 GOTO :Sorry
FOR /F "tokens=*" %%i in ('adb get-state') do SET STATE=%%i
IF "%STATE%" NEQ "device" goto :Loop
echo 
[*] Good news it was found, now lets check root.
GOTO :Rooted
goto :Failed


:Failed
echo 
[*] Root wasnt detected, are you rooted? did you grant permissions on superuser?
goto :Loop


:Rooted
adb push recovery.img /data/local/tmp/recovery.img
adb shell "su -c 'busybox dd if=/data/local/tmp/recovery.img of=/dev/block/platform/msm_sdcc.1/by-name/recovery'"
adb shell "su -c 'mount -o remount,rw system /system'"
adb shell "su -c rm /system/etc/install-recovery.sh 2> /dev/null" 
echo 
[*] Script complete!
echo 
[*] Rebooting to recovery
adb reboot recovery
echo 
[*] Press any key to exit.
pause
adb kill-server
goto :eof


:Sorry
echo 
[*] I'm sorry this script doesnt appear to be working.
echo 
[*] make sure your device can be found,
echo 
[*] if it can then check for root related issues.


:Missing
echo 
[*] You need to extract the whole zip in order to use this tool.
pause
goto :eof
 
Is everyone's backup date 1970(or something like that)? Not that I mind, just something I thought was odd.

Once again a big thanks to shabby and the OUDHS crew for this recovery
 
jtintle said:
Is everyone's backup date 1970(or something like that)? Not that I mind, just something I thought was odd.

Once again a big thanks to shabby and the OUDHS crew for this recovery
Click to expand...

its due to the time daemon being messed up in recovery broke in ics. no way to fix it, however you can use nandroid manager from the play store.

latest script has been uploaded. dont see how it was working then wasnt idk.. idc anymore. this will be my final upload of modifying the script
 
Backup and Restore to/from SDCard works. 1970 as well...heh.

Works shab. Just tested the script IDK why it would get hung up on the root check. Very curious. Oh well no complaints it woiks!



Special thanks for your effort Shabbypengiun and all those who helped bring this recovery to us.
 
Just discovered a bug that is kind of hard to notice. When making a backup I get an error

E: invalid argument

When first starting the backup to external SD

But the backup completed with no problems. Something probably cosmetic that I am not aware of. I'm one of those ocd people that it really gets my goat to see error messages of any kind lol
 
mind pulling recovery.log from /tmp/ ?

or after youve booted it can be found in /cache/last_recovery

im seriously wondering how this phone even works halfway right with all the software crap they put it through
 
You must log in or register to reply here.
Back
Top Bottom