I was flashing jb leak 3, it din't boot. I tried restarting the device but I get black screen after the moto logo. then I flashed stock ics and got the same problem. please help I need my phone running urgently.
sorry for my bad English.
Are using at&t phone?
I'm assuming that you are flashing with RSD Lite, are you sure that you are using the correct firmware for your phone?
Sent from my MB865 using xda app-developers app
I have an Asian retail model(installing jb leak 3 renamed it to me865 from mb865). I was using rsd lite and was using correct firmware file.
I got the problem fixed.
What i have to do every time i boot the phone by pressing vol+,vol- and power button together and then selecting bp tools...
After installing bmm recovery phone was able to boot up normally.
Sent from my ME865 using xda app-developers app
Related
I recently bought the sch I535. I rooted it with no problems using odin to flash the stripped stock rom with root. When i downloaded rom manager and flashed cwmr everything was fine. Made a recovery, and tried to download cm10 kang projectf from rom manager. When the package was finished installing i recieved a screen on boot that says "system software not authorized by verizon wireless has been found on your phone. Please turn off your phone and go to the nearest verizon wireless store for help." I tried reflashing the stripped. Tar file with odin and still get the same thing on boot. Phone will not boot into recovery but will still go into odin mode.
Sent from my DROID RAZR using xda app-developers app
keith843 said:
I recently bought the sch I535. I rooted it with no problems using odin to flash the stripped stock rom with root. When i downloaded rom manager and flashed cwmr everything was fine. Made a recovery, and tried to download cm10 kang projectf from rom manager. When the package was finished installing i recieved a screen on boot that says "system software not authorized by verizon wireless has been found on your phone. Please turn off your phone and go to the nearest verizon wireless store for help." I tried reflashing the stripped. Tar file with odin and still get the same thing on boot. Phone will not boot into recovery but will still go into odin mode.
Sent from my DROID RAZR using xda app-developers app
Click to expand...
Click to collapse
What baseband and version is your device running?
Ics came on it. The phone wont boot for me to get any further info.
Sent from my DROID RAZR using xda app-developers app
Probably because you didn't read anything... You have to flash kexec, if not you will get what you have. Go to the developer forum and download a stock image and odin it...
Well i had the samsung epic 4g when i had sprint, did everything the same way and didnt realize this phone was locked down.
Sent from my DROID RAZR using xda app-developers app
Okay so basically the problem I am having is that I used the Atrix 2 bootstrap recovery apk and I flashed CM10 onto my phone. Well out of the blue it would not load past the CM10 logo so I am stuck at a stand still. Basically I have no way of figuring out how to get stock ICS back on to use my phone. Anyone know how to get past this?
ProfessorHipster said:
Okay so basically the problem I am having is that I used the Atrix 2 bootstrap recovery apk and I flashed CM10 onto my phone. Well out of the blue it would not load past the CM10 logo so I am stuck at a stand still. Basically I have no way of figuring out how to get stock ICS back on to use my phone. Anyone know how to get past this?
Click to expand...
Click to collapse
Press down when the led is blue to enter boot menu. Select recovery>custom recovery, and then wipe data. It should load after that.
Sent from my MB865 using xda premium
Scottyfer said:
Press down when the led is blue to enter boot menu. Select recovery>custom recovery, and then wipe data. It should load after that.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
My led dose not change to any color at all. It boots up to the motorola logo then it goes to a persistent CM10 logo. I tired to go to the default recovery and do a factory reset but it resets to the CM10 persistent logo again:/
ProfessorHipster said:
My led dose not change to any color at all. It boots up to the motorola logo then it goes to a persistent CM10 logo. I tired to go to the default recovery and do a factory reset but it resets to the CM10 persistent logo again:/
Click to expand...
Click to collapse
It should change to blue and then to green on the Motorola logo. If it's not doing that you're going to have to flash the fxz through rsdlite.
Sent from my MB865 using xda premium
Scottyfer said:
It should change to blue and then to green on the Motorola logo. If it's not doing that you're going to have to flash the fxz through rsdlite.
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
That is what I am thinking and I just found out that they finally have a FXZ for 4.0.4 so hopefully that would solve it Is there a specific method of using it? I have never had to deal with fastboot before.
ProfessorHipster said:
That is what I am thinking and I just found out that they finally have a FXZ for 4.0.4 so hopefully that would solve it Is there a specific method of using it? I have never had to deal with fastboot before.
Click to expand...
Click to collapse
Read through this: http://forum.xda-developers.com/showthread.php?t=1909319
Sent from my MB865 using xda premium
*UPDATE* I just fixed the problem. I used the ICS fastboot file located on http://forum.xda-developers.com/showthread.php?t=1961310 and then I used RSD 6.0
Scottyfer said:
Read through this: http://forum.xda-developers.com/showthread.php?t=1909319
Sent from my MB865 using xda premium
Click to expand...
Click to collapse
Thanks for all the help!
Hello All - I am a long time viewer of the forum, Recently I noticed an update available for the GS# to 4.2.2. I downloaded the Rom and began my normal process of using ROM Manager to boot into recovery mode to install the latest file. When the update finished applying I was presented with a brief view of the Samsung boot screen and then remained stuck on the Google Boot Screen.
I downloaded a stock firmware to apply with Odin 3.07 but it fails halfway through the write process.
Can someone please give me a hand or point me in a direction if you experienced the same problem.
Also when I try to load into recovery mode the phone screen remains black.
Thanks for any help!
Nick
What rom did you try to upgrade? Link please? And just to verify, do you have a Verizon GSIII?
Sent from my SCH-I535 using xda app-developers app
Follow up
I tried to download the 4.2.2 file from the following location,rootzwiki - "aokp-d2vzw-jb-mr1-build-4", went through rom manager and now is timing out on the google screen.
I do still have the phone with me currently. Thanks for any help you can provide.
I never use Rom Manager so that's not surprising to me. When you pull the battery then hold power, home, and Up until it vibrates does it boot to recovery? I would suggest flashing through CWM.
Sent from my SCH-I535 using xda app-developers app
Follow up
SlimSnoopOS said:
I never use Rom Manager so that's not surprising to me. When you pull the battery then hold power, home, and Up until it vibrates does it boot to recovery? I would suggest flashing through CWM.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
When I pull the battery and do the pwer,home,up it acts like its going to boot into recovery.. has in blue letters boot into recovery but the screen goes blank. Is this supposed to happen.
thashock said:
When I pull the battery and do the pwer,home,up it acts like its going to boot into recovery.. has in blue letters boot into recovery but the screen goes blank. Is this supposed to happen.
Click to expand...
Click to collapse
It may take a few attempts to get it to work since it's fickle sometimes.
Sent from my SCH-I535 using xda app-developers app
Still having some issues
SlimSnoopOS said:
It may take a few attempts to get it to work since it's fickle sometimes.
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
Thanks SlimSnoop I have tried roughly 15 times and am still not having any luck, are there any other tools you or anyone can suggest??
Yea, as long as you can boot into download mode then I suggest you utilize Odin and flash a stock image. There are two routes that you can go:
1) Odin flash the Verizon OTA VRBLK3 stock tar from DroidStyle's guide in the dev section. With this method, you would be returned to out of the box VRBLK3 and would need to root/unlock then flash roms again. The Odin tars included here are labeled as wiping /sdcard so be mindful of this.
2) Odin flash a rooted VRBLK3 image from mrRobinson thread. His thread contains Odin flashable rooted tars that are exactly the same as the OTA equivalent except they are rooted already. With this method, you would just need to unlock your bootloader using EZ Unlock v1.2 before flashing any custom roms. There's two versions of each rooted image here, one that wipes /sdcard and one that does not. So if you download the one labeled as wiping /sdcard all of your contents will be completely erased.
Sent from my SCH-I535 using xda app-developers app
Ughhh... I am in recovery and after a restore , I go to reboot system and instead of going to rom it brings me back to recovery again. I can't get out of recovery. What can I do????
Thanks...
i'm having the same problem right now too.
Boot into download mode and hit the volume down to cancel (reboot)
Should work for now until there is a patch.
Team twrp
Sent from my SCH-I535 using xda app-developers app
you can also use Odin to flash an old version.
Just remember to either use odin to flash an old version or find one through ROM Manager, so you don't get stuck in a boot loop again next time you restart the phone.
I am having the same problem. Booting to download mode, selecting yes then pulling the battery got me out of it. Very frustrating to say the least.
Is there a problem with the new CWM touch that just came out I wonder?
Sent from my SCH-I535 using XDA Premium HD app
goatman101 said:
I am having the same problem. Booting to download mode, selecting yes then pulling the battery got me out of it. Very frustrating to say the least.
Is there a problem with the new CWM touch that just came out I wonder?
Sent from my SCH-I535 using XDA Premium HD app
Click to expand...
Click to collapse
yes there is. as soon as it updated it started everything mentioned in all of the above posts. i odined and flashed back to older recovery. all better.
Dear guys, so here is my issue. I previously used the 4.2.2 rom by edison and has managed to flash it using the Atrix 2 bootstrap methodhttp://forum.xda-developers.com/showthread.php?t=1346977. And now, I wanted to try out the 4.4 ROM using the same bootstrap method as well. However, after I pressed "Bootstrap Recovery" and "reboot Recovery", the phone reboots into the M logo, and then its screen just stays black and blank forever.
The first method I tried to fix it is by getting into the Recovery (Home+Vol Up+Vol Down), and after trying out several reboot options, still to no avail. And now, I have performed "wipe data factory" and "wipe cache" in the recovery option. So what should I do now? I cant access the CWM or bootstrap to install my ROM or to perform any restorations.
Sorry guys that I have to asked this, but I did it to prevent myself from further plunging into the hard brick state.
kenlohwj said:
Dear guys, so here is my issue. I previously used the 4.2.2 rom by edison and has managed to flash it using the Atrix 2 bootstrap methodhttp://forum.xda-developers.com/showthread.php?t=1346977. And now, I wanted to try out the 4.4 ROM using the same bootstrap method as well. However, after I pressed "Bootstrap Recovery" and "reboot Recovery", the phone reboots into the M logo, and then its screen just stays black and blank forever.
The first method I tried to fix it is by getting into the Recovery (Home+Vol Up+Vol Down), and after trying out several reboot options, still to no avail. And now, I have performed "wipe data factory" and "wipe cache" in the recovery option. So what should I do now? I cant access the CWM or bootstrap to install my ROM or to perform any restorations.
Sorry guys that I have to asked this, but I did it to prevent myself from further plunging into the hard brick state.
Click to expand...
Click to collapse
You installed rom with bootstrap. That's outdated method which only works with wang's CM10/10.1 builds. Newer builds is using BMM only. So with any 4.2< ROM you must use Boot Menu Manager. So you'll need to reflash stock rom via RSD Lite. By the way what's your phone model (MB865 Retail, ME865 China or MB865 at&t?)? First thing before flashing is correct fxz.
-edited-
turffe said:
You installed rom with bootstrap. That's outdated method which only works with wang's CM10/10.1 builds. Newer builds is using BMM only. So with any 4.2< ROM you must use Boot Menu Manager. So you'll need to reflash stock rom via RSD Lite. By the way what's your phone model (MB865 Retail, ME865 China or MB865 at&t?)? First thing before flashing is correct fxz.
Click to expand...
Click to collapse
thank you so much for the prompt reply. So my location is in Malaysia>South East Asia, and it should be MB865. Do i use the 'Android 4.0.4
Blur_Version.67.220.3.ME865.Retail.en.05' file to fxz it? found from the sbf developer site
My previous OTA was 4.0.4, i was worried that if i used it on the earlier custom ROM 4.2.2 that i had, i will hard brick it. So will there be any cause for concern?
and what do they do with the .xml file in the file prior to fxz it? is it fine if i skip that step?
On the phone's back is written ME865 or MB865? Is there any AT&T logo on it? If your phone model is Retail MB - you should flash 6.7.2-EDEM-18.
Sent from my Atrix 2 using Tapatalk
turffe said:
On the phone's back is written ME865 or MB865? Is there any AT&T logo on it? If your phone model is Retail MB - you should flash 6.7.2-EDEM-18.
Sent from my Atrix 2 using Tapatalk
Click to expand...
Click to collapse
MB865, therefore i suppose it should be Blur_Version.672.1.18.MB865.PSHAsiaRetail.en.03. Unfortunately I had sent the phone to a repair guy, so no chance for me to try it out yet. Will update you tomorrow!
that guy wasnt able to repair it, so I did it myself using "Blur_Version.672.1.18.MB865.PSHAsiaRetail.en.03" as the sbf file, and TADAA, problem solved within 10 minutes! Thanks alot for the help, RSD is truly the all-in-1 safe kit
kenlohwj said:
that guy wasnt able to repair it, so I did it myself using "Blur_Version.672.1.18.MB865.PSHAsiaRetail.en.03" as the sbf file, and TADAA, problem solved within 10 minutes! Thanks alot for the help, RSD is truly the all-in-1 safe kit
Click to expand...
Click to collapse
I'm glad you got it figured out. :thumbup: