I had Android 3.2 rooted on my CDMA Tablet. I won the tablet in a contest and I didn't want to pay for the 4G so i bypassed the Activation. Now, I forgot to remove root then wipe, but instead I wiped data (didnt think i would need a backup because so used to not doing so on the droid X), and now I can't get past (Please wait while we set up your tablet.....Please wait while your tablet is getting activated...sorry no network is available please turn off device and reinsert simcard) Am I screwed from this point? I cant get the tablet to be read via Odin.
*Edit*
I got it to read in Odin finally, but anything I flash trying to get back to stock or anything like that is causing me to still get the error of activation.
Did you skip the activation or did you do something else?
Could you describe you steps in a little more detail? You rooted the device and tried to achieve what?
Related
Some of you might have seen my earlier thread, my ReZound is rooted. HTC sent out the ICS update my phone attempted to install it and afterwards it would not advance past the white HTC screen. After many hours of playing around with it (being semi-noobish to all things rooting, but decently knowledable with technology) I realized that on the H-boot screen it was telling me that the Image was missing. I assumed that the HTC update deleted it? After thinking about it, I thought that maybe installing a custom ROM would fix this, so I grabbed Scotts Clean ROM. Sure enough I did and I was finally able to advance past the white HTC screen. It looks as if everything is working fine with the phone now EXCEPT I have no data and no calling connection. Im assuming that my phone is just that messed up from the attempted upgrade this morning that im missing files needed for the connection.
My next thought was to just say heck with it and do a factory reset hoping to get back to a bone stock phone that at least functioned, but when I try the factory reset it doesnt work....
Any ideas of what I should do next? Ive spent 5-6 hrs trying to fix this phone today, I really hope to get something figured out. Thank you everyone for your help!
EDIT: I feel like an idiot... Because of putting the battery in and out for resets I left the back off the phone. I now have service. Main issue now is that when I try to call out, as soon as I type a number on the dialer it freezes up and restarts itself....
The phone still tries to look for the old image on the restart and gives me issues every time on startup still also. Id like to be able to get this back to not needing a ROM....
If it were me, I would download the official RUU for ICS found here: http://www.androidpolice.com/2012/0...cream-sandwich-ruu-for-final-ota-3-14-605-12/ IIRC, mirror #3 was the fastest. Then follow the directions from that site:
After downloading the file, rename it to "PH98IMG.zip" (no quotes)
Place the renamed file onto the root of the SD Card
Power down your device
Reboot into the bootloader by holding VOL DOWN + Power
The flashing process should begin automatically
Let the device reboot, and you should be done.
That will get you up and running. Then you can go about rooting it again if you like.
I know there are lots of posts about bicks, but after a week searching I could not find any fix for my problem.
I have a S-Off, rooted GSM Evo 3D running Yoda ICS ROM and 4ext Recovery. One day, I was charging it when it hung, I restarted the phone, but it went directly to the bootloader (I didn't touch anything), as I was unaware of what was happening, I simply power it off (using the menu option), when I tried to power it on again, I got no success, only a dim red light appeared, and it is this way eversince.. I cannot power it on, go to the bootloader or anything, the computer recognizes it as QSUSB-DLOAD but there is no partition on it (I tried both Linux and Windows). I tried some unbricking methods without success. I am in Brazil, I tried to call HTC but they said I have to send the device to the origin country (mine is from Rogers, I believe it is Canada), but I don't even know where to send and I'd prefer to fix it by myself if possible. I am open to suggestions anyone could help?
Thanks a Lot!!
AW: [Q] Hard Brick evo 3D
Does adb detect the device?
In that case you could try to run a ruu...
If he can get it into recovery mode then yes. Most of the time its usually something that the end user has done to make it get bricked. I am not saying he actually did something. We also don't know what he has done with his . Phone changing your cid is a good way to brick it. Pulling the battery during a ruu update, flashing a CDMA firmware etc things like that are guaranteed brick makers. However there's only one solution I know of should you not be able to boot into recovery. Try and Google up JTAG. I'm fuzzy on the details about how it works but it can restore your hboot. If you know somebody that knows how to do it, that's your best shot. Otherwise, you will have to send it into HTC Canada or you could try to buy the JTAG hardware and learn how to use it to restore your phone. If anybody has a solution for him please feel free to chime in. Sorry about your phone though. I wish you the best of luck on getting it restored.
Quantenhall said:
Does adb detect the device?
In that case you could try to run a ruu...
Click to expand...
Click to collapse
No, it does not detect the phone. I was searching more thoroughly and found some places here in Brazil that do jtag repairs, I think I will give it a shot.
Thanks!
RonaldoPA said:
No, it does not detect the phone. I was searching more thoroughly and found some places here in Brazil that do jtag repairs, I think I will give it a shot.
Thanks!
Click to expand...
Click to collapse
Just to let you guys know, I did the jtag repair and it worked for about a week, I put back my cfw and yesterday, out of nothing it stopped work again. It was working normally, I left it on the table, checked the time and went do other things, later (about 2 hours) I took the phone to set the alarm for the next day and it didn't turn on...
If someone has any ideas, I appreciate!
Thanks in advance.
RonaldoPA said:
Just to let you guys know, I did the jtag repair and it worked for about a week, I put back my cfw and yesterday, out of nothing it stopped work again. It was working normally, I left it on the table, checked the time and went do other things, later (about 2 hours) I took the phone to set the alarm for the next day and it didn't turn on...
If someone has any ideas, I appreciate!
Thanks in advance.
Click to expand...
Click to collapse
Try using this to unbrick the phone (aimed specifically for DLOAD error, but has worked for other cases): http://forum.xda-developers.com/showthread.php?t=1522351. Afterward, use a combination of both the official instructions from Unlimited.io and this video tutorial to achieve S-OFF. The instructions give you an idea of how-to, the video actually gives you a better sense for the timing. The timing is very specific that needs to be done just right (might take quite a few times to get it done).
If you have an HTC Evo V 4G with Virgin Mobile USA, then you can use this flashable RUU to return to stock (I extracted this from the RUU.exe; just ensure that your bootloader is LOCKED. You can check this by Holding Pwr+Vol Down during boot; top of the screen should say LOCKED). If your phone skips loading into your bootloader and boots into the main OS, pull the battery to bypass quickboot (or turn it off in the settings). To flash the RUU, move the file to the root of your SD card, boot into bootloader, and follow the directions on screen.
brick evo 3d
when i update mwakiousSGS2rom_v.3.0.03 to my evo 3d . this is my bi mistake .and after that my mobile is of ..so pls what can i do .help me
Hello,
I'm a little bit at a dead end after trying so much things.
My phone already was in repair for three times. The first time the replaced the mainboard because of a defective earspeaker. Before sending it in I was on the latest available Stock OTA update for my ROM (2.3.4, Retail DACH).
After I got it back after the first repair, I started to get trouble with GPS. Then also the touchscreen started to get a dead area and I send it in for repair the second time. I mentioned the GPS problems aswell, but they just changed the screen.
Then I send it in for the third time and now I have the third mainboard in my phone.
Unfortunately GPS still didn't work. Shows satelites, even sometimes gets a fix for some seconds, but the GPS Test App never reported a value for Accuracy.
Since I didn't want to send it in a again I started to search and found that this seems to be related to libnmea.so.
So I rooted the phone, exchanged the file, checked the permissions and tested it after reboot. Phone showed satelites, but the values for the satelites never went above 30 and it didn't get a GPS-fix within the 20 minutes I was testing it outside in the cold
So I followed another advice to flash a newer radio (N_01.77.36P) just to see if that helps. This required me to unlock the bootloader and install CWM Recovery, since this Radio I found was a fruit cake.
GPS isn't still much better now though... I drove a distance of 350 km (from work back to my home office) with always getting some satelites (approx. max. 7 at a time) displayed but only on the last 40 km I got my first fix, which then also displayed accuracy, so it might have helped a bit, I thought, but GPS fix only worked until I rebooted the phone the next time, since then it seems I didn't drive far enough to get a fix again...
Then I discovered the next problem...
Since unlocking killed my settings I had to make them again. My Exchange ActiveSync at work requires DeviceEncryption, and when the phone rebooted to enable encryption CWM Recovery came up with an error, that it doesn't recognize the parameter, and the phone didn't get encrypted and so I was without my contacts, calender and mails...
I couldn't find a way in the forums to restore the stock recovery, so I decided to reflash the stock-image with SBF.
Followed the guidance to delete cache, davlik cache and factory reset via cwm, and to erase different partitions using fastboot before using RSD Lite.
RSD Lite was 5.7 and the Motodrivers are 5.5.0, running on Win8 64bit.
RSD Lite flashed until 99% and then failed when trying to restart the phone in BP Bypass mode (0x70BE), and the phone was stuck with Error "Failed to boot 1".
I tried the ROM 1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31-release-keys-signed-rtdach.sbf
Then I found hints, that others were in the same boat and were able to recover from this error flashing this image
1FF-olympus_emara-user-2.3.4-4.5.2A-74_OLE-31.1-release-keys-signed-NonEFIGSRetail-EU.sbf
But this didn't help me either, even after more retries. I also tried flashing on three computers and even tried to flash under linux using a Knoppix Live CD. Flash was always performed until the end, but after the last reboot I had the failed to boot 1 again.
Since I didn't find any more usefull guidance of things I could try, I thought "give it another try with the bootloader from the unlock (intl-fix-try1.sbf), can't get really worser now" and so did I and voila device is back and running.
Tried it again to flash a full sbf and came back to the same error, flashed the bootloader.sbf and it's working again...
After that I rooted it again and replaced the libnmea.so file again. But didn't have chance to test it yet, if this helped in any way...
I don't have much hope and think, that I 'll need to send it back to repair again, so again my question, is there any way, to get rid of the "Unlocked" of the bootscreen?
I can think of two possibilities, maybe there is a patched version of this intl-fix-try1.sbf available, that doesn't display this word or there is a way to really get back to the stock bootloader...
Best Regards
Mario
Exactly whats ur problem?????can u be more specific !!!
Sent from my MB860 using Tapatalk
Currently my problem is having the word "unlocked" during boot. Guess they'll refuse or charge for service, when they see it, when I send it in for repair once again...
GPS is still not working as it used to before the first repair. It sees some satelites (max. observed signal strength in GPS Test app yesterday was 23), but doesn't get a fix, even after 30 minutes.
Mario1976 said:
Currently my problem is having the word "unlocked" during boot. Guess they'll refuse or charge for service, when they see it, when I send it in for repair once again...
GPS is still not working as it used to before the first repair. It sees some satelites (max. observed signal strength in GPS Test app yesterday was 23), but doesn't get a fix, even after 30 minutes.
Click to expand...
Click to collapse
Mario1976,
I am encountering a similar problem with my AT&T Atrix 4G running Fruit Cake 4.5.141 with BL unlocked.
I cannot get the Data Encryption to work with CWM Recovery 5.8.1.8.
I'm beginning to think that I'll need to restore the stock Android Recovery to be able to get the Data Encrytion to work.
So far, my previous attempts at flashing the stock 4.5.141 SBF using RSDLite has met with the sec_exception: febe, 35, 35 error.
I also tried to use another set of instruction for restoring stock recovery onto another device on my Atrix but to no avail:adb push install-recovery.sh /data/local
adb shell
su
mount -o rw,remount /system
cat /data/local/install-recovery.sh > /system/etc/install-recovery.sh
dd if=/system/recovery-from-boot.p of=/dev/block/mmcblk0p1Konker
Update:
I finally figured out that the sec_exception: febe, 35, 35 error meant that the SBF was not intended for the device. That led me to suspect that the system board is not an original AT&T US board. I gave an Asian stock SBF a try & viola! The phone was successfully restored to factory stock ROM with stock bootloader & the Unlocked words removed from the boot screen. Device encryption is also working without any issues.
Hello.
I have been reading around on the forums and havent been able to find a suitable fix for my phone.
First of all- Im not a huge fan of updating apps and such due to not having the best success with compatibility after the updates. Also I am NOT a developer or anything, have never rooted my phone or flashed ROMs because I never really understood it and didnt want to brick my phone. That being said im not a idiot when it comes to technology either. I know how to use linux a decent amount tho i dont because I own a mac and havnt had a "x86" computer for sometime
Back in December I was having problems with my phone so I took it to Sprint and got a replacement. I dont usually use my phone for internet while im at home (because I use my computer) and overlooked the setting that updates apps over wifi.
So fast forward a few months- I went to Europe for the first time this winter for a ski vacation and when i connected to wifi over there, my phone just started updating everything and started making my phone act wierd. It would freeze up for a while after boot after entering my password and it would take 15-30 minutes to unfreeze. I got used to it working like that. Besides i was only using my phone for basic internet stuff and taking pictures. I wasnt making any phone calls or anything. The day before i came home I tried to connect to a wifi network and in the network settings under wifi it said "error" and then immediately shut off and rebooted. That was the last time my phone was usable. From then on it is just stuck in a continuous boot loop. I have to remove the battery to stop it. When it tries to boot it goes through the animation process to the "now" part of the "welcome to the now network" animation during boot. I have messed around with the safe mode and other boot options in the boot menu but nothing seems to work.
I DONT WANT to hard reset my phone yet because ALL MY PICs are on the Internal memory of the phone from my trip. I know now that this was a stupid idea to have them on the internal memory. My SD card was getting full and had like 7 gigs internally so i saved all my pic there. My phone was also encrypted with the pattern password (yes i enabled it).
Is there any way to get my pictures off the phone? I dont know what build version, kernel etc... or any of the other technical information is.... Please help!!!! thank you :crying:
help
Hello ,
I have Installed Custom ROM in my Photon 4g MB855 Here is What I installed using( *How to install Jelly beans 4.1.2 Custom on Motorola Photon 4g )
and After installation I stuck at Motorola M logo .
So I could not even go Back Because whenever I try to install any stock or SBF file in RSD I get this error ..
*Failed To Re Enimerate*
And I also tried to Erase my Recovery and Install A custom TWRP like another Recovery manager but i get this error in FastBoot.
Erasing Recovery FAILED <Remote 00180001>
Writing Recovery FAILED <Remote 00180002>
I've read somewhere that its because your device is not unlocked and I also tried to install Pudding Unlock via RSD but failed to re-enumerate ..
RSD show my device as *SE FLASH SUNFIRE* ..
NOTE: I had made a BACKUP before flashing the Custom Rom and Now When I go to Recovery and Restore I cant see the BackUp .. But When I attach that SD card and There is BackUp .. That BackUp (2.3.5) Consists ..It Consists Following FIles..
Data.img
System.img
Cache.img
I'm totally confused How to Unlock my Photon (If it is) Please Help me getting my Phone BACK!
Does anyone have any suggestions for me at all?????
Hey,
I'm pretty new here, so don't hate on my lack of knowledge^^
Maybe I'm even in the wrong sub-forum
(I think there was a sub-forum dedicated to moto x, but this isn't a device-specific issue, so here should be fine - no?)
Got the following problem:
My moto x (2nd gen) is stuck in a loop. I get to the logo-screen, then it goes to "Encryption unsuccessful" and when I click "Reset", it restarts and fails upon trying to reset.
How I got here:
1) A while ago I wanted to encrypt the phone for the lulz (using its' own encryption-tool)
Followed the simple steps, as in having it charged up, but the encryption did not go through.
Don't remember having it to reset at first, it just booted, even though it had bugs after that:
-whenever I charged it, I had problems turning it back on after charging, had to turn off and back on for it to actually work.
-those notifications on top which one can normally open via sliding down, that sliding down did not work after that.
Eventually I did a hard-reset and it fixed the sliding-problem.
Charging also worked fine at first until it did not.
2) I ended up stuck in a boot-loop that went to the logo-screen back and forth (got to logo-screen, restarted, got to logo-screen, restarted, ...)
Tried to soft-/hard-reset using the VOL- and POWER combo.
The hard-reset itself threw some errors at me, something like "can't delete [whatever]".
Still, after a few tries it eventually went past the logo-screen to the encryption-step.
After another few failed resets and emptied cache via recovery-screen, it somehow ignored the encryption-step and turned on the phone (was a fresh version).
3) Worked fine for 1 whole evening, no crashes/glitches/anything until I had to charge it up.
Then it was back to the broken state.
Note: during 2) I tried to boot with a custom recovery-mode(TWRP), but couldn't get it running.
Then I tried to flash it, but anything I tried to install failed.
I had my suspicions, but eventually I got it straightened out: my phone isn't rooted, and the bootloader is locked.
I did get the code to root it via some steps and the motorola service, but the code did not work as it wanted me to unlock the phone first.
From what I've read, to do that I need to get into the settings and unlock/root it...
Funny thing: I can not turn on the phone to get into the settings.
So - anyone got ideas?
Warranty is gone since apparently my tinkering with the locked bootloader and unrooted phone still was visible and they voided the warranty.
Not sure I broke much/anything with that, though, since it DID work at some point after that (even if it was for a few hours before needing recharging)
Therefore I'm open to any suggestions since the alternative stop would be throwing it into the bin^^
Can I unlock the bootloader without having a working system?
Can I root it somehow without having to get into settings (since I can not turn it on in the first place)?
I did a fair share of reading, but most times the guides just assumed that I already rooted it, or forwarded me to a guide where it said "go into settings and spam the build to get advanced options, then simply root/unlock that damn thing". Tried to find a way to unlock/root it without being able to turn it on, but did not get lucky with the search.
If I could unlock and root it, I probably could go from there. Guides are pretty specific and seem to work for most.
Also, I would try the original android version first before searching for any custom systems.
(that is the smartest way to do, right? since I'm just a user and dont plan on doing more hacking/breaking)
Hope all that above wasn't too much to read
Thx for any advice in advance.
Edit:
Well, after what feels like 50 restarts it miraculously did not send me to the "Encryption unsuccessful" but instead booted like it should (as a fresh version, though - so had to backup).
Now I've turned on the thing in the settings so next time it breaks, which I expect to happen by tomorrow, I can flash that sucker.
Still - anyone knows how to enable all that stuff one normally does via settings some way that does not involve successfully booting it?
I mean, there should be a way to root/unlock it without having to turn it on first, right?
Edit2:
As expected, the flashing part was pretty easy, so I'm now sitting with a fresh android 6.0.
Two days in and it's still working fine, haven't had any complications (except battery draining faster then at the very beginning, but I think that's due to it hanging too much on the usb-cable during all those sessions of me trying to fix it - and generally I've had it charge over night a few times to often)
Still would appreciate any advice on how to unlock developer mode and usb-debugging within the bootloader or recovery-mode.