[Q] Bionic won't flash correctly - Motorola Droid Bionic

Hi all,
My Bionic is having a bit of a tiff that I feel like I've searched for days for an answer. I was rooted and lost root at random w/o flashing or updating the system at all!
Firstly I'll post my system information:
System Version: 5.9.901.XT875.Verizon.en.US
Baseband Version: Unknown
Webtop Version: (Okay this one is tricky...) Its got 1 square symbol then ELF then 3 more squares ... a bunch of random spaces with a A and 2 4's......
Kernel Version: 2.6.35.7-g83f1a47
[email protected] #1
Mind you I have tried the one click methods and manual operation of those methods both to no success. It even says successful in AP Fastboot mode and in command prompt but everytime I restart my phone it is in EXACTLY the same state (also carries over if I uninstall an app and restart the phone).
Also when using the one click method it proceeds to push everything but only after saying Error: Device not found
Formating Internal Storage doesn't work either... for some reason it keeps restoring everything (to the .901 messed up state it's in) EVEN if i delete the WHOLE contents of the SD card over USB on my desktop... I'm REALLY at a loss... I also went through an entire FXZ flash with no errors and it still stayed in exactly the same condition with no changes...
ANY help with this would be MUCH appreciated
Thanks!

Have you tried this;
http://forum.xda-developers.com/showthread.php?t=1427945
Follow those instruction to the 'T' and it should work. (Credit to the OP)
I did this probably 10 times this past weekend and got the phone down to .886 then was able to apply 43v3r root and update to .901. I flashed a .901 compatible rom and it brought me back to .894. i will probably re-flash later.
One thing to remember, charge your battery to 100% before proceeding because the flashing process uses your battery even when plugged into USB.
Good luck and set aside a night to do this.

ErisDroid? said:
Have you tried this;
http://forum.xda-developers.com/showthread.php?t=1427945
Follow those instruction to the 'T' and it should work. (Credit to the OP)
I did this probably 10 times this past weekend and got the phone down to .886 then was able to apply 43v3r root and update to .901. I flashed a .901 compatible rom and it brought me back to .894. i will probably re-flash later.
One thing to remember, charge your battery to 100% before proceeding because the flashing process uses your battery even when plugged into USB.
Good luck and set aside a night to do this.
Click to expand...
Click to collapse
Thanks for the reply! I tried this before and when you posted I tried it again. Failed on recovery and booted into the EXACT same system (and EVERYTHING else for that matter) it had before... it's like I can't change a thing no matter how hard I try. I sent a PM to the OP of that link though, so hopefully he comes through !

No go.. I give up ... Best Advice don't freeze system apps, if you lose root you're screwed.... Verizon is going to warranty my Bionic and MOTO can suck it.

Related

Revolution Problems

Ok, so i've spent a few hours at this already but let me give as much info as I can. I have read through many threads searching for info. I am no expert but I have had OG Droid, Incredible, and currently Thunderbolt all rooted so I am a novice.
This is my GFs phone and was previously bone stock, never rooted, no Roms nothing. So she gets the update recently and clicks yes and that is where the trouble began, phone constantly reboots and will not go past the language/activation screen. It never once went past that first screen, and she tried the hard reset and the battery pull.
So this is where I took over. I retried the hard reset (power + vol down) and also the battery pull. I also tried to activate in numerous other languages, all cause a reboot.
As per
http://forum.xda-developers.com/archive/index.php/t-1208713.html
I was finally able to get past the activation screen and make some progress. However after about a minute the phone always reboots, no matter what it is doing. I hard reset in the settings menu and that did nothing.
I next followed
http://forum.xda-developers.com/showthread.php?t=1326347
and got the phone rooted.
Installed
http://forum.xda-developers.com/showthread.php?t=1144951
and than installed CWR 4.0.0.4 ? (not sure the version whatever it comes with) Tested recovery and it it seems to stick even after rebooting several times, which the phone automatically does (maybe its a feature and not a flaw?) So I was unsure of what version of Android was even running because the phone will not allow me to go into about phone it always force closes *com.android.settings* but I figure what the heck and try my luck with a new Rom. I decided on
http://forum.xda-developers.com/showthread.php?t=1326542&page=11
So I did the usual. Rebooted into recovery, made a nandroid backup, wiped data, cache, davlik and even did /system for good measure. Than did the install and upon first boot all the same problems are there. It will not activate from the screen, it just reboots the phone eventually. I used the same method above to avoid the screen and now it will boot up and the phone is in fact running an AOSP Rom but it still reboots after about a minute. Oddly enough it also continues to refuse to let me open About Phone, in the settings menu. I also for good measure went into recovery and wiped everything again and also tried fixing permissions in recovery, all to no avail.
At this point I am thinking it is perhaps just a hardware issue, although the phone does not reboot itself in recovery. I would be willing to try a different Rom, however I don't think it would work. I am wondering if anyone has any other suggestions? Should I try this?
http://forum.xda-developers.com/showthread.php?t=1120062
Other info:
What does work is wifi, so i can get on the internet briefly. I can connect to google and get apps from the market.
I am leaving this for a few hours or I may have to re-title the thread "How do you put the LG Revolution back together after throwing it against a wall?"
Currently I'm sad face that you rooted and installed cwm but I think the update bricked it personally. Hopefully S.Meezy will see this as he has stock recovery. I would say just get back to bone stock and get it replaced. If anyone else knows how to get it fixed, my best guesses would be mt or S.Meezy, though adb that might work. I hope it all gets figured out. Someone needs to post stock GB without data or anything for people to flash to if need be. That might fix your issue.
My suggestion is to get the recover the whole phone...
http://forum.xda-developers.com/showthread.php?t=1211295
follow that but use the v6 TOT file. That will revert the phone to out of factory new, with updated radios. If you still have the issue then I would contact Verizon.
If everything works then you can re-run the update to Gingerbread.
Could be a long shot but I remember seeing something a little way back in another forum where a user w the same problem accidentially resolved his issue by restarting w the sd card out. For him it turned out to be a bad or incompatible sd card at the root of the problem.
If you have one in, pull it and restart. Hope thats it for you...
Sent from my VS910 4G using XDA App
Well i'm a glutton for punishment so i'm back.
I didn't want to bother with rooting it honestly but I did it out of desperation, figured a total wipe + brand new Rom would surely fix things.
Going to attempt the full recovery.
Tried pulling the SD card, than just the Sim card and finally without anything and none of the combinations worked.
Have you tried downloading a stock ROM to your PC/Mac and dropping that on your SD card and then flashing that ROM, after checking the md5? To me it sounds like your gf just had a bad download.
I think the issue is that you keep trying to flash the bad bits. Just my two cents...
Sent from my Dell Streak 7 using Tapatalk
Honestly you really need to try reflashing the entire phone with one of the TOT files. At this point to me it is clearly not the ROM that is installed. Restoring the phone with one of the TOT files will cleanly overwrite everything on the phone. Takes about 20 minutes or so after you have the program installed and recognizing the phone. Do it and post back.
H.
Haxcid said:
Honestly you really need to try reflashing the entire phone with one of the TOT files. At this point to me it is clearly not the ROM that is installed. Restoring the phone with one of the TOT files will cleanly overwrite everything on the phone. Takes about 20 minutes or so after you have the program installed and recognizing the phone. Do it and post back.
H.
Click to expand...
Click to collapse
What he said.
Remember: Absolutely do not, under any circumstance, unplug/turn off your phone once you start that process. It can take awhile, and might look like it froze, but just let it do it's thang.

[Q] LG Thrill GB w/ClockworkMod Recovery

(Obvious Noob warning---) A friend helped me root my Thrill, install ClockworkMod Recovery, and then install CM7 on my Thrill. But I would like to try the LG GB release. Is it necessary to backtrack all the way back to stock to do this (i.e. reinstall the stock ROM, reinstall the stock recovery, unroot, etc.)?
My friend tried using the LG upgrade tool on his LG phone without going back to stock and ended up bricking it. He says that usually within a few days of release, a CMR compatible zip file (usually already rooted) appears here on XDA (I haven't seen it), which makes things easier (but obviously he didn't wait for it himself).
Will a zip be possible for the Thrill GB? (The file seems quite large (420MB), so I'm guessing there is a lot of media included.) Or should I just bite the bullet and backtrack?
Rick
Rick Tillery said:
(Obvious Noob warning---) A friend helped me root my Thrill, install ClockworkMod Recovery, and then install CM7 on my Thrill. But I would like to try the LG GB release. Is it necessary to backtrack all the way back to stock to do this (i.e. reinstall the stock ROM, reinstall the stock recovery, unroot, etc.)?
My friend tried using the LG upgrade tool on his LG phone without going back to stock and ended up bricking it. He says that usually within a few days of release, a CMR compatible zip file (usually already rooted) appears here on XDA (I haven't seen it), which makes things easier (but obviously he didn't wait for it himself).
Will a zip be possible for the Thrill GB? (The file seems quite large (420MB), so I'm guessing there is a lot of media included.) Or should I just bite the bullet and backtrack?
Rick
Click to expand...
Click to collapse
I'm assuming that the official update method was used.
Just use this method after downloading the update. No bricking.
SEE THREAD
The Dark Lestat said:
I'm assuming that the official update method was used.
Just use this method after downloading the update. No bricking.
SEE THREAD
Click to expand...
Click to collapse
Thank you for your help!
Rick
Trojan?
Sorry, but as a noob, I can't post in that other thread.
It seems that the shttp3.exe in the LG Flash Package triggers Symantec's trojan detection. Some searching seems to indicate (assuming I'm reading all the cryptic virus sites correctly) that there is something to this, although it seems that different scanners find different trojans/viruses (can't post the link, but Google for "shttp3.exe" and "trojan"). I also found that the web site for this utility is blocked at work, because it's a "malicious site."
Has anyone seen this? Has anyone been able to verify/refute this?
Rick
There is no virus, Lestat would never do that
Sent from my LG-P925 using XDA
Just my .02 .....Get rid of Symantec !! They are known for scaring people into a virus frenzy.. Yes, it is possible that it is seeing it as a potential virus because shttp is a workaround from the usual porting of windows ip services. ...
Correct me if i'm wrong somebody please !!
Get yourself Comodo and save your money...
Regards,
Dwayne
PS: somebody on here has written a script that just uses shttp temporarily while
your doing the flash procedure, and then reverts your host files back automatically after your done. You should try it.
dwaynedman said:
Just my .02 .....Get rid of Symantec !!
Click to expand...
Click to collapse
Symantec isn't really a choice on work PC.
Get yourself Comodo and save your money...
Click to expand...
Click to collapse
I'm sorry I can't give the link yet, but if you'll Google you'll see Comodo classifies shttp3.exe as "ApplicUnwnt.Win32.ServerWeb.SmallHTTP.~A" or "UnclassifiedMalware" (I guess depending on the version). A number of scanners find issues with shttp3.exe. I'm not saying it is infected, only that it is doing something suspicious.
Rick
Rick Tillery said:
Sorry, but as a noob, I can't post in that other thread.
It seems that the shttp3.exe in the LG Flash Package triggers Symantec's trojan detection. Some searching seems to indicate (assuming I'm reading all the cryptic virus sites correctly) that there is something to this, although it seems that different scanners find different trojans/viruses (can't post the link, but Google for "shttp3.exe" and "trojan"). I also found that the web site for this utility is blocked at work, because it's a "malicious site."
Has anyone seen this? Has anyone been able to verify/refute this?
Rick
Click to expand...
Click to collapse
shttp3.exe is in no way a virus. I've scanned with AVG and MalwareBytes Anti-Malware and they check out good.
Back to square one
OK, I seem to be stuck.
With paranoia in tow, I decided to take the long way back to stock. Unfortunately, when I tried to restore the backup of my stock image I made to SD card after installing CMR, the md5 checksum failed. I'm not sure what I can do about this.
So ok, I tried following the above link. The first step is to ensure the su binary is up-to-date. But when I tried this, I get a failure downloading the manifest. This is true for WiFi and HSPA+. I Googled and found a suggestion to delete the su binary. But that didn't help (I'm not sure how it would have helped anyway).
So back to the original question. Can I use the LG upgrade process to upgrade without going backwards (as you can see above, I can't) without bricking the phone? Can I start at step 3 in the link above and succeed?
Rick
The Dark Lestat said:
shttp3.exe is in no way a virus. I've scanned with AVG and MalwareBytes Anti-Malware and they check out good.
Click to expand...
Click to collapse
Thank you, sir. I hope it didn't seem accusing.
Rick
Rick Tillery said:
Thank you, sir. I hope it didn't seem accusing.
Rick
Click to expand...
Click to collapse
It's cool, my friend.
Sent from my Samsung Galaxy S II w/ CM9
Rick Tillery said:
OK, I seem to be stuck.
With paranoia in tow, I decided to take the long way back to stock. Unfortunately, when I tried to restore the backup of my stock image I made to SD card after installing CMR, the md5 checksum failed. I'm not sure what I can do about this.
So ok, I tried following the above link. The first step is to ensure the su binary is up-to-date. But when I tried this, I get a failure downloading the manifest. This is true for WiFi and HSPA+. I Googled and found a suggestion to delete the su binary. But that didn't help (I'm not sure how it would have helped anyway).
So back to the original question. Can I use the LG upgrade process to upgrade without going backwards (as you can see above, I can't) without bricking the phone? Can I start at step 3 in the link above and succeed?
Rick
Click to expand...
Click to collapse
Is it safe to ignore the su version update?
Short of this, can I override the MD5 checksum? I realize that image could be corrupt, but if I'm just going to replace it with the GB release, does that matter?
Rick
You should just put your phone in recovery mode and update through the tool
with your IMEI #. It will give you the latest update !
If you need some help on that I think Lestat or somebody has a write-up
on doing this.
Good luck,
Dwayne
dwaynedman said:
You should just put your phone in recovery mode and update through the tool
with your IMEI #. It will give you the latest update !
If you need some help on that I think Lestat or somebody has a write-up
on doing this.
Good luck,
Dwayne
Click to expand...
Click to collapse
Can you be a bit more specific?
1. By "recovery mode," do you mean into ClockworkMod Recovery, or I should revert to stock (I made a copy of it after I rooted the stock ROM, but before I installed CMR)?
2. By "the tool," do you mean the official LGMobile Software Update, or the LG Flash Package referenced in the link above?
3. By "latest update," do you mean the file directly from LG, or the copy (v20p) linked from the link above?
4. If the latter in both previous questions, which set of steps do I need to follow from the above link? Can I do only 3 (LG Flash Tool), or do I need to follow 1 (Recovery Manager), 2 (Returning to Stock), and 3?
My friend had a different LG phone, with ClockworkMod Recover and CM7 installed. He reverted the CM7 to stock, but did not replace CMR with the stock recovery. Then he used the official LG upgrade method and bricked his phone. I'm trying to avoid this.
Are you saying I don't have to worry about this on the LG Thrill 4G? Can I go straight from the current CMR+CM7 configuration to the LG GB release using the official LG process?
If you mean I should use a different process, can you point me to it? As I mentioned, I run into dead-ends using the method linked above. And I'm not even sure whether I should be doing steps 1, 2 and 3, or if I should just use step 3.
Any and all help is appreciated, but I guess I don't understand the shorthand you're using here, so if you could be a bit more specific, I wouldn't feel so lost.
Rick
Rick Tillery said:
Can you be a bit more specific?
1. By "recovery mode," do you mean into ClockworkMod Recovery, or I should revert to stock (I made a copy of it after I rooted the stock ROM, but before I installed CMR)?
2. By "the tool," do you mean the official LGMobile Software Update, or the LG Flash Package referenced in the link above?
3. By "latest update," do you mean the file directly from LG, or the copy (v20p) linked from the link above?
4. If the latter in both previous questions, which set of steps do I need to follow from the above link? Can I do only 3 (LG Flash Tool), or do I need to follow 1 (Recovery Manager), 2 (Returning to Stock), and 3?
My friend had a different LG phone, with ClockworkMod Recover and CM7 installed. He reverted the CM7 to stock, but did not replace CMR with the stock recovery. Then he used the official LG upgrade method and bricked his phone. I'm trying to avoid this.
Are you saying I don't have to worry about this on the LG Thrill 4G? Can I go straight from the current CMR+CM7 configuration to the LG GB release using the official LG process?
If you mean I should use a different process, can you point me to it? As I mentioned, I run into dead-ends using the method linked above. And I'm not even sure whether I should be doing steps 1, 2 and 3, or if I should just use step 3.
Any and all help is appreciated, but I guess I don't understand the shorthand you're using here, so if you could be a bit more specific, I wouldn't feel so lost.
Rick
Click to expand...
Click to collapse
Remove your battery and keep the phone unplugged
Launch the mobile updater tool
Hold the volume+ button plug the phone in and keep holding the volume+ till the computer downloads the drivers your phone is now in download mode
Once the phone is picked up go to customer support on the LG updater tool and click on recovery phone put your imie number in click check (make sure its the right model) an let the updater tool do its job. Once its done flashing launch into recovery volume- plus power plus 3D button do a complete wipe and factory reset and reboot your phone ... you'll lose cwm and root and be back to full stock
Sent from my LG-P925 using XDA
Bricked?
No joy. Following the steps, the upgrade stopped at 6%. Trying a number of times, it eventually forced me to exit the program (no more restarts). Rerunning the updater (and downloading the 420 MB image yet again on a VERY slow connection) I tried again and again, with different combinations of battery and plug order with power and volume buttons, but nothing worked. Checking elsewhere I found some issues had been reported with Windows Vista/7, so I tried on an XP machine. Now the "Start Updating" bar is red (it was always gray with W7). But now when I try to restore (or even update for that matter), it asks for my S/N (it never did that before) and then says it is "no longer able to upgrade." Reading around, it seems this is an indication of the device being bricked.
Rick
It sounds like you are very close to getting it working Rick.
My update did the same thing, looped over and over until it
finally kicked me out. Just plugging and unplugging the phone etc....
And when my update stuck at 6% the last time, i took my battery out and then in real quick and that seemed to work.
Does the phone still vibrate when you plug the usb cable into it while holding volume..? If it does then I highly doubt that your phone is bricked, just in a semi flashed state....No worries
Should Rick be trying to run LG Updater as administrator ? I didn't, but it might not hurt.
Regards & Luck,
Dwayne
http://forum.xda-developers.com/showthread.php?p=22417769
Have you tried this yet cause if you can get the LG logo to come up then you can reflash the phone and get it working send a pm to the dark lestat he may be able to team viewer you and help you out
Sent from my ****ty supported LG Thrill
dwaynedman said:
It sounds like you are very close to getting it working Rick.
Click to expand...
Click to collapse
I wouldn't have believed you early this morning, but now maybe...
My update did the same thing, looped over and over until it
finally kicked me out. Just plugging and unplugging the phone etc....
And when my update stuck at 6% the last time, i took my battery out and then in real quick and that seemed to work.
Click to expand...
Click to collapse
I tried a bunch of different combinations...none seemed to make the app happy. I finally punted Windows 7 and moved to an XP machine, only to get the "no longer able to update" message. At that point I assumed I was screwed (effectively bricked).
Does the phone still vibrate when you plug the usb cable into it while holding volume..? If it does then I highly doubt that your phone is bricked, just in a semi flashed state....No worries
Click to expand...
Click to collapse
It never really vibrated, but I was able to get back into CMR. Unfortunately NONE of my backups work at all. They all have MD5 checksum failures. I tried a trick I found online and got past that step, only to have it say a failure restoring /system. So much for CMR.
JReeher said:
http://forum.xda-developers.com/showthread.php?p=22417769
Have you tried this yet cause if you can get the LG logo to come up then you can reflash the phone and get it working send a pm to the dark lestat he may be able to team viewer you and help you out
Click to expand...
Click to collapse
Which step? As I mentioned above, I can't even get the first step of the first section (updating the su binary). And if I start at the 3rd section, Symantec prohibits me from using shttp3.exe (I tried to unquarantine it, but it gives a permission error, even as Administrator, when I try to run it), so I'll have to use a different machine.
I was able to reinstall the CM7 3/15 release, so that's something. I was going to restore the stock recovery backup I made, but even that doesn't seem to work. I'm having issue with backups :-(
Rick
i have never been able to restore a backup. i dont know why... but i have tried several times in several different instances.
---------- Post added at 11:56 AM ---------- Previous post was at 11:50 AM ----------
rick tillery, if you want to get your phone back to alive and well i'd suggest doing this:
http://forum.xda-developers.com/showthread.php?t=1558723&page=3
4th post i think

[Guide} Bionic to ICS w/Files

These files and steps will get your Bionic on ICS with root. Follow directions carefully and enjoy.
To make it simple and help I have made a 1 file tar to download. Contents include FXZ to 902 then supplied 902_905 and .230 files with RSD and new Moto Drivers. Also includes Rooting script.
http://android.mattsimoni.com/Bionic.tar
Code:
// Use at your own risk, I'm not responsible for anything that happens to your phone. This is the method I choose to do this and it worked without fail.
// You have been warned, now have fun and jump on the band wagon!!
** 902_905.zip treat like a normal update.zip and flash through stock recovery
** 6.7.230 ICS Bionic.zip you will need to unzip before flashing
**Install Flashing Process**
First back up both SDCARDS and format each
then RSD back to .902
When it boots up for the first time, bypass activation and stuff by touching the 4 corners of the screen
Top Left - Top Right - Bottom Right - Bottom Left
Add 902_905 zip to SDCARD
Reboot into recovery flash ZIP
When it boots up for the first time, bypass activation and stuff by touching the 4 corners
Top Left - Top Right - Bottom Right - Bottom Left
Add 6.7.230 ICS Bionic.zip and crc file to SDCARD
Reboot into recovery flash ZIP
When its boots up it will be ICS, dont panic wait a few minutes and your set.
**Rooting Process**
Install New MOTO Drivers
Put phone into USB Debugging Mode
Confirm you put your phone into USB Debugging Mode
Click run.bat from the Root Folder.
You are now rooted.
Super..
You are amazing, ty...
Ok I have been trying to post this for a bit now, I am running rooted Bionic .2233 very smooth and easy process. However, when I installed Avast anti virus Avast came back and told me that a program called Verizon Remote Diagnostic too is using a high SMS priority and Avast will not work properly with it installed. Avast at this point offered to uninstall and, of course, this tool will not uninstall. I googled this tool and I saw a Verizon rep saying something like this is a tool for customer service and sits in the background and does not mine data. Anyone else hear of this tool? Is there a way to freeze or due bloat? I don't like the idea that Verizon did this, the rep also said this tool was for the LG Optimus?? Is this leak originally for the Optimus?
Sqwaller said:
Ok I have been trying to post this for a bit now, I am running rooted Bionic .2233 very smooth and easy process. However, when I installed Avast anti virus Avast came back and told me that a program called Verizon Remote Diagnostic too is using a high SMS priority and Avast will not work properly with it installed. Avast at this point offered to uninstall and, of course, this tool will not uninstall. I googled this tool and I saw a Verizon rep saying something like this is a tool for customer service and sits in the background and does not mine data. Anyone else hear of this tool? Is there a way to freeze or due bloat? I don't like the idea that Verizon did this, the rep also said this tool was for the LG Optimus?? Is this leak originally for the Optimus?
Click to expand...
Click to collapse
Try disabling it from applications menu
Sent from my GT-P7510 using Tapatalk 2
Well done Matt, ty
matt1313 said:
Try disabling it from applications menu
Sent from my GT-P7510 using Tapatalk 2
Click to expand...
Click to collapse
Can not disable so tried force stop and that did not work, I did not see this app in titanium backup will look again and see if I can freeze it.
Thanks though for the quick response.
Can someone rehost. Data quota is exceeded.
arizona55 said:
Can someone rehost. Data quota is exceeded.
Click to expand...
Click to collapse
Give me a few and Ill upload to a server
That was really easy - now one question: Is there are restore process torestore the internal and External SD cards that we backed-up?
OR should I just drag/drop what I need?
Thanks again -
Ok I have a silly question.
I followed the instructions and RSD back to 902. The problem is when I boot into recovery I get the Android guy with the !
I am able to take the 905 update and that worked just fine.
I was unable to apply 905 or ICS from this thread or any others.
I have tried to search various places but can't find the same problem.
help?
arizona55 said:
Can someone rehost. Data quota is exceeded.
Click to expand...
Click to collapse
New link added
Lemmy Caution said:
That was really easy - now one question: Is there are restore process torestore the internal and External SD cards that we backed-up?
OR should I just drag/drop what I need?
Thanks again -
Click to expand...
Click to collapse
Drag and drop
powrful1 said:
Ok I have a silly question.
I followed the instructions and RSD back to 902. The problem is when I boot into recovery I get the Android guy with the !
I am able to take the 905 update and that worked just fine.
I was unable to apply 905 or ICS from this thread or any others.
I have tried to search various places but can't find the same problem.
help?
Click to expand...
Click to collapse
Try it all over again, sound like something went wrong
powrful1 said:
Ok I have a silly question.
I followed the instructions and RSD back to 902. The problem is when I boot into recovery I get the Android guy with the !
I am able to take the 905 update and that worked just fine.
I was unable to apply 905 or ICS from this thread or any others.
I have tried to search various places but can't find the same problem.
help?
Click to expand...
Click to collapse
did you unroot before you did all of this? try that and see if it works.
AWSOME ...!!!
This worked GREAT ... I followed the instructions as listed and am now running ICS - BTW make sure that your battery has a good charge on it BEFORE attempting ANY flashing ...!
My battery went too low while flashing - I thought I bricked it (would not charge after) I had to borrow a battery from a buddy.
Rookie mistake I know ...
Thanks again I will update if I find any bugs.
Bricked?
I downloaded to my unrooted stock 905 bionic last night and ran the update. All went successful until I rebooted. I received a great error message..
Code:
Invalid CG OTV (CG: webtop): Invalid SP Data
Invalid CG HAB (CG: webtop, status: 0x004E)
Invalid CG OTV (CG: webtop)
I tried going back to 902 using the FXB and RSDLite, but it fails. It worked the first time and failed at 19/20.. now it fails at 1/20 (aka immediately). I tried using laptop, desktop, two USB cords, etc. Any ideas on how to unbrick? I'll update this thread if I figure out how to fix it.
powrful1 said:
Ok I have a silly question.
I followed the instructions and RSD back to 902. The problem is when I boot into recovery I get the Android guy with the !
I am able to take the 905 update and that worked just fine.
Click to expand...
Click to collapse
PremierGT said:
did you unroot before you did all of this? try that and see if it works.
Click to expand...
Click to collapse
same thing happened to me and my phone is unrooted. I even re-ran RSD. Please help.
crobs808 said:
(turn off phone, hold down both vol buttons + power, press vol down then up to go into recovery, press both vol buttons at android exclamation icon to see menu options)
Click to expand...
Click to collapse
<was not doing the highlighted part
Can't Download files..
this ICS leak unlock Global GSM, Right?
what is the reason for formatting the sd cards?
my phone hasn't been rooted and i'm on 905 already. i'm just in it for the ics, i haven't had a need for root, as of yet.
Just install the 233 leak works great and i didnt format the sd cards, so i dont see the need of that.
I was using the gsm hack but after the install i cant get signal and i cant change the network type in settings, ICS for the bionic will open the global feature? If not can i re apply the gsm patch? or maybe use radiocomm
Thanks
Okay quick question I downloaded the .tar file, this makes the second time. Seems the root file is empty. After both downloads it still seems to be this way. Can I just use voodoo or is there another way? Thanks
Thanks for posting this. Also, i don't remember if I was on .893 or what I was on for stock. What if I never went past .893? thanks.
Can you just use cheesecake.apk to get the 905 and leaked ICS updates? thanks.

[Q] Having problems running 1 CLICK SBF .906

I actually found a thread on this but it didn't actually fully address the issue. My problem is I rooted my Droid 3 a few weeks ago without any issue using the Motofail method. I actually kept the stock OS, all I did was use Titanium Backup to freeze some apps and I performed the Radiocomm Hack, all without any issue. Well now it is a few weeks later and I notice I'm having some problems with my phone. The stock battery indicator is acting wonky. I plugged in the phone to charge and when I unplugged it, the indicator continued to stay animated like it was still charging. Also when I plugged in the phone to charge yesterday, it appeared to be charging fine but when I unplugged later that evening it actually hadn't charged at all as the battery indicator was not only in the red, but when I went into About Phone in the system setting it also said the battery was at a low percentage. Another issue I'm having is with the sudden disappearance of my Battery and Data Manger within the systems menu. I no longer have any Data Manager setting like I used to have. Infact all it shows when I go into there is what apps are using the most battery power. I don't even have an option to turn of the Background Data anymore or adjust battery saver settings. I'm not sure why all this is happening as I've kept the custom rom and only frozen a few apps that I confirmed to be safe by checking a safe list on several websites. I even went back and unfroze all the apps to see if maybe one of them was causing the issue. The only other thing I did was perform the Radiocomm Hack. Now I did follow a youtube video that told me that I need to apk a datamanagerservice file and also an oek (?) datamanager service file and also I had to go into Root Explorer and delete a database file of some kind. According to the gentleman who made the video, these were tracking programs that might be able to detect the radiocomm hack or some how detect that the phone was using tether. After everything was done in the video and I performed the hack, it worked perfectly. My phone worked fine and the the tethering was fine. Now a few weeks later and I'm having the problems I mentioned above. To fix this I decided I would unroot my phone and return it to factory setting then reroot again. To do this I decided to go with Overlay's 1-Click SBF.exe method. I did have the same problem as another poster in that the file had some sort of extended name on it (-dl=1). This prevented my computer from being able to read the file or recognize it. So I did what that post suggested and I deleted the "-dl=" part so that it said 1_CLICK_SBF.exe and low and behold it fixed the file. It went from a white paper icon to the green android man icon so I thought everything was ok. Well then I go to run the program and I keep gettin this "some files are corrupted" message "please close and find another download' or something of that nature. I've tried several times to redownload this file and I still keep getting this error. I tried disabling my virus protections and fire walls but still nothing worked. Can someone please tell me what I'm doing wrong and how I can get this working again. I'm not even sure if it's something with root that is causing my phone to act up, it could be the phone is bad which mean I need to contact the person I bought it from and send it back but I can't do that until I unroot the phone, return it to factory settings and see if that takes care of the battery issue and restores my data manager/battery settings to the system menu. Thank you in advance to anyone who can help me out with this.
fanofhan said:
I actually found a thread on this but it didn't actually fully address the issue. My problem is I rooted my Droid 3 a few weeks ago without any issue using the Motofail method. I actually kept the stock OS, all I did was use Titanium Backup to freeze some apps and I performed the Radiocomm Hack, all without any issue. Well now it is a few weeks later and I notice I'm having some problems with my phone. The stock battery indicator is acting wonky. I plugged in the phone to charge and when I unplugged it, the indicator continued to stay animated like it was still charging. Also when I plugged in the phone to charge yesterday, it appeared to be charging fine but when I unplugged later that evening it actually hadn't charged at all as the battery indicator was not only in the red, but when I went into About Phone in the system setting it also said the battery was at a low percentage. Another issue I'm having is with the sudden disappearance of my Battery and Data Manger within the systems menu. I no longer have any Data Manager setting like I used to have. Infact all it shows when I go into there is what apps are using the most battery power. I don't even have an option to turn of the Background Data anymore or adjust battery saver settings. I'm not sure why all this is happening as I've kept the custom rom and only frozen a few apps that I confirmed to be safe by checking a safe list on several websites. I even went back and unfroze all the apps to see if maybe one of them was causing the issue. The only other thing I did was perform the Radiocomm Hack. Now I did follow a youtube video that told me that I need to apk a datamanagerservice file and also an oek (?) datamanager service file and also I had to go into Root Explorer and delete a database file of some kind. According to the gentleman who made the video, these were tracking programs that might be able to detect the radiocomm hack or some how detect that the phone was using tether. After everything was done in the video and I performed the hack, it worked perfectly. My phone worked fine and the the tethering was fine. Now a few weeks later and I'm having the problems I mentioned above. To fix this I decided I would unroot my phone and return it to factory setting then reroot again. To do this I decided to go with Overlay's 1-Click SBF.exe method. I did have the same problem as another poster in that the file had some sort of extended name on it (-dl=1). This prevented my computer from being able to read the file or recognize it. So I did what that post suggested and I deleted the "-dl=" part so that it said 1_CLICK_SBF.exe and low and behold it fixed the file. It went from a white paper icon to the green android man icon so I thought everything was ok. Well then I go to run the program and I keep gettin this "some files are corrupted" message "please close and find another download' or something of that nature. I've tried several times to redownload this file and I still keep getting this error. I tried disabling my virus protections and fire walls but still nothing worked. Can someone please tell me what I'm doing wrong and how I can get this working again. I'm not even sure if it's something with root that is causing my phone to act up, it could be the phone is bad which mean I need to contact the person I bought it from and send it back but I can't do that until I unroot the phone, return it to factory settings and see if that takes care of the battery issue and restores my data manager/battery settings to the system menu. Thank you in advance to anyone who can help me out with this.
Click to expand...
Click to collapse
I also just want to add that I did load the phone into App Fast Mode without any problems and everything was ok. It's just when it came time to actually run the 1 Click file, I kept getting the message about parts of the zip being corrupted and to please find another download. Also I should add that I am on the .906 ota, 2.3.4, kernel 2.6.35.7-g5a4155.
There is now a full SBF zip download for 5.7.906 that you can flash with RSD Lite; see here: http://forum.xda-developers.com/showpost.php?p=39268610&postcount=241
I used it last week without issue. I unzipped the file first to make sure that it was a good download (a bad download will not unzip properly.)
[edit: here is a good "how-to" for RSD Lite: http://wiki.howardforums.com/index.php/How_to_flash_with_RSD_lite ]
You may want to make sure that you have a well-charged battery. Amazon sells a Motorola external charger if your phone does not charge the battery properly. http://www.amazon.com/Motorola-Battery-Charger-Series-Batteries/dp/B005LFXBJ6
doogald said:
There is now a full SBF zip download for 5.7.906 that you can flash with RSD Lite; see here: http://forum.xda-developers.com/showpost.php?p=39268610&postcount=241
I used it last week without issue. I unzipped the file first to make sure that it was a good download (a bad download will not unzip properly.)
[edit: here is a good "how-to" for RSD Lite: http://wiki.howardforums.com/index.php/How_to_flash_with_RSD_lite ]
You may want to make sure that you have a well-charged battery. Amazon sells a Motorola external charger if your phone does not charge the battery properly. http://www.amazon.com/Motorola-Battery-Charger-Series-Batteries/dp/B005LFXBJ6
Click to expand...
Click to collapse
First of all thank you for the reply because I really need help. The only way i've been able to do anything to my phone is mostly by watching youtube videos and following along. In other words I am a complete idiot to all of this and have no idea what i'm doing. With regards to your response about RSD Lite, I did go to the how to link but I still don't understand what to do. Unfortunately I don't have internet at my house so I can't even begin to attempt the rsdlite thing until tonight. I just feel like my nerves are shot. Nothing on this phone is working right. Infact im beginning to wonder if there is something wrong with the phone itself. This is the second d3 I've had and all the things i'm doing to this phone I did to the last and i'm having nothing but problems and I've done nothing major to the phone. I just tried tethering so I could access the internet on my laptop so I can try to fix this now and apparently the radiocomm hack didn't work either. It worked fine on my other droid3 that i ended up giving to my mom. Im beginning to think that the seller I purchased this phone from on ebay, lied about this phone not being. Refurbished or ever activated. Heck I knew it wasn't because it came already loaded with the. 906 update. Now if I can figure out how to factory restore I can see if I can get it working properly.
what is your battery level at, files will not flash if battery is too low
could cause the errors you are seeing
Sent from my Clear using xda premium
sd_shadow said:
what is your battery level at, files will not flash if battery is too low
could cause the errors you are seeing
Sent from my Clear using xda premium
Click to expand...
Click to collapse
Well a little while earlier my extended battery was in the red. Again I think this is a software issue as im sure the battery is good. Anyway I googled a fix and someone else who had the same issue accessed the Battery Manager app in settings and cleared the cache and the battery started to charge again. I cleared the cache and did a force sto then plugged the phone up and it hasn't died yet but im afraid to unplug the phone so im leaving it charged until I leave tonight to see if the battery charges. I do have the original battery as a bak up which when I placed it in the phone briefly this morning was at 80 or 90% so I think im ok battery wise. Im just freaking out about how to fix this. I know nothing about flashing roms or rsdlite or anything like that. I literally rooted the phone, froze some apps and did the radiocomm hack which doesn't seem to have worked with this phone. I just don't understand why this is happening. This all went perfectly without a hitch on the other droid 3 I had before I gave it to my mom and bought another one. Is there an easier way to unroor and restore to stock besides using rsdlite/ I don't know why Overlay's 1 click. 906.exe file is coming up as corrupted. That seemed like an incredibly easy fix. This rsdlite fix sounds incredibly complicated and as I said im an idiot to this kind of thing. I listen to the real creative geniuses and try to do what you all do.
rsd lite is very simple
download xml file
download rsd lite and install
down load moto drivers and install
open rsd lite
select the '...' button, select the xml file
boot phone to AP Fastboot, connect to pc
wait for windows to find correct drivers
select start on rsd lite, let it install xml file (10-25 min)
when rsd lite is done it will try to reboot phone,
if phone gets stuck in bootloop, wipe data in recovery and reboot
done
---------- Post added at 01:20 PM ---------- Previous post was at 01:15 PM ----------
How To Flash xml recovery files with RSD Lite
but you can not flash with a low battery, if software is corrupt battery will not charge
buy a Motorola Programing Adaptor by Team Black Hat
or Battery Desktop Charger for Motorola Droid 3 XT862
What are xml files and where do I get them? Are they specific to rsd lite or I have no idea what you're talking about with regards to xml files and which ones im supposed to download. Are you refering to the latest moto drivers for my device or some other drivers I need to download to run rsd lite? Seriously, explain it to me like you would to your 80 year old grandmother if you had one (unless you do have one). I usually watch videos of people doing what I need to do and I follow what they're doing so.....yeah i'm THAT noob.
read my how to flash xml file with rsd lite
links to every thing there
Sent from my Clear using xda premium
Ah, ok. Ill check out your link about the xml filed tonight as well as looking into downloading one of the battery apps you were talking about but the good news is that I do have a spare battery incase the one in the phone now proves not to be charging. Do you have any idea why this would be happening? I did the exact same stuff on another droid 3 and everything was fine. The first phone which I bought from a person who was upgrading did great yet this one that I bought froma verizon dealer on ebay is acting up. This phone came with stock screen cover and all the booklets and sealed battery charger and everything. I know the box wasn't sealed but with the exception of the. 90ynupdate already installed t, the phone appeared to have not been used. Is it possible that I wont be able to restore phone back to original. 890 stock that was shipped originally? I'm just trying to understand what could of happened so I know its not a faulty phone issue. Thank you Shadow for being so helpful, thank both of you that have responded. Please keep them coming lol!
fanofhan said:
Ah, ok. Ill check out your link about the xml filed tonight as well as looking into downloading one of the battery apps you were talking about
Click to expand...
Click to collapse
battery apps, will not help, and I did not suggest any
but the good news is that I do have a spare battery incase the one in the phone now proves not to be charging. Do you have any idea why this would be happening?
Click to expand...
Click to collapse
if software is corrupt, phone can not charge battery, just that simple
... Is it possible that I wont be able to restore phone back to original. 890 stock that was shipped originally?
Click to expand...
Click to collapse
even if 906 one click works, it flashes an unstable repacked 890, and recommended that 906 update is installed as part of the system restore
Yes im sorry, I had misunderstood you initially. I did have a chance to view the links so I realized what you meant after my post. Yes, I am also aware of the software possibly being corrupt, I just meant that fortunately I have z spare battery that I can pop in and use during the rsdlite fix but it does appear that my extended battery is charging since I emptied battery manager cache and force stopped. I will take it with me just in case though should I need to switch them out before I make the attempt tonight. Also I aware that the 1 click method would only be a temporary backup to .890 and that I would need to perform an update but I am just eager to see if my phone will revert back to. 890 because it came to me from a verizon authorized dealer with the latest update already installed even though they told me the phone had never been activated. It just makes me wonder if some how the operating system is locked from reverting to. 890 somehow. I just want to be able to return the phone to the condition it was when it arrived to me which was unrooted with the latest update already installed and all software functioning normally.
fanofhan said:
Yes im sorry, I had misunderstood you initially. I did have a chance to view the links so I realized what you meant after my post. Yes, I am also aware of the software possibly being corrupt, I just meant that fortunately I have z spare battery that I can pop in and use during the rsdlite fix but it does appear that my extended battery is charging since I emptied battery manager cache and force stopped. I will take it with me just in case though should I need to switch them out before I make the attempt tonight. Also I aware that the 1 click method would only be a temporary backup to .890 and that I would need to perform an update but I am just eager to see if my phone will revert back to. 890 because it came to me from a verizon authorized dealer with the latest update already installed even though they told me the phone had never been activated. It just makes me wonder if some how the operating system is locked from reverting to. 890 somehow. I just want to be able to return the phone to the condition it was when it arrived to me which was unrooted with the latest update already installed and all software functioning normally.
Click to expand...
Click to collapse
It's possible that the Droid 3 was never used. When a new update is released, the manufacturers tend to ship phones with updated software, rather than having the user go through an over the air update almost immediately.
A Droid 3 that has had 5.7.906 installed on it cannot revert back fully to an older version - the locked bootloader prevents it. I believe that the 1-click installs the system of the older version, as that can be managed, and then allows you to have the 5.7.906 upgrade installed, which you should do right away.
However, at this point I'd stay away from 1-click. This link has the SBF file that you need: http://sbf.droid-developers.org/cdma_solana/list.php
It's the third in that table, under the column "download", on the line with "5.5.1_84_D3G-66_M2-10
Blur_Version.5.7.906.XT862.Verizon.en.US" as the system build number.
You will download a zip file called VRZ_XT862_5.5.1_84_D3G-66_M2-10_1FF_01a.xml.zip. As you can tell by the name of the file, that file is a zip file. When you extract it, it will expand to 17 files, including one called VRZ_XT862_5.5.1_84_D3G-66_M2-10_1FF_01a.xml - this is the file that you will be looking for when you follow sd_shadow's instructions for RSD Lite.
In fact, just to be complete, the files that will be expanded are:
VRZ_XT862_5.5.1_84_D3G-66_M2-10_1FF_01a.xml
allow-mbmloader-flashing-mbm.bin
boot.img
cdrom
cdt.bin
device_tree.bin
ebr
emstorage.img
lbl
logo.bin
mbm.bin
mbmloader.bin
mbr
preinstall.img
radio.img
recovery.img
system.img
Click to expand...
Click to collapse
RSD Lite uses the .XML file as a list of instructions about what to do with the rest of the files.
Thank you doogald, I'm about to begin downloading the stuff I need now so that I can begin. I'm hoping everything runs smoothly since I have to have this completed by the end of my shift in the morning. I really don't want to have to stay here all day tomorrow using my employers internet to try and figure this out. Thanks both of you guys for all your help. I'll let you know how it turns out. Geez, I hope it turns out right..
Ok so right now I already feel like screaming in frustration. I can't seem to find an RSD Lite download file. The RSDlite.rar download link that I found here on XDA, doesn't work on my computer, the same as the 1 click method. I did find a download on a sight called Tucows for RSDlite 5.7 but it seems to be stuck in the "installing" phase. I went to the link that Shadows posted, taking me to the how to page for RSD Lite but again, the link there took me to the XDA link, which doesn't work. The Tucows download for RSDLITE 5.7 is showing a Window that says Windows Mobility, and it has a light blue bar that is completely full but all it says is "RSDLITE is being installed" it doesn't appear to be doing anything else. I guess I can close it and try installing it again. Ok I tried downloading the Tucows 5.7 download again but it tells me the file did not install properly the first time and I need to try installing. What is going on? I am trying to reinstall it again. Why is nothing working for me, why is everything being so difficult. I'm trying to not have a melt down but seriously, why can't I find any files that work? They all seemed to be working at some point and are working for other people right now. I need help finding a working file I think.
what version of windows?
i have several links on my main page
sd_shadow's list of links for Droid FAQs, SBF, Rooting, ROMs.... https://docs.google.com/document/d/1Goawxdx_UBF4Y8lqzHYWf8Ha3yUcRK4faq0UWIlXLWA/edit
Sent from my MILESTONE3 using xda premium
---------- Post added at 01:17 AM ---------- Previous post was at 01:14 AM ----------
try this one http://d-h.st/rLK
Sent from my MILESTONE3 using xda premium
Why can't I find a file that works?? None of the .rar files work. They all download and then have a paper icon and when I try to open and extract the files I get an error page about windows not being able to identify the files or something and then it asks me what program I want to use to open the download. The only one that unzipped was the Tucows file and that was an RSDLite5.7.msi (whatever that means) and when I extract the files and attempt the download it's a Windows Installer which I run and it looks like it's going to work but then it just stops doing whatever it's doing and does nothing until I close it at which point it asks me if I'm sure I want to close because the installation isn't complete. What is going on?? I can't believe I've been trying to find a working RSDlite file for the last 2 hours. I thought I'd be done by 3:30 and here it is 2:20am and I haven't even gotten to the first step yet because I can't find any working download.
i never let window unzip file, try 7zip link in my main page
.msi is a microsoft installer works like. exe, except alittle different
Sent from my MILESTONE3 using xda premium
sd_shadow said:
what version of windows?
i have several links on my main page
sd_shadow's list of links for Droid FAQs, SBF, Rooting, ROMs.... https://docs.google.com/document/d/1Goawxdx_UBF4Y8lqzHYWf8Ha3yUcRK4faq0UWIlXLWA/edit
Sent from my MILESTONE3 using xda premium
---------- Post added at 01:17 AM ---------- Previous post was at 01:14 AM ----------
try this one http://d-h.st/rLK
Sent from my MILESTONE3 using xda premium
Click to expand...
Click to collapse
I'm running Windows Vista Home Premium SP 2 64bit, I'm checking your page now Shadow. Bless you for replying.
ok vista 64 should be fine
Sent from my MILESTONE3 using xda premium

[Q] Need Help! Tried rooting my Note 3 for the first time and now very inoperable

To start this off im going to say that i am very new to Android devices, ive owned my Note 3 (The AT&T SM-N900A one) for nearly three weeks now spending time researching on rooting and the methods, etc. Well i just tried to and didnt quite have much success.
I followed this guide and its steps very thoroughly. http://forum.xda-developers.com/showthread.php?t=2559715
Yet it all ended with it booting up looking like new but nearly every 3 seconds errors appear about processes crashing and trying to stop, for example "Unfortunately, Direct pen input has stopped."
After that failure i went ahead and tried to undo it which probably wasnt a good idea, i followed this tutorial: http://www.droidviews.com/how-to-unbrick-att-galaxy-note-3-sm-n900a/.
I ended up at the exact same place, same error over and over. Does anyone know how to fix this?
Thank you.
(I apologize if this had been brought up before i went searching but found nothing that was a solution to my problem.)
baileynapier said:
To start this off im going to say that i am very new to Android devices, ive owned my Note 3 (The AT&T SM-N900A one) for nearly three weeks now spending time researching on rooting and the methods, etc. Well i just tried to and didnt quite have much success.
I followed this guide and its steps very thoroughly. http://forum.xda-developers.com/showthread.php?t=2559715
Yet it all ended with it booting up looking like new but nearly every 3 seconds errors appear about processes crashing and trying to stop, for example "Unfortunately, Direct pen input has stopped."
After that failure i went ahead and tried to undo it which probably wasnt a good idea, i followed this tutorial: http://www.droidviews.com/how-to-unbrick-att-galaxy-note-3-sm-n900a/.
I ended up at the exact same place, same error over and over. Does anyone know how to fix this?
Thank you.
(I apologize if this had been brought up before i went searching but found nothing that was a solution to my problem.)
Click to expand...
Click to collapse
Have you performed a factory data reset since the last attempt?
440bro said:
Have you performed a factory data reset since the last attempt?
Click to expand...
Click to collapse
Yes i have,a few times, it just then reboots with the setup and that error still occurring.
baileynapier said:
Yes i have,a few times, it just then reboots with the setup and that error still occurring.
Click to expand...
Click to collapse
That error is a bugger to get rid of, if you even can. i had this happen and had to return my device to the store. BUT that was before we had a working back to stock MJ5 solution.
http://forum.xda-developers.com/showthread.php?t=2559715
If you were on MJ5 this will get you back to out of the box stock with or without Root, its up to you.
i have used this twice and has worked smoothly both times, just make sure you download the files needed and follow the steps.
the2rrell said:
That error is a bugger to get rid of, if you even can. i had this happen and had to return my device to the store. BUT that was before we had a working back to stock MJ5 solution.
http://forum.xda-developers.com/showthread.php?t=2559715
If you were on MJ5 this will get you back to out of the box stock with or without Root, its up to you.
i have used this twice and has worked smoothly both times, just make sure you download the files needed and follow the steps.
Click to expand...
Click to collapse
That is the method OP used to get root....
OP, you should have used Kingo... Now you will have to redo that whole process just to restore back to stock. You had a bad flash or a bad download.
Sent from my SM-N9005A using XDA Premium 4 mobile app
28248965 286a
the2rrell said:
That error is a bugger to get rid of, if you even can. i had this happen and had to return my device to the store. BUT that was before we had a working back to stock MJ5 solution.
http://forum.xda-developers.com/showthread.php?t=2559715
If you were on MJ5 this will get you back to out of the box stock with or without Root, its up to you.
i have used this twice and has worked smoothly both times, just make sure you download the files needed and follow the steps.
Click to expand...
Click to collapse
That was the method that originally got me into this situation and i just tried it again step by step and i am still having the issue.
One thing that has caught my eye is that this was my devices information before ever trying any rooting process or anything:
MODEL NUMBER: SAMSUNG-SN-N900A
ANDROID VERSION: 4.3 (Jelly Bean)
BASEBAND VERSION: N900AUCUBNB4
KERNEL INFO -
3.4.0-1625098
se.i[email protected] #1
Mon Feb 10 21:13:28 KST 2014
BUILD NUMBER: JSS15J.N900AUCUBNB4
SELINUX STATUS: Enforcing
Is there any possible way to get it back to being a BNB4 device like the information above?
graydiggy said:
That is the method OP used to get root....
OP, you should have used Kingo... Now you will have to redo that whole process just to restore back to stock. You had a bad flash or a bad download.
Sent from my SM-N9005A using XDA Premium 4 mobile app
Click to expand...
Click to collapse
tis the reason i directed him back to that thread. i know they are working on a easier odin flash to return to stock in another thread. dont know why he was using that to get root, but he will now need to use it to get booting back to normal again.
anyway, apologies for not being more clear.
so to sum it all up, redownload the files in case you got a bad one and repeat the process my good sir.
the2rrell said:
tis the reason i directed him back to that thread. i know they are working on a easier odin flash to return to stock in another thread. dont know why he was using that to get root, but he will now need to use it to get booting back to normal again.
anyway, apologies for not being more clear.
so to sum it all up, redownload the files in case you got a bad one and repeat the process my good sir.
Click to expand...
Click to collapse
Okay, thank you guys very much but its back to functioning properly! :victory:
Now am i just trying to accomplish a root, but that doesnt seem to be working, after i put the root de la vega files onto the sdcard SuperSU never installs upon restart, why is it not auto-installing like it seems to be expressed as in the tutorial?
EDIT: Okay guys, nevermind about the root, i just used Kingo.
baileynapier said:
Okay, thank you guys very much but its back to functioning properly! :victory:
Now am i just trying to accomplish a root, but that doesnt seem to be working, after i put the root de la vega files onto the sdcard SuperSU never installs upon restart, why is it not auto-installing like it seems to be expressed as in the tutorial?
Click to expand...
Click to collapse
use kingo 1.1.8 it is a lot easier
baileynapier said:
ive owned my Note 3 (The AT&T SM-N900A one) for nearly three weeks now spending time researching on rooting and the methods, etc.
Click to expand...
Click to collapse
How did you NOT find Kingo right away?
What kind of research did you do for 3 weeks? lol
Well, I'm glad you're good to go now. The devs on this site are exceptional and you are lucky to have them. (me too).
baileynapier said:
Okay, thank you guys very much but its back to functioning properly! :victory:
Now am i just trying to accomplish a root, but that doesnt seem to be working, after i put the root de la vega files onto the sdcard SuperSU never installs upon restart, why is it not auto-installing like it seems to be expressed as in the tutorial?
EDIT: Okay guys, nevermind about the root, i just used Kingo.
Click to expand...
Click to collapse
So how did you get it back functioning properly? I am at the same point. I bricked my N3 screwing around with getting Face Unlock to work. So I followed the steps of Restore for MJ5 post, and immediately upon the final boot into setup, the Direct Pen Input error started, and makes the device useless. What fixed yours?
Re-download all the files and retry. Also, verify the size. I think you may have a corrupt file somewhere.
And factory reset after installing a ROM, even if it's the same ROM you had. Any ROM, on any phone, not just this one. Different ROMs store data in different locations, and if a ROM picks up the data from a previous ROM, that may bot be the data it wants, so it causes things to crash.
Ok thanks for the replies. I actually tried a factory reset after seeing the error, but it didn't help at all. And I did run a checksum on the only file that displayed a number, when I originally downloaded the files. But as would be expected, after all simple efforts to fix the issue failed, I started fresh on a whole different PC, downloaded all of the files again, used a different USB cable, and installed everything all over again. And low and behold, the second time was a total success. I can't explain what made the difference, and the checksum result showed an accurate download both times. But this is the nature of the beast isn't it?
Thanks,

Categories

Resources