Database Users

no service

I am in desperate need of help from this great community! ... I have had multiple smartphones (palm, blackberry, hero) and have hacked them all so I'm not a total noob at this, but I must admit this has me stumped ...
I rooted my phone about a month ago and installed fresh 2.0d ... everything was great with the phone ... it was superfast for me and had alot of cool features added from the stock 1.5 ... then slowly I started to notice a few bugs creaping out ... nothing major or that I couldnt handle / work around ... then yesterday my phone was in roaming mode all day and last night about 8 it lost all signal period ... I decided it was time that I reflash 2.0d ... when I boot into recovery I can wipe the data but when I try to wipe the dalvik it tells me to "run deldalv via console!" I used fresh kitchen and wiped dalvik and reflashed fresh 2.0d ... I also flashed the patch from fresh for menu-menu ... I have tried this multiple times and I still am unable to get my phone to connect to the sprint network ...
I have tried to search the forums and google several times now so if I am asking a question that is already answered somewhere else please be so kind as to point me in the right direction.
Thanks for any help!!! =o)
EDIT: I have just finished restoring a nandriod backup and I'm still not able to connect to the sprint network ...
I am still looking through the forums for answers, I'm thinking maybe flashing a new radio? possibly flashing another ROM to the phone ...

wolfscmb said:
I am in desperate need of help from this great community! ... I have had multiple smartphones (palm, blackberry, hero) and have hacked them all so I'm not a total noob at this, but I must admit this has me stumped ...
I rooted my phone about a month ago and installed fresh 2.0d ... everything was great with the phone ... it was superfast for me and had alot of cool features added from the stock 1.5 ... then slowly I started to notice a few bugs creaping out ... nothing major or that I couldnt handle / work around ... then yesterday my phone was in roaming mode all day and last night about 8 it lost all signal period ... I decided it was time that I reflash 2.0d ... when I boot into recovery I can wipe the data but when I try to wipe the dalvik it tells me to "run deldalv via console!" I used fresh kitchen and wiped dalvik and reflashed fresh 2.0d ... I also flashed the patch from fresh for menu-menu ... I have tried this multiple times and I still am unable to get my phone to connect to the sprint network ...
I have tried to search the forums and google several times now so if I am asking a question that is already answered somewhere else please be so kind as to point me in the right direction.
Thanks for any help!!! =o)
EDIT: I have just finished restoring a nandriod backup and I'm still not able to connect to the sprint network ...
I am still looking through the forums for answers, I'm thinking maybe flashing a new radio? possibly flashing another ROM to the phone ...
Click to expand...
Click to collapse
Have you tried nandroiding back to the one you made just after root?? You did nandroid right after root, right??

chfields said:
Have you tried nandroiding back to the one you made just after root?? You did nandroid right after root, right??
Click to expand...
Click to collapse
Yes I have reflashed the nandroid backup several times ... I have reverted back to 1.5 and back to fresh 2.0d ... several times and still no luck getting it on the sprint network ...
I read through the Fresh 2.0d thread and saw someone mention that they had no service as well and someone told them to update the profile and PRL ... I have tried to do both of these several times with no luck ...
I am about to DL Fresh 2.1.1 and another radio and see if flashing them on the phone will help anything out ...

could also be an issue with the raido on the hardware side, if flashing a new radio doesnt fix the issue then flash the stock radio back and then run the RUU and take it in to have it checked out.

thanks for the help chfields and wtphoto ...
I have been reading post after post and messing with the phone all night trying to get it up and running again .. somehow during one of my updates to the phone it error-ed out and now will only turn the screen on ... but when I plug it into the computer the HTC logo showed up ... I tried to flash a RUU to the phone but I kept receiving error 110 ... after searching online I found a posting where this guy says has saved about 15 Hero's that were in the same state as mine
Unfortunately it seems a bit complicated to me ... I'm having to learn about adb and fastboot (I originally used fresh kitchen to root my phone) ... at this point I'm going to take a break from this and hopefully after a taxing day at work tomorrow will have enough energy to come home and pull my phone back from the brink of death

ouch you got the 110 error that sucks man, from what I heard his method to fix it does work though.

Hey like ive offered to another guy im willing to help you out if you want just pm me if im on ive been in your shoe a while ago
It is stressfull at times but as long as you phone turns on somewhat you dont have a brick.

