Related
Yikes, am I in a predicament.
So, here I am, with my Nexus S I9020A on Koodo in Canada, rooted with TWRP v2.2.0 recovery and stock 4.0.4; well, with all the JellyBean buzz going about I figured, hey, why not, and I made a nandroid backup using TWRP, and copied said backup onto my PC for an extra copy.
Well, after playing around with an AOSP rom of 4.1.1 I want the stock OTA, but restoring the backup I made yields no results, touting "no recovery or img" as an error. So now I have no idea how to get to either stock JellyBean (which is where I want to be) or at least stock 4.0.4 for the I9020A so I can get the OTA.
What do I do?!
Try flashing twrp again. I had this problem on my ns4g awhile ago while running one of the older twrp recoveries. If memory serves, I was able to reflash twrp, reboot recovery, then restore a twrp backup. If it still won't restore, try wiping & flashing a ROM of your choice. You may have to adb fastboot flash...
Sent from my Nexus S 4G using xda premium
p1gp3n said:
Try flashing twrp again. I had this problem on my ns4g awhile ago while running one of the older twrp recoveries. If memory serves, I was able to reflash twrp, reboot recovery, then restore a twrp backup. If it still won't restore, try wiping & flashing a ROM of your choice. You may have to adb fastboot flash...
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
I'm trying to reflash TWRP and restore again - fingers crossed.
What happened to that list of all official OTA variants for the Nexus S?
I'm referring to that list that had for instance :
Nexus S - I9020A:
2.3.4 - Download link
2.3.6 - Download link
etc, etc.
I just want to get back to stock 4.0.4 so I can get the 4.1.1 OTA :S
Or have any way to get to STOCK 4.1.1 for the I9020A Nexus :S
Found this link posted by user oldblue910, it should have what you need if you're still stuck... http://www.randomphantasmagoria.com/firmware/nexus-s/
Sent from my Nexus S 4G using xda premium
p1gp3n said:
Found this link posted by user oldblue910, it should have what you need if you're still stuck... http://www.randomphantasmagoria.com/firmware/nexus-s/
Sent from my Nexus S 4G using xda premium
Click to expand...
Click to collapse
That's exactly what I was looking for, thanks, ended up just taking the long road there and back from Gingerbread to JellyBean, so far so good!
Thanks for everyone's help!
I've not been able to catch up to speed with the new custom roms and need some help from the community.
When I brought my UK WIFI Xoom (MZ604) back in Autumn 2011 I had it rooted, Clockwork recovery installed and a Tiamat custom rom on it. I switched it on earlier in the week and the boot screen just kept on loading in a cycle and wouldn't stop. I thought to save myself time I grab a new rom and install the ZIP as normal. Now the Xoom just goes in a cycle of the loading rom screen. I don't think I've bricked it because I'm able to get into the recovery mode.
I've been out of touch and need some clear guidance in what I need to do next.
1. All the ICS roms have ceased development? Reason why I ask is that its easier to 'recover' my Xoom with just install a new Rom over the old?
2. Jellybean requires additional steps to put the customer rom? Its not just a simple case of install new Rom over the old via clockwork.
EDIT: Just to note I'm still on HoneyComb so looking further I might need to put a new CWM on my tablet and reroot?
Thanks.
Question: As I've got CWM currently installed, if I perform flashing eos recovery, will this resolve my issues?
Can you download the stock firmware and flash it through fastboot and start from scratch?
Sent from my ADR6300 using xda premium
jlvlawrence said:
Can you download the stock firmware and flash it through fastboot and start from scratch?
Sent from my ADR6300 using xda premium
Click to expand...
Click to collapse
I think I can revert it back to stock but I was hoping to do a quick win solution and download a rom and install. I might have to follow some guides tonight and get it up and running again.
Try installing rogue touch recovery and flashing a different rom.
Sent from my Galaxy Nexus using xda premium
hello guys im new to the samsung game! im a former razr owner! but i noticed the is allot of differences in the motto hacking and the samsung hacks? i have a stock rooted Verizon galaxy s3 i downloaded the bootloader unlock app but haven't had the guts to hit the unlock button! and downloaded the ez recovery app but haven't use it ether! Im not sure where to start? i want to flash cm10 to try out the jelly bean effect! lol but i don't know where to start with that ether! and if i unlock the bootloader am i still able to flash the stock rooted rom using the same odin process that Ive done b4? do i need to back up anything? please help with a flashing guide 101 for samsung lol !
drnoob said:
hello guys im new to the samsung game! im a former razr owner! but i noticed the is allot of differences in the motto hacking and the samsung hacks? i have a stock rooted Verizon galaxy s3 i downloaded the bootloader unlock app but haven't had the guts to hit the unlock button! and downloaded the ez recovery app but haven't use it ether! Im not sure where to start? i want to flash cm10 to try out the jelly bean effect! lol but i don't know where to start with that ether! and if i unlock the bootloader am i still able to flash the stock rooted rom using the same odin process that Ive done b4? do i need to back up anything? please help with a flashing guide 101 for samsung lol !
Click to expand...
Click to collapse
See this:
forum.xda-developers.com/showthread.php?t=1837863
(sorry of the non-hyperlink, I'm not allowed)
You have everything you need. If you're rooted, unlock the bootloader using the app you have, flash the non-touch cwr 6.0.1 or 6.0.2 using the ez recovery app or rom manager, then download cm10 and appropriate latest jelly bean gapps, boot into recovery from rom manager or pull battery hold volume up+home +power. From there, do a nandroid backup first, then wipe data, cache, system, and dalvick. Now flash your cm10 or any other rom, then your gapps, profit.
Edit: no over the air updates should be accepted or you can brick that shiny phone.
The whole process is much simpler now that the bootloader is unlocked.
Sent from my SCH-I535 using xda premium
thanks for the info! so say I'm on a custom Rom with my boot loader unlocked and i want to go back to stock rooted, would i just flash the stock rooted image? and won't that lock the boot loader again?
Sent from my SCH-I535 using Tapatalk 2
drnoob said:
thanks for the info! so say I'm on a custom Rom with my boot loader unlocked and i want to go back to stock rooted, would i just flash the stock rooted image? and won't that lock the boot loader again?
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Depends if you're on an AOSP based rom. If so, you'll need to flash a stock kernel and a full wipe is also necessary. Otherwise you should pretty much just be able to dirty flash over any stock based roms.
No, it won't relock the bootloader. That's a separate process.
Update: This bootloader is older and is not the newest available one. If you want the 4.18 version one go to THIS post and flash it with fastboot.
Older bootloader version: Doesn't flash and take hold for everyone, flash at your own risk
Usefull for people that don't want to flash in fastboot. The official OTA for 4.2 flashes this bootloader through recovery in the exact same manner
Code:
md5sum: 7cb16bc418e15ee2c7c48b82ea923e23
Code:
sha1sum: 6151d4afd075d03cfdfa33d111a1a6bba25fcab8
Code:
sha256sum: 2b7efeade37c1ec00d03ba71a56d5b921e6c27d4393298020bcd1601ae079605
Code:
sha512sum: cd7444ec7073e553b7715e4ee30d69f64b06ab3846f1d0ff3d9129f652ab4e90c3400f139a0347f0b78a0719c86b6e2d7f41d36068f032472dbc90c3530cefcb
You need to be aware that on my Nexus7 the problem with Custom Recovery on the newest bootloader still exist.
Means you need to downgrade to 3.34 in order to flash CWM.
remmyhi said:
You need to be aware that on my Nexus7 the problem with Custom Recovery on the newest bootloader still exist.
Means you need to downgrade to 3.34 in order to flash CWM.
Click to expand...
Click to collapse
I need to be aware of problems that happens on your Nexus7? I don't have that issue I flashed TWRP Recovery just fine on this booloader...
No, I did not write to you personally. Glad it worked on your side.
Just the people to know.
That's really strange. I would try flashing the 4.1.2 factory images even though it might wipe everything including your sdcard.
Sent from my Nexus 7 using Tapatalk 2
Did that, thanks. Indeed wiped everything
Glad I had a backup
Hey guys,
So, I can flash this file from TWRP and it will upgrade my bootloader?
Thanks in advance!
you can, but make sure you check MD5, flashing a corrupt download can kill your device. OP, you should add a MD5 check in the zip if possible. but thanks for this none the less.
If you have a rom like cm10 installed or other rom that has buysbox in it, just type busybox md5sum /sdcard/bootloader-grouper-4.13.zip
Either in terminal emulator or adb shell.
If your on stock you'll probably want to check it with a program on your pc or install busybox from one of the playstore busybox apps. Of course you'll need to be rooted.
Sent from my Nexus 7 using Tapatalk 2
I went ahead and added sha1sum, sha256sum and sha512sum checks.
I have just flashed the file and thank you, I no longer have to keep my power button pressed for 20 seconds just to have my tablet go on
Thank you so much!!!
If anyone has any problems there is a link in my SIG to fix it or if you just need to revert back...
Just a FYI the older bootloaders are in the factory images! You can extract them out and flash the bootloader separately if you don't want to flash ALL the factory images. So far flashing this with twrp I have not had one single issue yet to speak of... Each bootloader is meant to run on specific platforms, recoveries, kernels ect. So on that note I still suggest if you want to revert your bootloader you revert completely with the factory images.
Sent from my Nexus 7 using Tapatalk 2
Hi,
thanks for that but when i falsh it in TWRP it's wipe all my data but i still have the 3.41 bootloader?
I'm not sure if i understood the thing to do with the md5sum?
f*** this bootloader i flash it yesteday.........
and my tablet stay on bootloader and i can't flash google image 4.1.1-4.1.2-4.2
why??
i can't downgrade bootloader too.........
CWM + CM10 stable
I just flashed this bootloader using CWM 6.0.1.0 and CM10 stable. I used Chrome to download it and the md5sum command in terminal emulator to check the md5 hash before hand. It flashed fine, I have the new version number, everything continues to work. Very easy.
farshad.shirzadii said:
f*** this bootloader i flash it yesteday.........
and my tablet stay on bootloader and i can't flash google image 4.1.1-4.1.2-4.2
why??
i can't downgrade bootloader too.........
Click to expand...
Click to collapse
Check this http://forum.xda-developers.com/showpost.php?p=32735541&postcount=5039
Thanks, easy flash, works perfectly
Sent from my Nexus 7 using xda app-developers app
Wondering does the new boot loader support older custom ROMs and the nexus toolkit, will I need to re unlock bootloader after flashing it ?
Answered my own questions flashed with cwm still have root but don't know how to check if boot loader is locked or what version I have. Works fine with cm10.
Sent from my Nexus 7 using xda premium
blucmal said:
Wondering does the new boot loader support older custom ROMs and the nexus toolkit, will I need to re unlock bootloader after flashing it ?
Answered my own questions flashed with cwm still have root but don't know how to check if boot loader is locked or what version I have. Works fine with cm10.
Sent from my Nexus 7 using xda premium
Click to expand...
Click to collapse
When you power your device on you hold the volume down button to get into bootloader. On the main screen it will say what version it is.
Sent from my Nexus 7 using Tapatalk 2
Hi – I have a stubborn issue with my Blaze 4G not working on CM roms, I would appreciate any help you guys can provide. Below are the details:
I recently bought a T-Mobile Samsung Galaxy S Blaze 4G, and did the following:
- Rooted it using the following guide (it now has ICS)
- SIM Unlocked it using the following guide (now it works on other networks)
- Updated to CWM 6.0.3.8, since JB roms needs it
- Flashed the T769-UVLH5 modem, since CM support it
And now when I flash CM 10 stable or 10.2 nightly it gets stuck in booting and displaying the CM logo animation screen, after few minutes it reboots and does it all over again.
I remember when I upgraded to CM JB on my SGS3 I needed to flash a JB stock rom on it to get the new boot loaders for JB, but I saw no mention of this on this forum. What else am I missing?
Thanks.
TINGEA said:
Hi – I have a stubborn issue with my Blaze 4G not working on CM roms, I would appreciate any help you guys can provide. Below are the details:
I recently bought a T-Mobile Samsung Galaxy S Blaze 4G, and did the following:
-Rooted it using the following guide (it now has ICS)
-SIM Unlocked it using the following guide (now it works on other networks)
-Updated to CWM 6.0.3.8, since JB roms needs it
-Flashed the T769-UVLH5 modem, since CM support it
And now when I flash CM 10 stable or 10.2 nightly it gets stuck in booting and displaying the CM logo animation screen, after few minutes it reboots and does it all over again.
I remember when I upgraded to CM JB on my SGS3 I needed to flash a JB stock rom on it to get the new boot loaders for JB, but I saw no mention of this on this forum. What else am I missing?
Thanks.
Click to expand...
Click to collapse
You wiped data/cache/system? Reinstall it. Anyways use the new 6.0.4.4 recovery.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
You wiped data/cache/system? Reinstall it. Anyways use the new 6.0.4.4 recovery.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom. I have to admit that I forgot to do the wipes. but even after doing the wipes (data/system/ factory rest/ cach/devalk) and reinstalling the CM nightly, I still have the same issue.
as for recovery, I updated to the latest version using the rom manager, and according to the official site clockworkmod[dot]com[slash]rommanager (can't post links) I have the latest version for Blaze. how do you get the 6.0.4.4 on blaze?
I still feel it's a ICS vs JB bootloaders issue, but not sure how to proceed next.
Thanks!
TINGEA said:
Thanks Somcom. I have to admit that I forgot to do the wipes. but even after doing the wipes (data/system/ factory rest/ cach/devalk) and reinstalling the CM nightly, I still have the same issue.
as for recovery, I updated to the latest version using the rom manager, and according to the official site clockworkmod[dot]com[slash]rommanager (can't post links) I have the latest version for Blaze. how do you get the 6.0.4.4 on blaze?
I still feel it's a ICS vs JB bootloaders issue, but not sure how to proceed next.
Thanks!
Click to expand...
Click to collapse
No boot loaders man. This is before Samsung's complications.
Recovery is here.
http://d-h.st/AFu
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Thanks Somcom3X, but still didn't work. When installing the CM room in recovery 6.0.4.4 I get a bunch of getprop assert failures. This used to work on the previous version (6.0.3.8). Now the Rom won't install.
Also, I'm curious what did you mean by this is before Samsung's complications?
Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
Thanks Somcom3X, but still didn't work. When installing the CM room in recovery 6.0.4.4 I get a bunch of getprop assert failures. This used to work on the previous version (6.0.3.8). Now the Rom won't install.
Also, I'm curious what did you mean by this is before Samsung's complications?
Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
After 2011 samsung began installing software and counters to try and prevent people from rooting and installing custom firmwares.
knox is an example of this.
These devices don't have any of that complicated security.
You handy with odin? Your recovery is not right. Just to be clear, what is your model number?
If it is T 7 6 9, your good to go to odin. I'd recommend going back to stock, and then install a recovery and you should be good to go.
Somcom3X said:
After 2011 samsung began installing software and counters to try and prevent people from rooting and installing custom firmwares.
knox is an example of this.
These devices don't have any of that complicated security.
You handy with odin? Your recovery is not right. Just to be clear, what is your model number?
If it is T 7 6 9, your good to go to odin. I'd recommend going back to stock, and then install a recovery and you should be good to go.
Click to expand...
Click to collapse
Thanks again, I use the guide here to convert the image into a tar.md5 to flash using odin, but after flashing successfully I still have the same issue when installing the CM zip file in recovery, and yes it is the T-mobile Samsung Galaxy S Blaze 4G T769.
any other possible causes?
BTW - when I was flashing via Odin my upload phone screen was showing that I have a custom rom and the counter was 1.... do I need to fix that?
TINGEA said:
Thanks again, I use the guide here to convert the image into a tar.md5 to flash using odin, but after flashing successfully I still have the same issue when installing the CM zip file in recovery, and yes it is the T-mobile Samsung Galaxy S Blaze 4G T769.
any other possible causes?
Click to expand...
Click to collapse
SOLUTION:
The reason your stock recovery system keeps getting overwritten at Android startup is because of a script that is being run.* All you need to do is either rename this script or simply delete it.
Please keep in mind that if you restore your stock ROM, this script will be restored with it so you will have to rename or delete it again.* Do the following:*
1.
Make sure your device is powered on and running normally,
2.
Make sure you have rooted your device and that you have all of the necessary permissions in order to manipulate system files.*
3.
In the root file system go to \system\etc
4.
Find the file named install-recovery.sh and either rename it or, as I did, delete it.*
That’s all there is to it.*
Please keep in mind that you will need to flash your custom system recovery one more time after modifying the script file.* After that, reboot away and you will always be able to get back into your new system recovery.
Good Luck and Happy Tweaking.
Click to expand...
Click to collapse
Try that.
Found it here http://mark.candleshoreblog.com/201...-factory-stock-roms-at-android-system-reboot/
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
Try that.
Found it here http://mark.candleshoreblog.com/201...-factory-stock-roms-at-android-system-reboot/
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom3X - but I'm not sure this is needed for my case. I read the original blog post and my recovery does not get overwritten. I actually rebooted multiple times into CWM recovery and each time it is the same 6.0.4.4.
I also went into the /system/etc folder and there is no install_recovery.sh file.
to clarify, here is where I'm stuck now:
- when I use CWM 6.0.3.8 CM install completes successfully, but then CM will not boot, and will keep on cycling on the boot logo screen.
- when I use CWM 6.0.4.4 I can't start to install CM as it complained that my phone is not t769.
in all cases I'm using CM 10.2 nightly for T769.
Thanks for the help.
You should delete assert lines at the top of the zip's updater-script and it will let you flash it.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
I removed the assert lines from the updater script, and it was able to complete the install process afterwards, however when I booted the new CM 10.0 system it got stuck on the cyanogenmod boot logo. I made sure I do a system/data rest, cleared cash, and cleared devalk.
I do not think it's an issue with my recovery as I'm getting the same result as I did with the official 6.0.3.8.
Something else is going on.
Any ideas?
Thanks.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
I removed the assert lines from the updater script, and it was able to complete the install process afterwards, however when I booted the new CM 10.0 system it got stuck on the cyanogenmod boot logo. I made sure I do a system/data rest, cleared cash, and cleared devalk.
I do not think it's an issue with my recovery as I'm getting the same result as I did with the official 6.0.3.8.
Something else is going on.
Any ideas?
Thanks.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
Tar back to stock GB. Upgrade to ICS. Then root and install cwm. Flash away
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Somcom3X said:
You should delete assert lines at the top of the zip's updater-script and it will let you flash it.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Thanks Somcom3X - but this is more trouble than what I wanted to put in - I'll stick with the rooted stock ROM I have. I was hoping the process was a little more straight forward, similar to my SGS3.
thanks for all your help thus far!
Somcom3X said:
Tar back to stock GB. Upgrade to ICS. Then root and install cwm. Flash away
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Click to expand...
Click to collapse
Ok, my rooted ICS stock is acting up (random shutdowns and such), so I need to give this another try and get this phone to CM.
I tared back to stock GB, skipped the upgrade to ICS (was not able to upgrade via the ROM software update option), flashed CWMR (5.0.4.x) via Odin, upgraded to CWMR 6.0.4.5, installed CM 11 nightly, and then wiped data/factory rest and Dalvik .... and ....
it is still stuck on the boot screen....
I seriously would appreciate a silver bullet right now!
TINGEA said:
Ok, my rooted ICS stock is acting up (random shutdowns and such), so I need to give this another try and get this phone to CM.
I tared back to stock GB, skipped the upgrade to ICS (was not able to upgrade via the ROM software update option), flashed CWMR (5.0.4.x) via Odin, upgraded to CWMR 6.0.4.5, installed CM 11 nightly, and then wiped data/factory rest and Dalvik .... and ....
it is still stuck on the boot screen....
I seriously would appreciate a silver bullet right now!
Click to expand...
Click to collapse
Hmm. Go back to stock ics, flash a 10.2 recovery, then flash whatever you desire.
Sent from my SAMSUNG-SGH-T769 using Tapatalk
What is a10.2 recovery? Is it a certain version of CWMR? And do I need to flash it via Odin? Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
TINGEA said:
What is a10.2 recovery? Is it a certain version of CWMR? And do I need to flash it via Odin? Thanks
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
It would be cwm 6.0.2.7
You can flash the img through a zip or by terminal on the phone.
Odin needs a tar'd recovery img
Sorry been very busy.
Have you tried this?
http://forum.xda-developers.com/showthread.php?t=2577265
Sent from my SAMSUNG-SGH-T769 using Tapatalk
Thanks Somcom3X - I looked all over this forum and the internet, and could not find a link for a 6.0.2.7 CWM for Blaze - I found it for other phones but not Blaze. can you please point me to a link if you happen to know of one. the official site does not have an archived list of previous versions.
as for the provided link, I did follow it through, and downloaded the recovery Tar (it was CWM 5.5.04) but that yielded the same results after installing CM 10 and 10.2 - stuck at boot screen logo. I'm reasonably confident now that it is not a recovery issue, as I flashed half a dozen different versions and none worked with CM 10, 10.2, or 11.... it has to be something else!
Thanks.
TINGEA said:
Thanks Somcom3X - I looked all over this forum and the internet, and could not find a link for a 6.0.2.7 CWM for Blaze - I found it for other phones but not Blaze. can you please point me to a link if you happen to know of one. the official site does not have an archived list of previous versions.
as for the provided link, I did follow it through, and downloaded the recovery Tar (it was CWM 5.5.04) but that yielded the same results after installing CM 10 and 10.2 - stuck at boot screen logo. I'm reasonably confident now that it is not a recovery issue, as I flashed half a dozen different versions and none worked with CM 10, 10.2, or 11.... it has to be something else!
Thanks.
Click to expand...
Click to collapse
I'm very sorry for the delay. Been very very busy.
https://www.dropbox.com/s/awp1zy4u3x34a2v/CWM-cm-10.2-Recovery-t769.zip
That is my personal 10.2 recovery. Works fine for me.
The author is me, but I was too lazy to change the lines.
Sent from my SAMSUNG-SGH-T769 using Tapatalk