I rooted my i9020a on 2.3.4 using the instrctions on how to root for mac. It worked perfectly but i think i made an error because i flashed clockwork recovery mod 3.0.0.0 as per the instructions. I am affraid after reading some posts that this was the wrong thing to do. The bootloader is still unlocked, is it ok to flash to a differant version and if so how do I do that? Will it be fine to leave it at 3.0.0.0 for this phone?
No clue with Macs but you can just reflash a different version. No big deal.
Thanks i actually figured out that rom manager flashed the correct version regardless
Related
So I rooted my phone via Universal Androot and it looks like it went through without a hitch. Kinda...
Then I DL Rom Manager and Flashed the CW Recovery from there and that looks like it installed ok as well.
Do I need to do this fastboot thing to install DJ Steve's 1.4.6 ROM or can't I just reboot into recovery and install from SD card now?
It seems like that would be the easier way just like the other android phones I have flashed new roms for?
I just want to make sure I dont need that fast boot to avoid any issues with new ROM flash.
You are going to need several different recoveries to upgrade the streak and none of them are the recovery you would flash through rom manager. I'm almost 100% sure you can not flash any roms via clockwork that has been installed through rom manager. Definately learn about fastboot. It's really quite essential to pretty much everything you want to do with the streak. Search for a thread entitled "guide to upgrading and downgrading the dell streak" which has been posted here at xda and on the modaco forum as well. It has a link to pdf which gives you an easy step by step guide to installing and using fastboot as well as the recoveries and pretty much everything else. Hope this helps. Good luck.
So, he's running a custom ROM right now, the latest desire hd port, GB, etc.
Well, most everything else needs CWM 3.006 or whatever. So, I'm trying to flash that. BUT, his phone acts as if he doesn't have root. I't S-offed and has "su" (the app) but it just doesn't work.
Tried flashing cwm with fastboot, "permission denied"
Idk what else to do
Regards
Smith
smithisize said:
So, he's running a custom ROM right now, the latest desire hd port, GB, etc.
Well, most everything else needs CWM 3.006 or whatever. So, I'm trying to flash that. BUT, his phone acts as if he doesn't have root. I't S-offed and has "su" (the app) but it just doesn't work.
Tried flashing cwm with fastboot, "permission denied"
Idk what else to do
Regards
Smith
Click to expand...
Click to collapse
doubt its bricked...(its not bricked if you can get to the bootloader
what h-boot version do you have?
use the PD15IMG.zip to restore your phone
VibrantOwnr said:
what h-boot version do you have?
Click to expand...
Click to collapse
86.0.0.0 i believe... I followed the perm root tut before flashing this custom ROM, then he messed it up..
smithisize said:
86.0.0.0 i believe... I followed the perm root tut before flashing this custom ROM, then he messed it up..
Click to expand...
Click to collapse
i dont think you can flash using fastboot in .86.
if it wont boot to the rom try the PD15IMG.zip file to restore
if it boots to the rom, go back to the true s-off/permroot guide in the development section and flash your bootloader (there is directions at the bottom of the first post (the post with the instructions))
After that it should work for fastboot
You can alternatively flash recovery through rom manager (off of the market..the free version will do)
VibrantOwnr said:
i dont think you can flash using fastboot in .86.
if it wont boot to the rom try the PD15IMG.zip file to restore
if it boots to the rom, go back to the true s-off/permroot guide in the development section and flash your bootloader (there is directions at the bottom of the first post (the post with the instructions))
After that it should work for fastboot
You can alternatively flash recovery through rom manager (off of the market..the free version will do)
Click to expand...
Click to collapse
ROM Manager didn't work (again, couldn't obtain permissions).
So, I'm going to flash the ROM, hope for the best, then if $*&^ hits the fan, I'll result to flashing a diff bootloader.
Thanks for your advice, didn't think about flashing a diff booloader... used to my Cappy xD
Regards
Smith
have you tried using TrueBlue's recovery .zip it was the only way I could get either of my phones to take 3.0.0.6
HERE is the thread for it
Well, I flashed regardless of the 3006 req, and it went fine... Whatever lol.
thanks for the help and suggestions
Regards
Smith
Hey, ive rooted a few phones before and am familiar with CWM and stuff but im having real trouble understanding the information on this forum at the moment.
Info on the phone:
Sys ver: 45.31.0.MB860.Orange.en.GB
Android Ver:
2.3.4
Baseband:
N_01.100.00r
Build Number:
4.5.2a-74_OLE-31
The phone is rooted and starting titanium back / rom manager confirms this. I tried flashing CWM through rom manager but got a failed to boot 2 error. I figured this was because the bootloader might be locked but i cant figure how to unlock it. Some threads say run fastboot oem unlock , some say flash sbf files only if your not on 2.3.4(but i am?).
Im just a little confused at why i cant get CWM installed and whats stopping me proceeding. It seems there is so much information on this subject but not enough clear and precise info.
Please help?
Thanks,
Piercy
You'll need to unlock your bootloader first. There's a thread titled "[HOWTO NOV18]UNLOCK BOOTLOADER, FLASH RECOVERY, INSTALL ROM Atrix 4G Bell/int'l + ATT". I suggest to read that up fully, and then follow the instructions for the international version. That's how I unlocked my (SEA Retail) Atrix.
One thing to mention is regarding the /system/etc/install-recovery.sh or /etc/install-recovery.sh which will restore stock recovery on boot. It was mentioned last in the thread, but I suggest to delete those files first before flashing cwm.
quetzalcoatl2435 said:
You'll need to unlock your bootloader first. There's a thread titled "[HOWTO NOV18]UNLOCK BOOTLOADER, FLASH RECOVERY, INSTALL ROM Atrix 4G Bell/int'l + ATT". I suggest to read that up fully, and then follow the instructions for the international version. That's how I unlocked my (SEA Retail) Atrix.
One thing to mention is regarding the /system/etc/install-recovery.sh or /etc/install-recovery.sh which will restore stock recovery on boot. It was mentioned last in the thread, but I suggest to delete those files first before flashing cwm.
Click to expand...
Click to collapse
Thanks you very much indeed. its been so easy now ive done that, im now in CWM (ahh feels like home). Backing up about to flash a rom so all good Thank you!
Hey guys I'm new to android had an iPhone for 6 years. Just got the gs4 two months ago. I rooted the phone took out bloat ware apps using titanium back up. Have a few other rooted apps. Got Interested in ROMs and kernels so did some research looked around on here to how to do it. I downloaded infamouses newest ROM. I have ROM manager and I downloaded cwm recovery through the Rom manager. When I go to back up my current ROM and everything it boots into recovery mode but it isn't cwm recovery. The emblem doesn't come up and I believe its the stock recovery. My question is how can I get the cwm recovery so I can back up my current ROM and then wipe it and install the new one. I'm new so sorry if this is easy or anything I appreciate all the help
Download goo manager and let it install twrp then just flash cwm thru twrp . Or keep twrp and remember to flash loki doki if needed.
Wait!
What firmware is your phone currently on? MDL OR MF3?
If MF3, stop now. Do not flash anything.
Sent from my SGH-I337 using xda premium
Okay I figured out the problems. When I hit reboot and superuser is supposed to grant root permissions an error comes up saying superuser has stopped working then goes into the stock recovery mode. The only thing I found with MDL in it was the baseband version 1337UCUAMDL
Your safe to continue flashing custom recovery on MDL Baseband
Sent from my SGH-I337 using xda app-developers app
Does anyone know how to fix this problem? Its so annoying I have tried goo manager and twsp recovery. And they all do the same thing.
Division4thor said:
Does anyone know how to fix this problem? Its so annoying I have tried goo manager and twsp recovery. And they all do the same thing.
Click to expand...
Click to collapse
Going on the information you have given, if you are doing right and using the correct version for your phone, GooManager and TWRP should be working for you. However, if you go to the development section and look for OUDHS CWM recovery, directions are given in the OP about how to manually install that recovery. Again, directions are in that thread about how to do it. I do hope you are reading all of every post that contains something you are trying to do (in other words, if you use OUDHS, read the entire thread first). Good luck.
scott14719 said:
Going on the information you have given, if you are doing right and using the correct version for your phone, GooManager and TWRP should be working for you. However, if you go to the development section and look for OUDHS CWM recovery, directions are given in the OP about how to manually install that recovery. Again, directions are in that thread about how to do it. I do hope you are reading all of every post that contains something you are trying to do (in other words, if you use OUDHS, read the entire thread first). Good luck.
Click to expand...
Click to collapse
Yeah Idk I'm so over this getting so frustrated. I'm new to this I read that post. Not all 51 pages hope you didn't mean that..
This is the easiest way ever, 1 click, and everything is ready to go....try it...
http://forum.xda-developers.com/showthread.php?t=2297900
Good luck
Thank you
TheAxman said:
This is the easiest way ever, 1 click, and everything is ready to go....try it...
http://forum.xda-developers.com/showthread.php?t=2297900
Good luck
Thank you
Hey thanks for the help. I got twsp recovery through goo manager and worked perfectly. I'm having such a bad experience trying to install this rom. I went into the recovery mode after backing up my current rom and system. I wiped everything out then went into my sd card amd installed the zip that is listed in the infamous page in the developers part. I hit install and then said I'm not rooted and would I like to install superuser. I slide the thing and then went to reboot and now has been stuck saying samsung and custom with an open love under it. Pulled the batter went back into twsp and tried to reboot and still stuck. This is all after I thought I installed the rom already and nothing changed except wiped my phone. Can anyone help
Click to expand...
Click to collapse
Are you installing loki doki after the rom ?
first, i unlocked the bootloader and it was perfectly fine.
then i flashed the latest TWRP version
now, when i flashed supersu, i got bootloops.
i tried to to install the older TWRP version (2.8.7.1) but nothing improved so i reverted back to the latest version. Now even my recovery is borken.
I REALLY hope someone will help me fix my problem.
EDIT: I also tried to install the 2.62 version of SuperSu because the 2.46 didn't work.
anyone, please?
xxhunterxx11 said:
anyone, please?
Click to expand...
Click to collapse
Can you boot into Bootloader? You might have to reflash back to complete stock before you can do anything again using adb/fastboot commands. Have a look at my posts in this thread:
SOLVED: Flashed TruPureXMM rom in Indian dualsim XT1572 and now No sim detection
Most of my posts are on the second page but should help guide you to get back to stock without relocking the bootloader. Once you are back to stock and can confirm the phone is working, you can start your modding again. I can only assume your phone has a software issue. Unfortunately, this is the only solution I can think of and can't really suggest anything else. You will lose all your internal storage data using this method unless you have made a backup. I would normally do this using recovery but seeing as you can't boot normally or into that, I don't see a way for you to do that, unless you try pulling files through adb though this will probably be a long and slow process.
Hope this helps.
Thanks,
Ooms
Is it bricked or bootlooping? Those are 2 very different things. If its bootlooping then its not bricked. If its bricked then you can't do anything with it.
Nevermind guys, i've fixed it by flashing stock firmware through fastboot, just like dj_ooms said. Thanks for the help anyways. And also razieltov, i was getting bootloops. Sorry for not knowing the difference between the two