Database Users

[Q] gingerbread 2.3.4 to froyo help my defy

hi
I flashed my defy using the nandroid backup with the fixed sbf attached.
and the phone bricked to the motorola start screen
looking up at the forums
I then tried flashing with the 2.3.4 orange version
and the phone flashed normally,
but as its the UK version of the firmware, I am now not able to connect to any of the mobile networks in india. and so I want to
downgrade to the original froyo that my phone came with..
the same
please help me
please

ashwanikoul said:
I then tried flashing with the 2.3.4 orange version
and the phone flashed normally,
Click to expand...
Click to collapse
Did you flash the full sbf when you did this?

yes the full sbf..

please... guys....
{
"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"
}
why dont you read the big effing warning!
this is the warning:
Simplestas said:
NO DIRECT DOWNGRADE
please don't flash sbf or you'll have serious problems going back to Froyo.
Click to expand...
Click to collapse
walter79 said:
cgxx.smg version:
Code:
[COLOR="Red"]CG31.smg version is 5[/COLOR]
CG32.smg version is 1
CG33.smg version is 1
CG34.smg version is 1
CG35.smg version is 2
[COLOR="Red"]CG39.smg version is 5[/COLOR]
CG42.smg: signature not found!
CG45.smg version is 0
CG47.smg version is 2
CG61.smg version is 1
CG64.smg version is 1
CG65.smg version is 1
Click to expand...
Click to collapse
walter79 said:
Android 2.3.4 "Gingerbread" !!BETA!!
!!! No downgrade for all Android 2.3.4 to FROYO ; NO DIRECT ROOT!! Use only the nandroid backup.
Click to expand...
Click to collapse

Downgrade to Froyo with Nandroid Backup + Fixed SBF
what you have to do right now,
you go and search edited leaked gingerbread 2.3.4 sbf for that.
the edited sbf gingerbread 2.3.4 automatically rooted.
but the problem is i don't have the link for that.
but i'm sure i ever see that in this forum.
why you have to search that edited 2.3.4 sbf?
because normal leaked gingerbread 2.3.4 can't be rooted!
if you cannot root, you can't install custom recovery..
if you cannot install recovery, you cannot restore froyo nandroid backup!
and froyo nandroid backup + froyo fixed sbf is the only hope right now.
sorry mate..
next time be prepared and be careful to read the warnings.

see I was not stupid not to read the warning but, since my phone bricked after flashing the custom nandroid 2.3.4and the fixed sbf.. I tried flashig again with indian roms 2.2, but it would get stuck in the bootloader loop, then I had no choice but to flash with 2.3.4 full sbf and my phone came alive.. but for the network problem and the battery getting heated up, I loved the gingerbread
but I now need desperate help

okay mate, since you only have 3 post you cannot asking for help on devs section.
i'll try to help searching edited-rooted-gingerbread sbf for you.
hope they'll answer and give me a link.
here, i ask them in devs section:
http://forum.xda-developers.com/showpost.php?p=15340284&postcount=188
okay, Walter79 answer my question.
thanks to him.

good news for you
detailed instructions how to downgrade to froyo
after you accidently flash full sbf of leaked gingerbread 2.3.4​
big thanks to:
_shadow_ from forum.androidfan.ru | link
djkail from xda | link
walter79 from xda | link
Click to expand...
Click to collapse
download this (these are painly big ass files):
-this unique eclair sbf: It's a unique eclair release with version 5 of cg31 and cg39 (same with leaked gingerbread), so you can flash directly to it.
-superoneclick root for defy
-custom recovery app for defy
-rsd lite 4.9
-moto usb drivers: for 32 bit, for 64 bit.
-cee froyo nandroid backup
-cee froyo fixed+edited sbf *EDIT* *AGAIN*
Click to expand...
Click to collapse
here's the steps:
- please, next time you'll have to be more careful, it's not a cheap device for some people
- make sure you have > 80 % battery
- power your phone with volume down still pressed to enter stock recovery,
- press vol.up+vol.down to show the menu
- then do "wipe data/factory reset" and "wipe cache" --> must do this!!
- reboot from stock recovery, immediately press and hold volume up for 5 seconds, then release to enter bootloader mode,
- make sure drivers and rsd lite have been installed before
- then plug your usb to computer, open rsd lite and flash that unique eclair sbf, wait untill it finish and defy got to main menu
- now you are on eclair. do not play with camera for now, i'm afraid it will broke your flashlight
- turn off usb debugging, set usb connection as mass storage,
- extract and copy cee froyo nandroid backup to \sdcard\goapkrev\backup | it should be like this: \sdcard\goapkrev\backup\ThisIsTheFolderOfCEENandroid\
- and copy custom recovery app somewhere you can access it later
- set usb connection as none
- turn on usb debugging, get root with superoneclick root for defy, reboot
- turn off usb debugging
- open custom recovery installer with file manager, open that app. Tap install recovery, then reboot recovery
- do wipe data, then wipe cache ----> must do!!
- select backup/restore, select restore, then select Froyo CEE Nadroid *EDIT*
- reboot system now, but immediately press and hold volume up for 5 seconds, then release to enter bootloader mode
- on bootloader mode, plug usb, open rsd lite, flash the fixed sbf of cee froyo
- wait untill the progress done, and defy run up on main menu.
- done, you should be happy now, it's froyo again. It's cee froyo (the stable one, many devs use it)
- install baseband switcher to suits your baseband region.
Click to expand...
Click to collapse

thanks a lot, I am in the process now to flash to eclair.. and am downloading the cee froyo nandroid
how do I install the baseband ?

ashwanikoul said:
thanks a lot, I am in the process now to flash to eclair.. and am downloading the cee froyo nandroid
how do I install the baseband ?
Click to expand...
Click to collapse
don't use ordinary eclair,
it's unique eclair with version 5 of CG31 and CG39,
use that unique full sbf eclair on the tutorial.
----------------
just download the baseband switcher apk, copy to your SD-Card,
then install, select your region.
you have to be get root, but don't worry,
because it seems Froyo CEE Nandroid backup already rooted,
just install and select your region.
happy to helps someone, sharing knowledge is caring.
you should do some, sometimes.

god!!
double post...
sorry.

I am now flashed with eclair, the one you sent the link to, and am not able to gain root access, using superoneclick, it just keeps waiting for the device?
any idea why?

ashwanikoul said:
I am now flashed with eclair, the one you sent the link to, and am not able to gain root access, using superoneclick, it just keeps waiting for the device?
any idea why?
Click to expand...
Click to collapse
is it usb debugging on? it should be on.
okay, if you have set it on,
try to set usb debugging off, then on again, it should be working.
if it still fails, close superoneclick, run it again.

yes usb debugging is off, I set it on and yep it rooted..
thanks again..
now just waiting for the nandroid froyo to get downloaded,
I don.t know how I can return the favour..
thanks a lot

GOD! i'm so sloppy.
i forget to add this line:
- select backup/restore, select restore, then select Froyo CEE Nadroid EDIT
go check the tutorial again,
sorry..
glad you haven't yet to that step, thats important!
please, confirm if you have read this

please, confirm if you have read the updated one

yes I have, I love you.. for caring so much

ashwanikoul said:
yes I have, I love you.. for care so much
Click to expand...
Click to collapse
because if you do not do that step,
it will ruin what you've done so far..
will go to endless boot loop..
------------------
oh ya, some information for people like you who accidently flash full gingerbread
------------------
when you install CM7, and want to go back to froyo,
you can't use that method of nandroid backup of froyo + fixed sbf.
because CM7 using different custom recovery,
CM7 is using bootmenu (consist of special 2ndInit + newest CWM)
normaly, if people want to go back to froyo from CM7:
they go to from stock recovery, wipe data+cache, go to bootloader, flash full sbf froyo, done.
but, for you, it is different.
use the latest tutorial i gave you earlier.
you have to go to that unique eclair first,
and remeber when on that eclair do not play with camera.
i think that's chinese sbf, and some says chinese sbf could damage flashlight.
maybe i just wrong about that, but play safe is better for your camera.

can I install CM7 to my phone after the steps you told me, go to froyo again,
and if I can how do I do that?
or you suggest I should not.?

ashwanikoul said:
can I install CM7 to my phone after the steps you told me, go to froyo again,
and if I can how do I do that?
or you suggest I should not.?
Click to expand...
Click to collapse
Yes, you still can use CM7
this tutorial is for your case only:
So you want to play again? Okay here CM7 tutorial for you..
- uninstall custom recovery app which already installed
- Copy CM7 RC1 v2 zip, Google Apps and Bootmenu Installer 1.7 to your SD Card
- Enable USB Debugging
- Install bootmenu installer 1.7 via File Manager, go to the app and click "Install 2ndInit Recovery" button. Wait for the led turn green.
- Disable USB Debugging, reboot
- Automaticly ended up on bootmenu
- Select custom recovery, "wipe cache partition" then "wipe data/factory reset"
- Select "install zip from sdcard", "choose zip from sdcard", then select CM7, then gapps
- Select "Go Back" then "reboot your system now"
- After all set, use baseband switcher app (already installed with cm7 package) to switch baseband which suit your region.
*if you want to go to custom recovery,
just reboot, when blue LED lights flashing, immediately press volume down.
select Custom recovery then Stable recovery.
DO NOT install bootmenu installer again when you are on CM7, surely will ****ed up your phone.
*if you want to go to froyo again,
just do the earlier tutorial.
Click to expand...
Click to collapse

[Guide] Upgrade Bell phone to Bell 2.3.4

This is a rough guide to help you upgrade your Bell phone to 2.3.4. This has been tested and it works.
*Usual disclaimer: I am not responsible for any damage to your phone.
This isn't detailed but should be enough to get you going.
You must have a Bell phone and your bootloader must be unlocked. Assume you will lose all data and BACKUP!!
1) Restore Bell System
Use NFHimself's GobStopper CWM zip to restore your phone to stock Bell 2.2.2 - at this link:
http://forum.xda-developers.com/showthread.php?t=1185171
2) Install 2.3.4 and root
- Download 2.3.4 zip from this link and copy to your sdcard:
http://forum.xda-developers.com/showthread.php?t=1166362
- Download root cwm zip from this link and copy to your sdcard:
http://forum.xda-developers.com/showthread.php?t=1159572
- Install edgan's kernel if you have d100 device
http://forum.xda-developers.com/showthread.php?t=1173225
- Install faux's d1100 kernel if you have d1100 device
http://forum.xda-developers.com/showthread.php?t=1156040
- Install CWM Recovery (attachment on first post):
http://forum.xda-developers.com/showthread.php?t=1185171
- go into CWM Recovery and install 2.3.4 zip from sdcard
- install Root zip from sdcard
Done!
Thanks to NFHimself, MagentoX , y2whisper and everybody who helped with this.

Plemen, thank you for your help so far. I have done everything you mentioned, and once I get to CWM installing the 2.3.4 over the Bell 2.2.2 (which I used NFHimself's script to get back to) I get the following error.
Any ideas? (Please see attached image)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

awryter said:
Plemen, thank you for your help so far. I have done everything you mentioned, and once I get to CWM installing the 2.3.4 over the Bell 2.2.2 (which I used NFHimself's script to get back to) I get the following error.
Any ideas? (Please see attached image)
Click to expand...
Click to collapse
I've had this error while upgrading and it was because the base ROM on the phone isn't "Bell enough".
Did you flash the French SBF or just use NFS script from OrangeFR (Option 1 or 2)?

Well, let's see:
I went from Bell stock to French SBF originally (via RSD) to Gingerblur. I then went back to stock French SBF and from French SBF to bootloader unlock (via IHOP) to fastboot OrangeFR (d001), though I didn't update the Webtop at all (except maybe during Gingerblur) which is where this error is originating from.
So I went from OrangeFR back to Bell stock 2.2.2 through NF's script (which went fine, no errors at all). I did a factory reset in the ROM itself (not through CWM) which was fine, and once I got back into the stock Bell 2.2.2 complete clean I did your steps.
1) Put the Bell 2.3.4 zip and CWM_root zip on the SD card.
2) Flashed IHOP with RSD
3) Flashed recovery via fastboot
4) Went into recovery and tried the .zip file.
That's where we stand. Should I wipe data/cache before flashing, or will that just put me further in the ****hole?
Thanks again.
plemen said:
I've had this error while upgrading and it was because the base ROM on the phone isn't "Bell enough".
Did you flash the French SBF or just use NFS script from OrangeFR (Option 1 or 2)?
Click to expand...
Click to collapse

What did you do, then, to make the ROM more "Bell-like"?
plemen said:
I've had this error while upgrading and it was because the base ROM on the phone isn't "Bell enough".
Did you flash the French SBF or just use NFS script from OrangeFR (Option 1 or 2)?
Click to expand...
Click to collapse

awryter said:
Plemen, thank you for your help so far. I have done everything you mentioned, and once I get to CWM installing the 2.3.4 over the Bell 2.2.2 (which I used NFHimself's script to get back to) I get the following error.
Any ideas? (Please see attached image)
Click to expand...
Click to collapse
when you did step one did it say it downloaded the files prior to updating the device? this step takes approx an hour to complete.

So it looks like one of your partitions isn't close enough to bell. When I ran into this issue I went with option 1 - I flashed the French SBF and then ran NFS script to root and then restore to install the Bell partitions and checked for OTA. Now that NFS has updated his script to restore 2.2.2 partitions, the OTA may not find any updates which is fine.
awryter said:
What did you do, then, to make the ROM more "Bell-like"?
Click to expand...
Click to collapse
awryter said:
Well, let's see:
I went from Bell stock to French SBF originally (via RSD) to Gingerblur. I then went back to stock French SBF and from French SBF to bootloader unlock (via IHOP) to fastboot OrangeFR (d001), though I didn't update the Webtop at all (except maybe during Gingerblur) which is where this error is originating from.
So I went from OrangeFR back to Bell stock 2.2.2 through NF's script (which went fine, no errors at all). I did a factory reset in the ROM itself (not through CWM) which was fine, and once I got back into the stock Bell 2.2.2 complete clean I did your steps.
1) Put the Bell 2.3.4 zip and CWM_root zip on the SD card.
2) Flashed IHOP with RSD
3) Flashed recovery via fastboot
4) Went into recovery and tried the .zip file.
That's where we stand. Should I wipe data/cache before flashing, or will that just put me further in the ****hole?
Thanks again.
Click to expand...
Click to collapse

Hi,
If you are using my restore phone option, be aware that it overwrites all the partitions except for partition 3 which is you pds partition, data, which is 2 GB and can be generated with a factory reset, and cache, which is a 600MB temp storage space which can be wiped as well. It isn't just system and boot. It restores partitions that sbfs may not write to but doesn't update any bootloaders or radios.
The only thing that the French sbf might do to make things work is to flash an older bootloader. It is also possible that some portion of your pds partition gets modified. Most likely it's a signature in the bootloader or command line options being passed to the kernel that don't apply. There have been reports of phones bricking on ATT when they go back to their older bootloader, however, there have been anecdotal reports that this isn't the case for Bell. Be careful and be prepared for the worst.
Cheers!

If I do this, will I still have an unlocked bootloader?

once the entire process is complete, yes.

y2whisper said:
once the entire process is complete, yes.
Click to expand...
Click to collapse
So then could this be a permanent fix to the RAM issue?

