Related
I had Odin 1.0 and i have flashed gingerbread 2.3.3 without any problem. But in forums so many peole talking about bootloader. I really dont understand what is the disadventages installing or updating bootloaders?
And if i want to go back froyo rom do i get problems due updating bootloader.
I have also a problem more, i dont find "format internal sd" section in new 3e recovery screen. Is it because of new bootloader?
Thanks for your answers..
Hi try
http://forum.xda-developers.com/showthread.php?t=1011701
Quite a bit of info here on the bootloader issues
rhitey said:
Hi try
http://forum.xda-developers.com/showthread.php?t=1011701
Quite a bit of info here on the bootloader issues
Click to expand...
Click to collapse
Thank you. I got my answers
How could we downgrade the bootloader to 2.2.1 version? Do we need to flash the 2.2.1 stock rom?
Official Gingerbread SBF release for AT&T
Android 2.3.4 --- Blur_Version.4.5.91.MB860.ATT.en.US
1FF-olympus-user-2.3.4-4.5.91-110625-release-keys-signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
http://www.filesonic.com/file/15073...signed-ATT-US-GAS_NA_OLPSGBATTSPE_P011.sbf.gz
WARNING : FLASH THIS SBF ONLY IF YOU ARE STILL RUNNING STOCK AT&T 2.2.2 WITH A LOCKED BOOTLOADER. ONCE YOU FLASH THIS ANY ATTEMPT AT A DOWNGRADE TO A PREVIOUS VERSION WILL BRICK YOUR PHONE.
If you are running anything else using this could increase your chances of bricking. Read the thread before flashing !!!!
This SBF is intended for people who don't want to deal with rooting and unlocking and OTA's and blur removal and fastboot and recovery and blah, blah blah I'm going to brick my phone regardless of what I do stuff.
It's also meant for people who have patience and want to upgrade safely who don't want to deal with Motorola Software Update because of the OS they're running.
It's an original SBF plain and simple.
Compression MD5 - 37D7E7D002B921F98D47BAD85DB55532
SBF MD5 - 56721D893E43B814E95683A00B165555
Read eval-s post below to clear up the confusion.
Would not use if you've unlocked with pudding. Will probably soft brick or worse.
Locked phones should be safe.
http://forum.xda-developers.com/showthread.php?t=1138204 (see post #2) for an unlocked version (with root).
I am complete noob in atrix,But i want to know that i have unlocked my atrix but if i flash New Firmware GB,Will it make my atrix again locked plz tell me.
is this the final version?
If i flash back to 1.8.3 will it be locked again? And update to official from there
I dont know about this sbf, but the service sbf i got from the motorola software update tool worked fine with the leaked ota (which is apparently the same as the official ota) and i was unlocked before i flashed it
edit: the compressed md5sum from the op is the same as the one i got from the motorola server which i flashed via rsd 5.3.1 with an unlocked bootloader. so apparently it is a sirvice sbf
edit: i also flashed zomgunlock-lite.sbf after i flashed the sbf
So is it safe to update if ur unlocked already...is this update unlockable? Im currently rooted and bl unlocked....
Sent from my MB860 using XDA App
rjayflo said:
So is it safe to update if ur unlocked already...is this update unlockable? Im currently rooted and bl unlocked....
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
Read the second post, or try and post your brick results!
I also recommend not using. I used the 4.5.91 SBF a long time ago and bricked my phone shortly thereafter.
No, this .sbf is safe. It will just burn your fuse, just like the OTA, and make downgrading to anything impossible. To downgrade, you will have to use something that includes pudding, and you will have to 'oem unlock' ...that's all.
The .sbf is no more unsafe than the OTA. And once you've OTA'd, if you see "Failed to boot 4" this .sbf is the ONLY thing you can flash if you want to stay locked. Basically, if you have even started the OTA process, or have ever flashed this .sbf, you burned a fuse in ReservedOdm and have only two types of .sbfs you can flash. This one, or any+Pudding. Only this one will let you stay locked and still boot.
If you flash anything with Pudding after the OTA and you are still locked, you will see 0x1000. But it will be a soft-brick, and then your only choice will be to:
a) 'fastboot oem unlock' to continue.
or
b) flash this .sbf instead, and stay locked.
An AT&T user should never see 0x1000 from flashing this .sbf.
But afterwards, downgrades are dangerous. 'Official' AT&T 4.5.91 users will hard-brick their phones with 0x1000, stuck in nvflash mode, if they ever try to use any .sbf except this one, or the very special non-motorola version of 1.8.3 (found in the Pudding thread) or Pudding itself. In the later case, you can still escape the 0x1000 by unlocking. If you flashed stock 1.8.3 or below after running GB 4.5.91 officially, your phone is a paperweight. Be warned.
the2dcour said:
Would not use if you've unlocked with pudding. Will probably soft brick or worse.
Locked phones should be safe.
http://forum.xda-developers.com/showthread.php?t=1138204 (see post #2) for an unlocked-safe version (with root).
Click to expand...
Click to collapse
Does this flash a new radio too?
Sent from my Atrix
martyotaku said:
Does this flash a new radio too?
Sent from my Atrix
Click to expand...
Click to collapse
Yes, it does, but its the same radio that has been available for awhile now.
Baseband version
N_01_77_30P
Sent from my MB860 using XDA App
Does this official update has differences from the leaked?
Fixed bugs/better battery life, etc..
If it does, will somebody make a safe cwm zip to install it?
(for unlocked users)
Sent from my MB860 using XDA App
Paschalis said:
Does this official update has differences from the leaked?
Fixed bugs/better battery life, etc..
If it does, will somebody make a safe cwm zip to install it?
(for unlocked users)
Sent from my MB860 using XDA App
Click to expand...
Click to collapse
You already have 2.3.4 CWMs.
the2dcour said:
You already have 2.3.4 CWMs.
Click to expand...
Click to collapse
Yes, but these cwm`s were based on the leaked(beta?) att version.. Not on the official..
So I m asking, if the official(today's update) has improved battery life/performance etc?
Thanx!
Sent from my MB860 using XDA App
Paschalis said:
Yes, but these cwm`s were based on the leaked(beta?) att version.. Not on the official..
So I m asking, if the official(today's update) has improved battery life/performance etc?
Click to expand...
Click to collapse
As far as can be determined, the beta (from Moto dev servers) is the same as the "official" release now being pushed out.
so this include at&t stock GB kernel ( already posted by faux) and the well known .30P radio rigth?
Enviado desde mi MB860 usando XDA Premium App
eval- said:
The .sbf is no more unsafe than the OTA. And once you've OTA'd, if you see "Failed to boot 4" this .sbf is the ONLY thing you can flash if you want to stay locked. Basically, if you have even started the OTA process, or have ever flashed this .sbf, you burned a fuse in ReservedOdm and have only two .sbfs you can flash. This one, or 1.8.3+Pudding. Only this one will let you stay locked and still boot.
Click to expand...
Click to collapse
Eval, can you give us the path to cat eFuse status again and the comparison against which we can tell whether we've passed the point of no return with bootloaders? I would like to see where I'm at. Thanks.
So is this a service or full sbf for 4.5.91?
I am currently running locked and stock At&t 1.8.3. I want to update to this new OTA sbf. I read eval's post.
However, can someone confirm (break it down for me) that it is possible and probably safe to unlock the phone later using pudding or some other means. I am not an advanced user but will like to flash CM7 once its available.
So,
My HTC Incredible S is rooted, and the bootloader is unlocked (what the point of unlocking the bootloader is I still don't know as I can't install custom ROMS... but back to the point at hand...), and the OTA update to 2.3.5 arrived 2 weeks ago.
Needless to say, the update would not install. Despite researching the issue, I'm still confused as to what exactly is preventing the update from working. Is the the fact that my device is rooted? Or is it the unlocked bootloader? I tried relocking the bootloader and that had no effect, so I'm assuming rooted devices for some reason are rejected by the update.
So considering I can't install custom ROMs (I'm HBOOT 1.16 and the downgrade guide didn't work for me, so no s-off), and I now can't upgrade officially, I'm feeling a little stuck.
Is there a way to force an official update to install on a phone in my 'condition'?
Note: My recovery is custom - Revolutionary CWM - and I can't find (and therefore cannot flash) an original recovery image... would this affect the updating process?
Thanks guys/gals,
G
Root won't stop an ota but an unlocked bootloader will. You can check in your boot screen if its still unlocked or if its relocked.
nope_okay said:
So,
My HTC Incredible S is rooted, and the bootloader is unlocked (what the point of unlocking the bootloader is I still don't know as I can't install custom ROMS... but back to the point at hand...), and the OTA update to 2.3.5 arrived 2 weeks ago.
Needless to say, the update would not install. Despite researching the issue, I'm still confused as to what exactly is preventing the update from working. Is the the fact that my device is rooted? Or is it the unlocked bootloader? I tried relocking the bootloader and that had no effect, so I'm assuming rooted devices for some reason are rejected by the update.
So considering I can't install custom ROMs (I'm HBOOT 1.16 and the downgrade guide didn't work for me, so no s-off), and I now can't upgrade officially, I'm feeling a little stuck.
Is there a way to force an official update to install on a phone in my 'condition'?
Note: My recovery is custom - Revolutionary CWM - and I can't find (and therefore cannot flash) an original recovery image... would this affect the updating process?
Thanks guys/gals,
G
Click to expand...
Click to collapse
You need to replace CWM with the standard HTC recovery (you simply need to extract the recovery.img file from a RUU/ROM.zip file) and then relock the bootloader before the OTA will install correctly.
At hboot 1.16 and rooted all you should have to do is install Cwm and than you can flash custom ROM's..... Not sure what your problem is.
Sent from my anus using xda crap
@itsbeertimenow - yeah, unlocking the bootloader never did anything for me in terms of being able to flash custom ROMs... I guess 's-off' is required
@tpbklake, nonverbose
Yeah, I had a feeling the custom recovery had something to do with it. As I mentioned before, even relocking the bootloader had no effect.
Does the recovery have to be a specific version? I'm running Android 2.3.3, so will any 2.3.3 recovery work or does it have to be a recovery for an HTC Incredible S running Android 2.3.3 - that's a little harder to find. Any suggestions for an ruu/zip file to extract a recovery img from?
Thanks again for the helpful responses.
G
nope_okay said:
@itsbeertimenow - yeah, unlocking the bootloader never did anything for me in terms of being able to flash custom ROMs... I guess 's-off' is required
@tpbklake, nonverbose
Yeah, I had a feeling the custom recovery had something to do with it. As I mentioned before, even relocking the bootloader had no effect.
Does the recovery have to be a specific version? I'm running Android 2.3.3, so will any 2.3.3 recovery work or does it have to be a recovery for an HTC Incredible S running Android 2.3.3 - that's a little harder to find. Any suggestions for an ruu/zip file to extract a recovery img from?
Thanks again for the helpful responses.
G
Click to expand...
Click to collapse
Instead of trying to install the OTA update for Sense 3/2.3.5 why don't you flash the stock, rooted version of 2.3.5/Sense 3 ROM that I posted in the Dev section. With the unlocked bootloader and CWM you can flash this ROM and then manually flash the boot.img in that ROM's zip file and you should be good to go.
@tpbklake
I think I'd already tried that and the update process aborted pretty early on. I'll give it another go and check out troubleshooting threads related to the process. thanks again.
G
Update: I'm following the instructions as per this thread: http://forum.xda-developers.com/showthread.php?t=1337105
Update 2: It worked and I managed to install CM7... happy day Thanks guys
nope_okay said:
@tpbklake
I think I'd already tried that and the update process aborted pretty early on. I'll give it another go and check out troubleshooting threads related to the process. thanks again.
G
Update: I'm following the instructions as per this thread: http://forum.xda-developers.com/showthread.php?t=1337105
Update 2: It worked and I managed to install CM7... happy day Thanks guys
Click to expand...
Click to collapse
Here is the 2.3.5/Sense 3.0 stock, rooted ROM built directly from the OTA you were trying to install. You would flash it in CWM just like you did for CM7.
http://forum.xda-developers.com/showthread.php?t=1430535
Thanks for the link, will come in handy when I want to go back to a 'stock' setup... wasn't very impressed with CM7 so I then tried the Virtuous Affinity ROM (2.3.5/S3.5) - fantastic. Thanks again for your help!
G
I just bought a HTC Vivid, and before I start rooting and doing all that stuff, I'd like to know if anyone has a 2.3.4 stock rom. I want this because if I brick it then I will be able to flash it back, and I can't seem to find one. I've been searching all over, so if anyone has a stock rom it would be very helpful!
Thank you
I hope this is the right category, just registered
Just use this...if your bricked you won't be able to use recovery to flash a Rom...here is a ruu...its not gingerbread but it will bring you to official ics stock...http://dl3.htc.com/application/htc_vivid_att_RUU_3.26.502.56_US.exe
Sent from my HTC Holiday using Tapatalk 2
Oh even better, I was just planning to go back to 2.3.4 then upgrade to 4.0.3 anyways, this is great. Thanks a bunch!
EDIT: Wait, will this act as a flash and flash the whole OS on my vivid back to ICS 4.0? or just update it...
Kevin147 said:
Oh even better, I was just planning to go back to 2.3.4 then upgrade to 4.0.3 anyways, this is great. Thanks a bunch!
EDIT: Wait, will this act as a flash and flash the whole OS on my vivid back to ICS 4.0? or just update it...
Click to expand...
Click to collapse
Will flash whole os
Sent from my HTC Holiday using xda premium
ronnie498 said:
Will flash whole os
Sent from my HTC Holiday using xda premium
Click to expand...
Click to collapse
Okay, good. Thanks. Sorry, first time rooting
Which also means that it'll flash the stock kernel, ROM, and wipe your entire phone. Remember to relock the bootloader before running the RUU if it's unlocked.
altanimi said:
Which also means that it'll flash the stock kernel, ROM, and wipe your entire phone. Remember to relock the bootloader before running the RUU if it's unlocked.
Click to expand...
Click to collapse
How would I go about unlocking/locking it back up? I'm not quite sure what to do, I don't have the phone just yet, but its in the mail. I'll most likely need help rooting it when I get it..
Kevin147 said:
How would I go about unlocking/locking it back up? I'm not quite sure what to do, I don't have the phone just yet, but its in the mail. I'll most likely need help rooting it when I get it..
Click to expand...
Click to collapse
Getting your phone flashed to the ICS RUU will help you later when flashing custom roms (as I believe all of them are ICS-based)
The Superguide sticky thread in development can help you with the Bootloader Unlock procedure and many other things like rooting and prepping your phone for the S-OFF procedure (if you want to S-OFF your phone). Link below.
Unlocking the bootloader gives you permission to flash to partitions like your recovery partition (so you can flash custom recovery like clockworkmod etc.)
Once your bootloader is unlocked, RUU's will refuse to flash to your phone until you re-lock the bootloader. To relock your bootloader, power up the phone into HBOOT/Bootloader mode, choose Fastboot, then in a command prompt, run the command:
Code:
fastboot oem lock
To confirm it worked, next time you power up the phone into HBOOT/Bootloader mode, you should see at the top of the screen **RELOCKED**
Then you will be able to flash an RUU via your computer (while having your phone in fastboot mode)
When you get to the S-OFF portion of the superguide:
If you DO want to S-OFF your phone, follow that section of the superguide EXACTLY. It has important steps for prepping your phone for the S-OFF procedure.
If you do NOT want to S-OFF your phone, note that whenever you flash custom ROMS, the kernel partition must be flashed manually via fastboot (either before or after flashing the rom - I don't think it matters if it is before or after - anyone know this for sure?). I think every ROM includes the kernel (boot.img) file inside the zip so you can copy it to the same folder that has your fastboot.exe so you can run:
Code:
fastboot flash boot boot.img
Here is the superguide link:
http://forum.xda-developers.com/showthread.php?t=1416836
Or use the toolkit...its easy and walks you through the steps of unlocking bootloader and rooting...it also has a relock bootloader option so you can relock it in a click of a button...
If your gonna use the ruu...use it before you even root/unlock.the bootloader...that way you won't have to relock it
Here's the toolkit: http://forum.xda-developers.com/showthread.php?t=1498003
Sent from my HTC Holiday using Tapatalk 2
Wow! Thank you both for your information. I'm sure that they will both help me out greatly when it comes down to rooting.
I am running 2.3.4 on my phone and looking to update next week when I get my new battery. Did you have any issues with your update? Are you running ICS now? Any advice?
Follow the user guides. It's not hard or long just make sure you read the guides so you can update the bootloader properly.
its impossible to get ahold of the RUU's for the vivid, i need the stock Bell one, seeing that i have a Virgin Mobile SIM, I'm still on GB and i want to update to ICS. already going through the process of returning to S-ON
There are ICS ruu's available on goo.im
Even the bell one
Sent from my Vivid 4G using Tapatalk 2
Yup - the ICS bell stock RUU specifically is
http://goo.im/stock/holiday/ruu/RUU_HOLIDAY_ICS_35_S_BM_3.38.666.2_Radio_3.04.4740.11_34.29.701040.22_release_255916_signed.exe
and the GB bell stock RUU is
http://goo.im/stock/holiday/ruu/RUU_Holiday_BM_1.65.666.3_Radio_1.11.1020.03_30.77.551061.02L_release_222207_signed.exe
htc velocity
vi need help reverting to Gingerbread from ice cream sandwich , im currently stuck at the juopunutbear s-off bootloader loopi need help reverting to Gingerbread from ice cream sandwich , im currently stuck at the juopunutbear s-off bootloader loop
DaveTNAF said:
vi need help reverting to Gingerbread from ice cream sandwich , im currently stuck at the juopunutbear s-off bootloader loopi need help reverting to Gingerbread from ice cream sandwich , im currently stuck at the juopunutbear s-off bootloader loop
Click to expand...
Click to collapse
Perhaps a new question thread is more appropriate for your issue. I recommend you do that and describe this boot loop in more detail. Also, I remember there being a thread re: s-off unsuccesful doesnt mean phone is bricked.
Sent from my SAMSUNG-SGH-I747 using xda app-developers app
Hello everybody,
I was quite happy with my Incredible S until I updated it via OTA to ICS 4.0.4 + Sense 3.6...
Before that, I had been using it with Gingerbread 2.3.3 (or 2.3.5 ?!?) and Sense 2.1 and it was pretty good! I mean.. it did its job without significant problems..
Last week I decided to do ALL the updates in a rush and now it's laggy and slow...What drives me crazy is when I type some text (text messages, whatsapp, browser web, etc.): the touchInput seems not to be as responsive as it was once.. and it is frustrating!
I read a lot about this topic and I discovered that it's a common problem.
I tried to install other keyboards, other messaging apps, I made a factory reset, but nothing helped!
Now I'd really like to downgrade it to Gingerbread + a lighter Sense because I think that Sense 3.6 is too much heavy for this stupid phone.
Since I was (indeed I currently am) a complete noob about mobile systems I need help from you!
My idea is to install a stock rom and not a custom rom because every custom rom have some drawbacks or flaws.. while the stock Gingerbread 2.3.3 was flawless (I swear!).
I read that it's not possible to install an older version of Android via RUU.. is it right?
Is it possible to do something without rooting / s-offing the phone? (I'm not sure about s-off = having root priviledges...)
I read all the threads but I didn't find a clear answer to my problem.. please help!
Thank you guys!
p.s. I'm quite sure that android gb 2.3.3 came with sense 2.1 while gb 2.3.5 came with sense 3.0
Sadly you can't downgrade with an RUU - that would be sweet. Since you are on ICS, i'd assume your hboot version is 2.00+. I'm not sure if you can downgrade that, but take a look around. Essentially, you'd want to install CWM recovery, and install this GB 2.3.5 rom with sense 3. Note, there are no radios, you will have to flash those as well. Unfortunately, this is the only way to downgrade. Also, you will need S-off.
seba_t said:
Hello everybody,
I was quite happy with my Incredible S until I updated it via OTA to ICS 4.0.4 + Sense 3.6...
Before that, I had been using it with Gingerbread 2.3.3 (or 2.3.5 ?!?) and Sense 2.1 and it was pretty good! I mean.. it did its job without significant problems..
Last week I decided to do ALL the updates in a rush and now it's laggy and slow...What drives me crazy is when I type some text (text messages, whatsapp, browser web, etc.): the touchInput seems not to be as responsive as it was once.. and it is frustrating!
I read a lot about this topic and I discovered that it's a common problem.
I tried to install other keyboards, other messaging apps, I made a factory reset, but nothing helped!
Now I'd really like to downgrade it to Gingerbread + a lighter Sense because I think that Sense 3.6 is too much heavy for this stupid phone.
Since I was (indeed I currently am) a complete noob about mobile systems I need help from you!
My idea is to install a stock rom and not a custom rom because every custom rom have some drawbacks or flaws.. while the stock Gingerbread 2.3.3 was flawless (I swear!).
I read that it's not possible to install an older version of Android via RUU.. is it right?
Is it possible to do something without rooting / s-offing the phone? (I'm not sure about s-off = having root priviledges...)
I read all the threads but I didn't find a clear answer to my problem.. please help!
Thank you guys!
p.s. I'm quite sure that android gb 2.3.3 came with sense 2.1 while gb 2.3.5 came with sense 3.0
Click to expand...
Click to collapse
You will have to unlock the bootloader using the procedure at HTCDEV.com. After that, you can use an unsecured boot.img to boot your phone and then modify the phone's version-main so that you can then flash the older GB 2.3.3/Sense 2.1 RUU.
tpbklake said:
You will have to unlock the bootloader using the procedure at HTCDEV.com. After that, you can use an unsecured boot.img to boot your phone and then modify the phone's version-main so that you can then flash the older GB 2.3.3/Sense 2.1 RUU.
Click to expand...
Click to collapse
Its as simple as that? unlock through htcdev and flash on older RUU? That would also work with a phone unlocked with an xtc clip right?
m82a1 said:
Its as simple as that? unlock through htcdev and flash on older RUU? That would also work with a phone unlocked with an xtc clip right?
Click to expand...
Click to collapse
No, you misread the post.
1. Unlock the bootloader using HTCDEV.com
2. Boot your phone using an unsecured boot.img
3. Modify the version-main value.
4. Flash a RUU.
If you have a IncS that has S-OFF via XTC Clip, then you can simply modify the version-main value and then flash a RUU.
tpbklake said:
No, you misread the post.
1. Unlock the bootloader using HTCDEV.com
2. Boot your phone using an unsecured boot.img
3. Modify the version-main value.
4. Flash a RUU.
If you have a IncS that has S-OFF via XTC Clip, then you can simply modify the version-main value and then flash a RUU.
Click to expand...
Click to collapse
Gotcha, good to know, thanks!
well.. thank you for showing interest in my thread.
I understand that is not possible to downgrade without at least unlocking the bootloader..
so.. flashing a RUU is the same as flashing a custom rom?
After unlocking the bootloader I have to:
- flash a custom recovery
- flash a RUU/custom rom?
mmm.. is it really possible to install an older version of android while keeping the hboot at version 2.02 (like mine)?
I don't understand what is an "unsecured boot.img" and what "Modify the version-main value" means..
thank you again
seba_t said:
well.. thank you for showing interest in my thread.
I understand that is not possible to downgrade without at least unlocking the bootloader..
so.. flashing a RUU is the same as flashing a custom rom?
After unlocking the bootloader I have to:
- flash a custom recovery
- flash a RUU/custom rom?
mmm.. is it really possible to install an older version of android while keeping the hboot at version 2.02 (like mine)?
I don't understand what is an "unsecured boot.img" and what "Modify the version-main value" means..
thank you again
Click to expand...
Click to collapse
Look at the Downgrade script sticky post and then download the Downgrade Kit zip file and take a look at it.
The script file has all of the functions you need. One the script is done, you should be able to run the RUU.
U have to relock the bootloader then run the ruu file (the one u choose) while the phone is in fastboot mode
Sent from my HTC Incredible S using xda app-developers app
Is it possible to flash Android 2.3.3 Rom on 2+ hboot?
Sent from my Incredible S using xda app-developers app
Silversniper said:
Is it possible to flash Android 2.3.3 Rom on 2+ hboot?
Sent from my Incredible S using xda app-developers app
Click to expand...
Click to collapse
Yes it is. You can use the downgrade script to reset your version-main so that you can flash the 2.3.3 RUU.
tpbklake said:
Look at the Downgrade script sticky post and then download the Downgrade Kit zip file and take a look at it.
The script file has all of the functions you need. One the script is done, you should be able to run the RUU.
Click to expand...
Click to collapse
Are you talking about this thread:
http://forum.xda-developers.com/showthread.php?t=1373697
or this:
http://forum.xda-developers.com/showthread.php?t=1337105
or more probably this one:
http://forum.xda-developers.com/showthread.php?t=1761319
If you point me to the thread where I can find the Nonverbose's Downgrade script and the Downgrade kit I will be grateful...
Thank you!
seba_t said:
Are you talking about this thread:
http://forum.xda-developers.com/showthread.php?t=1373697
or this:
http://forum.xda-developers.com/showthread.php?t=1337105
or more probably this one:
http://forum.xda-developers.com/showthread.php?t=1761319
If you point me to the thread where I can find the Nonverbose's Downgrade script and the Downgrade kit I will be grateful...
Thank you!
Click to expand...
Click to collapse
The first thread you posted is the one you want.
tpbklake said:
The first thread you posted is the one you want.
Click to expand...
Click to collapse
Thank you tpblake! I'll try to follow that guide asap