Related
I'm inviting all you guys shoot me down for the noob i am.
I've search and i have found, I've read but only partially understood.
the background:
-Nexus one on vodafone epf30
-Downgraded to erd79 using fastboot (via Terminal in Mac-osx).
-Rotted and installed Amon recovery with sucess.
-At this stage i tried to install a variety of different pre rooted roms
- upgraded to frf91 OTA after giving up on trying to root froyo
I basically just would Froyo 2.2 rooted on nexus one.
I've found a variety of different methods and techs but haven't had any success i can downgrade again and again but each attempt i reach the update.zip stage and simply get a varification failed message.it's likley ive missed something here?!
I'm on mac and I'm sure I'm not having the update.zip.zip issue. ive checked and double checked, (that same issue caught me out before on symbian).
Does anyone dhave a simple deffinitive soloution or can point me in the right direction/
im aware this post will cause a shower of "search you noob SCUM!" style posts.
cheers in advance
http://forum.xda-developers.com/showthread.php?t=712983
Read from:
"By Popular Demand (Credit to lox):
Update.zip to flash with custom recovery"
Download, update using AmonRa's recovery, reboot to bootloader, flash new radio from any Froyo ROM thread in Development, reboot, enjoy.
hi, thanks for your reply. I'm pretty sure i have tried this method. if i down grade to erd79 can i apply this from there or should i go up to ere27 ? and does this require amons recovery or can it be done from a standard recovery?
Sorry im a symbian migrant :-( this is all new and exciting
ok so i down graded again to erd79 then rooted and installed AMONs recovery
installation of update.zip fails with the verification failed, is there something about AMONs custom recovery that im missing should what could be the cause for the verification to fail. im pretty sad now.
maybe there is a way to flash pre rooted Froyo directly using super boot?
maybe i need to be up
You've already installed a custom recovery. Basically you are done the whole rooting process.
No more need to downgrade or anything of the sort. Now you just go into recovery and flash what you want, no other steps.
Now you should be able to flash any custom rom meant for unlocked users.
You may be trying to flash the official 2.2 rom, try looking for a 2.2 for root users. Or try flashing CyanogenMod 6.
Are you sure you have Amon's Recovery because my buddy though he had it and he didnt which is why he couldnt install a rooted froyo ROM. Try http://forum.xda-developers.com/showthread.php?t=702191
ok ill give that rom a shot though i think my main issue could be the fact im using mac os x the downloader in safari automatically unzips .zip files so maybe recompressing the zip is causing the varification to fail.
ill have a go when im home and at a faster net connection work is like 0.2 up and down makes me feel ill!
Oh ok. I have a MAC aswell but I use google chrome for my browser.
OMG! mods lock this down! no need for anything more to be added!
MAC = FAIL
Windows+win
all you have to do is download using anyother browser DONT USE SAFARI!
and success will be yours! rebooting now to pre rooted custom frf91 WOOP!
Hey OP,
Actually you can still use Safari as it does unzip the file automatically but it also downloads the zip file so you end up with both. At least my MAC does this. MAC's are great, Safari on the other hand is junk so don't blame the whole computer for the browsers fault.
Hi,
I have the official (stock) WWW Froyo ROM in my Legend. It was OTA updated two days ago. I only noticed today that the rooted version is now available, and I would like to install it
Is there any way to downgrade the HBOOT?
I tried to downgrade RUU with the goldcard method, but when I try to flash with RUU version 1.31, it says "wrong bootloader version", or something like that.
I mean, I cannot root my phone because I can't downgrade to a rootable RUU, because of the new HBOOT.
Any suggestion?
I have similar problem, I was updating the hboot, now I ended up with f*** official froyo rom, and no root access. Can't even install visionary r14 from modaco, for acheving temp root
qzem said:
I have similar problem, I was updating the hboot, now I ended up with f*** official froyo rom, and no root access. Can't even install visionary r14 from modaco, for acheving temp root
Click to expand...
Click to collapse
If it allows you to go in to recovery mode and then "flash zip", it may work.
Anyway, I don't believe temproot allows you to access the option to flash a zip.
If you are successful, let us know
qzem said:
I have similar problem, I was updating the hboot, now I ended up with f*** official froyo rom, and no root access. Can't even install visionary r14 from modaco, for acheving temp root
Click to expand...
Click to collapse
I read on the official VISIONary thread at MoDaCo that someone is telling Paul that he can only temp-root with r14, but can't perm-root with it anymore.
For now no way to downgrade HBOOT 1.01 to HBOOT 1.00 or 0.43 .....
We wait for a solution ....
You should follow the instrucions from this thread:
http://forum.xda-developers.com/showthread.php?t=845512
It is the same as rooting devices with HBOOT 1.00. And yes you will need to install visionary r13 or r14 from modaco and temproot your phone. I worked for me! I have new HBOOT 1.01 and CM 6.1 rom now. I've spend all afternone playing with my phone, to get it right.
EDIT: when you are doing the last step, you just have to choose some rooted stock rom that you prefer.
qzem said:
You should follow the instrucions from this thread:
http://forum.xda-developers.com/showthread.php?t=845512
It is the same as rooting devices with HBOOT 1.00. And yes you will need to install visionary r13 or r14 from modaco and temproot your phone. I worked for me! I have new HBOOT 1.01 and CM 6.1 rom now. I've spend all afternone playing with my phone, to get it right.
EDIT: when you are doing the last step, you just have to choose some rooted stock rom that you prefer.
Click to expand...
Click to collapse
Well, it does not work for me
At this stage: "Phone will reboot and find LEGEIMG.zip on your sdcard, copy it into RAM and check it." my device just reboots to the HBOOT menu, without any error, no copy and check happens. It just stays there forever waiting for me to choose an option: Fastboot; Recovery; Clear Storage; Simlock.
I think that the suggested tutorial does not contemplate HBOOT 1.01. Are you sure it wasn't your new rooted froyo image that installed you 1.01 HBOOT?
Just to add one more thing.
I am able to gain root access with the temproot trick, but when I ask clockworkmod to reboot in to recovery mode, it just takes me to a big red question mark. After a while it reboots and everything is normal again.
That's perfectly normal...
Sent from my HTC Legend
BlaY0 said:
That's perfectly normal...
Sent from my HTC Legend
Click to expand...
Click to collapse
And, do you think there is a solution?
Yes, qzem already presented you one. But you have another problem... bootloader can't see/find LEGEIMG.zip located on your sdcard. There were guys with exactly the same problem and some managed to solve it so it is documented right here on XDA forums.
Sent from my HTC Legend
Blow me down!! It worked!
I had to repartition, reformat and recreate the memory card as goldcard.
Now I have Stock Rooted Froyo
My path was: stock OTA 2.2 -> 2.1 -> rooted stock 2.2
Thanks
Nice to hear that you solved the problem.
Sent from my HTC Legend
Can someone explain where I am going wrong all I get is image not found or wrong image? I have tried 3 different roms and always get the same thing on the final step in HBOOT
FeaRThiS said:
Can someone explain where I am going wrong all I get is image not found or wrong image? I have tried 3 different roms and always get the same thing on the final step in HBOOT
Click to expand...
Click to collapse
Maybe you should do as I did:
-Delete all the partitions on the SD card;
-Create ONE FAT32 partition;
-Format it;
-Create Goldcard;
-Copy LEGEIMG.zip to the SD card;
Finally, try again.
tonypower said:
Maybe you should do as I did:
-Delete all the partitions on the SD card;
-Create ONE FAT32 partition;
-Format it;
-Create Goldcard;
-Copy LEGEIMG.zip to the SD card;
Finally, try again.
Click to expand...
Click to collapse
Cheers will give it a try now. Any idea why you have to do this if you already have a working goldcard?
That all worked fine and I am now on 2.1 I installed rom manager 2.5.1.2 but when I try to install clockworkmod it does nothing anyone got any ideas?
maybe I should also mention that i dont have superuser.apk but i do have root check in terminal and su is working.
Now that you have 2.1, you need to root your device.
Just follow this tutorial: http://theunlockr.com/2010/06/07/how-to-root-the-htc-legend/
On step 9, use the rooted rom of your preference.\
That is how I did it.
FeaRThiS said:
Cheers will give it a try now. Any idea why you have to do this if you already have a working goldcard?
That all worked fine and I am now on 2.1 I installed rom manager 2.5.1.2 but when I try to install clockworkmod it does nothing anyone got any ideas?
maybe I should also mention that i dont have superuser.apk but i do have root check in terminal and su is working.
Click to expand...
Click to collapse
Instal superuser from Market. Then open Rom Manager, FlashClockworkMod Recovery, then choose Install Rom from SD Card. Before that you should copy some custom rom(all custom roms are rooted usually) you want on the sd card.
tonypower said:
Now that you have 2.1, you need to root your device.
Just follow this tutorial: http://theunlockr.com/2010/06/07/how-to-root-the-htc-legend/
On step 9, use the rooted rom of your preference.\
That is how I did it.
Click to expand...
Click to collapse
Fails on step 1 phone never goes back to the fastbook menu and it shows errors in cmd. Tried this on windows 7 64bit and windows 7 32bit
qzem said:
Instal superuser from Market. Then open Rom Manager, FlashClockworkMod Recovery, then choose Install Rom from SD Card. Before that you should copy some custom rom(all custom roms are rooted usually) you want on the sd card.
Click to expand...
Click to collapse
already tried it superuser just doesnt work never asks to give anything root access got my custom rom on my card ready to go just cant get clockworkmod on the phone
Haha do I feel stupid I had removed one of the zip files jus did a screen shot to find out what the error was in cmd and a .zip was missing re extracted it and I am doing step 1 now will update once I have completed it.
I have finally got it all working I am now the proud owner of a sim free legend with stock 2.2 rooted with clockworkmod recovery. My phones still doesnt like my sim card though lol Cheers guys for all your help. Maybe someone should compile a guide of all of the steps used from other guides?
Nobody's stopping you
Hello people !
Since I'm living in Tokyo, I'm the happy owner of a Galaxy S, but unfortunately it doesn't seem to be exactly the same like the other devices.
Anyway, since 2 days ago, I had some fun (and cold sweat also) trying to root it, unbloat it, etc... Some difficulties and questions left without answers, so if anyone has a guess, please be my guest !
My phone as I got it :
SC-02B, with OMJJ1 firmware (Froyo 2.2)
1) Rooting
The easiest thing ever.
The SuperOneClick pack did a wonderful job.
http://forum.xda-developers.com/showthread.php?t=803682
2) Getting a "safe" firmware
Just in case anything would go wrong, I wanted to be able to flash back to an official firmware.
The ones from this post work without any problem so far.
http://forum.xda-developers.com/showpost.php?p=10558974&postcount=134
However, problem 1 : I couldn't get Heimdall flash my device. Since I'm mainly working on Linux and OSX, that would have been of a great help.
But the "handshaking with Loke" step is always failing...
Actually, I even though I had bricked the phone, since I was stucked with a black screen (1PC and 1GSM in orange) and it took me ages to figure out how to get rid of that.
Solution : get myself a Win 7 computer at office and use Odin. No problem so far with this one.
Problem 2 :after flashing with the official update, I get complains in the recovery mode (when unpacking the apps I think), saying that /dev/block/mmcblk0p3 cannot be mounted, because it does not exist.
After searching on japanese sites, it seems that there is a 3rd partition in addition to the one for /sdcard and /data that is used (as far as I know, only for that) by an app called DioDict (japanese / english dictionary).
Not that this is a great loss, but I don't know where and why this 3rd partition was deleted. I tried to restore one, but after a while I just gave up, since I don't have any dump of the data that was there anyway...
Could anybody confirm/infirm this ???
3) Recovery 2e
Since I wanted to test to other roms, I needed to get back to the recovery 2e.
I gave a try to CF-root, which included that also.
http://forum.xda-developers.com/showthread.php?t=788108
Once again, Odin was the only one that could do the job, Heimdall still ignores me.
Problem : the update is successfully done, but for a reason I ignore, I lose my SIM card in the process.
Flashing back an official ROM makes it available again, but CF-root won't allow me to phone in Japan.
How did you people handle that ? Unfortunately I couldn't afford staying too long without a working phone, so I didn't investigate much further, but did other people have the same kind of problem ?
Conclusion :
As of now, I have a rooted device, and am pretty happy with it.
However, I wish I could give a try to the nice work I've seen around (CyanogenMod on Galaxy S seemed very yummy), while still being able to use my SIM card here.
Any feedback is welcome !
I haven't played around that much with DioDict to tell you right away how to solve this, but maybe there's some answer getting the first firmware:
SC02BOMJJ1 (10/10/13) :
http://fus.samsungmobile.com/Phone_...2BDCMJJ1_SC02BOMJJ1_SC02BOMJJ1_OM_DCM.zip.enc
BINARY_ENCRYPT_STRING 1662317
thanks a lot for this link ! just a question, where did you guys find them ??? the site itself seems very dummy
but as far as I could read on japanese threads, that seems to be some prefab settings
in my case, that third partition has been deleted, so I think I would have to recreate again beforehand.
as for the "how", I must confess I don't know... I' had somehow succeeded in running parted to create one, but for a reason I ignore couldn't assign it to the block
I could install a Cyanogen Beta3 today, and though everything is alright, still got no 3G.
SIM card is not recognized, and it seems impossible to input the appropriate APN information. Could it be that the modem embedded in the SC-02B is different from the mainstream one ?
EDIT : seems that indeed the SC-02B has a different modem. At least the firmware has a different size, hence the need of a different PIT file when you flash from an "international" ROM.
I'm starting to wonder whether I'll see the end of it someday >_<
things that seem to work
Now that we have the capability to recover after we trash our ROM what can we do.
Super Oneclick root - works
Z4Mod "because we all have the need for speed" -works after you use titanium backup to remove some of the bloat-ware from /system
Z4Control works if you use Z4Mod to patch the kernel and convert /data to ext2 first.
The UOTKitchen will work to change the battery icon and other status bar icons if after you have completed these steps http://forum.xda-developers.com/showpost.php?p=9318973&postcount=1290 you extract the framework-res.apk from the resulting zip file and use adb to push the new framework-res.apk to /system/framework/framework-res.apk followed by an adb reboot recovery command before you do anything with the phone. From the recovery menu wipe cache and then reboot now. If you don't do this last step it could lead to having to reflash the factory firmware happened to me about 6 times this weekend. DO NOT TRY THIS IF YOU HAVEN'T CLEARED ENOUGH SPACE ON /SYSTEM BECAUSE IT WILL KILL YOUR PHONE!!!!!
For all those who want a pit file, here I leave you a custom pit file created for the sc-02b.
I must make this clear, this PIT file was made for those who flashed their devices with a rom for some other galaxy s version and want to reflash their devices back to the original SC02BOMJJ1 rom. I cannot ensure you it will be useful or that it will work for anything else.
Also, when using this PIT file with odin, be sure to check the "Re-partition".
@shikigamild :
is this PIT file the same that came from komugi.net ?
at the same time, could you tell me how you got the stock rom file links please ?
@dejanet :
so you say that with the Z4mod you have a fully working device ?
has anyone tried the CF-root package ? after applying it I lost my SIM card, so I wonder if you experimented the same kind of inconvenient there
Oh yes went through all of the fun of trying the various kernels everyone leaves you with sim not recognized.
Sent from my SC-02B using XDA App
Aaarghh,that sucks donkey balls...
Guess that means we won't get any, custom rom any time soon will we?
I'm new to all this stuff, so apologies for the noob questions.
I rooted my SC-02B using the tool in this thread. I was able to install and use the Barnacle Wi-Fi tethering app from the market, so I know it was a successful root. Now when I go to install and use Titanium Backup from the market, it tells me I don't have root access or don't have BusyBox installed. When I go to install BusyBox from the market it shows my phone as being rooted, but when I tap install it gives me a failed message saying my phone isn't NAND unlocked.
How do I do that? Once I get that problem solved, what are the next steps for installing the Z4Mod?
So far I've never installed BusyBox through the market. Just install it with Titanium and it should work fine (click the "Problem ?" button).
Then, I suggest that before doing ANYTHING involving a custom initramfs (like ClockWorkMod), you dump somewhere your mmcblk0p3 partition, in case you want to restore your phone exactly to the same state you got it.
If your not that paranoi, you can skip this part, but as I wrote myself a dozen times here, I forgot it and would be interested also ^^
Ok, thank you for the info. Does Z4Mod cause any problems with this phone? I read in dejanet's signature that the lagfix seems to cause problems. Z4Mod is the lagfix he's talking about right?
bnr32jason said:
Ok, thank you for the info. Does Z4Mod cause any problems with this phone? I read in dejanet's signature that the lagfix seems to cause problems. Z4Mod is the lagfix he's talking about right?
Click to expand...
Click to collapse
z4mod is just a rooting app. There's no lagfix. He's probably referring to OCLF which is made by the same developer. It's obsolete now, so do not use it.
About the rom problem, can't you just flash the modem from a Docomo rom after installing the custom rom?
No, z4root is only for rooting, but z4mod is a lagfix application. As far as i know, it will convert your phone system to ext2. However, i scare it will affect the DioDict application in SC-02B, so i haven't tried it yet.
Trojan,if you fear losing diodict,you can still dump your mmcblk0p3 partition.
It is the one containing diodict data.
I would actually be very grateful for an upload of that one (^-^)/
Sent from my SC-02B using XDA App
trojan111 said:
No, z4root is only for rooting, but z4mod is a lagfix application. As far as i know, it will convert your phone system to ext2. However, i scare it will affect the DioDict application in SC-02B, so i haven't tried it yet.
Click to expand...
Click to collapse
Opps. Didn't realise there are two apps with similar names.
Still, wouldn't suggest it. EXT2 is unstable.
Hi, bebert218. Actually, i am a noob, i don't know how to do it. Can you tell me how to view the partitions in the internal memory? I suppose DioDict application contains a database file somewhere in the internal memory, but i don't know where and what the file name is. Appreciate if you could give me a hand on it. Thanks.
Custom Kernel and Roms
From reading through the forums it seems custom roms present issues with the either the sim card or modem on the sc-02b. Are custom kernels causing issues as well on this phone?
Yes it is the kernel that causes the problem. I think a couple of us have tried them all.
Sent from my SC-02B using XDA Premium App
disappointing Other than rooting and using Galaxy tuner to do some tweaks there isn't really much else to do. At least the upgrade to omka5 showed much improvement from 2.2
Disclaimer: You may brick your phone. NOT for AT&T
Reminder: Make sure your phone has enough battery charge to flash this, it's larger than normal.Hi,
Here is a huge CWM zip that restores your Bell phone to stock 2.2.2. I have tested it on my phone several times and it worked perfectly, there is still the chance that something may go wrong, but I am feeling confident in it.
What this does is similar to my app or scripts, it puts my backup of Bell's 2.2.2 partitions on your phone, but instead of using dd, it uses tenfar's CWM and flash_image. Some partitions are HUGE, and take a while, your phone is not locked up.
This has been updated to include the Bell bootloader for 2.2.2 and the radio for 2.2.2.
EDIT: This has been updated again to ram fix the boot and recovery partitions if there is a ram problem.
It writes to partitions 1, 2, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 17. 3 is left out because it's your pds partition, and data and cache have no relevant content. You must factory reset after using this to clear those. So, that's your boot, recovery, system, webtop, cdrom, preinstall, and several other partitions. This is to get back to stock Bell 2.2.2, it's not just a boot/system replacement, if that is a fruitcake, this is a gobstopper.
Please note: This restores your Bell phone to stock condition, that means you won't be unlocked, CWM will be overwritten with the stock recovery. It will be just like you bought it. If you want to keep flashing things in CWM with the unlocked bootloader, then immediately after flashing the stock zip, flash the unlock and fix zip. If you don't then you will have to reflash an unlocked bootloader, and reflash CWM recovery, which is time consuming any annoying, it doesn't mean you will be permanently locked again. I had to spell that out to the folks that don't really understand this stuff. At all.
If you want root after installing this, just install Superuser.apk from the market.
Bell_FR_2.2.2.zip (Froyo not France)
(md5 e431b4cc3ba7e3a27b6aad6982a31066)
Cheers!Oh, I forgot to mention, this is not quite stock, there are su and sudo binaries in /system/bin. Just install Superuser.apk to be rooted. they haven't been a problem for doing an OTA yet, but they are easy enough to remove if it comes up.
unlocked-fixed-Bell-2.2.2.zip
Mirror: unlocked-fixed-Bell-2.2.2.zip
Damn, nice work as always, man! This should come in handy for lots of us Bell Atrix users that feel left out. Lots will appreciate this!
When you say without amnesia are you talking about the bootstrap or are you talking about a user who is using the bell_ihop and then installs cwm and then reboots and looses recovery?
So a 2.3.4 bootloader and radio will work find booting a 2.2.2 bell ?
Will you eventually be able to compile a zip for Bell gingerbread?
IrshaadH said:
Will you eventually be able to compile a zip for Bell gingerbread?
Click to expand...
Click to collapse
the problem would be hosting it, not sure how he would be able to do that.
akurit said:
When you say without amnesia are you talking about the bootstrap or are you talking about a user who is using the bell_ihop and then installs cwm and then reboots and looses recovery?
So a 2.3.4 bootloader and radio will work find booting a 2.2.2 bell ?
Click to expand...
Click to collapse
keeping in mind that this is only for the recovery with unlocked devices, what he means is that the CWM recovery that tenfar put out has a problem with int'l phones (pretty sure it's all int'l) where IN recovery (not just the normal ROM, like the problem we had before) only 300 and some mb of RAM is available. since this zip is over 300mb, it can't all load into your RAM properly with normal recovery.
NFH found this bug, and patched recovery for us so as to fix the RAM problem. the two files attached are fixed recoveries for the two separate MBR versions of int'l devices.
to find what version you should use, connect to phone via ADB and then
Code:
adb shell
su
cat /proc/cmdline
and then search for the part of the output where it says "tegrapart=mbr:" and read that. it should have either "1100" or "d00" somewhere in it, use the CWM zip attached that has your respective output.
hope that clears up your question, if you have any further ask them in here.
IrshaadH said:
Will you eventually be able to compile a zip for Bell gingerbread?
Click to expand...
Click to collapse
Hi,
I believe y2whisper may be working on something like that. The point of getting back to stock 2.2.2 is to be able to apply the final OTA for Bell GB. Certainly something similar can be done for any firmware you want to flash.
Cheers!
i flashed the d00 and I do maintain unlock however no cwm just stock recovery with no menus.
tried it again and it work
but seems like i have to fastboot flash it each time i want to use recovery
akurit said:
i flashed the d00 and I do maintain unlock however no cwm just stock recovery with no menus.
tried it again and it work
but seems like i have to fastboot flash it each time i want to use recovery
Click to expand...
Click to collapse
I know what you are talking about, but I got that with a stock bootloader.
If you are going to be using CWM recovery with this 2.2.2, then flash the boot file for d00 as well, it gives you the ram fix and for some reason it doesn't cause that issue.
Cheers!
Here is an international CWM recovery, it detects the 1100 vs d00 tegraparts and installs the right recovery for it.
CWM_INT_Recovery.zip
(Just use it with whatever CWM recovery you are using now, it will update it with the ram fixed one.)
NFHimself said:
I know what you are talking about, but I got that with a stock bootloader.
If you are going to be using CWM recovery with this 2.2.2, then flash the boot file for d00 as well, it gives you the ram fix and for some reason it doesn't cause that issue.
Cheers!
Here is an international CWM recovery, it detects the 1100 vs d00 tegraparts and installs the right recovery for it.
CWM_INT_Recovery.zip
(Just use it with whatever CWM recovery you are using now, it will update it with the ram fixed one.)
Click to expand...
Click to collapse
ohhh, that's a nicely scripted installer you got there. i think that would be quite handy for int'l users trying to flash custom kernels, is it possible to apply that script to select the correct boot.img out of two for the right tegrapart? if that's possible i think you should hit faux/edgan up with that script and let them apply it to their int'l kernels so users can just use on CWM to install it.
raybond25 said:
ohhh, that's a nicely scripted installer you got there. i think that would be quite handy for int'l users trying to flash custom kernels, is it possible to apply that script to select the correct boot.img out of two for the right tegrapart? if that's possible i think you should hit faux/edgan up with that script and let them apply it to their int'l kernels so users can just use on CWM to install it.
Click to expand...
Click to collapse
Hi,
Sure, it's just replacing the word recovery with boot and having the right boot images in the file.
Cheers!
yes its zipping now. off to bed but tomorrow I will back up my stuff and attempt to flash to see if it works.
@akurit
I forget off the top of my head but there is a file that you just have to delete to prevent that. the file just flashes the old recovery on every reboot. get rid of that and you will be fine.
Awesome work! This makes it much easier to get back to 2.2.2
Its installing now!
now at some point the install stopped and I think I saw it say status 0 and then recovery rebooted. so I am not sure what happened there.
ive rebooted with no problems. and its uploading now. if someone is willing to test this out (a bit difficult for me since I am already on 2.3.4) let me know. and will send you the link. would like to see a proper install before i share it with the masses.
This is why hehee
tenfar said:
......
Please Remove install_recovery.sh located in your /system/etc/ ,so that the recovery will not be overwrite to stock one.........
Click to expand...
Click to collapse
now it remains unlocked and I have recovery even if i reboot... but the ram issue still exists
y2whisper said:
Its installing now!
now at some point the install stopped and I think I saw it say status 0 and then recovery rebooted. so I am not sure what happened there.
ive rebooted with no problems. and its uploading now. if someone is willing to test this out (a bit difficult for me since I am already on 2.3.4) let me know. and will send you the link. would like to see a proper install before i share it with the masses.
Click to expand...
Click to collapse
i could test it for you, i should be able to tell if it works alright or not, since i'm starting from an AT&T build of 2.3.4. would i have to head back to stock Bell using Gobstopper before i use your package too? i got a whole buncha time on my hands this week, so i should be able to test it however you want.
anyone try flashing the bootloader and radio?
kevnb said:
anyone try flashing the bootloader and radio?
Click to expand...
Click to collapse
Hi,
I have tested it, no problems, but went back to IHOP and the ram-fixed bootloader for 2.2.2 in the OP so recovery will work.
Also, the file install_recovery.sh located in your /system/etc/ doesn't exist in the Gobstopper, so that isn't causing recovery to be generated by patching boot.
Cheers!
So its when flashing the webtop that the install stops with the error code. when i boot up all is ok but a reboot later and recovery is gone (as in you select it and it just boots into android). reflashing cwm recovery fixes that.
I have tried swapping the webtop files to no avail. going to keep trying. any ideas are welcome
y2whisper said:
So its when flashing the webtop that the install stops with the error code. when i boot up all is ok but a reboot later and recovery is gone (as in you select it and it just boots into android). reflashing cwm recovery fixes that.
I have tried swapping the webtop files to no avail. going to keep trying. any ideas are welcome
Click to expand...
Click to collapse
Hi,
What recovery are you using, if it's not ram fixed you are going to run into situations where you don't have enough space to flash it.
Cheers!
ahhhh.
you know i was wondering if that was it. I even repackaged the recovery thinking it would be the cause.
I don't believe I was ram fixed at the time of the backup. So I am thinking either, have custom recovery flashed in that spot, or change the order to where recovery gets flashed after.
Hi, I have many problems at a time lol. First of all, I bought this phone 'cause it was so cheap and it works fine for my mom. The problem is, I think I was scammed because the phone allows emergency calls only. I tested with many chips but they don't work, so I guess I'll have to find a solution for that (imei unlocking with z3x maybe?). Also, I don't know if the phone is branded. I think it's not, because it starts with other chips, but the bootscreen is still from the original company (don't know how to change it).
Okay, now that you know the conditions of the phone, I wanna ask if the phone being imei blocked affects on wether I can root it or not, cause I tried many many root files on CWM 5, but nothing happens. Some of them say that the process was completed, but I type "su" in the terminal and it says "not found". Also, I downloaded root checkers and they say the phone's not rooted. The roots I remember are universal_gb_root_v25, v23b, upd_1 and Root_Cooper. I am desperate, please help.
Also, I updated the firmware with Kies (can't remember old firmware), so now I have GB 2.3.6. I don't know if Kies might have screwed it up. I've also noticed that most people have a baseband ending in something like KT8, but mine is different... I remember I had to change the baseband on my Xperia X8 to unlock bootloader, but I know nothing about Samsung phones. Anyway, phone details are:
GT-S5830L
baseband S5830LUBLP1
kernel 2.6.35.7-1190892 [email protected] #1
compile number GINBGERBREAD.UBLP1
android 2.3.6
Thank you very much! I am posting cause I searched but found nothing u_u.
ps: sorry for my bad english.
Try this method,
[Guide] Know your Device: Galaxy Ace GT-S5830
:angel:
xwalero said:
Hi, I have many problems at a time lol. First of all, I bought this phone 'cause it was so cheap and it works fine for my mom. The problem is, I think I was scammed because the phone allows emergency calls only. I tested with many chips but they don't work, so I guess I'll have to find a solution for that (imei unlocking with z3x maybe?). Also, I don't know if the phone is branded. I think it's not, because it starts with other chips, but the bootscreen is still from the original company (don't know how to change it).
Okay, now that you know the conditions of the phone, I wanna ask if the phone being imei blocked affects on wether I can root it or not, cause I tried many many root files on CWM 5, but nothing happens. Some of them say that the process was completed, but I type "su" in the terminal and it says "not found". Also, I downloaded root checkers and they say the phone's not rooted. The roots I remember are universal_gb_root_v25, v23b, upd_1 and Root_Cooper. I am desperate, please help.
Also, I updated the firmware with Kies (can't remember old firmware), so now I have GB 2.3.6. I don't know if Kies might have screwed it up. I've also noticed that most people have a baseband ending in something like KT8, but mine is different... I remember I had to change the baseband on my Xperia X8 to unlock bootloader, but I know nothing about Samsung phones. Anyway, phone details are:
GT-S5830L
baseband S5830LUBLP1
kernel 2.6.35.7-1190892 [email protected] #1
compile number GINBGERBREAD.UBLP1
android 2.3.6
Thank you very much! I am posting cause I searched but found nothing u_u.
ps: sorry for my bad english.
Click to expand...
Click to collapse
Only if the above post didn't work, use the files from the below guide. They are posted by the people using S5830L. Here is the link,
Rooting Galaxy Ace GT-S5830L
Hope I Helped
xwalero said:
Hi, I have many problems at a time lol. First of all, I bought this phone 'cause it was so cheap and it works fine for my mom. The problem is, I think I was scammed because the phone allows emergency calls only. I tested with many chips but they don't work, so I guess I'll have to find a solution for that (imei unlocking with z3x maybe?). Also, I don't know if the phone is branded. I think it's not, because it starts with other chips, but the bootscreen is still from the original company (don't know how to change it).
Okay, now that you know the conditions of the phone, I wanna ask if the phone being imei blocked affects on wether I can root it or not, cause I tried many many root files on CWM 5, but nothing happens. Some of them say that the process was completed, but I type "su" in the terminal and it says "not found". Also, I downloaded root checkers and they say the phone's not rooted. The roots I remember are universal_gb_root_v25, v23b, upd_1 and Root_Cooper. I am desperate, please help.
Also, I updated the firmware with Kies (can't remember old firmware), so now I have GB 2.3.6. I don't know if Kies might have screwed it up. I've also noticed that most people have a baseband ending in something like KT8, but mine is different... I remember I had to change the baseband on my Xperia X8 to unlock bootloader, but I know nothing about Samsung phones. Anyway, phone details are:
GT-S5830L
baseband S5830LUBLP1
kernel 2.6.35.7-1190892 [email protected] #1
compile number GINBGERBREAD.UBLP1
android 2.3.6
Thank you very much! I am posting cause I searched but found nothing u_u.
ps: sorry for my bad english.
Click to expand...
Click to collapse
Mybe you haven't enough internal memory space to push su files
Try this
Firmwares and help rooting (3th Post)
Okay I'll try these solutions, thank you all very much!
btw, I don't think it's a space issue 'cause I have like 55mb left
xwalero said:
Okay I'll try these solutions, thank you all very much!
btw, I don't think it's a space issue 'cause I have like 55mb left
Click to expand...
Click to collapse
55mb internal space (data) is not the same as 55mb system space (rom space)
Oh god, I can't believe it still doesn't work D:
I think it would be good if I started from scratch. I mean, flash a stock firmware or something, like a factory reset. I installed CWM, how can I uninstall it?
What is the best way to do that?
thanks
xwalero said:
Oh god, I can't believe it still doesn't work D:
I think it would be good if I started from scratch. I mean, flash a stock firmware or something, like a factory reset.
What is the best way to do that?
thanks
Click to expand...
Click to collapse
Install CWM 5 from Recovery Mode. Go to CWM> Wipe data/ factory reset, Wipe cache partitions, Mounts & Storage> Format /system, Advanced> Wipe Dalvik cache, Wipe Battery Stats. Now re-flash the stock rom using odin through Download Mode. You can then try installing root and CWM. Hopefully it works well this time.
CWM 5.0.2.6 fix for Samsung Galaxy Ace S5830
Hope I Helped
Nothing seems to work u_u. I flashed the stock rom, installed cwm fix, flashed Root_Cooper.zip and nothing happened. Then I flashed the no-junk-apps and also tried with AceGingerRoot, upd_1, universal_gb_root_v25, and Root, but nothing happens. Root and upd_1 give me an error like Status 7, installation aborted (some guy in one of the links Viper sent me had the same error). I type in he terminal "su", and it says access denied.
I don't know what else to do :c
xwalero said:
Nothing seems to work u_u. I flashed the stock rom, installed cwm fix, flashed Root_Cooper.zip and nothing happened. Then I flashed the no-junk-apps and also tried with AceGingerRoot, upd_1, universal_gb_root_v25, and Root, but nothing happens. Root and upd_1 give me an error like Status 7, installation aborted (some guy in one of the links Viper sent me had the same error). I type in he terminal "su", and it says access denied.
I don't know what else to do :c
Click to expand...
Click to collapse
No, that's not what I meant. Before you flash a fresh copy of stock rom, make sure to do a complete wipe. You cannot do that with the stock recovery mode and hence you install CWM. Just follow my instructions in the above post. Once you have wiped of all data, then flash the stock rom back. Always remember Root first then install CWM. If you do it the other way, you will end up getting status 7 error. Do post the result.
mahithm said:
No, that's not what I meant. Before you flash a fresh copy of stock rom, make sure to do a complete wipe. You cannot do that with the stock recovery mode and hence you install CWM. Just follow my instructions in the above post. Once you have wiped of all data, then flash the stock rom back. Always remember Root first then install CWM. If you do it the other way, you will end up getting status 7 error. Do post the result.
Click to expand...
Click to collapse
Oooh okay, i did everything but rooted after cwm. Ill try that!
It worked! thank you all! (even though it rebooted once, but it hasn't happend again)
Now, what JellyBean ROM would you recommend? I just want a "fast" one. (I know there's no such thing as "best rom" or something, I'm just asking for advice)
Some ROMs say that I have to install CWM 6 or above, should I do that? or just stick with this fixed version?
xwalero said:
It worked! thank you all! (even though it rebooted once, but it hasn't happend again)
Now, what JellyBean ROM would you recommend? I just want a "fast" one. (I know there's no such thing as "best rom" or something, I'm just asking for advice)
Some ROMs say that I have to install CWM 6 or above, should I do that? or just stick with this fixed version?
Click to expand...
Click to collapse
All CM 10 (JellyBean) roms works quite well with CWM 5, so I suggest you stick with it unless you want to go for CM 11 (KitKat) roms. CWM 6 is mainly meant for CM 11 based roms but there is one CM 11 rom (KitKat for All) that works fine with CWM 5. I haven't tried all CM 10 roms, so I can't help you in that part. But I can provide you the list of all custom roms for Ace. You can try it yourself and be the judge Here is the link,
Know your Device:Galaxy Ace GT-S5830 ~Root~Odin~CWM~ROM LIST
Hope I Helped