lostinroot:) said:
Hey like ive offered to another guy im willing to help you out if you want just pm me if im on ive been in your shoe a while ago
It is stressfull at times but as long as you phone turns on somewhat you dont have a brick.
Click to expand...
Click to collapse
Thanks for your offer! =o) ... After my last post last night I ended up trying ONE MORE TIME to bring my beautiful Hero back from the brink of death ... I was actually able to fastboot it and then to root it again ... however the post that I found while is a GREAT resource, it isn't the clearest in all of the steps of what to do for those of us that have never messed with the manual rooting ... so I'm having to referance other posts at the same time
I thought that I had it fixed last night but when I tried to boot it into recovery so that I could flash it again it started to show a triangle with an exclamation point on the inside and a phone below it ... so I'm sure that I'm very close to bringing the phone back to life, just have to play with it a bit more ...
I'm currently at work dealing with month end (I work in finance) so hopefully I can try to go home early to take care of more pressing issues!

Code:
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\Shaun>cd C:\android-sdk-windows\tools
C:\android-sdk-windows\tools>adb devices
List of devices attached
HT0000000000 device
C:\android-sdk-windows\tools>adb push asroot2 /data/local/
931 KB/s (0 bytes in 74512.000s)
C:\android-sdk-windows\tools>
Correct me if I'm wrong but shouldn't the push asroot have some kind of bytes transferred? I have tried looking this up but I'm late for a birthday dinner ... the youtube video that I found shows 74512 bytes transferred
EDIT: I zeroed out my serial number just to be safe, in case anyone thought that might be an issue ...

after sifting through various forums and numerous posts I was finally able to get my phone booted into recovery! from there I was able to flash fresh 2.0d again and now have a working Hero again
However ... I'm left with my original issue that started this whole mess ... My phone will not connect to the sprint network ... I guess I'm off to many more google searches

You should try and update your PRL. If it is not 6066X then you are stuck roaming. I had this problem, and it was only after I got a new hero from the Sprint store that I found a fix. So just go to settings-about-system update and update PRL. You should get 60665. Hope that helps.
-------------------------------------
Sent via the XDA Tapatalk App

you could also try unrooting and sending it totally back to factory stock (see my signature for my guide) and then re-rooting again

My Hero is alive again!!!
After searching and reading every post I could get my hands on I was still unable to get my phone to connect to the sprint network ... I saw on the various forums that it was due to a PRL update issue ... I tried to use the built in PRL update feature with no success ... then I tried to manually update the PRL but was unable to without a code from sprint (and I wasn't willing to try a hack to find it on the phone) so I called sprint this morning and after spending over an hour on the phone with them I was finally able to get the PRL to update ... once that happend my phone was super happy!

[Q] Did something stupid, Softbricked.

Hey there, I recently purchased a Bell Atrix 4G. I rooted it and everything was going fine, so I thought I'd try the gingerblur rom for the device, the tutorial site didn't mention anything about not using it on a Bell Atrix, which I found out later was a bad idea (I did make a backup though at the backup prompt). So needless to say the phone is now at the "M screen flashing red led boot loop". What I wanted to know, is if that since I have access to fast boot, if there's any way to restore from that backup.tar file, or if I can use an at/t sbf file to restore to (I didn't try it in fear of making things worse). Thanks in advance!

Grimacexl said:
Hey there, I recently purchased a Bell Atrix 4G. I rooted it and everything was going fine, so I thought I'd try the gingerblur rom for the device, the tutorial site didn't mention anything about not using it on a Bell Atrix, which I found out later was a bad idea (I did make a backup though at the backup prompt). So needless to say the phone is now at the "M screen flashing red led boot loop". What I wanted to know, is if that since I have access to fast boot, if there's any way to restore from that backup.tar file, or if I can use an at/t sbf file to restore to (I didn't try it in fear of making things worse). Thanks in advance!
Click to expand...
Click to collapse
Whatever you do DO NOT USE THE ATT SBF! That is not meant for bell devices and will definetly make your situation even worse!

Yeah, I figured that would be the case.
Working on trying to push my backup files to my device atm

Grimacexl said:
the tutorial site didn't mention anything about not using it on a Bell Atrix,
Click to expand...
Click to collapse
dude, it's in CAPITAL RED LETTERS on both the tutorial website and the forum thread.
this guy had a similar situation, but i don't know if he got it fixed.
http://forum.xda-developers.com/showthread.php?t=1033184&highlight=bell+sbf
EDIT: attached

Yeah, the tutorial I used didn't say to not use it on bell atrix, but when it messed up, I went to all the other tutorials that have it in red, so I do feel pretty stupid.

Well, it's all good now, After pushing bell backup app and framework folders, I managed to get a working device (all be it with some force close crap which I'll iron out later) The device is working.

Never Before Seen or Discussed Soft Brick.

