[Q] Bootstrap issue with newly unrooted D2G - Droid 2 Global General

Sorry if this is the wrong place to post this. I had to unroot my work phone because my firm said the servers identified my phone as having an operating system not supported by our security system and they suspended my server access.
So I uninstalled most of the "root" apps, thawed all the bloatware I froze in Titanium, disabled all the crap in Startup Auditor and then unrooted with Z4root. It literally took a minute for Z4root to unroot the phone.
I then brought my phone to IT to do a factory reset/wipe with one of our IT people so they can put me back on the server and I took my phone back.
The problem is whenever I start my phone, I get the Clockwork Mod screen (see attached). FYI I did not delete Bootstrap just in case I needed to restore for some reason.
BTW I did wipe data/factory reset in Bootstrap and when I rebooted the screen still came up and I'm definitely not rooted since immediately after unrooting with Z4root, Superuser was gone and Titanium said I didn't have root.
Any thoughts how to get rid of Bootstrap?
Thx!

The easy way is to flash SBF. The hard way is to root again and manually remove the bootsrap point. Then unroot again. SBF is much faster and convenient. Edit: much faster no - but much more convenient yes
Edit: if you want to go the long way, once you rooted again from PC mount system in RW mode, delete /system/bin/logwrapper then rename /system/bin/logwrapper.bin to /system/bin/logwrapper. Reboot and custom recovery should be gone. Unroot with Z4root and you are done.

leobg said:
The easy way is to flash SBF. The hard way is to root again and manually remove the bootsrap point. Then unroot again. SBF is much faster and convenient.
Click to expand...
Click to collapse
Thanks. I was afraid someone was going to say that. Is SBFing n00b-proof like z4root was with rooting my phone?
Edit: if you want to go the long way, once you rooted again from PC mount system in RW mode, delete /system/bin/logwrapper then rename /system/bin/logwrapper.bin to /system/bin/logwrapper. Reboot and custom recovery should be gone. Unroot with Z4root and you are done.
Click to expand...
Click to collapse
What does that mean??

jjdavola said:
Thanks. I was afraid someone was going to say that. Is SBFing n00b-proof like z4root was with rooting my phone?
What does that mean??
Click to expand...
Click to collapse
Huh, I was afraid you would say that Edit - I am sorry - I was about to put the commands you need to type using ADB from PC, but decided it will be confusing. ('from PC' to be scratched)
Well - SBF-ing is the easier way for you then. Simply make sure all pre-requirements are fulfilled (proper drivers installed, software loaded) and it is as easy as the Z4root. Read these instructions and follow them carefully and you will be set in no time

leobg said:
Huh, I was afraid you would say that Edit - I am sorry - I was about to put the commands you need to type using ADB from PC, but decided it will be confusing. ('from PC' to be scratched)
Well - SBF-ing is the easier way for you then. Simply make sure all pre-requirements are fulfilled (proper drivers installed, software loaded) and it is as easy as the Z4root. Read these instructions and follow them carefully and you will be set in no time
Click to expand...
Click to collapse
Thanks again!
OK. I flashed the SBF , it said PASS so I unplugged the phone and rebooted and Bootstrap didn't appear when I booted back up. What I believe to be a problem is that everything appears to be exactly the same as it just was (e.g. no apps were deleted, LauncherPro and my settings were still there etc.). Plus the System Updates option is not clickable anymore and my phone number was changed.
FYI I was thinking that the SBF would have just totally erased everything and I'd have to start from scratch installing apps etc.
Any thoughts?? Should I do another factory reset?

Yes - SBF will not erase data partition (user data). It is recommended you do factory reset once SBF is complete to clear up all the stuff that customizations before might have caused. At least you should clear cache partition to avoid wired behaviour from the phone. To delete cache - boot phone in stock recovery (power up while pressing X button - when you get the triangle with the android guy - press the magnifying glass button on the keyboard - menu will show up. Use the arrows and OK button to navigate. Options in menu are self explanatory I believe. Deleting cache will not delete your data, but deleting cache & data will delete data (factory reset)
To fix the phone programming (CDMA Verizon) - dial *228 option 1

leobg said:
Yes - SBF will not erase data partition (user data). It is recommended you do factory reset once SBF is complete to clear up all the stuff that customizations before might have caused. At least you should clear cache partition to avoid wired behaviour from the phone. To delete cache - boot phone in stock recovery (power up while pressing X button - when you get the triangle with the android guy - press the magnifying glass button on the keyboard - menu will show up. Use the arrows and OK button to navigate. Options in menu are self explanatory I believe. Deleting cache will not delete your data, but deleting cache & data will delete data (factory reset)
To fix the phone programming (CDMA Verizon) - dial *228 option 1
Click to expand...
Click to collapse
I cleared the cache and did the activation earlier. If I really need to, I'll do another factory reset some other day since unrooting, reseting and flashing wore me out for today.
Thanks again for your patience and assistance. I greatly appreciate your help.

i had the same problem and i figured out why it does it generally. Though it is weird for your case. When you have anything that requires root set to launch at boot (e.x SetCPU for me) for some reason it boots into the recovery. But when you disable these things it boots regularly.

Related

Anyway to restore bricked phone after unplugged from odin restore??

So i was restoring my phone on odin when my daughter pulled on the usb before odin restored my phone now i have a symbol when going on download mode. Its of a (phone---!---computer). Is there anyway to restore after that?
Thanks any help will be appricated
I think that happened to me after flashing some funky things that didn't work. Boot to Odin mode like you would normally:
Disconnect USB.
Pull battery.
Put battery back in (do not turn on!)
Hold down both volume keys and plug in the USB cable to phone & PC while holding them.
Phone should show the PC & Phone and it should look very angry like it has before.
Odin should detect your phone on COM## (where ## is some number). You should be able to repeat the Odin process just the same as normal.
Aou said:
I think that happened to me after flashing some funky things that didn't work. Boot to Odin mode like you would normally:
Disconnect USB.
Pull battery.
Put battery back in (do not turn on!)
Hold down both volume keys and plug in the USB cable to phone & PC while holding them.
Phone should show the PC & Phone and it should look very angry like it has before.
Odin should detect your phone on COM## (where ## is some number). You should be able to repeat the Odin process just the same as normal.
Click to expand...
Click to collapse
You are amazing bro thanks. Another question will i be able to reflash infused rom?
After you use the ultimate unbrick, you will need to:
-Root your device again (if applicable... some versions of the unbrick have root included)
-(You might get a bunch of FC's on apps when it starts): Wipe data from 3e recovery
-Install the modified 3e recovery
-Install CWM and Rom Manager
-Download/install the rom through Rom Manager.
-Alternatively, you can install the rom through CWM, but I find Rom Manager to be very nice and easy.
This set of instructions you'll find scattered around the forums.
EDIT: forgot to add: you you'll just need to wipe user data, and wipe any/all caches. NO need to wipe your internal sdcard!
Oh, and as a rule of thumb: never, ever use Titanium Backup to restore SYSTEM DATA. It will cause all sorts of hellish bugs.
bvspunjah said:
You are amazing bro thanks. Another question will i be able to reflash infused rom?
Click to expand...
Click to collapse
yes. you will. i had to ODIN my phone when something messed up when i tried to upgrade from 1.5.3 to V2 stable. did ODIN and accidentally did the same thing you did(accidentally pulled USB).
dddeemann2 said:
yes. you will. i had to ODIN my phone when something messed up when i tried to upgrade from 1.5.3 to V2 stable. did ODIN and accidentally did the same thing you did(accidentally pulled USB).
Click to expand...
Click to collapse
Yeah, something went wrong for me also. I did follow instructions normally (i.e. let the voodoo disable do its work converting back, etc.), but it still gave me a samsung boot-loop. The Odin/unbrick-and-retry method worked flawlessly after that.
Pretty much, as a rule of thumb with this device, if it powers on to ANY screen whatsoever, it's likely recoverable. If it doesn't turn on (black screen, no lights), you're hosed. Trust me, it's very, very difficult to get an Infuse to this state. I am one of a very small handful that has succeeded in this.
Aou said:
After you use the ultimate unbrick, you will need to:
-Root your device again (if applicable... some versions of the unbrick have root included)
-(You might get a bunch of FC's on apps when it starts): Wipe data from 3e recovery
-Install the modified 3e recovery
-Install CWM and Rom Manager
-Download/install the rom through Rom Manager.
-Alternatively, you can install the rom through CWM, but I find Rom Manager to be very nice and easy.
This set of instructions you'll find scattered around the forums.
EDIT: forgot to add: you you'll just need to wipe user data, and wipe any/all caches. NO need to wipe your internal sdcard!
Oh, and as a rule of thumb: never, ever use Titanium Backup to restore SYSTEM DATA. It will cause all sorts of hellish bugs.
Click to expand...
Click to collapse
im not to sure what FC means and i also dont now how to wipe user data and caches. sorry im the ultimate noob
FC = force close
wiping data and cache will show as an option when you flash V2.just follow GTG's instructions when installing V2 ROM and youll see him mentioning it.
And this should be in General, as it has nothing to do with development. (by the way, Q&A is coming.)

Help: Unable to hard reset my Sprint Nexus S

Hi there,
I need some help here. My wife's Sprint Nexus S is acting up - keep popping messages such as "Unfortunately XXX has stopped." So I decided to do a hard reset. I followed the instructions but weirdly the phone did not do it. It acted like doing the hard resetting but then rebooted with nothing changed. I tried both the software way - Settings, factory reset, and the hardware way - Vol up button + Power, then recovery, then Vol up + Power again at the Android with exclamation image, chose "Wipe all data and factory reset." However, the phone boots with nothing changed.
Can anyone help me with this? What else can I try?
Thanks much in advance.
<DELETED>
You could try fixing the permissions on the files through Rom Manager; it fixes a lot of Force Close generally.
kwudude said:
Have you tried installing a custom recovery and doing a hard reset through that route yet? E.G. ClockworkMod or TWRP
Click to expand...
Click to collapse
Thanks. I will give it a try. Can you point me to some instructions / files for downloading, etc.?
Cpu.gastronomy said:
You could try fixing the permissions on the files through Rom Manager; it fixes a lot of Force Close generally.
Click to expand...
Click to collapse
This one is actually the Sprint stock rom untouched. So... no Rom Manager on it. Thanks anyway. I guess a custom recovery is the only way to go now...
<DELETED>
I wouldn't install a custom recovery, and ultimately technically void your warranty, for the sole purpose of resetting it though...
Just use a one click root tool, it flashes superuser, cmw, but keeps the rest of the (stock) rom you're on!
---===:::Greetzz, jojoost:::===---
Sent from my iPad using Tapatalk HD
Thanks to you all for all the good suggestions. I have tried several things but did not succeed.
1. Flashed a clockworkmod recovery. That was successful. So I went ahead to use its factory reset function. The process completed without error but once rebooted, the phone remains the same as before.
2. Connected the phone to a PC, turned on USB storage, copied a ROM image zip file to a folder. Then tried to install it through Recovery. But the file I copied was nowhere to be found.
3. Put then phone into the bootloader mode, connected to PC, use fastboot to flash boot, system, recovery, userdata, radio image files. All went through with any issue. Rebooted, phone is the same.
In short, whatever I do, the phone remains the same. No changes can be made.
I also tried the one-click tool but could not proceed ahead. It required USB debugging turned on. I turned it on, the check mark was there, but it was really NOT turned on because on the PC, the message is that it is not on. On the phone, if I switch to a different application, or simply go back one step, and then go to developer option, the checkmark was not turned on.
It feels like the internal memory/storage becomes read-only. No changes can be made. I am not sure if the hardware is bad, or some permission issue.
Any ideas that I should try next?
From what I read and understand, I think I had a bad nand problem. Guess time to let the phone go RIP.

Poor battery life since upgrade

Ever since the Jelly bean update my battery life has been awful. This issue isn't happening all the time however, a restart seems to resolve the issue. When my battery drains really fast Android OS is using anywhere from 30%-50%.
Anyone else having this?
richport29 said:
Ever since the Jelly bean update my battery life has been awful. This issue isn't happening all the time however, a restart seems to resolve the issue. When my battery drains really fast Android OS is using anywhere from 30%-50%.
Anyone else having this?
Click to expand...
Click to collapse
Have you tried to Wipe Data and Cache???? (Not through configuration, inside android. Wipe data and cache turning your phone on with 'vol +' and 'vol -' pressed.) When you see the black screen with white letters, scrool down using 'vol -' to 'RECOVERY' and press 'vol +' to select. When the green android appears, press 'vol +' and 'vol -' at the same time and you will have the option to wipe data and cache.
Then, reboot your phone and it will start as a new phone with jelly bean.
I saw a significant difference on my phone after this.
=p
zilian28 said:
Have you tried to Wipe Data and Cache???? (Not through configuration, inside android. Wipe data and cache turning your phone on with 'vol +' and 'vol -' pressed.) When you see the black screen with white letters, scrool down using 'vol -' to 'RECOVERY' and press 'vol +' to select. When the green android appears, press 'vol +' and 'vol -' at the same time and you will have the option to wipe data and cache.
Then, reboot your phone and it will start as a new phone with jelly bean.
I saw a significant difference on my phone after this.
=p
Click to expand...
Click to collapse
Are you rooted, and if so, did you maintain root? I was looking at the build.prop file and noticed a comment that one of the props is to allow the mounting of /system on the data partition which implies that it could be an image on the data partition or block of the data partition. I would like to wipe my data and cache so long as it didn't reinstall the entire OS causing me to lose root.
PantsDownJedi said:
Are you rooted, and if so, did you maintain root? I was looking at the build.prop file and noticed a comment that one of the props is to allow the mounting of /system on the data partition which implies that it could be an image on the data partition or block of the data partition. I would like to wipe my data and cache so long as it didn't reinstall the entire OS causing me to lose root.
Click to expand...
Click to collapse
Actually I'm on ICS rooted. But I know that if you wipe data and cache on JB, unfortunately ur gonna loose root. =/
I read people saying that there is a file that if you clear its data, everything gets back to normal and the battery drain stops. I just don't remember which one is. Do a little search here at the forum that you will find. =]
Thanks for both replies; the answer and the instructions.
I'm about to take the leap into the uncertainties surrounding an unlocked boot-loader, I think. Its been inevitable at some point, I guess...
It turns out that I'm one of the incredibly lucky ones. It wiped my internal sd but su was unaffected. All my rooted apps, except for a modifiaction to build.prop, a backup of build prop, and the su binary, were simlinked into root from a folder in data which I can restore from the tarball I'de made. The symlinks are still there, as was the modification to build.prop which meant I had no buttons at the bottom of the screen to start with. Perhaps because of this; no extra apks detected or something, and with the supersu.apk on data. I don't know if having the reinject root option of supersu previously checked mattered or not. In any case, bootloader still locked and everything wiped. Now I have to put it all back to how it was but that was a given, either way.
This had nothing to do with the rootkeeper app btw. When I installed it, it still had the same settings as prior; didn't have re-insert root or anything.
Sorry for posting a useless comment since I don't know what made my situation differant than what other people have had happen, keeping the binary but losing proper file permissions on it from what I had read last night, but I'm happy that it worked out for me and telling my wife would be futile.
Also, I cleared cache and did a wipe data/system restore... twice. The first time, I made it most of the way through the initial Android setup and it popped me back a few selections; opting not to enable to turn on Google+ and then the screen flickered and it pulled me back to entering my Google account again so I powered off and did the clear cache and wipe again. What luck!
Bringing this thread back. Lately I've been getting some poor battery life on my maxx HD. I used to be able to get through the day with around 50% battery left at the end of the night. Now that number has been steadily decreasing over time. Does the recovery method mentioned also wipe my apps? I would love to finally root the phone to remove all the crapware but everything seems to be for the 925 and not the 926.
Sent from my DROID RAZR HD using Tapatalk 2

[Q][HELP] I lost my IMEI! can everybody help?

*D821 (E) - hammerhead
*KTU84M
*HW version: rev_11
*bootloader version: HHZ11k
*baseband version: M8974A-2.0.50.1.13
*carrier info: NONE (is this wrong?)
*signing: production
*secure boot: enabled
*lock state: locked
#I didn't touch this phone's system, still original.
my story:
so it's been 3 weeks since I bought my phone. I was happy with it, nothing was wrong.
a week later, the 4.4.3 came out, I updated it, and nothing was wrong too.
until last night, I turned off my phone, curious to see how the Nexus 5's recovery look like,
I pressed (volume down + power), and I noticed that it enters FASTBOOT mode. and I just learned, navigate with the volume buttons and select with power button.
NOTICE: I'm already familiar with things like this, I was in the Galaxy W forum and Galaxy SIII mini forum. *yes lol I came from Samsuck
so I selected recovery mode and enter it.. I saw the android logo there, the healthy one, not the murdered robot with a red triangle on it.
I saw nothing but that logo, I pressed volume up button and the text showed up. I navigate down with volume down button, until it was down at the "wipe cache partition", I wanted to go up to reboot my phone, but I realized, the up button just a switch to hide or show the recovery text, so there's only one choice, press the power button, *if I press the power button, I wipe the cache because it selects "wipe cache partition"*.
and then it writes "wiping the cache", I was confused why it was so long, until I decided to reboot with holding the power button.
NOTICE: it is strange to wait sooooo long for cache wiping. I know this.
the system turned on. I'm not sure if the cache wiped cleanly, I'm afraid it will make the system error. so I decided to change my runtime from ART to Dalvik, so the cache wiped out and built again, strange process that took only 64 apps to optimize, that before it was around 110 apps. and then after reboot, I decided to go ART again to saw how many apps that optimized, LOL it was again, 64.
I reboot my phone again, and wait the reception, LOL strange I got no signal in my home *usually full*.
NOTICE: the signal has already gone after first cache wipe.
somehow I go to About Phone, Status on the Settings, and I found out the IMEI is UNKNOWN. I tried to check it with *#06# and it shows nothing.
I repeat the process how I get to the recovery and try to wipe cache, and it said, "error: can't mount /cache".
so I think the cache was gone?? I look to the "Explorer" app *the one who makes the root version too (Root Explorer)*, well the cache partition still there.. LOL
MY QUESTION:
1. am I having a defective Nexus 5? or there is a bug?
2. my IMEI lost, I have 2 expectations: my EFS/IMEI is truly lost, or the system just can't detect it? how can I know?
3. I saw a thread that tells me Nexus 5 doesn't have EFS partition backup, so where does the EFS located?
4. if I follow you guys, unlocking bootloader, rooting and etc. can I make my phone's state default again? *I don't mean fix this thing, just go default*
5. most important thing, HOW CAN I GET MY PHONE BACK TO NORMAL?? *peace bro
please help, right now I'm trying to reset my phone as soon as my backup finishes.
thx
I think people have remedied this problem by flashing the factory image. If that doesn't work then it is probably a hardware defect and will have to be replaced.
There's an option in the stock recovery which reads "Reboot System Now". You could have selected that if you didn't want to do anything.
1. No, the cache partition got messed up and hence the unknown IMEI and signal loss.
2. The system just can't detect it because of the reason mentioned above.
3. EFS is located on the /efs partition but you need root to back it up or restore it.
4. No need to root the phone to fix this. Go back to the stock recovery and wipe cache partition again and this time around WAIT PATIENTLY for it to complete. This should fix it.
5. ^^^^^^
vin4yak said:
There's an option in the stock recovery which reads "Reboot System Now". You could have selected that if you didn't want to do anything.
1. No, the cache partition got messed up and hence the unknown IMEI and signal loss.
2. The system just can't detect it because of the reason mentioned above.
3. EFS is located on the /efs partition but you need root to back it up or restore it.
4. No need to root the phone to fix this. Go back to the stock recovery and wipe cache partition again and this time around WAIT PATIENTLY for it to complete. This should fix it.
5. ^^^^^^
Click to expand...
Click to collapse
as I told you before, I can't select "reboot system now" because the volume up button strangely working as show/hide text. wipe cache partition, the /cache can't be mounted.
BirchBarlow said:
I think people have remedied this problem by flashing the factory image. If that doesn't work then it is probably a hardware defect and will have to be replaced.
Click to expand...
Click to collapse
well, my phone still original untouched.. what if you were me, having an untouched phone and it has already been like this? I don't think I would touch it ._.
anyway, @BirchBarlow @vin4yak , I can go adb and fastboot without root or unlock bootloader right? thx anyway
IvanKurnia said:
as I told you before, I can't select "reboot system now" because the volume up button strangely working as show/hide text. wipe cache partition, the /cache can't be mounted.
Click to expand...
Click to collapse
Strange indeed. Yeah, those errors are common. Just try wiping cache multiple times. If not, factory reset the device.
IvanKurnia said:
well, my phone still original untouched.. what if you were me, having an untouched phone and it has already been like this? I don't think I would touch it ._.
Click to expand...
Click to collapse
Since you're responsible for this mishap, I would certainly try to fix it myself if I were you. Wiping cache/factory reset is the only thing you can do with a locked bootloader. If that doesn't fix it, the phone's hosed!
IvanKurnia said:
anyway, @BirchBarlow @vin4yak , I can go adb and fastboot without root or unlock bootloader right? thx anyway
Click to expand...
Click to collapse
ADB is used whilst you're in Android OS/custom recovery. You first need to unlock the bootloader, flash/boot a custom recovery and then flash the supersu.zip to gain root. I'm not sure what purpose it will serve in your situation though??
this happened to me too. and I waited for the the wipe cache operation for 15 minutes. After a forced reboot the phone was not connecting to the cell network, had a 1970 date and gave various google errors. I went back to recovery, noticed the comatose android and the missing cache partition messages but again I selected wipe cache and this fixed it. It took just a minute or so to create and format it. After the reboot the phone was fine. phew...
This problem happens when the cache partion is not formated properly. You can't take screenshots either, right? You should try to format the cache partition again, and again until your phone becomes normal, or unlock bootloader and flash the cache.img from the stock images. You can find all the instructions about unlocking bl and flashing cache image in the sticky posts of the general forum.
Tapatalk-kal küldve az én Nexus 5-el

Storage is full but I just did a reset?

Hi,
My nexus 5 died a few weeks ago. Today I got a used motherboard to replace the broken one. Phone went on but still had personal files and a password from the previous owner (which had a cracked screen so he couldn't delete his files I guess). I did a factory reset via the recovery mode. Booted the phone up, logged in with my google account and selected the app backup thingy. So I get into the homescreen but my apps are not installing and I get a message my storage is full and it can't install apps and sync etc.
What's wrong? Did the factory reset fail to delete the files from the previous owner and how can I fix this?
Thanks
There's no such thing as a backup thingy. Learn the correct terms if you want to be understand. You dont state the recovery. Stock? CWM? TWR?. Lets try twr. That has two wipes. Did you tick the box to wipe the SD card?
SENT BY ENTANGLEMENT
zerosum0 said:
There's no such thing as a backup thingy. Learn the correct terms if you want to be understand. You dont state the recovery. Stock? CWM? TWR?. Lets try twr. That has two wipes. Did you tick the box to wipe the SD card?
SENT BY ENTANGLEMENT
Click to expand...
Click to collapse
Hi,
I'm not familiar with rooted android devices so I'm sorry but I don't mean what CWM/TWR is. So I guess it's just stock. I pressed volume and power buttong on boot up, selected recovery mode. Then I pressed the power button and volume up button and I selected wipe data/factory reset. Then the phone turned on just like when you take it out of the box. I logged in with my google account and with backup thingy I meant the option to redownload your apps and widgets like how they used to be on your previous device.
teunko123 said:
Hi,
I'm not familiar with rooted android devices so I'm sorry but I don't mean what CWM/TWR is. So I guess it's just stock. I pressed volume and power buttong on boot up, selected recovery mode. Then I pressed the power button and volume up button and I selected wipe data/factory reset. Then the phone turned on just like when you take it out of the box. I logged in with my google account and with backup thingy I meant the option to redownload your apps and widgets like how they used to be on your previous device.
Click to expand...
Click to collapse
Hi,
Thanks for providing more details about your issue (I guess). xP
Anyways. You need to open http://forum.xda-developers.com/showthread.php?t=2784527 in another tab, read the intro if you want, but you should definitely read post #2, chapters 1 and 4.
zerosum0 said:
There's no such thing as a backup thingy. Learn the correct terms if you want to be understand. You dont state the recovery. Stock? CWM? TWR?. Lets try twr. That has two wipes. Did you tick the box to wipe the SD card?
SENT BY ENTANGLEMENT
Click to expand...
Click to collapse
What an elitist arse, it's pretty clear what the poster meant. By the way understand isn't the same as understood, understand?

Categories

Resources