Related
I have an unrooted hero I have had since launch day. I am now thinking about rooting my hero with use of the latest Sprint leak. my understanding is if you update to the leak of even the official builld whenever that may come out, it will close all current rooting holes available. I guess that doesn't mean in the future there won't be other possibilities. do these new build give the same sense of stability as the official roms because we can now use an official 2.1 kernal?
so from what I have been reading there appears to be only one Rom that is based on the current 2.1 leak and that is flipz Rom? I have a few questions or statements before I do anything to my phone. one, will this help get rid of the lag when typing? two, I need to make sure Bluetooth is still going to work as I have a home phone that I connect my cell to when I enter the door. if I decided to flash back to the official release, is that possible?
dbldown768 said:
I have an unrooted hero I have had since launch day. I am now thinking about rooting my hero with use of the latest Sprint leak. my understanding is if you update to the leak of even the official builld whenever that may come out, it will close all current rooting holes available. I guess that doesn't mean in the future there won't be other possibilities. do these new build give the same sense of stability as the official roms because we can now use an official 2.1 kernal?
Click to expand...
Click to collapse
As of right now; many people are cautious about testing the latest 2.1 leak; because of the concerns you expressed earlier -- having your phone unrooted by the 2.1 leak when you flash the new update. So, with that said; the current 2.1 ROM's are all pretty stable. This new leak, however probably is as well, but again... I don't know whose all tested it, for fear of loosing root access.
dbldown768 said:
so from what I have been reading there appears to be only one Rom that is based on the current 2.1 leak and that is flipz Rom?
Click to expand...
Click to collapse
No. Damageless ROM's are also based on the latest Sprint leaks. All ROM's you see should tell which ROM they are based off of. Almost all 2.1 ROM's are currently built from any of the Damageless ROM's -- just read the front page of the ROM you're looking into.
dbldown768 said:
I have a few questions or statements before I do anything to my phone. one, will this help get rid of the lag when typing? two, I need to make sure Bluetooth is still going to work as I have a home phone that I connect my cell to when I enter the door. if I decided to flash back to the official release, is that possible?
Click to expand...
Click to collapse
1. Possibly. The lag problem is relative to the person/device. Not everyone experiences this problem. However, turning off "Vibrate when typing" apparently helps with the lag issues. YMMV.
2. Please see first post I made.
Thanks for the quick reply. I'm investigating the best way of rooting my phone. I see there are a few ways listed on the wiki, but then i just ran across Fresh Kitchen (http://geekfor.me/new-release/fresh-kitchen-105)? This is suppose to root your phone for you? Is this a stable way of rooting or should i just use the command line mehods? Also, i have read that you should do a nandroid backup of your phone? Not sure if fresh is doing this for you? The other thing i should mention is that i just have a stock microSD card, so I dont plan on using app2sd, i dont think this is a problem correct?
I also see people load their roms using their microSD card and just putting some update.zip file on there. Is this the standard procedure once you root your phone and get a rom loaded?
Actually, Fresh 2.1, and 2.1.1 are the only ones as of right based off of the newest leak (signed with release keys rather then test), Damageless and Treve are currently working on improving DCUpdater, DConfig, and building a new ROM from the release-keys build.
As far as how to root, I recommend the command line method. While the auto-root methods are nice, actually doing it yourself will give you some experience with things you're gonna be using.
Yes, loading the update.zip to the root of the SDCard is the standard way to flash.
No, not using Apps2SD is not a problem, most people use it because they have a faster SDCard, which gives better performance when loading apps.
A Nandroid backup is something that you will do before you flash any update.zip (At least you're supposed to). It's basically an "Image" of your phone exactly how it was the point in time that you made it, so if you flash something and everything goes horribly wrong, you can restore said nandroid, and it will be like it never happened. (The exceptions are flashing a radio and screwing with the PRL/PRI, nandroid doesn't touch those.)
dbldown768 said:
Thanks for the quick reply. I'm investigating the best way of rooting my phone. I see there are a few ways listed on the wiki, but then i just ran across Fresh Kitchen (http://geekfor.me/new-release/fresh-kitchen-105)? This is suppose to root your phone for you? Is this a stable way of rooting or should i just use the command line mehods? Also, i have read that you should do a nandroid backup of your phone? Not sure if fresh is doing this for you? The other thing i should mention is that i just have a stock microSD card, so I dont plan on using app2sd, i dont think this is a problem correct?
Click to expand...
Click to collapse
Fresh's kitchen will allow you root your phone and yes it's stable. However, it's best you try doing it via ADB commands, as there will come a time when you'll want to create things for the community and wished you had prior experience using it. I recommend you trying to root via this tutorial HERE If you follow the directions, you shouldn't have any problems whatsoever.
Stock card is perfectly fine; you're able to use Apps2sd, but don't have to.
dbldown768 said:
I also see people load their roms using their microSD card and just putting some update.zip file on there. Is this the standard procedure once you root your phone and get a rom loaded?
Click to expand...
Click to collapse
To try out different ROM's -- the process is to download the file (which is a update.zip file in itself), but has been renamed to match the name of the ROM. All you have to do is; copy to your sd card, boot into recovery, flash ROM from the sd card, reboot.
abcdfv said:
Actually, Fresh 2.1, and 2.1.1 are the only ones as of right based off of the newest leak (signed with release keys rather then test), Damageless and Treve are currently working on improving DCUpdater, DConfig, and building a new ROM from the release-keys build.
Click to expand...
Click to collapse
There's your real answer. Thanks.
I'm having a hard time understanding why i would need the flash recover image in this tutorial (http://forum.xda-developers.com/showthread.php?t=583291)? I understand i would want to do a backup of the current phones state, but why would i flash anything before actually making this backup? Maybe i'm not understanding the process correctly, but i just want to get "su" ability and then do the nandroid backup? Is the nandroid backup an app i use?
Nandroid is built into the recovery image you're flashing. Before flashing the recovery image, there is no way for you to nandroid.
thanks! after watching the youtube video posting that mad more sense. So i know there is a chance of bricking your phone during all of this, where does that chance increase? Is it during the flashing of the customs roms, not so much the rooting process?
It is safe to say once the "official" 2.1 android comes out there will always be a custom rom based on it? meaning that if chosen by developers here there could be a build off the "official" 2.1 with the only difference is the rooted user is still allowed? I know that most dev are going to change the build in someway to "improve" on what the official build is done.
The only proven way to brick this phone is by flashing a GSM radio, or by having a failed RUU. I've never heard of anyone getting a "true" brick from rooting/flashing ROMs.
Yes, once the official build is released, all ROMs from then on are most likely going to be based of off it.
Ok, stupid question. I just followed the guide to rooting my phone, doing the nandroid backup and copying the backup to my pc. There are a lot of guide to root, but how to you actually flash the custom rom? I saw something about holding down the 'home' button when starting up? Does this bring you to the recovery image again? Do the roms have to be named something specifically?
Place the ROM in the root of your sdcard, and boot into recovery by holding Home+Power. From then select the "Flash update.zip" option and it will show all of the .zip files in the root of your sdcard. Just pick which one you want to flash.
great! thanks for all the help.
ok, so i decided to load damage's sprint leak that would still give me root access, well it doesnt boot. just goes to the "sprint now" screen and reboots over and over again? any ideas?
Did you wipe data and Dalvik?
Anytime you go from one ROM version to another (1.5 to 2.1, 2.1 to 1.6, 1.6 to 1.5, etc etc) you have to wipe, or if there's major changes between rom versions.
what do you wipe the data? i just picked the flash from zip file from sd card?
In recovery there's a catagory for wipe. Wipe data and Dalvik, then reflash and you'll be fine.
cool. thanks. trying that now.
so everything is working now. So i know one of the main benefits of having a rooted is phone is wifi teathering. Are apps like this in the market place or only on here?
There's Easytether and PDAnet. I haven't tried Easytether, since last I've heard it's x86 only, but PDAnet was a horrible experience. I just flashed an Eris based ROM, broke my PRI, and it enabled the built in USB tethering.
dbldown768 said:
so everything is working now. So i know one of the main benefits of having a rooted is phone is wifi teathering. Are apps like this in the market place or only on here?
Click to expand...
Click to collapse
go to market and download barcode scanner
open up barcode scanner and go here and then just point the camera at the qr code and it'll download to your phone.
remember to check 'unknown sources' > setting > applications
wifitether 1.6. works flawlessly on either fresh or damageless latest 2.1
I have managed to unlocked my bootloader and run CM7 Beta on my phone, the drawback is you need to download a different radio image. (In the US anyway)
I have a Chinese Retail ME860, the Chinese radio firmware was ****ty anyway.
Unfortunately, the only proof I can offer is that the battery has Chinese writing under the battery model number. Flashing CM7 changed my phone to a MB860. o___o'
Screenshots: (Warning, Images are gigantic. Or rather Gingantic.)
http://img.photobucket.com/albums/v334/sejiro/IMG_9072.jpg
http://img.photobucket.com/albums/v334/sejiro/IMG_9073.jpg
http://img.photobucket.com/albums/v334/sejiro/IMG_9074.jpg
Here's also a message from eval I got via PM. This only applies if your OdmReserved is 30003000300004000 after your bootloader is unlocked.
eval- said:
But you are in dangerous territory... never accept and OTA or flash any ME860/MB861 .sbf ever again! I am not 100% sure what will happen if you flash another non-chinese international .sbf (it _might_ work) but I would suggest you stick with "fastboot flash" or using a CWM .zip (that does not have any motoflash or _update_bl or _update_mb lines in the updater-script!).
Click to expand...
Click to collapse
So, in other words, CM7 is my only option now.
Boohoo.
Dishard said:
So, in other words, CM7 is my only option now.
Boohoo.
Click to expand...
Click to collapse
Not really... What he meant was - you can flash any rom, even stock BUY you must do it via CWM or fastboot. (flashing system and boot partitions only is safe, there's no way you can screw up your bootloader.) Also, be careful with what radios you flash.
Otherwise, cheers on getting it to work.
xploited said:
Not really... What he meant was - you can flash any rom, even stock BUY you must do it via CWM or fastboot. (flashing system and boot partitions only is safe, there's no way you can screw up your bootloader.) Also, be careful with what radios you flash.
Otherwise, cheers on getting it to work.
Click to expand...
Click to collapse
Oh, I was under the impression that I couldn't use any ME860/MB861 based ROM either.
Well, for those Asians that wanted to try it. As long as follow the instructions properly, it can be done!
Hey!
I had CM10.2 on my Defy+, and tried to just follow Quarx simple post:
http://forum.xda-developers.com/showthread.php?t=2515036
I had some trouble with the update recovery (bad zip), reformatted my SD with sdcard.org's official formatting tool, and it worked.
The Quarx website seems to be down, so I downloaded the CM11 rom with the most recent date from http://defy.bytekiste.de/cm11-nightly-defy+/
Which is where I got the update-recovery as well, so I figured that would be fine.
Got a status 7 error (this package is for "MB526" but your device is ""), so I tried fiddling with the verification, editing the rom script (those few lines you have to delete), according to various topics on the status 7 subject. Nothing worked.
People in treads advice different recovery files, so I manually flashed TWRP from here:
http://teamw.in/project/twrp2/91
I rebooted into recovery again, an it just gives a blank (but lit) screen. I can still access the bootmenu, but not recovery, so I guess TWRP doesn't work with my phone. Should have read the comments on that downloadpage I guess... So I went on to find this "goomanager" people are talking about but all I get are dead links, so I tried the ROMManager and TWRPManager apps, but I can't find any reference to Defy+, Jordan or MB526 within those apps when they ask you to select a device.
I'm not an expert, so I was like, lets start all over from scratch to get recovery working again. Any recovery, I don't care. So I went back to:
http://wiki.cyanogenmod.org/w/Insta...alling_bootmenu_.26_the_ClockworkMod_Recovery
Which is what I used for when I bought the phone to get root, bootmenu & recovery through ADB from the windows command line.
I'm trying to follow that to at least recover the ICS recovery which I had, but I'm stuck there as well. When I switch USB from mass storage mode to "tools only", ADB disconnects, and when I leave it in mass storage mode, well, the sdcard is not mounted to the phone so I can't use ADB on it.
Can anyone give me a push in the right direction? Can I restore the update-recovery from Quarx CM11 thread somehow?
So I got adb to function (how, I do not know), ran the stuff here:
http://wiki.cyanogenmod.org/w/Insta...alling_bootmenu_.26_the_ClockworkMod_Recovery
Which gives me Bootmenu 0.6.1 (I had Bootmenu 2.0.0 before?). And it doesn't include a functional recovery, or a functional 2ndinit, so I completely (soft)bricked my phone now :laugh: Both recovery & boot give errors about missing sh scripts.
Soooo... I installed RSD Lite & motorola drivers with the intention of flashing a stock SBF.
http://forum.xda-developers.com/showthread.php?t=1618718
http://forum.xda-developers.com/showthread.php?t=1828639
Dead links, dead links everywhere.... sigh.
okdewit said:
Soooo... I installed RSD Lite & motorola drivers with the intention of flashing a stock SBF.
http://forum.xda-developers.com/showthread.php?t=1618718
http://forum.xda-developers.com/showthread.php?t=1828639
Dead links, dead links everywhere.... sigh.
Click to expand...
Click to collapse
Soooo, are you simply pointing out the fact that the links haven't been updated (or maybe expressing frustration), or are you saying that you didn't find the new location of the sbf files? The links do have a trail that lead to the new location of the sbf files -- yes, you have to go through several pages to get there and then you have to select the specific sbf that you want, but it's there (here for Defy: http://sbf.droid-developers.org/phone.php?device=27 or here for Defy+: http://sbf.droid-developers.org/phone.php?device=28).
Don't forget, these tutorials, as well as most everything on this forum, are written by people who freely (as in free beer) give of their time to help those of us that are less knowledgeable and therefore may not get updated in a timely manner or maybe not updated at all.
JimboN
JimboN said:
Soooo, are you simply pointing out the fact that the links haven't been updated (or maybe expressing frustration), or are you saying that you didn't find the new location of the sbf files? The links do have a trail that lead to the new location of the sbf files
Click to expand...
Click to collapse
Yesterday when I tried it, the whole droid-developers website just gave an Nginx server error, but I'm glad to see it's up again. Gonna load up RSDLite now and give it one last try!
JimboN said:
Don't forget, these tutorials, as well as most everything on this forum, are written by people who freely (as in free beer) give of their time to help those of us that are less knowledgeable and therefore may not get updated in a timely manner or maybe not updated at all.
JimboN
Click to expand...
Click to collapse
I fully realize that, it's mostly frustration with myself and a series of bad actions which led me to lock up my phone further and further with each action. I realized the risk in advance, so luckily I do have a full backup and a backup phone, but it still hurts a bit to see your beloved device dying on the operating table because of your own stupidity.
Sweet victory, I got froyo back at least! Thanks!
Now to tread very carefully...
okdewit said:
Sweet victory, I got froyo back at least! Thanks!
Now to tread very carefully...
Click to expand...
Click to collapse
Glad to hear you were successful.
Yep, know the frustration of my own stupid actions screwing up my phone and when you go to fix it, that don't work right either -- been there & done that.
Sweet victory #2: Now I have CM11 working! :laugh:
(using the SBF flash & the section in the guide for stock to kitkat: http://forum.xda-developers.com/showthread.php?t=2737990)
I've found one BIG culprit in my previous methodology: copying files through motorola phone portal is just plain wrong. I kept getting "bad zip" and other verification errors. Even by using the USB "Mass Storage" option in the stock Froyo rom the files didn't match exactly 1:1, at least not according to the checksums. It took multiple tries to copy the framaroot/2ndinit apk files to the SD card correctly, and the CM rom zip was just plainly impossible to get on there.
So for the rom itself I just mounted through "USB Mount" in TWRP recovery, It's copies way faster as well. I've also used the windows program Teracopy (for CRC checks) instead of the built-in windows explorer file copier. :good:
Thanks a lot for the support, if you had not pointed out that the SBF filehost was working fine again, this nice phone would've been thrown away.
okdewit said:
Sweet victory #2: Now I have CM11 working! :laugh:
(using the SBF flash & the section in the guide for stock to kitkat: http://forum.xda-developers.com/showthread.php?t=2737990)
Click to expand...
Click to collapse
Fantastic! CM11 works better for me than any other rom that i've tried (certainly smoother and probably faster), still has a few bugs but so did all the others. Best of all it's the latest android and can run all the latest apps.
okdewit said:
Even by using the USB "Mass Storage" option in the stock Froyo rom the files didn't match exactly 1:1, at least not according to the checksums. It took multiple tries to copy the framaroot/2ndinit apk files to the SD card correctly, and the CM rom zip was just plainly impossible to get on there.
Click to expand...
Click to collapse
Hmm... That's interesting. I've used USB Mass Storage to do just what you attempted to do without a problem -- good to know as a potential issue.
okdewit said:
So for the rom itself I just mounted through "USB Mount" in TWRP recovery, It's copies way faster as well.
Click to expand...
Click to collapse
Thanks for the tip.
in short: i need the mojo`s stock android rom in a form wich i can flash with twrp!
Hey Guys,
i am new here. i can t undersund why i can t directly write this thread in the mojo dev section where it belongs: http://forum.xda-developers.com/mad-catz-mojo/development
it says i have not enough rights for that - not understundable for me.
to the case:
already from the beginning i had the mojo, i worried becouse there were no recovery system like romanger or twrp available. i worried, if i make me the whole work, with installing configuring apps and system and an error occured, that i will have no posibility to play a working backup back and exact like that, it was comming:
suddenly sixaxis app wasn t working anymore and gave me the error-message: couldn t load hcl-library-something.
i deletet data and cache of this app, deinstalled, reinstalled, still the same proplem. so my worst nightmares came true.
now i had the choice to set the system to factory defaults (not sure if with this the spoken error were fixed) and lose everything and make the whole work again, or forget it and put the mojo to ebay or to look if in the meanwhile a recovery system is available so that i would have the whole work again, but then, through the posibility of recovery i am on the safe side.
so i decide it and i found out that now a twrp was available and and a unoffical cm12 rom:
[ROM][UNOFFICIAL][mojo] CyanogenMod 12 Mad Catz M.O.J.O: http://forum.xda-developers.com/mad.../rom-cyanogenmod-12-mad-catz-m-o-j-o-t2976401
let me say, that i am not a linuxfreak or a nerd. i see me as an enduser. i want to use things only, i don t have the time, nerves and even the intention to be more.
explanation: if you want for example fly to anywhere, you must not know how exact a plain is working, becouse you only want to use it.
so you buy an ticket jump into the plain and thats it.
i say that through i am no expert, i managed to install twrp and i managed to flash the custom rom.
then the problems began. after flashing it seems that i have no root. so i must research an half day to find out that you must hit seven times dev options to give the root setting free. i don t understund why people do this and don t give this information clear out. if anyone is able to install an costum rom, then you must not save him, with trying to hide the posiblity of root! this makes no sense for me.
my problem actual is that i need the stock rom, becouse the only thing i ever wantet was a working recovery system and this i have now.
i only installed the cm12 rom, becouse there was no stock rom, so i have had no choice.
I hope anyone can provide me the orginal mojo stock rom that i can flash it with twrp.
so if possible, please help me.
best regards
p.s.: forgive me my bad english wich isn t my foreign language. my german is much better
[email protected] said:
in short: i need the mojo`s stock android rom in a form wich i can flash with twrp!
Hey Guys,
i am new here. i can t undersund why i can t directly write this thread in the mojo dev section where it belongs: http://forum.xda-developers.com/mad-catz-mojo/development
it says i have not enough rights for that - not understundable for me.
to the case:
already from the beginning i had the mojo, i worried becouse there were no recovery system like romanger or twrp available. i worried, if i make me the whole work, with installing configuring apps and system and an error occured, that i will have no posibility to play a working backup back and exact like that, it was comming:
suddenly sixaxis app wasn t working anymore and gave me the error-message: couldn t load hcl-library-something.
i deletet data and cache of this app, deinstalled, reinstalled, still the same proplem. so my worst nightmares came true.
now i had the choice to set the system to factory defaults (not sure if with this the spoken error were fixed) and lose everything and make the whole work again, or forget it and put the mojo to ebay or to look if in the meanwhile a recovery system is available so that i would have the whole work again, but then, through the posibility of recovery i am on the safe side.
so i decide it and i found out that now a twrp was available and and a unoffical cm12 rom:
[ROM][UNOFFICIAL][mojo] CyanogenMod 12 Mad Catz M.O.J.O: http://forum.xda-developers.com/mad.../rom-cyanogenmod-12-mad-catz-m-o-j-o-t2976401
let me say, that i am not a linuxfreak or a nerd. i see me as an enduser. i want to use things only, i don t have the time, nerves and even the intention to be more.
explanation: if you want for example fly to anywhere, you must not know how exact a plain is working, becouse you only want to use it.
so you buy an ticket jump into the plain and thats it.
i say that through i am no expert, i managed to install twrp and i managed to flash the custom rom.
then the problems began. after flashing it seems that i have no root. so i must research an half day to find out that you must hit seven times dev options to give the root setting free. i don t understund why people do this and don t give this information clear out. if anyone is able to install an costum rom, then you must not save him, with trying to hide the posiblity of root! this makes no sense for me.
my problem actual is that i need the stock rom, becouse the only thing i ever wantet was a working recovery system and this i have now.
i only installed the cm12 rom, becouse there was no stock rom, so i have had no choice.
I hope anyone can provide me the orginal mojo stock rom that i can flash it with twrp.
so if possible, please help me.
best regards
p.s.: forgive me my bad english wich isn t my foreign language. my german is much better
Click to expand...
Click to collapse
try:
ftp://86.54.116.234/pub/software/mojo/
Not sure if it's flashable
gwaldo said:
try:
Not sure if it's flashable
Click to expand...
Click to collapse
i am also not sure if its flashable and i don t want destroy my mojo.
you are the first one, since i startet this threat, who are concern and tried to help.
thank you!
greetings
[email protected] said:
i am also not sure if its flashable and i don t want destroy my mojo.
you are the first one, since i startet this threat, who are concern and tried to help.
thank you!
greetings
Click to expand...
Click to collapse
Hi,
I'm not an andriod expert , and i too have no interest in trashing my mojo.
maybe ask on the dev forum for cm12 thread.
I'm 75% sure it will work :-\
gwaldo said:
Hi,
I'm not an andriod expert , and i too have no interest in trashing my mojo.
maybe ask on the dev forum for cm12 thread.
I'm 75% sure it will work :-\
Click to expand...
Click to collapse
i tried to write there:
i am new here. i can t undersund why i can t directly write this thread in the mojo dev section where it belongs: http://forum.xda-developers.com/mad-...jo/development
it says i have not enough rights for that - not understundable for me.
Click to expand...
Click to collapse
, but its not possible for me and it looks my thread get not moved to the correct section.
maybe someone with an stock mojo can install twrp:
[RECOVERY][mojo] TWRP 2.8.2.0 recovery Mad Catz M.O.J.O. :http://forum.xda-developers.com/mad...overy-twrp-2-8-2-0-recovery-mad-catz-t2973640
make a bakcup of his system with it and give me the rom.
i think this should work.
[email protected] said:
i tried to write there:
, but its not possible for me and it looks my thread get not moved to the correct section.
maybe someone with an stock mojo can install twrp:
[RECOVERY][mojo] TWRP 2.8.2.0 recovery Mad Catz M.O.J.O. :http://forum.xda-developers.com/mad...overy-twrp-2-8-2-0-recovery-mad-catz-t2973640
make a bakcup of his system with it and give me the rom.
i think this should work.
Click to expand...
Click to collapse
You can ask in the cm12 thread
gwaldo said:
You can ask in the cm12 thread
Click to expand...
Click to collapse
thank you! did so.
[email protected] said:
thank you! did so.
Click to expand...
Click to collapse
It's flashable just flash the zip and your back on stock.
Unjustified Dev said:
It's flashable just flash the zip and your back on stock.
Click to expand...
Click to collapse
thats sounds great. thanks!
can you please say me wich file exactly i need from the link?
there are several .zip files
[email protected] said:
thats sounds great. thanks!
can you please say me wich file exactly i need from the link?
there are several .zip files
Click to expand...
Click to collapse
I use MO0205-TS
Unjustified Dev said:
I use MO0205-TS
Click to expand...
Click to collapse
thank you very much! then my problem should to solved.
you also seem to be responsible for the MOJOs twrp-port. also thank you for that!
i was waiting for such an recovery system since i bought the mojo.
now i can work without beeing afraid to have no backup for the worst case.
nice work!
greetings
Unjustified Dev said:
It's flashable just flash the zip and your back on stock.
Click to expand...
Click to collapse
Unable to flash on my end. It's there an update to this?
paulie_gogetit said:
Unable to flash on my end. It's there an update to this?
Click to expand...
Click to collapse
Flash, the remix OS rom first and then flash this rom. It has to do with the partition structure. i was also unable to flash the stock rom after having CM12 on my mojo, but I first flashed remix OS and then was able to flash the stock rom.
I'm now running the stock rom happily and will not go back to any custom roms. The bottom line is that there is just one dev doing custom rom work and while I appreciate his work, It just doesn't seem like any of the custom roms are there yet in regards to stability.
Is there a keyboard sequence to get into recovery? I have bricked my MOJO because I failed to realize that it failed to flash the stock firmware after I wiped it.
(EDIT) I found a solution to the above!
Okay so the method I used to get into recovery is to use the MoDaCo root tool and edit the superboot-windows.bat file and change boot.superboot.img
to twrp-2.8.7.0-mojo.img. Of course you have to have the TWRP image as well to do this. This got me into TWRP, but the following issue still stands.
Okay, I can't seem to get Remix OS or the factory rom to install, CM12 installs fine though, anyone know how to fix this?
Side note:
I have a TWRP backup of my other MOJO but TWRP doesn't see anything when I choose restore, and I have tried choosing internal and SD card for the source to no avail, does anyone know how to get around that? Or is this just a current issue with this version of TWRP on the MOJO?
Please help need mojo stock rom
Hello all some reason my stock rom didn't back up and I've lost it please if anyone can help I need the stock rom for madcatz mojo thank you
konser13 said:
Hello all some reason my stock rom didn't back up and I've lost it please if anyone can help I need the stock rom for madcatz mojo thank you
Click to expand...
Click to collapse
Me too
Sent from my LG-H815 using Tapatalk
Their is a way to get it back to stock
To 1eyedmonster I had left information but I will explain how to do this if you can use ( Firefox internet browser ) you can download the stock frameware from madcatz site where you can find stock 4.2.2 for the m.o.j.o. link to original thread http://forum.xda-developers.com/mad...refox-to-download-madcatz-mojo-4-2-2-t3431587
imseanross1 said:
Is there a keyboard sequence to get into recovery? I have bricked my MOJO because I failed to realize that it failed to flash the stock firmware after I wiped it.
(EDIT) I found a solution to the above!
Okay so the method I used to get into recovery is to use the MoDaCo root tool and edit the superboot-windows.bat file and change boot.superboot.img
to twrp-2.8.7.0-mojo.img. Of course you have to have the TWRP image as well to do this. This got me into TWRP, but the following issue still stands.
Okay, I can't seem to get Remix OS or the factory rom to install, CM12 installs fine though, anyone know how to fix this?
Side note:
I have a TWRP backup of my other MOJO but TWRP doesn't see anything when I choose restore, and I have tried choosing internal and SD card for the source to no avail, does anyone know how to get around that? Or is this just a current issue with this version of TWRP on the MOJO?
Click to expand...
Click to collapse
If you still have issues entering recovery install terminal emulator from play store
Make sure usb debugging enabled in developer options
Then open terminal emulator and enter following commmnds you will need a keyboard for this Then follow these steps
Adb devices (enter)
Adb reboot recovery (enter)
Then you should be in twrp
Hi, I need the ROM for this phone, more specifically, the boot.img file, as the current kernel is for the older, Indian revision of the On5, and my revision, the USA version SM-G550T1, seems not to have any copies of its firmware floating around. I'm running an OS for the SM-G550FY, which has no audio or camera support. Even if the version isn't an exact match, if you bought this phone in the USA, new, in 2016, your boot.img will probably work. I need this kernel guys. Please, if someone has an On5 in the USA, can I please get a copy of your boot.img and possibly system.img? I really care about the boot.img.
Thanks guys
-Subsentient
Firstly, did you try the updated ones at these locations:
http://www.theandroidsoul.com/galaxy-on5-stock-firmware-2-86761/
http://firmwarefile.com/samsung-sm-g550fy
Secondly, why exactly do you need the boot.img, what problem do you think it'll solve? Is there any specific issue with your current ROM that you are trying to solve?
Yes, I did, but as you can see, those are for the SM-G550FY, not my SM-G550T1, and the camera and sound (including phone calls) don't work!
This makes me strongly suspect a driver issue, which could most likely be fixed by getting my hands on a copy of the factory boot.img.
Running Android 6.0.1 right now, compiled for the SM-G550FY, but I can't get it working.
Subsentient said:
Yes, I did, but as you can see, those are for the SM-G550FY, not my SM-G550T1, and the camera and sound (including phone calls) don't work!
This makes me strongly suspect a driver issue, which could most likely be fixed by getting my hands on a copy of the factory boot.img.
Running Android 6.0.1 right now, compiled for the SM-G550FY, but I can't get it working.
Click to expand...
Click to collapse
>> and the camera and sound (including phone calls) don't work!
Did they not work from day one or did they just stopped working after a passage of time or due to rooting or an OTA upgrade? If you didn't root or install a custom ROM, there is just no room for a software/driver issue to happen. Did you try wiping the cache partition and doing a factory reset?
EDIT
In any case, boot partition is the last place you look for actual component issues like camera or sounds. All the boot partition does is just kickstart your android OS and then the control is passed on to the system (as soon as the logo animation starts).
prahladyeri said:
>> and the camera and sound (including phone calls) don't work!
Did they not work from day one or did they just stopped working after a passage of time or due to rooting or an OTA upgrade? If you didn't root or install a custom ROM, there is just no room for a software/driver issue to happen. Did you try wiping the cache partition and doing a factory reset?
EDIT
In any case, boot partition is the last place you look for actual component issues like camera or sounds. All the boot partition does is just kickstart your android OS and then the control is passed on to the system (as soon as the logo animation starts).
Click to expand...
Click to collapse
I did install a custom ROM. None of the ROMs I can find support the camera or audio, not at all, ever.
Subsentient said:
I did install a custom ROM. None of the ROMs I can find support the camera or audio, not at all, ever.
Click to expand...
Click to collapse
There you are! I just cannot emphasize enough that why don't you guys backup your existing ROMs before flashing a new one? It hardly takes five minutes with CWM/TWRP recovery.
In any case, what happens when you flash the Indian ROM (5.1.1)? I guess that could be your only option.
Otherwise, you can put a request on the CyanogenMod thread for your particular Samsung model.
For future reference, perform device backups and all the research before flashing a custom ROM, not after the fact.
EDIT
If you can contact Samsung support, see if you can manage to get a stock ROM from them that you can flash using ODIN or something.
I contacted them already, they basically told me to go **** myself. The missing ROM is a result of bad parameters I accidentally put in to Heimdall/ODIN flasher. I wanted to back up, but ironically, my first attempt at installing TWRP is what destroyed my ROM.
I've downloaded the kernel source code from Samsung and I'll try compiling it myself. If I create a working boot.img, I'll post it here.
prahladyeri said:
In any case, boot partition is the last place you look for actual component issues like camera or sounds. All the boot partition does is just kickstart your android OS and then the control is passed on to the system (as soon as the logo animation starts).
Click to expand...
Click to collapse
boot.img is where the kernel is stored. I know, I decompressed it.
Subsentient said:
boot.img is where the kernel is stored. I know, I decompressed it.
Click to expand...
Click to collapse
You are right, boot.img has the monolithic kernel, however, a lot of drivers are available as separate modules in /system/lib/modules/, so you need to make sure that one is proper too.
In case of Samsung, I think it was probably a mistake to use TWRP/CWM to backup or flash ROMs since they don't tend to work as well with Samsung devices as ODIN/heimdall.
Yes, do post the result of your output once you are done, so its helpful to others.
prahladyeri said:
You are right, boot.img has the monolithic kernel, however, a lot of drivers are available as separate modules in /system/lib/modules/, so you need to make sure that one is proper too.
In case of Samsung, I think it was probably a mistake to use TWRP/CWM to backup or flash ROMs since they don't tend to work as well with Samsung devices as ODIN/heimdall.
Yes, do post the result of your output once you are done, so its helpful to others.
Click to expand...
Click to collapse
The kernel on this device does not have loadable module support. It's entirely monolithic. And, I'm having one hell of a time building a kernel this thing is willing to boot.
I really would love just to get a ROM from someone else's SM-G550T or SM-G550T1.
locked out by frp so i cant even turn on my sm-g550t1 so if you find the rom please let me know
bandtab said:
locked out by frp so i cant even turn on my sm-g550t1 so if you find the rom please let me know
Click to expand...
Click to collapse
I found a copy of the MetroPCS version: https://drive.google.com/file/d/0B_VtvT1vGmlsMjNnR2JvYzk0MFU/view?usp=sharing
You flash this with TWRP recovery, because those are tarballs and can't be flashed with Odin etc.
You flash TWRP for the On5 onto your recovery partition, and then restore from that.
Subsentient said:
I found a copy of the MetroPCS version: https://drive.google.com/file/d/0B_VtvT1vGmlsMjNnR2JvYzk0MFU/view?usp=sharing
You flash this with TWRP recovery, because those are tarballs and can't be flashed with Odin etc.
You flash TWRP for the On5 onto your recovery partition, and then restore from that.
Click to expand...
Click to collapse
thank you!
however, i can't install twrp to my recovery partition anymore because i got FRP locked, and i can't go into my settings to disable it now. so i think my only option really is via odin. i'll see what i can do with this though, thank you very much. i did have twrp on there before but after i got frp locked i can't go into recovery mode at all.
I've been losing my mind trying to make this work.
I think if I installed the stock recovery.img it may work, but I can't find it in the files you sent. Would you or anyone else be able to make a copy of it for me? I would be eternally indebted to whoever could.
If you want to go back to stock then use the official samsung software. I got a s6 tht a friend of mine straight up deleted the rom (idk how they managed that) and it wouldnt take to being flashed in odin. I put it in download mode and provided samsung smart something with all the info it wanted and it installed the stock rom and everything.
holydude92 said:
If you want to go back to stock then use the official samsung software. I got a s6 tht a friend of mine straight up deleted the rom (idk how they managed that) and it wouldnt take to being flashed in odin. I put it in download mode and provided samsung smart something with all the info it wanted and it installed the stock rom and everything.
Click to expand...
Click to collapse
unfortunately smart switch is incompatible with this model phone for the time being.
I got four of these from T-Mobile when we switched from Verizon ($120 for 4 lines). Three of our Verizon phones worked well on T-Mobile (after a few APN tweaks), but my dad's old Galaxy S3 barely worked at all, and when it did, only got Edge for data. So I set one of the On5 phones up for him.
Everything was going great. I put the TWRP recovery on it, rooted it, froze all the bloatware, and backed up/restored his apps from the old S3. However, he wanted me to see if I could restore all his SMS/MMS. I tried restoring that, and the stock Messaging app started FC'ing. I installed Textra, which worked (and saw the old messages), but he never received new texts (even though he could send). So I tried removing Messaging and Textra, as well as the SMS cache (which seemed to be in "Dialer Storage (Phone SMS/MMS). I removed it, but now I'm getting an error every five seconds about "com.android.phone" and can't seem to get rid of it. I tried to restore the dialer storage backup again, but it just seems to sit forever without installing.
I've looked far and wide for a stock ROM... hoping I could just put this mess behind me, but I'm surprised to find it is nowhere to be found.
My other alternative would be to fix the com.android.phone error, but nothing seems to fix it.
Which cynogenmod or any custom os suits for Samsung Galaxy on 5.......please tell me guys.....I am bored with this official os
I was really hoping to come back to this forum and finally see stock ODIN files for this phone. I really, really want to get rid of the MetroPCS ROM I used to fix it.
Has anyone been able to find it?