Let me start by saying im a noob well today i decided to root my Tmobile LG G2 running Lollipop 5.0.2 I searched many threads as im not advanced and i found kingroot. Used it version 4.80 and successfully rooted my phone. Then i tried superSU or what ever its called.. Did not work with king root.. So i did some research and came across Super Sume! I paid 3.99 i rebooted my phone and tried it out and it stuck on processing, did not do anything. So i forceclosed i rebooted again uninstalled it and ran it again. And again nothing. Waited half hour nothing. The loading bar would not move.. So i uninstalled the paid one and downloaded an earlier version of super sume. I think its 6.7 instead. I tried it and it installed super su on my device but would again not work. It also deleted king root files from the phone.. Since super su did not work i rebooted. Stuck on tmobile screen... Held the power button turned off the phone. Booted in recovery mode. Did a factory reset and am now stuck in the set up screen. Asks for the language i choose english then has me connect to wifi but when i go to type in the password no keyboard appears ive tried everything i turned in lanscape n tried it and keyboard will not launch so i cant type so I'm stuck. Even if i went to a no password wifi i would still be stuck in the type your name screen. Cause again NO KEYBOARD. What can i do ?? i will donate atleast 5$ if i can get help.

Download latest Lollipop V30h KDZ (stock firmware) for T-Mobile (D801) from here.
And use LG Flash Tool 2014 for flash KDZ: http://forum.xda-developers.com/showthread.php?t=2797190
It will fix your phone 100%. Use Kingroot then install this for TWRP. And update it from here. In the end, you are free to install any custom ROM you like. No need to donate.

khanjui said:
Download latest Lollipop V30h KDZ (stock firmware) for T-Mobile (D801) from here.
And use LG Flash Tool 2014 for flash KDZ: http://forum.xda-developers.com/showthread.php?t=2797190
It will fix your phone 100%. Use Kingroot then install this for TWRP. And update it from here. In the end, you are free to install any custom ROM you like. No need to donate.
Click to expand...
Click to collapse
Thanks for the reply but the website for the firmware u gave me.... It gives me a 403 forbidden access error.

PhoneNoobs said:
Thanks for the reply but the website for the firmware u gave me.... It gives me a 403 forbidden access error.
Click to expand...
Click to collapse
http://storagecow.eu/index.php?dir=Xda/LG+G2/Stock/T-Mobile+G2/Lollipop/

I am downloading a kdz from here at anothwr thread for my tmobile d80130c what flashtool settings do i need to use cdma or gsm and what do i need to input in the other fields on the flash tool. And what folder do i put the kdz file in for flashtool to have access to it.

I already have d80130c on my phone so should i be using that or do i have to use d80130h like u suggested? And should i do a normal flash or a cse flash? Sorry for all the noobie questions

Thanks it worked
I used cse flash and left all defaults in flashtool and it worked it removed my kingroot but after all the problem i went thru im just gonna leave it unrooted and sell my g2 i have two g3 phones currently so im gonna sell the g2 now and when i do i will donate 5$ as promised just send me your paypal info on a msg i should be able to sell it with in 3 days and send you the donation. Thank you so much bro i thought i bricked it.

PhoneNoobs said:
I used cse flash and left all defaults in flashtool and it worked it removed my kingroot but after all the problem i went thru im just gonna leave it unrooted and sell my g2 i have two g3 phones currently so im gonna sell the g2 now and when i do i will donate 5$ as promised just send me your paypal info on a msg i should be able to sell it with in 3 days and send you the donation. Thank you so much bro i thought i bricked it.
Click to expand...
Click to collapse
I didn't see your posts because i didn't mentioned or quoted. Be careful about that. You can see donate button below my avatar. But like i said before, i don't need to donate for this. Have a nice day!
http://forum.xda-developers.com//www.pinterest.com/pin/create/extension/

Hey i cant sell it because it has the screen jitters it turns out Nd theres a million threads about it with no fix. Do u know of any fix for that so i can sell this phone i will donate when i sell it. Used to be my moms phone shes like "sell it nobody has to know it has issues it only does it at random" im like "mom, i cant just **** somebody over like that this shyts annoying" i know ppl will buy it if i dont tell em but i dont have it in my heart to do so ive had ppl texting me to buy it until i told em about the issue. I wanted 120 for it now ill take 60 lol.

i have a solution
Here i have a perfect sol.
1)One word--"nandroid backup".yes download a nandroid backup of anyone with same phone as u are having.
2)put it in external sd in a folder naming "clockwardmod"
3)flash cwm or twrp. I have not used twrp,so i prefer cwm as i know more about it.
4)click "backup/restore"
5)now choose restore.
6)now wait and watch.
7)enjoy
8)xda is a helping website so no need of donation