Thanks for the detailed info on the scripts - it's great to get it from the horses mouth
NFHimself said:
Hi,
If you are using my restore phone option, be aware that it overwrites all the partitions except for partition 3 which is you pds partition, data, which is 2 GB and can be generated with a factory reset, and cache, which is a 600MB temp storage space which can be wiped as well. It isn't just system and boot. It restores partitions that sbfs may not write to but doesn't update any bootloaders or radios.
The only thing that the French sbf might do to make things work is to flash an older bootloader. It is also possible that some portion of your pds partition gets modified. Most likely it's a signature in the bootloader or command line options being passed to the kernel that don't apply. There have been reports of phones bricking on ATT when they go back to their older bootloader, however, there have been anecdotal reports that this isn't the case for Bell. Be careful and be prepared for the worst.
Cheers!
Click to expand...
Click to collapse

First of all...Can anyone who has been using the new 2.3.4 tell me is there any significant differences in the performance of the phone in everyday use?
Second: Will the WebTop without the Dock MOD work with this new ROM?
Third: If I do this will I be able to install Bell official OTA when it comes out officially or it will brick my phone?

I Am already on 2.3.4 on a bell Atrix, I can honestly say the upgrade does about 0 ... now with that said the real thing that we need is a market fix so we can finally play order and chaos in Canada.
I give this Guide a 1/10 because its redundant and is not as cohesive as the other guides that are already available.
Edit: no unlock in this guide?! whats the point?!
Edit2: nvm you didt write a guide... my mistake, you just posted a bunch of links for lazy people

hate when i hit thanks instead of reply.....
anyways thanks ray of sunshine for that post. the thread was created by request, but if you do have a more detailed breakdown feel free to contribute.
@sservati
I have noticed quite the difference with 2.3.4. outside of the added features like gtalk w/video, there are little tweaks like being able view your contacts by your google groups. as well as some performance tweaks live wallpaper still seems laggy but other transitions are very smooth. as long as you are comfortable with unlocking your bootloader etc, this is something I recommend. if you are overly nervous about doing that. then stick to what you have.

The most important thing to note when installing FR orange is to fastboot flash the boot.img that is appropriate for your phone (1100 / d00 ) before you flash the system.img otherwise you will boot loop! Its not clearly indicated in the linked thread from OP.
Carrion
P.S. I do like 2.3.4 more then 2.2.3 ... im just ticked cuz i lost a transparent widget, because for some ungodly reason its now incompatible?!

didn't know about the timing, but yes make sure you follow that guide as well.
ah sorry to hear that.
Did you try doing the spare parts fix? (download spare parts and turn off compatibility mode)

Why are you installing the FR Orange (2.3.4)? The 1100/d00 issue is dealt with in the unlock guides - this thread clearly notes the steps are for unlocked phones only to install Bell 2.3.4.
Anyhow, there are some great threads on unlocking international phones and folks should really consult those to unlock.
Carrion332 said:
The most important thing to note when installing FR orange is to fastboot flash the boot.img that is appropriate for your phone (1100 / d00 ) before you flash the system.img otherwise you will boot loop! Its not clearly indicated in the linked thread from OP.
Carrion
P.S. I do like 2.3.4 more then 2.2.3 ... im just ticked cuz i lost a transparent widget, because for some ungodly reason its now incompatible?!
Click to expand...
Click to collapse

Gonna try that now... thing is i don't have the apk,Ii need to download it from the market, i have already purchased it but its now no longer visable?! I have tried market enabler... this did nothing... i would really like the ability to see and use all the apps in the app market, i know this is a bit off topic though.

Carrion332 said:
Gonna try that now... thing is i don't have the apk,Ii need to download it from the market, i have already purchased it but its now no longer visable?! I have tried market enabler... this did nothing... i would really like the ability to see and use all the apps in the app market, i know this is a bit off topic though.
Click to expand...
Click to collapse
I'm having the same issue with a couple apps that i've purchased.
Anyways back on topic, I was on on cherryblur 0.5 and i managed to get to the bell GB following most of this guide. I tried to do a restore of a nandroid backup i made before going to GB, but for some reason the phone wouldn't boot. It would just stay at the moto symbol. Im assuming it was because of the boot.img. I tried for a few hours to get it to work, but then gave up and flashed the 2.1.1 french sbf, and then used NFHimselfs system restore script to get me back to the stock bell rom. It worked very well, just took a long time.
Personally I really like this Bell rom, works very well for me. Battery life has increased, its FAST, and there's no ram issues. As for the Webtop stuff, im not sure about. I rarely use it.
Just noticed that after flashing the bell_ihop.sbf to unlock the blootloader, the ram goes back down to 300mb. I wonder if someone can dig deeper into the bell_ihop bootloader and possibly fix the ram issues.

[ROM STOCK] REVIVE YOUR DROID PRO! [Dec-08-14]

