Related
I was wondering if it was possible to un-root a G1. I'm honestly having the hardest time with it. I've downgraded to RC29 but when trying to add "RC33: (md5: f24b6c237775147cb4bc42efc2393973)" it doesn't want to add when ... I followed the steps on the step by step of adding it and it always hangs up and wont add when in recovery mode while pressing Alt-S to apply the update.
-Could this be a problem because for some reason while i was putting in the info into Telnet it hung up at the recovery.img portion. Sorry new about moding phones... Cars i know phones i don't
I'm in the LA area if anyone else is and is willing to on there free time show me how i keep screwing up. Thanks
All you gotta do is reflash the DREAIMG.NBH file onto your G1 and it'll update by itself, which means you'll be back to stock.
Edit: Are you by any chance unzipping the file? If you are, you have to leave it unzipped and just rename to update.zip in the SD card.
skiptomylou11 said:
All you gotta do is reflash the DREAIMG.NBH file onto your G1 and it'll update by itself, which means you'll be back to stock.
Edit: Are you by any chance unzipping the file? If you are, you have to leave it unzipped and just rename to update.zip in the SD card.
Click to expand...
Click to collapse
no i'm leaving it update.zip like the set by step said. And how do i refresh it? Im on yahoo messenger by the same name on here if your on this to help me. Thank You
-i rather keep it rooted and not have to revert to tmo's software but 4 hours and i feel like a total moron
Why would you want to unroot your phone? But if you really want to then just flash back to RC29 then wait for the phone to get the OTA updates.
I don't want to unroot but im unable to add 1.5 like i intended on doing. So right now im stuck with rc 29 and not cuppycake like i want. I wanted to re-up back to 33 like it said in the posting i was using as step by step and it wont allow me to update
Questions on Android 1.5 and rooting
Some advice will be appreciated!
I just got my G1 a few days a go I was reading from the Official t-mobile web site that the up-grade for android will be out randomly to customers and their expecting that all of us customers will have it by the end of May
Now should I go thru all the work of rooting my G1 and getting cupcake or just wait for the upgrade?
Is there a difference between the two of them?
In the upgrade to 1.5 I don’t see or read anything about the apps getting install and running from the memory card does anyone about this?
Thanks in advance!
In the upgrade to 1.5 I don’t see or read anything about the apps getting install and running from the memory card does anyone about this?
Thanks in advance!
Click to expand...
Click to collapse
Thats only available to rooted phones.
Now should I go thru all the work of rooting my G1 and getting cupcake or just wait for the upgrade?
Click to expand...
Click to collapse
It all depends... If youre ONLY rooting to get cupcake, I would just say wait. See this link for some reasons why you would want to root and step by step instructions:
http://forum.xda-developers.com/showthread.php?t=442480
You can render your phone useless however while doing this. So BE CAREFUL... Youve been warned!
how to unroot my g1
So I rooted my phone and installed JF1.5 and my SD card is now acting a bit weird, and I want to undo the root and mod so I can go back to factory. How do I do this? Is this even possible now?
Thanks
yes, just flash an original RC33 firmware update... use search next time.
i got ya dude
http://forum.xda-developers.com/showthread.php?t=491350
go there
Interesting root problem
Hey guys, been playing in a cupcake irc channel, while we are all waiting for ota cupcake, helping half a dozen or so people root, and i came across one that i figured i'd post here, and see if anyone has any ideas. Obviously i don't have his phone in hand, so i can't be 100% sure that he isn't flubbing a step, but he seems compitent enough to follow simple instructions. He has a stock g1 pvt board with an 8 gig transcend class 6 sdcard, we have formatted this card many times, we get through the nbh file, installs fine, telnetd steps no problem, put the update.zip on the sd card and boot into the bootlader, and everything goes hey wire, it cant find nor install the update.zip, we have redownloaded different spl's to try, triple verified the files weren't named update.zip.zip. the only odd thing i found about his phone, was in one of the threads on here, people were checking the output of the mount command, and for some reason for his sd card his output is /dev/block/mmcblk0p5 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0711,dmask=0700,codepage=cp437,iocharset=iso8859-1,utf8 0 0 where everyone esles is p0 or p1 i cant quite remember. anyhow any ideas or suggestions would be great and no he does not have another sdcard at the moment for us to get it done with
Thanks in advance
ps this is his output form the boot loader
The top says:
Android system recovery utility
using test keys
e:cant open /cache/recovery/command
then when I hit alt+s
Installing from sdcard...
Finding update package...
E:Cant mount /dev/block/mmcblk0 p1 (or /dev/block/mmcblk0)
(Invalid arguement)
E:Cant mount sdcard:update.zip
installation aborted
should be something simple like editing fstab or mount.conf or useing a symlink right, can anyone help me with the commands searching left and right here over edge is killing me
wat is the whole output of the mount command?
n1gh7m4r3 said:
Hey guys, been playing in a cupcake irc channel, while we are all waiting for ota cupcake, helping half a dozen or so people root, and i came across one that i figured i'd post here, and see if anyone has any ideas. Obviously i don't have his phone in hand, so i can't be 100% sure that he isn't flubbing a step, but he seems compitent enough to follow simple instructions. He has a stock g1 pvt board with an 8 gig transcend class 6 sdcard, we have formatted this card many times, we get through the nbh file, installs fine, telnetd steps no problem, put the update.zip on the sd card and boot into the bootlader, and everything goes hey wire, it cant find nor install the update.zip, we have redownloaded different spl's to try, triple verified the files weren't named update.zip.zip. the only odd thing i found about his phone, was in one of the threads on here, people were checking the output of the mount command, and for some reason for his sd card his output is /dev/block/mmcblk0p5 /sdcard vfat rw,dirsync,nosuid,nodev,noexec,uid=1000,gid=1000,fmask=0711,dmask=0700,codepage=cp437,iocharset=iso8859-1,utf8 0 0 where everyone esles is p0 or p1 i cant quite remember. anyhow any ideas or suggestions would be great and no he does not have another sdcard at the moment for us to get it done with
Thanks in advance
ps this is his output form the boot loader
The top says:
Android system recovery utility
using test keys
e:cant open /cache/recovery/command
then when I hit alt+s
Installing from sdcard...
Finding update package...
E:Cant mount /dev/block/mmcblk0 p1 (or /dev/block/mmcblk0)
(Invalid arguement)
E:Cant mount sdcard:update.zip
installation aborted
Click to expand...
Click to collapse
is the phone plugged into computer UsB?
korndub said:
is the phone plugged into computer UsB?
Click to expand...
Click to collapse
hehe no its looking at mmcblk0p1 which doesn't exist
Getting Root on the 1.5 CRB43...The same process as before???
Im so sorry for posting... I can't clearly find any answer.
What is needed, if anything to access root on the G1 with the 1.5US crb43 OTA "cupcake" update.
Thanks in advance!!!
Clay
htcclay said:
Im so sorry for posting... I can't clearly find any answer.
What is needed, if anything to access root on the G1 with the 1.5US crb43 OTA "cupcake" update.
Thanks in advance!!!
Clay
Click to expand...
Click to collapse
Usual steps I would imagine, downgrade to RC29 with DREAMING,,,, ya da ya da ya! follow the link
Dantehman said:
Usual steps I would imagine, downgrade to RC29 with DREAMING,,,, ya da ya da ya! follow the link
Click to expand...
Click to collapse
You are the man!
Thanks for the quick reply!!!
Anyone finds out differently please post.
I'm going to give it a shot...
Clay
I just manually updated my phone to the new cupcake 1.5 US version. I would like to root my phone but don't I have to wait until the modify version comes out? Or can I root right now by downgrading and then manually upgrading to stock cupcake again? Will upgrading with the stock cupcake update wipe out the root?
Goog1e Phone said:
I just manually updated my phone to the new cupcake 1.5 US version. I would like to root my phone but don't I have to wait until the modify version comes out? Or can I root right now by downgrading and then manually upgrading to stock cupcake again? Will upgrading with the stock cupcake update wipe out the root?
Click to expand...
Click to collapse
root now...root later...no difference
If anyone can help me with this issue,its killing me. I love the DARCHDROID rom,couldnt wait anymore so i had to flash it. Flashed darchdroid,lwp kernel and everything else works, minus a few fc's. In adb i have #,and my device appears to be rooted, i have rerooted more then 35 times in the past 5 hours read numerous posts here,even some that would imply to address this issue,but does not solve my problem....seems that i dont have root access to my new 2.1 rom shell.....if this is possible. Ive tried many other roms and never come accross one that you had to re root for.But this rom looked worth it. Everything i have read seems to work for others but not me. Well the geniuses are here so here is where i ask for assistance....any thoughts or replies would be greatly appreciated, im not giving up on this rom yet......thanks in advance!
The newest darch rom is already rooted. Make sure you 'adb remount'. That allows read/write access to /system if you want to push files to it.
oops
BTW, forgot some important info,didnt want to list all of my links and flood the thread Im still at it...anyone that is capable of offering me help will understand this error....when i get to step 9 in the xda guide.forum.xda-developers. cdma hero root guide,.....site wouldnt allow me to use the link,error?strange i couldnt link because all my good links are from this site......after i enter "cat sh > su"
i get "cannot create su: directory nonexistent"......i know this is a red flag for my problem and im sure theres an easy fix......tried makdir and im denied access. ..I now have a headache and thanks for any help.....
reflash the rom. there was no need to asroot2 the shell.
Hi guys, it just came to my mind that test-key signed update.zip files were working back in the eclair days, so i guess the problem is the new recovery in the froyo builds needing Samsung signed files. Same problem was present on the sgs when it moved to froyo, but the devs there managed to change back to old recovery to make them work again, would be nice if someone could find a similar solution for the sg3 also... for more info search for recovery 2e 3e howto in sgs dev section... i am very busy at the moment and go for vacation on Sunday so wont find time to look into this before beginning of March, but eventually someone else could do it and just needed the hint....
Ok, to give this a bump, i need someone with a eclair rom installed and a rooted system. What i need is two files: /sbin/recovery and /sbin/recovery.sh
I think if we swap those files in jpf or whatever Froyo version we could use update.zip files again...
FadeFx
I have JK1 but in sbin directory I have only recovery file, no signs of recovery.sh
sorry, my bad, recovery.sh is part of the modified clockwork mod recovery on sgs custom kernel. also i am in conversation with hardcore about this, and eventually wed have to change the file in initramfs of the kernel... but we will see. to bad i go on vacation tomorrow and will be away for 3 weeks (going to thailand, cant wait to be there...) so i wont have time to complete this, but i will gather info and eventually gsam101 could compile a zimage with old recovery...
Ok, here is my pm conversation with hardcore, seems it can be done easily with loosing new recovery, or the complicated way keeping new recovery for system calls (CSC changes and stuff) and loading old recovery when using 3 button combo. All this is done by recovery.sh
hardcore said:
No u replace /system/bin/recovery in the rom, not kernel.
For kernel if u want to reroute to another recovery u have to use some shell script logic. Check out the initramfs source of my kernel for recovery.sh.
ok, thanx... so we would have to change the file /system/bin/recovery in the zimage´s initramfs to exchange recovery, right?
can we also put the replacement recovery into /sbin to replace the original? and if how is it then called when actually entering recovery mode so we dont enter the old recovery?
thanx Gerd
The recovery executable that comes with the ROM is actually in /system/bin/recovery
Modified kernels like mine have another CWM recovery in the kernel which is in /sbin/recovery which is compiled into the kernel's read-only initramfs.
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Click to expand...
Click to collapse
Content of recovery.sh:
(lagfix stuff is about sztupys lagfix for the sgs and can be ignored for g3 at the moment.
This replaces stock froyo recovery (3e) with clockwork recovery, but same procedure applies to old 2e recovery.
Code:
#!/sbin/busybox sh
/sbin/busybox cp /sbin/fat.format /system/bin/fat.format
# use default recovery from rom if we have an update to process, so things like CSC updates work
# Use CWM if we simply entered recovery mode by hand, to be able to use it's features
if /sbin/busybox [ -f "/cache/recovery/command" ];
then
# if we use the original recovery it might modify the filesystem, so we erase our config, in order to avoid regeneration
# of the filesystems. The drawback is that the lagfix has to be re-applied by hand
/sbin/busybox rm /system/etc/lagfix.conf
/sbin/busybox rm /system/etc/lagfix.conf.old
rm /sdcard
mkdir /sdcard
#/sbin/rec2e &
/system/bin/recovery &
else
# TODO: CWM is a bit more intelligent, but it might fail to
/sbin/recovery &
fi;
Hope someone can make use of this to get update.zip working again...
Nobody looked into this yet? This would make much things easier for us...
Bump
....
realy hope we get some good progress and development on this thread....
sry but im just a noob and flashing is all i do right now
but if i can give any help feel free to ask
Gonna check this out. If I get OCD about this, v1.2 will be delayed.
This could be really useful. For everyone.
Sent from my Lestatious v1.2 Galaxy 3 FROYO
Lestat, i think this is info enough, if not pm me with the questions and ill do my best to find out.
FadeFx said:
Lestat, i think this is info enough, if not pm me with the questions and ill do my best to find out.
Click to expand...
Click to collapse
Alright. Will do chief. Gonna bookmark this thread so I remember tomorrow.
Sent from my Lestatious v1.2 Galaxy 3 FROYO
I have the 2.1 recovery file. . If anyone interested i think i can post if xda allows. ..
Sent from my GT-I5800 using XDA App
I was going to respond, but you responded for me: I tried to make some change to the recovery, basically to make Clockworkmod Recovery work. It seems that in Samsung's phones, the recovery is stored in /system, which is a total nonsense. I managed to get CWN almost work, but it was really buggy.
Gsam101 said:
I was going to respond, but you responded for me: I tried to make some change to the recovery, basically to make Clockworkmod Recovery work. It seems that in Samsung's phones, the recovery is stored in /system, which is a total nonsense. I managed to get CWN almost work, but it was really buggy.
Click to expand...
Click to collapse
How buggy is it?
And i noticed that's where recovery was also. I was like, Hmm. Strange.
The Dark Lestat said:
How buggy is it?
And i noticed that's where recovery was also. I was like, Hmm. Strange.
Click to expand...
Click to collapse
Like i had to flash my phone back to make it work ^^
Did u use the sgs version of cwm or did u do an own port for the g3? I guess the sgs version wont run due to different bml layout
Gsam101 said:
I was going to respond, but you responded for me: I tried to make some change to the recovery, basically to make Clockworkmod Recovery work. It seems that in Samsung's phones, the recovery is stored in /system, which is a total nonsense. I managed to get CWN almost work, but it was really buggy.
Click to expand...
Click to collapse
Hi Gsam101
I interested in compile custom recovery too.
Can You please share build configs for apollo projects?
just wanted to bump this thread, since i think we should now have devs that should be capable of doing such stuff, update.zip support is normally a must have for any android device
is this helpful in any way? -> http://forum.xda-developers.com/showpost.php?p=12244509&postcount=159
No, not yet. Clockwork needs to be ported to our device to run, which i am not able to do. If u can port it i can eventually give some hints...
i have wrote to the developer of ROM Manager APP (Clockwork Recovery) asking him to support our phone. I wrote just because i saw
Don't see your phone? Email me if you want to help me get it working!
Click to expand...
Click to collapse
on his page (http://www.koushikdutta.com/2010/02/clockwork-recovery-image.html)
i'm not good at programming so i think if the developer replies and the answer will be yes then someone like FadeFx or anyone else who can help should contact [email protected] or [email protected]
Hello guys,
in the topics from the search my problem is not solved.I have buy a Wildfire with german Vodafone branding FroYo 2.2. Now i will flash the firmware using unrekoved3. But unrekoved doesn't flash my phone. It stopps by downloading the file and my mobile phone do not make any things. The driver package is installed and my phone is in the right modus to flash it. If i try to install a new Firmware with the RUU and the GoldCard method i become the error 140. I haven't any more Ideas what i can do. Can you help me? Here are many experts and i hope i get good help from you
Greetings
P.S.: Sorry for that bad english
You are probably having the same problem as my friend had.
Wildfire devices with a new Hboot can't be software hacked.. Yap.
But it's possible through some device that mobile shops should have.
Google your Hboot version and find out if rooting is possible for your device.
Hello,
thanks for your answer. I have read that my HBOOT Version can be rooted and on another thread in the internet I've read that is not possible.
I have tryed to root my Handy with a noob guide from this forum here D) but on the task where i push the m0td (or another thing with that name ^^) to SD Card the cmd says, that my System is read-only . What can I do to ignore this error?
Greetings and thanks for help ^^
I don't have too much experience with that but it probably has to do with mounting your SD.
Try to use these commands from adb before you push the file to SD (hit enter after each line):
adb shell
mount /sdcard
exit
if that won't work, google other solutions for mounting SD. Are you trying to do so in recovery mod? In that case you have "mount SD" option.
wait, you said System..
probably you need to use these commands from adb instead of the previous:
adb shell
su
mount -o rw,remount -t yaffs2 /dev/block/mtdblock3 /system
Sorry, but that don't solve my problem
I think the codes do not make anything. Because i seee the step and no anything else
OK..
You really should post your problem on Wildfire forum. Post your Hboot version as well.
There must be people there that will know the answer. Nobody else answers here, as you see.
Yes i think so. but i dosn't have enough permissions to post in this forum. I must have 10 posts
Yea, I know what you mean. I needed 10 posts for another forum.
Start posting "thanks" on random posts if you must heh.
Ok, then thanks for your help ^^
So I accidentally bricked the new Samsung Stellar and my backups got wiped during the process.
Can anyone find the stock firmware/kernel for the Samsung Stellar?
Much appreciated.
sovereign73811 said:
So I accidentally bricked the new Samsung Stellar and my backups got wiped during the process.
Can anyone find the stock firmware/kernel for the Samsung Stellar?
Much appreciated.
Click to expand...
Click to collapse
mines isnt bricked but im looking for the same thing. Deleted some stuff I shouldnt have and no getting system ui force close. Let me know if you have an luck. Ill do the same
Do you still have the stock recovery? I may be able to get into my old OS if you can get the stock recovery pulled off.
Unfortunately I'm not sure how you will extract the recovery ROM off of your phone...I'll keep looking around.
mcarrion78 said:
mines isnt bricked but im looking for the same thing. Deleted some stuff I shouldnt have and no getting system ui force close. Let me know if you have an luck. Ill do the same
Click to expand...
Click to collapse
I'm curious, have you reinstalled the pesky stock apps to see if the OS crashes would stop? There may be something to that.
Also I possibly can help you get an image but I need a recovery image. If you're still rooted, download this:
http://android.podtwo.com/romdump/
Download Terminal Emulator from the Google Play Store and then follow these instructions:
http://forum.xda-developers.com/showthread.php?t=1771347
If I can get back into my phone by restoring the stock recovery, I may be able to get you an image that works.
Uh...OK...feel free to; it keeps the topic up fresh on the first page! lol.
Anyways I managed to theorize that a recovery is all I need....dang, looks like that's both of us now eh?
Im still rooted. im trying to figure out how to pull the recovery myself to possibly help in building CWM for the phone. I know removing some stock apps is what caysed my force close i just dont know all of the ones i deleted. I didn't think to back any of them up
I've got something up there that should help you pull out the stock recovery as well.
Romdump should work and should not brick anything so please give it a try.
sovereign73811 said:
Also I possibly can help you get an image but I need a recovery image. If you're still rooted, download this:
http://android.podtwo.com/romdump/
Download Terminal Emulator from the Google Play Store and then follow these instructions:
http://forum.xda-developers.com/showthread.php?t=1771347
If I can get back into my phone by restoring the stock recovery, I may be able to get you an image that works.
Click to expand...
Click to collapse
used romdump and this is what i get. it leaves me a text file thats 2.46 know that cant be it
c:\SDK\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # /data/local/romdump
/data/local/romdump
Android ROM dumper v0.82b
(c)2011 Sebastian404
Device : IMM76D.I200VRALG4
Creating required files... cat: can't open '/proc/mtd': No such file or directory
Opening mtd table... Segmentation fault
139|[email protected]:/ #
mcarrion78 said:
used romdump and this is what i get. it leaves me a text file thats 2.46 know that cant be it
c:\SDK\platform-tools>adb shell
[email protected]:/ $ su
su
[email protected]:/ # /data/local/romdump
/data/local/romdump
Android ROM dumper v0.82b
(c)2011 Sebastian404
Device : IMM76D.I200VRALG4
Creating required files... cat: can't open '/proc/mtd': No such file or directory
Opening mtd table... Segmentation fault
139|[email protected]:/ #
Click to expand...
Click to collapse
That's complicated. It looks like you use ADB from your PC. I'm curious, is your phone stable enough to run the Romdump from the phone itself? You will need terminal emulator to do this.
There is also a method that just works for recovery and boot partitions (the ones I and a few others need). Take a look here and scroll down to the heading that says "Alternative Method If The Above Does Not Work:".
http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/
i get the same thing using terminal on my phone
http://www.addictivetips.com/mobile...es-boot-recovery-and-system-partition-images/
Have you looked at this link? It even has an alternate way to use romdump.
I don't know if this has anything to do with what we need for a stock ROM but here's something interesting:
http://androidforums.com/elite-all-things-root/551775-well-lets-get-ball-rolling-11.html
Again to any of you who have a rooted Samsung Stellar, please help us with a Stock ROM image!
heres the verizon stuff you were looking for
https://www.dropbox.com/sh/chkru9gi16k9ar8/G-DHp6SgnD
Thanks, although we already have that and we got a phone fixed for it...too bad not mine.
Hey did you get the message? Here I'll post it again:
OK people: here's a tip I've received from an XDA developer expert:
Quote:
a quick and dirty explanation (need root)
Code:
dd if=/dev/block/mmcblk0p1 of=/sdcard/output.img
this will save the partition mmcblk0p1 to output.img
now, to determine what partitions are
on my device its:
Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name/
but you're scheme and directory structure there might be a little different, so adjust accordingly
Longer Version:
http://www.darkyrom.com/index.php?th...with-adb.8059/
yeah i got that message and i got the output.img just havent uploaded it
What were you able to extract by chance?
If you could find a recovery partition, that would be great.
even in recovery its actually loaded to RAM and not mounted (this allows you to flash to it while in recovery)
do:
Code:
ls -l /dev/block/platform/msm_sdcc.1/by-name
(its msm_sdcc.1 on my device, yours may be different but it should be similar)
Click to expand...
Click to collapse
Another tip to extract and backup the stock recovery.
stock rom
hey so im reading the threads and i wanted to know some kind of update. Did people test out the stock rom yet? Any good news?
Yes, thankfully we've got them working (thanks invisiblek!) and I'll make a further update in a few hours.
Where is the thread for this at?
Has this been dropped all together? I was looking for some stock and/or stock-rooted roms for this thing. Any hope out there?