First things first, all credit goes to imnuts for bringing us Froyo! I'm not going to name this anything special, since all I did was download a little from the market here, delete and replace a little there, and make an Odin image. Since I can't in good conscience take any donations for this, if you're so inclined to donate to anyone, donate to imnuts!
This is a modified build of the stock EC03 ROM. I'll spare you all the boring details and just give the main points. As an aside, I take no responsibility if you brick your phone! I've tested this myself on my own Continuum with the actual uploaded ROM, so I can confirm that this works, unless you have already completely screwed up your phone! I have included the link to One Touch Unbrick for such a scenario (credit to AdamOutler)
- I've replaced the TouchWiz launcher with Go Launcher
- Stock browser has been replaced with Dolphin HD
- Bing, MS Streets, VZW apps all removed
- Google Search is the default, and Google Maps is included.
- I haven't figured out how to open Google Voice Search with a long press on the search softkey, but the softkey does open up Google Search
- When starting up, you may get a nag from Go Launcher. Don't worry, it will go away and you'll never see it again.
- For some odd reason, once the shortcut buttons for Go Launcher appeared in the wrong place. If this happens, tap Menu, Preferences, Operation Settings, and check Screen rotation. This will fix it, and you can disable Screen rotation if you'd like
Here's some useful links for what you'll need. This way, you don't have to go searching through threads to get everything you need. To flash, do the following:
1. Download the update.zip file and place it on the root of your SD card. It is probably best to do this first before flashing anything.
2. Place your phone in download mode by removing the battery and holding vol-down while connecting the USB cable.
3. If you want to do a NAND backup before proceeding, then flash just the CWM recovery listed below under PDA in Odin. Otherwise, proceed to step 4.
(a) Remove your USB cable, insert your battery, and power on the device while holding both the vol+ and vol- buttons until the Samsung logo appears
(b) To get into CWM, use the vol- to highlight apply sdcard:update.zip, and tap where the menu softkey normally is
(c) Once in CWM, the power button becomes select, and the back softkey is to go back. Use vol- to highlight backup and restore, select, then select Backup.
(d) Once backup is complete, remove your battery, and while holding down the vol- button, connect your USB cable. Keep holding until you are in download mode.
4. Unzip the ROM file to a tar.md5 file, select this file in Odin under PDA, and flash away!
5. Place the update.zip file linked below and boot into recovery by holding both volume buttons and the power button until you see the Samsung logo.
6. Once in recovery, apply update.zip. This is the CWM recovery, so you'll need to use the menu soft-key to select. Once in CWM, the power button is select and the back soft-key is back.
7. In CWM, make sure you do a wipe/factory reset and wipe cache partition, then reboot.
8. Profit!
Odin3 v1.85: http://www.4shared.com/file/DxGjuFFQ/Odin3.html
Cyan CWM update.zip: http://www.4shared.com/file/cLdwKNsU/update.html
ROM: http://www.4shared.com/file/2hM6e4B2/I400_Froyo.html
One Click Unbrick: http://www.4shared.com/file/u2e5ow7y/OneClick.html
Adrynalyn's CWM Restore: http://www.4shared.com/get/G2sff5Sg/cwm_recovery_test4_adryn.html
{
"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"
}
The voice search works for me on the original EC03 actually it works surprisingly well. Me and a friend of mine were having some drinks and saying random stuff to it and it searched for what we said every time lol..
Yeah, it worked for me, but I didn't want the Bing voice search, I wanted the Google voice search. The voice search works on this modified ROM as well, but it's Google Voice Search. It just won't pull up with a long-press on the search soft-key. It works fine though within applications, and if you press the search soft-key, it pulls up the Google Search, and you can voice search from there. If I get bored this evening, I might create a stock Odin image from the original EC03. No promises though!
Doesn't selecting wipe/factory reset and wiping cache partitions totally just uninstall the mod?
Confuuuuuused LOL. I'll try it following your directions exactly (though you should put the "Place Update.zip" part at the very beginning. I foresee a lot of people getting confused on that lol) and see how it goes Thanks!
TraMaI said:
Doesn't selecting wipe/factory reset and wiping cache partitions totally just uninstall the mod?
Confuuuuuused LOL. I'll try it following your directions exactly (though you should put the "Place Update.zip" part at the very beginning. I foresee a lot of people getting confused on that lol) and see how it goes Thanks!
Click to expand...
Click to collapse
No need to get confused! I might just take your suggestion and edit my post. Flashing an Odin image is a lot easier than it sounds, and if you mess something up, there's always a way to get back to stock.
Even though Android devices have a single internal flash drive, there are separate mount points that are used by the OS with different permissions for each. Remember the underlying OS is essentialy a Linux/Unix derivative, and what you see on the UI of the phone is nothing more than a well designed GUI. That being said, the system partition/mount point by default is set as read only. When doing a wipe/factory reset, you are deleting all the user-defined parts of the OS, such as downloaded apps, email, contacts, calendar, etc. The cache partition is just that - a location where parts of the OS are placed when in transition, such as when updating an app that is part of the system partition.
When you root an Android phone, you are essentially unlocking the system partition so you can not only see what data is on the internal storage itself, but by using a file explorer that can make use of the root permissions, you can add and delete content to the system partition, which is how I made this ROM. Once I had everything the way I wanted it, I then extracted those mount points and combined them together into the flashable Odin image.
When you install a custom ROM, you are replacing the system partition located on the internal flash drive, and typically the recovery and kernel partitions as well.
I'm guessing this may be more information than you wanted, but I thought I'd throw it all out there to make things, hopefully, a little clearer.
That's actually really cool to know how you made this. Just in case, in the future, I want to make my own back up or whatever for it. Also, the rom works flawlessly. I was having problems with the other stock froyo rom until I flashed this on. My home and Search keys did nothing and I had no lock screen at all. I think it was just a random error when I flashed it, possibly because I didn't wipe the cache or something when I flashed the first time. Thanks a bunch buddy!
Awsome info....thanks
sent from my XDA phone - its more than a continuum
I'm glad to hear it's working for people. The only issue is bringing up Google Voice Search with a long-press on the search key, but heck, it's a very small price to pay to be rid of Bing.
Anyhow, here's a post for making your own Odin image. Like most everything I've posted lately, this too is courtesy of imnuts.
http://forum.xda-developers.com/showthread.php?t=1082288
I didn't even know you COULD voice search lol!
Yes, this does have Google Voice Search pre-installed. When tapping the search button, the standard Google Search app will open. Tap the microphone icon, and you have voice search.
Pretty good stuff, i'm not much of a fan of Go Launcher, other than that its really good.
just got this going and everything is running good so far. I have one question since this is a rooted rom is the native 3g hotspot free now or am i better off using wireless tether either way it dosnt matter my ps3 just picks up the 3g hotspot.
nvm i got it lol. i used wireless tether3.1 set profile to fascinate and enabled softap mode and my ps3 picks it up just fine.
Does the "Ticker" area still function like the factory version?
Will Flash Player 10 work?
tanru said:
Does the "Ticker" area still function like the factory version?
Will Flash Player 10 work?
Click to expand...
Click to collapse
Yes and yes.
Sent from my SCH-I400 using XDA App
This is too damn funny. My ROM made its way to Addictive Tips without me even knowing! I'm back to working on trying to improve this ROM. I don't know if anyone else is working on one, but my Eris is giving me problems, so I'll be keeping the Continuum at least until the last week or so of September.
http://www.addictivetips.com/mobile/install-android-2-2-froyo-custom-rom-on-samsung-continuum/
I have a list of some apps I'd like to see removed to make a super clean ROM. Let me know if you're interested.
Sent from my SCH-I400 using XDA App
Just use root explorer to remove the system apps.
Sent from my SCH-I400 using XDA App
samuelhadams said:
I have a list of some apps I'd like to see removed to make a super clean ROM. Let me know if you're interested.
Sent from my SCH-I400 using XDA App
Click to expand...
Click to collapse
I'm actually looking at doing that. I'm trying to get GoogleVoice working with a long press of the search soft key, but so far no luck. When I do get around to making another flashable rom, I'll be incorporating the Launcher for GB, and possibly removing a few more apps that I added in that some users may not want installed. It will definitely be a super clean ROM when I'm done!
^
got long press working with google search xD I'll upload it later xD
you have to do some smali editing to fix it, that's why it wouldn't work xP
Sent from my SCH-I400 using XDA Premium App
Related
SuperAosp
THIS ROM IS NOT WELCOME IN FORUM HTCMANIA.
Special thanks to the creator of the inexus theme from which I have been inspired to give a graphic touch to the rom.
This rom (it is not a mod) has been developed entirely from the source code from Google and a very small part of Cyanogen framework.
Thanks to Cyanogen and all its staff for the contributions.
This rom was installed on three terminals, one free from Poland, and two from orange, one with two months and another one with one day. The tree without problems
Before start anything take into account the following steps:
Before start you must have kies installed on your pc and that detect your terminal in a normal way, this is necessary because it needs the driver for odin that is the following that we must hace to install the two first steps.
Odin is attached:
http://cdn.movilzona.es/repos/superatmel/ROMS/SuperAosp/Galaxy/OdinV3_1.85.zip
Also you must put your phone in download mode without problems, the phone must support the three buttons. Because depending on the buttons combination it will make different things.
With the phone totally turned off:
Home+volume up+power = Download mode
Home+volume down+power = Recovery mode
You must test these combinations before start because it is possible that your terminal does not support this buttons combination and you will have serious problems,
Rom installation method:
This rom in installed primary steps
You must have 3 files for installation
1. Rom Stock froyo http://cdn.movilzona.es/repos/superatmel/ROMS/SuperAosp/Galaxy/GT-I9000_FROYO_PDA.tar
2. Kernel with recovery ClockWork http://cdn.movilzona.es/repos/superatmel/ROMS/SuperAosp/8.6/KernelCMW2.tar
3. Rom SuperAosp http://cdn.movilzona.es/repos/superatmel/ROMS/SuperAosp/8.6/[email protected]
Method for installation onto the system
It is really easy, I will try to explain as easy as possible in order to avoid problems.
1st. Step
Turn off kies from the system try
Start Odin
Put the phone in download mode
Select PDA and put the first file GT-I9000_FROYO_PDA.tar
Plug the phone to the PC
It will turn yellow one of the com ports, wait several seconds and push Start
Wait to reboot
If in the boot it stops on recovery mode, make a wipe data factory reset.
If in the boot it starts as usual, it is not necessary to make anything, just wait until the launcher appears
Unplug the phone from the PC
Now on the mobile go to settings, privacy and turn on USB debug
Plug the phone to the PC
Activate the USB card to pass the SuperAosp rom to the internal SD card. BE CAREFUL to the internal not the external one. If you do it in the other way, you will not see the rom to make the installation.
With these steps we will have a original Froyo installed and the SuperAosp rom waiting in the SDCARD for the third step
2nd. Step
Close odin and unplug the phone
Turn off the phone
Reopen Odin
Select PDA
Put the kernel with recovery KernelCMW2.tar
Put the phone in download mode
Plug the phone to the PC
It will turn yellow one of the com ports
Push Start
Wait until reboot
When the Launcher is loaded, we will have a kernel with recovery ClockWork installed
Unplug the phone from the PC
3rd Step and last one
Turn off the phone and restart in recovery mode
Home+vol down+power
It will start in recovery mode
Select wipe data factory reset
Select choose zip from sdcard
Select SuperAosp
Install and wait until finish. Reboot the phone with reboot system now option.
It will reboot twice and finalle we will have the rom installed,
I hope that you find it easy. If you follow my steps to the letter you will not have any problem
ATTENTION!!!
This rom is autoinstalled itself, i.e. it is totally reconfigured
I advice you to skip the configuration of the google account pressing skip and afterwards in the launcher you can configure the rom to your like. If you don't skip the settings of the google account, the phone will connecto to the market and start downloading all the aplications you had preciously installed and that might (it probably will do) saturate the phone because it is trying to do a lot of things at the same time, and it also restore the background image of your home to the one you had previously, and you ask me that how it is possible if you had installed the rom with wipe, to have the same image as before. In this way, you will have a clean instalation. Afterwards, you can log in to the marker and install any free application, so the market will resync and install again the previous applications you had on the phone.
Those of you who made backups of any kind or program, pay special attention, because you might have some problems. (I am speaking of backups, included the SupSetup but applications), specially pay attention to the configuration data restoration of any kind. If in doubt, better not do it.
New SupSetup V20 on all roms, it will not work any other previous SupSetup for this rom
The new SupSetup has integrated the activation of applications on demand in the applications extra section, you can activate the applications that you are interested on because the rom comes in "LITE" mode (without extra applications installed) so as anyone of you can choose their best configuration.
It is important to activate the applications from the SupSetup before setting up the google account, so as when the phone sync with the servers while setting up the google acount, this extra applications fall into the download section. After opening the market, and for the applications to show in the download section, just install any free application, so the market wil resync the downloads.
General
- “LITE” mode rom
- New graphical aspect different to SuperGinger's
Added
- Wake & Unlock
- Bluetooth always visible from Settings (tolemaC)
- Clock hide
- Battery percentage
- Part of CyanogenModsettings from Cyanogen
- etc...
Apps
- More apps could be installed from extra application on SupSetup
- Google Apps
- Flash Player 10.2
Support in Movilzona
http://www.movilzona.es/foro/superaosp-para-samsung-galaxy-t5544.html
Twitter @superatmel
Captures:
{
"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"
}
looks great thanks!
Very nice to see a Pure AOSP build. Is there any bugs which we should look out for?
Also, did you go for a CM7 based kernel or build your own?
Damn it, ment to edit that post ^
Tried your rom (curiosity)
Respect Neat and clean
EDIT: CMW in spanish is a bit hard to understand , good thing there is google translate
haha i just installed this on my brother's nexus S
GREAT to see this here !!!
1.in step 1 do we need to check repartition or leave it unchecked?
2.if i am running Gingerbread now will my backups from titanium will have troubles restoring beacuse this is AOSP and now i am on samsung rom RFS and my backups were made on GB?
3.can i use this method to downgrade to froyo ? http://www.theandroidsoul.com/ezbase-ezrom-for-android-2-2-install-revert-back/
and then install SA ?
4.are there any bugs we should know about or its perfectly stable for daily use ?
hope to get these answers soon and i am SOOOO going to flash this baby _
The very last ROM I flashed on my Nexus One And that was 2 months ago. Will try this for sure.
thanks mate!!
How about the 720p recording and 3G video call?
If they are ok, this rom is good for me.
I am installing now and will report back. Looking great
Good news
I install also
super awesome.
So does everything works in here? like FM radio, video codecs etc? Anything should look out for?
Cheers
You can install the USB drivers from here if you don't want to install Kies, might want to add this to the OP:
http://forum.xda-developers.com/showthread.php?t=961956
Is this really an aosp build? Own kernel? Buglist?
No issues yet FM Radio is there
Yes they use there own SuperAOSP Kernel
Everything is working and running very well for me. I am curious to see what theming options are available? I am guessing I could try CM themes?
I did have to go into the Wireless and Network settings> Mobile networks and Tick Data Enabled and Un Tick Use only 2G Networks before I could get 3G signal as the toggle in the notification drop down was not working
is this as fast as CM roms uppon2? man downloads so slow lol
I'm gonna try. will report back.
NeoXTC said:
is this as fast as CM roms uppon2? man downloads so slow lol
Click to expand...
Click to collapse
I think it is just as fast maybe even faster
I like the fact that it already has the kernel and everything needed to flash inside the ROM. No need to get GAPPS afterwards or anything like that. Just works right away. There is a lack of features with the launcher but I am yet to test any others
OP: Please add this the first post: to go into the Wireless and Network settings> Mobile networks and Tick Data Enabled and Un Tick Use only 2G Networks before I could get 3G signal as the toggle in the notification drop down was not working
Also any chance of % battery mod? I love this theme but would be better with %
I think you could also add more apps to the extra apps list
It is running really well. I don't like the default launcher. I am going to try a modified TW 4 and report back. Might try to flash some themes too
So, this morning at 5am (yes, stupid time to be playing) I flashed a zip. I have stored on my phone zips for both this and my tablet, and guess what genius did? flashed the wrong friggin one! Very surprised it went through without fault, but hey, **** happens.
So, basically what happened, is my phone became a brick. Black screen, could not boot it up, couldn't et to bootloader or download mode or recovery, tried several things like pulling battery for 30 secs then putting back in, plugging into PC without battery and putting battery in, leaving without battery or SIM for 30 minutes and putting back in, NA friggin DA. Still a brick. Not even the vibration when it first kicks in. Nothing
Starting to think time to call tech support, but as I was trying to plug into PC, I noticed something trying to install, then disappearing real fast. That was my first clue. I opened device manager, plugged phone in, and watched what was happening. A device called OMAP4460 was trying to install for half a second before disappearing, failing, but still, it was something. Even though screen was still blank, and not even bootloader would come up, this was happening. So I googled.
I found this site/thread: http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/. Legija, is a friggin genius Downloaded and unzipped the package, ran the bat, and plugged in the phone. But alas, still no joy
Reread his post - install drivers first...So, putting on my tech hat, how to install drivers if device is not listed, I went into the Actions menu in Task Manager (Win 7), and selected to add legacy hardware. I then chose to install manually, then selected have disk, and browsed to the drivers in the zip package from Legija (all this without device plugged in BTW). I installed the OMAP flash driver successfully, and now showing in task manager with the nice yellow triangle/exclamation mark.
Ran the bat file again, plugged phone in **WITHOUT** battery in phone, and off it went scrolling through it's processes, ninja'n away my f'up. When it completed, put battery back in, held down power, and up she came! Woot! Got back into OS no issues, and I'm one very happy camper.
So I thought i'd share, not thinking anyone else may do the same bloody stupid thing, but maybe a variance, or just have the same symptom (black screen, attempt to install OMAP when plugged into USB), this may just help you! AS for me...deleted all files not for GNEX, i'll continue to stuff around before work, so this is safe
EDIT:
1. Download the zip file from http://forum.gsmhosting.com/vbb/f63...-i9100g-via-usb-cable-freeeeeeeeeeee-1465412/, created by Legija
2. Extract zip to whatever location you're comfortable with (I used Android directory)
3. Open up Device Manager (Hold down Windows Key, press R, the type in devmgmt.msc and press OK)
4. Go to actions menu, select Add Legacy Hardware
5. Choose install manually, then have disk. Browse to where you extracted the zip, select the 'inf' file in usb_drv_windows
6. Choose OMAP, you'll get a popup if on Win 7, continue anyway (driver not signed)
7. Once completed with driver, pull battery out of phone, then plug it into USB
8. Double click omap4460_tuna_hs_pro.bat to start the process. Once you see "Press any key to continue..." close the CMD window and proceed to step 9
9. Unplug from USB, put battery back in, and power-up!
10. Extra step - depending on what's been done, it may 'brick' again - suggest to do a restore or a wipe reinstall afterwards to be certain (mine bricked again next reboot)
Thanks for sharing this find, I'm sure others will find this to be useful
No problem, true believer in sharing my stupid mistakes so other may not follow, or if they do, know how to fix
Oh, in my write up - one change now edited - run the bat with the phone connected to USB **WITHOUT** battery in, once it's finished insert and boot up
Next time I'll be more safe while flashing roms to my phone.
Great find.
wow, this is possible? i thought cwm will prevent you from flashing wrong zips and even if not, why would it kill the bootloader? i was under the impression gnex is close to unbrickable but this topic you linked opened a whole can of worms for me, whats with all these hundreds of people who hard(!)bricked their nexus ... did i miss something?
This was a custom zip I had created myself to do some things on my tab, it ran from install script an install.sh that then went and installed a recovery img. Pretty sure i've never seen this before from any install zip, it was the behaviour I put in mine that allowed it to go through, and I hadn't put into the script to stop if not correct device - lesson learned
BUT - that said, you can do things like this to your phone running scripts, very easy to actually if it's running from su... So never run scripts unless you trust he person whose created it (or have written it yourself and certain of it), know it's definitely for your device, and, most importantly - never miss this step - have had 3 cups of coffee first :good:
Nice find OP, but honestly, how people manage to hard brick a Galaxy Nexus is beyond me.
Though, I am glad you learned from this and actually USED Google to search beforehand. ^^
Theshawty said:
Nice find OP, but honestly, how people manage to hard brick a Galaxy Nexus is beyond me.
Though, I am glad you learned from this and actually USED Google to search beforehand. ^^
Click to expand...
Click to collapse
LOL - easy thing to do if you're screwing with stuff before you're awake, especially scripts. Anything running under superuser can do this effectively, especially scripts working in /dev/block/... All it takes is one FAIL and you're bricked - the question then becomes is it permanent or not! And I always google before I ask questions, otherwise i'd lose my right to abuse others who don't!!! :angel:
rekrapg said:
LOL - easy thing to do if you're screwing with stuff before you're awake, especially scripts. Anything running under superuser can do this effectively, especially scripts working in /dev/block/... All it takes is one FAIL and you're bricked - the question then becomes is it permanent or not! And I always google before I ask questions, otherwise i'd lose my right to abuse others who don't!!! :angel:
Click to expand...
Click to collapse
If it's not permanent, it's not, and never was, a brick.
Sent from my Galaxy Nexus using Tapatalk 2
efrant said:
If it's not permanent, it's not, and never was, a brick.
Click to expand...
Click to collapse
True - but in how many cases would the above be considered a brick?
If I wasn't such a stubborn son of a *****, I would have just called it a brick after the standard revive tricks failed
Theshawty said:
Nice find OP, but honestly, how people manage to hard brick a Galaxy Nexus is beyond me.
Though, I am glad you learned from this and actually USED Google to search beforehand. ^^
Click to expand...
Click to collapse
Well it happens my dude.....at least he took the time out to give a guide and explained how he fixed it just in case someone else does something similar
---------- Post added at 08:56 AM ---------- Previous post was at 08:54 AM ----------
efrant said:
If it's not permanent, it's not, and never was, a brick.
Sent from my Galaxy Nexus using Tapatalk 2
Click to expand...
Click to collapse
True....but most people would not know what to do in this situation and call it a day....at least he searched Google and fixed his problem. Wish more people were like him ya know
---------- Post added at 09:00 AM ---------- Previous post was at 08:56 AM ----------
rekrapg said:
True - but in how many cases would the above be considered a brick?
If I wasn't such a stubborn son of a *****, I would have just called it a brick after the standard revive tricks failed
Click to expand...
Click to collapse
Exactly I said most people would have called it a day.....ZOMGZ MA FONEZ NO LITE UPZ IT HARDSOFT BRICKED!! .....lol all joking aside man your like me I wouldn't have stopped until I was absolutely sure I needed them JTAG boys
Persistence pays off...remember that
Yup. In most cases, there's a way around a problem, you just have to dig until you find it
Congratulations
Saludos desde Ecuador
Though I don't want to have chance to perform your provided method, it's really good to know, in case....
Congratulation and thanks!
rekrapg said:
5. Choose install manually, then have disk. Browse to where you extracted the zip, select the 'inf' file in usb_drv_windows
6. Choose OMAP, you'll get a popup if on Win 7, continue anyway (driver not signed)
7. Once completed with driver, pull battery out of phone, then plug it into USB
8. Double click omap4460_tuna_hs_pro.bat to start the process
9. Once completed, unplug from USB, put battery back in, and power-up!
10. Extra step - depending on what's been done, it may 'brick' again - suggest to do a restore or a wipe reinstall afterwards to be certain (mine bricked again next reboot)
Click to expand...
Click to collapse
In step 6 you say choose omap, but which one? omap flash drive? omap p4460? also i cant install any of those it says it is not signed and it wont install, i tried booting in safe mode and no luck, i tried using the 'bcdedit /set nointegritychecks ON" , rebooted, no luck either
My galaxy nexus is not exactly bricked but i cant get into bootloader, recovery or fastboot , do you think this method could be useful to me?
Chad_Petree said:
In step 6 you say choose omap, but which one? omap flash drive? omap p4460? also i cant install any of those it says it is not signed and it wont install, i tried booting in safe mode and no luck, i tried using the 'bcdedit /set nointegritychecks ON" , rebooted, no luck either
My galaxy nexus is not exactly bricked but i cant get into bootloader, recovery or fastboot , do you think this method could be useful to me?
Click to expand...
Click to collapse
Choose the one closest to what displays on the device manager. I started with the OMAP Flash Drive one and it worked for me, but you can always choose the 'update driver' option and install another if required. Turn off User Account Control in Control Panel/Users and make sure you're on an admin account, as it may by default block the ability to install unsigned drivers, to be honest not sure on that one as it's always been first port of call for me on Win 7 (and Vista).
I also found this that might help: http://www.techspot.com/community/t...signed-drivers-in-windows-vista-7-x64.127187/
Wish I would have found this a week ago! The exact same thing happened to me, except I had been running a working JB ROM for a day or so.
Went jogging, was listening to music, came home, music stopped, screen wouldn't turn on with power button or USB cable with a charger or a computer, but there was a notification LED flashing. No amount of pressing and holding the power button would bring it back to life, so I pulled the battery. After that it was in the exact state your GNEX was in. Not even the vibrate when trying to power it up. After a few hours of charging and trying all sorts of things to breathe life into it (including a battery swap) I ended up returning it to the brick and mortar VZW store and they replaced it because I was under 2 weeks with the phone.
Thanks for posting!
I ran the OMAPFLASH_tuna on my GNex and now, I seem to be stuck at "Sending Data"(SEE last line in the image attached)
The values of 131072 has been like that for over 20 minutes and have not changed. What data is it sending and to who or where?
to those who've used this too, What should happen after this?
thanks...
{
"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"
}
I would be lying if I said I knew exactly what this wonderful tool is doing mate With mine, it ran through in like 30 seconds to completion. I ran it 3 times to be sure! I have 2 suggestions,
1. Sign up to those forums and ask the expert
2. If your device is already 'bricked', it may be worth just disconnecting, closing the CMD window, reconnect and re-run it.
I'm no expert on this application though, I simply found it, it worked for me, so I shared. So option 1 may be your best shot. It's quite likely the bloke who created the tool will be able to let you know the proper path to go down.
EDIT: I am at work atm, so I can't 're-run' it on my device to show you the screen - but I recall it comes up with a 'press any key to continue' prompt after completion (pressing any key just re-runs it).
Funny because another person on GSMHosting is experiencing the same problem and says that his just stops downloading... Just like mines and at the same stop too... hummm...
EDIT March 11, 2016: Finally found a solution and no data was lost!
See post #5.
(is there no way to indicate on the thread that this is solved? I don't know exactly how it works on this forum...)
---------------------------------------------------------------
Hi!
So I've posted my problem on another forum but didn't get any reply, and I just realized I might have more chances to get faster replies on here.
Well, to make it short, I've tried to root my mothers' Galaxy Tab 3 (GT P5210), and as I've already rooted several devices (including another Galaxy Tab) without any problem, I didn't bother saving all the data on it... I'm afraid this was a big error.
I decided to root because it was getting stuck sometimes because of too many things running at a time in the background, and it made the tablet unusable until I reboot it. I wanted to install Greenify and make it work alone so my mother doesn't have anything to worry about but play without the tablet getting stuck. But I needed to root to use Greenify at its best...
As I've rooted several phones before, I know rooting doesn't wipe any data, unlike flashing seems to do. So I wasn't afraid of doing it.
I've followed this tutorial after installing the drivers.
Everything seemed to work correctly, Odin did what it had to do and it succeeded.
Though, now I can't turn on the tablet anymore: if it's turned on and that I press and hold the Power button, the "Samsung Galaxy Tab 3" screen shows up. But it doesn't move, it just stays here and does nothing.
I can turn it off, and try again, but the result is the same.
On the Internet I've read that charging it to 100% could solve the problem, but it doesn't seem to do anything as it was plugged all night and it's the same.
Now I've tried all combinations of buttons, because it was said that a second solution was to wipe the cache partition. But the only combination that works is Volume Down + Power, which brings the Download mode I had to get through in order to run Odin.
I've found this tutorial on here, but I don't even know if the correct word for my situation is "brick". And like many things I've found on the net, the tutorials for unlocking the tablet are for the tablets that have been flashed. But this is not what I wanted to do and I hope this is not what I did. And it doesn't inform if I'll lose data or not... which I'm afraid of.
I made the error of not making any backup before starting the process... I seriously hope nothing is lost.
Is there a way I can restart the tablet correctly again, even if I have to unroot, without losing anything?
Thanks by advance!
(sorry for the double-post)
No one?
Please, at least give me a clue on what I should do, or if there's hope to get back the data from it.
Joey79100 said:
(sorry for the double-post)
No one?
Please, at least give me a clue on what I should do, or if there's hope to get back the data from it.
Click to expand...
Click to collapse
I don't know if you've lost data or if this method will wipe data, but it's what I used to root stock kitkat
Method
Also - I seem to remember that you should uncheck auto reboot, and after flashing is finished power off and back on
Good luck
Thank you for your answer.
The thing is that I've already gone through some steps of the tutorial I linked in the OP (until step 10 / step 11), and when the tablet was meant to reboot, it got stuck on the "Samsung Galaxy Tab 3" screen. I can turn it off and on, but it won't go further than this screen.
I can still bring up the Download Mode (by pressing Volume Down + Power), but there's no way to bring up anything else. Even the debug menu with Volume Up + Power (though I don't know if it was even available this way before trying to root). It will just load the boot screen and nothing more.
I'd try something with the Download Mode only if I can be sure that no data will be lost. If it may erase data, I prefer not doing it and to find a way to get it back before anything else.
Do you know if there's some way to access the memory?
Okay okay... I've struggled a long time with this problem, brought the tabled to a local repair shop but didn't find anything that couldn't risk any data loss... And finally I've found something, so I'll post my solution in case other people have the same problem.
Remember, I could only boot the tablet in Download mode. Every other button combination led me to the boot screen.
The problem was indeed the cache, that I needed to wipe, but without being able to access the Recovery mode there was no way to do it.
-------------------------------------
Solution:
First, I downloaded Odin 3.07 from somewhere else than from the link given in the tutorial (quick search on Google), because I had to untick Auto-reboot. Actually I'm not sure this is needed, but it worked for me with it unticked (while the version of Odin given in the tutorial doesn't let you untick it).
Then, download TWRP for P5210 (a quick search through Google led me to this ). Take out the .tar file from the .zip, but DON'T try to extract anything from the .tar file.
(basically, we'll "install" it onto the tablet using the same method as described in the tutorial)
Boot the tablet in Download Mode (Volume- and Power), choose Continue (Volume+ IF I remember correctly, but it's written anyway), then plug the tablet to your computer.
Run Odin, untick Auto-Reboot (as said before, not sure it's needed, but oh well, it worked...). Then click PDA, select the file you've downloaded (for me it was twrp-2.8.6.0-p5210.tar).
Then press Start, and wait (I waited approx. 2 minutes) until Odin displays "PASS!".
Now unplug the tablet, and turn it off.
Turn it on with Volume+ and Power, this time it will bring you to the TWRP menu (it asks to stay in Read-Only mode or not... choose no). Go to Wipe > Advanced Wipe, and tick Cache ONLY. "Swipe" to start the operation, wait, wait... then, once it's completed, press back until you go back to the main menu, press Reboot > System (then Swipe).
Now the tablet will boot normally. It won't be rooted, but at least it will work again, and fortunately, without any data loss.
You couldn't flash super user from TWRP?
I have the same issue, my Tab 3 is stuck on the Samsung logo.
And the Odin is stuck on the file mentioned above.
Can someone please help?
{
"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 anyone has an old UK device at the bottom of a drawer somewhere which they recollect has a non-English language dictionary from B&N on it, please contact me before trying this.
Spoiler: How I did it
While looking at the CWM Region Changer with someone from the UK trying to get their old NST up and running, it occurred to me that we might be able to do better. Several days and a few out-of-order epiphanies later, I had a rough idea of what needed to happen.
The most important discovery was that the "UK ROM" was still there in the US FW 1.2.2 update. That is to say, if you copied over the splash screens from the UK 1.2.1 update and the Oxford dictionary, you had nearly everything that was different between the two. Except it didn't work. It looked different on boot, but was still the US version (you can tell by looking at Settings which are different in the two versions).
Eventually I took at look at the update script in the B&N zip and saw that it was checking build.prop before doing anything else. I compared that file on the UK 1.2.1 and US 1.2.2 zips and found the major difference was in localization. In two entries "GB" was used instead of "US". Was it that simple?
Yes!
Ah...but it refused to register. In fact, it refused to authenticate, so it never got to asking about your account. The final discovery was the result of a completely idle-brained attempt (because I was out of ideas). I had rooted an instance after skipping OOBE. In the launcher app drawer I saw the familiar junk, including DeviceRegistrator (anyone who has rooted an NST knows this app with the smiley-face icon). I've always thought it was just cyber-detritus, an early version or mock-up left by B&N developers. They were not very tidy, after all. But maybe intents of the app are used in the current registration process. Who knows? Anyway, I tapped on the icon and proceeded to successfully authenticate the device. That got my attention! Then I tried to register with my existing B&N account and password. BINGO! I could see my device on the B&N website under my account and I was able to "buy" a free book using the Shop app (you need a credit card on file with B&N to get even a free book).
So it works for me, in the US.
Because of the changes I made to the original US 1.2.2 update zip, the internal signature is broken, so it cannot be used as an auto-update zip. Hence the need for CWM.
To avoid the necessity to root (for those who would rather not), I removed the broken Lancher.apk in /system/app and replaced it with a simple launcher in the Gingerbread style that is able to run as a system app. So when the device gets to displaying "home", it asks how you want to do that. Initially, the Launcher app is selected so that you have access to an app drawer and the DeviceRegistrator app. After registration, a reboot will present the "home" option choice again. This time the "always" box can be ticked and the B&N "Home" app selected. The Launcher.apk will never be heard from again. Those who go on to root can remove it from /system/app if they wish.
Outstanding issue to be explored: dictionaries. There seems to be a capability for adding different language dictionaries. The User Guide refers to this also. I have not been successful in doing this and don't know whether there ever were any other dictionaries. Since this was not a US option, I'm guessing that the only hard-coded URLs for the dictionary downloads are to non-existent UK servers. I still haven't tracked down where those URLs are. The Nook app for Android is reputed to have the same capability, but when I installed it on one of my rooted tablets, it only had an English dictionary. The format of this db file seemed to be exactly the same as the Oxford dictionary on the UK ROM. I got a Spanish book from B&N and tried to look up a word from there. This gives an option to download a dictionary (as the user guide says) but the result just sends you to the Settings where the only dictionary visible is the default English. So maybe you have to be in another country? Anyway, I could not get the NST to recognize the English dictionary offloaded from the Nook app, despite the apparent structure similarity with the Oxford already onboard. Perhaps there is a database somewhere that would keep track of the dictionaries on the device if the download function were still working. I have not found it. Or, perhaps additional "downloaded" dictionaries have a special place to be (Edit: YES! They go into /data/media/B&N Downloads/Dictionary). Someone with a long memory who has experience with the UK ROM but is not primarily an English speaker might hold the key.
Spoiler: Q&A
--Is this the same thing as the Region Changer?
No. The region changer procedure gives you a device running US firmware (although it looks like B&N still knows it's a UK device based on the serial number and their own records--or they might be identifying its point of origin by the internet connection). This update zip will give you a true UK ROM: the different splash screens, the different settings options (including language) and the ability to enter letters with diacritical marks from the keyboard. It also features the Oxford dictionary. However, it will contact US B&N servers, not the non-existent UK ones.
--Do I need to have an existing B&N account?
I think so. The back door we are using to authenticate and register the device does not have an option for creating a new account.
--Should I deregister my device before doing this?
If you did a region change and are currently running registered US FW 1.2.2, I would recommend deregistering the device before converting to the UK ROM, just to avoid potential conflicts. You can use the same account to register the new ROM. If you have B&N content, it might even show up since it's the same account (mine did).
--Can I purchase books from B&N using the Shop app?
Maybe. I was able to "buy" a free book from B&N and have it appear on my device (note: to purchase even a free book you need to have a credit card on file for your B&N account). But, I am in the US. The B&N Terms of Service says that you have to use (or have on file) a credit card with a US address. There appear to be workarounds like purchasing a US-based cash card, etc. Seems like a lot of extra effort, but apparently some people have done it.
--I live in the US but this sounds interesting. Can I try it too?
Well, I did! The ROM is interesting in a number of ways. It really is a Western European variant, not just UK. German, English, French, Italian and Spanish are the available languages. If your primary language is not English but instead one of these, this might be an attraction. However, there is at least one unexpected consequence. Some external servers will be absolutely convinced you are outside the US. I found this out by trial-and-error when I could not get my Today's Comics app to work. When I changed the region to English (US), it began to work, so I guess the content was region-blocked. I jiggered the Settings app of the UK ROM slightly so it would display the English(US) option.
--I see "Chinese" among the languages! Can my NST display Chinese?
Well, no. Unfortunately the only way to get English(US) to display is to display all of the "development" languages. I tried to suppress "Chinese" but had no luck. There are Chinese characters in DroidSansFallback but the strings for the B&N system were never fully translated (maybe not at all). There is a lot that is translated (appears to be Taiwanese Chinese), probably left from the original phone ROM they used to make the NST OS. However, if you select Chinese any apps you may have installed that are correctly localized for Chinese will display appropriately.
How to do it
Note: I did this on a deregistered device. It does not matter whether your device is currently US FW 1.2.2 or a UK FW 1.2.1.
1. Prepare a CWM card (if you don't already have one, use one of the two sdcard versions). If you've never done this sort of thing before it's probably easiest to download the zip for the Nook Region Changer and follow the instructions there for making the sdcard (steps 1-3). You don't need the two update zips that are on the card, but it's still CWM. If you already have a Region Changer card, you can use it as-is.
2. Download a copy of my 1.2.2 UK update zip. Copy the update zip to the CWM card (the card should be in the card-reader slot of your PC, not in the Nook)
3. Power down your Nook.
4. Insert the CWM card into your Nook and power up. You'll see the logo and maybe the opening menu.
CWM is a little wobbly on the NST. Sometimes it seems to get stuck on a white screen after the logo. If that happens to you, press the lower right hardware button. That generally wakes it up.
Navigating in CWM involves using the upper left hardware button (go back to the previous menu), the two right hardware buttons (go up and down a menu) and the "n" button (do what is highlighted).
5. Move down to "backup and restore". Press "n".
{
"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"
}
6. The menu should show "backup" at the top. Press "n". This will backup your current configuration onto the sdcard.
7. At the conclusion of the backup you should be returned to the top of the menu.
8. Move down (or one step "up") to "advanced". Press "n".
9. Move down one step to "wipe dalvik cache". Press "n".
Then move way down (or a little up) to "yes". Press "n".
Here you may run into another CWM issue. At least for me, CWM has a tendency to freeze after any kind of wipe. If that happens to you, don't panic. If the buttons don't seem to be responsive, press and hold the power button. If the device does not reboot back into CWM, release the power button and press and hold again. Eventually the device will reboot, taking you to the top of the menu again.
10. From the top of the menu move down to "wipe data/factory reset". This option is just like the previous one, including the potential freeze. Do it.
11. From the top of the menu, move down to "install zip from sdcard". Press "n".
12. The top of the next menu says "choose zip from sdcard". Press "n".
13. Move to select the nook_1_2_2_UK_update_CWM.zip and press "n", etc.
14. After the update is complete you need to return to the top of the menu where it says "reboot now" (if you are not already there). At that point, remove the CWM card from the device and press "n" to reboot.
15. Your Nook will boot into the UK ROM setup. You'll see the familiar multi-lingual splash screen, the marching dots, and finally come to a Language choice screen.
Select whichever language you prefer. You can change this later from Settings.
16. The next screen is the "Welcome" screen.
You are now going to execute a "skip OOBE". Since registration fails in the usual setup wizard, we will have to go in the back door, so to speak. At the "Welcome" screen, press and hold the upper right hardware button and swipe your finger across the top of the screen from left to right. You should see a "Factory" button appear in the upper left corner of the screen. Tap it.
17. Now you are on the Factory screen.
Again, press and hold the upper right hardware button and tap the screen in the lower right corner. You should see a "Skip OOBE" button appear on the screen. Tap it.
18. OK, so now you are faced with a choice which I have added to the ROM in order to finesse the registration issue without needing to root the device. There should be two options listed on the screen: Home (the B&N home screen) and Launcher (I added this). For now tap on "Home". The B&N home screen loads up with the infinite spinner in the lower half (no registration, no wi-fi, no data).
19. Press the "n" button and select "Settings". Set up a wi-fi connection and set the time zone and time display format. Leave wi-fi on. Use the power button to shut the device off.
20. Power up your Nook. When it has passed the marching dots it will ask you again whether you want "Home" or "Launcher". This time, choose "Launcher".
A simple Android launcher screen is displayed. All you care about is the app drawer, that little square of tiny squares in the center of the bottom of the screen. Tap it.
21. There is a bunch of stuff (mostly junk) in the app drawer. Resist the impulse to fool around there. Keep your eyes on the prize! Locate the DeviceRegistrator app (stupid smiley-face icon). Tap it. Check to be sure your wi-fi is on.
22. You need to do two things here.
First, register (authenticate) the device itself. That's the first button on the left in the first row. Tap that. If all is going well (and your wi-fi is on) you should get a confirmation alert. After that, type in your username (email) and password for your B&N account. There is no option here to create an account, so you need to have one already established for this to work. After you've typed in the information, tap on "Register User". You should get a confirmation alert. You can now turn off wi-fi. Press the "n" button and select "Settings". Check Device Info>About your NOOK. If everything went according to plan you should see that it is registered.
23. Shut down the Nook. Power up one more time. After the marching dots you are again faced with the choice of "Home" or "Launcher". Before you make your selection, tap on the little (empty) checkbox. This will make your next move permanent. Now tap on "Home".
You'll never hear from "Launcher" again. It will just languish in /system/app with all the other unused apps and your Nook is now registered and good to go!
If you want to root and further customize your Nook, select one of the updated NookManager packages. I strongly recommend using NookManager to make a backup of your device before rooting. The CWM backup you made at the beginning of this process is not a complete nandroid backup and you'd be better off with one before you make any more changes. If you are not interested in rooting, you may want to make another backup with the CWM card at this point and then put it away somewhere safe. Just in case.
I've just followed these instructions on my 1.2.0 UK Nook Simple Touch. In the UK, and it works perfectly. Thanks very much!
ashh87 said:
I've just followed these instructions on my 1.2.0 UK Nook Simple Touch. In the UK, and it works perfectly. Thanks very much!
Click to expand...
Click to collapse
Thanks a lot for the feedback. Now we know it was not just a one-time fluke for me. I'm glad it worked for you as well.
Also worked for me. After registering I used NookManager to root it, then installed the latuk kernel from this post with CWM and it's now UK 1.2.2 and external keyboard supporting. That's all I was looking for. Another thumbs up for the repeatability of your method. Thanks for the detailed instructions.
A quick question - in step 23 ("never hear from Launcher again") above, if I accidentally make the wrong one the default, how would I get the launcher selection screen back again on startup?
markeq said:
A quick question - in step 23 ("never hear from Launcher again") above, if I accidentally make the wrong one the default, how would I get the launcher selection screen back again on startup?
Click to expand...
Click to collapse
Let's say--hypothetically, of course--that you did that. There are two ways around it.
1. If you rooted with the "traditional" or "stealth" versions of NookManager, you have ES File Explorer. You can use it to access the App Manager and remove the defaults from the "Launcher" (or "Home", or whatever). After doing this, a reboot will present you with the choices again. Screenshots for a likely sequence below.
2. A more general quick-and-dirty method that will work in any situation: install yet another launcher app. When you reboot, the activity picker will see a new option and give you your choices again. When you've got it right, just uninstall the additional launcher (which you never have to run for this method to work). Here's a link to another simple and relatively useless launcher that will fit the bill.
nmyshkin said:
Move to select the nook_1_2_2_UK_update_CWM.zip and press "n", etc.
Click to expand...
Click to collapse
@nmyshkin have you ever seen an issue where CWM freezes on this step under opening update package... ?
i have left it on this step for 2-3 hours - im guessing it doesnt normally take this long ?
i also had the same problem in the exactt same place when i tried running the nook_1_2_update_US_CWM.zip region changer
any ideas on what i could try different to get working ? otherwise im stuck on a de-registered 1.2.1uk so my only option might be to nuke all b&n and go custom ereader route (which is probably fine tbh)
A couple of minutes is all it should take.
Check out the update using a desktop zip utility.
Does it look normal?
Renate said:
A couple of minutes is all it should take.
Check out the update using a desktop zip utility.
Does it look normal?
Click to expand...
Click to collapse
yeah it looks normal on my computer (im running popos although i cant see how that would change anything)
Well, you can always do it semi-manually, at least you'll get feedback.
Extract META-INF\com\google\android\update-binary
Go to TWRP and use ADB to push both the (original) zip and the (extracted) update-binary somewhere useful.
Use ADB (you do have a rooted prompt?)
Code:
# chmod 755 update-binary
# ./update-binary 2 1 whatever.zip
You'll get text out of this and maybe figure out what the problem is.
cyberboy666 said:
@nmyshkin have you ever seen an issue where CWM freezes on this step under opening update package... ?
i have left it on this step for 2-3 hours - im guessing it doesnt normally take this long ?
i also had the same problem in the exactt same place when i tried running the nook_1_2_update_US_CWM.zip region changer
Click to expand...
Click to collapse
Hmm...
Well, two things come to mind. First, the zip package is NOT an update. You're just supposed to choose "install zip from sdcard". So if you chose an update zip instead, that could be a problem, although I would expect CWM to say it couldn't find an update zip rather than just hang. At least that's what it has done with me before when I've made the wrong choice.
Second, since you have the same problem with the "region changer" zip, is it possible that your CWM card is bad? You might want to go straight to the source: https://forum.xda-developers.com/t/...od-based-recovery-fixed-backup-issue.1360994/. Either sdcard version should work fine, depending on the size of your card.
FWIW, these are the MD5 values for the various files in question, just in case you've got a file corruption problem somewhere:
2 gb CWM zip: 61a9cfea527a81e17c9b5bc751af27ce
128 gb CWM zip: 670bccc38737a722eaed75871bb36d35
Unofficial UK 1.2.2 FWzip: fbaaac9957483850cb723d46a518c064
Region changer zip: bca752409c8cc6da43658c7d537dfdf1
nmyshkin said:
Hmm...
Well, two things come to mind. First, the zip package is NOT an update. You're just supposed to choose "install zip from sdcard". So if you chose an update zip instead, that could be a problem, although I would expect CWM to say it couldn't find an update zip rather than just hang. At least that's what it has done with me before when I've made the wrong choice.
Second, since you have the same problem with the "region changer" zip, is it possible that your CWM card is bad? You might want to go straight to the source: https://forum.xda-developers.com/t/...od-based-recovery-fixed-backup-issue.1360994/. Either sdcard version should work fine, depending on the size of your card.
FWIW, these are the MD5 values for the various files in question, jus tin case you've got a file corruption problem somewhere:
2 gb CWM zip: 61a9cfea527a81e17c9b5bc751af27ce
128 gb CWM zip: 670bccc38737a722eaed75871bb36d35
Unofficial UK 1.2.2 FWzip: fbaaac9957483850cb723d46a518c064
Region changer zip: bca752409c8cc6da43658c7d537dfdf1
Click to expand...
Click to collapse
omg thanks ! yes i think issue was with CWM card - i flashed a new one from the link you gave and now it is working
and also thanks for the advice @Renate - i want to get set up/learn to send ADB anyway so this is helpful
Hmm, well, I didn't know that.
OTOH, you would have seen that you couldn't find an update-binary in that zip.
nmyshkin said:
While looking at the CWM Region Changer with someone from the UK trying to get their old NST up and running, it occurred to me that we might be able to do better. Several days and a few out-of-order epiphanies later, I had a rough idea of what needed to happen.
Click to expand...
Click to collapse
Another success, from UK 1.2.1 to your pseudo-UK 1.2.2.
It halted, as in your examples, after both wipes.
Great step-by-step instructions. Spot on. I wouldn't say I'm a complete novice at such things, but it's always great to have such detailed instructions to make sure I don't go and do something daft.
Thanks so much! Do you have any kind of buy-me-a-coffee link?
(Now to work out what my battery issues were, if they come back, 'cos I know from disassembling the hardware and testing the battery that it's not the battery!)
jewelie said:
Another success, from UK 1.2.1 to your pseudo-UK 1.2.2.
It halted, as in your examples, after both wipes.
Great step-by-step instructions. Spot on. I wouldn't say I'm a complete novice at such things, but it's always great to have such detailed instructions to make sure I don't go and do something daft.
Thanks so much! Do you have any kind of buy-me-a-coffee link?
(Now to work out what my battery issues were, if they come back, 'cos I know from disassembling the hardware and testing the battery that it's not the battery!)
Click to expand...
Click to collapse
I'm glad it worked for you. That's my reward
Unless your glowlight is not turning off completely, I can't think of any other factor on a stock system that would drain the battery fast, barring some unknown hardware issue.
Hopefully this sorts it out.
On top of the running an unregistered device, I've read that manually tapping the power button to force it to sleep can cause battery issues, which is what I had been doing. Other possibilities that have been suggested to me are corrupt books, and maybe having the WiFi off.
I did notice that the internal disk was seen by windows and Linux as having an fs error, and windows couldn't fix it. That actually persisted following the instructions you gave above, it seems it didn't actually wipe the 240Mb internal disk so some files and settings and of course the corruption remained, which was a surprise, so I an erase and deregister to go properly from scratch. That did clean in!
Device is now on sleep with wifi off and no books after the fresh start. I also hacked the cover I was using to make sure it wasn't touching the screens or buttons. It's at 79% now, let's see what the percentage goes to over the next few days...
EDIT: BTW The reason I know it's not the battery itself is because I disassembled it and tested the battery through a few 0.5A charge & discharge cycles and gave it a week to see if there was any significant self discharge - madly, it still has almost the full 1500mAh capacity - impressive for a device that's been going for 10yrs now!
jewelie said:
I've read that manually tapping the power button to force it to sleep can cause battery issues, which is what I had been doing.
Click to expand...
Click to collapse
I think this has been debunked in the distant past although I can't put my finger on the particular post.
jewelie said:
I did notice that the internal disk was seen by windows and Linux as having an fs error, and windows couldn't fix it. That actually persisted following the instructions you gave above, it seems it didn't actually wipe the 240Mb internal disk so some files and settings and of course the corruption remained, which was a surprise, so I an erase and deregister to go properly from scratch. That did clean in!
Click to expand...
Click to collapse
That part is interesting and the initial result is not surprising. Unfortunately CWM cannot do a thorough wipe unlike, say, TWRP. A factory re-image is the most thorough cleaning I'm aware of, followed by the deregister/erase, then with CWM bringing up the rear. The reason I didn't include a factory re-image at the beginning of the process is that I wanted to keep it simple and not scare away those averse to anything approaching root. The 8-failed-boot-attempts method for a factory re-image is tremendously tedious and involves close timing and dexterity. OTOH, a NookManager card can initiate the process with the push of one hardware button. But that means making yet another card and flirting with the whole root thing (not necessary to root just to do the factory re-image).
The internal disk error may or may not have something to do with the battery drain. You'll find out. When I was doing a lot of testing with battery life a long time ago I found that a loss of 1% was typical overnight if the device was just sleeping. Of course, that's with whatever I had going on my system at the time.
@nmyshkin Thank you so much for the detailed guide.
I followed all the steps without any issue. I even got the freezing bug after clearing the Dalvik cache. But followed your steps, pressed on the power button twice and it restarted.
I used a 2Gb memory card and used the sd_2gb_clockwork-rc2.zip and I've written the image with WinImage 8.50.
nmyshkin said:
The internal disk error may or may not have something to do with the battery drain. You'll find out. When I was doing a lot of testing with battery life a long time ago I found that a loss of 1% was typical overnight if the device was just sleeping. Of course, that's with whatever I had going on my system at the time.
Click to expand...
Click to collapse
I'm seeing about 3% drop (as seen in settings -> about) every two days, which sounds about in the right ball park?
jewelie said:
I'm seeing about 3% drop (as seen in settings -> about) every two days, which sounds about in the right ball park?
Click to expand...
Click to collapse
I'd say so, especially if you've been doing any reading at all.
nmyshkin said:
I'd say so, especially if you've been doing any reading at all.
Click to expand...
Click to collapse
Update: It's over a month later, battery is still on 26%. Touch wood, it's fixed. THANK YOU!
Hello everyone good day.
Sadly my phone Samsung galaxy A22 has stumbled into a boot loop been happening for couple days it started when I put the phone on charge and heard it vibrating to which It was constantly rebooting over and over as soon as the Home Screen loads after a second it just reboots I tried to do a reset using power + volume down and no luck also tried wipe cache partion in the recover menu and repair apps but no luck tried searching YouTube for fixes and also called a phone repair shop and said it’s a tough one as I want to keep my data meaning I can’t do a factory reset as I have a lot of stuff I need on the phone so I am reaching out here as a last resort it would make my day if someone could help thanks.
Note: after many restarts the phone managed to come on a couple of times to which after entering my pin a pop up would happen saying “ serious software issue detected check for update “ if i click check the message goes away then it says android starting but fails to start up after 30 seconds to a minute it just re boots again I had some hope as it happened a few times it allowed me to put my pin in but on the android starting screen it would never get past and eventually reboot again I haven’t updated the phone for a while so is it also possible to update from download mode without losing my data or do I need some room for that??
Read I could try safe mode unfortunately that didn’t work either
Try downloading your phones firmware on samfw and installing it with the HOME_CSC, not CSC without HOME!!!
HeroGamer007 said:
Try downloading your phones firmware on samfw and installing it with the HOME_CSC, not CSC without HOME!!!
Click to expand...
Click to collapse
Hey how can this be done? Never done this before any guides you could link me to?
ThePhoneGuyy1 said:
Hey how can this be done? Never done this before any guides you could link me to?
Click to expand...
Click to collapse
IF SOMETHING FAILS DO NOT PROCEED TO AVOID ANY FURTHER DAMAGES!!!
I AM NOT RESPONSIBLE FOR ANY DAMAGES DO TO YOUR PHONE!!!
1. Power off your Phone
2. Now hold the volume up + down button and while doing that plug in a usb cable that is connected to your pc
3. You should see some kind of blue screen, press volume up and it will show "Downloading..."
4. Now Download Odin3, unzip it and Open the EXE on your PC (Click OK on the Warning)
5. You should see COM0 (the 0 can be any other number) under the ID:COM label, if it doesnt appear check your USB connection
6. Download your Device's Firmware:
go to SamFW.com and search for your model on the big Search Bar, if you don't know if its the F or M variant check the packaging, it should be on there. then Click on the Country you're in (or the Country your phone is from) and scroll down until you see this section:
{
"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"
}
Click on the Most-Top Version and select "Download on Browser" (you might need to login with google).
7. after that you should have 5 files starting with AP_, BL_, CP_, CSC_ and HOME_CSC
8. go into Odin and click "BL", then select the "BL_" file, do that for BL, AP and CP
9. now select the "HOME_CSC_" file on the "CSC" button, make sure its the HOME_CSC File!!!
10. after you made 10 time sure its the HOME_CSC file click start and pray
11. after the whole process your device should reboot and work.
HeroGamer007 said:
IF SOMETHING FAILS DO NOT PROCEED TO AVOID ANY FURTHER DAMAGES!!!
I AM NOT RESPONSIBLE FOR ANY DAMAGES DO TO YOUR PHONE!!!
1. Power off your Phone
2. Now hold the volume up + down button and while doing that plug in a usb cable that is connected to your pc
3. You should see some kind of blue screen, press volume up and it will show "Downloading..."
4. Now Download Odin3, unzip it and Open the EXE on your PC (Click OK on the Warning)
5. You should see COM0 (the 0 can be any other number) under the ID:COM label, if it doesnt appear check your USB connection
6. Download your Device's Firmware:
go to SamFW.com and search for your model on the big Search Bar, if you don't know if its the F or M variant check the packaging, it should be on there. then Click on the Country you're in (or the Country your phone is from) and scroll down until you see this section: View attachment 5891443
Click on the Most-Top Version and select "Download on Browser" (you might need to login with google).
7. after that you should have 5 files starting with AP_, BL_, CP_, CSC_ and HOME_CSC
8. go into Odin and click "BL", then select the "BL_" file, do that for BL, AP and CP
9. now select the "HOME_CSC_" file on the "CSC" button, make sure its the HOME_CSC File!!!
10. after you made 10 time sure its the HOME_CSC file click start and pray
11. after the whole process your device should reboot and work.
Click to expand...
Click to collapse
I’ll make sure to give it a good read I appreciate that hopefully this can fix for good quick question before i proceed do I need enough storage for this to update because I remember it being almost full if that’s the case is this possible by inserting an SD card without losing data? Just wanted to check before I proceed as my storage was close to being full
ThePhoneGuyy1 said:
I’ll make sure to give it a good read I appreciate that hopefully this can fix for good quick question before i proceed do I need enough storage for this to update because I remember it being almost full if that’s the case is this possible by inserting an SD card without losing data? Just wanted to check before I proceed as my storage was close to being full
Click to expand...
Click to collapse
It shouldn't need storage, it rewrites the system files and does not just "adds" them, so it should be at max 1-5 hundred MB bigger
HeroGamer007 said:
It shouldn't need storage, it rewrites the system files and does not just "adds" them, so it should be at max 1-5 hundred MB bigger
Click to expand...
Click to collapse
Perfect thank you so much will give this a try soon will update you what happens really appreciate you taking the time
ThePhoneGuyy1 said:
Perfect thank you so much will give this a try soon will update you what happens really appreciate you taking the time
Click to expand...
Click to collapse
Oh also to check the Country from which your phone is (you need to select that when downloading firmware) you can apparently use recovery mode, go into recovery mode (volume up + power while being plugged into a pc) and check if it says something with CSC-Code on the bottom, the 3-digit code after that is the Country Code which you will need to download.
T0stbrot said:
Oh also to check the Country from which your phone is (you need to select that when downloading firmware) you can apparently use recovery mode, go into recovery mode (volume up + power while being plugged into a pc) and check if it says something with CSC-Code on the bottom, the 3-digit code after that is the Country Code which you will need to download.
Click to expand...
Click to collapse
Sadly I haven’t been able to get this to fix used Odin and downloaded correct version for my model and csc code Odin said pass but phone still in boot loop
ThePhoneGuyy1 said:
Sadly I haven’t been able to get this to fix used Odin and downloaded correct version for my model and csc code Odin said pass but phone still in boot loop
Click to expand...
Click to collapse
I seen a video of someone using Odin once done there phone rebooted and showed a pop up saying updating apps etc along those lines but for me it just rebooted after Odin showed pass then bootloop again and a menu saying phone couldn’t start properly and get the same message “ serious software issue check for update “
ThePhoneGuyy1 said:
I seen a video of someone using Odin once done there phone rebooted and showed a pop up saying updating apps etc along those lines but for me it just rebooted after Odin showed pass then bootloop again and a menu saying phone couldn’t start properly and get the same message “ serious software issue check for update “
Click to expand...
Click to collapse
Try going into recovery maybe and deleting the cache and repair apps
T0stbrot said:
Try going into recovery maybe and deleting the cache and repair apps
Click to expand...
Click to collapse
Is that wipe cache partion? If so sadly not work for me and repair apps no fix but upon some research I’ve read it’s possible the storage can cause a bootloop also? Not sure if true but my phone was literally almost full as unfortunately didn’t make some room in time it seems this is most likely the reason as before bootloop I never installed any updates or did anything just simply put the phone on charge then it bootloop I’ve read that because there is almost no storage the phone just can’t boot up properly? No idea tbh but seems most reasonable as of now :/
ThePhoneGuyy1 said:
Is that wipe cache partion? If so sadly not work for me and repair apps no fix but upon some research I’ve read it’s possible the storage can cause a bootloop also? Not sure if true but my phone was literally almost full as unfortunately didn’t make some room in time it seems this is most likely the reason as before bootloop I never installed any updates or did anything just simply put the phone on charge then it bootloop I’ve read that because there is almost no storage the phone just can’t boot up properly? No idea tbh but seems most reasonable as of now :/
Click to expand...
Click to collapse
Also whilst my phone was bootlooping I got a menu similar to recovery menu saying android failed and a few options I believe was
1) try again
2) wipe app data
3) power off
Also a message saying if you don’t want to lose any data then it should be taken to a technician however one of the places I called said there is not much they can do as I wanna keep my data :/
Does it say wipe all data or wipe app data?
T0stbrot said:
Does it say wipe all data or wipe app data?
Click to expand...
Click to collapse
Wipe app data if I remember right it said about wiping the data of apps and configuration so this has also lead me to thinking it could be an internal storage also no idea as phone says there is a serious software issue it’s been a nightmare hopefully fix eventually just worried about my data I believe wipe app data will keep photos and videos safe but it would log out all my emails and wipe all my apps also? :/
ThePhoneGuyy1 said:
Wipe app data if I remember right it said about wiping the data of apps and configuration so this has also lead me to thinking it could be an internal storage also no idea as phone says there is a serious software issue it’s been a nightmare hopefully fix eventually just worried about my data I believe wipe app data will keep photos and videos safe but it would log out all my emails and wipe all my apps also? :/
Click to expand...
Click to collapse
Yeah it will delete all app data, so for example your google login or email login, it should keep your photos tho as that is not app data
T0stbrot said:
Yeah it will delete all app data, so for example your google login or email login, it should keep your photos tho as that is not app data
Click to expand...
Click to collapse
Hmm do you think this is pretty much the last resort for me to try if I can keep pics and videos I guess that’s a bonus just would have to pray it does let me boot my phone up and that I can regain access to emails and other stuff via logins not all wrote down so I guess at this point with nothing I’ve tried working seems one of the last options unless there is other ways to extract data whilst phone is in bootloop but haven’t found many also
Did you setup any 2FA Authenticator apps that aren't synced with a cloud? That would be pretty dumb and you probably won't be able to login except you saved the backup codes. But otherwise if it really only deletes app data it should be fine, and as long as you have access to your email you should be able to reset all your passwords.
Do you can share your phone recovery mode picture with download mode