Hi guys! Maybe the tittle is getting you confused, but it's so, now you're gonna unbrick and revive your Droid pro and also install de last update ( 4.7.3.XT610.Verizon.en.US) for your phone. "IT MEANS IT'S ONLY FOR VERIZON MODEL". Just follow the next instructions and you'll get it .
I know like me, many of you have gotten a brick in your phone or have your phone bricked for the time being. The first step that we'll do is unbricking the phone.
First:
Mod Edit link removed
Second:
Extract both archives, install one of the two installers of RSD, once RSD is installed, search for the DROIDPRO_2.26.20.sbf file that extracted.
Third:
Let's get your droid pro into bootloader mode,for this keep volume up and volume down keys + power button at the same time for 5 seconds, if do it right you'll get onto a screen like this,
{
"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"
}
Now, connect your phone by usb cable to you computer, (Remember to have installed drivers in your pc) RSD show that your droid is online, click on the search button and select DROIDPRO_2.26.20.sbf file, once this is done click on start button and RSD will begin to flash the phone, wait for the process , when it finishes, your phone will reboot and alive again!
For update your for to the last version just go> Settings>About phone>check update after first update and reboot, phone will show a pop up message with a new update, download and install all necessary times.
Hope I could have helped you :fingers-crossed:

Very useful post, since noone before mentioned the bootloader mode, only fastboot that didn't work in my case. I need to try this when I get my phone back from a magician who is trying to fix it....
Regarding the post itself, you should clearly declare that the SBF is from American (VERIZON) model, since it will brick European ones even more than they already are

A question regarding the SBF file that you have provided..
Is it SBF of Stock GB 2.3.4..???
Imagine that I have rooted my phone but now I want to remove Root from my phone permanently, so in that case can I follow these steps to get the pure Stock ROM..???
I am totally new to Motorola and coming from hTC, so that's why asking so many questions..

Mohammad Hashir said:
A question regarding the SBF file that you have provided..
Is it SBF of Stock GB 2.3.4..???
Imagine that I have rooted my phone but now I want to remove Root from my phone permanently, so in that case can I follow these steps to get the pure Stock ROM..???
I am totally new to Motorola and coming from hTC, so that's why asking so many questions..
Click to expand...
Click to collapse
That the Pre-final update for "Verizon" motorola droid pro, android 2.3.3. And yes, If Your phone is the Verizon droid pro, you can flash this firmware. Don't worry, ask all what you need

migui0401 said:
That the Pre-final update for "Verizon" motorola droid pro, android 2.3.3. And yes, If Your phone is the Verizon droid pro, you can flash this firmware. Don't worry, ask all what you need
Click to expand...
Click to collapse
Yes I have "Verizon" version.. After flashing SBF of GB 2.3.3, I will get OTA of GB 2.3.4, right..??
Thank You..

Mohammad Hashir said:
Yes I have "Verizon" version.. After flashing SBF of GB 2.3.3, I will get OTA of GB 2.3.4, right..??
Thank You..
Click to expand...
Click to collapse
Yes, just go to settings, about phone and check update.

migui0401 said:
Yes, just go to settings, about phone and check update.
Click to expand...
Click to collapse
Why don't you work on developing CM9 and CM10..???
EDIT: Can't I use ADB commands on Droid Pro..?? I tried entering "adb devices" into Command Prompt to list attached devices but it showed nothing in the list.. Phone was connected with the PC in Charge Only mode..
EDIT 2: The link to RSD Lite is not working..

Mohammad Hashir said:
Why don't you work on developing CM9 and CM10..???
Click to expand...
Click to collapse
I'm student and really don't have time for developing a new rom, I'm considering, but for the time being, I cant.

Mohammad Hashir said:
Why don't you work on developing CM9 and CM10..???
EDIT: Can't I use ADB commands on Droid Pro..?? I tried entering "adb devices" into Command Prompt to list attached devices but it showed nothing in the list.. Phone was connected with the PC in Charge Only mode..
EDIT 2: The link to RSD Lite is not working..
Click to expand...
Click to collapse
First, which rom are you using? Is usb debugging on? Do you have the correct drivers?
Download RSD here: http://pc.cd/5cL

migui0401 said:
First, which rom are you using? Is usb debugging on? Do you have the correct drivers?
Download RSD here: http://pc.cd/5cL
Click to expand...
Click to collapse
I am using the Stock GB 2.3.4, and yes USB Debugging is enabled.. I have the drivers installed..

Mohammad Hashir said:
I am using the Stock GB 2.3.4, and yes USB Debugging is enabled.. I have the drivers installed..
Click to expand...
Click to collapse
I don't know but, maybe ADB is not supported in stock. Now, i'm going to flash stock firmware in my phone, i'll let you if ADB works for me.

I bricked my phone, flashed the SBF using RSD Lite but still getting bootloop, Droid logo in red color coming again and again..
Please help..
EDIT: I got it working now, after flashing the SBF, I went into recovery (R+M then Volume up and down keys) and performed "wipe data/factory reset" and "wipe cache partition", and now it is working..
Thank You..

Mohammad Hashir said:
I bricked my phone, flashed the SBF using RSD Lite but still getting bootloop, Droid logo in red color coming again and again..
Please help..
EDIT: I got it working now, after flashing the SBF, I went into recovery (R+M then Volume up and down keys) and performed "wipe data/factory reset" and "wipe cache partition", and now it is working..
Thank You..
Click to expand...
Click to collapse
Every time you flash the firmware over a custom rom, you must do a factory reset from recovery.

