I have read many posts, and did many tries.........we all know that Froyo ver that is out, is not a official one. In order to get Official OTA update, our phones must be in complete factory stage. Unlocked boot-loader is not an issue. Trust me, i tried many different ways to "unroot" my N1. Following many "how to's" uproot your N, in order to get OTA (Froyo), all tries have failed. I was flashing original roms (ERD79), replaced recovery image, and then i GOT an OTA with 2.1-update1, no sweat! Then, when it tried to install, there was an error every time. I was able to install that (ER27) update manually, but it was NOT the thing i wanted to accomplish. I knew that i will be able to receive next OTA with ver 2.2 (Froyo), but i also knew that this update will NOT install either. The problem is a recovery image! After been running many different custom roms, i have decide to try again to go back to the state from the beginning, so i can be sure i can be able to install official Froyo, when it is out. I was afraid to do this, but i did it anyway.............and it was successful. I restored my Nexus to the original state (except boot-loader of course), and after i got back to ERD79, momentarily i got OTA with ver 2.1-1. But this time, it has installed with no problem!!! I am running it right now, waiting for next (2.2) OTA update.
Ok, here we go:
Just go there and grab Google OEM file (PASSIMG.zip). Put it on your SD card (root dir).
Then restart your phone into boot-loader (trackball+power button).
Once there, top power button again. It will look for passimg file as always. It will load the passimg file. Note the blue status bar at right-upper corner of your screen.
Then, it will check that file, and finally you will see "do you want to start update?"
Press Volume UP, for YES............and wait.
After phone reboots - you are done! Completely back to stock!
Then you can go to "menu-settings-about-system updates" and you should see that your phone is already downloading update 2.1-1.
That is it.
If for some reason you end up with android screen with triangle and exclamation mark, just press VOL up and Power, at the same time, you will get into recovery screen, and reboot your phone from there.
One more thing...........i did that in my own risk
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So, please do not blame me, if something would happen to you Nexus (phone just exploded, or something....
)
Wow..can't get any simpler than that..thx for this.
Thanks. Very simple.
this effectively make it so that if you root your phone and void the warranty you can unroot and regain your warranty?
This might be totally unrelated, but I finally just rooted my phone a few hours ago, so I'm a noob. I created a nand backup of my factory install. Then I installed cyanogen and some apps, then did another nand backup and think I wiped my factory nand backup. I wanted to keep that. Is there anyway I can get my factory image back for future use? How do you save a new nand backup as a different file name so this won't happen? I don't see how to do this...thanks.
-------------------------------------
Sent via the XDA Tapatalk App
Wow... Much appreciated!
laughter95 said:
this effectively make it so that if you root your phone and void the warranty you can unroot and regain your warranty?
Click to expand...
Click to collapse
Nope. Even if you unroot your phone, your bootloader cannot be locked back again (if you unlocked it). Rooted or not, if your bootloader was unlocked, you always get that unlocked padlock image on your first screen when you turn on your phone. However, I read somewhere that someone has sent his phone back for warranty exchange, after he revert everything to factory stage (except bootloader of course) and they (HTC) accepted. I don’t know how that happened...maybe they (HTC) overlooked that first screen??
As far as I know...this thread is total BS.
You CANT revert to a previous version of Android going through the bootloader's update.
You MUST pick up a stock (I did with a stock Froyo's) Nandroid backup and restore it from Amon's recovery. You'll lose root and your recovery will revert to stock anyway.
justclimb said:
As far as I know...this thread is total BS.
You CANT revert to a previous version of Android going through the bootloader's update.
You MUST pick up a stock (I did with a stock Froyo's) Nandroid backup and restore it from Amon's recovery. You'll lose root and your recovery will revert to stock anyway.
Click to expand...
Click to collapse
HA ha ha! You did NOT understand what i wrote! Read it again....and what if one does NOT have a Nan backup at all??
" You MUST pick up a stock (I did with a stock Froyo's) Nandroid backup and restore it from Amon's recovery. " <= that's total BS!!
Would this work on the AT&T N1?
RogerPodacter said:
This might be totally unrelated, but I finally just rooted my phone a few hours ago, so I'm a noob. I created a nand backup of my factory install. Then I installed cyanogen and some apps, then did another nand backup and think I wiped my factory nand backup. I wanted to keep that. Is there anyway I can get my factory image back for future use? How do you save a new nand backup as a different file name so this won't happen? I don't see how to do this...thanks.
Click to expand...
Click to collapse
Creating multiple nand backups doesn't overwrite the previous one. It creates a new folder each time, with the timestamp as the folder name. Unless you specifically went into your sd card and deleted the folder containing the first nand backup, it's still there If you click Restore in Recovery, you'll be given a list of all the backups you created.
And you can always go back to the factory image using the ROM here: http://forum.xda-developers.com/showthread.php?t=614850
This might be totally unrelated, but I finally just rooted my phone a few hours ago, so I'm a noob. I created a nand backup of my factory install. Th
Click to expand...
Click to collapse
Creating multiple nand backups doesn't overwrite the previous one. It creates a new folder each time, with the timestamp as the folder name. Unless you specifically went into your sd card and deleted the folder containing the first nand backup, it's still there If you click Restore in Recovery, you'll be given a list of all the backups you created.
And you can always go back to the factory image using the ROM here: http://forum.xda-developers.com/showthread.php?t=614850
Click to expand...
Click to collapse
Awesome good to know. But when I went into restore I only saw one file. But maybe I just needed to click into that and would have seen 2 restore files.
RogerPodacter said:
Awesome good to know. But when I went into restore I only saw one file. But maybe I just needed to click into that and would have seen 2 restore files.
Click to expand...
Click to collapse
Yeah, it should be something like "HTP123990" which is your device number. Click once more and it'll show all the backups for that device.
Or just browse your SD card to the nandroid folder with a file manager like Linda:
wow thanks! it's so easy to use..and works!
i had so many problems with the froyo 2.2..though i really LOVE the speed and the new interface...but afterwards decided to switch back to 2.1 wait for official OTA...
thanks op!
shouldnt the name of this thread be "from FROYO to stock" not "from ROOT to stock"? because this has nothing to do with root, its just going from froyo back to shipping rom.
http://forum.xda-developers.com/showthread.php?t=686593
Well coming from a rooted MoDaCo rom, I performed the steps and am now running the stock ROM and just been informed that there is an update available. Update is installing now and it works great.
Now I have my stock OS back while still rooted, and getting updates.
I just recently got my Nexus one a few days before Froyo hit. I've been sporting Froyo while traveling and getting barely any coverage. So this is a good test.
I'm on Fringe coverage now. With Froyo and its radio, I kept getting network disconnects. Flashing back to stock+update = 2/3 bars of EDGE.
Finally!
RogerPodacter said:
shouldnt the name of this thread be "from FROYO to stock" not "from ROOT to stock"? because this has nothing to do with root, its just going from froyo back to shipping rom.
Click to expand...
Click to collapse
It's the fastest way to reload stock recovery/image/radio altogether.
Not true. I can confirm the method in this thread.
justclimb said:
As far as I know...this thread is total BS.
You CANT revert to a previous version of Android going through the bootloader's update.
You MUST pick up a stock (I did with a stock Froyo's) Nandroid backup and restore it from Amon's recovery. You'll lose root and your recovery will revert to stock anyway.
Click to expand...
Click to collapse
If i use mybackup pro to backup apps and data, how do I restore that stuff once I'm unrooted? Do you have to redownload mybackup pro? Sorry if this is obvious to some, I'm new to android and really want to be able to get the OTA update. Basically I'm wondering how the people that have used this method got all their info and apps back, Thanks.
Related
Smart people of XDA Developers
I am experiencing a problem with connecting to my phone with fastboot.
I have a Nexus S which seems to be running a custom or developer build, currently marked as Android Version 2.4
drivers are successfully installed on windows xp (had to use the PDAnet work around) but when I try to do "fastboot oem unlock" I just get the message <waiting for devices> and it sits there forever. doing a "fastboot devices" shows nothing connected.
here is the kicker, it already says LOCKED STATE - UNLOCKED (got the device like this) but without the option to send the recovery image i am unable to do anything.
also, the device isnt rooted.
if you could provide any help that would be amazing, really want to get this sorted so I can put a custom rom on it, even if there is some way that I can get it back to Android 2.3
and how did you get this so-called "developer build?"
I somehow doubt you have 2.4
I work for a mobile company, we receive handsets from the operators to use for QA
Also, attached is a screenshot with the firmware details. I'm pretty sure it isnt real 2.4 either but some sort of developer build left on the phone.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Hmm.. its very easy to change the Android version.
Baseband version is definitely something new. Samsung does radios based on the month using letters (XXJK8 -> XXKB1 -> XXKB3.. never seen JL3).
So what is it that you're attempting to do? Restoring back to Android 2.3? If so.. what version? Stock? Custom ROM?
Also.. this is probably against your principles of a employee or whatever but a nandroid backup of that so-called developer build would be interesting to take a look at. And possibly a dump of the radio.
zephiK said:
Hmm.. its very easy to change the Android version.
Baseband version is definitely something new. Samsung does radios based on the month using letters (XXJK8 -> XXKB1 -> XXKB3.. never seen JL3).
So what is it that you're attempting to do? Restoring back to Android 2.3? If so.. what version? Stock? Custom ROM?
Also.. this is probably against your principles of a employee or whatever but a nandroid backup of that so-called developer build would be interesting to take a look at. And possibly a dump of the radio.
Click to expand...
Click to collapse
ideally I want to get to 2.3.3 and use cyanogenmod on the phone, plus rooted obviously. I just switched to this from the Moto Defy and while the phone is nice, not being rooted is a bit of a pain in the ass tbh.
yes that might be a bit of a grey area, but I will have to see.
Uninstall the drivers you have installed right now and install the ones linked below:
Follow the rooting process here: http://forum.xda-developers.com/showthread.php?t=895545
Get Drivers here: http://forum.xda-developers.com/showthread.php?t=878786&highlight=Driver
Make a 2.4 stock ROM for us.
Sent from my Nexus S using XDA Premium App
deez1234 said:
Make a 2.4 stock ROM for us.
Sent from my Nexus S using XDA Premium App
Click to expand...
Click to collapse
all hes gotta do is make a nandroid backup and upload it :|
a dump of the radio would be cool too... if its legit
Thanks for the links zephiK, I was following that root guide before, but will try those drivers on my windows 7 machine when I get home.
will also see what I can sort out in terms of a backup of the 2.4
do I also use nandroid to do a dump of the radio?
Yea if its legit that would be kinda swwweeeet. We would have a new toy to mess around with!
Sent from my Nexus S using XDA Premium App
zephiK said:
all hes gotta do is make a nandroid backup and upload it :|
a dump of the radio would be cool too... if its legit
Click to expand...
Click to collapse
Agreed. Its not that I have a particular issue with the OP, I'm just weary of anyone claiming to have test builds given that you can make the build.prop say pretty much anything you want it to say.
HowlinMadMurdoc said:
Thanks for the links zephiK, I was following that root guide before, but will try those drivers on my windows 7 machine when I get home.
will also see what I can sort out in terms of a backup of the 2.4
do I also use nandroid to do a dump of the radio?
Click to expand...
Click to collapse
Nandroid backups dont flash radios. I'll have to find the steps to make a backup of the radio
And yeah. I'm just somewhat believing it because the build number and radio are different.
The radio is something I've never seen before. I don't remember how Samsung fully does their radios if someone could clarify it. (KB3 vs. JL3) I used to remember but I forgot. Regardless if JL3 vs. KB1/KB3 are newer, it would be nice to at least get the radio and compare speeds to see which would be faster. More basebands to try out.. the better right?
If OP did decide to trick us, he definitely put a LOT of effort into doing it by changing the baseband and all that. I just don't think anybody would have that much time to change all that.
Yea kenvan, that's my concern as well.
Sent from my Nexus S using XDA Premium App
Hey its fair enough of you guys to be suspicious but really I didn't make this thread to show off but to get help with rooting and putting a custom rom on the handset, I posted the details about the android version because I have a feeling its the reason why I am having problems and if anyone can help me its the xda guys. I don't post much but I have been lurking for years using the guides and info on here.
Heading home now so ill try zephik's advice, if anyone else has some ideas I will appreciate it. I will also look into doing a nandroid backup for you guys. My main priority is just to get a rooted PHone I can put custom roms on
zephiK said:
Also.. this is probably against your principles of a employee or whatever but a nandroid backup of that so-called developer build would be interesting to take a look at. And possibly a dump of the radio.
Click to expand...
Click to collapse
hey zephiK, looks like those drivers worked brilliantly on my home PC! thanks for your help.
got clockwork on fine and superuser.
how with regards to nandroid, im reading through the procedure but I just dont know where to start?
HowlinMadMurdoc said:
hey zephiK, looks like those drivers worked brilliantly on my home PC! thanks for your help.
how with regards to nandroid, im reading through the procedure but I just dont know where to start?
Click to expand...
Click to collapse
It is pretty easy, flash cwm (in the root guides) then select backup & restore, then select 'backup'
It will take a while, then you can boot & take the nandroid off of your phone.
HowlinMadMurdoc said:
hey zephiK, looks like those drivers worked brilliantly on my home PC! thanks for your help.
got clockwork on fine and superuser.
how with regards to nandroid, im reading through the procedure but I just dont know where to start?
Click to expand...
Click to collapse
boot into recovery than perform a backup. thats a "nandroid" backup. backup everything.
You can do the Nandroid in Clockwork recovery. It should make a backup stored to the SD which you can upload. It wont help us much as far as flashing since we don't have a backup of the newest radio, but at least we can look into it until we can find a way to grab the radio.
HowlinMadMurdoc said:
hey zephiK, looks like those drivers worked brilliantly on my home PC! thanks for your help.
got clockwork on fine and superuser.
how with regards to nandroid, im reading through the procedure but I just dont know where to start?
Click to expand...
Click to collapse
If you have clockwork recovery already you are 90% of the way there.
Boot into recovery: With phone turned off, press and hold the power button and volume down at the same time. The fastboot screen will show up. Scroll down to recovery and press the power button to select. You will boot into recovery.
On the recovery screen, scroll down to backup/restore and hit the power button. On the next screen select "backup" by hitting the power button. Wait for the backup to complete.
Next plug your phone into your computer via usb. In the recovery menu, scroll down to storage and mounts and select that. Then scroll down to and select "mount usb storage". You should be able to see your phone mounted on your computer now. Find the clockworkmod folder, then the backup folder. Copy and paste the backup you just made (check the time stamp) onto your computer. Upload that file to somewhere we can download it (dropbox, mediafire etc.)
This is exciting.
I should of published this notice sooner. This was discussed early on, but we didn't think anyone would downgrade to the buggy firmware after rooting.
We were wrong.
Newer hboots (like the one in stock, hboot version 1.04.0000) flash/check images in an way that prevents the phone from encountering a SECURITY WARNING mid flash. This is good, prevents us from bricking.
Older hboots, like the one in 1.03.605.10 (hboot version 0.95.0000) on the otherhand do not, and flashing over custom firmware with them can lead to the dreaded SECURITY WARNING. This firmware is from January 3rd, is buggy and well should not be used for any reason outside of initail root. Avoid it.
A tester helping develop a one click root encountered this today, he tried to downgrade from custom firmware.
So, do not downgrade below 1.12.605.6 without a reason, if you do understand how to recover. You most likely have no reason to be on old firmware at this point, outside of initial root.
If you have a SECURITY WARNING, don't freak.
Recovering from this error:
Until we have newer RUUs, you only have one maybe two chances to do this. Since you obviously know how to flash an RUU, I am not going to go through the
process again.
Flashing this firmware the stock (1.12.605.6) firmware will fix this error.
LINK: http://www.multiupload.com/JWLPZAS15T
However if you get a MAIN VERSION HIGHER error while flashing, you only have one choice to recover, by flashing the newer than stock (1.12.605.9) firmware.
LINK: http://www.multiupload.com/UF40S2HZA7
If you are having issues, or are freaked out come find me in the chat (check my signature for a link). If I help you, I expect a donation to the Boys and Girls Club in the name of REWT.
-jcase
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
bumpity bump!
hello there i got the exact thing on my TB and i downloaded the files to fix it but i get back a Main Version Older am i doin somethin wrong
you can only flash files that are newer than your firmware. what were you trying to flash,overtop of what, when you got this security warning?
scotty1223 said:
you can only flash files that are newer than your firmware. what were you trying to flash,overtop of what, when you got this security warning?
Click to expand...
Click to collapse
i was trying to flash this [ROM][TH3ORYROM] SHIFTAO5P V1.2X [AOSP/CM7] Eclipse B5 Kernel (8/26/2011) but when i was trying to flash the radio, i wasnt getting any receptions and i tried all four radio listed, so my stupid self thinkin hey let me use the radio PM05IMG from the root process and see if that would work, well as soon as the bootloader started flashin the files it pop back into bootloader with the security warning, i tried the file the jcase said to use to get out of that problem but the file never open or go thru it come back saying Main Version Older file not updated.
"Main version higher" means that the firmware you're trying to flash is older than the firmware on the phone.
Have you tried both files above? If so,the next thing I would do is try and flash the mr2 ruu(1.70.605.0) it is newer than both files above,and both of the root files(downgrade and mr1 upgrade) so that one should work for you.
Afterward,you can run revolutionary to reroot and not encounter this prollem again when you flash something that you should have researched more before flashing.
Sent from my SHIFTAO5P using XDA Premium App
scotty1223 said:
"Main version higher" means that the firmware you're trying to flash is older than the firmware on the phone.
Have you tried both files above? If so,the next thing I would do is try and flash the mr2 ruu(1.70.605.0) it is newer than both files above,and both of the root files(downgrade and mr1 upgrade) so that one should work for you.
Afterward,you can run revolutionary to reroot and not encounter this prollem again when you flash something that you should have researched more before flashing.
Sent from my SHIFTAO5P using XDA Premium App
Click to expand...
Click to collapse
Hey there Scotty i really appreciate you helping me out here, im sitting at work with my TB stuck in Bootloader, getting ready to bust out my old rooted Eris out, but ima go and try that MR2 RUU do you have a link to where i can download that. and also where you said Main Version Higher mines Said Main Version Older,
and yes i thought i did everything correctly i mean i guess since i had the rom flashed but wasnt getting any reception made me make the stupid mistakes, by the way scotty do you have a tb
i have never seen "main version older" but it means the same thing... the firmware youre trying to flash is older that what is on the phone.
you can download MR2 from here: http://forum.xda-developers.com/showthread.php?t=1160286
just put your sd card in a cardreader to transfer and rename PG05IMG and flash in hboot. let us know how it goes.
and yes,i have a TB.
scotty1223 said:
i have never seen "main version older" but it means the same thing... the firmware youre trying to flash is older that what is on the phone.
you can download MR2 from here: http://forum.xda-developers.com/showthread.php?t=1160286
just put your sd card in a cardreader to transfer and rename PG05IMG and flash in hboot. let us know how it goes.
and yes,i have a TB.
Click to expand...
Click to collapse
Ok ima download it but my other prblem is that the phone doesnt charge the battery its not enough voltage to run the files, i have no other way of charging the phone i might have to buy a battery charger or somethin
only thing i know of is to use an external charger,or swap it into a good TB. if you have to,you could take it to a store and see if they will put it in a phone and charge it for you,tho i would take some care in what you tell them as to why you need to do that
i got an external charger and 3 extra generic batterys on ebay for about $30 so i wont ever ben in that situation. i dont like charging my phone during the day so i just go until it shuts off then put in a new battery.
ive heard of people hacking up usb cables to directly power the phone,but thats not something id really reccomend.
at any rate youre good to be caustious,an hboot flash is NOT a time that you want to run out of battery
take an old pair if headphones and strip them til you have only the cooper wire and connect them to the gold connector from your phone to your eris battery and that should work
scotty1223 said:
only thing i know of is to use an external charger,or swap it into a good TB. if you have to,you could take it to a store and see if they will put it in a phone and charge it for you,tho i would take some care in what you tell them as to why you need to do that
i got an external charger and 3 extra generic batterys on ebay for about $30 so i wont ever ben in that situation. i dont like charging my phone during the day so i just go until it shuts off then put in a new battery.
ive heard of people hacking up usb cables to directly power the phone,but thats not something id really reccomend.
at any rate youre good to be caustious,an hboot flash is NOT a time that you want to run out of battery
Click to expand...
Click to collapse
Ok so today i brought an HTC dock charger with a extra slot to charge the battery alone, so i charge that puppy up, put the battery back in with the file you gave me to put on my sd card and bootloader comes on does its checking the file and loaded the update ask me to press yes and BAM it took 5 mins to do its process and rebooted itself and now back to where it was when i first brought it, damn so thx you Scotty for the help and guide, so can youo tell me a method to use to root it back,
good,glad it worked out for you. use this to reroot: http://revolutionary.io/
its quick and easy and leaves you with a permanet hboot that wont accidentally get overwritten
scotty1223 said:
good,glad it worked out for you. use this to reroot: http://revolutionary.io/
its quick and easy and leaves you with a permanet hboot that wont accidentally get overwritten [/QUOTED]
do i need my pc to do this root process or i can do it on the phone.
Click to expand...
Click to collapse
portebr3 said:
do i need my pc to do this root process or i can do it on the phone.
Click to expand...
Click to collapse
you will need a pc
scotty1223 said:
you will need a pc
Click to expand...
Click to collapse
Ok ill need a pc, how will i know im rooted will it give me the superuser app like the other root method does
theres a video here on android forums: http://androidforums.com/thunderbolt-all-things-root/402115-thunderbolt-rooting-methods-updated.html
it will give you a permanent s-off hboot and flash clockwork recovery. tehre is a download for a superuser.zip that you will flash in recovery. then you will see the superuser app in your drawer after flashing that .zip/
scotty1223 said:
theres a video here on android forums: http://androidforums.com/thunderbolt-all-things-root/402115-thunderbolt-rooting-methods-updated.html
it will give you a permanent s-off hboot and flash clockwork recovery. tehre is a download for a superuser.zip that you will flash in recovery. then you will see the superuser app in your drawer after flashing that .zip/
Click to expand...
Click to collapse
ok Ima go go ahead and go that route and i think i should be able to download superuser from the app store, but yeaha ill keep you posted, so tell me what ROM are you using, i heard gingerbread is buggy as hell,
portebr3 said:
ok Ima go go ahead and go that route and i think i should be able to download superuser from the app store, but yeaha ill keep you posted, so tell me what ROM are you using, i heard gingerbread is buggy as hell,
Click to expand...
Click to collapse
the market will only have the superuser app,youll need the matching binary files. the superuser app is linked on revolutionarys page,you must flash that in recovery to become rooted.
from: the revolutionary website:
Does Revolutionary give me root?
No. You will need to flash this this zipfile from recovery.
jcase said:
I should of published this notice sooner. This was discussed early on, but we didn't think anyone would downgrade to the buggy firmware after rooting.
We were wrong.
Newer hboots (like the one in stock, hboot version 1.04.0000) flash/check images in an way that prevents the phone from encountering a SECURITY WARNING mid flash. This is good, prevents us from bricking.
Older hboots, like the one in 1.03.605.10 (hboot version 0.95.0000) on the otherhand do not, and flashing over custom firmware with them can lead to the dreaded SECURITY WARNING. This firmware is from January 3rd, is buggy and well should not be used for any reason outside of initail root. Avoid it.
A tester helping develop a one click root encountered this today, he tried to downgrade from custom firmware.
So, do not downgrade below 1.12.605.6 without a reason, if you do understand how to recover. You most likely have no reason to be on old firmware at this point, outside of initial root.
If you have a SECURITY WARNING, don't freak.
Recovering from this error:
Until we have newer RUUs, you only have one maybe two chances to do this. Since you obviously know how to flash an RUU, I am not going to go through the
process again.
Flashing this firmware the stock (1.12.605.6) firmware will fix this error.
LINK: http://www.multiupload.com/JWLPZAS15T
However if you get a MAIN VERSION HIGHER error while flashing, you only have one choice to recover, by flashing the newer than stock (1.12.605.9) firmware.
LINK: http://www.multiupload.com/UF40S2HZA7
If you are having issues, or are freaked out come find me in the chat (check my signature for a link). If I help you, I expect a donation to the Boys and Girls Club in the name of REWT.
-jcase
Click to expand...
Click to collapse
all multiupload.com links are non-functional and should be disabled, and refreshed with current mirror links.
[GUIDE] Comprehensive "Rooted Android 2.3.4 with unlocked bootloader" instructions
This is a guide on how to go from Froyo to rooted Gingerbread. Also, I'm on AT&T. Others beware. I take no responsibility if you hard or soft brick your phone.
I went from a rooted install running Gingerblur v4.5, but this will likely work regardless of what you have installed, since fastboot overwrites everything.
I didn't actually discover or develop any of this, but I figured someone might like to have a comprehensive guide, instead of searching through 500 different threads like I did.Known/potential issues:
- Fingerprint scanner not functional False alarm
- Avoid using RSDLite for *anything* if you installed the OTA 2.3.4 build
- Battery reading is sometimes inaccurate
- If you have a limited RAM issue, read here http://forum.xda-developers.com/showthread.php?t=1169409Step 0 - BACK UP EVERYTHING. Use Titanium backup, or just copy everything off your phone, whatever. This will leave you with an unlocked, rooted, but otherwise stock Motorola phone. Once this is done, set your USB mode to "None"
Step 1 - Install moto drivers
For x64 windows, use these: http://forum.xda-developers.com/attachment.php?attachmentid=634880&d=1308872277
For x32, http://www.multiupload.com/QNFILE4F07 (I havent tested these, I run Win7 x64)
Step 2 - Unlock your bootloader Note: some have hard bricked using RSDLite to install 1.8.3 over 4.5.91. Read warning here: http://forum.xda-developers.com/showthread.php?t=1160408
Download latest moto-fastboot from here: http://forum.xda-developers.com/showthread.php?t=1138092 *the win32 version worked for me, and I run 64bit windows 7*
Follow instructions here: http://briefmobile.com/how-to-unlock-the-atrix-4g-bootloader
Step 3 - Flash stock Gingerbread image (you can do this without restarting your phone from the unlock bootloader step)
Follow instructions here: http://forum.xda-developers.com/showthread.php?t=1163342
Step 4 - Flash CWM Recovery
Instructions here: http://forum.xda-developers.com/showthread.php?t=1138541
Step 5 - Install root
Instructions here: http://forum.xda-developers.com/showthread.php?t=1159572
Note: I used my phone's USB Mass Storage mode to put the .zip on my external SD card. To get to recovery mode, shut down the phone. Then hold the power and volume up buttons until you see "fastboot." Use the volume down key to cycle through until you see "Android Recovery" then press volume up again. This will get you into the CWM environment, where you can navigate the menus to install the root .zip.
Step 6 - Restore your stuff
Now you should have a factory fresh Gingerbread / MotoBlur installation (didn't you miss the bloat?), with the addition of the superuser app. For tethering, I use Barnacle (requires root). I used Titanium Backup to uninstall any apps I don't want (anything beginning with AT&T, Blockbuster, Y!, etc.) and to reinstall all of my apps.
Feel free to make any corrections, or ask questions. Hopefully someone finds this useful. All credit to the OP of each thread I linked to.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Nice for you to localize everything, ATT users will be grateful.
I went from a rooted install running Gingerblur v4.5, but this will likely work regardless of what you have installed, since fastboot overwrites everything.
Click to expand...
Click to collapse
Does this include the official 4.5.91? So many warnings about hard bricking since people flashed it.
From what I can tell, hard bricking only occurs when you use RSDLite to flash an older motorola SBF once you've gone to gingerbread. But someone else should chime in on that one - I never got a notice for an OTA update.
humjaba said:
From what I can tell, hard bricking only occurs when you use RSDLite to flash an older motorola SBF once you've gone to gingerbread. But someone else should chime in on that one - I never got a notice for an OTA update.
Click to expand...
Click to collapse
I didn't either. I downloaded a .zip and installed via stock recovery from a thread in the General Atrix forum.
Deggy said:
Does this include the official 4.5.91? So many warnings about hard bricking since people flashed it.
Click to expand...
Click to collapse
Nope, this one is the completely safe one.
Kennethpenn said:
"These are completely safe to flash. They don't mess with your bootloader like the OTA or SBF."
In the thread.
Magnetox said:
Nope, this one is the completely safe one.
Kennethpenn said:
"These are completely safe to flash. They don't mess with your bootloader like the OTA or SBF."
In the thread.
Click to expand...
Click to collapse
Just to clarify. I can NOT proceed to unlock my BL. Is that correct?
Deggy said:
Just to clarify. I can NOT proceed to unlock my BL. Is that correct?
Click to expand...
Click to collapse
What firmware did you flash? Can you link me to the thread you downloaded from?
Magnetox said:
What firmware did you flash? Can you link me to the thread you downloaded from?
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=1159604
Deggy said:
http://forum.xda-developers.com/showthread.php?t=1159604
Click to expand...
Click to collapse
Ah you have the deadly firmware
You simply cannot use RSD to flash down to 1.83 or 1.26 etc.
Or you will brick.
Clarify in Q&A, make your own thread with your question.
Taken from this thread kennethpenn said:
"What if I already flashed the official 4.5.91?
If you flashed the official update from XDA or by downloading through a dev-blur server (note: this excludes this ROM), you should avoid flashing SBF files in RSD Lite. We've confirmed this problem exists when users flash the 1.8.3 build specifically. It may happen with other SBF files, though."
So it looks like you can flash 2.3.4 builds via CWM. But double check by asking in Q&A.
Check out this thread.
http://forum.xda-developers.com/showthread.php?t=1163009
Fruit cakes basically dont touch your bootloader, they're basically modified sbf files that only contain the needed files to flash stuff. There's a 1.8.3 fruitcake in there as well as a 2.3.4 fruitcake.
An HKTW fruitcake is in development.
Fruitcake is the .sbf equivalent file that is flashable via CWM.
The big question is this - can you RSDflash the unlocked bootloader SBF by itself once you have the firmware of death? Once you have the bootloader unlocked, everything is gravy.
I don't know the answer
theres the moto-fastboot file i was looking for!
much appreciated.
Now there's a guide
I just did this like 3 hours before this guide came out. Though it at least seems like I was going to all the right threads that are in this guide anyways.
humjaba said:
The big question is this - can you RSDflash the unlocked bootloader SBF by itself once you have the firmware of death? Once you have the bootloader unlocked, everything is gravy.
I don't know the answer
Click to expand...
Click to collapse
From my understanding, if you flashed the official firmware of death you CANNOT use RSD in any way. All of your flashing has to be done via CWM and fruitcakes. Full .sbfs will brick your phone. Hard brick. As in #@$% ME hard brick.
humjaba said:
Step 6 - Restore your stuff
Now you should have a factory fresh Gingerbread / MotoBlur installation (didn't you miss the bloat?), with the addition of the superuser app. For tethering, I use Barnacle (requires root). I used Titanium Backup to uninstall any apps I don't want (anything beginning with AT&T, Blockbuster, Y!, etc.) and to reinstall all of my apps.
Click to expand...
Click to collapse
Weren't there some reports of issues restoring via TB after flashing Ken's beta 4.5? I'd have to search through his thread, but I thought it presented an issue or two.
So I guess no sweet Roms for me. Still haven't found a good thread to root my phone. I'm not sure if the FOD would mess with the rooting part of it.
SoberGuy said:
Weren't there some reports of issues restoring via TB after flashing Ken's beta 4.5? I'd have to search through his thread, but I thought it presented an issue or two.
Click to expand...
Click to collapse
I chose the batch "Restore missing apps with data" option from Ti Backup and it worked flawlessly.
humjaba said:
I chose the batch "Restore missing apps with data" option from Ti Backup and it worked flawlessly.
Click to expand...
Click to collapse
Perhaps it was settings then and not apps. Appreciate the information. I'll be doing that tonight
after i unlocked the bootloader
i flashed CWM
then i use CWM to flash 2.3.4 GB beta 4 zip from kenn
i like it better my way
This is a rough guide to help you upgrade your Bell phone to 2.3.4. This has been tested and it works.
*Usual disclaimer: I am not responsible for any damage to your phone.
This isn't detailed but should be enough to get you going.
You must have a Bell phone and your bootloader must be unlocked. Assume you will lose all data and BACKUP!!
1) Restore Bell System
Use NFHimself's GobStopper CWM zip to restore your phone to stock Bell 2.2.2 - at this link:
http://forum.xda-developers.com/showthread.php?t=1185171
2) Install 2.3.4 and root
- Download 2.3.4 zip from this link and copy to your sdcard:
http://forum.xda-developers.com/showthread.php?t=1166362
- Download root cwm zip from this link and copy to your sdcard:
http://forum.xda-developers.com/showthread.php?t=1159572
- Install edgan's kernel if you have d100 device
http://forum.xda-developers.com/showthread.php?t=1173225
- Install faux's d1100 kernel if you have d1100 device
http://forum.xda-developers.com/showthread.php?t=1156040
- Install CWM Recovery (attachment on first post):
http://forum.xda-developers.com/showthread.php?t=1185171
- go into CWM Recovery and install 2.3.4 zip from sdcard
- install Root zip from sdcard
Done!
Thanks to NFHimself, MagentoX , y2whisper and everybody who helped with this.
Plemen, thank you for your help so far. I have done everything you mentioned, and once I get to CWM installing the 2.3.4 over the Bell 2.2.2 (which I used NFHimself's script to get back to) I get the following error.
Any ideas? (Please see attached image)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
awryter said:
Plemen, thank you for your help so far. I have done everything you mentioned, and once I get to CWM installing the 2.3.4 over the Bell 2.2.2 (which I used NFHimself's script to get back to) I get the following error.
Any ideas? (Please see attached image)
Click to expand...
Click to collapse
I've had this error while upgrading and it was because the base ROM on the phone isn't "Bell enough".
Did you flash the French SBF or just use NFS script from OrangeFR (Option 1 or 2)?
Well, let's see:
I went from Bell stock to French SBF originally (via RSD) to Gingerblur. I then went back to stock French SBF and from French SBF to bootloader unlock (via IHOP) to fastboot OrangeFR (d001), though I didn't update the Webtop at all (except maybe during Gingerblur) which is where this error is originating from.
So I went from OrangeFR back to Bell stock 2.2.2 through NF's script (which went fine, no errors at all). I did a factory reset in the ROM itself (not through CWM) which was fine, and once I got back into the stock Bell 2.2.2 complete clean I did your steps.
1) Put the Bell 2.3.4 zip and CWM_root zip on the SD card.
2) Flashed IHOP with RSD
3) Flashed recovery via fastboot
4) Went into recovery and tried the .zip file.
That's where we stand. Should I wipe data/cache before flashing, or will that just put me further in the ****hole?
Thanks again.
plemen said:
I've had this error while upgrading and it was because the base ROM on the phone isn't "Bell enough".
Did you flash the French SBF or just use NFS script from OrangeFR (Option 1 or 2)?
Click to expand...
Click to collapse
What did you do, then, to make the ROM more "Bell-like"?
plemen said:
I've had this error while upgrading and it was because the base ROM on the phone isn't "Bell enough".
Did you flash the French SBF or just use NFS script from OrangeFR (Option 1 or 2)?
Click to expand...
Click to collapse
awryter said:
Plemen, thank you for your help so far. I have done everything you mentioned, and once I get to CWM installing the 2.3.4 over the Bell 2.2.2 (which I used NFHimself's script to get back to) I get the following error.
Any ideas? (Please see attached image)
Click to expand...
Click to collapse
when you did step one did it say it downloaded the files prior to updating the device? this step takes approx an hour to complete.
So it looks like one of your partitions isn't close enough to bell. When I ran into this issue I went with option 1 - I flashed the French SBF and then ran NFS script to root and then restore to install the Bell partitions and checked for OTA. Now that NFS has updated his script to restore 2.2.2 partitions, the OTA may not find any updates which is fine.
awryter said:
What did you do, then, to make the ROM more "Bell-like"?
Click to expand...
Click to collapse
awryter said:
Well, let's see:
I went from Bell stock to French SBF originally (via RSD) to Gingerblur. I then went back to stock French SBF and from French SBF to bootloader unlock (via IHOP) to fastboot OrangeFR (d001), though I didn't update the Webtop at all (except maybe during Gingerblur) which is where this error is originating from.
So I went from OrangeFR back to Bell stock 2.2.2 through NF's script (which went fine, no errors at all). I did a factory reset in the ROM itself (not through CWM) which was fine, and once I got back into the stock Bell 2.2.2 complete clean I did your steps.
1) Put the Bell 2.3.4 zip and CWM_root zip on the SD card.
2) Flashed IHOP with RSD
3) Flashed recovery via fastboot
4) Went into recovery and tried the .zip file.
That's where we stand. Should I wipe data/cache before flashing, or will that just put me further in the ****hole?
Thanks again.
Click to expand...
Click to collapse
Hi,
If you are using my restore phone option, be aware that it overwrites all the partitions except for partition 3 which is you pds partition, data, which is 2 GB and can be generated with a factory reset, and cache, which is a 600MB temp storage space which can be wiped as well. It isn't just system and boot. It restores partitions that sbfs may not write to but doesn't update any bootloaders or radios.
The only thing that the French sbf might do to make things work is to flash an older bootloader. It is also possible that some portion of your pds partition gets modified. Most likely it's a signature in the bootloader or command line options being passed to the kernel that don't apply. There have been reports of phones bricking on ATT when they go back to their older bootloader, however, there have been anecdotal reports that this isn't the case for Bell. Be careful and be prepared for the worst.
Cheers!
If I do this, will I still have an unlocked bootloader?
once the entire process is complete, yes.
y2whisper said:
once the entire process is complete, yes.
Click to expand...
Click to collapse
So then could this be a permanent fix to the RAM issue?
Thanks for the detailed info on the scripts - it's great to get it from the horses mouth
NFHimself said:
Hi,
If you are using my restore phone option, be aware that it overwrites all the partitions except for partition 3 which is you pds partition, data, which is 2 GB and can be generated with a factory reset, and cache, which is a 600MB temp storage space which can be wiped as well. It isn't just system and boot. It restores partitions that sbfs may not write to but doesn't update any bootloaders or radios.
The only thing that the French sbf might do to make things work is to flash an older bootloader. It is also possible that some portion of your pds partition gets modified. Most likely it's a signature in the bootloader or command line options being passed to the kernel that don't apply. There have been reports of phones bricking on ATT when they go back to their older bootloader, however, there have been anecdotal reports that this isn't the case for Bell. Be careful and be prepared for the worst.
Cheers!
Click to expand...
Click to collapse
First of all...Can anyone who has been using the new 2.3.4 tell me is there any significant differences in the performance of the phone in everyday use?
Second: Will the WebTop without the Dock MOD work with this new ROM?
Third: If I do this will I be able to install Bell official OTA when it comes out officially or it will brick my phone?
I Am already on 2.3.4 on a bell Atrix, I can honestly say the upgrade does about 0 ... now with that said the real thing that we need is a market fix so we can finally play order and chaos in Canada.
I give this Guide a 1/10 because its redundant and is not as cohesive as the other guides that are already available.
Edit: no unlock in this guide?! whats the point?!
Edit2: nvm you didt write a guide... my mistake, you just posted a bunch of links for lazy people
hate when i hit thanks instead of reply.....
anyways thanks ray of sunshine for that post. the thread was created by request, but if you do have a more detailed breakdown feel free to contribute.
@sservati
I have noticed quite the difference with 2.3.4. outside of the added features like gtalk w/video, there are little tweaks like being able view your contacts by your google groups. as well as some performance tweaks live wallpaper still seems laggy but other transitions are very smooth. as long as you are comfortable with unlocking your bootloader etc, this is something I recommend. if you are overly nervous about doing that. then stick to what you have.
The most important thing to note when installing FR orange is to fastboot flash the boot.img that is appropriate for your phone (1100 / d00 ) before you flash the system.img otherwise you will boot loop! Its not clearly indicated in the linked thread from OP.
Carrion
P.S. I do like 2.3.4 more then 2.2.3 ... im just ticked cuz i lost a transparent widget, because for some ungodly reason its now incompatible?!
didn't know about the timing, but yes make sure you follow that guide as well.
ah sorry to hear that.
Did you try doing the spare parts fix? (download spare parts and turn off compatibility mode)
Why are you installing the FR Orange (2.3.4)? The 1100/d00 issue is dealt with in the unlock guides - this thread clearly notes the steps are for unlocked phones only to install Bell 2.3.4.
Anyhow, there are some great threads on unlocking international phones and folks should really consult those to unlock.
Carrion332 said:
The most important thing to note when installing FR orange is to fastboot flash the boot.img that is appropriate for your phone (1100 / d00 ) before you flash the system.img otherwise you will boot loop! Its not clearly indicated in the linked thread from OP.
Carrion
P.S. I do like 2.3.4 more then 2.2.3 ... im just ticked cuz i lost a transparent widget, because for some ungodly reason its now incompatible?!
Click to expand...
Click to collapse
Gonna try that now... thing is i don't have the apk,Ii need to download it from the market, i have already purchased it but its now no longer visable?! I have tried market enabler... this did nothing... i would really like the ability to see and use all the apps in the app market, i know this is a bit off topic though.
Carrion332 said:
Gonna try that now... thing is i don't have the apk,Ii need to download it from the market, i have already purchased it but its now no longer visable?! I have tried market enabler... this did nothing... i would really like the ability to see and use all the apps in the app market, i know this is a bit off topic though.
Click to expand...
Click to collapse
I'm having the same issue with a couple apps that i've purchased.
Anyways back on topic, I was on on cherryblur 0.5 and i managed to get to the bell GB following most of this guide. I tried to do a restore of a nandroid backup i made before going to GB, but for some reason the phone wouldn't boot. It would just stay at the moto symbol. Im assuming it was because of the boot.img. I tried for a few hours to get it to work, but then gave up and flashed the 2.1.1 french sbf, and then used NFHimselfs system restore script to get me back to the stock bell rom. It worked very well, just took a long time.
Personally I really like this Bell rom, works very well for me. Battery life has increased, its FAST, and there's no ram issues. As for the Webtop stuff, im not sure about. I rarely use it.
Just noticed that after flashing the bell_ihop.sbf to unlock the blootloader, the ram goes back down to 300mb. I wonder if someone can dig deeper into the bell_ihop bootloader and possibly fix the ram issues.
Hi everyone, posting this as a information about something you should NOT try: upgrade your OTA rom with custom recovery installed, in my case TWRP.
I did this with ignorance of not think that (or search about) the custom rom could interfere at the normal process of OTA upgrade from Lollipop to MarshMallow. Actually I remembered that I was unlocked and rooted the phone but I did not remember I was using custom recovery. AFAIK at this device is impossible to root without unlocking and custom recovery.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If you are on TWRP don't do this!
For those don't know about TWRP and OTA updates, read this:
https://twrp.me/faq/officialota.html
In short terms: don't try OTA updates (official updates) if you installed custom rom such as TWRP. "Installing official updates from your manufacturer or carrier is not supported by TWRP." "[This] may result in unexpected behavior" "Most of the time the best way to get a new update onto your device is to simply wait a couple of days for ROM makers for your device to come up with ROMs that are based on the new update that you can safely and easily install."
But I did it. And now I'm reporting it for those who are curious. So, what's happened?
Fortunately the device is not bricked as I thought when it reboot to TWRP for flashing the OTA update instead of the stock recovery process! I thought that I messed everything when I see the frozen TWRP for something about 10 minutes or less. After the long 10 minutes of frozen TWRP image I got the recovery working and checked the log:
Of course, errors on the log.
Rebooted and got a frozen background image, after a while a permanent black. When the screen turn off the notification system shows the battery as dead (and it as not). But I could turn it off and gain access to the recovery holding power and volume down buttons.
After two failed reboots to the system with the same result I tried to make a screenshot using the hard buttons and it works (screenshoted the black screen) and suddenly the lock screen shows up. I got into, everything working slow meaning that there was a lot things working in the background. Got some error messages from google service and MMS/SMS communication and minutes later it automatically reboots and booted the TWRP again.
This turned to a loop. I stopped this by going to the system setup - about the device - check for updates. And got a message "the update has failed". Good. After a while the message offering the update shows again... No, thanks...
I rebooted to TWRP and fixed the permissions, maybe this solve some problems.
Right now the phone is working but the rebooting process has unexpected behaviors, some tries result in a normal fast process and other tries result in a long black image and the system/launcher just don't arm up for some minutes, but after a while it works. I'm not confident. Already backed up apps with Titanium backup.
I'm planning to restore everything from the stock using this guide:
http://forum.xda-developers.com/mot...e-restore-moto-e-2015-stock-firmware-t3054303
And them, maybe, update the OTA to marshmallow. Before doing that, I will search and get to know if it is possible to re-root the phone with marshmallow in osprey (that means re-unlock and install TWRP again). Rooted device it's a need for me.
This is what happened to my device when tried to OTA update with TWRP. I had luck not bricking this.
+1 on the dumb attempt. Early morning, excited for the release, upgrade please! Yeah, no good. Is restoring our only option? Seems the upgrade has not even started so what about deleting the downloaded image file or trying to kill the process attempt?
did you really had to make a new thread with that huge wall of text? haha come on man, common knowledge that to take the OTA you need stock recovery ?
Sent from my Nexus 6 using Tapatalk
Seems the upgrade has not even started so what about deleting the downloaded image file or trying to kill the process attempt?
Click to expand...
Click to collapse
Yeah, DON'T proceed with the update! Deleting the downloaded files just break the process... My advise is to make a backup before deleting this.
sgloki77 said:
did you really had to make a new thread with that huge wall of text? haha come on man, common knowledge that to take the OTA you need stock recovery
Click to expand...
Click to collapse
Ok, sorry about the huge wall of text.
No need to adb stock image. A simple factory reset worked for me. Next time will have more caffiene before attempting anything major with my phone.
golgiapp said:
No need to adb stock image. A simple factory reset worked for me. Next time will have more caffiene before attempting anything major with my phone.
Click to expand...
Click to collapse
:good:
Good to know that a factory reset could fix the problems caused by the OTA update with TWRP. But after this it should remain with custom recovery and not possible to OTA update. for stock MM
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
Not sure, but take a look at /cache
gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
/data/data/com.motorola.ccc.ota/app_download
hp420 said:
/data/data/com.motorola.ccc.ota/app_download
Click to expand...
Click to collapse
found it!!
thanks extracted ok !!
its a zip flashable,can it be converted to install like the oem recovery images using the adb method?
gonzodesigns said:
i downloaded the 24.11.25.en.US ota update not installed yet becuase i want to find it first and save it on my pc.
any idea what folder is saved ??
Click to expand...
Click to collapse
Thank you for the warning
---------- Post added at 12:58 AM ---------- Previous post was at 12:54 AM ----------
Thank you for the warning
I experience this today, I flashed a stock rom again so I can have the OTA update, but what I can't do is root my device, I flash the custom recovery and then I flash the beta version of SuperSU, and when I reboot my device it bricks in the Motorola Logo, anybody knows how to fix this, or should I wait a little bit longer to root my phone? as the OP I need root too
Use the latest 2.62 superSU zip. And never root with the TWRP option before reboot.
Sent from my MotoG3 using Tapatalk
nelsonw said:
Use the latest 2.62 superSU zip. And never root with the TWRP option before reboot.
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Never done that, I tried flashing the superSU 2.52 from a bunch of tutorials I found on Google, but all it does is bricking my phone on the Motorola Logo, then I have to do all the downgrade and update process again
VicSanRED said:
Never done that, I tried flashing the superSU 2.52 from a bunch of tutorials I found on Google, but all it does is bricking my phone on the Motorola Logo, then I have to do all the downgrade and update process again
Click to expand...
Click to collapse
this is a known issue with the mm update. Use 2.61 or newer, only. These are the new systemless root zips.
hp420 said:
this is a known issue with the mm update. Use 2.61 or newer, only. These are the new systemless root zips.
Click to expand...
Click to collapse
I tried with the latest version 2.66 and still the same issue. Don't know what to do now.
So its posible to root MM ?? Safe ,stable?
Supersu v 2.62??
Yeah, 2.62 is the only one working. This worked for me BETA-SuperSU-v2.62-20151210170034
Sent from my MotoG3 using Tapatalk
nelsonw said:
Yeah, 2.62 is the only one working. This worked for me BETA-SuperSU-v2.62-20151210170034
Sent from my MotoG3 using Tapatalk
Click to expand...
Click to collapse
Can you post a little tutorial?, I wanna be sure I'm doing everything OK.