Related
!!!This is NOT for Nexus S 4G!!!
Hi all,
Bootloader version updated to I9020XXLC2, in JB OTA(4.1.1, JRO03E)
IMO, Bootloader is important because it's optimized for OS(Dunno it's exactly true)
For someone doesn't want to flash OTA and update Bootloader version, I decided upload this here
**How to check bootloader version?
Turn off ur phone, and then, press volume up button and power button. It will show u bootloader version.
1)
Here is fastboot flashable file in attatchment.
You need to type
Code:
fastboot flash bootloader bootloader.img
FYI, http://forum.xda-developers.com/showthread.php?t=1116884
-Fastboot zip file is in this Thread. "Method 2"
2)
Flash via CWM-Zip file.
Then power-off your device(thanks to SuperSaiyan.IV, I dunno why)
Thanks to lar5, added md5check sum.
031ae14f0986dcfa26c730815f111f6e *bootloader.img
42f7a62af2231e46cab7378f9c17eddb *CWM-Bootloader.zip
No cwm version?:/
Sent from my Nexus S using xda app-developers app
CWM version is uploaded
Sent from my Nexus S using xda app-developers app
Is there a new radio too ? This is 9020 only right ?
Sent from my Nexus S using xda app-developers app
can i update on ICS too? i want to stay on ICS(don't want update to JB for now)
This new bootloader can port me some benefits on ICS?
thank you....
daniozzo83 said:
can i update on ICS too? i want to stay on ICS(don't want update to JB for now)
This new bootloader can port me some benefits on ICS?
thank you....
Click to expand...
Click to collapse
Nope, no faster phone, no better reception... it's just only the bootloader.
FloHimself said:
Nope, no faster phone, no better reception... it's just only the bootloader.
Click to expand...
Click to collapse
thx for answer.
Another question: i tried jelly bean with full image (not upgrading with ota)...
I tried then flashing from CWM recovery doing full wipe data etc.
Did i installed new bootloader in this way? i noted some battery drain and UI lag. Maybe i had old bootloader and that created some problem?
MrSmileyJr said:
Is there a new radio too ? This is 9020 only right ?
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
There is no new radio.
Sent from my Nexus S using xda app-developers app
daniozzo83 said:
thx for answer.
Another question: i tried jelly bean with full image (not upgrading with ota)...
I tried then flashing from CWM recovery doing full wipe data etc.
Did i installed new bootloader in this way? i noted some battery drain and UI lag. Maybe i had old bootloader and that created some problem?
Click to expand...
Click to collapse
I don't know what Jelly Bean "full image" you have flashed and whether the bootloader was included. But as said before: the bootloader isn't related to any battery drain or UI lag. It's just the bootloader, i.e. a piece of software bringing the phone into a state it can run the OS.
FloHimself said:
I don't know what Jelly Bean "full image" you have flashed and whether the bootloader was included. But as said before: the bootloader isn't related to any battery drain or UI lag. It's just the bootloader, i.e. a piece of software bringing the phone into a state it can run the OS.
Click to expand...
Click to collapse
is it like bios on a pc?
daniozzo83 said:
is it like bios on a pc?
Click to expand...
Click to collapse
http://www.tested.com/news/feature/1879-know-your-android-bootloaderwhat-it-is-and-why-it-matters/
Maybe this helps?
Sent from my Nexus S using xda app-developers app
ioplkj13 said:
http://www.tested.com/news/feature/1879-know-your-android-bootloaderwhat-it-is-and-why-it-matters/
Maybe this helps?
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
ty mate.... useful
ioplkj13 said:
CWM version is uploaded
Sent from my Nexus S using xda app-developers app
Click to expand...
Click to collapse
Thanks mate
Sent from my Nexus S using xda app-developers app
You should include for which model this is.
Thanks for the info in your OP links! Still have a couple questions. I'm using the latest Jellybelly release, all is flashed, all is well, no issues at all. But still want the new bootloader, is this new bootloader the same for all nexus s's?
I have the i9020A and just want to make sure this won't cause an issue. Also, after installing the new bootloader, will it require being unlocked again? May sound silly, but I'd like to know before potentially erasing my SD.
Thanks!
Can anybody provide the MD5 sum of the 2 files?? I am not sure the downloading is exactly okay.
xdoit said:
Can anybody provide the MD5 sum of the 2 files?? I am not sure the downloading is exactly okay.
Click to expand...
Click to collapse
031ae14f0986dcfa26c730815f111f6e *bootloader.img
42f7a62af2231e46cab7378f9c17eddb *CWM-Bootloader.zip
I flashed this on my 9020A through CWM, no issues, boot loader remained unlocked.
Edit nvm
mixtapes08 said:
Edit nvm
Click to expand...
Click to collapse
What's nvm..?
Sent from my Nexus S using xda app-developers app
hi guys, I am not sure whether I am in the right sections. I have a Asus eee pad slider sl101.just now I tried flashing a new ROM using power button and volume down. I flashed a cm9 for tf101.now it is stocked at the boot screen with nothing happening. what have I did wrong? Thanks in advance.
Sent from my HTC Desire S using xda premium
hisname said:
hi guys, I am not sure whether I am in the right sections. I have a Asus eee pad slider sl101.just now I tried flashing a new ROM using power button and volume down. I flashed a cm9 for tf101.now it is stocked at the boot screen with nothing happening. what have I did wrong? Thanks in advance.
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
You flashed the ROM using CWM, correct? What was the name of the ROM?
yes, it is correct I flashed using Clockworkmod by team rogue. I am not really sure what ROM I flashed. but I attached a image of the boot screen. but the ROM I flashed was for TF101(which I think should be compatible with my SL101). or do I need to flash a Asus stock recovery image to solve this issue? BTW is this a boot loop? thanks for the reply.
Edit: I found out the ROM that I flashed.
md5sum: dd80806298385a7a8057b21b384d389f. This is the stable ROM for TF101
Sent from my HTC Desire S using xda premium
hisname said:
yes, it is correct I flashed using Clockworkmod by team rogue. I am not really sure what ROM I flashed. but I attached a image of the boot screen. but the ROM I flashed was for TF101(which I think should be compatible with my SL101). or do I need to flash a Asus stock recovery image to solve this issue? BTW is this a boot loop? thanks for the reply.
Edit: I found out the ROM that I flashed.
md5sum: dd80806298385a7a8057b21b384d389f. This is the stable ROM for TF101
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
If you're getting a bootloop, then something either something went wrong with the installation or with the ROM. I don't think it's kernel related since you're getting to the ROM's boot animation. I would try to relash to ROM or try a different one that clearly states it's compatible with the Slider, because I still don't know which one you flashed.
then how do I flash another ROM when the slider is still in the boot animation? also what ROM is recommended for the slider? I have searched most forums and most of them are for the transformer.
Sent from my HTC Desire S using xda premium
I think even on that rom you should be able to boot in recovery mode. Perhaps you need to wipe data / cache and reboot again.
farsight73 said:
I think even on that rom you should be able to boot in recovery mode. Perhaps you need to wipe data / cache and reboot again.
Click to expand...
Click to collapse
even I boot into recovery mode, it is only "clear data" or "android", if I wipe data, wouldn't my data be gone?
Sent from my HTC Desire S using xda premium
hisname said:
even I boot into recovery mode, it is only "clear data" or "android", if I wipe data, wouldn't my data be gone?
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
A ROM that is guaranteed to work on the Slider is Android Revolution, created by mike1986. If I were you, I would just start over completely and flash that ROM.
Solar.Plexus said:
A ROM that is guaranteed to work on the Slider is Android Revolution, created by mike1986. If I were you, I would just start over completely and flash that ROM.
Click to expand...
Click to collapse
so I just connect my slider to the computer, go into recovery, and flash the ROM?
Sent from my HTC Desire S using xda premium
after flashing the Android revolution hd, it got worse. Now it does not even go into boot animation. It is stuck on asus screen
Sent from my HTC Desire S using xda premium
hisname said:
after flashing the Android revolution hd, it got worse. Now it does not even go into boot animation. It is stuck on asus screen
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
Did you install the compatability pack
hisname said:
so I just connect my slider to the computer, go into recovery, and flash the ROM?
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
This here doesn't sound right. You don't connect your Slider to a computer to flash ROMs. You flash the ROM (zip file) from recovery on your Slider.
Also, Android Revolution doesn't require flashing any compatibility pack. Since it is already based on Asus stock ROM, it already has the necessary files.
Solar.Plexus said:
This here doesn't sound right. You don't connect your Slider to a computer to flash ROMs. You flash the ROM (zip file) from recovery on your Slider.
Also, Android Revolution doesn't require flashing any compatibility pack. Since it is already based on Asus stock ROM, it already has the necessary files.
Click to expand...
Click to collapse
oh ok, but after flashing android revolution hd, it just got onto asus boot screen. do I do a full factory wipe to salvage this situation?
Edit: i took a video of what i did and uploaded to my dropbox account.here is the link: http://db.tt/YhJUuT7N
Sent from my HTC Desire S using xda premium
zachf714 said:
Did you install the compatability pack
Click to expand...
Click to collapse
what compatability pack are u talking about?mind if u put a link?
Sent from my HTC Desire S using xda premium
hisname said:
what compatability pack are u talking about?mind if u put a link?
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
In the development section for the tf101
---------- Post added at 11:18 AM ---------- Previous post was at 11:14 AM ----------
hisname said:
what compatability pack are u talking about?mind if u put a link?
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
It's called slider SL101 compatability pack
hisname said:
what compatability pack are u talking about?mind if u put a link?
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
Don't worry about the compatibility pack for the Android Revolution ROM.
To flash this ROM, you MUST first flash the SUPER WIPE file that is listed in the Android Revolution thread.
Solar.Plexus said:
Don't worry about the compatibility pack for the Android Revolution ROM.
To flash this ROM, you MUST first flash the SUPER WIPE file that is listed in the Android Revolution thread.
Click to expand...
Click to collapse
the lite version or full version?
Sent from my HTC Desire S using xda premium
hisname said:
the lite version or full version?
Sent from my HTC Desire S using xda premium
Click to expand...
Click to collapse
In theory, either should be fine.
ok, after flashing the super wipe lite and I flashed the ROM, it is still stuck on asus screen, do I use a nandroid back up and use the super wipe full version? it has been a week already and my problem still can't be solved. I am really getting very desperate.... what had happened????
Edit: problem solved. I use a factory wipe and flash a Cm9 and it worked!! but just a small question, what is the command to mount and unmount SD card in terminal emulator? my SL101 can't read my SD card
Sent from my HTC Desire S using xda premium
I need help.
Today i tried flashing the faux kernel using CWM and when my phone rebooted got stuck at boot (google screen)
I rebooted in recovery and tried flashing again but the same problem happen.
Now im stuck,
I can't load any file because on the computer i am using the drivers are not installed.
What shall I do?
sampy14 said:
I need help.
Today i tried flashing the faux kernel using CWM and when my phone rebooted got stuck at boot (google screen)
I rebooted in recovery and tried flashing again but the same problem happen.
Now im stuck,
I can't load any file because on the computer i am using the drivers are not installed.
What shall I do?
Click to expand...
Click to collapse
So you have no backup or another file you can flash? If not, install drivers...
This also belongs in QA.
Sent from my Nexus 4 using Tapatalk 2
Install correct drivers and flash stock rom with adb. Else use the toolkit.
CMNein said:
So you have no backup or another file you can flash? If not, install drivers...
This also belongs in QA.
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
Sorry i tought i posted it in QA.
I can't get to install drivers with the phone turned on in fastboot.
sampy14 said:
Sorry i tought i posted it in QA.
I can't get to install drivers with the phone turned on in fastboot.
Click to expand...
Click to collapse
Are you running Windows?
Sent from my Nexus 4 using xda app-developers app
Ace42 said:
Are you running Windows?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
yes I am
We can't debug your windows pc... Fast boot drivers can/will install fine. Try another computer and see if the toolkit will get you going.
Edit: all you need to do is read, read the stickies and read tutorials on how to return to stock. The drivers will install without being inside Android
Sent from my Nexus 4 using xda premium
sampy14 said:
yes I am
Click to expand...
Click to collapse
Remove the current n4 drivers with device manager in windows. Then find the proper drivers here on xda in the n4 general section. After that you should be able to use the toolkit to boot to recovery or flash a stock build.
Sent from my Nexus 4 using xda app-developers app
Haha
i managed to install the drivers. Now im downloading the stock image and i'll flash it with the toolkit
sampy14 said:
i managed to install the drivers. Now im downloading the stock image and i'll flash it with the toolkit
Click to expand...
Click to collapse
Btw when you used cwm did you use the clockwork app or the actual recovery?
Sent from my Nexus 4 using xda app-developers app
Why not just flash the ROM your on ?
Sent from my Nexus 4 using Tapatalk 2
Ace42 said:
Btw when you used cwm did you use the clockwork app or the actual recovery?
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
the actual recovery.
anyway i fixed it.
I just flashed the franco kernel and it worked.
sampy14 said:
the actual recovery.
anyway i fixed it.
I just flashed the franco kernel and it worked.
Click to expand...
Click to collapse
I know why it went into bootloop. To flash other kernals aside frmo Francos...you need to flash stock boot image. Francos kernal has you flash his boot image in order to flash his kernal. I dont know why this is the case on the nexus 4, maybe because he is building blindly without a nexus 4 present with him.
The Gnexus wasnt like this but.....thats why you went into boot loop. I just skimmed his thread and found out your case was due to the above.
kioshi said:
I know why it went into bootloop. To flash other kernals aside frmo Francos...you need to flash stock boot image. Francos kernal has you flash his boot image in order to flash his kernal. I dont know why this is the case on the nexus 4, maybe because he is building blindly without a nexus 4 present with him.
The Gnexus wasnt like this but.....thats why you went into boot loop. I just skimmed his thread and found out your case was due to the above.
Click to expand...
Click to collapse
yes you are totally right. I have never had any problem with my galaxy nexus, thats why i didn't think twice before doing it.
Think the op should change the title of the 3d as it is misleading and blame faux for nothing
Sent from my Nexus 4 using Tapatalk 2
kaiowas82 said:
Think the op should change the title of the 3d as it is misleading and blame faux for nothing
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
3d? Funny way to spell thread
you were supposed to flash reset kernel first then faux kernel!! read the op!!! >.<
You can't brick a Nexus LOLs. Just download the toolkit. Easy way to fix your phone.
Sent from my Nexus 4 using Tapatalk 2
kioshi said:
I know why it went into bootloop. To flash other kernals aside frmo Francos...you need to flash stock boot image. Francos kernal has you flash his boot image in order to flash his kernal. I dont know why this is the case on the nexus 4, maybe because he is building blindly without a nexus 4 present with him.
The Gnexus wasnt like this but.....thats why you went into boot loop. I just skimmed his thread and found out your case was due to the above.
Click to expand...
Click to collapse
Franco uses his own ram disk. Other kernels do not. This is why you need to flash back to stock first.
Sent from my Nexus 4 using Tapatalk 2
So all right, I thought that when a newer version of Android came out and I am for example on CM10.1, I can update the android version and ROM by flashing a new bootloader and baseband, then flash the ROM and Gapps you want.
But today I read about someone who didn't accomplish to install a 4.2.2 ROM when he was on 4.2.1 so he installed factory image.
Can someone now please tell me what you need to do, so I am prepared when KLP arrives.
Thanks in advance!
Sent from my Nexus 4 using xda app-developers app
Please search. There are a gazillion amount of the same post laying around here. It would help you and others.
Sent from my Samsung Galaxy S3 using tapatalk 2
scream4cheese said:
Please search. There are a gazillion amount of the same post laying around here. It would help you and others.
Sent from my Samsung Galaxy S3 using tapatalk 2
Click to expand...
Click to collapse
I know but everyone says different things...
Sent from my Nexus 4 using xda app-developers app
Thibaultvw said:
I know but everyone says different things...
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
http://forum.xda-developers.com/showthread.php?t=2145848
[INFO] Nexus OTA Help-Desk
Sent from my Nexus 4
Thibaultvw said:
So all right, I thought that when a newer version of Android came out and I am for example on CM10.1, I can update the android version and ROM by flashing a new bootloader and baseband, then flash the ROM and Gapps you want.
But today I read about someone who didn't accomplish to install a 4.2.2 ROM when he was on 4.2.1 so he installed factory image.
Can someone now please tell me what you need to do, so I am prepared when KLP arrives.
Thanks in advance!
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Best advice I can give you is to learn fastboot. You can download images from Google once released and manually flash each thing that you want to update. You just unzip the files and fastboot flash them to your phone.
Sent from my Nexus 4 using Xparent Cyan Tapatalk 2
I think I am misunderstood.
I meant how to upgrade android version if going from a custom rom to another custom rom.
So for example CM10.1 Android 4.2.2 and going to Xenon HD Android 5.0
Thats possible right?
Sent from my Nexus 4 using xda app-developers app
Most developers list instruction on how to install from different custom roms in the install method if they differ (example post#2 in http://forum.xda-developers.com/showthread.php?t=2075444). If not, you could post in the thread of the custom rom to see if there are any special steps for that rom. I would advise reading through the first few posts of the custom rom to make double sure they didn't explain how to first.
Most developers list instruction on how to install from different custom roms in the install method if they differ (example post#2 in http://forum.xda-developers.com/showthread.php?t=2075444). If not, you could post in the thread of the custom rom to see if there are any special steps for that rom. I would advise reading through the first few posts of the custom rom to make double sure they didn't explain how to first.
Click to expand...
Click to collapse
Yeah but not when a newer android version comes out.
Sent from my Nexus 4 using xda app-developers app
1. Download new factory image
2. Flash bootloader and radio
3. Flash new custom ROM
4. Done
It's not that hard really
EddyOS said:
1. Download new factory image
2. Flash bootloader and radio
3. Flash new custom ROM
4. Done
It's not that hard really
Click to expand...
Click to collapse
But I do have to flash factory image in fastboot? No other ways by just using CWM?
Sent from my Nexus 4 using xda app-developers app
You don't, bootloader and radio should be enough, but you WILL need fastboot to get that bit done
EddyOS said:
You don't, bootloader and radio should be enough, but you WILL need fastboot to get that bit done
Click to expand...
Click to collapse
There is a flashable zip for that. So I can just use CWM when upgrading ROMs?
Sent from my Nexus 4 using xda app-developers app
I personally prefer to use fastboot but if there is a ZIP then you could try that...
EddyOS said:
I personally prefer to use fastboot but if there is a ZIP then you could try that...
Click to expand...
Click to collapse
Why do you prefer that even of you install the same file? But the answer on my question is that I can install a 5.0 ROM if I just flash the new bootloader and baseband?
Thank you for helping me!
Yes, as I answered that earlier
As for why I prefer fastboot - I always like to do everything manually. I then know I'VE done things right as an updater-script in a CWM ZIP file could be wrong/corrupt. It's a safety thing. Plus, once it's done it's done so I wouldn't have to do it again unless I wanted to downgrade Android to 4.x
EddyOS said:
Yes, as I answered that earlier
As for why I prefer fastboot - I always like to do everything manually. I then know I'VE done things right as an updater-script in a CWM ZIP file could be wrong/corrupt. It's a safety thing. Plus, once it's done it's done so I wouldn't have to do it again unless I wanted to downgrade Android to 4.x
Click to expand...
Click to collapse
But with CWM you also have to flash once I think? Because you dont flash it on a ROM, but before a ROM so the baseband and bootloader will last untill you install another I think?
Sent from my Nexus 4 using xda app-developers app
Fastboot flashing is permanent - once flashed you don't have to do it again. A CWM ZIP can do the same but I, personally, DO NOT LIKE DOING IT THAT WAY. I don't know what else you want me to say?
Do what YOU want to do
EddyOS said:
Fastboot flashing is permanent - once flashed you don't have to do it again. A CWM ZIP can do the same but I, personally, DO NOT LIKE DOING IT THAT WAY. I don't know what else you want me to say?
Do what YOU want to do
Click to expand...
Click to collapse
All right. Thanks for the help.
Sent from my Nexus 4 using xda app-developers app
Just upgrade the ROM. The developer will update his ROMS as new android comes out
Sent from my Nexus 4 using xda app-developers app
aanonymoushuman said:
Just upgrade the ROM. The developer will update his ROMS as new android comes out
Sent from my Nexus 4 using xda app-developers app
Click to expand...
Click to collapse
Yeah but CM11 (or whatever it may be called) wont be ready as yes as Android 5.0 comes out, and I may use the stock ROM the first day it comes out, which I will flash in CWM so I wanted to know if I needed to do something else.
I had a theme installed on tarp recovery I ran the zip to remove the theme now tarp recovery starts fine but I have no touch so I can't do anything even.if I reflash the recovery still nothing can anyone help?
Try to erase twrp, download a fresh copy and flash it... Via fastboot you can find the commands here post #3 make sure you grab the right one.. If your on kk grab the kk one on jb grab a jb one
Sent from my XT907 using XDA Premium 4 mobile app
ezknives said:
Try to erase twrp, download a fresh copy and flash it... Via fastboot you can find the commands here post #3 make sure you grab the right one.. If your on kk grab the kk one on jb grab a jb one
Sent from my XT907 using XDA Premium 4 mobile app
Click to expand...
Click to collapse
Thanks but I got it I just used the twrp manager to flash the flashback2JBbootloader.zip and it did it all for me
kehres83 said:
Thanks but I got it I just used the twrp manager to flash the flashback2JBbootloader.zip and it did it all for me
Click to expand...
Click to collapse
Had the same problem. Where did you find the flashback--.zip?
http://www.droidrzr.com/index.php/topic/50096-how-tomobile-downgrader-flash-back-10-0
http://www.droidrzr.com/index.php/t...owngrader-flash-back-10-07-15-14/#entry449009
kehres83 said:
http://www.droidrzr.com/index.php/t...owngrader-flash-back-10-07-15-14/#entry449009
Click to expand...
Click to collapse
Works great for flashing back and forth from kk to jb also
I have done it a few times
kehres83 said:
Works great for flashing back and forth from kk to jb also
I have done it a few times
Click to expand...
Click to collapse
Thanks for the link.
I'll give it a try. This should be just what I need to try out the roms that need the older bootloader.
Sure is
Sent from my DROID RAZR M using Tapatalk