migui0401 said:
Hi guys! Maybe the tittle is getting you confused, but it's so, now you're gonna unbrick and revive your Droid pro and also install de last update ( 4.7.3.XT610.Verizon.en.US) for your phone. "IT MEANS IT'S ONLY FOR VERIZON MODEL". Just follow the next instructions and you'll get it .
I know like me, many of you have gotten a brick in your phone or have your phone bricked for the time being. The first step that we'll do is unbricking the phone.
First:
Download RSD Lite 6.1.x from here: http://pc.cd/5cL
And the SBF files from here https://my.pcloud.com/#page=publink&code=XZ3EMZwDjXjAu2s7BETYRGNfKhWL5MpSa7
Second:
Extract both archives, install one of the two installers of RSD, once RSD is installed, search for the DROIDPRO_2.26.20.sbf file that extracted.
Third:
Let's get your droid pro into bootloader mode,for this keep volume up and volume down keys + power button at the same time for 5 seconds, if do it right you'll get onto a screen like this,
Now, connect your phone by usb cable to you computer, (Remember to have installed drivers in your pc) RSD show that your droid is online, click on the search button and select DROIDPRO_2.26.20.sbf file, once this is done click on start button and RSD will begin to flash the phone, wait for the process , when it finishes, your phone will reboot and alive again!
For update your for to the last version just go> Settings>About phone>check update after first update and reboot, phone will show a pop up message with a new update, download and install all necessary times.
Hope I could have helped you :fingers-crossed:
Click to expand...
Click to collapse
These links no longer work :crying:
Can someone please help me with these sbf files.
I bricked my Droid Pro would love getting it back.
Thanks

Newyork! said:
These links no longer work :crying:
Can someone please help me with these sbf files.
I bricked my Droid Pro would love getting it back.
Thanks
Click to expand...
Click to collapse
Try again.

migui0401 said:
Try again.
Click to expand...
Click to collapse
Tried.
:crying:

Newyork! said:
Tried.
:crying:
Click to expand...
Click to collapse
Try the links on the Op first post. In the beginning of the thread.

migui0401 said:
Try the links on the Op first post. In the beginning of the thread.
Click to expand...
Click to collapse
Thanks!!
Downloading it now, will try tomorrow.
I hope i won't need anymore help

migui0401 said:
Every time you flash the firmware over a custom rom, you must do a factory reset from recovery.
Click to expand...
Click to collapse
Hello,
and if I try push power + R +M and there is onluy sign "!" and Android symbol? And there is no possible to choose any option to wipe data?

baroo89 said:
Hello,
and if I try push power + R +M and there is onluy sign "!" and Android symbol? And there is no possible to choose any option to wipe data?
Click to expand...
Click to collapse
Press both volume buttons when you see the exclamation mark, and you will get the menu.

[Q] **HELP!** Bricked DEFY - RDS lite not working

Hi! I have a huge problem. A couple of days ago I decided to install a custom ROM on my DEFY. I am a total rookie in this field, so I googled a little and got some information needed. I rooted my phone with One Click Root method. Then I installed 2ndInit and got an access to Custom Recovery. I downloaded CyanogenMod10, did a backup, wiped all my data and flashed CM10. Everything worked just fine and I was satisifed. But I forgot to do a copy of my contacts and some other stuff, so I decided to flash my backup back and store my contacts on sd card. I opened custom recovery and wiped all the data from the phone. Then I wanted to restore my backup, but my phone got somehow stuck or something and I had to reboot it. Now I cannot access custom recovery any more! When turn my phone on, I can only see Motorola logo. I can only get to so called Android recovery, where I can only wipe my data, and bootloader. So I tried the whole RDS Lite method, just as it was described here:
forum.xda-developers.com/showthread.php?t=1828639
Everything seemed to work fine, but after getting to around 97% it looked like this:
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
So I am out of options right now and I have no idea, what to do now. Can anyone please help me? I searched the web and I can't possibly find anything! Please, I really need to fix this.

Wiktor97 said:
Hi! I have a huge problem. A couple of days ago I decided to install a custom ROM on my DEFY. I am a total rookie in this field, so I googled a little and got some information needed. I rooted my phone with One Click Root method. Then I installed 2ndInit and got an access to Custom Recovery. I downloaded CyanogenMod10, did a backup, wiped all my data and flashed CM10. Everything worked just fine and I was satisifed. But I forgot to do a copy of my contacts and some other stuff, so I decided to flash my backup back and store my contacts on sd card. I opened custom recovery and wiped all the data from the phone. Then I wanted to restore my backup, but my phone got somehow stuck or something and I had to reboot it. Now I cannot access custom recovery any more! When turn my phone on, I can only see Motorola logo. I can only get to so called Android recovery, where I can only wipe my data, and bootloader. So I tried the whole RDS Lite method, just as it was described here:
forum.xda-developers.com/showthread.php?t=1828639
Everything seemed to work fine, but after getting to around 97% it looked like this:
So I am out of options right now and I have no idea, what to do now. Can anyone please help me? I searched the web and I can't possibly find anything! Please, I really need to fix this.
Click to expand...
Click to collapse
Hi, I am not an expert, but I will try to give you some recommendations. First of all e need to know what defy you have. Mb525 Defy or mb526 Defy+.
If you can to connect to RDS lite we are not in serious problem yet.
We need to found the correct SBF ROM.
Else take a look in "Guide all-in-one defy" in this community.
Enviado desde mi MB526 mediante Tapatalk