Yeah i finally learned all that and more. I was just comong into the phone game. But its an old post i still have 2 lg g3 and a lg g2. Yeah i know but i like to stick to my words and if i would of sold it i woulda paid em i feel its the right thing to do. Now im mostly into hacking and cracking and thats why im barely here but this site has been great i never bricked once because of this site i had close calls but was able to unbrick. My favorite method of rooting the g3 is the one click script method it works flawlessly.. Im using prime gsm on one phone and stock lollipop on the other. My g2 has the screen jitters. Cant type the letter h in the keyboard cant draw straight lines, scrolls like crazy and cant detect touch on the dead center of the screen so i cant sell it. I use twrp n supersu. Twrp is more user friendly and supports otg so i just flash from my usb drives and keep my phone memory open i have the 32gb versions and i always have more than enough memory on em.. Thanx for the feed back tho i appreciate it bud

Phone started rebooting randomly yesterday, now stuck at Google splash screen

I'm pretty adept when it comes to adb/fastboot/flashing etc but I'm running out of ideas here.
Yesterday my phone rebooted twice on its own --- didn't think much of it (but probably should have in hindsight). Happened a third time and now all I get is the white "Google" splash screen with constant reboots.
Holding volume down does get me to bootloader --- however cannot get into recovery (same issue with google screen). Tried plugging phone into multiple PCs in bootloader mode but I get device cannot be recognized (usb device malfunction). Tried manually updating the driver - nothing.
All I want is to retrieve the photos/videos of my kids --- hoping there is some last resort that someone can suggest before I give up on this thing.
Ideas anyone?

UPDATE: Got phone to recognize via fastboot ---- still can't get to recovery. Anyway to get files?

Same happened to me, something is horribly wrong with the build(s) that came out this month as more and more people are having this exact issue. I was able to barely get mine to boot initially with the latest stock image, just long enough to upload all my pictures via Google Photos before it would freeze and go right back to the constant rebooting.
Eventually even trying a stock image stopped working, I RMA'd my phone.
This seems to be a ticking time bomb and is going to be a huge issue very soon. It's really going to be rough for anyone beyond their warranty period unless Google/Huawei steps up after they realize what's going on. I'm not even sure what I'm going to do with my phone once I get it back for fear of causing the issue again.

My bootloader is locked so I feel like I'm SOL here.... hoping for a miracle

Just got off the phone with Huawei tech support.... apparently its a known issue with no resolution currently. This is some bs

That's not gonna help you ATM but you should really always backup important stuffs. My important stuffs are also kid photo and they are backed up in my cloud AND in Google photos.
From bootloader screen, can you give us your device specs? Like emmc, date, sku,.. ?

NYYFan325 said:
Just got off the phone with Huawei tech support.... apparently its a known issue with no resolution currently. This is some bs
Click to expand...
Click to collapse
Wow really? Are you saying they wont allow you to RMA it? Are you still covered by the warranty?

Seanmiz said:
Wow really? Are you saying they wont allow you to RMA it? Are you still covered by the warranty?
Click to expand...
Click to collapse
Trying to find out now....
Is there anyway to reflash stock images with only being able to access fastboot and a locked bootloader?