Casteleugim said:
Hi, I am not an expert, but I will try to give you some recommendations. First of all e need to know what defy you have. Mb525 Defy or mb526 Defy+.
If you can to connect to RDS lite we are not in serious problem yet.
We need to found the correct SBF ROM.
Else take a look in "Guide all-in-one defy" in this community.
Enviado desde mi MB526 mediante Tapatalk
Click to expand...
Click to collapse
I have Motorola Defy MB525 with green lens.

You are not very bad.
The sbf is ok maybe you need to download it again.
Flash it and do what you wanna do.

Wiktor97 said:
I have Motorola Defy MB525 with green lens.
Click to expand...
Click to collapse
Before flashing an SBF file, it is recommended to wipe data and cache in the stock recovery. To get into the stock recovery, power off the phone, hold in the volume- button then also press and hold the power button. After a few seconds you should see a triangle with an exclamation mark in the middle, and a little green android guy below that. Then press the volume+ and volume- buttons at the same time, and a menu should appear. Use the volume buttons to navigate the menu, and the power button to select an option. Select "wipe data/factory reset" and also "wipe cache partition."
Then try flashing the sbf file in RSD Lite again. Make sure the phone battery is fully charged beforehand, and also make sure your PC won't go into hibernate or sleep mode during the flashing process.

[GUIDE] UPDATED Lenovo Vibe P1 A42/C72/C58 Root

This thread is for Lenovo Vibe P1 and NOT for P1m
Code:
*I am not responsible for bricked devices, dead SD cards, thermonuclear war.
First of all im just a user, who want to help others, i am NOT the maker/creator of these files.
Root and first TWRP recovery:
This method will work if your phone is on latest rom / S288 / maybe its work on older rom, BUT i dont test it.
1. You need download Lenovo driver and install it.
2. Get the QFIL/QPST and install it too.
3. Download the P1a42_S288... zip and unzip to your desktop.
4.Go in your Developer options /Tap 7 times build number/ and allow OEM unlock and USB debugging.
{
"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 to expand...
Click to collapse
5. You need download Supersu and put it in your INTERNAL storage root folder.
6.Shut down your device / phone/, press Volume + and connect to the pc via USB
7. Your windows give sounds for a new device, u go in Device manager /and in QFIL too/ and u will see the qualcomm hs-usb qdloader 9008.
Click to expand...
Click to collapse
8.Open your QFIL and press the first BROWSE and choose prog_emmc_firehose_8936.mbn from the unzipped folder.
Click to expand...
Click to collapse
9. Choose Load xml and choose rawprogram0_aboot+twpr and then patch0.
Click to expand...
Click to collapse
10. Press the blue Download button and it will start.
Click to expand...
Click to collapse
11. That is not all!!! Your phone will reboot BUT u need to press 3/ i mean volume + , - and power / button for 10 second if it start reboot, or your phone will reboot in Android, and u will get again stock recovery.
12.A If you havent TWRP u need start it again from step 6.
12.B If you have TWRP swipe the trigger to right and confirm the first ask.
13. Go to install and search your Supersu and flash it.
14. Wipe your dalvick cache and normal cache and reboot your phone.
15. The first reboot will take a long time / 10 minute was for me / dont restart, let it work.
16. If you do everything good, have now a ROOTED phone.
P1C72/C58 root method if u are on vibeUI rom.
You have to do the same like the top one, but u have to download this one
And use rawprogram-flashj_rec instead of rawprogram0_aboot+twpr
If it work for you, please hit the Thanks button or send me a beer via paypal.

Very good English not bad at all, anyway when you do the first part does that mean TWRP is only temporary ? and the second part makes TWRP permanent what is the third part for ?

karlzberg said:
Very good English not bad at all, anyway when you do the first part does that mean TWRP is only temporary ? and the second part makes TWRP permanent what is the third part for ?
Click to expand...
Click to collapse
1. make a permanent twrp, u can root your phone with this twrp / and supersu/ for use stock rooted rom.
2. and 3. is for custom roms, with the 1. twrp u cant flash custom roms, thats why u need this twrps, one is a chinese twrp and one is kyo's recovery what i use every time.

. I already have done part one from the other thread but this is good to know thank you.

@suryavamsi6

I have a P1 c72, if I flash P1a42_S288... zip , will NFC work? I have a sensor for glucose, freestyle libre, working with NFC so this is an important point for me. Regards

MOBUTU90 said:
I have a P1 c72, if I flash P1a42_S288... zip , will NFC work? I have a sensor for glucose, freestyle libre, working with NFC so this is an important point for me. Regards
Click to expand...
Click to collapse
If i know it right, yes thats work perfectly for my friend.

I have a p1c58 (2gb ram 16 gb storage) bought from China. Is this procedure suitable for p1c58 too? Thanks

coolman7 said:
I have a p1c58 (2gb ram 16 gb storage) bought from China. Is this procedure suitable for p1c58 too? Thanks
Click to expand...
Click to collapse
Didnt tried, but the cpu and something are same, so u can try it.

Starchm said:
Didnt tried, but the cpu and something are same, so u can try it.
Click to expand...
Click to collapse
Is there any risk to damage or brick the phone?
Thanks

coolman7 said:
Is there any risk to damage or brick the phone?
Thanks
Click to expand...
Click to collapse
Yes it can, but on forums u csn search some backup rom

[ROM][7.1.1]Android Ice Cold Project 12.1
Hey Guys, I have got a big problem here. I had installed the latest release dated 28th Jan (link given by one of the developers). I had upgraded my TWRP to 3.0.2-0 then i installed the rom zip and the gapps zip. At first time it booted up normally without any bugs and all. However after next boot onwards i started getting many background app crashes so i decided to revert back to the TWRP backup which i had made on newly upgraded TWRP just before installing this rom. I had taken backup and then wiped everything to install.
After i restored with no errors i am stuck in boot loop. I mobile restarts and then holds on the boot animation and the vibrates and restarts again. This happens endlessly. I tried to re-wipe everything and restore but it didn't help. I tried to wipe everything and reinstall this rom again but now mobile turns up upto aicp boot animation and the screen turns off and only blue led indication comes on.
I have tried almost everything in laslt 24 hours but no way did anything. Am still stuck at endless bootloop.
This is all that i tried.
1. I tried to flash ROM S288 using QFIL : bootloop
2. I tried to flash ROM S285 using QFIL: bootloop
3. I tried to change partition from ext4 to fat and then back to ext4 for system and data and then restore twrp backup : Bootloop
4. I tried to change partition from ext4 to fat and then back to ext4 for system and data and then install aicp installable zip with gapps :stuck after boot animation with screen off and blue led on.
5. I erased all the partitions and formated all internal partitions as signle ext4 file system (29GB size) and then download stock rom with stock recovery using QFIL. : Bootloop.
There is only way i can stop bootloop and that is i force it to boot in recovery mode (stock/twrp). In either of the recovery mode it boots up and works normally. But irreespective of any rom i try to install it always ends up in bootloop. There is something that it is looking for just after boot animation which it is not able to find after boot animation and hence it boots again. I am not sure what it is looking for so i tried to erase every partition and restore that by downloading stock rom using qfil both lolipop and marshmallow version but still no use.
Please guys tell me what can be done now. its been over 24 hrs am struggling and i guess i already did everything i knew. Now i need your help.

Hey guys a new query here. Your expert opinion is required.
Check this attached screenshot.
I have range of both the networks. IMEI is also my original IMEI. But baseband is unknown. I remember baseband had some value. Why is it unknown now. Any idea?
Is there anything abnormal to worry or shall I ignore it?

Can anyone get me downloaded this p1c72 Vibe UI rom file from chinese website https://pan.baidu.com/s/1qXyzyX2. Please if anyone can please reply.

mity_dev said:
Can anyone get me downloaded this p1c72 Vibe UI rom file from chinese website https://pan.baidu.com/s/1qXyzyX2. Please if anyone can please reply.
Click to expand...
Click to collapse
http://4pda.ru/forum/index.php?showtopic
Translate this Russian language and look for vibe ui. What you are looking for is there.

Hey Guys
Today i have intentionally hard bricked my own Lenovo Vibe P1 (P1a42) just to demonstrate you all how to recover the dead (hard bricked) qualcomm devices.
This process is more or less same for all the qualcomm devices. In some devices other steps may be needed where you will have to wipe entire ROM space and make a single partition of ExFAT format.
https://youtu.be/ZU1vu5diGsE
Well i have tried to make the video in such a way that i include more or less everything possible. Please bare with me.
Further Readings and reference:
http://www.droidsavvy.com/unbrick-qualcomm-mobiles/
https://www.leakite.com/2016/06/revised-how-to-unbrick-qualcomm-android.html

can u please tell me which zip i have to download for putting in QFIL the link provided is having 7 downloads

[email protected] said:
can u please tell me which zip i have to download for putting in QFIL the link provided is having 7 downloads
Click to expand...
Click to collapse
P1a42_S288_160721_ROW_RAW_QFIL

Starchm said:
P1a42_S288_160721_ROW_RAW_QFIL
Click to expand...
Click to collapse
thanks , i have another problem i cant understand the steps after 11 can anybody explain them to me better .
11. That is not all!!! Your phone will reboot BUT u need to press 3/ i mean volume + , - and power / button for 10 second if it start reboot, or your phone will reboot in Android, and u will get again stock recovery.
12.A If you havent TWRP u need start it again from step 6.
12.B If you have TWRP swipe the trigger to right and confirm the first ask.
13. Go to install and search your Supersu and flash it.
14. Wipe your dalvick cache and normal cache and reboot your phone.
15. The first reboot will take a long time / 10 minute was for me / dont restart, let it work.
16. If you do everything good, have now a ROOTED phone.
Click to expand...
Click to collapse

lenovo vibe p1a42 with s288 row root device on ubuntu
Please anybody help in rooting my device lenovo vibe p1a42 with s288 row on ubuntu os
Thanks,
Sampath