NYYFan325 said:
Trying to find out now....
Is there anyway to reflash stock images with only being able to access fastboot and a locked bootloader?
Click to expand...
Click to collapse
I would grab the Nexus Root Toolkit (that's what I used for all of my resurrection attempts, makes it super easy)
http://www.wugfresh.com/nrt/
Use it to flash stock (and unlock the bootloader in the process) from Fastboot. Let it sit (and bootloop many times) afterwards as the popup suggests and see if you can get lucky with some access to your phone. Either way you can then relock your phone with the toolkit and you're ready to RMA.

The bootloader is not able to be unlocked since the setting was never checked within android itself. I let the phone sit trying to boot for a solid half hour or so just rebooting at the google logo. I think its just a brick at this point

NYYFan325 said:
The bootloader is not able to be unlocked since the setting was never checked within android itself. I let the phone sit trying to boot for a solid half hour or so just rebooting at the google logo. I think its just a brick at this point
Click to expand...
Click to collapse
I'm not sure what you mean, I could lock and unlock the bootloader at will, without anything but fastboot functionality.

Seanmiz said:
I'm not sure what you mean, I could lock and unlock the bootloader at will, without anything but fastboot functionality.
Click to expand...
Click to collapse
You probably had the box ticked in developer settings or had previously unlocked it.

I believe rootjunky posted a video on how to do it with bootloader being locked

Just got off the phone with tech support again.... phone is under warranty and they are going to send me a new one. Sucks about the pictures/videos but what can you do

Is it the recent updates that's the issue? I'm still on pure Nexus 7.0

Same happend to me and someone in another thread too.i think there is a big problem with the last build
Envoyé de mon HUAWEI VNS-L31 en utilisant Tapatalk

Wish I knew the cause.... as stated I was bone stock - locked bootloader and all (that's never going to happen again since I couldn't re-flash stock images because of this). Huawei was no help as to the cause other than to blame google.

NYYFan325 said:
Wish I knew the cause.... as stated I was bone stock - locked bootloader and all (that's never going to happen again since I couldn't re-flash stock images because of this). Huawei was no help as to the cause other than to blame google.
Click to expand...
Click to collapse
Well, to be fair, this issue seems to have just started popping up with a handful of us in the last week or two.
I'm sure they are in the process of trying to figure out what happened and why with the RMA units they have. Since we were all just fine prior to this month and suddenly had this happen on various 6P phones of different ages, I'm guessing some code that Google added lately can potentially corrupt the memory/storage in certain scenarios.

This is an escalating issue
ArN0V said:
Same happend to me and someone in another thread too.i think there is a big problem with the last build
Envoyé de mon HUAWEI VNS-L31 en utilisant Tapatalk
Click to expand...
Click to collapse
Have you requested RMA? The same happened to me too last monday night just browsing Chrome, but it isn't just the build people have in common but also the TWRP version 3.0.2-1, so everyone with their 6P still running, update your TWRP and change your ROM it sucks being a week without your phone besides losing all your files :crying:

GKti22 said:
Have you requested RMA? The same happened to me too last monday night, but it isn't just the build people have in common but also the TWRP version 3.0.2-1, so everyone with their 6P still running, update your TWRP and change your ROM it sucks being a week without your phone besides losing all your files :crying:
Click to expand...
Click to collapse
Yes i send it back to amazon.i'm waiting news from it

Any way to update via zip since ZTE's servers are dead?

My phone was broken through rigorous device testing at work. Took ZTE a very long time but they finally delivered my repaired phone in November. Been extremely busy and transfered my life to a replacement Moto G5 but now I want to go back to my trusted ZTE...
...except I can't update my device. What they sent back to me was a device with the last installed update from Jan 2017. Now that's OK if I can just go and update it, but I can't. Servers are dead, and I don't have the time to go and start rooting/unlocking/installing Roms. And I think because of how old the last update is, apps like Android Auto aren't working properly with my car.
Would be nice if the US gov't played nice and just allowed ZTE to at least keep their servers up and running, but I have no control of that. Right now I'm at the point where I'm deciding on buying a Oneplus 6 if I can't get this phone working properly. Android Auto is a #1 priority for me.
Is there a way to grab update Zips somewhere online and easily update from the updater tool? I did this before when I got my device to Android 7.1.1 ways back (I purchased my ZTE almost 2 years now).

Which one do you have the U, G and the Chinese version?

Really ? did you even searched ?
https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484

Sn8K said:
Really ? did you even searched ?
https://forum.xda-developers.com/axon-7/development/rom-guide-updates-to-stock-files-via-t3469484
Click to expand...
Click to collapse
Well, he did say
mozillameister said:
I don't have the time to go and start rooting/unlocking/installing Roms.
Click to expand...
Click to collapse
If he has the G model then there's this thread.

Via MiFlash

EwertonR19 said:
Via MiFlash
Click to expand...
Click to collapse
Not without the B35 stock firmware which no one seems to have as ZTE never put it up on the support page before everything went down.
I still have a fully stock phone for now and I have been trying to find a way to root without wiping my device so I can try to pull the OTA from /data, but so far I haven't had any luck.

KH_Lionheart said:
Not without the B35 stock firmware which no one seems to have as ZTE never put it up on the support page before everything went down.
I still have a fully stock phone for now and I have been trying to find a way to root without wiping my device so I can try to pull the OTA from /data, but so far I haven't had any luck.
Click to expand...
Click to collapse
FYI, just EDL the B35 with @djkuz B35 stock rom.
Give the guy some proper credits
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759

As i got my A2017G two day before, there was the v B02 installed on it! (from apr. 2017?)
Unfortunately, i can’t get a newer OTA update because all ZTE servers seems to be offline.
But I have found several v A2017G/B10 zip files in the internet. I have downloaded two of them and compared. Result=Equal
After putting some of the files onto my sd, the update was found and installed successful! Now i am on B10.
A little bit of work, but a good result!